Stuck on Tux - ZTE Axon 7 Questions & Answers

So I managed to screw up my phone by trying to update Magisk to v17... thought maybe I could sort it by flashing boot.img (I'm on B04) but no dice. Then I flashed the whole B04 ROM again, still no go.
How do I get this puppy running again?

Try pressing the power button twice and see if it moves from Tux.
It has worked in some other cases.
I hope this helps

Related

[Q] Unable to flash any files

Happy New Year!
I was flashing 4.4.2 last nite using fastboot commands. All was well until, on last file which was system.img. During this flash, it seemed to just hang there. Then, unexpectedly, while waiting things out, I got a BSOD and had to reboot the pc. Now, I cannot flash anything. I can boot the Nexus into bootloader ok, but it just stays there. Cannot boot into recovery, it just goes back to bootloader. I can use fastboot to reboot, flash cache and userdata, but not recovery.img or bootloader-xxx-xxx.img or system.img or boot.img. It just hangs.
How can I reformat or get a recovery or system image onto my Nexus? Hopefully the answer doesn't include advice such as putting it under my car tire.....
Thanks :crying:
Brrrr ......sure is cold out here.......all alone 'n such.
I'm happy to report that my problem has solved itself.
After spending all morning trying to solve my issues, I decided to give up for now and powered down the now useless tablet.
This evening, after seeing ( disappointedly) no replies to my thread, I decided to try one more time. For inexplicable reasons, it all worked. I was able to successfully flash all image files using fastboot. Why it decided to work this time and not before remains a mystery to me. I did nothing different that I could tell. Same commands, same sequence etc.
After flashing system.img, I rebooted the device and viola, 4.4.2 kitkat is in the house!
The BSOD I discover, was due to CPU overheating, reaching temps up around 60 C.
I really don't know what effect or impact that might have had on my problems. I'll need a higher IQ to sort that one out. Whatever, problem gone.
I wish everyone a happy new year. :good:

Successful Root of BOK3, but then I messed up, any help would be appreciated.

Hello,
I followed the guide for the Working Root Method For 5.0 Lollipop ROms and I was on BOK3 and everything actually worked and the phone was rooted, good to go. I was able to start the phone, installed busybox and safestrap, everything mentioned on the page, phone was good and working. However, I made a mistake. When I went to wipe the data so I could install a ROM I somehow managed to format, or wipe something I was not supposed to. Now, everytime I turn the power on it sticks on the Samsung Galaxy S5 page with the "Custom" wording and the open lock. I have been able to get to the download mode and when I tried to Odin to G900VVRU2BOK3_G900VVZW2BOK3_G900VVRU2BOK3_HOME.tar it says it passes, but still freezes on the "Custom" power on page. I honestly don't know what else I can do to try to get the device to power on/restore it, I've tried the N2 Kernal from the same page as the the tar and it doesn't get me anywhere, though it also says it passes. I'll be up for work in a few hours and if you have anything for me to try or requests for additional information I'll see what I can.
I have attempted to run the root bat file, just to see if it works, but that will not even list the phone.
Thank you,
Dale.
If you flash NK2 kernel and try to boot into lollipop, you're definitely going to freeze on boot because lollipop can't boot with a kitkat kernel.
Flash BOK3 stock image in Odin again. That image has the kernel in it also, so you don't need to flash anything else. Then boot into stock recovery (hold vol+UP and power), clear cache, then reboot.
If that doesn't work, boot back into stock recovery, clear cache and factory reset, then reboot.
That may work.
Thanks for the help. I don't know what I was thinking last night/this morning. All set now! For some reason now it didn't root when I went back through the procedures, but that is a problem to solve at a different time. I appreciate your calm response to my panic.
dhessjr2291 said:
Thanks for the help. I don't know what I was thinking last night/this morning. All set now! For some reason now it didn't root when I went back through the procedures, but that is a problem to solve at a different time. I appreciate your calm response to my panic.
Click to expand...
Click to collapse
You're welcome

Stuck in Boot Recovery

I tried to use Yemenroot to root my phone and ended up stuck in a Boot recovery and no matter what I try I cant get out of it. What suggestions could anyone give me? Ive tried the factory reset option and the clear cache. neither helped. Thanks in advance!
Not sure exactly what you mean by "stuck".
Are you saying that every time it reboots it boots into the recovery?
If so, then:
- Pull the battery
- Reinsert the battery*
- Boot the phone by holding down Vol-Down+Home+Power*
When it asks you if you want to go into Download Mode, select Cancel (Vol-Down iirc)
The phone should boot into the regular ROM, albeit completely unconfigured, as you have already performed a factory reset (which wasn't needed btw).
If the Stock ROM won't boot you will have to flash the Stock ROM in Odin
*don't have the phone plugged in to a PC at this point or it will spontaneously reboot.
bftb0 said:
Not sure exactly what you mean by "stuck".
Are you saying that every time it reboots it boots into the recovery?
If so, then:
- Pull the battery
- Reinsert the battery*
- Boot the phone by holding down Vol-Down+Home+Power*
When it asks you if you want to go into Download Mode, select Cancel (Vol-Down iirc)
The phone should boot into the regular ROM, albeit completely unconfigured, as you have already performed a factory reset (which wasn't needed btw).
If the Stock ROM won't boot you will have to flash the Stock ROM in Odin
*don't have the phone plugged in to a PC at this point or it will spontaneously reboot.
Click to expand...
Click to collapse
Thanks for responding! Yes you are correct that it boots in recovery. Home+Power+Vol Down brings me up to a Warning screen, says if i want to download a custom OS to hit vol up, if I want to cancel press Vol Down. I press vol down and it puts me back into recovery boot again.
If you are familiar with YemenRoot maybe I just screwed up doing that and can still continue with that to fix it? I ran the program, choose Tar.1 in Oden and hit start. Went back to the command prompt and "pressed any key" to continue. It went to 2). Rooting, but never went any farther. The phone automatically rebooted but into recovery mode. That was where I thought something went wrong and stopped.
EDIT: I went back again and pressed vol up to see where it would take me. It takes me back to the downloading screen like it showed in one of the steps for the root. I ran tar.1 and tar.2 and was able to get the phone usable again. No luck with the YemenRoot though Tried going through to do it a second time and came up with the same issues. It just sits on (2) Installing root forever and the phone eventually reboots into Recovery again. Im not sure how to get Yemen to work correctly, and no one seems to respond in the yemenroot post that I found on here.
trizzypballr said:
Home+Power+Vol Down brings me up to a Warning screen, says if i want to download a custom OS to hit vol up, if I want to cancel press Vol Down. I press vol down and it puts me back into recovery boot again.
Click to expand...
Click to collapse
Well that's a little odd & unexpected.
[Edit] - Oops, I didn't initially see the part about you getting it working [Edit]
I can't help you out with Yemenroot, I've never used it. (But I suspect the stock ROM needs to be booting in order for it to work, so you are going to have to do the Odin Flash no matter what)
I can suggest that if you are going to keep trying w/ yemenroot, I would only minimally configure the (factory reset) stock ROM in case you end up back in the same spot again.
PS if you know how to create Odin .tar.md5 files, you could create a "reduced" stock flash for Odin containing only boot.img & system.img. That way you could "dirty flash" those two in Odin if you got in the same situation again... without needing to do a factory reset.
good luck
I flashed using odin N900VVRUEOF1_N900VVZWEOF1_VZW. It took the flash but is now stuck on RED Verizon screen. Ity is like it is doing something but not fully recovered?? Any suggestions?
bftb0 said:
I can't help you out with Yemenroot, I've never used it.
Click to expand...
Click to collapse
Then how in the world did you root your phone? I thought those were the only ways to get your device rooted?
RaaidR said:
Then how in the world did you root your phone? I thought those were the only ways to get your device rooted?
Click to expand...
Click to collapse
I used Kingo root when my phone was on MJ7 and I never upgraded thereafter.
Even now my phone is only on the MJE bootloader (it can be rolled back to MJ7).
The version of TowelRoot that I have (v3?) currently seems to work on all stock versions from MI9-NC4, but it wasn't yet released when I rooted.
I'm not planning on upgrading my bootloader past NC2 until such a time as I am going to sell the phone, or there is a way to upgrade only the bootloader components while preserving root in the ROM.* My motivation for that is quite frankly to avoid using the yemen root tool.
*So that the bootloader unlock can be performed immediately thereafter, to regain bootability of a custom recovery. IMO this should be trivial so long as OB6/OF1 bootloader will boot a rooted-stock kernel+ROM from 4.4.x (NC4, NJ6, NK1). Frankly I believe that to be more likely than a 4.4.x bootloader booting a 4.3.x rooted-stock kernel+ROM (MI9/MJ7/MJE).
bftb0 said:
I used Kingo root when my phone was on MJ7 and I never upgraded thereafter.
Even now my phone is only on the MJE bootloader (it can be rolled back to MJ7).
The version of TowelRoot that I have (v3?) currently seems to work on all stock versions from MI9-NC4, but it wasn't yet released when I rooted.
I'm not planning on upgrading my bootloader past NC2 until such a time as I am going to sell the phone, or there is a way to upgrade only the bootloader components while preserving root in the ROM.* My motivation for that is quite frankly to avoid using the yemen root tool.
*So that the bootloader unlock can be performed immediately thereafter, to regain bootability of a custom recovery. IMO this should be trivial so long as OB6/OF1 bootloader will boot a rooted-stock kernel+ROM from 4.4.x (NC4, NJ6, NK1). Frankly I believe that to be more likely than a 4.4.x bootloader booting a 4.3.x rooted-stock kernel+ROM (MI9/MJ7/MJE).
Click to expand...
Click to collapse
Why do you not want to use the yemen tool? The one for Windows 10 worked flawlessly for me.
RaaidR said:
Why do you not want to use the yemen tool? The one for Windows 10 worked flawlessly for me.
Click to expand...
Click to collapse
The ends don't justify the means.
No disclosure of method.
No prior or subsequent author activity on XDA
Use of a PC
No Windows 10 box that I am willing to expose to random executables from unknown authors on the internet.
bftb0 said:
The ends don't justify the means.
No disclosure of method.
No prior or subsequent author activity on XDA
Use of a PC
No Windows 10 box that I am willing to expose to random executables from unknown authors on the internet.
Click to expand...
Click to collapse
I for sure understand not wanting to risk it. I really didn't either but didn't have another choice other than to stay unrooted.
DjRenigade said:
I flashed using odin N900VVRUEOF1_N900VVZWEOF1_VZW. It took the flash but is now stuck on RED Verizon screen. Ity is like it is doing something but not fully recovered?? Any suggestions?
Click to expand...
Click to collapse
Use Jasmine ROM 6.1, it is based on OF1 and works fine.
Sent from my SM-N900V using Tapatalk

Deleted Bootloader on LeEco S3 X626

A couple weeks back I deleted the OS off of my phone while messing with TWRP recovery trying to install a custom ROM. I looked around the forums and i got my phone to the point where It booted into a stripped down version of android with stock recovery on it, although everything was mirriored and backwards. But when i tried to install the stock rom for my LeEco S3 with stock recovery it got stuck i a boot loop and I couldn't turn off the phone or boot into recovery or anything. So i let it keep booting until it ran out of battery and died. So then i decided i would put the stripped down version back on and start again.
So I went back to my sp flash tool and reinstalled all the partions except the boot and recovery partitions (according to the steps on the forum) but my phone still wont boot into anything, it is completely black and wont boot into recovery or fastboot, and im running out of ideas on how to fix this phone :crying:
After pretty much giving up all hope of fixing my phone, i figured i would try the format option in the flash tool and then reinstall all of the pattitions. I selected format all flash, not doing proper research first, and now i cant even reinstall partions, I get a STATUS_BROM_CMD_SEND_DA_FAIL error anytime i try to flash the partitions.
can you at least get the phone to fastboot mode?
microMXL said:
can you at least get the phone to fastboot mode?
Click to expand...
Click to collapse
No I cannot, The screen is completely black and nothing comes on at all if I hold down the power button.
well damn, looks like a soft brick, it can be repaired but not gonna lie, it is a pain in the butt...
https://forum.xda-developers.com/le-2/help/bricked-le-s3-x626-flashing-twrp-power-t3715937
the guys have made an awesome guide on that thread.
microMXL said:
well damn, looks like a soft brick, it can be repaired but not gonna lie, it is a pain in the butt...
https://forum.xda-developers.com/le-2/help/bricked-le-s3-x626-flashing-twrp-power-t3715937
the guys have made an awesome guide on that thread.
Click to expand...
Click to collapse
I have already looked through that thread, and i have done everything up to the flashing process, and then I get a STATUS_BROM_CMD_SEND_DA_FAIL (0xC0060003) Error. I looked it up but the only option I haven't tried to solve the issue is to remove the battery, which i cannot do currently because to remove the battery you need a heat gun to remove the screen to get to the rest of the phone. I think I've given up all hope on fixing this phone and may just begin saving for a new one.
Sgt.Collywobbles said:
A couple weeks back I deleted the OS off of my phone while messing with TWRP recovery trying to install a custom ROM. I looked around the forums and i got my phone to the point where It booted into a stripped down version of android with stock recovery on it, although everything was mirriored and backwards. But when i tried to install the stock rom for my LeEco S3 with stock recovery it got stuck i a boot loop and I couldn't turn off the phone or boot into recovery or anything. So i let it keep booting until it ran out of battery and died. So then i decided i would put the stripped down version back on and start again.
So I went back to my sp flash tool and reinstalled all the partions except the boot and recovery partitions (according to the steps on the forum) but my phone still wont boot into anything, it is completely black and wont boot into recovery or fastboot, and im running out of ideas on how to fix this phone :crying:
After pretty much giving up all hope of fixing my phone, i figured i would try the format option in the flash tool and then reinstall all of the pattitions. I selected format all flash, not doing proper research first, and now i cant even reinstall partions, I get a STATUS_BROM_CMD_SEND_DA_FAIL error anytime i try to flash the partitions.
Click to expand...
Click to collapse
Help, pls I got the exact same problem... Pls any solution to it... I have been at it for a month now no solution, help
same problem. after twrp flash x626 not boot

Pretty sure I messed up, can anyone help?

Hi guys!
First off, I'm both new to this and not on a lot of sleep, which is a terrible combo to start off with.
So, naturally, I decided today was the day I'd root my phone (Global OnePlus 8 Pro IN11AA from Amazon).
However, right before I started I installed the 11.0.5.5 update OTA through the settings app. After that, I turned on
OEM unlocking and had a bit of trouble getting my PC to recognize the phone over USB, so I switched to a laptop,
which worked just fine. I unlocked the bootloader with the "fastboot flashing unlock" command.
After that, I found a boot.img, and went to patch it in Magisk. I used the latest Magisk Canary for this task. Here's
the smart part: I used the 10.5.5 boot.img and got to the Qualcomm crash dump. From there, I managed to get back
into fastboot and flash a clean 11.0.4.4 boot.img, which ended up working somehow and I got back to a working phone,
albeit with an unlocked bootloader. After that, I figured: well, if the 11.0.4.4 boot.img worked, maybe I could just patch
that and flash it? I couldn't find anything for 11.0.5.5. Anyways, I patched it with the same Magisk Canary build and
flashed it. I'm stuck in a boot loop right now and that original flashing-the-stock-11.0.4.4-img thing isn't giving me any
luck this time.
I was going to try and use the MSM tool, but I can't get into EDL mode for my life (I'm plugging in the phone to the computer after starting to hold vol up and vol down, but it keeps putting me into fastboot), and the tool isn't showing my phone
no matter what I do (I've got instantnoodlep_15_O.34_210201, hope that's the right version).
Anyone know what I can do from here? My end goal is a Magisk-only rooted phone on 11.0.5.5.
Edit: Got the tool to work, back in business.
Time to try and root again.
Probably should sleep on it. Sleep deprivation leads to bad judgement and mistakes.
At least have some nicotine as it helps to restore mental functionality especially when tired.
blackhawk said:
Probably should sleep on it. Sleep deprivation leads to bad judgement and mistakes.
At least have some nicotine as it helps to restore mental functionality especially when tired.
Click to expand...
Click to collapse
I actually just managed to successfully root using Magisk 21.4 and the latest Magisk Manager. The tool restored me to 11.0.4.4 and everything worked great from there. Now I'm facing an extremely weird issue- if I press the power button my phone crashes.
blackhawk said:
Probably should sleep on it. Sleep deprivation leads to bad judgement and mistakes.
At least have some nicotine as it helps to restore mental functionality especially when tired.
Click to expand...
Click to collapse
I'm pretty sure this suggestion illegal in the most of the World.

Categories

Resources