After installing Gingerth3ory and loving it, my friend then applied the speedtweak and i believe its in an undervolted setting that is causing the phone to powercycle. The phone cant go into recovery to reflash the rom to get rid of the tweak because the P50IMG.zip is still on the SD card, so HBOOT is trying to constantly update that. Is there any way to get rid of the tweak so he can boot up the phone?
Pull the SD card and delete the PG05IMG.zip either with another device or card reader
If you're bootlooping and you have the PG05IMG.zip radio file on your sdcard, the first thing you will need to do is get it off. Use an adapter so you can remove the file using a computer or place the sdcard in another phone and remove it that way. Either way, you need to get that file off to get to recovery to fix your bootloops.
Okay he was just able to get the PC to recognize the sd card and pulled the zip. If he reinstalls the rom will that negate the settings of the speedtweak?
Ch0s3n0n3 said:
Okay he was just able to get the PC to recognize the sd card and pulled the zip. If he reinstalls the rom will that negate the settings of the speedtweak?
Click to expand...
Click to collapse
It would help if we knew what the "speedtweak" you are speaking of actually is. Either way, he can flash the rom then try to boot. If it doesn't boot then boot back into recovery and wipe data/cache. Flashing just the rom will probably work though if they were just clock/voltage related tweaks.
Absolute_Zero said:
It would help if we knew what the "speedtweak" you are speaking of actually is. Either way, he can flash the rom then try to boot. If it doesn't boot then boot back into recovery and wipe data/cache. Flashing just the rom will probably work though if they were just clock/voltage related tweaks.
Click to expand...
Click to collapse
Sorry it was Script Fusion, and yes it was a undervolt and overclock tweak. I had him reflash and it seems all is well. I also told him to delete the Script zip until he reads further and learns about it. I really appreciate your help as I am fluent in Droid X not Thunderbolt lol.
Bad timing (almost a pun)
So far I'm having zero luck getting out of the boot loop. Tried hboot w/ the ROM as PG05IMG.zip in the root; no go. Tried wiping cash/data/dalvik in CWR; no go. Tried reflashing the ROM via CWR; reboots before it can complete the operation. Anything else I can try? I guess there's no way to get to the init.d file to wipe the changes made by speedtweak?
Tried the "Normal" setting in speedtweak and that's what started everything.
ProfEngr said:
So far I'm having zero luck getting out of the boot loop. Tried hboot w/ the ROM as PG05IMG.zip in the root; no go. Tried wiping cash/data/dalvik in CWR; no go. Tried reflashing the ROM via CWR; reboots before it can complete the operation. Anything else I can try? I guess there's no way to get to the init.d file to wipe the changes made by speedtweak?
Tried the "Normal" setting in speedtweak and that's what started everything.
Click to expand...
Click to collapse
bootloader flashing isn't for the rom. It needs to be flashed in CWR as you later tried. At this point, the only thing you should be naming PG05IMG.zip, placing on your sdcard, and flashing is a radio (if you need to upgrade). But even then, you should have a booting rom first (not mandatory but encouraged).
You are able to make it to recovery, wipe data/cache, and flash a rom? At what point does the flash fail and is there an error reason stated? If you're in recovery the only thing that should be "preventing" the rom from flashing is the rom itself. The speedtweak files should already be gone before the rom even starts flashing since at that point /data, /cache, and /system have already been wiped.
You could try manually wiping each of those partitions multiple times (which never made complete sense to me) or download another rom or another copy of the current rom and try flashing it.
I got help from an IRC chat. Reloaded the 'upgrade' PG05IMG from the Tbolt root thread via hboot. That got me back online to where I could reflash.
Just for reference though, it was rebooting itself about 30sec into the ROM flash after the ROM notes/info scrolled on the screen.
ProfEngr said:
I got help from an IRC chat. Reloaded the 'upgrade' PG05IMG from the Tbolt root thread via hboot. That got me back online to where I could reflash.
Just for reference though, it was rebooting itself about 30sec into the ROM flash after the ROM notes/info scrolled on the screen.
Click to expand...
Click to collapse
That is weird. A tweak script that forces you to reflash firmware from the bootloader to fix it? Hmm, I suppose I should look up what this SpeadTweak script actually does for future reference. Either way, glad you got it fixed.
Absolute_Zero said:
That is weird. A tweak script that forces you to reflash firmware from the bootloader to fix it? Hmm, I suppose I should look up what this SpeadTweak script actually does for future reference. Either way, glad you got it fixed.
Click to expand...
Click to collapse
No.. Speedtweak.sh is built into imoseyons kernels and it allows you to control your kernel frequencies and governor. You don't have to install via hboot to remove it, all you need to do is flash a new kernel, even one that has Speedtweak.sh would be fine because you need to activate it manually through terminal.
I'm not sure why the OP was rebooting in recovery, that's what all of the phones that were reported as bricks were doing, but they were also rebooting in hboot which the OP wasn't. Obviously it wasn't a brick, but the Speedtweak script doesn't need to be removed via hboot, and it's just weird that the OP was rebooting in recovery.
Sent from my ThunderBolt using XDA Premium App
joshnichols189 said:
No.. Speedtweak.sh is built into imoseyons kernels and it allows you to control your kernel frequencies and governor. You don't have to install via hboot to remove it, all you need to do is flash a new kernel, even one that has Speedtweak.sh would be fine because you need to activate it manually through terminal.
I'm not sure why the OP was rebooting in recovery, that's what all of the phones that were reported as bricks were doing, but they were also rebooting in hboot which the OP wasn't. Obviously it wasn't a brick, but the Speedtweak script doesn't need to be removed via hboot, and it's just weird that the OP was rebooting in recovery.
Sent from my ThunderBolt using XDA Premium App
Click to expand...
Click to collapse
If I understand your terminology, I need to make a clarification.
The phone was stuck in a loop that would make it as far as the 1st HTC boot screen, buzz, hang, then restart the sequence. I was only able to wipe in CWR. It would reboot shortly after starting a ROM flash. hboot still worked as normal.
I'll look into how to flash just a kernel in case this happens again (HOPE NOT!!!)
For another discussion... After I got things sorted and reflashed the MR2 radio, CWR gives me an error when trying to format /system during Nandroid restore of any of my previous backups.
joshnichols189 said:
No.. Speedtweak.sh is built into imoseyons kernels and it allows you to control your kernel frequencies and governor. You don't have to install via hboot to remove it, all you need to do is flash a new kernel, even one that has Speedtweak.sh would be fine because you need to activate it manually through terminal.
I'm not sure why the OP was rebooting in recovery, that's what all of the phones that were reported as bricks were doing, but they were also rebooting in hboot which the OP wasn't. Obviously it wasn't a brick, but the Speedtweak script doesn't need to be removed via hboot, and it's just weird that the OP was rebooting in recovery.
Sent from my ThunderBolt using XDA Premium App
Click to expand...
Click to collapse
It was my understanding from their posts that they couldn't even flash anything. If it's the kernel itself or even init or bash scripts then flashing the rom clearly would fix that but it does little good if your phone reboots before you can even flash something.
Still not clear on what caused the problems of the two users here but the common denominator was that SpeadTweak script which as I said, someone would need to review to determine what may be causing the problem.
Absolute_Zero said:
It was my understanding from their posts that they couldn't even flash anything. If it's the kernel itself or even init or bash scripts then flashing the rom clearly would fix that but it does little good if your phone reboots before you can even flash something.
Still not clear on what caused the problems of the two users here but the common denominator was that SpeadTweak script which as I said, someone would need to review to determine what may be causing the problem.
Click to expand...
Click to collapse
I'm by no means saying you're wrong or anything, I was just letting you know what the speedtweak.sh script was since you had mentioned you weren't completely sure. I'm also unsure as to what was amiss with their phones, I just noted that the people who had bricked their phones (via one way or another), were rebooting in recovery, and that's the only time I had heard of rebooting in recovery. Obviously his hboot was fine, it's just very strange that recovery was rebooting because from my understanding recovery uses a completely different kernel than the main ROM.
Nice(?) to know I have a few people scratching their heads over this. Probably won't work, but I'll try to keep out of trouble on this until someone posts what's up.
That sounds like the boot loop issue that people were having before the MR2 radio came out, doesn't it?
loonatik78 said:
That sounds like the boot loop issue that people were having before the MR2 radio came out, doesn't it?
Click to expand...
Click to collapse
If don't know what issue you mean, there was a bricking issue but this isn't a brick
Sent from my Transformer TF101 using XDA Premium App
joshnichols189 said:
If don't know what issue you mean, there was a bricking issue but this isn't a brick
Sent from my Transformer TF101 using XDA Premium App
Click to expand...
Click to collapse
What they were calling a brick really wasn't much of a brick by definition A) because all it did was boot loop, and B) it was recoverable.
Related
Hi, i'm new here and i got a big problem! after instaling RCMIX_3D_EVO_kernel_v2.2.3.zip my phone kept rebooting on the htc logo, i tried various ways to solve this like instaling a new kernel, restore from a previous backup, changing roms, and do a factory reset. Nothing worked and now my problem is even bigger cause i cant go to the recovery mode ...
If someone can help me on this pleeaase :/
mikick said:
Hi, i'm new here and i got a big problem! after instaling RCMIX_3D_EVO_kernel_v2.2.3.zip my phone kept rebooting on the htc logo, i tried various ways to solve this like instaling a new kernel, restore from a previous backup, changing roms, and do a factory reset. Nothing worked and now my problem is even bigger cause i cant go to the recovery mode ...
If someone can help me on this pleeaase :/
Click to expand...
Click to collapse
If your on 2.3.4 that's your issue.those kernels won't work for it.pull battery.hold power and volume down go into recovery when battery is put back in..
sent from my badass EVO 3D running Kaos Hybrid 4.20 using tapatalk
I did that but when i choose recovery it boots to the htc logo and then keeps rebooting ...
no one knows what i can do ? :/ is there a way to reset the phone without recovery ?
You pulled the battery? Cause if you don't and fastboot is on.its would do that.
sent from my badass EVO 3D running Kaos Hybrid 4.20 using tapatalk
yes i did it just as you said ...
If you still can't get into recovery or the phone continuously bootloops after the battery pull, just run the latest RUU.
What is a RUU and how do i run it ? Do you have a link ? Thanks for the replies.
Have you taken the latest OTA, or have you ran revolutionary on your phone?
yes i have revolutionary on the phone
Go here, download the .exe with the 1.13.651.7, and run it as admin.
thanks, Is it a problem if i'm not on sprint? cause i'm in france and got the gsm version.
Yes, that would be a problem...try this thread and see if your version is listed.
i guess i'll try the "europe" one... if i dont risk to brick my phone by doing so ...
Tried and didn't work wasn't the good one... I hope i will find the good one soon i'll bookmark your link hoping that my version will be upped...
Thank you for your help.
Did you solve the problem?
Hi I just have the same problems like you ... I am in France, and after installing a new kernel, the phone is an a restarting loop.
I can go to the recovery mode (revolutionary) , I have tried to install different kernel and different ROM, but it alwas failed...
Thanks
MikRunny problems
I have a similar problem.
I tried installing MikRunny, (I flashed the boot.img multiple times, and did a full wipe, multiple times), but I keep getting a bootloop.
I fastbooted the boot.img, and I replaced the boot.img in the kernel map in MikRunny.zip.
My phone is (according to recovery) S-OFF, Revolutionary, 1.49 HBOOT, GSM.
That was the problem, the boot.img was not for GSM, but for CDMA.
But yet, I replaced it, and it still doesn't work...
mikick said:
Tried and didn't work wasn't the good one... I hope i will find the good one soon i'll bookmark your link hoping that my version will be upped...
Thank you for your help.
Click to expand...
Click to collapse
Search Google, Rootzwiki, and XDA for an SD bootable CWM or TWRP recovery image for the phone. Use all terms for the Evo 3D (shooter, 3vo, E3D, and even the HTC model number, which is PG86100). Write it to a microSD with dd in Linux or Win32DiskImager in Windows. After it's done writing, just drop your zips onto the card as you normally would and place it back into the phone. Proceed to recovery as you normally would. Wipe system, data, cache, dalvik cache, and battery stats. Now flash your ROM zip and follow it with your GAPPS zip. Reboot system and pray for the best. If you need any more assistance or help, feel free to PM me. Hope this helps, I know how bricking a phone feels. Just remember that there's no such thing as a permanent brick, unless you hit it with a real brick .
Sent from my PG86100 using xda premium
MikeyCriggz said:
Search Google, Rootzwiki, and XDA for an SD bootable CWM or TWRP recovery image for the phone. Use all terms for the Evo 3D (shooter, 3vo, E3D, and even the HTC model number, which is PG86100). Write it to a microSD with dd in Linux or Win32DiskImager in Windows. After it's done writing, just drop your zips onto the card as you normally would and place it back into the phone. Proceed to recovery as you normally would. Wipe system, data, cache, dalvik cache, and battery stats. Now flash your ROM zip and follow it with your GAPPS zip. Reboot system and pray for the best. If you need any more assistance or help, feel free to PM me. Hope this helps, I know how bricking a phone feels. Just remember that there's no such thing as a permanent brick, unless you hit it with a real brick .
Sent from my PG86100 using xda premium
Click to expand...
Click to collapse
Hey i ran into this problem yesterday flashing this Kernel...i used the flash gui app...what happened was it booted after it flashed....and it stuck in bootloop...i tried reflashing it the regular way just through cwm and it wasnt doing anything...so i did a google search on how to flash kernels on hboot 1.5 this is what i got...http://youtu.be/HclYpo0ZR3s that youtube video shows how to flash the kernel....THE WAY I KNEW HOW TO....but he says at the end there is a backup way to flash kernels..he says its longer but it also works just as good he says that you fastboot flash it via command prompt...so this gave me an idea...he says open up command prompt and prompt it to the folder you have used to unlock the device...unzip the boot.img file from the kernel your using in command prompt youd type fastboot flash boot boot.img....THIS NEXT PART I THOUGHT OF MYSELF. i removed the boot.img from the rom i was using and flashed that first AND FLASHED THE EXACT ROM I REMOVED THE BOOT.IMG FROM TO GET IT ROOTED. Not only did i solve my original kenel problem where my radios were jacked up BUT, i also got this kernel to work, and my synergy rom to work with the kernel, everything works and i was unbricked...I HOPE ANYBODY WHO RUNS INTO THIS PROBLEM DOES THIS AND THEY ARE OK.
Ok, I looked around and cannot find an answer that works for me for this issue. I am wondering if it has to do with my phone having S-Off? I am most likely wrong, but i have to know whats going on. No matter what I try, I cannot get My Rezound to go from GB to ICS, ANY ICS BASED ROM for that matter. I checked MD5, Tried with battery door both removed and attached, with or without the SIM card inserted into the phone. The phone boots up almost 100%. I get a message saying "Updating Android" and it says its updating or doing something to 160 apps, the system then reboots, when it gets past the 4G screen again, It says that the boot was completed, I have no signal, i checked on the service type and its correct, tried a factory reset, and still nothing, the system just continues to boot loop over and over again, and when it boots up i cannot get past the Activation screen where it says that the phone is trying to contact Verizon to Auto Activate. I can go back to GB easily, and that works %100. Any and all information would be useful, Only reason why i think this might have to do with S-Off is because my first Rezound was S-On and worked just fine going to ICS, while this new one has S-Off and is just not cutting it.
If you have s-off the rom image could contain a radio update. That could be getting you...also data is off by default in some ICS ROMs.
Sent from my ADR6425LVW using Tapatalk
Sent from my ADR6425LVW using Tapatalk
MrSmith317 said:
If you have s-off the rom image could contain a radio update. That could be getting you...also data is off by default in some ICS ROMs.
Sent from my ADR6425LVW using Tapatalk
Sent from my ADR6425LVW using Tapatalk
Click to expand...
Click to collapse
so what would be recommended in this type of situation? I know its not the data being off thats causing the issue, because when i boot up i dont have a signal at all, and the lock screen instead of showing VZW banner it says No Signal. Would the Radio being an issue also cause boot loop issues?
Did you put the battery cover on the phone ?
Edit saw that u did sorry ...
Sent from my Dinc... I mean Rezound
Only thing i can think of is that the ICS rom you flashed has data off automatically, and requires you to keep pressing the home button until it passes the activation screen.
Also make sure your battery cover is on like yojoe600 said, your antenna is connected to the cover and without it you will have no signal.
who_mike_d said:
Only thing i can think of is that the ICS rom you flashed has data off automatically, and requires you to keep pressing the home button until it passes the activation screen.
Also make sure your battery cover is on like yojoe600 said, your antenna is connected to the cover and without it you will have no signal.
Click to expand...
Click to collapse
this is just sooooooooo irritating. all that i have tried, this is kinda depressing. One interesting thing that i did come across though. When i flashed the BAMF GB, and tried to go from rom to rom to rom, i didnt get any MainVer error.... Dont know if thats just because S-Off allows you to go from one to another freely, or if its just not taking these updates.....
S-off has no mainvar issues. Try putting the gb radio into a PB zip or whatever the resound uses and flash that and boot to see of you get data then
Sent from my ADR6425LVW using XDA App
hey guys, its not just data, the phone is bootlooping on him.
I know several people have s-off devices. You might try looking over on rootzwiki as well. Maybe a dev with s-off can help.
I am one of those people with an s-off and I have had no issues with it but I also updated to the ICS radio AMD have no issues so I'm not totally sure what not working with yours
Sent from my ADR6425LVW using XDA App
werdna87 said:
I am one of those people with an s-off and I have had no issues with it but I also updated to the ICS radio AMD have no issues so I'm not totally sure what not working with yours
Sent from my ADR6425LVW using XDA App
Click to expand...
Click to collapse
Not sure what is going on with mine that is making it so different. This is just frustrating, last thing that im going to try is going to be flashing th kernel through adb, know that whould not matter too much, but i'll give it a shot, not like it would hurt at all.
dalvear88 said:
Not sure what is going on with mine that is making it so different. This is just frustrating, last thing that im going to try is going to be flashing th kernel through adb, know that whould not matter too much, but i'll give it a shot, not like it would hurt at all.
Click to expand...
Click to collapse
Ok , so i tried this, and as i thought not much happened, more of the same. No real help at Rootz either sadly. I need to find me an S-Off Dev.... lol
On a side note, how would one go about flashing a different recovery.img on an S-Off device, do i have to adb it, or can i do it on the fly? If so, how?
Last thought...did you try the bootloop fix? ##whatever after booting without the battery covery etc...?? There' s a full thread on it.
MrSmith317 said:
Last thought...did you try the bootloop fix? ##whatever after booting without the battery covery etc...?? There' s a full thread on it.
Click to expand...
Click to collapse
yeah was about to give that a go, but the system seems to shut down before i get to the phone portion. I'm having to use the Emergency Call option to get to the dialer since the phone sits on the Self Activation Page.
Before anyone can help you fully and properly, more information needed!
What ROM are you trying to install?
angryPirate12 said:
Before anyone can help you fully and properly, more information needed!
What ROM are you trying to install?
Click to expand...
Click to collapse
what you mean more info, my original post was pretty clear, dont mean to be snappy or anything, i could try to give more info maybe. I've tried all the "fixes" and so far nothing works. ALL AND ANY ICS BASED ROMS are not staying stable on my phone. They get stuck in what i think is the data bootloop, but i cannot access the dial pad other than through the Emergency dial pad, i input the *#*#4636#*#* and nothing comes up, i try without the battery cover, and without the SIM card as well (Also have tried Various combinations of SIM and Battery Cover removals and inclusions). The device has S-Off, and is Unlocked with DevUnlock, and has Perm Root.
Like I stated in my initial post, the leak may contain a radio update that your phone(and the network) isn't ready for. We wouldn't get that update because our radios are locked and only a signed update from HTC would install it. I'd say back down to GB and wait it out...or post in the thread of the ROM maker and ask them about the radio.
dalvear88 said:
what you mean more info, my original post was pretty clear, dont mean to be snappy or anything, i could try to give more info maybe. I've tried all the "fixes" and so far nothing works. ALL AND ANY ICS BASED ROMS are not staying stable on my phone. They get stuck in what i think is the data bootloop, but i cannot access the dial pad other than through the Emergency dial pad, i input the *#*#4636#*#* and nothing comes up, i try without the battery cover, and without the SIM card as well (Also have tried Various combinations of SIM and Battery Cover removals and inclusions). The device has S-Off, and is Unlocked with DevUnlock, and has Perm Root.
Click to expand...
Click to collapse
When I say more info, I mean don't describe every symptom... tell us specifically what you did. Every ICS ROM is unique, like for example I last installed newtoroot's Senseless 4.0.3 ROM. In order to use it, I had to flash a ICS Kernel, I used the fastboot method. Then I could flash the ROM using AmonRa Recovery, and it would boot and operate effectively.
That's the kind of specifics we need, so we can follow your steps and identify possible error points, if any.
angryPirate12 said:
When I say more info, I mean don't describe every symptom... tell us specifically what you did. Every ICS ROM is unique, like for example I last installed newtoroot's Senseless 4.0.3 ROM. In order to use it, I had to flash a ICS Kernel, I used the fastboot method. Then I could flash the ROM using AmonRa Recovery, and it would boot and operate effectively.
That's the kind of specifics we need, so we can follow your steps and identify possible error points, if any.
Click to expand...
Click to collapse
Definetly more descriptive lol thank you for the breakdown infact. In that case, last one i tried what the ICS Sense Redefined, and I tried to use the fastboot method for the Included Kernel as well, but that didnt work at all, what ICS Kernel did you flash to get it to work? a Pre-Packaged one? When installing, I did a full wipe (Both the Amon Ra Factory Reset option and the SuperWipe that is in the Dev Forum) installed the Rom, went into the Bootloader and did ADB CMD of fastboot flash boot boot.img and thats about it.
dalvear88 said:
Definetly more descriptive lol thank you for the breakdown infact. In that case, last one i tried what the ICS Sense Redefined, and I tried to use the fastboot method for the Included Kernel as well, but that didnt work at all, what ICS Kernel did you flash to get it to work? a Pre-Packaged one? When installing, I did a full wipe (Both the Amon Ra Factory Reset option and the SuperWipe that is in the Dev Forum) installed the Rom, went into the Bootloader and did ADB CMD of fastboot flash boot boot.img and thats about it.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=22203549&postcount=40
That is the one I used. If you're having issues with fastboot flashing the kernel, you may want to throw the PH98IMG.zip onto your external sd-card and boot into HBOOT then hit vol up to install it that way
angryPirate12 said:
http://forum.xda-developers.com/showpost.php?p=22203549&postcount=40
That is the one I used. If you're having issues with fastboot flashing the kernel, you may want to throw the PH98IMG.zip onto your external sd-card and boot into HBOOT then hit vol up to install it that way
Click to expand...
Click to collapse
ok, i'll give this a shot really quick and do through ext. sd. thanks for the link btw, you've been extremely helpful. let ya know how this goes for me.
Hello,
I've been all over google and this site for the last two days trying to find a way to get my Evo 3d work! I tried searching the forum and unfortunately i kept getting server errors So i figured I would make a new thread in the hopes of figuring this out!
What happened:
I went through the rooting process, and I went to flash a ROM on to the phone and it would not load pass the HTC screen. I had a ROM on there of the stock version of the Sprint Evo 3d, unfortunately it wasn't the proper version and it did not allow 4G and such. So i tried to place another ROM on to the SD Card and flash it over, and for some dumb reason, I deleted the version of the Stock Rom that atleast enabled me to get the phone to turn all the way on. All I'm able now is to boot up to recovery, but I can't figure out what ROM to download to place on the phone to get me back to square one!!!
Help please!!
-Mike
jerseybizzle said:
Hello,
I've been all over google and this site for the last two days trying to find a way to get my Evo 3d work! I tried searching the forum and unfortunately i kept getting server errors So i figured I would make a new thread in the hopes of figuring this out!
What happened:
I went through the rooting process, and I went to flash a ROM on to the phone and it would not load pass the HTC screen. I had a ROM on there of the stock version of the Sprint Evo 3d, unfortunately it wasn't the proper version and it did not allow 4G and such. So i tried to place another ROM on to the SD Card and flash it over, and for some dumb reason, I deleted the version of the Stock Rom that atleast enabled me to get the phone to turn all the way on. All I'm able now is to boot up to recovery, but I can't figure out what ROM to download to place on the phone to get me back to square one!!!
Help please!!
-Mike
Click to expand...
Click to collapse
Hi jerseybizzle, I can certainly try to help you but you have to help me first.
1. Are you doing a factory reset and wiping dalvik cache before flashing?
2. What hboot version do you have?
3. Is your phone s-on or s-off?
4. Which rom did you try to flash that wouldn't boot?
wikdNoob said:
Hi jerseybizzle, I can certainly try to help you but you have to help me first.
1. Are you doing a factory reset and wiping dalvik cache before flashing?
2. What hboot version do you have?
3. Is your phone s-on or s-off?
4. Which rom did you try to flash that wouldn't boot?
Click to expand...
Click to collapse
1. Yes
2. 1.50
3. My phone says S-on but I have super user privileges and the guide I followed said I have the phone rooted whether or not it said S-Off or S-On.
4. I believe it was the ViperMod
jerseybizzle said:
1. Yes
2. 1.50
3. My phone says S-on but I have super user privileges and the guide I followed said I have the phone rooted whether or not it said S-Off or S-On.
4. I believe it was the ViperMod
Click to expand...
Click to collapse
If it was an ics Rom and you are having bootloops, it is most likely because you are s-on. I recommend getting s-off. The wire trick is easy to do, but you need to be careful.
http://forum.xda-developers.com/showthread.php?t=1585846
Sent from my ICS 3VO with Tapatalk 2
Did you flash the rom through fastboot? If you just booted into your recovery and attempted to flash the ICS version of that rom coming from GB it won't work since you still have S-ON and that doesn't let you flash certain things like kernels. You can still flash roms but you have to take a couple extra steps or achieve S-OFF.
To get your phone working again...
If you were just coming from a stock rooted rom before attempting to flash a new rom, simply download a stock rooted rom from the dev section, put it on your SD card, boot into recovery, wipe and reflash. Your phone should then boot up again.
Sent from my PG86100 using xda app-developers app
jerseybizzle said:
1. Yes
2. 1.50
3. My phone says S-on but I have super user privileges and the guide I followed said I have the phone rooted whether or not it said S-Off or S-On.
4. I believe it was the ViperMod
Click to expand...
Click to collapse
I'm guessing it was the ics version of vipermod, and since you're s-on your boot image didn't flash. So you're trying to boot an ics rom with a gingerbread kernel.
If you want to use an ics rom, you have a few choices. My favorite... Put a recovery image in the folder on your computer that has fastboot in it. Put the phone in fastboot mode and type in the command window, fastboot boot recovery.img, make sure that you name the recovery image on your comp. to "recovery.img". It should boot to recovery and you can flash away.
Something that's easier is to use 4ext recovery smart flash. I'm sure it works but I've never used it.
If you want to get back to your stock rom unrooted rom you could run an ruu.
Also, take coals advice and s-off that phone, you won't have nearly as many issues once you s-off, and you can use one of the splash screens in my Sig
flonker said:
Did you flash the rom through fastboot? If you just booted into your recovery and attempted to flash the ICS version of that rom coming from GB it won't work since you still have S-ON and that doesn't let you flash certain things like kernels. You can still flash roms but you have to take a couple extra steps or achieve S-OFF.
To get your phone working again...
If you were just coming from a stock rooted rom before attempting to flash a new rom, simply download a stock rooted rom from the dev section, put it on your SD card, boot into recovery, wipe and reflash. Your phone should then boot up again.
Sent from my PG86100 using xda app-developers app
Click to expand...
Click to collapse
I have a stock ROM finally loaded on to here now, but it won't allow me access to Wifi now! When I try to connect it just says "error". Any ideas?
jerseybizzle said:
I have a stock ROM finally loaded on to here now, but it won't allow me access to Wifi now! When I try to connect it just says "error". Any ideas?
Click to expand...
Click to collapse
Here's an idea, get flash image GUI, its free here at xda, google it. Then use it to flash the kernel from the stock rom that you have running and reboot. This should fix your WiFi. Let me know if I'm not being clear enough.
wikdNoob said:
Here's an idea, get flash image GUI, its free here at xda, google it. Then use it to flash the kernel from the stock rom that you have running and reboot. This should fix your WiFi. Let me know if I'm not being clear enough.
Click to expand...
Click to collapse
Where would I find the stock Kernel?
jerseybizzle said:
I have a stock ROM finally loaded on to here now, but it won't allow me access to Wifi now! When I try to connect it just says "error". Any ideas?
Click to expand...
Click to collapse
So, it sounds like wifi turns on just fine, you just get the error when attempting to connect to a network?
Have you tried resetting your router and rebooting your phone? Maybe remove that network from your saved preferences and resign in.
Sent from my PG86100 using xda app-developers app
jerseybizzle said:
Where would I find the stock Kernel?
Click to expand...
Click to collapse
Inside the rom that you flashed, just choose that rom with flash image GUI and it'll pull the kernel out for you
flonker said:
So, it sounds like wifi turns on just fine, you just get the error when attempting to connect to a network?
Have you tried resetting your router and rebooting your phone? Maybe remove that network from your saved preferences and resign in.
Sent from my PG86100 using xda app-developers app
Click to expand...
Click to collapse
The wifi won't turn on period. I'll click the icon for the Wi-Fi to turn on, and it just says error. No option to even try to connect!
jerseybizzle said:
The wifi won't turn on period. I'll click the icon for the Wi-Fi to turn on, and it just says error. No option to even try to connect!
Click to expand...
Click to collapse
If the app that was suggested to didn't do the trick, hit the stickies in the dev section on how to flash a rom with hboot 1.5 S-ON. I recommend the fastboot method, however, if you're so inclined, you can also go the route of getting S-OFF.
Most likely, some problems occurred when you tried to flash that ROM before and broke your wifi. So, if I were you, I'd grab a ROM (that viper ics should be fine if you still got it) and flash it through fastboot using a guide in the dev section. Be sure to read and understand the guide before attempting it.
The guide would be something like this...
1. Install the appropriate drivers and place a recovery on your PC.
2. Boot into your boot loader, select fast boot, and connect your device to your PC via USB.
3. Open a command prompt on your computer, switch to the directory containing drivers/recovery image
4. Type fastboot boot thenameofyourrecovery.img
5. Install the rom as you otherwise normally would using your phone, wiping data, clearing caches, installing zip.
NOTE: The above is not a guide, just an illustration of the guide you're looking for in the dev section.
Flashing a rom by this method allows you to flash roms with non stock kernels, so you can pretty much flash any rom made for your phone. This is the method I have used since day 1 and have never experienced any problems. You may also want to look into getting S-OFF, but I can't say much about that because I haven't done it myself (being content flashing through fastboot).
Hope this helps.
Sent from my PG86100 using xda app-developers app
flonker said:
If the app that was suggested to didn't do the trick, hit the stickies in the dev section on how to flash a rom with hboot 1.5 S-ON. I recommend the fastboot method, however, if you're so inclined, you can also go the route of getting S-OFF.
Most likely, some problems occurred when you tried to flash that ROM before and broke your wifi. So, if I were you, I'd grab a ROM (that viper ics should be fine if you still got it) and flash it through fastboot using a guide in the dev section. Be sure to read and understand the guide before attempting it.
The guide would be something like this...
1. Install the appropriate drivers and place a recovery on your PC.
2. Boot into your boot loader, select fast boot, and connect your device to your PC via USB.
3. Open a command prompt on your computer, switch to the directory containing drivers/recovery image
4. Type fastboot boot thenameofyourrecovery.img
5. Install the rom as you otherwise normally would using your phone, wiping data, clearing caches, installing zip.
NOTE: The above is not a guide, just an illustration of the guide you're looking for in the dev section.
Flashing a rom by this method allows you to flash roms with non stock kernels, so you can pretty much flash any rom made for your phone. This is the method I have used since day 1 and have never experienced any problems. You may also want to look into getting S-OFF, but I can't say much about that because I haven't done it myself (being content flashing through fastboot).
Hope this helps.
Sent from my PG86100 using xda app-developers app
Click to expand...
Click to collapse
Thanks. I ended up finally finding a ROM (CM) that would load on to the phone. The Wi-Fi is working now!
I just need to find a fix for the camera, neither the regular nor 3D camera will function now.
jerseybizzle said:
Thanks. I ended up finally finding a ROM (CM) that would load on to the phone. The Wi-Fi is working now!
I just need to find a fix for the camera, neither the regular nor 3D camera will function now.
Click to expand...
Click to collapse
Which cm rom exactly? I thought the camera works with all the cm roms. It sounds like you still have kernel issues, and until you figure out how to flash a kernel or boot image, you'll always have these types of issues, bootloop, broken WiFi/camera. I know that the instructions that flonker gave you are intimidating but after you've done it once you'll see how simple it is.
One limitation of HTC dev unlocking is that you can't write to the boot partition from recovery, the kernel resides in the boot partition. You can, however, write to boot from within the android system. That's why flash image GUI is so handy for people with s-on and HTC dev unlocked. Just open the app, find the rom you'd like to flash and select it, the GUI will extract the kernel from the rom zip and flash it. Then you just boot into recovery and flash the same rom that you selected with the GUI. It'll flash everything but the boot image, but that's ok because you already flashed the kernel with flash image GUI. Make sure you do a factory reset and wipe the dalvik cache.
When I was s-on I always chose fastbooting to recovery, when you do that it actually loads the recovery onto the boot partition and gives you permission to write to boot, so its like flashing should be. Just wipe, flash, enjoy.
Hope this helps.
Wikd said:
Which cm rom exactly? I thought the camera works with all the cm roms. It sounds like you still have kernel issues, and until you figure out how to flash a kernel or boot image, you'll always have these types of issues, bootloop, broken WiFi/camera. I know that the instructions that flonker gave you are intimidating but after you've done it once you'll see how simple it is.
One limitation of HTC dev unlocking is that you can't write to the boot partition from recovery, the kernel resides in the boot partition. You can, however, write to boot from within the android system. That's why flash image GUI is so handy for people with s-on and HTC dev unlocked. Just open the app, find the rom you'd like to flash and select it, the GUI will extract the kernel from the rom zip and flash it. Then you just boot into recovery and flash the same rom that you selected with the GUI. It'll flash everything but the boot image, but that's ok because you already flashed the kernel with flash image GUI. Make sure you do a factory reset and wipe the dalvik cache.
When I was s-on I always chose fastbooting to recovery, when you do that it actually loads the recovery onto the boot partition and gives you permission to write to boot, so its like flashing should be. Just wipe, flash, enjoy.
Hope this helps.
Click to expand...
Click to collapse
I have been flashing roms and kernels and such for awhile on several different phones and literally almost everything you said makes no sense and that goes for the other guy 2 posts above yours. WTF is flash image GUI? Is that an app, you never even say.
The other guy is telling him to flash a rom but describes to him how to flash a recovery image to his phone...have you guys ever done this before or are you just making stuff up as you go?
flukeSG2 said:
I have been flashing roms and kernels and such for awhile on several different phones and literally almost everything you said makes no sense and that goes for the other guy 2 posts above yours. WTF is flash image GUI? Is that an app, you never even say.
The other guy is telling him to flash a rom but describes to him how to flash a recovery image to his phone...have you guys ever done this before or are you just making stuff up as you go?
Click to expand...
Click to collapse
Those guys probably don't even have EVO 3D's anymore. Do you read dates before posting? Threads a year old :screwy:
Sent from my PG86100 using xda app-developers app
RayTrue04 said:
Those guys probably don't even have EVO 3D's anymore. Do you read dates before posting? Threads a year old :screwy:
Sent from my PG86100 using xda app-developers app
Click to expand...
Click to collapse
Yes I do, I was looking for information and I read the entire thread. Just because they posted it a year ago doesn't make the info any less wrong.
So I've had the joy of rooting/unlocking a Thunderbolt and a Galaxy Nexus and now my DNA, so I'm vaguely familiar with how it works.
I had unlocked and rooted the phone about two months ago. I think I'm running a stock ROM with all the bloat removed I couldn't tell you exactly which one, but I think it's just the one that's deodexed with bloat removed. Had been running fine for awhile. Decided to use the Cubed DNA Kernel 2.4.2, roughly after I did this my phone would start to randomly reboot, which started about 2 weeks ago.
I didn't think anything of it up to this point and thought I'd fix it at some point. Today it rebooted once again, but this time it would never make it back into the Android OS, or if it did make it it would immediately freeze and I'd have to force reboot it. At this time I could still get into the CWR and the Bootloader. But that's really all I could do. I attempted to roll back to previous backups, this didn't work. So then I thought maybe it's the Kernel, so I was going to put it back to stock. Per the instructions I attempted to flash the boot.img file before flashing the stock kernel modules zip file.
After I did the flash for the boot.img, I can no longer get into CWR. I can still get into the bootloader, but that's really about it.
Unfortunately I have no device to fall back on. So any help or suggestions would be extremely helpful.
What happens when you try to go into recovery?
And just so you know, it was your kernel that was causing the reboots. It is a known issue with cubed kernel that dsb is working hard to fix.
Sent from my HTC6435LVW using xda app-developers app
Bigandrewgold said:
What happens when you try to go into recovery?
And just so you know, it was your kernel that was causing the reboots. It is a known issue with cubed kernel that dsb is working hard to fix.
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
It basically just reboots. It says "entering recovery" at the top of the HTC boot screen, then reboots immediately after that again and attempts to boot normal, it then goes into the droid boot animation and just hangs there.
cowprince said:
It basically just reboots. It says "entering recovery" at the top of the HTC boot screen, then reboots immediately after that again and attempts to boot normal, it then goes into the droid boot animation and just hangs there.
Click to expand...
Click to collapse
Try redownloading and reflashing the boot.img in fastboot. And if that doesn't work than flash a different recovery and see if that helps.
Sent from my HTC6435LVW using xda app-developers app
Bigandrewgold said:
Try redownloading and reflashing the boot.img in fastboot. And if that doesn't work than flash a different recovery and see if that helps.
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
Thanks Big, I was going to try it before I went to work this morning, but now it seems like the device is completely dead.
Will not power on and I get no lights when I attempt to charge it. I've tried multiple USB cables and charging methods, none result in any charging LED...
cowprince said:
Thanks Big, I was going to try it before I went to work this morning, but now it seems like the device is completely dead.
Will not power on and I get no lights when I attempt to charge it. I've tried multiple USB cables and charging methods, none result in any charging LED...
Click to expand...
Click to collapse
I should have been more clear there now that I've reread it, I never got the chance to try your suggestion, it's as if the battery died overnight and won't charge now.
cowprince said:
I should have been more clear there now that I've reread it, I never got the chance to try your suggestion, it's as if the battery died overnight and won't charge now.
Click to expand...
Click to collapse
Plug it in & Hold the power button down for about 15 to seconds for a hard reboot. If you can get it to boot, then try to flash the original stock kernal (link is located in dsb cubed kernel thread or here http://d-h.st/Ma1 ).
Once you flashed the original kernel flash dsb's other kernel stock cubed kernal here http://forum.xda-developers.com/showthread.php?t=2064066 . This one works real good, its basically stock but you can read/write and it has the hsic fix for a little better battery life.
You can use the stock cubed until the full cubed kernel is up and running with its fixes.
Hope this helps...
Jrocker23 said:
Plug it in & Hold the power button down for about 15 to seconds for a hard reboot. If you can get it to boot, then try to flash the original stock kernal (link is located in dsb cubed kernel thread or here http://d-h.st/Ma1 ).
Once you flashed the original kernel flash dsb's other kernel stock cubed kernal here http://forum.xda-developers.com/showthread.php?t=2064066 . This one works real good, its basically stock but you can read/write and it has the hsic fix for a little better battery life.
You can use the stock cubed until the full cubed kernel is up and running with its fixes.
Hope this helps...
Click to expand...
Click to collapse
Thanks Jrocker, I just hope I can get the thing to charge and/or boot when I get home.
Well it's not completely dead. Looks like I made it back into the bootloader. I can't seem to flash the boot.img file though:
fastboot flash boot boot.img
sending 'boot' (5412 KB)...
OKAY [ 0.839s]
writing 'boot'...
FAILED (remote: battery low)
finished. total time: 0.863s
So first thought would be, well ok charge the phone. However, I'm not so sure it's actually charging.
I have it plugged into the AC adapter while the bootloader is showing and it says FASTBOOT AC, however I see no solid orange LED telling me that the device is charging.
Also is there a way to push files to the SD card using fastboot. For example the stock kernel zip file?
OK I'm pretty sure I know what happened. Same thing has happened to me a few times. Apparently it only happens on some phones. I think the /data partition on your phone got borked. As in corrupted. It has done this to me about 3 times, each time I was running a custom kernel. Now that I know that my phone is one of the susceptible ones, I've been running DSB's stock system write kernel and have not had any issues since.
If this is the case, it sucks but the only thing you can do to fix it is to factory reset. When this has happened to me I have run fsck2 (disk checker) on my /data partition and it comes up with multiple errors and fixes them, but the phone still won't boot. I know dsb is aware of the issue, as are others, but there is no fix as of now besides either running stock kernels until it is fixed, or getting a new device (which may or may not be susceptible.) You can run fsck2 on your data partition and see if maybe it boots after fixing the errors, but I've had no luck 3 out of 3 times. Hope this helps.
EDIT: didn't realize that your recovery partiton got borked too, that's weird. Never had that happen. Reflash your recovery and then you should be able to go from there.
BotsOne said:
OK I'm pretty sure I know what happened. Same thing has happened to me a few times. Apparently it only happens on some phones. I think the /data partition on your phone got borked. As in corrupted. It has done this to me about 3 times, each time I was running a custom kernel. Now that I know that my phone is one of the susceptible ones, I've been running DSB's stock system write kernel and have not had any issues since.
If this is the case, it sucks but the only thing you can do to fix it is to factory reset. When this has happened to me I have run fsck2 (disk checker) on my /data partition and it comes up with multiple errors and fixes them, but the phone still won't boot. I know dsb is aware of the issue, as are others, but there is no fix as of now besides either running stock kernels until it is fixed, or getting a new device (which may or may not be susceptible.) You can run fsck2 on your data partition and see if maybe it boots after fixing the errors, but I've had no luck 3 out of 3 times. Hope this helps.
EDIT: didn't realize that your recovery partiton got borked too, that's weird. Never had that happen. Reflash your recovery and then you should be able to go from there.
Click to expand...
Click to collapse
So ultimately if I just do a factory reset and then restore one of my old backups after flashing the stock kernel boot.img I should be good then? Or should I still run fsck2?
cowprince said:
So ultimately if I just do a factory reset and then restore one of my old backups after flashing the stock kernel boot.img I should be good then? Or should I still run fsck2?
Click to expand...
Click to collapse
If you plan on restoring a backup there's no need to wipe. Recovery will wipe the data partition before it restores the old one. After that just flash your kernel and modules and you should be back up and running.
Fsck2 is not necessary. The only reason you might want to run fsck2 would be to:
1. verify that this is indeed your problem.
2.you have have a (slim) chance of fixing your data partition, saving you from wiping. Like I said I tried it and it did fix the disk errors, but still wouldn't boot.
Well it looks like I cannot do a restore of an old backup, I get an error saying that it can't mount /system
Am I doing this all in the right order?
reboot to bootloader
fastboot flash boot boot.img
fastboot flash recovery recovery.img
reboot to bootloader
reboot to recovery
factory reset
flash kernel
restore recovery backup
reboot
cowprince said:
Well it looks like I cannot do a restore of an old backup, I get an error saying that it can't mount /system
Am I doing this all in the right order?
reboot to bootloader
fastboot flash boot boot.img
fastboot flash recovery recovery.img
reboot to bootloader
reboot to recovery
factory reset
flash kernel
restore recovery backup
reboot
Click to expand...
Click to collapse
You might be able to fix that error by flashing a newer version of whatever recovery you are using. Not sure, never had that error. If you can't get your backup to flash do this (I'm assuming you already have a custom recovery installed/working since you tried to restore a backup)
1. reboot into bootloader
2. fastboot flash boot boot.img (dsb's stock kernel img)
3. reboot into recovery
4. factory reset
5. flash modules (dsb's stock kernel modules)
6. wipe cache and dalvik for good measure
7. cross fingers
8. reboot
If it doesn't boot after that I think I would reflash the rom and try again starting at step 4, but I think that^^ should do the trick.
Looks like I'm back in business, went ahead and flashed the stock system writable kernel and CWR, then the kernel module zip, a fresh ROM the Genome ROM and was good to go again.
However I still have one remaining problem. The wifi errors out and won't turn on.
cowprince said:
Looks like I'm back in business, went ahead and flashed the stock system writable kernel and CWR, then the kernel module zip, a fresh ROM the Genome ROM and was good to go again.
However I still have one remaining problem. The wifi errors out and won't turn on.
Click to expand...
Click to collapse
Glad to hear you're back up and running! Wifi not turning on is a telltale sign that you need to reflash your modules for whatever reason.
BotsOne said:
Glad to hear you're back up and running! Wifi not turning on is a telltale sign that you need to reflash your modules for whatever reason.
Click to expand...
Click to collapse
That's kinda what I had assumed.
Now I just need to hope for an AOSP ROM and some email widgets not bound to the Sense UI...
Actually no dice on the reflashing of the kernel modules. Maybe I should do the boot.img as well?
cowprince said:
Actually no dice on the reflashing of the kernel modules. Maybe I should do the boot.img as well?
Click to expand...
Click to collapse
U should do the boot.img 1st then boot into recovery and wipe cache/davik cache and flash the module. If u still having problems then get the stock DNA kernel
sent from my beastly powered viper DNA using Tapatalk 2
I was on TWRP 2.6.3.0 and just flashed CWM 6.0.3.6. I was having random FCs on TACHYON and wanted to see if CWM might help. Do I need to wipe anything after flashing a new recovery? Thanks.
geronimo48 said:
I was on TWRP 2.6.3.0 and just flashed CWM 6.0.3.6. I was having random FCs on TACHYON and wanted to see if CWM might help. Do I need to wipe anything after flashing a new recovery? Thanks.
Click to expand...
Click to collapse
No you don't need to wipe anything after flashing a new recovery. What force closes were you getting?
Sent from my ADR6425LVW using Tapatalk
XAlexander_AlexanderX said:
No you don't need to wipe anything after flashing a new recovery. What force closes were you getting?
Sent from my ADR6425LVW using Tapatalk
Click to expand...
Click to collapse
Phone randomly shuts down. I get a black screen and can't reboot unless I pull the battery. It usually won't fully boot unless it is plugged into a charger or PC. I had a problem with battery drain and overheating. I did S-Off and went through all of R3v3nt3ch's procedures to return to stock and reload all signed RUUs and OTAs. Then flashed TACHYON. The battery drain/overheating problem seems much better. There were no FCs at first, but they are getting more frequent. Just had one and my battery is at 80%.
geronimo48 said:
I was on TWRP 2.6.3.0 and just flashed CWM 6.0.3.6. I was having random FCs on TACHYON and wanted to see if CWM might help. Do I need to wipe anything after flashing a new recovery? Thanks.
Click to expand...
Click to collapse
If your recovery is the "cause" of your force closes, then after you install the new recovery, you need to do a complete wipe and reinstall the ROM and setup manually... If recovery is the "cause" of your issues, it is in the flashing of the ROM that is problem, not the actual recovery itself, that is the issue.
To be honest, those issues sound more like you need to S-OFF and clean flash everything from first RUU forward... it is not the most logical approach, but it seems to work for people having "weird" issues that don't seem to have a real cause.
I just did all of that.
Thanks
Sent from my Rezound on Tachyon using xda app-developers app
Your recovery isn't in use when you're booted into a rom, that's not what is causing your FC's unless as noted the ROM didn't install correctly.
mjones73 said:
Your recovery isn't in use when you're booted into a rom, that's not what is causing your FC's unless as noted the ROM didn't install correctly.
Click to expand...
Click to collapse
correct me if im wrong but couldnt an all in one kit if he flashed a recovery that way possibly cause issues...ive seen prior posts of people having similar issues with flashing that method
REV3NT3CH said:
correct me if im wrong but couldnt an all in one kit if he flashed a recovery that way possibly cause issues...ive seen prior posts of people having similar issues with flashing that method
Click to expand...
Click to collapse
As far as a I know those all in one kits still run the same fastboot flash command under the covers so I don't know how that could cause an issue. It's basically a GUI that runs the commands for you, not a big fan of them because you never learn the actual commands.