Initially I was running stock froyo 2.2.1 and 2.28xxx Radio and it was running fine with the below mentioned hboot info
my bootloader info is something like
Blackrose
vivo pvt ship s-off rl
radio-3805.04.03.27_m
eMMC-boot
june 02 2012. 00:00:54
I then flashed a different radio version (corresponding to Froyo ROM) but after that It continously boot loop .
I can only enter into hboot and fastboot etc menus but cannot go to recovery anymore. when i go to recovery it again starts boot loop.
I unlocked and s-offed hboot an year back and i hardly remember those methods and my memory card is changed recently.
I tried flashing recovery using fastboot but problem persists. Still no recovery.( previously ClockwoodMod )
I have stock rom backup so once i can get into clockwood recovery i can restore those settings. Please help me out Guys . I did a huge mistake coming into custom roms after 1 year . lost all info .Now i'm pretty confused with all those terms and methods.
The only option is to flash recovery image. This is the reason you are not able to get into recovery.
What is the command you are using to flash recovery image?
Try to flash recovery image again.
Don't worry your phone is not bricked.
Sent from my HTC Incredible S using xda app-developers app
@di said:
The only option is to flash recovery image. This is the reason you are not able to get into recovery.
What is the command you are using to flash recovery image?
Try to flash recovery image again.
Don't worry your phone is not bricked.
Sent from my HTC Incredible S using xda app-developers app
Click to expand...
Click to collapse
1.on a freshly installed win 7 - 64 bit
2.installed java working
3.installed android-sdk installer_r20.0.3-windows.exe
4.opened sdk manager and installed platform tools
5.downloaded cwm recovery image and placed it in the platform tools folder
6.open cmd and inside platform tools folder
7.conned htc in fastboot mode and it showed fastboot usb after connecting
8.i typed follwing commands
fastboot flash recovery cwm-4.0.1.4.img
sending ' recovery ' <3700 kb>....
OKAY [1.150s]...
writing 'recovery'...
OKAY [0.799s]...
finished total time 1.947s
the fastboot usb in mobile stayed the same and i rebooted into hboot and went recovery . It rebooted into htc logo and boot loop continous . dint see any recovery. Where have i done wrong ? .. do i need any specific HTC Incredible S drivers for the PC ? ... what should i do now ? ...otherwise can i flash any ROM directly from fastboot usb mode ?
Thank you very much bro .. please help me out ..
What is your hboot version? 2.02.002?
Did you try flashing boot.IMG also?
If not then try that also...
Sent from my HTC Incredible S using xda app-developers app
@di said:
What is your hboot version? 2.02.002?
Did you try flashing boot.IMG also?
If not then try that also...
Sent from my HTC Incredible S using xda app-developers app
Click to expand...
Click to collapse
yes hboot version is 2.02. and which boot.img ? i dont get u .. of any ROM ?
Try a more recent recovery http://download.clockworkmod.com/recoveries/recovery-clockwork-5.0.2.0-vivo.img
and erase cache in fastboot
Code:
fastboot erase cache
Nonverbose said:
Try a more recent recovery http://download.clockworkmod.com/recoveries/recovery-clockwork-5.0.2.0-vivo.img
and erase cache in fastboot
Code:
fastboot erase cache
Click to expand...
Click to collapse
i tried the recent recovery image too but still it boots the moment it shows HTC logo( 2 secs logo and boot ) ... going to recovery after flashing also does the same boot loop. Do i need any adb drivers to detect vivo specifically ? .. i installed htc sync but dint connect vivo after that (when incS was actually working ).
also flashing boot.img from backed up froyo rom says FAILED writing. Battery is draining out on the otherside . It goes to boot loop when i charge it switched off too.
BTW Like i said I was running froyo stock rom which was also restored from backup but when i flashed the Radio maybe md5 or something dint match up and the firmware got corrupted . there's any bruteforce method to flash a custom or stock ROM or RUU ? ... I tried flashing nik_auro sense _4a ROM in fastboot usb but it says FAILED writing ! ... Can i solve this ? or my device is gone forever ?
I flashed boot.img of the backed up clockworkmod backup (froyo)
fastboot flash boot boot.img
it says
OKAY
Writing 'boot.img'
Finished.
Then i flashed recovery again
it says OKAY
Writing
Finished.
But same problem no difference.
BTW Everytime the usb is connected while booting up and al ... Windows 7 says USB driver not recognized ... ?? but flashing actually shows in cmd and hboot !!
You should install the driver correctly. Install htcsync and then uninstall it. Try flashing the recovery again. If that doesn't work, go into fastboot mode and type
Code:
fastboot getvar all
and post result here minus imei and serial number so we can get an ruu for you to flash.
boot loop
1.Exact boot loop time from vibration : 5 secs
2.i removed and reinstalled HTC Sync application but then it says
It popped up " HTC Sync Driver installed " when I went to Fastboot USB mode first time but also says
"USB Device not recognized . one of the USB devices attached to this has Malfunctioned . click for assistance " when connected in HBOOT mode as well as normal boot loop.
3.Tried flashing latest CWM recovery again and boot.img of backed up file. but still no difference .
4.IMEI and serial u mean the one in this below screenshot right ?
5.Previously i was on Codename Jellybean ROM and it worked fine then i wanted to get back to stock so i restored previous stock back up and it worked fine too and when i flashed this Froyo radio after which this problem started ( last froyo radio in the list )
Radio : From the 1.47.1400.3 RUU:
20.28.30.0802U_38.04.01.07
md5: eb83213f5a093a7baf7571409c9c2498
other info:
Blackrose
HBOOT 2.02.0002
Radio - 3805.04.03.27_M
jun 02 2012
I sent you PM, but it's nice to know that most problems connected to recoveries, boot.imgs and permissions get fixed with RUU. Of course it's easiest for s-off users (Revolutionary and BlackRose) cause all they need is to run RUU, and their phone will stay s-off and hboot won't be touched. For Alpharev and HTC unlocked users it's a bit different, Alpharev will lose their s-off cause hboot will be overwritten, and HTC unlocked have to relock their bootloader before RUU.
After successful RUU:
-S-off user have to flash recovery via fastboot
-HTC unlocked, so as Alpharev, have to unlock bootloader again (Alpharev for the first time) and flash recovery
The rest is magic...
Also, remember that flashing Froyo radio can cause you leaving with an expensive construction material (a hard brick)...
EDIT:
As I understood the last RUU is the same for all regions (same ruu.exe inside package One_Generic_code_Vivo.zip), so no need for gold cards anymore and the rest is handled with RUU itself. I already experienced that with Desire's 2.3 RUU.
n4naveen said:
1.Exact boot loop time from vibration : 5 secs
2.i removed and reinstalled HTC Sync application but then it says
It popped up " HTC Sync Driver installed " when I went to Fastboot USB mode first time but also says
"USB Device not recognized . one of the USB devices attached to this has Malfunctioned . click for assistance " when connected in HBOOT mode as well as normal boot loop.
3.Tried flashing latest CWM recovery again and boot.img of backed up file. but still no difference .
4.IMEI and serial u mean the one in this below screenshot right ?
5.Previously i was on Codename Jellybean ROM and it worked fine then i wanted to get back to stock so i restored previous stock back up and it worked fine too and when i flashed this Froyo radio after which this problem started ( last froyo radio in the list )
Radio : From the 1.47.1400.3 RUU:
20.28.30.0802U_38.04.01.07
md5: eb83213f5a093a7baf7571409c9c2498
other info:
Blackrose
HBOOT 2.02.0002
Radio - 3805.04.03.27_M
jun 02 2012
Click to expand...
Click to collapse
The last official Rom you had installed on your phone was not froyo, that may be why you're getting bootloops. You're actually extremely lucky you didn't get bricked but it seems only the phones shipped with gingerbread have that issue. Your main version shows you had a HK 2.3.3 ruu installed but that doesn't match your cid (india). Do you have a goldcard?
Try flashing a gb radio. That will likely fix your issue.
Here's the ruu matching your main version. http://www.filefactory.com/file/c0a...5AU_3805.04.03.27_M_release_189979_signed.exe
Nonverbose said:
The last official Rom you had installed on your phone was not froyo, that may be why you're getting bootloops. You're actually extremely lucky you didn't get bricked but it seems only the phones shipped with gingerbread have that issue. Your main version shows you had a HK 2.3.3 ruu installed but that doesn't match your cid (india). Do you have a goldcard?
Try flashing a gb radio. That will likely fix your issue.
Here's the ruu matching your main version. http://www.filefactory.com/file/c0a...5AU_3805.04.03.27_M_release_189979_signed.exe
Click to expand...
Click to collapse
Main version shows HK because i might've installed it before jellybean version or i also flashed GB boot.img after boot loop problem .
India is correct . My original ROM came with mobile is froyo in india .I have the back up of this Froyo ROM but dont know the exact RUU details . I have goldcard but it was made with another SDCARD dont know if that works with new SDCARD ...
Is it ok to flash this rom in fastboot usb mode for my mobile ?
ROM : HTC RUU Latin american version 4.14.405.2 ? ( it has file named One_generic_code_viva.zip) actually i need asia RUU but that link has incomplete file.
Mobile details : http://dl.xda-developers.com/attach...f7c459e3/50857d5a/1/4/1/9/7/4/1/vivo-info.jpg
I tried to flash HTC Canadian RUU(one_generic_code_vivo.zip ) in fastboot usb since i required asian RUU was a broken file in the link. ROM Update utility started , it identified my firmware version/ hboot so on .. like something like 2.12.xx to update latest 4.14.x so on .. but when i started to flash .. it started to show progress bar 1% .. but then immediately it changed to ----sending--- Bar(on PC) ......... (on mobile screen it showed HTC with black background without any progress bar ) it kept showing sending for 30 mins then i removed it and nothing flashed . same boot loop yet. any comments ? ... do i have to lock bootloader before flashing stock RUU ?... or can i flash a custom ROM ? ... I've no idea whats going on .. this is my device info http://www.4shared.com/photo/bgN6aHfQ/vivo-info.html?
It doesn't look like you flashed the gb radio like I suggested. Or even the ruu that I linked. You cannot flash a Canadian ruu because of the fact its a different model id.
Nonverbose said:
It doesn't look like you flashed the gb radio like I suggested. Or even the ruu that I linked. You cannot flash a Canadian ruu because of the fact its a different model id.
Click to expand...
Click to collapse
How am i supposed to flash the RUU which u gave ? cos none of these methods work ...
from PC in fastboot usb ... The rom update utility keeps showing sending ........ and on mobile HTC black screen logo without a progess bar .. i waited for 30 mins.
I made PG32IMG.zip and added my CID in android-txt file and placed it on SDCARD ... in Hboot mode it loaded the file ... showed parsing--for 1/10th of a sec and gone and the red progress bar dint appear. and the writing dint happen.
I extracted the rom.zip from RUU and flashed in fastboot flash zip file-name.zip . it says sending....and then stopped REMOTE : not allowed !
I also fastboot usb flashed 3805.4.03.27 radio of GB of my main version ... says the same error REMOTE : not allowed !
Ok, to cut all this nonsense, since you have blackrose you should be able to run any ruu cause it disables cid checking, but it, obviously, doesn't work for you.
Just flash newest radio via fastboot and install some custom rom.
nlooooo said:
Ok, to cut all this nonsense, since you have blackrose you should be able to run any ruu cause it disables cid checking, but it, obviously, doesn't work for you.
Just flash newest radio via fastboot and install some custom rom.
Click to expand...
Click to collapse
Not entirely true but thanks anyway.
boot loop
nlooooo said:
Ok, to cut all this nonsense, since you have blackrose you should be able to run any ruu cause it disables cid checking, but it, obviously, doesn't work for you.
Just flash newest radio via fastboot and install some custom rom.
Click to expand...
Click to collapse
I flashed the Latest GB Radio . says REMOTE : NOT ALLOWED)
I flashed CUstom ZIP nik_rebirth says REMOTE : NOT ALLOWED
it pretty much says the same except for cwm backed up boot.img
I flashed boot.img and it was written !!
I also changed modelid , cidnum , mainversion hbootpreupdate values same as my device details before flashing some GB radio and latest generic rom.zip but all it says is REMOTE : NOT ALLOWED !!
commands im using
fastboot flash zip PG32IMG.zip
fastboot flash zip rom-name.zip
fastboot flash boot boot.img
other conditions :
Cable is not the one provided by HTC
battery is around 10% now 3722mV
sdcard is not the goldcarded sdcard but i have the goldcard file with me.
below are the images before applying Blackrose HBOOT and running GB successfully
Related
Hi,
I used the procedure here (http://forum.xda-developers.com/showthread.php?p=14693680) to root and install CWM v4.0.1.4 on my Incredible S and while I was trying to flash a custom ROM onto my phone during CWM recovery, I kind of screwed up by wiping everything and not doing Backup.. I've been trying to find the Stock ROM for my phone to at least resume normal phone usage but I have been unable to find any. I've tried installing a lot of Custom ROMs including Cyanogen mod 7.1, Virtuous Quattro rc3, BinDroid RUNMED2.5, RCMix.Energized 2.21, etc, etc but nothing works. I desperately need advice as my phone is super important for my work :\
Please advise!
Btw here's my HBOOT message:
VIVO PVT SHIP S-ON RL
HBOOT-1.16.0000
RADIO-3805.09.03.27_M
eMMC-boot
Aug 26 2011, 12:28:53
My phone was on Android 2.3.4 and it was on HTC Sense 2.1..
Unlocked bootloader from htcdev.com? Need to know your region/carrier/cid.
Possible fix could be flashing boot.img from custom rom.zip in fastboot.
Code:
fastboot flash boot boot.img
Nonverbose said:
Unlocked bootloader from htcdev.com? Need to know your region/carrier/cid.
Possible fix could be flashing boot.img from custom rom.zip in fastboot.
Code:
fastboot flash boot boot.img
Click to expand...
Click to collapse
I'm not sure how to find out my region. I bought this phone 2nd-hand so I'm not sure about the specific details. I have the box and it says it's made in Taiwan. Do I provide the IMEI, S/N or P/N?
Sorry but what's a boot.img? :|
heyitsmik said:
I'm not sure how to find out my region. I bought this phone 2nd-hand so I'm not sure about the specific details. I have the box and it says it's made in Taiwan. Do I provide the IMEI, S/N or P/N?
Sorry but what's a boot.img? :|
Click to expand...
Click to collapse
EDIT:
I tried copying the boot.img from Cyanogen Mod 7.1.0 (File name: update-cm-7.1.0-RC1-IncS-signed) into C:/, then I typed "fastboot flash boot boot.img" into cmd after I 'cd' into C:/
Message:
C:\Android>fastboot flash boot boot.img
< waiting for device >
sending 'boot' (2178 KB)... OKAY [ 0.770s]
writing 'boot'... OKAY [ 0.598s]
finished. total time: 1.369s
Rebooting does nothing..
So I wiped (data/cache/Dalvik cache) and flashed the CM7.1.0 mod and now it works!! Amazing.. I spent 8 hours working previously and nothing worked. I shall try it on my real desired ROM later.
THANKS A LOT!
heyitsmik said:
I'm not sure how to find out my region. I bought this phone 2nd-hand so I'm not sure about the specific details. I have the box and it says it's made in Taiwan. Do I provide the IMEI, S/N or P/N?
Sorry but what's a boot.img? :|
Click to expand...
Click to collapse
Ok so if you were able to follow the procedure you quoted to install CWM, then you have adb and fastboot installed on your PC, so reboot the phone into FASTBOOT USB mode and then enter the following command and then post the results:
fastboot getvar all
Also was your HBOOT 1.16 S-Off or simply UNLOCKED before you flashed CWM?
tpbklake said:
Ok so if you were able to follow the procedure you quoted to install CWM, then you have adb and fastboot installed on your PC, so reboot the phone into FASTBOOT USB mode and then enter the following command and then post the results:
fastboot getvar all
Also was your HBOOT 1.16 S-Off or simply UNLOCKED before you flashed CWM?
Click to expand...
Click to collapse
Hi! Thanks for your input. Somehow the CM7.1.0 Mod was successfully flashed after I flashed the boot.img. No idea why though.. I am still on S-ON though, unlocked via HTCdev yeap..
Btw since I'm on the topic of custom ROMs on HBOOT 1.16.0000 with S-ON yet flashable, is it safe to say I can use the other ROMs that are available out there?
heyitsmik said:
Hi! Thanks for your input. Somehow the CM7.1.0 Mod was successfully flashed after I flashed the boot.img. No idea why though.. I am still on S-ON though, unlocked via HTCdev yeap..
Btw since I'm on the topic of custom ROMs on HBOOT 1.16.0000 with S-ON yet flashable, is it safe to say I can use the other ROMs that are available out there?
Click to expand...
Click to collapse
Yes, but you will have to manually flash the boot.img file from each custom ROM's zip file with the unlocked bootloader.
Not sure if I am in the right place to ask this question, well, i'll ask anyway.
I unlocked my bootloader using Revolutionary. I now need to revert to stock for warranty. I downloaded the INDIA RUU from goo manager.
I managed to replace the Revolutionary HBOOT by changing mainver. However, my radio is not getting replaced, no matter what I try. As a result, my phone bootloops though the RUU install was successful. So I had to revert to Revolutionary by installing WWE ASIA RUU. This was successful because the Radios are the same ie 3805.04.03.27_M.
I am currently on
HBOOT - 6.13.1002
Radio-3805.04.03.27_M
How can I go back to HBOOT 1.13 and Radio 38.02.01.11_M?
HBOOT - 6.13.1002 is still Revolutionary HBOOT?
I think that this is the easiest way to get stock bootloader and rom back. You need to find the latest WWE ASIA RUU for that.
Is that this one: RUU_VIVO_SENSE30_S_hTC_Asia_WWE_3.09.707.1_Radio_20.4802.30.0822U_3822.10.08.28_M_release_226940_signed.exe ?
If you have the latest RUU succesfully installed including the HBOOT, you're OK.
Inferi0r said:
HBOOT - 6.13.1002 is still Revolutionary HBOOT?
I think that this is the easiest way to get stock bootloader and rom back. You need to find the latest WWE ASIA RUU for that.
Is that this one: RUU_VIVO_SENSE30_S_hTC_Asia_WWE_3.09.707.1_Radio_20.4802.30.0822U_3822.10.08.28_M_release_226940_signed.exe ?
If you have the latest RUU succesfully installed including the HBOOT, you're OK.
Click to expand...
Click to collapse
thanks for the reply...but i don't think i explained my problem properly.
I first downloaded PG32IMG_Vivo_hTC_Asia_India_1.36.720.1_Radio_Radio_20.23.30.0802U_38.02.01.11_M_release_172022_signed.zip from Goo Manager. This is India RUU, but Froyo. This was what was installed on my phone first.
I first changed the mainver and renamed this RUU to PG32IMG.zip and let the bootloader install it. The HBOOT flashed perfectly, so my HBOOT became 1.09 but my radio was stuck at the same. This led the phone to bootloop because of incompatible radios.
So i tried extracting radio.img from PG32IMG_Vivo_hTC_Asia_India_1.36.720.1_Radio_Radio_20.23.30.0802U_38.02.01.11_M_release_172022_signed.zip and renamed to PG32IMG.zip and bootloader flash it. But it does not flash. My question is how do I replace the current radio with 38.02.01.11_M? The current radio is 3805.04.03.27_M.
craynet said:
thanks for the reply...but i don't think i explained my problem properly.
I first downloaded PG32IMG_Vivo_hTC_Asia_India_1.36.720.1_Radio_Radio_20.23.30.0802U_38.02.01.11_M_release_172022_signed.zip from Goo Manager. This is India RUU, but Froyo. This was what was installed on my phone first.
I first changed the mainver and renamed this RUU to PG32IMG.zip and let the bootloader install it. The HBOOT flashed perfectly, so my HBOOT became 1.09 but my radio was stuck at the same. This led the phone to bootloop because of incompatible radios.
So i tried extracting radio.img from PG32IMG_Vivo_hTC_Asia_India_1.36.720.1_Radio_Radio_20.23.30.0802U_38.02.01.11_M_release_172022_signed.zip and renamed to PG32IMG.zip and bootloader flash it. But it does not flash. My question is how do I replace the current radio with 38.02.01.11_M? The current radio is 3805.04.03.27_M.
Click to expand...
Click to collapse
If you currently have a GB ROM on your phone you also have a GB radio. If you attempt to flash the Froyo RUU you have downloaded, you are going to brick your phone because you cannot flash an older Froyo radio over a GB radio. This is a sure way to brick your phone.
fastboot....
tpbklake said:
If you currently have a GB ROM on your phone you also have a GB radio. If you attempt to flash the Froyo RUU you have downloaded, you are going to brick your phone because you cannot flash an older Froyo radio over a GB radio. This is a sure way to brick your phone.
Click to expand...
Click to collapse
yeah, you are right...i now remember that this will brick my phone, a risk not worth taking.
just a quick question, my phone is factory unlocked (the user I bought if from bought it on amazon.de) and currently I have an ICS rom with ICS radio, can I flash the GB RUU and then update to oficial ICS?
Do I still have to make goldcards and stuff?
skinniezinho said:
just a quick question, my phone is factory unlocked (the user I bought if from bought it on amazon.de) and currently I have an ICS rom with ICS radio, can I flash the GB RUU and then update to oficial ICS?
Do I still have to make goldcards and stuff?
Click to expand...
Click to collapse
With Revolutionary S-OFF, the RUU will not successfully overwrite the HBOOT and you will end up with a phone that won't boot past the HTC screen.
You would need to follow this procedure to allow the GB RUU to run successfully:
http://forum.xda-developers.com/showpost.php?p=15732727&postcount=14
This would leave you with a stock, unrooted phone. You woud be able to use HTCDEV.com to ulock the bootloader so you could root, but you are much better off staying S-OFF and using custom ICS ROMs.
tpbklake said:
With Revolutionary S-OFF, the RUU will not successfully overwrite the HBOOT and you will end up with a phone that won't boot past the HTC screen.
You would need to follow this procedure to allow the GB RUU to run successfully:
http://forum.xda-developers.com/showpost.php?p=15732727&postcount=14
This would leave you with a stock, unrooted phone. You woud be able to use HTCDEV.com to ulock the bootloader so you could root, but you are much better off staying S-OFF and using custom ICS ROMs.
Click to expand...
Click to collapse
Well I was stupid enought to flash the RUU so ended like you said.
I have macOs, downloaded fastboot and did fine till 2d.
I have the rom.zip but when I try to do
"fastboot flash hboot rom.zip"
it says:
cannot load 'rom.zip'
and the same if I try the vivo_downgrade.img
But if I do fastboot reboot-bootloader
It works..any suggestions?
exnerjan said:
This procedure is tested only AplhaRevX.
1. Install RUU ROM from: http://forum.xda-developers.com/show....php?t=1033922
2. Downgrade HBOOT
2a. download this file: http://alpharev.nl/vivo_downgrade.img
2aa. Connect your phone to the USB
2b.Turn your phone into FastBoot not to HBOOT!!! (VOL DOWN + POWER Button)
2c. Install over fastboot: cmd: "fastboot flash hboot vivo_downgrade.img" (you must install sdk tools)
2d. still fastboot cmd: fastboot reboot-bootloader
3. Start Installation RUU ROM, but DON´T INSTALL !!!!
3a. go tu C:\Users\%username%\AppData\Local\Temp and at last folder find rom.zip
3b. open it, and copy tu folder sdk hboot and instal the same as step 2c.
Click to expand...
Click to collapse
skinniezinho said:
Well I was stupid enought to flash the RUU so ended like you said.
I have macOs, downloaded fastboot and did fine till 2d.
I have the rom.zip but when I try to do
"fastboot flash hboot rom.zip"
it says:
cannot load 'rom.zip'
and the same if I try the vivo_downgrade.img
But if I do fastboot reboot-bootloader
It works..any suggestions?
Click to expand...
Click to collapse
Make sure that you have vivo_downgrade.img in the same folder where you run fastboot from.
Also, you cannot flash a ROM.zip file using the command fastboot flash hboot.
tpbklake said:
Make sure that you have vivo_downgrade.img in the same folder where you run fastboot from.
Also, you cannot flash a ROM.zip file using the command fastboot flash hboot.
Click to expand...
Click to collapse
So I do I do?
edit:
Just found it:
6. Rename this "rom.zip" file to "PG32IMG.zip"
7. Now take your SD card from Phone and connect it to your PC using a card reader or some other phone.
8. Paste that renamed "PG32IMG.zip" at the root of your SD Card.
9. Now power off your phone. Pull out the battery.
10. Insert the SD Card back in the phone. Insert the battery.
11. Now hold your volume down key and press power button. Keep the volume down key pressed. It will start your phone in boot-loader menu.
12. Select FASTBOOT if its not already selected and press power button.
13. It will search your SD Card for files and will find "PG32IMG.zip" file and will ask if you want to update.
14. Press the volume up button as instructed to continue and then sit back and relax.
Once finished it will ask you to reboot. Once rebooted, you'll be back on stock ROM with S-On.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1705913
Guys just a quick question.
Is any way to remove the "relocked" status of the bootloader?
My phone came from warranty,downgraded hboot with htcdev+alpharevx, now I must go to stock again because I need to send it again, did the whole thing but the bootloader says "relocked"
skinniezinho said:
Guys just a quick question.
Is any way to remove the "relocked" status of the bootloader?
My phone came from warranty,downgraded hboot with htcdev+alpharevx, now I must go to stock again because I need to send it again, did the whole thing but the bootloader says "relocked"
Click to expand...
Click to collapse
The only way is to load a stock RUU/ROM that has bootloader 1.13. If you have a ROM that uses HBOOT 2.00-2.02 then it will always show RELOCKED or UNLOCKED.
tpbklake said:
The only way is to load a stock RUU/ROM that has bootloader 1.13. If you have a ROM that uses HBOOT 2.00-2.02 then it will always show RELOCKED or UNLOCKED.
Click to expand...
Click to collapse
do you know wich one is it?for wwe phone.
skinniezinho said:
do you know wich one is it?for wwe phone.
Click to expand...
Click to collapse
wwe -> 2.30.405.1
Hey guys I badly need help!!! I was able to convert my HTC One GSM to Google Edition just last week, but today I want to restore it to its factory ROM so I can also restore the warranty. Now the problem became visible when I tried to flash a stock ROM (not the GPE ROM). Listed below are the problems I am facing at the moment:
1. Stuck in FASTBOOT USB, and cannot boot to ROM.
2. Can't boot to recovery. Everytime I highlight and select recovery the phone just shows up the "Google" logo, then vibrates, then back fastboot USB.
3. Factory Reset not working, again shows up "Google" then restarts to fastboot usb mode.
4. I ran cmd in sdk-tools, typed in "fastboot devices", and my phone is detected. But when I type "adb devices", my phone is not listed.
5. I tried flashing CWM or TWRP through fastboot in cmd but the reply is"remote: signature verify fail", as wellas flashing a RUU for my device.
6. On bootloader is written:
*** TAMPERED ***
*** RELOCKED ***
M7_UK PVT SHIP S-ON RH
HBOOT-1.54.0000
RADIO-4A.17.3250.14
OpenDSP-v30.120.3274.0520
OS-2.14.1700.15
eMMC-boot 2048MB
Guys I really badly need help to fix my phone. I don't wanna spend for repairs or throw it in the garbage. I am very sure there's a way to fix this and get it to work, but I am rookie in android as I've been an iOs user for a couple of years.
ClydeWinux said:
Hey guys I badly need help!!! I was able to convert my HTC One GSM to Google Edition just last week, but today I want to restore it to its factory ROM so I can also restore the warranty. Now the problem became visible when I tried to flash a stock ROM (not the GPE ROM). Listed below are the problems I am facing at the moment:
1. Stuck in FASTBOOT USB, and cannot boot to ROM.
2. Can't boot to recovery. Everytime I highlight and select recovery the phone just shows up the "Google" logo, then vibrates, then back fastboot USB.
3. Factory Reset not working, again shows up "Google" then restarts to fastboot usb mode.
4. I ran cmd in sdk-tools, typed in "fastboot devices", and my phone is detected. But when I type "adb devices", my phone is not listed.
5. I tried flashing CWM or TWRP through fastboot in cmd but the reply is"remote: signature verify fail", as wellas flashing a RUU for my device.
6. On bootloader is written:
*** TAMPERED ***
*** RELOCKED ***
M7_UK PVT SHIP S-ON RH
HBOOT-1.54.0000
RADIO-4A.17.33250.14
OpenDSP-v30.120.3274.0520
OS-2.14.1700.15
eMMC-boot 2048MB
Guys I really badly need help to fix my phone. I don't wanna spend for repairs or throw it in the garbage. I am very sure there's a way to fix this and get it to work, but I am rookie in android as I've been an iOs user for a couple of years.
Click to expand...
Click to collapse
try flashing the appropriate firmware files for an particular RUU before flashing RUU n check?
Harish_Kumar said:
try flashing the appropriate firmware files for an particular RUU before flashing RUU n check?
Click to expand...
Click to collapse
Yes I have tried flashing the appropriate RUU file but in CMD it returns "remote: signature verify fail"
ClydeWinux said:
Yes I have tried flashing the appropriate RUU file but in CMD it returns "remote: signature verify fail"
Click to expand...
Click to collapse
not RUU...i am talking about firmware files
for instance if you are about to flash an 4.3 sense 3.22 rom..flash its firmware in RUU mode before flashing the actual RUU
Harish_Kumar said:
not RUU...i am talking about firmware files
for instance if you are about to flash an 4.3 sense 3.22 rom..flash its firmware in RUU mode before flashing the actual RUU
Click to expand...
Click to collapse
Oh my, are the firmware files included inside the RUU.zip? or should I download the firmware files separately? @Harish_Kumar
ClydeWinux said:
Oh my, are the firmware files included inside the RUU.zip? or should I download the firmware files separately? @Harish_Kumar
Click to expand...
Click to collapse
RUU Zip will be encrypted..you cant extract files from it
you have to download firmware files seperately...you can find them in android development section
check here -> http://forum.xda-developers.com/showthread.php?t=2182823
I almost forgot... you should be S-off in order to flash the firmware
and even RUU Flashing requires S-off
Harish_Kumar said:
RUU Zip will be encrypted..you cant extract files from it
you have to download firmware files seperately...you can find them in android development section
check here -> http://forum.xda-developers.com/showthread.php?t=2182823
I almost forgot... you should be S-off in order to flash the firmware
and even RUU Flashing requires S-off
Click to expand...
Click to collapse
Ok I have flashed the firmware for my phone and now it's on 3.58.1700.5. Should I download a RUU.zip version 3.58.1700.5 and flash it on my phone? because until now I can't flash CWM or TWRP. @Harish_Kumar
ClydeWinux said:
Ok I have flashed the firmware for my phone and now it's on 3.58.1700.5. Should I download a RUU.zip version 3.58.1700.5 and flash it on my phone? because until now I can't flash CWM or TWRP. @Harish_Kumar
Click to expand...
Click to collapse
arent you able to flash custom recovery like CWM or TWRP even after flashing firmware files? if everything's right you should be able to
56562336461
Harish_Kumar said:
arent you able to flash custom recovery like CWM or TWRP even after flashing firmware files? if everything's right you should be able to
Click to expand...
Click to collapse
Everytime I tried to flash custom recovery (CWM/TWRP) in cmd it returns "remote: signature verify fail", I used command "fastboot flash recovery cwm.img". And now I tried to load up recovery from menu, and it's stuck on a 'dead-android-icon-with-exclamation-error' logo. @Harish_Kumar
Hi. I have been searching for two days on how to restore my phone to a stock Rom. I flashed some lame Rom that I can't remember the name of (has a blue firebird boot screen...) and now that's the only Rom I can flash. I tried many rims but haven't had any luck. I know the lame Rom I flashed made me first flash a boot image. I trtried reflashing a stock boot image but it doesn't help. The stock roms succeed but stay stuck on the lock screen totally unresponsive except for the power button to hard reset... I'm trying to get S-Off with FireWire but it fails saying that it cannot s-Off my device. Cannot RUU since I'm s-on and have no clue what to do.
The boot loader reads that the O.S. is version 4.19.531.10 but I currently have no O.S. installed since I wiped.
The boot loader is version 1.56 and it's a T-Mobile USA version.
ADB Sideload works but the install is faulty as described.
Thanks.
OfficialLocdoGg said:
Hi. I have been searching for two days on how to restore my phone to a stock Rom. I flashed some lame Rom that I can't remember the name of (has a blue firebird boot screen...) and now that's the only Rom I can flash. I tried many rims but haven't had any luck. I know the lame Rom I flashed made me first flash a boot image. I trtried reflashing a stock boot image but it doesn't help. The stock roms succeed but stay stuck on the lock screen totally unresponsive except for the power button to hard reset... I'm trying to get S-Off with FireWire but it fails saying that it cannot s-Off my device. Cannot RUU since I'm s-on and have no clue what to do.
The boot loader reads that the O.S. is version 4.19.531.10 but I currently have no O.S. installed since I wiped.
The boot loader is version 1.56 and it's a T-Mobile USA version.
ADB Sideload works but the install is faulty as described.
Thanks.
Click to expand...
Click to collapse
update your recovery to 2.6.3.3 and flash your rom again.
Code:
fastboot flash recovery name_of_recovery.img
fastboot erase cache
fastboot reboot-bootloader
you can also use the latest RUU.exe which will restore your phone back to stock and updated to the latest version. (better option imo)
http://www.htc1guru.com/dld/ruu_m7_..._10-33e-1718-01l_release_387953_signed_2-exe/
I'm going to try to update the recovery first because when I try to relock the bootloader even after flashing stock recovery it just boots to the bootloader even with a rom installed. (Even if its the erroring stock rom)
alray said:
update your recovery to 2.6.3.3 and flash your rom again.
Code:
fastboot flash recovery name_of_recovery.img
fastboot erase cache
fastboot reboot-bootloader
you can also use the latest RUU.exe which will restore your phone back to stock and updated to the latest version. (better option imo)
http://www.htc1guru.com/dld/ruu_m7_..._10-33e-1718-01l_release_387953_signed_2-exe/
Click to expand...
Click to collapse
OfficialLocdoGg said:
I'm going to try to update the recovery first because when I try to relock the bootloader even after flashing stock recovery it just boots to the bootloader even with a rom installed. (Even if its the erroring stock rom)
Click to expand...
Click to collapse
its fine to flash a ruu with phone booted in bootloader btw.
alray said:
its fine to flash a ruu with phone booted in bootloader btw.
Click to expand...
Click to collapse
Okay well I'm having no luck. Trying to flash the RUU wont work and updating the recovery didn't work. The ruu just hangs at 5% Checking headers. I tried extracting the rom.zip from the ruu but I get the invalid size crap and when trying to open the rom.zip it gives me an invalid error. I don't know what to do here.
OfficialLocdoGg said:
Okay well I'm having no luck. Trying to flash the RUU wont work and updating the recovery didn't work. The ruu just hangs at 5% Checking headers. I tried extracting the rom.zip from the ruu but I get the invalid size crap and when trying to open the rom.zip it gives me an invalid error. I don't know what to do here.
Click to expand...
Click to collapse
Let try this using the version just above your base version:
Download, rename to firmware.zip and place in your adb/fastboot folder: firmware 5.14.531.1
Boot into bootloader/FASTBOOT USB
Type:
Code:
[B][I]fastboot oem lock[/I][/B]
Type:
Code:
[B][I]fastboot oem rebootRUU [/I][/B]
NOTE: You should see a silver HTC logo come up on your phone after executing this command.
NOTE: if this command freezes, just disconnect the USB cable and hold the power and volume down buttons until the device reboots. Then, repeat the steps above again.
Finally:
Code:
[B][I]fastboot flash zip firmware.zip[/I][/B]
Repeat the same command: IMPORTANT
Code:
[B][I]fastboot flash zip firmware.zip[/I][/B]
NOTE: The green bar on the phone may not go to 100% of the bar ... but If you see completed on your computer command window, wait for a few seconds and move on.
Last Step:
Code:
[B][I]fastboot reboot[/I][/B]
Click to expand...
Click to collapse
Now run this RUU 5.14.531.1
If this is successful you can try to achieve S-OFF with firewater. Of course, you will need to unlock your bootloader and install TWRP 2.6.3.3 recovery. Or, you can retry the RUU in alray's post.
majmoz said:
Let try this using the version just above your base version:
Download, rename to firmware.zip and place in your adb/fastboot folder: firmware 5.14.531.1
Now run this RUU 5.14.531.1
If this is successful you can try to achieve S-OFF with firewater. Of course, you will need to unlock your bootloader and install TWRP 2.6.3.3 recovery. Or, you can retry the RUU in alray's post.
Click to expand...
Click to collapse
Thanks. This restored the phone to a usable state. I'm going to try firewater now.
Hi guys i got an htc one in placw of my samsung grand
I managed to unlock the bootloader using cmd and tried flashing a recovery. However after the flash when i try booting into recovery mode from bootloader, it first gives the entering recovery screen but then screen blacks out and then it reboots as normal.
Now htc just got a lollipop update and i want to update, but when it enters recovery, it blacks out and then reboots as normal due to the fail recovery
Before i tried flashing each and every reocvery and the same happened... Then i just left it at a version of cwm ( didnt work also) .
Now shall i flash stock recovery? What if that dosent work? Is there any way to do it without a pc or any other computer?
arushawasthi said:
Hi guys i got an htc one in placw of my samsung grand
I managed to unlock the bootloader using cmd and tried flashing a recovery. However after the flash when i try booting into recovery mode from bootloader, it first gives the entering recovery screen but then screen blacks out and then it reboots as normal.
Now htc just got a lollipop update and i want to update, but when it enters recovery, it blacks out and then reboots as normal due to the fail recovery
Before i tried flashing each and every reocvery and the same happened... Then i just left it at a version of cwm ( didnt work also) .
Now shall i flash stock recovery? What if that dosent work? Is there any way to do it without a pc or any other computer?
Click to expand...
Click to collapse
no .. you will need a PC to restore stock recovery / or RUU back to stock
Darn
clsA said:
no .. you will need a PC to restore stock recovery / or RUU back to stock
Click to expand...
Click to collapse
Hi,
Thanks for the reply.
I tried RUU, turns out theres no file for my cid (HTC_039).
I also tried alternate methods, turns out i cant use Guru reset as i need functioning recovery, and i have S-ON so no Nand.
pl help.
arushawasthi said:
Hi,
Thanks for the reply.
I tried RUU, turns out theres no file for my cid (HTC_039).
I also tried alternate methods, turns out i cant use Guru reset as i need functioning recovery, and i have S-ON so no Nand.
pl help.
Click to expand...
Click to collapse
Did you use the correct version of the recovery you flashed? I mean are you sure it wasn't a Sprint or Verizon recovery?
Secondly did you fastboot erase cache after flashing recovery?. This is the no.1 reason for recovery bootloop. Flashing recovery should be done like so.
Code:
fastboot erase cache
fastboot flash recovery "name-of-recovery".img
fastboot reboot-bootloader
Then select recovery from the bootloader for the first time load.
Sent from my M7 ARHD 84-Kitkat
arushawasthi said:
I tried RUU, turns out theres no file for my cid (HTC_039).
Click to expand...
Click to collapse
Yes there is one. 7.19.980.5 posted in the general section
http://forum.xda-developers.com/htc-one/general/lollipop-ruu-zip-small-collection-t3053944
see post #2.
If your phone is already on a 6.xx.980.x or 7.xx.980.x firmware you can flash it.
Danny201281 said:
Did you use the correct version of the recovery you flashed? I mean are you sure it wasn't a Sprint or Verizon recovery?
Secondly did you fastboot erase cache after flashing recovery?. This is the no.1 reason for recovery bootloop. Flashing recovery should be done like so.
Code:
fastboot erase cache
fastboot flash recovery "name-of-recovery".img
fastboot reboot-bootloader
Then select recovery from the bootloader for the first time load.
Sent from my M7 ARHD 84-Kitkat
Click to expand...
Click to collapse
Hi,
i didnt do the exact thing. Ill try like you said.
And how do i find out my firmware version? In settings?
arushawasthi said:
Hi,
i didnt do the exact thing. Ill try like you said.
And how do i find out my firmware version? In settings?
Click to expand...
Click to collapse
To find your firmware version it's best to use command
Code:
fastboot getvar all
this will show you a list of your devices version information.
You can post the list here if you need help but please remove your imei and serial number before posting for your own security.
There are 3 models of HTC One.
Sprint = m7_wls Downloads here http://techerrata.com/browse/twrp2/m7wls
Verizion = m7_vzw Downloads here http://techerrata.com/browse/twrp2/m7vzw
International = m7_ul or m7_u Downloads here http://techerrata.com/browse/twrp2/m7
There are also more model numbers for dual sim variants.
You must have the correct version of recovery depending on your model. The getvar info would be very helpful for me to make a recommendation :good:
Sent from my SM-T230 using Tapatalk