[Q] How do I restore oem partition table? - Kindle Fire Q&A, Help & Troubleshooting

hi
I was attempting (ok tempting fate) repartitioning my app space using the fireparted utility (yeah, I know it breaks stuff) and you guessed it... (it broke stuff)
So my partitions 10 and 11 are now gone.
How do I restore the partitions back to oem? I read about using firefirefire to do it, but I dunno what I'm doing. can someone walk me through it?
I have adb access, and I have the latest firefirefire I think (I ran kfu and it said it installed and I noticed my boot logo changed to the green android over Kindle Fire)
I tried running fastboot oem format and it gave me:
... FAILED (remote failure)
but it could be I just don't know how or when to run it.
I did a fastboot devices and right now it's giving me
0123456789ABCDEF fastboot
Thanx for your help.

berighteous said:
hi
I was attempting (ok tempting fate) repartitioning my app space using the fireparted utility (yeah, I know it breaks stuff) and you guessed it... (it broke stuff)
So my partitions 10 and 11 are now gone.
How do I restore the partitions back to oem? I read about using firefirefire to do it, but I dunno what I'm doing. can someone walk me through it?
I have adb access, and I have the latest firefirefire I think (I ran kfu and it said it installed and I noticed my boot logo changed to the green android over Kindle Fire)
I tried running fastboot oem format and it gave me:
... FAILED (remote failure)
but it could be I just don't know how or when to run it.
I did a fastboot devices and right now it's giving me
0123456789ABCDEF fastboot
Thanx for your help.
Click to expand...
Click to collapse
"fastboot oem format" is only available on FFF versions 1.1 and greater. Version 1.0 (i.e. the one installed by TWRP 2.0.0) does not have this feature.

Install this first: http://forum.xda-developers.com/showthread.php?t=1541043
Then try fastboot oem format

Thanks. When it happened I went to KFU and installed the latest firefirefire, and then went to install latest twrp, which must have downgraded firefirefire back. D'oh.
I knew I must have been missing something simple.
I ran the oem format and then restored a backup I had on it. So it looks like it's working again. Thanks.
I was really hoping to find a better way of repartitioning the apps space. 1gb is not enough by a long shot.

Related

[Q] Wiped the WHOLE Kindle, Need help ASAP!

so yesterday i got tired of my ICS Rom. So, i went to recovery (TWRP) then recovered my old back up of stock. But since it had all the settings like when I flashed the rom, I Factory reseted it. But then suddenly it had deleted the whole stock rom! Couldn't go back. So my kindle was stuck on recovery loop over and over again. I got really impatient. So I started moving around then I mounted my Kindle to my computer and apped the ICS Rom that I used before. Then it flashed but it was still stuck on recovery. started moving more stuff on it, clicked the partitioning sd card and now I can't mount my kindle via Usb -___- and Then I new it was on Recovery fastboot. Please help! I Need this fixed. it deleted everything. and when I connected it to Adb shell, it says "Missing system/bin/sh"
Help me! i'm going to california on next week and I would like my kindle to work for me to play, listen to music, watch tv on it on the way.
Sorry for bad Grammar -___-
Do you have FFF? Is fastboot working at all? If so, have you tried fastboot oem format? (this will cause all your data to get lost), or booting/reflashing TWRP?
Dasanko said:
Do you have FFF? Is fastboot working at all? If so, have you tried fastboot oem format? (this will cause all your data to get lost), or booting/reflashing TWRP?
Click to expand...
Click to collapse
I Have FFF 1.4, have TWRP 2.1 and fastboot works. But Mounting USB don't work. In recovery it says (cannot mount /sdcard/ (Invalid argument).)
What's the output of
adb shell "parted /dev/block/mmcblk0 p"
?
Can you please explain what that means. i really don't now many of these commands. I need more like a Step-by-step. Like in ADB Shell, it says error: device not found
Luise. said:
Can you please explain what that means. i really don't now many of these commands. I need more like a Step-by-step. Like in ADB Shell, it says error: device not found
Click to expand...
Click to collapse
Means your KF is either not plugged in, or the drivers are wrong. You can't go on until the drivers are properly installed, if that's your issue. Take a look here: http://forum.xda-developers.com/showpost.php?p=23747671&postcount=2
Okay, Installed ADB Drives I think it now works it just tells me (exec '/system/bin/sh' failed: No such file or directory (2))
Can you type "fastboot getvar product" and then restart/plug in the KF?
Dasanko said:
Can you type "fastboot getvar product" and then restart/plug in the KF?
Click to expand...
Click to collapse
Yes i did and it says "Kindle"
Get TWRP (http://teamw.in/project/twrp2/79) and type "fastboot boot openrecovery-twrp-blaze-2.1.1.img" and see if you can get ADB working now.
Okay I already have TWRP Installed on 2.1.1 so Do I just go on Recovery and try to work adb shell on there instead of FFF Fastboot?
You just hinted at your ADB not working properly, try to fastboot boot into that TWRP to see if ADB works fine from it (I guess your drivers are good on the Device Manager, no errors or warnings showing up?). If it doesn't, then I guess the alternative is to try restoring the entire stock layout...
okay, I have TWRP, and when i have the usb connected to Kindle while its on Recovery, My Internet i use a Easytether so you can tell what android devices are connected and while my kindle is on recovery, The Easytether says My Kindle can connect, (but it really cant) and the ID Shows up that 0000005 number? but I Really Need My kindle to work! -__-
These issues have been fixed.
For future reference, this user was experiencing a combination of bad drivers and a corrupt sd card partition (rm 12 + mkpartfs primary fat32 start end + name 12 media).
The ADB issues were gone after fixing the drivers, without a need to reinstall TWRP.

[Q] Kindle flashing and factory software

Hi everyone, I have two kindle fire, I messed with both of them.
I've root them the first one has the problem with the yellow triangle logo stucked. And the other one I've tried to reset it to the factory settings and everything was cool until I hit the TWRP utility and I think I erased everything.
I've see tons of posts regarding rooting and troubleshooting related to rooting and i'm pretty sick of rooting, I think that 3 months is sufficient time, please DON'T POST anything related to rooting.
I'm here asking if anyone knows how to flash all the data ofthe kindle from the pc and been able to install the factory software, firmware (I don't know) from scratch from my pc. Anyone, please?
The first one is probably stuck in fastboot. Try giving it a go with "fastboot oem idme bootmode 4000 && fastboot reboot".
For the second one, "I think I erased everything" is as descriptive as not wanting people to post about your procedure is helpful. What exactly is going on with it? For future reference: http://forum.xda-developers.com/showthread.php?t=1644970
You should also update both FFF and TWRP on both devices once they are working normally.
If i may suggest flashing modaco first after a good wipe everything except your sdcard I believe this will make a smoother transition if you desire to return to stock before returning to stock always do a good wioe to remove remnants of previous roms download the latest stock bin and rename it to update.zip do not place it in any folder just at the root of your sdcard flash in twrp this will also wipe out twrp and fff I really dont recommend doing this lots of people fail at doing the procedure correcty modaco is stock with only the market added try this approach first then you can retain fff and twrp for custom backups.
Ok, so, I've been investigating and what I'm really looking is to erase ABSOLUTELY everything from the kindle sdcard, system, etc, everything. And I'm looking for a method to sideload from the pc the orginal stock ROM of Kindle Fire. Any clues, directions? Any fully functional software?
I really, don't want to try the adb commands (I've tried them before), nor follow any tutorial about root troubleshooting.
I'm really sick of them and of all that mal-functioning software that you have to download(Eg. Not-responding superOneClick, kindleFireUnbrickUtility saying in one line <No device found> <Processing something> <Congrats, your kindle is good to go! (When it's not)>, Eternal loading Android Commander)
With all due respect I DON'T want any more of those, as I said, 3 months is sufficient time, I feel so frustrated.
jRam90 said:
Ok, so, I've been investigating and what I'm really looking is to erase ABSOLUTELY everything from the kindle sdcard, system, etc, everything. And I'm looking for a method to sideload from the pc the orginal stock ROM of Kindle Fire. Any clues, directions? Any fully functional software?
I really, don't want to try the adb commands (I've tried them before), nor follow any tutorial about root troubleshooting.
I'm really sick of them and of all that mal-functioning software that you have to download(Eg. Not-responding superOneClick, kindleFireUnbrickUtility saying in one line <No device found> <Processing something> <Congrats, your kindle is good to go! (When it's not)>, Eternal loading Android Commander)
With all due respect I DON'T want any more of those, as I said, 3 months is sufficient time, I feel so frustrated.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=25730666&postcount=2
Read from "Reverting to stock software". You can manually rename the file and then copy it into the KF instead of using ADB for it, just make sure the extension is .zip and not .zip.bin (Windows hides extensions per default settings).
jRam90 said:
Ok, so, I've been investigating and what I'm really looking is to erase ABSOLUTELY everything from the kindle sdcard, system, etc, everything. And I'm looking for a method to sideload from the pc the orginal stock ROM of Kindle Fire. Any clues, directions? Any fully functional software?
Click to expand...
Click to collapse
To restore back to full factory
1. Download Kindle Fire Software Update Version 6.3.1
2. Rename the file to update.zip
3. Get in to TWRP and mount USB drive
4. Copy update.zip to Kindle Fire
5. Unmount USB drive
6. Do factory reset, then wipe system cache, and dalvik cache
7. Flash the update.zip
8. Let it bootloop about 3 times or so...
If you want FFF and TWRP then flash Stock 6.3.1 Basic from TWRP. This has no root or gapps.
Dasanko said:
http://forum.xda-developers.com/showpost.php?p=25730666&postcount=2
Read from "Reverting to stock software". You can manually rename the file and then copy it into the KF instead of using ADB for it, just make sure the extension is .zip and not .zip.bin (Windows hides extensions per default settings).
Click to expand...
Click to collapse
When trying to execute the adb shell commands all I get is:
- exec 'system/bin/sh' failed: No such file or directory (2) -
I've also tried, fastboot update | flash | boot | flash:raw
This is with one kindle, with the other one, I can't even get the PC to recognized it as a USB
Is there any tool, that really erases everything and take the stock ROM to be installed again? Software, script?
jRam90 said:
When trying to execute the adb shell commands all I get is:
- exec 'system/bin/sh' failed: No such file or directory (2) -
I've also tried, fastboot update | flash | boot | flash:raw
This is with one kindle, with the other one, I can't even get the PC to recognized it as a USB
Is there any tool, that really erases everything and take the stock ROM to be installed again? Software, script?
Click to expand...
Click to collapse
Ahh, that's a bother. It's a pretty annoying error. Could be something messed with your TWRP (I'm assuming you tried the commands from there).
There isn't one, but there's really no need for it... you just rename the ROM to update.zip, wipe cache, dalvik-cache and factory reset, and install update.zip. If you just want to flash stock because you like it better for whatever reason, you could also just look at the MoDaCo custom ROM instead, as it is stock based.
As for the other KF... you can't get it recognized, from where? The ROM? TWRP? Fastboot?
Dasanko said:
Ahh, that's a bother. It's a pretty annoying error. Could be something messed with your TWRP (I'm assuming you tried the commands from there).
There isn't one, but there's really no need for it... you just rename the ROM to update.zip, wipe cache, dalvik-cache and factory reset, and install update.zip. If you just want to flash stock because you like it better for whatever reason, you could also just look at the MoDaCo custom ROM instead, as it is stock based.
As for the other KF... you can't get it recognized, from where? The ROM? TWRP? Fastboot?
Click to expand...
Click to collapse
Both of the kindles, are damaged. I can't access them. I just can access one by USB.
For future reference:
This user's issues have been partially dealt with.
The first KF will require a factory cable to be fixed.
The second KF was soft bricked (there were a few corrupt partitions) after a bad flash attempt of the stock ROM. Luckily, FFF was still installed, but the Windows fastboot drivers weren't. Reinstalled FFF+TWRP from Firekit, and then fixed the partitions, wiped and flashed the stock ROM.
Dasanko said:
For future reference:
This user's issues have been partially dealt with.
The first KF will require a factory cable to be fixed.
The second KF was soft bricked (there were a few corrupt partitions) after a bad flash attempt of the stock ROM. Luckily, FFF was still installed, but the Windows fastboot drivers weren't. Reinstalled FFF+TWRP from Firekit, and then fixed the partitions, wiped and flashed the stock ROM.
Click to expand...
Click to collapse
Thanks a LOT, Dasanko !!!!
jRam90 said:
Thanks a LOT, Dasanko !!!!
Click to expand...
Click to collapse
Ok, So, I have the factory cable. How can I test its Ok?
I have another question, the kindle is pratically empty no system, no sdcard memory, probably corrupted ¿How do I use the factory cable, to format the Kindle and install the Stock ROM again?
With the KF off and unplugged, type "fastboot getvar product" on a shell (KFU/tools).
Then plug in the KF using the factory cable. If you get anything listed or returned, it should be working fine. Otherwise, if you wait a few seconds and still nothing, you'll have to check the drivers to make sure the correct fastboot ones are installed.
To check the partitions, you can just "fastboot boot twrp.img" to load a TWRP into memory, and then "adb shell parted /dev/block/mmcblk0 p" to print all partitions' information.
Dasanko said:
With the KF off and unplugged, type "fastboot getvar product" on a shell (KFU/tools).
Then plug in the KF using the factory cable. If you get anything listed or returned, it should be working fine. Otherwise, if you wait a few seconds and still nothing, you'll have to check the drivers to make sure the correct fastboot ones are installed.
To check the partitions, you can just "fastboot boot twrp.img" to load a TWRP into memory, and then "adb shell parted /dev/block/mmcblk0 p" to print all partitions' information.
Click to expand...
Click to collapse
Well, I'm at my job now. So I will try this at home, but the shell is not working since system/sh (shell) it's not in the Kindle. I was trying to boot it yesterday with "fastboot boot twrp.img" and nothing. I also tried: "fastboot getvar product" and nothing but I only used the console. Anyway, let's see what happens...
Quick question, I've read that the factory cable puts the Kindle straight into bootmode, ¿So the color of the power button, has something to do with it? ¿I mean how do I know the kindle has entered factory mode? ¿The orange light is an indicator? (With a standard USB Cable I only get the green light with the power button, with the factory cable I first get green light, then orange light)
I've also read that if I can see the Kindle fire logo, the bootloader is Ok. Hence my Kindle is OK, but I can't enter fastboot mode. ¿Can anyone confirm this?
It'll get stuck in the bootloader screen, and fastboot commands should work as well, provided the drivers are properly installed and working.
Dasanko said:
It'll get stuck in the bootloader screen, and fastboot commands should work as well, provided the drivers are properly installed and working.
Click to expand...
Click to collapse
OK, I've finally made myself a working factory cable. And in the device manger I can see the kindle listed as "Android phone" and in that root it says "Android ADB Interface". Look like drivers are not working. Where can I download them?
Those are the proper drivers for fastboot you should be able to use kfu to send twrp and fff to the device if that doesn't work you will need to fastboot flash them
All I get is < waiting for device>. Looks like the drivers are not installed.
Simply hold the power button down while connected when it says waiting then power it back on and it should send also try unplug replug when it says waiting
---------- Post added at 03:49 PM ---------- Previous post was at 03:44 PM ----------
If you would like some help I have some time before work but you must finish your thread for the benefit of others

[Q] Bricked KF2 - no OS, fastboot & TWRP available

I've read through hundreds of similar threads and haven't been able to find a solution - I'll gladly give up my firstborn (and/or make a paypal donation) to anyone who is able to help solve my issue!!
From my research, I seem to have no OS installed on the Kindle, and as far as I can tell, I'm booting into fastboot mode (screen hangs on the blue/white Kindle Fire logo, screen does not ever dim). I AM able to access TWRP Recovery, but don't have any backup to load from, am unable to successfully flash the ROM that I have saved to my SD card. My device manager recognizes the Kindle as a Kindle Fire (Android ADB Interface), no yellow triangles. Typing ADB Devices into Command Prompt gets me: [device number ] offline. Typing fastboot devices into Command Prompt gets me nothing (blank line).
Background/How I 'Bricked' It: I have a Kindle Fire 2 and was able to successfully unroot/flash Cyanogenmod 10 onto it. Worked perfectly for about 6 months, when I decided that it would be a good idea to flash back to stock so that I could give it to a relative. I have TWRP 2.3.3.0, so I used a guide on xda to do the following:
I used a guide from xda and followed these instructions
-Download latest KF2 stock software from amazon. Re-name the file to update.zip
-Moved it to the root of the SD card
-Booted in to TWRP
-Factory Wipe/Restore
-Wiped Cache
-Wiped Dalvik Cache
-Wiped System
-Installed the "update.zip"
-Wiped cache/dalvik again
-Rebooted
Unfortunately, wiping the system seems to have wiped the CM10 OS (ROM) that I had installed, and there was a failure in installing the amazon stock:
Installing '/sdcard/download/update.zip...
assert failed: is_substring ("Otter2 , file_getstring("/proc/product_name"))
E: Error in /sdcard/download/update.zip
(Status 7)
Error flashing zip '/sdcard/download/update.zip'
Updating partition details...
Trying to reboot the system from TWRP results in a message that states: "No OS installed! Are you sure you wish to reboot?"
Investigating using ADB: So it looks like I have no OS on the Kindle Fire 2. This seems to be a problem because without an OS, I am unable to use adb (from what I've read, no OS = no way to accept/authenticate the computer RSA fingerprint to whitelist the kindle and allow adb to function). Trying to use KFU, KFFirstAide, or the Kindle UnBrick Utility results in Error: Device offline or Error: Device not found types of messages (I am assuming due to the fact that I can't "turn" adb on by accepting the RSA fingerprint prompt)
What does Device Manager tell me? My computer can 'see' the Kindle Fire in device manager [as I stated earlier: My device manager recognizes the Kindle as a Kindle Fire (Android ADB Interface), no yellow triangles] but going to My Computer and looking under mass storage devices, the computer doesn't seem to recognize the device as a USB storage device, which is a problem because I can't drag/drop or push/pull files to the SD card so I can't try to flash anything *other* than the original file that failed.
Fastboot Mode...? From what I can tell (http://forum.xda-developers.com/showthread.php?t=1668159), my device is in fastboot mode. My Kindle screen hangs on the blue/white Kindle Fire logo screen, which from what I understand is hashcode's bootloader/fastboot screen. However, when I look at the Hardware IDs in the device manager, it tells me that my hardware IDs are:
USB\VID_1949&PID_0006&REV_0216
USB\VID_1949&PID_0006
So...my kindle seems to be stuck on the blue/white fastboot screen, but register on my computer as the stock kindle fastboot? I'm not really sure what's going on there, and couldn't find too many people with the same discrepancy that I have...
I tried plugging in my cord (making sure to use a USB 2.0 port), going into Command Prompt and using some fastboot commands. (ie: fastboot flash bootloader \path\update.zip) but all I get is a <waiting for device> for a LONG time. As in, a few hours. Some basic googling/investigation seems to indicate that I don't have fastboot drivers installed, OR that I wasn't running fastboot in an 'elevated mode' but I haven't been able to find too many details about how to fix those, IF that is the problem.
TWRP 2.3.3.0: I can get into TWRP recovery just fine, although I can't seem to figure out how to get files onto my device. So I've tried re-installing the original update.zip file that failed the first time several times, with no success. trying to 'Mount' the device doesn't seem to do anything (at least, my computer doesn't see the device as USB storage regardless of whether it's mounted or not) I tried using Advanced --> ADB Sideload, but trying to send the file in Command Prompt using the adb sideload <filename> command just gets me an Error: Device not Found message. I thought maybe I could try Advanced --> Terminal Command, but have no idea how to do that or what it does, and most sites are very vague about the step-by-step details, so I didn't really touch it.
Not sure if this is relevant or not, but when my KF2 is plugged into (attached) to my computer with the cord and is in TWRP, device manager shows the device under 'Other Devices' --> Amazon Kindle Fire2, and there is a yellow triangle on it. Not sure why...going back to 'fastboot' mode gets rid of yellow triangles and is recognized as a Kindle Fire again.
At this point - I'm pretty much stumped and have (hopefully) demonstrated that I've done my best to do my own research/read through threads/done due diligence. Is there anyone out there that might have any suggestions? Or do I now have a very large paperweight?
ANY input/suggestions/encouragement is welcome! I absolutely and sincerely appreciate your time in reading through this thread and trying to help noobs like me!
Use fast boot mode to recover to stock: http://forum.xda-developers.com/showthread.php?t=2096888
Or
If you have access to twrp. Use the ADb sideload feature to push CyanogenMod or another ROM over.
One thing though- if you can boot into TWRP you didn't wipe the system partition. Twrp for kf2 requires a file named stack to be there.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
...tried those, but maybe am doing them incorrectly?
mindmajick said:
Use fast boot mode to recover to stock: http://forum.xda-developers.com/showthread.php?t=2096888
Or
If you have access to twrp. Use the ADb sideload feature to push CyanogenMod or another ROM over.
One thing though- if you can boot into TWRP you didn't wipe the system partition. Twrp for kf2 requires a file named stack to be there.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
Trying to use the ADB sideload feature to push CM or another ROM over doesn't seem to be working for me (unless I'm doing it wrong?)
I tried using Advanced --> ADB Sideload, but trying to send the file in Command Prompt using the "adb sideload C:\users\Name\update.zip command just gets me an Error: Device not Found message". Could I be using the command incorrectly?
Trying to use any fastboot command in Windows Command Prompt results in <waiting for device> to hang for hours, with no changes to command prompt and no changes to the kindle (still sits at the blue/white boot logo).
Ah. Sorry. Missed that in the OP.
Sounds like you probably need the drivers installed.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Fastboot Drivers
mindmajick said:
Ah. Sorry. Missed that in the OP.
Sounds like you probably need the drivers installed.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
Are there difference drivers for fastboot and adb? I don't get a 'yellow triangle' and my device manager identifies the device as a Kindle Fire [Android ADB Interface], so I thought I was okay.
Should I be looking for fastboot drivers?
And btw, thanks so much for your willingness to help and input!
ME TOO
Just purchased a KF from someone...thay had rooted it...I tried to unroot...got stuck...now mine is doing the same as yours. I hope someone has a fix for you as I too have a large paperweight.
Follow Up
tessa33 said:
I've read through hundreds of similar threads and haven't been able to find a solution - I'll gladly give up my firstborn (and/or make a paypal donation) to anyone who is able to help solve my issue!!
From my research, I seem to have no OS installed on the Kindle, and as far as I can tell, I'm booting into fastboot mode (screen hangs on the blue/white Kindle Fire logo, screen does not ever dim). I AM able to access TWRP Recovery, but don't have any backup to load from, am unable to successfully flash the ROM that I have saved to my SD card. My device manager recognizes the Kindle as a Kindle Fire (Android ADB Interface), no yellow triangles. Typing ADB Devices into Command Prompt gets me: [device number ] offline. Typing fastboot devices into Command Prompt gets me nothing (blank line).
Click to expand...
Click to collapse
tessa33,
I just sent you a response. Call me at 707-774-5923 when you have a moment.
Solution?
I figured I could post in this thread before staring my own because I am having a very similar issue trying to revert my Kindle Fire 2 back to stock from cyanogen so I can sell it. I downloaded the official software from Amazon but every time I try to flash it through TWRP I get the exact same error you were getting. Did anyone ever figure out how to resolve the issue for you?
Had the same problem, so I chatted with an Amazon associate, told him I turned it on one day and it showed the grey triangle and he sent me a new Kindle Fire 2nd Gen for free. Try that...
Sent from my iPhone using Tapatalk
Hello
I have rooted KF2 and I did factory reset I lost TWRP&Os I can see the device as ADB device, Howeverm when the device in fastboot the pc not recognize it.
issuing fastboot devices command return nothing.
I used ubuntu and windows still the same issue. any idea?

Partition table doesn't exist

Hey all,
So I seem to have soft bricked my tablet (Nexus 7 2013 LTE). I can get into fastboot mode (but not into the recovery menu) then I am stuck on the Google logo. Does this mean the device is repairable?
Device manager on Windows shows the tablet as
- an unknown device (no drivers installed / Samsung (Wugfresh) / Google drivers)
- Android bootloader interface (Snoop05's tool)
- Android ADB Interface (PDAnet (Wugfresh)).
On all of them the driver is not correctly installed and I have the exclamation mark showing on device manager. I am unable to access the tablet via fastboot or ADB at this time.
I have tried every permutation I can think of so am turning to the hive mind for advice.
To compound matters I am in Turkey and I don't speak Turkish. I've been in an internet cafe for about 5 hours now and it's 1am (Turkish keyboards have an ı where i should be and you can imagine how many times I have mistyped). I am on a year long cycle tour and the tablet has my music, books, guidebooks and dictionaries on it so I am pretty hacked off. Especially given that I've only just arrived...
I did manage to connect via ADB yesterday but ran out of time as I was borrowing someone's computer and can't replicate the steps. Gah!
I have backups of all my data so essentially I would just like to factory reset. Any help gratefully received!
Thanks,
Don
Well, I found the right combination of drivers (Snoop05's tool then PDANet on Wugfresh) and can now see the device via fastboot so I have unlocked it. However whenever I try and flash boot / system / recovery, etc via fastboot I'm receiving an error 'remote: partition table doesn't exist'. Any ideas, people?
Probably useful to add that the problem was initially caused when I removed the SIM card whilst the unit was switched on. I received a message asking me to reboot and it has been bricked since. Also, I was runing stock unrooted.
Thanks
I have now tried every toolkit I can find but still no joy. I seem to have corrupted my partition table which is preventing me writing anything to the device.
To confirm - I can boot into fastboot mode and can see the device via fastboot using command line and can unlock it using 'fastboot oem unlock'. I have the images to write using 'fastboot flash boot/recovery/system [image location] but nothing will let me write to the device without receiving the error 'FAILED - remote: partition table doesn't exist'.
I have searched everywhere and can't find very much. Is the device recoverable or have I fecked it...? I need to get out of internet cafes and onto my bike...
Cheers in advance
Gulp! 100+ views and no replies...does no-one want to break it to me that my lovely tablet is beyond help! Is the only solution some wizardry using GParted or something? I'm already in way over my head.
I'm only bugging you all as I am running out of time in town and need to head off into the wilds. I have tonight and that's it for at least a week. It would be nice to have some company ie books and music...oh and a Turkish dictionary and translator...poor attempt to drum up sympathy I know.
I'll be honest, I've never seen such an issue as yours but it's worth a try since you got fastboot to do fastboot format of all your partitions and see if it helps to flash factory image. Something like fastboot format system for example.
Sorry I can't be more help
Nexus 7 LTE
Carbon Rom
Faux Kernel
dondelion said:
I have now tried every toolkit I can find but still no joy. I seem to have corrupted my partition table which is preventing me writing anything to the device.
To confirm - I can boot into fastboot mode and can see the device via fastboot using command line and can unlock it using 'fastboot oem unlock'. I have the images to write using 'fastboot flash boot/recovery/system [image location] but nothing will let me write to the device without receiving the error 'FAILED - remote: partition table doesn't exist'.
I have searched everywhere and can't find very much. Is the device recoverable or have I fecked it...? I need to get out of internet cafes and onto my bike...
Cheers in advance
Click to expand...
Click to collapse
Remove Wug's drivers and what ever other old drivers you have and follow this tutorial http://forum.xda-developers.com/showthread.php?t=2381582 make sure your getting for the data and not WiFi only. Get them old drivers out of there first.
Sent from my Nexus 7 Flo running Odex SinLess ROM 4.4.2 with ElementalX kernel using XDA Premium 4 mobile app
Raverbunny said:
I'll be honest, I've never seen such an issue as yours but it's worth a try since you got fastboot to do fastboot format of all your partitions and see if it helps to flash factory image. Something like fastboot format system for example.
Sorry I can't be more help
Nexus 7 LTE
Carbon Rom
Faux Kernel
Click to expand...
Click to collapse
Fastboot format still appears to require an intact partition table as I still receive an error - 'FAILED (command write failed (invalid argument))' but thank for the response.
LinearEquation said:
Remove Wug's drivers and what ever other old drivers you have and follow this tutorial http://forum.xda-developers.com/showthread.php?t=2381582 make sure your getting for the data and not WiFi only. Get them old drivers out of there first.
Sent from my Nexus 7 Flo running Odex SinLess ROM 4.4.2 with ElementalX kernel using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I tried this but same problem - no partition table so unable write anything to the device, thanks...
don, did you ever solve this?
I am having a similar problem but cannot unlock the device.
i have the same problem ....i just usedf flo-ebb clamours repartition and it wiped out all my partions i can only access fast boot but cant install anything as it says " no such partition "
Is your bootloader unlocked? If so, you should be able to flash the factory image in fastboot.
If not, you should be able to sideload the OTA in recovery.

[Q] Wiped / no adb / Stuck on Fastboo

I feel silly and ashamed asking for help, but i f***ed up big time.
For some stupid reason I wiped my kindle and was left with only twrp. So no worries I thought Ill just push a rom back onto the sdcard via adb and all everything is fine...
So I though... win xp wont recognise the kindle any more. Well it does as amazon kindle 2 but not as adb device.
So I tried all this again:
http://forum.xda-developers.com/showthread.php?t=2283230
http://forum.xda-developers.com/showpost.php?p=37733595&postcount=361
and a little bit of this:
http://forum.xda-developers.com/showthread.php?t=2069117&highlight=root
and several other crazy things I read on XDA. Nothing realy helped.
So I thought. Hey! Why not try fastboot.... So I did. What a noobish thing to do...
Looking around I found this:
http://forum.xda-developers.com/showthread.php?t=2117224
screw adb in twrp, we'll use twrp's terminal emulator to go to fastboot with the command idme bootmode 4
In twrp, go to advanced. then go to terminal command. then press the select folder button.
type idme bootmode 4
reboot and you're in fastboot.
That is what I did.
Funny enough. Now ADB Drivers work perfectly and recognise Kindle as ADB device in the device manager.
Sadly though, when I try to connect through ADB or Fastboot in CMD no device is being detected.
I know you guys have better things to do than help noobsters to clean their mess up they have caused. However I would be dead gratefull if one of you mighty tech gurus could help me out on this one.
What can I do to get this fixed?
Thank you ever so much in advance!
androidschima said:
I feel silly and ashamed asking for help, but i f***ed up big time.
For some stupid reason I wiped my kindle and was left with only twrp. So no worries I thought Ill just push a rom back onto the sdcard via adb and all everything is fine...
So I though... win xp wont recognise the kindle any more. Well it does as amazon kindle 2 but not as adb device.
So I tried all this again:
http://forum.xda-developers.com/showthread.php?t=2283230
http://forum.xda-developers.com/showpost.php?p=37733595&postcount=361
and a little bit of this:
http://forum.xda-developers.com/showthread.php?t=2069117&highlight=root
and several other crazy things I read on XDA. Nothing realy helped.
So I thought. Hey! Why not try fastboot.... So I did. What a noobish thing to do...
Looking around I found this:
http://forum.xda-developers.com/showthread.php?t=2117224
screw adb in twrp, we'll use twrp's terminal emulator to go to fastboot with the command idme bootmode 4
In twrp, go to advanced. then go to terminal command. then press the select folder button.
type idme bootmode 4
reboot and you're in fastboot.
That is what I did.
Funny enough. Now ADB Drivers work perfectly and recognise Kindle as ADB device in the device manager.
Sadly though, when I try to connect through ADB or Fastboot in CMD no device is being detected.
I know you guys have better things to do than help noobsters to clean their mess up they have caused. However I would be dead gratefull if one of you mighty tech gurus could help me out on this one.
What can I do to get this fixed?
Thank you ever so much in advance!
Click to expand...
Click to collapse
I'm in a similar situation. TWRP will not mount anything, If i try to wipe cashe, ect it says failed. If i try adb push it does not work. At this point I would be fine with just going back to stock. Hopefully someone can find a solution to our problem.
androidschima said:
I feel silly and ashamed asking for help, but i f***ed up big time.
For some stupid reason I wiped my kindle and was left with only twrp. So no worries I thought Ill just push a rom back onto the sdcard via adb and all everything is fine...
So I though... win xp wont recognise the kindle any more. Well it does as amazon kindle 2 but not as adb device.
So I tried all this again:
http://forum.xda-developers.com/showthread.php?t=2283230
http://forum.xda-developers.com/showpost.php?p=37733595&postcount=361
and a little bit of this:
http://forum.xda-developers.com/showthread.php?t=2069117&highlight=root
and several other crazy things I read on XDA. Nothing realy helped.
So I thought. Hey! Why not try fastboot.... So I did. What a noobish thing to do...
Looking around I found this:
http://forum.xda-developers.com/showthread.php?t=2117224
screw adb in twrp, we'll use twrp's terminal emulator to go to fastboot with the command idme bootmode 4
In twrp, go to advanced. then go to terminal command. then press the select folder button.
type idme bootmode 4
reboot and you're in fastboot.
That is what I did.
Funny enough. Now ADB Drivers work perfectly and recognise Kindle as ADB device in the device manager.
Sadly though, when I try to connect through ADB or Fastboot in CMD no device is being detected.
I know you guys have better things to do than help noobsters to clean their mess up they have caused. However I would be dead gratefull if one of you mighty tech gurus could help me out on this one.
What can I do to get this fixed?
Thank you ever so much in advance!
Click to expand...
Click to collapse
What is the exact command you are running? Also uninstall any kindle drivers that are installed and let it reinstall the device, I always have to do that when I switch from adb recovery to fastboot, sometimes it will be part of a component device you have to uninstall, but in that case you have to check the components vid so you don't uninstall something else by accident. All fastboot commands should be prefixed with ”-I 0x1949” so for ex: fastboot -i 0x1949 getvar product
Hope this helps.
Sent from my Amazon Kindle Fire HD using Tapatalk
stunts513 said:
What is the exact command you are running? Also uninstall any kindle drivers that are installed and let it reinstall the device, I always have to do that when I switch from adb recovery to fastboot, sometimes it will be part of a component device you have to uninstall, but in that case you have to check the components vid so you don't uninstall something else by accident. All fastboot commands should be prefixed with ”-I 0x1949” so for ex: fastboot -i 0x1949 getvar product
Hope this helps.
Sent from my Amazon Kindle Fire HD using Tapatalk
Click to expand...
Click to collapse
hi there. thank you. when i type the command you said i get the following:
product otter2-prod-04
finished. total time: 0.016s
does this mean, that fastboot is actually working and i get a connection to the device?
androidschima said:
hi there. thank you. when i type the command you said i get the following:
product otter2-prod-04
finished. total time: 0.016s
does this mean, that fastboot is actually working and i get a connection to the device?
Click to expand...
Click to collapse
ok i get in and out of fastboot fine. i looked through the commands here for fastboot.
http://forum.xda-developers.com/showpost.php?p=23747804
so far so good.
However whenever i flash something onto the kindle in cannot find it. also when i am in twrp it tell me unable to mount data.
fastboot wont let me format the userdata. did i break the filesystem? this must have been done by twrp when accidently formatting it... right?
androidschima said:
ok i get in and out of fastboot fine. i looked through the commands here for fastboot.
http://forum.xda-developers.com/showpost.php?p=23747804
so far so good.
However whenever i flash something onto the kindle in cannot find it. also when i am in twrp it tell me unable to mount data.
fastboot wont let me format the userdata. did i break the filesystem? this must have been done by twrp when accidently formatting it... right?
Click to expand...
Click to collapse
im stuck....
i flashed new recovery through fastboot because this was supposed to get the twrp 2.3.3.0 bug out of the system formatting the data partition in a way i could flash a rom onto it. so new twrp 2.7 flashed through fastboot. according to the cmd it worked all fine...
now i come into white blue boot loade choose recovery and kindle wont boot from there.
this is just f***d up. Next time i jsut keep my hands of jailbreaking hardware.
anychance anyone out there could give me a hand and get this fixed? I am
I thought 2.7 hadn't been release for kf2. You sure you flashed the right version for your device? If it is a kf2 then flash this one: http://forum.xda-developers.com/showthread.php?t=2218868
Once you flash it from fastboot, recovery should work again.
Sent from my Amazon Kindle Fire HD using Tapatalk
stunts513 said:
I thought 2.7 hadn't been release for kf2. You sure you flashed the right version for your device? If it is a kf2 then flash this one: http://forum.xda-developers.com/showthread.php?t=2218868
Once you flash it from fastboot, recovery should work again.
Sent from my Amazon Kindle Fire HD using Tapatalk
Click to expand...
Click to collapse
ok got a factory cable and flashed the recovery as you said like that:
fastboot i- 0x1949 flash recovery d:\.android\recovery\twrpnew.img
target reportet max downlaod size of 486539264 bytes
sending 'recovery* (6768 KB)...
OKAY [ 0.438s}
writing 'recovery'...
OKAY [0.719s]
finished. total time 1.156s
so i reboot and select recovery but I get stuck on the blue white logo... what do I do wrong?
androidschima said:
ok got a factory cable and flashed the recovery as you said like that:
fastboot i- 0x1949 flash recovery d:\.android\recovery\twrpnew.img
target reportet max downlaod size of 486539264 bytes
sending 'recovery* (6768 KB)...
OKAY [ 0.438s}
writing 'recovery'...
OKAY [0.719s]
finished. total time 1.156s
so i reboot and select recovery but I get stuck on the blue white logo... what do I do wrong?
Click to expand...
Click to collapse
ok i am just making things worse here. i tried to erase the chach but accidently worte boot... (i know - stuidity needs to be punished)
soo now i get into fastboot. thats to the cable but i need all the files to flash to the right partitions.
could anyone tell me were to get the right
boot.img
system.img
Recovery.img
bootloader.bin
so i can just flash them back onto my device and get i over with....
PLEASE PLEASE PLEASE PLEASE!!!!
androidschima said:
ok i am just making things worse here. i tried to erase the chach but accidently worte boot... (i know - stuidity needs to be punished)
soo now i get into fastboot. thats to the cable but i need all the files to flash to the right partitions.
could anyone tell me were to get the right
boot.img
system.img
Recovery.img
bootloader.bin
so i can just flash them back onto my device and get i over with....
PLEASE PLEASE PLEASE PLEASE!!!!
Click to expand...
Click to collapse
kindle fire first aid has them. But it downloads them off the net last i heard so you wont find the images directly in there unless i am mistaken.
androidschima said:
ok i am just making things worse here. i tried to erase the chach but accidently worte boot... (i know - stuidity needs to be punished)
soo now i get into fastboot. thats to the cable but i need all the files to flash to the right partitions.
could anyone tell me were to get the right
boot.img
system.img
Recovery.img
bootloader.bin
so i can just flash them back onto my device and get i over with....
PLEASE PLEASE PLEASE PLEASE!!!!
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=43569633
This should be all u need
-》Sent from my mind to your screen.
Thank you! I will look into it!

Categories

Resources