Related
Facts:
Ive searched the site multiple times, cannot find the same issue elsewhere
Ive unlocked my bootloader and rooted my N1, so I know how to access the bootloader/recovery
When I hold down the rollerball and hit power to start the N1, it boots straight to the OS, not the bootloader menu
The OS is: Android 2.2, Build FRF50, Kernel [email protected] #5
The OS doesnt show a cell signal
The OS has lines through moving graphics
The OS crashes to the X graphic with the moving colors about every 30sec to 2 minutes
I can access abd-mac commands via usb, but ./adb-mac reboot recovery just reboots my phone back to the OS again
I tried http://wiki.cyanogenmod.com/index.php/RE-recovery-img
but the last step of ./adb-mac shell flash_image recovery /sdcard/recovery.img
comes back with "error opening /sdcard/recovery.img: No such file or directory
Im sure the recovery.img is on the sd card
in the gui of the OS I tried looking at the available space of the sd, and it states sd- unavailable
available space - unavailable.
Any more ideas?
I can think of three options:
boot to fastboot by holding the trackball while turning on the phone (you say this doesn't work)
boot to bootloader by holding volume down while turning on the phone
if your OS is stable enough, try installing "Quick Boot" from the market (it requires root). That app has the option to reboot to either bootloader, or recovery
just follow this guide forum.xda-developers.com/showthread.php?t=636795 no such file is because you have to put the recovery image in the root folder of the sd card in other words it should'nt be within another folder when you open and view your sd card.
slicklynice said:
just follow this guide forum.xda-developers.com/showthread.php?t=636795 no such file is because you have to put the recovery image in the root folder of the sd card in other words it should'nt be within another folder when you open and view your sd card.
Click to expand...
Click to collapse
Thanks slickynice, but recovery.img is on the root of the sd card.
pikipirs said:
I can think of three options:
boot to fastboot by holding the trackball while turning on the phone (you say this doesn't work)
boot to bootloader by holding volume down while turning on the phone
if your OS is stable enough, try installing "Quick Boot" from the market (it requires root). That app has the option to reboot to either bootloader, or recovery
Click to expand...
Click to collapse
Thanks pikipirs. vol down while booting doesnt do anything for me either. I cant access anything with market. Is there a way to manually install the "quick boot" app with abd-mac?
Try something like rom manager or quickboot and see if they can get you into recovery?
MSigler said:
Try something like rom manager or quickboot and see if they can get you into recovery?
Click to expand...
Click to collapse
Do you know if any is accessible from the explorer because my market doesnt respond.
DrBlast33 said:
Do you know if any is accessible from the explorer because my market doesnt respond.
Click to expand...
Click to collapse
Hold on, I'll find the APK for the free clockworkmod rom manager.
Actually he hasn't posted an APK, why can't you get it from market again?
My OS isnt stable enough, I have no radio, so I connect via wifi. When I go to the market, it says Loading.... and then the OS crashes to the X graphic with flying colors.... and the market is closed again.
DrBlast33 said:
My OS isnt stable enough, I have no radio, so I connect via wifi. When I go to the market, it says Loading.... and then the OS crashes to the X graphic with flying colors.... and the market is closed again.
Click to expand...
Click to collapse
Does ADB work?
Yes, adb-mac command works, but ./adb-mac reboot recovery or ./adb-mac reboot bootloader doesnt boot into the recovery or bootloader, instead it just restarts the phone back to the OS.
Thats why if I can get something to install via adb, I can do it that way, and hopefully get it to the bootloader to install a working rom.
is it stable enough to try to run an app?
amazingly trivial suggestion here, but have you attempted to reset to factory defaults from inside the system? Perhaps this will give you just enough stability to accomplish a recovery load so you can get your phone back to a happy state.
Of course, I have no idea why that would resolve your issue but nobody has suggested it yet and your situation sorta sucks
Best of luck!!
Thanks for your suggestions. Yes, it freezes up when I try to do factory defaults again. But I did a factory default before I put the bad rom on it, so its pain without any apps currently. Some apps will work like the browser for a few minutes. Not many other apps to use, since it was wiped prior.
Well, looks like Im going to send it to HTC. They said it will be $196+ to fix it. They have to replace the main board which, if its the only issue, is $196. Ill be shipping it out tomorrow. Anyone with any last suggestions before I bite the bullet on $200? I guess it beats buying the phone again for $580!
Try volume down and power to boot?
MSigler said:
Try volume down and power to boot?
Click to expand...
Click to collapse
Tried it, just boots to the OS still.
Try safe mode? Turn it off, wait for the X and the unlock icon, then hold trackball until it boots. Should say "Safe mode" in the lower left corner. Might be able to get it running stable and fix from there.
MSigler said:
Try safe mode? Turn it off, wait for the X and the unlock icon, then hold trackball until it boots. Should say "Safe mode" in the lower left corner. Might be able to get it running stable and fix from there.
Click to expand...
Click to collapse
I am able to boot to safe mode.... but Im not sure what I can do while in it that I cant do while in the OS otherwise.
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.
Yesterday I decided to update my Cm7 from 7.0.2 to 7.1.0. I erased the Data and the Cache before installing 7.1.0. I then installed the gapps and update-CM7-dalingrin-OC-emmc-042411ext4.zip so that I could overclock.
When I rebooted I first get the cyanogen mod logo the I just got the text saying android in the corner and nothing else. I rebooted 20-30 times and I never goes away.
If I hit the N while the cyanogens logo is up it boots into Encore U-boot menu, which I never installed or have seen before.
From there if I select “Boot Mode: Recovery” and then “Boot Now” but then it just goes to a blank screen.
Now I’m starting suspect that the blank screen might be the Clockwork Recovery because when I hit the N button twice it reboots as if I were in Recovery and selecting Reboot and confirm.
I tried getting into Clockwork Recovery the normal way which was to hold the power and the N button then powering it on but it doesn’t take me into it. I've also tried holding the power button with each of the volume button. No luck there either.
So first of all what did I do wrong. Second, how do I get into Clockwork Recovery and fix this?
jimvsmij said:
Yesterday I decided to update my Cm7 from 7.0.2 to 7.1.0. I erased the Data and the Cache before installing 7.1.0. I then installed the gapps and update-CM7-dalingrin-OC-emmc-042411ext4.zip so that I could overclock.
When I rebooted I first get the cyanogen mod logo the I just got the text saying android in the corner and nothing else. I rebooted 20-30 times and I never goes away.
If I hit the N while the cyanogens logo is up it boots into Encore U-boot menu, which I never installed or have seen before.
From there if I select “Boot Mode: Recovery” and then “Boot Now” but then it just goes to a blank screen.
Now I’m starting suspect that the blank screen might be the Clockwork Recovery because when I hit the N button twice it reboots as if I were in Recovery and selecting Reboot and confirm.
I tried getting into Clockwork Recovery the normal way which was to hold the power and the N button then powering it on but it doesn’t take me into it. I've also tried holding the power button with each of the volume button. No luck there either.
So first of all what did I do wrong. Second, how do I get into Clockwork Recovery and fix this?
Click to expand...
Click to collapse
You seem to mess things up.
Firstly, you failed to indicate where the CM7 currently running from.
Secondly, you force us to guess:
a. By saying this "I tried getting into Clockwork Recovery the normal way which was to hold the power and the N button then powering it on but it doesn’t take me into it." I assume you are running CM7 from uSD.
b. And from this "and update-CM7-dalingrin-OC-emmc-042411ext4.zip so that I could overclock." You are telling us that you had installed Dalingrin kernel of an eMMC version.
CM7 running from the device and not the sd card
I don't know what an eMMc is.
Good to know you're running CM7 from eMMC (referred to the internal memory)
1. Since you got the stable 7.1, you don't need to install that OLD 042411 version of Dalingrin kernel.
2. A question, how did you perform those updates? from ROM Manager or from CwMR uSD card?
This is the video that I used to show me how to initially put gingerbread cm 7.0.2 on my nook then I first got it:
http://www.youtube.com/watch?v=88qRbLLEAPQ&feature=related
And then yesterday I tried to install the CM 7.1.0 and the overclock kernal I mentioned above.
Did I brick my nook?
votinh said:
Good to know you're running CM7 from eMMC (referred to the internal memory)
1. Since you got the stable 7.1, you don't need to install that OLD 042411 version of Dalingrin kernel.
2. A question, how did you perform those updates? from ROM Manager or from CwMR uSD card?
Click to expand...
Click to collapse
I rebooted into Clockwork Recovery and installed 7.1.0 then the gapps then the overclock kernal, then rebooted.
I can't view any Youtube when at work. Speculate that clip was outdated.
NC is virtually un-brickable. Don't panic.
votinh said:
I can't view any Youtube when at work. Speculate that clip was outdated.
NC is virtually un-brickable. Don't panic.
Click to expand...
Click to collapse
Here is the Clockwork Recovery download link from the video:
http://legacyschool.us.to/nookdev/clockwork/0.7/downloads/
I don't know if it has been updated from when I did it earlier this year.
Also,
I tried putting the micro sd card back in that had the software that automatically installed the Clockwork but it didn't do anything. I would have thought that it would have tried to re-install the Clockwork recovery.
I'm at a loss on what I can try next. Does anyone know what I can try?
jimvsmij said:
I'm at a loss on what I can try next. Does anyone know what I can try?
Click to expand...
Click to collapse
Make a bootable CWR SD card http://forum.xda-developers.com/showthread.php?t=987735&highlight=recovery
Then then flash CM7 stable or the latest Nightly and once you've booted up you can use the Rom Manager to reflash your internal CWR.
I'm thinking about trying a program I looked up called auto nooter just so I can get it to do something! Does anybody think it will make it worse?
joenathane said:
Make a bootable CWR SD card http://forum.xda-developers.com/showthread.php?t=987735&highlight=recovery
Then then flash CM7 stable or the latest Nightly and once you've booted up you can use the Rom Manager to reflash your internal CWR.
Click to expand...
Click to collapse
Ok I'll try it when I get home tonight! I hope it works! Thanks!
joenathane said:
Make a bootable CWR SD card http://forum.xda-developers.com/showthread.php?t=987735&highlight=recovery
Then then flash CM7 stable or the latest Nightly and once you've booted up you can use the Rom Manager to reflash your internal CWR.
Click to expand...
Click to collapse
.
Do you know if I can use can 3.2.x.x for my nook? I got it towards the beginning when they first came out so its an older nook. I wonder because your link says that newer nooks are not compatible with can 3.0.x.x because the partitions are different. Do you know of a link that says what nooks are compatible with what cwm's?
The newer CWR is compatible with all Nooks, new and old.
joenathane said:
The newer CWR is compatible with all Nooks, new and old.
Click to expand...
Click to collapse
Thanks joenathane! I'm up and running again!
jimvsmij said:
I rebooted into Clockwork Recovery and installed 7.1.0 then the gapps then the overclock kernal, then rebooted.
Click to expand...
Click to collapse
The O/C kernel killed you. Do it again and leave that out.
My situation is this: I went through all the instructions to flash Cyanogen to my NC and started out with the 7.1 stable build. Then later I flashed again, this time to 7.2. Everything is working fine. But I'm just finding that there are little quirks to the Nook Reader for Android that make me like the stock Nook Color better. So I decided to follow the instructions to flash back to stock.
However, when I booted into CWM from my sd card, I get the menu and can scroll around in it. But none of the menu options actually work. When I select an option all I get is the black hat with the circular orange arrow icon and nothing happens. I can't get to the menu where I'm supposed to wipe data etc. The backup function doesn't work either. the So I booted back into Cyanogen then used rom manager to tell it to reboot into recovery. Same result as booting from the SD card. I can get to the menu but nothing actually works. Back in CM7.2 again I used the option in ROM manager to back up the existing ROM. It rebooted into CWM and did the backup successfully, even though backup doesn't work if I try to do it directly from CWM.
Everything still works fine from CM7.2. It just seems to be CWM that's flaky whether I boot it from the device itself or from the SD card. Sending CWM a command from inside ROM manager does work. I've tried both backups and flashing a new CM7 version from there and it works.
Is it possible to get around this by using the install update from sd functionality in ROM manager to re-flash the B&N 1.4.1 ROM?
Are you using the “n” key to select the options in CWM? The black hat with the orange arrow comes up if you are pressing the power button to try to select an option
Yes, you can flash the 1.4.1 ROM from ROM Manager, just download the file from HERE so that it will keep CWM
GMPOWER said:
Are you using the “n” key to select the options in CWM? The black hat with the orange arrow comes up if you are pressing the power button to try to select an option
Yes, you can flash the 1.4.1 ROM from ROM Manager, just download the file from HERE so that it will keep CWM
Click to expand...
Click to collapse
D'oh.....ok, I didn't know that. But I could swear I used the power button when I was originally flashing CM7. But, if I can just do it from ROM manager, that's easier anyway.
Thanks!
Edit. Question: Is there anywhere else those files can be downloaded? Firefox was telling me the download time was predicted to be over 3 hours. Then it only got through 3.3 MB before crapping out. Trying it again now and its saying I'm downloading at 10 KB/sec. Uggg. Might be easier to just go with the SD card route afterall.
ratman6161 said:
D'oh.....ok, I didn't know that. But I could swear I used the power button when I was originally flashing CM7. But, if I can just do it from ROM manager, that's easier anyway.
Thanks!
Edit. Question: Is there anywhere else those files can be downloaded? Firefox was telling me the download time was predicted to be over 3 hours. Then it only got through 3.3 MB before crapping out. Trying it again now and its saying I'm downloading at 10 KB/sec. Uggg. Might be easier to just go with the SD card route afterall.
Click to expand...
Click to collapse
I put together my own version, give this a try, LINK
GMPOWER said:
I put together my own version, give this a try, LINK
Click to expand...
Click to collapse
I eventually got one of the other links to work. Flashed back to 1.4.1 from rom manager and it works like a charm. Thanks for the hel[p.
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!