Related
Hello all.... I am working on a group project where we will be using a dev G1. The phone was shipped to a another group member and before I can get my hands on it, he decided to upgrade the firmware from 1.0 to 1.6, having very little knowledge of android beforehand and therefore he cant really tell me what exactly he did either. He followed the directions on the HTC website. As far as i can tell, I do have the 26I radio, engineering SPL and 1.6 installed currently, not sure about the recovery though (i.e. stock 1.0 or 1.6). When I got the phone, root access was gone but followed some simple steps on this website to regain it. By way of typing in "su" in terminal emulator and in ADB shell, I now also have su. However I still cant flash anything. When trying to flash cm 4.2.5 in the recovery, the system verifies it and then aborts installation. I then tried to install the Amon-RA recovery to no avail. Tried fastboot, ADP, terminal, im not sure how to access the /data/ partition on the phone and there is no option for acessing the console in the recovery menu. Installing through ADB dosnt work, no test-keys in current recovery. In fastboot it says "okay" for both sending and writing the recovery but rebooting into recovery shows that it didnt work. In terminal it says "flash_image: not found". I'm kinda lost and need some help....
All I need is cm4.2.5 on the phone with root.
Thanks in advance.....
Edit: I triple and quadruple checked the name of the recovery image when trying to install through terminal. I'm pretty sure it cant find the command "flash_image" and not the file itself. Just wanted to clarify...
You could try downgrading to RC29: http://wiki.cyanogenmod.com/index.p...ngrading_to_RC29_.28US.29_or_RC7_.28Europe.29
halr9000 said:
You could try downgrading to RC29: http://wiki.cyanogenmod.com/index.p...ngrading_to_RC29_.28US.29_or_RC7_.28Europe.29
Click to expand...
Click to collapse
Tried that, already... That method only works for the stock T-Mobile G1's which have a different SPL. The Dev G1's come with engineering SPL and I have no idea how to flash the .nbh image from that. All it does I think is enable Fastboot, I cant get it to do anything else.
This fails?
fastboot flash recovery recovery.img
Nope... No luck, it says:
sending 'recovery' <4456kb>.... OKAY
writing 'recovery' <4456kb>.... OKAY
and then I reboot using "fastboot reboot", wait till the homescreen loads, and then go back into recovery and it still shoes the the triangle and the !.....
Bump...
Anyone?? Right now we just have a reallly expensive paper-weight in our hands ANY help/thoughts/comments would be very appreciated...
This thread is meaningless since there is NO SUCH THING as a "DEV G1".
alilbitanuthin said:
Hello all.... I am working on a group project where we will be using a dev G1. The phone was shipped to a another group member and before I can get my hands on it, he decided to upgrade the firmware from 1.0 to 1.6, having very little knowledge of android beforehand and therefore he cant really tell me what exactly he did either. He followed the directions on the HTC website. As far as i can tell, I do have the 26I radio, engineering SPL and 1.6 installed currently, not sure about the recovery though (i.e. stock 1.0 or 1.6). When I got the phone, root access was gone but followed some simple steps on this website to regain it. By way of typing in "su" in terminal emulator and in ADB shell, I now also have su. However I still cant flash anything. When trying to flash cm 4.2.5 in the recovery, the system verifies it and then aborts installation. I then tried to install the Amon-RA recovery to no avail. Tried fastboot, ADP, terminal, im not sure how to access the /data/ partition on the phone and there is no option for acessing the console in the recovery menu. Installing through ADB dosnt work, no test-keys in current recovery. In fastboot it says "okay" for both sending and writing the recovery but rebooting into recovery shows that it didnt work. In terminal it says "flash_image: not found". I'm kinda lost and need some help....
All I need is cm4.2.5 on the phone with root.
Thanks in advance.....
Edit: I triple and quadruple checked the name of the recovery image when trying to install through terminal. I'm pretty sure it cant find the command "flash_image" and not the file itself. Just wanted to clarify...
Click to expand...
Click to collapse
Pretty sure there is...
http://developer.htc.com/adp.html
Bump...
anyone?
alilbitanuthin said:
Pretty sure there is...
http://developer.htc.com/adp.html
Click to expand...
Click to collapse
Do you see ANYTHING on there that says "G1"?
Answer: No you definitely do NOT.
If I remember correctly, after you use fastboot to flash the new recovery image, you can't let the phone reboot or it will overwrite the recovery with the stock recovery image
The solution would be to use fastboot to flash either Cyanogen's or Amon_RA's recovery image, and be quick here, but when you send the fastboot reboot command be holding down the home button on the phone so it will boot to the custom recovery image
lbcoder said:
Do you see ANYTHING on there that says "G1"?
Answer: No you definitely do NOT.
Click to expand...
Click to collapse
lol, no need to nitpick, about the name no less. Thats the least of my worries
As long as you get the message across...
jackslim said:
If I remember correctly, after you use fastboot to flash the new recovery image, you can't let the phone reboot or it will overwrite the recovery with the stock recovery image
The solution would be to use fastboot to flash either Cyanogen's or Amon_RA's recovery image, and be quick here, but when you send the fastboot reboot command be holding down the home button on the phone so it will boot to the custom recovery image
Click to expand...
Click to collapse
That maybe it I'll give it a try as soon as I get back home. Thanks a lot for the help!!
Thanks a lot jackslim, finally got it to work!
So I finally rooted my N1 today using SuperOneClick. I'm on FRG83. Here's what I've done so far...
Rooted.
Installed ROM Manager.
Flashed with ClockworkMod.
Unable to do a NANDBackup -> Re-rooted -> Still unable -> Flashed with RA -> Successfully did a NAND Backup.
Downloaded MoDaCo's ROM -> Tried flashing -> "Signature Verification Error"
Tried flashing again -> Unable to enter recovery.
Flashed with an older version of Clockwork -> Entered recovery -> Tried flashing -> Same error.
Downloaded Cyanogen 6 -> After multiple tries -> Entered recovery -> Same error
Wiped/Factory Reset -> Cannot enter recovery.
There has to be a simple explanation. Please help!
Thanks a lot
Fastboot oem unlock
daveid said:
Fastboot oem unlock
Click to expand...
Click to collapse
Will that unlock the bootloader? Because I rather keep it locked for warranty!
Thanks
Try using RA recovery instead. You can install the last stable version through ROM manager.
fzr-r4 said:
Try using RA recovery instead. You can install the last stable version through ROM manager.
Click to expand...
Click to collapse
Did do it but it doesn't alway boot into recovery. It usually boots with a Android+triangle+! . If it does boot in recovery, it says signature verification error.
i.mac said:
So I finally rooted my N1 today using SuperOneClick. I'm on FRG83. Here's what I've done so far...
Rooted.
Installed ROM Manager.
Flashed with ClockworkMod.
Unable to do a NANDBackup -> Re-rooted -> Still unable -> Flashed with RA -> Successfully did a NAND Backup.
Downloaded MoDaCo's ROM -> Tried flashing -> "Signature Verification Error"
Tried flashing again -> Unable to enter recovery.
Flashed with an older version of Clockwork -> Entered recovery -> Tried flashing -> Same error.
Downloaded Cyanogen 6 -> After multiple tries -> Entered recovery -> Same error
Wiped/Factory Reset -> Cannot enter recovery.
There has to be a simple explanation. Please help!
Thanks a lot
Click to expand...
Click to collapse
hints on rooting without unlocking bootloader:
http://forum.xda-developers.com/showthread.php?t=792016
general Nexus One wiki:
http://forum.xda-developers.com/showthread.php?t=744720
besides I would not worry about unlocking the bootloader (fastboot oem unlock); it has been proven several times that HTC will honor the warranty if the device has a hardware failure, even if the bootloader is unlocked.
it also seems to be the easiest and safest way to get to root
... on another note... you want your thread to be in Q&A, not development. a moderator will probably move your thread soon.
daveid said:
Fastboot oem unlock
Click to expand...
Click to collapse
this. only. this.
I feel the guy (or gal). I like that my initial "X" screen doesn't have the unlocked icon on it. Big deal? I guess not? Personal preference? Yes.
I too like the boot logo with out the padlock, it looks tacky.
The one time I tried clockworkmod, it messed my phone up, I always go with RA's recovery.
Sent from my Nexus One using XDA App
Google's stock ROM overwrites the recovery at boot. That is why your RA or ClockworkMod is not sticking. As a workaround, you should flash your recovery before rebooting into it else you will boot into the stock one.
Here's where I'm at right now...
I can boot into recovery every time now.
On ClockworkMod... once I select the .zip file (tried 3 now), it starts. Opening, verifying. As soon as it gets to the installing command it exits and goes back into recovery.
On RA, it always says signature verification failed.
Any ideas?
Thanks for all your help guys!
i.mac said:
Here's where I'm at right now...
I can boot into recovery every time now.
On ClockworkMod... once I select the .zip file (tried 3 now), it starts. Opening, verifying. As soon as it gets to the installing command it exits and goes back into recovery.
On RA, it always says signature verification failed.
Any ideas?
Thanks for all your help guys!
Click to expand...
Click to collapse
1) did you unlock the bootloader (fastboot oem unlock)? -- i recommend it
2) which version of amon_ra are you using?... all above 1.8 (i am using 1.9 alpha) allow flashing unsigned *.zip files
3) make sure you have downloaded the CORRECT amon_ra recovery *.img file (for NEXUS, any other will not work)
4) rename the AR recovery file to recovery.img (for easier typing and error minimization when flashing in fastboot) then put it in a folder where fastboot can find it
5) fastboot flash recovery recovery.img
6) flash a ROM of your choosing (i like CM6) - make sure it's fully downloaded and the zip file is not corrupt (= check the md5 sum)
7) flash in amon_ra recovery
8) if you use CM6, have gapps ready (http://wiki.cyanogenmod.com/index.php?title=Gapps) and flash immediately after CM6
9) reboot
i.mac said:
Here's where I'm at right now...
I can boot into recovery every time now.
On ClockworkMod... once I select the .zip file (tried 3 now), it starts. Opening, verifying. As soon as it gets to the installing command it exits and goes back into recovery.
On RA, it always says signature verification failed.
Any ideas?
Thanks for all your help guys!
Click to expand...
Click to collapse
Get Amon RA 1.9a like so (has instructions for locked bootloader):
http://forum.xda-developers.com/wiki/index.php?title=Nexus_One/Recovery_Images
I use RA 1.8.0.1 to skip around signatures. I'm not unlocked and haven't had issues flashing or the phone unrooting.
Sent from my Nexus One using XDA App
Ignore everyone saying you have to unlock the bootloader, there's zero reason to do so..
You just didn't follow instructions. As someone posted, follow the link for the XDA Wiki recovery images. You missed the part where you have to remove two files, or it restores the recovery image. /!\ symbol = stock recovery; the system restores it automatically if you don't remove the two files.
So right now, read the guide, re-flash RA, remove the two files, then your recovery will stick.
As for one this-or-that ROM doesn't install; ask in their thread.
khaytsus said:
Ignore everyone saying you have to unlock the bootloader, there's zero reason to do so..
Click to expand...
Click to collapse
HTC has proven that they will fix hardware (dust, power button) with or without an unlocked bootloader so circumventing 'fastboot oem unlock' for warranty purposes is not only a bit more trouble for those who can't read/are new.. its also counter productive in light of the whole G2 debacle.. kinda like they give us nice things and we abuse them anyways..
crachel said:
HTC has proven that they will fix hardware (dust, power button) with or without an unlocked bootloader so circumventing 'fastboot oem unlock' for warranty purposes is not only a bit more trouble for those who can't read/are new.. its also counter productive in light of the whole G2 debacle.. kinda like they give us nice things and we abuse them anyways..
Click to expand...
Click to collapse
They denied my warranty (trackball does not scroll downwards anymore) stating they would have to charge $200 for the repair. But, I found a local shop that will do it for $40 and have it done in an hour. I have no regrets unlocking my bootloader, that is why I bought this phone.
I do believe it is the best method, and I would not abuse it just for warranty claims - in hopes that there will be another device with this ability.
Honestly, what's the point of owning a Google Developer phone if you're going to *****-foot around unlocking the full potential of your device?
Honestly, the first thing I did when I got this phone in the mail was unlock it. Best decision ever.
wdfowty said:
Honestly, what's the point of owning a Google Developer phone if you're going to *****-foot around unlocking the full potential of your device?
Honestly, the first thing I did when I got this phone in the mail was unlock it. Best decision ever.
Click to expand...
Click to collapse
To each his or her own, but I have the potential of my phone fully available. If I'd gotten the N1 in January, I may have unlocked the bootloader.
Since there were good root options when I got the phone without unlocking the bootloader, though, I was happy to go that route.
Sent from my Nexus One using XDA App
Hi,
i have a nexus one with a broken power button, my warranty is out so there is no replacement, i want to root it to be able to install trackball wake s,o i can open the mobile and close it.
when i try to access the bootloader i hold the trackball then i take off the battery 2 to 3 time to switch on, and if i keep holding the trackball it access the bootloader screen.
but i can't choose bootloader because i need to use the power button to do so, i also tried the universal androot, i got a message saying failed! no ~~~fu goo~~~.
my OS version is 2.2.2, build number FRG83G.
please any help.
You can try manual root. I find it easier getting the drivers to install when the phone is in fastboot, but it isn't essential...
http://www.nexusoneforum.net/forum/...mple-sdk-setup-manual-root-guide-windows.html
Sent from my Nexus One using XDA App
If you hold Vol Up + Track Ball and Remove & Insert your battery while your plug in to USB cable you can access Fastboot screen. But you will not be able to select any options because it needs power switch to select options.
many thanks danger-rat, i got a superuser access now on my list
i need one more thing if you please, how can i install cyanogenmod? because as i mentioned before i need trackball wake setting.
best regards,
The quickest way in my opinion is to install ROM manager from the market. You can then choose to install either Clockwork recovery image or Amon_RA. If you choose Clockwork then you can use ROM manager to automate backing up/flashing of new ROMs. Alternatively you can choose Amon_RA recovery, which I personally use. There are only a few differences other than layout but both are excellent recoveries.
Once you've installed a recovery image, you can either download CM7 manually and place it on your SD card or use ROM manager to download it. Depending on your choice of recovery you can use ROM manager to backup then flash or alternatively go into recovery manually and flash CM7 there. To reboot directly to recovery either hook the phone up to a PC and issue the command 'adb reboot recovery' or alternatively install an application like Quickboot which does the exact same thing through a GUI.
You shouldn't really have any problems once you've flash CM7 as it has a reboot to recovery option built in. Good luck
Edit: Oh and always, I repeat always Nandroid! It'll save you any headaches.
thanks man for the guide, it worked wonderfully, but what do Nandroid do?!
omarqa said:
thanks man for the guide, it worked wonderfully, but what do Nandroid do?!
Click to expand...
Click to collapse
It's like imaging software for a PC, it takes a screenshot of your system at that time which can then be restored should anything go awry. I have a couple that I switch between
Bootloop cyanogen
Hi all,
after all your help guys i managed to get my self into trouble again , after i installed cyanogen i found out that the market is not there, and i couldn't add gmail account also, so i recovered the previous one.
i thought I'd reinstalled cyanogen again, so after a couple of failures in installing it "getting an android with and explanation mark over the head", the last one worked but it booted into a boot loop, i keep getting the cyanogen screen again and again.
can i do something with command line such as adb shell
best regards,
I ran into the same problem, it's a little long winded but I found this to work. Also, it seems your recovery is reverting to stock. This is because of files recovery-from-boot.p and install-recovery.sh. After flashing the ROM go to terminal and issue the following commands (Without #) :
# su (Making sure to accept the root privileges prompt)
# mount -o remount,rw /dev/null /system
# mv /system/recovery-from-boot.p /system/recovery-from-boot.p.bak
# mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.bak
# reboot
More info here.
Then flash Amon_RA recovery or Clockwork during fastboot commands from my first link. Rename the image downloaded to recovery and issue the following command during fastboot:
fastboot flash recovery recovery.img
You can then follow the rest of the guide to return to recovery. If you ever end up in a bootloop again just follow the guide in the first link as is and you'll be back in recovery to recover a nandroid backup or flash again.
Also it seems you're missing the Googleapps (Gapps) package for Gingerbread. Flash this after flashing CM7.
omarqa said:
Hi all,
after all your help guys i managed to get my self into trouble again , after i installed cyanogen i found out that the market is not there, and i couldn't add gmail account also, so i recovered the previous one.
i thought I'd reinstalled cyanogen again, so after a couple of failures in installing it "getting an android with and explanation mark over the head", the last one worked but it booted into a boot loop, i keep getting the cyanogen screen again and again.
can i do something with command line such as adb shell
best regards,
Click to expand...
Click to collapse
Did you flash a compatible gapps package (Google apps)? The market and other Google apps are not distributed with Cyanogen ROMs, and have to be flashed separately...
Edit: Sorry, must have overlooked the tail end of the post above...
Sent from my Nexus One using XDA App
how to flash the ROM
omarqa said:
how to flash the ROM
Click to expand...
Click to collapse
There should be an option saying something along the lines of 'Flash zip from SD card'. Simply browse to the zip and flash.
whenever i try to do recovery or anything i keep getting FAILED (remote: signature verify fail) anybody know why i keep getting this???
omarqa said:
whenever i try to do recovery or anything i keep getting FAILED (remote: signature verify fail) anybody know why i keep getting this???
Click to expand...
Click to collapse
Is your device unlocked? It must be unlocked to issue certain fastboot commands.
Which custom recovery do you have installed?
Sent from my Nexus One using XDA App
thanks guys, it got fixed.
so how can i install cyanogenmod, every time i try to install version 6.1.1 i get a android log with exclamation mark over it, any ideas
your help is really appreciated,
edit: i mean by fixed that i restored the original version of the device.
That's the stock recovery (hence my previous question)...
You need to install a custom recovery, and also delete the following two files:
/system/etc/install-recovery.sh
/system/recovery-from-boot.p
(as stated by HD earlier)
Sent from my Nexus One using XDA App
DJ Steve ported CWM 4.0.1.4 with the release of 507.
Requirements:
Stock 5xx based rom [Honeystreak is not supported!]
Ability to enter fastboot mode: Fastboot+ADB.zip
Battery with 60% or greater charge
Basic understanding of the command line
Install Instructions:
Download recovery.img
flash the recovery with "fastboot flash recovery recovery.img"
Finished
Credits:
DJ_Steve for porting it
Koush for creating clockwork mod
I take no credit beyond this basic guide
Notice:
The Streak 7 with HC might now detect the driver properly, if it doesnt you must force install it using the "Android ADB Interface" from the list of available drivers
Will not work on 2.2.x, you must use CWM 3.0 for that.
Do not attempt to wipe data from within CWM, it will likely case a boot loop afterwards.
Thank you!!
Can I just push this recovery to my recovery partition within 3.2?
Im having issues having my PC at work recognize the fastboot device, and installing the drivers.
I am on xp..
TIA!
'error: cannot load 'recovery.img'
I got fastboot going fine, commands like 'fastboot reboot' are working.
However just above when I use your line to flash recovery, any ideas on what it might be!?
Uploaded new version of fastboot+adb.zip hopefully it has the correct IDs so you dont have to force install it.
Are you sure you downloaded the image correctly, and did you name it correctly when using fastboot
Yeah I was making a repeated typo when pointing fastboot to the recovery but its all working now, thanks a lot.
Clockwork mod (cool blue writing) and rooted all within a few days, good work and thanks to all involved.
FWIW I tried this on the T-MO stock 2.2.2 ROM. The install went fine, I copied S7-4.0.1.4.img to recovery.img and ran the fastboot command with no problems.
I power up the Dell Streak 7 while holding power and the up volume key, and get the menu as expected. I Select "Software Upgrade via update.pkg on SD Card", and the message "Booting recovery kernel image" is displayed.
At this point the machine seems to be frozen. I can reset with a paper clip, and reboot the machine into 2.2.2 just fine, but if I cannot resolve why it does not show the clockwordmod menu, then I guess it is back to NVFLASH.
So what am I doing wrong? do I need an SD card in the device with an update.pkg on the card? Or is there something else?
Oh that was a strong possibility.
CWM 4.0 uses the 507 kernel as a base. 507 will not boot without updating the bootloaders.
So that means CWM 4.0 wouldnt be able to boot unless you had 50x installed.
TheManii said:
Oh that was a strong possibility.
CWM 4.0 uses the 507 kernel as a base. 507 will not boot without updating the bootloaders.
So that means CWM 4.0 wouldnt be able to boot unless you had 50x installed.
Click to expand...
Click to collapse
Probably a good idea then to remove that "Assumed to work on 2.2.2" phrase then from your first append.
So I guess it is NVFLASH time ... Or could I somehow flash back only the original recovery.img using fastboot somehow?
Post updated, i needed someone to actually confirm that it didnt work as i dont have access to a s7
dblml320 said:
Probably a good idea then to remove that "Assumed to work on 2.2.2" phrase then from your first append.
So I guess it is NVFLASH time ... Or could I somehow flash back only the original recovery.img using fastboot somehow?
Click to expand...
Click to collapse
I posted over at TabletRoms yesterday that the new recovery did not work with Froyo 2.2.2.
To answer your question, all you have to do is fastboot flash the old CWM recovery, version 3xx something I think it is.
"waiting for device " and nothing happen !!! what should i do? i can not install driver using files in : Fastboot+ADB\Win32\Streak 5+Streak 7+Venue\Win7 !
cdzo72 said:
I posted over at TabletRoms yesterday that the new recovery did not work with Froyo 2.2.2.
To answer your question, all you have to do is fastboot flash the old CWM recovery, version 3xx something I think it is.
Click to expand...
Click to collapse
Like he said if you flashed it on a s7 that's still on 2.2.x just reflash with the CWM 3.0 one and that one will work fine on 2.2.x
Is there another way to root stock 3.2?
I am getting this error in fastboot...
"Flashing StorMgr partition recovery
Read after write verify partition recovery"
Not the stock one, as no other rooting tools work on it.
Ways to get around it include: using a pre-rooted rom or using a custom rom (which are normally pre-rooted)
Something may be wrong with your device/install if that is coming up. Or possibly your download was bad, try re-downloading it.
I tried re-downloading didn't work, I have stock rom, I don't think I can install a custom or pre-rooted rom without installing CWM?
You can with nvflash, as honeystreak is ment to be installed with nvflash then updated with the bundled CWM, which is prerooted
Whichever method you decide is up to you, as I cannot formally recommend that one method is better then the other.
thesmacker11 said:
Is there another way to root stock 3.2?
I am getting this error in fastboot...
"Flashing StorMgr partition recovery
Read after write verify partition recovery"
Click to expand...
Click to collapse
Well just as an update I tried this on a windows xp, windows 7 32bit, windows 7 64bit computer, and redownloaded that file each time and it still does the same thing on my device.
It's likely your device itself that's the issue then, I cant be more specific as I dont own a S7
I'm not sure if I should be asking questions here or over in another forum. Figure I'll start here...
I was sorely missing app2sd in honeycomb so went to use and install Link2SD figuring I'd use that. But it doesn't seem to see the second partition I've made on my SDHC card. I can mount the card on Mac OS and Linux and both mount the two partitions on the card so I feel pretty sure I formatted the card correctly. I saw some comment about a change in the way CW mounts things and it causing troubles in the Link2SD thread but I don't understand enough about the magic of Android and how it mounts discs, although I know it had Linux roots, so the comments in that thread weren't clear to me what I can do to get Link2SD working or for that matter even start to gather info to try to figure out what's wrong. Can anyone help me out or point me to a thread that can get me started in figuring out what's going wrong?
Sent from my HTC Flyer P512 using Tapatalk
ok so i installed the drivers for fastboot and i can enter fast boot , but how can i push the file? soory im a newb with the streak.
If coming from the original JellyBean and have not updated your custom recovery since, you will need to install the recovery provided below. This step only needs to be performed once to support the newer updates.
Recovery Update
Boot into bootloader mode, connect the USB cable, and from a terminal window or command prompt type:
Code:
fastboot flash recovery recovery.img
To root an OTA, the procedure is pretty simple.
Code:
Copy the OTA from the cache folder to the sdcard.
Move the OTA zip somewhere it can be opened and unzip it
Go to system/etc/ to find the file named recovery and delete it
(extension may vary, but it is always named recovery)
Open the META-INF/com/google/android/updater-script
Delete all of step 1 and step 3 so that all that is left is the large middle portion without any steps
That's it. You have made the same files you find here.
Download the desired package below and copy it to your sdcard, along with the SuperSU recovery package.
Boot into recovery, select install from sdcard, and choose the update. Go back and repeat the install for SuperSU.
KitKat Update 98
KitKat Update 99
Lollipop Update 110
XDA:DevDB Information
Nvidia Root-Friendly Updates [No Wipe], ROM for the Nvidia Shield
Contributors
twistedumbrella
ROM OS Version: 2.3.x Gingerbread
Version Information
Status: Testing
Created 2014-11-08
Last Updated 2018-07-05
twistedumbrella said:
The new update has a few things that require updating the recovery, but since a recovery is not officially developed, updating the kernel of the existing recovery will do the trick. Flash this first.
Recovery Update
The install requires removing the assert checks since there is an error that the device is a Thor but looking for a Roth (same thing, right?). Install this from the new recovery.
KitKat Update
Immediately after installing the update, install the SuperSU recovery package to restore root and you're all set.
http://download.chainfire.eu/supersu
Click to expand...
Click to collapse
So install the first zip in your current recovery and then reboot recovery. After that, flash the next two back to back?
NapalmDawn said:
So install the first zip in your current recovery and then reboot recovery. After that, flash the next two back to back?
Click to expand...
Click to collapse
Recovery first, then the two back to back. The old recovery won't flash it properly because of new metadata commands
twistedumbrella said:
Recovery first, then the two back to back. The old recovery won't flash it properly because of new metadata commands
Click to expand...
Click to collapse
Currently my shield is 4.3, rooted and has a kernel of 3.4.10. When I boot to recovery, I get the broken android guy with the red triangle. I think if I remember right, when I was rooting it, I had issues getting a working recovery on there since mine was fairly new when I got it. So what is thebest way to install that first zip? Would I be doing it via fastboot?
NapalmDawn said:
Currently my shield is 4.3, rooted and has a kernel of 3.4.10. When I boot to recovery, I get the broken android guy with the red triangle. I think if I remember right, when I was rooting it, I had issues getting a working recovery on there since mine was fairly new when I got it. So what is thebest way to install that first zip? Would I be doing it via fastboot?
Click to expand...
Click to collapse
First off I want to say thanks umbrella, for coming up with this method.
Bit off topic but I figured I would throw it out there, when you get the broken android guy, your recovery is doing exactly what it's supposed to. It's working, dont quote me here but I think pressing home and back simultaneously will get the menu to come up. I could be wrong on the button combo but there is a combination of button's to get the stock recovery menu to come up. If I remember right my droid X was the same way.
KitKat Update Without Complete Re-root
hexitnow said:
First off I want to say thanks umbrella, for coming up with this method.
Bit off topic but I figured I would throw it out there, when you get the broken android guy, your recovery is doing exactly what it's supposed to. It's working, dont quote me here but I think pressing home and back simultaneously will get the menu to come up. I could be wrong on the button combo but there is a combination of button's to get the stock recovery menu to come up. If I remember right my droid X was the same way.
Click to expand...
Click to collapse
Quite possible. I stripped out the recovery in the update and used fastboot on recovery for this one. I rushed through it a bit lol.
If I remember right, I think it's by-name/SOS and the update uses it to install the system before flashing the recovery to the partition. I didn't update it, though, just in case that wasn't a secondary partition.
twistedumbrella said:
Quite possible. I stripped out the recovery in the update and used fastboot on recovery for this one. I rushed through it a bit lol.
If I remember right, I think it's by-name/SOS and the update uses it to install the system before flashing the recovery to the partition. I didn't update it, though, just in case that wasn't a secondary partition.
Click to expand...
Click to collapse
Ahh I gotcha. Well that's good to know. I haven't had a chance to really look at many of the files yet. Do you know if nvidia released the factory recovery packages yet?
EDIT:
Nevermind looks like 72 is out now.
Yeah, they are pretty good about that. It may be nearing the last update for this version, though
hexitnow said:
First off I want to say thanks umbrella, for coming up with this method.
Bit off topic but I figured I would throw it out there, when you get the broken android guy, your recovery is doing exactly what it's supposed to. It's working, dont quote me here but I think pressing home and back simultaneously will get the menu to come up. I could be wrong on the button combo but there is a combination of button's to get the stock recovery menu to come up. If I remember right my droid X was the same way.
Click to expand...
Click to collapse
Shield+home at the broken android guy brought up a menu.
What is the best way to install the recovery update file? Is this something that is done by booting the shield into the bootloader and then doing it via fastboot on the PC?
NapalmDawn said:
Shield+home at the broken android guy brought up a menu.
What is the best way to install the recovery update file? Is this something that is done by booting the shield into the bootloader and then doing it via fastboot on the PC?
Click to expand...
Click to collapse
Exactly
twistedumbrella said:
Exactly
Click to expand...
Click to collapse
Awesome. Thank you. Alternatively, I could accept the OTA and then push SU back to it again like I did the first time it was rooted right?
Last question-we have a working CWM recovery for the shield I believe. Are there any recoveries that work with the shield while running KitKat?
NapalmDawn said:
Awesome. Thank you. Alternatively, I could accept the OTA and then push SU back to it again like I did the first time it was rooted right?
Last question-we have a working CWM recovery for the shield I believe. Are there any recoveries that work with the shield while running KitKat?
Click to expand...
Click to collapse
The OTA will restore the stock recovery. This way updates it to one compatible with KitKat.
KitKat Update Without Complete Re-root
OTA 98 has been added. No recovery update is needed coming from 72. Flash the build and SuperSU and off you go. No data wipe necessary, either.
Link to the Recovery is not working :crying:
I am trying to install with the CWM Recovery and getting Status 7 errors, I try in stock recovery and get errors for Signature Verifications.
Neoistheone2000 said:
Link to the Recovery is not working :crying:
I am trying to install with the CWM Recovery and getting Status 7 errors, I try in stock recovery and get errors for Signature Verifications.
Click to expand...
Click to collapse
Updated
twistedumbrella said:
Updated
Click to expand...
Click to collapse
Thanks, that worked a treat
Yeah, to clarify, in recovery, you must press and hold Shield and Home buttons for a second, then release to bring up the menu. Then use X and Y to navigate, A to select. Don't understand why the bootloader or recovery don't use the D-pad at all. They're weird. Anyway, downloading this now, and will report back in a few minutes. This is just sideloaded via the stock recovery, right? I hope so, that's how I'm doing it right now.
EDIT: Nope. Failed again.
E:footer is wrong
E:signature verification failed
Installation aborted.
Click to expand...
Click to collapse
I think I'll try that new recovery (funny, because I had flashed the one included in the original update archive, still had issues). I shouldn't have to use that one, I was on update 92 already.
EDIT 2: Oh, I'm dumb. Here I thought this was still being done with the STOCK recovery. Didn't realize this would flash in CWM. Awesome. Flashed SuperSU 2.16 while I was at it. Rebooted, and it's at .98, with root access. You ROCK, @twistedumbrella!
Did you do this with update 99 yet? Just came out today.
GuyInDogSuit said:
Did you do this with update 99 yet? Just came out today.
Click to expand...
Click to collapse
I don't even have it yet. I usually wait for it to come through on the device instead of going to the site. Faster to copy than download again.
twistedumbrella said:
I don't even have it yet. I usually wait for it to come through on the device instead of going to the site. Faster to copy than download again.
Click to expand...
Click to collapse
Hmmm. It started downloading as soon as I turned mine on. I'm just gonna do the usual process.