Hello community,
today I've made a terrible mistake. In the past I was using a HTC Desire, I got a lot of experience in flashing and ''playing'' on it.
A few weeks ago I've bought the HTC EVO3D and unlocked it with the HTC unlock method today. Up to this point it all worked very well, so in the next step I've decided to get a shiny new custom rom work on it...
I've choosen this one: http://forum.xda-developers.com/showthread.php?t=1647674
The problem was that I have not installed the 4EXT Recovery system in the right way I think, but at this moment I didn't recognize that...
In the process of flashing the rom, I have flashed the kernel manually as the developer says in post #3 on his thread, before flashing the rom itself...this was very stupid...
I flashed this boot.img with the ''fastboot-method'' (cmd) to my phone, it succesfully worked.
The problem is that now nothing happens on the phone after the first HTC-logo shows up, only a black screen. Going to a nandroid-backup isn't possible because of the ''missing'' recovery system (only black screen appears instead of recovery). When I hit the factory reset option in the bootloader it starts the process but after a while (green loading symbol) it only shows a picture with a phone and a red warning symbol.
Is there anything that can be done to get the phone in a working mode, like flashing another kernel or something over ''fastboot-method''? Or is it totally bricked?
(Sorry for bad language/tenses, I'm from Germany)
FIRST LINK. lol on the other section. lol
http://forum.xda-developers.com/showthread.php?t=1563342
YOU SHOULD have waited until we found the correct way to root instead of using the HTC method. lol. but either way. FOLLOW THE INSTRUCTIONS! DONT' FORGET YOU HAVE TO UNDO THE HTC METHOD BEFORE DOING THE ENTIRE PROCESS! or did they fix that? haha I forget.
---------- Post added at 06:26 PM ---------- Previous post was at 06:24 PM ----------
wait a second!!!!!! SORRY just re-read some of your post! you used the HTC method TODAY!?!?!!?!?!!? lmao! like I said, follow the CORRECT instructions. the HTC method is a joke.
Sent from my PG86100 using xda premium
Go on fastboot mode. Type in fastboot boot recovery.img ( or whatever the name of your recovery image is)
*learned this the hard way*
---------- Post added at 11:49 PM ---------- Previous post was at 11:39 PM ----------
And also do you have S-ON or S-OFF ....... HBOOT 1.5 or 1.4??
Oh just a tip, never do a factory reset within the bootloader after you have rooted. Also download twrp and flash the .img through fastboot. Then flash a gingerbread Rom with probably a stock kernel. (Again the kernel through fastboot)
------
3(d)vo one s
Newts my hero.
kiewee3 is correct and also you need to be rooted before you install 4ext recovery
but don't forget that the developer never said to do it on a phone without first making sure S=off with the HTC method. it is left on. right?? or did I word that wrong? but you get what I mean. so you need to fully root your phone to prevent issues. make it easier on yourself.
Why don't you just flash the stock ROM? Copy PG86IMG.zip on the SD card via card reader, enter bootloader, let it flash and you are fine... It overwrites everything.
Then just fastboot connect the phone, type "fastboot oem writesecureflag 3" and you are back on the beginning.
Related
I need help my EVO 3D is stuck on the second screen that comes up as it boots. It has been unlocked (HTC dev) flashed (4ext) and has a custom rom (Shooter Sense 3.6) on it. I can get it into the bootloader, and into the recovery, but cleverly i forgot to make a stock backup and can't revert from where im at.
Hboot- 1.49.0012
Radio- 10.13.9020.20_M
eMMC-boot.
Thats pretty much all the information i have, other than its a Telstra phone.
you have to manually flash the boot.img using fastboot
---------- Post added at 02:16 PM ---------- Previous post was at 02:15 PM ----------
http://forum.xda-developers.com/showthread.php?t=1752270
EM|NEM said:
the reason its not booting is probably because you didnt flash the boot.img using fastboot. that is required to get roms to boot when you are s-on.
first install the rom from recovery.
then extract the boot.img from the rom zip file(probably in the kernel/shooteru folder) then place it in the folder where you have adb,fastboot and AdbWinApi.dll which you used to unlock.
then open cmd. change directory to the folder containing adb/fastboot.
Connect your phone in bootloader mode and make your it says "fastboot usb"
then type in cmd "fastboot flash boot boot.img"
it should do a process and show that it completed.
then reboot and it should boot up.
all the info you need is here:
http://forum.xda-developers.com/showthread.php?t=1752270
Click to expand...
Click to collapse
EM|NEM said:
you have to manually flash the boot.img using fastboot
---------- Post added at 02:16 PM ---------- Previous post was at 02:15 PM ----------
http://forum.xda-developers.com/showthread.php?t=1752270
Click to expand...
Click to collapse
Just gave it a go still on the boot screen for now. heres to hoping.
AndrewMoulakas said:
Just gave it a go still on the boot screen for now. heres to hoping.
Click to expand...
Click to collapse
No luck.
Maybe try a different rom.
And if all else fails you can always use RUU
http://forum.xda-developers.com/showthread.php?t=1208485
---------- Post added at 02:43 PM ---------- Previous post was at 02:41 PM ----------
go to recovery. do factory reset in 4ext and wipe cache+delvik
then install rom.
then flash boot.img in bootloader mode
Its still not working. stuck on the boot screen still. after manually booting with fast boot.
you could make your life so much easier by doing s-off. the rom you are trying to flash requires a newer firmware(which requires s-off).
I think you can update your firmware using an ICS RUU. or you could take the OTA update if its available
EM|NEM said:
you could make your life so much easier by doing s-off. the rom you are trying to flash requires a newer firmware(which requires s-off).
I think you can update your firmware using an ICS RUU. or you could take the OTA update if its available
Click to expand...
Click to collapse
I have S-OFF and i've tried the RUU, and my carrier does not support the ICS OTA update at the moment.
Im giving it a go again now following your instructions to the T.
If you have s-off then just flash the latest firmware in bootloader
http://d-h.st/Mf1
then install the rom. no need for manual flashing of boot.img
should have stated you were s-off :banghead:
IT WORKED!!!!! thanks man. I would have never figured that out on my own or even stumbled upon that other thread. Thank you so much.
glad i could help
hy evevy body
my phone now got black screen after installed chainfire 3d. using ics, root, hboot 1.50 unlock
now i just can enter fastboot via fastboot via terminal in windows,
i just push vol down+power button and then i push power button again to enter fastboot, my scren still black
when i type fastboot devices it shown my device
what can i do with that
thx 4advice
paijo0708 said:
hy evevy body
my phone now got black screen after installed chainfire 3d. using ics, root, hboot 1.50 unlock
now i just can enter fastboot via fastboot via terminal in windows,
i just push vol down+power button and then i push power button again to enter fastboot, my scren still black
when i type fastboot devices it shown my device
what can i do with that
thx 4advice
Click to expand...
Click to collapse
Can you get into the recovery via fastboot?
DjDom said:
Can you get into the recovery via fastboot?
Click to expand...
Click to collapse
i suposed i can.
the step to enter fasfboot are :
1. press vol down+power
2. wait few seconds and then press vol down
3. press power again
i do that with black screen condition
sorry for my bad english
Flash a new bootloader in Fastboot USB and a recovery and you should be able to tweak your way from there by flashing a new ROM.
MistedEvo said:
Flash a new bootloader in Fastboot USB and a recovery and you should be able to tweak your way from there by flashing a new ROM.
Click to expand...
Click to collapse
is "Flash a new bootloader" change the hboot? i mean i`m using hboot 1.50 and i have to update it?
or just change the boot from an ROM.
thx
Blank screen? Mine got stuck on htc logo a while back. It's not meant to be working on ics. I made a backup before, just in case and restored it. All was fine after. Flashing the same rom over, without cleaning any partitions should work fine too. But in your case i am not sure it will work.
put a recovery.img in your fastboot folder and then put your phone in fastboot mode then type "fastboot flash recovery recovery.img" then try to boot recovery again if it still doesnot work, try "fastboot boot recovery.img" but IMO chainfire should not affect your hboot and recovery. If nothing works you can use RUU.
mnomaanw said:
put a recovery.img in your fastboot folder and then put your phone in fastboot mode then type "fastboot flash recovery recovery.img" then try to boot recovery again if it still doesnot work, try "fastboot boot recovery.img" but IMO chainfire should not affect your hboot and recovery. If nothing works you can use RUU.
Click to expand...
Click to collapse
didn't work man :crying::crying::crying::crying:
my lcd still blank
is chainfire 3d flash my gpu firmware, so my gpu got in wrong 'state' so it wont work?
can i reflash my gpu firmware?
I'm a bit confused. So you said the screen is black even while in hboot?
And you are cdma, right? S-on or s-off? And to get into fastboot usb i think it is more like, power off your phone completely, if you were using sense 3.6 rom i guess it is a good idea to remove the battery for a sec in case fast boot was enabled in settings, then pwr+voldwn, wait a moment, pwr again and now you should be on fastboot.
Then on pc make sure you have installed all the required drivers for your phone and download fastboot. Connect your phone to the pc. Copy a recovery.img on the folder on your pc where fastboot executable is located. Then shift + right click on an empty space in that folder and create a terminal (cmd) there. Run fastboot flash recovery.img. then try to boot into recovery again. So shut down your phone again. Then pwr + voldwn. Again voldwn and now it should boot into recovery. You may also use 'fastboot reboot recovery' from fastboot instead of this i guess. If it doesnt work do fastboot boot recovery.img. If you are s-off you can just flash a ruu if it didn't work, but you will lose root ofcourse. If s-on you need to relock bootloader in fastbbot mode with 'fastboot oem lock' and then flash the ruu. I dont have time to find a ruu for you, so you better google for it yourself. Make sure to choose the appropriate ruu for your phone. To flash the ruu you just open the downloaded ruu.exe file and it will start flashind. It will take time and will tell you when it is done. If you are s-off i am not sure if you need to relock the bootloader but i guess you should not. If you are on a custom hboot(only possible if you are s-off), please no way lock your bootloader it will hardbrick it!
You may send me a pm. And i will do what i can to help you.
---------- Post added at 02:44 AM ---------- Previous post was at 02:11 AM ----------
And if you are not s-off i would reccommend you to go s-off after you have fixed this issue. Wire trick is the easiest way to gain s-off imho. Just go to this page and read the info on how to do this. I got s-off on my second try. It must be timed correctly. If anything goes wrong read the troubleshooting section. http://unlimited.io/juopunutbear.htm
And as always, if you need any help feel free to pm me.
MrJyrks said:
I'm a bit confused. So you said the screen is black even while in hboot?
Click to expand...
Click to collapse
yes, my screen is black while in hboot.
MrJyrks said:
And you are cdma, right? S-on or s-off?
Click to expand...
Click to collapse
yes my evo 3d is CDMA in S-on mode, but unlock
MrJyrks said:
Then on pc make sure you have installed all the required drivers for your phone and download fastboot. Connect your phone to the pc. Copy a recovery.img on the folder on your pc where fastboot executable is located. Then shift + right click on an empty space in that folder and create a terminal (cmd) there. Run fastboot flash recovery.img. then try to boot into recovery again. So shut down your phone again. Then pwr + voldwn. Again voldwn and now it should boot into recovery. You may also use 'fastboot reboot recovery' from fastboot instead of this i guess.
Click to expand...
Click to collapse
i have done that step, I have been success when flashing the recovery. when i turned it off, then turn it on again, my screen still black
when i tried boot from recovery boot,my screen still black too.
MrJyrks said:
If s-on you need to relock bootloader in fastbbot mode with 'fastboot oem lock' and then flash the ruu.
Click to expand...
Click to collapse
i'll try this thing
MrJyrks said:
I dont have time to find a ruu for you, so you better google for it yourself. Make sure to choose the appropriate ruu for your phone.
Click to expand...
Click to collapse
what make the rru different from me and the other? how to make sure is that ruu appropriate for my phone?
thanks for all your advice man, i'll try
paijo0708 said:
my phone now got black screen after installed chainfire 3d. using ics, root, hboot 1.50 unlock
Click to expand...
Click to collapse
Did you see this in the description of Chainfire 3D in the description on the Play Store:
!! For Froyo and Gingerbread ONLY. NOT COMPATIBLE with Honeycomb/Ice Cream Sandwich/Jelly Bean !!
Click to expand...
Click to collapse
Given that "NOT COMPATIBLE" is in caps, I'd suggest contacting the developer via his website or email in the Play Store listing and ask him what happens when it's run on ICS.
ramjet73
The RUU should be different on every carrier model and you must download the ICS RUU. For example, if you have a Sprint branded evo 3d, google for sprint evo 3d ics ruu. Also you should know the cdma version of evo 3d is alternatively named shooter and gsm version shooter u. I think it's relatively easy to find a ruu for your device. Please make sure your phones battery is fully charged before flashing and do not remove the usb cable before the process has completed. The ruu should be with .exe file extension. Just run the ruu and read the onscreen instructions.
---------- Post added at 01:21 PM ---------- Previous post was at 01:14 PM ----------
Oh and btw if you have got the wrong ruu the ruu should not flash. And please, dont ever flash CF3D on anything other than GB. And it is safer to have s off in my opinion but you should not do anything stupid if s off because it's easier to revive a s on device if bricked.
---------- Post added at 01:32 PM ---------- Previous post was at 01:21 PM ----------
Oh and as you are s on dont even bother flashing a new hboot as one has adviced.
---------- Post added at 01:40 PM ---------- Previous post was at 01:32 PM ----------
And if you didnt know a ruu will flash a hboot, rom and firmware. It must fix it. If it does not, there must be a hardware problem.
---------- Post added at 01:50 PM ---------- Previous post was at 01:40 PM ----------
And i dont get it why it didn't work. It works perfectly fine on sense 3.6 roms. At least it worked for me with the experimental driver.
---------- Post added at 01:55 PM ---------- Previous post was at 01:50 PM ----------
And use 4ext touch recovery, it seems to be more stable. To install just download app from play store and select install recovery from the app BUT you must be already rooted to flash the new recovery from the app. So to get s off back just do the htcdev method. fastboot flash recovery. Boot into recovery. Flash the root zip and then dl the app. The full version is a better option imho. It costs a little but its worth it.
Sounds like a hardware issue to me. How can CF3D affect hboot and recovery? It only touches the ROM.
@OP do you see a black light when you turn on the phone or your screen does not even light up.
I have installed CF3D on almost every ROM available for CDMA EVO 3D , just to mess around and it does not affect anything except the 3D graphics in games .They will get better or in worst case no 3D games at all only black screen but 2D HUD menu etc are visible.
And go s-off with juopunutbear. It is super easy with the correct timing. I watched a video to get the correct timing. And as far as i know s off should be required for jellybean roms.
---------- Post added at 02:09 PM ---------- Previous post was at 02:04 PM ----------
You just better flash a ruu. I dont think it is a hw issue if you had the screen functioning just before installing cf3d.
---------- Post added at 02:13 PM ---------- Previous post was at 02:09 PM ----------
If it doesnt work after flashing a ruu there is nothing we could do and you need to send it in for repair.
Nexus 7 (2013) black screen after installing chainfire 3D
paijo0708 said:
hy evevy body
I need help, plss
After install chainfire 3D on my nexus he is turn off,and i turn on but when is turn on,screen is black,and i can't fix.
I'm try wipe reset/factory but don't work,i connect with PC,but i can't see on PC my nexus,
How fix this problem
Plss help me
Thanks
Sry on my bad english
Click to expand...
Click to collapse
For the past 24 hours i have been dealing with my phone.
Trying to s off my phone i rooted and unlocked it via usual methods, finally reaching to j.bear wire trick part of the cmd. however upon reaching the wire trick part my phone would not succesfully complete the wire trick. I would get the still sober.
So in a mad rage i cleared system storage did a factory reset and went in recovery and did a superwipe.
This uninstalled my OS:crying:
Now i am stuck in this limbo between my being unlocked and loading the juopunut arrow screen and when i relock it i just keep getting back to bootloader. I was able to install a stock rom deodexed however after it finally finished installing it went right back to the juopunut black screen, I have a backup boot from when installed stock rom deo. but i wonder if that can do anything. Please help! i have not used android in about 3 years. I was on a windowsphone and i'm still very much used to that style so that is possible for my mistake. I got the Amaze 4g yesterday and i don't want my money wasted.
HELP!
Hmm can you flash an RUU?
---------- Post added at 06:03 PM ---------- Previous post was at 05:59 PM ----------
Basically can you get into boot loader mode. And do you have any way you can put a file on your external SD.
lamortcroix said:
Hmm can you flash an RUU?
---------- Post added at 06:03 PM ---------- Previous post was at 05:59 PM ----------
Basically can you get into boot loader mode. And do you have any way you can put a file on your external SD.
Click to expand...
Click to collapse
it may be possible. i do have access to the boot loader files however the only way i would be able to upload anything onto the SD would be to flash cwm..... i'll try it though
also since i know i left it out. I'm running tmous and the only reason i really did all this was to get rid of bloatware -_-
I am stuck at the black jbear screen with the arrow facing the phone.
You don't need to S-OFF to remove bloatware.
Good luck.
lamortcroix said:
You don't need to S-OFF to remove bloatware.
Good luck.
Click to expand...
Click to collapse
yes i realized that right after everything happened but alas too late.
However i am getting extremely close to figuring a solution. Will update soon enough
sugges
MC_Original said:
yes i realized that right after everything happened but alas too late.
However i am getting extremely close to figuring a solution. Will update soon enough
sugges
Click to expand...
Click to collapse
PROBLEM SOLVED (for the most part)
Thank you all for your help but i did discover that the only way to get myself off the constant switching between the jbear wiretrick screen and the bootloader loop was to use a wire from inside a telephone cord and complete the s off (even though it failed somehow) from there i had to manage my next issue of the constant bootloader which was solved through a matter of relocking my device, finding a original stock recovery file then having the amaze all in one kit flash the proper rom back to my phone.
Here's a tip for the next time you do the wire trick.
Use a metronome (or a website that uses a metronome ) and set it to 34 and use that rhythm and remember to only tap it twice.
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 reboot to go into bootloader. TWRP doesn't load up. I have no OS on it yet because the newest MeanBean wouldn't load correctly with the old twrp i was running. Help please. I'm disabled and live independently and my cell is my only phone. I have a thread open. Since i Didnt have enough posts to post here initially.
http://forum.xda-developers.com/showthread.php?p=39025710#post39025710
Thanks again.
If anyone wants to PM me a number to call, I'll borrow my neighbors landline.
Just load into fastboot and flash twrp then load up a Rom via recovery. Done.
Go onto the twrp page and download the .img file, and reboot your device into bootloader, and select fastboot. Now run the fastboot command and it will push recovery over the wire.
Sent From My HTC Evo 4G LTE, On The Now Network From Sprint!
---------- Post added at 12:21 PM ---------- Previous post was at 12:20 PM ----------
Wrong section btw...
Sent From My HTC Evo 4G LTE, On The Now Network From Sprint!
Well guys I figured out i needed to remove SD card and also remove that twrp file. I'm still getting stuck in bootup with this new rom i wanted to try so back to meanbean i go in hopes that the rom will clear boot on meanbean which is where it all started.
Are you saying that you have a recovery now, but no ROM will boot? Not sure what clear boot means. You mean wipe the boot.IMG (kerne) from previous ROM, or you mean make it all the way to boot up? Sorry, your post is confusing to me.
From my Evo LTE, yup.