Have now done the following .
1. Cell unroot per SuperSU ( If only a short note, then the app closed )
2. boot into TWRP manually and flashed Magisk - v6
3. next phh 's systemless superuser ) with Super SU magisk version already tried )
4. Mobile launched new
5. After that, it will not boot - When loading only the LED that flashes red and I have to flash a new firmware ...
Anyone know what I'm doing wrong ?
Have a Sony Xperia Z3 D6603
gerooted and SuperSU ( 2.78 )
TWRP 3.0.2-0
Rom : PureX v5 ( Android 6.0.1 - 23.5.A.1.291 )
Locked Blootloader
would be great if he had a solution for me ...
smellz said:
Have now done the following .
1. Cell unroot per SuperSU ( If only a short note, then the app closed )
2. boot into TWRP manually and flashed Magisk - v6
3. next phh 's systemless superuser ) with Super SU magisk version already tried )
4. Mobile launched new
5. After that, it will not boot - When loading only the LED that flashes red and I have to flash a new firmware ...
Anyone know what I'm doing wrong ?
Have a Sony Xperia Z3 D6603
gerooted and SuperSU ( 2.78 )
TWRP 3.0.2-0
Rom : PureX v5 ( Android 6.0.1 - 23.5.A.1.291 )
Locked Blootloader
would be great if he had a solution for me ...
Click to expand...
Click to collapse
I had the same, but maybe the SU can't uninstall. I'm on existenz Rom...
Don't you need an unlocked bootloader?
Sent from my D6633 using Tapatalk
at magisk was nothing about it because that an unlocked bootloader is required.
Yes unlocked Bootloader is required. My Bootloader is unlocked. But can't delete the superuser.apk. That's bad
Exactly the same happened to me. I tried SLiMM 3.1 and PureX V5. After installing Magisk in TWRP device is like dead - only led flashes. If I used Elite kernel, system boots, but the system gets random restarts. Now flashing eXistenZ.
Maybe cause you need to be on stock rom and stock kernel
I use the stock kernel with custom Rom based on the latest official version
Got same issue when using stock kernel on my Xperia Z2, switched to Advanced stock kernel Marshmallow 6.0.1 'cause it has Systemless root support and SElinux permissive and now everything works.
I have try it again, with unroot and install Magisk. Now it works with the advanced stock kernel. But I have some reboots when root is enabled.
Hi All,
I have the same problem, I can see S1 /SOMC Flash Device in Device Manager.
Could someone please post step by step instructions to restore a to Marshmellow?
Will I have to download an Image and a Flashtool?
I have D6603 with TWRP, I am not able to boot to recovery.
Z3- said:
Hi All,
I have the same problem, I can see S1 /SOMC Flash Device in Device Manager.
Could someone please post step by step instructions to restore a to Marshmellow?
Will I have to download an Image and a Flashtool?
I have D6603 with TWRP, I am not able to boot to recovery.
Click to expand...
Click to collapse
Resolved using Emma. I installed the S1 SOMC Flash Device Drivers and I was able to download lollypop.
I will attempt now to reinstall recovery, new rom, and Magisk
Just got this phone new from cricket. I'm having issues making calls. I downloaded the update. But am wondering should I use it. I'm wanting to do custom roms exc. I have not unlocked boot loader or anything yet. If I do the update will I still be able to unlock the boot loader and root custom roms exc? 6045o is the type
First of all I suggest unlocking the bootloader, because if you update to MM you will lose fastboot commands (you can have them back but it's tedious). Then maybe install the latest TWRP, update to MM and then systemless root or custom ROM If you want to update to latest official firmware but don't want to lose TWRP/root just download the update without installing it and then flash it with chainfire's FlashFire.
thanks
plumbe0 said:
First of all I suggest unlocking the bootloader, because if you update to MM you will lose fastboot commands (you can have them back but it's tedious). Then maybe install the latest TWRP, update to MM and then systemless root or custom ROM If you want to update to latest official firmware but don't want to lose TWRP/root just download the update without installing it and then flash it with chainfire's FlashFire.
Click to expand...
Click to collapse
thanks i have twrp recovery and unlocked boot loader. next step. im wanting to b able to play pokemon go. chainfire requires root. i havent rooted yet. because i know pokemon go wont work. any ideas what i can do? p.s. already backed up system image boot and efs. thanks again.
Luckeyleo said:
thanks i have twrp recovery and unlocked boot loader. next step. im wanting to b able to play pokemon go. chainfire requires root. i havent rooted yet. because i know pokemon go wont work. any ideas what i can do? p.s. already backed up system image boot and efs. thanks again.
Click to expand...
Click to collapse
First of all make sure you never mount /system as rw when using TWRP.
Then just do a systemless root (download SuperSU from chainfire website on your phone, launch TWRP's terminal and type "echo SYSTEMLESS=true>>/data/.supersu", then flash SuperSU as usual), systemless root won't be detected by apps/os. Will probably be detected by SafetyNet but i'm not sure PoGo uses it. In case you have problems with root detection you can try suhide by Chainfire.
Also note that systemless Xposed (rootcloak, etc) and V4A are possible via Magisk (just search it on XDA).
[Guide] XT1575 Update To NPH25.200-22 Nougat After Modifying Your System & Re-Root
THIS GUIDE IS NOW DEPRECATED. THERE IS NO NEED ANYMORE TO GO THROUGH THE UPDATING PROCESS AS THERE IS A FULL NOUGAT FACTORY IMAGE AVAILABLE (Build NPH25.200-22). FIRMWARE AVAILABLE HERE: https://forum.xda-developers.com/moto-x-style/general/xt1575-moto-x-pure-edition-factory-t3704142 BE SURE TO THANK @acejavelin FOR TRACKING DOWN THE FIRMWARE PACKAGE FOR US.
Notes:
-YOU ATTEMPT THIS AT YOUR OWN RISK IF YOU FLASHED ANY FIRMWARE PREVIOUSLY NOT FOR THE XT1575 US VERSION
-This guide will have 2 parts. 1 for those that kept their systems read only/systemless, and 1 for those that did not.
-Whether you live booted TWRP or Installed TWRP, if you chose to allow system modifications your OTA will likely fail (you'll need part 2).
-Restoring a TWRP backup will not work and will cause an OTA to fail due to having to allow system write access in TWRP - You Need Part 2.
-This guide assumes you have basic ADB knowledge and already know what fastboot is and how it works.
-Thanks to @gokart2 for the OTA and @acejavelin for the return to stock guides
Part 1: Those That Tweaked Systemlessly Currently On 24.49-18-16 (Will only work if you kept TWRP read only/used systemless root):
1: Disable & Remove systemless Xposed within Magisk Manager and all other Magisk modules. Reboot and wait for Art cache to rebuild.
2: Remove any adblock hosts within your adblock app if installed, or any other root level system altering apps like Greenify (don't worry, you'll get them back).
3: Remove Magisk by booting into TWRP and flashing the current Magisk Removal zip. Reboot.
4: For systemless SuperSu you need to consult their thread as I do not use it. (I'll update this if someone knows the correct process).
5: ADB reboot bootloader and fastboot flash the stock recovery. Latest MM recovery links at the bottom of this post. (rename file to recovery.img).
6: Move the OTA Blur_Version.24.231.16.clark_retus.retus.en.US.zip to the root of your internal sd card (NOT in a folder). File links at the bottom of the post. Thanks @gokart2
7: ADB reboot recovery, when "no command" is listed, hold power + tap volume up then release to access recovery options. Choose "apply update from phone storage". Choose the file and wait for the flash. It's a large update so be patient (about 10-20min). Choose reboot manually in recovery after flash succeeds. Enjoy Nougat!
8: For root you can go ahead and flash TWRP again or live boot TWRP (fastboot boot twrp.img) and then flash Magisk 14.0 from TWRP. Works perfectly.
Part 2: Those That Have Done Everything - TWRP Write Access, Custom Roms, On Older Firmware, Etc (XT1572 Build Flashers Do This At Their Own Risk):
1: Flash the latest full factory image available (24.49-18-8) available here: https://forum.xda-developers.com/mo...de-return-to-stock-relock-bootloader-t3489110. Thank @acejavelin for the thread while your at it. Follow the directions in that guide, it's well detailed and accurate - however read my notes just below first:
NOTES:
-Omit the "fastboot oem lock begin" & "fastboot oem lock" commands to remain bootloader unlocked.
-Omit the "fastboot erase userdata" command if you want to dirty flash and keep all of your data. I recommend clean, you can always root & restore each apps data with Titanium after the Playstore installs everything.
-The "fastboot oem fb_mode_set" instead of "fastboot oem lock begin" & "fastboot oem fb_mode_clear" instead of "fastboot oem lock" I've found to be unnecessary if staying unlocked. Your choice.
-The "fastboot flash partition gpt.bin" & "fastboot flash bootloader bootloader.img" commands will likely fail due to version mismatches. This is ok.
-The "fastboot flash modem NON-HLOS.bin" tends to fail too. For this, just run the command again until it succeeds.
2: After flashing 24.49-18-8 take the OTA to 24.49-18-16. Reboot. OTA zip provided below if you prefer to sideload.
3: Either install the 7.0 OTA the normal way via the update center or just side load it using the directions above. I recommend side loading due to the file size being very close to 1GB.
4: For root you can go ahead and flash TWRP again or live boot TWRP (fastboot boot twrp.img) and then flash Magisk 14.0 from TWRP. Works perfectly!
For Xposed, See My Guide Here: https://forum.xda-developers.com/showpost.php?p=74014516&postcount=96
Stock MM 24.49-18-16 Recovery: https://mega.nz/#!aZpC2RzQ!Fy3GTo_XYPjB1lwuHffCUUERuvnsyvON3kS8kMJ9Cm8
Stock MM 24.49-18-16 Recovery Mirror: https://drive.google.com/file/d/0BxxRfNko9QDKNS1NdnAyZVp6dVU/view?usp=sharing
24.49-18-8 OTA to 24.49-18-16: https://mega.nz/#!yZx2FLzR!cWfKIAYe5VyuadLI55UNHJvwWU98CXUi1g0DO1pDoKg
NPH25.200-22 OTA: https://mega.nz/#!HVhWWLxK!h-8G3vO3Sye_YwypyIJyWb2_79Ow34vNiDnMl2Q8uJg
NPH25.200-22 OTA Mirror: https://drive.google.com/file/d/0B3gPYUZ4nRLwOHJKQnNYczNEMHc/view?usp=sharing
MD5 for NPH25.200-22 OTA: 74d1a4b135200661cc4efd248f99ce33
Stock 7.0 NPH25.200-22 Recovery: https://mega.nz/#!TNoHQAjI!5U2w4p_G7pHlW6Mak7LqFR_PeWUDpSLc7S3OiUs_Qf8
Alrighty. I got back to stock 6.0 with the 18-16 update. I couldn't get the OTA via the system update, so I tried doing it via ADB. That threw up a "status 7 error". I then copied the file to my internal storage and selected update via SD Card in recovery. It hung on "Patching System Files" for a while, but in the end it moved on and worked fine. Thanks for the awesome guide!
Thread updated with downloads for the 24.49-18-8 OTA to 24.49-18-16 zip.
I exctracted the 7.0 Stock recovery to replace if you decide to flash TWRP and want to go back to the stock recovery for future updates (HAHAHA yeah right!). Download link in OP. The 7.0 Recovery is different than the MM recovery. They are not interchangeable. Don't flash the 7.0 recovery on MM.
Question... can those of us who are rooted, custom roms, with TWRP, not just flash a stock unrooted TWRP backup from here: https://forum.xda-developers.com/moto-x-style/development/pure-firmware-tuff-wip-t3224833
Then, flash the stock recovery like it says... and take the update? Isn't that easier than this method?
Bwangster12 said:
Question... can those of us who are rooted, custom roms, with TWRP, not just flash a stock unrooted TWRP backup from here: https://forum.xda-developers.com/moto-x-style/development/pure-firmware-tuff-wip-t3224833
Then, flash the stock recovery like it says... and take the update? Isn't that easier than this method?
Click to expand...
Click to collapse
It probably won't work. Once TWRP is given write access to your system (which is required to flash a full rom or restore a backup) any OTA's will fail. Plus any modem/bluetooth mismatches will cause a failure too. Fastboot flashing a stock image is really very easy & pretty much a guarantee that everything will work properly. However, if your able to get it to work, please let us know...though I don't think it will.
annoyingduck said:
It probably won't work. Once TWRP is given write access to your system (which is required to flash a full rom or restore a backup) any OTA's will fail. Plus any modem/bluetooth mismatches will cause a failure too. Fastboot flashing a stock image is really very easy & pretty much a guarantee that everything will work properly. However, if your able to get it to work, please let us know...though I don't think it will.
Click to expand...
Click to collapse
Once I do this, I can just reinstall TWRP and Magisk, backup the stock 7.0 and if I ever decided, just flash a custom rom later on?
hey thanks for the help on this one. I was so worried because I got stuck on th May security update OTA-wise.
question: I messed with the LatAm version of Nougat, so when I tried to re-lock the bootloader, it game the preflash error.
After this proper update flash, is there a way to run the bootloader CMD to just re-lock the bootloader?
Here's the recovery before the 7.0 one, just incase.. Was bored. Ok, I won't lie....didn't see u posted the 7.0 recovery....lol.:good::highfive:
Bwangster12 said:
Once I do this, I can just reinstall TWRP and Magisk, backup the stock 7.0 and if I ever decided, just flash a custom rom later on?
Click to expand...
Click to collapse
Yup. TWRP flashes and works, magisk v14 works, and so far systemless xposed api24 is working.
EsteBandido4444 said:
hey thanks for the help on this one. I was so worried because I got stuck on th May security update OTA-wise.
question: I messed with the LatAm version of Nougat, so when I tried to re-lock the bootloader, it game the preflash error.
After this proper update flash, is there a way to run the bootloader CMD to just re-lock the bootloader?
Click to expand...
Click to collapse
What is everyone's fascination with relocking the bootloader? You do not need to relock your bootloader. You cannot relock the bootloader unless all your system partitions match. Use my part 2 section. Read the notes, skip the bootloader lock commands. Leave your bootloader unlocked, get up and running on nougat, then you can issue the lock commands if you really want a locked bootloader.
How exactly do you flash the 24.49-18-16 OTA? I'm stuck at this part
EDIT nevermind didn't read lol
Amp699435 said:
How exactly do you flash the 24.49-18-16 OTA? I'm stuck at this part
Click to expand...
Click to collapse
Copy the file to the root of your internal storage. Reboot into recovery. Hold power = volume up & release to access menu options. Choose apply update from storage. Select the OTA.zip package and let it install. (Directions are clearly written in OP.)
Does it matter which version you're on? I'm currently on MPSH24.49-18-4 with the May 2016 security update.
GrandAdmiral said:
Does it matter which version you're on? I'm currently on MPSH24.49-18-4 with the May 2016 security update.
Click to expand...
Click to collapse
Part 1 implies that you are on MPSH24.49-18-16 (dec), for part 2 - no it doesn't matter. Go ahead and start with the full firmware available MPSH24.49-18-8 and follow the steps from there.
annoyingduck said:
Part 1 implies that you are on MPSH24.49-18-16 (dec), for part 2 - no it doesn't matter. Go ahead and start with the full firmware available MPSH24.49-18-8 and follow the steps from there.
Click to expand...
Click to collapse
Ok. Was going to have to follow option two anyway because of how I rooted...
Now I also take it that flashing Magisk is recommended, but optional?
GrandAdmiral said:
Ok. Was going to have to follow option two anyway because of how I rooted...
Now I also take it that flashing Magisk is recommended, but optional?
Click to expand...
Click to collapse
Root is completely up to you. It's noted so users know that TWRP/Root are working. My logic with any XDA thread is that your bootloader is unlocked and you want root, but that's me...
annoyingduck said:
Root is completely up to you. It's noted so users know that TWRP/Root are working. My logic with any XDA thread is that your bootloader is unlocked and you want root, but that's me...
Click to expand...
Click to collapse
Gotcha. I know I'm going to root again, but I've never used Magisk before so I wasn't sure of that piece.
annoyingduck said:
Part 1 implies that you are on MPSH24.49-18-16 (dec), for part 2 - no it doesn't matter. Go ahead and start with the full firmware available MPSH24.49-18-8 and follow the steps from there.
Click to expand...
Click to collapse
I am running Dirty Unicorns right now and when i looked up what I'm on in fastboot, it showed MPSH24.49-18-16. Would I just follow part 2 and use MPSH24.49-18-8 or something? I thought I had to use at least the version I'm on or newer.
GrandAdmiral said:
Does it matter which version you're on? I'm currently on MPSH24.49-18-4 with the May 2016 security update.[/QUOTE
Your issue is that TWRP has modified your
System, any restoring of the stock rom will fail to update. So yes, you'll need to go through part 2 and downgrade and work your way back up.
Click to expand...
Click to collapse
I downloaded the zip (it took a while).
Restored to stock like 3 different ways but still hit a road block. I went the adb sideload route but got status error 7 because my build fingerprint wasn't correct. I tried searching for the right build I need, but I'm not an expert and couldn't find the right set of files that I was sure I knew how to restore. I ended up restoring my AICP backup.
If somebody could PM me and give me a hand (messaging through Hangouts or something) that would be AWESOME!
I'm planning trying to snag an XL 2 pre-order next week, but until then the less headache the better! Plus stock Nougat looks better on a Swappa listing
Trying to sideload via recovery 24.49-18-16 but I keep getting "("unexpected contents:EMMC:/dev/block/bootdevice/by-name/boot...". I've also tried installing from the phone but the same error appears in recovery. Any ideas?
Hello everyone.
I come to you because I've searched a lot about S5 VRZ on the XDA forum. My purpose is to root my phone with the latest Magisk version (at least 14.0) and maybe to install a custom Rom on it too (I saw Phoenix v15 which could work f I'm not wrong). But I'm new in rooting and in customizing my phone, so I come here to request your help.
Those are my phone informations :
1) Before doing anything on it I had this : Galaxy S5 VRZ - Android 4.4.4 - BootLoader version ANK2
2) I followed this guide with CID 15 : [GUIDE] Root, Bootloader Unlocks, and More!
At this point I didn't saw this thread which told me I probably did the wrong thing in step 2: [GUIDE] painiac's Essential Guide to Galaxy S5 Flashing, Rooting, Fixing, Customizing
But now I did and after doing step 2 guide I'm in this configuration : Galaxy S5 VRZ - Android 6.0.1- BootLoader version QB2
My phone still work but I don't really know what to do, if I'm right or wrong ? I'm unrooted now, trying to reinstall Magisk on another way.
So my questions are:
What to do with this configuration to get rooted with Magisk version 14.0 at least ?
And after, which custom ROM may I install on my phone and how ? (links are welcomed ofc)
I would really be glad if someone could help me to solve this situation. And I thank everyone who'll fully read this thread for the attention you paid to it (and also because I'm french and probably don't speak a really good englsih ^^')
Thank you for you help and have a good day ! :good:
What I've alrdy read on xda-developper.com :
[GUIDE] Root, Bootloader Unlocks, and More! - eMMC_CID_Checker_.apk
[GUIDE] Root, Bootloader Unlocks, and More!
[GUIDE] Unlocking the Galaxys S5 Bootloader using DEV Bootloader [KK-MM]
[VZW_Stock TW Rom][6.0.1 MM QA1 Build Odex For Locked Bootloader SafeStrap Only]
How To Flash Custom 6.0.1 Roms On Locked Bootloader That Cannot Be Unlocked
[PORT][ROM][G900V][VZW]PhoeniX ROM V15.0 MM 6.0.1[Aroma Installer Dev Bootloader]
Verizon Samsung Galaxy S 5
If you want Magisk, you probably should install it.
It's usually is installed via TWRP recovery as a flashable zip file.
http://tiny.cc/latestmagisk
If you don't have TWRP recovery, you probably should install it.
It's usually is installed via Odin as a flashable tar file.
https://dl.twrp.me/klte/
You can only flash TWRP into SM-G900V if the bootloader is unlocked.
Unlocked bootloader looks like this (MODE: Developer):
If you still have not unlocked the bootloader, then you probably should try to do it.
It can be unlocked on the devices with CID15 (determined with this tool, first two digits in CID line).