My phone is stuck on the white splash screen that displays the HTC logo.
It happened because I’ve been trying to get an app working that requires me not to be rooted. I had tried a few of the “ hide your root” apps from the Market but none worked.
I eventually found a way to get it working by going into system/xbin and disabling all the su permissions.
However after disabling the su permissions I found I was unable to allow the permissions again when attempting to reverse the same procedure.
This morning I tried doing an ARHD Superwipe. I thought this would be similar to doing a factory reset (didn’t realise 4EXT had it’s own factory reset).
After doing Superwipe 4EXT told me I was now ready to flash my ROM. I still haven’t flashed the ROM, instead the phone attempted to boot up but got stuck on the white / HTC screen.
Is it normal procedure that Superwipe will completely wipe the ROM off my phone – hence the reason why it’s now stuck like this (until I flash the ROM again)?
I’m at work right now and don’t currently have the ROM on my SD card.
If I reflash the ROM when I get home will that fix everything?
I’m worried that I might have messed my phone up disabling these su permissions?
I can still get into recovery OK what it matters.
Please help if you can as I am panicking a bit here.
Kurdt Kobain said:
My phone is stuck on the white splash screen that displays the HTC logo.
It happened because I’ve been trying to get an app working that requires me not to be rooted. I had tried a few of the “ hide your root” apps from the Market but none worked.
I eventually found a way to get it working by going into system/xbin and disabling all the su permissions.
However after disabling the su permissions I found I was unable to allow the permissions again when attempting to reverse the same procedure.
This morning I tried doing an ARHD Superwipe. I thought this would be similar to doing a factory reset (didn’t realise 4EXT had it’s own factory reset).
After doing Superwipe 4EXT told me I was now ready to flash my ROM. I still haven’t flashed the ROM, instead the phone attempted to boot up but got stuck on the white / HTC screen.
Is it normal procedure that Superwipe will completely wipe the ROM off my phone – hence the reason why it’s now stuck like this (until I flash the ROM again)?
I’m at work right now and don’t currently have the ROM on my SD card.
If I reflash the ROM when I get home will that fix everything?
I’m worried that I might have messed my phone up disabling these su permissions?
I can still get into recovery OK what it matters.
Please help if you can as I am panicking a bit here.
Click to expand...
Click to collapse
Hi,
Yes,Superwipe will clear your phone.
This includes the ROM.
Re-flash the ROM,and this will return your ROM,and SU.
Kurdt Kobain said:
My phone is stuck on the white splash screen that displays the HTC logo.
It happened because I’ve been trying to get an app working that requires me not to be rooted. I had tried a few of the “ hide your root” apps from the Market but none worked.
I eventually found a way to get it working by going into system/xbin and disabling all the su permissions.
However after disabling the su permissions I found I was unable to allow the permissions again when attempting to reverse the same procedure.
This morning I tried doing an ARHD Superwipe. I thought this would be similar to doing a factory reset (didn’t realise 4EXT had it’s own factory reset).
After doing Superwipe 4EXT told me I was now ready to flash my ROM. I still haven’t flashed the ROM, instead the phone attempted to boot up but got stuck on the white / HTC screen.
Is it normal procedure that Superwipe will completely wipe the ROM off my phone – hence the reason why it’s now stuck like this (until I flash the ROM again)?
I’m at work right now and don’t currently have the ROM on my SD card.
If I reflash the ROM when I get home will that fix everything?
I’m worried that I might have messed my phone up disabling these su permissions?
I can still get into recovery OK what it matters.
Please help if you can as I am panicking a bit here.
Click to expand...
Click to collapse
I had a similar issue once when i removed superuser accidentally. I flashed a recovery and it fixed the problem and returned me to root. Did you do a backup?
Sent from my HTC Sensation using xda premium
evetsno1 said:
I had a similar issue once when i removed superuser accidentally. I flashed a recovery and it fixed the problem and returned me to root. Did you do a backup?
Sent from my HTC Sensation using xda premium
Click to expand...
Click to collapse
Cheers guys I was hoping it would be as simple as that. I just had a bit of a panic this morning I guess! I've never used Superwipe with previous Androids.
Yeah I did make a backup of my stock ROM before flashing.
So in future is there a more easier way to restore the permisions in su?
Kurdt Kobain said:
Cheers guys I was hoping it would be as simple as that. I just had a bit of a panic this morning I guess! I've never used Superwipe with previous Androids.
Yeah I did make a backup of my stock ROM before flashing.
So in future is there a more easier way to restore the permisions in su?
Click to expand...
Click to collapse
4ext fix permissions in tools menue I believe. You can also hold down on the apk till the menue comes up then go to properties and manually fix them if you know what to set them to.
Sent from my HTC Sensation using xda premium
evetsno1 said:
4ext fix permissions in tools menue I believe. You can also hold down on the apk till the menue comes up then go to properties and manually fix them if you know what to set them to.
Sent from my HTC Sensation using xda premium
Click to expand...
Click to collapse
I found that when I first went to disable them the various permission boxes all showed up no problem but when I went back to restore them the boxes would no longer display anymore.
That's good to know that I should be able to do it via 4EXT. Would also like to know if its possible via the phone itself too as my gf's Android doesn't have 4EXT.
Would it work if I copied the system/xbin/su file before disabling them, maybe store it on my PC, and copy it back again afterwards when I want the root reactivating? I'm thinking no because r/rw is turned off right?
Or if I just reflashed the root again from the PC to phone. Would that work?
Kurdt Kobain said:
I found that when I first went to disable them the various permission boxes all showed up no problem but when I went back to restore them the boxes would no longer display anymore.
That's good to know that I should be able to do it via 4EXT. Would also like to know if its possible via the phone itself too as my gf's Android doesn't have 4EXT.
Would it work if I copied the system/xbin/su file before disabling them, maybe store it on my PC, and copy it back again afterwards when I want the root reactivating? I'm thinking no because r/rw is turned off right?
Or if I just reflashed the root again from the PC to phone. Would that work?
Click to expand...
Click to collapse
I dont think you can get root back by fixing permissions. It is my understanding that root is a two part system. First is a binary and second is a program that interacts with the binary such as superuser or supersu. If you remove either part you lose root.
When I lost root I only lost it because I lost supersu. After losing supersu oil checked for root with root checker and it was lost. I tried replacing it but it didnt work. I had to flash a recovery that had root to get it back or re-root my phone. That is about the extent of my knowledge of it.
Sent from my HTC Sensation 4G using xda premium
Related
Does anyone have the htc phone.apk??? i accidentally and very stupidly deleted mines from my system applications using root explorer. i cant make calls without it.
chrisw491 said:
Does anyone have the htc phone.apk??? i accidentally and very stupidly deleted mines from my system applications using root explorer. i cant make calls without it.
Click to expand...
Click to collapse
if you have a custom rom, either flash the Nandroid back up or else Flash a new rom or else you can strip a rom of the Phone.apk file
ok i have a MAJOR problem. im kind of a noob at this stuff so im still learning. i was messing in my system files trying different phone.apk. i think i may have deleted something essential. when i turn my phone on it doesnt get past the boot animation. my phone was rooted with unrevoked 3. but everytime i try to install a new rom using clock work recovery, it gets to the part where it "opens update pakage" and just stops and goes back to the first menu screen of clockwork. i dont have a nandroid backup either so i cant even restore.
chrisw491 said:
ok i have a MAJOR problem. im kind of a noob at this stuff so im still learning. i was messing in my system files trying different phone.apk. i think i may have deleted something essential. when i turn my phone on it doesnt get past the boot animation. my phone was rooted with unrevoked 3. but everytime i try to install a new rom using clock work recovery, it gets to the part where it "opens update pakage" and just stops and goes back to the first menu screen of clockwork. i dont have a nandroid backup either so i cant even restore.
Click to expand...
Click to collapse
try wiping the phone in the recovery, wipe everything then install a new rom, sometimes not wiping screws up the installation
Diamond_dawg said:
try wiping the phone in the recovery, wipe everything then install a new rom, sometimes not wiping screws up the installation
Click to expand...
Click to collapse
yea i tried wiping the cache and wipe data/factory reset but I still get the same results. im willing to try anything.
chrisw491 said:
yea i tried wiping the cache and wipe data/factory reset but I still get the same results. im willing to try anything.
Click to expand...
Click to collapse
try posting this in the Evo forum, they will help you better
Hi,
The release of the stable CM7.1 really encouraged me to finally S-OFF my phone and install it. I used Revolutionary 0.4pre4, and installed CWM 5.0.20. I wiped everything (data, system, cache, dalvik, you name it), and installed the CM7.1 update zip and right afterwards the new Google apps zip. Eventually, I used Fix Permissions, and rebooted.
I was quite happy, until I saw the com.android.phone FC message. It just showed the same message over and over. I updated my radio to the latest version, to no avail. I tried reformatting, re-wiping, reinstalling quite a few times, and I even tried 3 different sim cards. I finally decided to go back to RUU (kept S-OFF), and didn't get any FCs.
I'm really frustrated, since it is my first Android phone, and I really believe I tried everything already.
Thanks in advance.
I got no problem at all until now.
Another thing I've discovered is when I get these FCs, sometimes if I enable the bluetooth, the phone suddenly discovers the network and the FCs stop. That's just very odd, to me.
I really hope that's not a problem with my phone (especially since it does work properly with RUU).
foouser said:
Hi,
The release of the stable CM7.1 really encouraged me to finally S-OFF my phone and install it. I used Revolutionary 0.4pre4, and installed CWM 5.0.20. I wiped everything (data, system, cache, dalvik, you name it), and installed the CM7.1 update zip and right afterwards the new Google apps zip. Eventually, I used Fix Permissions, and rebooted.
I was quite happy, until I saw the com.android.phone FC message. It just showed the same message over and over. I updated my radio to the latest version, to no avail. I tried reformatting, re-wiping, reinstalling quite a few times, and I even tried 3 different sim cards. I finally decided to go back to RUU (kept S-OFF), and didn't get any FCs.
I'm really frustrated, since it is my first Android phone, and I really believe I tried everything already.
Thanks in advance.
Click to expand...
Click to collapse
Nothing has ever broken my phone quite as much as when I have done the 'fix permissions' thing. Totally screwed my phone and was FC city. I've never done it since, and never had any problems since. Try going back over your steps and leave out the fix permissions part!
I recently had a quick go with CM7 nightlies and had no issues. This included the last nightly before it became stable which was very close to the stable version.
wnp_79 said:
Nothing has ever broken my phone quite as much as when I have done the 'fix permissions' thing. Totally screwed my phone and was FC city. I've never done it since, and never had any problems since. Try going back over your steps and leave out the fix permissions part!
I recently had a quick go with CM7 nightlies and had no issues. This included the last nightly before it became stable which was very close to the stable version.
Click to expand...
Click to collapse
Tried doing the same process without fixing permissions, twice already, and I still get the same problem.
have you tried this?
http://forum.xda-developers.com/showpost.php?p=18309360&postcount=9
Helped with the market issue, but not yet with the com.android.phone FC...
foouser said:
Helped with the market issue, but not yet with the com.android.phone FC...
Click to expand...
Click to collapse
Odd. Here is how I did mine, step-by-step. (Do a NANDroid backup before this, and copy it to your PC/Mac.)
1. Install latest 4EXTRecovery from here: http://forum.xda-developers.com/showthread.php?t=1130004
2. Use this to format all partitions to EXT4. (Not sure if you are using EXT3, not sure if it matters, just saying I'm on EXT4 formatting with no issues.)
3. Do the full wipe & manual format routine (including boot) again just in case!
4. Flashed CM7.
5. Flashed Gapps.
6. Flashed Tiamat kernel (1.1.4)
7. Reboot.
I'm used the same radio as in my sig but also doubt that matters. Not sure what else to suggest. Try downloading the ROM again, and compare the MD5 of your two downloads.
Wow, I believe I'm in some big trouble now. I decided to try and get my phone replaced in the store since I just recently bought it. I used this guide: http://forum.xda-developers.com/showpost.php?p=17481836&postcount=2 to get back to S-ON, but when I tried to flash back the RUU, I get a CUSTOMER ID ERROR and the flash fails.
I've tried two RUUs: RUU_Saga_HTC_Europe_1.47.401.4_Radio_20.28I.30.085AU_3805.06.02.03_M_release_199410_signed
RUU_Saga_hTC_Asia_WWE_1.48.707.1_Radio_20.28I.30.085AU_3805.06.02.03_M_release_199476_signed
But they both end up the same way. I'm now stuck on the HBOOT screen with S-ON and a big purple security warning (I guess since CM7 is still on the /system partition).
Any help?
Try solution 2 of this guide http://forum.xda-developers.com/showthread.php?t=1284196
but replace the mmc....
With
mmcblk0p25
this will format your system partition,
maybe also data could be formatted by replacing mmc... with mmcblk0p26,
after that run the ruu again.
Swyped from my Desire S
Tectas said:
Try solution 2 of this guide http://forum.xda-developers.com/showthread.php?t=1284196
but replace the mmc....
With
mmcblk0p25
this will format your system partition,
maybe also data could be formatted by replacing mmc... with mmcblk0p26,
after that run the ruu again.
Swyped from my Desire S
Click to expand...
Click to collapse
I don't really have access to recovery (it just gets me back to fastboot), let alone Android, so I don't see how I can follow this guide (maybe I misunderstood)...
I have FC with Market. Everytime i try to acces it.
foouser said:
I don't really have access to recovery (it just gets me back to fastboot), let alone Android, so I don't see how I can follow this guide (maybe I misunderstood)...
Click to expand...
Click to collapse
Don't mind the recovery step, just do the commands within adb shell
Swyped from my Desire S
mihaibuda said:
I have FC with Market. Everytime i try to acces it.
Click to expand...
Click to collapse
Have you tried wiping cache and
dalvik cache?
I also had fc after an update, this solved it for me.
If you're using cyanogen, try changing the language to English us, this solved it for some users.
Swyped from my Desire S
Never mind, I actually created a goldcard in order to bypass the CUSTOMER ID error and flashed my phone back to original and S-ON. Thanks anyways.
Just as a note to everyone, you should really go about getting back to S-ON via this way: Flash any RUU, get the original HBOOT image from that RUU (you can find it in your temp folder while flashing the RUU), and then just downgrade the HBOOT using fastboot. Easier than going through ENG HBOOT, and allows you to avoid these kind of problems (CID errors).
The problem is that you restored "DIALER STORAGE" via titanium backup. Reflash ROM, and don't restore this. It'll work, FOR SURE.
foouser said:
Never mind, I actually created a goldcard in order to bypass the CUSTOMER ID error and flashed my phone back to original and S-ON. Thanks anyways.
Just as a note to everyone, you should really go about getting back to S-ON via this way: Flash any RUU, get the original HBOOT image from that RUU (you can find it in your temp folder while flashing the RUU), and then just downgrade the HBOOT using fastboot. Easier than going through ENG HBOOT, and allows you to avoid these kind of problems (CID errors).
Click to expand...
Click to collapse
Can you please post the thread that contains the Gold Card creation process (if there was one) so that I can add it to the INDEX.
As no doubt this will be useful to others...
ty
ben_pyett said:
Can you please post the thread that contains the Gold Card creation process (if there was one) so that I can add it to the INDEX.
As no doubt this will be useful to others...
ty
Click to expand...
Click to collapse
Sure, it's really the same process for all HTC phones and works even on the newest models (Sensation generation). Thanks a lot to EFI from AlphaRev who actually pointed me in the right direction.
I used this guide: http://theunlockr.com/2010/03/10/how-to-create-a-goldcard/
I'm using Windows 7 x64 and when I inserted the card after modifying it, Windows required me to format it (as opposed to what's written in the above guide), but it still worked. Also, since my phone was stuck on HBOOT I had to use another Android phone to get the SD's CID (I used a friend's SGS, and the SD slot to query is mmc2 on it).
shrome99 said:
The problem is that you restored "DIALER STORAGE" via titanium backup. Reflash ROM, and don't restore this. It'll work, FOR SURE.
Click to expand...
Click to collapse
Well, I actually didn't use Titanium Backup at all, so nope.
Hey guys,
This is my very first post, just to let you all know, so please have some patience! Thanks!
Anyway, so I have a Nexus S 3G (Canada) and I have rooted it, unrooted it, installed roms and everything. I works...for the most part. It's giving me all sorts of different little errors and what not. So I was wondering, how can I COMPLETLY start ALL OVER, as in, factory new, like when you buy a new phone (without the carrier stuff). I wanted to start fresh, fresh out-of-the-oven kind of start, do you understand what I mean? FACTORY FRESH. Thank you all so much in advance!
well download your phone's stock rom and of course unroot it.Regarding the stock bloatware you can modify the custom rom by going in system/app and deleting the apps you dont want to be installed
[email protected] said:
well download your phone's stock rom and of course unroot it.Regarding the stock bloatware you can modify the custom rom by going in system/app and deleting the apps you dont want to be installed
Click to expand...
Click to collapse
Thanks for the reply, I've already done that, and I'm still getting errors and other weird things, like not going out of airplane mode, failing to download the OTA 2.3.6 Update (I'm on stock 2.3.1 unrooted, I think), and I don't know if this is normal, but ClockworkMod Recovery is still there. Am I still rooted or something? Plus, when I try to flash a restore, from let's say Gingerbread 2.3.6 Stock, it says MD5 mismatch! How about if it's an ICS AOSP Build, it gives me the normal white Google logo like normal, but then just stays stuck there.
Is the anyway to erase EVERYTHING and start over like NOTHING was ever done to the device? Like when they are first distributing the the device and no one has ever touched it? Is there anyway to do just that?
There is a difference between being "rooted" and using a rooted ROM. You could be using a non-rooted ROM, and your phone can still be "rooted". The first step in rooting a phone is changing SECURITY-ON to SECURITY-OFF. If you REALLY want to go back to when you first got the device, you will need to find a way to turn SECURITY from OFF to ON. When it is off, you are able to access the bootloader, in turn allowing you to install a recovery to install a ROM with rooted permissions. I think the best way to go back to stock would be for you to first download the latest OTA update for your device, do a FULL WIPE of everything on your phone thru recovery (data, system, cache, dalvik cache). Then installing the latest OTA. I do not think however, that this is how you turn your device S-ON.
I hope I've been of some help.
Sent from my Incredible 2 using xda premium
lodxcol said:
There is a difference between being "rooted" and using a rooted ROM. You could be using a non-rooted ROM, and your phone can still be "rooted". The first step in rooting a phone is changing SECURITY-ON to SECURITY-OFF. If you REALLY want to go back to when you first got the device, you will need to find a way to turn SECURITY from OFF to ON. When it is off, you are able to access the bootloader, in turn allowing you to install a recovery to install a ROM with rooted permissions. I think the best way to go back to stock would be for you to first download the latest OTA update for your device, do a FULL WIPE of everything on your phone thru recovery (data, system, cache, dalvik cache). Then installing the latest OTA. I do not think however, that this is how you turn your device S-ON.
I hope I've been of some help.
Sent from my Incredible 2 using xda premium
Click to expand...
Click to collapse
Thanks for your excellent reply, but I have also already done that, EXACTLY that, multiple times too. Dalvik, battery stats, factory reset/delete all user data, wipe cache partition and fix permissions. What else is there left to do?
Thank you all so very much!!!!
I have fixed my Nexus S!!!
HeroKhar said:
I have fixed my Nexus S!!!
Click to expand...
Click to collapse
how did you fix it?
lodxcol said:
how did you fix it?
Click to expand...
Click to collapse
I reinstalled the newest update with the vanilla recovery
Sent from my Xoom using XDA Premium HD app
I rooted my Samsung Galaxy Tab Plus 7.0 tablet with the tutorial from this site:
http://forum.xda-developers.com/showthread.php?p=24736900
It worked just fine for a couple days, then today I powered up the tablet and when I unlock it, it shows a problem loading all widgets, and within a few seconds the screen goes black, then proceeds back to the unlock screen. I unlock it again and this keeps repeating.
I didn't hack anything else, just installed superuser and a couple of other root apps. Really I haven't done anything else to cause this.
I don't even have enough time to go into settings and do a factory reset.
Any ideas? Perhaps in recovery?
EDIT - I did a factory reset in recovery. Is this going to fix it back to normal? I probably won't root ever again.
It probably has no affect, but what root apps did you install?
superuser, busybox, adfree, rom toolbox (which couldnt even detect my root but I never tried anything else)... those I can remember...
Did you install CWM and do a backup?
Im not sure what that acronym is for. I am new to all this. I followed the simple instructions in that tutorial and that was it.
It seems the issue is gone since my factory reset.
I am not sure if the root is still there however.
If there are extra steps to be done after a root it would help to have them with the tutorial....
A factory reset will remove root from your phone. Rooting it in and of itself should cause no issues like you are having it has to be something you installed and I would suspect ROM Toolbox. I'm not sure this app supports teh GTab+ or even has any useful purpose for us as we have no real ROMs to flash. It also contains a ROM Manager and if its the same one by Koush then it will defintely screw up our tablets.
repo97 said:
I rooted my Samsung Galaxy Tab Plus 7.0 tablet with the tutorial from this site:
http://forum.xda-developers.com/showthread.php?p=24736900
It worked just fine for a couple days, then today I powered up the tablet and when I unlock it, it shows a problem loading all widgets, and within a few seconds the screen goes black, then proceeds back to the unlock screen. I unlock it again and this keeps repeating.
I didn't hack anything else, just installed superuser and a couple of other root apps. Really I haven't done anything else to cause this.
I don't even have enough time to go into settings and do a factory reset.
Any ideas? Perhaps in recovery?
EDIT - I did a factory reset in recovery. Is this going to fix it back to normal? I probably won't root ever again.
Click to expand...
Click to collapse
I have done this ROOT like a million times (i'm a flash junkie)... testing the CM9 roms and back to stock again.. never had an issue with ROOTing the stock ROMs..
Suggest you download the latest firmware for your device and flash using ODIN and factory reset. Repeat the flash & factory reset a few times
Maybe you have the wrong clue of what your problem is. To root your tab is just a matter of put a binary called "su" on a directory on your PATH, usually /usr/bin and set it with proper permissions. This binary gives you superuser powers, but there's nothing on it or at least in the process that installs it that makes it interfere in anything without being called.
So accidentally you did anything that went wrong or any of programs that requires root did.
Sent from my GT-P6210
kzoodroid said:
A factory reset will remove root from your phone. Rooting it in and of itself should cause no issues like you are having it has to be something you installed and I would suspect ROM Toolbox. I'm not sure this app supports teh GTab+ or even has any useful purpose for us as we have no real ROMs to flash. It also contains a ROM Manager and if its the same one by Koush then it will defintely screw up our tablets.
Click to expand...
Click to collapse
Sorry for taking a bit to reply, havent had the chance to get much PC stuff done lately.
Aaah so you think it was the culprit.... its wierd because when I tried to run the rom toolbox it shown that my tab was not rooted.
Then the problems started... as in my tab was rebooting itself and was stuck in a loop.
I did do the factory reset and then used a root checker and noticed it shown as no root access.
I have read that a factory reset does not remove root... are you sure it does completely?
I'd hate to go through another reset as I have set everything up again.
The only bug I have noticed so far with my tab is that the odd app (so far market and dolphin browser) at times I am unable to go back a page... the page just kind of flashes and stays on that page but does not go back. I end up having to restart the app.
Should I reflash with latest firmware and do a factory reset?
If so... I found this site, shall I use these instructions and firmware?
http://www.androidauthority.com/galaxy-tab-7-0-plus-p6200-update-ddkl2-honeycomb-3-2-firmware-45993/
Hey guys, so I'm worried I might have bricked my One S, or at least messed it up beyond what I can personally repair.
Basically what happened was that I was trying to install the Auto brightness patch (http://forum.xda-developers.com/showthread.php?t=1638559) onto my One S, because I wasn't happy with the batterly life. Stupidly, I tried to install it without checking accurately for matching RUU version numbers. I thought the Virtuous Ville v1.40 ROM I was running had a 1.78 base, but it has a 1.70 one. Still, I figured that in case anything went wrong, I would just make a nandroid backup and restore. Unfortunately this did not work out so well.
My phone got stuck in a boot loop, so I reset it. When I tried to restore my Nandroid backup, I got an error saying "can't mount /sdcard" or something of the sort. Other Nandroid backups had always worked.
I think before entering recovery, I selected "factory reset" on the HBOOT menu instead of "recovery" by accident. It still loaded into the recovery though, so I wasn't sure what I had actually done. If I did press the wrong thing don't know if that somehow messed up the recovery's access to the SD card.
So now I don't know what to do. I don't mind having to reinstall everything and losing my data, I just want my phone to work. Everytime I try to turn it on it gets stuck in a boot loop, and there doesn't seem to be any way I can access my storage for either nandroid nor installing any roms.
Any help would be immensely appreciated.
Sorry guys, false alarm.
For anyone that's curious, all I had to do to fix my problem was simply reflash CWM recovery(interim touch). Not sure what went wrong, but I think that was that fixed it. Unfortunately I lost all my data and customizations(not sure ifbecause of the factory reset in HBOOT or because I also accidentally clicked on "clear storage" >_>) but since i just got the phone a few days ago and have been installing ROMs very frequently, it's no biggie.
Can a mod close this?
napilopez said:
Sorry guys, false alarm.
For anyone that's curious, all I had to do to fix my problem was simply reflash CWM recovery(interim touch). Not sure what went wrong, but I think that was that fixed it. Unfortunately I lost all my data and customizations(not sure ifbecause of the factory reset in HBOOT or because I also accidentally clicked on "clear storage" >_>) but since i just got the phone a few days ago and have been installing ROMs very frequently, it's no biggie.
Can a mod close this?
Click to expand...
Click to collapse
You shouldn't be using the interim release of the touch recovery anymore.
There is an official release now: Official Touch Recovery
And yes, you lost everything because you did a factory reset... it's all in the name you know... 'factory reset' - does it ring any bells?
I'm having the same problem here. I've tried to fastboot flash alternate recoveries and keep getting the sdcard error. I was trying to install cm9 and now phone won't boot and no sdcard!
Any help would be GREATLY appreciated........
Try this: http://forum.xda-developers.com/showthread.php?t=1630459
Sent from my HTC One S using Tapatalk 2