Database Info

[Q] [i9023] Blank/Black screen in recovery

Hey everyone,
Basically I was trying to flash a new ROM onto an old Nexus S of mine and when I tried to boot into recovery there was just a black screen. I pressed the power button and a single line saying "Clockwork mod Recovery" and the version number popped up. I assumed that the recovery must've been corrupted so I erased it and installed the latest version using fastboot which seemed to work fine.
Now whenever I try to boot into recovery I just get a blank screen with nothing else. I've tried using other recovery images such as twrp but the same problem happened, I just get the background wallpaper/image and nothing else.
I searched the forums and apparently people were having this issue earlier on when the i9023 was first released but now most custom recoveries are supposed to work with both i9020 and i9023.
Also the touch buttons light up and vibrate whenever I touch them when I'm in recovery mode.
Any help to this problem would be greatly appreciated as atm I have an old ROM which is buggy as hell and I need to get rid of it.
Cheers!

I had the same Issue. If you can boot into the rom, you can try to download the rommanager-app and install the recovery from there.

Hey I tried that already that and instead of booting into recovery it just went into the bootloader and said "No Recovery or Bootloader found".
Any other ideas?

Did you clicked the first point in rommanager? Install recovery, or you only hit the second button reboot into recovery?
Sent from my Full Android on Crespo using XDA App

Hey
I have the i9023 and I install rom manager. install CWM and if I reboot into recovery it works and I get in to CWM recovery.. but after reboot into os.. if I go into Rom manager and reboot to recovery it dont work? I just get the android figur and a "!".. then I just can Power + vol up and I'm in bootloader recovery..
Do I have to install CWM every time i want to use it? and can't I access CWM on boot op ?
sorry for my bad English

Normaly you have to flash the recovery only once.
Try to flash the newer clockwork-recovery with fastboot.
http://forum.xda-developers.com/showthread.php?t=988686

Alfiedk: You need to get rid of this file:
/system/etc/install-recovery.sh
As it re-installs the stock recovery every boot.
I think you can download any custom ROM for your phone, and flash it in CWM recovery, this will also solve the problem
Edit: Did you unlock the phone? Have you tried fastboot oem unlock?
Sent from my SNES

bedalus said:
Alfiedk: You need to get rid of this file:
/system/etc/install-recovery.sh
As it re-installs the stock recovery every boot.
I think you can download any custom ROM for your phone, and flash it in CWM recovery, this will also solve the problem
Edit: Did you unlock the phone? Have you tried fastboot oem unlock?
Sent from my SNES
Click to expand...
Click to collapse
I havent unlock my phone, but I can get in to bootloader is it then necessary to unlock ?
I try to delete the /install-recovery.sh

Yes you need to unlock your bootloader, if you dont want to reflash it all the time.
Sent from my Full Android on Crespo using XDA App

Xziped said:
Yes you need to unlock your bootloader, if you dont want to reflash it all the time.
Sent from my Full Android on Crespo using XDA App
Click to expand...
Click to collapse
Then it must be unlock as default.. I havent unlock it.. just delete the install install-recovery.sh and it works every time now.
now I just have to find a ROM to try..

Xziped said:
Did you clicked the first point in rommanager? Install recovery, or you only hit the second button reboot into recovery?
Sent from my Full Android on Crespo using XDA App
Click to expand...
Click to collapse
Yes I made sure I selected install clockwork mod. Like I said the problem isn't the same when I do this, instead of a blank screen, when I boot into recovery it goes straight to fastboot and tells me that I don't have a recovery image installed at all...

Simultaneity said:
Yes I made sure I selected install clockwork mod. Like I said the problem isn't the same when I do this, instead of a blank screen, when I boot into recovery it goes straight to fastboot and tells me that I don't have a recovery image installed at all...
Click to expand...
Click to collapse
what happens when you try to temporary boot into the recovery?
instead of "fastboot flash recovery recovery.img", try to "fastboot boot recovery.img"
Just look for an recovery.img that works temporary and then try to flash it permanently.

I'll try it and get back to you Xziped. If anyone else can think of any other ideas please just throw'em at me, I'm willing to try anything!

Yeah no help there either. It does the exact same thing temporarily booting into a recovery that it did when I actually had it installed on the phone :\.
I updated ROM manager to the latest and tried installing CWM with that but to no avail. It still says that there is no recovery installed when I do that.

Simultaneity said:
Yeah no help there either. It does the exact same thing temporarily booting into a recovery that it did when I actually had it installed on the phone :\.
I updated ROM manager to the latest and tried installing CWM with that but to no avail. It still says that there is no recovery installed when I do that.
Click to expand...
Click to collapse
Sorry but if not even the temporary recovery boots up, i dont know what else we can do
did you try some of the older recoverys? is your bootloader unlocked?

I haven't tried an older recovery and my bootloader is unlocked.
could it be a problem with my computer as opposed to the phone itself? As in my computer is messing up when trying to flash the recovery?
I've also noticed now that when I boot into fastboot mode the menu just locks up and doesn't respond to anything. Sometimes I have to pull the battery and other times it'll start responding after randomly pressing the power key a lot of times...
I'll try an older recovery next

Simultaneity said:
I haven't tried an older recovery and my bootloader is unlocked.
could it be a problem with my computer as opposed to the phone itself? As in my computer is messing up when trying to flash the recovery?
I've also noticed now that when I boot into fastboot mode the menu just locks up and doesn't respond to anything. Sometimes I have to pull the battery and other times it'll start responding after randomly pressing the power key a lot of times...
I'll try an older recovery next
Click to expand...
Click to collapse
Use Odin, that might solve your problems. Search for the Nexus S version of Odin in the Dev section here.

khartaras said:
Use Odin, that might solve your problems. Search for the Nexus S version of Odin in the Dev section here.
Click to expand...
Click to collapse
There's a version of Odin for the Nexus S!?!? I'll look into that straight away thanks!

Simultaneity said:
There's a version of Odin for the Nexus S!?!? I'll look into that straight away thanks!
Click to expand...
Click to collapse
Just look @ http://www.samfirmware.com/ .
There you should find all you need
Sent from my Full Android on Crespo using XDA App

[Q] Need help with SL101 (didn't see a fourm for it)

SL101 with CWM 1 click root v.1 which i understand is basically the same as the TF101
Tried rooting and seemed to be a success but bricked when trying to install cy mod.
Tried factory reset in recovery mode and still bricked.
Won't mount to SD card.
Can't seem to find any guides to reset firmware back to stock...
Any ideas? links to a guide i haven't found? (I have looked) or am I bushwacked?
Thanks.

TWRP recovery is advised instead of CWM, flash TWRP recovery and then try your ROM again

Did you use ROM Manager to install CWM?
That does not play nice with the Asus tablets.
You can try using PERI to push a new recovery via ADB when in recovery.
I would use ADB to push the TWRP 2.3.2.3 blob myself.

*Detection* said:
TWRP recovery is advised instead of CWM, flash TWRP recovery and then try your ROM again
Click to expand...
Click to collapse
I am not able to open any files through the tablet to access this app. The only screen i can get to is the CWM recovery when you hold power + vol. down.

chchas said:
I am not able to open any files through the tablet to access this app. The only screen i can get to is the CWM recovery when you hold power + vol. down.
Click to expand...
Click to collapse
Follow freds instructions above

*Detection* said:
TWRP recovery is advised instead of CWM, flash TWRP recovery and then try your ROM again
Click to expand...
Click to collapse
used PERI to "unbrick" and it went through the whole spiel with no change.
any instruction on how to use the TWRP?

chchas said:
used PERI to "unbrick" and it went through the whole spiel with no change.
any instruction on how to use the TWRP?
Click to expand...
Click to collapse
ALSO. Might note that I do not have access to my tablets home screen AT ALL. Not through cold boot or anything (unless it takes more than 30 minutes to cold boot)

chchas said:
used PERI to "unbrick" and it went through the whole spiel with no change.
any instruction on how to use the TWRP?
Click to expand...
Click to collapse
If you have TWRP installed as your recovery now, just boot into that, press WIPE, then wipe SYSTEM, CACHE and DALVIK CACHE, then press the Home button in TWRP to go back to the main screen and press INSTALL, choose your ROM, flash that, then clear CACHE and DALVIK again, then flash GAPPS and wipe both CACHES again, then reboot
You can also flash a kernel of your choice, KatKernel is the popular one to go with TeamEOS4 ROM

*Detection* said:
If you have TWRP installed as your recovery now, just boot into that, press WIPE, then wipe SYSTEM, CACHE and DALVIK CACHE, then press the Home button in TWRP to go back to the main screen and press INSTALL, choose your ROM, flash that, then clear CACHE and DALVIK again, then flash GAPPS and wipe both CACHES again, then reboot
You can also flash a kernel of your choice, KatKernel is the popular one to go with TeamEOS4 ROM
Click to expand...
Click to collapse
I only have CWM installed. I can't figure out how to load TWRP onto the tablet without being able to pull up the screen.
Still stuck, I'm finding a bunch of different ways to do it but I can't find a step by step specific to my particular problem.

chchas said:
I only have CWM installed. I can't figure out how to load TWRP onto the tablet without being able to pull up the screen.
Still stuck, I'm finding a bunch of different ways to do it but I can't find a step by step specific to my particular problem.
Click to expand...
Click to collapse
From a quick look at the PERI files I would assume this method:
Boot the tablet into CWM and connect it to the PC > USB
Download and extract the PERI files, right click and run EasyRecoveryV0.4.bat as Admin
Once its done you should have TWRP installed, instructions say it should reboot itself, but doing it from recovery I'm not sure, just make sure it says its done PC side then manually reboot if necessary
If all goes well, flash a new ROM from TWRP

*Detection* said:
From a quick look at the PERI files I would assume this method:
Boot the tablet into CWM and connect it to the PC > USB
Download and extract the PERI files, right click and run EasyRecoveryV0.4.bat as Admin
Once its done you should have TWRP installed, instructions say it should reboot itself, but doing it from recovery I'm not sure, just make sure it says its done PC side then manually reboot if necessary
If all goes well, flash a new ROM from TWRP
Click to expand...
Click to collapse
I really appreciate the help man!
PERI isn't working through recovery mode I guess. The tablet will show up as a device ONLY in device manager and I cannot access any of the storage and it isn't recognizing my SD card that I literally bought new a couple days ago. Please let me reiterate. I only have access to the "stuck" screen of EEE slider and can only get as far as the CWM recovery and using the volume and power buttons to navigate. i CANNOT get past this god forsaken screen.
Those of you guys who have the patience to help people in need FOR FREE are amazing and truly deserve a kings ransom! thanks again for the help so far! I hope we can get through this!

chchas said:
I really appreciate the help man!
PERI isn't working through recovery mode I guess. The tablet will show up as a device ONLY in device manager and I cannot access any of the storage and it isn't recognizing my SD card that I literally bought new a couple days ago. Please let me reiterate. I only have access to the "stuck" screen of EEE slider and can only get as far as the CWM recovery and using the volume and power buttons to navigate. i CANNOT get past this god forsaken screen.
Those of you guys who have the patience to help people in need FOR FREE are amazing and truly deserve a kings ransom! thanks again for the help so far! I hope we can get through this!
Click to expand...
Click to collapse
Been there done that. I had to use adb commands to push a new recovery blob. What version of cwm are you using again?

I have always had to use this one. After having this exact same issue.
D

DatDude123 said:
I have always had to use this one. After having this exact same issue.
D
Click to expand...
Click to collapse
v6.0.1.3
Do you have instruction on how you fixed yours? or a link ?

http://forum.xda-developers.com/showthread.php?p=16557195
This is what saved me. Alk I flash now is arhd and revolver. I do not attempt jellybean any longer......it was me, a laptop, and the tablet connected via usb and using adb commands. You are about to learn a lot.
D

So are there any handy links to a step by step of this? i found one for a Prime but i don't think it's the same thing....

So I followed this guide for adb http://forum.xda-developers.com/showthread.php?t=1071584 and got all the way to the end'. Now i'm stuck, where do I go from here? I don't want to screw anything up so any pointers will help!
Also, i can do this adb stuff while in recovery mode right?
Thanks!

A700 - Can't go into Recovery Mode ,OS OK, Root OK, FBoot Unlocked

Hello Guys,
i have made something wrong. i wanted to install the OTA JB Image from internal SD and i was thinking it would work with CWM.
First step i have made is, unlocked the bootloader with adb.exe etc...
The Second Step was to get root and superuser (here maybe i have done something wrong) but in the end i got superuser to work with a patched bootloader or something.
The Third Step i installed CWM and started to flash the recovery image.
But it doesnt go any further, if i try to go into recovery mode, it stucked always at the message "boot recovery kernel". from here its frozen.
i have two recovery images to choice with CWM, One is calling TeamWin Recovery Image and the other is the CWM Recovery. But both doesnt work. I tried to go directly from CWM to the recovery mode and with the Power Button and Vol + Method. Both not working. If i try to boot manually first it says "it update via sdcard" or something, and immiadately it follows the message "boot recovery kernel" and stucked....Nothing happened
Thats a big problem because i cant update anymore and i dont have an externel sd card here. And via google i cant find a solution to this problem.
Is there a Method to install a new Recovery.img via adb? that work properly?
Maybe someone can help me out?
Greetings
Jack
Sorry for my bad English.
[EDIT] i have solved the problem by my own. I've flashed the wrong recovery img. Now i have flashed that version for ICS with vorbeths Easy Root. And now i can Update the version. Hope there will be no more problems...

Please steps
JacKJodel23 said:
Hello Guys,
i have made something wrong. i wanted to install the OTA JB Image from internal SD and i was thinking it would work with CWM.
First step i have made is, unlocked the bootloader with adb.exe etc...
The Second Step was to get root and superuser (here maybe i have done something wrong) but in the end i got superuser to work with a patched bootloader or something.
The Third Step i installed CWM and started to flash the recovery image.
But it doesnt go any further, if i try to go into recovery mode, it stucked always at the message "boot recovery kernel". from here its frozen.
i have two recovery images to choice with CWM, One is calling TeamWin Recovery Image and the other is the CWM Recovery. But both doesnt work. I tried to go directly from CWM to the recovery mode and with the Power Button and Vol + Method. Both not working. If i try to boot manually first it says "it update via sdcard" or something, and immiadately it follows the message "boot recovery kernel" and stucked....Nothing happened
Thats a big problem because i cant update anymore and i dont have an externel sd card here. And via google i cant find a solution to this problem.
Is there a Method to install a new Recovery.img via adb? that work properly?
Maybe someone can help me out?
Greetings
Jack
Sorry for my bad English.
[EDIT] i have solved the problem by my own. I've flashed the wrong recovery img. Now i have flashed that version for ICS with vorbeths Easy Root. And now i can Update the version. Hope there will be no more problems...
Click to expand...
Click to collapse
How did you do that? could please put steps or that alike? I rooted my a700 and put the iconian rom but i wanted to put Cyanogen but it gets stuck like you said, I also installed iconian using Rom managerm please help!

[Q] Help Needed: Unbrick my P500!

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..

Can't Boot Recovery Philz Touch - Root Lost

I was running Alliance rom and decided I wanted to try a couple different roms. I had previously installed Philz touch recovery 6.48.4 and had no issues with it. So I went into recovery and did the 'clean to install new rom' option and then I installed the Beanstalk 4.4.285 rom and checked it out and then was going to wipe it and try out Paranoid Android 4.45 so I rebooted to recovery again using the script in Rom Toolbox which is how I had been rebooting in to recovery since having installed Philz Touch because it's just simpler than holding the hardware keys. I had never tried booting in to Philz recovery using hardware keys. So anyways once in recovery again I once again do the 'clean to install new rom' option and then I went to flash Paranoid Android and I get a message about (can't remember exactly what it said) root being lost and was asked If I want to (again not sure exactly what it said) push su back to system/xbin and I said yes at which point the phone rebooted and now I can not reenter Philz recovery. I have tried numerous key combos including V+,home, power ; V+,power : V-,Power : V-,home,power ; V-,V+,power, V-,V+,home,power and nothing. It just boots to the Samsung Galaxy SIII screen and sits there. When I tried the V-,Home,power combo I get a screen that reads something like "Warning a custom os can cause critical problems in phone and installed applications. If you want to download a custom OS press the volume up key...." I think that is download mode but not sure. How can I get back in to Philz and or regain root if lost and reflash back to Alliance? Hope I didn't brick it.

DuhCiphered said:
I was running Alliance rom and decided I wanted to try a couple different roms. I had previously installed Philz touch recovery 6.48.4 and had no issues with it. So I went into recovery and did the 'clean to install new rom' option and then I installed the Beanstalk 4.4.285 rom and checked it out and then was going to wipe it and try out Paranoid Android 4.45 so I rebooted to recovery again using the script in Rom Toolbox which is how I had been rebooting in to recovery since having installed Philz Touch because it's just simpler than holding the hardware keys. I had never tried booting in to Philz recovery using hardware keys. So anyways once in recovery again I once again do the 'clean to install new rom' option and then I went to flash Paranoid Android and I get a message about (can't remember exactly what it said) root being lost and was asked If I want to (again not sure exactly what it said) push su back to system/xbin and I said yes at which point the phone rebooted and now I can not reenter Philz recovery. I have tried numerous key combos including V+,home, power ; V+,power : V-,Power : V-,home,power ; V-,V+,power, V-,V+,home,power and nothing. It just boots to the Samsung Galaxy SIII screen and sits there. When I tried the V-,Home,power combo I get a screen that reads something like "Warning a custom os can cause critical problems in phone and installed applications. If you want to download a custom OS press the volume up key...." I think that is download mode but not sure. How can I get back in to Philz and or regain root if lost and reflash back to Alliance? Hope I didn't brick it.
Click to expand...
Click to collapse
I've used philz but only on my tablet. I prefer using terminal emulator to reboot if I need to. And the last part yes that is download mode. You can always try Odin
Sent from my SCH-I535 using Xparent ICS Tapatalk 2

ShapesBlue said:
I've used philz but only on my tablet. I prefer using terminal emulator to reboot if I need to. And the last part yes that is download mode. You can always try Odin
Sent from my SCH-I535 using Xparent ICS Tapatalk 2
Click to expand...
Click to collapse
I figured it out. I feel stupid though. I was really freaking out hoping I didn't brick my phone, couldn't you just hear the panic in my post. The first key combo I used to boot recovery was correct I just wasn't doing it right. I was pressing V+,home,power and waiting for the samsung logo before letting go and that's why it wasn't working. But I found out the correct method is to hold down V+ and home then hold down power also and wait for the phone to vibarate then let go of the power button but continue to hold down V+ and home until recovery boots.
I was about ready to try reflashing recovery via odin but I was a bit concerned about a few things when it comes to that. If I do need to use odin in the future is there a specific version I should use for the S3. I downloaded Odin3 v3.07 and also have 1.85. I know your phone needs to be in download mode to use it, so now I know how to boot to download mode at least. My bootloader is unlocked and I was wondering if using odin would lock it or affect that in anyway or have any other type of ill effect on my phone?

DuhCiphered said:
I figured it out. I feel stupid though. I was really freaking out hoping I didn't brick my phone, couldn't you just hear the panic in my post. The first key combo I used to boot recovery was correct I just wasn't doing it right. I was pressing V+,home,power and waiting for the samsung logo before letting go and that's why it wasn't working. But I found out the correct method is to hold down V+ and home then hold down power also and wait for the phone to vibarate then let go of the power button but continue to hold down V+ and home until recovery boots.
I was about ready to try reflashing recovery via odin but I was a bit concerned about a few things when it comes to that. If I do need to use odin in the future is there a specific version I should use for the S3. I downloaded Odin3 v3.07 and also have 1.85. I know your phone needs to be in download mode to use it, so now I know how to boot to download mode at least. My bootloader is unlocked and I was wondering if using odin would lock it or affect that in anyway or have any other type of ill effect on my phone?
Click to expand...
Click to collapse
No Odin has nothing to do with the bootloader.
Sent from my SCH-I535 using Xparent ICS Tapatalk 2