Related
First off, thanks for taking the time to read my post. I have been trying to root/flash rom since yesterday at 11am now 2:19pm a day later. So before whinning here, I did do my research. Flash is now done, *sigh*
I would like the froyo tazzv26 or 28 rom flashed on my Eris
I've watched yourtube how to videos, unlockr videos, several adroidforums how to posts. they all revert me back here.
My issue is this #1:most of those are old posts(which I've read and been reverted to), and obvious upgrades have been made therefore what thier videos/posts show are not what I'm seeing or reading . Being that this is new to me I feel lost and confused.
Issue#2 I found the rom I wanted, here when I searched Roms for Eris however a link that is next to it sends me to another and another page. Very frustrating.
Favor needed: I've never done this before so can someone please help walk me through the process of being on the ACTUAL page with the download link, and what happens from then. Then let me know what i'm supposed to be seeing on my computer screen once the process starts .** WOW this part is massively missing from all noobie post/videos= FYI for admins and moderators
FYI Eris is already rooted wth 4zroot (instead of HTC1 click since the power up and power button thing didn't work 4 times) I have superuser, quickboot, rom manager, and astro file manager all installed and ready to go.
I'm ready to take your lead
Dulce,
Saw your post over on AF and replied over there, but did really get the gist of your needs until I saw this thread over here on XDA.
Rooting with Z4 root does indeed root you, but this will not allow you to flash or install a custom ROM without having replaced your stock recovery with a custom one, the "one" being Amon_RA (stay away from ClockworkMod at this time for the Eris...the details are probably more than you want or need to know at this time).
The 1-click method that you mentioned previously is what you want and it will install Amon_RA's custom recovery for you.
I would highly advised you to read and understand this thread over on AndroidForums: http://androidforums.com/eris-all-things-root/127861-universal-eris-root-dummies.html
You will learn what you need to know from that thread and it will also show you how to install the very same custom recovery as the 1-click method/app. It is clearly more verbose, but the trade-off / benefit is that you will have the best instruction possible regarding rooting your Eris.
Check it out and good luck!
Cheers!
Hi everyone. I have a galaxy s4 on verizon and rooted. The phone is MK2 I believe. I have installed the safestrap recovery and nandroided my stock phone.
Every time I try to flash a custom ROM, the phone boots up, shows me the safestrap options to boot into recovery or continue. Once I hit continue, the phone just sits there with a black screen and doesn't boot up. I tried CM 11 and I tried Beanstalk and neither works. Does anyone have any ideas on what is causing this? I'm wiping data, cache, and dalavik cache before each flash. I flash the ROM and then I flash gapps. The recovery says the flash was successful.
Thanks for the help!
curryinaninstant said:
Hi everyone. I have a galaxy s4 on verizon and rooted. The phone is MK2 I believe. I have installed the safestrap recovery and nandroided my stock phone.
Every time I try to flash a custom ROM, the phone boots up, shows me the safestrap options to boot into recovery or continue. Once I hit continue, the phone just sits there with a black screen and doesn't boot up. I tried CM 11 and I tried Beanstalk and neither works. Does anyone have any ideas on what is causing this? I'm wiping data, cache, and dalavik cache before each flash. I flash the ROM and then I flash gapps. The recovery says the flash was successful.
Thanks for the help!
Click to expand...
Click to collapse
Take 5 minutes and scan the dozens of posts just like yours...the answers is there...good grief
safestrap enabled, Hyperdrive driven
I have but I'm new to this and all the jargon is confusing. Can you point me in the right direction please? Thanks for your help!
curryinaninstant said:
I have but I'm new to this and all the jargon is confusing. Can you point me in the right direction please? Thanks for your help!
Click to expand...
Click to collapse
Start reading...and there are youtube videos too...
safestrap enabled, Hyperdrive driven
---------- Post added at 03:06 PM ---------- Previous post was at 02:57 PM ----------
curryinaninstant said:
I have but I'm new to this and all the jargon is confusing. Can you point me in the right direction please? Thanks for your help!
Click to expand...
Click to collapse
Read safestrap thread...start at first post especially. .....
safestrap enabled, Hyperdrive driven
I have read that thread. I have watched the videos. When I try to use goo manager to do the loki hack, the phone boots up after installing a recovery and gives me an android screen that says DOWNLOADING. DO NOT UNPLUG DEVICE message and that just sits there forever. When I install via safestrap by creating a second partition and installing the rom there, as well as zipping the gapps and the requisite zzizp file, it just boots up into a blank screen. The only thing htat actually works the whole time is a nandroid backup. I don't know what I am doing incorrectly. Can you help please?
curryinaninstant said:
I have read that thread. I have watched the videos. When I try to use goo manager to do the loki hack, the phone boots up after installing a recovery and gives me an android screen that says DOWNLOADING. DO NOT UNPLUG DEVICE message and that just sits there forever. When I install via safestrap by creating a second partition and installing the rom there, as well as zipping the gapps and the requisite zzizp file, it just boots up into a blank screen. The only thing htat actually works the whole time is a nandroid backup. I don't know what I am doing incorrectly. Can you help please?
Click to expand...
Click to collapse
What makes you think you can install the loki hack on mk2 base phone in conjunction with safestrap?????
safestrap enabled, Hyperdrive driven
I uninstalled safestrap when I installed goomanager. Is that not what I'm suppoesd to do. I am new here. I don't know what I'm doing. Your help would be appreciated.
curryinaninstant said:
I uninstalled safestrap when I installed goomanager. Is that not what I'm suppoesd to do. I am new here. I don't know what I'm doing. Your help would be appreciated.
Click to expand...
Click to collapse
Why I suggested you do further reading...
safestrap enabled, Hyperdrive driven
look man. I think I've been respectful enough here. I've read the threads you recommended. I watched videos online. I have tried. I really have. I am new to this but you don't have to keep berating me for no reason. If you know what I'm supposed to do and can explain it to me in an easy to understand method, I'd really appreciate it. If not, then I'm not sure what you're trying to do because telling me to keep reading the same things that i've read over and over again without understanding them isn't getting either of us anywhere. I don't get the jargon. I don't get the lingo. I don't know what I'm doing wrong EVEN AFTER I've read through everything, so while I appreciate your attempts to educate me by trial, I'd really appreciate it if you just gave me an answer. If you don't have one, thats okay too, but at least we can stop playing this stupid game of cat and mouse.
curryinaninstant said:
look man. I think I've been respectful enough here. I've read the threads you recommended. I watched videos online. I have tried. I really have. I am new to this but you don't have to keep berating me for no reason. If you know what I'm supposed to do and can explain it to me in an easy to understand method, I'd really appreciate it. If not, then I'm not sure what you're trying to do because telling me to keep reading the same things that i've read over and over again withotu understanding them isn't getting either of us anywhere. I don't get the jargon. I don't get the lingo. I don't know what I'm doing wrong EVEN AFTER I've read through everything, so while I appreciate your attempts to educate me by trial, I'd really much rather appreciate it if you just gave me an answer. If you don't have one, thats okay too, but at least we can stop playing this stupid game of cat and mouse.
Click to expand...
Click to collapse
If you have done what you have said then because are on mk2 the ONLY option you have is safestrap after you are rooted You can't use goo manager. .you can't use twrp or cwm. You are limited to safestrap 3.71 and the couple of Roms thar are compatible to run...This is obvious from the getgo. If you don't understand the jargon then read and research more until you do...otherwise you will brick your phone and it will cost you money and time...
safestrap enabled, Hyperdrive driven
---------- Post added at 04:11 PM ---------- Previous post was at 04:09 PM ----------
decaturbob said:
If you have done what you have said then because are on mk2 the ONLY option you have is safestrap after you are rooted You can't use goo manager. .you can't use twrp or cwm. You are limited to safestrap 3.71 and the couple of Roms thar are compatible to run...This is obvious from the getgo. If you don't understand the jargon then read and research more until you do...otherwise you will brick your phone and it will cost you money and time...
safestrap enabled, Hyperdrive driven
Click to expand...
Click to collapse
New I'm not trying to berate you but this situation has been discuss countless times. I'm trying to help you.
safestrap enabled, Hyperdrive driven
that is much more helpful and I really do appreciate it. For a beginner, this isn't easy to parse through. IS there a way of switching from MK2 to something else so I can run one of the other roms?
curryinaninstant said:
that is much more helpful and I really do appreciate it. For a beginner, this isn't easy to parse through. IS there a way of switching from MK2 to something else so I can run one of the other roms?
Click to expand...
Click to collapse
Again...reading will tell you that you can't go back in firmware updates. Safestrap is a viable option and I have been running hyperdrive since safestrap was released.
safestrap enabled, Hyperdrive driven
curryinaninstant said:
look man. I think I've been respectful enough here. I've read the threads you recommended. I watched videos online. I have tried. I really have. I am new to this but you don't have to keep berating me for no reason. If you know what I'm supposed to do and can explain it to me in an easy to understand method, I'd really appreciate it. If not, then I'm not sure what you're trying to do because telling me to keep reading the same things that i've read over and over again without understanding them isn't getting either of us anywhere. I don't get the jargon. I don't get the lingo. I don't know what I'm doing wrong EVEN AFTER I've read through everything, so while I appreciate your attempts to educate me by trial, I'd really appreciate it if you just gave me an answer. If you don't have one, thats okay too, but at least we can stop playing this stupid game of cat and mouse.
Click to expand...
Click to collapse
OK, you want easy to understand. Let's try this:
Your phone has a version. In this case, it's apparently MK2.
You're doing stuff that worked on the original I545, build MDK. Those processes won't work on MK2, which is a fact that has been stated here over and over again, That's why you're getting berated, because this is a daily occurrence. We get people who don't read, don't understand what they're doing, and end up bricking their phones, just like you.
So here's what you would have found out if you had read around. Yes, I know there's a lot of threads here, but..
Any revision of the I545 later than MDK (ME7, MI1, MJ7, MK2) can't have a custom recovery, only Safestrap.
Any site where you got directions to install Goo Manager and flash away is wrong.
You're risking destroying your expensive phone by flashing before reading. Please look in to the Safestrap thread here and over in Android Development.
As we say, a little reading goes a long way.
Thank you!
curryinaninstant said:
Thank you!
Click to expand...
Click to collapse
I gotta say, I appreciate your tenacity here.
I too am fairly new to all this on the S4. I have done plenty of other flashes on other devices, and every time I go to work on a new device the learning curve is steep.
The 'scene' for lack of a better term has become a very convoluted mess filled with people that are quick to berate and think everyone is an illiterate asshole looking for a handout.
Everyday there seems to be another term or something I have not heard of. It is all well and good for the experts that have been in the thick of it from day one to just say, "Go read the forums!!!111one" and I get it, too many times the same questions are being asked. But the fact remains that if a single post like this would get stickied and maybe placed at the top General Q&A thread we would have an easy place to go for our answers and wouldn't have to start a new thread with a question like this and get flamed.
I mean good grief, you start reading the forum for OctOS, and nowhere does it say you cannot come from anything other than MDK originally. It does say that TWRP is the only supported method, but Safestrap, once booted it says at the top "Safestrap 3.70 (TWRP v2.6.3.1)" so how are we not to be confused?
You start reading a thread from the beginning and get terms like AOSP, GPe, Aroma, LOKI, Odexed, Deodexed, etc.. and all you can do is start searching for what each of those mean, which leads to you countless threads of "Shut up you lazy puke, and go read the forums!"
I know I'm ranting, but honestly, if you are taking the time to post a flame and tell someone to go read, then you could take the time and help point them in the right direction instead. I really appreciate the time both you guys took to answer his (and my) questions. It honestly did help me, and it was just a plain simple answer. I am glad I continued to read the thread though, because it certain started off as one of those 'shutup and read' threads. If there were something as simple as "So you want to mod you VZW S4?", stickied at the top of the S4 General forum, I for one would not have ended up here reading this same thread because I was in the same boat as this poor guy. Hell just making this thread a sticky would save you countless hours of replying to threads and telling people to read. I know all too well though that there are plenty lazy people out there just looking for the quick answer though, so believe me, I understand. But please remember we were all noobs at one point in time, and sometimes just need to ask someone for help.
So the long and short of it is, for us that were not smart enough to block or not take updates, or were unfortunate enough to have to swap equipment, if we are past the MDK build then we are stuck only being able to: root, install Safestrap 3.70, and possibly install one of the few Safestrap compatible roms based off the ME7 or MK2 official builds. I assume this is because the bootloader is locked on these versions and will only boot ROMS that have the same base signature, right? At least that is what I have been able to piece together from the countless threads I have tried reading and understanding.
And just because I mentioned them:
AOSP - Android Open Source Project, The raw version of Android that is free to use and modify for everyone. Countless custom roms are built on this.
GPe - Google Phone Edition? Not quite sure on this one. I think it means all the out-of-the-box Google Apps Functionality. Though I am still hazy.
Aroma - I believe this is a set of install scripts used by custom rom devs now days that allows their users to install the options they want. I have yet to be able to use a rom that has it, so I am not sure.
LOKI - A tool from Dan Rosenberg that allows people to bypass locked bootloaders. Verizon quickly caught the hole it used though and was patched after MDK, so that is why we on MK2 cannot have nice things.
Odexed vs. Deodexed - Refers to how an application runs and more specifically how it's memory space is handled. There is a nice write up but I am not allowed to post a link, essentially though odexed based ROMs will boot on the first load more quickly but are very customizible as far as themes and such go. Deodexed ROMs have to build the cache from instructions in the APK files, which take longer for the first boot only, or after a Dalvik wipe, and are just as fast after that first boot. Deodexed are more customizable.
Sorry for the long post, I am just tired of seeing threads that start off like these, while in the search for information. It was nice to see someone provide some guidance in the end though and I wanted to acknowledge that and rant a bit. [/RANT]
My KF HDX 7 is in 13.3.2.1, I had tried to up Gapps rom v2 but it don't work, I must factory reset and go back to stock rom.
Is there any rom that can my kindle can up???
Sory for my bad English
none.
tuilakhang said:
My KF HDX 7 is in 13.3.2.1, I had tried to up Gapps rom v2 but it don't work, I must factory reset and go back to stock rom.
Is there any rom that can my kindle can up???
Sory for my bad English
Click to expand...
Click to collapse
Do a manual upate to 13.3.2.2 ,root then the new thor rom will work with safestrap 3.75b02
jimyv said:
Do a manual upate to 13.3.2.2 ,root then the new thor rom will work with safestrap 3.75b02
Click to expand...
Click to collapse
Can you give me a link of 13.3.2.2 cause I had searched around but can't saw any link but 13.3.2.4
ok
tuilakhang said:
Can you give me a link of 13.3.2.2 cause I had searched around but can't saw any link but 13.3.2.4
Click to expand...
Click to collapse
There are multiple pages to these forums, for example if you open up the general section and you look at the bottom of the page it gives you option to go to the next page several pages worth of information there same goes with each subsection. There is also a( search this thread) option in the right upper of your page. If you are still reading by chance and you will find that updates you need for either Apollo or Thor on the bottom of page four in the general section.
Didnt already bricked one of your devices here? If you are one of the fellows that bricked I would advise you to learn how to use these forums efficiently before you break another device. If not then at the very least you need to do more homework at least figure out how to use this site efficiently into everyone's benefits. Most of us are here to help those that first at least are trying to help themselves. Good luck and enjoy.
Apparently pressing "ESC" in this window deletes all the text without being able to undo this.... so here goes again....
Sorry for the late reply, but i just saw your post in the developer's forum (Cpasjuste's Thor Gapps), where i cannot post due to my lurker nature.
i'm on the same FireOS version as you: 13.3.2.1
i had trouble getting Cpasjuste's ROM to work, because i was trying to use thor-gapps-13.3.0.0-v2. i didn't dare using thor-gapps-13.3.2.4-v1, because of the several warnings.
i then saw someone else having success with thor-gapps-13.3.2.4-v1 on an earlier version and thought i'd give it a try after all. i took the risk of closing the door to an unlocked bootloader, i took the risk of bricking my device. i decided to do this, because of my year long experience with custom ROMs, also on devices that were not intended to have them (Nook HD+, Kindle Fire...). i'm not sure, if the kernel is touched during the flash process, but i assum(ed) it isn't. i can boot into FireOS which still shows 13.3.2.1 as version, but who knows what has happened under the hood.
The ROM feels stable so far for such an early version. i haven't tested much, but the few apps I've been using regularly worked well. Ironically the amazon appstore crashed after about 20 seconds. Makes me think they are trying to block the "freed" devices, but it might just be a bug after all.
So, again, if you feel like risking to lose the possibility of an unlocked bootloader, if you want to risk or can afford to brick such an expensive device, you can try using thor-gapps-13.3.2.4-v1.
All i did, was to follow the instructions provided in Cpasjuste's thread exactly as they were.
Don't hold me accountable, it's already been a week, but if i recall correctly, these were my steps:
DIsable WiFi / Enable Airplane mode in FireOS (just to prevent automatic OTA updates)
Root device (i used towelroot)
Install Safestrap (i had to use Safestrap-Thor-3.75-os3.2.4-B02.apk, despite the instructions in the safestrap thread telling to use 3.72 on our version - another risk i took)
Boot into Safestrap
Backup Original ROM
Create ROM Slot (keep this new slot active/activated)
Restore Original ROM backup, but only the DATA partition
Wipe Cache + Dalvik Cache
Flash thor-gapps-13.3.2.4-v1.zip
Wipe Cache + Dalvik Cache
Boot into system
Hey, first post here but I've been reading some threads since 2011.
I have a Samsung Galaxy S4 (I have experience with custom roms and such with the Droid Charge, also Samsung. See a pattern?).
I rooted it a while back, but recently have been experiencing quite a bit of instability so I wanted to try a custom rom (Hyperdrive is the one that I'm looking at but that's kinda irrelevant to this post).
The problem for me is that every guide expects me to be rooted with the custom recovery. I am rooted, and I did have CWM installed to perform the root, but now for some reason recovery boots into stock and I haven't been able to load any custom recoveries. I tried the CWM Rom Manager app to get CWM back, but it didn't seem to work (touch or normal). I have also tried Goo Manager to get TWRP and that was a complete bust.
I noticed one or two other methods involving safe-strap but I cannot for the life of me get safe-strap working on my phone and I've followed a couple guides several times without success.
I need someone to point me in the right direction to get a custom recovery back on my phone. I'm assuming something got screwed up somewhere along the line, so I'm not confident in these other methods but I'm trying to find a guide using Odin. Part of the problem seems to be that the Verizon phones aren't too common so all the guides and downloads are for a different model.
Please help, I'd prefer an Odin method but I'm open to suggestions.
cdroid93 said:
Hey, first post here but I've been reading some threads since 2011.
I have a Samsung Galaxy S4 (I have experience with custom roms and such with the Droid Charge, also Samsung. See a pattern?).
I rooted it a while back, but recently have been experiencing quite a bit of instability so I wanted to try a custom rom (Hyperdrive is the one that I'm looking at but that's kinda irrelevant to this post).
The problem for me is that every guide expects me to be rooted with the custom recovery. I am rooted, and I did have CWM installed to perform the root, but now for some reason recovery boots into stock and I haven't been able to load any custom recoveries. I tried the CWM Rom Manager app to get CWM back, but it didn't seem to work (touch or normal). I have also tried Goo Manager to get TWRP and that was a complete bust.
I noticed one or two other methods involving safe-strap but I cannot for the life of me get safe-strap working on my phone and I've followed a couple guides several times without success.
I need someone to point me in the right direction to get a custom recovery back on my phone. I'm assuming something got screwed up somewhere along the line, so I'm not confident in these other methods but I'm trying to find a guide using Odin. Part of the problem seems to be that the Verizon phones aren't too common so all the guides and downloads are for a different model.
Please help, I'd prefer an Odin method but I'm open to suggestions.
Click to expand...
Click to collapse
If you are on NC5 then Safestrap is your only option. You are going to brick your phone if you just keep throwing recoveries at your phone until one sticks. If you are on MDK then your bootloader is unlocked and you can do what you want. Read the threads, that's what they're there for.
Jesus loves you!
Phone version
liljoe727 said:
If you are on NC5 then Safestrap is your only option. You are going to brick your phone if you just keep throwing recoveries at your phone until one sticks. If you are on MDK then your bootloader is unlocked and you can do what you want. Read the threads, that's what they're there for.
Jesus loves you!
Click to expand...
Click to collapse
I'm actually on ME7. I haven't updated in a very long while because I wanted to root and then stop tinkering. That's not an option for me anymore for the stability reasons. I had over a year of rock solid performance though so it was a good run.
I was searching threads on this forum and others. This one seems to be more reliable than others (and a whole lot friendlier), but I still can't find what I'm looking for.
Maybe you can help me out by pointing out one of the threads that has what I need?
Thanks much.
cdroid93 said:
I'm actually on ME7. I haven't updated in a very long while because I wanted to root and then stop tinkering. That's not an option for me anymore for the stability reasons. I had over a year of rock solid performance though so it was a good run.
I was searching threads on this forum and others. This one seems to be more reliable than others (and a whole lot friendlier), but I still can't find what I'm looking for.
Maybe you can help me out by pointing out one of the threads that has what I need?
Thanks much.
Click to expand...
Click to collapse
MDK, as I understand it, is the only bootloader that has been unlocked thus far. If you are still on ME7 and it's locked anyway, you may be better off just taking the update.
Jesus loves you!
liljoe727 said:
MDK, as I understand it, is the only bootloader that has been unlocked thus far. If you are still on ME7 and it's locked anyway, you may be better off just taking the update.
Jesus loves you!
Click to expand...
Click to collapse
Okay, well obviously I've messed up my phone somehow, I don't think it's possible for me to just go to system settings and update. How do I go about this if that doesn't work?
cdroid93 said:
Okay, well obviously I've messed up my phone somehow, I don't think it's possible for me to just go to system settings and update. How do I go about this if that doesn't work?
Click to expand...
Click to collapse
Well you can update via Samsung Keis, or if you know how to use ODIN you can flash the latest NC5 through ODIN. You'll find everything you'll need from here.
Forgot to say that after you upgrade you can root through towelroot which you can by searching this forum or Google it.
After you install busybox you should be able to install Safestrap, but if you can't, you need to download and install an app calle SElinuxmodechanger and set SElinux to permissive. Then you will be able to install Safestrap. Once you have SS you can only install ROMs on the Stock slot. non of the other slots work.
skeezer308 said:
Well you can update via Samsung Keis, or if you know how to use ODIN you can flash the latest NC5 through ODIN. You'll find everything you'll need from here.
Forgot to say that after you upgrade you can root through towelroot which you can by searching this forum or Google it.
After you install busybox you should be able to install Safestrap, but if you can't, you need to download and install an app calle SElinuxmodechanger and set SElinux to permissive. Then you will be able to install Safestrap. Once you have SS you can only install ROMs on the Stock slot. non of the other slots work.
Click to expand...
Click to collapse
Okay, for starters thank you. This is almost exactly what I needed. I've just got one more issue;
I cannot discern from what I've found on the forums or elsewhere what safestrap is safe for my phone now that I'm on NC5?
Thanks again for this, was a big help.
cdroid93 said:
Okay, for starters thank you. This is almost exactly what I needed. I've just got one more issue;
I cannot discern from what I've found on the forums or elsewhere what safestrap is safe for my phone now that I'm on NC5?
Thanks again for this, was a big help.
Click to expand...
Click to collapse
3.72
Jesus loves you!
Also keep in mind that you can only install TW ROMs or GPE ROMs that are SS friendly. If you try to install Cyanogen or other AOSP ROMs that require custom kernels you run the chance of bricking your phone
Hey guys ive got a hdx 7' RUNNING FIRE OS 3.2.4 everything i have been reading is saying that this version is somewhat unique in that there are a few roms availible mostly from safestrapp but most are not, twrp requires 3.2.3 and earlier as well as the bootloader unlock procedure. Can anyone point me in the direction on how to downgrade to one of the earlier versions. Currently i am rooted, ota disabled via: hdxtookit, i had safestrapp and a asop rom installed but was getting google play services stopped working error messages and restored to factory because i havent used the kindle in a year. Anyways i'm looking to get back into it and got cm 12.1 on my sgs3 and wanted to get something similar but keep runninginto problems with my version fire os. So just need a quick link to a roll back procedure in english and i should be able to do the rest from unlock - twrp - roms etc. I've been searching off and on the past few weeks but do not find anything definitive so i decided to finally ask to get an answer thanks for any and all help.
131 views no replies can anyone guide me to a solution?
rbkelley89 said:
131 views no replies can anyone guide me to a solution?
Click to expand...
Click to collapse
So basicaly for unlock BL and real TWRP you need have FW between x.3.1.0 and x.3.2.3:
Depending on your computer skills rollback can be achieved easy (or not).
Guide in english? Here, but you must mess with build.prop and on hdx especialy its really dangerous procedure - if you made simple mistake, it could be your last with that device and deadly for it for sure.
Sorry, I will not guide you through the process, if you feel you are lost, you can ask davey126 for help, but he answered this type of question soo many times . . . you can try read his posts before you ask him, there is high posibility he answered it somewhere...
jeryll said:
So basicaly for unlock BL and real TWRP you need have FW between x.3.1.0 and x.3.2.3:
Depending on your computer skills rollback can be achieved easy (or not).
Guide in english? Here, but you must mess with build.prop and on hdx especialy its really dangerous procedure - if you made simple mistake, it could be your last with that device and deadly for it for sure.
Sorry, I will not guide you through the process, if you feel you are lost, you can ask davey126 for help, but he answered this type of question soo many times . . . you can try read his posts before you ask him, there is high posibility he answered it somewhere...
Click to expand...
Click to collapse
@jeryll is spot on. There are a ton of helpful posts from a variety of authors that could get you started. This one comes to mind although there are many others. Lots of folks here are happy to answer targeted questions but you have to do your homework first. Read (and read some more), go slow, stop and post a question if unsure, don't take chances. Good luck.
Random thoughts:
- I strongly encourage upgrading to 13.3.2.5 or 13.3.2.6 prior to rolling back to 13.3.1.0. Lower risk and clears out 'crud' that could ruin your day.
- Use HDX toolkit to block/unblock OTA. Don't mess with any other technique; bad day follows.
- Once OTA is unblocked stay off WiFi. Period. Do transfer/installs via tether. Belt-and-suspenders types engage airplane mode and delete existing WiFi profiles too.
- Double check every action before executing. Stop and ask questions if unsure. Juggling babies is safer than taking a wrong turn (ok ... maybe that's a bit extreme).
- Many guides suggest bootloader unlocking before installing TWRP recovery. My comfort meter goes the opposite way. Your call. There are decent arguments for both approaches.
Davey126 said:
@jeryll is spot on. There are a ton of helpful posts from a variety of authors that could get you started. This one comes to mind although there are many others. Lots of folks here are happy to answer targeted questions but you have to do your homework first. Read (and read some more), go slow, stop and post a question if unsure, don't take chances. Good luck.
Random thoughts:
- I strongly encourage upgrading to 13.3.2.5 or 13.3.2.6 prior to rolling back to 13.3.1.0. Lower risk and clears out 'crud' that could ruin your day.
- Use HDX toolkit to block/unblock OTA. Don't mess with any other technique; bad day follows.
- Once OTA is unblocked stay off WiFi. Period. Do transfer/installs via tether. Belt-and-suspenders types engage airplane mode and delete existing WiFi profiles too.
- Double check every action before executing. Stop and ask questions if unsure. Juggling babies is safer than taking a wrong turn (ok ... maybe that's a bit extreme).
- Many guides suggest bootloader unlocking before installing TWRP recovery. My comfort meter goes the opposite way. Your call. There are decent arguments for both approaches.
Click to expand...
Click to collapse
How can I upgrade to 3.2.5 or 6. I believe I blocked ota it's been so lo.g ago I searched.for.the files and didn't see them anywhere so I assume it's still active even after factory restoration. And it's possible to twrp without unlocked boot loader? I didn't know that. What are the pros and cons. I'm not a dev so I went need to play around with much just want to rid of fire os and use a cm or nexus. If I can do that safety id LOVE that but still willing to try the adk route. Thanks for the info guys.
rbkelley89 said:
How can I upgrade to 3.2.5 or 6. I believe I blocked ota it's been so lo.g ago I searched.for.the files and didn't see them anywhere so I assume it's still active even after factory restoration. And it's possible to twrp without unlocked boot loader? I didn't know that. What are the pros and cons. I'm not a dev so I went need to play around with much just want to rid of fire os and use a cm or nexus. If I can do that safety id LOVE that but still willing to try the adk route. Thanks for the info guys.
Click to expand...
Click to collapse
Locate HDX toolkit in the Android Development thread and try to remove the OTA block that way. Keep WiFi off or you might receive an unwanted update.
Although not recommended twrp can be installed with a locked bootloader.
Travelling this week so can't get into more detail. Suggest you keep reading. Don't do stuff unless you are absolutely confident in your skills, knowledge, risks and expected outcome(s). Post questions. Many folks willing to help if you have done your homework. Sorry for brevity ...
Yes, be ESPECIALLY careful with build.prop. I learned this the hard way. They is nothing like Odin for Samsung that can save you.
XxD34THxX said:
Yes, be ESPECIALLY careful with build.prop. I learned this the hard way. They is nothing like Odin for Samsung that can save you.
Click to expand...
Click to collapse
The path I am suggesting does not involve modifying build.prop.
Can't he just use the rollback Images provided by ggow?
Must stay on 3.2.4. then though.
Cl4ncy said:
Can't he just use the rollback Images provided by ggow?
Must stay on 3.2.4. then though.
Click to expand...
Click to collapse
Nice finding, I absolutely forgot that this existed, of course he can use that thread with rollback images to downgrade to x.3.1.0! Then he can install TWRP etc... (as I did in the past - proof below )
jeryll said:
Thank you sir, successfully rolled back to 14.3.1.0, installed TWRP 2.8.1.0 and now I will play a little with TWRP
Click to expand...
Click to collapse
Cl4ncy said:
Can't he just use the rollback Images provided by ggow?
Must stay on 3.2.4. then though.
Click to expand...
Click to collapse
Nice find! I had seen that post (long ago) but the significance never set in for Safestrap v3 users with FireOS xx.3.2.4 in the stock slot. Even if not rocking SS it is probably easier (and definitely a lot safer) to install SS vs rolling up just to roll back or messing with build.prop.
The OTA block could still be a problem as the @ggow's procedure still involves Amazon's native update mechanism.
Edit: Disregard OTA comment as modified 3.2.4 goes on first and should restore OTA capability (more importantly the ability to detect and process FireOS bin files in the appropriate location).
I upgraded from 13.3.2.4 to 13.3.2.5 and edited build.prop, so now my version shows 13.3.0.9. I downloaded 13.3.1.0 rom from Amazon server. When updating I always received the following error message "Unable to complete update because the update file is not valid. Please try downloading the file again" (I tried downloading 13.3.1.0 at least 5 times, but none of the downloaded file works). I suspect that something goes wrong with the rom file on Amazon server.
Anybody can help direct me to a non-amazon site or upload your working file to somewhere I can download from?
Thank you very much.
Davey126 said:
Nice find! I had seen that post (long ago) but the significance never set in for Safestrap v3 users with FireOS xx.3.2.4 in the stock slot. Even if not rocking SS it is probably easier (and definitely a lot safer) to install SS vs rolling up just to roll back or messing with build.prop.
The OTA block could still be a problem as the @ggow's procedure still involves Amazon's native update mechanism.
Edit: Disregard OTA comment as modified 3.2.4 goes on first and should restore OTA capability (more importantly the ability to detect and process FireOS bin files in the appropriate location).
Click to expand...
Click to collapse
pquan2009 said:
I upgraded from 13.3.2.4 to 13.3.2.5 and edited build.prop, so now my version shows 13.3.0.9. I downloaded 13.3.1.0 rom from Amazon server. When updating I always received the following error message "Unable to complete update because the update file is not valid. Please try downloading the file again" (I tried downloading 13.3.1.0 at least 5 times, but none of the downloaded file works). I suspect that something goes wrong with the rom file on Amazon server.
Anybody can help direct me to a non-amazon site or upload your working file to somewhere I can download from?
Thank you very much.
Click to expand...
Click to collapse
AFAIK after upgrading to x.3.2.5(or 6) you cant use downgrading via editing build.prop anymore (thanks to Amazon), check this thread for more info.
IF you decide to take further actions PLEASE READ INSTRUCTIONS CAREFULLY, so far you are lucky you didnt brick your kindle.
jeryll said:
AFAIK after upgrading to x.3.2.5(or 6) you cant use downgrading via editing build.prop anymore (thanks to Amazon), check this thread for more info.
IF you decide to take further actions PLEASE READ INSTRUCTIONS CAREFULLY, so far you are lucky you didnt brick your kindle.
Click to expand...
Click to collapse
if i go this route which looks relatively easy do i end up deleting safestrap because i thought twrp doesnt work with it installed? and which safestrap do i install ss 3.72 ... download links are down l?
rbkelley89 said:
if i go this route which looks relatively easy do i end up deleting safestrap because i thought twrp doesnt work with it installed? and which safestrap do i install ss 3.72 ... download links are down l?
Click to expand...
Click to collapse
Assuming you are on 13.3.2.4 (must be that version) you need Safestrap v3.75 b02 for Thor (here). See Safestrap OP for additional information on installing/configuring Safestrap. Or follow part 1-2 of this guide. You do not need to create secondary slots as you will be overwriting FireOS in the Stock ROM Slot. This obviously dangerous. If something goes wrong you could be left with an unbootable device. Make a backup of your current environment from Safestrap recovery before flashing the rollback file. Note rolling back to 3.1.0 is a two step process. Be sure you understand these instructions and have the correct files. Ask questions if unsure.
After you have successfully rolled back to 3.1.0 you should uninstall safestrap before flashing native twrp, bumping your bootloader to 3.2.3 and then unlocking. Alternatively, you can work on bootloader unlocking first while Safestrap is installed which will offer more robust recovery capabilities should something go wrong in subsequent steps.
Davey126 said:
Assuming you are on 13.3.2.4 (must be that version) you need Safestrap v3.75 b02 for Thor (here). See Safestrap OP for additional information on installing/configuring Safestrap. Or follow part 1-2 of this guide. You do not need to create secondary slots as you will be overwriting FireOS in the Stock ROM Slot. This obviously dangerous. If something goes wrong you could be left with an unbootable device. Make a backup of your current environment from Safestrap recovery before flashing the rollback file. Note rolling back to 3.1.0 is a two step process. Be sure you understand these instructions and have the correct files. Ask questions if unsure.
After you have successfully rolled back to 3.1.0 you should uninstall safestrap before flashing native twrp, bumping your bootloader to 3.2.3 and then unlocking. Alternatively, you can work on bootloader unlocking first while Safestrap is installed which will offer more robust recovery capabilities should something go wrong in subsequent steps.
Click to expand...
Click to collapse
thank you so much for the walk through and linking everything i am initiating the process and now have safestrap and backup installed. going through with the rollback then i will start the unlock rocedure. update with any questions or issues i run into. thank you again!
quick thing i ran into before doing factory reset and rebooting into modified stock 3.2.4 it says to have the stock 3.1.0 files where can i find that file it wasn't linked in the rollback instruction or under the modified stock 3.2.4 zip from what i could see?
rbkelley89 said:
thank you so much for the walk through and linking everything i am initiating the process and now have safestrap and backup installed. going through with the rollback then i will start the unlock rocedure. update with any questions or issues i run into. thank you again!
quick thing i ran into before doing factory reset and rebooting into modified stock 3.2.4 it says to have the stock 3.1.0 files where can i find that file it wasn't linked in the rollback instruction or under the modified stock 3.2.4 zip from what i could see?
Click to expand...
Click to collapse
You can grab stock images here. Be absolutely certain you snag the correct one for your device. Verify md5=c49c0363de4d8dfa5c87c1bdb88aa2ba with ES FIle Explorer (long click the file and select 'properties' from the 'more' menu). Note you will loose root and OTA blocking. Be sure to stay off wifi. Use HDX Toolkit (requires usb tether to Windows PC) to root 3.1.0 and reblock OTA if needed.