Related
So I was able to successfully root my AT&T HTC One X and decided I wanted to install the CM 10 ROM (1st ROM install). I did all the data backups with Titanium, downloaded the latest zip files from cyanogenMod (both the 12/13 and 12/14 nightly versions), transferred them to my phone, booted into recovery (TWRP), did a back-up, did a system wipe, flashed the ROM and then did a reboot. However, when it boots it gets stuck in the boot-up screen (bootloop) and doesn't do anything. I have read on this and it keeps saying to wipe system data again and flash the ROM again and it keeps doing this. I want to install this ROM, but I need some help. Any suggestions on what I did wrong?
Note: I accidentally posted this in the Android Q&A section, so I apologize for the double post. I just think this is probably the best place to get my answer.
Did you flash the boot.img?
I did, but incorrectly the first time. I flashed it the right way and everything is working good. Then only problem I have now is when restoring from Titanium Backup it gives me an error from a process called com.android.phone (I think that is what it said). So I wiped it again and rebooted and everything is fine. I can reinstall all the apps, but what could cause that? Could it be some of the data backed up doesn't cooperate with this ROM? Either way I love the CM10 ROM.
jon8105 said:
I did, but incorrectly the first time. I flashed it the right way and everything is working good. Then only problem I have now is when restoring from Titanium Backup it gives me an error from a process called com.android.phone (I think that is what it said). So I wiped it again and rebooted and everything is fine. I can reinstall all the apps, but what could cause that? Could it be some of the data backed up doesn't cooperate with this ROM? Either way I love the CM10 ROM.
Click to expand...
Click to collapse
if they are backups from sense, that *MAY* cause problems, but don't quote me on that. I don't use sense, can't say for sure
OK, maybe that is why. Not a big deal since I haven't had the One X too long. Thanks for the help guys.
Good to know
Long time lurker (though I can't say I always understood everything I read), first time poster.
I've had several iPhones in the past and I finally decided to try the other option. I got a Verizon GS3 last November and I couldn't be happier.
However, like many others, I'm looking to get more from my phone. I do like TouchWiz (I have used a Nexus 4 for a week and didn't like the stock android), so I want to stay with about the same UI that I have now. I did some research and found that Synergy is probably the best option for me in terms of getting a bit more from my phone but still staying with (mostly) the same UI. Of course, getting rid of all the annoying Verizon apps is a huge bonus too.
This is what I have done already:
Used this method to root and unlock my bootloader: http://forum.xda-developers.com/showthread.php?t=2332825
Used TWRP to make a full backup of my phone to an external SD card
Used Titanium Backup to make a full backup of my apps to an external SD card
Here are my questions:
I have the latest Verizon OTA installed (June 20th, I535VRBMF1). I have read all the posts from the last 14 days on the Synergy thread and I think I understand that since my phone has a newer firmware than the one in the latest synergy ROM, I will need to downgrade my firmware before installing the ROM to avoid camera and wifi problems. Is this correct? Someone linked there to I535VRBMB1_firmware.zip. How do I install this firmware? I have ODIN but when I choose PDA it will not let me choose the zip file. When I extract it, ODIN doesn't find anything too.
What kind of wipe should I perform before I flash to Synergy? Should I take my SD card out for the wipe or leave it in? Do I even need to wipe?
Can I install the ROM from ROM Manager or should I always use recovery mode and TWRP?
Is it recommended to just restore my Titanium full backup after the wipe? Should I have backed up everything except verizon apps if I don't want these? Should I just restore those apps where I want my old data (like game progress)?
Thanks in advance for any help. I have learned a lot from these forums but I feel I need a bit more clarifications before I proceed with a task that may be damaging for my device.
Slartibartfast_ said:
Long time lurker (though I can't say I always understood everything I read), first time poster.
I've had several iPhones in the past and I finally decided to try the other option. I got a Verizon GS3 last November and I couldn't be happier.
However, like many others, I'm looking to get more from my phone. I do like TouchWiz (I have used a Nexus 4 for a week and didn't like the stock android), so I want to stay with about the same UI that I have now. I did some research and found that Synergy is probably the best option for me in terms of getting a bit more from my phone but still staying with (mostly) the same UI. Of course, getting rid of all the annoying Verizon apps is a huge bonus too.
This is what I have done already:
Used this method to root and unlock my bootloader: http://forum.xda-developers.com/showthread.php?t=2332825
Used TWRP to make a full backup of my phone to an external SD card
Used Titanium Backup to make a full backup of my apps to an external SD card
Here are my questions:
I have the latest Verizon OTA installed (June 20th, I535VRBMF1). I have read all the posts from the last 14 days on the Synergy thread and I think I understand that since my phone has a newer firmware than the one in the latest synergy ROM, I will need to downgrade my firmware before installing the ROM to avoid camera and wifi problems. Is this correct? Someone linked there to I535VRBMB1_firmware.zip. How do I install this firmware? I have ODIN but when I choose PDA it will not let me choose the zip file. When I extract it, ODIN doesn't find anything too.
What kind of wipe should I perform before I flash to Synergy? Should I take my SD card out for the wipe or leave it in? Do I even need to wipe?
Can I install the ROM from ROM Manager or should I always use recovery mode and TWRP?
Is it recommended to just restore my Titanium full backup after the wipe? Should I have backed up everything except verizon apps if I don't want these? Should I just restore those apps where I want my old data (like game progress)?
Thanks in advance for any help. I have learned a lot from these forums but I feel I need a bit more clarifications before I proceed with a task that may be damaging for my device.
Click to expand...
Click to collapse
1 - You can roll back to MB1, or flash a kernel that supports the camera w/MF1. The camera not working seems to be the primary issue. I know Ktoonsez kernel works as do a couple of others.
2 - Wipe system, cache and Dalvik. You don't need to do anything with your card.
3 - At least the first time, I'd recommend using TWRP in recovery mode to flash your new ROM. Someone else may have a different opinion, but you'll already be in TWRP to wipe everything.
4 - Different people have different experiences with TiBU. Most would recommend not restoring system data, but apps(non-system) and app. data is usually okay.
lvgdgts said:
1 - You can roll back to MB1, or flash a kernel that supports the camera w/MF1. The camera not working seems to be the primary issue. I know Ktoonsez kernel works as do a couple of others.
2 - Wipe system, cache and Dalvik. You don't need to do anything with your card.
3 - At least the first time, I'd recommend using TWRP in recovery mode to flash your new ROM. Someone else may have a different opinion, but you'll already be in TWRP to wipe everything.
4 - Different people have different experiences with TiBU. Most would recommend not restoring system data, but apps(non-system) and app. data is usually okay.
Click to expand...
Click to collapse
I appreciate your detailed response!
I'm probably going to attempt this tomorrow. Will report back with what my results. It looks like BoneStock might be another good option for me + save me the kernel replacement or firmware flash. I have some reading to do now
Slartibartfast_ said:
Here are my questions:
I have the latest Verizon OTA installed (June 20th, I535VRBMF1). I have read all the posts from the last 14 days on the Synergy thread and I think I understand that since my phone has a newer firmware than the one in the latest synergy ROM, I will need to downgrade my firmware before installing the ROM to avoid camera and wifi problems. Is this correct? Someone linked there to I535VRBMB1_firmware.zip. How do I install this firmware? I have ODIN but when I choose PDA it will not let me choose the zip file. When I extract it, ODIN doesn't find anything too.
Click to expand...
Click to collapse
Just to add onto lvgdgts' post: files ending with ".zip" are flashed in recovery, files ending with ".tar" or ".tar.md5" are flashed via Odin.
SlimSnoopOS said:
Just to add onto lvgdgts' post: files ending with ".zip" are flashed in recovery, files ending with ".tar" or ".tar.md5" are flashed via Odin.
Click to expand...
Click to collapse
Thanks!
I decided to go with BoneStock 3.1. Whole process took less than half an hour. Used TWRP manager to wipe+install the ROM. Restore from Titanium restored 95% of my stuff, only needed to manually restore my text messages.
Thanks for the help!
Hey guys, i'm posting here because I have a huge issue with my phone.
I think I have an idea of what caused my phone to go haywire, but i'm gonna post my phone specs:
Red Nexus 5 32gb
Rooted
Franco Kernel
4.4.2 (however, I think it may have somehow updated to 4.4.3 OTA somehow, which may be the root of the problems)
TWRP
Nandroid backup but done once i've been experiencing these problems
-The phone boots up normally and then abrubtly freezes.
-The dialogue "Unfortunately, the process com.android.systemui has stopped."
-I press ok, the screen turns black
-"Unfortunately, Update Device has stopped"
-I press ok, shortly after, both prompts pop up again repeatedly.
I literally have no way to get to the home menu, even using Safe Mode.
My main priority is to at least recover my SMS files. And obviously fix my phone..
NotReallyKnown said:
Hey guys, i'm posting here because I have a huge issue with my phone.
I think I have an idea of what caused my phone to go haywire, but i'm gonna post my phone specs:
Red Nexus 5 32gb
Rooted
Franco Kernel
4.4.2 (however, I think it may have somehow updated to 4.4.3 OTA somehow, which may be the root of the problems)
TWRP
Nandroid backup but done once i've been experiencing these problems
-The phone boots up normally and then abrubtly freezes.
-The dialogue "Unfortunately, the process com.android.systemui has stopped."
-I press ok, the screen turns black
-"Unfortunately, Update Device has stopped"
-I press ok, shortly after, both prompts pop up again repeatedly.
I literally have no way to get to the home menu, even using Safe Mode.
My main priority is to at least recover my SMS files. And obviously fix my phone..
Click to expand...
Click to collapse
reflash your rom, or flash another rom. if using stock, you can reflash the factory img or find a rooted stock rom. anyways, you DO want to update to 444, as many bugs have been fixed from 442 to 444. if yoy dont want to lose any data, grab a stock rooted rom and flash it dirty, as in dont wipe a single thing. and your phone can not update itself, only you can let it update. and with you using franco kernel, it can not flash an ota, you would have to do it manually.
simms22 said:
reflash your rom, or flash another rom. if using stock, you can reflash the factory img or find a rooted stock rom. anyways, you DO want to update to 444, as many bugs have been fixed from 442 to 444. if yoy dont want to lose any data, grab a stock rooted rom and flash it dirty, as in dont wipe a single thing. and your phone can not update itself, only you can let it update. and with you using franco kernel, it can not flash an ota, you would have to do it manually.
Click to expand...
Click to collapse
Do you mind linking me a good thread on how to dirty flash a rom? I've been looking all over and i'm getting a lot of results that simply don't work.
Edit:
Nevermind, found out how to use adb. Can you at least tell me where the SMS files are stored? I used Textra.
NotReallyKnown said:
Do you mind linking me a good thread on how to dirty flash a rom? I've been looking all over and i'm getting a lot of results that simply don't work.
Edit:
Nevermind, found out how to use adb. Can you at least tell me where the SMS files are stored? I used Textra.
Click to expand...
Click to collapse
well, theres no such thing. as most everyone will tell you the proper way is to clean flash, you wont find a dirty flashing thread. regardless, im known for my dirty flashing of everything. generally, what you do to dirty flash is make a backup in recovery first, then just flash what you need to flash, without wiping anything. the thing about dirty flashing is that you dont lose any data(while clean flashing you do).
where the sms files are stored, i have no idea. have you checked if your sms app created a file?
simms22 said:
well, theres no such thing. as most everyone will tell you the proper way is to clean flash, you wont find a dirty flashing thread. regardless, im known for my dirty flashing of everything. generally, what you do to dirty flash is make a backup in recovery first, then just flash what you need to flash, without wiping anything. the thing about dirty flashing is that you dont lose any data(while clean flashing you do).
where the sms files are stored, i have no idea. have you checked if your sms app created a file?
Click to expand...
Click to collapse
So what I should do is push the rooted stock rom somewhere into my phone and use TWRP to install it straight?
NotReallyKnown said:
So what I should do is push the rooted stock rom somewhere into my phone and use TWRP to install it straight?
Click to expand...
Click to collapse
right. adb push it to your phone, then flash it in twrp. if the dirty flash doesnt work out(chances are that it will) then you would have to wipe data(factory reset) and reflash.
simms22 said:
right. adb push it to your phone, then flash it in twrp. if the dirty flash doesnt work out(chances are that it will) then you would have to wipe data(factory reset) and reflash.
Click to expand...
Click to collapse
You are a f**king god. It worked perfectly! Thank you so much!
Why isn't Dirty Flashing suggested by most?
NotReallyKnown said:
You are a f**king god. It worked perfectly! Thank you so much!
Why isn't Dirty Flashing suggested by most?
Click to expand...
Click to collapse
because most follow older "proper" ways to flash software. and the proper way to flash, and to make sure all is working as should, is to clean flash. dirty flashing can cause issues, but its issues that are usually fixable. the problem is that most dont know that, or how to fix. 99.99% of issues caused by dirty flashing are caused by corrupt or incompatible data. where a data clearing for that particular app will usually fix. anyways, roms based on the same sourcw, and not far from what you are running, you can dirty flash. roms that have a different base than what you are running, you should factory reset first.
Dirty flashing has the potential of causing conflicts and issues. Of course it is not so bad if you back up your data. One problem though, is you might use your phone for a few weeks before the issues show up, then suddenly you are unable to backup data. So you lost a week or two of stuff.
By the way, I often dirty flash when I run into issues. After that though, it is a good idea to back everything up, wipe, and reflash everything. Limits potential issues arising and also causes of said issues.
wangdaning said:
Dirty flashing has the potential of causing conflicts and issues. Of course it is not so bad if you back up your data. One problem though, is you might use your phone for a few weeks before the issues show up, then suddenly you are unable to backup data. So you lost a week or two of stuff.
By the way, I often dirty flash when I run into issues. After that though, it is a good idea to back everything up, wipe, and reflash everything. Limits potential issues arising and also causes of said issues.
Click to expand...
Click to collapse
issues from dirty flashing do not appear weeks later, dirty flashing issues show up right away. all dirty flashing issues are caused by data, whether corrupt or incompatible. other issues are blamed on dirty flashes, but arent the real cause. issues like app fc's are the most common, and very fixable. the only issues that arent fixable are when you dirtt flash two completely different roms that are based on different sources, or different android versions. i have dirty flashed every single thing ive flashed onto my n5, since december, no issues. the only issue i had dirty flashing my n5 was dirty flashing L over rastakat. and the issue was minor. everything worked great except the status bar didnt go down all the way. why did it mess uo? because of incompatible data from rastakat with the new status bar code in L.
You are correct Simms, but it must be noted that you dirty flash the same version, for dirty flash to work. If just updating a rom it is usually fine, but if they have made a major change then it is not.
Have no tales to tell of my N5, but my Samcrap S3 (cracked the screen and she died, then I bought this bad boy ) had issues that would appear later. Maybe due to the dirty flash. Who knows, that is why I mentioned a clean flash rules that out.
Anyway, backing up everything leads to a carefree life!
My first post here is exactly as the title implies. I rooted my lg g3 us990 with kingroot(after attempting others) and have been using it for a while, working perfectly. I then got the idea to start learning about custom roms and attempting to install one.
So I used twrp and set up my recovery, I then backed up my current state. I found a rom that I assumed "should" work, CM12.1 and added it to my qeue on twrp. Starting out good.
I wiped my all options except internal storage and sd card and proceeded to flash CM12. All seemed well, it rebooted, with boot error message 1003 in the top left, on the LG boot page. Then, the cyanogenmod face came up, slightly uneven, and the boot went on for an hour. Not so good.
No biggie, I still had a backup to go back too right? Wrong. I went through the same steps to wipe memory, then restore my backup. LG screen, same error message, boot loop, CRAP.
Any help would be greatly appreciated to get my phone working again. I understand the rom not working, but why wouldnt my backup work?
Note, I am able to get into both twrp recovery and download mode.
Also, my twrp is displaying the wrong time, is that normal?
paul8m3 said:
My first post here is exactly as the title implies. I rooted my lg g3 us990 with kingroot(after attempting others) and have been using it for a while, working perfectly. I then got the idea to start learning about custom roms and attempting to install one.
So I used twrp and set up my recovery, I then backed up my current state. I found a rom that I assumed "should" work, CM12.1 and added it to my qeue on twrp. Starting out good.
I wiped my all options except internal storage and sd card and proceeded to flash CM12. All seemed well, it rebooted, with boot error message 1003 in the top left, on the LG boot page. Then, the cyanogenmod face came up, slightly uneven, and the boot went on for an hour. Not so good.
No biggie, I still had a backup to go back too right? Wrong. I went through the same steps to wipe memory, then restore my backup. LG screen, same error message, boot loop, CRAP.
Any help would be greatly appreciated to get my phone working again. I understand the rom not working, but why wouldnt my backup work?
Click to expand...
Click to collapse
Greetings and welcome to assist. I think your issue is related to a locked bootloader so unlocking it should fix it, I found this thread that might help you
https://forum.xda-developers.com/tmobile-g4/help/totally-screwed-secure-boot-1003-error-t3326495
Good Luck
Sawdoctor
sawdoctor said:
Greetings and welcome to assist. I think your issue is related to a locked bootloader so unlocking it should fix it, I found this thread that might help you
https://forum.xda-developers.com/tmobile-g4/help/totally-screwed-secure-boot-1003-error-t3326495
Good Luck
Sawdoctor
Click to expand...
Click to collapse
Thank you for the reply. I was fortunate enough to have a generous person give me a bunch of compatible roms and help me through my 'functionality' problem. Next is working on getting rid of that error message.
Hi all,
As you all know Android rolled out the new 9 pie Update on all xiaomi devices.
After updating my mi a2 lite became the crappiest phone on earth as all the bugs started appearing(phone was rebooting multiple times, image was broken, sd xcard not recognised and battery life draining fast as hell).
Because of that I decided to root my phone and install Havoc 2.0. Fair enough, I used the rom for a bit but honestly I am not really happy about it too as doesn't seem really stable at all (many functions are there but not working, the camera app is crap, the volume bar appears every time I touch the fingerprint sensor and the fingerprint lock isn't working as well). At this point I wanted to revert and get back to the stock oreo 8.1 so I booted the recovery twrp to restore the firmware backup that I did at the beginning before installing havoc but this disappeared!!!!!
Reading again the procedure i followed I noticed that one of the steps was to wipe the caches and, as the procedure was saying, the system as well(I know.... I am an idiot for relying on what the procedure said)!
Obviously this deleted my previous backup completely leaving me empty hands without any stock firmware/rom.
Is there any chance to revert back to the stock (maybe downloading all the pieces and then force flashing them?) or I am screwed?
I know, I should have followed one of your tutorial (and I am sorry for asking now for your assistance) but now I think you are the only one that can actually help me.
Best regards,
D.
manna.davide87 said:
Hi all,
As you all know Android rolled out the new 9 pie Update on all xiaomi devices.
After updating my mi a2 lite became the crappiest phone on earth as all the bugs started appearing(phone was rebooting multiple times, image was broken, sd xcard not recognised and battery life draining fast as hell).
Because of that I decided to root my phone and install Havoc 2.0. Fair enough, I used the rom for a bit but honestly I am not really happy about it too as doesn't seem really stable at all (many functions are there but not working, the camera app is crap, the volume bar appears every time I touch the fingerprint sensor and the fingerprint lock isn't working as well). At this point I wanted to revert and get back to the stock oreo 8.1 so I booted the recovery twrp to restore the firmware backup that I did at the beginning before installing havoc but this disappeared!!!!!
Reading again the procedure i followed I noticed that one of the steps was to wipe the caches and, as the procedure was saying, the system as well(I know.... I am an idiot for relying on what the procedure said)!
Obviously this deleted my previous backup completely leaving me empty hands without any stock firmware/rom.
Is there any chance to revert back to the stock (maybe downloading all the pieces and then force flashing them?) or I am screwed?
I know, I should have followed one of your tutorial (and I am sorry for asking now for your assistance) but now I think you are the only one that can actually help me.
Best regards,
D.
Click to expand...
Click to collapse
Wiping system is not what wiped your backup, your backup was stored on internal storage or on external sdcard, it does not get stored in system. The only you could have wiped the backup is if you also chose the option to wipe the internal storage when you wiped cache and system.
Factory reset and the normal wipes in TWRP do not wipe /data/media, /data/media is where your user data is stored. Only specifically choosing the option to wipe internal storage can wipe /data/media.
And you aren't an idiot for following instructions, you're an idiot for following instructions incorrectly. If you had wiped cache and system but left internal storage alone, you wouldn't be in the mess you're in.
Have you tried doing a Google search for:
"Return to stock (your model number)"
If it's available, that should find the instructions, tools and files you need.
Sent from my LGL84VL using Tapatalk
Droidriven said:
Wiping system is not what wiped your backup, your backup was stored on internal storage or on external sdcard, it does not get stored in system. The only you could have wiped the backup is if you also chose the option to wipe the internal storage when you wiped cache and system.
Factory reset and the normal wipes in TWRP do not wipe /data/media, /data/media is where your user data is stored. Only specifically choosing the option to wipe internal storage can wipe /data/media.
And you aren't an idiot for following instructions, you're an idiot for following instructions incorrectly. If you had wiped cache and system but left internal storage alone, you wouldn't be in the mess you're in.
Have you tried doing a Google search for:
"Return to stock (your model number)"
If it's available, that should find the instructions, tools and files you need.
Click to expand...
Click to collapse
Hi, first of all thanks for replying.
Interbal storage hasn't been wiped out, i am sure about it as the proceedure was saying not to do it. (I've selected just the first 3 options and internalbstorage is the 4th so I am def8nitely sure about it). Might be somewhere else then?
I did a second back up now and I see it so at this point I am not really sure where this could be!
Is 12 hours that I am searching proceedures but everything is very confusing.
manna.davide87 said:
Hi, first of all thanks for replying.
Interbal storage hasn't been wiped out, i am sure about it as the proceedure was saying not to do it. (I've selected just the first 3 options and internalbstorage is the 4th so I am def8nitely sure about it). Might be somewhere else then?
I did a second back up now and I see it so at this point I am not really sure where this could be!
Is 12 hours that I am searching proceedures but everything is very confusing.
Click to expand...
Click to collapse
Mate @Droidriven you're a monster!
I found it in data/media in the internal storage! thanks a lot mate!
I'll run it and see if all comes back as usual.
Infinite thanks!
Good to go.
Sent from my LGL84VL using Tapatalk
Droidriven said:
Good to go.
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
Do you mind me asking you one last thing?
At this point, having the original backup, I can try another custom Rom before reverting everything to Oreo.
My question are 2:
-Because you seem very driven, do you know any stable custom rom that I can run on this Xiaomi MI A2 lite?
-Do you know if I can Install the old Havoc on and purge this pie version?
Thanks again,
Davide
manna.davide87 said:
Do you mind me asking you one last thing?
At this point, having the original backup, I can try another custom Rom before reverting everything to Oreo.
My question are 2:
-Because you seem very driven, do you know any stable custom rom that I can run on this Xiaomi MI A2 lite?
-Do you know if I can Install the old Havoc on and purge this pie version?
Thanks again,
Davide
Click to expand...
Click to collapse
I don't know anything about any of the ROMs for your device, I don't have your device.
Sent from my LGL84VL using Tapatalk