Database Users

Cant flash another recovery image!!!

It used to work along time ago, this is my new refurb that i rooted a few days ago, im on the 1.5.2 recovery image and im trying to flash the new 1.6 but i dont what the crap im doing wrong. i keep getting error messages i used to be able to do this in 10 seconds. i already have the image on the root of my card can anyone help.
Plus those bastards sent me a refurb that has dead pixels that are white in the blk screen wtf sprint, thats pure whack customer service.
EDIT: problem solved, i was trying this whole time to flash another recovery inside recovery, i actually left the phone on and pushed the recovery lol no more ghanja.

see the # symbol when you enter teh shell? that means you have root already and su isn't necessary. Also try unplugging then plugging back in, the phone from the usb. The file not found error probably means that the sd card is mounted. do an ls from /sdcard to make sure

Also try "adb mount" over "mount -a".

DISABLE usb debugging.
i know, its the little things we overlook. i just did this last night and forgot to disable it.

i did and its still not working.........i dont understand, let me upload another pic. and i already tried adb mount and fastboot still no luck

i kept getting these errors what i did and found easiest with no errors is save the recovery in the sd card. download terminal emulator then in terminal emulator su then enter
then type flash_image recovery /sdcard/nameofimage.img
someone please make sure my prompts are right as i hadn't done it in awhile.

I am trying to do the exact same thing and getting the exact same errors. The file is definitely on the sd card, I am typing the name correct, and USB debugging is off.
Anyone have any other ideas or ways to update to the newest recovery image?

Maitiu said:
I am trying to do the exact same thing and getting the exact same errors. The file is definitely on the sd card, I am typing the name correct, and USB debugging is off.
Anyone have any other ideas or ways to update to the newest recovery image?
Click to expand...
Click to collapse
hahaha dude it used to work perfectly, i been trying and trying for the past couple of hours. (scratching head)

Demoyo23 said:
hahaha dude it used to work perfectly, i been trying and trying for the past couple of hours. (scratching head)
Click to expand...
Click to collapse
you try using the terminal emulator method directly on the phone? only way i can get to work and works everytime.

I'm working on that now, but I tried that a few days ago and got different errors, I'll post what the specific error was when I get there in a few minutes. For some reason Superuser Permissions is force closing right now.
Yeah even from the terminal emulator, I get a "not found" error.

I just updated today from RA1.5.2 to RA1.6.2. I used the Recovery Flasher to update to the newer version as that is what I had originally used to get 1.5.2 installed.
These were original instructions from theunlockr .com:
7. Save both the Recovery-RA-HEROC-v1.5.2.img and the FlashRec.apk to your computer, then copy them both to your SD card (do NOT put them inside any folders on the SD card, just put them on the SD card itself).
8. Unplug the phone from the computer once they are downloaded to the SD card.
8. Goto the Market and download Linda File Manager or any file manager program if you do not already have one.
9. Open the file manager and goto SDCard and then find the FlashRec apk file and click it. If asked tell it to use Package Installer to open it. It should automatically install the apk.
10. Open the FlashRec program and click on Backup Recovery Image and wait for it to finish.
11. Once done, click on the empty text box in the FlashRec program and type (again remember we have replaced the recovery image from the one in the video so type what is written here, NOT what is written in the video!):
/sdcard/recovery-RA-heroc-v1.5.2.img
Then click on the Flash Custom RecoveryImage button and wait for it to finish.

Just barely.

That's still not working flashrec won't back up it keeps saying failed. And it won't flash a custom img. This refurb is cursed I had no problem doing it all on my original.
-------------------------------------
Sent via the XDA Tapatalk App

Demoyo23 said:
It used to work along time ago, this is my new refurb that i rooted a few days ago, im on the 1.5.2 recovery image and im trying to flash the new 1.6 but i dont what the crap im doing wrong. i keep getting error messages i used to be able to do this in 10 seconds. i already have the image on the root of my card can anyone help.
Plus those bastards sent me a refurb that has dead pixels that are white in the blk screen wtf sprint, thats pure whack customer service..
Click to expand...
Click to collapse
Type 'adb devices' in... Whenever I see the '/' before the '#' it means that it isn't recognizing my phone.

Just do it through adb. I did mine through adb the 1st, 2nd and 3rd time. After looking at the dirwctiona, I think it might be easier and should work.
-------------------------------------
Sent via the XDA Tapatalk App

Make sure the phone is connected as charge only, once it is type
ls /sdcard
AND PASTE THE RESULTS HERE
It sounds like you don't have the sdcard mounted or if you do you may be typing the file wrong compared to what is on the sdcard.
Don't panic, this had nothing to do worth the phone being refurbished, it is only a simple file not found error that once you fun that command can easily be solved.

liquidtenmillion said:
Make sure the phone is connected as charge only, once it is type
ls /sdcard
AND PASTE THE RESULTS HERE
It sounds like you don't have the sdcard mounted or if you do you may be typing the file wrong compared to what is on the sdcard.
Don't panic, this had nothing to do worth the phone being refurbished, it is only a simple file not found error that once you fun that command can easily be solved.
Click to expand...
Click to collapse
it keeps telling me permission denied lol

Type in
"adb shell" then
"ls /sdcard"
Without the quotes exactly as I typed them one at a time and paste the results.

dirkydirk23 said:
i did and its still not working.........i dont understand, let me upload another pic. and i already tried adb mount and fastboot still no luck
Click to expand...
Click to collapse
did you try fastboot boot recovery [dir on your computer]

Do a search for adb shell recovery. It should tell you how to do it. You are going to have to mount the system before doing anything else...and also change the recovery image to something Like recovery.ing as it is easier to type and less likely to be mis-typed
-------------------------------------
Sent via the XDA Tapatalk App

[Q] CWM update brain fart - need help

Hi All,
I wanted to update my ideos s7-104 (best buy US) to the Joenilan froyo fusion rom and made one mistake along the way. I copied the .zip file to the external sd card not the internal sd card. So zip file is not available to CWM (2.5.1.8). I tried manually pushing the file to the tablet with ADB (from computer) but the tablet is not visible to the system (windows 7 64bit with drivers installed, I could not get HiSuite to install with upgrade.cmd). This is strange becasue the Upgrade utility which uses adb flashes the rom just fine. Of course I wiped the system and reformatted the device per the instructions. Now when the unit boots it goes the fastboot and then stops with option to reboot with back/home which works. I don't think the unit is bricked just yet since I can still get into the CWM recovery.
Does anyone have any bright ideas to move the Ideos S7 Froyo v1.3-EXT4 Stable.zip to the internal sdcard?
Thanks for all the useful information previously posted!
Bruce
St. Louis MO

Hi, let see if i can help you, if you have a backup restore, if you dont that implies some work, i dont use windows i prefer linux, you can try to create a virtual machine, with windows xp or linux ubuntu and then with fastboot commands push the file to sd card.
Another way, get the oficial rom for your tablet copy the file to ext-sdcard and follow the install instrutions of the rom, you must create the dload directory in ext-sdcard.
it look like you lost the system files and the kernel of the device, so it boot in to fastboot, fastboot does not acept adb, but fastboot has some commands to copy kernel and system file to the device, it cant copy a zip file, must be a img file.
Version 6.0.1 of cwm reads update files from ext-sdcard so you can also try to install that recovery version with fastboot.
Remember: it always a good idea to have a backup before doing anything.
Hope that helps.

Fixed
hal_2000 said:
Hi, let see if i can help you, if you have a backup restore, if you dont that implies some work, i dont use windows i prefer linux, you can try to create a virtual machine, with windows xp or linux ubuntu and then with fastboot commands push the file to sd card.
Another way, get the oficial rom for your tablet copy the file to ext-sdcard and follow the install instrutions of the rom, you must create the dload directory in ext-sdcard.
it look like you lost the system files and the kernel of the device, so it boot in to fastboot, fastboot does not acept adb, but fastboot has some commands to copy kernel and system file to the device, it cant copy a zip file, must be a img file.
Version 6.0.1 of cwm reads update files from ext-sdcard so you can also try to install that recovery version with fastboot.
Remember: it always a good idea to have a backup before doing anything.
Hope that helps.
Click to expand...
Click to collapse
Thanks so much for the tips. I was able to flash the trzmod-v3 image and now I have a working tablet again. Pretty slick I must say.

Hi, well done, i'm working with cm9 for s7 maybe in some few days you can try cm9
hal_2000

does anyone know the combination to get into recovery and cwm.
thank's
sorry my bad english

BANOUNDROID said:
does anyone know the combination to get into recovery and cwm.
thank's
sorry my bad english
Click to expand...
Click to collapse
Hi, with s7 power off press, menu + call(green key) + power, wait a few seconds and you get cwm screen if it is install
Hal_2000

Can't write on internal SD card after root

After having rooted (with nexus 10 toolkit v1.3.0) my nexus 10 and flashed AOPK Nexus 10 (WIP) Task650 & Ktoonsez (1-4) rom, I'm unable to upload to, change or move any files or folders on my internal SD card. I installed Root Explorer and changed from Mount R/O to Mounted as r/w. Access is granted by Super SU. I also tried to change permission settings, unfortunatedly without any success. There appeared the following message:
"Warning
Permissions change was not successful. Please note that some file systems (e.g. SD card) do not allow permission changes."
Is there a possibility to change these permissions in order to be able to create and move files and folders on my SD card?
Thanks for taking your time to help me with my issue!
Anzirothu

1. Clear cache
2. Clear dalvik
3. Fix Permissions
forgot something ?

Thank you for your reply, Patrik!
1. done.
2. done.
3. Fix Permissions - How? With cwm? I did fix permissions with cwm recovery, but the problem persists...

Just so we are clear, when you say "upload to, change, or move" are you meaning you cannot copy a file from your computer to your Nexus 10? Or just that you cant arrange stuff through root explorer from within the tablet itself?

Neither copying from PC to Nexus nor arranging stuff through root exlorer from within the tablet itself. I can't even download an email attachment and put it to the SD card. The card seems to be locked.

I had that problem once but I dont remember what caused it or what exactly I did to fix. I think I just did a complete wipe by locking and unlocking the bootloader and then installing a new ROM again.

I think I did this too (unroot, lock bootloader, then root and unlock bootloader) and then installed the same rom again. I will try it this time with another rom.
Isn't there really no other solution to get access to my SD card again??
Thx for your help!

Are you using a toolkit to unlock and root? If so them maybe it is not doing something right and it messing up a permissions somewhere. It could also be a driver problem on your PC with being unable to copy a file to the tablet.

Thank you for your help!
I am using the nexus 10 toolkit V1.3.0. Right now I'm trying to intall twrp recovery with a fully wiped sd card. No easy task fot me being a noob...

In ClockWorkMod, make sure that /data is mounted
Then download the Android SDK: http://developer.android.com/sdk/index.html
I usually put all the files just in C:/android-sdk-windows
Once you have it all there open up the SDK Manager and download all the additional files needed. You probably only need to download "Android SDK Tools" and "Android SDK Platform-tools", but I always download the other files for whatever version of Android I am running, in our case Android 4.2. That way I have them if I need to do something else.
Once downloaded, open the Android-sdk-windows/platform-tools directory. copy:
adb.exe
adbWinApi.dll
adbWinUsbApi.dll
fastboot.exe
to your base C:/Android-SDK-Windows directory.
Now open command prompt from Start -> run
type: cd C:/Android-SDK-Windows
type: "adb devices" and it should list your tablet. It will actually say something with your devices serial number and then "Recovery" after it, showing your tablet is in recovery. If you dont see this then you either dont have your tablet mounted right from in the Recovery, ClockWorkMod is stupid, or you dont have working adb drivers.
Now copy the ROM you want to flash to C:/Android-SDK-Windows
Then type: "adb push blahblahblah.zip /data/media/0"
That should push the ROM to the root of your SD card. Give it time, it takes a while to push a ROM file. Once it is done, flash the ROM.
That *should* put it in the right spot where it looks like it is on your "internal storage" (what you see when navigating files within the ROM). If you dont see the ROM in clockworkMod then keep navigating back to the root of your internal storage and then open up "data", then "media", then "0" and you should see it. If you still cant find the ROM, push it again but just use "/data/media" as the location.
I just did all these steps myself to verify I remembered it all correct and I was able to successfully copy a ROM and find it on my tablet to flash by doing everything I just listed above. SO you should be good to go if you follow all those steps properly. I know it looks like a lot of work, but it really isnt and will go quite fast. Most of it is just the setup for getting ADB and Fastboot ready to use.
For a ROM to install, I would recommend to someone new like you either of these:
http://forum.xda-developers.com/showthread.php?t=2071082
^^^^^ That one is pretty close to the stock ROM with a few fixes and a couple extra features
or: http://forum.xda-developers.com/showthread.php?t=2071082
^^^^^ This one is pretty much CyanogenMod 10.1, but built by a different guy and not pulling every new thing from CM, just the "cherry picks" of features. It tends to be a bit more stable and less buggy than the real CM10.1 nightly's
And for a kernel you can flash and forget you will want to try this one:
http://forum.xda-developers.com/showthread.php?t=2098157
^^^^^ To flash that you will want to do a similar thing as how you pushed the ROM to your device. Only this time you will copy the kernels' "boot-r4.img" file into your android-adk-windows directory and use the command: "fastboot flash boot boot-r4.img"
While I enjoy the KTManta kernel more, it does require a bit of tweaking to get running perfect. Which is one of the things I like about it because of all the options to tweak. But for someone just learning this stuff that would be a bad thing, so Franco's kernel is much better than stock and doesnt require you to adjust anything once it is flashed to your tablet.

[Q] Desperate need some help, failure updating 4.4

my nexus 4 was rooted with 4.3 but then i decide to upgrade to 4.4
this is the video i am trying to follow, basically just wipe & install which i did most the time.
youtube title "NEXUS 4: HOW TO MANUALLY UPDATE TO ANDROID 4.4 KITKAT"
it has two files one is mako and one is gapp.
after i did all the wiping in cwm and try to install the mako file, it shows "no file context" or sth similar, and installation is abort (i think there is problem when i transfer the file), but then i continue to install the gapp file (what the hell was i thinking?)
so now i am stuck in the google start up loop, i can only access cwm recovery mode and don't have a valid rom to install in my sdcard.
i tried to adb push another rom to the sdcard with no success (my storage was already very low, any way to remove files in the storage at this point?)
the "mount & storage" also doesn't seem to let me mount the sdcard (but system shows up "unmount").
so now i don't know what to do.
if anything has any idea or suggestion please let us know.
i am quite desperate now with a dead phone and will try anything.
thanks for reading such a long thread.

Dude that vid is old and it installs pa or some other port just flash factory images from google
Sent from my F1 using xda app-developers app

try to sideload a zip with ADB in recovery. no need to copy to your internal storage.
also try to connect with adb shell, then you can delete some files manual with rm.

Frickelpit said:
try to sideload a zip with ADB in recovery. no need to copy to your internal storage.
also try to connect with adb shell, then you can delete some files manual with rm.
Click to expand...
Click to collapse
any step by step guide to do this?
i am still new to this thing even i install a few roms before.
i will google it now, but any additional info is much appreciate.
thanks

Frickelpit said:
try to sideload a zip with ADB in recovery. no need to copy to your internal storage.
also try to connect with adb shell, then you can delete some files manual with rm.
Click to expand...
Click to collapse
frustrated..
i can't seem to get my windows to recogize the device (when i type adb devices, it shows an empty list)
already try trouble shooting this for a long time with no result.
any idea?

telly0050 said:
frustrated..
i can't seem to get my windows to recogize the device (when i type adb devices, it shows an empty list)
already try trouble shooting this for a long time with no result.
any idea?
Click to expand...
Click to collapse
after tons of troubleshooting finally got it back to work.
it ends up the reason is i didn't update to the latest cwm at the very beginning.
and sideloading 4.4 didn't work because of that too, i have to install an old 4.2 to have it working.

[Q] how to recover data from a phone that will not boot

I have jamal2367's [AOSP] official 4.4.2 - S4 Google Edition ROM installed (final R1.2) a SGH-1337M.
The other day it started getting stuck on boot; the blue, red, yellow, green circles just continually go in and out without anything else happening. I have booted into CWM Recovery (v6.0.4.4) and done a wipe cache partition and wipe dalvik cache but it did not help.
Can anyone provide advice/steps on how to copy the data (mostly pics and WhatsApp history) off this phone? SMS history would also be nice but not necessary.

toggly said:
I have jamal2367's [AOSP] official 4.4.2 - S4 Google Edition ROM installed (final R1.2) a SGH-1337M.
The other day it started getting stuck on boot; the blue, red, yellow, green circles just continually go in and out without anything else happening. I have booted into CWM Recovery (v6.0.4.4) and done a wipe cache partition and wipe dalvik cache but it did not help.
Can anyone provide advice/steps on how to copy the data (mostly pics and WhatsApp history) off this phone? SMS history would also be nice but not necessary.
Click to expand...
Click to collapse
I would make a backup in your recovery and then flash the rom you had installed. See if that helps.
Edit: You didn't try to update. I changed my comment saying you had tried.

1. Download Aroma File Manager
2. Put a external sd into your phone.
3. Boot into the custom recovery and flash the Aroma file.
4. It will boot into a file browser and you can copy all the files from internal to your external.
ps it's possible that your custom recovery already has a filemanager build in. Then all these steps are obsolete.

I boot into AROMA Filemanager but I can't see anything on the internal SD card (see attachment).
Any ideas? Does that folder icon mean the "sdcard" folder is encrypted?

toggly said:
I boot into AROMA Filemanager but I can't see anything on the internal SD card (see attachment).
Any ideas? Does that folder icon mean the "sdcard" folder is encrypted?
Click to expand...
Click to collapse
Is it encrypted? Then probably it won't work. In that case just reflash the rom you are on without wiping.

toggly said:
Does that folder icon mean the "sdcard" folder is encrypted?
Click to expand...
Click to collapse
Lennyz1988 said:
Is it encrypted? Then probably it won't work. In that case just reflash the rom you are on without wiping.
Click to expand...
Click to collapse
I don't know, that's why I am asking what that icon means?

You say CWM is working, so you can just adb pull everything you need. Applications usually save data in a directory under /data/data or /sdcard/Android/data.
You should find the directories you want with adb shell, then you can adb pull them, then if you reflash your rom you can adb push them back into the same locations. Also, depending where they are saved, your pictures will most likely not be deleted when you reflash your rom. Better safe than sorry though.
If you don't have adb you'll have to download the binary, or you can install the entire Android SDK. Which operating system do you use?

toggly said:
I don't know, that's why I am asking what that icon means?
Click to expand...
Click to collapse
The icons means that it's symlinked. If it's not encrypted then you should find the data. It can be in an other place then where you are looking. Try looking in /data/media or some other maps in /data
Or just flash the rom you are currently on without wiping.
soldier9599 said:
You say CWM is working, so you can just adb pull everything you need. Applications usually save data in a directory under /data/data or /sdcard/Android/data.
You should find the directories you want with adb shell, then you can adb pull them, then if you reflash your rom you can adb push them back into the same locations. Also, depending where they are saved, your pictures will most likely not be deleted when you reflash your rom. Better safe than sorry though.
If you don't have adb you'll have to download the binary, or you can install the entire Android SDK. Which operating system do you use?
Click to expand...
Click to collapse
Adb won't work unless he already has authorized adb when his device was booted.

toggly said:
I boot into AROMA Filemanager but I can't see anything on the internal SD card (see attachment).
Any ideas? Does that folder icon mean the "sdcard" folder is encrypted?
Click to expand...
Click to collapse
You need to mount partitions to see the contents.. Go to Aroma File Manager Settings and check the option "Moumt automatically partition on boot".. then restart your recovery and flash again the Aroma File Manager

Lennyz1988 said:
Adb won't work unless he already has authorized adb when his device was booted.
Click to expand...
Click to collapse
I've had devices where the first thing I did with them was unlock bootloader, fastboot flash recovery, and then go into recovery and adb sideload, all without booting the system.

peppe130 said:
You need to mount partitions to see the contents.. Go to Aroma File Manager Settings and check the option "Moumt automatically partition on boot".. then restart your recovery and flash again the Aroma File Manager
Click to expand...
Click to collapse
That did the trick, thanks!!

Nothing

soldier9599 said:
I've had devices where the first thing I did with them was unlock bootloader, fastboot flash recovery, and then go into recovery and adb sideload, all without booting the system.
Click to expand...
Click to collapse
Yes and I believe that. But from version 4.2.2 android forces rsa encryption. So you need to boot into your rom and enable it. Unless the custom rom/kernel has disabled it, but I haven't seen any that have.