So from stock V50020D, I have installed kkroot, and then able to install custom recovery of TWRP. First version I tried was 2.7.1.0 and then went to version 2.8.0.0.
Same happens at either TWRP version. I am able to get into recovery, WIPE, add a ROM of my choice, but as soon as it starts booting up the =with whoever's ROM boot animation, the screen is dim all the way up to the Android setup screen. It remains dim but I can at least lock the tablet and then unlock it and the brightness is normal until my next reboot.
I thought this version of TWRP 2.8.0.0 fixes this issue? If so, I can't get it to work.
I've read you can also try to flash back to version V50020A with the 4.2.2 kernel and work your way up back to 4.4.2 by updating to higher versions of TWRP, but that's not really a fix, that's more of a workaround and I can't get it to work.
I've tried flashing to LG-V500_JDQ39B.V50010A_US_Stock-BB-Rooted .zip but I start getting a boot loop (as in nothing happens when booting but if you try to get into TWRP, it's stuck running a script of some sort and kicks me out back to the beginning of the LG boot sequence, thus my loop). I then have to do a LG Factory restore and start the process over.
Has anyone successfully fix the dimming issue without updating/upgrading from kernel 4.2.2 and old stock ROM.
Thanks in advance.
If you are talking about the recovery being dim make sure to flash the version built specifically for the 4.4.2 base.
If you are running a ROM that is dim either switch to the 4.2.2 base or use a different kernel. I use a 4.4.2 base with RedKernel and SlimKat rom as an example...
Hello, I have tablet version V50020D and it is rooted. I haven't figured out how to get TWRP on it because the bootloader is locked. Can I ask how you got TWRP to work on this software version? Thanks.
shampiaj said:
Hello, I have tablet version V50020D and it is rooted. I haven't figured out how to get TWRP on it because the bootloader is locked. Can I ask how you got TWRP to work on this software version? Thanks.
Click to expand...
Click to collapse
I used a process a lot like this:
http://forum.xda-developers.com/lg-...e-root-twrp-customrom-kot49i-v50020d-t2894277
Basically the tablet is 4.4.2 except for the aboot partition, which has the older piece from 4.2.2...
muiriddin said:
I used a process a lot like this:
http://forum.xda-developers.com/lg-...e-root-twrp-customrom-kot49i-v50020d-t2894277
Basically the tablet is 4.4.2 except for the aboot partition, which has the older piece from 4.2.2...
Click to expand...
Click to collapse
Awesome. Thanks!
Hey, I was just about to start an a question tonight but saw yours and I was like 'how?!'.
I have a LG G Pad V50020d. Rooting is not an issue but the ability to flash TWRP is just not working for me. I have tried every guide possible, even the one you have suggested. I amended the runme file and things seem to go well but when I boot into recovery I get the fallen android and this message at the bottom of the screen;
"E:missing bitmap stage_empty
(Code -1)
E:missing bitmap stage_fill
(Code -1)"
Don't suppose you can help me?
Sent from my LG-D802 using XDA Free mobile app
Related
can't flash a CWM recovery on my wife's E980 using Freegee....Mine is the white one and I had no loki issues with it...everytime you flsays:
"checking if loki-ifying is needed/dev/block/platform/msm_sdcc. /by-name/boot needs lokifying. [-] Failed to find function to patch.
Error loki-ifying the boot image. "
yes I did use Freegee already and install CWM. When I booted it gave me this...I can't install any ROMS. yet my other G Pro (white) is fine and hasn't given me any issues. RIght now I'm stuck with it booting into clockwork by itself. And I would like to use TWRP but the version that comes with Freegee doesn't work right on the damn screen. If it's not bootlooping into Clockwork then it gets frozen at the LG screen with something about security crap. and the funny part is...I used Freegee both times.
EDIT: used LGFlashTool to bring it back..but she wants a custom ROM and every recovery I flash to it either
1. used this recovery. tried flashing using a CWM recovery that I used from Freegee http://forum.xda-developers.com/showthread.php?t=2552611
freezes at the LG screen with a SECURITY ERROR on the left corner of the screen (flashtools will fix)
2. When I do successfully flash a recovery using Freegee and I get it to boot into CWM it won't come back out of CWM it will boot automatically into it (LGflashtools will fix)
3. the freegee TWRP in won't work right with the touch screen.
Yes I saw that there are 2 topics similar to this, but they are G2's. Mine is an AT&T E980 that i'm having issues with.
I had exactly this same problem. I'm also on AT&T E980 and could not find a fix anywhere for this phone. I flashed back to stock so many times that I was ready to just get rid of it. What I finally noticed was that, if I flashed back to stock and took the update to E98010P, I could flash TWRP through FreeGee and the touch would work. I also used VooDoo OTA to preserve root through the update. I don't know if it was necessary, but it didn't cause me any problems and everything worked.
I have no idea why CWM stopped working and I could not use Phil's recovery either, but the whole experience has been maddening and I have never had so many problems with a phone before. Hope this helps.
i have the same annoying problem!
can someone help?
after the rom flash was done i've got the error so i immediately restored my backup
EdgarSnyder said:
I had exactly this same problem. I'm also on AT&T E980 and could not find a fix anywhere for this phone. I flashed back to stock so many times that I was ready to just get rid of it. What I finally noticed was that, if I flashed back to stock and took the update to E98010P, I could flash TWRP through FreeGee and the touch would work. I also used VooDoo OTA to preserve root through the update. I don't know if it was necessary, but it didn't cause me any problems and everything worked.
I have no idea why CWM stopped working and I could not use Phil's recovery either, but the whole experience has been maddening and I have never had so many problems with a phone before. Hope this helps.
Click to expand...
Click to collapse
so...Root using the old firmware...voodoo OTA then update?...and then restore root and then Freegee should work fine with TWRP?
ive installed the twrp recovery and the flash completed , but the idiot checked the MD5 than skipped it than finished and on the bottom line just did NOTHING!
what the hell!
what is going on with this phone! so frustrating ...
Yeah, I went back to stock, rooted and installed FreeGee and Voodoo, then took the update and flashed TWRP thru FreeGee.
Sent from my LG-E980 using xda app-developers app
and?
no you can install whatever rom you want?
amirnew said:
and?
no you can install whatever rom you want?
Click to expand...
Click to collapse
No, i'm pretty sure on the firmware i'm running (not sure what you're running) can only flash touchwiz based ROMS. No Cyanogenmod, AOSP or anything not based on samsung's stock UI
stanleyopar2000 said:
No, i'm pretty sure on the firmware i'm running (not sure what you're running) can only flash touchwiz based ROMS. No Cyanogenmod, AOSP or anything not based on samsung's stock UI
Click to expand...
Click to collapse
i've tryied flashing custom 4.1.2 rom... and my phone is e980 from att
amirnew said:
i've tryied flashing custom 4.1.2 rom... and my phone is e980 from att
Click to expand...
Click to collapse
wrong thread. it was meant for this one
http://forum.xda-developers.com/showthread.php?p=51529974
stanleyopar2000 said:
can't flash a CWM recovery on my wife's E980 using Freegee....Mine is the white one and I had no loki issues with it...everytime you flsays:
"checking if loki-ifying is needed/dev/block/platform/msm_sdcc. /by-name/boot needs lokifying. [-] Failed to find function to patch.
Error loki-ifying the boot image. "
yes I did use Freegee already and install CWM. When I booted it gave me this...I can't install any ROMS. yet my other G Pro (white) is fine and hasn't given me any issues. RIght now I'm stuck with it booting into clockwork by itself. And I would like to use TWRP but the version that comes with Freegee doesn't work right on the damn screen. If it's not bootlooping into Clockwork then it gets frozen at the LG screen with something about security crap. and the funny part is...I used Freegee both times.
EDIT: used LGFlashTool to bring it back..but she wants a custom ROM and every recovery I flash to it either
1. used this recovery. tried flashing using a CWM recovery that I used from Freegee http://forum.xda-developers.com/showthread.php?t=2552611
freezes at the LG screen with a SECURITY ERROR on the left corner of the screen (flashtools will fix)
2. When I do successfully flash a recovery using Freegee and I get it to boot into CWM it won't come back out of CWM it will boot automatically into it (LGflashtools will fix)
3. the freegee TWRP in won't work right with the touch screen.
Yes I saw that there are 2 topics similar to this, but they are G2's. Mine is an AT&T E980 that i'm having issues with.
Click to expand...
Click to collapse
Ok I have used CWM from FreeGee and used the Carbon (http://forum.xda-developers.com/showthread.php?t=2439911) ROM and it does not need lokifying for my AT&T E980. It loads fine. I'm looking for a way to fix the lokifying thing though as I can't flash too many ROMs, a lot need lokifying.
I've personally had no issues on my E980 using TWRP flashed by FreeGee, but you can always try the "hacked" TWRP provided by @madmack
http://forum.xda-developers.com/showpost.php?p=45497511&postcount=235
chp said:
I've personally had no issues on my E980 using TWRP flashed by FreeGee, but you can always try the "hacked" TWRP provided by @madmack
http://forum.xda-developers.com/showpost.php?p=45497511&postcount=235
Click to expand...
Click to collapse
+1
Always used Madmack's hacked TWRP for anything that requires loki and it works flawlessly.
Sent from my 4.4 Sphinx REMOD LG-E980
So, I have root (confirmed), unlocked bootloader (I guess), TWRP 2.7
I tried:
- omni-4.4.2-20140514-v500-HOMEMADE.zip
- cm-11-20140618-NIGHTLY-v500.zip
- cm-11-20140619-INFECTED-v500.zip
But it always says, that my device is a "palman" and no "v500". I made it to get the Slim-v500-4.4.3.build.5.9-INFECTED-20140616-1124.zip installed once, but then I ended up in a Boot-Loop wit the original "LG Logo - Security Error" screen. So I reverted everything with TWRP. Now I can only boot in TWRP and cannot get any ROM to run.
Any suggestions?
Addition:
Now I was able to Flash cm-11-20140618-NIGHTLY-v500.zip, although i edited the update script and removing the first line where it verifies the model. So it flashed the ROM correctly, but upon restarting, I ended up with the 'official' "LG Logo - Security Error".
So I did a restart via Power+Vol- into All three buttons. The Factory Reset screen comes up, when I hit Vol+ twice I gets me back into TWRP, but on the way there it also shows up the
Secure booting Error!
Cause : Device Unlock!, so Boot Success!!!
.... and now?
Aight, Now with the LG Mobile Support Tool and using Download-Mode on the device, I am hopefully able to go back to stock... Needs to DL 1,2 gig though -.-
So I guess I'll stick with the stock, except anyone is able to tell me where I went wrong...
I'm thinking:
1. towelroot
2. flashify for TWRP
3. choose rom and flash
right? Or do I have to do something extra to the bootloader?
AhNe said:
Aight, Now with the LG Mobile Support Tool and using Download-Mode on the device, I am hopefully able to go back to stock... Needs to DL 1,2 gig though -.-
So I guess I'll stick with the stock, except anyone is able to tell me where I went wrong...
I'm thinking:
1. towelroot
2. flashify for TWRP
3. choose rom and flash
/right? Or do I have to do something extra to the bootloader?
Click to expand...
Click to collapse
If you have the palman device, you have the Google Play edition, and should not be trying to install Roms for the 500 device. All that is out for the palman device is the sleekai kernel, and a base ROM with no extras. If you have the palman device, install the sleekai kernel and exposed and you will be better off anyway.
Is palman is the one have v510?? so awifi is v500 that i have, lol.
I got it to work after all and was able to install the latest CM nightly. After I did the reinstallation of everything (with the LG tool), I did the following:
- root via towelroot
- installed TWRP 2.7.0
- installed TWRP 2.7.1
- installed CM via TWRP 2.7.1
Still, I have no idea why it was recognized wrong during the first tries...
AhNe said:
I got it to work after all and was able to install the latest CM nightly. After I did the reinstallation of everything (with the LG tool), I did the following:
- root via towelroot
- installed TWRP 2.7.0
- installed TWRP 2.7.1
- installed CM via TWRP 2.7.1
Still, I have no idea why it was recognized wrong during the first tries...
Click to expand...
Click to collapse
Good to hear bro.
@AhNe
Just to get it clear. You have a v500 and you rooted it with towelroot and flashed the recovery sucessfully with Flashify ?
something wrong in Loki, try to give it a search...
Sent from my LG-V500 using Tapatalk
Hello everyone.
Im having this problme that only occurs in custom roms and custom recovery. I started having this problem after i updated my phone to official ColorOS 2.0.
So because i couldn't flash that firmware with TWRP I had to go back to Oppo Recovery. I did that and installed new ColorOS.
I then decided to install DU ROM back on my phone (gotta love stock android feel). I went about by flashing latest TWRP 2.8.0.1 to my phone. Restarded phone back into recovery.
This is when i noticed a horizontal line scrolling from top to bottom. I went back to the OS and it was fine. Rebooted back to recovery and the line was still there. I went ahead and flashed DU to my phone. Once it got done i rebooted and now the problem still occurred in the ROM itself. A restart didn't help it either. Went back to recovery and flashed ColorOS lite and problem wasn't there. But when i go back to recovery the problem still persists.
Anyone have this issue?
Everything was working fine before the Color update.
Try flash color is 1.2.6 and then go to flash twrp & DU
tork987 said:
Try flash color is 1.2.6 and then go to flash twrp & DU
Click to expand...
Click to collapse
Should I flash official or kayula rom?
Should i flash it with official recovery or twrp?
I would flash the official with twrp
I need to do some more investigation, but it seems like KitKat ColorOS 2.x contains a new bootloader that causes graphics issues when running custom firmwares (or probably older ColorOS if you didn't downgrade bootloader in the process, for example if you restored a recovery backup instead of flashing COS 1.2.6)
I'll look into methods for bootloader downgrade that don't involve flashing a complete ColorOS package this weekend. I'm not sure, but IIRC, I think some of the existing baseband packages might be sufficient for the bootloader downgrade.
Entropy512 said:
I need to do some more investigation, but it seems like KitKat ColorOS 2.x contains a new bootloader that causes graphics issues when running custom firmwares (or probably older ColorOS if you didn't downgrade bootloader in the process, for example if you restored a recovery backup instead of flashing COS 1.2.6)
I'll look into methods for bootloader downgrade that don't involve flashing a complete ColorOS package this weekend. I'm not sure, but IIRC, I think some of the existing baseband packages might be sufficient for the bootloader downgrade.
Click to expand...
Click to collapse
I think your right. New color os does have a new bootloader because before the update the boot logo didnt contain the words "powered by android" . With this new one the logo looks different and it states those words at the bottom for a few seconds.
tork987 said:
Try flash color is 1.2.6 and then go to flash twrp & DU
Click to expand...
Click to collapse
thanks. this did the trick!
djabi90 said:
I think your right. New color os does have a new bootloader because before the update the boot logo didnt contain the words "powered by android" . With this new one the logo looks different and it states those words at the bottom for a few seconds.
Click to expand...
Click to collapse
The boot logo and the actual bootloader are separate components.
I took my 5.1.1 VZW Note 4, and rooted it with King Root. I proceeded to follow the instructions to change my CID here. I used adb, performed the commands, and everything seemed golden. I used odin to flash TWRP, but something went wrong. I booted into the recovery, and tried to "update from external storage". I soon recieved a "dm-verity verification failed in recovery" messaged. It did not occur to me that I was still in the stock recovery; I did not bother to check it's initial look and feel, and assumed the TRWP programmers were just lazy. After reading up on this "dm-verity" error, xda posters said I should flash it with Kies. Thinking nothing wrong could happen, I gave it a shot. It updated to 6.0.1. This is where the problems start happening.
Since then, I can't reflash to 5.1.1. I've tried every version I could get my hands on, including the 5.1.1/6.0.1 hybrid posted here. I have 3 total verions of 5.1.1. I then tried to downgrade to 5.0.1. The first version of 5.0.1 started artifacting the screen, but booted and stopped promptly. It only artifacted the "Samsung" loading screen. I couldn't, however, root the device. Feeling desperate, I tried the only other version of 5.0.1. Success! I rooted and reran the adb commands and the script provided to change CID. This time, it skipped the first half of the script. It went directly to "backup up loader to external card". This tells me something about my CID will forever be changed, and is probably the reason my phone is boot looping. This time, I was able to flash TWRP. I installed CM 13 only to find out my sim wasn't recognized (when I used it to download King Root in 5.0.1 before). I figured it was because I was usig a 5.0.1 bootloader/modem. I tried reflashing to 5.1.1, the 5.1.1/6.0.1 hybrid, and 5.0.1 again. 5.11 boot loops and 5.0.1 hangs. Advice please... Thanks
Versions flashed:
"N910VVRU2BPA1_N910VVZW2BPA1_N910VVRU2BPA1_HOME.tar" - 5.1.1, boot loops at Verizon screen
"N910VVRU2BPA1_N910VVRU2CPD1_FullFirmware.tar" - 5.1.1/6.0.1 hybrid, boot loops
"N910VVRU2BOG5_N910VVZW2BOG5_N910VVRU2BOG5_HOME.tar" -5.0.1, boots but artifacts and cannot root
"N910VVRU2BOF1_N910VVZW2BOF1_N910VVRU2BOF1_HOME.tar" - 5.0.1, booted and rooted/flashed to TWRP, caused hiccups in MM custom roms, cannot get to boot again after a reflash
"N910VVRU2BPA1_StockRestore.tar" -5.1.1 unincremented stock restore, fails on ~90% of odin flash
"N910VVRU2BPA1_StockRestore_Incremented.tar" - 5.1.1 incremented stock restore, flashes, boot loops
Edit: Success!! I flashed the Incremented Stock Restore for 5.1.1 to no avail. It keep boot looping. I cleared the cache and data twice in a last ditch effort, and pulled the USB cord. It booted! Can anyone instruct me on how to proceed to flash only the modem/required portion of 6.0.1 after flashing TWRP? Do I just flash the 6.0.1 modem or modem and kernel?
Edit 2: I flashed the 6.0.1 modem over top of my 5.1.1 full firmware. I have TWRP and CM 13 loaded and working perfectly. From previous experiences, I've noticed CM 13 is more forgiving than some other 6.0.1 custom ROMs. Should I attempt to reflash the Lollipop on MM Stock Rom to obtain the MM bootloader, and then unlock it? This is working fine at the moment.
Edit 3: I reflashed to the hybrid rom and everything's okay. I had to wipe the cache..
mods, you can delete this thread. I solved my issue
av00va said:
mods, you can delete this thread. I solved my issue
Click to expand...
Click to collapse
Hey bud I'm on 6.0.1 can you give me the link to downgrade to 5.1.1 So I can root and unlock
Sent from my VS990 using Tapatalk
mwebb34 said:
Hey bud I'm on 6.0.1 can you give me the link to downgrade to 5.1.1 So I can root and unlock
Sent from my VS990 using Tapatalk
Click to expand...
Click to collapse
http://forum.xda-developers.com/note-4-verizon/general/note-4-verizon-bootloader-unlock-t3358913 and http://forum.xda-developers.com/not...t/howto-bootloader-unlock-upgrade-to-t3398144 Use the 2nd link 1st to downgrade to 5.1
I had to use Kingoroot(Google it) to root. It was a pain but once you root you have to be patient and leave the phone until it stabilizes after rooting. It took me a few attempts but in the end I'm golden. Part of my problem is a bad battery too but that's another story....
Stuck at "Patching System Image Unconditionally" when flashing CM12.1 via TWRP
Just got a Note 4, proceeding with the usual root and installation CyanogenMod ASAP
Everything was going smoothly until the actual flashing of CyanogenMod, whenever I try to flash it, it just gets stuck on "patching system image unconditionally" and doesn't progress beyond that point
Steps I've taken so far:
1) unboxed phone, was running Android 6.0 (I think, maybe 6.0.1)
2) Rooted with Chainfire's Auto Root
3) Flashed TWRP 3.0.2-0 via Odin 3.09 as per TWRP's instructions
4) Ensured that I could boot both to the stock ROM and TWRP
5) Copied cm12.1 and gapps to Note 4's internal storage (sd card hasn't come in yet, normally I put it onto sd card)
6) Did default factory wipe from TWRP
7) Attempted to flash cm12.1, ran into issue
I didn't make a backup of the stock ROM so now the phone has a recovery but no actual OS, as I had to pull the battery out to get it to do anything beyond being stuck at the patching system image step
I'm redownloading cm12.1 in case maybe there was a problem with the .zip itself, I know it's bad practice but I never check md5 sums
I've found other threads that suggested flashing the stock ROM for some reason, but they were for other phones and I'm not sure if it's related to the Note 4.
I've seen some mention of the bootloader being locked, but I don't know how to tell if the bootloader is locked or not. I see the same exact boot screen that I saw with my Note 3, S4, S3, etc. Could the issue be the bootloader?
I've also found this thread, but I can't get TWRP to mount in Windows, it keeps saying the driver failed to install. MTP transfers worked fine with the stock ROM was still there, but for some reason it doesn't work with the Mount option in TWRP. I'm downloading the Android SDK so I can try using adb
If anyone else has run into this, can you advise me on what to do from here?
EDIT: Nevermind, fixed it. Changed system partition's filesystem to F2FS via TWRP, and this allowed CM and gapps to flash with no issue. Now booted into CM But hopefully this will be helpful if anyone else has this issue
EDIT2: Buuuuut now the WiFi's not working. It just gets stuck at "turn on WiFi" but nothing actually turns on, and the on/off button for WiFi in settings is grayed out. IT NEVER ENDS
CyanogenMod Thread
Reddit Thread
EDIT3:
WiFi and Settings Issue seems to be resolved
I think the problem had something to do with the baseband version
As per Trex's post (http://forum.xda-developers.com/showpost.php?p=69520362&postcount=2), I had to revert back to the OK1 baseband
Now everything seems to work fine
As for TWRP not working and just going to a black screen, I redownloaded it from the TWRP website and it worked fine
So now both TWRP and CM are installed and working, WiFi works, and Settings don't crash.
Now I've encountered an issue where the camera doesn't focus, and I'm wondering if there's still some plastic film on the camera lens, but I've been picking at it and nothing is coming off and I'm afraid of damaging the plastic if I keep trying...
AbuFiraas said:
Just got a Note 4, proceeding with the usual root and installation CyanogenMod ASAP
Everything was going smoothly until the actual flashing of CyanogenMod, whenever I try to flash it, it just gets stuck on "patching system image unconditionally" and doesn't progress beyond that point
Steps I've taken so far:
1) unboxed phone, was running Android 6.0 (I think, maybe 6.0.1)
2) Rooted with Chainfire's Auto Root
3) Flashed TWRP 3.0.2-0 via Odin 3.09 as per TWRP's instructions
4) Ensured that I could boot both to the stock ROM and TWRP
5) Copied cm12.1 and gapps to Note 4's internal storage (sd card hasn't come in yet, normally I put it onto sd card)
6) Did default factory wipe from TWRP
7) Attempted to flash cm12.1, ran into issue
I didn't make a backup of the stock ROM so now the phone has a recovery but no actual OS, as I had to pull the battery out to get it to do anything beyond being stuck at the patching system image step
I'm redownloading cm12.1 in case maybe there was a problem with the .zip itself, I know it's bad practice but I never check md5 sums
I've found other threads that suggested flashing the stock ROM for some reason, but they were for other phones and I'm not sure if it's related to the Note 4.
I've seen some mention of the bootloader being locked, but I don't know how to tell if the bootloader is locked or not. I see the same exact boot screen that I saw with my Note 3, S4, S3, etc. Could the issue be the bootloader?
I've also found this thread, but I can't get TWRP to mount in Windows, it keeps saying the driver failed to install. MTP transfers worked fine with the stock ROM was still there, but for some reason it doesn't work with the Mount option in TWRP. I'm downloading the Android SDK so I can try using adb
If anyone else has run into this, can you advise me on what to do from here?
EDIT: Nevermind, fixed it. Changed system partition's filesystem to F2FS via TWRP, and this allowed CM and gapps to flash with no issue. Now booted into CM But hopefully this will be helpful if anyone else has this issue
EDIT2: Buuuuut now the WiFi's not working. It just gets stuck at "turn on WiFi" but nothing actually turns on, and the on/off button for WiFi in settings is grayed out. IT NEVER ENDS
Click to expand...
Click to collapse
You must flash 5.1.1 ok1 bootloader to get wifi work
I suggest you first flash 5.1.1 firmware in odin
Then flash twrp. Tar file in odin.
Then make full wipe
Flash cm rom + gapps
You will get clean rom install without any errors
Hope this will help
Trex888 said:
You must flash 5.1.1 ok1 bootloader to get wifi work
I suggest you first flash 5.1.1 firmware in odin
Then flash twrp. Tar file in odin.
Then make full wipe
Flash cm rom + gapps
You will get clean rom install without any errors
Hope this will help
Click to expand...
Click to collapse
Okay I'll give that a shot. Are "5.11 ok1 bootloader" and "5.1.1 firmware" the same thing? And do you know where I can find it/them?
Just flashed OK1 via Odin via this thread, but it's just boot looping over and over
EDIT: Did a simple factory wipe and it's working fine now. Currently running unrooted Stock 5.1.1, Baseband N910PVPS4COK1. So I'm basically starting from the beginning, whereas before it was on 6.0 but now it's 5.1.1
Am now rooted but I can't get TWRP installed, I flash it and try to boot to recovery but it just boots to a black screen
Issue seems to be resolved, edited original post
AbuFiraas said:
Okay I'll give that a shot. Are "5.11 ok1 bootloader" and "5.1.1 firmware" the same thing? And do you know where I can find it/them?
Click to expand...
Click to collapse
Go to download mode and check exact model number
Tell me model number and i give you links for bootloader and firmware
Trex888 said:
Go to download mode and check exact model number
Tell me model number and i give you links for bootloader and firmware
Click to expand...
Click to collapse
It's working now, I found another post that had all the various stock firmwares on there. Now the issue I'm having is that my camera doesn't focus at all, but I don't know if it's a hardware or software issue. I never checked the camera before rooting the first time. Gonna try going back to unrooted stock again but if that doesn't change anything, I might have to take it to a Sprint store and get a replacement. Hopefully they don't notice the KNOX trip... lol