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....
Related
Hey guys,so heres the problem...recently i had to use the LG Support Tool and prior to this i was v50020d. When the tool had finished restoring the stock ROM,it upgraded me to v50020f. So i went and successfully rooted it with KingoRoot surprisingly enough with no trouble at all. I then tried to install TWRP Recovery,through the TWRP app,Flashify,Rashr and i even tried Fastboot and ADB which im led to believe don't work with the v500 but i still tried it and had absolutely no success at all in installing TWRP. I have tried flashing every version of TWRP from 2.8.7.1 back to 2.6.3.0 i think using all those apps mentioned above. So i came on here to XDA to see could i find any solution to my problem but no luck either but i did find a post where a script was used,edited and apparently worked. I downloaded the zip file that was used in this process,edited the runme.bat file by changing the last letter of the build to f which would correspond to my build which is v50020f. I saved the edited file and then ran the script which when finished told me that recovery had been installed so i rebooted the G Pad,it started up,the blue teamwin screen came up and then it just hung there for hours! Thats was it nothing more. No recovery installed. So then i went and used Flashify & flashed `twrp-2.8.7.1-v500.img´ and when i rebooted i got 'secure booting error,cause:device unlock:so boot success!!' rebooted the G Pad again and the same thing happened blue teamwun screen loads and then nothing,no recovery. So i flashed the same recovery image with TWRP Recovery app and when it was finished i got the message 'Success!! Flashing recovery was successful,would you like to attempt rebooting into recovery? so i did and again the same thing happened. Teamwin blue screen and nothing more. When i check TWRP Recovery app afterwards it tells me that there is no recovery installed or it us not recognised. Can anybody please,please,please find a solution to my problem? Oh yeah,i even tried booting into recovey by using the power and volume up and down trick too and got the same result. Thank you so much guys...hope you can help.
I think I've seen that in order to install TWRP on the V500 is similar to how on my VK810 variant, at least the part that requires downgrading your bootloader. If it's like the VK810, it has to be the bootloader from 4.2.2. I'm sure there's TWRP threads in these sections, specifically for the V500 that give the details and files.
I'd love to know a way too. I just rooted which went great, but I have the V50020f and don't want to do another thing until I see what happens in this thread. After years of flashing and rooting I finally hard bricked my Lenovo Yoga 10 and this is my replacement tablet, so I don't want to chance it at all. Until I read a concrete solution for this build I'm staying where I am.
That wall of text is really hard to read @[email protected]!c, when I first saw it I was too tired to try and decipher it so ignored it. Now I've had another look.
Have you tried downgrading to an older firmware which people have had success with?
I had trouble when I first got this tablet but kept reading the forum and found a method to downgrade, it isn't pretty but eventually it worked. As I'm new to this device I'm not overly familiar with the different official firmware versions so I'm not exactly sure what you've got.
My tablet was more complicated as the LG tool put the Chinese, no Google apps, version on for me as that is where it was bought. So I had to downgrade so I could get apps from the Play Store to flash my recovery!
So patience and research will reward you.
[email protected]!c said:
Hey guys,so heres the problem...recently i had to use the LG Support Tool and prior to this i was v50020d. When the tool had finished restoring the stock ROM,it upgraded me to v50020f. So i went and successfully rooted it with KingoRoot surprisingly enough with no trouble at all. I then tried to install TWRP Recovery,through the TWRP app,Flashify,Rashr and i even tried Fastboot and ADB which im led to believe don't work with the v500 but i still tried it and had absolutely no success at all in installing TWRP. I have tried flashing every version of TWRP from 2.8.7.1 back to 2.6.3.0 i think using all those apps mentioned above. So i came on here to XDA to see could i find any solution to my problem but no luck either but i did find a post where a script was used,edited and apparently worked. I downloaded the zip file that was used in this process,edited the runme.bat file by changing the last letter of the build to f which would correspond to my build which is v50020f. I saved the edited file and then ran the script which when finished told me that recovery had been installed so i rebooted the G Pad,it started up,the blue teamwin screen came up and then it just hung there for hours! Thats was it nothing more. No recovery installed. So then i went and used Flashify & flashed `twrp-2.8.7.1-v500.img´ and when i rebooted i got 'secure booting error,cause:device unlock:so boot success!!' rebooted the G Pad again and the same thing happened blue teamwun screen loads and then nothing,no recovery. So i flashed the same recovery image with TWRP Recovery app and when it was finished i got the message 'Success!! Flashing recovery was successful,would you like to attempt rebooting into recovery? so i did and again the same thing happened. Teamwin blue screen and nothing more. When i check TWRP Recovery app afterwards it tells me that there is no recovery installed or it us not recognised. Can anybody please,please,please find a solution to my problem? Oh yeah,i even tried booting into recovey by using the power and volume up and down trick too and got the same result. Thank you so much guys...hope you can help.
Click to expand...
Click to collapse
Hi!! I'm in the same boat! Any chance you were able to work out a solution? Thanks so much for any help!!
I know it didn't work for the OP, but coming from bone stock v50020f, I successfully rooted using ioroot25r1, updated Supersu through playstore, then using flashify i installed TWRP 2.8.7.1 (newest I think). Once booted into TWRP recovery, I wiped cache, data, and system, and then installed AOSP Marshmallow. All went smooth as silk, no problems at all. Now I can finally stop being jealous of my wifes Nexus 7!! Hope this helps some.
vettejock99 said:
Hi!! I'm in the same boat! Any chance you were able to work out a solution? Thanks so much for any help!!
Click to expand...
Click to collapse
Thanks.!
i have just used twrp manager apk from playstore (similar to flashify) to get TWRP 2.8.7.1 on stock v50020f, rooted using ioroot25r1 on a mac, with updated Supersu through playstore. just had to run the apk twice as it failed first time, and have booted into twrp recovery.
Had the same problem with the recovery but worked by rooting and flashing recovery with flashify.
I was on fulmics 2.7 and decided to update to M.
I downloaded N&N Custom ROM based on stock ROM.
I booted to TWRP (newest version), wiped everything, format data.
Then I pushed the ROM according to dev instructions to the phone and installed.
Reboot, booting, bootanimation and then a white screen:
"Enter pin to unlock. 30/30 tries"
I do not have a PIN on the SIM card activated, but I entered the correct one - didnt work, not accepted.
Booted without SIM - same question.
I downloaded the files again, same problem.
I flashed a stock ROM with flashable system from XDA - same problem.
I downloaded MM kdz and tried to flash with LGUP. Error with "port open is failed after dload change".
I downloaded fulmics 2.7 and flashed in TWRP, not booting, stuck at LG logo, LED is green-blue.
Current status:
I still have TWRP but no TWRP backup.
I am not a newb about flashing:
ZTE Blade, Hannspad, Galaxy Nexus, Galaxy S, Nexus 4, Huawei something, Arcos something, Asus ME301T Tablet, but this is the first flash that went haywire.
Help?
Under stock rom you mean this?
http://forum.xda-developers.com/lg-g3/development/stock-d855-30b-images-kdz-flashables-t3282012
Thats one of the stock ROMs I tried.
The N&N is this:
http://www.htcmania.com/showthread.php?t=1120602
there is unbrick method under Bender007 signature
But you probably have to wait for more solutions. It is good that your TWRP is still there.
Direct link:http://www.androidbrick.com/unbrick-recover-your-dead-lg-g3-g2-all-variants/
Edit:
Maybe this info can help. the guy had some problems with lgup.
http://forum.xda-developers.com/showpost.php?p=64762900&postcount=2915
wohooo....
latest CM13 nightly works...
So the problem is the ROM...
r0tati0n said:
wohooo....
latest CM13 nightly works...
So the problem is the ROM...
Click to expand...
Click to collapse
No offense but you are totally INCORRECT my friend, there is no ROM problem. You have been answered to your problem in the original thread, me one of who answered to your issue. Please, report there if you downloaded the full v1.3 rom or just thev 1.4 update.
Thanks
I reflashed N&N 1.3 again, after CM13 (Wipe of course).
The problem happened again.
flashed CM13 again - no white screen.
I installed 1.3 and then 1.4 update, second try only 1.3.
To me: It is the ROM.
r0tati0n said:
I reflashed N&N 1.3 again, after CM13 (Wipe of course).
The problem happened again.
flashed CM13 again - no white screen.
I installed 1.3 and then 1.4 update, second try only 1.3.
To me: It is the ROM.
Click to expand...
Click to collapse
Sorry to hear that my friend.
Best of luck.
Works again....
What did I do?
Flashed original MM using LGUP and 0.5 DLL using these drivers:
http://download1443.mediafire.com/4grbrdu70t6g/yb4z4zereo3ax4g/LG-Mobile-Driver_v4.0.3.0.zip
Full Reset in LGUP.
TWRP gone. KingRoot installed, rooted.
AutoRecMMD855 installied, this installs TWRP from the system.
booted into TWRP, flashed TWRP again for security using original img.
flashed N&N 1.4, 1.5, flykernel, xposed and xpirt fix.
Only Odysseus Odyssey was longer
Not my work but it works now.
How to
Reboot in recovery
Wipe device
Flash Rom and kernel:
Download for rom:
Flash this after:
Reboot
Recommend using twrp 3.0.0.1
what about the hardware keys? do they work with moar rom and this kernel or do we need virtual hardware keys?
FingerBlastJ said:
what about the hardware keys? do they work with moar rom and this kernel or do we need virtual hardware keys?
Click to expand...
Click to collapse
Kernel fixes hardware issues
and if I'm on note 5 moar rom with patch.... no issue flashing right?
Sky-high made us a kernel? Sweet sadistic smiles, success! So happy. Anyone know if it'll work like the LP patch did for note roms, or does more need to happen first? Or do people just need to start trying and report back?
-edit-
Clicked the link and saw it was a note 5 Rom. What can I say, I was excited!
Blzfrost said:
Sky-high made us a kernel? Sweet sadistic smiles, success! So happy. Anyone know if it'll work like the LP patch did for note roms, or does more need to happen first? Or do people just need to start trying and report back?
-edit-
Clicked the link and saw it was a note 5 Rom. What can I say, I was excited!
Click to expand...
Click to collapse
Just flash Rom and kernel everything will work.
MonkeyAround said:
Just flash Rom and kernel everything will work.
Click to expand...
Click to collapse
Oh I'm setting everything up right now for the flash! I'm so excited. Once I realized you linked to a note 5 Rom most of my questions got answered. My favorite part, the kernel was posted on my bday.
i tried wiping and clearing cache then flashing the rom and the kernel. nothing actually happens to my phone. i end up on the same home screen and apps i had installed on moar 5.1.1 with note 5 patch.
any ideas why wiping my phone doesnt work on twrp 3.0.0.0?
FingerBlastJ said:
i tried wiping and clearing cache then flashing the rom and the kernel. nothing actually happens to my phone. i end up on the same home screen and apps i had installed on moar 5.1.1 with note 5 patch.
any ideas why wiping my phone doesnt work on twrp 3.0.0.0?
Click to expand...
Click to collapse
Update your TWRP.
https://dl.twrp.me/zenltespr/
yea I tried doing that with Odin and it would freeze mid way. I also tried flashing a twrp update zip file on twrp and that didn't work either.
you think I should flash with flash fire?
bricked my phone by trying to flash newer version of twrp with twrp manager
been trying to flash unbrick tar and pit file to get back up and running but its not working.
any help is much appreciated
fixed the brick by flashing new recovery in Odin, now on 3.0.2. still can't get the phone to wipe out install new rom and kernel
FingerBlastJ said:
fixed the brick by flashing new recovery in Odin, now on 3.0.2. still can't get the phone to wipe out install new rom and kernel
Click to expand...
Click to collapse
Have you checked for root with root checker? I have lost root access a few times in the past?
yea I just checked with root checker and I have root access.
I've never had this happen to me... weird
anything else you can think of?
FingerBlastJ said:
yea I just checked with root checker and I have root access.
I've never had this happen to me... weird
anything else you can think of?
Click to expand...
Click to collapse
Last thing I can think of is when opening TWRP the first time. It asks if you want to make the system 'read only'. Did you select No?
I never got that message when I flashed twrp 3.0.2 to unblock... how do I make it show up?
FingerBlastJ said:
I never got that message when I flashed twrp 3.0.2 to unblock... how do I make it show up?
Click to expand...
Click to collapse
Not sure. You can click mount and see what is mounted. I am not sure that will work. I am not sure exactly what you are trying to wipe, but mount the items you are attempting to wipe and make sure the read-only is unchecked.
Try this:
Check to see if oem is checked
Re-root via root tar/odin
twrp 3.0.0.1 from edge files post in general
Backup stock
Wipe
Flash Moar
Don't reboot
Flash skyhigh kernel
Flash xposed(don't have to)
Reboot
Allow it to boot loop a couple time (from sky kernel)
Give 5-10 minutes to boot
I just did it with no issues and I've personally had more luck with 3.0.0.1 than any of the others.
heres my issue...twrp doesnt do anything for me (all versions) whether i wipe or install
so i used flashfire to flash the rom and the kernel at once and it finally displayed aroma installer (wouldnt get that in twrp)
however, after it in stalled i got stuck on boot screen
the only fix for this was flashing unbrick aok3 tar file which brought me to stock
i put on twrp as a recovery again starting fresh unrooted and it still doesnt respond to any of my commands
i think i will try flash fire on stock one more time and see what happens since its the only thing that is responding
FingerBlastJ said:
heres my issue...twrp doesnt do anything for me (all versions) whether i wipe or install
so i used flashfire to flash the rom and the kernel at once and it finally displayed aroma installer (wouldnt get that in twrp)
however, after it in stalled i got stuck on boot screen
the only fix for this was flashing unbrick aok3 tar file which brought me to stock
i put on twrp as a recovery again starting fresh unrooted and it still doesnt respond to any of my commands
i think i will try flash fire on stock one more time and see what happens since its the only thing that is responding
Click to expand...
Click to collapse
Your on Lp bootloader that's your issue.
Download Marshmallow tar from the general post I made for rooting Bpg1.
Flash tar and follow post.
twrp. 3.0.x.x is more for marshmallow. You need to be on 6.0.1 not 5.1.1.
Don't use fireflash on this device.
Fireflash is more for phones with locked bootloaders like Verizon s4 on the of1 update.
Fireflash isn't really up to date with our phone and could easily brick your device.
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
I recently flashed v30b on my D855. I did a clean (CSE) flash with the LG flash tool 2014 and rooted the device with KingRoot. But every time I reboot I lose root acces.
I installed the bump'd version of TWRP with flashify, but when I try to boot into TWRP I get a MISMATCH_SIG_LEN error before the screen goes black and the led starts blinking. I then pull out the battery to start over with a fresh unrooted phone. I think I loose root acces before entering recovery or something. I did some searching, but the only solution I found was to do a clean install, which I already did.
My goal is to install TWRP to flash custom ROMs. How do I fix this?
I think that after installing root with kingroot you will need to perm root it. Kingroot is only temporaty and even if you uninstall it you get unrooted.
Nikolatas said:
I think that after installing root with kingroot you will need to perm root it. Kingroot is only temporaty and even if you uninstall it you get unrooted.
Click to expand...
Click to collapse
I'm having a sort of similar problem on my D85130d. I downgraded fine from 30g to 30d with LGUP. downloaded kingroot and rooted. That was all good. Installed TWRP and flashed the recovery rom and was able to make a backup of my current stock rom (which has saved my life because I think I've soft bricked my phone about 4 times trying to permanent root hahah). Since I AM new to rooting I think I'm missing a certain step, (or maybe the zips im trying to flash are corrupt?) Basically, tried https://forum.xda-developers.com/tm...wngrading-rooting-t3608851/page3#post74961164 and I've also tried https://forum.xda-developers.com/tm...ock-d851-30d-kdz-flashable-zips-imgs-t3367371. The problem with the first one is its not completely specific and like I mentioned before, I'm a white belt at rooting lol. The second thread gave me hope and i do have TWRP installed so I downloaded the 2 main zips I would need (a. LG-D85130D-Flashable.Boot-AUTOREPACK.zip
and b. SuperSU zip) reboot to recovery and flashed both zips separately then reboot. But I end up with a TMO screen and it stays like that. This last time I even left it loading on that screen for about 2 hours and no such luck. I'm wondering is there something I'm missing? Any help would be greatly appreciated from the XDA gods
HingleMcCringleberry said:
I'm having a sort of similar problem on my D85130d. I downgraded fine from 30g to 30d with LGUP. downloaded kingroot and rooted. That was all good. Installed TWRP and flashed the recovery rom and was able to make a backup of my current stock rom (which has saved my life because I think I've soft bricked my phone about 4 times trying to permanent root hahah). Since I AM new to rooting I think I'm missing a certain step, (or maybe the zips im trying to flash are corrupt?) Basically, tried https://forum.xda-developers.com/tm...wngrading-rooting-t3608851/page3#post74961164 and I've also tried https://forum.xda-developers.com/tm...ock-d851-30d-kdz-flashable-zips-imgs-t3367371. The problem with the first one is its not completely specific and like I mentioned before, I'm a white belt at rooting lol. The second thread gave me hope and i do have TWRP installed so I downloaded the 2 main zips I would need (a. LG-D85130D-Flashable.Boot-AUTOREPACK.zip
and b. SuperSU zip) reboot to recovery and flashed both zips separately then reboot. But I end up with a TMO screen and it stays like that. This last time I even left it loading on that screen for about 2 hours and no such luck. I'm wondering is there something I'm missing? Any help would be greatly appreciated from the XDA gods
Click to expand...
Click to collapse
To be fair, i perma rooted the v30B variant. Im not sure bout the D. I rooted it with kingroot, installed TWRP via autorec, i went in recovery and flashed the file thats in the post, rebooted and then installed supersu from the playstore and im perma rooted. After that kingroot is gone and you are left with supersu. This is the guide i followed https://forum.xda-developers.com/lg-g3/general/root-twrp-marshmallow-d855-30b-t3286268