How to Create a Nandroid backup
Your Bionic needs to be rooted!
You need to download and Install the Bionic Bootstrap.
http://cvpcs.org/blog/2011-09-16/bionic_bootstrap_recovery
Go into your applications and open “Bionic Bootstrap.”
Click on Bootstrap Recovery
You will see “Success!” tap OK
Now hit “Reboot Recovery.”
Your phone will boot into CWM-base Recovery (Volume is equal to UP and DOWN and Power is equal to Select/Enter/Ok/"DO IT, DO IT NOW")
Using your volume up/down keys, scroll down to “backup and restore” and press the power button.
Highlight "Backup" and press the power button button and the backup will begin.
Once complete highlight “reboot system now” and press the power button to reboot.
You have just created your first nandroid backup!
***Should you ever need to restore to this backup, simply boot into recovery like you just did, scroll down to “backup and restore” and this time highlight “restore” instead of “backup” and find your back up to restore.***
WHAT YOU DO TO YOUR PHONE IS YOUR FAULT!
theproj said:
How to Create a Nandroid backup
Your Bionic needs to be rooted!
You need to download and Install the Bionic Bootstrap.
http://cvpcs.org/blog/2011-09-16/bionic_bootstrap_recovery
Go into your applications and open “Bionic Bootstrap.”
Click on Bootstrap Recovery
You will see “Success!” tap OK
Now hit “Reboot Recovery.”
Your phone will boot into CWM-base Recovery (Volume is equal to UP and DOWN and Power is equal to Select/Enter/Ok/"DO IT, DO IT NOW")
Using your volume up/down keys, scroll down to “backup and restore” and press the power button.
Highlight "Backup" and press the power button button and the backup will begin.
Once complete highlight “reboot system now” and press the power button to reboot.
You have just created your first nandroid backup!
***Should you ever need to restore to this backup, simply boot into recovery like you just did, scroll down to “backup and restore” and this time highlight “restore” instead of “backup” and find your back up to restore.***
WHAT YOU DO TO YOUR PHONE IS YOUR FAULT!
Click to expand...
Click to collapse
Awesome work! Thank you! We can now do backup and restore!
Seeing that this is bootstrap recovery... how can you restore these backups if you can't get into android... like stuck in bootloop etc?
Someone please correct me if I am wrong but if you are stuck in a boot loop you would have to return yourself to stock, root, install Bionic Bootstrap and then restore
going to try that right now, i'm not 100% where the nandroid stored, too, we will see if its sd card or on internal once i restore to stock, will let you know.
Edit: im stuck at Dual Core logo, won't even start to boot android, guess I will go home in a lil bit and run the fast boot restore system files.
Should be under sdcard-ext\clockworkmod\backup
---------- Post added at 09:26 AM ---------- Previous post was at 09:25 AM ----------
Sounds like you need to return to stock like I posted above. What did you do that got you in a bootloop? Just so that I dont do it to myself.
I tried the modified android.policy.jar from adrynylene to be able to use volume buttons to wake the phone. It hasn't been tested, followed directions exactly, so yeah got a backup at least.
My first time dealing with this locked bootloader mess too, not as easy breasy as other phones with custom recoveries, but better than nothing... (a guide for us new to locked bootloader recoveries and restoring nandroid could be an idea for this thread?)
I would agree that will be a good idea. If you figure it out write one up or let me know how and I will write it up and link it in. I would like to learn some more of the technical/advanced side of things.
JimmyHACK said:
I tried the modified android.policy.jar from adrynylene to be able to use volume buttons to wake the phone. It hasn't been tested, followed directions exactly, so yeah got a backup at least.
My first time dealing with this locked bootloader mess too, not as easy breasy as other phones with custom recoveries, but better than nothing... (a guide for us new to locked bootloader recoveries and restoring nandroid could be an idea for this thread?)
Click to expand...
Click to collapse
Have you tried to restore your Nandroid Backup that you made through CWM?
You should be able to do a battery pull and then boot into recovery holding volume down and power on. Then restore your back-up through CWM
he is stuck in a loop so he will have to restore to stock, root, and then nandroid restore. I believe he will be the first to restore lol.
I believe this is because of the locked bootloader and the requirement of Bootstrap to be launched and have it write instructions to boot into recovery on reboot.
mzimand said:
Have you tried to restore your Nandroid Backup that you made through CWM?
You should be able to do a battery pull and then boot into recovery holding volume down and power on. Then restore your back-up through CWM
Click to expand...
Click to collapse
Being a bootstrapped CWM, you cannot cold boot into CWM, only stock recovery, so cant restore.... have to get into android and run the bootstrap to reboot into CWM so far what i have seen.. unless you know a way to cold boot into CWM, which would be awesome but I don't think these locked bootloader devices do it.
theproj said:
WHAT YOU DO TO YOUR PHONE IS YOUR FAULT!
Click to expand...
Click to collapse
Dude.... this is America.... its always someone elses fault
I will change the warning to
WHAT YOU DO TO YOUR PHONE IS TauntingBull's FAULT!
The 2nd init recovery being worked on by Hashcode is better than the bootstrap recovery in a couple critical ways. One being that the way its triggered in the boot menu allows you to access it even from a bootlooping phone. This is an obvious advantage if something unexpected happens.
Second, it makes a more complete backup including the boot.img.
In most cases, because we have a locked bootloader and we cannot run an unsigned boot.img this isn't important, but that may change.
The 2nd init version is not ready quite yet though and both provide the critical ability to backup and restore a nandroid. I have been using this version since he first created it and think it shows promise because of the boot menu trigger innovation.
More options makes for a healthier development community IMO!
Im not a english native speaker so in my understanding this not work right I was about to try it but after reading whole tread is my understanding please can you just tell me if works or not thanks
Sent from my DROID BIONIC using XDA App
denpad2010 said:
Im not a english native speaker so in my understanding this not work right I was about to try it but after reading whole tread is my understanding please can you just tell me if works or not thanks
Sent from my DROID BIONIC using XDA App
Click to expand...
Click to collapse
Yes this works and is safe. Another option that maybe an improvement is coming soon.
Both work and both are based on Clockworkmod recovery.
[Q] What'd I do wrong?
I tried to create a backup and received the following errors:
No /sdcard/.android_secure found. Skipping backup of applications on external storage.
No sd-ext found. Skipping backup of sd-ext.
Any ideas what this means and how to fix the apparent problem?
Thanks.
K back and going, used teh minimal fxz, reroot, rebootstrap, reboot into cwm then restored nandroid
can't wait for official 2nd_init recovery version
Yay security!
Underwater Mike said:
I tried to create a backup and received the following errors:
No /sdcard/.android_secure found. Skipping backup of applications on external storage.
No sd-ext found. Skipping backup of sd-ext.
Any ideas what this means and how to fix the apparent problem?
Thanks.
Click to expand...
Click to collapse
If you don't have an .android_secure folder in the root of your SD card, not a problem.
If you have not created an ext partition (a Linux file system partition) used by Darktremor's Apps2SD (http://forum.xda-developers.com/showthread.php?t=715938), not a problem.
FYI/FWIW - don't know if his script will work on a Bionic, I've got an EVO, a coworker has the DB. Just an innocent bystander here...
Related
First off, I'm very sorry as I know by now you are mostly sick of noobs but I tried to figure out what I'm doing wrong on my own and am just stuck.
So here it goes:
I rooted my DROID 2.2.1 with superone click. Did everything I've read to do and tried to install bugless beast ROM. Tried to boot into recovery but I got the triangle exclamation point screen on reboot. Tried to install the ROM via ROM manager and the same thing happened. I was then able to get to clockwork recovery through ROM manager somehow and installed the ROM. At this point, I got the startup screen for bugless beast and it just looped. I restored back to Froyo and cannot get back to recovery boot because that $#%% screen with the triangle exclamation is killing me.
What should I do now? Or am I just too noob at this and should go back to the Matrix lifestyle of "ignorance is bliss" by unrooting?
Thanks again.
Matt
prepare to kick yourself in the head ^^
- the "triangle exclamation" pictures is EXACTLY the point where you can enter Recovery.
here´s how: press "volumeUP" and the "camera" button at the same time.
then navigate through the recovery (if you have a custom recovery installed, you´ll need to choose "apply update.zip" to load the custom/open recovery on the first screen) using your D-Pad.
Thank you for the button combo to get where I need to go. Now does anyone know why when I load a ROM, the start up screen just loops forever? I have tried loading cyanogen6 and bugless beast now both with the same issue.
nevermind...I'm stupid. Sorry. Needed to wipe data. But how do I get all my data back? If I restore data through nandroid then I just get boot loops again.
I haven't used rom manager before.
So i would recommend you to use open recovery to do flashing or rooting.
Have u flash a vulnerable recovery sbf ??
If yes, you can go to recovery mode and select "apply update".
Then the open recovery is applied.
By using OR, you can root phone and apply any updates you want.
Sent from my A853 using XDA App
matty1098 said:
nevermind...I'm stupid. Sorry. Needed to wipe data. But how do I get all my data back? If I restore data through nandroid then I just get boot loops again.
Click to expand...
Click to collapse
Boot loops??
Do u mean your phone keep rebooting??
Sent from my A853 using XDA App
Ok, so after using clockwork rom manager on my nook color and seeing how convenient it was, I thought, "hey maybe this would be good on my milestone." WRONG. I flashed the clockwork recovery (they even had an option for milestone) and when I rebooted into recovery from the software (either in rom manager or the reboot power option) it just rebooted straight into android. When I held the power and camera keys, it just took me to bootloader.
Under rom manager, there was also an option to flash the RA recovery, but that didn't seem to help (exact same behavior as clockwork recovery).
I'm currently running the CM7 mod and prior to this fiasco, I was using RA 1.7 (pretty sure). edit: RA 1.7 was my girlfriend's HTCmagic, I just remembered that I would have had some version of openrecovery on this phone.
So, I guess my question is, what are my next steps here? I'd really like to stop flying without a recovery. My only shred of an idea was to flash a stock image from rsdlite and set my milestone all the way back to stock and then reroot and re everything, but if someone has a better idea, I'd be very open to that as my plan seems like a big hassle.
A) not really the place for this post but anywa
B) you should beable to just flash the Vulnerable recovery http://android.doshaska.net/rootable then you can install a recovery from this forum thats for our phone!
Apologies, I didn't mean to step on any toes. Could a mod please recategorize this thread.
I will check out that link and report back if I need further assistance. Although, if that's a surefire way to fix my problem, I should be fine. Thank you for your fast (and succinctly informative) reply.
Tyfighter said:
Apologies, I didn't mean to step on any toes. Could a mod please recategorize this thread.
I will check out that link and report back if I need further assistance. Although, if that's a surefire way to fix my problem, I should be fine. Thank you for your fast (and succinctly informative) reply.
Click to expand...
Click to collapse
Quite alright if you have any more problems feel free to just PM me
Check this thread:
http://forum.xda-developers.com/showthread.php?t=1139120
Well, the good news is, that I flashed the vulnerable recovery and I'm able to boot into recovery. The bad news is, it only lasts for a few seconds. I see the standard recovery icon and then a bar fills up and then my phone reboots into android. From what you said, I take it that there's another step in here where I take another file from the forums and then install that as well. Is that just through RSD lite then?
Tyfighter said:
Well, the good news is, that I flashed the vulnerable recovery and I'm able to boot into recovery. The bad news is, it only lasts for a few seconds. I see the standard recovery icon and then a bar fills up and then my phone reboots into android. From what you said, I take it that there's another step in here where I take another file from the forums and then install that as well. Is that just through RSD lite then?
Click to expand...
Click to collapse
Ok so you need to take an open recovery for example http://forum.xda-developers.com/showthread.php?t=1091787 and extract it to the root of your sdcard so you have a update.zip file and openrecovery folder.
Then boot into recovery and press the volume up and camera button and a menu should come up.
Then select the 'flash update.zip' and this should 'boot' you into the custom recovery, sadly because of the looked bootloader we must do this everytime we wish to boot into recovery
Okay, I have that file, or one similar, from when I originally had started using custom roms (and updated/changed them etc.).
The problem is that before, when I'd go into recovery, it would have the icon of the phone out of the box with the exclamation mark or whatever, and it would stay there indefinitely.
Now, it only stays for a few seconds before rebooting into android. A little bar appears, fills up, then reboot. Doing the volume up + camera combo only serves to expedite this process (i.e. reboots as soon as I press it).
zacthespack said:
Ok so you need to take an open recovery for example http://forum.xda-developers.com/showthread.php?t=1091787 and extract it to the root of your sdcard so you have a update.zip file and openrecovery folder.
Then boot into recovery and press the volume up and camera button and a menu should come up.
Then select the 'flash update.zip' and this should 'boot' you into the custom recovery, sadly because of the looked bootloader we must do this everytime we wish to boot into recovery
Click to expand...
Click to collapse
what your doing (power + camera) is meant to put you into the bootloader mode... to get into recovery, hold 'x' on the physical keyboard and then hold the power button. This will get you into recovery. Hope this helps.
~D
are you sure that you did in fact flash the vulnerable bootloader, and not a newer, non-vulnerable one? sounds like that.. exploit fails, system reboots. also, if you are running an original rom right now, it does check the bootloader every reboot and flashes the non-vulnerable one!
Tyfighter said:
Okay, I have that file, or one similar, from when I originally had started using custom roms (and updated/changed them etc.).
The problem is that before, when I'd go into recovery, it would have the icon of the phone out of the box with the exclamation mark or whatever, and it would stay there indefinitely.
Now, it only stays for a few seconds before rebooting into android. A little bar appears, fills up, then reboot. Doing the volume up + camera combo only serves to expedite this process (i.e. reboots as soon as I press it).
Click to expand...
Click to collapse
I'm a bit confused with how you're getting into Recovery mode, but the way to enter recovery is to hold Power + X, then Camera + Vol Up when you see the Motorola Logo.
I'm getting into recovery the same way I always have Power+camera then volumeup+camera. Power+DpadUp is how I've been getting into bootloader. Power+X actually yields nothing, just a regular boot.
Unless the file hosted on the site that was linked earlier in the thread is a newer, nonvulnerable recovery then, yes, I'm sure I flashed vulnerable recovery. I'm going to attempt to flash again. Just to see if maybe that's the issue.
I'm pretty sure I'm seeing it at least attempt to enter recovery, which is a step up from before (before being that it just went to bootloader). Because I'm seeing the image that displays in the recovery menu, but then it brings up a progress bar (which I never saw before) and when that fills up (in about 2.5 seconds), that's it. Reboot.
Thanks everyone, for all the help though.
EDIT: Despite RSD lite saying that the process as a success, the reflash did nothing.
Tyfighter said:
I'm getting into recovery the same way I always have Power+camera then volumeup+camera. Power+DpadUp is how I've been getting into bootloader. Power+X actually yields nothing, just a regular boot.
Unless the file hosted on the site that was linked earlier in the thread is a newer, nonvulnerable recovery then, yes, I'm sure I flashed vulnerable recovery. I'm going to attempt to flash again. Just to see if maybe that's the issue.
I'm pretty sure I'm seeing it at least attempt to enter recovery, which is a step up from before (before being that it just went to bootloader). Because I'm seeing the image that displays in the recovery menu, but then it brings up a progress bar (which I never saw before) and when that fills up (in about 2.5 seconds), that's it. Reboot.
Thanks everyone, for all the help though.
Click to expand...
Click to collapse
Where did you get the VR sbf? android.doshaska.net/rootable ?
Yep, that's the one.
EDIT: Finally got up the guts to load the official Telus sbf into RSD lite and pull the trigger. It seems like this is probably beyond salvage now. Once again, many thanks to everyone, and if all goes well, I hope to only be in the ranks of the unrooted/unmodded for a few minutes.
EDIT the second: Okay, so flash to stock went perfectly. Everything works, including recovery, but not openrecovery. I can get to the menu to flash the .zip, but it fails the esignature check. Which I'm assuming points to Vulnerable recovery not flashing correctly or perhaps my file is corrupt, or maybe something more exotic and exciting. I flashed SHOLS_U2_03.11.0 if that's relevant.
For those interested, everything is up and functional again.
I had to first flash back to stock, then flash the vulnerable recovery located at http://modmymobile.com/forums/downloads.php?do=file&id=28089 , then the standard, boot to recovery, blah blah blah, install a new rom.
Let this be a lesson to the rest of you; Clockwork Rom Manager does not, I repeat, does NOT seem to work on our milestones. Which is a real shame...
I realize this is a double post, but I'm just so darned jubilant to be able to update my rom again.
Well, i wanted to change my rom, CM 7.2, with DjangoManouche 1.2 and used the rom below..i backed up, and when i started flashing, it said that"this is not a ROM"..i..kind of panicked and after a minute, when i seen "nothing moves" i removed the battery. When i tried to start the phone, it only shows the LG logo..but does not boot(i waited for just 1-2 minutes..). I hope someone could help me.
xdafileserver.nl/Files/LG/Optimus%202x%20(P990)/ROMS/DjangoManouche%20ROM/1.2/1.2ROMS/DjangoManouche1.2WipeEXT3Stock.zip
Mitzu' said:
Well, i wanted to change my rom, CM 7.2, with DjangoManouche 1.2 and used the rom below..i backed up, and when i started flashing, it said that"this is not a ROM"..i..kind of panicked and after a minute, when i seen "nothing moves" i removed the battery. When i tried to start the phone, it only shows the LG logo..but does not boot(i waited for just 1-2 minutes..). I hope someone could help me.
xdafileserver.nl/Files/LG/Optimus%202x%20(P990)/ROMS/DjangoManouche%20ROM/1.2/1.2ROMS/DjangoManouche1.2WipeEXT3Stock.zip
Click to expand...
Click to collapse
I recall reading something about using NVFlash to force the stock rom on and allowing to recover from a bricking.
I'll defer to someone with experience in fixing bricked phones though.
Thank you...now..it wont even start, even when i plug-in the charger..it had pretty low battery..i am pretty ducked..
You have to reflash it with KDZ recovery method. Look up google and you'll get it working. I did this the first time too (what a bad joke to say "this is not a ROM")...
I'm sure you can still enter Cwm if you hold down volume- while pressing power button until it the Cwm menu appears.
Sent from my Optimus 2X using xda premium
First of all, don't worry, O2X is pretty unbrickable...at least in the level you're messing with it!
If you have recovery installed, you should be able to reboot into recovery : press and hold vol down button, then power button until you see blue halo of LG. before that, download another ROM and put it in your external SDcard. Flash that ROM.
You can also download and flash the original firmware of LG by using smartflash. You can find those in ANDROID DEVELOPMENT section!
Also check KDZ recovery!!
Thank you..it worked with recovery mode..i had back-ups. I got a bit scared because when i pressed vol_dwn+ shut down button..after i release the 2nd button, it turned off...but i menaged to make it. Again, thank you for help.
====================
well, today i tried again to install a new rom(temasek's cm7 last build)..but i couldn't..after it is installed it get's into boot and stays like that..i tried to AOKP and it worked..my backup also worked...i just can't get it, why these roms won't work?
Mitzu' said:
well, today i tried again to install a new rom(temasek's cm7 last build)..but i couldn't..after it is installed it get's into boot and stays like that..i tried to AOKP and it worked..my backup also worked...i just can't get it, why these roms won't work?
Click to expand...
Click to collapse
The common mistake for new people is that they restore entire nandroid backup after flashing ROM. CWM doesn't have option to backup DATA only, so you have to restore DATA from nandroid backup using Titanium Backup etc.
Try this:
1. Restore into fully functioning ROM(+data) if you don't have already
2. Reboot to recovery
3. Format /system
4. Flash new ROM
5. Clear cache and dalvik cache
6. Check if phone successfully boots
7. Flash Gapps if needed.
8. DO NOT DO ANY RESTORES AFTER STEP 1!!
9. If it doesn't work out, try another ROM. There may be some error with the file!!
I installed the beats audio installer and things seemed to be working ok, except that my phone volume was either lower than expected or overly loud where the external speaker had distortion. So I opened the app and clicked uninstall from within it. Afterwards I rebooted my phone as it said and now it's stuck in a bootloop. My brother rooted my phone for me when I went home for a visit for me. I'm not root or phone savvy. I live in South Florida and I can't make the 12 hour drive back there anytime soon. How do I fix this? I had performed a nandroid backup but I noticed my external storage was 100% full after I did that a few times. So I went into storage in settings and deleted the clockwork mod stuff sitting at 6.86 gigs. That must have been the backup in there I know. Now with no backup I did a factory reset, still a bootloop. Phone is rooted still. I'm thinking maybe the audio drivers were damaged. Please help how do I fix this? Thanks!
darinthereal said:
I installed the beats audio installer and things seemed to be working ok, except that my phone volume was either lower than expected or overly loud where the external speaker had distortion. So I opened the app and clicked uninstall from within it. Afterwards I rebooted my phone as it said and now it's stuck in a bootloop. My brother rooted my phone for me when I went home for a visit for me. I'm not root or phone savvy. I live in South Florida and I can't make the 12 hour drive back there anytime soon. How do I fix this? I had performed a nandroid backup but I noticed my external storage was 100% full after I did that a few times. So I went into storage in settings and deleted the clockwork mod stuff sitting at 6.86 gigs. That must have been the backup in there I know. Now with no backup I did a factory reset, still a bootloop. Phone is rooted still. I'm thinking maybe the audio drivers were damaged. Please help how do I fix this? Thanks!
Click to expand...
Click to collapse
I don't think the audio drivers were damaged. A factory reset wipes the /data partition, which is where all the personal data is stored, but it does not touch the /system partition, which is probably where the Beats Audio installs/modifies files, since it probably needs root (I'm just assuming, don't know which app that is nor what it does).
Since you have Clockwork Mod (CWM), I'm assuming your recovery is still working, right? When you start up your phone, the LED should turn on (either blue or purple), and then you should press volume up/down to enter recovery. Do you have an external SD card?
yes I have an external sd card
Antiga Prime said:
I don't think the audio drivers were damaged. A factory reset wipes the /data partition, which is where all the personal data is stored, but it does not touch the /system partition, which is probably where the Beats Audio installs/modifies files, since it probably needs root (I'm just assuming, don't know which app that is nor what it does).
Since you have Clockwork Mod (CWM), I'm assuming your recovery is still working, right? When you start up your phone, the LED should turn on (either blue or purple), and then you should press volume up/down to enter recovery. Do you have an external SD card?
Click to expand...
Click to collapse
Thanks for replying, I'm crushed. When I boot the phone the led goes red then purple. If I hold down volume down and power the purple becomes yellow then it goes into recovery but I have absolutely nothing to backup from. If I reboot it bootloops.
also...
darinthereal said:
Thanks for replying, I'm crushed. When I boot the phone the led goes red then purple. If I hold down volume down and power the purple becomes yellow then it goes into recovery but I have absolutely nothing to backup from. If I reboot it bootloops.
Click to expand...
Click to collapse
The phone says there is no OS now and when I power up it's stuck on the Sony logo. At this point am I able to install a custom rom say a stable version of Kit Kat? If so, where do I find one and how do I install it? I don't know how to get into download mode I'm afraid to because I don't want to hard brick my phone. Thanks!
darinthereal said:
The phone says there is no OS now and when I power up it's stuck on the Sony logo. At this point am I able to install a custom rom say a stable version of Kit Kat? If so, where do I find one and how do I install it? I don't know how to get into download mode I'm afraid to because I don't want to hard brick my phone. Thanks!
Click to expand...
Click to collapse
Ok, since you're talking about custom ROMs, I'm assuming you have an unlocked bootloader. You won't hardbrick your phone unless you mess up real bad, although I am wondering how on earth you ended up with "no OS". That would only happen if you wiped the /system partition. Here's what you're going to do:
1.- Download the links number 1,3 and 4 from this post.
2.- Connect your SDcard to your computer with a USB adapter or an SD adapter, and copy all those downloaded files to your external SD card.
3.- Once that is done, put the SDcard back in your phone, and turn it on and enter recovery.
4.- Navigate recovery with volume buttons up/down and Power button for enter, and select the "Wipe Data" option, which is the same as a Factory Reset (just for good measure, since you already did this); it will ask you to confirm the operation, select "Yes".
5.- Do the same with "Wipe Cache".
6.- Go to "Install ZIP from SDcard1", and, with vol +/- navigate to the file you downloaded in number 1 from the link above (filename should be "LT29i_Rockers_X_ROM_v1.2_03292014-signed.zip"), and press the Power button to confirm that you want to flash that file, then confirm with "Yes".
7.- Once that completes, do the same for the file from number 3 (filename should be "LT29i_9.2.A.1.199_kernel.zip").
8.- Finally, do the same with the file from number 4 (filename should be "UPDATE-SuperSU-v1.94.zip").
9.- Reboot your phone.
It should power up now, and if you have any doubts regarding the procedure, post back and/or read through the original thread here.
I just posted how to do method 2, described in the original link.
EDIT: In my opinion, there is no "stable" version of Kitkat. FXP has a CM11 ROM, but it has kernel issues regarding battery life; if you can live with a battery not lasting more than 7 - 9 hours, maybe you'd want to try that, but I wouldn't recommend it.
http://fxpblog.co/qualcomm-krait-200-family-1st-gen/sony-xperia-tx/
Antiga Prime said:
Ok, since you're talking about custom ROMs, I'm assuming you have an unlocked bootloader. You won't hardbrick your phone unless you mess up real bad, although I am wondering how on earth you ended up with "no OS". That would only happen if you wiped the /system partition. Here's what you're going to do:
1.- Download the links number 1,3 and 4 from this post.
2.- Connect your SDcard to your computer with a USB adapter or an SD adapter, and copy all those downloaded files to your external SD card.
3.- Once that is done, put the SDcard back in your phone, and turn it on and enter recovery.
4.- Navigate recovery with volume buttons up/down and Power button for enter, and select the "Wipe Data" option, which is the same as a Factory Reset (just for good measure, since you already did this); it will ask you to confirm the operation, select "Yes".
5.- Do the same with "Wipe Cache".
6.- Go to "Install ZIP from SDcard1", and, with vol +/- navigate to the file you downloaded in number 1 from the link above (filename should be "LT29i_Rockers_X_ROM_v1.2_03292014-signed.zip"), and press the Power button to confirm that you want to flash that file, then confirm with "Yes".
7.- Once that completes, do the same for the file from number 3 (filename should be "LT29i_9.2.A.1.199_kernel.zip").
8.- Finally, do the same with the file from number 4 (filename should be "UPDATE-SuperSU-v1.94.zip").
9.- Reboot your phone.
It should power up now, and if you have any doubts regarding the procedure, post back and/or read through the original thread here.
I just posted how to do method 2, described in the original link.
EDIT: In my opinion, there is no "stable" version of Kitkat. FXP has a CM11 ROM, but it has kernel issues regarding battery life; if you can live with a battery not lasting more than 7 - 9 hours, maybe you'd want to try that, but I wouldn't recommend it.
http://fxpblog.co/qualcomm-krait-200-family-1st-gen/sony-xperia-tx/
Click to expand...
Click to collapse
YES the bootloader is unlocked my brother did it when he rooted it back home but he's not familiar with many of the custom roms. THANKS! I'm going to try this. I erased the OS last night. Before all of this I installed One Click Scroll from GooglePlay. It worked perfectly but it install TeamWin recovery on my phone and it's still there. I'm not familiar with it at all, but it seems to work perfectly on the device. Ok I'll let you know how it goes thank you even if this doesn't work!
darinthereal said:
YES the bootloader is unlocked my brother did it when he rooted it back home but he's not familiar with many of the custom roms. THANKS! I'm going to try this. I erased the OS last night. Before all of this I installed One Click Scroll from GooglePlay. It worked perfectly but it install TeamWin recovery on my phone and it's still there. I'm not familiar with it at all, but it seems to work perfectly on the device. Ok I'll let you know how it goes thank you even if this doesn't work!
Click to expand...
Click to collapse
Well, directions still apply to TWRP; wipe /data and /cache, flash files in the order posted previously, then reboot. Good luck.
I love you!
darinthereal said:
yes the bootloader is unlocked my brother did it when he rooted it back home but he's not familiar with many of the custom roms. Thanks! I'm going to try this. I erased the os last night. Before all of this i installed one click scroll from googleplay. It worked perfectly but it install teamwin recovery on my phone and it's still there. I'm not familiar with it at all, but it seems to work perfectly on the device. Ok i'll let you know how it goes thank you even if this doesn't work!
Click to expand...
Click to collapse
i love you thank you how do i thank matt?!!!!!!!!!
darinthereal said:
i love you thank you how do i thank matt?!!!!!!!!!
Click to expand...
Click to collapse
Glad to be of help. If you must, just clicking on the "Thanks" button on a post is good, that's what it's for. And you'll have to probably find one of matt's posts too (don't know who you're talking about) and do the same, I guess.
THANKS!
Where is the thanks button? Lol
darinthereal said:
Where is the thanks button? Lol
Click to expand...
Click to collapse
Under each post, left side of the screen.
THANKS!
darinthereal said:
i love you thank you how do i thank matt?!!!!!!!!!
Click to expand...
Click to collapse
JUST CLICKED EVERY THANKS BUTTON THAT I COULD FIND THANK GOD FOR YOU! I had to come to my laptop the thanks button don't show in my mobile boat browser weird. Again thank you dearly Antiga Prime, cool name btw!
First & Foremost, this is my first time posting on here. So my sincerest apologies if I shouldnt be posting here. I am also somewhat new at rooting so again, I'm sorry. I am going on over 48 hours trying to resolve this myself but to no avail....
My situation is...
I recently rooted my Note 3 N900A by downgrading to KK and then updated to Lollipop 5.0. I then wanted to play around and download some different custom roms and just do some exploring around with my new rooted phone as this was really the first time doing so (I'm sure people like myself (noob) are annoying to a lot of you experienced people!) ... but before doing so... I wanted to make a backup of my phone. So using SafeStrap (TWRP v2.7.1.0)... I did a complete backup of my phone. I included all the partitions that SafeStrap listed . So i backed up the DATA, CACHE, and SYSTEM. However, normally I would have saved the backup to an SD card.. but the only one I had currently in my possession was full. So... I saved the backup to my internal storage.. which im hoping wasnt my mistake in causing this problem i am dealing with... I just figured once i saved the backup to my internal storage.. I could then later.. go back and save it to my computer or another SDcard. So i saved the backup to my internal storage. Well, the backup completed... no errors appeared. Even said the backup was successful and for me to reboot. Which i did... but then it never actually booted up. It would shutdown... restart... the screen where it says Safestrap: Disabled... and then below that is... the picture of that crazy lookin dude on it.. and then on each of the bottom corners its says... Recovery (on the left) and on the right bottom side it says CONTINUE... and then i also believe it mentions something about how in 10 seconds the system would reboot if nothing was pressed. Well no matter what I press or DON'T press... either Safestrap would come back up if I press the left bottom button that says RECOVERY. Ya know.. the one where it has those 8 boxes that say, Boot Options, Install, Backup, Restore, Mount, Wipe, Advanced, and Reboot... or if I dont hit anything or if I hit the bottom right button that says CONTINUE... then the ANDROID RECOVERY MODE screen would appear. I mean i honestly don't know what to do. Now, i can navigate to the ADVANCED button in Safestrap and then File Manager and see the backup that I made in the TWRP file. But I dont know what else to do to get my phone to boot back up like it normally should. Please anyone that could help... words can't describe how appreciative i would be!!!
I'm not sure which custom ROM you wanted to flash but the n900a has a locked bootloader and can only be flashed with a custom ROM that is based on a stock ROM.
This may help: https://forum.xda-developers.com/note-3-att/general/update-procedure-lollipop-5-0-oc1-t3063760