Related
I have an SCH-i545 MDK build.
I am trying to upgrade from 4.2.2 to 4.3 and get root working.
On a 4.2.2 ROM, the motochopper exploit works perfectly. However, if I load a 4.3 ROM and follow the same method, when I flash the kernel to the pre-release kernel, the phone hangs and never boots. I've tried it several times with the same result, clearing cache before the process starts also seems to have no effect.
So what's the deal? Why is this happening? I know I have the right build. I went back to stock 4.2 and re-rooted using these files to make sure it would work at all. It worked perfectly. WTF? I flashed back to the stock kernel before installing the 4.3 ROM and trying again. Same deal, no booting after flashing the pre-release kernel.
Is there an updated root exploit for 4.3 that I missed?
I am following this guide: http://forum.xda-developers.com/showthread.php?t=2290798
This is my desired 4.3 ROM: http://www.slimroms.net/index.php/downloads/dlsearch/viewcategory/582-jfltevzw
forkbomb said:
I have an SCH-i545 MDK build.
I am trying to upgrade from 4.2.2 to 4.3 and get root working.
On a 4.2.2 ROM, the motochopper exploit works perfectly. However, if I load a 4.3 ROM and follow the same method, when I flash the kernel to the pre-release kernel, the phone hangs and never boots. I've tried it several times with the same result, clearing cache before the process starts also seems to have no effect.
So what's the deal? Why is this happening? I know I have the right build. I went back to stock 4.2 and re-rooted using these files to make sure it would work at all. It worked perfectly. WTF? I flashed back to the stock kernel before installing the 4.3 ROM and trying again. Same deal, no booting after flashing the pre-release kernel.
Is there an updated root exploit for 4.3 that I missed?
I am following this guide: http://forum.xda-developers.com/showthread.php?t=2290798
This is my desired 4.3 ROM: http://www.slimroms.net/index.php/downloads/dlsearch/viewcategory/582-jfltevzw
Click to expand...
Click to collapse
I've never seen a custom ROM that didn't come rooted. I suspect that your 4.3 ROM doesn't need to be exploited to be rooted.
k1mu said:
I've never seen a custom ROM that didn't come rooted. I suspect that your 4.3 ROM doesn't need to be exploited to be rooted.
Click to expand...
Click to collapse
Ok with the 4.3 ROM installed, it has SuperSU installed but it says my device is not rooted. SuperSU says it needs to update it's binaries.
I click install normal, it says failed. I click CWM, it never reboots. Rebooting into recovery doesn't continue the process.
Is this the ROM's fault? Should I just pick another 4.3 ROM?
forkbomb said:
Ok with the 4.3 ROM installed, it has SuperSU installed but it says my device is not rooted. SuperSU says it needs to update it's binaries.
I click install normal, it says failed. I click CWM, it never reboots. Rebooting into recovery doesn't continue the process.
Is this the ROM's fault? Should I just pick another 4.3 ROM?
Click to expand...
Click to collapse
I'd ask the developer of that ROM what's up.
forkbomb said:
Ok with the 4.3 ROM installed, it has SuperSU installed but it says my device is not rooted. SuperSU says it needs to update it's binaries.
I click install normal, it says failed. I click CWM, it never reboots. Rebooting into recovery doesn't continue the process.
Is this the ROM's fault? Should I just pick another 4.3 ROM?
Click to expand...
Click to collapse
You must go to setting, about phone, tap the build number repeatedly until developer options are granted.
Now go to settings, developer options, look for Root. Select it and choose "ADB & Apps"
dynospectrum said:
You must go to setting, about phone, tap the build number repeatedly until developer options are granted.
Now go to settings, developer options, look for Root. Select it and choose "ADB & Apps"
Click to expand...
Click to collapse
Oh wow, that was simple. Thank you.
There are threads here and there but I couldn't find anything who has gotten encryption working on a custom ROM, except on a thread that someone did it with Jedi X Rom. Anyways, I have tried the following ROMs + TWRP to encrypt with no luck:
jfltevzw_JellyBeans_B7
S4_Echoev29.1_S5PORT_VZW_090814
S4_Echoev29_VZW_100814
Danvdh-CM11-09-18-2014-M9-stable
Danvdh-GPE-5-12242014
EclipseTW-S4-v4.0.2-KitKatNC5
HyperdriveRLS20KKS4Final
All of the above ROMS, after I enable encryption, green Android comes up, reboot and then back to Android like nothing happened. I tried disabling superuser, safe mode... Closest to success was JellyBeans where it encrypted successfully but then asked password for Storage which the password did not work.
Anyone has gotten encryption working on their custom ROM? If you did, what recovery/ROM/build combination? Anything special you had to do to get it working?
I disabled SU, ran the encryption then re-rooted. I was running stock NC5 so not really "custom," but it worked.
ammjr71 said:
I disabled SU, ran the encryption then re-rooted. I was running stock NC5 so not really "custom," but it worked.
Click to expand...
Click to collapse
Oh so many questions...
Which stock NC5 you were running - Can you point me to the file?
How did you install to your S4? Odin/recovery?
Which recovery do you have TWRP/CWM?
Why didn't you just enable SU after encryption instead of re-rooting?
Lastly, was using a PIN enabled available for encryption for this ROM or did you have to use a password instead?
Sorry for all the questions, but I see light at the end of the tunnel. I was going to go back to stock so that I can enable encryption. (My company policy requires 'Google Apps Device Policy')
Thanks!
ammjr71 - which stock NC5 ROM did you use?
Anyone else out there to successfully encrypt a rooted ROM?
OK, I think I see the light at the end of the tunnel for encryption on a custom ROM.
This method seems to work for most of the custom ROMs:
In SuperSU, uncheck 'enable superuser' and then in application manager, Turn off SuperSU. Make sure SuperSU is in turned off page. After that, reboot and encrypt should work... Also, I noticed for encryption to work, security software version under about phone should not be blank. It should be something like MDF v1.0 Release 3.. Lastly, try a password with 6 characters and one number; not a simple 4 digit PIN.
[Solved] Manual install CM11 & Original Thread: How to install CM 11.1 on Fire HDX 7?
Hello,
as I just managed to install CM 11 on my Fire HDX 7 (3rd Gen) (thanks a lot to @Cl4ncy, @Davey126 and @EncryptedCurse) I want to share the information I got during the process.
Note: This manual might be outdated if you read it. So check if there is a newer manual You could break your device if you dont do everything correctly. I am not responsible for breaking your device! If you have a question just ask! It could be that i forgot something.
When I started my Fire HDX 7" had Fire OS 4.5.5.
Note: CM 12 is not available yet for Safestrap v4. If you want CM 12 you need an unlocked bootloader. You can't do it if your version is above Fire OS 3.2.3.2. And you are not able to downgrade below 3.2.8 due to rollback protection by Amazon.
Some preperations:
- connect your Fire HDX to your PC (if your PC doesnt recognize your Fire HDX then install the USB drivers. If that doesn't work deinstall the actual Fire HDX driver and try it again.)
- copy every folder from the Fire HDX storage to your PC (backup music, ....)
- install (Holo Backup and click on every Backup Button (in my version there were 5 buttons))
- install minimal adb + fastboot
Download these files and save them on your PC:
- ES Explorer
- KingRoot
- Safestrap v4
- a Safestrap v4 compatible ROM (CM11 or Nexus v4)
- SuperSU if you want root - Download the .zip file from here: https://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip //Check if there is a newer Version
- GApps if you want the Google Apps (the right things should be already selected. If not select: ARM, 4.4, nano) -> the name should be sth like: "arm 4.4 nano 30 September 2015"
Thanks to @Davey126 and @Cl4ncy:
- Turn Wifi Off and flightmode on (you might need to enable Wifi, when you root your device with KingRoot)
- rollback to FireOS 3.2.8
// you do that by copying the file into the 'Internal storage folder' of your Fire HDX (not in a subfolder, just copy it where the DCIM, Document, Download, kindle, ... folder are.). Now wait a few minutes and go to Settings -> Device -> System Updates -> Tap Update
- upgrade to FireOS 4.5.2
// do it as before
- install ES Explorer and KingRoot with minimal ADB + Fastboot
- make sure that only the Fire HDX 7" is connected
- run this Code to see the connected devices
Code:
adb devices
- install the ES Explorer and KingRoot by using minimal ADB + Fastboot
- replace "C:\users\p-4\es.apk" with your own path and do the same for KingRoot
Code:
adb install C:\users\p-4\es.apk
- root with KingRoot or another method (i didn't find another one) //if it doesn't work directly just try it again (I tried it 10 times). If it still doesn't work just try another Wlan (that nothing gets blocked) or wait a week.
- block OTA (over-the-air updates) - only step#1 //you don't have to install the GApps because you will flash them with the ROM
- install Safestrap v4
- Copy the installation files (ROM, SuperSU, Gapps) to your Fire HDX into the /sdcard folder. (There the files won't get deleted if you wipe). If there folder isn't available then create one. But normally there should be one. Make sure you have your Fire HDX rooted. Only then you can see the folder with ES Explorer. In my case the "/sdcard" folder was the normal one, where i stored my Music, Documents, ... so had didn't have to do sth.
- Reboot
- Make a backup of the 'Stock-Slot'
- Copy the backup to your PC
- flash a Safestrap v4 compatible ROM to the ROM-Slot-1 , 2, 3 or 4 (currently CM11 or Nexus v4)
Safestrap v4 Tutorials:
(https://www.youtube.com/watch?v=K6fPF5UZsWw) General Safestrap usage
(https://www.youtube.com/watch?v=xR0WXCITq2Q) Specifically how to install a custom ROM
Notes: If you use a secondary slot the biggest possible Data Size is 16GB and your battery won't last long. You have to charge the Fire HDX very often.. If you use the Stock Rom Slot you will have the whole storage of your device.
Congratulations you successfully installed CM11 if you did everything right.
But as I mentioned before the performance is not very good, because the ROM is installed on a secondary slot.
--------------------------------------------------------------------------------------------------------------------------------------
To get the best performance and a very good battery life you have to install the ROM on the 'stock-slot'.
Thanks to @Cl4ncy and @Davey126 :
For that just:
- Reboot and go to the Safestrap Menu
- check if the installation files (ROM, Gapps, SuperSU) are in the "/sdcard" folder press "..." in the installtion menu to go up the path. There should be the "/sdcard" folder.
- Delete the secondary ROM-Slots
- Go into the Wipe Menu and Swipe to perform a factory reset (only a simple one - no advanced wipe)
- Go to install and add the ROM File
- add Gapps
- add SuperSU if you want root
- perform the flash
- if it was successfull Reboot otherwise DON'T Reboot. Just wipe again and flash the files again.
Note: If something went wrong with the stock-ROM don't reboot directly. Just install a ROM on a secondary slot and reboot then.
// The Original Post:
Hello,
since it is possible to download prime videos on any android device i would like to install Cyanogenmod 12.1 on my fire hdx 7.
I found this Cm 12.1 Port.
Is there a step by step manual how to install such a rom, because i never did that before and i have heard that if you do something wrong your device is broken.
Because I neither know how to get an unlock bootloader or what a TWRP is. Furthermore i also dont know how to flash the ROM.
In some forum posts i read, that it is possible to go from Cyanogenmod back to FireOS (unbrick). For now i dont want to go back from Cyanogenmod to FireOS, but i think it would be good to have such a possibility.
Do I have to take precautions for that?
And how do I make backups?
Info:
Kindle Fire HDX 7" (3. Generation): Fire OS 4.5.5
Thanks a lot
p-4
You can NOT use CM12 - all current builds require an unlocked bootloader. You can NOT unlock the bootloader of Fire OS versions above 3.2.3.2, thus you can NOT use CM12. You can also NOT use TWRP recovery.
Reason: Rollback protection by Amazon, preventing downgrading to Fire OS versions below 3.2.8
Good you asked first.
Your options would be to downgrade to 3.2.8, then update to 4.5.2, install Safestrap v4 and use either Nexus v4 for Safestrap v4 or CM11 for Safestrap v4.
@Davey126 gave a good overview here, so read all the info and ask before you brick your HDX! If you don't follow the procedure 100% correctly, you will brick your HDX! @tropicallazerbeams also linked to YouTube videos about Safestrap usage and installation of custom ROMs. Regarding the ROMs, read the installation requirements carefully!
Thanks for this answer
Cl4ncy said:
You can NOT use CM12 - all current builds require an unlocked bootloader. You can NOT unlock the bootloader of Fire OS versions above 3.2.3.2, thus you can NOT use CM12.
Good you asked first.
Your options would be to downgrade to 3.2.8, then update to 4.5.2, install Safestrap v4 and use either Nexus v4 for Safestrap v4 or CM11 for Safestrap v4.
@Davey126 gave a good overview here, so read all the info and ask before you brick your HDX! If you don't follow the procedure 100% correctly, you will brick your HDX! @tropicallazerbeams also linked to YouTube videos about Safestrap usage and installation of custom ROMs. Regarding the ROMs, read the installation requirements carefully!
Click to expand...
Click to collapse
Thanks for this answer,
what is the difference between Nexus v4 and CM11. Which one should i install?
CM 11 for Safestrap v4? Because i want to get CM12?
Can I use TWRP with 4.5.2?
Thanks
p-4
p-4 said:
Thanks for this answer,
what is the difference between Nexus v4 and CM11. Which one should i install?
CM 11 for Safestrap v4? Because i want to get CM12?
Can I use TWRP with 4.5.2?
Thanks
p-4
Click to expand...
Click to collapse
You can NOT use TWRP (see above), TWRP is available for Fire OS below 3.2.4 only. You must use Safestrap v4 (i.e. NOT Safestrap v3.72/3.75!).
I can't give you any recommendation, but you can try Nexus and CM11 after you installed Safestrap v4. You can even (depending on the size of your sdcard/storage) set up secondary slots and use dual boot with Safestrap installed.
But you should focus on downgrading to 3.2.8, then updating to 4.5.2, rooting, disabling OTA, and installing Safestrap first - that will be difficult and risky enough for the time being.
And note that CM12 is not an option for you. This could change in the future, but I wouldn't count on it.
And one other thing:
If you've Safestrap installed, NEVER use the factory reset in Amazon's stock recovery! You will most likely brick your HDX.
p-4 said:
Thanks for this answer,
what is the difference between Nexus v4 and CM11. Which one should i install?
CM 11 for Safestrap v4? Because i want to get CM12?
Can I use TWRP with 4.5.2?
Thanks
p-4
Click to expand...
Click to collapse
Nexus is basically an AOSP-based ROM (i.e. stock, just like Google intended).
CM11 should be self-explanatory.
I was able to successfully downgrade to 13.3.2.8.
Can I now downgrade to 3.2.3.2 (from here) to be able to get an unlocked bootloader?
Because CM 12.1 would be really nice
But for CM11 I also need an unlocked bootloader, dont I? (click).
Or is it possible, after I installed CM 11, to upgrade to CM12? (Has Cyanogenmod an Over the Air update possibility?)
p-4 said:
I was able to successfully downgrade to 13.3.2.8.
Can I now downgrade to 3.2.3.2 (from here) to be able to get an unlocked bootloader?
Because CM 12.1 would be really nice
But for CM11 I also need an unlocked bootloader, dont I? (click).
Click to expand...
Click to collapse
No, you can NOT downgrade below 3.2.8 due to rollback protection by Amazon (sorry I forgot to mention the reason, added it to my first reply above). Attempting to downgrade further will brick the HDX!
You can use the CM11 you linked to with either Safestrap v4 or an unlocked bootloader. You can NOT unlock (see above), thus you have to use it with Safestrap v4.
In order to install Safestrap v4 you must update to 4.5.2. Keep WLAN off/flight mode active! Kingroot probably requires a short moment of WLAN connection, be sure to enable flight mode right away, you don't want to get updated by Amazon to 4.5.5! After rooting disable OTA, then install Safestrap and make a backup of your Fire OS before you flash any custom ROM!
Cl4ncy said:
No, you can NOT downgrade below 3.2.8 due to rollback protection by Amazon (sorry I forgot to mention the reason, added it to my first reply above). Attempting to downgrade further will brick the HDX!
You can use the CM11 you linked to with either Safestrap v4 or an unlocked bootloader. You can NOT unlock (see above), thus you have to use it with Safestrap v4.
In order to install Safestrap v4 you must update to 4.5.2. Keep WLAN off/flight mode active! Kingroot probably requires a short moment of WLAN connection, be sure to enable flight mode right away, you don't want to get updated by Amazon to 4.5.5! After rooting disable OTA, then install Safestrap and make a backup of your Fire OS before you flash any custom ROM!
Click to expand...
Click to collapse
I successfully upgraded to 4.5.2.
Can I somehow install kingroot or es explorer without WLAN?
I got the apk on the device but I cant install it without es explorer, which I would download via the amazon app store. Can i enable Wifi for that time?
p-4 said:
I successfully upgraded to 4.5.2.
Can I somehow install kingroot or es explorer without WLAN?
I got the apk on the device but I cant install it without es explorer, which I would download via the amazon app store. Can i enable Wifi for that time?
Click to expand...
Click to collapse
Enable USB debugging, install Minimal ADB and fastboot, put the kingroot.apk into the adb directory, open a DOS box, change dir (cd) to your adb directory (e.g. enter cd\adb), then enter "adb install kingroot.apk" (without the quotes). This will install Kingroot on your HDX. Then do the same with ES Explorer.
The HDX must be connected to your PC by USB of course (should be obvious).
Thanks for that tip. Now i got these apps on my Fire HDX.
But Kingroot had some problems with the internet connection and now the Update Fire OS 4.5.4 is downloaded and could be installed. (Which i wont do).
Can I go ahead (with a better internet connection) to root the Fire HDX (it is not rooted yet). Or to I have to roll back to 3.2.8 and then update to 4.5.2 again?
p-4 said:
Thanks for that tip. Now i got these apps on my Fire HDX.
But Kingroot had some problems with the internet connection and now the Update Fire OS 4.5.4 is downloaded and could be installed. (Which i wont do).
Can I go ahead (with a better internet connection) to root the Fire HDX (it is not rooted yet). Or to I have to roll back to 3.2.8 and then update to 4.5.2 again?
Click to expand...
Click to collapse
As long as you're still on 4.5.2 you can try to root, just ensure 4.5.4 won't be installed. After successful root you can disable OTA, and delete the update file. Also ensure you have the latest Kingroot version - 4.50.902 I believe.
Now I tried to root the device with kingroot and a working internet connection but it failed :/
Is there an alternative method to root a kindle fire hdx.
I just tried the app rootGenius but i didnt understand what the app wants from me (the language is chinese or japanese).
Now i tried to root the Fire HDX 7 with 2 different apps. Do I have to reset the device? Or is uninstalling enough?
p-4 said:
Now I tried to root the device with kingroot and a working internet connection but it failed :/
Is there an alternative method to root a kindle fire hdx.
I just tried the app rootGenius but i didnt understand what the app wants from me (the language is chinese or japanese).
Now i tried to root the Fire HDX 7 with 2 different apps. Do I have to reset the device? Or is uninstalling enough?
Click to expand...
Click to collapse
I'm not sure why it failed. Kingroot should work with 4.5.2 - you sure the 4.5.4 update didn't start?
Probably wasn't a good idea to try another root app. I'm afraid you can not unroot in Kingroot, because the root attempt was unsuccessful?
Don't try a factory reset by using Amazon's stock recovery yet. May be just try Kingroot again? I think there was another report where it required a second attempt.
Cl4ncy said:
I'm not sure why it failed. Kingroot should work with 4.5.2 - you sure the 4.5.4 update didn't start?
Probably wasn't a good idea to try another root app. I'm afraid you can not unroot in Kingroot, because the root attempt was unsuccessful?
Don't try a factory reset by using Amazon's stock recovery yet. May be just try Kingroot again? I think there was another report where it required a second attempt.
Click to expand...
Click to collapse
At first I tried the kingroot 3 times and it always failed. Then i tried the other method which failed at 93%. Then I tried kingroot again, and it failed.
Is there another possibility to root it?
p-4 said:
At first I tried the kingroot 3 times and it always failed. Then i tried the other method which failed at 93%. Then I tried kingroot again, and it failed.
Is there another possibility to root it?
Click to expand...
Click to collapse
I'm afraid no.
Kingroot fails always between 53% and 55%. Once I got over 60%.
Should I upgrade to 4.5.5. And downgrade to 4.5.2 again? And try the kingroot again?
Could i try this one: http://www.gizmag.com/how-to-root-kindle-fire-hdx/30513/ ?
Or will I break my device then?
p-4 said:
Should I upgrade to 4.5.5. And downgrade to 4.5.2 again? And try the kingroot again?
Could i try this one: http://www.gizmag.com/how-to-root-kindle-fire-hdx/30513/ ?
Or will I break my device then?
Click to expand...
Click to collapse
That's an old root method not available for 4.5.x!
I'm not sure whether it's ok to update after a failed root attempt - again: you don't get any option to un-root in Kingroot?
You actually don't need to update 4.5.5 though, the 4.5.4 update would be enough, because you can downgrade to 3.2.8 from 4.5.4, too.
Keep flight mode active if you try it, so you won't get updated again. And keep the connection you must have during Kingroot as short as possible, so it won't download the entire 4.5.4 update again.
Cl4ncy said:
That's an old root method not available for 4.5.x!
I'm not sure whether it's ok to update after a failed root attempt - again: you don't get any option to un-root in Kingroot?
You actually don't need to update 4.5.5 though, the 4.5.4 update would be enough, because you can downgrade to 3.2.8 from 4.5.4, too.
Keep flight mode active if you try it, so you won't get updated again. And keep the connection you must have during Kingroot as short as possible, so it won't download the entire 4.5.4 update again.
Click to expand...
Click to collapse
Once I got the option to unroot but there i pressed FIX. At the moment I have WLAN the whole time active. 4.5.4 is already downloaded but not installed yet. I think i will upgrade to 4.5.4 now to downgrade and then do the whole stuff again.
p-4 said:
Once I got the option to unroot but there i pressed FIX. At the moment I have WLAN the whole time active. 4.5.4 is already downloaded but not installed yet. I think i will upgrade to 4.5.4 now to downgrade and then do the whole stuff again.
Click to expand...
Click to collapse
Ok, enable flightmode to avoid getting updated further to 4.5.5 then.
And good luck, I'm really not sure about this.
Does someone know if this root app works normally? (click)
After a few tries I can now locate to /system/priv-app/DeviceSoftwareOTA.apk but I am not able to rename this apk.
Can I also try these ways to root the Fire HDX 7" or will i brick my device then? (click)
//edit I just enabled wrong locations and it worked with kingroot
// edit now i got cm11 installed Can I also try other roms like CM12 and insert them in the Rom-slot 2? If it fails, my device isn't bricked, because i only have to restart and load rom-stock or rom slot 1, right?
The only big problem I noticed so far is the battery. After 8 hours in sleeping mode (only screen off) the battery status sank from 90% to 55%. How can I fix this problem?
I really did not know what to title this, here goes:
I have a Verizon SGS 4 (SCH-I545), running stock 4.4.2, no custom recovery (am currently running the stock recovery B.S.), bootloader I545VRUFNK4, build ID KOT49H.I545VRUFNK4, release date 4/26/13 & have been rooted with KingRoot V. 4.8.0135 and is unlocked (haven't really any idea what that means, upon boot-up it shows an unlocked lock icon and says CUSTOM, the dealer I bought it from, just a shop where they buy & sell new/used phones, said that it is unlocked for use on any carrier I want.)
Now I don't know how important, if at all, all of that is but I want to update to the most up-to-date OS, reroot & maybe start flashing new custom roms.
The problem is I don't have access to a computer without install restrictions, meaning I can download things but I can't install them without admin name & password trying it directly from the settings (Settings/More/Software update) it keeps saying service unavailable...
I'm lost, is there any way to update via stock recovery or install a custom recovery (TWRP/CWM) via stock recovery or a root app?
I would suggest you to upgrade your phone with a custom rom, elseway if you do it with any official update your bootloader will be upgraded and there are a lot of cons with that.
We cannot have TWRP, CWM or other recovery (thanks to the bootloader), so the best you can do it's getting SafeStrap and then flash any of these custom roms:
stang5litre Ediition 5.0
Albe95 S6 FULL PORT 4.7
Albe95 ASTRA v2 Note 5 PORT
(I listed those because you want to update your phone). You can find SafeStrap and the roms in Verizon Samsung Galaxy S 4 Android Development sub-forum
SafeStrap must not be compatible with my phone cause I tried to use it multiple times but it is not installing any recovery, I'm still stuck on stock recovery.
AlphaTekk said:
SafeStrap must not be compatible with my phone cause I tried to use it multiple times but it is not installing any recovery, I'm still stuck on stock recovery.
Click to expand...
Click to collapse
I'm in the same bootloader so you should be able to install it, you just need SuperSU as your superuser app and busybox
Busybox, ya, I have it and ran it but KingRoot installed it's own supersu thing and it won't let me switch, if there'sa way to switch to supersu from the Play store, how?
The recovery is being overwritten by a script in the system. The title of the file is..
Install.recovery.sh
Rename this file with adding ".bak" then reinstall safestrap
Sent from my SCH-I545 using Tapatalk
I searched Root Explorer but have no idea where this is found, maybe you could point me in the right direction.
Ok, my phone's settings say I545VRUFNK1 for baseband but the build number says KOT49H.I545VRUFNK4 and Samsung Smart Switch comes up with FNK4 (VZW)! It is a Verizon SCH-I545 but how can I update it without Smart Switch cause it keeps saying its up to date?
Can I use Odin and what recovery would I use with Odin?
I haven't touched this tablet in almost a year and cannot remember how i went about disabling OTA updates. Im on 4.5.2 rooted and safestrap installs fine but will not boot into recovery. So per another thread i was going to update to 4.5.5.1, root, and try to reinstall safestrap. I tried the hdx toolkit but when enabling it says "killed" a bunch of times and never really looks like it does anything but says its re-enabled. it is not enabled. Any ideas on how to re-enable OTA updates if that toolkit will not work. I was going to manually update but there is no internal storage folder when i plug in the tablet. So that isn't working either.
cpiddy said:
I haven't touched this tablet in almost a year and cannot remember how i went about disabling OTA updates. Im on 4.5.2 rooted and safestrap installs fine but will not boot into recovery. So per another thread i was going to update to 4.5.5.1, root, and try to reinstall safestrap. I tried the hdx toolkit but when enabling it says "killed" a bunch of times and never really looks like it does anything but says its re-enabled. it is not enabled. Any ideas on how to re-enable OTA updates if that toolkit will not work. I was going to manually update but there is no internal storage folder when i plug in the tablet. So that isn't working either.
Click to expand...
Click to collapse
There are two methods; will post details shortly (within 24 hours) along with thoughts on avoiding 4.5.5.2 which may not be rootable. Brain is a bit mushy after taxing day; want to make sure I get it right. Sorry for the wait.
cpiddy said:
I haven't touched this tablet in almost a year and cannot remember how i went about disabling OTA updates. Im on 4.5.2 rooted and safestrap installs fine but will not boot into recovery. So per another thread i was going to update to 4.5.5.1, root, and try to reinstall safestrap. I tried the hdx toolkit but when enabling it says "killed" a bunch of times and never really looks like it does anything but says its re-enabled. it is not enabled. Any ideas on how to re-enable OTA updates if that toolkit will not work. I was going to manually update but there is no internal storage folder when i plug in the tablet. So that isn't working either.
Click to expand...
Click to collapse
Davey126 said:
There are two methods; will post details shortly (within 24 hours) along with thoughts on avoiding 4.5.5.2 which may not be rootable. Brain is a bit mushy after taxing day; want to make sure I get it right. Sorry for the wait.
Click to expand...
Click to collapse
To restore OTA update functionality on FireOS 4.5.2 (one or both methods may have been used):
- navigate to /system/priv-app/ and search for DeviceSoftwareOTA.??? where '???' is likely 'bak' or 'apk_'; rename to 'DeviceSoftwareOTA.apk'
- navigate to /system/etc/security/ and search for otacert.zip.orig (or something similar); rename to 'otacert.zip'
Reboot device and check for updates. If FireOS 4.5.5.1 is pending allow it to download/install. If greater than 4.5.5.1 (eg: 4.5.5.2) immediately sever network connections (WiFi off; airplane mode engaged) and reboot your device to delete any partial downloads. Then grab FireOS 4.5.5.1 from this post. Note the image is not there at the moment (4.5.5 and 4.5.5.1 are different beasts). I'm hoping @ONYXis sees this post and updates the repository with the following links:
http://kindle-fire-updates.s3.amazo...Czd/update-kindle-13.4.5.5_user_455002120.bin (Thor)
http://kindle-fire-updates.s3.amazo...CgW/update-kindle-14.4.5.5_user_455002120.bin (Apollo)
Regardless of how FireOS 4.5.5.1 was obtained once installed you should root (Kingroot) and reblock OTA updates using one of the above methods before enabling network connectivity.
Davey126 said:
To restore OTA update functionality on FireOS 4.5.2 (one or both methods may have been used):
- navigate to /system/priv-app/ and search for DeviceSoftwareOTA.??? where '???' is likely 'bak' or 'apk_'; rename to 'DeviceSoftwareOTA.apk'
- navigate to /system/etc/security/ and search for otacert.zip.orig (or something similar); rename to 'otacert.zip'
Reboot device and check for updates. If FireOS 4.5.5.1 is pending allow it to download/install. If greater than 4.5.5.1 (eg: 4.5.5.2) immediately sever network connections (WiFi off; airplane mode engaged) and reboot your device to delete any partial downloads. Then grab FireOS 4.5.5.1 from this post. Note the image is not there at the moment (4.5.5 and 4.5.5.1 are different beasts). I'm hoping @ONYXis sees this post and updates the repository with the following links:
http://kindle-fire-updates.s3.amazo...Czd/update-kindle-13.4.5.5_user_455002120.bin (Thor)
http://kindle-fire-updates.s3.amazo...CgW/update-kindle-14.4.5.5_user_455002120.bin (Apollo)
Regardless of how FireOS 4.5.5.1 was obtained once installed you should root (Kingroot) and reblock OTA updates using one of the above methods before enabling network connectivity.
Click to expand...
Click to collapse
Thank you! That worked perfectly. Now i am having issues installing safestrap. Successfully rooted with king root, downloaded correct version for apollo, but when i go to install it prompts for root access then it gets to 50% mentions busy box, gets to 60% says installing, gets to 90% says cleaning up and then its finished. But nothing is installed and reboot to boot loader is greyed out. Have uninstalled and reinstalled multiple times, not sure what the deal is.
cpiddy said:
Thank you! That worked perfectly. Now i am having issues installing safestrap. Successfully rooted with king root, downloaded correct version for apollo, but when i go to install it prompts for root access then it gets to 50% mentions busy box, gets to 60% says installing, gets to 90% says cleaning up and then its finished. But nothing is installed and reboot to boot loader is greyed out. Have uninstalled and reinstalled multiple times, not sure what the deal is.
Click to expand...
Click to collapse
Quick checks:
- rebooted device after rooting
- messages you receive occur when installing Safestrap Recovery, not the app itself
Davey126 said:
Quick checks:
- rebooted device after rooting
- messages you receive occur when installing Safestrap Recovery, not the app itself
Click to expand...
Click to collapse
I missed the restart after rooting. Did that and was able to successfully install and boot into safe strap. Here's where I get a little confused. I have read through several threads with no real tutorial being available. So when safe strap boots, I want to select slot 1, this asks me to verify sizes, is there any preference here? Second, I'm assuming then I select the rom (cm11) then gapps, then choose to boot to slot 1?
cpiddy said:
I missed the restart after rooting. Did that and was able to successfully install and boot into safe strap. Here's where I get a little confused. I have read through several threads with no real tutorial being available. So when safe strap boots, I want to select slot 1, this asks me to verify sizes, is there any preference here? Second, I'm assuming then I select the rom (cm11) then gapps, then choose to boot to slot 1?
Click to expand...
Click to collapse
Do not create any additional slots. Unlike other Safestrap variants all activity takes place in the STOCK slot on HDX builds. In short you will be overlaying FireOS with CM11.
Secondary slots in Safestrap v4 are a disaster. A few of the liabilities:
- Nexus and FireOS will only run in the stock slot
- CM11 will only utilize 2 of the 4 CPU cores
- those two cores will run at 100% all the time
- device will not enter deep sleep when a secondary slot rom is active
- significant brick risk if backups are restored to a different slot
Davey126 said:
Do not create any additional slots. Unlike other Safestrap variants all activity takes place in the STOCK slot on HDX builds. In short you will be overlaying FireOS with CM11.
Secondary slots in Safestrap v4 are a disaster. A few of the liabilities:
- Nexus and FireOS will only run in the stock slot
- CM11 will only utilize 2 of the 4 CPU cores
- those two cores will run at 100% all the time
- device will not enter deep sleep when a secondary slot rom is active
- significant brick risk if backups are restored to a different slot
Click to expand...
Click to collapse
Awesome! everything successfully installed. Thank you again Davey for all of your help, it is greatly appreciated!