Related
Even simpler root than Invisiblek's method for the older versions: If you have already tried that method and now have broken wireless, see Post #2.
Note: A more detailed and user-friendly version of these instructions can be found at: http://www.oppoforums.com/threads/n5206-international-root-instructions.24159
Download http://lum.uk/n3/files/recmodn3.img and http://lum.uk/n3/files/Root_ColorOS_by_tantrums_v2.zip
Copy the rooter onto your SD card.
Boot into fastboot by holding volume up while powering on the phone.
fastboot oem unlock
fastboot flash recovery recmodn3.img
fastboot boot recmodn3.img
Flash the root coloros zip file, reboot and you're rooted.
Note: This is a modified stock recovery that can flash OTAs as well as zips not signed by Oppo. If you prefer TWRP then that is available here: https://dl.twrp.me/n3/. Note that at the time of writing TWRP is unable to flash OTAs.
Thanks to [email protected] for the original root method, Arvin A. [email protected] for the fixing SuperSU to work on ColorOS, and [email protected] for providing the modified N3 recovery.
Restoring stock firmware
Download your chosen firmware and recovery from this thread
Copy the firmware to the root of the internal storage
Take a nandroid backup using TWRP
Reboot to bootloader from within TWRP
Code:
fastboot flash recovery recovery_N3.img
fastboot reboot
adb reboot recovery
Use the stock recovery to flash your chosen firmware
If you are downgrading then wipe data and cache (you did remember to take a nandroid, right?)
Reboot
You are now on stock fimware. Follow the rooting instructions in post #1, and if you wiped you may optionally restore only the data partition from your nandroid backup.
Will memory be erased?
Hi,
So i'm looking forward to root my beautiful Oppo N3.
On my last Phones memory (data and so on) was erased alongside with unlocking the phone.
Will it be the same on this phone so that I have to backup all my data?
Your data will not be erased when rooting or unlocking. Also your warranty will not be invalidated like it is with other manufacturers.
It is, however, always wise to take a backup before anything like this, just in case something does go wrong.
Hi,
I tried rooting my N3 now but i made a mistake by not executing the commands after falshing SuperSU.
That's why my phone is always booting into TWRP. There i tried executing your commands, but apparently the shell refuses to su by throwing exception: "command not found"
Going on with mount-command, it is also giving back an error: "can't find /system in /proc/mounts"
Hope sb could help me now...
EDIT: Solved by installing stock recovery, booting system, and the reflash twrp.
Lum_UK said:
Even simpler root than Invisiblek's method for the older versions: If you have already tried that method and now have broken wireless, see Post #2
Download http://teamw.in/project/twrp2/282 and http://download.chainfire.eu/supersu
adb reboot bootloader
fastboot oem unlock
fastboot flash recovery openrecovery-twrp-2.8.4.0-n3.img
fastboot reboot
adb reboot recovery
Flash Super SU from within TWRP. Then boot the OS
adb shell
su
mount -o remount,rw /system
echo "/system/xbin/su --daemon &" >> /system/etc/init.qcom.post_boot.sh
Reboot and you're rooted.
By default ColorOS doesn't let apps auto-start themselves, so go into security centre and allow SuperSU to auto-start, otherwise you won't get prompts for root when other apps need it.
Thanks to invisiblek for the original root method and babelmonk for the fix. I have shamelessly copied these and adapted them for the new firmware.
Click to expand...
Click to collapse
Quoted from your post in oppo forum
Wait for the phone to boot:
adb reboot recovery
It should boot into TWRP recovery flash the SuperSU zip you downloaded but do not reboot as we need to fix a small bug in SuperSU due to Oppo not using the expected startup scripts.
adb shell
su
mount -o remount,rw /system
echo "/system/xbin/su --daemon &" >> /system/etc/init.qcom.post_boot.sh
Reboot and congratulations. You are now rooted.
Sorry , quite new in fastboot command so i apologize if I misunderstood you but I'm running on N5206_EX_23_150208 , which should i follow ? to boot up after flashing SuperSU or not to boot up ?
It doesn't matter which way around you do it, just that root won't work outside of ADB until it's done.
I assume that XDA folk are more familiar with ADB etc. than on the Oppo forums so the instructions skip over more detail here.
Updated the method to use fastboot boot instead of fastboot flash.
This should work around the issue with phones that can't flash twrp, and also leave the stock recovery in place which is more useful to have until we get some custom roms.
Lum_UK said:
Updated the method to use fastboot boot instead of fastboot flash.
This should work around the issue with phones that can't flash twrp, and also leave the stock recovery in place which is more useful to have until we get some custom roms.
Click to expand...
Click to collapse
I was using modified boot.img to get root and then edit init.qcom.post_boot.sh. Now my wi-fi is broken. Can I fix it without wiping? Maybe flash some other boot img?
Anilexis said:
I was using modified boot.img to get root and then edit init.qcom.post_boot.sh. Now my wi-fi is broken. Can I fix it without wiping? Maybe flash some other boot img?
Click to expand...
Click to collapse
Fixed it by flashing boot.img from 150208, root still there due to script edit.
Updated the OP to use the modified stock recovery (Wmjan's recovery for the N5207) as this will be friendlier to noobs and also make it easier to install OTAs.
Anyone know where to get the root coloros file? Link doesn't seem to work for me...
http://www.oppoforums.com/attachment..._v2-zip.31142/
cowabunga said:
Anyone know where to get the root coloros file? Link doesn't seem to work for me...
http://www.oppoforums.com/attachment..._v2-zip.31142/
Click to expand...
Click to collapse
Sorry for the delay in replying. I've re-hosted the file for you.
http://lum.uk/n3/files/Root_ColorOS_by_tantrums_v2.zip
You could also try this. It worked on my girlfriend's R5 running a similar version of ColorOS. Didn't need modified recovery or anything, install it, run, click the root button, and it'll reboot to recovery and root for you.
http://lum.uk/n3/files/ForceRoot.apk
can this root work with Chines n5207
Hello,
I'm from Malaysia,
I got problem with my N3 / N5206 after update the newest version of software...now it cannot detect any line signal and open a wifi...what the problem,can u help me...
I can't make the WiFi to work again. Installed all versions of firmware and no luck....
Update: I was using the wrong tool to flash the firmware.
Don't update the phone with Msm8974DownloadTool !!!!
You have to download and install QPST_2.7.460 and place the phone in download mode by pressing volume + and power button and then in QPST load the firmware N5206EX_11_A.11_150528_SVN6225 or Oppo_N3_N5206_EX_11_A.13_151230 or N5206EX_11_A.10_150519_SVN6196
After flashing the wifi is working but you gonna loose the NV ram backup for the IMEI numbers..
Then you have to open dealpad with *#801# and anable Full-port ON
In QFIL(QPST) click on Tools then click QCN Backup Restore
Choose the qcn file and press restore.
Everything will work again after reboot the phone...
I live in Taiwan and order my oneplus3 from China, but not from the official seller
Jindong or oneplus site but form 3rd party seller on Taobo, which is in Shenzhen.
Thay have sold hundreds of oneplus3 and have most high praise in Taobo- Shenzhen
My oneplus3 take over 7 days shipping to my hand.
While I 1st unbox my oneplus on 9/6 , it has already bootloader unlock and TWRP 3.2.0 installed. As you know, the 3 party seller sold me the used device, but it's not fake, it has full package and correct IMEI with it, I also cheked IMEI on oneplus official site.
I have no choice but jut to accept a used device with new-one price.
I immediately update to official TWRP 3.2.1 and install freedomOs CB 1.6, XPOSED, rooted, everything looks fine.
But after 4 days uesd, while I change system font with ifont and it won't boot to system, jut stuck at 1+ boot screen, after
a dozen of secnods , automatically boot into TWRP , it even can't boot into TWRP , just hang on TWRP logo,
Fastboot flash other version of TWRP, still can't boot into both system and TWRP.
After fastboot flash stock recovery, it can boot into recovery, and then flash TWRP -> boot in TWRP. But still can't mount system/data/cache, some boots even unable to mount internal storage.
(While on stock recovery, ADB sideload OTA.zip from official site always stuck at 47%)
Fastboot erase usersdata and TWRP format still don't work, no lucky, can't mount system/data/cache.
I ask my colleague hand carry my oneplus3 during his business trip, return it to the 3rd party seller. The 3rd party seller only took 3 days to ship to oneplus to fix it and return to them, and .. return to my colleague.
While my colleague got the phone, it work fine with bootloader lock, Chinese H2 OS for more then one week.=>( So that it's not the hardware issue, not internal SD Corrupt?)
I ask he to test it as he can, after 2weeks. He come to Taiwan and bring it to me. He dose not find any problem with daily use on bootloader locked H2 OS.
When I got the "return" oneplus 3 ,
fastboot unlock booloader->
Decrypt follow this: Decrypt OxygenOS without losing data
i also see this:SOLVED][TWRP]Unable to Decrypt Storage
I think is might be CB rom Unstable and encryption issue.
So I install FreedomOS 1.6 and decrypt data this time.
But guess what happen!?
It have happen again and again more then 5 times -
no flash anything, no reboot, just in system used-> got lag->got black screen-> got reboot->unable to reboot system-> unable to mount/wipe/restore data/system/cache in official TWRP.
The only solution seems to "fastboot format users data" , then I can mount/restore/format data/cache/system , till now, i am confused, I don't know if its software or hardware issue, I just spent too many hours on it!
Please help, any advise is welcome...and.. sorry for my English, tried my best.
This issue is really weird.
Can you share the logs given by TWRP, with the kernel log of your twrp recovery.
To do:
Code:
adb shell
dmesg > /tmp/dmesg.log
exit
adb pull /tmp/recovery.log <path_on_your_computer>
adb pull /tmp/dmesg.log <path_on_your_computer>
All theses things needs to be done directly in twrp, adb is needed.
If you want to boot into system after decrypting it, you have to flash supersu, otherwise OOS will encrypt itself at next boot, causing a brick. Also try the modded version of twrp.
NevaX1 said:
This issue is really weird.
Can you share the logs given by TWRP, with the kernel log of your twrp recovery.
To do:
Code:
adb shell
dmesg > /tmp/dmesg.log
exit
adb pull /tmp/recovery.log <path_on_your_computer>
adb pull /tmp/dmesg.log <path_on_your_computer>
All theses things needs to be done directly in twrp, adb is needed.
Click to expand...
Click to collapse
Dear Sir,
Done it Immediately, thank you!!
ArisLi said:
Dear Sir,
Done it Immediately, thank you!!
Click to expand...
Click to collapse
I can't see any errors here, can you try to capture the log after you get the same error in your twrp.
NevaX1 said:
I can't see any errors here, can you try to capture the log after you get the same error in your twrp.
Click to expand...
Click to collapse
Sure, I believe it will happen during this weekend or on Monday.
aadityarulez said:
If you want to boot into system after decrypting it, you have to flash supersu, otherwise OOS will encrypt itself at next boot, causing a brick. Also try the modded version of twrp.
Click to expand...
Click to collapse
For more information: I didn't try to decrypt data before my oneplus3 return to China, I did decrypt it after it return form China, and I only flash freedom OS 1.6 with systemless SU t and stock (patch) kernel, than flash EX kernel, i believe both of them is patched, disable force decrypting.
My decrypt sequence: Unlock bootloader->fastboot format users data-> flash freedom1.6 with systemlessSU let it boot without configuration ->work fine for 3 days and brick after 4 days used with serval times of booting.(less then 5 times)
Every time before my oneplus3 get this type of in-system-used-brick, I see some root access issue or permission issue, that is V4A driver lost, I have no permission to move my files in media storage( for example, move some files from download folder to XpoasedInstaller folder), or Dolby atom crash....
The latest brick, I used my phone on bed for more than 2 hours with no issue, suddenly Dolby ATOM crash, unable to open it and V4a lost its driver, then I try to boot into TWRP to make a boot/system/data backup, but it fail to mount data and system partition.
Even on system-mode SU, It still happen two times of in system brick.
So now i set SELunx permission and do frequently TWRP and Ti-back, I believe It would brick again few days later. At least after many times of Try/error, I can confirm "format uesers data then I can use TWRP for system/data partition.
NevaX1 said:
I can't see any errors here, can you try to capture the log after you get the same error in your twrp.
Click to expand...
Click to collapse
It happen again while this morning I get up and updating two apps,
It freeze then reboot to recovery, unable to mount system/data again.
I have the latest nandroid data/system/boot backup last night, i believe it finally would be brick again.
Here is the log.
I will keep it in the state, please help, I won't "fastboot format usersdata" this time, till we know the cause, and have your instruction.
EDIT： upload the video, you can see it unable to boot in sysytm, in TWRP can't mount system/data/cache , unable to back/restore/install anything
https://youtu.be/KM4gX16sEHQ
What happened when you went completely stock?
aadityarulez said:
What happened when you went completely stock?
Click to expand...
Click to collapse
My friend test with completely stock/ bootloader lock for more one week in Chian (oneplus
service Centre in Shenzhen recoverey it ), every thing is fine just without google service.
Yesterday,I just re-flash freedom 1.6.1 on cleanest status, fastboot formate userdata-> TWRP format (without this both nandroid or new flas rom won't boot up)-- BOOT
After two days used, every things is fine, but just half hours ago my phone brick with all cache/system/data partition encryption while I am in system uesing , I will report detail at night while I have time, i believe I have found the root cause.
Follow this guide
http://forum.xda-developers.com/oneplus-3/how-to/oneplus-3-decryption-ultimate-guide-t3497940
hi,
my oneplus 3 has been rote since i got it (i bought it on launch day) but since i updated it to the beta 19, my phone is no longer rooted : when i put the phone in fastboot it says that my bootloader it unlocked but all the apps who requier root are saying that the phne is not rooted and i cant get twrp to work. i tryied with the official app on my phone and with a program called "tool all in one" (https://forum.xda-developers.com/on...ol-tool-one-driversunlocktwrpfactory-t3398993) and when i flash twrp from the program, i can boot into twrp but then i can't access my files and after i boot the phone, i can no longer boot to twrp
does anyone have a solution that doesn't involve me wiping the phone?
You loose root after updating. Try installing twrp again and then rooting it. Use the toolkit for oneplus 3. Simplifies the process
what do you mean by "then rooting it" ?
the program i use does the same thing as the toolkit and when i install twrp, as i said, it can boot on twrp one time and in twrp i can't access my files and after i boot the phone i can't get back to twrp ,i get the stock recovery
Unless your ROM has built-in root, after flashing TWRP, you have to flash SuperSU or Magisk to obtain root. Mere flashing of TWRP will not give you root.
I know but i can't get to the folder when the magisk file is : when in boot into twrp i cant see my files
Few details... it's quite difficult to help you.
What's the root method? Magisk, SuperSU or Kingroot? Which version?
Ps TWRP recovery is not depending by root, you just need to unlock bootloader (surely it's already unlocked) and flash the same recovery, from PC, via the command "fastboot flash recovery filename.img".
Now enter in TWRP:
1) Wipe /system and /cache;
2) Flash another time Open Beta 19;
3) Flash Magisk or SuperSU (be sure to have latest release);
4) Move TWRP img file from computer to device, then flash it another time (because firmware provides the OOS stock recovery);
5) Reboot and wait 5-10 minutes, because of cache rebuilding.
Tell me if you solve
I am using magisk
Yes my bootloader is unlocked
My problem is that when i flash twrp i cant access my files so i don't want to wipe system if i cant reflash something after
I think that I'll wait for the next update, maybe then it will work
But thank you for your help
Which version of TWRP do you have? Try eng.stk's latest version.
I tryied 3.1.1-2
The eng.stk is not available anymore
Your phone is encrypted, so you have to format data ( but your internal storage wiped by formating data, so back it up ,then only twrp read files in your storage)and flash custom kernel then boot restore backup .
how do you know that my phone is encrypted? i never encrypted it
i use titanium backup so i can't back my phone up until i get rot back
Whenever you flash stock ROM it encrypt if you boot into system directly . So twrp could not read internal storage. Whenever you flash stock ROM you must flash custom kernel or any other method to avoid encryption. This is happened to me and what I'd done is flash custom kernel before boot into rom
To save your data try this
https://forum.xda-developers.com/oneplus-3/how-to/unencrypt-oxygenos-loosing-data-t3412228
Who said that? Check this: https://forum.xda-developers.com/devdb/project/?id=15934#downloads
Edit: If you want to save items in internal storage, you can use ADB commands instead of TWRP. You can also simply copy and paste if your PC recognises the internal storage of your phone.
I succeeded but i had to clean everything and use the last backup i made a week ago
Thank you all for your help
Good morning,
I don't know why but my current phone status is that doesn't boot anymore with Android installed on it. At the moment I've my phone unlocked, twrp 3.1.1 and a backup of last S.O.
I took (when unlocking) a complete full_dump.img as described in the thread UnlockBootloader correctly, with all other files also.
Now, I'm able to enter in TWRP, so I place these operatinos:
wipe all
restore backuped twrp zip
restart phone in normal booting
All operation seems to works fine but when I restart the phone it goes back in TWRP... no android boot window. I watched the content of phone and it seems no files where placed in system (it seems void).
What's the matter?
I'm able to go in fastboot mode also (download mode it working but my PC can't recognize the COM port at the moment)
Help me please, I'd like to restore the complete full_dump.img (and return with locked status var) with the command:
send_command \\.\COM19
dd if=/data/media/0/full_dump.img of=/dev/block/mmcblk0 bs=4096 count=1552384
Anyone help me please?
I tried many time to install a .ZIP custom image ROM, but it doesn't seem to boot with android because all times come back in TWRP.
Sounds like you wiped system, edited it, deleted something or it is corrupt.
Wipe everything excluding system ( don't check it off)
Go advanced > fix permissions
Install a ROM again
If that doesn't work. I suspect you have a file system anymore.
You will now have to go backwards, reinstall stock image using lg bridge if you didn't make a backup of stock with the file system
Romulus76 said:
Good morning,
I don't know why but my current phone status is that doesn't boot anymore with Android installed on it. At the moment I've my phone unlocked, twrp 3.1.1 and a backup of last S.O.
I took (when unlocking) a complete full_dump.img as described in the thread UnlockBootloader correctly, with all other files also.
Now, I'm able to enter in TWRP, so I place these operatinos:
wipe all
restore backuped twrp zip
restart phone in normal booting
All operation seems to works fine but when I restart the phone it goes back in TWRP... no android boot window. I watched the content of phone and it seems no files where placed in system (it seems void).
What's the matter?
I'm able to go in fastboot mode also (download mode it working but my PC can't recognize the COM port at the moment)
Help me please, I'd like to restore the complete full_dump.img (and return with locked status var) with the command:
send_command \.\COM19
dd if=/data/media/0/full_dump.img of=/dev/block/mmcblk0 bs=4096 count=1552384
Click to expand...
Click to collapse
You can use FWUL ( https://tinyurl.com/FWULatXDA ). Go into LG folder and double click on the lglaf auth icon.
Once you see the terminal window use your restore command:
dd if=/data/media/0/full_dump.img of=/dev/block/mmcblk0 bs=4096 count=1552384
Next time you should consider to use the DLM backup method ( https://tinyurl.com/dlbackup )
Regarding TWRP try the latest beta in the official TWRP thread.
Try to format system in the wipe menu then flash a custom ROM again. Pull the recovery log afterwards as described in the TWRP FAQ 4 A of the official TWRP thread.
.
Sent from my LG-H815 using XDA Labs
steadfasterX said:
You can use FWUL ( https://tinyurl.com/FWULatXDA ). Go into LG folder and double click on the lglaf auth icon.
Once you see the terminal window use your restore command:
dd if=/data/media/0/full_dump.img of=/dev/block/mmcblk0 bs=4096 count=1552384
Next time you should consider to use the DLM backup method ( https://tinyurl.com/dlbackup )
Regarding TWRP try the latest beta in the official TWRP thread.
Try to format system in the wipe menu then flash a custom ROM again. Pull the recovery log afterwards as described in the TWRP FAQ 4 A of the official TWRP thread.
.
Sent from my LG-H815 using XDA Labs
Click to expand...
Click to collapse
I'd try this method first. Steadfaster is more credible and knows what he us talking about before you try my suggestion and wipe data as well.
His method is to restore the file system... And to make a backup of it in case it happens again
---------- Post added at 08:11 AM ---------- Previous post was at 08:06 AM ----------
BTW I'm using twrp 3.1.1 works fine but your phone might not like it
deltadiesel said:
Sounds like you wiped system, edited it, deleted something or it is corrupt.
Wipe everything excluding system ( don't check it off)
Go advanced > fix permissions
Install a ROM again
If that doesn't work. I suspect you have a file system anymore.
You will now have to go backwards, reinstall stock image using lg bridge if you didn't make a backup of stock with the file system
Click to expand...
Click to collapse
Yes, it sounds like something was corrupt in the file system or similar.
I tried to install a new custom ROM (as many other times in the past), wiping data - cache - system first but with no luck, it wont boot Android, and return always in TWRP.
Yesterday evening I tried also a full KDZ refurbish with LGUP since my phone can boot in download mode (and recognized from LGUP), but with no luck because after start the process the tool give me a message back (at 9% of operation):
"FAIL - Flash error code 0x2000"
Is there any method to repair corrupted file system or flash partition? TWRP o similar?
steadfasterX said:
Next time you should consider to use the DLM backup method ( https://tinyurl.com/dlbackup )
Regarding TWRP try the latest beta in the official TWRP thread.
Try to format system in the wipe menu then flash a custom ROM again. Pull the recovery log afterwards as described in the TWRP FAQ 4 A of the official TWRP thread.
Click to expand...
Click to collapse
Thanks,
but when I made the full_dump.img there wasn't this DLM method out yet (I made this on the 11/16/2015)
I'll try the new beta TWRP on the official thread late this evening, and I'll try to make a LOG...
Thread update: my phone doesn't go in recovery mode also, now only in DOWNLOAD MODE (volUP + USB cable) and it hangs on error 0x2000
I think I'll take the phone to the LG customer care, for motherboard change.
You are getting 0x2000 because you are trying to flash a KDZ with an older ARB version than what is currently on your phone. You need to flash newer firmware that has the same or greater ARB version than what is on your phone.
-- Brian
Romulus76 said:
Thread update: my phone doesn't go in recovery mode also, now only in DOWNLOAD MODE (volUP + USB cable) and it hangs on error 0x2000
I think I'll take the phone to the LG customer care, for motherboard change.
Click to expand...
Click to collapse
You are flashing the wrong file for your phone
Flash another one
After you success fully flash right file( try one that is biggest in size and most recent)
Flash TWRP (3.1.1 should be fine after)
MAKE A BACKUP OF EVERYTHING (data, system, firmware, etc - so you don't have to go through this again just in case)
Wipe ( don't wipe system - you can do a regular wipe without checking things off it doesn't select system)
Install custom ROM
Flash SuperSU to root again
https://forum.xda-developers.com/showthread.php?t=3660257
Post 71-75
This is really a note to myself as a guide to convert out of box x727 to Linerage OS 14. I have converted 4 phones so far and I just wanted to leave a note for the next time. I have used the below method for going from 18s, 19s, and 21s. (I believe it also works for 23s. I think I have done it before.)
Steps below are for experts only with the usual warnings about bricking and warranty. (Always check for connection with devices command in both adb and fastboot - if you find adb working but not fastboot, change out the USB driver on you computer)
I wrote the steps down from my memory so let me know if you find something missing.
Files you need to hunt down :
emmc image
twrp image
los14 zip
ogapp zip
supersu zip
1) Boot up a new phone with no account and no wifi.
2) Set developer mode and enable USB debugging.
3) Connet USB and give permission on the phone.
4) adb reboot bootloader
5) fastboot flash aboot emm..xxx
5a)*reboot into fastboot by holding down power and vol- buttons.
6) fastboot oem unlock-go
7) fastboot flash recovery twrp..xxx
8) jump to recovery by pressing power and vol+
from twrp (if asked for password, just ignore)
9)make a back up if you would like to go back
10) mount system
11) format data (in the wipe section) and wipe cache and system
from adb
12) adb push los.zip, ogapp.zip, and supersu.zip to /sdcard/
from twrp
13) install los, ogapp, and supersu
14) boot system with no twrp install
Done. Phone should boot twice and will take some time to come up first time.
csrow said:
This is really a note to myself as a guide to convert out of box x727 to Linerage OS 14. I have converted 4 phones so far and I just wanted to leave a note for the next time. I have used the below method for going from 18s, 19s, and 21s. (I believe it also works for 23s. I think I have done it before.)
Steps below are for experts only with the usual warnings about bricking and warranty. (Always check for connection with devices command in both adb and fastboot - if you find adb working but not fastboot, change out the USB driver on you computer)
I wrote the steps down from my memory so let me know if you find something missing.
Files you need to hunt down :
emmc image
twrp image
los14 zip
ogapp zip
supersu zip
1) Boot up a new phone with no account and no wifi.
2) Set developer mode and enable USB debugging.
3) Connet USB and give permission on the phone.
4) adb reboot bootloader
5) fastboot flash aboot emm..xxx
6) fastboot oem unlock-go
7) fastboot flash recovery twrp..xxx
8) jump to recovery by pressing power and vol+
9) adb push los.zip, ogapp.zip, and supersu.zip to /sdcard/
from twrp (if asked for password, just ignore)
10)make a back up if you would like to go back
11) mount system
12) format data (in the wipe section) and wipe cache and system
13) install los, ogapp, and supersu
14) boot system with no twrp install
Done. Phone should boot twice and will take some time to come up first time.
Click to expand...
Click to collapse
Hey! hi.
Could you do a Step-by-Step Tutorial, with File etc. if its a Video tutorial, better! I have the X727 US with 19s Official Rom and I want Root/TWRP but any tutorial that I saw are weird.... I have fear to break my phone. Thanks!
kukuteku said:
Hey! hi.
Could you do a Step-by-Step Tutorial, with File etc. if its a Video tutorial, better! I have the X727 US with 19s Official Rom and I want Root/TWRP but any tutorial that I saw are weird.... I have fear to break my phone. Thanks!
Click to expand...
Click to collapse
If you have a specific question about a certain step or files, I can answer them for you but the guide is about as detailed as I want to make.
If you are comfortable with ADB, Fastboot, and TWRP, then the above guide should be detailed enough to get the job done.
If you are not, then I would advise not attempting the conversion since there is a good chance of bricking the phone.
And by the way, unlocking the bootloader will erase all the user data on the phone.
csrow said:
If you have a specific question about a certain step or files, I can answer them for you but the guide is about as detailed as I want to make.
If you are comfortable with ADB, Fastboot, and TWRP, then the above guide should be detailed enough to get the job done.
If you are not, then I would advise not attempting the conversion since there is a good chance of bricking the phone.
And by the way, unlocking the bootloader will erase all the user data on the phone.
Click to expand...
Click to collapse
Well, I Already did it!
Now I have Root / UBL/ TWRP.... Thank! :good:
kukuteku said:
Well, I Already did it!
Now I have Root / UBL/ TWRP.... Thank! :good:
Click to expand...
Click to collapse
Good for you. Enjoy.
This step is a little misleading
12) format data (in the wipe section) and wipe cache and system
You don't want to click the Format Data as it will erase the previously copied zip files (well you can copy them again). You should only do Advanced Wipe (System and Cache)
Joms_US said:
This step is a little misleading
12) format data (in the wipe section) and wipe cache and system
You don't want to click the Format Data as it will erase the previously copied zip files (well you can copy them again). You should only do Advanced Wipe (System and Cache)
Click to expand...
Click to collapse
Ah good point. Thanks.
Why the emmc image? Is it just for permanently unlocked bootloader? And if yes then is there a reason I would need unlocked bootloader after I flash recovery?
YouKittenMe said:
Why the emmc image? Is it just for permanently unlocked bootloader? And if yes then is there a reason I would need unlocked bootloader after I flash recovery?
Click to expand...
Click to collapse
Of 6 or 7 times I have tried oem unlock-go, only once did it work. Other times, I had to flash emmc first in order to unlock. You can try oem unlock-go first and see if it works for you.
The other thing to consider is if the flashed recovery will remain when you reboot without having flashing emmc first.
Good summary of steps. I found it was necessary to reboot the bootloader after flashing emmc_appsboot.mbn, though (as per this post: https://forum.xda-developers.com/showpost.php?p=71566961&postcount=203). Just did it on a new phone last night.
Redhawk2000 said:
Good summary of steps. I found it was necessary to reboot the bootloader after flashing emmc_appsboot.mbn, though (as per this post: https://forum.xda-developers.com/showpost.php?p=71566961&postcount=203). Just did it on a new phone last night.
Click to expand...
Click to collapse
Ah. good point. I will add it to the steps.
Glad it work out for you.
Joms_US said:
This step is a little misleading
12) format data (in the wipe section) and wipe cache and system
You don't want to click the Format Data as it will erase the previously copied zip files (well you can copy them again). You should only do Advanced Wipe (System and Cache)
Click to expand...
Click to collapse
You can Use OTG. I could not get a OTG, so I did flash Recovery 3.0.3 v6 because the 3.0.2 does not have support for Adb or MTP via Recovery. Once being on recovery your connect your movil to the PC and it appear like Drive, then you copy Your Rom, SU or anything else.