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.
Related
Q&A for Unofficial TWRP Padfone X
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:
Cant seem to get it right.
AdamOutler said:
Introduction:
The padfone X was released last friday and I wanted TWRP. As you may know; @Dees_Troy is on vacation. So, I hacked together this "repack" version which should have all features in order. One caveat with this version though, when launching recovery after it's installed, the screen must time out (2-minutes) before you can push power and see it.
Warning:
Even though you may simply be using your device and just running apps, you are modifying your device. There is no 100% back to stock. You can find a fastboot flashable stock recovery here, but there is no stock system. While this mod did not trigger a "modified status" on my device, I cannot guarantee the same for you. This is a very new device and unless you're one of the few, brave and anxious, it may be in your best interest to wait until a stock firmware update, back-to-stock flash, or even an official XDA-Developers forum has been created for this device.
you will need:
1.The Unofficial TWRP recovery image
2.SuperSU installed on your device
3.TowelRoot installed on your device. You will need to enable third-party sources.
4.Terminal access (pick the one you're more comfortable with)
4a.ADB
4b.Terminal emulator
installation:
If you chose to use ADB, then use these ADB Instructions. Otherwise skip down to Terminal Emulator Instructions.
ADB Instructions
Ensure you have installed SuperSU and TowelRoot.
Launch the TowelRoot app, follow instructions, and let it reboot your device.
navigate to the folder you downloaded ADB (and dll's if you're on windows) and execute the following command.
Code:
adb shell "curl 'http://builds.casual-dev.com/files/Asus/Padfone%20X/TWRP-Nexus5repack-AO1.img'>/sdcard/recovery.img; su -c 'dd if=/sdcard/recovery.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery' bs=4096; sync; reboot recovery;"
check your device for any pop-ups and grant root access to shell.
wait 2 minutes after the screen is black, and then press power button. This is due to a difference between Nexus5 and PadfoneX which will be fixed in an official version later.
Terminal Emulator Instructions
Ensure you have installed SuperSU and TowelRoot.
Launch the TowelRoot app, follow instructions, and let it reboot your device.
Launch Terminal Emulator and copy-pasta the following into it.
Code:
curl 'http://builds.casual-dev.com/files/Asus/Padfone%20X/TWRP-Nexus5repack-AO1.img'>/sdcard/TWRPrecovery.img; su -c 'dd if=/sdcard/TWRPrecovery.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery' bs=4096; sync; reboot recovery;
check your device for any pop-ups and grant root access to shell.
wait 2 minutes after the screen is black, and then press power button. This is due to a difference between Nexus5 and PadfoneX which will be fixed in an official version later.
Conclusion
Congratulations, you've got TWRP installed on your device. Now you can back up, restore, and install TWRP Flashable Zips. Please leave a comment and tell others how it worked. This worked great for me, Image below.
{
"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"
}
Click to expand...
Click to collapse
So after installing all the apps where do I put the twrp image at? I have towel root installed, superSU installed, twrp image on my SD card. I go to ADB and copy and paste the code and it just reboots the phone to the asus logo and does nothing else til a reboot. I have tried the terminal method and manually wrote in the code and it does nothing. I saw it do something on the terminal and waited for black screen, but after pressing the power button all it does is wake the screen to were i was. Been trying for days...
Got it, sort of...
I used flashify to get the twrp recovery image to install. Got everything running but TWRP will not read my SD Card and also I cannot mount the phones internal data. I wiped the device including the system and now all I can do is enter recovery. When I tried to install the stock rom zip file before I wiped the internal data they failed right away. What could be causing these issues? Need a way to get the rom on the phone and also install it, both of which are not working.
How to uninstall
I ask because I can't do the new att update without removing
-Epix- said:
How to uninstall
I ask because I can't do the new att update without removing
Click to expand...
Click to collapse
Use the same command that you use to flash TWRP, but instead with the stock recovery image. Let me know if you need a mirrored link.
What file did you have wrong?
I am having the same problem with my padfone X, where when I enter recovery it gets stuck on the Asus screen. Can you help me understand what file you ended up using and the command line you used.
Thanks,
This was the post that is like mine
Epix,
This earlier post is where I am at in the process.
Thanks,
Jack
I got it to work, but I had to take a different route
Download the TWRPRecovery File from here:
http://forum.xda-developers.com/showthread.php?t=2790542&page=3 (look for post 24)
Then rename it TWRPRecovery.img. Then save it to your internal folder. Once it is saved there. Follow all instructions previous to allow Shell access to the phone. Once you have shell access or if you are using a terminal app. The following code will install the TWRP recovery. It still takes the 2 minutes discussed previously but it works.
su -c 'dd if=/sdcard/TWRPrecovery.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery' bs=4096; sync; reboot recovery;
If you are trying to install the latest update, You will need to follow these steps here:
http://forum.xda-developers.com/padfone-x/development/padfone-x-stock-nandroid-backups-t2858573
Once you have your system back to stock and your ready to restore your original Stock Recovery (which is nessisary for the update) download the file here and copy it to your Internal folder:
http://forum.xda-developers.com/pad...dfone-x-stock-nandroid-backups-t2858573/page2 (look for post #12)
You will do the same with this file except rename it StockRecovery.img
and use the code
su -c 'dd if=/sdcard/StockRecovery.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery' bs=4096; sync; reboot recovery;
Everything works. I just finished updating my phone and rerooting it with towelroot version 1.
Have a good afternoon..
Stuck at logo boot
i read that TWRP mod can help me to go back to original ROM , because now im stuck at BOOT LOGO ( i tried use TB to delete some files, and now im kindda sorry for that ;d ). How to go to TWRP mod sir?? and things i've done is right??
http://i.imgur.com/Zyoq8E0.jpg
---------- Post added at 04:05 AM ---------- Previous post was at 03:38 AM ----------
"]http://
[/IMG]
Help me out with TWRP
https://drive.google.com/open?id=0BzzSvHdGBtI9Q2l0THJrUXVxWlU&authuser=0
https://drive.google.com/open?id=0BzzSvHdGBtI9WUZQQmNUMGJYTUE&authuser=0
i enter the code to Terminal Emulator but it wont go to TWRP mod , my phone shows like that and that's all.
I tried ADB-thing way but when i turn on the adb.exe it always turn off but dont know why like when i tried start -> run -> cmd.
hope you can help me out with that. Ty sir
Asus PadFone S
Compatible with Asus PadFone S? ?
---------- Post added at 05:51 PM ---------- Previous post was at 05:42 PM ----------
Compatible with Asus PadFone S ?
Failed to intall unofficial TWRP
Hi guys. I've tried the method using Terminal (thread http://forum.xda-developers.com/showthread.php?t=2790542 )
I have freshly factory reseted my phone and SuperSU + TowelRoot 1 installed and working.
Any ideas what could be wrong? It just stops like that. And phone freezes on black screen when attempting to enter the Recovery.
I have pasted http instead of https because the latter won't work at all.
curl 'http://builds.casual-dev.com/files/CASPAC/Asus/Padfone%20X/TWRP-Nexus5repack-AO1.img'>/sdcard/TWRPrecovery.img; su -c 'dd if=/sdcard/TWRPrecovery.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery' bs=4096; sync; reboot recovery;
So where can you download twrp to
ASUS PadFone X ( Model T00D)
device is rooted on 4.4.2 and followed instructions to get TWRP but nothing works...tried TE method...doesn't work...tried ADB...that doesn't work either...tried adding recovery.img directly to sdcard...that doesn't work either...all I want is detailed instructions on how to get a custom recovery on this device...along with links that actually work..why is it so difficult to find usable intel...and please, don't paste the links...I have already read through all known links...I need UP TO DATE information as most the crap out there is from months ago...thank you
Edit #1 (Update)...using Rashr, I was able to get stock recovery back...attempted to flash TWRP...but upon reboot into recovery after waiting the two minutes out, ASUS logo then screen goes blank
Edit #2 (Update)...ok, finally, using Rashr, I was able to get TWRP!...wow, to all fellow rooters, all it takes is the Rashr app with root access and a copy of the TWRP.img downloaded to internal memory...make sure you wait the two minutes out (once when partition is flashed, and again when rebooting into recovery)
---------- Post added at 06:02 AM ---------- Previous post was at 05:06 AM ----------
tjsooley said:
So where can you download twrp to
Click to expand...
Click to collapse
Here: https:// builds.casual-dev.com/index.php?dir=CASPAC/Asus/Padfone%20X/&sort=size&order=asc
includes a stock recovery as well
asus padfone x stock rom
Does any one have the stock ROM? I'm having the 491 error in Play store app
I can't find the stock firmware anyware
l00kus said:
Does any one have the stock ROM? I'm having the 491 error in Play store app
I can't find the stock firmware anyware
Click to expand...
Click to collapse
Here are the stock nandroid backups
http://forum.xda-developers.com/padfone-x/development/padfone-x-stock-nandroid-backups-t2858573
asus padfone x stock rom
tjsooley said:
Here are the stock nandroid backups
http://forum.xda-developers.com/padfone-x/development/padfone-x-stock-nandroid-backups-t2858573
Click to expand...
Click to collapse
But it doesn't let me install any app no more.
What is to be done in this case?
l00kus said:
But it doesn't let me install any app no more.
What is to be done in this case?
Click to expand...
Click to collapse
do a factory reset it worked fine for me
asus padfone x stock rom
tjsooley said:
do a factory reset it worked fine for me
Click to expand...
Click to collapse
Already did that my friend and no difference
l00kus said:
Already did that my friend and no difference
Click to expand...
Click to collapse
Maybe a bad flash re root and reflash twrp and redownload the restore and reflash.
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
Heres the latest update from LG.
Must be at least 20f/g with TWRP to flash this.
To get TWRP go here: (Kdz to 20f if on 20g)
https://forum.xda-developers.com/showthread.php?t=3533338
Do NOT wipe system or you might get stuck in twrp bootloop.
Includes new 20H modem.
**********************
FLASHING INSTRUCTIONS
**********************
1. WARNING, MUST BE IN 20F/G. IF ON LINEAGE, DO NOT FLASH. YOU MUST KDZ TO 20F OR RESTORE 20F BACKUP FIRST.
2. DO NOT FORMAT SYSTEM.
2. TWRP BACKUP FIRST
3. Flash from TWRP.
DOWNLOAD
LG-V521-20H-Stock-Rooted.zip
https://www.androidfilehost.com/?fid=745425885120726661
Sent from my LG-V521 using Tapatalk
{
"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"
}
Does it include the modem?
I'm going to try from lineage.
Edit -flashed from lineage worked fine. It rebooted straight from twrp so i wasn't sure if the flash comppeted. After waiting at bootscreen i still wasn't sure so i did the volume down, power button combo and it booted into system fine.
Edit 2 - no root and loss twrp
Airtioteclint said:
Does it include the modem?
I'm going to try from lineage.
Edit -flashed from lineage worked fine. It rebooted straight from twrp so i wasn't sure if the flash comppeted. After waiting at bootscreen i still wasn't sure so i did the volume down, power button combo and it booted into system fine.
Edit 2 - no root and loss twrp
Click to expand...
Click to collapse
Lineage always messes up going back to stock roms. I've had this problem to on 20g to after being on lineage. You'll have to kdz to 20f and get twrp. I had put this on the flashing instructions you must be on 20f/g. .
It does include modem.
Sent from my SM-G955U using Tapatalk
MicroMod777 said:
Lineage always messes up going back to stock roms. I've had this problem to on 20g to after being on lineage. You'll have to kdz to 20f and get twrp. I had put this on the flashing instructions you must be on 20f/g. .
It does include modem.
Sent from my SM-G955U using Tapatalk
Click to expand...
Click to collapse
Yeah kdz 20f and was able to get root back. Reinstalled your 20h and everything's working flawlessly. I was having problems with my touchscreen being a little laggy and I think your rom fixed it. :good:
Any way to install this update from SD card on stock recovery? I get error Everytime the regular way. Thanks
Hawksronny said:
Any way to install this update from SD card on stock recovery? I get error Everytime the regular way. Thanks
Click to expand...
Click to collapse
Impossible.
Sent from my SM-G955U using Tapatalk
MicroMod777 said:
Impossible.
Sent from my SM-G955U using Tapatalk
Click to expand...
Click to collapse
So even though there is an option to update from SD in stock recovery, it's impossible? Just want to confirm. Just doesn't make sense to me
Hawksronny said:
So even though there is an option to update from SD in stock recovery, it's impossible? Just want to confirm. Just doesn't make sense to me
Click to expand...
Click to collapse
Then try it! lol
Sent from my SM-G955U using Tapatalk
MicroMod777 said:
Then try it! lol
Sent from my SM-G955U using Tapatalk
Click to expand...
Click to collapse
I'm no developer. I just want to update without rooting or custom recovery. I try it 2 ways, and fails the normal way, and the stock recovery doesn't recognize the update.zip the 2nd way. I probably have it named wrong. Either way, I doubt it's impossible. Any help would be appreciated. Thanks
Hawksronny said:
I'm no developer. I just want to update without rooting or custom recovery. I try it 2 ways, and fails the normal way, and the stock recovery doesn't recognize the update.zip the 2nd way. I probably have it named wrong. Either way, I doubt it's impossible. Any help would be appreciated. Thanks
Click to expand...
Click to collapse
Its very, very impossible to flash this rom except per twrp.
LG uses security keys to flash anything from stock recovery.
Sent from my SM-G955U using Tapatalk
I don't want to flash a rom. I asked how to flash the stock update from the stock recovery because the update errors out when I try to do it the normal ota way. There is an option to update from SD in the stock recovery. It's just that it doesn't recognize the stock update.zip in the stock recovery because I probably don't have it named right. Was just wondering if anyone knew what to name it, where to download the update.zip, how to update with it etc. Didn't mean to offend anybody ?
Hawksronny said:
I don't want to flash a rom. I asked how to flash the stock update from the stock recovery because the update errors out when I try to do it the normal ota way. There is an option to update from SD in the stock recovery. It's just that it doesn't recognize the stock update.zip in the stock recovery because I probably don't have it named right. Was just wondering if anyone knew what to name it, where to download the update.zip, how to update with it etc. Didn't mean to offend anybody ?
Click to expand...
Click to collapse
No offence taken. All good. You just can't do that. [emoji4]
Sent from my SM-G955U using Tapatalk
Should i be able to downgrade from 20h to 20 f to root. I just got a new one on a warranty exchange and get an error in lgup at 4%. Sorry if this is off topic
same question, some body can check antirollback, this tab can downgrade from v521 v20h to v20f or mashmallow or not
Thanks
[ROM] T-Mobile LG G Pad X V521 20i Stock ROM Rooted TWRP\FF Backups Release 7/1/2017
A TWRP backup of a stock rooted v52120i:
Code:
https://drive.google.com/file/d/0B6L7kMY8TK7uZ2lPMUhtVmRINUk/view?usp=sharing
FlashFire Restore from backup:
Code:
https://drive.google.com/file/d/0B6L7kMY8TK7uQlFfY3lJTVl1X1k/view?usp=sharing
To install, move files to designated place (twrp/backups/{phoneid}/) or (FlashFire/backups).
at least 20f and root required.
saw nobody put it up so i decided i would.
Mine still has rooted 10c. How to update to this latest ROM and rooted ? TIA
Does 7.0 improve idling/sleeping battery ?
Yes that is probably one of its biggest changes vs MM.
Follow this guide to a T: https://forum.xda-developers.com/lg-g-pad-83/development/nougat-7-0-v521-guide-to-update-v521-lg-t3533338
then boot into recovery, copy my TWRP backup to internal/microsd/usb, in TWRP restore the system and boot partitions that are automatically checked.
Download the latest systemless or system mode supersu.zip and copy it to the main install folder C:\Program Files x86\Minimal ADB and Fastboot\.
Then in twrp click ADB sideload > do not check anything to erase > open minimal adb/fastboot and type adb sideload whateveryounamedyoursupersuzipfile.zip and you should be good to go.
Shockey0710 said:
Yes that is probably one of its biggest changes vs MM.
Follow this guide to a T: https://forum.xda-developers.com/lg-g-pad-83/development/nougat-7-0-v521-guide-to-update-v521-lg-t3533338
then boot into recovery, copy my TWRP backup to internal/microsd/usb, in TWRP restore the system and boot partitions that are automatically checked.
Download the latest systemless or system mode supersu.zip and copy it to the main install folder C:\Program Files x86\Minimal ADB and Fastboot\.
Then in twrp click ADB sideload > do not check anything to erase > open minimal adb/fastboot and type adb sideload whateveryounamedyoursupersuzipfile.zip and you should be good to go.
Click to expand...
Click to collapse
how did u get 20i ? and got it into permissive mode to obtain root ? know anything about 20h/i changelog ?
abced123 said:
how did u get 20i ? and got it into permissive mode to obtain root ? know anything about 20h/i changelog ?
Click to expand...
Click to collapse
i havent found a changelog nor have i looked though but new kernel version and various security fixes tho, and yes its getenforce permissive. from tmobile fota.
Can I use this in LG-V500???
Version 10.2.26.0
Version 10.2.24.0 ------------ > Stock/Root
Version 10.2.9.0
{
"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"
}
T4Ump said:
Version 10.2.24.0 - Link
Click to expand...
Click to collapse
so what do we do with this? fastboot it? is it like a full rom with magisk, rooted? cheers
vtec303 said:
so what do we do with this? fastboot it? is it like a full rom with magisk, rooted? cheers
Click to expand...
Click to collapse
Fastboot flash boot.img
It's only magisk for 10.2.24
You can create your own if you want, it's just 30s faster
Code:
fastboot flash boot boot.img
Thank you so much for posting this. I'd been trying for 2 days with twrp and magisk (19.1 and 19.2) and could never get past the recovery bootloop on my Mi 9.
Are you on global stable?
I am having boot loop too.
So far I haven't seen any root for 10.2.9.0
Does anyone have boot.img V10.2.9.0.PFAMIXM? I wanna try root, but only need that file
xxx
T4Ump said:
xxx
Click to expand...
Click to collapse
Hi, thanks for the patched one. Do you still have the stock one? My phone stuck at recovery mode
Edited: nvm. I'll download the fastboot ROM. Thank you anyway.
realm9thfeb said:
Are you on global stable?
I am having boot loop too.
So far I haven't seen any root for 10.2.9.0
Click to expand...
Click to collapse
I don't get it, what are you trying to achieve? Keep encryption and have root access?
Right now i'm on 10.2.9.0 running perfectly fine with root (magisk 19.1) but no encryption.
PriPhaze said:
I don't get it, what are you trying to achieve? Keep encryption and have root access?
Right now i'm on 10.2.9.0 running perfectly fine with root (magisk 19.1) but no encryption.
Click to expand...
Click to collapse
Hi, could you tell me how you root your phone? I installed magisk manager, chose boot.img then got magisk_patched.img. I flashed it via fastboot flash boot magisk_patched.img but I got stuck at stock recovery after rebooting. Did I miss any step?
syreg said:
Hi, could you tell me how you root your phone? I installed magisk manager, chose boot.img then got magisk_patched.img. I flashed it via fastboot flash boot magisk_patched.img but I got stuck at stock recovery after rebooting. Did I miss any step?
Click to expand...
Click to collapse
What i did was:
-Flash Stock Global ROM with Xiaomi Flash making sure to set the bat as clean all and NOT clean and lock!
-Once done it will automatically boot , and when it does simply reboot and hold down vol to go to the fastboot
-Flash Recovery img using minimal adb and fastboot
-Type "Fastboot reboot" and hold vol up to go to twrp
-In TWRP FORMAT data to get ride off encryption and reboot into recovery
-Again in TWRP now u can transfer files to the phone, so i patched "Disable_Dm-Verity_ForceEncrypt" and then patched Magisk 19.1
-That's it.
You can now reboot and it will start the phone configuration as normal but once you configure everything u will see that magisk is there and fully works.
Just one thing tho.... be careful if u will restore titanium back up apps...
Don't get me wrong; they do restore correctly but when you make a backup it becomes corrupted or at least that's what happened to me, so make sure to keep backups PRIOR to using the ROM saved in your PC or something.
EDIT: Maybe u should give a try to this twrp https://forum.xda-developers.com/Mi-9/development/recovery-unofficial-twrp-xiaomi-mi-9-t3905825, just got updated few hrs ago and so far seems it works really good.
syreg said:
Hi, could you tell me how you root your phone? I installed magisk manager, chose boot.img then got magisk_patched.img. I flashed it via fastboot flash boot magisk_patched.img but I got stuck at stock recovery after rebooting. Did I miss any step?
Click to expand...
Click to collapse
I have this problem too, do this steps.
1. Fastboot ROM
2. Update last version
3. Flash magisk_patched.boot
4. Factory reset
Done, you have root.
PriPhaze said:
What i did was:
-Flash Stock Global ROM with Xiaomi Flash making sure to set the bat as clean all and NOT clean and lock!
-Once done it will automatically boot , and when it does simply reboot and hold down vol to go to the fastboot
-Flash Recovery img using minimal adb and fastboot
-Type "Fastboot reboot" and hold vol up to go to twrp
-In TWRP FORMAT data to get ride off encryption and reboot into recovery
-Again in TWRP now u can transfer files to the phone, so i patched "Disable_Dm-Verity_ForceEncrypt" and then patched Magisk 19.1
-That's it.
You can now reboot and it will start the phone configuration as normal but once you configure everything u will see that magisk is there and fully works.
Just one thing tho.... be careful if u will restore titanium back up apps...
Don't get me wrong; they do restore correctly but when you make a backup it becomes corrupted or at least that's what happened to me, so make sure to keep backups PRIOR to using the ROM saved in your PC or something.
EDIT: Maybe u should give a try to this twrp https://forum.xda-developers.com/Mi-9/development/recovery-unofficial-twrp-xiaomi-mi-9-t3905825, just got updated few hrs ago and so far seems it works really good.
Click to expand...
Click to collapse
Thank you. I'll try your steps.
How do you know the titanium backup becomes corrupted?
T4Ump said:
I have this problem too, do this steps.
1. Fastboot ROM
2. Update last version
3. Flash magisk_patched.boot
4. Factory reset
Done, you have root.
Click to expand...
Click to collapse
Factort reset? You mean wipe data while stuck at stock recovery? I did. Somehow my phone rooted. But I realized when I charge my phone while turning off it shows mi logo & unlocked words instead of battery icon, even after I unplug the charger. So I have to press power button to turn it on and charge normally. Do you have this problem?
syreg said:
Thank you. I'll try your steps.
How do you know the titanium backup becomes corrupted?
Click to expand...
Click to collapse
Because once I moved back to revolution OS ( I sawp of ROMs quite often ) I realized that my entire apps restored with titanium were crashing , and the few that actually open correctly didn't hold my data.
They were as if you just download them for the first time from the store.
syreg said:
Thank you. I'll try your steps.
How do you know the titanium backup becomes corrupted?
Factort reset? You mean wipe data while stuck at stock recovery? I did. Somehow my phone rooted. But I realized when I charge my phone while turning off it shows mi logo & unlocked words instead of battery icon, even after I unplug the charger. So I have to press power button to turn it on and charge normally. Do you have this problem?
Click to expand...
Click to collapse
No, i dont have this problem.
Root images updated to 19.2 magisk.
10.9.20 require wipe all data after flash patched image, this is not practical at all.
1. you stuck in this rom unless you want to wipe all data every time there is new rom.
2. Magisk bug existed in the latest global stable rom, notification prompted everytime you open Magisk to install zip, you can only ignore it or installation zip brick the phone.
10.2.26.0 root/stock
Can I use those with locked bootloader ?
Sent from my MI 9 using Tapatalk
Avoid and pass by a fool and a madman
How to root Black Shark 2 Global (short way)
Avoid and pass by a fool and a madman
Avoid and pass by a fool and a madman
A few guide to fix your bricked or bad-conditioned phone
Avoid and pass by a fool and a madman
Avoid and pass by a fool and a madman
Thank you for this great guide, I'm sure it will help a lot of people.
The update file I used in my post was from this link, I just rename to make it easier to update.
KM7 said:
Thank you for this great guide, I'm sure it will help a lot of people.
The update file I used in my post was from this link, I just rename to make it easier to update.
Click to expand...
Click to collapse
Wow, thank you very much for the full name link. I think I found something great. I think, now, you can try to root directly on latest firmware, and save lots of time. I will test it... and post it soon.
How to download the latest update as full-sized, factory stock roms
Under Construction....
Sorry for deleting this post.
BS team never open the stock rom download site. I think we can build one, but I couldn't gather enough information.
I was able to find all my own factory stock rom OTAs including the latest, but not others due to lack of information. Further problem is that after I share how to find & download your own latest factory stock rom directly, that site is really slowed down now. Maybe lots read it, download, never share, or due to other reason... The region and ota link is enough to build the stock rom download site, but now the server is slowed down, no one shares... so I stop here.
I will re-open this if I could gather enough information.
wga0 said:
Hey guys, I realized that I neither need to provide a detailed explain nor can.
I can't attach any files, pictures, links... even I can write now. There are too much restriction.
(I must delete all links I included here You can search it in xda-dev forum)
So, here's the shortest and fastest way to root your black shark 2 global.
If anybody want a long detail, more safe way, let me know. I will add later if possible.
If something goes wrong, end to brick your phone, you can always revive that with safe way.
As you know, though safety is increased greatly (Thanks very much to a/b slot system),
but accident can happen anytime. It's on your own responsibility, at your own risk.
Pre-Requirements:
adb/fastboot drivers, Magisk Manager latest version, global OTA1 update
(I skip all the details of 3 firmware regions, payload_dumper, twrp, all others)
(Backup your data. It requires several factory reset)
Steps (also skip all detail. I wish you familiar with adb, fastboot, a/b slot)
1. Unlock the bootloader
1) fastboot oem bs2_unlock (Thanks greatly to Bave Lee)
2) fastboot oem bs2_unlock_critical (I'm not certain this is mandatory, I just do it at first)
2. flash the global OTA1 update and reboot
1) find and set active your not using slot
fastboot getvar all
fastboot set_active x
2) flash the global OTA1 images to that slot
fastboot flash partition_x partition.img (flash all of it, not partially)
fastboot reboot (It will be reboot again to do factory reset, than will boot successfully)
3. Patch the boot.img with Magisk Manager and flash it
Now, you have a working old version boot image. Patch it, flash it and reboot
4. Backup the latest, your own boot.img
Now, your phone is rooted with old version. Backup your original latest boot image
1) adb shell
su
dd if=/dev/block/bootdevice/by-name/boot_x(your using_latest slot) of=...(any folder you prefer)/boot.img
2) copy the boot.img to your PC (with adb pull or mtp)
5. patch your own latest boot.img
1) Set back the active slot to your original slot, reboot
2) do factory reset (because of using OTA1, OTA2 update request will be remained to your current slot)
3) push the magisk manager, boot.img again and repeat the job (patch, pull out, reboot, flash and reboot again)
6. Now, you have the latest updated, rooted phone with stock & modified boot image
7. Don't forget to backup all your stock ROM before doing anything!!
{
"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 you done well, you can check the root status. It's rooted with magisk systemless root, all function's normal.
And be careful. Don't share the patched or stock boot image directly. There's multiple global version.
This is the latest version from my own black shark 2 global. It definitely different from yours.
If you flash different region version, your phone will be bricked. That's why I didn't share it and write this long method.
(If anyone want, I will explain details later with more safe way, what I did. But It's quite long way, takes long time)
Click to expand...
Click to collapse
Here is my region skyw1991010Os00mp5,can u help me with this?
Avoid and pass by a fool and a madman
Flauros7 said:
Here is my region skyw1991010Os00mp5,can u help me with this?
Click to expand...
Click to collapse
you have same region with me,
do you still need the files ? i have magisk rooted boot.img if you want.
Need help
I am successful root my BS2
it run Magsik perfect
but the Build number is SKYW1908301CN00MP6 and wifi does not work, also i cant update build number to Build SKYW1910291CN00MP7
use *#*#1027#*#* to locall update with the
SKYW1907040OS01MP3 Stock Factory Image not work too, it said Error the package unauthorized
can u help me solve this problem,
does the Global OTA 1 boot can fix it?
Can u send me your boot file i cant find it
thank you very much!!!
Avoid and pass by a fool and a madman
The MP7 China OTA update...
IT'S WORKED!!!
thank you very much!
now i'm trying to root new version
exynos 540 said:
you have same region with me,
do you still need the files ? i have magisk rooted boot.img if you want.
Click to expand...
Click to collapse
Hi can you sent me the stock boot image for skw1991010Os00mp5? I really need it.
Hello , Please I need Stock boot.img for this region SKYW1902180OS00MP2 android version 9.
Mustafa9698 said:
Hello , Please I need Stock boot.img for this region SKYW1902180OS00MP2 android version 9.
Click to expand...
Click to collapse
Are you sure your revision SKYW1902180OS00MP2? Isn't it SKYW1904180OS00MP2?
exynos 540 said:
you have same region with me,
do you still need the files ? i have magisk rooted boot.img if you want.
Click to expand...
Click to collapse
Yes bro can u send me the file?
wga0 said:
You mean your revision is SKYW1911010OS00MP5. Right? If you didn't try anything to your roms, you'll have previous revision SKY1909192OS00MP4 at the inactive slot. Here is the factory boot image of it. How to root is similar as above.
Before doing, backup all your data and unlock the bootloader. In this time, unlock_critical is not needed.
1. adb reboot bootloader
2. fastboot getvar current-slot (let's assume it returns b)
fastboot set_active a <- set the opposite slot as active
3. fastboot reboot
After factory reset, this will bring you to previous revision SKYW1909192OS00MP4. Install Magisk Manager and patch the boot image.
4. adb pull /sdcard/Download/patch_boot.img (let's assume you save the image to Download directory)
5. fastboot flash boot_a patch_boot.img <- flash that patched image to same slot (you just set active)
Your phone is now rooted with previous revision. You can backup all of your latest stock rom.
6. adb shell
7. su
8. dd if=/dev/block/bootdevice/by-name/boot_b of=/sdcard/Download/boot.img <- example of boot image. For insurance, just backup all your stock roms.
Now back to your original latest slot, root your own image.
9. fastboot set_active b
and repeat the rooting again with your own roms.
As you know, adb command can be used with USB Debugging, fastboot can be used in bootloader mode.
Or... if you need all of those images, let me know. I will upload full MP4 OTA factory images for your region. You can flash this to your inactive slot and it will fix all problems during updating to MP5 to your active slot.
Click to expand...
Click to collapse
Can u give me the file again because the link is dead?
Boot images, Factory(Full) OTA images for known regions/revisions
Avoid and pass by a fool and a madman