Hey ppl! I messed up my phone and I need some help. I have a G2x and I recently rooted it using the root.zip I found on one of the forum threads here. It worked fine and I flashed over to Eagleblood 2.5 and I didn't notice when I downloaded it that it didn't come with the google apps. I couldn't figure out how to get the google apps back into the phone since market wasn't installed. I tried downloading it but the phone kept telling me I don't have an SD Card being that I don't have an external one yet. Yes, I could have just downloaded it on pc and then transfered market apk via usb but I couldn't find the option to activate usb which was weird. Usually when you plug in your usb cable the driod icon pops up. So instead of flashing back using the backup I made on CWM I used nvflash and then used that LG tool to install V21E_00.kdz to install Gingerbread again. That's where everything messed up. I no longer was getting a cell signal and the battery icon had a ? in it. I assumed that the installation went bad to i did the process again with the nvflash and the V21E_00.kdz file. I got the same results again. I managed to get the wifi working again cause it wouldn't connect and downloaded cm7 7.1.0.1 to see if it would fix the problem. I flashed over and got the same results on cm7. No cell signal and battery icon screwed up. I gave up and did a full wipe and tried to install Gingerbread again. This time my pc wasn't reading my phone anymore when I connected it to the usb to use the LG tool to install V21E_00.kdz. Now my phone is in a cm7 boot cycle. If my phone is broken just tell me so I can dump it. My friend warned me about the G2x and I didnt listen cause I was in a hurry to get a nice phone. Any input and help would be greatly appreciated. If you guys need more info on anything please ask. If I can salvage this hunk o' junk I'm getting rid of it.
This phone is unbrickable damn near, have you tried the rom for recovery in development section? It will low level nvflash your phone to GB OTA 2.3.3 good luck.
http://forum.xda-developers.com/showthread.php?p=17258229
Sent from my LG-P999 using xda premium
Great! Thanks for the help. The phone is somewhat alive but I still have no cell signal and my battery icon has a question mark in it again. I was reading on that thread you linked me mentioning to do a firmware upgrade using the kdz file or LG Tool. Do I have to flash the firmware to get the cell signal working and the battery icon to work? If so, where do I get the firmware to flash?
To fix the boot loop cycle just boot back into clockworkmod recovery and do a factory reset, wipe cache, Dalvik cache, and then reboot and give it several minutes (first boot takes a little longer).
Or since you said you have a backup, just boot into clockworkmod, do a factory reset, format /system, and then restore your backup.
Again, the first boot always takes a little longer.
Thanks phburk I managed to get the phone working again with the flash.bat file from the link posted but I still dont have cell signal and battery icon has a question mark in it. I'm trying to download and use the LG Update Tool to see if that flashes the firmware to get the cell signal and battery icon working again.
The LG Update Tool fails at 30%. I can't get wifi on the phone to work and I have no cell signal and battery icon has a question mark still. This phone has to be broken. I see no fix in site for this problem. Anyone want to trade a GS2 for a G2x?
Kolcrok78 said:
The LG Update Tool fails at 30%. I can't get wifi on the phone to work and I have no cell signal and battery icon has a question mark still. This phone has to be broken. I see no fix in site for this problem. Anyone want to trade a GS2 for a G2x?
Click to expand...
Click to collapse
If you have a backup from a working configuration, try restoring that. Before you restore it, boot into clockworkmod and do a factory reset, and then format /system. THEN restore your backup.
After you restore allow the phone to reboot. If you still don't have signal then go to Settings > About Phone and see what it says for Baseband version.
Right now its going to show "unknown" for baseband. Might sound stupid but remove the battery sim card and sdcard for 5 minutes or so and then put them all back in and reboot. Try that after the factory wipes and installing a new rom. I've done that when I saw the "?" And no cell or data...
Sent from my LG-P999 using xda premium
I'll give it a shot. That's all I can do at the moment.
I no longer have a backup. The backup got corrupted that's why I've been trying other methods of restoring my phone. After running backup from CWM, the phone would reboot and stay on a black screen and flash. Screen would go dim then black like the backlight showing a black screen and dim again. That's all it kept doing and would not reboot. I tried doing a kdz flash but the pc wouldn't even recognize my phone when I plugged in the usb. (Yes, the drivers were installed and it was working. Previous to this I have kdz flashed twice. Phone has to be in S/W Update Mode by first pressing power button and as soon as the LG Logo shows up on the screen, let go of the power button and hold volume down.)
This resolved my reboot issue since I couldn't do a kdz flash.
http://forum.xda-developers.com/showthread.php?t=1248644
It got my phone working but still have unknown baseband and a question mark inside my battery icon.
**Update**
I read several threads regarding unknown baseband issue.
I've tried this method:
http://forum.xda-developers.com/archive/index.php/t-1332350.html
Since I already just did the first part by using the flash.bat file all I had to do was use the kdz flash. Unfortunately, my pc is still not recognizing my phone when I plug it in to the usb while in S/W Update Mode. I tried using this method above since the phone doesn't have to be in S/W Update Mode.
Outcome:
The LG Update Tool used in the method above kept stalling at 4%.
I read in another thread that this LG Update Tool doesn't work on Gingerbread. This LG Update Tool only works on Froyo.
So my next option was to use this method and try installing Froyo:
http://forum.xda-developers.com/showthread.php?t=1048274
This method just didn't work period. Since I don't have baseband or wifi working on the phone I can't get into market to download Rom Manager and I can't install File Expert which I have backed up on my pc. I already had the _ExternalSD directory so I made a sub directory /clockworkmod and another subdirectory /backup in the previous subdirectory. Made this on both the External and Internal sd cards and CWM tells me Couldn't open directory - No files found. So installing Froyo this way was out of the question.
I found this thread:
http://forum.xda-developers.com/archive/index.php/t-1037120.html
This is the stock Froyo version before the Gingerbread update as a zip file.
Unfortunately, when I tried to install the zip file from CWM it didn't work. I unzipped the zip file and found 2 .bin files which answers my question why CWM didn't install the zip.
I tried this method as well:
http://forum.xda-developers.com/archive/index.php/t-1332350.html
This method involves the flash.bat file to be done as a prerequisite before flashing to kdz. To my understanding, the flash.bat file fixes the partitions that most likely were screwed up on the phone and the kdz flash fixes the baseband (update/repair). I still haven't been able to get that kdz flash v1e to work simply because my pc won't recognize my phone into the usb when its in S/W Update Mode. I'm leaning towards the LG Update Tool to fix my baseband but I just need to downgrade to Froyo.
Don't know what else to do. I've been at it for 2 days and I'm seriously going to give up and just cancel T-Mobile.
If one of the methods involves installing apps, u can use adb to install them from ur computer without having to copy them to ur phone. But that's if u can get it into usb debugging mode.
Sent from my LG-P999 using XDA App
When you installed the rom, there should've been an extra package for Google apps that you should have flashed along with the rom as well, but you did so many different things, I don't know what to say.
You don't need your backup, it won't fix your baseband if it's corrupted or at all because no one has been able to get this phone to independently flash a baseband and the only way is through running the Gingerbread update either with KDZ or the LG updater.
I also went through hell more than once when I bricked my phone a few times. The first time I spent almost 2 weeks at it until I fixed it with the help of others here.
I also had the KDZ update stop at 4% over and over again which drove me crazy with anxiety. I was desperate so, after a few of those 4% hangups, I decided to reinstall a ROM and kernel just to see if the phone's baseband had installed anyway. Well, what a surprise, it did work.
You should try KDZ update again and, when it stalls at 4%, leave it for about 20 minutes then install a ROM based on Android 2.3.3, such as Weapon 3, fix permissions then reboot. That's what worked for me once. Another time, I did the same but I installed MTK drivers first then ran KDZ which stopped at 4% too but it worked too.
Read post #20 in this thread about how someone else did that successfully: http://forum.xda-developers.com/showthread.php?t=1180177
Here's where the MTK driver is: http://www.4shared.com/file/EqniU1Xt/MCCI_r_Firmware_Update_Driver_.html
Kolcrok78 said:
I'll give it a shot. That's all I can do at the moment.
I no longer have a backup. The backup got corrupted that's why I've been trying other methods of restoring my phone. After running backup from CWM, the phone would reboot and stay on a black screen and flash. Screen would go dim then black like the backlight showing a black screen and dim again. That's all it kept doing and would not reboot. I tried doing a kdz flash but the pc wouldn't even recognize my phone when I plugged in the usb. (Yes, the drivers were installed and it was working. Previous to this I have kdz flashed twice. Phone has to be in S/W Update Mode by first pressing power button and as soon as the LG Logo shows up on the screen, let go of the power button and hold volume down.)
This resolved my reboot issue since I couldn't do a kdz flash.
http://forum.xda-developers.com/showthread.php?t=1248644
It got my phone working but still have unknown baseband and a question mark inside my battery icon.
**Update**
I read several threads regarding unknown baseband issue.
I've tried this method:
http://forum.xda-developers.com/archive/index.php/t-1332350.html
Since I already just did the first part by using the flash.bat file all I had to do was use the kdz flash. Unfortunately, my pc is still not recognizing my phone when I plug it in to the usb while in S/W Update Mode. I tried using this method above since the phone doesn't have to be in S/W Update Mode.
Outcome:
The LG Update Tool used in the method above kept stalling at 4%.
I read in another thread that this LG Update Tool doesn't work on Gingerbread. This LG Update Tool only works on Froyo.
So my next option was to use this method and try installing Froyo:
http://forum.xda-developers.com/showthread.php?t=1048274
This method just didn't work period. Since I don't have baseband or wifi working on the phone I can't get into market to download Rom Manager and I can't install File Expert which I have backed up on my pc. I already had the _ExternalSD directory so I made a sub directory /clockworkmod and another subdirectory /backup in the previous subdirectory. Made this on both the External and Internal sd cards and CWM tells me Couldn't open directory - No files found. So installing Froyo this way was out of the question.
I found this thread:
http://forum.xda-developers.com/archive/index.php/t-1037120.html
This is the stock Froyo version before the Gingerbread update as a zip file.
Unfortunately, when I tried to install the zip file from CWM it didn't work. I unzipped the zip file and found 2 .bin files which answers my question why CWM didn't install the zip.
I tried this method as well:
http://forum.xda-developers.com/archive/index.php/t-1332350.html
This method involves the flash.bat file to be done as a prerequisite before flashing to kdz. To my understanding, the flash.bat file fixes the partitions that most likely were screwed up on the phone and the kdz flash fixes the baseband (update/repair). I still haven't been able to get that kdz flash v1e to work simply because my pc won't recognize my phone into the usb when its in S/W Update Mode. I'm leaning towards the LG Update Tool to fix my baseband but I just need to downgrade to Froyo.
Don't know what else to do. I've been at it for 2 days and I'm seriously going to give up and just cancel T-Mobile.
Click to expand...
Click to collapse
Related
Ok so I have been trying to unroot my G2x to acquire the new OTA update and I followed everyone's unrooting instructions perfectly, but what keeps happening is I try and hold down volume and power to access recovery mode and the first thing to happen is it does not show that little Android text like normal before you can access recovery, but instead shows the LG symbol with a blue striped bar which disappears after a few seconds and then displays an Android character and a box with an arrow with an arrow coming out of it and a status bar, then it flashes the LG symbol again without the blue bar and it just restarts the phone with all my data wiped and starts over fresh from the "Welcome to LG-P999 Touch the Android to Begin." But preserves the root and mod.
All that aside I tried accessing the recovery through rom manager which worked but every single time I try and restore the stock rom it tells me I have an md5 mismatch despite every attempt I've made to fix the md5 problem (Changing folder names/following internet help guides.) nothing seems to work. Please help me
umbral said:
Ok so I have been trying to unroot my G2x to acquire the new OTA update and I followed everyone's unrooting instructions perfectly, but what keeps happening is I try and hold down volume and power to access recovery mode and the first thing to happen is it does not show that little Android text like normal before you can access recovery, but instead shows the LG symbol with a blue striped bar which disappears after a few seconds and then displays an Android character and a box with an arrow with an arrow coming out of it and a status bar, then it flashes the LG symbol again without the blue bar and it just restarts the phone with all my data wiped and starts over fresh from the "Welcome to LG-P999 Touch the Android to Begin." But preserves the root and mod.
All that aside I tried accessing the recovery through rom manager which worked but every single time I try and restore the stock rom it tells me I have an md5 mismatch despite every attempt I've made to fix the md5 problem (Changing folder names/following internet help guides.) nothing seems to work. Please help me
Click to expand...
Click to collapse
You're trying to unroot to get the OTA update? Are you on stock 2.2? If you are then you shouldn't need to unroot.
I'm on CM7 nightly with 2.3.3 but I would prefer the more official update plus I need to send my phone into t-mobile.
Can someone plz help.
umbral said:
I'm on CM7 nightly with 2.3.3 but I would prefer the more official update plus I need to send my phone into t-mobile.
Can someone plz help.
Click to expand...
Click to collapse
I found this video helpful. I know you said you looked for help/info and probably saw this already, but I thought I would throw it out there anyway.
http://www.youtube.com/watch?v=ryGIv8KQVIE
umbral said:
I'm on CM7 nightly with 2.3.3 but I would prefer the more official update plus I need to send my phone into t-mobile.
Can someone plz help.
Click to expand...
Click to collapse
I'm helping, don't worry lol. I just needed more info. (Oh and CM7 is 2.3.4 by the way.) But anyways you said you can get into clockworkmod recovery right? Download this file from TGA_Gunnman: http://www.multiupload.com/RNN8X15ETU
Extract it using 7zip or winrar so that you have a folder called LG-P999-v10f with system.img, boot.img, etc. directly inside it
Plug your phone into your computer and mount USB mass storage, then go to the clockworkmod folder then the backup folder
Move the LG-P999-v10f folder into the backup folder on your sdcard, so now it should be (from the root of your sdcard) clockworkmod->backup->LG-P999-v10f->system.img,boot.img,etc.
Now reboot into clockworkmod recovery and restore the LG-P999-v10f backup!
Thanks for advice I did that but whenever I hit restore it says checking md5 sums then it says "md5 mismatch" and the phone stays in the menu unless i restart it and when it reboots I still have the rom.
umbral said:
Thanks for advice I did that but whenever I hit restore it says checking md5 sums then it says "md5 mismatch" and the phone stays in the menu unless i restart it and when it reboots I still have the rom.
Click to expand...
Click to collapse
You have to delete the backup that's on your sdcard right now, download from the link I posted above, and copy it over. MD5 mismatch means that the checksum file in the backup doesn't match the images. You either have a bad download or something went wrong when you copied the files over. Just try again with a new download.
Ok cool so ur saying I need to delete the clockworkmod backups and transfer the new one over?
umbral said:
Ok cool so ur saying I need to delete the clockworkmod backups and transfer the new one over?
Click to expand...
Click to collapse
Yes. Download the backup from the link I posted and transfer that over and don't change any of the files around or anything like that.
Damn I did everything but now I have a new problem now my rom manager wont take me to recovery just starts the android guy and the tmobile jingle and the volume down and power option factory resets my phone every time. Any ideas?
EDIT: Ok I had to flash it for my phone then it worked but the MD5 mismatch is still showing up
umbral said:
Damn I did everything but now I have a new problem now my rom manager wont take me to recovery just starts the android guy and the tmobile jingle and the volume down and power option factory resets my phone every time. Any ideas?
EDIT: Ok I had to flash it for my phone then it worked but the MD5 mismatch is still showing up
Click to expand...
Click to collapse
Mount your phone as USB mass storage again and make sure the image files aren't 0 bytes. It could be your SD card, your computer not copying the files over right, or it could be clockworkmod recovery. You may want to try the nvflash version of clockworkmod recovery.
Ok im confused though do I store it to the SD card or the internal memory? Cause all the clockworkmod backups are internal.
I used the LG Update tool on a rooted G2x that had a NVFlashed CWM running a GB leak. It worked flawlessly.
I did have to NVFlash again to get CWM again and flash a rooted ROM over it.
If you are just opposed to using the Update tool, then go through the pain of unrooting and waiting, but personally, I didn't have the patience.
Tried that the updater says my phone cannot connect to it despite the first screen saying it is connected. Oh well I guess im screwed.
Thanks for the help guys imma try more stuff then give up cause ive been trying to figure this out forever.
I need some help to unbrick my Rogers branded O3D P925g. I was able to root it and manually install the camera mod from erosized. Then i tried manually installing the performance pack and when i rebooted its looping at the Rogers screen. Can i use the unbrick method from the p920? Thanks again.
Sent from my LG-P920 using XDA App
I had mine bricked as well and this method worked great for getting it back.
Step 1: Get the newest KDZ file for your phone/carrier. I got mine from here:
http://csmg.lgmobile.com:9002/csmg/b2c/client/auth_model_check2.jsp?esn=xxxxxxx
Where xxxx is enter the IMEI of your phone which is found under the battery.
Step 2: follow the instructions here:
http://forum.xda-developers.com/showthread.php?t=1186406\
This will bring it back from pretty much any state. Mine was not even booting up to the LG Logo and this restored it.
Good Luck.
Just fixed mine. Use LG Update Tool, Click on Customer Support and then Recovery Phone. Enter your IMEI number and it will completely wipe the phone contents and install the newly released v20c BB and software. This process took me about 20 minutes and then an additional 10 min or so to boot into the OS. Worked flawlessly with my SIM and microSD still in the phone. Didn't loose any data from my microSD either. Got 4G back as well. Note that rooted state will be removed and CWM Recovery will be replaced with Android Recovery.
Same Problem no resolution
I have the same phone and when I use those links I cannot get anything to show up no matter how i enter the information.
My phone is stuck on the lg screen and it wont boot up. could someone give me a link to LG P925G stock firmware or some method of unbricking my phone. i have't had much luck.
all because I used Rom Manager too.
I cannot even go into recovery mode is my phone totaly bricked? I need some tips.
how to unbrick
largo79 said:
I need some help to unbrick my Rogers branded O3D P925g. I was able to root it and manually install the camera mod from erosized. Then i tried manually installing the performance pack and when i rebooted its looping at the Rogers screen. Can i use the unbrick method from the p920? Thanks again.
Sent from my LG-P920 using XDA App
Click to expand...
Click to collapse
here is the most easy and straight-forward way I discovered to unbrick or overcome any flashing error no matter what it is (it applies to lg o3d, and thrill 4G, I think it will apply to their fellows)
1-you must have drivers installed of-course
2-remove your battery
2-open your pc device manager and look at COM and PORT section
3-hold volume up button (only) and connect your mobile to pc through USB while pressing this button, and keep pressing until you see a new port has been added and installed in your COM and PORT section (about 15-20 sec), now you can release the button, be sure that port will stay apparent after releasing the button, or repeat this step (with longer press on volume up button)
4-put your battery back and don't touch your phone again
5-now start flashing by following these 2 tutorials in order:
a-http://forum.xda-developers.com/showthread.php?t=1473781
b-http://forum.xda-developers.com/showthread.php?t=1327929
after finishing reboot and enjoy
I got in a SK4g for my wife intent on upgrading her current phone. I own a 4g myself, and have Rooted/ROM'd it with no issues, we we thought it best to get her the same phone for ease of use/manipulation.
I got the phone in and used superoneclick to root it, then went through the process of putting CWM in place and installing GenericGinger_2.0_SK4G. The process ran smooth as glass (as expected) until it got to reboot. On reboot it hung up on the sidekick screen. After about an hour of waiting I pulled the battery and restarted the machine.
It came back up in recovery mode with the stock recovery (blue) text. Since then I haven't been able to get it to do anything but restart into that recovery screen. Odin doesn't see the phone in download mode and t839-Sidekick4G-UVKG2-One-Click does nothing. It shows it uploading, reboots the phone, and I'm back at the blue text. flashing the bootloaders with One-Click shows success on everything *except* uploading the bootloaders. If I tell it to re-install packages I get a 'cannot validate signature' response. I've tried using android commander to push CWM's recovery file to the phone and get 'permission' denied.
I've done a lot of searching on this site, trying most suggested fixes I've come across with no luck.
what can be done with this phone to get it back in operating condition?
Thanks in advance!
try installing kies odin wouldnt see my phone until i installed it
Kies installed and Odin saw the phone. excellent, thanks!
now, the next issue... lol
I used Odin to push KD1OdinSTOCK onto the phone. it's doing more than it was (going to the initial sidekick screen then dumping to recovery). Now it'll load through the sidekick and samsung splash screens, then reset and do it again. The same thing happens when I tried StockKG2ODIN. I'm using the sk4g.pit that I pulled from this site, could that have anything to do with it/is there another one around that I could try? Anybody have thoughts or ideas on what to do next? I've tried using t839-Sidekick4G-UVKG2-One-Click again, but it nuked the drivers kies put into place and dropped the phone back to what it was doing before.
okay, I did some light reading of this thread here
and followed the directions closely. I also went through sduvick's list of things to do with the following results:
Black screen, no logo.
1. Get into download mode by using VolDown+Touchpad+Power
2. flash full sk4g.tar.md5 as posted.
device will boot through the logo and splash screens, then repeat. note: if I leave the USB cable plugged in on reboot it will go to the battery screen, otherwise it just boot loops.
_________________________________
logo only
1. Download mode
2. Flash full package
device boot loops
_________________________________
Can't flash recovery/boot/sbl
1. Download mode
2. use PIT only, run with repartition checked
3. reboot/reDownload mode
4. run the full image in Odin.
PIT only returns a black screen on the device. running the full image in afterward returns to the boot loop.
_________________________________
Anything else
1. Download mode
2. Full tar.md5 flash in Odin
3. Ask if it doesn't work
okay, so I'm asking...
I'm still able to boot into recovery mode (blue text).
I've noted a bit of strange behavior when trying to boot into download mode. holding vol down + trackball + power does nothing. however, if I plug the phone in while powered down while holding down the trackball it'll boot into download mode, no power or vol down required.
If you can't flash with Odin, you may have a hardware problem.
Judging from your issue with installing Kies, you had a driver problem previously.
Seems that you are bumbling in the dark here. Once again, people need to be better prepared to Odin their devices before they start modding them.
In fact, getting Odin working should be the first thing a person should do with their phone after rooting and installing CWM.
Anyhow, try a different version of Odin. If that doesn't clear up your problem, I suspect some bad blocks in your flash memory are responsible here. It's a dorment issue that would really only be a problem when you flashed the device. If that's the case, you have a new paperweight.
Good luck.
i never could get kd1 to work try kg2
use pit check repartion and place tar file in pda
I don't think the problem is that I can't flash with Odin, but that the device isn't loading the ROM that's flashed. poking around in the filestructure with android commander after a fresh load shows that the system makes it onto the phone.
Speaking of poking around with Android Commander, I've noted that the device is software rooted, but not hardware rooted. the default.class file shows ro.debuggable set at 0 where it should be 1. this is keeping me from just pushing the CWM recovery onto the system and restoring the backup I made before getting into this mess. Anybody want to help me pull/edit/flash the image to change that?
As for a driver issue, that's a good possibility given that the one-click uses a driver set, kies mini uses another, kies has a different one yet and we (as a community) started screwing with the t839's using vibrant drivers. I've got them all. thusfar the only drivers I've found that work with both flavors of Odin I have (1.61 and 1.85) would be those that came with the Kies (thanks for the tip pmp326).
On bumbling in the dark, yes, yes I am. There isn't much of an instruction manual for Odin past what's written here, and 90% of that is 'put your phone in download mode, connect Odin, plug the pit in pit and the tar in PDA make sure only auto-reboot is checked and hit start'. to be honest I haven't had to use the program previously as the stock one-click actually worked on my T839. This new device is being ... difficult.
the dormant bad blocks issue you spoke about, was this something found in new-out-the-box phones? I haven't seen a lot about that in the threads, can you point in at more info, please?
at any rate, it doesn't matter which version of Odin I use, I got the same result from both. I tried using a different cable/different USB port as well. I haven't tried using a different system (yet), but don't want to go through all the trouble of setting up everything on another box. Win7 is finicky enough, trying to get everything operating on Server2k3 would most likely end up a challenge. *lol*
I'll try repartitioning with KG1 when I get back to the house.
Sounds like you are getting far enough to get your device working again to me.
If you can manage to get access to the file system with adb or Android Commander, you may be able to push the rest of the OS files you need directly. This may provide a way to get around your flashing problems.
Try adding the missing files directly with Android Commander.
also i had some troubles a while back while in recovery wipe data and cache turn off phone pull sd card then flash with odin
orange808 said:
Sounds like you are getting far enough to get your device working again to me.
If you can manage to get access to the file system with adb or Android Commander, you may be able to push the rest of the OS files you need directly. This may provide a way to get around your flashing problems.
Try adding the missing files directly with Android Commander.
Click to expand...
Click to collapse
I've gotta pop the debug lock in the default.class to be able to push anything into the system folders with Android Commander. I've found a nice walk-thru to do this, it just requires a little knowledge of c++ and some patience. with any luck I should be able to pull default.class out of its img, edit it and flash that back (most likely with Heimdall since it can do itemized flashing).
pmp326 said:
i never could get kd1 to work try kg2
use pit check repartion and place tar file in pda
Click to expand...
Click to collapse
tried it, no joy.
pmp326 said:
also i had some troubles a while back while in recovery wipe data and cache turn off phone pull sd card then flash with odin
Click to expand...
Click to collapse
tried this, brings me back to the boot loop.
orange808 said:
Sounds like you are getting far enough to get your device working again to me.
If you can manage to get access to the file system with adb or Android Commander, you may be able to push the rest of the OS files you need directly. This may provide a way to get around your flashing problems.
Try adding the missing files directly with Android Commander.
Click to expand...
Click to collapse
currently I'm running into issues with getting ADB to push onto the system as the system is claiming it isn't rooted. Is there a way I haven't read about or found to root the phone without getting into the actual O/S (i.e. from the blue recovery screen)?
If you can get in to CWM Recovery you are fine.
If you cannot, just ODIN to stock.
If you cannot do that, or it doesn't boot after that, try a different PC, os, or drivers (x86 os is usually easier then an x64 os).
If it is still no good, buy a new phone on ebay .
Once booted, Root and install CWM first thing.
Once you are in CWM Recovery...
1) Check mounts (everything should be mounted, and therefore read "unmount [...]")
2) Format EVERYTHING one at a time: cache, data, system, sdcard (optional).
(sdcard should be fine, but to be sure you can format it too after backing it up to PC first and restore what you need after)
(you probably don't need to Wipe and Wipe-Dalvik as they should already be gone, but go ahead and do it anyway)
3) Check mounts again!
4) Install a ROM (must reload it to your sdcard first if you formatted your sdcard)
5) Check mounts one final time before rebooting.
That should ALWAYS work.
NOTE: This was said before: "2. flash full sk4g.tar.md5 as posted.", but that doesn't seem right... you should not be flashing a .md5 file... you need to flash the .tar... the .tar.md5 is just a checksum. (right?)
rpmccormick said:
If you can get in to CWM Recovery you are fine.
If you cannot, just ODIN to stock.
If you cannot do that, or it doesn't boot after that, try a different PC, os, or drivers (x86 os is usually easier then an x64 os).
If it is still no good, buy a new phone on ebay .
Once booted, Root and install CWM first thing.
Once you are in CWM Recovery...
1) Check mounts (everything should be mounted, and therefore read "unmount [...]")
2) Format EVERYTHING one at a time: cache, data, system, sdcard (optional).
(sdcard should be fine, but to be sure you can format it too after backing it up to PC first and restore what you need after)
(you probably don't need to Wipe and Wipe-Dalvik as they should already be gone, but go ahead and do it anyway)
3) Check mounts again!
4) Install a ROM (must reload it to your sdcard first if you formatted your sdcard)
5) Check mounts one final time before rebooting.
That should ALWAYS work.
NOTE: This was said before: "2. flash full sk4g.tar.md5 as posted.", but that doesn't seem right... you should not be flashing a .md5 file... you need to flash the .tar... the .tar.md5 is just a checksum. (right?)
Click to expand...
Click to collapse
Wow... did you even *read* before posting? fail. I mean, thanks for taking the time to write that up and all, but you just repeated everything already said up to this point and included a summary of the ROM for n00bs thread.
Artemis257 said:
Wow... did you even *read* before posting? fail. I mean, thanks for taking the time to write that up and all, but you just repeated everything already said up to this point and included a summary of the ROM for n00bs thread.
Click to expand...
Click to collapse
I like turtles.
Artemis257 said:
Wow... did you even *read* before posting? fail. I mean, thanks for taking the time to write that up and all, but you just repeated everything already said up to this point and included a summary of the ROM for n00bs thread.
Click to expand...
Click to collapse
Even the end... I mean, your not trying to odin a "tar.md5" are you?
rpmccormick said:
Even the end... I mean, your not trying to odin a "tar.md5" are you?
Click to expand...
Click to collapse
No....
Sorry man. I've never had to ODIN (this phone). I say check the md5 to make sure you downloaded a good copy, and maybe try a different USB cable. The ADB method seems nutz... if it doesn't boot after a successful ODIN, the phone is probably a paperweight.
Good luck!
Hey Guys,
So I have been all threw the forum over the past week plus trying to find a solutions and have tried the majority of the ones on the site. Here is what happend:
HOW I GOT HERE:
I was running a CM10 nightly build from 01/15/2013 that was installed via CWM. I had been running it for about a week. When I went to bed I set my phone on the nightstand. About 2 hours into sleep the phone rebooted as I eventually woke up and noticed it thinking it was just the phone wonking out. When I up fully 6 hours later the phone was still rebooting. Since then when ever I cut on the phone it will no get passed the Google logo with the padlock. I can boot into fastboot and recovery. I am running the latest CWM 6.0.2.5.
PHONE VITALS QUICK GLANCE
Android ROM version: CM10 01/15/2013 Nightly Build
Baseband: D720SPRLC1
Bootloader: D720SPRKC5
Recovery: CWM v6.0.2.5
WHAT I HAVE TRIED
Restoring from backup
My first fix was to flash three different roms via recovery (doing full wipes each time)
Then I tried flashing a new recovery
Formatting /system, /cache, /data, and /boot and then flashing a new rom
Then I focused on trying to get the USB storage to mount so I tried using adb shell to repair the file system and that worked
Then I tried new roms and things got REALLY weird. When I would place a rom on “sdcard” it would be available to flash. When I flashed it though it would not take and upon returning to recovery it wouldn’t be there or when I mounted the storage again. After about 10 times of this I figured let me make sure I am not crazy and try the following.
Format the internal storage. In windows when I tried this windows would show that the device formatted and was empty one I dismounted after putting items on it and go back to storage by both remounting it or by recovery the old data would come right back. In Ubuntu when I tried formatting it both via disc recovery and gparted they both said the device was empty but that they were unable to create a partition.
So then I went down the path of all of the debricking tools out there including the one from AdamOutler's (I think it is called ressurector), ODIN, and the Nexus Root Tool all with varying results.
Ressurector kept saying injection failed
ODIN just does not work on the nexus s from what I can tell (spent a day researching and no one seems to give a definitive answer on this one)
And Nexus Root Tool attempts to flash back to stock but runs into an error with the baseband.
So next I decided to try and flash back to stock using the Google images. Using Ubuntu I ran the flash-all.sh that comes in the zip and kept running into the baseband issue.
So next I found OldBlue910’s post with all the OTA updates and I went after trying to use that to fix my phone. Thanks to the amount of instruction he gives I got a lot further and got the flash-all.sh in his stock zip to give me a better error message telling me which baseband I needed to have to go back to stock which when I double checked he includes in the zip. The problem is when I try to flash that radio fastboot tells me I was successful but the bootloader still reads as D720SPRLC1 and does not change regardless of what I do. When I try flashing the stock images again after flashing the radio I receive the same errors.
So now I think I have hit the real brick wall and unless someone has any advice I will need to go and buy a new phone. Hoping you guys can help. I figured if you guys can figure out a hard brick then this is still doable, I have just exhausted my own realm of knowledge.
Please and thank you’s to anyone with advice.
Could you get any lights ON? The buttons or the screen?
lights are on
Yes during the boot loop the Google logo comes up, then the screen goes black, then the Google logo comes back, and finally in about 20 seconds the lights come on. Once that happens after about 4 minutes the process starts all over again.
I have spent all day pretty much trying to figure this out. I cannot flash ANYTHING. NO KDZ no DZ nothing. I have tried LGUP and LG Flash Tool 2014 and LG FLashTool. Everytime, whichever tool i try it seems to get stuck at 9%. I have tried 3 different PC's at work, windows 10 and windows 7. I have rebooted and reinstalled drivers and i have cleared registries left right and centre. Nothing will flash. Phone enters DL mode then sits there at 0% doing nothing while LGUP or Flash Tool sit there at 9% doing nothing.
I have seen a couple of users on the forum with the exact same problem and it appears to be a result of us flashing this http://forum.xda-developers.com/g-flex2/development/dec-21-stock-lollipop-flex-2-ls996-t3275531 which has somehow broken our download mode??
Does anyone have any ideas how i can restore my phone to stock. Or just flash 6.01 which was my original aim.
Thanks in advance. I'm losing my hair here....
Did you tried to restore stock system.img with http://forum.xda-developers.com/g-flex2/development/root-easy-root-att-flex-2-5-1-1-t3178354 ?
Thanks, I did try that method as well but the phone is still on rooted 15c. Did it twice. But it doesn't seem to be sticking.
Do you have free space on internal storage? Do you have system.img on your internal storage? Delete it and try then. I would recommend to you using official LG mobile support app and select emergency recovery or something like that in top-right list corner. Before you plug in phone into usb, turn it off and hold volume up button and connect it to pc simultaneously, your phone will go into download mode.
i did it!!
i stayed late at work last night and through a combination of flashing different KDZ's and system IMG's over and over again using various methods and it apparently failing each time..... I ended up flashing a KZ of the MM KDZ that i made using Windows LG Firmware Extract software. Flashed it using LG Flash Tool 1.4 and it worked. The last thing i did before that was flash the system IMG i got from the 'LGUP stuck at 9%' thread. I 'flashed' it using EasyRoot.
I can't put my finger on what worked. But my advice to anyone else having the same issues are to keep trying thanks for your advice everyone.
beardyone said:
i did it!!
i stayed late at work last night and through a combination of flashing different KDZ's and system IMG's over and over again using various methods and it apparently failing each time..... I ended up flashing a KZ of the MM KDZ that i made using Windows LG Firmware Extract software. Flashed it using LG Flash Tool 1.4 and it worked. The last thing i did before that was flash the system IMG i got from the 'LGUP stuck at 9%' thread. I 'flashed' it using EasyRoot.
I can't put my finger on what worked. But my advice to anyone else having the same issues are to keep trying thanks for your advice everyone.
Click to expand...
Click to collapse
I'm also having the same problem with flashmods .... can you exactly describe how to upgrade? I'm working on it now for hours but don't get it to work!
Please help!
Finaly fixed it!
Download the system.img from here: http://forum.xda-developers.com/g-flex2/general/lgup-stuck-9-t3401416/page2 (Post #15)
Place it on internal Storage.
Then start adb shell on PC - then type su and then: dd if=/data/media/0/system.img bs=8192 seek=53248 count=458752 of=/dev/block/mmcblk0
Just wait until the Phone turns off.
Now you should be able to upgrade to MM!