There were two main roms I wanted to try after I finally S-OFF'd my phone yesterday. Hatka Supreme 1.1.0 and Carbon. Neither of these worked and I'm glad that I backed up my S-OFF rooted stock rom. Hatka Supreme, the guy states its best to use Beast Mode kernal with the rom, which I flashed after I installed the room, and it just randomly reboots at the splash screen/a few seconds after getting into Android, so I restored my stock and everything worked fine. Next, I tried Carbon, and it just sat there at the carbon flash screen for like 20 minutes, so again, I had to restore to stock. Is there something I'm doing wrong? Is there a difference between Original Android Development and Android Development? Should I be looking at the original or what? I'm really lost, I'm going to try another rom, hopefully someone replies to this before it finishes downloading. Thanks for the help.
EDIT: I'd rather just sit and wait to see if someone replies before I waste time downloading another rom...any help would be appreciated.
rejectedjs said:
There were two main roms I wanted to try after I finally S-OFF'd my phone yesterday. Hatka Supreme 1.1.0 and Carbon. Neither of these worked and I'm glad that I backed up my S-OFF rooted stock rom. Hatka Supreme, the guy states its best to use Beast Mode kernal with the rom, which I flashed after I installed the room, and it just randomly reboots at the splash screen/a few seconds after getting into Android, so I restored my stock and everything worked fine. Next, I tried Carbon, and it just sat there at the carbon flash screen for like 20 minutes, so again, I had to restore to stock. Is there something I'm doing wrong? Is there a difference between Original Android Development and Android Development? Should I be looking at the original or what? I'm really lost, I'm going to try another rom, hopefully someone replies to this before it finishes downloading. Thanks for the help.
EDIT: I'd rather just sit and wait to see if someone replies before I waste time downloading another rom...any help would be appreciated.
Click to expand...
Click to collapse
Did you do a full wipe? System, factory reset, dalvik?
Tapatalked from my HTC DNA - Carbon
pio_masaki said:
Did you do a full wipe? System, factory reset, dalvik?
Tapatalked from my HTC DNA - Carbon
Click to expand...
Click to collapse
It's probably your recoverys fault. On my last DNA I had nothing but failures. Once it took at least 30 times to get a Rom installed. Never solved the issue on that phone. I just soffed my new DNA yesterday, installed the newest cwm touch and flashed 4 different roms with no problem. Try re-flashing cwm touch.
pio_masaki said:
Did you do a full wipe? System, factory reset, dalvik?
Tapatalked from my HTC DNA - Carbon
Click to expand...
Click to collapse
Yes, still the same thing, I'm not saying I didn't do that the first time though, that's like the basics of installing a rom.
str8upx said:
It's probably your recoverys fault. On my last DNA I had nothing but failures. Once it took at least 30 times to get a Rom installed. Never solved the issue on that phone. I just soffed my new DNA yesterday, installed the newest cwm touch and flashed 4 different roms with no problem. Try re-flashing cwm touch.
Click to expand...
Click to collapse
Do you think its TWRP's fault? After I found out there was no way to mount USB storage in TWRP I wanted to switch to CWM, but sadly I don't know how.
rejectedjs said:
Yes, still the same thing, I'm not saying I didn't do that the first time though, that's like the basics of installing a rom.
Do you think its TWRP's fault? After I found out there was no way to mount USB storage in TWRP I wanted to switch to CWM, but sadly I don't know how.
Click to expand...
Click to collapse
You could use the goomanager from the play store or use fastbook flash recovery cwm.img
Edit: for the touch version of cwm fastboot is required.
str8upx said:
You could use the goomanager from the play store or use fastbook flash recovery cwm.img
Edit: for the touch version of cwm fastboot is required.
Click to expand...
Click to collapse
I would rather use goomanager, because it seems easier, but the only thing it seems to be able to download is the twrp image. How would I set it to cwm?
I have canvas 2 running on suvi6 Jupiter rom i have some prob with this when i reboot some icon on home screen will disappear, i found that those apps which r installed on ext sd card its icon will disappear from home screen, but apps working in apps list, only icon from home screen disappeared.
Other problem is that while incoming a call i cannot see full picture of caller becoz half screen is black and half picture can be seen.
Please help me
Sent from my Micromax A110 using xda app-developers app
rejectedjs said:
I would rather use goomanager, because it seems easier, but the only thing it seems to be able to download is the twrp image. How would I set it to cwm?
Click to expand...
Click to collapse
Sorry I was mistaken, goomanager installs twrp not cwm.
Fastboot is easy to use, I'm at work so I can't to a step by step til I get home later. You should be able figure it out but if not I will help when I get home.
str8upx said:
Sorry I was mistaken, goomanager installs twrp not cwm.
Fastboot is easy to use, I'm at work so I can't to a step by step til I get home later. You should be able figure it out but if not I will help when I get home.
Click to expand...
Click to collapse
I don't know if you knew this already but I s-offed using moonshine, is that a problem? I installed cwm and tried installing hatka again and it did the same thing, restart like every three seconds into android. I don't know what to do anymore.
kundan.lohar said:
I have canvas 2 running on suvi6 Jupiter rom i have some prob with this when i reboot some icon on home screen will disappear, i found that those apps which r installed on ext sd card its icon will disappear from home screen, but apps working in apps list, only icon from home screen disappeared.
Other problem is that while incoming a call i cannot see full picture of caller becoz half screen is black and half picture can be seen.
Please help me
Sent from my Micromax A110 using xda app-developers app
Click to expand...
Click to collapse
Pretty sure you're in the wrong forum.
From my S-Off BadSeed DNA
rejectedjs said:
There were two main roms I wanted to try after I finally S-OFF'd my phone yesterday. Hatka Supreme 1.1.0 and Carbon. Neither of these worked and I'm glad that I backed up my S-OFF rooted stock rom. Hatka Supreme, the guy states its best to use Beast Mode kernal with the rom, which I flashed after I installed the room, and it just randomly reboots at the splash screen/a few seconds after getting into Android, so I restored my stock and everything worked fine. Next, I tried Carbon, and it just sat there at the carbon flash screen for like 20 minutes, so again, I had to restore to stock. Is there something I'm doing wrong? Is there a difference between Original Android Development and Android Development? Should I be looking at the original or what? I'm really lost, I'm going to try another rom, hopefully someone replies to this before it finishes downloading. Thanks for the help.
EDIT: I'd rather just sit and wait to see if someone replies before I waste time downloading another rom...any help would be appreciated.
Click to expand...
Click to collapse
I'm no expert, but when u flashed hatka, did u reboot into the system before flashing beast mode kernel? Flashing a kernel in the same recovery session is a no no. Also, beast mode is not compatible with carbon, fyi.
Sent from my HTC6435LVW using Tapatalk 4 Beta
kelvinnotcalvin said:
I'm no expert, but when u flashed hatka, did u reboot into the system before flashing beast mode kernel? Flashing a kernel in the same recovery session is a no no. Also, beast mode is not compatible with carbon, fyi.
Sent from my HTC6435LVW using Tapatalk 4 Beta
Click to expand...
Click to collapse
I did that the first time, and thats when I started experiencing it, so I figured that was the problem. So I restored to stock, and then just tried flashing the rom and booting, still same thing, rebooting every 5 seconds. Sometimes I'm able to get into settings, scroll up and down a few times, and then it reboots.
EDIT: If I remember correctly, I didn't even flash beast mode kernel after I flashed carbon.
rejectedjs said:
EDIT: If I remember correctly, I didn't even flash beast mode kernel after I flashed carbon.
Click to expand...
Click to collapse
If you had you never would have seen the carbon boot animation I don't think, just a white scrambled screen.
Tapatalked from my HTC DNA - Carbon
pio_masaki said:
If you had you never would have seen the carbon boot animation I don't think, just a white scrambled screen.
Tapatalked from my HTC DNA - Carbon
Click to expand...
Click to collapse
What exactly is the problem I'm experiencing here? x.x Of all roms I REALLY wanted to try Hatka, why me...
rejectedjs said:
What exactly is the problem I'm experiencing here? x.x Of all roms I REALLY wanted to try Hatka, why me...
Click to expand...
Click to collapse
I've had the same sort of thing happen to me when we first started working with CM. I had to lock up and run the RUU then unlock again, started flashing normally again after that.
Tapatalked from my HTC DNA - Carbon
pio_masaki said:
I've had the same sort of thing happen to me when we first started working with CM. I had to lock up and run the RUU then unlock again, started flashing normally again after that.
Tapatalked from my HTC DNA - Carbon
Click to expand...
Click to collapse
You mean you want me to go back to pure stock and soff all over again?
rejectedjs said:
You mean you want me to go back to pure stock and soff all over again?
Click to expand...
Click to collapse
I don't want you to do anything, in was just saying what I did to correct it when it happened to me.
And no, I didn't day s-on, I said relocked, the RUU won't run on an unlocked device. Locked and son are different.
Tapatalked from my HTC DNA - Carbon
pio_masaki said:
I don't want you to do anything, in was just saying what I did to correct it when it happened to me.
And no, I didn't day s-on, I said relocked, the RUU won't run on an unlocked device. Locked and son are different.
Tapatalked from my HTC DNA - Carbon
Click to expand...
Click to collapse
I've never had so many problems just trying to flash a Rom before, this is crazy...I'm seriously at a loss about what to do other than stay on rooted stock
bump?..I really want some help..
Did you figure it out? I'd do what pio said. He's kind of amazing. He's a very smart man who most likely knows what he's doing
Sent from my HTC6435LVW using xda app-developers app
Related
it wont load past the HTC screen..
flashed WARM-3.5-evo3d-unofficial-r100.zip
from sdcard.
had down a factory wipe initially.. tried clearing dalvik cache again but still cannot get past htc screen. ugh
correction i flashed to r119.zip
Did you wipe system as well? How long are you giving it at the HTC Splash screen before you decide it's frozen? I haven't been keeping up to date with the Warm train lately, so I'm not sure if there have been any issues with the builds. I know back in the day, sometimes the build bot that myn used would bork a build from time to time and it wouldn't flash. Have you tried flashing any other builds, or just r119?
yes i did a complete wipe initially.. flashed.. got stuck at screen.. i left it there for 2-3 mins with no response.. just hovering at the HTC screen. I have not tried flashing any other roms as I wasnt sure what if any adverse affect this may have on the current problem
tre976 said:
yes i did a complete wipe initially.. flashed.. got stuck at screen.. i left it there for 2-3 mins with no response.. just hovering at the HTC screen. I have not tried flashing any other roms as I wasnt sure what if any adverse affect this may have on the current problem
Click to expand...
Click to collapse
Before you go any further in trying to figure it out, I would let it sit at the HTC screen a bit longer than a couple minutes. I've had it hang there for 5 or 6 minutes on certain sense roms that I flash, especially on the first boot. Give it a solid 7 minutes or so, and if it's still hanging there..then yea it's stuck. After that, I would simply try flashing something else and see if it works. Perhaps you got a bad download as well, maybe try re downloading it.
suggestions on how to move rom to sdcard if phone isnt booting hence PC isnt seeing the drive?
is it possible to go back to stock rom if this doesnt work?
tre976 said:
suggestions on how to move rom to sdcard if phone isnt booting hence PC isnt seeing the drive?
is it possible to go back to stock rom if this doesnt work?
Click to expand...
Click to collapse
Transfer it to the SD card from recovery. I'm not sure what recovery you're on, but every recovery has the feature to mount the sd card from within recovery. It's like USB MS Toggle or something to that nature. In TWRP 2, I think it's under the 'mount' tab.
Did you just try turning it on again yet, and seeing if it will eventually get past the HTC Screen? Again, it could take a bit more than 2 or 3 minutes on the first boot.
EDIT: And yea, you should be able to get back to a stock ROM no problem, or at least get back to a functioning phone, lol. Did you make a nandroid of your stock setup right after you rooted, before you tried flashing warm?
no i didnt make a nandroid backup sadly. im letting it sit for 10 mins before i give up on tyhis version
I don't think that ROM will boot as I'm pretty sure it has no boot image in it. Joelz was doing some stuff on the later builds and removed the bootimage.
Go into the thread and look for Vin's post. He is on the front page or on post 2. He has been the one updating the ROM for Joelz. the last version I knew of was around 01/12 or so?
tre976 said:
no i didnt make a nandroid backup sadly. im letting it sit for 10 mins before i give up on tyhis version
Click to expand...
Click to collapse
Again, you said you're hboot 1.4, right? So you S-offed with revolutionary? Cuz if you're 1.5, then we're missing an important step....
Sent from my PG86100 using Tapatalk
Never mind, 01/27/12 was his last update.
Here ya go, flash this one.
http://forum.xda-developers.com/showpost.php?p=21019364&postcount=279
KB112 said:
I don't think that ROM will boot as I'm pretty sure it has no boot image in it. Joelz was doing some stuff on the later builds and removed the bootimage.
Go into the thread and look for Vin's post. He is on the front page or on post 2. He has been the one updating the ROM for Joelz. the last version I knew of was around 01/12 or so?
Click to expand...
Click to collapse
LOL, that would certainly explain his problems. As I said, I haven't been keeping up to date with the warm team
Sent from my PG86100 using Tapatalk
Yeah, I read his post too fast. I didn't realize he was flashing Sense 3.5 version. Vins version is really nice and clean, he's done an excellent job helping JoelZ and keeping the ROM alive.
k2buckley said:
Again, you said you're hboot 1.4, right? So you S-offed with revolutionary? Cuz if you're 1.5, then we're missing an important step....
Sent from my PG86100 using Tapatalk
Click to expand...
Click to collapse
no it was 1.4 from revolutinary.io.. it has the nandroid option i missed that step in the instructions before flashing. Thanks i'll try the link above
k2buckley said:
Transfer it to the SD card from recovery. I'm not sure what recovery you're on, but every recovery has the feature to mount the sd card from within recovery. It's like USB MS Toggle or something to that nature. In TWRP 2, I think it's under the 'mount' tab.
Did you just try turning it on again yet, and seeing if it will eventually get past the HTC Screen? Again, it could take a bit more than 2 or 3 minutes on the first boot.
EDIT: And yea, you should be able to get back to a stock ROM no problem, or at least get back to a functioning phone, lol. Did you make a nandroid of your stock setup right after you rooted, before you tried flashing warm?
Click to expand...
Click to collapse
gives me a Mount system or mount /data..
oh i see it i mounted sdcard.. oddly windows doesnt see the card tho as a drive still
tre976 said:
gives me a Mount system or mount /data..
oh i see it i mounted sdcard.. oddly windows doesnt see the card tho as a drive still
Click to expand...
Click to collapse
What recovery are you using?
It should be Toggle USB or something like that
i used my wifes phone sdcard to bypass the problem. that flash got me to a loading phone boot now. thanks! but i'm apparently not connecting to sprint. lol. go figure..
fwiw im using twrp 1.0.3
Ok, now you may have to call them ask to have your data reset. There is a specific thing to ask for. It's in the threads on how to root the Evo 3D.
My SGS2 has been running AOKP for a few months now, all of a sudden today the phone keeps rebooting itself every few minutes. I have tried wiping cache, full wipe etc.... I tried installing a different kernel and also a different rom, now it's on ShoStock, but it continues to loop. Also I have flashed the newest version of CWM but everytime I reboot the phone it reverts back to the old version. Any ideas help?
Still Mostly Harmless said:
My SGS2 has been running AOKP for a few months now, all of a sudden today the phone keeps rebooting itself every few minutes. I have tried wiping cache, full wipe etc.... I tried installing a different kernel and also a different rom, now it's on ShoStock, but it continues to loop. Also I have flashed the newest version of CWM but everytime I reboot the phone it reverts back to the old version. Any ideas help?
Click to expand...
Click to collapse
How do you flash CWM?
I got no clue on the issue at hand other than to go back to stock and see if it persists, if it does its hardware.
Is your name a throwback to the movies/books or something else? In hoping something else...
Good luck bro!
Clay
Team Pirate
Sent from my PINK GS2 using xda app
Thanks guys, another issue I noticed is that the power button was acting really strangely. When you pressed it it wouldnt turn off the phone it would just bring up the restart menu or it wouldn't register at all, so I thought I had a hardware issue. Any finally I ran this kernel cleaner:
http://forum.xda-developers.com/showthread.php?t=1363738
did a full wipe etc...installed rom and then kernel and that has seem to do the trick. Going to hope that it continues to work and I don't have to go out and buy a new phone!
Looks like I have some donating to do.
Don't use ROM manager to flash cwm. As that is what it sounds like u did when u said u "flashed" cwm. Our kernels have recovery built in.
Sent from my SGH-I777 using Tapatalk 2
Phalanx7621 said:
Don't use ROM manager to flash cwm. As that is what it sounds like u did when u said u "flashed" cwm. Our kernels have recovery built in.
Sent from my SGH-I777 using Tapatalk 2
Click to expand...
Click to collapse
Thats what I was thinking :highfive:
I download the latest CWM (6.0.1.0), put the zip on my SD then boot into recovery and installed it as a zip, is that incorrect?
Still Mostly Harmless said:
I download the latest CWM (6.0.1.0), put the zip on my SD then boot into recovery and installed it as a zip, is that incorrect?
Click to expand...
Click to collapse
Yeah, that's probably incorrect.
For our phones, CWM is included in all custom kernels and isn't separate from the kernel at all. The only way to update CWM is to flash an updated custom kernel, like if Siyah or NEAK were to update for instance.
Don't bother trying to update CWM all the time, there's honestly little to no benefit from even trying and you'll likely end up with problems instead like you did this time. The version of CWM included with the custom kernels available is more than sufficient, just stick with those instead of trying to update it separately.
So I thought I fixed it but at last I haven't. After running the kernel cleaner, installing different roms/kernels the phone still boots for no reason after a while, not as often but at least 2-5 times a day. I am have no idea what's going on.
Still Mostly Harmless said:
So I thought I fixed it but at last I haven't. After running the kernel cleaner, installing different roms/kernels the phone still boots for no reason after a while, not as often but at least 2-5 times a day. I am have no idea what's going on.
Click to expand...
Click to collapse
You tried going to stock and seeing if the problem persists? For my brother it was an app so keep that in mind as well
clay101eve said:
Is your name a throwback to the movies/books or something else? In hoping something else...
Good luck bro!
Clay
Team Pirate
Sent from my PINK GS2 using xda app
Click to expand...
Click to collapse
still awaiting an answer!
Have you noticed if the phone is getting really hot around the time it's rebooting?
Clay
Team Pirate
Sent from my PINK SGH-I777
clay101eve said:
still awaiting an answer!
Have you noticed if the phone is getting really hot around the time it's rebooting?
Clay
Team Pirate
Sent from my PINK SGH-I777
Click to expand...
Click to collapse
Yes it is definitely from my favorite series of books. This is one of the only forums I visit that I couldn't get just Mostly Harmless.
Doesn't really get hot, but after a while the power button stops responding and only time fixes this or a fresh install of a kernel. I formatted my SD card and the internal memory (without grabbing my pictures ) and any app I install is new from the market.
I was rooted on MeanROM, and from TWRP I cleared the cache and delvic cache and did a factory wipe, then tried to install the cm10 nightly build, but it said failed, so I cleared and wiped again and tried installing the FreshEVO ROM that I had on it before the MeanROM, it never finished installing, just froze after a while. then TWRP restarted then went into the white HTC "quietly brilliant" screen with the red disclaimer and stuck there. When i hold the power down, it just reboots back to this screen. I cant get it into recovery or bootloader or anywhere but this. My computer isn't recognizing the phone, I tried to adb to it from cmd but its not showing up. I don't think i had the latest hboot or whatever on it, it's been probably two months since i first rooted it. any help would be great, please and thank you. I'm heading to work but i'll check this on my breaks and answer any questions i can about what ive done. I was about to trade the phone for an s3 this saturday, but im sure he wont want it like this! THANK YOU.
I'm just gonna say this and don't take it offensively... That is the risk you took rooting your phone.. if you can get into bootloader, try loading a current ruu on there and see If that works.
Sent from my EVO using Tapatalk 2
thlinx said:
I'm just gonna say this and don't take it offensively... That is the risk you took rooting your phone.. if you can get into bootloader, try loading a current ruu on there and see If that works.
Sent from my EVO using Tapatalk 2
Click to expand...
Click to collapse
No offense taken, I understood the risks, and I accept the consequences, which is why I'm fairly calm and not freaking out. I'm going to read more into RUU's on my break, as I'm not completely sure how to do that. Does the computer have to recognize my device for that? I would think so. Is there a trick to getting from this white HTC screen back to TWRP other than trying to reboot or pwr+vol down? Everything just keeps going back here. It wont even turn off without the battery draining.. I'll keep reading on my break, any other helpful comments are definitely welcome. Thanks.
Hold down the power button for 10 seconds and the lights on the capacitive buttons will blink. As soon as the screen goes black wait about half a second then hold volume down and power to get into bootloader then go into recovery.
Hope that helps you. That's how I've always gotten back into recovery when I have a bad flash.
Sent from my EVO using xda premium
BrianBaker said:
Hold down the power button for 10 seconds and the lights on the capacitive buttons will blink. As soon as the screen goes black wait about half a second then hold volume down and power to get into bootloader then go into recovery.
Click to expand...
Click to collapse
This is correct and works. Couldn't boot after trying to install Chainfie 3D drivers but got to recovery this way.
Sent from my EVO 4g LTE on my 3g network.
Happened to me. You have to flash the boot image for cm10 if I recall correctly.
Sent from my EVO
themorningsleeve said:
I was rooted on MeanROM, and from TWRP I cleared the cache and delvic cache and did a factory wipe, then tried to install the cm10 nightly build, but it said failed, so I cleared and wiped again and tried installing the FreshEVO ROM that I had on it before the MeanROM, it never finished installing, just froze after a while. then TWRP restarted then went into the white HTC "quietly brilliant" screen with the red disclaimer and stuck there. When i hold the power down, it just reboots back to this screen. I cant get it into recovery or bootloader or anywhere but this. My computer isn't recognizing the phone, I tried to adb to it from cmd but its not showing up. I don't think i had the latest hboot or whatever on it, it's been probably two months since i first rooted it. any help would be great, please and thank you. I'm heading to work but i'll check this on my breaks and answer any questions i can about what ive done. I was about to trade the phone for an s3 this saturday, but im sure he wont want it like this! THANK YOU.
Click to expand...
Click to collapse
did you ever get this going? Sounds like from what i was seeing you got into your BL finally. I would try reinstalling TWRP like the second part of the OP http://forum.xda-developers.com/showthread.php?t=1794867 and then select reboot to recovery from the bootloader ot the button method. If you get back into twrp restore the last working rom setup you had which sounds like meanrom. If it works come back and let us know.
motcher41 said:
did you ever get this going? Sounds like from what i was seeing you got into your BL finally. I would try reinstalling TWRP like the second part of the OP http://forum.xda-developers.com/showthread.php?t=1794867 and then select reboot to recovery from the bootloader ot the button method. If you get back into twrp restore the last working rom setup you had which sounds like meanrom. If it works come back and let us know.
Click to expand...
Click to collapse
Hey guys, on my lunch break, i got it working! I couldn't get it to go into recovery last night for the life of me, but i tried this morning on my way to work and it worked just fine like it should. For some reason none of my roms would install though other than the jewel stock of the latest update with root that i had on here. It worked and I'm good to go. Thanks for the help though! Anyone know why the roms that i installed before are falling Everette i try to install them now? I always wipe and restore first..
themorningsleeve said:
Hey guys, on my lunch break, i got it working! I couldn't get it to go into recovery last night for the life of me, but i tried this morning on my way to work and it worked just fine like it should. For some reason none of my roms would install though other than the jewel stock of the latest update with root that i had on here. It worked and I'm good to go. Thanks for the help though! Anyone know why the roms that i installed before are falling Everette i try to install them now? I always wipe and restore first..
Click to expand...
Click to collapse
I'm willing to bet that you are not S-OFF, and on Hboot 1.15 or higher, and that was the issue when you tried to install CM10. Make sure you read the instructions for flashing CM10, because you have to do something special to flash a kernel when you are S-ON. Now, as far as the old roms not being able to flash, it may be that they were based on the original 1.13 software version with the 1.13 kernel, and it won't let you flash over your current kernel because the version is older. Essentially, if you are S-ON, you can't flash a kernel unless it matches or is a newer version than the one you have. Of course, you can follow one of the many guides on how to flash boot (kernel) with S-ON to get around this.
timtlm said:
I'm willing to bet that you are not S-OFF, and on Hboot 1.15 or higher, and that was the issue when you tried to install CM10. Make sure you read the instructions for flashing CM10, because you have to do something special to flash a kernel when you are S-ON. Now, as far as the old roms not being able to flash, it may be that they were based on the original 1.13 software version with the 1.13 kernel, and it won't let you flash over your current kernel because the version is older. Essentially, if you are S-ON, you can't flash a kernel unless it matches or is a newer version than the one you have. Of course, you can follow one of the many guides on how to flash boot (kernel) with S-ON to get around this.
Click to expand...
Click to collapse
Wow yes this all made perfect sense! I didn't think about my old roms not being compatible, and i also didn't realize i needed s-off for cm10. I have a bad habit of thinking i can just throw a zip on my card and flash it and it will magically work perfectly lol.. This kind of thinking is what gets me into trouble! Where can i read about turning s-off for installing cm10? Are there links on the download page?
themorningsleeve said:
Wow yes this all made perfect sense! I didn't think about my old roms not being compatible, and i also didn't realize i needed s-off for cm10. I have a bad habit of thinking i can just throw a zip on my card and flash it and it will magically work perfectly lol.. This kind of thinking is what gets me into trouble! Where can i read about turning s-off for installing cm10? Are there links on the download page?
Click to expand...
Click to collapse
S-OFF info is here, but because you are having this issue, you probably have HBoot 1.15 or higher, which means you can't achieve S-OFF until a new exploit is found.
http://forum.xda-developers.com/showthread.php?t=1737123
There are methods for flashing kernels here with S-ON here:
http://forum.xda-developers.com/showthread.php?t=1794867
Also, there's the newer twrp dumlock method if you install the latest version ot TWRP (2.2.1). http://teamw.in/project/htcdumlock
timtlm said:
S-OFF info is here, but because you are having this issue, you probably have HBoot 1.15 or higher, which means you can't achieve S-OFF until a new exploit is found.
http://forum.xda-developers.com/showthread.php?t=1737123
There are methods for flashing kernels here with S-ON here:
http://forum.xda-developers.com/showthread.php?t=1794867
Also, there's the newer twrp dumlock method if you install the latest version ot TWRP (2.2.1). http://teamw.in/project/htcdumlock
Click to expand...
Click to collapse
Ok thanks. My main goal is to not screw this phone up before Saturday when i trade it for an S3 so i may not bother, but i will definitely give it a look!
themorningsleeve said:
Wow yes this all made perfect sense! I didn't think about my old roms not being compatible, and i also didn't realize i needed s-off for cm10. I have a bad habit of thinking i can just throw a zip on my card and flash it and it will magically work perfectly lol.. This kind of thinking is what gets me into trouble! Where can i read about turning s-off for installing cm10? Are there links on the download page?
Click to expand...
Click to collapse
You dont have to have s-off though like he said for cm-10 you just need an extra step or two. I dont blame you for trading it in I did the same. Except I am going back to the Gnex.
motcher41 said:
You dont have to have s-off though like he said for cm-10 you just need an extra step or two. I dont blame you for trading it in I did the same. Except I am going back to the Gnex.
Click to expand...
Click to collapse
I had the gnex before this, why did you go back to that out of the other 2?
themorningsleeve said:
I had the gnex before this, why did you go back to that out of the other 2?
Click to expand...
Click to collapse
Well I'm going back cuz of the non htc clustscrew and the openess of the platform. No bs no s on or s off dev unlocks etc...its how a phone should be. Better camera functionality and I know the sammy platform. Imho it may be older but its a far superior device. Could afford any device out there and to me its hands down gnex
Sent from my SPH-M900 using Tapatalk 2
motcher41 said:
Well I'm going back cuz of the non htc clustscrew and the openess of the platform. No bs no s on or s off dev unlocks etc...its how a phone should be. Better camera functionality and I know the sammy platform. Imho it may be older but its a far superior device. Could afford any device out there and to me its hands down gnex
Sent from my SPH-M900 using Tapatalk 2
Click to expand...
Click to collapse
right on. I did enjoy that phone. I LOVE the camera on my EVO LTE though, that's the one thing ill miss about this one. I did just find out that the ass that was supposed to trade me on saturday already traded someone, so i'm stuck with the LTE for a while now, so i might venture into putting cm10 on it, but then again i might wait til a more stable version hits, just depends on how long that may take..
themorningsleeve said:
right on. I did enjoy that phone. I LOVE the camera on my EVO LTE though, that's the one thing ill miss about this one. I did just find out that the ass that was supposed to trade me on saturday already traded someone, so i'm stuck with the LTE for a while now, so i might venture into putting cm10 on it, but then again i might wait til a more stable version hits, just depends on how long that may take..
Click to expand...
Click to collapse
Ruu it back to stock locked and ebay it. Should get enough for nib sealed gnex. I found one for 319.00. Saw a couple s3 on swappa for about 430-440 nib sealed. Saw a bad esn one going for 290ish so yours should be 350ish or more
Sent from my SPH-M900 using Tapatalk 2
CM10 should be going completely open source with the camera very soon. Expect good things.
To the people complaining about HTC and leaving/trading for new phones.... cya.
That isnt helpful here... we dont need an announcement. Just go please.
Rxpert said:
CM10 should be going completely open source with the camera very soon. Expect good things.
To the people complaining about HTC and leaving/trading for new phones.... cya.
That isnt helpful here... we dont need an announcement. Just go please.
Click to expand...
Click to collapse
Me and the op are having a good clean conversation in his thread so.... cya
Sent from my SPH-M900 using Tapatalk 2
motcher41 said:
Me and the op are having a good clean conversation in his thread so.... cya
Sent from my SPH-M900 using Tapatalk 2
Click to expand...
Click to collapse
Take your private conversation to PM?
Hi guys, new poster, but I'm seriously stuck. I obviously have the HTC Evo 4G LTE, and I have root and unlocked bootloader with HBOOT 1.19 and S-ON. I have tried so many times to install CM10 (the Codefirex nightlies) with TWRP install, but I simply can't. I have tried copying the ROM to the root system folder (along with Gapps) and tried directly flashing the boot.img to the phone with Fastboot. I'm out of ideas and need help. Thanks!
Are u getting an OK in cmd window after a fast boot flash?
Sent from a lens flare powered EVO LTE
epic4gt said:
Are u getting an OK in cmd window after a fast boot flash?
Sent from a lens flare powered EVO LTE
Click to expand...
Click to collapse
I'm sorry, I really don't get what you mean.
Try jellybomb, it has the kernel installer, or go back to a sense Rom and use dumlock. Make a backup in recovery and go to advanced/dumlock and install. Boot back to sense and open dumlock, let it make a backup and execute. When you reboot it will go straight to recovery and from there go back to dumlock and restore boot. Now you can flash a Rom normally
om4 said:
Try jellybomb, it has the kernel installer, or go back to a sense Rom and use dumlock. Make a backup in recovery and go to advanced/dumlock and install. Boot back to sense and open dumlock, let it make a backup and execute. When you reboot it will go straight to recovery and from there go back to dumlock and restore boot. Now you can flash a Rom normally
Click to expand...
Click to collapse
THANK YOU! It worked!
Okay, never mind. It "installed", but after letting it go overnight, the blue screen with the words CyanogenMod and the blue circle spinning around them is still present. This has happened before, and I'm so confused. It's been 6 hours...
ajq2014 said:
Okay, never mind. It "installed", but after letting it go overnight, the blue screen with the words CyanogenMod and the blue circle spinning around them is still present. This has happened before, and I'm so confused. It's been 6 hours...
Click to expand...
Click to collapse
Experiencing the same phenomena with the spinning blue CyanogenMod circle after boot. Have copied CM10 zip (stable, not nightly - yet) and GAPP onto sdcard. Rooted, and S-Off completed on HBoot 1.19, 2.13.651.1 RUU. Will follow this thread for guidance! I guess I am a noob here, but should have graduated beyond that, getting S-Off and root complete. Oh well!
ajq2014 said:
Okay, never mind. It "installed", but after letting it go overnight, the blue screen with the words CyanogenMod and the blue circle spinning around them is still present. This has happened before, and I'm so confused. It's been 6 hours...
Click to expand...
Click to collapse
This may be a dumb question but did you wipe the dalvik and cache and system before installing?
om4 said:
This may be a dumb question but did you wipe the dalvik and cache and system before installing?
Click to expand...
Click to collapse
Yeah... I have half a mind to give up. I've been to so many forums.... That's why I posted here.
Deleted. Question was already answered.
Shahal said:
There's really no reason to not be s-off. It makes installing non sense ROMs infinitely easier. Just use the dirtyracun s-off method and then flash cm10 again. If for whatever reason you just don't want to be s-off you can flash the boot.img in fastboot and it ought to boot up.
Sent from my rooted LTEVO running CM10.
Click to expand...
Click to collapse
Another noob question, but what does S do exactly? And how do I flash the ROM / boot.img file?
Without getting too technical about it, being s-off means your device is fully unlocked rather than being half unlocked only using htcdev's unlock method. There's a much more in depth description in the FAQ among many other questions you probably have.
Sent from my rooted LTEVO running CM10.
Read don't panic in q&a
I have just recently received my replacement evo after smashing my old one. The phone was already fully upgraded to the latest JB software and hboot 2.09. The first thing i did was S-OFF using the DirtyRacun method all went well except for a few user errors but eventually achieved S-OFF. After that was done i installed TWRP recovery v2.3.3.0. After flashing Viper Rom my phone had random reboots spanning from minutes apart to a few hours apart. I redownloaded the same rom wiped everything again and the problem stayed consistent. so i decided to switch roms and tried PACman aokp rom and the same problem exist there also. is this a hardware issue or a result of an error during S-OFF? i have a couple logs from the app "Bootlog Uptime" if that may be of any assistance.
S-OFF using DirtyRacun
HBoot 2.09
TWRP v2.3.3.0
Roms Tried: Viper Rom and PACman aokp
Stock kernels
logs attached.
Try the latest TWRP?
... Sent from my 'Oops! Should've bought the S3!' via XDA-Developers App.
Delakit said:
Try the latest TWRP?
... Sent from my 'Oops! Should've bought the S3!' via XDA-Developers App.
Click to expand...
Click to collapse
I've heard nothing but bad things about the latest TWRP such as the touch screen not working so i decided it would be best to just stay away from it.
kcdre said:
I've heard nothing but bad things about the latest TWRP such as the touch screen not working so i decided it would be best to just stay away from it.
Click to expand...
Click to collapse
Try twrp 2.4.1.0 all my firmware including the touch panel drivers and have zero issues
Sent from my PoS MoPho
bigdaddy619 said:
Try twrp 2.4.1.0 all my firmware including the touch panel drivers and have zero issues
Sent from my PoS MoPho
Click to expand...
Click to collapse
I guess i could try updating the recovery and flashing again but ive never had this problem previously with 2.3.3.0. I just want to be sure its not hardware related before the return window closses for me to return this device for a new one.
I updated my recovery to the latest version and did a fresh install of viper rom and just had another random reboot. starting to think the problem is hardware related. ill have a log attached and hopefully someone will have a little insight on what's going on.
kcdre said:
I updated my recovery to the latest version and did a fresh install of viper rom and just had another random reboot. starting to think the problem is hardware related. ill have a log attached and hopefully someone will have a little insight on what's going on.
Click to expand...
Click to collapse
Post the log in the Viper thread, unless you've already done so. One of the devs will be able to take a look at it and hopefully be able to tell you what the problem is.
Sent from my EVO using xda premium