Related
Hello guys,
I have S-OFF, supercid, relocked bootloader phone
First I installed Firmware package from 2.17.401.1 RUU sucressfully my terminal quoted and then after reboot My phone was not reacting to any tipping on the screen. I only reached the screen where it demands the pin to type in.
So I flashed it again with firmware.zip from 1.29.401.12. Flash sucessfully (terminal quoted) and now it rebooted to the htc one logo and nothing else happens. I even cannot turn it off. Please help.
Update: I managed to reboot it but it is not reacting when i want to put in my PIN
Put the device under direct light (perhaps like a bulb) and press the power and volume down buttons together until the device reboots. While it is under direct light, do not cover the light sensors (on the left of the upper speaker grill) with your hand.
TarekElsakka said:
Put the device under direct light (perhaps like a bulb) and press the power and volume down buttons together until the device reboots. While it is under direct light, do not cover the light sensors (on the left of the upper speaker grill) with your hand.
Click to expand...
Click to collapse
ok i now restarted it but the touchscreen does not react when it asks me to put in the PIN
Reflash ROM..
Sent from my HTC One
Sindroid said:
Reflash ROM..
Sent from my HTC One
Click to expand...
Click to collapse
I flashed firmware 1.29.401.12 it again and same no reaction with touchscreen
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.
I did everything till step 14. Rom i have not installed yet because i want to install the firmware first.
Exxorzist said:
I flashed firmware 1.29.401.12 it again and same no reaction with touchscreen
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.
I did everything till step 14. Rom i have not installed yet because i want to install the firmware first.
Click to expand...
Click to collapse
I've had the same issue. Which rom do you use? CM wasn't working for me, so I had to flash Sense rom like ARHD 11 or Trickdroid 7.5
I also flashed the older firmware.zip and still no touch responsiveness. You will also have to flash a newer cwm touch recovery if you are using it, helps navigating through aroma http://goo.im/devs/Flyhalf205/M7/Recovery/recovery-clockwork-touch-6.0.3.2-m7.img
Exxorzist said:
I flashed firmware 1.29.401.12 it again and same no reaction with touchscreen
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.
I did everything till step 14. Rom i have not installed yet because i want to install the firmware first.
Click to expand...
Click to collapse
You need to flash this firmware: http://www.androidrevolution.nl/downloader/download.php?file=2.17.401.1-custom.zip again, and then flash the custom recovery stated above this post. Next, flash the latest Android Revolution which is on the newest base which other roms don't have yet. This should fix your issue. CM roms cannot be used by your device in its current state, as the touch drivers aren't compatible. You must use a Sense rom
MacHackz said:
You need to flash this firmware: http://www.androidrevolution.nl/downloader/download.php?file=2.17.401.1-custom.zip again, and then flash the custom recovery stated above this post. Next, flash the latest Android Revolution which is on the newest base which other roms don't have yet. This should fix your issue. CM roms cannot be used by your device in its current state, as the touch drivers aren't compatible. You must use a Sense rom
Click to expand...
Click to collapse
I flashed the firmware again sucessfully to 2.17.401.1
Since 2 days my Bootloader is relocked again but I am S-OFF. When I want to flash custom recovery I do have to unlock it again? How do I do that because I am still not able to use touchscreen and type in PIN?
George_Mn said:
I've had the same issue. Which rom do you use? CM wasn't working for me, so I had to flash Sense rom like ARHD 11 or Trickdroid 7.5
I also flashed the older firmware.zip and still no touch responsiveness. You will also have to flash a newer cwm touch recovery if you are using it, helps navigating through aroma http://goo.im/devs/Flyhalf205/M7/Recovery/recovery-clockwork-touch-6.0.3.2-m7.img
Click to expand...
Click to collapse
Exxorzist said:
I flashed the firmware again sucessfully to 2.17.401.1
Since 2 days my Bootloader is relocked again but I am S-OFF. When I want to flash custom recovery I do have to unlock it again? How do I do that because I am still not able to use touchscreen and type in PIN?
Click to expand...
Click to collapse
type fastboot oem flash unlocktoken unlock_code.bin
MacHackz said:
type fastboot oem flash unlocktoken unlock_code.bin
Click to expand...
Click to collapse
Thanks. I unlocked it and flashed the custom recovery
./fastboot-mac flash recovery recovery.img
sending 'recovery' (7422 KB)... OKAY
writing 'recovery'... OKAY
Then i rebootet it and touchscreen is still not reacting. Shall I now flash the revolution hd rom?
Exxorzist said:
Thanks. I unlocked it and flashed the custom recovery
./fastboot-mac flash recovery recovery.img
sending 'recovery' (7422 KB)... OKAY
writing 'recovery'... OKAY
Then i rebootet it and touchscreen is still not reacting. Shall I now flash the revolution hd rom?
Click to expand...
Click to collapse
Does touchscreen work in recovery mode?
What ROM do you currently have?
MacHackz said:
Does touchscreen work in recovery mode?
What ROM do you currently have?
Click to expand...
Click to collapse
Yes touchscreen works in recovery. I am at the moment not using any rom. I have bought a branded phone and all I did was giving it S-OFF, unlock bootloader, supercid, root.
And now after I flashed firmware 2.17, i simply want to put a rom on it like Revolution HD 11
Exxorzist said:
Yes touchscreen works in recovery. I am at the moment not using any rom. I have bought a branded phone and all I did was giving it S-OFF, unlock bootloader, supercid, root.
And now after I flashed firmware 2.17, i simply want to put a rom on it like Revolution HD 11
Click to expand...
Click to collapse
Flash Android Revolution 11 and it should work! :fingers-crossed:
MacHackz said:
Flash Android Revolution 11 and it should work! :fingers-crossed:
Click to expand...
Click to collapse
Stupid question. How do I get the zip file onto my Phone? Because I cannot type in my pin and then connect it as usual and pulling it via Android File Transfer over to my phone.
Exxorzist said:
Stupid question. How do I get the zip file onto my Phone? Because I cannot type in my pin and then connect it as usual and pulling it via Android File Transfer over to my phone.
Click to expand...
Click to collapse
Check my ADB push guide in my sig, jump to step 3
No need to relock bootloader when S-Off. If you upgrade firmware. If you upgrading to 2.17 f/w u need to flash new recovery as well.
Use sideload in recovery to reflash ROM.
Sent from my HTC One
MacHackz said:
Check my ADB push guide in my sig, jump to step 3
Click to expand...
Click to collapse
You are my hero!!!!!
Everything works great. Is there also the camera update included that was released by HTC in 1.29 because before I had 1.28.
Exxorzist said:
You are my hero!!!!!
Everything works great. Is there also the camera update included that was released by HTC in 1.29 because before I had 1.28.
Click to expand...
Click to collapse
It's all included You can also check the modded camera apk in my signature which allows you to take photos and focus using your volume buttons
Glad it worked
Thank you so much for this tip I thought I was SOL when it went into the WSOD and I couldn't turn it off.
Hi Xda
Forgive me for what you are about to read, as I have carried out some dumb ### noobness:
I was running Sinless 5.1Gpe rom (great rom) anyways I wanted to return to a sense based rom so decided to go for ARHD 40.2 fter reading a number of posts mentioning doing a complete wipe of the phone including SDCARD. I checked the process of pushing via adb and all seemed simple enough.
I initially did a test and it pushed the file, so then i carried out the complete wipe (no OS, no rom on sd card to flash). I then tried to push the rom and it failed. I tried a number of different ways sideload too.
I managed to get the rom to push in the end using the lastest TWRP of which it would not allow me to do rom failed to flash...
Now this is the stupid part, TWRP became unresponsive, and every time I tried to boot into recovery it would kick me out to the spash screen and bootloop. I did the fastboot erase cache without any success.
I managed to switch to CWM but could not mount anything so came across a post about switching to stock....This is the really stupid part. I flashed a stock recovery and also I now have a relocked bootloader.
Is this phone now bricked??
I have fastboot available
I am S-off
I can boot into stock recovery (Red triangle)
I cannot use ADB (device not recognised)
I cannot re unlock bootloader (tried twice and failed) - I will try again as it got to 4am and had to be up for work at 6am.
Any help really really apreciated.
Many thanks
Mick
I will get there said:
Now this is the stupid part, TWRP became unresponsive, and every time I tried to boot into recovery it would kick me out to the spash screen and bootloop. I did the fastboot erase cache without any success.
I managed to switch to CWM but could not mount anything so came across a post about switching to stock....This is the really stupid part. I flashed a stock recovery and also I now have a relocked bootloader.
Is this phone now bricked??
I have fastboot available
I am S-off
I can boot into stock recovery (Red triangle)
I cannot use ADB (device not recognised)
I cannot re unlock bootloader (tried twice and failed) - I will try again as it got to 4am and had to be up for work at 6am.
Any help really really apreciated.
Many thanks
Mick
Click to expand...
Click to collapse
How did you unlock the first time? HTCDev or S-OFF?
Can you post the error you get when you try to unlock?
I will get there said:
Hi Xda
I have fastboot available
I am S-off
I can boot into stock recovery (Red triangle)
I cannot use ADB (device not recognised)
I cannot re unlock bootloader (tried twice and failed) - I will try again as it got to 4am and had to be up for work at 6am.
Any help really really apreciated.
Many thanks
Mick
Click to expand...
Click to collapse
if you have s-off you should flash back a custom recovery:
fastboot erase cache
fastboot flash recovery <name of recovery>.img
fastboot erase cache
fastboot reboot-bootloader
-> enter RECOVERY, and adb should be working again,
use this to unlock your phone: http://forum.xda-developers.com/showthread.php?t=2475914
there's also a handy Guru Bootloader Reset (flashable zip): http://forum.xda-developers.com/showthread.php?t=2527194
but it needs either CWM 6.0.3.2+, or TWRP 2.6.3.3+ to work.
or even "revone -u"
I will get there said:
Hi Xda
Forgive me for what you are about to read, as I have carried out some dumb ### noobness:
I was running Sinless 5.1Gpe rom (great rom) anyways I wanted to return to a sense based rom so decided to go for ARHD 40.2 fter reading a number of posts mentioning doing a complete wipe of the phone including SDCARD. I checked the process of pushing via adb and all seemed simple enough.
I initially did a test and it pushed the file, so then i carried out the complete wipe (no OS, no rom on sd card to flash). I then tried to push the rom and it failed. I tried a number of different ways sideload too.
I managed to get the rom to push in the end using the lastest TWRP of which it would not allow me to do rom failed to flash...
Now this is the stupid part, TWRP became unresponsive, and every time I tried to boot into recovery it would kick me out to the spash screen and bootloop. I did the fastboot erase cache without any success.
I managed to switch to CWM but could not mount anything so came across a post about switching to stock....This is the really stupid part. I flashed a stock recovery and also I now have a relocked bootloader.
Is this phone now bricked??
I have fastboot available
I am S-off
I can boot into stock recovery (Red triangle)
I cannot use ADB (device not recognised)
I cannot re unlock bootloader (tried twice and failed) - I will try again as it got to 4am and had to be up for work at 6am.
Any help really really apreciated.
Many thanks
Mick
Click to expand...
Click to collapse
If you can get to the stock recovery press volume up then power button and quickly release both buttons and you should be in stock recovery. From here you should be able to follow any of the posted steps to flash a RUU back to pure stock.
solbirn said:
How did you unlock the first time? HTCDev or S-OFF?
Can you post the error you get when you try to unlock?
Click to expand...
Click to collapse
Hi thanks for your response, I initially HTCDev then rumrunner to gain s-off.
The error I get is:
Microsoft Windows [Version 6.3.9600]
(c) 2013 Microsoft Corporation. All rights reserved.
C:\Users\Michael\Desktop\Adb And Fastboot>fastboot flash unlocktoken Unlock_code
.bin
target reported max download size of 1514139648 bytes
error: cannot load 'Unlock_code.bin': No error
C:\Users\Michael\Desktop\Adb And Fastboot>
nkk71 said:
if you have s-off you should flash back a custom recovery:
fastboot erase cache
fastboot flash recovery <name of recovery>.img
fastboot erase cache
fastboot reboot-bootloader
-> enter RECOVERY, and adb should be working again,
use this to unlock your phone: http://forum.xda-developers.com/showthread.php?t=2475914
there's also a handy Guru Bootloader Reset (flashable zip): http://forum.xda-developers.com/showthread.php?t=2527194
but it needs either CWM 6.0.3.2+, or TWRP 2.6.3.3+ to work.
or even "revone -u"
Click to expand...
Click to collapse
Hey thanks for your response
I cant flash custom recovery the error i get is similar to trying to unlock.(above)
I cannot also use that thread because I cannot access adb (even though my phone recognises fastboot in device manager, when I go to what is now stock recovery is disappears from device manager)
I have no OS so cannot open up emulator for revone.
loughary said:
If you can get to the stock recovery press volume up then power button and quickly release both buttons and you should be in stock recovery. From here you should be able to follow any of the posted steps to flash a RUU back to pure stock.
Click to expand...
Click to collapse
Hey thanks for responding
I can get into stock android recovery(3e) it enters after notifying me that it failed to mount sd card 5 times then finishes with cannot mount sdcard (no such file or directory)
then finally write host_mode:0 done
any further suggestions?
I will get there said:
Hi thanks for your response, I initially HTCDev then rumrunner to gain s-off.
The error I get is:
Microsoft Windows [Version 6.3.9600]
(c) 2013 Microsoft Corporation. All rights reserved.
C:\Users\Michael\Desktop\Adb And Fastboot>fastboot flash unlocktoken Unlock_code
.bin
target reported max download size of 1514139648 bytes
error: cannot load 'Unlock_code.bin': No error
C:\Users\Michael\Desktop\Adb And Fastboot>
Hey thanks for your response
I cant flash custom recovery the error i get is similar to trying to unlock.(above)
I cannot also use that thread because I cannot access adb (even though my phone recognises fastboot in device manager, when I go to what is now stock recovery is disappears from device manager)
I have no OS so cannot open up emulator for revone.
Hey thanks for responding
I can get into stock android recovery(3e) it enters after notifying me that it failed to mount sd card 5 times then finishes with cannot mount sdcard (no such file or directory)
then finally write host_mode:0 done
any further suggestions?
Click to expand...
Click to collapse
You're getting "cannot load"? That just means the filename is wrong, as simple as that. If ur on Windows, check for .img.img (double extension)
Sent from my HTC One using Tapatalk
nkk71 said:
You're getting "cannot load"? That just means the filename is wrong, as simple as that. If ur on Windows, check for .img.img (double extension)
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Thanks @nkk71
I now have an unlocked bootloader
I have also now flashed CWM 6.0.4.5 however I still do not have adb available. The difference now is fastboot is recognised in device manager as before but when I boot into CWM instead of it dissapearing, it moves to 'other devices' one (with yellow exclamation) I know it did this before because of drivers not being installed/recognised but I have htc sync manager installed which in theory has installed the drivers??!
Anything else I can try without adb?
Again many thanks for your assistance, I see you in a number of threads helping people...top bloke!
Further update
I downgraded my hboot back to 1.55 and now TRWP is now functioning, I have now pushed a rom to the phone, however flash fails due to "unable to mount to internal storage"
Is there a fix for this?
Many thanks
I will get there said:
Further update
I downgraded my hboot back to 1.55 and now TRWP is now functioning, I have now pushed a rom to the phone, however flash fails due to "unable to mount to internal storage"
Is there a fix for this?
Many thanks
Click to expand...
Click to collapse
I suggest that you downgrade to Hboot 1.44, keep the bootloader locked and run the 1.28.401.7 RUU to be completely stock. Then its up to you whether you re staying stock or flashing sth custom.
Ivanovic said:
I suggest that you downgrade to Hboot 1.44, keep the bootloader locked and run the 1.28.401.7 RUU to be completely stock. Then its up to you whether you re staying stock or flashing sth custom.
Click to expand...
Click to collapse
Thanks @Ivanovic
I have since moved on a little further, i have now managed to push a rom via sideload, when i then go to flash it says:
Updating partion details....
E:unable to open zip file.
Error flashing zip /sdcard/sideload.zip
updating partition..details
failed
do you know a workaround this, if not could you direct me to a page with both hboot 1.44 and the RUU please
I will get there said:
Thanks @Ivanovic
I have since moved on a little further, i have now managed to push a rom via sideload, when i then go to flash it says:
Updating partion details....
E:unable to open zip file.
Error flashing zip /sdcard/sideload.zip
updating partition..details
failed
do you know a workaround this, if not could you direct me to a page with both hboot 1.44 and the RUU please
Click to expand...
Click to collapse
IF you re flashing a 4.4 ROM then use TWRP 2.6.3.3 or latest CWM
IF you re flashing a 4.3/4.2 ROM then use TWRP 2.6.3.0 or older CWM
Link for the RUU http://www.htc1guru.com/dld/ruu_m7_...1-27_10-31-1131-05_release_310878_signed-exe/
I will get there said:
Thanks @Ivanovic
I have since moved on a little further, i have now managed to push a rom via sideload, when i then go to flash it says:
Updating partion details....
E:unable to open zip file.
Error flashing zip /sdcard/sideload.zip
updating partition..details
failed
do you know a workaround this, if not could you direct me to a page with both hboot 1.44 and the RUU please
Click to expand...
Click to collapse
http://www.htc1guru.com/downloads/ruu-file-downloads/
I had to use the exe version to get it working when I had a similar issue.
Sent from my One using Tapatalk
Yes there is a fix. Install stock recovery. Go to bootloader and select factory reset. It will go to stock recovery and do it's thing and should go into a Bootloop . install custom recovery you should be good
Hi All
Just a quick note, to say all back up and running, thanks for all the respondants who helped.
I wanted add how i got it up and running, so if anyone has similar issues they can use it:
I believe the biggest culprit was the newest Firmware and TWRO 2.3.3.3 in which it did not want to load.
I downgraded by Hboot to firmware 3.xxx and then flashed TWRP 2.3.3.0 and it let me in instead of kicking me out to a bootloop.
I then had access to ADB sideload, which did not work for me in the 1st instance that led me to my problem, This i believe was due to not having the lastest SDK.(upgrade this).
Make sure the Rom you are pushing works well for that downgraded firmware i.e. a solid 4.3 based rom in my case.
Also to note I wiped my external SD card and was unable to mount this to flash, let TWRP sort this by doing a factory reset prior to flashing.
Hope this helps anyone who experienced similar symptoms to me.
Ok, I'm trying to flash the latest prl and firmware but I was on twrp 2.7.0.9, failed, updated to2.7.1.1 failed, tried to flash using the multi flasher withgem, Phil's twrp, ...every thing fails...I'm out of ideas
mxx20 said:
Ok, I'm trying to flash the latest prl and firmware but I was on twrp 2.7.0.9, failed, updated to2.7.1.1 failed, tried to flash using the multi flasher withgem, Phil's twrp, ...every thing fails...I'm out of ideas
Click to expand...
Click to collapse
Use this thread
http://forum.xda-developers.com/showthread.php?t=2766604
Modified firmware is in the second post.... You must flash it in fastboot
Commands
fastboot oem rebootRUU
fastboot flash zip firmware.zip (firmware.zip is the file name of the modified firmware rename it to firmware.zip to simplify)
fastboot reboot
That will get you the latest firmware. Whether you want to update your Rom is in the first post. That is a stock rooted Rom and can be flashed in TWRP.
tws101 said:
Use this thread
http://forum.xda-developers.com/showthread.php?t=2766604
Modified firmware is in the second post.... You must flash it in fastboot
Commands
fastboot oem rebootRUU
fastboot flash zip firmware.zip (firmware.zip is the file name of the modified firmware rename it to firmware.zip to simplify)
fastboot reboot
That will get you the latest firmware. Whether you want to update your Rom is in the first post. That is a stock rooted Rom and can be flashed in TWRP.
Click to expand...
Click to collapse
thanks, i must be blind or half asleep lol...
Hi. I have been searching for two days on how to restore my phone to a stock Rom. I flashed some lame Rom that I can't remember the name of (has a blue firebird boot screen...) and now that's the only Rom I can flash. I tried many rims but haven't had any luck. I know the lame Rom I flashed made me first flash a boot image. I trtried reflashing a stock boot image but it doesn't help. The stock roms succeed but stay stuck on the lock screen totally unresponsive except for the power button to hard reset... I'm trying to get S-Off with FireWire but it fails saying that it cannot s-Off my device. Cannot RUU since I'm s-on and have no clue what to do.
The boot loader reads that the O.S. is version 4.19.531.10 but I currently have no O.S. installed since I wiped.
The boot loader is version 1.56 and it's a T-Mobile USA version.
ADB Sideload works but the install is faulty as described.
Thanks.
OfficialLocdoGg said:
Hi. I have been searching for two days on how to restore my phone to a stock Rom. I flashed some lame Rom that I can't remember the name of (has a blue firebird boot screen...) and now that's the only Rom I can flash. I tried many rims but haven't had any luck. I know the lame Rom I flashed made me first flash a boot image. I trtried reflashing a stock boot image but it doesn't help. The stock roms succeed but stay stuck on the lock screen totally unresponsive except for the power button to hard reset... I'm trying to get S-Off with FireWire but it fails saying that it cannot s-Off my device. Cannot RUU since I'm s-on and have no clue what to do.
The boot loader reads that the O.S. is version 4.19.531.10 but I currently have no O.S. installed since I wiped.
The boot loader is version 1.56 and it's a T-Mobile USA version.
ADB Sideload works but the install is faulty as described.
Thanks.
Click to expand...
Click to collapse
update your recovery to 2.6.3.3 and flash your rom again.
Code:
fastboot flash recovery name_of_recovery.img
fastboot erase cache
fastboot reboot-bootloader
you can also use the latest RUU.exe which will restore your phone back to stock and updated to the latest version. (better option imo)
http://www.htc1guru.com/dld/ruu_m7_..._10-33e-1718-01l_release_387953_signed_2-exe/
I'm going to try to update the recovery first because when I try to relock the bootloader even after flashing stock recovery it just boots to the bootloader even with a rom installed. (Even if its the erroring stock rom)
alray said:
update your recovery to 2.6.3.3 and flash your rom again.
Code:
fastboot flash recovery name_of_recovery.img
fastboot erase cache
fastboot reboot-bootloader
you can also use the latest RUU.exe which will restore your phone back to stock and updated to the latest version. (better option imo)
http://www.htc1guru.com/dld/ruu_m7_..._10-33e-1718-01l_release_387953_signed_2-exe/
Click to expand...
Click to collapse
OfficialLocdoGg said:
I'm going to try to update the recovery first because when I try to relock the bootloader even after flashing stock recovery it just boots to the bootloader even with a rom installed. (Even if its the erroring stock rom)
Click to expand...
Click to collapse
its fine to flash a ruu with phone booted in bootloader btw.
alray said:
its fine to flash a ruu with phone booted in bootloader btw.
Click to expand...
Click to collapse
Okay well I'm having no luck. Trying to flash the RUU wont work and updating the recovery didn't work. The ruu just hangs at 5% Checking headers. I tried extracting the rom.zip from the ruu but I get the invalid size crap and when trying to open the rom.zip it gives me an invalid error. I don't know what to do here.
OfficialLocdoGg said:
Okay well I'm having no luck. Trying to flash the RUU wont work and updating the recovery didn't work. The ruu just hangs at 5% Checking headers. I tried extracting the rom.zip from the ruu but I get the invalid size crap and when trying to open the rom.zip it gives me an invalid error. I don't know what to do here.
Click to expand...
Click to collapse
Let try this using the version just above your base version:
Download, rename to firmware.zip and place in your adb/fastboot folder: firmware 5.14.531.1
Boot into bootloader/FASTBOOT USB
Type:
Code:
[B][I]fastboot oem lock[/I][/B]
Type:
Code:
[B][I]fastboot oem rebootRUU [/I][/B]
NOTE: You should see a silver HTC logo come up on your phone after executing this command.
NOTE: if this command freezes, just disconnect the USB cable and hold the power and volume down buttons until the device reboots. Then, repeat the steps above again.
Finally:
Code:
[B][I]fastboot flash zip firmware.zip[/I][/B]
Repeat the same command: IMPORTANT
Code:
[B][I]fastboot flash zip firmware.zip[/I][/B]
NOTE: The green bar on the phone may not go to 100% of the bar ... but If you see completed on your computer command window, wait for a few seconds and move on.
Last Step:
Code:
[B][I]fastboot reboot[/I][/B]
Click to expand...
Click to collapse
Now run this RUU 5.14.531.1
If this is successful you can try to achieve S-OFF with firewater. Of course, you will need to unlock your bootloader and install TWRP 2.6.3.3 recovery. Or, you can retry the RUU in alray's post.
majmoz said:
Let try this using the version just above your base version:
Download, rename to firmware.zip and place in your adb/fastboot folder: firmware 5.14.531.1
Now run this RUU 5.14.531.1
If this is successful you can try to achieve S-OFF with firewater. Of course, you will need to unlock your bootloader and install TWRP 2.6.3.3 recovery. Or, you can retry the RUU in alray's post.
Click to expand...
Click to collapse
Thanks. This restored the phone to a usable state. I'm going to try firewater now.
Requirements:
you need to have a pc with adb working
a stock firmware on your device (any)
unlocked bootloader
a working backup just in case
Pro:
you will not lose your data / application
Cons:
you will lose all system modification (root, busybox, custom kernel...)
you'll take all the risk of operation (I've tested on my device)
Guide:
some file names changes depending on version so please complete the {version_here} placeholder with the file you download
* prepend "sudo" on command line if you are on a Linux machine
download last version for your device here (if you want to root download the zip file in the section below to speed up the operations)
extract
extract image-{device_here}-{version_here}.zip in the same folder (no subdir)
command line* (or reboot device with vol down pressed):
Code:
adb reboot bootloader
command line*:
Code:
cd {your_path_here}
command line*:
Code:
fastboot flash bootloader bootloader-{device_here}-{version_here}.img
command line*:
Code:
fastboot reboot-bootloader
command line*:
Code:
fastboot flash radio radio-{device_here}-{version_here}.img
command line*:
Code:
fastboot flash system system.img
command line*:
Code:
fastboot flash boot boot.img
ONLY IF YOU FOUND A VENDOR.IMG IN THE ZIP command line*:
Code:
fastboot flash vendor vendor.img
command line*:
Code:
fastboot flash cache cache.img
command line*:
Code:
fastboot reboot
Now you have the lastest stock image and all your data.
Change recovery (TWRP) and root:
Note that we haven't flash the stock recovery, but during every boot of an unmodified system there's a script that do that (supersu usually deactive this behavior during install).
If you had TWRP installed and the SuperSU zip on your device, at the end of the above procedure you can boot directly from bootloader to recovery and go directly to last step:
download: TWRP image (twrp-{version_here}-{device_here}.img) for your device
download: chainfire SuperSU 2.71 on your device
command line*:
Code:
fastboot flash recovery twrp-{version_here}-{device_here}.img
alternatively you can keep the original recovery and use TWRP one time with
Code:
fastboot boot twrp-{version_here}-{device_here}.img
boot in recovery and flash supersu zip
working fine for me, all correct, thanks
Just tried with flash_all.bat. I'm getting the message "Can not generate image". How can I solve this, please?
Thank you, works like a charm!
Same here, cant flash system
There's not flash-all.bat in my steps (that delete you data!), can't give help about it sorry
i've gone your way, but i tried also the flash-all.bat with the -w switch, didnt work.
Tnx mate. Helped a lot
Cant flash the system.img manually. All the other img are working. I get this error message :
Code:
target reported max download size of 1073741824 bytes
error: cannot load 'system.img'
The old system.img from lrx22c works also.
Someone know whats going on?
Sp0KI said:
Cant flash the system.img manually. All the other img are working. I get this error message :
Code:
target reported max download size of 1073741824 bytes
error: cannot load 'system.img'
The old system.img from lrx22c works also.
Someone know whats going on?
Click to expand...
Click to collapse
I think that all who has flashed the developer preview got an broken filesystem or the partitions missmatch.
Before i used the preview the -w update flag worked well to rebuild the partitions, now it didnt work anymore, tried all factory images don to 4.4
c3k said:
Requirements:
you need to have a pc with adb working
a stock firmware on your device (any)
a working backup just in case
Click to expand...
Click to collapse
so if i have twrp, before i have to return stock 5.0.1??
or i flash directly 5.1 over twrp?
tnx
chikess said:
I think that all who has flashed the developer preview got an broken filesystem or the partitions missmatch.
Before i used the preview the -w update flag worked well to rebuild the partitions, now it didnt work anymore, tried all factory images don to 4.4
Click to expand...
Click to collapse
I didn't flash the preview.
Sp0KI said:
I didn't flash the preview.
Click to expand...
Click to collapse
Hmm ok, but u got the same problems. So, in this way we had to wait for a flashable zip or maybe ota.
@c3k why do you mention to flash twrp while in steps above stock recovery is not included to flash... ? Doesn't that mean that custom recovery (twrp) is still on device?
Doesn't this require an unlocked bootloader, and not necessarily root, or am I confused?
Sp0KI said:
Cant flash the system.img manually. All the other img are working. I get this error message :
Code:
target reported max download size of 1073741824 bytes
error: cannot load 'system.img'
The old system.img from lrx22c works also.
Someone know whats going on?
Click to expand...
Click to collapse
Are you using the latest version for the fastboot.exe file?
foosion said:
Doesn't this require an unlocked bootloader, and not necessarily root, or am I confused?
Click to expand...
Click to collapse
This requires an unlocked bootloader. But, there are users like us who have rooted the stock ROM.
This guide is meant for the users who has unlocked bootloader with rooted stock ROM.
This guide will also work for phones with unlocked bootloaders with STOCK ROM(rooted or un-rooted).
efrant said:
Are you using the latest version for the fastboot.exe file?
Click to expand...
Click to collapse
I had faced the same issue while flashing LRX22C. It got fixed by rebooting the phone and switching the cable to a different USB port. Might work for him too.
PS: I have flashed the images from Linux.
In my case I guess all the issues are from a previous attempt to flash OptiPop ROM. The flashing process it's a little tricky to understand (with that F2FS file system). I remember that after flashed OptiPop and the phone didn't boot, I tried to restore to stock ROM and it was a lot of errors until it worked fine again.
efrant said:
Are you using the latest version for the fastboot.exe file?
Click to expand...
Click to collapse
I'm using the newest Minimal ADB.
The strange thing is, that i can flash the LRX22C system.img and all other new lmy47d files but not the lmy47d system.img.
I guess i'll wait for the OTA update and hope it works then.
Tried rebooting and switching port and usb cabel..
You actually don't need to manually install supersu or root. Flash the 5.1 images and then (after the first full boot) flash twrp.
Once you boot into twrp and exit out of it, you will be promoted with a message that your phone is not rooted, and you're asked if you want to install supersu. It's built into twrp.