Database Users

Help with rooting G906S Marshmallow 6.0.1 (tried CFire, TWRP and kingroot)

Hi, I've just recently switched over from iphone to android so I'm still new to the whole system. Anyway I've been trying to root my phone for the past 2 days to no avail so I'm at my wits end here. Before I start my phone is from korea which I don't know if whether or not impacts its ability to be rooted, I've done all the basics like enable USB debugging from dev mode, install samsung usb drivers, open ODIN in admin mode and allow MTP to computer. My Device details are below:
>Baseband version : G906SKSU1CPF1
>KERNEL : 3.10.40-8533426
>BUILD NUMBER : MMB29M.G906SKSU1CPF3
So anyway I first tried flashing using CF autoroot for sm-G906S with odin which while it said it was passed and was successful on pc it would be stuck on the samsung logo with a message at the top left that said :
>Recovery booting
>Recovery is not seandroid enforcing
>set warranty bit recovery
So then I tried flashing TWRP custom recovery and putting Super user zip in the internal storage which although got my phone back to working order still wouldnt let me root as the process required me to go to recovery mode from the fastboot mode after it was done flashing (I tried both with and without autoreboot), however once the flashing was done on fastboot I couldn't get to recovery mode no matter how long I held the Vol up/power/home button combination and when i tried it after rebooting it would show normal recovery mode hence there was no way to install the Super User. (Also attempted this with phils recovery)
I then tried to do the TWRP method using adb with command prompt however it would get stuck saying waiting for device when i tried to flash and needless to say kingroot also failed.
At this point as far I've gone through all the methods I could find for my particular device. Would greatly appreciate any insight or advice regarding this problem.
Thanks

start reading from here http://forum.xda-developers.com/gal...ner-thread-t2807639/post68725608#post68725608

Bootlooping to Factory reset status

Hello,
I'll try to detail as much as I can to explain how i ended up Bootlooping :
I tried today to root my LG H870. (imported from Germany, according to the seller).
I followed the tutorial on xda to unlock the Bootloader on the device.
After flashing it, it launched Android the 1st time without difficulties.
I rebooted into TWRP, flashed supersu, then rebooted into Android. Problems started there, the system told me my partition was encrypted, and asked if i wanted to reinitialize it. After doing so, it's been stuck, bootlooping to TWRP, the internal partition empty.
I followed numerous tutorial on how to flash a stock ROM through TWRP, Fastboot, ADB Sideload, without any success.
With TWRP, it was always ending up saying the flash wasdone, without writing a single file in the partition.
I also tried installing stock ROM with LGUP, but once again, didn't seem to work. While in download mode, it was either telling me the phone was an unknown model, on port COM3, or that there was no handset connected.
I then followed another guide, using LG Firmware Extract and LG Flash Tool. It didn't work as expected, but, I don't really know how, it made LGUP seeing my phone correctly. I was then able to flash a stock ROM (H87010f). No error during the process.
After the LG Logo, i get now a blue screen, saying for some seconds "Encryption Progress", and after that "Factory Reset Status", with a big red "2", and it gets stucks there.
Once again, if I get into download mode and into LGUP, i get now the "no handset connected" message.
Is someone on here able to help me?
If more infos are needed, tell me, i'll try to answer!
Thank you all!

Possibly Dead Device? [P8/P9 Lite (2017)][PRA-LX1]

Urgent help needed as I'm leaving the country at the end of the week o any help is appreciated!
Just successfully rooted my device:
Black, Unlocked, PRA-LX1, UK, Dual SIM
After doing so successfully, I attempted to flash LineageOS from the following link:
https://forum.xda-developers.com/p8lite/p8-lite-2017-development/rom-lineageos-15-1-hi6250-devices-t3811583
Although when I completed Step 6 on the Installation guide and rebooted the phone, I started seeing the message:
------------------
ERROR MODE
Attention!
Please update system again
(Green Android picture)
Error!
Func NO : 11 (recovery image)
Error NO : 2 (load failed!)
------------------
Despite this, I didn't receive a box with my phone due to being second hand, and I didn't see the model number on the receipt as it was from a reselling store. I didn't remember to note down the specific model number
It'd be extremely helpful if someone could possibly help just from the device description above as I'm not sure if it's safe for me to just attempt to flash every stock rom for every other LX1 device out there.
---------------------------------------------------------------
Update:
To restore this, I connected via fastboot with a working USB & flashed an original stock recovery in the video found here
(Just in case their download link ever goes down, I have uploaded the same copy to my MEGA, found here)
The recovery installed fine when using the command
fastboot flash recovery oeminfo.img
Click to expand...
Click to collapse
Whenever trying to flash any other recovery such as twrp before this fastboot stuck on a loading icon.
The stock recovery seems to be downloading the original firmware, too.
PRA-LX1C432B202 is presumably the model.
Both the bootloader and FRA were unlocked when everything else was inaccessible.

Looks like the custom ROM's recovery that you've flashed is not compatible with PRA-LX1. Try to flash stock recovery. If not working, then flash stock firmware.

Thanks @Botar230!
I didn't see your comment until just now after deciding to edit this post since I've gotten a step closer to restoring my device.
Your solution was the method I used although I didn't know my phone model, so I found a random solution which just worked for my device, and the eRecovery seems to be downloading the stock firmware anyways. Thanks again

Before flashing this lineage os you should update to EMUI8 to get treble support, i suppose you was running EMUI5, hence the error mode.

Stuck with TWRP and unlocked bootloader. Unknown device in LGUP

Alright so this has happened
I was all a happy guy on H915_10e rooted rom on my H910PR when I decided to my destruction, flash Lineage 15.1 with second screen support as well as trying out gamma kernel for second screen. Turned out xda's dl server crapped on me by refusing to letting me download the SS gamma kernel for LOS 15.1
I ended up flashing x86cpu's LOS15.1 and then after a day I only observed phone lasting me 6-8 hrs due to the greyed out NFC and no option to get the problem sorted out (seemingly I am the only one having this issue).
So all I had to do was flash stock kdz again and start from zero to dirtysanta H915 rom
I have sold my PC and thus am left with two laptops (both have USB 2.0 as well as USB 3.0 ports).
I first installed LG drivers WHQL v4.2.0
Then I installed LG UP v1.14.3
Then I extracted the patched LGUP in correct folder (double checked)
I put my phone to download mode and connected > it gets recognized in device manager.
Now when I try to run LGUP, it says unknown in device model and shows me H915_10e (surprisingly enough its running on lineage 15.1 H910 with gamma kernel). It doens't let me proceed further. Even after using uppercut
I tried the guide to unbrick in LG G5 forum which basically follows LG Flash tool route which failed for me too.
After that I looked if I could get to TWRP and yes I could, as well as the engineering boot is still there (fastboot commands work).
Now that I do have full flashable image of H910_10r from brian's guide to root, when I try to reboot after flashing TWRP gives me an error that no OS is installed and I get stuck at LG Logo (not even the warning screen).
I tried flashing Super V20 rom as well and ended up in the same den. I havent tried to flash LOS back but that's of no use to me (battery nightmares).
Whats the valid route here to get back to my H915 or H910PR rom ? LGUP isn't working for me despite being patched
-Thanks

Put that h910_10r zip along with Magisk onto an SD card. In TWRP, wipe everything / format data, then put the SD card into the phone, and flash that zip. Once flashed, flash Magisk.
Before you reboot, make sure that data and system are mounted, unmount them (uncheck them), and then mount them again.
-- Brian

runningnak3d said:
Put that h910_10r zip along with Magisk onto an SD card. In TWRP, wipe everything / format data, then put the SD card into the phone, and flash that zip. Once flashed, flash Magisk.
Before you reboot, make sure that data and system are mounted, unmount them (uncheck them), and then mount them again.
-- Brian
Click to expand...
Click to collapse
Did so, before rebooting TWRP asked me that there is no OS installed.
Surprisingly after every flash process I checked in download mode if there is any sign of identification.
I ended up flashing full stock H910 10q through TWRP, still the phone said there is no OS installed. The same error popped up when I flashed super v20 full stock H910 too.....
welp, now I'm with locked bootloader with Firmware update screen showing me "633A B50" in the information and stuck at 0%
LGUP still identifies as unknown device. Looks like I've ended up in the same basket as some of the fellows who got stuck with disfunctional download mode. I'll try tomorrow if I get to buy another Type-C cable although phone identifies correctly even in LG Flash tool (the identifier worked as H915 before, then changed to H910PR when I tried the H910PR kdz on provision of LGUPc.dll from extracting the kdzs.
I can't do anything except charge phone and if I try to power it on, its stuck on LG Logo (no warning screen whatsoever and there is no going back to TWRP as of now.
I even tried kdzwriter and it just remaining blank on the kdzwriter commands despite I could see kdzwriter in sbin directory and manually setting permissions to 755 through twrp file manager, still it did nothing.

Also, the bloody funny thing is, LGUP still recognizes as H91510e while LG Flash Tool recognizes phone as H91010q as well as shows LG-H910 on the phone firmware update status log. Something from full stock H91010q didn't erase that info as well

Wait, how do you know you still had the engineering bootloader other than the fact that you could boot to TWRP?
If you had no warning screen, then you probably didn't.
You may have bricked your phone, but we may be able to learn something.
Edit: FYI .. you still may not have bricked your phone yet if you still have download mode.
EDIT2: If you want to save your phone, don't do anything else for now.... read the laf development thread, not the lafsploit thread....
-- Brian

runningnak3d said:
Wait, how do you know you still had the engineering bootloader other than the fact that you could boot to TWRP?
If you had no warning screen, then you probably didn't.
You may have bricked your phone, but we may be able to learn something.
Edit: FYI .. you still may not have bricked your phone yet if you still have download mode.
EDIT2: If you want to save your phone, don't do anything else for now.... read the laf development thread, not the lafsploit thread....
-- Brian
Click to expand...
Click to collapse
When I had engg bootloader (which facilitated all fastboot commands we need to flash modem recovery blahblah etc) and TWRP, the phone sat on LG Logo all the time if I did a normal bootup or reboot through recovery.
The warning screen only poppped when I used the enter recovery combo.
Also H910_10m has something different than H910_10r.
The warning screen on 10r is perfectly crisp and clear but the warning screen on H910_10m firmware is distorted all accross the screen with parts of it horizontally distributed all over and wrapped around.
Rigth now:
I have working download mode and only way the phone talks a little bit (mamma papa of a baby maybe) is through LG Flash tool when I give the LGUP.dll and a kdz to flash to it. It says its an LG-H910 on download mode status screen and says two lines about H91010r and the next line as the line of the firmware I'm trying to flash, here in my case those are H91510e and H910PR10j.
I can even go to factory reset screen and the nice circle spins saying to me erasing but it reboots back at LG Logo
I have full dump of my H910PR but that's useless if LGUP doesn't recognize my phone.
TLDR as of Now: I'm going to install Windwos 7 on my older Lenovo x230 Laptop and start from scratch. I believe there is a bad driver footprint left somewhere in this windows 10 and I hate windows 10's communication trouble with third party devices.
Will keep you updated via this thread. I hope I do not annoy you too much with my post backs

Bump! No chance. Stuck in same situation but now I have only access to download mode or factory reset (since I'm on stock H910 10q firmware). LGUP says unknown with H91510e while LG flash tool says it's H91010q. Can't flash sh**.... I've ordered a replacement H910 motherboard and it's gonna arrive in 15 days give or take. Will see if I can swap connection Midway in LGUP and flash this one to stock H910PR

K20 plus kernel panic - not syncing

Though I have some experience with rooting phones and flashing custom rooms, I still consider myself to be no more than a novice in this subject. I have a LG K20 PLUS, metro pcs, and I have it rooted running PBRP recovery and the unofficial lineage 14.1 rom. I have been trying different roms and just recently kernels. I was trying to get kali nethunter working and on here at xda two files that I could flash to install it. I will have to go and look to get the names right but one was something like kali nethunter generic rolling something and the other was a custom kernel to complement it. Both flashed without any errors. When I rebooted, after the LG logo I found myself with a kernel panic error.
Kernel crash!
DemiGod Handler : Kernel Crash!
If you want to get ram dump,
Please do following action.
1) Dload Mode. Please connect USB.
2) Get ram dump image using QPST Configuration.
Board Info : 6
rev. : 1.0, cx_pvs: 1 mx_pvs: 1
serial : aadd87fc0000000
secure boot : enabled
[ 4.000591 / 01-01 00:00:07.439][3] Kernel panic - not syncing: adsp_loader_do: pil get failed.
Jump to Bload Mode.
I am still able to enter revory mode and through recovery boot to bootloader. I had attempted reflashing the recovery to TWRP, which was successfull, but attempting reflashing kernels (though flashing without errors) has had no effect on the kernel panic issue. I have reflashed roms as well, it seems nothing that I know how to do will fix the problem. Surfing the web for answers... has only shined light on just how little I understand a lot of this stuff. Most information ℹ have been able to find (in a lot of cases I don't even know if it applies to my specific problem) is way beyond my technical ability to comprehend. I hope that someone here can guide me through this panic and help get my K20 plus functional again. :fingers-crossed:

You're gonna need a PC with LG Windows USB drivers, LG UP v1.14, as well as LG Uppercut 1.0 which is a modified version of LG UP, and a stock .kdz image to reflash your phone back to stock. You can find those links on this forums or other LG phones threads. I'm pressed for time so I can't link them all. I've had a similar issue with kernel panic where flashing any ROM or kernel couldn't fix the issue. The only thing I could do was flash a stock image so that the partitions could be overwritten and corrected. You can find the LG stock image here https://lg-firmwares.com/lg-mp260-firmwares/#tab=firmwares I suggest an older variant like 10j or 10v, though I've had success installing 11k and reverting to 10j but I'm not certain if the newer images have any code that makes it more difficult to modify bootloaders or revert to older stock versions. MTP is your ideal image. MTD is a Metro Demo and MTK are FRU (field replaceable unit) images with some capability of having special resizable partitions but that goes beyond my understanding and scope of this post.
There's a chance you'll find Download mode on your phone doesn't stick to more than 20 seconds or so, which isn't enough to flash an image without issues. I found the fix for this was to go into recovery and wipe everything you're allowed to wipe, recovery will caution there is no operating system installed. That's fine. Rebooting to system should lead to a similar warning on boot. Custom Recovery should still work but you won't need it. You'll need to get back to download mode, plug the phone to the computer, and be sure it is recognized by Device Manager along with a COM port number associated to it. LG UPPERCUT should then be able to see the phone model and COM port and launch, it won't launch otherwise. Once LG UP is running, load up the .kdz image and click UPGRADE. As long as your phone is able to remain in Download mode for more than 30 seconds you're good. If it continues to reboot short of that, give it another thorough wipe in custom recovery.
Once you have flashed stock, you can go back to adb or fastboot and reflash a custom recovery and root program as you did initially. Your bootloader should still remain unlocked after flashing stock so there's no need to run fastboot oem unlock commands again.

CabbyKing said:
Though I have some experience with rooting phones and flashing custom rooms, I still consider myself to be no more than a novice in this subject. I have a LG K20 PLUS, metro pcs, and I have it rooted running PBRP recovery and the unofficial lineage 14.1 rom. I have been trying different roms and just recently kernels. I was trying to get kali nethunter working and on here at xda two files that I could flash to install it. I will have to go and look to get the names right but one was something like kali nethunter generic rolling something and the other was a custom kernel to complement it. Both flashed without any errors. When I rebooted, after the LG logo I found myself with a kernel panic error.
Kernel crash!
DemiGod Handler : Kernel Crash!
If you want to get ram dump,
Please do following action.
1) Dload Mode. Please connect USB.
2) Get ram dump image using QPST Configuration.
Board Info : 6
rev. : 1.0, cx_pvs: 1 mx_pvs: 1
serial : aadd87fc0000000
secure boot : enabled
[ 4.000591 / 01-01 00:00:07.439][3] Kernel panic - not syncing: adsp_loader_do: pil get failed.
Jump to Bload Mode.
I am still able to enter revory mode and through recovery boot to bootloader. I had attempted reflashing the recovery to TWRP, which was successfull, but attempting reflashing kernels (though flashing without errors) has had no effect on the kernel panic issue. I have reflashed roms as well, it seems nothing that I know how to do will fix the problem. Surfing the web for answers... has only shined light on just how little I understand a lot of this stuff. Most information have been able to find (in a lot of cases I don't even know if it applies to my specific problem) is way beyond my technical ability to comprehend. I hope that someone here can guide me through this panic and help get my K20 plus functional again. :fingers-crossed:
Click to expand...
Click to collapse
Any updates? Were you able to get your phone up and running?