Related
This method worked great for the HTC EVO 4G LTE. See this thread for more information. I haven't actually tested this exact method listed below for the HTC One but I did it almost identical to this. The only difference is I used a different hboot on my phone. Anyone that tries it please let me know if it works.
First and foremost, a few disclaimers.
USE AT YOUR OWN RISK. IT MAY OR MAY NOT WORK WITH THE ENGINEERING HBOOT AS I HAVE NOT TESTED IT WITH THAT HBOOT.
YOU MUST BE S-OFF FOR THIS TO WORK. PLEASE DO NOT TRY THIS IF YOU ARE NOT ALREADY S-OFF.
FOR THE OTA UPDATE 1.31.651.2 YOU WILL FOR SURE RETAIN S-OFF AND THEY HAVEN'T CHANGED THE SECURITY TO S-ON. ALTHOUGH HIGHLY UNLIKELY, HTC COULD POTENTIALLY MAKE YOU S-ON IN FUTURE OTA UPDATES. SEE HERE FOR MORE INFORMATION.
Once you are s-off you can install the OTA update no problem and still retain root. I understand that there are rooted ROMs that come out within a day or whatever, I just find this method easier and less annoying than waiting for a rooted stock ROM to come out. I don't really theme, mod, or do crazy things with my phone but still want root access. So, I decided since I was s-off, I would give this method a whirl. I am happy to report that I am s-off, with TWRP, fully rooted, and with installing the OTA update. I had a little hiccup on my previous phone but was able to solve that. You could run into a similar issue with the HTC One.
Download the stock recovery zip file below. Place the file in the folder with your fastboot commands.
Make sure fastboot in unchecked on your phone in power settings>fastboot.
Power down phone by holding power button and pressing shut down.
Once phone is shut down, power phone into bootloader by holding volume down button and pressing power button.
Once in the bootloader navigate until it says fastboot usb (must have phone connected to computer).
Open up a command prompt where your fastboot commands are located.
Type the following with the filename of the stock recovery
Code:
fastboot flash recovery <filename>
Navigate in the bootloader menu to the reboot option to restart your phone.
Download the latest SuperSU and place it on your sdcard. I used this one: http://download.chainfire.eu/351/SuperSU/UPDATE-SuperSU-v1.65.zip
Install the OTA update just like normal.
Once it finishes installing, power down the phone like before and get back to fastboot usb.
Type the following in your command prompt:
Code:
fastboot oem rebootRUU
Then type the following to flash the recovery you downloaded. I used the one here.
Code:
fastboot flash recovery <recovery>
Then type
Code:
fastboot reboot-bootloader
Enter recovery by navigating with the volume buttons
Once in recovery, flash the zip of the SuperSU file you previously downloaded.
Restart once flashing is complete.
You are now rooted with the most current OTA update and all the goodies (radios, PRI, etc.)
This process should hopefully hold true for any future OTA updates if you are S-OFF. If this helped, feel free to thank! Go XDA!
What does the fastboot OEM rebootRUU do? I see it when you want to update firmware but why do I have to do that command?
Sent from my One using Tapatalk 4
YoungCorruptionV2.0 said:
What does the fastboot OEM rebootRUU do? I see it when you want to update firmware but why do I have to do that command?
Sent from my One using Tapatalk 4
Click to expand...
Click to collapse
It allows you to flash the engineering hboot. I don't know of another way to do it. I am 90% sure it relocked my bootloader when I installed the OTA. You have to have this hboot to be able to flash the recovery.
U can also use ota root keeper worked for me
Sent from my One using XDA Premium HD app
bpdamas said:
It allows you to flash the engineering hboot. I don't know of another way to do it. I am 90% sure it relocked my bootloader when I installed the OTA. You have to have this hboot to be able to flash the recovery.
Click to expand...
Click to collapse
Ah alright thanks for the information
Sent from my One using Tapatalk 4
pbedard said:
U can also use ota root keeper worked for me
Sent from my One using XDA Premium HD app
Click to expand...
Click to collapse
Interesting. I didn't even try it this last time. Can anyone else confirm OTA rootkeeper worked for them?
bpdamas said:
It allows you to flash the engineering hboot. I don't know of another way to do it. I am 90% sure it relocked my bootloader when I installed the OTA. You have to have this hboot to be able to flash the recovery.
Click to expand...
Click to collapse
You don't need the ENG hboot to flash recovery. Just to do it easily...it works just fine with an android-info.txt and recovery.img in a zip which is how s-off devices are supposed to flash files anyway.
Indirect said:
You don't need the ENG hboot to flash recovery. Just to do it easily...it works just fine with an android-info.txt and recovery.img in a zip which is how s-off devices are supposed to flash files anyway.
Click to expand...
Click to collapse
Good to know. I guess I didn't know what to name the zip file. Any insight? The method you describe is what I have used in the past. Let me know what you think and thanks for your help.
bpdamas said:
Good to know. I guess I didn't know what to name the zip file. Any insight? The method you describe is what I have used in the past. Let me know what you think and thanks for your help.
Click to expand...
Click to collapse
Don't have to name it anything. You need to fastboot oem rebootRUU then fastboot flash zip ZIPNAME.zip
Indirect said:
Don't have to name it anything. You need to fastboot oem rebootRUU then fastboot flash zip ZIPNAME.zip
Click to expand...
Click to collapse
Ah. Much easier. I will update the steps to show this.
Indirect said:
You don't need the ENG hboot to flash recovery. Just to do it easily...it works just fine with an android-info.txt and recovery.img in a zip which is how s-off devices are supposed to flash files anyway.
Click to expand...
Click to collapse
Indirect,
Would you please provide an explanation of this exactly.... Or a link to a thread that details it and includes the information on proper formatting of the android-info.txt
I have a img of twrp I just need an android-info.txt formatted properly. So I can place them in a zip and flash them.
This is exactly what I need.
tws101 said:
Indirect,
Would you please provide an explanation of this exactly.... Or a link to a thread that details it and includes the information on proper formatting of the android-info.txt
I have a img of twrp I just need an android-info.txt formatted properly. So I can place them in a zip and flash them.
This is exactly what I need.
Click to expand...
Click to collapse
modelid: PN0720000
cidnum: SPCS_001
mainver: 1.29.651.10
hbootpreupdate:3
Indirect said:
modelid: PN0720000
cidnum: SPCS_001
mainver: 1.29.651.10
hbootpreupdate:3
Click to expand...
Click to collapse
I assume change this to match my current version correct?
mainver: 1.31.651.2
Thank, Indirect
---------- Post added at 10:40 PM ---------- Previous post was at 10:22 PM ----------
Indirect said:
modelid: PN0720000
cidnum: SPCS_001
mainver: 1.29.651.10
hbootpreupdate:3
Click to expand...
Click to collapse
I just created this
https://www.dropbox.com/s/2r6g5n0hepswqs7/recovery.zip
and tried fastboot flash zip recovery.zip
FAILED remote not allowed
I am S-OFF locked HB 1.44 on ver 1.31
tws101 said:
I assume change this to match my current version correct?
mainver: 1.31.651.2
Thank, Indirect
---------- Post added at 10:40 PM ---------- Previous post was at 10:22 PM ----------
I just created this
https://www.dropbox.com/s/2r6g5n0hepswqs7/recovery.zip
and tried fastboot flash zip recovery.zip
FAILED remote not allowed
I am S-OFF locked HB 1.44 on ver 1.31
Click to expand...
Click to collapse
did you fastboot oem rebootRUU
also just remove the mainver line.
Indirect said:
did you fastboot oem rebootRUU
also just remove the mainver line.
Click to expand...
Click to collapse
Thanks Indirect,
It is working now
Removing Mainver line DID not work...
The exact code you gave with the old mainver worked fine.
file is https://www.dropbox.com/s/2r6g5n0hepswqs7/recovery.zip
That has TWRP 2.5
fastboot commands were
fastboot oem rebootRUU
fastboot flash zip recovery.zip
fastboot reboot
worked perfect thanks for your help.
I assume if I want to restore the stock recovery I can do so using the old 1.29 recovery on 1.31 and it won't matter?
Also if you really want to keep root on OTAs, just
adb shell
Code:
echo placeholder > /data/local.prop
chmod 766 /data/local.prop
chown 0:0 /data/local.prop
Take OTA
adb shell
Code:
echo ro.kernel.qemu=1 > /data/local.prop
reboot
adb remount
adb push su /system/xbin/
adb push Superuser.apk /system/app/
adb shell chmod 04755 /system/xbin/su
reboot
Indirect said:
Also if you really want to keep root on OTAs, just
adb shell
Code:
echo placeholder > /data/local.prop
chmod 766 /data/local.prop
chown 0:0 /data/local.prop
Take OTA
adb shell
Code:
echo ro.kernel.qemu=1 > /data/local.prop
reboot
adb remount
adb push su /system/xbin/
adb push Superuser.apk /system/app/
adb shell chmod 04755 /system/xbin/su
reboot
Click to expand...
Click to collapse
Will this work every time they come out with an update?
bpdamas said:
Will this work every time they come out with an update?
Click to expand...
Click to collapse
should
I got stuck at 25% and got a big red exclamation mark. I think Ive read something about that on one of the topics but can't find it anymore. Have no clue why it worked, but holding the phone under a bright light and holding volume down and power button finaly rebooted the device and its now working again only no OTA 4.2.2 update
If anyone could shed some light?
tws101 said:
Thanks Indirect,
It is working now
Removing Mainver line DID not work...
The exact code you gave with the old mainver worked fine.
file is https://www.dropbox.com/s/2r6g5n0hepswqs7/recovery.zip
That has TWRP 2.5
fastboot commands were
fastboot oem rebootRUU
fastboot flash zip recovery.zip
fastboot reboot
worked perfect thanks for your help.
I assume if I want to restore the stock recovery I can do so using the old 1.29 recovery on 1.31 and it won't matter?
Click to expand...
Click to collapse
I found that the only required lines to flash using this method are:
modelid: PN0720000
cidnum: SPCS_001
mainver: 1.29.651.10
and that mainver refers to a minimum version needed to flash the file, so it can remain the same for both 1.29 and 1.31 recoveries.
i flashed a new firmware to my ONE (DEV ED) i used this guide with this firmware
NOTE i was on 4.1.2 and wanted to install 4.2.2 ARHD, now after all this proccess my phone turns on and it shows only a black screen no htc logo nothing (well the HTC withe boot screen loads, but then nothing) :/ i wanted to push the rom through adb but i couldnt is my phone dead????
what can i do?
Code:
x.xx.1700.x - Google Edition (WWE)
modelid: PN0710000
modelid: PN0711000
modelid: PN0712000
modelid: PN0713000
modelid: PN0714000
modelid: PN071****
cidnum: 11111111
cidnum: T-MOB010
cidnum: CWS__001
cidnum: BS_US001
cidnum: GOOGL001
Download:
firmware.zip from 1.29.206.11
MD5:
F3CC4B4B0ACD18A4B35D0B3C9DF2AB20
Code:
How to flash?
(bootloader needs to be relocked)
Re-lock your bootloader (this will most probably wipe content of your device)
Copy downloaded .zip to fastboot.exe location (e.g. c:/SDK/platform-tools/fastboot.exe)
Re-name .zip file to firmware.zip
Open command prompt
Boot your device in fastboot mode (vol down + power ===> fastboot)
Connect device to the PC
In command prompt cd to fastboot.exe location
Make sure you have correct modeid and cidnum (type: fastboot getvar all)
Type: fastboot oem lock (if your device is not relocked yet)
Type: fastboot oem rebootRUU and wait for device to reboot
Type: fastboot flash zip firmware.zip and wait for process to complete
Sometimes flashing for the first time doesn't work, so flash firmware.zip again just to make sure.
Type: fastboot flash zip firmware.zip and wait for process to complete
Type: fastboot reboot
Unlock your bootloader and flash custom recovery if you are going to use custom ROM.
PLEASE HELP!!! any advise is great
eltoffer said:
i flashed a new firmware to my ONE (DEV ED) i used this guide with this firmware
NOTE i was on 4.1.2 and wanted to install 4.2.2 ARHD, now after all this proccess my phone turns on and it shows only a black screen no htc logo nothing (well the HTC withe boot screen loads, but then nothing) :/ i wanted to push the rom through adb but i couldnt is my phone dead????
what can i do?
Code:
x.xx.1700.x - Google Edition (WWE)
modelid: PN0710000
modelid: PN0711000
modelid: PN0712000
modelid: PN0713000
modelid: PN0714000
modelid: PN071****
cidnum: 11111111
cidnum: T-MOB010
cidnum: CWS__001
cidnum: BS_US001
cidnum: GOOGL001
Download:
firmware.zip from 1.29.206.11
MD5:
F3CC4B4B0ACD18A4B35D0B3C9DF2AB20
Code:
How to flash?
(bootloader needs to be relocked)
Re-lock your bootloader (this will most probably wipe content of your device)
Copy downloaded .zip to fastboot.exe location (e.g. c:/SDK/platform-tools/fastboot.exe)
Re-name .zip file to firmware.zip
Open command prompt
Boot your device in fastboot mode (vol down + power ===> fastboot)
Connect device to the PC
In command prompt cd to fastboot.exe location
Make sure you have correct modeid and cidnum (type: fastboot getvar all)
Type: fastboot oem lock (if your device is not relocked yet)
Type: fastboot oem rebootRUU and wait for device to reboot
Type: fastboot flash zip firmware.zip and wait for process to complete
Sometimes flashing for the first time doesn't work, so flash firmware.zip again just to make sure.
Type: fastboot flash zip firmware.zip and wait for process to complete
Type: fastboot reboot
Unlock your bootloader and flash custom recovery if you are going to use custom ROM.
PLEASE HELP!!! any advise is great
Click to expand...
Click to collapse
First, not sure where you got your instructions, but you did not have to relock your bootloader to flash firmware, especially not S-off as your screenshot shows. Anyways, your pic shows you are unlocked, S-off, on 3.06 firmware. Have you flashed a custom recovery yet? That should be next, I recommend TWRP, look in the Original Development thread for the TWRP thread for the download and instructions. You want the 2.6.0.1 version for the m7. Flash recovery, then flash ARHD thru TWRP
dgtiii said:
First, not sure where you got your instructions, but you did not have to relock your bootloader to flash firmware, especially not S-off as your screenshot shows. Anyways, your pic shows you are unlocked, S-off, on 3.06 firmware. Have you flashed a custom recovery yet? That should be next, I recommend TWRP, look in the Original Development thread for the TWRP thread for the download and instructions. You want the 2.6.0.1 version for the m7. Flash recovery, then flash ARHD thru TWRP
Click to expand...
Click to collapse
both instructions and firmware where from MIKE (http://forum.xda-developers.com/showthread.php?t=2182823)
i already installed CR indeed it was CWM, if i use TWRP how can i push the rom to the phone :/?
eltoffer said:
both instructions and firmware where from MIKE (http://forum.xda-developers.com/showthread.php?t=2182823)
i already installed CR indeed it was CWM, if i use TWRP how can i push the rom to the phone :/?
Click to expand...
Click to collapse
Hmmm....I never had to relock to flash firmware..anyways.....I use TWRP, but CWM is close to same
Go here: http://forum.xda-developers.com/showthread.php?t=2325853&highlight=sideload and here http://forum.xda-developers.com/showthread.php?t=2318497 for ADB push/sideload
dgtiii said:
Hmmm....I never had to relock to flash firmware..anyways.....I use TWRP, but CWM is close to same
Go here: http://forum.xda-developers.com/showthread.php?t=2325853&highlight=sideload and here http://forum.xda-developers.com/showthread.php?t=2318497 for ADB push/sideload
Click to expand...
Click to collapse
thanks this is what i needed, i couldnt push my rom with CWM but i did with TWRP flahsed and ok
BIG THANKS
eltoffer said:
thanks this is what i needed, i couldnt push my rom with CWM but i did with TWRP flahsed and ok
BIG THANKS
Click to expand...
Click to collapse
Haha, that's awesome! Happy to help and glad it's back!
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
Hey my HTC won't enter into recovery how do I fix it I have tried resetting the ruu but it keeps saying failed I need help bad ?
Yotekiller said:
Hey my HTC won't enter into recovery how do I fix it I have tried resetting the ruu but it keeps saying failed I need help bad ?
Click to expand...
Click to collapse
you have an AT&T Phone what file are you trying to flash? and how long has your OS been like that in the bootloader ?
Also your s-off so relocking the bootloader was not needed
clsA said:
you have an AT&T Phone what file are you trying to flash? and how long has your OS been like that in the bootloader ?
Also your s-off so relocking the bootloader was not needed
Click to expand...
Click to collapse
It's been like this for 60 days I have been in jail lol it crashed right before I went in yes it's att the file is a ruu zip m7 ul jb43 sense50 Mr cinguler us 3.17.502.3 decrypted sorry I didn't have the link handy for the file
Yotekiller said:
Hey my HTC won't enter into recovery how do I fix it I have tried resetting the ruu but it keeps saying failed I need help bad ?
Click to expand...
Click to collapse
can you post a "fastboot getvar all" excluding IMEI and s/n
it looks like you messed up some things, including your misc partition, fix that first: http://forum.xda-developers.com/showthread.php?t=2739126
then use an RUU
PS: you'll need to have bootloader unlocked, if you can't manage to unlock it in this state, let me know (but i'll need the output of your getvar all, excluding IMEI and s/n)
getvar all
nkk71 said:
can you post a "fastboot getvar all" excluding IMEI and s/n
it looks like you messed up some things, including your misc partition, fix that first: http://forum.xda-developers.com/showthread.php?t=2739126
then use an RUU
PS: you'll need to have bootloader unlocked, if you can't manage to unlock it in this state, let me know (but i'll need the output of your getvar all, excluding IMEI and s/n)
Click to expand...
Click to collapse
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4T.20.3218.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 8
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: 000000000000
(bootloader) imei: 000000000000
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4042mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-2da61e5e88
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Screen shot
This is all I get when eentering recovery
yotekiller82 said:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4T.20.3218.13
(bootloader) version-main: 8
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) product: m7_ul
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
First off, make sure you're not on Windows 8.1, use Win7 or ubuntu or mac.
flash the attached file (that will downgrade hboot to 1.44, and install the noBCB recovery):
fastboot oem rebootRUU
fastboot flash zip fw_hb144_twrp-nobcb.zip
fastboot flash zip fw_hb144_twrp-nobcb.zip <- yes TWICE
fastboot reboot-bootloader
fastboot erase cache
-> enter RECOVERY
then follow the steps http://forum.xda-developers.com/showthread.php?t=2739126 to fix your corrupted misc partition.
once done, use https://www.androidfilehost.com/?fid=23501681358544977 to reset everything back to stock (in case something else is corrupt)
rename the above file to ruu.zip:
fastboot oem rebootRUU
fastboot flash zip ruu.zip
fastboot flash zip ruu.zip <- yes TWICE
fastboot reboot-bootloader
i tried that didnt work
nkk71 said:
First off, make sure you're not on Windows 8.1, use Win7 or ubuntu or mac.
flash the attached file (that will downgrade hboot to 1.44, and install the noBCB recovery):
fastboot oem rebootRUU
fastboot flash zip fw_hb144_twrp-nobcb.zip
fastboot flash zip fw_hb144_twrp-nobcb.zip <- yes TWICE
fastboot reboot-bootloader
fastboot erase cache
-> enter RECOVERY
then follow the steps http://forum.xda-developers.com/showthread.php?t=2739126 to fix your corrupted misc partition.
once done, use https://www.androidfilehost.com/?fid=23501681358544977 to reset everything back to stock (in case something else is corrupt)
rename the above file to ruu.zip:
fastboot oem rebootRUU
fastboot flash zip ruu.zip
fastboot flash zip ruu.zip <- yes TWICE
fastboot reboot-bootloader
Click to expand...
Click to collapse
ok the first step worked but everytime i try to step 2 it locks up my pc and wont push the ruu onto the phone any help on that one im using a laptop with win 7
yotekiller82 said:
ok the first step worked but everytime i try to step 2 it locks up my pc and wont push the ruu onto the phone any help on that one im using a laptop with win 7
Click to expand...
Click to collapse
can you be more specific, which "step 2" doesn't work, also best to copy/paste your command prompt output (please copy/paste, screenshots are very hard to read).
Step 2
nkk71 said:
can you be more specific, which "step 2" doesn't work, also best to copy/paste your command prompt output (please copy/paste, screenshots are very hard to read).
Click to expand...
Click to collapse
OK the first part of the post went good downgraded the hboot to 1.44 the second ruu won't go to the phone when you try to push it on it looks like it works it starts flashing a single bar on the next line a couple times then locks up the pic while the phone is setting in the black logo I have let it set for 20 min what is going on Idk how much more I can tell yall
I have got a copy of skydragon to flash in recovery but in the initial setupit keep rebooting so iI'm getting closer if that helps
Yotekiller said:
OK the first part of the post went good downgraded the hboot to 1.44 the second ruu won't go to the phone when you try to push it on it looks like it works it starts flashing a single bar on the next line a couple times then locks up the pic while the phone is setting in the black logo I have let it set for 20 min what is going on Idk how much more I can tell yall
I have got a copy of skydragon to flash in recovery but in the initial setupit keep rebooting so iI'm getting closer if that helps
Click to expand...
Click to collapse
Do you have htcsync installed on your pc it's known to cause problems with RUU mode. If so uninstall htcsync but keep the drivers.
Then try flash the RUU again
Sent from my HTC One M7 - ARHD 81.0 Using Tapatalk
Htc sync
Danny201281 said:
Do you have htcsync installed on your pc it's known to cause problems with RUU mode. If so uninstall htcsync but keep the drivers.
Then try flash the RUU again
Sent from my HTC One M7 - ARHD 81.0 Using Tapatalk
Click to expand...
Click to collapse
No I don't have htc sync installed ? I really need my phone back up and running
Yotekiller said:
No I don't have htc sync installed ? I really need my phone back up and running
Click to expand...
Click to collapse
just reboot the phone and start the RUU process again till it finishes.
Did you md5 check your RUU download to be sure it's not corrupt ?
Yotekiller said:
OK the first part of the post went good downgraded the hboot to 1.44 the second ruu won't go to the phone when you try to push it on it looks like it works it starts flashing a single bar on the next line a couple times then locks up the pic while the phone is setting in the black logo I have let it set for 20 min what is going on Idk how much more I can tell yall
I have got a copy of skydragon to flash in recovery but in the initial setupit keep rebooting so iI'm getting closer if that helps
Click to expand...
Click to collapse
It would really help, if you copy/pasted your command prompt output.
Let's break this down again:
Step 1
First off, make sure you're not on Windows 8.1, use Win7 or ubuntu or mac.
Step 2
flash the attached file (that will downgrade hboot to 1.44, and install the noBCB recovery):
fastboot oem rebootRUU
fastboot flash zip fw_hb144_twrp-nobcb.zip
fastboot flash zip fw_hb144_twrp-nobcb.zip <- yes TWICE
fastboot reboot-bootloader
fastboot erase cache
Step 3
-> enter RECOVERY
then follow the steps http://forum.xda-developers.com/showthread.php?t=2739126 to fix your corrupted misc partition.
Step 4
once done, use https://www.androidfilehost.com/?fid=23501681358544977 to reset everything back to stock (in case something else is corrupt)
rename the above file to ruu.zip:
fastboot oem rebootRUU
fastboot flash zip ruu.zip
fastboot flash zip ruu.zip <- yes TWICE
fastboot reboot-bootloader
Am understanding correctly that
Step 1: confirmed
Step 2: successful
Step 3: completed successfully
Step 4: this is where you get stuck??
Reboot the ruu
nkk71 said:
It would really help, if you copy/pasted your command prompt output.
Let's break this down again:
Step 1
First off, make sure you're not on Windows 8.1, use Win7 or ubuntu or mac.
Step 2
flash the attached file (that will downgrade hboot to 1.44, and install the noBCB recovery):
fastboot oem rebootRUU
fastboot flash zip fw_hb144_twrp-nobcb.zip
fastboot flash zip fw_hb144_twrp-nobcb.zip <- yes TWICE
fastboot reboot-bootloader
fastboot erase cache
Step 3
-> enter RECOVERY
then follow the steps http://forum.xda-developers.com/showthread.php?t=2739126 to fix your corrupted misc partition.
Step 4
once done, use https://www.androidfilehost.com/?fid=23501681358544977 to reset everything back to stock (in case something else is corrupt)
rename the above file to ruu.zip:
fastboot oem rebootRUU
fastboot flash zip ruu.zip
fastboot flash zip ruu.zip <- yes TWICE
fastboot reboot-bootloader
Am understanding correctly that
Step 1: confirmed
Step 2: successful
Step 3: completed successfully
Step 4: this is where you get stuck??
Click to expand...
Click to collapse
Yes step 4 trying to flash the second file you give me
Yotekiller said:
Yes step 4 trying to flash the second file you give me
Click to expand...
Click to collapse
check MD5, and if the error persists:
hint:
It would really help, if you copy/pasted your command prompt output.
Copying command
nkk71 said:
check MD5, and if the error persists:
hint:
It would really help, if you copy/pasted your command prompt output.
Click to expand...
Click to collapse
It's kind of hard to do as I start the step 4 and it locks up the pc it won't response to anythingiI do I'm sorry I'm new to all this is there something I can do to get the pc to stop freezing up
I'm sorry if I don't understand what your trying to tell me ?
Yotekiller said:
It's kind of hard to do as I start the step 4 and it locks up the pc it won't response to anythingiI do I'm sorry I'm new to all this is there something I can do to get the pc to stop freezing up
I'm sorry if I don't understand what your trying to tell me ��
Click to expand...
Click to collapse
your pc completely freezes
then either fix your PC issues (whatever they may be, drivers, antivirus programs, firewalls, etc), or make life simple and make an Ubuntu Live USB (no need to install it, you can boot directly off a USB stick), check FAQ #5 here
The computer
nkk71 said:
your pc completely freezes
then either fix your PC issues (whatever they may be, drivers, antivirus programs, firewalls, etc), or make life simple and make an Ubuntu Live USB (no need to install it, you can boot directly off a USB stick), check FAQ #5 here
Click to expand...
Click to collapse
Yea the computer freezes up won't do nothing working on gettinga uUSB drive fixed up I don't have the fastest Internet where I live so lol sorry I have been trouble
Update I have one of my laptops running ubuntu now so hopefully in the next few days I can get all the drivers and everything I need to get the phone running again thanks for the help will update asap
Yotekiller said:
Yea the computer freezes up won't do nothing working on gettinga uUSB drive fixed up I don't have the fastest Internet where I live so lol sorry I have been trouble
Update I have one of my laptops running ubuntu now so hopefully in the next few days I can get all the drivers and everything I need to get the phone running again thanks for the help will update asap
Click to expand...
Click to collapse
You don't need drivers for your phone on ubuntu. If you have ubuntu running with adb/fastboot installed that's all you need. It will work
Sent from my HTC One M7 - ARHD 81.0 Using Tapatalk