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?

Htc logo white screen stuck

Im in great confusion right now... please developers, please help me... yesterday I used alpharevx to s-off my wildfire that has 1.01.002 unbranded hboot.. successful and then i have rooted it and its successful and then i tried flashing cyanogen 7 its stuck for 3hrs in installing updates, iremoved the battery now i only have htc whitescreen.. ican still boot to hboot and recovery (3.0.0.6) ive downloaded different roms, ihave openfire and couple of other roms under froyo build. but i had the "amend scripting error" i have searched and it seems that i need to flash an older version of clockworkmod .. i ended up downloading everything all versions.. when im trying to flash it... its giving me an error "installation aborted" I ended up STARTING this thread LOOKING for a small string of hope that my phone will BOOT TO NORMAL MODE... please, I'm not a developer and im in great panick... i hope my phone is not brick... thankyou

Try a different version of Clockworkmod. 3.0.0.6 is giving similar issues to many users. Try 3.1.0.2 for installing CM and Gingerbread ROMs . and 2.5.0.7 for Sense based Eclair / Froyo ROMs.
Both can be found here (Point 6)
http://forum.xda-developers.com/showthread.php?t=1029318
You can use Fastboot Mode for replacing and installing a new Recovery. Short Guide:
1.) Install Android SDK,
2.) Get the Recovery.IMG file of the Clockworkmod version you want to flash. (I linked the thread above, where you can get it)
3.) Place this in the SDK's Tools folder.
4.) Reboot your phone in the bootloader mode. (Power Down. Press Vol Down + Power Key together)
5.) Enter Fastboot mode (Press Power button on Fastboot).
6.) Open Command Prompt on Windows.
7.) cd (browse) to the SDK's tools folder.
8.) Type the following command: "fastboot flash recovery recovery.img". (Without quotes.)
Screen here (My SDK is in D:\Android)
{
"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"
}
NOTE: You don't even need the complete Android SDK to do this. Just the ADB and Fastboot Binaries will do. But, still I wrote with the SDK, because that is how I did it, and, it worked for me. Anyway. you can get that here:
http://forum.xda-developers.com/showthread.php?p=14693680 (Check Attachments)

thank you very much!
3xeno thankyou... i will try it now

the best!
3xeno i sucessfully flashed the old recovery! i successfully flashed ANONIMO'S-ROM (Froyo 2.2.1)! thank you very much its been 28hrs now without sleep and i thought my phone is bricked! THANK YOU VERY MUCH!

hydro25 said:
3xeno i sucessfully flashed the old recovery! i successfully flashed ANONIMO'S-ROM (Froyo 2.2.1)! thank you very much its been 28hrs now without sleep and i thought my phone is bricked! THANK YOU VERY MUCH!
Click to expand...
Click to collapse
If u can access hboot/fastboot/recovery menu, then u can solve any software problem the phone has. And certainly the phone is not bricked in above cases.
A bricked phone will not even show the splash screen on powering on. Although excluding the offline charging bug (search for it if u don't know).
And AFAIK, possibility of brick is only when flashing hboot and radio.
Sent from my HTC Wildfire using XDA App

bharatgaddameedi said:
If u can access hboot/fastboot/recovery menu, then u can solve any software problem the phone has. And certainly the phone is not bricked in above cases.
A bricked phone will not even show the splash screen on powering on. Although excluding the offline charging bug (search for it if u don't know).
And AFAIK, possibility of brick is only when flashing hboot and radio.
Sent from my HTC Wildfire using XDA App
Click to expand...
Click to collapse
noted... thank you for spending time reading...

Reset to factory stock XNPH38R

Hi All,
if you want an easy way to reset to stock, this is it. Works like a dream, for that squeeky clean, out of the packet install feeling.
This method uses a full 38R factory image from cyanogenmod.
I take no glory for this as our hero @MooDeeY has done the hard work.
You can find the original cyanogenmod files here
http://builds.cyngn.com/factory/bacon/cm-11.0-XNPH38R-bacon-signed-fastboot.zip
MD5: 01e7fc376c13614d38f5c4201310a1bb
http://builds.cyngn.com/factory/bacon/cm-11.0-XNPH38R-bacon-boot-debuggable.img
MD5: 88209189b99ffb7a6bf2534c3b03ab80
No ota baggage here!
"Step 1: Download full XNPH38R rom from here, with adb files & extract it.
https://mega.co.nz/#!NtUxwbBQ!YyOIreiqfJKCC6ZKNwlxi5ubskTLSGKH-DwR39hF_IM
Step 2: Make sure that your phone isn't connected to your PC via USB, because its some times prevent phone from entering fastboot mode correctly.
Step 3: Press VOL+ & Power Button. until you see Fastboot logo. it should be like this picture.
{
"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"
}
Note: Some times it ask to confirm if it's your first time to unlock it if you came from Color OS version.
you can use volume buttons to choose between menus and choose yes & Power button for confirm.
Step 4: Connect your phone to pc.
Step 5: In folder that you downloaded in first step you will find a file called Bootloader Unlock just press it & press any key on your keyboard to begin unlock your boot loader.
Step 6: Your phone will restart after unlock. Power it off again & Do Steps 2,3,4 again.
WHY I SHOULD USE THIS WAY !!
- if you have chinese version (Color OS) & want to make it 100% Original cyanogen.
- if you device is bricked or boot loop and can't make it work again.
- if you facing errors after OTA update.
- if your version is too old & want to install latest one without install any previous update.
- if you facing wi-fi issue or connection problem.
** this way install a complete rom from A-Z including stock recovery, modem, boot image, etc.....
Step 7: You will Notice that there is others two files in folder:
Install Rom 16GB = for 16gb phone.
Install Rom 64GB = for 64gb phone.
just open it, press any key, it will start installing new rom for you & lock your bootloader again.
Notice: When downloading using google chrome, maybe a warning message appears to you, this because folder contain .bat files. it's completely safe."
I have been running this since about 10:30 ths morning and it has been problem free. I also got the best antutu score I ever got for this rom on the oneplus with this method, so its cool in my book. I also noticed a big reduction in battery usage, but theres no stats behind this claim.
One last point, this does use the latest images. Its just that cyanogenmod have not updated their website yet.

Why lock the bootloader on the end?

Finally, there's some legit 38R factory images! Why do they still have 33R on https://cyngn.com/products/oneplusone? Thanks for the link! :laugh: :good:

Schrotty35 said:
Why lock the bootloader on the end?
Click to expand...
Click to collapse
Because it returns to stock. You can edit this out in the script if you want it left unlocked.

There's no need to relock the bootloader. In fact, in several cases locking the bootloader has resulted in not being able to unlock it again.
Transmitted via Bacon

the link in step one dosent work, could u put up the link again
thanks, i bricked my phone

Boot Up Question

Hi, I picked up this phone through a private sale and, while it works fine, I noticed a couple of things during boot up. This first flashed on the screen:
{
"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"
}
Then it went away and the following flashed on the screen:
Then it went to the main screen. Does this mean that something has been loaded onto the phone? What should I do to get it back to factory?
Thanks in advance.

vik123 said:
Hi, I picked up this phone through a private sale and, while it works fine, I noticed a couple of things during boot up. This first flashed on the screen:
Then it went away and the following flashed on the screen:
Then it went to the main screen. Does this mean that something has been loaded onto the phone? What should I do to get it back to factory?
Thanks in advance.
Click to expand...
Click to collapse
The first screen indicates the bootloader is unlocked.
The second means you are not stock but running a custom ROM.
Back to stock -> https://forum.xda-developers.com/essential-phone/development/stock-7-1-1-nmj20d-t3701681

Thank you for the link. I checked it but I am not sure which file to download. Sorry, I am not very familiar with all of this and I am nervous about bricking my phone.

vik123 said:
Thank you for the link. I checked it but I am not sure which file to download. Sorry, I am not very familiar with all of this and I am nervous about bricking my phone.
Click to expand...
Click to collapse
Plug your phone into your PC using a good USB 3.0 cable after you reboot into the bootloader (do this by holding down volume down and power button at once. Also, use a type a to c cable, the essential phone stock USB c to c cable doesn't work that well for flashing stuff).
Then install the drivers for this phone from here on a windows system: https://storage.googleapis.com/essential-static/Essential-PH1-WindowsDrivers.exe
Then install minimal adb and fastboot from here: https://www.androidfilehost.com/?fid=745425885120698566
Then, download the latest back to stock zip from here:
https://www.androidfilehost.com/?fid=745425885120698566
Unzip into the folder you installed minimal adb and fastboot into, and then open minimal adb and fastboot. In the command window that pops up, type "flash-all.bat && fastboot -w" and then hit enter. This will reflash all the stock partitions and wipe all data.
After you get the stock essential phone firmware booting, you can reboot into the bootloader and run "fastboot -w" and then "fastboot flashing lock" to relock the boatloader if you plan on keeping the stock unmodified firmware.
Credit goes to @aer0zer0 for the dump of the latest firmware.

Thank you so much. I followed the instructions and, while there were some nervous moments, managed to get it back to stock.

I can't believe the previous owner was such a jerk. I always return phones to full stock and relock the bootloader if I plan to sell a phone.

vik123 said:
Thank you so much. I followed the instructions and, while there were some nervous moments, managed to get it back to stock.
Click to expand...
Click to collapse
Hey no problem, always glad to help, especially since the situation you were in was caused by the previous owner not caring to flash stock and relock the bootloader before he sold you the phone. Seems like a careless thing to do, especially since he could've sold the phone to someone who wouldn't be tech savvy enough to restore stock.

The seller was really nice so I have a hard time calling him a jerk, but yeah, it was a careless thing to do. If it wasn't for this community I would probably have been screwed.
Thanks again everybody.

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!