[Q] CWM recovery on [I9020] - Nexus S Q&A, Help & Troubleshooting

Right I have CWM 5.0.2.0 on my t-mob nexus s I can get it into recovery but no files appear on any of the mounted drives. I have a good CWM recovery and a full TB back up file backed up on my comp. Since the sdcard is not removeable I can simply pull it out and put my recovery on it. When I plug in the phone the drive is hidden but my antivirus ask if I want to scan it. I have had no luck unhiding it. I have also tried to use ADB to push the file but am not yet a cmd line guru so I have had difficultly. Can anyone tell me where I need to put my recovery and the cmd to push it to CWMs recovery folder or any other solution. I have put a solid 12 hours into this and fell I'm just dancing around the answer.
ps forgot to mention that if I power up regularly it stops at the google logo with the unlock symbol

It's easy with adb. Just use:
adb shell mount /sdcard
adb push localfile /sdcard/newfilename

Thank you so much took a little of tweaking but finally got my phone working again. Though I have always said the only true way to learn to fix something is to break it, I would still be pulling my hair out if not for this community. Now the unlocked gsm galaxy nexus upgrade is less justified but maybe this can still be my new mp3 player.....
Thanks again guys and gals!

Even though it is fixed did you to mount USB storage from cmw? That's what you want to mount. Not /system /data etc.

Related

[Q] [URGENT] HELP!!! Followed instructions, now stuck at Boot Screen!?? [SGS4G]

I sure hope someone can help me! I followed the instructions posted here:
http://forum.xda-developers.com/showthread.php?t=1122508&page=3
Here is a detailed list of steps I've taken:
1. I had previously rooted my phone, some months ago, and I don't recall the specific steps but I'm pretty sure it involved BusyBox and SuperUser..
2. I had seen earlier instructions involving the use of ClockWorkMod ROM Manager, BUT I only installed the App, I DID NOT do any flashing with it (or anything at all). I simply uninstalled ROM Manager as soon as I saw the newer post and warnings!
3. I downloaded the "update.zip" and "recovery" files to my Dropbox from the links posted here:
http://forum.xda-developers.com/showthread.php?t=1099374
4. Opened my preferred File browser, "File Expert". It has root permissions, and handily, connects to Dropbox as well. I selected Menu > Mount > Mount as Read Write.
5. Copied the two files from my Dropbox account to the root of my SD card. Then, realizing the instructions actually required them to be in /system/bin, copied the files again, browsed to /system/bin, and Pasted the files, selecting "Overwrite" when asked.
5. I exited out of File Expert, powered down my phone, waited a minute, and then pressed (all together at the same time, but starting in this order): VOL Up + VOL Down + Power. Held all three for about 3 or 4 seconds until I saw the typical boot screen that says "Galaxy S 4G exclusively from T-Mobile -- SAMSUNG" -- waited another moment, then released the buttons.
6. Ohh CRAP!
It's been about five or ten minutes and it is STILL sitting there on the same Boot Screen! I'm afraid to turn off the device, afraid to do anything at this point, I'm terrified I've bricked my phone!
I've seen bits and pieces around these forums regarding something called "Odin", but my worst fear at this point is that I may be at risk for losing all my data. *sigh* Backing up my phone was my whole goal in the first place (Probably took precisely the wrong approach..)!
So...
ANY IDEAS? Any possible way to save my phone AND my data??
The update.zip was supposed to stay on the sd card. Only the recovery.bin file was to be pushed to the system.bin folder. Your not bricked. If you were your phone would be dead. Showing no life at all. As far as how to boot the phone I'm not sure. I would pull the battery and put in back in then try powering on. Don't know if it will work or not. If not you may need Odin.
Sent from my HTC_Amaze_4G using xda premium
Just put phone in "download" mode
Sent from my SGH-T959V using xda premium
Please use the Q&A Forum for questions Thanks
Moving to Q&A
I think at this point, you won't be able to recover your phone without losing all your data.
I've goofed and had my phone stuck like that, too. I was able to use adb to catch it and get it into download mode. I didn't try getting into adb shell, though. If you can do that, then you can move the update.zip from /system/bin to /sdcard. If you can open the shell window then try the following commands:
su
mount -o rw,remount /dev/block/stl9 /system
cd /system/bin
mv update.zip /sdcard/
reboot

Phone won't finish boot process, need urgent help

Alright so looks like I did something completely stupid and now my phone won't finish the boot process. I was looking at some remappings for the recent key to the menu option and from a post in the development section I found a thread in the International One X development forum that had re-odexed files so that the recent key stayed as the recent key and holding the home button became the menu key. Since they were re-odexed and I had root access I figured I would just manually replace them on my phone with Root Explorer...bad idea. The files were:
System/Framework/android.policy.odex
System/Usr/keylayout/qwerty.kl
After I moved them and reset permissions I rebooted my phone and now it goes through the first couple of boot animations but gets stuck on screen that displays beats audio at the bottom.
I really need to know what to do to fix this. When I plug my phone into my computer it recognizes it as a new \drive, but I don't have access to any of it (still says I need to mount). I also have the android SDk and adb installed if thats of any help. I would really like to not lose any data so hopefully thats possible.
Please help me with this if you have any knowledge of what to do.
Just one little quick update. Even though my computer won't let me access my One X as a drive, when I use command prompt and adb to check for adb devices my One X is listed.
Run the at&t ruu exe file, located in the Dev section.
tanman21 said:
Run the at&t ruu exe file, located in the Dev section.
Click to expand...
Click to collapse
Alright I'm downloading that now.
In the meantime, how do I get root access with adb/give it permission to overwrite read only files? I pulled the two files that caused this messed and pulled my backups, but when I push them back to the phone it tells me I can't because their read only. I'd rather do it this way since I will be changing only the files that caused the problem.
EDIT: Is the RUU really going to delete all the information on my device? If thats the case I would really appreciate figuring out how to get adb to push my backuped files to the /system directory instead
ErikWithNoC said:
Alright I'm downloading that now.
In the meantime, how do I get root access with adb/give it permission to overwrite read only files? I pulled the two files that caused this messed and pulled my backups, but when I push them back to the phone it tells me I can't because their read only. I'd rather do it this way since I will be changing only the files that caused the problem.
EDIT: Is the RUU really going to delete all the information on my device? If thats the case I would really appreciate figuring out how to get adb to push my backuped files to the /system directory instead
Click to expand...
Click to collapse
Yeah, the RUU returns your phone to factory (but doesn't touch your personal files)
EDIT: Also, just pulling this off the top of my head so take it with a grain of salt...
adb devices
adb shell
su
*grant the su request on your device*
adb push <from> <to>
stnguyen09 said:
Yeah, the RUU returns your phone to factory (but doesn't touch your personal files)
EDIT: Also, just pulling this off the top of my head so take it with a grain of salt...
adb devices
adb shell
su
*grant the su request on your device*
adb push <from> <to>
Click to expand...
Click to collapse
Thanks for your comment. I used the RUU and it kept my personal data so its not a big lose. Had to reinstall a few apps, but for most of them (games at least) my saved data was still there.
I tried a lot using adb and just couldn't get it to work. I don't the phone got far enough through the boot process for root access to be allowed. I was able to run the one click root tool while it was in its stuck boot phase, but it still wouldn't give me permission to modify the /system portion of the phone to be read/write.
All in all though this was a great learning experience. Prior to this happening I knew nothing about adb and now I know commands for pulling, pushing, remounting, shell commands, and other things. I also learned how to fix a softbrick (first one) and what RUU is.

HELP!

Right...
So basically im a trainee pen tester and ive moved onto the section about mobile devices, being the mug that i am i rooted my brand spanking new htc one x afors i was going to install backtack on my phone.
So after trying various roms i settled on leedroid... seemed to work best on my one x as i am currently waiting for an official cyanogen rom.
Anyhow.... after about two days loads of apps would open.. and if they did it took about 3-5 mins for them to do so.
Upon investigating my directory and system tree was absolutely goosed. So using my clockwork recovery i formatted the inbuilt sdcard, data, cache and system. (figured i'd start from scratch)
Naturally i got stook in bootloop but ive done a really stupid thing. I have transfered my nandroid backup of the stock rom off the handset and onto my pc to save space so i now cant so a recovery. Ive tried downloading the official vodafone uk RUU and it wont work, but i have had an idea!
I am a complete noob when it comes to fastboot and adb but ive learned how to use basic adb and i was wondering if i could use adb to "push" the file onto my phone to then use the recovery to recover the original rom.
The command i used was
adb mount /sdcard/
adb push stock /sdcard/
and then i get
push: stock/system.ext4.tar -> /sdcard/system.ext4.tar
and after 45 minutes its still there.... so im guessing im doing something wrong.
Can anyone help please because ive read nearly 100 pages now tried about 20 different things and have been on at this for 6 hours or do i need
to just put the phone in the bin...
Thanks
Kris
Looks like you might have posted in the wrong section bro..... We don't have a Leedroid ROM available for the OneXL, and CWM is OK at best on our phones. If you have the Tegra version of the One X, you might want to hit up the forums here: http://forum.xda-developers.com/forumdisplay.php?f=1533
For your issue, if the bootloader is unlocked, you might have to re-lock it before the RUU will work. Once you have a locked bootloader, if you put your phone into Fastboot mode, the RUU will detect it and format everything correctly back to stock.
klashnikoff said:
Right...
So basically im a trainee pen tester and ive moved onto the section about mobile devices, being the mug that i am i rooted my brand spanking new htc one x afors i was going to install backtack on my phone.
So after trying various roms i settled on leedroid... seemed to work best on my one x as i am currently waiting for an official cyanogen rom.
Anyhow.... after about two days loads of apps would open.. and if they did it took about 3-5 mins for them to do so.
Upon investigating my directory and system tree was absolutely goosed. So using my clockwork recovery i formatted the inbuilt sdcard, data, cache and system. (figured i'd start from scratch)
Naturally i got stook in bootloop but ive done a really stupid thing. I have transfered my nandroid backup of the stock rom off the handset and onto my pc to save space so i now cant so a recovery. Ive tried downloading the official vodafone uk RUU and it wont work, but i have had an idea!
I am a complete noob when it comes to fastboot and adb but ive learned how to use basic adb and i was wondering if i could use adb to "push" the file onto my phone to then use the recovery to recover the original rom.
The command i used was
adb mount /sdcard/
adb push stock /sdcard/
and then i get
push: stock/system.ext4.tar -> /sdcard/system.ext4.tar
and after 45 minutes its still there.... so im guessing im doing something wrong.
Can anyone help please because ive read nearly 100 pages now tried about 20 different things and have been on at this for 6 hours or do i need
to just put the phone in the bin...
Thanks
Kris
Click to expand...
Click to collapse
Wrong forum, this is for the Snapdragon 4 version of the One X (One XL). You should have posted in the International One X forums.
Aside from that, I don't think you're doing what you're trying to do correctly. First you need to extract Rom.zip from the RUU (look it up on YouTube), and then the command would be:
adb push rom.zip /sdcard/
That should put it on the root of the sdcard then you might be able to flash it through recovery, although I have never tried this so don't take my word for it.
You are doing it wrong, I believe. I've always done it the way below. Not sure if its supposed to work that way too.
You need to specify the destination file name as well.
So like if i wanted to push file.txt to my sdcard:
adb push file.txt /sdcard/file.txt
rohan32 said:
You are doing it wrong, I believe. I've always done it the way below. Not sure if its supposed to work that way too.
You need to specify the destination file name as well.
So like if i wanted to push file.txt to my sdcard:
adb push file.txt /sdcard/file.txt
Click to expand...
Click to collapse
Yep, this is the way to do it. Works for me every time.
Sent from my HTC One X using xda premium

File recovery...

Ok, here's the deal.. I have the Skyrocket, and a couple days ago, I accidentally stepped on it and cracked the screen. It no longer showed any picture, so.... In a fit, i threw it at the wall and shattered the screen completely. The phone still powers on, and boots to CM10 (I can hear the sound when I press the power/lock button). I have CWMR installed as well. Apparently, I didn't have USB debugging enabled (altho i could have sworn I did!), and now I can't get at any of my files from my sdcard.
I tried adb and fastboot, neither even detects the phone as being there.
I have a replacement device coming in a few days (AT&T insurance, GREAT STUFF!), so I would really like to be able to get my stuff from this phone ASAP... Anyone know a way?
Fastboot doesn't work?? Then something is wrong beyond just the screen. . . . Anyways, Can you boot into recovery?? If yes, there is a guess work method to mount the system partition via CWM so you can use adb. You can ask someone who uses the similar device with cyanogenmod10 to count the number of steps to go to the "mounts and storage" option in the CWM main menu and counts the steps to go to "mount system" option in the sub menu and use that counts to mount your system partition. . . . If you can successfully mount system partition then you can gain access to adbd (adb daemon) binary in your system partition and use adb from recovery just by plugging the device to your computer. And use adb shell to mount the other partitions and pull all the files you need. . . . I don't know whether if this works practically but theoretically it should work . . . . Keep in mind that you have to guess the no of steps carefully or else you may end up "wiping" any partition accidentally. . . .
#pitchblack5691#
i made the same mistake at one point lol try this it worked well for me when i couldnt even see the screen maybe it might work for you good luck http://code.google.com/p/adb-file-explorer/
pitchblack5691 said:
Fastboot doesn't work?? Then something is wrong beyond just the screen. . . . Anyways, Can you boot into recovery?? If yes, there is a guess work method to mount the system partition via CWM so you can use adb. You can ask someone who uses the similar device with cyanogenmod10 to count the number of steps to go to the "mounts and storage" option in the CWM main menu and counts the steps to go to "mount system" option in the sub menu and use that counts to mount your system partition. . . . If you can successfully mount system partition then you can gain access to adbd (adb daemon) binary in your system partition and use adb from recovery just by plugging the device to your computer. And use adb shell to mount the other partitions and pull all the files you need. . . . I don't know whether if this works practically but theoretically it should work . . . . Keep in mind that you have to guess the no of steps carefully or else you may end up "wiping" any partition accidentally. . . .
#pitchblack5691#
Click to expand...
Click to collapse
No, fastboot doesn't work either, I tried that as well... I was trying to get into recovery, I found another thread here that was an HTC phone, I think, with a similar issue. It gave steps for navigating CWM. I couldn't get the partitions to mount.
I think you're right, that there is something more wrong with it than the screenm, because in the Windows device manager, I could see 2 extra drives that were both listed as Samsung something (it's the next morning now), both with a size of 0 bytes. The strange thing is that the phone would boot. Completely boot. I had a friend message me on Fcebook, and the notification went off on my phone at the same time it did my loaner. (both of which were signed into my Facebook)...
crashpsycho said:
i made the same mistake at one point lol try this it worked well for me when i couldnt even see the screen maybe it might work for you good luck http://code.google.com/p/adb-file-explorer/
Click to expand...
Click to collapse
Thanks for the tip, but this didn't work either.. I don't know what else I screwed up on this phone, but wow... lol

[Q] /sdcard not accesable anymore

Hi together,
earlier I wanted to finally give the L-Preview a shot so I downloaded it and installed it as it was mentioned in the thread's instructions. Everything was fine until I was forced to reinstall it because Wifi kept getting stuck at switching (which didn't fix itself after a reboot) and some other things. So I did everything again like I did before but after I booted it up again and set up everything I noticed that in ES-File manager I couldn't access my sdcard directory. So I booted back into my recovery and saw that even there my usual sdcard directory was nearly gone except for a few folders (0, clockwordmod, legacy, obb and TWRP) which I couldn't see in ES-File explorer before. Because I was a little confused (and angry because I never had something like this happening) I just rebooted my device and connected it to my pc to see what I can access from there. But it was the same result like with the manager, there were no folders at all . So I went back into my recovery and just looked a bit around and after a while I found out that the whole /sdcard files just moved to the "0" folder that is inside the "old" sdcard-directory. And this is kind of where I am at right now not knowing what to do to get everything back to normal. I hope there is a way I can recover all of my files or at least a way that I can move them to my pc (had a few backups on there that I was too lazy to move which I do regret now...). If there is someone who understood my post and knows a solution to my problem please help me! I am actually quite lost right now because I can't even use Whatsapp without loosing all of my messages
I am sorry that I can't give you any pictures of my phones status but I don't know how I could do a screenshot/video in TWRP :/
Edit: I found an older device of myself with which I was able to take some pictures (has very bad quality because it has a little crack in the camera)
On InternerSpeicherSeite1 you can see that on my pc it shows that storage is used up but on InternerSpeicherSeite2 you can see that it is empty if I open it.
In ES you can see that there is this /legacy instead of /sdcard.
In TWRP1 you can see that the whole /scard directory is nearly empty.
In TWRP2 is the /sdcard direcory that is now in /sdcard/0 but unaccesable from anywhere except TWRP.
R4gi3X said:
Hi together,
earlier I wanted to finally give the L-Preview a shot so I downloaded it and installed it as it was mentioned in the thread's instructions. Everything was fine until I was forced to reinstall it because Wifi kept getting stuck at switching (which didn't fix itself after a reboot) and some other things. So I did everything again like I did before but after I booted it up again and set up everything I noticed that in ES-File manager I couldn't access my sdcard directory. So I booted back into my recovery and saw that even there my usual sdcard directory was nearly gone except for a few folders (0, clockwordmod, legacy, obb and TWRP) which I couldn't see in ES-File explorer before. Because I was a little confused (and angry because I never had something like this happening) I just rebooted my device and connected it to my pc to see what I can access from there. But it was the same result like with the manager, there were no folders at all . So I went back into my recovery and just looked a bit around and after a while I found out that the whole /sdcard files just moved to the "0" folder that is inside the "old" sdcard-directory. And this is kind of where I am at right now not knowing what to do to get everything back to normal. I hope there is a way I can recover all of my files or at least a way that I can move them to my pc (had a few backups on there that I was too lazy to move which I do regret now...). If there is someone who understood my post and knows a solution to my problem please help me! I am actually quite lost right now because I can't even use Whatsapp without loosing all of my messages
I am sorry that I can't give you any pictures of my phones status but I don't know how I could do a screenshot/video in TWRP :/
Click to expand...
Click to collapse
Move all your folders and files back to the old place, or get them to your pc with adb pull (use google if you want to now how) and flash the factory image for safety
You can learn to adb pull by clicking the link in my signature and then locating the adb and fastboot thread
Don't adb push your data back though. Adb pushing your entire sdcard back will cause permissions problems so use MTP to transfer data back
Sent from my Nexus 5 using Tapatalk
its a common issue with L, i even experienced it myself. first, there is a short terminal emulator command you can use. i dont know what it is, but a search should find it for you. itll move all back to where it should be. or secondly, you can do what i did. i didnt know there was a terminal command, so i used root explorer to move everything back manually. took me about 15-20 minutes.
GtrCraft said:
Move all your folders and files back to the old place, or get them to your pc with adb pull (use google if you want to now how) and flash the factory image for safety
Click to expand...
Click to collapse
rootSU said:
You can learn to adb pull by clicking the link in my signature and then locating the adb and fastboot thread
Don't adb push your data back though. Adb pushing your entire sdcard back will cause permissions problems so use MTP to transfer data back
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I already know how to adb pull but it just gives me the output seen on the picture...
there appears to be 3 different terminal emulator scripts people have been using, one for for some but not for others. heres one that i found, try it out in a terminal emulator app..
su(press enter)
restorecon -r /data/media/0/*(press enter)
simms22 said:
there appears to be 3 different terminal emulator scripts people have been using, one for for some but not for others. heres one that i found, try it out in a terminal emulator app..
su(press enter)
restorecon -r /data/media/0/*(press enter)
Click to expand...
Click to collapse
I've tried your command but it did nothing.
But I found a way simpler solution now, as I could still access my data in TWRP I was able to flash a 4.4.4 Rom (that I luckily still had on my phone^^) and now I can access everything including the "0" Folder on my pc again. So I'll move everything on my pc now and then copy it to the /sdcard directory
Thanks though for your help, really appreciate the support from the xda-community!!
But I gotta say good night now as it is already 1am but I will update this post one more time tomorrow giving a final result.
You already know /sdcard isn't working properly. Pull /data/media/0

Categories

Resources