Hi,
- I have rooted the 912 744 RAZR with Doomlord's method.
- I installed Safestrap
- backed up stock ROM is Safe Mode Disabled
- installed RAZRX ROM in Safe Mode Enabled.
How can I go totally back to stock as when phone was when picked up from VZW?
1. boot into Safe Mode Disabled to get back to original ROM?
2. Uninstall Safestrap by simply using Manage Apps and do uninstall? Is that gonna take care of deleting the safe side and all that?
3. Unroot with Doomlord's unroot?
Thank you!
bracca said:
Hi,
- I have rooted the 912 744 RAZR with Doomlord's method.
- I installed Safestrap
- backed up stock ROM is Safe Mode Disabled
- installed RAZRX ROM in Safe Mode Enabled.
How can I go totally back to stock as when phone was when picked up from VZW?
1. boot into Safe Mode Disabled to get back to original ROM?
2. Uninstall Safestrap by simply using Manage Apps and do uninstall? Is that gonna take care of deleting the safe side and all that?
3. Unroot with Doomlord's unroot?
Thank you!
Click to expand...
Click to collapse
Use the fastboot files then after that, do a factory reset before you reboot.. You are completely stock then...
thank you, detr0yt, but I have no idea how to use fastboot. I have a vague idea of what fastboot is. Can you please summarize?
edit:
ok, I found this on another Fastboot thread on another forum:
METHOD:
RSD Lite v5.6 - and the combined files in the OP
Loaded the file into RSD Lite v5.6
Booted the phone into AP Fastboot
Hit START on RSD - and let it run its course.
I guess I'll try it...
bracca said:
thank you, detr0yt, but I have no idea how to use fastboot. I have a vague idea of what fastboot is. Can you please summarize?
Click to expand...
Click to collapse
Check the thread in this section for the fastboot files. You download files and use RSD Lite 5.6. Plug your phone in and select the files you downloaded. It'll flash your phone will all the stock ROM. You'll then need to upgrade to .748 (either check for OTA updates or just download and flash it in Android recovery)
Related
I have a phone on 4.1.57 running GreyBlur. The Android Version is 2.2.1
I haven't accepted any OTA updates, but I recently found out that Gingerbread is out.
What is the best way to go on about rooting the phone after the gingerbread update? Flash back to stock, then update, then root? If someone could point me in the right direction it'd be greatly appreciated.
thank you.
1) root your phone...using this guide...http://www.youtube.com/watch?v=sQVVqxvg4Go (files that you need are under description of that video..)
2) unlock bootloader...using this guide..http://forum.xda-developers.com/showthread.php?t=1136261
3) install Tenfar's CWM using this guide...http://forum.xda-developers.com/showthread.php?t=1138541
4) choose a rom and flash Via CWM
***Stay away from RSD as much as possible***
deziguy420 said:
1) root your phone...using this guide...http://www.youtube.com/watch?v=sQVVqxvg4Go (files that you need are under description of that video..)
2) unlock bootloader...using this guide..http://forum.xda-developers.com/showthread.php?t=1136261
3) install Tenfar's CWM using this guide...http://forum.xda-developers.com/showthread.php?t=1138541
4) choose a rom and flash Via CWM
***Stay away from RSD as much as possible***
Click to expand...
Click to collapse
Is RSD and CWM the same thing? I don't understand what these two are.
If I'm on 2.2.2, stock w/ root and side-loading enabled, do I skip #1?
why isn't pudding used in any of this?
yes skip #1
RSD is a flashing tool...
CWM is used for flashing too but it's much safer then RSD...
in order to unlock your phone's bootloader u have to do one step using RSD here is a pretty good video tutorial http://www.youtube.com/watch?v=H02N4p9vEg0 on how to unlock ur bootloader...
on my previous post...2nd link is referring to pudding is it not?
deziguy420 said:
1) root your phone...using this guide...http://www.youtube.com/watch?v=sQVVqxvg4Go (files that you need are under description of that video..)
2) unlock bootloader...using this guide..http://forum.xda-developers.com/showthread.php?t=1136261
3) install Tenfar's CWM using this guide...http://forum.xda-developers.com/showthread.php?t=1138541
4) choose a rom and flash Via CWM
***Stay away from RSD as much as possible***
Click to expand...
Click to collapse
1) I'm already rooted.
2) You say to stay away from RSD but to unlock the bootloader I need to use it correct?
3) I already have Tenfar's CWM.
4) Just choose a ROM that's updated with Gingerbread and Flash?
Thanks for your help
rAFTA! said:
1) I'm already rooted.
2) You say to stay away from RSD but to unlock the bootloader I need to use it correct?
3) I already have Tenfar's CWM.
4) Just choose a ROM that's updated with Gingerbread and Flash?
Thanks for your help
Click to expand...
Click to collapse
there are 2 versions of cwm. one for locked and one for unlocked. after you unlock you have to fastboot flash recovery to get the good CWM then you can flash roms properly.
RSD the 1.83 pudding
Fastboot oem unlock to unlock bootloader
fastboot flash recovery to get the unlocked CWM
CWM recovery to install roms
As long as you have not OTA to gingerbread then RSD is ok but not recommended. If youhave the OTA gingerbread then rsd will hard brick your device if you try to go back to an older build.
rAFTA! said:
1) I'm already rooted.
2) You say to stay away from RSD but to unlock the bootloader I need to use it correct?
3) I already have Tenfar's CWM.
4) Just choose a ROM that's updated with Gingerbread and Flash?
Thanks for your help
Click to expand...
Click to collapse
if you already have Tenfar's CWM..then wt r u waiting for ...go crazy and start flashing...
I have accidentally wiped the stock Rom and install CM Rom on it without active any Rom slot and backup the stock Rom,
after flash the Rom and reboot,i can't access into system.
so any solution to unbrick the device?currently i can access Bootloader.
Use RSDLite to flash your stock ROM back.
DROID RAZR with Tapatalk 4
neo.ank said:
Use RSDLite to flash your stock ROM back.
DROID RAZR with Tapatalk 4
Click to expand...
Click to collapse
Thanks but i have new problem for RSD Lite "The phone faild to swith to fastboot mode",i try few method also didn't work.
Do you have any idea?
your in luck..lol. i just did this today actually. Does your phone enter in fastboot at all? if so lookup this DROID_RAZR_Utility_Jellybean_XT912_WinMacLin
i had it reload my phone via fastboot without any system on my phone.
frususx said:
Thanks but i have new problem for RSD Lite "The phone faild to swith to fastboot mode",i try few method also didn't work.
Do you have any idea?
Click to expand...
Click to collapse
I only have experience with M and HD but I believe the OG Razr is the same in that you need to go into fastboot mode on the phone, prior to plugging it into the computer. If you're leaving the phone plugged in and then trying to reboot into fastboot, that might be causing the error.
same here
frususx said:
I have accidentally wiped the stock Rom and install CM Rom on it without active any Rom slot and backup the stock Rom,
after flash the Rom and reboot,i can't access into system.
so any solution to unbrick the device?currently i can access Bootloader.
Click to expand...
Click to collapse
i've also experienced the same problem now and im still working on it.
ill give you feedback once im done alright?
fixed!
frususx said:
I have accidentally wiped the stock Rom and install CM Rom on it without active any Rom slot and backup the stock Rom,
after flash the Rom and reboot,i can't access into system.
so any solution to unbrick the device?currently i can access Bootloader.
Click to expand...
Click to collapse
i just fixed my razr! be sure to check your phone it has dead battery or low battery or still has battery and just follow this simple steps:
A. Enter AP Fastboot mode. how to enter ap fastmode mode?
1. press and hold the volume up & down buttons and the power button simultaneously for i think 10 secs.
2. you can also view it here: http://www.youtube.com/watch?v=togllOW3qvw
3. once youre on the Recovery mode:
3.1. Scroll down by pressing the volume down button and choose AP Fastboot mode
3.2 Once youre in fastboot mode connect your phone on the computer and launch RSD Lite application
3.3. RSD lite will detect your phone once its connected
3.4 then proceed to F.
B. if you phone is already lowbat?
you just cant figure it out for you have no OS to show the battery when you charge it.
you have to use motorola factory cable. i have created mine and you can follow the steps here: http://www.youtube.com/watch?v=XwwI_6doBWk
C. if everything is OK then just follow A.
D. download RSD Lite application. you can search that on google. Im using 5.7 version and its working.
E. Download the Firmware here: http://forum.xda-developers.com/showthread.php?t=2231289
1. there are different versions of razr firmwares you can choose depending your choice or place. Im from Philippines, i supposed to choose Asean version but razr has no Asean version for JB release so I use Europe version. Thats depending on you actually.
F. Open the RSD lite application:
1. on the "Filename" window choose the "Firmware" that you downloaded by clicking on the "Box" (has 3 dots) beside the filename window.
2. a pop up windown will appear and choose "Decompress only".
3. then click "Start" button on the RSD lite application.
4. Wait...
5. Wait...
6. Wait...
7. Voila! congratulations your Razr is alive!
proven and tested motorola phones are extremely great when it comes to quality!
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
I just used casual to root and unlock my note 2.i have root and it booted up on twrp but I want to check if I am unlocked bootloader. Is there a way I can check? In my about phone my status says normal
If the bootloader was not unlocked it would overwrite any changes you make to recovery and system files. So as long as you can reboot without losing TWRP or any custom ROM you've installed you're golden.
Unlocked Bootloader?
Jiggabitties said:
If the bootloader was not unlocked it would overwrite any changes you make to recovery and system files. So as long as you can reboot without losing TWRP or any custom ROM you've installed you're golden.
Click to expand...
Click to collapse
It's been a while for me since I rooted my phone, and I don't know if I unlocked my bootloader either... I have never installed a custom ROM, I only rooted so I could tether. But now that the new OTA update keeps trying to install itself, I need to fix this because it's extremely annoying. I read a thread that said I need to flash this: http://forum.xda-developers.com/showthread.php?t=2578458, but it said that I need my bootloader to be unloacked, and therein lies my question...
Am I thinking this through the correct way?
If you just want to stop the update notification fteeze SDM 1.0
James Mac said:
It's been a while for me since I rooted my phone, and I don't know if I unlocked my bootloader either... I have never installed a custom ROM, I only rooted so I could tether. But now that the new OTA update keeps trying to install itself, I need to fix this because it's extremely annoying. I read a thread that said I need to flash this: http://forum.xda-developers.com/showthread.php?t=2578458, but it said that I need my bootloader to be unloacked, and therein lies my question...
Am I thinking this through the correct way?
Click to expand...
Click to collapse
That is the correct thread. Easy way to check is to boot into recovery and see if there is a custom recovery installed. Power down your device, hold down the volume up + verizon button, then power up. Hold volume up + verizon button until you see the galaxy note 2 splash screen. If it boots into TWRP than you're still good. But you will probably want to update to the latest version of TWRP before you go installing any new roms.
Jiggabitties said:
That is the correct thread. Easy way to check is to boot into recovery and see if there is a custom recovery installed. Power down your device, hold down the volume up + verizon button, then power up. Hold volume up + verizon button until you see the galaxy note 2 splash screen. If it boots into TWRP than you're still good. But you will probably want to update to the latest version of TWRP before you go installing any new roms.
Click to expand...
Click to collapse
Thanks Jiggabitties, I updated TWRP and downloaded official firmware.md5 file and the Mj9 DeOdex file to my pc. Should I transfer those files to the sd card in my phone and install from the TWRP menu? If so, I do the official firmware file first, right? Then the deodex...?
Thanks for all your help man
James Mac said:
Thanks Jiggabitties, I updated TWRP and downloaded official firmware.md5 file and the Mj9 DeOdex file to my pc. Should I transfer those files to the sd card in my phone and install from the TWRP menu? If so, I do the official firmware file first, right? Then the deodex...?
Thanks for all your help man
Click to expand...
Click to collapse
The firmware update is done in ODIN and the ROM is done in TWRP.
James Mac said:
Thanks Jiggabitties, I updated TWRP and downloaded official firmware.md5 file and the Mj9 DeOdex file to my pc. Should I transfer those files to the sd card in my phone and install from the TWRP menu? If so, I do the official firmware file first, right? Then the deodex...?
Thanks for all your help man
Click to expand...
Click to collapse
Yes start by transferring the files to your SD card.
The firmware package from that thread is meant to be flashed via ODIN. If you are not comfortable in flashing firmware via ODIN then use this in it's place... https://www.dropbox.com/s/lz29kvrvzfttfpu/MJ9ModemParams.zip This is a TWRP flashable version of the firmware.
Place the MJ9 Deodex and the modemparam.zip I linked to above on your SD card. Flash the ROM file first, then the modemparam.zip. Then clear cache/ dalvik and reboot. That should be all you need to do. If when you boot you don't get service, then you will need to go ahead and flash the firmware vid ODIN. Some users have no issues with the flashable version that I linked above, some users do.
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