Related
I've combined toastcfh's and TheBiles how-to's in this tutorial, so if you've already rooted using TheBiles previous method, skip to step 9. I'll make this a bit more presentable when I get home from work today. I just thought this would be helpful to those who aren't comfortable with using adb.
I'm not responsible for damages to your phone, yada yada yada, you know the drill.
IF YOU HAVE A PROBLEM THAT HASN'T BEEN ADDRESSES IN THE SECOND POST, LET ME KNOW. OTHERWISE, SEE SECOND POST FOR FAQ'S. Follow these directions exactly as they are written and you won't run into any snags. It'll save us both a lot of time.This tutorial entails making the root process as fast and easy as possible, that means we won't be backing up any of your stuff (you can if you want, of course) nor will we be doing a nandroid backup, and even better, we won't be using adb to push files. With that being said, let's get started.
Step 1. Connect your phone to your pc via usb, then pull down the notification bar at the top of your screen and open the tab that says Charge Only and select Disk Drive then click done.
Step 2. Download this file http://link.geekfor.me/rootedromzip and put it on the root of your sd card by going to the start menu of your computer and opening up My Computer, then drop the file into the icon that reads Removable Disk. This is the root of your sd card. Remember that if you don't already know.
Step 3. Right click on the Removable Disk icon and select Eject. We're gonna flash the debug image now, say goodbye to any pic's, music, apps, texts, etc that you may have.
Step 4. Power down your phone.
Step 5. Hold down the volume down and power key simultaneously and keep holding it down until you see 3 android dudes on skateboards.
Step 6. It's going to give you some options, whether or not to install the PC36IMG.zip, select yes (volume up is yes) for any prompt you get.
Step 7. Once you've rebooted you will officially have root access. Congrats, but that's not all. There's a few more steps to gain -full- root access.
Step 8. Navigate to the root of your sd card and rename the PC36IMG.zip file whatever you want, doesn't matter. Just don't name it update. To rename the .zip file, right click on PC36IMG.zip and select rename.
Step 9. Download these files:
PC36IMG.zip -http://sdx-downloads.com/sdx/evo/troot/eng-PC36IMG.zip
mtd-eng.zip - http://forum.xda-developers.com/attachment.php?attachmentid=342668&d=1276481802
flash_image.zip - http://forum.xda-developers.com/attachment.php?attachmentid=342667&d=1276481776
recovery.img - http://files.androidspin.com/downloads.php?dir=amon_ra/RECOVERY/&file=recovery-RA-evo-v1.7.0.1.img
PLEASE NOTE SOME OF THE MIRRORS YOU ARE DOWNLOADING THESE FILES FROM ARE NAMED SOMETHING DIFFERENT, SO YOU WILL HAVE TO RENAME THEM ACCORDINGLY. The only one that I know of was the PC36IMG.zip file, it was named something else when I downloaded it. So name it accordingly. Right click, select Rename, then type in "PC36IMG" only, your pc adds the .zip.
Step 10. Extract the flash_image.zip and mtd-eng.zip files, do so by right clicking on them, then select Extract To flash_image\ and Extract To mtd-eng\ Open the newly extracted folders and take the flash_image file AND the mtd-eng file inside and drop them into the root of your sd card. (we remember how to do that, don't we.)
Step 11. Open up the Android Market and download the terminal emulator app by Jack Palevick, it's free.
Step 12. Make sure your sd card is no longer mounted to the computer, do so by pulling down the notification bar and switching Disk Drive to Charge Only.
Step 13. Open the terminal emulator app and type in these commands exactly as they are written. If you get an error, try again.
Note: After each line is completed, hit enter. A # sign means you've run the commands successfully.
Code:
[B]su
cat /sdcard/flash_image > /data/flash_image
chmod 755 /data/flash_image
/data/flash_image misc /sdcard/mtd-eng.img[/B]
Step 14. Remount your phone, and drop the PC36IMG.zip file onto the root of your sd card. MAKE SURE YOU USE THE CORRECT PC36IMG.ZIP FILE THAT YOU DOWNLOADED FROM STEP 9. Power down your phone.
Step 15.
Hold volume down and power to boot into hboot.
- It should now find and verify the PC36IMG.zip on the root of your sdcard. It'll show a blue status bar on the top right of the screen.
- After a minute or so it will ask u if u wanna flash Select YES.
- After it flashes the PC36IMG.zip it will ask if you wanna reboot. Select YES.
Click to expand...
Click to collapse
Step 16. Once your phone has rebooted, put the recovery.img file you downloaded earlier on the root of your sdcard.
Note: If the recovery image is named something other than "recovery.img" then rename it by right clicking and typing in "recovery" as the name.
Step 17. Still know how to use terminal emulator? Open it up and type in these commands. Make sure your USB connection is in Charge Only mode first.
Code:
[B]su
cat /sdcard/flash_image > /data/flash_image
chmod 755 /data/flash_image
/data/flash_image recovery /sdcard/recovery.img[/B]
*INTERMISSION*
Take uh break, eat uh cookie.
If you've made it this far and you've had no errors, then you now have full root access as well as a legit recovery.
Time to flash a ROM and the latest radio.
Step 18. Power down your phone and power it back on by holding down the Volume Up and Power key.
Step 19. Select BOOTLOADER then select Recovery.
Step 20. Select Wipe: Select wipe data factory reset then select wipe dalvik cache.
Step 21. Downlaod any ROM you'd like, I'm running BuglessPete's Bugless Beast ROM, here's the link if you want to run this one as well http://bit.ly/az4cWq
Step 22. Download the latest radio here http://link.geekfor.me/radio139000531
Step 23. In recovery mode, select the USB-MS toggle option, this mounts your sd card to your pc.
Step 24. Move your newly downloaded ROM and radio to the root of your sd card by dropping them onto the Removable Disk icon on your computer.
Step 25. Press the power key to disable USB-MS toggle.
Step 26. Select Flash Zip From Sdcard.
Step 27. Select the ROM you downloaded and you will be prompted whether or not you want to flash the file, follow through with the power key.
Step 28. Select flash zip from sdcard, then select the latest radio .zip file that you just downloaded and flash that mf'er.
Step 29. Try not to freak out when you see a static image of a phone with green arrows circling around it. Wait...
Step 30. Select Reboot System Now.
And that's it, you're done!
ALL CREDIT GOES TO THESE GUYS! toastcfh, keishou, maejrep, Paul, Amon_Ra, Koush, TheBiles, and anybody else I forgot.
Grammatical errors? I just worked a 12 hour shift and got right on this, I have to be in bed in about an hour, so **** you.
Problems flashing a ROM after you've completed the process?
This is more than likely on account of the Dev who made the ROM not signing it, tell them if they sign it that you'll love them forever. Or switch to Koush's recovery. This is pretty much guaranteed to work, as Koush's recovery has a toggle signature verification feature. http://forum.xda-developers.com/showthread.php?t=702214 Or, if you've the know-how, sign it yourself. http://forum.xda-developers.com/showthread.php?t=473580
ATTENTION: To the few getting the not enough space error when flashing the recovery image, Amon Ra has addressed the issue here, to no avail according to those who have tried his alternative recovery. At least we now know what the cause of the error is. Thanks again, Amon Ra.
Amon_RA said:
You have a bad block in your recovery (like a bad sector on your harddisk), these bad blocks are skipped when flashing. A bad block means you have less usable space on your recovery partition, hence the not enough space left to flash this recovery...
I made this recovery specially for you, it's 1MB less than the normal recovery (left out the evo charging stuff), all functions of the normal recovery should still work. Could you please give it a try and let me know?
Code:
fastboot flash recovery tiny-recovery.img
OR
flash_image recovery /sdcard/tiny-recovery.img
Click to expand...
Click to collapse
Bad block? Not enough space on sd error when trying to flash the recovery image? Try these.
Amon_RA said:
Could you please try to flash recovery-RA-evo-v1.7.0.2.img and use fastboot to flash :
Code:
fastboot erase recovery
fastboot flash recovery recovery-RA-evo-v1.7.0.2.img
I'll most likely not make my recovery compatible with Koush's rommanger because I would need to almost rewrite it fully.
Click to expand...
Click to collapse
tlisak25 said:
If people are still having problems tell them to unroot and start from scratch without doing system update from Sprint thanks for all or your help
Click to expand...
Click to collapse
In on this.
Will try this out right now and edit my post later.
[Edit]
Oh, so the only difference is instead of using ADB you're using the "terminal emulator" app.
It's a good guide and am sure it works. But if you know how to use ADB, I'd actually prefer ADB. It's much easier to type on your keyboard.
But GREAT guide none-the-less. For people who don't know how to use ADB.
It's not so much that people can't fiure out how to use ADB as it is they can't figure out how to install and run it. Even when I first got into Android I had no clue it was used through a cmd prompt for the first 2 weeks.
arozer said:
In on this.
Will try this out right now and edit my post later.
[Edit]
Oh, so the only difference is instead of using ADB you're using the "terminal emulator" app.
It's a good guide and am sure it works. But if you know how to use ADB, I'd actually prefer ADB. It's much easier to type on your keyboard.
But GREAT guide none-the-less. For people who don't know how to use ADB.
Click to expand...
Click to collapse
Exactly. Also, it's for those who rooted using TheBiles Idiot Proof method and were confused as to whether or not they could follow through with toastcfh's part 2nd part on gaining full root access.
Re: (How-To) FULL ROOT WITHOUT ADB.
ADB is just easier, in my opinion. I like bring able to easily copy and paste and type with a real keyboard. Plus, it's just good to know how to use. Not that I don't use the terminal on the phone, though! BTEP, for the win.
-------------
Sent from my HTC EVO 4G using Tapatalk Pro.
TheBiles said:
ADB is just easier, in my opinion. I like bring able to easily copy and paste and type with a real keyboard. Plus, it's just good to know how to use. Not that I don't use the terminal on the phone, though! BTEP, for the win.
-------------
Sent from my HTC EVO 4G using Tapatalk Pro.
Click to expand...
Click to collapse
Totally agreed. But this method is meant to make rooting as fast and easy as possible (for those who don't know how to neither set up, nor use adb, as setting it up as well as familiarizing yourself with it takes time) Although learning adb is a definite must.
i'm a "noob" and ive had my evo since the release and have been tring to acomplish full root without any luck using adb bs this is the easiest most well explaid way to do so and i am more greatful than words could express. if i can find a way to donate with out a credit card i will gladly help ur cause keep up the great work
bdd123456789 said:
i'm a "noob" and ive had my evo since the release and have been tring to acomplish full root without any luck using adb bs this is the easiest most well explaid way to do so and i am more greatful than words could express. if i can find a way to donate with out a credit card i will gladly help ur cause keep up the great work
Click to expand...
Click to collapse
I'm just glad it helped. Lol If there's anyone you should donate to, it's toastcfh. Without him, we wouldn't have root.
The download link for the PC36IMG.zip in step #9 is broken...I am assuming that the PC36IMG.zip in step 9 is different than the PC36IMG.zip in step 2. If its no different, then I will just proceed downloading the rest of the files and go from there, but If so can I get a mirror link?
nol3n said:
The download link for the PC36IMG.zip in step #9 is broken...I am assuming that the PC36IMG.zip in step 9 is different than the PC36IMG.zip in step 2. If its no different, then I will just proceed downloading the rest of the files and go from there, but If so can I get a mirror link?
Click to expand...
Click to collapse
Just a second, I'll get you a link.
the recovery.img link in step #9 is broken as well...
nol3n said:
The download link for the PC36IMG.zip in step #9 is broken...I am assuming that the PC36IMG.zip in step 9 is different than the PC36IMG.zip in step 2. If its no different, then I will just proceed downloading the rest of the files and go from there, but If so can I get a mirror link?
Click to expand...
Click to collapse
http://www.joeyconway.com/sdx/evo/troot/eng-PC36IMG.zip
Got it from toastcfh's thread. Should work. I'll update the link now.
Go damn it. -.- I'll update them all now. Thanks for the heads up.
thx for the hard work.
Lol Not really doing much but stealing links. They're all updated now.
evo root
I did the idiot guide but cant get ADB working on my windows 7. Should I go ahead and try this? Thx!
crpercodani said:
It's not so much that people can't fiure out how to use ADB as it is they can't figure out how to install and run it. Even when I first got into Android I had no clue it was used through a cmd prompt for the first 2 weeks.
Click to expand...
Click to collapse
Exactly! It took me 2 solid days of searching for the required driver for my laptop. I finally got it to work last night. None of the instructions on xda worked. The USB remover listed here didn't work, the driver in the SDK kit didn't work, nothing worked. I finally found another download for the USB remover and another link to a 32-bit driver that finally worked.
kevinniven said:
I did the idiot guide but cant get ADB working on my windows 7. Should I go ahead and try this? Thx!
Click to expand...
Click to collapse
It's pretty much the fastest/easiest (if you don't have adb set up) way to get full root access on your Evo, so...yes, that'd be a good idea. Lol
S
kevinniven said:
I did the idiot guide but cant get ADB working on my windows 7. Should I go ahead and try this? Thx!
Click to expand...
Click to collapse
Oh yeah, start from step 9 since you're coming from the first part of TheBiles Idiot Proof guide.
Hi guys, I believe I bricked my device. I was trying to format my sdcard in CWM, but accidentally selected /system and formatted it without realizing it. After I rebooted my device it's stuck at the Eee Pad logo.
I tried booting into APX mode to run NVflash but everytime I force shut it off (hold the power key for 10 seconds) it just restarts, so I hold the power and VOL+ key. It shuts off and the screen turns black, but now my computer doesn't recognize it. FML...
Why was I doing all of this? Because I was trying to follow this guide (http://forum.xda-developers.com/showthread.php?t=1514658) by MrNago. I went with Option B, because I rooted my device, but couldn't flash a ROM because I could mount my SD card (not microSD).
Here's what I'd like to know:
1) How unbrick my device under these circumstances
2) How to apply the update from MrNago's guide
3) Can I return this back to CompUSA without them knowing I bricked it?
Please help! And thank you for reading!
avatarjo3 said:
Hi guys, I believe I bricked my device. I was trying to format my sdcard in CWM, but accidentally selected /system and formatted it without realizing it. After I rebooted my device it's stuck at the Eee Pad logo.
I tried booting into APX mode to run NVflash but everytime I force shut it off (hold the power key for 10 seconds) it just restarts, so I hold the power and VOL+ key. It shuts off and the screen turns black, but now my computer doesn't recognize it. FML...
Why was I doing all of this? Because I was trying to follow this guide (http://forum.xda-developers.com/showthread.php?t=1514658) by MrNago. I went with Option B, because I rooted my device, but couldn't flash a ROM because I could mount my SD card (not microSD).
Here's what I'd like to know:
1) How unbrick my device under these circumstances
2) How to apply the update from MrNago's guide
3) Can I return this back to CompUSA without them knowing I bricked it?
Please help! And thank you for reading!
Click to expand...
Click to collapse
Its hold volume down and then hold power...
tweaked said:
Its hold volume down and then hold power...
Click to expand...
Click to collapse
Right. That's to get in to Recovery mode. I can get into recovery mode, but I can't get into APX Mode, which is what I need to do to apply the NVflash. I can't apply the flash via CWM because it's not letting me mount my SDcard.
Thanks for the reply!
avatarjo3 said:
I went with Option B, because I rooted my device, but couldn't flash a ROM because I could mount my SD card (not microSD).
Click to expand...
Click to collapse
Go get a micro sd card and try again. Buy one, get it out of your phone if you have it or get one from your sister.
Not 100% sure but my GUESS would be that since you have no OS on your tablet.
Which mean it can't communicate with your dock for you to use the SD card on the dock. If you can still get into CWM recovery you are NOT "bricked"
baseballfanz said:
Go get a micro sd card and try again. Buy one, get it out of your phone if you have it or get one from your sister.
Not 100% sure but my GUESS would be that since you have no OS on your tablet.
Which mean it can't communicate with your dock for you to use the SD card on the dock. If you can still get into CWM recovery you are NOT "bricked"
Click to expand...
Click to collapse
Whew... what a relief. Alrite, I'll get a microSD card. How can I format it? There's a slot on my laptop with an SDcard slot, but not one for microSD. I've tried using a microSD straight out of the package, without formatting it. Even though I didn't put anything on it, it wouldn't mount via the CWM mount feature.
Thanks for the reply!
avatarjo3 said:
Whew... what a relief. Alrite, I'll get a microSD card. How can I format it? There's a slot on my laptop with an SDcard slot, but not one for microSD. I've tried using a microSD straight out of the package, without formatting it. Even though I didn't put anything on it, it wouldn't mount via the CWM mount feature.
Thanks for the reply!
Click to expand...
Click to collapse
They have microSD USB adapter. Mine came with one when I bought it.
Format to FAT32. Use a program like sdformatter for best results.
baseballfanz said:
They have microSD USB adapter.
Click to expand...
Click to collapse
Alrite. I'll give it a shot.
When you say OS, is that the same thing as a ROM? I want to flash this ROM (http://forum.xda-developers.com/showthread.php?t=1514658), so would I transfer that rom to the microSD and flash it via CWM?
Thanks again!
Yes put that ROM filter on the micro sd card, boot into cwm recovery and install zip from sd card
baseballfanz said:
Yes put that ROM filter on the micro sd card, boot into cwm recovery and install zip from sd card
Click to expand...
Click to collapse
So I have the microSD card. It's 2gigs. I followed this guide (http://www.xda-developers.com/android/how-to-root-the-asus-transformer-xda-tv/) while my device was version 8.6.5.21. All I was trying to do was to get CWM on there. I think the best approach now would be to flash back to 8.6.5.13, then try and install CWM from there. I looked at this guide (http://forum.xda-developers.com/showthread.php?t=1281161), but it said it doesn't come with CWM, but comes with CWM support... What does that mean?
Any suggestions?
Thanks!
Don't go to firmware before 8.6.5.19, it is pointless to go any further back. Flash that firmware, then use razorclaw to root and gnufabios recoveryinstaller to get cwm, see the guide in my signature.
luna_c666 said:
Don't go to firmware before 8.6.5.19, it is pointless to go any further back. Flash that firmware, then use razorclaw to root and gnufabios recoveryinstaller to get cwm, see the guide in my signature.
Click to expand...
Click to collapse
Thanks the advice. I won't root from 8.6.5.13, but I don't think I can take the razorclaw approach, because all the links for the 8.6.5.19 roms are dead. I'm looking at Nachoroot (http://www.androidpolice.com/2012/0...nsformer-prime-even-with-the-newest-firmware/) and will report back when finished.
Quick question. Are the commands provided on the website meant to be ran in cmd?
Thanks!
avatarjo3 said:
Quick question. Are the commands provided on the website meant to be ran in cmd?
Thanks!
Click to expand...
Click to collapse
Yes in CMD window.
OK I'm a little lost. Currently my firmware is 8.6.5.21 and I'm not sure how to follow the Nachoroot guide (http://www.androidpolice.com/2012/0...nsformer-prime-even-with-the-newest-firmware/)...
I have ADB setup. I downloaded the 2 files. Do I need to have the files in a certain location? What do I need to do???
avatarjo3 said:
OK I'm a little lost. Currently my firmware is 8.6.5.21 and I'm not sure how to follow the Nachoroot guide (http://www.androidpolice.com/2012/0...nsformer-prime-even-with-the-newest-firmware/)...
I have ADB setup. I downloaded the 2 files. Do I need to have the files in a certain location? What do I need to do???
Click to expand...
Click to collapse
The two files need to go into the SDK (platform-tools) folder.
baseballfanz said:
The two files need to go into the SDK (platform-tools) folder.
Click to expand...
Click to collapse
Great, so I did that and I shift+rightclick in the folder to open up cmd and I type in the commands, but after I get do the second reboot and type in "adb shell id" I never get id 0... I type everything out carefully. Each time the tablet reboots my computer says it's installing the software but fails everytime. Could this have something to do with it? Does this only work with Transformer Prime?
Also, I'm running windows 7 and installed the SDK package in Program Files x86. I put the 2 files in the folder platform-tools and shift+rightclick and ran the commands. What am I doing wrong?
I really appreciate the replies. They're very helpful!
Thank you!
Please anyone? I could really use your help
Just forget everything everyone says. Follow my idiot-proof procedure for dummies.
Part 0
(1) Go to the following website.
ASUS - Eee- ASUS Eee Pad Transformer TF101
(2) Choose android.
(3) Download the latest WW, US, TW, etc. version you need.
(4) Unzip that file. Inside, you will probably find a folder called update. Inside that folder, you will find another zip file. Keep this zip file.
(5) Place this zip file in the root of your micro sd card.
(6) Insert micro sdcard into your TF.
Part I
(1) Download the following zip file from my cloud account.
honeycomb_root_cwm.zip - File Shared from Box - Free Online File Storage
(2) Unzip it onto your desktop.
You should find 3 things after you've unzipped it.
a-folder name "apps"
b-folder name "root honeycomb"
c-file name "root-honeycomb-instructions.txt"
(3) Place the folder "root honeycomb" in your c: directory. where is this? Click on Computer and go into Local Disk (C: ). Place the folder in there.
Part II
(1) Connect your TF to your computer.
(2) On your TF, press on the sync icon in the lower right hand corner of the taskbar. It will fail to sync with your computer. Try again. Keep trying againi until your computer and TF recognize each other.
(3) On your PC, press on the start menu. In the search bar, type in "cmd".
(4) Type in "cd\" and press enter.
(5) In the command prompt, type "cd root-honeycomb".
Part III
(1) Open up the text file "root-honeycomb-instructions.txt".
(2) Copy the first line in the text file.
(3) Right click the command prompt window and choose paste. Press enter.
(4) Copy and paste the 2nd line. Do this for the first 4 lines.
(5) After the 4th line, your TF should restart. Wait for it to completely restart. Unlock your TF.
(6) Copy and paste the 6th and subsequent lines. When you see <wait for boot>, it means you wait for your TF to reboot. Do not copy and paste such lines.
Part IV
(1) Congrats. You are now rooted.
(2) Transfer the folder "apps" into your TF.
(3) Install those 2 apps found in the folder.
(4) Open up the app "superuser". Then go back to your homescreen.
(5) Open up the app recovery installer. Press that big-ass button in the middle of the screen. Allow.
(6) Wait for your TF to restart completely.
(7) Turn off your TF.
(8) Turn on your TF by pressing and holding the power and volume down buttons together. As soon as you see white texts on the upper left hand corner of your TF, immediately release the power and volume down buttons and press the volume up button.
Part V (Final)
(1) You are now in what we call clockworkmod recovery.
(2) Using volume up and down buttons, navigate to "Install from zip file". To enter, press the power button.
(3) Choose "Choose zip file from sd card".
(4) Navigate to the zip file you got from the asus website and choose it.
(5) Watch your TF install ICS.
(6) Once ICS finishes installing, go back and reboot system.
At this point, your system will reboot into ICS. You now have a non-rooted ICS stock rom and stock recovery.
avatarjo3 said:
Hi guys, I believe I bricked my device. I was trying to format my sdcard in CWM, but accidentally selected /system and formatted it without realizing it. After I rebooted my device it's stuck at the Eee Pad logo.
I tried booting into APX mode to run NVflash but everytime I force shut it off (hold the power key for 10 seconds) it just restarts, so I hold the power and VOL+ key. It shuts off and the screen turns black, but now my computer doesn't recognize it. FML...
Why was I doing all of this? Because I was trying to follow this guide (http://forum.xda-developers.com/showthread.php?t=1514658) by MrNago. I went with Option B, because I rooted my device, but couldn't flash a ROM because I could mount my SD card (not microSD).
Here's what I'd like to know:
1) How unbrick my device under these circumstances
2) How to apply the update from MrNago's guide
3) Can I return this back to CompUSA without them knowing I bricked it?
Please help! And thank you for reading!
Click to expand...
Click to collapse
If its till bricked press down power and vol down buttons together that should help and your tablet will BOOT back into an existing ROM (Im telling you because i was trying to ROOT with ICS and more than once i was stuck in same situation).
If you want to root then follow my step, it should help you to ROOT as i was able get ROOT and install Revolver ICS and i was on stock ICS (US version). Click on the link below and understand all the steps.
http://forum.xda-developers.com/showthread.php?t=1527926
Sorry for the late reply guys. I lost my microSD card so I haven't tested your method yet.
Thank you for replying with length posts guys. This is most helpful! I will return with positive results!
avatarjo3 said:
Great, so I did that and I shift+rightclick in the folder to open up cmd and I type in the commands, but after I get do the second reboot and type in "adb shell id" I never get id 0... I type everything out carefully. Each time the tablet reboots my computer says it's installing the software but fails everytime. Could this have something to do with it? Does this only work with Transformer Prime?
Click to expand...
Click to collapse
You are typing in --stage1 --stage2 also correct?
I recently downloaded an ICS-based, Cynagen 9 ROM. It was making my Infuse very hot, so I decided to restore back to my previous ROM (Ethereal). I've tried Odin (can't get COM## to appear on it) and Heimdall (installed drivers, new version of Java, still doesn't recognize device). I don't want to pay to have it fixed again, so does anyone have any suggestions as to how I can fix myself? I have a blue CWM. Thanks.
GAPY427 said:
I recently downloaded an ICS-based, Cynagen 9 ROM. It was making my Infuse very hot, so I decided to restore back to my previous ROM (Ethereal). I've tried Odin (can't get COM## to appear on it) and Heimdall (installed drivers, new version of Java, still doesn't recognize device). I don't want to pay to have it fixed again, so does anyone have any suggestions as to how I can fix myself? I have a blue CWM. Thanks.
Click to expand...
Click to collapse
I flash a gb rom in blue cwm to get....red cwm, then flash a gb ROM again...
Have you tried diff usb port & cable....pc?
bigjoe2675 said:
I flash a gb rom in blue cwm to get....red cwm, then flash a gb ROM again...
Have you tried diff usb port & cable....pc?
Click to expand...
Click to collapse
I tried to reflash Ethereal ROM but it doesn't work. Oh, hell, I may just get GSIII on Verizon and call it a day.
GAPY427 said:
I tried to reflash Ethereal ROM but it doesn't work. Oh, hell, I may just get GSIII on Verizon and call it a day.
Click to expand...
Click to collapse
way to throw in the towel...some don't have that option...but XDA is learning experience, not for the towel tossers...
but if you require and want it we can provide it for you any and some assistance.
if you no longer require the thread you can click that triangle to the right of your op...and tell mods to close this thread..
thx
Sounds like if you would do a battery pull and get to download mode you could odin or heimdall back but if ya wanna toss money away to upgrade that's cool too
Sent from my SGH-I997 using xda premium
dawsndev said:
Sounds like if you would do a battery pull and get to download mode you could odin or heimdall back but if ya wanna toss money away to upgrade that's cool too
Sent from my SGH-I997 using xda premium
Click to expand...
Click to collapse
That's it -- I tried Odin and Heimdall but they didn't work. I downloaded the drivers several times, but both programs couldn't recognize my device. I couldn't see the COM## in Odin when I plugged in my Infuse.
bigjoe2675 said:
way to throw in the towel...some don't have that option...but XDA is learning experience, not for the towel tossers...
but if you require and want it we can provide it for you any and some assistance.
if you no longer require the thread you can click that triangle to the right of your op...and tell mods to close this thread..
thx
Click to expand...
Click to collapse
I want to fix my Infuse, but it becomes frustrating when you try these programs (Odin, etc.) and it isn't successful. I can't reboot my phone into anything right now (a new ROM, a restore, etc). It's stuck in the blue recovery.
to get COM## Try using a different usb plug. That has always been my fix for that issue
TheDSMjuggalo said:
to get COM## Try using a different usb plug. That has always been my fix for that issue
Click to expand...
Click to collapse
can I get in bluerecovery?
Sent from my SGH-I997 using xda premium
bradman117 said:
can I get in bluerecovery?
Sent from my SGH-I997 using xda premium
Click to expand...
Click to collapse
using a different usb port is for odin. download and flash the modded 3e rom found here: http://forum.xda-developers.com/showthread.php?t=1092021
Then flash over the rom you wanted thru the recovery
GAPY427 said:
I want to fix my Infuse, but it becomes frustrating when you try these programs (Odin, etc.) and it isn't successful. I can't reboot my phone into anything right now (a new ROM, a restore, etc). It's stuck in the blue recovery.
Click to expand...
Click to collapse
Since you're stuck in recovery and can't get Heimdall or Odin to work, you'll need to use adb to do what I'm about to explain. So, let me know if you need a tutorial on using adb. You can use adb to push items to /sdcard/ while in CWM recovery. Using adb, put the rom that you want on the internal sdcard and put Zen Arcade's Infusion-Z kernel zip there as well. Get the kernel here:
http://forum.xda-developers.com/showthread.php?p=25724526
Then, use the install from zip feature in CWM recovery to flash Zen's kernel to the phone. After the kernel flash, unplug the USB cable and shut the phone off by holding down the power button (it won't boot into anything yet). Then hold the power button and two volume buttons. When the Samsung logo appears, release the power button and keep holding the volume buttons until you are in red recovery. Go to mounts and storage and format system, data, and cache. Then, go back to flash your rom and then reboot. If you're still wanting to throw in the towel, mail it to me and I'll do it for you.
Sent from my SGH-I997 using Tapatalk 2
TheDSMjuggalo said:
to get COM## Try using a different usb plug. That has always been my fix for that issue
Click to expand...
Click to collapse
I've tried that several times. My device is not recognized by Odin.
jscott30 said:
Since you're stuck in recovery and can't get Heimdall or Odin to work, you'll need to use adb to do what I'm about to explain. So, let me know if you need a tutorial on using adb. You can use adb to push items to /sdcard/ while in CWM recovery. Using adb, put the rom that you want on the internal sdcard and put Zen Arcade's Infusion-Z kernel zip there as well. Get the kernel here:
http://forum.xda-developers.com/showthread.php?p=25724526
Then, use the install from zip feature in CWM recovery to flash Zen's kernel to the phone. After the kernel flash, unplug the USB cable and shut the phone off by holding down the power button (it won't boot into anything yet). Then hold the power button and two volume buttons. When the Samsung logo appears, release the power button and keep holding the volume buttons until you are in red recovery. Go to mounts and storage and format system, data, and cache. Then, go back to flash your rom and then reboot. If you're still wanting to throw in the towel, mail it to me and I'll do it for you.
Sent from my SGH-I997 using Tapatalk 2
Click to expand...
Click to collapse
Yes, I'll need a tutorial on adb.
GAPY427 said:
Yes, I'll need a tutorial on adb.
Click to expand...
Click to collapse
I've put together a package with all that you'll need for adb. Use these instructions to move the files that I mentioned in my earlier post.
First, let's make sure that we are on the same page with drivers, since you have had trouble with both Heimdall and Odin.
1.) Unplug USB cable.
2.) In the Windows Control Panel, go to "Programs and Features" or "Add/Remove Programs" and uninstall any instances of Samsung Kies and SAMSUNG USB Driver for Mobile Phones.
3.) Download and install THIS version of SAMSUNG USB Driver for Mobile Phones.
4.) After installing the driver, plug in USB cable, and give Windows a moment to setup the driver. When your connection is ready, a USB cable with a check beside it should appear in the Windows system tray.
You can give Odin another try, and it should work for you now with the new driver, or you can move forward with using adb to do what you need.
1.) Download and unzip THIS adb package.
2.) Browse to the folder containing adb.exe. Hold down shift and right click with the mouse; then choose "Open command window here".
3.) Make sure that you are in CWM recovery, and in the Windows command prompt, type
Code:
adb devices
If all is working correctly, your device should appear in the list.
4.) Place any files that you want to move to the device in the same folder as adb.exe.
5.) Then do this for each file: Type the command below, but replace fullfilename with the full name of the file.
Code:
adb push [I]fullfilename[/I] /sdcard/
When the transfer finishes, you should be able to access the items on your internal sd card. From here you can follow the instructions that I gave in the earlier post.
jscott30 said:
I've put together a package with all that you'll need for adb. Use these instructions to move the files that I mentioned in my earlier post.
First, let's make sure that we are on the same page with drivers, since you have had trouble with both Heimdall and Odin.
1.) Unplug USB cable.
2.) In the Windows Control Panel, go to "Programs and Features" or "Add/Remove Programs" and uninstall any instances of Samsung Kies and SAMSUNG USB Driver for Mobile Phones.
3.) Download and install THIS version of SAMSUNG USB Driver for Mobile Phones.
4.) After installing the driver, plug in USB cable, and give Windows a moment to setup the driver. When your connection is ready, a USB cable with a check beside it should appear in the Windows system tray.
You can give Odin another try, and it should work for you now with the new driver, or you can move forward with using adb to do what you need.
1.) Download and unzip THIS adb package.
2.) Browse to the folder containing adb.exe. Hold down shift and right click with the mouse; then choose "Open command window here".
3.) Make sure that you are in CWM recovery, and in the Windows command prompt, type
Code:
adb devices
If all is working correctly, your device should appear in the list.
4.) Place any files that you want to move to the device in the same folder as adb.exe.
5.) Then do this for each file: Type the command below, but replace fullfilename with the full name of the file.
Code:
adb push [I]fullfilename[/I] /sdcard/
When the transfer finishes, you should be able to access the items on your internal sd card. From here you can follow the instructions that I gave in the earlier post.
Click to expand...
Click to collapse
Followed your instructions. Removed SAMSUNG drivers. Installed drivers in your instructions. Odin did not work. Tried the other method and I receive this message in the Cmd window: 'adb' is not recognized as an internal or external command, operable program or batch file.
GAPY427 said:
Followed your instructions. Removed SAMSUNG drivers. Installed drivers in your instructions. Odin did not work. Tried the other method and I receive this message in the Cmd window: 'adb' is not recognized as an internal or external command, operable program or batch file.
Click to expand...
Click to collapse
You have to be in the exact directory as adb.exe or you'll continue to get that error. Go to the exact folder, hold shift and right click the mouse in that folder window. Choose "Open command window here".
Good luck, and enjoy the holiday.
Sent from my SGH-I997 using Tapatalk 2
jscott30 said:
You have to be in the exact directory as adb.exe or you'll continue to get that error. Go to the exact folder, hold shift and right click the mouse in that folder window. Choose "Open command window here".
Good luck, and enjoy the holiday.
Sent from my SGH-I997 using Tapatalk 2
Click to expand...
Click to collapse
Not working. I'm stuck either in blue recovery or a Galaxy S cyanogen(mod) screen.
GAPY427 said:
Not working. I'm stuck either in blue recovery or a Galaxy S cyanogen(mod) screen.
Click to expand...
Click to collapse
Anyone taking time to help you is going to need more to go on than "Not working." I already know that you're in blue recovery. What's the latest on using adb to push a kernel with red recovery to your device so we can get you back to Gingerbread?
Sent from my SGH-I997 using Tapatalk 2
jscott30 said:
Anyone taking time to help you is going to need more to go on than "Not working." I already know that you're in blue recovery. What's the latest on using adb to push a kernel with red recovery to your device so we can get you back to Gingerbread?
Sent from my SGH-I997 using Tapatalk 2
Click to expand...
Click to collapse
I tried pushing a kernel through adb but I didn't see it on my sd card. There were also 4 different choices of kernels (Core A, Core B, etc.). I tried to push A & B but saw neither of them on recovery.
GAPY427 said:
I tried pushing a kernel through adb but I didn't see it on my sd card. There were also 4 different choices of kernels (Core A, Core B, etc.). I tried to push A & B but saw neither of them on recovery.
Click to expand...
Click to collapse
Did you see the transfer in progress in the command line? If so, and if the transfer finished, it's on there. I wonder if you're looking on your external sd card instead of the internal.
Sent from my SGH-I997 using Tapatalk 2
---------- Post added at 08:59 PM ---------- Previous post was at 08:54 PM ----------
Alright, in blue recovery, go to "install zip from sdcard".
Then, go to "choose zip from sdcard". Do you see the items that you pushed with adb listed there? Don't choose "choose zip from internal sdcard". Despite what that sounds like, it's your external sdcard.
Rather than dive head first in to a situation I can't get myself out of, I'm going to make sure I have everything I need before I begin. I have not received my Htc One x yet, but assuming it comes with 1.85, I follow these steps.
Device setup (hopefully):
Device: Att Htc One X
Filmware version: 1.85
Step one: Root
Following these steps... Edit: http://forum.xda-developers.com/show....php?t=1709296
Quote from iElvis: DO NOT use the one-click method as this can update you to 2.20 if you goof it up, and then you're stuck until there's a new exploit.
Step two: Unlock bootloader
Following these steps... http://briefmobile.com/how-to-unlock-att-one-x-bootloader (from download link here: http://forum.xda-developers.com/showthread.php?t=1672284)
Step 3: Flashing preferred Rom -NOT INTERNATIONAL VERSIONS OF ROMS-:
I have selected Nocturnal Limited Edition... http://forum.xda-developers.com/showthread.php?t=1816853
Following these steps...
How to Flash
Download Rom.zip and save to phone storage
boot into recovery
wipe system
wipe data if coming from another rom
wipe cache
go to flash rom
select the proper download
follow the options in the Aroma installer
Reboot & Enjoy
Some questions before attempting:
"boot into recovery" Meaning I use Twrp2 (from download link here: http://forum.xda-developers.com/showthread.php?t=1677447)
"Wipe system/data/cache" I assume thats done via recovery (Twrp2) correct?
"go to flash rom, select proper download" I assume thats similar to clockwordmod, where you find the Rom on your sdcard (in this case, phone storage) and select it.
"follow options in the Aroma installer" follow instructions in the installer... simple enough.
Is there anything I missed? Devil's in the details.
Edit (more questions): In the following thread ( http://forum.xda-developers.com/showthread.php?t=1709296) it says "Put su in same directory as ADB. Get to adb command prompt and cd into that directory"
Put su (superuser) in same directory as ADB, means that you put Superuser in the same folder as ADB, right?
and cd into that directory. What does this mean?
A cool username said:
Filmware version: 1.85
Step one: Root
Following these steps... http://briefmobile.com/how-to-root-htc-one-x-att (from download link here: http://forum.xda-developers.com/showthread.php?t=1644167)
Click to expand...
Click to collapse
That's the wrong root procedure for 1.85. You need this one:
http://forum.xda-developers.com/showthread.php?t=1709296
DO NOT use the one-click method as this can update you to 2.20 if you goof it up, and then you're stuck until there's a new exploit.
I tried to do this using that post but found it confusing and had some trouble with it. I prefer onexroot.com. they have a great guide here http://onexroot.com/one-x-root/root-any-htc-one-x-windowsmaclinuxattinternationalone-click-method/ hope this helps!
Sent from my HTC One X using xda premium
A cool username said:
Edit (more questions): In the following thread ( http://forum.xda-developers.com/showthread.php?t=1709296) it says "Put su in same directory as ADB. Get to adb command prompt and cd into that directory"
Put su (superuser) in same directory as ADB, means that you put Superuser in the same folder as ADB, right?
and cd into that directory. What does this mean?
Click to expand...
Click to collapse
cd means change directory. It is a windows command prompt command. So you would type "cd C:\adb" if that was where your adb folder was. Folder and directory can be used interchangeably, although directory is more "correct". We only say folder because GUIs use folders to represent directories.
A cool username said:
Rather than dive head first in to a situation I can't get myself out of, I'm going to make sure I have everything I need before I begin. I have not received my Htc One x yet, but assuming it comes with 1.85, I follow these steps.
Device setup (hopefully):
Device: Att Htc One X
Filmware version: 1.85
Step one: Root
Following these steps... Edit: http://forum.xda-developers.com/show....php?t=1709296
Quote from iElvis: DO NOT use the one-click method as this can update you to 2.20 if you goof it up, and then you're stuck until there's a new exploit.
Step two: Unlock bootloader
Following these steps... http://briefmobile.com/how-to-unlock-att-one-x-bootloader (from download link here: http://forum.xda-developers.com/showthread.php?t=1672284)
Step 3: Flashing preferred Rom -NOT INTERNATIONAL VERSIONS OF ROMS-:
I have selected Nocturnal Limited Edition... http://forum.xda-developers.com/showthread.php?t=1816853
Following these steps...
How to Flash
Download Rom.zip and save to phone storage
boot into recovery
wipe system
wipe data if coming from another rom
wipe cache
go to flash rom
select the proper download
follow the options in the Aroma installer
Reboot & Enjoy
Some questions before attempting:
"boot into recovery" Meaning I use Twrp2 (from download link here: http://forum.xda-developers.com/showthread.php?t=1677447)
"Wipe system/data/cache" I assume thats done via recovery (Twrp2) correct?
"go to flash rom, select proper download" I assume thats similar to clockwordmod, where you find the Rom on your sdcard (in this case, phone storage) and select it.
"follow options in the Aroma installer" follow instructions in the installer... simple enough.
Is there anything I missed? Devil's in the details.
Edit (more questions): In the following thread ( http://forum.xda-developers.com/showthread.php?t=1709296) it says "Put su in same directory as ADB. Get to adb command prompt and cd into that directory"
Put su (superuser) in same directory as ADB, means that you put Superuser in the same folder as ADB, right?
and cd into that directory. What does this mean?
Click to expand...
Click to collapse
Did you end up getting root and unlock bootloader to work?
smartnphone said:
Did you end up getting root and unlock bootloader to work?
Click to expand...
Click to collapse
I'm not trying to be rude, but as stated in my opening post, first paragraph. I don't have my one x yet, I am just making sure I have everything before I get my one x so that way I don't have to worry about it.
Bump. Might get my One X today! (^_^)
Will keep updated on what happens
I really hope you find a rootable one.
gunnyman said:
I really hope you find a rootable one.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1842670
Me too. Me too....
It's 1.85!
Sent from my HTC One X using xda app-developers app
Dang.... I cant get the Spoof-Cid to work. Every time I try it says...
Restarting ADB
Pulling files
Checking files
Couldn't pull files from device. Your device was not altered.
Press any key to continue . . .
I'm rooted (checked with terminal emulator) and usd debugging is ON. Set to charge only. No matter what I try, its not working.
A cool username said:
Dang.... I cant get the Spoof-Cid to work. Every time I try it says...
Restarting ADB
Pulling files
Checking files
Couldn't pull files from device. Your device was not altered.
Press any key to continue . . .
I'm rooted (checked with terminal emulator) and usd debugging is ON. Set to charge only. No matter what I try, its not working.
Click to expand...
Click to collapse
Try rebooting your phone... worked for me!
Sent from my SGH-I777 using Tapatalk 2
C3RGIOSE1 said:
Try rebooting your phone... worked for me!
Sent from my SGH-I777 using Tapatalk 2
Click to expand...
Click to collapse
I will reboot.... AS MANY TIMES AS IT TAKES!!! -Determined-
A cool username said:
I will reboot.... AS MANY TIMES AS IT TAKES!!! -Determined-
Click to expand...
Click to collapse
Also make sure you use USB 2.0 and not front ports, but main ones on the back, if using desktop :thumbup:
Sent from my SGH-I777 using Tapatalk 2
C3RGIOSE1 said:
Also make sure you use USB 2.0 and not front ports, but main ones on the back, if using desktop :thumbup:
Sent from my SGH-I777 using Tapatalk 2
Click to expand...
Click to collapse
its not working (-_-) i have rebooted 5+ times and it wont do it.
A cool username said:
its not working (-_-) i have rebooted 5+ times and it wont do it.
Click to expand...
Click to collapse
I'm going to do mine Super CID on my X, see how it goes... I'll follow up
Sent from my SGH-I777 using Tapatalk 2
C3RGIOSE1 said:
I'm going to do mine Super CID on my X, see how it goes... I'll follow up
Sent from my SGH-I777 using Tapatalk 2
Click to expand...
Click to collapse
Thankyou so much. In the meantime I will start from square one and see if that works afterwords
A cool username said:
its not working (-_-) i have rebooted 5+ times and it wont do it.
Click to expand...
Click to collapse
Just did my SuperCID - and successfully unlocked BL....I just followed one-click by kennethpenn... where exactly do you get stuck? USB debugging enabled?
Sent from my SGH-I777 using Tapatalk 2
Step by step what I do.
Rooted: achieved. (checked via terminal emulator)
Next I connect my one x via usb, download the supercid file, extract it, run the file, get to where it wants me to press any button, I press any button, it then says it can't get the files and that my device is unchanged, then it closes out of the file. And that's where I'm stuck.
Any questions? At this point I'm thinking I'm missing something incredibly simple...
Sent from my HTC One X using xda app-developers app
Connect phone to computer. Open command prompt. Type adb devices. Does the phone show up ?
For those who may be flashing ROMs, cannot mount the SD Card any more, and may have accidentally corrupted their SD Card, here are some helpful steps.
Preliminary Review - Check to see if you can mount in recovery or bootloader
First, go back to your bootloader screen and click on fastboot (reset your phone and hold the power and vol down button). Once in bootloader check your computer drives to see if the sd card is recognized
Your computer may be able to recognize the drive even if it cant open it. If thats the case, you may be able to format it from your computer (use FAT32 formatting).
Second, If you cannot see your SD Card in your ROM or from the PC, and you are using Clockwork Recovery (CW), try flashing TWRP recovery first. Do this by going through the following steps:
Step #1
Download TWRP recovery from http://teamw.in/project/twrp2/100 Make sure to download the correct version for your device
Step #2
Place the recovery file into a folder with fastboot.exe
Step #3
Reboot your phone and hold down the Vol Down Button and Power Button until your bootloader screen appears, then enter fastboot. Then connect to your computer. I find this method works best by holding down the buttons right away. If your phone is off, press the power button then immediately press and hold the power and vol off buttons again until bootloader screen shows up. Dont let go until the screen shows.
Step #4
Type
Code:
fastboot flash recovery twrp.img
but replace the twrp.img wording with the exact name of your downloaded TWRP recovery
Step #5
Enter TWRP recovery by selecting it from your bootloader screen. Then ensure the device is connected to your computer and select the Mount option and then mount your sd card.
IF you still cant see your SD Card from TWRP recovery or you get an error, proceed to the next steps. Your computer may be able to recognize the drive, even if it cant open it (if your lucky).
If your computer recognizes the drive but cant open it, you can try formatting it from your computer (make sure to format as FAT32)
If you really cant see your SD Card, and your fairly sure its corrupted, and you have no way formatting it from your computer, continue on below:
Basic Solution
Reflashing Stock Recovery to your device using fasboot, then doing a full factory reset. This would be using the method in post http://forum.xda-developers.com/showthread.php?t=1630459
PLEASE NOTE THIS METHOD WILL WIPE THE DATA FROM YOUR DEVICE AS WELL AS FROM YOUR SD CARD
This method works because custom recoveries cannot re format SD Cards on the HTC One S, only wipe data from them. However, the stock recovery does have a proprietary feature that will reformat the internal sd card if it has been corrupted.
Inotherwords:
Step #1
Download the stock recovery from: http://loadbalancing.modaco.com/download.php?file=ville_recovery_signed.img
*******Note that this file is a stock recovery for S4 devices, not S3.
Place the file into the same folder as your fastboot.exe
Step #2
On your device, go into bootloader and fastboot mode, connect your computer to the device, and type
Code:
fastboot flash recovery ville_recovery_signed.img
Step #3
Reboot into the bootloader and then choose to "clear storage" from the main screen and afterwards reset to factory defaults.
Step #4
Go back into the bootloader once step #3 is done and enter fastboot, connect your device and reflash your original custom recovery again. Your SD Card should be visible
Advanced Solution - If you do not want to wipe the data from your device
This method does not require reflashing the original recovery and factory reseting the whole phone. However, it still means that the info on your sd card will be lost. It also needs a rooted device.
This method does not require you to access your bootloader or use fastboot. You can do this while having your phone in custom recovery.
DO NOT ATTEMPT UNLESS YOU FEEL COMFORTABLE WITH THE INSTRUCTIONS. THERE ARE ALWAYS RISKS WITH FORMATTING. DO NOT HOLD ME RESPONSIBLE FOR BRICKED DEVICES. YOUR DEVICE IS LIKELY OUTSIDE OF WARRANTY ALREADY SINCE YOU WOULD HAVE UNLOCKED THE BOOTLOADER.
I have taken this solution from HTC One X forums namely from post 17 at http://forum.xda-developers.com/showthread.php?t=1647806&page=2
However, I have also confirmed (SneakyGhost's partition list for HTC One S) that the correct mmcblk0p for the HTC One S sd card is mmcblk0p36.
Step #1: Download the version of busybox listed below, unzip it and also put this in the folder with ADB before you get started. You only need to do this if you dont already have busybox installed on your HTC One S. Sometimes this busybox file can be found under /system/bin or /system/xbin if youve previously installed it. If so, replace the paths in the instructions below for that of your busybox. If you have busy box already installed in /system/bin , then you do not need to type in the paths since the adb shell automatically picks up programs in that folder
Step #2: Go to your command prompt in the folder with adb.exe . Connect your HTC One S to your computer and type
Code:
adb devices
and ensure your computer sees your HTC One S. This command should work even if you are in a custom recovery like TWRP or CW (but for gods sake, if your on CW, the first thing you should do is flash TWRP, but thats just an editorial opinion, lol).
Step #3: Type
Code:
adb push busybox /data/local/tmp
This pushes busybox to a temp folder on your HTC One S. Make sure you are pushing the busybox file and not the zip file. If you already have busy box installed you do not need to do this step. (you can delete it from this folder later if you like)
Step #4: Type
Code:
adb shell
to get into your linux shell. Then type
Code:
su
to get root access. Your command prompt should now be a # and not $.
Step #5: Type
Code:
chmod 755 /data/local/tmp/busybox
to fix permissions for busybox. You may not need to do this if you already have busy box installed with the correct permissions. If these instructions dont work with your version of busy box, try setting the permissions with this code but replace the path with the location of your busybox.
Step #6: Type
Code:
cat /proc/partitions
and just ensure you see mmcblk0p36. This is the sdcard partition for HTC One S
Step #7:Type
Code:
/data/local/tmp/busybox mkfs.vfat /dev/block/mmcblk0p36
Make sure you type this correctly. You dont want to format the wrong partition accidentally.
That should work. Pls let me know if it doesnt. If it doesnt work with your version of busybox just try using the one in the zip file below. Also remember, dont just push the zip file. Extract the busybox file from the zip and push that to your device instead.
Also, it may help to use adb through a custom recovery instead of being in your ROM (ie if it doesnt work when your phone is booted normally, try doing the steps with recovery loaded).
There are other methods to try too They would be:
Other Solutions
Other Method #1: Relocking your bootloader and using a compatible RUU with your phone. This will fully wipe your device
Other Method #2: If your computer sees your sdcard even if it cant open it when your device is connected, you can try formatting it that way (ie the way you would format any other drive on your computer)
Only use the busybox method if you are comfortable with it and if other methods have failed. You can learn more about the formatting command (ie mkfs.vfat) by googling it.
So if I got this right if I have busybox already I only have to do is step 7.
Almost, but yes, that is the key step. Although you would still want to open a terminal Window, either an adb shell or from the phone, and type su to get root, and double check to ensure the shell sees the partition. Also, I did hear in the one X forums that not every version of busy box worked. I would imagine an updated version would likely work though.
Sent from my HTC One S using xda premium
Step 4, a quicker way: adb shell su , get you into shell as root right away
AKToronto said:
Almost, but yes, that is the key step. Although you would still want to open a terminal Window, either an adb shell or from the phone, and type su to get root, and double check to ensure the shell sees the partition. Also, I did hear in the one X forums that not every version of busy box worked. I would imagine an updated version would likely work though.
Sent from my HTC One S using xda premium
Click to expand...
Click to collapse
Oh right hope I don't need it lol.
I think this should be moved to Q&A and replace the other sticky that's there.
Darknites said:
Oh right hope I don't need it lol.
I think this should be moved to Q&A and replace the other sticky that's there.
Click to expand...
Click to collapse
Im thinking it would be helpful to have this post there. Im not sure how I request to do that though. Should I PM a moderator?
AKToronto said:
Im thinking it would be helpful to have this post there. Im not sure how I request to do that though. Should I PM a moderator?
Click to expand...
Click to collapse
No idea but does sounds like a good start lol.
Darknites said:
No idea but does sounds like a good start lol.
Click to expand...
Click to collapse
I asked a moderater to review by clicking on the ! in the post, but I havent heard back yet. I also updated the post to be more n00b friendly too, and tried to cover off all sd card related issues.
AKToronto said:
I asked a moderater to review by clicking on the ! in the post, but I havent heard back yet. I also updated the post to be more n00b friendly too, and tried to cover off all sd card related issues.
Click to expand...
Click to collapse
Nice update. Ya I wish they hurry up with sorting it, the other one is a load of crap and this really should replace it.
Updated with a link to another good tutorial about pushing ROMs to the phone
Its like they don't care about stickys any more, come mods its about time this replaced the crappy one.
Cant get past the
'fastboot flash recovery ville_recovery_signed.img'
step at the moment, just keep getting 'waiting for device'.
Steveh8204 said:
Cant get past the
'fastboot flash recovery ville_recovery_signed.img'
step at the moment, just keep getting 'waiting for device'.
Click to expand...
Click to collapse
Does your bootloaderscreen say "fastboot usb" anywhere? There is an option that you have to select in your bootloader called fastboot... If it says fastboot usb then you are connected, and you shouldnt get a waiting for device error.
AKToronto said:
Does your bootloaderscreen say "fastboot usb" anywhere? There is an option that you have to select in your bootloader called fastboot... If it says fastboot usb then you are connected, and you shouldnt get a waiting for device error.
Click to expand...
Click to collapse
yea I got into the bootloader and then fast boot. ive managed to sort it now, for some reason my pc was the problem, I had to reboot my computer after a command window prompt otherwise I just got the waiting for device screen.
typical really, my laptop and phone both conspiring against me.
eventually managed to flash another recovery which did see my sdcard so all is good now.
thanks for your reply though!
AKToronto said:
For those who may be flashing ROMs, cannot mount the SD Card any more, and may have accidentally corrupted their SD Card, here are some helpful steps.
Click to expand...
Click to collapse
Dude, this works flawless!
Thought I had a soft-brick, but your instructions bring back my sd-card!
I choose the "advanced Option", it works fine....
Typing su-command generated an error message, but the other steps still functioned....
I will place link in section "helpfull links" in my signatur
Big THX to you good sir, ...
Steveh8204 said:
Cant get past the
'fastboot flash recovery ville_recovery_signed.img'
step at the moment, just keep getting 'waiting for device'.
Click to expand...
Click to collapse
Just format your phone using your PC... That's all you need to do...all those steps are overkill... Bootloader on phone... Connect to pc .. Navigate to devices on PC and format your phone...then flash recovery like stated above..
Sent from my One S using xda premium
$droyd$ said:
Just format your phone using your PC... That's all you need to do...all those steps are overkill... Bootloader on phone... Connect to pc .. Navigate to devices on PC and format your phone...then flash recovery like stated above..
Sent from my One S using xda premium
Click to expand...
Click to collapse
Some people had reported not being able to see their phone from their PC no matter what they tried... Hence the advanced steps
Dude add S3 stock recovery please.
Darknites said:
Dude add S3 stock recovery please.
Click to expand...
Click to collapse
Good point Darknites. Thank you. Do you have a link to S3 stock recovery? I dont seem to have one handy... But I did edit the OP to make that point a bit clearer (that the link is for S4 devices). Thanks again bud. Good catch.
AKToronto said:
Good point Darknites. Thank you. Do you have a link to S3 stock recovery? I dont seem to have one handy... But I did edit the OP to make that point a bit clearer (that the link is for S4 devices). Thanks again bud. Good catch.
Click to expand...
Click to collapse
Nope but a RUU will have it.