Related
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?
Hey guys, I'm new but have been reading these forums for a while. I've rooted and unlocked 3 phones of mine with no problems but My HTC Evo LTE was ready for an upgrade so I tried to install a new rom, in the process I accidentally erased my back up. I have apps and system back up on titanium. I've read the don't panic thread, nothing helped. I've tried flashing the kernel and just about everything I know how to do.
So right now I have an unlocked device Jewel S-on, hboot 1.12, radio 1.02.12.0427 with TWRp Recovery installed. I have tried Vipers jellybean rom, Mean Rom ICS, and and a rooted stock rom.
All do the same thing, TWRP starts installing the rom and then it reboots real quick before the bar gets to 1/2, it reboots in the HTC quietly brilliant screen and the bar in the upper right goes up twice and then it just freezes and sits on the screen forever until i power it down and reboot into bootloader and nothing is installed. any ideas?
What version of twrp are you using?
You may not have the latest twrp recovery. Older versions will reboot or fail on install. There have been a few changes to the installers, especially with son users since hboots have become more restricted
bigdaddy619 said:
What version of twrp are you using?
Click to expand...
Click to collapse
Let's see, I'm running.....TWRP 2.4.1.0
mxbmx930 said:
Let's see, I'm running.....TWRP 2.4.1.0
Click to expand...
Click to collapse
download this and try 2.3.1.0 http://d-h.st/R9E
2.4.1.0 does not work properly unless you are using a 3.16 rom with updated binaries and you have the latest firmware installed
Glad I decided to hold off on updating twrp then
om4 said:
Glad I decided to hold off on updating twrp then
Click to expand...
Click to collapse
There is nothing wrong with the latest twrp, but the rom you are installing has to be compatible with it. The newest MeanBean is. It's kind of funny that the op has the most out of date phone firmware you can have but somehow updated his twrp to the newest available.
Sent from my icrap 2 using Tapatalk HD
bigdaddy619 said:
download this and try 2.3.1.0
2.4.1.0 does not work properly unless you are using a 3.16 rom with updated binaries and you have the latest firmware installed
Click to expand...
Click to collapse
Wow, so easy. I can't believe I spent all those hours frustrated trying to figure what I was doing wrong. I put 2.3.1 on and first try, installed fine. I have one more question, I downloaded titanium to reinstall everything and it's saying ERROR: I could not acquire root privileges, this app will not work. I installed Viperboys Stock Rooted 3.15.651.16 deodexed and SU is on there, I even updated it. Any ideas?
thanks a lot for the help so far.
cruise350 said:
There is nothing wrong with the latest twrp, but the rom you are installing has to be compatible with it. The newest MeanBean is. It's kind of funny that the op has the most out of date phone firmware you can have but somehow updated his twrp to the newest available.
Sent from my icrap 2 using Tapatalk HD
Click to expand...
Click to collapse
I usually wait at least a week to see if any problems come up
Everytime I go to make a call or receive a call the phone force closes and then signal drops off. I have flashed new kernals and have done a clean Rom install and problem continues. Any help would be greatly appreciated.
Sent from my HTC6435LVW using xda app-developers app
saabguy93 said:
Everytime I go to make a call or receive a call the phone force closes and then signal drops off. I have flashed new kernals and have done a clean Rom install and problem continues. Any help would be greatly appreciated.
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
Try reflashing a kernel. Might try stock first, then maybe Elkay's or dsb's writeable.
In case you're doing it a different way, try flashing it this way: flash the boot.img using the Flash Image GUI app. Then flash the corresponding modules for that specific boot.img kernel (can't mix and match) in Recovery.
If that doesn't help the situation, you may need to flash a different radio.
HTH!
saabguy93 said:
Everytime I go to make a call or receive a call the phone force closes and then signal drops off. I have flashed new kernals and have done a clean Rom install and problem continues. Any help would be greatly appreciated.
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
have you tried a completly different rom?
.torrented said:
have you tried a completly different rom?
Click to expand...
Click to collapse
I have relocked my bootloader. Loaded the stock RUU and then Unlocked again, rerooted and installed Viper Rom and still same Issue.
saabguy93 said:
I have relocked my bootloader. Loaded the stock RUU and then Unlocked again, rerooted and installed Viper Rom and still same Issue.
Click to expand...
Click to collapse
Have you tried a different SIM.
Sent from my HTC6435LVW using xda app-developers app
Perhaps you accidentally flashed your radio partition? Reflash your radio and you'll probably be good to go. Either that or like someone else said try a different sim card.
Bigandrewgold said:
Have you tried a different SIM.
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
I put the SIM in my Nexus and I dont have any problems at all.
saabguy93 said:
I put the SIM in my Nexus and I dont have any problems at all.
Click to expand...
Click to collapse
Like the other guy said, try flashing a radio.
Sent from my HTC6435LVW using xda app-developers app
Bigandrewgold said:
Like the other guy said, try flashing a radio.
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
Flashed the new radio and still a no go. I keep getting "com.android.phone" force close when i go to dial a number.
Run the RUU again but this time try and just booting into android from the RUU and trying to use your phone
saabguy93 said:
Flashed the new radio and still a no go. I keep getting "com.android.phone" force close when i go to dial a number.
Click to expand...
Click to collapse
If you are getting com.android.phone fcs. then reflash ruu, DL' a rom of choice on your computer and transfer using ADB push (will take a second) . reboot to bootloader. flash boot.img, boot to recovery, flash modules, then flash custom rom. when phone reboots, wait about 45 seconds before running setup. If this process still does not work, please report back. Or PM me or another RC so we can figure it out for you in a quick manner.
Well this morning I switched to CWM recovery and loaded Digital Dream 1.5 and I'm back working. Thanks for everyone's help.
Sent from my HTC6435LVW using xda app-developers app
saabguy93 said:
Well this morning I switched to CWM recovery and loaded Digital Dream 1.5 and I'm back working. Thanks for everyone's help.
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
Yeah so it was a rom issue then
Sent from my HTC6435LVW using XDA Premium HD app
Not a Rom issue, I've had the problem on viper and hatka, both before and after soff and new radio. New kernel, old kernel.
I'm getting ready to try stock 1.15 before I ruu.. will report back.
Edit: Fresh off RUU, with the old radios flashed before the RUU. Still no change. Tried turning phone off, remove sim card, phone on, try to use cell connection (obvious failure), phone off, insert sim card and boot. Still no good. About to try above method using CWM and Digital Dream, as soon as it downloads.
Edit 2: Still no such luck. After digging through system logs, there's quite a few errors pertaining to the radio, IccCard, and RIL. One that particularly caught my eye was an error that there stated Ril_get_icc_status returned an error, and it should never return an error. Unfortunately, I didn't get a capture on the time I saw that, the radio reset which Su to reset which caused catlog to reset. Still have quite a few errors pertaining to SIM problems as well. I am way over my head after this point. I can interpret java, and linux.. but not so much understand when they're mixed together in Android.
http://www.pastebin.ca/2317800 This is logcat capture I got of the radio log. Unknown technology doesn't sound good to me....
http://db.tt/nbYfqEkb A full system log as soon as I could save after the force close. Couple things here and there.
I suppose if I can't get it fixed in a day or two.. off Verizon for a replacement. What's the purpose of a phone if I can't make phone calls on it?
Sent from my HTC6435LVW using xda premium
Unless an error loops continually, its okay.
Have you tried to manually select a different network? I'm not quite sure how to do it on a sense rom, but I do know that when I was messing around within my CM10 build and changed to the wrong network type, I lost 4G data in sense. I reflashed CM10, selected a different network and then flashed back and it was working.
Have no fear...
THE MAN IS HERE!!!
OK guys honestly if it's up to me, we should all be scared ****less if we were relying on me. I bought a DNA with this problem to see if I could fix it and so far I've relocked, run the RUU twice (executable 1.15) unlocked and flashed recovery and done clean rom installs, kernels, switched to every network mode imaginable. I took my sim out of my DNA working perfectly so I know the sim is good in a different DNA.
I just flashed the 2.04 radios and I'm going to see what that does. I promise I'm going to give this issue my everything though because I gave a lot for this phone that's otherwise NIB condition and MINT. OK and the radios didn't help
CharliesTheMan said:
Have no fear...
THE MAN IS HERE!!!
OK guys honestly if it's up to me, we should all be scared ****less if we were relying on me. I bought a DNA with this problem to see if I could fix it and so far I've relocked, run the RUU twice (executable 1.15) unlocked and flashed recovery and done clean rom installs, kernels, switched to every network mode imaginable. I took my sim out of my DNA working perfectly so I know the sim is good in a different DNA.
I just flashed the 2.04 radios and I'm going to see what that does. I promise I'm going to give this issue my everything though because I gave a lot for this phone that's otherwise NIB condition and MINT. OK and the radios didn't help
Click to expand...
Click to collapse
Any luck figuring this out? I have the same issue and have tried radios, kernels, ROMs, RUU, and am still getting the same error message.
jc332986 said:
I was having "com.android.phone" issues. I relocked then ran the RUU. It didn't fix the error. I unlocked, tried to go Into recovery and there was no recovery. I flashed cwm recovery, flashed busy box/superuser, and rebooted. I flashed cubed kernel. The fix for the phone was to fix permissions with system write capabilities. I'm not sure why the RUU didn't put the phone all the way back to stock.
Click to expand...
Click to collapse
spjoneser said:
I had this problem with my first DNA, warrantied it out after trying all the same things, flashing different roms, RUUing. After replacement I came across a thread somewhere and found that someone had fixed the same problem by simply fixing permissions before doing anything else, sounds like once you flash something else you're screwed.
Anyone try that first?
Click to expand...
Click to collapse
Anyone have an idea about the permissions described here?
same issue
dragonstalker said:
If you are getting com.android.phone fcs. then reflash ruu, DL' a rom of choice on your computer and transfer using ADB push (will take a second) . reboot to bootloader. flash boot.img, boot to recovery, flash modules, then flash custom rom. when phone reboots, wait about 45 seconds before running setup. If this process still does not work, please report back. Or PM me or another RC so we can figure it out for you in a quick manner.
Click to expand...
Click to collapse
This is driving me crazy I have same issue mine won't make or receive calls after I did s-off get same message com.androd.phone fcs. I re-locked phone then flashed original rom. Turned on phone still have same problem. So at that point I flashed kernalls h-boot and radios booted still same problem. Then I decided to re-flash RUU rom still same problem. Please help don't know what to do next.:crying:
jimmydee62 said:
This is driving me crazy I have same issue mine won't make or receive calls after I did s-off get same message com.androd.phone fcs. I re-locked phone then flashed original rom. Turned on phone still have same problem. So at that point I flashed kernalls h-boot and radios booted still same problem. Then I decided to re-flash RUU rom still same problem. Please help don't know what to do next.:crying:
Click to expand...
Click to collapse
I'm in the same boat with you my friend :crying:...Can someone please help us. PLEASE!!!
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
I flashed demon dust Rom a couple weeks ago and wanted to reflash cm11. I got the status 7 in cwm and error executing binary script updater in TWRP. I have flashed RUU twice and tried different recovery versions but I keep getting the same errors... Any suggestions???
I switched to twrp and had the same issue, and when I switched back to clockwork mod everything was fine again. You might be having the reverse effect happening. I am on VZW as well.
Sjflowerhorn said:
I switched to twrp and had the same issue, and when I switched back to clockwork mod everything was fine again. You might be having the reverse effect happening. I am on VZW as well.
Click to expand...
Click to collapse
Thanks for replying, but i have been switching back and forth between recoveries and nothing is working
herzig.grant said:
Thanks for replying, but i have been switching back and forth between recoveries and nothing is working
Click to expand...
Click to collapse
I tried to look this up in Google and no one really has or had the same issue as me
if you have been trying the newest versions have you tried older versions or vice versa?
And are you flashing the recovery in adb using fastboot or using an app from the market? I finally had success using Rashr from the market since my laptop recently had the battery go and I still haven't unpacked my desktop since moving recently.
herzig.grant said:
I flashed demon dust Rom a couple weeks ago and wanted to reflash cm11. I got the status 7 in cwm and error executing binary script updater in TWRP. I have flashed RUU twice and tried different recovery versions but I keep getting the same errors... Any suggestions???
Click to expand...
Click to collapse
Were you using Fly's version of TWRP?
bfisch3r said:
Were you using Fly's version of TWRP?
Click to expand...
Click to collapse
I wasnt at the time.. But i figured out the problem yesterday. Guess i forgot to close this
herzig.grant said:
I wasnt at the time.. But i figured out the problem yesterday. Guess i forgot to close this
Click to expand...
Click to collapse
Ok, glad you got it figured out. Was the version of TWRP the issue?
bfisch3r said:
Ok, glad you got it figured out. Was the version of TWRP the issue?
Click to expand...
Click to collapse
Yeah i was using the non aosp friendly version.... Lol i can be such a n00b sometimes
Thread has been closed at OP's request.
Stephen