I updated to Oreo by signing up to the beta program and installed the full upgrade (~1GB) earlier today. It worked flawlessly for several hours and then the phone froze; I was unable to boot it up after that. I booted into recovery, performed a cache wipe, but since that, it still won't boot and now I can't go to recovery either (just get a blank screen after the Google logo). My device is locked, so I can't do a fastboot flashing unlock
Do you have any ideas what to do next? I can still go to fastboot and issue fastboot commands and the phone charges if I connect a charger in a powered-off state, but that's it.
Related
So I randomly have a corrupted data partition on my M8. I'm unlocked and S-off but was only running a rooted stock ROM.
What happened:
I went to go turn my screen on and hitting the power button did nothing. I thought maybe the battery was dead. Plugged the phone in and the battery charging screen came up. It said the battery was at 52%. I ended up holding the power button for awhile and it finally powered on. It took forever to load and I'm presented with this screen. It doesn't matter what password I put in, I always get this screen next. I can get into recovery but, again, it takes FOREVER to load and won't mount the userdata partition.
Here is what I've tried so far:
I've tried wiping through recovery but /data won't mount.
I've tried to flash a rom.zip through bootloader but I can't get it to RUU mode. The device just restarts normally when I run fastboot oem rebootRUU.
I've tried to run a RUU from my PC but it fails for the same reason as above. I'm thinking the RUU tries to run the fastboot OEM rebootRUU command because it just restarts like normal.
I've tried fastboot flashing userdata.img. That fails.
I've tried formatting with mkfs.
These guys are recovering OnePlus Ones through a debugging port. I'm trying to figure out if I might be able to do the same thing since the One M8 and the OnePlus One have a very similar chipset. I have ZERO experience with any of this so I'm looking for a little help. Unfortunately the OnePlus guys aren't responding to my PM's.
Thanks for any help!
TMartin said:
So I randomly have a corrupted data partition on my M8. I'm unlocked and S-off but was only running a rooted stock ROM.
What happened:
I went to go turn my screen on and hitting the power button did nothing. I thought maybe the battery was dead. Plugged the phone in and the battery charging screen came up. It said the battery was at 52%. I ended up holding the power button for awhile and it finally powered on. It took forever to load and I'm presented with this screen. It doesn't matter what password I put in, I always get this screen next. I can get into recovery but, again, it takes FOREVER to load and won't mount the userdata partition.
Here is what I've tried so far:
I've tried wiping through recovery but /data won't mount.
I've tried to flash a rom.zip through bootloader but I can't get it to RUU mode. The device just restarts normally when I run fastboot oem rebootRUU.
I've tried to run a RUU from my PC but it fails for the same reason as above. I'm thinking the RUU tries to run the fastboot OEM rebootRUU command because it just restarts like normal.
I've tried fastboot flashing userdata.img. That fails.
I've tried formatting with mkfs.
These guys are recovering OnePlus Ones through a debugging port. I'm trying to figure out if I might be able to do the same thing since the One M8 and the OnePlus One have a very similar chipset. I have ZERO experience with any of this so I'm looking for a little help. Unfortunately the OnePlus guys aren't responding to my PM's.
Thanks for any help!
Click to expand...
Click to collapse
Okay.
First, you can get into recovery, correct? That's how you should try to flash the ROM.zip
Can you boot into bootloader? If so, post what it says next to OS ( that's your firmware version) and I'll see if I can find an RUU.zip that you can flash through hboot.
If OS is blank (it's caused by older versions of TWRP), get into ADB/fastboot, and issue the command fastboot getvar all, then post the readout here. Delete the serial no. and IMEI from the readout for your own safety.
xunholyx said:
Okay.
First, you can get into recovery, correct? That's how you should try to flash the ROM.zip
Can you boot into bootloader? If so, post what it says next to OS ( that's your firmware version) and I'll see if I can find an RUU.zip that you can flash through hboot.
If OS is blank (it's caused by older versions of TWRP), get into ADB/fastboot, and issue the command fastboot getvar all, then post the readout here. Delete the serial no. and IMEI from the readout for your own safety.
Click to expand...
Click to collapse
I can get into TWRP but it won't mount the data partition. Are you saying I should try flashing another ROM the normal way through TWRP or try the sideload option? I tried to fastboot flash stock recovery. It says it worked but then continues to boot to TWRP.
I can get into bootloader. I'm pretty sure it's a 4.16.401.x ROM but I'll have to double check when I get home. I've tried to flash stock everything but it you know how it restarts through the process? When it restarts, it seems to want to restart to OS.
I'm about 99% sure the OS is there because it boots into Android but only gets me to the "Decrypt storage" screen.
Hello guys, a friend of mine has a galaxy nexus with some problems.
When I turn on the phone, it starts booting normally, but a few seconds after getting into "desktop" it starts popping up errors saying that the process as stopped.
I've already tried a few things, but without success. I'm running out of ideas and here I'm asking for your help.
Things I've tried:
-Boot into recovery mode and wipe all data.
The phone says that the operation completed successfully, but after rebooting the phone remains the same. All apps, wallpaper, lock screen, etc. It seems that nothing was changed by this process.
-Flash a original google ROM
Following the tutorials, the first step is to unlock the bootloader with fastboot oem unlock. The phone shows a confirmation asking if I want to unlock it, I say yes, and it shows "status: unlocked". But after rebooting the phone it is locked again!!!
I tried to flash the room without rebooting the phone after unlocking it,
Code:
fastboot flash bootloader bootloader-maguro-primela03.img
fastboot reboot-bootloader
sleep 5
fastboot flash radio radio-maguro-i9250xxla02.img
fastboot reboot-bootloader
sleep 5
fastboot -w update image-takju-imm76i.zip
The first command to flash the bootloader also says that completes successfully, but when I'm flashing the radio it will complain saying that the phone has the wrong bootloader version installed.
-Flashing via Odin
It fails when is flashing system.img to the phone
-Flash custom recovery - fastboot flash recovery recovery.img
The process completes "successfully" but when I boot into recovery mode, there is the original one and not the one I just flashed.
-emmc brickbug - partition scanner
I found this thread http://forum.xda-developers.com/showthread.php?t=1823918 and tried to run the partition scanner. As I can't have the phone on enough time to use adb shell, I tried to use this scanner via adb sideload but the phones returns an error when running it. (probably because it doesn't have busybox installed, not sure)
After trying all of steps above, the phone is still the same... nothing changed. Once, I managed to connect it to the pc as an usb storage device, and was able to copy some photos from the phone and deleted them. But after rebooting they were all there again. It seems that all write changes are not persistent.
I'm out of ideas now... Do you have any idea of what is the problem? Or any suggestion for me to try?
Thanks in advance
I believe that there is a script in the android SDK tools called flashall.bat which will reflash the kernel, bootloader, recovery, ROM ect. I'm not sure how to use it, but you could potentially try that
Hi, thanks for you suggestion, but unfortunately it didn't work.
I had a look at the flashall.bat script and it runs the same commands I run manually.
I think that the phone might have some hardware problem... Normally I would buy a new phone, but I'm trying to fix it because it is important for my friend and for me because it is challenging.
I guess that the next thing I will try, will be trying to run emmc_find_brick script by @hg42 via sideload
Try formatting /system and reinstall android. Power your device into bootloader mode. Make sure your device is unlocked. Also, make sure you have the factory image downloaded. After your device is plugged in into your computer, use this fastboot command: fastboot erase system. This will delete everything from /system. Also format /data and /cache: fastboot erase data and fastboot erase cache. After that, try installing the factory image again.
So before I get linked to a bunch of solutions, here's what I've tried so far as I do have fastboot access:
I've tried flashing the latest factory image from Google. Both manually from fastboot and with NRT, all to no avail. It shows the Google logo then reboots repeatedly. I've tried entering recovery to factory reset there after flashing, but the device won't get into recovery.
I've also tried this method, but I can't get the device to enter download mode. It shows that it's entering it for a moment when I plug it into my computer while holding volume up, but then reboots into the bootloop again.
There's one weird thing that should be noted that makes me think this is some weird software issue, and not a hardware failure. I let the device bootloop all night last night until the battery died. When I powered it on this morning it went all the way to the Android setup page where you select wifi, etc and go from there. However, when I plugged it in and kept going through setup, it rebooted and has been looping since. I've contacted Google and they're supposed to conference call me with LG to see what we can do. Do I have any options other than that? Thanks for any help.
From bootloader
fastboot erase cache
fastboot format cache
fastboot erase user
fastboot format user
BTW what exactly is happening when you say it doesn't enter recovery?
addisontodd said:
So before I get linked to a bunch of solutions, here's what I've tried so far as I do have fastboot access:
I've tried flashing the latest factory image from Google. Both manually from fastboot and with NRT, all to no avail. It shows the Google logo then reboots repeatedly. I've tried entering recovery to factory reset there after flashing, but the device won't get into recovery.
I've also tried this method, but I can't get the device to enter download mode. It shows that it's entering it for a moment when I plug it into my computer while holding volume up, but then reboots into the bootloop again.
There's one weird thing that should be noted that makes me think this is some weird software issue, and not a hardware failure. I let the device bootloop all night last night until the battery died. When I powered it on this morning it went all the way to the Android setup page where you select wifi, etc and go from there. However, when I plugged it in and kept going through setup, it rebooted and has been looping since. I've contacted Google and they're supposed to conference call me with LG to see what we can do. Do I have any options other than that? Thanks for any help.
Click to expand...
Click to collapse
it's seems like me , it's been a month i can't boot it up .
sfhub said:
From bootloader
fastboot erase cache
fastboot format cache
fastboot erase user
fastboot format user
BTW what exactly is happening when you say it doesn't enter recovery?
Click to expand...
Click to collapse
I choose reboot recovery from the fastboot menu and it just boot loops. It won't enter recovery.
addisontodd said:
I choose reboot recovery from the fastboot menu and it just boot loops. It won't enter recovery.
Click to expand...
Click to collapse
what if you try
fastboot boot twrp.img
I've bootlooped so many times I don't know where to start.
So you flashed the factory IMG from your bootloader correct.
Fastboot -w will wipe without wiping system.
Then reflash your whole system. I would redownload from the Google site through Skipsoft...the easiest way. When it asks to keep or flash new recovery you want to flash the stock recovery.
http://forum.xda-developers.com/nex...olkit-skipsoft-android-toolkit-nexus-t3230444
You'll have to reroot afterwards which you can also do through skipsoft.
Profit... Thank me if I helped.
It's a Hardware issue. Installing system again will not fix it. Send it to LG for a repair. My phone had the same issue.
I've been having the bootloop issue ever since ~November, where the phone will randomly reboot itself for no reason; charging, not charging, screen on or off, in any number of apps or phone call or just on the lock screen. Since I'm bootloader unlocked, I found that going into TWRP and clearing the Dalvik cache immediately fixed the issue (until tomorrow)! It typically happened once per day or every other day, seemingly depending on usage, until this week... I used it as normal, and it hasn't rebooted at all in over 5 days. Today it finally did, and now clearing the Dalvik cache does nothing for it; continuous bootloops. I decided now is as good as ever of a time to do a factory reset and update to stock 8.1 (previously was on stock 8.0 - I did the full wipe with the -w flag). Now it starts going through the setup process but locks up and turns itself off after about 60 seconds. I tried flashing BenzoRom using the below instructions and the same thing happens. Does anyone have any other thoughts? I really have nothing to lose at this point.
EDIT: Also tried Safe Mode with 8.0, 8.1, and BenzoRom 8.1. None worked better than without it.
EDIT2: Well this time I got all the way through setup (did set up as new device) and then went to download an app from the Google Play Store when it turned itself off. Lasted about 5 minutes.
EDIT3: It occasionally even freezes/turns off in TWRP. This is what's really making me think it's a phone defect.
EDIT4: I left it off overnight and it worked for an hour this morning before it turned off. Then I left it off for an hour but it froze immediately after turning on. Bizarre. Will let Verizon "troubleshoot" today (which will be a factory reset and then a shrug) and see what they recommend from there. Don't have high hopes since my bootloader is unlocked, even though that's completely unrelated to any issue. This shouldn't be happening after 15 months. I'm still making payments on it for the next 9
EDIT5: Verizon said out of warranty and no insurance so too bad. Checking with a different Verizon tomorrow and then ubreakifix. Not sure why I'm supposed to have insurance for something completely out of my control.
EDIT6: See reply below. Verizon is replacing with same phone.
xanaxdroid said:
For people having trouble booting custom roms please read:
Get a copy of the stock boot.img, twrp-3.2.0-0-marlin.img, twrp-pixel-installer-marlin-3.2.0-0.zip and the Benzo Rom zip.
1. Boot into bootloader
2. run: fastboot --slot all erase boot
3. run: fastboot --slot all format system
4. run: fastboot --slot all format vendor
Go to where you extracted the stock boot image
5. run: fastboot --slot a flash boot boot.img
6. run: fastboot --slot a flash boot twrp-3.2.0-0-marlin.img
7. run: fastboot --set-active=a
8. run: fastboot reboot-bootloader
9. Then select recovery from the bootloader menu
10. Go to wipe. Move the slider to factory reset which will wipe data, but not internal storage.
11. Install benzorom-8.1.0-date-version-marlin.zip and twrp-pixel-installer-marlin-3.2.0-0.zip
12. Reboot
If you want to install root after boot back into recovery by rebooting and holding volume down after you hit reboot then selecting recovery from bootloader. That will take you into TWRP on slot b which is where you want to install Magisk from. I don't use SuperSU anymore so Magisk is all I know that works.
You can get the twrp .img and .zip from their site right here.
Click to expand...
Click to collapse
Long story short, Verizon Extended Warranty at 866-406-5154 went through some troubleshooting (clear cache, then factory reset) then said this is NOT an insurance claim since it's a phone defect and they will replace the phone with a refurbished Pixel XL 128GB (same phone). Was hoping they could bump me up to an XL2 but no dice lol. They sent it with free overnight shipping and I have to send mine back within 5 days. Trading in my bootloader unlocked device hurts, but it's better than having no phone at all. Hope this helps others having the same issues.
I bought a Pixel XL yesterday from the local marketplace. It was being sold for cheap and mentioned that after an update the device doesn't start. I bought it for experimentation. When I brought it home it was completely discharged so I hooked it up to a wall charger and tried to turn it on. It turned on but was stuck in bootloop. I left it on charge for about 12 hours or so. After that I picked it up and saw that it was still in bootloop but now it was giving the "no command" screen as opposed to the Google splash screen that it was showing up in the morning. I pressed some buttons and went into recovery. I was completely unfamiliar with the issue at this point. I downloaded the official firmware matching the firmware version with the one being displayed at the top of the recovery screen. I put the phone into the "adb sideload" mode and started the sideload. After it completed the device booted up. I was really happy that I fixed the issue so easily.
However, I immediately got the prompt to update to Android 10 so without doing anything with the phone, I started the update process. I left it to update and after a few minutes I noticed the device was again stuck in the bootloop with the google splash screen. At this point, no matter what I tried, I could not boot into recovery mode but could easily boot into bootloader. After that I did the following things:
-> Tried installing the factory firmware from fastboot using the flash_all.bat file. It failed with an error saying could not update partitions table or something like that
-> I tried to boot into recovery using twrp recovery img but that failed as well, kept getting the Google splash screen
-> I flashed the boot.img from the factory firmware zip (that matched my firmware version) to both the partitions a and b using this command: fastboot flash boot_a path/to/file and fastboot flash boot_ab path/to/file. It did the flashing alright but the device just won't boot into recovery.
-> In short, I exhausted all the options but could not boot into recovery. When powered on with volume up button pressed, the device stayed on a black screen and when I let go the volume up button, the device would start bootlooping again
I hooked up the device to the charger and slept. When I woke up, the device was again stuck in bootloop. I went into bootloader and selected the option to power off. Since the device was on charge it showed the charging battery symbol and automatically landed onto the no command screen. I went into the recovery from there and again sideloaded the factory firmware hoping that the device will boot once done but upon restart it again got stuck into bootloop. I again exhausted all my options but could not get the device boot into the OS. I was however able to boot into twrp recovery and tried to do a complete wipe there but it gave error while wiping the dalvik cache and stopped there without completing the wipe. I pushed the twrp recovery.zip through adb into the device and tried installing, it got stuck while installation was in progress and started rebooting again. I could not get into the recovery again after that point onward. I flashed the factory boot.img to slots a and b but still couldn't get into it.
Now I have hooked up the device to the charger again and left it there. I am hoping after going through the bootloop for another 3 or 4 hours, it will boot into recovery once again. I will provide my results on this.
At this point, does anybody want to share their thoughts on this and suggest something that I should try? One option that I can think off is to disconnect the battery and reconnect it. It may break the loop but I don't want to disassemble the device at this point as I may break something and then won't be able to play with this anymore.