So I have bricked my phone for the 3rd time, the last 2 times I had to have someone with an authorized account fix it for me cost was 30EUR. Sucks. I have read every post on here and was just going to toss this thing in the trash after flashing and bricking it last night. This morning I came across a thread claiming if you used the SP Flash Tool with some other files that it would work, it didn't for me but in the process I found another thread talking about holding the volume down key while flashing, it did work. Here are the steps and how did I brick it, I flashed the files from MEGATHREAD so preloader was in place, I had working and install TWRP and was in the process of flashing vendor and PE ROM from TWRP. The zip was corrupted and it wiped me out and before rebooting I got the No OS installed message but figured I would to a clean flash of the OEM image from fastboot. Nope it failed and I got the LED light with nothing else, no boot no fastboot and no recovery. Dead. Here is what I did someone please try this.
I am on a Ubuntu box with ADB and Fastboot installed for the system I assume Windows or MAC would work just have those tools working and installed you must or you wouldn't have bricked your phone. I have begonia_global_images_V11.0.6.0.PGGMIXM_20200108.0000.00_9.0_global ROM and I went to the image directory, and typed:
Code:
fastboot devices
fastboot flash boot boot.img
When it was listed in fastboot devices I was like WHAT??? Sure enough it flashed it but do this right before you issue that command ITS IMPORTANT plug in the phone via USB and hold down the volume down key the phone will within a few seconds vibrate then hit the commands. Please see attached image you can see what I did. After that when I unplugged the phone it freaking booted into the OS and I had to set my phone up again but for the most part and this is weird my data was still intact, I don't care but it was nice. I really don't understand this phone at all but I hope others will try this and unbrick it would be awesome.
DC
dcindallas said:
So I have bricked my phone for the 3rd time, the last 2 times I had to have someone with an authorized account fix it for me cost was 30EUR. Sucks. I have read every post on here and was just going to toss this thing in the trash after flashing and bricking it last night. This morning I came across a thread claiming if you used the SP Flash Tool with some other files that it would work, it didn't for me but in the process I found another thread talking about holding the volume down key while flashing, it did work. Here are the steps and how did I brick it, I flashed the files from MEGATHREAD so preloader was in place, I had working and install TWRP and was in the process of flashing vendor and PE ROM from TWRP. The zip was corrupted and it wiped me out and before rebooting I got the No OS installed message but figured I would to a clean flash of the OEM image from fastboot. Nope it failed and I got the LED light with nothing else, no boot no fastboot and no recovery. Dead. Here is what I did someone please try this.
I am on a Ubuntu box with ADB and Fastboot installed for the system I assume Windows or MAC would work just have those tools working and installed you must or you wouldn't have bricked your phone. I have begonia_global_images_V11.0.6.0.PGGMIXM_20200108.0000.00_9.0_global ROM and I went to the image directory, and typed:
When it was listed in fastboot devices I was like WHAT??? Sure enough it flashed it but do this right before you issue that command ITS IMPORTANT plug in the phone via USB and hold down the volume down key the phone will within a few seconds vibrate then hit the commands. Please see attached image you can see what I did. After that when I unplugged the phone it freaking booted into the OS and I had to set my phone up again but for the most part and this is weird my data was still intact, I don't care but it was nice. I really don't understand this phone at all but I hope others will try this and unbrick it would be awesome.
DC
Click to expand...
Click to collapse
Thanks for sharing this. I've had a bricked rn8 pro for 3 weeks now and none of the other fixes worked for me. I'm looking forward to giving this a try when I get home from work. Perhaps I should've tried using my Kali box rather than windoze in my previous attempts.
I'll update with results if interested.
Hi, what exactly you did? Because I'm tired to test any possible method, I've tried disconnecting the battery, Press Volume - while try to flash, and now I'm waiting to prove the method that drain the battery adn then can connect and flash.
Did you flash with Ubuntu? It works? How can you do it If the phone can't enter to fastboot mode?
To what I understood you unlocked it 3 times and in one of those you updated the preloader?
Because if so. spflash unlocks it without asking for the happy account
Yup on Arch Linux and this worked fine
Melon_Bread said:
Yup on Arch Linux and this worked fine
Click to expand...
Click to collapse
What you did? Pls help ):
GERATKDASD said:
What you did? Pls help ):
Click to expand...
Click to collapse
Made sure the device was off completely, held down VOL-DOWN while pluging in phone and had it show up in my fastboot devices. Reflashed the system via fastboot with the begonia_global_images_V11.0.2.0.PGGMIXM_20191201.0000.00_9.0_global system image (flash-all.sh)
Melon_Bread said:
Made sure the device was off completely, held down VOL-DOWN while pluging in phone and had it show up in my fastboot devices. Reflashed the system via fastboot with the begonia_global_images_V11.0.2.0.PGGMIXM_20191201.0000.00_9.0_global system image (flash-all.sh)
Click to expand...
Click to collapse
I will try, thanks
Still not working ): IDK if I don't doing it right, I don't know, I'm tired of this phone ):
GERATKDASD said:
Hi, what exactly you did? Because I'm tired to test any possible method, I've tried disconnecting the battery, Press Volume - while try to flash, and now I'm waiting to prove the method that drain the battery adn then can connect and flash.
Did you flash with Ubuntu? It works? How can you do it If the phone can't enter to fastboot mode?
Click to expand...
Click to collapse
I already tested battery draining, doesnt worked :/
KonahZave said:
I already tested battery draining, doesnt worked :/
Click to expand...
Click to collapse
Holy cow, and then? now who can help us? ): I don't have 30 bucks right now ._.
Sed lyf
GERATKDASD said:
Holy cow, and then? now who can help us? ): I don't have 30 bucks right now ._.
Click to expand...
Click to collapse
I know how bad it is... Im sorry bro, if this guide couldnt help... then only paying. (╯︵╰,)
KonahZave said:
I know how bad it is... Im sorry bro, if this guide couldnt help... then only paying. (╯︵╰,)
Click to expand...
Click to collapse
You guys are NOT reading the method used, the battery isnt even removable on this phone follow the steps listed. You can't see anything happening on your phone just be at a terminal window HOLDING down the volume down key and type (oone handed or whatever) fastboot devices) it works I did it 3 times. Flash the boot.img and it will reboot and be fixed. I am tellng you FOLLOW instructions so many of you don't.
pablo159 said:
To what I understood you unlocked it 3 times and in one of those you updated the preloader?
Because if so. spflash unlocks it without asking for the happy account
Click to expand...
Click to collapse
None of that matters and no the preloader was over written, the point here is it was hard bricked only got the white LED light, then I did exactly what I wrote and it saw the phone in fastboot and it wrote the boot.img and then it rebooted and worked. Period. Worked for me. Someone else tested it worked for them. Try it but follow the directions....
dcindallas said:
You guys are NOT reading the method used, the battery isnt even removable on this phone follow the steps listed. You can't see anything happening on your phone just be at a terminal window HOLDING down the volume down key and type (oone handed or whatever) fastboot devices) it works I did it 3 times. Flash the boot.img and it will reboot and be fixed. I am tellng you FOLLOW instructions so many of you don't.
Click to expand...
Click to collapse
Man, Im not trying this method or such thing, Im not bricked. Im just telling for the dude my old experience with old guides.
dcindallas said:
You guys are NOT reading the method used, the battery isnt even removable on this phone follow the steps listed. You can't see anything happening on your phone just be at a terminal window HOLDING down the volume down key and type (oone handed or whatever) fastboot devices) it works I did it 3 times. Flash the boot.img and it will reboot and be fixed. I am tellng you FOLLOW instructions so many of you don't.
Click to expand...
Click to collapse
Sorry If I look like an annoying guy that don't understant, but litteraly i've tried that, I opened a Terminal window, typed fastboot devices, holding down volume -, but, IDK, how many time I need to press it;
I need to connect phone before hold the button, or vice versa?
GERATKDASD said:
Sorry If I look like an annoying guy that don't understant, but litteraly i've tried that, I opened a Terminal window, typed fastboot devices, holding down volume -, but, IDK, how many time I need to press it;
I need to connect phone before hold the button, or vice versa?
Click to expand...
Click to collapse
Plug the phone in and hold it down the phone will vibrate keep holding it down and try flashing it continue to hold it down until the flash is successful. All I had to do was flash the boot image but others have flashed_all. Hit me on telegram if you need help @dcindallas
dcindallas said:
Plug the phone in and hold it down the phone will vibrate keep holding it down and try flashing it continue to hold it down until the flash is successful. All I had to do was flash the boot image but others have flashed_all. Hit me on telegram if you need help @dcindallas
Click to expand...
Click to collapse
Ok, so, you only need to installed adb and fastboot right? no drivers or other things?
Related
NOTE: THIS ISSUE HAS BEEN FIXED, See this post #97 by "teppic74" for how I fixed the phone
My flatmate recently got a Desire from Vodafone, it's got their latest ROM on it with all their bloatware.
I told him I could debrand it, but the goldcard method didn't work because he had bootloader 0.83.
So I followed a thread to this site on how to downgrade the bootloader:
http://www.tolxdorff.net/tutorials/?step=2
So I did step 4... and then the screen went blank. I left it for a while, I thought it may be installing...
After a long time, I pulled the battery out and rebooted the phone ... I'm pretty nervous by this point LOL
Anyway, the phone reboots and I can hear the annoying HTC chime, which never happened on the Voda rom...
But I can't see anything. It appears that the phone is booting up, but the screen is not working.
Anyone got any advice on what I might do to fix this or am I toast? Grateful for any advice.
Have you try it again or download a original rom (maybe on vodafone...on my o2site it give a original rom and also here on xda)...or have you tried unrevoked...what say the h boot now..?????
with kind regards...Alex
Unforunately that's the problem... the phone is working and booting up, but the screen is blank... so I can't see anything.
I'll try to find and flash the voda rom, that's a good idea
mmm_ok said:
Unforunately that's the problem... the phone is working and booting up, but the screen is blank... so I can't see anything.
I'll try to find and flash the voda rom, that's a good idea
Click to expand...
Click to collapse
so you cant even get into recovery?
mmm_ok said:
Unforunately that's the problem... the phone is working and booting up, but the screen is blank... so I can't see anything.
I'll try to find and flash the voda rom, that's a good idea
Click to expand...
Click to collapse
you have no acsess to bootloader or recovery.....??
try vol down (hold it) and phone on (power)...
Well... I think I can get into recovery... it's just I can't tell because the screen is not showing anything...
if I was to make a noob guess at what's wrong, and this is unsubstantiated, it's that it's a new desire with SLCD screen and that it's get the driver for the AMOLED screen installed when I downgraded...
Two more people over at modaco at reporting the same issue, I think:
http://android.modaco.com/content/h...o-com/315329/ive-bricked-my-flatmates-desire/
http://android.modaco.com/content/htc-desire-desire-modaco-com/315332/borked-recovery-image/
Test your theory.
Pull out the battery and put it back in.
Press and hold volume down and birefly press power on.
Keep volume down pressed for 5 seconds, then release it.
Count 20 seconds, then press the power key briefly once more.
You should now be in fastboot.
Connect your phone to the USB port and it should list it self when you execute fastboot devices.
If see it listed, you can restore the original ROM via the vodafone RUU file.
mmm_ok said:
Well... I think I can get into recovery... it's just I can't tell because the screen is not showing anything...
if I was to make a noob guess at what's wrong, and this is unsubstantiated, it's that it's a new desire with SLCD screen and that it's get the driver for the AMOLED screen installed when I downgraded...
Click to expand...
Click to collapse
have you try phone on...wait 3-5 min and flash the original rom....or maybe a original ota with h boot 092...maybe windows recognizes the phone
georgemv said:
Test your theory.
Pull out the battery and put it back in.
Press and hold volume down and birefly press power on.
Keep volume down pressed for 5 seconds, then release it.
Count 20 seconds, then press the power key briefly once more.
You should now be in fastboot.
Connect your phone to the USB port and it should list it self when you execute fastboot devices.
If see it listed, you can restore the original ROM via the vodafone RUU file.
Click to expand...
Click to collapse
not bad...that is what i think too
edit: but better explained
mmm_ok said:
Two more people over at modaco at reporting the same issue, I think:
Click to expand...
Click to collapse
Correct that's me.
I tried a normal boot, unrevoked found the phone but got stuck waiting for boot loader.
I did follow the test you mentioned regarding fastboot.
Windows did make a bleep bleep sound when i plugged it in, but when I ran adb devices (is that what you meant when you asked "is it listed"?), there were no devices listed.
The phone does make the annoying htc sound on normal boot... just no screen
mmm_ok said:
I did follow the test you mentioned regarding fastboot.
Windows did make a bleep bleep sound when i plugged it in, but when I ran adb devices (is that what you meant when you asked "is it listed"?), there were no devices listed.
The phone does make the annoying htc sound on normal boot... just no screen
Click to expand...
Click to collapse
nothing in the list also not unknown...?
Alex-V said:
have you try phone on...wait 3-5 min and flash the original rom....or maybe a original ota with h boot 092...maybe windows recognizes the phone
Click to expand...
Click to collapse
Thanks I did try to flash an original ROM... but I get the same problem I had before when running the RUU (error 140)
If I find a .92 ROM, i'm not sure I can install it without seeing what's on the screen though...
Alex-V said:
nothing in the list also not unknown...?
Click to expand...
Click to collapse
Nah, it just says "List of devices attached" and then nothing
mmm_ok said:
I did follow the test you mentioned regarding fastboot.
Windows did make a bleep bleep sound when i plugged it in, but when I ran adb devices (is that what you meant when you asked "is it listed"?), there were no devices listed.
The phone does make the annoying htc sound on normal boot... just no screen
Click to expand...
Click to collapse
ADB will not find your phone in fastboot. You need to download fastboot binary and run fastboot devices to list devices in fastboot mode. If you use windows, you also need to install the fastboot windows driver. (I think you can find that in the android SDK)
I no longer even get the startup beep. Think I am totally screwed?
georgemv said:
ADB will not find your phone in fastboot. You need to download fastboot binary and run fastboot devices to list devices in fastboot mode. If you use windows, you also need to install the fastboot windows driver. (I think you can find that in the android SDK)
Click to expand...
Click to collapse
Thanks for your help. I'm working on it. Get back to ya soon.
SavageCore said:
I no longer even get the startup beep. Think I am totally screwed?
Click to expand...
Click to collapse
I'm getting the bleep bleep cause I tried to install the generic rom... you're probably not getting it because you only tried to root the existing rom, is that correct?
yeah i used this driver...open attached htm file (if you have download unrevoke...its also in) adb
I downloaded the Jedi Mind Trick JB 2 ROM and installed it via clocwork mod recovery .. That went fine but it took me a few days to realize I didnt have a working video camera anymore on my phone.. so I thought to flash a stock ROOTed rom instead...
Then I found this threat about an updated version of Jedi Mind Trick's ROM labled JB 3.. So I wiped as much as I could in recovery and chose to format all the options it gave me in recover , Format system , data , cache , emms(or something) .. and now when I boot the phone , it shows the first flash screen , and the samsung logo starts to shimmer then it reboots back to the splash screen and repeats this process everal times before just going black and sitting there..
So I've successfully bootlooped my phone doing this..
MY PROBLEM -- I don't know how to charge my phone or connect to it to install anything else..
Is this a serious problem? How can I charge my phone to continue troubleshooting it? It still has some battery to try some things but I don't know how to hook it up to transfer any other roms to it via USB cable and PC in it's current state..
I'm very computer savvy but I'm trying to learn this phone modding stuff and I realy hope I didn't brick my phone in this process.
Can someone please help me out here? I'll be on the forums religiously until I figure this out.
What should I start doing first??
Any help would be greatly appreciated!! Thanks!
still working at it
I think I'm at the point of having to use ODIN to flash a new rom since i cannot simply copy this rom to the sdcard to use clockwork to flash it .. Am I correct on this ?
For some reason this rom I found (should be stock rooted tmobile gSII rom) does not want to open from ODIN's PDA button cause its in .zip and not .tar or anything... I'm not sure how to flash this rom with ODIN ( I'm not even 100% sure this is how its supposed to go) Any suggestions ?
phew
UPDATE - So I managed to research enough to find out that there is no way to flash a CUSTOM rom with ODIN.. SO I had to download a stock (presumably rooted) t-mobile rom and flash THAT ...
Now I'm back up with a rooted rom and will begin re-installing clockwork and then my custom deodexed rooted rom afterward.
Thanks for all who almost kinda tried to care to reply in this past 2 hours =) -- As previously mentioned.. I am a nerd.. I just suck at phone modding. Haha
So , looks like I'm in the clear now and don't need any more support on this particular topic yet.
zarklon said:
UPDATE - So I managed to research enough to find out that there is no way to flash a CUSTOM rom with ODIN.. SO I had to download a stock (presumably rooted) t-mobile rom and flash THAT ...
Now I'm back up with a rooted rom and will begin re-installing clockwork and then my custom deodexed rooted rom afterward.
Thanks for all who almost kinda tried to care to reply in this past 2 hours =) -- As previously mentioned.. I am a nerd.. I just suck at phone modding. Haha
So , looks like I'm in the clear now and don't need any more support on this particular topic yet.
Click to expand...
Click to collapse
Is this true? Through a recommendation (haven't done anything to my phone from rooting/flashing KANGSJUGGERNAUT2 years ago), I tried to flash CM10 and ended up with a bootloop myself. Tried flashing through ODIN but it kept crashing; does anyone know why?
Afterward, I tried to reflash it through CWM and from then on bootloops into a installation process that never completes.
For some reason my CWM turned super slow, freezes/hangs and reboots after a few minutes.
I gave the phone to a friend who does this stuff on the regular but he said my initial flash wasn't complete cause in download mode says I'm still running official? No clue.
I was told this via email/chat: "No luck, it won't even boot anymore, I think I'll just bring it back tmrw morn
10:43 PM
Sorry I'm at a wedding (yea I know random) I left my phone with coat check
OK I've narrowed down the reason but not the solution, you had an AOKP based ROM which fundamentally is based on CyanogenMod, but it wasn't correctly flashed as the phone still thought it has factory ROMs still running
11:10 PM
Clockworkmod(even though it was working before) wasn't accessing the partitions of the phone correctly so it wasn't properly wiping or flashing properly.
11:12 PM
So basically from the first time you flashed cwm it didn't flash properly then the next time you flashed using the new recovery it didn't flash anything it was supposed to do itself properly , so basically it was a chain of events in addition to a bad boot loader, that's why it never went to recovery or download mode correctly
11:13 PM
That's something that had to do with the way the phone was built meaning you may of had a bad bootloader from the very begin and are now feeling the synptoms
Basically, and I would hate to be the reason or partially the reason you have a dead phone, basically it was a matter of coincedencr that it happened as this could of happened at anytime, once you have a bad boot loader its pretty much down hill from there"
Any helpful insight as how I can rectify this? is my phone truly dead? Sorry about the quoted format, it was copied and pasted.
If I were in your boat, I'd use Odin and flash the stock 4.1.2 ROM.
Sent from my Nexus 7 using Tapatalk 4 Beta
tronmech said:
If I were in your boat, I'd use Odin and flash the stock 4.1.2 ROM.
Sent from my Nexus 7 using Tapatalk 4 Beta
Click to expand...
Click to collapse
The phone won't turn on, unable to go into recovery and download mode; plugged in usb (hear connection beep but pressing power button plays disconnect button) to no avail. What can I do to unbrick?
Stock 4.1.2? Possible over a hardbricked T989 with old 2.3.6?
JahJahLoO said:
The phone won't turn on, unable to go into recovery and download mode; plugged in usb (hear connection beep but pressing power button plays disconnect button) to no avail. What can I do to unbrick?
Stock 4.1.2? Possible over a hardbricked T989 with old 2.3.6?
Click to expand...
Click to collapse
sorry but i have to assume that you are not doing the 3 button recovery or download mode right.
Pull battery, put battery back in, hold power button & Vol +/- untill you see SAMSUNG on the screen ---> let go off power button(keep holding
Vol +/- button) .....u will see recovery. (assuming you did flash cwm before).
Let me know.
hit thanks.
sam.balia1012 said:
sorry but i have to assume that you are not doing the 3 button recovery or download mode right.
Pull battery, put battery back in, hold power button & Vol +/- untill you see SAMSUNG on the screen ---> let go off power button(keep holding
Vol +/- button) .....u will see recovery. (assuming you did flash cwm before).
Let me know.
hit thanks.
Click to expand...
Click to collapse
I believe I am doing it correct, I have been entering recovery and download mode many times, right before I soft bricked it.
And sorry, no, I've tried many times, many methods and my phone is confirmed as entirely hard bricked.
SUPAR SAD, but thank you!
dont give up
JahJahLoO said:
I believe I am doing it correct, I have been entering recovery and download mode many times, right before I soft bricked it.
And sorry, no, I've tried many times, many methods and my phone is confirmed as entirely hard bricked.
SUPAR SAD, but thank you!
Click to expand...
Click to collapse
you can try using adb and put the phone in dl mode.
sometimes its as easy as pull battery and wait awhile (20 min or more) and try again.
if you've exhausted all possibilities, you can use a jig to force a dl mode.
let me know
sam.balia1012 said:
you can try using adb and put the phone in dl mode.
sometimes its as easy as pull battery and wait awhile (20 min or more) and try again.
if you've exhausted all possibilities, you can use a jig to force a dl mode.
let me know
Click to expand...
Click to collapse
I don't know what adb is, or how to use it; I have, however seen my friend RDP to my desktop and do something and used the term 'adb' in his attempt to code through the phone.
I've done that battery waiting period, for nearly an hour and still no result.
After doing some researching, I have found that many people have stated a USB JIG would not be applicable to a 'hard bricked' phone. I really wanted to try as it looked like the most, simple and inexpensive solution.
JahJahLoO said:
I don't know what adb is, or how to use it; I have, however seen my friend RDP to my desktop and do something and used the term 'adb' in his attempt to code through the phone.
I've done that battery waiting period, for nearly an hour and still no result.
After doing some researching, I have found that many people have stated a USB JIG would not be applicable to a 'hard bricked' phone. I really wanted to try as it looked like the most, simple and inexpensive solution.
Click to expand...
Click to collapse
If you know for a fact that you bricked your s2, maybe wrong rom or kernel that u flashed by accident then.....
contact these guys.... http://brickedmyphone.com/contact-me/
good like and click thanks if you agree.
sam.balia1012 said:
If you know for a fact that you bricked your s2, maybe wrong rom or kernel that u flashed by accident then.....
contact these guys.... http://brickedmyphone.com/contact-me/
good like and click thanks if you agree.
Click to expand...
Click to collapse
Lols, you're really fishing for them "Thanks"; you got it buddy. Very swift responses. :cyclops:
Anyway, I'm still searching the net for anymore possible solutions.
Thanks.
JahJahLoO said:
Lols, you're really fishing for them "Thanks"; you got it buddy. Very swift responses. :cyclops:
Anyway, I'm still searching the net for anymore possible solutions.
Thanks.
Click to expand...
Click to collapse
fishing for them ???????
what the hell does that even mean? it seems that brick did hit u in the head!!!
sam.balia1012 said:
fishing for them ???????
what the hell does that even mean? it seems that brick did hit u in the head!!!
Click to expand...
Click to collapse
It might as well have... :crying:
I have spent the last 3 days searching XDA & trying every possible fix, no luck!
Here's my dilemma.....
I have custom recovery, TWRP 2.6.3.3, don't know what I did after trying to flash something........ I wiped everything except SDcard by accident. Like a darn fool, forgot after backing up everything via computer, to put a spares on my SDcard. Sooooo, I tried restoring by using LG FlashTool..... Here's where my problems began:
1. I can't load into download mode, it sticks at the logo to enter download mode but doesn't connect.
2. I tried ADB Sideload, sticks at "STARTING ADB SIDELOAD FEATURE.........."
3. No matter what mode (including Fastboot) I try, just won't connect to my computer the way I need it to. (*ALL DRIVERS HAVE BEEN REINSTALLED NUMEROUS TIMES, STILL NO LUCK.*) When I look in DEVICE MANAGER, it shows in "OTHER DEVICES" as "LG-LS980" (*Which is a good thing right? *)
At this point i'm at my wits end...... I tried to HARD FACTORY RESET, but didn't go thru. I'm afraid that if I tried it again, I could cause even more damage.
I've been without my phone for days & I'm about to go crazy if I have to pay LG or Sprint again for another phone!!!! I'd rather use my $600 on something else.
PLEASE TELL ME SOMEONE HAS FOUND A WAY TO GET AROUND THIS!
I've searched just about every forum & tried different methods.
Forgot to add that every time I power off from recovery, I get a the message about my device not being rooted, would I like to install..... When I swipe to install, nothing happens. Just powers off.
MsOhSoPhresh said:
I have spent the last 3 days searching XDA & trying every possible fix, no luck!
Here's my dilemma.....
I have custom recovery, TWRP 2.6.3.3, don't know what I did after trying to flash something........ I wiped everything except SDcard by accident. Like a darn fool, forgot after backing up everything via computer, to put a spares on my SDcard. Sooooo, I tried restoring by using LG FlashTool..... Here's where my problems began:
1. I can't load into download mode, it sticks at the logo to enter download mode but doesn't connect.
2. I tried ADB Sideload, sticks at "STARTING ADB SIDELOAD FEATURE.........."
3. No matter what mode (including Fastboot) I try, just won't connect to my computer the way I need it to. (*ALL DRIVERS HAVE BEEN REINSTALLED NUMEROUS TIMES, STILL NO LUCK.*) When I look in DEVICE MANAGER, it shows in "OTHER DEVICES" as "LG-LS980" (*Which is a good thing right? *)
At this point i'm at my wits end...... I tried to HARD FACTORY RESET, but didn't go thru. I'm afraid that if I tried it again, I could cause even more damage.
I've been without my phone for days & I'm about to go crazy if I have to pay LG or Sprint again for another phone!!!! I'd rather use my $600 on something else.
PLEASE TELL ME SOMEONE HAS FOUND A WAY TO GET AROUND THIS!
I've searched just about every forum & tried different methods.
Click to expand...
Click to collapse
So try this...
Push the power button to turn the device on. Let it sit.
After you know that the g2 is on and trying to do its think, Press and hold power buttton, do not let go. It will force turn off the phone, but it will start to turn back on, if you keep holding the power button till it shuts off for the second time, you'll be set and the device will be fully off.
Have Lg Flash Tool open, make sure you have manual mode on and you point to the right dll and right tot file, could be zv7 zv8 or zva.
Click the arrow to have the flash tool biin check the files. when that is ready, do this next part fast. Plug in your phone, and immeditaly press and hold Volume up and Power. Download mode should appear.
and you should be good from there! If you try to enter download mode by using volume and up without the cable plug in, you'll hit the factory reset menu which is tied to the recovery, it'll do nothing, only take you to recovery. I hope this is of some help!
Edit:try new boot loader or system flasher via twrp
proplem i faced is one button which used to enter recovery is damged
Flash stock Ignoring the unmonted ianot able to be mounted then change system partitions u will be able to mount
Enjoy
bmxerkid954 said:
So try this...
Push the power button to turn the device on. Let it sit.
After you know that the g2 is on and trying to do its think, Press and hold power buttton, do not let go. It will force turn off the phone, but it will start to turn back on, if you keep holding the power button till it shuts off for the second time, you'll be set and the device will be fully off.
Have Lg Flash Tool open, make sure you have manual mode on and you point to the right dll and right tot file, could be zv7 zv8 or zva.
Click the arrow to have the flash tool biin check the files. when that is ready, do this next part fast. Plug in your phone, and immeditaly press and hold Volume up and Power. Download mode should appear.
and you should be good from there! If you try to enter download mode by using volume and up without the cable plug in, you'll hit the factory reset menu which is tied to the recovery, it'll do nothing, only take you to recovery. I hope this is of some help!
Click to expand...
Click to collapse
This isn't working. I've tried this numerous times..... No luck.
myaservip said:
Edit:try new boot loader or system flasher via twrp
proplem i faced is one button which used to enter recovery is damged
Flash stock Ignoring the unmonted ianot able to be mounted then change system partitions u will be able to mount
Enjoy
Click to expand...
Click to collapse
I'm now completely lost.....
Ok... So i made a little progress....
I am now able to boot into fastboot mode.... No recovery now tho. If someone can help me with manually pushing everything I need to restore my phone, it would make my day!
I'm having withdrawal symptoms now. LOL! I MISS MY PHONE!
Problem solved!
Flashed all the partitions 1by1 via fastboot, was able to then reboot into download mode. Now using LG FlashTool to return to stock! I am now a very happy camper after a week w/o my phone!
MsOhSoPhresh said:
This isn't working. I've tried this numerous times..... No luck.
Click to expand...
Click to collapse
MsOhSoPhresh said:
I am now able to boot into fastboot mode.... No recovery now tho. If someone can help me with manually pushing everything I need to restore my phone, it would make my day!
I'm having withdrawal symptoms now. LOL! I MISS MY PHONE!
Click to expand...
Click to collapse
MsOhSoPhresh said:
Flashed all the partitions 1by1 via fastboot, was able to then reboot into download mode. Now using LG FlashTool to return to stock! I am now a very happy camper after a week w/o my phone!
Click to expand...
Click to collapse
Glad to see you've fixed your problem! I myself haven't been around, had some down time to. My sim reader magically stopped working and then randomly started working days later. Anyway, congrats!!!
MsOhSoPhresh said:
Flashed all the partitions 1by1 via fastboot, was able to then reboot into download mode. Now using LG FlashTool to return to stock! I am now a very happy camper after a week w/o my phone!
Click to expand...
Click to collapse
Glad you figured it out. I was about to basically explain the steps to do exactly what you did.
Welcome back to the land of the living!
agentfusion said:
Glad you figured it out. I was about to basically explain the steps to do exactly what you did.
Welcome back to the land of the living!
Click to expand...
Click to collapse
After she got it the first time, which we both congratulated her for, something went completely wrong. She dug herself even deeper, but broke download mode. That was extremely fun to fix.
I have an issue that I hope someone can help me with, my daughters Moto G6 Play (Completely stock, 15months old) has just started boot looping from a black screen to Moto blue screen only.
I can move it to boot up screen using (Power and Volume Down) key but it will only stay there a few seconds before it then loops again.
I have tried "Recovery Mode" / "Power off" and they just do the same thing go into loop again.
I thought it was a battery issue, but I think this is a knock on affect of the phone boot looping so much. Also in boot up screen it was stating the battery was NOK
Took it apart and ordered new battery and installed but still the same issue.
Now before this second battery runs out as it wont charge while in this state, I wondered if anyone can help me resurrect it??
I will add its been a few years since I have flashed phones with dev roms etc (HTC One X days...) but I dont think I have even enabled USB debugging in the menu options..
Thanks in advance
Andy
Perchy35 said:
I have an issue that I hope someone can help me with, my daughters Moto G6 Play (Completely stock, 15months old) has just started boot looping from a black screen to Moto blue screen only.
I can move it to boot up screen using (Power and Volume Down) key but it will only stay there a few seconds before it then loops again.
I have tried "Recovery Mode" / "Power off" and they just do the same thing go into loop again.
I thought it was a battery issue, but I think this is a knock on affect of the phone boot looping so much. Also in boot up screen it was stating the battery was NOK
Took it apart and ordered new battery and installed but still the same issue.
Now before this second battery runs out as it wont charge while in this state, I wondered if anyone can help me resurrect it??
I will add its been a few years since I have flashed phones with dev roms etc (HTC One X days...) but I dont think I have even enabled USB debugging in the menu options..
Thanks in advance
Andy
Click to expand...
Click to collapse
Just use my guide, at the bottom of it it has everything you need to reflash stock firmware hold the power and volume down button until you get to the fastboot/ bootloader screen, also since you replaced the battery and did your own repair we still might not be able to help you because there's to many variables of user interference now, and yes Google kind of has made it a bit more complicated to root devices now unfortunately
Thanks for the reply, please can you put a link to your guide?
Perchy35 said:
Thanks for the reply, please can you put a link to your guide?
Click to expand...
Click to collapse
https://forum.xda-developers.com/g6-play/how-to/guide-t3929928
Thanks one last question before I attempt to go ahead, is it possible to "Catch" the phone between boot looping to reflash stock image?
As at the moment there is as I have stated 1/2secs between the boot screen and then it moving to "Moto" screen and then around to black screen again.
Perchy35 said:
Thanks one last question before I attempt to go ahead, is it possible to "Catch" the phone between boot looping to reflash stock image?
As at the moment there is as I have stated 1/2secs between the boot screen and then it moving to "Moto" screen and then around to black screen again.
Click to expand...
Click to collapse
Yes. Hold power and volume down, it'll look a few times and catch, you'll see fastboot. The Android guy and red and white text. May take a few loops
sorry one more thing, how do I find out the image version I need as I was unable to get this from phone before it starting acting up!?
Perchy35 said:
sorry one more thing, how do I find out the image version I need as I was unable to get this from phone before it starting acting up!?
Click to expand...
Click to collapse
Whats the carrier?
The phone was bought direct from Amazon so in my mind a generic model to take any SIM.
Perchy35 said:
The phone was bought direct from Amazon so in my mind a generic model to take any SIM.
Click to expand...
Click to collapse
Here you go. Amazon Jeter Firmware. That's the main folder.
I see there is the latest Android 8 and also an Android 9 version? This was never rolled out though... I will probably just put the following
XT1922-9_JETER_AMZ_8.0.0_OPPS27.91-140-6_cid18_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Perchy35 said:
The phone was bought direct from Amazon so in my mind a generic model to take any SIM.
Click to expand...
Click to collapse
Spaceminer is correct, once you catch that sweet spot with the phone to get it in bootloader/fastboot mode just flash the firmware and you should hopefully be good to go, if you want it rooted my guide covers that to but let's just get you a working phone first before you try to root lol
---------- Post added at 05:56 PM ---------- Previous post was at 05:55 PM ----------
Perchy35 said:
I see there is the latest Android 8 and also an Android 9 version? This was never rolled out though... I will probably just put the following
XT1922-9_JETER_AMZ_8.0.0_OPPS27.91-140-6_cid18_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Click to expand...
Click to collapse
You can either flash 8 or 9, what I would do is flash 8 then update it to 9 then if you want it rooted root it
Perchy35 said:
I see there is the latest Android 8 and also an Android 9 version? This was never rolled out though... I will probably just put the following
XT1922-9_JETER_AMZ_8.0.0_OPPS27.91-140-6_cid18_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Click to expand...
Click to collapse
Hey so out of curiosity did you get it fixed and working?
ninjakira said:
Hey so out of curiosity did you get it fixed and working?
Click to expand...
Click to collapse
Thanks for getting back to me!
I have just started yesterday getting my laptop ready, downloading image file, setting up "minimal adb" and getting motorola ID sorted.
Also can I check that without USB debugging selected this method will override and flash still?
Perchy35 said:
Thanks for getting back to me!
I have just started yesterday getting my laptop ready, downloading image file, setting up "minimal adb" and getting motorola ID sorted.
I am having issue with the last part, getting "The credentials you provided cannot be determined to be authentic" ?
Also can I check that without USB debugging selected this method will override and flash still?
Click to expand...
Click to collapse
Wait what are you needing your Moto id for? The links for the stock firmware are in my guide, just follow the bottom section of it
Oh ok in the guide it states its needed for Windows user, Excerpt below:
Motorola bootloader unlock request here https://motorola-global-portal.custh...-your-device-a
ok just started the process, I cant get past first command at the moment "fastboot oem fb_mode_set" and this is returning "waiting for any device".
I have tried toggling into the boot screen and selecting "Restart bootloader"..
Perchy35 said:
Oh ok in the guide it states its needed for Windows user, Excerpt below:
Motorola bootloader unlock request here https://motorola-global-portal.custh...-your-device-a
Click to expand...
Click to collapse
If you don't have the bootloader unlocked then that is something you can do if you want the phone rooted if not you don't have to unlock the bootloader to flash stock firmware
Perchy35 said:
ok just started the process, I cant get past first command at the moment "fastboot oem fb_mode_set" and this is returning "waiting for any device".
I have tried toggling into the boot screen and selecting "Restart bootloader"..
Click to expand...
Click to collapse
You either didn't install adb minimal or you have a bad cord, type fastboot devices and if nothing pops up saying you have a device in fastboot then it's one of the 2 things I said, extract the contents from the rar or zip file you got from adb minimal download, then install what you extracted
I have installed the adb minimal 1.4.3 (Latest), just tried three different leads with the command fastboot devices and it returns nothing and jumps back to command line when you first start adb minimal for the first time.
I have tried this whilst forcing it to boot screen (power/volume down), same issue.
Perchy35 said:
I have installed the adb minimal 1.4.3 (Latest), just tried three different leads with the command fastboot devices and it returns nothing and jumps back to command line when you first start adb minimal for the first time.
I have tried this whilst forcing it to boot screen (power/volume down), same issue.
Click to expand...
Click to collapse
Sorry been at work and I'm ona break, I totally forgot though you can use Moto smart Assistant for pc to fix this more than likely, so download and useMoto smart Assistant
Hi,
I followed this guide on how to root the pixel 2: "androidcentral.com/how-root-google-pixel-2" and finished all the steps. But when running step 11 it got stuck in a boot loop due to some software issues with the patched image I assume.
I've tried opening the phone in fastboot mode and then connecting with ADB, but it seems I cannot find my device since USB-debugging is not turned on.
Any ideas of how this can be solved? Or am I screwed?
Try rebooting into recovery. When you see the Android laying down and I believe it says no command, press the up button. This should bring you to another menu where ADB sideload is an option. you could then download the appropriate OTA from Google and sideload it to the phone.
Larzzzz82 said:
Try rebooting into recovery. When you see the Android laying down and I believe it says no command, press the up button. This should bring you to another menu where ADB sideload is an option. you could then download the appropriate OTA from Google and sideload it to the phone.
Click to expand...
Click to collapse
Thanks for your reply. I pressed "On/off" button + volume down and got into menu with recovery mode. But selecting recovery mode with "on/off" button and then clicking volume up just brings me to a view with the google logo showing and then the phone turns off. I can't seem to access menu with ADB sideload unfortunately...
helpless_user said:
Thanks for your reply. I pressed "On/off" button + volume down and got into menu with recovery mode. But selecting recovery mode with "on/off" button and then clicking volume up just brings me to a view with the google logo showing and then the phone turns off. I can't seem to access menu with ADB sideload unfortunately...
Click to expand...
Click to collapse
when in Bootloader mode (where it shows your "baseband version" and such), you actually use the volume button to change around the different options to boot, and then the "on/off" button to select.
But it looks like you get it to show the red "recovery mode" and, I imagine, you intuitively pressed the "on/off button" to select it, but in the unlikelihood that that is the case, make sure you are not holding or pressing or "....clicking volume up" button while it's booting; that's probably where you're going wrong....
only once you're in the stock recovery mode -- with the android lying down, dead, and a red exclamation point coming out of it -- is where you press the "volume up" and power button together to see the options...
good luck and hope this helps....
simplepinoi177 said:
when in Bootloader mode (where it shows your "baseband version" and such), you actually use the volume button to change around the different options to boot, and then the "on/off" button to select.
But it looks like you get it to show the red "recovery mode" and, I imagine, you intuitively pressed the "on/off button" to select it, but in the unlikelihood that that is the case, make sure you are not holding or pressing or "....clicking volume up" button while it's booting; that's probably where you're going wrong....
only once you're in the stock recovery mode -- with the android lying down, dead, and a red exclamation point coming out of it -- is where you press the "volume up" and power button together to see the options...
good luck and hope this helps....
Click to expand...
Click to collapse
I tried this and I never get to the dead android screen. I just get to a screen that says that my bootloader is unlocked and then the Google logo is showing.
helpless_user said:
I tried this and I never get to the dead android screen. I just get to a screen that says that my bootloader is unlocked and then the Google logo is showing.
Click to expand...
Click to collapse
Hmmmm...it sounds like something's wrong with your boot partition, then -- that's where the recovery resides. I suggest re-downloading the latest Full Factory image (from Google's developers site), editing flash-all to remove the "-w" and "exit" at the end, then running the flash-all once again on your device.
....after reading your OP, one key thing to keep in mind is that, in Bootloader Mode, you use "fastboot" commands while you use "adb" commands when within the OS or recovery....
And, for future reference, it would be better (most likely) if you wish to root the taimen for you to follow THIS GUIDE: https://forum.xda-developers.com/pixel-2-xl/how-to/guide-unlock-flash-root-pixel-2-xl-t3702418 .
helpless_user said:
Thanks for your reply. I pressed "On/off" button + volume down and got into menu with recovery mode. But selecting recovery mode with "on/off" button and then clicking volume up just brings me to a view with the google logo showing and then the phone turns off. I can't seem to access menu with ADB sideload unfortunately...
Click to expand...
Click to collapse
In fastboot you can boot to a recovery.img; fastboot boot twrp.img
Download TWRP .img here.
(that recovery menu allows adb mode also).
Here you can(re)flash zip/image etc.
Format /data to ensure it is not encrypted.
For example, flash the extracted images of the OTA images from Google.
simplepinoi177 said:
Hmmmm...it sounds like something's wrong with your boot partition, then -- that's where the recovery resides. I suggest re-downloading the latest Full Factory image (from Google's developers site), editing flash-all to remove the "-w" and "exit" at the end, then running the flash-all once again on your device.
....after reading your OP, one key thing to keep in mind is that, in Bootloader Mode, you use "fastboot" commands while you use "adb" commands when within the OS or recovery....
And, for future reference, it would be better (most likely) if you wish to root the taimen for you to follow THIS GUIDE: https://forum.xda-developers.com/pixel-2-xl/how-to/guide-unlock-flash-root-pixel-2-xl-t3702418 .
Click to expand...
Click to collapse
Thank you very much!! Running fastboot helped me do a factory reset and now my phone is working again! Thought my phone was bricked so this is a relief.
helpless_user said:
Thank you very much!! Running fastboot helped me do a factory reset and now my phone is working again! Thought my phone was bricked so this is a relief.
Click to expand...
Click to collapse
I'm real happy you got it back up and running!
Yeah, I'm not agreeing with all of what Google's doing now (in concerns with the Pixel 4 [i.e. removing unlimited original quality storage]), but they really did well with the whole "Bootloader Mode" where you can feel a bit more secure and confident that, as long as you have access to Bootloader Mode and can successfully connect your device, you're not too far gone and definitely bricked beyond hope! It's not so hopeless as with devices before and what the term "bricking" truly applies to....
Happy to have helped!
Not able to figure out the exact fix
helpless_user said:
Thank you very much!! Running fastboot helped me do a factory reset and now my phone is working again! Thought my phone was bricked so this is a relief.
Click to expand...
Click to collapse
@OP, I am still stuck with the exact same issue. How did you exactly fix it? After running the solution given, I'm back at the infinite logo screen again.
Edit: It worked, thank you so much! This is a life saver.
simplepinoi177 said:
I'm real happy you got it back up and running!
Yeah, I'm not agreeing with all of what Google's doing now (in concerns with the Pixel 4 [i.e. removing unlimited original quality storage]), but they really did well with the whole "Bootloader Mode" where you can feel a bit more secure and confident that, as long as you have access to Bootloader Mode and can successfully connect your device, you're not too far gone and definitely bricked beyond hope! It's not so hopeless as with devices before and what the term "bricking" truly applies to....
Happy to have helped!
Click to expand...
Click to collapse
Hi i have the same issue with different device lenovo tab m10 tbx605L and i cant boot the recovery.img it throws me this error.Can u give me any ideas?
helpless_user said:
Hi,
I followed this guide on how to root the pixel 2: "androidcentral.com/how-root-google-pixel-2" and finished all the steps. But when running step 11 it got stuck in a boot loop due to some software issues with the patched image I assume.
I've tried opening the phone in fastboot mode and then connecting with ADB, but it seems I cannot find my device since USB-debugging is not turned on.
Any ideas of how this can be solved? Or am I screwed?
Click to expand...
Click to collapse
Did you install TWRP before rooting? If you did, that is the source of the bootloop. Our root guides here are much simpler than the one you provided the address to. The article in question is also out of date. Current versions of TWRP and Magisk don't play nice together. You need to BOOT TWRP using fastboot instead of installing it.
Copying the latest Magisk package to your internal storage, then renaming it to uninstall.zip and flashing it through TWRP should remove Magisk and resolve the bootloop. If that doesn't work, flashing the last stock package should.
EDIT: Quoted the wrong poster. My reply is an answer to the quoted poster instead of the poster who revived a dead thread with a question for a totally different device.
Strephon Alkhalikoi said:
Did you install TWRP before rooting? If you did, that is the source of the bootloop. Our root guides here are much simpler than the one you provided the address to. The article in question is also out of date. Current versions of TWRP and Magisk don't play nice together. You need to BOOT TWRP using fastboot instead of installing it.
Copying the latest Magisk package to your internal storage, then renaming it to uninstall.zip and flashing it through TWRP should remove Magisk and resolve the bootloop. If that doesn't work, flashing the last stock package should.
Click to expand...
Click to collapse
unfortunately there is not an exact version of twrp recovery available for my device lenovo (tbx605L) even when i try to boot the stock recovery.img , it says FAILED (remote : unknown command) do you know what is causing this error??
safaan0313 said:
unfortunately there is not an exact version of twrp recovery available for my device lenovo (tbx605L) even when i try to boot the stock recovery.img , it says FAILED (remote : unknown command) do you know what is causing this error??
Click to expand...
Click to collapse
I didn't realize you had replied to a thread that was two years old AND for the wrong device. Ask in the Lenovo section. This is the Pixel 2 XL section and advice given here is not applicable to you.
Strephon Alkhalikoi said:
I didn't realize you had replied to a thread that was two years old AND for the wrong device. Ask in the Lenovo section. This is the Pixel 2 XL section and advice given here is not applicable to you.
Click to expand...
Click to collapse
Hmm well thanks for your indirect F**k off
safaan0313 said:
Hmm well thanks for your indirect F**k off
Click to expand...
Click to collapse
I'm not sure you're aware of this, but not all devices are the same. Case in point: Samsung. How do you use fastboot commands on a Samsung device? Answer: You can't as Samsung doesn't support fastboot.
But thank you for making your expectations clear. Apparently, according to you, I should be able to figure out your problem despite not owning your device. It doesn't work that way. The only reason I know the answer to the question I posted in the previous paragraph is because I own a Samsung device.
Seriously, you getting bent out of shape at me because of your own screw-up is laughable.
Strephon Alkhalikoi said:
I'm not sure you're aware of this, but not all devices are the same. Case in point: Samsung. How do you use fastboot commands on a Samsung device? Answer: You can't as Samsung doesn't support fastboot.
But thank you for making your expectations clear. Apparently, according to you, I should be able to figure out your problem despite not owning your device. It doesn't work that way. The only reason I know the answer to the question I posted in the previous paragraph is because I own a Samsung device.
Seriously, you getting bent out of shape at me because of your own screw-up is laughable.
Click to expand...
Click to collapse
Right I knew that.I am sorry.I was so damn angry at my own mistake.I AM S O R R Y.But off the record I just repaired my tab