Hi, I am new to the forum. And very new to rooting phone. And due to my lack of knowledge, here's the problem that I have as a result:
I have an UNFLASHABLE GSM unlocked galaxy nexus gt-i9250. Had it successfully rooted two days after I had it 3 weeks ago. I have flashed MIUI via CWM premium edition and it worked fine. I recently flashed AOKP Build 32 with the latest Leankernel baseband xx66 and have been running it fine for 4 days until now.
I just flashed [Amoled BLUE 2.2 for AOKP build 32] and stuck on boot loop for 2 hours now.
I made NANDROID of my rooted stock, but the problem is that I DID NOT have it saved on my Galaxy Nexus. What to do??? Please help.
You're fine buddy.
Boot into CWM...
(Power phone off by pulling battery. Power on with power+volume up+volume down)
Select the recovery option.
Wipe data (factory reset)
Flash ANY rom.
You'll boot right up.
Now move your nandroid to your phone and restore.
Edit:
Oh, and check my sig.
The second and third posts may be useful to you.
Thanks. I did everything you mentioned and still stuck in the AMOLED Blue theme anime boot loop.
So, another question that arises is how do I flash rom when I can't get past the boot loop with no NANDROID or backups stored in my Nexus?
muasxees said:
Thanks. I did everything you mentioned and still stuck in the AMOLED Blue theme anime boot loop.
So, another question that arises is how do I flash rom when I can't get past the boot loop with no NANDROID or backups stored in my Nexus?
Click to expand...
Click to collapse
You didn't do what I mentioned if you're asking how to flash the rom.
Jubakuba said:
Download the rom you'd like to try on your device.
Most roms also require you to install "gapps" as well.
You can find the correct ones for the rom you're using in the rom thread.
Make sure the Rom and Gapps are on your SD card.
Boot into ClockworkMod Recovery by turning your device completely off. Hold volume up, volume down, and power until the green Android with the open chest is displayed. Navigate to "Recovery Mode" with the volume buttons and select using the power button.
Remember to have a recent nandroid before continuing!
Navigate to "wipe data/factory reset" and select it. Select "yes."
Wait for the process to complete. This may take some time. Be patient!
Once complete: Navigate to "Install Zip from SD card" and "Choose zip from SD card."
Find the rom's .zip and install it. Once that completes install any applicable gapps' .zip.
Select the "Reboot" option.
Congratulations! Your phone should now boot into the custom rom!
Follow the prompts to re-activate your phone.
Click to expand...
Click to collapse
This post may help as well...
http://forum.xda-developers.com/showpost.php?p=23229578&postcount=3
It describes getting your files transferred to your phone.
But if you have a rom .zip on there you don't need this.
I didn't asked for how to flash a rom. I asked how to bypass the boot loop. Argh...
Okay, I flashed Amoled blue for AOKP build 32. I get stuck on boot loop anime after flashing it via CWM. Yes, I did a cavlik cache wipe before the flash.
But I'm stuck on boot loop, why?
muasxees said:
I didn't asked for how to flash a rom. I asked how to bypass the boot loop. Argh...
Okay, I flashed Amoled blue for AOKP build 32. I get stuck on boot loop anime after flashing it via CWM. Yes, I did a cavlik cache wipe before the flash.
But I'm stuck on boot loop, why?
Click to expand...
Click to collapse
And I'm telling you how, mate.
Don't flash the theme.
Flash a ROM.
The theme isn't a full system...which is what you need.
And you need to wipe data.
Edit:
I'll take it by your lack of response that this fixed it.
You're welcome.
Jubakuba said:
And I'm telling you how, mate.
Don't flash the theme.
Flash a ROM.
The theme isn't a full system...which is what you need.
And you need to wipe data.
Edit:
I'll take it by your lack of response that this fixed it.
You're welcome.
Click to expand...
Click to collapse
I've added a thanks as the op may have missed it
Sent from my Galaxy Nexus using XDA
My phone is back to running Stock Android 4.0.4 ICS via Odin.
killyouridols said:
I've added a thanks as the op may have missed it
Sent from my Galaxy Nexus using XDA
Click to expand...
Click to collapse
Added a second thanks.
Related
Need some help. I have a Verizon Galaxy Nexus and did bootloader and rooted my phone. Yeah!! Tried to install JellyBean and ran into a problem. The animation of Jellybean is locked what do I do? Need some serious help. I am able to get to Fastboot mode.
coachv said:
Need some help. I have a Verizon Galaxy Nexus and did bootloader and rooted my phone. Yeah!! Tried to install JellyBean and ran into a problem. The animation of Jellybean is locked what do I do? Need some serious help. I am able to get to Fastboot mode.
Click to expand...
Click to collapse
The animation is locked? I don't understand what you mean. Are you stuck at the boot logo (Google screen) or the boot animation (flashing X)? Either way, you can just go into your custom recovery, wipe data, and try flashing again if you are waiting on it to boot for that long. Some users have experienced waiting 5 minutes before it actually started up.
Agreed.
Initial boot on my Toro took 5-6 minutes.
It was butter ever since, however.
Give it a minute.
And make sure you're properly installing a rom (post 2 from the link in my signature).
Edit:
Anton&Juba.
Tag-teaming 'ze noobs until it goes out of style.
It's flashing X on Boot animation. It has stayed in that mode for hours. I am confused and can not back into my phone. Reading other posts, I am able to get back to Fastboot mode. What do I do next? I appreciate your help. Thanks
coachv said:
It's flashing X on Boot animation. It has stayed in that mode for hours. I am confused and can not back into my phone. Reading other posts, I am able to get back to Fastboot mode. What do I do next? I appreciate your help. Thanks
Click to expand...
Click to collapse
I see. So you're in a bootloop. What do you mean fastboot mode? Because I know some users get confused with the terms... I'm assuming you're able to enter the Bootloader (screen with android belly open, where you are able to move through some menu options with your up and down volume keys)? Note, this is not the screen with the Android and red exclamation point. If you are able to boot into bootloader, you should be able to enter your custom recovery (Clockworkmod Recovery?) and wipe data and either flash a rom (same one or new one) and try again, or restore a backup you made. If you're set on using fastboot commands, you can always flash Nexus Factory Images, although this will wipe your SD card. I recommend getting into your custom recovery and wiping and flashing or restoring. If you don't have a custom recovery, you can always flash a custom recovery (fastboot flash recovery recoveryname.img) and flash a custom rom or restore from there. Here is CWM recovery incase you don't have a custom recovery, or you have reverted back to stock (Android with red exclamation point).
yes the android belly is open. I just don't the steps that I need to do from here. This is where I get lost.
coachv said:
yes the android belly is open. I just don't the steps that I need to do from here. This is where I get lost.
Click to expand...
Click to collapse
Can you scroll through the menu options with your volume keys? And one of the options should be "reboot recovery." Do that one.
Yes I can scroll with volume controls. Here are my options: start, restart bootloader, recovery mode and power off
coachv said:
Yes I can scroll with volume controls. Here are my options: start, restart bootloader, recovery mode and power off
Click to expand...
Click to collapse
Okay dude.
1.) Move your volume keys to select recovery mode
2.) press the power button to actually select that option
3.) You will boot into your custom recovery
4.) EITHER Wipe Data, wipe cache, wipe dalvik, and then flash a new rom (or try re-flashing this jellybean rom you're having problems with) OR restore from a backup you have previously made (which I hope you did just incase something worse happens in the future).
You do know how to navigate through your custom recovery, right?
i just rooted with s on and i flashed a custom recovery then rebooted. htc logo came up, and then a black screen its been like an hour with the black screen and it wont boot. i know that normally its takes a long time to boot a fresh rom but this is ridiculous. and i made sure that i flashed a cdma rom marvelc. what do i do!!
i can still boot into the boot loader though
Dude im no expert in HTC phones but you had to turn s-off when rooting your phone. If you made a nandroid backup your in luck reflash your stock rom back and this time root with s-off and enjoy flashing plz hit the thanks button if i helped.
Sent from my Nexus S 4G using XDA
jvill100 said:
i just rooted with s on and i flashed a custom recovery then rebooted. htc logo came up, and then a black screen its been like an hour with the black screen and it wont boot. i know that normally its takes a long time to boot a fresh rom but this is ridiculous. and i made sure that i flashed a cdma rom marvelc. what do i do!!
i can still boot into the boot loader though
Click to expand...
Click to collapse
Boot into hboot with volume down + power. Scroll down to recovery and push power to enter it. All going well you should go into your recovery. If you get a red triangle with an ! Then you still have the stock recovery.
OK now scroll down and make a back UP!!! After that factory reset the device, wipe cache, dalvik cache. Data. Everything aside from your sdcard. Then reboot the device. This should get your device operational again. Reboot should take no longer than 15 minutes.
After that choose a custom rom to flash, or just go about setting up the phone as you want.
When you go to flash a new rom make sure you back up first, then wipe everything bar SD card. Then install the rom and reboot.
Good luck pal
Sent from my HTC Sensation XE using xda premium
still
heavy_metal_man said:
Boot into hboot with volume down + power. Scroll down to recovery and push power to enter it. All going well you should go into your recovery. If you get a red triangle with an ! Then you still have the stock recovery.
OK now scroll down and make a back UP!!! After that factory reset the device, wipe cache, dalvik cache. Data. Everything aside from your sdcard. Then reboot the device. This should get your device operational again. Reboot should take no longer than 15 minutes.
After that choose a custom rom to flash, or just go about setting up the phone as you want.
When you go to flash a new rom make sure you back up first, then wipe everything bar SD card. Then install the rom and reboot.
Good luck pal
Sent from my HTC Sensation XE using xda premium
Click to expand...
Click to collapse
actually when i was rooting the recovery wasnt working for me the tool tried to made me go into recovery but i was stuck at the htc logo. but the tool also offered to install twrp or clockworkmod i installed clock and still wont stuck at the htc logo so i tried twrp and it worked and then i got rooted.
i think i might be twrp that doesnt install roms right.
also i installed a rom it worked but no wifi and wifi was the most important tool for me so the rom is ussless to me
jvill100 said:
actually when i was rooting the recovery wasnt working for me the tool tried to made me go into recovery but i was stuck at the htc logo. but the tool also offered to install twrp or clockworkmod i installed clock and still wont stuck at the htc logo so i tried twrp and it worked and then i got rooted.
i think i might be twrp that doesnt install roms right.
also i installed a rom it worked but no wifi and wifi was the most important tool for me so the rom is ussless to me
Click to expand...
Click to collapse
ok your recovery is a beta. and as such i dont know if it is fully working. so, we shall try to give you a properl.y working clockworkmod recovery
download this http://www.mediafire.com/?p2p88udo32m9xcg and then put it on to the root of your sd card. boot into hboot and allow it to run the update. then Remove the sd card from the phone then boot back into hboot and scroll into recovery. once their out back in your sd card and then follow my above post .
good luck
fixed!
T
heavy_metal_man said:
ok your recovery is a beta. and as such i dont know if it is fully working. so, we shall try to give you a properl.y working clockworkmod recovery
download this and then put it on to the root of your sd card. boot into hboot and allow it to run the update. then Remove the sd card from the phone then boot back into hboot and scroll into recovery. once their out back in your sd card and then follow my above post .
good luck
Click to expand...
Click to collapse
Thank you you for replying but I did some experimenting around and I found out that the clockwork mod was a marvel recovery
I have a marvelc wildfire so I went to rezo609 folder and found the recovery img and replaced it with a clockwork marvelc img.
Then I opened the prompt selected install clockwork mod, it installed
Then I went to recovery, worked and installed the cm9 rom (marvelc) and gapps and It successfully worked
You were probably right its beta so it has some bugs
But thank you all who tried to help me I really appreciate it
Sorry I just started so I deleted the URL
no problem buddy always happy to help.
Okey doks, just received my new HTC One V and got myself in a pickle.
Using CWM 6.0.1.5 made a nandroid backup of the stock phone. The I proceeded to do flash the rom & kernel to CM10 nightly following all the directions. Then noticed it was able to boot into CM10 JB; however, it would keep saying the keyboard stopped working and after a min or so would reboot. So I then proceeded to try to go back to stock then I got md5 mismatch.. i was like wtf.. so i decided to flash the recovery to CWM 5.5.0.4 and now im stuck at the recovery and when i press the power button to select an option in CWM all my options just disappear. If press power again my options come back but if i try to select any and hit power it just disappears again. What to do?
Have you renamed the backup ??
donhashem.dh said:
Have you renamed the backup ??
Click to expand...
Click to collapse
Yea I tried renaming the backup and it still says mismatch md5. But anyways I put CWM 6.0.1.5 back on it and decided to try loading a different rom. I data/cache/dalvik wiped the phone, installed from zip AOKP PrimoC (I did CM10 the same way), Rebooted phone to fastboot and grabbed the boot.img from AOKP PrimoC zip and threw it in my fastboot folder and used:
c:\fastboot>fastboot flash boot boot.img
rebooted and i get a black boot screen and it just keeps rebooting. Can someone tell me what I'm doing wrong?
You are probably gonna have to follow this:
http://forum.xda-developers.com/showthread.php?t=2018518
And in clockworkmod 5 you have to use the volume buttons to scroll through the list from top to bottom a few times before using the power button to select items. A quirk but it will work after you do that. Let us know your results.
Sent from my One V using xda app-developers app
Dude ...reflash the first recovery you flashed then make a new nandroid backup to rename the old one as the form as the new one .....and you can get the date and time from details of the folder ...that's what I once did
whoshotjr2006 said:
You are probably gonna have to follow this:
http://forum.xda-developers.com/showthread.php?t=2018518
And in clockworkmod 5 you have to use the volume buttons to scroll through the list from top to bottom a few times before using the power button to select items. A quirk but it will work after you do that. Let us know your results.
Sent from my One V using xda app-developers app
Click to expand...
Click to collapse
This is the exact problem I'm having, I actually stumbled on it before reading your post. But nonetheless thanks! Yea, believe it has to do with my Radio-00.00.0928
Another question, How can i fully charge my phone when all i can get to is the bootloader and recovery?
reID_entify said:
Another question, How can i fully charge my phone when all i can get to is the bootloader and recovery?
Click to expand...
Click to collapse
Yes.
GamingFreak said:
Yes.
Click to expand...
Click to collapse
lol nicely put.
your phone will charge in bootloader and recovery. and im pretty sure thats the radio i had when i was bootlooping, and the ruu downgrade fixed it. just remember to relock your bootloader, and follow the instructions in that guide to pull your stock recovery and flash that back in fastboot.
Having a space " " in the Backup name also gives md5 md5 Error
reID_entify said:
Okey doks, just received my new HTC One V and got myself in a pickle.
Using CWM 6.0.1.5 made a nandroid backup of the stock phone. The I proceeded to do flash the rom & kernel to CM10 nightly following all the directions. Then noticed it was able to boot into CM10 JB; however, it would keep saying the keyboard stopped working and after a min or so would reboot. So I then proceeded to try to go back to stock then I got md5 mismatch.. i was like wtf.. so i decided to flash the recovery to CWM 5.5.0.4 and now im stuck at the recovery and when i press the power button to select an option in CWM all my options just disappear. If press power again my options come back but if i try to select any and hit power it just disappears again. What to do?
Click to expand...
Click to collapse
Please post all questions in Q&A. Thread moved there.
I have a rooted Galaxy S3 that is running the ATT Jelly Bean update.
Last night, while looking at ROM manager I got a popup saying there is a newer version of CWM and did I want to install it.
After installing it, the phone will only boot into recovery. I cannot get it to start. And when I tried to restore from a backup that I have used successfully before, I got an error while restoring data.
At this point, I am thinking that I might have bricked this phone. Searching on the ATT Galaxy S3 forum hasn't turned up anything relevant.
Does anyone have an idea what I can try next?
Thanks
northstar7 said:
I have a rooted Galaxy S3 that is running the ATT Jelly Bean update.
Last night, while looking at ROM manager I got a popup saying there is a newer version of CWM and did I want to install it.
After installing it, the phone will only boot into recovery. I cannot get it to start. And when I tried to restore from a backup that I have used successfully before, I got an error while restoring data.
At this point, I am thinking that I might have bricked this phone. Searching on the ATT Galaxy S3 forum hasn't turned up anything relevant.
Does anyone have an idea what I can try next?
Thanks
Click to expand...
Click to collapse
If you a can boot into recovery than you aren't bricked.
You can do a factory reset that might clear it up.
Worst case go into download mode and use Odin to reinstall the stock ROM.
Sent from my SGH-I747 using xda app-developers app
northstar7 said:
I have a rooted Galaxy S3 that is running the ATT Jelly Bean update.
Last night, while looking at ROM manager I got a popup saying there is a newer version of CWM and did I want to install it.
After installing it, the phone will only boot into recovery. I cannot get it to start. And when I tried to restore from a backup that I have used successfully before, I got an error while restoring data.
At this point, I am thinking that I might have bricked this phone. Searching on the ATT Galaxy S3 forum hasn't turned up anything relevant.
Does anyone have an idea what I can try next?
Thanks
Click to expand...
Click to collapse
Im assuming you powered down, did a battery pull and powered back up? Factory reset?
What error message is displayed when trying to restore a backup?
The latest cwm release is 6.0.2.8. If you came from 6.0.2.3, I would download a cwm flashable zip of that recovery and flash that. Perhaps try a reboot then. If it's still a no-go, try restoring a backup with the cwm you had just downloaded and flashed to see if it will restore without an error message
Different CWM
xBeerdroiDx said:
Im assuming you powered down, did a battery pull and powered back up? Factory reset?
What error message is displayed when trying to restore a backup?
The latest cwm release is 6.0.2.8. If you came from 6.0.2.3, I would download a cwm flashable zip of that recovery and flash that. Perhaps try a reboot then. If it's still a no-go, try restoring a backup with the cwm you had just downloaded and flashed to see if it will restore without an error message
Click to expand...
Click to collapse
Thanks very much for the advice.
For the record, my phone is displaying "ClockworkMod Recovery v6.0.2.9"
I just has this happen to me as well. I just put the s3 in download mode and used Odin to re flash cwm. I'm using the same version cwm.
Sent from my SAMSUNG-SGH-I747 using xda premium
I as well. Tried everything and no go. Will try ODIN and see if it works.
Domoo said:
I just has this happen to me as well. I just put the s3 in download mode and used Odin to re flash cwm. I'm using the same version cwm.
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
stranglely pressing the recovery button combo fixed it and im back in CM10.1 #lolwut?
In the end I got the phone working again
For whatever reason, after getting that update to ClockworkMod, the phone would not boot.
I followed the Beginners' Guide to Rooting the Galaxy S3 forum. When I was finished I immediately got an OTA update from ATT.
So now the phone is running again, but I've lost most of my customization and personal data.
What is with this CWM "upgrade?" Or is the problem with ROM Manager?
More likely is that I did something wrong.
At least I can make calls now.
Same here, stay away from that update! Bad things!
This also happened to me. Cwm is showing up as .9 instead of .8. I flashed a previous version of twrp and it still proceeded to go into recovery mode after selecting reboot. I did a factory reset and re flashed aokp and also cm10.1 (along with gapps of course) and it still did it. So I pulled the battery and put it into download mode and reset it from there. That's the only way to get the phone to boot up. From what I see here, is the basic fix for this problem flashing an older cwm in Odin?
Having the same issue, version .9 No amount of clearing data/wipe/reflash/restore will do anything for me either. So much for a lunchtime AOKP update...
I've looked in several different forums on xda and the general fix seems to be flashing a previous version of cwm. No need to reset your phone and flash roms all day long.
Download prior cwm release (.tar)
pull battery and replace
boot to download mode
connect to pc and flash cwm
Disconnect, pull battery, reboot
Here's the 6.0.2.3 release. You can grab the .8 in the Android dev section if you wish
https://www.dropbox.com/s/sfkjtndn7k0urmh/recovery-clockwork-6.0.2.3-d2att.tar
Let me know if this does not work. If your device is not recognized by your pc, you can try flashing this cwm zip in recovery itself (if you have a micro sd card):
http://d-h.st/8qP
I flashed with the same version of cwm I had previously before this issue (6.0.28). It seems to be an issue with 6.0.29 if so many people have this same issue.
Sent from my SAMSUNG-SGH-I747 using xda premium
xBeerdroiDx said:
I've looked in several different forums on xda and the general fix seems to be flashing a previous version of cwm. No need to reset your phone and flash roms all day long.
Download prior cwm release (.tar)
pull battery and replace
boot to download mode
connect to pc and flash cwm
Disconnect, pull battery, reboot
Here's the 6.0.2.3 release. You can grab the .8 in the Android dev section if you wish
https://www.dropbox.com/s/sfkjtndn7k0urmh/recovery-clockwork-6.0.2.3-d2att.tar
Let me know if this does not work. If your device is not recognized by your pc, you can try flashing this cwm zip in recovery itself (if you have a micro sd card):
http://d-h.st/8qP
Click to expand...
Click to collapse
I flashed the CMW-recovery_ATT-6.0.2.3_zip directly from the external sd card to the phone and the phone is now working. but I did have to reboot phone twice. the first time it stayed in recovery.
THANK YOU!!
xBeerdroiDx said:
I've looked in several different forums on xda and the general fix seems to be flashing a previous version of cwm. No need to reset your phone and flash roms all day long.
Download prior cwm release (.tar)
pull battery and replace
boot to download mode
connect to pc and flash cwm
Disconnect, pull battery, reboot
Here's the 6.0.2.3 release. You can grab the .8 in the Android dev section if you wish
https://www.dropbox.com/s/sfkjtndn7k0urmh/recovery-clockwork-6.0.2.3-d2att.tar
Let me know if this does not work. If your device is not recognized by your pc, you can try flashing this cwm zip in recovery itself (if you have a micro sd card):
http://d-h.st/8qP
Click to expand...
Click to collapse
I believe this can even be simplified a bit more. At least for me, some people may find Odin to be the simple way to do things. So you're stuck at recovery:
Hold the power button for 10 seconds to power off.
Boot to download mode by holding volume down and home. The phone will probably start to boot right away after releasing the power button. If it doesn't go to download, then your timing is off, try again.
Hold the power button for 10 seconds to power off and reboot.
It should boot regularly now.
Flash a new recovery. You can download CWM 6.0.2.8 or use this as an opportunity to move to TWRP. Once you have the img file on your phone, go to a terminal and (after su, if needed) run dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p18 (replace "/sdcard/recovery.img" with the path and name of the img file you downloaded. You can also flash the recovery using whatever other on-phone method you prefer.
The CWM download page is now showing that 6.0.2.8 is the newest version for many of the S3 variants, so they've certainly noticed the bug.
J M L said:
I believe this can even be simplified a bit more. At least for me, some people may find Odin to be the simple way to do things. So you're stuck at recovery:
Hold the power button for 10 seconds to power off.
Boot to download mode by holding volume down and home. The phone will probably start to boot right away after releasing the power button. If it doesn't go to download, then your timing is off, try again.
Hold the power button for 10 seconds to power off and reboot.
It should boot regularly now.
Flash a new recovery. You can download CWM 6.0.2.8 or use this as an opportunity to move to TWRP. Once you have the img file on your phone, go to a terminal and (after su, if needed) run dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p18 (replace "/sdcard/recovery.img" with the path and name of the img file you downloaded. You can also flash the recovery using whatever other on-phone method you prefer.
The CWM download page is now showing that 6.0.2.8 is the newest version for many of the S3 variants, so they've certainly noticed the bug.
Click to expand...
Click to collapse
How is this simpler? There are left out bits and errors all through your instructions. My steps were for odin so I'm not sure why you thought they were not.
Hi,
I was trying to flash CM onto my Tmobile Galaxy S2 and got into serious soup.
This phone is not unlocked. I thought it is not necessary.
I rooted the phone using instructions from galaxyroot website.
I did this cos i got my other Tmob Galaxy S2 rooted this way.
Afterwards, i downloaded CM cm-10.1.1-hercules and copied it to internal storage, and tried to update it from recovery.
Update completed successfully, but now the phone is stuck in a boot loop.
I have got this before when i did not clear all the data, but this time I am seeing these weird errors while wiping various data:
While doing "wipe data/factory reset" I get the below error:
Error mounting /sdcard/.android_secure!
Skipping format...
While doing "wipe dalvik cache"
E: Unknown volume for path [/sd-ext]
Also, i am using the CWM recovery 5.0.2.6 that i got from the above link, I could not get odin to flash any newer versions of CWMR.
Not sure if this is relevant, but just throwing it out there.
Please help!
mansmaan said:
Also, i am using the CWM recovery 5.0.2.6 that i got from the above link, I could not get odin to flash any newer versions of CWMR.
Not sure if this is relevant, but just throwing it out there.
Please help!
Click to expand...
Click to collapse
You need to update your recovery to flash CM10.1.
I would suggest TWRP 2.6.1.0 from here:
http://techerrata.com/file/twrp2/hercules/openrecovery-twrp-2.6.1.0-hercules.tar
Or you can look for a CWM 6xxx flash-able zip in the development threads.
meekrawb said:
You need to update your recovery to flash CM10.1.
I would suggest TWRP 2.6.1.0 from here:
Or you can look for a CWM 6xxx flash-able zip in the development threads.
Click to expand...
Click to collapse
meekrawb, i flashed the twrp2 using ODIN. Now when i goto recovery mode (pressing vol up,vol down,pwr and then releasing pwr) it goes into twrp, but it is just stuck showing the splash screen. no menus nothing.
mansmaan said:
meekrawb, i flashed the twrp2 using ODIN. Now when i goto recovery mode (pressing vol up,vol down,pwr and then releasing pwr) it goes into twrp, but it is just stuck showing the splash screen. no menus nothing.
Click to expand...
Click to collapse
How long did you wait on the splash screen? It does take a little while to boot at first.
If you waited more than a minute, there may be a problem with your phone and you might have to Odin back to stock.
meekrawb said:
You need to update your recovery to flash CM10.1.
I would suggest TWRP 2.6.1.0 from here:
Or you can look for a CWM 6xxx flash-able zip in the development threads.
Click to expand...
Click to collapse
meekrawb said:
How long did you wait on the splash screen? It does take a little while to boot at first.
If you waited more than a minute, there may be a problem with your phone and you might have to Odin back to stock.
Click to expand...
Click to collapse
I waited for about 10 minutes before giving up. Could you suggest me an odin-flashable CWM 6x ?
I tried to flash many versions from the forum but ODIN keeps crashing when it tries to flash them.
This is where i got them from: [RECOVERY] ClockworkMod 6.0.3.1 for Samsung Galaxy S2 (T-Mobile) SGH-T989 (Cant post links)
Thanks for all your help.
I would ODIN back to stock, then flash TWRP 2.44, and update TWRP from there... May solve some issues down the line if you have a corrupted recovery...
mansmaan said:
I waited for about 10 minutes before giving up. Could you suggest me an odin-flashable CWM 6x ?
I tried to flash many versions from the forum but ODIN keeps crashing when it tries to flash them.
This is where i got them from: [RECOVERY] ClockworkMod 6.0.3.1 for Samsung Galaxy S2 (T-Mobile) SGH-T989 (Cant post links)
Thanks for all your help.
Click to expand...
Click to collapse
I have an Odin flash-able of 6.0.3.1 on my dev-host.
http://d-h.st/4Pk
Hopefully that will work for you.
Edit: If it doesn't work you can find the stock 4.1.2 here:
http://d-h.st/IRQ
meekrawb said:
I have an Odin flash-able of 6.0.3.1 on my dev-host.
Hopefully that will work for you.
Edit: If it doesn't work you can find the stock 4.1.2 here:
Click to expand...
Click to collapse
meekrawb, thanks for your help! I was able to flash the new CWM but that does not seem to be working. When flashing cache, it says formatting cache for a long time and then reboots. Attempts to flash CM Rom using the new CWM did not help either. (Still bootlooping)
I was able to install the 4.1.2 from the md5 though. It is asking for the SIM which i dont have, but it is not stuck in a loop and seem to be responding. I will check with the sim in the evening and update. Thanks a ton for showing some light at the end of the tunnel!
Still I wonder why i cant flash CM on this phone. I have another phone of the same model on which i was able to flash without hassle.
Only difference i can think of is that this phone has an external sd card.
mansmaan said:
Still I wonder why i cant flash CM on this phone. I have another phone of the same model on which i was able to flash without hassle.
Only difference i can think of is that this phone has an external sd card.
Click to expand...
Click to collapse
Glad you at least got it running. Maybe your internal/external SD cards have errors? I'm not sure how to go about fixing that though.
meekrawb said:
Glad you at least got it running. Maybe your internal/external SD cards have errors? I'm not sure how to go about fixing that though.
Click to expand...
Click to collapse
Odin to stock first should repair any bad internal memory.
Sent from my SGH-T889 using xda app-developers app