So everyone says never do this, but what can I say, I was curious
My Optimus was previously rooted using sublimewolf's method: http://forum.xda-developers.com/showthread.php?t=935312
I then proceeded to brick it by using the Factory Reset found in the Privacy Screen. This forced my phone into a recovery loop.
If you can't even get to your custom recovery, your phone might be your newest paperweight But as long as you can both get to recovery and access the phone via adb, you'll be okay.
So here's how to unbrick it:
This is the flash_image: http://www.mediafire.com/?bx14hzq5i2pq3ps
And here's the stock recovery image + nand backup: http://www.mediafire.com/?ac0e2ksq0eslytk
(In my case, I was able to skip to Step 4 in the Nandroid Instructions because I had performed a Nand Backup when I rooted, therefore the necessary files were already in place)
Nandroid Instructions:
1) Unzip both downloaded archives
2) Move the BCDS-20110203-0357 dir into /sdcard/nandroid/mem=477M (also extract recovery.img and flash_image to root dir of your SD card, as you will need to later anyway)
2a) For Clockwork Recovery, place the BCDS-20110203-0357 dir into /sdcard/clockworkmod/backup
3) Mount SD into phone if it isn't already, boot into recovery if your phone isn't already there
4) Go into the "Backup/Restore" menu, and select "nand restore", confirm and wait
5) Reboot, proceed to Recovery Instructions below
Recovery Instructions:
1) Extract recovery.img and flash_image to root dir of your SD card if you haven't already done so
2) Connect to your phone via the adb shell and input the following commands:
# su
# mount -o remount,rw -t yaffs2 /dev/block/mtdblock5 /system
# cat /sdcard/flash_image > /system/bin/flash_image
# chmod 755 /system/bin/flash_image
# mount -o remount,ro -t yaffs2 /dev/block/mtdblock5
# flash_image recovery /sdcard/recovery.img
# reboot recovery
3) If everything was done correctly, your phone should boot up normally to the OS
If the links above go down, let me know and I'll re-up
(thanks to tankhull for putting this info together)
(oh and you're welcome for being a guinea pig )
Thank you very much for putting this together
I am one of the curious one too.
You saved me....
If you can't get into recovery, I'm sure you can flash one through fastboot. No?
Sent from my VM670 using XDA App
Hi!
I had stock rom, but my phone was rooted.
So if whenever I turn my phone on, it goes to Clockwork Mod, does that mean it is bricked?
And will there be any way to unroot my phone after I do this? BC my 3G wasn't working at all, it should be working, but its not, so I did a factory reset.
Didn't work for me
when typing su after nand restore i get
/sbin/sh: su: not found
Ok so I have followed the instructions to the letter. And am attemptingto access adb shell. But in cmd prompt when I type adb devices it comes up with list of devices attached and says nothing. So how are we supposed to be accessing adb shell?
In clockworkmod, I went to the option for mounting and mounted the sd card, and a folder popped up on my comp, and there was no folder called Nandroid or clockworkmod
Any help guys?
I don't understand how to do the Nandroid instructions part... do I have to go to ADB?
atr0phy said:
So everyone says never do this, but what can I say, I was curious
My Optimus was previously rooted using sublimewolf's method: http://forum.xda-developers.com/showthread.php?t=935312
I then proceeded to brick it by using the Factory Reset found in the Privacy Screen. This forced my phone into a recovery loop.
If you can't even get to your custom recovery, your phone might be your newest paperweight But as long as you can both get to recovery and access the phone via adb, you'll be okay.
So here's how to unbrick it:
This is the flash_image: http://www.mediafire.com/?bx14hzq5i2pq3ps
And here's the stock recovery image + nand backup: http://www.mediafire.com/?ac0e2ksq0eslytk
(In my case, I was able to skip to Step 4 in the Nandroid Instructions because I had performed a Nand Backup when I rooted, therefore the necessary files were already in place)
Nandroid Instructions:
1) Unzip both downloaded archives
2) Move the BCDS-20110203-0357 dir into /sdcard/nandroid/mem=477M (also extract recovery.img and flash_image to root dir of your SD card, as you will need to later anyway)
2a) For Clockwork Recovery, place the BCDS-20110203-0357 dir into /sdcard/clockworkmod/backup
3) Mount SD into phone if it isn't already, boot into recovery if your phone isn't already there
4) Go into the "Backup/Restore" menu, and select "nand restore", confirm and wait
5) Reboot, proceed to Recovery Instructions below
Recovery Instructions:
1) Extract recovery.img and flash_image to root dir of your SD card if you haven't already done so
2) Connect to your phone via the adb shell and input the following commands:
# su
# mount -o remount,rw -t yaffs2 /dev/block/mtdblock5 /system
# cat /sdcard/flash_image > /system/bin/flash_image
# chmod 755 /system/bin/flash_image
# mount -o remount,ro -t yaffs2 /dev/block/mtdblock5
# flash_image recovery /sdcard/recovery.img
# reboot recovery
3) If everything was done correctly, your phone should boot up normally to the OS
If the links above go down, let me know and I'll re-up
(thanks to tankhull for putting this info together)
(oh and you're welcome for being a guinea pig )
Click to expand...
Click to collapse
In the nandroid instructions, for placing BCDS-20110203-0357 into the /sdcard/nandroid/mem=477M
Do I have to do that, or step 2a if I have Clockworkrecoverymod, "For Clockwork Recovery, place the BCDS-20110203-0357 dir into /sdcard/clockworkmod/backup"
Also, how do I put this directory into the /sdcard/clockworkmod/backup folder or /sdcard/nandroid/mem=477M
Do I use ADB? And if so, how do I, because I have no idea about what commands/etc to use.. or could somebody please link me to a guide on how to push a file/folder into a folder like the ones I previously mentioned (/sdcard/clockworkmod/backup folder or /sdcard/nandroid/mem=477M)
Thank you in advance for your help!
Wreak_Peace said:
In the nandroid instructions, for placing BCDS-20110203-0357 into the /sdcard/nandroid/mem=477M
Do I have to do that, or step 2a if I have Clockworkrecoverymod, "For Clockwork Recovery, place the BCDS-20110203-0357 dir into /sdcard/clockworkmod/backup"
Also, how do I put this directory into the /sdcard/clockworkmod/backup folder or /sdcard/nandroid/mem=477M
Do I use ADB? And if so, how do I, because I have no idea about what commands/etc to use.. or could somebody please link me to a guide on how to push a file/folder into a folder like the ones I previously mentioned (/sdcard/clockworkmod/backup folder or /sdcard/nandroid/mem=477M)
Thank you in advance for your help!
Click to expand...
Click to collapse
You are making this harder than it has to be. All you are trying to do is place a folder and some files on your micro sdcard. Place the micro sd card on your computer. Grab the folder "BCDS-20110203-0357" and drag it to "/sdcard/clockworkmod/backup" (yes, that one because you have the clockworkmod recovery). If you have no way of placing the micro sd card onto your computer (card reader, micro sd to sdcard converter), then leave the card in the phone, connect the phone to your compter via USB, boot into the recovery, and then turn on USB massstorage mode through the recovery options. This should make the micro sd card pop up on your computer like a usb harddrive. Drag and drop the files.
mmarz said:
You are making this harder than it has to be. All you are trying to do is place a folder and some files on your micro sdcard. Place the micro sd card on your computer. Grab the folder "BCDS-20110203-0357" and drag it to "/sdcard/clockworkmod/backup" (yes, that one because you have the clockworkmod recovery). If you have no way of placing the micro sd card onto your computer (card reader, micro sd to sdcard converter), then leave the card in the phone, connect the phone to your compter via USB, boot into the recovery, and then turn on USB massstorage mode through the recovery options. This should make the micro sd card pop up on your computer like a usb harddrive. Drag and drop the files.
Click to expand...
Click to collapse
I put my microsd card into my computer, and there are no folders called sdcard, clockworkmod, or nandroid :/
Wreak_Peace said:
I put my microsd card into my computer, and there are no folders called sdcard, clockworkmod, or nandroid :/
Click to expand...
Click to collapse
Lol, first off, the sd card IS the folder "sdcard". That will only show up on your phone. Secondly, if the folders aren't there, just make them. They are not magic folders. Just right click, and select new -> folder, and name them as described.
clockworkmod\backup\
And then copy "BCDS-20110203-0357" into the "backup" folder.
You do have the Clockworkmod Recovery, right?
I do, and now, when i opened up my cmd
I did "cd c:\android\platform-tools"
then "adb shell"
then this came up "~#"
so even then, I went ahead and did "su"
and it said,
"su
/sbin/sh: su: not found"
So, what do I do now?
and I went ahead anyways did the next step
i typed in "mount -o remount,rw -t yaffs2 /dev/block/mtdblock5 /system"
then it said
"mount -o remount,rw -t yaffs2 /dev/block/mtdblock5 /system
(next line) mount: mounting /dev/block/mtdblock5 on /system failed: invalid arguement"
Try doing only the last two lines,
Code:
flash_image recovery /sdcard/recovery.img
reboot recovery
So I just do
"cd C:\android\platform-tools
adb shell
flash_image recovery /sdcard/recovery.img
reboot recovery"
Or do i add the su in an additional line after adb shell
?
Wreak_Peace said:
So I just do
"cd C:\android\platform-tools
adb shell
flash_image recovery /sdcard/recovery.img
reboot recovery"
Or do i add the su in an additional line after adb shell
?
Click to expand...
Click to collapse
You don't need the su because you already have the "#" sign. That means you have super user privileges.
mmarz said:
Try doing only the last two lines,
Code:
flash_image recovery /sdcard/recovery.img
reboot recovery
Click to expand...
Click to collapse
K, so this is what I came out with when doing what you said.. this is without typing in su after adb shell.
Code:
cd c:\android\platform-tools
c:\Android\platform-tools>adb shell
~ # flash_image recovery /sdcard/recovery.img
flash_image recovery /sdcard/recovery.img
failed with error: -1
error opening /sdcard/recovery.img~ # flash_image recovery /sdcard/recovery.img
flash_image recovery /sdcard/recovery.img
failed with error: -1
error opening /sdcard/recovery.img~ # reboot recovery
reboot recovery
This is what I came up with when i did type su after adb shell..
Code:
cd c:\android\platform-tools
c:\Android\platform-tools>adb shell
~ # flash_image recovery /sdcard/recovery.img
flash_image recovery /sdcard/recovery.img
failed with error: -1
error opening /sdcard/recovery.img~ # flash_image recovery /sdcard/recovery.img
flash_image recovery /sdcard/recovery.img
failed with error: -1
error opening /sdcard/recovery.img~ # reboot recovery
reboot recovery
c:\Android\platform-tools>adb shell
I've never done this method so I can't tell you why it is not working or how it should work. Sorry.
I do have my own method for solving the bootloop issue. Try flashing this with your recovery: http://www.mediafire.com/?fbaoutnaw717pnb
Place it on your SD card and then use your recovery's flash zip option to flash it. It has helped others. It will replace your recovery with the Xionia recovery. If it works, you should boot into the LG logo. Once you can do that, boot into your recovery by using the correct button combo and flash any rom that you want to use.
mmarz said:
I've never done this method so I can't tell you why it is not working or how it should work. Sorry.
I do have my own method for solving the bootloop issue. Try flashing this with your recovery: http://www.mediafire.com/?fbaoutnaw717pnb
Place it on your SD card and then use your recovery's flash zip option to flash it. It has helped others. It will replace your recovery with the Xionia recovery. If it works, you should boot into the LG logo. Once you can do that, boot into your recovery by using the correct button combo and flash any rom that you want to use.
Click to expand...
Click to collapse
So i extract it to root of the micro sd? all of it? and then instead of recovery.img its vrecovery.img?
And so if it replaces my recovery with xionias recovery, it will boot into android and I can use my phone normally?
Related
just wondering if anyone can help me out here, i was trying to flash the cyanogen hero recovery image to my phone using fastboot so i erased my stock recovery image, only to get the message "remote: signature verify fail" so im now stuck with no recovery image and dont know how to get it back, can anyone help me out please?
ok so i managed to mount my system as read write in fastboot and put the recovery.img from the wwe version in to system which has gave me my recovery back but when i boot it just stays on the hero screen and says fastboot usb at the top if i have it plugged into my pc. i have no idea how to reset the original files and i didnt back up, can anyone help me pleas?
Well after trying for hours to fix this, I give up. I can't install the system.img from wwe rom posted on here it says verify failed or something similar so I stupidly tried to flash the magic 32a heroski port hoping it would work and still nothing. Is there anyway someone could post there nandroid backup file and help me flash it to see if that works? Or should I just give up. I'm really stuck now lol
you can't flash anything from fastboot because the images need to be signed.
what version of hero do you have?
if you have the wwe hero(it's not needed ) i can send you (later, now i'm at work) my nandroid backup (system,boot,recovery, splash...) so you can restore them
I have the orange hero. I used fastboot to load cyanogens recovery image then flashed the heroski rom hoping it might work lol so I ended up using fastboot to erase system. Question is do you think your nandroid backup would work? I sure hope so it would be a great help!!! Thanks.
i have the unlocked wwe hero. i'm uploading now the system, boot and recovery to rapidshare . it'll be up in a couple of minutes. if you find a orange hero backup you can restore in the same way ;-)
restoring hero wwe
download the backup from(it's better if you verify the md5):
http://rapidshare.com/files/263636068/bkp.rar.html
MD5: BEAE167BCBB1FF6D3D2701FB64604203
Put the contents on sdcard (i'm assuming that you put the images in a folder named bkp on the sdcard)
so:
download the recovery from here: http://rapidshare.com/files/262621147/cm-hero-recovery.img.zip and extract it
put your phone in fastboot mode (with the phone off, press the back key then turn the phone on).
then:
boot with the downloaded recovery
Code:
fastboot boot cm-hero-recovery.img
0) mount the partitions
Code:
adb shell mount /system
adb shell mount /sdcard
1) do a wipe
select the wipe option from the recovery menu
2) restore boot
Code:
adb shell flash_image boot /sdcard/bkp/boot.img
3) restore recovery
Code:
adb shell flash_image recovery /sdcard/bkp/recovery.img
4)restore system
Code:
adb shell
cd /system
rm -rf * (ignore the errors)
unyaffs /sdcard/bkp/system.img
5) unmount the partitions
Code:
umount /system
6) reboot
Code:
reboot
hope it helps
Ok thanks. Have to wait 4 hours to try it as I'm in work lol, what is an md5 for, just out of curiosity?
A MD5sum is a checksum to verifiy that your downloaded file isn't corrupt.
maxisma said:
A MD5sum is a checksum to verifiy that your downloaded file isn't corrupt.
Click to expand...
Click to collapse
Ok dude makes sense thanks.
thanks
enlightener said:
download the backup from(it's better if you verify the md5):
http://rapidshare.com/files/263636068/bkp.rar.html
MD5: BEAE167BCBB1FF6D3D2701FB64604203
Put the contents on sdcard (i'm assuming that you put the images in a folder named bkp on the sdcard)
so:
download the recovery from here: http://rapidshare.com/files/262621147/cm-hero-recovery.img.zip and extract it
put your phone in fastboot mode (with the phone off, press the back key then turn the phone on).
then:
boot with the downloaded recovery
Code:
fastboot boot cm-hero-recovery.img
0) mount the partitions
Code:
adb shell mount /system
adb shell mount /sdcard
1) do a wipe
select the wipe option from the recovery menu
2) restore boot
Code:
adb shell flash_image boot /sdcard/bkp/boot.img
3) restore recovery
Code:
adb shell flash_image recovery /sdcard/bkp/recovery.img
4)restore system
Code:
adb shell
cd /system
rm -rf * (ignore the errors)
unyaffs /sdcard/bkp/system.img
5) unmount the partitions
Code:
umount /system
6) reboot
Code:
reboot
hope it helps
Click to expand...
Click to collapse
ok so i finally got time to fix my phone and just did what you said and can now happily say it worked. thanks enlightener you enlightened me lol. in future i will refrain from doing random terminal stuff without researching first lol.
Bad new : My hero is out of service area
Hello,
Sorry for my english, i'm french
I made a big mistake in my files system ... A too long story
My Hero :
HBOOT-1?76.0004
Radio-6.35.04.25
July, 3 2009
Well, now, my htc hero do not work 'first page, out of service area"... I would like to make your post, but i had error :
First, fastboot Ok, Adb shell mount system and sdcard ok, wipe ok
Second, when i do this code" adb shell flash_image boot /sdcard/bkp/boot.img", my hero "said" : "header is the same, note flashing boot". Same thing for restore recovery
Can you help me ?
pitou21 said:
Hello,
Sorry for my english, i'm french
I made a big mistake in my files system ... A too long story
My Hero :
HBOOT-1?76.0004
Radio-6.35.04.25
July, 3 2009
Well, now, my htc hero do not work 'first page, out of service area"... I would like to make your post, but i had error :
First, fastboot Ok, Adb shell mount system and sdcard ok, wipe ok
Second, when i do this code" adb shell flash_image boot /sdcard/bkp/boot.img", my hero "said" : "header is the same, note flashing boot". Same thing for restore recovery
Can you help me ?
Click to expand...
Click to collapse
in this case, you don't have to restore boot or recovery because they are the same as the images posted here.
proceed with system
Ok thanks, now it's goog !
I'm trying to remove some of the stock apps on my Hero, including Rosie (Sense UI) and such. What mode do I boot in before doing this?
I know all of the steps to remove apps using adb (at least I think I do), I'm fully rooted, etc. But I can't seem to get it to work.
This is the command I'm using in adb
Code:
# rm /system/app/something.apk
(replacing something.apk with the actual apk name of course)
When I boot in Recovery, it says "File not found". When I boot in Fastboot, I can't connect to adb it seems. And when I boot into Android, it says "rm failed for something.apk, Read-only file system"
So am I missing a step? What should I be doing differently?
Boot into recovery, then do a "mount -a" to mount the filesystems.
marinierb said:
Boot into recovery, then do a "mount -a" to mount the filesystems.
Click to expand...
Click to collapse
It doesn't seem to work, here's the output:
Code:
C:\asdk\tools>adb devices
List of devices attached
HT9ALNT00557 recovery
C:\asdk\tools>adb shell
/ # mount -a
mount -a
mount: mounting /dev/block/mmcblk0p2 on /system/sd failed: No such file or direc
tory
/ #
Thanks for the reply though.
Edit: Got it working, typing in "mount" alone without the -a switch worked Thanks marinierb
in normal mode you cold have just done
adb remount
adb rm /system/app/something.apk
garok89 said:
in normal mode you cold have just done
adb remount
adb rm /system/app/something.apk
Click to expand...
Click to collapse
That doesn't seem to work for me. This is what it outputs:
Code:
remount failed: Operation not permitted
If you can't remount it doesn't sound like you've rooted.
callummr said:
If you can't remount it doesn't sound like you've rooted.
Click to expand...
Click to collapse
I've performed other operations that would normally require it, so I should be rooted.
Is there a way I can confirm if it's properly rooted or not?
shell prompt:
$ .. no root
# .. root
..try typing "su" once in the shell (abd shell or adb-windows.exe shell) and see what it brings up
~David said:
It doesn't seem to work, here's the output:
Code:
C:\asdk\tools>adb devices
List of devices attached
HT9ALNT00557 recovery
C:\asdk\tools>adb shell
/ # mount -a
mount -a
mount: mounting /dev/block/mmcblk0p2 on /system/sd failed: No such file or direc
tory
/ #
Thanks for the reply though.
Edit: Got it working, typing in "mount" alone without the -a switch worked Thanks marinierb
Click to expand...
Click to collapse
typing only "mount" just list the mounted partitions, it will not mount anything. if your partition is ext4 you need to downgrade it to ext2 or ext3 or set the testflag, see "if you're having issues with ext4" in the first post of the recovery image thread.
Make sure you have run a Nandroid backup first so that if you accidentally remove something important.
Boot into normal mode. (full GUI)
Then:
Code:
C:\ADB MOUNT
C:\ADB SHELL
# rm /system/app/something.apk
reboot
You have to reboot at the end so that the apps are taken out of RAM, you may get FC (errors) if you try to do stuff after removing the apps before rebooting.
I removed (actually moved) *Twit*, Stock*, Launcher*, and a few other things.
HTH,
Unconn
Got bored of searching and googleing... but using MoDaCo's WIP R4 FroYo ROM and Clockwork Recovery... when I flashed the ROM I lost the boot time animation (the PC BIOS one) so tried to put it back in recovery using adb push *file* /data/local (file copied ok) but still only have the htc boot screen also tried pushing the file with the phone booted, but again no dice
Anyone got any ideas?
Thanks in advance
------ Resolution ------
Ok, firstly massive thanks to those who helped - you are what xda is all about ... I finally managed to resolve this problem by
adb mount /system
adb shell
looking around and removing all bootanimation.zip's I could...
then exit the shell session and adb push the bootanimation.zip to /system/media
adb reboot and
I found this info here: http://androidforums.com/all-things-root-droid/97562-froyo-boot-animation.html
Not sure why this keeps changing? Maybe it is something specific to the Modaco R5 ROM?
Try pushing it to /system/customize/resource
yes the directory for froyo is the
/system/customize/resource
thanks for the assist guys, I tried this in recovery
"adb push bootanimation.zip /system/customize/resource" which went ok, the adb reboot and no show with the new boot screen any ideas??
Many thanks
first of all
mount the /system
then the path should be /system/customize/resource/bootanimation.zip
still cant get it to work I'm afriad
Here is what I did...
reboot to recovery (clockwork mod)
adb shell mount /system/
adb push bootanimation.zip /system/customize/resource
adb reboot
and no new boot animation
any ideas what I'm doing wrong?
Ok, found this http://forum.xda-developers.com/showthread.php?p=7239986 - booted to clockworkmod recovery and tried:
adb shell
mount /system
and got "mount: mounting /dev/block/mtdblock3 on /system failed: Device or resource busy
MadMic said:
still cant get it to work I'm afriad
He is what I did...
reboot to recovery (clockwork mod)
adb shell mount /system/
adb push bootanimation.zip /system/customize/resource
adb reboot
and no new boot animation
any ideas what I'm doing wrong?
Click to expand...
Click to collapse
Is that a typo? the path for the first adb command entry should be 'adb shell mount /system', not 'adb shell mount /system/'
Also, where are you placing the bootanimation.zip file? try placing it directly to the C: (C:\bootanimation.zip) and try executing the commands again.
MasDroid said:
Is that a typo? the path for the first adb command entry should be 'adb shell mount /system', not 'adb shell mount /system/'
Also, where are you placing the bootanimation.zip file? try placing it directly to the C: (C:\bootanimation.zip) and try executing the commands again.
Click to expand...
Click to collapse
Thanks for the reply -
The bootanimation.zip is in the same folder as adb... it says xxx bytes copied which is the same as the file size... I've tried with /system with and without the trailling / still no joy..
If I do adb shell mount /system in recovery I dont see anything... but if I do adb shell [enter] then the commands I see the error about the device being busy...
Is there anyway to do this from a terminal app in the phone directly?? I seem to recall there is but cant find it...
Thanks for the help guys
http://psfreedom.com/wiki/index.php?title=OpenDesire4.0.4
http://www.ps3hax.net/showthread.php?p=123003
Im trying to install this recovery so i can jailbreak my PS3, but when i try to use unrEVOked, it hangs while pushing the recovery
When i try to use adb on both my phone and my computer it says i have no space!
what should i do?
EDIT:
fastboot erase recovery
fastboot flash recovery recovery.img
sounds like it would work, bu t i dont want to risk that lol
The no space error will happen if you don't mount system as writable. By default it is set as read only.
Read around to lookup the command to remount system as writable. The command varies depending on your device.
For the motorola droid I used the following:
mount -o remount,rw -t yaffs2 /dev/blockmtdblock4 /system
I think the G1 and other HTC phones use mtdblock3 instead of mtdblock4, but I'm not sure.
SwordOfWar said:
The no space error will happen if you don't mount system as writable. By default it is set as read only.
Read around to lookup the command to remount system as writable. The command varies depending on your device.
For the motorola droid I used the following:
mount -o remount,rw -t yaffs2 /dev/blockmtdblock4 /system
I think the G1 and other HTC phones use mtdblock3 instead of mtdblock4, but I'm not sure.
Click to expand...
Click to collapse
Alright, thats good to know. Ill look around
http://forum.xda-developers.com/showthread.php?t=770663
"You can only write to system on the desire via adb from recovery."
So i do what? boot into recovery, plug in my phone and adb it again?
flash_image recovery image.img?
Hmm, guess not.
I booted into recovery. Plugged my phone in and did an adb devices. It said one device called recovery
i did mount /sdcard (apparently i dont have to mount it to a location)
i cd'd into thte sdcard and did a flash_image recovery psfMod.img and it said i had no space
I was also looking at this
http://forum.xda-developers.com/showthread.php?t=770663
but i still cant get it to work.
do i have to have s-off?
Any ideas?
lonelliott said:
Any ideas?
Click to expand...
Click to collapse
Which command did you send?
Sent from my Kindle Fire using Tapatalk
are you logged in on adb? Try to type "exit" then "adb shell".
You don't have to mount your sdcard after using adb shell. (at least I didn't have to on my mac)
For some reason it will not mount my sdcard, at all. I can adb shell onto it, but when I try to run the update.zip from it, I get an error saying it cannot mount the sd card.
I had the same issue on mine. Heres the fix:
In TWRP with the fire connected to the pc run:
Code:
adb shell
echo /dev/block/mmcblk0p12 > /sys/devices/platform/usb_mass_storage/lun0/file
Windows will probably respond that the volume/device needs formatted before using it.
Thats okay. choose quick format and let it format it as fat32 block size 4096.
when its done
in twrp choose the mount option and mount USB storage then hit unmount again
tap the box next to Mount SDCard. It should now look like
[X] Unmount SDCard.
Download the 6.2.1 pre-rooted zip file from the thread in the dev section.
choose mount USB Storage
Place on SDCard
Turn off usb storage
choose wipe
choose cache
choose factory reset
choose dalvik cache
choose system
go back and choose install
choose the zip you placed on your sdcard
flash it.
reboot. if it reboots back into twrp
run
Code:
adb shell
idme ? <--that will probably tell you the bootmode is 0x5003
idme bootmode 0x4000
exit
in twrp choose reboot
choose system
enjoy! it may take a while to boot
I have the same problem. Can't mount sdcard.
I'm doing your fix step by step in Win XP. I formatted partition into Fat32. Though it didn't allow me to select block size. It just has one option "Default allocation size". Capacity is 200MB.
After that I'm trying to tap on the Mount SDCard option, but it wouldn't change to [X] Unmount SDCard. So it wouldn't mount and I'm back to the problem.
Any ideas on what could go wrong?
I finally figured it out!
The key thing is that sdcard HAS to be formatted in a certain way - FAT32 (and presumingly block size 4096 as mentioned above).
Brief history:
I followed the above instruction and formatted sdcard on a mac with Disk Utility. That didn't work. It still wouldn't mount. I tried to do the same thing in Windows XP. No luck. It wouldn't mount with the same "Invalid argument" error.
I figured that I should try and format sdcard right from the TWRP shell. I deleted and recreated partition with fdisk. Then I learned that TWRP 2 comes with pretty old busybox which doesn't have mkfs or mkfs.vfat to format the partition to FAT 32. So took the busybox binary from the pre-rooted 6.2.1 and pushed it to the KF. And I used mkfs.vfat.
Instructions:
Download and unzip pre-rooted 6.2.1..
Rename busybox to busybox1 (just not to mess up existing version) and copy it to your KF.
Code:
adb push /path_to_unzipped_6.2.1/system/xbin/busybox1 /sbin
Go to shell:
Code:
adb shell
~ # chmod 755 /sbin/busybox1
~ # busybox1 mkfs.vfat /dev/block/mmcblk0p12
~ # mount sdcard
There you go! Now your sdcard is mounted. And you can proceed with the instruction above.
death2all110, thanks for the post. This solved my issues....beer money sent!
Brad
Thanks Dmitry_G, That was exactly what I needed!
You guys are amazing and you have brought my Kindle back from the dead. Thank you sincerely.
i need someone to help me with this please i'm a newbie with the same problem
Same to me, but i got error, help me!
I follow your guide, but have error, pls help!!!
C:\>adb shell
~ # chmod 755 /sbin/busybox1
chmod 755 /sbin/busybox1
~ # busybox1 mkfs.vfat /dev/block/mmcblk0p12
busybox1 mkfs.vfat /dev/block/mmcblk0p12
mkfs.vfat: can't open '/dev/block/mmcblk0p12': No such file or directory
~ # ^
You try copy mmcblk0p12 file from another KF to your KF.
This error by mmcblk0p12 deleted
Death, I don't know if you will see this reply because this thread is so old but if you do,THANK YOU!!!!!! THANK YOU!!! THANK YOU!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! I had messed with kfu, unbrick utility and many other methods to try to unbrick my kindle and your guide was exactly what I needed.
death2all110 said:
I had the same issue on mine. Heres the fix:
In TWRP with the fire connected to the pc run:
Code:
adb shell
echo /dev/block/mmcblk0p12 > /sys/devices/platform/usb_mass_storage/lun0/file
Windows will probably respond that the volume/device needs formatted before using it.
Thats okay. choose quick format and let it format it as fat32 block size 4096.
when its done
in twrp choose the mount option and mount USB storage then hit unmount again
tap the box next to Mount SDCard. It should now look like
[X] Unmount SDCard.
Download the 6.2.1 pre-rooted zip file from the thread in the dev section.
choose mount USB Storage
Place on SDCard
Turn off usb storage
choose wipe
choose cache
choose factory reset
choose dalvik cache
choose system
go back and choose install
choose the zip you placed on your sdcard
flash it.
reboot. if it reboots back into twrp
run
Code:
adb shell
idme ? <--that will probably tell you the bootmode is 0x5003
idme bootmode 0x4000
exit
in twrp choose reboot
choose system
enjoy! it may take a while to boot
Click to expand...
Click to collapse
THANK YOU! It worked! I was about to trash this thing.