Related
For the last two years I have been going back and forth between my Note 2 that was Stock Rooted on 4.1.2 and my un-Rooted Note 2 fully stock on 4.4.2. Each had their advantages
I had all but given up
Now thanks to GhettoRoot I have the best of both worlds.:highfive:
I would like to hear what is COOL about having Root on 4.4.2.
You newbies to 4.4.2 check out the Active apps widget . it only takes up one space on the home screen. It is a must have.
Because of GhettoRoot XDA will need to redo Most of the Verizon Note 2 Forum. AdamOutler's Root is obsolete, Thanks for the good times Adam
doctor-cool said:
For the last two years I have been going back and forth between my Note 2 that was Stock Rooted on 4.1.2 and my un-Rooted Note 2 fully stock on 4.4.2. Each had their advantages
I had all but given up
Now thanks to GhettoRoot I have the best of both worlds.:highfive:
I would like to hear what is COOL about having Root on 4.4.2.
You newbies to 4.4.2 check out the Active apps widget . it only takes up one space on the home screen. It is a must have.
Because of GhettoRoot XDA will need to redo Most of the Verizon Note 2 Forum. AdamOutler's Root is obsolete, Thanks for the good times Adam
Click to expand...
Click to collapse
AdamOutler's Root is obsolete, Thanks for the good times
Click to expand...
Click to collapse
Adam has done A LOT for this community especially for Samsung phone in general.. His work is NOT obsolete and he still very involved on this forum. I am not friends with him or do I know him but he was the master mind behind unlocking/exploiting Verizons bootloader.. which currently on 4.3 and 4.4.3 is still not possible. This is most likely do to him not having the phone and the phones age..
SOo I hope I got the wrong impression from your statement.. Bc that man you mentioned.. Is a LEGEND.. Hands down
Just to confirm, Ghettoroot does not work on 4.4.2 baseband ND7. Is that correct?
Sent from my Galaxy Note 2 using Tapatalk
11/9/14 Update. I successfully rooted with GhettoRoot with Note 2 running Android 4.4.2 and baseband ND7 (Verizon). Required SDK install and Note 2 Android drivers for Windows first.
jtsmall said:
11/9/14 Update. I successfully rooted with GhettoRoot with Note 2 running Android 4.4.2 and baseband ND7 (Verizon). Required SDK install and Note 2 Android drivers for Windows first.
Click to expand...
Click to collapse
I also had success using GhettoRoot from this post:
http://forum.xda-developers.com/showpost.php?p=55210343&postcount=27
ADB from this post:
http://forum.xda-developers.com/showthread.php?t=2588979
Koush's universal android drivers from here:
https://github.com/koush/UniversalAdbDriver
Yes, that's it. Samsung's drivers work for me.
Sent from my Galaxy Note 2 using Tapatalk
travisn000 said:
I also had success using GhettoRoot from this post:
http://forum.xda-developers.com/showpost.php?p=55210343&postcount=27
ADB from this post:
http://forum.xda-developers.com/showthread.php?t=2588979
Koush's universal android drivers from here:
https://github.com/koush/UniversalAdbDriver
Click to expand...
Click to collapse
crossing fingers
shissler said:
crossing fingers
Click to expand...
Click to collapse
woot woot im rooted..lol now what way to go
shissler said:
woot woot im rooted..lol now what way to go
Click to expand...
Click to collapse
I used it to replace the APN config file in my wife's phone for use on other carriers (T-Mobile & international use):
http://forum.xda-developers.com/showpost.php?p=57070787&postcount=7
It worked great for up to HSDPA+ speeds, but no LTE.. ..then she left the phone on top of her car; it fell off in traffic and got run over.. maybe this will help someone else!
Before it got smashed, I had planned on trying the following thread out next (for the VZW Note 3) to see if I could get LTE working on T-Mobile:
http://forum.xda-developers.com/showthread.php?t=2530523
travisn000 said:
I also had success using GhettoRoot from this post:
http://forum.xda-developers.com/showpost.php?p=55210343&postcount=27
ADB from this post:
http://forum.xda-developers.com/showthread.php?t=2588979
Koush's universal android drivers from here:
https://github.com/koush/UniversalAdbDriver
Click to expand...
Click to collapse
nothing works for me.
I have Verizon Note 2 with version 4.4.2 and ND7
it says "error: device not found" 6 times
samloves said:
nothing works for me.
I have Verizon Note 2 with version 4.4.2 and ND7
it says "error: device not found" 6 times
Click to expand...
Click to collapse
I followed travis's post and mine is rooted now with superuser access.
My only question now is what method do we use to install twrp or cwm on this nd7 rooted note 2 with 4.4.2?
Can we use odin and just flash the latest twrp or is there another workaround?
zbomb5610 said:
I followed travis's post and mine is rooted now with superuser access.
My only question now is what method do we use to install twrp or cwm on this nd7 rooted note 2 with 4.4.2?
Can we use odin and just flash the latest twrp or is there another workaround?
Click to expand...
Click to collapse
In order to install a custom recovery, you have to have an unlocked bootloader. At this moment, there is no do it yourself method to unlock the bootloader on factory stock 4.4.2, so you can't install CWM/PHILZ or TWRP. For about $75 I think... you can send your phone off to a company that uses special equipment to downgrade your phone to 4.1.2... then you would be able to unlock the bootloader.... Otherwise, the most you can do right now is root the device and make modifications that don't require unlocked bootloader (e.g. debloat, install Xposed modules, etc...). An XDA user named Beastmode is working on trying to get a modified version of TWRP called Safestrap working for 4.4.2 which wouldn't require an unlocked bootloader, so you may want to keep an eye on that thread here: http://forum.xda-developers.com/showthread.php?p=57190369
Thanks for the reply. I figured that was the case. I had 4.1.2 a few days ago also and figured "hey, i haven't updated in over a year" and didn't read into it enough and then upgraded to stock ota 4.4.2 so that sucks. I guess I can live with it like this for now till a fix comes out if one does.
also having trouble
I also have been having trouble rooting my note2 with 4.4.2. I followed travis' approach and I got the 6 device not found errors. Am I not installing the correct drivers? Any help or information is greatly appreciated.
UPDATE: Just got it to work. Will post soon what I was doing wrong and what I did to correct it.
I was able to get GhettoRoot to find my device once and the install failed. Now no matter what I do including removing and adding drivers it says it cannot see your Android device. Is there a trick i'm missing?
travisn000 said:
I also had success using GhettoRoot from this post:
http://forum.xda-developers.com/showpost.php?p=55210343&postcount=27
ADB from this post:
http://forum.xda-developers.com/showthread.php?t=2588979
Koush's universal android drivers from here:
https://github.com/koush/UniversalAdbDriver
Click to expand...
Click to collapse
---------- Post added at 08:43 PM ---------- Previous post was at 08:37 PM ----------
I had something similar happen to me. The very first time I ran GhettoRoot it found my device and tried to install but failed. Now, it won't find device no matter what I do.
IceCo1d said:
I also have been having trouble rooting my note2 with 4.4.2. I followed travis' approach and I got the 6 device not found errors. Am I not installing the correct drivers? Any help or information is greatly appreciated.
Click to expand...
Click to collapse
for me a message came up on my phone asking for permission and then i was able to root after installing the drivers.
I just had to accept on my phone first for it to actually work.
popdevil said:
I was able to get GhettoRoot to find my device once and the install failed. Now no matter what I do including removing and adding drivers it says it cannot see your Android device. Is there a trick i'm missing?
---------- Post added at 08:43 PM ---------- Previous post was at 08:37 PM ----------
I had something similar happen to me. The very first time I ran GhettoRoot it found my device and tried to install but failed. Now, it won't find device no matter what I do.
Click to expand...
Click to collapse
The part you are talking about does not come up until after the command prompt finds your device. Then you get the message to accept. That message came up the very first time but now it will not find the device for me to get to that part.
zbomb5610 said:
for me a message came up on my phone asking for permission and then i was able to root after installing the drivers.
I just had to accept on my phone first for it to actually work.
Click to expand...
Click to collapse
popdevil said:
I was able to get GhettoRoot to find my device once and the install failed. Now no matter what I do including removing and adding drivers it says it cannot see your Android device. Is there a trick i'm missing?
---------- Post added at 08:43 PM ---------- Previous post was at 08:37 PM ----------
I had something similar happen to me. The very first time I ran GhettoRoot it found my device and tried to install but failed. Now, it won't find device no matter what I do.
Click to expand...
Click to collapse
I had similar issues with some of my trials.. ...try turning developer mode off and on, plug in and then give the phone 30-90 seconds or so for installer mode to time out and verify the device is in MTP or PTP mode.
Just rooted my Note 2 running 4.4.2
Ok gang, so after about a week of trying every method to root my phone I finally got it to work. I'm going to tell you what I was doing wrong and what you can check to see where you are messing up. Hope this helps someone.
The issue I kept running into was that my device could not be found. I would run Ghettoroot and it would just tell me error device not found. This made no sense because I could get Kies to work and the bubble in the lower right corner that says installing device drivers would always succeed. However if I went into Device Manager (on the computer) there was a little yellow exclamation point next to my device. After looking in to the properties it said there were no drivers installed.
Also if you open a command prompt and type "adb devices" (with your phone plugged in) it should show you your device, if nothing comes up then the drivers are not properly installed.
So... First check that drivers are properly installed in your Device Manager (again this is on your computer), and then open a cmd window and type adb devices to see if your phone shows up. If it does then you are ready to use Ghettoroot.
I used this Ghettoroot:
http://forum.xda-developers.com/showpost.php?p=55210343&postcount=27
and the drivers I used were called:
SAMSUNG_USB_Driver_for_Mobile_Phones_v1.5.45.0 (I can't remember where I DLed it from, sorry)
Also, if you are interested. My method for figuring out what was wrong started by right clicking on the GhettoRoot .bat file to see the sequence cmd commands. They began with adb commands and I then googled to see how to check that the command would work. That is when I stumbled on the comman "adb devices" to make sure my phone was properly connected.
I hope this helps someone and if I can help in any other way just ask!
Heimdahl? Odin?
mattnmag said:
In order to install a custom recovery, you have to have an unlocked bootloader. At this moment, there is no do it yourself method to unlock the bootloader on factory stock 4.4.2, so you can't install CWM/PHILZ or TWRP. For about $75 I think... you can send your phone off to a company that uses special equipment to downgrade your phone to 4.1.2... then you would be able to unlock the bootloader.... Otherwise, the most you can do right now is root the device and make modifications that don't require unlocked bootloader (e.g. debloat, install Xposed modules, etc...). An XDA user named Beastmode is working on trying to get a modified version of TWRP called Safestrap working for 4.4.2 which wouldn't require an unlocked bootloader, so you may want to keep an eye on that thread here: http://forum.xda-developers.com/showthread.php?p=57190369
Click to expand...
Click to collapse
I've only had this phone a week. My vs980 fractured :crying: now I'm stuck with this "thing" which I've done nothing with as I'm still trying to figure out WHAT never mind how. There's so much bloat I'm thinking AOSP. But how?
So far, ghetto-root hasn't worked for me but have removed Kaspersky etc to see if that was the problem. Then worry abt boot loader. Am on Pageplus Carrier so there wont be any OTA updates
Is there any merrit in the "Heimdahl" (??) method shown here CYANOGENMOD
I've read some of people using Odin to load pre-rooted stock image (and have found the images... but... )
I bricked the vs980 playing too fast and not waiting for answers. (learned a thing or 2 unbricking it)
So am I correct in understanding that you can no longer "Drop" an Un****** version of the factory image into the phone? By any means?
THANKS
VW
Q&A for [THOR/RECOVERY LOCKED] Safestrap Recovery v3.72/v3.75 [B02 2014-07-03]
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:
Help to Uninstall SafeStrap v3.65 - Samsung S4 Active
Our young son jumped way out of his league, and installed SafeStrap 3.65 on his new Samsung S4 Active. We need to Uninstall it.
Can someone please help us with uninstall directions? (We're lost in the various directions on the thread.) THANKS!
ClearSynergy said:
Our young son jumped way out of his league, and installed SafeStrap 3.65 on his new Samsung S4 Active. We need to Uninstall it.
Can someone please help us with uninstall directions? (We're lost in the various directions on the thread.) THANKS!
Click to expand...
Click to collapse
All you have to do is open the Safestrap app and tap the "Uninstall Recovery" button.
ClearSynergy said:
Our young son jumped way out of his league, and installed SafeStrap 3.65 on his new Samsung S4 Active. We need to Uninstall it.
Can someone please help us with uninstall directions? (We're lost in the various directions on the thread.) THANKS!
Click to expand...
Click to collapse
Sounds to me like he jumped way out of your league and you're not comfortable with it. Lol.
nymica said:
Sounds to me like he jumped way out of your league and you're not comfortable with it. Lol.
Click to expand...
Click to collapse
Oh, I admit he jumped out of my league. He's gonna be a brilliant developer, I'm sure. But he's got exams in two days & hasn't done any (boring) school work in a month. It's no fun squelching his brilliance.
---------- Post added 20th October 2014 at 12:47 AM ---------- Previous post was 19th October 2014 at 11:51 PM ----------
EncryptedCurse said:
All you have to do is open the Safestrap app and tap the "Uninstall Recovery" button.
Click to expand...
Click to collapse
Thanks for the quick reply.
I can't find the "Uninstall Recovery" button. When I turn on the phone, the "SafeStrap: Disabled" screen comes on. It has 2 buttons: One says "Continue" , the other button says "Recovery". If I press "Recover" it brings up the screen in the attached photo. If I press through all the options possible, I don't find an "Uninstall Recovery" button. ???
If I press "Continue" instead, and then go to Samsung's Application Manager, the only application listed is "Samsung Applications". There's no SafeStrap application listed there.
ClearSynergy said:
Oh, I admit he jumped out of my league. He's gonna be a brilliant developer, I'm sure. But he's got exams in two days & hasn't done any (boring) school work in a month. It's no fun squelching his brilliance.
---------- Post added 20th October 2014 at 12:47 AM ---------- Previous post was 19th October 2014 at 11:51 PM ----------
Thanks for the quick reply.
I can't find the "Uninstall Recovery" button. When I turn on the phone, the "SafeStrap: Disabled" screen comes on. It has 2 buttons: One says "Continue" , the other button says "Recovery". If I press "Recover" it brings up the screen in the attached photo. If I press through all the options possible, I don't find an "Uninstall Recovery" button. ???
If I press "Continue" instead, and then go to Samsung's Application Manager, the only application listed is "Samsung Applications". There's no SafeStrap application listed there.
Click to expand...
Click to collapse
You need to install the APK.
Just to let you know, this is the Kindle Fire HDX forum. Safestrap isn't a universal solution, rather each device has its own specific version.
You should head over to this thread instead: http://forum.xda-developers.com/showthread.php?t=2448942
Problems with safetrap by booting ROM-1 (Stock ROM works)
Problems with safetrap.
Everything looks fine at my Kindle (thor) with safetrap, except, when I have restored a backup (from stock) to rom-1 and reboot my kindle fire System REcovery says, that it cannot boot. I shall reset to factory setting.
But when I go directly at bootscreen to safetrap back and aktivate the stock rom for booting, it seems to boot without problems.
How can I solve this? Before flashing a new rom I will have a backup that works.
Edit: Seems the problem is: When safetrap is enabled at booting: I have the Problems,
When safetrap is disabled (boot from stock rom): I can directly boot.
Solved the problem: I think you need 13.3.2.4 or 13.3.2.5, then safetrap works fine. Have also running new rom,
thanks.
Hi. I have the 16gig version, and when left it stock I had 10gigs left, after safestrap and putting the Nexus on it, I show only 2.44 gigs. I'm wondering how big the romslot partitions are and if they can be changed. I'm assuming that's some of the problem.
Thanks.
Anyone?
Will safestrap work with fire os 4.5.2 ?
captain_xyz said:
Will safestrap work with fire os 4.5.2 ?
Click to expand...
Click to collapse
AFAIK latest reported firmware version where safestrap v3 is working is 3.2.8
Need help rooting (& installing SafeStrap) on my Fire HDX 7"
I can't figure out how to root this thing (so that I can next install SafeStrap) and it is driving me crazy. I have looked through many threads and have tried many Google searches about how to supposedly root this device but have come up empty. I don't understand what Hashcode means when he says:
"To root, I recommend flashing SuperSU.zip from here and flash in Safestrap to the active rom-slot after flashing the ROM:"
I tried installing the file with the following command:
adb install UPDATE-SuperSU-v2.46.zip
But it keeps giving me the following error message:
file 'UPDATE-SuperSU-v2.46.zip' does not contain AndroidManifest.xml
rm failed for /data/local/tmp/UPDATE-SuperSU-v2.46.zip, No such file or directory
Please help.
---------- Post added at 02:56 AM ---------- Previous post was at 02:52 AM ----------
I am also wondering how to downgrade to an earlier version of the stock ROM. The device I am using is running Fire OS 4.5.3
WickdWzrd said:
I can't figure out how to root this thing (so that I can next install SafeStrap) and it is driving me crazy. I have looked through many threads and have tried many Google searches about how to supposedly root this device but have come up empty. I don't understand what Hashcode means when he says:
"To root, I recommend flashing SuperSU.zip from here and flash in Safestrap to the active rom-slot after flashing the ROM:"
I tried installing the file with the following command:
adb install UPDATE-SuperSU-v2.46.zip
But it keeps giving me the following error message:
file 'UPDATE-SuperSU-v2.46.zip' does not contain AndroidManifest.xml
rm failed for /data/local/tmp/UPDATE-SuperSU-v2.46.zip, No such file or directory
Please help.
---------- Post added at 02:56 AM ---------- Previous post was at 02:52 AM ----------
I am also wondering how to downgrade to an earlier version of the stock ROM. The device I am using is running Fire OS 4.5.3
Click to expand...
Click to collapse
Safestrap does not run on 4.5.3 or any version above 3.2.8.
You can't root 4.5.3 directly. You have to rollback to 3.2.8, upgrade to 4.5.2 then disable OTA (over the air updates) so Amazon doesn't push you to back up to 4.5.3 or beyond. Basic instructions here but I suggest you skim the entire thread before doing anything. Also see this if you are thinking about installing other roms and this thread if considering installing gaps on 4.5.2.
Looking for help rooting 3.2.8
Hey guys, I managed to downgrade my HDX Thor to 3.2.8 from 4.5.3 and upgraded back to 4.5.2. I rooted it and that was successfully I'm having the black screen issue after installing safestrap, namely the screen flickers a little but doesn't do anything and needs a hard reset. Booting back into fire os is fine.
So I decided to downgrade back to 3.2.8 to try installing safestrap again but can't gain root access. Any clues on rooting 3.2.8? I searched but couldn't find anything for 3.2.8 specifically, only lower or at 4.5.2.
H3rrPie said:
Hey guys, I managed to downgrade my HDX Thor to 3.2.8 from 4.5.3 and upgraded back to 4.5.2. I rooted it and that was successfully I'm having the black screen issue after installing safestrap, namely the screen flickers a little but doesn't do anything and needs a hard reset. Booting back into fire os is fine.
So I decided to downgrade back to 3.2.8 to try installing safestrap again but can't gain root access. Any clues on rooting 3.2.8? I searched but couldn't find anything for 3.2.8 specifically, only lower or at 4.5.2.
Click to expand...
Click to collapse
Safestrap does not work with 4.x.x. See previous post. Lucky you did not brick your device.
Towelroot works for rooting 3.2.8 and below.
updated source for Safestrap-thor?
I have been trying for two days, on three devices to download: "Safestrap-Thor-3.75-os3.2.4-B02.apk" from goo.im... however everytime the page loads and i get the download button, I get an error "invaildcust" message.
I have spent a good amount of time searching for alternative sources, but unforturnity been unable to locate one... I have rolled back from 4.5.3 (which was rooted, but I want a diff rom, so didnt help me much). So that I could install a different rom... I would even be happy with roll-back or upgrade to a differnt version...
In the end I want to replace fireos, the goal was to go with Ubuntu Touch... but the more I mess with this the more it seems like my Kindle isnt the right version (only seem to be otter and otter2 ports).
Sooooo if anyone could direct me on to where I can download/obtain SafeStrap, that would be a great help. Thanks
kgillette said:
I have been trying for two days, on three devices to download: "Safestrap-Thor-3.75-os3.2.4-B02.apk" from goo.im... however everytime the page loads and i get the download button, I get an error "invaildcust" message.
I have spent a good amount of time searching for alternative sources, but unforturnity been unable to locate one... I have rolled back from 4.5.3 (which was rooted, but I want a diff rom, so didnt help me much). So that I could install a different rom... I would even be happy with roll-back or upgrade to a differnt version...
In the end I want to replace fireos, the goal was to go with Ubuntu Touch... but the more I mess with this the more it seems like my Kindle isnt the right version (only seem to be otter and otter2 ports).
Sooooo if anyone could direct me on to where I can download/obtain SafeStrap, that would be a great help. Thanks
Click to expand...
Click to collapse
I checked the Goo.im link and they seem to be having issues with it right now. I get the same "invalid cust" as you do too. I've uploaded "Safestrap-Thor-3.75-os3.2.4-B02.apk" to my Google Drive for you, hope that helps.
I can't post links as I don't have 10 posts yet, you just have to remove the spaces I added to the link below. Gotta help another out you know!
https:// drive.google.com /file/d/ 0Byd6tCdgX3HpNUF2YlFaRHlfcEE /view?usp=sharing
H3rrPie said:
I checked the Goo.im link and they seem to be having issues with it right now. I get the same "invalid cust" as you do too. I've uploaded "Safestrap-Thor-3.75-os3.2.4-B02.apk" to my Google Drive for you, hope that helps.
I can't post links as I don't have 10 posts yet, you just have to remove the spaces I added to the link below. Gotta help another out you know!
https:// drive.google.com /file/d/ 0Byd6tCdgX3HpNUF2YlFaRHlfcEE /view?usp=sharing
Click to expand...
Click to collapse
H3rrPie thanks alot for apk :highfive:
kgillette said:
H3rrPie thanks alot for apk :highfive:
Click to expand...
Click to collapse
No problem, I hope that helps you out. Not sure about Ubuntu touch though. I may be wrong and it might have been a new development but I haven't seen it here yet.
Q&A for [TOOL] HDX ToolKit v0.94
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:
adb
Successfully rooted with adb!
Where is the folder of adb? I want to use adb driver in console.
---------- Post added at 07:26 AM ---------- Previous post was at 07:14 AM ----------
Problem solved. C:\Users\%username%\AppData\Local\Temp\afolder
Cannot detect device
Hi, I tried to install the ADB driver but it never shows as "Device Updated".
Also, when I tried to do Towelroot or anything else afterwards, the computer can't seem to detect the Kindle Fire HDX.
I have already enabled the ADB and Apps from Unknown Source. Please help.
Thanks and regards
Fire OS 4.5
I just bought my 4th Gen HDX 8.9 and I am guessing the Fire 4.5 version isn't supported yet by your tool? I also can't seem to find anywhere it states the long form software version running. I did try running through the various steps and I wasn't able to get KFHDX to see my device properly. Keeps saying waiting for device. Any idea or anything I can do to help speed up the rooting available for this version?
KFHDX 8.9 (2014 version) root-ability?
I just got 2 KFHDX 8.9s, which are the latest 2014 versions. I doubt this model is still called "Apollo", does anyone know?
In any case, it arrived on FireOS 4.5. I don't see anywhere on this forum that this can be rooted... Can it? Anyone know?
Thanks.
Update of KFDX root kit
Thanks for the update. Just need to know why the files from the main and mirror sites are different. The one from the main site has a "zip.exe" extension while the one from the mirror site is a regular "zip" file. The first was flagged by AVG as a threat while there was no problem with the one from the mirror site.
lennV said:
Thanks for the update. Just need to know why the files from the main and mirror sites are different. The one from the main site has a "zip.exe" extension while the one from the mirror site is a regular "zip" file. The first was flagged by AVG as a threat while there was no problem with the one from the mirror site.
Click to expand...
Click to collapse
The files are not different you clicked on one of dev-host's ads. I'll change the main host. I use ad-blocker and don't see any ads. Sorry .
Much appreciated
Faznx92 said:
The files are not different you clicked on one of dev-host's ads. I'll change the main host. I use ad-blocker and don't see any ads. Sorry .
Click to expand...
Click to collapse
No problem. Thanks for the super fast clarification!
Trying to root, device not found
Just got KFHDX7, updated to 13.3.2.5 manually, now trying to root using 0.95 ToolKit. I already had ADB installed from rooting previous KFHD7, but unistalled and reinstalled using the ToolKit and via latest post from OP. Try to root via #1 and it says device not found - waiting for device - . I can see the Kindle on my computer (Windows 8) as I was able to manually update. I've enablde ADB and apps from unknown sources. See attached for screen showing install of ADB via ToolKit and error trying to root. Sometimes it doesn't show the * daemon lines.
Thanks in advance for your help!
Update 11/13: Must be a Win8 / ADB issue. I was able to root and disable OTA using my wifes Win7 laptop and it worked just fine. Also the confirmation text for ADB install matched the tutorials vs my screenshot. Still interested to know if anyone has been able to get this to work with Win8.
Question
So if I were to use this could this root my kindle fire hdx OS 4.1.1?
Leafman said:
So if I were to use this could this root my kindle fire hdx OS 4.1.1?
Click to expand...
Click to collapse
No. There's currently no method to root 4.1.1.
root a new hdx 7 with 13.3.1.0
Hello,
i just got my new hdx 7 today and wanted to know what i should do first in order to root successfully.
1) should i root first, before i sign in with my account on that hdx and before i configure my wlan?
2) or should i first register it on my name, configure wlan, get an software update ota and finally try to root?
in advance thanks for you replies.
best regards,
mika
@big_mika:
I would root first and disable the OTA. No one needs the ****ty fireOS updates. get root, install xposed, good launcher and enjoy a good android feeling
I'm on version 13.3.0.0 on my kindle after my kindle updated to 13.3.2.5. I flashed the 13.3.1.0 but it shows every time the 13.3.0.0
Now my question: which toolkit should i use and it is recommended to change the build.prop settings and flash another time?
If you need some screenshots or a deeper explanation of the process i will post it.
unfortunately i failed...
@ taette: thanks for your reply but unfortunately i failed and now i am on os 4.5.1
so, if anybody got an idea how to root fire hdx 7" with fire os 4.5.1 just let me know
thank you very much.
Rooting Kindle 7 HDX (13.3.2.5) - possible?
Hi everyone,
Can't post to the appropriate thread due to being new here...
Just got a brand new Kindle for my son yesterday, but don't feel like re-purchasing his games from Google Play. Can it be rooted? It's not ver 14 yet, but after all instructions from thread http://forum.xda-developers.com/showthread.php?t=2665683 I get stuck on "waiting for device".
Thanks!
Need help on rooting process Kindle Fire HDX 7"
Okay. So I am thinking of getting a 64gb Kindle Fire HDX 7", but I want to root it so i can get google play. I know about towelroot and all that but I have seen that it doesn't work on the new update. So what would I have to do with the updates and such when I get my device so I can properly root it to get Google Play Services and all that.
ImmaFatJesus said:
Okay. So I am thinking of getting a 64gb Kindle Fire HDX 7", but I want to root it so i can get google play. I know about towelroot and all that but I have seen that it doesn't work on the new update. So what would I have to do with the updates and such when I get my device so I can properly root it to get Google Play Services and all that.
Click to expand...
Click to collapse
Since you seem new, I don't recommend this device for you. If you want a tablet and not the risk, buy an Ipadeek or a different tablet. This is a very nice device for people who are already on the rooted versions, people who like the fireos designeek, people who have prime and wanted a powerful device, or people who are side-loading everything from the play store. The hdx is a powerful tablet waiting to be unleashed but unless your ready to deal with a few headaches then don't. Many people bought this device but the potential for it is in the future. As of now you will need to deal with the current state. I recommend giving this a read.
No root access on any version past X.3.2.6 as of typing this. You can give it a shot at your version number. Like I said, know what you're buying first, rethink it over 2 times after that.
big_mika said:
@ taette: thanks for your reply but unfortunately i failed and now i am on os 4.5.1
so, if anybody got an idea how to root fire hdx 7" with fire os 4.5.1 just let me know
thank you very much.
Click to expand...
Click to collapse
It is not possible to Root the latest Updates... So the only solution is Rollback to Fire OS 3... check out this thread... http://forum.xda-developers.com/showthread.php?t=2946946
Sent from my KFTHWI using XDA Free mobile app
I can't find instructions :\
I tried rooting it with your toolkit but all it says is "device not found".
It's plugged in, ADB is activated and I just installed ADB driver. But still can't be found.
Tried Number 1 and 2 of your toolkit with "y" and "y"
HDX toolkit with 3.2.8
Hi,
anyone tried HDX toolkit with 3.2.8.
My HDX 7 was downgraded from 4.2.5 to 3.2.8 today and now I think about routing and installing play store etc.
Thanks, Stef.
(sorry for posting initially in the wrong thread)
Q&A for [APOLLO/RECOVERY LOCKED] Safestrap Recovery v3.72/v3.75 [B02 2014-07-03]
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [APOLLO/RECOVERY LOCKED] Safestrap Recovery v3.72/v3.75 [B02 2014-07-03]. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Fire HDX 8.9 vs Kindle Fire HDX 8.9
Okay, so I have noticed that Hashcode built this for both the 7" and 8.9" versions of the Kindle Fire HDX, but does the 8.9" version here: http://forum.xda-developers.com/showthread.php?t=2612772
Does this support the 3rd generation Fire HDX 8.9" version? I noticed that the download links say it supports systems earlier than 14.3.2.1 and later than 14.3.2.1, but does it support the newer Fire HDX 8.9" system 4.1.1? Judging from what I have researched, I believe that there isn't much difference between 14.3.2.1 and 4.1.1. Has anyone tried to root or install CM on this newest version of the HDX 8.9 yet?
Thanks in advance.
WickdWzrd said:
Okay, so I have noticed that Hashcode built this for both the 7" and 8.9" versions of the Kindle Fire HDX, but does the 8.9" version here: http://forum.xda-developers.com/showthread.php?t=2612772
Does this support the 3rd generation Fire HDX 8.9" version? I noticed that the download links say it supports systems earlier than 14.3.2.1 and later than 14.3.2.1, but does it support the newer Fire HDX 8.9" system 4.1.1? Judging from what I have researched, I believe that there isn't much difference between 14.3.2.1 and 4.1.1. Has anyone tried to root or install CM on this newest version of the HDX 8.9 yet?
Thanks in advance.
Click to expand...
Click to collapse
No, it's not possible to mod FireOS 4 in any way.
Safestrap apk for Kindle Fire HDX 14.3.2.3.2
Hi I'm trying to install safestrap on my kfhdx, but all the links in the forums seem to be broken. Any suggestions on where I can find this download? Thanks a lot
j1mbo83 said:
Hi I'm trying to install safestrap on my kfhdx, but all the links in the forums seem to be broken. Any suggestions on where I can find this download? Thanks a lot
Click to expand...
Click to collapse
Available here.
Although I'm not sure why you want to install safestrap as the firmware version you are running (self reported as 14.3.2.3.2) permits flashing 'native' twrp which is far more robust. From there you can flash CM11 or Nexus 2.0.5. With a bit of work you can also unlock your bootloader which opens the door to CM12 and Nexus 4.x. None of these roms work with safestrap.
Safestrap is a primary used by those who cannot flash 'native' twrp (most newer Kindles) and/or if you wish to toggle between Fire OS and Nexus 1.01. Those are the only roms that work with safestrap. Also note you must take steps to block OTA while using Safestrap or risk bricking your device. At present the only method that works reliably is HDX toolkit.
Thanks for the reply, I'm obviously new to this but I've rooted my Kindle, installed Google play, but recently Google has been forcing updates of play services and I'm afraid to mess with anything else until I can either unlock bootloader it install custom recovery, if you could point me in the right direction on how to do this I'd appreciate it. Didn't know I could install twrp. Any directions in layman's terms would help, thanks.
j1mbo83 said:
Thanks for the reply, I'm obviously new to this but I've rooted my Kindle, installed Google play, but recently Google has been forcing updates of play services and I'm afraid to mess with anything else until I can either unlock bootloader it install custom recovery, if you could point me in the right direction on how to do this I'd appreciate it. Didn't know I could install twrp. Any directions in layman's terms would help, thanks.
Click to expand...
Click to collapse
Installing a custom recovery (twrp) is straight forward given your version of Fire OS. Please confirm you really are on v14.3.2.3.2 and OTA (over-the-air) updates have been blocked and if so, via which method. Did you roll your device back from a higher firmware version? Sorry for all the questions - want to make sure the foundation is solid before taking next steps.
Outline to install custom recovery:
- side load Flashify (here). You can also find/install this from Play Store if working on your device.
- download custom twrp (here); you want Apollo v2.8.6.0
- use Flashify to backup your current recovery (don't skip this step)
- use Flashify to flash (install) the twrp recovery image previously downloaded. You must use this image; don't go downloading/flashing a generic version!
When complete you device will reboot back into Fire OS as if nothing changed. You can verify twrp was correctly installed by powering down and then restarting by pressing power + vol-up. Release the power button when the grey Kindle logo appears; release the vol-up button a few seconds alter. After a few moments a blue logo should appear and you will enter twrp recovery. Have a look around but don't change anything. Reboot you device and post back for further instructions (actually information on next steps; where the fun begins!) .
Be aware that any type of flashing can render your device unusable. The steps outlined above are relatively safe if you follow directions carefully and double check each action before executing. Ask questions in advance; don't panic and start doing unscripted stuff if something goes wrong.
I am running v14.3.2.3.2, I rooted the kindle and blocked OTA updates using hdx toolkit. I did this maybe about 7 months ago and never rolled back. Will these directions still work for me?
j1mbo83 said:
I am running v14.3.2.3.2, I rooted the kindle and blocked OTA updates using hdx toolkit. I did this maybe about 7 months ago and never rolled back. Will these directions still work for me?
Click to expand...
Click to collapse
Looks good. Just go slow and double check each step. Once twrp is installed and confirmed working you can then flash either the Nexus or CM11 rom which will give you unfettered access to the Play store and all the goodness of a 'generic' android device. Effectively your Kindle looses its identity as an Amazon tablet. Nexus (what I use) has proven rock solid but is getting a bit long in the tooth. CM11 is based on KitKat and only has a minor issues with bluetooth, LTE and occasionally wifi. Most users of this rom are quite happy and can easily work around the issues.
Prior to flashing a new rom you should make a complete backup of your current system in twrp and then store that image on another device. Also keep in mind that once you flash twrp it is very difficult to restore your device to full 'stock'. Assume a one way trip.
Edit: Forgot to mention LTE. At present none of the roms support LTE but that will likely change in the near future. If you have an LTE enabled tablet you'll have to decide if that or play store access is more important.
Thanks. Ok I installed flashify, then followed your link to download and install twrp and it has a note at the top that says to unlock boot loader. I don't think it is unlocked. How do I check this? And if it isn't, how would I go about unlocking it?
---------- Post added at 09:00 PM ---------- Previous post was at 08:11 PM ----------
Ok I successfully installed twrp, created a backup, and saved it to another device. Ready for the next step. Thanks for all your help.
Congrats. If you are asking how to know if you are unlocked, chances are good it is locked. You do not need to unlock the bootloader, but it is highly recommended as once successfully unlocked it is another failsafe, and opens up other roms (like cm 12). To unlock it, I suggest grabbing Draxie's automated (slightly) script from the original dev section. Know that the act of unlocking the bootloader is difficult, and will require you to learn more about your device, but it does pay off in the end.
j1mbo83 said:
Thanks. Ok I installed flashify, then followed your link to download and install twrp and it has a note at the top that says to unlock boot loader. I don't think it is unlocked. How do I check this? And if it isn't, how would I go about unlocking it?
---------- Post added at 09:00 PM ---------- Previous post was at 08:11 PM ----------
Ok I successfully installed twrp, created a backup, and saved it to another device. Ready for the next step. Thanks for all your help.
Click to expand...
Click to collapse
Congrats!! See post from lekofraggle (here) which I fully agree with. However, I think you can defer the bootloader unlock for a little while recognizing that it provides an important failsafe should you bork your device and is a prerequisite for some roms (eg: CM12).
Next step involves flashing a rom of your choice. Recognize all aps/data will be wiped; you'll be starting clean. However, anything previously purchased in the play store can be downloaded again assuming you use the same credentials when setting up accounts on the 'new' rom.
Choices:
- Nexus 2.0.5: JellyBean based, rock solid, near AOSP (unmodified Android). Info/links here.
- CM11: KitKat based, popular across numerous Android devices with useful extensions baked in. Some minor BT/WiFi flakiness on HDX devices. Info/links here.
Both roms can also be downloaded using the ROMs tab at the top of this page. Don't go trying anything else. You want HDX Nexus or CM11-Apollo. Magic Beans will also work but carries no significant advantage over the other two and hasn't see much development in recent months.
All ROMs can be flashed from twrp. Be sure to make a backup of your current environment first. Use caution in twrp if you are new to the tool; it's easy to mess things up including a full brick of your device.
I recommend you start with Nexus. It's a great rom that will serve you well; an upgrade (KitKat) is in the works and should be released in the not-too-distant future. CM11 is also a fine choice and offers greater compatibility with some of the more recent app releases. Both are further customizable via Xposed Framework but that's another discussion.
Ok thanks, I downloaded the zips, now I have just one more question (I know, I have a lot...). Do I need to wipe my system before installing new Rom?
j1mbo83 said:
Ok thanks, I downloaded the zips, now I have just one more question (I know, I have a lot...). Do I need to wipe my system before installing new Rom?
Click to expand...
Click to collapse
Keep asking! Lots of devices have died in the hands of ignorant users (not intended to be an insult...were are all ignorant until educated).
In theory you do not need to wipe the device but there have been scattered reports of strange behaviors after performing a 'dirty' flash. My recommendation is to perform a factory reset (under wipe) from within twrp. This will clear data, cache and dalvik while leaving system and internal storage intact. If you opt for an "advanced wipe" select the previous 3 plus system; leave internal storage alone. Do not format or repair; just asking for trouble.
As always make a backup before proceeding and store a copy of that off-device. Short term keep a copy on the device along with the rom image just in case you have to redo something and can't connect via tether. Rare but it does happen.
So far, fit and finish is outstanding. Better than a number of units that have gone through our hands in testing. (I'm keeping this one) Very, very little bloatware. But, not having root and the ability to write to SD etc is a PITA
Root was achieved using the method developed by social-design-concepts You will want to use the T4 trigger option. His thread is here. You will want to be sure that you use the download he mentions that are what he calls the public trial release, it's here
Glad to answer any questions about the device and follow up questions as well. I'm conversant with adp, etc.
Thanks!
Sent from my Venue 10 7040 using Tapatalk
Does this work on the latest Lollipop 5.1 firmware update?
Yes, it does.
How did you get the adb fastboot to work? I've installed the universal adb driver from http://androidxda.com/download-dell-usb-drivers but I still haven't gotten it to work.
I checked the Device Manager and the only unknown device is MTP.
Thanks!
I generally switch connection types to mass storage VS MTP and that makes it happen. Do remember that on occasion you have to specify the exact driver in device manager, Windows necessarily get it right. (Not being condescending mind you, just not sure where your skill level is at.)
I could use some help... After the T4 selection Fastboot Mode starts doing it's thing and attempting to copy over files but in the end it says Result: Fail (command now allowed in this device state) and I noticed the device state is Locked...
That's pretty straight forward. In short, your bootloader is still locked. Social design concept covers this well in his post. It's the first link in my original post. My apologies for the late reply. Been bringing up my Nexus devices to Marshmallow and dealing with all that.
Fearcher said:
That's pretty straight forward. In short, your bootloader is still locked. Social design concept covers this well in his post. It's the first link in my original post. My apologies for the late reply. Been bringing up my Nexus devices to Marshmallow and dealing with all that.
Click to expand...
Click to collapse
Hello Fearcher Congrats on rooting your 7040! Im in desperate need of your expertise. Trying to root my 7040 on L5.1
-installed drivers
-bootloader unlocked but text is in red?
-adb devices attached successfully
-fastboot devices found successfully
-have tried t4 on both tools with remote flashing to this partion error?
-tablets encryption is "encrypted"
Please help me root this tablet what am I missing?!
Is there anything about rooting 5.1 on a venue 10 that would prohibit future updates? I have read of rooted venue 8 users being unable to update to 5.1 after root but there was speculation that it was due to it being a 5.1 based root to begin with. I don't know enough about the details to know if this is plausible. This is the post I am reffering to: http://forum.xda-developers.com/showpost.php?p=64196214&postcount=15
I'd like to root but if it means no future updates that would be a deal breaker. Fearcher, you say this root method works on 5.1. Does this mean you had updated your tablet from 5.01 (rooted) to 5.1? If so did it require any special procedure or was it an OTA update? Thanks for you help
what driver do i need
Hello.
I've tried the ADB fastboot driver found in this thread and the stickied one. I've gone into device manager and selected several different drivers including the one named "dell adb fastboot" something which required me to turn off driver signature enforcement. Driver installed fine every time. When I launch the program I get the correct status message. Everything is right according to the instructions. I'm still getting the fail when it tries to install its files (command not allowed in this state).
What am i missing exactly? I've followed everything i can find in both this thread and the linked thread.
I have the latest 5.1 update from dell/google. I just bought the device from dell. My PC is Windows 10 64 bit if that matters. Driver signing is off.
Hey bro he hasn't been replying to any questions. Your bootloader is locked. I unlocked mine and it still don't work. From what I can gather you have to downgrade to kitkat then run Intel flash tool. We need a droidboot.zip file for flash tool but no one has helped. We need a package made from this site
---------- Post added at 07:06 PM ---------- Previous post was at 07:05 PM ----------
http://opensource.dell.com/releases/Venue_10_7040_Moorefield/developer-edition/
r_nation said:
Hey bro he hasn't been replying to any questions. Your bootloader is locked. I unlocked mine and it still don't work. From what I can gather you have to downgrade to kitkat then run Intel flash tool. We need a droidboot.zip file for flash tool but no one has helped. We need a package made from this site
---------- Post added at 07:06 PM ---------- Previous post was at 07:05 PM ----------
http://opensource.dell.com/releases/Venue_10_7040_Moorefield/developer-edition/
Click to expand...
Click to collapse
That's what I was thinking. is this because the 10 has a different chip than the smaller versions or something? It seems like they're having fun with their root and stuff. I thought moving to a device without a carrier would be easier. I have no idea why these are locked. it's nuts.
both models have same processor. It has to do with android 5.1 , they were able to root because there was kitkat firmware they could flash. Actually I don't even think my above method will work. We have to wait for an Intel based custom recovery for lollipop 5.1 but don't unlock your bootloader til there is one available.
whosloosin92 said:
I...
I'd like to root but if it means no future updates that would be a deal breaker. ...
Click to expand...
Click to collapse
Don't worry about future updates because they aren't coming. Dell killed off the Android dev team last year, so these are amazing but orphaned devices.
Are you sure?
bcjackson said:
Don't worry about future updates because they aren't coming. Dell killed off the Android dev team last year, so these are amazing but orphaned devices.
Click to expand...
Click to collapse
bc are you sure, who told you this? I am also a corporate customer of Dell, I am going to go to my SE and see what he saids. I am not doubting you, really hate to hear this actually. But I just find it hard to believe. But you and I know, it's all about the money. If they are not moving the 7040, then...bye, bye.
r_nation said:
Hey bro he hasn't been replying to any questions. Your bootloader is locked. I unlocked mine and it still don't work. From what I can gather you have to downgrade to kitkat then run Intel flash tool. We need a droidboot.zip file for flash tool but no one has helped. We need a package made from this site
---------- Post added at 07:06 PM ---------- Previous post was at 07:05 PM ----------
http://opensource.dell.com/releases/Venue_10_7040_Moorefield/developer-edition/
Click to expand...
Click to collapse
Do tell if u are able to root it in 5.1
They have enabled encryption by default so it would be tough
I don't want to go back to 4.4 :c
That opensource firmware is lollipop. There is literally no development for venue 10 7000 root is still impossible.
Just wanted to report in that I successfully rooted my 7040 today using the social-designs-concepts method mentioned in the first post of this thread with IntelAndroid-FBRL-07-24-2015.7z (had attempted to use the recommended IntelAndroid-FBRL 05-16-2015 Public Trail Release but Windows 10 AV kept quarantining it due to detected trojan malware). SuperSU Free v2.76 is installed successfully.
FWIW, I did this on a refurb 32GB 7040 that I purchased online for US$216 (as my 16GB one has become to precious to experiment with). I did not allow the system to connect to networks before rooting, and it is on Android 5.0.2. I'm not sure if that affected the success of rooting; I just wanted to report clearly what I did. Please note that after rooting automatic firmware updates to 5.1 failed. Will undo the rooting and try again after 5.1 update.
The expanded memory will be useful, as well as the ability to extend "internal" to include the external SD card.
Now if I could just figure out how to put Nougat on this thing I would be ecstatic.
rcbarr said:
bc are you sure, who told you this? I am also a corporate customer of Dell, I am going to go to my SE and see what he saids. I am not doubting you, really hate to hear this actually. But I just find it hard to believe. But you and I know, it's all about the money. If they are not moving the 7040, then...bye, bye.
Click to expand...
Click to collapse
Dell now confirming that they are discontinuing Android lines and will not provide further updates.
http://www.pcworld.com/article/3090466/android/dell-stops-selling-android-devices.html
bcjackson said:
Just wanted to report in that I successfully rooted my 7040 today using the social-designs-concepts method mentioned in the first post of this thread with IntelAndroid-FBRL-07-24-2015.7z (had attempted to use the recommended IntelAndroid-FBRL 05-16-2015 Public Trail Release but Windows 10 AV kept quarantining it due to detected trojan malware). SuperSU Free v2.76 is installed successfully.
FWIW, I did this on a refurb 32GB 7040 that I purchased online for US$216 (as my 16GB one has become to precious to experiment with). I did not allow the system to connect to networks before rooting, and it is on Android 5.0.2. I'm not sure if that affected the success of rooting; I just wanted to report clearly what I did. Please note that after rooting automatic firmware updates to 5.1 failed. Will undo the rooting and try again after 5.1 update.
The expanded memory will be useful, as well as the ability to extend "internal" to include the external SD card.
Now if I could just figure out how to put Nougat on this thing I would be ecstatic.
Click to expand...
Click to collapse
So the baseline is that u cannot root once you upgrade to 5.1?
---------- Post added at 02:15 PM ---------- Previous post was at 02:09 PM ----------
bcjackson said:
Just wanted to report in that I successfully rooted my 7040 today using the social-designs-concepts method mentioned in the first post of this thread with IntelAndroid-FBRL-07-24-2015.7z (had attempted to use the recommended IntelAndroid-FBRL 05-16-2015 Public Trail Release but Windows 10 AV kept quarantining it due to detected trojan malware). SuperSU Free v2.76 is installed successfully.
FWIW, I did this on a refurb 32GB 7040 that I purchased online for US$216 (as my 16GB one has become to precious to experiment with). I did not allow the system to connect to networks before rooting, and it is on Android 5.0.2. I'm not sure if that affected the success of rooting; I just wanted to report clearly what I did. Please note that after rooting automatic firmware updates to 5.1 failed. Will undo the rooting and try again after 5.1 update.
The expanded memory will be useful, as well as the ability to extend "internal" to include the external SD card.
Now if I could just figure out how to put Nougat on this thing I would be ecstatic.
Click to expand...
Click to collapse
So the baseline is that u cannot root once you upgrade to 5.1?
well now that they have abandoned android maybe they will release the open source?:crying: