Related
My phone keeps booting into recovery mode.
Power on -> Blank -> Reboot -> Recovery
I had the new SPL (the saphire ported one), JF's recovery (i still have it on) and JF1.51.
This happened since i tried to flash the HTC ADP update.zip.
I have tried using the hardSPL, reflashing the saphire SPL, tried flashing back to JF1.5, Rodgers but nothing seems to work
Any ideas?
EDIT: I just checked and it didnt flash the saphireSPL! i dont think adb shell push is copying the update.zip's to the SD card.
EDIT:
SOLUTION:
I was right in that it wasn't copying the updates to the sd card, i borrowed a friends G1, used it to put on the saphireSPL, flashed (and it worked this time), got into fastboot (the hardSPL fastboot didnt seem to work), and restored my nandroid backups! yey! now to try JAC's build
if you want to adb push in recovery, you'll need to mount the sdcard first or it will appear to have transfered, but actually done nothing.
next time, try
Code:
adb shell mount /sdcard
adb push update.zip /sdcard/update.zip
ravenge said:
if you want to adb push in recovery, you'll need to mount the sdcard first or it will appear to have transfered, but actually done nothing.
next time, try
Code:
adb shell mount /sdcard
adb push update.zip /sdcard/update.zip
Click to expand...
Click to collapse
Thank you, that'll come in really handy for when i dont have a spare Dream or card reader about!
ravenge said:
if you want to adb push in recovery, you'll need to mount the sdcard first or it will appear to have transfered, but actually done nothing.
next time, try
Code:
adb shell mount /sdcard
adb push update.zip /sdcard/update.zip
Click to expand...
Click to collapse
Oh my god... this (hopefully) has fixed the problem I've had for the past two days - I've spent so long reading every thread on here about the SPL problems, etc. I had a feeling the problem was the update wasn't working correctly, but I had no idea why. (It didn't complain, but just went very quickly - much to quick to be doing a full os upgrade).
Thanks!!!
umm how would i even run that script?cuz i keep bootlooping
Jerzdre said:
umm how would i even run that script?cuz i keep bootlooping
Click to expand...
Click to collapse
On Phone:
Recovery -> ALT+X -> Console
On PC
Command prompt
"cd <directory where you have update.zip>"
"adb shell mount /sdcard"
"adb push update.zip /sdcard/update.zip"
On Phone
Hold 'Home' and then:
On PC:
"adb shell reboot"
ravenge said:
if you want to adb push in recovery, you'll need to mount the sdcard first or it will appear to have transfered, but actually done nothing.
next time, try
Code:
adb shell mount /sdcard
adb push update.zip /sdcard/update.zip
Click to expand...
Click to collapse
but you can abd push to the ext2 portion of the sd card without mounting while in recovery, correct?
Hey there
i cant restore from a nandroid backup.. it says "run "nandroid-mobile.sh" via adb"
when i run it from # shell i get that it cant mount /sdcard (it isnt goldcard)
anyne that can help?
Holyachmed said:
Hey there
i cant restore from a nandroid backup.. it says "run "nandroid-mobile.sh" via adb"
when i run it from # shell i get that it cant mount /sdcard (it isnt goldcard)
anyne that can help?
Click to expand...
Click to collapse
are you connected via USB ???
if yes , unmount the card or disconect from usb ......
Do that work ?
here is original android 1.6 if you cant do backup
HTML:
http://rs584.rapidshare.com/files/292517090/RUU_Click_HTC_WWE_1.67.405.6_WWE_release_signed_NoDriver.exe
To make a restore you have to have more than 50% of battery.
if i disconnect it from usb it doesnt work either going to check the battery now ... hope it works
i got nearly full battery... and even tried with and without goldcard and different sdcards and i tried put the nandroid-mobile.sh in /system/bin and flash it when the phone is on .. now trying to make a update.zip by the .img
...
Go to recovery, plug your phone with USB, and in a shell do:
cd /system/bin/
nandroid-mobile.sh --restore
I miss a part of the command, you have to complete it, and during the restore it will tell you the error.
Code:
/ # nandroid-mobile.sh --restore
nandroid-mobile.sh --restore
nandroid-mobile v2.2.1
Using G1 keyboard, enter a directory name substring and then <CR>
to find matches or just <CR> to accept default:
Using string to search for matching backup directories
error: unable to mount /sdcard, aborting
this is the error.. but i restored from an app called backup root now so it is working again
Mod. edit: not dev related, moved to general
gl though
the subject says it all. I've been trying to push apps to my encrypted xoom all afternoon without any luck...
I'll go ahead and admit upfront that I am a noob when it comes to using the sdk... so that could also be a major factor.
adb install (insert exact location+ filename.apk for the app you want to install)
I just tested it out
for example
adb install C:/abc.apk
What command are you using? What error message are you getting? Did you do a adb remount to make sure that the /system/app path is writable?
You can always do an adb install [package name].apk as well.
scsa20 said:
What command are you using? What error message are you getting? Did you do a adb remount to make sure that the /system/app path is writable?
You can always do an adb install [package name].apk as well.
Click to expand...
Click to collapse
I just tried to execute adb remount (I had not until you mentioned it), but I get a "remount failed: operation not permitted".
Code:
Hannibal:platform-tools dmoore$ ./adb install /Users/dmoore/Documents/android-sdk/platform-tools/AsusReader.apk
1259 KB/s (7747001 bytes in 6.007s)
pkg: /data/local/tmp/AsusReader.apk
Failure [INSTALL_FAILED_DEXOPT]
Additional information: I am on a MacBook Pro using the latest version of the SDK (downloaded it yesterday).
try typing "adb devices" if it does not list your xoom try installing or re-installing the motorola usb drivers
http://www.motorola.com/Support/US-...tware_and_Drivers/USB-and-PC-Charging-Drivers
just noticed the macbook part
http://www.samsung-tablets.com/motorola-xoom-usb-driver-for-pc-and-mac-download.html/
Ok... back to me being a complete when it comes to the SDK (and the Xoom in particular)...
My Xoom is completely stock... it has not been rooted or otherwise modified.
With that being said, is there some trick to getting the file system to mount as r/w? Do I need to reboot in to recovery before adb remount will work?
Sic123 said:
just noticed the macbook part
http://www.samsung-tablets.com/motorola-xoom-usb-driver-for-pc-and-mac-download.html/
Click to expand...
Click to collapse
I've already installed the Android File Transfer app... it only allows me to browse the SD card - not the root fs... unless there's something I'm missing...
dmoore44 said:
Ok... back to me being a complete when it comes to the SDK (and the Xoom in particular)...
My Xoom is completely stock... it has not been rooted or otherwise modified.
With that being said, is there some trick to getting the file system to mount as r/w? Do I need to reboot in to recovery before adb remount will work?
Click to expand...
Click to collapse
you dont have to be in recovery (recovery wont do any good unless you install clockwork recovery) for adb remount to work but if your not rooted you cant push files into the system folder thats the whole point of rooting is to unlock the system files also if your pushing it into /system/app the rom is odexed so you will need the apk plus the odex file
Sic123 said:
you dont have to be in recovery (recovery wont do any good unless you install clockwork recovery) for adb remount to work but if your not rooted you cant push files into the system folder thats the whole point of rooting is to unlock the system files also if your pushing it into /system/app the rom is odexed so you will need the apk plus the odex file
Click to expand...
Click to collapse
I have the odex file, so i'm not terribly worried about that.
My major question would be this though... Do I need to go full blown root, or can I just unlock the device?
Hey Everyone,
So last night randomly while texting my phone reboots and is now stuck in "Android is Updating screen, Apps is starting" with the swirl icon swirling forever [waited over 15 min]. It keeps doing this and now I assume some file somehow got corrupt?
I'm on 4.2.2, stock rom, franco kernel. I've tried fixing permissions, wiping cache/dvalik and nothing has helped thus far. Only thing I can see is a complete wipe? Nandroid backup is not possible atm. Is there a way to pull all my pictures and files from recovery only?
Are there any other suggestions before I go that route?
Thanks,
Jonathan
Boot into recovery and use adb to pull all the contents of your SD card like this:
Code:
adb pull /sdcard/
Then do a full wipe and flash a ROM.
chromium96 said:
Boot into recovery and use adb to pull all the contents of your SD card like this:
Code:
adb pull /sdcard/
Then do a full wipe and flash a ROM.
Click to expand...
Click to collapse
Just had a question, how do I set where ADB pulls the files?
impruv said:
Just had a question, how do I set where ADB pulls the files?
Click to expand...
Click to collapse
Code:
adb pull \path\of\your\choice /sdcard/
i had the exact thing happen to me in january, something corrupted and it wouldnt finish booting. nandroid restore and wiping/flashing didnt help, i had to flash the factory img to get up and running, then i restored a nandroid backup. did you have fsync disabled?
chromium96 said:
Code:
adb pull \path\of\your\choice /sdcard/
Click to expand...
Click to collapse
Hmmm weird, it says my "remote object '\D:\nexuspull' does not exist" and I'm positive that's the correct path
impruv said:
Hmmm weird, it says my "remote object '\D:\nexuspull' does not exist" and I'm positive that's the correct path
Click to expand...
Click to collapse
Sorry I screwed up the command. It should be like this:
Code:
adb pull /sdcard/ D:\nexuspull
chromium96 said:
Sorry I screwed up the command. It should be like this:
Code:
adb pull /sdcard/ D:\nexuspull
Click to expand...
Click to collapse
Ah thank you. Works perfectly now!
chromium96 said:
Sorry I screwed up the command. It should be like this:
Code:
adb pull /sdcard/ D:\nexuspull
Click to expand...
Click to collapse
It seemed to have pulled MOST of the folders, but I have gone and manually done the rest. There is still one folder I can't pull because the folder name has spaces "Photo Grid". Can adb not deal with paths with spaces? I tried _ as a space but did not work.
impruv said:
It seemed to have pulled MOST of the folders, but I have gone and manually done the rest. There is still one folder I can't pull because the folder name has spaces "Photo Grid". Can adb not deal with paths with spaces? I tried _ as a space but did not work.
Click to expand...
Click to collapse
Have you tried putting the path is double quotes?
So, before I do a firmware update (In this case 4.2.2 to 4.3 OTA) I do a Titanium backup and a TWRP backup and copy both sets of backup files to my PC; it obviously makes no sense to only have backups on the device you are backing up. I upgraded to TWRP 2.6.0.0, did a full backup, and as usual I went to copy my backup files over to my Windows 7 computer using Windows Explorer and I can only get a couple of the files to move over. No warning, no error, no nuttin. This has always worked before......Did something change, and if so, how do I fix it?
I see from another post that TWRP changed the permissions of the backup files in the latest version of the program, and in my case the location as well. The workaround is to a) change the permissions on all those backup files, which I could see the nightmare problems that could cause later on when doing a restore and/or the security issues or b) doing an adb pull.
SOLVED.
The adb pull did the trick. All files were transferred over to my PC.
I had several issues getting adb to work:
1) I had an old version of the SDK installed on my PC which was causing a devices not recognized problem or something similar.
2) I didn't notice the message about verifying the RSA on my phone, which once verified, fixed the phone "offline" problem.
3) The screen lock on my phone was coming on after its timeout and locking me out from seeing the phone.
reverted to twrp 2.5.0.0
Same problem here with Google Nexus i9250 / twrp 2.6.0.0 / win7 64bit. Tried to copy backup of (BOOT/SYSTEM/DATA) via MTP or ftp from Nexus to PC. Only the first two files (boot.emmc.win/-md5) were copied. After downgrading to twrp 2.5.0.0 everthing was fine.
I had the same problem. It is caused by strange suid permissions set by TWRP. Solved it using chmod 0664 /data/media/0/TWRP/... (as root)
I was not able to adb pull before changing the files' permissions.
More details here:
http://forum.xda-developers.com/showpost.php?p=44120545&postcount=14
(Google found that HTC One thread first, so I didn't search any further)
Type this in Terminal Emulator:
su
busybox chown - R 1023.1023 /data/media/*
That should solve all permissions problems.
I had no trouble at all by doing the following:
Access the sdcard from /data/media/0
Copy data.ext4.win and system.ext4.win to a temporary location.
(The "Set UID" and "Set GID" permissions were automatically removed. If not, you can change them from here.)
Copy the files to PC using MTP.
The remaining backup files from the TWRP directory can be copied normally.
Done
Note: You can instead just change the permissions on these two files inside the TWRP directory, but I did the temporary location copy just to be safe.
Mercado_Negro said:
Type this in Terminal Emulator:
su
busybox chown - R 1013.1023 /data/media/*
That should solve all permissions problems.
Click to expand...
Click to collapse
coming up with chown: unknown user -
is that a space between 1023 and /data?
daryllh said:
coming up with chown: unknown user -
is that a space between 1023 and /data?
Click to expand...
Click to collapse
I'm sorry, I made a mistake there. The correct command is:
su
busybox chown -R 1023.1023 /data/media/*
I wrote 1013.1023 and it's 1023.1023
Mercado_Negro said:
I'm sorry, I made a mistake there. The correct command is:
su
busybox chown -R 1023.1023 /data/media/*
I wrote 1013.1023 and it's 1023.1023
Click to expand...
Click to collapse
After I did this command, my pc can't detect the back up
handols said:
After I did this command, my pc can't detect the back up
Click to expand...
Click to collapse
Did you plug/unplug your device after running this command? There shouldn't be any problems. Furthermore, now you should be able to copy your TWRP and TiBu backups successfully to your computer. It's a pretty straight forward process.
Im on twrp 2.5.0.0 with Android 4.3. I cant copy the BACKUP folder directly to my PC with the default windows explorer because the backup isnt stored in /sdcard/TWRP. How can I fix this? I used to be able to do this without adb push/pull...
Mercado_Negro said:
I'm sorry, I made a mistake there. The correct command is:
su
busybox chown -R 1023.1023 /data/media/*
I wrote 1013.1023 and it's 1023.1023
Click to expand...
Click to collapse
Thanks for this. I'm able to backup TWRP folder to PC now :highfive:
Since my original post 3 months ago I updated all my programs to 4.3 friendly versions as each was released (superuser 1.0.2.1, Windows drivers, TWRP 2.6.3.0, etc.) and now I don't need to do adb pulls any more and I can just copy and paste files from my phone to my pc and all files are copied over without missing any of them. Now I see the updated programs are already starting to show up for Android 4.4; here we go again.
Now see 0 / legacy emulated
Mercado_Negro said:
I'm sorry, I made a mistake there. The correct command is:
su
busybox chown -R 1023.1023 /data/media/*
I wrote 1013.1023 and it's 1023.1023
Click to expand...
Click to collapse
Hi just wondering, Is there a way to cancel this command (just add a +R maybe) I did it on my phone and I think it may be the cause that I have a Legacy emulated 0 path problem Ive searched around and cant seem to find a solution. Thanks
NightCrawler504 said:
Hi just wondering, Is there a way to cancel this command (just add a +R maybe) I did it on my phone and I think it may be the cause that I have a Legacy emulated 0 path problem Ive searched around and cant seem to find a solution. Thanks
Click to expand...
Click to collapse
What's the problem? That's a valid path.
Legacy emulated 0
Mercado_Negro said:
What's the problem? That's a valid path.
Click to expand...
Click to collapse
I have an external sd (sdcard1) = /storage/sdcard1 so gr8 but then I have emulated (??) Storage/emulated/legacy and Storage/emulated/0 and sdcard0 storage/sdcard0 they were complety different folders been reading around seems to be a problem with cm when I go from 4.2 and over my phone is a e970 att, cant delete the emulated folder... already erased all my data previously, any help will do,I'm almost sure it had nothing to do with the chown command but had to give a try.
NightCrawler504 said:
I have an external sd (sdcard1) = /storage/sdcard1 so gr8 but then I have emulated (??) Storage/emulated/legacy and Storage/emulated/0 and sdcard0 storage/sdcard0 they were complety different folders been reading around seems to be a problem with cm when I go from 4.2 and over my phone is a e970 att, cant delete the emulated folder... already erased all my data previously, any help will do,I'm almost sure it had nothing to do with the chown command but had to give a try.
Click to expand...
Click to collapse
No, it doesn't have anything to do with this command since it's just a way to set different permissions.