So following Davey126's advice, I started looking into doing a rollback on my apollo 3.2.5. I managed to get the play store up and running after some work, and grabbed the latest prop editor following the instructions in http://forum.xda-developers.com/showthread.php?t=2782159 So far so good. I then edited the four lines in question, and allowed the device to reboot.
The changes didn't seem to take. After the reboot I ended up on the same version as where I started, and the four lines I changed were back to their unedited versions. Since I have run into a problem with r/w permissions before, I suspect I'm missing them here as well - but I haven't seen the thread/entry on how to change those. Any help would be appreciated.
If, those aren't the issue, then I'm lost again.
begalund said:
So following Davey126's advice, I started looking into doing a rollback on my apollo 3.2.5. I managed to get the play store up and running after some work, and grabbed the latest prop editor following the instructions in http://forum.xda-developers.com/showthread.php?t=2782159 So far so good. I then edited the four lines in question, and allowed the device to reboot.
The changes didn't seem to take. After the reboot I ended up on the same version as where I started, and the four lines I changed were back to their unedited versions. Since I have run into a problem with r/w permissions before, I suspect I'm missing them here as well - but I haven't seen the thread/entry on how to change those. Any help would be appreciated.
If, those aren't the issue, then I'm lost again.
Click to expand...
Click to collapse
Stop!! You are following the wrong procedure and could brick your device! Don't reboot again. I will post further info shortly (on a call at the moment...).
EDIT: Sorry for the earlier drama; you were headed for a cliff ...
Recheck the guide (post #1) from the thread you linked. Note there are two sections: One for devices below 3.2.5 and a second for 3.2.5-3.26. You want the second section. There is no need to mess with build prop. You should immediately restore that file to its previous state (hopefully you have/made a backup). Then follow the rest of the instructions. Again, sorry for sounding like an alarmist worry wort. A quick check of the forums will surface many hdx carcases in the sad hands of those who didn't follow instructions or made simple mistakes (we all make mistakes).
Davey126 said:
Stop!! You are following the wrong procedure and could brick your device! Don't reboot again. I will post further info shortly (on a call at the moment...).
EDIT: Sorry for the earlier drama; you were headed for a cliff ...
Recheck the guide (post #1) from the thread you linked. Note there are two sections: One for devices below 3.2.5 and a second for 3.2.5-3.26. You want the second section. There is no need to mess with build prop. You should immediately restore that file to its previous state (hopefully you have/made a backup). Then follow the rest of the instructions. Again, sorry for sounding like an alarmist worry wort. A quick check of the forums will surface many hdx carcases in the sad hands of those who didn't follow instructions or made simple mistakes (we all make mistakes).
Click to expand...
Click to collapse
No worries!
1. Yes, I had a backup.
2. Nothing got broken, so everything is peachy.
3. The way that post is written, there is absolutely no easy way to tell (for the average user) that you still don't edit the file with build prop. All it appears is that you need a different roll back file for 3.2.5 and 3.2.6 variants instead of the earlier versions.
Someone should likely edit that post - or at least add something to it to make it more clear. I know I read every entry in that thread and I never caught anything that told me "hey, you are on one of these two versions. Skip the build prop step and just push the update. it'll work fine from there."
However, I thank you for the added information. I'll give it a whirl and see if that works. It would be nice to get beyond at least point C so I can get to the steps I want to do. I keep getting stuck at the point just before where things get nice.
begalund said:
No worries!
Nothing got broken, so everything is peachy.
Click to expand...
Click to collapse
Glad nothing got busted!
begalund said:
Someone should likely edit that post - or at least add something to it to make it more clear. I know I read every entry in that thread and I never caught anything that told me "hey, you are on one of these two versions. Skip the build prop step and just push the update. it'll work fine from there."
Click to expand...
Click to collapse
It's an old post created before 3.2.5+ was released. I do not know if the OP is still around. As many others have commented the hdx forums are generally a mess (with a few notable exceptions) as the landscape is continually changing. No one has the time/energy to create and validate step-by-step guides given the number of permutations/combinations and high risk of bad outcomes given a touchy device with limited recovery options...especially for those who can't install twrp and/or unlock their bootloader.
Note to newbies: Many tinkerers come to these forums thinking all the cautions are the byproduct of excessive hand wringers blowing smoke out of a certain orifice. Hey, if I create a brick I'll just whip out my magical fastboot cable, arsenal of fastboot commands and make everything right again. Err, no. Fastboot cables don't work on the HDX nor to most other recovery techniques. Tread carefully...respect the kindle. Rewards will come soon enough.
Hey, already pushed the thank you, for all of your help, but I've got one more fundamental question that might seem kind of stupid, but what exactly does this mean?
"4. Put "update-kindle-1X.3.1.0_user_310079820.bin" in SAME folder,
. . . . .
7. put update-kindle-1X.3.1.0_user_310079820.bin" in internal storage."
I skipped steps 5 and 6, because they make sense to me. But step 4 loses me. which "same" folder? None of the previous steps mention anything about a folder where anything is being stored. Likely this is referring back to that same previous post you referenced above.
I have no trouble with step 7 - that makes sense - but I'm suddenly worried about this mysterious step 4, especially since "SAME" is in all caps.
begalund said:
Hey, already pushed the thank you, for all of your help, but I've got one more fundamental question that might seem kind of stupid, but what exactly does this mean?
"4. Put "update-kindle-1X.3.1.0_user_310079820.bin" in SAME folder,
. . . . .
7. put update-kindle-1X.3.1.0_user_310079820.bin" in internal storage."
I skipped steps 5 and 6, because they make sense to me. But step 4 loses me. which "same" folder? None of the previous steps mention anything about a folder where anything is being stored. Likely this is referring back to that same previous post you referenced above.
I have no trouble with step 7 - that makes sense - but I'm suddenly worried about this mysterious step 4, especially since "SAME" is in all caps.
Click to expand...
Click to collapse
Tanks for the thanks. As a new comer I struggled a bit and got help from some kind souls in these forums. Giving back ...
It is a tethered operation as you probably gathered. Step 4 means you need to put the .bin file in the same folder on Windows where install.bat lives. If you edit the batch file you'll see it generates a signed flashable image from the bin file and then issues a bunch of adb commands on your behalf. For Step 7 copy the bin file to root (not sdcard) on your hdx. Then reboot.
Footnotes:
- when you download the batch file be sure to use the blue "download now" button. Filename should be "rollback.zip" .The orange button yields an executable called "rollback.zip.exe". Probably fine but since I can't see into it can't tell for sure. Also, make sure to download the file appropriate for your device (7"/Thor or 8.9"/Apollo).
- be sure to immediately disable wifi after performing the update; otherwise Amazon may push a nasty update of their own. As a precaution I would advise deleting all existing wifi profiles and make sure you are not within range of an open hotspot. Don't want the Kindle to auto connect and update while you are sleeping.
- I would strongly recommend flashing twrp immediately after, test and backup of you stock rom from within twrp. Leave the image on your kindle if you have room.
- Once everything is working to your satisfaction flash the nexus rom (v2.0.5) and optionally the 3.2.3 bootloader update as described in earlier posts. Read up on any caveats.
- (optional) Unlock your bootloader. This not necessary to run Nexus and CM11 but is for some CM12 builds. An unlocked bootloader also opens additional recovery options should you loose twrp. That said, unlocking the bootloader is not for the faint of heart and carries its own set of risks.
Davey126 said:
For Step 7 copy the bin file to root (not sdcard) on your hdx. Then reboot.
- be sure to immediately disable wifi after performing the update; otherwise Amazon may push a nasty update of their own. As a precaution I would advise deleting all existing wifi profiles and make sure you are not within range of an open hotspot. Don't want the Kindle to auto connect and update while you are sleeping.
Click to expand...
Click to collapse
Okay. New headaches.
First part of the rollback happened. I'm now on 14.3.0.0. That worked okay. I grabbed the 14.3.1.0 update and loaded it on but then nothing happened. No further updates.
At this point I figure 1 of 3 things happened. Either:
A. I put it in the wrong place - I stuck it in Internal Storage (/storage/emulated/0), I would move it to either / or /root, but I can't - "no space available" error when I attempt to move it via es file explorer
B. I could keep turning OTA off and on and hope it eventually takes, but how many times exactly?
or C. I'm missing something with wireless needing to be on (or off but in some weird mode) or whatever. I'm just worried about having an automatic update to another newer version that I can't fix.
So what am I missing?
begalund said:
Okay. New headaches.
First part of the rollback happened. I'm now on 14.3.0.0. That worked okay. I grabbed the 14.3.1.0 update and loaded it on but then nothing happened. No further updates.
At this point I figure 1 of 3 things happened. Either:
A. I put it in the wrong place - I stuck it in Internal Storage (/storage/emulated/0), I would move it to either / or /root, but I can't - "no space available" error when I attempt to move it via es file explorer
B. I could keep turning OTA off and on and hope it eventually takes, but how many times exactly?
or C. I'm missing something with wireless needing to be on (or off but in some weird mode) or whatever. I'm just worried about having an automatic update to another newer version that I can't fix.
So what am I missing?
Click to expand...
Click to collapse
Hum. Everything seems ok. Bin file is in the correct location (/storage/emulated/0). Make sure OTA is enabled using the same tool/technique you originally used to disable (there are several methods) and reboot. Some posters claim they had to toggle it on/off a few times. While my device recognized the update fairly quickly (minutes) others mentioned it took a while. Keep checking settings->device->system updates. Some say the update did not take until WiFi was disabled. Might want to try that first. I recall seeing something about airplane mode but can't immediately find the post.
btw, you can mitigate the automatic update risk by making sure there are NO WiFi profiles on your device and you are not in range of any open hotspots (if possible).
Well, still no dice.
I've reset OTA (cycled off then on) and rebooted about 10 times now. I've also attempted various options of wifi on, off, and in airplane mode. The only thing I haven't done is connected to an actual network and pushed the check now button (I'm not quite that dumb). The lovely device just keeps taunting me with 14.3.0.0 and refusing to do anything else.
Very frustrating.
I'm gonna head for bed and look at it fresh sometime tomorrow. Maybe it will miraculously fix itself while I ignore it (but I really doubt that will be the case).
begalund said:
Well, still no dice.
I've reset OTA (cycled off then on) and rebooted about 10 times now. I've also attempted various options of wifi on, off, and in airplane mode. The only thing I haven't done is connected to an actual network and pushed the check now button (I'm not quite that dumb). The lovely device just keeps taunting me with 14.3.0.0 and refusing to do anything else.
Very frustrating.
I'm gonna head for bed and look at it fresh sometime tomorrow. Maybe it will miraculously fix itself while I ignore it (but I really doubt that will be the case).
Click to expand...
Click to collapse
Sorry for your troubles. One or more of the following are likely culprits:
- OTA capability not fully restored (try HDX Toolkit if you haven't already)
- ensure the .bin file name matches exactly and is located in the proper folder
- Verify .bin MD5 on the device (use a tool like hash droid) MD5=0F2BC5278C057E7A6B4823B0F68D0727
- use notepad to view the batch file; make sure all the files made it to respective directories on your HDX
- repeat the preliminary steps with your device tethered
If everything checks out then the real fun begins. You'll need to comb threads for others who have experienced a similar problem. You are looking for some morsel that may provide a path forward. Frustrating - yes! One reason there are not step-by-step tutorials as everyone's device seems to respond differently; too many uncontrolled variables. Not sure anyone really knows what all those variables are.
Remain calm and don't do anything crazy. Be wary of fixes that involve manually modifying build.prop or flashing via adb. Both are legitimate tools/techniques in skilled hands. Used incorrectly they can (and usually do) yield a brick.
So I was attempting to write a nice long message about how I was using the right toolkit, and how to check on OTA messages to verify whether it was performing correctly, when all of a sudden I look down at my device and it suddenly stopped being obstinate.
No idea what I did. It just started playing nice.
14.3.1.0 now installed. I'm going to go get a drink.
begalund said:
So I was attempting to write a nice long message about how I was using the right toolkit, and how to check on OTA messages to verify whether it was performing correctly, when all of a sudden I look down at my device and it suddenly stopped being obstinate.
No idea what I did. It just started playing nice.
14.3.1.0 now installed. I'm going to go get a drink.
Click to expand...
Click to collapse
Funny how some devices take their time processing update files. Would love to know the criteria for checking and if processing can be manually triggered. Don't forget to disable OTA or keep WiFi off as long as there is a version of stock os in the system partition. One you load nexus or some other rom OTA worries will be history.
Edit: Enjoy that drink; you earned it
So I thought I would just report back with a final update as of 20 minutes ago:
Finally got the device rolled forward to 14.3.2.4
Re-rooted
Re-safestrapped
Backedup
Partitioned
And Nexus 4.2.2 running perfectly fine in Rom slot 1.
I'll go add a few apps later to personalize and make it wife-friendly. Thanks to everyone here and especially Davey126 for the patient assistance. I'll probably be back at some point in the near future to figure out the next step, but for now I'm gonna go enjoy an ad-free device for awhile.
begalund said:
So I thought I would just report back with a final update as of 20 minutes ago:
Finally got the device rolled forward to 14.3.2.4
Re-rooted
Re-safestrapped
Backedup
Partitioned
And Nexus 4.2.2 running perfectly fine in Rom slot 1.
I'll go add a few apps later to personalize and make it wife-friendly. Thanks to everyone here and especially Davey126 for the patient assistance. I'll probably be back at some point in the near future to figure out the next step, but for now I'm gonna go enjoy an ad-free device for awhile.
Click to expand...
Click to collapse
Glad to hear you are back in business! An interesting choice to upgrade to 3.2.4 vs 3.2.3. Native twrp requires 3.2.3 or lower so no CM11/12 or bootloader unlock. I do not believe there are meaningful differences between Nexus v1.0.1 (safestrap edition) and v2.0.5 (native) so nothing lost at this point. Plus you still have access to stock with a simple reboot which can be an advantage. But it is unlikely other roms will be adapted to run under safestrap. Btw, downgrading from 3.2.4 is a bit tricker than 3.2.5/3.2.6. You many need to upgrade first.
Don't forget to reblock OTA if you haven't already. Enjoy your 'new' device
Davey126 said:
Glad to hear you are back in business! An interesting choice to upgrade to 3.2.4 vs 3.2.3. Native twrp requires 3.2.3 or lower so no CM11/12 or bootloader unlock. I do not believe there are meaningful differences between Nexus v1.0.1 (safestrap edition) and v2.0.5 (native) so nothing lost at this point. Plus you still have access to stock with a simple reboot which can be an advantage. But it is unlikely other roms will be adapted to run under safestrap. Btw, downgrading from 3.2.4 is a bit tricker than 3.2.5/3.2.6. You many need to upgrade first.
Click to expand...
Click to collapse
So it turns out I may have done myself a big favor by going the safe route. I'm not positive of course since I haven't tried the "non-safe route", but I'm guessing I'm right. I recently obtained a bluetooth KB to use with the fixed device - specifically the bear motion KB/case - cause I figured if I only spent $40 on the tablet, I'm not going to spend more than that on the KB. Since one of the purposes for this is to allow me to use it for remote work options, I wanted a better KB than pulling up the native one - especially if I'm running teamviewer, the screen is small enough as it is.
In any event, the Nexus SS edition has troubles pairing up with the KB (already logged a bug report on it), so I'm probably going to have to swap over to a different rom. Since I've already been through the process, and I've seen your updated posts in another thread, I'll just upgrade, rollback, and follow the twrp, cm11/12 route instead.
I just need to check and see if anyone has used this combination of hardware with another rom and made them work out.
begalund said:
So it turns out I may have done myself a big favor by going the safe route. I'm not positive of course since I haven't tried the "non-safe route", but I'm guessing I'm right. I recently obtained a bluetooth KB to use with the fixed device - specifically the bear motion KB/case - cause I figured if I only spent $40 on the tablet, I'm not going to spend more than that on the KB. Since one of the purposes for this is to allow me to use it for remote work options, I wanted a better KB than pulling up the native one - especially if I'm running teamviewer, the screen is small enough as it is.
In any event, the Nexus SS edition has troubles pairing up with the KB (already logged a bug report on it), so I'm probably going to have to swap over to a different rom. Since I've already been through the process, and I've seen your updated posts in another thread, I'll just upgrade, rollback, and follow the twrp, cm11/12 route instead.
I just need to check and see if anyone has used this combination of hardware with another rom and made them work out.
Click to expand...
Click to collapse
Have you tried stock Fire OS yet? Should be an easy test given you are on Safestrap with (presumably) stock in the base slot. That would help rule out any native compatibility issues.
If you opt for a different rom might try the native version of Nexus first (v2.0.5) after you get twrp loaded as it's an easy test. Possible (albeit unlikely) Safestrap is interfering. Of the two CM varients CM11 would see the better choice today as the latest CM12 build still seems to have some issues with BT. As always, watch the forums for updates.
Davey126 said:
Have you tried stock Fire OS yet? Should be an easy test given you are on Safestrap with (presumably) stock in the base slot. That would help rule out any native compatibility issues.
If you opt for a different rom might try the native version of Nexus first (v2.0.5) after you get twrp loaded as it's an easy test. Possible (albeit unlikely) Safestrap is interfering. Of the two CM varients CM11 would see the better choice today as the latest CM12 build still seems to have some issues with BT. As always, watch the forums for updates.
Click to expand...
Click to collapse
Second thing I did. Rebooted into the stock rom and retested. KB works fine on that slot. So it doesn't appear to be a safestrap issue - more than likely a problem with the SS version of Nexus - else it might be a Nexus compatibility issue with the KB itself.
I haven't had time to do any more playing with the tablet - Wife's birthday, but I'll retest once I know more. Should probably make a new thread however....
begalund said:
So it doesn't appear to be a safestrap issue - more than likely a problem with the SS version of Nexus - else it might be a Nexus compatibility issue with the KB itself.
Click to expand...
Click to collapse
Well, that's verified. :good: Although on the plus side, I did have a completely problem free rollback to 14.3.1.0, got twrp installed, and then cycled through a couple of the roms available looking for one that worked with the KB. Again, much thanks for all the assistance - including the assistance you lent to another user in the main thread - it helped immensely with getting twrp working on the first attempt. :victory:
Native Nexus - no go. It had the same issue. Eventually found it, but never recognized any key strokes. :crying:
Swapped to CM11 and at first it appeared to not work either (more on this), as the rom never got past the boot stage, so I bootloaded and realized I made an error (forgot to mount). Then the rom loaded but everything crashed on opening (rebooted again, wiped and reinstalled) now everything worked but the KB - I'll come back to this one.
Was about to try magic beans when I read something about the KB being "finicky" - so I swapped back to native nexus and played with the BT a bit. after 20 minutes of trying it never synced up, so I went back to CM11.
Turns out it does actually recognize it. You need to turn the KB on, then press its BT pair button, and then have the system search for new BT devices (in that order). It still has an issue where certain apps like titanium backup (or anything else that makes root calls) cause the system's BT to drop the KB - but it does find it and it works just fine 90% of the time. And when it does drop, it can be reset pretty easily in settings by removing the pairing and going through those steps again. You'll also have to do this every time the system is first turned on and you want to use it. A bit aggravating, but better than not having it any functionality or needing to swap back to FireOS.
Plus it appears that CM11 works just slightly better than nexus for the apps I tend to use anyway - so that's another bonus.
begalund said:
Plus it appears that CM11 works just slightly better than nexus for the apps I tend to use anyway - so that's another bonus.
Click to expand...
Click to collapse
Thanks for posting your BT findings with various HDX roms (below). Helpful to others who may be experiencing similar issues. I agree Nexus (based on Jellybean) is getting a bit long in the tooth. I stick with it given overall stability for the apps and and devices that I use including a AmazonBasics keyboard which pairs fine. I have been monitoring the HDX CM11/12 threads and will likely move there as the few remaining issues of concern to me are hammered out. Been running CM11 on another device (HD) for 15+ months; great rom that brought new life to an aging device.
Related
Hi,
I have finally received my replacement watch. (yay)
I was so discouraged after waiting 3 months to get it that I sort of fell out of the loop on what's been going on in the community.
The watch I got has the following:
(when I got to OTA) - truesmart-20140801-1006
Under About:
Android 4.2.2
Kernel - 3.4.5
OUI 2.1
Build - Omate_Truesmart_20140801.10312_v2.0
So,
Do I need to update anything?
How do I ROOT this version as what I did with my previous watch doesn't seem to work anymore.
Any suggestions for next steps or apps/things to load?
I tried going through all the old threads but there seems (to me at least) a lot of info that is no longer relavant or doesn't pertain to what I have now... I am just trying to make sure I am on the right path as I don't want to screw this watch up like the last one.
Much appreciated.
D.
what I would do
**** DO THE LAST PART OF THIS POST FIRST ***
Build - Omate_Truesmart_20140801.10312_v2.0
### First time I have seen this date on a firmware
Do I need to update anything?
### Look like you have newest firmware already
How do I ROOT this version as what I did with my previous watch doesn't seem to work anymore.
### Not sure since you have newer firmware but if it is like older versions you are sorta rooted now. If this true then all you need to do is push SU and BusyBox via ADB and set permissions. Then install SuperSU or one of the other GUI level root managers.
Any suggestions for next steps or apps/things to load?
### My touchscreen is bad and my watch is unusable but in the couple weeks I got to play with it I found that NOVA launcher + Swipe Status bar to a better desktop than the stock launcher. Google MyTracks worked great for logging walks / trips and even logged while the screen was off.
I tried going through all the old threads but there seems (to me at least) a lot of info that is no longer relavant or doesn't pertain to what I have now... I am just trying to make sure I am on the right path as I don't want to screw this watch up like the last one.
### Given your newer firmware you might just be blazing a new trail. I would find/Download the ALLTOOLS kit that Lokifish put together if you can find it. Then use MtkDroidTools to make a backup of your firmware (then share that with the rest of us, please) and your device IDs just in case. In fact I would do this first before anything else.
DO THIS LAST BIT FIRST ^^^^ !!!!
Also I don't think TWRP recovery is working for firmware 5/27/14 or newer so...
Good Luck!
walscobry said:
Also I don't think TWRP recovery is working for firmware 5/27/14 or newer so...
Click to expand...
Click to collapse
Daniel Ortiz (with Dees Troy) fixed TWRP for "May list #4" and later with new TWRP. (In post on July 9 on G+.)
Not sure how to tell the difference with new eemc. The scatter file is different, but you need a reference...
https://plus.google.com/111628072657804333818/posts/bVRd9aDvBwm
I'd be happy to do a dump of this firmware if it is newer than what people have.
Walk me through it and I will take care of it.
D.
thanks for the may info
Well that did lead me to the may twrp that I have been looking for but it does not work. By that I mean it only sees the boot partition and also when exiting exclaims that no rom is present. I don't think it is full aware of the partition layout of my 5/27/14 firmware after OTA update. But exiting does return the TS to normal so not much harm done in trying.
As for a walk thru. Using the MtkDroidTools is fairly read whats on screen and proceed carefully. But I will refresh myself with it and try to be ready for more questions.
FYI while in TWRP I did not get the constant screen touching and dragging from the lower right corner like I do when booted into the full OS. Some people have mentioned static. I think it might be what us HAM radio guys call getting RF back into the system. In TWRP I am guessing all radios (cell, wifi, BT) off so no RF getting into the touch controller cable. I wonder if I open it up and see if there is someplace to insert a little RF blocking foil near that cable. This might have been a fruitful try even if I still have no recovery.
Also I was asking to share the backup of your firmware only. DO not share your Device ID / IMEI numbers!
From many many different threads and frankly confusing instructions I think I have puzzled together the following solid guideline for my kindle fire hdx from basic root to custom rom. Currently my firmware is 13.3.1.0.
Could someone take a look at this and tell me if I got this right or if I need to do stuff differently (or could do them better)? Don't assume that something is obvious, if it isn't written down, don't be shy to mention it. I would be ever so grateful .
Edit: I'm updating my experience as I move along the list and get more info just in case this might be useful to someone who is just as lost as I was in the beginning
Obligatory disclaimer: this is just a step-by-step guideline that worked for me. I'm not responsible if you chose to follow any of these steps and damage or brick your device.
Guideline:
-Download firmware version 3.2.3.2 and upgrade directly from any of the previous version by putting the file into the internal storage of the kindle, going to settings>device>system update on the kindle and installing the update from there.
-Root with Towelroot in the HDX toolkit downloaded from here (Edit: I got various error messages at this step but got it to work in the end. The 3rd post here shows what I did to get it working after getting error message 2 and 3 at various times)
-block OTA also with the tool in the HDX toolkit (is there a way to safely check that this worked? Edit: It worked )
-connect to wifi and install Flashify from the playstore (Edit: I ended up installing File Expert and flashify on another android device, backing up the flashify apk and sideloading it with ES File Explorer from the amazon app store to the kindle, I guess I could have also download the apk somewhere but I have trust issues.)
-download the img of TWRP 2.8.5.0. and put it in internal storage of kindle (had no problems)
-use flashify to save original stock recovery (had no problems)
-Use flashify to flash TWRP (had no problems)
- Boot into recovery mode via flashify to see if it worked (had no problems)
Now either A)
-download CM11 image and gapps and put the zip files on internal storage
-Edit: disconnect Kindle from USB afterwards
- go into TWRP recovery mode (by powering off kindle and then pressing power and volume at the same time)
- make backup of original stockrom under backups and save copy on your Computer
- wipe system, data, cache and dalvik cache under wipe/advanced (all except internal)
- flash cm11 image and gapps (under install and then find them in the files)
- reboot
-Edit: I had the wifi not connecting problem that some people have with CM11 but a reboot took care of it.
-Edit 2: I couldn't get the kindle app to work on CM11 (it wouldn't synch my books, the device wasn't recognized by amazon and it would crash every time I logged in.) so I ended up replacing it with the Nexus rom. If the chance of this happening doesn't bother you then CM11 seems to still be a good choice.
or B)
- download HDX thor nexus rom and gapps and put the zip files on internal storage
- go into TWRP recovery mode (by powering off kindle and then pressing power and volume at the same time)
- make backup of original stockrom under backups and save copy on your Computer
- wipe system, data, cache and dalvik cache under wipe/advanced (all except internal)
- Edit: disconnect Kindle from USB afterwards
- flash nexus rom and gapps (under install and then find them in the files)
- reboot
- Edit: I'm very happy with it, it works flawlessly. Since it's based on Jelly Bean I may try replacing it with another rom sometime in the future, but I'm in no hurry
Mostly correct, you can update directly to 3.2.3.2 no need for incremental steps. The only way to know if ota blocker worked is to check for update but there's really no need, as soon as you've run towel root just disable WiFi as it won't be needed anymore.
Where is unlock bootloader? As I know, you cannot flash TWRP without unlocking bootloader?!
uhraman said:
Where is unlock bootloader? As I know, you cannot flash TWRP without unlocking bootloader?!
Click to expand...
Click to collapse
You can flash a cuber signed TWRP on a locked bootloader, as long as you're below 3.2.4.
derpadoodle said:
You can flash a cuber signed TWRP on a locked bootloader, as long as you're below 3.2.4.
Click to expand...
Click to collapse
Thanks for your replies! Is the method uhraman hinted at the better one?
snorklm said:
Thanks for your replies! Is the method uhraman hinted at the better one?
Click to expand...
Click to collapse
Fully unlocking your bootloader is definitely worthwhile but it's quite a complicated endeavour and not required for running the current custom recoveries and ROMs. I'd recommend you stick with your current method and read up on the unlocking process once you're more conformable working with this device.
derpadoodle said:
Fully unlocking your bootloader is definitely worthwhile but it's quite a complicated endeavour and not required for running the current custom recoveries and ROMs. I'd recommend you stick with your current method and read up on the unlocking process once you're more conformable working with this device.
Click to expand...
Click to collapse
Could I bother you to give me a few examples on *why* it is worthwhile? Thanks!
snorklm said:
Could I bother you to give me a few examples on *why* it is worthwhile? Thanks!
Click to expand...
Click to collapse
- more robust recovery options when recovery (TWRP) is damaged/inaccessible; better chance of reviving a bricked device
- some custom roms install/operate better with unlocked BL (technically should not be needed but sometimes seen in early builds)
- some DRM aware apps on custom roms work better with unlocked BL(eg: playstore, prime)
Guidance form derpadoodle is sound. Enjoy what you have achieved thus far; revisit BL unlock when you are more comfortable with device/technique.
Davey126 said:
- more robust recovery options when recovery (TWRP) is damaged/inaccessible; better chance of reviving a bricked device
- some custom roms install/operate better with unlocked BL (technically should not be needed but sometimes seen in early builds)
- some DRM aware apps on custom roms work better with unlocked BL(eg: playstore, prime)
Guidance form derpadoodle is sound. Enjoy what you have achieved thus far; revisit BL unlock when you are more comfortable with device/technique.
Click to expand...
Click to collapse
Thanks for the sound advice, I will probably never feel comfortable enough for that , especially because I haven't achieved much at all yet. I haven't even flashed TWPR yet.
Yay, I did it. CM11 seems to be working as intended! Thanks again for everyone who replied and also to everyone who put so much work into making and improving all the tools and software necessary to make this kind of thing even possible, I appreciate it!
What firmware were you on to begin your process mate... ?
B3NJY said:
What firmware were you on to begin your process mate... ?
Click to expand...
Click to collapse
I was on 3.0.5 when I got the device. Amazon didn't upgrade the firmware at all before sending it out, then I upgraded to 13.3.2.3. Why do you ask?
Hmm, I have now noticed that the kindle app is not working properly. I can sign in (though every time I sign in or deregister my account the app crashes) but it's not synching any of my books. They don't show up at all. The device (named android device 2 in the kindle app settings) does also not show up under my devices on amazon. Anyone know what the problem could be because this is a bit frustrating. Is this a bug with CM11 or with the amazon app?
snorklm said:
Hmm, I have now noticed that the kindle app is not working properly. I can sign in (though every time I sign in or deregister my account the app crashes) but it's not synching any of my books. They don't show up at all. The device (named android device 2 in the kindle app settings) does also not show up under my devices on amazon. Anyone know what the problem could be because this is a bit frustrating. Is this a bug with CM11 or with the amazon app?
Click to expand...
Click to collapse
Can't say definitively but I would lean towards CM11 as all Amazon apps (kindle/prime/shopping/video) work fine with the Nexus ROM (v2.0.5) which is layered on the same hw/fw base as CM11. Don't get me wrong; CM11 (and the devs who adapted to the HDX) are great! But there may still be a few hiccups with native Amazon apps.
Davey126 said:
Can't say definitively but I would lean towards CM11 as all Amazon apps (kindle/prime/shopping/video) work fine with the Nexus ROM (v2.0.5) which is layered on the same hw/fw base as CM11. Don't get me wrong; CM11 (and the devs who adapted to the HDX) are great! But there may still be a few hiccups with native Amazon apps.
Click to expand...
Click to collapse
Thanks for the opinion! I couldn't find any solution to the problem anywhere online and therefore just finished replacing CM11 with the Nexus rom, now the kindle app works perfectly fine and I'm very satisfied with what I've got. I will keep an eye out on rom development but for now I'm resting on my laurels :victory:. Considering that I was helplessly lost when I first came to the board I'm very happy with how smoothly everything went. But I really needed that step-by-step list I made and the assurance from the pros that it was correct, otherwise I would have probably made a careless mistake :silly:. Maybe it will be useful to a few other newbies as well. Not sure I will ever dare to fully unlock the bootloader like some suggested I might want to do at a later point in time, but we will see . Thanks again for the help!
snorklm said:
Thanks for the opinion! I couldn't find any solution to the problem anywhere online and therefore just finished replacing CM11 with the Nexus rom, now the kindle app works perfectly fine and I'm very satisfied with what I've got. I will keep an eye out on rom development but for now I'm resting on my laurels :victory:. Considering that I was helplessly lost when I first came to the board I'm very happy with how smoothly everything went. But I really needed that step-by-step list I made and the assurance from the pros that it was correct, otherwise I would have probably made a careless mistake :silly:. Maybe it will be useful to a few other newbies as well. Not sure I will ever dare to fully unlock the bootloader like some suggested I might want to do at a later point in time, but we will see . Thanks again for the help!
Click to expand...
Click to collapse
Glad to hear everything is working well! My daily driver is on Nexus and I could not be happier. Everything works as it should. No need to unlock the bootloader unless you plan to do more modding. Enjoy your device!
Nice. I think everybody needs this kind of guide. Whenever a question is asked it just kind of trails off most of the time.
I'm still working on the downgrade piece.
johnwaters said:
Nice. I think everybody needs this kind of guide. Whenever a question is asked it just kind of trails off most of the time.
I'm still working on the downgrade piece.
Click to expand...
Click to collapse
Agreed, I was overwhelmed by all the different threads and possibilities at first. I ended up approaching it like any other research project for a paper or presentation and dumped every solid (and recent) piece of good advice into Evernote and sorting it out there. But writing and updating guides (especially with the fast development I have observed) would be a lot of work, I understand completely why no one would volunteer to do it and everybody would rather answer questions on a case by case basis.
First of all thank you very much! I was looking for something like this, since i am also new to rooting devices and this stuff...
I got a new fire hdx 7 with 13.3.02
I haven't tried anything yet, I am still reading threads and i got some questions here:
http://forum.xda-developers.com/kindle-fire-hdx/general/update-1314-4-1-1-probably-sangria-t2901813
-> I can only find 3.2.3.2 here, which is the firmware u used? Or did you mean another one?
http://forum.xda-developers.com/show....php?t=2665683
-> the second link for hdx toolkit isnt working
How do i get the playstore on my device?
are there anywhere more informations regarding flashify? since i have no idea what this is...
thank you!
dynein said:
First of all thank you very much! I was looking for something like this, since i am also new to rooting devices and this stuff...
I got a new fire hdx 7 with 13.3.02
I haven't tried anything yet, I am still reading threads and i got some questions here:
http://forum.xda-developers.com/kindle-fire-hdx/general/update-1314-4-1-1-probably-sangria-t2901813
-> I can only find 3.2.3.2 here, which is the firmware u used? Or did you mean another one?
http://forum.xda-developers.com/show....php?t=2665683
-> the second link for hdx toolkit isnt working
How do i get the playstore on my device?
are there anywhere more informations regarding flashify? since i have no idea what this is...
thank you!
Click to expand...
Click to collapse
First thing you want to do is block OTA (over the air updates) or your device may be upgraded by Amazon to a level that gives you less options. Suggest using HDX Toolkit (here) to both root and block OTA. Then install twrp (here). From there you can opt to replace Fire OS will several different roms including Nexus, CM11 or CM12.
Flashify is an app that allows flashing recovery and roms from from within Android vs adb or a recovery environment. You can grab it from the Play store or another market. It's a dangerous tool; use with extreme caution.
Be aware that any of the above actions, if executed incorrectly, can permanently brick your device with little/no hope of recovery (guess that's the definition of permanent). Read, read and read some more before taking any action. Be sure to keep WiFi off on your device until OTA is blocked to prevent auto-updates.
Okay, I managed to get root, supersu, and whatnot up and running (thanks to people in these forums). I then went for the safestrap route.
My new issue is this - I click on "install recovery" - and that seems to work fine. I get notification that it's been installed, and the "State: Installed" status updates. It appears the next step would be to reboot so I have a boot menu, or at least another set of options. The only choice available in safestrap itself is "reboot to recovery". If I choose this, the device reboots to the grey logo, then the screen goes mostly black (powered up, back lit, but dark), and stays that way. I can hold power to turn off and then re-power up to reset (I assume to reboot into the stock rom slot).
Obviously I'm missing something, but I'm not sure what step I might have skipped. To anticipate some questions, I'm on 14.3.2.5, and I used HDX Toolkit v0.95 to root and install safestrap. I did have some difficulty in getting my system to recognize the device as an android adb one, but eventually I got a driver installed that worked.
begalund said:
Okay, I managed to get root, supersu, and whatnot up and running (thanks to people in these forums). I then went for the safestrap route.
My new issue is this - I click on "install recovery" - and that seems to work fine. I get notification that it's been installed, and the "State: Installed" status updates. It appears the next step would be to reboot so I have a boot menu, or at least another set of options. The only choice available in safestrap itself is "reboot to recovery". If I choose this, the device reboots to the grey logo, then the screen goes mostly black (powered up, back lit, but dark), and stays that way. I can hold power to turn off and then re-power up to reset (I assume to reboot into the stock rom slot).
Obviously I'm missing something, but I'm not sure what step I might have skipped. To anticipate some questions, I'm on 14.3.2.5, and I used HDX Toolkit v0.95 to root and install safestrap. I did have some difficulty in getting my system to recognize the device as an android adb one, but eventually I got a driver installed that worked.
Click to expand...
Click to collapse
Thanks documenting so clearly. Unfortunately, having never used Safestrap (know just enough to be dangerous ...) I can't confidently answer your question but I'm sure someone with more experience will jump in.
Question: Why did you opt for Safestrap instead of twrp? It is a simple matter to downgrade to 14.3.1.0, reroot and then install twrp. From there you can stick with stock or install several different roms including nexus and CM11/12. Now, if you prefer rooted stock Fire OS then 3.2.5 and safestrap makes sense (although safestrap isn't necessary it does offer a more robust recovery...albeit not as rich/powerful as twrp). Thanks for taking time to respond; just trying to better understand people's choices as it may help others in similar circumstances.
Davey126 said:
Question: Why did you opt for Safestrap instead of twrp? It is a simple matter to downgrade to 14.3.1.0, reroot and then install twrp. From there you can stick with stock or install several different roms including nexus and CM11/12. Now, if you prefer rooted stock Fire OS then 3.2.5 and safestrap makes sense (although safestrap isn't necessary it does offer a more robust recovery...albeit not as rich/powerful as twrp). Thanks for taking time to respond; just trying to better understand people's choices as it may help others in similar circumstances.
Click to expand...
Click to collapse
Well, since I'm just learning, the SS route seemed easier to not screw up - I had less to do, so I had far fewer chances of ending up with a shiny paperweight. It also seemed to be reversible, so I could learn and then maybe go with the option you quoted above.
However, if I can't seem to make this part work, maybe I'll just skip the in-between step.
begalund said:
Well, since I'm just learning, the SS route seemed easier to not screw up - I had less to do, so I had far fewer chances of ending up with a shiny paperweight. It also seemed to be reversible, so I could learn and then maybe go with the option you quoted above.
However, if I can't seem to make this part work, maybe I'll just skip the in-between step.
Click to expand...
Click to collapse
Yep - makes a ton of sense. Wish everyone acted with your restraint. You'll do fine. Keep reading, watch for gotchas, post questions. Sorry for your Safestrap troubles. It works well for many/most so it sounds like a unique problem with (hopefully) an easy fix.
While I awaited a further reply, I decided to at least see about starting the next steps towards your approach. I downloaded the apollo gapps apks, got them installed, got my account loaded, but the app just keeps stopping immediately after start up. Makes it difficult to grab the prop editor to do a rollback unless there is another way to install that.
I'm currently looking into fixes for gapps, but not finding what I need yet. And yes, this is just the apks and not the rom - since I haven't gotten safestrap fixed, and haven't (obviously) moved on to the alt version, I haven't attempted flashing roms yet.
Update:
So, nevermind. I figured that part out. I was dumb and installed the apks as r/o and not r/w. live and learn (and don't brick I guess).
a stock android ROM (recommendations?)?
I've searched, but not found anything that can handily take me from having a rooted 14.3.2.6 HDx 8.9 (Apollo, right?) to a ROM. There's so much confusion about downgrading to an earlier version (for what?), having/not having safestrap, having TWRP, etc.
Anyone got a place where I can simply follow a 1-2-3 guide to go from root to ROM? Thanks!
BRPW said:
a stock android ROM (recommendations?)?
I've searched, but not found anything that can handily take me from having a rooted 14.3.2.6 HDx 8.9 (Apollo, right?) to a ROM. There's so much confusion about downgrading to an earlier version (for what?), having/not having safestrap, having TWRP, etc.
Anyone got a place where I can simply follow a 1-2-3 guide to go from root to ROM? Thanks!
Click to expand...
Click to collapse
There are no 1-2-3 guides. However, the steps required are not complicated but do require carefully reading and attention to detail. As you are probably aware Kindles in general and HDX models in particular are easy to 'brick' with limited/no recovery options. Many folks have killed their device with a simple mistake. Stakes are high with an Apollo given the device's value. Think hard before moving forward; even if you do everything right you can end up with an expensive paperweight. If you're an 'android expert' be aware many recovery techniques used on other devices simply will not work on an HDX. Fastboot cables are useless.
Preliminary questions:
- have you blocked OTA (if so via which method) or otherwise taken steps to isolate your device from automatic updates?
- do you have safestrap or Xposed Framework installed?
- have you enabled adb?
Davey126 said:
There are no 1-2-3 guides. However, the steps required are not complicated but do require carefully reading and attention to detail. As you are probably aware Kindles in general and HDX models in particular are easy to 'brick' with limited/no recovery options. Many folks have killed their device with a simple mistake. Stakes are high with an Apollo given the device's value. Think hard before moving forward; even if you do everything right you can end up with an expensive paperweight. If you're an 'android expert' be aware many recovery techniques used on other devices simply will not work on an HDX. Fastboot cables are useless.
Preliminary questions:
- have you blocked OTA (if so via which method) or otherwise taken steps to isolate your device from automatic updates?
- do you have safestrap or Xposed Framework installed?
- have you enabled adb?
Click to expand...
Click to collapse
Hi,
thanks for the response; I understand 100%.
I have blocked OTA (but weirdly keep getting "kindle is upgrading" messages every time I restart my Kindle)
I have Xposed Framework installed
ADB is enabled.
On another note, I've installed the four Gapps APKs, but my google play store won't work. Any idea why? When I install them, the play store opens and displays apps just fine, but won't download them. I reboot, and when I do I get "Google play store has stopped" and "Google play services has stopped working" messages, and Google Play crashes instantly.
I can't figure out why. Any idea? Apologies for bombarding you with queries.
Your play store issue is probably Google play services. Download version .99 from the internet or the general thread.
As for your next steps.
It depends on how involved you want to go.
You can use safestrap and run the nexus Rom. Some people feel that is less risky because you are not modifying the system as much or recovery at all. However, if something goes wrong, you have almost no way to fix it (it is possible to brick with safestrap).
Or,
Downgrade to 2.3.2 (you have to do this because the 2.6 bootloader will not load any other recoveries or roms. Then put twrp on and use cm11 or similar. This gives you a working recovery to fix some issues which could go wrong.
Finally, you could rollback and unlock your bootloader. If you do that, it is the most involved, and a little risky. However, if you succeed. You will be able to put more rooms on it and this gives you the most options to recover from an error.
Many people are playing with cm12 after this.
It all depends on how you are willing to take your risks. It will all require a lot of reading on the forums.
Good luck.
Sent from my KFTHWI using Tapatalk
BRPW said:
Hi,thanks for the response; I understand 100%.
I have blocked OTA (but weirdly keep getting "kindle is upgrading" messages every time I restart my Kindle)
I have Xposed Framework installed
ADB is enabled.
On another note, I've installed the four Gapps APKs, but my google play store won't work. Any idea why? When I install them, the play store opens and displays apps just fine, but won't download them. I reboot, and when I do I get "Google play store has stopped" and "Google play services has stopped working" messages, and Google Play crashes instantly.
I can't figure out why. Any idea? Apologies for bombarding you with queries.
Click to expand...
Click to collapse
You need to clean up your device before going further. Yes, some folks have successfully rolled back with baggage in tow. With limited data points my observation is previously unsurfaced add-ons and tweaks (usually revealed only after someone fubars their device) are contributors to unfavorable outcomes. Take that for what it's worth.
Recommendations:
- Identify and discard the update file that is triggering the "Kindle is upgrading" message. Best guess is a 14.x upgrade that can't progress due to OTA block. You are looking for a large (500 MB+ file) .bin file with a name similar to "update-kindle-14.4.5.3_user_453011120.bin". Reboot to make sure the upgrade message goes away.
- Tether your device. Download HDX Toolkit to a Windows box and make sure it can see your Kindle. Don't take any actions other than confirming root.
- Disable wifi and delete all existing wireless profiles. Then remove the existing OTA blocker reversing whatever technique was previously used.
- Use HDX toolkit to block OTA (this is the only method I trust for Fire OS 3.0.x-3.2.x)
- Uninstall Xposed framework and all associated modules (module portion isn't technically necessary as they won't run with framework disabled)
- Remove play store, services, framework (via services) and all Google apks. Reboot to make sure your device is 'clean'. You should still have root, of course.
- Come clean on any other tweaks previously made including modifications to build.prop, failed root attempts, safestrap, etc. Anything that deviates from stock.
Post back when complete. I'll then help you through the roll back process and installation of twrp. From there you can install Nexus (excellent, stable rom but Jellybean based) or CM11 (KitKat). Save bootloader unlocking for another day.
Davey126 said:
You need to clean up your device before going further. Yes, some folks have successfully rolled back with baggage in tow. With limited data points my observation is previously unsurfaced add-ons and tweaks (usually revealed only after someone fubars their device) are contributors to unfavorable outcomes. Take that for what it's worth.
Recommendations:
- Identify and discard the update file that is triggering the "Kindle is upgrading" message. Best guess is a 14.x upgrade that can't progress due to OTA block. You are looking for a large (500 MB+ file) .bin file with a name similar to "update-kindle-14.4.5.3_user_453011120.bin". Reboot to make sure the upgrade message goes away.
- Tether your device. Download HDX Toolkit to a Windows box and make sure it can see your Kindle. Don't take any actions other than confirming root.
- Disable wifi and delete all existing wireless profiles. Then remove the existing OTA blocker reversing whatever technique was previously used.
- Use HDX toolkit to block OTA (this is the only method I trust for Fire OS 3.0.x-3.2.x)
- Uninstall Xposed framework and all associated modules (module portion isn't technically necessary as they won't run with framework disabled)
- Remove play store, services, framework (via services) and all Google apks. Reboot to make sure your device is 'clean'. You should still have root, of course.
- Come clean on any other tweaks previously made including modifications to build.prop, failed root attempts, safestrap, etc. Anything that deviates from stock.
Post back when complete. I'll then help you through the roll back process and installation of twrp. From there you can install Nexus (excellent, stable rom but Jellybean based) or CM11 (KitKat). Save bootloader unlocking for another day.
Click to expand...
Click to collapse
I can't find anything resembling that type of file name, after doing a ES file explorer search. I also tried ordering by size and going through folders and files, but still couldn't find anything.
BRPW said:
I can't find anything resembling that type of file name, after doing a ES file explorer search. I also tried ordering by size and going through folders and files, but still couldn't find anything.
Click to expand...
Click to collapse
Don't have an immediate explanation but suggests something is amiss that could muck-up roll back efforts. It could be OTA is only partially blocked so your Kindle sees there is an update but can't download or process it. Do you know what method was used to block updates?
Davey126 said:
Don't have an immediate explanation but suggests something is amiss that could muck-up roll back efforts. It could be OTA is only partially blocked so your Kindle sees there is an update but can't download or process it. Do you know what method was used to block updates?
Click to expand...
Click to collapse
Yeah, I used the KFHDX Toolkit 0.95, and once I'd installed Xposed Framework, I installed the HDXposed module, which also blocks OTA updates.
BRPW said:
Yeah, I used the KFHDX Toolkit 0.95, and once I'd installed Xposed Framework, I installed the HDXposed module, which also blocks OTA updates.
Click to expand...
Click to collapse
HDXposed is likely part of the problem. Uninstall that (make sure wifi is off), reboot then reapply the OTA blocker integrated into KFHDX Toolkit 0.95. Reboot again and see if update message goes away. Might not if a bit got set somewhere indicating that an update is available. That in itself shouldn't be an issue unless information about the update version is also stored (don't believe it is).
Disclaimer: Anytime you muck with OTA blocking there is a chance it won't get set properly resulting in an unwanted update when wifi is restored. Recently this has been the case with renaming the otacerts file...at least on some versions of Fire OS. That said, I have yet to have the OTA blocker in KFHDX Toolkit fail. Once you ditch Fire OS this worry goes away.
Davey126 said:
HDXposed is likely part of the problem. Uninstall that (make sure wifi is off), reboot then reapply the OTA blocker integrated into KFHDX Toolkit 0.95. Reboot again and see if update message goes away. Might not if a bit got set somewhere indicating that an update is available. That in itself shouldn't be an issue unless information about the update version is also stored (don't believe it is).
Disclaimer: Anytime you muck with OTA blocking there is a chance it won't get set properly resulting in an unwanted update when wifi is restored. Recently this has been the case with renaming the otacerts file...at least on some versions of Fire OS. That said, I have yet to have the OTA blocker in KFHDX Toolkit fail. Once you ditch Fire OS this worry goes away.
Click to expand...
Click to collapse
Tried that; deactivated HDXposed, reboot. Enabled OTA, then re-disabled it, and rebooted again. Message still pops up briefly.
Should I continue with the steps you've listed above?
BRPW said:
Tried that; deactivated HDXposed, reboot. Enabled OTA, then re-disabled it, and rebooted again. Message still pops up briefly.
Should I continue with the steps you've listed above?
Click to expand...
Click to collapse
Yes - still need to prep the device. I'll be out-of-pocket for the next 8-10 hours; will look for an update then.
Davey126 said:
Yes - still need to prep the device. I'll be out-of-pocket for the next 8-10 hours; will look for an update then.
Click to expand...
Click to collapse
Okay, I'll complete the list of things you've recommended; again, thanks for your help so far. Really appreciate it.
Edit: All Google apps/APKs removed, Xposed Framework's gone also. Rebooted and clean as stock (apart from root, of course), and zero custom apps apart from SuperSU and towelroot; interestingly, after reboot, there's no 'upgrading' message. So seems that's also disappeared.
BRPW said:
Okay, I'll complete the list of things you've recommended; again, thanks for your help so far. Really appreciate it.
Edit: All Google apps/APKs removed, Xposed Framework's gone also. Rebooted and clean as stock (apart from root, of course), and zero custom apps apart from SuperSU and towelroot; interestingly, after reboot, there's no 'upgrading' message. So seems that's also disappeared.
Click to expand...
Click to collapse
Have a look here for next steps. You are following instructions for 3.2.5-3.2.6 which is at the bottom of the post shaded in grey. To be clear you do not need to modify build.prop (if anything suggests that and/or installing Safestrap you're in the wrong section). You can get everything ready following the post and move forward if you feel comfortable. Remember you will need to reroot and block OTA once the rollback completes; use HDX toolkit for both. An outline of further actions can be found here.
Ok - now i really do have to go ...
Davey126 said:
Have a look here for next steps. You are following instructions for 3.2.5-3.2.6 which is at the bottom of the post shaded in grey. To be clear you do not need to modify build.prop (if anything suggests that and/or installing Safestrap you're in the wrong section). You can get everything ready following the post and move forward if you feel comfortable. Remember you will need to reroot and block OTA once the rollback completes; use HDX toolkit for both. An outline of further actions can be found here.
Ok - now i really do have to go ...
Click to expand...
Click to collapse
Haha thanks; I have the update file downloaded, but getting suspicious about the update.prop file download link. Got phishing warnings and malicious warnings all over the place. May wait and see what you say once you're back.
Edit: Did some research; was clicking the wrong damn button. For anyone who comes across this, click the BLUE 'download now' button. I was clicking the green (read: advert) button. I've rolled my update back all fine; one question.
The update file says: 14.3.1.0, yet my Kindle firmward says 14.3.0.0. Is that supposed to be like that? Anyhow, I'm rerooted, OTA updates blocked. I think I'm going to wait to proceed with the next part. Thanks again (so far)!
BRPW said:
Haha thanks; I have the update file downloaded, but getting suspicious about the update.prop file download link. Got phishing warnings and malicious warnings all over the place. May wait and see what you say once you're back.
Edit: Did some research; was clicking the wrong damn button. For anyone who comes across this, click the BLUE 'download now' button. I was clicking the green (read: advert) button. I've rolled my update back all fine; one question.
The update file says: 14.3.1.0, yet my Kindle firmward says 14.3.0.0. Is that supposed to be like that? Anyhow, I'm rerooted, OTA updates blocked. I think I'm going to wait to proceed with the next part. Thanks again (so far)!
Click to expand...
Click to collapse
Not sure the rollback completed successfully. It is normal for your Kindle to report 14.3.0.0 just after executing the batch file. Fire OS normally won't downgrade so the script 'tricks' the system into thinking it's at 14.3.0.0. Your device then sees the 14.3.1.0 file as an update and processes it. You are essentially leveraging Amazon's update process to execute a rollback.
I'm guessing your forgot to transfer the bin file to your device after executing the upgrade script. If accurate your Kindle is in a someone dangerous state. You'll want to disable OTA blocking, copy the bin file to 'internal storage' and then check for updates via Fire OS settings. It may take a few minutes for your Kindle to recognize the update file. Also note the original bin file needed to reside in the same windows directory as the batch file when it was executed.
Side note: We are experiencing a rare power outage in my area. I'm penning this from a secondary system. Won't be staying on long to conserve battery. Will check for updates once power is restored.
Davey126 said:
Not sure the rollback completed successfully. It is normal for your Kindle to report 14.3.0.0 just after executing the batch file. Fire OS normally won't downgrade so the script 'tricks' the system into thinking it's at 14.3.0.0. Your device then sees the 14.3.1.0 file as an update and processes it. You are essentially leveraging Amazon's update process to execute a rollback.
I'm guessing your forgot to transfer the bin file to your device after executing the upgrade script. If accurate your Kindle is in a someone dangerous state. You'll want to disable OTA blocking, copy the bin file to 'internal storage' and then check for updates via Fire OS settings. It may take a few minutes for your Kindle to recognize the update file. Also note the original bin file needed to reside in the same windows directory as the batch file when it was executed.
Side note: We are experiencing a rare power outage in my area. I'm penning this from a secondary system. Won't be staying on long to conserve battery. Will check for updates once power is restored.
Click to expand...
Click to collapse
Hey Davey,
hope your power problems get sorted soon. As for the update, I did in fact pull the file both into the "rollback89v2" folder (containing the install.bat) and into the 'internal storage' area of the kindle, so should be no problem there. Got up this morning, headed to the 'Device' section to find my Kindle says 'update available'.
Bear in mind that OTA is disabled, and I've not enabled my WiFi since I began the process yesterday, so there should be ZERO chance of that being a normal OTA; I'm guessing it's the 'update' to 14.3.1.0?
BRPW said:
Hey Davey,
hope your power problems get sorted soon. As for the update, I did in fact pull the file both into the "rollback89v2" folder (containing the install.bat) and into the 'internal storage' area of the kindle, so should be no problem there. Got up this morning, headed to the 'Device' section to find my Kindle says 'update available'.
Bear in mind that OTA is disabled, and I've not enabled my WiFi since I began the process yesterday, so there should be ZERO chance of that being a normal OTA; I'm guessing it's the 'update' to 14.3.1.0?
Click to expand...
Click to collapse
Sorry for the delay. Yes, accept the update if you have not done so already. You will probably need to re-enable OTA (keep wifi off) for processing to complete. After reboot the device should report it's on 14.3.1. You can then reroot and block OTA via HDX toolkit.
Next step is to install twrp. If you are comfortable issuing adb commands you can use the method outlined here which is also where you grap the custom apk. Alternatively, sideload flashify (here or elsewhere; copy apk via tether). I recommend the latter as flashify simplifies future efforts and contains some nice backup/recovery features.
Test twrp by powering down your device then restarting by pressing power + vol-up. Release the power button when the grey Kindle logo appears. Release the volume button a few seconds later. You should eventually enter the twrp environment. Familiarize yourself with the options but don't take any actions. When complete hit the reboot button from the main screen (lower right corner).
Then update your bootloader to 3.2.3.2. This is listed as a prerequisite for twrp but the order is not important provided both get done. Personally I prefer to get twrp installed early in the sequence as it offers vastly improved recovery options should something go wrong. You can flash the updated bootloader from twrp or flashify.
Once this is done you are ready for a custom rom! Post when complete and I will briefly outline your options.
As always, think through each step before proceeding. Make sure you have the right files. Verify MD5s once copied to your device (I use Hash Droid). Installing twrp and the bootloader update involve flashing code directly to your device. A mistake can be non-recoverable.
Davey126 said:
Sorry for the delay. Yes, accept the update if you have not done so already. You will probably need to re-enable OTA (keep wifi off) for processing to complete. After reboot the device should report it's on 14.3.1. You can then reroot and block OTA via HDX toolkit.
Next step is to install twrp. If you are comfortable issuing adb commands you can use the method outlined here which is also where you grap the custom apk. Alternatively, sideload flashify (here or elsewhere; copy apk via tether). I recommend the latter as flashify simplifies future efforts and contains some nice backup/recovery features.
Test twrp by powering down your device then restarting by pressing power + vol-up. Release the power button when the grey Kindle logo appears. Release the volume button a few seconds later. You should eventually enter the twrp environment. Familiarize yourself with the options but don't take any actions. When complete hit the reboot button from the main screen (lower right corner).
Then update your bootloader to 3.2.3.2. This is listed as a prerequisite for twrp but the order is not important provided both get done. Personally I prefer to get twrp installed early in the sequence as it offers vastly improved recovery options should something go wrong. You can flash the updated bootloader from twrp or flashify.
Once this is done you are ready for a custom rom! Post when complete and I will briefly outline your options.
As always, think through each step before proceeding. Make sure you have the right files. Verify MD5s once copied to your device (I use Hash Droid). Installing twrp and the bootloader update involve flashing code directly to your device. A mistake can be non-recoverable.
Click to expand...
Click to collapse
Having issues with the first part. I have 'update failed'. I keep trying wifi on/OTA disabled, OTA enabled/Wifi disabled. Sometimes I get 'update now', but having trouble. It wants OTA and Wifi enabled. Any workaround?
BRPW said:
Having issues with the first part. I have 'update failed'. I keep trying wifi on/OTA disabled, OTA enabled/Wifi disabled. Sometimes I get 'update now', but having trouble. It wants OTA and Wifi enabled. Any workaround?
Click to expand...
Click to collapse
Suggestions (in priority order):
- remove all existing wifi profiles (so your device can't connect), move away from open hotspots, enable wifi and retry. Some report this solves the problem.
- if above fails shut down device and boot into recovery via power + vol-up. From there perform a factory reset. Then see if the update takes.
There is a small risk of crashing your device with the second method. I used to recommend against it but others report it is a necessary step. Suspect it depends on how OTA has been disabled in the past. Factory resets only cause problems if your device has unusual mods that prevent the reset from fully completing.
Davey126 said:
Suggestions (in priority order):
- remove all existing wifi profiles (so your device can't connect), move away from open hotspots, enable wifi and retry. Some report this solves the problem.
- if above fails shut down device and boot into recovery via power + vol-up. From there perform a factory reset. Then see if the update takes.
There is a small risk of crashing your device with the second method. I used to recommend against it but others report it is a necessary step. Suspect it depends on how OTA has been disabled in the past. Factory resets only cause problems if your device has unusual mods that prevent the reset from fully completing.
Click to expand...
Click to collapse
First option worked. Right, I side-loaded flashify. I'm guessing Im choosing the recovery image option, which then asks me to choose a recovery option; I choose TWRP, which then takes me to a device option. I don't see HDX 8.9 anywhere there. Which device am I choosing?
Edit: Scratch that; figured out what I had to do. Right, everything is done. TWRP's installed and working fine; bootloader is installed (though I don't know how to check it installed correctly). I think I'm ready for ROMs unless there are more checks to do?
Second edit: After some research, I think I've decided on CM11 (That's KitKat, right?). It seems that everything works on that; wifi works nicely, the Kindle app works nicely (had a HD7 that had issues after I flashed an Android ROM), even the camera works nicely. Just need a clear guide on how to flash it, so will wait for you to come back. It's things like "do I wipe dalvik cache, etc" that I'm confused about also. I'd rather not mess it up on the last hurdle trying to rush into it.
To specify, I'm looking at this one: http://forum.xda-developers.com/kin...rom-cm-11-20150228-unofficial-apollo-t3042776
Does it come pre-installed with gapps or no? Can't quite figure that out, since some ROMs specifically mention that they have gapps already loaded in.
Thanks.
DEPRECATED
This firmware is old and deprecated.
See the below link for new firmware and a better root method.
https://forum.xda-developers.com/galaxy-s8/development/root-partcyborgrom-aqi6-deodexed-t3702988
You can just flash the BL_ tarball if you don't want to install a new system
but want the better screen and modem drivers.
PART 2: FIRMWARE RELOADED
I have done extensive research into the issues reported by those of you who are still experiencing screen issues.
I was unable to reproduce the screen issue on my then-current firmware with this update.
Not being content to leave people with buggy screens, I learned as much as I could about the s8 firmware.
This is what I did with that information.
Flashable Custom Firmware Package For ALL SM-G950U/U1 ON US CARRIERS
If you have a non-us G950U and want to install this pm me or ask in the thread and ill make one. Its very simple but I wanted to get this out to everyone else ASAP
NOTICE!
This an UPDATE (and More) to the Green/Garbled Screen Issue firmware.
There is NEW firmware to download below, and everyone who is rooted should read on, even if you installed the previous version.
Background
At the core of the issue with the garbled screen, modem panics, and sd card issues are two central themes: Bugs, and Incompatibilities. The S8 family of phones was fraught with issues early in its release, including the infamous "Red Tint', Fingerprint scanner malfunctions, mysteriously poor battery life, and surely a bunch of smaller others. Many of these bugs were caused by issues in the device's underlying firmware. Like most devices, Samsung has worked to fix these bugs and improve device performance throughout the phones lifetime for sale in public.
Root Bugs
The problem was unfortunately worse for users of one of the rooting methods for the S8. The biggest reason for this is that in order to relax security constraints enough to make rooting possible, a "non-user oriented", "factory" combination firmware was used. This firmware, being designed apparently for configuration/repair processes inside a factory, was not tuned to the normal level as the public firmware, likely did not go through the same testing, and ultimately any bugs unique to this "Combination" firmware that did not directly affect basic functionality or also stock were probably largely initially ignored.
This is where most of the issues that you all have had come from.
Finding a Solution
As I was unable to reproduce the issue on my device without resorting to the original firmware shipped out with the root method I used, I decided to think about what made my device different than the other devices reporting these issues. While sure we may have slightly varying hardware and that may contribute to these issues as well. What I am absolutely certain of is that most of us have different releases of software from each other. Not only have people essentially ad-hoc upgraded from the original firmware they rooted with until now, many have not upgraded at all or, only partially upgraded (such as with the pervious version of this).
While I could have simply packaged up my firmware/bootloader flashfire backup, I decided to take it a step further.
THE GOODS
Without further ado, I present to you:
S8Root Improved: A SM-G950U1 Custom Firmware Package for Root Users
This package contains a custom mix of the latest AQH3 STOCK (not combination) firmware used wherever possible with the Necessary boot/kernel images from the combination firmware necessary to keep root working with permissive SELinux. It contains all of the improvements from the previous version, and many more.
RESULTS
I can only speak for myself, but the results I experienced were amazing:
- Better UI Responsiveness.
Things surprise me how they move
- Sharper/brighter screen colors
I thought it couldn't get better than the last version but it has! Everything just looks crisper and are super bright without being oversaturated like with the Adaptie Mode.
- POSSIBLY Improved LTE network connectivity.
Note I said POSSIBLY. I personally regularly experienced 8-10Mb/s download bumps and 2-3Mb/s upload bumps in LTE while moving back and forth from this new firmware. I have my LTE radio locked to a specific channel (there are two i pick up at my place and one is terrible) and I carefully measured -107 to -112 dBm RSRP and -13 to -14 dB RSRQ prior to each measurement. I almost left this out but I figured it would be better to give you the information with no conclusion either way. It ABSOLUTELY could be Atmospheric changes, Traffic level changes, or any other of a million thins. YMMV
- Could POTENTIALLY still any remaining fix long-standing SDCard issues
I did not experience this, but had a few reports from users that did. The same pieces used in that version that would touch SDcard usage are used here, so that fix/improvement will carry over.
DISCLAIMER
Unfortunately proving beyond any shadow of a doubt that this package fixes the issue was impossible . I have TRIED AND TRIED AND TRIED to trigger the screen issues, including tweaking on and off every setting (auto brightness, multiple DPIs, different graphs modes, etc) I could get my hands on and it just was not happening. I used every software/systems trick I could think of to break this again, and I was completely unable to tickle the bug on this firmware, despite being able to reliably trigger it almost on command using my previous firmware.
The only thing left to do is either:
- Get the source from samsung, fix the bug myself, and get them to sign my new kernel image with their key so our locked bootloaders would allow it (HAHA I DOUBT IT)
- Acquire a large fleet of S8s (and S8+s) to run distributed integration testing (like the kind Android use at Google). Well if someone wants to buy me a few dozen s8s and s8+s (each) sure I'll take a month off work and squash this, but otherwise not gonna happen either.
If it STILL happens for you, I'm sorry.
I have done everything I can think of, and if it happens to you and you have suggestions, I'm all ears.
BUT HEY, but this is XDA right? Land of mods like Xposed which will brick one persons device and work flawlessly on the identical one next to it. And we love Xposed don't we?
Despite absolutely hilarious comments to the contrary, this package absolutely meets the (aka "BugFix") as well as just about any android update ever does, given the wide variety of environments, usecases and software configurations out there. I surely hope that this works for you.
Instructions
1) Download the package from the link above.
- Here it is Again for good measure.
2) Reboot into download mode and flash using Comsy Odin
Thats it! I packaged this in a way to make the process as smooth as possible.
There is NO reinstall, NO wipe of any kind, nor ANY further work on your part needed to install and use this.
The file size is small so the download is fast, and again, there is NO WIPE or config change needed.
if (for some inexplicable reason) you want to roll back, or go to 100% stock sans root, that process should not be made any more difficult as well.
Legacy Information
If you were here before and either looked at or downloaded the previous version, AND YOU HAVE NO QUESTIONS you can skip this part.
If you have questions, please read through to the end of the post before asking them, as I tried to answer as many as I could before hand and all of this information still applies.
WHAT IT IS NOT:
I wanted to outline a few things it is NOT about, to make a valliant effort to stem off the flow of questions before they begin (ha!):
NOT: A new Stock ROM for Your Phone
THIS IS NOT A FULL OS BUILD! DO NOT DOWNLOAD THE WHOLE THING AND FLASH IT EXPECTING AN ENTIRELY UPGRADED OS.
There is no full stock AQI1 image I have found. Believe me I looked a bunch of places after I found it
NOT: Oreo Early Preview
Given the predictions that the next release from Samsung would likely be Oreo, there was some initial over excitement. This wound up being NOT the case and if you read at least current Samsung Oreo projections they are predicting AQB now.
NOT: A Fix for the 80% Battery Issue
I know this is completely futile to hope for but:
THIS DOES NOT FIX THE 80% BATTERY ISSUE!!!!
NO WE DO NOT HAVE A FIX FOR THAT OR ONE COMING ANY TIME SOON!
YES SOME PEOPLE ARE STILL TRYING!
PLEASE DO NOT ASK! OFF TOPIC FOR THS THREAD
NOT: Currently Tested by ANYONE but ME
Since the moment I installed this I have not had ONE SINGLE screen issue, where previously I would have them several times throughout the day (at least 3 sometimes upwards of 6). For the case of ME and MY device, I am confident in declaring that this boot ROM does not have the same kernel bug that was causing the issue on the boot.img provided as part of your traditional root method.
NOTE: This is for the s8 G950 US Snapdragon models ONLY! Do NOT Flash this on your exynos, your Chinese/HK S8, your N8, your MOTO RAZR flip phone, whatever else you have. Kernels/boot.img files are very device specific and you will surely break it if not completely brick it.
DISCLAIMER:
YOUR WARRANTY IS ALREADY VOID if you are paying attention and are doing this to fix bugs with the existing sampwnd root.
HOWEVER IT IS EVEN VOIDER NOW. FLASH THUS TO YOUR DEVICE AT YOUR OWN RISK!
and if you break it I AM NOT RESPONSIBLE! FLASH AT YOUR OWN RISK!
As I said I have not tested this anywhere but my phone as I dont have any other s8s nor do I have access to any locally. I hope it works for you as well as it has for me.
STEPS
Download Boot Image
Use the URL here to Download the AQI1 boot.img file: Go Download the New Hotness
Prepare Phone for Flashing in FlashFire
If you did not download it on your phone, copy it somewhere FlashFire can see it.
Flash it
Open up FlashFire
Hit the "+" button
Select the "Flash Firmware Package" option, NOT the "Flash Zip or OTA" option!
You should see a popup window thing that has a checkbox next to the word BOOT, with "boot.img, 22MiB" underneath.
Make sure the checkbox is checked.
Make sure that it says BOOT above boot.img.
I have no idea if its possible for this to get messed up, but BOOT implies flashing the BOOT partition so if it says something else you are headed towards brick town, abort immediately.
Press the Check mark at the top right corner once you have confirmed the two things above.
MAKE SURE EVER ROOT IS DISABLED!!!
Click on the "Reboot" box, and choose "Recovery". MAKE SURE PRESERVE RECOVERY IS NOT CHECKED!
Back at the main menu, click the lightening bolt next to the word FLASH. Confirm.
Wait for FlashFire to do its thing. Sometimes it takes a minute for FF to wake up and start flashing. Occasionally for me it never happens, if this happens DO NOT PANIC ITS FINE. Hold down power+volDown until you eventually wind up in upload mode, then just reboot normally and everything will come back fine.
When FlashFire finishes (it will go really fast, the image is only 22MB we arent flashing a 5GB system here), it will auto-reboot your device into the recovery men
Select Wipe Cache and Confirm
This will wipe cache which is fine and safe. Again maybe not needed, feel free to skip if you know what you are doing. If you mess up and accidentally click factory reset instead, please tell me so I can laugh at you.
Reboot into a Clear New World
Select reboot and boot the system normally. If you formatted the cache partition above, it will take a little longer to start your phone. This is just the first time per normal.
Thats it! Welcome to the world of clear screens and bright colors. It could be a total placebo effect but I actually think this kernel drives the display better sometimes.
Please let me know what you think, and if this works for you. I wi;; be here for a while to answer questions or fix anything i typoed above or whatever.
FYI: A s8+ thread is coming too, as I sprung for purchasing both downloads to be an equal opportunity XDAer (at least with US flagship Samsung devices lol) but since I have an s8 and thus had the files locally already I made this one first
@jhofseth for nerding out with me the last few nights on trying crazy **** to get a bootloader unlock which prompted me to dig at this in the first place
Most of all, all of the tons of you who have made so many aewesome mods, themes, apps, what have you that I use every day and that make me enjoy my device all the more. I could not be happier to have the opportunity to give back a little.
Here is the restof the s8 combo firm if you are interested, but don't just flash this as its not a full OS:
EDIT: DOWNLOAD THE NEW ONE ABOVE
Can I Get The Link To The S8+ Boot im willing to try it
Mark805 said:
Can I Get The Link To The S8+ Boot im willing to try it
Click to expand...
Click to collapse
Coming very soon I promise! 10m max
Ok thanks
Mark805 said:
Can I Get The Link To The S8+ Boot im willing to try it
Click to expand...
Click to collapse
Its up now! https://forum.xda-developers.com/ga...sampwnd-root-green-screen-corruption-t3673815
whats the bootloader verison? it can be found by booting into download mode manually.
Cameron581 said:
whats the bootloader verison? it can be found by booting into download mode manually.
Click to expand...
Click to collapse
This isn't a bootloader change, it's boot.img which is the kernel and root filesystem essentially
Hey, btw this does not void warranty. I understand it's a standard disclaimer but it doesn't void it. It doesn't trip knox, so warranty is still very intact.
mweinbach said:
Hey, btw this does not void warranty. I understand it's a standard disclaimer but it doesn't void it. It doesn't trip knox, so warranty is still very intact.
Click to expand...
Click to collapse
Uh just because their service does not catch you does not mean that technically you are not violating your warranty contract thus making using technically illegal
That would be like saying "it's not murder if you leave no forensics!" Lol
wildermjs8 said:
Uh just because their service does not catch you does not mean that technically you are not violating your warranty contract thus making using technically illegal
That would be like saying "it's not murder if you leave no forensics!" Lol
Click to expand...
Click to collapse
i mean legally a warranty can not be void through software modifications unless it causes physical damage to the device. Since the efuse was not tripped no physical damage has been caused and no warranties have legally been void.
I had the green screen/graphics corruption after flashing this still...
goliath714 said:
I had the green screen/graphics corruption after flashing this still...
Click to expand...
Click to collapse
Apparently this happens to some people. I am fairly certain it is a firmware combination issue but I haven't been able to track it down. One thing you can do to eliminate it if you have the issue still (please let me know if this does not work) is to disable auto brightness.
wildermjs8 said:
Apparently this happens to some people. I am fairly certain it is a firmware combination issue but I haven't been able to track it down. One thing you can do to eliminate it if you have the issue still (please let me know if this does not work) is to disable auto brightness.
Click to expand...
Click to collapse
I have auto brightness off and still get it here and there.
goliath714 said:
I had the green screen/graphics corruption after flashing this still...
Click to expand...
Click to collapse
Please check out the OP again and download/flash the new version. Rather than just a few files, its a whole new entire bootloader/kernel package that I assembled piece by piece to have as much latest stock firmware as possible while maintaining what we need for root.
My primary suspect for why some people experience this regression is having older parts of their system. Rather than push everyone to upgrade, I made a painless upgrade process for all of their firmware instead
This includes the Radio drivers and bootloaders, kernels and flash layer libraries. Its all either latest stock or its AQI1 Combination because it was absolutely necessary.
wildermjs8 said:
Please check out the OP again and download/flash the new version. Rather than just a few files, its a whole new entire bootloader/kernel package that I assembled piece by piece to have as much latest stock firmware as possible while maintaining what we need for root.
My primary suspect for why some people experience this regression is having older parts of their system. Rather than push everyone to upgrade, I made a painless upgrade process for all of their firmware instead
This includes the Radio drivers and bootloaders, kernels and flash layer libraries. Its all either latest stock or its AQI1 Combination because it was absolutely necessary.
Click to expand...
Click to collapse
We flash the tar in the AP slot correct?
CloudyxVision13 said:
We flash the tar in the AP slot correct?
Click to expand...
Click to collapse
Yep
---------- Post added at 08:29 PM ---------- Previous post was at 08:28 PM ----------
Seems to be running better to me. Thanks bro
CloudyxVision13 said:
We flash the tar in the AP slot correct?
Click to expand...
Click to collapse
It actually does not matter, as Odin will do the right thing no matter what.
Sorry I should have made that clear. I will update the op to make that clear
Just wanna make sure of something. First, I flash the first download files through modded doin, then afterwards, flash the second file in ff?
AngelIsL33T said:
Just wanna make sure of something. First, I flash the first download files through modded doin, then afterwards, flash the second file in ff?
Click to expand...
Click to collapse
Nope, only need the tar file bud. The old boot.img file is just basically the previous version of this.
AngelIsL33T said:
Just wanna make sure of something. First, I flash the first download files through modded doin, then afterwards, flash the second file in ff?
Click to expand...
Click to collapse
The old image is actually part of the new tar, do you will have it anyway . I packaged it in Odin this time because there are some pieces of firmware FF either can't or warns against using it for. Plus one clean simple tar seemed easier, no?
Do you see the boot.img in the op? I thought I nixed all the instances of the link but I may have missed one.
I almost rewrote all the old text to reflect now but it felt like editing history so I tried to preserve what made the most sense still. It sounds like it's still a little confusing sobrskr another crack at it shortly.
Please let me know if you have any trouble! I'll be here to help all evening