Develop Bugs

[Q] Disaster Recovery

Help Please..i really need ur special help,
i have been trying flash a new custom ROM by using ARHD 17.0 n after completion of flashing the firmware to update my Hboot from 1.12 to 1.36, i did not manage to flash the custom ROM since my phone failed to reboot. it stuck and hang at the HTC logo.
after a few research on the forum, i found a threat that might help me with my problems. from the threat ''[TUT] Disaster Recovery - How to recover from nearly everything [Updated 28/04/2012]'', it say that i need to clear the cache on the fastboot. i have tried but the same problems still occurs.
in addition my battery goes very low and i failed to flash any ROM since low battery. i have done the power down steps more than 20 times but my battery still did not charge.
in summary,
1- i still stuck at reboot where it still hang on the HTC Logo even after i clean the ROM cache
2- i still cannot charge my phone even after several times power down and on repeatedly more than 20 times.
i realy need help here, since i realy dunno wut to do even after applying what have been advised in the threat. really hope that someboody can help me with it.

Use this script to charge phone. Did you flash the boot.img?

TToivanen said:
Use this script to charge phone. Did you flash the boot.img?
Click to expand...
Click to collapse
yes i did flash the boot.img after i flash the CWM recovery..

Any way to re-charge the battery if stuck at boot ?

I have a E988 indian version which is stuck at boot with the "secure booting error cause : Boot certification verify",
I can get only into download mode and no recovery or can not boot into OS,
Earlier when i was in the situation i could get into download mode and use LG support tool to flash stock, But now i am getting battery low error..
My question is "Is there any way to recharge the phone if stuck at secure booting error or in download mode ?"
I tried offline KDZ flashing also but there also i was getting battery low error.
Thanks

If you can get to recovery. Mine charges while in recovery.
_________________
Beavers & Ducks!

esimon311 said:
If you can get to recovery. Mine charges while in recovery.
_________________
Beavers & Ducks!
Click to expand...
Click to collapse
i cant get into recovery also.Had installed CWM from freegee and then tried installing philz recovery and resulted in this condition ..
Any other options ?

Akhileshjj said:
I have a E988 indian version which is stuck at boot with the "secure booting error cause : Boot certification verify",
I can get only into download mode and no recovery or can not boot into OS,
Earlier when i was in the situation i could get into download mode and use LG support tool to flash stock, But now i am getting battery low error..
My question is "Is there any way to recharge the phone if stuck at secure booting error or in download mode ?"
I tried offline KDZ flashing also but there also i was getting battery low error.
Thanks
Click to expand...
Click to collapse
Try a factory reset by holding power and volume down at the same time. Press power button to confirm reset. If you do this, sometimes it will reboot you in to recovery, if not try it again and this time manually enter recovery.

uppon2 said:
Try a factory reset by holding power and volume down at the same time. Press power button to confirm reset. If you do this, sometimes it will reboot you in to recovery, if not try it again and this time manually enter recovery.
Click to expand...
Click to collapse
If i try to factory reset it initially asks for do you want to go ahead with factory reset and after i confirm the same old error of secure booting comes in... (factory reset does not happen), And i can not go into recovery mode directly using the volume up and power button...

Akhileshjj said:
If i try to factory reset it initially asks for do you want to go ahead with factory reset and after i confirm the same old error of secure booting comes in... (factory reset does not happen), And i can not go into recovery mode directly using the volume up and power button...
Click to expand...
Click to collapse
Keep trying it over and over. If it still doesn't work I have no idea what you could do. Can you explain how you got in to this problem?

uppon2 said:
Keep trying it over and over. If it still doesn't work I have no idea what you could do. Can you explain how you got in to this problem?
Click to expand...
Click to collapse
I was on CM11. then tried to restore to stock by using one of the CWM backup posted in XDA this landed me in continuous booting into recovery. Then tried to flash philz recovery and got into secure booting error...
now not able to get into recovery, not able to reset , only i am able to get into download mode but not able to use LG flash tool due to low battery error...

Akhileshjj said:
I was on CM11. then tried to restore to stock by using one of the CWM backup posted in XDA this landed me in continuous booting into recovery. Then tried to flash philz recovery and got into secure booting error...
now not able to get into recovery, not able to reset , only i am able to get into download mode but not able to use LG flash tool due to low battery error...
Click to expand...
Click to collapse
I hate that stupid low battery message. It's so dumb that they do not allow you to continue at your own risk. I have also had this problem going from AOSP back to stock. The only safe way to do it is using LG Flash tools first, then flash one of those stock zipped roms. Now it is too late for that. Do they sell your handset in the country you live in? If so, they can fix it in store in most cases. For me, they don't sell this phone in my country, I was just lucky enough to be able to continually try to factory reset and then my phone randomly booted in to recovery (don't know why or how, it just did). After that, I flashed lockified TWRP and CM11 again.

uppon2 said:
I hate that stupid low battery message. It's so dumb that they do not allow you to continue at your own risk. I have also had this problem going from AOSP back to stock. The only safe way to do it is using LG Flash tools first, then flash one of those stock zipped roms. Now it is too late for that. Do they sell your handset in the country you live in? If so, they can fix it in store in most cases. For me, they don't sell this phone in my country, I was just lucky enough to be able to continually try to factory reset and then my phone randomly booted in to recovery (don't know why or how, it just did). After that, I flashed lockified TWRP and CM11 again.
Click to expand...
Click to collapse
Hey, My G Pro is on Miui and everything works fine on it. I can enter recovery mode and all that. But, I want to revert back to stock and this low battery error keeps popping upon during offline flashing. I have seen your method for bypassing it, but I have not found a solution. Is there anything else I can possibly do? Thanks!

Shanewoodward said:
Hey, My G Pro is on Miui and everything works fine on it. I can enter recovery mode and all that. But, I want to revert back to stock and this low battery error keeps popping upon during offline flashing. I have seen your method for bypassing it, but I have not found a solution. Is there anything else I can possibly do? Thanks!
Click to expand...
Click to collapse
This is what I did by accident

The problem, as I see it, is once you root your phone and put the custom recovery on it, CWM or TWRP, it overwrites your factory recovery. I tried using a 10k flashable zip I have to get my phone back to stock. BUT once I tried to get the OTA update to 10P, as another member here pointed out, My phone boot looped. So my question is, is there a way to remove the custom recovery and restore the stock recovery WITHOUT having to go through the PITA process of using flash tools? If there is a way it would save people countless hours fixing their phones just to get an update.
I know many of you don't see this as an issue because your whole point IS flashing new Roms. But from everything I have seen of this phone it's more trouble than it's worth. This phone is so very picky it's ridiculous. I just wnna get the damn 4.4 update, have it rooted to remove bloat, and call it a day. But to answer the OP question, you always have the option of buying a battery station online and charging your battery that way.

Fixed low battery error
My friend managed to fix the low battery error. He tested the method on my phone and during flashing the error did not show up. Will be creating a new thread which fixes the low battery warning soon. Stay tuned !
Sent from my LG-E988 using xda app-developers app

Nice work. And that thread will definitely help allot of others with that issue.

TL;DR
Aside from all the technical stuff, and since the g pro has a removable battery(thank god for that) there are several chargers that you can use which charge the battery outside of your phone. Here where i live (honduras) I have seen quite a few and had one myself(used it to charge spare batteries).

[Q] Help please Samsung Galaxy S3 unbrick.

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.

Help! My phone is bricked!

Ok so I have a samsung galaxy s3 att and I have been rooted for the past month or so, no issues. Then, I decide to install a custom rom so I get a stable cm11 and attempt to flash it and it says my cwm version is too low so the reboot my phone so I can update it. The phone starts to boot and gets stuck on the att globe logo with the blue light pulsing. I shut off the phone, pull out the battery and try again, still nothing. I start getting scared so I restore the nandroid backup I made right before this custom rom incident and boot it, still gets stuck at the same place. I really need my phone fixed so can someone help me please??
I was talking to @sd_shadow on another forum earlier and was wondering if he could help me?

supy99 said:
Ok so I have a samsung galaxy s3 att and I have been rooted for the past month or so, no issues. Then, I decide to install a custom rom so I get a stable cm11 and attempt to flash it and it says my cwm version is too low so the reboot my phone so I can update it. The phone starts to boot and gets stuck on the att globe logo with the blue light pulsing. I shut off the phone, pull out the battery and try again, still nothing. I start getting scared so I restore the nandroid backup I made right before this custom rom incident and boot it, still gets stuck at the same place. I really need my phone fixed so can someone help me please??
I was talking to @sd_shadow on another forum earlier and was wondering if he could help me?
Click to expand...
Click to collapse
this thread may help
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"

Don't panic
Grab the latest version of philz touch recovery https://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2lte/
The zips are made to be flashed from a recovery like cwm. Install it using cwm, reboot into recovery and philz should come up. You should be able to proceed with wiping and installing your custom rom at this point.
If the zip doesn't work out for some reason, you could also use Odin to flash a .tar.md5 from that link to update your recovery.

Try this: http://forum.xda-developers.com/showpost.php?p=60162192&postcount=2

Is there any solution for boot loop in gt-i9192?

Is there any solution for boot loop in gt-i9192?
My phone was rooted. I was using s5 rom proyect and my recovery was Philz Touch Recovery. I was happily using this rom for arround 8 months. Recently my phone was responding slow and my storage was almost full. One day while watching youtube videos my phone got hang! I just removed the battery and tried to restart. But there was a failure and no vibration. The phone is simply dead. I connected my charger and of :crying:course there was no indication. Later I went through several post to learn how to revive my phone from hard brick. I downloaded debrick.img file and made a bootable memory card. This time I was able to switch on my phone but it went through bootloop. The recovery mode takes too long to load and wiping cache and dalvik cache or even reset was not possible because of some error like E: failed to mount ......
Then I went into the download mode. and installed a firmware from sam mobile. Later I flashed CWM recovery through odin successfully.
But this bootloop still exists. Whenever I try to go into recovery mode it still takes a long time. And istead of loading CWM recovery it loads philz recovery mode that was previously installed
Please help I am tired

mbiotanveer said:
Is there any solution for boot loop in gt-i9192?
My phone was rooted. I was using s5 rom proyect and my recovery was Philz Touch Recovery. I was happily using this rom for arround 8 months. Recently my phone was responding slow and my storage was almost full. One day while watching youtube videos my phone got hang! I just removed the battery and tried to restart. But there was a failure and no vibration. The phone is simply dead. I connected my charger and of :crying:course there was no indication. Later I went through several post to learn how to revive my phone from hard brick. I downloaded debrick.img file and made a bootable memory card. This time I was able to switch on my phone but it went through bootloop. The recovery mode takes too long to load and wiping cache and dalvik cache or even reset was not possible because of some error like E: failed to mount ......
Then I went into the download mode. and installed a firmware from sam mobile. Later I flashed CWM recovery through odin successfully.
But this bootloop still exists. Whenever I try to go into recovery mode it still takes a long time. And istead of loading CWM recovery it loads philz recovery mode that was previously installed
Please help I am tired
Click to expand...
Click to collapse
Dude,
I am also having a bootloop problem on my S4 Mini GT-I9192...
My TWRP recovery was working, I was using version 3.0.0.0 for serrano3gxx, but when I tried installing a custom rom, the right rom for gt-i9192!!!! for some stupid reason the twrp recovery keeps thinking that my phone is gt-i9190 !!!! it is so stupid!!!
for this stupid reason I couldn't install the ROM !!!
I decided to install the right recovery for my gt-i9192, so I downloaded openrecovery-twrp-2.8.7.0-serranodsxx-STABLE-signed
now, there was a warning to not install the zip using the recovery, but how could I install the recovery if I am unable to install anything with Odin!!!!
Nothing at all!!! I can't install anything with Odin, it just gets stuck!!!! So frustrating!!!!
And now afer I installed it said the installation completed successfully, but..... I can not even get the phone in recovery mode!!!!
What happened??? can anyone please help!!!
I am stuck in this stupid bootloop problem, and now on top of it I can't even go to recovery mode!!!! Nothing!!!
It is useless to do anything with Odin either, it recognises the phone, it says Added! but cannot install anything, it just gets stuck
WHAT CAN I DO?????
PLEASE HELP IF YOU CAN.

Check out
You can try this:
1. Download this file: openrecovery-twrp-3.0.0-0-serranodsxx-STABLE-signed.zip and copy the file in sd card
2. Then go to recovery mood.
3. Install the zip file from sd card.
4. hope you will be able to install the correct recovery mood.

mbiotanveer said:
You can try this:
1. Download this file: openrecovery-twrp-3.0.0-0-serranodsxx-STABLE-signed.zip and copy the file in sd card
2. Then go to recovery mood.
3. Install the zip file from sd card.
4. hope you will be able to install the correct recovery mood.
Click to expand...
Click to collapse
I think you didn't understand... My phone is not going into recovery at all!!!

I had this problem once when I flashed an incompatible kernel, but I forgot how I got out of it. Best suggestion I have is take out the battery and put it back.
The "hard brick" you suffer the first time was likely a dead battery. The phone looks hard bricked when a battery is below critical energy, and not enough power is available to charge it with an USB. At that point, you had to wait for the energy in the battery to store up again, and then plug it into the USB to charge. Just a little power was necessary to get it charged again.
If you can still access download mode, flash the stock ROM baseband of your phone (you should know what this is). Your data will be wipe but at least you will be able to use the phone again.

Teracotta said:
I had this problem once when I flashed an incompatible kernel, but I forgot how I got out of it. Best suggestion I have is take out the battery and put it back.
The "hard brick" you suffer the first time was likely a dead battery. The phone looks hard bricked when a battery is below critical energy, and not enough power is available to charge it with an USB. At that point, you had to wait for the energy in the battery to store up again, and then plug it into the USB to charge. Just a little power was necessary to get it charged again.
If you can still access download mode, flash the stock ROM baseband of your phone (you should know what this is). Your data will be wipe but at least you will be able to use the phone again.
Click to expand...
Click to collapse
Bro hard brick was not a low battery case. I kept it connected to the charger for almost a day. Can you please just say how to solve the problem. I am totally disappointed.

Samsung Galaxy s4 mini (GT-I9192)
Also help me please i wanted to flash the firmware that i just downloaded from sammobile but if i started flashing, my phone stays the same like nothing happen. please help meee.. I've working on it since last month

Hi, anybody here can solve the problem? I have a S4 Mini I9195, is in a bootloop, can enter Download Mode, but not in Recovery Mode, I try flash stock ROM, Recovery y Custom Recory, I used both ODIN and Haindell, always said OK in both flash, but I still can´t enter in Recovery Mode