Database Users

Help! I screwed up :(

Hey guys... friend of mine asked me to put in a custom ROM to his Hero, tires of waiting for HTC to release a 2.1/2.2 for us here in SE Asia.
The phone had already been rooted, but I could not manage to put in a recovery partition, even trying with the GoldCard method.
So, I dug around and found recommendations to try Droid Explorer, which I did, very nice program!
What I did was to use the "update custom ROM" function to put in the ChocolateEclair ROM
Everything seemed to run fine, phone rebooted, showed the new boot animation, then went to a green screen for a few minutes, but this is normal as per the ROM's details page.
But, since then, it's rebooted, it does the boot animation (hand-drawn droid), over and over again, can't get past that. I can get into bootloader and stock recovery screens, though. I'm thinking I should try to wipe the device again, but I cannot select this option in the recovery, it says to press alt-w but that's a bit hard without a keyboard!
I also tried to connect with adb shell (when in recovery mode) but it tells me it cannot find the shell.
So... have I bricked this poor phone? Right now I am downloading the latest RUU I can find, and hope it will work, but if anyone has any experience and advice to share it will be greatly appreciated!

Hey mate... You should have posted in ChocolateEclair topic. Can a mod merge the topics?
To answer you... This does not mean the phone is bricked. Are you sure you don't have a custom recovery image?(boot with home+power) Please paste me your logcat(adb logcat) and I'll tell you what causes the reboot, there's nothing to worry about.

Hey RaduG,
Thanks for getting back so quick! I posted a general thread as I thought it would not be a problem specific to your mod but rather my method or lack thereof
Now the problem is... I can't run logcat either.:
- exec '/system/bin/sh' failed: No such file or directory (2) -
when I go to the recovery image I am quite sure it is the stock one (3D exclamation mark with a phone next to it, then loads the reboot/apply update.zip/wipe data menu. There's also a warning "E: can't open /cache/recovery/command" in yellow at the bottom.

How you try to run logcat? "adb logcat"?

Apparently you can reinstall a recovery using that Droid Explorer?.... I'd try that for AmonRa1.6.2 if Radug cant help you once you have supplied a logcat.
Then load into the recovery, do your wipes, and flash again.

..... And please post in GENERAL or QnA next time.

are you able load into armon recovery console?
if yes try wipe everything & reflash others custom rom then wipe again & reflash ChocolateEclair 1.0.1. i also face the same problem just now when i'm at work *playing with roms secretly* ^^"
i load in success without seeing the green screen now =)
& best not to use the ExtremeKernel as not all phone can support as stated on the dev post =)

ddotpatel said:
Apparently you can reinstall a recovery using that Droid Explorer?.... I'd try that for AmonRa1.6.2 if Radug cant help you once you have supplied a logcat.
Then load into the recovery, do your wipes, and flash again.
Click to expand...
Click to collapse
he is unable to do this atm, as he is stuck at the boot screen...so unable to load previous ROM...
ADB stuff should be the way

Most likely his hero cant be overclocked to 69x mhz. So flash the low kernel.

jarski12345 said:
Most likely his hero cant be overclocked to 69x mhz. So flash the low kernel.
Click to expand...
Click to collapse
I'm quite sure this is the case... but I am so far unable to put in any other ROM. When i get into the stock recovery console, I can select the "apply update.zip" option, but pressing the trackball does nothing, same with the factory wipe option. Are there any other button combinations for these? It says Alt+S and Alt+W for these options, but without a physical keyboard, how to do?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Droid Explorer does let me update a new ROM, but... nothing happens on the phone.
As for trying to put in a new recovery through Droid Explorer, it can only do so by pulling the file for the SDcard... which is not detected when the phone is in recovery mode
I tried to run a recent HTC RUU, but it does not detect the phone...
Last option seems to be working from ADB, yes... But half the commands I try end up with the error "- exec '/system/bin/sh' failed: No such file or directory (2) -"
So, are there any ADB commands I could try, to wipe the device?

Errors while trying to update LG-E612

So I got this phone off a friend and I factory reset it which all worked fine, then I thought I would update it before I got to far. I have not had any success, I have even scoured the forums and the internet without any success so I'm hoping that someone with some experience may be able to assist or point out something I am missing. The phone is stuck in Download mode - I can't get it to boot to the rom at all.
I have a feeling there may be corruption on the phone - You'll see why a little further down, however I cannot be sure.
I am stuck in Download Mode
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I have tried every method to get the update to work that I can find.
I started off by installing all the LG apps and Drivers. The phone is recognised from what I can tell.
I downloaded a couple of stock roms
When I open LG Mobile Support Tool - It says the software is up to date. When I go to 'Options' the only option I get is 'Update Recovery' which I chose and let it download and start installing. Once it gets to 4% is stops. I have pulled the battery and tried over and over again but it keeps stopping the update at 4%. I have even tried removing the battery completely and continuing the install but the same thing happens.
So I tried this over and over with no success. I tried with battery, without battery, I tried getting in Emergency Mode with no success. I tried booting into the OS with no success. So I continued surfing looking for answers.
I found KDZ and thought this might be the missing piece of the puzzle, however this kept crashing every time I tried loading info from the phone and even when I skipped that and just tried installing the ROM.
And the data in the log file looks out of place...
I played around with this hoping to get it to work, but I couldn't. I tried CDMA and it kept failing and it wouldn't even attempt to install the ROM.
So the next one I gave a shot was LG Flash Tool 2014.
This is the only info I can get to pull from the phone.
I am out of options and I'd really like to get this sorted without having to send it off for repair. I see there is an IMEI error - Does anyone know a way for me to repair it?
Any suggestions or experiences you can share that may help would be really great.

Jack_Bauer_AUS said:
So I got this phone off a friend and I factory reset it which all worked fine, then I thought I would update it before I got to far. I have not had any success, I have even scoured the forums and the internet without any success so I'm hoping that someone with some experience may be able to assist or point out something I am missing. The phone is stuck in Download mode - I can't get it to boot to the rom at all.
I have a feeling there may be corruption on the phone - You'll see why a little further down, however I cannot be sure.
I am stuck in Download Mode
I have tried every method to get the update to work that I can find.
I started off by installing all the LG apps and Drivers. The phone is recognised from what I can tell.
I downloaded a couple of stock roms
When I open LG Mobile Support Tool - It says the software is up to date. When I go to 'Options' the only option I get is 'Update Recovery' which I chose and let it download and start installing. Once it gets to 4% is stops. I have pulled the battery and tried over and over again but it keeps stopping the update at 4%. I have even tried removing the battery completely and continuing the install but the same thing happens.
So I tried this over and over with no success. I tried with battery, without battery, I tried getting in Emergency Mode with no success. I tried booting into the OS with no success. So I continued surfing looking for answers.
I found KDZ and thought this might be the missing piece of the puzzle, however this kept crashing every time I tried loading info from the phone and even when I skipped that and just tried installing the ROM.
And the data in the log file looks out of place...
I played around with this hoping to get it to work, but I couldn't. I tried CDMA and it kept failing and it wouldn't even attempt to install the ROM.
So the next one I gave a shot was LG Flash Tool 2014.
This is the only info I can get to pull from the phone.
I am out of options and I'd really like to get this sorted without having to send it off for repair. I see there is an IMEI error - Does anyone know a way for me to repair it?
Any suggestions or experiences you can share that may help would be really great.
Click to expand...
Click to collapse
I haven't viewed the images, but try this
-Goto download mode.
-Open KDZ updater
-Select the kdz, select 3QCT (something like that) and DIAG (forgot the options, its been long since I flashed a stock ROM)
-Flash the kdz
-KDZ updater will crash, it is quite normal
-Do a hard reset (remove battery, put it back, vol - + power + home, when it vibrates remove power and hold on vol - and home for another 5 sec)
-Hopefully, it should boot..
Sent from my Moto G XT1033 using Tapatalk

Make sure you have drivers installed BEFORE conecting the phone.
Also the only flasher that worked for me is this: http://forum.xda-developers.com/showthread.php?t=2409308

N7 (3G, 2012) bricked? Boot mode, no recovery. N Toolkit doesn't flash.

Hello there.
I am writing because I need your help on unbricking my Nexus 7 3G (2012). Yesterday night I was trying to upgrade it from 5.1.0 to 5.1.1 (from the OTA) and I couldn't because I had an error produced by Stickmount. It changed a file on system/bin which I tried to push manually (following some thread's intructions on XDA) and it didn't work, showing error Status 7 (unexpected content on file debuggerd).
Because of that, I decided to flash the 5.1.1 system image using Nexus Toolkit. I set it up so it'd download and install it automatically (using the "Flash stock + Unroot" option). Everything went okay and started the flashing process until the command prop window force closed mid flash, thing that never happened to me before (as I had tried many times flashing from zero my N7 before).
I tried to start the Toolkit again and the command prop window says it flashes bootloader and radio img's successfully, but then a line of code appears and the cmd window force closes again (it says "No se esperaba ( en este momento" or roughly translated as "The ( was not expected at this moment" into English) and my N7 turns off.
Next, I try to turn it on and it shows the Google logo and a green arrow saying "start". I press it and the N7 reboots to the same screen, saying "booting failed" at the top of the screen. If I choose recovery, the same thing happens.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I just can make it to boot to bootloader mode but I cannot flash the firmw (even when this mode must be selected in order to the Toolkit to start flashing). It shows the same line of unexpected code as above.
I tried pushing the files manually using ADB and I cannot may it work either.
What can I do to solve this? I've read that as long as you can get to bootloader mode you can unbrick a device.
I hope you could help me out. Thanks in advance.

Anyone?

Im not a expert, but so if you in bootloader, fastboot (android sdk) dont see your nexus? For check type - 'fastboot devices', if that return something, you can use it to flash recovery/or whole system.
Im linux user, so I dont know how to check how visible is device in windows - and whether drivers are working properly.
I'm sorry if I say the obvious, I just would like to help as much I can. Good luck!

wombat3 said:
Im not a expert, but so if you in bootloader, fastboot (android sdk) dont see your nexus? For check type - 'fastboot devices', if that return something, you can use it to flash recovery/or whole system.
Im linux user, so I dont know how to check how visible is device in windows - and whether drivers are working properly.
I'm sorry if I say the obvious, I just would like to help as much I can. Good luck!
Click to expand...
Click to collapse
Thanks wombat. Actually, the N7 is listed under adb devices. It starts the flashing process but ends automatically without finishing the installation.

i probably hard bricked a1 open for any ideas ( only launch in edl mode)

Hello I recently bought mi a1. First time using xiaomi or aosp kind of devices. I didnt know anything about fastboot, adb etc. Thanks to xda users learned it and open bootlock my phone. I flashed twrp magisk etc and working flawlessly. After oreo update i want to clean flash my device. Since first time using android to now i always made a clean flash to my phones when changing roms or updating major updates. I think this time is the beginning of my agony When i flashed oreo and factory reset the device stuck at first time opening. I waited about 10mins more or less and a bit hasty i turn off my phone. When i turn on the device keep bootlooping to twrp. I have done a thing seen in a thread that i couldnt remember now i will add when i found it.
Now my device doesnt respond to any buttons. No power off no power off + volume up etc. all the combinations No fastboot no adb etc.
*When i plugged in to my pc white led keeps blinking. I searched google about it i thinks its in EDL mode.
When i look at the device manager it says Qualcomm HS-USB QDLoader 9008 (COM6)
When try to flash fastboot room via xiaomiflash it couldnt read hello packet and says Can not read from port COM6
When i use eMMC DL Tool for Customer ENG v5.2.0 R it says Failed to connect phone
When i use QFIL 2.0.1.1 it says sth about sahara. ( i try to flash now but it no errors however nothing on phone.)
Rom i try to flash is tissot_images_7.12.19_7.1
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

onursewimli said:
Hello I recently bought mi a1. First time using xiaomi or aosp kind of devices. I didnt know anything about fastboot, adb etc. Thanks to xda users learned it and open bootlock my phone. I flashed twrp magisk etc and working flawlessly. After oreo update i want to clean flash my device. Since first time using android to now i always made a clean flash to my phones when changing roms or updating major updates. I think this time is the beginning of my agony When i flashed oreo and factory reset the device stuck at first time opening. I waited about 10mins more or less and a bit hasty i turn off my phone. When i turn on the device keep bootlooping to twrp. I have done a thing seen in a thread that i couldnt remember now i will add when i found it.
Now my device doesnt respond to any buttons. No power off no power off + volume up etc. all the combinations No fastboot no adb etc.
*When i plugged in to my pc white led keeps blinking. I searched google about it i thinks its in EDL mode.
When i look at the device manager it says Qualcomm HS-USB QDLoader 9008 (COM6)
When try to flash fastboot room via xiaomiflash it couldnt read hello packet and says Can not read from port COM6
When i use eMMC DL Tool for Customer ENG v5.2.0 R it says Failed to connect phone
When i use QFIL 2.0.1.1 it says sth about sahara. ( i try to flash now but it no errors however nothing on phone.)
Rom i try to flash is tissot_images_7.12.19_7.1
Click to expand...
Click to collapse
Oh, I know that feeling of having bricked one beloved device or at least thinking it is bricked. So I did some new year's digging for you and maybe found a way to help.
Assuming your bootloader is still unlocked and it is really the EDL mode (at least it sounds a lot like it reading the info you have provided) you should have still some good chances.
Please follow this tutorial found here: http://en.miui.com/thread-294318-1-1.html
And for flashing the firmware you are looking for, please have a look at my thread over here, which leads you to the best suited download package of version 7.12.19, that I could find:
https://forum.xda-developers.com/mi-a1/how-to/ota-official-fastboot-image-n2g47h-7-12-t3728929
So give it a go, good luck & please provide your feedback here.
Maybe it can help others too
Edit: I guess the part which is probably the most important is the qualcomm driver

hello thank you for help however i almost tried everything that could be tried. nothing happened. i sent my phone to service. hope they would repair with no additional cost.

onursewimli said:
hello thank you for help however i almost tried everything that could be tried. nothing happened. i sent my phone to service. hope they would repair with no additional cost.
Click to expand...
Click to collapse
Did they fixed it? Without any cost?

I'm having an issue with my G Pad 7 (LG-LK430)

Heres the problem I started getting after I took the update from Magisk this morning. I did the update through Magisk app using their recommended method of flashing it I believe and I think thats how the problems started.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
it just boot loops now with that message over and over again. On top of that error I am unable to boot into Download Mode or Recovery, I get this when I try to:
Any one have any ideas on how to fix this, I'm all ears. Thanks for the help

arksoother said:
Heres the problem I started getting after I took the update from Magisk this morning. I did the update through Magisk app using their recommended method of flashing it I believe and I think thats how the problems started.
it just boot loops now with that message over and over again. On top of that error I am unable to boot into Download Mode or Recovery, I get this when I try to:
Any one have any ideas on how to fix this, I'm all ears. Thanks for the help
Click to expand...
Click to collapse
Try flashing Mr. Bump linked here -> https://forum.xda-developers.com/showpost.php?p=68638985&postcount=54

rahimali said:
Try flashing Mr. Bump linked here -> https://forum.xda-developers.com/showpost.php?p=68638985&postcount=54
Click to expand...
Click to collapse
So here's the problem with doing this, I have no way of flashing Mr.Bump at the moment with the stupid tablet looping like it is. When I plug in the tablet I don't get the bepoop from my laptop telling me its plugged in and ready to go unless I press the power button and volume down. But then I get what the second picture showed, at that point then the pc does the bepoop sound but I still can't do anything with the tablet. So I guess my next question is how do I flash or use this with the state my tablets in? Thanks.

arksoother said:
So here's the problem with doing this, I have no way of flashing Mr.Bump at the moment with the stupid tablet looping like it is. When I plug in the tablet I don't get the bepoop from my laptop telling me its plugged in and ready to go unless I press the power button and volume down. But then I get what the second picture showed, at that point then the pc does the bepoop sound but I still can't do anything with the tablet. So I guess my next question is how do I flash or use this with the state my tablets in? Thanks.
Click to expand...
Click to collapse
Can you not even boot into bootloader/fastboot or TWRP/recovery?
You should be able to boot to recovery by following the steps shown here -> https://www.hardreset.info/devices/lg/lg-lk430-g-pad-f-70/recovery-mode/
You could also try and boot into safe mode and try and use the magisk manager to uninstall magisk - howto here -> https://www.hardreset.info/devices/lg/lg-lk430-g-pad-f-70/safe-mode/

okay update, so if you look at the fsecond picture it says fastboot_init() I assume this means its initialised? I have no idea what any of the stuff below that means. when I do the recovery mode it shows the words recovery for like a second then gives me the black screen with white text that you see in picture 2. when I try the other method all the tablet does is bootloop with a new error code of 2250 I think. So I have know idea whats going on with this. I'll try uninstalling Magisk like you said but things are looking bleak I feel?

arksoother said:
okay update, so if you look at the fsecond picture it says fastboot_init() I assume this means its initialised? I have no idea what any of the stuff below that means. when I do the recovery mode it shows the words recovery for like a second then gives me the black screen with white text that you see in picture 2. when I try the other method all the tablet does is bootloop with a new error code of 2250 I think. So I have know idea whats going on with this. I'll try uninstalling Magisk like you said but things are looking bleak I feel?
Click to expand...
Click to collapse
somebody else apparently had the same experience although on a different LG device -> https://forum.xda-developers.com/lg-spirit/help/help-fastboot-error-loading-keystore-t3430163
So it seems that fastboot commands may have been disabled which means you can't interact with the device in fastboot mode whatever you do.
If nothing else works, you could try and re-flash stock ROM if you can manage to get into download mode.
Best of luck!