Database Info

[Solved] almost bricked mt4g. please verify my next step

First, let me say thanks to all who contribute. I started with a G1 when it first came out, using the JF mods and lurking these forums for hours. Without you guys, we'd all be stuck with boring stock devices!
Heres my question:
I've done a search and just want someone to verify my next planned step.
Tonight I think almost bricked my Mytouch 4g. I had root, and had CM6.1.2-RC2 installed. It was working great.
Then I wanted to get the CM7 nightlies working. I couldn't get the CM7 rom past the mytouch splash screen. So, I upgraded Rom Manager, and thought i had to upgrade ClockworkMod to 3.0 to get the CM7 nightly rom to boot. I accidentaly flashed the wrong ClockworkMod Recovery. I flashed the file that was for a G2 (vision). Rebooted without noticing my mistake, than noticed my error when I couldn't get into recovery mode.
Fortunately i installed Hboot during the rooting process. I'm planning on letting Hboot flash the file mentioned in this post to get back to stock:
http://forum.xda-developers.com/showpost.php?p=10514066
What do you think?
Just don't want to get myself in deeper S...
Thanks again.

connect the usb and run adb. Boot into bootloader and flash the recovery 3.0??? that way. You'll be good to go after that

osugsxr said:
connect the usb and run adb. Boot into bootloader and flash the recovery 3.0??? that way. You'll be good to go after that
Click to expand...
Click to collapse
You can connect adb with the bootloader? I ran:
Code:
adb devices
and adb came back with no devices found.
How do I flash the recovery if adb has nothing to communicate with?
BTW, I'm using Hboot Engineering, and Hboot does recognize the usb connection by displaying: HBOOT USB PLUG

fastboot devices

fastboot devices
fastboot flash recovery recovery.img

SOLVED
Thanks for trying to help osugsxr. I will have to read up on fastboot.
However, I did not follow your advice. I didn't get your reply in time to try fastboot. My impatient ADD personality went ahead and followed the advice in the thread that I referred to in my original post. In an effort to help others who may have gotten into a jam, heres what I did:
1. Took out my SD card and connected it to my PC via external SD card reader.
2. Because I had a ton of crap on the SD card, I formatted it FAT32 to have a clean card.
3. Downloaded the stock Glacier rom (A large 315mb file. Should have a filename like PD15IMG_Glacier_TMOUS_1.17.531.2_Radio_12.28b.60.140e_26.03.02.26_M_release_155771_signed.zip)
4. Copied the stock Glacier rom to the SD blank card.
5. Renamed the rom to PD15IMG.zip (maybe case sensitive, not sure)
6. Unmounted/Ejected the SD card from the PC reader an put it back in my phone.
7. Pulled the battery on my phone for about a minute then put it back in.
7. Hold volume down and the power button at the same time.
8. Hboot should start up, then after a few moments it will say loading PD15IMG.zip. After PD15IMG.zip loads, it will ask you "Do you want to start update?". Press VOL UP for Yes.
9. You will then see Hboot working its way down a list of about 9 items. Be patient, this takes a while. After this is done, it will say so, and tell you to press the power button to reboot.
Hopefully you have successfully flashed the stock rom, and your phone will be back to what it was like when you first bought it.
I attached pictures of the Hboot screen and flashing process for reference

[SOLVED] gt-i9023 help please - no usb,adb,fastboot access

I am a beginner at this so please excuse me.
I successfully rooted my phone, installed clockwork, super user was working, could connect like a dream with usb to the phone. Flashed stuff using fastboot in command line - all was good.
When I say successfully it did take a long time, the phone didnt work for a while but I flashed clockwork on then flashed the rom for my phone from here http://forum.xda-developers.com/archive/index.php/t-1063664.html
I used this one:
Android 2.3.3/GRI40/KB1 Radio/KA3 Bootloader (http://android.clients.google.com/p...2cf141e6a.signed-soju-ota-102588.f182cf14.zip)
Works on: I9020T, I9023
Official, signed, can flash with ClockworkMod or stock recovery. Contains recovery, radio and bootloader.
Which was great - sorted the phone a treat - I had the super user working - I installed the clockwork rom app - worked a treat - even did a backup (I think)
Then the phone tried to update to 2.3.4 which failed - right now I should of check the forums but thought I know I'll just flash the update from the above page - which failed - not to be defeated I tried harder using different roms through clockwork recovery or clockwork rom mod until sucess 2.3.4 GRJ22 build.
Then I find the super user app doesnt work or the clockwork rom - no problem boot into clockwork recovery - uh oh thats gone as well though i can get to android recovery.
I'll just flash clockwork recovery on but I cant as I've no access with adb or fastboot the phone is not connecting to the pc in fastboot mode with the android logo and phone details.
When I'm trying to use USB connection on the phone normally the USB man goes orange then back to green - and the phone prepares the USB storage again.
I can use a app to get files on to the sd card for use with android recovery so i try to reflash the 2.3.3 rom above that worked but I get the status 7 error with a long number 1297306095
I try the update again and this is where i realise that the update ROM i put on was the wrong one.
I flashed this: Android 2.3.3 (Build GRI54/KB3 Radio/KA3 Bootloader) (whole rom)
I should of flashed this Android 2.3.3 (Build GRI40/KB1 Radio/KA3 Bootloader) (smaller update)
I can flash the correct update above but it doesnt change anything.
I have spent a few days now trawling the forum with little success and having got all the correct drivers on the pc and had it connecting fine I am assuming it is a phone issue now
the base band details have changed from XXKB1 to XXKD1 and the build from GRI40 to GRJ22
I am at my wits end here and before I put a hammer to my phone and send it back as an insurance job I'd like to mend my stupid mistakes.
Thanks
Acne

it doesnt matter if you flashed the whole rom. (provided you didnt use odin)
first thing, try to format sd card through the phone,
then enable usb debugging and try using adb n fastboot.
also, try to flash a newer recovery.img ( be careful no to use one not meant for ur phone e.g ns4g...)
post ur results.
good luck

can't find an option from within the phone to format the SD card - found an app on the store that is called "format sd" which did something and allowed me to connect to the USB once but it was very flaky and took a few attempts at the "turn on usb" screen to get it to connect. I'm not sure that it wasnt just deleting the data from the sd rather than formatting as it took maybe 10 seconds first time and now its done straight away if I try again.
Edit - i've used the stock erase usb command within the phone and the USB connection within the phone seems to becoming more stable - I can read and write data to it from the pc but it still struggles to connect first time.
No change with command line commands abd or fastboot neither are connecting.
I've come to the conclusion that maybe I need to flash a newer recovery image (ROM?) myself but where do I find one? And how do i check that it really is the correct one for my phone - which of the details are important - should i use the original stock details? I'm confused, remembering all I can use is the "Android system recovery <3e>" that only gives me the option of reboot, apply update from sd card, wipe data/factory reset, & wipe cache partition.
I flashed the wrong ROM with the clockwork rom app from within the phone I dont know what odin is.
Thanks for the pointer anymore ideas or direction appreciated.
Acne

Try to wipe from the stock recovery and then install this
http://android.clients.google.com/p...2cf141e6a.signed-soju-ota-102588.f182cf14.zip
It is the full 2.3.3. It will return your phone to complete stock 2.3.3
P.s sorry i am not being able to help more. I am myself in a far bigger trouble

I tried that rom but got the status7 error. That one worked before under clockwork but won't reflash now. I can do a factory reset under stock but will that make a difference? I thought all that did was reset user data not the system data. I think l need to wait for a new stock Tom to be issued.
Acne

Tried the reset phone from within the phone and reset using stock recovery, still cant flash the old 2.3.3 rom above getting the status 7 error:
assert failed ! less_than _int(1297306095. getprop(ro.build.date.utc"))
so the usb works fine from within the phone when the phone is running normally, when I connect the phone in fastboot mode it shows as an Android ADB interface on the "safely remove hardware" window but i cant use any command prompt instructions on the phone - using fastboot devices to show connected devices I get no reponse.
Any ideas?
Any pointers to a later rom that will correct my problems?
Thanks
Acne

After a bit of experimenting I find that when the phone is switched on normally I can use the ADB devices command to return the ID of the phone. The fastboot devices command still returns a blank.
Is this normal?
Does this mean I could flash the clockwork recovery image onto the phone? or can all that malarkey only be done in fastboot mode?
thanks
Acne

You need the fastboot devices command to return your phone info then you can fastboot flash recovery in order to try flashing a recovery that will allow you to flash the rom you are getting a failed message from. The stock recovery can only flash official updates put out by Google iirc.
I am thinking you are having driver issues on the PC you are using. Try another PC with fresh drivers or uninstall and reinstall the drivers on the one you have been using.
sent from the nexus of the 4g universe

I've read up on the driver problems, I tried the phone on two different pcs using two different methods on each to install the correct drivers. none work. The phone used to connect fine which is how i rooted the phone. I'm using the same pc, same supplied cable and can see the ADB mounted in the "safely remove hardware" window
The adb command works when the phone is switched on normally, but not fastboot command.
When in fastboot mode neither works. Looking in device manager the android adb interface is listed fine under android phone.
I'm pretty sure its not the drivers.
Doesn't the above prove that the pc connects fine but the phone is broken in fastboot mode?

You could still flash the latest 2.3.4 full ROM with ODIN. The Phone will be restored completely and then you can root it again.

Thats great Odin looks like it will be the way forward, just so I dont make another noob error could someone point me in the right direction for the correct version of odin and a guide on how to use it. I have looked around the forum but am struggling to find the relevant thread
I have tried the usb/2 button and it enters download, the version od odin that i found (1.81) does see the phone but I think that version is for the 9020 only I have the GT-i9023 so dont want to use the wrong programme/rom
Thanks
Acne

Ok took a chance and flashed the phone with odin - great it worked reset all the fastboot mode values back to their original ones when i got the phone. (seems I chose the correct rom) the only difference is that the Carrier info is now EUR not VDF as it was when I first got the phone.
Applied the auto update to 2.3.4
Tried at every step but I still have no fastboot or ADB access the phone just doesnt connect. Tried different leads, tried different usb ports - nothing.
I'm stumped now unless there are any advanced settings in odin I should try.
Acne
The

Discovered after the auto update to 2.3.4 that the USB connection from within the phone was "broken" again, To sort this i did a format cache and reset phone from the stock recovery which sorted the usb connection. so thats that one solved then.
tried again to connect via command prompt, unistalled drivers - reinstalled drivers - no change still no devices detetcted.
Any good ideas?

Solved
using the usbdeview mentioned here I uninstalled all the usb drivers on my pc that looked like they could be anything remotely connected to the nexus and samsung.
I ran and updated/download pretty much everything i could through SDK
Then I did everything I read in this thread
Up till then I had been using the fastboot command found and downloaded through this thread
That continued not to work but when i tried the fastboot in the android-sdk/tools folder I finally got fastboot access.
Solved Solved Solved
to get my phone unlocked and updated I did an odin restore to 2.3.3 let it auto update to 2.3.4 copied the su(superuser zip) to the sd card. flashed clockwork recovery and then installed the su.zip with clockwork. after that I installed the rom manager from the android shop and Inow have the phone just how i want it.
To all those that have helped with their ideas here many many thanks.
Acne

ROM won't boot, can't get to recovery, only bootloader

I was running the Hypernonsense ROM and wanted to try a diff kernel. I flashed the newest faux kernel and now it's stuck at the first boot screen.
I do a battery pull and can voldown + power and get to the bootloader, but the problem there is that it sees the latest 3.32 P58IMG update on my SD card every time and won't let me select any other options. I can flash that over and over, but it's still sticking at the first boot screen, doesn't make it to the ROM's bootup screen.

Delete PG58IMG.zip.
Hang on, isn't Hyper-non-Sense ROM based on ICS? Faux's kernel's are only for Gingerbread based ROMs. Reflash the ROM to restore the 'stock' kernel.

help please
wmoore said:
Delete PG58IMG.zip.
Hang on, isn't Hyper-non-Sense ROM based on ICS? Faux's kernel's are only for Gingerbread based ROMs. Reflash the ROM to restore the 'stock' kernel.
Click to expand...
Click to collapse
How do I get to a point where I can delete the IMG file or reflash...it's just "stuck".

take the sd card out,
boot the phone into the boot loader
go to recovery
it will start counting down or whatever looking for the sd card
put the card back in
it will see the sd card
it will continue on into recovery
connect to pc
mount usb in recovery
delete img file
reboot now if you like everything will be back to normal
* i believe this will also work if you put the sd card in after the bootloader is loaded before you go to recovery, the card just needs to be not present while the bootloader is loading. i believe it checks the card when it loads the bootloader, but after the bootloader comes up you can put the card back in then proceed to recovery

dwcasey said:
How do I get to a point where I can delete the IMG file or reflash...it's just "stuck".
Click to expand...
Click to collapse
Ok, I was able to have it plugged into my laptop, voldown+power until I heard windows "bing" like a new device connected.
Then I went to a command prompt where I have adb installed and ran
adb devices
To make sure it was connected and it was. Then I ran
adb reboot recovery
And now I'm back to 4EXT recovery...phew, was getting worried. Gonna super wipe and install a new ROM.

I'm sweating bullets now cause I only have a Mac computer

PamelaGirl said:
I'm sweating bullets now cause I only have a Mac computer
Click to expand...
Click to collapse
Hi,
What is the problem?

Hello malybru,
Yesterday my device got stuck and I couldn't boot up and I could not access recovery.
I than found these steps that would allow a Mac user access to adb and fastboot.
[GUIDE] Set up ADB and Fastboot on a Mac easily (With Screenshots!)
http://forum.xda-developers.com/showthread.php?t=1917237
Now I am all good again, but I was nervous at first cause it seemed like most of the tools are PC related.
Thank you

Stucked in BooLoader

By mistake due to some problems I've accidentily deleted internal storage in the bootloader mode. Meaning that I can't get into android and I can't install any ROM (since i've deleted the storage). How does one fix this problem? How do I connect it to the computer and upload rom?
Ty

Moose321 said:
By mistake due to some problems I've accidentily deleted internal storage in the bootloader mode. Meaning that I can't get into android and I can't install any ROM (since i've deleted the storage). How does one fix this problem? How do I connect it to the computer and upload rom?
Ty
Click to expand...
Click to collapse
You can either push a rom to your device through a custom recovery using adb or flash the factory image. You also might be able to see your device when booted into recovery and copy and paste a rom to it.
Sent from my Nexus 5 using XDA Free mobile app

jd1639 said:
You can either push a rom to your device through a custom recovery using adb or flash the factory image. You also might be able to see your device when booted into recovery and copy and paste a rom to it.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
More details pls :/ I cant just plug it into computer and upload it, it doesnt go into the system and it has that SD card issue :/

Well I’ve managed to make every turn possible with my hammerhead. I’ll just explain these turns as much as I can.
1. Unlocked the device
2. Installed ROM, everything was OK.
3. Applied different ROM, started having problems with SD card. Installed TWRP manager, problem fixed. Though there were some space issues (backup 6 gb and so on)
4. Made the worst turn, bootloader mode, deleted internal storage, wiped.
5. In turns on, goes into cataclysm rom, but the system doesnt show and Back buttons or minimize or Home (those 3 buttons at the foot of the phone), wallpaper is black. IF u connect it to the computer, the internal system is just EMPTY. Can’t transfer any rom to the phone. Cant go to the store and install TWRP manager. All kinds of crazy ****.
6. Tried Force flashing it with nexus root toolkit while in bootloader mode. Failed. Doesnt recognize the device, bootloader on the phone freezes.

[Q] Need help with flashing recovery image PLEASE!

Hi everyone,
Forgive me if this is a noob question but I've been searching all night and I cannot find a solution.
Background - A friends sister recently passed away and she asked me if I could somehow get the data off of her phone. The phone is a Boost Mobile LG855 (Marquee). It is not rooted, is not in debug mode and is keylocked. We don't have the unlock code so based on what I've read, my only hope is to get CWM somehow flashed on the phone and use it to back up the phone data to the SD card.
Because I cannot get the phone into debug mode and there doesn't seem to be a download mode on this phone, any of the USB-based flashing techniques will not work. I am able to connect the phone as a storage device and access the SD card from my computer but I can't get the computer to recognize it as an ADB device. So that rules out the fastboot, adb or odin-like methods. I believe my only hope is to use the stock recovery to flash CWM from the SD Card (update.zip method).
I downloaded the CWM image for this phone (recovery-clockwork-5.0.2.8-marquee.img) but I can only flash a file called "update.zip" from the stock recovery options. I read somewhere that I should be able to rename the image file to "recovery.img" and put it in an uncompressed "update.zip" file which I did. I copied it to the SD card and tried the flash it only to get the dreaded "E: signature verification failed" "installation aborted." message.
Here are my questions:
Is what I am trying to do even possible?
Can I flash a .img image by sticking it in an update.zip file?
Do I need to create a /dev/recovery/ structure inside the zip file?
If so, how do I fix the zip file so it doesn't fail the signature verification?
Is there a better way to do what I am trying to do?
There are all kinds of tutorials on how to use CWM to flash things from the SD card but surprisingly few that describe how to do what I am trying.
Any help or suggestions would be most appreciated. Thank you so much in advance.

JZ_Hack_Nub said:
Hi everyone,
Forgive me if this is a noob question but I've been searching all night and I cannot find a solution.
Background - A friends sister recently passed away and she asked me if I could somehow get the data off of her phone. The phone is a Boost Mobile LG855 (Marquee). It is not rooted, is not in debug mode and is keylocked. We don't have the unlock code so based on what I've read, my only hope is to get CWM somehow flashed on the phone and use it to back up the phone data to the SD card.
Because I cannot get the phone into debug mode and there doesn't seem to be a download mode on this phone, any of the USB-based flashing techniques will not work. I am able to connect the phone as a storage device and access the SD card from my computer but I can't get the computer to recognize it as an ADB device. So that rules out the fastboot, adb or odin-like methods. I believe my only hope is to use the stock recovery to flash CWM from the SD Card (update.zip method).
I downloaded the CWM image for this phone (recovery-clockwork-5.0.2.8-marquee.img) but I can only flash a file called "update.zip" from the stock recovery options. I read somewhere that I should be able to rename the image file to "recovery.img" and put it in an uncompressed "update.zip" file which I did. I copied it to the SD card and tried the flash it only to get the dreaded "E: signature verification failed" "installation aborted." message.
Here are my questions:
Is what I am trying to do even possible?
Can I flash a .img image by sticking it in an update.zip file?
Do I need to create a /dev/recovery/ structure inside the zip file?
If so, how do I fix the zip file so it doesn't fail the signature verification?
Is there a better way to do what I am trying to do?
There are all kinds of tutorials on how to use CWM to flash things from the SD card but surprisingly few that describe how to do what I am trying.
Any help or suggestions would be most appreciated. Thank you so much in advance.
Click to expand...
Click to collapse
None of this is necessary..
You can not flash a zip made by us from stock Recovery.
Your final hope is fastboot mode.
Before that, Install Minimal ADB and Fastboot in PC (Google it)
Switch off the mobile.
Hold any button combination like Power + Volume Up (or whatever, it's specific to phone) which will take you to a boot menu.
Connect phone to PC.
Select fastboot option in that menu from phone.
Now open Minimal ADB and Fastboot desktop icon and type the following:
Code:
fastboot boot recovery location_of_recovery\recovery.img
This will boot the CWM recovery.
Do whatever you want there

Thanks for your suggestion. I did start to go down that road and installed fastboot/adb. I gave up when the only key combination I could find for this stupid phone was power+volume down to boot into recovery. I will search more on whether there is a boot menu available on Boost Mobiles crappy stock ROM. Will update on what I find.
Thx again for the suggestion.

JZ_Hack_Nub said:
Thanks for your suggestion. I did start to go down that road and installed fastboot/adb. I gave up when the only key combination I could find for this stupid phone was power+volume down to boot into recovery. I will search more on whether there is a boot menu available on Boost Mobiles crappy stock ROM. Will update on what I find.
Thx again for the suggestion.
Click to expand...
Click to collapse
Inside the recovery, check if you have an option like 'bootloader' or 'fastboot' or 'debug'
If there's something like that, that's the fastboot mode.
Some phones don't have fastboot mode, so the phone might be one of those if there's nothing like that
Anyway, what data do you want to recover from the phone??

Believe it or not, I'm reading that these LG phones require a special cable from shady overseas websites to access the boot loader and flash capabilities.
Awesome...

GokulNC said:
Inside the recovery, check if you have an option like 'bootloader' or 'fastboot' or 'debug'
If there's something like that, that's the fastboot mode.
Some phones don't have fastboot mode, so the phone might be one of those if there's nothing like that
Anyway, what data do you want to recover from the phone??
Click to expand...
Click to collapse
Ya there's nothing like that unfortunately.
Mainly contacts and text messages. There's suspicions that her bf may have had something to do with her death and the police won't bother to do forensics on the phone so she asked if I could help.

I've been doing more research on this and have established that there is no way to get the LG855 (Marquee) into bootloader mode and no way to unlock the bootloader without getting past the keylock, I'm back to square one.
So my question remains, is there a way to convert a CWM recovery image (.img) file into a properly signed update.zip file that I can use the stock recovery to flash onto the phone from the SD card?
Thanks.

JZ_Hack_Nub said:
I've been doing more research on this and have established that there is no way to get the LG855 (Marquee) into bootloader mode and no way to unlock the bootloader without getting past the keylock, I'm back to square one.
So my question remains, is there a way to convert a CWM recovery image (.img) file into a properly signed update.zip file that I can use the stock recovery to flash onto the phone from the SD card?
Thanks.
Click to expand...
Click to collapse
I found this - which may help me sign the zip file.
http://forum.xda-developers.com/showthread.php?t=1966007
Still not sure if the .img file will flash properly without making changes to it. Any thoughts?

JZ_Hack_Nub said:
I found this - which may help me sign the zip file.
http://forum.xda-developers.com/showthread.php?t=1966007
Still not sure if the .img file will flash properly without making changes to it. Any thoughts?
Click to expand...
Click to collapse
You can never flash a zip file created by us from stock recovery.
You can do it from custom recovery.
However hard you try, you can never do it from stock recovery. It's waste of time

GokulNC said:
You can never flash a zip file created by us from stock recovery.
You can do it from custom recovery.
However hard you try, you can never do it from stock recovery. It's waste of time
Click to expand...
Click to collapse
Appreciated. I'm not one to give up though. I think I'll try this and let you know if it works. Thanks for all of your advice.
http://forum.xda-developers.com/showthread.php?t=732957