Related
Okay i have a big problem...
I have rooted my device, however didn't run the ENG build, so my recovery is dependent on the pushing of the update.zip...
I flashed the myfroyo5 after pushing the update.zip... and ADB worked great, found the device in HBOOT and recovery.
Now after flashing this ROM, when i try and reboot back HBOOT no devices found.. however when i'm at the home screen with Myfroyo5 booted up, it sees the device..
Now i can't run any update, or get into clockwork recovery because i can't push the update.zip, because ADB can't see my device....
Please help! Any idea how i can get it to see my device with Myfroyo5? Otherwise i'm stuck with Myfroyo5 and can't reverse or do anything with it
Before all i did was change the option from device storage, to charge only, and that's how it worked...
again any ideas are appreciated!
wow 58 views and no one has any ideas? Please help!
Try turning on USB debugging mode?
Yes its always on, always check marked
I feel like I did have a similar problem at one point, but I don't remember how I resolved it. Sorry.
gee maybe you should have flashed the eng build as everyone was told to do when they rooted their slide. try a dozen different large and small SD cards, i don't really think that is what makes it work but others seem to disagree and maybe once you swap them out you'll get lucky. but first i would try flashing the eng build
tubaking182 said:
gee maybe you should have flashed the eng build as everyone was told to do when they rooted their slide. try a dozen different large and small SD cards, i don't really think that is what makes it work but others seem to disagree and maybe once you swap them out you'll get lucky. but first i would try flashing the eng build
Click to expand...
Click to collapse
Must your replies always, ALWAYS have some snarky bit about how the person asking the question screwed up?
Humans are prone to error. You have valuable insight but beating someone's ego up before you give it really offsets your kindness.
Sent from my T-Mobile myTouch 3G Slide using XDA App
They don't always have snarky bits, but when 90% of problems are caused by not following directions then it apparently needs to be retold, I help a lot and I gave ideas to try here. Odds are he can still flash the eng build and then get into clockwork, but not following directions causes issues like this.
Sent from my T-Mobile myTouch 3G Slide using XDA App
I see your point but, as I recall, the ENG build came after root had been put out there for a day or so. I'm also pretty sure it came after SlideMeRoot1.
Things like this, along with simple mistakes, can cause these errors. You are helpful but I just find the "hey, dummy" tone to be overkill.
Not everyone who screws up is out to **** up your day, ya know? I've been having my own ENG build problems because I made a mistake. It doesn't mean I don't know how to follow directions, it just means I made a mistake, the way every human on the planet does.
I apologize, as well, because my own real life smiley fun tone doesn't translate well to the forum. IE: you good kid.
tubaking182 said:
They don't always have snarky bits, but when 90% of problems are caused by not following directions then it apparently needs to be retold, I help a lot and I gave ideas to try here. Odds are he can still flash the eng build and then get into clockwork, but not following directions causes issues like this.
Sent from my T-Mobile myTouch 3G Slide using XDA App
Click to expand...
Click to collapse
Sent from my T-Mobile myTouch 3G Slide using XDA App
well first off.. i did follow directions... and it didn't work... and i've flashed multiple roms by just re-doing the ota.zip then the update.zip push, to get me into clockwork, until i flashed myfroyo5
which does not allow me to "charge only" which is why ADB doesn't allow to recognize my device in HBOOT/Recovery.
On the contra-ire i do know what i'm doing however a little bit of "knowledge" to point out maybe something that will fix an issue i have would be great.
Now i'm running myfroyo5, the device is seen by adb when the phones booted up, however upon reset to HBOOT/Recovery no devices are found. I've tried putting ENG build on my Sdcard, and HBOOT doesn't see it, also, i've tried pushing flash_image to /data/local, and mtd0.img to /data/local, and the files will not move.
That is part of my problem i'm assuming, i'll try another SD card to see if it will fix it, but i'm not sure its something that simple... but who knows, right?
javolin13 said:
well first off.. i did follow directions... and it didn't work... and i've flashed multiple roms by just re-doing the ota.zip then the update.zip push, to get me into clockwork, until i flashed myfroyo5
which does not allow me to "charge only" which is why ADB doesn't allow to recognize my device in HBOOT/Recovery.
On the contra-ire i do know what i'm doing however a little bit of "knowledge" to point out maybe something that will fix an issue i have would be great.
Now i'm running myfroyo5, the device is seen by adb when the phones booted up, however upon reset to HBOOT/Recovery no devices are found. I've tried putting ENG build on my Sdcard, and HBOOT doesn't see it, also, i've tried pushing flash_image to /data/local, and mtd0.img to /data/local, and the files will not move.
That is part of my problem i'm assuming, i'll try another SD card to see if it will fix it, but i'm not sure its something that simple... but who knows, right?
Click to expand...
Click to collapse
Just use CR new root method for the ota update and then follow the steps to flash ENG build. wouldnt that work? cause its unneccessary for the device to be recognized in hboot in adb that way =\ just guesing
i would do all that too.... you know i think the issue is the copying the files over... none of them are actually moving where they need to go!...
And when i try to do it manually the folder says "read only file system" and when i try to push files it says "1188 KB/s <0 bytes in XXXX.000s>
so none of the image files are moving over to allow me to flash ENG build... i swapped different SD cards and now i can flash the ENG build, but i cant move the files to /data/local before i do that, so right now its pointless to flash it...
javolin13 said:
i would do all that too.... you know i think the issue is the copying the files over... none of them are actually moving where they need to go!...
And when i try to do it manually the folder says "read only file system" and when i try to push files it says "1188 KB/s <0 bytes in XXXX.000s>
so none of the image files are moving over to allow me to flash ENG build... i swapped different SD cards and now i can flash the ENG build, but i cant move the files to /data/local before i do that, so right now its pointless to flash it...
Click to expand...
Click to collapse
do u have root in the shell script when u try to push the files over?
yes i do, that's whats really weird... i do adb shell, and i get #
when i do it the cat way, it does what it needs to, yet when i go search for the files using linda file manager they're still not there...
i dont want to flash eng build and it not work...
javolin13 said:
yes i do, that's whats really weird... i do adb shell, and i get #
when i do it the cat way, it does what it needs to, yet when i go search for the files using linda file manager they're still not there...
i dont want to flash eng build and it not work...
Click to expand...
Click to collapse
i mean u could always just unroot and start from square one
can't unroot if my device is not seen with adb in hboot / recovery
javolin13 said:
well first off.. i did follow directions... and it didn't work... and i've flashed multiple roms by just re-doing the ota.zip then the update.zip push, to get me into clockwork, until i flashed myfroyo5
which does not allow me to "charge only" which is why ADB doesn't allow to recognize my device in HBOOT/Recovery.
On the contra-ire i do know what i'm doing however a little bit of "knowledge" to point out maybe something that will fix an issue i have would be great.
Now i'm running myfroyo5, the device is seen by adb when the phones booted up, however upon reset to HBOOT/Recovery no devices are found. I've tried putting ENG build on my Sdcard, and HBOOT doesn't see it, also, i've tried pushing flash_image to /data/local, and mtd0.img to /data/local, and the files will not move.
That is part of my problem i'm assuming, i'll try another SD card to see if it will fix it, but i'm not sure its something that simple... but who knows, right?
Click to expand...
Click to collapse
I had the same problem just about and used the following thread. http://forum.xda-developers.com/showthread.php?t=710056 <-- BIG THANKS to Beartard for taking the time to type this all out. It worked just fine. I picked it up from - Installing the Engineering ROM - I kept my old update.zip file on the root of my sd card, and I got everthing back to normal, and everything works like new. Hope this helps
Suntar said:
I had the same problem just about and used the following thread. http://forum.xda-developers.com/showthread.php?t=710056 <-- BIG THANKS to Beartard for taking the time to type this all out. It worked just fine. I picked it up from - Installing the Engineering ROM - I kept my old update.zip file on the root of my sd card, and I got everthing back to normal, and everything works like new. Hope this helps
Click to expand...
Click to collapse
Thanks for the idea, but flashing the ENG build is pointless unless i can push the flash_image, and mtd0.img to /data/local... which for some reason my phone will not allow me to do this part;
Code:
type "adb push flash_image /data/local" and hit enter.
2. Type "adb push mtd0.img /data/local" and hit enter.
So I'm not fluent in the linux terminal. I'm basically illiterate, deaf and dumb. So here I am trying to root using toasts tutorial, How To Root The HTC EVO ~ Part-1 \0/
the forum won't let me post links yet., and apparently the software here thinks some part of the code I'm posting is a link.
Anyway I'm at this step,
- At this point it will boot into a rooted rom.
- YOU ARE NOW ROOT!!!
- rename the PC36IMG.zip on your sdcard:
- plug your phone into a usb port on your desktop and do:
Click to expand...
Click to collapse
I may be root but I had a problem and had to redo this step... my sdcard was not being recognized. After reflashing/ updating I was able to access it again.
Now this rename the zip file step... I'm thinking if I rename it the code I'm supposed to enter isn't going to work. What should I rename it to?
How should I enter this code? first off my sd card isn't called sdcard it's called an 8 digit number.
I tried this (can't post the code for some reason) without changing the name of the zip file. I'm thinking I don't have the locations right because I know the file is in there.
I need some direction to get to the next step.
Thanks
Mods please move this thread....
to wherever it will get the most or correct exposure. Sorry if I put it in the wrong place.
i have no idea what your doing...i rooted via the unREVOked method...i had to downgrade to 2.1, then actually root...can u send me a PM with what tutorial your following? and also the current info you have for your phone, like what its running (2.1 or 2.2) and stuff of that nature.... we shall see if i can help, not sure but its worth a shot
okay form what i read you have already flashed the .zip. Make sure you clear your data and cache as these will cause boot loops if not cleared. Also you can rename the .zip to anything you want, this just makes it so the bootloader does not try to install the .zip a second time.
oshizzle1991 said:
i have no idea what your doing...i rooted via the unREVOked method...i had to downgrade to 2.1, then actually root...can u send me a PM with what tutorial your following? and also the current info you have for your phone, like what its running (2.1 or 2.2) and stuff of that nature.... we shall see if i can help, not sure but its worth a shot
Click to expand...
Click to collapse
I'm running 2.1. I never upgraded. The tutorial I'm following is in thread #690762 I'll try to pm the link but I don't think they'll let me. I thought unrevoked wasn't a full root. I want to unlock nand. I'm also using Ubuntu here, not windows.
http://forum.xda-developers.com/showthread.php?t=690762
nfaust01 said:
okay form what i read you have already flashed the .zip. Also you can rename the .zip to anything you want, this just makes it so the bootloader does not try to install the .zip a second time.
Click to expand...
Click to collapse
Nice looks like I'm allowed to put up links now... Thanks!
Yes I flashed the .zip my phone called it "updating" when it was going on.
Make sure you clear your data and cache as these will cause boot loops if not cleared.
Click to expand...
Click to collapse
Do I do that from the boot menu?
Also you can rename the .zip to anything you want, this just makes it so the bootloader does not try to install the .zip a second time.
Click to expand...
Click to collapse
I just removed the .zip part. What is the point of the next step, which I couldn't get to work, if I rename the file?
Code:
adb shell mv /sdcard/PC36IMG.zip /sdcard/root-PC36IMG.zip
Well I guess I'm going to start over and wait for the latest unrevoked to come back out. Thanks to everyone that tried to help. "NO ROOT FOR YOU!"
You have a lot to learn....
First of all, don't rename the sdcard, rename pc36img.zip. Just rename it to anything you want so boat loader doesn't recognize it and try to update itself. Next, you aren't utilizing root. You do have a rooted boot loader, but you are still using a protected recovery and rom. Install a custom recovery and flash a new rom so you can be cool.
dkdude36 said:
First of all, don't rename the sdcard, rename pc36img.zip
Click to expand...
Click to collapse
Yes, I know I have a lot to learn. I didn't rename the sdcard, that wasn't possible. I figured part of the problem with getting this to work was the path. My sdcard wasn't called sdcard it was called some 8 digit number. I eventually worked around pushing the file to the sd card by installing the phone as a drive and dragging the file to the sdcard.
Just rename it to anything you want so boat loader doesn't recognize it and try to update itself.
Click to expand...
Click to collapse
After I rebooted and updated/ flashed the file, I renamed the file on the sdcard by removing the .zip. I did this via disk drive on my laptop because I wasn't getting anywhere with the command line.
Again this part didn't make any sense to me, not that most of it does, but what was the point of the next command in the directions if I renamed the file?
Next, you aren't utilizing root. You do have a rooted boot loader, but you are still using a protected recovery and rom. Install a custom recovery and flash a new rom so you can be cool.
Click to expand...
Click to collapse
Right "I have a lot to learn" I thought following the directions in toasts tutorial step by step would have gotten me to that point. I didn't realize I was just supposed to skip stuff when I run into problems. That kinda seems like what your telling me to do. I thought all of the commands were important.
I was hoping you had some follow up insight dkdude.
if you still on 2.1, try this method (just make sure the files aren't corrupted)
http://forum.xda-developers.com/showthread.php?t=741294
I followed 2 guides to get my phone rooted and get my HBOOT patched to allow S-OFF - AlphaRev and Clockwork Recovery 2.5.0.1.
I want to get rid of the Joker from start up - had I would of known that I would of remained S-ON till they fixed that. That did permanently add Clockwork Recovery to the recovery area. There is a new version I downloaded and told it to install from ZIP and it reloaded and came to 2.5.0.7 but it never permanently patched it in. I am seriously considering going to AmonRA if it is available - I have done so many searches my head is spinning from lack of finds.
Am I missing something or is this something that needs to be done via ADB/Fastboot? If thats the case, I may need some help.
Permanently flashing recoveries has to be done through fastboot with a .img file, the update.zip way will never permanently flash a recovery, unfortunately. Here is a download link for the 2.5.0.7 recovery image, here's how you flash it (you must have the android sdk installed, and you have to have the fastboot.exe command in either \tools or \platform-tools):
Open up a command prompt window and type this:
fastboot flash recovery C:\location\of\recovery.img
When you reboot into recovery again via hboot, it should be 2.5.0.7.
As for the splash screen, that can be changed too (thank god, I hated the joker screen as well). Follow the instructions on this thread, there are plenty of screens to choose from, including the stock t-mobile screen.
If you need anything better explained, I can try to better explain it.
Thanks for the tips. I did find one I wanted - simple and Tmobile-ish. I do have the SDK installed with all updates from the Java Frontend that it uses BUT I still do not have fastboot.exe
I tried one from a friend but it keeps sticking at WAITING FOR DEVICE. Do I need to be in fastboot first on the phone then do this? It is detecting the phone with ADB devices command.
I'm pretty sure you need to be in fastboot to do this. Why the need for permanent recovery anyway?
I tried fastboot mode on the phone and it worked - Thanks for the tip! Flashed just fine and with help of some of the threads on the themes area i got the splash screen modified. (joker is gone - thank goodness!)
I am wanting to change the boot animation - I know how that works but I can't seem to find any for the MT3GS.
Again, I appreciate the tips. They have been helpful. ( I had to transpose what your talking about to the mac - and find fastboot for the mac - HTC had it on their site with a google search )
Yeah, for some reason google stopped compiling fastboot.exe for the sdk, it sucks. I just kept mine from older revisions of the sdk, and I copy it over whenever there's an update.
And at least for me, (@ whoever asked), permanent recoveries are significantly more convenient, and it saves time. It's nice to actually be able to use hboot recovery option, bypassing the stock recovery. It's also nice to be able to write to /system without a r/w overlay or without having to be in recovery.
MusicMan374 said:
Yeah, for some reason google stopped compiling fastboot.exe for the sdk, it sucks. I just kept mine from older revisions of the sdk, and I copy it over whenever there's an update.
And at least for me, (@ whoever asked), permanent recoveries are significantly more convenient, and it saves time. It's nice to actually be able to use hboot recovery option, bypassing the stock recovery. It's also nice to be able to write to /system without a r/w overlay or without having to be in recovery.
Click to expand...
Click to collapse
Not only that but it keeps that wonderfull 800k space free I am a space freak and like all free space and things organized. But the fact that if I screw up a flash - and for some reason I don't have a rom downloaded I can pop in my NANDROID backup card (which is stored in a safe under my foundation) and restore. That way I don't have to download update.zip anymore.
But I am seriously considering AmonRA - I just can't find a copy for my phone. Looks like it is for older phones unless I am missing something.
Does this phone support any other MicroSD cards 16GB or above?
thronka said:
Not only that but it keeps that wonderfull 800k space free I am a space freak and like all free space and things organized. But the fact that if I screw up a flash - and for some reason I don't have a rom downloaded I can pop in my NANDROID backup card (which is stored in a safe under my foundation) and restore. That way I don't have to download update.zip anymore.
But I am seriously considering AmonRA - I just can't find a copy for my phone. Looks like it is for older phones unless I am missing something.
Does this phone support any other MicroSD cards 16GB or above?
Click to expand...
Click to collapse
There is no AmonRA recovery for our phone, I don't believe. It was requested of him after we got s-off, but we don't know since he doesn't own a slide, and it's awfully hard to develop for a phone you don't have, haha
Well the easiest way to flash a recovery is to make sure you have CM7, or CM6, or separately put the files, MTD0 and Flash_Image in /Data/Local So if you have that, Here it is:
You just need to go to terminal Emulator type
Su
Flash_image recovery /sdcard/xxxx/xxxx.img
(Making sure you realize that the x's represent directories and file names)
For example I would put mine on the Root of the SD card and mine would look like this
Flash_Image recovery /sdcard/recovery.img
Sent from my T-Mobile myTouch 3G Slide using XDA App
iDaZzLeFatHoeZz said:
Well the easiest way to flash a recovery is to make sure you have CM7, or CM6, or separately put the files, MTD0 and Flash_Image in /Data/Local So if you have that, Here it is:
You just need to go to terminal Emulator type
Su
Flash_image recovery /sdcard/xxxx/xxxx.img
(Making sure you realize that the x's represent directories and file names)
For example I would put mine on the Root of the SD card and mine would look like this
Flash_Image recovery /sdcard/recovery.img
Sent from my T-Mobile myTouch 3G Slide using XDA App
Click to expand...
Click to collapse
Been flashed for a while now. I did not know this method but it is good to have and try when there is an update.
I have been tinkering with the ArayrayMod Revamped files since Arayray moved on to a MyTouch 4G. (traitor! LOL)
Looks like I may be going into the developing side of roms but I am just waiting for approval to post the rom for public viewing. a .32 kernel with Wifi calling included and thats really it - well retaining OC on that rom as well.
Much more tough than I thought doing this by hand - and I always thought my Unix Administration skills would be wasted.
I have the Hong Kong variant of the Galaxy Nexus GSM (yakjuzs) running 4.0.2.
I haven't even unlocked the bootloader yet. (Stupid, I know.)
I've had the phone long enough to know "how it's supposed to behave" so that when I unlock and root a ROM I'll know if something is behaving badly, so now I'm looking to switch to the latest/greatest yakju (who comes up with these terrible names?) 4.0.4.
However, before I do so, I'd like a perfect backup of my phone 'as-is' so that if something goes horribly, horribly wrong I can get back to the 'original state'.
Now, I've done some reading around and I'm confused. It looks like I need several different kinds of backups, and I'm not even sure if all of them are going to be 'worth it'.
First, I found the Galaxy Nexus Toolkit. It only mentions the yakju variant, not my yakjuzs, but it "seems to" work for making a backup of my phone's data. I just haven't tested the backups, nor do I know how to, so I don't know if it's actually working or not.
I'm just not sure what it's backing up. It's obviously NOT backing up the ROM or radios (is there anything else it's not backing up?), and I don't know what it means by "System Apps", nor "apps data". Obviously it's backing up all the APKs I've installed from the market, etc. That part I get. What else is it backing up? (I know it's also backing up the virtual SD card if I tell it to, as long as I uninstall Google Currents first, which seems to have a directory structure that doesn't jive well with Win7.)
Secondly, I found this thread about backing up the Desire S which I'm going to take a wild guess and say that the advice given in it still applies to my phone as well: namely that a "NANDROID" backup will backup the ROM and radios and other 'stuff' on my phone that the GNT doesn't grab.
Thing is: I don't know what "Clockwork Recovery Mod" or "NANDROID" are, or where to get them. If I Google "Clockwork Recovery Mod", it takes me to this page which doesn't have anything on it called "Recovery Mod" at all. Is it the "ROM Manager" app?
A little more Googling suggests that this is true, or at least that I can get "Clockwork Recovery Mod" through that app (weird way of getting it, honestly), but I thought I'd ask here first.
Is "NANDROID" a part of CRM? I'd use this, which is the first thing that shows up when I Google 'Nandroid', but it seems to be four years old, and references phones that I might not even be able to find on eBay, so I'm thinking it's not a trustworthy source.
Of course, all of this requires root, right? I've been told this requires unlocking the Bootloader, though I do see this exploit that lets you get Root without doing that. So, basically, I can root with that exploit, then download that 'ROM Manager', use it to flash CRM over my locked Bootloader, then use that to do a NANDROID backup of my phone?
Right?
And, regarding that whole 'rooting/superuser' thing, I know that the 'standard' is to use 'superuser.apk' for root permissions for apps. I've read about SuperSU, the 'superior' superuser alternative. Does that require superuser.apk, or can it be used as a replacement for it? And if it can be a replacement for superuser.apk, does that mean I can use it *instead* of superuser.apk in that root exploit? How would I get the APK to use? Buy it on the market, and then somehow (adb pull? Is that it?) take the APK off of my phone and on to my computer?
I'm asking mostly because any app that checks for 'root permissions' (such as Google Movies Play Movies Play Play Movies or whatever it's called) apparently dislikes root permissions being available on a phone, but only checks for a file called 'superuser.apk'. If I don't have that file, no problem, right?
Finally, how do I get the 4.0.4 yakju straight-from-Google ROM? Do I need new radios for that? Where do I get those? No, I don't want AOKP or CM9.
Moleculor said:
[snip]
Of course, all of this requires root, right? I've been told this requires unlocking the Bootloader, though I do see this exploit that lets you get Root without doing that. So, basically, I can root with that exploit, then download that 'ROM Manager', use it to flash CRM over my locked Bootloader, then use that to do a NANDROID backup of my phone?
Right?
Click to expand...
Click to collapse
Right. Root with the exploit, install ROM Manager from the market, use ROM Manager to flash CWM recovery, boot into CWM recovery, and perform a (nandroid) backup. This will be saved in a folder in /sdcard. Now you have to pull all of the data off your phone somehow*, and save it to your computer. Then follow this guide to flash yakju 4.0.4.
*The easiest way to pull the data off your device is to boot into CWM recovery, and plug into your computer (assuming you have the drivers set up properly), open a command prompt in the directory where you have your adb.exe file, and type adb pull /data/media. This will put everything in /sdcard onto your computer.
Moleculor said:
And, regarding that whole 'rooting/superuser' thing, I know that the 'standard' is to use 'superuser.apk' for root permissions for apps. I've read about SuperSU, the 'superior' superuser alternative. Does that require superuser.apk, or can it be used as a replacement for it? And if it can be a replacement for superuser.apk, does that mean I can use it *instead* of superuser.apk in that root exploit? How would I get the APK to use? Buy it on the market, and then somehow (adb pull? Is that it?) take the APK off of my phone and on to my computer?
I'm asking mostly because any app that checks for 'root permissions' (such as Google Movies Play Movies Play Play Movies or whatever it's called) apparently dislikes root permissions being available on a phone, but only checks for a file called 'superuser.apk'. If I don't have that file, no problem, right?
Finally, how do I get the 4.0.4 yakju straight-from-Google ROM? Do I need new radios for that? Where do I get those? No, I don't want AOKP or CM9.
Click to expand...
Click to collapse
Just flash su and you will be fine. There are still some issues with supersu that have not been sorted out yet. (And by the way, the file that the apps look for is su, not Superuser.apk. Superuser.apk does not give root access - it basically acts as a firewall for apps requesting root from the su binary.)
efrant said:
Right. Root with the exploit, install ROM Manager from the market, use ROM Manager to flash CWM recovery, boot into CWM recovery, and perform a (nandroid) backup. This will be saved in a folder in /sdcard.
Click to expand...
Click to collapse
Ok, this is one thing I've never understood: I don't have an /sdcard, or at least I don't see it. Is this because I don't have root, and thus when I access my phone's internal storage, it's shortcutting me directly into /sdcard as if it's the root directory, thus I never see the directory /sdcard is in?
efrant said:
Now you have to pull all of the data off your phone somehow*, and save it to your computer. Then follow this guide to flash yakju 4.0.4.
*The easiest way to pull the data off your device is to boot into CWM recovery,
Click to expand...
Click to collapse
Ok. Wat? I've booted into the stock bootloader once before, would I do that same process to get into CWM recovery once CWM recovery is installed? And can a CWM recovery be installed on a phone with a locked bootloader (but with root)? Or should I just bite the bullet and unlock the bootloader?
efrant said:
and plug into your computer (assuming you have the drivers set up properly), open a command prompt in the directory where you have your adb.exe file, and type adb pull /data/media. This will put everything in /sdcard onto your computer.
Click to expand...
Click to collapse
Wait, what? Ok. I'm an ancient IBM-DOS and MS-DOS user, so I 'get' directory structures, but... where exactly is /sdcard? What's the directory structure of the phone like? Because /data/media doesn't exactly scream "/sdcard" to me.
efrant said:
Just flash su and you will be fine. There are still some issues with supersu that have not been sorted out yet.
Click to expand...
Click to collapse
Aww. SuperSU looked so nifty.
efrant said:
(And by the way, the file that the apps look for is su, not Superuser.apk. Superuser.apk does not give root access - it basically acts as a firewall for apps requesting root from the su binary.)
Click to expand...
Click to collapse
Hm. So if the APK were to instead look for... say... "tacolicker" instead of "su" for root access, apps that detect root would be less likely to find root access and be all DRM-y?
----
Also, I downloaded the binaries for 4.0.4 from the AOSP, including radios, drivers, etc. Do I leave them in the tarballs? (Those are called tarballs, right? The TGZ files? Only used linux for two minutes in my life, not counting this phone,) Or do I extract them first? And I'm assuming some of this goes onto my phone... somehow?
Moleculor said:
Ok, this is one thing I've never understood: I don't have an /sdcard, or at least I don't see it. Is this because I don't have root, and thus when I access my phone's internal storage, it's shortcutting me directly into /sdcard as if it's the root directory, thus I never see the directory /sdcard is in?
Click to expand...
Click to collapse
Yes, it is shortcutting you there.
Moleculor said:
Ok. Wat? I've booted into the stock bootloader once before, would I do that same process to get into CWM recovery once CWM recovery is installed? And can a CWM recovery be installed on a phone with a locked bootloader (but with root)? Or should I just bite the bullet and unlock the bootloader?
Click to expand...
Click to collapse
Yes, CWM can be installed with root and a locked bootloader. What I suggested to do is root, install CWM, backup, then unlock.
Moleculor said:
Wait, what? Ok. I'm an ancient IBM-DOS and MS-DOS user, so I 'get' directory structures, but... where exactly is /sdcard? What's the directory structure of the phone like? Because /data/media doesn't exactly scream "/sdcard" to me.
Click to expand...
Click to collapse
That is because /sdcard is just a symlink (linux term -- just a link/shortcut) to /data/media, which is the actual directory.
Moleculor said:
Aww. SuperSU looked so nifty.
Hm. So if the APK were to instead look for... say... "tacolicker" instead of "su" for root access, apps that detect root would be less likely to find root access and be all DRM-y?
Click to expand...
Click to collapse
Yes.
Moleculor said:
Also, I downloaded the binaries for 4.0.4 from the AOSP, including radios, drivers, etc. Do I leave them in the tarballs? (Those are called tarballs, right? The TGZ files? Only used linux for two minutes in my life, not counting this phone,) Or do I extract them first? And I'm assuming some of this goes onto my phone... somehow?
Click to expand...
Click to collapse
Follow the directions in the link I provided in my previous post. If you do that, you will need to extract everything: the tgz, the tar, and the zip inside.
efrant said:
Yes, CWM can be installed with root and a locked bootloader. What I suggested to do is root, install CWM, backup, then unlock.
Click to expand...
Click to collapse
Ok, just to completely clarify... to boot into CWM Recovery, I hold both volume buttons and turn the phone on? Or is that just the bootloader, and Recovery is something different? Or am I right, but I'm missing a step?
efrant said:
That is because /sdcard is just a symlink (linux term -- just a link/shortcut) to /data/media, which is the actual directory.
Click to expand...
Click to collapse
S'what I thought. They use the same thing in Win7, apparently.
Thanks!
Moleculor said:
Ok, just to completely clarify... to boot into CWM Recovery, I hold both volume buttons and turn the phone on? Or is that just the bootloader, and Recovery is something different? Or am I right, but I'm missing a step?
Click to expand...
Click to collapse
To boot into CWM recovery (after you flash it), you can:
1) Hold both volume buttons and turn the phone on to get you into the bootloader, then scroll with the volume buttons until you see recovery and then select it with the power button; or
2) Install Quick Boot from the market. Awesome app.
---------- Post added at 10:38 PM ---------- Previous post was at 10:34 PM ----------
Moleculor said:
[snip]
Also, I downloaded the binaries for 4.0.4 from the AOSP, including radios, drivers, etc. Do I leave them in the tarballs? (Those are called tarballs, right? The TGZ files? Only used linux for two minutes in my life, not counting this phone,) Or do I extract them first? And I'm assuming some of this goes onto my phone... somehow?
Click to expand...
Click to collapse
And you don't need to download the binaries. All you need to download is the IMM76D "factory images" found here: http://code.google.com/android/nexus/images.html
efrant said:
To boot into CWM recovery (after you flash it), you can:
1) Hold both volume buttons and turn the phone on to get you into the bootloader, then scroll with the volume buttons until you see recovery and then select it with the power button; or
2) Install Quick Boot from the market. Awesome app.
Click to expand...
Click to collapse
Excellent. Thanks. So Recovery shows up as another option in the bootloader. Or something.
efrant said:
And you don't need to download the binaries. All you need to download is the IMM76D "factory images" found here: http://code.google.com/android/nexus/images.html
Click to expand...
Click to collapse
Ohh, good to know, since I downloaded both that AND the drivers. So, no drivers, just that one image. K.
Dumb question: What's 'fastboot'? I "get" adb... but what's "fastboot"?
Moleculor said:
Dumb question: What's 'fastboot'? I "get" adb... but what's "fastboot"?
Click to expand...
Click to collapse
Nexus devices have two interfaces: fastboot and ADB.
Fastboot commands (used via the fastboot.exe file) can only be used when your device is booted in the bootloader (or fastboot mode).
ADB commands (used via the adb.exe file, along with two .dll files) can only be used when your device is booted normally with USB Debugging enabled in your device's settings, or booted into CWM.
They each do different things. For example, fastboot allows you to unlock/re-lock your bootloader, flash images to partitions on your device, boot kernels on your device without flashing them, erase partitions, etc. ADB has a set of commands that let you interface with the OS. As well, it allows you to execute shell commands directly on the phone using adb shell.
Aha. Weird that there would be two separate interfaces... unless technically the bootloader and Android are two separate OSes?
Final questions I hope (since I have your attention)... this might actually be more appropriate in the exploit thread, but once I have root access, how do I clean up after myself? i.e. Delete the files I put into /data/local/tmp? Did I create the /tmp directory when I pushed those files onto the phone, or is there other stuff in there too?
EDIT:Scratch that, I just used cd, ls, and rm to remove the files, rmdir to remove the ../tmp directory... but now I note that /data/local is empty too. Can I safely delete that?
Does the ROM Manager ROM backup thing that I'm running (is this nandroid? I didn't have to boot into the bootloader to do it) back up the /data/local/tmp directory? If so, I think I might need to delete my ROM backup, delete those files, and rerun the backup.
It's running now. I'm assuming it's dumping everything into one file, or something?
And is this the nandroid backup thing, or is that something in the recovery mode?
Actually, where can I read about the directory structure and all what each directory is for? /data/media is the fake SD Card, obviously, so what's /data/local? Etc.
Moleculor said:
Aha. Weird that there would be two separate interfaces... unless technically the bootloader and Android are two separate OSes?
Click to expand...
Click to collapse
Think of the bootloader as the BIOS, nothing more. The recovery is like a mini OS.
Moleculor said:
Final questions I hope (since I have your attention)... this might actually be more appropriate in the exploit thread, but once I have root access, how do I clean up after myself? i.e. Delete the files I put into /data/local/tmp? Did I create the /tmp directory when I pushed those files onto the phone, or is there other stuff in there too?
EDIT:Scratch that, I just used cd, ls, and rm to remove the files, rmdir to remove the ../tmp directory... but now I note that /data/local is empty too. Can I safely delete that?
Click to expand...
Click to collapse
No, you did not create the /tmp directory. And there is no harm in leaving the three files there, but feel free to remove them.
Moleculor said:
Does the ROM Manager ROM backup thing that I'm running (is this nandroid? I didn't have to boot into the bootloader to do it) back up the /data/local/tmp directory? If so, I think I might need to delete my ROM backup, delete those files, and rerun the backup.
Click to expand...
Click to collapse
Yes, a backup in CWM is called a nandroid backup. The three files that you copied there don't matter. They can be deleted at any time, with or without root.
Moleculor said:
It's running now. I'm assuming it's dumping everything into one file, or something?
And is this the nandroid backup thing, or is that something in the recovery mode?
Click to expand...
Click to collapse
It's creating a backup and storing it in /clockworkmod/backup/
Moleculor said:
Actually, where can I read about the directory structure and all what each directory is for? /data/media is the fake SD Card, obviously, so what's /data/local? Etc.
Click to expand...
Click to collapse
Look in these forums. When I first started, I spent hours reading before I attempted anything.
[HOWTO] ClockworkMod Recovery & TWRP - Upgrade/Downgrade (Touch/Non-Touch Recovery)
IF YOU TRASH YOUR PHONE USING THIS PROCEDURE, THEN IT IS A VERY GOOD INDICATION YOU ARE AN IDIOT AND SHOULD NOT BE FLASHING ANY ROMS NOR PARTICIPATING ON THESE FORUMS. . . . JUST SAYIN'. . . .
Please be VERY careful when using this method as you can brick your phone. Make sure you triple check the file you downloaded is the right size and placed in the right area, but most importantly that the command lines you type are exactly right. If you are not comfortable using this method, then please do not and go find a flashable version of these recoveries.
I've posted a procedure to format/'flash' your recovery while on your phone in one of the threads on here and was asked by a Forum Mod to make a quickie guide to be placed as a sticky on the dev boards so others might benefit.
Anyway, here is a very quick and easy way to change your ClockworkMod recovery with a couple of command lines.
The TWRP link is in the second post.
Now for the ClockworkMod Instructions:
1. First, go here and look up your ClockworkMod recovery that pertains to your phone: http://www.clockworkmod.com/rommanager
2. Download the .img file for your phone and save it on your computer.
3. Rename the .img file to recovery.img and save it to your internal sd card of your phone. For example: recovery-clockwork-6.0.1.4-hercules.img ------> recovery.img
4. Open up Terminal Emulator on your phone and type the following 2 commands:
su
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p22
(please note the second command is a one line command with spaces between "dd & if=" and ".img & of=")
If your Rom identifies your internal sdcard as /emmc instead of /sdcard, then make the adjustment to command line (dd if=/emmc/recovery.img) instead of what is posted above.
That simple.
You can also issue these commands from adb shell if you are connected to your computer.
If Terminal Emulator does not have Superuser or SuperSU permissions for root privileges then make sure it does. You can also go from NON Touch CWM to Touch CWM using this and vice versa. Simply make sure you have the right recovery for your phone and rename it to recovery.img.
As for explanations:
dd if= command is a common Unix program whose primary purpose is the low-level copying and conversion of raw data.
dd stands for "data description"
if stands for "input file"
of stands for "output file"
the = is the location of the data you are using. ie. /sdcard/recovery.img
the /dev/block/mmcblk0p22 is the location/partition of the recovery on your phone.
So essentially you are doing a low level rewrite of the recovery image on your phone via command lines.
***Also, the best way to remember this command line is to not to. Copy the command line and save it to your own personal contact info in Google under Notes and then you will have it with you wherever you go. You really do not want to mess with getting it wrong. You could brick your phone if you mess things up.
Anyway, I hope this helps. . . . it really is very easy to execute without fault.
Works with TWRP too.
This also works with changing to and from TWRP. Download the image (for our phones it's TWRP 2.3.1.1) rename it to recovery.img and follow the above instructions and you are good to go.
Follow this link to get the image file: http://teamw.in/project/twrp2/101
***I attached the old TWRP 2.2.2.0 is case you run into problems with the newer versions not restoring backups properly or renaming backups correctly.***
Excellent Thread, I hope Dev's requiring specific CWM versions can link to your post.
Thanks for your efforts.
Noellenchris
XDA Forum MOD
Thanks for the instructions! Thanks even more for explaining the command lines.
Just thought I'd point out a small bug with the Touch Recovery. If you flash one of the newer ICS roms like Darkside Evolution through the Touch Recovery, once booted, the ROM WILL NOT SLEEP through time out. I've confirmed this with 2 separate ICS roms. Flashing non-touch recovery through Rom Manager fixes this problem.
Wouldn't it be easier to use gscript and run the commands as you need them?
Thanks for the HOW TO I actually was looking for it.
What is wrong with ROM Manager? I use it to go between Touch and normal all the time and it works flawlessly.
dextroamphetamine said:
What is wrong with ROM Manager? I use it to go between Touch and normal all the time and it works flawlessly.
Click to expand...
Click to collapse
For some people Rom Manager doesn't work. On the T-Mobile SGH-T989 Galaxy SII, Rom Manager will only allow you to go to 5.0.2.6 not 5.0.2.7. And, I think you have to upgrade Rom Manager to go to Touch. I bought Rom Manager, and don't use Touch Recovery, so I am not sure.
I like to use the command structure verses program because I know it works, it's fast, and I can see the results if an error occurs.
Oh yeah...this was really simple...Thanks...went from Touch back to Non Touch.
Give this a try
If you want a simple way to flash the Touch Recovery then give this a try. I will be adding the Hard Recovery as well in the next release.
SGSII T989 Root Toolkit
http://forum.xda-developers.com/showthread.php?t=1650908
http://forum.xda-developers.com/showthread.php?p=26200755
I get a write error: No space left on device. 1001+0 records in 1000+0 records out 512000 bytes transferred in 0.132 secs.
I reboot into recovery and it's still on 5.0.2.6
Edit: so i closed the terminal and I ran it again, and now my phone won't turn on. I get a USB device in windows called QHSUSB_DLOAD. I hold the power button, and the device disappears, but it won't turn on. I let go of the button, the same device reappears.
albanianbrotha said:
Edit: so i closed the terminal and I ran it again, and now my phone won't turn on. I get a USB device in windows called QHSUSB_DLOAD. I hold the power button, and the device disappears, but it won't turn on. I let go of the button, the same device reappears.
Click to expand...
Click to collapse
hate to be the dude that tells you this but i'm pretty sure qhsusb_dload is magic windows talk for "hard bricked phone." had that problem a while back. however all is not lost - these guys have a great reputation for Lazarus-ing dead phones.
hobakill said:
hate to be the dude that tells you this but i'm pretty sure qhsusb_dload is magic windows talk for "hard bricked phone." had that problem a while back. however all is not lost - these guys have a great reputation for Lazarus-ing dead phones.
Click to expand...
Click to collapse
Haha no worries bro. I mean worries that it failed for no reason, but I already sent it in, he just got it today. Same person you linked. Definitely trying to install ics again when i get it. Plus I think the ota ics for tmo came out yesterday or something? Probably a better experience than what was already out there with the radio and stuff.
the files from the CWM site are not .img for me, they are .ndif is it the same procedure?
MustangFTW said:
the files from the CWM site are not .img for me, they are .ndif is it the same procedure?
Click to expand...
Click to collapse
No! Do NOT use this procedure with that file extension!
What recovery are you trying to install? And for what phone? I briefly ran my cursor over the various files and the download links are either .img or .zip files. I did not see .ndif file extension.
PM me if you need additional help.
Would you happen to have the .img file for 5.0.2.7??
Edit* Nvm.. a quick google search and I was able to find it. You are a life saver.. I tried updating my recovery to the 6.0.1.2 Hercules port and for a couple days, it was working great up until an hr. ago. Nothing would flash and it would just hang in recovery... so I found this thread and thankfully I was able to downgrade back down to 5.0.2.7.
If you were local, I would take you out and get you piss drunk for helping me save my device. Cheers!!!!
fresherthanU said:
Would you happen to have the .img file for 5.0.2.7??
Edit* Nvm.. a quick google search and I was able to find it. You are a life saver.. I tried updating my recovery to the 6.0.1.2 Hercules port and for a couple days, it was working great up until an hr. ago. Nothing would flash and it would just hang in recovery... so I found this thread and thankfully I was able to downgrade back down to 5.0.2.7.
If you were local, I would take you out and get you piss drunk for helping me save my device. Cheers!!!!
Click to expand...
Click to collapse
You're welcome, I'm glad I could help you. But, the link to the .img files is in the OP instructions. . . .
Unfortunately this method did not work for me... I have tried many ways to update my CWM and none of them worked, it is almost hopeless for me
Good news! You made front page! http://www.xda-developers.com/andro...gn=Feed:+xda-developers/ShsH+(xda-developers)