Database Info

[Q] Difference recovery and flashboot flash?

I have a fastboot oem unlock'ed Nexus S I9020T. I am interested in the methods I can use to restore stock GRI40 (e.g. android.clients.google.com/packages/ota/google_crespo/f182cf141e6a.signed-soju-ota-102588.f182cf14.zip). I am running stock recovery although I have a copy of
Clockwork Recovery 3.0.2.4 on hand. I don't care about any data on the device -- in fact, I would probably prefer to nuke it all.
One way I have successfully done this already (thanks to instructions on the forum) is to copy the soju ROM to the /sdcard root, boot into recovery and 'apply update from /sdcard'.
Are there other ways I could do this? I can imagine there is using fastboot flash or fastboot flashall might work... and there are probably more that I'm too n00b to imagine.
Thanks!
PS: as a forum newcomer, I'm posting this dev-centric question in this forum per the instructions in this thread. Please let me know if this is the wrong place.
PPS: Managed to post with a crap title, and can't edit that. Sorry!

"fastboot flash" is not for ROMs.. its using for flashing radios/bootloader etc.
Recovery is what you need to flash ROMs.
Updating radios and bootloaders can also be in done in recovery but in a flashable .zip format.
Fastboot flash is for .img(s)
Just use Recovery.. I don't know why you would want to flash it with something else. Alternatively, you can use Odin but I wouldn't recommend it since there isn't any need to. It's a last resort.

Thanks! As a followup, does does flashing a ROM from recovery also flash the radio, boot image, bootloader, recovery (so, for example, will flashing stock GRI40 overwrite clockwork recovery if installed)?
Inside the GRI40 zip, I see boot.img, bootloader.img, and radio.img, so I'm guessing yes, at least partially. Does bootloader.img include a stock recovery?
Thanks again.

Desire s stuck after 2.3.5 update

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.

Did something wrong while rooting, how to fix it

after all the trouble I had for flashing a wrong PG58IMG (flashed a firmware instead of clockworkmod)
Now I have Hboot 1.17.2008, clockworkmod flashed, super cid.
I can log into CWM recovery mode, but having trouble installing su-2.3.6.3-efgh-signed to have it rooted.

anthony0721 said:
after all the trouble I had for flashing a wrong PG58IMG (flashed a firmware instead of clockworkmod)
Now I have Hboot 1.17.2008, clockworkmod flashed, super cid.
I can log into CWM recovery mode, but having trouble installing su-2.3.6.3-efgh-signed to have it rooted.
Click to expand...
Click to collapse
Hi,
Sometimes it takes more than one go.
If it still fails,then look for a different version HERE

Don't worry, it's still fine.
Flash JB ICS Hboot from http://Unlimited.io.
Now, as for flashing recovery, flash an image instead of using the PG58IMG.zip.
I had given your very clear instructions previously, if you don't listen, this is what is going to happen.

malybru said:
Hi,
Sometimes it takes more than one go.
If it still fails,then look for a different version HERE
Click to expand...
Click to collapse
thanks, installation completed after flashing it 3 times.
But now still asking me for unlocking code after inserting Sim card

[HELP] Root Help

i attempted to root my sensation, i signed up with the htcdev thingy, and i got the unlock boot loader thing...(sorry not familiar with sensation) and i let it install with One X??? and i did the steps, and i did flash CWM and i went into it, made a back up, then i installed a custom rom, and i rebooted, and now its just on this android boot screen and its a flash going accross it...PLEASE help...

Did you wiped your old ROM before installing a new one? From the steps you mentioned - NOT.
Perform a full wipe and re-flash the ROM and also check that your RADIO (or firmware in the Sensation forum) matches the version required for the ROM
Such information can be found in the ROM's thread - links/guides everywhere in the Development section

9595jakob said:
i attempted to root my sensation, i signed up with the htcdev thingy, and i got the unlock boot loader thing...(sorry not familiar with sensation) and i let it install with One X??? and i did the steps, and i did flash CWM and i went into it, made a back up, then i installed a custom rom, and i rebooted, and now its just on this android boot screen and its a flash going accross it...PLEASE help...
Click to expand...
Click to collapse
extract the boot.img from the custom rom zip file ...
and flash it via fastboot
fastboot flash boot boot.img
also check if the one-x tool kit has option to flash a boot.img ..if so ..use that ..but use the boot.img you have extracted from the custom rom zip file that you have flashed

[Q] Bricked?

I unlocked and installed the CWM recovery. The ROM manager confirmed this was installed.
Following the guide at teamadroid.com for the twistedkat 4.4.2 ROM.
I flashed a new boot.img (from the twistedkat ROM).
Now I just see the "Only for internal use" red letters, and cannot invoke the CWM recovery for installing the ROM.
Any help would be appreciated on how to install the ROM or get back to stock.
EDIT: I progressed from this situation by re-flashing the CWM recovery, even though this emitted an error indicating that the file could not be validated or such. After this I can enter the CWM recovery.
Thanks!

qabi said:
I unlocked and installed the CWM recovery. The ROM manager confirmed this was installed.
Following the guide at teamadroid.com for the twistedkat 4.4.2 ROM.
I flashed a new boot.img (from the twistedkat ROM).
Now I just see the "Only for internal use" red letters, and cannot invoke the CWM recovery for installing the ROM.
Any help would be appreciated on how to install the ROM or get back to stock.
EDIT: I progressed from this situation by re-flashing the CWM recovery, even though this emitted an error indicating that the file could not be validated or such. After this I can enter the CWM recovery.
Thanks!
Click to expand...
Click to collapse
Do you have Ville (S4) or Ville C2 (S3) model?
If you have S4 ( I suppose due to te fact you installed TwistedKat) install this recovery --> http://goo.im/devs/philz_touch/CWM_Advanced_Edition/ville/philz_touch_6.19.3-ville.zip
The recovery provided by rom manager does NOT support Android 4.4.2 KItKat roms !!!
PLS check if you have S3 or S4

LS.xD said:
The recovery provided by rom manager does NOT support Android 4.4.2 KItKat roms !!!
Click to expand...
Click to collapse
Thanks for your suggestion.
Actually I don't know. I think only one HTC One S was ever in my market (Denmark).
In the meantime I succeeded installing the TwistedKat ROM and have it running now.
Does anybody know of a tutorial for resetting to stock ROM? (Just in case I want to revert).
-qabi

Unable to enter clockwork recovery?
I installed clockwork recovery and actually managed to install TwistedKat (what seems to be an old version).
But I am unable to enter the clockwork recovery in order to reflash to another ROM. Choosing RECOVERY from HBOOT just shows the warning screen and then halts the phone.
I have been reding through a ton of threads mentioning similar symptoms, but with no solution found.
Any help would really be appreciated!

qabi said:
I installed clockwork recovery and actually managed to install TwistedKat (what seems to be an old version).
But I am unable to enter the clockwork recovery in order to reflash to another ROM. Choosing RECOVERY from HBOOT just shows the warning screen and then halts the phone.
I have been reding through a ton of threads mentioning similar symptoms, but with no solution found.
Any help would really be appreciated!
Click to expand...
Click to collapse
I get this as well. Try it twice. For me the second time always boots up into CWM.
Can you tell me what you did to get rid of the red letters/HTC??? Did you flash boot.img again???

808phone said:
I get this as well. Try it twice. For me the second time always boots up into CWM.
Can you tell me what you did to get rid of the red letters/HTC??? Did you flash boot.img again???
Click to expand...
Click to collapse
Which recovery do you use? Are you S-OFF // SuperCID // HBOOT 2.15??

808phone said:
I get this as well. Try it twice. For me the second time always boots up into CWM.
Can you tell me what you did to get rid of the red letters/HTC??? Did you flash boot.img again???
Click to expand...
Click to collapse
The "red letters" have nothing to do with kernel. To get rid of them you must be S-Off and flash a moded hboot/firmware. There is one in the firmware thread that has the red warning removed.
@qabi: don't use CWM. Flash latest TWRP 2.7, you should be able to flash any ROM with it except the ones for 2.16 hboot
Sent from nowhere over the air...

Rapier said:
The "red letters" have nothing to do with kernel. To get rid of them you must be S-Off and flash a moded hboot/firmware. There is one in the firmware thread that has the red warning removed.
@qabi: don't use CWM. Flash latest TWRP 2.7, you should be able to flash any ROM with it except the ones for 2.16 hboot
Sent from nowhere over the air...
Click to expand...
Click to collapse
Rapier, can you explain this? A while back I loaded TWRP (S-ON) then loaded one of the CM series (either 11 or 10, can't remember). Then after I flashed boot.img, I was stuck in boot loop with HTC/red letters.
The reason I was asking what he did was I never did get to stop the boot loop myself. I paid to get it fixed, but I would like to know what I should have done to fix the boot loop after flashing the boot.img and having the problem. Seems like a lot of people get this so, so would be nice to know.
I was basically following everything listed on a web page and everything was working. Unlocked boot loader, SuperSU, TWRP etc... the last thing I did was flash the boot.img and then the problems occurred.
As far as the double try for CWM, I am S-OFF, 2.15 and I noticed it happens every now and then. I don't have this issue with TWRP at all.

It is hard to say why, apparently you did all right. What I can think off is a bad download or a bad flash or you could have used a wrong TWRP version. Also that ROM you have tried could have issues. It is very hard to know why without some logs that shows what went wrong
Sent from nowhere over the air...

LS.xD said:
If you have S4 ( I suppose due to te fact you installed TwistedKat) install this recovery -->
Click to expand...
Click to collapse
After much mucking about I flashed the "philz" recovery. That helped alot - I can now enter recovery every time. So apparently the original CWM recovery has problems on the HTC one S.
Thanks for your suggestions guys!

qabi said:
After much mucking about I flashed the "philz" recovery. That helped alot - I can now enter recovery every time. So apparently the original CWM recovery has problems on the HTC one S.
Thanks for your suggestions guys!
Click to expand...
Click to collapse
I think so. I am running the latest CWM and never had problems before this.