Related
I had my wife's EVO 3D working fine on VipeRom2.1 I think and when i tried to update it to 2.5 it went into a reboot loop. I cleared everything by formatting the system and clearing the cache and data and nothing. I tried a different rom, MeanRom and same thing. Right before it seems like it is going to get me to the unlock screen, reboot. I can get into the bootloader and the recovery just fine but no matter what i install, reboot, reboot, reboot.
Evo 3D
twrp 1.03
Recovery 2e
HBOOT 1.5
Any assistance would be greatly appreciated.
jschauf said:
I had my wife's EVO 3D working fine on VipeRom2.1 I think and when i tried to update it to 2.5 it went into a reboot loop. I cleared everything by formatting the system and clearing the cache and data and nothing. I tried a different rom, MeanRom and same thing. Right before it seems like it is going to get me to the unlock screen, reboot. I can get into the bootloader and the recovery just fine but no matter what i install, reboot, reboot, reboot.
Evo 3D
twrp 1.03
Recovery 2e
HBOOT 1.5
Any assistance would be greatly appreciated.
Click to expand...
Click to collapse
What software is your phone on ? The 2.08 or 2.17?
jschauf said:
I had my wife's EVO 3D working fine on VipeRom2.1 I think and when i tried to update it to 2.5 it went into a reboot loop. I cleared everything by formatting the system and clearing the cache and data and nothing. I tried a different rom, MeanRom and same thing. Right before it seems like it is going to get me to the unlock screen, reboot. I can get into the bootloader and the recovery just fine but no matter what i install, reboot, reboot, reboot.
Evo 3D
twrp 1.03
Recovery 2e
HBOOT 1.5
Any assistance would be greatly appreciated.
Click to expand...
Click to collapse
Did you change/update your radios at all?
I am not sure of the software version. I tried going back to unrooted stock with RUU_Shooter_U_HTC_ARA_1.24.415.2_Radio_10.55.9020.00_10.13.9020.29_M_release_208706_signed and it gave me a version error.
I am running radio 0.97.10.0808 according to the relocked screen that I am getting while trying to restore to unlocked sprint stock.
And now I see the difference in radio and the version in the restore file.
Thanks for the assistance, my Epic Touch 4g has been so simple to tinker with, this thing is a pain in the rear.
The RUU you installed was for the GSM version of the phone, re-run the CDMA version. The GSM version is called Shooter_U whereas the sprint version is just called Shooter.
I'm guessing this would be a good place to start?
http://www.scottsroms.com/downloads.php?do=cat&id=4
I will try this one when I get home today. Hopefully I can get it back stock and then start over and get a functional custom ROM working.
The wife was not to happy I blew up her phone yesterday trying to update it, I am guessing she is not going to let me "fix" it again.
Yupp, install one of them, not sure which one will allow you to do the HTC unlock though.
I think I figured out what I did wrong in the first place. Someone please correct me if I am wrong. I forgot that 1.5 S-ON can't just install the ROM from the standard recovery method like I can with my Epic Touch 4G. I think I need follow the "How to Flash Any ROM or Kernel You Want" instructions from http://forum.xda-developers.com/showthread.php?t=1239821. I just booted to recovery and tried to install the ROM. Does this sound about right?
jschauf said:
I think I figured out what I did wrong in the first place. Someone please correct me if I am wrong. I forgot that 1.5 S-ON can't just install the ROM from the standard recovery method like I can with my Epic Touch 4G. I think I need follow the "How to Flash Any ROM or Kernel You Want" instructions from http://forum.xda-developers.com/showthread.php?t=1239821. I just booted to recovery and tried to install the ROM. Does this sound about right?
Click to expand...
Click to collapse
I didn't look at the link you posted. But with hboot 1.5 you can not write to the boot partition from recovery. In order to do this you need to extract the boot img from the ROM your gonna flash and fastboot flash boot boot.img then fastboot boot recovery.img will take you to recovery and flash ROM from there
Sent from my PG86100 using XDA App
mteezey said:
I didn't look at the link you posted. But with hboot 1.5 you can not write to the boot partition from recovery. In order to do this you need to extract the boot img from the ROM your gonna flash and fastboot flash boot boot.img then fastboot boot recovery.img will take you to recovery and flash ROM from there
Sent from my PG86100 using XDA App
Click to expand...
Click to collapse
You actually dont need to do both. If you just do a fastboot boot recovery.img it will give you complete access, including flashing the kernal. So after you type that command, it will load a the custom recovery and when you flash the rom, it will flash the kernel included with the rom as well. FYI you need to do a fastboot boot recovery.img each time you want to flash a kernel. If you arent changing kernals then you can just go into recovery as you normally would and flash a rom. If you want to flash a kernal without hooking up to a computer, then read into Flash Image GUI.
JayDaKissEP said:
You actually dont need to do both. If you just do a fastboot boot recovery.img it will give you complete access, including flashing the kernal. So after you type that command, it will load a the custom recovery and when you flash the rom, it will flash the kernel included with the rom as well. FYI you need to do a fastboot boot recovery.img each time you want to flash a kernel. If you arent changing kernals then you can just go into recovery as you normally would and flash a rom. If you want to flash a kernal without hooking up to a computer, then read into Flash Image GUI.
Click to expand...
Click to collapse
This is what I thought, The first one I tried was the newest version of ViperRom. I first tried to just flash over top of the existing rom with the hope I would not have to reset everything and make her start over with how she had it setup, I guess the newest version had a newer kernel. Hopefully I am able to get it back to a functional state this afternoon.
jschauf said:
This is what I thought, The first one I tried was the newest version of ViperRom. I first tried to just flash over top of the existing rom with the hope I would not have to reset everything and make her start over with how she had it setup, I guess the newest version had a newer kernel. Hopefully I am able to get it back to a functional state this afternoon.
Click to expand...
Click to collapse
I believe that does have the anthrax kernel havent downloadedthe new version. However i know some people have been having problems with roms that are based off the new OTA if their phones still have the old firmware. Definatly flash teh kernel/boot via fastboot recovery that should take care of the problem.
Correction not anthrax.
I got everything back working yesterday, I guess doing it correct the first time will save me some headache. I just need to remeber to start recovery from windows instead of from the bootloader screen. Thanks for the assistance.
Hey im new to the fourms but i have a HTC evo 3d on the Sprint network. I am unlocked S-On hboot 1.58 with MeanRom ( the latest) i am suffering from a boot loop. The screen boots i see the ring and then black screen back to HTC and restarts process. I am in way to over my head. Can anyone tell me if i can put a stock rom back on and it will fix boot loop or i heard about relock but don't know how to do it. Ive rooted other devices and jail broken devices but never had a problem like this. Help is much appreciated. Thanks
edit: I used a video on youtube but cant post the link :/
ClockWorkMod Recovery was used in it so i think i have it still.
I have tried the factory reset from the boot menu (power + vol down)
Tanker990 said:
Hey im new to the fourms but i have a HTC evo 3d on the Sprint network. I am unlocked S-On hboot 1.58 with MeanRom ( the latest) i am suffering from a boot loop. The screen boots i see the ring and then black screen back to HTC and restarts process. I am in way to over my head. Can anyone tell me if i can put a stock rom back on and it will fix boot loop or i heard about relock but don't know how to do it. Ive rooted other devices and jail broken devices but never had a problem like this. Help is much appreciated. Thanks
edit: I used a video on youtube but cant post the link :/
ClockWorkMod Recovery was used in it so i think i have it still.
I have tried the factory reset from the boot menu (power + vol down)
Click to expand...
Click to collapse
Don't panic tanker, lol I can help you out with this. Here is the reasons behind your boot loop
Your recovery,
Your hboot
Your kernel
Let me elaborate. Cwm has been known to cause lots of problem with evo3d flashing latest twrp or 4ext recovery is recommended. Highly for 4ext. Now before I explain about hboot and kernel, currently you are a s-on user. What that means is that you only have access to certain partitions in the nand memory. System, data, and recovery. That leaves radios and boot partition( that's where your kernel sits) inaccessible through normal recovery means. Anytime you flash a ROM inside of recovery, you phone can't flash the kernel that came with it. So in actuality, your still on stock kernel with mean ROM.
Now for the solution. Your in a endless boot loop with your phone so you will have to download 4ext recovery for your phone and place the recovery image in your fastboot directory. Hook your phone up to the computer and run the command fastboot flash recovery "whatever the name of recovery"img . Boot into recovery and navigate to tools directory. Scroll down and turn on smart flash. This feature will allow you to flash kernels within recovery for s-on users. Wioe everything and flash your ROM again.
Now as for your kernel. Hboot 1.58 is only compatible with ICS stock kernels. That's the main point of your problem. What you will need to do is navigate to the meanrom folder and select the 2.89 kernel and flash it. Your phone should be able to boot up properly after that.
If that doesn't work, you could also try the first step of Ramjet's thread. That will get you back to stock and hopefully not bootlooping. Then if you continue the steps, you'll be s-off which makes flashing easier. See: http://forum.xda-developers.com/showthread.php?t=1889438
Jsparta26 said:
Now for the solution. Your in a endless boot loop with your phone so you will have to download 4ext recovery for your phone and place the recovery image in your fastboot directory. Hook your phone up to the computer and run the command fastboot flash recovery "whatever the name of recovery"img . Boot into recovery and navigate to tools directory. Scroll down and turn on smart flash. This feature will allow you to flash kernels within recovery for s-on users. Wioe everything and flash your ROM again.
Now as for your kernel. Hboot 1.58 is only compatible with ICS stock kernels. That's the main point of your problem. What you will need to do is navigate to the meanrom folder and select the 2.89 kernel and flash it. Your phone should be able to boot up properly after that.
Click to expand...
Click to collapse
okay so i have downloaded 4extrecoveryupdater.apk
Now i would open up CMD and what do i type in for "whatever the name of revoery".img or is that just someting i make up?
sorry im a really noob
Tanker990 said:
okay so i have downloaded 4extrecoveryupdater.apk
Now i would open up CMD and what do i type in for "whatever the name of revoery".img or is that just someting i make up?
sorry im a really noob
Click to expand...
Click to collapse
Funny. No you cannot make up file names, or commands...
First of all you need fastboot application. Save it to c:/fastboot folder.
1. Open CMD, type cd fastboot to enter fastboot folder
2. Type : fastboot flash recovery recovery.img (where recovery.img is the name of your recovery choice weather it is TWRP, 3eXT, or CWM.
I am currently using 4eXT, which I switched to from TWRP
And that's it after its done you should have a flashed recovery on your EVO 3D
Maybe I should add that the "recovery.img" file HAS to be inside c:/fastboot folder.
Good luck. If that doesn't fix it, or if you need any recovery images that worked on my phone, POST
peteypub said:
Funny. No you cannot make up file names, or commands...
First of all you need fastboot application. Save it to c:/fastboot folder.
1. Open CMD, type cd fastboot to enter fastboot folder
2. Type : fastboot flash recovery recovery.img (where recovery.img is the name of your recovery choice weather it is TWRP, 3eXT, or CWM.
I am currently using 4eXT, which I switched to from TWRP
And that's it after its done you should have a flashed recovery on your EVO 3D
Maybe I should add that the "recovery.img" file HAS to be inside c:/fastboot folder.
Good luck. If that doesn't fix it, or if you need any recovery images that worked on my phone, POST
Click to expand...
Click to collapse
petey I am having the same issue as him, 1.58 hboot running ext4 recovery with smart flash on and i cant get out of a boot loop. i have tried using an ruu to return to stock (ruu fails/becomes non responsive). as well as flashing roms using ext4 and then flashing the boot image via fastboot.
if you could help me as well or send me any recovery files you have i would appreciate it
Sure ill send you the images I'm using. I'm at work now, so ill shoot you an email when I get back...
Sent from my PG86100 using Tapatalk 2
pm sent with email address
Youre in a boot loop because you need to downgrade your hboot see link below
Don't forget to hit the thank button!
http://forum.xda-developers.com/showthread.php?t=1906172
sent from my 1920 overclocked note 2 running jedi xp11
---------- Post added at 02:06 AM ---------- Previous post was at 02:05 AM ----------
Btw I use TWRP not 4ext. And forget the ruu.
Just downgrade and it will work
sent from my 1920 overclocked note 2 running jedi xp11
restore rom
When you flashed rom did u make back up cause you could always restore old rom. And you could try flashing the right kernel but most of the time it cause you have to flash boot image that worked for me in trying flash cm 10.1 and I keep get bootloops my self try figure this one out. Same hboot 1.58 2.89 base
harry1471 said:
When you flashed rom did u make back up cause you could always restore old rom. And you could try flashing the right kernel but most of the time it cause you have to flash boot image that worked for me in trying flash cm 10.1 and I keep get bootloops my self try figure this one out. Same hboot 1.58 2.89 base
Click to expand...
Click to collapse
Are you saying youre still getting boot loops and you havent figured this out yet or you did figure it out?
If you havent figured it out I can assist as ive got it 100% working
sent from my 1920 overclocked note 2 running jedi xp11
Same deal
markbencze said:
Are you saying youre still getting boot loops and you havent figured this out yet or you did figure it out?
If you havent figured it out I can assist as ive got it 100% working
sent from my 1920 overclocked note 2 running jedi xp11
Click to expand...
Click to collapse
I'm having the same problem:
Sprint EVO 3D
Unlocked
S-On
Hboot 1.58
eMMC-boot
Won't boot any rom past the OS lock screen. Tried relocking and RUU update, Tried booting recovery from fastboot.
Any help?
Thanks!
jy04 said:
I'm having the same problem:
Sprint EVO 3D
Unlocked
S-On
Hboot 1.58
eMMC-boot
Won't boot any rom past the OS lock screen. Tried relocking and RUU update, Tried booting recovery from fastboot.
Any help?
Thanks!
Click to expand...
Click to collapse
Give me a bit mire info on this. I can help for sure. The evo3d is a pita but we can get it. So basically if I understand, you're stock rooted but have s-on and im assuming all roms are bootlooping?
sent from my Jedi powered Note ll
respect, teach & coach, have fun and say thanks!
the Jedi way
markbencze said:
Give me a bit mire info on this. I can help for sure. The evo3d is a pita but we can get it. So basically if I understand, you're stock rooted but have s-on and im assuming all roms are bootlooping?
sent from my Jedi powered Note ll
respect, teach & coach, have fun and say thanks!
the Jedi way
Click to expand...
Click to collapse
Yes, that's were I am at this point. Right now I've got MeanRom booting to the homescreen seems like it's going to work, but the time is wrong and there's no service, before it can completely boot, bam, shuts down and reboots.
It does the same for the stock Sprint ROM.
Unfortunately I didn't make a backup of the phone when I gor it so I'm using a downloaded one.
I had Meanrom running on another 3D not too long ago, but don't remember it being this troublesome. What did I miss?
jy04 said:
Yes, that's were I am at this point. Right now I've got MeanRom booting to the homescreen seems like it's going to work, but the time is wrong and there's no service, before it can completely boot, bam, shuts down and reboots.
It does the same for the stock Sprint ROM.
Unfortunately I didn't make a backup of the phone when I gor it so I'm using a downloaded one.
I had Meanrom running on another 3D not too long ago, but don't remember it being this troublesome. What did I miss?
Click to expand...
Click to collapse
Ok well the first thing you need to do is downgrade your hboot to v 1.49000. I posted a link on the first page. If you were stock you coukd get s-off via the wire trick
But since you're s-on you need to flash the boot.img in fastboot and then flash the rom or vise versa. I cant remember which one needs to be done first as its been a while since I've used my evo3d. Basically anything thats ics and above cant be flashed unless you downgrade your hboot. Htc sent a hidden hboot ota to you at some point without your knowledge to prevent you from flashing. So downgrading your hboot is your #1 priority and you need to get back to stock to get s-off too
sent from my Jedi powered Note ll
respect, teach & coach, have fun and say thanks!
the Jedi way
Using the wrong ROM!! Got it to boot using MeanRom ICS. Thanks!
Can I get S-OFF with MeanRom flashed? Or do I need to flash a rooted stock ROM?
jy04 said:
Can I get S-OFF with MeanRom flashed? Or do I need to flash a rooted stock ROM?
Click to expand...
Click to collapse
You can try but the instructions say stock. You tube it. Ive done it. It works. Just be patient with the wire trick
sent from my Jedi powered Note ll
respect, teach & coach, have fun and say thanks!
the Jedi way
Oh how i loathe this POS phone
i have this as my work support phone. It wouldn't reliably stay powered up, any time I did turn it on it took 20+ minutes to acquire data/cell/3g signal. turning on maps crashed the phone. so i figured i'd install a new rom
I have lots of experience with sony ericsson, nexus 4, nexus 7 2012, 2013, acer 10.1 tab. i've done all this stuff before, but i cannot get cyanogen 10 or 11 to install properly, and now my phone sits with a spinning logo doing nothing
i:
unlocked the bootloader as per instructions at htc dev
setup ADB on the phone
first jsut copied the c11.zip to the sd card and tried to install that, same issue on with the HTC logo
used hansoon's kit to sideload c10. claims to have installd, now just spins the logo.
any help would be great.
simonsgray said:
Oh how i loathe this POS phone
i have this as my work support phone. It wouldn't reliably stay powered up, any time I did turn it on it took 20+ minutes to acquire data/cell/3g signal. turning on maps crashed the phone. so i figured i'd install a new rom
I have lots of experience with sony ericsson, nexus 4, nexus 7 2012, 2013, acer 10.1 tab. i've done all this stuff before, but i cannot get cyanogen 10 or 11 to install properly, and now my phone sits with a spinning logo doing nothing
i:
unlocked the bootloader as per instructions at htc dev
setup ADB on the phone
first jsut copied the c11.zip to the sd card and tried to install that, same issue on with the HTC logo
used hansoon's kit to sideload c10. claims to have installd, now just spins the logo.
any help would be great.
Click to expand...
Click to collapse
You give a lot of info in your sig, but nothing there or in your post if you're s-off or on and which recovery you're using. Since, you're Canadian you probably need s-off to flash the latest T-Mobile ruu for the radio. And ext4 seems to be the most trouble-free recovery for the amaze. If s-on you can probably still get CM working if you were already on ICS and flash with smart flash enabled in 4ext. If you're still having issues then try pushing the kernel with adb from hboot wth your pc.
I hope this helps.
Odysseus1962 said:
You give a lot of info in your sig, but nothing there or in your post if you're s-off or on and which recovery you're using. Since, you're Canadian you probably need s-off to flash the latest T-Mobile ruu for the radio. And ext4 seems to be the most trouble-free for the amaze. If s-on you can probably still get CM working if you were already on ICS and flash with smart flash enabled in 4ext. If you're still having issues then try pushing the kernel with adb from hboot wth your pc.
I hope this helps.
Click to expand...
Click to collapse
Thanks man. sig is a little out of date, i havent' needed xda as much since jumping to nexus. TWRP and i didn't do the s-off stuff. it says it needs a stock rom and i just havea spinning cyanogen mod. i will try install the 4ext and see if that changes the results.
Odysseus1962 said:
You give a lot of info in your sig, but nothing there or in your post if you're s-off or on and which recovery you're using. Since, you're Canadian you probably need s-off to flash the latest T-Mobile ruu for the radio. And ext4 seems to be the most trouble-free recovery for the amaze. If s-on you can probably still get CM working if you were already on ICS and flash with smart flash enabled in 4ext. If you're still having issues then try pushing the kernel with adb from hboot wth your pc.
I hope this helps.
Click to expand...
Click to collapse
Tried to install this RUU http://www.androidruu.com/getdownlo...1.41.661.3_release_258801lhwl8053lp8g5hcp.zip
but i get an error status 7 because the file_getprop assert fails.
was trying to install stock so i can do th s-off thing
simonsgray said:
Tried to install this RUU http://www.androidruu.com/getdownlo...1.41.661.3_release_258801lhwl8053lp8g5hcp.zip
but i get an error status 7 because the file_getprop assert fails.
was trying to install stock so i can do th s-off thing
Click to expand...
Click to collapse
If you want to flash back to the stock ICS image you need to first relock your bootloader. When you relock it will say relocked when in hboot. The procedure is to place the image in the root of your external SD card and select from hboot. It should recognize and flash back to stock, however everything other than your external SD gets wiped in the process. So you need to make sure you have a good recent backup. Also, you remember when you first HTC dev unlocked they sent you an image to push to unlock? Well, I hope you saved it, because you'll need it again to re-unlock the bootloader after flashing the firmware image, but before attaining s-off.
However, if you were already on your carrier's latest ICS firmware before you started flashing different ROMs, you probably already have their latest radio. If you install the latest 4ext and enable smart flash, you'll probably succeed in installing any of the source built ROMs (ASOP, CM, PACman, evervolv) without s-off, because ROMs built from the source don't have the CID flag in their binaries.
If you still decide to go back and attain s-off the procedure is as follows: 1) relock your bootloader 2) flash the latest stock firmware for the carrier that sold your device. 3) Unlock your bootloader again using the image and commands you previously did to HTC dev unlock the first time, 4) get s-off using the wire-trick 5) flash the hacked hboot (and another radio if you desire, but not required for most ROMs) 6) super CID to remove all carrier locked file / partition limitations and protections 7) Flash your preferred recovery. Because you're now s-off you can use TWRP, CWM, or 4ext since the protected partitions are no longer an issue. 8) Flash any ROM you want provided it's based on ICS or later (below won't work because the radio is incompatible).
Edit: One other thing to note before starting any of this make sure your battery is fully charged. Also, the first time you boot after installing CM or any ASOP based ROM it can take quite some time to go through the process before you get to the login screen. For me it usually takes a little under 10 mins. It may at first appear to be a little sluggish until the rom settles, usually about 10-15 mins.
I hope this helps
i bought the m8 on att froma guy on craigslist i cant figure out how to unroot it ive tried installing skydragon a maximus but i cant get pass the htc boot screen ive tried updating the twrp to the newest and no i dont have a recovery ive even tried downgrading to an older one any help?? edit!! i cant get pass the boot screen i had cwm and tried installing stock att firmware please help
Jduncan312 said:
i bought the m8 on att froma guy on craigslist i cant figure out how to unroot it ive tried installing skydragon a maximus but i cant get pass the htc boot screen ive tried updating the twrp to the newest and no i dont have a recovery ive even tried downgrading to an older one any help?? edit!! i cant get pass the boot screen i had cwm and tried installing stock att firmware please help
Click to expand...
Click to collapse
What does your heart really want? Do you want to run custom ROMs and have root or not? It mostly sounds like you may want to return to stock due to lack of understanding and knowledge. That's okay if you want to do that. But kinda against the spirit of XDA!
Relock the bootloader and RUU will return the phone to stock and unrooted.
But it just sounds like you have mismatched firmware (results in long boot times with no boot animation, which some folks mistake for it not being booted).
Also, the newest TWRP require updated hboot, so that is probably the problem there.
If you want the phone rooted, and running a custom ROM: either run a ROM that corresponds with your firmware, or s-off and update your firmware.
What hboot and radio numbers? S-on or S-off?
redpoint73 said:
What does your heart really want? Do you want to run custom ROMs and have root or not? It mostly sounds like you may want to return to stock due to lack of understanding and knowledge. That's okay if you want to do that. But kinda against the spirit of XDA!
Relock the bootloader and RUU will return the phone to stock and unrooted.
But it just sounds like you have mismatched firmware (results in long boot times with no boot animation, which some folks mistake for it not being booted).
Also, the newest TWRP require updated hboot, so that is probably the problem there.
If you want the phone rooted, and running a custom ROM: either run a ROM that corresponds with your firmware, or s-off and update your firmware.
What hboot and radio numbers? S-on or S-off?
Click to expand...
Click to collapse
my hboot is 3.16.0 not sure about the s on and off thing but yeah iw ould love to run roms on it I tried downloading the skydragon 5.0.1 on it but it was stuck at the boot screen im using clockwork mod but I cant get twrp back on because I cant boot into the phone and ive tried everything to install the drivers and ive tried to manually install them also but no luck if you can email me or something to help me out it would be great!! [email protected]
Jduncan312 said:
my hboot is 3.16.0 not sure about the s on and off thing but yeah iw ould love to run roms on it I tried downloading the skydragon 5.0.1 on it but it was stuck at the boot screen im using clockwork mod but I cant get twrp back on because I cant boot into the phone and ive tried everything to install the drivers and ive tried to manually install them also but no luck if you can email me or something to help me out it would be great!! [email protected]
Click to expand...
Click to collapse
Holy run-on sentence! Seriously, please take the time to type a proper response with punctuation. Making it easier to read, makes it easier for me to help you. And that is what you want, isn't it???
I don't use my personal email for this type of support. That is what these forums are for.
Skydragon is probably not "stuck" but rather taking an extremely long time to boot (10+ minutes) with no boot animation, which often leads folks to believe its stuck altogether. If you leave it alone, it will probably boot eventually, but you may also find that WiFi is broken. Both are symptoms of the wrong firmware for the ROM you flashed.
Your hboot number also indicates that you don't have the right firmware installed, as firmware includes hboot as well as radio, WiFi, Bluetooth, and other modules.
On the AT&T variant, you will not have any "official" way to update the firmware to anything more up-to-date than 2.x firmware (hboot 3.17). You need 4.x firmware (hboot 3.19) to run the ROM you mentioned. Therefore you need s-off by sunshine (if not s-off already).
You can check s-on or s-off by booting into bootloader, and you will see it says one of the other near the top of the screen.
Alternately, if you don't s-off, you can flash a ROM that corresponds to your firmware. Try the following ROM, but putting the ROM zip on a removable SD card using a card reader connected to your computer (if you have those available). Then boot into recovery,navigate to the file and flash: http://forum.xda-developers.com/showthread.php?t=2705640
Aside from that, you should really get your USB connectivity issue sorted out. You can't do much without it. Verify no response when you type fastboot devices when the phone is in fastboot mode. If it doesn't respond (should return device ID) then try a different USB cable, and different USB port. If on Windows, try going to Device Manager, finding the phone, and pick the option to manually select the drivers, than pick the USB MTP drivers (not the HTC ones). This will often fix adb/fastboot connectivity issues.
Hi guys
Well, where do I start?
I was using Virtous Shooter rom from these forums and it was all fine.
Since a new game came out and it requires Kitkat I wanted to install a custom rom. Funny thing is I wanted to do the same thing a year ago but with no success.
Anyway, I did all those unlocking, rooting and fastboot things but after I got to the cyanogen logo boot it just restarted itself and gone into a loop.
Info:
S-ON
HBOOT 1.53
Unlocked right now
Currently main rom installed is once again virtous shooter but it won't boot. I can only use fastboot and recovery right now
Recovery is Revolutionary but I also used 4Ext for installing Cyanogen 11. I have it all on SD card.
The main thing I am asking you:
Steps on how to revert everything to stock and make it functional. I don't care what it takes, I'll try everything but I just need some direction.
I think I know why Cyanogen didn't boot up in the first place. I had to downgrade my hboot to 1.49 before doing anything else but I didn't...
Please, if you can, help me. I want to revert everything or even better install directly Cyanogen 11 Kitkat for my device but 100% functional.
I am not a complete noob in this so you can skip all those beginner things.
Thank you!!
Okay I fixed it a bit. I succesfuly installed the stock RUU. Any help on installing cyanogen 11?
sime30 said:
Okay I fixed it a bit. I succesfuly installed the stock RUU. Any help on installing cyanogen 11?
Click to expand...
Click to collapse
Bump. Device is working just fine on the stock RUU. I still , however, want to use Kitkat Cyanogen mod 11.
My main issue is HBOOT. Could anyone give me some insight/steps on how to do this?
Thanks
sime30 said:
Hi guys
Well, where do I start?
I was using Virtous Shooter rom from these forums and it was all fine.
Since a new game came out and it requires Kitkat I wanted to install a custom rom. Funny thing is I wanted to do the same thing a year ago but with no success.
Anyway, I did all those unlocking, rooting and fastboot things but after I got to the cyanogen logo boot it just restarted itself and gone into a loop.
Info:
S-ON
HBOOT 1.53
Unlocked right now
Currently main rom installed is once again virtous shooter but it won't boot. I can only use fastboot and recovery right now
Recovery is Revolutionary but I also used 4Ext for installing Cyanogen 11. I have it all on SD card.
The main thing I am asking you:
Steps on how to revert everything to stock and make it functional. I don't care what it takes, I'll try everything but I just need some direction.
I think I know why Cyanogen didn't boot up in the first place. I had to downgrade my hboot to 1.49 before doing anything else but I didn't...
Please, if you can, help me. I want to revert everything or even better install directly Cyanogen 11 Kitkat for my device but 100% functional.
I am not a complete noob in this so you can skip all those beginner things.
Thank you!!
Click to expand...
Click to collapse
I am in a similar position to you.
I managed to recover my phone with PG86IMG.ZIP and yodas_ICS_deodex.zip.
I am now back at ICS until I can figure out how to get KitKat on, so I can have a go at pokemon Go.
To get ICS back on my Evo 3D (GSM) I applied Clockwork Recovery image via fastboot (but PhilzTouch recovery also works), then told it to apply the above two zip files and it now boots back into ICS.
So at least I can use my phone again until I have the energy again to try to conquer my STATUS 7 issue.
If you are GSM and want my files or links I used to get up and running, please let me know.
therealeasterbunny said:
I am in a similar position to you.
I managed to recover my phone with PG86IMG.ZIP and yodas_ICS_deodex.zip.
I am now back at ICS until I can figure out how to get KitKat on, so I can have a go at pokemon Go.
To get ICS back on my Evo 3D (GSM) I applied Clockwork Recovery image via fastboot (but PhilzTouch recovery also works), then told it to apply the above two zip files and it now boots back into ICS.
So at least I can use my phone again until I have the energy again to try to conquer my STATUS 7 issue.
If you are GSM and want my files or links I used to get up and running, please let me know.
Click to expand...
Click to collapse
Thanks for the reply.
Seems like both of us want to play Pokemon Go.
My phone is working fine since I used PG86IMG.zip. I really don't need files for stock ICS because as I said I managed to make it work at least on it's default rom.
I am still however in mood to get Kitkat rom but no luck so far