Hi guys,
A few days into this fiasco now aha - my Pixel 4 seems to be (nearly entirely?) bricked.. won't turn on past the fastboot screen, pretty much stuck in a loop there.
I fear that I may have wiped it entirely or otherwise severely corrupted it. Was originally trying to root it, but never got that far and ended up in this mess.
I have tried to re-flash from the website as well as the batch file but it keeps getting stuck on the "fastbootd" screen when "uploading partition data 1/10".
I can access fastboot mode. It is unlocked. Cables and all that are definitely fine. Just can't bring it back to android.
Thanks for any help in advance
Edit: here's a link to the flashing process and what happens - Video
Anyone? Aha
have you tried to flash factory image locally? (instead of web flasher?)
what does the fastboot screen say when it boots into fastboot?
(It gives a reason for having booted into fastboot)
Related
Hi, my wife got an Asus Zenpad 10 (Z300 series) tablet not too long ago, and recently it seemed to be acting up. It didn't seem to know what its battery level was so it'd suddenly shut down and would rarely stay on for a few hours if that.
I've been reading these forums and Google searching every evening for days now to no avail.
The the other day when i turned it on, it was in a bootloop. I had this happen on my own tablet so I was aware of using ADB and the recovery menu to wipe the davlik cache.
Except, that this Asus tablet only has fastboot screen (which I'd not seen before - my Samsung went to a different recovery mode), so I've been researching that more recently.
I got ADB and Fastboot working, erased the cache via Fastboot which stopped the bootloop, but it would only go as far as the logo with the little spinner circle. After messing around with fastboot trying to do a factory reset and put a custom recovery on it (TWRP) it now will only boot to the Asus logo and not even have a spinner anymore!
The flashing of anything - recovery, stock rom from ASUS (this file as I found elsewhere on these forums: UL-P01M-WW-3.3.8.0-user.zip -- although I'm not entirely sure i'm flashing correctly).
Anyway, I'm stuck with only an Asus logo or fastboot mode screen and am not that good with fastboot/adb since I only had to delve into it once to fix my own tablet over a year ago.
If anyone can help that'd be very much appreciated! :good:
[update]
OK so after failing to flash any zips (or anything!) to the device, I left it on in fastboot mode while I went to work. Now upon coming home the tablet is just a black screen! The laptop recognises it because Windows makes that chime sound when its plugged in via USB. But other than that, I can't get a response out of it Button combinations don't seem to help so now I'm not sure what to do!
Can anyone help me please? :crying:
Unless the bootloader is locked, you may have made a mistake trying to flash the ROM and trying to install a custom recovery. Anyways, if you hadn't made any changes yet to the system, I would have said check the battery first because it may be malfunctioning and not the phone it's self. I know from experience that it may have been the battery considering the way you said it was not reading the battery percentage right and shutting down. And that "bootloop", this was probably happening because it didn't have any power to start up the device as this is exactly what my device did when I had a faulty battery. My best bet is to 1 try to get a new battery, and then 2 see if your system is still intact otherwise try and reflash with the stock ROM (through adb or any computer to android debugger) and then reinstalling the right recovery that goes with the device or that of which is c-o-m-p-a-t-a-b-l-e.
Using CM12.1 on my SGH-T999
I exactly got the same issue, nothing I particularly have done as far I know, my tablet suddenly rebooted and now is stuck on Asus logo with the little circle that keeps turning.
I tried to let it go till my tablet get completely discharged and also tried to charge it completely, nothing change.
And when I wanna access to the recovery, I just get the green android mascot with the message "ERROR!". So I can't even access the recovery to reset my tablet :crying:
Edit: Tried a fastboot erase userdata and an erase cache, still bootlooping
Sorted
The only way I fixed this was by returning it to the shop and having the device replaced! Not the ideal solution, but it worked. :good:
MrLewk said:
The only way I fixed this was by returning it to the ship and having the device replaced! Not the ideal solution, but it worked. :good:
Click to expand...
Click to collapse
I guess I will have to do the same
MrLewk said:
Hi, my wife got an Asus Zenpad 10 (Z300 series) tablet not too long ago, and recently it seemed to be acting up. It didn't seem to know what its battery level was so it'd suddenly shut down and would rarely stay on for a few hours if that.
I've been reading these forums and Google searching every evening for days now to no avail.
The the other day when i turned it on, it was in a bootloop. I had this happen on my own tablet so I was aware of using ADB and the recovery menu to wipe the davlik cache.
Except, that this Asus tablet only has fastboot screen (which I'd not seen before - my Samsung went to a different recovery mode), so I've been researching that more recently.
I got ADB and Fastboot working, erased the cache via Fastboot which stopped the bootloop, but it would only go as far as the logo with the little spinner circle. After messing around with fastboot trying to do a factory reset and put a custom recovery on it (TWRP) it now will only boot to the Asus logo and not even have a spinner anymore!
The flashing of anything - recovery, stock rom from ASUS (this file as I found elsewhere on these forums: UL-P01M-WW-3.3.8.0-user.zip -- although I'm not entirely sure i'm flashing correctly).
Anyway, I'm stuck with only an Asus logo or fastboot mode screen and am not that good with fastboot/adb since I only had to delve into it once to fix my own tablet over a year ago.
If anyone can help that'd be very much appreciated! :good:
Click to expand...
Click to collapse
Asus has the firmware (Nougat) for this Z300M but I've no idea how you would get this loaded. Something to learn but as long as the OS is available you should be able to get back stock, latest OS............
zls
So I think my Nexus 6P is hard bricked, but I just want to be sure before I issue an RMA.
I was on a plane flying over the Pyrenees and opened the camera to take a picture. The phone froze and started rebooting, which I found strange really strange as it never happened before. Since then, it wasn't able to boot again. The phone is completely stock, running 7.0, apart from the unlocked bootloader that I had unlocked the day I bought it (March/April this year). The phone shows the unlocked bootloader warning, goes to the white Google logo with the padlock below, and then goes back to the unlocked bootloader.
From here I can Power + Vol down and get to bootloader, which I thought would leave me to recover the phone somehow. I know my way around nexus devices so the first thing I tried was scrolling in the bootloader menu and boot into stock recovery. No luck, unlocked bootloader warning, white Google logo and loop. Tried "Factory" in the menu and the same thing happens.
So then I've gained access to a computer and tried downloading a twrp recovery and boot into it. Ran fastboot boot twrp.img, the phone tries to boot again, and the same thing happens. Boot loop. After that, I've downloaded the latest stock Google images and I've run a different set of things, all with no luck. Booting directly from fastboot into stock recovery doesn't work. Flashing stock recovery and trying to enter stock recovery via bootloader menu doesn't work. I've erased and flashed bootloader, radio, and all other partitions (system, boot, recovery, vendor and cache), without any luck. The fastboot commands return "OKAY" but it seems like it's doing nothing.
I am out of ideas, I always thought I would be able to recover a Nexus phone as long as I could reach bootloader mode, but I guess I'm wrong. Should I RMA, or is there anything else I should try?
Thank you.
You say you "Ran fastboot boot twrp.img." Try to do fastboot flash recovery twrp.img from fastboot and see if you can get twrp working. Then try to flash a ROM
vladniko said:
You say you "Ran fastboot boot twrp.img." Try to do fastboot flash recovery twrp.img from fastboot and see if you can get twrp working. Then try to flash a ROM
Click to expand...
Click to collapse
Done both, actually. Tried to boot directly from a fastboot command and then tried flashing the actual recovery image to the phone. No luck in both. Never able to get into twrp.
I had the same thing happening to me. I was also using stock 7.0 with an unlocked bootloader. My screen froze during webbrowsing and had to restart the phone. Once booting up, it never came past the Google logo. Getting into recovery didn't work either, just started looping again. Tried to flash twrp, got in there after many tries. Tried flashing all kind of android versions but nothing helped. After that I decided to just use my warrenty and send the phone to the store. They replaced the motherboard and are now sending it back.
hubhib said:
I had the same thing happening to me. I was also using stock 7.0 with an unlocked bootloader. My screen froze during webbrowsing and had to restart the phone. Once booting up, it never came past the Google logo. Getting into recovery didn't work either, just started looping again. Tried to flash twrp, got in there after many tries. Tried flashing all kind of android versions but nothing helped. After that I decided to just use my warrenty and send the phone to the store. They replaced the motherboard and are now sending it back.
Click to expand...
Click to collapse
Yep, I gave up already. Tried all different sort of thing, and was never able to get into any kind of recovery, let alone Android itself.
Called Google support yesterday evening, a replacement is on its way already.
eddie_gordo said:
Yep, I gave up already. Tried all different sort of thing, and was never able to get into any kind of recovery, let alone Android itself.
Called Google support yesterday evening, a replacement is on its way already.
Click to expand...
Click to collapse
Needed the RMA anyways. If you had an unlocked bootloader and formatted each partition and then flashed each partition with the corresponding image file from the latest factory image, it was shot. It happens from time to time. Happened to mine as well. 2 or 3 days after I finally got it (pre ordered on launch) I rebooted the phone at some point 2 or 3 days later and it just never turned back on. 100% bone stock. Not even an unlocked bootloader. Nothing would happen when I plugged it into a PC, left it on AC power for hours and hours and still nothing. Holding power 10-15 seconds, nada. RMA'd and luckily this one's been perfect ever since. Good luck with the new device!
VS995 Unlocked with dirty santa, Konverged kernel, stock rom
The other day phone just randomly shut off without warning, battery was low (5%) so I figured battery just died. Went to plug phone in, got to the "device cannot be trusted" screen and to the LG screen, screen goes black, and gives me this yellow "RPM Crash" screen (see below). I can boot into fastboot just fine, and up until just a few minutes ago I was able to boot into twrp by flashing my twrp image as boot and rebooting the phone (if I use the button method it gives me the factory reset screens, goes to the lg screen, and goes back to the crash screen). I can reboot to recovery from twrp and it works just fine. Booting into download mode shows the download mode icon for a few seconds and then it goes black and to the crash screen.
Issues found/fixed so far
I saw in another thread someone had a boot.img issue so I messed with the boot1 and boot2 imgs from the dirty santa process and managed to get to a looping verizon screen with boot1 and the encryption unsuccessful screen with the boot2.img
In twrp my data and dalvik partitions were corrupted but I was able to reformat and repair them. (I found out when trying to wipe them in fastboot)
In fastboot, after working in twrp I was able to wipe and reflash all partitions except system I extracted from a kdz with no luck as far as getting past the error.
My system partition is currently wiped and I have not flashed a new system.img as fastboot won't let me flash it and I cannot get back into twrp to flash it.
I'm curious if this is more of a hardware fault than it is a software fault as download mode was also affected
Thoughts? Suggestions?
spalding1028 said:
VS995 Unlocked with dirty santa, Konverged kernel, stock rom
The other day phone just randomly shut off without warning, battery was low (5%) so I figured battery just died. Went to plug phone in, got to the "device cannot be trusted" screen and to the LG screen, screen goes black, and gives me this yellow "RPM Crash" screen (see below). I can boot into fastboot just fine, and up until just a few minutes ago I was able to boot into twrp by flashing my twrp image as boot and rebooting the phone (if I use the button method it gives me the factory reset screens, goes to the lg screen, and goes back to the crash screen). I can reboot to recovery from twrp and it works just fine. Booting into download mode shows the download mode icon for a few seconds and then it goes black and to the crash screen.
Issues found/fixed so far
I saw in another thread someone had a boot.img issue so I messed with the boot1 and boot2 imgs from the dirty santa process and managed to get to a looping verizon screen with boot1 and the encryption unsuccessful screen with the boot2.img
In twrp my data and dalvik partitions were corrupted but I was able to reformat and repair them. (I found out when trying to wipe them in fastboot)
In fastboot, after working in twrp I was able to wipe and reflash all partitions except system I extracted from a kdz with no luck as far as getting past the error.
My system partition is currently wiped and I have not flashed a new system.img as fastboot won't let me flash it and I cannot get back into twrp to flash it.
I'm curious if this is more of a hardware fault than it is a software fault as download mode was also affected
Thoughts? Suggestions?
Click to expand...
Click to collapse
I have a H910 that just received a screen replacement and I am also getting the yellow error screen. I am still able to get into Twrp though. However no matter how many times I flash a Rom, it keeps getting stuck at the yellow screen.
ozymandiasmusic said:
I have a H910 that just received a screen replacement and I am also getting the yellow error screen. I am still able to get into Twrp though. However no matter how many times I flash a Rom, it keeps getting stuck at the yellow screen.
Click to expand...
Click to collapse
Can you take a picture of of the screen, or is it identical to the one that has been posted? My guess is that you put the wrong screen on.
-- Brian
runningnak3d said:
Can you take a picture of of the screen, or is it identical to the one that has been posted? My guess is that you put the wrong screen on.
-- Brian
Click to expand...
Click to collapse
Here is the photo, sorry it's not the best quality since it's taken with a OnePlus One.
I had gotten the screen replaced by a cell phone repair shop. Luckily they still gave me the original screen. If it's a bad screen I will just get them to switch it out again...
You will have to upload a better quality picture for me to be sure, but I can tell you that you are getting an selinux failure for some reason when it is trying to load some driver. Again, I need a better picture.
-- Brian
runningnak3d said:
You will have to upload a better quality picture for me to be sure, but I can tell you that you are getting an selinux failure for some reason when it is trying to load some driver. Again, I need a better picture.
-- Brian
Click to expand...
Click to collapse
Sorry for the delay, I had the repair shop reinstall the original screen I was using. I am still getting an error screen, but I have my actual camera with me so here you go. I have tried installing a new ROM, I've tried doing "STEP3.BAT": https://forum.xda-developers.com/v20/how-to/root-h910-v10m-t3664500 Because thought it needed a new boot.img
Still having errors. Any advice would be great. I haven't reverted back to stock because not sure how, and worried I'll lose twrp and would prevent me from actually doing anything.
I have a LG g4 that got the blue screen of death and it won't respond to anything I've tried so I'd say this is the same...........
my lg v20 started displaying this RPM crash screen two days ago. I am not certain what caused it, but it was immediately after charging it with a power bank. To boot mine, I have to plug the phone to a wall charger, once it shows charging, I press the power button and it will boot flawlessly, after that I am free to unplug it. I cant say if it wouldnt degenerate and I havent tried flashing the phone afresh. For now, I would back up my data to avoid surprises.
ozymandiasmusic said:
Sorry for the delay, I had the repair shop reinstall the original screen I was using. I am still getting an error screen, but I have my actual camera with me so here you go. I have tried installing a new ROM, I've tried doing "STEP3.BAT": https://forum.xda-developers.com/v20/how-to/root-h910-v10m-t3664500 Because thought it needed a new boot.img
Still having errors. Any advice would be great. I haven't reverted back to stock because not sure how, and worried I'll lose twrp and would prevent me from actually doing anything.
Click to expand...
Click to collapse
did you try changing the battery?
ozymandiasmusic said:
Sorry for the delay, I had the repair shop reinstall the original screen I was using. I am still getting an error screen, but I have my actual camera with me so here you go. I have tried installing a new ROM, I've tried doing "STEP3.BAT": https://forum.xda-developers.com/v20/how-to/root-h910-v10m-t3664500 Because thought it needed a new boot.img
Still having errors. Any advice would be great. I haven't reverted back to stock because not sure how, and worried I'll lose twrp and would prevent me from actually doing anything.
Click to expand...
Click to collapse
How do you boot into twrp? I am unable to. Are you currently able to copy your files from your internal memory to sd via twrp?
So here is my predicament, I got a warranty Axon 7 replacement. Was going through the procedures to get everything setup. I got everything done and flashed RR. Booted up RR and then hit the "Enter Password Screen", which I remember from my first time the data partition needed to be reformatted with a new file system. Here is where my idiot self screwed up. I accidentally chose the system partition used xfat 4 and now TWRP won't load back up. I have one of those devices where EDL is not longer accessible from the hardware keys, it boots into DFU mode instead.
Things I've tried:
- I've tried getting into EDL mode from fast-boot modifications, It simply reboots normally and the whole system is frozen
- I've tried Re-Flashing TWRP using the Axon 7 Toolkit and it freezes on the TWRP load screen. Any solution to completely re-flash stock software includes getting into EDL mode, which I'm unable to do with the hardware keys. (My old Axon 7 gets into it just fine still)
- (update) Tried to flash a new TWRP image via fastboot as well. It's still frozen on the TWRP load screen.
Things I can do
- Get into Fastboot
- Get to a Twrp loading Screen
- Sit on the ZTE logo or unlocked boot loader screen at startup
If anyone can be of assistance, I'd greatly appreciate it. I really do love this phone! If you need more info just ask, I'm happy to provide it. Generally I figure these things out when I screw up(which has happened more often than I care to admit) but I'm honestly stuck here and at a loss of what to do to fix this issue. If anyone has any suggestions, I'd love your help!
UPDATE/EDIT - I figured out a solution! I pulled a factory Image from the EDL Files and pushed it via fastboot. I'm not back into TWRP! Wahoo!
I replaced my GNEX10 battery last january. Aside from the battery calibration being off... (which eventually corrected itself!) it's been working fine. As of late it had rebooted itself while I was using it a few times. A few days ago, it had enough battery such that I left it on overnight. I picked it up the next morning and the notification lamp was flashing so I knew it was still on. I tried to wake it up without success. Usually a quick tap on the power button should do it. Nothing. So I rebooted... and on the google logo it stuck. I knew that a factory reset was probably in order since I didn't do it when I replaced the batter... I got it into the recovery screen... but I could not get the menu. I likely didn't press the right volume rocker. Then I tried again... booted to the bootloader, and selected recovery. This time, and since, only the google logo comes up. No andy on his back with "no command". It just tries to boot into something. I can't do a factory reset this way.
I tried the Nexus Root Toolkit. I can only get it to recognize the device if it's in the bootloader... when I try to use it to boot to recovery, same thing and the NRT says waiting for device... and gets no further. I tried to use it to flash (stock?) recovery but the N10 just sits there on the twrp logo screen and nothing more after temporarily booting into twrp. Just keeps saying "waiting for device"
Anyone have any suggestions! Getting seriously bummed!
So one more data point... I manually rebooted into the bootloader after trying to flash the stock recovery using the NRT. Then it appeared to flash the recovery image.... here is the bit of the log where it ended up:
Checking Fastboot Connectivity
fastboot devices
R32CB04GHGT fastboot
+ Fastboot Device Connected
Flashing Stock Recovery to RECOVERY partition...
fastboot flash recovery "C:\usr\NRT\data\Recovery_Stock\recovery_stock_mantaray_5.1.1_LMY49J.img"
Temporarily Booting TWRP...
fastboot boot "C:\usr\NRT\data\Recovery_Custom\TWRP\twrp-3.0.2-0-manta.img"
Flashing 'undo-perm-recovery-signed.zip'...
Waiting for your device...
That's where it ended up... not getting any further. Once again, attempting to boot into recovery gets it stuck on the Google logo.
How screwed am I? Is there a thread somewhere in the forum anyone can point me at?
Well, in spite of the crickets... I understand. I've managed to resurrect my Nexus 10. Alas there are no good contemporary replacements. The last so-called nexus table google put out there was too damn expensive in the first place and they seem to have abandoned the tablet market to others.
So the key question here: So long as I can get this tablet into the bootloader is it generally possible to reflash a stock image? I'd like to know of any types of caveats etc. The mystery I have still though is: How or why did my N10 get into this state (of of only being able to get to the Google screen) in the first place? I didn't have any questionable apps installed etc. I was totally on stock. One thing that did happen a week or two prior to my tablet going belly up... was somehow the thing lost my google account info and gmail had none of my accounts in place... it was very odd.
I did have to wipe the system because evidently you can't flash anything onto a locked bootloader (the Nexus Root Toolkit by wugfresh is up to date so far as the N10 is concerned at least). I know I could have resorted to using fastboot.exe and the adb directly but this was a touch easier. Alas the backup options for it say you need an unlocked bootloader which seems to be a chicken/egg issue if you've always been on stock.... so it goes.