Related
Hi all,
I am trying to flash my G1 to one of the nice custom roms. I flashed the recovery and spl just fine.
Now I cannot flash anything. I've tried different roms (cyanogen and dude's) and even tried flashing the radio. No love. The error is that it cannot find my sdcard or update.zip.
Phone is pvt and is rooted.
Any thoughts?
Thanks,
Hank
What steps did you take to root? Is your card fat32?
Did you mount the sdcard on windows? If you did, rename the file to update not update.zip on WINDOWS! Also, can you even mount your sdcard? If not, then there's your problem.
I followed the rooting instructions from this site. i do have # in the local terminal.
i can mount the sd card and i did mount in windows to transfer fikes over. i should just name them update not update.zip?
djscamper said:
I followed the rooting instructions from this site. i do have # in the local terminal.
i can mount the sd card and i did mount in windows to transfer fikes over. i should just name them update not update.zip?
Click to expand...
Click to collapse
That will probably help.. By default Windows hides the extension (the .zip part) so when you rename it to "update.zip" you actually make it update.zip.zip
Easy way to check is look at the original file.. if it says something like
Code:
update-cm-3.6.6-signed.zip
you need to rename to
Code:
update.zip
if it says
Code:
update-cm-3.6.6-signed
then just call it
Code:
update
Thanks. Getting a signature error now.
Will try a different version of the file once I am off Caltrain.
Yeah - if you have a modded recovery and get that error, it's most likely a bad download. Good luck.
That did it. It is always something so simple.
Thanks a ton. Hopefully this thread will help someone else as well.
Ok guys I noticed a lot of people are getting stuck with this myself included and for me it was because the information I needed was fragmented all over the place, So here is all the information that I used some parts have been edited to fit the purpose of rooting 1.01 as there is no definative guide at the minute.
1st thing to do is make a goldcard even if you already have a working goldcard make it again mine was working for other phones but wouldnt work for this.
All credit for the goldcard guide goes to BlaY0
BlaY0 said:
Here are few easy steps on how to make Goldcard without taking it out of your phone but you have to be root (VISIONary temproot is fine).
You will be doing this from command prompt:
Code:
adb shell
su
First you need to find out sdcard's CID:
Code:
cat /sys/class/mmc_host/mmc0/mmc0:*/cid
...copy it into text box on http://hexrev.soaa.me/. Now go to http://psas.revskills.de/?q=goldcard and put in the reversed CID you have got on previous web page. Push goldcard.img to your phone via 2nd command prompt:
Code:
adb push goldcard.img /data/local/
...unmount sdcard via Settings, go back to 1st command prompt and make a backup then make goldcard:
Code:
dd if=/dev/block/mmcblk0 count=1 of=/data/local/sdcard_backup.img
cat /data/local/goldcard.img > /dev/block/mmcblk0
sync
exit
You may also pull that backup to your PC:
Code:
adb pull /data/local/sdcard_backup.img .
Click to expand...
Click to collapse
The 2nd guide you will need to use is also by BlaY0
BlaY0 said:
Preface
Because there are too many ppl without any knowledge spreading false findings and statements I decided to write this HOWTO.
Audience
This HOWTO is primarily ment for those who already have rooted Legends but they recently experienced problems flashing CM's or new Vodafone FroYo boot.img.
Background
HBOOT is like a BIOS in our PCs and to cut a long story short it also contains partition table for phone's internal storage. That means it has info on where exactly certain partition starts and how big it is.
At HTC they decided to partition Legend's internal storage this way:
misc 640 kB
recovery 4,375 MB
boot 2,5 MB
system 240 MB
cache 40 MB
data 185 MB
...but as we found out (first with CM nightly) boot partition was a little short for the boot.img to fit in if we had one or more bad cells (sectors) on it. Eventually we found out that quite some Legend's had bad cell on boot partition and those unfortunate souls that owned such phone were unable to upgrade to Vodafone FroYo rooted ROM too.
I think that HTC also recognized that Legend's boot partition was kinda small so they rearanged partition table in HBOOT 1.00 a bit making boot partition bigger (now it is 3 MB) by shrinking recovery partition a little.
So now we know that some of us actually need HBOOT 1.00 in order to flash FroYo's boot.img without a problem. But how do we keep root then?
Prerequirements
Android SDK (primarily adb)
working USB drivers (for adb to work)
goldcard (in case you are trying to flash ROMs with different CID than your phone has)
ClockWorkMod recovery (if your Legend is already rooted)
Rerequirements
Vodafone FroYo OTA update (actually just firmware.zip from OTA)
Legend rooting tools (just testimage.zip)
Hack 4 Legend v5(just misc1-2.img and flash_image)
VISIONary r13(r14 is out also but i haven't tested it yet)
Instructions
I will split instructions into two parts... for already rooted phones and phones that were already updated with Vodafone OTA thus they lost root.
Already OTA updated with HBOOT 1.00
That one is relatively easy. You could also follow Paul's guide but I like my approach better
Connect your phone to your PC. Second you have to install VISIONary r13 into your phone and do the "temproot" procedure. After a successful "temproot" you should be able to adb shell and then su. Fire up command prompt and issue:
Code:
adb shell
su
...you should have root privileges now (showing #). Next thing is backing up misc partition and replacing it with one from hack4legend-v5.zip. Extract this zip somewhere and fire another command promt there. Now you should upload flash_image binary and misc1-2.img:
Code:
adb push flash_image /data/local/
adb push misc1-2.img /data/local/
...switch back to 1st command prompt and change permission of flash_image_binary:
Code:
chmod 755 /data/local/flash_image
...and backup your current misc partition:
Code:
cat /dev/mtd/mtd0 > /sdcard/misc_backup.img
Now flash misc1-2.img:
Code:
/data/local/flash_image misc /data/local/misc1-2.img
exit
...and you are set to downgrade retaining HBOOT 1.00.
Unzip r4-legend-root.zip and find testimage.zip in it. Put it on your phone's sdcard renaming it to LEGEIMG.zip. You can then reboot into bootloader issuing:
Code:
adb reboot bootloader
...from command prompt. Phone will reboot and find LEGEIMG.zip on your sdcard, copy it into RAM and check it. If you get CID error at this point, then you don't have goldcard. Make your sdcard gold and try again. After successful flash and reboot you may remove LEGEIMG.zip from sdcard. Next step is upgrading of rooted FroYo ROM. Put FroYo update ROM zip to your sdcard and install it via ClockworkMod recovery. You may also flash backed up misc partition after that. Still in recovery mode and hooked with your PC switch to command prompt and restore it back:
Code:
adb shell
flash_image misc /sdcard/misc_backup.img
exit
...and reboot.
Click to expand...
Click to collapse
So by now you will be on an unrooted Eclair rom. The third guide I used was by David Cogen
David Cogen said:
I. Before You Begin
1. YOU MUST BE ON VERSION 1.31 IN ORDER TO ROOT THE LEGEND, IF YOU ARE NOT YOU CAN DOWNGRADE USING THIS PROCEDURE.
2. This will erase all the data on your phone so please at least sync your contacts with Google before continuing.
3. You must have HTC Sync version 2.0.33, not a newer version. Uninstall HTC Sync and install this version instead.
1. Download the Rooting Tools
Legend Rooting Tools
2. Unzip them to the C: drive on your computer (so the file path is C:\r4-legend-root\)
3. Turn off your phone and turn it back on by holding down Back and Power until you see Fastboot come up on the screen. Push the Power button while highlighting Fastboot on the phone and Fastboot should show up in red now on the phone (if it doesn’t push Power again until it does).
4. Plug the phone in via USB cable to the computer.
5. Open the folder you extracted to the C drive and double click “step1-windows.bat” and wait for it to finish.
6. Once you see the menu on the phone come back up, navigate to BOOTLOADER and push power, then navigate to RECOVERY using the volume buttons to navigate and the power button to select and the phone should boot to the ! screen.
7. Now on the computer double click the “step2-windows.bat” file and wait for it to finish. (UPDATE 12.13.10 – You MUST have HTC Sync version 2.0.33 not a newer version for step2 to work. Please uninstall HTC Sync and download and install this version instead, unplug then plug your phone back in, then rerun step2-windows.bat).
8. Now you should see a custom recovery screen, using the optical trackpad navigate to Wipe and push on the trackpad to select it. Then navigate to Wipe data/factory reset and select that.
9. Once that is done, push volume down to go back to the main menu and select Flash zip from sdcard and select the rootedupdate.zip file and wait for it to flash. All done, you have root access and can use any root required app! Enjoy!
IV. Load a Custom ROM etc (Optional)
1. Head over to our How To Load a Custom ROM on the HTC Legend procedure and continue with that to load custom ROMs and other fun stuff!
Thanks to Paul at Modaco for his awesome scripts!
Click to expand...
Click to collapse
By now you should have HBOOT 1.01 with a rooted Ecclair ROM and Clockwork Recovery Mod So you can flash any custom rom that you like although I would recommend you try B 0.2
If you use this guide, you do so at your own risk.
wow...nice tutorial
I've requested that this goes in the stickies. Well done mate
FeaRThiS said:
The 2nd guide you will need to use is also by http://forum.xda-developers.com/member.php?u=609649
So by now you will be on an unrooted Eclair rom.
Click to expand...
Click to collapse
Question: So the second guide is to downgrade Froyo 3.5 to Eclair 1.3?
smartsreenath said:
wow...nice tutorial
Click to expand...
Click to collapse
Thanks glad it helped.
TheGrammarFreak said:
I've requested that this goes in the stickies. Well done mate
Click to expand...
Click to collapse
Cheers m8 Might not be the best way but it was the only way I managed to root mine on 1.01.
nxdu said:
Question: So the second guide is to downgrade Froyo 3.5 to Eclair 1.3?
Click to expand...
Click to collapse
Fist FroYo is 2.2 not 3.5 and Eclair is 2.1 not 1.3 but yes it is to downgrade to Eclair so that you can root and then upgrade back to FroYo so you end up with rooted FroYo.
FeaRThiS said:
Fist FroYo is 2.2 not 3.5 and Eclair is 2.1 not 1.3 but yes it is to downgrade to Eclair so that you can root and then upgrade back to FroYo so you end up with rooted FroYo.
Click to expand...
Click to collapse
FroYo is HTC WWE 3.x, and éclair is 1.x and 2.x
Thank you!, so it doesn't matter which version of Froyo you're on but what the Hboot version of your phone is on that varies what guide you'll be using ? mine is asia's 3.15.707.3
Yes , one last thing;o how do I check whether all my contacts are properly syncd with Google ? As gmail does not display any of my contacts, if so how would I go about doing it ?._.
Sent from my HTC Legend using XDA App
TheGrammarFreak said:
FroYo is HTC WWE 3.x, and éclair is 1.x and 2.x
Click to expand...
Click to collapse
Ahh I was talkin Android version not HTC version more confusion.
Sent from my HTC Legend using XDA App
FeaRThiS said:
You will be doing this from command prompt:
Code:
adb shell
su
Click to expand...
Click to collapse
Creating a goldcard procedure
What I did, installed visionary r13, clicked on "temproot now"
Access the adb shell via "cd c:\windows-anroid-sdk\platform-tools\adb shell"
however I got the $ sign and when I typed su it says "permission denied" what might be the problem? sorry._. new to this
Hi Folks,
If you don't mind me asking, do you reckon this will work for HTC Wildfire running 2.2 RUU from shipped ROMs with Hboot of 1.01? TIA.
First I was like... but then I was like
Hey Guys,
I hope someone can help me. I followed some tutorials about rooting the HTC Legend. I followed some steps but when I had to downgrade my HTC Legend it went wrong, whatever I try every methode keeps saying, permission denied. And when I use the RUU Bootloader it says some kind of error:S I really want my Legend to get rooted! Can anyone help me?
Kind Regards Tom
After rebooting the bootloader in the second guide, it can't find LEGEIMG.zip. It says image is wrong. I have the LEGEIMG.zip in goldcard root. please help!
haha123 said:
After rebooting the bootloader in the second guide, it can't find LEGEIMG.zip. It says image is wrong. I have the LEGEIMG.zip in goldcard root. please help!
Click to expand...
Click to collapse
Format your SD card in a card reader, as FAT32, then create the Goldcard as described in the first post in this thread.
Make sure you get a NEW goldcard.img as Blay0 describes in the quoted post, my old Goldcard image I used with the 2.1-update1 no longer worked and I needed to get a new one. I think the CID changed when upgrading to 2.2.
This was my problem and doing what I described above solved my problem.
TheLegendaryJay said:
Format your SD card in a card reader, as FAT32, then create the Goldcard as described in the first post in this thread.
Make sure you get a NEW goldcard.img as Blay0 describes in the quoted post, my old Goldcard image I used with the 2.1-update1 no longer worked and I needed to get a new one. I think the CID changed when upgrading to 2.2.
This was my problem and doing what I described above solved my problem.
Click to expand...
Click to collapse
What about this?:
What I did, installed visionary r13, clicked on "temproot now"
Access the adb shell via "cd c:\windows-anroid-sdk\platform-tools\adb shell"
however I got the $ sign and when I typed su it says "permission denied" what might be the problem?
justcookiesncream said:
What about this?:
What I did, installed visionary r13, clicked on "temproot now"
Access the adb shell via "cd c:\windows-anroid-sdk\platform-tools\adb shell"
however I got the $ sign and when I typed su it says "permission denied" what might be the problem?
Click to expand...
Click to collapse
you could try visionary r14 but r13 worked fine for me and many others.
Is this safe?
(or safe as it can be?)
I was previously rooted, but then the microphone on my handset broke, and I replaced it under warranty.
I now have a new handset, but it's back to the stock Vodafone UK Froyo build, with HBOOT 1.0
I'm really liking the look of Blay0's ROM, but fearful of breaking the phone...
brypie said:
Is this safe?
(or safe as it can be?)
I was previously rooted, but then the microphone on my handset broke, and I replaced it under warranty.
I now have a new handset, but it's back to the stock Vodafone UK Froyo build, with HBOOT 1.0
I'm really liking the look of Blay0's ROM, but fearful of breaking the phone...
Click to expand...
Click to collapse
I would say its as safe as it can be and BlaY0's rom is amazin 1500+ score on quadrant with data2ext
I have personally used this method to root my phone without any problems but if you are on hboot 1.00 there may be a easier/safer way of rooting but I am unsure about that.
Trying it now...
In the 2nd guide, I can't crete the misc_backup.img --> "read-only file system".
Is this the S-ON / S-OFF thing?
How can I get around this?
Thanks.
brypie said:
Trying it now...
In the 2nd guide, I can't crete the misc_backup.img --> "read-only file system".
Is this the S-ON / S-OFF thing?
How can I get around this?
Thanks.
Click to expand...
Click to collapse
Nothing to do with s-on looks like you dont have root when you type su in adb do you get a # ?
FeaRThiS said:
Nothing to do with s-on looks like you dont have root when you type su in adb do you get a # ?
Click to expand...
Click to collapse
Yep - tempRoot using Visionary
EDIT - just figured it out - I still had the SD Card connected as a disk drive to my PC D'oh!
I keep on getting this error when trying to flash a custom ROM into my phone. Is there a way to manually apply the ROM?
I tried booting into recovery then conecting my phone through usb and running the following commands through cmd: "adb push update.zip /sdcard/update.zip". then it tells me if I want to push "update.zipj", but once I press enter it gives me, "error: device not found"
Here's the cmd log:
Code:
C:\Users\Admin>cd\
C:\>cd\android\android-sdk\tools
C:\Android\android-sdk\tools>adb devices
List of devices attached
000000000000 recovery
C:\Android\android-sdk\tools>adb push update.zip /sdcard/update.zip
protocol failure
C:\Android\android-sdk\tools>
C:\Android\android-sdk\tools>adb push update.zip /sdcard/update.zipj
error: device not found
C:\Android\android-sdk\tools>
Am I doing the manual flashing corrrectly? I figured manually flashing the ROM would stop the error from coming up. Could someone either show me or point me in the right direction on how to fix this error and/or possibly how to manually flash the ROM in detail. I've already searched and I keep seeing threads with people asking for similar problems but with no real answer.
any help is appreciated.
1. adb push does not flash a ROM - just copies the file to the SD card
2. Looks like you are in recovery and you cannot push a file, unless you mount the SD card in recovery
Not sure what you mean "manually apply the ROM". ROM flash has to be manual, there's nothing automatic about it.
And, if you had really searched... I am sure you would have found atleast 10 references on how to flash a ROM.
Anyways, here's a link that will give you enough information to just about do anything with your CDMA Hero: http://forum.xda-developers.com/showthread.php?t=1063843. BTW, this is a sticky right at the top of where you posted this question...
BOOM. lol. Also the status 0 is an improper mount command, or you have a bad version of busybox. What zip were you trying to flash out if curiosity? And are you rooted, if so how did you do it?
What I meant when I said "manually" I meant to do it through command prompt instead of Rom manager or through recovery. And I was mainly searching for a fix for the status error I was getting. Which there is no info about that in the link you posted, however it does help with flashing my Rom through command prompt. :]
@il duce It's called "nfx speedy kingdom". I've been using the salsa builds in the development section, but I came across this Rom and it says it has everything working including Bluetooth so I wanted to test it out. Ill try using the tutorial on flashing roms without an sdcard and see if it works.
1. By the looks of it, adb is not recognizing your device... so, first and foremost you will have to setup everything properly for adb to connect
2. Even if adb recognizes the device, to the best of my knowledge, you cannot flash anything through adb, you must have confused it with fastboot. And, that too is possible only if you have engineering spl
One of the links from the thread you linked to show how to push the rom to system/data and use cmd to flash it from there, but the rom I'm trying to flash is over 300mb so it doesn't fit :/
I guess I'll try contacting the dev and see if he knows of a solution, might be that the file isn't correctly packed or signed?
edit: flashing using RA recovery it gives me the following:
Code:
E:Missing file:
system/lib/libvoAMRWBDec.so
E:Verification failed
Installation aborted
Does that mean it's the ROM that's corrupted?
Dude wtf... thats an evo rom.
Also, andy is correct 100%. Cease and desist before you bork your phone.
o_o he has it under heroc roms.
http://sprint.hero.ptyork.com/?cat=1
Edit: Sorry everyone for the questions, I just pm'd nfinitefx and he cleared out everything for me.
I have HTC Hero CDMA obviously lol
but anyways i have the latest HBOOT without S-OFF and i have a corrupt recovery i have tried restoring with the latest offical RUU with no luck as i get the 170 usb error connection error
Why not just reflash your recovery ???
#Root-Hack\Mod*Always_
""Shooter on Deck""
i try to with rom manager and i get an error
any othere method other than hboot as i dont have s-off and need a recovery to get that
omg i can not find any way to get a working recovery with out S-OFF *RAGE FACE*
evoandroidevo said:
i try to with rom manager and i get an error
any othere method other than hboot as i dont have s-off and need a recovery to get that
omg i can not find any way to get a working recovery with out S-OFF *RAGE FACE*
Click to expand...
Click to collapse
Go to my signature and click on the CWM link. Then unzip a version and place the recovery.img on the root of your SD card. Now download Busybox installer, and terminal emulator. Install busybox and after installing open terminal emulator and then enter these commands:
Code:
$ su
# flash_image recovery /sdcard/recovery.img
私のEVO 3Dから送信される。
i did all that installed busybox and all that stuff and i always get flash_image not found or something like that
EDIT:
Got it to work jsut need to go to 2.27.651.5 instead of 2.27.651.6
I seem to be having nearly this exact same problem. Maybe If I can flash a recovery to my hero I wont need to create a thread of my own asking for help.
What did you mean by "need to go to 2.27.651.5 instead of 2.27.651.6"?
I have root... or at least the "su" command in terminal gives me a #. I have placed the recovery image on the root directory of my sd just as dastin said and run the command but I am getting the flash_image not found error.
That's the RUU version.
Sent from my PG86100 using xda premium
Okay. Maybe my issue is not so similar after all.
I have stock that has been rooted. That is as far as I got. There were countless problems during the rooting process but I have achieved the # in the terminal. This means it's rooted right?
At this point I think I just need to flash a recovery and for some reason I can't install "ROM manager" as I get a "Parse error" when running the .apk. So I thought this manual method would solve my issues.
Maybe I should start my own thread. This might get complicated.
Jacob_newton said:
Okay. Maybe my issue is not so similar after all.
I have stock that has been rooted. That is as far as I got. There were countless problems during the rooting process but I have achieved the # in the terminal. This means it's rooted right?
At this point I think I just need to flash a recovery and for some reason I can't install "ROM manager" as I get a "Parse error" when running the .apk. So I thought this manual method would solve my issues.
Maybe I should start my own thread. This might get complicated.
Click to expand...
Click to collapse
Install busybox.
私のEVO 3Dから送信される。
busybox says my device is rooted.
busybox location: /system/xbin v.119.3.
I still get that same not found error.
Jacob_newton said:
busybox says my device is rooted.
busybox location: /system/xbin v.119.3.
I still get that same not found error.
Click to expand...
Click to collapse
Why not just flash the recovery ??? From terminal,hooot, or adb.
#Root-Hack\Mod*Always_
""Shooter on Deck""
If I use the command prompt and enter:
cd ...\android-sdk\platform-tools
adb shell
# flash_image
I still get "flash_image: not found" it's as if it's missing the command. It's the same error if I tell it where to get the .img from
edit: this is the exact same when I do it from terminal and i have no idea what hooot is.
Jacob_newton said:
If I use the command prompt and enter:
cd ...\android-sdk\platform-tools
adb shell
# flash_image
I still get "flash_image: not found" it's as if it's missing the command. It's the same error if I tell it where to get the .img from
edit: this is the exact same when I do it from terminal and i have no idea what hooot is.
Click to expand...
Click to collapse
Were did you place the recovery img at ??
#Root-Hack\Mod*Always_
""Shooter on Deck""
The image file is on the root directory of my sd card.
I'm not sure but it seems like the "flash_image" command just doesn't work. If I type "flash_image" and hit enter, it gives the same error as if I type "dead_bears".
dead_bears: not found
I don't think this has anything to do with my image file. I think something is wrong with the command.
Jacob_newton said:
The image file is on the root directory of my sd card.
I'm not sure but it seems like the "flash_image" command just doesn't work. If I type "flash_image" and hit enter, it gives the same error as if I type "dead_bears".
dead_bears: not found
I don't think this has anything to do with my image file. I think something is wrong with the command.
Click to expand...
Click to collapse
Let me ask you this are you trying to flash this from terminal or from adb ?? If there isn't a copy of the recovery img in your adb tools folder then trying to flash it threw adb wouldn't take because the image isn't there. Since the img is on your SD card then you should flash it threw terminal if your not trying it already. If you want to flash it threw adb then place a copy of the recovery img in your adb tools folder and then run the commands from cmd terminal VIA pc/laptop. Also have you made sure that the recovery img is named correctly ?? Also will you post your setup, as in rom,kernel,baseband/radio, and hboot. Also how did you obtain root ??? Thanks
#Root_Hack-Mod*Always\
I am using the terminal and I have tried ADB as well. Both do the exact same thing. I obtained root manually but I had so many problems that don't remember where the guide that I followed is. I named the recovery image "r.img" for ease of typing.
I don't know about rom,kernel,baseband/radio, and hboot. I flashed stock to the phone after purchasing it so that I could get it activated, so these things are likely at defaults.
I still don't think that the "flash_image: not found" error has anything to do with the image file itself.
Jacob_newton said:
I am using the terminal and I have tried ADB as well. Both do the exact same thing. I obtained root manually but I had so many problems that don't remember where the guide that I followed is. I named the recovery image "r.img" for ease of typing.
I don't know about rom,kernel,baseband/radio, and hboot. I flashed stock to the phone after purchasing it so that I could get it activated, so these things are likely at defaults.
I still don't think that the "flash_image: not found" error has anything to do with the image file itself.
I think you should ruu back to stock and reroot again. Reason why I suggest this is because of how you gained root. If something wasn't done correctly we could be at this for hours and days trying to figure this out. But before you take that route I'll send you a pm with something I would like you to try that might work.
#Root-Hack_Mod*Always\
Click to expand...
Click to collapse
Jacob_newton said:
I am using the terminal and I have tried ADB as well. Both do the exact same thing. I obtained root manually but I had so many problems that don't remember where the guide that I followed is. I named the recovery image "r.img" for ease of typing.
I don't know about rom,kernel,baseband/radio, and hboot. I flashed stock to the phone after purchasing it so that I could get it activated, so these things are likely at defaults.
I still don't think that the "flash_image: not found" error has anything to do with the image file itself.
Click to expand...
Click to collapse
Quick??? Are you able to boot up into your Rom ???
#Root-Hack_Mod*Always\
I'm not sure what you mean by that, but I decided to flash stock the other night so now I'm going to try and re-root and flash a custom ROM.
I am considering this method for re-rooting: http://forum.xda-developers.com/showthread.php?t=909258&highlight=root
Any suggestions before I get started?
What I meant by have to be on the 2.27.651.5 RUU instead of 2.27.651.6 RUU as the flash_image is not in thr 2.27.651.6 RUU so you need to be on the 5 version of stock in order to use flash_image
Sent from my Shooter using XDA
Have you recently installed a new rom?
Have you lost your SDCard storage space?
Is your SDCard size now about 200kb?
Well fear not... The answers are out there... You've just got to search for them
But if you can't find the answer... Here is the solution
The reason your SDCard is showing the wrong size is that you've flashed a rom that is not meant for the hboot on your phone.
The solution is simple really, it can be done 1 of 3 ways
But before you start you need to know what hboot you're on. Get the phone into bootloader and it will show you what hboot you're on (If you don't know how to do this by now, give up and get an iPhone lol )
1. Download ESfile Explorer from Play Store and go to settings and then root settings and give it root privileges. Once thats done go to root of phone and go to /system/etc and find a file called vold.fstab and open it with a text editor and find this line
dev_mount sdcard /mnt/sdcard 34 /devices/platform/msm_sdcc.2/mmc_host
now for 1.25 hboot you will need to change where it says 34 to 33
and for 1.28 hboot you will need to change where it says 33 to 34
Save the file once done and reboot phone and voila you should have your sdcard back if you've done it right
2. Download the files I've attached for which hboot you are on and then make sure usb debugging is enabled in settings/developer options and plug your phone into computer. Then download the ADB & FASTBOOT zip attached and open zip and drag the folder onto your desktop, open the folder up and then open the zip for your hboot and drag the vold.fstab into the ADB & FASTBOOT folder. Double click on runme.bat and you should get a command prompt window pop up. With your phone connected you will need to type this
adb remount
then
adb push vold.fstab /system/etc
then
adb reboot
Once rebooted you should have your SDCard back
3. Probably the easiest way, just download the right hboot zip and get the vold.fstab from it and put it in the rom zip you flashed at /system/etc and flash it again... Or edit the one that is already there...
Told you it was Easy
Best guide evar!
It's actually pretty good.. I only wish it had been written sooner, as it would have saved me so much effort searching... Haha
Sent from my HTC Sensation XL with Beats Audio X315e
[vertigo] said:
Have you recently installed a new rom?
Have you lost your SDCard storage space?
Is your SDCard size now about 200kb?
Well fear not... The answers are out there... You've just got to search for them
But if you can't find the answer... Here is the solution
The reason your SDCard is showing the wrong size is that you've flashed a rom that is not meant for the hboot on your phone.
The solution is simple really, it can be done 1 of 3 ways
But before you start you need to know what hboot you're on. Get the phone into bootloader and it will show you what hboot you're on (If you don't know how to do this by now, give up and get an iPhone lol )
1. Download ESfile Explorer from Play Store and go to settings and then root settings and give it root privileges. Once thats done go to root of phone and go to /system/etc and find a file called vold.fstab and open it with a text editor and find this line
dev_mount sdcard /mnt/sdcard 34 /devices/platform/msm_sdcc.2/mmc_host
now for 1.25 hboot you will need to change where it says 34 to 33
and for 1.28 hboot you will need to change where it says 33 to 34
Save the file once done and reboot phone and voila you should have your sdcard back if you've done it right
2. Download the files I've attached for which hboot you are on and then make sure usb debugging is enabled in settings/developer options and plug your phone into computer. Then download the ADB & FASTBOOT zip attached and open zip and drag the folder onto your desktop, open the folder up and then open the zip for your hboot and drag the vold.fstab into the ADB & FASTBOOT folder. Double click on runme.bat and you should get a command prompt window pop up. With your phone connected you will need to type this
adb remount
then
adb push vold.fstab /system/etc
then
adb reboot
Once rebooted you should have your SDCard back
3. Probably the easiest way, just download the right hboot zip and get the vold.fstab from it and put it in the rom zip you flashed at /system/etc and flash it again... Or edit the one that is already there...
Told you it was Easy
Click to expand...
Click to collapse
Help.
adb remount
remount failed: Success
Have you got USB debugging on in developer options on your phone?
Sent from my Galaxy Nexus using xda premium
THANX!!!
I just wanna say that posts like this one are making my life so much easier! I would have NEVER found this myself...
Guys like you are AWESOME!!!
:good:
lexusis220d said:
I just wanna say that posts like this one are making my life so much easier! I would have NEVER found this myself...
Guys like you are AWESOME!!!
:good:
Click to expand...
Click to collapse
Am saying the same:good::good:
santafeng said:
Help.
adb remount
remount failed: Success
Click to expand...
Click to collapse
hahaha wtf
but seriously, lots of thanks to OP, this guide has saved my ass several times.
You can also just put my SD card fix to your SD card and then you can flash it easy if something is wrong. Also don't edit cold.fstab. some wrong line and phone is bricked for good.
Sent from my HTC Sensation XL with Beats Audio X315e using xda premium
Hboot version not one of the ones you listed
[vertigo] said:
Have you recently installed a new rom?
Have you lost your SDCard storage space?
Is your SDCard size now about 200kb?
Well fear not... The answers are out there... You've just got to search for them
But if you can't find the answer... Here is the solution
The reason your SDCard is showing the wrong size is that you've flashed a rom that is not meant for the hboot on your phone.
The solution is simple really, it can be done 1 of 3 ways
But before you start you need to know what hboot you're on. Get the phone into bootloader and it will show you what hboot you're on (If you don't know how to do this by now, give up and get an iPhone lol )
1. Download ESfile Explorer from Play Store and go to settings and then root settings and give it root privileges. Once thats done go to root of phone and go to /system/etc and find a file called vold.fstab and open it with a text editor and find this line
dev_mount sdcard /mnt/sdcard 34 /devices/platform/msm_sdcc.2/mmc_host
now for 1.25 hboot you will need to change where it says 34 to 33
and for 1.28 hboot you will need to change where it says 33 to 34
Save the file once done and reboot phone and voila you should have your sdcard back if you've done it right
2. Download the files I've attached for which hboot you are on and then make sure usb debugging is enabled in settings/developer options and plug your phone into computer. Then download the ADB & FASTBOOT zip attached and open zip and drag the folder onto your desktop, open the folder up and then open the zip for your hboot and drag the vold.fstab into the ADB & FASTBOOT folder. Double click on runme.bat and you should get a command prompt window pop up. With your phone connected you will need to type this
adb remount
then
adb push vold.fstab /system/etc
then
adb reboot
Once rebooted you should have your SDCard back
3. Probably the easiest way, just download the right hboot zip and get the vold.fstab from it and put it in the rom zip you flashed at /system/etc and flash it again... Or edit the one that is already there...
Told you it was Easy
Click to expand...
Click to collapse
Hi, my HBoot version is 1.27.111. I tried to experiment with some of the numbers you posted and my phone won't boot at all now (stuck in swirling cyanogenmod animation). Any recommendations?
---------- Post added at 08:50 AM ---------- Previous post was at 08:29 AM ----------
chefmarc said:
Hi, my HBoot version is 1.27.111. I tried to experiment with some of the numbers you posted and my phone won't boot at all now (stuck in swirling cyanogenmod animation). Any recommendations?
Click to expand...
Click to collapse
anders3408 said:
You can also just put my SD card fix to your SD card and then you can flash it easy if something is wrong. Also don't edit cold.fstab. some wrong line and phone is bricked for good.
Sent from my HTC Sensation XL with Beats Audio X315e using xda premium
Click to expand...
Click to collapse
My phone appears to be bricked. any recommendations?
sorry
[vertigo] said:
Have you recently installed a new rom?
Have you lost your SDCard storage space?
Is your SDCard size now about 200kb?
Well fear not... The answers are out there... You've just got to search for them
But if you can't find the answer... Here is the solution
The reason your SDCard is showing the wrong size is that you've flashed a rom that is not meant for the hboot on your phone.
The solution is simple really, it can be done 1 of 3 ways
But before you start you need to know what hboot you're on. Get the phone into bootloader and it will show you what hboot you're on (If you don't know how to do this by now, give up and get an iPhone lol )
1. Download ESfile Explorer from Play Store and go to settings and then root settings and give it root privileges. Once thats done go to root of phone and go to /system/etc and find a file called vold.fstab and open it with a text editor and find this line
dev_mount sdcard /mnt/sdcard 34 /devices/platform/msm_sdcc.2/mmc_host
now for 1.25 hboot you will need to change where it says 34 to 33
and for 1.28 hboot you will need to change where it says 33 to 34
Save the file once done and reboot phone and voila you should have your sdcard back if you've done it right
2. Download the files I've attached for which hboot you are on and then make sure usb debugging is enabled in settings/developer options and plug your phone into computer. Then download the ADB & FASTBOOT zip attached and open zip and drag the folder onto your desktop, open the folder up and then open the zip for your hboot and drag the vold.fstab into the ADB & FASTBOOT folder. Double click on runme.bat and you should get a command prompt window pop up. With your phone connected you will need to type this
adb remount
then
adb push vold.fstab /system/etc
then
adb reboot
Once rebooted you should have your SDCard back
3. Probably the easiest way, just download the right hboot zip and get the vold.fstab from it and put it in the rom zip you flashed at /system/etc and flash it again... Or edit the one that is already there...
Told you it was Easy
Click to expand...
Click to collapse
sorry man I tried
but it doen't work(
jeanpean said:
sorry man I tried
but it doen't work(
Click to expand...
Click to collapse
This was made nearly a year ago, there will be more up to date guides now...
help
[vertigo] said:
This was made nearly a year ago, there will be more up to date guides now...
Click to expand...
Click to collapse
I tried everything but no solution...relocked.s-on.unroot..I see constantly the same message..error 155.....
Thanks
And moor thanks
Easiest way 2.nd