Blaze recovery not working - Samsung Galaxy S Blaze 4G

Im brand new to android i have used iOS for the past 3 years. I have rooted my blaze and flashed into cwm recovery , but i cant go into it . It just displays green and red dots if i boot into it . Please help me
Sent from my SGH-T769 using XDA

Welcome to android! I'm not a guru by any means, but make sure you are using the CWM from the Blaze recovery thread that is flashed through Odin. I don't think any others like the ones available through ROM Manager will work. I use GooManager to reboot into that recovery and it works great. Good luck.

Thats the problem. I accidently flashed the recovery to some other model and I cant get it to go back.

Ah, I see. There is a thread for returning to stock under the Blaze Dev section. It sounds like you should start over with that.
At this point, it's probably best to only use both the root and recovery threads in the Blaze forum. The devs are doing a great job with this phone, but it's at the beginning stages so far.

manuja22 said:
Thats the problem. I accidently flashed the recovery to some other model and I cant get it to go back.
Click to expand...
Click to collapse
Go to the CWM thread and flash that, you will have a working CWM on your phone.

i came into this thread thinking there was an issue with the cwm i had compiled. not i flashed [insert phone's recovery]

It works great Shabby thanks for your work!

shabbypenguin said:
i came into this thread thinking there was an issue with the cwm i had compiled. not i flashed [insert phone's recovery]
Click to expand...
Click to collapse
Should we BIG RED LETTERS about ROM Manager?

well in all honesty rom manager will work fine in regards that should koush accept it. the recovery is 90% tmobile sgs2 all i did is compile it and figure out the necessarily changes to make it display properly.
did we ever find out what the code name was for this device? (tmobile sgs2 is hercules, epic 4g was victory etc etc)
i did try to build twrp2.1 for you guys but it seems it hits teh black screen of death all the other samsung devices get :/

Guys thank you all for your support , but as i said before , the recovery is not working it boots into a black screen with green and red dots . Therefore , odin cannot recognize it and nothing happens on the phons
Sent from my SGH-T769 using XDA

Just to cover all bases... I don't think you should be booting to recovery at this point. You should try to boot to 'download mode', which involves holding down both volume buttons as you power on. There is a video on how to do it in the CWM how-to. Hope this helps.

Related

Think I've Bricked my Nexus One

Right I rooted my N1 today, all went fine, then I had some issues trying to install a new recovery image (still on stock recovery right now) and I've rebooted my N1 and INSTANTLY AFTER the screen with the big X and the padlock my screen turns off. Everything seems to work but u can't see anything.
I can access fastboot and recovery so it seems like there may be some hope for my phone. Any ideas people?
addam360 said:
Right I rooted my N1 today, all went fine, then I had some issues trying to install a new recovery image (still on stock recovery right now) and I've rebooted my N1 and INSTANTLY AFTER the screen with the big X and the padlock my screen turns off. Everything seems to work but u can't see anything.
I can access fastboot and recovery so it seems like there may be some hope for my phone. Any ideas people?
Click to expand...
Click to collapse
good news is its not bricked, just flash new rom from recovery...
read the tutorials on doing this, and I suggest going to the n1 forums on this site
tbirdguy said:
good news is its not bricked, just flash new rom from recovery...
read the tutorials on doing this, and I suggest going to the n1 forums on this site
Click to expand...
Click to collapse
Cheers thats great news! Only issue is I have the stock recovery image and my laptop isn't working exactly right when I try to flash a new recovery image. I'll have to work on setting it up right I guess but since now I know it'll work its worth it. Already gone most of today without a phone and theres no way I'm reverting to my Motorola DEXT.
Thanks.

[Q] bricked / backup troubles..

Rooted successfully, flashed cwm's most recent recovery and made a backup,i go and DL miui and try to flash that and get a neverending bootloop , so i go into recovery and try to go to backup/restore and my power button wont work.. aka im trying to select the option to do my backup and it isnt responding.. but it does respond correctly when going into recovery/ download mode.. help.
samsung galaxy s2 epic 4g.. sprint version
Where did you get cwm from?
Sent from my GT-P7510 using xda premium
jager555 said:
Where did you get cwm from?
Sent from my GT-P7510 using xda premium
Click to expand...
Click to collapse
from market earlier
power button did work for me the one time prior i tried to flash a rom and didnt have success, and i used my backup successfully. using my power button as selector in cwm recovery. but now i just cant get my power button to respond while in recovery i can scroll up and down no problemo.. sorry for late responses im a new user and there is a 5min wait between posts
If you got cwm from market then you made a mistake. Rom manager does not work correctly for the sgs4g.
Sent from my SGH-T959V using xda premium
dam, worked fine for me the first time i used it. what does this mean for me? how do i get out of this hole i dug myself, i was watching the zedomax vids and it said to get the current cwm recovery off of the market so i was just trying to follow instructions unless i heard wrong.
Made this post in wrong thread meant to have it under ssgs2 e4g, please forward any comments and suggestions there thankyou, and sorry for posting wrong location
http://forum.xda-developers.com/showthread.php?p=18479010#post18479010
Wait, your OP said you have the Samsung Galaxy SII Spring Version (Epic 4G Touch). That's a completely different device. This is the Samsung Galaxy S 4G.
I'm not even sure if that phone has root yet, since it's relatively new. I never checked on those forums.
EDIT: I guess I took a bit too long to type this message. That's what happens when I multitask!
Flashed lost kernel = fix
Sent from my SPH-D710 using XDA App

My Replacement S3 will not boot into custom recovery??

Hello,
I just got my replacement S3 and I rooted it with SuperSu-GS3_Debugfs and then unlocked my bootloader with the tool posted here and then I downloaded Goomanager and installed a custom recovery but it continues to boot into the Samsung recovery...? I never had this issue before.... Right after Goomanager downloaded the recovery I was able to enter custom recovery once so that I could make a backup but after I made a backup I cannot get back into custom...? Weird, maybe I am just tired but I have done this plenty of times and don't see why it's not working... This is the first replacement that I received with the newest Verizon OTA on it though... Other than that I don't see what the deal is? Thanks in advance!! I'm sure it is something simple I am missing here...
Download ez recovery and just reinstall the recovery.
Sent from my sexy white Eclipsed galaxy S3
kintwofan said:
Download ez recovery and just reinstall the recovery.
Sent from my sexy white Eclipsed galaxy S3
Click to expand...
Click to collapse
I thought of that but I just don't understand why Goomanager would not do it.... I really want TWRP so that is my main goal here... You think goomanager is the culprit even though it allowed me to enter TWRP to make a backup already....?
Did it ever boot into recovery? The first time I was in cwm recovery it went then I clicked through a screen that asks you to click yes to boot into it every time. When I rebooted to recovery it took me to stock recovery. I went into rom manager and flashed it again, then made sure I chose yes on the screen that warns you that it might boot into stock recovery.
Sent from my SCH-I535 using XDA Premium HD app
edjm711 said:
Did it ever boot into recovery? The first time I was in cwm recovery it went then I clicked through a screen that asks you to click yes to boot into it every time. When I rebooted to recovery it took me to stock recovery. I went into rom manager and flashed it again, then made sure I chose yes on the screen that warns you that it might boot into stock recovery.
Sent from my SCH-I535 using XDA Premium HD app
Click to expand...
Click to collapse
Yes I made my first backup in TWRP after I flashed it.... Now it will go straight to Samsungs recovery...
EDIT: Just tried the recovery program from the app store and it's doing the same thing....? I can get into custom recovery once and after I reboot I seem to lose it? This **** is weird!
Anybody??
What build number is it? I remember on my droid charge Samsung put a command to flash stock recovery on boot. You could just install the recovery, boot into it and immediately install a custom ROM.
Sent from my sexy white Eclipsed galaxy S3
kintwofan said:
What build number is it? I remember on my droid charge Samsung put a command to flash stock recovery on boot. You could just install the recovery, boot into it and immediately install a custom ROM.
Sent from my sexy white Eclipsed galaxy S3
Click to expand...
Click to collapse
It is baseband version I535VRLG7
IMM76D.I535VRALG7- build number
This is just the latest build right? I should not have any issues... Its got me sooo pissed off right now!
Ya that's strange? You could try to Odin rout66 or a stock ROM and try again
Sent from my sexy white Eclipsed galaxy S3
kintwofan said:
Ya that's strange? You could try to Odin rout66 or a stock ROM and try again
Sent from my sexy white Eclipsed galaxy S3
Click to expand...
Click to collapse
Ya I am trying that now.... Thanks for the replies though! :good:
kintwofan said:
What build number is it? I remember on my droid charge Samsung put a command to flash stock recovery on boot. You could just install the recovery, boot into it and immediately install a custom ROM.
Sent from my sexy white Eclipsed galaxy S3
Click to expand...
Click to collapse
Okay... So as you said earlier about your Charge, I think Verizon is getting tricky here cause I tried EVERYTHING and I had to flash a custom rom to get my custom recovery to stick on the latest build and I have never had to do that.... This has never been an issue so something has changed?? I finally got Cleanrom on it with TWRP cause I was determined not to go back to the old build! I installed TWRP again and again but it would not stick after a reboot so I just quickly flashed a rom while I was in TWRP and I'm golden now so idk what the deal was.... Verizon is a pain in my ASS!!! I never had to go through all this **** to install a rom on this device. Glad I had patience today cause I was gettin angry!! Oh well it is solved for the moment.... :victory: I am glad that at least one person tried to help me out ( kintwofan).... I thought I would have gotten more feedback but I guess that's what I get for thinkin...
Glad you got it going
Sent from my sexy white Eclipsed galaxy S3
kintwofan said:
Glad you got it going
Sent from my sexy white Eclipsed galaxy S3
Click to expand...
Click to collapse
You just about got all my thanks today just because you at least tried to give me a solution.... Soooo Thanks! LOL
No problem, since I can't develop I try to help in some way.
Sent from my sexy white Eclipsed galaxy S3
kintwofan said:
No problem, since I can't develop I try to help in some way.
Sent from my sexy white Eclipsed galaxy S3
Click to expand...
Click to collapse
Ya me too but I was kinda let down today.... Oh well, people got their own **** to deal with I guess but this was really my first time I was REALLY in need for some help and no one showed up to the party.... LOL Have a good night buddy! Thread closed!
That also happened to me.
After upgrading to latest AT&T OTA same thing happened to me.
I downloaded ROM Manager and instaled CWM recovery.
I was able to reboot in recovery once and then at boot a message would appear saying (something really fast) and then back to stock recovery.
Anyway in ROM manager it would recognize again that I had flashed the CWM recovery.
After I installed CWM touch it stop doing it. SO.
Best luck
I'm due to get my replacement tomorrow but what's funny is I ran into the same issue with my current device after I had gone back to stock and rooted again. Thinking it just has something to do with the update they pushed but ill report back tomorrow after I get it all rooted to see if I run into it again.
Sent from my SCH-I535 using xda app-developers app
There is a file somewhere I'm not sure that you can delete and it should stop this. It is strange though because I don't recall this being an issue with this phone. I'll see if I can't find where that file would be.
imurg said:
After upgrading to latest AT&T OTA same thing happened to me.
I downloaded ROM Manager and instaled CWM recovery.
I was able to reboot in recovery once and then at boot a message would appear saying (something really fast) and then back to stock recovery.
Anyway in ROM manager it would recognize again that I had flashed the CWM recovery.
After I installed CWM touch it stop doing it. SO.
Best luck
Click to expand...
Click to collapse
bc760 said:
I'm due to get my replacement tomorrow but what's funny is I ran into the same issue with my current device after I had gone back to stock and rooted again. Thinking it just has something to do with the update they pushed but ill report back tomorrow after I get it all rooted to see if I run into it again.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
JBO1018 said:
There is a file somewhere I'm not sure that you can delete and it should stop this. It is strange though because I don't recall this being an issue with this phone. I'll see if I can't find where that file would be.
Click to expand...
Click to collapse
Ya this was my first time I had ever encountered a problem and I have had 3 different refurbs.... So what they are doing is forcing the device to go into Samsung's recovery instead of your custom... But as long as you transfer a rom over the first time you boot into custom recovery and flash it your all good.... Just took me awhile to figure it out... Them bastards!! LOL
I did mine this weekend but it had been rooted prior to the OTA update, and I didnt do the update, I'm running AOKP JB..
My GFs has the update and just now I tried doin hers to put JB on it and it won't boot into CWM, just keeps goin to the Samsung recovery. I used the EZ-unlock tool v1.2, and Odin to put CWM on.
Hopefully we can get some help....
---------- Post added at 09:34 PM ---------- Previous post was at 09:25 PM ----------
OK, HA, shoulda read some first
So if I flash a custom rom through odin I can do this? Can someone point me to somewhere there is a guide?
I'm new to this stuff, my last phone was a motorola i3. LOL

Methinks I hath killed it....

Sooo....
Been reading, researching and studying for a little more than two weeks now on rooting my S3, flashing roms, kernels, etc. Most of the 2 weeks my S3 has been rooted. I felt brave enough early on to do that, but only worked up the courage to flash my first rom this morning. Using the guide found here...
http://forum.xda-developers.com/showthread.php?t=1762709
...I flashed the newly updated "SynergyROM VZW S3 | JB 4.1.1 | Multiwindow | PDroid | 1-10-13 r169" and to my delight it worked like a charm! For most of the day today I've been learning the ins and outs of my new rom and loving it!
This evening I decided that due to my success I'd give flashing a kernel a try. I apparently should've quit while I was ahead. I found this kernel : "SGS3-VZW-kernel-jb-cm-u-10312012" I followed the above mentioned guide again and followed all of the instructions up through step 6. I unzipped the kernel, and prior to rebooting I was unexpectedly asked a question about if I wanted to restore the stock recovery (if I remember it correctly). I chose the "go back" option (to see if I could just reboot without worrying about that question) in CWM and my S3 rebooted itself at that point.
Unfortunately the reboot process got through the quick glimpse of "Samsung", then the "Galaxy S3" screen then went black and that was it. I waited a while, removed the battery to be sure it was off and tried starting up again. Same result. I've tried rebooting into recovery (vol down/ home/power) but it just shows me the same two screens and goes black, never going into recovery and never taking me to the download screen.
I decided to plug the S3 into my computer to see if I could see it in Windows Explorer (I couldn't) but I fired up Odin and it is showing that it recognizes the S3 is plugged in in the ID:COM box.
Should I attempt flashing the stock rom through Odin even though I can't get the S3 into the download screen and even though it seems the kernel is what caused my problem? Or does it not really matter at this point....is it hard bricked? I survived a soft brick last week so I have the stock rom all ready to go, but I don't want to just try Odin'ing it in without the advice of those more schooled in this than I am.
I'm not a complete idiot. My device is a Verizon Galaxy S3, I535. I've been very careful about choosing the correct roms and kernels for my device....at least I thought I had.
Any suggestions and/or advice? Perhaps I should blow the dust off my Droid X to use until I send the GS3 out for JTAG repair. Heh.
Thanks in advance from a very humbled Noob.
Well did you try to put it in download mode not recovery but download
I don't believe it's hard bricked i think you can get past this of you did put it in download mode and Odin sees it i would push the ROM
Sent from my SAMSUNG-SGH-I577 using xda premium
---------- Post added at 07:48 PM ---------- Previous post was at 07:44 PM ----------
On my phone i have to take the battery out hit the volume down button and power button at the same time then plug into the computer then it goes into download mode. It sounds like you know how to do it..
Sent from my SAMSUNG-SGH-I577 using xda premium
djteague said:
Sooo....
Been reading, researching and studying for a little more than two weeks now on rooting my S3, flashing roms, kernels, etc. Most of the 2 weeks my S3 has been rooted. I felt brave enough early on to do that, but only worked up the courage to flash my first rom this morning. Using the guide found here...
http://forum.xda-developers.com/showthread.php?t=1762709
...I flashed the newly updated "SynergyROM VZW S3 | JB 4.1.1 | Multiwindow | PDroid | 1-10-13 r169" and to my delight it worked like a charm! For most of the day today I've been learning the ins and outs of my new rom and loving it!
This evening I decided that due to my success I'd give flashing a kernel a try. I apparently should've quit while I was ahead. I found this kernel : "SGS3-VZW-kernel-jb-cm-u-10312012" I followed the above mentioned guide again and followed all of the instructions up through step 6. I unzipped the kernel, and prior to rebooting I was unexpectedly asked a question about if I wanted to restore the stock recovery (if I remember it correctly). I chose the "go back" option (to see if I could just reboot without worrying about that question) in CWM and my S3 rebooted itself at that point.
Unfortunately the reboot process got through the quick glimpse of "Samsung", then the "Galaxy S3" screen then went black and that was it. I waited a while, removed the battery to be sure it was off and tried starting up again. Same result. I've tried rebooting into recovery (vol down/ home/power) but it just shows me the same two screens and goes black, never going into recovery and never taking me to the download screen.
I decided to plug the S3 into my computer to see if I could see it in Windows Explorer (I couldn't) but I fired up Odin and it is showing that it recognizes the S3 is plugged in in the ID:COM box.
Should I attempt flashing the stock rom through Odin even though I can't get the S3 into the download screen and even though it seems the kernel is what caused my problem? Or does it not really matter at this point....is it hard bricked? I survived a soft brick last week so I have the stock rom all ready to go, but I don't want to just try Odin'ing it in without the advice of those more schooled in this than I am.
I'm not a complete idiot. My device is a Verizon Galaxy S3, I535. I've been very careful about choosing the correct roms and kernels for my device....at least I thought I had.
Any suggestions and/or advice? Perhaps I should blow the dust off my Droid X to use until I send the GS3 out for JTAG repair. Heh.
Thanks in advance from a very humbled Noob.
Click to expand...
Click to collapse
I think you flashed the kernel for cm, and not for touchwiz.
djteague said:
Sooo....
"SGS3-VZW-kernel-jb-cm-u-10312012"
Click to expand...
Click to collapse
This is an AOSP kernel. You only flash kernels if they match your rom. Synergy is a TouchWiz rom, so you would only flash a kernel if it states it's for TouchWiz. CM =CyanogenMod, an AOSP rom. AOSP = Android Open Source Project. Basically, AOSP is stock Android but on phones that don't ship with stock Android like a Nexus device.
Should I attempt flashing the stock rom through Odin even though I can't get the S3 into the download screen and even though it seems the kernel is what caused my problem?
Click to expand...
Click to collapse
Yes, Odin flash a stock image then re-rooted and unlock your bootloader again. Just like what the other folks have said above. "Fool me once..." as the saying goes.
Sent from my SCH-I535 using xda app-developers app
SlimSnoopOS said:
This is an AOSP kernel. You only flash kernels if they match your rom. Synergy is a TouchWiz rom, so you would only flash a kernel if it states it's for TouchWiz. CM =CyanogenMod, an AOSP rom. AOSP = Android Open Source Project. Basically, AOSP is stock Android but on phones that don't ship with stock Android like a Nexus device.
Yes, Odin flash a stock image then re-rooted and unlock your bootloader again. Just like what the other folks have said above. "Fool me once..." as the saying goes.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Get him SlimSnoop. :laugh:
So reflashing the stock rom will in essence erase the AOSP kernel? It won't still be there to continue to cause problems after I Odin in the stock rom?
I'm getting an education now! Thanks so much for the continued help!
djteague said:
So reflashing the stock rom will in essence erase the AOSP kernel? It won't still be there to continue to cause problems after I Odin in the stock rom?
I'm getting an education now! Thanks so much for the continued help!
Click to expand...
Click to collapse
Odin flash will reset everything to factory settings. You'll just have to reroot and unlock once again.
Edit: Since I re-read your post. Volume down, home, and power will take you to download mode. This still works correct?
SlimSnoop you are turning what was a rather bummer of a night around! One final question before I push the start button in Odin...
I can flash the stock rom even though my S3 doesn't appear to be in dowload mode? (although the ID:COM box shows that Odin sees my phone)
Thanks again!
djteague said:
SlimSnoop you are turning what was a rather bummer of a night around! One final question before I push the start button in Odin...
I can flash the stock rom even though my S3 doesn't appear to be in dowload mode? (although the ID:COM box shows that Odin sees my phone)
Thanks again!
Click to expand...
Click to collapse
What do you mean it "doesn't appear to be in download mode"? When you pull the battery/reinsert then hold volume down, power, and home for like ten seconds, what does it do? Do you get the prompt to to boot into download mode?
SlimSnoopOS said:
What do you mean it "doesn't appear to be in download mode"? When you pull the battery/reinsert then hold volume down, power, and home for like ten seconds, what does it do? Do you get the prompt to to boot into download mode?
Click to expand...
Click to collapse
Don't hit no button if not in download mode.
Nevermind...my bad. Now my noobness is really starting to show. I had tried putting it into download when I first realized there was a problem, but apparently did something wrong. It worked this time, the stock rom is flashed and all is well.
Now, all that remains to be seen is whether or not this little adventure has scared me into being satisfied with my stock GS3 or if I go back to tinkering.
I truly thank you guys for holding my hand and getting me through this! Much obliged!
djteague said:
Nevermind...my bad. Now my noobness is really starting to show. I had tried putting it into download when I first realized there was a problem, but apparently did something wrong. It worked this time, the stock rom is flashed and all is well.
Now, all that remains to be seen is whether or not this little adventure has scared me into being satisfied with my stock GS3 or if I go back to tinkering.
I truly thank you guys for holding my hand and getting me through this! Much obliged!
Click to expand...
Click to collapse
Go back to custom roms and flash Synergy again!

[Q] Stuck in ''entering recovery...'' htc one s

What's up everybody! This is my first post here and I am what you would call a noob!
First of all I got tired of the 4.2.2 jb upgrade never coming to my htc one s and decided to give cyanogenmod 10.1 a shot (my first attempt ever tampering with mobile software)!
So I have unlocked the bootloader on my phone following a guide. It now says ''unlocked''
After that, I have tried to flash the paul recovery.img from this post http://forum.xda-developers.com/showthread.php?t=1583427 .
I have done it through adb with the command promt as it says on the article above!
The command promt apparently managed to do the job and it said ''finished'' as it should!
Then i rebooted the phone into recovery mode through the bootloader menu but it then stucks there doing nothing...I have left it for 5 minutes and it was still like that and i thought that the recovery wasn't succesful (i ve seen it going very fast at the clockworkmod menu at videos on youtube while mine was stuck). I then rebooted it by holding down the power button and it went to the sence screen normally.
Then i have tried the other recovery img described at the article...Same thing happened...Then the other one! Same thing again!
Every time i am trying to flash the recovery image the phone stucks in ''entering recovery...'' screen, doing nothing.
Am I doing something wrong?
Please help, it will be much appreciated! I really want to dig custom roms...I' m a total geek
Thanks in advance!!
letakgr said:
What's up everybody! This is my first post here and I am what you would call a noob!
First of all I got tired of the 4.2.2 jb upgrade never coming to my htc one s and decided to give cyanogenmod 10.1 a shot (my first attempt ever tampering with mobile software)!
So I have unlocked the bootloader on my phone following a guide. It now says ''unlocked''
After that, I have tried to flash the paul recovery.img from this post http://forum.xda-developers.com/showthread.php?t=1583427 .
I have done it through adb with the command promt as it says on the article above!
The command promt apparently managed to do the job and it said ''finished'' as it should!
Then i rebooted the phone into recovery mode through the bootloader menu but it then stucks there doing nothing...I have left it for 5 minutes and it was still like that and i thought that the recovery wasn't succesful (i ve seen it going very fast at the clockworkmod menu at videos on youtube while mine was stuck). I then rebooted it by holding down the power button and it went to the sence screen normally.
Then i have tried the other recovery img described at the article...Same thing happened...Then the other one! Same thing again!
Every time i am trying to flash the recovery image the phone stucks in ''entering recovery...'' screen, doing nothing.
Am I doing something wrong?
Please help, it will be much appreciated! I really want to dig custom roms...I' m a total geek
Thanks in advance!!
Click to expand...
Click to collapse
To boot into recovery, Hold VolumeDown + Power.
Edit: maybe you've done that, but make sure that you choose the correct recovery version. that is, match the version of your phone S3/S4 with the recovery.
Specific recovery for specific phone.
khan.orak said:
To boot into recovery, Hold VolumeDown + Power.
Edit: maybe you've done that, but make sure that you choose the correct recovery version. that is, match the version of your phone S3/S4 with the recovery.
I have booted of course into recovery by doing that!
Can you tell me where i can find the right recovery for my S3 model?
Click to expand...
Click to collapse
Here link
Sent from my HTC One S using Tapatalk 4 Beta
Thank you! Have you tried it yoursef?
Problem solved thanks to the mister above!!!!!Thank you very much! I'm now getting the jb upgrade!!!
letakgr said:
Problem solved thanks to the mister above!!!!!Thank you very much! I'm now getting the jb upgrade!!!
Click to expand...
Click to collapse
Have the same problem (HTC one at&t) and that link he has that I clicked gives you a page of LIKE A WHOLE LIST of versions.. How do you know which one to choose?
plus spent all night trying to download the recovery.img from clockworkmod.com as well as other links and all I get is this LONG encrypted script page displayed, and not an actual FILE that prompts you to download. going crazy here!
Chri5topher said:
Have the same problem (HTC one at&t) and that link he has that I clicked gives you a page of LIKE A WHOLE LIST of versions.. How do you know which one to choose?
plus spent all night trying to download the recovery.img from clockworkmod.com as well as other links and all I get is this LONG encrypted script page displayed, and not an actual FILE that prompts you to download. going crazy here!
Click to expand...
Click to collapse
The link works, i ve managed to do it but twrp is useless if you want to flash any roms...I have tried every known version of cm for htc one s and I can't flash any of them in my phone through the twrp recovery...Always fails for no apparent reason! If you want my advise, do not waste your time, cause it's almost certain that ig you flash any custom rom, you will loose the advantages of htc sense, including the camera performance and special effects and also the beautiful widgets...If anyone though knows how to flash a REALLY nice rom with twrp we will be glad to hear his/her suggestions!
letakgr said:
The link works, i ve managed to do it but twrp is useless if you want to flash any roms...I have tried every known version of cm for htc one s and I can't flash any of them in my phone through the twrp recovery...Always fails for no apparent reason! If you want my advise, do not waste your time, cause it's almost certain that ig you flash any custom rom, you will loose the advantages of htc sense, including the camera performance and special effects and also the beautiful widgets...If anyone though knows how to flash a REALLY nice rom with twrp we will be glad to hear his/her suggestions!
Click to expand...
Click to collapse
sad part is I'm not going for anything fancy.. When I bought the phone (last week) it had version 4.1 on there and all I want to do is upgrade it to 4.2... and no it's NOT available through AT&T in anyways what's so ever.. hence the flash recovery chaos.
If no one response with a solid solution, then I'm just gonna let it be like you said.
Chri5topher said:
sad part is I'm not going for anything fancy.. When I bought the phone (last week) it had version 4.1 on there and all I want to do is upgrade it to 4.2... and no it's NOT available through AT&T in anyways what's so ever.. hence the flash recovery chaos.
If no one response with a solid solution, then I'm just gonna let it be like you said.
Click to expand...
Click to collapse
Tell me what do you want to do to your phone?
State in points, easy for me
blah
No it wont affect.
By the way, TWRP recovery has been the most successful one with The One S.
Google twrp and Download it for VILLE (THE S4 MODEL HTC ONE S) and then flash it.
Sent from my Nexus 7 using Tapatalk HD
khan.orak said:
No it wont affect.
By the way, TWRP recovery has been the most successful one with The One S.
Google twrp and Download it for VILLE (THE S4 MODEL HTC ONE S) and then flash it.
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
but.. I don't have the one S.. I have.. just.. the ONE .. HTC ONE ha ha.. dude.. I don't know, cause I've been using the iphone since it's FIRST generation! so ALL this is new to me, but I am tech savvy enough to try to go the distance on this phone.
Chri5topher said:
but.. I don't have the one S.. I have.. just.. the ONE .. HTC ONE ha ha.. dude.. I don't know, cause I've been using the iphone since it's FIRST generation! so ALL this is new to me, but I am tech savvy enough to try to go the distance on this phone.
Click to expand...
Click to collapse
The One. Try the specific threads for the One.
Sent from my Nexus 7 using Tapatalk HD
HTC ONE S Stuck with "Entering Recovey" message
letakgr said:
Problem solved thanks to the mister above!!!!!Thank you very much! I'm now getting the jb upgrade!!!
Click to expand...
Click to collapse
how did you resolved this issue, currently I am facing same issue, mobile got stuckn with the message "entering recovery". Please help.

Categories

Resources