hey guys I tried looking into the forums and tried to google but I'm having a hard time entering CWM. I rooted my phone today successfully right away I installed cwm recovery and did a nandroid. I tried to install beastmode 4.0 and I flashed the .zip file for the conversion. I rebooted my phone and now im stuck in a blue samsung screen. it's been like this for an hour. I came from an evo 4g and I cant seem to get into recovery. Ive tried pressing up and down volume key and power at the same time and letting go of the power switch when the screen flickered but no go. Is there something i'm doing wrong?
p.s Im really sorry to be asking this but I just bought the phone and I hope I didnt brick my phone
There is always the watt to flash back to stock using Odin Samsung phones are very hard to brick
Sent from my SGH-I727 using XDA Premium App
Go here do this http://forum.xda-developers.com/showthread.php?t=1342348. Complete guide to use odin for flashig the stock tar. And then re root and boot into cwm recovery and flash data, and cache 3 times each before flashing your rom....
I flashed CWM 5.8.3.1 and rooted the phone. Everything seems to be fine, except when I reboot form the recovery every time, it gives an "abnormal reset" error with the option to report to HTC. Is this normal?
Thanks!
Same here with CWM v5.1.8.5.
Everything is working although I havnt tried to flash a custom ROM yet.
It's because you used an app or adb to reboot phone into recovery. It's like turning off pc by hitting power button instead of shut down.
If u power it off and reboot into recovery using power and vol down buttons u won't get that
Sent from my HTC VLE_U using Tapatalk 2
I have to say that this is the most finicky phone I've had as far as booting to recovery manually. Sometimes it works, sometimes it doesn't.
Apparently, I haven't found this phone's g-spot yet
It has something to do with the CMW (not being signed?) If I flash the stock recovery back, the error goes away.
Hey all, i wiped my system in TWRP recovery and when i hold power, home, and vol down, i get to the TWRP splash screen but then i reboot. Any suggestions?
bump please help
So it will not boot into TWRP fully? How many times have you tried cuz if you rebooted accidentally after wiping system (I've done this), it takes a few tries.
Alternatively, you could Odin flash TWRP (file is in Open1your1eyes0 root thread) and try booting into TWRP then. This increments your flash counter.
Sent from my SCH-I535 using xda app-developers app
SlimSnoopOS said:
So it will not boot into TWRP fully? How many times have you tried cuz if you rebooted accidentally after wiping system (I've done this), it takes a few tries.
Alternatively, you could Odin flash TWRP (file is in Open1your1eyes0 root thread) and try booting into TWRP then. This increments your flash counter.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
ive tried around 8 or so, its worked before on my second ot third try but im getting no dice this time around, ill check out the odin file, thanks for the reply man =)
VinBertinelli said:
ive tried around 8 or so, its worked before on my second ot third try but im getting no dice this time around, ill check out the odin file, thanks for the reply man =)
Click to expand...
Click to collapse
No problem. You're saying its booting to the TWRP logo or booting to the Samsung logo? Just wanted to clarify.
Also, hold: power, home, and volume then once it boots release the power button. That seems to be the only way I can cold boot into recovery.
Sent from my SCH-I535 using xda app-developers app
SlimSnoopOS said:
No problem. You're saying its booting to the TWRP logo or booting to the Samsung logo? Just wanted to clarify.
Also, hold: power, home, and volume then once it boots release the power button. That seems to be the only way I can cold boot into recovery.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Yeah i hold home, power, and vol down, then it goes Samsung screen > Samsung Galaxy SIII screen > blue TWRP splash screen > reboot to system and freezes. And another thing, if i odin flash this TWRP, will it wipe internal storage by any chance? Its happened one too many times to me
VinBertinelli said:
Yeah i hold home, power, and vol down, then it goes Samsung screen > Samsung Galaxy SIII screen > blue TWRP splash screen > reboot to system and freezes. And another thing, if i odin flash this TWRP, will it wipe internal storage by any chance? Its happened one too many times to me
Click to expand...
Click to collapse
Hmm, weird. What were you doing before which led to this?
Nope, it doesn't wipe internal storage. Just overwrites your recovery partition. When Odin reboots your phone, pull the battery then try booting straight to TWRP. If you still can't boot into recovery try the same steps but flash CWM, flash a rom, and then reinstall TWRP via GooManager.
Sent from my SCH-I535 using xda app-developers app
SlimSnoopOS said:
Hmm, weird. What were you doing before which led to this?
Nope, it doesn't wipe internal storage. Just overwrites your recovery partition. When Odin reboots your phone, pull the battery then try booting straight to TWRP. If you still can't boot into recovery try the same steps but flash CWM, flash a rom, and then reinstall TWRP via GooManager.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Just flashed it and it still wouldn't fully boot TWRP. I'm about to try CWM now. What happened was i came from LiquidSmooth AOSP and I was ready to flash Hyperdrive Touchwiz so I wiped all the partitions and flashed the zip. The Aroma Installer froze before it started so i battery pulled and figured I'd retry. It wouldn't boot and now I'm where I am now.
SlimSnoopOS said:
Hmm, weird. What were you doing before which led to this?
Nope, it doesn't wipe internal storage. Just overwrites your recovery partition. When Odin reboots your phone, pull the battery then try booting straight to TWRP. If you still can't boot into recovery try the same steps but flash CWM, flash a rom, and then reinstall TWRP via GooManager.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
CWM WORKED! Thanks so much Slim, you're a life saver.
Always happy to help!
Sent from my SCH-I535 using xda app-developers app
Hello,
Earlier today I installed BAKED ROM on my AT&T HTC ONE XL that was at the time running CM 10.1 After having some issues with wifi not working I decided to restore from my backup made in CWR when installing CM 10.1 on my phone. After the restore finished i was stuck in a bootloop. So i went back into CWR to re install the BAKED ROM. Once i cleared drive i came to realize that i somehow deleted the .zip files for the ROM on my phone and no longer had a ROM to install. After that i decided that I would mount my phone from CWR so i can transfer the .zip to my phone and then install. After realizing i need to use TWRP to be able to mount and transfer files i was going to flash over TWRP in fastboot. My issue currently is that my phone is powered off after telling it to shutdown in bootloader, and i can not get it to turn back on or to boot into bootloader so that i can flash TWRP. Hopefully i am missing something small here. Any advise is appreciated.
Thank You
coltp10 said:
Hello,
Earlier today I installed BAKED ROM on my AT&T HTC ONE XL that was at the time running CM 10.1 After having some issues with wifi not working I decided to restore from my backup made in CWR when installing CM 10.1 on my phone. After the restore finished i was stuck in a bootloop. So i went back into CWR to re install the BAKED ROM. Once i cleared drive i came to realize that i somehow deleted the .zip files for the ROM on my phone and no longer had a ROM to install. After that i decided that I would mount my phone from CWR so i can transfer the .zip to my phone and then install. After realizing i need to use TWRP to be able to mount and transfer files i was going to flash over TWRP in fastboot. My issue currently is that my phone is powered off after telling it to shutdown in bootloader, and i can not get it to turn back on or to boot into bootloader so that i can flash TWRP. Hopefully i am missing something small here. Any advise is appreciated.
Thank You
Click to expand...
Click to collapse
hold the power button down for about 15 seconds. wait for 5 seconds, then press the power button and volume down at the same time after a few seconds you should get the bootloader screen.
does the led come on when you're charging it?
cr1960 said:
hold the power button down for about 15 seconds. wait for 5 seconds, then press the power button and volume down at the same time after a few seconds you should get the bootloader screen.
does the led come on when you're charging it?
Click to expand...
Click to collapse
Thank you for your response. From following your instructions i was still not able to get into bootloader, and when i plug it in to charge the LED does not come on
coltp10 said:
Thank you for your response. From following your instructions i was still not able to get into bootloader, and when i plug it in to charge the LED does not come on
Click to expand...
Click to collapse
Sadly based on my knowledge and experience(I learned this the hard way by taking the ATT OTA) if the led doesn't come on while charging and you cant access your bootloader your phone is sadly dead. However you can double check to see if its your cord and if it is not then call HTC if device is still under warranty. They replaced the internals of mine and recieved it back at no charge.
If I have helped in any way hit the Thanks button please.
Why did you "need" to go to TWRP to mount SD? Clockworkmod has had SD mount fixed for some time now, hasn't it?
Leave the phone on wall charger (not connected to computer) overnight or 8 Hrs or so, and see if you get any LED's or can get into bootloader. If you were only messing with ROMs and recovery, I don't see how you can be bricked (as long as anything you were trying to flash was for the EVITA). The battery may just have run down while you were messing with the device.
redpoint73 said:
Why did you "need" to go to TWRP to mount SD? Clockworkmod has had SD mount fixed for some time now, hasn't it?
Leave the phone on wall charger (not connected to computer) overnight or 8 Hrs or so, and see if you get any LED's or can get into bootloader. If you were only messing with ROMs and recovery, I don't see how you can be bricked (as long as anything you were trying to flash was for the EVITA). The battery may just have run down while you were messing with the device.
Click to expand...
Click to collapse
Well when i went into clockworkmod and told it to mount SD it did not work, i have all of my drivers installed properly so it couldn't be a driver issue. So i figured that i would just flash over TWRP and use mount to usb as a second shot. I will have to try and leave it plugged in later after work. Yes the ROM that i installed was for the EVITA, it was running fine except the wifi wouldnt turn on.
coltp10 said:
Well when i went into clockworkmod and told it to mount SD it did not work, i have all of my drivers installed properly so it couldn't be a driver issue.
Click to expand...
Click to collapse
If/when you get back up and running, if still on CWM, make sure its up to date. I think the SD mount was fixed quite some time ago.
redpoint73 said:
If/when you get back up and running, if still on CWM, make sure its up to date. I think the SD mount was fixed quite some time ago.
Click to expand...
Click to collapse
Okay thanks for the input i will check it out as soon as I am able
When i came home from work and plugged it in the red LED light came on. After letting it charge for about 5 hours i tried to access the bootloader by pressing power down for 15 seconds, then waiting 5, and then power and volume down, to no result. Only when holding down power for the first 15 seconds the soft on screen keys did flash
coltp10 said:
When i came home from work and plugged it in the red LED light came on. After letting it charge for about 5 hours i tried to access the bootloader by pressing power down for 15 seconds, then waiting 5, and then power and volume down, to no result. Only when holding down power for the first 15 seconds the soft on screen keys did flash
Click to expand...
Click to collapse
After holding the power button down and let the capacitive keys flash 6 times. The 6 flashes means a hard reset and it's about to start rebooting. Let go of the power button and immediately hold volume down. It should take you into the bootloader. Then you can fastboot flash TWRP.
Sent from my HTC One X using Tapatalk 2
Thank you
Finally after letting it charge all night, i was able to access my bootloader, i flashed over TWRP and am in the process of mounting my sd to transfer the rom and hopefully install. Thank you all for you help!!
coltp10 said:
Finally after letting it charge all night, i was able to access my bootloader, i flashed over TWRP and am in the process of mounting my sd to transfer the rom and hopefully install. Thank you all for you help!!
Click to expand...
Click to collapse
Good luck
Sent from my HTC One X using xda premium
Well i was able to install cm 10.1 back to my phone and successfully load it, my only issue now as before when i installed the BAKED rom, is my wifi doesn't seem to work or recognize any networks
coltp10 said:
Well i was able to install cm 10.1 back to my phone and successfully load it, my only issue now as before when i installed the BAKED rom, is my wifi doesn't seem to work or recognize any networks
Click to expand...
Click to collapse
Glad you got it working.
What hboot are you on? If you are on one of the newer ones, not 1.09, and don't have s-off you have to manually flash the boot.img through fastboot after installing the ROM. That sounds like it might be your issue.
pside15 said:
Glad you got it working.
What hboot are you on? If you are on one of the newer ones, not 1.09, and don't have s-off you have to manually flash the boot.img through fastboot after installing the ROM. That sounds like it might be your issue.
Click to expand...
Click to collapse
Agreed, i did forget to flash to boot image during my excitement to a working phone again, even so, if i hadn't flashed the boot image why is it that my phone was actually able to start up the rom and go through phone system setup?
coltp10 said:
Agreed, i did forget to flash to boot image during my excitement to a working phone again, even so, if i hadn't flashed the boot image why is it that my phone was actually able to start up the rom and go through phone system setup?
Click to expand...
Click to collapse
because the rom you flashed is based on CM so it was compatible enough to boot but not have everything working as it should. if you don't flash the boot.img, the previously used kernel would still be used.
The ROM was running and i was able to use my phone. Then i flashed over the boot.img for my rom and now it doesnt boot up it is stuck at the Cyanogen Mod loading screen
coltp10 said:
The ROM was running and i was able to use my phone. Then i flashed over the boot.img for my rom and now it doesnt boot up it is stuck at the Cyanogen Mod loading screen
Click to expand...
Click to collapse
boot to recovery, wipe everything (cache, dalvik, system, factory reset), reflash the rom you want to use, then reboot to bootloader and fastboot flash boot boot.img extracted from the rom you just flashed.
Not sure where you went wrong but that will get you booting. To avoid having to fastboot flash boot boot.img everytime, you can S-OFF.
exad said:
boot to recovery, wipe everything (cache, dalvik, system, factory reset), reflash the rom you want to use, then reboot to bootloader and fastboot flash boot boot.img extracted from the rom you just flashed.
Not sure where you went wrong but that will get you booting. To avoid having to fastboot flash boot boot.img everytime, you can S-OFF.
Click to expand...
Click to collapse
I will have to look into the S-OFF. As of right now i wiped everything, installed rom, installed gaps, went to bootloader flashed boot.img and now just waiting to see if it will start up
coltp10 said:
I will have to look into the S-OFF. As of right now i wiped everything, installed rom, installed gaps, went to bootloader flashed boot.img and now just waiting to see if it will start up
Click to expand...
Click to collapse
You can also use the flash image GUI app to flash a boot image in Android right before you boot to recovery to flash the ROM. But I would definitely look into s-off. It's a very easy process and then you don't ever have to worry about the boot.img at all.