Database Info

Bricked after all this time

I had a lunch TB4g and it just bricked today, I was running ShiftAOSP 1.2 (I believe unrelated) and the .802 radio (possible) but it will just go to the HTC screen and reset and keep trying to boot. I can get into HBOOT and FASTBOOT, I have tried to reflash a root friendly RUU but it didnt fix anything and still cant boot. Just giving you a heads up. I had it overclocked to 1.22, I had it in my car on the way home, sent one text, 23% battery and I plugged it into my CPU USB to charge for a little waiting for some friends to show up and that is when it went into bootloop. Heat was not an issue as I had used it minimally the whole day sending small texts. It did sustain a major G shock 2 days prior but no excessive G or roughness today. Since it can get into HBOOT it might be recoverable but thats to the devs to decide, I have the unlocked 1.04 hboot installed.

i doubt the radio caused it, but that sucks man. see if you can talk verizon into a bionic for a replacement.

Does it bootloop in recovery?
Sent from my HTC Thunderbolt

JBO1018 said:
Does it bootloop in recovery?
Sent from my HTC Thunderbolt
Click to expand...
Click to collapse
he wont be able to get to recovery, hes bricked. i had this sorta happen to me weeks ago but my phone recovered on its own. to say the least i put full insurance on it.

fixxxer2008 said:
he wont be able to get to recovery, hes bricked. i had this sorta happen to me weeks ago but my phone recovered on its own. to say the least i put full insurance on it.
Click to expand...
Click to collapse
He said it boots to the splash screen and he can get into hboot. So I'm confused why you would think he couldn't select recovery in hboot and see what happens. If he already flashed a full stock RUU custom recovery will be gone tho.
Sent from my HTC Thunderbolt

JBO1018 said:
He said it boots to the splash screen and he can get into hboot. So I'm confused why you would think he couldn't select recovery in hboot and see what happens. If he already flashed a full stock RUU custom recovery will be gone tho.
Sent from my HTC Thunderbolt
Click to expand...
Click to collapse
if i were him id just replace it. i just hope my tbolt lasts until the vigor ships.

it will boot to hboot and not reboot, but it will not boot to recovery

Have you tried flashing one of the recoveries that were modified to install through hboot? you can take your sd card out, and using a computer, place the PG05IMG.zip (search here @ XDA) and place it on the root of the card, flash through hboot. then using the computer again, remove the PG05IMG.zip from the sd card and go back into hboot and select recovery. i had to do this not too long ago and it worked for me, maybe it will help you.

I pulled the battery and wont plug it in all night to see if it resets some error it maybe had, my new phone is delivered tomorrow so its not a big deal.

fixxxer2008 said:
if i were him id just replace it. i just hope my tbolt lasts until the vigor ships.
Click to expand...
Click to collapse
I would agree. The whole reason I asked about recovery boot looping is because if it is thats pretty much identical symptoms everyone who had the boot loop of death "brick" thing had. If that is what the situation is I would get it s-on and get VZW to replace because I doubt he caused it.
Sent from my HTC Thunderbolt

fillyo said:
All you cheap ****ers trying to get something for free, if he bricked, his loss. Period.
Click to expand...
Click to collapse
Ditto. He probably told insurance he lost the phone and paid his $100 bucks.
People are so greedy these days. All for nothing and nothing for all.

Doesn't sound design like there was much effort to fix it either.
Questioned posted and shortly after a new one is on the the way?
Keep an extra phone around for instances like this.
Not everything is an insurance claim.
Sent from my A500 using XDA Premium App

You wonder why all the major companies are starting to hate people who root phones. Some people will flash a Rom everyday just to do it and if they miss up their phone they don't seem to care. Now do I think a thunderbolt is worth 700 bucks retail hell no it only cost about 125 to build. But people need to hit up these forums to try to fix their phones before they call Verizon. I read a few post of guys who buy bricks phone fix them and sell them so any bricked phone can be fixed as far as he said. Read up and don't be so quick to clear data as first sign of a problem. Always try what got me out of the bootloop of death.
1. Battery pull
2. Power and hold down volume button
3. Never and I mean never keep a radio stored on root of SD card after install this will cause Hboot to install radio and that is not what we want to do here.
4. Go to recovery
5. Under download folders in your SD card always keep a updated ROM of what ever ROM you are currently using or at least a stable build inside that folder if you are using AOSP keep a stable ROM that last worked for you so no data clear is needed if you are using Sense do the same.
6. I never flash a recovery at this point follow this it saved my phone. Clear cache, clear delvik, format system under mounts and storage.
7. Format is most important since it will not delete recovery if you need to try again. Go to install zip file, select zip file, and install your fresh ROM or a stable build I never have flashed a normal ROM or have I flashed back to a down graded GB ROM.
8. Reboot after ROM has flashed and your phone will boot correctly.
I hope this has helped it saved me a few times in boot loop of death. Stop clearing data you lose your recovery and stop flashing old GB ROMs thinking they will save you, it might but message me so I can say I told you so.
****NOTE also make sure you are updated to newest CWM there was a problem with bootlooping after flashing a kernel and maybe Rom. I had the problem with flashing a kernel sent me into a bootloop. Update or roll back.******
Sent from my ADR6300 using XDA App

The OP probably gets into recovery for a few seconds then bootloops randomly. If you are not bootlooping in hboot, you are not bricked. Find the stock ruu file and flash that through hboot. Although you will lose root, the phone should work again.

If it's bricked, throw it to the ground and stomp on it til it breaks and claim insurance..... That should piss some people off here
Seriously tho some guy mentioned something about a HBoot friendly RUU. You should look into it
Sent from my SICKLY INFECTED VirusBolt Synergy 3.0 using XDA Premium App

As far as I have seen the random and sudden boot loop of death thing has happend to rooted and stock phones. Leading people much smarter than me to come to the conclusion it is most likely caused by some kind of hardware defect existent in a lot if not all Thunderbolts. If he bricked it trying to flash an hboot from an Incredible or a bad flash because of not taking 30 seconds to check MD5 sums then I would put the blame on him. I'm not trying to condone fraud but if the situation is what I was thinking it might be he shouldn't have to pay because HTC got cheap on some build lots or had some bad quality control. Bootlooping from a bad flash and being able to get into recovery and restore is NOT the same thing I'm talking about. In the situation I'm refering to the ROM and recovery both bootloop. You can still flash an RUU in hboot but even after that the phone still bootloops.
Sent from my HTC Thunderbolt

JBO1018 said:
As far as I have seen the random and sudden boot loop of death thing has happend to rooted and stock phones. Leading people much smarter than me to come to the conclusion it is most likely caused by some kind of hardware defect existent in a lot if not all Thunderbolts. If he bricked it trying to flash an hboot from an Incredible or a bad flash because of not taking 30 seconds to check MD5 sums then I would put the blame on him. I'm not trying to condone fraud but if the situation is what I was thinking it might be he shouldn't have to pay because HTC got cheap on some build lots or had some bad quality control. Bootlooping from a bad flash and being able to get into recovery and restore is NOT the same thing I'm talking about. In the situation I'm refering to the ROM and recovery both bootloop. You can still flash an RUU in hboot but even after that the phone still bootloops.
Sent from my HTC Thunderbolt
Click to expand...
Click to collapse
He could not get into recovery cause he cleared data, can't get there is there is not one. And it didn't seem to me like he tried to flashed CWM from HBoot either.
Sent from my ADR6400L using XDA App

Grnlantern79 said:
He could not get into recovery cause he cleared data, can't get there is there is not one. And it didn't seem to me like he tried to flashed CWM from HBoot either.
If he can't think of a way to fix it send it to me will have it running in a couple of google searches.
Sent from my ADR6400L using XDA App
Click to expand...
Click to collapse
Sent from my ADR6400L using XDA App

I tried to get into recovery a few times before doing anything, it would just go black and reboot to the HTC logo. As a last attempt I tried to load a rooted a ruu, it installed but didnt not boot. I have the 1.04 modded hboot so I dont think I can overwrite recovery. Either way, contrary to your beliefs I will not claim insurance on it, although this is a warranty issue, these phones are dropping left and right. I just moved to tmobile this week and my sensation 4g and G2x are supposed to be delivered today.

Thanks for your ideas but I tried to reflash recovery and it installed through hboot but it will just reset before it loads. I still have s-off and my emmc was the sem08g. I am going to plug it in and just let it boot loop all day while I am at work, maybe it will get out, maybe it wont, either way is it wont hurt anything.

phone go to recovery when charging

help me, im rooted with eng spl, my problem is when i power off my phone its goes to recovery mode, now using sparcsco 1.1, also when battery dies and i charge the phone go to recovery mode
any idea why??
before this i flashed cwm touch with flash image gui
Sent from my PG06100

Not sure of the exact reason why your handset does it. But in the early days of development for the Desire HD, this would occur when a custom recovery had been flashed.
The reason behind it was, when your handset was stock, turned off & placed on charge the phone would "boot" into a very basic HTC recovery mode to display the orange or green charging LED. When you replace the stock HTC recovery it simply boots up the recovery you have got installed.

andyharney said:
Not sure of the exact reason why your handset does it. But in the early days of development for the Desire HD, this would occur when a custom recovery had been flashed.
The reason behind it was, when your handset was stock, turned off & placed on charge the phone would "boot" into a very basic HTC recovery mode to display the orange or green charging LED. When you replace the stock HTC recovery it simply boots up the recovery you have got installed.
Click to expand...
Click to collapse
Wow, thanks for the explanation. That makes perfect sense. But I thought that issue had been fixed for the Shift? Sorry, been a few months since I had my Shift so I can't remember if it was ever fixed or we just all stopped complaining about it. Or at least I thought it had been fixed on the recent CM7 nightlies. Maybe one of these good for nothing current Shift owners could put down the crack pipe and chime in here

That has never been a problem with the shift. It's weird that it happens to you cause when I was on cwm touch that never happened. I have no idea how to help
Sent from my PG06100 using Xparent Cyan Tapatalk

jesusice said:
Wow, thanks for the explanation. That makes perfect sense. But I thought that issue had been fixed for the Shift? Sorry, been a few months since I had my Shift so I can't remember if it was ever fixed or we just all stopped complaining about it. Or at least I thought it had been fixed on the recent CM7 nightlies. Maybe one of these good for nothing current Shift owners could put down the crack pipe and chime in here
Click to expand...
Click to collapse
It's a htc charging while off issue only for recovery. The htc charging while off mode was used for the older recovery versions of clockworkmod but has since been depriciated and no longer works for ICS based recoveries like clockworkmod touch. No crack pipe smokers here bud.

sparksco said:
It's a htc charging while off issue only for recovery. The htc charging while off mode was used for the older recovery versions of clockworkmod but has since been depriciated and no longer works for ICS based recoveries like clockworkmod touch. No crack pipe smokers here bud.
Click to expand...
Click to collapse
so my phone is fine?
Sent from my PG06100

finally figured out this myself, need to reflash recovery with flash image gui
Sent from my PG06100

hacklana said:
finally figured out this myself, need to reflash recovery with flash image gui
Sent from my PG06100
Click to expand...
Click to collapse
Yeah I like flash image gui. The main issue I have with the recovery is that it will boot into recovery but if I don't touch anything it turns itslef back off again after about 5 seconds. It's almost like charging off is somewhat working but not completely. Oh well it's not a big deal for me and I'm very content right now with clockworkmod touch. another good way to flash recovery is in fastboot with the fastboot erase recovery command before flashing it.

Tip/warning rom manager recovery for htc one x (gsm)

I am creating this post as a tip and warning to everyone with an at&t htc one x (mostly noobs for help). If you have rom manager on your phone do not use it to flash the new recovery listed for the htc one x (gsm). I've been messing with android since 2009, but me seeing a new recovery for the one x with (gsm) next to it thought hey finally got an official clockwork recovery for our phones!!!!! Well i was wrong. Its for the international versions only not ours. The partition it writes the recovery to is on our bootloader partition, and flashing it will kill your phone. I flashed it, kept it on for hours but as soon as i rebooted the phone it turned off and would not turn on or charge. You'll pretty much be screwed and have to get a new phone unless you know how to run linux and ask for help fixing it which is harder than you think. Again do not flash the htc one x (gsm) recovery in rom manager!!!!!
Hope this helps some of you before hand and not after.
If this post isn't necessary i am sorry and please close it.

Nobody should ever use ROM Manager for anything, EVER.
Sorry for your loss.

Why would you flash a recovery for a different device and expect it to work?
When ROM manger is supported on your device its a great tool, like on the sgs2. If its not officilially supported on your device, don't mess with it.
Sent from my Nexus 7 using xda premium

nooomoto said:
Why would you flash a recovery for a different device and expect it to work?
When ROM manger is supported on your device its a great tool, like on the sgs2. If its not officilially supported on your device, don't mess with it.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
it was new on there at the time and with gsm next to i i figured it was for ours, anyway point is if i knew it wasnt for my phone i wouldnt have flashed it.

rob219 said:
it was new on there at the time and with gsm next to i i figured it was for ours, anyway point is if i knew it wasnt for my phone i wouldnt have flashed it.
Click to expand...
Click to collapse
in fact, it is not really that hard to fix. Just re-lock the phone via fastboot. then run RUU package from AT&T
It should set every thing back to original.
if your phone is not respond RUU, try reboot on RUU via fastboot.
By the way, The only recovery that works now is TWRP
Use this one only

sugeraddict said:
in fact, it is not really that hard to fix. Just re-lock the phone via fastboot. then run RUU package from AT&T
It should set every thing back to original.
if your phone is not respond RUU, try reboot on RUU via fastboot.
By the way, The only recovery that works now is TWRP
Use this one only
Click to expand...
Click to collapse
The ruu has to access the boot loader to verify your version. If you end up flashing a device and it writes certain partitions of your boot loader (ICJ).... Well your left with a permabrick, until someone finds a way to JTAG the One X(AT&T). I've heard that its already been done, but the person who has performed it has kept the pinout secret.
I'm not entirely sure which partitions your ROM manager has wrote to, if you can find that out you might be able to fix it... Depending on which ones have been written too.
Sent from my One X using xda app-developers app

Zombie thread alert!

Like many of us have said before. We are not the one x. We are the one XL.
Sent from my One X using xda app-developers app

_MetalHead_ said:
Nobody should ever use ROM Manager for anything, EVER.
Sorry for your loss.
Click to expand...
Click to collapse
Sorry, but I disagree!
I've had more problem locating backup files and restoring when in TWRP, than ROM manager!
Mike

MaverickCoast said:
Sorry, but I disagree!
I've had more problem locating backup files and restoring when in TWRP, than ROM manager!
Mike
Click to expand...
Click to collapse
You must be doing something wrong then. You don't even need to locate backups with TWRP, they're found automatically. Anyway, was it really necessary to revive an 18 month old thread just to say that?
Sent from my Evita

New to HTC need some help

Hey guys my s3 killed its self yesterday so I grabbed one of these beauties today and I'm really impressed so far(maybe its the custom ROM).
Now I got the phone off a guy, had it he unlocked the bootloader,rooted,and gave me the phone already running 4.1(dirty 1.8).no back ups to even a rooted stock.
Although I love jelly bean this battery is killing me and I would really like to have at least a stock zip I can flash in emergencies.
I am so unfamiliar with HTC(nexus one was the last one I owned)thank I really don't want to brick it.
OK so my questions are these
I have the rogers version of the Onex is there certain builds I need to look for or are they all just HTC one x?
With HTC is there a fallback like with samsung if things go wrong at least there's always download mode and Odin.
Do I need to have my boot loader unlocked?
Thanks in advance
And sorry for the noobness I just can't kill 2 phones in a week
Sent from my One X using xda app-developers app

You have a lot of reading ahead of you, grasshopper, before you're ready to do anything to your phone:
http://forum.xda-developers.com/showthread.php?t=1671237
To answer your questions:
todorcim said:
I have the rogers version of the Onex is there certain builds I need to look for or are they all just HTC one x
Click to expand...
Click to collapse
No! It is wise of you to ask this, because there are two versions of the One X, the International (Tegra 3 quad-core) and the US/Rogers/Telstra (dual-core S4). Flashing stuff for the wrong version can permanently brick your phone (i.e., there is no current fix for some of these mistakes).
With HTC is there a fallback like with samsung if things go wrong at least there's always download mode and Odin.
Click to expand...
Click to collapse
Assuming you haven't flashed the wrong ROM, you can generally always get out of trouble by booting into bootloader, relocking, and running the RUU for your firmware. Most problems can be fixed by going back into recovery and re-flashing or flashing something else.
Note: Figure out what version of hboot you have before doing anything. With 1.09, modding is pretty straightforward. With 1.14, you have to take some extra steps and there are a few things you can't do at all.
Do I need to have my boot loader unlocked?
Click to expand...
Click to collapse
Yes. Leave it unlocked unless you need to RUU.

His hboot should be 1.11 which is the same as 1.09 as far as installing roms go.
If you're looking for a Sense ICS rom, I recommend ViperXL or CleanRom5. But there are other roms to try. As long as you stay in this forum and not the international forum you should be safe to flash anything you want.

Awesome thanks guys.
I check my boot loader and it is 1.11..
So that makes me happy cause all in all I'm addicted to flashing
One last question for you before I venture off on my own here..
With my nexus one I and the passimg I could flash through my bootloader in cause something went wrong or I just want to refresh my n1,is there something like that for this phone or are those days long gone?
Again thanks a bundle
Sent from my One X using xda app-developers app

Flash from TWRP recovery

todorcim said:
With my nexus one I and the passimg I could flash through my bootloader in cause something went wrong or I just want to refresh my n1,is there something like that for this phone or are those days long gone?
Click to expand...
Click to collapse
Correct, stick to TWRP. There is an app called GooManager that makes installing and updating TWRP close to effortless.
If you haven't already, reboot to recovery and see what you've got installed. Some people insist on using ClockworkMod recovery because they've used it on other phones, but it's not supported for this one and can cause issues with data getting corrupted. If you have CWM installed, all you need to do is download GooManager and select "Install openrecovery script" in settings and it will replace it with TWRP.

Ya I always use twrp have for a while but what I mean is if (can?) I soft brick my phone or something happens that I can't flash from recovery is there a passimg zip like we had for the n1 that could be flash through the boot loader?
You know just in case
I only ask cause its HTC thought maybe there was something like that...could have been a Google thing too not sure..
Sent from my One X using xda app-developers app

todorcim said:
Ya I always use twrp have for a while but what I mean is if (can?) I soft brick my phone or something happens that I can't flash from recovery is there a passimg zip like we had for the n1 that could be flash through the boot loader?
You know just in case
I only ask cause its HTC thought maybe there was something like that...could have been a Google thing too not sure.
Click to expand...
Click to collapse
Yes, you can still flash stuff through fastboot, if that's what you mean.

Ya that's what I mean
Thanks
Sent from my One X using xda app-developers app

[Q] Where to Access Hasoon2000 S-Off Tool?

I've spent hours searching for how to S-Off my device. I've been running CM 9 and then 10, but it seems like my problem with 10.1 is S-on.
Most searches come to someone recommending Hasoon2000s S-Off tool, and linking to the original thread at: http://forum.xda-developers.com/showthread.php?t=1696373&highlight=s+off
The problem is that the link in that original thread to download the S-Off Tool is no longer there. I've looked through Hasoon2000s other downloads, and while there is the all-in-one toolkit 2.0, there doesn't seem to be a way to do S-Off in that kit.
I'll probably settle for JuopunutBear's solution, but since everywhere I go people are swearing by Hasoon2000s, (and I used the all-in-one toolkit with great success), does anyone have any new direction to track down a downloadable version of the S-Off tool, or a way to access it, or is JuopunutBear's all that is left for some reason? I haven't found any posts saying why Hasoon2000's has been pulled?
Thanks!

If I were you I would stay away from toolkits altogether. Not because they are bad, only because you learn absolutely nothing from using them and usually come bomb the threads when **** hits the fan.
The wire trick is a fun little task to handle though so everything should be okay that way.
Sent from my Nexus 4 using Tapatalk 2

Toolkit
ArachnydZ28 said:
I've spent hours searching for how to S-Off my device. I've been running CM 9 and then 10, but it seems like my problem with 10.1 is S-on.
Most searches come to someone recommending Hasoon2000s S-Off tool, and linking to the original thread at: http://forum.xda-developers.com/showthread.php?t=1696373&highlight=s+off
The problem is that the link in that original thread to download the S-Off Tool is no longer there. I've looked through Hasoon2000s other downloads, and while there is the all-in-one toolkit 2.0, there doesn't seem to be a way to do S-Off in that kit.
I'll probably settle for JuopunutBear's solution, but since everywhere I go people are swearing by Hasoon2000s, (and I used the all-in-one toolkit with great success), does anyone have any new direction to track down a downloadable version of the S-Off tool, or a way to access it, or is JuopunutBear's all that is left for some reason? I haven't found any posts saying why Hasoon2000's has been pulled?
Thanks!
Click to expand...
Click to collapse
His toolkit is still there, just browse around a bit... or go here... http://d-h.st/users/hasoon2000/?fld_id=2818#files

acwest said:
His toolkit is still there, just browse around a bit... or go here...
Click to expand...
Click to collapse
Thanks for your help I appreciate it- That was the same place linked to above.
Thats his toolkit 2.0 which I used to unlock my phone, but it doesn't give the phone S-Off (or atleast I couldnt find a way to do it in the toolkit)
His S-Off toolkit can't be found anymore on the otherhand, and I've searched in depth. I've been trying for at least 6-8 hours to get S-Off. Now I have a semi-bricked phone. Every path I go down is a dead end and its driving me nuts!
I was going to try the wire trick, but it requires stock rom. I had backed up the stock rom but it won't load. I downloaded 2 PD15IMG.zip files but neither of them will load, recovery says "Bad" when I try to run the .zip files. Did a little research. I think I need to do it via fastboot for the PD15IMG.zip files. Trying to figure that out now. Warnings seem pretty dire about trying to do it on a non-stock rom
This is getting above my head but I'm working my best to figure it out. Worst comes to worse I'll just have to order a new phone! I hate to be the novice that ends up being a PITA, as I've dealt with them plenty on the car forums I'm active on. I'd like to apologize up front for being "that guy".

Whats your situation now, do you have a recovery? What does it all say on your bootloader screen? Write that all down here
Sent from my Nexus 7 using xda premium

demkantor said:
Whats your situation now, do you have a recovery? What does it all say on your bootloader screen? Write that all down here
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
unlocked
Doubleshot PVT Ship S-On RL
Hboot- 1.45.0013
Microp-0353
eMMC-Boot
Nov 21 2011, 20:20:47
I do have recovery and hboot. Stock backup won't load though even though the file is there in recovery.
Thanks!

And what if you were to try and flash another rom, like miktouch, through recovery?
Sent from my MyTouch 4G Slide using xda premium

demkantor said:
And what if you were to try and flash another rom, like miktouch, through recovery?
Sent from my MyTouch 4G Slide using xda premium
Click to expand...
Click to collapse
I was able to reflash a version of CM10 I was using for a while and that works, but I can't find a stock one that will work. I've tried multiple, and they all give me "bad" error and don't finish the install.
I was going to try a different version of CM10, 10.1, or go to a stable release of 9. If none of those worked, I'd be happier with stock. None of the ones I've tried will work, but I'm assuming thats because I'm S-On, but since I can't find hasoon2000s S-Off tool everyone was raving about, and the wire trick requires stock ROM based on what the directions say, I find myself in a pickle.
The CM10 version I have can't do some basic things I need for work- like sync with my bluetooth in the car or not randomly freeze up during the day without me knowing it sending all my calls to voicemail. I tried versions of the others that other people are using (like silverL's 10.1 and the CM-listed stable CM9) and neither would load.
Do I have a different issue? AKA are other people with S-On able to load those Roms? I can try miktouch too.
---
Also trying to load via fastboot and I'm getting this error:
"Whoops: didn't find expected signature
read_central_directory_entry_failed
error: failed to access zipdata in [Whole bunch of non-english characters taking up a few lines]"
----
Update: Just to clarify, when I try to install a stock rom it gives me "Can't open [filename] (bad)
However, when I try to install the CM's, it installs fine and says "Install from sdcard complete" they just won't load when I restart my phone, except for the original version of CM10. (for example, in all the 10.1s I've tried I get "Unfortunately, the process com.android.phone has stopped" but the intro page will load. I figured that came down to an S-On issue when I tried to troubleshoot.

Any rom that is based off stock (like miktouch) should work to do the wire trick. I would check md5sums of the roms that won't flash to make sure they aren't corrupt at all. Also some say the latest twrp (and maybe other recoveries) won't flash some roms, so may need to change that as well
Sent from my MyTouch 4G Slide using xda premium

demkantor said:
Any rom that is based off stock (like miktouch) should work to do the wire trick. I would check md5sums of the roms that won't flash to make sure they aren't corrupt at all. Also some say the latest twrp (and maybe other recoveries) won't flash some roms, so may need to change that as well
Sent from my MyTouch 4G Slide using xda premium
Click to expand...
Click to collapse
Great, thanks!
I'll give miktouch a shot to see if I can use it for the wire trick. I'll let you know if it works.

ArachnydZ28 said:
Great, thanks!
I'll give miktouch a shot to see if I can use it for the wire trick. I'll let you know if it works.
Click to expand...
Click to collapse
negative.
miktouch would go through the install process, and end at the Tmobile mytouch 4g slide screen forever. I know on one install it took a long time to "load" the first time so I left it on this screen for about 15 minutes to no avail. Let me know if there is any chance of it taking longer than that. Reinstalls were the same story.
I got CM9.1 to install by installing it twice on top of itself (not sure why that fixes it) but it was a tiny bit buggy.
Is there any chance this could be bootloader related or recovery related? I can try to reload those too. grrr...

Its possible but if your bootloader can boot up one ROM it should be able to boot another. For this phone the only reason I have seen to change bootloaders is to unlock all the fastboot options. Flashing a new bootloader would reformat your partitions which may be the cause of your issue. Make sure you do a full wipe from recovery or fastboot -w or use a superwipe script, hell I tend to do all three between flashes but I'm kinda ocd when it comes to this, I hate debugging issues caused by residual effect from old data left after a dirty flash
But it may be worth it to flash a new recovery, not sure what you are using now but sometimes one will work when another doesn't, this would probably be my next step
Sent from my Nexus 7 using xda premium

demkantor said:
Its possible but if your bootloader can boot up one ROM it should be able to boot another. For this phone the only reason I have seen to change bootloaders is to unlock all the fastboot options. Flashing a new bootloader would reformat your partitions which may be the cause of your issue. Make sure you do a full wipe from recovery or fastboot -w or use a superwipe script, hell I tend to do all three between flashes but I'm kinda ocd when it comes to this, I hate debugging issues caused by residual effect from old data left after a dirty flash
But it may be worth it to flash a new recovery, not sure what you are using now but sometimes one will work when another doesn't, this would probably be my next step
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
I'm running CWM 5.5.0.4
I'll try to reload it or another version (I'm seeing some issues people have with 5504)
Thanks!

ArachnydZ28 said:
I'm running CWM 5.5.0.4
I'll try to reload it or another version (I'm seeing some issues people have with 5504)
Thanks!
Click to expand...
Click to collapse
You should try CWM 5.0.2.7. Also, since you are S-On you should extract the boot.img from Miktouch and flash it from fastboot, separately from the ROM. Since you have been on an ICS/Jellybean rom, I have to believe your original boot.img was replaced at some point. This is the only way to get back the Gingerbread boot.img. I am not savvy enough to know if this file is the bootloader or the kernel, but this process should get you back to stock-enough to do the wire trick.
Sent from my SGH-T699 using xda app-developers app

It's the kernel.....the boot.img file, I mean. The bootloader is that mostly white screen you see with "Hboot" at the top that will have "S-On" or "S-Off" after the word Radio. Good response.:good:

ArachnydZ28 said:
Thanks for your help I appreciate it- That was the same place linked to above.
Thats his toolkit 2.0 which I used to unlock my phone, but it doesn't give the phone S-Off (or atleast I couldnt find a way to do it in the toolkit)
His S-Off toolkit can't be found anymore on the otherhand, and I've searched in depth. I've been trying for at least 6-8 hours to get S-Off. Now I have a semi-bricked phone. Every path I go down is a dead end and its driving me nuts!
I was going to try the wire trick, but it requires stock rom. I had backed up the stock rom but it won't load. I downloaded 2 PD15IMG.zip files but neither of them will load, recovery says "Bad" when I try to run the .zip files. Did a little research. I think I need to do it via fastboot for the PD15IMG.zip files. Trying to figure that out now. Warnings seem pretty dire about trying to do it on a non-stock rom
This is getting above my head but I'm working my best to figure it out. Worst comes to worse I'll just have to order a new phone! I hate to be the novice that ends up being a PITA, as I've dealt with them plenty on the car forums I'm active on. I'd like to apologize up front for being "that guy".
Click to expand...
Click to collapse
Load the pd15img.zip on your sd card and boot to your bootloader. It should detect the file on your card and ask if you want to flash it. Just follow the directiins it gives you
Edit: actually should be pd59img not 15
Sent from my SGH-T889 using Tapatalk 2