Related
Last night I installed geefree on my phone from the app store and used it to install TWRP. I downloaded a nightly CM11 and an appropriate gapps. Using geefree I rebooted to recovery (never figured out the button combination to boot to recovery "naturally") and installed both of the zips. This could be where I made my mistake, I installed both at the same time.
Now my phone loops, displaying the LG logo for a few seconds, then shutting off and rebooting before repeating the process. I can't seem to get it to go into download mode or the recovery menu. I've tried power+up, power+down, down+up and each of those while plugging the device in, etc. I can get the device to a hardware key control mode, though it doesn't seem too useful.
How can I save my phone? This forum has been a great resource in the past and I'm very grateful for the many tutorials I've followed rooting other devices. Hopefully you guys can save the day once again!
Volume up plus power is how to access recovery on sprint.
What stock sw version were you on before you flashed cm?
Did you wipe data before flashing?
Sent from my LG-LS970 using xda app-developers app
I was using stock 4.2.2, I believe. I didn't wipe the data (shame on me), a bad habit that I picked up from my first rooted device, the Samsung Moment. It didn't ever matter on that one, afaik. Thanks for the reply!
Edit: Volume up and power whether plugged in or not takes me to the hardware key control mode screen.
Second Edit: http://forum.xda-developers.com/showthread.php?t=2432476&page=35 I also found this thread where someone seems to be experiencing similar issues and they fix it with "LG Utility." Is that a PC application? It's a little vague to google, but I've been trying!
I have a bootloop issue every time i flash a rom i have to wipe all but sd flash roms and gapps the i do a restore from twrp and oly restore my boot image only and they boot no prob
I'm kind of starting to suspect my power button doesn't work at all for whatever reason. I have a lot of difficulty getting the phone to shut down, then it doesn't seem to easily power up. It's a strange collection of problems. Would a Sprint repair place be able to fix this?
If they have parts on hand if not either a swap out or a sendoff
Same problem here - bootloop and no download mode - CWM works! - urgently need help
I guess I have the same problem as InlineFourPower (apart from that my power-button has no problem).
I am stuck in bootloop since I tried to upgrade to Kitkat a few days ago. Now I can´t get into download mode any more, nor into fastboot or anything else. Only CWM works.
From within CWM I can successfully flash ROMs but that doesn´t help, since afterwards I am still stuck in bootloop. It is possible, however, to push files via adb-commands while I am in CWM.
Does anybody have an idea how to go from here or how to get download-mode back?
Device is recognized but can´t be mounted - bricked forever?
Parinibbana said:
I guess I have the same problem as InlineFourPower (apart from that my power-button has no problem).
I am stuck in bootloop since I tried to upgrade to Kitkat a few days ago. Now I can´t get into download mode any more, nor into fastboot or anything else. Only CWM works.
From within CWM I can successfully flash ROMs but that doesn´t help, since afterwards I am still stuck in bootloop. It is possible, however, to push files via adb-commands while I am in CWM.
Does anybody have an idea how to go from here or how to get download-mode back?
Click to expand...
Click to collapse
I tried a few things on Linux.
After terminal-command "ls /dev/sd*" when the device is unplugged from the computer I get "/dev/sda".
When the device is connected via USB, I get: "/dev/sda /dev/sdb"
So sdb is my LG G2.
So I went on to the next command: "gdisk -l /dev/sdb"
As a result I get: "Problem opening /dev/sdb for reading! Error is 123."
Does it mean that the phone isn´t mounted or what? Now I´ve connected my phone to another Linux machine with the same result. It is recognised (p.e. as sdd), but there is no sdd1. Seems as if it is recognized, but can´t be mounted. Does that mean my device is bricked for good? That´s it?
to get the phone into download mode you have to plug the usb cord in and hold VOL+, so to get this right as I have a case on mine, plug the usb into the phone first then hold VOL+ and plug into usb port on the computer.
it does take a loooong time to power down the phone with the button when stuck in a boot loop, just keep holding it until it shuts off, it will shut off eventually!!
plug the phone in while in download mode to install drivers and set com ports, then unplug before you begin your flash with LGFlashTool, hope this helps you out.
Cronic2009 said:
to get the phone into download mode you have to plug the usb cord in and hold VOL+, so to get this right as I have a case on mine, plug the usb in first then hold VOL+ and plug into usb port.
it does take a loooong time to power down the phone with the button when stuck in a boot loop, just keep holding it until it shuts off, hope this helps
Click to expand...
Click to collapse
Thanks Cronic2009 for your advice.
There are, however, szenarios where download-mode is not accessible any more. Neither by using the hardware-keys, nor by using the adb-command.
After four days of resarch and a lot of trial and error, I finally unbricked my F320L using the two adb-commands outlined at the beginning of that thread: http://forum.xda-developers.com/showthread.php?t=2451696
Worked like a charm.
Thanks everyone for your advice.
no problem buddy, glad you got it figured out, good luck to you from here on out!
FYI, that link doesn't work
I just wanted to ask anyone who might know, since the bootloader of the LS980 is locked, we cannot "break" this correct, so no matter what commands we decide to run through root, we cant touch the true bootloader there for LS980 fail safe? (Besides Acts of God, EMP, ect)
Cronic2009 said:
no problem buddy, glad you got it figured out, good luck to you from here on out!
Click to expand...
Click to collapse
Thanks for letting me know. I corrected the link in my previous post.
Be sure if you use a aosp based rom to flash the ZV8 modem. Your can use dr87 or furnance kernals after you flash the zva modem althought i have encountered soft brick due to this.
so i'm having this exact issue and i don't know how to get out of it. i just need to transfer the radio to my phone somehow but nothing shows up under adb devices. i'm trying to the lg mobile support tool now. its downloading the software. but if it doesn't work does any one have any fixes?
edit: i fixed it by following this http://forum.xda-developers.com/showthread.php?p=51637410&highlight=download+fail#post51637410
pitbullmommy45245 said:
so i'm having this exact issue and i don't know how to get out of it. i just need to transfer the radio to my phone somehow but nothing shows up under adb devices. i'm trying to the lg mobile support tool now. its downloading the software. but if it doesn't work does any one have any fixes?
edit: i fixed it by following this http://forum.xda-developers.com/showthread.php?p=51637410&highlight=download+fail#post51637410
Click to expand...
Click to collapse
Thank You for sharing you fixed your issue pittbullmommy but the link you posted points back to a post about a failed run on LGFlashTool, will you please fix the link and point it to the post/guide you used to fix your phone, it may help others stuck in a similar situation, glad to hear you got it fixed and working, best of luck with it from here on out!
Hi all
was just about to start a new thread but didn't want to get into trouble..anyway I am in need of some assistance please.my ls980 has been bricked for some time now been searching all over the internet for a solution to be stuck back at square one.found this video on youtube which is pretty much exactly what my phone is doing.I have used lg flash tool to revert to stock and still nothing I lost root doing that but last night,I managed to regain root access I have no idea how but it happened when i clicked ioroot batch file i went into download mode and it stated bottom left ROOTED in red so i managed that but that is it still doing what is being shown in the video its on youtube
watch?v=PjLF-pBhZSY
please if anyone has the know how I would like to fix this phone rather then bin it thank you all happy 4th everyone
After using tot and flash tool to get back to stock, did you try going into stock recovery and do a factory data reset? I know it sounds stupid especially after a tot but try it. Couldn't hurt
Sent from my LG-LS980 using Tapatalk
Borderline noob here, so please bear with me...
I have been using TWRP 2.7.0.0 to do all my work, and I was able to get the Lego ROM installed with ZVA. I got into too big of a hurry and forgot to make a backup of stock. I've also been unsuccessful in trying to install ZVC modem and firmware. Thankfully ZVA works as does the LEGO ROM, but I'd like to have stock there to access as well. The stockZVC that's on the Android Development page has been getting stuck (bootloop?) on the Sprint Spark logo. I've done TWRP's factory reset with no success. Any help would be great.
Thanks in advance!
Yes sir I've tried that and more to no avail is there anything I can do through adb I'm on stock recovery phone doesn't stay on long enough to install anything
sarfdawg said:
Borderline noob here, so please bear with me...
I have been using TWRP 2.7.0.0 to do all my work, and I was able to get the Lego ROM installed with ZVA. I got into too big of a hurry and forgot to make a backup of stock. I've also been unsuccessful in trying to install ZVC modem and firmware. Thankfully ZVA works as does the LEGO ROM, but I'd like to have stock there to access as well. The stockZVC that's on the Android Development page has been getting stuck (bootloop?) on the Sprint Spark logo. I've done TWRP's factory reset with no success. Any help would be great.
Thanks in advance!
Click to expand...
Click to collapse
You ever get her fixed?
I found the guide to unlock downgrade and root 20i, but since i was already on 20i i figured id just skip to the unlock part.
ADB connected.
Got the oem unlock to work flawlessly, tried to boot TWRP, and it said file sent, cannot boot, file unsigned (or something similiar, can copy paste the actual text when i get off work tonight)
I got annoyed and just booted the phone normally and it worked fine and is unlocked-
But cant get the phone to show up on adb again.
Maybe try the universal drivers? Seems to hang on the drivers- the laptop has them installed but the phone doesnt know that they are and keeps asking me to reinstall (which doesnt work)
Any ideas?
Should i start over,upgrade the stock rom and then downgrade, like the directions actually say?
redchigh said:
I found the guide to unlock downgrade and root 20i, but since i was already on 20i i figured id just skip to the unlock part.
ADB connected.
Got the oem unlock to work flawlessly, tried to boot TWRP, and it said file sent, cannot boot, file unsigned (or something similiar, can copy paste the actual text when i get off work tonight)
I got annoyed and just booted the phone normally and it worked fine and is unlocked-
But cant get the phone to show up on adb again.
Maybe try the universal drivers? Seems to hang on the drivers- the laptop has them installed but the phone doesnt know that they are and keeps asking me to reinstall (which doesnt work)
Any ideas?
Should i start over,upgrade the stock rom and then downgrade, like the directions actually say?
Click to expand...
Click to collapse
The LG driver you've installed on your laptop is most likely no longer functional for the phone. If it shows in Device Manager when you're trying to connect it, uninstall it (mine didn't work either after unlocking/using FWUL, or something else, for whatever reason).
Once the current driver is uninstalled, turn off your computer, plug your phone in with the USB cable and then turn on the computer and let Windows install the driver now (It worked on mine).
See the attachment below for a screenshot of the current driver for my LG G4 that is working completely.
I got it to show up, but I've realised I have the motherboard issue common to G4's.
The phone hangs at 'bootloader unlocked' lg screen.
Hope the seller will give me a refund or exchange.
redchigh said:
I got it to show up, but I've realised I have the motherboard issue common to G4's.
The phone hangs at 'bootloader unlocked' lg screen.
Hope the seller will give me a refund or exchange.
Click to expand...
Click to collapse
It may just be a 'soft brick' you've encountered, in which case you should be able to it overcome relatively easily. First thing to try, is just unplug the phone and take out the battery. Put the battery back in and see if it will boot up. If not, see if you can get into Download mode and flash your rom version for your phone model with LGUP-NEW.
With respect to TWRP, if you can get into bootloader/fastboot mode, refer to this thread: https://forum.xda-developers.com/g4/development/recovery-twrp-3-touch-recovery-t3442424 and follow the instructions to flash by fastboot commands. Use the latest preview version for your rom version, i.e., MM, N or O.
Note: The Thanks button at the bottom right of the post should be used when members are trying to help you with your issues. It's an XDA courtesy, so please learn to use it.
sdembiske said:
It may just be a 'soft brick' you've encountered, in which case you should be able to it overcome relatively easily. First thing to try, is just unplug the phone and take out the battery. Put the battery back in and see if it will boot up. If not, see if you can get into Download mode and flash your rom version for your phone model with LGUP-NEW.
With respect to TWRP, if you can get into bootloader/fastboot mode, refer to this thread: https://forum.xda-developers.com/g4/development/recovery-twrp-3-touch-recovery-t3442424 and follow the instructions to flash by fastboot commands. Use the latest preview version for your rom version, i.e., MM, N or O.
Click to expand...
Click to collapse
Thanks for the tip. I already tried ADB (wouldn't boot reliably), LG UP (completes successfully- the phone, when LG UP sends the reboot at 75% or so, just hangs on the LG screen forever (though LG UP says it was successful). I also have LG Bridge, but haven't reached any level of success with it either. Luckily all these bookmarks will come in super handy with my replacement.
(Also the day it broke, somehow the camera activated in my pocket. I detected the warmth, but working an assembly line, under a cameras watch, I couldn't pull it out and fix it quickly.
sdembiske said:
Note: The Thanks button at the bottom right of the post should be used when members are trying to help you with your issues. It's an XDA courtesy, so please learn to use it.
Click to expand...
Click to collapse
Thanks for the reminder, I'll try to remember.
redchigh said:
Thanks for the tip. I already tried ADB (wouldn't boot reliably), LG UP (completes successfully- the phone, when LG UP sends the reboot at 75% or so, just hangs on the LG screen forever (though LG UP says it was successful). I also have LG Bridge, but haven't reached any level of success with it either. Luckily all these bookmarks will come in super handy with my replacement.
(Also the day it broke, somehow the camera activated in my pocket. I detected the warmth, but working an assembly line, under a cameras watch, I couldn't pull it out and fix it quickly.
Thanks for the reminder, I'll try to remember.
Click to expand...
Click to collapse
OK - one last thing to try if you want to try it. Using the power and volume keys, see if you can get into Recovery mode to do a hard factory reset
- refer to this link for the how-to for entering Recovery mode: https://www.androidexplained.com/lg-g4-recovery-mode/
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
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?