Develop Bugs

For all the flashers here for the T989

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!!!

[Q] Bricked my phone after flashing new Kernel on top of Cyanogenmod 10

Hello everyone,
As the title says I have a problem with my Galaxy Note II N7105 Lte (Vodafone, Germany)
I flashed the new cyanogenmod nightly one the phone and that was all well and good but then I made the mistake of flashing the Note2Core Kernel on top of if rendering my phone dead. My first Idea was to flash another Kernel on top, as I had some issues with the newest Note2Core Kernel (v3.06 OC) when I was still on my stock rom. I used the Perseus Kernel from this thread: http://forum.xda-developers.com/showthread.php?t=1927852 (I used the correct one for the N7105, so I think that is not the problem.)
What I then did was search the internet for an answer and most of the time I found something like "go enter cwm" but that just wont work and I have no idea why. I can only get into the normal "Download" mode. I tried pushing the 3 buttons from the start and just holding them, waiting for the first samsung logo with the device name and then pressing them and also pressing them and then letting go of the power button as one tutorial suggested. At the end it means I can't go into cwm, which would have been the easy way out.
What I did then was trying to flash the stock rom (from samsung-updates.com) on top of it with odin to get rid of the whole mess but that got me nowhere too. When I start up the phone the samsung logo is back but it is stuck... I left it like that for about an hour just to see if it would work eventually but I am stuck at the logo.
Trying to find out what is going on I entered the "Download" mode again and that confused me a bit there as it says binary SAMSUNG official BUT System custom. Just to see what would happen I flashed the auto root on top of it but that just gave my the notice that my binary was also custom so I went and flashed the official samsung rom on top again to no effect.
I spend the whole night yesterday to find a solution but this is all I got. I assume that cyanogenmod 10 is just not working with another kernel and found that out the hard way.
I would really appreciate help on this matter as I am out of options right now.

Boot in recovery now tgat you flashed stock rom. To boot in recovery press
Volume up+home button+on/off.
When samsung logo appears release the power button.
When it will boot in stock android recovery select wipe cache and wipe whole system (can't recall how it is written). Then select reboot now. That should do it.
Sent from my GT-N7100 using xda premium

mariosraptor said:
Volume up+home button+on/off.
Click to expand...
Click to collapse
That did not quite do it but I feel like a fool right now since this is the first time I realised that I mixed up Volume up and Volume down. But you gave me an option for that factory reset and after flashing CWM on top of that with ODIN it works again. One night wasted on nothing but my own lack of sleep and stupidity.
Thanks!

Good that it is working
Sent from my GT-N7100 using xda premium

I don't think Perseus supports CM10 at this time.
Sent from my GT-N7100 using xda app-developers app

SenK9 said:
I don't think Perseus supports CM10 at this time.
Sent from my GT-N7100 using xda app-developers app
Click to expand...
Click to collapse
AFAIK:
Perseus: Samsung based ROMs.
RedPill: Samsung and AOSP.
N.E.A.K. Note2: Samsung and AOPS (AOPS support is only available for the N7100).
Note2Core: Samsung.
Anyway, glad it ended well for you OP!

Androssama said:
AFAIK:
Perseus: Samsung based ROMs.
RedPill: Samsung and AOSP.
N.E.A.K. Note2: Samsung and AOPS (AOPS support is only available for the N7100).
Note2Core: Samsung.
Click to expand...
Click to collapse
Thanks! I haven't experimented much with custom kernels and my first try in combination with CM 10 didn't end that well. This gives me something to go from. Also I had a HTC Desire before and just got the Note 2 a few weeks ago, so there is another thing I have to get to know better.

Dude, please note that, for those kernels above which support both Touchwiz/Samsung and AOSP/Cyanogenmod based ROMS, there will be a separate version of the kernel for each.

hdr32 said:
Hello everyone,
As the title says I have a problem with my Galaxy Note II N7105 Lte (Vodafone, Germany)
I flashed the new cyanogenmod nightly one the phone and that was all well and good but then I made the mistake of flashing the Note2Core Kernel on top of if rendering my phone dead. My first Idea was to flash another Kernel on top, as I had some issues with the newest Note2Core Kernel (v3.06 OC) when I was still on my stock rom. I used the Perseus Kernel from this thread: http://forum.xda-developers.com/showthread.php?t=1927852 (I used the correct one for the N7105, so I think that is not the problem.)
What I then did was search the internet for an answer and most of the time I found something like "go enter cwm" but that just wont work and I have no idea why. I can only get into the normal "Download" mode. I tried pushing the 3 buttons from the start and just holding them, waiting for the first samsung logo with the device name and then pressing them and also pressing them and then letting go of the power button as one tutorial suggested. At the end it means I can't go into cwm, which would have been the easy way out.
What I did then was trying to flash the stock rom (from samsung-updates.com) on top of it with odin to get rid of the whole mess but that got me nowhere too. When I start up the phone the samsung logo is back but it is stuck... I left it like that for about an hour just to see if it would work eventually but I am stuck at the logo.
Trying to find out what is going on I entered the "Download" mode again and that confused me a bit there as it says binary SAMSUNG official BUT System custom. Just to see what would happen I flashed the auto root on top of it but that just gave my the notice that my binary was also custom so I went and flashed the official samsung rom on top again to no effect.
I spend the whole night yesterday to find a solution but this is all I got. I assume that cyanogenmod 10 is just not working with another kernel and found that out the hard way.
I would really appreciate help on this matter as I am out of options right now.
Click to expand...
Click to collapse
As long as you can enter DOWNLOAD mode, your phone is NOT bricked. When you **** up your bootloader and stuff, then we can talk...

Hopefully this has taught you how important it is ti actually read up on something before you do it. Not only are the note2core and perseus kernels for samsung based roms only, other kernels such as redpill and neak only support the n7100 for their aosp/cm kernels.
As far as I know there is currently no other cm kernel for the n7105, although there is a neak cm kernel for the n7105 currently in beta testing.
Sent from my GT-N7100 using xda premium

No worries... learned my lesson... Sometimes I just need that smack in the face to get it.
And before I break my bootloader or some similar disaster occurs... I'll read first.
Sent from my GT-N7105 using xda app-developers app

Think we need a sticky with good instructions how to install and make a nandroid backup.
As well as sticky for EFS backup and why its so important to do it first and properly.
I know I had a lot of problems finding this info and implementing it proper,

Bricked?

I rooted the phone with oden and clockwork mod no problem. Installed team win through goo manager. Booted into Team win to flash HD REvolution ROM
Made a backup before flashing. Installed the ROM followed all the promps. Wiped cache and dav. and rebooted system.
Phone wont power on. I can't get into recovery with volume -home -power it's just dead.
Do I have a option or did I brick it somehow?
I have rooted and flashed my Note 2 countless times without issue.
Here is the ROM
http://www.androidrevolution.nl/downloader/download.php?file=Android_Revolution_HD-SGS3_30.5.zip
Thread
http://forum.xda-developers.com/showthread.php?t=1797334

Care to link the thread for the ROM you flashed I have never heard of it.
Sent from my SPH-L710 using Tapatalk 2

CZuber said:
I rooted the phone with oden and clockwork mod no problem. Installed team win through goo manager. Booted into Team win to flash HD REvolution ROM
Made a backup before flashing. Installed the ROM followed all the promps. Wiped cache and dav. and rebooted system.
Phone wont power on. I can't get into recovery with volume -home -power it's just dead.
Do I have a option or did I brick it somehow?
I have rooted and flashed my Note 2 countless times without issue.
Here is the ROM
http://www.androidrevolution.nl/downloader/download.php?file=Android_Revolution_HD-SGS3_30.5.zip
Click to expand...
Click to collapse
Please tell me that you weren't flashing this International Rom, from over in the International Section... Or please tell me that you actually have the international version of the phone, and not the Sprint version.
Otherwise, you're hard bricked. The only two solutions you have are to do an insurance return (only if you have Sprint TFE, and even then, some on XDA frown upon using it for hard-bricking your phone), or to do a JTAG repair.
The first rule of flashing is: Read as much as you can prior to flashing, including the stickies!
The second rule of flashing is: Re-read everything you just read and make sure you understand it before flashing anything.
Third

Nevermind found it. You flashed a ROM for the International S3 and bricked your phone. Read one of the other hundred threads were people have done this here. Go buy a Jtag.

Yup its hard bricked there is nothing you can do and no a jig won't work it needs to be Jtagged I heard these guys work wonders mobiletechvideos.com
Sent from my SPH-L710 using xda app-developers app

60.00 lesson learned. I just googled best GS3 Roms got a link and went to the Sprint version. never realized it was a international version. It was my son-in laws phone he took the news pretty well.

CZuber said:
60.00 lesson learned. I just googled best GS3 Roms got a link and went to the Sprint version. never realized it was a international version. It was my son-in laws phone he took the news pretty well.
Click to expand...
Click to collapse
Yeah, unfortunately it's a hard lesson. Back when I first got my S3 (about a month after they came out in the US), I came really close to flashing CM10 for the international phone. The only reason I didn't is because I couldn't find too much information on it and decided to wait a little. I'm glad I did, because shortly after I found that XDA have the Sprint forum. If I hadn't found out on here that international Roms brick our phones, I might've lost out on $150 (TEP deductible).
It's understandable, and now that you're here, you can find tons of great Roms for your son-in-law. Lots of really cool features throughout this forum.

Yeah you are lucky it can be jtagged. Just learn to be sure the ROM is labeled for your model of the phone which is sph-l710 or d2spr.
http://i1202.photobucket.com/albums/bb374/TexasEpic/ThePeoplesROM-KennyGlass123/daniel4653.png
Odexed Blue by Strong Steve + Ktoonz w/ Team Kernelizers tweaks

[Q] PA_3.99 bootloop

Again fruitless search results when browsing for a solution. So Im posting, PA_3.99 has been refusing to work right after 1st reboot after intitial flash reboot.
It started out twrp was having partition encryption issues, after reverting to PA's kernel i no longer encountered that. But the bootloop that issue caused (or atleast I thought) still continued.
Heres exactly what happens: Full format x2, flash PA, flash PA_Gapps, wipe, reboot (goes normally, go through setup, can use phone normally), second reboot (for whatever reason), bootloop at yellow sub samsung splash screen( not the PA glowing bean.
Idk if this has to do with TWRP or PA's kernel but those are the only things I can think of with my limited knowledge of android.
This will be the 8th time Ive had to format, flash, setup, reboot, and repeat. I love the PA rom and dont want to have to go to stock again just for a working phone.
pls&thx

if your having this problem like i was you wont find a fix here no one seems to know the answer. ive searched and to no avail. 4.3 wont work on your phone no matter what rom you try. ive tried them all its not the newer phone problem because it reads my card with no problem. only happens on 4.3 roms. if you find a solution please post it or pm me i would love to use 4.3. also a guy had same thing on a note or s4 cant remember. we arent the only ones lol. good luck my friend

bbrita said:
if your having this problem like i was you wont find a fix here no one seems to know the answer. ive searched and to no avail. 4.3 wont work on your phone no matter what rom you try. ive tried them all its not the newer phone problem because it reads my card with no problem. only happens on 4.3 roms. if you find a solution please post it or pm me i would love to use 4.3. also a guy had same thing on a note or s4 cant remember. we arent the only ones lol. good luck my friend
Click to expand...
Click to collapse
Mos definitely. Likewise. What did you read? I can't find anything defining the issue on any technical level. Everyone on here seems too good to answer any questions. ive read more smart ass remarks relating to questions asks then actual answer.
This forum just frustrates the **** out me. I'll pm my email. Probably won't be on here too much after this.
Goodluck

Well after fruitless and frustrating attempts to search/ask for a solution I simply tried flashing clockwork Mod through ROM manager on the successful boot. I've had 3 successful boots to PA 3.99.
I really hope I'm not the first to figure this out. No one mentioned this in paranoid androids thread or team win.
Sent from my SPH-L710 using xda app-developers app

[Q] VM root/recovery weirdness

I'm no stranger to rooting and flashing ROMs, but this is a new one on me. I've had my Virgin Mobile Siii for several months and am pretty happy with it. However, I want to go to CyanogenMod. I also want to root and put a custom recovery on my phone.
My first problem is that I put TWRP on the phone a month or two ago, but when I try to boot into recovery, all I see is the <e3> recovery. I have a TWRP folder with a copy of a Nandroid backup on it, so it must have been there, right? Anyway, to try to figure this out, I downloaded ROM Manager (free version). It says I have both TWRP and Clockwork recoveries on the phone, and trying to have it set me up to use or update either one goes nowhere. Superuser says I'm not rooted.
What I'd prefer to do is get a working root and TWRP recovery on the phone -- I've used it with both an EVO 4G and HTC One V I had in the past and I'm comfortable with it, though if I have to use CWM I can. Then I'd like to use the new CyanogenMod installer if I can be sure it's compatible with the phone. My baseband/build version numbers end with MG2, so I know the phone might be slightly different than a Sprint SIII, but from my exploring the forums here and on other sites it seems to be pretty compatible.
This uncertainty of whether or not I have a custom recovery on the phone makes me very leery of trying to flash a new one without a second opinion. Can anyone help or give me guidance on this?

EelResuah said:
Can anyone help or give me guidance on this?
Click to expand...
Click to collapse
Have you went here and used this method? I would first flash all that way back to stock unrooted on pc Odin to get rid of all the clutter. And if it were me, I wouldn't use ROM manager either. It says Sprint in the link, but everything is the same.
http://forum.xda-developers.com/showthread.php?p=34579827
Sent from my SPH-L710 using XDA Premium 4 mobile app

Gracias
jdsingle76 said:
Have you went here and used this method? I would first flash all that way back to stock unrooted on pc Odin to get rid of all the clutter. And if it were me, I wouldn't use ROM manager either. It says Sprint in the link, but everything is the same.
http://forum.xda-developers.com/showthread.php?p=34579827
Thanks, I will check this one out. The problem I often have is finding my way through a dozen or so threads that almost give me what I need, but this one looks pretty straightforward. I probably won't try it until the weekend, but in the meantime, thanks for the tip!
Click to expand...
Click to collapse