I don't have anything against toolkits, I just prefer to use adb and fastboot so I have more control over of what's going on. I also think it's a good idea for folks to have a little idea about what they're doing, even if they aren't experts. Below are the steps I used to install TWRP (recovery) and SuperSU (root) for my X522 (aka S3, the US variant which uses the Snapdragon 652). I don't see any reason this wouldn't work for all other Snapdragon variants: X520 (Chinese), X526 (Indian), and X527 (International). That said, you do what you do at your own risk. If you have one of the other Snapdragon variants and this works for you, though, please respond to the thread and let me know!
This thread is intended to be noob-friendly! That means that there are no dumb questions...unless you ask a question that is directly answered in the first post or in the FAQs found in the second post. To that extent, please read and re-read and if you still can't find your answer, please feel free to post your question.
Many thanks to @Rishabh Rao and his team for getting us an official TWRP image.
WARNING: this will reset your phone entirely! Make sure you save anything you want from internal storage before proceeding any further!
WARNING: as of right now, unlocking / rooting your phone will break your ability to take official OTAs. We're not sure why. That said, you should be able to flash modified OTA zip files manually, after a certain block of the update script is removed (see second post for more information).
Unlocking and Rooting your Le 2
Download and install Minimal ADB and Fastboot: http://forum.xda-developers.com/showthread.php?t=2317790
Download latest official TWRP, place file in ADB installation folder, and rename to "twrp.img": https://twrp.me/devices/leecole2.html
Download SuperSU 2.78 (stable): https://download.chainfire.eu/1001/
Boot up phone and plug into computer
Settings > scroll to bottom to "About phone" > touch "Build" 7 times to enable developer options
Developer options > toggle "OEM unlocking" and "USB debugging" so that they're both enabled
When "Allow USB debugging?" window pops up on phone, check "Always allow..." box and hit OK
In Minimal ADB installation folder, hold Shift and right-click "Open command window here", then type:
Code:
adb reboot bootloader
Once in fastboot:
Code:
fastboot oem unlock-go
fastboot boot twrp.img
If password screen comes up, tap "Cancel" button
If it asks, tap "Keep Read Only" button (probably doesn't matter, but whatever)
Wipe > Format Data
Make backups (I suggest boot, recovery, and system since this will allow you to return everything to stock later on)
Mount > Enable MTP
Copy entire TWRP folder from internal storage to your computer
Copy SuperSU zip from your computer to root of internal storage
Reboot > Bootloader
Code:
fastboot oem unlock-go
fastboot flash recovery twrp.img
Hold Vol+ and Pwr until boots into TWRP
Swipe to Allow Modifications
Install > select SuperSU zip > swipe to flash
Wipe Cache/Dalvik
Reboot (first boot will take a little while, so be patient)
Enjoy your rooted phone!
Restoring to Stock(ish)
Follow steps 4-7 above
If your boot and recovery backups from TWRP aren't already on your phone, move them to the appropriate folder (internal storage/TWRP/BACKUPS/[yourphoneserialnumber])
In Minimal ADB installation folder, hold Shift and right-click "Open command window here", then type:
Code:
adb reboot recovery
Wipe > check Dalvik, Cache, Data
Restore > select your package, ensure boot and recovery are checked, then Swipe to Restore
Reboot > Recovery
In stock recovery: uncheck "Update system", check "Clear data", and tap "Start"
Reboot to bootloader (hold Vol- and Pwr until it comes up) and then:
Code:
fastboot oem unlock-go
fastboot boot twrp.img
Wipe > Format Data
Reboot > System
Your phone is now back to stock!
If you didn't back up your stock recovery, boot, or system, you can find the ones I pulled from my phone at the link below. They're from 19S. I don't know if that makes a difference (vs 18S) with boot and recovery or not, but obviously that's what you're getting with the system.
https://mega.nz/#F!bV0XUbhJ!k2ZfY5t9bxb8gRa3rKQbyA
FAQs
Fastboot and/or ADB doesn't see my phone!
If you've enabled OEM unlocking and USB debugging and fastboot devices returns <waiting for device> or adb devices doesn't show anything, the most likely culprit is that Windows is using updated ADB drivers and you need to roll back. You can do this via Device Manager > right-click Android Device (or Kedacom USB device) / Android Bootloader Interface > Update driver > Browse my computer for driver software > Let me pick... > Choose older version (probably something from 2014)
I haven't seen the "Allow USB debugging?" prompt. Where is it?
In some cases, you will need to run an ADB command first to make the prompt show up. If you toggled the appropriate developer options and didn't get the popup immediately, make sure your phone is plugged into your computer and type adb devices in the command prompt. You should get the popup box then.
Stock recovery is in Chinese and I can't read Chinese!
As I was testing the above procedures, this happened to me once or twice and I don't know why. Upon a full restore and boot back into recovery, it was in English again. It might have something to do with the data wipe in TWRP. Anyway, the options in stock recovery are the same in Chinese and English so do this:
Uncheck the first item and check the second
It will direct you to a screen with some red text and a blue button: tap the button
It will return you to the first page: ensure the second item is checked and tap the blue button
Uh, how do I re-lock the bootloader? Am I missing something?
As far as I can tell - and someone please correct me if I'm wrong - using this guide, your bootloader is only ever temporarily unlocked and will re-lock with a reboot. That's why you have to use fastboot oem unlock-go more than once. You can verify this by restarting the phone, rebooting into the bootloader, and using the code below to check the status:
Code:
fastboot oem device-info
If for some reason your phone shows that you still have an unlocked bootloader, you can re-lock it using:
Code:
fastboot oem lock-go
I'm stuck in a stock recovery bootloop. How do I get out of it?
This probably happened because you're just holding down the power button to reboot instead of using the "restart" button in stock recovery. If you use the "restart" button to in stock recovery, it should kick you out of the loop.
Thanks for this guide , can we expect some roms from your side.
Just curious to know if any developer is working for rom on le2
Great guide for beginners but can you tell that how can one lock the bootloader again and when we make a backup does it make the back up of TWRP recovery of stock recovery?
Great!! Informative thread for beginners!
Miketoulson said:
Just curious to know if any developer is working for rom on le2
Click to expand...
Click to collapse
Yes. @Rishabh Rao and his team (the same ones who did TWRP and the AIO toolkit) are working on CM. As a reminder, please do not ask for ETAs. They will post the ROM when it's available.
Swastik Raj Chauhan said:
Great guide for beginners but can you tell that how can one lock the bootloader again and when we make a backup does it make the back up of TWRP recovery of stock recovery?
Click to expand...
Click to collapse
1.) Regarding the bootloader: good question. I've updated the FAQ.
2.) Regarding recovery backup: that's why we only boot into TWRP the first time, rather than replacing recovery from the beginning. That way, stock boot and recovery are backed up. Later on, when we flash TWRP, stock recovery is replaced.
I'm having trouble with this guide. I have TWRP recover flashed, but it isn't working correctly. It says there is nothing in my sdcard directory and my computer won't connect to the phone in recovery. I've also tried "adb push ... /sdcard/" method. The SuperSU files gets put in the sdcard directory and I can flash it, but it says "unable to mount storage" and the file is gone after a reboot. Is this because it's encrypted and I'm just hitting cancel when it asks for a password?
abel408 said:
I'm having trouble with this guide. I have TWRP recover flashed, but it isn't working correctly. It says there is nothing in my sdcard directory and my computer won't connect to the phone in recovery. Is this because it's encrypted and I'm just hitting cancel when it asks for a password?
Click to expand...
Click to collapse
Sounds like you missed steps 12 and 14.
rczrider said:
Sounds like you missed steps 12 and 14.
Click to expand...
Click to collapse
Nope... I formatted data and enabled MTD. When I enable MTD, my computer tells my the phone is locked...
---------- Post added at 07:19 PM ---------- Previous post was at 07:14 PM ----------
My bootloader keeps locking itself...
(bootloader) Device product name: []
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
I can unlock it, but it locks itself after a reboot.
abel408 said:
Nope... I formatted data and enabled MTD. When I enable MTD, my computer tells my the phone is locked...
---------- Post added at 07:19 PM ---------- Previous post was at 07:14 PM ----------
My bootloader keeps locking itself...
(bootloader) Device product name: []
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
I can unlock it, but it locks itself after a reboot.
Click to expand...
Click to collapse
That's expected and is addressed in the FAQ
You're only ever temporarily unlocking it. You will need to unlock it every time you reboot the phone.
rczrider said:
That's expected and is addressed in the FAQ
You're only ever temporarily unlocking it. You will need to unlock it every time you reboot the phone.
Click to expand...
Click to collapse
oh wow... so there is no perm unlock with this phone yet? Does the Chinese version have perm unlock? We can flash the chinese bootloader for perm unlock if that's the case.
---------- Post added at 07:45 PM ---------- Previous post was at 07:27 PM ----------
And now I'm stuck... I cannot go back to stock because TWRP doesn't mount the storage.
---------- Post added at 08:01 PM ---------- Previous post was at 07:45 PM ----------
abel408 said:
oh wow... so there is no perm unlock with this phone yet? Does the Chinese version have perm unlock? We can flash the chinese bootloader for perm unlock if that's the case.
---------- Post added at 07:45 PM ---------- Previous post was at 07:27 PM ----------
And now I'm stuck... I cannot go back to stock because TWRP doesn't mount the storage.
Click to expand...
Click to collapse
I was able to fix this by wiping Internal Storage... You may need to add that to your guide. Thanks for the guide!
abel408 said:
oh wow... so there is no perm unlock with this phone yet? Does the Chinese version have perm unlock? We can flash the chinese bootloader for perm unlock if that's the case.
Click to expand...
Click to collapse
I can't get permanent root using the AIO Toolkit, but maybe it's just the 2 phones I've tried. I'd love to hear from other users (X522 or other variants) on whether or not their unlock actually sticks after a reboot.
abel408 said:
I was able to fix this by wiping Internal Storage... You may need to add that to your guide. Thanks for the guide!
Click to expand...
Click to collapse
If other folks run into the same issue, I'll add it. I followed my own steps on a second phone (one that had never been unlocked/rooted before and was currently set up and in use) after your post and I didn't have any need to do anything different. I'm wondering if that need arose because you didn't unlock the bootloader a second time before booting into TWRP. If that's the case, the guide works as written, so I'll add it to the FAQ.
I seem to have done something wrong. I'm having a really difficult time accessing the Data partition in TWRP. Every time I reboot into recovery I cannot access the files on the sdcard (it is simply empty). I reboot and the files are still in storage (along with the TWRP backups I made) - I just can't seem to get to them in TWRP. I cannot mount Data because it doesn't appear. There is a box to decrypt data but that then requires a password (which I obviously don't know). Don't want to go any further if I can't seem to have a dependable way to access backups. Any suggestions?
Edit: Enable MTP also doesn't work for me in TWRP so there is no way to bring any files over from my PC while in TWRP - also adb push/pull doesn't seem to be working
skyman88882002 said:
I seem to have done something wrong. I'm having a really difficult time accessing the Data partition in TWRP. Every time I reboot into recovery I cannot access the files on the sdcard (it is simply empty). I reboot and the files are still in storage (along with the TWRP backups I made) - I just can't seem to get to them in TWRP. I cannot mount Data because it doesn't appear. There is a box to decrypt data but that then requires a password (which I obviously don't know). Don't want to go any further if I can't seem to have a dependable way to access backups. Any suggestions?
Edit: Enable MTP also doesn't work for me in TWRP so there is no way to bring any files over from my PC while in TWRP - also adb push/pull doesn't seem to be working
Click to expand...
Click to collapse
If TWRP is asking for a password, that means you missed step 12.
I'm trying to upgrade from 18s to 19s and I'm getting upgrade failed every time. I've tried restoring to factory defaults and restoring my TWRP backup. Seems to be fully on stock now and it still fails. My question is, do you think it would be alright if I restored your 19s TWRP backup so that I am on 19s?
abel408 said:
I'm trying to upgrade from 18s to 19s and I'm getting upgrade failed every time. I've tried restoring to factory defaults and restoring my TWRP backup. Seems to be fully on stock now and it still fails. My question is, do you think it would be alright if I restored your 19s TWRP backup so that I am on 19s?
Click to expand...
Click to collapse
Tell you what: give me an hour or two. I'm currently on non-stock (ie. rooted) 18S and since the Xposed module EUI Moder (http://forum.xda-developers.com/xposed/modules/mod-leeco-eui-moder-t3416932) doesn't work (lockscreen flicker / system UI crash), I don't mind wiping the phone and testing the ability to go back to stock and do an OTA update to 19S. If it doesn't work for me, I'll restore 19S (from my other S3) via TWRP and see if that does it.
@abel408
My first try was to just grab the OTA file (which I did) and do a local update, but no dice. In case anyone cares, I've uploaded the OTA zip file (IFXNAOP5801910272S).
So I went ahead and used both 19S TWRP backups (one for boot/recovery and one for system only) downloadable from Mega via the link in the OP and it worked just fine. Those files were generated from a different phone and worked fine on this one, so you should be good to go.
rczrider said:
@abel408
My first try was to just grab the OTA file (which I did) and do a local update, but no dice. In case anyone cares, I've uploaded the OTA zip file (IFXNAOP5801910272S).
So I went ahead and used both 19S TWRP backups (one for boot/recovery and one for system only) downloadable from Mega via the link in the OP and it worked just fine. Those files were generated from a different phone and worked fine on this one, so you should be good to go.
Click to expand...
Click to collapse
Thanks buddy!
Thank you sir, this worked (almost) perfectly. For some reason on my laptop, I wasn't able to get the phone to connect with debugging (never got the prompt for permission, etc.). No clue why not, I've got drivers and everything, and that laptop works with many other phones. Oh well. Went to a different PC and it worked perfectly.
rczrider said:
@abel408
My first try was to just grab the OTA file (which I did) and do a local update, but no dice. In case anyone cares, I've uploaded the OTA zip file (IFXNAOP5801910272S).
So I went ahead and used both 19S TWRP backups (one for boot/recovery and one for system only) downloadable from Mega via the link in the OP and it worked just fine. Those files were generated from a different phone and worked fine on this one, so you should be good to go.
Click to expand...
Click to collapse
I think I'm doing something wrong @rczrider, but I can't get TWRP to even recognize the backup you uploaded. Do I just drag the extracted files to the TWRP folder?
Related
It seems that unlocking the BootLoader on the WileyFox Swift2+ is even easier.
To unlock the boot loader (WARNING!!! This wipes your user data!!!)
Go To 'Settings - About Phone' Tap 'Build Number' seven times to enable 'Developer Options'.
Go To 'Developer Options' Enable 'Advanced Reboot', Enable 'OEM Unlocking'
...## not sure if these next few steps are even needed!!
Connect to computer running "Minimal ADB and Fastboot"
Open command window as administrator (To prevent Win10 messing around).
Enter command "fastboot oem unlock"
...##
Press the phone 'Power Off - Reboot - FastBoot'
PC detects device and states "Follow instructions on device screen"
Phone screen issues dire warnings about unlocking Bootloader.
Proceed and job done Bootloader is Unlocked (device at this point not rooted).
The stock Swift2+ Cyanogen Rom is no longer available - seek out the LineageOS rom instead
I unlocked my bootloader the other day and those are the same steps I did so I can confirm this works.
I then proceeded to root the phone with SuperSU 2.78. Worked a treat.
Swift 2 Plus and SuperSU
FelixPiers said:
I unlocked my bootloader the other day and those are the same steps I did so I can confirm this works.
I then proceeded to root the phone with SuperSU 2.78. Worked a treat.
Click to expand...
Click to collapse
Yes initially the only version of SuperSU I could find was v2.46, which kept failing.
Any help? My reboot menu doesn't have a fastboot option. Yes I have advanced reboot and oem unlocking enabled.
Edit: Sorted it. Turns out you have to reboot into the bootloader.
thejackle123 said:
Any help? My reboot menu doesn't have a fastboot option. Yes I have advanced reboot and oem unlocking enabled.
Edit: Sorted it. Turns out you have to reboot into the bootloader.
Click to expand...
Click to collapse
Is it too hard to google your question?
Works on most devices:
1) Turn off device
2) Hold VOLUME UP button
3) Connect device to PC via usb-cable
I installed SuperSU, before that I installed TWRP. Now I am unable to install the latest update "cm-marmite-a1478a0ee9-to-7aa1c797975e-signed"
When I download this update and perform the actual install, it gives an error. Restarting the phone via TWRP recovery gives the same error. I am getting "Error 7"
So no I want to revert back, to get rid off SuperSU and TWRP to install all updates and then later root the device with TWRP and SuperSU. How do I get the original state of the phone back?
Or do you have any advice how to get the latest update installed?
Thx.
SMessy said:
It seems that unlocking the BootLoader on the WileyFox Swift2+ is even easier.
To unlock the boot loader (WARNING!!! This wipes your user data!!!)
Go To 'Settings - About Phone' Tap 'Build Number' seven times to enable 'Developer Options'.
Go To 'Developer Options' Enable 'Advanced Reboot', Enable 'OEM Unlocking'
...## not sure if these next few steps are even needed!!
Connect to computer running "Minimal ADB and Fastboot"
Open command window as administrator (To prevent Win10 messing around).
Enter command "fastboot oem unlock"
...##
Press the phone 'Power Off - Reboot - FastBoot'
PC detects device and states "Follow instructions on device screen"
Phone screen issues dire warnings about unlocking Bootloader.
Proceed and job done Bootloader is Unlocked (device at this point not rooted).
The stock Swift2+ Cyanogen Rom is here
http://builds.cyngn.com/factory/marmite/cm-13.1.4-ZNH2KAS5RM-marmite-signed-fastboot-c64f8f5d87.zip
Click to expand...
Click to collapse
Hi, mate
unfortunately teh link to the stock rom is not working.
Can u provide me with another working link?
I deleted my rom and i can't find the stock to reanimate my phone.....
EDIT!!!!
All done, device is restored
THy @ll
Rom location
RayfG said:
Hi, mate
unfortunately teh link to the stock rom is not working.
Can u provide me with another working link?
I deleted my rom and i can't find the stock to reanimate my phone.....
EDIT!!!!
All done, device is restored
THy @ll
Click to expand...
Click to collapse
Just to confirm the stock room is still at this location as at 2nd march 2017
http://builds.cyngn.com/factory/marmite/cm-13.1.4-ZNH2KAS5RM-marmite-signed-fastboot-c64f8f5d87.zip
"Just to confirm the stock ROM is still at this location as at 2nd march 2017 :"
Link above does not work now, however below one does.
https://androidfilehost.com/?w=files&flid=126553
Hmmm. I'm going to try again. Before I got fastboot in red and Dvice Status: Locked. But I'll try again, see where I get.
Image of issue: https://ibb.co/jfLPye
edit: Updating to the latest Oreo update (8.1 I think)
---------- Post added at 08:34 AM ---------- Previous post was at 08:14 AM ----------
ohhhhhhh, I had to turn the phone off while connected, already running "adb & fastboot" (not just adb) then (phone connected in USB debugging mode) turn off the phone and hold volume up (no need to hole the power key as connected and I got the option to unlock with a warning that I may void the warranty. Then my phone encrypted/re-encrypted itself (I think it was already encrypted).
Now to flash TWRP (3.2 I think) and flash a custom ROM (Lineage 15.1 / 8.1 Oreo) Not sure if I should root or not. And if I do, should I root before installing 8.1?
got damit i never understand how to flash twrp i followed what google said.
fastboot flash recovery XXX.img it does its thing i reboot still no recovery im on stock cm12 ? i think or cm13 android 6.0)
Hi, trying to unlock my S2+ bootloader with Ubuntu MATE. Have completed all the steps listed, entered fastboot oem unlock into the terminal which now just sits there displaying < waiting for any device >
Any idea where I go from here?
bl91 said:
Hi, trying to unlock my S2+ bootloader with Ubuntu MATE. Have completed all the steps listed, entered fastboot oem unlock into the terminal which now just sits there displaying < waiting for any device >
Any idea where I go from here?
Click to expand...
Click to collapse
your device isn't picked up by fastboot ...first of all install the very latest version of adb ...using the usual Ubuntu story
sudo apt-get install adb
sudo apt-get upgrade
sudo apt-get update
sudo reboot
then switch on your device
go to /settings/about/buildnumber
click until developer settings are enabled
go to developer settings
toggle oem unlock to on
toggle adb to on
WITHOUT SWITCHING OFF
connect device to pc/laptop with original orange wileyfox cable
now your Ubuntu machine
must install drivers and Mount the phone so it should appear as a mounted volume on desktop
now open a terminal
now run the following :
sudo adb
sudo adb devices
now look on your phone and pull down the notification shadse ..make sure you have adb connected and file transfer mode ..if not change from charge to file transfer ...
there should be a pop up window on phone screen asking for permission for adb ..select allways allow and give pernission / authorization ..
now in terminal run adb devices and it should return some value as connected device
run:
adb reboot bootloader
phone will reboot to bootloader
run:
fastboot oem unlock
*use volume up to select yes
**beware will erase DATA ...
***if it doesn't work and adb and fastboot doesn't detect your device it is a driver problem but i haven't used Ubuntu in ages so can't remember steps to update your drivers other than updating the whole adb package
****some ubuntu instructions might be a little off as I've explained previously it's been a while
*****your waiting for device means
-adb service didn't start
+try "sudo adb"
-adb drivers out of date
+try sudo apt-get update
-adb on device not toggled to on
+toggle adb in dev settings
*adb authorization not given **should still see unauthorized device
-bad usb cable
+try another usb cable
-bad usb port
+try a different usb port
_____for clarity double check Ubuntu adb instructions and commands but this should put you on the right track____
---------- Post added at 08:30 AM ---------- Previous post was at 08:19 AM ----------
reggiexp said:
got damit i never understand how to flash twrp i followed what google said.
fastboot flash recovery XXX.img it does its thing i reboot still no recovery im on stock cm12 ? i think or cm13 android 6.0)
Click to expand...
Click to collapse
don't reboot immediately ..stock recovery will be flashed back over twrp
*i assume you know how to get to fastboot
adb reboot bootloader
fastboot oem unlock
*volume up for yes
fastboot flash recovery recovery.img
*make sure you have a copy of twrp called recovery.img in adb folder
when it says sending...
then is says writing ...
then it says done
DON'T REBOOT
UNPLUG USB
***MANUALLY BOOT TO BOOTLOADER USING VOLUME UP AND POWER
**** IN BOOTLOADER SELECT "RECOVERY"
you should then just wait on wileyfox first time it takes a minute or two don't know why then
it should boot to twrp
***you can take stock boot.img and patch it with magisk
-use: fastboot flash boot boot.img
-then you will have magisk and rooted
-using twrp apk or something like root rasher or flasher ..give apk root permission
-download twrp ..flash with apk from inside system ..after flashing select yes to reboot directly to recovery
Thanks very much, I've unlocked my bootloader now! Onto the TWRP, Magisk and LineageOS business now
bl91 said:
Thanks very much, I've unlocked my bootloader now! Onto the TWRP, Magisk and LineageOS business now
Click to expand...
Click to collapse
okay no problem
*i know everybody likes lineage and its usually more stable and the base for many custom roms
however just my 2cents worth ...i tried all the roms for our device ..but the by far the best for me was following the tutorial on how to make our device treble compatible ..
Then ...after 3-4 months of trying different treble GSI's i have stopped on Viper Official Pie 64bit A-only treble system.img ... at least give it a try after trying out lineageOs ..
you might thank me .
I can't get my device to show up usb debugging is on, Advanced Reboot', 'OEM Unlocking' etc. I've been trying for hours and hours. It shows up to transfer files if I want that mode so my PC is recognising it, but it doesn't seem to have drivers for adb. I've tried installing google usb drivers and also this: https://afterthoughtsoftware.com/posts/using-adb-with-wileyfox-swift
sorry if I haven't explained clearly, I'm just so sleepy from going around in circles. :|
I've rooted phones before and never had this issue. please can anybody help?
edit: have fixed I think! did two things at once so not sure which. I revoked usb devices so that my computer would have to ask permission again to connect (or something like this) and also clicked a thing on my PC to allow it to update what I think said driver icons automatically, which I wouldn't have thought would help, but it seemed to find the adb driver this time. I'd probably make more sense if it weren't 1am. :|
When i got my Swift 2 X, it came updated with 8.1 Oreo out of the box and the issue I had was unlocking the bootloader.
Sure fastboot oem unlock unlocked so I could flash recovery and roms but whenever I tried flashing a bootloader via fastboot, it gave me "FAILED (remote: Critical partition flashing is not allowed)". So that part was still locked.
This I fixed way back after searching around on my own about it but since the solution to this aint mentioned around here and I can't be the only one who have encountered this I think, I am just gonna add it in here.
There are now other commands to unlock your device, fastboot flashing unlock that does the exact same thing that fastboot oem unlock does and fastboot flashing unlock_critical is the command that unlocks the bootloader.
Both commands prompts you with the usual to confirm unlock and wipes your data.
It doesn't matter if you already unlocked the device with the oem command or flashing command, fastboot flashing unlock_critical should be able to unlock the bootloader either way.
My swift was also at 8.1 I had no problem unlocking the bootloader.
DH
RavZ75 said:
When i got my Swift 2 X, it came updated with 8.1 Oreo out of the box and the issue I had was unlocking the bootloader.
Sure fastboot oem unlock unlocked so I could flash recovery and roms but whenever I tried flashing a bootloader via fastboot, it gave me "FAILED (remote: Critical partition flashing is not allowed)". So that part was still locked.
This I fixed way back after searching around on my own about it but since the solution to this aint mentioned around here and I can't be the only one who have encountered this I think, I am just gonna add it in here.
There are now other commands to unlock your device, fastboot flashing unlock that does the exact same thing that fastboot oem unlock does and fastboot flashing unlock_critical is the command that unlocks the bootloader.
Both commands prompts you with the usual to confirm unlock and wipes your data.
It doesn't matter if you already unlocked the device with the oem command or flashing command, fastboot flashing unlock_critical should be able to unlock the bootloader either way.
Click to expand...
Click to collapse
bubba_66 said:
My swift was also at 8.1 I had no problem unlocking the bootloader.
DH
Click to expand...
Click to collapse
Doesn't seem that many who have this lock on their bootloaders, the only ones I could find here who had locked bootloaders the same way as I had are in the LineageOS 14.1 thread.
So at least I am not alone with that but sure makes me wonder how it is so for some while others not.
After unlock bootloader Everytime reboot always like this https://ibb.co/NSZR818
This guide is supposed to help you root your lg k8 (2016) or k10 (2016) device (i guess any models with and unlockable bootloader and working TWRP).
Not for the 2017 models!
Why "friendly" root? Go see my old guide how unfriendly the method used to be:
https://forum.xda-developers.com/lg-k10/how-to/twrp-root-lg-k8-k350n-t3475807
Guys with latest (2017 febr. 1) security patch read this before you proceed:
https://forum.xda-developers.com/showpost.php?p=71469157&postcount=183
https://forum.xda-developers.com/showpost.php?p=72414225&postcount=250
Short version:
1. unlock bootloader (read step 2.1 if there is no device corrupt message during every boot up after unlocking bootloader!!!)
2. boot into TWRP (i tested with 3.0.0 twrp and above, never tested below)
3.1 install rce_univ.zip (download from this thread: https://forum.xda-developers.com/apps/supersu/ramdisk-compression-exchanger-t3533327, but follow instructions here!)
3.2 install supersu
3.3 install rce_univ.zip again
reboot
Long version:
The links written with italic fonts are video guides (please excuse me for the quality they were made by my mobile phone)
1. unlock bootloader
- in settings/about phone/software info tap on build number about 10 times so you unlcok developer options
- in settings/developer options tick on "oem unlock" and "usb debugging" and untick "verify apps over usb"
- in settings/security tick on "unknown sources" and untick "verify apps"
video guide for above steps: Link Removed by Moderator
- make sure you installed all the drivers for your mobile from lg's site (LGMobileDriver_WHQL_Ver_4.1.1.exe and also lg bridge) - Link Removed by Moderator
- set up adb/fasboot using 15 seconds adb installer: https://forum.xda-developers.com/showthread.php?t=2588979 - Link Removed by Moderator
- go to the folder it's installed (in my case it's C:/adb - adb.exe and fastboot.exe supposed to be there) hold shift and right click "open cmd here" - Link Removed by Moderator
- in the command window type "adb devices"
it will start adb services and will print a line like "...lgk350... or ...lgk420... lgk430, etc"
if you can't find your device there check device manager or google how to work things out
normally in device manager you should find "LGE Mobile USB Serial Port" under Ports - Link Removed by Moderator
- now reboot to fastboot mode typing the command: "adb reboot bootloader"
your phone should go blank and only print fastboot mode on the bottom of the screen
- check your fastboot connection: type: "fastboot devices"
same as before (in my case it was writing some unrecognizable letters - probably wrong coding) if you see nothing then check device manager -Link Removed by Moderator
you may try to install android SDK (command line tool is enough - https://developer.android.com/studio/index.html - bottom of the page Link Removed by Moderator) if the connection is not working - however there must be a way to make it work (i had a hard time in device manager - i changed each driver a million times until it worked)
in device manager you should find "android bootloader interface" in my case its under "samsung android phone" i don't know why but it works
- In case you have a working adb and fastboot connection type (if you lost connection you have to get to fastboot again: "adb reboot bootloader"):
"fastboot oem unlock" - the phone will ask you if you really mean it, using the volume and the on/off buttons (twice) you can accept
you will lose all your data!!! and most likely lose warranty as well!!! Link Removed by Moderator
however your phone shell restart just fine (you have to manually restart it by taking out the battery or boot into twrp and reboot from there. There should be some message during boot up that your system is vulnerable from now on.
- after reboot you may want to check if your bootloader is really unlocked: get back to fastboot and type "fastboot getvar all" and find the line which sais if your bootloader is unlocked (if it's not you may repeat the process)Link Removed by Moderator
set up developer settings again:
- in settings/about phone/software info tap on build number about 10 times so you unlcok developer options
- in settings/developer options tick on "oem unlock" and "usb debugging" and untick "verify apps over usb"
- in settings/security tick on "unknown sources" and untick "verify apps"
Link Removed by Moderator
- !!!if there is no device corrupt message during every boot up then you need an additional step i'll describe at step 2.1!!! - Link Removed by Moderator
2. find a working TWRP for your device (i collect them in the first comment below - https://forum.xda-developers.com/showpost.php?p=70375626&postcount=2):
- put the recovery image (e.g "k8twrp.img") into your ADB folder (like c:\adb - where you opened command promt earlier)
- Get back to fastboot again and boot to TWRP - type in cmd: "fastboot boot k8twrp.img" (or whatever your TWRP image's filename is)
- if its not booting into TWRP normally try another TWRP (comment #2)
- on the first screen of the TWRP it's asking for password to decrypt data - just hit cancel
- if you have the device corrupt message during every boot up you can skip the next step (go straight to step 3.)
2.1. in case you have no device corrupt message during every boot up follow the next steps
- on the keep system read only? screen of the TWRP let it allow modifications (swipe!)
- reboot to System
- Link Removed by Moderator
you must see the device corrupt message during boot up -> you are ready to go for a root
- try to reboot the device if the device corrupt message is still there during boot up (Link Removed by Moderator). If it's not there you may repeat the process or check my old guide for troubleshooting.
3. the rooting part -Link Removed by Moderator[/I]
(you can read my old guide why we need to tweak the boot image before installing SuperSU - if you are interested)
- download the ramdisk compression exchanger: https://forum.xda-developers.com/apps/supersu/ramdisk-compression-exchanger-t3533327 (we need this because SuperSU can only work with gzip compressed ramdisks while we have lz4 compressed ones)
- download latest SuperSU TWRP flashable version: https://forum.xda-developers.com/apps/supersu/stable-2016-09-01supersu-v2-78-release-t3452703
- put this (rce_univ.zip) and latest SuperSU (i used v2.79) on your sd card (you need external sd because the internal sd is encrypted in TWRP)
- reboot your device into TWRP (through adb and fastboot as before)
- cancel decrypt data
- don't swipe on system modifying screen just click on "keep read only"
- go to backup, backup your boot image (tick only boot partition /untick the rest/ and select storage as micro sd card) in case anything goes wrong during the rest of the process you can always restore it
- go to install
- select storage and chose micro sd card
- install rce_univ.zip (it will recompress your ramdisk to gzip - so SuperSU can tweak it)
- when it's finished don't wipe or don't reboot! Go back (hit back button button) and install SuperSUxxx.zip
- go back again (without restart or wipe) and install rce.zip again (this will recompress your ramdisk to lz4)
- now you can reboot to system (without any wipe) - it will bootloop a few times, be patient!
If something goes wrong check my old guide for deeper understanding and troubleshooting!
If you have any problem with installing rce_univ.zip please post comments to it's thread:
https://forum.xda-developers.com/apps/supersu/ramdisk-compression-exchanger-t3533327
Comments in this thread shell be only TWRP related or deeply device specific.
No promises... and no responsibility i take... !!!
Supported TWRPs:
in case you want to go for sure or you can't find a working TWRP port it yourself easily using my guide: https://forum.xda-developers.com/lg-k10/development/mtk-portable-twrp-porter-t3536123
or use the ones already ported:
Lg k10 k430: https://forum.xda-developers.com/lg-k10/development/teamwinrecoveryproject-3-0-0-0-lg-k10-t3404434
Lg k10 k430dsy (firmware: 10k - 2017 feb security date): Link Removed by Moderator
(Lg k10 k420n/ds: https://forum.xda-developers.com/lg-k10/development/unofficial-twrp-3-1-0-k420-ds-n-t3571943 - different root method required)
Lg K8: https://forum.xda-developers.com/lg-k10/development/recovery-twrp-3-0-2-lg-k8-k350-mtk-t3517894
others take a look around here: https://forum.xda-developers.com/lg-k10/development
or use this guide: http://www.chinaphonearena.com/foru...752-MT6753-MT6795-MT6797-TWRP-MT67xx-tutorial
Looks cleverly. May take a try
Could it be this SuperSU?
https://download.chainfire.eu/696/supersu/
a_lewicki said:
Could it be this SuperSU?
https://download.chainfire.eu/696/supersu/
Click to expand...
Click to collapse
Well... why would you use that old one? This might not even be systemless root so it would not work. Why dont you check the link i posted in the OP so you could find this one i recommend to use: https://s3-us-west-2.amazonaws.com/supersu/download/zip/SuperSU-v2.79-201612051815.zip
after flashing rce.zip i got an error " unpacking boot image failed! aborting..."
what should i do to fix that? i've tried reading throught your old guide but i'm a noob and i couldn't find anything i could understand.
help anybody???
pedrodgr said:
after flashing rce.zip i got an error " unpacking boot image failed! aborting..."
what should i do to fix that? i've tried reading throught your old guide but i'm a noob and i couldn't find anything i could understand.
help anybody???
Click to expand...
Click to collapse
Next time you try, please make a recovery log (In recovery advanced menu) and send it to me or upload it here!
Which model? Which TWRP?
Also upload or send me your boot image that you backed up!
I added one more line to the script to see where its found the boot partition so please download again before you proceed for a better troubleshooting experience!
@gottlasz after everey install reboot system? (rce.zip then reboot supersu and reboot and rce.zip again and reboot?) or without rebooting?
a_lewicki said:
@gottlasz after everey install reboot system? (rce.zip then reboot supersu and reboot and rce.zip again and reboot?) or without rebooting?
Click to expand...
Click to collapse
No way! Do not reboot! Once you install rce.zip it changes the ramdisk compression so the phone can't boot up. Then the supersu tweaks the boot image (roots the phone) then you install rce.zip to change the ramdisk compression back to normal. Then you can reboot.
@gottlasz thank you so much IT WORKS
a_lewicki said:
@gottlasz thank you so much IT WORKS
---------- Post added at 01:44 PM ---------- Previous post was at 01:42 PM ----------
@gottlasz thank you so much IT WORKS
Click to expand...
Click to collapse
I know it works...
Do you mind me asking which phone you have (k8/k10), which model and which TWRP you used?
gottlasz said:
I know it works...
Do you mind me asking which phone you have (k8/k10), which model and which TWRP you used?
Click to expand...
Click to collapse
twrp 3.0.2
lg k10 k430dse
---------- Post added at 02:39 PM ---------- Previous post was at 02:24 PM ----------
[mention]gottlasz[/mention] do you know how to make snapchat working on root?
a_lewicki said:
twrp 3.0.2
lg k10 k430dse
---------- Post added at 02:39 PM ---------- Previous post was at 02:24 PM ----------
[mention]gottlasz[/mention] do you know how to make snapchat working on root?
Click to expand...
Click to collapse
okay, thanks for the info. I dont know anything about snapchat. If you just download it from playstore?
yes from playstore but i read this app won't work with root
a_lewicki said:
yes from playstore but i read this app won't work with root
Click to expand...
Click to collapse
I just downloaded and tested. Works without any issue...
gottlasz said:
I just downloaded and tested. Works without any issue...
Click to expand...
Click to collapse
Hmmm that's strange...
On my device I can't login to this app and i read this app won't work with root
a_lewicki said:
Hmmm that's strange...
On my device I can't login to this app and i read this app won't work with root
Click to expand...
Click to collapse
I don't know man... i don't think it's a root related issue. The app should promt if it had any problem with root.
However if you use any paid service through the app that can be an issue. Still.. the app has to write something about root if it has a problem with it.
gottlasz said:
Next time you try, please make a recovery log (In recovery advanced menu) and send it to me or upload it here!
Which model? Which TWRP?
Also upload or send me your boot image that you backed up!
I added one more line to the script to see where its found the boot partition so please download again before you proceed for a better troubleshooting experience!
Click to expand...
Click to collapse
Thanks for the fast reply, it's the k10 430dsf
i'll try downloading it again and give it a new try.
I was also using the twrp 3.0.0
i'm downloading the 3.0.2 now and i'll let you know if it works.
Thanks once again.
Happy new year for everyone:good:
i have the LG K8 (K350F) model.
Can i root my phone with this method???. Anyone with this model has probe this tutorial???.
thanks in advanced
raul2903 said:
i have the LG K8 (K350F) model.
Can i root my phone with this method???. Anyone with this model has probe this tutorial???.
thanks in advanced
Click to expand...
Click to collapse
If you have a working TWRP then its gonna work. Did you test any TWRPs already?
Hey Everyone....So I just have a question about the HTC BOLT and how to root it
So I guess I am little confused as to how do I go about this in terms of rooting it
My phone must be unlocked through the htc dev site correct? If so then I am good with that step, I also have seen many posts on how to root it but I just need one general site or a way on how to do it...Last thing I want to do is screw this up and brick the phone from reading multiple posts...So any information would def help me...Currently I am on Nougat 7.0
Thanks
Jay
jortiz31877 said:
Hey Everyone....So I just have a question about the HTC BOLT and how to root it
So I guess I am little confused as to how do I go about this in terms of rooting it
My phone must be unlocked through the htc dev site correct? If so then I am good with that step, I also have seen many posts on how to root it but I just need one general site or a way on how to do it...Last thing I want to do is screw this up and brick the phone from reading multiple posts...So any information would def help me...Currently I am on Nougat 7.0
Thanks
Jay
Click to expand...
Click to collapse
you'll need to flash twrp from download mode, then boot into twrp & either flash SuperSU or Magisk v11.1
my preference is now Magisk, as it now has it's own root plus you can install magisk modules (mods or ROM) without breaking /system
Thanks for the information, So i went to the htc dev site to proceed on how to unlock bootload my phone and they mentioned about "fast boot' that is not a option that needs to be selected on my phone while in download mode ...So can i still unlock it with out that "fast boot " option?
jortiz31877 said:
Thanks for the information, So i went to the htc dev site to proceed on how to unlock bootload my phone and they mentioned about "fast boot' that is not a option that needs to be selected on my phone while in download mode ...So can i still unlock it with out that "fast boot " option?
Click to expand...
Click to collapse
you said u were good w/ that step so I didn't mention....fastboot is not an option in the menu, it's a tool...you need to use fastboot command to unlock bootloader & also to flash twrp
install this for fastboot: https://forum.xda-developers.com/showthread.php?t=2317790
Okay so I know the phone must be connected using the command terminals and to simplify this i would:
1- Use fastboot to get the phone unlocked using the code to unlock it then (NOT Choosing to flash a rom at all for my phone)
2- use use maglsk v11.1 or Super Su and follow the instructions while leaving the phone plugged into the PC
3- once done then go to the play store and update magisk manager
4 - Check any rooted apk via the play store to verify if your phone is rooted
If there is something that i am missing please let me know. Much appreciations so far getting me to this point.
jortiz31877 said:
Okay so I know the phone must be connected using the command terminals and to simplify this i would:
1- Use fastboot to get the phone unlocked using the code to unlock it then (NOT Choosing to flash a rom at all for my phone)
2- use use maglsk v11.1 or Super Su and follow the instructions while leaving the phone plugged into the PC
3- once done then go to the play store and update magisk manager
4 - Check any rooted apk via the play store to verify if your phone is rooted
If there is something that i am missing please let me know. Much appreciations so far getting me to this point.
Click to expand...
Click to collapse
after unlocking bootloader, you will need to flash twrp (fastboot flash recovery nameofrecovery.img), the twrp.img needs to be in you sdktools folder on pc, after flashing, then boot into twrp...from download mode, choose reboot to bootloader, then reboot to recovery. once in twrp, you should probably leave /system read only, then copy either supersu or magisk to sd card, and choose install from main menu of twrp....once done, boot device. if using magisk, update from store
u only need to connect to pc when entering fastboot cmds
will this root work with boost mobile HTC bolt or is there a root that will work for this phone
Chrism1971 said:
will this root work with boost mobile HTC bolt or is there a root that will work for this phone
Click to expand...
Click to collapse
Either should work fine
Sent from my unknown using XDA Labs
Question
OMJ said:
you'll need to flash twrp from download mode, then boot into twrp & either flash SuperSU or Magisk v11.1
my preference is now Magisk, as it now has it's own root plus you can install magisk modules (mods or ROM) without breaking /system
Click to expand...
Click to collapse
Look I know you know what your doing I just barley got into rooting my android devices so my question is will this Brick my phone because last time I tried kingroot and it lock everything. I am scared to lose my warranty on my phone and want to know it will work. I had to take my phone to a sprint tech store last time to get it fixed so I was wondering if you could make a video of how to do it. Thanks for your time and effort Sam.
craftingatic said:
I am scared to lose my warranty on my phone.
Click to expand...
Click to collapse
You will lost your warranty anyway, if you open the bootloader via HTCdev.
craftingatic said:
Look I know you know what your doing I just barley got into rooting my android devices so my question is will this Brick my phone because last time I tried kingroot and it lock everything. I am scared to lose my warranty on my phone and want to know it will work. I had to take my phone to a sprint tech store last time to get it fixed so I was wondering if you could make a video of how to do it. Thanks for your time and effort Sam.
Click to expand...
Click to collapse
1st...as far as warranty goes, HTC is pretty good about repair even if you unlock the bootloader. So if you unlock bootloader, then flash TWRP & root, I always recommend restoring to stock before having any warranty work done.
sorry I don't do videos, but I'm always willing to help out...it's really not very difficult, the risk of a brick is very low if u just follow the instructions...if you're just looking for root, here are the basic steps:
1. unlock bootloader via htcdev.com (you'll have to create a account)
-when selecting the device, choose "all other supported models"
-you'll need to install drivers to pc to communicate to phone, see "required resources" to the left of step 1
-you don't need to install SDK but you will need the fastboot binary in step 4
-at step 5 make sure you are communicating w/ the device by using the cmd fastboot devices, it should list your device in the output
-follow the remaining steps to unlock
2. once bootloader is unlocked, boot back into download mode to flash twrp (custom recovery)
-download latest twrp from here: https://dl.twrp.me/aca/ copy the twrp.img to the folder that has the fastboot binary
-use this cmd to flash twrp: fastboot flash recovery twrp-3.1.1-0-aca.img
-it flashes pretty quick, then boot to bootloader, then boot to recovery
3. 1st time u boot twrp it will ask if u want to keep /system read only, if u plan to stay stock w/ only root, then keep read only
-I always recommend to make a system & boot image backup just in case
-flash MagiskSU or SuperSU, I prefer Magisk
the Sprint ROM has a lot of bloat, if you're interested, I have a ROM posted that cleans all that junk up along with a lot of useful mods, with a stock look
OMJ said:
1st...as far as warranty goes, HTC is pretty good about repair even if you unlock the bootloader. So if you unlock bootloader, then flash TWRP & root, I always recommend restoring to stock before having any warranty work done.
sorry I don't do videos, but I'm always willing to help out...it's really not very difficult, the risk of a brick is very low if u just follow the instructions...if you're just looking for root, here are the basic steps:
1. unlock bootloader via htcdev.com (you'll have to create a account)
-when selecting the device, choose "all other supported models"
-you'll need to install drivers to pc to communicate to phone, see "required resources" to the left of step 1
-you don't need to install SDK but you will need the fastboot binary in step 4
-at step 5 make sure you are communicating w/ the device by using the cmd fastboot devices, it should list your device in the output
-follow the remaining steps to unlock
2. once bootloader is unlocked, boot back into download mode to flash twrp (custom recovery)
-download latest twrp from here: https://dl.twrp.me/aca/ copy the twrp.img to the folder that has the fastboot binary
-use this cmd to flash twrp: fastboot flash recovery twrp-3.1.1-0-aca.img
-it flashes pretty quick, then boot to bootloader, then boot to recovery
3. 1st time u boot twrp it will ask if u want to keep /system read only, if u plan to stay stock w/ only root, then keep read only
-I always recommend to make a system & boot image backup just in case
-flash MagiskSU or SuperSU, I prefer Magisk
the Sprint ROM has a lot of bloat, if you're interested, I have a ROM posted that cleans all that junk up along with a lot of useful mods, with a stock look
Click to expand...
Click to collapse
Do u have to rename the twrp to tarp.img? I flashed the latest tarp the direction I saw said rename twrp so did I do it wrong cause I can't boot into twrp at all I get HTC and some red text then boots all the way up
roadkill42 said:
Do u have to rename the twrp to tarp.img? I flashed the latest tarp the direction I saw said rename twrp so did I do it wrong cause I can't boot into twrp at all I get HTC and some red text then boots all the way up
Click to expand...
Click to collapse
twrp can be named anything u want, your fastboot flash cmd just has to match...when u try to boot into recovery & get a red triangle, that's stock recovery, so yeah it didn't flash then
OMJ said:
twrp can be named anything u want, your fastboot flash cmd just has to match...when u try to boot into recovery & get a red triangle, that's stock recovery, so yeah it didn't flash then
Click to expand...
Click to collapse
OK did it twice it said it did with no errors so just keep doing it till it dose? Or is there another way?
---------- Post added at 04:35 PM ---------- Previous post was at 04:34 PM ----------
roadkill42 said:
OK did it twice it said it did with no errors so just keep doing it till it dose? Or is there another way?
Click to expand...
Click to collapse
No triangle just HTC in gray then flashes red letters under it
roadkill42 said:
OK did it twice it said it did with no errors so just keep doing it till it dose? Or is there another way?
---------- Post added at 04:35 PM ---------- Previous post was at 04:34 PM ----------
No triangle just HTC in gray then flashes red letters under it
Click to expand...
Click to collapse
you should only need to flash twrp once....
post your cmds so I can see what you're doing....make sure you're in download mode
OMJ said:
you should only need to flash twrp once....
post your cmds so I can see what you're doing....make sure you're in download mode
Click to expand...
Click to collapse
OK I was in download mode I c what I can do on the rest thanks probly later today or tomorrow
roadkill42 said:
OK I was in download mode I c what I can do on the rest thanks probly later today or tomorrow
Click to expand...
Click to collapse
Is there a complete in full detail way of flashing tarp in download load mode?
roadkill42 said:
Is there a complete in full detail way of flashing tarp in download load mode?
Click to expand...
Click to collapse
full detail? it's 1 cmd.... fastboot flash recovery twrp.img
https://twrp.me/htc/htcbolt10evo.html
OMJ said:
full detail? it's 1 cmd.... fastboot flash recovery twrp.img
https://twrp.me/htc/htcbolt10evo.html
Click to expand...
Click to collapse
OK thanks there is a lot out there I might did wrong one I try this way and let u know thanks again is there a special key combo to get into twrp after flashing ?
Microsoft Windows [Version 10.0.14393]
(c) 2016 Microsoft Corporation. All rights reserved.
C:\Program Files\Minimal ADB and Fastboot>adb devices
List of devices attached
HT7120403511 device
when i try to reboot to recovery under the htc says this build for devloping purpose only im on n with no updates installed this phone came to me like this bran new
C:\Program Files\Minimal ADB and Fastboot>fastboot flash recovery twrp.img
sending 'recovery' (8156 KB)...
OKAY [ 1.782s]
writing 'recovery'...
(bootloader) HOSD CL#821651
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) Update partition OK
(bootloader) [email protected]
OKAY [ 2.311s]
finished. total time: 4.096s
C:\Program Files\Minimal ADB and Fastboot>adb reboot
error: device not found
C:\Program Files\Minimal ADB and Fastboot>fastboot reboot
rebooting...
finished. total time: 0.004s
C:\Program Files\Minimal ADB and Fastboot> I'm on 7.0
Hi guys,
I have started this thread so that you guys can root your moto M XT_1663_S356 andriod (7.0)
First of all i'm not responsible if your phone bricks burns or dies.
A big thanks to VVizard from lenovo RU forum with out him, it was not possible.
Thanks to Chainfire for the SuperSu.zip
To check Build number go to Settings -> About Phone-> Build number
Note -
1 - This only works for Moto M which is having build number XT1663_S356_170621_ROW. If you are on any other build number then please don't proceed.
2 - All the files are attached
3 - Install all the Motoral drivers and Minimal and adb folder.
4 - Following link contains all files needed to root the phone.
https://drive.google.com/file/d/0B3eDb0dWRU-uUjk4ZS1tdFpRR1U/view?usp=sharing
Rooting Moto M phone is divided into 3 Parts
1) Unlocking BootLoader
2) Flashing TWRP
3) Flashing SuperSu.zip
unlocking the bootloader
Note - This will wipe out all the data hence take a backup before unlocking boot loader
1 - First of all enable the Developer Option, To Enable the Developer Option, Go to your Settings -> About Phone-> Now Tap on the Build Number 7-8 Times until you see a toast message “Developer option enabled"
2 - Go back to settings -> Now you need to enable the OEM Unlock by going to Settings -> Developer Option and Enable OEM Unlock and USB Debugging
3 - Download and Extract the Downloaded ADB fastboot Zip file on your PC
4 - Now connect your phone to Computer using USB Cable.
5 - When you connect your Phone to Computer, please wait until all the drivers get installed.
6 - In your ADB fastboot folder open a command prompt window by pressing Shift Key + Right Mouse Click
7 - Now type the command in your command window
adb devices
If you see a pop up to allow USB Debugging on your phone, Click OK
8 - Now type the command below to reboot your phone to bootloader
adb reboot bootloader
9 - Once your phone reboot into bootloader, then type the command below to make sure fastboot drivers are installed properly.
fastboot devices
10 - This command will list the connected devices. If your phone’s serial number shows up you are good to go and may continue. If the phone is NOT listed this indicates that your drivers are not installed correctly.
11 - If your phone is listed then type in the following command in CMD.
fastboot oem unlock
12 - Check your phone you would have written"do you really want to unloock bootloader ? "(something like this). Just select yes using volume up and down button and press power button to confirm it .
13 - Congrats your bootloader is unlocked
Install TWRP
Note - You should have your bootloader unlocked before proceeding.
Copy the boot_XT1663_356.img and TWRP_Moto_M.img to Minimal adb folder
1 - First of all enable the Developer Option, To Enable the Developer Option, Go to your Settings -> About Phone-> Now Tap on the Build Number 7-8 Times until you see a toast message “Developer option enabled"
2 - Go back to settings -> Now you need to enable the OEM Unlock by going to Settings -> Developer Option and Enable OEM Unlock and USB Debugging
3 - Download and Extract the Downloaded ADB fastboot Zip file on your PC
4 - Now connect your phone to Computer using USB Cable.
5 - When you connect your Phone to Computer, please wait until all the drivers get installed.
6 - In your ADB fastboot folder open a command prompt window by pressing Shift Key + Right Mouse Click
7 - Now type the command in your command window
adb devices
If you see a pop up to allow USB Debugging on your phone, Click OK
8 - Now type the command below to reboot your phone to bootloader
adb reboot bootloader
9 - Once your phone reboot into bootloader, then type the command below to make sure fastboot drivers are installed properly.
fastboot devices
10 - This command will list the connected devices. If your phone’s serial number shows up you are good to go and may continue. If the phone is NOT listed this indicates that your drivers are not installed correctly.
11 - If your phone is listed then type in the following command in CMD.
fastboot flash boot boot_XT1663_356.img
12 - To flash the recovery, Type the command
fastboot flash recovery TWRP_Moto_M.img
13 - Congrats! you have successfully installed TWRP.
Rooting Phone.
Note -
You should have your bootloader unlocked.
You should have TWRP installed.
You should have supersu.zip copied in your phone.
1 - Switch off your phone. Now press volume down + power button till phone vibrates. Once it vibrates release the power button you should see android logo.
2 - Now with the help of volume up and down button select 'Recovery mode' and press power button.
3 - TWRP should start up.
4 - Select 'Allow Modification' and proceed.
5 - Select 'Install' and then select the 'SuperSu.zip' file and flash it.
6 -Restart the Phone.
7 - Congrats! your phone is rooted.
Note -
I have tried all this steps and have successfully rooted my phone i'm not responsible for any damage.
I have not build the boot_M_S365/ img file this is done by VVizard and really very thank full to him.
I am making a video on this!
Method Issues
Bro, I have faced a few problems since I have started
i) When I type in adb devices it shows my phone but unauthorized
so I have to allow it as you said but only after a reboot and doing the process again will it show authorized
ii) after entering adb reboot bootloader it doesnt show bootloader locked but straight up fastboot mode
iii) then when i enter fastboot oem unlock it shows asks me if I want to unlock, I press on volume up. Then it again asks me some other thing and I hold the volume up down and power together. Next I reboot into my phone. All data erased. I setup it again.
Now, does this mean my bootloader is unlocked? When I reboot it shows something on the middle right- unlocked..
So does this mean I continue and install twrp now? or what?
manandua01 said:
Thanks bro, I will give you credits ^_^
Click to expand...
Click to collapse
Cool!
manandua01 said:
Bro, I have faced a few problems since I have started
i) When I type in adb devices it shows my phone but unauthorized
so I have to allow it as you said but only after a reboot and doing the process again will it show authorized
ii) after entering adb reboot bootloader it doesnt show bootloader locked but straight up fastboot mode
iii) then when i enter fastboot oem unlock it shows asks me if I want to unlock, I press on volume up. Then it again asks me some other thing and I hold the volume up down and power together. Next I reboot into my phone. All data erased. I setup it again.
Now, does this mean my bootloader is unlocked? When I reboot it shows something on the middle right- unlocked..
So does this mean I continue and install twrp now? or what?
Click to expand...
Click to collapse
1 - It doen't matter if its authorized or not..
2 - yes! thats correct it directly takes you to fastboot mode it use to show bootloader locked for old Moto phones).I 'll make changes in the thread.
Yes! your bootloader is unlocked successfully..
if you see something like 'Your devices is unlocked and cant be trusted' on the left hand side during the moto logo.
TWRP Recovery
akash.mahadeshwar said:
1 - It doen't matter if its authorized or not..
2 - yes! thats correct it directly takes you to fastboot mode it use to show bootloader locked for old Moto phones).I 'll make changes in the thread.
Yes! your bootloader is unlocked successfully..
if you see something like 'Your devices is unlocked and cant be trusted' on the left hand side during the moto logo.
Click to expand...
Click to collapse
Thanks for your help Y_Y
Hey bro, I am not about to install the recovery.
Before this may I ask why we need to flash boot_XT1663_356.img ?
Also, isn't this command wrong? fastboot flash boot boot_XT1663_356.img
It should be fastboot flash boot boot_XT1663_356.img
Without the boot twice ryt?
Also, will the data be erased after installing TWRP recovery or not? If not, will it be erased after installing the SuperSU?
manandua01 said:
Thanks for your help Y_Y
Hey bro, I am not about to install the recovery.
Before this may I ask why we need to flash boot_XT1663_356.img ?
Also, isn't this command wrong? fastboot flash boot boot_XT1663_356.img
It should be fastboot flash boot boot_XT1663_356.img
Without the boot twice ryt?
Also, will the data be erased after installing TWRP recovery or not? If not, will it be erased after installing the SuperSU?
Click to expand...
Click to collapse
1 - It is the Image file which is specifically build for S356 (build number) hence it is necessary to flash it before flashing TWRP. If you don't flash boot image then you might face boot loop issues and hard brick your phone.
2 - The correct command is 'fastboot flash boot boot_XT1663_356.img' . the first boot is to recognize cmd that we are flashing a boot image and the second boot is the name of image file.
3 - Flashing TWRP and Super SU won't erase your data.
akash.mahadeshwar said:
1 - It is the Image file which is specifically build for S356 (build number) hence it is necessary to flash it before flashing TWRP. If you don't flash boot image then you might face boot loop issues and hard brick your phone.
2 - The correct command is 'fastboot flash boot boot_XT1663_356.img' . the first boot is to recognize cmd that we are flashing a boot image and the second boot is the name of image file.
3 - Flashing TWRP and Super SU won't erase your data.
Click to expand...
Click to collapse
I installed TWRP unlocked bootloader copied SuperSU- and was abt to root. With volume up and down I came to Factory Mode
It said Factory Mode
I pressed on power button- now it shows something in Japenese or Chinese what should I DO? I am scared as hell bro
ITS DOING SOME WEIRD STUFF NOW- GPS, SIM etc I have no clue .-.
UPDATE: Rebooting phone- Back to my home screen now. Heres what happened
(uploading video will post link here soon)
manandua01 said:
I installed TWRP unlocked bootloader copied SuperSU- and was abt to root. With volume up and down I came to Factory Mode
It said Factory Mode
I pressed on power button- now it shows something in Japenese or Chinese what should I DO? I am scared as hell bro
ITS DOING SOME WEIRD STUFF NOW- GPS, SIM etc I have no clue .-.
UPDATE: Rebooting phone- Back to my home screen now. Heres what happened
(uploading video will post link here soon)
Click to expand...
Click to collapse
As i have mentioned in my thread that you need to select recovery mode and not factory mode
Please select recovery mode and you should b able to see twrp
Note - to select recovery mode press volum up n down button till it shows 'recovery mode ' in the andrioid logo screen
akash.mahadeshwar said:
1 - It is the Image file which is specifically build for S356 (build number) hence it is necessary to flash it before flashing TWRP. If you don't flash boot image then you might face boot loop issues and hard brick your phone.
2 - The correct command is 'fastboot flash boot boot_XT1663_356.img' . the first boot is to recognize cmd that we are flashing a boot image and the second boot is the name of image file.
3 - Flashing TWRP and Super SU won't erase your data.
Click to expand...
Click to collapse
akash.mahadeshwar said:
As i have mentioned in my thread that you need to select recovery mode and not factory mode
Please select recovery mode and you should b able to see twrp
Note - to select recovery mode press volum up n down button till it shows 'recovery mode ' in the andrioid logo screen
Click to expand...
Click to collapse
Bro, I opened Recovery Mode, but now its asking for a password. It shows temp on the top. You from India, ryt? Could you give me your number? or maybe a skype id?
EDIT: Here's what was on my cmd after flashing the recovery http://prntscr.com/ft3t1l
manandua01 said:
Bro, I opened Recovery Mode, but now its asking for a password. It shows temp on the top. You from India, ryt? Could you give me your number? or maybe a skype id?
Click to expand...
Click to collapse
Go ahead ignore the password part.. it will only appear first time.. you should have a option to go ahead..
akash.mahadeshwar said:
As i have mentioned in my thread that you need to select recovery mode and not factory mode
Please select recovery mode and you should b able to see twrp
Note - to select recovery mode press volum up n down button till it shows 'recovery mode ' in the andrioid logo screen
Click to expand...
Click to collapse
Please reply asap
---------- Post added at 08:57 AM ---------- Previous post was at 08:56 AM ----------
akash.mahadeshwar said:
Go ahead ignore the password part.. it will only appear first time.. you should have a option to go ahead..
Click to expand...
Click to collapse
Ok trying now
---------- Post added at 09:21 AM ---------- Previous post was at 08:57 AM ----------
akash.mahadeshwar said:
Go ahead ignore the password part.. it will only appear first time.. you should have a option to go ahead..
Click to expand...
Click to collapse
Yo bro, I can only view External (sd card) storage. Not internal storage! What to do now? As I have SuperSU in Internal Storage
---------- Post added at 09:29 AM ---------- Previous post was at 09:21 AM ----------
Ok, I have rooted the phone successfully. Had to copy the SuperSU file to SD Card though 6-6
manandua01 said:
Please reply asap
---------- Post added at 08:57 AM ---------- Previous post was at 08:56 AM ----------
Ok trying now
---------- Post added at 09:21 AM ---------- Previous post was at 08:57 AM ----------
Yo bro, I can only view External (sd card) storage. Not internal storage! What to do now? As I have SuperSU in Internal Storage
---------- Post added at 09:29 AM ---------- Previous post was at 09:21 AM ----------
Ok, I have rooted the phone successfully. Had to copy the SuperSU file to SD Card though 6-6
Click to expand...
Click to collapse
Ext_sdcard folder is ur memory card folder and sdcard folder is the internal memory folder in twrp
BAM!
---------- Post added at 01:14 PM ---------- Previous post was at 01:12 PM ----------
I really thank you for this great effort
all things went good but I had a problem that I didn't find the SuperSU-v2.82-201705271822.zip although I am sure that I put it in the internal memory
please help
Hi there,
After I unlocked the bootloader, pushed the twrp recovery successfully, got stuck in the recovery mod each time I reboot the phone so can't boot the stock rom. Done wipe factory reset and format data and still nothing changed. Any ideas?
Thanks in advance OP
Edit: Just solved issue by flashing stock firmware
pdf5 said:
Hi there,
After I unlocked the bootloader, pushed the twrp recovery successfully, got stuck in the recovery mod each time I reboot the phone so can't boot the stock rom. Done wipe factory reset and format data and still nothing changed. Any ideas?
Thanks in advance OP
Edit: Just solved issue by flashing stock firmware
Click to expand...
Click to collapse
May I have the firmware file, just in case? Is it ok if firmware country code doesn't match? Do you get imei?
any idea? when image for new build will be released?
rajesh280392 said:
any idea? when image for new build will be released?
Click to expand...
Click to collapse
Well, yes ... The new boot.img for removing encryption. Especially for post-OTA updating to XT1663_S364_170803_ROW.
boot_XT1663_364.img
Does anyone know how to keep your Moto M rooted even after updating to the new security update of 7.0? Do we just flash the new .img file or what? Kinda newb here
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.