Doing anything listed here will void your warranty. I don't know the laws where you are so assume it makes you a criminal. These things are posted here for educational purposes only. Never follow any guide if you don't understand the commands.
Enough BS, let's jump in.
For windows users. Installing drivers:
1. Plug USB cable into PC.
2. On the A3 prime, instead of using USB as charging, select use USB as Updating Firmware (i forget actual wording)
3. A prompt will come up on Windows, install those drivers.
4. Reboot.
Install adb and fastboot on your PC, it is up to you to do this.
Enable developer options on your phone, and enable USB debugging and OEM Unlocking.
In your CMD/Shell/Whatever you have.
adb reboot bootloader
fastboot flashing unlock (use volume up to confirm)
fastboot flashing unlock_critical (use volume up to confirm)
Congrats you've unlocked the bootloader.
Use 'fastboot reboot' to reboot if you haven't done so already.
-----
this is where the progress on this device comes to a halt.
The kernel source is available from opensource.ztedevices.com
The device codename is Z5157V, the Kernel they have is listed under Z5157V Q(10) Kernel(4.4.185)
What needs to happen next? Someone needs to compile the kernel from source.
Once that is done, they can extract the boot.img from it, use Magisk, and make a modified boot.img
Whoila, they will now have root. Once this person has root, they can extract recovery.img from the device, and we can begin making a custom TWRP, or who knows, maybe Team Win will pick it up (unlikely).
Once we have a custom recovery and working Magisk, it's just a matter of time before we start seeing custom ROMS.
If someone will sign up to be a guinea pig, or has an extra A3 Prime laying around I will continue development. I bricked mine because I was impulsive and honestly, kinda stupid. (browse through thread to see my idiocy)
Until such a time that I come to possess another A3 Prime OR someone steps up to provide a firmware dump, I am unable to help.
Good luck developing!
Only managed to unlock the bootloader but can't seem to find any information on rooting it.
The structure is indeed different than what you would normally expect to find. 'recovery' isn't a valid partition when trying to flash under fastboot for example.
The only reason I'm interested in trying to root this device is because The mtk engineering mode app doesn't work on this phone, at least not the visible version, so band locking doesn't seem possible without root and a different rom.
Yeah, I bricked my device by flashing a universal MTK TWRP.
Came here to say this, do not flash universal MTK.
It is a soft brick, bootloops with no access to stock or TWRP recovery.
The phone's model number is Z5157V and the stock firmware is Z5157VV1.0.0B17 for google indexing reasons. Only place that MAY have it is behind a $40 pay wall.
Managed to get the kernel from opensource.ztedevices.com, just beginning to work on it now (not sure how I'm gonna get my phone out of bootloop mode, but I'll solve it later)
I have never compiled a kernel from source, but I'm eager to learn, I have two days in the wilderness planned ahead of me. If anyone would compile the kernel, that is great. If not? I'll get it done when I get back.
Been playing around with the phone and key combinations, I think I have found a way to use SP Flash Tool in it's current soft brick state.
If I am successful in compiling the kernel, I will share it.
If I am able to unbrick this phone, I will write a guide.
If those two things happen, I'll be moving forward to make an AOSP based custom ROM for this phone. Maybe a first for a $100 device, but I like root.
If anyone else knows HOW to compile the kernel, you'd put me a few steps ahead when I get back.
Either way, nearly 200 lurkers on this thread, I hope to have answers soon.
ORANGE
zaduma said:
I was able to unlock the bootloader. Confirmed with a boot message on boot.
Click to expand...
Click to collapse
how does that bootmessage read?
does it say : "ORANGE STATE" et cetera ?
s4goa said:
how does that bootmessage read?
does it say : "ORANGE STATE" et cetera ?
Click to expand...
Click to collapse
Yeah
Orange State
Device can't be trusted
Booting in x seconds
1st.
zaduma said:
to make an AOSP based custom ROM for this phone. Maybe a first for a $100 device, but I like root.
Click to expand...
Click to collapse
why do you think you are first ? their are literally tons of €100 phones in circulation!
s4goa said:
why do you think you are first ? their are literally tons of €100 phones in circulation!
Click to expand...
Click to collapse
Who knows, guess I don't have much experience in this area. (Cheap phones) Figured it's usually not worth it to do all this work for a throwaway phone.
That said, I've been wrong before!
zaduma said:
Yeah
Orange State
Device can't be trusted
Booting in 5 seconds
Click to expand...
Click to collapse
same here after
Code:
fastboot flashing unlock_critical
(bootloader) Start unlock flow
FAILED ()
Finished. Total time: 21.830s
s4goa said:
same here after
Code:
fastboot flashing unlock_critical
(bootloader) Start unlock flow
FAILED ()
Finished. Total time: 21.830s
Click to expand...
Click to collapse
Strange it fails, try flashing unlock first, then flashing unlock_critical, make sure to press volume up on phone when prompted.
fastboot
dude, in order to avoid fuqqing confusion you ought not abbreviate a shell command like you do.
Anyhow, since we two guys have different phones, it makes sense only for me to generally discuss the rooting strategy on a ZTE Spreadtrum phone, as the specifics will differ too much.
I have fastboot on a Lumigon T3 as my "ZTE blade A5 2019" does not have fastboot.
---------- Post added at 16:07 ---------- Previous post was at 15:55 ----------
rooters, come join https://forum.xda-developers.com/group.php?groupid=1925
s4goa said:
dude, in order to avoid fuqqing confusion you ought not abbreviate a shell command like you do.
Anyhow, since we two fuys have different phones, it makes sense only for me to generally discuss the rooting strategy on a ZTE Spreadtrum phone, as the specifics will differ too much.
I have fastboot on a Lumigon T3 as my "ZTE blade A5 2019" does not have fastboot..
---------- Post added at 16:07 ---------- Previous post was at 15:55 ----------
rooters, come join https://forum.xda-developers.com/group.php?groupid=1925
Click to expand...
Click to collapse
Sorry, for clarity if on Linux type su and your root password, or use sudo to escalate your permissions if you don't have permission to use fastboot as a regular user.
If you're on windows, consider a free upgrade, but also leave out sudo and once in fastboot mode on a3 prime, type
1. (sudo) fastboot flashing unlock
2. (sudo) fastboot flashing unlock_critical
Press volume up when prompted and congrats your warranty is now void, bootloader unlocked. I'm not responsible for your choices.
__________
Also yeah, the phones even have different chipsets the Z5157V is a MTK phone
fastboot
this "orange state unlock bootloader" has - however - nothing or little to do with "Developer Menu option UNLOCK BOOTLOADER"
do you know more about this?
on my Lumigon these 2 unlockings are independent of each other, never mind the identical name "unlock bootloader".
s4goa said:
this "orange state unlock bootloader" has - however - nothing or little to do with "Developer Menu option UNLOCK BOOTLOADER"
do you know more about this?
on my Lumigon these 2 unlockings are independent of each other, never mind the identical name "unlock bootloader".
Click to expand...
Click to collapse
Yeah, you'll need to toggle that option to on in Developer Settings before entering the bootloader/fastboot mode and running the unlock commands or they will fail.
we're screwed !
dude, dammit! they cryptosign bootloaders now LINK
if that is true we're done for! how to hack those cryptochips?
its for Unisoc SC9863A Spreadtrum but also other CPUs.
zaduma said:
:crying:
Click to expand...
Click to collapse
s4goa said:
Click to expand...
Click to collapse
Well, I am terribly sorry to hear that, but at least the A3 prime is on mediatek chipsets which I don't believe has any such protection.
Spreadtrum SC9832E, 64bit
zaduma said:
the A3 prime is on mediatek chipsets
Click to expand...
Click to collapse
if you are sure that boot.img can be "modded" then the A3 is a superior phone, let me tell you.
---------- Post added at 22:54 ---------- Previous post was at 22:50 ----------
anyway... its kewl u posted at https://www.gizmochina.com/2020/07/01/zte-blade-a3v-key-specs-leak/
s4goa said:
if you are sure that boot.img can be "modded" then the A3 is a superior phone, let me tell you.
---------- Post added at 22:54 ---------- Previous post was at 22:50 ----------
anyway... its kewl u posted at https://www.gizmochina.com/2020/07/01/zte-blade-a3v-key-specs-leak/
Click to expand...
Click to collapse
Keep checking for updates, once I'm back in town that's exactly what I'll be working on.
Sorry to anyone following this thread, I will continue working on building the kernel, extracting boot, and getting this phone rooted. I will need a volunteer to test the root solution once it is built, and then if possible follow a few steps and extract recovery.img on your newly rooted device and send that to me.
I just don't have the time today even though I said I would be doing it. If there are any volunteers with an A3 prime let me know!
Related
Updated guide rewritten here: http://forum.xda-developers.com/showpost.php?p=68538891&postcount=1
WARNING: THIS IS FOR THE MOTO MAXX ONLY. I AM NOT RESPONSIBLE FOR ANY DAMAGE THAT MIGHT HAPPEN TO YOUR BELONGINGS.
@respider made a custom recovery for us. It's not even beta, it's alpha. What it means is that it's the first attempt to make a custom recovery. Bugs are expected.
To root, you can use the attached datroot, or SuperSU
Before anything, go to the Motorola website and unlock your bootloader.
1. Download the file attached. Download the recovery
2. Leave the maxxpatched.img in your PC and put datroot.zip in your phone.
3. Open a terminal with adb and fastboot. If you don't know what i'm talking about, Google it.
4. In terminal use:
Code:
adb reboot bootloader
Your phone will reboot and you'll see the fastboot screen.
5. Unzip the recovery and rename the file to recovery.img
Code:
fastboot boot recovery.img
6. Now you'll boot into the recovery. Press simultaneously Power and Vol UP to show the commands.
Some users say the best way is to hold the Vol UP and then press and release the Power.
7. Install > click on the datroot.zip/supersu.zip> let it install > clear cache and dalvik
8. Reboot system.
9. You've got root.
glad to see the recovery is being useful... I hope we manage to get a working TWRP or CWM soon
Do I need to unlock the bootloader first??
ellopr said:
Do I need to unlock the bootloader first??
Click to expand...
Click to collapse
If he says no, he just earned like over 5 grand.
Maxx only were his first words, yes you must unlock your bootloader first.
Did this couple of days back, worked perfectly!! Now waiting for custom recovery and roms
---------- Post added at 10:48 PM ---------- Previous post was at 10:45 PM ----------
Hey since some of us are rooted, any body with knowledge care to look into trying to boost the sound of this baby a little?
tested
NOT WORKING ON DROID TURBO
prking07 said:
Did this couple of days back, worked perfectly!! Now waiting for custom recovery and roms
---------- Post added at 10:48 PM ---------- Previous post was at 10:45 PM ----------
Hey since some of us are rooted, any body with knowledge care to look into trying to boost the sound of this baby a little?
Click to expand...
Click to collapse
Bummed i aint' got root. Anyway. 'mixer_paths.xml' search xda for the proper values to modify. Its super simple and should dramatically increase the volumes. I've used this method on a bunch of phones running stock 4.x.x. Will work on 5.0 also. Tested on my nexus 7 2nd gen.
I'm sure Danger2u was 'reporting' and not 'complaining'.. easy enough to understand. it's way impossible OP would have been trying this on a turbo either,...
There needs to be a Moto Maxx forum. Seeing this in the turbo forum from my turbo just makes me sad.
alexcreto said:
5.
Code:
fastboot boot maxxpatched.img
6. Now you'll boot into the recovery.
Click to expand...
Click to collapse
When I get to step 5 and try to boot into recovery, only a resting android with a red exclamation point is shown.
And a text that says "Ningún comando" which means "No command".
I can't do anything else, after a while the phone reboots itself into my homescreen.
What should I do? What could be wrong?
UPDATE: Ok, after a while I found the solution:
When it shows "no command", press and hold the VOL UP key for 10-15 seconds. While still holding the VOL UP key tap and release the POWER key. It will display additional menu options.
Click to expand...
Click to collapse
Thanks to sbdc003 in androidforumshttp://androidforums.com/
Thanks @alexcreto, great tutorial!
ImpheOtus said:
When I get to step 5 and try to boot into recovery, only a resting android with a red exclamation point is shown.
And a text that says "Ningún comando" which means "No command".
I can't do anything else, after a while the phone reboots itself into my homescreen.
What should I do? What could be wrong?
Click to expand...
Click to collapse
Oh, my bad...
I'm so used to that I forgot to mention.
Press simultaneously Power and Vol UP
alexcreto said:
Oh, my bad...
I'm so used to that I forgot to mention.
Press simultaneously Power and Vol UP
Click to expand...
Click to collapse
Thank you!
I'm comming from Galaxy SII and S4 and I had never had to do this so it's my first time with fastboot, ADB and custom recoveries.
ImpheOtus said:
Thank you!
I'm comming from Galaxy SII and S4 and I had never had to do this so it's my first time with fastboot, ADB and custom recoveries.
Click to expand...
Click to collapse
Don't worry man, glad you enjoyed.
i understand very well that the guide is for Moto Maxx and NOT for Droid turbo.
but like some cases a method works on other phone that are similar
so i tested and just say that is not working on Droid turbo
in this way other users will not try on their Turbo
and i don t make any flame or other
frankeegee said:
I guess there is a reason for your name, eh? ?
Sent from my XT1254 using Tapatalk
Click to expand...
Click to collapse
I try, but my xt 1225 is not recognized, no drives installed? I have de MDM 2.4.5, but in Windows 7 not Works. How to download latest version of drives to Motorola xt1225?
adb devices not list my xt1225. I try with minimal adb and fastboot and Android SDK.
How to fix this? I need unlock bootloader.
Thanks
Thanks
muccioli said:
I try, but my xt 1225 is not recognized, no drives installed? I have de MDM 2.4.5, but in Windows 7 not Works. How to download latest version of drives to Motorola xt1225?
adb devices not list my xt1225. I try with minimal adb and fastboot and Android SDK.
How to fix this? I need unlock bootloader.
Thanks
Thanks
Click to expand...
Click to collapse
In the control panel, access the device manager and find your phone among the connected devices.
(Im not running Win right now, so Im gonna try to tell you the steps by memory)
You have to right click and install updates to it.
Instead of letting it find them over the net, you'll choose the option to choose one from the list.
In that list find and pick the Moto Comp ADB
That should make it work.
If I switch to Win later today I'll update this post.
Hope it helps....
alexcreto said:
In the control panel, access the device manager and find your phone among the connected devices.
(Im not running Win right now, so Im gonna try to tell you the steps by memory)
You have to right click and install updates to it.
Instead of letting it find them over the net, you'll choose the option to choose one from the list.
In that list find and pick the Moto Comp ADB
That should make it work.
If I switch to Win later today I'll update this post.
Hope it helps....
Click to expand...
Click to collapse
Many thanks, but,
Do not have Moto Comp ADB in the options.
I try again use SDK, show message Daemon not start. Start daemon in port 5037. Daemon start. But nothing is happening. Don not show my device.
muccioli said:
Many thanks, but,
Do not have Moto Comp ADB in the options.
Click to expand...
Click to collapse
I remember that there was a parent called Motorola and a parent called Android ADB. Did you check both?
help
well im in the same position of the non recognized adb drivers i can't get my unlocked bootloader, and i wanna ask. after achieving root, can i install xposed framwork an then the gravity box, to make some changes??
Hey guys, I'm looking into getting an axon7mini. Before I do, I want to verify that I can get into EDL mode and talk to the device. Is anyone willing to take one of the axon7 tools and see if it will talk to the axon7mini in EDL mode? You don't need to write anything, just read. For example, do a backup of the recovery image using one of the tools.
If that works, I'll snag one off ebay and get Lineage up and running in short order.
If you can provide some instructions, I'm happy to test this for you. Running the latest lollipop rom atm. Can update to nougat if required.
Thanks
Just grab one of the axon7 EDL programs, such as:
https://forum.xda-developers.com/axon-7/development/wip-axon-7-root-bootloader-unlokced-t3441204
Or:
https://forum.xda-developers.com/axon-7/development/axon7tool-flash-backup-boot-recovery-t3514254
Follow the instructions there to backup your recovery or boot partition.
If it can communicate with the axon7mini, then odds are very high that we can get the boot loader unlocked and start building custom ROMs.
If it cannot communicate with the axon7mini, I'll need to pursue other channels for an unlock, which may not be successful.
dpgc213 said:
If you can provide some instructions, I'm happy to test this for you. Running the latest lollipop rom atm. Can update to nougat if required.
Thanks
Click to expand...
Click to collapse
tdm said:
Just grab one of the axon7 EDL programs, such as:
https://forum.xda-developers.com/axon-7/development/wip-axon-7-root-bootloader-unlokced-t3441204
Or:
https://forum.xda-developers.com/axon-7/development/axon7tool-flash-backup-boot-recovery-t3514254
Follow the instructions there to backup your recovery or boot partition.
If it can communicate with the axon7mini, then odds are very high that we can get the boot loader unlocked and start building custom ROMs.
If it cannot communicate with the axon7mini, I'll need to pursue other channels for an unlock, which may not be successful.
Click to expand...
Click to collapse
Cool, will give it a go tomorrow.
tdm said:
Just grab one of the axon7 EDL programs, such as:
https://forum.xda-developers.com/axon-7/development/wip-axon-7-root-bootloader-unlokced-t3441204
Or:
https://forum.xda-developers.com/axon-7/development/axon7tool-flash-backup-boot-recovery-t3514254
Follow the instructions there to backup your recovery or boot partition.
If it can communicate with the axon7mini, then odds are very high that we can get the boot loader unlocked and start building custom ROMs.
If it cannot communicate with the axon7mini, I'll need to pursue other channels for an unlock, which may not be successful.
Click to expand...
Click to collapse
Hi,
I can get it to communicate however when attempting "axon7tool -r gpt boot recovery" I'm getting an error which cause the tool to crash. it reads failed to read command.
Thanks
dpgc213 said:
Hi,
I can get it to communicate however when attempting "axon7tool -r gpt boot recovery" I'm getting an error which cause the tool to crash. it reads failed to read command.
Thanks
Click to expand...
Click to collapse
Thanks. That probably means it's incompatible. :/
tdm said:
Thanks. That probably means it's incompatible. :/
Click to expand...
Click to collapse
Yeah, this means incompatible, we need the programmer, firehose file 8952. But is only in a old firmware (NOT SD card upgrade). Anyone have this?
tdm said:
Just grab one of the axon7 EDL programs, such as:
https://forum.xda-developers.com/axon-7/development/wip-axon-7-root-bootloader-unlokced-t3441204
Or:
https://forum.xda-developers.com/axon-7/development/axon7tool-flash-backup-boot-recovery-t3514254
Follow the instructions there to backup your recovery or boot partition.
If it can communicate with the axon7mini, then odds are very high that we can get the boot loader unlocked and start building custom ROMs.
If it cannot communicate with the axon7mini, I'll need to pursue other channels for an unlock, which may not be successful.
Click to expand...
Click to collapse
tdm, you don't live far from me.
i'll try these out as well, but you have a local beta tester
Edit:
Same error even running in compatibility mode Windows 8
Code:
E:\Axon>axon7tool -r recovery
Connecting to device...
Sending programmer...
S: target error 0x00000014
terminate called after throwing an instance of 'std::runtime_error'
what(): error: No error
This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.
Code:
E:\Axon\axon7root>axon7root -d
Copyright @tenfar [email protected]
Version 1.10
Failed to say hello to device
device no response
!!!!!!!! Horse is dead!!!!!!!!!
rombdeta said:
Yeah, this means incompatible, we need the programmer, firehose file 8952. But is only in a old firmware (NOT SD card upgrade). Anyone have this?
Click to expand...
Click to collapse
I can probably find a 8952 firehose, but it will be from another manufacturer. So it won't be signed with the proper key. Which means it almost surely won't work.
Sent from my Find 5 using Tapatalk
Been trying to snag an axon7mini on ebay for about $120 but they keep going for $140-$150. @fallen00sniper if you want to trade me for another phone for a week, I can try my hand at unlock.
Well i have the programmer finally!
rombdeta said:
Well i have the programmer finally!
Click to expand...
Click to collapse
Which programmer? The official axon7mini one? Or for another device?
tdm said:
Which programmer? The official axon7mini one? Or for another device?
Click to expand...
Click to collapse
Axon 7 mini, 8952, but i will work with my device, i need info how to edit the bootloader bit
Currently, I added a file to remove patron / code, since some recovery does not bring the option of "wipe data", but I repeat is only a test, I do not take responsibility for damages, this is the door to unlock the boot and customs roms , recoverys and so on.
https://mega.nz/#!k1M2gKya!tjtjCD4Jp...xvYzx-wjeTrYvE
tdm said:
Been trying to snag an axon7mini on ebay for about $120 but they keep going for $140-$150. @fallen00sniper if you want to trade me for another phone for a week, I can try my hand at unlock.
Click to expand...
Click to collapse
We would have to speak about this further.
I'm on MetroPCS and they charge $15 Everytime I move the Sim to a different device, maybe on the website I can do it for free, not sure.
How do they do that? You should just be able to swap your sim over shouldn't you?
Hdale85 said:
How do they do that? You should just be able to swap your sim over shouldn't you?
Click to expand...
Click to collapse
I can swap the Sim over, but the IMEI change is where they get me, but it looks like I can do it free on the website, since I cannot go any further without a different IMEI I don't know if they charge and I am currently out of work :/
However if @tdm pm me we can talk about this trading for a week and try to get this ball rolling.
rombdeta said:
Axon 7 mini, 8952, but i will work with my device, i need info how to edit the bootloader bit
Click to expand...
Click to collapse
Nice! I'd love a copy of that. I can most likely make unlock tools with it.
Next question... does this device have a fbop partition?
tdm said:
Nice! I'd love a copy of that. I can most likely make unlock tools with it.
Next question... does this device have a fbop partition?
Click to expand...
Click to collapse
I think so, the link is in another post.
rombdeta said:
I think so, the link is in another post.
Click to expand...
Click to collapse
The link is bad, it says the provided key is invalid.
Since the majority of the hardware between the devices is gonna be almost exactly the same, I'mma give a shot at rooting it. Picking up tomorrow, so hopefully it goes well
I just got this phone. Let me know how what happens please.
tge101 said:
I just got this phone. Let me know how what happens please.
Click to expand...
Click to collapse
Yeah, I'll keep a heads up. I'm sitting in metro now tryna see what's going on, small argument. Their commercials in Philly don't mention that you need to switch carriers for the rebates.
I'll probably be getting one next week. Says it has 7.1.2 an it weighs less? Cool
attempt
Ok so I tried to root this and everything went well up ubtil I flashed Team win. When i try to open it, the program starts HOWEVER something is up with the touch screen. Im unable to click anything the only power button works. I tried flashing versions 3.0.0, 3.0.1, 3.0.2, 3.0.3. No luck! Is the problem they are old versions? Should i use 3.1.1 which was designed for Nougat supposedly?
Any advice this is my first attempt in to rooting android devices. Forgive me if any of my lingo is incorrect.
tribal1209 said:
Ok so I tried to root this and everything went well up ubtil I flashed Team win. When i try to open it, the program starts HOWEVER something is up with the touch screen. Im unable to click anything the only power button works. I tried flashing versions 3.0.0, 3.0.1, 3.0.2, 3.0.3. No luck! Is the problem they are old versions? Should i use 3.1.1 which was designed for Nougat supposedly?
Any advice this is my first attempt in to rooting android devices. Forgive me if any of my lingo is incorrect.
Click to expand...
Click to collapse
Are you trying to root the aristo or aristo 2?
Aristo 2. Sorry, kind of diving in head first with this whole process. If im doing something obviously wrong go easy on me lol.
---------- Post added at 11:26 PM ---------- Previous post was at 11:25 PM ----------
Aristo 2
Hmm and you flashed the twrp that was for the aristo right?
Well the TWRP files i used were on *How To* forums posts and youtube videos for the original LG Aristo. Everything was going fine but the touch screen while in TWRP does not work. Maybe there os a different version I can try? Do any of you guys have any ideas, my understanding though is that TWRP has to be created for a specific device once released. Is thats whats going wrong?
you unlocked the bootloader and flashed the aristo 1 recovery thats what you did so far right?
The aristo 1 recovery will not work at all.
The screens are of the same build, but different composition.
That's why I wanted to test this myself before posting further on the subject.
I can risk my phone, most of you cant.
I figured as much. Thanks for the info! Just got mine today. Glad the aristo's battery works in the aristo2 as i bought a couple batteries for it. I still do like the aristo though it feels a bit better in my hand.
Well luckily It seems i have not screwed up my phone. Have reset and wiped it multiple times which was annoying, but seems to be ok. It sucks because it looks like the touch screen alone is whats screwing me over. If only i had a way around it. Then again im sure you guys have a better idea of whats going on. Guess ill just be patient until more is posted on subject.
We need a new recovery for this anyway. Since the aristo 2 isn't gonna have multiple versions (besides the Korean base model the 2 is built after), we should be able to build just one recovery using the model number as it's target, we can make it borderline universal if a new version were to pop up.
I decided against going the metro route, buying mine in bulk. So I'll have one to smash when this is all over.
The TWRP method works the same as the Aristo, and the TWRP recovery IS compatible. However the touch screen does not function.. Is there a way to get it to work?
@ninjasinabag @teknoweanie @tribal1209 Hey guys, spent a few hours figuring out how to root. Pretty Simple
1) Enable Developer Options, USB Debugging & OEM Unlock
2) Reboot to Fastboot Mode (Using ADB via PC type: adb reboot bootloader)
3) Add root_boot.img into your adb folder
4) In ADB type: fastboot flash boot root_boot.img
5) After flash successful, type: fastboot reboot
6) Install Magisk Manager App
brad2192 said:
@[email protected]@tribal1209 Hey guys, spent a few hours figuring out how to root. Pretty Simple
1) Enable Developer Options, USB Debugging & OEM Unlock
2) Reboot to Fastboot Mode (Using ADB via PC type: adb reboot bootloader)
3) Add root_boot.img into your adb folder
4) In ADB type: fastboot flash boot root_boot.img
5) After flash successful, type: fastboot reboot
6) Install Magisk Manager App
Click to expand...
Click to collapse
Not to sound sceptical but is this the real deal?
spirithandler said:
Not to sound sceptical but is this the real deal?
Click to expand...
Click to collapse
Please someone let me know! I want this phone rooted (Its an awesome phone) but want some verification before I start flashing and downloading random files.
spirithandler said:
Not to sound sceptical but is this the real deal?
Click to expand...
Click to collapse
Yes, it is. What I did was use LG firmware extractor and extracted the boot image, then I proceeded to patch the boot image with magisk manager. Enabling OEM unlock allows me to flash the boot image with the newly-created custom one. Remember though, you should create a backup of your device because enabling OEM unlock will completely erase everything.
brad2192 said:
@ninjasinabag @teknoweanie @tribal1209 Hey guys, spent a few hours figuring out how to root. Pretty Simple
1) Enable Developer Options, USB Debugging & OEM Unlock
2) Reboot to Fastboot Mode (Using ADB via PC type: adb reboot bootloader)
3) Add root_boot.img into your adb folder
4) In ADB type: fastboot flash boot root_boot.img
5) After flash successful, type: fastboot reboot
6) Install Magisk Manager App
Click to expand...
Click to collapse
Supposedly the img you posted is simply a modified version of Magisk you posted. Someone please explain to me (Who is new to this whole process) why this supposed explanation does not involve any recovery program or requiring of wiping/clearing any cache or what have you?
Hi All,
In the best interest to provide clarity I'm creating this quick and easy tutorial on how to root your Razer Phone 2 after the Pie Upgrade. Please send me any feedback to improve this post, we need to build up a strong community.
*As usual, I'm not responsible of any damage or brick to your phone, do it at your own risk.
Pre-Requirements:
-Be sure to have at least 70% of charges... or plug your phone to power
-Backup anything you consider important
-Already installed Pie Upgrade via OTA or Side Loaded
-Enable Developer Options
• Open Phone "Settings" and scroll down.
• You will see an option "Build Number".
• Simply tap on it 7 times to enable it on your Android Oreo based device.
• Your device immediately display a message on screen that will say "You are now a developer".
• The Developer Option is now available in the Settings>System>Developer Options. Enjoy!
- Install Android Drivers (https://developer.android.com/studio/run/win-usb) and ADB, I personally recommend -[TOOL]Minimal ADB and Fastboot [2-9-18] - https://forum.xda-developers.com/showthread.php?t=2317790
-Unlock Bootloader
• To enable OEM unlock, go to Settings > Developer options and check Enable OEM unlock
• Using ADB commands reboot on bootloader
adb reboot bootloader
• After reboot completes follow phone menus and select "UNLOCK BOOTLOADER"; accept all warnings, after restart you have completed the unlock.
Root and Installing Magisk
Since our phone doesn't have a proven customer recovery fully working (Ex TWRP) Magisk needs to be installed by manually patching the device boot image.
Making leverage of Warrior1988 post [Root Magisk Pie Update For Unlocked Devices] all credits to him. Download the image from his post
• Boot in fastboot mode To boot into fastboot, press and hold the Power button + Volume Down Keys for few seconds; Copy the image on the same folder as your ADB and Run the following commands:
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot reboot
Install Magisk Download the apk and install it as usual on your RP2, that should be all.
DONE!!!! You now have a unleashed the beast! Please send me any recommendations to improved this guide.
chpimentelpr said:
Install Android Drivers and ADB
Click to expand...
Click to collapse
Your link has everything necessary for this step, right? Direct link to version 1.4.3 is here: https://androidfilehost.com/?fid=746010030569952951
Or are drivers and ADB two separate downloads?
chpimentelpr said:
• To enable OEM unlock, go to Settings > Developer options and check Enable OEM unlock
Click to expand...
Click to collapse
I assume this is where we plug our phone into our computer?
chpimentelpr said:
• Using ADB commands reboot on bootloader
Click to expand...
Click to collapse
For anyone dumb and new like me, I think this is with cmd.exe in Windows. Win+S -> type "cmd" (without quotation marks) and hit enter. Once open, you want to navigate to ADB, which you've already installed via the above instructions.
So your cmd will say:
C:\Users\YourName>
And you want to get to ADB, so you'll type "cd" (without quotation marks) which means you want to change directories, and then "cd adb" (if its in C:\ directory) or "cd [whatever the path is to the ADB folder]\adb"
Assuming it was directly in C:, you should see something like:
C:\adb>
Now you want to type "adb devices" to make sure it sees your phone is plugged in. You should see: "list of devices attached - [model] device" or something.
Now you're ready to go with the instructions starting at "adb reboot bootloader." If I'm wrong about this, someone less new and dumb than I am please correct me.
chpimentelpr said:
• Copy the image on the same folder as your ADB and Run the following commands:
fastboot flash*boot_a boot.img
fastboot flash boot_b boot.img
fastboot reboot
Click to expand...
Click to collapse
I'm confused on this one. The first one has "flash*boot_a," but the second one has "flash boot_b" without the * symbol. What does the * do, and what happens if we mess it up? Sorry if that's a dumb question.
AbsoluteContingency said:
Your link has everything necessary for this step, right? Direct link to version 1.4.3 is here: https://androidfilehost.com/?fid=746010030569952951
Or are drivers and ADB two separate downloads?
I assume this is where we plug our phone into our computer?
For anyone dumb and new like me, I think this is with cmd.exe in Windows. Win+S -> type "cmd" (without quotation marks) and hit enter. Once open, you want to navigate to ADB, which you've already installed via the above instructions.
So your cmd will say:
C:\Users\YourName>
And you want to get to ADB, so you'll type "cd" (without quotation marks) which means you want to change directories, and then "cd adb" (if its in C:\ directory) or "cd [whatever the path is to the ADB folder]\adb"
Assuming it was directly in C:, you should see something like:
C:\adb>
Now you want to type "adb devices" to make sure it sees your phone is plugged in. You should see: "list of devices attached - [model] device" or something.
Now you're ready to go with the instructions starting at "adb reboot bootloader." If I'm wrong about this, someone less new and dumb than I am please correct me.
I'm confused on this one. The first one has "flash*boot_a," but the second one has "flash boot_b" without the * symbol. What does the * do, and what happens if we mess it up? Sorry if that's a dumb question.
Click to expand...
Click to collapse
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot reboot
Warrior1988 said:
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot reboot
Click to expand...
Click to collapse
No asterisk. Cool. Got it. Thank you, dude.
The drivers are the regular ones for android nothing specific, they can be downloaded from their SDK https://developer.android.com/studio/run/win-usb
App root detection?
If I root my Razer phone 2 using this guide, will certain apps like banking apps, and rideshare apps be able to detect root?
Bounty33 said:
If I root my Razer phone 2 using this guide, will certain apps like banking apps, and rideshare apps be able to detect root?
Click to expand...
Click to collapse
You can use magisk to hide the root from those apps. In general banking app are not affected by root. Google pay could be affected, but I don't use it so can't be sure. And you can always unroot.
AbsoluteContingency said:
No asterisk. Cool. Got it. Thank you, dude.
Click to expand...
Click to collapse
Did you rooted? Anything missing on the guide? I want make it as useful as possible so feedback is welcome.
chpimentelpr said:
Did you rooted? Anything missing on the guide? I want make it as useful as possible so feedback is welcome.
Click to expand...
Click to collapse
I have not, but I've been really sick and useless. I think I'll try tonight and let you know how it goes. Thanks for the guide, dude.
---------- Post added at 02:50 PM ---------- Previous post was at 02:45 PM ----------
Wait, yes, I do have a question. I download the drivers, and I download the Fastboot ADB thing. What do I do with the drivers? Do they just install in Windows like anything else, and that allows me to connect to the phone?
AbsoluteContingency said:
I have not, but I've been really sick and useless. I think I'll try tonight and let you know how it goes. Thanks for the guide, dude.
---------- Post added at 02:50 PM ---------- Previous post was at 02:45 PM ----------
Wait, yes, I do have a question. I download the drivers, and I download the Fastboot ADB thing. What do I do with the drivers? Do they just install in Windows like anything else, and that allows me to connect to the phone?
Click to expand...
Click to collapse
Yes, install them as any other driver.
After rooting can you relock the boot loader or will that brick the phone?
ndragon798 said:
After rooting can you relock the boot loader or will that brick the phone?
Click to expand...
Click to collapse
Not sure, but why you want to relock the boot.
chpimentelpr said:
Not sure, but why you want to relock the boot.
Click to expand...
Click to collapse
Mostly to get rid of the startup message
Very nice. I've rooted a ton of phones over the years, but they had more established communities and had well-explained (and tested) methods of rooting. The previous guide posted (that you referenced) was fine enough, but it was very much lacking a couple prerequisites that I was wondering/concerned about. This guide has cleared all of that up for me, and I now feel confident about rooting this phone.
Just as soon as I charge up the phone and install the OTA I've been avoiding until now... lol. Hoping somebody will make a Magisk module to move the clock back to where it belongs (if they haven't already).
EDIT: Just wanted to add my success story to this. Only thing I had to do that wasn't listed in the instructions (but makes sense) is that fastboot didn't work until I enabled USB Debugging (again, after the wipe and reboot), and I had to very manually tell the computer which driver to use (ADB) after that. Didn't have that issue for the bootloader instructions beforehand (that time, the driver worked automatically), so I figured I'd mention it.
chpimentelpr said:
Not sure, but why you want to relock the boot.
Click to expand...
Click to collapse
Also is there a way to turn back on the preboot authentication. Pretty much I just want to maintain full encryption and the built in security while having root.
ndragon798 said:
Also is there a way to turn back on the preboot authentication. Pretty much I just want to maintain full encryption and the built in security while having root.
Click to expand...
Click to collapse
I don't believe encryption is supported at the moment, and I don't encourage you to try it until TWRP is fully supported since you may end up in a boot loop. I'm eagerly waiting for the full encryption capability, so I will let you know as soon as something come up.
This has to be......one of the most usefull and noob friendly guides i have ever seen.....
You sir....are a God
Thank You.
ChronosTrigger said:
This has to be......one of the most usefull and noob friendly guides i have ever seen.....
You sir....are a God
Thank You.
Click to expand...
Click to collapse
i'm glad it helps.
Alright so after fighting with windows for a few hours, I discovered that my ADB was severely outdated.... Lesson learned there.
After getting the new boot image installed, though, I hit another problem... WiFi refuses to work. The toggle switch in the statusbar, nor the toggle in the system settings, will bring my wifi to life. Which is weird! Because I got through setup just fine, connected to wifi and signed into google... Yet now all wifi functionality has vanished. I tried a factory reset, to no avail. I'm gonna have to restore the factory boot image and start all over... But for now, figured I'd ask if anyone else has run into this weird bug?
***update***
I've now gone and flashed the global image for 8.1.0 to the phone... and it's telling me the OS is up to date???? How do I get back to pie?? It's late here and I've got wifi back now... but I'm stumped. Any help would be so greatly appreciated!
xttweaponttx said:
Alright so after fighting with windows for a few hours, I discovered that my ADB was severely outdated.... Lesson learned there.
After getting the new boot image installed, though, I hit another problem... WiFi refuses to work. The toggle switch in the statusbar, nor the toggle in the system settings, will bring my wifi to life. Which is weird! Because I got through setup just fine, connected to wifi and signed into google... Yet now all wifi functionality has vanished. I tried a factory reset, to no avail. I'm gonna have to restore the factory boot image and start all over... But for now, figured I'd ask if anyone else has run into this weird bug?
***update***
I've now gone and flashed the global image for 8.1.0 to the phone... and it's telling me the OS is up to date???? How do I get back to pie?? It's late here and I've got wifi back now... but I'm stumped. Any help would be so greatly appreciated!
Click to expand...
Click to collapse
I doubt the issue with the wifi is related with the image, since it doesn't have anything to do with it. If your phone doesn't detect the update you will need to sideload it. Then try the root guide again. Let us know how it goes, it the first time I hear something wrong with WIFI after rooting.
Asus' unlock tool for M1 is dead (network error, guess they just cut the line for older models). Attached one I had in my backup from who knows how long ago, since I couldn't find any working links anymore.
Trying unlock tool for newer devices throws "Device model is not supported".
Dev. menu option for OEM Unlock is not available in neither of "official" images.
Max Pro's unlock doesn't work for this device.
So am I really stuck with Android 10 Beta release? I guess it is kind of "win" considering this release isn't completely bloated by Asus, but it would still be nice to get TWRP and Lineage on it. Not to mention I really wanted to give the Postmarket try on this device.
I'm more than willing to be lab rat if anyone wants to try.. stuff.. on my device, at this point I wouldn't even mind if it got bricked in progress.
Alright I have not given up on this, yet. I've stumbled upon post from one of the Asus' moderators on their forums:
For ZB555KL, there will no longer be any system updates and maintenance (including server).
Sorry for any inconvenience it may cause.
Click to expand...
Click to collapse
What this means is there is no official way to unlock this phone anymore, as their unlock app has nothing to communicate with.
In the same thread, another user posted this:
I dont know if you are still looking for this but after working on it for hours what you are looking for is:
in fastboot mode type:
fastboot oem enable-unlock-once
will unlock the bootloader for you until the phone is reset. Just have to do it everytime you reboot back into fastboot.
Also if you're flashing recovery, these other 2 commands may prove useful:
fastboot oem reboot-recovery
fastboot oem reboot-recovery-wipe
Cheers!
Click to expand...
Click to collapse
Indeed using this, I was able to flash recovery. Multiple actually: TWRP, stock from step 3 of the post, OrangeFox, stock again.
Why? Well, booting into any recovery leaves me hanging on black screen.
I've tried TWRP, OrangeFox. Nothing. I have found stock recovery image as well, which I have flashed. Got black screen again. BUT. Thanks to the stock recovery image I've figured out it was actually working, since after pressing some buttons randomly (kind of stupid, I know, but I though its bricked at that point anyway) I've managed to wipe data and was presented with fresh startup. I'm thinking both TWRP and OrangeFox worked as well, its the screen that doesn't want to show things for some reason while in recovery.
So if any of you got any ideas why would any recovery present me with blank screen and how should I deal with it, I'm all ears. Or eyes..