Greetings all! I have tried to read as many threads as I could, but is it correct that currently, there is not a viable TWRP for the WiFi version of the S7+ ?
I have my S7+ rooted and everything seems to be working great, and I have been doing this with android devices for a long time. I am genuinely shocked that a WiFi device does not have TWRP available, but the cellular version of the same device does? Usually it is the other way around!
Thanks, I'd appreciate any confirmation on this.
There is no such "rule" which device is gonna get the TWRP first. It all depends on the "Dev" who makes the TWRP and which device he has. If it happens that the DEV has the Cellular version, then there it is, he makes a twrp for his device. Sometimes they do for both if they have people who can test properly and take/send logs. No rules in this, it's a coincidence.
Related
I just recieved a replacement Unit for my malfunktioning HDX 9.8. Current version on this thing is 14.3.0.2_user_302075320. I have just started it up to check the version and have not yet registered it or even connected it to a network. This time around I would like to be in control of things! What would be the appropriate thing to do with this version, if I want to :
1. Root it and keep it from auto-updating.
2. getting it safestrapped to be able to...
3. ...flash custom roms safely in the future,
Ive been looking around these forums to find out myself but information is scrambled and depending on version numbers and other things. The learning curve sure is steep here
/sebastian
My humble suggestion is to install TWRP (here) followed by the ROM of your choice. Each has pros/cons....stock is also an option. You will need to do some reading, plan carefully and be prepared for the unexpected. Keep that pup in 'airplane' mode to prevent debilitating OTA updates until you identify and apply an appropriate blocker. I think you will find the community quite willing to help with specific questions but you probably won't get a start-to-finish recipe. Lots of reading ahead but the rewards are worth it IMO. Good luck!
Thanks for the reply! Good to hear that airplane mode can be a temporary update blocker! I'll do some more reading up on TWRP to begin with then.
Device Manager said:
Thanks for the reply! Good to hear that airplane mode can be a temporary update blocker! I'll do some more reading up on TWRP to begin with then.
Click to expand...
Click to collapse
Be carefull and dont use airplane mode to block updates while in stock! At least one user reported that amazon can update your kindle even with airplane mode on! If you setup your wifi already, just turn-off / forget your wifi while in stock, or use OTA blocker ...
Forgetting all WiFi networks is good advise indeed! I have seen Kindle readers pop out of airplane mode on occasion; suppose the same could happen on Fire/HDX tablets although I have not personally experienced this. OTA blocker is great (what I use) but obviously requires root.
OK, thanks everyone!
I'm good so far! I first rooted with towelroot then went for the toolkit. Installed the ADB drivers, then SU, then OTA blocker. After that I Installed safestrap, made a backup and a new rom-slot, to which I restored the recovery. So now I should be OTA blocked and have a stock ROM recovery option. I hope I haven't made any terrible mistakes yet
I'm a happy camper! (as of yet
Now I will do som reading up on HDXposed and custom roms I guess. Does anyone have any suggestions? Is the Nexus rom a good option?
Thanks again!
Ok Iplayed around some and read up some more. Now I can definitely see the benefits of going for the custom recovery! I have a few remaining questions about the specifics about flashing TWRP that I cant seem to find the answer to. Hope somewone would be kind enough to help or point me in the right direction.
Do I need to uninstall safestrap before (or after) flashing TWRP?
Is "Copy image to SD-card root" the same as copying it to the device file system root? As in draging and dropping in windows perhaps?
What is the tool for issuing the commands mentioned in the TWRP install guide? (I have used ADB but only via the Toolkit aplication and I havent seen a command prompt for this around).
Sorry for lacking in some fundamentals on this... (being a noob on android stuff)
Never mind the above. All sorted. Up and running HDX Nexus 2.0.5. Great stuff!
Okay I'm hoping someone can clear up my confusion.
I've got a 8.9 HDX 2.2 (16gb) I managed to pick up for $40 new. Unfortunately, it auto updated extremely quickly on me and I'm now on system build 14.3.2.5_user_325001120 from 2014.08.05.
I've been reading the forums on here for the past couple of days, and this appears to be the exact timeframe in which all easily searchable information vanishes on me. I'd like to completely replace the stock OS with the nexus 4.2.2 one ggow has been working on - assuming it's possible of course.
My problem has been that depending on the thread I search through rooting is either "possible", "totally impossible", "extremely difficult", or "well, I've got it working ...". Things would be different apparently if I had almost any other build of the stock OS other than the version I'm on:
3.2.4? No problem
3.2.8? Perfectly rootable, no problem there either
anything larger or smaller - also no problem since you can either update or rollback (at least on the Thor).
Anyway, before I get too much more confused, can someone give me a quick definitive yes or no, and then point me at the right starting point? I have no troubles reading more before starting, I just wanna be sure I'm reading intelligently.
Thanks in advance.
Yes, 3.2.5 is easy to root with towelroot. Get the tool here
http://forum.xda-developers.com/kindle-fire-hdx/development/hdx-toolkit-revived-gui-t2987043
Once you're rooted, enable airplane mode immediately. Next you'll probably want to get downgraded to 3.2.3 and install TWRP so you can use any custom ROM, so have a read here
http://forum.xda-developers.com/showthread.php?t=2782159
And here
http://forum.xda-developers.com/kin...ecovery-twrp-recovery-2-8-1-0-apollo-t2991155
thanks for the assist
derpadoodle said:
Yes, 3.2.5 is easy to root with towelroot. Get the tool here
http://forum.xda-developers.com/kindle-fire-hdx/development/hdx-toolkit-revived-gui-t2987043
Once you're rooted, enable airplane mode immediately. Next you'll probably want to get downgraded to 3.2.3 and install TWRP so you can use any custom ROM, so have a read here
http://forum.xda-developers.com/showthread.php?t=2782159
And here
http://forum.xda-developers.com/kin...ecovery-twrp-recovery-2-8-1-0-apollo-t2991155
Click to expand...
Click to collapse
Thanks, I'm checking it all out now. Hopefully I'll get it all to work. Proceeding slowly, as this was the last tablet in the valley we could find at this price (and we checked pretty hard - $40 is a steal for a new in box, even if it is the older 2.2 version).
I've mostly understood the guides, there are a couple of places where I get lost by someone who doesn't speak English as a primary language - but you've definitely pointed me in the right direction. I should have this done in a couple of days.
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.
Hi there,
I've been cruising these forums for a while and have managed to root my device, get adb setup, and TWRP installed. An unfortunate bit seems to be that you cannot leave TWRP installed and actually boot the device. I managed to get stuck in a boot loop having not restored the 5.4.1 bootloaders. I turned the device off and rebooted into TWRP, flashed the 5.4.1 bootloaders, rebooted, and I'm golden. However, this doesn't really get me anywhere.
So my goal here is to just wipe all this FireOS crap and turn this tablet into a normal android tablet. I've seen plenty of posts about it but cannot seem to find any single post that would achieve this for my specific device and software version. So I'm coming here for help.
Mostly, what I have done so far has come from this thread: http://forum.xda-developers.com/fire-hd/general/how-to-upgrade-to-lollipop-root-gapps-t3163950
Unfortunately, from what I can tell, this process does not remove FireOS and replace it with stock Lollipop, it just updates you to 5.1.2 (which I'm already at) and installs GAPPS. It does not really have a "pure" Android install and it somehow retains the FireOS as the primary OS.
Now, please correct me if I am wrong here with any of the above (this is not a hobby of mine) but since I've rooted a few devices before I figured I could handle it. It seemed like a bargain getting this Fire HD 7 used for like $64... if only I can get it onto stock Android. I'm basically trying to make it a Nexus 7.
Since I CAN get into TWRP, I figure I should just be able to flash a custom ROM right? I've just been having a really hard time finding a stock Lollipop ROM specifically for my device. From what I've heard, flashing the new ROM is the most error-prone part of this type of stuff and can totally brick the device if it were not meant for it. If that did happen, I would need to be able to boot the device back up, get an adb connection, run the scripts that flash the correct bootloaders (post #2, section 101, from the link above) so I can reboot into TWRP and fix it. Perhaps understandably so, I've been very hesitant to just go trying things willy-nilly that I don't fully understand.
Could anyone offer any assistance? Perhaps just point me in the right direction? I've probably read most of the threads you'll likely link, so a short bit of context to how something pertains to my specific device as well as the link could help me significantly. The guides that people write usually contain updates and are quite difficult to follow to the "T" and half the time I'm not even sure something I'm doing actually pertains to my device.
[EDIT] I found this video (https://www.youtube.com/watch?v=_c5hHSCO_o8) but it looks like he's doing that on a previous generation Fire so, again, I'm not sure it will work and don't want to try and then brick it.
nedwards said:
Hi there,
I've been cruising these forums for a while and have managed to root my device, get adb setup, and TWRP installed. An unfortunate bit seems to be that you cannot leave TWRP installed and actually boot the device. I managed to get stuck in a boot loop having not restored the 5.4.1 bootloaders. I turned the device off and rebooted into TWRP, flashed the 5.4.1 bootloaders, rebooted, and I'm golden. However, this doesn't really get me anywhere.
So my goal here is to just wipe all this FireOS crap and turn this tablet into a normal android tablet. I've seen plenty of posts about it but cannot seem to find any single post that would achieve this for my specific device and software version. So I'm coming here for help.
Mostly, what I have done so far has come from this thread: http://forum.xda-developers.com/fire-hd/general/how-to-upgrade-to-lollipop-root-gapps-t3163950
Unfortunately, from what I can tell, this process does not remove FireOS and replace it with stock Lollipop, it just updates you to 5.1.2 (which I'm already at) and installs GAPPS. It does not really have a "pure" Android install and it somehow retains the FireOS as the primary OS.
Now, please correct me if I am wrong here with any of the above (this is not a hobby of mine) but since I've rooted a few devices before I figured I could handle it. It seemed like a bargain getting this Fire HD 7 used for like $64... if only I can get it onto stock Android. I'm basically trying to make it a Nexus 7.
Since I CAN get into TWRP, I figure I should just be able to flash a custom ROM right? I've just been having a really hard time finding a stock Lollipop ROM specifically for my device. From what I've heard, flashing the new ROM is the most error-prone part of this type of stuff and can totally brick the device if it were not meant for it. If that did happen, I would need to be able to boot the device back up, get an adb connection, run the scripts that flash the correct bootloaders (post #2, section 101, from the link above) so I can reboot into TWRP and fix it. Perhaps understandably so, I've been very hesitant to just go trying things willy-nilly that I don't fully understand.
Could anyone offer any assistance? Perhaps just point me in the right direction? I've probably read most of the threads you'll likely link, so a short bit of context to how something pertains to my specific device as well as the link could help me significantly. The guides that people write usually contain updates and are quite difficult to follow to the "T" and half the time I'm not even sure something I'm doing actually pertains to my device.
[EDIT] I found this video (https://www.youtube.com/watch?v=_c5hHSCO_o8) but it looks like he's doing that on a previous generation Fire so, again, I'm not sure it will work and don't want to try and then brick it.
Click to expand...
Click to collapse
You seem to have the gist of it, which is that what you want to do can't be done. There is only one ROM for this device--CM11, here: http://forum.xda-developers.com/fire-hd/orig-development/rom-cm-11-kindle-hd6-t3270138 --and it is not fully working. No one's ever posted here about successfully installing a ROM for a different device, only about bricks as a result of trying.
@xSentinel has been disabling all possible apps, while still keeping the device running. His goal may be the same as yours(?). He started a thread here, but has since got a lot more disabled: http://forum.xda-developers.com/fire-hd/help/5-1-2-bloatware-safe-to-remove-apps-2014-t3355167. Might want to post there and see what he's up to.
DoLooper said:
You seem to have the gist of it, which is that what you want to do can't be done. There is only one ROM for this device--CM11, here: http://forum.xda-developers.com/fire-hd/orig-development/rom-cm-11-kindle-hd6-t3270138 --and it is not fully working. No one's ever posted here about successfully installing a ROM for a different device, only about bricks as a result of trying.
@xSentinel has been disabling all possible apps, while still keeping the device running. His goal may be the same as yours(?). He started a thread here, but has since got a lot more disabled: http://forum.xda-developers.com/fire-hd/help/5-1-2-bloatware-safe-to-remove-apps-2014-t3355167. Might want to post there and see what he's up to.
Click to expand...
Click to collapse
Ah, that is unfortunate. At least you've helped me to understand that my goal cannot be fully realized. I probably should have done a bit more research before purchasing the Fire tablet. I'm really just looking to set up an in-car tablet to handle Torque guages, navigation, and music. Perhaps I should just return the Kindle and shell out the extra cash for a Nexus 7. I think I could probably get a refurbished one for a price similar to what I paid for the Fire. I'll poke around xSentinel's thread a bit and see what I'm up against first though. If it comes down to it, the headache of dealing with Amazon's locked down devices might just outweigh the extra money/hassle of a Nexus 7 and a return.
nedwards said:
Ah, that is unfortunate. At least you've helped me to understand that my goal cannot be fully realized. I probably should have done a bit more research before purchasing the Fire tablet. I'm really just looking to set up an in-car tablet to handle Torque guages, navigation, and music. Perhaps I should just return the Kindle and shell out the extra cash for a Nexus 7. I think I could probably get a refurbished one for a price similar to what I paid for the Fire. I'll poke around xSentinel's thread a bit and see what I'm up against first though. If it comes down to it, the headache of dealing with Amazon's locked down devices might just outweigh the extra money/hassle of a Nexus 7 and a return.
Click to expand...
Click to collapse
You also might check out the Fire forums. (I got a refurb for $30.) They have a few ROMs and are doing interesting things. Also, lots of activity over there.
Some people may strive to be "purists", but remaining pragmatic is a recipe for relatively happy life
Because the bootloaders are locked, there are very limited options on what to boot. There was some lucky bug in the earlier bootloaders that gifted us with the ability to boot an unsigned TWRP using 4.5.3 bootloaders. But boot.img always had to be signed, or it would not boot.
To create a custom OS, one needs to match the custom ROM to the existing boot.img from a given version of FireOS. Kind of pain in the @ss, don't you agree ?
Instead, however, one can just keep FireOS 5, and tweak it to behave like almost a pure Android. And it's not hard ! So why chase the unicorns when all you want is right in front of you !
I'm currently working on completing a CM11 port - as someone else mentioned it needs to use the stock boot.img though, so I have to heavily modify CM code in order to get it to work with full functionality. CM11 does run very well on the device though, and it's much snappier than Fire OS imo.
In theory this device could use something like safestrap to boot unsigned boot images, however I probably won't bother writing something like that until I have CM11 at 100% functionality (currently my build is at about 60% if I were to estimate).
I think the guy who posted the first CM11 port is now working on porting CM12, although it's a massive pain to test.
nedwards said:
Ah, that is unfortunate. At least you've helped me to understand that my goal cannot be fully realized. I probably should have done a bit more research before purchasing the Fire tablet. I'm really just looking to set up an in-car tablet to handle Torque guages, navigation, and music. Perhaps I should just return the Kindle and shell out the extra cash for a Nexus 7. I think I could probably get a refurbished one for a price similar to what I paid for the Fire. I'll poke around xSentinel's thread a bit and see what I'm up against first though. If it comes down to it, the headache of dealing with Amazon's locked down devices might just outweigh the extra money/hassle of a Nexus 7 and a return.
Click to expand...
Click to collapse
Just so you know it can be done, I am running Torque on a Fire HD 6 and still running thr Fire O.S. There is also a similar app to Torque Pro in the Amazon app store - search for OBD and it should see it (sorry I can't give the name, soft bricked the device and won't be near a computer for another 4 days) It is similar in capabilities to Torque Pro, and runs around the same price.
Good afternoon all,
For starters, please excuse any improper protocol with this post. Ironically, I am a programmer myself (C++, C#, JS, ASP.NET) but I am unaccustomed to posting on forums. Aside from one on StackOverflow and one on the MS Community help forums I am new to this. However, I am coming out of my cave as it occurs to me that learning, and possibly assisting, with Android development on such a level as this is of great interest to me; so I might as well start learning!
I decided to jump in with an old S4 (SCH-I545) to see if I could get that rooted. I was successful with the very useful tools on this site but now I am attempting to install Magisk (seems "system-less" is the new thing). I have come to conclude that I must install a new recovery on my device for this and it sounds like TWRP is the recommended choice for installing Magisk. Unfortunately, when attempting to flash the tar in the most recent version of Odin, I only get an error of "SECURE CHECK" failure.
My research on the threads seem to indicate that you cannot change the recovery software on that particular model (due to not being able to change the bootloader I think?). Anyway, I thought it was time to stop and confirm with the experts if something like Magisk can even be installed on the SCH-I545. Thank you for any advice you can offer.
References:
https://forum.xda-developers.com/showthread.php?t=2398311
https://forum.xda-developers.com/showthread.php?t=2398311
https://forum.xda-developers.com/ga...tall-custom-recovery-twrp-verizon-s4-t3631776
https://forum.xda-developers.com/ga...tried-to-flash-twrp-rooted-galaxy-s4-t3547458
https://forum.xda-developers.com/showthread.php?t=2292565
https://forum.xda-developers.com/galaxy-s4-verizon/general/how-to-make-verizon-sch-i545-att-t3267687 (this last one is about changing the carrier but I thought it would be a good read to see if they had to do anything with the bootloader)