Since yesterday I have the strange problem. Searched the forum but can't find any solution thats right for me.
I testet a sense 3.5 rom (Insertcoin) and then wanted to restore an backup. It went wrong. So I wanted to wipe everything and flash my old rom new.
No I get the error messege when I want to wipe data/factory reset?
What could I do to solve this problem?
I also tried superwipe from the revolution rom, but this doesn't solve my problem :-(
I just want to wipe everything and then flash a new fresh rom.
What I tried so far:
Installed the original Vodafone RUU. Then installed clockworkmod (latest version) then installed root.
Error still occurs.
I got the same problem!
GrossmeisterB said:
I got the same problem!
Click to expand...
Click to collapse
This just happened to me after flashing stock RUU again and installing CWM and CM7.
Should i worry or is it irrelevant?
Also Now in the bootloader it says
LOCKED but s-off on hboot 1.18 should i run Revolutionary again? I tried but it would just close a second after. I did manage to flash CM7
format volume problem
fr0zenblood75 said:
This just happened to me after flashing stock RUU again and installing CWM and CM7.
Should i worry or is it irrelevant?
Also Now in the bootloader it says
LOCKED but s-off on hboot 1.18 should i run Revolutionary again? I tried but it would just close a second after. I did manage to flash CM7
Click to expand...
Click to collapse
ive got the same problem also tried super wipe but didnt work try formatting the sd card but didnt work.... please help... could this cause the phone to power off and reboot constantly.....
problem format volume
any news on how to address this problem
Related
My ChaCha is stuck at HTC boot screen. i have done factory reset, battery pulls and installing ROMS to no avail. I keep getting errors while trying to install the stock ROMS. Am I going about it the right way, trying to find ROMs or Is there something else I can do to solve this problem.
dagbula said:
My ChaCha is stuck at HTC boot screen. i have done factory reset, battery pulls and installing ROMS to no avail. I keep getting errors while trying to install the stock ROMS. Am I going about it the right way, trying to find ROMs or Is there something else I can do to solve this problem.
Click to expand...
Click to collapse
do you have root? and have recovery? if yes then go there and delete dalvik, delete cache and try factory reset
petulikt said:
do you have root? and have recovery? if yes then go there and delete dalvik, delete cache and try factory reset
Click to expand...
Click to collapse
Yes, I have root and can boot to recovery. I already tried clearing the dalvik cache and factory reset. i also restored from a Nandroid backup, all this to no avail. The boot loop problem still persist.
i also tried flashing ROM but all the ROMs i got gives one error or the other. I really need help.
dagbula said:
i also tried flashing ROM but all the ROMs i got gives one error or the other. I really need help.
Click to expand...
Click to collapse
Have you tried flashing an official RUU 1.33 with a goldcard?
Did you find a solution ?
i am having the same problem
ZaSa 4 chacha ROM saved me from the trouble check here http://forum.xda-developers.com/showthread.php?t=1343636
I was running the ruu 1.7x with PA because I had a soft brick a few weeks ago, just last night I tried flashing King Cobra in TWRP. Upon rebooting it gave me trouble but I eventually got the phone to boot up all the way. Everything worked except and I couldn't call or text but I can receive them. I thought maybe installing the latest update would solve the problem but I'm still having the same issue. EVERYTHING got wiped no backs up no nothing, am I screwed?
Sent from my HTC One X using xda app-developers app
Check your apn settings and make sure your using the correct settings for your carrier.
Grnfinger said:
Check your apn settings and make sure your using the correct settings for your carrier.
Click to expand...
Click to collapse
I did that when I was running KC and now on the stock software, I thought it was because I was on 1.7x and flashed KC cause I didn't have this problem with PA, so I did the update ruu tool to 2.20 and the problem still persist :/
WOOOWWW.
I am the biggest herp that ever derped. I did not flash the FC.zip fix provided in the King Cobra thread instead I updated with the RUU tool and the problem still persists. So I suppose I have to wait for the amazing minds of XDA to figure out a way to root the HOX on 2.20 before I can root/unlock to flash this silly zip. Ohhhh woe is me.
droidnamedjakke said:
I am the biggest herp that ever derped. I did not flash the FC.zip fix provided in the King Cobra thread instead I updated with the RUU tool and the problem still persists. So I suppose I have to wait for the amazing minds of XDA to figure out a way to root the HOX on 2.20 before I can root/unlock to flash this silly zip. Ohhhh woe is me.
Click to expand...
Click to collapse
Since you already unlocked the phone with HTC dev unless you changed your cid before the ruu you can unlock again with the same token and install twrp and flash a rooted rom.
You will just need to flash the boot.img from fastboot before the rom
Sent from my HTC One XL using Forum Runner
droidnamedjakke said:
I am the biggest herp that ever derped. I did not flash the FC.zip fix provided in the King Cobra thread instead I updated with the RUU tool and the problem still persists. So I suppose I have to wait for the amazing minds of XDA to figure out a way to root the HOX on 2.20 before I can root/unlock to flash this silly zip. Ohhhh woe is me.
Click to expand...
Click to collapse
As long as you left your phone SuperCID, then you can reunlock and re-root.
I unlocked it once again and flashed KC back, but the .zip fix he provided isn't working. Any ideas fellas?
droidnamedjakke said:
I unlocked it once again and flashed KC back, but the .zip fix he provided isn't working. Any ideas fellas?
Click to expand...
Click to collapse
Try going in to recovery and clearing everything (cache, dalvik, factory reset, system) and reflash. Keep in mind if you are on 2.20, you have to flash the boot.img manually.
Butters619 said:
Try going in to recovery and clearing everything (cache, dalvik, factory reset, system) and reflash. Keep in mind if you are on 2.20, you have to flash the boot.img manually.
Click to expand...
Click to collapse
It didn't solve the problem I still can't flash the .zip fix nor is the issue gone. Should I try flashing a different Rom and see if that takes care of it?
flash newest twrp 2.2.2.0 in fastboot. also do a "fastboot erase cache" then "fastboot flash boot boot.img" using the boot.img from CleanROM 4.5. then wipe cache,dalvik,data,system,etc. even flash external after backing up everything. then mount usb copy CleanROM 4.5 to storage. then install selecting full wipe in aroma. then install cleanmods in the created storage folder. that will be the safest method to make sure your starting clean.
DvineLord said:
flash newest twrp 2.2.2.0 in fastboot. also do a "fastboot erase cache" then "fastboot flash boot boot.img" using the boot.img from CleanROM 4.5. then wipe cache,dalvik,data,system,etc. even flash external after backing up everything. then mount usb copy CleanROM 4.5 to storage. then install selecting full wipe in aroma. then install cleanmods in the created storage folder. that will be the safest method to make sure your starting clean.
Click to expand...
Click to collapse
I'll try this when I get home from work at 2:30, thanks for giving the advice. But what do you mean "even flash external"?
DvineLord said:
flash newest twrp 2.2.2.0 in fastboot. also do a "fastboot erase cache" then "fastboot flash boot boot.img" using the boot.img from CleanROM 4.5. then wipe cache,dalvik,data,system,etc. even flash external after backing up everything. then mount usb copy CleanROM 4.5 to storage. then install selecting full wipe in aroma. then install cleanmods in the created storage folder. that will be the safest method to make sure your starting clean.
Click to expand...
Click to collapse
I did a full wipe of everything and installed CleanROM but to no avail I'm still getting the error as listed before. I don't understand everything was wiped for my HOX why is it still doing this?
Hey guys, I have a problem with my camera on every aosp ROM I've tried. I don't know what's wrong with it, on opening the camera app it gives me "camera error: can't connect to the camera" I've tried reflashing the roms and everything but to no avail, maybe someone can help me? Thanks in advance!
If you are s-on, did you flash boot.img using fastboot?
Did you do a factory reset (in recovery, not in bootloader) and wipe cache before installing each new custom ROM?
redpoint73 said:
If you are s-on, did you flash boot.img using fastboot?
Did you do a factory reset (in recovery, not in bootloader) and wipe cache before installing each new custom ROM?
Click to expand...
Click to collapse
I'm s-off so I don't need to flash the boot.img and yes I've tried full wipes and wiping the caches but nothing seems to work, I'm going to restore a backup of viper and see if it's working on that ROM.
Edit: No go on viper either, I'm not sure what's happening.
Maybe RUU and start over again?
If that doesn't fix it, might be a hardware failure.
redpoint73 said:
Maybe RUU and start over again?
If that doesn't fix it, might be a hardware failure.
Click to expand...
Click to collapse
Yeah I'm gonna try to RUU today and see how it goes.
Hello all !
I have an issue after trying to change ROM : I had "icon stretching" issue with Source, something apparently no one had seen before. I wanted to switch to Maximus, so I flashed it apparently with no problems. But then the phone only booted to Recovery (TWRP)...
So I tried to flash firmware again, the one given in tuto for Maximus but same problem.
And this is when it got tricky, not only I couldn't boot to Android, but I couldn't mount USB either, the option just disappeared ! Along with issue to mount "/cache" apparently. I tried factory reset, then full wipe, no result.
I tried a more recent version of TWRP than the one given with Maximus' tutorial, with it I have the option to mount USB but only for a 48 MB space ! Again, factory reset and full wipe don't help.
I'm not too worried since I can access bootloader and Recovery fine but I feel out of options... I flashed 2.16 firmware like a dozen times (is it any point in doing that ?), I wonder just how I can get a recovery that can mount USB, or a stock ROM to start fresh.
Anybody to help me ? Thanks in advance !
stick on TWRP 2.3.3.0 which (iirc) is the last one that allows you to mount storage. slap another rom across, flash, fastboot boot.img, get the rom up and running and then consider changing recoveries.
Thanks for your reply
I flashed this version but I can only mount a 48MB storage . I didn't reflash the firmware, should I downgrade to 2.15 ?
i've got no experience with 2.16 firmware so i can't really help you as far as it goes with the best recovery on that... all i can say is the last version of TWRP that allows sd mount is 2.3.3.0. have you tried the latest CWM that works with kitkat roms? that might be worth a shot.
djiock said:
Thanks for your reply
I flashed this version but I can only mount a 48MB storage . I didn't reflash the firmware, should I downgrade to 2.15 ?
Click to expand...
Click to collapse
Maybe you should use recovery from maximus thread, it can be specialized for hboot 2.16. AFAIK 2.16 hboot has a different partition system, that could be the problem. Try to wipe your sd with op recomended recovery. You should flash the firmware twice by the way(second one when got the error), i think you already know that
Sent from my One S using xda app-developers app
djiock said:
Hello all !
I have an issue after trying to change ROM : I had "icon stretching" issue with Source, something apparently no one had seen before. I wanted to switch to Maximus, so I flashed it apparently with no problems. But then the phone only booted to Recovery (TWRP)...
So I tried to flash firmware again, the one given in tuto for Maximus but same problem.
And this is when it got tricky, not only I couldn't boot to Android, but I couldn't mount USB either, the option just disappeared ! Along with issue to mount "/cache" apparently. I tried factory reset, then full wipe, no result.
I tried a more recent version of TWRP than the one given with Maximus' tutorial, with it I have the option to mount USB but only for a 48 MB space ! Again, factory reset and full wipe don't help.
I'm not too worried since I can access bootloader and Recovery fine but I feel out of options... I flashed 2.16 firmware like a dozen times (is it any point in doing that ?), I wonder just how I can get a recovery that can mount USB, or a stock ROM to start fresh.
Anybody to help me ? Thanks in advance !
Click to expand...
Click to collapse
Look at this thread, might help you:
http://forum.xda-developers.com/showthread.php?t=2584297
---------- Post added at 03:17 PM ---------- Previous post was at 03:11 PM ----------
djiock said:
Thanks for your reply
I flashed this version but I can only mount a 48MB storage . I didn't reflash the firmware, should I downgrade to 2.15 ?
Click to expand...
Click to collapse
I can mount sdcard with TWRP 2.6.3.0 for hboot 2.15 from this thread: http://forum.xda-developers.com/showthread.php?t=2528113
YYYYYEEEEEESSSS !
Finally ! That was the right way to do it, downgrade to Hboot 2.15 with help of http://forum.xda-developers.com/showthread.php?t=2322755 but the recovery wasn't booting, just reflashing TWRP offered in http://forum.xda-developers.com/showthread.php?t=2528113 did the trick.
And then I was able to mount my SD card and follow the steps to flash Maximus.
What a relief. Thank you all for your help ! I'm just surprised not many people seem to have had the same issue... But maybe they manage to resolve it by themselves !
hi, i just tried to flash Pacman 4.4 Rom from here http://forum.xda-developers.com/showthread.php?t=2670076 but it stopped at the animated "PACROMS loading" Screen (after flashing Rom, Gapps and rebooting).
I had Vipers 5.1 installed before. Restoring my nandroid backup it rebooted after Vipers loading Screen and stopped at the white HTC screen. :crying:
Installed new Vipers now and that worked but all my Settings are gone.
Should i try to restore my backup now again? and what could have been the Problem with the pacman Rom?
my Sensation xe is rooted, s-off, supercid and i used 4ext recovery
thanks in advance and sorry for mistakes. English is not my native language
I don't know if it helps in any way, but since cwm is kinda old (as far as I know) I'd say install latest 4ext recovery and try again.
Did you wipe everything before flashing pac?
Sajito said:
I don't know if it helps in any way, but since cwm is kinda old (as far as I know) I'd say install latest 4ext recovery and try again.
Did you wipe everything before flashing pac?
Click to expand...
Click to collapse
oh my bad im new into all this
i have 4ext recovery already (not cwm) and yes i wiped everything
snierecht said:
oh my bad im new into all this
i have 4ext recovery already (not cwm) and yes i wiped everything
Click to expand...
Click to collapse
What hboot and firmware are you using? And is your 4ext latest one? (v. 1.0.0.6 RC1)
snierecht said:
hi, i just tried to flash Pacman 4.4 Rom from here http://forum.xda-developers.com/showthread.php?t=2670076 but it stopped at the animated "PACROMS loading" Screen (after flashing Rom, Gapps and rebooting).
I had Vipers 5.1 installed before. Restoring my nandroid backup it rebooted after Vipers loading Screen and stopped at the white HTC screen. :crying:
Installed new Vipers now and that worked but all my Settings are gone.
Should i try to restore my backup now again? and what could have been the Problem with the pacman Rom?
my Sensation xe is rooted, s-off, supercid and i used 4ext recovery
thanks in advance and sorry for mistakes. English is not my native language
Click to expand...
Click to collapse
Hi,
try to restore backup, then don't erase nothing with a new install of Vipers5.1.0 but dont wipe anything, it maybe fix your bootloop
Sajito said:
What hboot and firmware are you using? And is your 4ext latest one? (v. 1.0.0.6 RC1)
Click to expand...
Click to collapse
thanks, i had an older 4ext Version (something like 5.xxxx without touch), i updated it now
i guess that will also fix my restore Problem ?
hboot 1.27.1100
Firmware was 3.33 as far as i remember but cant find it at the moment, where can i look it up?
snierecht said:
thanks, i had an older 4ext Version (something like 5.xxxx without touch), i updated it now
i guess that will also fix my restore Problem ?
hboot 1.27.1100
Firmware was 3.33 as far as i remember but cant find it at the moment, where can i look it up?
Click to expand...
Click to collapse
It might help, not sure if it really does. Try out and tell us.
Sajito said:
It might help, not sure if it really does. Try out and tell us.
Click to expand...
Click to collapse
got most things set up again now, had some titanium backups^^
dont want to ruin it again
found this in another thread
keithross39 said:
Jellybean firmwares use a partition called preload.....I'd say with certainty that cwm didn’t backup this partition.....you have to enable the option before you make the nandroid.....
Without the preload backup, any firmware restore will bootloop.....
Sent from my rooted, de bloated, stock JB powered S2 via PhilZ kernel and XDA developers app
Click to expand...
Click to collapse
could this be the reason for not restoring my backup?
snierecht said:
got most things set up again now, had some titanium backups^^
dont want to ruin it again
found this in another thread
could this be the reason for not restoring my backup?
Click to expand...
Click to collapse
Maybe, I don't know since I never faced such an issue.
Sajito said:
Maybe, I don't know since I never faced such an issue.
Click to expand...
Click to collapse
ok thanks for your help and time anyway
snierecht said:
ok thanks for your help and time anyway
Click to expand...
Click to collapse
Have you Tried latest PacMan build???
Its the pac_pyramid-nightly-20140423.zip the latest.
you can get it PacMan Thread
snierecht said:
hi, i just tried to flash Pacman 4.4 Rom from here http://forum.xda-developers.com/showthread.php?t=2670076 but it stopped at the animated "PACROMS loading" Screen (after flashing Rom, Gapps and rebooting).
I had Vipers 5.1 installed before. Restoring my nandroid backup it rebooted after Vipers loading Screen and stopped at the white HTC screen. :crying:
Installed new Vipers now and that worked but all my Settings are gone.
Should i try to restore my backup now again? and what could have been the Problem with the pacman Rom?
my Sensation xe is rooted, s-off, supercid and i used 4ext recovery
thanks in advance and sorry for mistakes. English is not my native language
Click to expand...
Click to collapse
It is so simple if you using 4EX.
Go to recovery>Go to tolls> at the end of page enable Smartfalsh.
Go to wipe> format data/catch and format system with out SD Card. now everything is ok.
Install new ROM and enjoy it
marco1962 said:
It is so simple if you using 4EX.
Go to recovery>Go to tolls> at the end of page enable Smartfalsh.
Go to wipe> format data/catch and format system with out SD Card. now everything is ok.
Install new ROM and enjoy it
Click to expand...
Click to collapse
Im S-Off so i don't need smartflash i think
Updating recovery and firmware solved my problems
snierecht said:
Im S-Off so i don't need smartflash i think
Updating recovery and firmware solved my problems
Click to expand...
Click to collapse
Yeaaaaaaah very nice