I have a bricked Nokia 6 here. Chinese variant. Ta-1000.
It doesnt start up.
The screen keeps flashing an image of a broken Android and the text "No Command".
The screen doesnt stay on that image. Keeps flashing between black and that image.
It had the Oreo Beta on it before.
Is there a way to reflash it?
IndigoHD said:
I have a bricked Nokia 6 here. Chinese variant. Ta-1000.
It doesnt start up.
The screen keeps flashing an image of a broken Android and the text "No Command".
The screen doesnt stay on that image. Keeps flashing between black and that image.
It had the Oreo Beta on it before.
Is there a way to reflash it?
Click to expand...
Click to collapse
The flashing screen I suspect is the standard recovery.
If yes, then you may see some text on the screen.
If no, maybe use ADB or fastboot to reinstall the standard firmware.
wong.izzat said:
The flashing screen I suspect is the standard recovery.
If yes, then you may see some text on the screen.
If no, maybe use ADB or fastboot to reinstall the standard firmware.
Click to expand...
Click to collapse
I was trying to reflash with OST LA 6.1.2., which always crashes when trying to reflash.
How would i go about using ADB or fastboot to reflash?
Related
I have a Verizon LG G2 I tried to flash my backed up stock recovery with Flashify so I could flash the most recent OTA. After accepting the OTA update my phone restarted, tried to install the update, hung at a black screen but was still turned on. If I power it off and back on it shows the LG logo, some white text, then goes to the same black screen. What appears to be happening is that my backup recovery did not restore properly and it's hanging when it tries to go into recovery. It's almost like my recovery partition is blank.
I've tried to follow the instructions to flash back to stock, but I do not believe I'm actually able to get my phone into download mode. When it is plugged into my windows 7 computer with the LG drivers installed it shows up in device manager as QHSUSB_BULK.
Is there any way for me to push a stock recovery, or even a custom recovery to my phone so I can somehow salvage it, or am I permanently bricked?
toopty said:
I have a Verizon LG G2 I tried to flash my backed up stock recovery with Flashify so I could flash the most recent OTA. After accepting the OTA update my phone restarted, tried to install the update, hung at a black screen but was still turned on. If I power it off and back on it shows the LG logo, some white text, then goes to the same black screen. What appears to be happening is that my backup recovery did not restore properly and it's hanging when it tries to go into recovery. It's almost like my recovery partition is blank.
I've tried to follow the instructions to flash back to stock, but I do not believe I'm actually able to get my phone into download mode. When it is plugged into my windows 7 computer with the LG drivers installed it shows up in device manager as QHSUSB_BULK.
Is there any way for me to push a stock recovery, or even a custom recovery to my phone so I can somehow salvage it, or am I permanently bricked?
Click to expand...
Click to collapse
I have the same exact problem. exactly the same. mine doesnt even show up for download mode. this sucks!
cgillie92 said:
I have the same exact problem. exactly the same. mine doesnt even show up for download mode. this sucks!
Click to expand...
Click to collapse
I'm still trying to find a solution I will post here if i have any luck. I've dug through a lot of forum posts and I think what makes us unique is the fact that we have a corrupt or blank recovery partition.
toopty said:
I'm still trying to find a solution I will post here if i have any luck. I've dug through a lot of forum posts and I think what makes us unique is the fact that we have a corrupt or blank recovery partition.
Click to expand...
Click to collapse
Ive looked through a lot too. and its crazy how that would happen i made sure it was rebooting correctly before i took the ota and then when i did the ota bam! only screens i can get to come up are the hardware key control mode and the factory hard reset which both go to white screens after I do them both. every one else probably has not taken the ota.
cgillie92 said:
Ive looked through a lot too. and its crazy how that would happen i made sure it was rebooting correctly before i took the ota and then when i did the ota bam! only screens i can get to come up are the hardware key control mode and the factory hard reset which both go to white screens after I do them both. every one else probably has not taken the ota.
Click to expand...
Click to collapse
One difference in what mine is doing and what your phone is doing. I go to a solid black screen not a white screen. It's very hard to tell my phone is even turned on. I'm having to look if the back-light to verify if it's on or not. I can hold my power button for 10 seconds through one LG logo cycle and then it turns off.
toopty said:
One difference in what mine is doing and what your phone is doing. I go to a solid black screen not a white screen. It's very hard to tell my phone is even turned on. I'm having to look if the back-light to verify if it's on or not. I can hold my power button for 10 seconds through one LG logo cycle and then it turns off.
Click to expand...
Click to collapse
I hope someone helps us out. I really cant afford a new one because the warranty is void. I was going back to stock because of all of the little bugs that need to be ironed out in roms. cause kit kat is around the corner hopefully and my problem virtually is the same i might have had my brightness on auto or something prior to that.
Foolow this tutorial to get your phone back.
http://forum.xda-developers.com/showthread.php?p=48765620
Partager.info said:
Foolow this tutorial to get your phone back.
http://forum.xda-developers.com/showthread.php?p=48765620
Click to expand...
Click to collapse
Thanks for the link. I'm tryingto follow the instructions,but when I get to the step where i plug in my phone it just showes up as a bunch of failes partitions, and slows my ubuntu to a crawl. I'm a linux noob, is there a command i can run to stop this from happening? I also created a reply asking this question in the link you sent me.
Thanks for the help.
Partager.info said:
Foolow this tutorial to get your phone back.
http://forum.xda-developers.com/showthread.php?p=48765620
Click to expand...
Click to collapse
After following the instructions on the above link i was able to get fastboot status on my phone. It did not fully restore my phone however. I was able to flash twrp via fastboot. I was then able to boot into twrp and run the command at this link via twrp terminal http://forum.xda-developers.com/showthread.php?t=2451696
Thanks to everyone for all your help.
toopty said:
Thanks for the link. I'm tryingto follow the instructions,but when I get to the step where i plug in my phone it just showes up as a bunch of failes partitions, and slows my ubuntu to a crawl. I'm a linux noob, is there a command i can run to stop this from happening? I also created a reply asking this question in the link you sent me.
Thanks for the help.
Click to expand...
Click to collapse
How did you get past the ubuntu slowing down? I cant win for ubuntu freezing due to all of the failed partitions either so close but yet so far =/
cgillie92 said:
How did you get past the ubuntu slowing down? I cant win for ubuntu freezing due to all of the failed partitions either so close but yet so far =/
Click to expand...
Click to collapse
Ignore all the message, unplug you phone get ready to type the command, plug it in and immediately press enter to run the command. it took some trial and error, and i had to use this other post to help me out. I actually got fastboot working first, then used this post to http://forum.xda-developers.com/showthread.php?t=2477595 to get download mode working, and to flash twrp recovery. After that i used this post to run the command line from with twrp. http://forum.xda-developers.com/showthread.php?t=2451696 . I didn't have to flash the factory tot to my phone, but i have that option now because download mode is working. This process will work, there is hope for you getting your phone back. I'm fully recovered. I decided 12B is not worth it in the mean time, but if you want 12B you need to flash the factory tot and then upgrade. There is a way to root 12B, but as of this time you are unable to get Custom Recovery on it.
Was having issues with my Nexus 7(2013) this morning, rebooted the device and now it gets stuck at the "Google" loading screen.
I can get into the Fastboot loader. I was able to unlock the bootloader.. I have LOCK STATE - unlocked and the unlocked lock showing up on the "Google" boot screen.
I am UNABLE to get into Recovery mode.. either by selecting "Recovery mode" in Fastboot or holding the power and vol up buttons. It just sits on the "Google" boot screen.
I have downloaded and installed the SkipSoft Android Toolkit(mskip).. very nice toolkit BTW. But no matter what I do I'm unable to start the tablet up normally or get into a Recovery mode of any kind.
I have tried to flash TWRP. I have tried to flash the stock ROM. Nothing, still sits at the Google boot screen. Since flashing the stock ROM its been 30 min and still just says "Google".
I'm open to any ideas or anything that you can think of.
Still have TWRP and fastboot access? If so, use the command line fastboot the img using
"fastboot boot <filename>.img"
Reply back; do you get to recovery?
Snuzzo said:
Still have TWRP and fastboot access? If so, use the command line fastboot the img using
"fastboot boot <filename>.img"
Reply back; do you get to recovery?
Click to expand...
Click to collapse
No.. I do not get into recovery of any kind. Stock or TWRP after loading it.. just sits at the Google screen.
Quick question; what were your partition setups like? F2fs? Ext4?
Snuzzo said:
Quick question; what were your partition setups like? F2fs? Ext4?
Click to expand...
Click to collapse
No idea.. it should be whatever it is stock. Before today I never rooted, flashed or did anything to this device.
FDokinawa said:
No idea.. it should be whatever it is stock. Before today I never rooted, flashed or did anything to this device.
Click to expand...
Click to collapse
Answers all of my questions. I know myself I won't be able to help. All I can say is to try relocking and then unlocking again.
Snuzzo said:
Answers all of my questions. I know myself I won't be able to help. All I can say is to try relocking and then unlocking again.
Click to expand...
Click to collapse
Thanks for the help.. will give it a shot.
FDokinawa said:
Thanks for the help.. will give it a shot.
Click to expand...
Click to collapse
What that should do is wipe internal, could have some corruption there. Try doing the command line fastboot of the recovery.img again. Those are the only few things I can think of short from exercising your warranty.
Snuzzo said:
What that should do is wipe internal, could have some corruption there. Try doing the command line fastboot of the recovery.img again. Those are the only few things I can think of short from exercising your warranty.
Click to expand...
Click to collapse
Dont think I can use the warranty.. bought it used(1 hour old) from a friend for $100.. he got it and then decided he didnt like the aspect ratio. His loss, my gain. Until now.. lol
I'll keep hacking at it.. thanks again.
Anytime! You're welcome!
So the original issue I was having was that the screen was not responding to touches. Was unable to slide the unlock button on the screen.
I was able to "Boot to Custom/Stock Recovery without Permanently Flashing it" via SkipSoft Toolkit.. and had TWRP load up. But like before it was not responding to touches.
Starting to think this thing is totally borked.. =/
I'm able to get into TWRP now.. but sits on boot animation screen now. one step forward. Going to try and reload the stock ROM again and see if that helps.
That seemed to work.. at the Welcome screen.
So if anyone else runs into something like this..
Issues:
Flakey touch screen
Stuck on Google bootup screen
Eventually stuck boot loop animation
Get SkipSoft Android Toolkit, donate a couple bucks and keep flashing anything and everything you can. Sorry I can't give you a specific order that works. I would say try the 'ALLINONE'(#8) option first and then download and flash the stock ROM. I did several things in the toolkit a few times over and over. Hopefully I'm good now, if not I will update.
Have you tried reflashing recovery via fastboot?
Exact thing happend to my n4.
Sent from my N⁴ using Android Lollipop by @Sykopompus running Unleased kernel by @DeFcOni
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?
I do not have a great track record when flashing ROMS etc on LG devices..
Today I decided to flash my device back to total stock in prep for the incoming Oreo update and also the dreadful battery life i've been experiencing.
I tried using LGUP first but found that once the device completed it's boot, it got to the 'Android is starting' screen before rebooting.. It did this a few times before I turned it off and booted it into download mode.
I then used LG bridge and flashed everything directly through the Bridge software - This was successful however when it boots it is now doing the same thing.
It will show the boot animation, flash very quick the 'Android is updating/booting/upgrading' white screen before rebooting, showing 'erasing' very quickly then showing the boot animation again.
What am I missing here? Why is this happening?
For some reason flashing stock bricks the phone just factory reset it though the recovery. Tell me did you succeed...
ZinX09 said:
For some reason flashing stock bricks the phone just factory reset it though the recovery. Tell me did you succeed...
Click to expand...
Click to collapse
So yes, I managed to resolve this somehow.
As I managed to get into fastboot mode, reflashed TWRP and formatted the data partition - reflashing via bridge tool causes the same issue again and I only managed to get eh device to boot after I accidentally booting into safemode and allowing the device to finish optimising. Rebooting into normal mode then worked just fine.
adaimespechip said:
So yes, I managed to resolve this somehow.
As I managed to get into fastboot mode, reflashed TWRP and formatted the data partition - reflashing via bridge tool causes the same issue again and I only managed to get eh device to boot after I accidentally booting into safemode and allowing the device to finish optimising. Rebooting into normal mode then worked just fine.
Click to expand...
Click to collapse
I meant for you to reset through the stock recovery but i guess that works as well.
ZinX09 said:
I meant for you to reset through the stock recovery but i guess that works as well.
Click to expand...
Click to collapse
Oh I see, sorry.. I couldn't get into stock recovery - it would simply erase the device and reboot each time. That was part of the problem..
adaimespechip said:
Oh I see, sorry.. I couldn't get into stock recovery - it would simply erase the device and reboot each time. That was part of the problem..
Click to expand...
Click to collapse
Hello i have the same problem how to fix it showing erarsing for sek and that's it.
Mercz23 said:
Hello i have the same problem how to fix it showing erarsing for sek and that's it.
Click to expand...
Click to collapse
Have you tried to boot to the stock recovery and factory reset it the phone.
same problem here, how did you boot safe mode??
My phone is stuck on the screen with the big orange exclamation point after trying to flash using fastboot boot twrp-3.3.1-1-fajita.img and now I can't get anything to get it to turn on. Is there a way to fix this?
AliMusa said:
My phone is stuck on the screen with the big orange exclamation point after trying to flash using fastboot boot twrp-3.3.1-1-fajita.img and now I can't get anything to get it to turn on. Is there a way to fix this?
Click to expand...
Click to collapse
Shut down your phone, download msm tool and go to wipe it using it. Will make your phone go to a locked bootloader state with stock Android version
AliMusa said:
My phone is stuck on the screen with the big orange exclamation point after trying to flash using fastboot boot twrp-3.3.1-1-fajita.img and now I can't get anything to get it to turn on. Is there a way to fix this?
Click to expand...
Click to collapse
I know this doesn't help you now but the version of TWRP that you flashed is not compatible with Android 10. You have to use the latest unofficial builds from mauronofrio.
Actually, you can exit that mode and force reboot with pushing 3 buttons simultaneously until it reboots.