Related
I've got ClockworkMod on my Nexus S, but as I might be returning it, I'd like to also throw the stock Recovery on. I know Best Buy probably doesn't even know how to check so I'm not terribly worried, but I can't find the fastboot img anywhere. Is this because the AOSP isn't out for 2.3 yet?
Once CWM has been flashed, there is no "old" install-recovery.sh file anymnore, right? Thanks.
allen099 said:
I've got ClockworkMod on my Nexus S, but as I might be returning it, I'd like to also throw the stock Recovery on. I know Best Buy probably doesn't even know how to check so I'm not terribly worried, but I can't find the fastboot img anywhere. Is this because the AOSP isn't out for 2.3 yet?
Once CWM has been flashed, there is no "old" install-recovery.sh file anymnore, right? Thanks.
Click to expand...
Click to collapse
No, that shouldn't be correct on a stock rom.
CW does not delete that file, that's why so many people come here complaining that CW disappears after rebooting.
If you haven't messed with that file, and you're on stock, you should be able to just reboot and find yourself in stock recovery. If you did mess with it by renaming it, just rename it back to normal and reboot.
distortedloop said:
No, that shouldn't be correct on a stock rom.
CW does not delete that file, that's why so many people come here complaining that CW disappears after rebooting.
If you haven't messed with that file, and you're on stock, you should be able to just reboot and find yourself in stock recovery. If you did mess with it by renaming it, just rename it back to normal and reboot.
Click to expand...
Click to collapse
My apologies. I forgot to mention that I'm on CM7 right now, but I have a nandroid backup of the stock ROM. So in that case, I should go back to the stock and then do all of this install-recovery.sh magic?
allen099 said:
My apologies. I forgot to mention that I'm on CM7 right now, but I have a nandroid backup of the stock ROM. So in that case, I should go back to the stock and then do all of this install-recovery.sh magic?
Click to expand...
Click to collapse
Yes, that should get you going. You're going to want to return to stock to refund the phone anyways, right? I mean if you're worried about them checking for a custom recovery, they're more likely to check for a custom rom (and an unlocked bootloader, by the way).
If I were returning my phone, I would flash back to stock rom, then let the stock recovery restore, then do the fastboot oem lock, then fastboot oem unlock, then fastboot oem lock again. The purpse of the 3 fastboot oem steps is to ensure that your phone is 100% wiped of all personal data and files, including the sdcard, and then to relock the bootloader, which is the first obvious sign on boot (the unlocked padlock) that you've messed around with the operating system.
i tried to update via phone (after the notification), but after green bar was full, my phone rebooted and stuck in white screen with htc logo... if i try to enter in recovery i see this
h*tp://i39.tinypic.com/xdxnc5.jpg
it seems to be s-off (i bought it used) ...what have i to do for make it work again??
tnx.. and sorry for my bad english
same problem here, help is needed!
A golden rule: never update OTA on a modified device (custom ROM even modified Stock one, custom Recovery, Revolutionary hboot!, etc.)
How to fix:
do not pull battery!
flash a custom recovery (e.g. 4EXT) with the fastboot command (search for a how-to)
reboot to recovery, wipe all partitions and install custom ROM
Ok, to late with the battery, have already pulled that one out!
I also have S-Off on my phone, really dont understand the how to fix a recovery??
And is it really neccessary to flash a new ROM for this?
An official release that screwes the phones up?
I think the general issue is that an 'Official' OTA upgrade should not screw up your phone - enough testing by HTC should make sure of that.
Hoever, if you have modified your phone (e.g. by rooting it, installing custom recovery etc) then you can not expect to blame HTC when their upgrade doesn't work as expected. They can't be held responsible for problems caused by modifications you make to the phone.
But all I have done is S-Off, I have not installed another ROM or anything else?
So the update should work I really think!
Can I install a custom recovery without have to be able to start the phone?
Akerhage said:
But all I have done is S-Off, I have not installed another ROM or anything else?
So the update should work I really think!
Can I install a custom recovery without have to be able to start the phone?
Click to expand...
Click to collapse
The OTA flashes a new hboot also.
If you S-OFFed with Revolutionary your hboot has to be version 6.98.000x. This hboot has a protection and cannot be overwritten. This is the point where the update process is interrupted. The result is a bootloop, because the new system is incomplete.
If you can boot to bootloader (hboot) you should be able to flash a custom recovery with the fastboot command (in the 4EXT Recovery thread there is an attachement - a zip file that contains recovery.img). Extract the archive and flash it with this command from cmd (there is a guide how to make fastboot working in my signature):
Code:
fastboot flash recovery {path to file on your PC}/recovery.img
If this works reboot to recovery, wipe all partitions and flash a custom ROM. Then your phone should be working again.
Then if you want the OTA flash a 0.98.2000 hboot, then use the 1.47.401.4 RUU (if you are using European unbranded) or the corresponding for your brand/region to return back to complete Stock and S-ON. Then you will be prompted to update and you will have the latest OTA on your device
Okay, I have now fixed the 4EXT Recovery and it is working!
Do I have to put a new ROM on the SD-card or is there another way to install a ROM (from cmd with the ROM on the computer etc?)
I dont have an adapter to the SD-card, but maybe I can put the ROM on the sdcard with a command in cmd aswell?
What ROM do you recommend to use? (sense, no sense doesnt matter)
Edit: I did a backup as well, thinking that I should do that...
Can you link to zip file you used for recovery i have exactly same issue and same software versions as you have.
@ Mooler. First of follow the guide that was posted here regarding the adb-drivers.
After that download this: http://forum.xda-developers.com/attachment.php?attachmentid=631186&d=1308596026
Then install that one as described with the cmd-command.
After that just put a custom ROM or a shipped ROM on the SD-card, wipe data/cache and install the ROM you want. That solved the problem for me!
Good Luck and thanks for the help I got here! Xda always delivers
Damn this phone! After hours of fixing with this problem!
I managed great, installed new kernels, radios, ROMs etc. And the first thing I did was to drop it on the floor so the whole damn display cracked!
Thanks for both of you.
I managed to restore the phone quickly after i got the correct recovery file. 30 mins and custom ROM was up and running. Good bye official update.
Akerhage: sad to here, it really was hours of reading and trying before you get it right.
Hi people,
I have a bit of a problem here
Recently updated my Nexus S i9020t (unlocked uk version) to 4.0.3, all done no hassle and working fine.
Then I rooted the device following the instructions on nexushacks .com, including flashing TWRP recovery and superuser.
Again, all fine no hassle.
HOWEVER now, whenever I try to boot into recovery, i see a belly up android with a big exclamation mark
Any ideas as to how to fix this, ie re-install stock recovery?
Much appreciated in advance,
All the best
if you still have root just download rom manager and install recovery from there.
Sent from my Nexus S using XDA App
Hi Camalus,
I already tried installing clockworkmod recovery from rom manager, unfortunately the issue persists (same deal, android belly up with exclamation)
Is Root working? You can test this by using terminal emulator and typing in "su".
If it is, rename /etc/install-recovery.sh to something else (ie. /etc/install-recovery.sh.bak). This will stop stock recovery installing each boot. After this, flashing CWM or TWRP again will keep it there.
Job Done
Hi Harbb,
Thanks an absolute million, I did as you suggested and then flashed an old version of CWM recovery.
Result: SUCCESS!
Awesome job done, nice one bro
Flash the new one, save you trouble down the track. Also remember to rename that file i said so stock doesn't replace recovery
And of course you're welcome.
Hi Harbb,
Can I flash the new version of CWM recovery through ROM manager, or would it be advisable to do it manually, with fastboot (as I did successfully just now)?
Also, I have renamed install-recovery.sh to install-recovery.sh.bak just as you suggested.
Are there any other files I need to rename in order to ensure recovery works as it's supposed to, or should that be ok now?
Once again, thanks for your help
That's all you need to rename. I'd generally just advise wiping/flashing manually, ROM Manager should be fine for recovery since it doesn't actually reboot into recovery and execute commands.
I am on stock 4.0.4 with a locked bootloader. I want to have root with the stock rom, nothing else just root.
So I am gonna use the tool provided here,
http://forum.xda-developers.com/showthread.php?t=1544940
I have already installed drivers and have the tool downloaded.
Then I would like to flash the stock google 4.0.4 rom that will let me receive OTA updates. Is this the right file?
http://forum.xda-developers.com/showthread.php?t=1569509
Or can I just flash the stock rom from here?
http://forum.xda-developers.com/showthread.php?t=1572307
I heard there are problems flashing stock rom with CWR if the stock recovery isnt removed? Thats why I dont know if I should flash the stock image.
Is the process of flashing rom with CWR recovery the same as with stock recovery?
My phone is the i9023.
Thanks a bunch in advance.
Gambler_3 said:
I am on stock 4.0.4 with a locked bootloader. I want to have root with the stock rom, nothing else just root.
So I am gonna use the tool provided here,
http://forum.xda-developers.com/showthread.php?t=1544940
I have already installed drivers and have the tool downloaded.
Then I would like to flash the stock google 4.0.4 rom that will let me receive OTA updates. Is this the right file?
http://forum.xda-developers.com/showthread.php?t=1569509
Or can I just flash the stock rom from here?
http://forum.xda-developers.com/showthread.php?t=1572307
Is the process of flashing rom with CWM recovery the same as with stock recovery?
Thanks in advance.
Click to expand...
Click to collapse
Baseband version? under about phone
billchen0014 said:
baseband version? Under about phone
Click to expand...
Click to collapse
i9023xxki1.
Sorry should have specified my phone in the OP.
Best way is to do it manually. You can find all of the steps required here. The only difference is that you should be flashing the latest recovery from here and the latest superuser.zip file when flashing with recovery.
Note, unlocking bootloader will cause loss of EVERYTHING on the device that you have put on there (sdcard, apps, data partition, etc).
Harbb said:
Best way is to do it manually. You can find all of the steps required here. The only difference is that you should be flashing the latest recovery from here and the latest superuser.zip file when flashing with recovery.
Note, unlocking bootloader will cause loss of EVERYTHING on the device that you have put on there (sdcard, apps, data partition, etc).
Click to expand...
Click to collapse
You suppose thats better to do manually so I will have latest version of recovery and superuser?
And yes I am aware of the data loss waited sometime to finish all my games now I am ready to lose all my app data.
Harbb said:
Best way is to do it manually. You can find all of the steps required here. The only difference is that you should be flashing the latest recovery from here and the latest superuser.zip file when flashing with recovery.
Note, unlocking bootloader will cause loss of EVERYTHING on the device that you have put on there (sdcard, apps, data partition, etc).
Click to expand...
Click to collapse
Do it this way. The one click is fine but using Android SDK and going through all that will help you in the long run. This way you know the process in case something goes wrong. It may be confusing at first but worth it. It will teach you a lot more than flashing a one click!
I learnt a lot from this and feel much more experienced and capable because of it. I know I will be able to solve any major issues using Android Debug Bridge (adb).
Okay then I am gonna try the manual way and gonna take out time for it. Now I just need to know what do I flash once I have unlocked bootloader and installed CWR?
I just want the stock google rom and receive OTA if nexus S continues to be supported by google.
You won't need to reinstall the ROM if you are currently on 4.0.4. The ROM stays there as-is. Feel free to do your wipes in recovery and reflash stock 4.0.4 through CWM if you must. You flash CWM to your phone and then superuser through CWM.
Steps:
Setup ADB/fastboot
Bootloader --> fastboot oem unlock --> agree
Bootloader --> fastboot flash recovery recovery.img --> this will give you CWM
Recovery --> flash superuser.zip and, if you must, wipe and reflash ICS (flash su AFTER this if done)
Reboot --> bingo
Also note, with stock ROMs it will replace your current recovery with stock recovery on each boot. If you want to keep CWM, delete /system/etc/flash-recovery.sh when you first boot. You'll have to reflash recovery afterward and it will stick.
Oh I was of the impression that unlocking bootloader wipes everything means it wipes the OS as well. That is nice if it's just data and not the OS, dont think I would reflash it if it's not needed.
Can you explain what you mean by will have to reflash recovery? I will have to do that even if I delete that file on first boot? And whats the drawback if I dont delete that file and stick with stock recovery?
As soon as you boot into stock android it will replace the recovery. So if that file is there on first boot, it will replace it while booting and you will be without CWM (stock instead). After first boot you can delete the file (you can reflash a ROM which has this deleted, or delete it yourself from a stock ROM, or even use adb or a recovery-based file manager to delete the file, then you won't have this problem at all) and it will no longer reflash stock recovery, but you would already have the stock one and need to flash CWM one more time to get it to stick. Easiest way is to just flash CWM and delete it within android imo, saves mounting commands and the such.
No downside really. If you need to flash something for one reason or another you'll just have to reflash CWM before you do so. Once rooted, ROM Manager can do this for you within android anyway.
I had already downloaded and installed the drivers from the one click root thread and my computer shows the android adb thing when I connect my phone with USB debugging.
But as you guys suggested I am gonna do the manual way. So do I just skip the installing driver on computer in the part 1 of this guide?
http://forum.xda-developers.com/showthread.php?t=1007782
In my bootloader menu why is it showing my phone as an i9020?? Is it normal?
Gambler_3 said:
In my bootloader menu why is it showing my phone as an i9020?? Is it normal?
Click to expand...
Click to collapse
Because you have a Nexus S with amoled. That's the i9020. The i9023 is SLCD.
DeuXGod said:
Because you have a Nexus S with amoled. That's the i9020. The i9023 is SLCD.
Click to expand...
Click to collapse
He has the i9023 to my knowledge. It is completely normal, though. Bootloader and recovery for i9020 and i9023 series are the same, this can be attributed to the issue with 4.0.3 recovery backlight not turning on.
If fastboot recognises your phone in the bootloader (the fastboot menu), your drivers are installed an working perfectly.
Finally got to the unlock bootloader screen, didnt do it just yet but now I know how to do it.
I must say the guide is a bit outdated, the software has changed quite a bit seems. The most frustrating part was that the fastboot file is actually in the platform tools folder instead of the tools folder which I didnt figure for a while. I will hold off rooting when I have a whole day off because once I lose everything I would be very anxious to get my phone back to normal which will take time.
Thanks for the help harbb, if I have any problem flashing recovery and superuser I will come back for more help.
And yes I have the LCD version i9023.
Btw the guide said the fastboot will be in the tools folder but the tools folder had a read me that "adb has moved to the platform tools folder" this is how I figured to go to that folder and thats where the fastboot file actually was.
Now it says I should put the recovery image in the tools folder so should I do that or put it in the platform tools folder?
In the instructions for the flashing recovery I am not understanding one thing.
6 - Then back on the SNS select Power Off (Reboot also works)
Part 4 - Root
1 - Power ON the SNS
So after flashing recovery I have to reboot? Since I am on stock rom that would bring back the stock recovery so how would I flash superuser then?
If I delete the stock recovery can I still get OTA updates?
fastboot and adb is now in platform tools, that is correct. Easiest way is to put your recovery in there too so you don't have to type in the absolute file path to it, don't put it in tools.
Don't power off or reboot the phone. After you flash recovery go straight into the recovery menu and root, flash custom ROMs, kernels, etc. You can transfer files to flash via the mounts and storage --> mount usb storage menu. After this feel free to reboot.
Harbb said:
fastboot and adb is now in platform tools, that is correct. Easiest way is to put your recovery in there too so you don't have to type in the absolute file path to it, don't put it in tools.
Don't power off or reboot the phone. After you flash recovery go straight into the recovery menu and root, flash custom ROMs, kernels, etc. You can transfer files to flash via the mounts and storage --> mount usb storage menu. After this feel free to reboot.
Click to expand...
Click to collapse
Just wanted to update that I successfully unlocked and rooted. Thanks a bunch mate.
Gambler_3 said:
Just wanted to update that I successfully unlocked and rooted. Thanks a bunch mate.
Click to expand...
Click to collapse
Good work, been wandering what you were up to on this
Hope you enjoy the possibilities.
I'm thinking about unlocking my bootloader (well I will eventually, it just depends on how long I can last without root), but I've forgotten, is it still possible to take OTA's after you unlock your bootloader?
Thanks
Probably not.
Why shouldn't he be able to. Up until now the last four HTC devices M7, M8, M9, and 10 all received OTA updates even though the bootloader has been unlocked. There's just one new thing which startet with the change to Block-Based-OTA updates. An OTA won't install as soon as you change anything on the system partition (meaning that even mounting r/w in TWRP causes this!), due to a change in its md5 checksum.
5m4r7ph0n36uru said:
Why shouldn't he be able to. Up until now the last four HTC devices M7, M8, M9, and 10 all received OTA updates even though the bootloader has been unlocked. There's just one new thing which startet with the change to Block-Based-OTA updates. An OTA won't install as soon as you change anything on the system partition (meaning that even mounting r/w in TWRP causes this!), due to a change in its md5 checksum.
Click to expand...
Click to collapse
Wait, so if I flash magisk, I won't be able to take OTA?
Dang. If I just flash the stock recovery, will everything work, or will I have to restore to stock and take the OTA, then re-root?
When you unlock, then flash TWRP, first thing you do is Keep System Read Only. Then make a backup of System Image, boot image. When its time for OTA. restore system image, boot img and flash stock recovery. Reboot and then take OTA. You can now fastboot boot TWRP from download mode to make a backup of stock recovery(before flashing TWRP).
schmeggy929 said:
When you unlock, then flash TWRP, first thing you do is Keep System Read Only. Then make a backup of System Image, boot image. When its time for OTA. restore system image, boot img and flash stock recovery. Reboot and then take OTA. You can now fastboot boot TWRP from download mode to make a backup of stock recovery(before flashing TWRP).
Click to expand...
Click to collapse
Since TWRP can flash OTAs (firmware part of OTAs needs to be flashed separately via fastboot), restoring (and backing up) stock recovery is not mandatory.
Do you think Sunshine will come to U 11 or it's un-crackable?
schmeggy929 said:
When you unlock, then flash TWRP, first thing you do is Keep System Read Only. Then make a backup of System Image, boot image. When its time for OTA. restore system image, boot img and flash stock recovery. Reboot and then take OTA. You can now fastboot boot TWRP from download mode to make a backup of stock recovery(before flashing TWRP).
Click to expand...
Click to collapse
Thanks! For some reason though, when I tried to fastboot boot twrp, it would flash successfully but hang on the rebooting part. I have no idea what was going on. Pretty frustrating.
No laughing now- I'm on an old Galaxy s4 & U11 seems like my next device, VZW is too much & Sprint has a 1yr free program. I have rooted B4, & used Odin, but I got into other things & I don't recall how Fastbooting works… PLS help the once again Fastbooy noob & explain. Since the Sprint program requires you bring an already-paid-for 'bring your own phone' this is a BIG up front investment & I can't imagine going w/out Root/TitaniumBU/ or twrp to save images to pull my coals out of potential fires… TIA, oldwolf
IMHO, fastboot commands and such to get TWRP installed is waaaaaaay easier and faster than ODIN. I actually try every few phone generations to use a samsung device, but the pains of doing updates and such through odin isn't worth it to me. Pretty much you can unlock your phone through HTC.dev and then with the bootloader unlocked you can load your own recovery like TWRP. they walk you through all the steps and everything.
tacotoy, thanks for the reply; but what constitutes a FB command, & fm what program & in what status of android boot is it run? tia, oldwolf
Yeah, lost... New VZW OTA out today, but since I'm unlocked with TWRP, won't install. Trying to find the zip in the cache so that TWRP can install it, no joy so far, re-reading the TWRP thread.
Edit: Found path: /data/data/com.htc.updater/files/OTA_OCEAN_WHL_N71_SENSE90GP_NA_Gen_Unlock_1.11.617.4-1.11.617.3_R2_release_.zip
Fails, says system modified, even after restore to stock.
deafmetal1 said:
Yeah, lost... New VZW OTA out today, but since I'm unlocked with TWRP, won't install. Trying to find the zip in the cache so that TWRP can install it, no joy so far, re-reading the TWRP thread.
Edit: Found path: /data/data/com.htc.updater/files/OTA_OCEAN_WHL_N71_SENSE90GP_NA_Gen_Unlock_1.11.617.4-1.11.617.3_R2_release_.zip
Fails, says system modified, even after restore to stock.
Click to expand...
Click to collapse
Did you check to keep system read only before restoring the backup?
oldwolf613 said:
tacotoy, thanks for the reply; but what constitutes a FB command, & fm what program & in what status of android boot is it run? tia, oldwolf
Click to expand...
Click to collapse
just google Minimal ADB and Fastboot. Download the lastest and place all your zips and images in that folder. It is a standalone program easy and pain free.
Schmeggy929, thanks, that's easy enuf, but since this is gonna be (hopefully) my 'bring your phone'
to Sprint to get the free years worth of service- it's gotta be bought outright & while it's a good investment, I cannot afford to brick it & I'd rather look like a noob again than NOT ask…
I just used the latest RUU that OBJ posted in the Collection Post. This time I'll make sure to do the initial TWRP recovery in read-only... HTC noob...