was running viperXL 3.2.5 and wiped and went to cm10.1 now i used goo manager to download xhata (sorry i butchered it) now i can only boot into spash screen and bootloader. i used fastboot to reflash twrp and still only boots to the custom spash... hboot 1.09 s-off..... im kinda lost here. should have syuck with viper, why screw with perfection.
What is xhata? Is it a rom?
I'm not sure we can install roms with Goo Manager on this phone.
If you installed a rom for the quad-core Tegra One X, your phone will not boot and you're lucky you didn't get a brick. You need to do a full wipe and reflash.
first off not a noob. it was the evita rom. i still have bootloader access and can get half way into recovery( spash screen then twrp spash...) then reboot into custom splash. it was the rom... http://forum.xda-developers.com/showthread.php?t=2075783 so if anyone has any ideas please help, just dont start with the usual u screwed up flashing roms i know better. and the odd part is after reflashing the recovery via fastboot i get Twrp spash before going back to the phone main splash and boot looping.... and yes im s-off
No need to be so defensive. If we don't know exactly what you flashed, all we can do is ask. Its not meant as an insult. But its always better to ask the seemingly "obvious" questions first, get them out of the way.
If there is a "usual thing" that gets mentioned, its because the mistake of flashing ROMs for the ENDEAVORU in fact happens so often. Downloading from GooManager is not a great idea either, and often a red flag that someone installed a ROM for the wrong version of the phone.
Did the phone operate properly when you were on CM10.1?
What version of TWRP, and what fastboot command did you use to flash it?
I asked the "usual" questions because:
-You have less than 100 posts. That's often a sign of someone who is new to this.
-You used a rom name I've never heard of, and suggested you weren't sure of the name yourself. That's usually a big red flag for someone who flashed some random rom they found via Google.
-You mentioned using Goo Manager. That's a non-standard method for this phone, and an awful lot of people have bricked their phones trying to flash roms through apps that aren't well-supported. CWM Touch was notorious for this when the One X first came out.
If you don't want people to assume things, you need to state them up front.
On topic: There appears to be a bug in the latest TWRP that causes issues for some people. Try rolling back to an earlier version.
iElvis said:
On topic: There appears to be a bug in the latest TWRP that causes issues for some people. Try rolling back to an earlier version.
Click to expand...
Click to collapse
Yeah, I saw that too, and why I asked the OP what version of TWRP.
i had problems with that rom on version 4.0.1 and 4.1.0 had alot of errors and trouble. i haven't tried 4.2.0 though, i have been having better luck with rom after clearing out recovery cache running "fastboot erase cache" and running only twrp 2.3.3.1.
i flashed the second to last release of twrp (latest gave mount issues), viper was running great, cm 10.1 avatar was running fine just didnt like how plain it was so i used goo manager to download hatkaXL and when the download finished i picked select and flash.. then the usual warning about flashing and it rebooted, hit spash screen where it still is hours later. i then tried manually boot into recovery, it hit the bootloader i selected recovery and it seemed to try and load. next step was back to fast boot and to reflash twrp (fastboot flash recovery recovery.img ) flashed 100% success and still wont boot into recovery just the bootloader, and i wasnt trying to get all defensive, i sent first post using the wifes phone and posted quick, had a guy hooking up my satellite at same time as phone crashed. has anyone tried the new version of cwm for the evita? maybe flashing that may get me back, i have roms and backups on the pc that i can seem to side load but never boot as well.
well after repeated flashing of recovery and (fastboot erase cache) it finally booted to recovery, now to see if my backup will load.
Related
I did a lot of reading before I got into hacking my s3. I'm pretty new to the android development of Samsung phones, so the terms Odin and kexec are a little unfamiliar to me. I've owned and rooted and flashed 4 different HTC phones within the past 2 years successfully. But Samsung is a new ball game for me. And to my limited knowledge, I'm stuck and I'm hoping you guys can help me out.
Here's the process of what I did to my phone that got me to where I am.
1. I was able to root my phone and flash the custom recovery using using Adam outler's program successfully
2. I downloaded ez unlock boot loader from the play store and then successfully unlocked my boot loader
3. I tried to make a nandroid but I didn't know how to with the recovery I had. So I installed Rom manager and flashed cwm.
4. I downloaded the custom bean build 8 ROM, fully wiped, and attempted to flash the Rom with the Rom file sitting on the root of my phone's "sdcard"
- The zip seemed to flash correctly but then after I reboot from recovery, the screen would be sent back into recovery for some odd reason.
- I even tried to repeat the flashing process but it still resulted in sending me back to recovery after I hit reboot
5. So I restored my nandroid. Moved the Rom file to the root of extsdcard and then tried to flash it with cwm. It seemed to flash correctly once again but after I hit reboot, the phone shows the black splash screen with "Samsung galaxy s iii" in white letters then the phone shuts off. That's all that happens when I try to turn my phone on now.
Now normally if this were a HTC phone, I'd boot the phone to bootloader then recovery then restore my back up. But it's a Samsung. I know the volume down/home/power button trick but when I do that with my s3, the caution box pops up.. I hit volume up to by pass it then it just shows a big "downloading" sign that stays there forever. (I've literally left the phone sitting at the "downloading" sign for over an hour and nothing happened.)
So now I'm stuck. I no longer have a solution to get out of this situation. (I suppose this is a soft brick? )
Can anyone offer me any advice?
j0hnnyn said:
I did a lot of reading before I got into hacking my s3. I'm pretty new to the android development of Samsung phones, so the terms Odin and kexec are a little unfamiliar to me. I've owned and rooted and flashed 4 different HTC phones within the past 2 years successfully. But Samsung is a new ball game for me. And to my limited knowledge, I'm stuck and I'm hoping you guys can help me out.
Here's the process of what I did to my phone that got me to where I am.
1. I was able to root my phone and flash the custom recovery using using Adam outler's program successfully
2. I downloaded ez unlock boot loader from the play store and then successfully unlocked my boot loader
3. I tried to make a nandroid but I didn't know how to with the recovery I had. So I installed Rom manager and flashed cwm.
4. I downloaded the custom bean build 8 ROM, fully wiped, and attempted to flash the Rom with the Rom file sitting on the root of my phone's "sdcard"
- The zip seemed to flash correctly but then after I reboot from recovery, the screen would be sent back into recovery for some odd reason.
- I even tried to repeat the flashing process but it still resulted in sending me back to recovery after I hit reboot
5. So I restored my nandroid. Moved the Rom file to the root of extsdcard and then tried to flash it with cwm. It seemed to flash correctly once again but after I hit reboot, the phone shows the black splash screen with "Samsung galaxy s iii" in white letters then the phone shuts off. That's all that happens when I try to turn my phone on now.
Now normally if this were a HTC phone, I'd boot the phone to bootloader then recovery then restore my back up. But it's a Samsung. I know the volume down/home/power button trick but when I do that with my s3, the caution box pops up.. I hit volume up to by pass it then it just shows a big "downloading" sign that stays there forever. (I've literally left the phone sitting at the "downloading" sign for over an hour and nothing happened.)
So now I'm stuck. I no longer have a solution to get out of this situation. (I suppose this is a soft brick? )
Can anyone offer me any advice?
Click to expand...
Click to collapse
aye. go here and look for the return to stock section. remember to read it all before you start at least once.
http://forum.xda-developers.com/showthread.php?t=1762709
psycopanther said:
aye. go here and look for the return to stock section. remember to read it all before you start at least once.
http://forum.xda-developers.com/showthread.php?t=1762709
Click to expand...
Click to collapse
I'll try this when I get home. Do you know where it is I messed up while flashing the Rom? Did I use the wrong recovery?
Sent from my ADR6425LVW using xda premium
volume up/home/power button is recovery try that
and you used rom manger to flash rom?
j0hnnyn said:
I'll try this when I get home. Do you know where it is I messed up while flashing the Rom? Did I use the wrong recovery?
Sent from my ADR6425LVW using xda premium
Click to expand...
Click to collapse
Use EZ-Recovery to flash CWM 6.0.1.0 and just avoid rom manager next time. Does Beans still use kexec? Could be the issue since the cwm in rom manager doesn't support it.
PJnc284 said:
Use EZ-Recovery to flash CWM 6.0.1.0 and just avoid rom manager next time. Does Beans still use kexec? Could be the issue since the cwm in rom manager doesn't support it.
Click to expand...
Click to collapse
Yep, kexec rom (kernel) using a recovery that doesn't support it.
not sure if this can help but read this post I made, it may help:
http://forum.xda-developers.com/showthread.php?t=1842716
Make sure you have the right CWR version which is 6.0.1 or 6.0.2. Don't mess around with flashing things in rom manager.
To get to your recovery you need to use vol up+home+power.
The vol down puts the phone into Download/ODIN mode. It's like the bootloader/hboot screen of HTC phones.
I always super wipe)cache,data,dalvil,system) before any install, nandroid or fresh rom. And then install downloaded apps with tit backup.
To use Bean's nandroids after bootloader unlock, flash a fresh copy of bean first to install kexec, then flash your nandroid.
If I understand correctly, Bean's Custom Build 9 is out and no longer needs kexec. Therefore I can now use CWM 6.0.1.2 as I did earlier and I should have no problems now that kexec is no longer necessary. Can anyone confirm that?
j0hnnyn said:
If I understand correctly, Bean's Custom Build 9 is out and no longer needs kexec. Therefore I can now use CWM 6.0.1.2 as I did earlier and I should have no problems now that kexec is no longer necessary. Can anyone confirm that?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1768209]
From what I have read in his original post for his new build, it does require an unlock and is running a custom non-kexec kernel, so it I would draw the same conclusion that you are and it should in theory work with the 6.0.1.2 version of CWM.
j0hnnyn said:
If I understand correctly, Bean's Custom Build 9 is out and no longer needs kexec. Therefore I can now use CWM 6.0.1.2 as I did earlier and I should have no problems now that kexec is no longer necessary. Can anyone confirm that?
Click to expand...
Click to collapse
You should be able to use cwm6.0.1.2 to flash Imoseyons leankernel on any version of a custom touchwiz rom and enjoy no kexec
Im running beans 8 with imo's 2.2 kernel w/ no kexec...dont really like beans 9.
Long time lurker first time poster. I had a Nexus One two years ago so I was here very very often.. Since I got my Desire S a year ago, I haven't been able to flash a custom rom OR S-OFF.
Unlocked with HTCdev, rooted, HBOOT 2.00.0002 (downgrading hboot never worked either), S-ON
Last night I tried again to get onto ICS (official RUU doesn't install either). I installed 4EXT touch, flashed recovery, had my ROM (Fallout) on SD ready. Rebooted phone into new recovery to find that is was still the OLD revolutionary recovery and not 4EXT. This was 4am so I thought I'd try the usual wiping + rom flash. It went through normally and said completed although the progress bar only got about 1/3rd before jumping straight to finished. Rebooted.. stuck at white HTC logo screen.
My issues are that I cannot install HTC Sync phone drivers without phone powering up to be recognised by the PC, AND I cannot turn USB debugging on for obvious reasons
My phone is veryvery important and I'm now scared I won't be able to get it working again. Please help me.
TLDR; stuck on White HTC logo screen, no Android installed, cannot see how I can install one, help!
If anyone could shine some light on what I need to do next, I'd be very grateful.
Thanks in advance.. and afterwards
How did you flash the recovery? In fastboot? And did you flash the boot.img (also in fastboot) of the Rom you flashed?
You should definitely have read more before flashing anything...
teadrinker said:
How did you flash the recovery? In fastboot? And did you flash the boot.img (also in fastboot) of the Rom you flashed?
You should definitely have read more before flashing anything...
Click to expand...
Click to collapse
For the 4EXT recovery I 'flashed' it from inside the touch app thinking that was enough these days.. naively. Had just been fighting with GF at 4am and was fed up and about to go to bed and in Revolutionary recovery so I thought what the hay, I'll wipe etc in here and use this to try and flash the rom.
I did not flash the boot.img. I goofed. I understand that but now I'm just desperate for any route back to a functional device.
I never stopped installing ROMs and etc on my old Nexus One but that was a while ago and everything just seemed to work. Desire S is being a nightmare.
Decide what you want to do.
If you want to upgrade the phone to official ROM - relock your bootloader and run RUU.
If you want to use custom ROMs - flash the recovery from fastboot and don't forget to flash the kernel from fastboot too.
I won't get into any more details, searching for the right info with these pointers will get you whatever you might need.
Thank you, I'm all fixed. Simply found an old 2.3.5 ROM and flashed and booted fine. Reason I was so stuck was because I had formatted my PC since last installing phone drivers so I couldn't do much hurdur
First noted this is first time installing a custom rom. Long time lurker, first time problem!
HTC One S from Bell (Canada) Rooted/unlocked. CWM for Recovery.
Installed the from Zip in CWM. Cleared everything, went and flashed with fastboot for the boot. Everything looked good. Went back into CWM and cleared cache again.
Went to boot, hanging at htc screen but has the additional red text as well.
What did I miss ?
Thanks for any help or insight into this issue.
Is your phone s-off ... If not thm install 4ext recovery n flash the rom by enabling smart flash in 4ext recovery... Search for 4ext recovery n how to flash rom with s on ull b done
If I hve helped you press the thanks button ...
sent from HTC sensation
No idea what the above poster is on about but... My engrish isnt that good.
CWM is a crappy recovery for our phones. You should use TWRP instead.
But that doesnt seem to be the issue here. The issue you are describing is exactly what happens if boot.img isnt flashed through fastboot.
So, I suggest trying to flash it again through fastboot (fastboot flash boot boot.img).
If it still doesnt work after a couple of tries, change recovery to TWRP and start over from scratch (wipe everything, flash viper, flash boot.img).
Goatshocker said:
No idea what the above poster is on about but... My engrish isnt that good.
CWM is a crappy recovery for our phones. You should use TWRP instead.
But that doesnt seem to be the issue here. The issue you are describing is exactly what happens if boot.img isnt flashed through fastboot.
So, I suggest trying to flash it again through fastboot (fastboot flash boot boot.img).
If it still doesnt work after a couple of tries, change recovery to TWRP and start over from scratch (wipe everything, flash viper, flash boot.img).
Click to expand...
Click to collapse
Thanks so much, It worked. I was starting to stress out. Re-did the flash and BAM music happened. Just sitting at the HTC One screen now. I assume that takes a couple minutes.
Yeah. We dont have 4ext recovery yet for our phones. Only an old outdated version of clockwork, and of course a good updated version of TWRP. I havent used 4ext but have heard interesting things. I hear in the new year there will be some work on bringing it to HTC One S, although I dont know if it will have any features that arent already covered in TWRP.
AKToronto said:
Yeah. We dont have 4ext recovery yet for our phones. Only an old outdated version of clockwork, and of course a good updated version of TWRP. I havent used 4ext but have heard interesting things. I hear in the new year there will be some work on bringing it to HTC One S, although I dont know if it will have any features that arent already covered in TWRP.
Click to expand...
Click to collapse
Yeah im going to be switching over to TWRP. Sounds like its allot better to work with. I know with cwm you can't even mount usb storage, so you end up pushing files on using adb.
I was able to get my wife's phone unlocked over the weekend. I threw twrp 2.5.0.0 on there and tried to flash cleanrom. The phone was on the newest bootloader, so I tried flashing the boot.img in fastboot. It just stays on the boot screen forever. I found that there may be issues with newer twrp versions so I tried installing 3 different older version of twrp and all were unresponsive to touch. I could press power once and the twrp lock screen would come up, but that was it. I put 2.5.0.0 back on and it became usable again. Unfortunately I'm not S-Off yet because it says you have to be rooted and my plan was to put CleanRom on and then S-Off. I've verified the MD5 of the ROM zip on the phone. When I am going through the rom install though, and I go through all the options and it starts to install, it literally takes a tenth of a second and says successful. Then when I go to reboot to bootloader, it asks me if i'm sure since i don't have an OS installed. I figured that's just because I haven't flashed the boot img yet, but I am used to rom installs taking a couple seconds on my One XL. I've tried installing the boot.img with Hasoon's all-in-one and it says successful. I've tried installing the bulletproof kernel both via zip format and the boot img and still nothing boots up. What else can I try guys? The wife goes out of town tomorrow morning and needs a working phone. Thanks for your help.
edit: i found the log of the cleanrom install which appears to show the install failing.
utdps said:
I was able to get my wife's phone unlocked over the weekend. I threw twrp 2.5.0.0 on there and tried to flash cleanrom. The phone was on the newest bootloader, so I tried flashing the boot.img in fastboot. It just stays on the boot screen forever. I found that there may be issues with newer twrp versions so I tried installing 3 different older version of twrp and all were unresponsive to touch. I could press power once and the twrp lock screen would come up, but that was it. I put 2.5.0.0 back on and it became usable again. Unfortunately I'm not S-Off yet because it says you have to be rooted and my plan was to put CleanRom on and then S-Off. I've verified the MD5 of the ROM zip on the phone. When I am going through the rom install though, and I go through all the options and it starts to install, it literally takes a tenth of a second and says successful. Then when I go to reboot to bootloader, it asks me if i'm sure since i don't have an OS installed. I figured that's just because I haven't flashed the boot img yet, but I am used to rom installs taking a couple seconds on my One XL. I've tried installing the boot.img with Hasoon's all-in-one and it says successful. I've tried installing the bulletproof kernel both via zip format and the boot img and still nothing boots up. What else can I try guys? The wife goes out of town tomorrow morning and needs a working phone. Thanks for your help.
edit: i found the log of the cleanrom install which appears to show the install failing.
Click to expand...
Click to collapse
Did you flash boot boot.img?
Crypto66 said:
Did you flash boot boot.img?
Click to expand...
Click to collapse
I've narrowed down the issue to the install of CleanROM failing. This may be to twrp 2.5.0.0 but as I've said, earlier versions such as 2.3.3.0 aren't responding to touch for some reason. I don't think 2.5.0.0 is my problem though. I can see it if it didn't wipe properly, but the install is failing due to I/O errors.
But yes, I have tried flashing boot.img. twrp tells me I don't have an os when I try to reboot though, so that's the issue.
Try going to the advanced tab and fix permissions.
Sorry for slow responses, I've got to wait 5 minutes in between posts.
Crypto66 said:
Try going to the advanced tab and fix permissions.
Sorry for slow responses, I've got to wait 5 minutes in between posts.
Click to expand...
Click to collapse
Fix permissions won't work without a rom installed. It fails. And from what I understand anyways, fixing permissions is mostly for apps anyways.
Problem solved. Everyone make sure to use TWRP 2.3.3.1 and only that exact version. Older has touchscreen problems and newer has install issues. Man, this stuff can be frustrating at times.
That's not exactly true. Older versions work just fine, I'm using version 2.2 and it has never failed me.
Older versions aren't working for you because you have a newer touchscreen firmware, you would need to downgrade your touchscreen firmware in order to have touch response. For the same reason, you would not be able to run aosp roms until downgrading. Just thought I'd clear that up.
Sent from my One XL using XDA Premium
I unlocked and installed the CWM recovery. The ROM manager confirmed this was installed.
Following the guide at teamadroid.com for the twistedkat 4.4.2 ROM.
I flashed a new boot.img (from the twistedkat ROM).
Now I just see the "Only for internal use" red letters, and cannot invoke the CWM recovery for installing the ROM.
Any help would be appreciated on how to install the ROM or get back to stock.
EDIT: I progressed from this situation by re-flashing the CWM recovery, even though this emitted an error indicating that the file could not be validated or such. After this I can enter the CWM recovery.
Thanks!
qabi said:
I unlocked and installed the CWM recovery. The ROM manager confirmed this was installed.
Following the guide at teamadroid.com for the twistedkat 4.4.2 ROM.
I flashed a new boot.img (from the twistedkat ROM).
Now I just see the "Only for internal use" red letters, and cannot invoke the CWM recovery for installing the ROM.
Any help would be appreciated on how to install the ROM or get back to stock.
EDIT: I progressed from this situation by re-flashing the CWM recovery, even though this emitted an error indicating that the file could not be validated or such. After this I can enter the CWM recovery.
Thanks!
Click to expand...
Click to collapse
Do you have Ville (S4) or Ville C2 (S3) model?
If you have S4 ( I suppose due to te fact you installed TwistedKat) install this recovery --> http://goo.im/devs/philz_touch/CWM_Advanced_Edition/ville/philz_touch_6.19.3-ville.zip
The recovery provided by rom manager does NOT support Android 4.4.2 KItKat roms !!!
PLS check if you have S3 or S4
LS.xD said:
The recovery provided by rom manager does NOT support Android 4.4.2 KItKat roms !!!
Click to expand...
Click to collapse
Thanks for your suggestion.
Actually I don't know. I think only one HTC One S was ever in my market (Denmark).
In the meantime I succeeded installing the TwistedKat ROM and have it running now.
Does anybody know of a tutorial for resetting to stock ROM? (Just in case I want to revert).
-qabi
Unable to enter clockwork recovery?
I installed clockwork recovery and actually managed to install TwistedKat (what seems to be an old version).
But I am unable to enter the clockwork recovery in order to reflash to another ROM. Choosing RECOVERY from HBOOT just shows the warning screen and then halts the phone.
I have been reding through a ton of threads mentioning similar symptoms, but with no solution found.
Any help would really be appreciated!
qabi said:
I installed clockwork recovery and actually managed to install TwistedKat (what seems to be an old version).
But I am unable to enter the clockwork recovery in order to reflash to another ROM. Choosing RECOVERY from HBOOT just shows the warning screen and then halts the phone.
I have been reding through a ton of threads mentioning similar symptoms, but with no solution found.
Any help would really be appreciated!
Click to expand...
Click to collapse
I get this as well. Try it twice. For me the second time always boots up into CWM.
Can you tell me what you did to get rid of the red letters/HTC??? Did you flash boot.img again???
808phone said:
I get this as well. Try it twice. For me the second time always boots up into CWM.
Can you tell me what you did to get rid of the red letters/HTC??? Did you flash boot.img again???
Click to expand...
Click to collapse
Which recovery do you use? Are you S-OFF // SuperCID // HBOOT 2.15??
808phone said:
I get this as well. Try it twice. For me the second time always boots up into CWM.
Can you tell me what you did to get rid of the red letters/HTC??? Did you flash boot.img again???
Click to expand...
Click to collapse
The "red letters" have nothing to do with kernel. To get rid of them you must be S-Off and flash a moded hboot/firmware. There is one in the firmware thread that has the red warning removed.
@qabi: don't use CWM. Flash latest TWRP 2.7, you should be able to flash any ROM with it except the ones for 2.16 hboot
Sent from nowhere over the air...
Rapier said:
The "red letters" have nothing to do with kernel. To get rid of them you must be S-Off and flash a moded hboot/firmware. There is one in the firmware thread that has the red warning removed.
@qabi: don't use CWM. Flash latest TWRP 2.7, you should be able to flash any ROM with it except the ones for 2.16 hboot
Sent from nowhere over the air...
Click to expand...
Click to collapse
Rapier, can you explain this? A while back I loaded TWRP (S-ON) then loaded one of the CM series (either 11 or 10, can't remember). Then after I flashed boot.img, I was stuck in boot loop with HTC/red letters.
The reason I was asking what he did was I never did get to stop the boot loop myself. I paid to get it fixed, but I would like to know what I should have done to fix the boot loop after flashing the boot.img and having the problem. Seems like a lot of people get this so, so would be nice to know.
I was basically following everything listed on a web page and everything was working. Unlocked boot loader, SuperSU, TWRP etc... the last thing I did was flash the boot.img and then the problems occurred.
As far as the double try for CWM, I am S-OFF, 2.15 and I noticed it happens every now and then. I don't have this issue with TWRP at all.
It is hard to say why, apparently you did all right. What I can think off is a bad download or a bad flash or you could have used a wrong TWRP version. Also that ROM you have tried could have issues. It is very hard to know why without some logs that shows what went wrong
Sent from nowhere over the air...
LS.xD said:
If you have S4 ( I suppose due to te fact you installed TwistedKat) install this recovery -->
Click to expand...
Click to collapse
After much mucking about I flashed the "philz" recovery. That helped alot - I can now enter recovery every time. So apparently the original CWM recovery has problems on the HTC one S.
Thanks for your suggestions guys!
qabi said:
After much mucking about I flashed the "philz" recovery. That helped alot - I can now enter recovery every time. So apparently the original CWM recovery has problems on the HTC one S.
Thanks for your suggestions guys!
Click to expand...
Click to collapse
I think so. I am running the latest CWM and never had problems before this.