search

tonyho / galaxy-nexus-linux-toolkit

Automatically exported from code.google.com/p/galaxy-nexus-linux-toolkit
0 stars 0 forks source link

Instructions do not agree with Nexus 7 Recovery Mode menu #2

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
Using unlt.tgz v. 1.0, uploaded Aug 22, with a Nexus 7...

The instructions say:

4. Wait for automatically reboot in Recovery Mode.
5. Go to 'install zip from sdcard' >> 'choose zip from sdcard' >> 'GNLT'
   and choose 'su.zip'.
6. Go to 'Go back' >> 'reboot system now'.

My comments follow:

- Step 4 works as expected
- Step 5 should start by saying "Press Power and Volume up buttons at the same 
time to see the menu."  
- There is no "install zip from sdcard" in the recovery mode menu.  The menu 
items are:
  reboot system now
  apply update from ADB 
  wipe data/factory reset
  wipe cache partition

If I choose "apply update from ADB" the message appears as follows:
  Now send the package you want to apply to the device with "adb sideload <filename>"...

The discrepancy may be because there is no physical SD card in the Nexus 7, or 
it may just be a different recovery bootloader.

Original issue reported on code.google.com by jmat...@gmail.com on 30 Aug 2012 at 10:19

GoogleCodeExporter commented 8 years ago 
But for rooting, you first have to flash CWM Recovery. That's why the 
instructions are different. Please flash clockworkmod recovery and then root.

Original comment by lucasfa...@gmail.com on 30 Aug 2012 at 10:50

GoogleCodeExporter commented 8 years ago 
I thought I did that successfully first, but I will try it again.

After the CWM step, I expected to see something different on the boot screen, 
but it looked the same.  Maybe that step failed.  If it doesn't have a 
different result this time, I'll update this issue.

Original comment by jmat...@gmail.com on 30 Aug 2012 at 11:06

GoogleCodeExporter commented 8 years ago 
Having tried these steps again, here are the results:

The CWM Recovery step appears to work, but there is no difference in the screen 
at boot.   The system recovery menu is the standard Android system recovery.

Everything appears to work in the root step as well, with the results described 
in the issue above.

Original comment by jmat...@gmail.com on 30 Aug 2012 at 11:26

GoogleCodeExporter commented 8 years ago 
Please run again the script and copy all the output here.

Original comment by lucasfa...@gmail.com on 31 Aug 2012 at 8:03

GoogleCodeExporter commented 8 years ago 
Here's the ClockworkMod flash output.  When the device reboots in recovery mode 
in the next step, the recovery mode menu is the standard Android system 
recovery.

I see that the fastboot command is flashing to the 'recovery' partition.  Does 
adb provide a way for me to verify the contents of that partition without being 
rooted?

********************************************************************************
*                Universal Nexus Linux Toolkit v1.0 by tatelucas               *
********************************************************************************
Flash ClockworkMod Recovery

Before starting the process your device must be in Android Debugging Mode.
In the following instructions you will learn how to do it:

1. Power on your device and connect the device to your PC via USB.
2. Go to 'Settings' >> 'Developer options', turn ON the switch,
   and check 'USB debugging'. You're now in Android Debugging Mode!
3. Do you want to start the process? [Y/N]: Y

sending 'recovery' (6480 KB)...
OKAY [  0.777s]
writing 'recovery'...
OKAY [  1.239s]
finished. total time: 2.064s
rebooting...

finished. total time: 0.020s

Press ENTER to return to the main menu...

------------------------------
Here's the root output...

********************************************************************************
*                Universal Nexus Linux Toolkit v1.0 by tatelucas               *
********************************************************************************
Root the device

Before starting the process your device must be in Android Debugging Mode.
In the following instructions you will learn how to do it:

1. Power on your device and connect the device to your PC via USB.
2. Go to 'Settings' >> 'Developer options', turn ON the switch,
   and check 'USB debugging'. You're now in Android Debugging Mode!
3. Do you want to start the process? [Y/N]: Y

4. Wait for automatically reboot in Recovery Mode.
5. Go to 'install zip from sdcard' >> 'choose zip from sdcard' >> 'GNLT'
   and choose 'su.zip'.
6. Go to 'Go back' >> 'reboot system now'.
1187 KB/s (674673 bytes in 0.554s)

Press ENTER to return to the main menu...

Original comment by jmat...@gmail.com on 3 Sep 2012 at 4:37

GoogleCodeExporter commented 8 years ago 
Are you running on a 32 bit or 64 bit OS?

Original comment by lucasfa...@gmail.com on 3 Sep 2012 at 9:19

GoogleCodeExporter commented 8 years ago 
It's a 64-bit OS.

Original comment by jmat...@gmail.com on 3 Sep 2012 at 10:01

GoogleCodeExporter commented 8 years ago 
Please install 32 bit libraries and try again. Search in Google how to install 
them. Please tell me if that fix the issue.

Original comment by lucasfa...@gmail.com on 13 Sep 2012 at 3:22

GoogleCodeExporter commented 8 years ago 
I have had the same problem, and tried on both 64 and 32bit Ubuntu. Is this 
something to do with Jelly Bean?

Original comment by ch...@witte.net.au on 13 Sep 2012 at 8:12

GoogleCodeExporter commented 8 years ago 
OK, I'm guessing it has something to do with this, from 
http://forum.xda-developers.com/showpost.php?p=20843237

"For those of you that don't know, every OTA update places two files on your 
system (that are not there on a non-update stock ROM) that re-flash the stock 
recovery on EVERY boot. The two files are /system/recovery-from-boot.p and 
/system/etc/install-recovery.sh. You need to make sure that these files are 
either deleted or renamed, or else CWM will disappear when you reboot. These 
files serve no purpose other than re-flashing the stock recovery on every boot. 
So, if you've recently gotten an OTA and applied it, your CWM is gone... Use 
something like Root Explorer, delete them, and re-flash your CWM recovery."

I tried moving them, but I can't without root permissions, and I can't get root 
without flashing CWM first!

Original comment by ch...@witte.net.au on 13 Sep 2012 at 8:39

GoogleCodeExporter commented 8 years ago 
The package ia32-libs (Debian) was already installed.  Just in case, I also 
installed ia32-libs-dev.  The result was the same as before:  the system 
recovery is the standard Android system recovery.  When there is time, I will 
look into the issue mentioned in comment 10.

Original comment by jmat...@gmail.com on 15 Sep 2012 at 10:07

GoogleCodeExporter commented 8 years ago 
It was easy to get the files in question with adb.  The file 
/system/etc/install-recovery.sh looks like it probably does what message 10 
describes.  I'll attach it to this message.  It may be possible to rename, 
move, or delete the files with adb, but I hesitate to try it without being sure 
I'm not going to damage something beyond repair.

Original comment by jmat...@gmail.com on 15 Sep 2012 at 10:13

Attachments:

GoogleCodeExporter commented 8 years ago 
It looks like I should be able to check for the effect of this script in the 
system log, but I don't yet know where to find it on the Android filesystem.

Original comment by jmat...@gmail.com on 15 Sep 2012 at 10:16

GoogleCodeExporter commented 8 years ago 
Work around:

Instead of doing an automatic, do a manual install of clockworkmod recovery.  
Once it is installed do NOT reboot.  Immediately go into recovery mode.  Once 
you are in clockworkmod recovery, then go to reboot.  Before it reboots, CWM 
checks for these files.  If they are there it will ask you if you want to 
remove them, answer yes.

Original comment by ch...@witte.net.au on 16 Sep 2012 at 4:51

GoogleCodeExporter commented 8 years ago 
The manual install worked.  Thanks!

Original comment by jmat...@gmail.com on 19 Sep 2012 at 4:29

GoogleCodeExporter commented 8 years ago 
On 4.2, the manual installation method works though throws an error if the 
other method was used previously "mkdir failed for /sdcard/UNLT, File exists" 
(su.zip was obviously copied over correctly first time). You might want to 
check for that in the script.

I'm guessing you could just apply the su.zip while in CWM the first time?

Original comment by mike.ham...@gmail.com on 27 Nov 2012 at 5:15

GoogleCodeExporter commented 8 years ago 
[deleted comment]
GoogleCodeExporter commented 8 years ago 
Monica here from <a href="http://www.nexus10reviews.com/"> Nexus 10 Reviews </a>

May I ask what Ubuntu version are you using?

Original comment by monicaod...@gmail.com on 8 Dec 2013 at 8:12