[Guide]ATT KitKat leak working with root - Moto X General

I have been trying to get the KitKat leak working in a safestrap rom slot for days. Each time it failed, and I concluded that it was currently incompatible with the hijack Hashcode was using. So, I tried flashing my KK rom to the stock slot, and then I immediately flashed supersu. Voila, KitKat with root on my locked at&t moto x!
The interesting thing is that this method should work for any rom that is compatible with the stock kernels (because locked bootloader wont allow any other kernel). Hopefully this will 'open the floodgates' to flashing AOSP roms on locked devices that can run safestrap.
I AM NOT RESPONSIBLE IF YOU MESS UP YOUR PHONE. With that said, this doesn't touch your bootloader, and you should be able to restore back to stock if there is a problem.
Here are the steps I followed on my locked ATT moto x starting with the at&t stock .51 rom:
1) extract ext4 filesystem image from leak's system.img
2) used android kitchen (thanks dsixda) to cook a flashable rom and fixed some symlinks with help from the updater-script found in dhacker29's 4.4 rom
3) root (pwnmymoto - thanks jcase)
4) install safestrap (thanks Hashcode)
5) copied the rom I cooked to sdcard
6) copied supersu flashable zip to sdcard (thanks chainfire)
7) booted to SS TWRP recovery
8) switched to stock rom slot
9) flashed my cooked rom
10) immediately flashed supersu
11) rebooted into bootloader
12) flashed kitkat kernel: fastboot flash boot boot.img
13) cleared cache and userdata
(I left the modem from the 4.2.2 .54 update)
Rebooted to kitkat with root!
I haven't tested bluetooth, but wifi and gps work. Strangely, the safestrap 'recovery or continue' screen is still there, but the /ss directory is empty. (I would like to know how to manually remove ss, as it is almost certainly not working now.)
I would be happy to share my flashable 4.4 rom, but I noticed that the original leak was taken down. What/where is the smart place to get this up?

I found a place to upload the rom: http://forum.xda-developers.com/showthread.php?p=47451659#post47451659
Hopefully the instructions there are clear...

Can I ask how you extracted from the system.img? I tried to follow the guide that uses ext4_unpacker, but it won't open it. It just says unknown file format. Guessing you did it on a Linux machine?

Ctrl-Freak said:
I have been trying to get the KitKat leak working in a safestrap rom slot for days. Each time it failed, and I concluded that it was currently incompatible with the hijack Hashcode was using. So, I tried flashing my KK rom to the stock slot, and then I immediately flashed supersu. Voila, KitKat with root on my locked at&t moto x!
The interesting thing is that this method should work for any rom that is compatible with the stock kernels (because locked bootloader wont allow any other kernel). Hopefully this will 'open the floodgates' to flashing AOSP roms on locked devices that can run safestrap.
I AM NOT RESPONSIBLE IF YOU MESS UP YOUR PHONE. With that said, this doesn't touch your bootloader, and you should be able to restore back to stock if there is a problem.
Here are the steps I followed on my locked ATT moto x starting with the at&t stock .51 rom:
1) extract ext4 filesystem image from leak's system.img
2) used android kitchen (thanks dsixda) to cook a flashable rom and fixed some symlinks with help from the updater-script found in dhacker29's 4.4 rom
3) root (pwnmymoto - thanks jcase)
4) install safestrap (thanks Hashcode)
5) copied the rom I cooked to sdcard
6) copied supersu flashable zip to sdcard (thanks chainfire)
7) booted to SS TWRP recovery
8) switched to stock rom slot
9) flashed my cooked rom
10) immediately flashed supersu
11) rebooted into bootloader
12) flashed kitkat kernel: fastboot flash boot boot.img
13) cleared cache and userdata
(I left the modem from the 4.2.2 .54 update)
Rebooted to kitkat with root!
I haven't tested bluetooth, but wifi and gps work. Strangely, the safestrap 'recovery or continue' screen is still there, but the /ss directory is empty. (I would like to know how to manually remove ss, as it is almost certainly not working now.)
I would be happy to share my flashable 4.4 rom, but I noticed that the original leak was taken down. What/where is the smart place to get this up?
Click to expand...
Click to collapse
Glad to see locked BLs getting some love. Any chance of KK screenshots? No one seems to have uploaded them on any thread. How has your experience been with it so far?

freak4dell said:
Can I ask how you extracted from the system.img? I tried to follow the guide that uses ext4_unpacker, but it won't open it. It just says unknown file format. Guessing you did it on a Linux machine?
Click to expand...
Click to collapse
This took me a day to figure out. I used simg2img in ubuntu.

anirudh412 said:
... How has your experience been with it so far?
Click to expand...
Click to collapse
The only material problem I am having is battery life - it seems noticeably worse that the att .54 ota version.

Related

Update to 2.3.6 and keep root

If you haven't already done so, install Rom Manager and flash Clockworkmod Recovery. It doesn't replace the actual recovery partition or the files that restore it so it won't affect flashing the update.
If you received an OTA notice don't flash it. You can go into /system/cache and copy it, or download it from the links in other threads. Place the update zip (no need to rename it) on the root of your sd card.
To install the update you must be fully stock (root is okay). That means any changed or deleted system files (including bootanimation.zip) will prevent the update from flashing. You will get a status 7 error. If you used Bloat Freezer you must defrost all before flashing the zip or it will error.
Also, have available whatever zip you used to root your Nexus one (i.e., su.zip or superboot, etc.) and put on the root of your sd card.
Once your system is back to stock reboot into CWM recovery and select flash zip from sd card. Then flash the 2.3.6 update file. Then DO NOT reboot yet. Now flash your root zip. After you have flashed both the udpate and the root zip you can reboot your phone. No need to wipe anything.
When your phone reboots you will have 2.3.6 and it will still be rooted. No bootloader gymnastics necessary.
I am using stock (almost) version of GRJ22 , but unfortunatelly I got the status 7 error when I tried to apply the update via clockworkmod recovery. I guess that's because I have already integrated some system apps into ROM using Titanium Backup.
So, if I flash stock vanilla GRJ22, then SU, then GRK39F (the incremental update) and finally SU again, won't that do the job??
Thanks..
Nikos_s3 said:
I am using stock (almost) version of GRJ22 , but unfortunatelly I got the status 7 error when I tried to apply the update via clockworkmod recovery. I guess that's because I have already integrated some system apps into ROM using Titanium Backup.
So, if I flash stock vanilla GRJ22, then SU, then GRK39F (the incremental update) and finally SU again, won't that do the job??
Thanks..
Click to expand...
Click to collapse
Yes, that will do nicely. Just need to get back to GRJ22 stock before you can flash the udpate. The updater-script does an assert and checks the md5 checksum of every system file before it allows the update to flash. If it doesn't find all stock files or checksums don't match what it is looking for, you get a status 7 error and the line above will show which file it stopped on. So you can look at those messages and keep restoring files it wants (if only a few) without having to flash completely back to stock.
I guess that would take much time, as almost all of my google apps are integrated into ROM...so I will try to follow the procedure I wrote earlier and if that won't work, I will try a ready stock,rooted ROM (Fireb33 has done it already)..
thanks mate..
Why so complicated?
You can update to 2.3.6 AND keep root even much more simple:
1.) Update from OTA to 2.3.6 (and loose root).
2.) Flash Superboot from Madaco and get back root.
Done in 3 minutes.. No need to flash, recover, overwrite and/or whatever, no need for ADB, no messing:
Code:
https://bexton.net/2011/09/24/root-access-for-nexus-one-on-android-2-3-6-grk39f-superboot/
Bexton said:
You can update to 2.3.6 AND keep root even much more simple:
1.) Update from OTA to 2.3.6 (and loose root).
2.) Flash Superboot from Madaco and get back root.
Done in 3 minutes.. No need to flash, recover, overwrite and/or whatever, no need for ADB, no messing:
Code:
https://bexton.net/2011/09/24/root-access-for-nexus-one-on-android-2-3-6-grk39f-superboot/
Click to expand...
Click to collapse
That's only for those who have the bootloader unlocked?
_raz_ said:
That's only for those who have the bootloader unlocked?
Click to expand...
Click to collapse
Well, yep. That method indicates your (phones) bootloader is unlocked. But as it's the N1, unlocking the bootloader is just 19 (up to 25) characters away -> "fastboot(-linux) oem unlock".
Edit: By the way, i looked up that post from an android platform engineer:
Code:
groups.google.com/group/android-platform/msg/b7d83992dd92accb?dmode=source
The N1 is just made for that.
tried superboot but wifi down
I flashed the update for 2.3.6 and then superboot but my wifi gives an error when I try to turn it on.
New Superboot file for GRK39F?
Is there a new Superboot file for the new OTA update?
jboxer said:
If you haven't already done so, install Rom Manager and flash Clockworkmod Recovery. It doesn't replace the actual recovery partition or the files that restore it so it won't affect flashing the update.
If you received an OTA notice don't flash it. You can go into /system/cache and copy it, or download it from the links in other threads. Place the update zip (no need to rename it) on the root of your sd card.
To install the update you must be fully stock (root is okay). That means any changed or deleted system files (including bootanimation.zip) will prevent the update from flashing. You will get a status 7 error. If you used Bloat Freezer you must defrost all before flashing the zip or it will error.
Also, have available whatever zip you used to root your Nexus one (i.e., su.zip or superboot, etc.) and put on the root of your sd card.
Once your system is back to stock reboot into CWM recovery and select flash zip from sd card. Then flash the 2.3.6 update file. Then DO NOT reboot yet. Now flash your root zip. After you have flashed both the udpate and the root zip you can reboot your phone. No need to wipe anything.
When your phone reboots you will have 2.3.6 and it will still be rooted. No bootloader gymnastics necessary.
Click to expand...
Click to collapse
I want to update to gingerbread and looking for the proper guidance going forward. I've done some looking around the forums but i'm still unclear if i need to unroot or install a stock build, etc. What i know is the phone is rooted and sim unlocked. How can i check to see if the bootloader is open/locked?
Current specs:
android version 2.2.1
Baseband 32.41.00.32U_5.08.00.04
Kernal Version 2.6.35.9-cyanogenmod
Mod Version: Cyanogenmod-6.1.1-N1
Build: FRG83D
edit:
Please treat me like an idiot and walk me through this process. It's be utterly frustrating and I'm a stone's throw away from busting out my Nokia 3390 (equipped with led disco keypad).
If your bootloader is unlocked you will see an unlocked padlock on the boot up screen...

4.4.2 (KOT49H) update fails on rooted device

Received the update today but it failed to install. I'm running the stock rom KRT16S. My Nexus 10 is rooted and my recovery is TWRP 2.6.3.1. I have added nothing else to this rom except a few apps from the google play store. I wanted to try again but couldn't find where the OTA is stored. It wasn't in the /cache/fota folder. So I downloaded a flashable zip from the net. But this update file failed to install also. I've seen a few others have success installing the update. I just don't know what's preventing me from updating. I welcome your suggestions. Thanks.
Same here on my Nex5.
It seems, that some custom zips changed my stock (rooted) rom in this way that I am not able to install the 4.4.2 update.
I got similar issue on my Nex4 in the past, I could help me out by flashing full rom (rooted) deodexed, but where can I find the full rom of 4.4.2 for my Nex5 now?
Anybody can give me a clue?
Thank u very much.
Greetz from Germany.. Fred
Lexus One said:
Received the update today but it failed to install. I'm running the stock rom KRT16S. My Nexus 10 is rooted and my recovery is TWRP 2.6.3.1. I have added nothing else to this rom except a few apps from the google play store. I wanted to try again but couldn't find where the OTA is stored. It wasn't in the /cache/fota folder. So I downloaded a flashable zip from the net. But this update file failed to install also. I've seen a few others have success installing the update. I just don't know what's preventing me from updating. I welcome your suggestions. Thanks.
Click to expand...
Click to collapse
amplifier1980 said:
Same here on my Nex5.
It seems, that some custom zips changed my stock (rooted) rom in this way that I am not able to install the 4.4.2 update.
I got similar issue on my Nex4 in the past, I could help me out by flashing full rom (rooted) deodexed, but where can I find the full rom of 4.4.2 for my Nex5 now?
Anybody can give me a clue?
Thank u very much.
Greetz from Germany.. Fred
Click to expand...
Click to collapse
Hi Fred, and greetz from Ohio. I'm not aware of anything in the 4.4.2 flavor right now for the Nex10. I'm not sure about the Nex5. I think we're just going to have to wait. But I'd like to have the same thing. A lean & clean deodexed stock rooted 4.4.2 rom with a few performance tweaks. Like the old "Cleanrom" by scrosler. As for right now, did you try an ADB Sideload update to 4.4.2 using Wug's Toolkit? http://www.wugfresh.com/faqs/how-to-update-ota-not-working/
Lexus One said:
Hi Fred, and greetz from Ohio. I'm not aware of anything in the 4.4.2 flavor right now for the Nex10. I'm not sure about the Nex5. I think we're just going to have to wait. But I'd like to have the same thing. A lean & clean deodexed stock rooted 4.4.2 rom with a few performance tweaks. Like the old "Cleanrom" by scrosler. As for right now, did you try an ADB Sideload update to 4.4.2 using Wug's Toolkit?
Click to expand...
Click to collapse
Hi. Meanwhile i found a thread in nexus5 Android development area which contains both deodexed and odexed stock rooted full rom . so i just flashed odexed Version over my 4.4... Now i am on 4.4.2 finally... And still rooted..
Thank u anyway..
Greetz, fred
Lexus One said:
Received the update today but it failed to install. I'm running the stock rom KRT16S. My Nexus 10 is rooted and my recovery is TWRP 2.6.3.1. I have added nothing else to this rom except a few apps from the google play store. I wanted to try again but couldn't find where the OTA is stored. It wasn't in the /cache/fota folder. So I downloaded a flashable zip from the net. But this update file failed to install also. I've seen a few others have success installing the update. I just don't know what's preventing me from updating. I welcome your suggestions. Thanks.
Click to expand...
Click to collapse
Hi,
You can try performing a full unroot in the SuperSU app if it still doesn't work... I had to adb sideload mine to work, don't know how it works with toolkit, but you have to first set your tablet to receive it. As you are on TWRP you simply go to advanced and select adb sideload, then try using the tool, or following the instructions on it to do so .
You cannot install a OTA zip like a Custom ROM zip, they are a little bit different hehe.
Hope this helps,
~Lord
PS.: This will work for N5 too.
I somehow got the idea that rooted Nexus devices with a custom recovery could handle OTA's without trashing the recovery. I guess I expected that I would lose root. I think I'm just going to wait for someone to put together a "CleanROM" based on 4.4.2 or newer. I've been waiting for a rom like this since I bought my Nex10 anyway. I don't think I'll suffer too much running on 4.4 until then.
Thanks to those who contributed, I'll remember your suggestions. Especially if I end up waiting a long time for a 4.4.2 based Cleanrom.
Update: Thanks to Wug's toolkit. I'm now running 4.4.2..
I should ask for a sticky for this but these instruction will work EVERY TIME if you are running either custom recovery or Root.
You will need the latest adb/fastboot from google, you can either install the SDK or download any of the many smaller adb/fastboot and libs for your os
You will need STOCK 4.4/4.3/4.2 recovery depending on what version of android you are currently on. Download the factory image from here. Open the zip within the package and pull out recovery.img and rename it stockrecovery.img
Copy your custom recovery to the adb folder name it twrp.zip or short name for whatever you are using I am using twrp.
You will need the correct OTA you are seeking to apply - rename it to something short simple and obvious - for this example I will use otaupdate.zip
If you wish to root get the latest patch (I believe its up to 1.75 now) and copy it to the adb/fastboot folder.
BACKUP YOUR DEVICE FIRST AND COPY IT TO YOUR PC
If you are already Rooted:
If you are using SuperSU - go to the application options and completely unroot and reboot if needed
BACKUP YOUR DEVICE FIRST AND COPY IT TO YOUR PC
If not rooted start here:
I am assuming most of you are Windows users. Open your file explorer and open the ADB folder.
On the left hand folder where ADB is located press shift and right click the ADB folder and select "Open command window from here". This will open a command prompt window for you to run all your adb/fastboot commands from. This is the same folder where you copied your recoveries and updates to.
BACKUP YOUR DEVICE FIRST AND COPY IT TO YOUR PC
Copy your custom recovery and stock recovery to your adb folder
Copy and rename the OTA to the adb folder
Copy your root.zip patch to the /sdcard downloads folder (if you wish root)
>adb reboot bootloader
>fastboot flash recovery stockrecovery.img
>fastboot reboot-bootloader
Go into recovery and wait till dead droid appears
Press power and Volume Up at same time to go into the stock recovery menu
Using the volume buttons move and down the blue list of options and select: Apply update from ADB
You will now have orange text at the bottom of the screen - follow the instructions to side load by typing >adb sideload otaupdate.zip in your command prompt window
Wait and watch the progress, at this point you should see the ota processing steps of which there a few and will vary depending on the package. When its complete there will be a "install complete" or similar message
Reboot and let the update complete the system optimizations and go in validate your device is working and the version is what you wanted
>adb reboot bootloader
>fastboot flash twrp.zip
>fastboot reboot-recovery
Using your newly installed custom recovery you can now apply zips/root etc
Reboot as needed and update root if using older .zip to current binaries and enjoy your updated device.
And yes you only need to backup once prior to starting but many people skip that step -DON'T BE ONE OF THOSE PEOPLE.
Hopefully I've not missed a bit.
You can also use these same instructions if you're stuck in boot loop or applied a patch without first replacing stock or unrooting - just boot to bootloader using fastboot and replace recovery and apply the patches. This will usually work just fine and prevent much heart ache on your part.

[HOW TO] Easy root a stock Android 4.4.2 - 4.4.4

Ok, assuming your bootloader is already unlocked, the easiest way to root your device if you want to keep the stock firmware (including recovery partition) is to flash a special modified boot.img called "Superboot r2" that installs su binaries and SuperSU on your device. It's nothing new, this workaround was originally developed by PaulOBrien, founder of MoDaCo, several months ago. People started to complain since 4.4.2 release saying this method doesn't work anymore... false! They just don't know the trick! I successfully rooted even the 4.4.4:good:
You just need to:
1) have your stock or official firmware flashed
2) clear cache partition through recovery before to flash
3) flash boot.superboot.img using the standard fastboot, not the mfastboot
4) your phone will crash with a disappearing android logo, just press the power button for few second to reboot it
5) if you don't find SuperSu in your drawer just try again
This method doesn't compromises your phone from receive OTA updates, fully tested.
I already re-packed it for you, just run the batch file.
DOWNLOAD
All credits to PaulOBrien.
Clarification
So all one needs to do is run the batch file if the bootloader is already unlocked?
chaserblack said:
So all one needs to do is run the batch file if the bootloader is already unlocked?
Click to expand...
Click to collapse
Yeah, clear cache and run the batch while you're in fasboot mode.:good:
Worked.
1st try, thanks man.

Rooting Kindle Fire HDX 7 32 GB 3rd Gen Fire OS 13.3.2.1 Wrapup

Rooting Kindle Fire HDX 7 32gb 3rd Gen Fire OS 13.3.2.1
Airplane Mode ON WIFI Off
Kindle Fire ADB Composite Drivers must be installed to working PC
In KFHDX Settings
Set Enable ADB - ON
Set Apps from unknown sources - ON
Faznx's KF-HDX Toolkit v0.95
https://www.androidfilehost.com/?fid=95832962473395302
KFHDX ToolKit v0.95.zip
MD5: 3C1D7DB855E54A39BF2FD59BE6ABA9DC
SHA-256: 614A0D077BEC8B85F6D6B377D2D18EB719AB9ED15B08B41CD5 8968BEED653C0C
Rooted KFHDX using Towelroot in above toolkit. - No Issues
Then applied:
1> SuperSU v2.14 installer in Faznx's KF-HDX Toolkit v0.95 - No Issues
2> Over the air update blocker and re-enabler for all current rootable versions in Faznx's KF-HDX Toolkit v0.95 - No Issues
Airplane Mode ON WIFI Off
Use adb to install ES File Explorer
http://www.howtogeek.com/125769/how-to-install-and-use-abd-the-android-debug-bridge-utility/
ADB install (installs application) -- adb install c:\com.estrongs.android.pop.apk - No Issues
Checked in ES File Manager to make sure I had root.
Next rename the /system/etc/security/otacerts.zip file - one issue - resolved
Even though I ran the disable OTA updates, I am concerned that some post I have read said their system was update even though they renamed.
I think now it's possible they get around us by running an MD5 hash on files in that folder and compare to the hash they store for that version.
The better idea may be to move that file out of that folder. I did just that.
Here are the directions to rename:
see the contents of that folder with adb shell ls -Ral /system/etc/security
Example:
C:\Users\davcam\AppData\Local\Android\sdk\platform-tools>adb shell ls -Ral /system/etc/security
/system/etc/security:
drwxr-xr-x root root 2014-02-07 04:23 cacerts
-rw-r--r-- root root 1337 2014-02-07 04:23 otacerts.zip
Before you can rename this file you must set the \ and \system file systems to r/w - then you can rename or mv the file.
When completed, change \ and \system file systems back to ro
Next : Safestrap
https://goo.im/devs/Hashcode/thor/safestrap/
I tried Safestrap-Thor-3.72.apk and it did not seem to work. I unistalled recovery and Safestrap-Thor-3.72.apk.
I was able to successfully install Safestrap-Thor-3.75-os3.2.4-B02.apk, install recovery, boot into recovery, backup up stock, create a new rom slot,
change to that Rom slot and restore stock backup into that slot.
Now on startup i get the Safestrap screen.
One thing I noticed was that the stock values for the rom slots are a little small, so keep that in mind.
Thanks to everyone on XDA Forums, especial to EncryptedCurse for the terse, meaningful tips., Faznx's KF-HDX Toolkit v0.95, Geohot's Towelroot,
hashcode0f's Safestrap, OTA disable, and Supersu.
Current Status:
Using a copy of stock on a somewhat larger partition, no otacerts.zip file
Next steps:
0> Thank and donate to the developers I mentioned above.
1> Airplane mode OFF, wifi ON , register with Amz
1.1> Get GAPPS installed on this copy of stock I'm booting into
2>to see if possible to load a CM11 image into one or my bran new slots.
Question: If Amazon were able to push an update to me, would I just be able to recover to my stock image and move on?
Thanks for the help and education!
reggie9 said:
Next steps:
0> Thank and donate to the developers I mentioned above.
1> Airplane mode OFF, wifi ON , register with Amz
1.1> Get GAPPS installed on this copy of stock I'm booting into
2>to see if possible to load a CM11 image into one or my bran new slots.
Question: If Amazon were able to push an update to me, would I just be able to recover to my stock image and move on?
Thanks for the help and education!
Click to expand...
Click to collapse
Dont try to install CM11 with Safestrap!! It wont work, and you will brick your device! You have to install TWRP 2.8.4.0 and only then you can install CM11 safely.
If your device get FW 4.X.X, you lost root and ability to install custom roms through custom recovery (Safestrap, TWRP 2.8.4.0) - and only way to get the root again is rollback from 4.x.x to 3.2.7-8 (by amazon tech support), and then you can use only Safestrap, so no CM11 or Nexus 2.0.4 ROMs for FW 3.2.7-8!
Edit: Looks like jeryll already said it.
jeryll said:
Dont try to install CM11 with Safestrap!! It wont work, and you will brick your device! You have to install TWRP 2.8.4.0 and only then you can install CM11 safely.
If your device get FW 4.X.X, you lost root and ability to install custom roms through custom recovery (Safestrap, TWRP 2.8.4.0) - and only way to get the root again is rollback from 4.x.x to 3.2.7-8 (by amazon tech support), and then you can use only Safestrap, so no CM11 or Nexus 2.0.4 ROMs for FW 3.2.7-8!
Click to expand...
Click to collapse
Thanks! I appreciate the heads up. Any idea where I can locate TWRP 2.8.4.0 for this device?
Sorry - Found it here: http://forum.xda-developers.com/kindle-fire-hdx/development/recovery-twrp-2-8-1-0-thor-t2986004
Reggie9
jeryll said:
Dont try to install CM11 with Safestrap!! It wont work, and you will brick your device! You have to install TWRP 2.8.4.0 and only then you can install CM11 safely.
If your device get FW 4.X.X, you lost root and ability to install custom roms through custom recovery (Safestrap, TWRP 2.8.4.0) - and only way to get the root again is rollback from 4.x.x to 3.2.7-8 (by amazon tech support), and then you can use only Safestrap, so no CM11 or Nexus 2.0.4 ROMs for FW 3.2.7-8!
Click to expand...
Click to collapse
Everything has seemed pretty clear up to now, but I am trying to understand what I should do next? I have Safestrap 3.72 beta installed and I'm running off of a backup of stock running in ROM-Slot 1.
Do I need to wipe rom slot one, remove recovery and uninstall Safestrap? Then install TWRP? Can I take a backup of my current ROM Slot one and use it in TWRP. I am looking for a good install post or video for installing TWRP 2.8.4.0 on KFHDX. It appears that TWRP does not use the concept of ROM slots but actually wipes the main system (that has been backed up to the builtin recovery area?) Then installs an image on the main system? I understand basically what Safestrap is doing, but not TWRP.
reggie9 said:
Everything has seemed pretty clear up to now, but I am trying to understand what I should do next? I have Safestrap 3.72 beta installed and I'm running off of a backup of stock running in ROM-Slot 1.
Do I need to wipe rom slot one, remove recovery and uninstall Safestrap? Then install TWRP? Can I take a backup of my current ROM Slot one and use it in TWRP. I am looking for a good install post or video for installing TWRP 2.8.4.0 on KFHDX. It appears that TWRP does not use the concept of ROM slots but actually wipes the main system (that has been backed up to the builtin recovery area?) Then installs an image on the main system? I understand basically what Safestrap is doing, but not TWRP.
Click to expand...
Click to collapse
You are on compatible firmware so dont complicate things so much If you want to understand how Safestrap or TWRP itself work - google is your friend, you will certainly find plenty of information about how things works: here is little introduction about differencies between them, not all of course...
And here is little something from ggow about how to install twrp and remove safestrap, you can later find safestrap slot image files in data/media/safestrap - and after you have functional TWRP 2.8.4.0, you can delete safestrap folder safely and free some space taken by these image files
Normal way is how TWRP 2.8.4.0 works (IMHO) - only one big playground managed by mighty TWRP recovery always accessible by shortcut when you made mistake and need to repair something...
Safestrap uses multiple slots for (un)modified stock roms simply because is too dangerous to play with stock rom on systems with locked bootloader, so you can play with slot rom instead of stock where small mistake leads to different types of bricks - some repairable, some not
And yes you can make a backup of your current ROM and use it later with TWRP, but here comes catch, Safestrap only backups system and data partition, not boot (contains kernel), so I recommend after you install your preferred CM11 or Nexus 2.0.4, restore only DATA part of your backup
jeryll said:
You are on compatible firmware so dont complicate things so much If you want to understand how Safestrap or TWRP itself work - google is your friend, you will certainly find plenty of information about how things works: here is little introduction about differencies between them, not all of course...
And here is little something from ggow about how to install twrp and remove safestrap, you can later find safestrap slot image files in data/media/safestrap - and after you have functional TWRP 2.8.4.0, you can delete safestrap folder safely and free some space taken by these image files
Normal way is how TWRP 2.8.4.0 works (IMHO) - only one big playground managed by mighty TWRP recovery always accessible by shortcut when you made mistake and need to repair something...
Safestrap uses multiple slots for (un)modified stock roms simply because is too dangerous to play with stock rom on systems with locked bootloader, so you can play with slot rom instead of stock where small mistake leads to different types of bricks - some repairable, some not
And yes you can make a backup of your current ROM and use it later with TWRP, but here comes catch, Safestrap only backups system and data partition, not boot (contains kernel), so I recommend after you install your preferred CM11 or Nexus 2.0.4, restore only DATA part of your backup
Click to expand...
Click to collapse
jeryll - Thanks for the the thoughtful response - will study this. - reggie9

[SOLVED] On Reboot, Kernel keeps resetting to MM

===Solved! Just overwrite your old SafeStrap by installing the SafeStrap.apk included at this thread:
http://forum.xda-developers.com/verizon-galaxy-s5/general/root-method-og5-ok3-t3290370
and be sure to have BusyBox installed prior to overwriting the SafeStrap install, otherwise it will not actually work.
Unsure if related, but if problem persists connect your microSD directly to a PC and look for ".MM_KERNEL_SS-FF_Flashable" folder
===
So I had followed jkruse's locked bootloader guide to use a stock MM ROM with SS support. After using it for a while, I decided to go back to OptimalROM. Unfortunately, every reboot results in stock recovery. I found I can just flash a PB1 kernel through Odin and that fixes it for now- however on the next reboot BAM- back to the same problem.
I assuming this is caused by the current SafeStrap I have installed- which was linked in the MM for locked bootloaders thread.
How can I prevent the kernel from being overwritten every reboot?
On a side note, where can I find the latest stagefreight fix zip for 5.0? I have tried a few but they only seem to work on the 5.1.1 ported ROMs. Tried Stagefreight_Fix_02_Nov.zip and gets stuck at boot. Same situation with Stagefright_Fix_v2_i9505_i337M.zip.
Surely there is a ported fix somewhere for 5.0 roms?
Can you not flash PB1 thru Odin and just root and install OptimalROM via FF that way
Nandr0idC0nsumer said:
Can you not flash PB1 thru Odin and just root and install OptimalROM via FF that way
Click to expand...
Click to collapse
I can always resort to that, but I am trying to figure out what it is that keeps reflashing the MM kernel on reboot. I assume its the MM_Safestrap.apk, but only @jrkruse knows for sure
It appears I was right on the money! After grabbing the SafeStrap.apk from the OK3-V5 root package and installing that version of SS over the MM specific one, I no longer have the issue! I also opened my microSD directly on my computer (not connected through phone USB) and deleted the .MM_KERNEL_SS-FF_Flashable (note the .) folder.
Hope this helps anyone else who downgrades.
Still looking for a solution to the Stagefright Vulns in 5.0 ROMs

Categories

Resources