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.
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
Introduction
This is a Sprint android 6.0 sense 7 leak. Everything is included in this Zip. Firmware, system img, boot img, latest SuperSU and a read me text file with detailed steps to install. I also have a mod pack by me if anyone is interested, with full apm, prism menu, brightness slider, right pull down, always show menu and search, long press options for several buttons, clear all in card view recent apps, and extra settings options
Features
Android 6.0
HTC Sense Version 7
Software Version 3.33.651.2
Latest SuperSU
Sprint_M9_Android_6.0.zip
How to install
Read the read me text file but I'll write it here as well
Copy 0PJAIMG.zip to root of external storage
Copy boot and system img to root of internal storage
Copy SuperSU v2.62 zip somewhere either on internal or external storage
Boot into download mode and update firmware ( I did this twice)
Boot into recovery and open terminal to flash the boot and system img
adb shell enter
dd if=/sdcard/boot.img of=/dev/block/bootdevice/by-name/boot
dd if=/sdcard/system.img of=/dev/block/bootdevice/by-name/system
Then flash the new SuperSU v2.62 zip
Then reboot to android M. DO NOT INSTALL SU FROM TWRP POPUP. CHOOSE DO NOT INSTALL
Any confirmation on this, testing?
EDIT:
I can confirm that 4.1 Venom boots. I pushed the firmware, using fastboot, pushed recovery, flashed 4.1 Venom.
Thanks for the leak.
Hi mate @[email protected]
I'm using the rom with firmware 2.11.651.19 but I had to unlock SIM.
If I flashing the new rom with firmware 3.33.651.2, I'll have to unlock SIM again?
could you share the mod too?
Thanks so much
working great for me so far!
dmonium said:
Hi mate @[email protected]
I'm using the rom with firmware 2.11.651.19 but I had to unlock SIM.
If I flashing the new rom with firmware 3.33.651.2, I'll have to unlock SIM again?
could you share the mod too?
Thanks so much
Click to expand...
Click to collapse
I'm not sure about Sim unlock, never did it before. I'd think you'd be fine tho
thanks for the leak lol... god i havnt seen a leak since the evo days.
Trying this.. EDIT: Worked ... Fastboot flash method didn't work (kept rebooting to recovery) 'dd' worked a treat.
Took a long time to 'dd' please be patient
Anyway when the RUU.exe is available
when the link is live it should be.....
NOT A WORKING LINK AT TIME OF POST
http://dl3.htc.com/application/RUU_HIMA_WHL_M60_SENSE70_SPCS_MR_Sprint_WWE_3.33.651.2.exe
Based on Dev Edition M8 and M9 file names
dmonium said:
Hi mate @[email protected]
I'm using the rom with firmware 2.11.651.19 but I had to unlock SIM.
If I flashing the new rom with firmware 3.33.651.2, I'll have to unlock SIM again?
could you share the mod too?
Thanks so much
Click to expand...
Click to collapse
SAFE AS Tested myself.
To all my unlocked Sprint Pepz...
WE ARE GOOD (s-off) obviously to flash the ZIP
Some Screen shots of some of the mods I like and use if anyone wants. I'll update when official comes too
{
"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"
}
Quick question when you say boot into recovery for the boot and system img you mean twrp? Then while in twrp run those commands? Just a lil confused sorry if its a stupid question dont want to mess anything up..and thanks a ton for the leak!
billyho7993 said:
Quick question when you say boot into recovery for the boot and system img you mean twrp? Then while in twrp run those commands? Just a lil confused sorry if its a stupid question dont want to mess anything up..and thanks a ton for the leak!
Click to expand...
Click to collapse
It's not a stupid question and I should have been more specific. Yes twrp recovery and do those commands in terminal in twrp, and you're welcome, glad to share
Sent from my 0PJA2 using Tapatalk
[email protected] said:
It's not a stupid question and I should have been more specific. Yes twrp recovery and do those commands in terminal in twrp, and you're welcome, glad to share
Sent from my 0PJA2 using Tapatalk
Click to expand...
Click to collapse
Ok thanks i just never heard of booting into recovery and then running commands on the computer so i wanted to be sure
[email protected] said:
It's not a stupid question and I should have been more specific. Yes twrp recovery and do those commands in terminal in twrp, and you're welcome, glad to share
Sent from my 0PJA2 using Tapatalk
Click to expand...
Click to collapse
Sorry but when i go to terminal command in twrp how do i input those commands i just see folders to choose from?
billyho7993 said:
Sorry but when i go to terminal command in twrp how do i input those commands i just see folders to choose from?
Click to expand...
Click to collapse
It's letting you choose a directory to open terminal in. Just check the folder check box in the root directory when you first choose terminal. Then
adb shell enter
Then do these for boot and system one at a time and enter
dd if=/sdcard/boot.img of=/dev/block/bootdevice/by-name/boot
dd if=/sdcard/system.img of=/dev/block/bootdevice/by-name/system
Boot goes fairly quickly but system will take a few
[email protected] said:
It's letting you choose a directory to open terminal in. Just check the folder check box in the in the root directory when you first choose terminal. Then
adb shell enter
Then do these for boot and system one at a time and enter
dd if=/sdcard/boot.img of=/dev/block/bootdevice/by-name/boot
dd if=/sdcard/system.img of=/dev/block/bootdevice/by-name/system
Boot goes fairly quickly but system will take a few
Click to expand...
Click to collapse
Thanks one more thing i do all this then flash superSU and then rom in that order correct? Thanks for your help
billyho7993 said:
Thanks one more thing i do all this then flash superSU and then rom in that order correct? Thanks for your help
Click to expand...
Click to collapse
SuperSU zip gets flashed last. Do not install su from the twrp popup when ready to boot up, choose do not install
[email protected] said:
SuperSU zip gets flashed last. Do not install su from the twrp popup when ready to boot up, choose do not install
Click to expand...
Click to collapse
OK I got rom booted just need to flash superSU..I never got that message in twrp..what is that itson app? During setup I kept getting pop-ups every second that it stopped and it was annoying as hell
Quick Questiions
I'm on a stock bootloader-locked device on 2.11.651.19.
Q1. I'm planning to Unlock Bootloader > Root > Install TWRP. Then will I be able to install this ROM with S-ON?
Q2. I don't have an external (micro SD card). The method says "copy 0PJAIMG.zip to root of external SD card". Will this work if I use the internal memory?
I've had flashing experience with non-htc devices but this is a different game. I'll appreciate some community support. Thanks.
radio firmware
So it looks to me the radio is the same version as the 2.11 release. Anyone else notice trouble with the radio when connected to lte band 41? a lot of time i get no data throughput, reminds me of the previous radio released by sprint/htc for the m9 about 6 months ago when b41 had all sorts of trouble. Just throwing that out there, wondering if anyone else is seeing the same . Love the look so far, i am glad they made sense look like it does for the A9. That was my favorite thing about the A9 how the status bar has been scaled back a bit on the sense side and looks more like vanilla.
In the included "read me" text file it states that the system and boot images can also be flashed through bootloader. Since this is the way I flash firmware due to the sd card method not working for me I decided to go this route. I flashed firmware twice as I always do and I recieved no errors. I flashed both system.img and boot.img the same way and again no errors. I then booted in recovery and flashed the SU zip but it gave me errors trying to patch boot. I tried to reboot and got nothing. It kept booting back into recovery. I went ahead and reflashed system and boot using the terminal in TWRP. Then I flashed SU and this time it took a much longer time and didnt display the patching boot errors. Its been on the HTC One splash screen for over 10 minutes now. Not sure how much longer to wait before I hit the panic button. Seems to be alittle longer to boot than I remember from other clean installs.
Where do we find the mods such as APM?
UPDATE ...So after about 20 minutes still stuck on HTC screen. Went back to recovery to try again. When I type adb shell in TWRP terminal, it says adb not found.
2nd UPDATE...the 2nd try same result. Hangs on the HTC screen for 30 minutes. Restored my Badboyz rom and will wait for a flashable zip or the final release.
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
TWRP has been successfully ported to the Galaxy J7 Refine (SM-J737P) (Oreo 8.0)ROOT METHOD POSTED BELOW IN POST #2Giving credit where credit is due:
@Dark98 for compiling the TWRP.img
@☆KØŁØЯΛĐØ☆ providing device files + testing/porting
@topjohnwu for Magisk
DISCLAIMER: This is NOT in Odin flashable .tar format. Due to sporadic updates in security & Oreo, Odin won't be much help here.
This has been tested & confirmed working on device build R16NW.J737PVPU1ARG3. It should work on other versions.
UPDATE: This will work on any Oreo version as well, including the new April 1, 2019 R16NW.J737PVPS3ASC2 update.
The patched_boot.img.tar I've attached will not work if you are on a different version of Oreo. You must provide your own patched_boot.img.tar that coincides with your respective version.
Proof of port is in the screenshot below (I've underlined the device build)
{
"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"
}
There is a downside & an upside:
- The downside is that after you flash TWRP & reboot, you will lose root.
- The upside is that TWRP will remain so all you need to do to regain root is flash the Magisk-v18.1.zip in Recovery.
Procedure:
- In order to flash, you need an app that will do so without booting into recovery. View attachment Flashify.apk is the ideal choice for this procedure.
- Flash TWRP in Flashify but do not reboot from the app itself. Power off your device & boot into [TWRP] Recovery manually.
PAY ATTENTION TO THESE NEXT FEW STEPS!!!
- Extract the twrp.img from View attachment J737P_TWRP.zip
- Flash through Flashify, then boot into TWRP for the first time
- Now that you have booted into TWRP the first time, Swipe to allow modifications
- Navigate to Wipe > Format Data > type yes when prompted (this will not delete any files you have in your Internal Storage)
- Once the format is completed, go to TWRP home screen & Reboot > Power Off
DO NOT REBOOT TO SYSTEM
- Once device powers off, reboot back into TWRP (yes you will boot into recovery twice)
If you fail to immediately boot back into TWRP, you will brick & have to start over. The fiirst reboot is to clear out (wipe) the /Data partition to make room for your new recovery. Wiping will not delete any internal storage items. However, it will return a value of 0 for /Data. The second boot is to secure TWRP as your new Recovery, as well as fix the /Data return value.
- Now that you have secured TWRP, go ahead & make a TWRP backup as a safety precaution before you reboot. The backup could be considered "stock" with TWRP as the Recovery. The reason being is that you will lose root after formatting /Data. No worries, you will get it back.
After creating the backup, follow these next steps very carefully!!
You will now flash Magisk-v18.1 to regain root. With the new security measures Samsung put in late 2017, you will need to flash 2 .zip files after to ensure that root sticks.
YOU NEED TO FLASH THESE FILES IN ORDER. DO NOT WIPE CACHE AFTER EACH FLASH. DO NOT REBOOT AFTER EACH FLASH. FLASH EACH PACKAGE ONE AT A TIME. WAIT UNTIL THE 3RD FLASH IS COMPLETE & THEN REBOOT DEVICE. IT WILL TAKE SEVERAL MINUTES SO BE PATIENT.
(Still in TWRP)
- Go to Home & select Instal
- In this order, flash one at a time:
View attachment Magisk-v18.1(18100).zip
View attachment no-verity-opt-encrypt-6.0.zip
View attachment RMM-State_Bypass_Mesa_v2.zip
DO NOT WIPE THE CACHE
Screenshots of proper installation (in order):
- Reboot device normally. If you do not flash the dm-verity & RMM .zip files in order, you will bootloop & have to start over.
- When you get to your home screen, you will receive a notification to update Magisk. Update by either selecting the notification or manually through Magisk Manager.
- Allow Magisk to install the update; do not update through TWRP.
ĐØΠΞ
[ROOT] Galaxy J7 Refine (SM-J737P) (Oreo 8.0)
FOLLOW THESE DIRECTIONS. I AM NOT RESPONSIBLE IF YOU BRICK YOUR DEVICE.
View attachment 4733553 View attachment 4733552
I have given you a freebie by providing the patched_boot.img.tar, thus saving you a few steps
All files needed are uploaded to my Drive: https://drive.google.com/folderview?id=1-8CGkYef58I-DrkyOshRFniecO_0dBDc
NOTICE: Patched_boot.img.tar is solely for the J737PVPU1ARG3 software version. Any attempt to flash to a different version will result in a bootloop. You must patch + flash your own stock boot.img if you are on a different software version.
YOU MUST PAY ATTENTION TO THE FOLLOWING
- In the Bli5zkrieg.zip you extracted, load up Odin_v13.1 (non-patched)
- Load only the BL/AP/CP files from your stock firmware into Odin
- As soon as the flashing process ends, you must reboot quickly back into Download Mode. You have to be quick. If you allow the device to begin booting up, it makes the rooting process more difficult.
Assuming you followed directions...
- Close Odin_v13.1 & unplug your device while still remaining in Download Mode
- Launch Odin_v13.1 [Patched] & load up the patched_boot.img.tar in the AP slot
- Reconnect device & proceed to flash
- Device will reboot with "Verification Failure" so you must reset (this is part of root) (it does not activate FRP lock)
- When device reboots to Setup Wizard, skip through it. Do not add any accounts (Google or Samsung). Do not consent to giving any device data for whatever purposes (they will ask twice; look carefully)
- On the home screen, unlock Dev Options &allow USB Debugging. OEM should already have been unlocked
- Connect device to your pc & in the ZeeToolz folder you extracted, run CMD.exe
- Input adb devices to ensure proper connection
- Input adb install -r MagiskManager-v7.0.0.apk to install MM to your device
- Open MagiskManager & make sure everything is good to go (see attached screenshot)
- If everything is done properly then you will see a superuser tab in the left side-bar, indicating root access
ĐØΠΞ
Thanks for making / working on this man. Running butter smooth on my SM-j737P (J737PVPU2ARJ2.)
note: I had to use an sdcard to store the proper files to be able to flash in twrp. adb sideload nor mtp would not work while in twrp during the initial install.
I used the files below.
Root Files (patched boot image): https://drive.google.com/file/d/1xan3RfRs4x4As7ONxLtW-WXKh_KvjyXY/view
Unbrick Files (stock J737PVPU2ARJ2) : https://androidfilehost.com/?fid=11410932744536992025
Cheers!
kinehumane said:
Thanks for making / working on this man. Running butter smooth on my SM-j737P (J737PVPU2ARJ2.)
note: I had to use an sdcard to store the proper files to be able to flash in twrp. adb sideload nor mtp would not work while in twrp during the initial install.
I used the files below.
Root Files (patched boot image): https://drive.google.com/file/d/1xan3RfRs4x4As7ONxLtW-WXKh_KvjyXY/view
Unbrick Files (stock J737PVPU2ARJ2) : https://androidfilehost.com/?fid=11410932744536992025
Cheers!
Click to expand...
Click to collapse
No problem man. I didnt think to test sideload or mtp as I always use an SDcard (comes in handy lol). It was a tad bit tedious to get the whole process down due to Oreo. That being said, ensure that you have a backup. Editing any part of the system (ie. Build.prop) will result in failure. I installed the Time Zones update & it failed. As far as MagiskSU goes, I like the Modules but prefer SuperSU root. Will see about incorporating it in the near future
This is likely a silly question, but I downloaded and installed flashify, have put the TWRP.img on the SD Card, but for some reason, flashify won't go further than giving me the option of flashing a recovery... one tap and the app is frozen....
So, is there another app that will flash the image, so as to follow the directions in the OP? Flashify doesn't seem to be happening for me. Can't seem to find one that doesn't do a root-check first, refusing to do the deed if root isn't there yet?
Trying from square 1, to the point that I did a total backup, factory reset, and am starting with a reset phone.
pauljulian said:
This is likely a silly question, but I downloaded and installed flashify, have put the TWRP.img on the SD Card, but for some reason, flashify won't go further than giving me the option of flashing a recovery... one tap and the app is frozen....
So, is there another app that will flash the image, so as to follow the directions in the OP? Flashify doesn't seem to be happening for me.
Click to expand...
Click to collapse
I experienced the sluggish behavior as well. Manually go into Magisk Manager > SuperSU & make sure Flashify has been granted root access. I've noticed Magisk is rather slow when it comes to asking or granting root access on some apps. If you cannot get it to flash with Flashify, I'd suggest going with Root Essentials. Its an all-in-one root toolbox with a flashing mechanism
Root Essentials won't work as a secondary flasher bc it requires a custom recovery to be installed beforehand. Flashify will be your best bet so try all possibilities to get it to work
☆KØŁØЯΛĐØ☆ said:
I experienced the sluggish behavior as well. Manually go into Magisk Manager > SuperSU & make sure Flashify has been granted root access. I've noticed Magisk is rather slow when it comes to asking or granting root access on some apps. If you cannot get it to flash with Flashify, I'd suggest going with Root Essentials. Its an all-in-one root toolbox with a flashing mechanism
Click to expand...
Click to collapse
I'll give it a try... thanks... Just trying to follow the instructions to the letter, and I'm laboring under the assumption that the TWRP image has to be on there before going on to the next steps...
pauljulian said:
I'll give it a try... thanks... Just trying to follow the instructions to the letter, and I'm laboring under the assumption that the TWRP image has to be on there before going on to the next steps...
Click to expand...
Click to collapse
I revised my last comment. TWRP is to be flashed after you have rooted with Magisk. The posts are a little offputting due to the order they are in & I apologize for that lol Root with Magisk first & then you can install TWRP
pauljulian said:
I'll give it a try... thanks... Just trying to follow the instructions to the letter, and I'm laboring under the assumption that the TWRP image has to be on there before going on to the next steps...
Click to expand...
Click to collapse
Hmm... Root Essentials tells me it failed to install the image...
If flashify does work, but is just seriously sluggish, I can live with that if it's just a matter of setting it aside until it loads it up, that's cool... just trying to get the TWRP.img on there per instructions... Selecting the Install Recovery Image craps out... I have a copy of that image on both the emulated and the external SD, just to see if it was that... doesn't seem to work.
My understanding from the instructions is that I can't flash this particular TWRP image with Odin...
Does the patched boot image go on first, or what? I've been around here for a while, and have flashed other phones in the past, but this one is a challenge.
---------- Post added at 07:01 PM ---------- Previous post was at 06:58 PM ----------
☆KØŁØЯΛĐØ☆ said:
I revised my last comment. TWRP is to be flashed after you have rooted with Magisk. The posts are a little offputting due to the order they are in & I apologize for that lol Root with Magisk first & then you can install TWRP
Click to expand...
Click to collapse
OK... that makes more sense... I'll do that first, then go on to the other... Thanks, friend.
pauljulian said:
Hmm... Root Essentials tells me it failed to install the image...
If flashify does work, but is just seriously sluggish, I can live with that if it's just a matter of setting it aside until it loads it up, that's cool... just trying to get the TWRP.img on there per instructions... Selecting the Install Recovery Image craps out... I have a copy of that image on both the emulated and the external SD, just to see if it was that... doesn't seem to work.
My understanding from the instructions is that I can't flash this particular TWRP image with Odin...
Does the patched boot image go on first, or what? I've been around here for a while, and have flashed other phones in the past, but this one is a challenge.
---------- Post added at 07:01 PM ---------- Previous post was at 06:58 PM ----------
OK... that makes more sense... I'll do that first, then go on to the other... Thanks, friend.
Click to expand...
Click to collapse
Flashing with Flashify is under the assumption that you dont have a lot of 3rd party apps installed. If you are logged into your Google or Samsung account(s) & have your data being backed up, it creates a more sluggish environment.
First, follow the rooting guide I posted above. If you do, you should have root access via Magisk with very little apps installed & you arent logged into any Account(s). After you have that, then install Flashify. Manually set root access if need be. Make sure you have all your device security settings disabled, Dev Options, USB Debugging, blah blah blah
We will get you root access & TWRP installed bud
pauljulian said:
My understanding from the instructions is that I can't flash this particular TWRP image with Odin...
Does the patched boot image go on first, or what? I've been around here for a while, and have flashed other phones in the past, but this one is a challenge.
---------- Post added at 07:01 PM ---------- Previous post was at 06:58 PM ----------
OK... that makes more sense... I'll do that first, then go on to the other... Thanks, friend.
Click to expand...
Click to collapse
When you go to get root, you will need your stock firmware (BL/AP/CP files). My directions are pretty straight forward. Unzip the tools, load up Odin (non-patched), flash BL + AP + CP in their respective slots. Make sure that after you flash the stock, you instantly reboot back into Download Mode. Close the current Odin & open the patched Odin. Load the patched_boot.img.tar I provided to the AP slot & flash. It will reboot with a Verification Failure, thus forcing you to format your device. When your device reboots, skip through Setup Wizard, dont link any Google or Samsung accts. On the home screen, use cmd terminal on your pc to install the MagiskManager.apk. Once sideload, you will see root access & more than likely a toast notification asking you to update Magisk.
Rashr (View attachment de.mkrtchyan.recoverytools.apk) works as a good substitute for Flashify. You just need to move the TWRP.img to the root of your sdcard (/emulated/0/sdcard) & flash it through the Recovery from Storage option. Reboot into TWRP &continue following the instructions I've posted
pauljulian said:
Hmm... Root Essentials tells me it failed to install the image...
If flashify does work, but is just seriously sluggish, I can live with that if it's just a matter of setting it aside until it loads it up, that's cool... just trying to get the TWRP.img on there per instructions... Selecting the Install Recovery Image craps out... I have a copy of that image on both the emulated and the external SD, just to see if it was that... doesn't seem to work.
My understanding from the instructions is that I can't flash this particular TWRP image with Odin...
Does the patched boot image go on first, or what? I've been around here for a while, and have flashed other phones in the past, but this one is a challenge.
---------- Post added at 07:01 PM ---------- Previous post was at 06:58 PM ----------
OK... that makes more sense... I'll do that first, then go on to the other... Thanks, friend.
Click to expand...
Click to collapse
OK... one more silly question... the patched.boot file gets loaded into the AP slot in Odin, and not the BL slot? Reason I'm asking is that after flashing that from the AP slot, the device sits at the Boot logo, and sits there...
As I had tried a few other things, and needed to add my account info to grab the Root Essentials, I just said the hell with it, and re-flashed the stock files.. then without anything other than Dev mode enabled, I booted into download mode and flashed the patched.boot tar file in the AP slot, as directed, and here it sits.
I get this happening, you make it to Albuquerque, and I owe you a few beers...
---------- Post added at 08:09 PM ---------- Previous post was at 08:07 PM ----------
pauljulian said:
OK... one more silly question... the patched.boot file gets loaded into the AP slot in Odin, and not the BL slot? Reason I'm asking is that after flashing that from the AP slot, the device sits at the Boot logo, and sits there...
As I had tried a few other things, and needed to add my account info to grab the Root Essentials, I just said the hell with it, and re-flashed the stock files.. then without anything other than Dev mode enabled, I booted into download mode and flashed the patched.boot tar file in the AP slot, as directed, and here it sits.
I get this happening, you make it to Albuquerque, and I owe you a few beers...
Click to expand...
Click to collapse
OK... missed the immediately into download mode... Once more, with feeling.
When all else fails, go back and read the instructions CAREFULLY... <lol>
Reflashing the stock files and starting over...
pauljulian said:
OK... one more silly question... the patched.boot file gets loaded into the AP slot in Odin, and not the BL slot? Reason I'm asking is that after flashing that from the AP slot, the device sits at the Boot logo, and sits there...
As I had tried a few other things, and needed to add my account info to grab the Root Essentials, I just said the hell with it, and re-flashed the stock files.. then without anything other than Dev mode enabled, I booted into download mode and flashed the patched.boot tar file in the AP slot, as directed, and here it sits.
I get this happening, you make it to Albuquerque, and I owe you a few beers...
---------- Post added at 08:09 PM ---------- Previous post was at 08:07 PM ----------
OK... missed the immediately into download mode... Once more, with feeling.
When all else fails, go back and read the instructions CAREFULLY... <lol>
Reflashing the stock files and starting over...
Click to expand...
Click to collapse
Lol The directions are on point. They're solid. You just have to pay attention ?
Here's the old fart with another question....
After flashing the stock files as instructed, I immediately hit the download mode as soon as the screen went black. Flashed the patched boot as instructed, and, as you stated, it would go immediately into recovery due to verification error.
I wiped the cache and hit factory reset, then reboot.
It's now sitting at the boot logo screen, and has been there for more than 1/2 hour.
Honest! I followed your instructions to the letter, and I recall first boot after rooting taking a while to come up into the system on other devices I've had, but I don't recall first boot taking anywhere this long.
I'm stumped.
pauljulian said:
OK... one more silly question... the patched.boot file gets loaded into the AP slot in Odin, and not the BL slot? Reason I'm asking is that after flashing that from the AP slot, the device sits at the Boot logo, and sits there...
As I had tried a few other things, and needed to add my account info to grab the Root Essentials, I just said the hell with it, and re-flashed the stock files.. then without anything other than Dev mode enabled, I booted into download mode and flashed the patched.boot tar file in the AP slot, as directed, and here it sits.
I get this happening, you make it to Albuquerque, and I owe you a few beers...
---------- Post added at 08:09 PM ---------- Previous post was at 08:07 PM ----------
OK... missed the immediately into download mode... Once more, with feeling.
When all else fails, go back and read the instructions CAREFULLY... <lol>
Reflashing the stock files and starting over...
Click to expand...
Click to collapse
pauljulian said:
Here's the old fart with another question....
After following the instructions, yes, the phone went immediately into recovery mode, after flashing the error message you described.
I went ahead and did the factory reset, and told it to reboot... It's been sitting at the boot logo for about 25 minutes.
Should it take this long for first boot, after flashing the patched.boot.img.tar? I loaded the tar into the AP slot, as instructed. After flashing it, and the screen going to black, hit the download mode immediately... I flashed it, as said, at reboot, it went into recovery after a quick error message... I did factory reset, then rebooted normally.
I really have no idea... I'll let it keep sitting, to see if it finally boots, but this seems like a terribly long time that it's' at the bootscreen.
Click to expand...
Click to collapse
You seem to be rebooting into Recovery an awful lot. You shouldn't be booting into recovery mode at all when attempting to root. Recovery mode only needs entered during either process whenever you attempt to flash TWRP. Luckily for you, I dont have sh¡t to do tonight so I can help you until you get it right lol Shoot me an email at [email protected] & we can get started. I dont want to clutter up this feed with a revised how-to guide lol
Other Variants
I tried on my j737p ( rooting worked like a charm ) however your patched boot image had to be substituted in order for my j737 variant to go further than a boot loop.
for twrp the flash of the recovery image went over fine and booted into twrp nicely. however i flashed those 3 files one at a time and all 3 at once both in order each time a few different times to verify. regardless what i do it sends me into a boot loop upon leaving twrp.
do you have any recommendations on what to modify in your procedure for my variant?
my specs are as follows:
Model - SM-J737P
ROM - J737PVPS2ASA1
Android - 8.0
SDK - 26
Kernel - 4.4.13-14521356 [email protected] gcc 4.9.x 20150123
Processsor - armv8l
I have 2 of the same j737p phones so im using one as my test subject before i move each step to my daily j737p.
I am comfortable with beta experimentation within reason.
on a side note - If anyone has my variant and would like the root to work I can send you the patched boot image that I used to get the root to take and let you boot into android successfully.
fsceo said:
I tried on my j737p ( rooting worked like a charm ) however your patched boot image had to be substituted in order for my j737 variant to go further than a boot loop.
for twrp the flash of the recovery image went over fine and booted into twrp nicely. however i flashed those 3 files one at a time and all 3 at once both in order each time a few different times to verify. regardless what i do it sends me into a boot loop upon leaving twrp.
do you have any recommendations on what to modify in your procedure for my variant?
my specs are as follows:
Model - SM-J737P
ROM - J737PVPS2ASA1
Android - 8.0
SDK - 26
Kernel - 4.4.13-14521356 [email protected] gcc 4.9.x 20150123
Processsor - armv8l
I have 2 of the same j737p phones so im using one as my test subject before i move each step to my daily j737p.
I am comfortable with beta experimentation within reason.
on a side note - If anyone has my variant and would like the root to work I can send you the patched boot image that I used to get the root to take and let you boot into android successfully.
Click to expand...
Click to collapse
I have since revised my instructions for root, starting that my guide is very device specific & you will have to tweak instructions in order to accommodate your version.
As far as TWRP goes, did you boot into TWRP twice? Once for the initial install to format the /data partition & the second to secure TWRP along with flashing the files? You need to do it simultaneously & in order otherwise it won't work
It's a happenin' thang!!!!
Many thanks to Killer for all the help! Decent person stayed up with me troubleshooting until 6:30 this morning... It's working!!!!
(now, if I can find the damned SIM card that bounced off my desk into the carpeting, I'll have basically a laptop replacement! (well, for a lot of things, that is... <chuckle>)
pauljulian said:
It's a happenin' thang!!!!
Many thanks to Killer for all the help! Decent person stayed up with me troubleshooting until 6:30 this morning... It's working!!!!
(now, if I can find the damned SIM card that bounced off my desk into the carpeting, I'll have basically a laptop replacement! (well, for a lot of things, that is... <chuckle>)
Click to expand...
Click to collapse
Not a problem buddy. Was fun & if you have any more questions, you have my contact info
fsceo said:
I tried on my j737p ( rooting worked like a charm ) however your patched boot image had to be substituted in order for my j737 variant to go further than a boot loop.
for twrp the flash of the recovery image went over fine and booted into twrp nicely. however i flashed those 3 files one at a time and all 3 at once both in order each time a few different times to verify. regardless what i do it sends me into a boot loop upon leaving twrp.
do you have any recommendations on what to modify in your procedure for my variant?
my specs are as follows:
Model - SM-J737P
ROM - J737PVPS2ASA1
Android - 8.0
SDK - 26
Kernel - 4.4.13-14521356 [email protected] gcc 4.9.x 20150123
Processsor - armv8l
I have 2 of the same j737p phones so im using one as my test subject before i move each step to my daily j737p.
I am comfortable with beta experimentation within reason.
on a side note - If anyone has my variant and would like the root to work I can send you the patched boot image that I used to get the root to take and let you boot into android successfully.
Click to expand...
Click to collapse
Sent you a pm, but having trouble rooting the same variant