• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Stock Files: Deodexed & Unmodified ROMs, Recovery, Kernel

I have flashed the img with flashify.
After reboot the phone, it took very long time stuck on red led, so I long pressed the power button.
Now, when I press power and volume down together, the phone still goes to factory recovery not twrp recovery.
Is there anything I missed?
It does not seem like you missed anything, but it sounds like either twrp was not flashed correctly (not your fault) or your bootloader replaced it after it was flashed. Without the device it will be hard for me to figure it out. You could try to see if you have install-recovery.sh in /system/etc or /system/bin. If so, that may be replacing your recovery. /system/recovery-from-boot.p may also do the same. You can rename these files if you have root, and try again if you are up for some experimenting. I was told you may not have write access to /system however so you may not be able to rename them at all. I will keep thinking.
 
Upvote 0
Flashify reports it has been flashed correctly, and asked for if want to flash more imgs.
I guess that bootloader has replace the recovery.
I am not able keep testing now, as the phone is not belong to me now.
I borrowed it for the test. I have there are some else who is willing to test it.

It does not seem like you missed anything, but it sounds like either twrp was not flashed correctly (not your fault) or your bootloader replaced it after it was flashed. Without the device it will be hard for me to figure it out. You could try to see if you have install-recovery.sh in /system/etc or /system/bin. If so, that may be replacing your recovery. /system/recovery-from-boot.p may also do the same. You can rename these files if you have root, and try again if you are up for some experimenting. I was told you may not have write access to /system however so you may not be able to rename them at all. I will keep thinking.
 
  • Like
Reactions: SuperR
Upvote 0
It is not hard to make kingroot success, but without kingoroot, the root authorization by kingroot does not work.

You can try to run kingroot and Antutu video test together, and run kingoroot from PC when kingroot over 20%.

Working on trying it out, would be so much easier if Kingroot was more consistent on getting temproot. I'm only getting it about 5% of the time, using both Kingroot/Kingoroot or Kingroot/Antutu.
 
Last edited:
Upvote 0
Last I knew with ZTE's.. They made Fastboot unavailable without Root. What about getting temp Root and then using it to ADB "reboot Fastboot" and whatever terminal cmd to exchange the TWRP image or run the cmd from terminal within Android itself? Just a thought.. I'm actually on my way to Best Buy & grab one or 2 devices for this project..
@SuperR: You want one as well? Mine will be just a last ditch backup
 
  • Like
Reactions: SuperR
Upvote 0
Last I knew with ZTE's.. They made Fastboot unavailable without Root. What about getting temp Root and then using it to ADB "reboot Fastboot" and whatever terminal cmd to exchange the TWRP image? Just a thought.. I'm actually on my way to Best Buy & grab one or 2 devices for this project..
@SuperR: You want one as well? Mine will be just a last ditch backup
I don't think your fastboot trick will work but it is worth a try. Hopefully I won't need one of these devices lol. Thanks for the offer but no need to worry for now. Honestly I would recommend getting a different device if you want to spend money. The Moto E 2015 has an unlockable bootloader and just got official cm13 support for example ;)
 
  • Like
Reactions: bcrichster
Upvote 0
I don't think your fastboot trick will work but it is worth a try. Hopefully I won't need one of these devices lol. Thanks for the offer but no need to worry for now. Honestly I would recommend getting a different device if you want to spend money. The Moto E 2015 has an unlockable bootloader and just got official cm13 support for example ;)
Ooh.. [emoji15] OK then.. Never mind I guess. I'll just grab this $20 Speed device (new @ Best Buy). It listed in BB CPU as the "Warp Speed"! Lmao
 
  • Like
Reactions: SuperR
Upvote 0
OK.. I have said "Speed" device and Bluetoothing KingRoot v4.81, Super-SuMe-Pro, Flashify, Rashr, DingDong_Root, online Nandroid.. Are there any special commands or desired processes, Mr. @SuperR?
As in: flash fastboot specific recovery (whatever) from terminal..?? Cuz if not, I'll try Super-SuMe-pro as a last-ditch ONLY effort. Trying to avoid Kingo cuz Super-SuMe only does KingRoot..
 
Last edited:
Upvote 0
I was using 4.8.1 and turned off update. I don't know if 4.8.5 work or not.
atutu vidoe test always stop once it is not on front, so I try to reactive it after start kingroot.
What version Kingroot do you use? I was using 4.8.1 before, been using 4.8.5 since this morning and haven't had any luck at all.
Any tips on keeping the apps alive in the background? ~75% of the time one of the 3 gets killed.
 
Upvote 0
I have a ZTE Speed my mother-in-law brought me that will not boot. It will show the white zte screen and that's it. I can get to recovery, I guess it's recovery, where you can reset/wipe data, clear cache, apply update from sd card-adb sideload-cache. This device has never been rooted that I know of. Is anybody here that could help me get this thing to boot? Thanks
 
Upvote 0
I have a ZTE Speed my mother-in-law brought me that will not boot. It will show the white zte screen and that's it. I can get to recovery, I guess it's recovery, where you can reset/wipe data, clear cache, apply update from sd card-adb sideload-cache. This device has never been rooted that I know of. Is anybody here that could help me get this thing to boot? Thanks
You might be out of luck if you can't boot to Android. The bootloader is unlockable (at least so far) so you would need Android booting to gain temp root and flash the TWRP posted above that has yet to be tested.

How are you getting into stock recovery?
 
Upvote 0
I don't get it.. I get the normal ZTE splash screen & a weird flash/reboot then goes into dfu mode (black screen, red light).
You could try using ftm mode to issue adb commands. Not sure how to get there...either vol up + power, or vol down + power, or both vol + power. Once there, connect to pc and use the command "adb reboot recovery".
 
  • Like
Reactions: bcrichster
Upvote 0

BEST TECH IN 2023

We've been tracking upcoming products and ranking the best tech since 2007. Thanks for trusting our opinion: we get rewarded through affiliate links that earn us a commission and we invite you to learn more about us.

Smartphones