Related
I get my GT in a day or so. I've been reading lots of horror stories and dire warnings about what not to do. These are very useful and I thank those that are trying to protect the nOObs. I've been modding phones since the VX6600 so I know how this goes.
I'm concerned about the early ROM version woo-Tabs have been turning up with.
Is there some advice on how to get these 32xx ROMS to 3588?
Should we wait until the OTA updates pushes to the device and see what where that gets the device?
Can we install the .08 beakit (sp?) right away and we're off and modding?
What is the main difference between nvflash and adb?
Thanks,
Matt
This is what I would recommend:
- OTA update to 3588 first. You want the latest stock, right off the bat (this is what the vendor wants, as well). I would argue that updating to 3588 first is absolutely positively CRITICAL. The reason why is that their 3991 UAT seemed to indicate that 3588 is possibly a "gateway" ROM to get users to their 1.2 development branch (that's assuming they don't kill it, of course). 3588 recovery is the ONLY recovery that worked for the 3991 UAT.
- If you install clockworkmod .8, just understand the risks. See above, as an example. I've stated this a few times, but cwm does not support updating the bootloader. So, if a future ROM or mod requires it, you could have problems. Other than the 3991 UAT that we've sequestered, I'm not aware of a ROM that requires this yet.
- adb and nvflash are very different tools. adb is a remote shell and is built into Android. It's like a SSH tool, that's the closest comparison. There's a lot of documentation not just here in XDA, but on other sites.
nvflash is specific to Tegra 2 devices only. It's a low-level tool for formatting and re-creating the partition structure. Since it's Tegra 2 based, the only documentation you'd find is on devices like the GTAB. There's a good HOWTO that "Rev" wrote, but has my name attached it to in the Development section.
Never mind... Roebeet beat me to it...
thanks roe
one followup please.
As I understand it... the only thing GT uses nvflash is repartitioning?
this is required because different roms required different partion structures?
ok, that was two
Being newly interested in rooting and tweaking my devices (started with my S3) there are a lot of terms that are mentioned in customizing threads that I do not understand, and a lot of those threads don't have detailed instructions for someone that's new to tweaking. Is there one post somewhere on xda that lists terms, methods, etc for newcomers like me?
I don't trust any forum other than xda because I simply think its the best forum for tweaking, etc so I don't really trust links outside xda. I also know that the way some things need to be done is device specific.
I'm confused about how to "flash" something in "recovery' (such as removing the wifi notification thread), flashing a custom recovery, using Goomanager to flash, etc. Don't get me wrong; I can follow detailed instructions as long as they are there......but if they aren't, that leaves me and a great deal of newcomers in the dark.
Some of these things are done via the phone and some have to be done via PC....and many times there aren't detailed instructions so I'm unsure what I an supposed to do and don't want to brick a $700 device.
So....is this information contained in all separate posts throughout the forum? Or is there one thread per device that details it? Being as some of these things are device specific, I'm hesitant to even look in other device forums.
Thanks for reading, and any assistance is appreciated.
wolfgrrl said:
Being newly interested in rooting and tweaking my devices (started with my S3) there are a lot of terms that are mentioned in customizing threads that I do not understand, and a lot of those threads don't have detailed instructions for someone that's new to tweaking. Is there one post somewhere on xda that lists terms, methods, etc for newcomers like me?
I don't trust any forum other than xda because I simply think its the best forum for tweaking, etc so I don't really trust links outside xda. I also know that the way some things need to be done is device specific.
I'm confused about how to "flash" something in "recovery' (such as removing the wifi notification thread), flashing a custom recovery, using Goomanager to flash, etc. Don't get me wrong; I can follow detailed instructions as long as they are there......but if they aren't, that leaves me and a great deal of newcomers in the dark.
Some of these things are done via the phone and some have to be done via PC....and many times there aren't detailed instructions so I'm unsure what I an supposed to do and don't want to brick a $700 device.
So....is this information contained in all separate posts throughout the forum? Or is there one thread per device that details it? Being as some of these things are device specific, I'm hesitant to even look in other device forums.
Thanks for reading, and any assistance is appreciated.
Click to expand...
Click to collapse
Well, this can be a complex arena to play in. For the S4, you'll want to download Odin v3.07 and a copy of the stock ROM just in case you break something.
> http://forum.xda-developers.com/showthread.php?t=2289325
> http://forum.xda-developers.com/showthread.php?t=2189539
ROM = read-only memory - this is the part of your phone's internal storage you're not really supposed to be able to play with (like /system, or the phone's radio for example)
The act of "flashing" is writing data to ROM
Recovery just means that you should always be able to boot your device into this mode to RECOVER from a software problem; IE: flashing a bad ROM (IE: one that doesn't work and you can't start your phone anymore).
I don't really know a whole lot more than that, I just poke around and pretend like I do =)
OverkillSD said:
Well, this can be a complex arena to play in. For the S4, you'll want to download Odin v3.07 and a copy of the stock ROM just in case you break something.
> http://forum.xda-developers.com/showthread.php?t=2289325
> http://forum.xda-developers.com/showthread.php?t=2189539
ROM = read-only memory - this is the part of your phone's internal storage you're not really supposed to be able to play with (like /system, or the phone's radio for example)
The act of "flashing" is writing data to ROM
Recovery just means that you should always be able to boot your device into this mode to RECOVER from a software problem; IE: flashing a bad ROM (IE: one that doesn't work and you can't start your phone anymore).
I don't really know a whole lot more than that, I just poke around and pretend like I do =)
Click to expand...
Click to collapse
Thanks As I learn more, I think I'm going to make a post that contains everything I learn, so others have it all in one place.
Well, there's a LOT to learn...like I said; complex arena. So much so that there's no way to make a single post take you from newbie to knowledgeable newbie in one read.
Then there's Google;
"what is rom"
"what is flashing rom"
"what is recovery mode android"
Eliminates the need for said post
Plus, by the time you get it all written, it will have all changed ^_^
Hi there,
I'm quite new in the kindle hdx world and wondering, if there are still some activities of developers aiming for unlocking the bootloader of our beloved hdx with version 13.3.2.8 and higher? At least for me, I would love to see the bootloader unlocked, so that we can flash a custom recovery on our devices.
Best regards,
scotch
scotchbonnet43 said:
Hi there,
I'm quite new in the kindle hdx world and wondering, if there are still some activities of developers aiming for unlocking the bootloader of our beloved hdx with version 13.3.2.8 and higher? At least for me, I would love to see the bootloader unlocked, so that we can flash a custom recovery on our devices.
Best regards,
scotch
Click to expand...
Click to collapse
It's not a development issue. The android vulnerability that was exploited to permit bootloader signature bypassing and unlocking was patched by Amazon in 13.3.2.4. Some clever individuals figured out how to 'rollback' 3.2.4-3.2.6 to earlier levels which could then be exploited. Amazon noticed and implemented anti-rollback protection in 3.2.7 and above.
To do what you ask one of the following must happen:
- someone figures out how to circumvent the anti-rollback protection (some claim to have done it but I have yet to see mainstream evidence)
- a new vulnerability is found which can be successfully exploited
I personally believe both are long shots. Google and Amazon have been buckling down on vulnerabilities making it more difficult to develop exploits when a weakness is identified. Sure hope I'm wrong.
If you don't mind, can you link me to the rollback? I'm feeling left out here on 3.2.4, thanks!
fdigl said:
If you don't mind, can you link me to the rollback? I'm feeling left out here on 3.2.4, thanks!
Click to expand...
Click to collapse
Details here. Note there are sections for 3.2.4 (titled "earlier version than 1x.3.2.5") and 3.2.5-3.2.6 (grey background). Read carefully. Although you can downgrade directly from 3.2.4 I strongly suggest upgrading to 3.2.5 (instructions) and then rollback from there as it avoids messing with build.prop which seems to be the source of many failed rollback attempts with varying outcomes up to and including unrecoverable bricks.
Additional notes:
- there are no tutorials; you must read up on details. Information is disorganized and spread across many threads
- uninstall safestrap (if necessary) using the original apk. It is not needed going forward.
- upgrading to 3.2.5 will trash root and reenable OTA. Keep wifi off (better yet remove all wireless profiles). Use HDX Toolkit to reroot and block OTA
- don't mess with build.prop
- flashing involves risk that can permanently disable (brick) your device even when executed correctly. Read up in advance and understand what your are doing. If things go wrong don't panic, don't try random stuff and don't do a system reset/restore. Post what's happening (details matter) and someone will try to help.
fdigl said:
If you don't mind, can you link me to the rollback? I'm feeling left out here on 3.2.4, thanks!
Click to expand...
Click to collapse
I made somewhat of a guide to get out of .3.2.4 into cm12. I would read each link first to see what you are going to end up doing. Lots of steps, but its not so hard to do. Like Davey said to me if you get stuck, wait and ask questions.
http://forum.xda-developers.com/showpost.php?p=60186871&postcount=82
Thanks! I'll definitely give this a go.
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.
Hi,
I have read the ROM porting guides on https://forum.xda-developers.com/showthread.php?t=2073370
AND ....... they are all useless. There are a dozen questions that need answers BEFORE you can start using any of these guides!
1) Where to get a ROM
2) How to check if the ROM is compatible with your device
3) How to chose between available ROMs
4) How to check for malware BEFORE installing (like advertising malware that even pitches up in the ROMs that emulators use and those people are theoretically the experts)
5) Which rootkits are recommended for computer savvy people who have never ported a ROM before (which is theoretically what the guides are supposedly written for)
6) What danger signs to look out for during the process
7) What actions must be avoided at all costs during the process so you dont burn out the bootstrap
I am sure there are more questions that should be answered during the guides tooo.
All of the guides start in the middle with almost no necessary information supplied.