I've followed every guide possible and I end up in the same spot almost everyone else ended up that I can see, and that's after flashing TWRP, it stays stuck on your device is booting up.
I read on TWRP's site that sometimes phones auto write over it so you have to boot into recovery right after typing in fastboot reboot but that never works.
I've seen some TWRP's are dedicated to Honor 8, and that didn't seem to work.
https://twrp.me/devices/huaweihonor8.html
I got
twrp-3.2.1-0-frd.img
I flash it at the white bootloader screen. and that's as far as I can get, it never goes into TWRP.
Am I missing a step here?
My guess is that your bootloader is locked. It's literally a click of a button to install, and the only thing that would block that is a locked bootloader.
Nah, it's the screen that says "your device cannot be trusted because it's unlocked" or something like that and at the bottom it just stays at booting up. I've done everything and it never goes into TWRP as if it never flashed in, even though the adb command screen said it did.
[edit] Well, it finally worked, I just kept doing the same thing over and over and it finally took. No idea why lol. Now it's just not wanting to take SuperSU. It starts flashing then immediately restarts, looks like it stops on the "creating image" part?
I had the same trouble but I installed an older version of TWRP and it worked fine with B405.
zinko_pt said:
I had the same trouble but I installed an older version of TWRP and it worked fine with B405.
Click to expand...
Click to collapse
That's what I ended up doing, supersu wouldn't flash so I used that other new popular one and started right up.
Use Huawei Multitool
Related
edit: Nevermind. 3rd try is a charm. Can't figure out how to delete this thread.....
Of all things to get hung up on or have trouble with, it's freakin rooting that is giving me fits. I just got my Nexus S today and I have used the toolkit to unlock the bootloader and install drivers and that worked fine. Now, I get to rooting/flashing recovery (TWRP) and I get to the step "waiting for your device to finish booting back up..." and it just stays in recovery. If I manually reboot, it does so just fine, but it's not rooted. I'm on 4.1.2.
Did you do anything to get it to work? I am having the same problem of being stuck on waiting for phone to boot. No problem with unlocking.
korsjs said:
Did you do anything to get it to work? I am having the same problem of being stuck on waiting for phone to boot. No problem with unlocking.
Click to expand...
Click to collapse
I just manually booted from recovery. I didn't have to do anything outside of what was instructed.
I had my OPO for about two week before this bug had happened, it was on the charger when suddenly the screen flashed as if it was updating, and it counted from 1 to 121 and then restarted. I though it was just updating automatically until i came back to use it and was stuck at the bootloader animation and just rotating, but never actually loading.
I looked up online on this issue and found out its a common bug, and i went ahead and put my phone in fastboot and unlocked the bootloader and it went fine except that it didn't restart like the videos I saw, I though it was an error so i ran the command to show the info and it turns out i I am unlocked already. So i went ahead and tried to flash the stock recovery again but i keep getting FAILURE:Failed to erase partition or some times i get failed to flash. So I booted into twrp recovery, but I don't have it flashed through a boot command i looked up the terminal which showed failed to mount the E:/data and the cache folder or anything i tried it would either fail or have no access to it. Is my OPO bricked to death or can it be fixed.
Please if anyone can help me I would appreciate it much.
P.S. (This phone that broke I bought off a china retailer, although i have the international copy bought from the OPO store.)
red_devilsrr said:
I had my OPO for about two week before this bug had happened, it was on the charger when suddenly the screen flashed as if it was updating, and it counted from 1 to 121 and then restarted. I though it was just updating automatically until i came back to use it and was stuck at the bootloader and just rotating, but never actually loading.
I looked up online on this issue and found out its a common bug, and i went ahead and put my phone in fastboot and unlocked the bootloader and it went fine except that it didn't restart like the videos I saw, I though it was an error so i ran the command to show the info and it turns out i I am unlocked already. So i went ahead and tried to flash the stock recovery again but i keep getting FAILURE:Failed to erase partition or some times i get failed to flash. So I booted into twrp recovery, but I don't have it flashed through a boot command i looked up the terminal which showed failed to mount the E:/data and the cache folder or anything i tried it would either fail or have no access to it. Is my OPO bricked to death or can it be fixed.
Please if anyone can help me I would appreciate it much.
P.S. (This phone that broke I bought off a china retailer, although i have the international copy bought from the OPO store.)
Click to expand...
Click to collapse
I'd suggest using one of these methods:
http://forum.xda-developers.com/showthread.php?t=2970390
http://forum.xda-developers.com/showthread.php?t=2991851
http://forum.xda-developers.com/oneplus-one/help/guide-unbrick-oneplus-one-t3013732
And one thing...
red_devilsrr said:
...was stuck at the bootloader and just rotating, but never actually loading...
Click to expand...
Click to collapse
What you're talking about there is the boot animation, not the bootloader, they're two very different things.
Transmitted via Bacon
timmaaa said:
I'd suggest using one of these methods:
http://forum.xda-developers.com/showthread.php?t=2970390
http://forum.xda-developers.com/showthread.php?t=2991851
http://forum.xda-developers.com/oneplus-one/help/guide-unbrick-oneplus-one-t3013732
And one thing...
What you're talking about there is the boot animation, not the bootloader, they're two very different things.
Transmitted via Bacon
Click to expand...
Click to collapse
I have tried one of the methods there but the problem is not with the method its with the flashing of the phone itself it keeps failing or even when i try to erase a partition.
And i will be changing that to the bootloader animation.
http://forum.xda-developers.com/showthread.php?t=2820912
I'm on my second oneplus after I shattered the screen on the first, bought this one used and for whatever reason the bootloader wouldn't unlock using fastboot commands. Sounds like the same thing is going on with yours. I finally got mine unlocked with the tool in that link.
red_devilsrr said:
I have tried one of the methods there but the problem is not with the method its with the flashing of the phone itself it keeps failing or even when i try to erase a partition.
And i will be changing that to the bootloader animation.
Click to expand...
Click to collapse
Ok, perhaps you need to try the methods that you haven't tried though. And it's just boot animation, not bootloader animation.
Transmitted via Bacon
Ok, I've been reading around the forum for about a week, trying to solve a problem with an original moto g (falcon). Basically my cousin got the moto g a few years back, and I, in my ignorance, tried to root the device for him. What I can remember was oem unlocking the bootloader with Motorola's unlock code through their website and adb. then my cousin freaked about the warranty warning on the boot animation, and decided against it. So cut to now, I'm a little more experienced, the phone's years old now, and he'd like to refresh it with a new rom, which I suggested, trying to help him. So forgetting what I'd originally done those years ago, I started the process of rooting the phone, installing a custom recovery, to hopefully put a lighter rom on it for him.
OK so it's a UK Retail on tesco mobile, moto g xt1032 running Android 5.1.
in bootloader menu it says "Device Locked status 2", dunno what this is in relation to.
first I checked the bootloader was still unlocked, and adb said it was. so I tried to use CF-autoroot to finish the job, but there was issues. it restarted the phone into fastboot mode, but when the script started, pc end did nothing, on the phone it said, "flashing unlock" and just sat there for 10-15mins doing nothing (i left it the time, just incase it was doing it).
So i read a little more, and found because i'd already unlocked the bootloader, I could just flash a custom recovery and root from adb? so I downloaded the latest twrp and tried. I was unable to do so. it said the partition wasn't the right size? should have documented it, but really didn't expect to run into any problems.
So I restarted and tried to do my usual fallback, and flash the factory image and start again, But couldn't find a source for the specific img, and tried to keep fighting on.
So I noticed that the phone wouldn't respond to adb or fastboot once in fastboot mode, when in android with usb debugging, no problems, in fastboot, didn't show up as adb devices?
I tried booting into the recovery from the bootloader menu, and got a no command. So there isn't a recovery, and I can't flash a new one? if i could find the stock recovery, I would try that.
so apart from deleting all his apps and settings, I hadn't solved the problem at all, and had to leave the job there as I couldn't find a solution.
I know this isn't the most detailed, but I've done this with quiet a few phones now, and felt I was pretty competent. I see everyday as an excuse to learn more, and like to think I have humility. So, I'm assuming I did something those years ago to damage the recovery? I'm running out of ideas, and was hoping someone could point me in the right direction?
I've lurked on xda for years, and learned so much about this kind of thing through my past experiences, but I'm stumped this time, and feel obliged to resolve the problem, as it was me who caused it.
TL DR
Can't flash recovery, no command when I try to open recovery, trying to either factory image back, or root/custom recovery it.
any insight would be much appreciated.
Hi. I just rooted and installed CM13 on an old XT1034 about two days ago. I am also sort of a ROM noob, I have ROMed a few devices, but usually but following strict step by step guides I have found here on XDA. Over the years I have some minor understanding of the process now.
I also got the "No command screen" when trying to get into TWRP recovery. The issue seems to be that if you reboot via ADB and the ROM launches it will automatically rewrite the recovery to the stock one, and when you try to go to recovery from fastboot, it gives you the "no command" error. Apparently you can get to the stock recovery from there by a hardware key combo, something like holding up vol for 10 sec then a quick press of power (I can't remeber the exact key sequence or what forum I read it in). If it does this you have to reflash TWRP again. This issue is mentioned here (http://wiki.cyanogenmod.org/w/Install_CM_for_falcon) in step 8 about installing recovery. What I ended up doing was after the flash of TWRP via ADB, I manually powered down, then manually bood into fastboot by holding volume down and power, and selecting recovery. This was a bit fiddly and I had to attempt it a few times but eventually it worked and TWRP installed.
The issue with the phone not being recognized may be due to incorrect drivers. I had no issue with this because I installed the official driver package from Motorola. It is available in their website in the developer section. I don't have the URL right now.
Hopefully this helps, for me CM13 Official has been an a stable fresh start for this old device.
So I have a recent issue that I have not seemed to resolve. Today, under normal use, my pixel's screen went black and I have not been able to power it back on. I was using the pixel dust rom when the issue happened. I have booted into twrp and tried to factory reset but the screen even went black during the wipe. After that, I booted into the bootloader and attempted to flash google's factory image. The phone actually stays on during the bootloader session. It seemed that I was able to flash the factory rom but once I tried to reboot, the same thing happens. The boot animation will play but that's as far as it gets until the screen goes black once again.
If anyone has had this issue or if anyone has an idea on how to resolve this issue, please respond quickly.
Much Appreciated!
After the screen goes black, are you still able to communicate with the device over adb/fastboot? Have you tried reflashing the factory image (make sure the checksum is correct!)? If you put the phone in the refrigerator for a bit, will it last longer before going black (i.e., bad solder)?
post-mortem said:
After the screen goes black, are you still able to communicate with the device over adb/fastboot? Have you tried reflashing the factory image (make sure the checksum is correct!)? If you put the phone in the refrigerator for a bit, will it last longer before going black (i.e., bad solder)?
Click to expand...
Click to collapse
So during fastboot, the screen actually doesn't go black. I am still able to remain communication and That is when I tried flashing the factory image. How do you make sure that the checksum is correct? I didn't receive any errors during the flash indicating that it didn't flash properly.
If you're using Windows, Hashtab is a good, free checksum program with a GUI.
Download
Info/Review
On Google's image download page, copy the SHA-256 listed, and compare it to what you have locally (which you used to flash onto your phone).
how to boot into twrp? almost the same issue to you, adb cant find my phone.
jcd173339 said:
So I have a recent issue that I have not seemed to resolve. Today, under normal use, my pixel's screen went black and I have not been able to power it back on. I was using the pixel dust rom when the issue happened. I have booted into twrp and tried to factory reset but the screen even went black during the wipe. After that, I booted into the bootloader and attempted to flash google's factory image. The phone actually stays on during the bootloader session. It seemed that I was able to flash the factory rom but once I tried to reboot, the same thing happens. The boot animation will play but that's as far as it gets until the screen goes black once again.
If anyone has had this issue or if anyone has an idea on how to resolve this issue, please respond quickly.
Much Appreciated!
Click to expand...
Click to collapse
bush911 said:
how to boot into twrp? almost the same issue to you, adb cant find my phone.
Click to expand...
Click to collapse
If adb cant detect your phone, it looks like the only way that you're going to boot into twrp is through the bootloader mode (if you had it previously installed). Holding down volume down and power will get you into bootloader and then using the volume buttons, you can cycle through the options until you find "recovery". Pressing the power button will select that option.
post-mortem said:
After the screen goes black, are you still able to communicate with the device over adb/fastboot? Have you tried reflashing the factory image (make sure the checksum is correct!)? If you put the phone in the refrigerator for a bit, will it last longer before going black (i.e., bad solder)?
Click to expand...
Click to collapse
It looks like your freezer method works. Putting it in the freezer actually gets the phone to boot completely into google's factory image. its usuable for about a minute until the problem of freezing and turning off reoccurs. It feels like the phone warms up while running so maybe i have a hardware problem rather than software.
I seem to have the exact same problem with my pixel 32gb, my device was not rooted, nor did I had any custom recovery but the bootloader was unlocked. The issue happened one day while I was browsing the device went black right infront of me. It was not like I did a dirty flash/mod or something. I'm able to detect my pixel via fastboot, able to flash the factory image no problem, but does not boot up after successful completion of the flashing, it just goes black after "google" logo. Anyone found a solution yet??
thank you sir, I have twrp installed previously. but the screen doesnt turn on so I can't choose the recovery model. and try to hold the power button for a while the phone will become warm. no other response:crying:
jcd173339 said:
If adb cant detect your phone, it looks like the only way that you're going to boot into twrp is through the bootloader mode (if you had it previously installed). Holding down volume down and power will get you into bootloader and then using the volume buttons, you can cycle through the options until you find "recovery". Pressing the power button will select that option.
Click to expand...
Click to collapse
Thufail19 said:
I seem to have the exact same problem with my pixel 32gb, my device was not rooted, nor did I had any custom recovery but the bootloader was unlocked. The issue happened one day while I was browsing the device went black right infront of me. It was not like I did a dirty flash/mod or something. I'm able to detect my pixel via fastboot, able to flash the factory image no problem, but does not boot up after successful completion of the flashing, it just goes black after "google" logo. Anyone found a solution yet??
Click to expand...
Click to collapse
Maybe try locking the bootloader? I might try to do that since you and i both are experiencing the same problem with an unlocked bootloader. But i can't see why that would impact anything.
Hi all, I've been on Lineageos 16 for a while and finally decided to update to 17. I went ahead and acquired the latest twrp from mauronofrio. I flashed on both AB slots stock OS and then proceeded to flash the latest lineageos with of course gapps, magisk and twrp. However, once finished I booted to system and got stuck in the lineageos loading screen.
Thinking I might've done it wrong, I reded my steps and still the same. This took me almost the whole day, but nothing worked. So I decided to go back to 16 and then everything got worse. Suddenly I got an error that slot A was denied and now I somehow cannot even access twrp anymore. I've tried all different twrps, from the official one to blu_spark one and mauronofrio. Nothing worked, I would either get the Fastboot mode logo or just a black screen with the led light on. Now my phone is stuck with these outcomes.
I can access fastboot so I decided to use the flash-all bat but that didn't work either. I can't even boot to system as I get a black screen again with the led light on. I seem to be stuck at this and now I regret having even attempted to update my lineageos. I didn't even get the chance to backup my data. So idk if there's a unbrick tool that doesn't erase all your data as I cannot afford to lose my data.
Any help is appreciated. My phone is currently in fastboot mode and I'm completely worned out. I spent the whole day trying to fix it, checked so many forums and I feel like it only got worse. If more information is needed let me know. (And yeah the bootloader is unlocked.)
Mangob0y said:
Hi all, I've been on Lineageos 16 for a while and finally decided to update to 17. I went ahead and acquired the latest twrp from mauronofrio. I flashed on both AB slots stock OS and then proceeded to flash the latest lineageos with of course gapps, magisk and twrp. However, once finished I booted to system and got stuck in the lineageos loading screen.
Thinking I might've done it wrong, I reded my steps and still the same. This took me almost the whole day, but nothing worked. So I decided to go back to 16 and then everything got worse. Suddenly I got an error that slot A was denied and now I somehow cannot even access twrp anymore. I've tried all different twrps, from the official one to blu_spark one and mauronofrio. Nothing worked, I would either get the Fastboot mode logo or just a black screen with the led light on. Now my phone is stuck with these outcomes.
I can access fastboot so I decided to use the flash-all bat but that didn't work either. I can't even boot to system as I get a black screen again with the led light on. I seem to be stuck at this and now I regret having even attempted to update my lineageos. I didn't even get the chance to backup my data. So idk if there's a unbrick tool that doesn't erase all your data as I cannot afford to lose my data.
Any help is appreciated. My phone is currently in fastboot mode and I'm completely worned out. I spent the whole day trying to fix it, checked so many forums and I feel like it only got worse. If more information is needed let me know. (And yeah the bootloader is unlocked.)
Click to expand...
Click to collapse
tipically when phone starts on fastboot and Is recognized from PC there Is always a chance to make It working again
I am used to use the *fastboot.zip when i run on throubles... there Is also the "All-In-One" tool, but before... dis you run the "flash all.zip" file running with admin priviledges?
basically type "cmd" tight click on "command prompt" then "run as administrator"
once in dos prompt type 'cd "full path of unzipped folder"'
then "flash all"
(you can also use powershell, it's the same, important Is the "run as administrator" start option")
I was able to finally get into twrp and backup important files. Did a clean install with msmdownloadtool to bring it back to stock. I think my rooting days are on hiatus for now. What a stress this was.
This thread can be closed. Thank you!