I tried rooting Moto G4 Plus and just after flashing the supersu and rebooting, it got bricked. Nothing shows except LED blink while connecting to PC/charger. Also, it won't detect in the device manager as a qualcomm device/qhsusb bulk or anything... I seriously need your help. Please help.
PS: I surfed over various related threads and all of them required the device to be detected on PC.
1) are you able to power off your device, then hold down the power and volume down keys? Does that boot you into the bootloader?
Or can you hold the power button for 1-2 minutes to force a hard shutdown, then attempt to boot into the bootloader?
2) did you flash a custom kernel before attempting to root? On stock Nougat for our device, you need a custom kernel.
The device is already in the switched off stage. When I press and hold the power button, nothing happens. When connected to USB cable, the front LED blinks. Nothing more. It doesn't return any sound or indication while connecting to PC. I tried installing various Qualcomm drivers to get it detected on PC. The Windows device manager shows nothing.
I tried this tutorial to root my device. I missed flashing the elementalx kernel during the root process. it caused the brick.
technorajeev10 said:
The device is already in the switched off stage. When I press and hold the power button, nothing happens. When connected to USB cable, the front LED blinks. Nothing more. It doesn't return any sound or indication while connecting to PC. I tried installing various Qualcomm drivers to get it detected on PC. The Windows device manager shows nothing.
I tried this tutorial to root my device.
Click to expand...
Click to collapse
That tutorial should work, provided you flashed the ElementalX kernel before rooting.
Hmm, what happens if you try to boot by holding down both the power button and the volume down key at the same time? You should still be able to boot into the bootloader (with the AP fastboot secure mode).
What TWRP and SuperSU did you try to flash?
echo92 said:
That tutorial should work, provided you flashed the ElementalX kernel before rooting.
Hmm, what happens if you try to boot by holding down both the power button and the volume down key at the same time? You should still be able to boot into the bootloader (with the AP fastboot secure mode).
What TWRP and SuperSU did you try to flash?
Click to expand...
Click to collapse
I used twrp and supersu as exactly as mentioned in the root thread (twrp-3.2.1-0-athene.img & phh's supersu).
The key combo doesn't work either. No response. Is there any way to get it detected on PC?
I previously had it happened on my Yureka and I had to short the board to get it detected as a qcomm device.
technorajeev10 said:
I used twrp and supersu as exactly as mentioned in the root thread (twrp-3.2.1-0-athene.img & phh's supersu).
The key combo doesn't work either. No response. Is there any way to get it detected on PC?
I previously had it happened on my Yureka and I had to short the board to get it detected as a qcomm device.
Click to expand...
Click to collapse
That's odd, as that key combo should get you booting to the bootloader (as in the tutorial), which should then get your device detected via fastboot. Did your bootloader look similar to this when you were flashing TWRP?
https://plus.google.com/photos/106899236533864901773/album/6441285188929274337/6441285190332216978
If your device is still on, try a hard shutdown (hold power button 1-2 minutes until shutdown, verify it's off by connecting power, you should see the charging symbol come on), then boot by holding volume down and power at the same time.
You could also try a hard reboot https://motorola-global-portal.custhelp.com/app/answers/indevice_detail/a_id/110630/p/30,6720,9687
I just found that the volume down key is broken. I hope that's the reason it won't boot to the bootloader. Let me fix it first and try your suggestion.
And yes, the bootloader menu was the same as shown in this pic.
Thanks a lot for your time bro. Much appreciated.
echo92 said:
That's odd, as that key combo should get you booting to the bootloader (as in the tutorial), which should then get your device detected via fastboot. Did your bootloader look similar to this when you were flashing TWRP?
https://plus.google.com/photos/106899236533864901773/album/6441285188929274337/6441285190332216978
If your device is still on, try a hard shutdown (hold power button 1-2 minutes until shutdown, verify it's off by connecting power, you should see the charging symbol come on), then boot by holding volume down and power at the same time.
You could also try a hard reboot https://motorola-global-portal.custhelp.com/app/answers/indevice_detail/a_id/110630/p/30,6720,9687
Click to expand...
Click to collapse
I just disassembled the phone and flipped the volume rockers so that the volume down should work fine. Then pressed and hold vol - & power button. Violaaa. Got into the bootloader. On TWRP, Just wiped data and flashed the ElementalX followed by SuperSU. It's working super fine now. A billion hugs for your support.
Related
Okay so I seem to have run into a little problem I was planning on updating cleanrom up to 1.2.5 but was on cwm. I had managed to switch over successfully to twrp 2.2.0. I went ahead and used goo manager to download the updated zip of 2.2.1 and tried flashing it thru twrp. Now I am stuck in google bootloop and cant get into recovery or more importantly bootloader. I have been trying last 30mins to hold power and both volume buttons but it either keeps rebooting back to the google screen or not doing anything at all just have to repress to to turn it off but it will turn back on automatically. I tried hooking it up to my usb and labtop but it looks like it wont even recognize it. I just fully charged it so I am good for now just a little worried cant get out of this mess.
I ran into a problem like that with clockwork recovery it kept on rebooting in recovery but I could still go into download mode I was at work away from my computer so I had no choice but to keep trying that three button magic until it finally restored a backup I had on my external card.just keep on trying to pull the battery then try to go into recovery. You might 've gotten a bad download
Sent from my SGH-T999 using xda premium
problem is I cant get into recovery. or the green screen to get to bootloader. It just completely stuck in a bootloop on the google screen mocking me... I am really contemplating opening it up and taking out battery but is that a good idea? Or is there anything else I can do?
so I pulled off the back cover but really dont want o disconnect the battery might mess something up but I cannot get the device to shut off.
disconnecting the battery does nothing it shuts it off and keeps it off but when I connect it to the charger the battery symbol pops up for a second and then goes completely blank. I went ahead and tried again to boot into bootloader pressing power vol up + down and all combinations of power vol -, power vol +
power turbo press vol +/- but no luck still in google screen.
If you're in a bootloop you need to connect your Nexus 7 to a computer. Then you will be able to access recovery via the Power button and volume buttons.
is it going to make a difference that everytime i try to reboot it just the black google screen? I have tried it connected to the wall charger and connected usb to the labtop but nothing.
clago87 said:
is it going to make a difference that everytime i try to reboot it just the black google screen? I have tried it connected to the wall charger and connected usb to the labtop but nothing.
Click to expand...
Click to collapse
It's supposed to do that when you're trying to go to recovery from bootloader without the USB cable plugged into a computer, may need to have the drivers installed on said computer. It's an issue with the nexus 7 bootloader and every one of them does it. What your experiencing is perfectly normal if you tried to go to recovery from bootloader with the bolume buttons and then got the google screen bootloop.
If it doesn't work when you plug it in and try, then try unplugging it, manually rebooting with it plugged in first, or vice versa
Update: I can get on Team Viewer and remotely reboot you into recovery through the PC if you want, or at least give it my best shot.
ok so i disconnected battery and have the device off. I should then try connecting it to the pc and try booting up holding down all buttons?
clago87 said:
ok so i disconnected battery and have the device off. I should then try connecting it to the pc and try booting up holding down all buttons?
Click to expand...
Click to collapse
Have you installed the right drivers on the computer you're using, for ADB and the device drivers, when you unlocked and rooted?
Answer to your question is yes try that. But I wouldn't be disconnecting and reconnecting it, I can't recommend that and then learn tomorrow that static zapped something important.
yea I am getting nothing by connecting to pc. I have all the drivers adb and fastboot installed when I rooted and unlocked couple weeks back but it looks like device is not being recognized or read at all by the pc.
connecting to the pc holding the volume + button gets it recognized for a second and tries to install a driver apx but unsuccessfully.
I am not making any progress whatsoever kinda sucks starting the weekend like this. I have gone thru some bad stuff with my atrix but nothing like this were I cant even access my bootloader boot into recovery or even fastboot. Should I try and get it to just stay off and see if overnight it works its own magic? Hate going to sleep witht his on my mind but I think with a clear mind in the morning something good will happen.
I can get it to stay off by holding both vol+ and vol- but trying to turn it off with just the power button just keeps it turning back on/off...
so I slepted on it thru the night let the tablet rest but went back this morning and I still cant get into bootloader or recovery. Is there anything I can do?
Has anyone else had this problem where they cant boot into recovery or bootloader? It's like the power button and vol keys are unresponsive even though they still work to turn on the device.
are you sure that you flashed the right recovery? but you should still be able to get the bootloader. are you pressing power + volume down(volume down, not both volume buttons. i noticed you wrote both volume buttons) to get into the bootloader?
I think I chose the right recovery the first version downloaded thru goo manager but it was the 2.2.0 version. I had the option on the of downloading the 2.2.1 zip or the .img but i downloaded the .img to just to flash with the current version of twrp that was working. There have been times were I have not been able to get into recovery on my atrix or htc but I've always been able to get into the bootloader this is the first time I've been locked out of my device kind of got me scared its not even a month old. So you say to get into bootloader you dont have to hold down both volume buttons? I will try again to power back up using the volume down and power button at same time... Wish me luck
clago87 said:
I think I chose the right recovery the first version downloaded thru goo manager but it was the 2.2.0 version. I had the option on the of downloading the 2.2.1 zip or the .img but i downloaded the .img to just to flash with the current version of twrp that was working. There have been times were I have not been able to get into recovery on my atrix or htc but I've always been able to get into the bootloader this is the first time I've been locked out of my device kind of got me scared its not even a month old. So you say to get into bootloader you dont have to hold down both volume buttons? I will try again to power back up using the volume down and power button at same time... Wish me luck
Click to expand...
Click to collapse
good luck!
yea, only power button and the volume down button.
quick question before I connect the battery does it make a difference whether or not I have it plugged in charging or connected to the PC while trying to boot into bootloader?
So I have this strange issue. I just tried shutting my tablet down so I can reboot to recovery to flash something. (Mind you, I haven't flashed anything in a few days)
So I shutdown and I can't access recovery. It just wont boot. Vol+, Vol- and Power at the same time. I tried going power first, then volume and vice versa but no dice. My volume buttons and power button work perfectly fine while in the ROM.
Now at this point I was like, "Screw it, I'll boot into the ROM" but no.... It wouldn't even turn on. I tried plugging it in and nothing (~70% battery when shutting it off). Then I plugged it into my computer and it showed "Device driver software was not successfully installed" with a device named "QHSUSB_DLOAD".
Quick Google-ing made me think I bricked the device. I ended up just holding on the power button for a good minute and it finally booted into the ROM. I'm still unable to boot into recovery via Power + Volume Buttons... I have to use an app to boot me into it.
Why? What happened / is happening?
I'm not sure with the N7, but with my SGS III that's what happened when it bricked.
blaze0303 said:
I'm not sure with the N7, but with my SGS III that's what happened when it bricked.
Click to expand...
Click to collapse
Yeah... very strange. I'm able to get into the bootloader without a problem... only through an app.
Can you attempt to reflash your recovery?
anekdotos said:
So I shutdown and I can't access recovery. It just wont boot. Vol+, Vol- and Power at the same time. I tried going power first, then volume and vice versa but no dice. My volume buttons and power button work perfectly fine while in the ROM.
Click to expand...
Click to collapse
Could you double check you are pressing the right buttons based on these instructions:
[Info] Guide to entering safe mode, bootloader, stock recovery
You are NOT supposed to press 3 buttons, Vol+ and Vol- and Power as you described, rather just 2 buttons depending on whether you want recovery or bootloader.
sfhub said:
Could you double check you are pressing the right buttons based on these instructions:
[Info] Guide to entering safe mode, bootloader, stock recovery
You are NOT supposed to press 3 buttons, Vol+ and Vol- and Power as you described, rather just 2 buttons depending on whether you want recovery or bootloader.
Click to expand...
Click to collapse
Well now I feel like a total dimwit.
I guess I was so used to my Galaxy Nexus... I did a Google search on how to access the N7 recovery but I guess I glanced over the instructions too quickly.
This thread can be locked, lol.
BTW sorry, I fixed the link.
Hello, I have a problem with my storm. Two days ago I received it and flashed the then latest cm13 and its corresponding recovery. Everything seemed to work just fine until yesterday when there appeared to be an ota update. After the download finished, the phone rebooted itself and is since then stuck with a black flickering screen. Every attempt to start the phone using recovery or bootloader seems to fail, as the phone keeps showing me the black flickering screen, no matter the combination of keys (vol+/vol-) I use to turn it on. If during the black screen I plug the phone to the computer adb can actually see the phone but says it's not authorized to perform any command. On the other hand fastboot won't even see the device.
Is there anything else I can try before sending it back to wileyfox?
Thank you in advance
I've made some progress, I found out that the device can be forced to Qualcomm HS-USB QDLoader 9008 mode by turning it off and then connecting it to usb while holding vol+ and vol-.
I've also found the stock firmware at https://cyngn.com/support.
Now it would be great if somebody could help me, and the others in my situation, to figure the wole QFIL unbricking out, because I'm overwhelmed, and can't seem to find the right info on google.
Thanks to anyone who'll care to help, or share some info
I had a similar issue so have created a thread with stock recovery instructions, which resolved the issue for me.
http://forum.xda-developers.com/wileyfox-storm/help/how-to-flash-stock-images-brick-recovery-t3319617
I hope this helps.
miSAKe said:
I had a similar issue so have created a thread with stock recovery instructions, which resolved the issue for me.
http://forum.xda-developers.com/wileyfox-storm/help/how-to-flash-stock-images-brick-recovery-t3319617
I hope this helps.
Click to expand...
Click to collapse
Thank you for your reply.
Unfortunately this does not seem to be applicable to my case because on my device fastboot mode doesn't seem to work.
I've spent an entire afternoon trying to get it to boot to fastboot mode using different vol keys combinations and timings, but none of them seemed to work. No matter the combination, it just kept booting to a black screen flickering.
I'm starting to think that it could be some problem unrelated to my actions because if, as I think it is, recovery mode and fastboot mode are two separated things, nothing I did would justify this kind of behaviour.
maxxie00 said:
Thank you for your reply.
Unfortunately this does not seem to be applicable to my case because on my device fastboot mode doesn't seem to work.
I've spent an entire afternoon trying to get it to boot to fastboot mode using different vol keys combinations and timings, but none of them seemed to work. No matter the combination, it just kept booting to a black screen flickering.
I'm starting to think that it could be some problem unrelated to my actions because if, as I think it is, recovery mode and fastboot mode are two separated things, nothing I did would justify this kind of behaviour.
Click to expand...
Click to collapse
Sorry to hear you are still having trouble, it does sound like the same issue, was a CM13 update from the last couple of days, upon reboot I saw the wileyfox logo but when the Cyanogen logo would normally show during boot it displayed a black screen, which would flicker every few seconds. Holding vol- and power to reboot resulted in the same thing so I was unable use recovery.
When the display was black and connected via USB I was able to see the device using ADB but like you no commands were authorised.
Leaving the phone plugged in via USB and holding down vol+ and power until it rebooted I was able to enter fastboot, once the fastboot prompt was displayed on the screen I attempted using fastboot to boot from a custom recovery, unfortunately that just resulted in the same blank screen for me. I also tried booting the stock recovery with the same result, I admit I did not try many older CM recoveries, but I wanted to revert to CM12.1 anyway, as the accelerometer and gyroscope not working in CM13 at the moment is no good for me.
Only thing that worked was a stock restore, so I think something beyond the recovery got broken as you could not even boot a previously working recovery.
For the sake of sanity it may be work getting someone else try booting it into fastboot before resorting to Wileyfox support. Though your phone is really new so could claim a refund or replacement from the seller, that would probably be faster.
FYI if you do end up sending it to Wileyfox support they do flash it back to stock, I had a broken screen replaced, was repaired and back to me in just under 2 weeks.
What would be exactly the timing for it to boot to fastboot mode?
Because I just tried (again...) to plug it to the computer while powered off, then it powered on on its own.
After that I rebooted it by holding together power and vol+ and immediately after it rebooted (right after the vibration) I let the power button go and kept holding the vol+ until the black screen appeared again... no fastboot
maxxie00 said:
What would be exactly the timing for it to boot to fastboot mode?
Because I just tried (again...) to plug it to the computer while powered off, then it powered on on its own.
After that I rebooted it by holding together power and vol+ and immediately after it rebooted (right after the vibration) I let the power button go and kept holding the vol+ until the black screen appeared again... no fastboot
Click to expand...
Click to collapse
Hi,
Just tried a few combinations to check timings for you.
Powered off, not plugged in, holding vol+ while plugging in phone end of usb connected to computer, keep holding vol+ -> boots straight to fastboot.
Powered on, already connected to computer via usb, holding vol+ and power, release power when vibrates to indicate reboot but keep holding vol+ -> boots straight to fastboot.
Are you seeing the black and white Wileyfox logo when first booting? When going to fastboot it should skip that. If you are not seeing the logo it might not show the fastboot screen either. You can try following the steps above and then issuing fastboot devices from a command/shell session to see if you are in fastboot mode.
I hope that is of some help.
Thank you but I can confirm that neither of these combinations work for me. When rebooted/powered the device shows the wileyfox's logo.
If I use your first method it just seems to freeze on the wileyfox's logo screen, and the computer won't even see it (it's not listed on the usb devices list) so fastboot's not an option.
If I use your second method, or any other I tried, it shows me the wileyfox's logo and then proceeds to the black screen, which can be seen just by adb (not fastboot) but I'm not authorized to perform any action like you described for your issue.
I'm out of ideas so I'm sending it back and getting it replaced. On the cyanogenmod irc they told me that to brick it like that it cannot be done just by accident but it should require a lot of deliberate effort, and that just installing cm13 + recovery doesn't justify this problem nor does an OTA update, so it's probably some other (hardware?) issue with a very bad timing.
I'm kind of sure it's not the vol+ button that's damaged, because if I leave the device powered off and then proceed to plug the USB while holding together vol+ and vol- it powers on, but the screen stays off meaning the Qualcomm HS-USB QDLoader 9008 mode has been triggered.
Anyway thank you for your help, I could rule out my inability to start the fastboot mode and blame it on the phone xD
Hope I'll be luckier with the next one...
maxxie00 said:
Thank you but I can confirm that neither of these combinations work for me. When rebooted/powered the device shows the wileyfox's logo.
If I use your first method it just seems to freeze on the wileyfox's logo screen, and the computer won't even see it (it's not listed on the usb devices list) so fastboot's not an option.
If I use your second method, or any other I tried, it shows me the wileyfox's logo and then proceeds to the black screen, which can be seen just by adb (not fastboot) but I'm not authorized to perform any action like you described for your issue.
I'm out of ideas so I'm sending it back and getting it replaced. On the cyanogenmod irc they told me that to brick it like that it cannot be done just by accident but it should require a lot of deliberate effort, and that just installing cm13 + recovery doesn't justify this problem nor does an OTA update, so it's probably some other (hardware?) issue with a very bad timing.
I'm kind of sure it's not the vol+ button that's damaged, because if I leave the device powered off and then proceed to plug the USB while holding together vol+ and vol- it powers on, but the screen stays off meaning the Qualcomm HS-USB QDLoader 9008 mode has been triggered.
Anyway thank you for your help, I could rule out my inability to start the fastboot mode and blame it on the phone xD
Hope I'll be luckier with the next one...
Click to expand...
Click to collapse
No problem, I hope you have more luck with the replacement.
Here I am again, new device, still can't boot to fastboot mode (this time I didn't flash anything, just unlocked bootloader so it's not bricked).
"adb reboot-bootloader" works, advanced reboot menu works, yet the vol+ combination hangs on the vendor's logo.
I'm contacting cyanogen os people to try to understand what might be the issue...
Could you please confirm that your device boots into fastboot mode when using the vol+ way? thank you
maxxie00 said:
Here I am again, new device, still can't boot to fastboot mode (this time I didn't flash anything, just unlocked bootloader so it's not bricked).
"adb reboot-bootloader" works, advanced reboot menu works, yet the vol+ combination hangs on the vendor's logo.
I'm contacting cyanogen os people to try to understand what might be the issue...
Could you please confirm that your device boots into fastboot mode when using the vol+ way? thank you
Click to expand...
Click to collapse
Hello again,
So these 5 methods work for me, someone else may have other experiences:
Phone powered off, hold vol+ while connecting USB, other end of USB already plugged into PC, continue holding vol+ until booted to fastboot (almost instant).
Phone powered on, already connected to USB, other end of USB already plugged into PC, hold vol+ and power until reboot vibrate, continue holding vol+ until booted to fastboot (almost instant).
Phone powered on and in OS, already connected to USB, other end of USB already plugged into PC, debug enabled, from ADB console, adb reboot fastboot or adb reboot bootloader
Phone powered on and in OS, advanced reboot options turned on, hold power, select reboot, select bootloader, reboot
Phone powered on and in Recovery, select reboot to bootloader
Currently I am running stock everything.
Perhaps try different USB cables or ports, though I still get to fastboot without the USB cable plugged in.
My Storm was a pre-order so is one of the first releases, it is possible they have changed something since.
Edit: I have come across a thread on the Cyanogen forums which implies this may be related to encrypting your device: http://forum.cyanogenmod.org/topic/117661-bootloader-hangs/ - I see you have been there already
as reference mine is not encrypted at the moment
I was messing with my P10 Lite and I accidentally wiped the Vendor partition (not sure if I wiped anything else) with TWRP. After the phone rebooted it said something about a critical error during boot and went into erecovery. It gave me two options( I don't remember the second one) and I chose factory reset. It started doing it's thing but I guess something went wrong because it wasn't able to boot and it started to bootloop.
I managed to get into fastboot once. The bootloader and FRP should be unlocked but I am not sure as I think I semi accidentally used the command to relock the bootloader in the hopes of it doing the automatic low level factory reset. After that restart, the phone wanted to boot up but after the Huawei logo it went into the EMUI logo which I've shown in the pictures. Now I can't use any button combination and can't enter any menu. I also can't shut down the phone as it bootloops into the EMUI logo after I press the power button. I opened the phone and turned it off by detaching the battery cable but after holding the power down key and plugging the usb cable into the phone it still boots into the EMUI logo right after the Huawei logo.
I guess not being able to enter fastboot is the major issue and after hours of googling I am yet to find a solution.
Edit: I am a newb!
Please help!
Why did you delete the vendor partition, you could try plugging the phone into your computer and checking if you can do anything with fastboot while it's showing emui logo?
Alaunus said:
I was messing with my P10 Lite and I accidentally wiped the Vendor partition (not sure if I wiped anything else) with TWRP. After the phone rebooted it said something about a critical error during boot and went into erecovery. It gave me two options( I don't remember the second one) and I chose factory reset. It started doing it's thing but I guess something went wrong because it wasn't able to boot and it started to bootloop.
I managed to get into fastboot once. The bootloader and FRP should be unlocked but I am not sure as I think I semi accidentally used the command to relock the bootloader in the hopes of it doing the automatic low level factory reset. After that restart, the phone wanted to boot up but after the Huawei logo it went into the EMUI logo which I've shown in the pictures. Now I can't use any button combination and can't enter any menu. I also can't shut down the phone as it bootloops into the EMUI logo after I press the power button. I opened the phone and turned it off by detaching the battery cable but after holding the power down key and plugging the usb cable into the phone it still boots into the EMUI logo right after the Huawei logo.
I guess not being able to enter fastboot is the major issue and after hours of googling I am yet to find a solution.
Edit: I am a newb!
Please help!
Click to expand...
Click to collapse
Dload method. Put sd card in other phone or some card readers and put appropriate files.
nemanjsb said:
Dload method. Put sd card in other phone or some card readers and put appropriate files.
Click to expand...
Click to collapse
I've already tried that. I've placed the appropriate files into my SDcard but I can't use any button commands including volume up+down+power. When I press them my device just boots into the EMUI logo and nothing happens.
Edit: It boots into the EMUI logo even if I only press the power button. Pressing volume down + usb also boots me into the EMUI logo
DaarkZek said:
Why did you delete the vendor partition, you could try plugging the phone into your computer and checking if you can do anything with fastboot while it's showing emui logo?
Click to expand...
Click to collapse
I measured once and not trice before cutting... I was also not paying enough attention/in a hurry...
Power OFF the phone.
Press and Hold VOL Down and connect the phone to PC via USB cable. The phone should boot into Bootloader (fastboot mode). Does this method work?
or try this:
Press and Hold VOL Up and connect the phone to PC via USB cable. The phone should boot into eRecovey mode and then then select "Download latest stock rom and install".
Aalesund said:
Power OFF the phone.
Press and Hold VOL Down and connect the phone to PC via USB cable. The phone should boot into Bootloader (fastboot mode). Does this method work?
or try this:
Press and Hold VOL Up and connect the phone to PC via USB cable. The phone should boot into eRecovey mode and then then select "Download latest stock rom and install".
Click to expand...
Click to collapse
Ok, it seems like not all is lost about my phone. I managed to get into fastboot. In my situation, pressing volume down + usb cable while the battery was plugged into the phone did not work. That was before I opened up my phone's case and disconnected the battery cable.
As I mentioned before, I had opened my phone and disconnected the battery cable because that was the only way to shut it off.
What I did after I disconnected the battery cable was the following:
1 - Hold volume down and don't release it
2 - Plug in USB
3 - Plug in the battery cable into the phone's mobo.
That booted me into fastboot. Right now, the phone says my bootloader in unlocked and my FRP is locked. What would be the best way to flash the new stock OS on my phone?
Aalesund said:
Power OFF the phone.
Press and Hold VOL Down and connect the phone to PC via USB cable. The phone should boot into Bootloader (fastboot mode). Does this method work?
or try this:
Press and Hold VOL Up and connect the phone to PC via USB cable. The phone should boot into eRecovey mode and then then select "Download latest stock rom and install".
Click to expand...
Click to collapse
I have downloaded THIS and THIS for the new OS but by talking with Alexxxx1 in THIS discussion I learnt that Huawei has implemented a security patch in their latest update, which I've most likely installed, that prevents you from rolling back your OS version. That means I need to install the .386 version, which should be the last if I am not wrong, instead of the .378 correct? Though I heavily dislike patches like this I guess I can't do anything about that...
Hi together,
thanks especially to xyz` and k4y0z for your effort and your contributions! This is amazing!
I have an Amazon Fire HD 8 (karnak) with FireOS 6.3.1.2 which I want to root, unlock and install LineageOS on.
With 6.3.0.0 on another tablet, I already performed this procedure successfully.
As k4y0z writes in https://forum.xda-developers.com/hd...nlock-fire-hd-8-2018-karnak-amonet-3-t3963496 that a hardware-change in combination with the soft-brick method could lead to a real brick rendering the device unusable, I went for the hardware method.
What I did:
1. Disconnect tablet
2. Run "bootrom-step.sh"
3. Shorten CLK to GND and at the same time connect the tablet to USB
4. I get the message to remove the short and confirm with ENTER
--> flashing occurs and I find myself in fastboot mode (the tablet also shows up when I do a "fastboot devices")
5. Run "fastboot-step.sh"
--> flashing of recovery and misc occurs, followed by a reboot
Then I see the "Amazon" logo flashing shortly and then the screen stays black. I tried pressing power and the volume-keys shortly, twice, for a long time, ... nothing happens.
If I disconnect and reconnect USB I see the "Amazon" logo flashing again. The device is not in fastboot mode, ("fastboot devices" shows no device) nor is it in adb mode ("adb devices" also shows no device).
Luckily the steps below can be performed again and the flash procedure happens again so I can always get into fastboot mode but then I'm stuck flashing the TWRP with the fastboot-step.sh...
I tried the files from karnak-3.0, karnak-3.0.1 as well as the original amonet-v2, all with the same issue.
Can anybody please shed some light here? What am I doing wrong? Is there anything else I can try or is the tablet unusable now (which I cannot believe as there is fastboot access).
I am in fact running Debian 10 on a VirtualBox on my MacBook with USB forwarding to the Virtual Machine but I'm not sure if that can be the issue as all the flashes are working just fine.
Thanks for your support!
How old is the tablet? Anything bought January or newer is potential unlock-blocked....
Thanks for your answer, Michajin.
The tablet was bought in February 2020. Does that mean I'm out of luck getting LineageOS to run on this tablet?
Would the error I am seeing fit the unlock-block? I had the feeling that all the installing went through just fine, just TWRP is not loaded correctly, right?
Thanks!
Michajin said:
How old is the tablet? Anything bought January or newer is potential unlock-blocked....
Click to expand...
Click to collapse
freddy40 said:
Thanks for your answer, Michajin.
The tablet was bought in February 2020. Does that mean I'm out of luck getting LineageOS to run on this tablet?
Would the error I am seeing fit the unlock-block? I had the feeling that all the installing went through just fine, just TWRP is not loaded correctly, right?
Thanks!
Click to expand...
Click to collapse
If the fastboot-step finishes as success you have TWRP (fastboot step is just the flashing of twrp replacing stock recovery). You should be able to hold the volume down and press the power button, this will boot the device into recovery.
Thanks, Michaejin! That did the trick. Pressing those buttons yesterday didn't help as the tablet was somehow turned on, now I disconnected and reconnected the battery and pressed VolDown + Power and got into TWRP!
Great! Thanks again!
Michajin said:
If the fastboot-step finishes as success you have TWRP (fastboot step is just the flashing of twrp replacing stock recovery). You should be able to hold the volume down and press the power button, this will boot the device into recovery.
Click to expand...
Click to collapse
freddy40 said:
Thanks, Michaejin! That did the trick. Pressing those buttons yesterday didn't help as the tablet was somehow turned on, now I disconnected and reconnected the battery and pressed VolDown + Power and got into TWRP!
Great! Thanks again!
Click to expand...
Click to collapse
You can also hold the power button for about 10 seconds to force a power down, so you should have to pull the cover off in case something goes wrong. Likely the device was stuck in preloader or bootrom.