Ive looked around the internet, and here, and cant really figure something out. Do I have to install CM10 from fastboot or can I just install the zip using TWRP?
I ask because I tried installing the stable version of CM10 using TWRP and when I reboot I just get the spinning Cyanogenmod logo for a long time. Nothing ever happens.
Am I doing something wrong?
Did you make a backup of your stock Rom? Log into that. Get flashimagegui and use on the cm10 zip then boot back into twrp and install the zip.
Or
Open the cm10 zip on your computer. Extract boot.img. put your phone in fastboot. Put the boot.img in your fastboot folder and type fastboot flash boot boot.img
Sent from my HTC One XL using xda app-developers app
area51avenger said:
Did you make a backup of your stock Rom? Log into that. Get flashimagegui and use on the cm10 zip then boot back into twrp and install the zip.
Or
Open the cm10 zip on your computer. Extract boot.img. put your phone in fastboot. Put the boot.img in your fastboot folder and type fastboot flash boot boot.img
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse
Thanks a lot. I will do that right now. Appreciate the help.
Is flashimagegui an android app? Thats the only reference to it I can find.
Yes it is. There is a donation version on play store. Or there's an xda free version if you search the forums
Sent from my HTC One XL using xda app-developers app
Well, looks like something might have gone wrong and I fear I might be SOL. I used flashimagegui then returned to TWRP to install CM10. I still got the spinning log. I went to restore my backup and I cant boot back into my back up. During bootup a HTC logo comes up with some red text (like its going to go into revocery) and then the screen goes blank. Nothing happens after that. If I turn off the phone and power on again, the same thing happens. I can turn it off then and go through the steps to get back into recovery. I have no idea what do to now. Any recommendations?
JohnnyDanger said:
Well, looks like something might have gone wrong and I fear I might be SOL. I used flashimagegui then returned to TWRP to install CM10. I still got the spinning log. I went to restore my backup and I cant boot back into my back up. During bootup a HTC logo comes up with some red text (like its going to go into revocery) and then the screen goes blank. Nothing happens after that. If I turn off the phone and power on again, the same thing happens. I can turn it off then and go through the steps to get back into recovery. I have no idea what do to now. Any recommendations?
Click to expand...
Click to collapse
what version of hboot is on your device? if it is one of the later ones (1.12+) then you'll need to flash the boot img seperately. If this is the case, (and it sounds like it , as the same thing happened to me and the symptoms where the same).
Extract it from the ROM that you are flashing (open the zip file and drag out the boot.img). Then while TWRP is running, connect the USB cable to your comp and fire up a terminal (you'll need ADB/fastboot set up and working - search google or XDA for how to do it in your operating system).
Once you have adb/fastboot working and TWRP running -> at a terminal (or command prompt on windows) use adb to push the rom onto the sdcard, and then reboot to bootloader and select fastboot.
run "fastboot flash boot boot.img" without the quotes. This should write the kernel image to the boot partition, and then you should be able to load TWRP to (wipe cache/dalvik and then) reflash cyanogen mod.
Good luck
If you can still boot into recovery, you're fine. Manually flash the CM10 boot.img with fastboot, do a full wipe in TWRP and then reinstall the CM10 zip + gapps. Should be good after that.
Thanks for the info, from both of you. Im going to try that right now.
Im trying to flash the boot.img file, but I keep getting an error. Any ideas?
Heres what I get
C:\adt-bundle-windows\sdk\platform-tools>fastboot flash boot boot.img
sending 'boot' (5248 KB)...
FAILED (data transfer failure (Unknown error))
finished. total time: 0.016s
Click to expand...
Click to collapse
did you do a factory reset from the bootloader by any chance? this can corrupt the sdcard, and might cause this. only use the factory reset from recovery.
if you did, try this (http://forums.team-nocturnal.com/showthread.php/1050).
---------- Post added at 02:51 PM ---------- Previous post was at 02:28 PM ----------
Check that it says fastboot usb on your phone. You might not be in fastboot mode.
Otherwise, maybe try a different USB port on your computer, I've had issues trying to get it to detect through a usb hub, so plug it directly inot the computer to rule this out.
codeprimate said:
did you do a factory reset from the bootloader by any chance? this can corrupt the sdcard, and might cause this. only use the factory reset from recovery.
if you did, try this (http://forums.team-nocturnal.com/showthread.php/1050).
---------- Post added at 02:51 PM ---------- Previous post was at 02:28 PM ----------
Check that it says fastboot usb on your phone. You might not be in fastboot mode.
Otherwise, maybe try a different USB port on your computer, I've had issues trying to get it to detect through a usb hub, so plug it directly inot the computer to rule this out.
Click to expand...
Click to collapse
I didnt use the factory reset option from the bootloader. Being that I didnt, should I still try the directions on the link you gave?
When I go into fastboot is start off just saying "fastboot". If I press the volume up or down button is changes to "fastboot usb". I didnt even think about trying a different usb port, I will see if that makes a difference.
JohnnyDanger said:
I didnt use the factory reset option from the bootloader. Being that I didnt, should I still try the directions on the link you gave?
When I go into fastboot is start off just saying "fastboot". If I press the volume up or down button is changes to "fastboot usb". I didnt even think about trying a different usb port, I will see if that makes a difference.
Click to expand...
Click to collapse
can you get into TWRP? if you can, go to the mount menu and see if you can unmount and then remount the sdcard. If you can do this, then you have no need to do the team-nocturnal sdcard fix.
I was able to unmount and then remount the sdcard. Actually, when I went into Mount menu in TWRP to begin with it gave me the option to Mount, then unmount. Is that the same thing? Does that mean my sdcard is not mounted and should I mount it in TWRP?
I was finally able to flash the boot.img. I then went into TWRP to install CM10. It installed and now is back into the spinning logo. Im ready to give up on this. Any more suggestions?
Just a thought, should I be removing the boot.img from the CM10 zip Im trying to install?
No don't remove it. Did you wipe data/system before installing. And wipe cache/dalvik after? Also the first boot could take up to 5 minutes sometimes
Sent from my HTC One XL using xda app-developers app
area51avenger said:
No don't remove it. Did you wipe data/system before installing. And wipe cache/dalvik after? Also the first boot could take up to 5 minutes sometimes
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse
Ive been trying to install the latest stable build of CM10. I decided to try the most recent Nightly now. That seemed to work. The spinning just stopped and Im on the welcome screen. FINALLY! Thank you guys for all the help. Never had such a hard time with installing a custom rom before.
JohnnyDanger said:
Ive been trying to install the latest stable build of CM10. I decided to try the most recent Nightly now. That seemed to work. The spinning just stopped and Im on the welcome screen. FINALLY! Thank you guys for all the help. Never had such a hard time with installing a custom rom before.
Click to expand...
Click to collapse
No worries man, good luck with your One X, I hope the worst is behind you now.
If you are feeling confident, there is a method to downgrade your hboot so you don't need to stuff around flashing the boot image separately. This however does involve bricking and then de-bricking your device, and you'll need a linux computer to pull it off, so this isn't for everyone.
Related
Attempted to flash update to current CM 7 Nightly build, from Nightly10. When doing so, Bootloader>Recovery(System hangs on Google load screen), Battery is then pulled. Attempts are made without SIM card. Also initiated with ROM Manager v3.0.0.7 +Fix Permissions, with same results.
No luck with returning to previous ROM, or cleaning Cache and Dalvic-cache for same reason.
All other ROM flashing attempts have been flashed on my Nexus S, great success.
Side Note: CM 7 Nightly10 is running great! Boots/Loads with no issue.
Red Fox said:
Attempted to flash update to current CM 7 Nightly build, from Nightly10. When doing so, Bootloader>Recovery(System hangs on Google load screen), Battery is then pulled. Attempts are made without SIM card. Also initiated with ROM Manager v3.0.0.7 +Fix Permissions, with same results.
No luck with returning to previous ROM, or cleaning Cache and Dalvic-cache for same reason.
All other ROM flashing attempts have been flashed on my Nexus S, great success.
Side Note: CM 7 Nightly10 is running great! Boots/Loads with no issue.
Click to expand...
Click to collapse
dont use rom manager, rom could be corrupted while downloading. download it manually then flash from recovery.
simms22 said:
dont use rom manager, rom could be corrupted while downloading. download it manually then flash from recovery.
Click to expand...
Click to collapse
What could cause, or any suggestion on how to fix/pass the system freeze on: Power+VolumeUP>Recovery= Google ... .. ... (snooze, thinking, snooze)
Much help is greatly appreciated, updating to the latest and greatest is inspiring.
Sent from my Nexus S
Red Fox said:
What could cause, or any suggestion on how to fix/pass the system freeze on: Power+VolumeUP>Recovery= Google ... .. ... (snooze, thinking, snooze)
Much help is greatly appreciated, updating to the latest and greatest is inspiring.
Sent from my Nexus S
Click to expand...
Click to collapse
ahhh, i misunderstood you first. try flashing the recovery again.
simms22 said:
ahhh, i misunderstood you first. try flashing the recovery again.
Click to expand...
Click to collapse
I just tried the recovery OS ROM, no progress, still freezing the same. Could you please explain this recovery, that you suggest?
If the system doesn't make it to the next stage/screen, w/the android. I feel like something is missing to pass go, and collect $100 big one's, LOL!
Sent from my Nexus S
Note: I also attempting this through, ROM Manager. As Bootloader triggers same results. ROM's are all DL'ed from http://mirror.teamdouche.net/?device=crespo (Blank Stare)
Sent from my Nexus S
adb update:
cmd
cd c:\androidsdk\tools
fastboot flash recovery recovery.img
ENTER
Figured it out through trial, and error.
Hope this helps fellow XDA members.
Thanks for your efforts, and taking the time to help with this issue.
Sent from my Nexus S
Red Fox said:
adb update:
cmd
cd c:\androidsdk\tools
fastboot flash recovery recovery.img
ENTER
Figured it out through trial, and error.
Hope this helps fellow XDA members.
Thanks for your efforts, and taking the time to help with this issue.
Sent from my Nexus S
Click to expand...
Click to collapse
I do have exactly the same problem.
Which recovery.img did you flash?
stiefa00 said:
I do have exactly the same problem.
Which recovery.img did you flash?
Click to expand...
Click to collapse
Here is the recovery.img that I flashed:
http://www.megaupload.com/?d=C933QJOO
Same recovery.img used when rooting, here is the source:
http://theunlockr.com/2010/12/17/how-to-root-the-samsung-nexus-s/
Sent from my Nexus S
Another alternative, Terminal Emulator:
- install recovery to sd-card(no folders)
- Terminal:
su
flash_image recovery /sdcard/name-of-recovery.img
-=Edit=-
Phone should pause for a second and then show you a new blank line. Turn it off and back on. Holding down VolumeUp and Power to ensure it flashed correctly. Done.
Sent from my Nexus S
thx, got it!
Dunno if mine is the same problem.
My recovery seems to "reset" itself after every reboot. I have done it from ROM manager also also fastboot.
1. I flash the recovery
2. reboot
3. recovery comes up fine
4. reboot again, it show me this triangle sign with a exclamation mark inside.
So i need to fastboot/ROM manager everytime I want to go into the clockwork recovery.
ykphuah said:
Dunno if mine is the same problem.
My recovery seems to "reset" itself after every reboot. I have done it from ROM manager also also fastboot.
1. I flash the recovery
2. reboot
3. recovery comes up fine
4. reboot again, it show me this triangle sign with a exclamation mark inside.
So i need to fastboot/ROM manager everytime I want to go into the clockwork recovery.
Click to expand...
Click to collapse
Dude, this is discussed in multiple threads already.
The OTA 2.3.1 and 2.3.2 updates place a new script in the /etc folder that checks the crc on your recovery image at every bootup. If it fails, a backup copy of stock replaces it.
If you want to stay on Clockwork, you need to rename the file /etc/install-recovery.sh to something like /etc/install-recovery.sh.bak
Ah ok thanks! I din know where or what term to search for this.
So im running 3.1 rooted with the 1.4.4 Tiamat Kernel. I had this weird force closing issue where gapps would force close whenever i tried to connect to wifi. I powered down, turned on, and am now stuck in a boot animation loop. I can hold down the Vol Down button and it says "Starting Fastboot Protocol Support." but nothing changes. Is there anything I can do it fix it/turn it off until i get home to my computer with the SDK? On another note I did install the wpa supplicant (sp?) files to allow it to connect to an adhoc wifi source (eris tether). Please and thank you
EDIT: I have booted into recovery, but I am unable to mount any of the drive locations or wipe them. I did a factory data reset (as much as it could I guess?), but im still at the boot loop.
Hook it up to computer while its in fastboot and open a command prompt from the folder you have fastboot. Type "fastboot reboot-bootloader" and you should get adb to recognize, then push stock images or root images and recovery.
What recovery were you using? Did you flash the one from ROM manager?
I am using the CM from the ROM manager the latest one I think that it is version 4 something. does this make a difference? I have backups from my previous flash but when I tried to recover it won't take them. where can I get the root image? I might have it already since I rooted using adb, I will have to look on my laptop when I get home. Any other info you have will help. Thank you,,,,
razor532 said:
I am using the CM from the ROM manager the latest one I think that it is version 4 something. does this make a difference? I have backups from my previous flash but when I tried to recover it won't take them. where can I get the root image? I might have it already since I rooted using adb, I will have to look on my laptop when I get home. Any other info you have will help. Thank you,,,,
Click to expand...
Click to collapse
You will need to flash a good recovery, I suggest you you use the .img file in this thread through adb when you get to your laptop:
http://forum.xda-developers.com/showthread.php?t=1074979
The recovery version you updated to won't look at your external sdcard, so you can't flash from it until you re-install a good recovery.
Can't we get a pinned warning about this issue?
Thanks everyone, sorry for the delay. I ended up fixing it with a fastboot oem unlock command. However after countless flashes unable to get it to boot again i realized i was flashing the tiamat rom and then a different tiamat kernel boot.img, most likely the culprit in my boot loop. The minute i did a factory reset, updated cwr and only flashed the rom, everything works fine. Thanks for everyones help
Sent from my Eris using XDA App
So glad you were able to fix it!
i tried to reinstall viper rom in cwm recovery along with the ics gapps package, everything flashed fine but when i tried to boot the phone up it has become stuck in a boot loop and i cannot enter recovery (it starts to load then it reboots and resumes its boot loop). i re flashed cwm recovery, but the same error persists. in dire need of suggestions, need this thing working by tomorrow morning.
thanks in advance
Have you flashed the boot .img Before you flashed the ROM ？
Sent from my HTC One S using xda app-developers app
You should try to get into the Bootloader mode , this will be possible even though you are in a bootloop. After you got into Bootloader mode you should flash using the AIO Toolkit the TWRP recovery (I think the AIO Toolkit can do that via Fastboot USB)
After that you can mount your sd card in TWRP and push a Nandroid of someone (You can find plenty of nandroids on the forums using the search, but search for TWRP nand) and restore it. AFTER all this you should read the instructions given on every rom thread you wanna flash. Google apps flashing on viper rom? srsly?
i already flashed both cwm and twrp manually before i posted, but went ahead and gave the toolkit a shot, it installs twrp no problem, but it still crashes and resumes the bootloop whenever i try to boot into recovery. and before you try to give people crap about installing an extra package, i flashed the gapps because the google services framework was not working, and your method (stated so far) was unhelpful. maybe check your tone next time
a448y901 said:
Have you flashed the boot .img Before you flashed the ROM ？
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
You don't flash before you flash after
Sent from my HTC One S using xda app-developers app
---------- Post added at 10:48 AM ---------- Previous post was at 10:42 AM ----------
OK if you can get in recovery try to reflash the ROM without wipe and let it go threw and then click reboot into boatloader and just hold the bottom volume
After you get in there put the boot IMG in what ever folder you have you fastboot on your computer and hold down shift and click the right on the mouse and click command prompt and type fastboot flash boot boot.img it will load it after type fastboot erase cache and then fastboot reboot and just let it do its thing it will probably reboot twice and it will load right up
Sent from my HTC One S using xda app-developers app
fixed the issue myself, rather simple. erased the cache via fastboot and bam, able to boot into recovery
HidaKureku said:
and before you try to give people crap about installing an extra package ... maybe check your tone next time
Click to expand...
Click to collapse
Wassup, bro, you mad?
The dude was trying to help, so don't poke him. You're a house guest, so respect the house rules and respect people who try to help you. And if you can't swallow a little irony or a joke, at least check your own tone!
Cheers!
sorry just noticed this thread is 2 years old...
ok, i guess i screwed up, didnt make nandroid etc, but lets put that aside.
i installed xenonhd the other day, and then the matr1x kernel. since i was not satisfied with matr1x, i wanted to change the kernel. i downloaded franco and flashed it.
not my device instantly boots into recovery without me even pushing volume+ button. on the top of the screen there is a red message: "fastboot mode - no boot or recovery img". i dont think this message was there before.
anyway, i wanted to just reflash the system again with xenonhd rom, but its not on the sd memory. now i tried to push it on the device with adb, but when i do "adb device", my device doesnt appear in the list. the list is empty. however, "fastboot device" does show the device.
ok, the big question: how do i get the rom (zip file) on the device so i can reflash it from recovery? recovery is working.
Try to reflash an entire boot IMG. It might work, but you'd lose everything.
This happened to me once, I got that message too.. But I couldn't do anything at all.. I think my sdcard was dead. I had to send mine into Sammy repair.
Sent from my Nexus S using xda app-developers app
what do you mean by boot img? you mean a complete rom?
the rom i have is xenonhd, it does come in a zip file, not as am img file.
murfi said:
ok, i guess i screwed up, didnt make nandroid etc, but lets put that aside.
i installed xenonhd the other day, and then the matr1x kernel. since i was not satisfied with matr1x, i wanted to change the kernel. i downloaded franco and flashed it.
not my device instantly boots into recovery without me even pushing volume+ button. on the top of the screen there is a red message: "fastboot mode - no boot or recovery img". i dont think this message was there before.
anyway, i wanted to just reflash the system again with xenonhd rom, but its not on the sd memory. now i tried to push it on the device with adb, but when i do "adb device", my device doesnt appear in the list. the list is empty. however, "fastboot device" does show the device.
ok, the big question: how do i get the rom (zip file) on the device so i can reflash it from recovery? recovery is working.
Click to expand...
Click to collapse
Recovery is working?
Then you boot into recovery, and mount USB storage in Mount and storage section in CWM. Once you mounted it, unplug and replug your cable for the drive to show up.
It's important your recovery be v6.0.1.0 or older because the newer versions have a USB mounting bug with the Nexus S.
yeah that doesnt work, i have a newer version.
anyway, i figured that the rom zip had a boot.img inside, so i just flashed that file alone. voila, the phone boots again.
thank you guys for your help!!!
murfi said:
yeah that doesnt work, i have a newer version.
anyway, i figured that the rom zip had a boot.img inside, so i just flashed that file alone. voila, the phone boots again.
thank you guys for your help!!!
Click to expand...
Click to collapse
Good job!
That's what FirePoncho meant. Might be a good idea to switch your recovery either to an older version of CWM (6.0.1.0 doesn't have the bug) or to TWRP in case you need it one of these days.
polobunny said:
Good job!
That's what FirePoncho meant. Might be a good idea to switch your recovery either to an older version of CWM (6.0.1.0 doesn't have the bug) or to TWRP in case you need it one of these days.
Click to expand...
Click to collapse
I agree! I've been sticking with CW v 5.0.2.3, cause there are no bugs, and I like using the volume buttons
Sent from my Nexus S using xda app-developers app
Hi,
I have put more than 12 hours of my time, before creating this thread. I have tried things, but still struck, so thought to post it in a new thread. Thanks for all your time.
Currently struck in,
fastboot mode started udc_start()
I tried, fastboot erase recovery -> fastboot flash recovery recovery.img -> fastboot reboot (successfully). But it still struck at same place after reboot.
I tried with different recovery images, but still the same observation. I tried to boot by key combination (volume down+home+power), still same observation.
Earlier, I installed ROM manager through google play and installed CWM recovery, version 5.xxx (which I feel now is a mistake), as I tried to install CM11 from MukilSoni, which needs CWM version 6.xx +. I am able to go into recovery and select CM11 image through CWM and proceed with install steps. But, after initial selection in CWM (like app install, etc) it rebooted and went into fastboot mode.I checked the log, it ended with some return error 7.
Then, I tried to Google and check how to recover from fastboot mode, but all failed. I didnt tried KDZ method, but thought to hear from you guys before making it more messy.
Glad, if I get any help and appreciate it.
Thanks for reading it and your time.
Regards,
Ganesh
Hi,
I have put more than 12 hours of my time, before creating this thread. I have tried things, but still struck, so thought to post it in a new thread. Thanks for all your time.
Currently struck in,
fastboot mode started udc_start()
I tried, fastboot erase recovery -> fastboot flash recovery recovery.img -> fastboot reboot (successfully). But it still struck at same place after reboot.
I tried with different recovery images, but still the same observation. I tried to boot by key combination (volume down+home+power), still same observation.
Earlier, I installed ROM manager through google play and installed CWM recovery, version 5.xxx (which I feel now is a mistake), as I tried to install CM11 from MukilSoni, which needs CWM version 6.xx +. I am able to go into recovery and select CM11 image through CWM and proceed with install steps. But, after initial selection in CWM (like app install, etc) it rebooted and went into fastboot mode.I checked the log, it ended with some return error 7.
Then, I tried to Google and check how to recover from fastboot mode, but all failed. I didnt tried KDZ method, but thought to hear from you guys before making it more messy.
Glad, if I get any help and appreciate it.
Thanks for reading it and your time.
Regards,
Ganesh
Click to expand...
Click to collapse
Did you ever try pull out the battery, reinsert, reboot system with 3 buttons combination? I got several fastboot mode as you're facing, and the system works just fine using above method.
I think you got just soft brick. Please, keep the device stay untouched until someone with such expertise to solve the problem will guide you. I think @akiratoriyama can share his bad experience bricking his lovely p500.
Wish you luck.
PS.
You must to press three buttons a bit longer, do not release it, until recovery mode appearing. Otherwise fastboot mode or blank screen showing instead.
Sent from my Optimus One using xda app-developers app
agk.ganesh said:
Hi,
I have put more than 12 hours of my time, before creating this thread. I have tried things, but still struck, so thought to post it in a new thread. Thanks for all your time.
Currently struck in,
fastboot mode started udc_start()
I tried, fastboot erase recovery -> fastboot flash recovery recovery.img -> fastboot reboot (successfully). But it still struck at same place after reboot.
I tried with different recovery images, but still the same observation. I tried to boot by key combination (volume down+home+power), still same observation.
Earlier, I installed ROM manager through google play and installed CWM recovery, version 5.xxx (which I feel now is a mistake), as I tried to install CM11 from MukilSoni, which needs CWM version 6.xx +. I am able to go into recovery and select CM11 image through CWM and proceed with install steps. But, after initial selection in CWM (like app install, etc) it rebooted and went into fastboot mode.I checked the log, it ended with some return error 7.
Then, I tried to Google and check how to recover from fastboot mode, but all failed. I didnt tried KDZ method, but thought to hear from you guys before making it more messy.
Glad, if I get any help and appreciate it.
Thanks for reading it and your time.
Regards,
Ganesh
Click to expand...
Click to collapse
Two years ago I bricked my phone also after using ROM manger. Though I will never ever use this or similar tools again. But at least, if I remember correctly, I could revive my phone with the "fastboot erase recovery" method http://forum.xda-developers.com/showthread.php?t=1088046. But since you failed is seems to be another problem. I am not a fastboot expert , but since you bricked your phone with ROM manager too, I wanted to share my success story with above mentioned method and installing AmonRa recovery. So maybe you will give it a second try? All I can remember is, that it is extremely important to follow the instructions exactly.
xu3sno said:
Did you ever try pull out the battery, reinsert, reboot system with 3 buttons combination? I got several fastboot mode as you're facing, and the system works just fine using above method.
I think you got just soft brick. Please, keep the device stay untouched until someone with such expertise to solve the problem will guide you. I think @akiratoriyama can share his bad experience bricking his lovely p500.
Wish you luck.
PS.
You must to press three buttons a bit longer, do not release it, until recovery mode appearing. Otherwise fastboot mode or blank screen showing instead.
Sent from my Optimus One using xda app-developers app
Click to expand...
Click to collapse
androidck said:
Two years ago I bricked my phone also after using ROM manger. Though I will never ever use this or similar tools again. But at least, if I remember correctly, I could revive my phone with the "fastboot erase recovery" method http://forum.xda-developers.com/showthread.php?t=1088046. But since you failed is seems to be another problem. I am not a fastboot expert , but since you bricked your phone with ROM manager too, I wanted to share my success story with above mentioned method and installing AmonRa recovery. So maybe you will give it a second try? All I can remember is, that it is extremely important to follow the instructions exactly.
Click to expand...
Click to collapse
Thanks @xu3sno & @androidck
I am also getting help from mukulsoni & others in Official CM11 version 10 thread.
I am able to go into the flash tool (pointed by mukulsoni, http://forum.xda-developers.com/showpost.php?p=49567169&postcount=45)
and able to go 'Select kernel to hotboot' with recovery.img (CWMod-6.4.0.6-Jan16)
But rebooting by HOME+Volume DOWN+POWER --> goes into CWM recovery of v5.0.2.0 (which i installed initially)
I am thinking, what to do next.
I will keep my progress posted here.
Thanks for listening..
agk.ganesh said:
Thanks @xu3sno & @androidck
I am also getting help from mukulsoni & others in Official CM11 version 10 thread.
I am able to go into the flash tool (pointed by mukulsoni, http://forum.xda-developers.com/showpost.php?p=49567169&postcount=45)
and able to go 'Select kernel to hotboot' with recovery.img (CWMod-6.4.0.6-Jan16)
But rebooting by HOME+Volume DOWN+POWER --> goes into CWM recovery of v5.0.2.0 (which i installed initially)
I am thinking, what to do next.
I will keep my progress posted here.
Thanks for listening..
Click to expand...
Click to collapse
Are you sure that you are booting into cwm v5.0.2.0? Version is listed at the top. If that is true, then either the flash tool failed to flash cwm v6.4.0.6, or you have chosen the wrong recovery.img. This can easily happen since they all have the same name. Try to flash it again, but make sure that you use the correct image.
Also, I believe that you may not have any rom installed, or existing rom might be corrupted. So you may want to flash a cm-9 or cm-10.x rom first, just to stabilize and to be sure that you are healthy. Those can be flashed using cwm 5.0.2.0. I can post a link or two, if you'd like.
Edit: Here is a link to cm-10.1.6:
http://jenkins.androidarmv6.org/view/All/job/android/597/
Gapps already included.
Sent from my LG-P509 using Tapatalk 2
ibub said:
Are you sure that you are booting into cwm v5.0.2.0?
Also, I believe that you may not have any rom installed, or existing rom might be corrupted. So you may want to flash a cm-9 or cm-10.x rom first, just to stabilize and to be sure that you are healthy. Those can be flashed using cwm 5.0.2.0. I can post a link or two, if you'd like.
Click to expand...
Click to collapse
+1
CM10.1.6 worked
ibub said:
Are you sure that you are booting into cwm v5.0.2.0? Version is listed at the top. If that is true, then either the flash tool failed to flash cwm v6.4.0.6, or you have chosen the wrong recovery.img. This can easily happen since they all have the same name. Try to flash it again, but make sure that you use the correct image.
Also, I believe that you may not have any rom installed, or existing rom might be corrupted. So you may want to flash a cm-9 or cm-10.x rom first, just to stabilize and to be sure that you are healthy. Those can be flashed using cwm 5.0.2.0. I can post a link or two, if you'd like.
Edit: Here is a link to cm-10.1.6:
http://jenkins.androidarmv6.org/view/All/job/android/597/
Gapps already included.
Sent from my LG-P509 using Tapatalk 2
Click to expand...
Click to collapse
Thanks @ibub for your helping hand.
I will check why recovery image not upgrading as expected. (I didn't manually download CWM5.xx version to my PC. I got it via ROM manager app, so i hope I haven't chosen wrong image)
Yes, I got CM10.1.6 from your link and installation went successfully and able to boot up..
But, it is very slow. (May be it will take some time?!) I will check it.
Between, @mukulsoni advised to install CWM6.xxx via CWM5.0.2.0. I will check how it goes.
mns123 said:
+1
Click to expand...
Click to collapse
Thanks.
agk.ganesh said:
Thanks @ibub for your helping hand.
I will check why recovery image not upgrading as expected. (I didn't manually download CWM5.xx version to my PC. I got it via ROM manager app, so i hope I haven't chosen wrong image)
Yes, I got CM10.1.6 from your link and installation went successfully and able to boot up..
But, it is very slow. (May be it will take some time?!) I will check it.
Between, @mukulsoni advised to install CWM6.xxx via CWM5.0.2.0. I will check how it goes.
Thanks.
Click to expand...
Click to collapse
Yeah, I chose to post that link only to make sure that your phone is healthy. Now you can install any recovery/rom that you want. If your volume keys are broken, I suggest that you flash to twrp recovery. It's touch driven.
Sent from my LG-P509 using Tapatalk 2
Thanks
ibub said:
Yeah, I chose to post that link only to make sure that your phone is healthy. Now you can install any recovery/rom that you want. If your volume keys are broken, I suggest that you flash to twrp recovery. It's touch driven.
Sent from my LG-P509 using Tapatalk 2
Click to expand...
Click to collapse
Yes, I will try installing now new recovery and then new ROM.
Very glad to see the support from you guys... Thanks ibub and all..
[rant] NEVER EVER USE KDZ. PERIOD. :crying: [/rant]
Best of luck on your ROM journey :good:
Thanks
akiratoriyama said:
[rant] NEVER EVER USE KDZ. PERIOD. :crying: [/rant]
Best of luck on your ROM journey :good:
Click to expand...
Click to collapse
Thanks @akiratoriyama.
I have upgraded CWM recovery 6.xx through CWM 5.0.2.0 and successfully installed MukulSoni's Kitkat ROM.
And enjoying eating kitkat..
Thanks all..