Hi, I want to transfer a file called undo.zip from my computer to my phone, but it is bricked.
The file is in the external-sd, but in the recovery I can't flash it because my phone won't acces the external-sd in recovery mode.
The file is a zip to be flashed in the internal sd OR I can also have a framework to be moved directly to system/framework. Both ways should FIX my brick.
Okay, I can enter in recovery and download mode, but I don't want to wipe it or to change the ROM.
What I tried to do is:
Flash the file on the external sd on the recovery mode: Transfered the file to the external sd with an adapter... The recovery option for mount external sd in mounts and storage WON'T let me mount it. I think it's because of the kernel (I've got a DOC's kitchen rom with speedmod, but I installed Super Optimized Kernel and overclocked my phone up to 1.2GHz), so I can't mount the external-sd on the recovery.
So the other only solution is
Transfer the file to the internal sd with ADB
The file is in
C:\android\android-sdk-windows\undo.zip
And I have to move it to the ROOT of the Sdcard, but I don't mind where do I move it if it is on the internal sdcard.
This is what I exactly do:
-Connect the phone on the USB on recovery mode
-Open CMD.exe (I'm on wvista) and type adb.exe in the correct folder. A lot of scripts appear, so I suposse I'm doing it good.
-In adb, type ums_enable. DOES NOT WORK (does not recognize the command). I can't activate USB connection in that way.
-In adb, push my framework-res.apk to system/framework. Superuser error, DOES NOT WORK and my phone is rooted. I could do adb shell and then su, but I can't accept the su request in my phone because... well, it's on the recovery!
LAST AND ONLY SOLUTION: In adb, push the file to my sdcard root
--------------------------------------------------------------------------------------------------------------------------------------------------
SHORT STORY:
All I do is "adb push C:\android\android-sdk-windows\undo.zip sdcard", but it gives me error because it's a folder. So, YES, it's a folder because I want to move it to that folder! If I try to move it to a folder in the sdcard, for example by typing "adb push c:\android\android-sdk-windows\undo.zip sdcard/foldernameIwant" it gives me the same error.
------------------------------------------------------------------------------------------------------------------------------------------------
PART 2, IGNORE THE TEXT ABOVE
So, I managed to be able to move files to my sd on the recovery, but when I want to restore my framework by installing a JS5 stock theme, phone won't de-brick even if it has got a new stock framework that should make it boot... Any help? I'm sure the problem is on the framework-res, but it's now restored by another from a JS5 stock theme (I'm using a self-made JS5) and it continues bricked...
Related
Hello,
I don't know how, but I managed to end up with a system that has /dev/block/mtd* wiped clean. All the partitions contain valid yaffs2 file systems, but all they contain is a lost+found directory.
This includes the recovery partition, which I guess is the reason why I am not able to enter recovery or download mode anymore. No matter how I boot, the phone display only shows the cyanogen^mod splash screen.
I still have root access to the device using adb shell, and I can call flash_image and mount /sdcard as well as /dev/mtd*.
How do I best recover from this situation?
Can I download the missing contents from somewhere? I wasn't even able to find a suitable rescue image, even the clockwork recovery images from koushikdutta.com come as .zips which have to be properly installed.
And is it sufficient to mount mtdX and extract the files there, or do I have to use flash_image?
Thanks for any suggestions!
Here is how I recovered:
Download SpeedMod Kernel
Create a nandroid backup on a working phone, copy that over to the broken one
Copy zImage from SpeedMod kernel to SD on broken phone with adb
Enter shell mode on phone
Look into misc/recovery.fstab to figure out the name of the sdcard block device
Mount sdcard with `mount [blockdev] /sdcard`
Flash zImage with `flash_image boot /sdcard/zImage`
Flash nandroid backups with `flash_image {system,cache,datadata} /sdcard/{system,cache,datadata}.img` (but not data)
Leave the phone without battery for at least 1 and at most 6 hours (my phone appeared completely dead after this operation, not even adb shell access, so I went to bed frustrated)
Now you can boot into download mode again using "adb reboot download" (which didn't work when running the CM7 kernel)
Use One Click Odin to revert to stock firmware
Install 3ButtonFix to get combos working again
Note that the original problem that caused all the trouble was that flashing the stock ROM with Odin One-Click disables the 3 Button combos. You have to use the 3ButtonFix to get it working again.
When i type the dd if=/data/recovery.img of=/block/mmcblk0p6 bs=4096 to flash over the clockworkmod, into my command promt it says 'cannot open for read: No such file or directory' and i dont know what im doing wrong.
I mean everything else seemed to workout fine. i downloaded the recovery image it said to save it but it was already saved to my computer after i downloaded it so i dont know if this could be the problem.
Then i used the adb push recovery.img/data command to push the recovery image to my phone, i think this might be where i messed up. After i put in the command a long list of text pops up on the command prompt. It starts out showing 'Android Debug Bridge version 1.0.26' then is followed by a long list of adb commands. Idk know if this is what its supposed to show.
Next i did the adb shell, su, dd if=/dev/block/mmcblk0p6 of=/sdcard/mmcblk0p6.backup bs=4096 command and that worked fine it said 2560+0 records out, 2560+0 records in 10485760 bites transfered in 0.413 secs and i actually found that file on my sdcard. So i think i did that right.
Next i tried to use the command 'dd if=/data/recovery.img of=/block/mmcblk0p6 bs=4096' and like i said earlier it just says 'cannot open for read: No such file or directory'
Lastly i tried the rm /data/recovery.img command and it said rm failed for /data/recovery.img, No such file or directory in the command prompt.
Im sorry i am new at this but i thought i followed the directions perfectly and any help anyone could give me would be greatly appreciated.
First off, before someone else says it, you shouldn't start a new thread for something we already have a topic for. But anyways,
Sounds to me like recovery.img never got pushed to /data. Not sure if its a typo in your post but 'adb push recover.img/data' should be 'adb push recovery.img /data'. The space is important. On your phone use a root file explorer and go to your /data partition and see if recovery.img is there. You may need to either change permissions for /data or just put recovery.img on your sdcard and move it to /data with a root explorer.
Sent from my LG-P925 using Tapatalk
Well im sorry im new to this kind of thing, i didnt want to make anyone mad i just wanted some help and i apologize if ive ticked somone off. How would i change the permissions for the data? And could you tell me how to use the root explorer to put the recovery image in the right place? Again i appreciate any help you can offer.
Is recover.img in the same folder as adb? Because the instructions assume your recovery.img is in the same folder you are working from. So if you have to cd to your adb folder to use adb then recovery.img should be in that folder as well. Look at your cmd window, whatever directory/ folder it says you are in that is where you should put recovery.img.
If you saw a bunch of commands it means the .img did not go through your command did not work. You dont have the recovery.img in /data either put the file on your sdcard and use a root explorer to move it to /data or try the adb push again, you most likely made a typo or something.
You would put recovery.img on your sdcard through your computer. Open root explorer and navigate to your sdcard, long press on the recovery.img select move, go to/ data on the root of the phone, not the one on either sdcard it MUST be /data not /mnt/sdcard/data or anything like that once there paste file to /data and finish up in adb shell.
Alright i copied the recovery image to the /data folder and finished up in command prompt and everything worked out like it was supposed to. what was i supposed to do next to put it into cwm recovery mode? I held power, volume down, 3d button but i just went into normal recovery mode. then i went to rom manager to try and put it into cwm recovery that way but it just rebooted my phone. And when i went back into the /data folder i couldnt find the recovery image there anymore and i did a search on my root explorer and couldnt find it anywhere.
Hold vol down + 3D + power when lg logo appears release power but keep vol down +3D held down until recovery pops up. If you still don't boot into cwm try flashing recovery.img again. Do NOT use rom manager at all to install cwm on this phone.
Well ive tried to take the recovery image from the sd card to the /data folder but when i run 'rm /data/recovery.img' on the command prompt then reboot my phone, i turn it off then try and put it in recovery mode but its just regular recovery mode not cwm recovery mode. And everytime i run the 'rm /data/recovery.img' when my phone boots back up the recovery image is no longer in the /data folder or anywhere. But if i dont run the 'rm /data/recovery.img' after moving the recovery image to the /data folder it stays in the folder. Is it supposed to dissapear from the /data folder?
And i tried putting the recovery image in the same folder as abd which is the platform tools folder then flash it over and i got the same message. (cannot open for read: No such file or directory.)
Im sorry for all the questions and I am thankful for your help. I feel like i cant be the only person having this problem, well i hope im not that would make me feel really stupid. Thanks.
powers.jereme said:
Well ive tried to take the recovery image from the sd card to the /data folder but when i run 'rm /data/recovery.img' on the command prompt then reboot my phone, i turn it off then try and put it in recovery mode but its just regular recovery mode not cwm recovery mode. And everytime i run the 'rm /data/recovery.img' when my phone boots back up the recovery image is no longer in the /data folder or anywhere. But if i dont run the 'rm /data/recovery.img' after moving the recovery image to the /data folder it stays in the folder. Is it supposed to dissapear from the /data folder?
And i tried putting the recovery image in the same folder as abd which is the platform tools folder then flash it over and i got the same message. (cannot open for read: No such file or directory.)
Im sorry for all the questions and I am thankful for your help. I feel like i cant be the only person having this problem, well i hope im not that would make me feel really stupid. Thanks.
Click to expand...
Click to collapse
rm is the command to remove. So yes, recovery.img is supposed to disappear after that command. Put it back on /data and run the whole process from the CWM thread again making sure you do every step. Sounds like you may have accidentally skipped a step.
Sent from my LG-P925 using Tapatalk
Double post.
Ugh...keep selecting quote instead of edit on Tapatalk...Triple post...
Alright ill try that again, so i should put the file back on the /data folder and then still do the step where you try to flash over cwm from the cwm thread, even though its already there? Thanks
powers.jereme said:
Alright ill try that again, so i should put the file back on the /data folder and then still do the step where you try to flash over cwm from the cwm thread, even though its already there? Thanks
Click to expand...
Click to collapse
Yea just do it all again. Worst case is you flash cwm back over cwm
Sent from my LG-P925 using Tapatalk
I got it to work Urabewe was right i just needed to put the recovery image in the correct folder and everything worked perfect. Thanks guys.
Hello...i've search4ed and searched and no answer pertains to my problem that I can find. I followed this guide to get CM7.2 loaded on my 16gb sandisk sd card: http://forum.xda-developers.com/showthread.php?t=1000957 The gapps I'm using the CM7 download link. The CM7.2 rom is the newest one available on the download link
Everything loaded smooth and works great except when I get to the part of installing gapps, I reboot into recovery mode (blue penguin with scrolling writing) and everytime it cannot find gapps installer so it ignores it!! I don't know what else to do here.. I've verified the hash using md5sum and it matches... I have my gapps.zip file located on the ROOT of my sd card /sdcard/gapps.zip. I've also tried putting gapps in /sdcard/boot. I've also tried changing the name to gapps-update.zip, update-gapps.zip, gapps-gd....etc.zip, etc etc etc. No matter what or where I put the file it isn't found.
When I boot the NC i can get to a boot menu from there, i've tried all combinations of booting (internal, sd, normal, etc etc). I've tried installing through boot manager and that doesnt work. It reboots to recovery mode and still doesn't find the file. I've flashed clockwork in boot manager and that didn't help anything.
I'm not sure what I just did, but i rebooted and now I have a "burrito manager" icon. I tried installing through that and no go. Don't know what else to do.
I DO have wifi setup/connected.
*EDIT... not sure if it matters, but I do seem to have an issue. I'm connected to wifi but NTP isn't updating my clock settings. It is setup in settings to auto update the date/time using network settings and it doesn't update. Could this be an issue with getting market to show up if the time is wrong??
Its most likely you are not placing gapps in the root of the boot partition... try this:
if adb works for you:
adb shell mkdir /sdcard/boot
adb shell mount /dev/block/mmcblk1p1 /sdcard/boot
adb push ***GAPPS INSTALLER*** /sdcard/boot
then when you reboot to sd recovery mode it will see the gapps installer.
DizzyDen said:
Its most likely you are not placing gapps in the root of the boot partition... try this:
if adb works for you:
adb shell mkdir /sdcard/boot
adb shell mount /dev/block/mmcblk1p1 /sdcard/boot
adb push ***GAPPS INSTALLER*** /sdcard/boot
then when you reboot to sd recovery mode it will see the gapps installer.
Click to expand...
Click to collapse
Hello...thanks for the reply! But I'm a little confused what you mean? I manually put the gapps.zip file on /sdcard/gapps.zip AND also copied to /sdcard/boot/gapps.zip. The file is there. What is the filename supposed to be??? I've tried gapps-...zip, update-gapps...zip, gapps.zip, etc.
Is there something that adb does that copy on the terminal doesn't do??
See attached screenshot, the file is there. For some reason the installer script in recovery mode isn't finding it. That's why i was asking what filename it's looking for?
ballgum said:
Hello...thanks for the reply! But I'm a little confused what you mean? I manually put the gapps.zip file on /sdcard/gapps.zip AND also copied to /sdcard/boot/gapps.zip. The file is there. What is the filename supposed to be??? I've tried gapps-...zip, update-gapps...zip, gapps.zip, etc.
Is there something that adb does that copy on the terminal doesn't do??
See attached screenshot, the file is there. For some reason the installer script in recovery mode isn't finding it. That's why i was asking what filename it's looking for?
Click to expand...
Click to collapse
Do not put the file in 'sdcard'. It needs to go in the boot partition like dizzy said. Take the card out of the nook and put in your PC. That will show the boot partition. Put the gapp file there. Make sure the name starts with gapps-gb-. Put the card back into the Nook and reboot to recovery like before.
leapinlar said:
Do not put the file in 'sdcard'. It needs to go in the boot partition like dizzy said. Take the card out of the nook and put in your PC. That will show the boot partition. Put the gapp file there. Make sure the name starts with gapps-gb-. Put the card back into the Nook and reboot to recovery like before.
Click to expand...
Click to collapse
That worked! thank you very much...
delete
deletedeletedelete
Try a new cable/port/computer. Also move to twrp and install a rom which works with it, I didn't know some ROMs won't work with it.
There is an option in CWM to mount your device as USB, even when in recovery. I think its in advanced, do that. Then ou can copy the rom file to the device and flash it by selecting as zip from sdcard.
Basically I accidentally factory reset my phone from the bootloader (i was supposed to enter recovery but went 1 option down and pushed the power button then it started the reset).
Now when I flashed the ARHD rom again (which was working perfectly fine before), i cannot take pictures, it says "unable to save file to sd card due to insufficient file permissions". If I open file manager it shows nothing, but if I go to the settings it shows the SD card only has 5GB left.
I can also open TRWP's file manager and go to the /sdcard directory and see all my pictures etc there on the sdcard.
When I plug in the HTC One via USB to my laptop I cannot access the sdcard contents...
I even tried to push some files via adb but it says "remote object "file name" does not exist" when it definitely does because I can see it on the TRWP file manager.
Any help is very much appreciated, I tried full wiping and reflashing but it still exists...
Is there any way I can fix this without losing all my sdcard contents?
Help is very much appreciated!
Lanky09 said:
Basically I accidentally factory reset my phone from the bootloader (i was supposed to enter recovery but went 1 option down and pushed the power button then it started the reset).
Now when I flashed the ARHD rom again (which was working perfectly fine before), i cannot take pictures, it says "unable to save file to sd card due to insufficient file permissions". If I open file manager it shows nothing, but if I go to the settings it shows the SD card only has 5GB left.
I can also open TRWP's file manager and go to the /sdcard directory and see all my pictures etc there on the sdcard.
When I plug in the HTC One via USB to my laptop I cannot access the sdcard contents...
I even tried to push some files via adb but it says "remote object "file name" does not exist" when it definitely does because I can see it on the TRWP file manager.
Any help is very much appreciated, I tried full wiping and reflashing but it still exists...
Is there any way I can fix this without losing all my sdcard contents?
Help is very much appreciated!
Click to expand...
Click to collapse
Try this, using a Terminal emulator on your phone. (you can download one from the play store if you need one) Enter these commands
Code:
su
restorecon -FR /data/media/0
Reboot and check sd. If that fails you should be able to fix it with e2fsck and an adb command window but try the terminal emulator first. :good: