Hi Everyone! I'm not a Dev (yet), so this is one of my contributions to the Sprint community
This is a DIY root method. By doing it yourself, you will learn some basic knowledge about using cmd windows, using ADB, and using fastboot. All files are in the
Unlock your bootloader - www.htcdev.com Follow the instructions at HTC-Dev to unlock your bootloader.
Flash TWRP Recovery - (refer to the Read Me First Text on how to fastboot flash TWRP Recovery)
Flash SuperSU - (copy to sdcard and flash from TWRP; v2.48 is the first working version)
Using this method will NOT give you S-OFF, but it will help you unlock your bootloader (HTC-DEV method), flash a custom recovery (TWRP for now), and install the Superuser app of your choice.
What's included:
Read Me Text (Instructions, ADB commands, and all the things)
ADB Tool
Latest HTC Drivers v4.2.0.001 and HTC BMP USB Drivers v1.0.5375(32 and 64 bit versions)
TWRP openrecovery v2.8.6.0
SuperSU.apk v2.48
I would like to thank:
TeamWin (for TWRP)
Captain_Throwback for his version of TWRP
Chainfire (for SuperSU)
The Incredible XDA Community
Root Files Below
AFH
DropBox Mirror
Frequently Asked Questions - HTC One-M9-Sprint(M9_Hima)
Disclaimer:
Code:
* Standard disclaimer:
* Your warranty is now void. Use at your own risk.
* In other words: It is your choice to use these files.
* I am not responsible for any damage or problems you may have!
I suggest extracting it to a folder on your desktop so you can find it and start by reading the Read Me Text.
I will update this thread as updates become available.
Driver problems- get HTC Sync Manager HERE
Latest version of SuperSU can be found here: http://download.chainfire.eu/735/SuperSU/BETA-SuperSU-v2.48.zip
If you are having issues with the "Official" TWRP in the folder I recommend this one HERE
Please see the next post (post #3) on how to take an OTA
The first thing EVERYONE should do prior to rooting or anything else that modifies system is DO A NANDROID BACKUP!!! You must also use the latest TWRP, preferably @Captain_Throwback beta version.
On the M9, any changes to system will cause OTAs to fail, even using an older version of TWRP (which mounts the system RW), will cause OTAs to fail. The latest version of TWRP is RO. Captain_Throwback has taken this to the next level by implementing auto detection, if it detects your system is untouched, it is RO allowing you to do a clean backup. If it detects system has been modified, it will allow you to mount system as RW just like in the past.
for reference...
Captain_Throwback said:
Well, the bad news is that rooting will break the ability to take an OTA. In fact, ANY change to the system block (even just mounting it as read/write in recovery) will cause an OTA to fail. This is confirmed by the updater-script:
Code:
(range_sha1("/dev/block/bootdevice/by-name/system", "2,0,1") == "261d26028677f988c9e174a26438698d3049a1f3") || (range_sha1("/dev/block/bootdevice/by-name/system", "2,0,1") == "80a8e88fcc1c59e572557c09d58b46a060ce9313") || [B]abort("/dev/block/bootdevice/by-name/system has been remounted R/W; reflash device to reenable OTA updates")[/B];
if range_sha1("/dev/block/bootdevice/by-name/system", "2,0,1146880") == "1396016f0a12721094d8b414b2f9d2b075409b3d" then
ui_print("Patching system image...");
show_progress(0.900000, 0);
block_image_update("/dev/block/bootdevice/by-name/system", package_extract_file("system.transfer.list"), "system.new.dat", "system.patch.dat");
else
(range_sha1("/dev/block/bootdevice/by-name/system", "2,0,1146880") == "2a40a25d6999821224a246129bd31fe2e6945272") ||
[B] abort("system partition has unexpected contents")[/B];
endif;
Notice that it's confirming the checksum of the entire system block device. The first thing everyone will need to do before flashing ANYTHING is make a backup of system.
TWRP for the M9 is set up to mount system as read-only to prevent any checksum changes. Any backup taken of system is done via dd, which means the backup is done in image format and should exactly match the original checksum if/when restored.
Click to expand...
Click to collapse
To restore your clean system backup to accept OTAs, you must use fastboot. If you are S-ON, you must be in download mode.
-copy your clean system.emmc.win to your adb/fastboot folder on your pc
-boot into download mode
-use cmd fastboot flash system system.emmc.win
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
if using Captain_Throwbacks beta TWRP, now when you boot into TWRP, it should detect an untouched system, you can verify this by making sure TWRP does not show "system" in the Mount menu.
If you have installed a pre-2.8.6.0 TWRP or forgot to do a backup or it's corrupted or whatever, @solver404 has provided a clean M9_stock_twrp_boot_system.zip
for reference on required fastboot...
Captain_Throwback said:
No. You can't just restore the backup. You have to fastboot flash the system image.
Click to expand...
Click to collapse
Captain_Throwback said:
The reason you can't just restore the stock system while in TWRP is because the system in TWRP is mounted read-write. As soon as you restore it, it'll be compromised again. So, you have to flash the system image while in fastboot to ensure it keeps its integrity. Then if you reboot into TWRP, system will be mounted read-only again. That'll allow you to take a full system image backup again after taking the OTA.
Click to expand...
Click to collapse
I think this needs a little more detail you can refer to my thread if you would like
Alright, post #1 has been updated with the links to a zip containing everything necessary (TWRP, superSU, etc) to get your device rooted, and get a custom recovery. I'm still working on the OPs, but it should be (mostly) right, and please look at post #3 by @OMJ on how to restore a backup, and what to do if you'd like to take an OTA
OMJ said:
The first thing EVERYONE should do prior to rooting or anything else that modifies system is DO A NANDROID BACKUP!!! You must also use the latest TWRP, preferably @Captain_Throwback beta version.
On the M9, any changes to system will cause OTAs to fail, even using an older version of TWRP (which mounts the system RW), will cause OTAs to fail. The latest version of TWRP is RO. Captain_Throwback has taken this to the next level by implementing auto detection, if it detects your system is untouched, it is RO allowing you to do a clean backup. If it detects system has been modified, it will allow you to mount system as RW just like in the past.
for reference...
To restore your clean system backup to accept OTAs, you must use fastboot. If you are S-ON, you must be in download mode.
-copy your clean system.emmc.win to your adb/fastboot folder on your pc
-boot into download mode
-use cmd fastboot flash system system.emmc.win
if using Captain_Throwbacks beta TWRP, now when you boot into TWRP, it should detect an untouched system, you can verify this by making sure TWRP does not show "system" in the Mount menu.
If you have installed a pre-2.8.6.0 TWRP or forgot to do a backup or it's corrupted or whatever, @solver404 has provided a clean M9_stock_twrp_boot_system.zip
for reference on required fastboot...
Click to expand...
Click to collapse
If one would rather just keep stock recovery, but have root for apps like Wifi Tether Router, would the below steps work?
1) Unlock with HTCDev
2) Only boot into TWRP (not flash it as permanent recovery): Fastboot boot twrp.img
3) Once booted into TWRP, install supersu
Then should OTA updates work, after which you only have to repeat steps 2 & 3?
My intent is to just get root access for apps like WiFi Tether Router.
ReproOne said:
If one would rather just keep stock recovery, but have root for apps like Wifi Tether Router, would the below steps work?
1) Unlock with HTCDev
2) Only boot into TWRP (not flash it as permanent recovery): Fastboot boot twrp.img
3) Once booted into TWRP, install supersu
Then should OTA updates work, after which you only have to repeat steps 2 & 3?
My intent is to just get root access for apps like WiFi Tether Router.
Click to expand...
Click to collapse
only way to know is to try...I've used fastboot boot in the past, not sure if it still works.
if it doesn't just do this:
-unlock
-flash twrp
-BACKUP!!!
-flash SuperSu
-flash stock recovery
this is actually better, as you want a good backup b4 modifying /system
OMJ said:
only way to know is to try...I've used fastboot boot in the past, not sure if it still works.
if it doesn't just do this:
-unlock
-flash twrp
-BACKUP!!!
-flash SuperSu
-flash stock recovery
this is actually better, as you want a good backup b4 modifying /system
Click to expand...
Click to collapse
Do you have a link for the stock recovery. The one in the post above does not appear to be available yet? I'm getting my M9 over the weekend, and I have used the option to just boot to TWRP on the M8. I was hoping someone may have tried that on the M9.
ReproOne said:
Do you have a link for the stock recovery. The one in the post above does not appear to be available yet? I'm getting my M9 over the weekend, and I have used the option to just boot to TWRP on the M8. I was hoping someone may have tried that on the M9.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=3066720 ?
ReproOne said:
Do you have a link for the stock recovery. The one in the post above does not appear to be available yet? I'm getting my M9 over the weekend, and I have used the option to just boot to TWRP on the M8. I was hoping someone may have tried that on the M9.
Click to expand...
Click to collapse
https://www.androidfilehost.com/?fid=95916177934552130
pull the recovery from that zip
nickmilla15 said:
http://forum.xda-developers.com/showthread.php?t=3066720
Click to expand...
Click to collapse
That has TWRP. I was asking for the actual stock recovery.img if one wanted to put that back as recovery. Did I miss something?
ReproOne said:
That has TWRP. I was asking for the actual stock recovery.img if one wanted to put that back as recovery. Did I miss something?
Click to expand...
Click to collapse
Yeah, you missed the fact that I'm an idiot today haha. I'm really sorry. I guess I forgot what stock recovery meant ?
nickmilla15 said:
Yeah, you missed the fact that I'm an idiot today haha. I'm really sorry. I guess I forgot what stock recovery meant
Click to expand...
Click to collapse
I believe you are far from an idiot!
I've been reading through all posts before getting my M9 tomorrow.
I intend to unlock the bootloader and then first try to just boot into the newest beta of twrp to install supersu. If that does not work, I am trying to plan ahead and either learn how to backup recovery.img or find the stock of it. Can you assist with that, please?
I basically want root with the ability to accept OTA updates as normal.
ReproOne said:
I believe you are far from an idiot!
I've been reading through all posts before getting my M9 tomorrow.
I intend to unlock the bootloader and then first try to just boot into the newest beta of twrp to install supersu. If that does not work, I am trying to plan ahead and either learn how to backup recovery.img or find the stock of it. Can you assist with that, please?
I basically want root with the ability to accept OTA updates as normal.
Click to expand...
Click to collapse
Sending ya a PM ?
nickmilla15 said:
Sending ya a PM
Click to expand...
Click to collapse
I have replied. Thank you!
OMJ said:
The first thing EVERYONE should do prior to rooting or anything else that modifies system is DO A NANDROID BACKUP!!! You must also use the latest TWRP, preferably @Captain_Throwback beta version.
On the M9, any changes to system will cause OTAs to fail, even using an older version of TWRP (which mounts the system RW), will cause OTAs to fail. The latest version of TWRP is RO. Captain_Throwback has taken this to the next level by implementing auto detection, if it detects your system is untouched, it is RO allowing you to do a clean backup. If it detects system has been modified, it will allow you to mount system as RW just like in the past.
for reference...
To restore your clean system backup to accept OTAs, you must use fastboot. If you are S-ON, you must be in download mode.
-copy your clean system.emmc.win to your adb/fastboot folder on your pc
-boot into download mode
-use cmd fastboot flash system system.emmc.win
if using Captain_Throwbacks beta TWRP, now when you boot into TWRP, it should detect an untouched system, you can verify this by making sure TWRP does not show "system" in the Mount menu.
If you have installed a pre-2.8.6.0 TWRP or forgot to do a backup or it's corrupted or whatever, @solver404 has provided a clean M9_stock_twrp_boot_system.zip
for reference on required fastboot...
Click to expand...
Click to collapse
When i use this flash system method via fastboot in download mode using the instructions provided command prompt looks like its going to start the process but then it just sits there. See screenshot
deakelem said:
When i use this flash system method via fastboot in download mode using the instructions provided command prompt looks like its going to start the process but then it just sits there. See screenshot
Click to expand...
Click to collapse
mine did exactly as you're describing. i had to let it sit for something like 5-10min (i didnt time it), and then it finally progressed. if it doesnt go anywhere for you, make sure you've updated to the newest sdk-tools
deakelem said:
When i use this flash system method via fastboot in download mode using the instructions provided command prompt looks like its going to start the process but then it just sits there. See screenshot
Click to expand...
Click to collapse
So i followed the instructions and flashed the untouched system to my phone but when i attempt to take todays ota it fails and says something like reenabled OTA system has been r/w...
I factory reset and everything too and it still does that
Im using the stock recovery but do i need to relock my bl?
Ill try to get a pic of the error once it happens again.. cause it will
deakelem said:
So i followed the instructions and flashed the untouched system to my phone but when i attempt to take todays ota it fails and says something like reenabled OTA system has been r/w...
I factory reset and everything too and it still does that
Im using the stock recovery but do i need to relock my bl?
Ill try to get a pic of the error once it happens again.. cause it will
Click to expand...
Click to collapse
you shouldn't have to relock. i didn't relock mine, and i just finished updating the new OTA about 10 minutes ago. all i did was fastboot flash the original system image, fastboot flash the stock recovery, and then do the OTA.
hsmith1514 said:
you shouldn't have to relock. i didn't relock mine, and i just finished updating the new OTA about 10 minutes ago. all i did was fastboot flash the original system image, fastboot flash the stock recovery, and then do the OTA.
Click to expand...
Click to collapse
its working now thanks! i was just in a rush and didnt wait for the system to flash all the way like you said it took nearly 10 mins. OTA looks like its good so far
---------- Post added at 04:18 PM ---------- Previous post was at 04:10 PM ----------
hsmith1514 said:
you shouldn't have to relock. i didn't relock mine, and i just finished updating the new OTA about 10 minutes ago. all i did was fastboot flash the original system image, fastboot flash the stock recovery, and then do the OTA.
Click to expand...
Click to collapse
well i spoke too soon.. the ota progressed much further but then eventually said system has unexpected contexts.. I flashed untouch system and rebooted and took OTA thats it. So idk why it would say that
Related
Hi,
I recently recovered from a soft brick by reflashing my phone using odin back to stock using VRUAMDK_NoWipe.tar.md5. I was able to successfully root using motochopper, but the bootloader is locked. When I first got the phone, I used GooManager to install twrp so I could install a custom rom. But now, GooManager 404s when trying to download openrecovery-twrp-2.6.3.1-jfltevzw.img.
So, I manually downloaded openrecovery-twrp-2.6.3.1-jfltevzw.img, copied it to the phone (at /storage/sdcard0/r.img), opened the terminal emulator app, hopped to root, and dd'd it over the recovery partition manually.
Code:
su
cd /storage/sdcard0
dd if=/dev/block/mmcblk0p21 of=r.orig.img # created backup
dd if=r.img of=/dev/block/mmcblk0p21
md5sum r.img
md5sum /dev/block/mmcblk0p21 # curiously, these didn't match on repeated attempts; even after reboot
As the comments say above, I noticed that the md5sums of r.img and /dev/block/mmcblk0p21 after the dd didn't match, even after numerous attempts. Note: when I eventually dd'ed the original contents of the recovery partition back, the md5sums of r.orig.img and /dev/block/mmcblk0p21 matched fine.
When I rebooted with the twrp image copied to my recovery partition, and tried to enter recovery mode, I saw this message:
System software not authorized by Verizon Wireles has been found on your phone. Please turn off your phone and go to the nearest Verizon Wireless store for help.
Click to expand...
Click to collapse
What's the cause of this message? Any ideas on how I can get twrp on my phone so I can install a custom rom again?
I've also looked into fastboot, but I couldn't get `fastboot devices` to show my phone (though `adb devices` showed my phone fine)--even after uninstalling samsung drivers, rebooting, and reinstalling the drivers.
PS. This all happened due to soft brick, which occured because PAC crashed immediately when I began to encrypt the contents of the phone. Is this a known issue?
Phone Info:
Verizon Android Galaxy S4 == jfltevzwm == SCH-I545
Flash: VRUAMDK_NoWipe.tar.md5
What firmware version was the phone on before it got bricked?
JeeperDon said:
What firmware version was the phone on before it got bricked?
Click to expand...
Click to collapse
I'm not 100% sure. It was either pac_jfltevzw-nightly-20130706.zip or pac_jfltevzw-milestone.1.RC1.zip
fedcba098 said:
I'm not 100% sure. It was either pac_jfltevzw-nightly-20130706.zip or pac_jfltevzw-milestone.1.RC1.zip
Click to expand...
Click to collapse
Think he's asking if you were already running MDK build with a custom recovery?!
Sent from my SCH-I545 using XDA Premium 4 mobile app
Mistertac said:
Think he's asking if you were already running MDK build with a custom recovery?!
Click to expand...
Click to collapse
Before I flashed it with pac? I'm not sure what the initial firmware was. I *do* know my initial firmware was before ME7, so I chose MDK because it was 1 version before ME7. Does it need to be put back to the same firmware as when I bought it? If so, how do I find out the initial version?
And, yes, I had a custom recover (twrp) on my phone before the soft brick.
fedcba098 said:
Hi,
I recently recovered from a soft brick by reflashing my phone using odin back to stock using VRUAMDK_NoWipe.tar.md5. I was able to successfully root using motochopper, but the bootloader is locked. When I first got the phone, I used GooManager to install twrp so I could install a custom rom. But now, GooManager 404s when trying to download openrecovery-twrp-2.6.3.1-jfltevzw.img.
So, I manually downloaded openrecovery-twrp-2.6.3.1-jfltevzw.img, copied it to the phone (at /storage/sdcard0/r.img), opened the terminal emulator app, hopped to root, and dd'd it over the recovery partition manually.
Code:
su
cd /storage/sdcard0
dd if=/dev/block/mmcblk0p21 of=r.orig.img # created backup
dd if=r.img of=/dev/block/mmcblk0p21
md5sum r.img
md5sum /dev/block/mmcblk0p21 # curiously, these didn't match on repeated attempts; even after reboot
As the comments say above, I noticed that the md5sums of r.img and /dev/block/mmcblk0p21 after the dd didn't match, even after numerous attempts. Note: when I eventually dd'ed the original contents of the recovery partition back, the md5sums of r.orig.img and /dev/block/mmcblk0p21 matched fine.
When I rebooted with the twrp image copied to my recovery partition, and tried to enter recovery mode, I saw this message:
What's the cause of this message? Any ideas on how I can get twrp on my phone so I can install a custom rom again?
I've also looked into fastboot, but I couldn't get `fastboot devices` to show my phone (though `adb devices` showed my phone fine)--even after uninstalling samsung drivers, rebooting, and reinstalling the drivers.
PS. This all happened due to soft brick, which occured because PAC crashed immediately when I began to encrypt the contents of the phone. Is this a known issue?
Phone Info:
Verizon Android Galaxy S4 == jfltevzwm == SCH-I545
Flash: VRUAMDK_NoWipe.tar.md5
Click to expand...
Click to collapse
You didn't loki the recovery. Thats why its failing.
Surge1223 said:
You didn't loki the recovery. Thats why its failing.
Click to expand...
Click to collapse
The recovery you download right from the TWRP website is already loki'd. I downloaded it the other day and followed the same instructions (exact ones posted on TWRP website) and all was fine with me.
The loki thing is not your problem here, unfortunately.
roboots21 said:
The recovery you download right from the TWRP website is already loki'd. I downloaded it the other day and followed the same instructions (exact ones posted on TWRP website) and all was fine with me.
The loki thing is not your problem here, unfortunately.
Click to expand...
Click to collapse
I disagree. I couldn't install CyanogenMod though twrp because I wasn't lokied so I had to install and loki cwm then I was able to install CyanogenMod
Sent from my SCH-I545 using xda app-developers app
reinaldistic said:
I disagree. I couldn't install CyanogenMod though twrp because I wasn't lokied so I had to install and loki cwm then I was able to install CyanogenMod
Sent from my SCH-I545 using xda app-developers app
Click to expand...
Click to collapse
The TWRP image is loki'd already .. Check their site. I did EXACTLY as he is describing yesterday and it worked perfectly .. Loki is not the issue.
Sent from my SCH-I545 using Tapatalk
---------- Post added at 12:56 PM ---------- Previous post was at 12:52 PM ----------
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my SCH-I545 using Tapatalk
Is there any way you can get TWRP 2.5 instead of 2.6? I remember reading that there were people having issues running 2.6.
I thought with a locked bootloader you aren't able to Oden downgrade?
Correct... Unless your original baseband is MDK, and you have never taken an OTA, you cannot get MDK. Once you take an OTA, you are stuck with whatever baseband that OTA was.
What I was saying was for him to try an eariler version of TWRP.
Yay! I got in TWRP!!
I downloaded loki-jfattvzw.zip, which contained loki_patch, and a few scripts. I deleted the recovery.img file that came with the loki zip, and renamed openrecovery-twrp-2.5.0.0-jfltexx.img to recovery.zip. Then I executed install-cwm.cmd, which `adb push`ed the files to the phone, and executed a script that loki'd my twrp recovery.img file using the aboot partition on my phone (it used dd and stuff).
Anyway, I'm now happily in twrp, ready to install PAC again. Thanks for your support!!
fedcba098 said:
Yay! I got in TWRP!!
I downloaded loki-jfattvzw.zip, which contained loki_patch, and a few scripts. I deleted the recovery.img file that came with the loki zip, and renamed openrecovery-twrp-2.5.0.0-jfltexx.img to recovery.zip. Then I executed install-cwm.cmd, which `adb push`ed the files to the phone, and executed a script that loki'd my twrp recovery.img file using the aboot partition on my phone (it used dd and stuff).
Anyway, I'm now happily in twrp, ready to install PAC again. Thanks for your support!!
Click to expand...
Click to collapse
Any chance you can give me a noob walkthrough of this. I am in the same boat and would like to get a custom recovery back so i can nandroid back to one of my saved set ups. I am on MDK rooted, just cant install a CWM or TWRP for some reason
Have a question. The recovery is the one is in Charge of the loki patch? I root my device with casual and install google play edition 4.4 with no problem. Then I dont remember if it was before of after flashing the first rom I update twrp to the latest version and flash darthstalker and went to a yellow triangle boot screen that says that the software is not authorized by att. Bla bla bla. Hopefully I nandroid the mdl stock root and was able to go back. But I was getting the samsung custom boot and the device was running without issues. I was reading about how to take off that image and find that if you use triangle away to reset counter flash it will back to the Samsumg Galaxy s4 screen what works for me. then I run CASUAL again and it gave me back the old recovery. If some can explain or bring me some info about how loki works and which roms can be flashed without having this issue I will appreciate.
Sent from my SAMSUNG-SGH-I337 using XDA Premium HD app
MAFU21 said:
Have a question. The recovery is the one is in Charge of the loki patch? I root my device with casual and install google play edition 4.4 with no problem. Then I dont remember if it was before of after flashing the first rom I update twrp to the latest version and flash darthstalker and went to a yellow triangle boot screen that says that the software is not authorized by att. Bla bla bla. Hopefully I nandroid the mdl stock root and was able to go back. But I was getting the samsung custom boot and the device was running without issues. I was reading about how to take off that image and find that if you use triangle away to reset counter flash it will back to the Samsumg Galaxy s4 screen what works for me. then I run CASUAL again and it gave me back the old recovery. If some can explain or bring me some info about how loki works and which roms can be flashed without having this issue I will appreciate.
Sent from my SAMSUNG-SGH-I337 using XDA Premium HD app
Click to expand...
Click to collapse
CASUAL, as far as I know, isn't used on the I545 (Verizon GS4).
You can't assume that a tool for some other carrier's GS4 will work on the I545.
k1mu said:
CASUAL, as far as I know, isn't used on the I545 (Verizon GS4).
You can't assume that a tool for some other carrier's GS4 will work on the I545.
Click to expand...
Click to collapse
U r right. By the way wrong thread. Sory.
Sent from my SAMSUNG-SGH-I337 using XDA Premium HD app
blindfaith76 said:
Any chance you can give me a noob walkthrough of this. I am in the same boat and would like to get a custom recovery back so i can nandroid back to one of my saved set ups. I am on MDK rooted, just cant install a CWM or TWRP for some reason
Click to expand...
Click to collapse
When presented with the "System software not authorized by Verizon Wireless has been found on your phone. Please turn off your phone and go to the nearest Verizon Wireless store for help." error, I followed these steps.
1. hold volume down button to enter download mode
2.press volume down button again to cancel download mode
(This restarts the phone and gets you into your homescreen without the error)
3.Downloaded "Recovery Tools" from the market
4. using recovery tools Flashed the TWRP recovery.
5. Rebooted.
(flashing Clockwork Recovery always triggers the error message)
6. Now, I am unfortunately unable to restore my previous Clockwork nandroids, however I can access the TWRP recovery to flash roms and basically "start over". Any new nandroid I make with TWRP is good to go and able to be restored.
hope this helps somebody out there that may be in my same situation. For whatever reason Clockwork Mod recovery always triggers this error, but TWRP works fine.
This is a TWRP backup of the stock firmware for V510 GPE GPAD 8.3. They have already been updated. It is completely stock no mods, no root, no busybox. This should ensure that you are able to take future OTAs without issue. Many GPE users have been having problems with the OTAs. The reason is that the OTA does a system verification and any type of modification causes it to fail.
How to flash this:
1. Reboot into bootloader
2. Flash TWRP if you don't already have it. Current version is 2.8.1.0 fastboot flash recovery xxxxxxxxxxxxx.img (where xxxxx is the filename)
3. Reboot System
4. Copy the entire contents of the zip file to your TWRP/BACKUPS/LG0000XXXXXXXX folder. Make sure you copy the folder 2014-11-30--23-35-25 LRX21P.L004 or 2014-06-26--18-41-18 KTU84P.L002. If you don't have a backups folder, create one in TWRP by choosing Backup, then backup something like the boot partition.
5. Reboot to Recovery Vol Dwn+Pwr or adb reboot recovery.
6. Choose Restore and select 2014-11-30--23-35-25 LRX21P.L004 or 2014-06-26--18-41-18 KTU84P.L002
7. Once finished Reboot System.
8. Upon boot you should be greeted with the usual Setup screens.
9. Reboot into bootloader
10. (Optional for Kit Kat) Flash stock recovery: fastboot flash recovery 17-recovery.img
11. Reboot into system
.
Flashing the stock recovery is optional however if you want a completely stock experience and ensure future OTAs, you probably want to do so. Also note that you must unroot to take any future OTAs.
To reroot flash latest version of TWRP.
Download Links:
LMY47O.L008 with Stock Recovery
TWRP Backup 5.1 LMY47O.L005 with Stock Recovery
TWRP Backup 5.1 LMY47O Thanks @rocket321 for providing the image.
TWRP BACKUP 5.0 LRX21P.L004
TWRP BACKUP 4.4.4 KTU84P.L002
KK Stock Recovery
You did an excellent job on this thread. Thanks for doing this for our small community.
BTW: regarding recovery for our device, the latest (and in fact only) that I see is TWRP 2.7.0.1 in the Original Android Development section.
Agreed. I wasn't able to flash 4.4.4 any other way. Tried everything, kept getting errors. This finally worked!
cam30era said:
You did an excellent job on this thread. Thanks for doing this for our small community.
BTW: regarding recovery for our device, the latest (and in fact only) that I see is TWRP 2.7.0.1 in the Original Android Development section.
Click to expand...
Click to collapse
Figured it will come in handy to have this online for everyone in the future...when I bought the device when it was announced thought there would be more dev on it...but that hasn't been the case. Luckily we at least have twrp.
No partitions selected for restore.
djkinetic said:
This is a TWRP backup of the stock firmware for V510 GPE GPAD 8.3. It has already been updated to 4.4.4. It is completely stock no mods, no root, no busybox. This should ensure that you are able to take future OTAs without issue. Many GPE users have been having problems with the OTA for 4.4.4 The reason is that the OTA does a system verification and any type of modification causes it to fail.
How to flash this:
1. Reboot into bootloader
2. Flash TWRP if you don't already have it. Current version is 2.7.0.1 fastboot flash recovery xxxxxxxxxxxxx.img (where xxxxx is the filename)
3. Reboot System
4. Copy the entire contents of the zip file to your TWRP/BACKUPS/LG0000XXXXXXXX folder. Make sure you copy the folder 2014-06-26--18-41-18 KTU84P.L002. If you don't have a backups folder, create one in TWRP by choosing Backup, then backup something like the boot partition.
5. Reboot to Recovery Vol Dwn+Pwr or adb reboot recovery.
6. Choose Restore and select 2014-06-26--18-41-18 KTU84P.L002
7. Once finished Reboot System.
8. Upon boot you should be greeted with the usual Setup screens.
9. Reboot into bootloader
10. (Optional) Flash stock recovery: fastboot flash recovery 17-recovery.img
11. Reboot into system
.
Flashing the stock recovery is optional however if you want a completely stock experience and ensure future OTAs, you probably want to do so. Also note that you must unroot to take any future OTAs.
Download Links:
TWRP BACKUP 4.4.4 KTU84P.L002
Stock Recovery
Click to expand...
Click to collapse
When I flash this in twrp it fails to flash and i get an error message: No partitions selected for restore. Have twrp 2.7.0.1 installed. Thank you.
Do I unzip the folder before I move it to the backup folder?
1barlog17 said:
Do I unzip the folder before I move it to the backup folder?
Click to expand...
Click to collapse
Delete
Figured out what was going on. finally got it to flash in TWRP. Works great. Thank you for this.
Thanks for this image - was the only way I was able to update.
Sent from my LG-V510 using Tapatalk
I was not able to update using your image and I don't know why. Everything was done correctly as far as I know. I downloaded and unpacked the zip and placed it in the back apps folder of TWRP and rebooted into recovery and tried restore with no success during the system restore it stops halfway through and says failed.
I tried downloading the file twice, installing the file from my computer, changing my SD card, deleting everything and trying, deleting just dalvik cache a,updating the partition separately, and was able to update the boot partition but not system and data. I honestly don't know what the trouble is as I was able to restore my own back up several times.if anybody has any insight into what is happening here please tell me. I would really like to install the update! I don't know why it is not allowing me to.
sleekmason said:
I was not able to update using your image and I don't know why. Everything was done correctly as far as I know. I downloaded and unpacked the zip and placed it in the back apps folder of TWRP and rebooted into recovery and tried restore with no success during the system restore it stops halfway through and says failed.
I tried downloading the file twice, installing the file from my computer, changing my SD card, deleting everything and trying, deleting just dalvik cache a,updating the partition separately, and was able to update the boot partition but not system and data. I honestly don't know what the trouble is as I was able to restore my own back up several times.if anybody has any insight into what is happening here please tell me. I would really like to install the update! I don't know why it is not allowing me to.
Click to expand...
Click to collapse
First off, I use solid explorer, dual pane. Very easy to navigate for me.
I only copied system. I didn't even wipe. All my data and settings were intact. As close to an OTA I could get. The system backup was 790.95mb
It sounds like you did everything right to me. I included a screen shot of what it looked like after i clicked the backup.zip and moved the unzipped backup to the TWRP backup folder.
Sent from my LG-V510 using XDA Premium 4 mobile app
sleekmason said:
I was not able to update using your image and I don't know why. Everything was done correctly as far as I know. I downloaded and unpacked the zip and placed it in the back apps folder of TWRP and rebooted into recovery and tried restore with no success during the system restore it stops halfway through and says failed.
I tried downloading the file twice, installing the file from my computer, changing my SD card, deleting everything and trying, deleting just dalvik cache a,updating the partition separately, and was able to update the boot partition but not system and data. I honestly don't know what the trouble is as I was able to restore my own back up several times.if anybody has any insight into what is happening here please tell me. I would really like to install the update! I don't know why it is not allowing me to.
Click to expand...
Click to collapse
im not sure if this would work
did u try restoring from the internal sd instead of external. as far as I know the backup file should have no issues.
djkinetic said:
im not sure if this would work
did u try restoring from the internal sd instead of external. as far as I know the backup file should have no issues.
Click to expand...
Click to collapse
That was it!! Thank you!
Do I need to uninstall Xposed Framework, unroot, restore the stock kernel, etc., before restoring this system back up TWRP? I assume the answer is no, though I'll need to reinstall those afterward, but I figured I'd check first!
UPDATE: Never mind. I just went ahead and restored it successfully and am in the process of restoring my apps from TiBu now. Thanks again for providing this for those of us who couldn't upgrade to 4.4.4 any other way!
Hey guys,
first off thank you for posting this tutorial, I was able to perform the backup0 and am currently on 4.4.4.
I did, however, run into a slight hiccup when I was trying to flash the stock recovery. I kept getting messages about partitions and so forth. I entered in the following commands from beginning to end:
adb devices
adb reboot bootloader
fastboot flash recovery 17-recovery.img
but as I said I can't get the job done lol.
Any ideas?
ephayzee said:
Hey guys,
first off thank you for posting this tutorial, I was able to perform the backup0 and am currently on 4.4.4.
I did, however, run into a slight hiccup when I was trying to flash the stock recovery. I kept getting messages about partitions and so forth. I entered in the following commands from beginning to end:
adb devices
adb reboot bootloader
fastboot flash recovery 17-recovery.img
but as I said I can't get the job done lol.
Any ideas?
Click to expand...
Click to collapse
A few things to check:
you need to have usb debugging checked on phone
you need the recovery image in same folder as your fastboot.exe/adb files
you need to cd to that directory/folder
TWRP source
Hi,
Can you please tell me where to find TWRP 2.7.x for the V510. I currently have 2.6.3.0, I believe?
Thanks
techinv said:
Hi,
Can you please tell me where to find TWRP 2.7.x for the V510. I currently have 2.6.3.0, I believe?
Thanks
Click to expand...
Click to collapse
It worked fine for me with TWRP 2.6
techinv said:
Hi,
Can you please tell me where to find TWRP 2.7.x for the V510. I currently have 2.6.3.0, I believe?
Thanks
Click to expand...
Click to collapse
Here > http://forum.xda-developers.com/showthread.php?t=2682606
However, download link in OP is currently broken. I PMed the OP about it.
Has anyone gotten the error "E: No partitions selected for restore." when trying to flash the recovery?
The below steps are only part of the solution since there are a couple of prerequisites (with solutions for those already on these forums and MIUI sites). I'm afraid since it's getting late here, I cannot provide detailed steps for everything, I'm assuming you are like me and only got so far, so already know what you're doing
I'm not responsible for hard bricks, however if any steps I've entered are entirely wrong, please do let me know. I'm only trying to help the community out.
What you need:
Unlocked bootloader, sadly you will have to wait for the permission from them (I don't like this process either)
Decent knowledge of TWRP menu system
no care for completely wiping the SD Card contents - please make a backup of pictures or anything else you want
adb and fastboot both working and recognising the phone properly
Gemini (Xiaomi Mi 5) TWRP - https://drive.google.com/file/d/0B95J_je8rRN0V1Y2T2o0Mlh2R1E/view?usp=docslist_api **Thanks to Nesquix for posting the link to this** it is in Chinese and the theme changing solution did not work for me - but this doesn't really matter if you know your way around TWRP
Latest SuperSU - https://download.chainfire.eu/924/SuperSU/BETA-SuperSU-v2.68-20160228150503.zip
Latest DEV Fastboot ROM - I cannot post the link however it can be found by searching for "mi 5 fastboot developer rom" on Google and selecting the link going to en.miui.com
STEPS to take:
Extract the contents of the fastboot ROM to a location of your choice. The only file you need is this one: \...\...\images\system.img (if someone can upload separately, I'll link in OP)
Place both the system.img from the fastboot ROM and twrp img file in the location of your fastboot folder
Enter fastboot mode (bootloader) on the Mi 5 via Power off --> volume down + power on --> let go once you see the MI logo
Check your device can be seen via the command, fastboot devices --> ENTER
Now input the following command, fastboot flash recovery twrp-mi5.img --> ENTER
Now enter in to recovery via volume up + power on - There appears to be a bug with TWRP whereby on some boots, touch isn't responsive, just keep booting back till it works (it will eventually)
Swipe on the first screen to enter the menu, tap the top right icon for wiping data, then the bottom right icon, you will see a text box with a warning - enter yes, then tick to fully wipe the SD card
Power off again, and reboot back to fastboot mode (bootloader)
Once there, input this command, fastboot flash system system.img --> ENTER
Once the system is flashed, input this command, fastboot reboot
Skip past initial steps for speed place the superSU zip on the root of the SD Card and then reboot back to recovery again
Flash SuperSU in recovery (top left option, find your zip, flash it
Reboot system
PROFIT - you now have an unencrypted system with working superSU and apps like Adaway work flawlessly - HAVE FUN and don't forget to say thanks if I did actually help you
Interesting notes.....
I'm not sure about anyone else, but I found web browsing to be alarmingly slow with no good explanation, the above steps completely resolved this
Google is now a search option in the default browser (it wasn't before!!)
Call it placebo all you want, but the phone really does seem a lot faster now.
Last but not least, I'm fairly certain to update to newer versions, you only have to extract same system.img from future fastboot ROM zips, and flash this on it's own to update the system.
To get the multilingual functionality of TWRP working, copy this file in TWRP\theme
You can also change the theme color in the advanced settings .
https://drive.google.com/file/d/0B95J_je8rRN0N19DLXdFYXV4NW8/view?usp=docslist_api
nesquix said:
To get the multilingual functionality of TWRP working, copy this file in TWRP\theme
You can also change the theme color in the advanced settings .
https://drive.google.com/file/d/0B95J_je8rRN0N19DLXdFYXV4NW8/view?usp=docslist_api
Click to expand...
Click to collapse
I think we dont need to copy TWRP theme. You can set language in first welcome screen or in Settings menu, and tap "world icon".
Here is the attachment of TWRP Screenshot :
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
---------- Post added at 03:38 PM ---------- Previous post was at 03:26 PM ----------
kickassdave said:
The below steps are only part of the solution since there are a couple of prerequisites (with solutions for those already on these forums and MIUI sites). I'm afraid since it's getting late here, I cannot provide detailed steps for everything, I'm assuming you are like me and only got so far, so already know what you're doing
.
Click to expand...
Click to collapse
I think we dont need to flash system.img. check out my post here. After flashing TWRP via fastboot, format data and type yes in TWRP, all you need to do is reboot to system and swipe disable stock recovery flash. Setup your Mi5 and then copy SuperSU 2.65 or 2.68 beta to your Mi5. Next is reboot back to recovery, swipe allow modification, and then flash the SuperSU. Done. I tested out on Dev ROM and Stable ROM too, that there is no need to flash system.img again.
tomhtg90 said:
I think we dont need to copy TWRP theme. You can set language in first welcome screen or in Settings menu, and tap "world icon".
Here is the attachment of TWRP Screenshot :
---------- Post added at 03:38 PM ---------- Previous post was at 03:26 PM ----------
I think we dont need to flash system.img. check out my post here. After flashing TWRP via fastboot, format data and type yes in TWRP, all you need to do is reboot to system and swipe disable stock recovery flash. Setup your Mi5 and then copy SuperSU 2.65 or 2.68 beta to your Mi5. Next is reboot back to recovery, swipe allow modification, and then flash the SuperSU. Done. I tested out on Dev ROM and Stable ROM too, that there is no need to flash system.img again.
Click to expand...
Click to collapse
When I set to English in TWRP without the theme mod, it instantly reverts to Chinese.
With regards to flashing the system.img, I have a slight nagging issue with regards to the amount of files inside the fastboot image which WEREN'T required for full functionality.
I'm also concerned about where my data was going when browsing, as my browsing was slow no matter which browser I used - almost as if it was proxying via China.
Having only flashed system.img I no longer have this issue.
kickassdave said:
When I set to English in TWRP without the theme mod, it instantly reverts to Chinese.
With regards to flashing the system.img, I have a slight nagging issue with regards to the amount of files inside the fastboot image which WEREN'T required for full functionality.
I'm also concerned about where my data was going when browsing, as my browsing was slow no matter which browser I used - almost as if it was proxying via China.
Having only flashed system.img I no longer have this issue.
Click to expand...
Click to collapse
English languages in TWRP will not go back to chinese if you tap on "Never show this screen during boot again", "swipe to allow modification" and "Swipe disable recovery flash". But, if that's the only method that work for you, good then. Cheers
No need to flash again system here too
What exactly do the rest of the contents of the ROM contain then since I literally flashed on a single img from the entire zip!
I have mine Mi5 unlocked, with TWRP, root (SU) open encryption.
I'm on china dev rom 6.3.17 and would like to upgrade to 6.3.24, as I have some issues (camera force close after trying to get picture during video recording and some apps crashes).
Anyway, my question is: HOW should I update system and not lose all my setting, apps, data, etc and of course I can't lose root, open encryption and unlocked bootloader.
Please advise.
1myxomatosis1 said:
I have mine Mi5 unlocked, with TWRP, root (SU) open encryption.
I'm on china dev rom 6.3.17 and would like to upgrade to 6.3.24, as I have some issues (camera force close after trying to get picture during video recording and some apps crashes).
Anyway, my question is: HOW should I update system and not lose all my setting, apps, data, etc and of course I can't lose root, open encryption and unlocked bootloader.
Please advise.
Click to expand...
Click to collapse
this is what i'm trying to do now. but i'm on another base... not the 6.3.17 but the 7.2.7.0, anyway this is the same procedure.
when you have unlocked your bootloader, there is no way to encrypt all data again if you don't select "flash_all_lock.bat" with MiFlash windows app...
so you can play all TWRP partitions...except the SDCARD (called "data/media", don't mingle/mix up/confound with the "data" partition.... )
So since fastboot is still open with your unlocked bootloader are always able to reflash a recovery and do whatever you want again, don't panic !
i tried updating my rom 7.2.7.0 to 6.3.24 by flashing the system.img BUT there are some force close.... security center FC... wifi not working... i think they forgot to say that we need to manually flash the boot.img too (kernel.... who contain a lot of drivers and system links...)
so i just flashed the system.img and boot.img of the 6.3.24 on my 7.2.7.0 rom, i will report my feedback in some hours max. EDIT : WORKING !
but don't wory, since you don't wipe your SDCARD in the recovery (or use the flash_all_lock.bat with MiFlash), you will not loose your decrypted data partition
if my method of "simple updating" is not working by just flashing system.img and boot.img over the rom........ i suggest to reflash all partition with adb (system.img and boot.img), after that you can reboot to the twrp recovery, flash supersu 2.68 (or the last one) to be root, and setup your phone again... (you can do a MiBackup in the settings, and restore it later, this is working fine for your app, settings and so on)
:silly:
---------- Post added at 08:21 PM ---------- Previous post was at 08:13 PM ----------
UPDATE : WORKING.
Procedure to UPDATE since your phone have UNLOCKED BL, data decrypted and TWRP already flashed (or you can flash it before the procedure by adb) :
PROCEDURE
just flash the system.img AND the boot.img with adb in the CMD
(be sure your files are in the same folder of adb.exe and fastboot.exe)
"fastboot flash system system.img"
"fastboot flash boot boot.img"
then reboot to twrp recovery... flash supersu 2.68..
you don't need to wipe something.
just reboot and wait.
your phone is now updated, with root, twrp, decrypted data, and you don't loose your apps, settings and files. :good:
nesquix said:
[...]
PROCEDURE
[...]
Click to expand...
Click to collapse
Sound so easy and so fantastic that I can't just believe I'll try tomorrow as today I don't have power if something went wrong and I would have to start from a zero point:]
1myxomatosis1 said:
Sound so easy and so fantastic that I can't just believe I'll try tomorrow as today I don't have power if something went wrong and I would have to start from a zero point:]
Click to expand...
Click to collapse
I can't flash anything on TWRP, I can't mount the data... and so there's no file in sdcard
so at which point is the phone unencrypted? With installing SuperSU ?!
I also have the provlem, that TWRP changes the language instantly after changing it. And it also prompts me for password of encrypted partitions
Ivyn87 said:
I can't flash anything on TWRP, I can't mount the data... and so there's no file in sdcard
Click to expand...
Click to collapse
Because your phone is still encrypted.
So read all 3stpage and you will understand what you need to do.
http://forum.xda-developers.com/mi-5/help/rooting-mi-4-unlocking-bootloader-t3334677/page3
---------- Post added at 04:12 PM ---------- Previous post was at 04:11 PM ----------
p1nky said:
so at which point is the phone unencrypted? With installing SuperSU ?!
I also have the provlem, that TWRP changes the language instantly after changing it. And it also prompts me for password of encrypted partitions
Click to expand...
Click to collapse
After wiping all the phone 2 times in the twrp recovery.
nesquix said:
Because your phone is still encrypted.
So read all 3stpage and you will understand what you need to do.
http://forum.xda-developers.com/mi-5/help/rooting-mi-4-unlocking-bootloader-t3334677/page3
---------- Post added at 04:12 PM ---------- Previous post was at 04:11 PM ----------
After wiping all the phone 2 times in the twrp recovery.
Click to expand...
Click to collapse
Very thanks... now it work
Why can't TWRP write to encrypted partitions? I thought this is possible with TWRP 3.0. At least I have not heard from new Nexus owners that disabling encryption is necessary.
Hello,
I have Twrp already and a custom rom, i only want to decrypt . Am i right that i only< had to do this:
Swipe on the first screen to enter the menu, tap the top right icon for wiping data, then the bottom right icon, you will see a text box with a warning - enter yes, then tick to fully wipe the SD card.
And later to get root:
Skip past initial steps for speed place the superSU zip on the root of the SD Card and then reboot back to recovery again
Flash SuperSU in recovery (top left option, find your zip, flash it
Reboot system.
Kind regards gandalf
Thank you very much. !!!!:laugh::laugh:
I saved this tutorial, I had left the phone in the login screen.
Hello guys , I need some advice. I have a Mi5s already unlocked with TWRP and custom rom, but would like to get rid of encryption. My doubt is, if I format data and wipe everything, will I be able to move the rom zip in TWRP? And also, will I still have a system installed ? Thanks for your reply
christ-al said:
Hello guys , I need some advice. I have a Mi5s already unlocked with TWRP and custom rom, but would like to get rid of encryption. My doubt is, if I format data and wipe everything, will I be able to move the rom zip in TWRP? And also, will I still have a system installed ? Thanks for your reply
Click to expand...
Click to collapse
Yes ... U keep system...get blank data... Restart the phone... copy the zip/ROM again...or use USB otg
Unofficial release -TWRP recovery for the Samsung Galaxy Tab S3 - SM-T820/T825, Qualcomm MSM8996
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
TWRP 3.2.1-0 Released
Dec 9, 2017
TWRP 3.2.1-0 is out now for most currently supported devices.
What's new in 3.2.1-0:
What's new in 3.2.1-0:
* minui fixes (cryptomilk)
* Better android-8.0 compatibility in ROM trees (Dees_Troy)
* Fix missing library in android-8.0 (nkk71)
* Fix inconsistent SDCard naming (DevUt)
* Default to TWRP restore instead of adb backup restore to fix restore on fresh TWRP boot (jlask)
Update 18/5/2018
TWRP 3.2.1-1 build released.
Current status: BETA
Features:
MTP working
ADB working
SEANDROID warning fix
TWRP and Kernel built from latest source
Factory Image flashing(see below) >> to be added
NTFS support
F2FS support >> To be added
Twrp app support
IMPORTANT:
PLEASE READ ALL OF THIS POST BEFORE FLASHING ANYTHING TO YOUR DEVICE.
WHATEVER YOU DO BEFORE FLASHING ANYTHING MAKE A BACKUP OF YOUR DEVICE AND HAVE THE STOCK FIRMWARE TO HAND JUST IN CASE, DOWNLOADED FROM SAMMOBILE OR UPDATO.
THIS WILL TRIP KNOX AND MAY VOID YOUR WARRANTY!
Instructions:
Flash with ODIN using the AP slot.
1. Put your device in DOWNLOAD mode.
2. Uncheck Auto reboot.
3. Load the respective file below into the AP slot and hit start.
4. After flashing and ODIN reports PASS immediately reboot to recovery by holding POWER + HOME + VOL DOWN.
As soon as the screen goes blank change to VOL UP whilst still holding POWER + HOME.
You should now see TWRP recovery.
Failure to implicitly comply with step 4 will result in stock recovery replacing TWRP at first boot
NOTE: Since android 5.1.1 it is necessary to enable OEM Unlock.
Settings -> Developer Options -> OEM unlocking
ENABLE OEM UNLOCK FIRST OR YOU MAY ENCOUNTER 'BLOCKED BY FRP LOCK' WHEN FLASHING.
DOWNLOAD -
Device must be running at least AQD6 or later firmware. Earlier firmware may need the previous builds:
UPDATE: 18/5/2018 TWRP 3.2.1-1
twrp_3.2.1-1_T820_28518
twrp_3.2.1-1_T825_29518
UPDATE: 8/5/2017 TWRP 3.1.0-1
twrp_3.1.0-1_sm-t820_AQD6
twrp_3.1.0-1_sm-t825_AQD6
Previous builds:
SM-T820:
https://www.androidfilehost.com/?fid=745425885120721426
SM-T825:
https://www.androidfilehost.com/?fid=673368273298945058
IMPORTANT! This device enforces dm-verity. ANY modifications or even mounting system will put the device into a bootloop. To prevent this TWRP will ask at first boot if you want to keep system 'Read only' or 'Allow modifications to system'. If you choose to keep 'Read only' you will have to flash TWRP at every boot to recovery.
If you choose to 'Allow' then Magisk needs flashing below to disable dm-verity.
Follow the instructions below to disable dmverity, forced encryption and mount internal storage(DATA):
MARSHMALLOW AND NOUGAT ONLY!:
To disable forced encryption, mount internal storage(DATA) and disable dm-verity:
1. Boot to Twrp
2. Format Data partition using FORMAT DATA button under Wipe options.
(Note: This will wipe the internal storage)
3. Check DATA is mountable.
4. Install Magisk
5. Reboot
OREO ONLY!:
To disable forced encryption, mount internal storage(DATA) and disable dm-verity:
1. Boot to TWRP
2. Install the Forced encryption patch: Tabs3_oreo_forced encryption_disabler
3. Format DATA using the *FORMAT DATA button* under the wipe options.
(NOTE - THIS WILL WIPE ALL INTERNAL STORAGE!)
4. Install Magisk
5. Reboot and check DATA is mountable
Done.
Magisk: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
INSTRUCTIONS TO USE ADB BACKUP:
https://www.droidorigin.com/take-adb-backup-using-twrp-v3-1-0-0/
DEVICE TREE: soon
PLEASE DO *NOT* DIRECT LINK TO THESE FILES. PLEASE LINK TO THIS POST
Credits: Me, my testers @suzook, @jonathonalexander, Teamwin
Please note I don't own this device and spend a lot of my free time bringing these builds for you to use and benefit from.
FEEDBACK IS APPRECIATED PLEASE.
THANKS.
DONATE ME HERE IF YOU WANT TO BUY ME A BEER OR HIT THE THANKS BUTTON IF I HELPED YOU
.
RESERVED
Delete
Deleted.
ashyx said:
How do you mean it bootloops? I thought you said that you were able to mount the partitions and flash supersu?
Click to expand...
Click to collapse
I can. It flashes, and boots to TWRP., Partitions are mounted. But I can never reboot to system. It winds up bootlooping, even without flashing SuperSU.
suzook said:
I can. It flashes, and boots to TWRP., Partitions are mounted. But I can never reboot to system. It winds up bootlooping, even without flashing SuperSU.
Click to expand...
Click to collapse
Ah right, the issue isn't twrp, it's dmverity. If you allow modifications to system in twrp it triggers dm-verity which causes a boot loop.
To remedy this you need to disable it by either flashing SuperSU and/or the boot patch
Be aware that after flashing the boot patch you will need to FORMAT (not wipe) /DATA
The other alternative is to disable 'allow modifications to system'
However if you choose to disable modifications you will need to reflash twrp each time you reboot as it will be replaced by stock recovery.
.
ashyx said:
Ah right, the issue isn't twrp, it's dmverity. If you allow modifications to system in twrp it triggers dm-verity which causes a boot loop.
To remedy this you need to disable it by either flashing SuperSU and/or the boot patch
Be aware that after flashing the boot patch you will need to FORMAT (not wipe) /DATA
The other alternative is to disable 'allow modifications to system'
However if you choose to disable modifications you will need to reflash twrp each time you reboot as it will be replaced by stock recovery.
.
Click to expand...
Click to collapse
Format data for me at this point is fine, as I'm starting fresh again. Where is this boot patch? Will give it a try tonight.
suzook said:
Format data for me at this point is fine, as I'm starting fresh again. Where is this boot patch? Will give it a try tonight.
Click to expand...
Click to collapse
Its in the first post.
ashyx said:
Its in the first post.
Click to expand...
Click to collapse
, TWRP flashed, booting, and making backups. Supersu....No good. It flashes, but I have NO ROOT. Thoughts?
its failing on the boot.img patcher it states boot.img not found.
suzook said:
, TWRP flashed, booting, and making backups. Supersu....No good. It flashes, but I have NO ROOT. Thoughts?
its failing on the boot.img patcher it states boot.img not found.
Click to expand...
Click to collapse
I need the recovery log after installing supersu and boot.img patcher.
ashyx said:
I need the recovery log after installing supersu and boot.img patcher.
Click to expand...
Click to collapse
https://drive.google.com/file/d/0BwPAGUQCA8FDN2pGWV9HSmdYNDQ/view?usp=drivesdk
suzook said:
https://drive.google.com/file/d/0BwPAGUQCA8FDN2pGWV9HSmdYNDQ/view?usp=drivesdk
Click to expand...
Click to collapse
Looks like Chainfires script can't find partitions defined as block devices. I must say a bit of an oversight by CF if that's the case.
Try this, recovery log if possible please after installing.
https://www.androidfilehost.com/?fid=529152257862715887
If there is still an issue I will patch the boot image manually.
.
ashyx said:
Looks like Chainfires script can't mount partitions defined as block devices. I must say a bit of an oversight by CF if that's the case.
Try this, recovery log if possible please after installing.
https://www.androidfilehost.com/?fid=529152257862715887
If there is still an issue I will patch the boot image manually.
.
Click to expand...
Click to collapse
Thanks, will give it a go, and post results and recovery log.
Edit...So flash this new recovery, then SuperSU, and the patch?
suzook said:
Thanks, will give it a go, and post results and recovery log.
Edit...So flash this new recovery, then SuperSU, and the patch?
Click to expand...
Click to collapse
Yes apply the patch after supersu to be on the safe side.
Wow, I haven't got the tab in my hands yet, and there's already recovery & root!
Have some beer: Confirmation number: 49581192XS319942M
ashyx said:
Yes apply the patch after supersu to be on the safe side.
Click to expand...
Click to collapse
Quick question, can I flash the latest TWRP you updated with the current TWRP installed? Or should I Odin it?
suzook said:
Quick question, can I flash the latest TWRP you updated with the current TWRP installed? Or should I Odin it?
Click to expand...
Click to collapse
Yep. Just extract it from the tar archive and then select install in twrp.
ashyx said:
Yep. Just extract it from the tar archive and then select install in twrp.
Click to expand...
Click to collapse
Latest TWRP does not mount partitions again
https://drive.google.com/file/d/0BwPAGUQCA8FDcmdCUWNXUnNRdEk/view?usp=drivesdk
Log
suzook said:
Latest TWRP does not mount partitions again
https://drive.google.com/file/d/0BwPAGUQCA8FDcmdCUWNXUnNRdEk/view?usp=drivesdk
Log
Click to expand...
Click to collapse
Damn, even defining the boot device in the command line doesn't allow named partitions to mount.
Back to the previous twrp then.
Looks like manual patching of the boot image is going to be required.
ashyx said:
Damn, even defining the boot device in the command line doesn't allow named partitions to mount.
Back to the previous twrp then.
Looks like manual patching of the boot image is going to be required.
Click to expand...
Click to collapse
Ok, sounds good. Ready to test whenever you need. I'm available rest of day, and all weekend. Thanks.
Hi,
I tried to update my P6 using the magisk OTA update method:
-Unistall / Restore image
-Install OTA, no reboot
-Install magisk on inactive slot
-Reboot
My phone was on the SQ3A.220705.001.B2 update, few months old.
When I rebooted, I was prompted with the "device corrupted" message. I pressed the power key to continue, and was stuck at the Google logo boot loop.
I forced turned off the phone (hold power + vol up a few sec), and the phone rebooted, no corruption message to my surprise, and booted correctly. However, my system did not update (still on SQ3A.220705.001.B2).
I'm a rookie on device rooting, but my understanding is that my inactive slot (partition b) as the update installed but is corrupted and goes in boot loop, while partition a is not updated but not corrupted either.
The thing is, I only did "install on inactive slot", so magisk was uninstalled on partition a, and rebooting made me lost root on that partition.
Is there any way to de-corrupt partition b without losing data ? Because without root on partition a, it seems like I'll need to reinstall it, meaning a factory reset...
I've searched a bit on here, saw that it was probably an avb bug (but rookie me doesn't know what avb is), and that OTA update using magisk inactive partition was not recommended for P6 and P7.
Any help would be greatly appreciated, thanks !
SleinBuyt said:
Is there any way to de-corrupt partition b without losing data ? Because without root on partition a, it seems like I'll need to reinstall it, meaning a factory reset...
I've searched a bit on here, saw that it was probably an avb bug (but rookie me doesn't know what avb is), and that OTA update using magisk inactive partition was not recommended for P6 and P7.
Any help would be greatly appreciated, thanks !
Click to expand...
Click to collapse
Be certain you're running the latest version of ADB. Google provides a link to the package you can download and extract. Then download a factory image from Google, extract the files from the zip to the same folder ADB was wxtracted to, and edit "flash-all.bat" in a text editor. You're looking for a snippet of text, "-w". Delete that text and save the file. From there, connect the unit to your PC and flash the ROM.
This will restore both partitions to working condition without removing data, but you will lose root in the process and will need to root again.
Strephon Alkhalikoi said:
Be certain you're running the latest version of ADB. Google provides a link to the package you can download and extract. Then download a factory image from Google, extract the files from the zip to the same folder ADB was wxtracted to, and edit "flash-all.bat" in a text editor. You're looking for a snippet of text, "-w". Delete that text and save the file. From there, connect the unit to your PC and flash the ROM.
This will restore both partitions to working condition without removing data, but you will lose root in the process and will need to root again.
Click to expand...
Click to collapse
Strephon Alkhalikoi said:
Be certain you're running the latest version of ADB. Google provides a link to the package you can download and extract. Then download a factory image from Google, extract the files from the zip to the same folder ADB was wxtracted to, and edit "flash-all.bat" in a text editor. You're looking for a snippet of text, "-w". Delete that text and save the file. From there, connect the unit to your PC and flash the ROM.
This will restore both partitions to working condition without removing data, but you will lose root in the process and will need to root again.
Click to expand...
Click to collapse
Ok I'll find out how to flash ROM using adb beacause I don't remember, and I'll do what you said.
After that, I should be able to force boot to partition b (the updated one) using adb, right? And will I be able to root without losing data ?
SleinBuyt said:
Ok I'll find out how to flash ROM using adb beacause I don't remember, and I'll do what you said.
After that, I should be able to force boot to partition b (the updated one) using adb, right? And will I be able to root without losing data ?
Click to expand...
Click to collapse
Ok so I've searched a bit, since my bootloader is unlocked I'll be able to root without losing data. The only question that remains :
You told me to download a factory image and to flash it with adb. Can I download the lasted version, for example the one that I failed to update to? If so, after flashing, will my de va ice be updated to the lasted version ?
Because that means that it's a way to update my phone, if I don't want to get the corruption error :
-download lasted update
-flash using adb, with the edited .bat
-Reboot and re-flash magisk
-done
SleinBuyt said:
Ok so I've searched a bit, since my bootloader is unlocked I'll be able to root without losing data. The only question that remains :
You told me to download a factory image and to flash it with adb. Can I download the lasted version, for example the one that I failed to update to? If so, after flashing, will my de va ice be updated to the lasted version ?
Because that means that it's a way to update my phone, if I don't want to get the corruption error :
-download lasted update
-flash using adb, with the edited .bat
-Reboot and re-flash magisk
-done
Click to expand...
Click to collapse
I think that the easiest way is with Pixel Flasher, it makes everything automatically with data preserve.
SleinBuyt said:
Ok so I've searched a bit, since my bootloader is unlocked I'll be able to root without losing data. The only question that remains :
You told me to download a factory image and to flash it with adb. Can I download the lasted version, for example the one that I failed to update to? If so, after flashing, will my de va ice be updated to the lasted version ?
Because that means that it's a way to update my phone, if I don't want to get the corruption error :
-download lasted update
-flash using adb, with the edited .bat
-Reboot and re-flash magisk
-done
Click to expand...
Click to collapse
m_pastuszek said:
I think that the easiest way is with Pixel Flasher, it makes everything automatically with data preserve.
Click to expand...
Click to collapse
@SleinBuyt : Yes
@m_pastuszek : While he could do that he should learn how to do it without a tool first. That way he can understand what is going on when the tool is working.
Strephon Alkhalikoi said:
@SleinBuyt : Yes
@m_pastuszek : While he could do that he should learn how to do it without a tool first. That way he can understand what is going on when the tool is working.
Click to expand...
Click to collapse
I agree on this side, but actually editing script that makes something similar comes down to the same thing
That was the same case for me.
After latest OTA update, no matter how many time I tried to flash full factory image via fastboot, stil showing device corrupted.
A couple of things everyone having this issue should be aware of.
Currently, "Flash to Inactive Slot" breaks verification/dm-verity on the Pixel 6/7, and I believe that's responsible for the "Device corrupted" error. The Magisk devs are aware but don't have a fix yet. I haven't been able to test because there have been no OTAs since I disabled those myself (which PixelFlasher can do for you), but I believe disabling them should prevent that problem during OTAs, but be advised I think doing so requires wiping /data when you do it.
Also, if you're still getting "device corrupted" even after reflashing stock, first watch for any errors during flashing in PixelFlasher (I may have a fix for anyone that has USB issues on Windows devices, but it involves the registry so it makes some people nervous), but if it isn't working then try Google's Android Flash Tool by finding your device and desired firmware here and clicking Flash. You'll need to be using Chrome. That's never failed for me. Once you have it up and running again *then* use PixelFlasher to patch and flash the boot image.
ALSO, for anyone on T1B1/QPR2: Magisk currently is not working at all with these versions. It'll boot, but you'll have no root. No one knows why yet as far as I'm aware. You'll have to stick to earlier/non beta builds until there's an answer for that if you want root.
Jaitsu said:
ALSO, for anyone on T1B1/QPR2: Magisk currently is not working at all with these versions. It'll boot, but you'll have no root. No one knows why yet as far as I'm aware. You'll have to stick to earlier/non beta builds until there's an answer for that if you want root.
Click to expand...
Click to collapse
To root the Pixel 6 on QPR2 Beta 1 you can patch the Pixel 7 boot image and then flash that on the Pixel 6.
Compression method of ramdisk in Pixel 6 boot image is incorrect · Issue #6441 · topjohnwu/Magisk
After switching to the beta version can't patch boot img and succesfully get root, with the stable version works. Device: Pixel 6a Android version: Android 13 QPR2 Beta 1 (T2B1.221118.006) Magisk v...
github.com
UPDATE : I did it, I used ADB for the sake of trying it, next time I'll look into PixelFlasher I guess. The message is gone.
Exact step followed :
-I first trained to use adb by flashing magisk, but ended up patching the wrong boot.img (the one from the A13 update, while being on A12), which sent me in a bootloop.
-I then flashed the A13 ROM, with the modified flash-all file
-Rebooted bootloader, flashed magisk
-Rebooted device.
Took me 2h lol, each step was learning something.
Thanks everyone!
SleinBuyt said:
UPDATE : I did it, I used ADB for the sake of trying it, next time I'll look into PixelFlasher I guess. The message is gone.
Exact step followed :
-I first trained to use adb by flashing magisk, but ended up patching the wrong boot.img (the one from the A13 update, while being on A12), which sent me in a bootloop.
-I then flashed the A13 ROM, with the modified flash-all file
-Rebooted bootloader, flashed magisk
-Rebooted device.
Took me 2h lol, each step was learning something.
Thanks everyone!
Click to expand...
Click to collapse
Just make sure you have the A13 bootloader on both slots if you haven't already, since it sounds like you just updated from A12 to A13?
🛑❗⚠️ WARNING! Read this before your initial upgrade to Android 13!⚠️❗🛑
***Note: THIS IS NOT A ROOT GUIDE. For updating and root instructions, check out my guide here.*** From the Pixel Images page: This applies to ALL Tensor devices, regardless of whether or not you're rooted! What this means: Once Android 13...
forum.xda-developers.com
Lughnasadh said:
Just make sure you have the A13 bootloader on both slots if you haven't already, since it sounds like you just updated from A12 to A13?
🛑❗⚠️ WARNING! Read this before your initial upgrade to Android 13!⚠️❗🛑
***Note: THIS IS NOT A ROOT GUIDE. For updating and root instructions, check out my guide here.*** From the Pixel Images page: This applies to ALL Tensor devices, regardless of whether or not you're rooted! What this means: Once Android 13...
forum.xda-developers.com
Click to expand...
Click to collapse
I mean, the objective was to update my device and keep root, wich is now done. Why do I need the A13 bootloader on both slots, and if it's important how should I do it ?
SleinBuyt said:
I mean, the objective was to update my device and keep root, wich is now done. Why do I need the A13 bootloader on both slots, and if it's important how should I do it ?
Click to expand...
Click to collapse
It's important if you don't want to brick your device. Did you read the link I gave you?
Lughnasadh said:
It's important if you don't want to brick your device. Did you read the link I gave you?
Click to expand...
Click to collapse
Sorry I didn't see, I've read now.
So If ok reboot to fastboot, plug in, and with adb :
fastboot flash bootloader --slot=all flash-all.img
I should be good ?
SleinBuyt said:
Sorry I didn't see, I've read now.
So If ok reboot to fastboot, plug in, and with adb :
fastboot flash bootloader --slot=all flash-all.img
I should be good ?
Click to expand...
Click to collapse
fastboot flash bootloader --slot=all <A13 bootloader image>
My situation is a bit bizarre. I'm on beta and recently got an update notification that was 190mb. I went to magisk to restore images and magisk says stock backup does not exist. From there and went ahead and use my PC to flash my stock boot image and rebooted. Once an Android it's still says the same thing but when I go back to the update it says installation problem Even though I am on stock. That's where I'm at right now. Haven't messed with it since just rolled with no root and stock boot image.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Lughnasadh said:
fastboot flash bootloader --slot=all <A13 bootloader image>
Click to expand...
Click to collapse
And it's done ! Thanks for potentially saving my phone later !