Intro: Below are the instructions for 3 steps to get Kitkat 4.4 (140.44.3.ghost_att) running on the AT&T moto x with locked bootloaders:
Install full 139.44.44.ghost_att (leaked) rom
Patch the rom to 140.44.3.ghost_att (ota to leak)
Patch the modem to the 140.44.3.ghost_att version
The updates came in stages, otherwise it would not have been my intention for this to be so long and messy. I soon hope to create a single rom and simplify the instructions. Testers can help with the WIP items below...
WARNING: I AM NOT RESPONSIBLE IF YOU MESS UP YOUR PHONE.
This rom is simply a flashable zip made from the ATT 4.4 leak which will install version 139.44.44. It is intended for the ATT moto x with locked bootloaders, however it should work with an unlocked bootloader if you fastboot flash the included boot.img. The flashable zip does not modify the bootloader or anything besides /system, but the full instructions will wipe out everything.
Prerequisite:
Att moto x with either the .51 (original) or .54 (1st OTA) stock rom
BACKUP ANYTHING YOU DON'T WANT TO LOSE. THESE INSTRUCTIONS WILL WIPE YOUR USERDATA AND SDCARD.
Instructions for ATT moto x with locked bootloader:
root with PwnMyMoto or RockMyMoto (for .51 or .54 respectively, thanks jcase)
install safestrap (thanks Hashcode and Team Win)
download rom to sdcard (motox-att-kitkat-leak-44.zip, link below)
download supersu flashable to sdcard (link below, thanks Chainfire)
enter safestrap recovery (TWRP) and activate the stock-slot
flash rom (motox-att-kitkat-leak-44.zip) to the stock-slot using TWRP recovery
immediately flash supersu using TWRP recovery
within TWRP reboot to bootloader
flash boot.img (included in ROM) to boot: fastboot flash boot boot.img
flash same boot.img to recovery: fastboot flash recovery boot.img
erase cache: fastboot erase cache
erase userdata: fastboot erase userdata (This wipes everything) This is not necessary. Thanks HeroSon.
powerup normally and enjoy
Update 11/17/2013: I made a patch to safely apply the ota that was received by people running the att 4.4 leak. This will bring the system build up to 140.44.3.ghost_att. The patch script DOES NOT modify anything except /system, and should be safe. The updated kernel (boot.img) is included in the zip. In case something goes wrong, backup your data to be on the safe side. Here are the Instructions:
Complete the installation of the att 4.4 leak (above instructions)
Reinstall safestrap This is not necessary. Thanks HeroSon.
Download the patch to sdcard (motox-140.44.3.ghost_att-ota-safepatch.zip, link below)
Reboot into safestrap recovery (TWRP)
Install the patch (motox-140.44.3.ghost_att-ota-safepatch.zip)
within TWRP reboot to bootloader
flash boot.img (included in the patch) to boot: fastboot flash boot boot.img
flash same boot.img to recovery: fastboot flash recovery boot.img
powerup normally
Update 11/18/2013: I attached a link to the modem patch that will update the 139.44.44 modem to a 140.44.3 modem. I really wanted to create a fastboot flashable NON-HLOS.bin image, but I haven't tested the procedure. Here are the instructions for the modem patch that I have tested:
Download the modem patch to the sdcard (motox-140.44.3.ghost_att-modem-patch.zip, link below)
Fastboot flash NON-HLOS.bin (included within the zip): fastboot flash modem NON-HLOS.bin
erase modemst1: fastboot erase modemst1 (I've done these erases a few times. They are prudent when you flash a modem.)
erase modemst2: fastboot erase modemst2
Reboot into safestrap recovery TWRP
Install the modem patch (motox-140.44.3.ghost_att-modem-patch.zip)
Powerup normally
Notes:
I am running the modem from the .54 ota, and it works with kitkat. I am not sure about the original .51 modem. The 140.44.3 modem is necessary after running patch to 144.44.3. This fixes the settings->security force close.
The safestrap "recovery or continue" screen still appears when you boot. If you erased userdata, reinstall safestrap to get all of the program back.
You should always be able to flash back to stock, as this procedure does not modify your bootloader.
There is a new version of safestrap. These instructions work with either v3.63 and v3.65. (Thanks HeroSon.)
I get a FC in settings->security on the 140.44.3 (patched) version. So far this is the only problem I have noticed. This force close is fixed by the modem patch.
WIP: I would like testers to help with the following:
What happens if you skip step 12 and don't erase useradata (this will keep [more of] safestrap intact)?
How do you remove safestrap manually?
Safestrap has been updated. Does the original 139.44.44 rom now run in a rom slot with 4.2.2 running in the stock-slot? What about the patches? I tried it - doesn't work.
Once 4.4 is installed in the stock-slot, can you backup the stock slot and restore to a rom-slot? (I'm guessing it works this way.) I guessed wrong. This doesn't work. Apparently safestrap needs a bit of tweaking to work with KK.
Is it possible for Safestrap TWRP to flash boot.img to the stock slot? (My experience is that it did not flash boot.img when using a rom-slot)
To clean up this mess, I am considering making a single rom that includes the base 4.4 version with the safepatch included. PM if you want to help by testing this all in one rom once I have it finished. There is a new rom of the official att 4.4.
I have an 100MB ext4 image of /modem. I would like guidance making a fastboot flashable non-HLOS.bin image. (Otherwise I wont be able to combine the leak and the patch.) I see instructions that might work if someone wants to try it and report their findings: http://forum.xda-developers.com/showthread.php?t=1588461 The official att 4.4 SBF includes NON-HLOS.bin
Part of the stock modem procedure is to flash "fsg.mbn", but I have not done that because I have been able to confirm that you can downgrade after flashing it. Can anyone confirm that this is safe on the moto x? (http://forum.xda-developers.com/showthread.php?t=2529569) This works.
139.44.44 rom download : http://www.androidfilehost.com/?fid=23212708291677349
rom patch to 140.44.3 download: http://www.androidfilehost.com/?fid=23212708291678076
modem patch to 140.44.3 download: http://www.androidfilehost.com/?fid=23212708291678561
supersu: http://forum.xda-developers.com/showthread.php?t=1538053 (download "CWM / TWRP / MobileODIN installable ZIP")
Original source files: http://rootzwiki.com/topic/107721-att-moto-x-44-leak/ (thanks designgears)
ooo yeah !! Nice job !!
Sa sens le Rooting icite !!
Wish mine was from AT&T, still have one year of warranty....cant see the time when kitkat comes global.
Is there any reason why I would have to wipe the SD card? It seems unnecessary. I may test this, but I'm a bit leery given that my Moto X is my daily driver...
Sent from my XT1058 using XDA Premium 4 mobile app
How do I do steps 9-12?
Does this include the recent ATT 4.4 OTA as well? Or is it just the system images from the original leak?
Sent from my XT1053
rubiksmoose said:
Is there any reason why I would have to wipe the SD card? It seems unnecessary. I may test this, but I'm a bit leery given that my Moto X is my daily driver...
Sent from my XT1058 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
It might work without the wipe. Honestly, I tried this so many times that I quit once I had something that worked... I attributed most of my failures to a incompatibility between safestrap and the 4.4 boot process, but each of those attempts was done to a rom slot and not the stock slot.
Hopefully someone else can 'give it a whirl' and report their findings.
penpen72 said:
How do I do steps 9-12?
Click to expand...
Click to collapse
These steps are done using "FASTBOOT" from a PC while the phone is booted to the bootloader in fastboot mode.
phositadc said:
Does this include the recent ATT 4.4 OTA as well? Or is it just the system images from the original leak?
Click to expand...
Click to collapse
The rom was made from the original leak. I have been thinking about the OTA, but I am unclear how to approach this.
I am in AP Fastboot Flashmode on the phone what do I need to do now to do the steps? Sorry but I am coming from Samsung and HTC that have never been this hard.
---------- Post added at 02:52 PM ---------- Previous post was at 02:46 PM ----------
Also, my bootloader is locked. I figured I wouldn't have to do the extra steps since you say that it doesn't change those.
penpen72 said:
I am in AP Fastboot Flashmode on the phone what do I need to do now to do the steps? Sorry but I am coming from Samsung and HTC that have never been this hard.
---------- Post added at 02:52 PM ---------- Previous post was at 02:46 PM ----------
Also, my bootloader is locked. I figured I wouldn't have to do the extra steps since you say that it doesn't change those.
Click to expand...
Click to collapse
I assume you are on windows. First you need to download the FASTBOOT.exe program for our Motorola phones, and make sure the fastboot drivers install on your PC. (Maybe someone can help with this link.) Then you can issue the "fastboot ..." commands 9-12 I listed above from your PC with your phone plugged into the PC.
You certainly need to flash /boot, and you should also flash boot to recovery to allow RW access to /system. It might be possible to skip the "erase userdata" step, but that is unclear to me at this moment.
How is the leaked ROM working for you? Worth it? Any bugs or anything?
rubiksmoose said:
How is the leaked ROM working for you? Worth it? Any bugs or anything?
Click to expand...
Click to collapse
Everything is working fine. Take a look here for other people's observations:http://forum.xda-developers.com/showthread.php?t=2517577
There are only two odd things I have noticed. 1) the recent apps screen acts a bit strange when you swipe away apps 2) the transparent status bar becomes less transparent when you go for a drive and the "driving" notification is displayed. It is almost not worth mentioning, and a reboot fixes this issue.
It is hard to answer the "worth it" question. Ultimately, it is a still a smartphone with the same core capabilities, but I enjoy the challenge and the opportunity to learn something.
[edit]I am starting to think that there is additional battery drain vs the .54 ota version. "Wakelock detector" doesn't work, and settings->battery shows "Android System" at the top. This is a 'deal breaker' for me. I'll try and figure out how to apply the 4.4 ota without modifying the bootloader.[/edit]
question. Do you have to reboot the phone into recovery for system write-protect to be turned off the way you do currently, or is it off by default?
n1ckr0th said:
question. Do you have to reboot the phone into recovery for system write-protect to be turned off the way you do currently, or is it off by default?
Click to expand...
Click to collapse
When you enter SS recovery (step 4), safestrap will reboot itself if necessary to make sure you are in system rw mode.
Ctrl-Freak said:
When you enter SS recovery (step 4), safestrap will reboot itself if necessary to make sure you are in system rw mode.
Click to expand...
Click to collapse
I'm referring to post install. Currently you must be booted into recovery (normal os with write protect off) for changes to system to stick. is this still the norm with the 4.4 leak, or is WP off while booting normally?
n1ckr0th said:
I'm referring to post install. Currently you must be booted into recovery (normal os with write protect off) for changes to system to stick. is this still the norm with the 4.4 leak, or is WP off while booting normally?
Click to expand...
Click to collapse
Yes. After you have 4.4 working, you must still boot to recovery to enable RW mode on /system. Step 10 ensures you have the 4.4 boot.img in the recovery partition.
(The stock bootloader is still enforcing RO mode for a normal boot.)
I install this and skip step 12 and don't erase useradata. Everything working and all the data still there.
So can I clarify a few things for myself?
You made this by taking the leak files and packaging them into the zip, and it just works with safestrap now? Can you explain what you did to make the leak imgs Safestrap-bootable?
j2cool2012 said:
You made this by taking the leak files and packaging them into the zip,
Click to expand...
Click to collapse
I had to tweak and debug the script, but basically this is the only software part of what I did. To keep things simple, I left out the modem and simply included boot.img within the zip. The rom script does not flash boot.img.
Can you explain what you did to make the leak imgs Safestrap-bootable?
Click to expand...
Click to collapse
Nothing.
and it just works with safestrap now?
Click to expand...
Click to collapse
I'm glad you asked these question. First of all I failed to get 4.4 running in a rom-slot - you can read about my methods on this forum...
Finally, it came to me. Hashcode's Safestrap intercepts the boot process so nicely on the stock-slot that the SS:TWRP recovery program is [nearly] as effective as TWRP or CWM running from the recovery partition. Nice work Hashcode! So I made a regular rom that you can flash via safestrap TWRP. This rom only formats and flashes /system to keep things simple.
The only other thing I did was describe a set of instructions that worked for me.
Ctrl-Freak said:
I had to tweak and debug the script, but basically this is the only software part of what I did. To keep things simple, I left out the modem and simply included boot.img within the zip. The rom script does not flash boot.img.
Nothing.
I'm glad you asked these question. First of all I failed to get 4.4 running in a rom-slot - you can read about my methods on this forum...
Finally, it came to me. Hashcode's Safestrap intercepts the boot process so nicely on the stock-slot that the SS:TWRP recovery program is [nearly] as effective as TWRP or CWM running from the recovery partition. Nice work Hashcode! So I made a regular rom that you can flash via safestrap TWRP. This rom only formats and flashes /system to keep things simple.
The only other thing I did was describe a set of instructions that worked for me.
Click to expand...
Click to collapse
Thanks for taking the time to answer. I'm trying to figure out what has been done to see if I can try to do something similar for the VZW moto X using the T-Mobile leak.
j2cool2012 said:
Thanks for taking the time to answer. I'm trying to figure out what has been done to see if I can try to do something similar for the VZW moto X using the T-Mobile leak.
Click to expand...
Click to collapse
the Att bloatware and carrier name in notification bar scared me away
Related
Help!!! I am willing to pay someone $50 via Paypal to help me resolve my issues.
Here is my story. I have a DNA bought a month ago. Have not installed the latest OTA updates. I wanted to root it because I had my Thunderbolt rooted and was using the Wifi Tether app which was great.
So last night I followed exact directions and rooted the phone. I first did all the unlocking the boot loader then installed TWRP recovery, etc then rooted it. I am sorta a newbie when it comes to rooting but I have done about 5 Thunderbolts for friends and families without any issues.
So after the root things seems to be OK. I went ahead and installed the Wifi Tether app (the yellow one) but it did not work. I then checked SuperSU and it kept saying the binaries needed to be updated but everytime I told it to do that the phone would reboot and if I go back into SuperSU then it would say binaries needed to be updated again. I researched then installed Superuser and chose to use that instead. At this point the Wifi stopped working. It would say "turning on" but never does.
So I tried different ROMs including the HTC sense rooted, Viper, CM Mod, whatever.
With different ROMs either I still experience the same Wifi not turning on or get message "unfortunately, the process com.android.phone has stopped" and it would be like that every 2 seconds.
At this point I am so disgusted as it wasted so much of my time. All I wanted was to get wifi hotspot which I assumed I had to root.
This is a nightmare and at this point I still would like to root it but more importantly I need a working phone like it was before I rooted this.
If anyone willing to invest some time and help me straighten this out I can pay you $50 by Paypal. It maybe an easy fix but I gave up.
Vince
did you flash a kernel with system write enabled?
with each rom usually comes a boot.img in a zip file (or the rom dev will have a separate download) and what you need to do is copy the boot.img file to where you have adb.exe, then issue the following:
Code:
adb reboot bootloader
Flash boot.img in Bootloader by doing this (make sure on the phone screen when you are in bootloader it says "fastboot usb") :
Code:
fastboot flash boot boot.img
Then once you flashed your boot.img file reboot to recovery and then flash the rom and modules (usually the modules.zip is in with the boot.img) take the modules.zip place them on your sdcard where ever you like and after you flash the rom then flash the modules.zip in recovery and that should fix your wifi issues and by flashing the correct kernel(boot.img) that will fix the su binaries and they will update
oh and if you are on a shared data plan the wifi tethering is free...
hondaguy28 said:
Help!!! I am willing to pay someone $50 via Paypal to help me resolve my issues.
Here is my story. I have a DNA bought a month ago. Have not installed the latest OTA updates. I wanted to root it because I had my Thunderbolt rooted and was using the Wifi Tether app which was great.
So last night I followed exact directions and rooted the phone. I first did all the unlocking the boot loader then installed TWRP recovery, etc then rooted it. I am sorta a newbie when it comes to rooting but I have done about 5 Thunderbolts for friends and families without any issues.
So after the root things seems to be OK. I went ahead and installed the Wifi Tether app (the yellow one) but it did not work. I then checked SuperSU and it kept saying the binaries needed to be updated but everytime I told it to do that the phone would reboot and if I go back into SuperSU then it would say binaries needed to be updated again. I researched then installed Superuser and chose to use that instead. At this point the Wifi stopped working. It would say "turning on" but never does.
So I tried different ROMs including the HTC sense rooted, Viper, CM Mod, whatever.
With different ROMs either I still experience the same Wifi not turning on or get message "unfortunately, the process com.android.phone has stopped" and it would be like that every 2 seconds.
At this point I am so disgusted as it wasted so much of my time. All I wanted was to get wifi hotspot which I assumed I had to root.
This is a nightmare and at this point I still would like to root it but more importantly I need a working phone like it was before I rooted this.
If anyone willing to invest some time and help me straighten this out I can pay you $50 by Paypal. It maybe an easy fix but I gave up.
Vince
Click to expand...
Click to collapse
Find a kernel you like and flash both parts of it.
Flash the modules in recovery and flash the boot.img wither in fastboot using "fastboot flash boot boot.img" or using the flash img gui app.
Sent from my HTC6435LVW using xda app-developers app
ninja'd by Bigandrewgold
You need to flash a kernel with system write enabled. Since you are not S-off you have to flash the kernel via fastboot and then reboot to recovery and flash the kernel modules zip that comes with your kernel of choice. Without system write enabled you cannot update busy box. If you do not have adb or fastboot enabled to flash the kernel via fastboot there is a tool suite that will help. Most wifi issues are because of not having flashed the modules.zip in recovery after flashing the kernel. Once you get that fixed there is a thread in the Questions section where I posted my Wifi Tether settings that work with the DNA.
Thanks for the fast responses. I like the Viper DNA ROM. I will try to follow your directions. I will be home in a couple of hours and will try it and plan on spending all night if I need to get this thing working.
Vince
Man I'm counting my cash already look out suckers.. J/K I really don't know anything..
.torrented said:
did you flash a kernel with system write enabled?
with each rom usually comes a boot.img in a zip file (or the rom dev will have a separate download) and what you need to do is copy the boot.img file to where you have adb.exe, then issue the following:
Code:
adb reboot bootloader
Flash boot.img in Bootloader by doing this (make sure on the phone screen when you are in bootloader it says "fastboot usb") :
Code:
fastboot flash boot boot.img
Then once you flashed your boot.img file reboot to recovery and then flash the rom and modules (usually the modules.zip is in with the boot.img) take the modules.zip place them on your sdcard where ever you like and after you flash the rom then flash the modules.zip in recovery and that should fix your wifi issues and by flashing the correct kernel(boot.img) that will fix the su binaries and they will update
oh and if you are on a shared data plan the wifi tethering is free...
Click to expand...
Click to collapse
Hi, say I want to use Viper DNA. Can you point me to where I can download what I need to make this happen?
Vince
hondaguy28 said:
Hi, say I want to use Viper DNA. Can you point me to where I can download what I need to make this happen?
Vince
Click to expand...
Click to collapse
Download this its the ROM and put it on your /sdcard in your phone: http://www.androidfilehost.com/?fid=9390288116658473299
Then
Go here and download this .zip its what ViperDNA Recommends (but later if you want to you can download any kernel you wish)
http://forum.xda-developers.com/showthread.php?t=2064066
Now this is what you do with this second download, open the .zip and there will be a boot.img and a Modules.zip
place the modules.zip where you placed the ViperDNA .zip, then take the boot.img and place it where you have your adb.exe file
then boot into the bootloader where it says "fastboot usb"
now after you get into fastboot issue the
Code:
fastboot flash boot boot.img
then it will flash the boot.img file after it completes on the phone boot into recovery
then do all of the wipes (FR, cache, dalvik) then flash the viperdna rom and after that finishes flash the modules.zip then you can boot into the rom and everything should be working
then once you get all of those done you should get some kind of notification from ViperDNA to flash some kind of OTA (their versions there should be three) to update to the latest ViperDNA
here is the viperdna thread http://forum.xda-developers.com/showthread.php?t=2105745 for w/e you need it for
if you need anymore help just send me a PM ill be more than happy to help
hondaguy28 said:
Hi, say I want to use Viper DNA. Can you point me to where I can download what I need to make this happen?
Vince
Click to expand...
Click to collapse
Go to the Rom thread. There will be a link for the Rom for you to install and there will be another download for the boot.img for you to flash.
Sent from my HTC6435LVW using xda app-developers app
.torrented said:
Download this its the ROM and put it on your /sdcard in your phone: http://www.androidfilehost.com/?fid=9390288116658473299
Then
Go here and download this .zip its what ViperDNA Recommends (but later if you want to you can download any kernel you wish)
http://forum.xda-developers.com/showthread.php?t=2064066
Now this is what you do with this second download, open the .zip and there will be a boot.img and a Modules.zip
place the modules.zip where you placed the ViperDNA .zip, then take the boot.img and place it where you have your adb.exe file
then boot into the bootloader where it says "fastboot usb"
now after you get into fastboot issue the
Code:
fastboot flash boot boot.img
then it will flash the boot.img file after it completes on the phone boot into recovery
then do all of the wipes (FR, cache, dalvik) then flash the viperdna rom and after that finishes flash the modules.zip then you can boot into the rom and everything should be working
then once you get all of those done you should get some kind of notification from ViperDNA to flash some kind of OTA (their versions there should be three) to update to the latest ViperDNA
here is the viperdna thread http://forum.xda-developers.com/showthread.php?t=2105745 for w/e you need it for
if you need anymore help just send me a PM ill be more than happy to help
Click to expand...
Click to collapse
Hi, I sent you PM but not sure if it went out. If it did not please send me one and I will reply.
Thanks.
You could follow the steps in my guide which can be found in my signature. Skip any steps you don't need.
Everything you need to know is there
Read before continue:
http://forums.yuplaygod.com/threads/15124/
http://forum.xda-developers.com/showpost.php?p=63197935
http://forum.xda-developers.com/android/software-hacking/wip-selinux-capable-superuser-t3216394
Requirements:
Completely stock, untouched device (OnePlus One).
Unlocked bootloader.
Rooted boot images:
cm-12.1-YOG7DAS2K1-bacon-boot-debuggable-rooted.img
Usage:
Download the rooted boot image that matches with your installed build.
Flash using fastboot:
Code:
fastboot flash boot XXX.img
Install the SuperUser manager app: https://play.google.com/store/apps/details?id=me.phh.superuser
Profit!
To take incremental OTA:
Download the stock boot image that matches with your installed build. Either extract from signed fastboot flashable zips or get from this thread.
Flash using fastboot:
Code:
fastboot flash boot XXX.img
You should be able to take & install the OTA, if /system isn't tampered previously.
Note:
The rooted boot images are based on official boot-debuggable images & super-bootimg by @phhusson.
The whole thing is in alpha stage & still WIP, so expect bugs.
Not all apps are compatible with systemless root approach, so root access mayn't be visible to them.
Please provide detailed feedback to me, @phhusson & the concerned app developer.
Reserved for future v1.
Reserved for future v2.
I read the second and third links, but had to sign up to get the first (not with it at this time) and I'm kinda confused. What exactly is wrong with the "old way" of rooting? Is it just for things like Android pay to work or is there other benefits?
Sent from my LG-D800 using Tapatalk
@FlashHappy78
In a nutshell, traditional rooting method modifies the /system partition. As a consequence, subsequent OTAs will fail. In case of Cyanogen OS devices, it may be easier to grab the full signed zip later & update manually, but for others they need to re-flash the stock system.img to take the OTA.
In this new approach, only the boot image is modified but /system is untouched. Thus any event/application that verifies the integrity of /system partition (like OTA, Android Pay etc.) is ready to be executed on top of the rooted device without any hitch.
If OTA contains an updated boot image, then user need to re-flash the stock boot image first which is considerably easy to re-flash than the whole system.img.
I've always been under the assumption that oem OTA updates usually break root anyways, plus patch whatever exploits were used to gain root (especially from OEM's like Samsung and LG), so because of that, I never take OTA updates unless they come from custom ROM devs.
Anyways, thanks for the clarification. I don't use android pay and I use only custom ROMs, so this probably isn't for me then. Thanks again mate.
Sent from my LG-D800 using Tapatalk
Do you have any systemless image for CM13? I tried to find a way to change the : cm-13.0-ZNH0EAS2JK-bacon-boot-debuggable.img for myself but no luck, I will have to come back to it next week.
Do you have any links to suggest?
poulopoulosa said:
Do you have any systemless image for CM13? I tried to find a way to change the : cm-13.0-ZNH0EAS2JK-bacon-boot-debuggable.img for myself but no luck, I will have to come back to it next week.
Do you have any links to suggest?
Click to expand...
Click to collapse
Flash supersu at least the stable 2.64
poulopoulosa said:
Do you have any systemless image for CM13? I tried to find a way to change the : cm-13.0-ZNH0EAS2JK-bacon-boot-debuggable.img for myself but no luck, I will have to come back to it next week.
Do you have any links to suggest?
Click to expand...
Click to collapse
As suggested by @hellcat50, I'll not provide any more update on this as newer SuperSU can patch the boot image on the fly.
Welcome everyone!
This thread has been created for extreme newbies/noobs and for their benefit. Not only noobs, but everyone is free to post questions and also give answers to those questions. Any type of question is allowed as long as it is related about the device. No off-topic discussions are allowed!
Hit Thanks if I Helped You!
Regards,
PoseidonKing
Hello,
I've installed a custom recovery, SuperSU and the xposed framework on my Wileyfox Swift 2 Plus and yesterday I've received an OTA update with wich I was (as expected) unable to update my phone. (it just rebooted to TWRP and did nothing) On their website I was only able to find an older build. I think what I have to do is install the stock recovery(to install the update then switch back to a custom one), but I don't know where to get it from.
boa05 said:
Hello,
I've installed a custom recovery, SuperSU and the xposed framework on my Wileyfox Swift 2 Plus and yesterday I've received an OTA update with wich I was (as expected) unable to update my phone. (it just rebooted to TWRP and did nothing) On their website I was only able to find an older build. I think what I have to do is install the stock recovery(to install the update then switch back to a custom one), but I don't know where to get it from.
Click to expand...
Click to collapse
Here you go. https://drive.google.com/file/d/0B1k2IwBoVgfFVVF1UEY3cUVVY28/view?usp=sharing
I grabbed this from cm-13.1.4-ZNH2KAS5RM-marmite-signed-fastboot-c64f8f5d87 - flash it via Fastboot preferably.
linuxct said:
Here you go. https://drive.google.com/file/d/0B1k2IwBoVgfFVVF1UEY3cUVVY28/view?usp=sharing
I grabbed this from cm-13.1.4-ZNH2KAS5RM-marmite-signed-fastboot-c64f8f5d87 - flash it via Fastboot preferably.
Click to expand...
Click to collapse
Thank you very much, I've installed the stock recovery and also uninstalled xposed framework and SuperSU so the System partition would be clean but when trying to update I get a derpy android with the text: ERROR. Does anyone know how can I fully revert to stock so I can install the update, would a factory reset solve my problem?
boa05 said:
Thank you very much, I've installed the stock recovery and also uninstalled xposed framework and SuperSU so the System partition would be clean but when trying to update I get a derpy android with the text: ERROR. Does anyone know how can I fully revert to stock so I can install the update, would a factory reset solve my problem?
Click to expand...
Click to collapse
You mean, a Cid face? LOL
You can revert by flashing the system.img via fastboot from the very same zip I mentioned before. You can get it here: http://builds.cyngn.com/factory/marmite/cm-13.1.4-ZNH2KAS5RM-marmite-signed-fastboot-c64f8f5d87.zip
boa05 said:
Thank you very much, I've installed the stock recovery and also uninstalled xposed framework and SuperSU so the System partition would be clean but when trying to update I get a derpy android with the text: ERROR. Does anyone know how can I fully revert to stock so I can install the update, would a factory reset solve my problem?
Click to expand...
Click to collapse
Exactly the same here. I flashed TWRP so I can install SuperSU for root access, now I've flashed back the stock recovery to apply the update and it ends in "Error".
It's also not possible to apply the downloaded zip-package manually (not via TWRP and not via Cyanogen recovery).
Log file says:
E: footer is wrong
E: Signatur verification failed
Installation aborted.
Click to expand...
Click to collapse
It's not an option for me to do a full reset each time they (who ever it might be in the future) release an update.
I bought this phone because I thought it might be easier to update/ get root access compared with e.g. Samsung devices, but in the end I must say Cyanogen OS is really bad and I hope there will be some mods soon, so I can get these bad/restrictive stock-OS off my phone...
zerospaced said:
Exactly the same here. I flashed TWRP so I can install SuperSU for root access, now I've flashed back the stock recovery to apply the update and it ends in "Error".
It's also not possible to apply the downloaded zip-package manually (not via TWRP and not via Cyanogen recovery).
Log file says:
It's not an option for me to do a full reset each time they (who ever it might be in the future) release an update.
I bought this phone because I thought it might be easier to update/ get root access compared with e.g. Samsung devices, but in the end I must say Cyanogen OS is really bad and I hope there will be some mods soon, so I can get these bad/restrictive stock-OS off my phone...
Click to expand...
Click to collapse
I haven't checked myself but linuxct seems to say its an img file. You need to flash img files with fastboot. Have you tried unziping the .zip file and seeing if there are img files (e.g system.img, recovery.img)
If you don't know how to use fastboot here is a good tutorial: https://forum.xda-developers.com/showthread.php?t=2277112
Hope this helps.
zerospaced said:
I flashed TWRP so I can install SuperSU for root access
Click to expand...
Click to collapse
You can enable that inside Developer options > Root access. There's no need to either alter your system nor unlock your bootloader if your only concern is root privileges.
zerospaced said:
... but in the end I must say Cyanogen OS is really bad and I hope there will be some mods soon, so I can get these bad/restrictive stock-OS off my phone...
Click to expand...
Click to collapse
Cyanogen is no more, Wileyfox's switching to an AOSP-based ROM through the following OTAs, which will be Android 7.0 Nougat and will start rolling on february. You've more info here: https://forum.xda-developers.com/swift-2/how-to/official-wileyfox-statement-regarding-t3528844
linuxct said:
You can enable that inside Developer options > Root access. There's no need to either alter your system nor unlock your bootloader if your only concern is root privileges.
Click to expand...
Click to collapse
No, I think that is only there in CyanogenMod (the community based custom rom) not in the Cyanogen OS (the proprietary OS for businesses). As far as I know no OEM can release an android phone with Gapps and root. We have an option there called "OEM unlock" which will allow you to unlock your bootloader (from a computer) but nothing else that would grant root out of box.
zerospaced said:
Exactly the same here. I flashed TWRP so I can install SuperSU for root access, now I've flashed back the stock recovery to apply the update and it ends in "Error".
It's also not possible to apply the downloaded zip-package manually (not via TWRP and not via Cyanogen recovery).
Log file says:
It's not an option for me to do a full reset each time they (who ever it might be in the future) release an update.
I bought this phone because I thought it might be easier to update/ get root access compared with e.g. Samsung devices, but in the end I must say Cyanogen OS is really bad and I hope there will be some mods soon, so I can get these bad/restrictive stock-OS off my phone...
Click to expand...
Click to collapse
Just flashing back to the stock recovery does not remove SuperSU. Due to your error I'm assuming you have a non-systemless root. In order to remove SuperSU you must flash http://downloadmirror.co/Uot/UPDATE-unSU.zip (with TWRP), and if that doesn't work I would recommend flashing back to full stock cyngn from: https://cyngn.com/support.
Cheers!
linuxct said:
You mean, a Cid face? LOL
You can revert by flashing the system.img via fastboot from the very same zip I mentioned before. You can get it here: http://builds.cyngn.com/factory/marmite/cm-13.1.4-ZNH2KAS5RM-marmite-signed-fastboot-c64f8f5d87.zip
Click to expand...
Click to collapse
Thank you very much, flashing the system.img with
Code:
fastboot flash system system.img
fixed the issue and I was able to update my system to the latest version and since it only changed the system partition, no data (files from internal/external storage) nor apps (not even their data) were deleted. After the update I had to flash TWRP, SuperSU and Xposed again.
boa05 said:
Thank you very much, I've installed the stock recovery and also uninstalled xposed framework and SuperSU so the System partition would be clean but when trying to update I get a derpy android with the text: ERROR. Does anyone know how can I fully revert to stock so I can install the update, would a factory reset solve my problem?
Click to expand...
Click to collapse
boa05 said:
Thank you very much, flashing the system.img with
Code:
fastboot flash system system.img
fixed the issue and I was able to update my system to the latest version and since it only changed the system partition, no data (files from internal/external storage) nor apps (not even their data) were deleted. After the update I had to flash TWRP, SuperSU and Xposed again.
Click to expand...
Click to collapse
Thank you, but unfortunately I've read this hint after trying the unsu method described here:
https://forum.xda-developers.com/showpost.php?p=63615067
I've installed the unsu-zip package and flashed the original boot.img via TWRP. It did not help, but since I did this I have another warning message when booting: "The dm-verity is not started in enforcing mode."
In the end I managed to get the update by installing the original zip package again and after this the OTA update worked.
What still remains is the new "dm-verity error message" right after booting....
Does anyone know if there is anywhere I can find the files to manually update to the new AOSP based ROM. Or has Wileyfox not released it?
(Or has anyone captured the PTA link?)
There is currently no new AOSP ROM. I've received only Cyanogen OS update (probably the last one?). According the Wileyfox statement on facebook, the new ROM (Nougat) will be released in the february...
rivierakid said:
There is currently no new AOSP ROM. I've received only Cyanogen OS update (probably the last one?). According the Wileyfox statement on facebook, the new ROM (Nougat) will be released in the february...
Click to expand...
Click to collapse
Nah they are releasing an update first to transition to their new rom.
"We have been ruthlessly testing this and planning a distribution for this update, with a rollout to be released beginning today with immediate effect." -Wileyfox Facebook
Click to expand...
Click to collapse
Then later (between February and end of Q1) they will release nougat. Its an easy mistake to make as they aren't too clear about it.
Thanks anyway.
It is unclear what kind of ROM will they release. According the statement it should be bloatware free OS
AOSP, Lineage OS, something else?
I really like cyanogenmod, so I hope there will be Lineage OS ROM in the future...
The new update
Hi, I'm not in the least technologically minded so please don't take the mick when I ask, will the new update delete the cyanogen os? Or is that something I will have to do? If so, what is safe to delete without damaging my phone?
Wow, that was a couple more questions then I had thought!
Thanks all.
Hello,
iam very frustrated by this OTA thing..
I had TWRP and SuperSU installed and i've tried everything but I can't install this OTA -.-" everytime i've tried it it gives me just an "ERROR".
1. I flashed the unSU zip in twrp.
2. I set the switch for stock recovery in developer options.
3 I fastboot flashed the stock recovery.img
4 I fastboot flashed the stock system.img
Then rebooted and did the update it just runs to like 20% and stops and then it shows me "ERROR" ..
Can somebody experienced help me pls This update is annoying I had to block it out of my mobile data use because it would eat up all my mobile data
EDIT: Maybe I have to relock my bootloader?
MCPoppa said:
Hello,
iam very frustrated by this OTA thing..
I had TWRP and SuperSU installed and i've tried everything but I can't install this OTA -.-" everytime i've tried it it gives me just an "ERROR".
1. I flashed the unSU zip in twrp.
2. I set the switch for stock recovery in developer options.
3 I fastboot flashed the stock recovery.img
4 I fastboot flashed the stock system.img
Then rebooted and did the update it just runs to like 20% and stops and then it shows me "ERROR" ..
Can somebody experienced help me pls This update is annoying I had to block it out of my mobile data use because it would eat up all my mobile data
EDIT: Maybe I have to relock my bootloader?
Click to expand...
Click to collapse
I don't think it'd be a good idea to mess with the bootloader for now. Also, I uninstalled SuperSU from the app. If you have xposed I suggest you uninstall that too (At least that's what I did). Sorry I can't help more I 'm still a little newby myself.
rivierakid said:
It is unclear what kind of ROM will they release. According the statement it should be bloatware free OS
AOSP, Lineage OS, something else?
I really like cyanogenmod, so I hope there will be Lineage OS ROM in the future...
Click to expand...
Click to collapse
Sadly, an OEM cannot rely on community-driven software, so it surely won't be CyanogenMod/Lineage. But, that doesn't mean that in the future we wouldn't be able to enjoy it thanks to custom ROM development
Jahane said:
Hi, I'm not in the least technologically minded so please don't take the mick when I ask, will the new update delete the cyanogen os? Or is that something I will have to do? If so, what is safe to delete without damaging my phone?
Wow, that was a couple more questions then I had thought!
Thanks all.
Click to expand...
Click to collapse
Welcome to the community!
This depends on what you understand about 'new update'. If the new update you're talking about is the currently rolling OTA, the one that's getting prompted on every phone right now, no, that won't delete CyanogenOS yet, but prepare the device to upgrade to a CyanogenOS-free Android 7.0 ROM, which will happen in a month or so. You won't have to do anything but let the phone update each and every single time it requests it. Cyanogen itself is not something you can remove as a user, unless you install what's called a custom ROM (this means, a different ROM software than the one provided by Wileyfox), so, you don't need to worry about it but keeping your device up-to-date as soon as it prompts you with an update ^_^
MCPoppa said:
Hello,
iam very frustrated by this OTA thing..
I had TWRP and SuperSU installed and i've tried everything but I can't install this OTA -.-" everytime i've tried it it gives me just an "ERROR".
1. I flashed the unSU zip in twrp.
2. I set the switch for stock recovery in developer options.
3 I fastboot flashed the stock recovery.img
4 I fastboot flashed the stock system.img
Then rebooted and did the update it just runs to like 20% and stops and then it shows me "ERROR" ..
Can somebody experienced help me pls This update is annoying I had to block it out of my mobile data use because it would eat up all my mobile data
EDIT: Maybe I have to relock my bootloader?
Click to expand...
Click to collapse
Try relocking like you said, but before, flash everything included in the latest CyanogenOS fasboot image zip (from here). To flash all of them at once, execute each and every of the following commands:
Code:
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot flash cache cache.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash modem NON-HLOS.bin
fastboot flash dsp adspso.bin
fastboot flash devcfg devcfg.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot flash keymaster keymaster.mbn
fastboot flash rpm rpm.mbn
fastboot flash sbl1 sbl1.mbn
fastboot flash splash splash.img
fastboot flash tz tz.mbn
Once done, relock your bootloader by doing:
Code:
fastboot oem lock
Please note, this probably doesn't fully lock your bootloader, as some propietary DRM keys might've been lost during the unlock process...
Good luck and please, keep us posted!
Back to Stock with @raystef66's Files
This guide used a method stemmed from paranoia. Now that we have decent flashable files everything is much simpler!
We'll be using raystef66's flashable TWRP files to go completely back to stock. At the end there's instructions if you want to lock your bootloader.
Be sure that you are on the latest TWRP version!
1) Files to Download:
- TWRP Flashable Bootstack/Stocksystem Image from here: Download Center. Download the latest BOOTSTACK and STOCKSYSTEM from there.
- If you want to lock the bootloader, also download the STOCK RECOVERY zip from the same stocksystem version that you downloaded. The flashable stock recovery zips are on the Factory Images Division, right above the TWRP flashable files.
- Magisk 15.2 (or latest), or SuperSU 2.79 (Latest not recommended ). If you will relock the bootloader, skip this part.
2) Installation
- Put all the files on the internal storage or SD card. Backup your important stuff from the internal storage, because you might need to format it!
- Go to TWRP. Wipe data, system and cache (don't format data though).
- Install the bootstack that you downloaded. Then install the stock system.
- If you will NOT relock the bootloader, install Magisk or SuperSU
- Reboot
If the phone asks for a password when it gets to the system, go to TWRP. It will ask for a password, just select Cancel. After you're on the main TWRP screen, select Wipe, then Format data, then type yes. After that, reboot.
3) 5 second screen removal / restore Fastboot
This is useful whether you're relocking the bootloader or not. Just go to raystef66's guide and follow it completely. After doing it your phone will have Fastboot (very good for softbricks and relocking), no 5 seconds screen (your phone will boot up faster) and it will be even closer to full stock.
4) ONLY FOR RELOCKING - Replace TWRP with Stock Recovery
Simply go to TWRP and flash the stock recovery file you downloaded. After that, enable OEM unlocking and USB debugging from the dev options, and then go to Fastboot and issue "fastboot oem lock".
@Choose an username... thanks for the credits.
you can return to stock in that way. you can reflash twrp with tool, allways checking bootloader still unlocked.
I allway update in this way, reboot to twrp, flash the recovery image, not a zip, its the same, but I make sure that the recovery correspond to the base version in my phone. after that, I reboot to system directly, update in the ota way, or the zip way, but from running android, rooted or not, and I dont have to wipe.
After update is done, the most important thing is leave the phone till it is completly booted, then you can reflash twrp with axon7tool again.
You dont need to root, you dont need anything to keep twrp. You only need to flash supersu or magisk if you use darkenfx zips. And if you do it, you have to backup wipe and restore cause you lose encryptation.
But thats all. I think stock rom its still the best, not in battery life, but in camera and bundled apps, It works perfectly, except, I have 2 bugs since allways, wake up with proximity sensor covered, and whatsapp online with app in background, I can live with that
I can re-lock bootloader after this process?
thanks for the guide.
Help Needed ! A2017g Bricked while trying to returning to stock
Hi, Please help me to get my Axon 7 in a working state. I was using Xenon HD Rom for A2017g Oreo. With twrp version as suggested in the guide.
I followed the procedure, installed the bootstack and then stock system B09
But when I tried to reboot, it said no OS Installed. Then I rebooted, and it was stuck at bootloader with no twrp and just the message as follows :
Android Recovery : ZTE/P996A04_N/ailsa_ii
7.1.1/NMF26V/20171120.101942
user/release-keys
Use volume up/down and power
and then certain other options in blue
Please help !
I also have a Problem.
I tried going back to stock from LOS 14.1. Now I am stuck on the 5 seconds screen, it won't continue.
The files I used were the Nougat B10 Files :-/
HansWursT619 said:
I also have a Problem.
I tried going back to stock from LOS 14.1. Now I am stuck on the 5 seconds screen, it won't continue.
The files I used were the Nougat B10 Files :-/
Click to expand...
Click to collapse
Enter the recovery, it should be the stock one (turn the phone off, then hold vol+ and power). Then download a stock B10 file (not the twrp flashable one) and install it from an SD card
No its not the stock one, its still TWRP.
I only flashed Bootstack and stock system (step 2). The reboot afterwards doesnt work
What do you mean by "a stock B10 file"? There are so many files types :-/
I am not quite sure what I should do now, do I have to do the EDL route? That one sounds confusing as well.
EDIT: I tried using B08 Files and now the reboot prompt in TWRP tells me there is no os installed.
Will I, like naveen09y, end up without TWRP if I reboot now?
HansWursT619 said:
No its not the stock one, its still TWRP.
I only flashed Bootstack and stock system (step 2). The reboot afterwards doesnt work
What do you mean by "a stock B10 file"? There are so many files types :-/
I am not quite sure what I should do now, do I have to do the EDL route? That one sounds confusing as well.
EDIT: I tried using B08 Files and now the reboot prompt in TWRP tells me there is no os installed.
Will I, like naveen09y, end up without TWRP if I reboot now?
Click to expand...
Click to collapse
Probably, so just don't. You should just wipe system and data, flash the bootstack, then the system. Also follow raystef's guide to "remove bootloader unlocked inscription"
I now managed to get the phone working with EDL flash of MM B10.
But I cant relock the bootloader :-/
Bascially my bootloader is gone so I cant reboot to it and do "fastboot oem lock".
Why is this such a hassle
HansWursT619 said:
I now managed to get the phone working with EDL flash of MM B10.
But I cant relock the bootloader :-/
Bascially my bootloader is gone so I cant reboot to it and do "fastboot oem lock".
Why is this such a hassle
Click to expand...
Click to collapse
You didn't follow my instructions. Follow raystef's removed unlocked bootloader inscription and you'll get fastboot back. You can do that with the phone on.
Don't relock it unless it's really necessary (i.e. warranty). If you're gonna sell it just follow that guide and don't relock, the 5 seconds screen will disappear and it'll look like it's locked
I cant follow the guide because I can't access the bootloader...
Also the TWRP files in https://forum.xda-developers.com/axon-7/how-to/guide-install-twrp-unlock-bl-flash-t3517379 this guide (step 6) are no longer accessible.
HansWursT619 said:
I cant follow the guide because I can't access the bootloader...
Also the TWRP files in https://forum.xda-developers.com/axon-7/how-to/guide-install-twrp-unlock-bl-flash-t3517379 this guide (step 6) are no longer accessible.
Click to expand...
Click to collapse
What? Lol
First of all - you are basically installing the bootloader with raystef's guide, so I have no idea why you want to enter it...
You have to enter TWRP and follow the guide from there.
The guide from Controllerboy is basically the same guide but it also has instructions on other things (i.e. unlock etc.). I don't know what you are trying to accomplish with it. Use EDL Tool by djkuz if you want to install TWRP (it is explained there how to do that).
Phone was rooted with Magisk 16, I was on AEX Android 8.1 ROM. I'm trying to return to stock and relock bootloader.
I wiped everything, I flashed A2017G-N-B10-bootstack and A2017G-N-B10-stocksystem from "TWRP flashable Bootstack/Stocksystem Images" section. Booted to system and now phone is stuck on the ZTE POWERED BY android boot screen. 5 minutes there. Is it normal?
Edit: Got tired of waiting and kept pressing the power button. After doing so, the phone reboots but same thing. And I can't access TWRP with VOL INCREASE + POWER BUTTON.... VOL DECREASE + POWER BUTTON takes me to Factory Test Mode.
aLexzkter said:
Phone was rooted with Magisk 16, I was on AEX Android 8.1 ROM. I'm trying to return to stock and relock bootloader.
I wiped everything, I flashed A2017G-N-B10-bootstack and A2017G-N-B10-stocksystem from "TWRP flashable Bootstack/Stocksystem Images" section. Booted to system and now phone is stuck on the ZTE POWERED BY android boot screen. 5 minutes there. Is it normal?
Edit: Got tired of waiting and kept pressing the power button. After doing so, the phone reboots but same thing. And I can't access TWRP with VOL INCREASE + POWER BUTTON.... VOL DECREASE + POWER BUTTON takes me to Factory Test Mode.
Click to expand...
Click to collapse
Try this.
Oki said:
Try this.
Click to expand...
Click to collapse
Yes, thanks. I already had seen it some minutes ago. It's so convenient that you posted this guide today lol
I want to flash stock rom from RR Nougat. I have installed latest twrp, flash bootstack and then stock system. After that I flash supersu 2.79. But when I press reboot system it say no OS installed
Willchi said:
I want to flash stock rom from RR Nougat. I have installed latest twrp, flash bootstack and then stock system. After that I flash supersu 2.79. But when I press reboot system it say no OS installed
Click to expand...
Click to collapse
The best way to return to stock is via EDL, for example MiFlash or EDL tool. If you have an U, then DrakenFX's zips can do that, it happened to me already. Usually G zips like raystef's work just fine.
Try using Magisk instead of SuperSU, just in case. Use 16.7
@Choose an username...
Thanks for posting this.
Credits to all concerned a big thumbs up.
I do however feel that there are to many versions of the Axon 7 packages and I can see why people are ending up with boot issues etc.
Syberclone said:
@Choose an username...
Thanks for posting this.
Credits to all concerned a big thumbs up.
I do however feel that there are to many versions of the Axon 7 packages and I can see why people are ending up with boot issues etc.
Click to expand...
Click to collapse
what
you do realize this guide is older than a year right?
Yeah, its all good
Note 8 V5 Bootloaders If Not Already On Safestrap Follow My EDL Pie Safestrap Method
Please Note This Is Not A Root Method For Oreo Or Pie. As Of Now There Is Still No Root Method For Oreo Or PieThis Takes Some Patience To Install
N8 SM-N955U/U1/W Install Instructions And Files
Download
SM_N950_DSF6_SYSTEM.rar Latest Build
Install Instructions Safestrap Method
Make Sure The Latest Samsung Drivers Are Installed. They Can Be Found Here
1. Copy ****_SYSTEM.img to your internal sdcard. Reboot to download mode and in BL slot in Odin flash Use The BL_ENG_BOOTLOADERS_SAFESTRAP_N950U_V5.tar.md5 and reboot to safestrap
2. In Safestrap choose install then choose select storage and select internal storage click ok then at bottom choose install image and choose ****_SYSTEM.img then select flash to system image then swype to flash
3. Now chose zip and flash Safestrap-4.10-B03-GREATQLTE-PIE.zip
4. To leave safestrap reboot to download mode
5. In odin load BL_N950USQU5****tar.md5 in BL slot and flash
To Enter And Exit Safestrap After Intitial Install
1. To enter safetrap flash the BL_ENG_BOOTLOADERS_SAFESTRAP_N950U_V5.tar.md5 in BL Slot in odin phone will boot too safestrap sometimes it may take a minute to do so
2. To leave safestrap reboot to bootloader or download still does not work so you still need to manually reboot to bootloader
3. Use modded Odin and load BL_N950USQU5****tar.md5 In BL Slot
Helpful Key Combos
Recovery Mode
Bixby + Volume Up + Power @ Same time
Download Mode
Bixby + Volume Down + Power @ Same time
Safe Mode
Phone Powered Off
Press and hold the Power key past the model name screen.
When “SAMSUNG” appears on the screen, release the Power key.
Immediately after releasing the Power key, press and hold the Volume down key.
Maintenance Mode
Press and hold the Power + Volume Down buttons for approximately 10
Bugs:
DO NOT USE ENCRYPTION
Safestrap rom slots do not work
Safestrap might not read larger than 64gig sd cards on some cards
Formating data in safestrap may cause reboot so make sure to format data very last thing
What Is Safestrap
Safestrap is a Bootstrap / Recovery for locked bootloader phones. Safestrap is now based on TWRP Recovery (a touch based recovery) and you can perform .zip installs, backups and restores here.
View attachment 4531040View attachment 4531041View attachment 4531042View attachment 4531043View attachment 4531044View attachment 4531045
Credits:
- @Raymonf for modified odin
- @afaneh92 for safestrap Main Thread Here Consider a donation to him he worked along time on this Donation Link
- @me2151 for finding this method
- @tytydraco for some instructions
- @mweinbach for some instructions
- @Craz Basics for xposed on non rooted
- @partcyborg for finding the root method!
- @elliwigy for being great help and original S8 root
- @rayan-refoua for boot animation
- @SamGuy2020 for testing S8 install method
Click to expand...
Click to collapse
View attachment Safestrap-4.10-B03-GREATQLTE-NOUGAT.zip Needed If running nougat rom
View attachment Safestrap-4.10-B03-GREATQLTE-PIE.zip Needed If running Pie rom
Main question I have is about the battery do we get %100 on the unrooted pie?
DroidisLINUX said:
Main question I have is about the battery do we get %100 on the unrooted pie?
Click to expand...
Click to collapse
Still 80% battery.
Sent from my Pixel 3 XL
DroidisLINUX said:
Main question I have is about the battery do we get %100 on the unrooted pie?
Click to expand...
Click to collapse
Yes
Sent using some kind of device I modified
Eudeferrer said:
Still 80% battery.
Sent from my Pixel 3 XL
Click to expand...
Click to collapse
80 percent is only on rooted nougat. Pie is unrooted and battery will charge to 100 percent
Sent using some kind of device I modified
jrkruse said:
80 percent is only on rooted nougat. Pie is unrooted and battery will charge to 100 percent
Sent using some kind of device I modified
Click to expand...
Click to collapse
Magisk just tweeted that the "world's first true system-as-root" was just created. Do you think that with this we could achieve root for Pie? Or would this not change anything?
Sent from my Pixel 3 XL
Eudeferrer said:
Magisk just tweeted that the "world's first true system-as-root" was just created. Do you think that with this we could achieve root for Pie? Or would this not change anything?
Sent from my Pixel 3 XL
Click to expand...
Click to collapse
All that a and b partition stuff reefers to phones that were released with pie. Our phone is still old school no treble support.
Sent using some kind of device I modified
Would I have to flash every time i want to enter safestrap?
also if I were to want to revert to the rooted nougat ROM, do I have to follow all the steps on the rooting guide or could I just flash an image through safestrap?
purpleuser said:
also if I were to want to revert to the rooted nougat ROM, do I have to follow all the steps on the rooting guide or could I just flash an image through safestrap?
Click to expand...
Click to collapse
you can just flash image in safestrap and then flash the safestrap for nougat zip in post 2 (or its included in the new DSF6 build) after you flash the nougat system image in safestrap to get back to nougat safestrap. If you fail to flash the safestrap zip for nougat your phone will automatically boot to safestrap on every reboot on a nougat rom.
jrkruse said:
you can just flash image in safestrap and then flash the safestrap for nougat zip in post 2 (or its included in the new DSF6 build) after you flash the nougat system image in safestrap to get back to nougat safestrap. If you fail to flash the safestrap zip for nougat your phone will automatically boot to safestrap on every reboot on a nougat rom.
Click to expand...
Click to collapse
Thanks for answering my question. I'm new to all of this, so I appreciate the guidance.
Another question. Would I brick my phone if I tried to flash a ROM image with a v3 bootloader through safestrap?
purpleuser said:
Thanks for answering my question. I'm new to all of this, so I appreciate the guidance.
Another question. Would I brick my phone if I tried to flash a ROM image with a v3 bootloader through safestrap?
Click to expand...
Click to collapse
You can flash a system image from v3 firmware but must remain on v5 boot and recovery images and bootloaders and modems
Sent using some kind of device I modified
Nice this ROM just goes over the Nougat image with all my settings and apps intact. Even the pay apps are working (probably because no root). Now I just need to find a way to flash Viperaudio drivers then I'm all set.
jrkruse said:
You can flash a system image from v3 firmware but must remain on v5 boot and recovery images and bootloaders and modems
Sent using some kind of device I modified
Click to expand...
Click to collapse
Awesome. This is great. Thanks
Hey, is it alright to do an update for June Security Patch? It's changing my build number to N950USQS / N950UOYN - DSF3.
vman00 said:
Nice this ROM just goes over the Nougat image with all my settings and apps intact. Even the pay apps are working (probably because no root). Now I just need to find a way to flash Viperaudio drivers then I'm all set.
Click to expand...
Click to collapse
I've tried to flash a few different viper zips in safestrap to no avail. The driver would not load. I was told that root is needed to actually "load" the drivers, even if you install them via safestrap. I'm not sure this is true though because if it was, the viper app would ask for root privs, wouldn't it? Anyways, if you make any progress let me know I need that viper in my life.
BotsOne said:
I've tried to flash a few different viper zips in safestrap to no avail. The driver would not load. I was told that root is needed to actually "load" the drivers, even if you install them via safestrap. I'm not sure this is true though because if it was, the viper app would ask for root privs, wouldn't it? Anyways, if you make any progress let me know I need that viper in my life.
Click to expand...
Click to collapse
might as well wait for rootless
https://forum.xda-developers.com/android/apps-games/app-viper4android-fx-2-6-0-0-t3774651
vman00 said:
might as well wait for rootless
https://forum.xda-developers.com/android/apps-games/app-viper4android-fx-2-6-0-0-t3774651
Click to expand...
Click to collapse
You should be able to change the permissions for the files themselves with safestrap you can change file permissions if it allows us read write to system then you could try making an init script to load in on boot with rooted permissions to load the viperaudio like an init.d
Vipermod start service this is just off of the top of my head but I will look into more this weekend when I got some time to test out the new rom and safestrap
Viper will not work without root because it needs to execute a script at startup and no scripts will execute on a stock system. There were or maybe are rootless version but they still needed a permissive kernel to work
Sent using some kind of device I modified