[Q] ViperRom stuck on splash screen - Sprint HTC One (M7)

So I flashed ViperRom with no problem after clearing all cache, dalvik, data and system. everything loaded perfectly, I logged into all of my accounts and then re-installed all of my apps and system data using Titanium Backup. After the TB restore, TB recommended a reboot so I did. And now when the system loads, it is stuck on the ViperRom splash screen. I'm pretty new at this, but not a complete novice.
Can anyone offer a solution?

sicdude said:
So I flashed ViperRom with no problem after clearing all cache, dalvik, data and system. everything loaded perfectly, I logged into all of my accounts and then re-installed all of my apps and system data using Titanium Backup. After the TB restore, TB recommended a reboot so I did. And now when the system loads, it is stuck on the ViperRom splash screen. I'm pretty new at this, but not a complete novice.
Can anyone offer a solution?
Click to expand...
Click to collapse
reflash

sicdude said:
So I flashed ViperRom with no problem after clearing all cache, dalvik, data and system. everything loaded perfectly, I logged into all of my accounts and then re-installed all of my apps and system data using Titanium Backup. After the TB restore, TB recommended a reboot so I did. And now when the system loads, it is stuck on the ViperRom splash screen. I'm pretty new at this, but not a complete novice.
Can anyone offer a solution?
Click to expand...
Click to collapse
Sometimes Titanium Backup restores something from one ROM that doesn't play nicely with another. I'd do as flex says and reflash then be careful restoring your apps.
Sent from my HTCONE using Tapatalk 4 Beta

sicdude said:
I logged into all of my accounts and then re-installed all of my apps and system data using Titanium Backup.
Click to expand...
Click to collapse
coal686 said:
Sometimes Titanium Backup restores something from one ROM that doesn't play nicely with another. I'd do as flex says and reflash then be careful restoring your apps.
Click to expand...
Click to collapse
Restoring system data is really iffy. You shouldn't do it unless you really need to. If the app has most/all my data in the cloud (i.e FB, email), then I don't bother backing it up.

Thanks everybody for your help. I did clear all my data again and re-flash. Everything loaded just fine, and I was a little more selective when I restored my apps from titanium. Everything seems to be working ok now. I haven't restarted again for fear of getting stuck again, but I'll cross that bridge when I need to

Help
sauprankul said:
Restoring system data is really iffy. You shouldn't do it unless you really need to. If the app has most/all my data in the cloud (i.e FB, email), then I don't bother backing it up.
Click to expand...
Click to collapse
Please help I had the same problem and I've flashed it twice now but it is still stuck on HTC One screen, Can anyone please help me

thedream83 said:
Please help I had the same problem and I've flashed it twice now but it is still stuck on HTC One screen, Can anyone please help me
Click to expand...
Click to collapse
Try being more careful on what you restore from Titanium Backup. Personally I only backup and restore games + messages + contacts every time I wipe my device.
Alternatively, if you have SuperSU installed, make sure to try flashing it from TWRP from this link. Just telling this to you because most of the booting problems are because of SuperSU atm.

Related

[Q] Droid 4 CM10.1 Stuck at Boot

My phone will currently not boot bast the CyanogenMod boot screen.
I flashed my phone several months ago to CM10.1 It was the update that patched the "masterkey" bug. I have been using it daily since then with no problems.
Today, I turn my phone on, and it just hangs at the boot animation.
There were no significant changes since the last time it was powered on. I think I installed McPixel from the humblebundle, and uninstalled a game from the playstore called Krog. No setting changes of any significance.
I've tried booting into safestrape and deleting both the cache and the dalvik cache, neither has helped. My stock rom still loads just fine, but i had factory reset it quite a while ago. I do have a backup of the rom from about 40 days ago i can try restoring, but i would love a more nondestructive way to fix this.
Try booting into safestrap, wiping system, cache, and dalvik, then reinstall the ROM and gapps.
Droid 4 - Avatar
kwyrt said:
Try booting into safestrap, wiping system, cache, and dalvik, then reinstall the ROM and gapps.
Droid 4 - Avatar
Click to expand...
Click to collapse
0.o wouldn't that be a LOT more destructive than just restoring the old backup?
pyro42 said:
0.o wouldn't that be a LOT more destructive than just restoring the old backup?
Click to expand...
Click to collapse
Nope. You are not wiping data so all your apps, setting, etc will still be there.
the data itself will remain if you just wipe the system, cache and dalvik cache but be sure to reinstall the latest stable build of CM and gapps for it
Sent from my XT894 using xda premium
kwyrt said:
Nope. You are not wiping data so all your apps, setting, etc will still be there.
Click to expand...
Click to collapse
ah gotcha gotcha...
unfortunately it didn't work.
for troubleshooting's sake, i went ahead and made a backup of the rom in it's non-working state.
i restored my old backup, it boots just fine.
restored borked backup (tested it, still won't boot), wiped cache/dcache, wiped system, installed cm-10.2-20130821-NIGHTLY-maserati.zip and gapps 20130812, wiped cache/dcache again for good measure, then reboot and waited 10 minutes, still won't pass boot logo.
so i figure someting's wrong with Data right? so i rebooted to safestrap and did a factory restore, then wiped cache/dcache, and still won't boot.
so now i'm going at it the opposite direction. restoring the working backup, restoring just the data from the nonworking backup, then upgrading CM/Gapps
rebooting.. and....
blank screen with full backlight. not so much as a CM logo.
i guess for now i am going to restore back to the old backup, update the rom, and go about reconfiguring, unless anyone has any more suggestions?
pyro42 said:
ah gotcha gotcha...
unfortunately it didn't work.
for troubleshooting's sake, i went ahead and made a backup of the rom in it's non-working state.
i restored my old backup, it boots just fine.
restored borked backup (tested it, still won't boot), wiped cache/dcache, wiped system, installed cm-10.2-20130821-NIGHTLY-maserati.zip and gapps 20130812, wiped cache/dcache again for good measure, then reboot and waited 10 minutes, still won't pass boot logo.
so i figure someting's wrong with Data right? so i rebooted to safestrap and did a factory restore, then wiped cache/dcache, and still won't boot.
so now i'm going at it the opposite direction. restoring the working backup, restoring just the data from the nonworking backup, then upgrading CM/Gapps
rebooting.. and....
blank screen with full backlight. not so much as a CM logo.
i guess for now i am going to restore back to the old backup, update the rom, and go about reconfiguring, unless anyone has any more suggestions?
Click to expand...
Click to collapse
Yeah, definitely sounds like something in /Data. Only other possible option I can think of would be to use Titanium Backup. It has an option to "Extract from Nandroid backup". It's under the "SPECIAL BACKUP/RESTORE" options. I've never used that option before so I have no idea how or if it would work but might be worth a shot.
kwyrt said:
Yeah, definitely sounds like something in /Data. Only other possible option I can think of would be to use Titanium Backup. It has an option to "Extract from Nandroid backup". It's under the "SPECIAL BACKUP/RESTORE" options. I've never used that option before so I have no idea how or if it would work but might be worth a shot.
Click to expand...
Click to collapse
wonderful idea, unfortunately TB crashes when i point it at either backup.
buuut i did find Nandroid Manager * ROOT which looks like it might be working.
if you really wanna see if it is the data or not have you tried to
flash 10.2 or whatever you started out with... then restore -just-
the data to the freshly flash system and then do a wipe of all
said caches... I do that sometimes to get a fresh start on my
os itself.. works pretty well. Just do not restore the cache just
the data part. Or restore with MD5 checking... if it doesn't check
out then you know for a fact that the data partition in that specific
nandroid isn't any good :/

[Q] Stuck at Boot logo after App Restore using TiBu

My N7000 stays stuck at the "Samsung Galaxy Note" screen when I try restarting after a restore using TiBu. This is the case with both CM 10.2 as well as Stock ROM. However, If I get into the recovery and wipe data and cache (Factory Reset) it boots back normally.
I am on the latest DBT German ROM with latest Philz Kernel in case of Stock.
In case of CM 10.2 there is no kernel or recovery change.
Any suggestions to fix this?
Maybe you'll tell us what you restored with TB first?
TB Back up order
ThaiDai said:
Maybe you'll tell us what you restore with TB first?
Click to expand...
Click to collapse
Step 1: Restoring the messages and call logs (XML Format)
Step 2: Followed by restore of User Apps and Data.
Step 3: Finally System Apps Data.
I have shuffled between CM and Stock several times in the past and have followed this order without issues.
Now, as soon as I restore User Apps and do a reboot, it gets stuck.
Step 3: not difficult to guess why this is your problem. Try without.
ThaiDai said:
Step 3: not difficult to guess why this is your problem. Try without.
Click to expand...
Click to collapse
Right now it is getting stuck after step 2 but before executing step 3. I was also aware that step 3 could be an issue so i let it stay minimal or rare.
Fixed
Can the Admins close the thread please? This has been fixed now.
Solution the way i closed the issue:
I did not perform the App restore. I downloaded the apps afresh and then did the data restore alone for the really necessary apps.
Never restore system apps. Don't even use TiBU to back up system apps. This causes conflicts within the OS and will cause a boot loop.
normaltusker said:
Step 1: Restoring the messages and call logs (XML Format)
Step 2: Followed by restore of User Apps and Data.
Step 3: Finally System Apps Data.
I have shuffled between CM and Stock several times in the past and have followed this order without issues.
Now, as soon as I restore User Apps and do a reboot, it gets stuck.
Click to expand...
Click to collapse
Never restore system data. If the rom has other structure there's no way it can boot. You have to set up whole settings by yourself. And for the messages use program from Google store to backup and restore them. This won't brick Your phone
Sent from my GT-N7000 using xda app-developers app

[Q] Restore a recovery image onto another phone

I have a rooted HTC one with viper rom, my coworker has the same phone but with Android Revolution.
If I was to restore my recovery image.zip onto his phone, would this work? Or do I have to customise it alittle. If so, how would I do this?
I want him to keep all the same settings I have, but with different phone information. If that makes any sense? (sorry)
Any help would be greatly appreciated. Don't want the trouble of installing the rom and setting up the same settings and tweaks.
Thanks,
Andy
killerb4dger said:
I have a rooted HTC one with viper rom, my coworker has the same phone but with Android Revolution.
If I was to restore my recovery image.zip onto his phone, would this work? Or do I have to customise it alittle. If so, how would I do this?
I want him to keep all the same settings I have, but with different phone information. If that makes any sense? (sorry)
Any help would be greatly appreciated. Don't want the trouble of installing the rom and setting up the same settings and tweaks.
Thanks,
Andy
Click to expand...
Click to collapse
the image.zip that recovery creates only contains /system not everything (at least for me CWM 6.0.3.2), but you could do a full backup and transfer the entire folder to the other phone, and then do a RESTORE (not flash).
That will duplicate everything including apps and data, as well as all your accounts etc. which I guess you would have to delete and setup again.
nkk71 said:
the image.zip that recovery creates only contains /system not everything (at least for me CWM 6.0.3.2), but you could do a full backup and transfer the entire folder to the other phone, and then do a RESTORE (not flash).
That will duplicate everything including apps and data, as well as all your accounts etc. which I guess you would have to delete and setup again.
Click to expand...
Click to collapse
So I would need wipe and install the viper rom onto his device and restore my (custom) backup to it also. Sounds easy enough, I'll give that a try.
Thanks for the help.
killerb4dger said:
So I would need wipe and install the viper rom onto his device and restore my (custom) backup to it also. Sounds easy enough, I'll give that a try.
Thanks for the help.
Click to expand...
Click to collapse
No need to wipe, the restore will automatically wipe everything on the phone. Except sdcard of course.
But in recovery do a wipe of cache and dalvik after restore and before boot, just to be safe.
Sent from my HTC One using Tapatalk
Ah, I understand.
Thanks again!

[Q][Solved] Dialer Crashes After Installing Nexus Version

Hi, so I have Moto G 2014 XT1068. It's rooted, and TWRP is installed. I flashed the Nexus dialer (the one with Nearby Places, and Caller ID by Google) from recovery using a zip file, and uninstalled the original one (Big mistake, I know.)
Then I couldn't get calls UI to work, so I reinstalled the original stock dialer using a backup. Now calls work, but everytime I try to open the stock dialer, it shows up as "Dialler has stopped working."
The Nexus UI, however, still works.
I could live with this current scenario, as I can make, pick up, and break calls without problems, but I might need to access the call settings from the stock dialer's menu, which I can't.
All help appreciated - I'm not open to reflashing the firmware / resetting it. I have a backup of the stock dialer made using Titanium, but restoring it does not fix the issue.
Cheers!
Uninstall the Nexus dialer app and then wipe cache and dalvik-cache from TWRP.
sharkymyn said:
Uninstall the Nexus dialer app and then wipe cache and dalvik-cache from TWRP.
Click to expand...
Click to collapse
EDIT : Thank you for your reply. Sadly, this did not work.
I have also tried booting in Safe Mode, but the app did not work there either.
Cheers!
Did you take a full system backup via TWRP?. Try restoring it else flashing factory firmware is the only option left.
Follow this thread : http://forum.xda-developers.com/moto-g-2014/general/restore-to-stock-t2873657
sharkymyn said:
Did you take a full system backup via TWRP?. Try restoring it else flashing factory firmware is the only option left.
Follow this thread : http://forum.xda-developers.com/moto-g-2014/general/restore-to-stock-t2873657
Click to expand...
Click to collapse
I think I'll wait it out, see if somebody else has another solution, or until I really need to open the settings
Thanks again.
Go to setting>app>stock dialer>clear data n cache> reboot. Njoy
gauravrai said:
Go to setting>app>stock dialer>clear data n cache> reboot. Njoy
Click to expand...
Click to collapse
Thanks, but that didn't work. I fixed it, but it was quite long, though not complicated.
Remove Nexus dialer using Titanium.
Take Nandroid / Titanium backup of all apps and data.
Flash stock - without clearing user data. This will remove recovery as well. Boot and install any OTA updates available.
Reinstall recovery and reroot. Restore stuff using Titanium.
Moral of the story : Have a nandroid backup before messing around.
Cheers!

[Q] Bootloop "Unfortunately the process com.android.phone has stopped"

Hi everybody !
I have a very annoying issue with my Nexus 6
I did a full nandroid backup with TWRP before sending it for RMA
I received yesterday my phone repaired, and I have tried to restore my nandroid backup
unfortunately, I've got a bootloop with the message "Unfortunately the process com.android.phone has stopped"
Can somebody help me please ? thank you very much
I will be very grateful...
MrMoi said:
Hi everybody !
I have a very annoying issue with my Nexus 6
I did a full nandroid backup with TWRP before sending it for RMA
I received yesterday my phone repaired, and I have tried to restore my nandroid backup
unfortunately, I've got a bootloop with the message "Unfortunately the process com.android.phone has stopped"
Can somebody help me please ? thank you very much
I will be very grateful...
Click to expand...
Click to collapse
You can't restore a back from one device to another. Boot to recovery and do a full factory reset. You'll have to set it up as a new device.
This is triggered by the phone application or sim card application. Can you get into bootloader or twrp?
thank you !
but it's the same phone, just the screen is new
And I have access to twrp and the bootloader of course
Nobody ? I can pay for a solution...
MrMoi said:
Nobody ? I can pay for a solution...
Click to expand...
Click to collapse
Have you tried a factory reset in recovery, as I suggested previously?
You can try to flash system.img using fastboot (download factory image from developers.google.com/android/nexus/images, and extract system.img, and fastboot flash it - no guarantees it will work, but worth a try )
I have already try to flash only the system.img
And a factory reset works.. But I wont lost everything ..
MrMoi said:
I have already try to flash only the system.img
And a factory reset works.. But I wont lost everything ..
Click to expand...
Click to collapse
Pick your poison...
if someone know which apps cause the issue, I can try to delete it with adb shell
You have a nandroid backup, so do a full reset to get the phone up and running again...
After that, let the Google backup feature install all your apps from the playstore and then use Titanium Backup to restore data only from the nandroid.
I've flashed a clean system, and after I tried to restore my app with Titanium Backup with my nandroid backup but it doesn't work..
Details please... "It doesn't work" doesn't say anything.
Stop using the nandroid to restore things.. They almost always cause issues. Also never restore a nandroid after a repair. The parts are different. So things could easily get messed
I use Google backup and MyBackup Pro.
When I try to restore with titanium backup, I can browse my nandroid backup, see all my apps.. Restore them (it tooks long time ) titanium tell me "success" but nothing append
zelendel said:
Stop using the nandroid to restore things.. They almost always cause issues. Also never restore a nandroid after a repair. The parts are different. So things could easily get messed
Click to expand...
Click to collapse
There's a reason he has zero thanks. He won't listen to advice....
cam30era said:
There's a reason he has zero thanks. He won't listen to advice....
Click to expand...
Click to collapse
I would like.. but a nandroid backup is the only backup that I have ... for the next time, I will do a different backup..
Do you have a better alternative for the next time ?
for the moment.. I have only a nandroid backup.. I need to try with it
MrMoi said:
I would like.. but a nandroid backup is the only backup that I have ... for the next time, I will do a different backup..
Do you have a better alternative for the next time ?
for the moment.. I have only a nandroid backup.. I need to try with it
Click to expand...
Click to collapse
Just flash stock, it's that easy!
As long as you sign in with the same Google account that was previously on the device, there will be something in the setup asking if you would like to restore from a previously used device, and you just select Nexus 6 from the drop down menu (make sure you select the right date), it will restore all of your apps, contacts, and it'll be back to normal within a few minutes. You'll lose your app data, but this doesn't matter much unless you play games. You'll have to flash twrp and root again, but at least you'll have a working device.
Although this is coming from someone who doesn't have any important data on their phone, it doesn't matter. You still have between having a device that doesn't boot or starting fresh. It's kind of fun sometimes .

Categories

Resources