Database Info

All AOSP/CM ROMs bootlooping [FIXED]

All AOSP or CM ROMs are bootlooping. It gets to a certain stage in the boot animation, and then freezes for about 20-25 secs, then reboots and does the whole process again.
This only happens on AOSP or CM based ROMs. Doesn't happen on Sense based ROMs.
Anyone have any suggestions on how to solve this? I'm going to pull a logcat as soon as I can.
Thanks,
Phil

Probably wrong firmware.
Sent from my HTC Pyramid using xda premium

stonew5082 said:
Probably wrong firmware.
Sent from my HTC Pyramid using xda premium
Click to expand...
Click to collapse
So what firmware would I need for AOSP/CM based ROMs?

Steps to install rom properly after rooting and installing clockworkmod recovery.
For Gingerbread roms, 1.17 or 3.12, if you haven't touched the firmware, yours is 1.17.
For ICS roms, flash either 3.12 or 3.24. 3.12 is backwards compatible with GB roms, but 3.24 offers better performance.
Once you have the right firmware, put the rom onto your SD card and reboot into the recovery. There's an option to wipe data and factory reset, usually called "Wipe data/factory reset". Run that once, then install the rom from the zip that you copied earlier and that's about it. If you install anything cyanogen, make sure you flash Google Apps to get the market.
Roms should only take about 2 to 3 minutes to boot for the first time.
Possible issue you're having: Wrong firmware for the rom or you didn't wipe data before installing.

sshede said:
Steps to install rom properly after rooting and installing clockworkmod recovery.
For Gingerbread roms, 1.17 or 3.12, if you haven't touched the firmware, yours is 1.17.
For ICS roms, flash either 3.12 or 3.24. 3.12 is backwards compatible with GB roms, but 3.24 offers better performance.
Once you have the right firmware, put the rom onto your SD card and reboot into the recovery. There's an option to wipe data and factory reset, usually called "Wipe data/factory reset". Run that once, then install the rom from the zip that you copied earlier and that's about it. If you install anything cyanogen, make sure you flash Google Apps to get the market.
Roms should only take about 2 to 3 minutes to boot for the first time.
Possible issue you're having: Wrong firmware for the rom or you didn't wipe data before installing.
Click to expand...
Click to collapse
I do a superwipe and data wipe before installing, so it can't be that.
I'll try your solution now, thanks a lot!
I'm more of an app dev than firmware/ROM/kernels

redbullcat said:
I do a superwipe and data wipe before installing, so it can't be that.
I'll try your solution now, thanks a lot!
I'm more of an app dev than firmware/ROM/kernels
Click to expand...
Click to collapse
MAKE SURE MAKE SURE MAKE SURE your MD5s match. Flashing a firmware can brick your phone extremely easily so make sure your md5s match and that you have sufficient battery life left.
Also you will not be able to go back into bootloader without it asking if you want to flash the firmware if its still on your sd. If it asks you can say no but it will just reboot you into your system so if you have no system to boot into youll be stuck and will have to pull your sd card out and then reinsert it when in recovery.

It worked! Thanks guys, I owe you one

[Q] Switch from 4EXT to CWM ? / Flashing boot.img ? (CM10-alpha)

Hi XDA
My device before the procedure : HTC Desire S, unbranded, Bootloader locked,
HBoot 2.00.0002, S-ON, ICS stock rom via HTC RUU tool
I unlocked the bootloader via htcdev.com.
After hours of reading and testing "everything" I found here on xda (great stuff!!),
I finally managed to have a running CM10-alpha.
(http://forum.xda-developers.com/showthread.php?t=1776256 / Version 2012-09-17)
As I am new to this flashing stuff, I first tried to follow the flashing guide
on the CM-website. Was not workable because "Revolutionary" can not be used on hboot 2...
So I continued with flashing CWM-recovery and after a wipe (factory/reset/cache/dalvik),
I flashed CM10.zip and gapps.zip.
It went through without any errors, unfortunately, the device did not boot afterwards.
I found this guide :
http://forum.xda-developers.com/showthread.php?t=1525100 (CustomROM with 4EXT-recovery)
It indicates flashing "boot.img" (from the CM10 zip-file) as a last step.
Probably the most important step for this HTC device ?!
The Desire S booted CM10 without any further problems and is running since.
(I did not flash GApps.zip, just downloaded Maps and Youtube.)
I have 3 questions :
1. Is it possible to update to a newer version of 4EXT-recovery without losing
the CM10-installation ?
(e.g. 4EXT-Touch : http://forum.xda-developers.com/showthread.php?t=1377745)
2. Is it possible to switch from 4EXT to CWM-recovery without losing
the CM10-installation ? I would like to have CWM because I could then use the ROMManager App.
(e.g. http://forum.xda-developers.com/showthread.php?t=1484753)
3. If I would stick with the current 4EXT-recovery,
do I always have to flash "boot.img" as the last step before booting up the device ?
(e.g. after the next CM10-alpha release)
"fastboot flash boot boot.img"
Click to expand...
Click to collapse
Thanks so much !
CM10 is great, so much faster than HTC-stock rom ICS (with Sense 3.6) !!
CU

1) yes
2)yep
3)si
Edit: you only have to flash the boot.img when the kernel changes from cm10 to fallout yes.
Updating cm10 no, if the dev didn't change the kernel.
After a full wipe (in 4ext format everything exept SD-card) you also have to use fastboot. Because that wipes the boot.img

Thanks !
Just to recap, I can flash CWM-recovery and then do a normal bootup (with my existing CM10 installation). No further actions required !?
As the kernel will probably remain at v2.xx with the next CM10-alpha-release of nik111, I only wipe reset/factory/cache/dalvik
and then flash the new cm10.zip.
I do not think that I will format anything. But if I would, I would have to replace boot.img again.

FrolicFrog said:
Thanks !
Just to recap, I can flash CWM-recovery and then do a normal bootup (with my existing CM10 installation). No further actions required !?
As the kernel will probably remain at v2.xx with the next CM10-alpha-release of nik111, I only wipe reset/factory/cache/dalvik
and then flash the new cm10.zip.
I do not think that I will format anything. But if I would, I would have to replace boot.img again.
Click to expand...
Click to collapse
Changing recovery will not touch anything else on your device. But there were some issues reported with CWM on some ROMs.
I think one of them is a lack of /system/lib partition support, which is important if you go from a ROM that has such to a ROM without one (it will end with two conflicting /system/lib directories and the device will not boot.
Also I am not sure that CWM wipes the .android-secure directory on the SDcard which can cause issues if going from AOSP to Sense ROM

For some reason I never changed from cwm to 4ext whilst I owned a ds but I can confirm it does wipe .android-secure on the sd card

pughie said:
For some reason I never changed from cwm to 4ext whilst I owned a ds but I can confirm it does wipe .android-secure on the sd card
Click to expand...
Click to collapse
I have used it about an year ago so it is definitely improved. But there was an user with Bluetooth issues after flashing my kernel and changing the recovery solved it. Also 4EXT has a lot of minor but very useful settings over CWM. Anyway the OP can try both and stick with the one he likes more
Btw Rom Manager can be used to check for updates and ROM downloads with 4EXT if you choose "manual flash override" from the menu
Sent from my HTC Desire S

amidabuddha said:
Btw Rom Manager can be used to check for updates and ROM downloads with 4EXT if you choose "manual flash override" from the menu
Click to expand...
Click to collapse
Ah, will check on this one. Thanks !

FrolicFrog said:
As the kernel will probably remain at v2.xx with the next CM10-alpha-release of nik111, I only wipe reset/factory/cache/dalvik
and then flash the new cm10.zip.
I do not think that I will format anything. But if I would, I would have to replace boot.img again.
Click to expand...
Click to collapse
Nk111 uploaded a screenshot today, that shows kernel v3.0.16
When upgrading cm10 wiping cache & dalvic cache should be enough. If you get any problems, apps fc or something like that, do a full wipe(I use format all partitions except SD card in 4ext, after that don't forget to flash the kernel with fastboot).
Btw wipe and format is the same.

Bug in CM10 Alpha by nk11
Hello XDA,
Sorry if this question is in the wrong thread.
It is regarding the cm10 alpha port by nk111.
I got it working, save one major bug, the speaker does not produce any sound output whatsoever:
This applies to ringtones, alarm tones and music.
The sound is perfectly audible through a pair of earphones.
I followed the steps in the official thread to delete the file /system/lib/hw/audio_policy.msm7x30.so and reboot
but this only aggravates the issue by disabling all audio outputs!!!
I am running clockwork mod v5 with HTC bootlocker unlocked, S-ON.
Any help would be greatly appreciated.

c.m.b said:
Nk111 uploaded a screenshot today, that shows kernel v3.0.16
When upgrading cm10 wiping cache & dalvic cache should be enough. If you get any problems, apps fc or something like that, do a full wipe(I use format all partitions except SD card in 4ext, after that don't forget to flash the kernel with fastboot).
Btw wipe and format is the same.
Click to expand...
Click to collapse
I saw the screenshot of kernel version 3, too. And was quite excited
Thanks for the hint with wiping only cache&dalvik.

Help! Trying to revert to stock rooted from CM10

I upgraded to CM10 from the original OS and I am using the latest version to root my phone, I am using TWRP. Anyway, Everything worked fine, I rooted the phone, I upgraded to CM10. I want to go back to the original OS. I downloaded [ROM][8/3] - Stock Rooted AT&T 2.20.502.7 - Android 4.0.4 - Odex or De-Odex, I got the ODEX version, I flashed it to my phone but its just hangs at the HTC One X Splash screen with the red lettering. What am I missing here? I can get back into recovery and I backed up my old ROM just in case.

How long are you letting it hang for? Try 2 more power downs and power ons. The first few times it took about 5 min to load.

mgutierrez87 said:
How long are you letting it hang for? Try 2 more power downs and power ons. The first few times it took about 5 min to load.
Click to expand...
Click to collapse
It just shuts off and turns back on again, it basically loops. Did I download the wrong file maybe? Is there a specific ROM I need other than the one I mentioned earlier?

Boot into recovery and wipe your cache and dalvik cache again

mgutierrez87 said:
Boot into recovery and wipe your cache and dalvik cache again
Click to expand...
Click to collapse
Factory reset, wipe system, flash ROM, wipe cache and delvik.
Any time you go from non sense to sense or vise versa you have to wipe the system and factory reset.
Sent from my One X using xda app-developers app

This was the ROM that worked when i did it.
http://forum.xda-developers.com/showthread.php?t=1872842
---------- Post added at 04:53 AM ---------- Previous post was at 04:46 AM ----------
Myrder said:
Factory reset, wipe system, flash ROM, wipe cache and delvik.
Any time you go from non sense to sense or vise versa you have to wipe the system and factory reset.
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
He mentioned in another thread that he did those steps. The only other thing I would try is to flash the boot.IMG from the ROM you want to use

I still want to keep my phone rooted. This wont kill the root right?

No the ROM posted above is stock rooted
But if you made a backup as you said in the first post why are you not just restoring the backup?
Sent from my Nocturnalized One XL using Forum Runner

Basically where I am right now. I downloaded the original OS, by following instructions, I have managed to delete my backed up rom of CM10 that i backed up earlier. I was able to FLASH the OS I wanted, I flashed the boot.img file using fastboot. I restarted the phone and now its just stuck on the HTC Quietly Brilliant screen with the red lettering at the bottom. It doesn't restart or anything, it just hangs there. What am I missing here guys? ):

I'm going to install cm10 right now them go back to stock rooted and see what's up with this

There's no issues going back and forth. You probably flashed a bad ROM

yea, your most likely just doing it wrong. you need to do a full wipe and flash boot.img
answer: oh yea cant flash the stock rom using twrp 2.3.1.0 you will need to flash twrp 2.2.2.0 then flash stock rom. that is actually most likely your problem.

What hboot are you on? If you separately flashed boot.img from CM10 via fastboot, you might need to again separately flash the boot.img from the stock ROM. Also remember that the procedure employed to root 2.20 is substantially different from the root procedure to root the previous build of stock. Not sure what software you rooted, or whether this would pose a problem, but it's a consideration.
Another option is to just restore to stock via RUU and re-unlock, re-root, if nothing else works. Getting stuck on HTC splash screen sounds like a boot.img issue. Good luck.

DvineLord said:
answer: oh yea cant flash the stock rom using twrp 2.3.1.0 you will need to flash twrp 2.2.2.0 then flash stock rom. that is actually most likely your problem.
Click to expand...
Click to collapse
Really? Why is that?
Just curious, I haven't heard this before. Is this a known issue with flashing the 2.20 stock ROM? I haven't seen any cases of ROMs (stock rooted or otherwise) being sensitive to version of TWRP. At least not the case of having to use an older version (keeping TWRP updated is usually the recommendation).
Of course, just because I haven't heard of it, doesn't mean it didn't happen!

Did you fastboot flash boot boot.img?
Sent from my HOX running Cyanogenmod 10

redpoint73 said:
Really? Why is that?
Just curious, I haven't heard this before. Is this a known issue with flashing the 2.20 stock ROM? I haven't seen any cases of ROMs (stock rooted or otherwise) being sensitive to version of TWRP. At least not the case of having to use an older version (keeping TWRP updated is usually the recommendation).
Of course, just because I haven't heard of it, doesn't mean it didn't happen!
Click to expand...
Click to collapse
im assuming the age of the stock rooted would have conflicts with the new twrp. i have had problems with roms not flashing with newest twrp. it is also a known problem since twrp 2.3.1.0 release.

[Q] ViperS 3.1.2 + Sensation XE

Hi.
I want to switch to ViperS 3.1.2 but have few questions before I do so. I've never done it before so I'm new to this.
Does it come rooted (or do all ROMs come rooted)?
Is there any instruction on how to do it or just flash it from .zip via the recovery mode (I have CWM 5.x.x installed already)?
And are there any bugs with it such as Wi-Fi problems/tethering, or calls (speaker)?
Also, what if something goes wrong? I've got a backup of my current ROM (stock), so do I just flash that one back or try ViperS' in case it was a mistake on my side?
Lastly, I've heard some people mentioning OTA updates. I'm assuming it's done in the same way as stock ROMs, so you just need Wi-Fi/working internet and the new update will install on its own, or do I have to download the update from here and then do it myself?
Thanks!

MrCatalyst said:
Hi.
I want to switch to ViperS 3.1.2 but have few questions before I do so. I've never done it before so I'm new to this.
Does it come rooted (or do all ROMs come rooted)?
Is there any instruction on how to do it or just flash it from .zip via the recovery mode (I have CWM 5.x.x installed already)?
And are there any bugs with it such as Wi-Fi problems/tethering, or calls (speaker)?
Also, what if something goes wrong? I've got a backup of my current ROM (stock), so do I just flash that one back or try ViperS' in case it was a mistake on my side?
Lastly, I've heard some people mentioning OTA updates. I'm assuming it's done in the same way as stock ROMs, so you just need Wi-Fi/working internet and the new update will install on its own, or do I have to download the update from here and then do it myself?
Thanks!
Click to expand...
Click to collapse
Are you S-Off or S-On? If S-Off then you can flash the zip directly from recovery and if you're S-On then you gotta flash 4EXT recovery first and enable smart flash feature and then flash the zip file.
There are no major bugs in the Rom except the ones listed on the OP of the official thread. Enjoy flashing.
Sent from my HTC Sensation Z710e using xda app-developers app

I'm S-Off. I've had root earlier but I've installed SuperSU and accidentally pressed Clean SU which has pretty much wiped it. :|

Post your bootloader details to make things more clearer. Flashing a custom Rom doesn't need root access. You can flash it as you're s-off.
What Rom you're using currently? What firmware?
Sent from my HTC Sensation Z710e using xda app-developers app

I apologise for not posting, although it may be a bit too late now since I'm already installing the ROM.
So, just wanna know now - do ROMs come rooted, and if I can always go back to stock ROM as long as I have the boot.img/download stock ROM from HTC site?

MrCatalyst said:
I apologise for not posting, although it may be a bit too late now since I'm already installing the ROM.
So, just wanna know now - do ROMs come rooted, and if I can always go back to stock ROM as long as I have the boot.img/download stock ROM from HTC site?
Click to expand...
Click to collapse
Yup they come pre-rooted

Thanks for the help, everyone! Managed to install the ROM, despite being stuck in bootloop for 2 hours but it works flawlessly now.

MrCatalyst said:
I apologise for not posting, although it may be a bit too late now since I'm already installing the ROM.
So, just wanna know now - do ROMs come rooted, and if I can always go back to stock ROM as long as I have the boot.img/download stock ROM from HTC site?
Click to expand...
Click to collapse
Most roms come rooted, and the rest provide root tools so you have a choice while flashing.
To return to stock look up ruu. An ruu + s on = your device as it came.

If you had flashed Firmware-3.33 before the ROM - you would have had no "bootloops" at all! The most important thing is to have Firmware-3.33

Rom is broken , EMERGENCY , plz help
Hello everybody. I'm in a real trouble with my phone. it's very emergency , so i really need your help please. My ViperS 3.1.2 is broken and doesn't boot. i reinstalled Rom without wiping and again with update only setting but still doesn't boot.I flashed boot.img again but still... i did everything i could such as wiping cache and dalvik cache but again the same problem. the phone stays on "SENSATION" boot screen with beats audio on bottom for 20 seconds and suddenly screen become dark and phone restarts . i wiped dalvik and again "android is upgrading" starts and after it finished the phone restarts again i know if i perform a full wipe during Rom installation it will be fixed but i REALLY,REALLY,REALLY need my contacts and messages.... is there anyway i could fix my phone or make a backup of contacts and messages??? PLEEAAASSSE help me . tnx

VAHIDHAVASBEIGY said:
Hello everybody. I'm in a real trouble with my phone. it's very emergency , so i really need your help please. My ViperS 3.1.2 is broken and doesn't boot. i reinstalled Rom without wiping and again with update only setting but still doesn't boot.I flashed boot.img again but still... i did everything i could such as wiping cache and dalvik cache but again the same problem. the phone stays on "SENSATION" boot screen with beats audio on bottom for 20 seconds and suddenly screen become dark and phone restarts . i wiped dalvik and again "android is upgrading" starts and after it finished the phone restarts again i know if i perform a full wipe during Rom installation it will be fixed but i REALLY,REALLY,REALLY need my contacts and messages.... is there anyway i could fix my phone or make a backup of contacts and messages??? PLEEAAASSSE help me . tnx
Click to expand...
Click to collapse
If you made a backup before flashing you should restore it, or else flash the ROM you had before flashing.
Then use "Titanium Backup" and back up your messages (your contacts are automatically synced with your google account, unless you saved them on the phone, but you can change that with the "people" app.
after you backed your phone up, make a full wipe, and flash the new ROM. Install Titanium Backup and restore your messages backup.
Good luck.

astar26 said:
If you made a backup before flashing you should restore it, or else flash the ROM you had before flashing.
Then use "Titanium Backup" and back up your messages (your contacts are automatically synced with your google account, unless you saved them on the phone, but you can change that with the "people" app.
after you backed your phone up, make a full wipe, and flash the new ROM. Install Titanium Backup and restore your messages backup.
Good luck.
Click to expand...
Click to collapse
excuse me, you said 2 options . first is to restore backup , unfortunately i don't have backup. second is flashing the rom i had before flashing ! i didn't understand what you said... what do you mean? i don't have any backup, if you can help me to boot up phone just for 2 mins to backup my contacts! they aren't synced to my google account....

pleeeeaaaaaaaaaasssseeeee helppp meee. i am becoming crazyy because of my problem.... HELP PLZZZ :crying:

VAHIDHAVASBEIGY said:
excuse me, you said 2 options . first is to restore backup , unfortunately i don't have backup. second is flashing the rom i had before flashing ! i didn't understand what you said... what do you mean? i don't have any backup, if you can help me to boot up phone just for 2 mins to backup my contacts! they aren't synced to my google account....
Click to expand...
Click to collapse
Get a download of the ROM you had before, and you can flash it normally. If you had stock, find a download of stock ROM (although Sense 3.6 custom ROMs might actually work too).

Right
i dont had a Problem :good:

astar26 said:
Get a download of the ROM you had before, and you can flash it normally. If you had stock, find a download of stock ROM (although Sense 3.6 custom ROMs might actually work too).
Click to expand...
Click to collapse
excuse me again! you mean install another ROM without Wiping on ViperS? I am using ViperS for about 1 years, Are you sure? now i should download another ROM like Android Revolution HD for sensation and install it on my phone without performing full wipe and it can fix boot problem?

VAHIDHAVASBEIGY said:
excuse me again! you mean install another ROM without Wiping on ViperS? I am using ViperS for about 1 years, Are you sure? now i should download another ROM like Android Revolution HD for sensation and install it on my phone without performing full wipe and it can fix boot problem?
Click to expand...
Click to collapse
Oh no, I thought you wanted to flash viperS. Flash the ROM you had before flashing, whichever ROM that was (but flash that specific ROM, not a different one. My advice from the previous comment was if you came from stock ROM). If you flash the same ROM you don't have to wipe, and then you can back up your phone.

astar26 said:
Oh no, I thought you wanted to flash viperS. Flash the ROM you had before flashing, whichever ROM that was (but flash that specific ROM, not a different one. My advice from the previous comment was if you came from stock ROM). If you flash the same ROM you don't have to wipe, and then you can back up your phone.
Click to expand...
Click to collapse
ohhh , in my first post i said ( i reinstalled Rom without wiping and again ...) i mean i did your advice , but it doesn't fix my problem... :crying:

VAHIDHAVASBEIGY said:
ohhh , in my first post i said ( i reinstalled Rom without wiping and again ...) i mean i did your advice , but it doesn't fix my problem... :crying:
Click to expand...
Click to collapse
I hope you can operate adb, because the solution I found requires it.
Go to recovery, and use adbto pull the contacts database with the following command:
adb pull data/data/com.android.providers.contacts/databases/contacts.db
It might give an error for a protected directory (but I don't know since it's going to be done in recovery), if that happens, use 'adb shell' and then 'su'. then exit, and you have root access to the device (do it only if required).
Once you obtained the file, it should be on your adb folder. you need to open it with a database app which supports SQLite3 (I won't reccomend anyrhing since I've never used them. but from a quick search I found a few. and searching in the context of reading android databases would give some recommendations.).
Good luck
p.s - It's hard for me to believe this is the simplest solution. It might work, but it's not easy. So others might give better solutions.

astar26 said:
I hope you can operate adb, because the solution I found requires it.
Go to recovery, and use adbto pull the contacts database with the following command:
adb pull data/data/com.android.providers.contacts/databases/contacts.db
It might give an error for a protected directory (but I don't know since it's going to be done in recovery), if that happens, use 'adb shell' and then 'su'. then exit, and you have root access to the device (do it only if required).
Once you obtained the file, it should be on your adb folder. you need to open it with a database app which supports SQLite3 (I won't reccomend anyrhing since I've never used them. but from a quick search I found a few. and searching in the context of reading android databases would give some recommendations.).
Good luck
p.s - It's hard for me to believe this is the simplest solution. It might work, but it's not easy. So others might give better solutions.
Click to expand...
Click to collapse
tnx , if i try i can do it. i can operate adb easily . but a person said me to backup /data partition with recovery and then perform a full wipe and install viperS again then restore /data . do you have any idea abou it? can it help?

[Q] Flashing Pacman and Restore Problem

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