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.
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
Hey guys Im trying to fix my HTC One. I was on a call last night and the battery died and now it will only boot to fastboot. Problem is my Windows 8 box is not working with ADB. ADB does not see the device, but fastboot works. I try booting to twrp recovery and it just reboots to the HTC logo.
Can anyone help me out? I dont mind completely blasting it, but I dont want to waste a $600 phone.
Also good to note guys
piftoffpenguin said:
Hey guys Im trying to fix my HTC One. I was on a call last night and the battery died and now it will only boot to fastboot. Problem is my Windows 8 box is not working with ADB. ADB does not see the device, but fastboot works. I try booting to twrp recovery and it just reboots to the HTC logo.
Can anyone help me out? I dont mind completely blasting it, but I dont want to waste a $600 phone.
Click to expand...
Click to collapse
By the way at fastboot usb screen I have
*****Tampered*****
*****Unlocked*****
M7_UL PVT SHIP S-ON RH
HBOOT-1.44.0000
piftoffpenguin said:
By the way at fastboot usb screen I have
*****Tampered*****
*****Unlocked*****
M7_UL PVT SHIP S-ON RH
HBOOT-1.44.0000
Click to expand...
Click to collapse
adb doesnt work in fastboot mode;
Just flash the custom recovery again
fastboot flash recovery recovery-file-here.img
Thanks for the reply
darksnoopy said:
adb doesnt work in fastboot mode;
Just flash the custom recovery again
fastboot flash recovery recovery-file-here.img
Click to expand...
Click to collapse
I have tried this several times. I even tried to flash clockwork and a few different versions of twrp, and clear the cache and when I go to recovery it shows the Teamwin splash screen and then it reboots.
It says it transferred successfully, but even when I flashed clockwork I still see the Teamwin splash when entering recovery mode.
Image attached of successful flash
darksnoopy said:
adb doesnt work in fastboot mode;
Just flash the custom recovery again
fastboot flash recovery recovery-file-here.img
Click to expand...
Click to collapse
I just tried to flash clockwork as seen in the picture as well. Same issue, when I hit recovery, Teamwin splash and then it begins another endless reboot. Thanks again for the reply.
piftoffpenguin said:
I just tried to flash clockwork as seen in the picture as well. Same issue, when I hit recovery, Teamwin splash and then it begins another endless reboot. Thanks again for the reply.
Click to expand...
Click to collapse
hm i dont know if i can help anymore... but some steps to do
fastboot erase cache
then write the recovery again
again fastboot erase cache
reboot your device and then try to boot into recovery
else
flash stock recovery and then try again to flash custom recovery...
Last choice is to restore with a RUU
P.S If you dont have any luck flashing openrecovery-twrp-2.6.3.3-m7.img then try with this version:
openrecovery-twrp-2.6.3.0-m7.img
EDIT: twrp25.img???? i dont think this recovery is meant for htc one..you are flashing wrong version of twrp.... flash with the recoveries i mentioned above
Its correct - actually TWRP 2.5.0.0 renamed
darksnoopy said:
hm i dont know if i can help anymore... but some steps to do
fastboot erase cache
then write the recovery again
again fastboot erase cache
reboot your device and then try to boot into recovery
else
flash stock recovery and then try again to flash custom recovery...
Last choice is to restore with a RUU
P.S If you dont have any luck flashing openrecovery-twrp-2.6.3.3-m7.img then try with this version:
openrecovery-twrp-2.6.3.0-m7.img
EDIT: twrp25.img???? i dont think this recovery is meant for htc one..you are flashing wrong version of twrp.... flash with the recoveries i mentioned above
Click to expand...
Click to collapse
That's just the filename that I renamed TWRP 2.5.0.0 to for a simpler command.
I found the problem but dont know how to fix it. My device is in Fastboot which means no ADB. Also without being able to boot I can't change that (at least I dont think I can.).
Anyhow the damned thing re-engaged S-ON and its blocking access to the NAND (even if its saying it wrote to it, it can't be because of S-ON).
How do I RUU?
HTC One M7 Tmobile.
Thanks for the info sir. Much appreciated.
piftoffpenguin said:
That's just the filename that I renamed TWRP 2.5.0.0 to for a simpler command.
I found the problem but dont know how to fix it. My device is in Fastboot which means no ADB. Also without being able to boot I can't change that (at least I dont think I can.).
Anyhow the damned thing re-engaged S-ON and its blocking access to the NAND (even if its saying it wrote to it, it can't be because of S-ON).
How do I RUU?
HTC One M7 Tmobile.
Thanks for the info sir. Much appreciated.
Click to expand...
Click to collapse
type
fastboot getvar all
post here without your imei and serial number
Getvar
darksnoopy said:
type
fastboot getvar all
post here without your imei and serial number
Click to expand...
Click to collapse
C:\Users\cwatson\Desktop\FASTBOOT>fastboot getvar all
INFOversion: 0.5
INFOversion-bootloader: 1.44.0000
INFOversion-baseband: 4A.14.3250.15
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main: 1.27.531.7
INFOversion-misc: PVT SHIP S-ON
INFOserialno:
INFOimei:
INFOmeid: 00000000000000
INFOproduct: m7_ul
INFOplatform: HBOOT-8064
INFOmodelid: PN0713000
INFOcidnum: T-MOB010
INFObattery-status: good
INFObattery-voltage: 4330mV
INFOpartition-layout: Generic
INFOsecurity: on
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.047s
This is the RUU for your phone ruu_m7_ul_jb_50_tmous_1-27-531-11_radio_4a-17-3250-20_10-40-1150-04_release_324846_signed-exe
you can find it at htc1guru but to use it you must relock your bootloader and i wouldnt advice it cause of this error
piftoffpenguin said:
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.047s
Click to expand...
Click to collapse
I dont want to risk to brick your device so it would be better to post your problem at the Tmobile htc one forum at xda here
http://forum.xda-developers.com/htc-one-tmobile/help
Unlock can I relock
darksnoopy said:
This is the RUU for your phone ruu_m7_ul_jb_50_tmous_1-27-531-11_radio_4a-17-3250-20_10-40-1150-04_release_324846_signed-exe
you can find it at htc1guru but to use it you must relock your bootloader and i wouldnt advice it cause of this error
I dont want to risk to brick your device so it would be better to post your problem at the Tmobile htc one forum at xda here
http://forum.xda-developers.com/htc-one-tmobile/help
Click to expand...
Click to collapse
If I unlock my bootloader can I relock in without ADB access and S-on or will that be a one way street??
piftoffpenguin said:
If I unlock my bootloader can I relock in without ADB access and S-on or will that be a one way street??
Click to expand...
Click to collapse
bootloader unlocking happens in fastboot with fastboot flash unlocktoken unlock_code.bin so no you dont need adb
Are you locked or unlocked right now?
Unlocked
darksnoopy said:
bootloader unlocking happens in fastboot with fastboot flash unlocktoken unlock_code.bin so no you dont need adb
Are you locked or unlocked right now?
Click to expand...
Click to collapse
I'm unlocked and have my unlock_code.bin as well saved.
piftoffpenguin said:
I'm unlocked and have my unlock_code.bin as well saved.
Click to expand...
Click to collapse
if you want to lock it and try to run the RUU give the command fastboot oem lock but i would not advice it and i take no responibility since i dont have a tmobile phone. I recommend to post on tmobile forum for help
Tried RUU
darksnoopy said:
if you want to lock it and try to run the RUU give the command fastboot oem lock but i would not advice it and i take no responibility since i dont have a tmobile phone. I recommend to post on tmobile forum for help
Click to expand...
Click to collapse
I tried the RUU you recommended. It said RUU ERROR 171 USB Connection Error. I can send it fastboot commands manually and the RUU sees its Rom version and requests the upgrade and reboots, but it then bombs. It also would not let me relock giving the following error:
... INFOLock successfully...
INFOmipi display off
INFOmipi_dsi_cmds_tx_ext
INFOpm8921_vreg_disable function, vreg_id = 38
INFOpm8921_vreg_disable function, vreg_id = 1
INFOTZ_HTC_SVC_DISABLE ret = 534642044 (0x1FDDFD7C)
INFOUse PSHOLD to reset device.
FAILED (status read failed (No such file or directory))
finished. total time: 1.158s
Is this device finished or is there anything else I can do?
Trying this now
Reference:
http://forums.androidcentral.com/ht...k-bootloader-cant-get-into-recovery-help.html
"when you have all that done open a cmd prompt and with the phone in fastboot usb mode type these cmd's
fastboot erase cache
fastboot erase userdata
fastboot erase system
fastboot reboot bootloader
fastboot oem rebootRUU
fastboot flash zip rom.zip
with the last cmd, if it comes back with a error about flushing or something like that just type the cmd again "
Dunno but I am at my wits end and do not know if the EPROM is even good now:
May have it beat finally
Crossing my fingers.
NOTE** This did not work earlier today despite MANY attempts.
I downloaded clockwork recovery to my fastboot computer folder.
I renamed it to recovery.img.
I ran fastboot boot recovery.img and I got clockwork.
I found the Viper ROM I installed months ago.
It ran the install.
Now it rebooted and I got endless reboot again lol ****E! Curse you and your S-On HTC!!!!
piftoffpenguin said:
Crossing my fingers.
NOTE** This did not work earlier today despite MANY attempts.
I downloaded clockwork recovery to my fastboot computer folder.
I renamed it to recovery.img.
I ran fastboot boot recovery.img and I got clockwork.
I found the Viper ROM I installed months ago.
It ran the install.
Now it rebooted and I got endless reboot again lol ****E! Curse you and your S-On HTC!!!!
Click to expand...
Click to collapse
Simple, s-off your device.
Sent from my HTC One using Tapatalk
Restore factory settings and wipe cache and dalvik cache and flash the rom again
How
xcrazydx said:
Simple, s-off your device.
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
How do I s-off the device when Adb commmands are not working and an RUU isnt even working?
Hi All,
I'm a noob when it comes to this stuff, but I've learned a lot over the last day. I soft bricked my HTC One Developer Edition while trying to do the most recent OTA update to 4.4.
What happens:
When booting normally, it goes initially to the normal white HTC screen, then to a "pink" screen (it's mostly pink, but it's really just messed up graphics), then goes to the HTC One loading screen (except BEATS is blue instead of red). Then it just freezes on that loading screen.
I can boot into the bootloader and recovery (currently TWRP, but was stock when doing the OTA update)
What I've tried:
I've used Fastboot to flash TWRP, so that part is good. Within TWRP, I've wiped the cache, system, Dalvik.
I've tried using Fastboot to flash the RUU Zip file (first one in the list here) in both Windows and OSX, while in "FASTBOOT USB" mode and in RUU mode. Each time, it starts sending, but around 43-44 secs it fails with "remote:not allowed: For reference, the top of the bootloader screen says TAMPERED, then UNLOCKED. I'm running HBOOT 1.55 and have S-ON (but unlocked bootloader). OS shows 3.22.1540.1
I can't get past the remote:not allowed issue, and I'm not such an expert to know what to try next. Can anyone please give me some tips on what to do next? I've tried searching, but I don't know what exactly to search for.
Thank you all!
awer25 said:
Hi All,
I'm a noob when it comes to this stuff, but I've learned a lot over the last day. I soft bricked my HTC One Developer Edition while trying to do the most recent OTA update to 4.4.
What happens:
When booting normally, it goes initially to the normal white HTC screen, then to a "pink" screen (it's mostly pink, but it's really just messed up graphics), then goes to the HTC One loading screen (except BEATS is blue instead of red). Then it just freezes on that loading screen.
I can boot into the bootloader and recovery (currently TWRP, but was stock when doing the OTA update)
What I've tried:
I've used Fastboot to flash TWRP, so that part is good. Within TWRP, I've wiped the cache, system, Dalvik.
I've tried using Fastboot to flash the RUU Zip file (first one in the list here) in both Windows and OSX, while in "FASTBOOT USB" mode. Each time, it starts sending, but around 43-44 secs it fails with "remote:not allowed: For reference, the top of the bootloader screen says TAMPERED, then UNLOCKED. I'm running HBOOT 1.55 and have S-ON (but unlocked bootloader). OS shows 3.22.1540.1
I can't get past the remote:not allowed issue, and I'm not such an expert to know what to try next. Can anyone please give me some tips on what to do next? I've tried searching, but I don't know what exactly to search for.
Thank you all!
Click to expand...
Click to collapse
Please post the output of ''fastboot getvar all'' minus your IMEI and serial no. And please post the commands your were using to flash the ruu.zip or a screenshot of your command prompt
alray said:
Please post the output of ''fastboot getvar all'' minus your IMEI and serial no. And please post the commands your were using to flash the ruu.zip or a screenshot of your command prompt
Click to expand...
Click to collapse
Thanks! The command prompt was fastboot flash zip rom.zip (I renamed it to that). For TWRP it was fastboot flash recovery recovery.img
GETVAR is attached.
EDIT: I added the command prompt and fail as well.
awer25 said:
Thanks! The command prompt was fastboot flash zip rom.zip (I renamed it to that). For TWRP it was fastboot flash recovery recovery.img
GETVAR is attached.
Click to expand...
Click to collapse
ok, first you can't flash that ruu you linked above (first in the list) because its a decrypted ruu. Decrypted ruu.zip require s-off and you are s-on. Whit s-on you can only flash signed ruu.
and btw did you enter ruu mode before ''fastboot flash zip rom.zip'' ?
---------- Post added at 07:52 PM ---------- Previous post was at 07:51 PM ----------
awer25 said:
Thanks! The command prompt was fastboot flash zip rom.zip (I renamed it to that). For TWRP it was fastboot flash recovery recovery.img
GETVAR is attached.
EDIT: I added the command prompt and fail as well.
Click to expand...
Click to collapse
There is a 3.22.1540.1 RUU.exe on htcdev.com you could use to restore your phone. But it will not work using windows 8.1. what is your computer OS?
alray said:
ok, first you can't flash that ruu you linked above (first in the list) because its a decrypted ruu. Decrypted ruu.zip require s-off and you are s-on. Whit s-on you can only flash signed ruu.
and btw did you enter ruu mode before ''fastboot flash zip rom.zip'' ?
Thank you for that explanation. I got into RUU mode by doing fastboot oem rebootRUU, which took me to a black screen with silver HTC. That may not be RUU mode...I'm just guessing.
---------- Post added at 07:52 PM ---------- Previous post was at 07:51 PM ----------
There is a 3.22.1540.1 RUU.exe on htcdev.com you could use to restore your phone. But it will not work using windows 8.1. what is your computer OS?
edit: Wait, there is also a 3.22.1540.1 ruu.zip on htcdev.com so try it first.
fastboot oem rebootRUU
fastboot flash zip <name_of_file>.zip
fastboot flash zip <name_of_file>.zip
fastboot reboot
Click to expand...
Click to collapse
Amazing! Thanks - I'll try this and let you know how it goes. I have Windows 8.1, but with fastboot and a zip file it should work, right? If not, I have a Windows 7 laptop at home.
awer25 said:
Amazing! Thanks - I'll try this and let you know how it goes. I have Windows 8.1, but with fastboot and a zip file it should work, right? If not, I have a Windows 7 laptop at home.
Click to expand...
Click to collapse
yes ruu.zip should work flawlessly with windows 8.1. but do not attempt the ruu.exe with 8.1, will work fine on 7.
alray said:
yes ruu.zip should work flawlessly with windows 8.1. but do not attempt the ruu.exe with 8.1, will work fine on 7.
Click to expand...
Click to collapse
I saw that I already had the 3.22.1540.1 zip file on my computer, so I tried. It got a lot further, but still failed with a remote:not allowed (see attached pic).
My next tries will be to re-download the file and try again, and if that fails, to try the RUU.exe file on the Windows 7 laptop. Is this correct, or is there something else I should try?
I'm leaving work now, so I won't be able to answer for another hour or so but thank you for your help thus far!
awer25 said:
I saw that I already had the 3.22.1540.1 zip file on my computer, so I tried. It got a lot further, but still failed with a remote:not allowed (see attached pic).
My next tries will be to re-download the file and try again, and if that fails, to try the RUU.exe file on the Windows 7 laptop. Is this correct, or is there something else I should try?
I'm leaving work now, so I won't be able to answer for another hour or so but thank you for your help thus far!
Click to expand...
Click to collapse
the ruu you have from the link you posted above is DECRYPTED it will not work with s-on!!!
alray said:
ok, first you can't flash that ruu you linked above (first in the list) because its a decrypted ruu. Decrypted ruu.zip require s-off and you are s-on.
Click to expand...
Click to collapse
And does the phone was in ruu mode? I don't see any ''fastboot oem rebootRUU'' from your screenshot...
alray said:
the ruu you have from the link you posted above is DECRYPTED it will not work with s-on!!!
And does the phone was in ruu mode? I don't see any ''fastboot oem rebootRUU'' from your screenshot...
Click to expand...
Click to collapse
Sorry I didn't explain better - the file I meant was the one from HTCDevs - I downloaded it a while ago when I had a different issue. I just renamed it to rom1 or whatever. Is this then the correct file?
Also, the phone was not in RUU mode - it was in regular fastboot mode ("FASTBOOT USB"). I'll try again in RUU mode.
awer25 said:
Sorry I didn't explain better - the file I meant was the one from HTCDevs - I downloaded it a while ago when I had a different issue. I just renamed it to rom1 or whatever. Is this then the correct file?
Also, the phone was not in RUU mode - it was in regular fastboot mode ("FASTBOOT USB"). I'll try again in RUU mode.
Click to expand...
Click to collapse
you can not flash ruu with fastboot. you MUST reboot phone in ruu mode using ''fastboot oem rebootRUU'' it will then reboot with a black screen and the htc logo. so:
Code:
fastboot oem rebootRUU
fastboot flash zip name_of_ruu.zip
fastboot flash zip name_of_ruu.zip <------ yes again!
fastboot reboot
When in ruu mode you'll have a screen similar to this:
then proceed with ''fastboot flash zip...................''
alray said:
you can not flash ruu with fastboot. you MUST reboot phone in ruu mode using ''fastboot oem rebootRUU'' it will then reboot with a black screen and the htc logo. so:
Code:
fastboot oem rebootRUU
fastboot flash zip name_of_ruu.zip
fastboot flash zip name_of_ruu.zip <------ yes again!
fastboot reboot
When in ruu mode you'll have a screen similar to this:
then proceed with ''fastboot flash zip...................''
Click to expand...
Click to collapse
Ok, I booted into RUU mode and flashed the file twice as per your instructions. Both times it failed. Screenshot is attached. (I even tried it a 3rd time but it still failed with the same message)
Also, I renamed the zip file to rom1.zip just to make typing it easier, but it is the file from HTCDevs, "3.22.1540.1 Developer Edition", Zip (not RUU).
Thank you!
awer25 said:
Ok, I booted into RUU mode and flashed the file twice as per your instructions. Both times it failed. Screenshot is attached. (I even tried it a 3rd time but it still failed with the same message)
Also, I renamed the zip file to rom1.zip just to make typing it easier, but it is the file from HTCDevs, "3.22.1540.1 Developer Edition", Zip (not RUU).
Thank you!
Click to expand...
Click to collapse
Try the ruu.exe on windows 7.
alray said:
Try the ruu.exe on windows 7.
Click to expand...
Click to collapse
Ok, I tried it on the Windows 7 laptop and got another error (155 - unknown error). Pic is attached. It was in RUU mode btw.
I'm currently downloading the older 1.29.xx version (Android 4.1) and will try again with that.
Just for my own knowledge - how many "parts" (partitions?) of the system are there? As in, there's the recovery partition, the "main" ROM, etc. Are those the only two? I only ask because I wonder if I messed up something in another part that makes the phone think it's not the Developer Edition? (the errors seem to point to using the wrong image, but I got it directly from HTCDevs and have now tried both the RUU and Zip versions.
awer25 said:
Ok, I tried it on the Windows 7 laptop and got another error (155 - unknown error). Pic is attached. It was in RUU mode btw.
I'm currently downloading the older 1.29.xx version (Android 4.1) and will try again with that.
Just for my own knowledge - how many "parts" (partitions?) of the system are there? As in, there's the recovery partition, the "main" ROM, etc. Are those the only two? I only ask because I wonder if I messed up something in another part that makes the phone think it's not the Developer Edition? (the errors seem to point to using the wrong image, but I got it directly from HTCDevs and have now tried both the RUU and Zip versions.
Click to expand...
Click to collapse
I got it! I had to relock my bootloader for some reason. Then, the Windows RUU installed fine.
Thank you alray for your help!
Is being stuck at the booting screen (Htc one with beats audio (red color)) same as this scenario ? Is it soft bricked or boot looped or what's it called?
I'm S-off, rooted, stock rom, hboot is 1.56 w/ CWM. At some point the phone just rebooted on its own (I was even in a different place at that time!!!) and got stuck forever at that screen. Rebooting would just make it get stuck there again. bootloader, custom recovery all work.
what do?
-marco- said:
Is being stuck at the booting screen (Htc one with beats audio (red color)) same as this scenario ? Is it soft bricked or boot looped or what's it called?
I'm S-off, rooted, stock rom, hboot is 1.56 w/ CWM. At some point the phone just rebooted on its own (I was even in a different place at that time!!!) and got stuck forever at that screen. Rebooting would just make it get stuck there again. bootloader, custom recovery all work.
what do?
Click to expand...
Click to collapse
Mine did get stuck there, but after a weird messed up pink screen (and the Beats text was blue, not red for some reason). If I was in your boat, I'd just flash a fresh rom and be done.
awer25 said:
Mine did get stuck there, but after a weird messed up pink screen (and the Beats text was blue, not red for some reason). If I was in your boat, I'd just flash a fresh rom and be done.
Click to expand...
Click to collapse
thanks !
but which one? And how?
also getvar !
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.23.3263.28
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.20.707.6
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0714000
(bootloader) cidnum: HTC__044
(bootloader) battery-status: good
(bootloader) battery-voltage: 3867mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-59adc32b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.066s
-marco- said:
thanks !
but which one? And how?
also getvar !
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.23.3263.28
(bootloader) version-main: 4.20.707.6
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) product: m7_ul
(bootloader) modelid: PN0714000
(bootloader) cidnum: HTC__044
finished. total time: 0.066s
Click to expand...
Click to collapse
-marco- said:
I am at work in the office and at some point I look at my phone and I see it rebooted on its own. now it's stuck forever on the HTC one beats audio loading screen.
I didn't even touch anything before. Tried to reboot but it just gets stuck there.
Click to expand...
Click to collapse
1- Please also post a screenshot of bootloader.
2- So you're on completely stock ROM?
3- are you able to enter recovery?
4- have you simply tried "fastboot erase cache" and tried booting?
nkk71 said:
1- Please also post a screenshot of bootloader.
2- So you're on completely stock ROM?
3- are you able to enter recovery?
4- have you simply tried "fastboot erase cache" and tried booting?
Click to expand...
Click to collapse
Thanks man!
Let's get this started:
1- done, see attached.
2- yes, up to latest OTA but i was rooted.
3- yes , CWM
4- done, still gets stuck at the same screen.
now: million $ question - is there a way to get out of this stupid problem without having to lose any data at all ? one gets quite sick at having to wipe and restore backups everytime there's a booting problem with the phone. i remember with the SGS2 i just had to reflash with odin the rom i was using and boom, back in order!
-marco- said:
Thanks man!
Let's get this started:
1- done, see attached.
2- yes, up to latest OTA but i was rooted.
3- yes , CWM
4- done, still gets stuck at the same screen.
now: million $ question - is there a way to get out of this stupid problem without having to lose any data at all ? one gets quite sick at having to wipe and restore backups everytime there's a booting problem with the phone. i remember with the SGS2 i just had to reflash with odin the rom i was using and boom, back in order!
Click to expand...
Click to collapse
Well first I would recommend you update recovery to TWRP
2.6.3.3: http://techerrata.com/browse/twrp2/m7
or 2.6.3.4: http://techerrata.com/browse/twrp2/m7ul
since they are more compatible when flashing 4.4 ROMs (make sure to check MD5 on the files, that site doesn't play nice with download managers!)
Code:
[B]fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader[/B]
-> enter recovery
Second, in TWRP, make a nandroid backup, you may need it later *** (please check below)
Third, put a ROM on the phone (in custom recovery):
Code:
C:\ADB3>[B]adb devices[/B]
List of devices attached
HT34xxxxxxxx recovery <- you need to be in recovery
[B]adb push <name of rom>.zip /sdcard/[/B] <- this will take about 5 mins without any progress
and install the ROM, don't select WIPE during installation, and you should have your million $ question solved... all apps, data, etc should be there, but if you get apps crashing it's because of the "dirty-flash"
As to which ROMs you can use for the above procedure, there's is a 100% stock version of 4.19.401.9 here: http://forum.xda-developers.com/showthread.php?t=2224752
I'm personally using ARHD 52.0 from here: http://forum.xda-developers.com/showthread.php?t=2183023 (stock but with improvements, and rooted)
I haven't checked if there's a 100% stock 4.20.707.6 ROM around, so you could do some googling and see.
Hope that helps
*** once you've done the backup, you can try wiping "data, cache, dalvik", and then restore the nandroid... sometimes that works
if not keep the nandroid, as it has all the information, and you can use Nandroid Manager (in play store) to extract individual information, if need be.
Good Luck
I have a HTC ONE M7 that's locked with Bell Mobility, I recently bought off some guy who rooted it to android revolution hd 71.1 running 4.4.2 , I wanted to convert it back to stock, so I followed this tutorial.
"YOUTUBE VIDEO: How to Unroot/Unbrick the HTC One to Stock BY qbking77"
First of all, I'm a complete noob at this, I've been using iPhone prior and this is my first android. I'm unaware of what the difference is with OTA RUU and normal RUU.
When I followed that tutorial I had done every step up to entering the command prompt "fastboot oem lock" the phone reset and now I'm at bootloader, being the idiot I am, in the video the guy had some .exe file to open but in my file there isn't any (btw the OS is 3.23.66.1) the link I downloaded was this:
"SEARCH ON GOOGLE: 3.23.666.1 AND CLICK THIRD LINK FROM HTC1GURU.COM"
I've tried getting out of the bootloader, but it keeps returning to there, please help I'm very scared! I just want to get back to the way it was and just pay someone to get it back to normal.
EDIT: Currently the Bootloader says the following:
***TAMPERED***
***RELOCKED***
***Security Warning***
M7_UL PVT SHIP S-ON RH
HBOOT-1.55.0000
RADIO-4A.20.3263.16
OpenDSP-v32.120.274.0909
OS-3.23.666.1
eMMC-boot 2048MB
Sep 17, 2013, 23:36:49
H Boot
Vol Up
Vol Down
Power
FASTBOOT
RECOVERY
FACTORY RESET
SIMLOCK
IMAGE CRC
SHOW BARCODE
Rembokz said:
I have a HTC ONE M7 that's locked with Bell Mobility, I recently bought off some guy who rooted it to android revolution hd 71.1 running 4.4.2 , I wanted to convert it back to stock, so I followed this tutorial.
"YOUTUBE VIDEO: How to Unroot/Unbrick the HTC One to Stock BY qbking77"
First of all, I'm a complete noob at this, I've been using iPhone prior and this is my first android. I'm unaware of what the difference is with OTA RUU and normal RUU.
When I followed that tutorial I had done every step up to entering the command prompt "fastboot oem lock" the phone reset and now I'm at bootloader, being the idiot I am, in the video the guy had some .exe file to open but in my file there isn't any (btw the OS is 3.23.66.1) the link I downloaded was this:
"SEARCH ON GOOGLE: 3.23.666.1 AND CLICK THIRD LINK FROM HTC1GURU.COM"
I've tried getting out of the bootloader, but it keeps returning to there, please help I'm very scared! I just want to get back to the way it was and just pay someone to get it back to normal.
EDIT: Currently the Bootloader says the following:
***TAMPERED***
***RELOCKED***
***Security Warning***
M7_UL PVT SHIP S-ON RH
HBOOT-1.55.0000
RADIO-4A.20.3263.16
OpenDSP-v32.120.274.0909
OS-3.23.666.1
eMMC-boot 2048MB
Sep 17, 2013, 23:36:49
H Boot
Vol Up
Vol Down
Power
FASTBOOT
RECOVERY
FACTORY RESET
SIMLOCK
IMAGE CRC
SHOW BARCODE
Click to expand...
Click to collapse
unlock the bootloader again from htcdev.com
flash twrp recovery version 2.6.3.3
restore this backup with twrp
alray said:
unlock the bootloader again from
Click to expand...
Click to collapse
The 2nd link isn't working, it says "The disc image file is corrupted"
Rembokz said:
The 2nd link isn't working, it says "The disc image file is corrupted"
Click to expand...
Click to collapse
its not a disc image its a recovery. To flash it:
Code:
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
alray said:
its not a disc image its a recovery. To flash it:
Code:
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
Click to expand...
Click to collapse
So I have to put the HTC back into bootloader, and use command prompt to flash it?
Rembokz said:
So I have to put the HTC back into bootloader, and use command prompt to flash it?
Click to expand...
Click to collapse
yes boot your phone in bootloader mode / fastboot usb mode
with the recovery file in the same folder where you ahve adb and fastboot on your computer, open a command prompt:
Code:
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
alray said:
yes boot your phone in bootloader mode / fastboot usb mode
with the recovery file in the same folder where you ahve adb and fastboot on your computer, open a command prompt:
Code:
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
Click to expand...
Click to collapse
Okay, and for the final step, how do I proceed with restoring the backup with the other twrp? I apologize for being such a noob
Rembokz said:
Okay, and for the final step, how do I proceed with restoring the backup with the other twrp? I apologize for being such a noob
Click to expand...
Click to collapse
boot the phone in twrp recovery
select "backup"
select "boot" only
Swipe to Back Up
reboot in android
from your computer go in the phone storage:
HTC One\Internal storage\TWRP\BACKUPS\YOUR_SERIAL_NUMBER\TODAY'S_DATE\
delete all files in that folder (your backup of boot) extract the backup zip file and place all files there
reboot in twrp
select restore
select the backup
swipe to restore
reboot
@Rembokz Any news? Is your phone booting to the stock rom now?
If yes, you'll also have to flash the stock recovery as the last step if you want to install updates.
alray said:
@Rembokz Any news? Is your phone booting to the stock rom now?
If yes, you'll also have to flash the stock recovery as the last step if you want to install updates.
Click to expand...
Click to collapse
Yes it works! I managed to access google play store, activate my google account, and download apps, all of which I couldn't do before. By flashing the stock recovery, does that mean I have to do that in order to make software updates such as Android Lollipop in the future? BTW, Thank you so much!
Rembokz said:
Yes it works! I managed to access google play store, activate my google account, and download apps, all of which I couldn't do before.
Click to expand...
Click to collapse
:good:
By flashing the stock recovery, does that mean I have to do that in order to make software updates such as Android Lollipop in the future?
Click to expand...
Click to collapse
Yes and there are already newer versions than 3.23.666.1 so you should be able to update it after flashing the stock recovery.
The recovery file you need is here
save it in the same folder where you have adb and fastboot on your computer
reboot in bootloader/fastboot usb mode
Code:
fastboot flash recovery recovery_3.23.666.1.img
fastboot erase cache
fastboot reboot
then:
Settings --> About --> Software update --> Check now
Latest version for your phone should be 6.XX.666.X with HTC Sense 6 and Android 4.4.3 (there should be more than 1 update so repeat the same process after each update until it says: Your phone is up to date / There are no updates available for your phone)
Lollipop is expected to be released early 2015
BTW, Thank you so much!
Click to expand...
Click to collapse
you're welcome
alray said:
@Rembokz Any news? Is your phone booting to the stock rom now?
If yes, you'll also have to flash the stock recovery as the last step if you want to install updates.
Click to expand...
Click to collapse
alray said:
:good:
Yes and there are already newer versions than 3.23.666.1 so you should be able to update it after flashing the stock recovery.
The recovery file you need is here
save it in the same folder where you have adb and fastboot on your computer
reboot in bootloader/fastboot usb mode
Code:
fastboot flash recovery recovery_3.23.666.1.img
fastboot erase cache
fastboot reboot
then:
Settings --> About --> Software update --> Check now
Latest version for your phone should be 6.XX.666.X with HTC Sense 6 and Android 4.4.3 (there should be more than 1 update so repeat the same process after each update until it says: Your phone is up to date / There are no updates available for your phone)
Lollipop is expected to be released early 2015
you're welcome
Click to expand...
Click to collapse
Hey man I've gotten into some trouble, I got the update downloaded, called 4.19.666.8 and when I tried to install it it takes me to the blue menu TWRP and from there I don't know what to do.
Rembokz said:
Hey man I've gotten into some trouble, I got the update downloaded, called 4.19.666.8 and when I tried to install it it takes me to the blue menu TWRP and from there I don't know what to do.
Click to expand...
Click to collapse
You can't install updates with twrp recovery hence why I told you to flash the stock recovery in my last post
just hold power and volume down until you are back in the bootloader then flash the stock recovery
once the stock recovery is flashed reboot to android and re-check for updates.
alray said:
You can't install updates with twrp recovery hence why I told you to flash the stock recovery in my last post
just hold power and volume down until you are back in the bootloader then flash the stock recovery
once the stock recovery is flashed reboot to android and re-check for updates.
Click to expand...
Click to collapse
Oh I found out the problem, the link added in a .exe file which resulted in the bootloader not working woops. Okay after update, I got the software update 4.19.666.8, I made sure I did the command prompt right, this is correct right?:
C:\android-sdk>fastboot flash recovery recovery_3.23.666.1.img
target reported max download size of 1526722560 bytes
sending 'recovery' (11958 KB)...
OKAY [ 1.438s]
writing 'recovery'...
OKAY [ 0.935s]
finished. total time: 2.373s
C:\android-sdk>fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.559s]
finished. total time: 0.561s
C:\android-sdk>fastboot reboot
rebooting...
finished. total time: 0.035s
C:\android-sdk>
Click to expand...
Click to collapse
Rembokz said:
Oh I found out the problem, the link added in a .exe file which resulted in the bootloader not working woops. Okay after update, I got the software update 4.19.666.8, I made sure I did the command prompt right, this is correct right?:
Click to expand...
Click to collapse
everything seems right. You can apply each updates one by one, the latest one shoulb be 6.xx.666.xx.
alray said:
everything seems right. You can apply each updates one by one, the latest one shoulb be 6.xx.666.xx.
Click to expand...
Click to collapse
The thing is is that it says I have no more updates available, despite it only being updated to 5.11.666.8
Maybe 5.xx.666.x is the latest for Bell...
alray said:
Maybe 5.xx.666.x is the latest for Bell...
Click to expand...
Click to collapse
Well, I hope so, thanks so much for your help! I just have one last question, do I ever need to flash ever again in order to get future updates? Or will I just have to scan for updates and update from there?
Rembokz said:
Well, I hope so, thanks so much for your help! I just have one last question, do I ever need to flash ever again in order to get future updates? Or will I just have to scan for updates and update from there?
Click to expand...
Click to collapse
alray said:
Maybe 5.xx.666.x is the latest for Bell...
Click to expand...
Click to collapse
It actually is
http://support.bell.ca/Mobility/Smartphones_and_mobile_internet/Operating-Systems?alias=HTC-One
Rembokz said:
Well, I hope so, thanks so much for your help! I just have one last question, do I ever need to flash ever again in order to get future updates? Or will I just have to scan for updates and update from there?
Click to expand...
Click to collapse
You will receive a notification when there will be an update available. No need to flash anything