Related
Hello, I have a T-Mobile HTC Sensation 4G, and I've ran into some problems recently. I'm a basic-intermediate user when it comes to Android, but I can't find a solution specifically for this. It started with a small problem but got worse and worse until I couldn't even boot correctly.
I started out installing a small custom battery mod, but that led to a few problems with the notification bar (not a big deal).
Then I tried to revert to the stock battery to fix the problem, format cache and dalvik cache in recovery, and reset. Then I was put into an infinite boot loop with the HTC splash, but going into cwm recovery was still possible.
Then, in recovery, I could not access my sd card for some reason, so I shut off, reinserted the sd card, and remounted it, then I reset again.
Now, it's impossible to boot to android at all, and I am completely stuck at HBOOT/FASTBOOT, and cannot access recovery OR perform a hard reset.
If I try to reinstall cwm recovery, I get a partition update fail as well...
I have full root, s-off, etc.
ROM- InsertCoin 3.3.1
Kernel- Stock
Hboot- 1.17.1011
Clockwork version- 5.0.0.8
Any suggestions? Am I bricked? I can give more details if needed.
I think you could take a official RUU and rename to the same as if you were trying to flash CWR pm58img or whatever it is.... Don't have my files with me. It should reformat to stock. Hope it helps.
Sent from my HTC Sensation XE with Beats Audio using xda premium
neoissuperman said:
I think you could take a official RUU and rename to the same as if you were trying to flash CWR pm58img or whatever it is.... Don't have my files with me. It should reformat to stock. Hope it helps.
Sent from my HTC Sensation XE with Beats Audio using xda premium
Click to expand...
Click to collapse
Alright, thanks, I'll try that soon and see if it works.
Update: Unfortunately, I don't think I can flash anything, it just comes up with a partition update fail...
Anyone else know what I could try? I also tried to flash the 1.45 RUU, but it can't continue past the search for the bootloader.
If u can get to fastboot have u tried manually flashing recovery.img ie
Fastboot flash recovery recovery.img
This should work if u can get into fastboot and allow u to then get back to a recovery and may save ya life lol
Sent from my mind control device
joshndroid said:
If u can get to fastboot have u tried manually flashing recovery.img ie
Fastboot flash recovery recovery.img
This should work if u can get into fastboot and allow u to then get back to a recovery and may save ya life lol
Sent from my mind control device
Click to expand...
Click to collapse
I just tried that, but I get this error in the terminal-
"writing 'recovery'... FAILED (remote: image update error)"
I tried adb devices, and it's not even recognized, even though my sensation says FASTBOOT USB...
have you tried re-installing the drivers...
http://forum.xda-developers.com/showthread.php?t=1161769
from here to see if the phone will re-mount the phone...
also have you tried adb remount... see if that works?
personally im running out of ideas
joshndroid said:
have you tried re-installing the drivers...
http://forum.xda-developers.com/showthread.php?t=1161769
from here to see if the phone will re-mount the phone...
also have you tried adb remount... see if that works?
personally im running out of ideas
Click to expand...
Click to collapse
Nope, still nothing, I even tried different sd cards and usb cables, with no difference...
So has my phone been reduced to a paperweight?
APmoss13 said:
I just tried that, but I get this error in the terminal-
"writing 'recovery'... FAILED (remote: image update error)"
I tried adb devices, and it's not even recognized, even though my sensation says FASTBOOT USB...
Click to expand...
Click to collapse
ummmm just a quick questions.... if you are on the fastboot screen and at the top it says fastboot usb have you tried running the ruu from there and are you scid? what carrier are you on? also in another post above this you said the bootloader doesnt get past the searching files, im wondering if you left the .zip that says pm58img on the root of your sd card. that could be the reason it doesnt get past that screen. just trying to get more info to see if we can get more help for you.
Divine flaw said:
ummmm just a quick questions.... if you are on the fastboot screen and at the top it says fastboot usb have you tried running the ruu from there and are you scid? what carrier are you on? also in another post above this you said the bootloader doesnt get past the searching files, im wondering if you left the .zip that says pm58img on the root of your sd card. that could be the reason it doesnt get past that screen. just trying to get more info to see if we can get more help for you.
Click to expand...
Click to collapse
Yes, I have tried to flash the 1.45 Pyramid RUU, but when the RUU tries to reset my phone into bootloader, it just resets right back into fastboot (the RUU command stays at "waiting for bootloader"). I am also super cid and my carrier is US T Mobile. I made sure not to leave the update package on my sd card, and I even tried the RUU without an sd card at all, but no difference.
APmoss13 said:
Yes, I have tried to flash the 1.45 Pyramid RUU, but when the RUU tries to reset my phone into bootloader, it just resets right back into fastboot (the RUU command stays at "waiting for bootloader"). I am also super cid and my carrier is US T Mobile. I made sure not to leave the update package on my sd card, and I even tried the RUU without an sd card at all, but no difference.
Click to expand...
Click to collapse
ok.... i was just askin cause did the exact same thing (well almost, i tried to change the notification icons which resulted in my notification bar completely gone) you did and got into that infinite boot loop. and couldnt boot into android. and couldnt figure it out. the only thing i did was just install the ruu while i was in the fastboot screen and it worked. i wasnt aware that there was a 1.45 ruu for tmous but i dont think that should matter since you are scid anyways. now im just wonderin if you tried any other ruu's besides that one. for me i flashed the 1.29 ruu for tmous and that got me up and running...... sorry i couldnt help
Today I unlocked my HOX using Hasoon2000's all in one kit. Unlocked the phone, super cid 1111111111, and rooted the phone with no problems. Once i got everything completed i attempted to install Viper XL rom onto the device through TWRP. The first time it froze during the process, so I rebooted and repeated the process. However, once i got it to work through TWRP, it started to boot up with the Viper XL boot screen and then suddenly turn off, and repeat itself. I can't get into boot loader and once plugged into my pc it simply makes the connect and disconnect sounds. Please any help at to unbrick this phone would be highly appreciated...
Have you tried flashing a different ROM?
If it's continually looping when trying to boot, hover your finger over the volume down button, then press and hold it as soon as the screen goes blank. Hopefully that'll get you into bootloader.
Sent from my Evita
dopedbadger said:
Today I unlocked my HOX using Hasoon2000's all in one kit. Unlocked the phone, super cid 1111111111, and rooted the phone with no problems. Once i got everything completed i attempted to install Viper XL rom onto the device through TWRP. The first time it froze during the process, so I rebooted and repeated the process. However, once i got it to work through TWRP, it started to boot up with the Viper XL boot screen and then suddenly turn off, and repeat itself. I can't get into boot loader and once plugged into my pc it simply makes the connect and disconnect sounds. Please any help at to unbrick this phone would be highly appreciated...
Click to expand...
Click to collapse
XDA Rules = Search before posting. This issue has been answered a million times.
That being said, while I would prefer you would help yourself a bit since you were smart enough to get yourself into this mess, I will still help you.
You are currently S-ON?
What hboot?
What version of TWRP are you using?
The phone still turns on right? bootloops?
It's not just black screen?
BAH TIMMAAA BEAT ME TO IT!
timmaaa said:
Have you tried flashing a different ROM?
Sent from my Evita
Click to expand...
Click to collapse
I can't. I'm stuck in a boot loop, where the device continuously reboots on it's own. Can't get to fastboot or the bootloader. Device isn't being found through the adb since it powers off before it can be recognized.
dopedbadger said:
I can't. I'm stuck in a boot loop, where the device continuously reboots on it's own. Can't get to fastboot or the bootloader. Device isn't being found through the adb since it powers off before it can be recognized.
Click to expand...
Click to collapse
If the phone turns on, you can get into bootloader.
As soon as the HTC screen comes back on press and hold power until the screen goes black. When the screen goes black, let go of power and press and hold volume down until the bootloader comes up.
exad said:
XDA Rules = Search before posting. This issue has been answered a million times.
That being said, while I would prefer you would help yourself a bit since you were smart enough to get yourself into this mess, I will still help you.
You are currently S-ON?
What hboot?
What version of TWRP are you using?
The phone still turns on right? bootloops?
It's not just black screen?
BAH TIMMAAA BEAT ME TO IT!
Click to expand...
Click to collapse
I actually did attempt searching through the forums, but i could not find a thread that actually helped me in my current predicament.
I am currently still S- ON, my firmware was the latest 3.18, the version of TWRP used was 2.5.0. and yes the phone still turns on, however it's doing it automatically by itself into a constant bootloop from the HTC white screen to the Viper XL boot animation.
exad said:
If the phone turns on, you can get into bootloader.
As soon as the HTC screen comes back on press and hold power until the screen goes black. When the screen goes black, let go of power and press and hold volume down until the bootloader comes up.
Click to expand...
Click to collapse
Alright, i was just having issues with my timing of trying to enter into bootloader. I'm currently sitting on the bootloader. fastboot however returns me to my eternal bootloop.
dopedbadger said:
Alright, i was just having issues with my timing of trying to enter into bootloader. I'm currently sitting on the bootloader. fastboot however returns me to my eternal bootloop.
Click to expand...
Click to collapse
Enter bootloader with the phone hooked up to PC, it should automatically put u you fastboot USB
Download twrp 2.3.3.1
check md5
flash twrp 2.3.3.1
fastboot erase cache
reboot to bootloader again fastboot reboot bootloader
select recovery wipe everything flash a sense rom.
If you're s-off fastboot flash boot boot.img extracted from the rom your flashing. GL HF. this phone has many quirks. Please read stickies for more info.
exad said:
Enter bootloader with the phone hooked up to PC, it should automatically put u you fastboot USB
Download twrp 2.3.3.1
check md5
flash twrp 2.3.3.1
fastboot erase cache
reboot to bootloader again fastboot reboot bootloader
select recovery wipe everything flash a sense rom.
If you're s-off fastboot flash boot boot.img extracted from the rom your flashing. GL HF. this phone has many quirks. Please read stickies for more info.
Click to expand...
Click to collapse
I can't seem to get my computer to recognize the phone when i plug it in. it makes the sound saying its connected, but it's just not displaying. Can't flash anything unless pc finds the device.
Sometimes it takes time and a couple unplug replugs for fastboot USB to come up. Took me almost a minute for it to connect properly for me earlier today.
Sent from my One X using xda app-developers app
exad said:
Sometimes it takes time and a couple unplug replugs for fastboot USB to come up. Took me almost a minute for it to connect properly for me earlier today.
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
I can't get it to recognize the phone. the fastboot usb option show whenever i plug into a pc. however, neither my desktop or laptop will recognize the phone..already reinstalled htc drivers and adb drivers
So it says fast boot USB?
What happens when you do fastboot devices?
Sent from my One X using xda app-developers app
exad said:
So it says fast boot USB?
What happens when you do fastboot devices?
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
It says fast boot on the phone in bootloader. if i reboot in fastboot, it just sends me to my bootloop. Man, i wish i would've just stopped i got this thing rooted.
While 2.3.5 of TWRP i reinstalled the Viper XL on my sd card, for the fourth time. Out of desperateness. But it actually booted up completely. Seems as if everything is working as well. Thanks man for everything.
I have an XE, HBOOT 1.27 Unlocked and S-ON and I flashed many ROMs, always enabling SmartFlash in 4Ext.
Yesterday I tried to flash Sebastian's ROM, Revelation, and now my phone is stuck at HTC Splash Screen.
First I did a nandroid to my current ROM, Pac 1.1, then format all(except SD Card), then flashed Revelation and something went wrong.
After flash complete I confirmed reboot and right before 4Ext closed, it showed a message saying something like : It has been detected a change in your boot partition, a backup of previous has been made in /sdcard/4Ext/boot.
It stays like that for a few seconds(I always had this message when flashed other ROMs) and soon after says something "there has been an error, report it" (never seen this message before) and reboots, but keeps showing Splash Screen for ~5 seconds, turns black, then Splash Screen again and so on until I remove the battery.
What can I do and how?
Someone told me to push via fastboot the ROM's boot.img but there is a problem.I have a PC where the phone has never been connected via USB cable, so I have no driver/tool anything.
When I connect it to PC, nothing shows up.
If I select FASTBOOT from the bootloader menu, still nothing shows up on PC.I tried from 4Ext menu Toggle usb connection, but still no trace on my PC.
I beg you, help me.
EDIT : I just found out that Sebastian messed up something in the installer, and all I have to do is to flash the boot.img through fastboot.
doublin said:
I have an XE, HBOOT 1.27 Unlocked and S-ON and I flashed many ROMs, always enabling SmartFlash in 4Ext.
Yesterday I tried to flash Sebastian's ROM, Revelation, and now my phone is stuck at HTC Splash Screen.
First I did a nandroid to my current ROM, Pac 1.1, then format all(except SD Card), then flashed Revelation and something went wrong.
After flash complete I confirmed reboot and right before 4Ext closed, it showed a message saying something like : It has been detected a change in your boot partition, a backup of previous has been made in /sdcard/4Ext/boot.
It stays like that for a few seconds(I always had this message when flashed other ROMs) and soon after says something "there has been an error, report it" (never seen this message before) and reboots, but keeps showing Splash Screen for ~5 seconds, turns black, then Splash Screen again and so on until I remove the battery.
What can I do and how?
Someone told me to push via fastboot the ROM's boot.img but there is a problem.I have a PC where the phone has never been connected via USB cable, so I have no driver/tool anything.
When I connect it to PC, nothing shows up.
If I select FASTBOOT from the bootloader menu, still nothing shows up on PC.I tried from 4Ext menu Toggle usb connection, but still no trace on my PC.
I beg you, help me.
Click to expand...
Click to collapse
Hi,
Try flashing a STOCK ROM
Choose the XE in the second post.
Otherwise you will have to setup your PC to run a RUU,and return everything back to square one.
The weird thing is that even if I try to flash another ROM, stil the same problem.
I format all except SD card,wipe cache+dalvik, mount SD card into PC and delete folder 4Ext/boot_backup.
Go back to 4Ext, enable SmartFlash and flash CM 10.1 by Albino . Reboot, I get the message about my boot partition has been modified, but not the error too, and when it reboots, stuck at splash screen.
I'm desperate.
doublin said:
The weird thing is that even if I try to flash another ROM, stil the same problem.
I format all except SD card,wipe cache+dalvik, mount SD card into PC and delete folder 4Ext/boot_backup.
Go back to 4Ext, enable SmartFlash and flash CM 10.1 by Albino . Reboot, I get the message about my boot partition has been modified, but not the error too, and when it reboots, stuck at splash screen.
I'm desperate.
Click to expand...
Click to collapse
Hi,
It looks like your only option to reconfigure your boot partition ,is to run a RUU.
Look HERE
Do you know the version-main of your phone?
But first you will also need to setup your PC for ADB.
Look HERE
malybru said:
Hi,
It looks like your only option to reconfigure your boot partition ,is to run a RUU.
Look HERE
Do you know the version-main of your phone?
But first you will also need to setup your PC for ADB.
Look HERE
Click to expand...
Click to collapse
Ok thank you for your links.
I'll try to do it tomorrow `cause right now I can't keep my concentration, too late and had a long day.
malybru said:
Hi,
It looks like your only option to reconfigure your boot partition ,is to run a RUU.
Look HERE
Do you know the version-main of your phone?
But first you will also need to setup your PC for ADB.
Look HERE
Click to expand...
Click to collapse
actually if he setup the pc with adb and fastboot files he will be able to flash the boot.img manually
so why the ruu.exe?
rzr86 said:
actually if he setup the pc with adb and fastboot files he will be able to flash the boot.img manually
so why the ruu.exe?
Click to expand...
Click to collapse
I tried that yesterday with the help of a guy, but no success.
I installed all necessary drivers, adb and fastboot, but I can't get my phone discovered on my PC.
If the boot partition would be screwed, why it doesn't work when I try to flash other ROM? Like CM 10.1 or the XE Stock that I've been suggested a few posts above. Flashing this ROMs, shouldn't the boot partition be written with the ROM's files, and everything should turn back as normal?
doublin said:
I tried that yesterday with the help of a guy, but no success.
I installed all necessary drivers, adb and fastboot, but I can't get my phone discovered on my PC.
If the boot partition would be screwed, why it doesn't work when I try to flash other ROM? Like CM 10.1 or the XE Stock that I've been suggested a few posts above. Flashing this ROMs, shouldn't the boot partition be written with the ROM's files, and everything should turn back as normal?
Click to expand...
Click to collapse
It should rewrite the boot partition. Are you sure 4ext says "a pending update to..." and the process completes?
First boot after a new flash can take as long a 10mins. Wait it out.
Anyway if it diesnt work, try another wipe (all except sdcard) flash another rom, and if you're still stuck, use an ruu.
Happy to help.
Far_SighT said:
It should rewrite the boot partition. Are you sure 4ext says "a pending update to..." and the process completes?
First boot after a new flash can take as long a 10mins. Wait it out.
Anyway if it diesnt work, try another wipe (all except sdcard) flash another rom, and if you're still stuck, use an ruu.
Happy to help.
Click to expand...
Click to collapse
I'm very sure 4ext says "a pending update to..." but only it doesn't completes as usual, instead show an error saying that the process couldn't be completed and the boot partition was reverted back as it was,report the problem. This happens when trying to flash Revelation.
I flashed CM 10.1 and says only " a pending update to..." no error , reboots and keeps turning off and on the splash screen.
I flashed a stock XE ROM, happens same thing as in CM 10.1 case.
I tried restoring from nandroid , happens same as CM 10.1 and stock XE ROM.
I wiped and flashed so many times in the last 2 days that I didn't do in the whole year that I had the phone.
I can't use a RUU, as I'm stuck at getting the phone discovered by PC.As I said, I installed all necessary drivers found on a topic here, but still can't see the phone.I tried HTC Sync also, as that pack installs the drivers too, but still no luck.
My last hope is to try connecting the phone on an older PC that I put it in a box and thrown it in the garage.That PC has all drivers and set-up for the phone, but they are outdated for sure.
doublin said:
I'm very sure 4ext says "a pending update to..." but only it doesn't completes as usual, instead show an error saying that the process couldn't be completed and the boot partition was reverted back as it was,report the problem. This happens when trying to flash Revelation.
I flashed CM 10.1 and says only " a pending update to..." no error , reboots and keeps turning off and on the splash screen.
I flashed a stock XE ROM, happens same thing as in CM 10.1 case.
I tried restoring from nandroid , happens same as CM 10.1 and stock XE ROM.
I wiped and flashed so many times in the last 2 days that I didn't do in the whole year that I had the phone.
I can't use a RUU, as I'm stuck at getting the phone discovered by PC.As I said, I installed all necessary drivers found on a topic here, but still can't see the phone.I tried HTC Sync also, as that pack installs the drivers too, but still no luck.
My last hope is to try connecting the phone on an older PC that I put it in a box and thrown it in the garage.That PC has all drivers and set-up for the phone, but they are outdated for sure.
Click to expand...
Click to collapse
There you go. The reason your phone is in a bootloop is that the correct boot.img is not written.
And something is not right with your recovery. It could be a bad flash (I'm not sure).
I don't think you need to use an ruu. Just get on a pc that recognizes your device, and flash the correct boot.img.
I would advise that you flash the recovery.img again.
EDIT: Change usb port to 2.0. Try all usb ports on your computer. It is quite common that fastboot recognizes devices on some usb ports and not on others.
Alternatively read this, point 4. This will surely work if you can't get another pc
doublin said:
I'm very sure 4ext says "a pending update to..." but only it doesn't completes as usual, instead show an error saying that the process couldn't be completed and the boot partition was reverted back as it was,report the problem. This happens when trying to flash Revelation.
I flashed CM 10.1 and says only " a pending update to..." no error , reboots and keeps turning off and on the splash screen.
I flashed a stock XE ROM, happens same thing as in CM 10.1 case.
I tried restoring from nandroid , happens same as CM 10.1 and stock XE ROM.
I wiped and flashed so many times in the last 2 days that I didn't do in the whole year that I had the phone.
I can't use a RUU, as I'm stuck at getting the phone discovered by PC.As I said, I installed all necessary drivers found on a topic here, but still can't see the phone.I tried HTC Sync also, as that pack installs the drivers too, but still no luck.
My last hope is to try connecting the phone on an older PC that I put it in a box and thrown it in the garage.That PC has all drivers and set-up for the phone, but they are outdated for sure.
Click to expand...
Click to collapse
Hi,
If you need windows 7 & 8 drivers, look HERE
If it worked on your old computer,then,it will still work now.
Far_SighT said:
There you go. The reason your phone is in a bootloop is that the correct boot.img is not written.
And something is not right with your recovery. It could be a bad flash (I'm not sure).
I don't think you need to use an ruu. Just get on a pc that recognizes your device, and flash the correct boot.img.
I would advise that you flash the recovery.img again.
EDIT: Change usb port to 2.0. Try all usb ports on your computer. It is quite common that fastboot recognizes devices on some usb ports and not on others.
Alternatively read this, point 4. This will surely work if you can't get another pc
Click to expand...
Click to collapse
I think this is the key to my problem. I checked the link you gave me and I think I might get it done using that method.
Gonna give it a try as soon as I get some free time later today.
PS : I tried all 3 usb ports on PC, ofc.
Thank you, I will keep this topic update with results.
I'm having a hard time finding the right RUU for my phone, as I don't have access to fastboot, which would make my job a lot easier.
I found a list with providers and CIDs and I suppose mine is HTC-ITA HTC__405 , since I bought it in Italy and it was unbranded.
But i can't get software version, as it asks me to go to setting/About phone . I can't do that.
I think the right RUU is RUU_PYRAMID_LE_ICS_35_S_HTC_Europe_3.32.401.105_R2_Radio_11.69.3504.00U_11.22.3504, so now I'm downloading that and then move on step 4 on that tutorial.
Hope I just won't brick the phone.
doublin said:
I'm having a hard time finding the right RUU for my phone, as I don't have access to fastboot, which would make my job a lot easier.
I found a list with providers and CIDs and I suppose mine is HTC-ITA HTC__405 , since I bought it in Italy and it was unbranded.
But i can't get software version, as it asks me to go to setting/About phone . I can't do that.
I think the right RUU is RUU_PYRAMID_LE_ICS_35_S_HTC_Europe_3.32.401.105_R2_Radio_11.69.3504.00U_11.22.3504, so now I'm downloading that and then move on step 4 on that tutorial.
Hope I just won't brick the phone.
Click to expand...
Click to collapse
You can flash only one particluar ruu. Just make sure it's pyramid le(sensation xe). You will not be able to flash a wrong one, so no need to worry.
Far_SighT said:
You can flash only one particluar ruu. Just make sure it's pyramid le(sensation xe). You will not be able to flash a wrong one, so no need to worry.
Click to expand...
Click to collapse
Yea I'm downloading right now RUU_PYRAMID_LE_ICS_35_S_HTC_Europe_3.32.401.105_R2_Radio_11.69.3504.00U_11.22.3504
Says LE, so I should be fine.
Hi,
The RUU process will not work if the phone says "Unlocked"
You will need to relock the phone,according to the section 3 of the guide.
So,you will need a PC
did you check also if the bootloader screen says fastboot usb?
malybru said:
Hi,
The RUU process will not work if the phone says "Unlocked"
You will need to relock the phone,according to the section 3 of the guide.
So,you will need a PC
Click to expand...
Click to collapse
OOps, forgot that step (I flash ruu via ruu.exe)
malybru said:
Hi,
The RUU process will not work if the phone says "Unlocked"
You will need to relock the phone,according to the section 3 of the guide.
So,you will need a PC
Click to expand...
Click to collapse
But I'm gonna do the step 4 which says only to execute the RUU .exe but don't do anything, and in the temp folder on my pc I will find a file which then I'll have to move to the SD Card and flash straight from my recovery.
rzr86 said:
did you check also if the bootloader screen says fastboot usb?
Click to expand...
Click to collapse
When I vol down & power to get in bootloader I see :
FASTBOOT
RECOVERY
FACTORY RESET
SIM LOCK
IMAGE CRC
I don't know about fastboot usb...
Anyway, selecting FASTBOOT and connecting my phone to PC, nothing shows up, and running fastboot commands doesn't work, there's no link between pc and phone.
doublin said:
But I'm gonna do the step 4 which says only to execute the RUU .exe but don't do anything, and in the temp folder on my pc I will find a file which then I'll have to move to the SD Card and flash straight from my recovery.
When I vol down & power to get in bootloader I see :
FASTBOOT
RECOVERY
FACTORY RESET
SIM LOCK
IMAGE CRC
I don't know about fastboot usb...
Anyway, selecting FASTBOOT and connecting my phone to PC, nothing shows up, and running fastboot commands doesn't work, there's no link between pc and phone.
Click to expand...
Click to collapse
when you select fastboot does it say after that fastboot usb in bootloader screen?
actually have you enabled usb debugging mode from tettings?
Hi Folks,
I tried to s-off my One S S4 via Facepalm SOFF via the procedure below
Followed instructions to the letter, got error 92 and continued. Ran the 3 commands at the end, rebooted to bootloader and no dice, still S-on. Re ran the whole process and this time I got error 99, still no luck. Every subsequent attempt it went straight to error 99...
Relocked my bootloader by running "Fastboot oem lock" and reunlocked it via htc dev (this now generating the token after I had done SuperCID).
Re ran facepalm and received error 92 again, this time ran all 3 commands and upon reboot, success
Click to expand...
Click to collapse
After the flash of PJ4010000-OneS.zip I tried to get out of RUU mode to flash soffbin via "fastboot oem boot" and it took really a very long time like around 10 mins and I tried to forcefully restart my mobile by using the power button and later the screen completely went black. I was not able to get even into bootloader or recovery or even fastboot. It seems like the mobile itself is bricked. Please help me to get my mobile back up.
csakthikumar said:
Hi Folks,
I tried to s-off my One S S4 via Facepalm SOFF via the procedure below
After the flash of PJ4010000-OneS.zip I tried to get out of RUU mode to flash soffbin via "fastboot oem boot" and it took really a very long time like around 10 mins and I tried to forcefully restart my mobile by using the power button and later the screen completely went black. I was not able to get even into bootloader or recovery or even fastboot. It seems like the mobile itself is bricked. Please help me to get my mobile back up.
Click to expand...
Click to collapse
bump :crying:
I have searched and tried different things but I'm getting nowhere. I have been running Purity rom on this for a while but when I woke up this morning, I found my screen black and only being able to boot to the bootloader and and google screen (which quickly goes away and goes black again). When I tried to go to recovery at first I believe it was just shutting off. Now it goes to a light black screen.
The first thing I did was flashed the factory image .bat file and everything seemed to go ok but when trying to go to recovery after it went to the light black screen. I turned it off and it booted to the Google screen then off again. Then it booted to the google screen and it froze that way. I can always get it back to the bootloader screen and got it to recovery once by flashing TWRP again using ADB.
TWRP opened once and I tried to do a factory reset but it couldn't find anything and couldn't mount to anything. I got it back to the bootloader again but the recovery has disappeared again. I tried to flash the factory image again but it definitely failed this time.
Please help.
aburn95 said:
I have searched and tried different things but I'm getting nowhere. I have been running Purity rom on this for a while but when I woke up this morning, I found my screen black and only being able to boot to the bootloader and and google screen (which quickly goes away and goes black again). When I tried to go to recovery at first I believe it was just shutting off. Now it goes to a light black screen.
The first thing I did was flashed the factory image .bat file and everything seemed to go ok but when trying to go to recovery after it went to the light black screen. I turned it off and it booted to the Google screen then off again. Then it booted to the google screen and it froze that way. I can always get it back to the bootloader screen and got it to recovery once by flashing TWRP again using ADB.
TWRP opened once and I tried to do a factory reset but it couldn't find anything and couldn't mount to anything. I got it back to the bootloader again but the recovery has disappeared again. I tried to flash the factory image again but it definitely failed this time.
Please help.
Click to expand...
Click to collapse
@bitdomo might be able to help you lol
Might be bad eMMC or something?
when youre flashing recovery, which command are you using.. fastboot boot recovery recoveryname.img or fastboot flash recovery recoveryname.img?
aburn95 said:
I have searched and tried different things but I'm getting nowhere. I have been running Purity rom on this for a while but when I woke up this morning, I found my screen black and only being able to boot to the bootloader and and google screen (which quickly goes away and goes black again). When I tried to go to recovery at first I believe it was just shutting off. Now it goes to a light black screen.
The first thing I did was flashed the factory image .bat file and everything seemed to go ok but when trying to go to recovery after it went to the light black screen. I turned it off and it booted to the Google screen then off again. Then it booted to the google screen and it froze that way. I can always get it back to the bootloader screen and got it to recovery once by flashing TWRP again using ADB.
TWRP opened once and I tried to do a factory reset but it couldn't find anything and couldn't mount to anything. I got it back to the bootloader again but the recovery has disappeared again. I tried to flash the factory image again but it definitely failed this time.
Please help.
Click to expand...
Click to collapse
Lock your bootloader then reboot to fastboot. If the lock state remains locked try LG flashtool. Link in my signature. If the lock state reverts back to unlocked, then you have to rma your device. If that is the case can you check the variant text in fastboot for me? There should be D820 or D821 and after there should be a letter E or H in (). I want to know that letter in the (). Thanks.
Dont forget to report me your progress
simms22 said:
when youre flashing recovery, which command are you using.. fastboot boot recovery recoveryname.img or fastboot flash recovery recoveryname.img?
Click to expand...
Click to collapse
Hey I'm using "fastboot flash recovery recovery.img" and that's what I've used in the past. I've had a fully functioning rom with fully functioning recovery for a while until yesterday.
bitdomo said:
Lock your bootloader then reboot to fastboot. If the lock state remains locked try LG flashtool. Link in my signature. If the lock state reverts back to unlocked, then you have to rma your device. If that is the case can you check the variant text in fastboot for me? There should be D820 or D821 and after there should be a letter E or H in (). I want to know that letter in the (). Thanks.
Dont forget to report me your progress
Click to expand...
Click to collapse
Ok thanks I'll try this and check the text in fastboot after work today. Thanks for the responses guys.
After reading some more last night I'm afraid it's an emmc problem but I like to be proven wrong sometimes.
Maybe also try this?
http://forum.xda-developers.com/showthread.php?t=2577447
beekay201 said:
Maybe also try this?
http://forum.xda-developers.com/showthread.php?t=2577447
Click to expand...
Click to collapse
I actually have that thread open on my computer. It was my next attempt of repair before starting the thread late last night. Thanks for the suggestion I will certainly try it.
Update: I tried pushing Philz recovery to the phone which seemed to work fine until I selected go to recovery mode. It just went back to that barely light black screen. I'll try again when I get home. Going to try Bitdomo's advice about locking bootloader first.
bitdomo said:
Lock your bootloader then reboot to fastboot. If the lock state remains locked try LG flashtool. Link in my signature. If the lock state reverts back to unlocked, then you have to rma your device. If that is the case can you check the variant text in fastboot for me? There should be D820 or D821 and after there should be a letter E or H in (). I want to know that letter in the (). Thanks.
Dont forget to report me your progress
Click to expand...
Click to collapse
Out of curiosity what's the reason for using two brands, or were they just available so they were used?
bitdomo said:
Lock your bootloader then reboot to fastboot. If the lock state remains locked try LG flashtool. Link in my signature. If the lock state reverts back to unlocked, then you have to rma your device. If that is the case can you check the variant text in fastboot for me? There should be D820 or D821 and after there should be a letter E or H in (). I want to know that letter in the (). Thanks.
Dont forget to report me your progress
Click to expand...
Click to collapse
Bitdomo I'm trying the Flashtool but it's staying at 0% on the firmware update and nothing is popping up on computer or in Device Manager. Had no connection issues prior to the brick or with adb/fastboot. My Ports aren't evening showing at all in DM even if I select show hidden devices.
aburn95 said:
How do I lock the bootloader without being able to put the .zip on my internal memory?
Click to expand...
Click to collapse
In fastboot type
fastboot oem lock
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
In fastboot type
fastboot oem lock
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
I honestly wanted to do that but it seemed too easy. I was trying to lock it like I did before when i had to send original back to T-Mobile. Sorry and thanks.
bitdomo said:
Lock your bootloader then reboot to fastboot. If the lock state remains locked try LG flashtool. Link in my signature. If the lock state reverts back to unlocked, then you have to rma your device. If that is the case can you check the variant text in fastboot for me? There should be D820 or D821 and after there should be a letter E or H in (). I want to know that letter in the (). Thanks.
Dont forget to report me your progress
Click to expand...
Click to collapse
Ok so it stayed locked so that's a start. I'm back in download mode again but it's staying at 0% and nothing on computer.
I tried to re-download the factory images and flash again using adb. It failed again. Here's a picture of what happened:
Unzip the zip and use manual flash commands. Clikc the link in my signature and read my "adb and fastboot. What is it?" thread of you're unsure of the commands.
Sent from my Nexus 5 using Tapatalk
aburn95 said:
I tried to re-download the factory images and flash again using adb. It failed again. Here's a picture of what happened:
Click to expand...
Click to collapse
You have "remote: flash write failure" error. It means your emmc (internal storage) is broken and you cannot modify the data on it. You have to rma your device.
Just for matter of research can you enter to fastboot and post the variable line here?
Mine is: hammerhead D821(H) 16GB
bitdomo said:
You have "remote: flash write failure" error. It means your emmc (internal storage) is broken and you cannot modify the data on it. You have to rma your device.
Just for matter of research can you enter to fastboot and post the variable line here?
Mine is: hammerhead D821(H) 16GB
Click to expand...
Click to collapse
Sorry I meant to tell you yesterday... D820H 16GB. Should I still be able to toggle the tamper tag so they will take it back with no problems? Or am I screwed?
aburn95 said:
Sorry I meant to tell you yesterday... 820H. Should I still be able to toggle the tamper so they will take it back with no problems? Or am I screwed?
Click to expand...
Click to collapse
You should be able to if you managed to lock the bootloader. The name of the zip does not came into my mind which you have to flash, but you have to do it with the adb sideload command because you cant copy anything to your phone, or use adb push command to push it to the "/" folder because it is mounted to the ram which you can write not like your storage . If you bought your phone from google it does not matter you have tamper flag set to 1.
bitdomo said:
You should be able to if you managed to lock the bootloader. The name of the zip does not came into my mind which you have to flash, but you have to do it with the adb sideload command because you cant copy anything to your phone, or use adb push command to push it to the "/" folder because it is mounted to the ram which you can write not like your storage . If you bought your phone from google it does not matter you have tamper flag set to 1.
Click to expand...
Click to collapse
Ok thanks. I haven't quite figured out the adb sideload function yet. I tried doing it through TWRP but it just sits there and does nothing after selecting. Maybe I'm trying the wrong thing. I got my phone from T-Mobile so I'll need to solve this. Thanks for the help.
This phone is being a real a-hole. I'm trying to boot to stock recovery but it just sits on a screen with a really big android with wiggling antennae. I pressed up+power many times but it stayed that way. So I tried booting to TWRP again and it did but went immediately to an "OpenRecoveryScript," had a little bar at the bottom for a while with some other stuff on the screen, then turned off.
I tried stock recovery again and it went to the little dead android this time but still nothing when I press up+power.