steve19150
Newbie
When i Reboot My Zte Zmax the TWRP Come Up N Starts Flashing & It Never Enter TWRP
-
After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.
Root ZMAX Stuck On TWRP Logo
- Thread starter steve19150
- Start date
-
- Tags
- zte zmax
shlickwilly
Newbie
1. What were you doing when you got in this situation.
2. What happens when you boot the phone with the power button and the volume button.
3. What version of phone do you have which rom are you using.
2. What happens when you boot the phone with the power button and the volume button.
3. What version of phone do you have which rom are you using.
steve19150
Newbie
1. I Was On Cm12.1 Nd It Was Actin Up So I Resetted My Zmax
2.TWRP Comes Up & Starts Blinking And Never Go Into TWRP
3.T-mobile . CM 12.1 BETA 1
shlickwilly
Newbie
When you say you reset your phone did you use the wipes menu twrp?
steve19150
Newbie
I Reset my Zmax From Setting Not From TWRP Wipe menu
shlickwilly
Newbie
Well ...... you cannot use the reset within settings there are several Posts that state you are only aloud to use the wipe option In twrp. Are you certain that using the power and vol. You get just the twrp boot screen? @xtremeassure has a (zmax brick thread) post there he may be able to help you.
steve19150
Newbie
yes im sure
oh boy... here we go
Masterchief87
Android Expert
You MIGHT be able to fix it with adb since twrp provides root access adb shell.
PHP87
Android Enthusiast
If I had the knowledge, I would write a clear, concise guide on how to root your ZMax but I don't.
One of the first rules of bug writing is to write the bug in a way so that someone that has never seen the app can easily regress the bug based on the way the bug is written. This way new Devs and QA Testers on the project know what's going on.
With all of the work the Devs put in to Rooting the Z, I'm surprised no one has bothered to write a clear, concise newbie guide, which is one reason why devices are getting bricked.
Example on the "simple" way to root from another thread: (The "How?" has been added by me)
Method 1 backup restore
1. Get su binary on sdcard (How?)
2. Make a backup of your system and boot (How?)
3. Run Restore from twrp(this restores your backup you just made) (How?)
4. Don't reboot yet
5. Mount system in twrp (How?)
6. Copy su binary from sdcard to /system/xbin/su (How?)
7. chmod 755 with twrp file browser (How?)
8. Copy install-recovery.sh to /system/etc/install-recovery.sh (How?)
9. Chmod 755 install-recovery. sh (How?)
10. Copy daemonsu /system/xbin/daemonsu (How?)
11. Chmod daemonsu 755 (How?)
12. Cleanup delete old ku.sud from /system/xbin (How?)
Delete /system/use/iku (How?)
Delete kingroot.txt in system folder
Reboot
Enjoy SuperSU
Tell me, what noob is going to understand how to perform most of these steps?
Not asking to be spoon fed, but when it comes to something as Rooting, which can Brick your device, someone with the knowledge can't take 5 minutes to write a clear, concise, step-by-step guide?
When I was into playing with Satellite Encryption, I would write clear, concise steps that someone that has never hacked encryption could easily do first time around and it was more detailed than rooting a phone.
Now, when it came to troubleshooting, I would point them in the right direction and see if they could figure it out as knowing your setup was the key to troubleshooting it, and everyone had a different setup be it sat box, switches, LNB's, etc....
But a phone is all the same. There are little to no variables.
Instead of answering numerous "how to" questions and posting "You're bricked, sorry" responses and having someone be without their only phone, wouldn't it make sense for someone with the knowledge to write a clear and concise Root how-to?
Hell, I used to even include screen shots when I was writing hacking sat encryption instructions for newbs.
For now, I will wait until the bugs are worked out and either an .apk is available or a concise how-to is written as I do not wish to brick my device as most of the instructions are outside of my scope of knowledge and by the number of people that have bricked their devices, it's outside their scope as well.
Also, with all of the control the user has over the Android OS compared to the iOS, I could see how Jailbreaking would be needed, but Rooting an Android doesn't have nearly as many benefits as JB'ing an iPhone IMO
Either way, I'll sit this one out until a more stable Root is available that doesn't require numerous tries to root.
One of the first rules of bug writing is to write the bug in a way so that someone that has never seen the app can easily regress the bug based on the way the bug is written. This way new Devs and QA Testers on the project know what's going on.
With all of the work the Devs put in to Rooting the Z, I'm surprised no one has bothered to write a clear, concise newbie guide, which is one reason why devices are getting bricked.
Example on the "simple" way to root from another thread: (The "How?" has been added by me)
Method 1 backup restore
1. Get su binary on sdcard (How?)
2. Make a backup of your system and boot (How?)
3. Run Restore from twrp(this restores your backup you just made) (How?)
4. Don't reboot yet
5. Mount system in twrp (How?)
6. Copy su binary from sdcard to /system/xbin/su (How?)
7. chmod 755 with twrp file browser (How?)
8. Copy install-recovery.sh to /system/etc/install-recovery.sh (How?)
9. Chmod 755 install-recovery. sh (How?)
10. Copy daemonsu /system/xbin/daemonsu (How?)
11. Chmod daemonsu 755 (How?)
12. Cleanup delete old ku.sud from /system/xbin (How?)
Delete /system/use/iku (How?)
Delete kingroot.txt in system folder
Reboot
Enjoy SuperSU
Tell me, what noob is going to understand how to perform most of these steps?
Not asking to be spoon fed, but when it comes to something as Rooting, which can Brick your device, someone with the knowledge can't take 5 minutes to write a clear, concise, step-by-step guide?
When I was into playing with Satellite Encryption, I would write clear, concise steps that someone that has never hacked encryption could easily do first time around and it was more detailed than rooting a phone.
Now, when it came to troubleshooting, I would point them in the right direction and see if they could figure it out as knowing your setup was the key to troubleshooting it, and everyone had a different setup be it sat box, switches, LNB's, etc....
But a phone is all the same. There are little to no variables.
Instead of answering numerous "how to" questions and posting "You're bricked, sorry" responses and having someone be without their only phone, wouldn't it make sense for someone with the knowledge to write a clear and concise Root how-to?
Hell, I used to even include screen shots when I was writing hacking sat encryption instructions for newbs.
For now, I will wait until the bugs are worked out and either an .apk is available or a concise how-to is written as I do not wish to brick my device as most of the instructions are outside of my scope of knowledge and by the number of people that have bricked their devices, it's outside their scope as well.
Also, with all of the control the user has over the Android OS compared to the iOS, I could see how Jailbreaking would be needed, but Rooting an Android doesn't have nearly as many benefits as JB'ing an iPhone IMO
Either way, I'll sit this one out until a more stable Root is available that doesn't require numerous tries to root.
steve19150
Newbie
Masterchief87
Android Expert
Since it has been a while since you first posted your question, I need to know a few things.
[1] When you hold power+volume up to enter twrp recovery, what exactly happens? I need you to be specific.
[2] Do you have a PC with adb installed?
[3] If you have a PC with adb, connect your phone while it is attempting to boot into twrp.
Then open a command prompt or terminal and type
[1] When you hold power+volume up to enter twrp recovery, what exactly happens? I need you to be specific.
[2] Do you have a PC with adb installed?
[3] If you have a PC with adb, connect your phone while it is attempting to boot into twrp.
Then open a command prompt or terminal and type
Can adb recognize the phone?
steve19150
Newbie
1 twrp keeps flashing now the screen turns black after bootup
nd my zmax is connected to my pc with adb
Masterchief87
Android Expert
Can adb recognize the phone?
steve19150
Newbie
Masterchief87
Android Expert
Okay, type
If you see a $ then type
$ indicates that adb is running without root permissions.
# means that adb has root access.
Do you see a $ or a #
If you see a $ then type
Do you have a # now?
$ indicates that adb is running without root permissions.
# means that adb has root access.
steve19150
Newbie
Masterchief87
Android Expert
Sweet, that means that there is hope. You can try this.
Attempt to boot into twrp by pressing power+vol up.
Connect your phone to PC via USB.
Open a command prompt or terminal and type the following commands
Attempt to boot into twrp by pressing power+vol up.
Connect your phone to PC via USB.
Open a command prompt or terminal and type the following commands
Just so you know this will wipe your entire data partition including internal storage so if you have files on the internal storage that you want to recover then don't use the "rm -r /data" command. If you want you can first try just "rm -r /cache" and see if your phone will boot normally after that.