Related
I flashed and tried install custom rom without turning off S-on. Hboot and Rocover is ok but phone is not starting. Any help how can i turn off S-on now?
vimrul said:
I flashed and tried install custom rom without turning off S-on. Hboot and Rocover is ok but phone is not starting. Any help how can i turn off S-on now?
Click to expand...
Click to collapse
If adb is working you can unlock the bootloader and try to flash the rom. Also you can look at this giude
vimrul said:
I flashed and tried install custom rom without turning off S-on. Hboot and Rocover is ok but phone is not starting. Any help how can i turn off S-on now?
Click to expand...
Click to collapse
Did you flash the boot.img from fastboot?
bananagranola said:
Did you flash the boot.img from fastboot?
Click to expand...
Click to collapse
No didn't. Should I do that ??
vimrul said:
No didn't. Should I do that ??
Click to expand...
Click to collapse
If you are S-ON, you need to flash the ROM's boot.img in fastboot each time you flash a ROM.
bananagranola said:
If you are S-ON, you need to flash the ROM's boot.img in fastboot each time you flash a ROM.
Click to expand...
Click to collapse
Is it possible to lash the ROM's boot.img when I am on S-on ? OK I am on it ..
bananagranola said:
If you are S-ON, you need to flash the ROM's boot.img in fastboot each time you flash a ROM.
Click to expand...
Click to collapse
Waiting for device on CMD problem while i was trying to flashing boot.img. Any other way to do this? its not possible to on USB debugging mode because Phone stacked on white screen. Any other to flash boot.img? please
vimrul said:
Waiting for device on CMD problem while i was trying to flashing boot.img. Any other way to do this? its not possible to on USB debugging mode because Phone stacked on white screen. Any other to flash boot.img? please
Click to expand...
Click to collapse
From fastboot, not ADB. Detailed instructions are in post #7 of the Ace Think Tank thread in my signature.
vimrul said:
I flashed and tried install custom rom without turning off S-on. Hboot and Rocover is ok but phone is not starting. Any help how can i turn off S-on now?
Click to expand...
Click to collapse
Did you unlock the bootloader?? If not flashing the boot.img won't work either. you need to try unlocking the bootloader from fastboot first, then when you have working phone you decide what to do.
hi, i need help with this.
QUick run down on my story, bought the phone and found out that it is rooted so wanted to go back to stock and ended up getting it stuck on fastboot loop.
Im only new to this and found the thread in developers area with guidance on how to fix this but im getting very confused as to what i need to do and what files i need downloaded including ruu, im from AU and there isnt many ruus for voda 021 floating around. I would be happy tho if i can flash it to same rooted state as it was as long i get it working again.
Can someone give me some pointers pls, the way that thread with instruction is written is very hard for me to understand because some basic steps are skipped prob because orger understand them but im very nooby and cant work with it
tx:crying:
deemoIII said:
hi, i need help with this.
QUick run down on my story, bought the phone and found out that it is rooted so wanted to go back to stock and ended up getting it stuck on fastboot loop.
Im only new to this and found the thread in developers area with guidance on how to fix this but im getting very confused as to what i need to do and what files i need downloaded including ruu, im from AU and there isnt many ruus for voda 021 floating around. I would be happy tho if i can flash it to same rooted state as it was as long i get it working again.
Can someone give me some pointers pls, the way that thread with instruction is written is very hard for me to understand because some basic steps are skipped prob because orger understand them but im very nooby and cant work with it
tx:crying:
Click to expand...
Click to collapse
you need to give more info than what you have !! . can you access recovery volume down and power for about six seconds,remove when you get to fastboot screen- what is your hboot 3rd down are you locked unlocked, s-off s-on,select recovery and see if you are on stock recovery or custom ?
markb63 said:
you need to give more info than what you have !! . can you access recovery volume down and power for about six seconds,remove when you get to fastboot screen- what is your hboot 3rd down are you locked unlocked, s-off s-on,select recovery and see if you are on stock recovery or custom ?
Click to expand...
Click to collapse
ok i got relocked and security warning
ship s-on
radio 2.1204.135.20
when i go to recovery phone goes to a red triangle o top of a phone after being green arrow for short time, then i have to shut down cus that does nothing. dont know what else i can tell u about recovery
deemoIII said:
ok i got relocked and security warning
ship s-on
radio 2.1204.135.20
when i go to recovery phone goes to a red triangle o top of a phone after being green arrow for short time, then i have to shut down cus that does nothing. dont know what else i can tell u about recovery
Click to expand...
Click to collapse
ok, i think you've tried to flash a stock rom without flashing a stock recovery !!.
do you have fasboot adb on your pc ?
you need to unlock your bootloader and re flash a custom recovery
if not search the dev section for a tool that will unlock your boot and re-flash a custom recovery for you-all the instructions are on there.
once you have re unlocked and flashed a custom recovery,go into recovery and see if there are any backups of the previous rom (nand)
see if that works ..
markb63 said:
ok, i think you've tried to flash a stock rom without flashing a stock recovery !!.
do you have fasboot adb on your pc ?
you need to unlock your bootloader and re flash a custom recovery
if not search the dev section for a tool that will unlock your boot and re-flash a custom recovery for you-all the instructions are on there.
once you have re unlocked and flashed a custom recovery,go into recovery and see if there are any backups of the previous rom (nand)
see if that works ..
Click to expand...
Click to collapse
If you wanna go back to stock and are stuck at bootloop you have to flash the boot.omg file for your stockrom .
markb63 said:
ok, i think you've tried to flash a stock rom without flashing a stock recovery !!.
do you have fasboot adb on your pc ?
you need to unlock your bootloader and re flash a custom recovery
if not search the dev section for a tool that will unlock your boot and re-flash a custom recovery for you-all the instructions are on there.
once you have re unlocked and flashed a custom recovery,go into recovery and see if there are any backups of the previous rom (nand)
see if that works ..
Click to expand...
Click to collapse
im sorry champ, not getting this too good.
when you say " re flash a custom recovery" what do you mean with that and would i be able to get one from the net. I tried looking for the instructions without much luck
deemoIII said:
im sorry champ, not getting this too good.
when you say " re flash a custom recovery" what do you mean with that and would i be able to get one from the net. I tried looking for the instructions without much luck
Click to expand...
Click to collapse
you need to read and study this http://forum.xda-developers.com/showthread.php?t=2069904
Try this
markb63 said:
you need to read and study this http://forum.xda-developers.com/showthread.php?t=2069904
Click to expand...
Click to collapse
Try to do this from this guide : http://www.youtube.com/watch?v=SZuAjz4PIjU
cool, so i follow this, tx Mark
markb63
you need to read and study this: [url said:
http://forum.xda-developers.com/show....php?t=2069904[/url]
Click to expand...
Click to collapse
ytube vid as a guide, tx Omer
Omer Slomovic said:
Try to do this from this guide : http://www.youtube.com/watch?v=SZuAjz4PIjU
Click to expand...
Click to collapse
al tho this is the video i followed when i screwed it in the first place
and i need to do parts 1 and 2 ? did i screw up the ROM on my phone so i have to flash it, thing is a can only do same rooted rom as it was cus there is no stock available for download for Australias voda021
i hope you can tell me that i only need part 1.
Damn i shouldnt have even touched it
Post 1: How to unlock your bootloader, flash a recovery and root
Post 2: How to flash a custom ROM and kernel (boot.img)
ill be trying this after wk
the problem i have is that the pc doesnt see the phone, only for 3-4 secs when fastboot usb selected and ph says sd checking, then it gives an error and goes back to first screen and pc doesnt see it again.
How do i figure out what RUU i need and can use safely? considering its got radio 2.1204.135.20 currently
ill post some screens, these are all i can manage to get into
its relocked and s-on
rooted atm radio 2.1204.135.20
phone cid is vodap021
first screen http://s39.beta.photobucket.com/user/bijeli_gavran/media/Photo2215.jpg.html
i can get in here http://s39.beta.photobucket.com/user/bijeli_gavran/media/Photo2219.jpg.html
but then when i hit power i get this http://s39.beta.photobucket.com/user/bijeli_gavran/media/Photo2216.jpg.html and no connection to pc
and when i try recovery i can get this screen but i dont think i got the files the recovery is after
http://s39.beta.photobucket.com/user/bijeli_gavran/media/Photo2220.jpg.html
help?:crying:
According to the hboot (1.12) you need a 2.17 based ruu .... but i can't find it !
Tthe basic steps now are
Unlock the bootloader, flash a custom recovery
http://db.tt/Krlm4dPs
http://forum.xda-developers.com/showthread.php?t=1975140
Get your nandroid backup there,(the vodap021 2.17) you need to flash the boot.img file from that nandroid with fastboot commands, then do a full wipe in recovery and restore the nandroid.
But you still have to fix the fastboot part right ? You need to install android SDK/java SDK and the HTC drivers. Then you have to put the phone in the bootloader and open a commandprompt from inside the folder where the adb/fastboot files are located ...they are in a subfolder in the installed javaSDK install folder
Mr Hofs said:
According to the hboot (1.12) you need a 2.17 based ruu .... but i can't find it !
Tthe basic steps now are
Unlock the bootloader, flash a custom recovery
http://db.tt/Krlm4dPs
http://forum.xda-developers.com/showthread.php?t=1975140
Get your nandroid backup there,(the vodap021 2.17) you need to flash the boot.img file from that nandroid with fastboot commands, then do a full wipe in recovery and restore the nandroid.
But you still have to fix the fastboot part right ? You need to install android SDK/java SDK and the HTC drivers. Then you have to put the phone in the bootloader and open a commandprompt from inside the folder where the adb/fastboot files are located ...they are in a subfolder in the installed javaSDK install folder
Click to expand...
Click to collapse
Thanks, it is beginning to make some sense to me now.
So first bit I got to do is the fastboot issue, which is tha last bit you mentioned right?
And after unlock boot loader than flash the recovery with one you provided in the link, tx
So that means I will go back to stock right?
Yes unlock, flash custom recovery, flash boot.img, full wipe in recovery, restore the nandroid, flash back the stock recovery .....
And yes this way you go back to stock and i will also give you the download link for the stock recovery. This one is the last you flash after restoring everything
http://db.tt/U5CK4noo
Then you are able to update to JB from within the phones software update menu :thumbup:
Ps you do not have to relock the bootloader anymore !
Mr Hofs said:
Yes unlock, flash custom recovery, flash boot.img, full wipe in recovery, restore the nandroid, flash back the stock recovery .....
And yes this way you go back to stock and i will also give you the download link for the stock recovery. This one is the last you flash after restoring everything
http://db.tt/U5CK4noo
Then you are able to update to JB from within the phones software update menu :thumbup:
Ps you do not have to relock the bootloader anymore !
Click to expand...
Click to collapse
Thanks for that, ill need to study some tuts on how to do some of this stuff and see ihow i go
deemoIII said:
Thanks for that, ill need to study some tuts on how to do some of this stuff and see ihow i go
Click to expand...
Click to collapse
ugh, im really having hard time getting this done, any chance you can point me out towards some TUT pages for unlocking?
Ok, iwe made some progress, unlocked, flushed custom recovery, wiped
now im having trouble working out how to restoring the nandroid? iwe got the files but how do i restore them on the phone, is it through the cmd or over usb...is there any detailed tuts
deemoIII said:
Ok, iwe made some progress, unlocked, flushed custom recovery, wiped
now im having trouble working out how to restoring the nandroid? iwe got the files but how do i restore them on the phone, is it through the cmd or over usb...is there any detailed tuts
Click to expand...
Click to collapse
Please guys, iWe spent all day trying to figure it out, after wipe phone reboots constantly and when if boot screen it's not charging so I'm prob going to run out of battery in a couple of hours
You restore through the custom recovery. Power+vol , choose recovery. If you flashed the recovery ok then you can do from in there. Ie mount usb, copy over your nand backup and restore it. You may have to flash the boot.img using fastboot.
Sent from my HTC One X
Hey
I was following this tutorial:
http://forum.xda-developers.com/showthread.php?t=1525100
And everything worked well untill the part I had to boot into recovery mode.
I couldn't get into it and decided to skip that part and just flash the boot.img from the ROM
http://forum.xda-developers.com/showthread.php?t=1778202
I flashed everything succesful without any errors but now my phone won't boot, it just gives me a black screen and can't get into recovery.
My bootloader is unlocked and I can still get into it.
I was thinking about flashing the stock RUU or another ROM, but is this possible?
Now I can't use my desire hd .. need some help with it.
EDIT:
I'm S-ON and unlocked bootloader.
I just tried to flash CWM and it flashed succesfully but still couldn't boot into recovery..
That tutorial is for the Desire S. What RUU did you use?
bananagranola said:
That tutorial is for the Desire S. What RUU did you use?
Click to expand...
Click to collapse
I didn't use RUU yet, I was thinking about it..
...OK, I'm confused. Exactly what have you done?
bananagranola said:
...OK, I'm confused. Exactly what have you done?
Click to expand...
Click to collapse
First I unlocked the bootloader.
Then I moved the ROM's zip file to the SD card.
I flashed the 4EXT Recovery after that.
I couldn't boot into recovery so I flashed the ROM's boot.img
Then I couldn't boot my phone in normal mode
After that I flashed CWM but it also didn't work..
Then I used fastboot erase cache and after that I tried fastboot oem rebootRUU
that's all I did untill now
What did you have on your phone to begin with, stock? What ROM zip did you get the boot.img from? How did you flash recovery? Which image?
bananagranola said:
What did you have on your phone to begin with, stock? What ROM zip did you get the boot.img from? How did you flash recovery? Which image?
Click to expand...
Click to collapse
I had stock rom on my phone, didn't make a backup.
http://forum.xda-developers.com/showthread.php?t=2335496 is the rom I tried to put on my phone, that is where the boot.img is from.
And I flashed recovery with
fastboot flash recovery recovery.img
btw, i dont have a file PD98IMG
EDIT:
I tried booting into recovery with the command fastboot boot recovery.img
but it is stuck on the HTC screen
OK, you've flashed a JB AOSP boot.img on a Froyo/GB Sense ROM. No wonder it's not booting. Again, where did you get the recovery image from? You need to flash a working recovery from fastboot (fastboot flash recovery recovery.img), flash the ROM from recovery, and flash the matching boot.img from fastboot (fastboot flash boot boot.img).
bananagranola said:
OK, you've flashed a JB AOSP boot.img on a Froyo/GB Sense ROM. No wonder it's not booting. Again, where did you get the recovery image from? You need to flash a working recovery from fastboot (fastboot flash recovery recovery.img), flash the ROM from recovery, and flash the matching boot.img from fastboot (fastboot flash boot boot.img).
Click to expand...
Click to collapse
I just googled the CWM Recover img...
Can you link me to a working recovery img? and to a ROM that is running android 4.0 or higher and is easier to flash?
thanks man!
SmikkelMikkel said:
I just googled the CWM Recover img...
Can you link me to a working recovery img? and to a ROM that is running android 4.0 or higher and is easier to flash?
thanks man!
Click to expand...
Click to collapse
Recoveries are device specific. http://www.clockworkmod.com/rommanager. ROMs are all flashed the same way if you are S-On with an unlocked bootloader.
bananagranola said:
Recoveries are device specific. http://www.clockworkmod.com/rommanager. ROMs are all flashed the same way if you are S-On with an unlocked bootloader.
Click to expand...
Click to collapse
Well thanks, I fixed it myself but still thank you for your help.
You sent me in the right direction !
I have an unlocked bootloader but not s-off am I still able to flash custom roms? if so how do I know which ones I can flash?
dbarrett480 said:
I have an unlocked bootloader but not s-off am I still able to flash custom roms? if so how do I know which ones I can flash?
Click to expand...
Click to collapse
Does the old trick of booting to recovery via fastboot still work? I haven't had an HTC phone for a while....
dbarrett480 said:
I have an unlocked bootloader but not s-off am I still able to flash custom roms? if so how do I know which ones I can flash?
Click to expand...
Click to collapse
dbarrett480 said:
Does the old trick of booting to recovery via fastboot still work? I haven't had an HTC phone for a while....
Click to expand...
Click to collapse
Yes you can flash any ROM while S-On. S-Off is not needed for that.
And yes, you can get to recovery via your bootloader. But once you have a custom ROM, the option to boot to recovery will be available when you long press power.
S-OFF only really comes handy as you can flash different FW packages that aren't signed by HTC, or downgrade to an older FW package if required/wanted
Correct me if I am wrong, but from what I understand you can't flash a kernel with S-ON right?
TempestZ said:
Correct me if I am wrong, but from what I understand you can't flash a kernel with S-ON right?
Click to expand...
Click to collapse
Wrong
U can flash following partitions
system
boot
data
recovery
TempestZ said:
Correct me if I am wrong, but from what I understand you can't flash a kernel with S-ON right?
Click to expand...
Click to collapse
That was the case with the One X a few years back but changed since...
I was able to flash a kernel last night by fastbooting to recovery
Sent from my HTC One_M8 using XDA Free mobile app
I have an international stock HTC One M9. CID is: HTC__621 and firmware version: 210.709.1 - I've already found the stock recovery for 210.709.1 - I'm looking to install a custom ROM, but I may want to go back to stock later on. I found a TWRP stock backup for 210.709.1, but because I am S-ON, will I not have to manually flash the boot.img? I used winrar to look into the TWRP backup, and I could not find a boot.img. So, my question is: if I flash the TWRP backup using TWRP, will the boot.img automatically get flashed?
You will have to flash the boot.img manually. The boot image is there it should be called boot.emmc.win .
mrbtree98 said:
You will have to flash the boot.img manually. The boot image is there it should be called boot.emmc.win .
Click to expand...
Click to collapse
Should I rename this to: "boot.img"? And then, use command: " fastboot flash boot boot.img"?
mrbtree98 said:
You will have to flash the boot.img manually. The boot image is there it should be called boot.emmc.win .
Click to expand...
Click to collapse
There's no "boot.emmc.win" within the archive? I can't find it...
arif9m9 said:
Should I rename this to: "boot.img"? And then, use command: " fastboot flash boot boot.img"?
Click to expand...
Click to collapse
Some weeks ago I was told that all newer phones than the HTC One M7 are able to flash boot images with TWRP even if they are S-ON. (I wasn't able to verify that since my phone is S-OFF.) So there should be no need to rename and manually flash the boot image if it's already inside the backup.
arif9m9 said:
There's no "boot.emmc.win" within the archive? I can't find it...
Click to expand...
Click to collapse
You can find the needed boot image in my signature.
Flippy498 said:
You can find the needed boot image in my signature.
Click to expand...
Click to collapse
Thanks. I downloaded: "boot_2.10.709.1.img" from your signature. Do I just flash it in fastboot like this: fastboot flash boot boot_2.10.709.1.img"? Is it okay if I rename it to just: boot.img?
My M9 is completely stock, right now. I'm intending to: unlock the bootloader, flash TWRP recovery, and finally, install an ASOP ROM.
When attempting to go back to stock, I'm going to: boot into TWRP, wipe everything except for SD card, flash the 2.10.709.1 TWRP stock backup, boot into fastboot and flash the command: "fastboot flash boot boot_2.10.709.1.img", flash the stock 2.10.709.1 recovery, and finally, relock the bootloader. Will all these steps be correct for an attempt to go back to stock?
arif9m9 said:
Thanks. I downloaded: "boot_2.10.709.1.img" from your signature. Do I just flash it in fastboot like this: fastboot flash boot boot_2.10.709.1.img"? Is it okay if I rename it to just: boot.img?
My M9 is completely stock, right now. I'm intending to: unlock the bootloader, flash TWRP recovery, and finally, install an ASOP ROM.
When attempting to go back to stock, I'm going to: boot into TWRP, wipe everything except for SD card, flash the 2.10.709.1 TWRP stock backup, boot into fastboot and flash the command: "fastboot flash boot boot_2.10.709.1.img", flash the stock 2.10.709.1 recovery, and finally, relock the bootloader. Will all these steps be correct for an attempt to go back to stock?
Click to expand...
Click to collapse
If you use the backup from my signature you only need to follow the instructions on the first page of my google sheet to get back to stock.
Be warned: Since Android 5.1 you should only relock the bootloader if you are completely sure that your phone is able to boot to system and that you ticked the new option that allows a bootloader unlock (can be found in the developers options). Many users already got stuck with a non-booting phone that cannot be re-unlocked because they didn't fulfill these requirements. (Sidenote: If you only want to get back to stock to install new OTAs you don't need to relock your bootloader.)
Besides I read that some people stated that the AOSP roms of the M9 messed up their LTE reception (so that LTE was even unusable on other custom roms or stock rom). I don't know whether this problem is already fixed. Some weeks passed since I read about that problem so I suggest you to read the corresponding threads before you start flashing.
arif9m9 said:
Thanks. I downloaded: "boot_2.10.709.1.img" from your signature. Do I just flash it in fastboot like this: fastboot flash boot boot_2.10.709.1.img"? Is it okay if I rename it to just: boot.img?
My M9 is completely stock, right now. I'm intending to: unlock the bootloader, flash TWRP recovery, and finally, install an ASOP ROM.
When attempting to go back to stock, I'm going to: boot into TWRP, wipe everything except for SD card, flash the 2.10.709.1 TWRP stock backup, boot into fastboot and flash the command: "fastboot flash boot boot_2.10.709.1.img", flash the stock 2.10.709.1 recovery, and finally, relock the bootloader. Will all these steps be correct for an attempt to go back to stock?
Click to expand...
Click to collapse
There is no need to flash the boot.img separately on this phone.
As noted DO NOT RELOCK unless you have ticked that "allow oem unlocking" option first. I cannot stress this enough.
Also, no AOSP rom currently has a working camera.
iElvis said:
There is no need to flash the boot.img separately on this phone.
As noted DO NOT RELOCK unless you have ticked that "allow oem unlocking" option first. I cannot stress this enough.
Also, no AOSP rom currently has a working camera.
Click to expand...
Click to collapse
My phone is S-ON, won't I have to flash the boot.img via fastboot?
arif9m9 said:
My phone is S-ON, won't I have to flash the boot.img via fastboot?
Click to expand...
Click to collapse
Flippy498 said:
Some weeks ago I was told that all newer phones than the HTC One M7 are able to flash boot images with TWRP even if they are S-ON.
Click to expand...
Click to collapse
iElvis said:
There is no need to flash the boot.img separately on this phone.
Click to expand...
Click to collapse
No, it's not needed. The only exceptions are backups that don't contain a boot image (like mine for example). That's why I created the google sheet with the instructions.
Flippy498 said:
No, it's not needed.
Click to expand...
Click to collapse
But, when installing custom ROMS, I'll definitely have to use the fastboot command to flash the boot image, right?
arif9m9 said:
But, when installing custom ROMS, I'll definitely have to use the fastboot command to flash the boot image, right?
Click to expand...
Click to collapse
No.
Flippy498 said:
No.
Click to expand...
Click to collapse
But, I'm S-ON....
arif9m9 said:
But, I'm S-ON....
Click to expand...
Click to collapse
It hasn't been an S-on restriction since the M7.
iElvis said:
It hasn't been an S-on restriction since the M7.
Click to expand...
Click to collapse
Does that mean I can flash RUUs even if I'm S-ON?
arif9m9 said:
Does that mean I can flash RUUs even if I'm S-ON?
Click to expand...
Click to collapse
For your CID/MID, yes.
iElvis said:
For your CID/MID, yes.
Click to expand...
Click to collapse
But, all the 'Returning to stock' guides
for the M9 state S-OFF is obligatory?
arif9m9 said:
But, all the 'Returning to stock' guides
for the M9 state S-OFF is obligatory?
Click to expand...
Click to collapse
It depends. If you have a current RUU for your phone (i.e., you don't need to downgrade), you can run it S-on, as that's what it's for.
But if you need to downgrade because the only RUU is an earlier version, yes you do need s-off.
S-off also allows you to go back to LOCKED instead of RELOCKED.
iElvis said:
It depends. If you have a current RUU for your phone (i.e., you don't need to downgrade), you can run it S-on, as that's what it's for.
But if you need to downgrade because the only RUU is an earlier version, yes you do need s-off.
S-off also allows you to go back to LOCKED instead of RELOCKED.
Click to expand...
Click to collapse
When going back to stock, at which stage should I relock my bootloader?
arif9m9 said:
But, all the 'Returning to stock' guides
for the M9 state S-OFF is obligatory?
Click to expand...
Click to collapse
Because if you follow these guides your phone will state "locked" instead of "relocked" at the end. And that is only possible with S-OFF. Besides with S-ON you can only use RUUs with the same firmware version as your phone (or newer RUUs)*.
*Actually downgrades seem to be possible, too, but as far as I know only if the two first numbers of the firmware versions before and after the downgrade are the same. Like from 1.32.xxx.15 to 1.32.xxx.8 but not from 1.40 versions to 1.32 versions or from 2.xx versions to lower versions.
Edit: Looks like I didn't type fast enough.