Ok guys, i have truly screwed up. Im not sure if this is the right thread, but i need some serious help! I had my kindle fire rooted and flashed with cm9. It was running great then next thing i know i was getting spammed with "Sorry but the process com.android.phone has stopped working." everytime i click ok it would pop up again instantly. I looked online and it suggested a double-system wipe. So i did, but without thinking, i wiped the SD folder too! Which deleted my rom! My back ups are gone, i cant restore to anything! I still have TWRP v2.1.1 on it though. But when i boot normal it just sits at a black screen, help me please....
Are u able to open in recovery mode ?
Sent from my GT-S5830 using xda premium
Manvendra05 said:
Are u able to open in recovery mode ?
Sent from my GT-S5830 using xda premium
Click to expand...
Click to collapse
If you mean from the boot menu where it loads TWRP, then yes.
Josepho1997 said:
Mount your SD Card and transfer a new ROM, and then flash it. If you can't Mount, transfer the ROM via
adb push ROM /sdcard
And then flash it.
Sent from my Amazon Kindle Fire using xda premium
Click to expand...
Click to collapse
Im kind of new to the twrp, how do i mount my SD Card specifically? i can select mount but nothing shows up on my computer as Removable Disk like it did when i first put the ROM on there. I think my best bet would be pushing the ROM via adb, but could you explain more on how to do so?
Here let me help. I accidently did that this morning. If ur new to kf. adb is complicated. This adb free way. Not steppin on any ones shoes.launch twrp. Then go to mount it should be the bottom left button. Plug ur kf in . Then click mount usb. Then your kf should be connected to ur computer. From there you can go 2 ways download the stock rom. Or download any other custom rom. So download it and google apps on your comp. then copy and paste it somewhere on the kf sd card that you remember. On ur kf after the file is done copying hit unmount. Then reboot kindle and launch it into twrp again. then just hit install then locate the rom and coresponding g.apps then install it. Then ur good to go. I would back that up on the kf using twrp and create a folder on the comp and copy and paste the folders from kf to that just incase this happens again.
Jarodroll said:
Im kind of new to the twrp, how do i mount my SD Card specifically? i can select mount but nothing shows up on my computer as Removable Disk like it did when i first put the ROM on there. I think my best bet would be pushing the ROM via adb, but could you explain more on how to do so?
Click to expand...
Click to collapse
No he said he didnt know how.
Sent from my Amazon Kindle Fire using xda app-developers app
Nv ur right
If your having trouble when you go to mount in twrp make sure there are no checks in the boxes of data and system then select mount you should then see your sdcard contents likely you will only see the twrp folder if not you will need to adb push a ROM zip file and a gapps zip to your sdcard to have something to flash as Josepho instructed above if you can't figure out how to do this maybe someone can assist via teamviewer to do so
Josepho1997 said:
Copy the tools folder from KFU to your local disk.
Then copy your ROM to your local disk.
Then open cmd and type:
cd c:\tools
adb
adb push c:\ROM'SNAME.zip /sdcard
Then flash it in TWRP(Select Install and then select your ROM)
Note that you do need to have the drivers for your kindle fire installed.
Sent from my Kindle Fire using xda premium
Click to expand...
Click to collapse
Okay i typed
cd c:\tools then
adb then
adb push c:\cm9-02-24.zip /sdcard
^Is there supposed to be a space?
and it said
"daemon not running. Starting it now"
"daemon started successful"
"error: device not found"
I think its because its not connected through adb? In order for this to work my adb status must be online, correct?
Josepho1997 said:
Copy the tools folder from KFU to your local disk.
Then copy your ROM to your local disk.
Then open cmd and type:
cd c:\tools
adb
adb push c:\ROM'SNAME.zip /sdcard
Then flash it in TWRP(Select Install and then select your ROM)
Note that you do need to have the drivers for your kindle fire installed.
Sent from my Kindle Fire using xda premium
Click to expand...
Click to collapse
Okay, i typed
cd c:\tools
adb
adb push c:\cm9-02-24.zip /sdcard
There is a space between .zip and the / right?
Well anyways, the first time i attempted this, it came back with "error: device not found"
I later realized my adb status was offline, so i tried letting it boot through, but since i have no rom on there, it was just a black screen, but i rechecked my device stats and it said
"adb status: online
boot status: unknown" i then re-attempted to push the rom, but it took a few seconds and came back with a different message
"failed to copy 'cm9-02-24.zip' to '/sdcard' : is a directory"
I know the boot status is supposed to be like, 4000, but i cant figure out how to get it to say that. In TWRP, i can click mount and i have the four options for my cache, sdcard, so on and so on. Should i tick the sd card to where it says "mount sdcard" or "unmount sdcard" and should that be the only thing i mount or should i also mount something else with it? Im sorry for being such a pain in the you know what, but thanks for all yalls help.
Thepooch said:
If your having trouble when you go to mount in twrp make sure there are no checks in the boxes of data and system then select mount you should then see your sdcard contents likely you will only see the twrp folder if not you will need to adb push a ROM zip file and a gapps zip to your sdcard to have something to flash as Josepho instructed above if you can't figure out how to do this maybe someone can assist via teamviewer to do so
Click to expand...
Click to collapse
Okay, when i mount, it should show up under my computer folder im pretty sure, because i dont know where else it would come up. If that is the case, my kindle doesnt like to connect to my computer...The only time it comes up is when im in twrp and it says "Removeable Disk (E' But when i open it, there is absolutely nothing inside where all my files used to be...
Thepooch said:
If your having trouble when you go to mount in twrp make sure there are no checks in the boxes of data and system then select mount you should then see your sdcard contents
Click to expand...
Click to collapse
Is there any other possible way to see if my /sdcard is mounted???
i need help guys, please!
Jarodroll said:
Okay, i typed
cd c:\tools
adb
adb push c:\cm9-02-24.zip /sdcard
There is a space between .zip and the / right?
Well anyways, the first time i attempted this, it came back with "error: device not found"
I later realized my adb status was offline, so i tried letting it boot through, but since i have no rom on there, it was just a black screen, but i rechecked my device stats and it said
"adb status: online
boot status: unknown" i then re-attempted to push the rom, but it took a few seconds and came back with a different message
"failed to copy 'cm9-02-24.zip' to '/sdcard' : is a directory"
I know the boot status is supposed to be like, 4000, but i cant figure out how to get it to say that. In TWRP, i can click mount and i have the four options for my cache, sdcard, so on and so on. Should i tick the sd card to where it says "mount sdcard" or "unmount sdcard" and should that be the only thing i mount or should i also mount something else with it? Im sorry for being such a pain in the you know what, but thanks for all yalls help.
Click to expand...
Click to collapse
Try "adb push c:\cm9-02-24.zip /sdcard/" instead, I mean, since /sdcard is a directory...it sounds like it is trying to prevent you from overwriting a directory with a same-named file.
Also, it looks like your Fire is visible to ADB, but to be sure try "abd devices" and see if your Fire's serial number shows up. Probably does once you boot it through to the point where you get the error message about the directory.
Deleted everything on kindle fire hd 8.9
Hi Guys, i have been a complete idiot, managed to root kindle fire hd 8.9 installed twrp then found I couldn't add custom roms as computer was no longer seeing KF. couldn't mount usb. after two weeks of frustration and trying all combinations of installing and un-installing drivers etc got frustrated and instead of factory wipe I deleted everything. KF now doesn't show up on computer, turns on and stops at logo. occasionally unplug usb and plug back in it briefly shows up as Jem-tv- or something. so does it go in the bin or can it be rescued.
Mediamania
Please help me unbrick my soft bricked Asus SL101 tablet.
I'm normally pretty good at rooting and upgrading android phones etc to custom ROMs and decided to install CM9 on it recently.
Rooted using PERI
Installed CM9 using PERI
Rebooted into CM9
Screen appeared telling me it cannot access my encrypted user data partition
Gave it permission to re-format that partition (I had nothing on it that wasn't on my PC anyway)
Tablet reboots and returns to screen asking to format encrypted partition
(rinse and repeat)
From everything I have read the solution seems to be re-installing the factory Asus ICS firmware, logging into the encrypted partition and unencrypting it. However, all of my attempts to install the stock Asus ICS firmware (9.2.1.27) have failed as follows.
Code:
[B]assert failed: write_raw_image ("/tmp/blob", "staging"[/B])
I researched that and found that I could create a dummy "staging" through ADB.
(post 3 of this thread: http://forum.xda-developers.com/showthread.php?t=1235724)
So I set up Android SDK and ADB, but running the commands produces no result.
Code:
C:\Users\Joe\adb shell
~# mount /dev/block/mmcblk0p4 /staging
mount /dev/block/mmcblk0p4 /staging
~# exit
exit
I then run the zip install in Rogue again, but get the same result.
Any help will be greatly appreciated.
Today I tried to enable ART on my S3 Mini running Maclaw's CM11. After the phone was shut down, the CM loading circle stayed there forever and the phone didn't boot.
To fix this you can boot the phone into recovery (I'm using CWM) and use ADB to revert the runtime back to Dalvik.
There are 3 ways to do this:
Use the following manual instructions
Download the second attachment and run the batch file, while the phone is connected using a USB cable and in recovery mode. For this you need USB drivers installed.
Download the first attachment and flash it in recovery
Manual instructions
Boot to recovery
Open the shell
Code:
adb shell
Now, while in the shell, the data filesystem must be mounted.
Code:
mount /data
Still staying in the shell, use the following command to set Dalvik as the runtime of choice.
Code:
setprop persist.sys.dalvik.vm.lib libdvm.so
Now the /data-filesystem can be unmounted using
Code:
umount /data
Type exit in the shell to exit ADB shell.
Reboot the phone and it should get past the loading circle again
If anything goes wrong, I'm not responsible
Very good idea. Thanks
I am not sure, but maybe it is possible to set property from recovery update script?
Such script, downloaded onto phone and accessible from recovery would be better, than PC with USB drivers and a cable
piskor said:
Very good idea. Thanks
I am not sure, but maybe it is possible to set property from recovery update script?
Such script, downloaded onto phone and accessible from recovery would be better, than PC with USB drivers and a cable
Click to expand...
Click to collapse
Thank you for the idea, implemented it now and added to the OP.
dextrey said:
Thank you for the idea, implemented it now and added to the OP.
Click to expand...
Click to collapse
Excellent, thanks
Updated to mount the /data filesystem directly using the fstab entry. Also changed the recovery-flashable .ZIP to use a temporary BusyBox for all commands, because I'm not completely sure about the filesystem differences between different ROMs and recoveries (the locations of binaries such as mount and umount)
Thanks!!!
Very useful!!
Thanks, this worked. I was on CM11 nightlies and read an article about ART and switched it from Dalvik, phone app crashed and wouldnt let me boot in. Although I'm using HTC One, this method worked for me.
For TWRP users, boot into recovery and go into Advanced, and then use terminal to command the type the main line to switch to Dalvik, no need to adb shell and mount data.
Fixed my HTC ONE m7 that got brinked when selecting ART.
dextrey said:
Today I tried to enable ART on my S3 Mini running Maclaw's CM11. After the phone was shut down, the CM loading circle stayed there forever and the phone didn't boot.
To fix this you can boot the phone into recovery (I'm using CWM) and use ADB to revert the runtime back to Dalvik.
There are 3 ways to do this:
Use the following manual instructions
Download the second attachment and run the batch file, while the phone is connected using a USB cable and in recovery mode. For this you need USB drivers installed.
Download the first attachment and flash it in recovery
Manual instructions
Boot to recovery
Open the shell
Code:
adb shell
Now, while in the shell, the data filesystem must be mounted.
Code:
mount /data
Still staying in the shell, use the following command to set Dalvik as the runtime of choice.
Code:
setprop persist.sys.dalvik.vm.lib libdvm.so
Now the /data-filesystem can be unmounted using
Code:
umount /data
Type exit in the shell to exit ADB shell.
Reboot the phone and it should get past the loading circle again
If anything goes wrong, I'm not responsible
Click to expand...
Click to collapse
Thank you, thank you, I'm in great debt for this.
Can recommend the method if you are running viperOne 6** on a HTC one m7 (bulletproof kernel).
NB:
My ADB was totally broken, but I wrote all commands in the TWRP terminal window, and it reverted my phone back to dalvic from ART!
using terminal in ubuntu with adb. can access root with phone booted fine. Need to access su with phone in recovery as im attempting to mount internal storage to perform emergency data recovery. Im using the guide from MohammedAG's blog. (which seems to have been taken down as of yesterday....)
Is this possible? phone is rooted with safestrap 3.72 installed.
Im able to get the drive to mount temporarily (with phone booted), with this command:
echo /dev/block/platform/msm_sdcc.1/by-name/userdata > /sys/devices/virtual/android_usb/android0/f_mass_storage/lun0/file
it shows the files and directories for between 2-10 minutes then the phone will reboot. Want to create a drive image using GNU ddrescue.
Any help/thoughts/insight would be greatly appreciated.
Success!!!!
Ok so i figured out another way. I was unable to access root from recovery...I would get error "CANNOT LINK EXECUTABLE: could not load library "libc.so" needed by "/sbin/sh"; caused by library "libc.so" not found"
But I DID have access with phone booted. I was working in unbuntu terminal as MohammedAG suggested as Windows cannot read ext3 partitions. This would work temporarily as I mentioned above but would then crash and reboot the phone. Due to the system being double mounted?? i think...
So i tried it in windows, the command worked I saw the drive! It asked me to format so i could use the drive...Cancel. The drive was now still visible(but not usable by windows) as a logical drive.
So using iRecover (diydatarecovery.nl) which supports ext3/4 drives I was able to perform recovery on the device and create an image file just to be safe.
Recovered a ton of files! Awesome!
In recovery mode I am not able install any ROMS, theres the error Failed to mount /efs (Invalide argument)
I can only flash stock roms using odin, everything works on stock roms except for the wifi, after connecting/disconnecting multiple times, the wifi stops responding and wont work in the future
---------------------------------------------------------------------------------------------------------------------------------------------
(( SOLVED ))
First thing you should do, is to backup your EFS if you still have it.
I had mine but it wasn't mounting properly.
In order to back it up, please download terminal emulator on a rooted device and follow this video
I would try to back it up, even if you think the efs is messed up... worst case scenario is you end up where you started, not worse off.
---------------------------------------------------------------------------------------------------------------------------------------------
Your device needs to be rooted.
1.) Download SDK tools here - Scroll down to the bottom and "Get just the command line tools"
2.)Install TWRP , Find your device, download the .tar and flash it using ODIN
Boot in to recovery, in TWRP you want to go to mount, make sure system, esf are checked.
3. If you installed SDK tools, go to c:\android tools\SDK tools. hold shift and right click on the area inside the folder and select run command line from here.
4.) In cmd, type
Code:
ADB devices
ADB Shell
SU
mke2fs /dev/block/mmcblk0p10
mount -w -t ext4 /dev/block/mmcblk0p10 /efs
5.) You should be good!!!