Related
I know there have been similar threads, and I'm sorry that I'm raising another one. But reading to all those old topics didn't help me.
It's a friend's i9020T, bought in the US, so returning it back would be a real problem. He never unlocked bootloader, never applied any custom ROMs or Recovery, always updated it over OTA, and sometime in November, after reboots, phone started to hang on Google logo. Usually, it helped to remove the battery and wait some time, but it doesn't any more. We tried to remove it for a full day, didn't helped.
I tried going into recovery and doing full wipe and cache wipe - didn't help
I tried to unlock the bootloader, can select 'Yes', apply it via Power button, but the phone hangs.
If I want to flash anything with fastboot (boot, system img), it complains about locked bootloader
I tried Odin as well, but can't trick the phone into download mode with both volume up and down, again reports to unlock the bootloader
Is there any way to and how to fix this? I cannot transfer anything to internal memory, have stock recovery?
Thanks a lot to all of those who are willing to help, and I've really want to somehow fix the phone, because I don't have here in Serbia where to repair it. Several mobile providers only imported i9023, so they can't fix i9020T
I'm having the exact same problem with a GT-i9020 so would be interested in any help on this!
May need to format phone. Basically reflash latest update via boot loader. Wipe system to factory. And wipe sd
Sent from my Full Android on Crespo using Tapatalk
RANDYRKELLY said:
May need to format phone. Basically reflash latest update via boot loader. Wipe system to factory. And wipe sd
Sent from my Full Android on Crespo using Tapatalk
Click to expand...
Click to collapse
but I downloaded 2.3.6 stock from here, unpacked in the same folder where adb and fastboot are, and tried to do fastboot flash boot boot.img and so, and didn't work, was bugging me that bootloader isn't unlock
Highl1 said:
but I downloaded 2.3.6 stock from here, unpacked in the same folder where adb and fastboot are, and tried to do fastboot flash boot boot.img and so, and didn't work, was bugging me that bootloader isn't unlock
Click to expand...
Click to collapse
That's the problem dude u don't unpack it. U need to leave as a update zip. Look on xda for the stock 4.0.3 update zip or wait till I provide link. U go thru stock recovery if unrooted, and flash with it. To unlock boot loader u need to be in fastboot and type fastboot oem unlock. But u wait first. Lets get it booted. I'll find link.
Sent from my Full Android on Crespo using Tapatalk
Read here
http://www.androidcentral.com/how-manually-update-your-gsm-nexus-s-ice-cream-sandwich
Sent from my Full Android on Crespo using Tapatalk
RANDYRKELLY said:
That's the problem dude u don't unpack it. U need to leave as a update zip. Look on xda for the stock 4.0.3 update zip or wait till I provide link. U go thru stock recovery if unrooted, and flash with it. To unlock boot loader u need to be in fastboot and type fastboot oem unlock. But u wait first. Lets get it booted. I'll find link.
Sent from my Full Android on Crespo using Tapatalk
Click to expand...
Click to collapse
I'll wait for your link and instructions, it's obvious that I am doing something wrong
Thanks mate!
RANDYRKELLY said:
Read here
http://www.androidcentral.com/how-manually-update-your-gsm-nexus-s-ice-cream-sandwich
Sent from my Full Android on Crespo using Tapatalk
Click to expand...
Click to collapse
But I have stock recovery and can't copy anything to internal memory, since my phone doesn't boot
Highl1 said:
I know there have been similar threads, and I'm sorry that I'm raising another one. But reading to all those old topics didn't help me.
It's a friend's i9020T, bought in the US, so returning it back would be a real problem. He never unlocked bootloader, never applied any custom ROMs or Recovery, always updated it over OTA, and sometime in November, after reboots, phone started to hang on Google logo. Usually, it helped to remove the battery and wait some time, but it doesn't any more. We tried to remove it for a full day, didn't helped.
I tried going into recovery and doing full wipe and cache wipe - didn't help
I tried to unlock the bootloader, can select 'Yes', apply it via Power button, but the phone hangs.
If I want to flash anything with fastboot (boot, system img), it complains about locked bootloader
I tried Odin as well, but can't trick the phone into download mode with both volume up and down, again reports to unlock the bootloader
Is there any way to and how to fix this? I cannot transfer anything to internal memory, have stock recovery?
Thanks a lot to all of those who are willing to help, and I've really want to somehow fix the phone, because I don't have here in Serbia where to repair it. Several mobile providers only imported i9023, so they can't fix i9020T
Click to expand...
Click to collapse
First download this : http://www.4shared.com/zip/2L09-JyW/Root_Nexus_S.html
Just unpack , connect your device and click run.bat - that will root your phone and installed new ClockWordMod Recovery
After that you need : remove install-recovery.sh just in .....
run in windows-> Start->at the search bar write cmd and navigate into your android sdk is installed
For me :
C:/"Programs and Files (x86)"/Android/android-sdk/tools/>adb shell
# rm /system/etc/install-recovery.sh
#exit
or with Root Explorer into system/etc/install-recovery.sh just renam it (ex. : .sh.old)
surdu_petru said:
First download this : http://www.4shared.com/zip/2L09-JyW/Root_Nexus_S.html
Just unpack , connect your device and click run.bat - that will root your phone and installed new ClockWordMod Recovery
After that you need : remove install-recovery.sh just in .....
run in windows-> Start->at the search bar write cmd and navigate into your android sdk is installed
For me :
C:/"Programs and Files (x86)"/Android/android-sdk/tools/>adb shell
# rm /system/etc/install-recovery.sh
#exit
or with Root Explorer into system/etc/install-recovery.sh just renam it (ex. : .sh.old)
Click to expand...
Click to collapse
Same thing mate, I ran it, click two times in console, can't unlock the bootloader, I always get stuck on it
Trying to update the drivers for Nexus S : http://www.4shared.com/rar/_bgEMHqk/Nexus_S_Drivers_x86__x64.html
and after that try to run.bat...Good luck!
I'll try today, but my problem is that adb cannot find the device, fastboot can
I would try downloading the full OTA from this thread, rename it to update.zip (for easy typing), place it in a directory where you can run fastboot, then use the command:
Code:
fastboot update update.zip
I got an error
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt
Should I create android-info.txt (how?) and place it into the zip (where?)
Thanks.
<edit> I saw this topic http://forum.xda-developers.com/showthread.php?t=1131588 and followed this http://forum.xda-developers.com/showthread.php?t=884416&highlight=STOCK but that as well complains about a locked bootloader </edit>
Is the problem solved？
szk5230 said:
Is the problem solved？
Click to expand...
Click to collapse
Not so far, I'm still having trouble with the phone, and no solution so far helped
Highl1 said:
I got an error
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt
Should I create android-info.txt (how?) and place it into the zip (where?)
Thanks.
<edit> I saw this topic http://forum.xda-developers.com/showthread.php?t=1131588 and followed this http://forum.xda-developers.com/showthread.php?t=884416&highlight=STOCK but that as well complains about a locked bootloader </edit>
Click to expand...
Click to collapse
Sorry my bad, haven't tried that before either...
If it bugs you the bootloader isn't unlcoked before flashing can't you just use
fastboot oem unlock
then commence with flashing your stock image?
Edit - Nevermind...I see you tried that.
any other suggestion? I'm out of ideas
I had this problem in December. I tried everything you tried without any luck so eventually took it back for warranty repair. Unfortunately I had some water damage from 9 months before so they wouldn't touch it. Luckily I got it replaced on my phone insurance but they said it couldn't repaired.
As far as I know it's a hardware fault. With CWM it looked like I could transfer files into the sd but they would disappear! I was able to use Fastboot and Odin but no joy. I had the same errors when trying to apply update using fastboot and never found answers about the "missing" files.
Sorry to come with bad news and good luck! I'm worried it'll happen to my replacement handset so keen to know if you resolve it.
I was stupid. Point blank.
How can I get a ROM zip back on so I can flash it again?
It just hangs at the boot screen when I try to start up, but I'm able to get into TWRP recovery. Please help..I'm kinda freakin out.
Nothing showing on the internal card to be able to flash.
Trying to figure out how to maybe sideload? In ADB, the device doesn't show up...
I need baby step - by step
Vinsane said:
Trying to figure out how to maybe sideload? In ADB, the device doesn't show up...
I need baby step - by step
Click to expand...
Click to collapse
have you tried flashing the stock rom with fastboot?
crazynitro said:
have you tried flashing the stock rom with fastboot?
Click to expand...
Click to collapse
No I havent - how would i go about that?
It needs something to read to be able to flash...right now there's nothing on internal and wont mount to ADB
If I could flash via fastboot, would I be able to flash back the custom rom instead of the stock rom?
Vinsane said:
No I havent - how would i go about that?
It needs something to read to be able to flash...right now there's nothing on internal and wont mount to ADB
If I could flash via fastboot, would I be able to flash back the custom rom instead of the stock rom?
Click to expand...
Click to collapse
you dont need any anything to be able to flash. you just need a laptop with the asus drivers installed and the latest fastboot. I'm pretty sure you cant flash a custom rom with fastboot. i havent tried it myself but i wont take the risk. you could just flash the stock rom and then later intall the custom recovery and then go ahead and install the custom rom.
I think I got it. Thank GOD for the NEW TWRP recovery.
This is what I did. I poked around TWRP and noticed that I was able to change the storage location on where it looks to install. I thought...if I can load the zip to a micro SD and flash it from there..gravy.
Of course the day as it is...the SD reader on my comp stopped working..been running around the office trying to find on that did. Finally did...placed rom zip on it..rebooted into recovery..flashing right now as we speak
Praying and crossing fingers!
It freakin WORKED! I'm baaaaaack.
The only bad part is I lost my stock backup...but that's a small price to pay to have it working again.
First of all, I have been reading this forum for about two weeks and just registered in order to get some help as I do not want to break my one week old nexus 5.
From my reading, the updates can be done in quite different ways and because of that I want to be sure what I should do.
I started by:
- root the mobile with cf-auto root. It did everything for me, got the superuser icon automatically
- installed clockwork mod and I have the custom recovery. By the way, I made a backup with it but where was it written? I want to copy it to my pc.
- other than that, I have installed some root only apps like rom manager, greenify, root Explorer, etc. I supported those developers with purchase. Those guys deserve it.
Anyway, i am looking for the safe way to update to 4.4.1. I read some members saying they lost root after the update, others lost something else (I am referring to the thread on nexus 5 general forum).
Can you help me? What path shall I go? Thanks a lot.
To update you'll basically have to go back to stock in a way. By that I mean you can either flash the System.img file from the Factory Image and then update using the update files for 4.4.1 by flashing it in recovery (via Sideload) and then just root again. OR you can install an updated "Stock" 4.4.1 image from the development section and root that.
cesar.maranhao said:
- installed clockwork mod and I have the custom recovery. By the way, I made a backup with it but where was it written? I want to copy it to my pc.
Click to expand...
Click to collapse
Hi, your backups are in /mnt/shell/emulated/clockworkmod/backup/
Copy to your PC with 'adb pull /mnt/shell/emulated/clockworkmod/backup'
Cheers
shotta35 said:
To update you'll basically have to go back to stock in a way. By that I mean you can either flash the System.img file from the Factory Image and then update using the update files for 4.4.1 by flashing it in recovery (via Sideload) and then just root again. OR you can install an updated "Stock" 4.4.1 image from the development section and root that.
Click to expand...
Click to collapse
i sense i am getting somewhere but how do i do that? i am new to this and been reading a lot but the first time all seems very vague. i need a little more help from you!
lets assume i want to just apply the 4.4.1 update (maybe this is the easiest way for now). how do i do it?
also, after the update succeds, i need to root again correct? what happens to all the apps i have right now with root permissions? do they stop working until i root again and give them root privileges again? can i use the cf auto root again?
also, i am on ART, i thought of letting you know since that can cause some problems updating(??)
finistere said:
Hi, your backups are in /mnt/shell/emulated/clockworkmod/backup/
Copy to your PC with 'adb pull /mnt/shell/emulated/clockworkmod/backup'
Cheers
Click to expand...
Click to collapse
thanks!
one more thing...
can't i copy that folder like a regular folder? just copy paste?
or move that folder (with root explorer) to my dropbox folder?
cesar.maranhao said:
i sense i am getting somewhere but how do i do that? i am new to this and been reading a lot but the first time all seems very vague. i need a little more help from you!
lets assume i want to just apply the 4.4.1 update (maybe this is the easiest way for now). how do i do it?
also, after the update succeds, i need to root again correct? what happens to all the apps i have right now with root permissions? do they stop working until i root again and give them root privileges again? can i use the cf auto root again?
also, i am on ART, i thought of letting you know since that can cause some problems updating(??)
Click to expand...
Click to collapse
If you want to apply the new update it all depends on your current setup. I gave you vague options because I don't know what you've done to your phone. If you've only rooted and not changed any of the files in system then it's easy to just flash the update with the recovery. You can download the update and then start recovery (look it up). Once in recovery start ADB sideload and connect to your PC (this assumes you already have working ADB, if not.... look it up ). To sideload you just need to adb sideload filename.zip. You can probably use WugFresh's Toolkit to also sideload but I generally don't use those so dunno what they do these days. Much easier to learn and understand what it does then do it yourself.
If you have a custom recovery you might just be able to flash the update with the recovery like you normally flash any zip in recovery.
cesar.maranhao said:
thanks!
one more thing...
can't i copy that folder like a regular folder? just copy paste?
or move that folder (with root explorer) to my dropbox folder?
Click to expand...
Click to collapse
You can just copy it, no need to use ADB but this is why it's good to know how to use ADB.
shotta35 said:
If you want to apply the new update it all depends on your current setup. I gave you vague options because I don't know what you've done to your phone. If you've only rooted and not changed any of the files in system then it's easy to just flash the update with the recovery. You can download the update and then start recovery (look it up). Once in recovery start ADB sideload and connect to your PC (this assumes you already have working ADB, if not.... look it up ). To sideload you just need to adb sideload filename.zip. You can probably use WugFresh's Toolkit to also sideload but I generally don't use those so dunno what they do these days. Much easier to learn and understand what it does then do it yourself.
If you have a custom recovery you might just be able to flash the update with the recovery like you normally flash any zip in recovery.
You can just copy it, no need to use ADB but this is why it's good to know how to use ADB.
Click to expand...
Click to collapse
thanks for the reply. i am reading on the adb sideload right now... i already have the update zip inside the platform tools. however, in the command prompt, it says my device is unauthorized (i have both the usb debugging and unknown sources ticked). the nexus 5 is connected as MTP.
any clues?
about what i have done to my nexus, i applied the cf autoroot, installed clockwork mod... nothing much besides some play store apps..
as for this paragraph:
"If you have a custom recovery you might just be able to flash the update with the recovery like you normally flash any zip in recovery. "
i have never done it, hence all these questions!
cesar.maranhao said:
thanks for the reply. i am reading on the adb sideload right now... i already have the update zip inside the platform tools. however, in the command prompt, it says my device is unauthorized (i have both the usb debugging and unknown sources ticked). the nexus 5 is connected as MTP.
any clues?
about what i have done to my nexus, i applied the cf autoroot, installed clockwork mod... nothing much besides some play store apps..
as for this paragraph:
"If you have a custom recovery you might just be able to flash the update with the recovery like you normally flash any zip in recovery. "
i have never done it, hence all these questions!
Click to expand...
Click to collapse
You do it from Recovery. So just copy the file to the phone in some folder. You can't update the phone with it running. So reboot to CWM and then choose Install from ZIP then find the file on your storage and then choose update. That may or may not work as I said depending.
-----------------
Plenty of these questions around... check them out first.
http://forum.xda-developers.com/showthread.php?t=2561198
http://forum.xda-developers.com/showthread.php?p=47369234
http://forum.xda-developers.com/showthread.php?t=2561076
shotta35 said:
If you want to apply the new update it all depends on your current setup. I gave you vague options because I don't know what you've done to your phone. If you've only rooted and not changed any of the files in system then it's easy to just flash the update with the recovery. You can download the update and then start recovery (look it up). Once in recovery start ADB sideload and connect to your PC (this assumes you already have working ADB, if not.... look it up ). To sideload you just need to adb sideload filename.zip. You can probably use WugFresh's Toolkit to also sideload but I generally don't use those so dunno what they do these days. Much easier to learn and understand what it does then do it yourself.
If you have a custom recovery you might just be able to flash the update with the recovery like you normally flash any zip in recovery.
You can just copy it, no need to use ADB but this is why it's good to know how to use ADB.
Click to expand...
Click to collapse
cesar.maranhao said:
thanks for the reply. i am reading on the adb sideload right now... i already have the update zip inside the platform tools. however, in the command prompt, it says my device is unauthorized (i have both the usb debugging and unknown sources ticked). the nexus 5 is connected as MTP.
any clues?
about what i have done to my nexus, i applied the cf autoroot, installed clockwork mod... nothing much besides some play store apps..
as for this paragraph:
"If you have a custom recovery you might just be able to flash the update with the recovery like you normally flash any zip in recovery. "
i have never done it, hence all these questions!
Click to expand...
Click to collapse
shotta35 said:
You do it from Recovery. So just copy the file to the phone in some folder. You can't update the phone with it running. So reboot to CWM and then choose Install from ZIP then find the file on your storage and then choose update. That may or may not work as I said depending.
-----------------
Plenty of these questions around... check them out first.
http://forum.xda-developers.com/showthread.php?t=2561198
http://forum.xda-developers.com/showthread.php?p=47369234
http://forum.xda-developers.com/showthread.php?t=2561076
Click to expand...
Click to collapse
yes, i have been reading those topics and many others.. i managed to solve the adb device unauthorized anyway. just flashed the 4.4.1 zip file under clockwork mod recover.. android is upgrading at the moment. lets see if everything is work as it should.
No need to sideload adb bla bla..
copy the OTA zip into the phone, and just flash it in CWM (install file from internal storage).. 1 minute and done.
You'll get error status 7 at checking if you changed something in system (apart from rooting), else you shouldn't have any problem.
RusherDude said:
No need to sideload adb bla bla..
copy the OTA zip into the phone, and just flash it in CWM.. 1 minute and done.
You'll get error status 7 at checking if you changed something in system (apart from rooting), else you shouldn't have any problem.
Click to expand...
Click to collapse
yes, everything is fine. 4.4.1 loaded fine without any errors. i have root checker and when i tested, it says i do not have proper root access. i also lost my clockwork mod recovery.
i am now checking into it to see what needs to be done to gain root access again and get the custom recovery as it was before the update.
cesar.maranhao said:
yes, everything is fine. 4.4.1 loaded fine without any errors. i have root checker and when i tested, it says i do not have proper root access. i also lost my clockwork mod recovery.
i am now checking into it to see what needs to be done to gain root access again and get the custom recovery as it was before the update.
Click to expand...
Click to collapse
You need to flash the recovery again via fastboot (youll lose it every time, unless you flash the flashable recovery ZIP just after flashing the OTA and before rebooting the phone).You'll have this problem every OTA unless you flash the zipped version everytime.
I'd recommend the easy way to root, get the SuperSU binaries and flash them through the custom recovery and you're done..
RusherDude said:
No need to sideload adb bla bla..
copy the OTA zip into the phone, and just flash it in CWM (install file from internal storage).. 1 minute and done.
You'll get error status 7 at checking if you changed something in system (apart from rooting), else you shouldn't have any problem.
Click to expand...
Click to collapse
RusherDude said:
You need to flash the recovery again via fastboot (youll lose it every time, unless you flash the flashable recovery ZIP just after flashing the OTA and before rebooting the phone).You'll have this problem every OTA unless you flash the zipped version everytime.
I'd recommend the easy way to root, get the SuperSU binaries and flash them through the custom recovery and you're done..
Click to expand...
Click to collapse
i see. things are starting to make sense for me.
before reading you post, i tried to get the clockwork mod recovery through the Rom Manager App. it failed. i am now looking for those files you mentioned.
EDIT: i am at the clockworkmod recovery website... is the file i want an IMG?
cesar.maranhao said:
i see. things are starting to make sense for me.
before reading you post, i tried to get the clockwork mod recovery through the Rom Manager App. it failed. i am now looking for those files you mentioned.
EDIT: i am at the clockworkmod recovery website... is the file i want an IMG?
Click to expand...
Click to collapse
You'd only be looking for the supersu binaries, since you already have the recovery IMG from te previous time, right? (the one that you need for fastboot).
EDIT: Yes, IMG files are for fastboot, ZIP files for recovery.
RusherDude said:
You'd only be looking for the supersu binaries, since you already have the recovery IMG from te previous time, right? (the one that you need for fastboot).
EDIT: Yes, IMG files are for fastboot, ZIP files for recovery.
Click to expand...
Click to collapse
but how do i install it? when i go into recovery it only gives me 4 options:
reboot system now
apply update from adb
wipe cache/factory reset
wipe cache partition
i am lost
cesar.maranhao said:
but how do i install it? when i go into recovery it only gives me 4 options:
reboot system now
apply update from adb
wipe cache/factory reset
wipe cache partition
i am lost
Click to expand...
Click to collapse
That's the stock recovery, you can't do nothing from there.
You need to flash the recovery via fastboot (didn't you do that the first time to get your custom recovery..?)
Check this tutorial mate: http://forum.xda-developers.com/showthread.php?t=2507905
RusherDude said:
You'd only be looking for the supersu binaries, since you already have the recovery IMG from te previous time, right? (the one that you need for fastboot).
EDIT: Yes, IMG files are for fastboot, ZIP files for recovery.
Click to expand...
Click to collapse
RusherDude said:
That's the stock recovery, you can't do nothing from there.
You need to flash the recovery via fastboot (didn't you do that the first time to get your custom recovery..?)
Check this tutorial mate: http://forum.xda-developers.com/showthread.php?t=2507905
Click to expand...
Click to collapse
no, i got the custom recovery when i installed clockworkmod recovery from the play store. i am now reading the thread you linked me! thanks!
cesar.maranhao said:
no, i got the custom recovery when i installed clockworkmod recovery from the play store. i am now reading the thread you linked me! thanks!
Click to expand...
Click to collapse
done it! i now have root again and the clockworkmod custom recovery! nice!
:good:
RusherDude said:
You need to flash the recovery again via fastboot (youll lose it every time, unless you flash the flashable recovery ZIP just after flashing the OTA and before rebooting the phone).You'll have this problem every OTA unless you flash the zipped version everytime.
I'd recommend the easy way to root, get the SuperSU binaries and flash them through the custom recovery and you're done..
Click to expand...
Click to collapse
from where can i get the flashable clokwork mod recovery zip file?
i am going to apply the 4.4.2 update now and will be doing it this way:
from the recovery apply the 4.4.2 zip. after this apply the supersu zip. i want to install the custom recovery zip too so when the phone restarts everything will be configured. is this possible?
RusherDude said:
You need to flash the recovery again via fastboot (youll lose it every time, unless you flash the flashable recovery ZIP just after flashing the OTA and before rebooting the phone).You'll have this problem every OTA unless you flash the zipped version everytime.
I'd recommend the easy way to root, get the SuperSU binaries and flash them through the custom recovery and you're done..
Click to expand...
Click to collapse
well, it seems i haven't lost my custom recovery. was it because i installed the supersu before rebooting?
I tried to install the new update but on the install screen it says failed to verify and asks if i want to install anyways.
I choose yes and it errors out saying the update is for device "roth" and i have device "thor"
Does ayone know a workaround for this?
Have you messed with any system files or changed out the recovery or anything like that? I assume the Shield is going to look to make sure the system is all intact before allowing the update. Though the fact it says Roth which is a spelling error of Thor seems weird. Mine updated fine...
If you can find the update using root explorer you could delete it and redownload it.
I unlocked bootloader, installed cwm, and rooted using Kwonggers toolkit.
Sent from my XT1053 using Tapatalk
csos95 said:
I unlocked bootloader, installed cwm, and rooted using Kwonggers toolkit.
Sent from my XT1053 using Tapatalk
Click to expand...
Click to collapse
OTAs will commonly fail if you install custom recovery. You'll have to wait for someone to make it into a zip that you can run through CWM.
csos95 said:
I unlocked bootloader, installed cwm, and rooted using Kwonggers toolkit.
Sent from my XT1053 using Tapatalk
Click to expand...
Click to collapse
You probably still have CWM installed, to install an OTA you must first go back to the stock recovery. You can download it from here: http://goo.im/devs/agrabren/shield/original_images/recovery.img
Put that file in your ADB folder
To flash it, connect to usb and enable ADB debugging.
on PC type:
adb reboot bootloader
-Wait to reboot-
fastboot flash recovery recovery.img
-Now you have stock recovery installed-
Reboot the shield normally and install the OTA update, it should work.
Your bootloader is still unlocked, but you don't have root.
To install CWM, just follow the same instructions but replace the stock image with the CWM recovery image. You can download that here: http://goo.im/devs/agrabren/shield/cwm/recovery.img
The shield will be unrooted when you update. To root, simply flash CWM and reboot. CWM will ask you if you want to disable Stock reflashing, and if you want to root.
You may also need to flash the real SU zip from here: http://download.chainfire.eu/396/SuperSU/UPDATE-SuperSU-v1.94.zip?retrieve_file=1
For me, I was not able to let the SU app install the binary's alone, (Normal, or CWM method) I had to flash the SU zip.
But the update is smooth, and everything is working. Just no SD write support obviously.
CDeviant said:
You probably still have CWM installed, to install an OTA you must first go back to the stock recovery. You can download it from here: http://goo.im/devs/agrabren/shield/original_images/recovery.img
Put that file in your ADB folder
To flash it, connect to usb and enable ADB debugging.
on PC type:
adb reboot bootloader
-Wait to reboot-
fastboot flash recovery recovery.img
-Now you have stock recovery installed-
Reboot the shield normally and install the OTA update, it should work.
Your bootloader is still unlocked, but you don't have root.
To install CWM, just follow the same instructions but replace the stock image with the CWM recovery image. You can download that here: http://goo.im/devs/agrabren/shield/cwm/recovery.img
The shield will be unrooted when you update. To root, simply flash CWM and reboot. CWM will ask you if you want to disable Stock reflashing, and if you want to root.
You may also need to flash the real SU zip from here: http://download.chainfire.eu/396/SuperSU/UPDATE-SuperSU-v1.94.zip?retrieve_file=1
For me, I was not able to let the SU app install the binary's alone, (Normal, or CWM method) I had to flash the SU zip.
But the update is smooth, and everything is working. Just no SD write support obviously.
Click to expand...
Click to collapse
I tried this but it wouldn't download the ota again an I couldn't find where it was. So, I tried going back to stock to update but now it is stuck on the boot screen. I tried downloading a newer factory image from the nvidia website but now all of the windows links are locked behind some developer program that I have to make an account, submit an application, and wait for approval. Do you have any links to a recent factory restore image?
EDIT: I ended up just downloading mint and the linux .sh file to get the factory images.
You can use the root toolbox on this forum to reflash stock and relock and fix it
eric4shay said:
You can use the root toolbox on this forum to reflash stock and relock and fix it
Click to expand...
Click to collapse
That's what I tried before but it didn't work
If some updates please capture the OTA zip that downloads and upload it for us to tear apart.
What steps are you doing on there also email me [email protected] I will be able to respond more quickly
you dont have to
you can just use kwonggers toolkit, and just revert to stock kernel, stock system image, and stock recovery, you don't need to relock bootloader, but you must download the ota's separately, if you don't automatically see them under about shield> updates, then go to application manager>all> and force stop google services framework, then check for the update(it should now show up and download). this is what I have been doing, everytime I want to revert to the stock, most up to date ota, after this, you can reflash cwm recovery, flash the super su.zip and root again!
The ota (for some back assward reason) downloads not to the ota folder but to the cache folder. Anyway uploading the full otq zip now will edit with link when its done
Sent from my SHIELD using Tapatalk
Mechcondrid said:
The ota (for some back assward reason) downloads not to the ota folder but to the cache folder. Anyway uploading the full otq zip now will edit with link when its done
Sent from my SHIELD using Tapatalk
Click to expand...
Click to collapse
That could be more than one reason. But off the top of my head, maybe it's because the OTA folder is userspace, and there might not be enough Storage left on the internal. Cache is a separate partition, Things can even be deleted while running. So basically it insures enough space to download, and the user would never need to delete his own data to make room.
It might be awkward when you're looking for the OTA, but I think it's designed that way with the user in mind. :good:
Well regardless here's the ota file https://drive.google.com/file/d/0B2khjpo7TDP0Y3c0SjNNRWNXT28/edit?usp=sharing
Sent from my SCH-I545 using Tapatalk
Hello,
So I just discovered this while trying to flash the 5.0.1 OTA from 5.0. I'm rooted on LRX21O via the Nexus Root Toolkit 1.9.9 (which is what I've always used in the past with no issues).
1 Tried flashing the OTA via Google notification push. It reboot, and no changes occur.
2 Fine - I try to use the Root Toolkit again. Boots into bootloader, appears to flash the radio and other necessary components. Reboots - no changes occur.
3 I then tried to just download the 5.0.1 package and flash everything manually via adb. Everything appears to go smoothly, and upon bootup Android updates all of its apps - still nothing. I appear to be completely stuck on LRX21O without any way to reflash stock or OTA's.
Anyone have any clue why this is occurring or have heard of such an issue before?
Thanks all.
Just flash factory images. With fastboot/flash-all script.
https://developers.google.com/android/nexus/images
You flash these in fastboot not adb
Sent from my Nexus 5 using Tapatalk
Did you not understand? I did flash in boot loader USING adb on my computer. All that bat script does is just automate the flashing of each image for you (system, radio, etc) so this is not helpful. I know how to flash, but flashing seems to have no effect despite successfully flashing via manually installing or just using the script
Sane116 said:
Did you not understand? I did flash in boot loader USING adb on my computer.
Click to expand...
Click to collapse
You use fastboot in bootloader, not adb.
I'm not the one asking for help. Anyways, carry on.
Your device's /system partition is tampered (you say you rooted it) and thus the OTA fails. Flash the 5.0 factory image (LRX21O) WITHOUT rooting/flashing kernels/whatever and then use the OTA zip to do adb sideload in the stock recovery to update to 5.0.1 LRX22C.
Manually use fastboot commands to flash system.img and boot.img of the full 5.0.1 factory image (not script). post the output please
I'm not the one asking for help. Anyways, carry on.
Click to expand...
Click to collapse
Sorry about that - didn't mean to come across snippy
It worked this time with fastboot. For future reference can this be done the same way with the OTA update zip instead of reflashing the entire image?
Sane116 said:
Sorry about that - didn't mean to come across snippy
It worked this time with fastboot. For future reference can this be done the same way with the OTA update zip instead of reflashing the entire image?
Click to expand...
Click to collapse
No, but if your phone is setup correctly you can sideload the ota zip in the stock recovery
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
No, but if your phone is setup correctly you can sideload the ota zip in the stock recovery
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
Would you mind explaining this? I've used sideload in cwm and twrp before but I'm unsure of how to operate anything within stock recovery. adb won't even connect while in recovery. I would like to just remain on unrooted stock until xposed eventually get's developed for ART and flash zips that way.
Sane116 said:
Would you mind explaining this? I've used sideload in cwm and twrp before but I'm unsure of how to operate anything within stock recovery. adb won't even connect while in recovery. I would like to just remain on unrooted stock until xposed eventually get's developed for ART and flash zips that way.
Click to expand...
Click to collapse
Sideloading in the stock recovery works much the same as in a custom recovery. Boot into the stock recovery and there is an option to sideload. Then on your pc in a command window you type adb sideload update.zip. or whatever the file name is that you're trying to sideload. Obviously, if you can't get adb to recognize your device that's a problem. But that's a separate driver issue.
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
Sideloading in the stock recovery works much the same as in a custom recovery. Boot into the stock recovery and there is an option to sideload. Then on your pc in a command window you type adb sideload update.zip. or whatever the file name is that you're trying to sideload. Obviously, if you can't get adb to recognize your device that's a problem. But that's a separate driver issue.
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
How can this be possible though without a custom recovery with the sideload feature? Stock recovery is essentially unusable as it just displays a picture of a dead android on a black screen.
Perhaps we're on different pages, or am I just confused still?
sideloading an OTA update from stock recovery
Hello, to make it work you will need to use the Google USB drivers you downloaded when you go into stock recovery then press the power button and volume up once then you will see a menu option with the "install update from adb option select this and plug in your phone to the computer. After this is done you will need to go to device manager and install the USB drivers from the Google USB drivers you downloaded. at this point after that is done you then go into the folder that has ADB installed and use adb sideload filename.zip
at this point your phone will accept the ota update package and you wont lose any data, I hope this helps..
-cs
Sane116 said:
How can this be possible though without a custom recovery with the sideload feature? Stock recovery is essentially unusable as it just displays a picture of a dead android on a black screen.
Perhaps we're on different pages, or am I just confused still?
Click to expand...
Click to collapse
When you get the dead android you need to press vol up and then press and release power. That'll get you into the stock recovery. It's stupid and I don't know why they made it that way
Sent from my Nexus 9 using XDA Free mobile app
thanks all, can't believe i never knew that volumeup+power got me into stock recovery options.
new issue: sideload works all well and perfect, but how can I bypass the "signature verification failed" flag that kicks me from the zip install every time?
Sane116 said:
thanks all, can't believe i never knew that volumeup+power got me into stock recovery options.
new issue: sideload works all well and perfect, but how can I bypass the "signature verification failed" flag that kicks me from the zip install every time?
Click to expand...
Click to collapse
Well you can't. The limitation of the stock recovery is you can only flash files signed by Google. That's why you need a custom recovery to flash most files
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
Well you can't. The limitation of the stock recovery is you can only flash files signed by Google. That's why you need a custom recovery to flash most files
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
So can I just flash twrp with fastboot and go about that method? I believe it can bypass the signature. I am unlocked without root currently.
Sane116 said:
So can I just flash twrp with fastboot and go about that method? I believe it can bypass the signature. I am unlocked without root currently.
Click to expand...
Click to collapse
If you're trying to flash the update.zip to 5.0.1 you need to do that in the stock recovery. It will not work in twrp or cwm. I'm not sure what you're trying to do right now
Sent from my Nexus 9 using XDA Free mobile app
my apologies.
so originally i wanted to just flash the OTA. ended up performing a fresh install and un-rooted. but there's a few unsigned zips i like to have installed.
So I think I'm going to re-root, flash twrp, install my zips, and leave it at that. i'll just flash stock recovery whenever I need the OTA which should be quick now that I know what to do.
hope that sounds correct. thanks for all the help!