I have been trying to unbrick my phone for 2 days now. So right now when I boot it goes through the boot screens then it goes black and just says
"process system ins't responding" , so if i press wait that error will just pop up again. Otherwise all I get is a black screen and have to force reboot.
So here is what I have done so far:
When bought phone I did S-OFF and have it unlocked "I believe it was with firewater, but that was months ago",
Installed CWM 6.0.4.8 <--im pretty sure thats the one.
Created nandroid
Then I installed SKYFALL and used that ever since.
Decided I wanted ViperOne.
Read many post and here is where the fun started.
Restored my origional nandroid.
fastboot flashed stock recovery then erase cache
booted nandroid. and installed downloaded 4.4.3 OTA
phone rebooted just fine.
fastboot flashed twrp recovery (openrecovery-twrp-2.8.0.3-m8_wlv.img) then erase cache
booted recovery and installed ViperOne.
then error process system isn't responding.
Since then I have repeated those steps. I have also tried CleanRom and RKDN and those get stuck in loading loops. I have tried the RUU options, and tried RUU and fastboot to get back to the 1.55.605.2 completely stock as it can be with a stock image or the nandroid and nothing seems to work. Just get the same errors. Now I am stuck and unsure what to do or how to go about fixing this....
Not sure if you've already tried this, but might help.
Load the RUU from here http://forum.xda-developers.com/ver...ent/ruu-m8vzw-4-4-3-s-off-onlynewest-t2873144
After that, go into the stock recovery and do a factory reset.
dab1414 said:
I have been trying to unbrick my phone for 2 days now. So right now when I boot it goes through the boot screens then it goes black and just says
"process system ins't responding" , so if i press wait that error will just pop up again. Otherwise all I get is a black screen and have to force reboot.
So here is what I have done so far:
When bought phone I did S-OFF and have it unlocked "I believe it was with firewater, but that was months ago",
Installed CWM 6.0.4.8 <--im pretty sure thats the one.
Created nandroid
Then I installed SKYFALL and used that ever since.
Decided I wanted ViperOne.
Read many post and here is where the fun started.
Restored my origional nandroid.
fastboot flashed stock recovery then erase cache
booted nandroid. and installed downloaded 4.4.3 OTA
phone rebooted just fine.
fastboot flashed twrp recovery (openrecovery-twrp-2.8.0.3-m8_wlv.img) then erase cache
booted recovery and installed ViperOne.
then error process system isn't responding.
Since then I have repeated those steps. I have also tried CleanRom and RKDN and those get stuck in loading loops. I have tried the RUU options, and tried RUU and fastboot to get back to the 1.55.605.2 completely stock as it can be with a stock image or the nandroid and nothing seems to work. Just get the same errors. Now I am stuck and unsure what to do or how to go about fixing this....
Click to expand...
Click to collapse
I can team viewer with you and checkout what's up. What error do you get on RUU flashing?
jsaxon2 said:
Not sure if you've already tried this, but might help.
Load the RUU from here http://forum.xda-developers.com/ver...ent/ruu-m8vzw-4-4-3-s-off-onlynewest-t2873144
After that, go into the stock recovery and do a factory reset.
Click to expand...
Click to collapse
I had this ruu already, and the MD5 matched up. So I downloaded a new copy anyways, However I am unable to flash it. On another note I did try other non 443 rru's that did flash but factory reset did not work.
dottat said:
I can team viewer with you and checkout what's up. What error do you get on RUU flashing?
Click to expand...
Click to collapse
when trying to flash
Code:
C:\Users\balddav\My Documents\M8\ruu\443>fastboot oem rebootRUU
C:\Users\balddav\My Documents\M8\ruu\443>fastboot flash zip 0P6BIMG.zip
target reported max download size of 1830711296 bytes
error: cannot load '0P6BIMG.zip'
Then I push file to root of external sd card:
once boot to HBOOT
Loading...[0P6BIMG.zip]
and after 1 hour still loading. then I tried to load 442 ruu and this:
Code:
C:\Users\balddav\My Documents\M8\ruu\442>fastboot flash zip 0P6BIMG.zip
target reported max download size of 1830711296 bytes
sending 'zip' (825739 KB)...
OKAY [ 35.882s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) shift signature_size for header checking...
FAILED (remote: 32 header error)
finished. total time: 36.033s
I can ruu the 443 firmware from this post http://forum.xda-developers.com/showthread.php?t=2723159with no issues.
dab1414 said:
I had this ruu already, and the MD5 matched up. So I downloaded a new copy anyways, However I am unable to flash it. On another note I did try other non 443 rru's that did flash but factory reset did not work.
when trying to flash
Code:
C:\Users\balddav\My Documents\M8\ruu\443>fastboot oem rebootRUU
C:\Users\balddav\My Documents\M8\ruu\443>fastboot flash zip 0P6BIMG.zip
target reported max download size of 1830711296 bytes
error: cannot load '0P6BIMG.zip'
Then I push file to root of external sd card:
once boot to HBOOT
Loading...[0P6BIMG.zip]
and after 1 hour still loading. then I tried to load 442 ruu and this:
Code:
C:\Users\balddav\My Documents\M8\ruu\442>fastboot flash zip 0P6BIMG.zip
target reported max download size of 1830711296 bytes
sending 'zip' (825739 KB)...
OKAY [ 35.882s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) shift signature_size for header checking...
FAILED (remote: 32 header error)
finished. total time: 36.033s
I can ruu the 443 firmware from this post http://forum.xda-developers.com/showthread.php?t=2723159with no issues.
Click to expand...
Click to collapse
Flash the firmware and then go right to RUU flashing via sd.
dottat said:
Flash the firmware and then go right to RUU flashing via sd.
Click to expand...
Click to collapse
I have tried that and it hangs on loading. But I will try it again.
When I woke up I noticed my phone actually booted up normally. I think what I did different was reformat external drive. Copy the 442 RUU to it. I flashed the 442 firmware, then reboot to hboot it loaded the RUU, went to sleep and it worked.
So when I get a chance today I will make sure I have a good copy of the 443 firmware and try it the same way I just did 442, and post my steps.
Thanks for your help so far.
removed
So I was just trying something out and downloaded the OTA update and installed it. Everything looked like it updated fine so I just rebooted and the error process system isn't responding came back when rebooting. So I am trying the 443 firmware and RUU.
One thing I noticed from this post http://forum.xda-developers.com/showthread.php?t=2723159 is there is no boot or recovery, so after flashing the 443 firmware, I flashed the boot and recovery images found on the same thread. then I inserted the sd card with the RUU from here http://forum.xda-developers.com/verizon-htc-one-m8/development/ruu-m8vzw-4-4-3-s-off-onlynewest-t2873144 and this time HBOOT loaded the file and installed with no errors.
Now on booting up it still says Process system isn't responding.
dab1414 said:
So I was just trying something out and downloaded the OTA update and installed it. Everything looked like it updated fine so I just rebooted and the error process system isn't responding came back when rebooting. So I am trying the 443 firmware and RUU.
One thing I noticed from this post http://forum.xda-developers.com/showthread.php?t=2723159 is there is no boot or recovery, so after flashing the 443 firmware, I flashed the boot and recovery images found on the same thread. then I inserted the sd card with the RUU from here http://forum.xda-developers.com/ver...ent/ruu-m8vzw-4-4-3-s-off-onlynewest-t2873144 and this time HBOOT loaded the file and installed with no errors.
Now on booting up it still says Process system isn't responding.
Click to expand...
Click to collapse
You did not need to flash boot and recovery. In fact, the ruu will do that automatically for you.
Did your phone calm down? Sometimes on boot if blinkfeed and other apps try to update it can crash. . Reboot once more after that and see what happens.
dottat said:
You did not need to flash boot and recovery. In fact, the ruu will do that automatically for you.
Click to expand...
Click to collapse
I realized that shortly after I typed it, I looked in the zip files.
dottat said:
Did your phone calm down? Sometimes on boot if blinkfeed and other apps try to update it can crash. . Reboot once more after that and see what happens.
Click to expand...
Click to collapse
No my M8 is nothing but issues apparently. I have been rooting, unlocking, updating and installing ROMS for years now and I haven't had so many issues. Usually just my own mistakes, which this is probably one of them. I have done so much before I asked for help I couldn't tell you exactly what I did. If I would have read more then I wouldn't have gone the OTA route.
Right now I have not been able to get 442 or 443 to work. Here is a link to the picture right after I flashed firmware through RUU then hboot loaded 0P6BIMG.zip
https://www.dropbox.com/s/feu0tkkfkzyso67/Photo%20Oct%2016%2C%2023%2039%2048.jpg?dl=0
Then when it boots up it goes from verizon logo to the error. Here is a link to video I made of that boot process.
https://www.dropbox.com/s/wfnd0bxh6zz2bwh/Video%20Oct%2016%2C%2023%2042%2033.mov?dl=0
I have tried rebooting several times with the same results.
dab1414 said:
I realized that shortly after I typed it, I looked in the zip files.
No my M8 is nothing but issues apparently. I have been rooting, unlocking, updating and installing ROMS for years now and I haven't had so many issues. Usually just my own mistakes, which this is probably one of them. I have done so much before I asked for help I couldn't tell you exactly what I did. If I would have read more then I wouldn't have gone the OTA route.
Right now I have not been able to get 442 or 443 to work. Here is a link to the picture right after I flashed firmware through RUU then hboot loaded 0P6BIMG.zip
https://www.dropbox.com/s/feu0tkkfkzyso67/Photo Oct 16, 23 39 48.jpg?dl=0
Then when it boots up it goes from verizon logo to the error. Here is a link to video I made of that boot process.
https://www.dropbox.com/s/wfnd0bxh6zz2bwh/Video Oct 16, 23 42 33.mov?dl=0
I have tried rebooting several times with the same results.
Click to expand...
Click to collapse
I'm at a loss, the only other thing I could tell you to try would be to remove the sdcard and try rebooting.
I have a few comments. Go back and flash the 4.4.3 RUU from fastboot. Make sure your SDK is up to date with the latest and greatest. Your firmware is ok. In looking through your log from the fastboot attempt, you got error - Failed (remote: 32 header error). This means the zip couldn’t be read and unzipped properly. Something is borked. Make sure you have lots of room on your internal SD card too.
dab1414 said:
I realized that shortly after I typed it, I looked in the zip files.
No my M8 is nothing but issues apparently. I have been rooting, unlocking, updating and installing ROMS for years now and I haven't had so many issues. Usually just my own mistakes, which this is probably one of them. I have done so much before I asked for help I couldn't tell you exactly what I did. If I would have read more then I wouldn't have gone the OTA route.
Right now I have not been able to get 442 or 443 to work. Here is a link to the picture right after I flashed firmware through RUU then hboot loaded 0P6BIMG.zip
https://www.dropbox.com/s/feu0tkkfkzyso67/Photo Oct 16, 23 39 48.jpg?dl=0
Then when it boots up it goes from verizon logo to the error. Here is a link to video I made of that boot process.
https://www.dropbox.com/s/wfnd0bxh6zz2bwh/Video Oct 16, 23 42 33.mov?dl=0
I have tried rebooting several times with the same results.
Click to expand...
Click to collapse
You could have hosed partitions. I can team viewer and try a couple things to see if we can get it fixed.
jsaxon2 said:
I'm at a loss, the only other thing I could tell you to try would be to remove the sdcard and try rebooting.
Click to expand...
Click to collapse
Irieone said:
I have a few comments. Go back and flash the 4.4.3 RUU from fastboot. Make sure your SDK is up to date with the latest and greatest. Your firmware is ok. In looking through your log from the fastboot attempt, you got error - Failed (remote: 32 header error). This means the zip couldn’t be read and unzipped properly. Something is borked. Make sure you have lots of room on your internal SD card too.
Click to expand...
Click to collapse
dottat said:
You could have hosed partitions. I can team viewer and try a couple things to see if we can get it fixed.
Click to expand...
Click to collapse
Finally!!! Thank you all for the help.
So I removed my sdcard, then installed twrp, then went and advanced wipe and selected every box ( all i did before was factory resets). Then flashed firmware through ruu mode. Then reinserted sdcard with the 0P6BIMG file. rebooted to bootloader selected hboot, then when done rebooted and it was working fine. then reinstalled twrp and installed viperone, and rolling through just fine. Guess there was something floating around the factory reset didnt wipe.
Again thank you all for your time and help to resolve my screwup!!
dab1414 said:
Finally!!! Thank you all for the help.
So I removed my sdcard, then installed twrp, then went and advanced wipe and selected every box ( all i did before was factory resets). Then flashed firmware through ruu mode. Then reinserted sdcard with the 0P6BIMG file. rebooted to bootloader selected hboot, then when done rebooted and it was working fine. then reinstalled twrp and installed viperone, and rolling through just fine. Guess there was something floating around the factory reset didnt wipe.
Again thank you all for your time and help to resolve my screwup!!
Click to expand...
Click to collapse
Yeah....I think your partition was wonked. Twrp even has a repair option built in now for ext4 partitions under advanced wipe.
Related
Hey guys, I'd really appreciate a hand with this one:
My OneX wasn't able to install the update from rogers. The phone was rooted, but was running stock and did NOT have CWM. I tried the update many times, but always got a red triangle icon while installing. The phone would then reboot into the old version.
I did a factory reset, which removed root, but the update still fails.
Now I'm trying to install the rogers RUU and see if that will make the update work.
The phone is now unrooted. Recovery says: Locked, Tampered
I got my hands on the following RUU and extracted it.
PJ83IMG_Evita_UL_Rogers_WWE_1.73.631.1_Radio_0.16a.32.09.06_10.81.32.14L_release_254934_signed.zip
I ran:
Code:
fastboot flash boot boot_signed.img
And got this error:
Code:
sending 'boot' (6236 KB)... OKAY
writing 'boot'... INFOsignature checking...
FAILED (remote: signature verify fail)
Does this mean that it needs to be unlocked to install the RUU? I thought it does not need to be unlocked because the RUU files are signed.. Is that true?
Any ideas how I can get the RUU working, or other ways to make the update work?
Thanks in advance
SOLVED:
1. I updated to the latest version of HTC Sync Manage. I used the link that opens when windows detects the phone being connected, NOT the one that is available on the HTC website. I disabled antivirus while installing it.
2. I followed these instructions: http://forum.xda-developers.com/showthread.php?t=1658929
When doing step 2, I moved my RUU zip (with the really long name mentioned above) into the ARUWizard folder and renamed it to "rom.zip".
i think your supposed to do this method http://forum.xda-developers.com/showthread.php?t=1658929
DvineLord said:
i think your supposed to do this method http://forum.xda-developers.com/showthread.php?t=1658929
Click to expand...
Click to collapse
I can confirm this works as I did this a few months ago.
Thanks for the replies guys!
I gave it a shot, but my phone hangs at a silver HTC logo when it is supposed to be rebooting into the bootloader... ARUWizard says "waiting for bootloader..." and eventually times out. The phone stays stuck at the silver logo till I restart it.
I found this: http://forum.xda-developers.com/showthread.php?p=27882810#post27882810
Which suggests the following commands instead of using ARUWizard:
Code:
fastboot oem rebootRUU
fastboot flash zip ruu.zip
But I get the same thing: freeze before going to the bootloader with a silver HTC logo.
Any ideas?
start the phone in bootloader then try it?
I updated to the latest version of HTC Sync Manager and now it seems to be working!
Says: "Sending..."
EDIT: Yep, it worked. Thanks guys.
All,
Long time lurker, first time poster. I've been doing a bunch of reading for the past few hours, I think my phone isn't completely f***, I'm just missing something simple.
So basically, I started with a stock HTC One XL with Telstra. Updated to the latest firmware version (3.17) and bootloader 2.14.
1. I unlocked the bootloader using htcdev. Installed CM10.1 smoothly, booted into the ROM and realised the touch screen didnt work (now I realise that's the new firmware problem).
2. Booted back into recovery (TWRP 2.4.1) and accidently wiped my SD card along with everything else (including backups).
3. Mounted SD card, and formatted it with FAT32. Put Viper 3.2.7 on it and installed it via recovery ---> Stuck in a boot loop. Phone boots to the Viper screen, does a bit of loading, and then re-boots. (I have also tried this with various other sense based ROMs, with the same problem).
4. After a bit of reading, I tried to manually load the boot.img file via fastboot. I get the following error message: FAILED: <remote: signature verify fail>.
So now I turn to you for help! After 3 years with Android, I have never had trouble flashing new ROMs following the instructions on this awesome site. I hope you guys can help me out on this one. All my phone content is backed up on my PC, so my only concern is getting a working ROM again.
So in summary, what I am able to do is:
- Boot to bootloader (which is unlocked)
- I DO NOT have s-off
- I can boot to TWRP recovery and mount my SD to copy any file across
I have not tried running RUU yet, leaving that as a last resort.
brad.cap said:
All,
Long time lurker, first time poster. I've been doing a bunch of reading for the past few hours, I think my phone isn't completely f***, I'm just missing something simple.
So basically, I started with a stock HTC One XL with Telstra. Updated to the latest firmware version (3.17) and bootloader 2.14.
1. I unlocked the bootloader using htcdev. Installed CM10.1 smoothly, booted into the ROM and realised the touch screen didnt work (now I realise that's the new firmware problem).
2. Booted back into recovery (TWRP 2.4.1) and accidently wiped my SD card along with everything else (including backups).
3. Mounted SD card, and formatted it with FAT32. Put Viper 3.2.7 on it and installed it via recovery ---> Stuck in a boot loop. Phone boots to the Viper screen, does a bit of loading, and then re-boots. (I have also tried this with various other sense based ROMs, with the same problem).
4. After a bit of reading, I tried to manually load the boot.img file via fastboot. I get the following error message: FAILED: <remote: signature verify fail>.
So now I turn to you for help! After 3 years with Android, I have never had trouble flashing new ROMs following the instructions on this awesome site. I hope you guys can help me out on this one. All my phone content is backed up on my PC, so my only concern is getting a working ROM again.
So in summary, what I am able to do is:
- Boot to bootloader (which is unlocked)
- I DO NOT have s-off
- I can boot to TWRP recovery and mount my SD to copy any file across
I have not tried running RUU yet, leaving that as a last resort.
Click to expand...
Click to collapse
FAILED: <remote: signature verify fail> means your bootloader is locked.
exad said:
FAILED: <remote: signature verify fail> means your bootloader is locked.
Click to expand...
Click to collapse
But it says **** UNLOCKED **** (as well as **** TAMPERED ****) at the top of the bootloader?
brad.cap said:
But it says **** UNLOCKED **** (as well as **** TAMPERED ****) at the top of the bootloader?
Click to expand...
Click to collapse
what is the command you used to load the boot.img and where did the boot.img come from?
on an unrelated note. flash twrp 2.3.3.1 instead every version above has issues wiping leading to issues not unlike yours.
after flashing 2.3.3.1 dont forget to do fastboot erase cache.
exad said:
FAILED: <remote: signature verify fail> means your bootloader is locked.
Click to expand...
Click to collapse
exad said:
what is the command you used to load the boot.img and where did the boot.img come from?
on an unrelated note. flash twrp 2.3.3.1 instead every version above has issues wiping leading to issues not unlike yours.
after flashing 2.3.3.1 dont forget to do fastboot erase cache.
Click to expand...
Click to collapse
I use "fastboot flash flash boot.img", the boot.img is extracted from the zip of the Viper ROM that is installed on my phone.
Will do! Will this help with the situation at hand? I'd rather keep as many factors static as possible. I'll flash twrp 2.3.3.1 once everything is resolved (unless it can help now?)
brad.cap said:
I use "fastboot flash flash boot.img", the boot.img is extracted from the zip of the Viper ROM that is installed on my phone.
Will do! Will this help with the situation at hand? I'd rather keep as many factors static as possible. I'll flash twrp 2.3.3.1 once everything is resolved (unless it can help now?)
Click to expand...
Click to collapse
Flash it now then try flashing again after wiping everything on 2.3.3.1
Sent from my HTC One X using xda app-developers app
brad.cap said:
I use "fastboot flash flash boot.img", the boot.img is extracted from the zip of the Viper ROM that is installed on my phone.
Will do! Will this help with the situation at hand? I'd rather keep as many factors static as possible. I'll flash twrp 2.3.3.1 once everything is resolved (unless it can help now?)
Click to expand...
Click to collapse
the command is fastboot flash boot boot.img btw.
but yes flash 2.3.3.1 first then fastboot erase cache then the boot img.
if you experience bugs that are not discussed in the ROMs op do a fresh wipe everything and reflash the rom because wiping with 2.4 probably wasn[t a clean wipe.
exad said:
the command is fastboot flash boot boot.img btw.
but yes flash 2.3.3.1 first then fastboot erase cache then the boot img.
if you experience bugs that are not discussed in the ROMs op do a fresh wipe everything and reflash the rom because wiping with 2.4 probably wasn[t a clean wipe.
Click to expand...
Click to collapse
Thanks. Will try that now.
Edit: Yep. That worked. Viper booted up fine and everything is working!
I'm going to make a back-up of this working ROM now, and have another go at getting CM10.1 to work.
Thanks for your help guys, really appreciate it. Especially exad.
Good day everyone.
I relocked and installed stock RUU (4.0.3) on my Evita since I had that failing zip install though TWRP. It worked fine but when I tried to manually install the latest RUU (Android 4.1) it failed. Now I decided to unlock it again and start to flash custom ROMs, problem started.
1.) After flashing boot, recovery and custom rom (tried it with CM 10.1 and JellyBam), it would go only up to the boot image (HTC) and stay on there forever. Cleared everything that I could clear on the recovery and cleared fastboot cache.
What I did, relocked it again and tried running the stock RUU (through the computer) and shows error and won't complete.
2.) Now, phone no longer recognizes the Unlock_code.bin from HTC dev. I tried manually flashing it in fastboot and as well as using the All-in-one-tool for Evita, it would somehow show that it went through on both but looking at my phone, it stays: Relocked. Tried it with at least three unlock bin files to no avail.
3.) Other than that, turning the phone off and back on would go straight to bootloader. When I select Recovery, it would go back straight to fastboot mode. Tried to flash recoveries again, and would get this:
E:\Mobile Devices\sd-fix\Nocturnal_SD_FIX_EVITA\Nocturnal_SD_FIX_EVITA>fastboot
flash recovery openrecovery-twrp-2.5.0.0-evita.img
sending 'recovery' (7992 KB)... OKAY [ 2.140s]
writing 'recovery'... INFOsignature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.871s
E:\Mobile Devices\sd-fix\Nocturnal_SD_FIX_EVITA\Nocturnal_SD_FIX_EVITA>fastboot
flash recovery openrecovery-twrp-2.2.0-evita.img
sending 'recovery' (7460 KB)... OKAY [ 1.692s]
writing 'recovery'... INFOsignature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.370s
Now I'm stuck with a phone with no OS. Please help. I appreciate your time.
Here's my phone info.
AT&T HTC One X
S-ON
HBOOT - 2.14.0000
Getting a new code only requires fast boot. So just get a new unlock code.....
*edit*
Sorry I misread. This happened to me. Just simulate a battery pull by pressing and holding power and try again. Keep doing that over and over. Eventually, it will work.
Took me about 10-15 tries once.
Sent from my One X using xda app-developers app
Also try to lock the phone even if it tells you it is already locked.
fastboot oem lock
Do that prior to attempting the unlock after full power cycle. Sometimes that gets the device back on track, dont worry too much this issue is not exactly new and after a bit of dicking around the phone will unlock again.
Thanks for your responses!
Yeah, it did. After a number times requesting for unlock bins and re locking, finally it was unlocked.
Now I now have problem #1 from OP. It actually goes to HTC boot screen, stays there for a couple of seconds then reboot. It's been doing that in a loop. Flashed three different ROMs and three different versions of TWRP and phone still does the same thing.
Found my mainver to be 3.18 which I suspect have been changed when I attempted to run the 4.1 RUU (this was before I tried to unlock the bootloader). Downloaded the said RUU from two different sites just to be sure. None of those have worked.
So I found a thread here in XDA saying that this could be the reason why I couldn't boot any of these ROMs.
Any thoughts/help would be greatly appreciated.
Must not have read very much before trying to root if you don't know fastboot flash boot boot.Img
Sent from my One X using xda app-developers app
You're s-on so you need to flash the boot.img manually on hboot 2.14.
Retrieve the boot.img from the ROM zip and place it in your working directory on your pc.
Copy ROM to phone (if you haven't already done that).
Do a full wipe in recovery, then flash the ROM.
Reboot to the bootloader, connect phone to pc, make sure it says fastboot usb on your phone screen.
Open a command prompt in your working directory and issue the following command:
fastboot flash boot boot.img
Reboot the phone.
Enjoy.
Sent from my Evita
Typically bootloops are solved by
flashing recovery cwm or twrp.
wipe cache, data and system.
Manual install the boot.ing from rom you are installing.
Fastboot flash boot boot.img
Install your rom in recovery.
Hopefully all will work then
Sent from my HTC One XL using xda app-developers app
exad said:
Must not have read very much before trying to root if you don't know fastboot flash boot boot.Img
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
timmaaa said:
You're s-on so you need to flash the boot.img manually on hboot 2.14.
Retrieve the boot.img from the ROM zip and place it in your working directory on your pc.
Copy ROM to phone (if you haven't already done that).
Do a full wipe in recovery, then flash the ROM.
Reboot to the bootloader, connect phone to pc, make sure it says fastboot usb on your phone screen.
Open a command prompt in your working directory and issue the following command:
fastboot flash boot boot.img
Reboot the phone.
Enjoy.
Sent from my Evita
Click to expand...
Click to collapse
twistedddx said:
Typically bootloops are solved by
flashing recovery cwm or twrp.
wipe cache, data and system.
Manual install the boot.ing from rom you are installing.
Fastboot flash boot boot.img
Install your rom in recovery.
Hopefully all will work then
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse
It's actually my fourth device. Did flash boot.img all the time. That's why it's kind of frustrating.
Any thoughts about damaged eMMC? Just hypothetical.
I don't know if it was a brick but I had an issue before where this HOXL didn't boot up after flashing a wrong kernel. Didn't even light up when plugged to power and had to re-flash the eMMC block using that WIP method. It went back to life.
Might need to try that again. Would that be possible? Still have to download live ubuntu, though. The one I used before got corrupted.
What I did so far:
-relock
-unlock
-erased fastboot cache
-flashed boot.img ( from the custom ROMs that I've tried )
-flashed twrp ( 3 versions )
-wiped every wipe option i could see
I already have tested at least 6 ROMs on this device with no issue with TWRP.
I had ViperXL installed before this happened. I wiped everything out and tried to flash the ATT Android 4.1 RUU and everything got screwed.
edit: i typed the capcha on the title box. lol
You're still s-on right?
Sent from my One X using xda app-developers app
exad said:
You're still s-on right?
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
Yup!
Is there a way to s-off while you're on fastboot? Facepalm method requires it on booted android. So far can't see other procedures done through fastboot.
EjWilkes0121 said:
Yup!
Is there a way to s-off while you're on fastboot? Facepalm method requires it on booted android. So far can't see other procedures done through fastboot.
Click to expand...
Click to collapse
Get twrp running 2.3.3.1 and flash any sense Rom then s-off
Sent from my HTC One XL using xda premium
I'm going to try again once I get home from work.
Thanks for all your responses guys.
Done it all.
Relocked, intalled RUU - fail.
Unlocked, wiped everything, installed ROM, erased fastboot cache, flashed boot.img, erased fastboot cache - bootloop.
Tried using CWM and same thig happes - bootloops after flashing rom and boot.img
However, I just noticed something.
Whenever I get to flash a zip through recovery, process seems to just complete in no time. I have flashed multiple ROMs and one could really see progress shown on progress bar on both recovery flashing( CM10.1, JellyBam ) and through Aroma installer( CleanROM, ViperXL ).
When this problem started, entire process would initiate, pauses for few seconds then it completes. Can't see the progress bar move across.
I might be going out of topic here but I'm desperate in having this fixed.
Your thoughts and ideas means a lot.
Are there any roms you can boot?? How are you downloading the files? On a pc? Did the md5 match. Maybe the usb wire has a defect and screws the file upon transfer. Your have a really strange issue. I'll flash out of boredom and never had that happen, Even with roms that do nothing more than boot.
And your running twrp 2.3.3.1???
Sent from my HTC One XL using xda premium
I think the recovery is most likely at fault here.
Make sure it's twrp 2.3.3.1: http://goo.im/devs/OpenRecovery/evita/openrecovery-twrp-2.3.3.1-evita.img
Use a USB 2.0 port just to be safe.
check md5 omg so important!
Code:
fastboot erase recovery
fastboot flash recovery openrecovery-twrp-2.3.3.1-evita.img
fastboot erase cache
fastboot reboot bootloader
Select recovery
Check the md5 of the sense rom you downloaded
Extract boot.img from rom.
Transfer the rom zip to the phone.
wipe cache, dalvik, system and factory reset in recovery
install sense rom
reboot to bootloader
Code:
fastboot flash boot boot.img
fastboot reboot
Do all that and then tell me what happens.
Back to life!
A huge thanks to you guys! Big time! :victory:
It could be the recovery that screwed it up. Been trying TWRP 2.5 and TWRP 2.2 most of the time. I gave TWRP 2.6 a shot and that made a successful install. I flash ViperXL 3.2.7 + ElementalX 6.7 and phone's back to life!
One thing i noticed. After I S-Off'ed, phone's kind of jerky using normal use. One noticeable thing is the lock screen that doesn't respond after waking, takes 1-2 sec to respond when swiping the lock ring. Big prob for me, battery stuck at 77% even when charged or used heavily. Random reboots also happen. Maybe have to read the entire FacePalm S-Off thread this week. LoL. For now, back to S-On, phone works perfect.
Again, thanks so much for your help guys! Won't be missing any Thank button that you got. :laugh:
I found current sense roms work better with latest firmware so s-off ruu to 3.18 and then see how things run.
Sent from my HTC One X using xda app-developers app
Hey guys,
So this morning I stupidly tried to update to 4.4.4 since the phone said it has an update available. I was rooted running a few xposed modules, so I did the update, everything was fine, then upon getting back into the OS system.ui kept crashing every 3 seconds.
"Okay, just go use your Nandroid back up and flash via TWRP like always" I thought. So I did exactly that - rebooted to recovery, and went to flash my backup and it just sat there at "writing system" and did nothing. Next I rebooted to recovery again and did a full wipe of the OS - userdata and all, then tried two different toolkits (Mac and PC) and THEY got stuck at the 'writing system' as well.
Now I'm trying to flash stock to get my damn phone working via fastboot, but when i use the command fastboot flash userdata userdata_64g.img I get my cmd window saying "target reported max download size of 536870912 bytes erasing 'userdata'..."
This has been displaying for about 25 minutes now and I don't know what to do... Do I just leave it? Clearly something's not working. If this is an issue, what do I do to get around it and get back to android? How can I make the phone work again? I've flashed and reflashed stuff before but why is it seemingly busted now?
Help....anyone?
(FYI Since I have no phone, replies might be very sparse throughout the day because I can't actually check this thread and have to now go to work.)
Talnoy said:
Hey guys,
So this morning I stupidly tried to update to 4.4.4 since the phone said it has an update available. I was rooted running a few xposed modules, so I did the update, everything was fine, then upon getting back into the OS system.ui kept crashing every 3 seconds.
"Okay, just go use your Nandroid back up and flash via TWRP like always" I thought. So I did exactly that - rebooted to recovery, and went to flash my backup and it just sat there at "writing system" and did nothing. Next I rebooted to recovery again and did a full wipe of the OS - userdata and all, then tried two different toolkits (Mac and PC) and THEY got stuck at the 'writing system' as well.
Now I'm trying to flash stock to get my damn phone working via fastboot, but when i use the command fastboot flash userdata userdata_64g.img I get my cmd window saying "target reported max download size of 536870912 bytes erasing 'userdata'..."
This has been displaying for about 25 minutes now and I don't know what to do... Do I just leave it? Clearly something's not working. If this is an issue, what do I do to get around it and get back to android? How can I make the phone work again? I've flashed and reflashed stuff before but why is it seemingly busted now?
Help....anyone?
(FYI Since I have no phone, replies might be very sparse throughout the day because I can't actually check this thread and have to now go to work.)
Click to expand...
Click to collapse
I would try to download another ROM like Cm m9 and see if that will boot.
Sent from my A0001 using Tapatalk
I have an HTC A9 (mid: 2PQ910000 / cid: VODAP001) which is S-ON currently. Up until yesterday it was running OEM HTC Nougat. I attempted to downgrade it to MM so I could run LineageOS using the VodaPhone 1.27.161.6 zip in collection thread (hxxps://forum.xda-developers.com/one-a9/general/wip-ruu-htc-one-a9-t3240344). Per the instructions in Post #2 I was able to edit partion 28 but when I attempt to actually flash the .zip both via the "SDCARD Method" and via the "rebootRUU Method" I get the cool errors below. Does anyone have any ideas? Or did I hose this real good? I should also mention the bootloader is unlocked and I do have TWRP flashed. I would be happy if I could get back to factory and ideally I'd like to get it so I can get Sunshine and get S-OFF so I can not worry about this kind of thing in the future.
[SDCARD Method Error]
12 RU_ZIP_ERROR
12 RU_ZIP_ERROR
FAIL 12 RU_ZIP_ERROR
[rebootRUU Method Error (Ubuntu Linux using htc_fastboot)]
sending 'zip' (1886913 KB)... FAILED (remote: data too large, 1932198913 > 939151360)
[rebootRUU Method Error (Win10Pro using htc_fastboot)]
load_file: could not allocate 1932198913 bytes
I was able to get this to downgrade to MM (1.27.161.6) but from there I was not able to get LineageOS (lineage-14.1-20170704-nightly-hiaeuhl-signed) to boot. It would keep dropping to the HBOOT screen. In case anyone else ends up with the sweet boot loop I ended up in I have listed what I did below in the unlikely event it helps someone.
1) Grab the 1.27.161.6 zip
2) Grab the RUU decryptor (hxxps://forum.xda-developers.com/chef-central/android/tool-universal-htc-ruu-rom-decryption-t3382928)
3) Using the RUU decryptor decrypt the zip file above. Grab the "boot.img" and "system.img" files in the "OUT_2PQ_[version]\system" folder.
4) Flash TWRP to the recovery partition
5) Boot into TWRP and flash the "boot.img" file to the boot partition and the "system.img" to the system partition. For whatever reason, my phone rebooted twice and on the third boot went to safe mode. I was trying to shut it down, so I may have forced it to safe boot. Regardless after one more boot it looks like everything is working with the older MM stock.
Maybe in a few days I will try to get S-OFF using Sunshine. For now I'm just glad to have a working phone again.