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
Hi! All. I have a Acer Iconia A500 wifi 32gb. Rooted with "Iconia Root". Installed custom rom. Wish to return to official stock rom & receive OTA. Unfortunately, when i root my tab, i accidentally deleted my stock rom image. i can't remember my build therefore am having difficulty finding the correct rom to revert. My set is from Singapore & therefore need a rom thats meant for Singapore. I managed to find some information about a fellow user of the iconia tab from Singapore. His Build number & android version is as follows:
Android Version : 3.0.1
Build Number : Acer_A500_1.016.04_COM.GEN1
My kernel version is 2.6.36.3.
Hope someone can direct me to the correct stock rom to install & enable OTA again.
wolvie77 said:
Hi! All. I have a Acer Iconia A500 wifi 32gb. Rooted with "Iconia Root". Installed custom rom. Wish to return to official stock rom & receive OTA. Unfortunately, when i root my tab, i accidentally deleted my stock rom image. i can't remember my build therefore am having difficulty finding the correct rom to revert. My set is from Singapore & therefore need a rom thats meant for Singapore. I managed to find some information about a fellow user of the iconia tab from Singapore. His Build number & android version is as follows:
Android Version : 3.0.1
Build Number : Acer_A500_1.016.04_COM.GEN1
My kernel version is 2.6.36.3.
Hope someone can direct me to the correct stock rom to install & enable OTA again.
Click to expand...
Click to collapse
Ok, now you are in the correct forum.
Now, next time, you want to go installing things, that you really shouldn't, take some safe measures before you make a mess of things.
Rule #1. Always have CWM or RA installed, and make a damn backup of your current system.
IF you were rooted, and had CWM or RA recovery installed, you will find your original CUID number in your Ext SD cards, clockwork or recovery folder.
Somehow, I think you didn't do this.
Ok, you will need this ;
http://forum.xda-developers.com/showthread.php?t=1516012
Read the thread, all the posts. Then run the tool EXACTLY like he says. Remember to remove the 0x from your UID number, and plug your tab in only at the point he says.
Remember, you have to get your current UID number by running a terminal app from your tab. Then copy the txt to your pc and open it.
After you get the unstable rom running, you should be able to install some stable Com Gen 1 roms from;
http://forum.xda-developers.com/showthread.php?t=1113878
Remember to de-crypt the update.zip from the encrypted roms, and copy it to your Tab's Ext SD card.
Then with tab off. Hold both PWR and Vol+ and it should install.
Of course, this is theory, as in well over 200 rom installs, I have never got into the mess You, have gotten yourself into.
Mr. Moscow,
do you know what causes the mess for some folks that no UID is in the dmesg-output?
My dmesg.txt just has no line containing "androidboot.serialno".
All the other ways to get the UID are resulting in a 11 digit UID, which is not valid for either nvflash or Acer's EUU tool?
I was also so bright to delete my older Honeycomb based backups, so i am stuck gettting the original UID of my tablet.
Am I now bound to the "Acer_AV041_A500_0.009.00_WW_GEN1" forever just because i have no valid UID anymore?
I am applying custom roms, kernels, radios and bootloaders since the good old days of the G1, but this time i somehow was too impatient obviously
Pittek said:
Mr. Moscow,
do you know what causes the mess for some folks that no UID is in the dmesg-output?
My dmesg.txt just has no line containing "androidboot.serialno".
All the other ways to get the UID are resulting in a 11 digit UID, which is not valid for either nvflash or Acer's EUU tool?
I was also so bright to delete my older Honeycomb based backups, so i am stuck gettting the original UID of my tablet.
Am I now bound to the "Acer_AV041_A500_0.009.00_WW_GEN1" forever just because i have no valid UID anymore?
I am applying custom roms, kernels, radios and bootloaders since the good old days of the G1, but this time i somehow was too impatient obviously
Click to expand...
Click to collapse
What tab are you running? 500 or 501?
Were you using adb? (to get the dmesg)
Moscow Desire said:
What tab are you running? 500 or 501?
Were you using adb? (to get the dmesg)
Click to expand...
Click to collapse
Thx for the quickreply!
Running an A500 here, getting the dmesg via terminal emulator from running system.
Pittek said:
Thx for the quickreply!
Running an A500 here, getting the dmesg via terminal emulator from running system.
Click to expand...
Click to collapse
Try with adb
I already tried "adb devices" as well as getting the UID via "details - parents" of my USB PC connectIon.
This leads to an invalid 11-digit UID...
Pittek said:
I already tried "adb devices" as well as getting the UID via "details - parents" of my USB PC connectIon.
This leads to an invalid 11-digit UID...
Click to expand...
Click to collapse
Did you remove the "0x" when entering ?
Moscow Desire said:
Did you remove the "0x" when entering ?
Click to expand...
Click to collapse
Yeah i did, problem was the invalid UID.
I finally managed to get a valid 16 digit UID this way:
Here is how i finally was able to get a valid 16 digit UID:
Install the "half root" for the leak like posted on Tegra Owners -> http://forum.tegraowners.com/viewtopic.php?f=30&t=350
Now run any terminal emulator and run dmesg to get the UID (dmesg>/mnt/external_sd/bla.txt
After rooting, the resulting text finally gave me a line containing "androidboot.serialno=" which has the expected 16 digits.
Before rooting it, i had no such line in dmesg.txt, and all other methods just returned the invalid 11 digit UID.
I think i am able now to downgrade to Stock, root and install a custom recovery again (will check later when back home from work)
Yeah, I have a 501, and fortunately it wasn't effected by the 500 leaked ICS.
Suppose that specific kernel just ignore my tab, and installs with 0 issues.
I tell you who to contact about your issue, and it's ATGadmin. You can pm him here, or at our site http://www.androidtabletgeeks.com
There he is KJY2010. Post in his ICS Tutorial thread. He's in NY and probably sleeping right now. But he knows a lot about getting a 500 ICS back to HC. I should know, I spent several hours with his "locked" tab on the sites live chat!
Moscow Desire said:
Yeah, I have a 501, and fortunately it wasn't effected by the 500 leaked ICS.
Suppose that specific kernel just ignore my tab, and installs with 0 issues.
I tell you who to contact about your issue, and it's ATGadmin. You can pm him here, or at our site http://www.androidtabletgeeks.com
There he is KJY2010. Post in his ICS Tutorial thread. He's in NY and probably sleeping right now. But he knows a lot about getting a 500 ICS back to HC. I should know, I spent several hours with his "locked" tab on the sites live chat!
Click to expand...
Click to collapse
Thanks again
Fortunately i solved the issue in the meantime (see my post above), I am now back on good ole rooted 3.01 with custom recovery. Free to update again.
This time my UID is saved secure, just in case i have a "bad day" again
Pittek said:
Thanks again
Fortunately i solved the issue in the meantime (see my post above), I am now back on good ole rooted 3.01 with custom recovery. Free to update again.
This time my UID is saved secure, just in case i have a "bad day" again
Click to expand...
Click to collapse
Great!!!!!
Yeah, one has to avoid those bad days
I'm just waiting for word when people start getting the ICS updates for the 501. Then I'll go back to stock, grab the updates (without booting), pull the updates via adb, then assemble a rooted ICS for the 501.
At least in theory anyhow
Moscow Desire said:
Ok, now you are in the correct forum.
Now, next time, you want to go installing things, that you really shouldn't, take some safe measures before you make a mess of things.
Rule #1. Always have CWM or RA installed, and make a damn backup of your current system.
IF you were rooted, and had CWM or RA recovery installed, you will find your original CUID number in your Ext SD cards, clockwork or recovery folder.
Somehow, I think you didn't do this.
Ok, you will need this ;
http://forum.xda-developers.com/showthread.php?t=1516012
Read the thread, all the posts. Then run the tool EXACTLY like he says. Remember to remove the 0x from your UID number, and plug your tab in only at the point he says.
Remember, you have to get your current UID number by running a terminal app from your tab. Then copy the txt to your pc and open it.
After you get the unstable rom running, you should be able to install some stable Com Gen 1 roms from;
http://forum.xda-developers.com/showthread.php?t=1113878
Remember to de-crypt the update.zip from the encrypted roms, and copy it to your Tab's Ext SD card.
Then with tab off. Hold both PWR and Vol+ and it should install.
Of course, this is theory, as in well over 200 rom installs, I have never got into the mess You, have gotten yourself into.
Click to expand...
Click to collapse
Hi! I've checked on my tab. I actually already have Acer Recovery Installer with ClockworkMod Recovery rev1.3.4 by thor2002ro & Stock USA 1.141.07_COM_GEN1 recovery. Is it possible to find my CUID from there? i can't find it on my SDcard. my internal memory has alot of folders but can't find any thats says clockwork or recovery.
wolvie77 said:
Hi! I've checked on my tab. I actually already have Acer Recovery Installer with ClockworkMod Recovery rev1.3.4 by thor2002ro & Stock USA 1.141.07_COM_GEN1 recovery. Is it possible to find my CUID from there? i can't find it on my SDcard. my internal memory has alot of folders but can't find any thats says clockwork or recovery.
Click to expand...
Click to collapse
Get your UID:
a) install any terminal emulator from market, open it and type "dmesg>/mnt/external_sd/bla.txt" (w/o the quotes)
Open the resulting textfile in an editor on your PC and seach for "androidboot.serialno", this number is your UID
or
b) connect your tab to pc and find it via ADB -> adb devices
or
c) connect to your PC, check device manager for your Iconia, rightclick, choose properties -> details and look for "parent" in the dropdown field -> the last 16 digits is your UID
Pittek said:
Get your UID:
a) install any terminal emulator from market, open it and type "dmesg>/mnt/external_sd/bla.txt" (w/o the quotes)
Open the resulting textfile in an editor on your PC and seach for "androidboot.serialno", this number is your UID
or
b) connect your tab to pc and find it via ADB -> adb devices
or
c) connect to your PC, check device manager for your Iconia, rightclick, choose properties -> details and look for "parent" in the dropdown field -> the last 16 digits is your UID
Click to expand...
Click to collapse
i used method 'c' & this is what i see. can u advice which is the UID?
USB\VID_8087&PID_0020\5&875cd47&0&1
wolvie77 said:
i used method 'c' & this is what i see. can u advice which is the UID?
USB\VID_8087&PID_0020\5&875cd47&0&1
Click to expand...
Click to collapse
Evereything after the last "\"...
This cannot be the correct one, it should only contain numbers as far as i know, also the VID and PID should be different for the Iconia, like:
USB\VID_0502&PID_3325\xxxxxxxxxxxxxxxx
Also, it should be 16 digits.
Make sure your system is up and running, USB debugging is enabled and you have installed the Acer USB drivers before.
Then plug into your PC and you should have something like "ACER Composite ADB Interface" in your device manager.
Rightclick on this and chosse "Properties" and goto the "Details" tab. In the dropdownbox there choose "Parent" (something like that, i have a german OS).
I recommend method a) anyway, its fast and simple.
Cheers
My husbands Acer a500 screen froze when he was playing Zimga a poker game when this happened.
He believes he had ICS but he is not sure of anything speciffic.
He doesn't have any type of backup.
He never had it connected to the computer.
We tried the factory reset.
We tried the hard reset.
We cleaned the cache & whatnot...
Nothing helps.
I've tried to use the GUIDE: Recovering Recovery/Obtaining SKB
Of course we only option we have, because nothing was ever back up, connected to a computer. I downloaded unbumtu 12.04 and installed it onto my laptop.
The requirements:
-ubuntu 12.04
-micro USB cable
-paper clip ....
I also made sure I installed gcc, lsusb, libusb-1.0-dev, & libusb-1.0.x
I get it to show on the desktop ...
I type in: sudo su
Then: gcc apx.c -o apx -lusb-1.0
I end up with an errors.
If I remember correctly it says that line 4 and line 5 of EPPE code was in errors.
The another time it states...
Then it stats su: invalid option -- 'o'
I am by all no means a computer code writer, and hope someone will help me solve this issue.
I just can't afford sending the tablet back to Acer to be fixed.
I even tried flashing the information on the micro SD card, but I believe since his tablet wasn't connected ever to a computer things aren't running as smoothly as I would like.
I've downloaded nvFlash, blackthud3r, and many Roms.
I.ve even tried to flash a few with no luck. Mister Android has fallen and can't get up with the RED triangle and all.
I can get the tablet in Apx mode.
Also I can get the screen with the Fastboot...
I've tried all the tricks with the volume up and power button and toggle switch, AND/OR the volume down button and toggle.
But without the UIP or CPUID those items aren't doing me any good.
The tablet was only updated the old fashioned way. No customized anything.
Hubby mainly used it to get email and play pocker over the internet with it.
Not sure what other information you need, but I hope someone could get me out of this MISERY!
Been messing with it for over a week trying to read and get as much information about others having simular situations.
Thank you in advance & Hope to hear from you SOON!
We've even tried doing things in different computers...:crying:
radarbill said:
My husbands Acer a500 screen froze when he was playing Zimga a poker game when this happened.
He believes he had ICS but he is not sure of anything speciffic.
He doesn't have any type of backup.
Click to expand...
Click to collapse
Well, seeing it a stock tab, not a lot of options.
I would try this, here is a link where I gathered 4 500 ICS updates. Note that I named them with build numbers to keep things in order.
Rename one of the files to only "update.zip" (remove the build number in other words).
With the tab off, hold VOL+ and PWR until you see the update start to install, then release both.
Now, if one of them doesn't complete, then try the other. Hopefully one of them completes the install and boots the tablet.
Here's the link;
http://forum.xda-developers.com/showpost.php?p=31323893&postcount=8
MD
How to recover Acer a500 without any backup? Need Help?
Moscow Desire said:
Well, seeing it a stock tab, not a lot of options.
I would try this, here is a link where I gathered 4 500 ICS updates. Note that I named them with build numbers to keep things in order.
Rename one of the files to only "update.zip" (remove the build number in other words).
With the tab off, hold VOL+ and PWR until you see the update start to install, then release both.
Now, if one of them doesn't complete, then try the other. Hopefully one of them completes the install and boots the tablet.
Here's the link;
http://forum.xda-developers.com/showpost.php?p=31323893&postcount=8
MD
Click to expand...
Click to collapse
I appreciate you getting back so quickly.
I've already tried these.
I also tried most of these from this web page.
http://forum.xda-developers.com/showthread.php?t=1816560
Nothing seems to work.
There was a couple of them that would install about 25% but then android would keel over and the red triangle of death took over.
I would appreciate if you had any other suggestions, or if anyone else did.
There has to something I can do?!?
Well, without having the UID number, I think NVFlash is out of the question. Usually we get these quite simply when the tab is operating.
There is a Linux solution, to get UID, but I'm not a linux guy. There's a thread about UID, I think in the dev section. In there are steps to get it through Linux I believe.
With the UID, I think we can run TimmyDeans rollback tool. But as far as I know, you have to have the UID number.
MD
radarbill said:
I type in: sudo su
Then: gcc apx.c -o apx -lusb-1.0
I end up with an errors.
If I remember correctly it says that line 4 and line 5 of EPPE code was in errors.
The another time it states...
Then it stats su: invalid option -- 'o'
Click to expand...
Click to collapse
Please post the the commands you run and the exact result you get, it is hard to tell what went wrong without knowing exactly what you did and exactly what results you got.
Just a copy of the terminal buffer as it is would be good.
Moscow Desire said:
There is a Linux solution, to get UID, but I'm not a linux guy.
Click to expand...
Click to collapse
I have posted code for two Windows variants as well, one using libusb-win32 and one using the winusb driver delivered by Acer.
It can be found in the [GUIDE] Recovering Recovery/Obtaining SKB thread.
solved thankyou all
eppeP said:
Please post the the commands you run and the exact result you get, it is hard to tell what went wrong without knowing exactly what you did and exactly what results you got.
Just a copy of the terminal buffer as it is would be good.
I have posted code for two Windows variants as well, one using libusb-win32 and one using the winusb driver delivered by Acer.
It can be found in the [GUIDE] Recovering Recovery/Obtaining SKB thread.
Click to expand...
Click to collapse
well we ended up getting a new mobo and that did the trick. so thankyou one and all
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
Hello,
Recently I've bought a new B&N Nook Glowlight (4GB, BNRV500).
All was good and well, until I've figured out that I've a few kindle books (.mobi) and PDF's that I'd love to be able to read them on my brand new NG.
I've done some reading here on XDA, and it seemed like a root has to be achieved (to gain ADB access) to in order to sideload some APKs.
Root operation is a GO.
After reading 40 and something pages out of the 'Hacking the new glowlight' thread, I've decided to use the method described by idefix0815.
TBH, it took me a while. I'm a regular user of Ubuntu, and the older versions of libusb drivers (described in idefix0815 post) gave me a headache.
So, I've tried OpenSUSE distribution as someone has recommended, and after a few versions, I've found a good one (I've tried the 32bit version, 32bit GNOME live usb, 64bit KDE live usb).
I followed the instructions, and things were alright. Until I rebooted for the first time. Seems like I had only ReLaunch (with no stock launcher) and apparently I've disabled also the stock epub reader. So, again, I enabled them. Now, when pressing the home button , I get to choose between the stock launcher and the ReLaunch.
Quick question before I get to the point,
Isn't it weird that when I try to read a book (epub) using the stock launcher, it opens up immediately, yet when trying to open it up (same book or a different one) using the ReLaunch, a spinning wheel (loading icon) appears until I touch the screen (If I don't touch the screen, It just keeps 'spinning', also, I touch the screen right after opening the book, meaning the spinning wheel isn't 'loading the book' or something.) Any explanation?
Anyhow, I now have ADB access to the nook (Although when I try to 'adb shell' from my Ubuntu [AND NOT THE OS I USED FOR ROOTING IT, THAT ONE WORKS JUST FINE], I get an error message saying 'ADB: error: insufficient permissions for device'. So I've to run 'adb kill-server' and 'sudo adb usb' to gain access to adb shell (tried listing the files using 'ls', seems to be working.)
Now what?
Can someone please direct me to some APK worth installing (Kindle app? recommended PDF/EPUB reader?)
Sorry for the long post and thanks in advance.