[SD CARD][HOW TO] Cant Mount SD Card or SD Card Corrupted - HTC One S

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.

Related

OBSOLETE.

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.

[TUTORIAL] Root HTC explorer

I decided to create a clean tutorial (as the method started with several bugs and issues) for those who want to root their HTC explorer.
will be editing it as new improvements appear.
btw, this will NOT change anything in your phone, it just make root access possible, if you want overclock and ext-2/3/4 partitions posible look here once you finish rooting with this tutorial.
1. Install HTC Sync on your PC
you can download it from: www.htc.com/www/help/htc-explorer/#download
(needed so computer recognises commands)
2. Unlock your phone's bootloader
- Following the steps in www.htcdev.com/bootloader
Note: HTC Explorer isn´t listed as a working device yet but it has been tested and works perfectly. Choose "all other supported models" when selecting device.
3. Add a recovery
That will allow you to install .zip ROMs. You can access to it in the menu android phones have when booting the phone after removing-inserting the battery and pressing "volume down" and "power" buttons simultaneously. (Other phones have different button combinations).
- Download View attachment 913094
- extract it in any window on your PC (ie: C:\HTC)
- run the recovery.bat with phone in fastboot mode (first option in the "3 android menu" ) and connected with usb.
Note: I edited the recovery.bat and removed any unnecessary commands so no errors occur
Done! You got the recovery installed if no errors, you can now install any compatible .zip ROM or app.
4. ROOT the device
- Place this View attachment Superuser.zip file somewhere in the microSD first.
- Go into Recovery mode ("volume down" + "power")
- install Superuser.zip with the option "install .zip from sd" from the recovery menu.
Note: after rooting dont restore to factory setting if you don´t want to end up in a bootloop, if this or similar happens you have to install a custom rom to fix it.
Click to expand...
Click to collapse
ROOTED !!
once rooted my advice is to install "link2sd". Excellent application after making a fat32 partition of your SD with programs like MiniTool partition wizard
It moves all applications directly to the SD when configuring it in automatic mode. (the entire application, not like the inbuilt phone option). See post # 9 for instructions.
enjoy
tnx,
I'll try asap this guide.
bye!
Thank you very much jaggy jags.
I did a test with superuser, and changing the files you said to "root explorer", but still giving error WIFI.
Definitely use the "plan B" and flashing the ROM China. Now they will wait out a new "European ROM" cooked.
Find the link in this forum for the European RUU, only I have not got the tools and skills to cook.
Sorry for my bad English, I use "go Translator"
al_nadita said:
Thank you very much jaggy jags.
I did a test with superuser, and changing the files you said to "root explorer", but still giving error WIFI.
Definitely use the "plan B" and flashing the ROM China. Now they will wait out a new "European ROM" cooked.
Find the link in this forum for the European RUU, only I have not got the tools and skills to cook.
Sorry for my bad English, I use "go Translator"
Click to expand...
Click to collapse
Sorry about that. I should have mentioned the files permissions have to be the same. I haven't checked this by myself I cannot confirm. I edited main post to say this.
Hello, I am just a beginner in android, what do u mean by the files permissions, u could explain in more detail what is the procedure for doing that ? or someone else that has this knowledge ...and write this step by step for rest of us that have little experience with setting android to be able on succeeding this. I want to get root on my explorer but I am afraid that will lose my wifi connectivity after and i am not sure that I will manage to replace that files with corresponding "matched files attributes".
Another request is if I could make a complete back-up of my original firmware/rom of my phone to have it in case that something vent wrong in process of rooting (to restore my phone on factory condition)? It is doable in any way it is any software for this? The European version will contain all languages or just base english?
thank you!
Reason for WIFI error after rooting
Just jumping in for letting u guyz know the reason reason for why u get wifi error
The zip "A310e_recovery...." has a boot.img in it, which is basically a kernel and if for any android device you flash a kernel you need dhk.ko or similar file (which should be in system/lib/modules) as mention alot earlier by jaggy. (this dhk.ko is a file which acompanies kernel/boot.img to run the data connection and wifi and other stuffs)
So basically to avoid all these, simple step is:
You can open recovery.bat present in the zip with a text editor (i suggest Notepad ++, default windows notepad will mess up the files) and delete the line "fastboot flash boot boot.img". now save and exit.
So, Dont flash the boot.img as it is not giving u guys any benefit. just flash recovery.img
@Jaggy. for link2sd, which ext r u using for sdcard partition , 1 2 3 ??????
jitin02 said:
@Jaggy. for link2sd, which ext r u using for sdcard partition , 1 2 3 ??????
Click to expand...
Click to collapse
Fat32 partition
No other format is supported by our rom.
I will be reuploading the recovery in a while with the .bat edited and clarifying the fat32 format.
So are you sure the recovery will be flashed just as good without the boot.img ?
jaggyjags said:
Fat32 partition
No other format is supported by our rom.
I will be reuploading the recovery in a while with the .bat edited and clarifying the fat32 format.
So are you sure the recovery will be flashed just as good without the boot.img ?
Click to expand...
Click to collapse
to be frank i have not tryd editting and using the .bat again
but the one i am sure is the fastboot method . flashing via adb
the command is "fastboot flash recovery recovery.img"
and the folder inwhich u need to put the recovery.img is the "tools" folder in adb main folder , which on my laptop got made in c drive (the main drive)
---------- Post added at 05:07 PM ---------- Previous post was at 04:30 PM ----------
I am not able to get this link2 sd thing work on my official Asian rom
jaggyjags, can u guide me on this one??
jitin02 said:
---------- Post added at 05:07 PM ---------- Previous post was at 04:30 PM ----------
I am not able to get this link2 sd thing work on my official Asian rom
jaggyjags, can u guide me on this one??
Click to expand...
Click to collapse
Sure! same procedure for both asian and stock rom (and any other y suppose).
using minitool wizard
make two primary fat32 partitions (not logical) of your micro sd. plug to computer using a sd card or usb adapter (dont plug phone by usb). the main partition at the left which will be the one detected by windows and then the second one (the rest of the available space).
And thats it, select the type of partition when opening link2sd and you will need to reboot to start moving apps (the app will ask to reboot).
note that if at anytime you clean rom partition (option in recovery) you will need to format the second partition again as this option makes it a ext-3 format and it is not supported.
Once in automatic, apps will install directly to the partition but if you link them manually you need to reboot to see the changes (at least me )
Recobery.bat error
run the recovery.bat in fastboot mode (first option in the "3 android menu" ) with phone connected with usb.
(Note: I edited the recovery.bat and removed any unnecessary commands so no errors occur)
Done!, you got the recovery installed if no errors, you can now install any compatible .zip rom.
Click to expand...
Click to collapse
Hi,
I have a problem when I run the Bat fie....
I can see in the CMD that:
C:\Downloads\A310E Recovery\A310E Recovery>adb wait-for-device
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
And then nothing else... I have nstalle HTC sync and I unloked the bootloader sucessfully.
I don't known were I'm wrong...
Can anybody help me?
Thank u so much
acasanovas said:
Hi,
I have a problem when I run the Bat fie....
I can see in the CMD that:
C:\Downloads\A310E Recovery\A310E Recovery>adb wait-for-device
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
And then nothing else... I have nstalle HTC sync and I unloked the bootloader sucessfully.
I don't known were I'm wrong...
Can anybody help me?
Thank u so much
Click to expand...
Click to collapse
Try this and report back:
Here i am assuming u have adb installed on ur pc/laptop
take ur device battery out and insert it back.
while long pressing volume down press power button untill u see a menu with 3 androids at the bottom.
now select fastboot option and connect via USB. now u will see fastboot usb or something like that.
now open cmd and enter the path to ur adb folder . for example in my case my folder is in my c drive and i enter
HTML:
cd\
cd android-sdk-windows\tools\
place the recovery.img in adb's tool folder.
Now enter following (this is after u navigated to the adb's tool folder)
HTML:
fastboot flash recovery recovery.img
fastboot reboot
If all went right, so u have the custom recovery (clockworkmod recovery) on the device or if not please post here , we will try help u again
acasanovas said:
Hi,
I have a problem when I run the Bat fie....
I can see in the CMD that:
C:\Downloads\A310E Recovery\A310E Recovery>adb wait-for-device
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
And then nothing else... I have nstalle HTC sync and I unloked the bootloader sucessfully.
I don't known were I'm wrong...
Can anybody help me?
Thank u so much
Click to expand...
Click to collapse
download the recovery again and try. It is a simple problem. Reuploaded de recovery and deleted "adb wait for device" command line because it keeps waiting endlesly. I forgot to delete before, sorry about that.
try it and tell me how it goes
@jitin02 it is simpler than that I already eliminated the adb command and should work with no issues. Recovery reuploaded!
It works and wifi too!
jaggyjags said:
@jitin02 it is simpler than that I already eliminated the adb command and should work with no issues. Recovery reuploaded!
Click to expand...
Click to collapse
Thaks @jitin02 and @jaggyjags it works!!!! so nice!!
now how can I install de superuser?
Where and how i have to put that :
adb push bash /system/bin
adb push profile /system/bin
adb push su /system/bin
adb push busybox /system/xbin
adb push su /system/xbin
I have the superuser folder in the same directory of adb, an then?
Can u help me again?
Thank u very much!
Easy, put it in the Microsd card and then open recovery in the 3 android menu (pressing -volume and power for 10 seconds after taking and placing battery). install it with the "install zip from sd" option and select your .Zip
confirm it moving up and down with volume keys
It works perfectly and wifi too! Thank u so much again!
Sent from my HTC Explorer A310e using XDA App
U can share for me back up this rom?
Don't understand, sorry. what rom do you mean?
Everything worked perfectly on my Italian/Vodafone HTC explorer!
No need to create any partition on my SD card to move apps using Link2SD. Is it advisable to do so?
I moved many useless vodafone apps on SD, wanting an European custom rom
Thanks so much!
jaggyjags said:
Don't understand, sorry. what rom do you mean?
Click to expand...
Click to collapse
This rom which u're using in first post.

[HOW-TO] ADB Push a ROM to your phone

Hello all,
I've seen multiple people who recently, by one way or another, have a phone that have the bootloader unlocked, device rooted, and a recovery flashed...but for some reason you don't have a ROM flashed and your phone won't boot up past the bootanimation. If you're in that situation, this will hopefully help solve that issue.
What this thread is designed to do is inform you how to flash a ROM.zip file onto your seemingly bricked HTC One S device that you can't boot up. As you know, usually if your phone boots up, you just plug it into your computer, mount it, and just drag and drop the file. Well, for those of you that have no way to do that, I hopefully have a fix for you!
Requirements:
Unlocked Bootloader/Rooted Device
CWM Recovery flashed from fastboot.
Basic knowledge of adb/fastboot commands
Steps:
- Download your ROM of choice (referred to as ROM.zip) and place it wherever your ADB is on computer's harddrive (referred to as c:\AndroidSDK\tools)
- Boot your phone into Recovery and select the "Mounts & Storage" screen
- Plug your phone into your computer using USB Data Transfer Cable
- Ensure in Recovery that your phone shows "Unmount /sdcard/" and "Unmount /system/" (If they do not show this automatically, just press each one once respectively as pressing just toggles Mount and Unmount)
- Open Command Prompt on your computer by doing Start -> Run -> cmd
- In Command Prompt, type "cd c:\AndroidSDK\tools" replacing AndroidSDK\tools with wherever your adb and ROM are located.
- This is probably the most important part - Still in Command Prompt, type "adb push ROM.zip /sdcard/ROM.zip" replacing ROM with the EXACT name of the ROM file and including the .zip piece on both ends. This may take a minute or two...or four, but you will see a message in Command Prompt saying something like <12345678kb to 1234567kb>. That is just telling you that the file was pushed properly. (I did not include that message in the picture below)
- Once this has completed, unplug your phone from your computer and close the Command Prompt window
- Back in Recovery, go to Recovery's main screen and Do a "Factory Reset", "Wipe Cache Partition", and "Wipe Dalvik Cache [which is in the Advanced menu of Recovery]"
- When these are all done, from Recovery's main screen, select "Install ZIP from SD Card" and then "Choose file from SD Card" and select the ROM.zip file you just pushed from your computer to the SD Card. If you do not see the file, go back to Mounts and Storage and toggle them to say "Mount /sdcard/" and "Mount /system/" and then go back and try to fine the ROM.zip file. If you still do not see it, it was not pushed correctly...go back and ensure you were letter for letter with the name and the file path.
- Once the screen in Recovery says "Install from SD Card Complete.", go back to Recovery's main screen yet again and select "Reboot system now" - If your device fails to Install the ROM.zip, I had this happen to me. You must push the CWM SuperSU ZIP (the .zip file is found at the end of this thread)file as outlined before and Install THAT .zip file in Recovery, then reboot Recovery and Install the ROM.zip from SD Card.
- Let your phone have some time to boot up...initial boot from installing a new ROM have histories of taking a couple minutes.
- You should now be on a working HTC One S running whatever ROM you decided to flash.
Conclusion:
I hope you got your phone working again and I hope this helped. Please feel free to critique this guide as I am quite new to the HTC One S, but not new to rooting phones at all. If you have questions, please comment and ask or don't hesitate to shoot me a PM...I'm more than willing to help.
I hope this helped all of you who may be in the situation I was in and the situation I've seen a couple of people in.
Thanks for this information goes out to doktortaru, strker45, and torxx.
Don't need this tutorial as im not having this issue but wanted to say thanks for posting it. This should definitely help some people in the future! Great write up!
+1
Sent from my Transformer TF101 using xda premium
Thank you man.
Very informative for self learning!
Nice tutorial. But wrong forum.
Sent from my HTC One S using Tapatalk 2
you don't need to finish the command with rom.zip:
adb push ROM.zip /sdcard
is enough.. Also you should so the ROM.zip in the same folder as ADB, with the your picture.
Zylith I tried that when my phone was messed up, but I couldn't find the SD Card. However when I includes the name of the zip at the end, it worked.
Sent from my HTC VLE_U using xda premium
thanks for the detailed guide! the issue im having is not being able to mount /sdcard in recovery. I can successfully adb push the zip to the sdcard but when i try to flash in recovery, it gives me error mounting /sdcard.
can you post a quick guide on how to flash via fastboot the boot.img and system.img from the RUU? i think thats the only option i have at this point. and thanks again for this guide!
mrroey said:
thanks for the detailed guide! the issue im having is not being able to mount /sdcard in recovery. I can successfully adb push the zip to the sdcard but when i try to flash in recovery, it gives me error mounting /sdcard.
can you post a quick guide on how to flash via fastboot the boot.img and system.img from the RUU? i think thats the only option i have at this point. and thanks again for this guide!
Click to expand...
Click to collapse
When you click to mount /sdcard/ before you push the ROM over, what does Recovery tell you? What error is it?
So when I press mount sdcard it shows me Error mounting /sdcard. Same message when I try to format the sd card.
Adb seems.to push the file to sd card successfully in cmd. However when I go to install from zip it gives me "Cannot mount /sdcard"
I tried partitioning the sd card in recovery but that doesn't seem to have any effect.
mrroey said:
So when I press mount sdcard it shows me Error mounting /sdcard. Same message when I try to format the sd card.
Adb seems.to push the file to sd card successfully in cmd. However when I go to install from zip it gives me "Cannot mount /sdcard"
I tried partitioning the sd card in recovery but that doesn't seem to have any effect.
Click to expand...
Click to collapse
Try my solution here:
http://forum.xda-developers.com/showthread.php?t=1630459
Sent from my HTC One S using Tapatalk 2
Yea, I had trouble mounting anything prior to all of this.
I had to do Clear Storage in the bootloader, reinstall CWM Recovery and SuperSU and I got it to work. Hopefully we don't have too many more people with this issue. If we do, I'll be around to help.
I'm always trying to learn and try new things, so hopefully I'll be able to help with more stuff in the future.
just to make sure, for the T-Mobile One S folks, you guys aren't able to mount /system with adb yet right?
as in.. being able to adb push files to the /system folder ..
in the current state of our root.
I think that this thread is definitely in the RIGHT section !! And i also think it should be stickied !!
Its a very useful thread / Guide as we dont have mount USB storage option working in CWM... So if something fails, And you are left with no flashable ROM on your phone THIS guide will save your life
Thanks to the OP !!
Yes definitely this should be stickied! Saved me a lot of trouble and headache.
can you do one for mac?? please
Can this be moved/stickied possibly? This seems to be a decent size problem for many people.
if adb is too hard then droid explorer does the hard work for you.
Sent from my Amazon Kindle Fire using xda premium
Unable to see how is this tutorial helpful
Its like pushing a FILE to ur SDCARD with ADB
So the title is misleading; as installing a ROM is a different issue
om.thelostone said:
Unable to see how is this tutorial helpful
Its like pushing a FILE to ur SDCARD with ADB
So the title is misleading; as installing a ROM is a different issue
Click to expand...
Click to collapse
There are a lot of users who love to flash new things but who don´t deal with all the computer stuff every day. So when you are addicted to the install instructions but something unexpectful happens and your phone is in boot loop this guide is very useful.
When this is stickied it could a) avoid heard attacks of users who think "OMG I have bricked my phone" and b) avoid that dev threads become off topic.

Bootloop after Trickdroid tweaks

Hello Forum,
I have a problem with my Htc One S today i installed Trickdroid 8.0 and it worked fine so i wanted to install the tweaks too. So i selected what i wanted and when the phone started it got stuck at the bootloader screen. I thought it just needed some time but after 15 minutes i gave up and turnt it off. Then i went into the recovery to install the rom newly but it always says it can't mount the sd card. Already relocked the bootloader and tried to install the europe ruu 1.78 but i got error 131 i have read that might be, beacause mine was branded by T-Mobile (but no simlock or else)
Really need help appreciate any answer
Really no one knows how i can fix this ? Need to fix it pretty soon because i need my phone :/ I can't even turn mine off, so i just let the battery die don't think that's to good either
Boot into recovery and ref lash. What tweak did you do? Not all work with 8.0. Tweaks have not been updated for this version. Make sure to do a full wipe.
j0hnh0lmes said:
Boot into recovery and ref lash. What tweak did you do? Not all work with 8.0. Tweaks have not been updated for this version. Make sure to do a full wipe.
Click to expand...
Click to collapse
I can't reflash in recovery, because it always says "can't mount sd card"
Don't remember all of the tweaks i did but i did the nova launcher, remove sense, some apps, all of the tweaks on the first page and some other.
Okay now I did a "clear storage" and a "reset to factory defaults" with a stock recovery and after that i reinstalled the custom recovery again. Now I can access the sdcard again but it's empty of course. Then i bootet in recovery and tried to push the trickdroid zip on to the sdcard via adb like this "adb push Trickdroid_v8.0.0.zip /sdcard/Trickdroid_v8.0.0.zip" but then it says:
daemon not running starting it now on port 5037
daemon started successfully
protocol failure
and simply ends. How can I push the Rom really need help, because my phone has no rom at all right now ?
ah okay needed to use the adb in the android sdk folder not in the little fastboot folder i had it just worked
Not at home to double check your command line--sounds like that is issue
But, you can type adb devices first to see if phone is recognized
I usually cd to the directory I have adb/fastboot files in, put zip on C: root
and type: adb push C: "then the rest"
rugmankc said:
Not at home to double check your command line--sounds like that is issue
But, you can type adb devices first to see if phone is recognized
I usually cd to the directory I have adb/fastboot files in, put zip on C: root
and type: adb push C: "then the rest"
Click to expand...
Click to collapse
Thanks for your help but as i have written i already got it back working thread can be closed
Sorry,
I posted before your edit showed up--
Glad to hear.
steps for next time
Hi, just before the thread is locked.
What has helped me in more of these occassions:
1. Make sure you read the install instructions of the ROM builder (I overlooked the 'flash Boot.img' which was added after some version)
2. Make sure you don't 'custom' work your memory (no partitioning etc).
3. First install the ROM and do REQUIRED afterwork (most often: Data/factory reset. Which doesn't wipe your photo's or just your account information and saved settings that will interfere with new rom options)
4. after making sure it boots and it reboots.
5. If this is the case, make sure you get the tweak package pointed out by the rom builder.
6. If all else fails, first read up on XDA and rom builder's site (often community on XDA) THEN start actions well informed.

[Q] Help in London

Dear All,
I own a Asus EeePad Transformer TF101 tablet. I have accidentally bricked my tablet (wiped out the Android operating system) whilst attempted to upgrade to Android 4.4.
I have contacted various IT Repair services, but they have been unable to repair the tablet. It is regrettable that the tablet cannot currently be repaired because it is a lovely machine.
Please could you let me know if there are any Android experts who can help me? Your support is much appreciated.
Best,
Stephen Tang
st1974 said:
Dear All,
I own a Asus EeePad Transformer TF101 tablet. I have accidentally bricked my tablet (wiped out the Android operating system) whilst attempted to upgrade to Android 4.4.
I have contacted various IT Repair services, but they have been unable to repair the tablet. It is regrettable that the tablet cannot currently be repaired because it is a lovely machine.
Please could you let me know if there are any Android experts who can help me? Your support is much appreciated.
Best,
Stephen Tang
Click to expand...
Click to collapse
Can you boot in your custom recovery?
alray said:
Can you boot in your custom recovery?
Click to expand...
Click to collapse
Clockwork Mod Recovery is installed, but doesn't recognise the memory card.
st1974 said:
Clockwork Mod Recovery is installed, but doesn't recognise the memory card.
Click to expand...
Click to collapse
have you tried another sd card?
alray said:
Can you boot in your custom recovery?
Click to expand...
Click to collapse
alray said:
have you tried another sd card?
Click to expand...
Click to collapse
Yes, I've tried another SD card and tried reformatting in different ways too (e.g. FAT and FAT32) but no luck
st1974 said:
Yes, I've tried another SD card and tried reformatting in different ways too (e.g. FAT and FAT32) but no luck
Click to expand...
Click to collapse
Ok so there might be a problem with the sdcard reader or maybe with the recovery. But anyway you should be able to use adb to push a rom to your transformer when booted in recovery mode.
alray said:
Ok so there might be a problem with the sdcard reader or maybe with the recovery. But anyway you should be able to use adb to push a rom to your transformer when booted in recovery mode.
Click to expand...
Click to collapse
I've tried Easyflasher and other things but no luck. The recovery won't mount the SD card.
I haven't tried adb - apparently it's very complicated to do and I'm not exactly the most technically gifted person!
st1974 said:
apparently it's very complicated to do
Click to expand...
Click to collapse
And who told you that?
alray said:
And who told you that?
Click to expand...
Click to collapse
I've read the instructions on a Forum here. I'm not confident about using adb so if you have easy to follow instructions it's much appreciated
@st1974
---------- Post added at 02:05 AM ---------- Previous post was at 01:34 AM ----------
Even easier you could use adb to push the newest twrp and use the built-in MTP function so you could see your tablet as a Storage device on windows, then drag and drop a rom to your internal storage and flash it.
So make sure you have all you drivers installed for the tf101 on your computer
download and install "minimal adb and fastboot"
download twrp 2.8.1.1 and save it in the same folder where you have installed minimal adb and fastboot"
Boot your phone in CWM recovery
In the folder where you have installed minimal adb and fastboot, hold left SHIFT and right click a blank space in that folder, select "open a command prompt here".
in the command prompt, type:
Code:
adb devices
you should see an output like this
Code:
List of devices attached
(your tf101 serial number) recovery
If yes then proceed with the next step, if no, post back here.
in the command prompt, type this:
Code:
adb push signed_twrp-2.8.1.1_tf101.zip /sdcard
and wait for the output, something like
Code:
1330 KB/s (5215688 bytes in 3.828s)
then in cwm, select "install zip from sdcard" and navigate to find "signed_twrp-2.8.1.1_tf101.zip" and install it.
then power off your tablet and reboot in recovery mode again, but this time you should boot in TWRP 2.8.1.1
when booted in recovery (TWRP) You should see your tablet as a storage device in windows, so all you need to do from there is to drag n drop a rom like this one to your device in windows and install it using twrp.
alray said:
@st1974
---------- Post added at 02:05 AM ---------- Previous post was at 01:34 AM ----------
Even easier you could use adb to push the newest twrp and use the built-in MTP function so you could see your tablet as a Storage device on windows, then drag and drop a rom to your internal storage and flash it.
So make sure you have all you drivers installed for the tf101 on your computer
download and install "minimal adb and fastboot"
download twrp 2.8.1.1 and save it in the same folder where you have installed minimal adb and fastboot"
Boot your phone in CWM recovery
In the folder where you have installed minimal adb and fastboot, hold left SHIFT and right click a blank space in that folder, select "open a command prompt here".
in the command prompt, type:
Code:
adb devices
you should see an output like this
Code:
List of devices attached
(your tf101 serial number) recovery
If yes then proceed with the next step, if no, post back here.
in the command prompt, type this:
Code:
adb push signed_twrp-2.8.1.1_tf101.zip /sdcard
and wait for the output, something like
Code:
1330 KB/s (5215688 bytes in 3.828s)
then in cwm, select "install zip from sdcard" and navigate to find "signed_twrp-2.8.1.1_tf101.zip" and install it.
then power off your tablet and reboot in recovery mode again, but this time you should boot in TWRP 2.8.1.1
when booted in recovery (TWRP) You should see your tablet as a storage device in windows, so all you need to do from there is to drag n drop a rom like this one to your device in windows and install it using twrp.
Click to expand...
Click to collapse
Thanks! I'll give it try and let you know how I get along
st1974 said:
Thanks! I'll give it try and let you know how I get along
Click to expand...
Click to collapse
Hi There,
My IT repair people tried your instructions and they said that the tablet won't accept the any of the instructions. Do you have any other ideas?
Best,
Steve
st1974 said:
Hi There,
My IT repair people tried your instructions and they said that the tablet won't accept the any of the instructions. Do you have any other ideas?
Best,
Steve
Click to expand...
Click to collapse
Well all you need to do is to push a rom to your tablet using adb, which should be done when booted in recovery mode. Don't even need to use an sdcard. I don't have any other ideas except finding another IT or a friend that know how to use ADB. Or you could send it to me but im near Montreal so I don't think it will worth it vs shipping cost.
Btw im using this method to flash roms on my gf's transformer without issue (the sd card port is damaged so I can't use sd cards)
Thanks for the prompt response. So the Repair Man should follow through steps 1-7. What happens at Step 8? Is this where he would push a ROM to the tablet using ADB - instead of using CWM?

Categories

Resources