After unlocking the device I've succesfully installed ressurrection remix and tried a few other custom roms on my device. I flashed twrp to root it as well as to make nandroid backups. However, as twrp wasn't working very well yet, not supporting encryption, not saving its settings, and because some of my apps couldn't be installed from the play store, I decided to try LineageOS. All flashing has been done with fastboot, nothing with twrp (since it wasnt working well i didnt trust it).
With LineageOS I also flashed the remove encryption he offers so I could try Nandroid backups, then the bootloops started. I can get into eRecovery, recovery, fastboot. The system starts, I get the boot logo, I get the ROM boot logo, I hear some sound, then the Huawei logo pulses. After that it just restarts and drops to eRecovery.
I first tried to reflash myself with fastboot, I got some help on the OpenKirin telegram group but that didn't help. I then tried HuRUpdater, but it doesn't detect the volume buttons and the script bails out with an error message.
I decided to pay for and try with DC Phoenix. Everything flashes and completes succesfully. It still bootloops. I asked for support but he says there is no way that he knows of, so I got a refund.
When I boot the device and hold down volume up and down, it seems to start an update. A system boot follows and it still boot loops.
After a factory reset the system still boot loops.
I knew this could happen so I'm not too fussed about it. But before sending it back and pay for repairs, is there anything I can try that you guys can think of?
Or should I just wait for the development to progress and hope there will come a fix in a few weeks time?
Any tips would be greatly appreciated!
Thanks!
When I bootlooped my SHT-AL09, Funky Huawei's eRecovery method is all that worked for me.
It wasn't free, and I wasn't necessarily dealing with the same thing you are. I would try it before sending back to Huawei and paying for a true factory reset.
You might also have more success posting to other more active Huawei boards. EMUI should have its own subforum...
Thanks, I dropped them a mail to see if he can give some advise. They are expensive and have a no-refund policy so it's a gamble. I don't think the factory reset from Huawei is going to be that expensive.
I did notice this:
Code:
c:\adb>fastboot getvar rescue_enter_recovery
getvar:rescue_enter_recovery FAILED (remote: FAIL:need all image flashed!)
finished. total time: 0.024s
Doesn't look good. Could that be the reason for the boot loop, and how do I fix that? Any ideas?
Related
I recently tried a factory reset on my phone after finding that one of my apps was sending out spam texts to random people and racking up my text plan. Upon the first boot, it showed a green android man with a blue orb thing spinning in its stomach and kept going for hours.
My phone was previously running an unofficial build of CM12 and was unlocked and rooted.
Now, I just figured that I could just flash a new recovery to the phone and flash a new ROM to get it back up and running, but I also keep having troubles getting it to flash. Using 'flashboot devices', I see my phone's serial, but when I try to use 'flashboot erase recovery' or 'flashboot flash recovery recovery.img' seems to hang up. I finally got it to write clockwork recovery to the phone somehow, but the device still boots to the green android man w/ blue instead of clockwork. I thought it was an issue, so I have been trying to flash TWRP, and it just hangs, and doesn't even give the <waiting for device> text, so I know it sees it.
Can anyone help me figure out a way to get my recovery flashed correctly? From that point, I should be good to go, as long as it loads into recovery.
Tampered
I have tried everything I can think of, and it still stalls while it is supposed to flash the new recovery, then fails with the error "too many links".
Also, now the **TAMPERED** flag pops up at the top of the bootloader. It still lets me into the FASTBOOT portion, so I don't believe that it is effecting anything, so I will probably just have to worry about that later, if I really feel like going through the whole rumrunner/revone process.
TWRP
Not sure if it is a good sign or not, but I replaced the USB cable and was able to get TWRP to install and actually load once. There were errors after it booted, and I choose to do a full factory wipe to hopefully start over fresh, and the phone rebooted itself. Now TWRP seems to endlessly load while it the splash screen flashes on and off, almost as if it is in a bootloop. I tried reflashing with a slightly older TWRP for my phone, and no luck.
Also, another strange thing is that when I flash a new recovery file, it shows that it only takes a total time of 2.607s. If feel like this is quite short and I remember it taking a bit longer in the past. I just feel like it is not writing the entire recovery, hense the blinking teamwin logo that seems to be stuck in a bootloop.
So a while ago, I rooted my nexus 6 phone and along with it TWRP. So, today, I tried unrooting it, and in the process of doing this, I didn't notice something failed and after this, I locked the OEM, so now I can't unlock it. After doing this, my phone starts to boot, and the image for TeamWin Just keeps flashing, and when I try to go to recovery mode from the fastboot, it just tries to go to teamwin and the image for it just keep flashing as well. I have no idea what to do and I am really panicking. Could anyone please direct me to something that could fix this? I am limited in my knowledge involving fastboot and flashing custom ROM's so I need specific steps as to what to do. I really need help.
*Also, when I mean the image for teamwin keeps flashing, I mean the literal picture of the teamwin bootup keeps flashing on screen and nothing happens.
If you didn't select the lock bootloader option in Developer Options, then you should still be able to do the fastboot oem unlock. If you have, then I think you are out of luck...
Alright, so after having my Fire HD 6 rooted for a few months I started experiencing some random restart issues. I decided to reset to Factory Defaults as I believe that it doesn't touch root (Please verify that one.)
Whenever I clicked on Facotory Reset, however; it immediately restarted and DID NOT RESET.
Then I tried to boot into TWRP and just reflash 4.5.3 (Downgrade) but when I tried to boot into recovery nothing happened, it just booted as normal. Thinking that it was just an error on my part, liking the wrong buttons, etc, I tried running 'adb reboot recovery'
This yielded the same result, just a normal reboot.
I have since unrooted my Kindle to try to update to 5.0.1 (To downgrade again)
Upon trying to update, I restart with no change just like in Factory Reset.
This leaves me with no Root, and no Recovery.
Next I tried using Fastboot to reset it, which now leaves me in a reboot loop that's stuck on the "Fire" logo.
TL;DR:
I have no root, I cannot get into recovery, I cannot access bootloader since ADB doesn't have permission without me giving it (Again, bootloop)
Overall, I'm kind of screwed, any help appreciated.
KeybladePaladin said:
Alright, so after having my Fire HD 6 rooted for a few months I started experiencing some random restart issues. I decided to reset to Factory Defaults as I believe that it doesn't touch root (Please verify that one.)
Whenever I clicked on Facotory Reset, however; it immediately restarted and DID NOT RESET.
Then I tried to boot into TWRP and just reflash 4.5.3 (Downgrade) but when I tried to boot into recovery nothing happened, it just booted as normal. Thinking that it was just an error on my part, liking the wrong buttons, etc, I tried running 'adb reboot recovery'
This yielded the same result, just a normal reboot.
I have since unrooted my Kindle to try to update to 5.0.1 (To downgrade again)
Upon trying to update, I restart with no change just like in Factory Reset.
This leaves me with no Root, and no Recovery.
Next I tried using Fastboot to reset it, which now leaves me in a reboot loop that's stuck on the "Fire" logo.
TL;DR:
I have no root, I cannot get into recovery, I cannot access bootloader since ADB doesn't have permission without me giving it (Again, bootloop)
Overall, I'm kind of screwed, any help appreciated.
Click to expand...
Click to collapse
Please help.... I see you random viewer >.>
I think if someone had an answer they would have posted. Unfortunately, fastboot doesn't work on the 2014 HDs, and it sounds like that's what put you into the bootloop. At this point I think your only option is to contact Amazon for replacement if you're still under warranty.
DoLooper said:
I think if someone had an answer they would have posted. Unfortunately, fastboot doesn't work on the 2014 HDs, and it sounds like that's what put you into the bootloop. At this point I think your only option is to contact Amazon for replacement if you're still under warranty.
Click to expand...
Click to collapse
You're sure fastboot doesn't work? I believe I have used it prior to this with no issues. (By the way, warranty is out >.<)
KeybladePaladin said:
You're sure fastboot doesn't work? I believe I have used it prior to this with no issues. (By the way, warranty is out >.<)
Click to expand...
Click to collapse
Bootloader screen doesn't indicate fastboot mode. Getvar doesn't return anything. If flash commands worked, I'm sure someone would have reported it.
If you haven't tried all button combinations, you should. (You know, hold down power; try power and vol down; try all three.) Without recovery that's all I can suggest. Sorry this happened.
I got the same problem too.
I tried to root and install gapps follow this tutorial. Everything work perfectly.
One day, my Fire's battery was empty and it turned off. I charged it and when it started, it falt in bootloop. The screen show amazon about 8sec and reboot.
I booted into twrp and flashed only 2 files update-kindle-full_ariel-20.5.2.2_user_522053520 and supersu, try to make it work but it didn't
Now, when i hold power button , "Amazon" and then "Fire" appear and it stuck there.
I tried to get into recovery by power and volume+ but didn't work, the screen show "Amazon" and reboot and stuck on "Fire" again.
What should I do now?
Sorry about my English.
So I recently got a Nexus 9. I think it was affected by the battery issues with android nougat. I rooted and used greenify and got much better battery life but decided I wanted to unroot and see if over a couple days the battery life would have gotten better. So I connected to my computer and stupidly sent the "fastboot flashing lock" command and now my Nexus is stuck in a boot loop because of TWRP. I knew that locking the bootloader would initiate a factory reset but didn't take into account that TWRP may affect that so now I can not use my Nexus. The device says it is a developer edition and not intended for personal use and I don't I know what to try. Just letting everyone know I only tried to sideloading and flash. I appreciate everyone who takes the time to read this and try to help.
Have you tried following instructions from google to flash a factory image ?
https://developers.google.com/android/images
I have but I can't flash due to the bootloader being locked and I can't sideloading because every time I tried it just errors or does nothing
AUSTIZ1997 said:
I have but I can't flash due to the bootloader being locked and I can't sideloading because every time I tried it just errors or does nothing
Click to expand...
Click to collapse
Did you try booting your nexus to fast boot and execute fastboot oem unlock?
I have, it just send me an error message
Update, I was able to finally get into the custom recovery and tried to flash the stock recovery and now it just boots into fastboot mode but I got rid of the custom recovery (as far as I know) and the boot screen that said the tablet was a developer device
Same problem here in May 2017, the OTA update prompted by Google sent the device into a bootloop. As the Bootloader was locked and there was no way to change to USB debugging mode it wasn't possible to use Recovery mode or to flash an OTA. Wiped data cache, tried all options in HBoot menu, tried flashing OTAs and full block OTA didn't work either. Just stuck in bootloop.
Repair shop encountered same problems so they then suspected the logic board. They heated it up to reflow the solder and success! Logic board may fail again through dry joint but I believe this risk can't be avoided by switching manufacturer as they all use the same component-to-board soldering practice.
Hey, I think the phone is totally brick, can anyone confirm it? Here we go
The phone came totally crazy and it has restart automatically, and went to the Fastboot mode. (i dont know if it was updating something, i had not using it). So, I've UNLOCKED it with the code that Huawei brings, till here everything is fine. The problem becames when I try to flash the CUST, CACHE, ABOOT, and the others that I think that are useless, it says
"FAILED (remote: Command not allowed)". But I can flash SYSTEM, RECOVERY, BOOT and USERDATA correctly. But that doesn't solve the problem of the LOOP RESTART, it show the Logo of Huawei and keeps restarting. I also tried 3 other stock roms, and the problem persists. Also tried putting the dload in SD with the UPDATE.app, and starting the phone with 3 buttons pressed and I have the error of "Error:update.app is a invalid package" and doens't work. (If i go to the Recovery it just stay for 1-2 seconds and automatically restart again). I don't think it could be the power button because it stays well in the Fastboot mode and also tried the CWM and works. I've been searching solutions for around 5 hours and didn't found any. I wish someone could help me, thanks in advance!
PD: I have the ADB Drivers updated.
live it