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?

fastboot mode and recovery mode not working

ok so my gf was on stock 2.1 .
and i wanted to put cust ROM on the phone .. i could not get into fastboot or recovery and found that i need 2.1 with fastboot kdz . so i downloaded that installed via kdz updater . and could still not get into it. so after some searching i found a clockwork rom kdz and downloaded installed that and still cant get into fastboot or recovery ..
here is what my phone is saying in about phone after clockwork kdz flash
gt540
2.1-update1
2.2.29 [email protected] #1 tue oct 5 15:18 edt 2010
gt540-v20a-oct-05-2010
i personally dont think either of the kdz's i flashed worked
also she is rooted
can anyone give me a hand please so i can put cust ROM on her phone

Ok first i need to know what KDZ with fastboot you flashed, second did you check that the KDZ show -- FINISHED -- after 5-10 minutes that takes the process to finish?
What are the combo buttons you're pressing for get in fastboot?
The proper way is CAMERA+POWER BUTTON ( Hold camera button for 1 sec then hold power button without put down camera button, so both buttons needs to be pressed)
The phone will boot , you'll see LG LOGO then after that you should see a dark-blue clean screen (no logo, no letters, NOTHING! just a clean screen). If you get in the mode, congratulations, you are in fastboot now!

Hi IM not on PC at the moment. But I downloaded the 2.1 with fastboot from Modaco (I think) and on the kdz it said all things like param 1-128 call ended and a few other things but noting said fail and then it said finish. I did leave it for about 5 mins after it said finish before I exited and unplugged. I also done camera power and it just boots phone normally.
Sent from my HTC Desire using XDA Premium App

ok i put the v20b 2.1 with fastboot back onto the phone with kdz updater , but i caAN STILL NOT GET IT TO BLANK SCREEN JUST FULL REBOOT TO NORMAL

adz63 said:
ok i put the v20b 2.1 with fastboot back onto the phone with kdz updater , but i caAN STILL NOT GET IT TO BLANK SCREEN JUST FULL REBOOT TO NORMAL
Click to expand...
Click to collapse
ok now that you there try with the KDZ modified by Mur4ik so you get data2system method too...
so follow this:
http://forum.xda-developers.com/showpost.php?p=13620585&postcount=1
Advantages: Its the lates stock 2.1 ROM released in March 2011, it has fastboot and support for recovery as well plus it has been modified for get 238MB of space for install apps.
PS: *When it get stuck at --apram 244 - 245 you done is normal (you wont see -- FINISHED --)
* the process will take 5 minutes, not even 10
* the fastboot screen is blue, more like electric blue with white letters wich is very different than the normal fastboot mode we are used to, so dont panic is normal.

stuck on lg sign after update 2 20e

adz63 said:
stuck on lg sign after update 2 20e
Click to expand...
Click to collapse
get in fastboot do not let it load read carefully the thread because you need to wipe data
fastboot -w

ok got into fastboot on device (i think ) it says suspend reset port change etc .
when running fastboot.exe -w it says waiting for device ..
all drivers are installed correct

adz63 said:
ok got into fastboot on device (i think ) it says suspend reset port change etc .
when running fastboot.exe -w it says waiting for device ..
all drivers are installed correct
Click to expand...
Click to collapse
Is the screen blue with white letters?, if so then you are in fastboot.
What O/S do you have xp, windows 7, 32, 64 bits? you need to install the proper drivers for your pc recognize your phone in fastboot mode
Download Drivers for your computer recognize the phone in fastboot mode. Unzip and put the files inside the folder in C:\android-sdk (take a look of the 3th image)
INSTALL WITH YOUR PHONE PLUGGED:
{
"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 next and it will install the drivers.
FOR MORE INFORMATION ABOUT HOW-TO PROPERLY FLASH ROMS OR ANY OTHER USEFULL INFO PLEASE CLIC ON FAQ | LG GT540 Reference Thread
Veronica

i already had them installed ... i have it fixed now with cm6 2.2.1with fastboot and recovery ..... am going to update it to 2.3 rom now ...
thanks very much for your help

actually saying that i have no mobile network connectivity

adz63 said:
actually saying that i have no mobile network connectivity
Click to expand...
Click to collapse
you need to configure APN with the one of your cellphone provider in Wireles & Network settings >> Access Point Names >> press menu button >> New APN
Veronica

lavero.burgos said:
you need to configure APN with the one of your cellphone provider in Wireles & Network settings >> Access Point Names >> press menu button >> New APN
Veronica
Click to expand...
Click to collapse
thats fixed she now has cm7 2.3.4 and all working normal.... Thanks once again
Sent from my HTC Desire using XDA Premium App

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

[SOLVED] Can't boot, can't boot recovery, oem locked, usb debugging disabled

Happened when I was updating twrp:
I downloaded the .img from their website, booted into my older version of twrp, went to flashing pressed the butting in the bottom right corner, selected the file and selected 'recovery'
Said it was successful, so I rebooted, then it wouldn't do anything anymore except for fastboot.
1. Can't boot into recovery
2. Can't boot normally
3. USB debugging disabled
4. oem locked
Only thing I can enter is fastboot.
I followed this guide, but no luck on my end.
https://forums.oneplus.net/threads/...ck-guide-for-a-hard-bricked-oneplus-2.347607/

Have you tried this?
http://forum.xda-developers.com/oneplus-2/general/guide-return-op2-to-100-stock-unbrick-t3229606
and
All in one toolbox by mauronofrio.
I my self had lost recovery myself and flashed stock image in toolbox and then flashed image from above link to restore to stock and started custom rom process again.
Should not erase twrp once recovered if it has reflash your previous version of twrp or hybrid version.
Hope this helps.

passion8059 said:
Have you tried this?
http://forum.xda-developers.com/oneplus-2/general/guide-return-op2-to-100-stock-unbrick-t3229606
and
All in one toolbox by mauronofrio.
I my self had lost recovery myself and flashed stock image in toolbox and then flashed image from above link to restore to stock and started custom rom process again.
Should not erase twrp once recovered if it has reflash your previous version of twrp or hybrid version.
Hope this helps.
Click to expand...
Click to collapse
It's no use because oem is locked. That means I can't flash anything.

toolbox should still help you unlock bootloader again

Just use the Qualcomm factory restore image to return the phone to original shape of things.

passion8059 said:
toolbox should still help you unlock bootloader again
Click to expand...
Click to collapse
{
"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"
}
pitrus- said:
Just use the Qualcomm factory restore image to return the phone to original shape of things.
Click to expand...
Click to collapse
I have no idea how I would do this without being able to flash anything.

Do you mean that the Qualcomm download program also crashes like fastboot? Sounds like you either have some problems with your windows installation or perhaps you haven't searched for and downloaded the Qualcomm restore if your still trying to flash the ordinary way instead of the emergency way.

Was able to fix it when I was messing around. Not sure what I did but it worked.
Thank you for all your help guys

Theevilsocks said:
Was able to fix it when I was messing around. Not sure what I did but it worked.
Thank you for all your help guys
Click to expand...
Click to collapse
I'm having this problem too, and this isn't helpful. What were the last steps, or at least some of them, that you took to get it working? Which toolkit/script/program were you using? etc

Redjax said:
I'm having this problem too, and this isn't helpful. What were the last steps, or at least some of them, that you took to get it working? Which toolkit/script/program were you using? etc
Click to expand...
Click to collapse
I used this tool: http://forum.xda-developers.com/oneplus-2/general/guide-official-op2-stock-reset-to-oos-3-t3402020
I fiddled around a bit with it, but I'm not sure what I did, and I already deleted the files.

Theevilsocks said:
I used this tool: http://forum.xda-developers.com/oneplus-2/general/guide-official-op2-stock-reset-to-oos-3-t3402020
I fiddled around a bit with it, but I'm not sure what I did, and I already deleted the files.
Click to expand...
Click to collapse
Literally JUST finished with this guide, and my OP2 is alive again! I was going to come back and post. Thanks for the link.
Anyone trying to use this guide without success:
There's one very important step I somehow missed. You MUST disconnect your phone, hold the power button for ~15-20 seconds until it's off, and hold the Volume+ button, THEN plug it back in. Your computer will make the "device connected" sound, but the screen will stay black. THIS IS OK! That means you're in a special recovery, which is where you need to be for the tool.
I also installed the certificate file in the folder I downloaded, then rebooted (it did not work before a reboot, but did work after).
So, the steps:
1. Download the files, make sure your signature signing for drivers is off.
2. Install the trusted certificate, then the driver.
3. Reboot PC
4. Power off phone (hold power for 15-20 secs), hold volume+, then connect through USB (wait for device connected sound, screen on phone will still be black)
5. Run the tool (I ran as admin, not sure if that's required)
6. Weep with joy that you finally found a solution that works.