[Q] Flashing Pacman and Restore Problem - HTC Sensation

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

Related

[Q] sensation white screen with green logo

Hi guys,
yesterday I have tried to flash androi revolution 6.8.0 on my sensation, but when i have reeboted it have appeared the white screen... my previous rom was the android revolution 6.7.2 for this reason when i flashed the new ARHD I did it whithout superwipe... so what should i do? I can only enter in hboot and recovery i' am disperead!!
thank you for your help!
what recovery do you have? is your device s-on or s-off? If you are s-on you need to flash boot.img separately or enable smart flash in 4ext recovery if you have that installed on your device.
affo93 said:
Hi guys,
yesterday I have tried to flash androi revolution 6.8.0 on my sensation, but when i have reeboted it have appeared the white screen... my previous rom was the android revolution 6.7.2 for this reason when i flashed the new ARHD I did it whithout superwipe... so what should i do? I can only enter in hboot and recovery i' am disperead!!
thank you for your help!
Click to expand...
Click to collapse
Okay, first off calm down becaue you haven't screwed your phone up.
If you can get to recovery, odds are the phone works perfectly fine.
But you did bork up the ROM somehow. All my following advice assumes you are S-OFF. Don't do anything if that's not correct.
Here are your options....
First your cache might be loused up. Go to 4EXT and wipe cache and dalvik and reboot. See if that helps. I don't think this will fix your problem but it's simple and quick to try so why not give it a shot?
Next, if you made a full nandroid backup of ARHD 6.7.2 then you should be able to restore it from 4EXT Recovery. Just go to the restore section and tell it to restore 6.7.2 and it should flash it and boot right up.
If you didn't make a nandroid, you've learned a valuable lesson on why you ALWAYS make a nandroid before flashing a new ROM. ALWAYS!!! So this experience is still a positive for you because you've learned something.
Unfortuantely that means you have an unbootable screwed up ROM installed now that contains all of your user data. And you're going to have to wipe that clean to start this over. So go to 4EXT and do a full wipe, or use Superwipe, then install ARHD 6.8 from scratch. It should boot right up. If it doesn't, download a new copy of 6.8 and put it on teh SD card and try again. It could just be a bad download.
You might even try installing 6.8 again overtop of whatever clustered up mess you've got on there now to see if it resets everything without losing user data. I don't think that will work, but it won't make it worse.
Skipjacks said:
Okay, first off calm down becaue you haven't screwed your phone up.
If you can get to recovery, odds are the phone works perfectly fine.
But you did bork up the ROM somehow. All my following advice assumes you are S-OFF. Don't do anything if that's not correct.
Here are your options....
First your cache might be loused up. Go to 4EXT and wipe cache and dalvik and reboot. See if that helps. I don't think this will fix your problem but it's simple and quick to try so why not give it a shot?
Next, if you made a full nandroid backup of ARHD 6.7.2 then you should be able to restore it from 4EXT Recovery. Just go to the restore section and tell it to restore 6.7.2 and it should flash it and boot right up.
If you didn't make a nandroid, you've learned a valuable lesson on why you ALWAYS make a nandroid before flashing a new ROM. ALWAYS!!! So this experience is still a positive for you because you've learned something.
Unfortuantely that means you have an unbootable screwed up ROM installed now that contains all of your user data. And you're going to have to wipe that clean to start this over. So go to 4EXT and do a full wipe, or use Superwipe, then install ARHD 6.8 from scratch. It should boot right up. If it doesn't, download a new copy of 6.8 and put it on teh SD card and try again. It could just be a bad download.
You might even try installing 6.8 again overtop of whatever clustered up mess you've got on there now to see if it resets everything without losing user data. I don't think that will work, but it won't make it worse.
Click to expand...
Click to collapse
Ok, first of all thank you!
I have tried to make a superwipe and install again ARHD 6.7.2 i had on sdcard but no change, but i have noticed maybe an important thing... when i go in recovery appear this
" your 4EXT theme got corrupted! It was unistalled to prevent damage.
4EXT smartflash is courrently set to update your boot partition on nest system start.
is this wanted or should it be removed?
remove smart flash?"
Could be important?
matekaneve said:
what recovery do you have? is your device s-on or s-off? If you are s-on you need to flash boot.img separately or enable smart flash in 4ext recovery if you have that installed on your device.
Click to expand...
Click to collapse
I have 4EXT and i'm S-OFF. When i go in recovery i see this:
" your 4EXT theme got corrupted! It was unistalled to prevent damage.
4EXT smartflash is courrently set to update your boot partition on nest system start.
is this wanted or should it be removed?
remove smart flash?"
Could it help me?
affo93 said:
I have 4EXT and i'm S-OFF. When i go in recovery i see this:
" your 4EXT theme got corrupted! It was unistalled to prevent damage.
4EXT smartflash is courrently set to update your boot partition on nest system start.
is this wanted or should it be removed?
remove smart flash?"
Could it help me?
Click to expand...
Click to collapse
Remove smartflash because you are S-OFF so you don't need it
Sent from my HTC Sensation XE with Beats Audio Z715e using xda premium
---------- Post added at 10:55 PM ---------- Previous post was at 10:50 PM ----------
Are you running the 3.33 firmware? If not then you need to flash it - goto Kohr-Ah's universal firmware thread in the dev section for it.
If no then its probably just a bad flash. Redownload the ROM then check MD5, if they match then flash, if not then try downloading again.
If MD5 is correct but it still doesnt work reflash the ROM but do a full wipe (wipe everything except sd card from the 4EXT wipe menu).
If that still doesn't work then just try a different ROM.
Sent from my HTC Sensation XE with Beats Audio Z715e using xda premium
Jonny said:
Remove smartflash because you are S-OFF so you don't need it
Sent from my HTC Sensation XE with Beats Audio Z715e using xda premium
---------- Post added at 10:55 PM ---------- Previous post was at 10:50 PM ----------
Are you running the 3.33 firmware? If not then you need to flash it - goto Kohr-Ah's universal firmware thread in the dev section for it.
If no then its probably just a bad flash. Redownload the ROM then check MD5, if they match then flash, if not then try downloading again.
If MD5 is correct but it still doesnt work reflash the ROM but do a full wipe (wipe everything except sd card from the 4EXT wipe menu).
If that still doesn't work then just try a different ROM.
Sent from my HTC Sensation XE with Beats Audio Z715e using xda premium
Click to expand...
Click to collapse
Ok i' ll try this solution!
affo93 said:
Ok i' ll try this solution!
Click to expand...
Click to collapse
Please report back to tell if it worked or not. If it does work this thread will be helpful to someone who finds it on a Google search 3 months from now.
If you don't tell what the outcome was, it will be useless to someone who finds it on a search.
Hope it all works out! Good luck!
First of all... Thank you everybody!
I have tried all solution but nothing seemed to work.... finally I have tried to flash the 4EXT from fastboot and , after reflasing ROM, i have seen my sensation switcing on without problem!
PROBLEM SOLVED!

[Q] phone FC

So I have searched the forums tried the solutions to no avail.
I s-offed friends phone, flashed the RUU to stock, he tries to make a phone call com.android.htcdialer FC's
I then flashed a recovery and used the ATT Stock Root - 3.18.502.6 - JB 4.1.1
I wiped and erased cache and still the same error.
UPDATE:
Issue was resolved when flashing recovery CWM
scrizo said:
So I have searched the forums tried the solutions to no avail.
I s-offed friends phone, flashed the RUU to stock, he tries to make a phone call com.android.htcdialer FC's
I then flashed a recovery and used the ATT Stock Root - 3.18.502.6 - JB 4.1.1
I wiped and erased cache and still the same error.
Click to expand...
Click to collapse
Ruu then try.
Some of the things I have tried.
Went to Apps -> Contacts Cleared Data
Contacts Storage -> Clear Data
Dialer -> Clear Data
Phone -> Clear Data
I noticed on my HTC One X my versions differ than his
My Phone ver: 2.0.503092
His Phone ver: 2.0.503901
My Dialer ver: 4.0.513296
His Dialer ver: 4.0.500167
Is there anything I can do to get him my updated dialer and etc?>
Even when I did the RUU did not work. I did the RUU_EVITA_UL_JB_45_S_Cingular_US_3.18.502.6_Radio_0.24p.32.09.06_10.130.32.34_release_signed_With_Partial
exad said:
Ruu then try.
Click to expand...
Click to collapse
scrizo said:
Some of the things I have tried.
Went to Apps -> Contacts Cleared Data
Contacts Storage -> Clear Data
Dialer -> Clear Data
Phone -> Clear Data
I noticed on my HTC One X my versions differ than his
My Phone ver: 2.0.503092
His Phone ver: 2.0.503901
My Dialer ver: 4.0.513296
His Dialer ver: 4.0.500167
Is there anything I can do to get him my updated dialer and etc?>
Click to expand...
Click to collapse
Dialer version means about as much as the color pants you're wearing.
Flash CWM, wipe everything. Then flash whatever rom. Tell me if it works while CWM is flashed
exad said:
Dialer version means about as much as the color pants you're wearing.
Flash CWM, wipe everything. Then flash whatever rom. Tell me if it works while CWM is flashed
Click to expand...
Click to collapse
CWM touch or non touch or it does not matter?
scrizo said:
CWM touch or non touch or it does not matter?
Click to expand...
Click to collapse
Shouldn't matter
exad said:
Shouldn't matter
Click to expand...
Click to collapse
Works with CWM
scrizo said:
Works with CWM
Click to expand...
Click to collapse
I thought it would.
Seems to be a bug with CWM - TWRP
You can either stay on CWM or try flashing an older version of CWM (the oldest you can find for evita) and then TWRP. and then wipe all and reflash.
It's up to you.
exad said:
I thought it would.
Seems to be a bug with CWM - TWRP
You can either stay on CWM or try flashing an older version of CWM (the oldest you can find for evita) and then TWRP. and then wipe all and reflash.
It's up to you.
Click to expand...
Click to collapse
I told him to stay in the stocked rooted image. It seems he has the first gen htc one x and there was internal issues with the phone and they released an update to the other phones except his, so I just told em to stick with what he has until he upgrades or picks a compatible rom for CWM

[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] Codename Lungo CM11, stuck at android logo first boot.

Hello,
This is my first post. I have searched throughout for an answer but nothing seems to point me in the right direction. So here it goes:
I have an HTC sensation Z710e with:
Kernel : 3.016-ga462f5f (stock)
Unlocked bootloader
CWM 5 flashed
Rooted (obvious i guess, just to be thorough )
S-OFF.
So far so good. I followed the rules/tutorials to the letter and managed to flash the Codename Lungo CM11 version on my phone. On first reboot (before going for the GAPPS as instructed ) the device passes the HTC logo and gets stuck on the android loading logo. Tried it twice with the same results, had to revert to my recovery to get back to working condition.
Is it/could be a kernel issue?
Any tips/advice would be more than welcome.
PS: I wanted to post it in the related thread but no access for me yet :http://forum.xda-developers.com/showthread.php?t=1930403
Silvang said:
Hello,
This is my first post. I have searched throughout for an answer but nothing seems to point me in the right direction. So here it goes:
I have an HTC sensation Z710e with:
Kernel : 3.016-ga462f5f (stock)
Unlocked bootloader
CWM 5 flashed
Rooted (obvious i guess, just to be thorough )
S-OFF.
So far so good. I followed the rules/tutorials to the letter and managed to flash the Codename Lungo CM11 version on my phone. On first reboot (before going for the GAPPS as instructed ) the device passes the HTC logo and gets stuck on the android loading logo. Tried it twice with the same results, had to revert to my recovery to get back to working condition.
Is it/could be a kernel issue?
Any tips/advice would be more than welcome.
PS: I wanted to post it in the related thread but no access for me yet :http://forum.xda-developers.com/showthread.php?t=1930403
Click to expand...
Click to collapse
flash the rom with different recovery
use 4ext instead of cwm
rzr86 said:
flash the rom with different recovery
use 4ext instead of cwm
Click to expand...
Click to collapse
Hey and thanks for your reply. I have followed your advice but the problem persists. Any other ideas?
Cheers
Silvang said:
Hey and thanks for your reply. I have followed your advice but the problem persists. Any other ideas?
Cheers
Click to expand...
Click to collapse
Format the data partition along with system/cache and dalvic cache before flashing the ROM.
Edit: Data partition can be formatted by factory rest operation. Not sure though.
Jeanz Sensation said:
Format the data partition along with system/cache and dalvic cache before flashing the ROM.
Edit: Data partition can be formatted by factory rest operation. Not sure though.
Click to expand...
Click to collapse
You were right that did the trick. Thank you

Need help! May have bricked phone!

So I was trying to updated to a new rom.
to do so i needed to install tarp 2.7
I flash the recovery with fast boot
when it started back up, my internal storage is now at 0 and basically it seems that my sd card is empty...
Any ideas?
bnd10706 said:
So I was trying to updated to a new rom.
to do so i needed to install tarp 2.7
I flash the recovery with fast boot
when it started back up, my internal storage is now at 0 and basically it seems that my sd card is empty...
Any ideas?
Click to expand...
Click to collapse
Run a RUU, return to stock. I'm allmost sure that it is't bricked, or you can try to flash 2.6.3.0 twrp
Insecret said:
Run a RUU, return to stock. I'm allmost sure that it is't bricked, or you can try to flash 2.6.3.0 twrp
Click to expand...
Click to collapse
Ill try to flash 2.6.3.0 to see, i still have fast boot commands.
how do I run an RUU? sorry its been awhile for me.
Insecret said:
Run a RUU, return to stock. I'm allmost sure that it is't bricked, or you can try to flash 2.6.3.0 twrp
Click to expand...
Click to collapse
installing 2.6.3.0 yeilded no results
bnd10706 said:
installing 2.6.3.0 yeilded no results
Click to expand...
Click to collapse
You need to flash the stock recovery and perform "factory reset + clear storage" fo fix the sd card bug. Once done you can install a custom recovery and flash a custom rom OR ru RUU to get your phone back to full stock
LS.xD said:
You need to flash the stock recovery and perform "factory reset + clear storage" fo fix the sd card bug. Once done you can install a custom recovery and flash a custom rom OR ru RUU to get your phone back to full stock
Click to expand...
Click to collapse
Thank you, installed RUU and it worked fine. Thanks!

Categories

Resources