After trying to do a factory reset with the latest CWMR, my kindle no longer mounts any of the partitions. I have been able to view the folders when directly loading TWRP through fastboot, but fastboot oem format doesnt work, nor does firekit usb tools, nor rekindle, and yes I've tried the short into usbboot mode method. The kindle was fully functional this morning until trying to do a factory reset.
Unfortunately, I missed the little one line blurb buried in the CWM dev post about not doing this, but it completely ruined all adb partitioning functions. I can access an adb shell and fastboot, but no repartition tools are working. This includes the entire thread about reformatting each partition http://forum.xda-developers.com/showthread.php?t=1388996
Nearly every command I issue in parted, when booting from fastboot directly into cwm, hangs, and I have to ctrl+c out of it.
I do not know where else to turn at this point. It seems like I need to completely wipe the emmc, but it won't respond to any commands required to do this.
I checked the emmc type, I forget the post, and it was not the type affected by the one-time-write bug.
Does anyone have any ideas on how to reformat the kindle from the ground up, becuase that's the only thing left... basically ripping out the memory chip and erasing it.
I am on the same page as you, others are too
Dont know what to do, i live in brazil and will cost as much as a new kindle to send it to repair.
I am thinking about formating the /dev/block/mmcblk0 in ext4 but dont know if it will make things even worse.
I thought about asking for fastboot images and flashing all the partitions through that, but I'm not sure that would work because the partition table is still ruined beyond repair.
edit:
if we completely erase the emmc, can it still do a usbboot shorting the pin to ground? then maybe the partition table would take.
Do you think the eMMC is the problem? I think its only the partitions, maybe the master /dev/block/mmcblk0 is corrupt and the other are too.
If you try to Mount USB Storage on TWRP or CWR, it will say, at least on mine, that the windows needs to format the storage and if you agree, it dont recognize the size of the partition
I have read a few threads where others have gone ahead and let windows format their SD card it seems they had good results I don't know how this pertains to the problem you guys are having maybe the only recourse is to buy another motherboard sadly I will dig around later to see if I can find a solution.
I never got it to mount the usb partition, but I agree, it's definitely partition table related. Under adb shell I can view all the files on there that should be there, specifically the ones I downloaded. Not sure what I could do from here, since installing anything would be moot anyway without partitions to install to.
Can you run an adb shell? What is the result of running 'fdisk /dev/block/mmcblk0' ? My shell just hangs until i ctrl-c out of it. The problem with this whole situation is that every tool that could possibly format the disk just hangs when used...
have you read through this thread? http://forum.xda-developers.com/showthread.php?t=1654498
---------- Post added at 12:35 AM ---------- Previous post was at 12:32 AM ----------
the nipad rom might have some rescue for you only issue its in chinese.
Already a dozen times
My fdisk returns this
~ # fdisk /dev/block/mmcblk0
fdisk /dev/block/mmcblk0
fdisk: can't read from /dev/block/mmcblk0
I think we need to format the master partition, /dev/block/mmcblk0
if we could do this, maybe we have a chance i think, but dont know if doing this it will screw everything up
fastboot oem format runs in about 0.6 seconds and returns success. Tried Firekit too, samething
Related
There doesn't appear to be anyone that has this problem, and I wasn't able to find anything in the development forum for CWM.
Per what everyone says, can't format /data or "factory reset" in CWM due to some sort of partition thing.
1. I boot to CWM
2. I go to mounts and storage and unmount /data
3. I plug the usb into the computer
4. Open Command Prompt and go to the adb directory
5. Enter Command adb shell and opens ~# at least that is what it looks like
6: I type "/sbin/mke2fs_static -t ext4 -b 4096 /dev/block/mmcblk0p30"
7: the response "/sbin/sh: /sbin/mke2fs_static: not found"
What am I doing wrong?
Edit: I figured it out. I ended up having to reinstall practically everything. But it worked
1 Loaded backed up rom from cwm
2 reinstalled adb
3 copied the backup recovery image back to it's original place.
4 factory reset
5 copy the cwm back
6 boot to recovery mode
7 adb commands work!!!
edit: I really should learn better grammar. I cleaned the wording up a bit.
edit2: I solved my own problem
The command not being recognized was a result of not having the latest CWM from bytecode installed. He updated it from his initial release to add support for these commands. Glad you figured it out! It can be frustrating when stuff like that happens.
Personally I'm avoiding CWM all together at this point. It's been almost a month with not a single problem (besides the BT incident) with no CWM installed, no boot loops, no reboots. There is something seriously wrong with current CWM...
[email protected] said:
Personally I'm avoiding CWM all together at this point. It's been almost a month with not a single problem (besides the BT incident) with no CWM installed, no boot loops, no reboots. There is something seriously wrong with current CWM...
Click to expand...
Click to collapse
You are right, i brick my phone today.
I was lucky that Bell change it for a brand new.
Rom development is not that safe with a so bad recovery...
HO!NO! said:
You are right, i brick my phone today.
I was lucky that Bell change it for a brand new.
Rom development is not that safe with a so bad recovery...
Click to expand...
Click to collapse
Indeed, but I have been ok since not touching /data via CWM. The manual format of /data works fine. I have flashed my own ROM zips over 20 times without issue.
Sent from my LG Nitro HD
[email protected] said:
Personally I'm avoiding CWM all together at this point. It's been almost a month with not a single problem (besides the BT incident) with no CWM installed, no boot loops, no reboots. There is something seriously wrong with current CWM...
Click to expand...
Click to collapse
I still feel CWM is a very important safety net if anything goes serious wrong ( I saw there is some download mode, but I still feel cwm is much easier to use than download mode).
For example, if you phone /system messed up, how do you fix, you only have download mode, right? If you have cwm, you will have one more option.
HO!NO! said:
You are right, i brick my phone today.
I was lucky that Bell change it for a brand new.
Rom development is not that safe with a so bad recovery...
Click to expand...
Click to collapse
I saw these unfortunately case several times in this forum, even though I never met for my self ( I following instructions never touched /data), so when you say brick, what happen exactly? Can you boot into cwm?
gte460z said:
The command not being recognized was a result of not having the latest CWM from bytecode installed. He updated it from his initial release to add support for these commands. Glad you figured it out! It can be frustrating when stuff like that happens.
Click to expand...
Click to collapse
I figured I just had a bad install. Because I think the version was the same...
but anyway, it was most definitely a fun experience.
I love CWM if it weren't for CWM I wouldn't be able to reset my phone. Which was way necessary...porting a new rom over existing data instead of a clean system caused some really interesting errors.
adb shell
umount /data
/sbin/mke2fs_static -t ext4 -b 4096 /dev/block/mmcblk0p30
/sbin/e2fsck_static -y /dev/block/mmcblk0p30
its working on LG SU640，you can try
I've done so much research on this and tried so many things and now I'm so confused on what to do.
I'm trying to bring this KF back from the dead. It was stuck in a bootloop, no computer would recognize it. So I soldered a factory cable..that made my computer actually see the KF.
After that I used the KFU to install TWRP and FFF. It's currently in fastboot mode. I have managed to get it into ADB a few times. Everytime I do that I get an "ACK" error.
I'm attaching a screenshot of an older verson of KFU and of my device manager as well as my .ini file. I added a line in my .ini file which you will see.
I have tried using most of the fastboot commands to reboot it into "normal" mode but it doesn't seem like it does anything.
Currently it's on the Kindle Fire boot screen (it's white & blue) and says v1.4a in the upper right corner. I've uninstalled/reinstalled drivers many times. Maybe I'm doing something wrong there.
I also tried the Kindle Fire Unbrick Utility with no luck. At this point I can't get into TWRP. I tried to mount the SD card in there last night so I could copy update.zip over but it threw an error. Something like E: /sdcard could not mount.
I have also had Clockwork recovery installed and I tried to mount the sd card in there. Similar error. Am I wrong in believing if TWRP was working I should be able to ADB in from there?
I feel like I've done a lot of research and tried very hard before making a thread..so any ideas at this point are very welcome!
Edit: It actually does boot into clockwork recovery at this point. The exact error is: E:Can't mount /sdcard
To mount your sdcard:
Boot into recovery and enter...
Code:
adb shell
echo /dev/block/mmcblk0p12 > /sys/devices/platform/usb_mass_storage/lun0/file[CODE]
And if you have to, format your sdcard FAT32 block size 4096
Obviously, by formatting your sdcard, you will lose all the data that's on it.
I need to keep rebooting/messing around until it's in ADB mode to do that correct? Or will it work in fastboot mode?
You can't use adb in fastboot.
I still can't get it in ADB mode again.. I tried ubuntu as well with no success..should I be using the factory boot cable at this point? Or should I just keep telling it to boot into "normal" (adb) mode and hope it does that one of these times? I wish I could just get the drive to show up in windows..
edit: I guess I had misunderstood before. I selected recovery mode in KFU (option 3) and then ran the stuff you told me to. this was the result: error: device not found and: the system cannot find the path specified
The factory cable probably won't do you much good.
In Ubuntu, did you install drivers and set up udev rules for adb? And are you using 32 or 64 bit?
Sorry I didn't post that earlier, I'm using windows vista- 32 bit. In ubuntu I simply used firekit. No other configuration was done. I did the jumper trick & it claimed it re-wrote the file system but it appears it didn't touch it. It did install an older version of TWRP & FFF.
I'm not completely convinced it has ever made it into ADB, everytime KFU claims it's online my internet connection is completely lost & that's where I get the ACK error.
I guess one thing I'm very unclear about- is it possible adb was completely removed? It certainly seems like it. It should load adb from the FFF screen, correct?
Just an FYI I got the kindle like this so please don't think I'm a complete moron!
Is your Ubuntu on a LiveUSB or full install? If it is a LiveUSB did you set it up with any persistence?
It is a live cd, and no- I didn't set it up with any persistence. I wouldn't be opposed to installing ubuntu if needed. I also have access to Osx (hackintosh) on the same machine, it's dual booting windows/osx.
Thanks for all your help.
do you have an 8 gig usb drive?
legojerry said:
It is a live cd, and no- I didn't set it up with any persistence. I wouldn't be opposed to installing ubuntu if needed. I also have access to Osx (hackintosh) on the same machine, it's dual booting windows/osx.
Thanks for all your help.
Click to expand...
Click to collapse
OSX should do. Get it booted up and PM me.
Nada, I'm headed to walmart now to get one though..lol
If you have OSX, there should be no need for LiveUSB.
Okay. PM was sent.
Format SD card
I Bricked, looped, KF. Resisted far too long just formatting the SD card and starting over. At some point that is likely your only option. Rebuilding your KF , rooting , and ROMing. Partial fixes cxan be frustrating as well.
Sadly I can't get the sdcard formatted..
legojerry said:
Sadly I can't get the sdcard formatted..
Click to expand...
Click to collapse
Wont mount? Your the second one this week. I have done both methods factory/data reset including sdcard contents and factory/ data reset wiped sd as well in twrp the only worked fine for me only thing is my sdcard is now known as removable storage on my computer. Theres got to be a way to get that card mounted to the system or unmounted and mounted to the pc for formating
I wish I could just see the file system from my computer..nothing, and TWRP errors out.
yeah I have been working with someone else on a the same issue with no avail
---------- Post added at 05:37 PM ---------- Previous post was at 05:35 PM ----------
Im wondering if the battery wasnt unplugged and replugged if it would force it to mount either way shutting down the system maybe windows would be able to grasp it for formatting my only fear with that is it might hand you the system partition instead
Interesting idea.. I just tried that, windows detected it- now it's showing an unknown device and it's sitting at the FFF bootloader.
edit: just tried it again, it went straight into fastboot.
If you encrypt your phone using ICS encryption on CM9 for example then you can't just put in a password to turn off the encryption feature like you can on a Samsung rom. Today my phone was completely unusable because I couldn't boot into recovery or Android, reverting to stock with Odin would make my phone hang at the Samsung logo when booting Android. We're going to flash a new recovery using Odin and format your /data partition so that you can mount your internal and external SD cards once again so your phone is usable.
Software required:
Odin
ADB
Files:
Odin
http://samsung-updates.com/Odin307.zip
Flashable CWM Recovery
https://www.dropbox.com/s/ukx3l58wpcb3h4b/connor.tar.md5
Open Odin and make sure Auto Reboot and F. Reset Time are checked, click PDA and open connor.tar.md5 then flash the phone.
Once the recovery is done flashing and your phone is rebooting remove the battery from your phone. Replace the battery and hold volume up, home (center button) and power. Once the Samsung logo appears release the power button and your phone will boot into recovery. From here we are going to format our data partition.
Start an adb shell.
Linux:
/android-sdk-linux/platform-tools/adb start-server
adb shell
Windows:
Open a CMD window in your ADB folder (shift click and click open new command window).
adb shell
From here we are going to format our data partition.
cat /etc/recovery.fstab
If /data is mmcblk0p15 then everything is going as planned.
mke2fs -t ext4 /dev/block/mmcblk0p15
What that command will do is format your /data partition.
mount /data
mount
You should see /dev/block/mmcblk0p15 mounted on /data
Flash a new rom and your broken phone is now usable.
Credits to koush for CWM and utkanos for helping me with the process.
Thanks for the info. However it seems to me that the encryption causes more problems than it helps. I've seen too many posts about how implementing encryption ends up screwing someone. But I've never seen a post that said...wow I am sure glad that I encrypted my phone! Let's face it...unless u are working for the government or the like...there's no need for it. And if u are working for the government, they will have some I.T. guy handling it for you. Its best to leave it alone and password protect your phone / files / data and then u wouldn't have to deal with the above steps.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
My friend runs his Galaxy Nexus rooted with no custom rom and has his phone encrypted because he's strange like that (when googling about illegal stuff he always uses an incognito browsing session), he's just paranoid I suppose. I encrypted mine just because I could without thinking that something like this could occur. There was absolutely no information on the internet about how to undo the encryption and this is the only possible way I know.
Does anyone know how to restore mtd to bml through adb?
i bricked a phone and cant get into DL mode and it just loops to cwm. now before everyone starts sending me links to tools and odin images to fix this, just stop. cause i know its a formatting error.
it seems when i mount the device in adb it says the /cache partition is ext4
here is the recovery log(i know its not this phone but the best devs i know are in here)
http://pastebin.com/wVtxEqw4
is there a way i could adb push the boot.img systemrfs and others? or am i sol?
I recall a thread somewhere in the abyss of this forum that gave the complete partition layout for our device, and shows how to use adb and whatnot for pushing files to said partitions.
You might want to start getting crafty with your search queries to try and locate that info.
Hey guys,
My password isn't working (never did) and I can't get much done in my phone. What to do?
So I was running CM11 on my LS980 and things were working great. I had a nandroid of the rooted stock software on my PC, and decided to encrypt my phone.
So I tried to encrypt my phone, the encryption went well (I think), but when I got to the screen where I type a number in, my code wouldn't work. I wrote it down, I made absolute sure I had it right. I selected the Pin option, as well as the option to automatically unlock the phone when the pin is entered correctly.
I typed the proper code in, and it just kept saying "try again." I have a nandroid backup of the rooted stock Rom saved to my computer, so I can fix this I think, but how do I get back in? I originally heard that wiping data/factory reset would get rid of encryption, but when I try this with my CWM 6.0.4.7 I get:
-- Wiping data...
Formatting /data...
Error mounting /data!
Skipping format...
Formatting /cache...
Formatting /sd-ext...
E: unknown volume for path [/sd-ext]
Formatting /sdcard/.android.secure...
Error mounting /sdcard/.android_secure!
Skipping format...
Data wipe complete.
Someone told me this has to do with the way CWM tries to format things (by mounting them first), and that I can go into mounts and storage. but which ones do I format there? I really don't want to mess anything up. Here are my options:
/boot
system
data
cache
persist
firmware
sns
persist-lg
mpt
/data and /data/media (/sdcard
Thanks!
Mods, please move
1. You are in the wrong section, this is not help and troubleshooting (I know more people will see it here) However, we learn from others mistakes and when you post in there people with the same problem might search and see a solution of how you solved your problem.
2. Not sure if adb works in recovery or if it will in your situation but I would try adb reboot recovery or try adb sideload and sideload a rom onto it.
This does not belong in the Development Section, read the Forum Rules on posting....Moved here, thanks.
jhr5474 said:
1. You are in the wrong section, this is not help and troubleshooting (I know more people will see it here) However, we learn from others mistakes and when you post in there people with the same problem might search and see a solution of how you solved your problem.
2. Not sure if adb works in recovery or if it will in your situation but I would try adb reboot recovery or try adb sideload and sideload a rom onto it.
Click to expand...
Click to collapse
Ok ****. So far I've always avoided having to use adb while rooting (rooted evo 4g, gs2, and lg g2). Guess it's time to learn. Any advice on where to start reading?
Judge Joseph Dredd said:
This does not belong in the Development Section, read the Forum Rules on posting....Moved here, thanks.
Click to expand...
Click to collapse
Hey thanks man
While you're here mind telling me why my profile pic doesn't show up on my posts?