So I was about to flash a ROM and I had too many things on storage and cleaned and wiped everything. I then went on to use Format Data, hoping that it will only delete files and not the OS too. So now it deleted the OS and I'm stuck between bootloader or recovery mode and I can't seem to find a way to copy the zip file to my internal storage. Tried adb using cmd but it's not recognized and I'll have to dowload Google's SDK. This in turn will take about 2 hours and I'd really like to fix the problem ASAP. Anything I could do please?
Thanks and much appreciated.
You could always go to recovery, Mount your sd card and copy the file that way. Or setup fast boot and flash the stock image, or even just push the rom file through adb. You have a few options.
Sent from my Nexus 4 using Tapatalk 4 Beta
eqjunkie829 said:
You could always go to recovery, Mount your sd card and copy the file that way. Or setup fast boot and flash the stock image, or even just push the rom file through adb. You have a few options.
Sent from my Nexus 4 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Adb-toolkit is in the folder but cmd is not recognizing it unfortunately. And through TWRP I have no option to mount USB... usb-otg doesn't work...
Anyone please? I have no idea what to do at this point and I'm pretty much phone-less...
Related
hi can i have some help?
stuck on the adb push part, cmd window says failed to copy ____ to _____ read-only file system.
any idea how to fix this?
(from step by step rooting guide for 9020a)
I assume you mean the "adb push su-2.3.6.1-ef-signed.zip /sdcard/su-2.3.6.1-ef-signed.zip" part. Maybe you forgot the /sdcard at the beginning, otherwise no need to worry about adb anyway. Just copy that file over to the sdcard by any means you like (adb, mount usb storage, etc).
However, i would be using a newer su zip from the official web page, just to save hassle if you are using ICS. Guaranteed to work
If you have already flashed the recovery... easiest way is just to boot into recovery then mount the USB storage and copy it that way. Then unmount and flash the zip while still in recovery.
Sent from my Nexus S using XDA App
thanks for the help!
sorry to ask another question (first time rooting), but I can't find any sdcard folder after i go into usb mass storage?
and the new su zip will work on 2.3.6? (planning on using cm9)
New su works on 2.3.6 fine. Mount USB storage is the sdcard partition, so anywhere in there.
So I downloaded aokp_grouper_PUB to flash and I decided to format /system in recovery before I did a nandroid back up *facepalm
Now I cant load the rom or anything... I been trying to mount my sd card to try and load another rom into the sdcard but I can't seem to do it...
I can use adb but my memory with adb is pretty bad.
When I typed command, adb devices, my n7 is recogonized and is in recovery.
Any help is appreciated
hongphooey said:
So I downloaded aokp_grouper_PUB to flash and I decided to format /system in recovery before I did a nandroid back up *facepalm
Now I cant load the rom or anything... I been trying to mount my sd card to try and load another rom into the sdcard but I can't seem to do it...
I can use adb but my memory with adb is pretty bad.
When I typed command, adb devices, my n7 is recogonized and is in recovery.
Any help is appreciated
Click to expand...
Click to collapse
Here's a link to another post I made regarding basically the same thing. Hope this helps ya out http://forum.xda-developers.com/showthread.php?p=36454180. Use the adb useful commands
Sent from my Nexus 7 using xda premium
Thanks man, I used adb push rom.zip /data/media
and it all worked out great.
hongphooey said:
Thanks man, I used adb push rom.zip /data/media
and it all worked out great.
Click to expand...
Click to collapse
Good stuff!
Sent from my Nexus 7 using xda premium
I did sift reset but didnot worked. he samsung kies is not detecting my phone, when connected. can you please help me? I think i have access to SD card only ( i mean any boot up from SD card can help, i guess)
Hi,
I will have your thread moved to your device section. You will need to register on XDA to respond to any replies you get.
Good luck!
There are a few ways to make your phone boot:
1. If you have knowledge of ADB pull the build.prop from your device onto your desktop and edit it.
2. Re flash stock ROM.
3. If you have TWRP recovery, just pull the build.prop from any Touchwiz based rom zip and put on your SD card, then move it to /system/.
This_Guyse said:
There are a few ways to make your phone boot:
1. If you have knowledge of ADB pull the build.prop from your device onto your desktop and edit it.
2. Re flash stock ROM.
3. If you have TWRP recovery, just pull the build.prop from any Touchwiz based rom zip and put on your SD card, then move it to /system/.
Click to expand...
Click to collapse
=============================================================================
Thanks Guyse for your prompt reply.
I dont have knowledge on ADB and i want to flash. Can i jusy copy the ZIP file on SD card and boot the device using " Apply update fromexternal Storage option?
bdvkishore said:
=============================================================================
Thanks Guyse for your prompt reply.
I dont have knowledge on ADB and i want to flash. Can i jusy copy the ZIP file on SD card and boot the device using " Apply update fromexternal Storage option?
Click to expand...
Click to collapse
Oh, looks like you have stock recovery. You need to flash a custom recovery before you can install ROM zips.
Hi guys,
I need some hints on what has changed from Android < 5 to Lollipop when it comes to internal storage.
I have booted my Nexus 4 running Lollipop into ClockworkMod recovery and mounted the internal storage.
Then I did an "adb push" of files that I have backed up before to restore those onto the internal storage.
Once that was done I have opened a shell and changed ownership back to media_rw:media_rw and also
checked POSIX permissions to be correct.
Basically this is what I have done so many different times on different Android devices.
Once I have booted back into the system ... I could not access any of those files and directories.
I assume that there was something added on top of plain POSIX access control. A SELinux thing or something
like ACL or stuff, or maybe a database referring to files stored on /sdcard.
Anyway what can I do in recovery mode to make manually copied files and directories available in the system?
Any help would be appreciated!
Thanks in advance!
/Al
I had this problem too but all I could do to correct it was to reflash my ROM.
Sent from my Nexus 4 using Tapatalk
GorfDroid said:
I had this problem too but all I could do to correct it was to reflash my ROM.
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
Well finally I went back to 4.4.4 and copied the files back to SD card via adb. I hope the OTA will do everything for me.
But still I would like to understand how it work. This is what I am looking for.
If you are running Lollipop and create a file on SD card it looks exactly the same in Recovery mode. Same user, same group and same POSIX permission ... but still different in some way. How?
My phone was taking too long to boot up yesterday after installing latest franco kernel so I have decided to format and clean flash rastapop. After everything's up and running, I tried to access my internal storage via USB on Windows 8 but when I click into the drive it was completely empty. I checked the storage space on my phone to make sure that I didn't accidentally wiped the internal storage and it showed 5.1GB out of 12.92GB. I've also used ES File Explorer to see if I can access storage directly from the phone but it showed the same thing - completely empty. Wifi sharing didn't help either. One weird thing was that I could see the files when I booted into the recovery mode. I have tried almost everything including clean flashing the rom again. I really don't want to format my internal storage. Please help. Thanks!
Found the solution: http://forum.xda-developers.com/showpost.php?p=56782014&postcount=7
Simply just type in these in adb:
adb shell
su
restorecon -FR /data/media/0
For a permanent solution flash stock boot.img again. Otherwise you face the same problem when flashing any other custom kernel again.
brownmonkey300 said:
For a permanent solution flash stock boot.img again. Otherwise you face the same problem when flashing any other custom kernel again.
Click to expand...
Click to collapse
What? Not true
Sent from my Nexus 9 using XDA Free mobile app