I have a custom ROM, but after a few phone drops while watching the kids I have a broken screen. Black and unresponsive. I can still plug it in and recovered all my files. Phone still works. So it's time for a warranty repair.
Using Axon7Toolkit (or any other means), can anyone confirm that I can successfully restore stock + relock without having to touch anything on the screen?
I can boot into TWRP just fine. I just want to make sure I won't end up dead in the water at any point bc there will be something on the screen I can't see or touch "OK" to.
Backup your files and then reflash with edl.
Related
Was checking facebook earlier, it stopped responding and just went to a grey screen. Decided to restart the tablet. Now it's stuck in a bootloop and will not turn on. Tried going into recovery but once I select it, the next screen I get is an android with a red triangle/exclamation point. It won't go into recovery and I'm not sure what to do from here. My laptop won't recognize that I have my tablet plugged in either, fwiw.
Is this thread my only option or did I miss something else? This link sounds complicated, but if it's my only option, I guess I'll give it a shot. http://forum.xda-developers.com/showthread.php?t=1907796&highlight=can+t+boot+into+recovery+mode
It can be anything from hw failure to corrupted data. I guess your tablet is stock, without custom recovery or anything. If this is the case, you should try restoring a stock image by that guide or by using a toolkit, like this one. If you have custom recovery on your tab, you should boot into bootloader and reflash the custom recovery with fastboot, this way your data might be saved.
Completely stock. I'll download Wug tonight after work and give it a try since it seems easier than the link I provided.
I didn't back anything up, but that's okay, I can live with that. Just want to be able to use the tablet again.
Well, got home and decided to give recovery another shot. I got it to wipe all data (was pressing the vol up button for too long earlier), but now when i go to reboot the device, it's just stuck on the X screen.
Any advice on what I should do at this point? Should I still try wug?
Good day, guys. This is my first thread here, and it's safe to say that I'm a total noob when it comes to Nexus devices. This is my second Nexus device, and it's kinda heartbreaking that I accidentally bricked it on the second day of usage. What happened was that I flashed XenonHD ROM on it (did the usual wipes before doing so). It booted successfully, but after that whole finishing start-up screen before going to lockscreen, it reboots and repeats the process. So I attempted to go back to recovery via bootloader (CWM v6.0.4.3) to restore my back-up, but then it just got stuck at the recovery screen without any menus or options for about 2 minutes and then rebooted itself and went back to the same screen (cwm without any menus or options). And now, it's stuck there (the whole process which I now call recovery loop) whenever I power on my device and the only way to shut it off is by pressing and holding the volume up button. PS, I cannot access the bootloader after this happened. Whenever I try to, it just goes to what (from what I've read over and over from a lot of different forums and guides) people call APX mode. But they say that the only way to access that mode is if I press power-volume up simultaneously.
So my question is, is my nexus hard bricked (or any kind of bricked), or do I just need to have the physical button module replaced? If it is bricked, is there anyway I can fix this myself? Is there a process that I need to follow to undo this? I have searched far and wide, but it seems that the only way to unbrick this is if I can access the bootloader and go to fastboot mode, which I cannot at the moment.
Please, someone help me.
I have same problem after flash xenon rom.
Sent from my C5303 using XDA Premium 4 mobile app
I think as long as you can't access the boot loader then you are up a creek. You are not powering off by pressing vol up you are entering apx mode the fact that you are getting apx mode and not the bootloader tells me you have a corrupted bootloader. Your nexus is dead and I'm sorry for your loss. I'm not sure what has caused this I think you have just been unfortunate. The only way to revive your nexus is either if you had backed up the bootloader using the nv flatline procedure but I think its clear you haven't the other option is a new motherboard they are not too expensive on ebay
Sent from my C5303 using XDA Free mobile app
Since we do not have a dedicated forum for HP Slate 7 Extreme, I am posting here.
I need to restore my tablet back to factory so I can warranty it back due to a failing back light/screen (It flickers in various bars up/down the screen in random places), but am having trouble with two things - I cannot get the stock recovery back on the device, it is now stuck at "No Command" when I attempt to enter recovery mode. I then tried to manually write it to the device with Fastboot, but no matter what I try, I cannot get Fastboot to load up from the bootloader. It simply reloads the bootloader. I have not been able to super su the device either after applying the factory restore image from HP.
I previously loaded up the Tegra Note 7 Rom on this device which is where it ran perfectly up until this point.
Does anyone have a fix for this so I can get back into the fastboot so I can restore the recovery kernel? And....
Does anyone know how to relock the bootloader so I can get rid of the voided warranty flag?
Anybody???
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?
when reinstalling a ROM earlier today, I got an error 7 ... no problem. probably TWRP problems... so, i go to reboot phone to recovery to begin fresh, and now, TWRP boots, but the screen flashes blank every couple seconds, for a second, then the TWRP splash screen comes back up. blank screen, then TWRP splash screen again. never gets further than that. because I dont have an OS installed, i cannot access debugging for adb. because i deleted my OS, i cannot allow fastboot, to flash a new recovery and begin again. ..
I am broke, and cannot afford to pay for a new replacement thru insurance or to just go buy a junker phone and make do with that.
am i ****ed, or is this recoverable...? ive been searching the forums, but cannot seem to find the answer, and im starting to get nervous enough that its sorta beginning to compound my problems more than i can deal with.
edited to add again: .... battery removed + volume dn then insert battery will not enter fastboot. im about to paperweight this ****.
again edited - Sprint LS997 is phone model. no TOT'ing for me.
What about if you remove the battery, put it back in, hold volume down and then plug the usb cable?
XblackdemonX said:
What about if you remove the battery, put it back in, hold volume down and then plug the usb cable?
Click to expand...
Click to collapse
tried this. still a no-go. phone screen does not power on when trying this or any other combo of steps. LAF works, which is vol+ and plug in USB cable. odd that vol- and plug in USB cable does nothing. maybe faulty vol+ button? never had a problem with that button functioning before now. i have access to: LAF (download mode), and TWRP. However, TWRP 'flashes' off n on... i see the splash screen for a second, then screen goes blank, but still powered on. then splash screen again. rinse, and repeat. no response to touch or vol/pwr buttons. tried pulling battery upon TWRP splash hoping this clears cache, but still just same story afterwards.
would having access to fastboot even matter, since I have no OS install with which to give fastboot/adb access anyway?
elijah420 said:
would having access to fastboot even matter, since I have no OS install with which to give fastboot/adb access anyway?
Click to expand...
Click to collapse
From fastboot you can reflash TWRP which from where you can reflash the OS which would unbrick the phone.
elijah420 said:
i have access to: LAF (download mode)
Click to expand...
Click to collapse
If you have access to download mode, can't you reflash your phone using the LGUP with the backup that did in the first place?(you did a backup of the original OS right?)
elijah420 said:
tried this. still a no-go. phone screen does not power on when trying this or any other combo of steps. LAF works, which is vol+ and plug in USB cable. odd that vol- and plug in USB cable does nothing. maybe faulty vol+ button? never had a problem with that button functioning before now. i have access to: LAF (download mode), and TWRP. However, TWRP 'flashes' off n on... i see the splash screen for a second, then screen goes blank, but still powered on. then splash screen again. rinse, and repeat. no response to touch or vol/pwr buttons. tried pulling battery upon TWRP splash hoping this clears cache, but still just same story afterwards.
would having access to fastboot even matter, since I have no OS install with which to give fastboot/adb access anyway?
Click to expand...
Click to collapse
Sounds like empty or bad battery to me. When did your phone start acting up upon ya? Right after root or you had it working with root etc before u ended up into such situation.
Also, as XblackdemonX pointed out, you can still use LGUP to stock.
I'm pretty sure that happened to me. And I fixed my H990DS by flashing kdz file in download mode with LG BRIDGE.
There's a guide about how to unbrick any v20 around here.
@elijah420 What software version were you on before this started? Why does it matter? If you were on ZV7 or earlier, then you can flash a VS995 KDZ in download mode, root it, and then fix your phone. If you were on ZV8 or later, then you still might be able to salvage your phone, but you will have to run firmware from another model since you will not be able to root and flash back to Sprint firmware if you were ARB 1 or later. Better than having a totally busted phone though.
Last possibility is to use the debug firehose that I have, but that is an even bigger unknown than running firmware from another model.
-- Brian