Well. I've been reading as much as possible, and although my requirements are here/there, putting together and nailing down my specific needs have got me quite stuck.
My Current System:
Verizon (On Straight Talk) SCH-I545 , Android: 4.4.2
Build: VRUFNK1
Rooted , SafeStrap Installed (Also, running XPosed Framework, quite a bit of bloat and Verizon apps removed).
I want to upgrade to Stock Lollipop (Rooted). I have researched to my limits and my problem is primarily my loss of understanding of the various Builds and requirements. This is my only phone and I just want to assure to be quite sure before proceeding.
I do understand the answer to this is here, it just seems that it is somewhat fragmented and I can't seem to nail down the specifics I need to make it happen.
It seems that FlashFire and this thread:
http://forum.xda-developers.com/gal...-to-update-to-i545oc1-5-0-1-keeproot-t3096558
(I just realized that the ROM files here for use in Flashfire are now broken URL's), not sure where to find the proper files?
Do the trick? Flash the I545_OC1_Stock_Rooted_ROM_wNK4_BL Rom using FlashFire. (This link is now broken? New file location?) If I read correctly, it will take to the required NK4, from my NK1.....and put me right to Lollipop.....Done.
I've only ever used ODIN, so FlashFire is new to me. Just a few quick questions that I KNOW have really caused problems in the past, and just want to make sure I'll be ok:
1. Will the removal of tons of the Verizon Bloatware be an issue, or does it need to be wiped back to close to stock (Anything removed was on the XDA list of "Ok to remove KitKat files"
2. Should I Remove XPosed for the flash and put it back later if desired.
Am I missing anything? To be honest, it seems quite simple. I've flashed several phones and this almost seems too easy (A compliment).
Just a confirmation would be great. I think I've done the homework, but would really like some feedback before I pull the trigger.
I REALLY APPRECIATE THE HELP......THANKS.....
Here is a link to sign up as a tester of flashfire which once you are approved will allow you to download the application from this link as well.
https://play.google.com/apps/testing/eu.chainfire.flash
I will upload the file to my server and send you the link shortly.
ROM LINK: http://myowntoilet.com/dl/I545_OC1_Stock_Rooted_ROM_wNK4_BL.zip
An answer to your questions:
1. Any system apps you removed should not have an effect because the ROM which you are flashing has the basic Verizon bloatware pre-insatlled. You will have to delete them again after installing a new rom unless it is debloated/deodexed.
2. If I were you I would remove XPosed just to be safe as it may leave something behind which could cause problems. But you shouldn't have an issue if you leave it in before flashing.
Be very careful to follow the directions in FlashFire word for word, if you skip or miss any steps it could result in a soft-brick.
THANKS for the reply. Also, thank you for the ROM link. I read in much of the original flashing comments there were several WI-FI issues. Has that been repaired in this version of the ROM?
I did get FlashFire. There seems to be several versions of that floating around, just hopefully the latest should be fine.
I did have 1 other question. I believe I also read that after the flash, Safestrap will no longer work? Is this true? Should SafeStrap be removed prior to this process? (Although if something goes wrong, I like having that there to hopefully get back?). Is the latest version of SS compatible? Will it just fail to even come up if the flash is successful?
I've flashed many times, over the past years, but am no expert. I guess I'll ask, although I clearly understand the concept of soft-brick....In this particular case, any insight of what 'Could' happen and maybe what I could have prepared to fix? Shouldn't be an issue I would hope.
BOTTOM-LINE QUESTIONS:
1. Can you please verify this ROM def. has the WiFi issues worked out?
2. Status of SafeStrap after Flash?
THANKS SO MUCH FOR THE REPLY!
Any other thoughts, etc...greatly appreciated. (I see quite a few posts of people wanting to go BACK to 4.4.2 (where I am now) that gets me thinking also...lol...hmmm?
ALL the best and thanks again....
Matthew M. said:
Here is a link to sign up as a tester of flashfire which once you are approved will allow you to download the application from this link as well.
https://play.google.com/apps/testing/eu.chainfire.flash
I will upload the file to my server and send you the link shortly.
ROM LINK: http://myowntoilet.com/dl/I545_OC1_Stock_Rooted_ROM_wNK4_BL.zip
An answer to your questions:
1. Any system apps you removed should not have an effect because the ROM which you are flashing has the basic Verizon bloatware pre-insatlled. You will have to delete them again after installing a new rom unless it is debloated/deodexed.
2. If I were you I would remove XPosed just to be safe as it may leave something behind which could cause problems. But you shouldn't have an issue if you leave it in before flashing.
Be very careful to follow the directions in FlashFire word for word, if you skip or miss any steps it could result in a soft-brick.
Click to expand...
Click to collapse
I am unable to verify if the wifi issues are fixed or not, but you could just flash it anyway and then restore from a backup in odin. Safestrap will probably need to be reinstalled as you will flash recoveries when you do the update in flashfire.
The people who post about going back to 4.4.2 are not on NK4 but on OC1 which does not allow reverting to 4.4.2. NK4 could use the nc5flasher to then revert to 4.4.2 or even something like Hyperdrive.
Thank you. I'm pretty sure that I read in one of the original threads that the WiFi issues had been worked out. I'm just wanting to make sure this particular version of the ROM is the corrected one. You mentioned if it is broken, restore from a backup in ODIN, your referring to the original KitKat ROM.
I was a bit confused. I thought that this also took it all the way to OC1, which is why I was questioning SafeStrap? Could you please clarify when you mentioned flashing recoveries when the update is done in FlashFire?
So, this particular update takes it to NK4, with Lollipop....not OC1 ? I was def. a bit confused there.
Really appreciate the info. Just want to make sure I have it all in a row before I pull the trigger. According to all I've read and what you've posted, I think that I wouldn't have much issue. I'm just nervous about the WiFi. Guess, I'll need to track down the proper file/s to flash in ODIN if there is a problem.
If you happen to run across anything about this ROM and the WiFi, would appreciate the info. Just no rev numbers on the file, so bit of guessing I assume.
THANKS AGAIN FOR THE INFO........Little more research and I should be ready to roll....THANKS....
Matthew M. said:
I am unable to verify if the wifi issues are fixed or not, but you could just flash it anyway and then restore from a backup in odin. Safestrap will probably need to be reinstalled as you will flash recoveries when you do the update in flashfire.
The people who post about going back to 4.4.2 are not on NK4 but on OC1 which does not allow reverting to 4.4.2. NK4 could use the nc5flasher to then revert to 4.4.2 or even something like Hyperdrive.
Click to expand...
Click to collapse
This rom will put on 5.0.1 Lollipop but with the nk4 bootloader, not OC1. NK4 has safestrap capabilities. And yes i did mean restore to a stock nk4 rom if you had issues (via odin of course)
Sorry....Had a last thought. In the original procedure I read, it discusses flashing another file enabling tethering. I believe (?) that was after flashing the OC1 file, which I'm convinced your right about staying on NK4. Any idea about that? When I mentioned problems with WiFi, I think that was part of the issue, which they now worked out. Not sure if it's viable on the NK4 though?
Thanks again for all the help/advice with this. Just REALLY trying to make sure I understand it A-Z before I move.....THANKS.....
(Just went and checked, yep the tether flash is for the OC1, from what else I've read though, your right about the best move being to stay on the KK BL'er.)...
Related
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
I experienced spontaneous reboots, & I use Safestrap 3.65 & I noticed that SS was missing in the Stock slot. I'm rooted & running HyperDrive 10.2 & Android OS 4.2.2 - or was....
I d/l'ed SS3.65 & to be sure I used the app to remove the recovery & then reinstalled the recovery on the Stock side & rebooted & recreated slot 1 w/HyperDrive 10.2 via a nand backup.
However, I kept getting spontaneous reboots, so I tried to do a full factory reset on the Stock side & when I tried to reboot the only thing that shows is the "Custom" warning & it doesn't move from there.... I have to remove the battery to turn off the phone.
I did some homework & looking back at it, I shouldn't have done the full factory reset before removing the recovery...
I do NOT have nor do I know ADB, but I need to get back my S4 if possible, I would greatly appreciate any help.
I am in New York City, so if there are any locals that can help, but need to look at it; I can get around to the 5 boros.....
Thanks very much in advance, Oldwolf
If you know what your original build was you could use Odin to get back to stock.
Sent from my NCC-1701 using Tapatalk.
Riker, tnx so much for ur tip! I was on MI1, can I just Odin that?, or do I need the version that was 'native' to the phone.
Also, I need input on how to get into the mode needed for Odin to work- I forgot the button-press sequence… also, please tell me where to find the required driversto get my new PC (Win7) to 'see' the S4.
Unfortunately, most of my hacking b4 has been on the Moto platform; so I'm still 'Green' w/the Sammy stuff…
Thanks again! oldwolf
oldwolf613 said:
Riker, tnx so much for ur tip! I was on MI1, can I just Odin that?, or do I need the version that was 'native' to the phone.
Also, I need input on how to get into the mode needed for Odin to work- I forgot the button-press sequence… also, please tell me where to find the required driversto get my new PC (Win7) to 'see' the S4.
Unfortunately, most of my hacking b4 has been on the Moto platform; so I'm still 'Green' w/the Sammy stuff…
Thanks again! oldwolf
Click to expand...
Click to collapse
You should be able to recover easily. It's not a hard brick by all means.
First, follow this link http://forum.xda-developers.com/showthread.php?t=2301259 and donwload the MI1 odin file. It should come as a zip but you unzip it and then you get a .tar file.
Then, download odin 3.09. A simple google will give a link.
Then, put phone in download mode. From a power off state, hold home button+volume down+power button. To get it powered off, you may have to pull battery and reinsert. Plug in usb cable into cpu and phone.
Then in odin, leave everything the same, click AP, choose the mi1 tar file.
Run odin
Done! :good::good:
Richard, thanks so much for your clear steps. What about rooting once I get MI1 up & running? It feels funny; in the Moto world I wouldn't have to ask… but so far in the Sammy world I've only rooted & Odin'ed once a long while back…
Also, what about taking an OTA update?, from what I've seen, it is not a good idea b/c of tougher security fm Sammy- but I heard there is an NC5 image that is rootable & you can even roll back… anybody have any ideas?
I'm also considering a diff ROM, but suggestions would be welcome- I've been spending a lot of time on my PC…
thanks in advance to all, Oldwolf
To All, never mind about the re-rooting question. I didn't know the link in the prev answer provided guidance for this.
I really appreciate getting timely responses & people being willing to help me get into the Sammy side of hacking…
Custom ROM suggestions?
What is the feel about taking the OTA update once I have MI1 Stock - it seems that there are more updates for HyperDrive available for 4.3 or 4.4x, or even Lollipop- but t_ere were reports of probs w/diff things, Wifi I believe & now that VZW has enticed me to give up unlimited data (for a sweethevrt deal on unlimited talk & text) I can't afford yo be w/out wifi…
regards, Oldwolf
oldwolf613 said:
Richard, thanks so much for your clear steps. What about rooting once I get MI1 up & running? It feels funny; in the Moto world I wouldn't have to ask… but so far in the Sammy world I've only rooted & Odin'ed once a long while back…
Also, what about taking an OTA update?, from what I've seen, it is not a good idea b/c of tougher security fm Sammy- but I heard there is an NC5 image that is rootable & you can even roll back… anybody have any ideas?
I'm also considering a diff ROM, but suggestions would be welcome- I've been spending a lot of time on my PC…
thanks in advance to all, Oldwolf
Click to expand...
Click to collapse
My personal, non-richard, suggestion would be to odin to nc5, towelroot, get safestrap 3.75, then download either eclipse, hyperdrive or a safestrap compatible google play edition rom. This is because nc5 is simply a newer version and MI1 doesn't give you any special tweaks that nc5 doesn't have.
there are many threads around these forums discussing each step of the process that I've listed. Try searching for them first. I like to simply type in google " towelroot s4 xda" for example. If you can't find a thread that helps, i'll be happy to assist you.
p.s. I'm not richard.
Raymond, er, um, uh?!
Sorry about calling you that other name.... guess I was distracted... you know, w/my S4 sitting corrupted on the table & all.... & it looks like I gotta get more sleep.....
I noted in the thread you mentioned SafeStrap 3.75 & Towel Root, & a SS-compatible Google Play Edition Rom.... mine is a retail VZW S4, I'm guessing if you mentioned it that it'd be OK. BTW, I thought that Eclipse is no longer being developed for the S4... just older versions made for earlier versions of the Android OS.... via updates fm Eclipse's author...:laugh:
Also, do you know any issues related to Hyperdrive for NC5? I'd given up on updating b/c I heard about wifi issues & I must have wifi....
Also, can you go directly fm a soft-bricked MI1 to NC5 just thru Odin, or are there intermediate steps. I ask b/c I've seen postings in my email box w/forum updates - even if I haven't been involved in the forums... & someone posted a non-data-wiping image to go to NC5, but you had to be on M2 first....
Another point- I saw in a referred thread that being stuck on the Sammy logo means data corruption & it seems that I'd need a ready-for-Odin wiping image; do you have anything on that?
Anyway, thanks for the search tips, I haven't been good at internet searching, I guess that I will have those skills improved also...
Thanks again for the non-Richard help, Raymond- Oldwolf
oldwolf613 said:
Raymond, er, um, uh?!
Sorry about calling you that other name.... guess I was distracted... you know, w/my S4 sitting corrupted on the table & all.... & it looks like I gotta get more sleep.....
I noted in the thread you mentioned SafeStrap 3.75 & Towel Root, & a SS-compatible Google Play Edition Rom.... mine is a retail VZW S4, I'm guessing if you mentioned it that it'd be OK. BTW, I thought that Eclipse is no longer being developed for the S4... just older versions made for earlier versions of the Android OS.... via updates fm Eclipse's author...:laugh:
Also, do you know any issues related to Hyperdrive for NC5? I'd given up on updating b/c I heard about wifi issues & I must have wifi....
Also, can you go directly fm a soft-bricked MI1 to NC5 just thru Odin, or are there intermediate steps. I ask b/c I've seen postings in my email box w/forum updates - even if I haven't been involved in the forums... & someone posted a non-data-wiping image to go to NC5, but you had to be on M2 first....
Another point- I saw in a referred thread that being stuck on the Sammy logo means data corruption & it seems that I'd need a ready-for-Odin wiping image; do you have anything on that?
Anyway, thanks for the search tips, I haven't been good at internet searching, I guess that I will have those skills improved also...
Thanks again for the non-Richard help, Raymond- Oldwolf
Click to expand...
Click to collapse
Don't sweat the Richard thing! Haha, I'm just fooling around. But I still don't know where you got Richard from.
~Eclipse works very well for nc5 even though the last update was in June. Its still a perfectly good rom.
~If you set up everything correctly, Hyperdrive will work fine for you. No bugs for me.
~As long you can get to download mode, you're set for odin. You can always odin to a official new version, just not a older one.
Raymond, I'm on my old Razr = small scrn; but I'll be sure to give you official forum props for all of your help when I get back to my PC.
I do like HyperDrive, but once upon time I saw that some of the versions in earlier teens had probs w/wifi & that's crucial to me… I also missed screen rotation since HD 10.2 for viewing pix & reading text/books but it was stable… & I have to admit I was a little worried
about having to go back & forth recovering fm Sammy hacking errors as its still new to me… if I were rich I wouldn't care, but I have to update my PC as well as other expenses, so spending a lot on phones is not on my horizon.
I suppose your help will crank things up a notch for me, there's nothing like experience w/a more experienced person pointing you in the right direction.
Which version are of HD are you on?
Which version of safestrap is needed for NC5? If I can find an official image to flash, I may want to go directly there, but I vlso heard that newer OTAs fm Sammy are harder if not impossible to root & I like root too!
BTW, your demeanor & willingness to help twigged me to the fact that you weren't all that upset at the slip w/your name, & I actually got a laugh out of how you reacted.
All the best, Oldwolf
Raymond,
Great news! Success on the first try.... I did have some minor blips, but all seems to be working. I tested first via wifi & then contacted VZW to re-attach my service back to my S4 & so far so good.
BTW, since I had a nand backup of MI1, I just restored that version via Odin b/c I wasn't sure if a nand made on an older version of the Android OS would work on a newer version of the OS & I needed to be back up & running quickly.
Of course, if using a nand backup made on MI1 can be restored to a device running NC5... I now feel comfortable about going ahead based on this experience you helped me to gain & I would just Odin NC5 & restore fm my old MI1-based nand b/u set -
I also anticipate that there might be a problem if the nand backup was made on SafeStrap 3.65 & one wanted to restore it on a device running SS 3.75....
One of the blips was that after running the tar.md5 for DeLaVega root, the last 2 items of that driver installation failed; but root worked & so far so good.
I am very excited to be back on the S4, & you can know that much more than the forum thanks I put on your post here, I am appreciative.
All the best, Oldwolf
I am on 3.72 safestrap with TWRP 2.7.0.0. My system version is 13.3.1.0. I have noticed intermittent wifi problem. Sometime it drops connection for no reason, while my other devices keeps connected with no disconnection. Sometimes wifi got turned off for no reason, then back on moment later. Does anyone know what's going on? Is there any fix? Thanks.
Uhm, I do not believe safestrap is compatible with 13.3.1.0. That could be the issue.
Sent from my KFTHWI using Tapatalk
That particular firmware was always well-known for erratic Wi-Fi behavior.. My advice if you are actually on that firmware . Is to unlock your boot loader and flash
Newer firmware version . That way with an unlocked Loader we can flash any modified update and assume the benefits without being locked . You're then able to revert back to any firmware that you preferred . Or flash and android ASOP if you run out of interest in your Amazon account .
I personally have not run the actual unlock on my 7 inch or -8.9 . But my 7 inch is running the modified recovery that bypasses the boot loader checks .http://forum.xda-developers.com/kindle-fire-hdx/development/recovery-twrp-2-8-1-0-thor-t2986004 and then somewhere in there he actually has a stock 4.5.2 stock img that can be flashed in your new recovery . That is what I am running with gapps installed and seems to run quite smoothly with no Wi-Fi drops
Why are you posting this question when issues with your current config (including wifi problems) and paths forward (plural) have been posted here: http://forum.xda-developers.com/showpost.php?p=59741324&postcount=105
Come on mate, stop wasting people's time. Update or accept the limitations of your config as-is.
Davey126 said:
Why are you posting this question when issues with your current config (including wifi problems) and paths forward (plural) have been posted here: http://forum.xda-developers.com/showpost.php?p=59741324&postcount=105
Come on mate, stop wasting people's time. Update or accept the limitations of your config as-is.
Click to expand...
Click to collapse
Davey, I really appreciate your help in the Nexus rom thread. I respect your expertise and willingness to help other people. But this OP, if you have read it, is asking for a possible fix for the wifi problem of 3.1.0. It has nothing to do with Nexus rom. So i think it's appropriate to ask seperately.
jimyv said:
That particular firmware was always well-known for erratic Wi-Fi behavior.. My advice if you are actually on that firmware . Is to unlock your boot loader and flash
Newer firmware version . That way with an unlocked Loader we can flash any modified update and assume the benefits without being locked . You're then able to revert back to any firmware that you preferred . Or flash and android ASOP if you run out of interest in your Amazon account .
I personally have not run the actual unlock on my 7 inch or -8.9 . But my 7 inch is running the modified recovery that bypasses the boot loader checks .http://forum.xda-developers.com/kindle-fire-hdx/development/recovery-twrp-2-8-1-0-thor-t2986004 and then somewhere in there he actually has a stock 4.5.2 stock img that can be flashed in your new recovery . That is what I am running with gapps installed and seems to run quite smoothly with no Wi-Fi drops
Click to expand...
Click to collapse
Thanks, jimyv. It looks like there isn't a fix for the wifi problem if i stay with 3.1.0. Thanks for pointing me to the TWRP thread. My further qurstions will be asked in the TWRP thread.
yichen382 said:
Davey, I really appreciate your help in the Nexus rom thread. I respect your expertise and willingness to help other people. But this OP, if you have read it, is asking for a possible fix for the wifi problem of 3.1.0. It has nothing to do with Nexus rom. So i think it's appropriate to ask seperately.
Click to expand...
Click to collapse
@yichen, I appreciate your thoughtful response and apologize for the gruff post. I did read the OP but failed to explain the common roots behind your WiFi issue. In most cases the low level interface (hw drivers; binaries) remain the same regardless of which rom you are running. They are supplied by Amazon and are consistent with the base firmware level on your device. Sometimes code from other releases can be substituted and the really talented/adventurous developer may attempt to modify if source is available. It this case the easiest/best solution is to upgrade the base firmware as Amazon fixed many of the problems in 3.2.x and made further refinements in 3.2.5/3.2.6 . Hope that helps.
Thanks Davey. As always, your post is informational and easy to understand. You are the best.
Finally, I am able to get away from the buggy 3.1.0 stock firmware and now I am running CM11. Much thanks to Davey who helped me greatly along the way, also jimvy who clarified things for me. I want share my steps so if anyone in similar situation can take a reference:
1. Deleted slots in safestrap. Leave only stock slot.
2. Uninstalled safestrap in safestrap app.
3. Flahed twrp 2.8.5 using Flashify.
4. Upgraded bootloader to 3.2.3 in twrp.
5. Full wipe in twrp.
6. Flash CM11.
Now i am sitting comfortably at 3.2.3 which is just below 3.2.4. Thank you again Davey. People like you made this forum so great.
yichen382 said:
Finally, I am able to get away from the buggy 3.1.0 stock firmware and now I am running CM11. Much thanks to Davey who helped me greatly along the way, also jimvy who clarified things for me. I want share my steps so if anyone in similar situation can take a reference:
1. Deleted slots in safestrap. Leave only stock slot.
2. Uninstalled safestrap in safestrap app.
3. Flahed twrp 2.8.5 using Flashify.
4. Upgraded bootloader to 3.2.3 in twrp.
5. Full wipe in twrp.
6. Flash CM11.
Now i am sitting comfortably at 3.2.3 which is just below 3.2.4. Thank you again Davey. People like you made this forum so great.
Click to expand...
Click to collapse
Glad all is well! As for assistance, the participants in this forum are great. Much of what you read are the aggregated outputs from small number of talented developers and average users like you who are willing to share their experiences. That's how 'stuff' gets done.
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.
I didn't think this warranted a development thread at this point, Mods may disagree and move it. Since a few people, myself included, need some TouchWiz features and want something closer to a stock rom than Jasmine but debloated, deodexed with the Verizon wifi tether provisioning disabled, I threw this together. I'll try to answer any questions and fix any issues that pop up but I cant make any promises due to work and other projects. If I do move forward with anything I may try to port the stock Verizon Note 4/5, but that's getting ahead of myself.
Now the usual warning about your warranty being voided (as if any Note 3s are under warranty and you didn't void it rooting/flashing recovery) and me not being responsible for you bricking your device because I was stoned when I packaged this.
Download the rom here.
So far the only changes to the stock OF1 are:
Deodexed
Moderatly debloated
Wifi tether provisioning disabled
Start up sound disabled
Rooted*
Busybox added*
*SuperSu and Busybox packages are installed during rom installation.
A list of debloated files can be found here.
Coming soon
Some files were left because they are too integrated into TouchWiz. I don't want people confused by orphaned menu items or get FCs. Some stuff I left because people I know use them. If you want anything back you'll have to get it yourself for now, sorry. I'm open to suggestions on stuff to keep and stuff to remove, but I'll want a good description of their functions before I remove anything. I'm funny about not deleting stuff I don't know what it does.
For those looking for Xposed, I'm using the latest Snapdragon requestConcurrentGC version from here.
Flashing instructions are pretty simple. Boot to TWRP, make a backup, wipe system/data/dalvik/cache, flash the rom and reboot system.
All thanks go to the Yemen rooters and @beaups and @ryanbg for liberating our devices.
thanks i tried it out and its working great! however one of the apps i like is S-Note and you debloated it :/ along with galaxy store. which i cannot find a download source for either, and its needed to reinstall s-note. anyway its a crucial app for the S-pen launcher and s-pen features.
if you could share the apks or upload a full but deodexed superSu/busybox version of this Rom it'd be a real winner.
also im not sure if its just me but i noticed the task manager is a little strange and is missing the ram clear button. ill take a screen shot and upload later
doombuger said:
if you could share the apks or upload a full but deodexed superSu/busybox version of this Rom it'd be a real winner.
Click to expand...
Click to collapse
All of the stock apps are in the system.img files in the Stock Odin tar bundles (available from sammobile.com for instance)
The only trick to getting them out of there is that those (system.img) image files are "sparse" ext4 files. The Android development environment has a tool called "simg2img" which allows you to create an uncompressed image file, which can then be mounted as an ext4 filesytem (loopback mount), and you can browse through there and copy out anything you want.
All of this is more convenient to do in a Linux environment (get yourself VirtualBox and install Ubuntu), but there are workarounds using Windows too, and there are even tutorials here on XDA on how to do this both ways. (Use searches for "sparse image" or "simg2img")
An even easier way is to simply pull them out of TWRP backup files of your rooted-stock ROMs; those "system.ext4.win00x" are just tar files. Heck, you could probably even use 7-zip for that.
You do make backups, right?
Ask your devs to do things that are interesting for the dev and difficult for almost any anybody else to do; not the simple stuff like "go get me some freely available files".
as some people like the stock image, you should do a non-debloated version, like beans did for 4.4.2 NC2/4: http://forum.xda-developers.com/showthread.php?t=2787627 Its just a minor thing, and i can add those apps back in.
How would i enable the startup sound that you disabled?
I'm running the deodexed version of NC4 (with an NC2 bootloader) that i linked above, and finally want to upgrade. I'm assuming that safestrap (which is currently installed) isn't compatible, so do have a link for a version of TWRP that is compatible?
also, can i upgrade from NC4 (with an NC2 bootloader) directly? or is there a step in between that i should do first?
Morlok8k said:
as some people like the stock image, you should do a non-debloated version, like beans did for 4.4.2 NC2/4: http://forum.xda-developers.com/showthread.php?t=2787627 Its just a minor thing, and i can add those apps back in.
How would i enable the startup sound that you disabled?
I'm running the deodexed version of NC4 (with an NC2 bootloader) that i linked above, and finally want to upgrade. I'm assuming that safestrap (which is currently installed) isn't compatible, so do have a link for a version of TWRP that is compatible?
also, can i upgrade from NC4 (with an NC2 bootloader) directly? or is there a step in between that i should do first?
Click to expand...
Click to collapse
i updated to of1 then rooted and bootloader unlocked then used flashify to flash recovery (back up stock recovery if u like) then no more safe strap or worries. but to each their own.
Very cool, thank you!
---------- Post added at 11:34 PM ---------- Previous post was at 11:33 PM ----------
njdan30 said:
i updated to of1 then rooted and bootloader unlocked then used flashify to flash recovery (back up stock recovery if u like) then no more safe strap or worries. but to each their own.
Click to expand...
Click to collapse
How did you bootloader unlock after rooted? Were you able to install custom recovery? If so, do you mind sharing how you did that as well?
Thank you!!
Neo3D said:
Very cool, thank you!
---------- Post added at 11:34 PM ---------- Previous post was at 11:33 PM ----------
How did you bootloader unlock after rooted? Were you able to install custom recovery? If so, do you mind sharing how you did that as well?
Thank you!!
Click to expand...
Click to collapse
yes you need to root 1st in order to get bootloader unlocked then head to play store for flashify the take the 1st(newest recovery)and thats it.check the yemen root http://forum.xda-developers.com/ver...b6-of1-n900v-note-3-verizon-oneclick-t3333569 for of1 use that then the retail to dev unlock and enjoy,for unlock i did the adb method but think theres a 1 click unlock now also http://forum.xda-developers.com/ver...l/official-note-3-verizon-bootloader-t3359370
Problems with data
I appreciate all of your hard work. I do have a question though. Every single 5.0 and newer rom I have tried I have problems getting my data to work reliably. I get 4G after reboot but as soon as I send/receive a SMS message it reverts to 3g until the next reboot. This was a clean install and I've also tried reinstalling sim, done factory reset, cleared all data, everything under the sun I can think of. Nobody else seems to have this problem. Any ideas? Other than that this is exactly what I'm looking for.
May I ask somebody create a .tar version to use with odin.
I has no custom recovery .
Tried peazip software to convert .zip to .tar but odin always hangs when i use file
Long time first boot. thoght i made a brick Thanks mate
Quick question. I have kit Kat 4.4.2 with safe strap on mine. How would I be able to upgrade to this?
nitroevo said:
Quick question. I have kit Kat 4.4.2 with safe strap on mine. How would I be able to upgrade to this?
Click to expand...
Click to collapse
I am also looking for advice. My Note 3 is in a similar position with NC2 and Baja ROM in the stock slot of safestrap.