Related
I'm a little lost. Let me explain what just happened.
1st 3D was having reboots randomly and BSOD.. so I replaced it.
Picked up new 3D today.
It's Hboot 1.50.000 (oh noez)
I unlock via HTC method
(( Now with HTC's method it's my understanding that you can flash a custom recovery and roms, but you're locked on the Kernel that came with your phone and thus no aosp roms/kernels OR if you're trying to flash a sense rom but the rom has a higher kernel than the one on your phone - you're still up the creek))
After unlocking with HTC's method I promptly went into TWRP, wiped everything without a nand backup because if it screws up i'm using my upgrade lol. I then flashed Eternity 3.0 R39.. to my surprise it worked fine. I didn't test if I could OC.
I then rebooted into recovery through power button and then installed the current miui rom, immediately followed by the Anthrax AOSP kernel.. to my surprise I got no errors of any sort, booted up fast as hell, restored SetCPU and Oc'd to 1.8 just fine.. been going for about 15-20 minutes now just like normal.
I THOUGHT I WASN'T SUPPOSED TO BE ABLE TO DO THIS GUYS
saboture said:
I'm a little lost. Let me explain what just happened.
1st 3D was having reboots randomly and BSOD.. so I replaced it.
Picked up new 3D today.
It's Hboot 1.50.000 (oh noez)
I unlock via HTC method
(( Now with HTC's method it's my understanding that you can flash a custom recovery and roms, but you're locked on the Kernel that came with your phone and thus no aosp roms/kernels OR if you're trying to flash a sense rom but the rom has a higher kernel than the one on your phone - you're still up the creek))
After unlocking with HTC's method I promptly went into TWRP, wiped everything without a nand backup because if it screws up i'm using my upgrade lol. I then flashed Eternity 3.0 R39.. to my surprise it worked fine. I didn't test if I could OC.
I then rebooted into recovery through power button and then installed the current miui rom, immediately followed by the Anthrax AOSP kernel.. to my surprise I got no errors of any sort, booted up fast as hell, restored SetCPU and Oc'd to 1.8 just fine.. been going for about 15-20 minutes now just like normal.
I THOUGHT I WASN'T SUPPOSED TO BE ABLE TO DO THIS GUYS
Click to expand...
Click to collapse
I bet you got a refurb that someone previously rooted. If they used revolutionary then you retain S-off even on hboot 1.50 when the refurb facility repaired the device. Why don't you check if you're S-off?
It was S-On. That was the first thing I checked while walking out of the store. S-On 1.50.000
How strange. Hopefully people will keep coming to the thread and ask the right question. With the right question, the right answer will come to shed some light on what is special about your scenario.
Unfortunately that will not be me, because I have hboot 1.4, thus have less knowledge on the HTC unlock method.
Hopefully this has happened to someone else. I'm not sure why it happened. :O
saboture said:
I'm a little lost. Let me explain what just happened.
1st 3D was having reboots randomly and BSOD.. so I replaced it.
Picked up new 3D today.
It's Hboot 1.50.000 (oh noez)
I unlock via HTC method
(( Now with HTC's method it's my understanding that you can flash a custom recovery and roms, but you're locked on the Kernel that came with your phone and thus no aosp roms/kernels OR if you're trying to flash a sense rom but the rom has a higher kernel than the one on your phone - you're still up the creek))
After unlocking with HTC's method I promptly went into TWRP, wiped everything without a nand backup because if it screws up i'm using my upgrade lol. I then flashed Eternity 3.0 R39.. to my surprise it worked fine. I didn't test if I could OC.
I then rebooted into recovery through power button and then installed the current miui rom, immediately followed by the Anthrax AOSP kernel.. to my surprise I got no errors of any sort, booted up fast as hell, restored SetCPU and Oc'd to 1.8 just fine.. been going for about 15-20 minutes now just like normal.
I THOUGHT I WASN'T SUPPOSED TO BE ABLE TO DO THIS GUYS
Click to expand...
Click to collapse
umm i have hboot 1.50 unlocked htc method and i can flash any rom or kernal i want by just booting into recovery through fastboot its an extra step that takes about 10 seconds with a copy and paste of 2 commands from dos prompt
Yeah, I'm not sure why there's this myth that you can't flash kernels with 1.5, just need to load recovery in fastboot. Only limit I know of for 1.5 is that I can't use boot manager (if I'm wrong, let me know because I would love to use it). Either way, doesn't sound like OP was flashing through fastboot, which is odd.
Sent from my HTC Evo 3D using XDA App
saboture said:
After unlocking with HTC's method I promptly went into TWRP, wiped everything without a nand backup because if it screws up i'm using my upgrade lol. I then flashed Eternity 3.0 R39.. to my surprise it worked fine. I didn't test if I could OC.
I THOUGHT I WASN'T SUPPOSED TO BE ABLE TO DO THIS GUYS
Click to expand...
Click to collapse
Sounds like after unlocking with htc method you never disconnected your phone from PC and directly booted recovery from fastboot when you flashed TWRP .
So there's nothing new, i guess.
Every hboot1.50 user can flash kernels whether it is sense kernel or AOSP......
You can also use Flash image GUI to flash custom kernels from within the running android environment too.
So far JUST using HTC's unlock method I'm able to do the following
Flash custom roms through recovery like normal
Flash custom kernels through recovery like normal
Perform Nandroid backups/restores of EVERYTHING
UNABLE TO FLASH A CUSTOM SPLASH SCREEN
I thought this was going to be horrible going from a 1.40.000 device to 1.50.000 but honestly it's exactly like when I used Revolutionary to unlock my 1.40.000 device. And yes - I did leave my USB cable hooked up from start to finish. Hopefully other people will see this thread.
I tried Flash GUI and I couldn't get it to work for me so I guess I'm grateful. I'll check if I can install a splash screen once I post this and edit with the update.
saboture said:
I'm a little lost. Let me explain what just happened.
1st 3D was having reboots randomly and BSOD.. so I replaced it.
Picked up new 3D today.
It's Hboot 1.50.000 (oh noez)
I unlock via HTC method
(( Now with HTC's method it's my understanding that you can flash a custom recovery and roms, but you're locked on the Kernel that came with your phone and thus no aosp roms/kernels OR if you're trying to flash a sense rom but the rom has a higher kernel than the one on your phone - you're still up the creek))
After unlocking with HTC's method I promptly went into TWRP, wiped everything without a nand backup because if it screws up i'm using my upgrade lol. I then flashed Eternity 3.0 R39.. to my surprise it worked fine. I didn't test if I could OC.
I then rebooted into recovery through power button and then installed the current miui rom, immediately followed by the Anthrax AOSP kernel.. to my surprise I got no errors of any sort, booted up fast as hell, restored SetCPU and Oc'd to 1.8 just fine.. been going for about 15-20 minutes now just like normal.
I THOUGHT I WASN'T SUPPOSED TO BE ABLE TO DO THIS GUYS
Click to expand...
Click to collapse
You can flash kernels through fastboot. But you stated that you booted into recovery using power button, so it doesn't sound like you used fastboot....
You didn't use the flashimage GUI app, did you?
Sounds strange to me. Did you check the kernel In settings after you flashed? Don't think Its possible for stock kernel to support miui, but I suppose its possible.
Either way, you had something happen that shouldn't have. Either got a kernel to flash in a way that it shouldn't have, or got a rom to run on a kernel that shouldn't be compatible.
Another possible thing....I wonder if the 2.08.651.3 update did something that allows for you to flash kernels now. We know it wasn't possible on the .2 software, has anyone tried it with. 3. Doubt it made a difference as it was supposed to be a security update only.
Who knows. Ill give it a shot tomorrow to see if I can flash kernels without fastboot or flashimage GUI.
Sent from my PG86100 using XDA App
If you can flash a splash or radio then you should seek out a dev and let them know. They would probably have you do some tests. Might help achieve s off on 1.50
Sent from my PG86100 using XDA App
thos25 said:
You didn't use the flashimage GUI app, did you?
Click to expand...
Click to collapse
I tried it but when I booted into miui I got stuck at the boot screen. Miui boots in about 30 seconds or so on a fresh install but I was there for over 10 minutes.
Right now my phone is flashing Eternity 3.0 - R39 followed by Anthrax kernel. I'll let you guys know in a sec.
Edit: Well, the kernel flashed successfully but I'm freezing in the middle of the boot screen. Gonna try another kernel
Okay while booting Eternity 3.0 R39 I froze up mid boot screen. I remembered seeing a post about it freezing and I found it here and did what he said to do and it all works fine now. This is after I flashed rom+kernel in recovery then rebooted.
saboture said:
I tried it but when I booted into miui I got stuck at the boot screen. Miui boots in about 30 seconds or so on a fresh install but I was there for over 10 minutes.
Right now my phone is flashing Eternity 3.0 - R39 followed by Anthrax kernel. I'll let you guys know in a sec.
Edit: Well, the kernel flashed successfully but I'm freezing in the middle of the boot screen. Gonna try another kernel
Click to expand...
Click to collapse
Yeah. I have trouble with flashinage GUI as well. Funny thing is my issues with it were with miui as well.
Sent from my PG86100 using XDA App
saboture said:
Okay while booting Eternity 3.0 R39 I froze up mid boot screen. I remembered seeing a post about it freezing and I found it here and did what he said to do and it all works fine now. This is after I flashed rom+kernel in recovery then rebooted.
Click to expand...
Click to collapse
Good stuff. Did you check to see if you can flash radio or splash?
Sent from my PG86100 using XDA App
thos25 said:
Good stuff. Did you check to see if you can flash radio or splash?
Sent from my PG86100 using XDA App
Click to expand...
Click to collapse
I'm unable to flash a splash, and I've never flashed a radio before.
But as of right now I can flash kernels/recoveries/roms from TWRP. I'll try flashing a bootscreen with Rom Toolbox real quick just for extra measure.
Edit: can flash custom boot screens. One thing I cant seem to do though is take screenshots with screenshot it. When it saves it's always corrupted and wont let me transfer the screenshot to anything.
From what I gather, the questions you have answered still haven't shed any light as to whether your phone is behaving in a matter that is the same anyone else in your situation would experience? If it is still in fact behaving different than what we would expect it to I think the suggestion given to you to contact a Dev would be best. You may end up and be able to help the community achieve a more comprehensive solution to the root process.
Sad Panda said:
From what I gather, the questions you have answered still haven't shed any light as to whether your phone is behaving in a matter that is the same anyone else in your situation would experience? If it is still in fact behaving different than what we would expect it to I think the suggestion given to you to contact a Dev would be best. You may end up and be able to help the community achieve a more comprehensive solution to the root process.
Click to expand...
Click to collapse
Yeah, I was thinking the same thing.
Sent from my HTC Evo 3D using XDA App
could it be possible htc updated their unlock process to allow access to the boot.img without using fastboot?
ok. so I finally got around to trying to flash a kernel without using fastboot to see if it would work.
It did not. Like others have reported, it will say that the flash is successful, but when I go into the "about phone" menu, it did not change.
I have CM7 (secretpartymeow) on it now with stock (as in whatever kernel came with the ROM) kernel. Tried flashing infected Anthrax (aosp). No luck.
It is indeed looking more and more like your phone is a bit of an anomoly. I would suggest contacting one of the devs over at TeamWin to let them know what you are able to do.
I was running infectedROM Sense 3.0, and I had successfully set up several other ROMs via boot manager previously. Today I just installed Playground ICS to an SD slot through boot manager and I backed up my phone ROMs boot img and clicked reboot to playground. The phone rebooted and showed the splash screen. After about 10 seconds on the splash screen, it shut off and won't turn back on. No charge light, regular boot and vol down + power both don't work. All I need to do is get to recovery, then I have to flash the update.zip for my phone ROM in the bootmanager folder. Can anyone help me get into recovery or the bootloader?
edit: I installed playground by installing the zip, and I didn't install any other mods/kernels on top of playground. On the other ROMs I have installed in boot manager, I installed them via a nandroid backup.
If you look through the last few pages of the Playground ICS thread, it is an issue and can be fixed, but its not that easy unless you know what you are doing. I hope you have a linux box.
Look at these posts for help.
http://forum.xda-developers.com/showpost.php?p=23963768&postcount=257
http://forum.xda-developers.com/showpost.php?p=23960522&postcount=250
http://forum.xda-developers.com/showpost.php?p=23968691&postcount=274
netwokz said:
If you look through the last few pages of the Playground ICS thread, it is an issue and can be fixed, but its not that easy unless you know what you are doing. I hope you have a linux box.
Look at these posts for help.
http://forum.xda-developers.com/showpost.php?p=23963768&postcount=257
http://forum.xda-developers.com/showpost.php?p=23960522&postcount=250
http://forum.xda-developers.com/showpost.php?p=23968691&postcount=274
Click to expand...
Click to collapse
looks like I've got my work cut out for me. Glad I have a dual boot with Ubuntu...anyway thanks for your help.
no problem. You might want to post anything further in that thread, you will probably get more help over there. But either way let us know if you succeed.
Sent from my Ice Creamed 3D
w0rdOo said:
I was running infectedROM Sense 3.0, and I had successfully set up several other ROMs via boot manager previously. Today I just installed Playground ICS to an SD slot through boot manager and I backed up my phone ROMs boot img and clicked reboot to playground. The phone rebooted and showed the splash screen. After about 10 seconds on the splash screen, it shut off and won't turn back on. No charge light, regular boot and vol down + power both don't work. All I need to do is get to recovery, then I have to flash the update.zip for my phone ROM in the bootmanager folder. Can anyone help me get into recovery or the bootloader?
edit: I installed playground by installing the zip, and I didn't install any other mods/kernels on top of playground. On the other ROMs I have installed in boot manager, I installed them via a nandroid backup.
Click to expand...
Click to collapse
Do you know how many times I tried to brick this thing when I was downgrading? I almost gave up! And you do it by accident? Lucky you
Edit... Sorry bout your luck, hope all goes well.
no luck so far, I opened windows sda13 thru sdk13 and none of them found the device. i guess i'll reboot and try sda13-sdz13 lol.
Just took my phone to a sprint store, after about 30 min the repair guy came back and handed me the phone. He told me he doesn't have the tools necessary to fix it so I need to come back tomorrow, but he said I'm going to have to lose all my data in order to get the phone working again using his method. I hope the emmc_recover works tonight, or tomorrow I'll probably have hboot 1.5 and s-on
Is it possible that emmc_recover won't work because I'm on the engineering hboot?
I just realized I should probably post in the downgrade hboot thread, so I'm doing that now.
EDIT: fixed my phone flawlessly, the only reason it didn't work the first time is I forgot to pull the battery before plugging it in. Thanks again for your guys' help!
Post-trial of ICS Playground
w0rd,
I had the same problem with my EVO after playing around with this as well. For all others that may have this problem here was my solution...
Symptoms:
After trying to re-flash from ICS Playground to another ROM my phone was stuck at the HTC splash screen and would not do anything. I restarted into recovery and was unsuccessful; even tried to recover to my original files and after that it passed the splash screen and then the screen went black.
Resolution:
Finally used fastboot into recovery and flashed another ROM and it worked. Morale of the story use fastboot from your computer to get into recovery and Flash your ROM.
Hope this helps...
____________________
Device: EVO 3D unlocked via HTCdev
TeamWin Recovery v1.1.1
HBOOT 1.5 (ehh)
MilkRunny 3vo CDMA v.1.13
rugbykj said:
w0rd,
I had the same problem with my EVO after playing around with this as well. For all others that may have this problem here was my solution...
Symptoms:
After trying to re-flash from ICS Playground to another ROM my phone was stuck at the HTC splash screen and would not do anything. I restarted into recovery and was unsuccessful; even tried to recover to my original files and after that it passed the splash screen and then the screen went black.
Resolution:
Finally used fastboot into recovery and flashed another ROM and it worked. Morale of the story use fastboot from your computer to get into recovery and Flash your ROM.
Hope this helps...
____________________
Device: EVO 3D unlocked via HTCdev
TeamWin Recovery v1.1.1
HBOOT 1.5 (ehh)
MilkRunny 3vo CDMA v.1.13
Click to expand...
Click to collapse
I appreciate the reply. However, the problem I had was with one specific release of playground which bricked my phone once installed. I couldn't boot into recovery or the bootloader; the screen wouldn't turn on no matter what. Fastboot won't work from this state. The only way to unbrick at that point without going to a sprint store is to use the emmc_recover tool that's part of the hboot 1.5 downgrade process (in case this happens to you or anyone else, you have to follow step 3 ONLY in the downgrade process in order to recover from bricking your phone)
w0rdOo said:
I appreciate the reply. However, the problem I had was with one specific release of playground which bricked my phone once installed. I couldn't boot into recovery or the bootloader; the screen wouldn't turn on no matter what. Fastboot won't work from this state. The only way to unbrick at that point without going to a sprint store is to use the emmc_recover tool that's part of the hboot 1.5 downgrade process (in case this happens to you or anyone else, you have to follow step 3 ONLY in the downgrade process in order to recover from bricking your phone)
Click to expand...
Click to collapse
Just curious. How do you know it was a specific release, and did it happen to anyone else? Do you know the cause of it?
wikdNoob said:
Just curious. How do you know it was a specific release, and did it happen to anyone else? Do you know the cause of it?
Click to expand...
Click to collapse
The links netwokz provided above showed me that it was a specific release. TwistedUmbrella was experimenting (and I downloaded the experimental ROM, not one of the more "stable" releases) to try to get usb mount to pc to work, and something was wrong in the build I downloaded because it wiped the emmc so I couldn't boot to the phone, recovery, or bootloader. Basically, the ROM bricked my phone in the same way that you're supposed to brick your phone when downgrading from hboot 1.5. Luckily, Twistedumbrella is a great dev who helped people who bricked their devices out. In case you're worried about running into the same issue I did, the build that bricked me is no longer online, as he's updated the experimental and regular download links.
I know it was a specific release because I wasn't the only person who reported this problem. I think it was the 1 am experimental build from 03/22. Anyway, I'm now downloading twistedumbrella's latest experimental. Back to the ROM flashing game
With boot manger they say you must be running the same os as your phone rom or you could brick it. If your phone rom is GB I would recommended running GB roms instead of ICS roms
emarlatt said:
With boot manger they say you must be running the same os as your phone rom or you could brick it. If your phone rom is GB I would recommended running GB roms instead of ICS roms
Click to expand...
Click to collapse
I haven't had any sort of issue from running an ICS ROM in boot manager while running a sense 3.0/3.5 ROM as my default OS. This reported brick was caused by one specific release of playground ICS that would have bricked my phone in the exact same way if I just installed it through my recovery instead of through boot manager. Boot manager wasn't at fault here.
This thread was resolved several days ago. Can I close this thread or something? I've never tried to before so idk how to go about doing that...Well in the meantime, I guess I can just hope nobody else decides not to read page one before posting...
I just rooted my new HTC EVO LTE phone recently because I had to get a new one. Any way, after rooting it, I imminently made a nandroid back up. Then I flashed a few different roms and recoverys. However, what I found out is after I flash a new rom, my wifi says error and won't turn on. I'm not sure what the problem is. And yes, I cleared everything out before flashing a new rom. However, what is even more interesting is I can use my recovery that I made after rooting my phone to go back to the stock rom and it has no trouble with the wifi. I'm not sure why I'm getting this error or how to fix it.
I've thought about flashing some new radios, but I've had issues in the past with this phone trying to make it S-Off, so as a result it is currently S-On. I would like it to be S-off, but after having a lot of experience with it, I've learned it is very time consuming to do and it is a pain to get it to work, it almost always bricks my phone and then I have to go unbrick it in Linux.
I'm planning on running through the rooting method again to see if that does anything, but I'm doubtful. I've also tried updating the prl, profile, firmware and HTC software with no luck. Let me know if anyone has any suggestions. Thanks.
NoClemency said:
I just rooted my new HTC EVO LTE phone recently because I had to get a new one. Any way, after rooting it, I imminently made a nandroid back up. Then I flashed a few different roms and recoverys. However, what I found out is after I flash a new rom, my wifi says error and won't turn on. I'm not sure what the problem is. And yes, I cleared everything out before flashing a new rom. However, what is even more interesting is I can use my recovery that I made after rooting my phone to go back to the stock rom and it has no trouble with the wifi. I'm not sure why I'm getting this error or how to fix it.
I've thought about flashing some new radios, but I've had issues in the past with this phone trying to make it S-Off, so as a result it is currently S-On. I would like it to be S-off, but after having a lot of experience with it, I've learned it is very time consuming to do and it is a pain to get it to work, it almost always bricks my phone and then I have to go unbrick it in Linux.
I'm planning on running through the rooting method again to see if that does anything, but I'm doubtful. I've also tried updating the prl, profile, firmware and HTC software with no luck. Let me know if anyone has any suggestions. Thanks.
Click to expand...
Click to collapse
S-OFF is really the way to go if it's still an option for you it's the only way to get the new firmware without relocking and taking the OTA then unlocking and rooting again read post 2 in the lazypanda thread found here http://forum.xda-developers.com/showthread.php?t=1737123 just go down the list and verify everything works before running lazypanda there are plenty of members that subscribe to that thread so there is plenty of help availiable
Also, rerooting won't do anything. You're already rooted? Think the problem is in the rom u installed. Possibly a bad download. Try downloading from a good connection and install it again. If it is close to stock like flex's stock w goodies just clear cache and dalvik in recovery.
And what do u mean u tried a few recoveries? Cwm doesnt work well with the evo LTE. Try twrp 2.2 and leave it alone until its updated again.
What is your hboot? What rom did you try flashing?
Sent from my lair.
Im also getting this issue and i know its not anything to do with rooting and all that since ive been rooted since i picked this up from best buy on preorder release day and ive been flashing and running the same rom and mods forever now also i was using wifi yesterday soooo yea lol
Recognized Hooker Killer
First, I don't believe I can make my phone S-off, because it has software version 2.13.651.1 710Rd on it and even though I do have a nandroid back on 1.13 hboot, for the default rom from a long time ago with my old HTC EVO LTE, I can't flash back a hboot to 1.13 so I believe I'm stuck S-On for now. Let me know if I'm wrong.
I've attempted several different roms including fresh rom 5.1.1, viper4G_1.0.0, and a jelly bean rom (cm-cfX-20120904-OFFICIAL-jewel all with the same problem. As for recoverys, I should have said I've tried restoring back to several different nandroid backups that I created in the past that were working just find with my old HTC EVO LTE.
Right now my phone is unlocked and rooted. I am running H Boot-1.19.000, I am S-On, and Radio-1.12.11.0809.
I know this problem has something to do with flashing new roms, because when I do a nandroid back up to the default rom, I don't have this problem, and the wifi is working great, I only have this problem if I try to flash any custom rom or use a nandroid backup that I made with my old HTC EVO LTE.
Again, this is not my first time around the track with an HTC EVO LTE, this just happens to be a new phone that I recently got from Sprint when they were thinking my dropped calls were caused by my phone when in fact they figured out they had a tower down. Since then, the tower is back up, so that is why I just rooted this new phone they gave me.
Let me know if you have any suggestions or if you need anymore information.
It's been while now, and I haven't gotten a real response back yet, and I was wondering if anyone knows anything that will help me out? Thanks.
Edit: Found out that I simply needed to flash the boot.img manually of what ever custom rom that I want to switch to in order to get around being S-On.
Please Help
NoClemency said:
It's been while now, and I haven't gotten a real response back yet, and I was wondering if anyone knows anything that will help me out? Thanks.
Edit: Found out that I simply needed to flash the boot.img manually of what ever custom rom that I want to switch to in order to get around being S-On.
Click to expand...
Click to collapse
Hey im having the same exact issue I however went back to my stock backup from right after I rooted. The issue I had was I flashed a CMX nightly. I had been running them fine and suddenly everything went haywire i was bootlooping but only after about 30 seconds after the rom would load up. I'd have just under a minute to fish around and the it would reboot again. it was in this short window that I saw the wifi error and that it would not connect to the sprint network at all for voice or data. Im S-On Hboot 1.15 Evo LTE. I used Flash GUI to go from Stock sense to CMX as im sure youve figured out you have to do. Since i had backups of previous CMX nightlies I tried to just restore But none of my nandroids would fix the looping issue I managed to flash the boot img from the CMX rom i was previously on through adb/fastboot and it took but still my device kept looping. Finally i found this http://forum.xda-developers.com/showthread.php?t=1917106 but I didn't have any Sense Based Roms only my Stock Nandroid back up. So i used the Boot Image Flasher Tool, it took, then Instead of rebooting the system I went straight to my custom recovery and restored my Stock Sense BackUp since the tool flashes the stock sense kernel. To my relief the phone booted right up no problem connected to the network and all but to my dissmay the wifi is STILL broken somehow it says error and will not switch on. Everything else seems to be working fine though. This is crucial there is no way I can go without wifi on my phone. I don't want to ruin anything further or permanitely but i do plan to move forward. My plan is to download a sense rom (MeanRom) which im doing now but it's taking forever on 3G. Wipe everything (using TWRP 2.2) Data Dav rom and use super wipe, and try to install MeanRom. If anyone has any other suggestions Im all ears. Also im alittle confused on the Hboot kernel limitations I know I have to use Flash GUI if Im going from a sense Rom to Aosp and vise versa but do I have to use it when say Going to a nandroid backup of a sense rom while currently on a Aosp rom because I couldnt find a boot.img file in my backup file when i used the tool to extract it. I hate S-On HTC really screwed us with this. And I hate my original evo which had S-Off for dying on me on the 15th day and me having to get this replacement with 1.15 im sorry guys I love this phone but it has become a nightmare and the Evo 3D was no walk in the park either. I apprectiate any comment from anyone this is the first time in almost 8 years of hacking I've been truely worried I may not be able to fix something.
Try this....had the same problem during one of my flashing sessions from rom to rom...this fixed it for me.
You also might want to try a different rom with its corresponding boot img. I'm currently running Venom rom with its boot img file and its working great. Right now, it sounds like your kernel is what is giving you problems like mine, so flashing the correct boot img should fix it.
vel7wil said:
Try this....had the same problem during one of my flashing sessions from rom to rom...this fixed it for me.
Click to expand...
Click to collapse
Thank you I'll be sure to try this out quick update, in TWRP recovery I had (force MD5 check on all zips?) checked now I don't remember checking it or if it came checked by default but as soon as I unchecked it I was able to run superwipe and flash MeanRom which both failed multiple times when it was checked on. Not sure if this was the cause of my problem but I agree I think I got a bad kernel in the CMX nightly. Either that or the Flash GUI app didnt exract the boot image properly. Either way I haven't been brave enough to try another AOSP rom man I hate having S-On my first Evo was perfect then I get stuck with this locked down replacement. One question though is that boot image for a stock/sense rom just wanna be sure.
vel7wil's advice worked for me I was having the same issue. Download the zip he recommends. Use flash image gui to flash the kernel and clear dalvik and cache. I just did a standard reboot after that and it said "android updating... apps x of xx" then everything was back to working.
So today, i went to load up a book in kindle and it crashed a couple times in a row. I figured no biggy, and rebooted the phone (which I can't remember the last time I did, weeks ago).
Upon reboot, for some reason, I'm stuck in a boot loop. I get the white screen with the HTC logo for about 15-30 seconds, it shuts down, repeat. I figured no biggy, everything is stock, I don't care about anything on it, I'll just use the RUU to fix it.
That is where my problem begins. Unforunately, I am updated to 2.95, and the last release RUU is 2.89, so it won't let me install. I can get into hboot, I can use fastboot, so I used fastboot to erase the cache. Anything I select (factory reset, recovery, etc) in hboot just sends me back into the reboot loop. Manually flashing errors out because of the mainver discrepancy. I can't use the low version fix because I'm not rooted, so sure, let's try that... I started the process and unlocked successfully. Now the problem is, any recovery I've installed (4ext from the root thread, CWM5.8 from the boot loop thread) installs fine, but whenever I reboot recovery, again, boot loop. It doesn't matter whether the reboot comes from a fastboot command or selecting recovery reboot from inside hboot.
So, desperate (and somewhat ignorant), I booted up into Linux and tried the unbrick post, and of course, the device never shows up with the battery out, cause it ain't bricked. I was hoping somehow that I could use it to replace hboot, figuring that might be corrupt or something crazy like that (grasping at straws really).
What I really need is a 2.95 RUU, but that hasn't been released, and I figured if that didn't work, something is probably fried hardware wise.
I restored a stock signed recovery, so more or less, right now I'm back exactly where I'm started (other then the fact that my phone is now unlocked) and just not sure where to go from here. Any advice would be helpful. Thanks!
EDIT: I'm a moron, and I forgot to specify, but the phone is sprint. I also don't have any service on it (mainly used as an mp3 player) so I don't have any recourse through them.
I'm almost considering bricking the thing to change the hboot (I haven't done my homework on it yet) any thoughts there? Or is it not something I can do because of my problem?
Sounds like you didn't flash a ROM after getting into recovery.
You need to make sure you're unlocked, and flash a recovery...4ext recovery is highly recommended as it has a setting just to help s on users.
To start and get you up and going, i suggest downloading butterz sense ROM and placing it on your SD card.
Then you need to wipe everything except your SD card
Now flash a new rom, like butterz sense.
Reboot and you should be good
If not you may need to flash boot.IMG in fast boot.
to run an old ruu, you will need to get s off and for that you need a booting ROM.
Good luck!
Sent from my Evo 3D CDMA using xda app-developers app
hossman said:
Sounds like you didn't flash a ROM after getting into recovery.
You need to make sure you're unlocked, and flash a recovery...4ext recovery is highly recommended as it has a setting just to help s on users.
To start and get you up and going, i suggest downloading butterz sense ROM and placing it on your SD card.
Then you need to wipe everything except your SD card
Now flash a new rom, like butterz sense.
Reboot and you should be good
If not you may need to flash boot.IMG in fast boot.
to run an old ruu, you will need to get s off and for that you need a booting ROM.
Good luck!
Sent from my Evo 3D CDMA using xda app-developers app
Click to expand...
Click to collapse
Well, the problem is that I can't get into a recovery after I install it, I'm still caught in the boot loop... but I will try flashing the boot img. Thanks!
If you would like a quicker response/fix check your pm....i can try to help
Sent from my Evo 3D CDMA using xda app-developers app
Well, I did reflash boot.img with no success. I went to relock the phone and was just gonna throw it on the shelf for a couple weeks (as I do have another one), and when I did that using fastboot, it sent the command over and the phone received it, but it gave me a failure message. So now, it doesn't turn on, when I hook it up to the charger, I get the red charging light for about 10 seconds, and very occasionally when I remove the battery and put it back in the HTC logo appears for about 3-5 seconds before the phone cuts off again.
I'm starting to think there was some hardware issue. Since it had a screwy digitizer anyways (and I chose to get another evo for 65 rather then paying 30-35 for the ldc/dig combo), I'm just going to keep it around for parts and maybe play with it another time.
Your offer of help is greatly appreciated however, thank you.
EDIT: It doesn't seem to be truly bricked, or it isn't a recoverable brick... not really seeing the dim red light and the unbrick script doesn't detect it... the phone isn't in emmc mode... but I'm not hugely concerned with it now like I said.
LOL I'm a moron... my battery went dead during the whole recovery thing. Slapped another battery in and I am back to the original problem. Ignore my last post, basically.
At this point, I think that I might be possible that I can't get into recovery because, to the best of my knowledge, the "fast boot" option is ticked in the settings. Unfortunately, I can't get into the phone to change it, so even more chicken/egg stuff. Bleh. I'm still chugging along, any input appreciated. Maybe I can call HTC or Sprint and beg for an RUU?
thatdumbguy said:
LOL I'm a moron... my battery went dead during the whole recovery thing. Slapped another battery in and I am back to the original problem. Ignore my last post, basically.
At this point, I think that I might be possible that I can't get into recovery because, to the best of my knowledge, the "fast boot" option is ticked in the settings. Unfortunately, I can't get into the phone to change it, so even more chicken/egg stuff. Bleh. I'm still chugging along, any input appreciated. Maybe I can call HTC or Sprint and beg for an RUU?
Click to expand...
Click to collapse
Good luck!
So pull the battery, and put it back in.
Hold volume up and then press power.
Does that bring you to boot loader?
Does it say unlocked?
Sent from my Evo 3D CDMA using xda app-developers app
Hello everyone.
I own an HTC EVO V 4G, which I have come to understand is practically identical to the 3D.
I went ahead and did the simple(ish) bootloader unlock process through HTC Dev, and had my phone rooted for at least a year now, tried a few S-ON capable roms, the usual mild rooting stuff, etc etc....
Much more recently, I decided that some of these S-OFF roms make my Unsensible rom look pretty old, and tried out the whole Wire Trick method through unlimited IO.
After a solid 3 hours of staring at my laptop screen....
I rebooted into the bootloader with that glorious S-OFF overtop.
As you might understand... I was very eager to install one of those amazing roms, and downloaded and tried installing the PACman rom for the EVO 3D, admittedly (and regrettably!!) rushing a bit :/
So, after flashing and rebooting, I was stuck in a bootloop with PACman's boot screen. I tried rebooting back into recovery through bootloader (pull out battery, volume down + power, reboot into 4ext recovery) and wiping everything except SD-card, re-installing the ROM, with no success.
At that point I was frustrated enough, to the point where I ended up trying anything I thought might have the slightest chance of giving me my long-awaited rom.
I don't remember what I did exactly, but I flashed a few more files, actually modified the updater-script in the ROM zip.... :/
And now I'm stuck at that White n' Green HTC boot logo, it does not reboot, just stays on constantly, laughing at my hours of fruitless labor.
I can boot into the bootloader whenever with a battery pull, go into 4ext with no troubles.
I have a backup of stock rom, but after whatever I did... Everything I have tried gives me the same results.
I've spent literally the past 9 hours trying to fix this thing, stayed up all night because I need it for the day, and the next day, and the next day...
I tried using the RUU, but I have taken both OTA updates, and even when I finally did get it to start up and run, it denies me almost instantly...
Some device specifics:
I am using linux (Ubuntu).
I own an HTC EVO V 4G (shooter)
I used to run 4.0.4 stock ROM.
Switched to Unsensible (with no issues before S-OFF)
Using 4ext recovery.
Currently on JuopunutBear HBOOT-1.57.5757.
Radio is 1.09.00.0108.
Last ROM I tried flashing before giving up in fear of throwing my phone was PACman.
A few weird things... That scare me a bit...
I can put anything on my SD-card from Ubuntu fine through 4ext's USB function, but everything I do doesn't "stick"...
As in... I put a PG861IMG on the root, see it stay on the root in Ubuntu's file manager, but then boot into bootloader and it doesn't register that there is one.
This is just one example, any other files I transfer over don't take either.
I've been using another phone (I think it's an ancient EVO 4G (Not an EVO V 4G))
I us that one to hold the SD card, and things transfer fine on that one, so I don't think it's the SD card.
If anyone can give me a miracle reply that will save my whole life, you have no idea how appreciative I would be.
Thank you in advance to any replies and/or advice and/or suggestions, etc...
I'm not 100% sure where to put this explanation/plea for help, so... I put it here for one.
I apologise if there's somewhere It'd fit better.