Related
This should help a few people out. Thanks to dfgged, we now have stock Odin files. There has been minimal testing of these, but they do in fact work to help recover. It won't fix everything, but if you had to go back to stock for warranty reasons, this would be better than having a really messed up ROM. Currently, I only have the System and Kernel. Both are untouched, minus the System dump being rooted, which was required to get the dump. Flash in Odin via the PDA button. I will also work on getting the rest of the usable images posted, and will post a CWM flashable package for stock, stock deodexed, and debloated then as well for DJ20.
System
Kernel
So I flashed dl09 followed by both above and I'm still stuck at the Samsung screen...wtf?
If you have a Fascinate, why did you flash these files? If you have a Continuum, why did you flash DL09?
imnuts said:
If you have a Fascinate, why did you flash these files? If you have a Continuum, why did you flash DL09?
Click to expand...
Click to collapse
I have both. I needed to try something on the continuum with prl and modem modification to try and overwrite vzw pop settings. But now nothing on the continuum. And it doesn't appear to be any Odin backs...
jenisiz said:
I have both. I needed to try something on the continuum with prl and modem modification to try and overwrite vzw pop settings. But now nothing on the continuum. And it doesn't appear to be any Odin backs...
Click to expand...
Click to collapse
so you flashed verizon odin files on your continuum? that wasnt going to end well
nitsuj17 said:
so you flashed verizon odin files on your continuum? that wasnt going to end well
Click to expand...
Click to collapse
No kidding...but it has been confirmed that dl09 works on the continuum...however for somereason, not so well on mine.
jenisiz said:
No kidding...but it has been confirmed that dl09 works on the continuum...however for somereason, not so well on mine.
Click to expand...
Click to collapse
By confirmed do you mean "not at all confirmed"?
jenisiz said:
No kidding...but it has been confirmed that dl09 works on the continuum...however for somereason, not so well on mine.
Click to expand...
Click to collapse
where was it confirmed? i dont recall ever seeing that
jenisiz said:
No kidding...but it has been confirmed that dl09 works on the continuum...however for somereason, not so well on mine.
Click to expand...
Click to collapse
The only thing that is confirmed to work as far as going from the Fascinate to the Continuum are the radios. If you get a botched up baseband, you can flash a Fascinate radio to a Continuum (and probably the other way if we had Continuum radios, but we don't), but that is the only thing that is cross-compatible that I've seen. Maybe you could get most of a ROM to work as well, but you'd loose your softkeys as well as the ticker functionality if you didn't have the proper framework files.
nitsuj17 said:
where was it confirmed? i dont recall ever seeing that
Click to expand...
Click to collapse
Search...dl09 has been confirmed. I'd post links but its to much trouble on my phone. But I attempted and no go...still searching for ideas. Confused why I would be held up by the radio?
jenisiz said:
Search...dl09 has been confirmed. I'd post links but its to much trouble on my phone. But I attempted and no go...still searching for ideas. Confused why I would be held up by the radio?
Click to expand...
Click to collapse
I just searched the entire Continuum sub-forum, and there is no mention anywhere that DL09 from the Fascinate works on the Continuum. The only thing I found close was mention that the DL09 baseband works, but there is no mention of anyone using DL09 on their Continuum. I even searched at Android Central and Android Forums, and no one anywhere has flashed a full DL09 that is recorded at XDA/AC/AF.
imnuts said:
I just searched the entire Continuum sub-forum, and there is no mention anywhere that DL09 from the Fascinate works on the Continuum. The only thing I found close was mention that the DL09 baseband works, but there is no mention of anyone using DL09 on their Continuum. I even searched at Android Central and Android Forums, and no one anywhere has flashed a full DL09 that is recorded at XDA/AC/AF.
Click to expand...
Click to collapse
That's what I attempted? I flashed the band and no boot...not complete dl09
Edit: You and I actually talked about it through pm.
Flashing the modem doesn't cause the phone to stop booting, so something else is likely the problem.
jenisiz said:
That's what I attempted? I flashed the band and no boot...not complete dl09
Edit: You and I actually talked about it through pm.
Click to expand...
Click to collapse
you made it sound like you flashed the dl09 rom, thats where i was coming from on my comments
Nope...not the rom lol. I was going off of a convo in pm with nuts. I wish it was that obvious though...
hi everyone..
having an issue with this recovery...i have used this file twice before to recover the wife's continuum.. however last night it wouldn't work.. meaning, it flashes in ODIN just fine, gives me "success" however when the phone reboots, nothing has flashed and it is exactly the same as before flashing..
i have red cwm on the phone, and have tried clearing everything (cache, dalvik, data/factory reset, mounted all partitions and wiped those) i also tried flashing the kernel which seemed to work.. however it still will not reset to factory.. i used the same file i have on my computer that worked 2x before, and even re-downloaded the one posted here and tried that as well.. nothing..
it appears for some reason the phone accepts the connection and/or files, but won't "run" them if that makes any sense...
i also have 2 nandroid backups that i tried to restore, which is the factory setup..and it hangs at the samsung logo (i gave up after 20 mins and pulled battery) .. and the second nandroid takes me to the deodexed/basic rom that was built here.. which works but has issues..
im trying to get back to complete stock.. i have also tried using superoneclick to unroot, but the program gives me an "error 22" when pushing rage, and locks up..
i have tested adb, and it will connect to phone, but NOTHING can be pushed or pulled using the commands..
im lost here.. anyone have any ideas?
Did you convert the partition with voodoo?
Sent from my SCH-I400 using XDA Premium App
trailblazer101 said:
Did you convert the partition with voodoo?
Sent from my SCH-I400 using XDA Premium App
Click to expand...
Click to collapse
thanks for the reply sir..
i did not convert to voodoo...however i will check that in the voodoo section just to be certain its not toggled..im very familiar with voodoo, as i ran it on my fascinate for a long time .. i am using factory cable as well.. i will edit the post if it comes to fruition that it did..i never flashed a kernel - unless the one with the ROM here was voodoo..but i dont remember hearing sexy lady telling me anything when i flashed it
this is SO frustrating..it worked 2x before.. im assuming something is borked with r/w somewhere..but i havent a clue where to look to change it..
it boots to blue recovery, run update.zip to red..
under mounts and storage (that i cleared all on before) it currently reads all mounted except /dbdata which is unmounted..
Lmao, sexy lady...
When I get home, log into the Continuum irc channel, and lets see if we can't straighten you out
Sent from my SCH-I400 using XDA Premium App
any chance we can have the OP links updated, please, i tried downloading the files but links are broken
So I flashed Skyraider tonight, wiped data, installed the ROM, and booted up the phone. I was halfway through setting up my Google account when the phone froze and rebooted. Except, it didn't boot back up. It did the "vibrate five times and flash the LED" thing. Didn't think it was a big deal, so I pulled the battery, tried to boot it back up. But it does the same thing.
I can get into the hboot menu, and if the phone is plugged into the computer, it'll boot up into Skyraider, but it can't read the SD card or the internal storage. So, essentially, a pretty screwy phone. I also cannot boot back into recovery. It just does the vibrating thing when I try. My computer doesn't detect the SD card or storage, either. (The SD card is fine, though. I put it in another phone and everything is still there.)
I have no idea what happened with it. I don't know if this is some random hardware damage, or if I should find an RUU and try to fix it or what.
I've had the worst luck with phones these past few weeks.
Any suggestions?
What version of CM Recovery do you have?
I would go back to stock and redo everything again. Download this file
http://www.fourty.net/~berzerker/stockstuff/PB31IMG_3.26.605.1_RUU.zip
Rename it PB31IMG.zip and put it on the root of your SD card, boot into the bootloader and let the update run its course. This will bring you back to a completely stock 2.2. From there you can re-root and do as you please.
I was on CW 2.5.1.2. But everytime I try to get into the recovery, the phone just vibrates five times and the LED flashes green. I'm also not sure that hboot is seeing my SD card. I'm going to try it, though.
Here is the RUU if you need it
http://shipped-roms.com/index.php?category=android&model=Incredible
The bottom one on that page is the Stock 2.2 build.
g00s3y said:
Here is the RUU if you need it
http://shipped-roms.com/index.php?category=android&model=Incredible
The bottom one on that page is the Stock 2.2 build.
Click to expand...
Click to collapse
I appreciate it, but hboot isn't recognizing the SD card.
I'm really thinking there's some hardware damage.
godsmacked4653 said:
I appreciate it, but hboot isn't recognizing the SD card.
I'm really thinking there's some hardware damage.
Click to expand...
Click to collapse
I'm not sure if it works, but can you boot into hboot and run the RUU from there and update. I don't think you need to have a working SD Card in order to do that, but I could be wrong. At least then it will be stock and no worries if you take it to verizon.
g00s3y said:
I'm not sure if it works, but can you boot into hboot and run the RUU from there and update. I don't think you need to have a working SD Card in order to do that, but I could be wrong. At least then it will be stock and no worries if you take it to verizon.
Click to expand...
Click to collapse
Do you mean running the Windows RUU? I tried that last night, but it could never find the device. ADB recognizes it, though, so idk what the problem was.
godsmacked4653 said:
Do you mean running the Windows RUU? I tried that last night, but it could never find the device. ADB recognizes it, though, so idk what the problem was.
Click to expand...
Click to collapse
If you have the unrevoked USB drivers installed I believe that is what causes it. You have to have the "stock" drivers for the phone installed on the PC for it to work, that was a problem I was having when trying to run the RUU.
g00s3y said:
If you have the unrevoked USB drivers installed I believe that is what causes it. You have to have the "stock" drivers for the phone installed on the PC for it to work, that was a problem I was having when trying to run the RUU.
Click to expand...
Click to collapse
I do have the stock drivers. I used unrevoked on Linux, and I've tried the RUU in Windows. But still no go.
I'm probably just going to take it up to Verizon today. If it can't boot, they really can't see that I've changed anything, right?
very true, good luck
g00s3y said:
very true, good luck
Click to expand...
Click to collapse
yes, good luck let us know ho it goes....
Kent_Davis said:
yes, good luck let us know ho it goes....
Click to expand...
Click to collapse
The sales rep looked at it for two minutes, and they're overnighting another Incredible to me.
So on one hand, I'm pretty happy about how easy it was.
On the other hand, I'd rather keep the AMOLED screen.
Does anybody know if I'm going to get a refurb, or will I get a new SLCD model?
If you had AMOLED first and they give you an SLCD, you can ***** at them and they have to give you an AMOLED one. Cuz that's what you payed for.
Sent from my ADR6300 using XDA App
dpwhitty11 said:
If you had AMOLED first and they give you an SLCD, you can ***** at them and they have to give you an AMOLED one. Cuz that's what you payed for.
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
^ that. I just had to have a new one sent to me, its coming today. When I called tech support I asked them about what one I would be getting. They said that because I bought an AMOLED, I would be getting an AMOLED replacement.
g00s3y said:
^ that. I just had to have a new one sent to me, its coming today. When I called tech support I asked them about what one I would be getting. They said that because I bought an AMOLED, I would be getting an AMOLED replacement.
Click to expand...
Click to collapse
Yep. I got my replacement today. It's an AMOLED. As far as I can tell, all the hardware is working like it should.
This is probably the easiest time I have EVER had with Verizon.
But for future reference, five vibrations + blinking green LED = replacement.
I had same problem yesterday, five vibr.+ green blinks, but I had access into bootloader. I decided to reflash stock rom. Finally fixed problem
Sent from my ADR6300 using XDA Premium App
So my USB port on my Epic is messed up. It charges just fine but it wont connect to the computer. So I want to unroot my phone so I can take it into Sprint.
I haven't been able to find a method for unrooting the phone with out using a USB cord though. I was wondering if it was possible or not.
Thanks,
Daniel
Just flash the stock rom in .zip form and you'll be good to go, Sprint reps aren't going to look for a custom recovery.
Well the thing I was worried about is if they noticed that I was on 2.1 still and tried to update it to the latest one. It would obviously fail.
Is this an original ROM that would work? http://forum.xda-developers.com/showthread.php?t=786266
I will give you a link for stock EC05, what are you running now?
Well, actually I guess I am running just the stock 2.1 rom now that I think about it. I never got around to flashing a custom rom (was trying to a few weeks ago and realized the usb stopped working). But I do have several applications installed that require super user. So do you think I could just remove those and no one at sprint would really notice?
Thanks,
Daniel
You should be fine, I'm assuming you don't have a custom kernel, boot animation, or any modification on the stock Rom, right?
Nope never got around to any of that. Okay well I will see how it goes then. Thanks for your help.
edit: dumb question but how do I uninstall the root user application that manages the su permissions? It is only app left that shows it is rooted.
pierce71588 said:
Nope never got around to any of that. Okay well I will see how it goes then. Thanks for your help.
edit: dumb question but how do I uninstall the root user application that manages the su permissions? It is only app left that shows it is rooted.
Click to expand...
Click to collapse
The sdx stock app removal tool should work for that. Superuser.apk is kept in the same place as the other system apps
Sent from my SPH-D700 using XDA Premium App
Sweet! Thanks guys for all of the help! Hopefully I can get the USB fixed now!
Did you try a different cord? Stock sammy cords are known to be crap.
Ya I have tried different cords as well as different computers. Plus I know a few other people with Epics and their's have no issue at all.
The whole process is pretty simple on what I have done. I will explain my situation here and my question that has got be baffled.
So it all started about two weeks ago, where I was flashing LiquidSmooth on my phone. I had a Touch-type CWM. It isn't mega old but it's pretty old for CWM, I haven't updated in a while (as i've seen there are updates to recent ones).
Anywho, I did a complete wipe, used the darkside wipe, alongside with the darkside cache wipe.
I think this was my fault, so please correct me anyone if I am wrong here. I accidentally hit "reboot phone" instead of "reboot bootloader"
I got a permabrick from this whole ordeal. It was a permabrick because It said QHSUSB_DLOAD in the device manager, looking this up further confirmed my reasoning. I didn't want to jtag because that invovles removing the phone to pieces and soldering on wires etc. etc.
So I resorted to send it out to Samsung.
All is well when it came back. I made sure this time the whole phone was setup properly.
So I use Odin install for CWM and SU was installed via CWM. I install an older version of CWM (non-touch, i believe 1st revision as i've posted in one of the threads).
I kept stock ROM, everything was working okay and suddenly, KERPLUNK, it went back into permanent brick after I deleted cache partition, dalvik cache, and battery cache wipe. I didn't do fix permissions or anything, just hit reboot afterwards.
This is a super head scratcher here..... Anyone know where I went wrong?
Any insight here is greatly appreciated! :good:
P.S. I am now sending in my phone TWICE to Samsung for repairs.
If you are on the most up to date CWM, do not use the scripts. They are no longer needed, and will cause problems( hard brick though, never heard of) The second time, im stumped. I suggest go to TWRP and ditch the scripts. Latest TWRP does not need it
LoopDoGG79 said:
If you are on the most up to date CWM, do not use the scripts. They are no longer needed, and will cause problems( hard brick though, never heard of) The second time, im stumped. I suggest go to TWRP and ditch the scripts. Latest TWRP does not need it
Click to expand...
Click to collapse
I finally jumped in the water and flashed twrp! Yay!
Sent from my SAMSUNG-SGH-T989 using xda premium
All the steps you say you did don't point to a brick. But one thing caught my eye! You said you were flashing liquidsmooth? What File did you flash? Did it have Hercules in the name? Because if it didn't then it's not for our phone.. I only ask because a lot of other people made that mistake
Sent from my SGH-T989 using xda premium
rymanh said:
All the steps you say you did don't point to a brick. But one thing caught my eye! You said you were flashing liquidsmooth? What File did you flash? Did it have Hercules in the name? Because if it didn't then it's not for our phone.. I only ask because a lot of other people made that mistake
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
great call on that I had to educate a few users that the d2tmo is not for our phone but indeed the S3. Good catch on your part and it sounds like user error as well
LoopDoGG79 said:
If you are on the most up to date CWM, do not use the scripts. They are no longer needed, and will cause problems( hard brick though, never heard of) The second time, im stumped. I suggest go to TWRP and ditch the scripts. Latest TWRP does not need it
Click to expand...
Click to collapse
Could you please educate me with a link referring to what TWRP is? Sorry, i'm still fairly new to the scene and all i've ever been educated upon is CWM.
suaverc118 said:
I finally jumped in the water and flashed twrp! Yay!
Sent from my SAMSUNG-SGH-T989 using xda premium
Click to expand...
Click to collapse
Nice! What is TWRP and how is it like?
rymanh said:
All the steps you say you did don't point to a brick. But one thing caught my eye! You said you were flashing liquidsmooth? What File did you flash? Did it have Hercules in the name? Because if it didn't then it's not for our phone.. I only ask because a lot of other people made that mistake
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
I've flashed the hercules ROM. I know this for sure because Liquidsmooth was working, it was extremely glitchy (playing games gave me pixelated actions sometimes, and using something like gameCIH/Game Guardian was unworkable). So i decided to ditch it and was getting ready to flash Jedi Mind Trick.
After the whole hard bricking ordeal, I decided to stick to stock rom, and even on that, I just flashed CWM and SU ONLY. Rebooted, and deleted the cache's (like i've posted to you) with absolutely no success. It baffled me that I bricked the phone AGAIN too!
playya said:
great call on that I had to educate a few users that the d2tmo is not for our phone but indeed the S3. Good catch on your part and it sounds like user error as well
Click to expand...
Click to collapse
Yes..... there is something wrong, i feel it is a user error also, but i'm very unsure where to even start
Once again, all of your insight is well appreciated! I just do not want to hardbrick my phone AGAIN and have to send it to Samsung. I am not allowed to even think of a replacement because this was a b-day present a year or two ago from my fiance.
You say that it is bricked again. Do you mean by that, that you cannot get into recovery?
Sent from my SAMSUNG-SGH-T989 using xda premium
XxGoKoUxX said:
Could you please educate me with a link referring to what TWRP is? Sorry, i'm still fairly new to the scene and all i've ever been educated upon is CWM.
Nice! What is TWRP and how is it like?
I've flashed the hercules ROM. I know this for sure because Liquidsmooth was working, it was extremely glitchy (playing games gave me pixelated actions sometimes, and using something like gameCIH/Game Guardian was unworkable). So i decided to ditch it and was getting ready to flash Jedi Mind Trick.
After the whole hard bricking ordeal, I decided to stick to stock rom, and even on that, I just flashed CWM and SU ONLY. Rebooted, and deleted the cache's (like i've posted to you) with absolutely no success. It baffled me that I bricked the phone AGAIN too!
Yes..... there is something wrong, i feel it is a user error also, but i'm very unsure where to even start
Once again, all of your insight is well appreciated! I just do not want to hardbrick my phone AGAIN and have to send it to Samsung. I am not allowed to even think of a replacement because this was a b-day present a year or two ago from my fiance.
Click to expand...
Click to collapse
Flash this in recovery, reboot recovery, and you will have TWRP!!
TWRP 2.3.1.1
DM_Sledge said:
You say that it is bricked again. Do you mean by that, that you cannot get into recovery?
Sent from my SAMSUNG-SGH-T989 using xda premium
Click to expand...
Click to collapse
Yes, it is perma-bricked, meaning the only method of fixing the brick is jtagg'ing
Upon plugging it into device manager, I get the prompt "QHSUSB_DLOAD" and phone doesn't even boot on no matter what combinations I make.
LoopDoGG79 said:
Flash this in recovery, reboot recovery, and you will have TWRP!!
TWRP 2.3.1.1
Click to expand...
Click to collapse
Thank you LoopDo, I will do this after I get my phone home again.
I have this phone, and none of the steps you listed would brick the device. Even with no ROM on the phone, you should still be able to get into recovery.
Is there something you aren't telling us?
Sent from my Galaxy Nexus using xda premium
Nope, wouldn't be a reason why I would lie because then the problem will never be resolved.... I'm kind of nervous on reflashing ONE more time after the phone comes home again....
The phone has been fixed once AGAIN, and it is in the process of being shipped back to me.
Phone will be home Wednesday and I will give it ONE more try
Wish me luck!
P.S. my PC has been glitchy lately, so that MAY or MAY NOT contribute to the permabrick, then again the brick doesn't happen until I flash stuff via CWM.
P.S.S. I've since re-installed Win 7 again, it hasn't been glitchy since
XxGoKoUxX said:
Nope, wouldn't be a reason why I would lie because then the problem will never be resolved.... I'm kind of nervous on reflashing ONE more time after the phone comes home again....
The phone has been fixed once AGAIN, and it is in the process of being shipped back to me.
Phone will be home Wednesday and I will give it ONE more try
Wish me luck!
P.S. my PC has been glitchy lately, so that MAY or MAY NOT contribute to the permabrick, then again the brick doesn't happen until I flash stuff via CWM.
P.S.S. I've since re-installed Win 7 again, it hasn't been glitchy since
Click to expand...
Click to collapse
You most likely flashed the Wrong Liquidsmooth ROM (incompatible Kernel), and it hard bricked the phone. It happened to me the same way, and I had to send it in for JTAG.
I have bricked my phone installing the Liquidsmooth ROM too. I downloaded the wrong ROM, though. The thread should have a big ****in warning to double check the ROM you are about to download, otherwise your phone is a toast. There were more people who bricked their phones by installing the Liquidsmooth.
Well, I got it back from the warranty and the phone looks good. Installed that Liquidsmooth again and played for a day. Tried other JB ROMs. Most of them are OK in terms of battery life and smoothness, but there is something wrong with the signal. People always say my voice isn't clear. I got tired of all this BS and testing new ROMs and went to back to ICS and won't look back, not anytime.
Don't use darkside scripts, btw. You don't need that anymore.
I'd like to say thank you for everyone's patience. All of your insight is more than helpful!
DroidDonX said:
You most likely flashed the Wrong Liquidsmooth ROM (incompatible Kernel), and it hard bricked the phone. It happened to me the same way, and I had to send it in for JTAG.
Click to expand...
Click to collapse
I might have, but the one i downloaded (which is still on the phone's memory card) is a hercules ROM. Either way on my second try there was a hard brick also, in return of which I had to resend it in. The second try was just simply: Odin---->CWM---->Root---->SU---->wipe cache partition+fix permissions+wipe dalvik cache via CWM (not the super scripts).
cipsaz said:
I have bricked my phone installing the Liquidsmooth ROM too. I downloaded the wrong ROM, though. The thread should have a big ****in warning to double check the ROM you are about to download, otherwise your phone is a toast. There were more people who bricked their phones by installing the Liquidsmooth.
Well, I got it back from the warranty and the phone looks good. Installed that Liquidsmooth again and played for a day. Tried other JB ROMs. Most of them are OK in terms of battery life and smoothness, but there is something wrong with the signal. People always say my voice isn't clear. I got tired of all this BS and testing new ROMs and went to back to ICS and won't look back, not anytime.
Don't use darkside scripts, btw. You don't need that anymore.
Click to expand...
Click to collapse
Thanks again for your insight I think i'm done with flashing for a little bit for now.... I kind of want as factory of a JB Rom as possible. :good:
If anyone has any idea where I can get that, please let me know as my Stock ICS is a bit laggy at times, with the facial recognition system, it lags even worse!
rymanh said:
All the steps you say you did don't point to a brick. But one thing caught my eye! You said you were flashing liquidsmooth? What File did you flash? Did it have Hercules in the name? Because if it didn't then it's not for our phone.. I only ask because a lot of other people made that mistake
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
that just happened to me today with liquid smooth. i had to unroot, flash stock, and start over. im pretty sure i got it from goo.im under hercules. unfortunate mislabeling? oh yeah, and if your phone shows anything other than nothing, youre not hard bricked. thats why its called Hercules, i think. ive been soft bricked so many times from dumb **** like. ****ing with the governors and all that **** cm gives you the option to do when there aint even a 1080p camera that works fully = / lol <3 Cm I Love Yew!! But yeah, odin will set you free!!!
I tried to install a ROM that must have not downloaded properly now my Nexus does not boot at all. It doesn't even go to the Google screen, it's just plainly black. The worst part is that it happened last week and I thought the phone had just broken so I got a hardware swap at Best Buy but now I realize it must have been the ROM. I don't want to go back to Best Buy this quickly (not even 24 hours later...) Does anyone know how I might fix it?
hulslanderam said:
I tried to install a ROM that must have not downloaded properly now my Nexus does not boot at all. It doesn't even go to the Google screen, it's just plainly black. The worst part is that it happened last week and I thought the phone had just broken so I got a hardware swap at Best Buy but now I realize it must have been the ROM. I don't want to go back to Best Buy this quickly (not even 24 hours later...) Does anyone know how I might fix it?
Click to expand...
Click to collapse
If it was a faulty download the rom wouldn't have installed properly, what steps did you take in installing the from. Are you able to boot into recovery?
Sent from my Galaxy Nexus using xda app-developers app
FIXED
sensation lover said:
If it was a faulty download the rom wouldn't have installed properly, what steps did you take in installing the from. Are you able to boot into recovery?
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
I installed a kernel too, both from CWM. Maybe it was the kernel. and no, I couldn't get to recovery but I managed to fix it. I can't post links because I'm a new user but it involved installing omap drivers and running a batch file of some sort that made it bootable. Even though the screen was totally black I guess the computer could still detect it with some work.
Awesome!
hulslanderam said:
I installed a kernel too, both from CWM. Maybe it was the kernel. and no, I couldn't get to recovery but I managed to fix it. I can't post links because I'm a new user but it involved installing omap drivers and running a batch file of some sort that made it bootable. Even though the screen was totally black I guess the computer could still detect it with some work.
Click to expand...
Click to collapse
Congrats! That's gotta feel good to resurrect a "dead" phone!
I've tried to use the OMAP flash to fix mine, but I still can't get into Odin mode (even tho the drivers and bat file seem to install successfully). If you have any tips, then please let me know.