Database Info

[Q] hey so i bricked my 3devo phone... what now?

solved i was flashing a rom, but i guess i didn't do a wipe or something, so now my sprint evo3d won't boot. when i power up, it shows the htc logo and thats all.
i can get into recovery(TWRP) and fastboot just fine, so what do i need to flash/wipe to fix this?
rooted htc method so unlocked with s-on hboot1.50
solution if anyone has the same problem:
reflashed my previous rom then was able to boot. now i am restoring and backing up like i should have

Did you make a nandroid backup?
Sent from my HTC_A510c using XDA App

nope i was that stupid

anyone? i kinda need my phone... could i flash the stock rom and kernal? or does anyone have a backup they could post or anything

3rdsurfer said:
anyone? i kinda need my phone... could i flash the stock rom and kernal? or does anyone have a backup they could post or anything
Click to expand...
Click to collapse
so many people and no help... LOL! it seems that you are soft bricked! no worries, flash the same ROM you had before the one you were trying to flash and you should then be fine! make nandroid and then flash the new ROM that you wanted happy flashing

ha i just had that thought of flashing my old rom myself. thanks for the second on that idea. ill do that if the file ever feels like copying....

PersianSphinx said:
so many people and no help... LOL! it seems that you are soft bricked! no worries, flash the same ROM you had before the one you were trying to flash and you should then be fine! make nandroid and then flash the new ROM that you wanted happy flashing
Click to expand...
Click to collapse
oh, and i forgot: Its rare to hard brick phones by just flashing ROMs, the worse thing to get is a bootloop like you got, usually. the way to get hard bricked is to flash a bad SPL, so interupt an SPL installation or flash a ROM with SPl and install it wrong or Radio, or in some phones, deleting or flashing the recovery wrong and then soft bricking, boot loop for sure then
---------- Post added at 12:36 AM ---------- Previous post was at 12:33 AM ----------
3rdsurfer said:
ha i just had that thought of flashing my old rom myself. thanks for the second on that idea. ill do that if the file ever feels like copying....
Click to expand...
Click to collapse
if your old rom doesnt copy, no problem just install a rom that works with your SPL and kernel and radio. damn HTC, why do they make it so hard? when i wanna flash my samsung, all i need to do is go to boot loader, fire up this program called odin, and odin does everything for me! get a samsung phone next time its better

yep that fixed it. so now my question is what was the problem? and more importantly how can i avoid this problem (yes i need to backup, i mean the brick)

<--- EDIT accidentally inserted this lol
3rdsurfer said:
yep that fixed it. so now my question is what was the problem? and more importantly how can i avoid this problem (yes i need to backup, i mean the brick)
Click to expand...
Click to collapse
If you're going to a new kernel, wipe the cache and dalvik cache. If you're going to a new version of the same ROM you're on, same thing unless stated otherwise. If you're going to a totally new ROM, wipe everything (obviously, minus your card) unless stated otherwise. If you're reflashing the same ROM you were on, you don't have to wipe unless you end up with a different kernel; then wipe cache and davlik cache.

3rdsurfer said:
yep that fixed it. so now my question is what was the problem? and more importantly how can i avoid this problem (yes i need to backup, i mean the brick)
Click to expand...
Click to collapse
I think you may have forgot to wipe data... or bad install maybe? you said you have problems copying the file... maybe bad copy?
---------- Post added at 12:53 AM ---------- Previous post was at 12:52 AM ----------
Product F(RED) said:
Click to expand...
Click to collapse
Y U mad man? chill out

PersianSphinx said:
I think you may have forgot to wipe data... or bad install maybe? you said you have problems copying the file... maybe bad copy?
---------- Post added at 12:53 AM ---------- Previous post was at 12:52 AM ----------
Y U mad man? chill out
Click to expand...
Click to collapse
Mad? I just gave you a straight-forward answer lol. I wasn't angry at all.
OH LOL I see. I somehow got the angry emote in there.

Product F(RED) said:
If you're going to a new kernel, wipe the cache and dalvik cache. If you're going to a new version of the same ROM you're on, same thing unless stated otherwise. If you're going to a totally new ROM, wipe everything (obviously, minus your card) unless stated otherwise. If you're reflashing the same ROM you were on, you don't have to wipe unless you end up with a different kernel; then wipe cache and davlik cache.
Click to expand...
Click to collapse
i knew about the dalvik and cache, but what else do i need to wipe if i am switching roms? or do i wipe everything then backup what i need?

3rdsurfer said:
i knew about the dalvik and cache, but what else do i need to wipe if i am switching roms? or do i wipe everything then backup what i need?
Click to expand...
Click to collapse
well im not 100% sure about your phone, but in the G1 forum the devs suggest a complete /system wipe... also factory reset before and after flashing is a very good idea

ok thanks all i'll do all that from now on.

3rdsurfer said:
i knew about the dalvik and cache, but what else do i need to wipe if i am switching roms? or do i wipe everything then backup what i need?
Click to expand...
Click to collapse
If you're switching ROMs and you wanna be able to get everything back exactly like it was, use Nandroid to backup/restore. It takes a full backup of everything in your phone's memory: The ROM, the apps and their data, etc.
If you want to be able to backup and restore apps and data between different ROMs, use Titanium Backup. But be careful because in some cases restoring app data on 2 ROMs with different bases can cause the ROM to act funky.

Switching from one ROM to another

I'm currently using SkyRocket ICS (2.3.5 Gingerbread)
http://forum.xda-developers.com/showthread.php?t=1377087
and everything is awesome but my phone signal, att logo, wifi, notifications, doesnt appear on the top of the phone so i want to try out another ROM. This one in particular, NexusMod 4
http://forum.xda-developers.com/showthread.php?t=1426590
Do I just flash the new ROM in CWM recovery like I did to get my first ROM? Or is there more to it?
Thanks!

That's a problem on your end, that rom is flawless and you flashed it wrong

This is the guide I used to flash the ROM
http://www.traemcneely.com/2011/12/27/install-custom-rom-at-ciq-removed-short-review-instructions/
I compared it with ones on xda and it was identical but more noob friendly which I preferred. I dont know what I couldve possibly done wrong.. I followed EVERYTHING step by step. I love everything about this ROM except this one major annoyance.

penance said:
This is the guide I used to flash the ROM
http://www.traemcneely.com/2011/12/27/install-custom-rom-at-ciq-removed-short-review-instructions/
I compared it with ones on xda and it was identical but more noob friendly which I preferred. I dont know what I couldve possibly done wrong.. I followed EVERYTHING step by step. I love everything about this ROM except this one major annoyance.
Click to expand...
Click to collapse
It was a bad flash or bad download. Try to redownload and check the md5, then simply reflash it making sure to follow instructions and wipe properly

Sorry, but may I ask what an md5 is? And the specific ROM I want
http://forum.xda-developers.com/showthread.php?t=1377087
doesn't provide instructions, at least that I know of so I followed this guide
http://www.traemcneely.com/2011/12/27/install-custom-rom-at-ciq-removed-short-review-instructions/
Only problem I can think of that I made was flashing the RC 6.75 Stock ROM and then wiping cache partition and flashing the 7.4 Stock Nonewipeupdate right afterwards which is exactly what the guide asked for. Was I suppose to reboot after flashing the stock RC 6.75 ROM before flashing the 7.4 Stock Nonewipeupdate?

penance said:
Sorry, but may I ask what an md5 is? And the specific ROM I want
http://forum.xda-developers.com/showthread.php?t=1377087
doesn't provide instructions, at least that I know of so I followed this guide
http://www.traemcneely.com/2011/12/27/install-custom-rom-at-ciq-removed-short-review-instructions/
Only problem I can think of that I made was flashing the RC 6.75 Stock ROM and then wiping cache partition and flashing the 7.4 Stock Nonewipeupdate right afterwards which is exactly what the guide asked for. Was I suppose to reboot after flashing the stock RC 6.75 ROM before flashing the 7.4 Stock Nonewipeupdate?
Click to expand...
Click to collapse
You need to flash the base and boot it before flashing an update, like you said.
Before flashing any rom this is a general procedure
wipe data/factory reset 3x
Wipe cache 3x
wipe dalvik cache 3x
format system 3x
flash radio if need be
flash rom
reboot
dont touch phone for at least 10 mins
set up basics
if it has an update
reboot to cwm
wipe cache 3x
wipe dalvik cache 3x
flash update
reboot

Okk. ONE LAST question. The SkyRocket ICS (2.3.5 Gingerbread) ROM I'm using doesn't have or provide a radio file to DL on the page which I linked earlier. Does that imply that this particular ROM doesn't need it? Or am I suppose to find a radio to flash before flashing the ROM and update?
Thanks alot for your help/advice!! Really appreciate it!

penance said:
Okk. ONE LAST question. The SkyRocket ICS (2.3.5 Gingerbread) ROM I'm using doesn't have or provide a radio file to DL on the page which I linked earlier. Does that imply that this particular ROM doesn't need it? Or am I suppose to find a radio to flash before flashing the ROM and update?
Thanks alot for your help/advice!! Really appreciate it!
Click to expand...
Click to collapse
In about phone, what does it say for baseband? Kj2 is the 2.3.5 stock radio
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2

If the radio you're using is working and you're flashing from gb to gb, you shouldn't have to worry about the radio. You'll still have the same one. Radios flash separately from roms. I don't think you'll NEED to flash a new radio unless you change to an ICS rom.
Sent from my SAMSUNG-SGH-I727 using xda premium

Android version 2.3.6
Baseband version I727UCKJ2
Kernal version 2.6.35.11+
Build number Sky-ICS RC7.4 Stock
When I purchased my phone and after I rooted it, I was v2.3.5 but after I flashed my first ROM (which is my current ROM) the android version changed to v2.3.6. So if KJ2 is the stock radio for v2.3.5 is there a possibility my problem of not having the att logo and wifi signal on the top of my phone due to not having the correct radio for this ROM? or for v2.3.6 in general? Or is it from what you said earlier, my flashing process was wrong? Or a mixture or not having the correct radio and flashing wrong?

boobah204 said:
If the radio you're using is working and you're flashing from gb to gb, you shouldn't have to worry about the radio. You'll still have the same one. Radios flash separately from roms. I don't think you'll NEED to flash a new radio unless you change to an ICS rom.
Sent from my SAMSUNG-SGH-I727 using xda premium
Click to expand...
Click to collapse
Well, I don't really know whether or not the radio is working. I suppose in my case it is working since I am able to recieve and make calls, text, and go on the web. However, I am unable to see the att logo, wifi/cell signal on the top of my phone. I don't know if this problem has anything to do with the radio though. Sorry for my lack of understanding..
I'm assuming the problem is more my fault in terms of not flashing correctly. I have no idea whether or not I need a separate radio for this ROM.

Sounds like a systemui /frame work problem
Wipe data/cache/dalvik
Reflash
Fully boot
Shutdown
Flash update
Wipe dalvik
Reboot.

The signals at the top wouldn't be affected by he radio. You would most likely get them back if you reflashed your from or flashed another. As long as it's a 2.3.5 or 2.3.6. And also follow the instructions (usually pretty standard, wipe data factory reset a few times, wipe cache partition, advanced, wipe dalvik cache a few times, go back, mounts and storage, format system a few times. Then install zip from SD card) oh and always backup first and make sure you can restore the backup. But yeah if you can make calls and use internet, your radio should be OK.
Sent from my SAMSUNG-SGH-I727 using xda premium

silver03wrx said:
Sounds like a systemui /frame work problem
Wipe data/cache/dalvik
Reflash
Fully boot
Shutdown
Flash update
Wipe dalvik
Reboot.
Click to expand...
Click to collapse
Thanks! That's what I figured the problem to be JK.
I'll give it go and hope for the best this time around.

boobah204 said:
The signals at the top wouldn't be affected by he radio. You would most likely get them back if you reflashed your from or flashed another. As long as it's a 2.3.5 or 2.3.6. And also follow the instructions (usually pretty standard, wipe data factory reset a few times, wipe cache partition, advanced, wipe dalvik cache a few times, go back, mounts and storage, format system a few times. Then install zip from SD card) oh and always backup first and make sure you can restore the backup. But yeah if you can make calls and use internet, your radio should be OK.
Sent from my SAMSUNG-SGH-I727 using xda premium
Click to expand...
Click to collapse
Alright thanks alot for your guide and clarification. Still learning day by day

penance said:
Alright thanks alot for your guide and clarification. Still learning day by day
Click to expand...
Click to collapse
Just do this and skip the radio step
xcrazydx said:
You need to flash the base and boot it before flashing an update, like you said.
Before flashing any rom this is a general procedure
wipe data/factory reset 3x
Wipe cache 3x
wipe dalvik cache 3x
format system 3x
flash radio if need be
flash rom
reboot
dont touch phone for at least 10 mins
set up basics
if it has an update
reboot to cwm
wipe cache 3x
wipe dalvik cache 3x
flash update
reboot
Click to expand...
Click to collapse

Not sure the deal with your cell/wifi signals not showing in your status bar, but, the carrier logo could have been removed in the ROM itself.

I would try out the nexusmod zero ics I'm running it now and I like it a lot more than nexus 4. Also when I went from the from you are on now I had to do a super wipe before I could get the ics rom to work without bootloop
Sent from my SAMSUNG-SGH-I727 using XDA

[Q] Speaker Phone broke?

I've been having a problem with phone calls putting them on speaker. The volume of the external speaker is comparable to the volume of the ear piece. This is only in calls, music and notifications seem to be fine. It was fine before I rooted, but seems to be goofed up on JB roms. I rooted with the brand new 2.20 root method. I tried things like Volume+ and nothing seems to make a difference. I've tried all the basic things like wiping cache/dalvick. What are the chances it's a bad device?

you already posted this in the roms thread. someone probably saw it so why make a thread? wipe and reflash. you also can't blame root because you flashed another rom. on first root, unlock, recovery flashing i always "fastboot erase cache", then wipe literally everything in twrp, then flash my rom. you could first try "fastboot erase cache" in bootloader then wipe cache/dalvik then fix permissions before doing the above and see if that fixes it.

DvineLord said:
you already posted this in the roms thread. someone probably saw it so why make a thread? wipe and reflash. you also can't blame root because you flashed another rom. on first root, unlock, recovery flashing i always "fastboot erase cache", then wipe literally everything in twrp, then flash my rom. you could first try "fastboot erase cache" in bootloader then wipe cache/dalvik then fix permissions before doing the above and see if that fixes it.
Click to expand...
Click to collapse
yes, i posted it there because at the time i thought the problem was specific to that rom (i think it started with the codename rom). but after being on more than one rom (i'm now on the jb build 4) i don't think it is. or it may be specific to jb roms. i'm not sure. i thought i would ask before i just go flashing away... i'm also wondering if anybody else is having this problem.
i followed you all the way till "fix permissions", is this another tab in twrp?

with all the changes right now with CM10 which is base for alot of jb roms its hard to determine the cause. unless you are using a jb aosp build before the kernel changes which is basically anything after 10/01 then you might have some unique issues.
fix permissions is under advanced

Speaking of kernels, I haven't gotten any kernels to successfully flash with either ROM. For instance rohans kernel to oc. Flashed it with his ROM. Won't take.
So basically what you're saying is wipe caches with fastboot, go into twrp, erase everything, reflash, then fix permissions?
Sent from my One X using xda app-developers app

ck4794 said:
Speaking of kernels, I haven't gotten any kernels to successfully flash with either ROM. For instance rohans kernel to oc. Flashed it with his ROM. Won't take.
So basically what you're saying is wipe caches with fastboot, go into twrp, erase everything, reflash, then fix permissions?
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
use the stock kernel that comes with your rom for now. reboot in to bootloader and "fastboot flash boot boot.img" the kernel(ie boot.img) from ur current rom. then run "fastboot erase cache" then boot into recovery. wipe cache/dalvik then go into advanced and fix permissions.
if that doesnt work then wipe everything and reflash your rom and gapps if its aosp rom, then rewipe cache/dalvik and reboot.

Didn't work, but sandy just knocked out the power so I think this can wait a while haha
Sent from my One X using xda app-developers app

ck4794 said:
Speaking of kernels, I haven't gotten any kernels to successfully flash with either ROM. For instance rohans kernel to oc. Flashed it with his ROM. Won't take.
So basically what you're saying is wipe caches with fastboot, go into twrp, erase everything, reflash, then fix permissions?
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
I respectfully suggest you stay away from custom kernel for now until you are a little more familiar with your device, especially if you're playing with jb/cm10 based roms stay with the kernel that came with. The devs will not support any issues that arise from flashing a custom kernel on top of a their roms.

Crappyvate said:
I respectfully suggest you stay away from custom kernel for now until you are a little more familiar with your device, especially if you're playing with jb/cm10 based roms stay with the kernel that came with. The devs will not support any issues that arise from flashing a custom kernel on top of a their roms.
Click to expand...
Click to collapse
i will definitely take this under consideration

DvineLord said:
use the stock kernel that comes with your rom for now. reboot in to bootloader and "fastboot flash boot boot.img" the kernel(ie boot.img) from ur current rom. then run "fastboot erase cache" then boot into recovery. wipe cache/dalvik then go into advanced and fix permissions.
if that doesnt work then wipe everything and reflash your rom and gapps if its aosp rom, then rewipe cache/dalvik and reboot.
Click to expand...
Click to collapse
did this and still a no go... no volume on speaker phone during a call. wiped everything and reflashed rom with stock kernel, wiped again, fixed permissions. all other volumes seem to be appropriate.

ck4794 said:
did this and still a no go... no volume on speaker phone during a call. wiped everything and reflashed rom with stock kernel, wiped again, fixed permissions. all other volumes seem to be appropriate.
Click to expand...
Click to collapse
relock bootloader and ruu...if that does not do it you have a hardware issue.

i'm not questioning your logic, but for my own knowledge can you explain this a little better for me? not the process but the reasoning? to my understanding an ruu basically strips the phone back to some previous state, depending on the ruu you chose, and reverts it back to stock. what purpose does re locking the bootloader serve here? would i need a new unlock code or would the unlock code i got from the first time i unlocked it still work?
also let me make sure i have this process down, relock, ruu, unlock, flash? am i missing any steps in there? like will i need to reflash my recovery?

ck4794 said:
i'm not questioning your logic, but for my own knowledge can you explain this a little better for me? not the process but the reasoning? to my understanding an ruu basically strips the phone back to some previous state, depending on the ruu you chose, and reverts it back to stock. what purpose does re locking the bootloader serve here? would i need a new unlock code or would the unlock code i got from the first time i unlocked it still work?
also let me make sure i have this process down, relock, ruu, unlock, flash? am i missing any steps in there? like will i need to reflash my recovery?
Click to expand...
Click to collapse
here is the logic.
1. you need to relock bootloader to run ruu
2. ruu bring you back to vanilla stock everything, allowing you to evaluate your hardware/software issue. If your speaker works it was some kind of corruption if doesn't it you know you have a hardware problem.
Unlock code stays the same.
That's also why you should always do a clean install/full wipe/factory reset when you experiment with different roms (aosp/sense)

Crappyvate said:
here is the logic.
1. you need to relock bootloader to run ruu
2. ruu bring you back to vanilla stock everything, allowing you to evaluate your hardware/software issue. If your speaker works it was some kind of corruption if doesn't it you know you have a hardware problem.
Unlock code stays the same.
Click to expand...
Click to collapse
thanks for being patient with me man, i appreciate it. i'll give this a go a little later this evening and post back results.

ck4794 said:
thanks for being patient with me man, i appreciate it. i'll give this a go a little later this evening and post back results.
Click to expand...
Click to collapse
good luck. :highfive:

[STOCK] AT&T RUU_Evita_UL_Cingular_US-1.85.502
am i ok to run this ruu even though i came from 2.20 when i rooted?

ck4794 said:
[STOCK] AT&T RUU_Evita_UL_Cingular_US-1.85.502
am i ok to run this ruu even though i came from 2.20 when i rooted?
Click to expand...
Click to collapse
http://dl3.htc.com/application/htc_o...s_08022012.exe

Crappyvate said:
http://dl3.htc.com/application/htc_o...s_08022012.exe
Click to expand...
Click to collapse
bad link

ck4794 said:
bad link
Click to expand...
Click to collapse
what...i just tested it ?? hold on
http://forum.xda-developers.com/showpost.php?p=29766409&postcount=3

Crappyvate said:
what...i just tested it ?? hold on
http://forum.xda-developers.com/showpost.php?p=29766409&postcount=3
Click to expand...
Click to collapse
i saw some where i think that this ruu would get me back to square one, unrooted. is there anything like that i should know about before i run this ruu? also i've never run an ruu, is it one of those i put it on my c: drive run it and it will do the work?

Help! Trying to revert to stock rooted from CM10

I upgraded to CM10 from the original OS and I am using the latest version to root my phone, I am using TWRP. Anyway, Everything worked fine, I rooted the phone, I upgraded to CM10. I want to go back to the original OS. I downloaded [ROM][8/3] - Stock Rooted AT&T 2.20.502.7 - Android 4.0.4 - Odex or De-Odex, I got the ODEX version, I flashed it to my phone but its just hangs at the HTC One X Splash screen with the red lettering. What am I missing here? I can get back into recovery and I backed up my old ROM just in case.

How long are you letting it hang for? Try 2 more power downs and power ons. The first few times it took about 5 min to load.

mgutierrez87 said:
How long are you letting it hang for? Try 2 more power downs and power ons. The first few times it took about 5 min to load.
Click to expand...
Click to collapse
It just shuts off and turns back on again, it basically loops. Did I download the wrong file maybe? Is there a specific ROM I need other than the one I mentioned earlier?

Boot into recovery and wipe your cache and dalvik cache again

mgutierrez87 said:
Boot into recovery and wipe your cache and dalvik cache again
Click to expand...
Click to collapse
Factory reset, wipe system, flash ROM, wipe cache and delvik.
Any time you go from non sense to sense or vise versa you have to wipe the system and factory reset.
Sent from my One X using xda app-developers app

This was the ROM that worked when i did it.
http://forum.xda-developers.com/showthread.php?t=1872842
---------- Post added at 04:53 AM ---------- Previous post was at 04:46 AM ----------
Myrder said:
Factory reset, wipe system, flash ROM, wipe cache and delvik.
Any time you go from non sense to sense or vise versa you have to wipe the system and factory reset.
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
He mentioned in another thread that he did those steps. The only other thing I would try is to flash the boot.IMG from the ROM you want to use

I still want to keep my phone rooted. This wont kill the root right?

No the ROM posted above is stock rooted
But if you made a backup as you said in the first post why are you not just restoring the backup?
Sent from my Nocturnalized One XL using Forum Runner

Basically where I am right now. I downloaded the original OS, by following instructions, I have managed to delete my backed up rom of CM10 that i backed up earlier. I was able to FLASH the OS I wanted, I flashed the boot.img file using fastboot. I restarted the phone and now its just stuck on the HTC Quietly Brilliant screen with the red lettering at the bottom. It doesn't restart or anything, it just hangs there. What am I missing here guys? ):

I'm going to install cm10 right now them go back to stock rooted and see what's up with this

There's no issues going back and forth. You probably flashed a bad ROM

yea, your most likely just doing it wrong. you need to do a full wipe and flash boot.img
answer: oh yea cant flash the stock rom using twrp 2.3.1.0 you will need to flash twrp 2.2.2.0 then flash stock rom. that is actually most likely your problem.

What hboot are you on? If you separately flashed boot.img from CM10 via fastboot, you might need to again separately flash the boot.img from the stock ROM. Also remember that the procedure employed to root 2.20 is substantially different from the root procedure to root the previous build of stock. Not sure what software you rooted, or whether this would pose a problem, but it's a consideration.
Another option is to just restore to stock via RUU and re-unlock, re-root, if nothing else works. Getting stuck on HTC splash screen sounds like a boot.img issue. Good luck.

DvineLord said:
answer: oh yea cant flash the stock rom using twrp 2.3.1.0 you will need to flash twrp 2.2.2.0 then flash stock rom. that is actually most likely your problem.
Click to expand...
Click to collapse
Really? Why is that?
Just curious, I haven't heard this before. Is this a known issue with flashing the 2.20 stock ROM? I haven't seen any cases of ROMs (stock rooted or otherwise) being sensitive to version of TWRP. At least not the case of having to use an older version (keeping TWRP updated is usually the recommendation).
Of course, just because I haven't heard of it, doesn't mean it didn't happen!

Did you fastboot flash boot boot.img?
Sent from my HOX running Cyanogenmod 10

redpoint73 said:
Really? Why is that?
Just curious, I haven't heard this before. Is this a known issue with flashing the 2.20 stock ROM? I haven't seen any cases of ROMs (stock rooted or otherwise) being sensitive to version of TWRP. At least not the case of having to use an older version (keeping TWRP updated is usually the recommendation).
Of course, just because I haven't heard of it, doesn't mean it didn't happen!
Click to expand...
Click to collapse
im assuming the age of the stock rooted would have conflicts with the new twrp. i have had problems with roms not flashing with newest twrp. it is also a known problem since twrp 2.3.1.0 release.

Problem Flashing Roms, Stuck on Boot logo(not bootloop)

Hi, I have a bit of a problem with my Mytouch 4g slide. I wanted to flash roms on my device for a while so i finally got around to trying it a few days ago. I have an unlocked bootloader, S-off, and CWR 5.0.2.7. I tried to flash CM 10 alpha 3, and CM 9.1 stable, but everytime I try, I get stuck on the Mytouch 4g Slide bootlogo. I even made sure that I was waiting long enough for the rom to flash. I left it on 10 hours over night, but it is still stuck on the boot logo. It is not in a boot loop, it just staying on that boot up screen. I have a recovery stock rom, so i can always nandroid restore to it, but I really want to be able to flash roms. I have tried everything, clear cache, clear Dalvik cache, factory reset, format /system. I have tried them all together and in every combo that makes sense. Please help!

goballistic23 said:
Hi, I have a bit of a problem with my Mytouch 4g slide. I wanted to flash roms on my device for a while so i finally got around to trying it a few days ago. I have an unlocked bootloader, S-off, and CWR 5.0.2.7. I tried to flash CM 10 alpha 3, and CM 9.1 stable, but everytime I try, I get stuck on the Mytouch 4g Slide bootlogo. I even made sure that I was waiting long enough for the rom to flash. I left it on 10 hours over night, but it is still stuck on the boot logo. It is not in a boot loop, it just staying on that boot up screen. I have a recovery stock rom, so i can always nandroid restore to it, but I really want to be able to flash roms. I have tried everything, clear cache, clear Dalvik cache, factory reset, format /system. I have tried them all together and in every combo that makes sense. Please help!
Click to expand...
Click to collapse
Did you do all them wipes before you flash the ROM like your supposed to? If you did a full wipe before flashing and it still don't boot you got a bad download.
Sent from my myTouch_4G_Slide using Tapatalk 2

im stupid
strapped365 said:
Did you do all them wipes before you flash the ROM like your supposed to? If you did a full wipe before flashing and it still don't boot you got a bad download.
Sent from my myTouch_4G_Slide using Tapatalk 2
Click to expand...
Click to collapse
Turns out that I do have s-on at the moment... I will get s-off asap. Crossing my fingers that that was the problem. And yes, I did wipe everything and do all those steps. I even downloaded the from twice. But, again, stupid me has s-on. I'll keep you posted.

goballistic23 said:
Turns out that I do have son at the moment... I will get s-off asap. Crossing my fingers that that was the problem. And yes, I did wipe everything and do all those steps. I even downloaded the from twice. But, again, stupid me has s-on. I'll keep you posted.
Click to expand...
Click to collapse
If you're still S-ON, that's the problem for sure. You can always fastboot flash the boot.img separate when flashing the ROMs if you don't feel like going to S-OFF.

HappyKhicken said:
If you're still S-ON, that's the problem for sure. You can always fastboot flash the boot.img separate when flashing the ROMs if you don't feel like going to S-OFF.
Click to expand...
Click to collapse
That's the method I use, and I haven't had any issues. I went through four ROMs during the week of New Year's.

Yay!!! S off!
HappyKhicken said:
If you're still S-ON, that's the problem for sure. You can always fastboot flash the boot.img separate when flashing the ROMs if you don't feel like going to S-OFF.
Click to expand...
Click to collapse
Got s-off, and running CM 10 for doubleshot like a boss! Thanks for all the help guys.