Related
This guide worked for me. I am using v20i stock rom without any modification. I saw this on web and i want to share it. If you use this guide, it is on your own risk (such as mine)
We will have a rooted lolipop rom without downgrading to any kitkat rom. We dont need to flash bumped twrp for this.
This guide describes for windows users but same method can work with linux. Linux users know how
1- Download this file.
2- Copy zip file to your C:\ hard drive and extract there. It should be like this: C:\g3-root
3- Enter your phone's settings and activate the developer settings (with clicking build number 5-6 times)
4- Enter developer settings and activate usb debbuging
5- Enter the file g3-root and press and hold the shift button on your keyboard and right click with mouse. Select "open command window" or something like this (i am not using english windows)...
6- Connect the phone to your pc with usb cable.
7- Dont let the screen off. If your phone asks you about usb debbuging (trusting the computer), select "remember this" and click "yes"
8- now test the connection... write this into the command window
Code:
adb devices
if you can see your device's serial number, you can start now. If not, check the adb and windows drivers and try it again.
9- push the files which are needed for root with this commands
Code:
adb push g2_root.sh /data/local/tmp/
and
Code:
adb push busybox /data/local/tmp/
and
Code:
adb push UPDATE-SuperSU-v2.46.zip /data/local/tmp/
10- Now we will enter download mode of our phone. For this, discoonnect the usb cable, shut down the phone, press and hold the volume up button and connect the phone.
You will see "downloading" on your screen.
11- Now return the command window. Look your computer and verify which port of windows that the phone is connected . Mine is COM6 and i will go on with this way. You must change this with yours(COM1 COM2 COM3 COM4.... etc) . Enter this command (for COM6)
Code:
Send_Command.exe \\.\COM6
12- Next send this command:
Code:
ls
if you see the folders, everything is fine and you can continue.
13- finally we send last command and gonna be rooted
Code:
sh /data/local/tmp/g2_root.sh dummy 1 /data/local/tmp/UPDATE-SuperSU-v2.46.zip /data/local/tmp/busybox
You can see these lines if rooting is successfull
ui_print - Disabling OTA survival
ui_print - Removing old files
ui_print - Placing files
ui_print - Post-installation script
ui_print - Unmounting /system and /data
ui_print - Done !
Click to expand...
Click to collapse
if not, read and try again.
Now reboot your phone and you can see the supersu app in your application drawer
Good Luck!
I am not responsible of any damage to your phone.
I saw this guide in: http://forum.donanimhaber.com/m_103553600/tm.htm
But the main guide is : blog.lvu.kr/g2-lollipop-%EC%88%9C%EC%A0%95-%EB%A3%A8%ED%8C%85/
credits: these guides
Root is working but the problem is TWRP because is not working its giving error so no flashing other custom rom or mods for now.
Yes root is working fine. I didnt tried twrp or cwm. With this guide, you can use stock odexed and unmodified lolipop rom.
hi guys
New Root Method for LG Devices lollipop
http://forum.xda-developers.com/android/development/guide-root-method-lg-devices-t3049772
jojobans said:
hi guys
New Root Method for LG Devices lollipop
http://forum.xda-developers.com/android/development/guide-root-method-lg-devices-t3049772
Click to expand...
Click to collapse
Same method
LG-D855 cihazımdan Tapatalk kullanılarak gönderildi
agritux said:
Same method
LG-D855 cihazımdan Tapatalk kullanılarak gönderildi
Click to expand...
Click to collapse
evet arkadash
Muhahahah
LG-D855 cihazımdan Tapatalk kullanılarak gönderildi
agritux said:
This guide worked for me. I am using v20i stock rom without any modification. I saw this on web and i want to share it. If you use this guide, it is on your own risk (such as mine)
We will have a rooted lolipop rom without downgrading to any kitkat rom. We dont need to flash bumped twrp for this.
This guide describes for windows users but same method can work with linux. Linux users know how
1- Download this file.
2- Copy zip file to your C:\ hard drive and extract there. It should be like this: C:\g3-root
3- Enter your phone's settings and activate the developer settings (with clicking build number 5-6 times)
4- Enter developer settings and activate usb debbuging
5- Enter the file g3-root and press and hold the shift button on your keyboard and right click with mouse. Select "open command window" or something like this (i am not using english windows)...
6- Connect the phone to your pc with usb cable.
7- Dont let the screen off. If your phone asks you about usb debbuging (trusting the computer), select "remember this" and click "yes"
8- now test the connection... write this into the command window
Code:
adb devices
if you can see your device's serial number, you can start now. If not, check the adb and windows drivers and try it again.
9- push the files which are needed for root with this commands
Code:
adb push g2_root.sh /data/local/tmp/
and
Code:
adb push busybox /data/local/tmp/
and
Code:
adb push UPDATE-SuperSU-v2.46.zip /data/local/tmp/
10- Now we will enter download mode of our phone. For this, discoonnect the usb cable, shut down the phone, press and hold the volume up button and connect the phone.
You will see "downloading" on your screen.
11- Now return the command window. Look your computer and verify which port of windows that the phone is connected . Mine is COM6 and i will go on with this way. You must change this with yours(COM1 COM2 COM3 COM4.... etc) . Enter this command (for COM6)
Code:
Send_Command.exe \\.\COM6
12- Next send this command:
Code:
ls
if you see the folders, everything is fine and you can continue.
13- finally we send last command and gonna be rooted
Code:
sh /data/local/tmp/g2_root.sh dummy 1 /data/local/tmp/UPDATE-SuperSU-v2.46.zip /data/local/tmp/busybox
You can see these lines if rooting is successfull
if not, read and try again.
Now reboot your phone and you can see the supersu app in your application drawer
Good Luck!
I am not responsible of any damage to your phone.
I saw this guide in: http://forum.donanimhaber.com/m_103553600/tm.htm
But the main guide is : blog.lvu.kr/g2-lollipop-%EC%88%9C%EC%A0%95-%EB%A3%A8%ED%8C%85/
credits: these guides
Click to expand...
Click to collapse
Finally YES!!! thank you so mu ch. Will try later.
Root plus Custom Recovery, or Root Only?
Hi,
This is interesting and looks a lot easier than the guide I just put up over the weekend: http://forum.xda-developers.com/lg-g3/general/guide-update-to-lollipop-root-bumpd-twrp-t3048845.
But I wanted to confirm first, this is purely for rooting only, correct? In other words, if I follow only the steps in this guide I will have root...but I will not be able to install a custom recovery (like TWRP) (same as this thread: http://forum.xda-developers.com/android/development/guide-root-method-lg-devices-t3049772)?
EDIT: nevermind, one user of the other thread confirmed my question already: http://forum.xda-developers.com/showpost.php?p=59325441&postcount=55. So indeed, this method is for root only, because this method starts with a fully-flashed Lollipop firmware (inclusive of Lollipop version boot stack - aboot.img, sbl1.img, rpm.img, tz.img, etc.).
topet2k12001 said:
Hi,
This is interesting and looks a lot easier than the guide I just put up over the weekend: http://forum.xda-developers.com/lg-g3/general/guide-update-to-lollipop-root-bumpd-twrp-t3048845.
But I wanted to confirm first, this is purely for rooting only, correct? In other words, if I follow only the steps in this guide I will have root...but I will not be able to install a custom recovery (like TWRP) (same as this thread: http://forum.xda-developers.com/android/development/guide-root-method-lg-devices-t3049772)?
EDIT: nevermind, the OP of the other thread confirmed my question already: http://forum.xda-developers.com/showpost.php?p=59325441&postcount=55. So indeed, this method is for root only, because this method starts with a fully-flashed Lollipop firmware (inclusive of Lollipop version boot stack - aboot.img, sbl1.img, rpm.img, tz.img, etc.).
Click to expand...
Click to collapse
This is a way for rooting from lollipop, and access to fastboot too.
For custom recovery, it needd bump ! , and bump works only with KK bootloader. So for having a custom recovery, we need to downgrade BL first, and inject Bumped recovery + bumped kernel after.
And if we downgrade BL, maybe we need downgrade complete bootstack too (sbl,rpm,tz,dbi,laf) ?
Just to make sure, this works for v20i only or does it work for, say, my v20h too?
6ril1 said:
This is a way for rooting from lollipop, and access to fastboot too.
For custom recovery, it needd bump ! , and bump works only with KK bootloader. So for having a custom recovery, we need to downgrade BL first, and inject Bumped recovery + bumped kernel after.
And if we downgrade BL, maybe we need downgrade complete bootstack too (sbl,rpm,tz,dbi,laf) ?
Click to expand...
Click to collapse
Yup yup, I got it. Thanks. Just wanted to confirm.
Yes, I'm aware also of fastboot ability. Basically, dd if=/dev/zero means "writing zeroes" to whatever partition (in the case of the guide, it's the "laf" partition where "Download Mode" is stored). So, zeroing out the "laf" partition will make the device fall back to standard fastboot - except for the Verizon variant. I think you can do that regardless if you are in Kitkat or Lollipop, since the process is mere deletion of a partition's contents to "force" the device to fall back to fastboot.
Yes, you need to downgrade the entire boot stack. Basically, all partitions will need to stay at "Kitkat" version, and then manually flash ONLY system.img, boot.img, and modem.img (just like the one in my guide). And then, "bump" the boot.img so that you can install a custom recovery. I wrote that in my how-to guide as well.
In my case, I feel uncomfortable not having a custom recovery. I tinker around with my device a lot and have "bricked" it a lot of times but was saved because I have a backup via custom recovery.
I would suggest making it clear that this is for root only (meaning, does not include custom recovery). Very important, because I have seen threads from other users where they got bricked and can no longer restore at all - too bad because they did not have a custom recovery backup.
topet2k12001 said:
Yup yup, I got it. Thanks. Just wanted to confirm.
Yes, I'm aware also of fastboot ability. Basically, dd if=/dev/zero means "writing zeroes" to whatever partition (in the case of the guide, it's the "laf" partition where "Download Mode" is stored). So, zeroing out the "laf" partition will make the device fall back to standard fastboot - except for the Verizon variant. I think you can do that regardless if you are in Kitkat or Lollipop, since the process is mere deletion of a partition's contents to "force" the device to fall back to fastboot.
Yes, you need to downgrade the entire boot stack. Basically, all partitions will need to stay at "Kitkat" version, and then manually flash ONLY system.img, boot.img, and modem.img (just like the one in my guide). And then, "bump" the boot.img so that you can install a custom recovery. I wrote that in my how-to guide as well.
In my case, I feel uncomfortable not having a custom recovery. I tinker around with my device a lot and have "bricked" it a lot of times but was saved because I have a backup via custom recovery.
I would suggest making it clear that this is for root only (meaning, does not include custom recovery). Very important, because I have seen threads from other users where they got bricked and can no longer restore at all - too bad because they did not have a custom recovery backup.
Click to expand...
Click to collapse
@robalm writes in his OP, he uses LP rpm and tz (and cust) in his flashables 20x original fw flzshable zip (i've not verified it was the case)
http://forum.xda-developers.com/showthread.php?p=57223144
6ril1 said:
@robalm writes in his OP, he uses LP rpm and tz (and cust) in his rom (i've not verified it was the case)
http://forum.xda-developers.com/showthread.php?p=57223144
Click to expand...
Click to collapse
Yes, however that is a repackaged firmware (extract everything, root it, and then "bump" the necessary components, and then put it back together as a single flashable zip). That is why it will have root plus "bump" (bump'd boot.img and recovery.img a.k.a. custom recovery). Therefore, those who will download it will no longer have to root it manually. This guide (and mine) are different from repackaged firmwares, in the sense that we are not "pre-rooting" (or "pre-bumping") the firmware. We are rooting (or "bumping") the firmware after installation.
topet2k12001 said:
Yes, however that is a repackaged firmware. That is why it will have root plus "bump" (bump'd boot.img and recovery.img a.k.a. custom recovery). Therefore, those who will download it will no longer have to root it manually. Your guide (and mine) are different from repackaged firmwares, in the sense that we are not "pre-rooting" (or "pre-bumping") the firmware. We are rooting (or "bumping") the firmware after installation.
Click to expand...
Click to collapse
Yes, it seems it's a little different than @autoprime and you propose and i was asking myself if these three partitions were realy needed in this case (flashable zip from kdz exracted) or not.
I should prefer to let them in the bootstack version but maybe i'm xrong.
6ril1 said:
Yes, it seems it's a little different than @autoprime and you propose and i was asking myself if these three partitions were realy needed in this case (flashable zip from kdz exracted) or not.
I should prefer to let them in the bootstack version but maybe i'm xrong.
Click to expand...
Click to collapse
Ah, sorry I misunderstood what you were saying.
I do not know what rpm.img and tz.zip are for. I did read somewhere in XDA that tz.img is for the "radio" (or transmitter?). But I would suggest to keep those files (tz.img, rpm.img, aboot.img, sbl1.img) at "Kitkat version" because there will be a signature mismatch resulting to "certificate verify" or "security error" - if people want to have a custom recovery.
If people will NOT install a custom recovery (they just want root) then they can use this guide. The device will boot fine without the error messages, since recovery.img is Lollipop non-"bump'd" version (so the signatures match).
It should be possible to make a script that flash kk bootstack, bumped recovery and bumped kernel in a one click process, for a LP rooted.
6ril1 said:
It should be possible to make a script that flash kk bootstack, bumped recovery and bumped kernel in a one click process, for a LP rooted.
Click to expand...
Click to collapse
Yes, that's another way of approaching it. Or maybe create a flashable zip from it. But we will still need to instruct users to extract their Kitkat Image files (I don't think all Image partitions are the same for all variants), that's why I find the manual method (like @autoprime) to be a good approach because I personally find it to be more "universal".
One example: the D858HK does not have cust.img.
So for us to create an all-in-one script, zip, or approach, it would be difficult because of the many variants of the LG G3. Maybe if there were not that many variants, I'm sure skilled people like you can have a universal and convenient solution. For now, I still think that manual flashing is more universal.
topet2k12001 said:
Yes, that's another way of approaching it.
Click to expand...
Click to collapse
; -)
Tz trustzone,rpm ressource power managment, sbl secondary bootloader
https://wiki.linaro.org/Boards/IFC6410
6ril1 said:
; -)
Tz trustzone,rpm ressource power managment, sbl secondary bootloader
https://wiki.linaro.org/Boards/IFC6410
Click to expand...
Click to collapse
So that explains why even if the Lollipop versions are included/flashed, they won't cause an issue of signature mismatch. The Image file that causes a signature mismatch when you flash a "bump'd" file is aboot.img (the Android Bootloader). Which explains also in my experiment (prior to discovering it all and creating a thread) why I was initially able to "fix" my issue, following @autoprime's tutorial, when I flashed aboot.img - however, in exchange I lost "bump" status.
So basically, people will need to flash their Kitkat version of aboot.img and "bump" will still work (and will have custom recovery). That is our hypothesis at this point.
This reminds me: in my how-to guide, there was a user complaining about fast battery drain. Maybe if I advise him to flash the Lollipop version of rpm.img, that would help alleviate the issue. I will do an experiment and if this will succeed, I will update my how-to guide. In your case, for this thread's purpose, you may also do an experiment and create scripts.
Nice teamwork.
I don't know what "trustzone" is though. Will it affect signature mismatches? sbl1.img and rpm.img seem to be self-explanatory.
EDIT:
As mentioned previously, it is very dangerous to flash any of the restricted boot partitions such as sbl1, sbl2, sbl3, aboot or rpm. However it is safe to flash any other partition in order to install custom Linux builds and run them.
Click to expand...
Click to collapse
...do we really want people to touch this?
Edit:
[Procedure] http://forum.xda-developers.com/showpost.php?p=64841837&postcount=27
Edit/
I am creating this thread dedicated for me and other beginners "noobs".
Where should I begin as a beginner?
I am looking to unlock and root with latest MM that motorola supplies.
Things you should know about me:
I have no idea how to use adb.
I have no idea how to unlock & root or even if I should but I don't like ads.
I have no idea which firmware to use.
http://forum.xda-developers.com/moto-x-style/development/pure-firmware-tuff-wip-t3224833
http://forum.xda-developers.com/mot...rom-stock-rooted-debloated-x1575-6-0-t3262242
I am completely lost.
I have not gotten my phone yet, I ordered it this morning and will be here Friday. I am just trying to compile sources and info.
Thanks a bunch guys, I really need help with this.
One piece of advice for starters just since you used the word noob. Never mod your phone on a low battery. You can mess a phone up enough to break offline charging, and without a removable battery that you can swap out or charge in a cradle that could get awkward in a hurry on this phone. I always make sure I'm >75% just in case. You can fastboot your way out of all kinds of trouble; but not if your battery is dead and your phone is so screwed up it is not offline charging.
Your phone will probably show up with Android 5.1.1 installed, at least I got mine about 3 weeks ago and it did. Once it is through initial setup it should want to apply an OTA to Android 6.0 right away; if not check for it in Settings -> About -> System updates and it should find one. Just let it update before you do any setup or app downloading.
Once you're on MM, before you do any setup you have to unlock your bootloader if you intend to root. You'll get all the warnings about voiding warranty and here there be dragons, so be prepared for that. Also, unlocking the bootloader will wipe your internal storage, so don't bother with any setup or app downloading before you do it.
Start with Heisenberg's thread. It is a great guide on how to setup your computer for adb and fastboot as well as all the syntax you need for unlocking the bootloader and installing a custom recovery. Make sure to get the 2.8.7.1 version of TWRP that is patched to work with the MM bootloader.
When you boot to TWRP recovery for the first time it will ask if you want to keep system read only. Keep system read only and make a backup immediately. I usually make one backup of boot, system, and data, and a separate one of just efs; don't worry if you don't understand, you'll figure it out when you get there. TWRP is all touch based and pretty intuitive. This way you have good, untouched system backup to fall back on just in case.
When it comes to rooting MM, don't use the old system install method. Flash a SuperSU from this experimental systemless root thread (I used this instead of the ivcarlos method linked to the Heisenberg thread because it is more automated and easier). I can vouch for the 2.62-20151210170034 version of SuperSU. I've used it to root stock MM on this phone 3 or 4x as I've restored backups and changed kernels. I've heard the 2.64 and above SuperSU versions are not working with this phone on MM, and the older traditional system root methods like the v2.49 version that is linked to the Heisenberg thread are causing bootloops on MM. Don't panic on first boot after the systemless root; it appears to bootloop once but comes up normally the second time.
One other thing, TWRP doesn't seem to be able to detect the systemless rooting method, and it really wants your phone to be rooted. If/when TWRP offers to automatically install SuperSU, don't let it - ever - it will keep asking. It must use the old method that causes bootloops on MM, not the new systemless method linked above.
Once you're all rooted and settled in, if you get sick of the unlocked bootloader warning you can fix it by reading up in this thread. Just be sure to read carefully and get the MM logo and not the LP logo.
Wow, thank you so much for the long type up.
Duly noted and this is a great start. May I continue here if I run into any problems?
I think ima have fun with this phone
I am into tinkering with devices, "sometimes linux" etc, like my PC OS win7x64 is modified big time, so I probably will catch on with unlocking rooting etc very quickly.
I got chillz and cannot wait!
Read a lot. Do a lot of reading on the topic before trying it. Basically learn all the possible errors or negative outcomes before they happen, so your not blindsided and are ready for anything that can happen.
gokart2 said:
Read a lot. Do a lot of reading on the topic before trying it. Basically learn all the possible errors or negative outcomes before they happen, so your not blindsided and are ready for anything that can happen.
Click to expand...
Click to collapse
Will do. I was reading, flashing can screw up the modem,wif and what ever else.
I hope I don't screw it up.
Hitti2 said:
Will do. I was reading, flashing can screw up the modem,wif and what ever else.
I hope I don't screw it up.
Click to expand...
Click to collapse
Good luck :good:
I just noticed one thing that might not be entirely clear in the Heisenberg thread. It says to enable adb in the Settings -> Developer Options menu, but by default you won't have a Developer Options menu.
To get one, go into Settings -> About Phone, scroll all the way to the bottom, and tap on build number about 8 or 10 times. Your phone will say something to the effect of congratulations now you're a developer, and you'll have the menu.
Edit: i just noticed it says how to enable developer options further down the page
ty, I will need it lol.
Dev options were on my S5 too. My pops showed me how to on the S5, kinda hoping it was the same way to enable them, turned out to be. Cool.
gokart2 said:
Read a lot. Do a lot of reading on the topic before trying it. Basically learn all the possible errors or negative outcomes before they happen, so your not blindsided and are ready for anything that can happen.
Click to expand...
Click to collapse
^^^This^^^
and remember what XDA is really for ...http://forum.xda-developers.com/showpost.php?p=2031989
with that, enjoy all the reading, and do not be afraid to look at other sites too, there are even videos around that can help guide you...
and there are fellow members here to help...but most questions have already been asked and answered, so search first! Cheers! :highfive:
This might sound so stupid.
So, I will begin with the recommendation of installing twrp as my first step.
http://forum.xda-developers.com/showpost.php?p=64545146&postcount=131
1) Be sure to get the newest TWRP that has been patched for M.
Click to expand...
Click to collapse
How do I go on installing this TWRP? Does it include flashing TWRP to the phone? Or is an app? I don't understand.
How many ROMs can be flashed to the phone, 2? TWRP & Marshmallow?
Hitti2 said:
This might sound so stupid.
So, I will begin with the recommendation of installing twrp as my first step.
http://forum.xda-developers.com/showpost.php?p=64545146&postcount=131
How do I go on installing this TWRP? Does it include flashing TWRP to the phone? Or is an app? I don't understand.
How many ROMs can be flashed to the phone, 2? TWRP & Marshmallow?
Click to expand...
Click to collapse
Sounds like you need to do more studying and reading
TWRP is not a ROM, it is a custom recovery image, which allows you to flash ROMs.
Start here..http://androiding.how/root-moto-x-pure/
Then go here..http://forum.xda-developers.com/mot...l-windroid-universal-android-toolkit-t3206883 for a good tool. (May have already been linked above...)
[Q] Where should I begin as a beginner?
At the beginning, of course.
Sorry couldn't resist...
Naddict said:
Sounds like you need to do more studying and reading
TWRP is not a ROM, it is a custom recovery image, which allows you to flash ROMs.
Start here..http://androiding.how/root-moto-x-pure/
Then go here..http://forum.xda-developers.com/mot...l-windroid-universal-android-toolkit-t3206883 for a good tool. (May have already been linked above...)
Click to expand...
Click to collapse
Tyvm.
Before I proceed, I need to backup, right? How do I go forth doing a backup?
Also, I am updated on MM, does those two links above work on MM?
Hitti2 said:
Tyvm.
Before I proceed, I need to backup, right? How do I go forth doing a backup?
Also, I am updated on MM, does those two links above work on MM?
Click to expand...
Click to collapse
after you unlock and install custom recovery, you use TWRP (the custom recovery) to create the backup...
as you are on MM, you cannot use the "all in one" application that I provided in the link...so you will have to manually install/flash your rom
Wow im so frustrated. I think i give up. There is no guides upto date to do exactly twrp, backup, install w/e n root for ota mm.
I'll donate 30 usd via paypal if someone can.
Hitti2 said:
Wow im so frustrated. I think i give up. There is no guides upto date to do exactly twrp, backup, install w/e n root for ota mm.
I'll donate 30 usd via paypal if someone can.
Click to expand...
Click to collapse
Clearly you are impatient (not trying to be rude here), - XDA truly is not a place to pay for someone to do it for you, XDA is about learning and development, there are several places that a search will get you what you need. Many members have also posted links above to vast amount of information (specifically this post and this entire thread here http://forum.xda-developers.com/showpost.php?p=64183396&postcount=151 and here too http://forum.xda-developers.com/showpost.php?p=64311581&postcount=171) that you should take time to read and then, as you move through these things then you ask questions.
Offering to pay to have someone do it for you is really not what this site is about.
Read, do google searches...it has been done a hundred time already mate, take the time to learn what it is you are doing before actually doing it.
I dont have 400 to spare for for another phone if i brick this one because i was pointed to all kinds of mixed links. Ionno ill wait till someone comes up with a guide then.
Thanks.
Edit:
Let it be known as well, because you know how to milk a cow doesn't mean I know how to milk a cow. Or change a complete motor out of a vehicle etc.
Not being a smartarsh either. I'll prob end up like this guy https://www.reddit.com/r/MotoX/comments/3z2e6g/stuck_rooting_moto_x_pure_on_60/
And I read this, http://forums.androidcentral.com/moto-x-pure-edition/622331-6-0-marshmallow-root.html#post4899736
Dunno which one to go for.
I'm done for today, I'll come back tomorrow to upset with this.
Hitti2 said:
I dont have 400 to spare for for another phone if i brick this one because i was pointed to all kinds of mixed links. Ionno ill wait till someone comes up with a guide then.
Thanks.
Edit:
Let it be known as well, because you know how to milk a cow doesn't mean I know how to milk a cow. Or change a complete motor out of a vehicle etc.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=2031989
Hitti2 said:
Not being a smartarsh either. I'll prob end up like this guy https://www.reddit.com/r/MotoX/comments/3z2e6g/stuck_rooting_moto_x_pure_on_60/
And I read this, http://forums.androidcentral.com/moto-x-pure-edition/622331-6-0-marshmallow-root.html#post4899736
Dunno which one to go for.
I'm done for today, I'll come back tomorrow to upset with this.
Click to expand...
Click to collapse
Looks to me like several folks in there offered suggestions on how to successfully get root ...and again, as my last helpful post here...you really need to read Heisenberg's thread, that guide works, and from what I can tell, you have to use systemless root.
Ok, I will follow
Intro
This thread will serve as a location for basic how-to guides for the Moto X Pure. I'm going to start off with a couple of the more obvious ones and go from there. If anyone has any suggestions for additions please feel free to let me know.
Prerequisites:
You'll need a working adb/fastboot environment on your PC to get through some of these guides. Go here to download the Android SDK, which will give you most updated version of adb and fastboot. Scroll to the bottom of the page and find Other Download Options>SDK Tools Only, and grab the right version for your OS. While it's downloading create a folder in C:\ called SDK (C:\SDK). Once you've downloaded the zip you can extract it into your C:\SDK folder. Navigate to C:\SDK\android-sdk-windows and open SDK Manager.exe. In SDK Manager you need to install the following packages:
Tools> Android SDK Tools, Android SDK Platform-tools
Extras> Android Support Library
Once you have installed those, inside C:\SDK you should see some new folders, one of them will be called platform-tools, within that folder you should see fastboot.exe and adb.exe. I'll refer to this as your fastboot folder/directory or working folder/directory during this guide. To make sure adb is correctly installed, open a command prompt from within your fastboot folder (hold shift + right click, select open command prompt here) and issue this command:
Code:
adb version
If it returns a version number for Android Debug Bridge then you're good to go.
You'll find Motorla drivers here, download it and install, then reboot your PC.
You can test adb by connecting your device to your PC while booted into Android (making sure that adb/usb debugging is enabled in Settings>Developer Options) with the screen unlocked and issuing this command:
Code:
adb devices
It should return your device serial number, if so, adb is working.
You can test fastboot by connecting your device to your PC while booted into fastboot mode (power + volume down) and issuing this command:
Code:
fastboot devices
It should return your device serial number, if so, fastboot is working.
By attempting any of the processes listed this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches on fire, or turns into a hipster and claims to have been modified before it was cool.
Index
How To Unlock Your Bootloader
How To Install A Custom Recovery On Your Device
How To Make A Nandroid Backup With TWRP Recovery
How To Root Your Stock Rom
How To Install A ROM with TWRP Recovery
How To Install A Custom Kernel With TWRP Recovery
How To Make Sure You Can Pretty Much Always Recover From An Accidentally Wiped System
1. How To Unlock Your Bootloader
Go into About Phone in Settings, click on Build Number 7 or 8 times until it says you have enabled Developer Options. Go back to Settings and enter the newly opened Developer Options section, scroll and click on the Enable OEM Unlock option.
Power off your phone then boot into fastboot mode (power + volume down).
Connect your phone to your PC via usb cable.
Open a command prompt from within your fastboot folder (navigate to where you have fastboot.exe located on your PC, shift + right click anywhere within that folder, select open command prompt here).
Check your fastboot connection by issuing this command:
Code:
fastboot devices
It should return your device serial number, if not you need to make sure your drivers are installed correctly.
Once you've confirmed your fastboot connection issue this command:
Code:
fastboot oem get_unlock_data
It should return something like this:
Code:
(bootloader) 0A40040192024205#4C4D3556313230
(bootloader) 30373731363031303332323239#BD00
(bootloader) 8A672BA4746C2CE02328A2AC0C39F95
(bootloader) 1A3E5#1F53280002000000000000000
(bootloader) 0000000
Copy that code (with no spaces between the characters) and paste it somewhere for safekeeping, you'll use it in a minute.
Go to the Motorola bootloader unlocking page. You'll need to create an account with Motorola if you don't already have one. Once you're signed in you can scroll down to step 6 and paste the above code into the text field and hit the “can my device be unlocked” button.
Read the terms and conditions and accept them if you agree (you can't continue unless you accept).
Click the “request unlock key” button and an email with your unlock token will be sent to the email account that you signed up with.
Once you have retrieved the token from the email you can use it within the following command to unlock your bootloader:
Code:
fastboot oem unlock xxxxxxxxxx
(Replace the xxxxxxxx with your unique unlock token)
Your bootloader is now unlocked!
Reboot with this command:
Code:
fastboot reboot
It's now safe to disconnect your usb cable.
Please note: this will erase all user data from your device, it is best to do this before you really start using the device and installing apps or putting data on the internal storage
2. How To Install A Custom Recovery On Your Device
Prerequisites: unlocked bootloader.
Download the recovery of your choice, here's TWRP.
Make sure you check the md5 to verify its integrity (where possible).
Place the file in your fastboot folder (this is where fastboot.exe is located on your PC).
Put the phone in fastboot mode and connect it to your PC via usb cable.
Open a command prompt from within your fastboot folder (shift + right click, select open command prompt here), and enter the following commands:
Code:
fastboot flash recovery <filename>.img
(Replace <filename> with the actual filename of the recovery, the recovery filename in the command will change depending on which recovery you're flashing)
Wait for the recovery to flash, it'll only take a few seconds, you'll get a finished message in your command prompt window once it's done.
It's now safe to disconnect your usb cable.
Don't reboot the phone normally, use the volume buttons to highlight recovery and press the power button to select it. This will stop the stock OS from patching it with the stock recovery in boot. Once you've booted into TWRP like this once, you can reboot normally.
3. How To Make A Nandroid Backup With TWRP Recovery
Prerequisites: unlocked bootloader, TWRP recovery.
A nandroid backup is a very important thing to have before installing any custom software on your device. It's basically a backup of your stock system that you can fall back on if anything goes wrong or if you just want your stock ROM back. You can also use the backup tool to create a backup of your favourite ROM set up exactly the way you like it. The backup you create can be easily restored using the restore tool in TWRP recovery.
All you need to do is enter TWRP recovery, select the backup option from the TWRP home screen, check the system/data/boot boxes, and swipe to backup. The process will take a few minutes.
Click to expand...
Click to collapse
& I will follow
Hello guys!
I make my own ROOT (systemless, thanks for Chainfire) images for Moto X Style with Marshmallow (build MPH24.49-18). Its use "experimental" systemless SuperSU version 2.56 - more info on http://forum.xda-developers.com/show...35&postcount=2. No need replace bootloader or recovery. Still need unlocked booloader.
Because TWRP didn't work in this version of bootloader (0xA048), I cooked "su.img" in a Linux box and used "/data/local/tmp" as bridge (accessible by ADB).
WARNING! I am not responsible for any harm on your phone. When you're not sure if you can do it, leave it!
For use, you need
1) unlocked bootloader.
2) if your bootloader not unlocked, make sure you have copy of your data, because this process will erase your device.
3) install ADB and FASTBOOT on your pc using minimal ADB or Android SDK.
4) install ADB drivers from Motorola or Universal ADB.
5) download provided files.
6) download SuperSU ver. 2.56 from http://forum.xda-developers.com/apps...ellow-t3219344.
Steps:
1) extract files in a folder of your choice (su.img, boot.img).
2) extract Superuser.apk from SuperSU-v2.56-20151030013730.zip from common folder.
3) enable USB debugging on Android.
4) connect your device on pc.
5) open a command prompt in a new folder.
6) type "adb push su.img /data/local/tmp" without quotes.
7) type "adb install Superuser.apk" without quotes.
8) now reboot your device into fastboot mode by typing "adb reboot bootloader".
9) type "fastboot flash boot boot.img" without quotes.
10) type "fastboot reboot" without quotes.
And enjoy!
Now you have a rooted MotoX Style Marshmallow. To apply any OTAs, you only need reflash stock boot.
Click to expand...
Click to collapse
I still think its going to brick but uhwell.
So far so good, I've got it unlocked.
I apologize for my ignorance. I am gonna take it a step at a time.
Doing step one "unlocking" was scary but it went good.
Wish me luck!
:good:
I have cm13 ported over from different Phone (Blu Life_Max) and booting.
already working
1. wifi
2. camera but not video camera
3. bluetooth audio
4. loud speaker audio
5. FM Radio
6. cell in sim1 and sim2 slot, but sim2 only gets H+ speed(5-10Mbps)
SIm1 gets 4G(LTE) speeds on test 50Mbps Both tests with freedomPop
known issue (mostly camera related)
1. videocamera causes camera crash
2. selfie-camera not available **Fixed with V6**
3. panarama shot crashes camera
4. NFC not able to turn on (stock rom did not have NFC, so this may not be possible to work) : next update may remove this **fixed in V5**
V7 -- Hassome permission changes in boot.img that were found in logcat, for "SMI"
still not working videocamera
To install:
1. Must be bootloader unlocked
.
How to Unlock Bootloader via Fastboot
1. Setup ADB and Fastboot on your PC.
2. Enable USB debugging and OEM Unlock on your Android device.
3. Connect your device to the PC with a USB cable.
4. Open a command window on your PC.
5. Boot your device into bootloader mode using the following command:
Code:
adb reboot bootloader
└ You may get a request to authorize USB debugging on the device, accept it.
6. Once your device is in bootloader mode, issue the following command to unlock bootloader:
Code:
fastboot oem unlock
You get a confirmation screen on your device. Press Volume Up button to highlight Yes and press Power button to select it.
This will begin bootloader unlocking process, which shouldn’t last more than couple of minutes.
7. Once bootloader is unlocked, your device will reboot into bootloader mode. You need to boot it into system now using the command below:
Code:
fastboot reboot
During reboot, your device will go through a factory reset and then finally boot into system.
2. Install included twrp(New kernel for recovery allows touchscreen to work)
***PRIOR RELEASES NEED TO USE LOPESTOM RECOVERY TO INSTALL***
Due to different moint point descriptions Future versions(If they come) will use block number moints to be compatible with both
******V-7-Block is compatible with both recoveries
1. make sure developer options is enabled
2. Reboot to bootloader
Code:
adb reboot bootloader
3. Test recovery works for your device
(example commands assume you have the vampirefo version of recovery downloaded to the desktop)
Code:
Fastboot boot Desktop/recovery-TWRP-3.1.1-Vampirefo-studio-xl-2.img
4. If recovery boots good, then return to bootloader and flash (commands work from in booted twrp)
These steps are what I find to be best order to prevent the stock rom from replacing the stock recovery on boot.
Code:
fastboot flash recovery Desktop/recovery-TWRP-3.1.1-Vampirefo-studio-xl-2.img
fastboot boot Desktop/recovery-TWRP-3.1.1-Vampirefo-studio-xl-2.img
adb wait-for-device
adb reboot recovery
3. If first install. do wipe and wipe system too. If Updating no wipe needed
Sources:
Rom not built for this device Built for Blu Life-Max --no thread to link, sorry
Rom uses the stock kernel, pulled from oem device (studio_XL_2)
keeping a git of files swapped to make rom work
https://github.com/mrmazakblu/BLU_Studio-XL-2_port_from_Life-Max
kernel source for recovery:
https://github.com/mrmazakblu/Blu_studio-XL_2_kernel_source
Other projects for Studio_XL_2:
Reserrection Remix Port
XDA:DevDB Information
blu-studio-xl-2, ROM for all devices (see above for details)
Contributors
mrmazak, Thanks to vampirefo --building donor rom
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.10.x
ROM Firmware Required: BLU-Studio-XL-2--BLU_S0270UU_V09_GENERIC
Based On: Lineage OS
Version Information
Status: Testing
Created 2017-10-30
Last Updated 2017-11-30
New TWPR kernel
Reserved
TWRP touchscreen
new kernel for TWRP allows touchscreen to work when recovery is flashed to device.
thanks to @vampirefo for finding a fix for Life-Max. Same fix worked here too.
New kernel is also put into @lopestom twrp.
Choose either one they both work.
Thanks for porting. I'm looking forward to testing it with my Studio XL2
killer13666 said:
I tried flashing it like you said and this is what happened....
Code:
Installing zip file '/external_sd/BLU_Studio-XL-2_port_from_Life-Max-V-7.zip'
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
I:Update binary zip
I:Zip contains SELinux file_contexts file in its root. Extracting to /file_contexts
I:Legacy property environment initialized.
Target: Blu Studio XL 2
Target: Blu Studio XL 2Check if system is already mounted
Check if system is already mountedcould not detect filesystem for /dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/system, assuming ext4could not detect filesystem for /dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/system, assuming ext4
mount: failed to mount /dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/system at /system: No such file or directorymount: failed to mount /dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/system at /system: No such file or directoryRunning backup script for update installsabout to run program [/tmp/install/bin/backuptool.sh] with 2 args
Running backup script for update installs
run_program: child exited with status 127
unmount of /system failed; no such volumeChecking if Data is compatableunmount of /system failed; no such volume
Checking if Data is compatable
about to run program [/tmp/install/bin/otasigcheck.sh] with 1 args
You have an installed system that isn't signed with this build's key, aborting...
run_program: child exited with status 124
script aborted: Can't install this package on top of incompatible data. Please try another package or run a factory reset
Can't install this package on top of incompatible data. Please try another package or run a factory reset
Updater process ended with ERROR: 7
I:Legacy property environment disabled.
I:Install took 14 second(s).
Error installing zip file '/external_sd/BLU_Studio-XL-2_port_from_Life-Max-V-7.zip'
Updating partition details...
Click to expand...
Click to collapse
Do not know why you have failed to mount /system error could be because you have /system set to be read only.
In install directions it says need to wipe /data
and
also advanvance wipe /system
second error says imcompatable /data == this means you did not wipe data before installing.
Please continue here in the rom thread.
mrmazak said:
Do not know why you have failed to mount /system error could be because you have /system set to be read only.
In install directions it says need to wipe /data
and
also advanvance wipe /system
second error says imcompatable /data == this means you did not wipe data before installing.
Please continue here in the rom thread.
Click to expand...
Click to collapse
I figured out what the problem was. For some reason, the recovery image you supplied wasn't mounting the system partition properly. I used a different image and the ROM flashed perfectly
killer13666 said:
I figured out what the problem was. For some reason, the recovery image you supplied wasn't mounting the system partition properly. I used a different image and the ROM flashed perfectly
Click to expand...
Click to collapse
please let me know which one worked for you and which one did not.
I think I was using the one marked 3.1.1 (vampirefo) but now I am not sure.
I may do independet testing again on both, but would appreciate your input.
Just confirmed there is a problem with the combination of the update-binary used in these install zips and the vampirefo recovery. The fix can be either i use different update-binary file or you use lopestom recovery.
**EDIT**
Problem was with the my updateer-script. I put fixed install packages up.
Thanks for the port my version is v06.0.04.00_generic 16/06/2017
I have a unlocked phone from best buy
I keep seeing everyone say v09 mine has updated twice wondering if it will work on mine or if I need to update somehow
ahnuts72 said:
Thanks for the port my version is v06.0.04.00_generic 16/06/2017
I have a unlocked phone from best buy
I keep seeing everyone say v09 mine has updated twice wondering if it will work on mine or if I need to update somehow
Click to expand...
Click to collapse
I dont see any version of my stock OS that is similar to that number you have.
When I had stock installed, In the settings screen, about phone listed the build version as
Code:
BLU_S0270UU_V09_GENERIC
This port is for Blu_Studio_XL_2 make sure that is device you have.
If you look in the build.prop you will get more information about the device.
if you want to , you can pull the build.prop and post it , so I can see
Code:
adb pull /system/build.prop Desktop\build-prop.txt
then attach the file here.
According to the device in about phone mine is studio xl 2 and that was what the box said when I purchased the phone at best buy
And this one shows the version
And this one shows the version
Wrong pic
ahnuts72 said:
Wrong pic
Click to expand...
Click to collapse
The dates show it is a newer software than what I had, but this should still work, as long as you are still able to unlock the bootloader.
In the developer options I have a setting that says oem unlocking allow the bootloader to be unlocked will that work or will I have to still do it from adb
ahnuts72 said:
In the developer options I have a setting that says oem unlocking allow the bootloader to be unlocked will that work or will I have to still do it from adb
Click to expand...
Click to collapse
here is guide.
https://www.theandroidsoul.com/unlock-bootloader-via-fastboot-android/
the unlocking does do a complete wpe on the data part of the phone. so if you have pictures or music or any files you want to keep , make sure to copy first. Also to be safe , if you have external sdcard in , take it out before doing unlock
****
****
Must complete the unlock as the guide shows includeing the reboot, so stock recovery does its wipe, I t is important part of the unlock.
**
**
after unlocked,
to flash recovery, enable developer options again, enable usb debugging. authorize adb connection to your pc-
Code:
adb reboot bootloader
fastboot boot recovery.img
**recovery.img = "full path to the downloaded recovery"
**example if you downloaded the vampire based recovery and you downloaded to the desktop**
Code:
fastboot boot Desktop/recovery-TWRP-3.1.1-Vampirefo-studio-xl-2.img
after booted to recovery and it works return to bootloader and flash it to phone. I allways recomend this boot first method to verify it recovery works. You cant be certain every od will work on every device. Better safe than sorry.
select reboot menu from recovery and then select reboot bootloader.
Due to a securety measure android has (recovery-from-boot) when replacing recvoery to need to boot directly to new recovery to prevent the android system from replacing it with stock version. so I use the steps below
Code:
fastboot flash recovery Desktop/recovery-TWRP-3.1.1-Vampirefo-studio-xl-2.img
fastboot boot Desktop/recovery-TWRP-3.1.1-Vampirefo-studio-xl-2.img
adb wait-for-device
adb reboot recovery
.
Android 6 or 7, plus install questions
Hi, I have rooted several phones but the procedure keeps getting more difficult. I see the instructions for installing recovery-TWRP-3.1.1-Vampirefo-studio-xl-2.img but I am curious what is on this image .... will it be rooted and if so, what version of Android is bundled? Will the phone then support Xposed and Xprivacy?
From what I can determine, the video camera is not working with your most recent release, V8, is this correct?
Thank you for your assistance!
Donphillipe said:
Hi, I have rooted several phones but the procedure keeps getting more difficult. I see the instructions for installing recovery-TWRP-3.1.1-Vampirefo-studio-xl-2.img but I am curious what is on this image .... will it be rooted and if so, what version of Android is bundled? Will the phone then support Xposed and Xprivacy?
From what I can determine, the video camera is not working with your most recent release, V8, is this correct?
Thank you for your assistance!
Click to expand...
Click to collapse
LineageOS 13 is android 6
there is no V8 only upto V7
video recording does not work
Lineage has root built in. Enable it in developer options
I do not know about xposed I not use it
Donphillipe said:
" I see the instructions for installing recovery-TWRP-3.1.1-Vampirefo-studio-xl-2.img but I am curious what is on this image "
Click to expand...
Click to collapse
That image is TWRP recovery only
I have not been working on this anymore.
I have ported "better" Resurection rom based on android 7 , have been using it as a daily use phone for just over a month now
https://forum.xda-developers.com/android/development/-t3699638
I appreciate your patience with someone who only dabbles in this hobby. When you say that the install image is TWRP only, what exactly does this mean?
I know I have owned several BLU phones and each time I tried to install a high-end recovery tool in the past, the list of supported phones on the recovery software list would never include my BLU device, saying something to the order of the source needing to be recompiled (as I recall) or something to that order which never seemed to happen. So are there additional steps for getting the phone to the point it will take this image other than the steps you outlined for unlocking the boot loader? Or what do I need to be aware of?
Also, do you have a backup of the factory image available in case something goes wrong, with basic instructions on how to recover the phone back to the factory version? Or is there something I can install or do on this phone to create a backup copy on my own?
Again I am sorry to have to ask for what to some appears a simple procedure. I do appreciate your going to the effort when you have already contributed so much with your images. Thank you!
Donphillipe said:
I appreciate your patience with someone who only dabbles in this hobby. When you say that the install image is TWRP only, what exactly does this mean?
I know I have owned several BLU phones and each time I tried to install a high-end recovery tool in the past, the list of supported phones on the recovery software list would never include my BLU device, saying something to the order of the source needing to be recompiled (as I recall) or something to that order which never seemed to happen. So are there additional steps for getting the phone to the point it will take this image other than the steps you outlined for unlocking the boot loader? Or what do I need to be aware of?
Also, do you have a backup of the factory image available in case something goes wrong, with basic instructions on how to recover the phone back to the factory version? Or is there something I can install or do on this phone to create a backup copy on my own?
Again I am sorry to have to ask for what to some appears a simple procedure. I do appreciate your going to the effort when you have already contributed so much with your images. Thank you!
Click to expand...
Click to collapse
The recovery image (TWRP) works for this device.
Yes recovery images, just like android roms are specific to each different device. This one has been edited to work for Studio XL 2
The TWRP is a custum recovery needed to install the custom ROM
The steps are complete, you shouldn't need anything else (need adb and fastboot)
Yes stock recovery image is available. Installing back to stock recovery is same steps as installing custom recovery.
both can be done as described with fastboot. Or both can be installed using SPFT (smart phone flash tool)
TWRP Custom Recovery for the Onn Android Tablet series
This is the first fully-featured custom recovery for Walmart's MediaTek-based Onn tablets: ONA19TB002, ONA19TB003 and ONA19TB007. TWRP needs no introduction. If you have come here, you probably have some idea of what it is and what it's used for. This TWRP build does not need the bootloader unlocked or VBMeta verification disabled, although it's recommended that you at least unlock the bootloader.
DISCLAIMER
Everything described in this thread is done at your own risk. No one else will be responsible for any data loss, corruption or damage of your device, including that which results from bugs in this software.
FEATURES
Decrypted data partition
All USB modes functional: MTP, ADB, Mass Storage, OTG, Charging
Fast boot time
Adoptable storage mounting
Firmware image backup and restore
Works under locked bootloader
Android 9 build fits within the 16MB recovery partition -- no compromises or partition resizing necessary
INSTALLATION METHOD 1
Download the recovery to your PC and unzip the image
Unlock the bootloader (skip if you have already done this)
Enable OEM Unlock in Developer Options in Android Settings
Boot into fastboot mode either by holding vol. up+power to power it on and selecting "Fastboot mode", or by running the 'adb reboot bootloader' command from within Android.
Install fastboot and appropriate drivers on your PC if you have not set those up
Unlock the bootloader with the command
Code:
fastboot flashing unlock
...and follow the instructions on the screen. This will wipe your data.
Flash the custom recovery with
Code:
fastboot flash recovery twrp-3.3.1-ONA19TB002.img
(use the right file name path for your device)
Reboot to recovery with
Code:
fastboot oem reboot-recovery
INSTALLATION METHOD 2
This assumes you are familiar with SP Flash Tool or can figure it out on your own
Download the recovery to your PC and unzip the image
Get the appropriate scatter file for your device. The scatter file may be found in the device's firmware under /system/data/misc.
Set up SPFT Download tab as Download Only. Load your scatter file.
Under the recovery line, double-click Location and open your TWRP image.
Click Download and connect your powered-off tablet to your PC. SPFT will automatically flash the recovery to the emmc and disconnect when finished.
INSTALLATION METHOD 3
Head over to Amazing Temp Root for MediaTek ARMv8, read the requirements and directions, and grab the latest mtk-su.
Open a root shell with mtk-su
Flash the (unzipped) recovery with the command:
Code:
dd bs=1048576 if=twrp-3.3.1-0-ONA19TB002.img of=/dev/block/by-name/recovery
(replace the if= file name with your appropriate recovery image path)
Exit root shell
START RECOVERY
Three methods:
On a powered off tablet, hold Vol. up+power for about 3 seconds. In the menu that appears, select "Recovery mode"
With Android ADB, use the command 'adb reboot recovery'
From Android root shell, use the command 'reboot recovery' or just use any root app with OS reboot features
NOTES
Kind of important: Make a backup of your Crypto Footer as soon as you can. This is the encryption key to your data partition. When accessed from TWRP, this key can get "upgraded" so that you will get locked out of Android. TWRP uses a hacky workaround that saves and restores the original footer on every /data decrypt. But that method is not what I would call 100% reliable.
Make sure you have a backup of the untouched stock system and vendor images. There are no official firmware packages available to download.
Only mount system/vendor partitions in read/write mode if you have unlocked the bootloader. It is recommended to choose to leave system read-only at the startup prompt unless you have a specific reason to modify it. If the bootloader is locked, then dm-verity is enforced.* So merely mounting it once in r/w will cause a boot loop.
It's currently not possible to install incremental OTA updates using this TWRP. Use the stock recovery to update the FW. That will only work if you have never mounted system/vendor in write mode.
DOWNLOAD (Nov. 30, 2019)
Current version: 3.3.1-1
ONA19TB002 - Onn 8" model
ONA19TB003 - Onn 10.1" model
ONA19TB007 - Onn 10.1" w/keyboard model
Source code
ONA19TB002 | ONA19TB003 | ONA19TB007
ACKNOWLEDGEMENTS
The team behind TWRP & OmniROM
@tek3195 for testing and feedback on the 8" model
Please post feedback since these are still pretty new and not exhaustively tested. Let me know if I should port it to other models in the series.
Reserved also
grabbing this one too cuz why not
Very nice! I'll download and test the 003 one soon.
I also have a 007 model to experiment with.
I tried about a dozen times to build TWRP and failed miserably LOL. Closest I got was one that would boot but the rotation was all messed up, USB wouldn't work, didn't mount some partitions... Yeah, it was a hot mess.
Do you happen to have sources available?
Hi @NFSP G35,
I'll have the source code soon. Most of the tricks involved patching bootable/recovery. So I need to commit those changes and include the proper patch set from my tree....
Amazing!! Gonna install and test 8" right now.
Has anyone tried a GSI on these tablets yet?
MishaalRahman said:
Has anyone tried a GSI on these tablets yet?
Click to expand...
Click to collapse
I do know @tek3195 , the Onn 8 thread starter, has tried many of them as well as others here, somewhere on that thread he listed his tests and opinion of several of them.
I'm pretty sure others on that thread have also tried GSI's.
MishaalRahman said:
Has anyone tried a GSI on these tablets yet?
Click to expand...
Click to collapse
I did try both Phhuson vanilla and also Liquid Remix (I'm keeping this one for now). I didn't flash them through twrp, but using fastboot via bootloader.
WoW! AwEsOmE! I cannot wait to try this! THANK YOU!!!!!!
Hey,
This is a neat thing to see for the Onn tablets. I have a question though. I own a device based on the mt8163, and am trying to help people with another device I don't own (the powkiddy x18 which also uses the mt8163). One of the things I wanted to do was to make a custom rom for the x18, since it's stock firmware is horrible. And of course, one of the first steps to custom roms is twrp. So I have a question for you that I hope you can answer for me. How did you make this build of twrp? I have seen no device trees for this device so I was kinda curious. If you can help me in any way, I'd be so grateful, and I'm sure the other people with the x18 would be grateful for help.
@diplomatic
Is there a different procedure for installing TWRP on a locked bootloader?
I can confirm that using SP Flash to load your TWRP.img will produce a bootloop when installing to a device with the BL locked. Reflashing the original recovery.img makes the problem go away. You mentioned in the OP that this TWRP will work on a locked BL so I thought I would share my case study with you in following the procedure you defined.
MY SINCERE GRATITUDE FOR YOUR EFFORTS IN PORTING THIS TO THE ONN!
You're welcome, @Spatry.... Can you describe how you ended up with a locked BL? Was it unlocked before? Have you ever tweaked vbmeta? Also, when you say bootloop, do you mean for Android or just for recovery? I'm not going to insist that it works under locked BL. I tested it once and it did boot up...
diplomatic said:
You're welcome, @Spatry.... Can you describe how you ended up with a locked BL? Was it unlocked before? Have you ever tweaked vbmeta? Also, when you say bootloop, do you mean for Android or just for recovery? I'm not going to insist that it works under locked BL. I tested it once and it did boot up...
Click to expand...
Click to collapse
Presently, I am running stock with Magisk patched BOOT on locked bootloader, stock vbmeta. The boot loop was at the ONN Android screen, I could not get it to even boot into recovery.
At one time I did run with the bootloader unlocked (with --disable-verification on stock vbmeta) and I ran Phusson's AOSP, Liquid Remix and Bliss. I found there was no benefit to me in running the other mods so I reverted back to stock courtesy of @CaffeinePizza and the bootloader re-locked to get rid of that annoying 5 second orange state.
In each instance, I always used SP Flash tools to load all .img files. I only used fastboot to install magisk_patched.img onto the stock installation. Unlocking the bootloader erases all data and I did not feel like reinstalling everything again, so I figured I would try to install TWRP per your instruction to see if it would work while the BL was still locked... Restoring the original recovery got rid of the bootloop. I do want to try your TWRP so I will try it with BL unlocked when I get some free time to do so.
Spatry said:
Presently, I am running stock with Magisk patched BOOT on locked bootloader, stock vbmeta. The boot loop was at the ONN Android screen, I could not get it to even boot into recovery.
Click to expand...
Click to collapse
This sounds like you might have flashed a wrong/corrupt image to recovery. It may have to do with AVB checks rather than bootloader lock. But those conditions might be interdependent somehow so I can't tell you for sure. The fact that you are able to boot a patched image on a locked BL says it doesn't care too much about verification. I can tell you for sure that any recovery image must have avb metadata, not necessarily the required hash, for both Android and recovery to boot. Can you try to unzip the image file and flash it over again?
Hmm, the situation with the bootloader lock sounds eerily similar to the Nabi SE. The latter also had a similar implementation where there's not much in the way of locking things down, other than an (easily circumvented) SP Flash Tool signature check and different preloader keys. And here's the real kicker: the nearly-identical Fisher Price Nabi also ran on the MT8163, so it makes me wonder if it's possible to boot Pie on it, or perhaps a GSI assuming that Treble can be tacked onto it.
Also, do you have the source repo to this TWRP port of yours?
If anyone here gave me an XDA ad-free subscription, thanks a lot! I didn't get a notification of who it was. Using this site is a lot more bearable now.
diplomatic said:
If anyone here gave me an XDA ad-free subscription, thanks a lot! I didn't get a notification of who it was. Using this site is a lot more bearable now.
Click to expand...
Click to collapse
Where do I find crypto footer to backup
diplomatic said:
If anyone here gave me an XDA ad-free subscription, thanks a lot! I didn't get a notification of who it was. Using this site is a lot more bearable now.
Click to expand...
Click to collapse
Kinda cool without the ads isn't it. I know I sent one about a week ago or so. I think everybody ought to send you one, you deserve it. THANKS and AWESOME work.
Red Magic 5G Bootloader Unlock Guide: OR get ROOT & TWRP without unlocking the BL!!!
***Bootloader Unlock Instructions for the Nubia Redmagic 5G + installing TWRP:***
WARNING: ANY BOOTLOADER UNLOCK METHOD INVOLVES THE RISK OF BRICKING YOUR DEVICE PERMANENTLY. WHILE THERE IS USUALLY A WAY TO RECOVER, DO NOT ATTEMPT THIS PROCEDURE IF YOU DO NOT KNOW WHAT YOU ARE DOING. BAD THINGS CAN HAPPEN. YOU HAVE BEEN WARNED!!! YOU MAY BE LEFT WITH A USELESS BRICK!!! READ ALL FURTHER WARNINGS EXPERIMENTAL METHOD IN ORIGINAL DOWNLOAD FILE WORKS, I'M USING IT
If you want a NOOB guide look at this post: https://forum.xda-developers.com/nu...beginner-tutorial-unlock-bootloader-t4131585/
Also note a user has managed to fix the FP sensor post BL unlock, see this post here: https://forum.xda-developers.com/nu.../guide-calibration-finger-print-loss-t4132961
Still, I suggest root bypass it's better.
MegaNZ Link for Root without unlocking the Bootloader, and without breaking the FP, also includes instructions for installing BlackMagic5G (explanation below), adding HD VOLTE, how to restore from a brick, and some other cool tricks: https://mega.nz/file/igphSCTD#OybJo9t1zwvJ0bdbAcN2BCqxWXAfHdhk3JFB4_5xkVc
I suggest you flash my BlackMagic5G and don't unlock your bootloader at all - just root. It's CN 2.52 ROM based. You'll get VOLTE, , GApps installed, Rooted with Magisk, TWRP, debloated, YouTube Vanced, AdAway, SmartPack Kernel Manager, etc. - looks like the Global / NA variant of the ROM. Almost perfect except still uses Messages and Phone from Nubia. Plus you will enable Face Unlock not available in the Global or NA versions of the ROM, and FP will still work! Click on the Google Search bar widget and the mic icon takes you to the Google Assistant, the left icon is Google Feed, type in the middle bar for a Google Search. Has 1Weather Free weather widget that looks great, and Google Calendar widget for your whole month of activities. Translate, Lens, Chrome, all the Google Apps are there. And the Chinese Nubia apps are nearly all GONE!
MegaNZ Link for BlackMagic5G Beta - IT'S ONLY THE DATA PARTITION + ROOTED KERNEL + NA SPLASH SCREEN, you NEED to 1) install the Red Magic 2.52 ROM below FIRST 2) Root using the first link posted above 3) Flash restore this from TWRP: https://mega.nz/file/r9hF2BwS#RrAXiFWSBNX8dLqfrH8nNHo_uigPC8uYXonwhALhGbo
MegaNZ Link for the Red Magic 5G CN 2.52 ROM: https://mega.nz/file/aoxBFAqY#EDt2OZBGTME4ZGKnERKpK_t-aJT_rWgD0aqBFkilRcY
*** NOW THE BOOTLOADER UNLOCK INSTRUCTIONS ***
Go to Settings / About phone / Build Number (NX659_J_ENCommon_V3.08 on North American Variant), click 7 times, Now you are a developer message appears, go back a menu to Settings / Other system settings / Developer options.
Enable:
OEM unlocking "Allow the bootloader to be unlocked"
USB debugging "Debug mode when USB is connected"
Install Minimal ADB and Fastboot (Windows 10 in this example): https://www.androidfilehost.com/?fid=746010030569952951
Default install path is:
C:\Program Files (x86)\Minimal ADB and Fastboot\
Go to the Search button on the bottom on Windows 10, type cmd, Command Prompt will appear in the menu. Right click it and Run as Administrator. All commands to be typed will be run in this Command Prompt window (referred to as terminal) unless otherwise stated to run on the phone.
Now Terminal window appears (it says Administrator: Command Prompt in the heading):
Text displayed is:
Microsoft Windows
(c) 2020 Microsoft Corporation. All rights reserved.
C:\WINDOWS\system32>
Typed in terminal:
cd "c:\Program Files (x86)\Minimal ADB and Fastboot"
I now connected the phone to a USB port on the PC.
On the phone, a Window appeared:
"Allow USB debugging?"
The computer's RSA key fingerprint is:
[36 digit code] Example:
C8:A17:E2:01:F6:A1
:368:10:E8:33:20:FB:
93:7D
Always allow from this computer (it's my computer so I clicked it since I trust the computer)
CANCEL / ALLOW (I clicked ALLOW)
Typed in terminal:
adb reboot bootloader
The phone reboots. Once the phone screen boots, in the center it says: Now you are in fastboot mode.
From the terminal I typed:
fastboot oem nubia_unlock NUBIA_NX659J
The terminal now displayed:
...
(bootloader) START update nubia fastboot unlock flag!!!
(bootloader) START set state to 1 ok!!!
In the terminal I typed:
fastboot flashing unlock *** DO NOT TYPE THIS IF YOU WANT TO KEEP A WORKING FP!!! READ TOP OF POST!!! AVOID THIS WITH THE EXPERIMENTAL METHOD OF ROOT WITH NO BL UNLOCK ***
Now a screen appeared on the phone with a big <!> red icon in the left corner. The rest in white text is a warning message. "By unlocking the bootloader, you will be able to install custom operating system on this phone. A custom OS is not subject to the same level of testing as the original OS, and can cause your phone and installed applications to stop working properly-
Software integrity cannot be guaranteed with a custom OS, so any data stored on the phone while the bootloader is unlocked may be at risk.
To prevent unauthorized access to your personal data, unlocking the bootloader will also delete all personal data on your phone.
Press the Volume keys to select whether to unlock the bootloader, then the Power Button to continue."
I selected UNLOCK BOOTLOADER and my device was completely erased. The factory OS loaded then. This process takes some time to complete.
Now the device rebooted with a warning message, and a big <!> yellow icon in the left corner.
"The boot loader is unlocked and software integrity cannot be guaranteed. Any data stored on the device may be available to attackers. Do not store any sensitive data on the device.
Visit this link on another device:
g.co/ABH"
Now the device reloads the firmware apparently and wipes all user data. Upon setting up the phone, the fingerprint display registration comes up and asked to place my finger on the back of the phone. There is no fingerprint sensor on the back of the Redmagic 5G! It is under the screen! So this step must be skipped. The ROM setup is corrupt or incomplete, a beta possibly. I setup the phone then went into Settings / Security to try to add a fingerprint. The button to add fingerprint then appears. Once I click the button, I get this error:
Loss of fingerprint calibration data
Loss of fingerprint calibration data was detected.
Currently unable to complete fingerprint entry,
please contact Nuia after-sales service via
4007006600
See the XDA post for recalibrating the FP: https://forum.xda-developers.com/nu.../guide-calibration-finger-print-loss-t4132961
ROOT FOR ALL DEVICES:
(These files are included in the tools download zip, Magisk 20.4 and MagiskManager-v7.5.1.apk, but this is the official source as updates post): Go to XDA and Download Magisk Manager and install the APK. Download the latest Magisk as well from the Manager. You can then reboot to Recovery (volume up + power, release the power button once the screen shows it loading, hold the volume up down until you see TWRP pop up). Flash Magisk from TWRP Install / Zip / sdcard / Magisk.zip reboot and you'll have root.
BL unlock first method was tested on North American variant and it works. But it breaks your FP sensor and gives you an annoying boot prompt.
If at any time you want to remove the OEM Bootloader unlock, you plug into the PC, go to the terminal for Minimal ADB and Fastboot, type:
adb reboot fastboot
fastboot oem nubia_unlock NUBIA_NX659J
fastboot flashing lock (screen will prompt to relock BL, choose to Relock)
The phone should reboot and install the original software. BUT...
If it says you are corrupted well, you have more issues.
You'll have to reflash the stock recovery.img, reboot to stock recovery, wipe data, wipe cache, and flash the CN update.zip rom to a flash drive FORMATTED TO FAT32 (annoying as hell) But you NEED a USB-C to OTG Adapter to attach a Flash Drive / SDCARD this way). If you don't have one, you better reflash TWRP using the prior instructions and flash the update.zip from there. Install, select the update.zip, flash. Wipe Data, Cache, ART/Dalvik. Reboot.
Now it should WIPE the entire phone and be back to normal Android 10 setup non rooted, no unlocked bootloader. Always beware of data loss doing root functions!!! Always be prepared to setup your phone entirely over again. Google Backup is very good to turn on before you do any of this stuff if you have already installed apps.
*** WARNING - THIS BYPASS METHOD COULD GO AWAY AT ANYTIME. IT SHOULD EVENTUALLY BE FIXED BY NUBIA ***
mslezak said:
{Mod edit}
***Bootloader Unlock Instructions for the Nubia Redmagic 5G + installing TWRP:***
Settings / About phone / Build # click 7 times, now your a dev message appears, good back a menu, go to Additional Settings / Developer Options
Enable:
ADB debugging, + OEM unlock
Connect phone to PC, approve device on phone RSA key for USB debugging
From Minimal ADB and Fastboot:
adb reboot bootlader
fastboot oem nubia_unlock NUBIA_NX659J
fastboot flashing unlock
(approve on phone with volume keys to unlock and hit the power button, now you'll get an annoyng mesage on boot as insecure unlocked BL) *ALL YOUR DATA WILL BE WIPED*
Next:
fastboot flash recovery recovery-TWRP-3.4.1B-0324-NUBIA_REDMAGIC_5G-CN-wzsx150.img
fastboot reboot recovery
Enter TWRP, set to not be removed by updates if prompted.
Boot up the device, setup as a new device. You're on stock ROM / kernel now unlocked.
Once you get up and running you'll want APK Mirror app to install stuff on the China Variant it's in the Nubia Playstore. Gboard download as well and set as default it's a lot easier than the Chinese keyboard that swaps between Chinese and English. Set size extra tall for this huge phone (I prefer anyhow). Chrome go download it from APK Mirror app as well. Then go to XDA and Download Magisk Manager and download it and install the APK. Download the latest Magisk as well from the Manager. You can then reboot to Recovery (volume up + power). Flash Magisk from TWRP reboot and you'll have root.
Note on my testing the fingerprint did not work after unlocking the bootloader. It says to contact Nubia support at some odd number. Hopefully they fix this.
Click to expand...
Click to collapse
You were able to actually install TWRP? Not just boot it? I thought A10 devices cant have twrp permanently installed?
That is a very good question my friend. I had to reflash it several times while rooting so it appears you are correct.
Now a window when I FIRST installed popped up and said make Recovery read only so a system update. can't overwrite it, to this I didn't even pay attention. So assuming that question does lock down recovery, it should stick.
mslezak said:
That is a very good question my friend. I had to reflash it several times while rooting so it appears you are correct.
Now a window when I FIRST installed popped up and said make Recovery read only so a system update. can't overwrite it, to this I didn't even pay attention. So assuming that question does lock down recovery, it should stick.
Click to expand...
Click to collapse
So its not permanent? Thats what I thought.
Well it could be permanent...
VZTech said:
So its not permanent? Thats what I thought.
Click to expand...
Click to collapse
What I was trying to say is that I've never had a phone where I had to select "prevent recovery from being overwritten" so I just clicked off the message. Had I selected "keep TWRP from being overwritten" then possibly it sticks. It's just a matter of making the recovery partition READ ONLY.
mslezak said:
What I was trying to say is that I've never had a phone where I had to select "prevent recovery from being overwritten" so I just clicked off the message. Had I selected "keep TWRP from being overwritten" then possibly it sticks. It's just a matter of making the recovery partition READ ONLY.
Click to expand...
Click to collapse
The issue with that could be any future updates though. Rm uses there own recovery for that. They don't provide fastboot images either I believe
Can anyone send me backup of the super partition?
I accidentally flashed an image to the super partition with twrp thinking it was the system partition (it technically is tho) and it bricked my phone and messed up twrp.
Only stock recovery works but the stock recovery cannot fix it by installing a full ota from a otg drive.
I do have a backup on my phone but it is inaccessable.
Could anyone please send me a backup of the super partition or have any idea on how to fix this?
(I tried to use edl and backup my data to recover my backup of the super partition but it seemed like it needed a programmer binary from qualcomm)
Future updates...
VZTech said:
The issue with that could be any future updates though. Rm uses there own recovery for that. They don't provide fastboot images either I believe
Click to expand...
Click to collapse
Yes what I've been told by prior Redmagic Users 3 and 3S is the ROM is released, as long as your boot.img is not patched with Magisk, it can be installed through the menus in Settings / About Phone / Update or someplace like that. You just download the ROM to the appropriate folder on the phone.
So far I have 1 link to a China ROM update here: https://ui.nubia.cn/rom/detail/65
Now on how to install the ROM, I use the Chrome browser set to autotranslate webpages. Most of the Chinese will be translated from here: https://bbs.nubia.com//thread-1136030-1-1.html
Basically it's going to wipe your device clean, and you can use a Nubia backup tool which will save all your items to a folder. Which then you should copy to your PC before installing the new ROM. Then it gives you instructions to get that data back onto your updated device.
apersomany said:
I accidentally flashed an image to the super partition with twrp thinking it was the system partition (it technically is tho) and it bricked my phone and messed up twrp.
Only stock recovery works but the stock recovery cannot fix it by installing a full ota from a otg drive.
I do have a backup on my phone but it is inaccessable.
Could anyone please send me a backup of the super partition or have any idea on how to fix this?
(I tried to use edl and backup my data to recover my backup of the super partition but it seemed like it needed a programmer binary from qualcomm)
Click to expand...
Click to collapse
Your probably screwed. I had this issue on a rm3s. You will need an unbrick tool. It was released for the rm3s about 4 mos after release. NUBIA should have true fastboot images available for download, but they dont.
VZTech said:
Your probably screwed. I had this issue on a rm3s. You will need an unbrick tool. It was released for the rm3s about 4 mos after release. NUBIA should have true fastboot images available for download, but they dont.
Click to expand...
Click to collapse
That's because of the super (dynamic) partition, see from the latest (and only) ROM:
Excerpt of the ROM installation script where it delineates the dynamic vs non dynamic partitions - you have product w/ a file transfer list, then vendor, system, and odm, The other files (boot.img, dtbo.img, splash.img, etc. and other various files) should be flashable with fastboot.
# Update dynamic partition metadata
assert(update_dynamic_partitions(package_extract_file("dynamic_partitions_op_list")));
unmap_partition("product");
block_image_update(map_partition("product"), package_extract_file("product.transfer.list"), "product.new.dat.br", "product.patch.dat");
unmap_partition("vendor");
block_image_update(map_partition("vendor"), package_extract_file("vendor.transfer.list"), "vendor.new.dat.br", "vendor.patch.dat");
unmap_partition("system");
block_image_update(map_partition("system"), package_extract_file("system.transfer.list"), "system.new.dat.br", "system.patch.dat");
unmap_partition("odm");
block_image_update(map_partition("odm"), package_extract_file("odm.transfer.list"), "odm.new.dat.br", "odm.patch.dat");
# --- End patching dynamic partitions ---
apersomany said:
I accidentally flashed an image to the super partition with twrp thinking it was the system partition (it technically is tho) and it bricked my phone and messed up twrp.
Only stock recovery works but the stock recovery cannot fix it by installing a full ota from a otg drive.
I do have a backup on my phone but it is inaccessable.
Could anyone please send me a backup of the super partition or have any idea on how to fix this?
(I tried to use edl and backup my data to recover my backup of the super partition but it seemed like it needed a programmer binary from qualcomm)
Click to expand...
Click to collapse
You should be able to flash the latest ROM via EDL mode if you've ever used EDL mode before, it usually requires shorting pins together in the device, although some recoveries will let you just boot into EDL mode if the phone still boots. It will be detected. Although on this device with the dynamic partition, I don't know how you would flash these in EDL mode... dynamic partitions - you have product w/ a file transfer list, then vendor, system, and odm that do not look like fastboot flashable parts. Possibly the unbrick tool for Redmagic 3/3S could be modified to do this for you.
mslezak said:
That's because of the super (dynamic) partition, see from the latest (and only) ROM:
Excerpt of the ROM installation script where it delineates the dynamic vs non dynamic partitions - you have product w/ a file transfer list, then vendor, system, and odm, The other files (boot.img, dtbo.img, splash.img, etc. and other various files) should be flashable with fastboot.
# Update dynamic partition metadata
assert(update_dynamic_partitions(package_extract_file("dynamic_partitions_op_list")));
unmap_partition("product");
block_image_update(map_partition("product"), package_extract_file("product.transfer.list"), "product.new.dat.br", "product.patch.dat");
unmap_partition("vendor");
block_image_update(map_partition("vendor"), package_extract_file("vendor.transfer.list"), "vendor.new.dat.br", "vendor.patch.dat");
unmap_partition("system");
block_image_update(map_partition("system"), package_extract_file("system.transfer.list"), "system.new.dat.br", "system.patch.dat");
unmap_partition("odm");
block_image_update(map_partition("odm"), package_extract_file("odm.transfer.list"), "odm.new.dat.br", "odm.patch.dat");
# --- End patching dynamic partitions ---
Click to expand...
Click to collapse
Yes those .img files can easily be fastboot flashed. Unfortunately it wont solve his problem. He needs the nubia unbrick tool, which is tough to get. I dont understand why Nubia makes things difficult. They should provide proper Fastboot files.
I already tried edl (not to flash, but to recover my backup of the super partition) but it seems like it needed a firehose binary. I still can use bootloader, fastbootd, recovery. It's just that the recovery fails at assert dynamic partition update thing with a error 7 (probably because my super partition turned into a normal partiton). I tried to flash a super empty image made with lpmake and try flashing the ota but that didn't work. I think if someone gives me a backup of the super partition I could flash that and that could work. I also had an idea of flashing a super partition of another devices factory image to make my super partition a dynamic partition, but I couldn't find any online.
apersomany said:
I already tried edl (not to flash, but to recover my backup of the super partition) but it seems like it needed a firehose binary. I still can use bootloader, fastbootd, recovery. It's just that the recovery fails at assert dynamic partition update thing with a error 7 (probably because my super partition turned into a normal partiton). I tried to flash a super empty image made with lpmake and try flashing the ota but that didn't work. I think if someone gives me a backup of the super partition I could flash that and that could work. I also had an idea of flashing a super partition of another devices factory image to make my super partition a dynamic partition, but I couldn't find any online.
Click to expand...
Click to collapse
I get a Global Device on Monday. I'll try to use Qualcomm tools to make a brick restore image of Global. If I get one made I'll post all the tools to restore the device on Mega.nz. Because of the super partition it has to be done this way. Not via TWRP as you know. I'm working on Dev tools for this device as fast as possible.
mslezak said:
I get a Global Device on Monday. I'll try to use Qualcomm tools to make a brick restore image of Global. If I get one made I'll post all the tools to restore the device on Mega.nz. Because of the super partition it has to be done this way. Not via TWRP as you know. I'm working on Dev tools for this device as fast as possible.
Click to expand...
Click to collapse
Thank you so much!
Okay I can't add anything special but daaamn this community is amazing. So much help I love you all
To relock BL repeat the instructions with 1 different command
Just replace
fastboot flashing unlock
with
fastboot flashing lock
Again you approve to lock on the phone prompt with the volume keys and your phone will be wiped and all will be back to normal, you'll be locked. And back to phone setup.
I'd edit the original post but the moderators took away my rights!!! Because I posted a Telegram link WHY - how do you expect development to get better???
BTW anyone with a NEW phone arriving that can record the FP failures and all errors please contact me so I can send to Nubia. They are waiting for me to reproduce the error but I already setup my new phone... Thinking I wouldn't be the ONLY ONE to contact [email protected] ... Guys you want developer support on this phone or not. Contribute please.
mslezak said:
{Mod edit}
***Bootloader Unlock Instructions for the Nubia Redmagic 5G + installing TWRP:***
Settings / About phone / Build # click 7 times, now your a dev message appears, good back a menu, go to Additional Settings / Developer Options
Enable:
ADB debugging, + OEM unlock
Connect phone to PC, approve device on phone RSA key for USB debugging
From Minimal ADB and Fastboot:
adb reboot bootlader
fastboot oem nubia_unlock NUBIA_NX659J
fastboot flashing unlock
(approve on phone with volume keys to unlock and hit the power button, now you'll get an annoyng mesage on boot as insecure unlocked BL) *ALL YOUR DATA WILL BE WIPED*
Next:
fastboot flash recovery recovery-TWRP-3.4.1B-0324-NUBIA_REDMAGIC_5G-CN-wzsx150.img
fastboot reboot recovery
Enter TWRP, set to not be removed by updates if prompted.
Boot up the device, setup as a new device. You're on stock ROM / kernel now unlocked.
Once you get up and running you'll want APK Mirror app to install stuff on the China Variant it's in the Nubia Playstore. Gboard download as well and set as default it's a lot easier than the Chinese keyboard that swaps between Chinese and English. Set size extra tall for this huge phone (I prefer anyhow). Chrome go download it from APK Mirror app as well. Then go to XDA and Download Magisk Manager and download it and install the APK. Download the latest Magisk as well from the Manager. You can then reboot to Recovery (volume up + power). Flash Magisk from TWRP reboot and you'll have root.
Note on my testing the fingerprint did not work after unlocking the bootloader. It says to contact Nubia support at some odd number. Hopefully they fix this.
Click to expand...
Click to collapse
Just in case if somebody need a Chinese version of official ROM v2.46 for RedMagic 5G.
Code:
https://mega.nz/file/vc0DiabR#npahTop-JXZ9Mwv-lA7G6DxTG2qqOOAf6AwW8NdEEKw
mslezak said:
Just replace
fastboot flashing unlock
with
fastboot flashing lock
Again you approve to lock on the phone prompt with the volume keys and your phone will be wiped and all will be back to normal, you'll be locked. And back to phone setup.
I'd edit the original post but the moderators took away my rights!!! Because I posted a Telegram link WHY - how do you expect development to get better???
BTW anyone with a NEW phone arriving that can record the FP failures and all errors please contact me so I can send to Nubia. They are waiting for me to reproduce the error but I already setup my new phone... Thinking I wouldn't be the ONLY ONE to contact [email protected] ... Guys you want developer support on this phone or not. Contribute please.
Click to expand...
Click to collapse
we found out that using the cn rom it all works without even unlocking the bootloader, even while oem unlock was disabled in dev options but there is some kind of vbmeta img required. a full guide is incoming.
VZTech said:
The issue with that could be any future updates though. Rm uses there own recovery for that. They don't provide fastboot images either I believe
Click to expand...
Click to collapse
You can flash their NX659J-update.zip files directly from TWRP that's how we restored our bricked devices already. So OTA updates no, but you can download them anyway and flash from TWRP directly. Yes we have to figure out a concrete restore method which isn't 100% working yet. I.e. all your data is lost this way apparently AT THIS MOMENT... MORE TO COME.