:silly: (I had a TA backup of 5.0.2 stock rom before proceeding, and supersu 2.49 beta.zip).
followed steps like:
1. I updated My Z3 to 5.1.1
2. then unlocked my bootloader
3. flashed cm12.1 boot.img
4. booted into cwm recovery using cm12.1 boot.img
5. flashed supersu 2.49 beta.zip
6. reflashed the 5.1.1 kernel back using stock 5.1.1 ftf and flashtool ( only kernel dont reflash system!!!!!!!!! )
7. successfully booted into rooted stock rom.
FROM HERE BOOTLOADER LOCK WITH TA PARTITION BEGINS
8. run backup TA and restore previous TA Backup of 5.0.2 and reboot the phone( usb debugging must be enabled).
9. Now the phone is a locked bootloader with TA installed of 5.0.2 (partially compatible kernel but locked bootloader with TA and DRM keys)
10. reflash the 5.1.1 kernel back using stock 5.1.1 ftf and flashtool. ( only kernel dont reflash system!!!!!!!!! )
11. yipee.. you got a rooted 5.1.1 stock rom with locked bootloader.
You then can install XZ Dual recovery and can reflash supersu beta 2.49.zip if you face problem in mounting system R/w.
Finally Done. :laugh::laugh:
If you didnt had TA backup and are on locked bootloader then you can revert back to 5.0.2 , root it using kingroot, backup TA and then follow steps from post.
https://drive.google.com/file/d/0B58yPhN4YGyiZkw4U09LaXducDg/view download stock ftf
http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133 supersu 2.49 beta
https://github.com/DevShaft/Backup-TA/releases backup TA
https://drive.google.com/file/d/0B3-13Z8Bw0WeczM1Y0Fpcm5XaHM/view?usp=sharing cm12.1 boot.img
please could you tell in detail
TechnoFreak750 said:
:silly: (I had a TA backup of 5.0.2 stock rom before proceeding, and supersu 2.49 beta.zip).
followed steps like:
1. I updated My Z3 to 5.1.1
2. then unlocked my bootloader
3. flashed cm12.1 boot.img
4. booted into cwm recovery using cm12.1 boot.img
5. flashed supersu 2.49 beta.zip
6. reflashed the 5.1.1 kernel back using stock 5.1.1 ftf and flashtool ( only kernel dont reflash system!!!!!!!!! )
7. successfully booted into rooted stock rom.
FROM HERE BOOTLOADER LOCK WITH TA PARTITION BEGINS
8. run backup TA and restore previous TA Backup of 5.0.2 and reboot the phone( usb debugging must be enabled).
9. Now the phone is a locked bootloader with TA installed of 5.0.2 (partially compatible kernel but locked bootloader with TA and DRM keys)
10. reflash the 5.1.1 kernel back using stock 5.1.1 ftf and flashtool. ( only kernel dont reflash system!!!!!!!!! )
11. yipee.. you got a rooted 5.1.1 stock rom with locked bootloader.
You then can install XZ Dual recovery and can reflash supersu beta 2.49.zip if you face problem in mounting system R/w.
Finally Done. :laugh::laugh:
If you didnt had TA backup and are on locked bootloader then you can revert back to 5.0.2 , root it using kingroot, backup TA and then follow steps from post.
Click to expand...
Click to collapse
TechnoFreak750 said:
https://drive.google.com/file/d/0B58yPhN4YGyiZkw4U09LaXducDg/view download stock ftf
http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133 supersu 2.49 beta
https://github.com/DevShaft/Backup-TA/releases backup TA
https://drive.google.com/file/d/0B3-13Z8Bw0WeczM1Y0Fpcm5XaHM/view?usp=sharing cm12.1 boot.img
Click to expand...
Click to collapse
hello friend
can you tell me more detail how you have root your z3 caause i am a new user and i dont really get how you do nummer 3 flash cm12.1 boot img and how to boot to CWM. My phone is unlockbootloader
thank you very much
mangyi said:
hello friend
can you tell me more detail how you have root your z3 caause i am a new user and i dont really get how you do nummer 3 flash cm12.1 boot img and how to boot to CWM. My phone is unlockbootloader
thank you very much
Click to expand...
Click to collapse
Brother it is critical method for advanced users. you should wait till exploits arrives for the device. or else you can go for pre rooted firmwares.
Related
Usage is for people NOT on LXB22.99-16 who want to try stage fright patch but cant get it OTA i.e LXB22.46-28
[TWRP] Back up of LXB22.99-16.3 [5.0.2 with STAGE FRIGHT PATCH] This installs via restore function in TWRP 2.8.5.0
this is a fresh installed (before setup) of LXB22.99-16.3 (Build number) system version 22.56.3.TITAN Build date WED 26th AUGUST 2015 00:26:33 CDT
BACKUP CONTAINS /system and boot only -no PDS, Cache or Data folders
made with TWRP 2.8.5.0 as version .6 and .7 just hang my phone.
TWRP Backup of CLEAN LXB22.99-16.3
make a FULL BACKUP via TWRP of your phone before you try to use this.
Stock Recovery LXB22.99-16.3
This is stock recovery to Flash back via fastboot method to remove custom recoveries in AP FASTBOOT MODE
Code:
fastboot flash recovery recovery.img
reefuge said:
This is stock recovery to Flash back via fastboot method to remove custom recoveries in AP FASTBOOT MODE
Code:
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
Thank you for making this guide...even i wanted to make a guide for kitkat restore but didnt..lazy..lol..just one ques i am curious..how did u made backup of stock recovery because the only way to root is to flash twrp n den install super user??
Naman rana said:
Thank you for making this guide...even i wanted to make a guide for kitkat restore but didnt..lazy..lol..just one ques i am curious..how did u made backup of stock recovery because the only way to root is to flash twrp n den install super user??
Click to expand...
Click to collapse
temporary boot to TWRP not install, then root with supersu v2.46 - install flashify (paid) and backup recovery to googledrive - hang on that not how i did it lol (might work)
I used browser explorer to make it from restore from boot.img.bak you have to change .bak to .p and alter permissions - theres a guide on xda
Hi guys,
I know how rooting and flashing works but I've been using HTC devices since the nexus one so there are some differences I just want to make sure of. I got my 6P yesterday, I unlocked the bootloader and flashed TWRP. I wanted to gain root but Im not sure about flashing the modified boot img and the vendor thing.
My build was K but I got an OTA before unlocking the bootloader which updated to L. Anyway I don't know why I just formatted every thing in TWRP instead of the factory reset and I lost the OS X_X I tried to restore my nandroid with no luck. Anyway I got the factory img (MDB08L) from google dev and flashed used 'flash-all.bat' in the bootloader, the phone is running fine right now but I would like to update to the latest firmware 6.0.1+root since im not getting any OTA.
I would like to install CleanCore(6.0.1), the guide is
-> Flash Bootloader & Radio (as needed)
-> Flash CleanCore
-> Flash Modified Boot (named angler-xxxxxx-boot.zip)
-> Flash SuperSU or SuperSU Beta
-> Flash latest vendor.img (ROM & Vendor builds need to match!)
1. Should I use MMB29M factory img and flash 'flash-all.bat' like I did with the L build for the first step? then I flash new recovery?
-Flashing the rom through the recovery
2. so after I flash the rom I boot into the bootloader and flash the modified boot img with fastboot flash boot boot.img right?
3. then I go back to recovery and flash SU which I should download before.
4. vendor img is flashed in recovery too or fastboot?
Sorry for the hassle I just want to make sure.
One more thing, in this guide http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928 at step 9, OP flashes the factroy img files separately (bootloader,radio,etc), is there a problem with using flashall.bat?
Thanks in advance and sorry for my noobish questions.
If you want to keep your data while doing this process, then yes, using the flash-all.bat is a problem. However, if you are fine with reverting back to stock(where you have to activate Android and reinstall all of your apps) then the flash-all.bat file is just fine.
That guide in the thread you linked walks you through how to update without losing data. After doing all of that, you'll just need to install TWRP and SuperSU again(do the latest systemless supersu though)
Enddo said:
If you want to keep your data while doing this process, then yes, using the flash-all.bat is a problem. However, if you are fine with reverting back to stock(where you have to activate Android and reinstall all of your apps) then the flash-all.bat file is just fine.
That guide in the thread you linked walks you through how to update without losing data. After doing all of that, you'll just need to install TWRP and SuperSU again(do the latest systemless supersu though)
Click to expand...
Click to collapse
Thanks for the help.
I have rooted my stock rom and gained root. I also installed exposed so i'll be fine without a custom rom for some time. There has been a report that some cameras aren't working on 6.0.1 with root so I'll wait for a while.
Thanks again
mr.dj26 said:
Thanks for the help.
I have rooted my stock rom and gained root. I also installed exposed so i'll be fine without a custom rom for some time. There has been a report that some cameras aren't working on 6.0.1 with root so I'll wait for a while.
Thanks again
Click to expand...
Click to collapse
I'm pretty sure those reports are because they used the SuperSU root method that didn't auto patch the boot image(which is the version(or two versions) behind the current version of SuperSU). This is happening because people are updating to 6.0.1, but the patched SuperSU boot image is for 6.0 and the 6.0 boot image conflicts with 6.0.1
As long as you use the latest version of SuperSU then you won't have any trouble with the camera
Enddo said:
I'm pretty sure those reports are because they used the SuperSU root method that didn't auto patch the boot image(which is the version(or two versions) behind the current version of SuperSU). This is happening because people are updating to 6.0.1, but the patched SuperSU boot image is for 6.0 and the 6.0 boot image conflicts with 6.0.1
As long as you use the latest version of SuperSU then you won't have any trouble with the camera
Click to expand...
Click to collapse
Thanks for the info
Guys today I came here with a simplified rooting method for titan running marshmallow 6.0 that doesn't need boot.img modification
Note -You need to have bootloader unlocked and custom recovery like twrp installed on your device before proceeding
Unlock bootloader here
Flash the custom recovery of your choice using auto flash script included in separate attachment
1) Download and rename recovery file as recovery.img and put into the folder of auto flash script.
2) Reboot your device into bootloader mode and connect to PC using USB cable [You shold have latest motorola device manager installed and your device should indicate usb connected on bootloader screen]
3) Now open 'auto flash recovery script' folder and run auto_flash_recovery.bat file
4) Now custom recovery is installed on your device
Steps for rooting-
1. Download BETA-SuperSU-v2.62-3-20151211162651.zip and place it in root of your internal sd card (other supersu version does not work on titan running official marshmallow)
2. flash BETA-SuperSU-v2.62-3-20151211162651.zip using twrp recovery
3. wipe delvick cache and cache (optional)
4. reboot device
5. If you want to use stable super su version i.e. UPDATE-SuperSU-v2.65-20151226141550.zip or any version like any supersu beta except BETA-SuperSU-v2.62-3. download and flash it over BETA-SuperSU-v2.62 after rooting.
6. If you have previously rooted your MM running device using SuperSu-v2.52 with modified boot.img, You need to flash stock boot.img first and reboot then follow this guide (step 1-5)
#BETA-SuperSU-v2.62 will do all required modification by its own script automatically.
Note- Dnt flash any other supersu version or SuperSU-v2.65 alone on unrooted device. you will get bootloop. Do a backup of your rom before any rooting operation.
In case if u stuck on bootloop flash this update UnSu script via twrp, wipe delvick and cache and reboot. this script will remove any supersu file installed in your device thus fully unrooting ur device that will recover you from bootloop
Thank you! It's working!
Perfect, It's working!
Working,great
Sent from my XT1068 using Tapatalk
Where can we get the stock boot.img for Marshmallow?
If u r running stock mm, then ur boot.img is also stock.
i think it's not necessary to root again if i already rooted with modified boot image does that make any difference
mandar91 said:
i think it's not necessary to root again if i already rooted with modified boot image does that make any difference
Click to expand...
Click to collapse
It is recommended to use stock boot.img
gauravrai said:
It is recommended to use stock boot.img
Click to expand...
Click to collapse
BUT currently i m on cm 13
Failed Root with XT1064 6.0
Everything ran smoothly installing the zip from TWRP, but on reboot: no SuperSU; no root. Now warnings or errors came up in the TWRP text during root.
MotoG 2014 XT1064
System: 24.41.34 titan_retuaws.retuaws.en.US retus
Kernel version 3.4.42-gef77327
TWRP-3.0.0-0-titan
Installed zip: BETA-SuperSU-v2.62-3-20151211162651.zip
Device is unlocked. Status Code 3
Update to 6.0 was with OTA after flashing the stock rom using XT1064_TITAN_RETUAWS_5.0.2_LXB22.99-24.12_cid9_CFC.xml.
The phone was previously 5.0.2 Rooted.
I did not lock the bootloader during the process.
The OTA to 6.0 went smoothly.
Followed the above instructions to the letter....
The only thing odd I did was uninstall the SuperSU App on the phone before flashing TWRP and starting this Root operation.
Has anyone gotten this to work on XT1064? Or any other root method on stock 6.0 and XT1064
fidorulz said:
Has anyone gotten this to work on XT1064? Or any other root method on stock 6.0 and XT1064
Click to expand...
Click to collapse
This will work on all Moto devices running stock marshmallow.
Root Moto G2 running on Official 6.0 Android Marshmallow Without (modified boot image)
https://youtu.be/9_9vkJvzWcU
Every time i remove system apps it boot loop any work around for this in marshmallow.. In lollipop removing system apps can normally booted up without any problem..
I successfully rooted my stock marshmallow on XT1068. I had softbricked it previously by using a newer version os SuperSu (I hadn't located this post yet, so I didn't recover from it with you script. I reflashed stock).
So, many many thanks.
In the end, my successful steps were
- flashboot flash recovery twrp-3.0.2-0-titan.img
- reboot into recovery
- install BETA-SuperSU-v2.62-3-20151211162651.zip from TWRP
- wipe dalvik & cache
- reboot device
wildingol said:
I successfully rooted my stock marshmallow on XT1068. I had softbricked it previously by using a newer version os SuperSu (I hadn't located this post yet, so I didn't recover from it with you script. I reflashed stock).
So, many many thanks.
In the end, my successful steps were
- flashboot flash recovery twrp-3.0.2-0-titan.img
- reboot into recovery
- install BETA-SuperSU-v2.62-3-20151211162651.zip from TWRP
- wipe dalvik & cache
- reboot device
Click to expand...
Click to collapse
Now over 2.62 supersu u can also flash any upgraded version like stable or any latest beta.
Sent from my XT1068 using XDA-Developers mobile app
Confirmed working on TWRP 3.0.0.1, stock Marshmallow 6.0 from OTA updates. Every other SuperSU got stuck on unlocked bootloader screen.
Thanks!
gauravrai said:
Guys today I came here with a simplified rooting method for titan running marshmallow 6.0 that doesn't need boot.img modification
Note -You need to have bootloader unlocked and custom recovery like twrp installed on your device before proceeding
Unlock bootloader here
Flash the custom recovery of your choice using auto flash script included in separate attachment
1) Download and rename recovery file as recovery.img and put into the folder of auto flash script.
2) Reboot your device into bootloader mode and connect to PC using USB cable [You shold have latest motorola device manager installed and your device should indicate usb connected on bootloader screen]
3) Now open 'auto flash recovery script' folder and run auto_flash_recovery.bat file
4) Now custom recovery is installed on your device
Steps for rooting-
1. Download BETA-SuperSU-v2.62-3-20151211162651.zip and place it in root of your internal sd card (other supersu version does not work on titan running official marshmallow)
2. flash BETA-SuperSU-v2.62-3-20151211162651.zip using twrp recovery
3. wipe delvick cache and cache (optional)
4. reboot device
5. If you want to use stable super su version i.e. UPDATE-SuperSU-v2.65-20151226141550.zip or any version like any supersu beta except BETA-SuperSU-v2.62-3. download and flash it over BETA-SuperSU-v2.62 after rooting.
6. If you have previously rooted your MM running device using SuperSu-v2.52 with modified boot.img, You need to flash stock boot.img first and reboot then follow this guide (step 1-5)
#BETA-SuperSU-v2.62 will do all required modification by its own script automatically.
Note- Dnt flash any other supersu version or SuperSU-v2.65 alone on unrooted device. you will get bootloop. Do a backup of your rom before any rooting operation.
In case if u stuck on bootloop flash this update UnSu script via twrp, wipe delvick and cache and reboot. this script will remove any supersu file installed in your device thus fully unrooting ur device that will recover you from bootloop
Click to expand...
Click to collapse
VIDEO TUTORIAL:-
https://www.youtube.com/watch?v=9_9vkJvzWcU
Work !
---------- Post added at 12:43 AM ---------- Previous post was at 12:42 AM ----------
Work thanks
i Tried this on Xt1072 Moto G 2nd Gen 2014 LTE and had to use the UnSu first as per the instructions and for the reasons described in red. I was also stuck in bootloader with that horrible message that says your bootloader is now unlocked! Now the issue is I seem to be stuck on the Motorola hand stitched by peter crawley boot screen? I saw someone aske dhow long this lasts? I had to use an OTG usb flash drive to get my files on to the damn phone for some strange reason phone and pc having massive communication issues, not playing very nicely with each other????? wtf? anyway I got okays and successful messages when in TWRP 2.8.5.0 I just dont understand why there seems to be such a huge problem with getting this f"£$%^&*g phone sorted.
Nexus 5 rooted and flashed with the beautiful elemental x kernel, why cant we get elementalx for moto g? its absolute genius! now someone tel me what the hell is going on here, when will I ever have success with this damn phone? I hate bloat and it only has 8GB plus the sd card which is configured as internal storage, could this be what the problem is?
Hi,
I try to root my S7 4g x25 but i need a twrp flashable zip of the stock rom
please can anyone help me find one or create one from my unrooted phone ?
i can unlock bootloader and install twrp but when i do this, i am no longer able to boot so i think i must flash an image with twrp but i don't have flashable image of stock ROM
i precise i have stock ROM in Android Nougat 7.1.1
wyrlok said:
Hi,
I try to root my S7 4g x25 but i need a twrp flashable zip of the stock rom
please can anyone help me find one or create one from my unrooted phone ?
i can unlock bootloader and install twrp but when i do this, i am no longer able to boot so i think i must flash an image with twrp but i don't have flashable image of stock ROM
i precise i have stock ROM in Android Nougat 7.1.1
Click to expand...
Click to collapse
Hello, YOU MUST FLASH TWRP THROUGH FLASHTOOL AND THEN ( very important) you MUST BE REMOVED THE USB CABLE and finally YOU'll ACCESS TO THE TWRP.
Hi
My Oneplus 5 is rooted (OOS 5.0.1) + recovery is TWRP now.
I would like to get back to Stock OOS without root and stock recovery?
Can I get method for this ?
THX
Hello !
You must flash full Zip OOS 5.0.1 and stock recovery file, both on TWRP. Reboot and everything will be OK.
Here is full Zip OOS 5.0.1 : http://otafsg.h2os.com/patch/amazon...5Oxygen_23_OTA_028_all_1801031502_04d7cc5.zip
Here is stock recovery : http://oxygenos.oneplus.net.s3.amazonaws.com/OP5_recovery.img
To flash stock recovery, don't forget to choose flash image.
Thank you so much.
Can I after these relock the bootloader?
THX
So
1 Flash 5.0.1 OOS
2 Flash Stock Recovery
Now bootlop all the time!
The solution!
1: TWRP sideload
2: Flash ROM by ADB
3: Reboot ....USB debugging etc
4: Fastboot.....relock bootloader
Done