Hi,
I am going to describe my experience in hopes that it might help anybody. Also, the result at the end is not consistent with the Lollipop build info I have seen on multiple sites, so I am looking for any comments that experts might have. I am not an expert.
I accepted the Lollipop update (foolishly without looking at others' experiences) and I ended up experiencing the boot loop with the 3 circles flying around endlessly (or at least for multiple hours).
I looked at the various forums of people experiencing problems and learned how to enter the bootloader mode and the screen with the android on his back with red triangle & exclamation point coming out of his chest (can't recall the name of that screen). {apologies that I am in Montreal and I don't have my device so I can't reproduce this to be 100% precise with all statements}
Via these screens I tried:
1-resetting the cache with seemingly no impact ... still had endless boot load screen
2-wipe data/ factory reset with seemingly no impact
Interestingly, both options appeared to complete successfully based on the messages displayed
The forums at this point stated that the only way to get the device working was to flash the factory image, so I spent a while to get ADB and fastboot and the factory image and watched a bunch of youtube videos and got my ducks in a row. I got to the bootloader screen and realized that I didn't have the driver loaded, so took care of that.
For various reasons I re-started the device in order to get back to the boot loader screen. But, I had a brain fart and couldn't remember the sequence to press on the buttons to get there. I got to the first screen with the android on his back (red triangle w/ exclamation point) and the prompt "no command" (or something like that), and I started searching online for the button sequence. Then I got distracted with a phone call for like 15 or 20 minutes, but I am still sitting there with the device in front of me showing the same screen.
THEN, for some unknown reason, the device re-booted itself as it was lying untouched on my table, booted into the started screen and then the setup screen for Lollipop showed up. I was in shock. I set the tablet up without any issues. All the data and all apps were gone (but it seems to not have reverted to factory condition b/c it wasn't setting up KitKat). At any rate, I haven't found any bizarre/bad behavior, though I also had to leave it at home for my wife whilst I went on a business trip.
The one strange thing I noticed was that the versions didn't seem accurate as I compared them to some of the sites I was researching in my prep for flashing to Lollipop.
These 2 looked correct:
build number
LRX22G
Android version
5.0.2
but not in conjunction with this:
Baseband version
DEB-G00_2.42.0_1204
-because this should be for 4.4.3 or 4.4.4 as indicated on these websites
I restarted the device in the event something just wasn't refreshed properly, but all of those still showed the same after the restart. So, this is where things stand. Hopefully there isn't a problem with this combination, but please advise if you think there is. Also, please provide any insight as to how the machine can reboot itself in that mode and suddenly start working. I'm thankful, but befuddled.
Thanks, Peter
Related
Im trying to get the new Official Tmobile USA rom on my phone. I just flashed my phone over from a China 2.2 rom running one of jboogies recoverys. I wiped, then flashed the leaked tmobile rom. When I try to log into my motoblur account, the phone just locks up, and then shows a black screen. This lockup is once im within android, not during the boot sequence. The sbf was successfully flashed, but just black screens after a while. Also, the keyboard wasnt appearing when I tried typing in my details.
Any help is appreciated.
Ive managed to get passed the login screen by essentially racing to typing in my account and password before it crashed. I eventually got it. I can now the android os but it crashes almost instantly. About 10 or so seconds of actually navigation. I tried to get into the "about the phone" menu in the setting, but it kicks me out of it really fast. I saw something that said 2.1_update1. on my latest boot, ive activated USB debugging, which seems to be working. The phone isnt shutting down anymore. I however have no service (I didnt have any before USB debugging either though).
My phone seems stable being on with usb debugging on, but I still cant get into the "about phone" menu. It just kicks me back out. Still open to suggestions
Heres what i can read from the "about phone"
System Version:
Blur_Version.3.6.360.MB525.T-Mobile.en.us
Model Number
MB525
Firmware Version
2.1_update1
Baseband
EPU93ST2_U_03.04.2
Kernal Version
2.6.29
[email protected] #1
My phone keeps pushing me out of several apps such as the dialer, messagging, mostly anything Motorola related.
Tried flashing the tmobile us 3.4.2. I got my reception back, but home home screen was just black. I did have my bar at the top though. I couldn't access anything. I could receive calls. Flashing back to the u3_6.36.3.0 sbf. what a headache
I think i know my problem. I guess I need to do a full wipe in between flashing. Only problem is is that im not rooted anymore and i cant get any SBF to really work anymore. all im getting are black screens. What sbf can I use that I can root so I can wipe.
As far as wiping is concerned. I did wipe the first time, but then I rebooted the phone. I feel like that was my mistake.
Anyways, how can i get my phone working again?
After an unbelievable amount of frustration, ive managed to get it
Firstly, I went back to the u3_6.36.3.0 sbf. Like all the other roms I tested, I continued to have a black screen with a menu bar. I shut the device down, and booted into the stock recovery (Volume down + Power). I then touched the bottom right corner to get into the menu. I did a full factory reset. After I rebooted, the device was working 100% as intended. I check for the system update, and sure enough, its downloading now.
I really hope this can help someone, but I feel due to my lack of proper notation and poor documentation, it wont. Anyways, My only advice can really be to those trying to get the official tmobile 2.2. If when you flash the u3_6.36.3.0 sbf and you get a ton of errors, just try a factory reset via the stock bootloader.
What do you mean by touching the bottom right corner of the phone? On the screen or button need to be pressed? And surely it will enter into another menu sort of service menu where one can do a list of actions??
Great getaway by the way...
bottom right corner of the screen (lcd). Its the stock recovery. When you boot into the stock recovery, it will have a exclamation point in a triangle as well as an android standing by it. Once you actually enter the menu, it will look alot like the custom recovery. Also, be patient if you do the factory reset. it takes a little bit. It doesnt really show any indication that its working other then some periods occurring two or three times throughout the process.
Hi All,
Really hoping someone can suggest a possible solution for this one, only had the phone a few months!
So, Chinese released M9. Unlocked. Stock recovery, not rooted. Gapps installled.
Everything perfect, then today I got the 5.1 update.
Seemed like a slightly iffy install process...looked a little like it failed a couple of times and tried again.
Finally finished, the phone shows the white screen with the one logo, takes a while, opens on the desktop and turns off, back to the white screen with the logo.
I have been able to boot into safe mode, which is stable
I have been able to get to download mode and bootloader. Neither of these offer a cache wipe or a factory reset.
I have not been able to get into recovery mode, it shows a phone with a red triangle and an exclamation point.
So for my (largely uneducated) part I have two theories for the cause:
1) Gapps is somehow proving a problem, either faulting the install or causing a fatal error on startup
2) Since the update was notified and downloaded while on a VPN via Hong Kong, I wonder if I accidentally ended up with the HK version in which case I suspect there may be hardware differences (at least the radio). This seems unlikely, I would hope there were enough checks in place to prevent this happening.
No solid idea where to go from here. I have not yet tried ADB access, but even if I can connect, what will I do? Flash a new ROM? I'd rather not. And surely I'd need to root in order to do that....
At a loss, any potential solutions welcomed whole heartedly!
Thanks...
Booting into safe mode, but not booting otherwise, indicates a problem with some app or rom setting.
You're probably going to need to do a factory reset, but that's odd that it doesn't show up in bootloader or download mode. Have you tried the options in stock recovery (which is that screen with the red triangle)? Use the volume keys to change options.
Hi iElvis - the screen with the red triangle - there's nothing other than the red triangle, no options, no text and nothing happens if I press any of the physical buttons.
Trying a factory reset from safe mode - I'll let you know what happens!
misteral1970 said:
Hi iElvis - the screen with the red triangle - there's nothing other than the red triangle, no options, no text and nothing happens if I press any of the physical buttons.
Click to expand...
Click to collapse
Hmm. It would seem the Chinese models are set up differently, which would not surprise me at all.
Watch was working great for few weeks and then suddenly I started getting lots of error message stating "Android Wear has Stopped". So i tried to reset my watch, after the restart the watch was not getting past spinning color screen. I even tried couple of hours but nothing happened.
I went through some of the forum topics and tried to flash Boot, Recovery and System with the stock images. Now the issue seems to be different, whenever the system boots I get a image of Android System chest open with a red alert symbol on it.
I am able to login to Fastboot and Recovery mode, tried the same process multiple times. But still not able to get pass the latest error. I tried to TRWP recovery, Stock Recovery and tried to reset my watch. But nothing seems to fix the issue. Any guidance on how to fix this will be really helpful.
Do let me know if I am doomed also...Hope it is not the case...
Did Anyone managed to solve this issue, currently having my watch without doing anything. Any help on this is really very much appreciated. Thanks.
Okay, so i have an LG G3 D855, few months ago it worked like a charm.. But then shortly after i started noticing random reboots everytime during using apps. Then it went in bootloop. I tried to turn it on again, entered recovery screen, choosed factory reset and it did, but then it went through the same process, random restart. Eventually stuck up in factory resetting screen. However i think i made mistake when the phone freezed in reset screen : pulling out the battery. later it lost its IMEI & kept heating up (probably tried to find its cellular framework of some sort).
Days passed, several factory resets has been done. Now the phone's at its worst state. It refused to get past the boot logo. everytime it finishes booting, the display just goes black, tried to plug usb charger, chargin indicator doesn't want to turn on, neither after i pulled out the battery. I have to leave it a few days to get it working again, but it keeps persisting.
Addition : The phone's also feels warm post the blackscreen.
Any thoughts whether can this be fixed or i have to replace something inside the phone's board?
thanks in advance.
Sussudioo said:
Okay, so i have an LG G3 D855, few months ago it worked like a charm.. But then shortly after i started noticing random reboots everytime during using apps. Then it went in bootloop. I tried to turn it on again, entered recovery screen, choosed factory reset and it did, but then it went through the same process, random restart. Eventually stuck up in factory resetting screen. However i think i made mistake when the phone freezed in reset screen : pulling out the battery. later it lost its IMEI & kept heating up (probably tried to find its cellular framework of some sort).
Days passed, several factory resets has been done. Now the phone's at its worst state. It refused to get past the boot logo. everytime it finishes booting, the display just goes black, tried to plug usb charger, chargin indicator doesn't want to turn on, neither after i pulled out the battery. I have to leave it a few days to get it working again, but it keeps persisting.
Addition : The phone's also feels warm post the blackscreen.
Any thoughts whether can this be fixed or i have to replace something inside the phone's board?
thanks in advance.
Click to expand...
Click to collapse
Reflash with lgup.
Remove the SIM card and the memory card. try again. Full wipe system data ...
I've had the same problem. I've tried. Worked
found the problem. memory card
EDIT: Some kind of voodoo happened right now! I was about to unbrick again and wanted to give the phone a try to boot before. And it did! So no problem at the moment, but still a strong feeling of uncertainty...
EDIT: Phone is still randomly rebooting and gets stuck in bootloops
-----
Hej guys, I really need your advice,
but first things first: Thank you very much for all of your wonderful work on custom roms and further support of older devices. I've been reading here for a few years now and was more or less happy to have up-to-date-roms for some of my phones.
Now I'm facing quite the same problem like OP did / does. Everything started with me, following this guide to root my D855 (coming from stock rom) and flash TWRP: you tube.com/watch?v=8VOgM3jLas4 (Note: The guide told me to flash "3__HacerPermisivo.zip" for updating the kernel, which I did.)
Next, I flashed a newer version of TWRP ("twrp-3.2.3-0-d855.img") than the one provided in "2__AutoRecMMD855.apk" by the guide above. I wiped dalvik and cache and after that, I flashed "lineage-15.1-20190410-nightly-d855-signed.zip", wiped dalvik and cache again and flashed "open_gapps-arm-8.1-pico-20190411.zip". I wiped dalvik and cache again and told TWRP to reboot.
Here is, where problems began to occur. The phone got into a bootloop, showing up the LG splash screen again and again instead of booting into LOS correctly and set it up. At some point I decided to remove the battery. When I did, at the same time LOS was just going to load, which I saw because of its beginning boot animation. So I screwed it up right at the wrong moment, I guess.
From here, the phone bootlooped every time, I wanted it to start. No battery acrobatics helped and on top I couldn't get it into recovery mode. Any attempts ended in bootloops. I think, this might be what is called a brick / to brick your device, isn't it? I found this guide to unbrick a D855 and followed its steps: open -freax.fr/guide-unbrick-your-lg-g3/
Believe me, it was a real pain in the ass! Because of me, messing up something or the phone getting stuck into a bootloop during the unbrick process, I had to do it 4 to 5 times until success... I have to say: I didn't follow the last steps beginning from "Root". Instead, I followed the guide from the beginning of my post.
Finally, I got "lineage-15.1-20190410-nightly-d855-signed.zip" and "open_gapps-arm-8.1-pico-20190411.zip" to run. I set it up and began to load some of my apps of my Play Store collection. While downloading, the phone froze, crashed and began to bootloop, from here unable to boot normally or to get into recovery mode. So I unbricked and flashed again (again several times because of bootloops before LOS first set up). When I got it to work again, I was able to install my apps without being trolled by the phone again. But scrolling through the eBay app froze the phone and it began bootlooping again...
You can believe me, I was about to throw the D855 against the hardest piece of wall, I could possibly find in my rage. The reason why I didn't give up at this point is, that I LOS-rommed two other D855s just a few days before. Those were my mom's and my girlfriend's and they work fine until today. I bought this third one for myself, because I was impressed, how good LOS worked on the D855s. On top I wanted to get rid of my Samsung Galaxy S4 (GT-I9515), because LOS kinda sucks on it, but this is another story...
So I figuered that the earlier LOS version I used for the women's phones, could solve the problem. So I unbricked again and flashed "lineage-15.1-20190327-nightly-d855-signed.zip" and "open_gapps-arm-8.1-pico-20190329.zip". And hell yeah, that did work! No bootloops, eBay worked fine, just everything was as I loved it on the other phones, I flashed. Until tonight. I've been lucky for almost two days, but tonight this happened: I plotted a route in Google Maps and saved it as a shortcut on my homescreen. I closed Maps and tapped the route icon. Freeze - crash - bootloop - no recovery mode! I wanted to start crying, because Maps has already worked fine yesterday. And it still does on the other two phones, which run exactly the same rom...
So now, I'm sitting here, not knowing what can be done further. I'm not a programmer / developper or any of those cracks providing us the newest software for old phones. So I just can do wild guesses. Maybe the moment I removed the battery the very first time after flashing messed something up very deep inside the phones internals and it can not be cured any more. Maybe some of you guys have experienced similar things and know a tweak or a simple step, I forgot. Anyway, I hope I can use my phone on LOS some day which I bought especially for this case.
Keep up the great work, folks!
Greets
I ordered a new mainboard. It should arrive within 3 weeks. I'll keep you updated.
A week ago, all of a sudden, my Pixel decided to freeze and become unresponsive. To make a long story short, it only goes to the Google logo screen and will not go into bootloader or recovery mode. Took it to a repair shop and they said it needed to be sent back to Google (it's three years old so long past its warranty) which would cost a fortune. They said it is soft bricked.
I'm looking into things and since my phone is already useless, I surely can't make it any worse. (fingers crossed.)
I'm wondering if anyone has any tips on how to get my phone back up and running whilst also keeping all of the data on my phone. I'm not keen on wiping the data as it has important information on it. Is it possible to unbrick a Pixel XL without factory resetting it?
Does anyone have a simpletons guide on how to do it? I've looked at numerous guides and they are either long winded or far too complicated for me. I'm not familiar with downloading a file to unzip it or extracting it. Although, I am very much willing to learn given my circumstances.
If anyone can provide any information, I would be very grateful!
i think if anything at this point, you need to assume none of your data can be saved. if you send it to google for them to fix, no data will be kept most likely, nor if you find any solution to do yourself. what happens if on the google screen you hold down power and voldown until it turns off and then keep holding them down?
It goes into fastboot with the android guy on it's back and it gives me the "restart bootloader", "recovery mode", "barcodes", etc, options. None of which the phone can enter apart from the barcodes and the powering off option. :crying:
HanaTruly said:
A week ago, all of a sudden, my Pixel decided to freeze and become unresponsive. To make a long story short, it only goes to the Google logo screen and will not go into bootloader or recovery mode. Took it to a repair shop and they said it needed to be sent back to Google (it's three years old so long past its warranty) which would cost a fortune. They said it is soft bricked.
I'm looking into things and since my phone is already useless, I surely can't make it any worse. (fingers crossed.)
I'm wondering if anyone has any tips on how to get my phone back up and running whilst also keeping all of the data on my phone. I'm not keen on wiping the data as it has important information on it. Is it possible to unbrick a Pixel XL without factory resetting it?
Does anyone have a simpletons guide on how to do it? I've looked at numerous guides and they are either long winded or far too complicated for me. I'm not familiar with downloading a file to unzip it or extracting it. Although, I am very much willing to learn given my circumstances.
If anyone can provide any information, I would be very grateful!
Click to expand...
Click to collapse
I have the same exact problem. Started Nov. 14. Talked to google asked me to take it to uBreakiFix. They ran diagnostics and said they can't fix it.
My phone used to boot up randomly but would freeze after 2-3 mins and crash again into a bootloop. Now it's stuck on white "google" screen and can't get into recovery or any other modes.
Nilkong said:
I have the same exact problem. Started Nov. 14. Talked to google asked me to take it to uBreakiFix. They ran diagnostics and said they can't fix it.
My phone used to boot up randomly but would freeze after 2-3 mins and crash again into a bootloop. Now it's stuck on white "google" screen and can't get into recovery or any other modes.
Click to expand...
Click to collapse
by boot up randomly do you mean it would randomly reboot or turn on while it was off?
sudoxd said:
by boot up randomly do you mean it would randomly reboot or turn on while it was off?
Click to expand...
Click to collapse
I mean it would boot successfully and take me to lock screen where I can use the phone for few minutes until it freezes again.
Currently I am connected to computer with adb shell open and have phone on the screen where I can see options to select 'barcode' 'recovery mode' 'power off'. The screen shows baseband version, CPU, UFS, DRAM, "Device is locked".
Adb is recognizing the devices (I can't unlock because I had the option to "OEM unlock" turned off in settings). But when I try selecting 'recovery mode' its back to 'Google' screen and stuck there.
Nilkong said:
I mean it would boot successfully and take me to lock screen where I can use the phone for few minutes until it freezes again.
Currently I am connected to computer with adb shell open and have phone on the screen where I can see options to select 'barcode' 'recovery mode' 'power off'. The screen shows baseband version, CPU, UFS, DRAM, "Device is locked".
Adb is recognizing the devices (I can't unlock because I had the option to "OEM unlock" turned off in settings). But when I try selecting 'recovery mode' its back to 'Google' screen and stuck there.
Click to expand...
Click to collapse
try sideloading the latest OTA and see what happens, this doesnt require an unlocked bootloader, just adb sideload.
sudoxd said:
try sideloading the latest OTA and see what happens, this doesnt require an unlocked bootloader, just adb sideload.
Click to expand...
Click to collapse
I flashed the new version of OTA from google's site. And it looks like it's booting up. Will report back if it crashes or continues to hold up.
Thanks!
EDIT: It's back to boot looping. It was at the "G" screen with white loading bar underneath. It froze there and went back to bootloop. Looks like there might be no avail.
Similar issue here. I gave up on it a month ago, but I figured it can't hurt to ask around. FWIW, there seem to be a lot of similar reports on Google's Pixel support forum.
Anyway, during the 2nd year of owning my Pixel XL (got it in Septempter 2017), I started experiencing slowdowns and random reboots more frequently, but never any bootloops until after receiving Android 10. After receiving Android 10, the random reboots seemed to be happening more frequently. I also experienced a weird issue where the phone would spontaneously exit out of the Google app (reached by left edge swipe from home screen) consistently within a few seconds of entering it.
Eventually, after another increasingly common random freeze, the phone rebooted and got stuck in a bootloop. Initially, chances were high that I would be able to complete the boot process after a few attempts, but inevitably, it would freeze and start bootlooping again. During the handful of successful boot attempts, I was able to backup some photos, and more importantly, enable OEM bootloader unlock in the developer options. After several more failed attempts to boot successfully, I did a total reflash of the latest factory image as of September 2019, after which I was able to get partially through the new phone setup process before crashing. For each subsequent attempt, the crash would happen earlier and earlier in the setup process until it wouldn't get further than the 'G' logo before rebooting. When the October 2019 factory image became available, I tried flashing that as well, but no luck.
On one hand, considering that the failures got progressively worse over time, it seems that this is fundamental hardware failure in the SOC, motherboard, RAM, etc. On the other hand, there seems to have been so many recent reports of this, especially after the Android 10 update, that I wonder whether or not it is software issue. Or could it be some combination of both, where the Android 10 update is pushing the hardware in new ways that is more likely to exacerbate an underlying hardware flaw?
Should I try re-flashing with Android 9 instead? At this point, it is a total brick...
sudoxd said:
try sideloading the latest OTA and see what happens, this doesnt require an unlocked bootloader, just adb sideload.
Click to expand...
Click to collapse
Would this be possible to do with a phone that doesnt turn on but the computer does see it as a qualcom device?
ckidmcd said:
Would this be possible to do with a phone that doesnt turn on but the computer does see it as a qualcom device?
Click to expand...
Click to collapse
Needs to boot to any recovery, custom or not, to sideload an ota
sudoxd said:
Needs to boot to any recovery, custom or not, to sideload an ota
Click to expand...
Click to collapse
Do I have any options to pull the data from the device since it does see a qualcomm device when plugged into a computer?
ckidmcd said:
Do I have any options to pull the data from the device since it does see a qualcomm device when plugged into a computer?
Click to expand...
Click to collapse
does fastboot see your phone at all if you type `fastboot devices`