Today I decided to unleash my kfhd7 and install CyanogenMod.
After installing the 2nd Bootloader and the recovery, I 'accidentally' removed all my data in the hurry (anyway, I forgot to place the ROM on the SDCard folder before :silly. I was quite confident while doing this, based on my experience with other Android devices, I thought it would be easy to mount the SDCard folder to the computer using TWRP... But that wasn't the case. And my device was not recognize by ADB while in Recovery Mod.
After some research on the forum I noticed that the poor people who had this problem before had to reflash the stock image through the recovery. I used another method, mostly by finding a way to reinstall the drivers. So I decided to share my experience. I know that is maybe a bit noob, but I would enjoyed to find this tutorial while I was despaired and stuck on recovery mod.
Last precision : I am using Windows 8 (and I'm French, so pardon my French ).
What you need
ADB version 1.0.29 or higher you can find the version by typing "adb version" at the command terminal
Kindle Fire HD ADB drivers already installed, I guess it was the case if you were able to install the recovery. Other wise try to install it, you should find the the file executable easily on this forum.
The .zip file of whatever you want to flash, dont forget the gapps if you want to flash Cyanogen
That's all, no need of factory cable.
1. Install drivers
The first step is to reinstall the driver, considering the device was recognised before the flash but not anymore.
Open the Device Manager (hint: by typing directly devmgmt.msc)
You should see "Amazon Kindle Fire HD" under the "Other Devices"
Right click "update driver"
"Browse my computer for driver software"
"Let me pick from a list of device drivers on my computer"
"All devices" then next
At the bottom of the window you can choose a custom driver. Go this path:
C:\Windows\System32\DriverStore\FileRepository\android_winusb.inf_amd64_048d6e54936abbc3
The last number might be different (or may not, in fact I have no idea).
And voilà!!
Now adb should work.
2. Use sideload
You can now push your .zip to the sdcard, but TWRP have a really useful and smart way to do it.
Go into the advanced option of ADB. The click ADB sideload and swipe to start.
Just type
Code:
adb sideload yourfile.zip
and it's done! Don't forget to repeat it for googleapps if you need it.
For some reasons I had an error from TWRP complaining that he didn't find any OS installed. It worked anyway for me.
Just wanted to say merci bc.
Running the stock rom (rooted + 2nd boot-loader) I´ve flashed the "1.4 GHz(try me first)" by Maromi.
I made a backup before of everything but unfortunately moved. the files to my PC.
With the result of stucking at the blue Kindle logo.
A fastboot cable has been ordered but didn´t arrived in time before the week-end.
Just like you I´ve looked around quite a long time, tried several options but then your thread was the only solution!
By your advice I´ve sideloaded the last 7.3.1 (provided by hashcode) flashed and voilà - my kindle´s back!!
thx again!
Mistaz said:
Just wanted to say merci bc.
Running the stock rom (rooted + 2nd boot-loader) I´ve flashed the "1.4 GHz(try me first)" by Maromi.
I made a backup before of everything but unfortunately moved. the files to my PC.
With the result of stucking at the blue Kindle logo.
A fastboot cable has been ordered but didn´t arrived in time before the week-end.
Just like you I´ve looked around quite a long time, tried several options but then your thread was the only solution!
By your advice I´ve sideloaded the last 7.3.1 (provided by hashcode) flashed and voilà - my kindle´s back!!
thx again!
Click to expand...
Click to collapse
I'm glad that it was useful to you
I was affraid that I was the only one "enthusiastic" enough to do the mistake. :laugh:
gornog said:
Today I decided to unleash my kfhd7 and install CyanogenMod.
After installing the 2nd Bootloader and the recovery, I 'accidentally' removed all my data in the hurry (anyway, I forgot to place the ROM on the SDCard folder before :silly. I was quite confident while doing this, based on my experience with other Android devices, I thought it would be easy to mount the SDCard folder to the computer using TWRP... But that wasn't the case. And my device was not recognize by ADB while in Recovery Mod.
After some research on the forum I noticed that the poor people who had this problem before had to reflash the stock image through the recovery. I used another method, mostly by finding a way to reinstall the drivers. So I decided to share my experience. I know that is maybe a bit noob, but I would enjoyed to find this tutorial while I was despaired and stuck on recovery mod.
Last precision : I am using Windows 8 (and I'm French, so pardon my French ).
What you need
ADB version 1.0.29 or higher you can find the version by typing "adb version" at the command terminal
Kindle Fire HD ADB drivers already installed, I guess it was the case if you were able to install the recovery
The .zip file of whatever you want to flash, dont forget the gapps if you want to flash Cyanogen
That's all, no need of factory cable.
1. Install drivers
The first step is to reinstall the driver, either the device was recognised before the flash.
Open the Device Manager (by typing directly devmgmt.msc)
You should see "Amazon Kindle Fire HD" under the "Other Devices"
Right click "update driver"
"Let me pick driver on my computer"
"choose in a list..."
"All devices" then next
At the bottom of the window you can choose a custom driver. Go this path:
C:\Windows\System32\DriverStore\FileRepository\android_winusb.inf_amd64_048d6e54936abbc3
The last number might be different (or may not, in fact I have no idea).
And voilà!!
Now adb should work.
2. Use sideload
You can now push your .zip to the sdcard, but TWRP have a really useful and smart way to do it.
Go into the advanced option of ADB. The click ADB sideload and swipe to start.
Just type
Code:
adb sideload yourfile.zip
and it's done! Don't forget to repeat it for googleapps.
For some reason I had an error from TWRP complaining that he didn't find any OS installed. It worked anyway for me.
Click to expand...
Click to collapse
After following your steps I will get to the part where i have to click the last file for the drivers and after I do my computer will say that Windows was unable to find the drivers for the KFHD7, if you have any suggestions on what to do that would be greatly appreciated.
th3lawmak3r76 said:
After following your steps I will get to the part where i have to click the last file for the drivers and after I do my computer will say that Windows was unable to find the drivers for the KFHD7, if you have any suggestions on what to do that would be greatly appreciated.
Click to expand...
Click to collapse
Did ADB worked properly before, with drivers installed? If so you can try something else to reinstall it.
The first step are the same,
Right click "update driver"
"Browse my computer for driver software"
"Let me pick driver on my computer"
And try to find in the list if there is a "Kindle Fire" in the list of devices. You might be able to install it from here.
Otherwise try to reinstall the amazon adb driver (you can find it easily in this forum), and then eventually perform again the operation above.
Update software driver of Windows7 32 bit path :
C:\Windows\system32\driver\ android_winusb.inf
I've tried all your steps and plenty more all over this forum.. I can't figure out why my Kindle HD 8.9 wont connect properly so I could push the rom via ADB.. I basically fell through the same issue as you.. except I'm stuck at trying to get Windows to recognize the Kindle properly... This is what I get regardless of what driver, or .inf I push at 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"
}
/10postprereq
EDIT: I got it working, thank you very much for your post.. Helped a lot
gornog said:
2. Use sideload
You can now push your .zip to the sdcard, but TWRP have a really useful and smart way to do it.
Go into the advanced option of ADB. The click ADB sideload and swipe to start.
Just type
Code:
adb sideload yourfile.zip
and it's done! Don't forget to repeat it for googleapps if you need it.
For some reasons I had an error from TWRP complaining that he didn't find any OS installed. It worked anyway for me.
Click to expand...
Click to collapse
For some reason I cannot get this to work. I must not be typing the command language properly.
adb sideload cm-10.1xxxx
I get the following message:cannot read "sideload"
Any thoughts here? Thanks!!
krakora said:
For some reason I cannot get this to work. I must not be typing the command language properly.
adb sideload cm-10.1xxxx
I get the following message:cannot read "sideload"
Any thoughts here? Thanks!!
Click to expand...
Click to collapse
Make sure the ROM or file you're sideloading is in the same directory from which you are sending the command, or replace the filename with the exact full path to the file.
Success
soupmagnet said:
Make sure the ROM or file you're sideloading is in the same directory from which you are sending the command, or replace the filename with the exact full path to the file.
Click to expand...
Click to collapse
Thanks soupmagnet. Yes and Yes.
First: I did not have the Android SDK tools set up properly. I watched the interwebs and took some time to learn the very basic ADB commands. Once I changed directories to the desktop (where my zips were sitting) the simple sideload was a snap. I did get "error closed" message a couple times and used "adb usb" seemed to restart the process. At the end of day, success, my Kindle is flipping awesome now, I know a bit more about pushing files using ADB, and all is good in the world.
Thanks again XDA Developers!
PS: As a side note... I was on 7.4.3 version of the Amazon software and when I installed TWRP and the bootloader. Flash fire makes you switch to 7.2.3 version of the bootloader. I think that is what hosed me in the process... I could only get to recovery and it was like the OS was gone afterwards. Anyways, if you get trapped in recovery, get ready to learn something. :good:
I'm having trouble getting ADB to recognize the sideload command. I have found 2 different places that it is installed on my computer.
Do I use the ADB in the Android SDK, or the one in the Kindle Fire First Aide folder? When I try to open the one in the Android SDK folder the CMD Prompt pops up and flashes loads of text before auto closing, I get the same thing from the KF First Aide folder.
I just need to get my rom.zip onto my Kindle Fire HD, but I am totally lost on where to go from here since I am stuck on either the Boot screen or the TWRP bootloader.
Any help you can offer would be greatly appreciated.
ButchTheKitty said:
I'm having trouble getting ADB to recognize the sideload command. I have found 2 different places that it is installed on my computer.
Do I use the ADB in the Android SDK, or the one in the Kindle Fire First Aide folder? When I try to open the one in the Android SDK folder the CMD Prompt pops up and flashes loads of text before auto closing, I get the same thing from the KF First Aide folder.
I just need to get my rom.zip onto my Kindle Fire HD, but I am totally lost on where to go from here since I am stuck on either the Boot screen or the TWRP bootloader.
Any help you can offer would be greatly appreciated.
Click to expand...
Click to collapse
You don't run ADB like a standalone program. It's just a series of commands to be used from the command line. In order for this to work, the adb executable/binary/whatever must be in the same directory from which you are entering the commands (research the 'cd' command for more details).
Also, for the "sideload" command to work, your device must be booted into TWRP and you have to execute the sideload function from the "Advanced" menu.
soupmagnet said:
You don't run ADB like a standalone program. It's just a series of commands to be used from the command line. In order for this to work, the adb executable/binary/whatever must be in the same directory from which you are entering the commands (research the 'cd' command for more details).
Also, for the "sideload" command to work, your device must be booted into TWRP and you have to execute the sideload function from the "Advanced" menu.
Click to expand...
Click to collapse
Thanks for the quick reply, I decided to just re-flash to the stock 8.1.4 and restart the process, only this time I made sure to put the .zip folder for the new Rom on the systems storage first. Seems to be working so far, CyanogenMod is installing as I type this.
Thanks so much for working on this though, you guys do amazing work.
Dam thank you man
man with out this tread i would be F in a major way i have suceded in bricking two kindle fires hd 7 in the last week
one is compleatly dead dead dead waiting on factory cable. the other i was able to rescue today because of your post
(op) post,
i am not new to ADB, but the kffa, twrp,and other programs used to do these projects never seem to work, for me always stop at a bad time
. The thread installing twrp-2nd bootloader on this site has major flaws i am new to this so i chose 1st timer treads
(thing for dummies) things like step by step instructions, like i was able to follow your instructions easily (although you should have used an address like C;/desktop/xxxx.zip insted of (your zipfile) in the sideload code example. after i figerd out that deal it was easly done 5 min later loaded the code into adb ADB sideload C;/desktop/kfhd7-amizon-os-7.4.3.zip and 5 min after that my kindle rebooted and was back to normal all files intact even my apps. like i never touch a thing. it upgraded back to 7.4.6 and reloaded my apps.
I followed the instructions to a tee 2 times on the "root and recovery w/TWRP" tread and both times wound up having the programs kffa, and twrp, flashfile. stop at some point during the process, and result in me bricking.
i could have missed something or maybe the step by step missed a step or maybe my jdk was f but both time
i was screwed.
I think maybe they don't see the reader as a novice, although most if not all readers here are a novice's of some kind and so leave out info needed to complete with success, the tread i mention earlier he steered away from the topic so many times it made it almost impossible to follow and only refereed to successful outcomes, like put this into the cmd line next do this. but not stopping to think what if the person reading didnt get that response from the command line what do i do then?
And thats just what happen to me both times everything was going great and he said put this adb code in and i couldn't get it to respond like he said or it stoped cant find device or just sit there and do nothing, screwed... im into it now cant back up cant go forward your screwed. anyway my rant over now. THANKS FOR MAKING THIS TREAD you saved my ass.
thelz said:
man with out this tread i would be F in a major way i have suceded in bricking two kindle fires hd 7 in the last week
one is compleatly dead dead dead waiting on factory cable. the other i was able to rescue today because of your post
(op) post,
i am not new to ADB, but the kffa, twrp,and other programs used to do these projects never seem to work, for me always stop at a bad time
. The thread installing twrp-2nd bootloader on this site has major flaws i am new to this so i chose 1st timer treads
(thing for dummies) things like step by step instructions, like i was able to follow your instructions easily (although you should have used an address like C;/desktop/xxxx.zip insted of (your zipfile) in the sideload code example. after i figerd out that deal it was easly done 5 min later loaded the code into adb ADB sideload C;/desktop/kfhd7-amizon-os-7.4.3.zip and 5 min after that my kindle rebooted and was back to normal all files intact even my apps. like i never touch a thing. it upgraded back to 7.4.6 and reloaded my apps.
I followed the instructions to a tee 2 times on the "root and recovery w/TWRP" tread and both times wound up having the programs kffa, and twrp, flashfile. stop at some point during the process, and result in me bricking.
i could have missed something or maybe the step by step missed a step or maybe my jdk was f but both time
i was screwed.
I think maybe they don't see the reader as a novice, although most if not all readers here are a novice's of some kind and so leave out info needed to complete with success, the tread i mention earlier he steered away from the topic so many times it made it almost impossible to follow and only refereed to successful outcomes, like put this into the cmd line next do this. but not stopping to think what if the person reading didnt get that response from the command line what do i do then?
And thats just what happen to me both times everything was going great and he said put this adb code in and i couldn't get it to respond like he said or it stoped cant find device or just sit there and do nothing, screwed... im into it now cant back up cant go forward your screwed. anyway my rant over now. THANKS FOR MAKING THIS TREAD you saved my ass.
Click to expand...
Click to collapse
Which thread did you use to install TWRP?
>>Sent from my homebuilt TARDIS running Android 4.3... Or maybe it's a rooted Kindle Fire HD running ChameleonOS<<
Adb sideload not working
Hi guys, i need your help please! I am at the twrp menu trying to open adb sideload and it says"starting adb sideload feature..." but it stays like that for ages. Any idea??
guidomagaldi said:
Hi guys, i need your help please! I am at the twrp menu trying to open adb sideload and it says"starting adb sideload feature..." but it stays like that for ages. Any idea??
Click to expand...
Click to collapse
Stunts has a nice write up on this exact thing here http://forum.xda-developers.com/showthread.php?t=2459498
LinearEquation said:
Stunts has a nice write up on this exact thing here http://forum.xda-developers.com/showthread.php?t=2459498
Click to expand...
Click to collapse
thanks! its working!
guidomagaldi said:
thanks! its working!
Click to expand...
Click to collapse
You're welcome. Stunts did the write up, I just laid it out for you to play out.
Sent from my Amazon Kindle Fire HD running CM 10.2 using xda app-developers
Help please
gornog said:
Today I decided to unleash my kfhd7 and install CyanogenMod.
After installing the 2nd Bootloader and the recovery, I 'accidentally' removed all my data in the hurry (anyway, I forgot to place the ROM on the SDCard folder before :silly. I was quite confident while doing this, based on my experience with other Android devices, I thought it would be easy to mount the SDCard folder to the computer using TWRP... But that wasn't the case. And my device was not recognize by ADB while in Recovery Mod.
After some research on the forum I noticed that the poor people who had this problem before had to reflash the stock image through the recovery. I used another method, mostly by finding a way to reinstall the drivers. So I decided to share my experience. I know that is maybe a bit noob, but I would enjoyed to find this tutorial while I was despaired and stuck on recovery mod.
Last precision : I am using Windows 8 (and I'm French, so pardon my French ).
What you need
ADB version 1.0.29 or higher you can find the version by typing "adb version" at the command terminal
Kindle Fire HD ADB drivers already installed, I guess it was the case if you were able to install the recovery. Other wise try to install it, you should find the the file executable easily on this forum.
The .zip file of whatever you want to flash, dont forget the gapps if you want to flash Cyanogen
That's all, no need of factory cable.
1. Install drivers
The first step is to reinstall the driver, considering the device was recognised before the flash but not anymore.
Open the Device Manager (hint: by typing directly devmgmt.msc)
You should see "Amazon Kindle Fire HD" under the "Other Devices"
Right click "update driver"
"Browse my computer for driver software"
"Let me pick from a list of device drivers on my computer"
"All devices" then next
At the bottom of the window you can choose a custom driver. Go this path:
C:\Windows\System32\DriverStore\FileRepository\android_winusb.inf_amd64_048d6e54936abbc3
The last number might be different (or may not, in fact I have no idea).
And voilà!!
Now adb should work.
2. Use sideload
You can now push your .zip to the sdcard, but TWRP have a really useful and smart way to do it.
Go into the advanced option of ADB. The click ADB sideload and swipe to start.
Just type
Code:
adb sideload yourfile.zip
and it's done! Don't forget to repeat it for googleapps if you need it.
For some reasons I had an error from TWRP complaining that he didn't find any OS installed. It worked anyway for me.
Click to expand...
Click to collapse
Hey please help me I have donwloaded amazon kindle fire but it doesn't displays in my device manager furthermore in my computer I cant find driver software but yes in program files i do have amazon kindle folder, what should I do please help
Related
TGA_Gunnman created a one click root that new users will want to use, said thread is a sticky in Captivate Development. If you still want to use the old method (and install ADB) please use this one.
I followed my own guide! This works perfectly if you read everything and follow the instructions.
Also: once you are rooted, be EXTREMELY careful! Half of the new threads are people who have screwed up their phones by deleting this or corrupting that. Please, for the sanity of all of the devs and Android veterans, make backups and just be all around careful. Almost all problems that anyone has had are repareable AND PREVENTABLE with a little reading and care. Just to clarify, rooting does not automatically enable sideloading. Please follow http://forum.xda-developers.com/showthread.php?t=738376 to enable sideloading.
Follow these steps exactly and there will be no risk of bricking your Captivate, the worst that may happen is the phone rejecting the update.zip.
HOWEVER:
I take no responsibility if ANYTHING at all happens to your device that you don't like. Don't come crying to me if your brand new phone breaks in any way. Your warranty is also void, but you could have figured that out for yourself.
Now that that's over with, lets get to the fun bit. If you are on Windows, you can follow this procedure, or for TGA_Gunnman's one click root program (only on Windows), you can go ahead and skip to the bottom.
1) You may need Samsung drivers if you are on a PC, which you can learn about here: ADB Drivers at the Unlockr
For 64 bit Windows, you'll need these drivers: http://zedomax.com/blog/2010/07/14/s...iver-download/
Don't proceed until your phone is fully installed on Windows with the drivers!
2) Download the attached zip (at the bottom of the post) and rename it to update or update.zip if you are on a Mac. (If you are on a Mac, DO NOT USE SAFARI to download the file, it automatically unzips any zip file. Use Google Chrome or firefox instead.) Scroll down the notification bar and click "mount" to allow your computer to read the internal memory. Put the file on the INTERNAL SD card of the Captivate, which won't be tough to figure out if you don't have an SD card in the phone.
3) EDIT--There is an easier way to get to recovery, but do this step anyway. Turn the phone off, then hold power, volume up and volume down. If you still want the android SDK (which will be very useful throughout your rooted experiences) follow the old procedure:
This step requires the Android SDK, and Android Debugging enabled. You can get the SDK here: Android SDK. Just download the zip, extract it to something like C:\Android. You won't need the Java dev pack or anything.
You can enable Android Debugging like this: From the homescreen, press Menu, then click Settings. Navigate to Applications>Development and check USB Debugging. Now, hook the phone to the computer. Next,
On a PC, click start>run>"cmd" (in the text box) or on a Mac, spotlight "Terminal". Linux users, you know what to do.
The command you will use is in the tools folder of wherever you extracted it to (IE: C:\android\tools), so be sure your working directory of command prompt is in that tools location!
Finally, type:
Code:
adb reboot recovery
Click to expand...
Click to collapse
4) Once the phone is booted into recovery, use the volume keys on the phone to scroll to "Reinstall packages." Use power to select what you have highlighted.
5) Give yourself a pat on the back. You are now rooted. You should see a Superuser application now.
MD5 Sum: 1eb65923281c113e8751a7d8a6faff43
Can we please have more detailed instructions? I don't understand the part where it says "type in the terminal"
I am very new to android as this will be my first Android phone.
Also, after rooting will we be able to install 3rd party applications? Or do we have to do anything else to bypass ATT's restrictions?
adb terminal is software you need to install on your PC , will probably need samsung drivers also , guide is indeed not noob friendly. This will help you get needed bits including ADB
Probably None of us have captivate , so writing a guide is a bit troublesome
Ditto, a guide to the adb terminal please! I will acquire this phone, this Sunday.
Actually, you'd have to install a custom ROM for that. MoDaCo should be coming out with them pretty soon, and so will XDA. It won't be too long. BTW, once you have ADB installed on your computer, you can sideload apps all you want. The command is
Code:
adb install /directory/of/app/on/computer
point me to some functioning samsung drivers and I can do this!
If you cant get it to work on windows, try a ubuntu live cd. All you need to do is go to ubuntu and burn a disc and reboot.
Are there no Windows 64 bit drivers?
Edit- I found some that work. I think. Haven't tried it (yet).
http://zedomax.com/blog/2010/07/14/...ic-4g-and-fascinate-galaxy-s-driver-download/
Edit 2- Just did the root. Seems to have worked (no errors) but how do I know if it did? How do I delete say, ATT Maps?
Thanks for this. I am new to smartphones and plan on purchasing the Samsung Galaxy-S, but don't want to mess it up. I am new to editing the OS of any smartphone, but I think if I have a tutorial I will be fine
For Mac and Linux you put a ./ in front of the adb correct? (./adb install...)
NOSintake said:
For Mac and Linux you put a ./ in front of the adb correct? (./adb install...)
Click to expand...
Click to collapse
if you are in the directory above yes. the ./ just saves you from writing out the full path
lets say adb is in "/home/user/Downloads/sdk/tools"
you could type out "/home/user/Downloads/sdk/tools/adb command" regardless of where your terminal window was focused
or if you were currently in the directory "/home/user/Downloads/sdk/tools"
you could use the shortcut "./adb command"
OP I'd change your post based on my experiences... Here's a little more detail and I've rearranged it (you need the drivers before running these commands, for example).
blackjackboy said:
Please let me know if this rooting method works as I have no Captivate to test on. I'm not taking any credit for any of these files, LeshaK made the original file to root the European Galaxy S, Justadude modified it for the T-Mobile Vibrant and chaoscentral edited the file for use on the Captivate.
Follow these steps exactly and there will be no risk of bricking your Captivate, the worst that may happen is the phone rejecting the update.zip.
HOWEVER:
I take no responsibility if ANYTHING at all happens to your device that you don't like. Don't come crying to me if your brand new phone breaks in any way.
Now that that's over with, lets get to the fun bit.
1) You may need Samsung drivers if you are on a PC, which you can learn about here: ADB Drivers at the Unlockr
For 64 bit Windows, you'll need these drivers: http://zedomax.com/blog/2010/07/14/...ic-4g-and-fascinate-galaxy-s-driver-download/
Don't proceed until your phone is fully installed on Windows with the drivers!
2) Download the attached zip (at the bottom of the post) and rename it to update or update.zip if you are on a Mac. Scroll down the notification bar and click "mount" to allow your computer to read the internal memory. Put the file on the INTERNAL SD card of the Captivate, which won't be tough to figure out if you don't have an SD card in the phone.
3) This step requires the Android SDK, and Android Debugging enabled. You can get the SDK here: Android SDK. Just download the zip, extract it to something like C:\Android. You won't need the Java dev pack or anything.
You can enable Android Debugging like this: From the homescreen, press Menu, then click Settings. Navigate to Applications>Development and check USB Debugging. Now, hook the phone to the computer. Next,
On a PC, click start>run>"cmd" (in the text box) or on a Mac, spotlight "Terminal". Linux users, you know what to do.
The command you will use is in the tools folder of wherever you extracted it to (IE: C:\android\tools), so be sure your working directory of command prompt is in that tools location!
Finally, type:
Code:
adb reboot recovery
4) Once the phone is booted into recovery, use the volume keys on the phone to scroll to "Reinstall packages." Use power to select what you have highlighted.
5) Give yourself a pat on the back. You are now rooted. You should see a Superuser application now.
Thank you to LeshaK, Justadude, and chaoscentral. Once again, I didn't discover how to root, that credit goes to LeshaK, bringing it over to the USA was Justadude's doing, and chaoscentral edited the file for use on our Captivates.
MD5 Sum: 1eb65923281c113e8751a7d8a6faff43
Click to expand...
Click to collapse
Ubuntu 10.04 - adb
Any step by step instructions just to get adb running enough on 10.04 to root and side load software? I'm getting command not found when I try to run adb, even after downloading packages.
Hi,
Did this thread worked well to Root the Captivate or anyother suggested link? I'll appreciate any help.
Thanks
rerooting captivate
This worked perfectly on my Captivate. I now have the SuperUser Permission on my application screen. Now I can REALLY screw up my Captivate!!!
Thanks for the answer & More Queston
cellgeek said:
This worked perfectly on my Captivate. I now have the SuperUser Permission on my application screen. Now I can REALLY screw up my Captivate!!!
Click to expand...
Click to collapse
Hi,
Thanks for your helpful answer. As I'm getting my Cativate tomorrow, can you please just answer yes or no to each of my questions as follow ?
After Rooting will I be able to:
1- download any 3rd party Android application?
2- install any "Samsung Galaxy S" ROM on my Captivate?
3- Recieve any "OTA" update as a "Galaxy S" phone?
Thanks again
Muhamadabdelaall said:
Hi,
Thanks for your helpful answer. As I'm getting my Cativate tomorrow, can you please just answer yes or no to each of my questions as follow ?
After Rooting will I be able to:
1- download any 3rd party Android application?
2- install any "Samsung Galaxy S" ROM on my Captivate?
3- Recieve any "OTA" update as a "Galaxy S" phone?
Thanks again
Click to expand...
Click to collapse
1. No. You will have to use adb or the database modification method (which having root access makes possible). Both are described in detail elsewhere in this forum.
2. Rooting means simply getting superuser permissions. Loading a ROM has to do with the bootloader and recovery partition. Unmodded Galaxy S ROMs probably will not work on the Captivate, but be patient.
3. Not sure what you're asking. You will still get any Captivate OTA updates as if you hadn't rooted, but you won't get, for example, the rumored Korean FroYo Galaxy S update OTA when it drops. You'd have to wait for the Captivate OTA FroYo upgrade (or there may be a ROM or patch you can flash by then).
Rooting is basically just allowing programs to run as the superuser account. Many programs like Metamorph, some screenshot apps and some wifi tethering apps require more permission than Android normally gives an app.
Thanks Drachen
Drachen said:
1. No. You will have to use adb or the database modification method (which having root access makes possible). Both are described in detail elsewhere in this forum.
2. Rooting means simply getting superuser permissions. Loading a ROM has to do with the bootloader and recovery partition. Unmodded Galaxy S ROMs probably will not work on the Captivate, but be patient.
3. Not sure what you're asking. You will still get any Captivate OTA updates as if you hadn't rooted, but you won't get, for example, the rumored Korean FroYo Galaxy S update OTA when it drops. You'd have to wait for the Captivate OTA FroYo upgrade (or there may be a ROM or patch you can flash by then).
Rooting is basically just allowing programs to run as the superuser account. Many programs like Metamorph, some screenshot apps and some wifi tethering apps require more permission than Android normally gives an app.
Click to expand...
Click to collapse
Thanks alot for taking all this time & energy to reply to me! WOW, it seems like everytime I wanna step up one, I go back 10 steps. All I need is to use my Captivate for installing a Stock Rom of "Galaxy S" & be able to get rid of any "AT&T" restrictions for anything on this phone, what should I do please?
Thanks
Muhamadabdelaall said:
Thanks alot for taking all this time & energy to reply to me! WOW, it seems like everytime I wanna step up one, I go back 10 steps. All I need is to use my Captivate for installing a Stock Rom of "Galaxy S" & be able to get rid of any "AT&T" restrictions for anything on this phone, what should I do please?
Thanks
Click to expand...
Click to collapse
The ATT stuff doesn't actually run so they aren't a big deal at this point. I also don't see Amazon MP3 background stuff like some Android devices have, so... There's really not a huge case for rooting yet.
That said, when Custom ROMs for this come out I'll still be getting one.
For those of you having a hard time installing ADB Shell, try this video. It worked for me.
http://www.youtube.com/watch?v=YeWH6Bj1DYw&feature=related
So I am not quite sure what exactly fastboot is supposed to do. I know you can flash recoveries, bootloaders, etc with it but that is about it for my understanding.
I tried to get into fastboot (following instructions here on the forum) mode earlier today and while the tablet gives me the fastboot message in the upper left, windows says that fastboot failed. Is there a folder I am supposed to be running cmd prompt from?
Sorry, still new to this stuff and my understanding of some of these tools is limited at best.
Sent from my A500 using Tapatalk 2
a friendly warning
CyaN1de said:
So I am not quite sure what exactly fastboot is supposed to do. I know you can flash recoveries, bootloaders, etc with it but that is about it for my understanding.
I tried to get into fastboot mode earlier today and while the tablet gives me the fastboot message in the upper left, windows says that fastboot failed. Is there a folder I am supposed to be running cmd prompt from?
Sorry, still new to this stuff and my understanding of some of these tools is limited at best.
Sent from my A500 using Tapatalk 2
Click to expand...
Click to collapse
Give me 30 mins got all the reading u gonna need b4 u make an attempt
if u fk up in here there is definitely NO WAY BACK in meantime you'll
Want to set adb as environmental variable in windows gonna make it
Helluva lot easier . Android sdk will too. f u don't know what I'm on About..
.best do some reading up on these as well.
Fast boot ain't something someone else can talk u thru and I doubt the devs will
Have any sympathy for anyone asking ....i bricked my tab pls help....
dibb_nz said:
Give me 30 mins got all the reading u gonna need b4 u make an attempt
if u fk up in here there is definitely NO WAY BACK in meantime you'll
Want to set adb as environmental variable in windows gonna make it
Helluva lot easier . Android sdk will too. f u don't know what I'm on About..
.best do some reading up on these as well.
Fast boot ain't something someone else can talk u thru and I doubt the devs will
Have any sympathy for anyone asking ....i bricked my tab pls help....
Click to expand...
Click to collapse
Running adb from its native folder is not an issue.....is fastboot the same way having to run cmd from folder that a file is located?
I prefer not to mess stuff that I do not fully comprehend (not that I fully comprehend ANY of this) but some of it makes more sense once you are into it rather than reading someone elses interpretation.
Sent from my A500 using Tapatalk 2
CyaN1de said:
Running adb from its native folder is not an issue.....is fastboot the same way having to run cmd from folder that a file is located?
I prefer not to mess stuff that I do not fully comprehend (not that I fully comprehend ANY of this) but some of it makes more sense once you are into it rather than reading someone elses interpretation.
Sent from my A500 using Tapatalk 2
Click to expand...
Click to collapse
yeh just a group of extended adb commands that allow you to do some pretty awesome stuff - like really, really bricking your tab for instance, lol. I'm unsure as to whether all the fastboot commands are available to us - i havent had enough spare time to devote to heavy duty reading in the Dev Forums!!!! You can flash everything in here so its like a supercharger;;;;Sort of like going from timmydeans EUU root to Civ's nvflash unlocking bootloaders thing, if you know what i mean.......
But heres some reading, most of it tutorial step by step stuff, mostly for other devices which may not apply to our tab but definitely apply to fastboot. AS you know, there is alot of info in our own dev forum but its hard to find a flow as the devs actually speak a different language to us!!!! So the tutorials are quite good in that respect as they use noob-ite speak
the backup and restore tute is a goody, couldnt get it going on v3 so looking forward to giving it a go on v4 (when i can find a quiet 30 mins or so, that is)
anyways happy reading be interested in your thoughts and keep us posted about what you get around to trying
rgds
Full Phone Backup http://forum.xda-developers.com/showthread.php?t=1420351
setup adb http://forum.xda-developers.com/showthread.php?t=1249798
adb http://forum.xda-developers.com/showthread.php?t=879701
adb logcat http://droid-force.com/showthread.php?tid=150&pid=573#pid573
ics BL by Skrilax_CZ http://forum.xda-developers.com/showthread.php?t=1514951
So I located Fastboot in D:\Android\android-sdk\platform-tools\Fastboot.exe
But putting tablet into fastboot mode yields the driver installer to report that "Device driver software was not succesfully installed".......Fastboot X Failed....is this normal? Will it run when I use cmd prompt from D:\Android\android-sdk\platform-tools?
I guess a little linux knowledge would go a long way.....too bad I can't get a grasp on that either.
Thanks for the links.....hopefully I can find time to give a read.
Set up adb/fastboot for noob-ites 101
CyaN1de said:
So I located Fastboot in D:\Android\android-sdk\platform-tools\Fastboot.exe
But putting tablet into fastboot mode yields the driver installer to report that "Device driver software was not succesfully installed".......Fastboot X Failed....is this normal? Will it run when I use cmd prompt from D:\Android\android-sdk\platform-tools?
I guess a little linux knowledge would go a long way.....too bad I can't get a grasp on that either.
Thanks for the links.....hopefully I can find time to give a read.
Click to expand...
Click to collapse
weird??? i kicked straight in to bl, fastboot drivers installed, never saw red x
u mean u arent cmd from platform tools???
in the cpuid guide I suggested extracting the just_adb.zip into C:\ so setting
up the env. var. would be easier I have been meaning to post the steps for
doing that, guess theres no time like the present
Set adb as Environment Variable or call adb direct from command prompt
............ first, copy the path to your install - in your case:
............ "Path to adb" = D:\Android\android-sdk\platform-tools
1. Click on the Start menu
2. Right click on Computer
3. Click on Advanced system settings
4. Click on the Environment Variables button
5. Look for Path in the System Variables section. Double click on it
6. Go to the end of the Variable value box and put in a semicolon ;
7. Now paste your "Path to adb" after the ;
8. it should look like this in your case ;D:\Android\android-sdk\platform-tools
9. Now test it out - start - run/search - cmd - in cmd window type: adb devices
10. If you've followed the steps you will see your device ID - voila!!!!
as you can see this makes trouble shooting so dam easy -
if you cant get a device id do not go any further in what u r doing
cos it aint gonna work....period!!!!! also since ICS has screwed
with getting our cpuid like this, for our purpose here, it is only important
that a device id is shown - not how right or wrong it is.....clear????
so getting back to it, check fastboot*.exe in same folder as adb.exe -
it came like this in my own setup not sure about the asdk setup -
remember too fastboot only has a few commands and i still havent
got round to trying them all out yet....
to anyone following this, I cannot say enough how dangerous this can be
please, please, please take a moment to read thru just one of the links i
posted earlier - they are tutorials and if you see the dev thread regarding
v4 unlock...you will not only learn something amazing but begin to
appreciate and respect the work done by these devs who laid the groundwork
that enabled civato and blakthund3r to produce what they have with the
unlocked bootloader - without this groundwork we would still be waiting
for a way to get full root access and cwm, custom roms, themes and mods......
Thanks for that
Seems my Windows skillz need brushing up on again too....LOL
C:\Users\username>adb devices
List of devices attached
11717XXXXXX device
CyaN1de said:
Thanks for that
Seems my Windows skillz need brushing up on again too....LOL
C:\Users\username>adb devices
List of devices attached
11717XXXXXX device
Click to expand...
Click to collapse
sweet m8 -
yeh whoever thought windoze would actually be useful!!!!
which i guess is freakn handy as having to go linux would spin me out....
what can i say??? I'm a child of windoze had no choice, forced-addiction
before i was born, lol - breaking the habit, but always go back, goddamit
OK....I get the adb ok.
But when I put tab into FB i get the driver error (see attachment). I suppose that I should not be getting this?
Trying just "fastboot reboot" (not wanting to go any farther until I get a grasp...HAHA) I get "waiting for device"
CyaN1de said:
OK....I get the adb ok.
But when I put tab into FB i get the driver error (see attachment). I suppose that I should not be getting this?
Click to expand...
Click to collapse
dont let windows install
choose let me choose where to install dunno exact wording
Does not give me a choice.
Driver is located at D:\Android\android-sdk\extras\google\usb_driver ???
This is making my head hurt....LOL
CyaN1de said:
Does not give me a choice.
Driver is located at D:\Android\android-sdk\extras\google\usb_driver ???
This is making my head hurt....LOL
Click to expand...
Click to collapse
Yr head hurts????
Ive updated the cpuid guide u my wanna take 5 min timeout to read it, the answers r all in there
I don't use full sdk there's a link to mini sdk zip in that post just has ad and fast boot
I've never had to use google drivers
Just plugged my tab in and its just 'worked'
DL Acer drivers if u haven't already . These are the most important ones to have installed right.
Disconnect and reboot everything
Run Acer setup.exe
Plug USB in
Go into fast boot, win doze will want to install f/b drivers let win doze do it, but if they fail, then run again and choose let me install, blah, blah, blah
What OS u got? Vista/win 7 don't normally have any probs
Acer drivers have been installed and all relevant sdk packages installed and up to date AFAIK. (USB_Acer_1.06.1500_A30HA31H_A.zip)
Had no issues installing ICS Bootloader V.3 manually through APX (no auto script) via instructions so I know I can at least do that well.....LOL
Might have to try reinstalling USB drivers and see if that helps.
Thanks
EDIT: Reinstalled USB Drivers now I can't get adb working....F#@K!!!!!!!!!
EDIT II: Re-Re-Installed Drviers and ADB working again...yay...LOL
EDIT III: Used A500_Manager.exe, clicked on "Enter Fastboot" and windows installed and recognized drivers......DBL YAY!!!!
C:\Users\username>fastboot reboot
rebooting...
finished. total time: 0.165s
Now.......to Brick this puppy.....
Thanx for your help dibb_nz....looks like all I needed in the first place was a driver reinstall...HAHA.
Hek m8 for a second or two there, I was feeling ya pain, lol
Oh but the elation when it finally happens!!!!!
I dunno why those drivers act out like that, but it always the same....
Fail, reinstall, fail, reinstall u can understand why peeps get frustrated
Glad u got it m8
Hi all,
After countless checks on forums and other threads on XDA, I've decided to post this thread as I couldn't find a similar case anywhere.
Situation is I have a TPT from China. Long story short, it was from my company, and when I moved back to Europe I got to keep it.
Anyway, the problem is that it comes with a blocked Lenovo Store, meaning I can't access any of European/US/international apps. Going to Google Play store online doesn't work ("you haven't used any device with this account") - tried from tablet or from computer.
So I thought I would root and install a custom ROM that could enable me to get to the store and personalization/optimization of the device.
I managed to root my TPT thru this thread: http://forum.xda-developers.com/showthread.php?t=1925025
Everything went OK but then I am stuck at the next stage.
If I understand well from this thread http://forum.xda-developers.com/showthread.php?t=1846044, I need to install CWM and then install the custom ROM.
The thread about installing CWM, http://forum.xda-developers.com/showthread.php?t=1831161, just doesn't work, maybe I'm doing something wrong.
If anyone can help it would be very helpful, right now my TPT is just useless...
Thanks all, any help will be very much appreciated.
M0t3l
Here are the specs:
Thinkpad Tablet 32GB
Android version 4.0.3
Kernel: 2.6.39.4-g9b8008b-dirty
Build number: A400_03_0070_0132_SC
Machine Type/model: 183825C
I am on Windows 7 and Mac OSX
Needing a few more details than "just doesn't work"... Are you getting an error message?
Thinkpad Tablet from China
da_reeseboy said:
Needing a few more details than "just doesn't work"... Are you getting an error message?
Click to expand...
Click to collapse
Hi Da Reeseboy, thanks for answering first.
ADB drivers have already been installed on my windows machine in order to root the TPT.
Then at step 3 of the tutorial ("backup your old recovery"), I tried to input the commands into the TPT but nothing happens.
I have installed an application from the chinese lenovo store called SuShell in order to do that (I do speak some chinese). SuShell just tells me "command executed", that's it.
Actually I am not clear if I have an "old recovery" or if it's only for people already with CWM.
So I went on to step 4.
I did copy the file "recovery.img" to an SD card, stick it into the TPT and tried to proceed on the TPT via SuShell again, but when I type in the commands, SuShell tells me "command executed", but nothing happens again.
So I am a little confused if I am doing something the wrong way or typing the commands not thru the right channel or something else.
That's where any help will be very useful.
Thanks again!
Those commands are intended to be run from the computer in a command prompt with admin rights from the directory adb is in (normally the folder you extracted the root files to).
TPT from China
da_reeseboy said:
Those commands are intended to be run from the computer in a command prompt with admin rights from the directory adb is in (normally the folder you extracted the root files to).
Click to expand...
Click to collapse
Thanks da_reeseboy, that made it!
I had a few gliches on the way but nothing major that I couldn't overcome.
I did follow the steps on the tutorials and now CM seems to be working fine on the tablet. It seems that a couple of functions on the TPT are either crashing or not working correctly, will try to look into it, but mainly I am now able to access the Play Store and said goodbye to the Chinese Lenovo Store.
Cheers again!
M0t3l
Right I have UK Nexus 4, running 4.2.2, Developer Mode is enabled, but USB Debugging is not, it is not rooted.
How can I enable USB Debugging mode, without wiping everything on the phone as I need to use a program called MoboRobo before I wipe the phone (I need to backup messages, bookmarks and contacts)
I can't see anything on the screen at all, so if you are able to help and tell me I need to boot into Recovery mode, then pick an option I need to know how many times to press up or down, this is purely as I can't see a single thing on the screen at all.
I've been trying to follow this: http://forum.xda-developers.com/showthread.php?t=2177440
But I've no idea if that's correct for what I need to do (purely enable USB Debugging mode without wiping what's already on the phone)
Sorry if this has been covered, I've tried to search but the only thing that came close was a Nexus 7 where the user could still see the whole screen.
Ok first, let me ask a few questions.
1. Is your bootloader unlocked?
2. Do you have a custom recovery installed? If so, which one?
3. Will you have access to a working Nexus 4 in the near future? A replacement, a friend's, a family member's, a repaired version of your current phone, etc?
Johmama said:
Ok first, let me ask a few questions.
1. Is your bootloader unlocked?
2. Do you have a custom recovery installed? If so, which one?
3. Will you have access to a working Nexus 4 in the near future? A replacement, a friend's, a family member's, a repaired version of your current phone, etc?
Click to expand...
Click to collapse
1] No
2] No
3] No
JuicedToday said:
1] No
2] No
3] No
Click to expand...
Click to collapse
Hmm, that's a tough one then. Do you have adb set up on your computer? If not, follow the instructions posted here.
Setting up ADB for our device:
Download the AndroidSDK onto your computer.
Note: Google changes their mind every other week as to if this will be distributed as a .zip or an .exe. If you get an .zip file, simply extract the contents to your C:\ drive. For an .exe install it like you would any other program, but set the path directly to the C:\ drive when the installer asks.
Or...you can use this page to download the "ADB for Dummies AIO App."
This will automatically install ADB for you to your C:\ directory. It's very very simple this way.
If your platform-tools folder doesn't have a fastboot.exe, place this fastboot.exe file in your C:\android-sdk-windows\platform-tools (or possibly simply called tools, if you set up ADB ages ago) folder.
Now you have ADB installed! Congratulations.
Click to expand...
Click to collapse
Now I would boot into bootloader (Turn off device, then press volume down and power at the same time until it vibrates). Now, press volume down twice, then power button. It should vibrate. That'll boot your phone into recovery. Now set up the drivers:
Get the drivers:
Uninstall any previously attempted drivers if they don't work and move to the next.
Option One:
Navigate to the "Device Manager" (Control Panel > Device Manager) in Windows and Select the android device. Open the properties and select the "Install Driver" option. Pick the driver with "Install from disk." Ignore any warnings about the driver not being signed properly.
PDAnet's drivers may work if the above options don't. Simply install PDAnet (after uninstalling any previous attempted driver installations) to get the drivers.
Click to expand...
Click to collapse
To verify your computer is seeing your phone and that you're in recovery, open a cmd window in the location of your platform-tools folder under the Android SDK location (fastest way is to shift+right-click a blank area in the folder in Windows Explorer, Open command window here). then type "adb devices", and it should pop up with a device number followed by "recovery". If you've gotten this far, there is still hope.
Now what you're going to do is use the "adb pull" command to pull the files from your phone onto your computer. I'll try to see if I can figure out the locations of the files you need. One question: What browser are you using (not yet sure if it makes a difference, but in case I find out it does)
By the way, after typing all of that I realized that if you're signed into your Google account, your contacts should be synced with your account in the cloud, you should be able to pull them down on a new phone if you sign back into your account on that new phone. Same with your bookmarks if you're using Chrome or the default AOSP browser. In any case, it won't sync SMS so I'll still try to find out where they're located.
Johmama said:
Hmm, that's a tough one then. Do you have adb set up on your computer? If not, follow the instructions posted here.
Now I would boot into bootloader (Turn off device, then press volume down and power at the same time until it vibrates). Now, press volume down twice, then power button. It should vibrate. That'll boot your phone into recovery. Now set up the drivers:
To verify your computer is seeing your phone and that you're in recovery, open a cmd window in the location of your platform-tools folder under the Android SDK location (fastest way is to shift+right-click a blank area in the folder in Windows Explorer, Open command window here). then type "adb devices", and it should pop up with a device number followed by "recovery". If you've gotten this far, there is still hope.
Now what you're going to do is use the "adb pull" command to pull the files from your phone onto your computer. I'll try to see if I can figure out the locations of the files you need. One question: What browser are you using (not yet sure if it makes a difference, but in case I find out it does)
By the way, after typing all of that I realized that if you're signed into your Google account, your contacts should be synced with your account in the cloud, you should be able to pull them down on a new phone if you sign back into your account on that new phone. Same with your bookmarks if you're using Chrome or the default AOSP browser. In any case, it won't sync SMS so I'll still try to find out where they're located.
Click to expand...
Click to collapse
Appreciate your efforts. I did as you instructed, and once I'd got to the "adb devices" I get nothing showing. As the picture shows.
{
"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"
}
I use firefox and chrome, and googlemail, but I've set them to not sync for personal reasons. All my contacts were saved directly to the phone. Messages I'm not too fussed about, but it would be nice to be able to view them, possibly back them up.
I've apparently unlocked the bootloader via the Nexus 4 Toolkit. I've no idea if that's worked or not though as I can't see the screen and I don't know how to test.
JuicedToday said:
Appreciate your efforts. I did as you instructed, and once I'd got to the "adb devices" I get nothing showing. As the picture shows.
I use firefox and chrome, and googlemail, but I've set them to not sync for personal reasons. All my contacts were saved directly to the phone. Messages I'm not too fussed about, but it would be nice to be able to view them, possibly back them up.
I've apparently unlocked the bootloader via the Nexus 4 Toolkit. I've no idea if that's worked or not though as I can't see the screen and I don't know how to test.
Click to expand...
Click to collapse
Ok, let's try eliminating possible reasons for your phone not showing up. Try re-entering recovery mode with the steps I provided above, in case it didn't work. I know this will sound stupid, but it's worked for me in the past: try switching which port on your computer that your USB cable is plugged in to. Try a different cable altogether if you have a spare. Oh, make sure you're using a USB 2.0 cable/plug. Sometimes MTP doesn't play nicely and you need to do weird things to get it working.
I've gathered a few database file locations that you might be interested in. I *think* they are correct anyway. I pulled them onto my computer but I can't try to view them right now, it'd have to be this weekend when I could get around to it, as I'm moving and I'd need to get settled first (Internet up and whatnot). I can still help you troubleshoot adb though.
SMS:
/data/data/com.android.providers.telephony/databases/mmssms.db
Click to expand...
Click to collapse
Contacts
/data/data/com.android.providers.contacts/databases/contacts2.db
Click to expand...
Click to collapse
Browser (I'm not exactly sure which browser)
/data/data/com.android.browser/databases/browser.db
Click to expand...
Click to collapse
Once adb is up and running, you'd use these commands to pull the .db file onto your computer:
Code:
adb pull /data/data/com.android.providers.telephony/databases/mmssms.db
Code:
adb pull /data/data/com.android.providers.contacts/databases/contacts2.db
Code:
adb pull /data/data/com.android.browser/databases/browser.db
Those would pull the .db files onto your computer inside of the platform-tools folder. Again, I'm not sure about this, and can't confirm till later in the weekend, but I think to view those on your computer you can download SQLite from here. More importantly, I assume you can just put those .db files into the proper folders on your new phone to restore them. You'd have to figure out the correct folder location depending on your new device, as the manufacturer or carrier sometimes switches them.
Still getting nothing showing under adb devices even after trying several USB ports with a couple of various data cables.
Think it's a lost cause! Guess I'll just have to plump for the screen when I can afford it. Or swap the screen over on my insurance replacement enable USB Debugging then swap the screen back.
Other option would be to sell my replacement, buy the screen and still have a few quid left over.. Choices choices!
Thanks for taking the time and effort though, appreciate it.
Just thought I'd give this one last try. The data at this point isn't of any concern. I need to wipe everything that is on the phone, if that means the OS as well, then that's fine.
Is there a way I can remove my apps, data, messages etc via USB cable without USB Debugging being enabled?
Thank you for your time.:good:
cracked scereen, tried command, debugging alreadfy enabled. says devivce offline. is that because i have no SIM in it>?
Johmama said:
Ok first, let me ask a few questions.
1. Is your bootloader unlocked?
2. Do you have a custom recovery installed? If so, which one?
3. Will you have access to a working Nexus 4 in the near future? A replacement, a friend's, a family member's, a repaired version of your current phone, etc?
Click to expand...
Click to collapse
I have this same issue. Rooted with TWRP, which does NOT allow you to toggle through the recovery menu with the volume buttons.
After hours googling, I STILL have not found a way to wipe everything from my phone. I tried using the Android Device Manager to erase everything, but that didn't work.
Please, any help on what to do is so much appreciated. Thanks.
ji_mestone said:
I have this same issue. Rooted with TWRP, which does NOT allow you to toggle through the recovery menu with the volume buttons.
After hours googling, I STILL have not found a way to wipe everything from my phone. I tried using the Android Device Manager to erase everything, but that didn't work.
Please, any help on what to do is so much appreciated. Thanks.
Click to expand...
Click to collapse
Looks like you're hijacking this thread, but just because I'm currently fighting a similar situation...
you can download the recovery image for CWM at http://download2.clockworkmod.com/recoveries/recovery-clockwork-6.0.4.3-mako.img
and then reboot to bootloader, run "fastboot flash recovery cwm.img" (using the file you just downloaded, i usually just drag and drop onto cmd line)
That will get you the recovery installed that will be useful because you don't have to touch the screen.
After that, It's as simple as selecting wipe all. if you can't see the screen, then you'll have to do these steps (after installing CWM):
hold Vol- and Power until it turns off, then keep holding Vol- and push power again.
down, down, power - boots into recovery
down, down, power - gets you to wipe/factory reset page
down x 7, power - confirms wiping all data
First i want to say Speacial Thanks to @xyz`, @k4y0z, @diplomatic and @ggow who make it possible to get a costum rom on a fire 7(9th gen)!
But i needed informations from more sites to get it work and i want to collect all informations in this Thread to make it easier for noobs like me I hope thats okay, i only collect informations, credits goes to:
@k4y0z and @xyz` for the bootloader hack
@diplomatic for the temp root
@ggow for the lineageos for mustang
So i will show the hole way From Stock FireOs 6.3.1.2 until you boot LineageOs 14.1
In this Guide i will use the Software method to get into bootrom mode. Software method: use mtk-su to do the thing.
Careful: this will break your device… and then you fix it by installing a new OS.
Any OS above 6.3.1.2 needs to use the hardware method!
Here you can find the hardware method: https://forum.xda-developers.com/am...ire-7-2019-mustang-unbrick-downgrade-t3944365
I flash some devices but that was the most difficult. It will help if you have some experience how to flash devices.
NOTICE :
Before you move further, make clear that rooting device -
Your warranty will be void
Some of functions may not work on rooted device, some function may get back with un rooting, some may never.
All your data on device will be lost
Flashing custom binaries may brick (Usually soft but can be hard brick too) your device, so follow it on your own risk!
If you are ready with condition, move further -
Click to expand...
Click to collapse
Make sure you read this guide completely before starting!
This Hardware you need:
Working Amazon Fire 7 2019 9th gen (tested with FireOs 6.3.1.2)
USB cable for Kindle Fire
empty USB drive (min. 2Gb)
computer that can boot from USB drive
Download This Software:
lubuntu-19.10-desktop-amd64.iso # get it here https://lubuntu.net and download the AMD64 version
rufus-3.9.exe # get it here https://rufus.ie
mtk-su_r21.zip # get it here https://forum.xda-developers.com/attachment.php?attachmentid=4971443
amonet-mustang.zip # get it here https://forum.xda-developers.com/attachment.php?attachmentid=4785431&d=1561925516
lineage-14.1-20190827-UNOFFICIAL-mustang.zip # get it here https://androidfilehost.com/?w=files&flid=297948
open_gapps-arm-7.1-mini-20200403.zip # go to https://opengapps.org and choose AMR -> 7.1 -> and a variant of your choice i use mini
Step 1 Prepare Usb Stick
################################
Okay first we make the usb stick ready with Lubuntu.
1.1 Start the rufus-3.9.exe
1.2 choose the Lubuntu image file and push start
1.3 it will ask ISO image mode or DD image mode, choose the DD image mode!
1.4 after that put these files to C:\ :
mtk-su_r21.zip
amonet-mustang.zip
lineage-14.1-20190827-UNOFFICIAL-mustang.zip
open_gapps-arm-7.1-mini-20200403.zip
1.5 Turn off your Computer!
Step 2 Boot Live Linux
################################
2.1 Turn on your Computer and boot from usb and start lubuntu
(2.1.1 If you use wlan connect with it)
2.2 Open a terminal window # (go to "start button" at the left corner choose -> system tools -> QTerminal)
2.3 type "sudo apt install python3 python3-serial android-tools-adb android-tools-fastboot" push enter
2.3.1 it ask you something, say yes
2.4 type "sudo apt-get remove modemmanager" push enter
2.4.1 it ask you something, say yes, if it done close this window
2.5 Click on the "Computer" icon on Desktop
2.6 Search your Windows device and copy the 4 files from step 1.4 to lubuntu home directory (make it easier later)
Step 3 Prepare kindle
################################
3.1 Go to settings and enable developer options (need to push the serialnummber multiple times)
3.2 Go to developer options Enable USB debugging
3.3 Connect kindle to computer
3.3.1 On the kindle,
3.3.2 pull down the menu,
3.3.3 click the USB charging, “tap for other USB options” and select PTP for “transfer photos”
3.3.4 Click Accept to allow permission for your computer.
Step 4 Temporary root (Terminal window1)
################################
4.1 Open the mtk-su_r21.zip
4.2 copy the arm folder to lubuntu home directory
4.3 Open a new terminal window
4.4 type "sudo adb push arm/mtk-su /data/local/tmp” push enter
once successful, run these commands:
4.5 type "adb shell" push enter
4.6 type "cd /data/local/tmp" push enter
4.7 type "./mtk-su" push enter
4.8 type "getenforce" push enter # Just to confirm it says Permissive
4.9 type "echo 0 > /sys/block/mmcblk0boot0/force_ro" push enter
4.10 type "dd if=/dev/zero of=/dev/block/mmcblk0boot0 bs=512 count=8" push enter
Dont close this window!. you will need it in a moment.
Step 5 Bootrom Mode (Terminal window2)
################################
5.1 Open the amonet-mustang.zip
5.2 copy the amonet-mustang folder to lubuntu home directory
5.3 Open a new terminal window
5.4 type "cd amonet-mustang/" push enter
5.5 type "sudo ./bootrom-step.sh" push enter
5.6 Go back to the first Terminal window and type "reboot" push enter
5.7 Go back to the second Terminal, the tablet should restart, and the amonet script will begin to run.
Press Enter to continue, it will start copying things. Should take about 4 minutes.
Once the script finished, the kindle will restart into fastboot mode.
5.8 All you will see if the amazon logo. to verify that the device is in fastboot mode go back to the first Terminal window
and type "sudo fastboot devices" push enter
it will list the device # if it find 1 device you make all right
Step 6 Fastboot & TWRP
################################
6.1 Go back to the second Terminal window
6.2 type "sudo ./fastboot_step.sh"
The tablet will flash some text and do a few things. give it a minute or two.
The tablet will flash and appear to restart, let it do its thing until the screen goes dark.
6.3 Tap the power button twice and TWRP will pop up.
SUCCESS! # TWRP (Team Win Recovery Project) is now installed and can be launched by holding down VOL Down (left most button from pwr) and Power when starting up the device.
(At this point you can try to put the files on a SD Card, but i try it with multiple ones and TWRP dont find one, if you have one that work you can jump to step 8.4)
Edit: or use adblink from here https://forum.xda-developers.com/fire-tv/themes-apps/adblink-v2-04-t3389826
Step 7 Set permissions to Copy
################################
7.1 In TWRP on you kindle push wipe -> push Format Data and Swipe to reset
7.2 Now we need to obtain the idVendor of the kindle.
Go to the first Terminal window and type "sudo dmesg" push enter look for idVendor"XXXX", for me, the ID was "18d1".
7.3 Next, you need to give the ”plugdev” group access to the device.
You are going to create a file and then change some permissions then restart the services.
7.4 type "sudo nano /etc/udev/rules.d/51-android.rules" # create the file
7.5 and type the following line: #(Change idVendor to your ID)
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", MODE="0666", GROUP="plugdev"
7.6 push ctrl + x , and hit y to save. # push a button and it close but hold the terminal open
7.7 Now assign read permissions on the files, reload udev and reload the adb daemon:
7.7.1 type "sudo chmod a+r /etc/udev/rules.d/51-android.rules" push enter
7.7.2 type "sudo udevadm control --reload-rules" push enter
7.7.3 type "adb kill-server" push enter
7.7.4 type "adb start-server" push enter
(You may have to disconnect and connect again your device to the USB port) # i dont needed it
Step 8 Copy & Install LineageOs
################################
NOW you can copy the files using the adb push command, like we did before.
8.1 type "sudo adb push /lineage-14.1-20190827-UNOFFICIAL-mustang.zip /data/local/tmp/lineage.zip" push enter
8.2 type "sudo adb push /open_gapps-arm-7.1-mini-20200403.zip /data/local/tmp/gapps.zip" push enter
After it finish copying, use TWRP to install the image
8.3 In TWRP push install go to path /data/local/tmp/ # there you find lineage.zip & gapps.zip
8.4 Choose lineage.zip and swipe to install
8.5 After that go back and choose gapps.zip and swipe to install
8.6 if its done you can push "Reboot System"
You are Finaly Done LineageOs 14.1 will booting now! # it will take some time at the first boot
Edit:
Install the "sod-fix-test.zip" by using TWRP you can find it here https://forum.xda-developers.com/showpost.php?p=80621157&postcount=253 @Ziona
(This fix the charge issue)
i find so much usefull things at xda-developers to flashing much devices include this device
So for this device it was really difficult and i was think it will be great thanks when i collect all informations for other(and me for the next time ).
And i think, thats understandable for anyone. I Hope it will help other People too.
Sources:
Unlock & root By xyz` https://forum.xda-developers.com/am...ire-7-2019-mustang-unbrick-downgrade-t3944365
Amazing Temp Root By diplomatic https://forum.xda-developers.com/android/development/amazing-temp-root-mediatek-armv8-t3922213
LineageOS 14.1 By ggow https://forum.xda-developers.com/amazon-fire/orig-development/rom-lineage-14-1-t3957329
Thanks for the guide, do you know if this also applies to Fire OS 6.3.1.5 ? as I have a fire 7 mustang version
At first start i connet the fire 7 with wifi and it makes a small update to 6.3.1.4 then i make a factory reset with stock recovery and i was back to 6.3.1.2
Try the factory reset if that dont work and you are still on 6.3.1.5, dont try this Guide i only test it with a 6.3.1.2 device!
It's all good, followed your guide and I'm on lineage os now. Thanks again!
So just to understand, Cozzysa: you sis it with 6.3.1.5 ?
Hi, I try here, and I stooped in the step 4.6, the result is: No such file or directory.
What's wrong?
edit: I founded the error, in the step, please correct the folder temp to tmp.
lucas.lop said:
Hi, I try here, and I stooped in the step 4.6, the result is: No such file or directory.
What's wrong?
edit: I founded the error, in the step, please correct the folder temp to tmp.
Click to expand...
Click to collapse
Thanks! i edit it! if you find some other things tell me
nimrodk3 said:
So just to understand, Cozzysa: you sis it with 6.3.1.5 ?
Click to expand...
Click to collapse
Thats a good question
_SWaTcH_ said:
Thanks! i edit it! if you find some other things tell me
Thats a good question
Click to expand...
Click to collapse
I try here with 6.3.1.5 and don't work. I'm with this problem too.
lucas.lop said:
I try here with 6.3.1.5 and don't work. I'm with this problem too.
Click to expand...
Click to collapse
This guide will only work if you are on 6.3.1.2 or below.
MTK-su = Amazon Fire 7 2019 -- up to Fire OS 6.3.1.2 build 0002517050244 only
---------- Post added at 01:19 PM ---------- Previous post was at 01:10 PM ----------
---------- Post added at 01:22 PM ---------- Previous post was at 01:19 PM ----------
@_SWaTcH_
You might want to give credit to "diplomatic" for his temp root and you should possibly change to links to their threads.
For example 14.1 has this right next to the link to download. "*** Please do NOT create any mirrors ***"
I would also recommend a note that any OS above 6.3.1.2 needs to have the hardware unlock and link them over to the over thread.
Very nice instructions though!
Is no way out for 6.3.1.5?
lucas.lop said:
Is no way out for 6.3.1.5?
Click to expand...
Click to collapse
Go here for the hardware unlock method-
https://forum.xda-developers.com/am...ire-7-2019-mustang-unbrick-downgrade-t3944365
Once you get into TWRP, you can install Lineage. You can put the lineage on your sdcard, or transfer to your download folder from a PC. You odnt have to use adb to push files. an easy way of transfering files is to use adblink from here...
https://forum.xda-developers.com/fire-tv/themes-apps/adblink-v2-04-t3389826
Or when plugged in set it to file transfer and it would come up as a removable media on a computer.
follow the instructions from the 14.1 thread for install.
Michajin said:
@_SWaTcH_
You might want to give credit to "diplomatic" for his temp root and you should possibly change to links to their threads.
For example 14.1 has this right next to the link to download. "*** Please do NOT create any mirrors ***"
I would also recommend a note that any OS above 6.3.1.2 needs to have the hardware unlock and link them over to the over thread.
Very nice instructions though!
Click to expand...
Click to collapse
Im sorry that i miss the credit for diplomatic :silly:
I add note that you need to use the hardware method for Os version above 6.3.1.2 and add links to their threads.
Device offline MTP Error
I follow everything flawlessly until step 7. None of my SD cards are recognized. So I follow the steps posted in Step 7. In my device list I see "omni mustang" then it says I cant access this drive. I do step 7 then go to push lineage onto the system it says device offline.
I have rebooted the tablet many times Disable MTP and Enabled MTP countless times.
Sorry this is all jumbled up. Hopefully you understand what I am trying to say.
{
"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"
}
nimrodk3 said:
So just to understand, Cozzysa: you sis it with 6.3.1.5 ?
Click to expand...
Click to collapse
Yeah it worked perfectly with the hardware hack
Ozed20 said:
I follow everything flawlessly until step 7. None of my SD cards are recognized. So I follow the steps posted in Step 7. In my device list I see "omni mustang" then it says I cant access this drive. I do step 7 then go to push lineage onto the system it says device offline.
I have rebooted the tablet many times Disable MTP and Enabled MTP countless times.
Sorry this is all jumbled up. Hopefully you understand what I am trying to say.
Click to expand...
Click to collapse
So i think you have install TWRP and you only need to copy the files to your fire 7, Michajin post a other way:
Michajin said:
Once you get into TWRP, you can install Lineage. You can put the lineage on your sdcard, or transfer to your download folder from a PC. You odnt have to use adb to push files. an easy way of transfering files is to use adblink from here...
https://forum.xda-developers.com/fire-tv/themes-apps/adblink-v2-04-t3389826
Or when plugged in set it to file transfer and it would come up as a removable media on a computer.
follow the instructions from the 14.1 thread for install.
Click to expand...
Click to collapse
Worked then broke
Not sure what happened. Got everything installed booted into lineage 14.1 downloaded apps browsed the web etc. I went into the list of apps and turned off auto start on things I wasn't planning to use the tablet for. Mail, messages, etc to save on memory usage these devices don't seem to come with much to spare. Then held the power button, clicked restart and it never came back, doesn't respond on the power button. Not sure where I need to go from here.
Additional Info: I had to use the hardware method since reset to factory took me back to 6.3.1.5
DrGuns4Hands said:
Not sure what happened. Got everything installed booted into lineage 14.1 downloaded apps browsed the web etc. I went into the list of apps and turned off auto start on things I wasn't planning to use the tablet for. Mail, messages, etc to save a memory usage. Then held the power button, clicked restart and it never came back, doesn't respond on the power button. Not sure where I need to go from here.
Click to expand...
Click to collapse
Hold the power button for about 10 seconds to do a power off...
It is a known issue with 14.1 Lineage rom for this. Did you install the sod patch? Check out the 14.1 thread here.... Post #566
https://forum.xda-developers.com/amazon-fire/orig-development/rom-lineage-14-1-t3957329/page57
Michajin said:
Hold the power button for about 10 seconds to do a power off...
It is a known issue with 14.1 Lineage rom for this. Did you install the sod patch? Check out the 14.1 thread here.... Post #566
https://forum.xda-developers.com/amazon-fire/orig-development/rom-lineage-14-1-t3957329/page57
Click to expand...
Click to collapse
Not sure what sod means. I did hold down the power button for quite a while and the tablet wouldn't turn on, but I can't say for certain it was 10 seconds I'll have to try again when I get home. Perhaps this patch should be in the installation instructions here if this is a known issue?
DrGuns4Hands said:
Not sure what sod means. I did hold down the power button for quite a while and the tablet wouldn't turn on, but I can't say for certain it was 10 seconds I'll have to try again when I get home. Perhaps this patch should be in the installation instructions here if this is a known issue?
Click to expand...
Click to collapse
Screen Of Death. You might have to pull the battery. The Developer who created the Rom has been unavailable, being custom roms expect bugs. Always good to look at the last few pages of any thread to know status and current issues. When the GGOW returns he will likely update the latest security patches and install the patches into the latest. Remember these are volunteers who have no obligation to do this. Some don't even accept donations.
Michajin said:
Screen Of Death. You might have to pull the battery. The Developer who created the Rom has been unavailable, being custom roms expect bugs. Always good to look at the last few pages of any thread to know status and current issues. When the GGOW returns he will likely update the latest security patches and install the patches into the latest. Remember these are volunteers who have no obligation to do this. Some don't even accept donations.
Click to expand...
Click to collapse
Thanks. This is my first time with a custom ROM. I got the tablet just to do chromecast control for my TV in the living room and realized quickly that Fire OS just felt to clunky to keep on the device. Guess I'll be learning how to do update patches since I think that lineage will still be the better solution overall. Any suggestion on where to look to understand how to do the updates? I followed this guide as a step by step assuming it would be the whole kit and kaboodle, so can't really say I understand what pieces I'd need to update or where to look to keep things up to date to the most stable version.