Related
I've unlocked/rooted/flashed many Android devices in the past, including many Nexus devices. I've run into some problems here and there, but I've always been able to get around them. This time seems to be different, so far anyway.
I started with the WugFresh Nexus Root Toolkit - I know how to do it manually but this just has everything included, the drivers, adb.exe, fastboot.exe, etc.
I told it to unlock the tablet, and it rebooted the device into Fastboot. The tablet asked me if I wanted to unlock it and I said yes. Then, NRT booted me into TWRP and gave me instructions to do a factory reset from TWRP (a step I've never had to do manually before). I tried to factory reset but TWRP told me it failed. Weird. Anyway, I decided to reboot the device from TWRP and see what happened.
All I see is the swirly, colourful "X" logo forever. It never boots into Android. I can reboot by holding down the power button, and I can get into fastboot by holding down the power button with Vol-. In Fastboot, I only have the "start" option (which works, but never gets past the "X"). I can't use the volume keys to select "recovery", etc.
From Fastboot, my computer does not show the tablet under "fastboot devices" in the command prompt. It does, however, show my (working) nexus 4 in fastboot devices.
So, without working android, I can't use ADB. Without fastboot connecting with fastboot.exe, I can't push through recovery. Without a working fastboot menu on the physical device, I can't try to go into whatever recovery is there or whatever.
And worst of all, at this stage I can't even turn my device off. It's just sitting here either in the fastboot menu or with the colourful "X". It's just sitting in its original box getting warm and using up its battery.
Any ideas? This is supposed to be a present for my wife for tomorrow - I don't really want to give it to her like this.
Just used wug's kit to root my second nexus device. Both times, it said failed during the factory reset. Wierd.
Put it in bootloader mode by pressing BOTH volume keys and power. There you should see the arrows and you can go to recovery but you shouldn't have a recovery installed yet. Instead, use the wugkit to download and flash a system image, hit the flash stock + unroot button. I also had to do that on both devices for some reason. After it flashes, your bootloader will remain unlocked and you will have a clean, bootable 4.2.2 rom. Then you can root from there.
---------- Post added at 10:29 PM ---------- Previous post was at 10:26 PM ----------
Sorry I may have misread. If you are already in fastboot mode and your having a problem with your computer recognizing it, check your device manager for an uninstalled item, either adb something or android something. Then just follow the instructions in the toolkit to install the drivers. But try the flash and unroot button first and see what the toolkit says.
Same thing happened to me but luckily I had found this video before I started the unlock, root process.
Watch: https://www.youtube.com/watch?feature=player_embedded&v=T1Se7Hr9Cww
Seeing this guy missing getting the proper recovery menu really helped in understanding that it can be tricky.
I took the sage advise of others and did all the manual steps to unlock and root (no toolkit). The following link below is super whether your N10 is on Android 4.2.1 or 4.2.2 with instructions for Linux, OSx and Windows. Includes videos and pictures:
http://nexus10root.com/nexus-10-root/how-to-root-nexus-10-easiest-method/
hlaalu said:
Just used wug's kit to root my second nexus device. Both times, it said failed during the factory reset. Wierd.
Put it in bootloader mode by pressing BOTH volume keys and power. There you should see the arrows and you can go to recovery but you shouldn't have a recovery installed yet. Instead, use the wugkit to download and flash a system image, hit the flash stock + unroot button. I also had to do that on both devices for some reason. After it flashes, your bootloader will remain unlocked and you will have a clean, bootable 4.2.2 rom. Then you can root from there.
---------- Post added at 10:29 PM ---------- Previous post was at 10:26 PM ----------
Sorry I may have misread. If you are already in fastboot mode and your having a problem with your computer recognizing it, check your device manager for an uninstalled item, either adb something or android something. Then just follow the instructions in the toolkit to install the drivers. But try the flash and unroot button first and see what the toolkit says.
Click to expand...
Click to collapse
Hey mate, just wanted to say thanks. I don't know what is was that made the difference in the end, but your suggestion to use both Vol+ and Vol- together with power did the trick. I got it all working brilliantly now, thanks to you.
I'm still so confused. Why does Vol- and Power get into fastboot that doesn't work? I've never seen this behaviour on a Nexus device, or any Android device in general. It's wrapped up in a box ready to be given away in a few hours - but I will have a play with this fastboot because it's certainly weird. Definitely not like my Nexus 4 or 7.
Big thanks again. Hours of pulling my hair out and you saved me!
I believe the reason is the volume buttons are reversed. So when you think your pressing vol- your really doing vol+ lol.. That's what I did. Vol+ + power = download mode and it won't do anything from your computer. J think its an Odin mode.
Also for future reference you cannot unlock, and then use TWRP to do a factory reset. You will get a cache error. The only way it works the first time is to unlock, wipe through stock recovery, flash twrp and boot to success. But have to complete 1 boot before changing your ROM.
I've gone through multiple N10's and each of them had this behavior, I think its a bootloader bug since unlocking the device is supposed to perform a factory reset automatically.
Sent from my Nexus 10 using Tapatalk HD
Glad you're up and running!
Sent from my Galaxy Nexus using Tapatalk 2
I just bought a wileyfox storm, then I followed the process to flash custom recovery and root the phone which done successfully.
After while I got an error massage and the desktop wont show up although I was able to access settings from status bar.
so I made a factory reset from recovery but didnt work
then downloaded the kipper rom from cyanogen but it wont pass the verification, it keep saying this is a crackling phone
So I downloaded the crackling rom for The SWIFT version and from recovery mode I flashed its zip file successfully,(PASSED THE VERIFICATION), then flashed supersu.zip.
I pressed reboot system
It shaut down but never come back to life, the only thing that works is the charging notification red light
Please Help
1- turn off your phone
2- plug it on pc with vol + pressed
3- now type on cmd "fastboot devices" normaly it appear
4- if you haven't unlocked bootloader unlock it with the command "fastboot oem unlock"
5- download cyanogen recovery from cyanogenmod site !!AND CHECK IF WRITEN RECOVERY FOR KIPPER!!
6- flash it via fastboot, type in cmd "fastboot flash recovery cyanogenmod-recovery-kipper.img
And wait
7- now type fastboot reboot
And press vol - during the reboot
8- now you're in cyanogen recovery, so flash the ROM and do not forget to wipe
bobslesbricoleurs said:
1- turn off your phone
2- plug it on pc with vol + pressed
3- now type on cmd "fastboot devices" normaly it appear
4- if you haven't unlocked bootloader unlock it with the command "fastboot oem unlock"
5- download cyanogen recovery from cyanogenmod site !!AND CHECK IF WRITEN RECOVERY FOR KIPPER!!
6- flash it via fastboot, type in cmd "fastboot flash recovery cyanogenmod-recovery-kipper.img
And wait
7- now type fastboot reboot
And press vol - during the reboot
8- now you're in cyanogen recovery, so flash the ROM and do not forget to wipe
Click to expand...
Click to collapse
Appretiate your kind response
Unfortunatly, this wont work for my case, I think I need a way to unbrick the phone, cant access to fast boot, my pc can see the phone only as CUALCOMM chip.
What's OS you're using?
bobslesbricoleurs said:
What's OS you're using?
Click to expand...
Click to collapse
Windows 7 X64
Did you install fastboot driver?
---------- Post added at 01:32 PM ---------- Previous post was at 01:31 PM ----------
Try to press vol + and vol - and power, tell if it vibrate?
bobslesbricoleurs said:
Did you install fastboot driver?
---------- Post added at 01:32 PM ---------- Previous post was at 01:31 PM ----------
Try to press vol + and vol - and power, tell if it vibrate?
Click to expand...
Click to collapse
Sir, I really appreciate your concern, but believe me it's a hard brick case, so I cant access any usual boot neither fastboot nor recovery.
I wish someone tells me how to unbrick it.
Plug usb and try two vol button in same time, tell me if vibrate, if not let it charge during 1 hour and retry
bobslesbricoleurs said:
Plug usb and try two vol button in same time, tell me if vibrate, if not let it charge during 1 hour and retry
Click to expand...
Click to collapse
Nothing happened, even after recharging
There is a probleme, you've just flashed the swift ROM, not really a reason to brick...
And the swift have same partition like the storm.
Where do you live? Me in france
bobslesbricoleurs said:
There is a probleme, you've just flashed the swift ROM, not really a reason to brick...
And the swift have same partition like the storm.
Where do you live? Me in france
Click to expand...
Click to collapse
I'm in Egypt
When i googled my problem i found the same happend with oneplus one phones,
The problem was hard brick due to wrong rom, and windows can see the phone only as Cualcomm hs-usb Qdloader 9008, same as my case. And the problem solved for the oneplus one, so I have some hope that my phone will come back to life.
kazparoph said:
I'm in Egypt
When i googled my problem i found the same happend with oneplus one phones,
The problem was hard brick due to wrong rom, and windows can see the phone only as Cualcomm hs-usb Qdloader 9008, same as my case. And the problem solved for the oneplus one, so I have some hope that my phone will come back to life.
Click to expand...
Click to collapse
Good news, if your problem is solved please post how you do on this thread or new to explain the tutoriel
bobslesbricoleurs said:
Good news, if your problem is solved please post how you do on this thread or new to explain the tutoriel
Click to expand...
Click to collapse
Ofcourse I will.
bobslesbricoleurs said:
Did you install fastboot driver?
---------- Post added at 01:32 PM ---------- Previous post was at 01:31 PM ----------
Try to press vol + and vol - and power, tell if it vibrate?
Click to expand...
Click to collapse
Hi I have a similar problem, I installed the correct cyanogenmod and recovery and it was working fine, but after today's update it shows the bootup logo and then gets stuck in a black flickering screen.
I can't seem to be able to boot neither to the recovery nor to the fastboot mode, no volume key combination seems to work.
All adb says is the device is unauthorized and fastboot doesn't seem to be able to even see the device.
I tried the vol+ and vol- and power and it does vibrate, if I use the vol+ only it seems to get stuck forever on the vendor's bootup logo and the device doesn't seem to be seen neither from fastboot nor adb.
Is there anything else I can try to unbrick it or is it gone?
Thank you in advance for your help
kazparoph said:
I just bought a wileyfox storm, then I followed the process to flash custom recovery and root the phone which done successfully.
After while I got an error massage and the desktop wont show up although I was able to access settings from status bar.
so I made a factory reset from recovery but didnt work
then downloaded the kipper rom from cyanogen but it wont pass the verification, it keep saying this is a crackling phone
So I downloaded the crackling rom for The SWIFT version and from recovery mode I flashed its zip file successfully,(PASSED THE VERIFICATION), then flashed supersu.zip.
I pressed reboot system
It shaut down but never come back to life, the only thing that works is the charging notification red light
Please Help
Click to expand...
Click to collapse
wow, exact same thing, kept saying my device is a crackling device so i flash a crackling rom, it went dead flash!
Please stop flashing crackling roms on kipper.
If it reports crackling is wrong maybe ota somehow messed up.
kazparoph said:
I just bought a wileyfox storm, then I followed the process to flash custom recovery and root the phone which done successfully.
After while I got an error massage and the desktop wont show up although I was able to access settings from status bar.
so I made a factory reset from recovery but didnt work
then downloaded the kipper rom from cyanogen but it wont pass the verification, it keep saying this is a crackling phone
So I downloaded the crackling rom for The SWIFT version and from recovery mode I flashed its zip file successfully,(PASSED THE VERIFICATION), then flashed supersu.zip.
I pressed reboot system
It shaut down but never come back to life, the only thing that works is the charging notification red light
Please Help
Click to expand...
Click to collapse
Have you tried to hold together for about 20 seconds the power button and sound button less ?
Strugglin
I have same problem, either stuck in bootloop (to the wileyfox screen and back to black) or just off. ONLY red charger light shows when I plug it in. Fastboot not working, recovery boot not working... NOTHING is working. On top of that I haven't even installed any roms, not rooted etc. All I did was reboot when it froze on a silly game I didn't mean to open WTFF
wileyfox dead
I have the same problem, bootloop, qualcomm 9008 no fastboot or adb recognition. I'm guessing was the OTA update cos I didn't install any roms at all. TOTAL waste of money, zero support too. It's a non-starter DO NOT BUY!!!!
maxxie00 said:
Hi I have a similar problem, I installed the correct cyanogenmod and recovery and it was working fine, but after today's update it shows the bootup logo and then gets stuck in a black flickering screen.
I can't seem to be able to boot neither to the recovery nor to the fastboot mode, no volume key combination seems to work.
All adb says is the device is unauthorized and fastboot doesn't seem to be able to even see the device.
I tried the vol+ and vol- and power and it does vibrate, if I use the vol+ only it seems to get stuck forever on the vendor's bootup logo and the device doesn't seem to be seen neither from fastboot nor adb.
Click to expand...
Click to collapse
Same here , interesting is the different device status between linux and windows,
at debian it's "offline" - at windows "unauthorized".
I went to factory reset my completely stock and never rooted Nexus 10. It rebooted in to recovery and started "Erasing". It did this for a few hours. If I power it down, it will power back up and go right back to "Erasing" and never erase. If I hold power and volume up on this Erasing screen, I can see "Erasing /data", but it never shows any other status. I cannot boot in to recovery, it will only go to the Erasing screen - I never get the recovery menu. I can boot in to fastboot, but I cannot get the fastboot cli program to recognize the device. I've tried installing drivers for it multiple ways with no success. I figure if I can get in to fastboot I should be able to fix this device, but I'm stuck. Can anyone help?
No one can help here?
ganiman said:
I went to factory reset my completely stock and never rooted Nexus 10. It rebooted in to recovery and started "Erasing". It did this for a few hours. If I power it down, it will power back up and go right back to "Erasing" and never erase. If I hold power and volume up on this Erasing screen, I can see "Erasing /data", but it never shows any other status. I cannot boot in to recovery, it will only go to the Erasing screen - I never get the recovery menu. I can boot in to fastboot, but I cannot get the fastboot cli program to recognize the device. I've tried installing drivers for it multiple ways with no success. I figure if I can get in to fastboot I should be able to fix this device, but I'm stuck. Can anyone help?
Click to expand...
Click to collapse
I know the Nexus 10 takes longer to do stuff like that than other devices but I have never had it stuck on erasing for hours. If you hold down the power button long enough, will it reboot? If you can time it right, you should be able to hold the Power + Volume up + Volume down and hopefully get into the recovery. I think it has to be all three buttons. Not just Volume up. At least that takes me to the bootloader screen.
jsgraphicart said:
I know the Nexus 10 takes longer to do stuff like that than other devices but I have never had it stuck on erasing for hours. If you hold down the power button long enough, will it reboot? If you can time it right, you should be able to hold the Power + Volume up + Volume down and hopefully get into the recovery. I think it has to be all three buttons. Not just Volume up. At least that takes me to the bootloader screen.
Click to expand...
Click to collapse
If I hold in power, it will reboot. It does not stay powered down. And when it comes up, it goes right in to "Erasing" again. I thought volume down as Fastboot and Up was Recovery (or maybe the other way around). I will try holding in both volume up/down at the same time instead. I might have tried it in my rage when this happened, but can't remember, so will try it for sure when I charge it back up again (it eventually stops because the battery just dies).
ganiman said:
If I hold in power, it will reboot. It does not stay powered down. And when it comes up, it goes right in to "Erasing" again. I thought volume down as Fastboot and Up was Recovery (or maybe the other way around). I will try holding in both volume up/down at the same time instead. I might have tried it in my rage when this happened, but can't remember, so will try it for sure when I charge it back up again (it eventually stops because the battery just dies).
Click to expand...
Click to collapse
I've always held all three buttons with my Nexus devices and it takes me to the bootloader. You could be right about volume down being Fastboot and Up being Recovery but I'm not 100% sure. There should be a way of getting out of that though. If you just did a factory reset, I don't think it would have messed with recovery or anything.
jsgraphicart said:
I've always held all three buttons with my Nexus devices and it takes me to the bootloader. You could be right about volume down being Fastboot and Up being Recovery but I'm not 100% sure. There should be a way of getting out of that though. If you just did a factory reset, I don't think it would have messed with recovery or anything.
Click to expand...
Click to collapse
From https://source.android.com/source/running.html#booting-into-fastboot-mode
Booting into fastboot mode
During a cold boot, the following key combinations can be used to boot into fastboot mode, which is a mode in the bootloader that can be used to flash the devices:
manta Press and hold both Volume Up and Volume Down, then press and hold Power
Hopefully, this thread is still followed....
So, about 6mos ago, my Nexus 10 stopped working and I couldn't get it back working...eventually moved onto a new tablet, which now I hate....
Anyway, I figured I'd head back to my N10 because I loved it. However, one of the reasons I left it was because it was stuck in bootloop and I was pretty sure it was bricked.
The bad news, I have followed MANY, if not ALL, of the suggestions on getting it back, I just cannot get it to boot. The good news, fastboot connects with the tablet. So, some specifics:
The tablet WILL boot into fastboot and I can send commands and the tablet is unlocked (also, I believe someone said they had issues because they had an older version of ADB and Fastboot. I'm pretty sure I downloaded the 'most current' version 1.4.3). So, with that, I was able to do the fastboot erase functions, such as cache, userdata, system, etc... and then also load the bootloader (mantafm01) and also send the stock .zip file (image-mantaray-....) and the tablet appears to load everything fine. Thumbs up, right? However, when it reboots it stops at the 'erasing' android bot and will not pass that. I left the tablet in that state for a few minutes all the way up to 3 days...no success.
I also tried the above using Wugfresh only to have the same thing occur. So, basically, I am stuck at 'erasing' and I don't know what to do. I feel confident that the tablet has the ability to be brought back to life, I just cannot figure out how/why all of the attempts lead to the same issue.
What I can also tell you is that while fastboot 'sees' the tablet, the tablet does not appear as a device in "My Computer" like it normally did when connecting via USB. I am using the original USB cable and have tried on multiple computers, all to no avail. I've downloaded/installed the drivers, as instructed on many links. Also, while I can get to the 'Recovery Mode' by pressing Power, Volume Up, Volume Down, if I choose "Recovery Mode" on the tablet, it reboots and goes to the 'erasing' screen. I have tried flashing TWRP on the tablet using fastboot as well. And, sometimes, not all the time, the TWRP blue/black screen appears but it will not progress past that screen (i.e., it doesn't go into recovery).
So, if you can, please help. I believe I have followed all of the instructions, but I have to be missing something or not following something correctly. I'm stoked that it looks like it's only soft-bricked, I just can't get it un-bricked.
Thanks in advance!
Please help, I went to update my magisk to 11.6 as it said, everything else is fine. It's rooted has NATFs ROM on it, 3.2 and everything else was otherwise fine. Then, it rebooted to install the Magisk update and here I am stuck with a phone that won't boot past the LG Life's Good screen. The screen dims slightly after the LG logo is displayed and then nothing. Absolutely nothing at all. I can't boot into recovery or bootloader, and the device isn't recognized even though my computer makes a noise as though it's connected when I plug it in to the computer's USB port.
Please help, I'm really stuck here.
sanjsrik said:
Please help, I went to update my magisk to 11.6 as it said, everything else is fine. It's rooted has NATFs ROM on it, 3.2 and everything else was otherwise fine. Then, it rebooted to install the Magisk update and here I am stuck with a phone that won't boot past the LG Life's Good screen. The screen dims slightly after the LG logo is displayed and then nothing. Absolutely nothing at all. I can't boot into recovery or bootloader, and the device isn't recognized even though my computer makes a noise as though it's connected when I plug it in to the computer's USB port.
Please help, I'm really stuck here.
Click to expand...
Click to collapse
Have you tried going to recovery via button combinations?
JeyTruth said:
Have you tried going to recovery via button combinations?
Click to expand...
Click to collapse
Yes, thanks. I tried that. Nothing registers with the power on/volume down nor volume up.
Is the bootloader corrupted?
sanjsrik said:
Yes, thanks. I tried that. Nothing registers with the power on/volume down nor volume up.
Is the bootloader corrupted?
Click to expand...
Click to collapse
Then unbrick the phone by going fastboot mode
Type "fastboot oem lock (or locker)"
*Then shut off the phone.
*Then do a factory reset by the same combination you do when going to recovery.
*after that try going fastboot again and unlock the oem
*with "fastboot oem unlock(or "unlocker" don't remember
Then you should be able to go to recovery.
BE AWARE : your phone my be wiped so make sure you backup.
Just wanted to say I'm on the same rom and did the update too, but I didn't have any issues thankfully.
JeyTruth said:
Then unbrick the phone by going fastboot mode
Type "fastboot oem lock (or locker)"
*Then shut off the phone.
*Then do a factory reset by the same combination you do when going to recovery.
*after that try going fastboot again and unlock the oem
*with "fastboot oem unlock(or "unlocker" don't remember
Then you should be able to go to recovery.
BE AWARE : your phone my be wiped so make sure you backup.
Click to expand...
Click to collapse
I'm a moron. Can I ask for really stupid steps here because I'm kind of nervous about making this worse.
1. I was able to oem lock and unlock, however I still can't get past the LG screen. I can get to fastboot, nothing more
2. I'm sure everything is wiped, I'll worry about later, I just want to be able to get to recovery and nothing is registering at all
3. ADB reboot recovery isn't working at all I get error: device '(null)' not found
Currently, I'm sitting with the device plugged into my computer on fastboot mode displayed on the screen with the command "use fastboot reboot" if the fastboot is available.
fastboot devices shows the following:
LGH918ad448f8 fastboot
Is there a way to get to recovery from fastboot?
ugh, this is so frustrating. Any help would be gratefully appreciated.
sanjsrik said:
I'm a moron. Can I ask for really stupid steps here because I'm kind of nervous about making this worse.
1. I was able to oem lock and unlock, however I still can't get past the LG screen. I can get to fastboot, nothing more
2. I'm sure everything is wiped, I'll worry about later, I just want to be able to get to recovery and nothing is registering at all
3. ADB reboot recovery isn't working at all I get error: device '(null)' not found
ugh, this is so frustrating. Any help would be gratefully appreciated.
Click to expand...
Click to collapse
After you locked the oem. Did you turn off the phone and then factory reset (by pressing volume down and power, after you see lg you then release only power button for a second and press it again)?
Make sure to do this after locking oem and before unlocking oem.
JeyTruth said:
After you locked the oem. Did you turn off the phone and then factory reset (by pressing volume down and power, after you see lg you then release only power button for a second and press it again)?
Make sure to do this after locking oem and before unlocking oem.
Click to expand...
Click to collapse
Okay, did this bit and yes, wiped the data and the screen showed up asking me to do so.
sanjsrik said:
Okay, did this bit and yes, wiped the data and the screen showed up asking me to do so.
Click to expand...
Click to collapse
Alright you can theoretically flash the recovery twrp.img through fast boot, after you reflash the recovery you can go recovery from there.
I think typing fastboot reboot recovery
Check online. I'm not sure exactly.
sanjsrik said:
Okay, did this bit and yes, wiped the data and the screen showed up asking me to do so.
Click to expand...
Click to collapse
I'm taking the battery out.
reinserting the battery
Pressing the power and volume up button and releasing for a second and reholding what do I release and rehold? I am trying to hold the volume up while releasing and reholding the power but I just get the same LG screen and no recovery
Ugh, i"m so sorry for asking for so much help.
sanjsrik said:
I'm taking the battery out.
reinserting the battery
Pressing the power and volume up button and releasing for a second and reholding what do I release and rehold? I am trying to hold the volume up while releasing and reholding the power but I just get the same LG screen and no recovery
Ugh, i"m so sorry for asking for so much help.
Click to expand...
Click to collapse
After you do that button combinations it's going to ask you if you want to wipe or factory reset etc, you choose YES twice!. If you flashed recovery before then it'll take you over there after the choosing yes (it's not really gonna do anything just suppose to take you to recovery)
Edit: Okay let me be clear. When you lock the oem you should do the buttons combination. If you do them successfully then it should take you to a white screen. Asking you about confirmation twice. Then it will wipe and factory reset.
Now when you already have oem unlocked, you do the same procedure and which will take you to white screen then you choose YES twice then it'll take you to recovery (if you have successfully flashed it before)
---------- Post added at 12:41 AM ---------- Previous post was at 12:34 AM ----------
sanjsrik said:
I'm taking the battery out.
reinserting the battery
Pressing the power and volume up button and releasing for a second and reholding what do I release and rehold? I am trying to hold the volume up while releasing and reholding the power but I just get the same LG screen and no recovery
Ugh, i"m so sorry for asking for so much help.
Click to expand...
Click to collapse
Lol, btw it's volume DOWN not volume up.
So don't even lock the oem, try doing the combination properly now
Edit: so if it still doesn't work then try flashing twrp.img through fastboot there is a command I just don't remember. Make sure you have the .img twrp file locally so you can flash it.
JeyTruth said:
After you do that button combinations it's going to ask you if you want to wipe or factory reset etc, you choose YES twice!. If you flashed recovery before then it'll take you over there after the choosing yes (it's not really gonna do anything just suppose to take you to recovery)
Click to expand...
Click to collapse
i did choose yes twice, but when exactly did I flash recovery at this point? You write "IF you flashed recovery" I had recovery on here already but can't get to it
at this point, all I can do is see fastboot if I plug the phone into a cable, put the battery in and hold the volume down button down otherwise, I can't get to anything else but fastboot.
I'm at the fastboot mode
I downloaded the latest recovery twrp-3.0.2-1-h918.img (renamed to image.img), I'm trying the following command to push and flash recovery through bootloader but I get the following error
message:
fastboot flash image.img and I see the following error message:
cannot determine image filename for 'image.img'
What am i doing wrong?
ugh, I'm really sorry for asking so many dumb questions
sanjsrik said:
i did choose yes twice, but when exactly did I flash recovery at this point? You write "IF you flashed recovery" I had recovery on here already but can't get to it
at this point, all I can do is see fastboot if I plug the phone into a cable, put the battery in and hold the volume down button down otherwise, I can't get to anything else but fastboot.
I'm at the fastboot mode
I downloaded the latest recovery twrp-3.0.2-1-h918.img (renamed to image.img), I'm trying the following command to push and flash recovery through bootloader but I get the following error
message:
fastboot flash image.img and I see the following error message:
cannot determine image filename for 'image.img'
What am i doing wrong?
ugh, I'm really sorry for asking so many dumb questions
Click to expand...
Click to collapse
The proper command is;
Fasboot flash recovery image.img
And make sure the twrp file is stored locally from where you started the command prompt.
If it worked and flashed then try: Fasboot reboot recovery
To go to recovery.
I was able to run the following command from fastboot (looked it up):
fastboot flash recovery image.img
I see the following error message:
target reported max download size of 5368...
sending 'recovery' (24092 KB)
OKAY [0.578s]
writing 'recovery'...
FAILED (remote: unknown command)
finished. total time: 0.598s
So, should I try the volume down and power button again?
sanjsrik said:
I was able to run the following command from fastboot (looked it up):
fastboot flash recovery image.img
I see the following error message:
target reported max download size of 5368...
sending 'recovery' (24092 KB)
OKAY [0.578s]
writing 'recovery'...
FAILED (remote: unknown command)
finished. total time: 0.598s
So, should I try the volume down and power button again?
Click to expand...
Click to collapse
Yes, power off phone and try the combination
---------- Post added at 01:05 AM ---------- Previous post was at 12:56 AM ----------
@sanjsrik if still not working then take a look at this;
http://techxat.com/restore-lg-v20-stock-romfirmware-unroot/
JeyTruth said:
Yes, power off phone and try the combination
---------- Post added at 01:05 AM ---------- Previous post was at 12:56 AM ----------
@sanjsrik if still not working then take a look at this;
http://techxat.com/restore-lg-v20-stock-romfirmware-unroot/
Click to expand...
Click to collapse
Ugh, thank you so much for your patience. I did the following:
battery pull
power on, volume down
LG logo finger off for one second on the power button, kept volume down
rebooted into recovery, I'm flashing NATF ROM now
thank you so much I hope this works, all the data and stuff can be recovered, didn't/wouldn't lose much, all backed up. It's installing now.
i sure hope this works
YES, I SEE THE ANDROID boot screen. This thing takes a while to get past but at least it means I'm on the right track.
I thank you a lot brother.
sanjsrik said:
I'm taking the battery out.
reinserting the battery
Pressing the power and volume up button and releasing for a second and reholding what do I release and rehold? I am trying to hold the volume up while releasing and reholding the power but I just get the same LG screen and no recovery
Ugh, i"m so sorry for asking for so much help.
Click to expand...
Click to collapse
I hit this issue on my h910 I extracted the boot image from the ROM flashed it in fastboot after that I was able to access recovery
Sent from my LG-H910 using Tapatalk
I'm sitting here doing nothing waiting for all the apps to reinstall. What a waste of a day. I didn't reinstall Magick, never really used it. Not sure what happened, but at least it wasn't fatal.
sanjsrik said:
I'm sitting here doing nothing waiting for all the apps to reinstall. What a waste of a day. I didn't reinstall Magick, never really used it. Not sure what happened, but at least it wasn't fatal.
Click to expand...
Click to collapse
Yea, happens. Just to be sure. Make sure you keep twrp and supersu stored on SD just in case. And always backup [emoji14]
Thank you
JeyTruth said:
Yea, happens. Just to be sure. Make sure you keep twrp and supersu stored on SD just in case. And always backup [emoji14]
Click to expand...
Click to collapse
I do a daily backup at about 3am to my SD card. Thought about restoring from it, but then realized this is an opportunity to start all over which is something I was leery to do because I didn't want to set the phone up again. Yet, I'm doing it now to see what was causing the awful battery drain.
<SOLVED>
I am still pretty new to Android and modding so be gentle..............
Should have know better. Flashed the latest Omega Kernel on my 6T while watching the kiddos practice for an upcoming belt test. I know I don't mulit task!
Flashed the Android 10 version on my Android 9 phone. Realized what I did when it would go past the bootloader unlocked warning. Eventually it went to the qualcomm dump mode then rebooted.
Now I can't get it to do anything. It is stuck on that screen. Power button does nothing. My theory is if I can get into recovery I can just flash the correct previous version of Omega that is on the phone.....but without a working power button I am stuck. Computer does not even see the phone when I plug it in.
What now?
Many thanks in advance.
Use the MSM Tool method to un brick your phone. Look for the forum in the Roms, Kernels... Section.
You're going to loose all data.
I will get over losing my data. I don't have a windows machine at the house. I will have to go to our shop to use that horrible OS. Thanks for the intel.
You can fix this issue in minutes without requiring to run MSM Tool or lose any data. I faced a similar issue myself few days ago and got it running back again by doing the follows:
Boot your device into fastboot mode, download the latest boot.img (stock or any other kernel) and TWRP and type these in command line:
1) Fastboot flash boot.img
2) Fastboot boot twrp.img
3) Your device will boot into TWRP Recovery, so flash TWRP installer zip so it sticks.
4) Reboot to recovery again and flash Magisk or Full Rom OTA.
You should be fine then.
Anwar Syed said:
You can fix this issue in minutes without requiring to run MSM Tool or lose any data. I faced a similar issue myself few days ago and got it running back again by doing the follows:
Boot your device into fastboot mode, download the latest boot.img (stock or any other kernel) and TWRP and type these in command line:
1) Fastboot flash boot.img
2) Fastboot boot twrp.img
3) Your device will boot into TWRP Recovery, so flash TWRP installer zip so it sticks.
4) Reboot to recovery again and flash Magisk or Full Rom OTA.
You should be fine then.
Click to expand...
Click to collapse
Thanks, but you missed the part where my power button is not working. The phone is stuck on the 'bootloader unlocked' warning message and the power button does nothing. No way to boot into recovery or fastboot.
PattayaGlock said:
Thanks, but you missed the part where my power button is not working. The phone is stuck on the 'bootloader unlocked' warning message and the power button does nothing. No way to boot into recovery or fastboot.
Click to expand...
Click to collapse
Is your power button broken by any chance?
If it isn't, then hold volume up + power button for a few minutes and it will reboot to Fastboot screen.
Edit: Also try volume down + power button if volume up does nothing. Make sure you hold either of the combination for a few minutes until you get a haptic feedback. Google "Boot OnePlus 6T into Fastboot mode" and follow the instructions there. Once in Fastboot, follow what I wrote in my previous reply.
Anwar Syed said:
Is your power button broken by any chance?
If it isn't, then hold volume up + power button for a few minutes and it will reboot to Fastboot screen.
Edit: Also try volume down + power button if volume up does nothing. Make sure you hold either of the combination for a few minutes until you get a haptic feedback. Google "Boot OnePlus 6T into Fastboot mode" and follow the instructions there. Once in Fastboot, follow what I wrote in my previous reply.
Click to expand...
Click to collapse
Holding the power button does nothing.
Power + down volume does nothing.
Discovered power + up button WILL turn the phone off. It also just brings it back to the "bootloader unlocked" warning page. It won't bring it to fastboot mode.
Makes sense as recovery is now part of the boot.img instead of a partition. I am assuming fastboot is also part of the boot.img. If that is the case there is no way to get into fastboot with an Android 10 kernel on my Android 9 phone. ..... I think
PattayaGlock said:
Holding the power button does nothing.
Power + down volume does nothing.
Discovered power + up button WILL turn the phone off. It also just brings it back to the "bootloader unlocked" warning page. It won't bring it to fastboot mode.
Makes sense as recovery is now part of the boot.img instead of a partition. I am assuming fastboot is also part of the boot.img. If that is the case there is no way to get into fastboot with an Android 10 kernel on my Android 9 phone. ..... I think
Click to expand...
Click to collapse
Go through my reply history. I was on 9.0.17 and had flash RadioActive kernel which was based on/for Android 10 and went into crash dump mode. Doing those steps resolved it.
Both volume buttons + power for a hard shutdown [emoji6]
Anwar Syed said:
(...) Make sure you hold either of the combination for a few minutes until you get a haptic feedback.(...)
Click to expand...
Click to collapse
Minutes? [emoji50] We don't want users dislocating their fingers [emoji51]
Wrapped with delicious Fajita [emoji896]
Timmmmaaahh said:
Both volume buttons + power for a hard shutdown [emoji6]
Minutes? [emoji50] We don't want users dislocating their fingers [emoji51]
Wrapped with delicious Fajita [emoji896]
Click to expand...
Click to collapse
Should've said seconds, my bad, but your reply is hilarious...lmao xD
Turns out holding all 3 buttons did the trick....in a weird FUBAR kind of way.
1st time it popped into fastboot. Figured what the hell, tried to reboot, nope.
2nd time just booted back to the warning screen.....okay, freaked out again.
Got back into fastboot, flashed twrp, rebooted to the warning screen. SH*T!
Got back to fastboot, flashed twrp, damn thing booted into the os as if nothing had ever happened.
Held my breath, downloaded the correct kernel, rebooted to recovery, flashed, rebooted system. Everything is good.
Guess the a/b partition maybe?
Anyway, problem solved, headache over, NO DATA LOST.
Thank you everyone!
All 3 buttons did it....in a wierd FUBAR kind of way.
1st time fastboot popped up. Figured I would try reboot, nope.
2nd time just booted back to warning screen, uh oh.
3rd time fastboot, flash twrp, booted back to warning screen.
4th time fastboot, twrp, booted into OS like nothing ever happened.
Held my breath, downloaded the correct kernel update, recovery, flashed, rebooted and I am good to go.
Thanks everyone for your help!
Sorry for the dual post, I am in BOTARD mode apparently. Didn't see the post and thought I forgot to send......missed page 1 of 2!
PattayaGlock said:
Guess the a/b partition maybe?
Click to expand...
Click to collapse
That would be my guess. It should just switch to the functional slot if the other isn't (properly) booting but I've experienced this system to behave quite erratically. I presume these are childhood diseases of a relatively new Android partitioning system.
Back in the 'old' system all you should've done was boot to recovery (which couldn't be corrupted by the OS!) and dirty flash either a working kernel or the original (stock) ROM that includes the kernel.
Anyway, glad you retained all your data! Thanks for updating the title and OP with a solved tag
PattayaGlock said:
<SOLVED>
I am still pretty new to Android and modding so be gentle..............
Should have know better. Flashed the latest Omega Kernel on my 6T while watching the kiddos practice for an upcoming belt test. I know I don't mulit task!
Flashed the Android 10 version on my Android 9 phone. Realized what I did when it would go past the bootloader unlocked warning. Eventually it went to the qualcomm dump mode then rebooted.
Now I can't get it to do anything. It is stuck on that screen. Power button does nothing. My theory is if I can get into recovery I can just flash the correct previous version of Omega that is on the phone.....but without a working power button I am stuck. Computer does not even see the phone when I plug it in.
What now?
Many thanks in advance.
Click to expand...
Click to collapse
hello
I have the same problem with my phone, I have read all your comments about how to fix it, but I didn't understand how you fixed it, only holding the 3 bottons? and waiting to get into recovery or what?
tnx
My phone is sony xperia z1. I rooted this phone. and flashed wrong kernel after that the phone was not responding. Even though I pressed the power button, nothing appeared on the screen, please help me