*** DISCLAIMER ***
I AM NOT RESPONSIBLE IF YOU MESS UP YOUR PHONE! OR IF YOU LOSE ANY DATA, ITS CALLED BACK IT UP BEFORE HAND!
Word to the wise if you don't know how to use RSDLite or Fastboot to restore your phone then leave this thread now please! You need to backup everything on your internal storage before you install this in case you need to restore back. If using the Safestrap version this rom needs to be flashed to the STOCK SLOT and the 4.4.2 KitKat Kernel and Baseband need to be flashed for it to work. If your Unlocked you either need to be on 4.4.2 prior to install or flash the 4.4.2 Baseband after the install. YOU'VE BEEN WARNED!
Okay this is a stock unmodified rooted rom of the Republic Wireless and C-Spire 4.4.2 KitKat OTA with full Safestrap functionality, except for restoring back to 4.2.2. To go back to 4.2.2 you will have to restore back using RSD or Fastboot. You will need to have the phone's drivers installed to get this working, so click the link below to download them and install them before you start. https://motorola-global-portal.custhelp.com/app/answers/prod_detail/a_id/94931/p/30,6720,8696
I don't own a XT1049 I threw this together for some users that asked for it, y'all will be my testers to confirm it's working.
Instructions to install this rom for Safestrap Users, read every step before you start...
1. You need to be rooted on 4.2.2 or 4.4 with Safestrap installed
2. You also need to have disabled write protection via MotoWpNoMo
3. Boot into Safestrap Recovery
4. Factory Reset the STOCK Slot in Safestrap DO NOT wipe the /system it can cause issues
5. Flash the Rom zip to the STOCK Slot (this can take up 10 minutes just walk away and let it finish)
6. Once the Rom has finished flashing, reboot to the Bootloader from within Safestrap
7. Plug your Moto X via usb cable into your computer the Bootloader screen should say usb connected now
8. Unzip the "RW & C-Spire Moto X Kernel and Radio Flasher.zip"
9. Open the extracted folder and find the FlashMyMotoX.bat and run it
10. For RW choose option 2 and for C-Spire option 4 within the FlashMyMotoX utility to flash the 4.4.2 KitKat Kernel
11. Once it finishes get back to the options and for RW choose option 3 and for C-Spire option 5 this will flash the 4.4.2 KitKat Baseband
12. Once it finishes successfully unplug your usb cable and reboot the phone
13. Enjoy 4.4.2 KitKat!
For Unlocked Users
1. Boot into TWRP 2.7 factory reset then install the rom.
2. If you were on 4.4.2 already then reboot and enjoy if you weren't on 4.4.2 then continue to step 3.
3. Once done installing reboot to the bootloader from within TWRP.
4. Once on the bootloader screen plug your usb cable into your Moto X the screen should say usb connected.
5. Extract and run my utility for RW choose option 3 and for C-Spire option 5 to flash the 4.4.2 Baseband.
6. Reboot and Enjoy 4.4.2!
Downloads: DO NOT repost links on other forums, link them to this thread!
Republic Wireless Versions
Safestrap Version
Unlocked Version
C-Spire Versions
Safestrap Version
Unlocked Version
Utility
RW & C-Spire Flashing Utility
Thanks to Google for Android and their Search engine, Hashcode for Safestrap, jcase for root, beaups and fuses for MotoWpNoMo, dhacker29 for TWRP 2.7, and the Chinese middle man for my bootloader unlock without them this wouldn't be possible!
great work
Stuck at "Formatting System...."
I followed your guide and at the point where I am attempting to flash the update, it is hung up. The last message the console printed was "formatting system...."
What should I do? It has been 5 minutes now... If the update is corrupt somehow, is there any way to push another version to the device from recovery?
* UPDATE * the flash finally completed. For those of you that are unsure, let it sit. It takes quite some time to flash (more than a couple minutes)!
I followed your guide, and did the install. I installed the Safestrap APK after everything was up and running. I am unable to reboot the device with R/W permissions. Write protection IS enabled after the reboot. Did I do something wrong?
slgooding said:
I followed your guide and at the point where I am attempting to flash the update, it is hung up. The last message the console printed was "formatting system...."
What should I do? It has been 5 minutes now... If the update is corrupt somehow, is there any way to push another version to the device from recovery?
* UPDATE * the flash finally completed. For those of you that are unsure, let it sit. It takes quite some time to flash (more than a couple minutes)!
Click to expand...
Click to collapse
slgooding said:
I followed your guide, and did the install. I installed the Safestrap APK after everything was up and running. I am unable to reboot the device with R/W permissions. Write protection IS enabled after the reboot. Did I do something wrong?
Click to expand...
Click to collapse
Yeah the install for Safestrap takes forever for some reason it doesn't for custom recoveries though. You need to run MotoWpNoMo to remove Write Protection, because you can't flash the 4.4.2 boot.img to the recovery partition, Moto signed them with different keys. It says that in the OP!
slgooding said:
I followed your guide, and did the install. I installed the Safestrap APK after everything was up and running. I am unable to reboot the device with R/W permissions. Write protection IS enabled after the reboot. Did I do something wrong?
Click to expand...
Click to collapse
did you run MotoWpNoMo when you were still on 4.2.2 ? thats the only way to retain write protection on 4.4.2
jbrukardt said:
did you run MotoWpNoMo when you were still on 4.2.2 ? thats the only way to retain write protection on 4.4.2
Click to expand...
Click to collapse
Well crap. I can't believe I missed that step... Is it safe for me to flash back to 4.2.2 (using safestrap recovery), remove WP and then upgrade again? I'm guessing I'm stuck...
slgooding said:
Well crap. I can't believe I missed that step... Is it safe for me to flash back to 4.2.2 (using safestrap recovery), remove WP and then upgrade again? I'm guessing I'm stuck...
Click to expand...
Click to collapse
I'm pretty sure you can run MotoWpNoMo while on 4.4.2, I might be wrong but I think someone did it in my Verizon 4.4.2 thread. I will check the comments later.
iKrYpToNiTe said:
I'm pretty sure you can run MotoWpNoMo while on 4.4.2, I might be wrong but I think someone did it in my Verizon 4.4.2 thread. I will check the comments later.
Click to expand...
Click to collapse
I just ran it MotoWpNoMo within 4.4.2. It WORKED. I verified with the following command: adb shell getprop ro.boot.write_protect
This means that for anyone that didn't remove write protection before updating (but had rooted prior to update) you can still disable WP.
slgooding said:
I just ran it MotoWpNoMo within 4.4.2. It WORKED. I verified with the following command: adb shell getprop ro.boot.write_protect
This means that for anyone that didn't remove write protection before updating (but had rooted prior to update) you can still disable WP.
Click to expand...
Click to collapse
Nah it still works because you're not on the 4.4.2 bootloader!
I was succesfully able to update to 4.4.2 with this update.zip. It is working great and I still have root! I did forget to wipe before updating, but so far I haven't noticed any problems. If I do, I just do a wipe and reflash. Thanks!
RobertsDF said:
I was succesfully able to update to 4.4.2 with this update.zip. It is working great and I still have root! I did forget to wipe before updating, but so far I haven't noticed any problems. If I do, I just do a wipe and reflash. Thanks!
Click to expand...
Click to collapse
Glad to hear, Enjoy!
Just updated my wife's moto x as well. Once again, it's working great.
Sent from my XT1049 using Tapatalk
settings are force closing when I try to access it.
I had Installed everything fine, had root, safestrap and wpnomo active prior to installing the 4.4 ROM.
Everything is working fine, except for my settings. I cannot turn off the option to install app store only apks. The settings app is force closing when I try to access it. From settings > personal > security. Then it just force closes. Any help would be appreciated.
I did do a factory reset from withen safestrap prior to installing, without wiping system. Should I wipe again now that its on 4.4? Maybe try wiping system.
It seems silly to have root If I can't use adaway, ES File explorer, titanium, Xposed and gravitybox. That sorta defeats the purpose of having root.
If you happen to be a Dev if this bug is either confirmed or absolved, I have a bug report I can share if needed.
-------------------------------------------------------
Sent via my Republic Wireless XT1049 Moto X with Tapatalk Pro.
-------------------------------------------------------
PM or e-mail me if you want to as well starting @ $5/month!
-------------------------------------------------------
Hello guys,
Just curious - Is anyone that successfully unlocked their bootloader (on Republic Wireless Moto X) with China code interested in selling their unlocked moto X?
I'm disappointed that I missed the bandwagon, so this may be my only opportunity to obtain an unlocked unit.
Thanks,
samwathegreat
EDIT: Offer withdrawn. Got BL unlocked. Thanks anyways.
EeyoreSyndrome said:
I had Installed everything fine, had root, safestrap and wpnomo active prior to installing the 4.4 ROM.
Everything is working fine, except for my settings. I cannot turn off the option to install app store only apks. The settings app is force closing when I try to access it. From settings > personal > security. Then it just force closes. Any help would be appreciated.
I did do a factory reset from withen safestrap prior to installing, without wiping system. Should I wipe again now that its on 4.4? Maybe try wiping system.
It seems silly to have root If I can't use adaway, ES File explorer, titanium, Xposed and gravitybox. That sorta defeats the purpose of having root.
Click to expand...
Click to collapse
I used Malcolmputer's exploit instructions and packages so that may be the difference but you are the first one to report this issue in either this thread or his.
Try booting into Safe Mode. That will tell you if it is an app conflict. Android Device Manager, and probably others too, can tell you what order your apps were installed in so that you can trace back to find the rogue app if Settings no longer does an f.c. in Safe Mode.
If it still crashes in Safe Mode then remember: The first rule of the Force Close club is -- don't let your cache talk to Android! The SafeStrap ROM was a bit of a learning curve for me (or I just worry too much) but if you go into it and Select WIPE there are 4 checkboxes. Start with just the cache. If you have already done that then ...
The next step is to wipe cache and Dalvik cache. Your phone will take much longer to boot up after that as it needs to rebuild the Dalvik cache. It will show you app by app until it finishes.
Malcolmputer has said that his idea was that if things went wrong that you could:
I did it. I now have an update.zip that you can flash from SafeStrap, keeping your recovery where it is at already.
This means that if you f- something up, you can just sbf back to stock 4.2.2, root, safestrap, my update.zip, and then be back at rooted 4.4.2, with WP off.
Click to expand...
Click to collapse
I sure hope it doesn't come to that.
I also haven't seen any reports of anyone trying it either, so ...
EeyoreSyndrome said:
I had Installed everything fine, had root, safestrap and wpnomo active prior to installing the 4.4 ROM.
Everything is working fine, except for my settings. I cannot turn off the option to install app store only apks. The settings app is force closing when I try to access it. From settings > personal > security. Then it just force closes. Any help would be appreciated.
I did do a factory reset from withen safestrap prior to installing, without wiping system. Should I wipe again now that its on 4.4? Maybe try wiping system.
It seems silly to have root If I can't use adaway, ES File explorer, titanium, Xposed and gravitybox. That sorta defeats the purpose of having root.
If you happen to be a Dev if this bug is either confirmed or absolved, I have a bug report I can share if needed.
-------------------------------------------------------
Sent via my Republic Wireless XT1049 Moto X with Tapatalk Pro.
-------------------------------------------------------
PM or e-mail me if you want to as well starting @ $5/month!
-------------------------------------------------------
Click to expand...
Click to collapse
Did you flash the new 4.4.2 baseband? There was issues with 4.4 if you didn't flash the baseband you would have FC's in the security settings.
iKrYpToNiTe said:
Did you flash the new 4.4.2 baseband? There was issues with 4.4 if you didn't flash the baseband you would have FC's in the security settings.
Click to expand...
Click to collapse
Maybe I was impatient in flashing the last two things
OBV if I didn't flash the kernal, it would simply not boot right?
On the kernal / baseband flasher, I get to "flashing modem" then done on my fastboot screen.
But the program seems to stick at "writing modem".
After unplugging the usb cord and then back in, it then finished erasing partition modems 1+2 and then flashed the fsg.
Okay, seems that I didn't properly flash the baseband on the first go, thanks for helping me troubleshoot! At least I can confirm that not having that updated baseband = force closing in settings app.
EeyoreSyndrome said:
Maybe I was impatient in flashing the last two things
OBV if I didn't flash the kernal, it would simply not boot right?
On the kernal / baseband flasher, I get to "flashing modem" then done on my fastboot screen.
But the program seems to stick at "writing modem".
After unplugging the usb cord and then back in, it then finished erasing partition modems 1+2 and then flashed the fsg.
Click to expand...
Click to collapse
I had this issue one time while trying to flash a kernel using my new usb 3.0 ports it ended up borking my phone pretty bad had to rsd several times to 4.2.2 to fix. I only use my usb 2.0 ports for flashing now. When do you get FC, is it as soon as you open the security settings or is it when you check unknown sources?
Hmm I used my USB 3.0 as well, didn't stop to think about it.
As for what your Bork was, what happened?
The FC happened as soon as I clicked on security, couldn't make it futhur then that.
As it is, things seem fine now, tho If you feel I should reflash em on USB 2.0, let me know.
Sent from my XT1049 using Tapatalk
Related
Hi all,
I'm having trouble getting Safestrap to install and work properly on my VerizonSG4. Phone is rooted with stock ROM and still on 4.3 with updates and notifications blocked.(SDM frozen with TB) Other mods include Exposed Framework using 2 modules,Greenify, Busybox, and a couple other root dependent apps that are not likely to be the issue. The problem I'm having is that upon getting Safestrap to install (which took multiple attempts) it will open to the screen where you can choose to install or uninstall recovery and when I hit install it does its thing but shows "State: Not Installed". However, I DO get a little pop up at the bottom of the screen that says" Installation Complete". Safe System says " Not Active" and " Reboot to Recovery" is grayed out so that I can't select it. Manual reboot into recovery brings up stock recovery so I'm not sure what's going on. I've tried everything I can think of to make it work including defrosting SDM, disabling my antivirus, verifying that USB debugging is enabled, etc. So I'm frustrated and could use some insight. I'm obviously missing something or doing something wrong so any help would be greatly appreciated. Oh, and the apk that I downloaded was Safestrap-JFLTEVZW-3.71which is supposed to be the correct on for Verizon MK2.
Thanks in advance
markctco said:
Hi all,
I'm having trouble getting Safestrap to install and work properly on my VerizonSG4. Phone is rooted with stock ROM and still on 4.3 with updates and notifications blocked.(SDM frozen with TB) Other mods include Exposed Framework using 2 modules,Greenify, Busybox, and a couple other root dependent apps that are not likely to be the issue. The problem I'm having is that upon getting Safestrap to install (which took multiple attempts) it will open to the screen where you can choose to install or uninstall recovery and when I hit install it does its thing but shows "State: Not Installed". However, I DO get a little pop up at the bottom of the screen that says" Installation Complete". Safe System says " Not Active" and " Reboot to Recovery" is grayed out so that I can't select it. Manual reboot into recovery brings up stock recovery so I'm not sure what's going on. I've tried everything I can think of to make it work including defrosting SDM, disabling my antivirus, verifying that USB debugging is enabled, etc. So I'm frustrated and could use some insight. I'm obviously missing something or doing something wrong so any help would be greatly appreciated. Oh, and the apk that I downloaded was Safestrap-JFLTEVZW-3.71which is supposed to be the correct on for Verizon MK2.
Thanks in advance
Click to expand...
Click to collapse
After rooting your phone with presumably saferoot did you open up SuperSu and update it's binary?
Sounds like a Superuser problem. Either open up SuperSu and update binary the " normal" way or run saferoot again if that doesn't work and then update binary. Then you should be OK to install SafeStrap.
Sent from my SCH-I545 using Tapatalk
Solved it!
Mistertac said:
After rooting your phone with presumably saferoot did you open up SuperSu and update it's binary?
Sounds like a Superuser problem. Either open up SuperSu and update binary the " normal" way or run saferoot again if that doesn't work and then update binary. Then you should be OK to install SafeStrap.
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
Thanks for the response, and I actually figured it out last night. But you were on the right track. After trying a download from a different source the apk installed, opened up and showed that I wasn't rooted! Surprised me because the app itself needed super user rights itself so I knew I was rooted. Turns out I needed to have the paid/full version of SuperSU! Bought it and I now have Safestrap. I know I should probably always purchase the full versions of such high tech apps but damn it would have been nice if someone...anyone would have said that. I'm guessing there are other versions of SuperUser that may work differently right out of the box? IDK but I'm up and running and grateful that I didn't brick my phone. Been down that road before and know that it doesn't take much to mess things up.
Anyway, thanks to all that read and maybe this will help someone else
markctco said:
Thanks for the response, and I actually figured it out last night. But you were on the right track. After trying a download from a different source the apk installed, opened up and showed that I wasn't rooted! Surprised me because the app itself needed super user rights itself so I knew I was rooted. Turns out I needed to have the paid/full version of SuperSU! Bought it and I now have Safestrap. I know I should probably always purchase the full versions of such high tech apps but damn it would have been nice if someone...anyone would have said that. I'm guessing there are other versions of SuperUser that may work differently right out of the box? IDK but I'm up and running and grateful that I didn't brick my phone. Been down that road before and know that it doesn't take much to mess things up.
Anyway, thanks to all that read and maybe this will help someone else
Click to expand...
Click to collapse
I'm not sure why you had to get a paid version of su. I had the SU zip and installed it as part of the upgrade/downgrade method
sent by baja kitkat S4
Definitely shouldn't need the paid version but hey good to support Chainfire anyways.
Sent from my SCH-I545 using Tapatalk
Mistertac said:
Definitely shouldn't need the paid version but hey good to support Chainfire anyways.
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
Yes, I found that odd also. When I switched to the other apk download it installed but said I did not have root, so I backed out one step and under the apk download that I selected was text in red that said "full version of SuperSu is required to complete this operation." So I paid for the full version, rebooted and everything worked fine from there. At that point the price was worth it, plus I typically use free versions of apps if I can get away with it so by supporting the Dev, as stated, perhaps I made a small deposit in the karma bank
Now I'm just trying to figure out if I need to do a factory reset before installing Hyperdrive. This is not my first ROM install but is under this format, so i want to take every precaution. Any suggestions? Leaning towards doing it except for concern about my phone downloading KitKat before I can reinstall TB and block it. Maybe I just need to be quick fingered. Again, open for suggestions.
Thanks in advance
markctco said:
Yes, I found that odd also. When I switched to the other apk download it installed but said I did not have root, so I backed out one step and under the apk download that I selected was text in red that said "full version of SuperSu is required to complete this operation." So I paid for the full version, rebooted and everything worked fine from there. At that point the price was worth it, plus I typically use free versions of apps if I can get away with it so by supporting the Dev, as stated, perhaps I made a small deposit in the karma bank
Now I'm just trying to figure out if I need to do a factory reset before installing Hyperdrive. This is not my first ROM install but is under this format, so i want to take every precaution. Any suggestions? Leaning towards doing it except for concern about my phone downloading KitKat before I can reinstall TB and block it. Maybe I just need to be quick fingered. Again, open for suggestions.
Thanks in advance
Click to expand...
Click to collapse
You should have plenty of time. I've flashed back to stock so many times and never had that update pop up before I could freeze SDM
I have an MDK phone so I'm not 100% up to speed on what you should do... @decaturbob has done it all and I'm sure would help send you down the right path
Sent from my SCH-I545 using Tapatalk
markctco said:
Yes, I found that odd also. When I switched to the other apk download it installed but said I did not have root, so I backed out one step and under the apk download that I selected was text in red that said "full version of SuperSu is required to complete this operation." So I paid for the full version, rebooted and everything worked fine from there. At that point the price was worth it, plus I typically use free versions of apps if I can get away with it so by supporting the Dev, as stated, perhaps I made a small deposit in the karma bank
Now I'm just trying to figure out if I need to do a factory reset before installing Hyperdrive. This is not my first ROM install but is under this format, so i want to take every precaution. Any suggestions? Leaning towards doing it except for concern about my phone downloading KitKat before I can reinstall TB and block it. Maybe I just need to be quick fingered. Again, open for suggestions.
Thanks in advance
Click to expand...
Click to collapse
the steps listed in surge's method are pretty easy and there is a video. Once you have rooted NC5 deox rom installed, then you can flash another rom right over the top as you would normally do. I installed Bajarom.
- roms go in stock slot
- be sure to flash SU update.zip (a step in safestrap right after you flash hyperdrive)
decaturbob said:
the steps listed in surge's method are pretty easy and there is a video. Once you have rooted NC5 deox rom installed, then you can flash another rom right over the top as you would normally do. I installed Bajarom.
- roms go in stock slot
- be sure to flash SU update.zip (a step in safestrap right after you flash hyperdrive)
Click to expand...
Click to collapse
Ok, thanks, but now I'm hung up again. But first of all let me say that there are numerous methods to be found online and I'm not familiar with surge's method, plus I'm not sure exactly how or when to flash the SU update .zip you mention. With that being said, after getting Safestrap to run I decided to flash a Hyperdrive ROM. Following several a combination of instructions and videos, I settled on Hyperdrive RLS12 as it claims to work with 4.3/MK2. But I've also seen that I need to flash the correct module, in this case JFLTEVZW-MK2-modules.zip file. There are conflicting instructions as to whether to flash both zips together or to flash the ROM and then the module just before rebooting. I've also read that I need to wipe cache etc. before rebooting.
Long story short, no matter what I try, I always get the same results...I see the Verizon Galaxy S4 logo followed by a black screen followed by a new boot audio? followed by over 30 minutes of black screen and a very hot battery. I have wiped rom slots between flashes, tried different ROM slots, just about everything I can think of besides the SU update. So perhaps someone can provide some detail on that step and some clarity on the other steps that vary from source to source.
I'm sure I'm doing something wrong but have gotten to a point where I'm just going to leave it alone for a while and use my stock ROM until I can get some help UGHHH
Thanks in advance
markctco said:
Ok, thanks, but now I'm hung up again. But first of all let me say that there are numerous methods to be found online and I'm not familiar with surge's method, plus I'm not sure exactly how or when to flash the SU update .zip you mention. With that being said, after getting Safestrap to run I decided to flash a Hyperdrive ROM. Following several a combination of instructions and videos, I settled on Hyperdrive RLS12 as it claims to work with 4.3/MK2. But I've also seen that I need to flash the correct module, in this case JFLTEVZW-MK2-modules.zip file. There are conflicting instructions as to whether to flash both zips together or to flash the ROM and then the module just before rebooting. I've also read that I need to wipe cache etc. before rebooting.
Long story short, no matter what I try, I always get the same results...I see the Verizon Galaxy S4 logo followed by a black screen followed by a new boot audio? followed by over 30 minutes of black screen and a very hot battery. I have wiped rom slots between flashes, tried different ROM slots, just about everything I can think of besides the SU update. So perhaps someone can provide some detail on that step and some clarity on the other steps that vary from source to source.
I'm sure I'm doing something wrong but have gotten to a point where I'm just going to leave it alone for a while and use my stock ROM until I can get some help UGHHH
Thanks in advance
Click to expand...
Click to collapse
have you looked at any youtube videos concerning S4 and safestrap?
decaturbob said:
have you looked at any youtube videos concerning S4 and safestrap?
Click to expand...
Click to collapse
Absolutely! But good news, phone is now booting! I tried flashing both zips together and it's working...at least I think it is. Displaying what I think is Google Play Edition boot image, 4 dots, yellow green red and blue zooming in and out. Not sure how long this is supposed to go on but I'm further along than previously. Any suggestions in case I end up in a boot loop or how long to wait to decide?
markctco said:
Absolutely! But good news, phone is now booting! I tried flashing both zips together and it's working...at least I think it is. Displaying what I think is Google Play Edition boot image, 4 dots, yellow green red and blue zooming in and out. Not sure how long this is supposed to go on but I'm further along than previously. Any suggestions in case I end up in a boot loop or how long to wait to decide?
Click to expand...
Click to collapse
Did you check the thread for compatibility of roms with ss?
sent by baja kitkat S4
decaturbob said:
Did you check the thread for compatibility of roms with ss?
sent by baja kitkat S4
Click to expand...
Click to collapse
Yup! As a matter of fact this is the video I watched that shows Hyperdrive RSL12 on the exact same phone as mine with 4.3 MK2 build.I think this is also the one that suggests flashing the module at the end. I've watched so many videos I can't remember which ones say what.
Am I missing something? I've made sure that I have USB debugging checked as well as unknown sources before flashing, I've tried flashing both zips at the same time and individually, even tried again without selecting any music players besides the Samsung one and not picking any audio mods when setting up the rom as per someones post on some blog somewhere. I've changed boot image, keyboards...I'm just about over this ROM. It can clearly be used with 4.3 but just not for me I quess? I've even considered backing up my stock rom and doing a factory reset on my phone and then starting from scratch. I'm just hoping I don't have to update to KitKat, which by the way is what Hyperdrive's website states you have to do, but this video contradicts that. UGHHH AGAIN!
http://www.youtube.com/watch?v=pA8cV3-r3oU
Wow, really? Nothing? No one? I thought this was where all the Android Root and Rom specialist hung out? Am I posting in the wrong thread or something? I cannot be the only one with this problem, can I?
markctco said:
Wow, really? Nothing? No one? I thought this was where all the Android Root and Rom specialist hung out? Am I posting in the wrong thread or something? I cannot be the only one with this problem, can I?
Click to expand...
Click to collapse
Alright since your trying Rls12 this should be easy since that's for Mk2.. Which your on.
Hop into SafeStrap and create a ROM slot. After its created activate that ROM slot. Then for good measure once your on that ROM slot wipe it.. Factory data reset. Then proceed to flash the Hyperdrive zip. Once that's finished don't leave SafeStrap until you'll flash those modules.
Then you can wipe cache and Dalvic again before rebooting.
If that's still not working for you I'm not sure where the problem lies. You're using SafeStrap v3.71 right?? Not version 3.72..
Sent from my SCH-I545 using Tapatalk
Mistertac said:
Alright since your trying Rls12 this should be easy since that's for Mk2.. Which your on.
Hop into SafeStrap and create a ROM slot. After its created activate that ROM slot. Then for good measure once your on that ROM slot wipe it.. Factory data reset. Then proceed to flash the Hyperdrive zip. Once that's finished don't leave SafeStrap until you'll flash those modules.
Then you can wipe cache and Dalvic again before rebooting.
If that's still not working for you I'm not sure where the problem lies. You're using SafeStrap v3.71 right?? Not version 3.72..
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
Thanks for responding! And yes I'm using that version of Safestrap and did everything you mentioned as per this video:
http://www.youtube.com/watch?v=l4F5UYDcQ5A
The only thing I can think of comes from something someone else mentioned about updating superuser binaries which made me realize that SuperSu, which is what I have doesn't appear to have that option. I checked the Play Store and there is the original Super User apk that I've used before to root other versions before all this bootloader crap started. I remember updating binaries in that version...I think. It may have been an option in CWM which I've also used. Could that be the issue? SuperSu acts just like Super User, asking for permissions and whatnot, but maybe Safestrap needs the other version. I think I'm going to uninstall or freeze (better idea) SuperSu and install the regular SuperUser. What gets me thought is that they are both developed by Chainfire, so I'm not sure what the difference would be. I do know that something is not right because I'm confident I'm doing everything as instructed.
HOT DAMN! I got it! It was a SuperSu issue, just took me a bit to figure out how to update binaries. It doesn't just have a button for that, had to uninstall and reinstall newest version.
Wow, what a trip that was! And I love the ROM.Gotta go and play now though
Thanks for everyones help and patience!
markctco said:
Hi all,
I'm having trouble getting Safestrap to install and work properly on my VerizonSG4. Phone is rooted with stock ROM and still on 4.3 with updates and notifications blocked.(SDM frozen with TB) Other mods include Exposed Framework using 2 modules,Greenify, Busybox, and a couple other root dependent apps that are not likely to be the issue. The problem I'm having is that upon getting Safestrap to install (which took multiple attempts) it will open to the screen where you can choose to install or uninstall recovery and when I hit install it does its thing but shows "State: Not Installed". However, I DO get a little pop up at the bottom of the screen that says" Installation Complete". Safe System says " Not Active" and " Reboot to Recovery" is grayed out so that I can't select it. Manual reboot into recovery brings up stock recovery so I'm not sure what's going on. I've tried everything I can think of to make it work including defrosting SDM, disabling my antivirus, verifying that USB debugging is enabled, etc. So I'm frustrated and could use some insight. I'm obviously missing something or doing something wrong so any help would be greatly appreciated. Oh, and the apk that I downloaded was Safestrap-JFLTEVZW-3.71which is supposed to be the correct on for Verizon MK2.
Thanks in advance
Click to expand...
Click to collapse
Edited
---------- Post added at 10:01 PM ---------- Previous post was at 09:57 PM ----------
Install Terminal Emulator. Type su and press enter. Then type setenforce 0 with a space after setenforce. Then press enter and reopen SafeStrap and all is well. The reboot recovery button will not be greyed out no more.
James- tech for a site dealing with Android day and night!
I have rooted my phone and uninstalled all the AT&T apps but when i reboot my phone they all come back, please help
tckdvr said:
I have rooted my phone and uninstalled all the AT&T apps but when i reboot my phone they all come back, please help
Click to expand...
Click to collapse
Have you installed JMZ's kernel. Without this any changes to /system won't stick after reboot.
MiniBlu
MiniBlu said:
Have you installed JMZ's kernel. Without this any changes to /system won't stick after reboot.
MiniBlu
Click to expand...
Click to collapse
No I didn't, but I will try that thank you.
that worked thank you
tckdvr said:
No I didn't, but I will try that thank you.
that worked thank you
Click to expand...
Click to collapse
I really wished I had seen THIS thread 2 days ago....
question
MiniBlu said:
Have you installed JMZ's kernel. Without this any changes to /system won't stick after reboot.
MiniBlu
Click to expand...
Click to collapse
How do you install JMZ's kernal to the htc desire 610
I use clear d's root tool the first day he released it and it took about 3 times to get it to work. Now I wonder if the kernel installed???
I have the jz rar file still unpacked on my sd card...only reason I asked is because the op's question rung a bell. I uninstalled every piece of bloatware I could and my free space is curiously low.
Is there a way to verify it got installed? If not can I unpack the rar file on my phone or do I have to use the root tool again?
KLit75 said:
I use clear d's root tool the first day he released it and it took about 3 times to get it to work. Now I wonder if the kernel installed???
I have the jz rar file still unpacked on my sd card...only reason I asked is because the op's question rung a bell. I uninstalled every piece of bloatware I could and my free space is curiously low.
Is there a way to verify it got installed? If not can I unpack the rar file on my phone or do I have to use the root tool again?
Click to expand...
Click to collapse
Look in settings, about, software information, more. Kernel version should say something like [email protected]*********#1 SMP PREEMPT. I can't tell you the exact name as I'm running my own modified version of his kernel for testing. If your are not running JMZ kernel it will be called something quite different.
MiniBlu
Thanks a lot for this. No. I do not have jmz's kernel!
I'm kind of confused. Supersu and twrp are present. I've used several apps that require root. So what exactly is going on?
The night I rooted (supposedly rooted) I'm pretty certain I asked if there was anyway to tell and I don't think I was informed about checking the kernel. That would've been easy. There's a chance it was updated I guess. AT&T was trying to push an update. I kept declining it but noticed it stopped asking. On other devices that usually means it was installed.
Any suggestions? Well I guess run the newer root tool then verify I have the kernel.
Thanks for the info, mini blu.
KLit75 said:
Thanks a lot for this. No. I do not have jmz's kernel!
I'm kind of confused. Supersu and twrp are present. I've used several apps that require root. So what exactly is going on?
The night I rooted (supposedly rooted) I'm pretty certain I asked if there was anyway to tell and I don't think I was informed about checking the kernel. That would've been easy. There's a chance it was updated I guess. AT&T was trying to push an update. I kept declining it but noticed it stopped asking. On other devices that usually means it was installed.
Any suggestions? Well I guess run the newer root tool then verify I have the kernel.
Thanks for the info, mini blu.
Click to expand...
Click to collapse
If yoy have root and can reboot to recovery thenyYou don't need to re-run the root tool. Just download JMZ kernel and flash it from TWRP.
MiniBlu
Thanks again. Can you clear up a couple of things for me?
1. If I have root then what exactly does the kernel do? I used to think it was essential.
2. When you say flash...all I need to do is boot into the boot loader screen, from there boot recovery, then when in twrp press install & select the kernel?
Do I need to connect to my pc?
Sorry. It's just for the past couple of months I thought I was all set but now there is clearly more to learn.
KLit75 said:
Thanks again. Can you clear up a couple of things for me?
1. If I have root then what exactly does the kernel do? I used to think it was essential.
2. When you say flash...all I need to do is boot into the boot loader screen, from there boot recovery, then when in twrp press install & select the kernel?
Do I need to connect to my pc?
Sorry. It's just for the past couple of months I thought I was all set but now there is clearly more to learn.
Click to expand...
Click to collapse
HI Klit75, in answer to above
1. Root(supersu) gives you access and control over which apps can run with root permissions, however the stock kernel has the /system partition write protected so any changes you or apps you install make to that partition are lost on reboot. JMZ kernel has this right protection removed which allows system customization's to remain after rebooting.
2. Everything you said here is right. No PC conecction required. Only thing is, it is sometimes tricky to get it to boot into boot loader so I have "android terminal emulator" installed from play store and run it then type
su
reboot recovery
this will reboot you straight to recovery. The above can also be done by connecting to the phone by adb and typing
adb reboot recovery
MiniBlu
ps before flashing the JMZ kernel I strongly recommend taking a TWRP backup (boot and system partitions will be enough) as JMZ kernel over-rights some modules on the system partition and it is always good to be able to go back if you have problems. Also after flashing the kernel select wipe dalvic and cache to avoid possible wifi issues.
Well I tried it. Got an error installing zip then I cleared dalvk cache and it went to "upgrading android upgrading so that seemed encouraging because that's what the root tool said was supposed to happen. But after reboot I still had the old kernel.
Thinking either the zip file I have doesn't work or I should have clicked the box to verify its signature. Gonna try again. Thanks a lot. Your info is extremely helpful.
UPDATE--Well I owe you a big thanks but not because it worked but for your advice to backup first.
As suspected, it didn't flash the first time because I clicked "verify signature" So this time it installed. I wiped dalvik and rebooted. I connected to WiFi and my first move was to come here & thank you. That's when my phone died.
It froze then turned off. I couldn't get it to turn on. I was able to get back to recovery with my pc and thankfully took your advice and restored from backup.
I'm obviously not an expert but I've jb ios devices, done softmods and I have rooted other android devices. This is the first time I've had trouble. 3 different root tools aren't getting the job done completely. Now my pc says "install unsuccessful"when it tries to get new HTC drivers. Is this due to an unlocked boot loader?
I was actually thinking this time it would work. Was there an update to the jmz kernel? Or did my phone possibly get an update the conflicts with the kernel? I'm not sure where I go from here
But I do appreciate your time. Now it makes sense why bloatware keeps returning and I still get notices of updates sometimes.
After regaining my composure...I got it working. There was a problem with Supersu binaries. I reinstalled it. Then reflashed jmz kernel. After wiping dalvik I rebooted. It's been working fine for an hour now.
I do have what I believe is the engineering image. The initial screen says it's just for developers but unless there's something nefarious there then I can live with it. Now I'd like to finally unload some of this bloatware. If anyone has any tips on what's safe to uninstall please share. Thanks.
Well I have just rooted my device by installing ES File Explorer from the Apps Store and then using Silk browser to download towelroot from towelroot.com. Install it using ES File Explorer and run. Click make it rain and the tablet is rooted. Open ES File Explorer again, top left open the menu, select tools and turn Root Explorer ON.
Now I just need to find what to do next and see what roms are available!
Help!?!
well
reconminicon said:
Well I have just rooted my device by installing ES File Explorer from the Apps Store and then using Silk browser to download towelroot from towelroot.com. Install it using ES File Explorer and run. Click make it rain and the tablet is rooted. Open ES File Explorer again, top left open the menu, select tools and turn Root Explorer ON.
Now I just need to find what to do next and see what roms are available!
Help!?!
Click to expand...
Click to collapse
you could have accomplished most of that by one of the utilities in the development section and use same. 95 utility to disable updates. From that point on start reading there are all kinds of new things that are coming out and lots and lots and lots of information.
from what I read, after you have been rolled back BY Amazon you no longer need to OTA updates ?
jimyv said:
you could have accomplished most of that by one of the utilities in the development section and use same. 94 utility to disable updates. From that point on start reading there are all kinds of new things that are coming out and lots and lots and lots of information.
Click to expand...
Click to collapse
It does work with that firmware. Installed Safestrap and the thor 202 rom with gapps and all works fine.
reconminicon said:
It does work with that firmware. Installed Safestrap and the thor 202 rom with gapps and all works fine.
Click to expand...
Click to collapse
Edit: Just received a reply in another thread, it isn't currently possible to rollback 13.3.2.7. Hopefully it's not too far away though. =( If you did find a way too do it with 13.3.2.7 be sure to tell us how you did it then.
reconminicon said:
It does work with that firmware. Installed Safestrap and the thor 202 rom with gapps and all works fine.
Click to expand...
Click to collapse
just trying to clarify here what worked on your firmware?
The utility for the HDX?
did the rep also tell you you would not be eligible for further OTA updates?so no need to use that utility to block them?
Not a further rollback correct?
which safestrap version? operating on which firmware?
after your roll back down to .7. From what firmware?
as far as I have read there is currently not a way to roll back any further than .7 from .5.1 \.5.2 ...=BRICK
so please explain what you are saying here so you are not confusing people into attempting the wrong things
jimyv said:
just trying to clarify here what worked on your firmware?
The utility for the HDX?
did the rep also tell you you would not be eligible for further OTA updates?so no need to use that utility to block them?
Not a further rollback correct?
which safestrap version? operating on which firmware?
after your roll back down to .7. From what firmware?
as far as I have read there is currently not a way to roll back any further than .7 from .5.1 \.5.2 ...=BRICK
so please explain what you are saying here so you are not confusing people into attempting the wrong things
Click to expand...
Click to collapse
I bought it for my mother for Christmas and thought would be better with Andriod.
Got it out the box connected to the internet and it automatically updated to 4.5.1. I contacted Amazon using the SOS app and told them what I wanted to do and they rolled it back. They told me I would not get any future updates and customer service might be hard in the future as it would be running different software version. They requested TS to do it and said it would take two days. The update automatically came through and updated/backdated.
The SafeStrap version would of been the most recent as I think I downloaded it from their site.
The 2.0.2 Thor Rom I mentioned worked fine. The other one would not install. Cannot remember the message I was given but when going onto the Play Store Iand trying to download the daily newspaper it was saying designed for mobile. So I guess it was based on a mobile Rom. This was no good for me and thought my mother was getting along with the Amazon OS quite good. (As she is 67 and its her first device) so I ended up installing the Amazon OS from SafeStrap.
I ended up taking it back to Argos for an exchange, said it was switching itself of as I didnt know how to get rid of SafeStrap on boot and wanted the updates back. My mother loves it.
Amazon also removed the adverts free of charge but after the emplacement they are back. Need to SOS them again.
Hope this helps as I am no pro.
Sorry. Ignore it. Was 13.3.2.6 not 13.3.2.7
kindle fire hdx 14.3.2.8 (apollo 8.9)
greetins,
I received rollback update to 14.3.2.8, is possible to install any other rom instead on this? Tablet is rooted via towelroot, what is next step, what is necessary to do (is possible to install safestrap? may I after this rollback to previous version where is bootloader unlocked?
Thank you very much for your answer.
dont try to rollback you will brick your device
undulus said:
greetins,
I received rollback update to 14.3.2.8, is possible to install any other rom instead on this? Tablet is rooted via towelroot, what is next step, what is necessary to do (is possible to install safestrap? may I after this rollback to previous version where is bootloader unlocked?
Thank you very much for your answer.
Click to expand...
Click to collapse
Well right now you cant do much:
1. Download safestrap and try to install it (should work)
2. If you can enter safestrap make a backup for stock so you can restore if something goes wrong
3. Make a new slot
4. Switch to new slot
5. Install previously downloaded Nexus 2.0.2 rom to created slot (not stock!!!)
6. Reboot and enjoy your kindle
7. Tell us if you succeeded, its possible that safestrap or later nexus wont work because of 3.2.8 kernel
Dont try to roll back you most probably brick your device
jeryll said:
Well right now you cant do much:
1. Download safestrap and try to install it (should work)
2. If you can enter safestrap make a backup for stock so you can restore if something goes wrong
3. Make a new slot
4. Switch to new slot
5. Install previously downloaded Nexus 2.0.2 rom to created slot (not stock!!!)
6. Reboot and enjoy your kindle
7. Tell us if you succeeded, its possible that safestrap or later nexus wont work because of 3.2.8 kernel
Dont try to roll back you most probably brick your device
Click to expand...
Click to collapse
Thank you very much, installation of safestrap and after this rom Nexus 2.0.2 was without problem, all is working, thank you again. But is any way howto rollback to previous firmware - I am not sure version, but as I read, is possible to rollback into version where the bootloader was open and is not necessary to use safestrap ( Safestrap is good, but I have to modifed my partition )
How big partition for system is necessary? Default value was mayby 2.5GB.
And thank you again
Well
undulus said:
But is any way howto rollback to previous firmware - I am not sure version, but as I read, is possible to rollback into version where the bootloader was open and is not necessary to use safestrap ( Safestrap is good, but I have to modifed my partition )
How big partition for system is necessary? Default value was mayby 2.5GB.
And thank you again
Click to expand...
Click to collapse
I am glad you have working Nexus...
For downgrading using known method you must be on firmware xx.3.2.6, xx.3.2.5, xx.3.2.4. Several peoples reported that they bricked their device trying downgrade from xx.3.2.7! You can check here, but you have been warned, dont try that on your device!!! If you brick your device I cant help you, dont know how...
Default size for system partition is fine, I think...
undulus said:
Thank you very much, installation of safestrap and after this rom Nexus 2.0.2 was without problem, all is working, thank you again. But is any way howto rollback to previous firmware - I am not sure version, but as I read, is possible to rollback into version where the bootloader was open and is not necessary to use safestrap ( Safestrap is good, but I have to modifed my partition )
How big partition for system is necessary? Default value was mayby 2.5GB.
And thank you again
Click to expand...
Click to collapse
Hi,
which version of Safetrap you installed? All links I see are for Apollo (in the thread linked above), and my device is Thor. I assume i sould install Safestrap-Thor-3.75-os3.2.4-B02.apk (not Apollos) ?
Also, once installed, is there a way to revert back everything (fire recovery and etc)?
johim said:
Hi,
which version of Safetrap you installed? All links I see are for Apollo, and my device is Thor. I assume i sould install Safestrap-Thor-3.75-os3.2.4-B02.apk (not Apollos) ?
Also, once installed, is there a way to revert back everything (fire recovery and etc)?
Click to expand...
Click to collapse
Safestrap actually doesn't replace the original recovery like TWRP.
All you need to do is uninstall it through that same app, but remember to remove any additional ROM slots or else they'll still be taking up space.
EncryptedCurse said:
Safestrap actually doesn't replace the original recovery like TWRP.
All you need to do is uninstall it through that same app, but remember to remove any additional ROM slots or else they'll still be taking up space.
Click to expand...
Click to collapse
I understand. Its all working now. Its more slow than usual thou.
Another question, once installed Nexus 2.0.2, do I need to root it? Any recommended method? I'm guessing I only need to flash supersu from safetrap, tried searchin in the safetrap topic, but its huge.
I am on rooted Thor with 13.3.2.4, with the Nexus Rom installed via safestrap. I have been reading all the threads on unlocking the bootloader and find all of the steps to be very scary. I would like to wait until there was some kind of "toolkit" for this rather than having to first downgrade and then use python through adb etc which I am somewhat uncomfortable with. Will there ever be such a simpler solution?
The bootloader unlock procedure is a no brainer, can't mess up anything there. Downgrading is a little risky, but you're on 3.2.4, thus you can even use the rollback images for Safestrap, take a look at this thread (page 1 is about 3.2.5/3.2.6 users who can NOT use the downgrade images). I'm afraid it won't get any easier than that.
If you don't want to use Python, just execute the adb commands to get your ID and serial (post them here, or PM me if you don't want anyone to see them), I'll create the .unlock file for you then. Downgrading and (actual) unlocking are tasks you have to do yourself though.
I think I might try it this weekend. Thanks for the help.
Cl4ncy said:
The bootloader unlock procedure is a no brainer, can't mess up anything there. Downgrading is a little risky, but you're on 3.2.4, thus you can even use the rollback images for Safestrap, take a look at this thread (page 1 is about 3.2.5/3.2.6 users who can NOT use the downgrade images). I'm afraid it won't get any easier than that.
If you don't want to use Python, just execute the adb commands to get your ID and serial (post them here, or PM me if you don't want anyone to see them), I'll create the .unlock file for you then. Downgrading and (actual) unlocking are tasks you have to do yourself though.
Click to expand...
Click to collapse
I have successfully downgraded to 13.3.1.0, but I am confused about how to install TWRP. Since I have not enabled wifi and registered, I can't install flashify or cwm, or even install a file explorer apk to access my storage, and I don't know how to get the twrp.img file (which I guess I can only install via adb?) Where do I get the correct twrp.img file? I'm kind of stuck....
kbs24 said:
I have successfully downgraded to 13.3.1.0, but I am confused about how to install TWRP. Since I have not enabled wifi and registered, I can't install flashify or cwm, or even install a file explorer apk to access my storage, and I don't know how to get the twrp.img file (which I guess I can only install via adb?) Where do I get the correct twrp.img file? I'm kind of stuck....
Click to expand...
Click to collapse
I am by no means an expert but I just went through this process myself yesterday and it was relatively simple. Check this thread. It has a number of helpful posts in it, including my questions from yesterday.
The correct TWRP image is here. Just follow the instructions in that thread. It's super simple if you use the minimal adb and fastboot linked by Cl4ncy in the first thread I linked. If you have any other questions I'll do my best to help you.
kbs24 said:
I have successfully downgraded to 13.3.1.0, but I am confused about how to install TWRP. Since I have not enabled wifi and registered, I can't install flashify or cwm, or even install a file explorer apk to access my storage, and I don't know how to get the twrp.img file (which I guess I can only install via adb?) Where do I get the correct twrp.img file? I'm kind of stuck....
Click to expand...
Click to collapse
Sorry for the late reply, @muunkin pointed you in the right direction already.
Be sure to (re-)root 3.1.0 and disable OTA via HDX ToolKit, and enable USB debugging in Fire OS, hope you installed minimal adb and fastboot, then copy the TWRP image for your HDX (Thor = 7", Apollo = 8.9") to the root of the sdcard (which is the directory you'll see in Explorer after connecting the HDX to your PC, i.e. don't open another directory), open a DOS box, change dir to the adb directory (enter cd\adb) and enter the commands mentioned in the TWRP thread. This will flash the TWRP image to the recovery parition.
Do a backup of your Fire OS in TWRP before you flash any custom ROM, and copy it to your PC, also look for the TWRP backup of the stock recovery (I think TWRP does a backup somewhere), and move that to your PC as well.
In case you don't know how to access TWRP: with the HDX powered off, you press and hold volume up, then press and hold the power button, release both when the grey Kindle Fire logo appears on screen. Some ROMs (e.g. CM12) offer the advanced reboot in developer options, this will add options to reboot into recovery, bootloader or a soft (quick) reboot to the power menu.
Cl4ncy said:
Sorry for the late reply, @muunkin pointed you in the right direction already.
Be sure to (re-)root 3.1.0 and disable OTA via HDX ToolKit, and enable USB debugging in Fire OS, hope you installed minimal adb and fastboot, then copy the TWRP image for your HDX (Thor = 7", Apollo = 8.9") to the root of the sdcard (which is the directory you'll see in Explorer after connecting the HDX to your PC, i.e. don't open another directory), open a DOS box, change dir to the adb directory (enter cd\adb) and enter the commands mentioned in the TWRP thread. This will flash the TWRP image to the recovery parition.
Do a backup of your Fire OS in TWRP before you flash any custom ROM, and copy it to your PC, also look for the TWRP backup of the stock recovery (I think TWRP does a backup somewhere), and move that to your PC as well.
In case you don't know how to access TWRP: with the HDX powered off, you press and hold volume up, then press and hold the power button, release both when the grey Kindle Fire logo appears on screen. Some ROMs (e.g. CM12) offer the advanced reboot in developer options, this will add options to reboot into recovery, bootloader or a soft (quick) reboot to the power menu.
Click to expand...
Click to collapse
Thank you both @muunkin and @Cl4ncy for guiding me through this. It is clear now that I have to flash TWRP via adb. Unfortunately I did, however, last night briefly turn on wifi in order to get es file explorer, and very quickly the OS ugraded itself to 13.3.2.3. Then, stupidly, I decided to go back to Nexus rom 2.0.2, which I did by reinstalling safestrap. And, Nexus rom is installed on the Stock Rom slot, and I did NOT backup the 13.3.2.3 stock rom. SO, since I am on Nexus rom, do I understand correctly that I need to begin again by downgrading to 13.3.1.0? Right? (After printing out all of these threads and printing out a lot of it and carefully reading, it looks to me like if I had stayed on stock 13.3.2.3 I would not have had to downgrade.....but too late now anyway.) I do have the minimal adb and fastboot installed, and my device is recognized, so eventually this will work I'm pretty sure. I appreciate the help!
kbs24 said:
Thank you both @muunkin and @Cl4ncy for guiding me through this. It is clear now that I have to flash TWRP via adb. Unfortunately I did, however, last night briefly turn on wifi in order to get es file explorer, and very quickly the OS ugraded itself to 13.3.2.3. Then, stupidly, I decided to go back to Nexus rom 2.0.2, which I did by reinstalling safestrap. And, Nexus rom is installed on the Stock Rom slot, and I did NOT backup the 13.3.2.3 stock rom. SO, since I am on Nexus rom, do I understand correctly that I need to begin again by downgrading to 13.3.1.0? Right? (After printing out all of these threads and printing out a lot of it and carefully reading, it looks to me like if I had stayed on stock 13.3.2.3 I would not have had to downgrade.....but too late now anyway.) I do have the minimal adb and fastboot installed, and my device is recognized, so eventually this will work I'm pretty sure. I appreciate the help!
Click to expand...
Click to collapse
No, 13.3.2.3 is ok for both TWRP and unlocking the bootloader, i.e. no need to flash 3.1.0 again - a firmware below 3.2.4 is enough.
Cl4ncy said:
No, 13.3.2.3 is ok for both TWRP and unlocking the bootloader, i.e. no need to flash 3.1.0 again - a firmware below 3.2.4 is enough.
Click to expand...
Click to collapse
Even if I am not running on the stock rom? I can adb install TWRP while on Nexus rom?
kbs24 said:
Even if I am not running on the stock rom? I can adb install TWRP while on Nexus rom?
Click to expand...
Click to collapse
Hm, I'm not exactly sure about this - @ggow's answer here seems to point out that you really have to do it all over again.
Why did you install Safestrap again anyway? ADB-flashing TWRP and unlocking the bootloader before you install a custom ROM would've been the next steps. Also I told you to create a backup of your stock slot before you flash any custom ROM, didn't I?
Cl4ncy said:
Hm, I'm not exactly sure about this - @ggow's answer here seems to point out that you really have to do it all over again.
Why did you install Safestrap again anyway? ADB-flashing TWRP and unlocking the bootloader before you install a custom ROM would've been the next steps. Also I told you to create a backup of your stock slot before you flash any custom ROM, didn't I?
Click to expand...
Click to collapse
Yes you sure did, and that's why I said "stupidly" about me putting safestrap back and nexus rom. I was overanxious and acted impulsively, not having a recovery installed was freaking me out. Bad habit. About doing the backup, there did not appear to be enough room on the internal storage. Sorry. We'll start over no problem. Again thanks.
kbs24 said:
Yes you sure did, and that's why I said "stupidly" about me putting safestrap back and nexus rom. I was overanxious and acted impulsively, not having a recovery installed was freaking me out. Bad habit. About doing the backup, there did not appear to be enough room on the internal storage. Sorry. We'll start over no problem. Again thanks.
Click to expand...
Click to collapse
I'm also not sure how to do this now. You don't have any Safestrap 3.2.3 Fire OS backup to restore, you shouldn't use the 3.2.4 rollback image, as you're not on 3.2.4, so what do you want to flash to the stock slot now? Or did I miss anything?
Cl4ncy said:
I'm also not sure how to do this now. You don't have any Safestrap 3.2.3 Fire OS backup to restore, you shouldn't use the 3.2.4 rollback image, as you're not on 3.2.4, so what do you want to flash to the stock slot now? Or did I miss anything?
Click to expand...
Click to collapse
I was going to look for a stock 3.2.3 to flash. If can't find, I do have a backup of stock 3.2.4 on the card which I would flash, thus requiring the downgrade.
kbs24 said:
I was going to look for a stock 3.2.3 to flash. If can't find, I do have a backup of stock 3.2.4 on the card which I would flash, thus requiring the downgrade.
Click to expand...
Click to collapse
I haven't seen a 3.2.3 Safestrap flashable Image, good luck. Regarding the 3.2.4 backup I'm not sure whether it works with the 3.2.3 bootloader.
Cl4ncy said:
I haven't seen a 3.2.3 Safestrap flashable Image, good luck. Regarding the 3.2.4 backup I'm not sure whether it works with the 3.2.3 bootloader.
Click to expand...
Click to collapse
Yeah, I am probably screwed. But we'll see. I'm pretty sure I understand what the process should be at least.
kbs24 said:
Yeah, I am probably screwed. But we'll see. I'm pretty sure I understand what the process should be at least.
Click to expand...
Click to collapse
Not sure how far you got with this but you *should* be able to flash TWRP from Nexus provided the version of FireOS was 3.2.3.2 or lower prior to the installation of Safestrap v3. The customized version of twrp leverages a vulnerability in the HDX bootloader that is installed with FireOS. Neither Safestrap nor Nexus mess with the bootloader so the prerequisites should remain intact. I say should as interactions are complex - further complicated by a fussy device with limited recovery capability should something go wrong. To the best of my knowledge no one has attempted a twrp flash from Nexus while Safestrap v3 is installed.
Thoughts:
- grab flashify from the play store or here; make a backup of your current recovery environment (this step will also help to familiarize you with flashify)
- download the HDX customized version of twrp (here); use ES File Explorer to verify MD5
- use flashify to install twrp (can also be done via adb commands as shown in the twrp op)
Options:
- unlock the bootloader before attempting other remedial steps. Unlocking is a frustrating but low/no risk activity that yields substantially improved recovery capabilities once completed. Yep - you can do this without twrp (unlocking before flashing twrp is the recommended path according to several devs - although I prefer the opposite).
[-or-]
- flash 3.1.0 from here to the stock slot and then attempt to remove Safestrap v3. If successful you can proceed with flashing twrp unlocking, etc in the normal manner. As with any flash there is a risk something will go wrong or FireOS will not start up properly. To help mitigate the latter suggest installing a fallback version of Nexus v2 in a secondary slot. Don't forget to remove this slot before uninstalling SS.
The above is only an outline. Give it some thought and post any questions BEFORE taking action. I also suggest you let this post sit for a few days in case some of the rational is fatally flawed. Lots of smart people in the community who will jump in if my guidance is misdirected (which it has been shown to be on occasion). Don't risk a brick by acting too quickly. Proper preparation is essential for a successful outcome.
Sorry for sounding like your mum ... :angel:
Davey126 said:
Not sure how far you got with this but you *should* be able to flash TWRP from Nexus provided the version of FireOS was 3.2.3.2 or lower prior to the installation of Safestrap v3. The customized version of twrp leverages a vulnerability in the HDX bootloader that is installed with FireOS. Neither Safestrap nor Nexus mess with the bootloader so the prerequisites should remain intact. I say should as interactions are complex - further complicated by a fussy device with limited recovery capability should something go wrong. To the best of my knowledge no one has attempted a twrp flash from Nexus while Safestrap v3 is installed.
Thoughts:
- grab flashify from the play store or here; make a backup of your current recovery environment (this step will also help to familiarize you with flashify)
- download the HDX customized version of twrp (here); use ES File Explorer to verify MD5
- use flashify to install twrp (can also be done via adb commands as shown in the twrp op)
Options:
- unlock the bootloader before attempting other remedial steps. Unlocking is a frustrating but low/no risk activity that yields substantially improved recovery capabilities once completed. Yep - you can do this without twrp (unlocking before flashing twrp is the recommended path according to several devs - although I prefer the opposite).
[-or-]
- flash 3.1.0 from here to the stock slot and then attempt to remove Safestrap v3. If successful you can proceed with flashing twrp unlocking, etc in the normal manner. As with any flash there is a risk something will go wrong or FireOS will not start up properly. To help mitigate the latter suggest installing a fallback version of Nexus v2 in a secondary slot. Don't forget to remove this slot before uninstalling SS.
The above is only an outline. Give it some thought and post any questions BEFORE taking action. I also suggest you let this post sit for a few days in case some of the rational is fatally flawed. Lots of smart people in the community who will jump in if my guidance is misdirected (which it has been shown to be on occasion). Don't risk a brick by acting too quickly. Proper preparation is essential for a successful outcome.
Sorry for sounding like your mum ... :angel:
Click to expand...
Click to collapse
Thanks for your input. I am still on the nexus rom, but I am fairly sure that Safestrap was installed while on 13.3.2.4. Is there a way to tell? It is safestrap 3.75, based on twrp 2.7.
I had some time today to work on this, and after looking over the ideas from all of you (thank you very much!) it seemed that my only option is to restore my backup which will get me back to the Nexus 2.0.2 rom. So I did this successfully. Being on Nexus rom, I was then able to use the 13.3.2.4 rollback file to get back to 13.3.0.9. Then ran into trouble......the system update to 13.3.1.0 was not successful. the .bin file was located, but all that happened was a "validating update file" followed by forced reboot. I remain stuck on 13.3.0.9. There are threads discussing editing build.prop but I know I did not have to do this when I first did a rollback a few days ago. Not sure whether to give up or maybe someone has another idea how to get the system to use that .bin file? Should I turn on wifi and wait for an ota or is that too risky, will it jump me all the way up to the most current build? Will it maybe go incrementally?
kbs24 said:
Thanks for your input. I am still on the nexus rom, but I am fairly sure that Safestrap was installed while on 13.3.2.4. Is there a way to tell? It is safestrap 3.75, based on twrp 2.7.
Click to expand...
Click to collapse
(Also as you suggested, I did try flashing the zip 3.1.0 and it did not work, never rebooted successfully. So went back again to 3.0.9.)
kbs24 said:
I had some time today to work on this, and after looking over the ideas from all of you (thank you very much!) it seemed that my only option is to restore my backup which will get me back to the Nexus 2.0.2 rom. So I did this successfully. Being on Nexus rom, I was then able to use the 13.3.2.4 rollback file to get back to 13.3.0.9. Then ran into trouble......the system update to 13.3.1.0 was not successful. the .bin file was located, but all that happened was a "validating update file" followed by forced reboot. I remain stuck on 13.3.0.9. There are threads discussing editing build.prop but I know I did not have to do this when I first did a rollback a few days ago. Not sure whether to give up or maybe someone has another idea how to get the system to use that .bin file? Should I turn on wifi and wait for an ota or is that too risky, will it jump me all the way up to the most current build? Will it maybe go incrementally?
Click to expand...
Click to collapse
Glad you were able to make some progress. I believe you could have flashed twrp from Nexus as I believe you successfully downgraded/upgraded to 13.3.2.3 which would then be the base version when you reininstalled Safestrap. But you found another path which is just fine.
It is possible the 13.3.1.0 is invalid (possibly corrupt). You can use ES File Explorer to validate the MD5 (c49c0363de4d8dfa5c87c1bdb88aa2ba) or download a fresh copy here. You can also upgrade directly to 13.3.2.3 instead of hopscotching through 13.3.1.0 and then applying the 13.2.3.3 bootloader update.
I strongly suggest you NOT connect to WiFi as it is unpredictable if/when you will receive at OTA and what version will be downloaded. Options for getting files onto you device:
- use HDX toolkit to root and block OTA on 13.3.0.9; you can then enable WiFi
- tether your device and drop files into "Internal Storage"
- use 'adb push' to transfer files
You should not need to mess with build.prop as the 3.2.4->3.0.9 rollback should have handed that. It's quite easy to brick your device if you get any of the edits or permissions wrong.
I got a new Motherboard and daughterboard in my HDX Apollo. I was able to get TWRP on it, but it keeps saying i dont appear to have root. I tried installing the latest supersu but it apparently didnt work. Anyway, i have realized that i just keep getting myself into trouble playing with root. All i want is to get my 3rd gen back to 4.5.5.1 fire os and wait for the fire os 5 update for it(hopefully) Any help on how i can do that? Ive tried downloading the latest Kindle update for apollo, renaming the .bin to update.zip and transferring it over and installing it but it never boots further than the 'kindle' screen.
Thanks for your help, sorry to be a pain
If you're on Fire OS 4.x you don't have TWRP, but Safestrap v4. After what you've done, do you still have access to Safestrap? Installing an amazon update with Safestrap installed, or even just rooted could easily mess up the device, i.e. brick it.
I don't think it's fire os 4x then. It does boot into the twrp interface and is fully functional but when you go to reboot into a different recovery it says something like "it appears you do not have root. Would you like to install supersu?" Even if I say yes it acts like it installs but apparently doesn't. I can post pics later
Sent from my SM-G920V using XDA-Developers mobile app
Cl4ncy said:
If you're on Fire OS 4.x you don't have TWRP, but Safestrap v4. After what you've done, do you still have access to Safestrap? Installing an amazon update with Safestrap installed, or even just rooted could easily mess up the device, i.e. brick it.
Click to expand...
Click to collapse
Oh and I'm not sure what the new board had on it. It never fully booted. That's why I installed twrp. Thanks for the reply though!
Sent from my SM-G920V using XDA-Developers mobile app
mhuck0625 said:
I don't think it's fire os 4x then. It does boot into the twrp interface and is fully functional but when you go to reboot into a different recovery it says something like "it appears you do not have root. Would you like to install supersu?" Even if I say yes it acts like it installs but apparently doesn't. I can post pics later
Click to expand...
Click to collapse
mhuck0625 said:
Oh and I'm not sure what the new board had on it. It never fully booted. That's why I installed twrp. Thanks for the reply though!
Click to expand...
Click to collapse
- how did you "install" TWRP (method)?
- how are you accessing TWRP - just pressing the power button or some key combination (yes, it's important)?
- does a graphic vaguely resembling Frankenstein appear when you power up the device?
Davey126 said:
- how did you "install" TWRP (method)?
- how are you accessing TWRP - just pressing the power button or some key combination (yes, it's important)?
- does a graphic vaguely resembling Frankenstein appear when you power up the device?
Click to expand...
Click to collapse
I installed TWRP using the method instructed here: http://forum.xda-developers.com/kin...-to-unbrick-kindle-fire-hdx-firmware-t3277197
When i want to get to TWRP i press and hold Power + Vol UP until it rebootes into the Teamwin screen and TWRP. It is version 2.8.7.0 now(the instructions got 2.8.5.0 installed then i upgraded)
I dont remember what the graphic looked like when booting into TWRP but i know it said TeamWin. I can check when i get it charged back up enough to turn on. Ive had it sitting unplugged for days and the battery ran dead. I hope this is enough info to help get me pointed in the right direction. Thanks!
Ok, if it's the real TWRP which it seems to be, Safestrap has no TeamWin logo at boot, I'd suggest you leave it be. Currently you can use all available ROMs, so if there'll be a future version of Fire OS you could use a TWRP flashable version of it. I doubt there will be a Fire OS 5 update for the "old" Thor/Apollo line though.
You would destroy the possibilities you currently have by updating to Fire OS 4.5.5.1.
Meanwhile you can unlock your bootloader (if you haven't already), and update TWRP to 3.0.0-1 (requires unlocked bootloader).
Don't I need root though? How can I unlock my bootloader from the stage I'm at now? I'm just a bit afraid of proceeding in case I brick it again
Sent from my SM-G920V using XDA-Developers mobile app
Cl4ncy said:
Ok, if it's the real TWRP which it seems to be, Safestrap has no TeamWin logo at boot, I'd suggest you leave it be. Currently you can use all available ROMs, so if there'll be a future version of Fire OS you could use a TWRP flashable version of it. I doubt there will be a Fire OS 5 update for the "old" Thor/Apollo line though.
You would destroy the possibilities you currently have by updating to Fire OS 4.5.5.1.
Meanwhile you can unlock your bootloader (if you haven't already), and update TWRP to 3.0.0-1 (requires unlocked bootloader).
Click to expand...
Click to collapse
Don't I need root though? How can I unlock my bootloader from the stage I'm at now? I'm just a bit afraid of proceeding in case I brick it again
Sent from my SM-G920V using XDA-Developers mobile app
There's no risk in unlocking, the bootloader either unlocks or it errors/fails. Try the one-click-solution first (might require the PDANet drivers). It's recommended to update the bootloader to 3.2.3.2 (do it only, if the unlock worked ok).
TWRP can be updated from TWRP itself, so I'd recommend doing it that way. Just be sure to flash the TWRP image to the recovery partition.
Cl4ncy said:
There's no risk in unlocking, the bootloader either unlocks or it errors/fails. Try the one-click-solution first (might require the PDANet drivers). It's recommended to update the bootloader to 3.2.3.2 (do it only, if the unlock worked ok).
TWRP can be updated from TWRP itself, so I'd recommend doing it that way. Just be sure to flash the TWRP image to the recovery partition.
Click to expand...
Click to collapse
Tried 1-Click. In both Linux(Ubuntu 16.04) and Windows(10.1 x64) i get an error saying ADB is not enabled on the device. Ive tried booting into fastboot(with fastboot cable) tried using the regular cable and booting into TWRP. Any combination of boot modes and cables i can think of wont work. Where should i go from here?
Thanks
mhuck0625 said:
Don't I need root though? How can I unlock my bootloader from the stage I'm at now? I'm just a bit afraid of proceeding in case I brick it again
Click to expand...
Click to collapse
Root is irrelevant at this stage as nothing has been flashed to the system partition (where ROMs live).
Davey126 said:
Root is irrelevant at this stage as nothing has been flashed to the system partition (where ROMs live).
Click to expand...
Click to collapse
Ok, so i will need root to install ROMs then? How do i solve my problem unlocking the bootloader?
mhuck0625 said:
Tried 1-Click. In both Linux(Ubuntu 16.04) and Windows(10.1 x64) i get an error saying ADB is not enabled on the device. Ive tried booting into fastboot(with fastboot cable) tried using the regular cable and booting into TWRP. Any combination of boot modes and cables i can think of wont work. Where should i go from here?
Thanks
Click to expand...
Click to collapse
Lack of a functioning ROM could prove problematic if ADB is not enabled. I do not recall if the version of TWRP you installed provides native support for MTP which is essential for moving files onto the device. You may need to go the manual route to unlock bootloader which still requires tethered access but only at the fastboot level.
Nearing the edge of my pay grade on this topic; looking for others with more recent experience to jump in...
Davey126 said:
Lack of a functioning ROM could prove problematic if ADB is not enabled. I do not recall if the version of TWRP you installed provides native support for MTP which is essential for moving files onto the device. You may need to go the manual route to unlock bootloader which still requires tethered access but only at the fastboot level.
Nearing the edge of my pay grade on this topic; looking for others with more recent experience to jump in...
Click to expand...
Click to collapse
I do have mtp access and can transfer files easily. Should I try installing a Rom to see if I get adb access? What's a good Rom to try
Sent from my SM-G920V using XDA-Developers mobile app
Davey126 said:
Lack of a functioning ROM could prove problematic if ADB is not enabled. I do not recall if the version of TWRP you installed provides native support for MTP which is essential for moving files onto the device. You may need to go the manual route to unlock bootloader which still requires tethered access but only at the fastboot level.
Nearing the edge of my pay grade on this topic; looking for others with more recent experience to jump in...
Click to expand...
Click to collapse
Just curious on one thing. Whenever i see a ROM to download it says i need to unlock the bootloader and have root before i can do that. In MY case i do NOT have either, yet i was able to flash a new recovery(TWRP) How is this possible? How would i go about installing a new ROM or unlocking the bootloader?
Is there a way to flash the stock recovery back so i can reinstall fireOS and start from scratch?
Is there a way to tell what bootloader i have from within TWRP?
I realize i probably should have done a little more reading before i started messing with it :/ I do appreciate all the help you have been able to provide so far!
mhuck0625 said:
I do have mtp access and can transfer files easily. Should I try installing a Rom to see if I get adb access? What's a good Rom to try
Click to expand...
Click to collapse
mhuck0625 said:
Just curious on one thing. Whenever i see a ROM to download it says i need to unlock the bootloader and have root before i can do that. In MY case i do NOT have either, yet i was able to flash a new recovery(TWRP) How is this possible? How would i go about installing a new ROM or unlocking the bootloader?
Is there a way to flash the stock recovery back so i can reinstall fireOS and start from scratch?
Is there a way to tell what bootloader i have from within TWRP?
I realize i probably should have done a little more reading before i started messing with it :/ I do appreciate all the help you have been able to provide so far!
Click to expand...
Click to collapse
- traveling; response will be brief
- suggest flashing cm11 as it does not require an unlocked bootloader nor GAaps for basic functionality
- include SuperSU in flash package to secure root
- follow flashing directions in cm11 OP
- report back results; will go from there
Davey126 said:
- traveling; response will be brief
- suggest flashing cm11 as it does not require an unlocked bootloader nor GAaps for basic functionality
- include SuperSU in flash package to secure root
- follow flashing directions in cm11 OP
- report back results; will go from there
Click to expand...
Click to collapse
Downloaded CM11 and installed via this thread
http://forum.xda-developers.com/kin...-cm-11-safestrap-20150628-unofficial-t3145547
Copied it as well as the latest SuperSu(v2.65) to the Kindle Fire
Went to Install, saw both Zip files. Selected them(CM11 first, then Supersu second) Swipe to install, rebooted and nothing came up. Rebooted into TWRP and repeated the process after wiping dalvik/cache. Still nothing
mhuck0625 said:
Downloaded CM11 and installed via this thread
http://forum.xda-developers.com/kin...-cm-11-safestrap-20150628-unofficial-t3145547
Copied it as well as the latest SuperSu(v2.65) to the Kindle Fire
Went to Install, saw both Zip files. Selected them(CM11 first, then Supersu second) Swipe to install, rebooted and nothing came up. Rebooted into TWRP and repeated the process after wiping dalvik/cache. Still nothing
Click to expand...
Click to collapse
Makes sense. Likely no kernel. Will probably need to install a full version of FireOS for underlying components. Need to have a think about which build to maximize results, minimize rework. More later....
Davey126 said:
Makes sense. Likely no kernel. Will probably need to install a full version of FireOS for underlying components. Need to have a think about which build to maximize results, minimize rework. More later....
Click to expand...
Click to collapse
You have no idea how much i appreciate the help!
I look forward to hearing what you come up with!!
I would be happy just going straight back to full fire os - Stock EVERYTHING and not even worrying about running another OS. I just want to have a usable tablet again!