Database Develop

[Q] Verizon SGT... where do I start?

Which root method is easiest/best?
what rom? Is there really no CM or MIUI support for this thing?
Thanks for any advice in advance!

My suggestion is you should stay with the stock rom first for at least 2 month before you make decision to root it. Play with it to the fullest, by doing so, then you will notice what its weeknest and find the best way to solve it by 3rd party app. If stil not satistfy, then go with the root thingy. But maybe i should warn you, that more reading is required, equip your self with good knowledge of rooting thing so that you will not screw up your tab. I'm my self already 17 days own this tab and still learning from xda community. I read a lot and found most people are facing big trouble after root. That had down my moral and make me think twice about rooting thing. But if you had confidence, than why not just go for it!!!
Sent from my GT-P1000 using XDA App

Oh I am not new to rooting, I have owned a few Android devices. There is no question I want root, the question is how to go about it.
This devices support is so clustered it is near impossible to get through with anything remotely close to ease. Anyhow for those who follow in my footsteps and find this thread, here is how I have progressed.
First, how to undo and return to stock.
http://forum.xda-developers.com/showthread.php?t=967175&highlight=return+to+stock
Power On + Volume Up is recovery
PoewrOn + Volume Down is downloader mode
Please note: the driver called for by Zadig should be SAMSUNG composite device, and it would not even show up unless the SGT was connected and in download mode already; Also you will have to check for and install the update after using this.
Next to skip Activation press Volume keys in this order
Up Down Up down left right left right B A Start... erm, no, thats not it...
Try
Up down down up up up down down down down
OK now on to root. Search for kies, here or on Google, you will find it. I am not even sure why this is necessary but when I skip this, **** don't work. Install it, check that you are not in USB debug mode (found under applications settings, developer) and connect your SGT. Wait for the error that you need to be in PC Studio mode, which we dont have, then disconnect.
Now you need to have Super One click Downloaded, (search the forums) and run it. Set your device to USB debugging ON then connect it. MAKE SURE YOU DO NOT SKIP THIS... I swear to god every device I get, at least once I will forget about debugging and spend hours reinstalling drivers because the device is not recognized!
Press Root
After it is rooted donate, and reboot the tab (MAKE SURE to reboot, trust me SU can do odd things before you do).
Download Verizon Boot Strapper. Yes it is 2.99, take your cheap ass to the bank, deposit 3 bucks, and support the dev.
CLick Bootstrap Recovery and you will gett a SU request, if you dont, you did not reboot like I said earlier, do so now, and hope you dont get a bad install
After it is done click reboot into recovery like it tells you. Once it is done, do not reboot yet, whipe the cache, then go into advanced and wipe Dalvic. I am not sure if anyone else does this, but the only time I did not, I got stuck at the samsung screen and had to repeat this whole process.
Reboot, and enjoy your Galaxy tab.

Gear Live Stock Firmware Image - 24JUL14 & Bootable Root ADB image

Hi guys, I just managed to pull the stock firmware image off the Sprat, with the assistance of @Dees_Troy. We've been working on this for a few days. Lots of highs and lots of lows. Lots of hardware glitches, device overheating, reading kernel logs to troubleshoot problems... And you know what? All of it could have been avoided if Samsung had released a stock image.
Without any further ado, though, you can find a factory image for this device here: https://builds.casual-dev.com/index.php?dir=random/sprat/
Here is the first custom kernel created for this device. It's mostly dees troy's work, he compiled it and made it operate, but I had to reimage it a few times to make it operate properly. If you absolutely need root for checking something out right now, you can fastboot boot this image and get it.
If you'd like to pull your OWN firwmare including the EFS(serial info) for the device, you can use this command in adb root shell after booting the above image.
Code:
cd /dev/block/platform/msm_sdcc.1/by-name;
f=`ls`;
for f in $x;
do
dd if=$f of=/data/local/tmp/$f.img;
done;
rm /data/local/tmp/userdata.img
exit;
adb pull /data/local/tmp/
the contents of the entire device will come to your computer
now clean up the temp folder.
Code:
adb shell rm /data/local/tmp/*
You now have the firmware above + EFS data.
[rant]
I mean seriously.. Samsung, WTF? I've been working on this for 5 straight days now.
Why did I have to go through the process of keeping this Quad-core watch cool while i tinkered with UART, and continuously rebooted it?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Why did I have to wade knee deep in your kernel problems to get this done?
Is it becoming apparent that Samsung doesn't want people messing with their "open devices"? I mean, I can think of no other reason they haven't released a stock image for a device which can be destroyed with a bad flash.
[/rant]
Either way, we finally have a stock image and that means Dees_Troy can release a TWRP, ROM devs can begin working with the system, and those in need of stock firmware now have access to it. Pretty good news if you ask me.

Thank you Adam and I suppose I can speak for every Live owner here when I say we really do appreciate it. I can't wait to start tinkering with it and lets hope we can get that WatchFace API soon. I'm dying for a more sophisticated looking face with a more blue and silver brushed metal look to it. Can't find one anywhere. Thanks again Adam. What would we do without u?
---------- Post added at 09:03 PM ---------- Previous post was at 09:01 PM ----------
Oh and if you add any more green text to your display... just go head on and Follow The White Rabbit....

Sweet Adam, you made a lot of progress since Friday

thanks for all this work! Now to start working on port for Gear 1... Haven't messed with this stuff since HD2 days....Ugh.
Chris

I'd like to get someone to test some TWRP images for me. Need someone that's set up to use adb and fastboot and has basic working knowledge of how to use them. Find me in #twrp on Freenode.

Dees_Troy said:
I'd like to get someone to test some TWRP images for me. Need someone that's set up to use adb and fastboot and has basic working knowledge of how to use them. Find me in #twrp on Freenode.
Click to expand...
Click to collapse
Contacting now.

Dees_Troy said:
I'd like to get someone to test some TWRP images for me. Need someone that's set up to use adb and fastboot and has basic working knowledge of how to use them. Find me in #twrp on Freenode.
Click to expand...
Click to collapse
Incase you missed the link on iirc, http://pastebin.com/5rUD9X0t

Annnnnd this is why i ditched Samsung after the SGSII, Im so glad I got the G Watch instead.
Seems to be a Thing now that Samsung is playing hard to beat with factory images and source, Devs should jump on some form of anti Sammy bandwagon because although this is sure a great feat in hacking but for people here who Crack flash and test stuff for devs on their devices this is a pain and slows down evolution.
if sammy continue with his imagine all the ideas they can't steal from the clever devs here at XDA, I say screw them and buy devices from companies who truly keep android open source

Can this be used in Odin?

Krunk_Kracker said:
Can this be used in Odin?
Click to expand...
Click to collapse
No, it is a fastboot image

How do I actually use this!? Sorry for the noobness haha. I understand I have to unlock my bootloader first, but how do I actually obtain root after I do that? TIA!

Joe0113 said:
How do I actually use this!? Sorry for the noobness haha. I understand I have to unlock my bootloader first, but how do I actually obtain root after I do that? TIA!
Click to expand...
Click to collapse
Hello,
As these are ADB/Fastboot packages, you will need do the following
1) Setup the Android SDK (for ADB and Fastboot)
2) Unlock the bootloader
3) Use the "fastboot boot <filename.img>" (replace this with the location of the extracted content from the zip file)
I honestly would recommend against trying this unless you are a bit seasoned as breakage is possible.

Boot into TWRP
Mount the system
Use the TWRP terminal emulator
rm /system/app/SuperSU.apk
OK so these are the instructions I was given to root. I am currently sitting in TWRP, system was mounted, when I hit reboot system, it told me I wasnt rooted, so I swiped to root...rebooted back to recovery...clicked terminal command which opened up a directory telling me to choose a starting folder :|
this is where im lost.. Also how do I type anything into the terminal commands once I get it open since theres no keyboard lol
Manually removed it using the file manager though its called superuser.apk and it works..Guess im rooted given I can use the rebooter that Adam posted!

KMyers said:
Hello,
As these are ADB/Fastboot packages, you will need do the following
1) Setup the Android SDK (for ADB and Fastboot)
2) Unlock the bootloader
3) Use the "fastboot boot <filename.img>" (replace this with the location of the extracted content from the zip file)
I honestly would recommend against trying this unless you are a bit seasoned as breakage is possible.
Click to expand...
Click to collapse
Do we have to do each individual img? I downloaded the file, extracted it and theres 23 img files lol. I have yet to do anything with a .tar file also
Im debating on returning to stock and taking the watch back to wait for the 360,

Instructions on returning to Stock??
Could someone please post some instructions on returning to Stock? I flash the Octa Rom and did not make a back up and then tried returning to stock by flashing the system.img and it would not boot. I have returned to stock with Nexus devices in the past but looking at the stock firmware image files here I'm not getting how this works. PLEASE HELP

AdamOutler said:
Hi guys, I just managed to pull the stock firmware image off the Sprat, with the assistance of @Dees_Troy. We've been working on this for a few days. Lots of highs and lots of lows. Lots of hardware glitches, device overheating, reading kernel logs to troubleshoot problems... And you know what? All of it could have been avoided if Samsung had released a stock image.
Without any further ado, though, you can find a factory image for this device here: https://builds.casual-dev.com/index.php?dir=random/sprat/
Here is the first custom kernel created for this device. It's mostly dees troy's work, he compiled it and made it operate, but I had to reimage it a few times to make it operate properly. If you absolutely need root for checking something out right now, you can fastboot boot this image and get it.
If you'd like to pull your OWN firwmare including the EFS(serial info) for the device, you can use this command in adb root shell after booting the above image.
Code:
cd /dev/block/platform/msm_sdcc.1/by-name;
f=`ls`;
for f in $x;
do
dd if=$f of=/data/local/tmp/$f.img;
done;
rm /data/local/tmp/userdata.img
exit;
adb pull /data/local/tmp/
the contents of the entire device will come to your computer
now clean up the temp folder.
Code:
adb shell rm /data/local/tmp/*
You now have the firmware above + EFS data.
[rant]
I mean seriously.. Samsung, WTF? I've been working on this for 5 straight days now.
Why did I have to go through the process of keeping this Quad-core watch cool while i tinkered with UART, and continuously rebooted it?
Why did I have to wade knee deep in your kernel problems to get this done?
Is it becoming apparent that Samsung doesn't want people messing with their "open devices"? I mean, I can think of no other reason they haven't released a stock image for a device which can be destroyed with a bad flash.
[/rant]
Either way, we finally have a stock image and that means Dees_Troy can release a TWRP, ROM devs can begin working with the system, and those in need of stock firmware now have access to it. Pretty good news if you ask me.
Click to expand...
Click to collapse
Hi adam i have a Gear Live with Build KMV78Y and when i fastboot boot rootADB.img my device freezes at the bootloader screen and never reboots. i have to adb reboot to get out of it. which is the funny part since i am still on the bootloader screen but adb works. any idea of what is going on here thanks.
Tom
Edit Never Mind i got it just wasnt expecting it to work this way. pretty funny temp root. why not make it perminant root?

Tomsgt said:
Hi adam i have a Gear Live with Build KMV78Y and when i fastboot boot rootADB.img my device freezes at the bootloader screen and never reboots. i have to adb reboot to get out of it. which is the funny part since i am still on the bootloader screen but adb works. any idea of what is going on here thanks.
Tom
Edit Never Mind i got it just wasnt expecting it to work this way. pretty funny temp root. why not make it perminant root?
Click to expand...
Click to collapse
Hiyas Tom..did you really get your Gear?!?!?!

Tower1972 said:
Hiyas Tom..did you really get your Gear?!?!?!
Click to expand...
Click to collapse
yes got it today and working on the Restore Tool like my LG G Watch restore tool. right now its tested and working just cleaning it up

Tomsgt said:
yes got it today and working on the Restore Tool like my LG G Watch restore tool. right now its tested and working just cleaning it up
Click to expand...
Click to collapse
That's the best news I've heard all day!

Tower1972 said:
That's the best news I've heard all day!
Click to expand...
Click to collapse
Samsung Gear Live Tool is up click here and enjoy

[Q] Verizon G2 acting crazy after FDR

Hello, and thank you in advance for any support on my issues. I have done some extensive searching regarding my issues but am coming up empty. I consider myself a relative noob and am now facing multiple questions and issues with my phone.
Device Info:
Verizon LG G2
Rooted, stock
Android Version 4.2.2
Software Version VS98011A
I did not personally root my phone - I paid to have it done for me remotely.
I have been using Titanium Backup to freeze or remove applications and bloat.
I also have used the paid version of ROM Manager for when/if I need it - I have never personally flashed a custom ROM or Kernel, etc.
I did personally side load the HotSpotProvision apk to use the Verizon Hotspot feature with my unlimited data and it worked great.
I also have the Verizon versions of the Galaxy S5 and LG G3. I recently did a 4G LTE speed test with all 3 devices and got insane speeds (attached) with the S5 and G5 but not the G2. I tried researching whether KitKat was the reason for being able to access XLTE speeds or not but couldn't find anything definitive there either. So I decided to attempt the Verizon OTA KitKat update for the G2. Here is where my nightmare begins...
To my knowledge, no backup had ever been done to my phone unless it was done when it was rooted. Regardless, I wanted to do one before making any changes to the phone but I have a feeling I was unsuccessful. After more searches on how to perform a backup and trying 6 times with ROM Manager (unsuccessfully), I decided to try the physical key option to launch into Recovery Mode. Based on what I did find online, this method would take you to the FDR screen but not to worry and to continue because it would actually take you to the TWRP home screen. Well, it did not. My phone reset and I lost everything in my gallery, etc. On reboot, I did see that I was still rooted but not able to do the OTA (because I am still rooted, I assume?). I have done 2 more FDRs and now my phone is acting out of it's mind.
Issues:
Touch screen unresponsive or turning off/on all by itself
Contact info not syncing to native messaging app
Previously installed free or purchased apps not reinstalling (although they did after the first FDR)
Can't receive OTA
At this point, I might as well do whatever I need to do to get things working correctly since I'm already reset.
My questions are:
How can I check if I do in fact have, or don't have a backup that I can access?
How do I create a backup so this doesn't happen again?
What do I need to do to get the OTA and will KK allow me to access the XLTE band?
Can I still do a Factory Data Reset and get back to the true "out of the box" version of the phone? If so, how?
I think that's it for now!! Thanks for any help that can be offered. Cheers.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Sounds like whoever you paid to root the phone didn't install a recovery or you lost it from applying the KK OTA.
You can install TWRP using Autorec if you're on KK (4.4.2) now.
http://forum.xda-developers.com/showthread.php?t=2715496
Personally I'd start clean to see if it clears up your issues, the touch screen thing sounds more like a hardware problem. If all is well after returning it to stock, re-root it yourself using ioroot/towelroot and install a recovery again and make a back up to save somewhere once you get it set up the way you want it.
http://forum.xda-developers.com/showthread.php?t=2448960

Thank you very much, Matt.
KK never did get installed...I am still on 4.2.2 and every time I try to go back to stock through various methods on this site I get the attached image. I would definitely like to start with the out-of-box device again, OTA KK and re-root but I'm not even having any luck with that either. This whole project began with the thinking that I needed KK to access the XLTE network since I was getting incredible speeds with the G3 and S5...do you know if that is accurate?
mjones73 said:
Sounds like whoever you paid to root the phone didn't install a recovery or you lost it from applying the KK OTA.
You can install TWRP using Autorec if you're on KK (4.4.2) now.
http://forum.xda-developers.com/showthread.php?t=2715496
Personally I'd start clean to see if it clears up your issues, the touch screen thing sounds more like a hardware problem. If all is well after returning it to stock, re-root it yourself using ioroot/towelroot and install a recovery again and make a back up to save somewhere once you get it set up the way you want it.
http://forum.xda-developers.com/showthread.php?t=2448960
Click to expand...
Click to collapse

lantzman said:
Thank you very much, Matt.
KK never did get installed...I am still on 4.2.2 and every time I try to go back to stock through various methods on this site I get the attached image. I would definitely like to start with the out-of-box device again, OTA KK and re-root but I'm not even having any luck with that either. This whole project began with the thinking that I needed KK to access the XLTE network since I was getting incredible speeds with the G3 and S5...do you know if that is accurate?
Click to expand...
Click to collapse
Follow the directions in the return to stock guide provided, see if you can get the phone in download mode...
Install the LG Flash Tool and drivers then try this.
1) Go ahead and put phone in Download mode by VolUp + plug in USB to PC. At this time your computer should install the device, if it hadnt already. Open device manager to check if un der "Ports (Com and LPT)" it shows up as LGE AndroidNet for VZW USB Serial Port (COM##) IF the COM number is anything other than 41, which it probably will be. Right click it in device manager and choose peroperties, then go to port settings tab and click advanced. On the bottom choose COM41 and hit OK. (if you get an error about it being in use I'll write more about that later)
hit ok and all that and close out the properties.
Click to expand...
Click to collapse

OK, I'm on download mode, the computer installed drivers and I changed to COM41. Phone still shows "Firmware Update" screen and 0% on progress. Where do I go from here?
mjones73 said:
Follow the directions in the return to stock guide provided, see if you can get the phone in download mode...
Install the LG Flash Tool and drivers then try this.
Click to expand...
Click to collapse

lantzman said:
OK, I'm on download mode, the computer installed drivers and I changed to COM41. Phone still shows "Firmware Update" screen and 0% on progress. Where do I go from here?
Click to expand...
Click to collapse
Did you unplug and replug in the phone?

I think I got it done. Phone is downloading KK now. This is where I would get the error on the install because I was rooted. Did the process I just go through unroot me?
mjones73 said:
Did you unplug and replug in the phone?
Click to expand...
Click to collapse

OK, it's doing the OTA!
lantzman said:
I think I got it done. Phone is downloading KK now. This is where I would get the error on the install because I was rooted. Did the process I just go through unroot me?
Click to expand...
Click to collapse

lantzman said:
I think I got it done. Phone is downloading KK now. This is where I would get the error on the install because I was rooted. Did the process I just go through unroot me?
Click to expand...
Click to collapse
Yes, returns the phone to out of the box stock basically. Now if you want to re-root, you can use ioroot25 or towelroot.
ioroot25 - http://forum.xda-developers.com/showpost.php?p=48709232&postcount=869
Once rooted, use autorec to install a recovery (kitkat requires some additional steps besides just flashing a recovery and it does them for you)
http://forum.xda-developers.com/showthread.php?t=2715496
Make sure you grab the vs980 version of autorec.

So I can't create a stock recovery prior to root, correct...so that I can go back to stock from root?
mjones73 said:
Yes, returns the phone to out of the box stock basically. Now if you want to re-root, you can use ioroot25 or towelroot.
ioroot25 - http://forum.xda-developers.com/showpost.php?p=48709232&postcount=869
Once rooted, use autorec to install a recovery (kitkat requires some additional steps besides just flashing a recovery and it does them for you)
http://forum.xda-developers.com/showthread.php?t=2715496
Make sure you grab the vs980 version of autorec.
Click to expand...
Click to collapse

lantzman said:
So I can't create a stock recovery prior to root, correct...so that I can go back to stock from root?
Click to expand...
Click to collapse
No, you need to root it first if you want to back it up.

OK, so I can root with the Towelroot app and use Autorec for backup. Does it give me TWRP?
mjones73 said:
No, you need to root it first if you want to back it up.
Click to expand...
Click to collapse

and where do I find the process for installing Autorec?
lantzman said:
OK, so I can root with the Towelroot app and use Autorec for backup. Does it give me TWRP?
Click to expand...
Click to collapse

sorry, I was making this way too difficult. I ran Towelroot and Autorec and I believe we are good to go. Now, when would I use Autorec...when I have an issue flashing other ROMs, kernels, etc?
How do you prefer to receive donations? I really appreciate your help...you've been great!

lantzman said:
sorry, I was making this way too difficult. I ran Towelroot and Autorec and I believe we are good to go. Now, when would I use Autorec...when I have an issue flashing other ROMs, kernels, etc?
How do you prefer to receive donations? I really appreciate your help...you've been great!
Click to expand...
Click to collapse
Autorec is a one and done, you can remove it now, it installs TWRP, that's all you need it for. You should now be able to get into recovery using the same sequence you used before if it installed clean for you. Any flashing of rom, kernels, etc would be via TWRP.
One last note, don't install any OTA's while you're rooted.
You don't have to donate anything but if you really want to, just hit the Donate to Me button under my name.

OK, thank you. One last question: it seems the touch screen may be starting to fail. If I needed to unroot or at least show unrooted to turn it in for a warranty replacement, can that be done and if so, how?

lantzman said:
OK, thank you. One last question: it seems the touch screen may be starting to fail. If I needed to unroot or at least show unrooted to turn it in for a warranty replacement, can that be done and if so, how?
Click to expand...
Click to collapse
This will get you back to stock. Make sure you read the first page before you do this...if needed. FYI: Device needs to be off to get into download mode and you should be in download mode before installing the drivers. http://forum.xda-developers.com/showthread.php?t=2448960
Sent from my XDABBEB VS98025A v2.0.0 using XDA free mobile app

Perfect, that's the process I just did from root so I could get the KK OTA. Just wasn't sure if there was an easier way to just show "unrooted" in "about phone" before having them look at it. Love your call sign/avatar. Huge Huge Huge Zeppelin fan here! Ever since hearing "Stairway" in 7th grade! Mght need to see if "LantZeppelin" is available! Thanks again.

[Help Thread][7" Kindle Fire HD](2nd Gen 2012) Ask Any Question, Noob Friendly

[SIZE=+2]This thread has been created
for
Questions & Answers/Troubleshooting[/SIZE]​[SIZE=+2]Specific to[/SIZE]
7" Kindle Fire HD - 2012​
Please feel free to share issues, questions and offer help. Noob questions are welcomed.
It is always best to use the Thanks button , in lieu of simply posting "Thank you".
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Please keep discussion focused, on questions pertaining to this Device
List of supporters@sd_shadow
...
...
...​To those seeking help: Please don't bombard the supporters with PMs asking for help. Instead, ask your question here in the thread so others can benefit from the solution to your problem as well. If you want to be sure someone particular gets notified of your question, put his / her username directly after an @.
If you have ROM related questions, post in the relevant ROM Q&A thread (if there is one) or directly in the ROM development thread. If you are not eligible of posting there, you may post here. Thank you!
Supporters: If you want to be put on or off the list, just make a request here in the thread!
Before posting anything, I strongly advise you to read
Forum Rules
[GUIDE] - XDA New User Guide - Getting started on XDA
XDA Tour
Fire Index: Which Amazon (Kindle) Fire Do I have? There are several Amazon Fires. Be sure you know which one you have
[Index] Amazon 7" Kindle Fire HD, 8.9" Kindle Fire HD, Kindle Fire 2
Frequently Asked Questions - 2nd Generation Kindle Fires
[REF]All Things About Kindle Fire HD 7"
Please look for a similar [HELP THREAD] when visiting another device forum.
If you would like to create a similar [Help Thread] please Click Here.
​

[SIZE=+3]Frequently Asked Questions[/SIZE]
[SIZE=+2]Kindle Fire HD 7 (2012)[/SIZE]​
[SIZE=+1]This a short list of frequently asked questions in this device forum and the answers often given as a response. It should serve as a starting point for gathering knowledge and finding solutions to many common problems. [/SIZE]
[SIZE=+1]Q1: How do I tell if i have a Kindle Fire HD 7 (2012)?[/SIZE]Kindle Fire HD 7" (2012) has Power and volume buttons on the sides, Front-facing HD camera.​
[SIZE=+1]Q2: What is the ........................................................................................................?[/SIZE]Replace this block of text with a short answer for the above question. If the answer is complicated or otherwise lengthy, avoid the temptation to provide a full answer here. If the answer is truly that involved, this should be answered in another thread outside of this document. The answer then should provide a brief summary or overview and direct the reader to the document providing a full coverage of the topic.​[SIZE=+1]Q3: Why does the ........................................................................................................?[/SIZE]Replace this block of text with a short answer for the above question. If the answer is complicated or otherwise lengthy, avoid the temptation to provide a full answer here. If the answer is truly that involved, this should be answered in another thread outside of this document. The answer then should provide a brief summary or overview and direct the reader to the document providing a full coverage of the topic.​*​Forum Rules | New Users Guide | XDA Tour | Report Posts​A special thanks to everyone who contributed to the production of this FAQ​

Index
Kindle Fire HD 7" - Power and volume buttons on the sides, Front-facing HD camera
Model #:
Serial #
D025------Kindle Fire HD 7" 16GB
D059------Kindle Fire HD 7" 32GB
Codename: Tate
Software: Amazon:7.5.1 - Based on Android OS 4.0.3

Glad you're here to help. Like 6 weeks ago I attempted to return to stock. It was my understanding that I needed to downgrade twrp to flash the image (which I did easily . In the other thread it specified to wipe system first (REALLY wish I had thought that one through). Now I can't push ANYTHING to the SD card. No adb, no USB mtp.
I've tried updating drivers on 3 different computers, (windows 7, Windows 10, and yosemite) Tried unbreakable tool and kfhd restore tool.
All I can do is manually boot to twrp.
I realize there's probably more details needed but I'm strapped for time (on break) I was just ? to see your thread.
Any attempts to help will be profoundly appreciated! Thanks.

KLit75 said:
Glad you're here to help. Like 6 weeks ago I attempted to return to stock. It was my understanding that I needed to downgrade twrp to flash the image (which I did easily . In the other thread it specified to wipe system first (REALLY wish I had thought that one through). Now I can't push ANYTHING to the SD card. No adb, no USB mtp.
I've tried updating drivers on 3 different computers, (windows 7, Windows 10, and yosemite) Tried unbreakable tool and kfhd restore tool.
All I can do is manually boot to twrp.
I realize there's probably more details needed but I'm strapped for time (on break) I was just to see your thread.
Any attempts to help will be profoundly appreciated! Thanks.
Click to expand...
Click to collapse
Can you still get to twrp?

sd_shadow said:
Can you still get to twrp?
Click to expand...
Click to collapse
Yes. That's all I can do. Not home but believe I'm running v 2.7.0.0
---------- Post added at 12:48 PM ---------- Previous post was at 12:40 PM ----------
I've had time to think about it and I doubt hashcode would make a mistake like telling people to wipe system. And if he were mistaken there would be a LOT of people in my situation. So I believe what sets me apart is that my recovery is too old. The right drivers aren't present and I can't use adb as a result.
I CAN get this into Factbook both with a factory cable and with a regular one (the latter only works on Mac it seems). However, on Windows the restore tools both say Fastboot is not recognized command. I believe I tried flashing the updated twrp with Fastboot on mac but for some reason it didn't work.

KLit75 said:
Yes. That's all I can do. Not home but believe I'm running v 2.7.0.0
---------- Post added at 12:48 PM ---------- Previous post was at 12:40 PM ----------
I've had time to think about it and I doubt hashcode would make a mistake like telling people to wipe system. And if he were mistaken there would be a LOT of people in my situation.
Click to expand...
Click to collapse
Wiping system is necessary to install a new system stock or custom
So I believe what sets me apart is that my recovery is too old.
Click to expand...
Click to collapse
possibly do you know the full file name of current recovery?
The right drivers aren't present and I can't use adb as a result.
Click to expand...
Click to collapse
What error(s) are you getting?
I CAN get this into Factbook both with a factory cable and with a regular one (the latter only works on Mac it seems). However, on Windows the restore tools both say Fastboot is not recognized command. I believe I tried flashing the updated twrp with Fastboot on mac but for some reason it didn't work.
Click to expand...
Click to collapse
"Fastboot is not recognized command." is a window issue not Kindle issue

Good info. Unfortunately I'm at work. But hopefully to nite I'll get what you're asking for. Really appreciate the help!

@sd_shadow
The current recovery is TWRP v2.7.0.0
I provided all the info I can think of at the moment. It's been about a month since I tried anything so my memory is a bit fuzzy. If you need anything specific please let me know. Bascially all I want to do is push any rom (custom or stock to this). I have the second bootloader and twrp working. I think MAYBE a newer version of TWRP may solve the driver issue. But I know I tried flashing twrp through fastboot and it din't work. I believe it just hung with no error listed.
Thought I might be on to something. I went into device manager and noticed the option to install legacy drivers. Both android and kindle show up so I got excited but it was short llived... Both attempts yielded they got installed but may not work. Sure enough they didn't. ��
Updated when in twrp over USB I can see kindle and now 3 android composite add interface. But they have a yellow triangle on them.
If I try to connect over add it says list of attached devices but show nothing. I tried mounting system but that does nothing
Clicking on Android in device manager I get this device cannot starts code 10

I spent a few hours trying different things and this seems to be my best bet (or at least the next thing I try). Can't do it tonight though because the windows pc I have is running adb 15 second installer and I don't have everything I need to complete it. If you or anyone else knows an easier way please share. Otherwise I'll setup sdk tools when I have a chance. Hopefully some time tomorrow. I'd prefer to do it on my mac because this pc isnt the best and really slowed me down tonight.
http://www.jayceooi.com/how-to-install-kindle-fire-adb-usb-driver/

KLit75 said:
I spent a few hours trying different things and this seems to be my best bet (or at least the next thing I try). Can't do it tonight though because the windows pc I have is running adb 15 second installer and I don't have everything I need to complete it. If you or anyone else knows an easier way please share. Otherwise I'll setup sdk tools when I have a chance. Hopefully some time tomorrow. I'd prefer to do it on my mac because this pc isnt the best and really slowed me down tonight.
http://www.jayceooi.com/how-to-install-kindle-fire-adb-usb-driver/
Click to expand...
Click to collapse
You have used the preferred driver from here Kindle_Fire_HD_ADB_Drivers.zip
What is your windows version?
Twrp should connect to the Mac, without issue, using mount usb or mtp.

sd_shadow said:
You have used the preferred driver from here Kindle_Fire_HD_ADB_Drivers.zip
What is your windows version?
Twrp should connect to the Mac, without issue, using mount usb or mtp.
Click to expand...
Click to collapse
Windows 10
I have NOOO idea how but I connected with mac. I swear to you I've tried connecting over adb before(MTP still didn't work btw). But I ran some basic commands with twrp mounted to SYSTEM, ran "adb devices" and it shows up. (I had tried SEVERAL variations of this before tonight)
Except instead of saying tate like it used to it had a string of letters/numbers then just said "recovery". Might be what it said before when in TWRP. I used to mostly use MTP when transferring files.
I was able to push the only amazon stockish files I could get 7.41 rooted+su from Hashcode. I also pushed updated TWRP and open apps for CM 12.1. Unfortunately adb push hung on that last one and then adb was gone. Couldn't connect. I bit the bullet and just flashed amazon and it worked. Just did this like 5 minutes ago so haven't tested root, recovery or anything else. I was intending on buying a kids case for this and letting my toddler son use it. We have prime and a lot of books i can access. So I might stay here but would like to get a newer version. Is there an easy way to get a later version of stock? I hate to give up root but he definitely doesn't need it and I've acquired several newer faster devices since I bought this a few years back.
Thanks a lot btw! I had sort of given up on this then I saw your thread. Just having someone to answer questions was enough to keep trying.

KLit75 said:
Windows 10
I have NOOO idea how but I connected with mac. I swear to you I've tried connecting over adb before(MTP still didn't work btw). But I ran some basic commands with twrp mounted to SYSTEM, ran "adb devices" and it shows up. (I had tried SEVERAL variations of this before tonight)
Except instead of saying tate like it used to it had a string of letters/numbers then just said "recovery". Might be what it said before when in TWRP. I used to mostly use MTP when transferring files.
I was able to push the only amazon stockish files I could get 7.41 rooted+su from Hashcode. I also pushed updated TWRP and open apps for CM 12.1. Unfortunately adb push hung on that last one and then adb was gone. Couldn't connect. I bit the bullet and just flashed amazon and it worked. Just did this like 5 minutes ago so haven't tested root, recovery or anything else. I was intending on buying a kids case for this and letting my toddler son use it. We have prime and a lot of books i can access. So I might stay here but would like to get a newer version. Is there an easy way to get a later version of stock? I hate to give up root but he definitely doesn't need it and I've acquired several newer faster devices since I bought this a few years back.
Thanks a lot btw! I had sort of given up on this then I saw your thread. Just having someone to answer questions was enough to keep trying.
Click to expand...
Click to collapse
With Win 8, 8.1 & 10, Disabling Driver Signature Enforcement is likely needed.
For those with Windows 8.1 or 10
Watch [Video] How to disable driver signature enforcement - Windows 8.1 & 8
or How to Disable Driver Signature Verification on 64-Bit Windows 8.1 or 10 (So That You Can Install Unsigned Drivers)
and try
Open the charm bar and go into Settings and at the bottom click on Change PC Settings.
Go to the update and Recovery on left then Recovery
Advanced Startup > restart now
Choose the Troubleshoot option followed by Advanced options.
Choose Startup settings then on next screen click on ‘restart’.
Select option
Disable driver signature enforcement
Windows 8.1 will now reboot and you can go ahead and use the Kindle_Fire_HD_ADB_Drivers.zip
more here https://learn.sparkfun.com/tutorials/disabling-driver-signature-on-windows-8/all​.

I signed up for free time and so far the only difference I see between 7.41 and a newer version would be inability to download prime titles. Of course this is my only amazon product running stock so I have nothing to compare it to. It's strange that the newest version on Hashcode's thread disappeared but older versions are still available. Usually it's the opposite.

KLit75 said:
I signed up for free time and so far the only difference I see between 7.41 and a newer version would be inability to download prime titles. Of course this is my only amazon product running stock so I have nothing to compare it to. It's strange that the newest version on Hashcode's thread disappeared but older versions are still available. Usually it's the opposite.
Click to expand...
Click to collapse
Download Information for OS 7.4.3:
http://goo.im/devs/Hashcode/tate/kfh...n-os-7.4.3.zip
md5sum: 45e687e8e85975348f81f5cbfc8358ac
The reason file is gone is the goo.im site is gone, I will look for a different source

found it on @Tomsgt 's site
kfhd7-amazon-os-7.4.3.zip
http://rootjunkysdl.com/?device=Kindle Fire HD 7in

sd_shadow said:
found it on @Tomsgt 's site
kfhd7-amazon-os-7.4.3.zip
http://rootjunkysdl.com/?device=Kindle Fire HD 7in
Click to expand...
Click to collapse
Thanks. Think I did stumble upon that when I first thought about return to stock. But I'm not sure...
That page shows stock. I think the version I have, 7.4.1, is a modded version of stock. I also see recovery. Zip which is what I need to go full stock. But I don't know if flashing that in twrp will get me to stock.
After struggling just to push a file I don't want to take any chances. If there's a clear way of doing it I'm all in. I think this device will be eligible for the OS 5 update so that'd be my motivation to sacrifice root.
A little off topic--free time is pretty cool if you have prime but adding locally stored videos is a hassle (haven't been able to do it) I'm sure amazon did this deliberately but there must be a workaround.
I was able to download prime videos. Unlike on my android phone, they need to be added to the library first.

Can anyone recommend a fastboot recovery cable for a 2012 kindle fire HD 7 (tate)?

FBis251 said:
Can anyone recommend a fastboot recovery cable for a 2012 kindle fire HD 7 (tate)?
Click to expand...
Click to collapse
Several links in my
What is a Fastboot Cable and Low Battery Options
written for Motorola Devices, but same cable.

I have added a
What is a Fastboot Cable? post to my Fire Index: Which Amazon (Kindle) Fire Do I have?

Droid Turbo (XT1254) autoiniroot problem

Hey.
I have a Droid Turbo XT1254 with bootloader locked (I am planning to unlock soon).
Recently, I stumbled across the thread and saw that someone had made rooting MCG25.251-5-5 possible and it made me want to try it out.
Anyways, I downloaded all the files (magisk and autoinitroot) and was able to root my phone just fine.
I tried giving Super user permission to some apps, and it worked flawlessly. I then tried to install Magisk module but oddly enough it failed.
It gave me an error that magisk was not properly installed. Also the SafetyNet check failed.
I decided to uninstall root, factory reset my device and root the device again.
Now the thing is that when I booted back into fastboot and ran the command that was meant to uninstall the root, it failed.
Obviously, I made sure that I was typing the correct command, I didn't even miss the "" marks. But it still didn't work.
It only gave me an error that the command 'confirm' doesn't exist.
I tried running the autoinit script and I booted just fine.
But the problem is that magisk isn't working properly and I'm unable to uninstall the autoinit root.
Any help will be greatly appreciated.
Also, Im using minimal adb and fast boot setup. Not sure if that's what causing the uninstall to fail or not.
TL; DR: Magisk doesn't work properly after doing the autoinitroot and I'm unable to uninstall the root by using the command that was mentioned in the original post.
Thanks for taking the time to read it

DuringSummer said:
Hey.
I have a Droid Turbo XT1254 with bootloader locked (I am planning to unlock soon).
Recently, I stumbled across the thread and saw that someone had made rooting MCG25.251-5-5 possible and it made me want to try it out.
Anyways, I downloaded all the files (magisk and autoinitroot) and was able to root my phone just fine.
I tried giving Super user permission to some apps, and it worked flawlessly. I then tried to install Magisk module but oddly enough it failed.
It gave me an error that magisk was not properly installed. Also the SafetyNet check failed.
I decided to uninstall root, factory reset my device and root the device again.
Now the thing is that when I booted back into fastboot and ran the command that was meant to uninstall the root, it failed.
Obviously, I made sure that I was typing the correct command, I didn't even miss the "" marks. But it still didn't work.
It only gave me an error that the command 'confirm' doesn't exist.
I tried running the autoinit script and I booted just fine.
But the problem is that magisk isn't working properly and I'm unable to uninstall the autoinit root.
Any help will be greatly appreciated.
Also, Im using minimal adb and fast boot setup. Not sure if that's what causing the uninstall to fail or not.
TL; DR: Magisk doesn't work properly after doing the autoinitroot and I'm unable to uninstall the root by using the command that was mentioned in the original post.
Thanks for taking the time to read it
Click to expand...
Click to collapse
1) why are you waiting to unlock your bootloader? Temp root is unstable and won't give you what you want.
2) of course Magisk won't work until you unlock your bootloader. Why would you think otherwise? On Motorola phones you have to unlock the bootloader to make changes like permanent root, install custom recovery, etc. Magisk just hides that.
3) you SAY you typed the correct command but after having a back-and-forth for two days over three pages with someone else who claimed the same thing and was WRONG, I'm skeptical.
Type exactly what you think is the correct command. Don't copy and paste anything. Actually type it out.
Better yet, post screenshot. That's how we proved to the other guy he was not reading what we had written.
"Oh, I didn't know."
Yes he did. It was in post #2, the very FIRST reply in the thread, which I wrote. And I told him over and over to go re-read that post!

Thanks for replying.
The answer to the first question is that I don't have $$$ right now. Will do it next month or so.
#2: Hahah. I did read that thread, and I'm pretty sure I'm not making that mistake, In any case I'll attach screenshots.

This is the screenshot. This time I tried specifying the directory to the fastboot.exe that came with autoinitroot, still no luck. Same error comes up regardless of whether I specify the directory or just use normal fastboot the came with minimal ADB.
And yes. I did it while I was in fastboot mode.
For some reason the app won't let me upload screenshot. Here is the link instead
http://i.imgur.com/Y5L5kvw.png

ChazzMatt said:
1) why are you waiting to unlock your bootloader? Temp root is unstable and won't give you what you want.
2) of course Magisk won't work until you unlock your bootloader. Why would you think otherwise? On Motorola phones you have to unlock the bootloader to make changes like permanent root, install custom recovery, etc. Magisk just hides that.
3) you SAY you typed the correct command but after having a back-and-forth for two days over three pages with someone else who claimed the same thing and was WRONG, I'm skeptical.
Type exactly what you think is the correct command. Don't copy and paste anything. Actually type it out.
Better yet, post screenshot. That's how we proved to the other guy he was not reading what we had written.
"Oh, I didn't know."
Yes he did. It was in post #2, the very FIRST reply in the thread, which I wrote. And I told him over and over to go re-read that post!
Click to expand...
Click to collapse
Yeah but in the original thread by autoprime, users have posted that they managed to install modules like "xposed systemless" etc. No reason it shouldn't work on mine.
Edit: Furthermore, autoptime himself mentioned that we can use custom magisk script to avoid boot loop, as far as I understand that's only possible when magisk recognizes modules.
Thing is that I have root, I can even use apps like titanium backup and whatnot. I can't use the script he mentioned unless magisk allows me to install something.

DuringSummer said:
This is the screenshot. This time I tried specifying the directory to the fastboot.exe that came with autoinitroot, still no luck. Same error comes up regardless of whether I specify the directory or just use normal fastboot the came with minimal ADB.
And yes. I did it while I was in fastboot mode.
For some reason the app won't let me upload screenshot. Here is the link instead
http://i.imgur.com/Y5L5kvw.png
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Your screenshot shows you typed "confirm". That's not the right command. It's "config".
fastboot oem config fsg-id ""

ChazzMatt said:
Your screenshot shows you typed "confirm". That's not the right command. It's "config".
fastboot oem config fsg-id ""
Click to expand...
Click to collapse
Oh. Hell. I feel stupid. I kinda copied from one the comments in OP. Will update brb.

Still doesn't work. This time it gave me error (bootloader) something-suffixes: false.
Etc etc. Will post screenshot.
EDIT: It WORKED. I placed the autoinitroot to desktop and changed the directory along with folder names. Ran the command, seems to have worked. Thanks anyways.
Probably had something to do with really long directory name. Idk.

DuringSummer said:
Yeah but in the original thread by autoprime, users have posted that they managed to install modules like "xposed systemless" etc. No reason it shouldn't work on mine.
Click to expand...
Click to collapse
Show me examples of that with Motorola phones.
I also have extensive experience with LG phones, and many of those (like LG G2 and LG G3) do not need bootloader unlock to root and install custom recovery. Whereas, Motorola phones require unlocked bootloader.
---------- Post added at 03:27 PM ---------- Previous post was at 03:21 PM ----------
DuringSummer said:
Still doesn't work. This time it gave me error (bootloader) something-suffixes: false.
Etc etc. Will post screenshot.
EDIT: It WORKED. I placed the autoinitroot to desktop and changed the directory along with folder names. Ran the command, seems to have worked. Thanks anyways.
Probably had something to do with really long directory name. Idk.
Click to expand...
Click to collapse
Yes, the suffixes errors are normal. Only by rebooting do you see if it worked.

ChazzMatt said:
Show me examples of that with Motorola phones.
I also have extensive experience with LG phones, and many of those (like LG G2 and LG G3) do not need bootloader unlock to root and install custom recovery. Whereas, Motorola phones require unlocked bootloader.
Click to expand...
Click to collapse
http://i.imgur.com/u06AaAV.png
http://i.imgur.com/7AHc5Bk.png
He explicitly mentioned that about bootloader locked Moto. Also the tool only works on Moto so.

DuringSummer said:
http://i.imgur.com/u06AaAV.png
http://i.imgur.com/7AHc5Bk.png
He explicitly mentioned that about bootloader locked Moto. Also the tool only works on Moto so.
Click to expand...
Click to collapse
Well, I know he was wrong about one thing. When the phone reboots it doesn't just boot into a stock system. Instead it bootloops and gets hung on the Moto logo. It never finishes booting until you run that end temp root command in fastboot.
Go to the thread and ask him how to do what he describes.... He is an expert and knows a lot more than me.
But also remember if your phone reboots in any way while you are away from your computer with fastboot installation, your phone will be totally useless until you get back to your computer and temp re-root or run that end temp root command.

ChazzMatt said:
Well, I know he was wrong about one thing. When the phone reboots it doesn't just boot into a stock system. Instead it bootloops and gets hung on the Moto logo. It never finishes booting until you run that end temp root command.
Click to expand...
Click to collapse
Oh that. What he meant was that if you place the custom magisk script in the right folder it will avoid boot loop and will boot into stock system, from there you'll have to use autoinitroot tool from pc again to re-root it, the script is handy if you're going somewhere and won't have access to pc. In which case, even if your phone gets turned off or reboots, it won't bootloop like crazy and you get access to stock system. Though you won't have root until you run autoroot script again from PC.
Also, it does provides full root. The only downside is that it isn't permanent. So as long as you're careful and don't mess with system and only use systemless modifications using magisk, you're safe. In worst case scenarios you'll only have to run the unroot command and factory reset to go back to 100% stock.
It's useful for those who can't get their bootloader unlocked.
Sadly, In my case magisk isn't working properly. That's why I'll factory reset and try again. Hopefully it'll work then.
Also do you by any chance know how and where to place custom scripts of magisk? Will be doing that after factory reset.
Also you helped a lot. Thanks, mate

DuringSummer said:
Oh that. What he meant was that if you place the custom magisk script in the right folder it will avoid boot loop and will boot into stock system, from there you'll have to use autoinitroot tool from pc again to re-root it, the script is handy if you're going somewhere and won't have access to pc. In which case, even if your phone gets turned off or reboots, it won't bootloop like crazy and you get access to stock system. Though you won't have root until you run autoroot script again from PC.
Also, it does provides full root. The only downside is that it isn't permanent. So as long as you're careful and don't mess with system and only use systemless modifications using magisk, you're safe. In worst case scenarios you'll only have to run the unroot command and factory reset to go back to 100% stock.
It's useful for those who can't get their bootloader unlocked.
Sadly, In my case magisk isn't working properly. That's why I'll factory reset and try again. Hopefully it'll work then.
Also do you by any chance know how and where to place custom scripts of magisk? Will be doing that after factory reset.
Also you helped a lot. Thanks, mate
Click to expand...
Click to collapse
His post #2 seems to talk about folders.

ChazzMatt said:
His post #2 seems to talk about folders.
Click to expand...
Click to collapse
Yeah. Saw that. Couldn't find those folders. Checked both root and normal storage.
Thanks anyway.

The whole temp root thing is really just a way to proceed with the bootloader unlock. to use temp root on any daily driver just seems like more trouble than its worth. Hurry up and find 25 bucks!!!
My opinion is that for the work that these guys do its a small price to pay and was money well spent

bigmatt503 said:
The whole temp root thing is really just a way to proceed with the bootloader unlock. to use temp root on any daily driver just seems like more trouble than its worth. Hurry up and find 25 bucks!!!
My opinion is that for the work that these guys do its a small price to pay and was money well spent
Click to expand...
Click to collapse
Actually, I don't have any problem paying 25 bucks. The thing is that I'm planning to buy a new phone. Seems really pointless spending 25$ on something that I'll replace in a few months. At first I thought that I should get it unlocked, however, this phone is 3 years old. I decided that I should upgrade to current technology.

ChazzMatt said:
Show me examples of that with Motorola phones.
I also have extensive experience with LG phones, and many of those (like LG G2 and LG G3) do not need bootloader unlock to root and install custom recovery. Whereas, Motorola phones require unlocked bootloader.
---------- Post added at 03:27 PM ---------- Previous post was at 03:21 PM ----------
Yes, the suffixes errors are normal. Only by rebooting do you see if it worked.
Click to expand...
Click to collapse
Caution thread jacking...... since you are very familiar with LG phones. What are the chances of the verizon g6 ever getting root?
Sent from my VS988 using XDA-Developers Legacy app