Hey all
I've done the searching through all of the forums on here, and all around Google. I decided today that I was going to root my phone and get a custom rom in it. I first started out with CM7, and that just kept going into an endless boot cycle where it never actually booted up.
Since that didn't work, I tried a different rom, which did the same thing, but just never made it past the HTC screen. Now I've tried to do honestly everything that I could possibly think of just to get the phone to boot up and work, and the thing that got it the closest was installing a stock rom.
Once I installed a stock Rom, I booted it up, and it started up until it got to the lock screen. It started to look like it was going to go, but just got to the lock screen and reboots from there. I don't know what to do, and RUU won't recognize that my phone is even there, and the Bootloader won't recognize the RUU .zip file.
I'm not sure what to do, and at this point I just want a working phone. I can get a video of exactly what's going on if it would help. Video is up on Youtube. /watch?v=jCF_-7ZP-CQ
Edit: For more Info - CDMA, HBOOT 1.58.0000, S-ON, Unlocked, Don't know Baseband, using TWRP1.1.1 Recovery, and the last ROM I had attempted was Sick Sense. vx.1.
More info would definately increase the likelyhood of getting your phone up and running . Hboot version, cdma or gsm, s-on or s-off, and if possible baseband, recovery and what rom?
( Don't ask me for help, as I couldn't care if your phone explodes, eh!!!)
flashallthetime said:
More info would definately increase the likelyhood of getting your phone up and running . Hboot version, cdma or gsm, s-on or s-off, and if possible baseband, recovery and what rom?
( Don't ask me for help, as I couldn't care if your phone explodes, eh!!!)
Click to expand...
Click to collapse
Alright, updated the first post, thanks.
Seems you need to flash the kernel via fastboot since you're s-on, everything seems to point to that, although I could be wrong..
Sent from my PG86100 using xda app-developers app
No problem, wish I could help you but unfortunately I have the gsm version, hboots are issues on some roms and being s-on wont allow you to flash the kernel , so 4ext recovery helps. You may also might look at going s-off too. Hope you get your answer. In the Q&A stickies you will see ask team drp any question, you may get answers there also
( Don't ask me for help, as I couldn't care if your phone explodes, eh!!!)
beneath-a-burning-turtle said:
Seems you need to flash the kernel via fastboot since you're s-on, everything seems to point to that, although I could be wrong..
Sent from my PG86100 using xda app-developers app
Click to expand...
Click to collapse
I thought that you couldn't flash the Kernel without being S-Off? I put the video in the first post, maybe that will help?
flashallthetime said:
More info would definately increase the likelyhood of getting your phone up and running . Hboot version, cdma or gsm, s-on or s-off, and if possible baseband, recovery and what rom?
Click to expand...
Click to collapse
You know, that would make a good guide.
A thread with screenshots of where to find all the relevant information with a text attachment consisting of a template to be completed and attached to the OP of a new thread asking for help. Or just an inline form that could be copied and pasted into the OP and completed before it is posted.
Maybe "How to ask for help" would be a good title for the guide.
Any takers?
ramjet73
Go ahead I'm banned hahahahahahah
( Don't ask me for help, as I couldn't care if your phone explodes, eh!!!)
---------- Post added at 09:32 PM ---------- Previous post was at 09:31 PM ----------
I could start a thread with screen shots and info required
( Don't ask me for help, as I couldn't care if your phone explodes, eh!!!)
---------- Post added at 09:36 PM ---------- Previous post was at 09:32 PM ----------
As I would like to contribute in positive way
( Don't ask me for help, as I couldn't care if your phone explodes, eh!!!)
flashallthetime said:
Go ahead I'm banned hahahahahahah
Click to expand...
Click to collapse
I've got a guide thread already. It can wait until you are unbanned.
I was thinking that if there's a free app that displays all the information on a single screen that might be even easier, but that won't help if people can't boot into Android. Come to think of it, there may be some info available from 4EXT and other custom recoveries that would help, but in the worst case it may come down to just the bootloader info.
It's probably easier just to ask when the info is needed since the procedure to get it depends on the situation.
ramjet73
So... Okay. While I fully support the idea of having an FAQ on what to do to ask a question, I did make some headway.
I ended up flashing a new ROM, and it booted up and it all worked until the only thing on the screen was process android.process.acore has stopped. And whenever I press OK, it just pops right up. I've read places that I need to factory reset, wipe all the caches, and reflash. Does this all sound right?
Ryphon said:
I thought that you couldn't flash the Kernel without being S-Off? I put the video in the first post, maybe that will help?
Click to expand...
Click to collapse
Sorry, I didn't mean to ignore you but I got distracted with the system info guide discussion.
You can flash a kernel (boot.img) with S-ON three different ways:
1. Using the "fastboot flash boot boot.img" command from a PC.
2. Using the Flash Image GUI app from a booted Android system.
3. Using the SmartFlash (S-ON) feature of 4EXT.
In your situation, I would recommend #1, since #2 and #3 require some setup. You could also use the "fastbboot boot recovery.img" command to start a custom recovery, then flash the entire ROM from there which will incude the kernel.
In the long run, I would suggest getting setup for #3 if you plan to stay S-ON.
---------- Post added at 03:52 PM ---------- Previous post was at 03:46 PM ----------
Ryphon said:
So... Okay. While I fully support the idea of having an FAQ on what to do to ask a question, I did make some headway.
I ended up flashing a new ROM, and it booted up and it all worked until the only thing on the screen was process android.process.acore has stopped. And whenever I press OK, it just pops right up. I've read places that I need to factory reset, wipe all the caches, and reflash. Does this all sound right?
Click to expand...
Click to collapse
It would be a good idea to use one of the superwipe zip files or the 4EXT "format all partitions excep SD card" before flashing the ROM. If you are only flashing a kernel, wiping cache+dalvik is all that is necessary and many of the installation scripts already have that included.
Sometimes if apps force close (FC) after a ROM flash the permissions need to be reset in recovery, but I think your problem is related to not formatting the partitions before flashing the ROM.
What ROM are you flashing? There are usually instructions for flashing on the OP of most of the ROM threads that include the required partition initialization.
ramjet73
Hey, sorry for not replying til now. I ended up just wiping it clean one more time with 4ext, clearing cache, and fixing permissions, then installing a new Rom that actually worked. I had to flashboot the boot.img, but regardless I got it to actually start up and work like a normal phone. You definitely gave me inspiration on what to try next, so thanks for that. Not even sarcastic. I ended up flashing the Team D3rp Drama rom, and after some permissions and cache cleaning up, it ended up working fine.
Ryphon said:
Hey, sorry for not replying til now. I ended up just wiping it clean one more time with 4ext, clearing cache, and fixing permissions, then installing a new Rom that actually worked. I had to flashboot the boot.img, but regardless I got it to actually start up and work like a normal phone. You definitely gave me inspiration on what to try next, so thanks for that. Not even sarcastic. I ended up flashing the Team D3rp Drama rom, and after some permissions and cache cleaning up, it ended up working fine.
Click to expand...
Click to collapse
Now that you have a working ROM, try enabling the S-ON (SmartFlash) option in the 4EXT app. The next time you flash a ROM or kernel from 4EXT recovery you will know it worked if the phone boots twice, the first time to flash the boot partition (boot.img) and the second to boot into the actual ROM.
ramjet73
Related
Okay so i've had my htc evo 3d for a while and i decided to root it finally.
i rooted it, everything was fine, it was s-on.
i flashed like 3 roms and everything was great, ....until i flashed a kernel.
i first used the MAC kernel, and it worked great.
but then i flashed the "No name" kernel from the same creator from the MAC kernel for the htc evo 3d and i got bootloops?
i also noticed it sent me back to Hboot 1.57 somehow? and i was on 1.58?
so, i went back into 4ext recovery and wiped everything and flashed a stock rom i had.
yet, i still have the bootloop going on...
what do i do? i really want my htc evo 3d back, i had to go back to my lg optimus V for now until someone can help me :/
Thank you for your time, and to whoever helps me with my semi-bricked device
Firemanzeus said:
Okay so i've had my htc evo 3d for a while and i decided to root it finally.
i rooted it, everything was fine, it was s-on.
i flashed like 3 roms and everything was great, ....until i flashed a kernel.
i first used the MAC kernel, and it worked great.
but then i flashed the "No name" kernel from the same creator from the MAC kernel for the htc evo 3d and i got bootloops?
i also noticed it sent me back to Hboot 1.57 somehow? and i was on 1.58?
so, i went back into 4ext recovery and wiped everything and flashed a stock rom i had.
yet, i still have the bootloop going on...
what do i do? i really want my htc evo 3d back, i had to go back to my lg optimus V for now until someone can help me :/
Thank you for your time, and to whoever helps me with my semi-bricked device
Click to expand...
Click to collapse
It's not a Rom or kernel issue, try flashing my pg86img.zip in the EVO 3d gsm development thread, adding your own cid to the text file (this has only been tested on gsm) but if your already looping what's the harm in trying
But my htc is CDMA. Sorry I forgot to mention it's from virgin Mobile.
Sent from my LG-VM670 using xda premium
Firemanzeus said:
But my htc is CDMA. Sorry I forgot to mention it's from virgin Mobile.
Sent from my LG-VM670 using xda premium
Click to expand...
Click to collapse
I don't think that's even relevant, but I'm gsm and can't test cdma so I can't tell you it works, but on another note, where's the harm in trying
S-on is an issue, I believe because you are s-on the kernel flash was bad, some kernels require s-off , did you try another kernel, or flashing bootimg through fastboot
Signature (Don't ask me for help, couldn't careless if your phone explodes)
flashallthetime said:
S-on is an issue, I believe because you are s-on the kernel flash was bad, some kernels require s-off , did you try another kernel, or flashing bootimg through fastboot
Signature (Don't ask me for help, couldn't careless if your phone explodes)
Click to expand...
Click to collapse
Yeah I think it's an issue too. I've tried flashing the MAC kernel that worked before and nothing. Where can I find a bootimg? Is it the same as pg86img?
Sent from my LG-VM670 using xda premium
No, pg86img is the firmware but some Roms have the bootimg within the zip, just open your Rom with WinZip or 7zip extract bootimg and place it on your sdcard and flash it with fastboot
Signature (Don't ask me for help, couldn't careless if your phone explodes)
---------- Post added at 06:44 PM ---------- Previous post was at 06:42 PM ----------
Or try to wipe dalvik and cache and refresh the kernel
Signature (Don't ask me for help, couldn't careless if your phone explodes)
Okay, so I went into bootloader and tried going to recovery, and I guess I don't have a recovery anymore? Is there anything I can flash for one? So I can wipe dalvik and so on.
Sent from my LG-VM670 using xda premium
The unnamed kernel requires S-OFF to work correctly
You can try 4ext, but you might need to run a ruu and.start from scratch again?
Signature (Don't ask me for help, couldn't careless if your phone explodes)
---------- Post added at 07:19 PM ---------- Previous post was at 07:15 PM ----------
I asked about a month ago for the mods to verify if a kernel requires s-off to be flashed, see what happens. if you can I would recommend going s-off.
Signature (Don't ask me for help, couldn't careless if your phone explodes)
flashallthetime said:
You can try 4ext, but you might need to run a ruu and.start from scratch again?
Signature (Don't ask me for help, couldn't careless if your phone explodes)
---------- Post added at 07:19 PM ---------- Previous post was at 07:15 PM ----------
I asked about a month ago for the mods to verify if a kernel requires s-off to be flashed, see what happens. if you can I would recommend going s-off.
Signature (Don't ask me for help, couldn't careless if your phone explodes)
Click to expand...
Click to collapse
I know right? I looked at the the forum again and It nowhere says I need s off.... So it just screwed me over cause I was s-on. Where can I find a Ruu? Sorry, I'm kinda new to all this.
If I need to go back to factory stock unrooted, I don't care, I just want my evo 3d to boot up again Haha.
Sent from my LG-VM670 using xda premium
Stickies are where you will find them, might be in cdma development stickies, ask around and see what others think, maybe they will have other suggestions
Signature (Don't ask me for help, couldn't careless if your phone explodes)
Alright, thanks for your replies. Hopefully I'll get this fixed, if not, it's 300$ down the drain..
Sent from my LG-VM670 using xda premium
No it's fixable, again ruu will cure most issues but b4 you do that, ramjet, he knows a lot ask him otherwise there's a thread under Q & A stickies where you can ask any question
Signature (Don't ask me for help, couldn't careless if your phone explodes)
flashallthetime said:
No it's fixable, again ruu will cure most issues but b4 you do that, ramjet, he knows a lot ask him otherwise there's a thread under Q & A stickies where you can ask any question
Click to expand...
Click to collapse
If you have the Virgin Mobile version of the Evo 3D the RUU.exe you want to use is the fourth one from the top on this page.
To flash the RUU.exe, if you have HTC unlocked the bootloader you will need to "fastboot oem lock" with the phone in the "fastboot USB" mode in the bootloader, then start the RUU.exe from Windows. It takes about 10 minutes to run and should leave you with a totally stock configuration, except the bootloader will say "***RELOCKED***" at the top instead of "***LOCKED***".
Before you run that it might be worth starting 4EXT recovery by using "fastboot boot recovery.img" from a PC and flashing a mostly stock rooted ROM like MeanROM ICS or CleanROM BE ICS because it sounds like you may just have a non-bootable kernel and 4EXT SmartFlash required for flashing kernels directly from recovery with S-ON won't work if the current kernel is not bootable. You could also try flashing the stock VM kernel from here after using the fastboot command to start recovery.
ramjet73
See you ask and he shall reply, hope it solves your problem, good luck
Signature (Don't ask me for help, couldn't careless if your phone explodes)
Firemanzeus said:
Okay so i've had my htc evo 3d for a while and i decided to root it finally.
i rooted it, everything was fine, it was s-on.
i flashed like 3 roms and everything was great, ....until i flashed a kernel.
i first used the MAC kernel, and it worked great.
but then i flashed the "No name" kernel from the same creator from the MAC kernel for the htc evo 3d and i got bootloops?
i also noticed it sent me back to Hboot 1.57 somehow? and i was on 1.58?
so, i went back into 4ext recovery and wiped everything and flashed a stock rom i had.
yet, i still have the bootloop going on...
what do i do? i really want my htc evo 3d back, i had to go back to my lg optimus V for now until someone can help me :/
Thank you for your time, and to whoever helps me with my semi-bricked device
Click to expand...
Click to collapse
You should reflash a Stock ROM from RUU or extract ROM.ZIP to flash via Fastboot.
ramjet73 said:
If you have the Virgin Mobile version of the Evo 3D the RUU.exe you want to use is the fourth one from the top on this page.
To flash the RUU.exe, if you have HTC unlocked the bootloader you will need to "fastboot oem lock" with the phone in the "fastboot USB" mode in the bootloader, then start the RUU.exe from Windows. It takes about 10 minutes to run and should leave you with a totally stock configuration, except the bootloader will say "***RELOCKED***" at the top instead of "***LOCKED***".
Before you run that it might be worth starting 4EXT recovery by using "fastboot boot recovery.img" from a PC and flashing a mostly stock rooted ROM like MeanROM ICS or CleanROM BE ICS because it sounds like you may just have a non-bootable kernel and 4EXT SmartFlash required for flashing kernels directly from recovery with S-ON won't work if the current kernel is not bootable. You could also try flashing the stock VM kernel from here after using the fastboot command to start recovery.
ramjet73
Click to expand...
Click to collapse
Thanks alot for your reply ramjet,
okay, well i tried downloading the 4th one from where you told me and file factory is giving me a "problem loading page" so i cant download it. i have my htc locked now and it says ***RELOCKED*** so all i need to do now is install the 4ext recovery through bootloader and flash the rom and kernel and run RUU,but i need your download.
Edit: So i tried flashing recovery.img through fastboot and i got "cannot load 'recovery.img'" ?
No, ramjet told you to flash 4ext recovery before you do anything, now you can't flash recovery because you have a locked bootloader.
if you still want to go the 4ext way, you will have to unlock bootloader via htcdev.com again or use the same unlock code.bin that you used previously. then fastboot flash the recovery. then get a Rom that works with your bootloader version and flash it using 4ext recovery with smartflash turned on.
mnomaanw said:
No, ramjet told you to flash 4ext recovery before you do anything, now you can't flash recovery because you have a locked bootloader.
if you still want to go the 4ext way, you will have to unlock bootloader via htcdev.com again or use the same unlock code.bin that you used previously. then fastboot flash the recovery. then get a Rom that works with your bootloader version and flash it using 4ext recovery with smartflash turned on.
Click to expand...
Click to collapse
EDIT: So i managed to re-unlock it, and now im fasboot flashing the Recovery.img, the recovery works now! i have 4ext. what should my next steps be to getting my htc evo 3d back?
i rooted my htc evo lte in the midst of installing the rom it wouldnt load, i deleted the os by accident now trying to figure out how to get back into the phone to reinstall it but cant figure it out any help is appreciated thanks
sickamoose239 said:
i rooted my htc evo lte in the midst of installing the rom it wouldnt load, i deleted the os by accident now trying to figure out how to get back into the phone to reinstall it but cant figure it out any help is appreciated thanks
Click to expand...
Click to collapse
did you try holding down the power and volume buttons to load your recovery?
---------- Post added at 02:54 PM ---------- Previous post was at 02:25 PM ----------
May I ask if you can be more specific? such as; what build OTA you have, hboot version, what recovery you have, which rom and/or kernel you are trying to flash, and if you are s-on or s-off
I had a similar problem. I unlocked and rooted my EVO LTE ... Then I tried to install a custom ROM and it just got stuck at the boot animation. I didnt do a back up or anything so I was just stuck. I was able to get into Recovery. As a matter of fact I fixed it last night by loading up flashing that superwipe zip and flashing Stock with Goodies ROM. Now my EVO LTE works fine.
Sent from my PC36100 using xda app-developers app
lmvcorp said:
I had a similar problem. I unlocked and rooted my EVO LTE ... Then I tried to install a custom ROM and it just got stuck at the boot animation. I didnt do a back up or anything so I was just stuck. I was able to get into Recovery. As a matter of fact I fixed it last night by loading up flashing that superwipe zip and flashing Stock with Goodies ROM. Now my EVO LTE works fine.
Sent from my PC36100 using xda app-developers app
Click to expand...
Click to collapse
Alright so I am having the same problem with the Paranoid Android ROM it won't boot past the boot animation. I don't have the superwipe zip and the only other ROM I have on my phone is ViperROM which won't even flash. Any help would be appreciated.
You most likely need to flash the kernel. I'm assuming you're s-on?
metalfan78 said:
You most likely need to flash the kernel. I'm assuming you're s-on?
Click to expand...
Click to collapse
I am S-on. how do I flash the Kernel? and where do I find it? thanks again for all your help.
There are a lot of guides in the development section. I'm s-off, I've never had to do it. Sorry I can't help more.
metalfan78 said:
There are a lot of guides in the development section. I'm s-off, I've never had to do it. Sorry I can't help more.
Click to expand...
Click to collapse
it's cool. thanks man. yeah, i had my other EVO 4G LTE that was s-off and rooted a friend's phone that was s-off. just recently recieved a replacement phone for my stolen one and followed the same method but s-on. so frustrating. thanks for all your help though!
extract the boot image from the rom, place it in adb folder and open cmd in that folder
shift+right click, open command window here
then connect phone in fastboot and type fastboot flash boot boot.img
Om4 is always around to rescue people!
randmc562 said:
I am S-on. how do I flash the Kernel? and where do I find it? thanks again for all your help.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1917106 this might help it's an image flasher run from your PC
Hey there
I had the same problem, just when I loaded the goodies rom it crashed. Can't do anything, except boot into TWRP. Basically if I try to reflash a rom it should solve my problem?
Most likely you need to flash the kernel, use that image flash app or adb tools/android SDK to flash it in fastboot
I had a feeling
First, thanks
Ok, can I use TWRP to flash the Kernel or is there an app or pc that ill have to use?
You can use fastboot to flash the kernel or the image flash app, I havent got a link for it right now but its probably in themes and apps or original development
No PC
I don't have a PC to use. I'm wondering if I could go recovery->advance->terminal command. I see a fast lot process, but requires a PC.
Not that I know of, you need access to fastboot
Dumlock?
Reading on dumlock, else return to project when computer is available. Thanks for the help.
You can't use dumlock without access to android
So it appears
*sigh* got all excited flashed a rom without a kernel, and now **** out of luck. Seemed so much easier for my OGEVO. So my only option is to do a fast boot with a PC using the .zip I have on the sdcard?
Hey guys,
I was running the latest Viper rom. Every great once in a while the phone would just turn off. I could get it back fine and this happened about 5-6 times. Today the phone got stuck in a boot loop. I figured something went wrong.
I attempted to restore the phone to stock using the RUU thread found here: http://forum.xda-developers.com/showthread.php?t=2152993
I restored it once fine, said it was good. Phone only rebooted over and over. The HTC logo came up 3-4 times then screen went blank. So I flashed again. Same thing, nothing.
Now I had been playing around and think I updated my radio. Now the RUU from that thread above says it cannot upgrade my phone. I can get to fastbook and lock and unlock the bootloader. I did install latest TWRP but it never enters recovery. I had hoped to just install a basic rom from the 2.04 update and be done. But I cannot get into recovery.
I'm stuck and don't know what else to do. Is there and RUU file like the one above for the new 2.04?
I still think something else is wrong with this phone. Somehow doubt VZW will take it back and exchange.
S-ON
Phone displays HBOOT-1.33.0001
RADIO-1.01.01.0110
Any ideas what I can do next please?
I think the radio got updated when I tried to do S-OFF. Instead of an error at step 3 it flashed. Now I've gone back and tried it again and though I get the proper errors is still shows S-ON. Maybe this isn't even needed. I think my days of tinkering with Android should be over. I can follow guides and such
When I try to enter recovery for TWRP I get a lot of colored lines. Going to try reflashing that and see what gives. I feel that if I could get into TWRP and get a rom file on the phone since I cannot get into Android I might have a chance.
Tersanyus said:
I think the radio got updated when I tried to do S-OFF. Instead of an error at step 3 it flashed. Now I've gone back and tried it again and though I get the proper errors is still shows S-ON. Maybe this isn't even needed. I think my days of tinkering with Android should be over. I can follow guides and such
When I try to enter recovery for TWRP I get a lot of colored lines. Going to try reflashing that and see what gives. I feel that if I could get into TWRP and get a rom file on the phone since I cannot get into Android I might have a chance.
Click to expand...
Click to collapse
Did you take the verizon update as you mentioned 2.04? If you did you will have to wait a bit yet to root again. Your only option would be stock verizon. Their software update basically closed the previously open window. If not...You HAVE updated radio per the # you posted, not sure if that really matters with regard to recovery. It seems like you have compounded many issues. I would try relocking bootloader and flash stock RUU again. Try to get back to stock verizon. If that's a no go, would try reflashing old radio and try stock ruu. How are you getting to try bootloader/recovery, turning on phone holding down vol button? Last ditch if it's says s-on and locked, I think you would be ok to try for a new phone.
I did not take the OTA from Verizon. I never got any prompt for an update. I did the updates for Viper that turned I think just turned that off.
Getting to bootloader is fine. I can lock it and unlock it fine. I know the RUU only loads if locked. I know recovery can only be installed if unlocked I believe. And yes I do that from vol down plus power button.
If I use newest TWRP recovery just gives a whole bunch of colored lines. If I try 2.4.0.0 I can see TWRP come up briefly then the phone reboots again.
The RUU exe file just now gives error 158. Basically it thinks it is not the correct ROM
I found the 1.15 radio but it won't flash. http://forum.xda-developers.com/showpost.php?p=38379254&postcount=19
Just gives error of FAILED remote: 92 supercid
Tersanyus said:
The RUU exe file just now gives error 158. Basically it thinks it is not the correct ROM
I found the 1.15 radio but it won't flash. http://forum.xda-developers.com/showpost.php?p=38379254&postcount=19
Just gives error of FAILED remote: 92 supercid
Click to expand...
Click to collapse
Is there a boot.img for the ruu? Maybe the previous boot image is still directing the process, a thought at least. Also that error 92 cid MAY be the issue, Do you have the newest one on (cid)? I had a lot of issues getting s-off and had to run supercid again to run the process after several error 92 messages. I would look at the whole s-off thread in original dev section maybe some answers in there or a direction to head in.
---------- Post added at 10:39 AM ---------- Previous post was at 09:48 AM ----------
rootntootn said:
Is there a boot.img for the ruu? Maybe the previous boot image is still directing the process, a thought at least. Also that error 92 cid MAY be the issue, Do you have the newest one on (cid)? I had a lot of issues getting s-off and had to run supercid again to run the process after several error 92 messages. I would look at the whole s-off thread in original dev section maybe some answers in there or a direction to head in.
Click to expand...
Click to collapse
Can you get to fastboot? adb can communicate with the phone? Says in red fastboot usb? Also how are you doing RUU, assuming your using executable from your pc? Forgot to ask..
Yes I can get to fastboot fine. I do a "fastboot devices" and it is read. adb doesn't seem to do anything though. The RUU is the .exe I found.
For the cid I did the old one so mine reads all 1's. I didn't think I could so the new cid as I cannot boot into Android at all.
Ok success!! Yes.
I did the S-OFF directions once. Nothing, no change.
Did it again this time it booted to factory rom.
I am S-OFF cid is all ones.
I got the prompt for the OTA update, took ot, phone rebooted to recovery, TWRP, then nothing.
Wifi not working, I know I read about that so looks like I have a little more work.
Tersanyus said:
Ok success!! Yes.
I did the S-OFF directions once. Nothing, no change.
Did it again this time it booted to factory rom.
I am S-OFF cid is all ones.
I got the prompt for the OTA update, took ot, phone rebooted to recovery, TWRP, then nothing.
Wifi not working, I know I read about that so looks like I have a little more work.
Click to expand...
Click to collapse
Not sure how you got there s-off should have all 2's....but it sounds like progress. If you are back to recovery and have a rom to flash in your phone that's great...but you'll need adb working to flash the image file that's associated with it, that will likely fix your wifi issue as well. Even with S-off most of the roms still need to have their respective image files flashed but I am unsure about stock RUU, someone with more experience may know that answer and can maybe steer you in the right direction...
Tersanyus said:
Ok success!! Yes.
I did the S-OFF directions once. Nothing, no change.
Did it again this time it booted to factory rom.
I am S-OFF cid is all ones.
I got the prompt for the OTA update, took ot, phone rebooted to recovery, TWRP, then nothing.
Wifi not working, I know I read about that so looks like I have a little more work.
Click to expand...
Click to collapse
If you have a custom recovery then you can't install the ota. If you want the ota stuff you can install the Rom kernel and radio from it.
As far as wifi not working, just flash a kernel, right now it sounds like you have the modules from one kernel and the boot.img from another.
Sent from my HTC6435LVW using xda app-developers app
---------- Post added at 09:43 PM ---------- Previous post was at 09:40 PM ----------
rootntootn said:
Not sure how you got there s-off should have all 2's....but it sounds like progress. If you are back to recovery and have a rom to flash in your phone that's great...but you'll need adb working to flash the image file that's associated with it, that will likely fix your wifi issue as well. Even with S-off most of the roms still need to have their respective image files flashed but I am unsure about stock RUU, someone with more experience may know that answer and can maybe steer you in the right direction...
Click to expand...
Click to collapse
You don't need all 2s to get s off, you can do it with all ones without a problem.
Sent from my HTC6435LVW using xda app-developers app
Bigandrewgold said:
If you have a custom recovery then you can't install the ota. If you want the ota stuff you can install the Rom kernel and radio from it.
As far as wifi not working, just flash a kernel, right now it sounds like you have the modules from one kernel and the boot.img from another.
Sent from my HTC6435LVW using xda app-developers app
---------- Post added at 09:43 PM ---------- Previous post was at 09:40 PM ----------
You don't need all 2s to get s off, you can do it with all ones without a problem.
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
BTW There was nothing wrong with your phone, it's just that when you restored, you needed to flash the boot.img from your rom that you restored. It was most likely a kernel issue that we could correct with viper.
It sounds like you just need to install the matching rom and boot.img. If you're s off, just fastboot flash the boot.img for whatever rom you currently have installed. For the OTA update, you can install the radios without an RUU if you're s off.
I ran for several hours and several reboots on the RUU .exe file. When I downloaded a custom rom from http://forum.xda-developers.com/showthread.php?t=2150262 - That fan fine for an hour or so. Then boot loop over and over again. Thankfully I made a backup in twrp. I restored that and all is well.
I can't stand this factory rom, the part that really annoys me, besides the VZW bloat, is the recent apps button. For over a year with other HTC's I am used to making that the menu button. Had that in the custom rom.
So it looks like that rebooting loop just means I need to fastboot the boot.img?
I go back to the rom I linked about and fastboot the boot.img. I really liked viper rom but am going to stick to stock that is rooted and debloated.
My cid is all 1's since I did that before all this OTA came out. I did that about 3 weeks ago the day I got the phone.
Thanks for the tips. I'll let you know what happens when I go back to the rom above.
Bigandrewgold said:
If you have a custom recovery then you can't install the ota. If you want the ota stuff you can install the Rom kernel and radio from it.
As far as wifi not working, just flash a kernel, right now it sounds like you have the modules from one kernel and the boot.img from another.
Sent from my HTC6435LVW using xda app-developers app
---------- Post added at 09:43 PM ---------- Previous post was at 09:40 PM ----------
You don't need all 2s to get s off, you can do it with all ones without a problem.
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
Sorry about the 2's info but read that the older cid apk would no longer work (from thread below) and myself put on the new one which yields the all 2's. Bottom line, glad you made progress, hopefully problem resolved
http://forum.xda-developers.com/showthread.php?t=2109862
I have HTC Flyer. can boot into fastboot and recovery CWM 5.2. when i install ROM it doesnt boot. assuming cause its s-off?? so can i get s-off when i cant boot into OS.
thanks
techknewz1 said:
I have HTC Flyer. can boot into fastboot and recovery CWM 5.2. when i install ROM it doesnt boot. assuming cause its s-off?? so can i get s-off when i cant boot into OS.
thanks
Click to expand...
Click to collapse
You can unlock the bootloader via htc dev unlock (link), but that won't let the rom flash the new boot.img, you need to do that manually using fastboot usb (fastboot flash boot boot.img) otherwise you'll never boot up.
edit....
using htc dev gives you UNLOCKED instead of S-OFF, so long as you flash boot.img you'll be fine.
trstn said:
You can unlock the bootloader via htc dev unlock (link), but that won't let the rom flash the new boot.img, you need to do that manually using fastboot usb (fastboot flash boot boot.img) otherwise you'll never boot up.
edit....
using htc dev gives you UNLOCKED instead of S-OFF, so long as you flash boot.img you'll be fine.
Click to expand...
Click to collapse
I already have that
techknewz1 said:
I already have that
Click to expand...
Click to collapse
'
What do u have? HTCdev unlock or S off? What rom are u trying to flash?
Great mod/ROM. I will flash right away.
Wrong section. Questions belong in . . . .Q&A (believe it or not!).
Development is for posting work (mods, ROMs) that you have done, and want to share with others.
techknewz1 said:
I already have that
Click to expand...
Click to collapse
I'm assuming you have UNLOCKED via htc dev.... did you flash the new boot with fastboot as part of the install? (because the failing to boot issue is exactly what happens when you don't)
Thread moved to Q & A.
As with the issue, and I'm not a Flyer owner, but when you do a new ROM, don't you have to perform "wipes" in CWM? Like Data and System?
Just a thought.
MD
trstn said:
You can unlock the bootloader via htc dev unlock
Click to expand...
Click to collapse
Unlocking the bootloader is not needed (and pointless extra work) when the OP already has S-off.
Try to re-download the ROM, or try another ROM. If is still fails, try to re-install CWM.
---------- Post added at 03:58 PM ---------- Previous post was at 03:56 PM ----------
Moscow Desire said:
As with the issue, and I'm not a Flyer owner, but when you do a new ROM, don't you have to perform "wipes" in CWM? Like Data and System?
Click to expand...
Click to collapse
Yes, OP should always wipe Dalvik, cache, and user data (factory reset) before flashing a new ROM. System wipe shouldn't be necessary (is automatically formatted when the new ROM is flashed).
Failure to wipe user data alone may be a reason for the ROM not booting.
redpoint73 said:
Unlocking the bootloader is not needed (and pointless extra work) when the OP already has S-off.
Try to re-download the ROM, or try another ROM. If is still fails, try to re-install CWM.
---------- Post added at 03:58 PM ---------- Previous post was at 03:56 PM ----------
Yes, OP should always wipe Dalvik, cache, and user data (factory reset) before flashing a new ROM. System wipe shouldn't be necessary (is automatically formatted when the new ROM is flashed).
Failure to wipe user data alone may be a reason for the ROM not booting.
Click to expand...
Click to collapse
I was explaining how you can unlock the Flyer as I suspect they don't have S-OFF, rather they are UNLOCKED after using htcdev. Meaning manual flash of boot.img is needed with every flash or you get stuck in a black screen boot loop - the problem OP describes.
Agree to wipe Dalvik but you absolutely don't have to factory reset before flashing a new ROM. Sometimes yeah, but not always.
trstn said:
I was explaining how you can unlock the Flyer as I suspect they don't have S-OFF, rather they are UNLOCKED after using htcdev. Meaning manual flash of boot.img is needed with every flash or you get stuck in a black screen boot loop - the problem OP describes.
Click to expand...
Click to collapse
I took the OP to mean that he was S-off. But reading it again, its actually unclear whether he is S-on or S-off.
trstn said:
Agree to wipe Dalvik but you absolutely don't have to factory reset before flashing a new ROM. Sometimes yeah, but not always.
Click to expand...
Click to collapse
I always factory reset (wipe user data) when moving to a new ROM. It might not always be "absolutely necessary", but if you don't know when the "sometimes" is, than its just better to factory reset. Especially as it may cause random and severe bugs, and also may cause failure to boot.
The exception is moving from one "build" of a particular custom ROM to another (and even then, if its not a major build change). But that's just my own philosophy.
Let me first start off and say that this was entirely my fault for the postion that my phone is in. I did not sOFF because I was lazy, and only have a Mac. I was fine with just being rooted and running MeanBean, that was until I saw SENSE 5 experimental roms coming out for our phone. I tried to flash to one of the SENSE 5 builds using HTC DUMLOCK, and now I can't get past the first boot screen.
info
Unlocked
HBOOT-2.09
RADIO-1.12.11.1210
Open Dsp-v31.1.0.45
eMMC-boot
S-on
3.16 &
Teamwin 2.4.1.0
I can boot to recovery, and when I try to wipe and re-flash MeanBean it goes straight to the BootLoader. I've tried searching the forum to fix my problem, but couldn't find a solution. (long-time-lurker) To my knowledge they haven't come out with a 3.16 RUU.
Basically I felt as though I've flashed a different kernel & boot.image that doesn't coincide with MeanBean and because I'm S-ON, It won't allow me to change that.
I'm very humble and grateful for any help. I didn't want to post, and wanted to find the solution myself, but I failed
Thanks in advance!
If you have a backup, you can restore it from recovery.
Once you're up and running, I highly suggest getting S-off. You can use the newest method, Moonshine. It's Windows friendly.
FinZ28 said:
If you have a backup, you can restore it from recovery.
Once you're up and running, I highly suggest getting S-off. You can use the newest method, Moonshine. It's Windows friendly.
Click to expand...
Click to collapse
Ya that was the first thing I tired, to restore my backup. But when it booted up it goes straight to the main boot screen. Yes I agree as soon as I get my phone working I'll S-off, I've just been putting off using boot camp to dual boot to Windows. I've got virtualbox Windows, but I haven't had much luck pushing commands via usb.
Are you using TWRP recovery, and if so, what version?
Sent from my EVO using xda premium
FinZ28 said:
Are you using TWRP recovery, and if so, what version?
Sent from my EVO using xda premium
Click to expand...
Click to collapse
It's in post 1 you noob j/k Fin
2.4.1.0
---------- Post added at 04:44 PM ---------- Previous post was at 04:39 PM ----------
Hmmmmm maybe it's me every time I show up the OP leaves
bigdaddy619 said:
It's in post 1 you noob j/k Fin
2.4.1.0
---------- Post added at 04:44 PM ---------- Previous post was at 04:39 PM ----------
Hmmmmm maybe it's me every time I show up the OP leaves
Click to expand...
Click to collapse
LOL I've seen this lately but thanks for your help and tutorials!
Sent from my EVO using xda app-developers app
jocarog said:
LOL I've seen this lately but thanks for your help and tutorials!
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
YW I'm always willing to help if I can
If my backup won't flash correctly, I'm guessing I'm screwed at the moment. I've tried restoring my backup multiple times. I've tired several different roms with the same problem.
Maybe try and take it to sprint, and see if they have a 3.16 RUU to Restore to stock? Or send it to HTC?
virtualhypocrisy said:
If my backup won't flash correctly, I'm guessing I'm screwed at the moment. I've tried restoring my backup multiple times. I've tired several different roms with the same problem.
Maybe try and take it to sprint, and see if they have a 3.16 RUU to Restore to stock? Or send it to HTC?
Click to expand...
Click to collapse
I don't think your problem is that serious. What are you wiping in TWRP? On that note, make sure you aren't wiping anything once you flash the ROM.
Sent from my EVO using xda premium
virtualhypocrisy said:
If my backup won't flash correctly, I'm guessing I'm screwed at the moment. I've tried restoring my backup multiple times. I've tired several different roms with the same problem.
Maybe try and take it to sprint, and see if they have a 3.16 RUU to Restore to stock? Or send it to HTC?
Click to expand...
Click to collapse
After you try flashing MeanBean and it returns to the bootloader have you tried flashing it a second time?
Wiping cache/dalvik cache/system/factory reset before flashing the first time of course
Have you tried typing "fastboot erase cache" without the quotes from a cmd window while the phone is booted to bootloader
FinZ28 said:
I don't think your problem is that serious. What are you wiping in TWRP? On that note, make sure you aren't wiping anything once you flash the ROM.
Sent from my EVO using xda premium
Click to expand...
Click to collapse
I usually use superwipe.zip before installing a rom. But since my problem, I'm wiping all 4 options on TWRP, and not after I install the rom, always before.
bigdaddy619 said:
After you try flashing MeanBean and it returns to the bootloader have you tried flashing it a second time?
Wiping cache/dalvik cache/system/factory reset before flashing the first time of course
Have you tried typing "fastboot erase cache" without the quotes from a cmd window while the phone is booted to bootloader
Click to expand...
Click to collapse
Yes I've tried re-flashing MeanBean a second time, so that it tries to install the kernel but no luck. I've flashed all 4 settings before installing any zips.
I'll try the "fastboot erase cache" this weekend, when I have access to a Windows computer.
Thanks again for all your suggestions.