Related
Ok so if the answer to this question is already on this forum I searched for a hour and if you could drop me a link that would be great. Last night I flash v10k onto my LG thrill with no hiccups. The only problem is I want to go back to V20p because it changed to a O3D and all I can get is 2g edge service. So this morning I attempted to flash V20p and everything was kosher until it said there was a connection error. "Disconnect phone remove battery..." So i figured I needed to get the phone back into download mode in order to continue. The phone isnt bricked, however, I cant seem to get it back into Download mode to try again. Ive tried everything (that I can think of). Restarted my computer wipe all my phones data... My end goal is to have either v10e or the v20p. So I'm open to any routes to this end. I've read about doing a nandroid backup but all the links are dead. I've already decided I'm going to get the Galaxy Nexus and sell this phone if I can ever get it back to stock or semi stock. This is the second time I've had this connection error the first time it was during the update to GB and that time it bricked it. At the time I thought it was a faulty data cable, however, this time I was using a gold plated gigawire and it still did it... This coupled with the ghost call issue almost costing me my job(the reason for trying to go back to froyo) My experience has been buggy to say the least. Any help at all will be greatly appreciated.
PROlific666 said:
Ok so if the answer to this question is already on this forum I searched for a hour and if you could drop me a link that would be great. Last night I flash v10k onto my LG thrill with no hiccups. The only problem is I want to go back to V20p because it changed to a O3D and all I can get is 2g edge service. So this morning I attempted to flash V20p and everything was kosher until it said there was a connection error. "Disconnect phone remove battery..." So i figured I needed to get the phone back into download mode in order to continue. The phone isnt bricked, however, I cant seem to get it back into Download mode to try again. Ive tried everything (that I can think of). Restarted my computer wipe all my phones data... My end goal is to have either v10e or the v20p. So I'm open to any routes to this end. I've read about doing a nandroid backup but all the links are dead. I've already decided I'm going to get the Galaxy Nexus and sell this phone if I can ever get it back to stock or semi stock. This is the second time I've had this connection error the first time it was during the update to GB and that time it bricked it. At the time I thought it was a faulty data cable, however, this time I was using a gold plated gigawire and it still did it... This coupled with the ghost call issue almost costing me my job(the reason for trying to go back to froyo) My experience has been buggy to say the least. Any help at all will be greatly appreciated.
Click to expand...
Click to collapse
So you want V20P or V10E?
Sent from my Samsung Galaxy S II w/ DUAL BOOT: AOKP / MIUI
I really want V10e if its possible but If not then V20p will work.
I am having similar problems when I try as well. I have tried 5 or six times but tells me something about the b2c not loaded or a connection to the internet. Every time I hit "normal web upgrade test" it throws up a pop up and wont let me proceed any further. It has worked for me twice before, I got the no connection pop up and ignored it, but its not working this time. I set everything up the same from instructions on Acidhazzard rom web site. Please help...
I had to change the port back to 80 and put the orig host file back in the ect file just to download the bc2app then change it all back it worked the first time when i flashed v10k... idk i would delete the lg drivers and everything then start from scratch if i could boot into download mode.
Sent from my LG-P920 using Tapatalk 2
I have been starting...
From scratch. I download the LG flash package and go from there. It does it every time I try. The times I got it to work, I would just hit cancel or OK on the pop up and then hit the OK button I was wanting to hit real fast before the pop up could come back up. I thought it may be a Windows 7 issue (cause I have seen people talk about it) and tried win xp yesterday. Same things happened.
Im running Xp and Im having the same exact thing happen. I got it into download mode finally idk what was going on but now I just keep getting the communications error Ive tried the whole process (each one is like 5 errors) like 3 times now. If it keeps popping up before the update even starts then your probably need to change your small server port from 80 to 9002.
fixed
Somehow after getting the com error 100 times with the flash tool I noticed it had changed my model number back to P925 (I don't know how it did this) I then decided to chance it (after I changed the host file back and changed the port back to 80 and closed the small http server) I went through the LG support tool and clicked start update. After about 20 min of uncertainty during the update and another 5 minutes of self-loathing after getting a bootloop on the at&t screen... I did a hard reset and cleared all data and wah-la... I got it back to V20p. But the flash tool wouldn't flash the v20p for me.. So if I didnt somehow get rid of the P920 model number and back to the P925 model number I don't think it would have worked the way it did.
Im posting here because I am not sure this is phone specific issue, but if you guys could help me that would be great.
Long story short i screwed up my phone, cant recover with rsd so used fastboot...blah blah blah Its up and running except one thing.
WHen the phone boots I see the motorola Logo....but thats it, I hear the droid doing the weird machine startup,,,i plug the phone in to the computer and it recognizes it, i even called from another phone and it rings...
I just cant see anything it black, I also get haptic feedback on the buttons.
I fxz'd with the latest update from verizon...I boot into recovery and i see the little android man, i Islo see the white letters on bootloader, its just when the rom actually loads its a black screen?
If anybody could help i would appreciate it.
Phone is a bionic
Reinstall your android. Your os must hav corrupted. Flash it again.
i have re-installed over 20 times, i think maybe the phone is done??? i accidentally tried flashing a GB fxz before the JB one.....the phone s running but soon as the bootanimation starts for the phone i get nothing on the screen only sound.
SomebodyPleaseHelp said:
i have re-installed over 20 times, i think maybe the phone is done??? i accidentally tried flashing a GB fxz before the JB one.....the phone s running but soon as the bootanimation starts for the phone i get nothing on the screen only sound.
Click to expand...
Click to collapse
from my understanding once you go to JB there is no going back.. Were you getting any errors when you fxz? mine would get an error at step 5 and stop. their was a separate image file for that error which I used and it worked fine. It's on the page. I have bricked mine 3 or 4 times and it always came back to life. I really like this phone. wish it wasn't nearing the end of it's life for support. Times I thought mine was a gonner but it always came back. try redownloading the fxz file.
Hi to all ill jump strait in,
last night i attempted to root my phone as i have many of my other android phones in the past including a previously owned htc one however it all went pear shaped when using TWRP recovery which was a first (used to use cwm)
essentially i have wiped everything from the phone including the rom zip file i was going to install and the backup i created before doing so. i have spent about 7hours both yesterday evening and today trying to get my phone working again but because i cant find an RUU for my phone and i cant transfer a Rom to it thanks to adb not being able to see my phone i am at a loss, i have browsed my of the threads on xda to fix my adb but everything i try does not work and right now i want to cry just looking at my phone sitting infront of me unusable .
I dont have a great deal of knowledge when i comes to adb so its entirly possible that its an easy fix and im just an idiot who overlooked somthing simple.
PS soryy to create yet another thread on this topic but i am truly lost at what to do and no one elses fixes seem to work for me so this is my last resort
many thanks for any help in advance
3.04.651.2 RUU
3.05.651.5 RUU
A little searching in Sprint Android Development you would have found both
So anyone figure out why some ROMs fail to flash on to some devices?
I have a theory, I think it has something to do with "fastboot flash partition gpt_main0.bin" failing to flash on certain devices depending on which rom it's sourced from, also depending on which the device currently has already flashed successfully..
Although this is beyond my comprehension, I don't know the reasoning and or the correct wording. Perhaps someone with more knowledge could shed some insight..
I.E. I can successfully "fastboot flash partition gpt_main0.bin" on my device using MX retail, Bell and AT&T versions/copies will fail to flash on my device and I think it is because the last complete successful flash I was able to do with RSDlite was MX retail.
Anyone got any ideas?
The Atrix HD can be a pain
Hey @clockcycle does the flashing of gpt_main0.bin actually "fail" or does it freeze up? I know that you cannot flash an earlier version of "gpt_main0.bin" over a newer one. I had the same issue as you've described while manually flashing and RSD doesn't work for me anymore. It took me a month of trying different approaches to get back to stock just so I could make a nandroid because my original backup corrupted. Anyway, Myth Tools would get the furthest while flashing stock, but would freeze up. I'm assuming you've tried Myth Tools and failed. However, I discovered something (in frustration and desperation) that totally worked for me. Soft bricks don't scare me anymore so I tried the method I describe in this post
[TheJeremyWhite;49794944]Disclaimer: Even though this worked for me I am not responsible if you brick your phone, I am simply sharing my experience
Okay, this is not for the faint of heart and is going to sound a little backward but it just worked for me 5mins ago. I am running Windows 8.1 Pro 64bit, so there shouldn't be a problem with your setup. I was having the same problem until I just double clicked on flashing.bat or main.bat instead of running as admin. After all I AM the admin of my PC. Then, it worked perfect...until flashing the tz.mbn file and froze up while writing the file. I thought mmm...it shouldn't take that long to write such a small file, and writing happens on the phone side (I believe) so I hit the phone's power button while leaving the Myth Tools window open, which disconnected the phone obviously. I booted back into fastboot and it continued from where it left off. (Note: I did this a few weeks ago when I lost my radios and manually flashed the modem file, which froze, but I followed the same procedure and it successfully flashed it) Then when it got to the last system.img chunk (it writes it in small chunks of 30mb and the last one is smaller, that's how I knew it was the last one) it froze again. I let it sit for about 5mins just to make sure it was written to the phone the repeated the sequence to reboot manually into fastboot and bang, once again it continued right where it left off. one or two more freezes and voila...it rebooted right back to stock.
But honestly, I have no clue why some ROM's fail, but I now know how to flash any one of them without any issues.
TheJeremyWhite said:
Hey @clockcycle does the flashing of gpt_main0.bin actually "fail" or does it freeze up? I know that you cannot flash an earlier version of "gpt_main0.bin" over a newer one. I had the same issue as you've described while manually flashing and RSD doesn't work for me anymore. It took me a month of trying different approaches to get back to stock just so I could make a nandroid because my original backup corrupted. Anyway, Myth Tools would get the furthest while flashing stock, but would freeze up. I'm assuming you've tried Myth Tools and failed. However, I discovered something (in frustration and desperation) that totally worked for me. Soft bricks don't scare me anymore so I tried the method I describe in this post
[TheJeremyWhite;49794944]Disclaimer: Even though this worked for me I am not responsible if you brick your phone, I am simply sharing my experience
Okay, this is not for the faint of heart and is going to sound a little backward but it just worked for me 5mins ago. I am running Windows 8.1 Pro 64bit, so there shouldn't be a problem with your setup. I was having the same problem until I just double clicked on flashing.bat or main.bat instead of running as admin. After all I AM the admin of my PC. Then, it worked perfect...until flashing the tz.mbn file and froze up while writing the file. I thought mmm...it shouldn't take that long to write such a small file, and writing happens on the phone side (I believe) so I hit the phone's power button while leaving the Myth Tools window open, which disconnected the phone obviously. I booted back into fastboot and it continued from where it left off. (Note: I did this a few weeks ago when I lost my radios and manually flashed the modem file, which froze, but I followed the same procedure and it successfully flashed it) Then when it got to the last system.img chunk (it writes it in small chunks of 30mb and the last one is smaller, that's how I knew it was the last one) it froze again. I let it sit for about 5mins just to make sure it was written to the phone the repeated the sequence to reboot manually into fastboot and bang, once again it continued right where it left off. one or two more freezes and voila...it rebooted right back to stock.
But honestly, I have no clue why some ROM's fail, but I now know how to flash any one of them without any issues.
Click to expand...
Click to collapse
Fails to downgrade.
clockcycle said:
Fails to downgrade.
Click to expand...
Click to collapse
Haha, you're absolutely right. Thanks for pointing that out.
Sent from my MB886 using XDA Premium 4 mobile app
I have managed to delete the whole OS without backup and custom recovery. I also deleted the single launcher I had on my previous device. Tell me your biggest blooper you spent hours fixing.
When I was 11 yo, I saw "fastboot mode started" after a badly flashed ROM, I've decided to reflash the whole phone, which ended up in a fully bricked NAND Flash, being the partition table corrupted.
R.I.P LG-P500/h, you were a good friend.
I messed up real bad with my first Moto G. This was the time when Kikat 4.4.4 OTA came out and I should have checked the forums before updating anything(from 4.4.3 to 4.4.4) and needless to say, I had hard bricked my phone due to OTAs reacting violently with unlocked bootloaders. What's worst that my bootloader was unlocked I knew there was no way I was getting a replacement device but somehow I had fooled the warranty centre, because they couldn't boot to fastboot mode to check warranty status and in fact second they couldn't boot it at all so I got a freaking replacement device.
Sent from my XT1033 running good ol' Stock ROM
I think the worst I've done is forget to move a zip to my card before a reflash on a phone, meaning that I did a full wipe and RSD to a specific firmware then didn't have the ROM version that I needed for it. Led to yet another RSD session back to stock, getting the zip to the SD, then RSD again, then flashing the ROM.
Not too bad really, just time consuming.
My biggest mistake was buying a Samsung phone.
Trafalgar Square said:
My biggest mistake was buying an Samsung phone.
Click to expand...
Click to collapse
Yeah,i agree to that...
Trafalgar Square said:
My biggest mistake was buying a Samsung phone.
Click to expand...
Click to collapse
Don't worry. We all reach that point where we just give up on Samsung phones, because let's face it, Samsung is only worth it when you buy NOT low budget phones.
Sent from my XT1033 running good ol' Stock ROM
I told a guy I could update his rooted Kindle Fire HD. Ended up formatting the whole thing wiping the current rom, the backup and the zip I was about to flash. Tried for days and even rang in sick to work to get it working. In the end I ended up buying him a new iPad mini. Next day I sideloaded a rom on the damn thing!
Truth be told, I've still got it and it's a damn awesome little tablet.
Sent from my HTC 10 using XDA Labs
rooted my first phone the first week i got it and bricked it, panicked the whole weekend trying to fix it and thankfully fixed it by the following week
My brother Put on a tempered glass On his gionee and dropped it In the road to test it .the fall only damaged the glass and but a bike ran over it
dropped it
without unlocking bootloader properly installed random buggy ROM on Moto E and then bricked my phone.!
recovered after 1 day of internet seraching.!
Bought a cheap ass Screen Guard from a local dealer. Wanted to test it out. Dropped it from about 5 feet in air.
Goodbye Phone. Yeah it sounds noobish. But I was 12 when I did it
using it as a "personal stimulation" device on a girl. you dont wanna use that phone after that. GG
I accidentally deleted my system partition.
hehe, what a story, 4 years ago, when i was 13,5 years old. It was the first time a had an android(s7562) phone, as i had only symbian(n97) (i had some experiences with symbian as i had flashed it with JAF with some better CFWs, curruntly using a CFW made by Omar_Bazaraa).
Then i started learning android with a symbian'ish background(how to install qt? where's pips,sdl?...hhhh).
I did some foolish things, the worst thing i did is that is downgraded it to GB's cm7 (WHILE CM DOESN'T EXIST TO OUR PHONE AT ALL!, I TRIED A FOOLISH WAY TO PORT IT!).
Well, this caused it to no longer boot in recovery, so i stuck in B.L until i reflashed agin.
Thx for reading,...
Trying to unscrew a screw in order to open the phone. The screw was stucked though and I accidently destroyed the display because it was right under it.
Considering it was my first and only phone, I had to spent lots of time without an phone afterwards
Haha! Install custom Rom in my clean android
Deleted
The biggest mistake with an android phone i´ve ever made was flashing something to a device from a laptop and forgot to plug in the external power suplly. Exacly in the moment i started flashing a system img the battery from the laptop was down to 10% and it shut off itself. After that the phone was never again able to get a fastboot connection. Luckily twrp was already flashed on the device and so i could use it for more then one year xD