Related
Hello, I've spent about the past 5 days trying to figure this out. So, how this started was, a while back when I first got the phone, I wanted 4.4, so I rooted my phone, and tried to flashify a recovery like CWM and TWRP. Both of these failed. I tried many times, and no matter what I tried, flashing always failed. But guess what, my stock recovery was erased in the process. I forgot about it until today, where I found the OTA update to 4.4 was released, and attempted to do it. To my dismay, I forgot I had no recovery mode, and instantly got the "boot certification verify" error screen. Now All I can access is download mode, to my knowledge. So I've been trying to fix this, either by installing stock recovery, or another way to install a custom. All to no avail. When I use the lg flash tool for the stock recovery, it fails at "BIN CRC Check". Every.... Single.... Time. Despite downloading multiple replacement files. I would be perfectly content with installing a customer recovery, but the ways I see require the phone to be on, and use the built in recovery mode. At this point, my phone is bricked, and I am looking for any and all ways to either A) boot back up normally without installing a recovery and fix it later, or B) install a recovery, even if it's the hard way.
Update:
I followed this thread:
http://forum.xda-developers.com/showthread.php?t=2582142
It looked like it was going to work. I am using a Xubuntu virtual machine. I was copying the files over, and every time it finished copying a file, it unmounted and remounted my phone (I don't know if that was suppose to happen, just worth mentioning if it wasn't suppose to). I was super excited to do it. Hard rebooted my phone. And now it's just a blank screen. I have no logo, no error, and no download mode like I had before. Seriously need some help here.
Update#2:
I have the flash tool correctly working. Awesome! But..... I still have no download mode here.... So I can't use the tool....
Lastly, I am aware of the title.... i don't know how that happened. I intended to type "need", but somehow that happened. I do not know how to edit it.
Can you enter recovery?
Sent from my LG-LS980 using XDA Premium 4 mobile app
Ouch bud you are hard bricked pretty much. It sounds to me from what you explained all the partitions are wiped clean. I don't think there is any recovery from that unless you have a nand programmer
Sent from my LG-LS980 using xda app-developers app
brockzilla said:
Hello, I've spent about the past 5 days trying to figure this out. So, how this started was, a while back when I first got the phone, I wanted 4.4, so I rooted my phone, and tried to flashify a recovery like CWM and TWRP. Both of these failed. I tried many times, and no matter what I tried, flashing always failed. But guess what, my stock recovery was erased in the process. I forgot about it until today, where I found the OTA update to 4.4 was released, and attempted to do it. To my dismay, I forgot I had no recovery mode, and instantly got the "boot certification verify" error screen. Now All I can access is download mode, to my knowledge. So I've been trying to fix this, either by installing stock recovery, or another way to install a custom. All to no avail. When I use the lg flash tool for the stock recovery, it fails at "BIN CRC Check". Every.... Single.... Time. Despite downloading multiple replacement files. I would be perfectly content with installing a customer recovery, but the ways I see require the phone to be on, and use the built in recovery mode. At this point, my phone is bricked, and I am looking for any and all ways to either A) boot back up normally without installing a recovery and fix it later, or B) install a recovery, even if it's the hard way.
Update:
I followed this thread:
http://forum.xda-developers.com/showthread.php?t=2582142
It looked like it was going to work. I am using a Xubuntu virtual machine. I was copying the files over, and every time it finished copying a file, it unmounted and remounted my phone (I don't know if that was suppose to happen, just worth mentioning if it wasn't suppose to). I was super excited to do it. Hard rebooted my phone. And now it's just a blank screen. I have no logo, no error, and no download mode like I had before. Seriously need some help here.
Update#2:
I have the flash tool correctly working. Awesome! But..... I still have no download mode here.... So I can't use the tool....
Lastly, I am aware of the title.... i don't know how that happened. I intended to type "need", but somehow that happened. I do not know how to edit it.
Click to expand...
Click to collapse
Im confused you said you had download mode then didnt? If it works try using the alternate G2 dll named 8974, because the second time I used Flashtool only the alternate dll worked which is weird because just hours earlier I had used the original, the original said wrong model/download failed the second time.
abhinav.tella said:
Im confused you said you had download mode then didnt? If it works try using the alternate G2 dll named 8974, because the second time I used Flashtool only the alternate dll worked which is weird because just hours earlier I had used the original, the original said wrong model/download failed the second time.
Click to expand...
Click to collapse
As I explained in my update, the method I used didn't work and had removed all modes I could boot into, including download mode.
brockzilla said:
As I explained in my update, the method I used didn't work and had removed all modes I could boot into, including download mode.
Click to expand...
Click to collapse
Try this
http://forum.xda-developers.com/showthread.php?t=2477595
Then use LG Flash Tool, the Verizon guide works for LS980. Except use LS980 dll, and you must use Verizon USB drivers (Not T-Mobile, ATT etc), or Flash Tool wont work.
http://forum.xda-developers.com/showthread.php?t=2448960
I definitely hope you only semi bricked..... Tell me if that works.
brockzilla said:
As I explained in my update, the method I used didn't work and had removed all modes I could boot into, including download mode.
Click to expand...
Click to collapse
abhinav.tella said:
Try this
http://forum.xda-developers.com/showthread.php?t=2477595
Then use LG Flash Tool, the Verizon guide works for LS980. Except use LS980 dll, and you must use Verizon USB drivers (Not T-Mobile, ATT etc), or Flash Tool wont work.
http://forum.xda-developers.com/showthread.php?t=2448960
I definitely hope you only semi bricked..... Tell me if that works.
Click to expand...
Click to collapse
from what he said it sounds like a hard brick
Damn, not even fastboot? Feel sorry for you.
I was trying to carrier unlock my phone, and to do that i tried to downgrade it 4.3 to 4.1.1, and only after i had pressed the button, i had noticed that this might brick my phone in a comment in one of the forums, this is what i did:
http://forum.xda-developers.com/showthread.php?t=2625461
after following this and trying to run odin with it, odin returned "FAIL", and due to my high level of stupidity at the time, i tried to use the original 4.1.1 as my PDA in odin right after, i didnt reboot or anything, just pressed start again with the other tar.md5 file....
so now i cannot go past the samsung galaxy s3 logo when booting. I CAN go into download mode though, but i have no clue what i am supposed to do afterwards
i have the Galaxy S 3 i747 (was 4.3 before the whole mess) at&t carrier, i am trying to unlock it because i am travelling and need a phone.
please help me fix it, i do not care about the warranty since i dont have it anymore anyways, as long as the phone is working
also, if possible, i also need to unlock it afterwards, any help is HIGHLY appreciated, thanks!
baruchadi said:
I was trying to carrier unlock my phone, and to do that i tried to downgrade it 4.3 to 4.1.1, and only after i had pressed the button, i had noticed that this might brick my phone in a comment in one of the forums, this is what i did:
http://forum.xda-developers.com/showthread.php?t=2625461
after following this and trying to run odin with it, odin returned "FAIL", and due to my high level of stupidity at the time, i tried to use the original 4.1.1 as my PDA in odin right after, i didnt reboot or anything, just pressed start again with the other tar.md5 file....
so now i cannot go past the samsung galaxy s3 logo when booting. I CAN go into download mode though, but i have no clue what i am supposed to do afterwards
i have the Galaxy S 3 i747 (was 4.3 before the whole mess) at&t carrier, i am trying to unlock it because i am travelling and need a phone.
please help me fix it, i do not care about the warranty since i dont have it anymore anyways, as long as the phone is working
also, if possible, i also need to unlock it afterwards, any help is HIGHLY appreciated, thanks!
Click to expand...
Click to collapse
Downgrading your boot loader from 4.3 is a guaranteed brick. I'm not sure if the brick will get you to the Samsung screen.
If you're already assuming its bricked reboot into recovery and do a full wipe. Restore a nandroid of something if you have one or try flashing a custom ROM. Because Odin failed maybe it never flashed the boot loader.
Worth a try
Sent from my SGH-I747M using XDA Free mobile app
baruchadi said:
I was trying to carrier unlock my phone, and to do that i tried to downgrade it 4.3 to 4.1.1, and only after i had pressed the button, i had noticed that this might brick my phone in a comment in one of the forums, this is what i did:
http://forum.xda-developers.com/showthread.php?t=2625461
after following this and trying to run odin with it, odin returned "FAIL", and due to my high level of stupidity at the time, i tried to use the original 4.1.1 as my PDA in odin right after, i didnt reboot or anything, just pressed start again with the other tar.md5 file....
so now i cannot go past the samsung galaxy s3 logo when booting. I CAN go into download mode though, but i have no clue what i am supposed to do afterwards
i have the Galaxy S 3 i747 (was 4.3 before the whole mess) at&t carrier, i am trying to unlock it because i am travelling and need a phone.
please help me fix it, i do not care about the warranty since i dont have it anymore anyways, as long as the phone is working
also, if possible, i also need to unlock it afterwards, any help is HIGHLY appreciated, thanks!
Click to expand...
Click to collapse
Welcome to the forum! Wished you'd come in much earlier though as you would have found you CANNOT downgrade from 4.3 to 4.1.1 to free unlock. Sorry, but once you are on 4.3, the surest way to unlock is to obtain the unlock code from the carrier or purchase one online. Sounds like you do have a soft brick. If your phone is still booting to the Samsung logo, then it's only a soft brick. Attempting to downgrade the 4.3 bootloader usually results in a hard brick so you may be in luck.
To fix this first, try to see if you can boot to recovery mode and do a hard wipe/factory reset. If you are able to boot to recovery (or download) mode then you have little to worry about. If the reset does not work, you can flash custom recovery via Odin and follow the instructions in the thread below to restore stock 4.3. Afraid, you have to revert to full stock 4.3 to get the phone back in working order and don't even think about 4.1.1.
http://forum.xda-developers.com/showthread.php?t=2658486
If you are not able to get to recovery, then you can see if you can boot from a debrick image following the instructions (on the first page) of the thread below ...
http://forum.xda-developers.com/showthread.php?t=2549068
Once your phone is working normally, you can request the unlock code from AT&T via the request form below. If eligible, they should provide this. Otherwise, you would have to buy one online ....
https://www.att.com/deviceunlock/client/en_US/
Let me know if you need any further help.
KorGuy123 said:
Downgrading your boot loader from 4.3 is a guaranteed brick. I'm not sure if the brick will get you to the Samsung screen.
If you're already assuming its bricked reboot into recovery and do a full wipe. Restore a nandroid of something if you have one or try flashing a custom ROM. Because Odin failed maybe it never flashed the boot loader.
Worth a try
Sent from my SGH-I747M using XDA Free mobile app
Click to expand...
Click to collapse
I tried wiping everything, i also wiped cache, still didn't boot, thanks though!
Larry2999 said:
Welcome to the forum! Wished you'd come in much earlier though as you would have found you CANNOT downgrade from 4.3 to 4.1.1 to free unlock. Sorry, but once you are on 4.3, the surest way to unlock is to obtain the unlock code from the carrier or purchase one online. Sounds like you do have a soft brick. If your phone is still booting to the Samsung logo, then it's only a soft brick. Attempting to downgrade the 4.3 bootloader usually results in a hard brick so you may be in luck.
To fix this first, try to see if you can boot to recovery mode and do a hard wipe/factory reset. If you are able to boot to recovery (or download) mode then you have little to worry about. If the reset does not work, you can flash custom recovery via Odin and follow the instructions in the thread below to restore stock 4.3. Afraid, you have to revert to full stock 4.3 to get the phone back in working order and don't even think about 4.1.1.
http://forum.xda-developers.com/showthread.php?t=2658486
If you are not able to get to recovery, then you can see if you can boot from a debrick image following the instructions (on the first page) of the thread below ...
http://forum.xda-developers.com/showthread.php?t=2549068
Once your phone is working normally, you can request the unlock code from AT&T via the request form below. If eligible, they should provide this. Otherwise, you would have to buy one online ....
https://www.att.com/deviceunlock/client/en_US/
Let me know if you need any further help.
Click to expand...
Click to collapse
I am able to get to recovery, but the first link isn't very clear.... i am not really familiar with odin and all this other stuff... lol, i am now downloading the files it says to download in the first link though, can you maybe tell me in a quick list what exactly im supposed to do?
thanks!
baruchadi said:
I tried wiping everything, i also wiped cache, still didn't boot, thanks though!
I am able to get to recovery, but the first link isn't very clear.... i am not really familiar with odin and all this other stuff... lol, i am now downloading the files it says to download in the first link though, can you maybe tell me in a quick list what exactly im supposed to do?
thanks!
Click to expand...
Click to collapse
It's time to start reading. Before doing any flashing/modding, you should make sure you understand what you're doing and know the risks.
Now as for Odin, it's quite straight forward. Phone needs to be in download mode, you put the PDA file in Odin and flash (if it's a Odin one-click, just need to hit start). One thing is to not interrupt it! Especially if flashing bootloaders cause that will brick your phone. Also, don't downgrade bootloaders.
There are a few guides in the sticky, I suggest you take an hour or two reading them so things like that don't happen again (or that you know what to do if it does).
GL!
baruchadi said:
I tried wiping everything, i also wiped cache, still didn't boot, thanks though!
I am able to get to recovery, but the first link isn't very clear.... i am not really familiar with odin and all this other stuff... lol, i am now downloading the files it says to download in the first link though, can you maybe tell me in a quick list what exactly im supposed to do?
thanks!
Click to expand...
Click to collapse
Alright. If wipe/reset didn't work, you'll need to restore full stock 4.3 via custom recovery. Here's what we need to do....
1) Download the Odin flashable *.Tar file for custom recovery. I prefer TWRP because of the GUI so that's where I'm pointing you to ...
http://techerrata.com/file/twrp2/d2att/openrecovery-twrp-2.6.3.1-d2att.tar
2) Download the stock restore file for 4.3 from the thread below... If you are using TWRP, then the first link is the one you need
http://forum.xda-developers.com/showthread.php?t=2658486
3) Copy the stock restore zip file to a good quality (micro) SD card
4) I presume you have Odin already so you will use this to flash custom recovery to your phone. Run Odin.exe on your PC. If you are using Odin v.3.09 then you need the AP tab. For all other versions, use the PDA tab. Navigate to the custom recovery *.Tar file you downloaded earlier and place this in the PDA (or AP tab). Leave the default settings as is and do not check/uncheck any boxes other than the default settings.
5) Boot the phone to download mode via the 3-button combo (Volume Down/Home/Power). When you get to Odin (Download) mode, press volume up to continue. Connect the phone to your PC with a good quality micro USB cable. Wait until Odin has recognized the device then click on the Start button to start firmware installation (flashing). Wait for the flashing to end and the <Pass> message. Disconnect the phone from the PC and pull the battery to stop auto reboot.
6) Place the micro SD card with the stock restore zip in your phone. Replace the battery and boot to recovery mode. If you were successful with the firmware flashing above, it should boot you to custom recovery.
7) Select install from external card and navigate to the stock restore zip file. Select this file and swipe the screen to start firmware installation. Wait for installation to complete. Then clear your cache/dalvik and reboot to system.
This will hopefully do it.
Hello Everyone.
Please, I need some help. I was trying to downgrade an ATT Samsung Galaxy S3 from 5.0 to 4.1.1 and try to unlock it.
First, Try to flash with Odin 3.04, Odin 3.07 and Odin 3.09 with the firmware 4.1.1 from Samsung. It always failes.
So I rooted it , installed a team Win Recovery Project 2.6.3.1 and flashed a custom rom based on Android
4.1.2 thinking it will break the bootloader. Nothing.
I tried Emergency Recovery with Kies did not work.
In odin mode:
Product Name: SGH-I747
Current Binary: Custom
System Status: Custom
Qualcom Scoreboot: Enable
Warranty Bit:1
Bootloader AP SWREV:3
I spent hours on it. I don't know what to do.
Anyone has a idea to help me please?
Thanks you very much in advance.
If you can get into download mode, flash the latest Philz d2lte recovery using the tar.md5 file and Odin. Copy a ROM to an external SD card (I recommend the latest CM11), boot into recovery, flash the ROM, boot the phone. Once the phone boots, confirm your bootloader and modem version. I recommend not flashing anthing until you at least know your bootloader version.
Continuing to flash files without knowing the bootloader verson can hard brick you phone.
audit13 said:
If you can get into download mode, flash the latest Philz d2lte recovery using the tar.md5 file and Odin. Copy a ROM to an external SD card (I recommend the latest CM11), boot into recovery, flash the ROM, boot the phone. Once the phone boots, confirm your bootloader and modem version. I recommend not flashing anthing until you at least know your bootloader version.
Continuing to flash files without knowing the bootloader verson can hard brick you phone.
Click to expand...
Click to collapse
Thank you for your quick answer like you said i tried to flash cyanogen mod 11 and it aborted. How can I find out my bootloader version?
MEEEEEEEE said:
Thank you for your quick answer like you said i tried to flash cyanogen mod 11 and it aborted. How can I find out my bootloader version?
Click to expand...
Click to collapse
If you're on Philz touch, download AROMA file manager and store it on your external SD. You can get it here.
Boot into recovery and flash the file manager like you would install a ROM and it will open the file manager. Once you're up in the AROMA file manager, one of the menu options is to open a console. Once you're up in the console window the following command will tell you what bootloader you have loaded:
Code:
getprop ro.bootloader
That command will work from ADB shell in custom recovery too, if you happen to have ADB and all the drivers set up right on your computer.
What error did you get when flashing with Philz? Was it error 7?
Yes. It was a status 7. And I don't know what happens. Right now it looks hard bricked. I can not even it start it and put it on the downloading mode. When I plugged it to the power source without the battery. I have a big red led on and any responses. What is it? Can I go back to the downloading mode with a jig?
MEEEEEEEE said:
Yes. It was a status 7. And I don't know what happens. Right now it looks hard bricked. I can not even it start it and put it on the downloading mode. When I plugged it to the power source without the battery. I have a big red led on and any responses. What is it? Can I go back to the downloading mode with a jig?
Click to expand...
Click to collapse
Pull the battery, leave it out for a few minutes, then try to boot into recovery or download mode. This has cured some curious behavior for me a few times (just a shot in the dark though).
Another random thought, do you know how much battery power you had left? I'm a little surprised a failed CM flash would result in a hard brick when you still had download and recovery working before. Any chance the battery is dead? It won't charge without a working rom.
If that doesn't work and you can't get into recovery or download mode it might be time to move on to the debrick threads.
You may have to try a de-brick image. Status 7 usually occurs when the recovery is out of date.
jason2678 said:
Pull the battery, leave it out for a few minutes, then try to boot into recovery or download mode. This has cured some curious behavior for me a few times (just a shot in the dark though).
Another random thought, do you know how much battery power you had left? I'm a little surprised a failed CM flash would result in a hard brick when you still had download and recovery working before. Any chance the battery is dead? It won't charge without a working rom.
If that doesn't work and you can't get into recovery or download mode it might be time to move on to the debrick threads.
Click to expand...
Click to collapse
I tried to take the battery out and the flash is light on for a micro second but the phone does not boot. I can not go either in the recovery mode nor the downloading mode.
The is a custom rom on the phone. There is a slim kat v9 on it.
MEEEEEEEE said:
I tried to take the battery out and the flash is light on for a micro second but the phone does not boot. I can not go either in the recovery mode nor the downloading mode.
The is a custom rom on the phone. There is a slim kat v9 on it.
Click to expand...
Click to collapse
You did put the battery back in after pulling it for a couple of minutes, right? Looking back at my previous post it was poorly worded.
The fact that you went from working recovery and download to not working on a status 7 is curious. Usually status 7 errors are the developers trying to protect us from ourselves; your recovery is out of date, you are trying to flash a rom that isn't for your phone or doesn't like your bootloader, something like that. When you get a status 7, usually the recovery didn't actually do anything. It failed a safety check and quit. That's what made me wonder if maybe your battery just died.
So you flashed CM11 for the d2lte using the latest version of Philz? Did you flash anything else?
Actually I gave the cellphone to someone few days ago and he told me that I needed to unlock the bootloader and install EZ-unlock. Unlocked the bootloader. Philz is still on the recovery partition. The firmware flashed is slim kat v9. Since the bootloader has been unlocked. The phone does not want to start. I tried to take out the battery for few minutes. it does not change anything.
MEEEEEEEE said:
Actually I gave the cellphone to someone few days ago and he told me that I needed to unlock the bootloader and install EZ-unlock. Unlocked the bootloader. Philz is still on the recovery partition. The firmware flashed is slim kat v9. Since the bootloader has been unlocked. The phone does not want to start. I tried to take out the battery for few minutes. it does not change anything.
Click to expand...
Click to collapse
the phone wont start because the i747 bootloader does not come locked. what ez-unlock does for this device is effectively BRICK it!!!!! i know because thats how i bricked my first i747. now you really do need the debrick image. when plugged in , without battery does the led show red ?
http://forum.xda-developers.com/showthread.php?t=2549068
"all i can really do , is stay out of my own way and let the will of heaven be done"
Yes. The red led is showing when I plugged the device without the battery.
mrrocketdog said:
the phone wont start because the i747 bootloader does not come locked. what ez-unlock does for this device is effectively BRICK it!!!!! i know because thats how i bricked my first i747. now you really do need the debrick image. when plugged in , without battery does the led show red ?
http://forum.xda-developers.com/showthread.php?t=2549068
"all i can really do , is stay out of my own way and let the will of heaven be done"
Click to expand...
Click to collapse
MEEEEEEEE said:
Yes. The red led is showing when I plugged the device without the battery.
Click to expand...
Click to collapse
pretty positive sign of a brick if thats all you can get. check the link for the "de-brick" thread that i posted. remember that sometimes it takes more than one try , and while one sdcard will work for one phone , it may or may not work for another. just keep trying. good luck.:thumbup:
"all i can really do , is stay out of my own way and let the will of heaven be done"
Do I need to get a jig to un-bricked it?
MEEEEEEEE said:
Do I need to get a jig to un-bricked it?
Click to expand...
Click to collapse
nope. read the thread. a de-brick image and sdcard should do it.
"all i can really do , is stay out of my own way and let the will of heaven be done"
A jig would be helpful if the phone boots but you can't get into download mode.
Hey guys, im running 5.0.2 atm. i want to unroot my htc one m9 because i have no reason for it to be rooted really. i was hoping to be able to use game killer and those memory editors, but no available version for the new lollipop. so i want to unroot. I have the stock rom and adb files ready on my pc. but when i try to issue a command to my phone, it says the device is offline. and yes the pc's fingerprint is allowed. if you are going to suggest i download drivers or anything like that please link it. i have tried updating drivers and all that, says it is working properly. thanks in advance!!
EDIT: Ok as of right now, my main concern is flashing the stock rom, which i downloaded, and renamed the 0pjaimg.zip thing. I typed "fastboot flash zip 0pjaimg.zip" and it says "error can not load '0pjaimg.zip'" what do i do?
iSike said:
Hey guys, im running 5.0.2 atm. i want to unroot my htc one m9 because i have no reason for it to be rooted really. i was hoping to be able to use game killer and those memory editors, but no available version for the new lollipop. so i want to unroot. I have the stock rom and adb files ready on my pc. but when i try to issue a command to my phone, it says the device is offline. and yes the pc's fingerprint is allowed. if you are going to suggest i download drivers or anything like that please link it. i have tried updating drivers and all that, says it is working properly. thanks in advance!!
EDIT: Ok as of right now, my main concern is flashing the stock rom, which i downloaded, and renamed the 0pjaimg.zip thing. I typed "fastboot flash zip 0pjaimg.zip" and it says "error can not load '0pjaimg.zip'" what do i do?
Click to expand...
Click to collapse
Open SuperSU->Settings->Unroot?
j to the 4n said:
Open SuperSU->Settings->Unroot?
Click to expand...
Click to collapse
Yea I tried that, didn't work. I ended up almost having a heart attack haha. I went to wipe but accidentally wiped everything on my phone, my data , the root, and even the OS. I was stuck in download mode and boot loader, could not boot into recovery. And I was stupid enough to not have a backup. I ended up reflashing a ruu (thru my PC with a ruu utility) several times and it finally worked. My phone now is unrooted and I removed the boot loader. I achieved by beginning goal with a big hiccup before hand haha. I will now make a back up of my phone today lol. And I had titanium backup up, but it said I didn't have root access(when my device was rooted) so I figured if half the root perks weren't working, I'll just unroot, which I am happy I did. Don't have to worry about harming my device anymore. Game killer and all those memory editors didn't work anyway so root was useless to me
iSike said:
Yea I tried that, didn't work. I ended up almost having a heart attack haha. I went to wipe but accidentally wiped everything on my phone, my data , the root, and even the OS. I was stuck in download mode and boot loader, could not boot into recovery. And I was stupid enough to not have a backup. I ended up reflashing a ruu (thru my PC with a ruu utility) several times and it finally worked. My phone now is unrooted and I removed the boot loader. I achieved by beginning goal with a big hiccup before hand haha. I will now make a back up of my phone today lol. And I had titanium backup up, but it said I didn't have root access(when my device was rooted) so I figured if half the root perks weren't working, I'll just unroot, which I am happy I did. Don't have to worry about harming my device anymore. Game killer and all those memory editors didn't work anyway so root was useless to me
Click to expand...
Click to collapse
When I unrooted using SuperSu it ruined my installation also. I was stuck in a bootloop until I installed TWRP and reinstalled SuperSu, terrible!!! It eventually unrooted and I relocked bootloader but nothing worked so I was forced to root and unlock bootloader again.
I am wondering though, how did you return to stock? I really want the latest AT&T stock but when I install that RUU .exe it gives me error 155 so I can't install it. I was using 1.32 stock AT&T and wanted to install 2.6 (I think that's what it is, it's Android 5.1).
I am S-On, and not S-off, could that be an issue? Bootloader is unlocked and I am rooted now.
You know how u r supposed to rename the ruu u want to flash (assuming you downloaded the stock ruu for your carrier and device). The problem for me was, I could never connect my device thought adb after I rooted it (fast boot worked when I put it in fastboot). Even when I could give a command , it could never load the ruu. So what I did, was right click the ruu and click run as admin. It should open up a page on the top saying something about a ruu/rom utility. Make sure you device is connected and had usb debugging( before you got stuck in the loop hopefully). Now click accept and all that good stuff on the utility, it should scan your phone and show u your current rom image, and then show you the latest rom image. Click update and it will boot your phone to boot loader and begin sending it to your phone. IMPORTANT: DO NOT TOUCH YOUR PHONE. Now here's the catch, if it said it failed or something about a USB error, close the program and start it up again. If your phone is stuck without the download bar moving(displayed on your phone), you are going to have to hard reset it. Google how to do it for your device (just a button holding combination). And start the program again. It will take a couple times for the program to work (mine took about 5-6 times). But it will work sooner or later. I am not home atm, but when I get home, I will find the link to the page where this info is displayed in a more orderly fashion and with pictures. It will be tonight, probably about 9 hours. Try this though, if it is too confusing, wait till I post the link. Good Luck!!
EDIT: Sorry just got back home from a long day haha, I'll be sure to look for the link tomorrow. But my directions above should be good, give it a try.
Hi,
My phone is stuck in a bootloop after battery had ran out. Basically I got a new phone and it the HTC sat in a box for about 6 months. Took it out yesterday and it says : Software stats Modified; Locked; S-ON.
I never attempted to root it, never done anything to the phone. Contacted HTC and they shrugged me off.
So I guess I need to try to find out what's wrong myself.
I have the reboot to bootloader; to download mode and to recovery mode options, but none of them work. Each time I try to access one of the options it says "Failed to boot to <...> mode, press up or down to return to menu"
Anyone know what the hell happened?
Thanks
Flash the stock firmware of what it is running now. Eg 3.35.401.12 then flash the zip of 3.35.401.12 via download mode.. stock firmware flash should solve it.
If you can't boot in download most probably you have a dead nand and you can't fix it by yourself.
lucyr03 said:
If you can't boot in download most probably you have a dead nand and you can't fix it by yourself.
Click to expand...
Click to collapse
Is there another way to force the phone into download mode, or to root it? I don't even know exactly what the original version on the phone is, because I never checked, and now, of course, I can't check.
dig_sf said:
Is there another way to force the phone into download mode, or to root it? I don't even know exactly what the original version on the phone is, because I never checked, and now, of course, I can't check.
Click to expand...
Click to collapse
No, you can't do anything, you need a new motherboard.