Develop Bugs

[Q] Wind SGH-T999V CM Help

Okay, I'm new to Android and I heard this is the go-to spot for help. Anyway, this is what happened to my Wind SGH-T999V. Mind you i'm VERY new to this rooting thing
I rooted my S3 by using TWRP 2.6.3.0 and i used odin3 v1.85 and it worked. I downloaded a root checker and it said i'm rooted. Then i put CM 10.1.2 on my sd card and wanted to install it via TWRP recovery but it gave me an error that said "No MD5 filed found" or something along those line.
I then tried to use different versions of twrp ( twrp 2.6.1.0) and a different CM (10.1.1) but i still got the same "no Md5 found" error. So, a friend then told me to ditch twrp all-together and download CWM instead. So, I download recovery clockwork touch 6.0.3.7 and put it on my phone.
THEN, i tried to go back to the recovery boot place, but after that small blue font saying "recovery boot", my phone goes black. I dont see the old twrp recovery or the clockwork one.
I just really want to have Cyanogenmod on my phone, i've been having a hard time. Help please?

Just disable the md5 check, most or the ROM files are not going to include a hash file, but will flash fine. TWRP or CWM will error out if the flash fails.
Also, it sounds like your recovery install failed, just reinstall using ODIN and a file from @DocHoliday77 (I recommend TWRP over CWM, but it is just preference)

It's already unchecked.

Install TWRP and try again, should work without issue. Also, redownload the ROM file, preferably the latest version, 10.1.3RC2 (I think)
Sent from my T-Mobile T999L using TapaTalk 4 and delivered by Planet Express.

Can you link me the most STABLE CM that works with my Wind SGh-T999V?

qasde455 said:
Can you link me the most STABLE CM that works with my Wind SGh-T999V?
Click to expand...
Click to collapse
Don't use RC2. If you want stable, use 10.1.2. get.cm, filter it for your device. I think Doc also has them in his signature.

http://get.cm/?device=d2tmo&type=stable
"Stable" is relative, the RCs are just as good.

Aerowinder said:
Don't use RC2. If you want stable, use 10.1.2. get.cm, filter it for your device. I think Doc also has them in his signature.
Click to expand...
Click to collapse
I have cm 10.1.2 downloaded but like i said, it\s not installing for me. I used multiple recovery's and atm i'm using twrp 2.2.2.0 and it's not installing either.
EDIT: I'm getting a status 7 error when I try to install it via twrp install

qasde455 said:
I have cm 10.1.2 downloaded but like i said, it\s not installing for me. I used multiple recovery's and atm i'm using twrp 2.2.2.0 and it's not installing either.
EDIT: I'm getting a status 7 error when I try to install it via twrp install
Click to expand...
Click to collapse
You need to edit the install script because your device isn't supported. Or you can download Doc's version.

Actually I'm pretty sure cm includes the T999V, but I'm betting the firmware needs to be updated.
Look in Aerowinders Sig for the links to the firmware. In that OP you should find a link to the thread with the T999V firmware.
Or, you can go to my T999L thread and get the Rom there. But w/o updated firmware it may be buggy.
Sent from my SCH-I535 using Tapatalk 4

It's already unchecked.

qasde455 said:
I have cm 10.1.2 downloaded but like i said, it\s not installing for me. I used multiple recovery's and atm i'm using twrp 2.2.2.0 and it's not installing either.
EDIT: I'm getting a status 7 error when I try to install it via twrp install
Click to expand...
Click to collapse
CM10.1.3 is now Stable and will be the last 4.2.2 build. It should has the all of the Asserts, including the MB7 one. Also, update your TWRP, the current is 2.6.3.0.

I want to install CM so bad but after reading lot of threads n comments, I am scared. there are many terms used, i even dont know like flash kernel, OTI, radio etc... i just know about rooting, recovery and ROM... so i have decided to install PAC man instaed its a combination of couple roms and is most successful and stable..

malibu.barbie said:
I want to install CM so bad but after reading lot of threads n comments, I am scared. there are many terms used, i even dont know like flash kernel, OTI, radio etc... i just know about rooting, recovery and ROM... so i have decided to install PAC man instaed its a combination of couple roms and is most successful and stable..
Click to expand...
Click to collapse
You should read the sticky threads, and use xdas search for terms or definitions anytime you run into stuff you aren't familiar with.
Sent from my SGH-T999V using Tapatalk 4

cm11 compatible kernel?

I am currently using cm11 nightly, however i cant find any kernel that works......
i tried franco, faux, elemental, bulletproof.
at first i thought it was my recovery being outdated, so i updated twrp, didnt work, tried cwm, didnt work.
so i was like, maybe it was my bootloader? I updated it to 402, repeated previous steps, didnt work.
I thought it might be corrupted file, nope, redownloaded it, did sumcheck on some of the files with key provided.
after i flash these kernels, on first boot i'll see a scrambled screen and just hang there.
Is it just me or is anyone suffering from the same problem as well?

You need a caf based kernel for CM. You have been trying AOSP based kernels which will not work with CM.

[Q] Bootlooping: Why won't my phone work with KitKat roms?

I have a T989, not a T989D, running TWRP 2.7.1.0 and UVMC6 radio, coming from a JB 4.1.2 Slimrom.
Also I have taken out the board and inspected the power button, and everything seems okay there. I don't think it's being caused by a faulty button or some other hardware problem because I can flash my old Slimrom, and that boots up just fine.
I wanted to give Paranoid Android a whirl with the latest Wild kernel, and though I've tried 8 different PA builds, a PACman, a Slimkat, and an Alpine rom, ALL KitKat roms so far are bootlooping. [EDIT: Even PA 3.99 JB 4.3 is doing it. So it's more than just KitKat even.]
I'm doing the following:
Wipe system, data, cache, dalvik, and perhaps android secure and preload as well
Flash ROM & Gapps
Wipe cache & dalvik
Reboot
I reach the splash, and maybe it even finishes booting. But invariably, it takes about 60-90s from initialization before the screen dims, everything freezes for 2-5s, and it reboots.
I'm out of ideas.
Why won't my phone work with KitKat?
Thanks in advance

Have you ever used odin to flash the factory 4.1.2 UVMC6 rom? Some driver stuff was updated in that version and can only be installed with odin.
Edit: If your phone came with 4.1.2 jellybean, you already have the newest drivers.

meekrawb said:
Have you ever used odin to flash the factory 4.1.2 UVMC6 rom? Some driver stuff was updated in that version and can only be installed with odin.
Edit: If your phone came with 4.1.2 jellybean, you already have the newest drivers.
Click to expand...
Click to collapse
I read something to that effect. Haven't seen a .tar file for it, only .zip.

jaybird16 said:
I read something to that effect. Haven't seen a .tar file for it, only .zip.
Click to expand...
Click to collapse
If you sign up for an account on sammobile.com you can download from there. Just type "t989" in the search box.

meekrawb said:
If you sign up for an account on sammobile.com you can download from there. Just type "t989" in the search box.
Click to expand...
Click to collapse
Okay, I did that. Flashed the latest Paranoid Android 4.45. No dice. Same story.

jaybird16 said:
Okay, I did that. Flashed the latest Paranoid Android 4.5. No dice. Same story.
Click to expand...
Click to collapse
That was the only thing I could think of. Maybe someone else has some ideas.

I had the same problem. Turned out it had to do with the recovery. I redownloaded twrp, used flashify to install it. And that fixed the problem.

meekrawb said:
That was the only thing I could think of. Maybe someone else has some ideas.
Click to expand...
Click to collapse
Much appreciated. My phone shipped at the tail end of Gingerbread. So now I have whatever drivers from 4.1.2, and that's one more potential problem eliminated.
The stock rom ran just fine, btw, once I factory reset (the documentation was nil, but at 750mb, I knew it was more than just UVMC6 radio firmware...)
So 4.1.x seems to be okay, but not 4.3.x or 4.4.x. Next I'll have to try a flavor of 4.2.x and see how it feels about that.

Lokke9191 said:
I had the same problem. Turned out it had to do with the recovery. I redownloaded twrp, used flashify to install it. And that fixed the problem.
Click to expand...
Click to collapse
Interesting.
After I flashed the stock UVMC6 (and associated rom and lameass stock recovery) earlier today, I felt it was safest to use Odin to reflash TWRP while I had a functioning rom (even tho not rooted). So I downloaded the tar and that's the recovery I used to test PA 4.45. I will be doing more testing. I mean, it's not because there are leprechauns in my phone, right?

jaybird16 said:
Interesting.
After I flashed the stock UVMC6 (and associated rom and lameass stock recovery) earlier today, I felt it was safest to use Odin to reflash TWRP while I had a functioning rom (even tho not rooted). So I downloaded the tar and that's the recovery I used to test PA 4.5. I will be doing more testing. I mean, it's not because there are leprechauns in my phone, right?
Click to expand...
Click to collapse
Never. Ever. Rule out leprechauns!

Lokke9191 said:
Never. Ever. Rule out leprechauns!
Click to expand...
Click to collapse
LOL, good point.
w00t! TWRP 2.1.8 for the Hercules just dropped!
I was thinking maybe the MD5 wouldn't have checked out the first time you downloaded, but would have the second time. I don't usually bother unless I have a reason to think that's a problem. I can always look after the fact.
Downloaded 2.1.8 and MD5 checks out...now to flash it...

jaybird16 said:
LOL, good point.
w00t! TWRP 2.1.8 for the Hercules just dropped!
I was thinking maybe the MD5 wouldn't have checked out the first time you downloaded, but would have the second time. I don't usually bother unless I have a reason to think that's a problem. I can always look after the fact.
Downloaded 2.1.8 and MD5 checks out...now to flash it...
Click to expand...
Click to collapse
Nice. Lemme know how it works out. Oh. The new PA is awesome.

My bad. I saw the number "8" at the bottom of the page which had not been there earlier and assumed it was next after after "7". No, that's an ancient recovery from 2012.
TWRP 2.8.1 for the Hercules has NOT just dropped!

Okay, so, my first test with a newly downloaded, MD5 checked, and flashed TWRP 2.7.1 recovery, and an MD5 checked PA 4.45 has not produced any different result.
However, you've made me realize that I can't hope to troubleshoot this without being fastidious about MD5 from here on out, so, thx 4 that.
...same goes for a 2nd test with an MD5 checked PA 4.5 Alpha3...
...same goes for a 3rd test with an MD5 checked PA v3.69 (4.2)...
...But Slim-Star v4.12 (4.2) loads no problem...go figure...

Fix permissions?
I tried to install the PA 4.5 Beta, and same problem. It bootloops.
Could it have anything to do with permissions?

jaybird16 said:
Interesting.
After I flashed the stock UVMC6 (and associated rom and lameass stock recovery) earlier today, I felt it was safest to use Odin to reflash TWRP while I had a functioning rom (even tho not rooted). So I downloaded the tar and that's the recovery I used to test PA 4.45. I will be doing more testing. I mean, it's not because there are leprechauns in my phone, right?
Click to expand...
Click to collapse
when i had an issue like this i re-installed the factory original rom and started from the very beginning. if you've tried that and it doesn't work, well i'm pretty much unhelpful here. :crying:

Also note that WildKernel has a special version of v9 out for recent roms (roms released within the last two months).
Any other version of wildkernel will lead to bootloops in my experience.
If your rom is older than two months, then v8 or v9 should do fine

ayr0 said:
Also note that WildKernel has a special version of v9 out for recent roms (roms released within the last two months).
Any other version of wildkernel will lead to bootloops in my experience.
If your rom is older than two months, then v8 or v9 should do fine
Click to expand...
Click to collapse
There were problems reported of even the latest version of Wild! not working with Paranoid.
jrc2
Sent from my T-Mobile S2 using Tapatalk.

I'm having the same issues, but no one knows what's up. I've tried so many ROM's and only the older ones work.
http://forum.xda-developers.com/showpost.php?p=55050951&postcount=9
This is my post with the logs I got from the constant crash on cm11. I tried pa and had the same result.

Issue solved
After sharing some logs with Sultanxda, he pointed out this bootloop issue due to the CM kernel and helped me get it fixed.
My problem was that my phone would not boot on MOST JellyBean ROM's or ANY KitKat ROM. It would crash/kernel panic on or before the set up screen.
I do not know if the latest KitKat ROM's have the issue patched, but I asked if he could upload the patch for the kernel to source for other ROM's to use.
This thread should be solved I guess.

[Q] getting weird error when I try to flash ROM in TWRP

I was hoping that someone could help me out with some advice. I'm having a lot of hiccups after installing CM11 (M12) and I thought flashing a newly downloaded and MD5 verified copy might fix some of the problems.
I originally had CWM installed on my e980, but I've recently swapped that out to TWRP 2.8.1.0. The issue that I'm seeing is that every time I try to flash a ROM, TWRP gives me an error that says CM 11 for my e980 isn't compatible with my device, which it's detecting as an LG F310LR (which appears to be a Korean variant).
Can anyone give me some suggestions on how to fix/bypass this? Flashing ROMS in CWM was working fine, but I've had a lot of problems with TWRP. So many in fact that I've reverted to CWM a couple of different times.
Thanks in advance!

racer25x said:
I was hoping that someone could help me out with some advice. I'm having a lot of hiccups after installing CM11 (M12) and I thought flashing a newly downloaded and MD5 verified copy might fix some of the problems.
I originally had CWM installed on my e980, but I've recently swapped that out to TWRP 2.8.1.0. The issue that I'm seeing is that every time I try to flash a ROM, TWRP gives me an error that says CM 11 for my e980 isn't compatible with my device, which it's detecting as an LG F310LR (which appears to be a Korean variant).
Can anyone give me some suggestions on how to fix/bypass this? Flashing ROMS in CWM was working fine, but I've had a lot of problems with TWRP. So many in fact that I've reverted to CWM a couple of different times.
Thanks in advance!
Click to expand...
Click to collapse
Did you ever figure this out, mine just did the same thing.

zole2112 said:
Did you ever figure this out, mine just did the same thing.
Click to expand...
Click to collapse
Use another version of twrp, that works for me.
Sent from my LG-F240L using Tapatalk

The same thing happened to me once , I had to do a full restore with the kdz , and redo everything.
but you can modify the build.prop or something and change it to your variant.
the thing gets messed up by the Unlocker app.

irt118 said:
Use another version of twrp, that works for me.
Sent from my LG-F240L using Tapatalk
Click to expand...
Click to collapse
Thanks. I'll try this tonite:
https://dl.twrp.me/e980/twrp-2.8.7.0-e980.img.html
If that doesn't work, I guess I'll have to revert to stock and start over.

Lg g3 T-Mobile screen split offset

I need some help guys. I rooted. And flashed a new ROM on my lg g3. I flashed two different ROMs and completely formated my phone both times. But every time I flash a ROM my screen gets this weird split down the middle and both sides are offset. Any reason why this is happen and if so what can I do to fix this?

I'm just going to bump this because I have the exact same issue with my Verizon G3.

For me it happens on first startup every time. Once you lock and unlock the screen it goes away.
Sent from my LG-D851 using Tapatalk

It has to do w/ the LP 20e/g bootloader combined w/ AOSP and CM ROMs. I haven't tried it myself, but apparently by flashing a KK bootstack, the split screen/misalignment issue is fixed. You can find the 10r KK bootstack here...
http://forum.xda-developers.com/tmobile-lg-g3/development/rom-tmo-d851-lollipop-20b-stock-t3096479
If you want to retain TWRP, then it will need to be flashed after flashing the bootstack.zip

redduc900 said:
It has to do w/ the LP 20e/g bootloader combined w/ AOSP and CM ROMs. I haven't tried it myself, but apparently by flashing a KK bootstack, the split screen/misalignment issue is fixed. You can find the 10r KK bootstack here...
http://forum.xda-developers.com/tmobile-lg-g3/development/rom-tmo-d851-lollipop-20b-stock-t3096479
If you want to retain TWRP, then it will need to be flashed after flashing the bootstack.zip
Click to expand...
Click to collapse
Did clean wipe, then flashed the 10R KK bootstack, then flashed my favorite 5.1.1 custom ROM (Exodus) + gapps, and the phone fails to boot, so I'm missing something.
If anyone can detail the exact steps to fix this glitch, would be most appreciated.