Related
For some reason I'm just not able to Google this answer or find it here on XDA.
I'm on 5.0.1 (LRX22C) and want to go to 5.0.2 (LRX22G). I have downloaded an OTA update capture and tried to adb sideload it.
It failed. After a sec I thought, "duh. I'm rooted with franco kernel installed." I then did the following:
* Used SuperSU to unroot
* Booted to bootloader
* Flashed stock recovery and kernel
* Rebooted to recovery
* Attempted adb sideload again
This still gave a failure message.
The only other post I've seen where anyone is attempting the same suggests to use Nexus Root Tookit. I'm running Xubuntu. I've loaded it through wine but all the files it downloads are failing hash checks (though the app).
Can anyone post how to go from rooted 5.0.1 to 5.0.2 (LRX22G from LRX22C) without loosing user land data? I'd really do not want to flash the recovery image.
Notes: When trying to sideload with latest CWM recovery the script says that I'm on 4.0.4 (I think) and with TWRP it says I'm on 4.3. With stock recovery it gives me an error about the recovery script (7) or something similar.
Thanks,
Mike G.
Make sure you have downloaded the proper OTA for Nexus 7(2013).
Hashcheck fails in Nexus Root Toolkit is common.After Hashfails,there will be a dialog box which contains the steps to do it manually with the Link to the files.Download it & follow the instruction.
I hope this helps
I'm having the exact same problem. I'm attaching what's appearing on TWRP.
All you need to do is flash the boot and system.img
Then flash su from twrp. It's that easy. No data loss.
I just used wugfresh's toolbox to do it. A piece of cake. I enjoyed a cup of coffee while I watched being updated.
You can also use TWRP and dirty flash the stock, rooted rom by Scrolser found here: http://forum.xda-developers.com/nex.../rom-factory-stock-rooted-rom-lrx22g-t3004110 . Simple and fast with no data loss.
yosmokinman said:
All you need to do is flash the boot and system.img
Then flash su from twrp. It's that easy. No data loss.
Click to expand...
Click to collapse
So I can just ”fastboot flash system system.img" from the 5.0.2 image and not loose data?
That seems like it would be the easiest. I prefer the adb/fastboot commands as NRT hides what it is doing and I like to know what's going on when I "do something" liken push a button.
Sent from my Nexus 7 using XDA Free mobile app
^Yes. It's a good idea to flash boot as well just to get in the habit of it, it didn't change this time I don't think but I could later. Only flash the bootloader if it's a new version no need otherwise.
I simply ran:
fastboot flash system system.img
fastboot flash boot boot.img
fastboot format cache
Done, flash su through twrp to get root back.
You probably don't need to format cache but theres no reason not to and it could save you some trouble.
newkydawg said:
You can also use TWRP and dirty flash the stock, rooted rom by Scrolser found here: http://forum.xda-developers.com/nex.../rom-factory-stock-rooted-rom-lrx22g-t3004110 . Simple and fast with no data loss.
Click to expand...
Click to collapse
that worked perfectly for me. thx
mikejr83 said:
I prefer the adb/fastboot commands as NRT hides what it is doing and I like to know what's going on when I "do something" liken push a button.
Click to expand...
Click to collapse
NRT opens a terminal window (a real-time log) and tells you exactly what it's doing while it does its work.
All you need to do is flash the boot and system.img
Then flash su from twrp. It's that easy. No data loss.
Click to expand...
Click to collapse
I have a n7 2013 I have already rooted and installed twrp and SuperSU. I'm currently running 4.4.2 and to update to 5.02. Currently I'm getting the ota update msg for 4.4.3 which I've continued to ignore. With google not messaging me to update to 5.02 makes me think it's required to go to 4.4.3,4.4.4,5,5.02 is that correct? Or can one jump directly to 5.02? I want to keep root and twrp and my existing data I see mentioning of restoring stock recovery first. Why would one do that? What's the point of installing a custom recovery in the first place?
Long time ago I read that ota will work when rooted, but you'll lose root which then can be restored with twrp without losing data. Is that no longer true? Or is it only true of KitKat but not lollipop?
HI everyone.
Today, I managed to root my LG G3(D855) that is on the Lollipop version(OTA update).
The reason for this root was to flash the cyanogenMod 12 rom. I found out that I needed a bump'd twrp recovery image which I got from this page:
I tried using flashify to flash this image which flashify claims was a success but when I try to boot into recovery, it gives me a "Secure boot error" message.
does the same methods that apply for flashing custom recovery in android 4.4.2 on LG G3 not apply to Lollipop versions?
if I do a battery pull and boot up the device normally, the device seems to work alright but I can't boot into recovery.
So, please I need help as I want to install this CM12. it bothers me a lot that my nexus 7 seems faster than my G3
-- Problem Solved---
I was able to fix this problem and booting into a custom recovery by going through this thread: http://forum.xda-developers.com/lg-g3/general/guide-update-to-lollipop-root-bumpd-twrp-t3048845
Here are the files I used:
"aboot.img" from a kitkat D855 stock rom. (here is the one I used https://docs.google.com/file/d/0B7fkQwhNpU7YNTdfZUQyZlQzLTA)
oversharpening fix flashable zip (here is the one I used http://forum.xda-developers.com/lg-g3/orig-development/fix-sharpening-mod-script-1-0-beta-t2957648 used the latest version at the time of posting.)
a bump'd twrp recovery image for D855 from here: http://downloads.codefi.re/thecubed/lg_g3/bump/
kikat bootstack from here for D855: https://www.androidfilehost.com/?fid=95916177934540501
after getting all these files, move it to the root folder of your SD card.
attempt the process below at your own risk
Here is how I used the files:
I first used flashify (download from play store) to install the bump'd twrp recovery.img.
Then using android terminal emulator (download from play store) I ran this command
Code:
su [b](no need to retype this if you did not exit from the previous Android Terminal session)[/b]
dd if=/dev/block/platform/msm_sdcc.1/by-name/aboot of=/sdcard/lollipop-aboot.img [b](this makes a backup to your Internal Storage)[/b]
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/aboot [b](writes “zeroes” to the partition to “wipe” it out)[/b]
dd if=/sdcard/aboot.img of=/dev/block/platform/msm_sdcc.1/by-name/aboot [b](flashes the Kitkat version aboot.img to the aboot partition)[/b]
from this post: http://forum.xda-developers.com/showpost.php?p=59353812&postcount=44
I then reBooted my device into recovery mode which of course now has become TWRP recovery.
in the twrp recovery I flashed in the oversharpening fix.zip file (I was prompted during the installation to choose a sharpening level, I chose 5. this value doesn't have anything to do with the recovery process, we just need it to bump the lollipop boot.img)
After that, I flashed in the Kitkat boot stack and then rebooted my device.
that's it. I am on CM 12 now. Good luck.
and of course, credit goes to this user: @topet2k12001. He is a G3 superhero.
same
Hey ,i got the same problem ,just rooted my d855 and i want to flash a custom recovery so i can install xposed ,but after flashify reboots the device i get the same message...plz reply me if u found a solution
N00R28 said:
Hey ,i got the same problem ,just rooted my d855 and i want to flash a custom recovery so i can install xposed ,but after flashify reboots the device i get the same message...plz reply me if u found a solution
Click to expand...
Click to collapse
I did but it was a very complex solution. see http://forum.xda-developers.com/lg-g3/general/guide-update-to-lollipop-root-bumpd-twrp-t3048845
I am yet to attempt that.
Causes of "Secure Boot Error"
Hi Friends,
"Secure Boot Error" and "Certification Verify" are already "known" errors, and by "known" it means that the causes are already well-established and therefore, can be fixed.
Please visit my thread and read the very first post at Page 1, for the following topics:
1. "The Logic Behind It All"
2. "Troubleshooting and "Q&A"
Heads up: I'm not the type of member who will give a straight answer, so please expect my how-to and posts to be very wordy. I want fellow members to understand what they are doing, not just tell them what they are doing (teach people how to fish, not just give them fish - so to speak).
Sent from my LG-D855 using XDA Free mobile app
Yeah i saw that solution but the kdz extracte thread is not that detailed ...tnx tho
N00R28 said:
Sent from my LG-D855 using XDA Free mobile app
Yeah i saw that solution but the kdz extracte thread is not that detailed ...tnx tho
Click to expand...
Click to collapse
Hi @N00R28,
I agree. That's why I wrote a detailed version of it in my how-to guide.
Sent from my LG-D855 using XDA Free mobile app
Hey,tnx but i will wait for an easier solution ,i would like to do the complicated way as its fun to do but i have exams and dont have much time ,so im gonna wait for something fast and easy :
But may i ask why these problems with lg g3 lollipop?all nexus and Samsung devices r easier and been there since the lunch of lollipop,even rooting g3 was a pain untill last week
N00R28 said:
Sent from my LG-D855 using XDA Free mobile app
Hey,tnx but i will wait for an easier solution ,i would like to do the complicated way as its fun to do but i have exams and dont have much time ,so im gonna wait for something fast and easy :
But may i ask why these problems with lg g3 lollipop?all nexus and Samsung devices r easier and been there since the lunch of lollipop,even rooting g3 was a pain untill last week
Click to expand...
Click to collapse
The explanation is in my how-to thread, Page 1.
I created an easy solution already as well, it's in my how-to thread. I created a script called "Imageprep". It only requires typing a single command in the Terminal. You must have not read the guide fully so you might have missed it. Understandable because you said you have exams.
Sent from my LG-D855 using XDA Free mobile app
Ohh cool ,tnx will check it out tomorrow
N00R28 said:
Hey ,i got the same problem ,just rooted my d855 and i want to flash a custom recovery so i can install xposed ,but after flashify reboots the device i get the same message...plz reply me if u found a solution
Click to expand...
Click to collapse
I was able to decipher the parts I needed in that thread. see my first post for the solution I used.
lordzouga said:
I was able to decipher the parts I needed in that thread. see my first post for the solution I used.
Click to expand...
Click to collapse
Very good, @lordzouga.
This is the reason why as much as possible, I explain the logic and force other members to understand it first. It makes the process easier for them because they know what they are doing.
The method worked perfectly after i bricked my device for the 1st time (was flashing the wrong recovery)after it worked i noticed most of the apps i need dont run on lillipop (due to devs not upgrading the apps to run with ART) so i downgraded to kitkat ......tnx alot for ur help
Thanks, this method worked perfectly.
Sent from my LG-D855 using Tapatalk
Totally bricked my phone with these instructions Won't turn on anymore. Tried everything...only shows a trinagle if I connect to usb without battery.
Super easy to use thank you buddy:d
SUPER EASY TO USE THANK YOU BUDDY
Please explain about sharpening what it actually do ?? what difference it makes..??
lordzouga said:
HI everyone.
Today, I managed to root my LG G3(D855) that is on the Lollipop version(OTA update).
The reason for this root was to flash the cyanogenMod 12 rom. I found out that I needed a bump'd twrp recovery image which I got from this page:
I tried using flashify to flash this image which flashify claims was a success but when I try to boot into recovery, it gives me a "Secure boot error" message.
does the same methods that apply for flashing custom recovery in android 4.4.2 on LG G3 not apply to Lollipop versions?
if I do a battery pull and boot up the device normally, the device seems to work alright but I can't boot into recovery.
So, please I need help as I want to install this CM12. it bothers me a lot that my nexus 7 seems faster than my G3
-- Problem Solved---
I was able to fix this problem and booting into a custom recovery by going through this thread: http://forum.xda-developers.com/lg-g3/general/guide-update-to-lollipop-root-bumpd-twrp-t3048845
Here are the files I used:
"aboot.img" from a kitkat D855 stock rom. (here is the one I used https://docs.google.com/file/d/0B7fkQwhNpU7YNTdfZUQyZlQzLTA)
oversharpening fix flashable zip (here is the one I used http://forum.xda-developers.com/lg-g3/orig-development/fix-sharpening-mod-script-1-0-beta-t2957648 used the latest version at the time of posting.)
a bump'd twrp recovery image for D855 from here: http://downloads.codefi.re/thecubed/lg_g3/bump/
kikat bootstack from here for D855: https://www.androidfilehost.com/?fid=95916177934540501
after getting all these files, move it to the root folder of your SD card.
attempt the process below at your own risk
Here is how I used the files:
I first used flashify (download from play store) to install the bump'd twrp recovery.img.
Then using android terminal emulator (download from play store) I ran this command
Code:
su [b](no need to retype this if you did not exit from the previous Android Terminal session)[/b]
dd if=/dev/block/platform/msm_sdcc.1/by-name/aboot of=/sdcard/lollipop-aboot.img [b](this makes a backup to your Internal Storage)[/b]
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/aboot [b](writes “zeroes” to the partition to “wipe” it out)[/b]
dd if=/sdcard/aboot.img of=/dev/block/platform/msm_sdcc.1/by-name/aboot [b](flashes the Kitkat version aboot.img to the aboot partition)[/b]
from this post: http://forum.xda-developers.com/showpost.php?p=59353812&postcount=44
I then reBooted my device into recovery mode which of course now has become TWRP recovery.
in the twrp recovery I flashed in the oversharpening fix.zip file (I was prompted during the installation to choose a sharpening level, I chose 5. this value doesn't have anything to do with the recovery process, we just need it to bump the lollipop boot.img)
After that, I flashed in the Kitkat boot stack and then rebooted my device.
that's it. I am on CM 12 now. Good luck.
and of course, credit goes to this user: @topet2k12001. He is a G3 superhero.
Click to expand...
Click to collapse
The reason why recovery wont load if you rooted using LG's lollipop firmware is because they patched the hack that bypasses the Security check. You need to downgrade to kitkat or keep on Lg's lollipop
χχ
My G3 does not start up
lordzouga said:
HI everyone.
Today, I managed to root my LG G3(D855) that is on the Lollipop version(OTA update).
The reason for this root was to flash the cyanogenMod 12 rom. I found out that I needed a bump'd twrp recovery image which I got from this page:
I tried using flashify to flash this image which flashify claims was a success but when I try to boot into recovery, it gives me a "Secure boot error" message.
does the same methods that apply for flashing custom recovery in android 4.4.2 on LG G3 not apply to Lollipop versions?
if I do a battery pull and boot up the device normally, the device seems to work alright but I can't boot into recovery.
So, please I need help as I want to install this CM12. it bothers me a lot that my nexus 7 seems faster than my G3
-- Problem Solved---
I was able to fix this problem and booting into a custom recovery by going through this thread: http://forum.xda-developers.com/lg-g3/general/guide-update-to-lollipop-root-bumpd-twrp-t3048845
Here are the files I used:
"aboot.img" from a kitkat D855 stock rom. (here is the one I used https://docs.google.com/file/d/0B7fkQwhNpU7YNTdfZUQyZlQzLTA)
oversharpening fix flashable zip (here is the one I used http://forum.xda-developers.com/lg-g3/orig-development/fix-sharpening-mod-script-1-0-beta-t2957648 used the latest version at the time of posting.)
a bump'd twrp recovery image for D855 from here: http://downloads.codefi.re/thecubed/lg_g3/bump/
kikat bootstack from here for D855: https://www.androidfilehost.com/?fid=95916177934540501
after getting all these files, move it to the root folder of your SD card.
attempt the process below at your own risk
Here is how I used the files:
I first used flashify (download from play store) to install the bump'd twrp recovery.img.
Then using android terminal emulator (download from play store) I ran this command
Code:
su [b](no need to retype this if you did not exit from the previous Android Terminal session)[/b]
dd if=/dev/block/platform/msm_sdcc.1/by-name/aboot of=/sdcard/lollipop-aboot.img [b](this makes a backup to your Internal Storage)[/b]
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/aboot [b](writes “zeroes” to the partition to “wipe” it out)[/b]
dd if=/sdcard/aboot.img of=/dev/block/platform/msm_sdcc.1/by-name/aboot [b](flashes the Kitkat version aboot.img to the aboot partition)[/b]
from this post: http://forum.xda-developers.com/showpost.php?p=59353812&postcount=44
I then reBooted my device into recovery mode which of course now has become TWRP recovery.
in the twrp recovery I flashed in the oversharpening fix.zip file (I was prompted during the installation to choose a sharpening level, I chose 5. this value doesn't have anything to do with the recovery process, we just need it to bump the lollipop boot.img)
After that, I flashed in the Kitkat boot stack and then rebooted my device.
that's it. I am on CM 12 now. Good luck.
and of course, credit goes to this user: @topet2k12001. He is a G3 superhero.
Click to expand...
Click to collapse
Please help!!! I followed your instructions and as i powered off my phone, now it does not boot up....can't even go to download mode.... please help!!
paragxx said:
Please help!!! I followed your instructions and as i powered off my phone, now it does not boot up....can't even go to download mode.... please help!!
Click to expand...
Click to collapse
Be careful with this thread, it will brick your phone. On the safe side make sure you remove laf partition and fastboot is working. I got mine bricked.
Does it work for Android 5.0 Lollipop or only Android 4.4 Kitkat?
I was running Lam Hoang 2.2 just fine on my D850 and then decided to update TWRP from 2.8.6.1 to 2.8.7.0 (released yesterday). I downloaded the right one. I couldn't get it to flash (using the TWRP app or Flashify) and it kept giving me the secure boot error message at the top left of the screen when trying to go back into recovery (it was booting fine, though).
From the TWRP thread, the app creator posted their app AutoRec (https://play.google.com/store/apps/details?id=b007.autorecd850) and I downloaded it, installed, and ran. It worked. I updated TWRP from within recovery and rebooted...and now I'm in trouble
I can't get into recovery (getting the secure boot error message again) and the phone won't boot normally anymore. I'm getting the LG logo with the words "Security Error" in bold beneath the logo: http://k36.kn3.net/ED11C35D9.png
Thoughts? Did I just brick my phone?
rczrider said:
I was running Lam Hoang 2.2 just fine on my D850 and then decided to update TWRP from 2.8.6.1 to 2.8.7.0 (released yesterday). I downloaded the right one. I couldn't get it to flash (using the TWRP app or Flashify) and it kept giving me the secure boot error message at the top left of the screen when trying to go back into recovery (it was booting fine, though).
From the TWRP thread, the app creator posted their app AutoRec (https://play.google.com/store/apps/details?id=b007.autorecd850) and I downloaded it, installed, and ran. It worked. I updated TWRP from within recovery and rebooted...and now I'm in trouble
I can't get into recovery (getting the secure boot error message again) and the phone won't boot normally anymore. I'm getting the LG logo with the words "Security Error" in bold beneath the logo: http://k36.kn3.net/ED11C35D9.png
Thoughts? Did I just brick my phone?
Click to expand...
Click to collapse
Maybe the recovery was not bump'd?
RapHaeL_4_4_4_ said:
Maybe the recovery was not bump'd?
Click to expand...
Click to collapse
That's possible. I got it directly from here: https://dl.twrp.me/d850/
rczrider said:
That's possible. I got it directly from here: https://dl.twrp.me/d850/
Click to expand...
Click to collapse
I ran into the same issue when i tried to flash the .img file through TWRP.
If you manage to boot your phone normally the you can use the imageprep method to bump the new TWRP version and flash it using the imagepregui. I managed to get 2.8.7 working using this method.
Same Problem "Secure Error"
So my friend I did the same thing as you did and I got stuck and now I cannot use my phone but I may need to go back to stock and then root and get back to AOSP.
I am thinking of maybe there is a recovery.img in the .TOT file and a Boot.img to flash and we may have our phones back in no time, Just maybe.
thefireofwar said:
So my friend I did the same thing as you did and I got stuck and now I cannot use my phone but I may need to go back to stock and then root and get back to AOSP.
I am thinking of maybe there is a recovery.img in the .TOT file and a Boot.img to flash and we may have our phones back in no time, Just maybe.
Click to expand...
Click to collapse
Very possible, but only if you have access to a method you can flash using (such as if you had removed laf and have fastboot)
I believe imageprep makes a backup of your previous files and stores them on your computer even.
But if you can't get into fastboot then you may have to do a factory kdz image
BoredKender said:
Very possible, but only if you have access to a method you can flash using (such as if you had removed laf and have fastboot)
I believe imageprep makes a backup of your previous files and stores them on your computer even.
But if you can't get into fastboot then you may have to do a factory kdz image
Click to expand...
Click to collapse
I am thinking of flashing the files with LG Flash Tool and maybe it will work as i will be extracting the Kitkat TOT file and restore to stock but only flashing the recovery and boot image.
It's possible, I can never get the dang flash tool to see my phone so I can't offer much guidance on that.
I'm thinking the TWRP folks uploaded a non-BUMP'd recovery image to their website...because now 2.8.7.0 is missing from their site and it was definitely there yesterday when I downloaded it: https://dl.twrp.me/d850/. Maybe they never BUMP their images?
I posted in the TWRP thread when it first happened and @bender_007 (maker of AutoRec) reminded me about restoring to stock via download mode and helped me get it back to stock. When I flashed TWRP last night after doing the stock KK > root > install recovery > upgrade to LP process, I used TWRP from @777jon's thread: https://www.androidfilehost.com/?w=files&flid=22377
So yeah, if you're like me and tried updating TWRP using the image from the TWRP site and borked your phone, I'm betting the only way to unbork it is to restore KK stock via the TOT.
Confirmed, it wasn't bumped(while the 2.8.6.0 was)
Poslano sa mog LG-D802 koristeći Tapatalk
Finally
I am back to AOSP after doing alot of "BACK TO STOCK" Now I am Rooted Bumped and AOSPed!!!!!!!!!!!!!!!!!!
Gotta to go back to KitKat to root and Bump " I have tried every Lollipop root method and didnt work for me
YAY!!!!!!!!!!!!
thefireofwar said:
I am back to AOSP after doing alot of "BACK TO STOCK" Now I am Rooted Bumped and AOSPed!!!!!!!!!!!!!!!!!!
Gotta to go back to KitKat to root and Bump " I have tried every Lollipop root method and didnt work for me
YAY!!!!!!!!!!!!
Click to expand...
Click to collapse
search for jac10000 thread in here he and 6ril1 for sure had the sollution for rooting
I have kitkat 4.2.2 stockbase, rooted, trying to install cwm but stuck in the secure booting error boot certification verify.
Previously i installed rom manager app and flash the cwm from the app. After reboot to recovery, only stock recovery that showed, then i reboot to system, install freegee in order to flash the cwm but fail as freegee doesnt support gpro kitkat.
After that i install gpro kitkat recovery and flash the cwm from the app, success, reboot to recovery but stuck on the error.
I uninstalled rom manager and freegee, but still no luck to get the flashed cwm recovery,stuck in secure booting error.
Any suggestion or thread reference? Why is very difficult to install custom rom on this device?i plan to install carbon rom :crying:
Thank you in advance.
hotmatua.parulian said:
I have kitkat 4.2.2 stockbase, rooted, trying to install cwm but stuck in the secure booting error boot certification verify.
Previously i installed rom manager app and flash the cwm from the app. After reboot to recovery, only stock recovery that showed, then i reboot to system, install freegee in order to flash the cwm but fail as freegee doesnt support gpro kitkat.
After that i install gpro kitkat recovery and flash the cwm from the app, success, reboot to recovery but stuck on the error.
I uninstalled rom manager and freegee, but still no luck to get the flashed cwm recovery,stuck in secure booting error.
Any suggestion or thread reference? Why is very difficult to install custom rom on this device?i plan to install carbon rom :crying:
Thank you in advance.
Click to expand...
Click to collapse
Start from 4.1.2 stock, root, use freegee to bypass lockdown, flash latest TWRP then flash Lollipop ROMs... There is info about everything on the forums.
ShadySquirrel said:
Start from 4.1.2 stock, root, use freegee to bypass lockdown, flash latest TWRP then flash Lollipop ROMs... There is info about everything on the forums.
Click to expand...
Click to collapse
Thank you very much Shady.. Please be kindly to review steps that i should execute when flashing to Carbon Lollipop with regards to my current state (rooted 4.4.2. stock Kitkat):
Prerequisite:
- LG Flash Tool 2014 installed in PC
- LG United Mobile Driver (i use v3.11.3) installed in PC
- Stock firmware E98810e_00.kdz (Indonesia Jellybean) -- Jellybean stock base is required to cater modem/wakelock issue
- Stock firmware E98820c_00.kdz (Indonesia Kitkat)
- ROM Manager (for current state backup/restore)
- Freegee (to cater LG security issue after success flash)
- Towelroot (to root device after success flash)
- TWRP (for recovery tool after success flash)
- Downloaded ZeKrnl 1.7 Build 11/28 - https://forum.xda-developers.com/optimus-g-pro/development/rom-e980-ze-krnl-1-6-t3255975
- Downloaded ZeKrnl 1.6 - https://forum.xda-developers.com/optimus-g-pro/development/rom-e980-ze-krnl-1-6-t3255975/page4 (to cater camera issue after flashed to Carbon)
1. Flash CWM via ROM Manager
2 Execute Backup Current ROM to sd card via ROM Manager and save copy to PC
3. Backup manual for files, apks, contacts to sd card and save copy to PC
4. Copy ZeKrnl 1.7 zip & ZeKrnl 1.6 zip to sd card
5. Turn off phone, plug usb cable to phone
6. Press & hold Volume keys (Up + Down) then plug the other end of usb into PC to until download mode showned
7. Run LG Flash Tool with administrator privilege
8. Flash E98810e firmware into the device till success
(After Success Flash to Andro 4.1.2 JB):
9. Install towelroot and root the device
10. Install freegee to cater LG security issue
11. Install latest TWRP
12. Reboot into recovery mode
13. wipe system, data, cache, dalvik cache
14. flash ZeKrnl 1.7
--Camera issue
debug.composition. type=dyn --> debug.composition. type=gpu using build prop editor and/or flash ZeKrnl 1.6 kernell
https://forum.xda-developers.com/optimus-g-pro/development/rom-e980-ze-krnl-1-6-t3255975/page8
--Deep Sleep issue
https://forum.xda-developers.com/optimus-g-pro/development/rom-e980-ze-krnl-1-6-t3255975/page10
-- SD Card issue
https://forum.xda-developers.com/optimus-g-pro/development/rom-e980-ze-krnl-1-6-t3255975/page12
-- Kernel parameter tuning sampel
https://forum.xda-developers.com/optimus-g-pro/development/rom-e980-ze-krnl-1-6-t3255975/page14
Btw looks like you are the only person that still active in this thread...really appreciate it...thank you very much
You're complicating it too much, to be honest
Just do it this way:
1. flash stock 4.1.2 and keep it that way
2. root, install Freegee, install initial recovery (twrp, cwm, doesn't mater), update it to TWRP from forums (2.8 version is preferred)
3. you're ready to flash create stock backup and flash roms.
If I remember, all those changes are already implemented in both SlimLP and Carbon. Slim has newer kernel and gpu drivers, and that's it.
So you are saying i just flash the rom as is without any further change?Noted shady...i will inform you the result
ShadySquirrel said:
You're complicating it too much, to be honest
Just do it this way:
1. flash stock 4.1.2 and keep it that way
2. root, install Freegee, install initial recovery (twrp, cwm, doesn't mater), update it to TWRP from forums (2.8 version is preferred)
3. you're ready to flash create stock backup and flash roms.
If I remember, all those changes are already implemented in both SlimLP and Carbon. Slim has newer kernel and gpu drivers, and that's it.
Click to expand...
Click to collapse
Ive tried your suggestion with the following result:
a. Flash to stock 4.1.2 (v10e) : success but then the master file i downloaded is gone
b. Root, install freegee, initial recovery: success
c. Update to twrp 2.8 using twrp manager: success
d. Flash to Carbon: fail, canot enter recovery mode with message secure booting error,boot certification verify
So i just rollback to kitkat stock
hotmatua.parulian said:
Ive tried your suggestion with the following result:
a. Flash to stock 4.1.2 (v10e) : success but then the master file i downloaded is gone
b. Root, install freegee, initial recovery: success
c. Update to twrp 2.8 using twrp manager: success
d. Flash to Carbon: fail, canot enter recovery mode with message secure booting error,boot certification verify
So i just rollback to kitkat stock
Click to expand...
Click to collapse
So, you can't boot TWRP at all? It seems that TWRP you installed isn't lokified. Are you sure you've installed TWRP 2.8? I remember flashing it directly via flashify on my device and it worked.. Also, check TWRP thread for lokified zip, I think someone posted that.
Edit: you see now why almost everyone abandoned this device
ShadySquirrel said:
So, you can't boot TWRP at all? It seems that TWRP you installed isn't lokified. Are you sure you've installed TWRP 2.8? I remember flashing it directly via flashify on my device and it worked.. Also, check TWRP thread for lokified zip, I think someone posted that.
Edit: you see now why almost everyone abandoned this device
Click to expand...
Click to collapse
Yes, i cant boot twrp, i used twrp manager apk,i think its not lokified.
hotmatua.parulian said:
Yes, i cant boot twrp, i used twrp manager apk,i think its not lokified.
Click to expand...
Click to collapse
After installing freegee's twrp, reboot to recovery. Then, it might be OK.
After that, reboot system and use flashify, the free version will do.
You can either choose to download the file or chose from your internal / external memory.
I'm using the latest version TWRP 3.0.2.0.
If it doesn't work at first, go back to start and try again...
g0at1 said:
After installing freegee's twrp, reboot to recovery. Then, it might be OK.
After that, reboot system and use flashify, the free version will do.
You can either choose to download the file or chose from your internal / external memory.
I'm using the latest version TWRP 3.0.2.0.
If it doesn't work at first, go back to start and try again...
Click to expand...
Click to collapse
Thanks for respond, i have to download the jb stockbase again as the file used for lg flash tool is missing, looks like flashtool keep it somewhere...btw, when i use flashtool to flash the jb stock (offline mode), it.doesnt complete 100%, at 99% device was successfully boot and normal but state in flashtool screen is 99% and message to.retry is showned up.
Fyi, after flashed to jb, i cant execute fastboot flash command, the result is waiting for any device, but adb devices command return expected result. Enable debugging setting is already checked also.
Quiet interesting this device...salut to programmers of this device...
hotmatua.parulian said:
Thanks for respond, i have to download the jb stockbase again as the file used for lg flash tool is missing, looks like flashtool keep it somewhere...btw, when i use flashtool to flash the jb stock (offline mode), it.doesnt complete 100%, at 99% device was successfully boot and normal but state in flashtool screen is 99% and message to.retry is showned up.
Fyi, after flashed to jb, i cant execute fastboot flash command, the result is waiting for any device, but adb devices command return expected result. Enable debugging setting is already checked also.
Click to expand...
Click to collapse
G Pro doesn't support fastboot commands (or is really limited in that field, I'm not sure what to say/think), due to some mess LG made. Mine didn't even want to 'adb reboot bootloader', it simply rebooted device back to system, and was pain in the ass for many things because It has custom download mode, it has custom boot sequence, everything is locked down... everything is different from everything else you're used to. Thank God back then a+b OTA system didn't exist, we'd never get any AOSP support not...
Do as g0at1 said - flash TWRP from Freegee, boot it to make sure it works, reboot back to system and flash newer TWRP from Flashify or any other tool like that one. I did have E988 (just Taiwan variant), and never had that much issues, nearly every time it was a straightforward 'flash JB KDZ, root it manually, Freegee, newer TWRP, backup, flash ROM', and trust me, that one was "revived" many times.
In the end, if even that doesn't help, flash CWM from Freegee, and update it with Philz Touch for E980. I think it will support Lollipop ROMs without any issues, just don't ever boot directly into it if you're not ready to mess with dd from recovery mode - always use adb.
hotmatua.parulian said:
Quiet interesting this device...salut to programmers of this device...
Click to expand...
Click to collapse
This device was one of the hardest devices to work with... and I had Note N7000 with bad MMC which nearly bricked five times running unrooted stock firmwares Samsung provided. And Tegra-based Galaxy S2 clone with many hardware and software issues on stock... And many nameless devices with chips made by "big" vendors, like Allwinner, Rockchip etc which got some older CyanogenMod version builds with some or even complete success... And I never, never had that much issues porting stuff to any of these above, as I had with G Pro. Heck, working on a overclocking and underclocking for G Pro took me nearly two months of coding, testing, scratching everything off and starting from the beginning to just get it to some functional level and make it work as intended... and when I look at that code, I still have a feeling that it isn't completed and that some fixes are still necessary. I won't even start with GPU issues, I've spent more time than I'd like to admit on patching sessions.
ShadySquirrel said:
G Pro doesn't support fastboot commands (or is really limited in that field, I'm not sure what to say/think), due to some mess LG made. Mine didn't even want to 'adb reboot bootloader', it simply rebooted device back to system, and was pain in the ass for many things because It has custom download mode, it has custom boot sequence, everything is locked down... everything is different from everything else you're used to. Thank God back then a+b OTA system didn't exist, we'd never get any AOSP support not...
Do as g0at1 said - flash TWRP from Freegee, boot it to make sure it works, reboot back to system and flash newer TWRP from Flashify or any other tool like that one. I did have E988 (just Taiwan variant), and never had that much issues, nearly every time it was a straightforward 'flash JB KDZ, root it manually, Freegee, newer TWRP, backup, flash ROM', and trust me, that one was "revived" many times.
In the end, if even that doesn't help, flash CWM from Freegee, and update it with Philz Touch for E980. I think it will support Lollipop ROMs without any issues, just don't ever boot directly into it if you're not ready to mess with dd from recovery mode - always use adb.
This device was one of the hardest devices to work with... and I had Note N7000 with bad MMC which nearly bricked five times running unrooted stock firmwares Samsung provided. And Tegra-based Galaxy S2 clone with many hardware and software issues on stock... And many nameless devices with chips made by "big" vendors, like Allwinner, Rockchip etc which got some older CyanogenMod version builds with some or even complete success... And I never, never had that much issues porting stuff to any of these above, as I had with G Pro. Heck, working on a overclocking and underclocking for G Pro took me nearly two months of coding, testing, scratching everything off and starting from the beginning to just get it to some functional level and make it work as intended... and when I look at that code, I still have a feeling that it isn't completed and that some fixes are still necessary. I won't even start with GPU issues, I've spent more time than I'd like to admit on patching sessions.
Click to expand...
Click to collapse
:good::good::good::good: salut to you...the true programmer..never quit..yes im agree with you...i had played with nexus 1,2,3 before but never found something like this...
OK then, i will try g0at1 suggestion, hopefully it works... Like you said its only JB, root, freegee, newer twrp, backup, flash custom
Update
I couldnt wait to try again,i cant download the jb stock for a while due to internet quota limitation, so i did this:
1. Flash to stock that i still have v20c 4.4.2
2. Reboot to stock recovery then reboot to system
3. Run roottool.kitkat batch script (found from http://www.gadgetstroop.com), reboot to recovery, sideload installation of root script with result success
4. Reboot to system, run Root Checker to ensure device has been rooted
5. Install cwm recovery with GPro Kitkat Recovery 6.0.4.4 with result success
6. Reboot to cwm recovery success and do nandroid backup
7. Reboot to system, install flashify, download latest twrp official 3.0.2 and flash it using flashify: success
8. Reboot to recovery, now the recovery become twrp
9. Install package Carbon 5.1 unofficial: fail with message "cant install this package on top of incompatible data"
hotmatua.parulian said:
Update
I couldnt wait to try again,i cant download the jb stock for a while due to internet quota limitation, so i did this:
1. Flash to stock that i still have v20c 4.4.2
2. Reboot to stock recovery then reboot to system
3. Run roottool.kitkat batch script (found from http://www.gadgetstroop.com), reboot to recovery, sideload installation of root script with result success
4. Reboot to system, run Root Checker to ensure device has been rooted
5. Install cwm recovery with GPro Kitkat Recovery 6.0.4.4 with result success
6. Reboot to cwm recovery success and do nandroid backup
7. Reboot to system, install flashify, download latest twrp official 3.0.2 and flash it using flashify: success
8. Reboot to recovery, now the recovery become twrp
9. Install package Carbon 5.1 unofficial: fail with message "cant install this package on top of incompatible data"
Click to expand...
Click to collapse
You forgot to wipe system, data and caches.
ShadySquirrel said:
You forgot to wipe system, data and caches.
Click to expand...
Click to collapse
Hehehe,..thats what i thought at 1st place when it comes to fail..so i reboot to system again, reboot to recovery and try again but the result is still the same....cant install on top of icompatible data..
P.S: now downloading your slim lp 5.1 beta unofficial and i want to try it 2morrow...
hotmatua.parulian said:
Hehehe,..thats what i thought at 1st place when it comes to fail..so i reboot to system again, reboot to recovery and try again but the result is still the same....cant install on top of icompatible data..
P.S: now downloading your slim lp 5.1 beta unofficial and i want to try it 2morrow...
Click to expand...
Click to collapse
I use SlimLP for a long time because it's the only one that works smoothly for me. You might not have any trouble flashing it Through the latest TWRP.
Have fun!
g0at1 said:
I use SlimLP for a long time because it's the only one that works smoothly for me. You might not have any trouble flashing it Through the latest TWRP.
Have fun!
Click to expand...
Click to collapse
Finally carbon installed successfully after I repeat the step very carefully including your reminder bout wiping...
Thank you very much, I will consult any bugs I found..
Half Day 1 issue:
- Scrambled screen layout each time booting
- Camera unstable/crash, also with apps camera mx and open camera
- i think batt is draining faster than kitkat stock
- i feel internet via wifi is slower than kitkat stock
- phone call, other person cant hear my voice
Just flashed SlimLP..Gosh its so slim and smooth...thank you very much...there issue bout the camera and scrambled screen each time I reboot the system, which camera apps I should use?
LG Joan H933 GLOBAL CANADA 20i ROM
DO NOT USE THIS ZIP FOR CONVERTING YOUR MODIFIED TO US998 PHONE BACK TO H933!
Your phone needs to be on H933 software with TWRP kept via LGUP partition dl mode (leaving recovery partition out when flashing kdz). Have a look at the second post, @cloud1250000 wrote a guide for that with an massive amount of help from @christopherrrg.
Also, there's a Telegram Group Chat available for H933 users only, for sorting out eventually arising problems:
LG V30 H933 Canada
Hi!
This Rom is 100% Stock. Most recent TWRP should first be installed. Then you can install this Rom and have Oreo with working TWRP.
This zip is created from the original KDZ. It contains almost the complete 20i firmware, but the partition table rewriting part and recovery image (beside five to eight other images) is removed. I changed the system.img, so you do not have to reinstall TWRP (recovery-from-boot.p deleted) when ROM once booted. I also changed the partition size of system.img, so the vendorized people can install this too without having problems because of a too small system partition.
This is a continuation of westwood24's idea and work, I've updated it to the newest fw version and edited it a bit. I followed his idea and made this for users who can not take OTA's because they have Custom Recovery / Root installed.
Features
Stock build made from official KDZ
Stock Build.prop
Unrooted
system.img modified to keep TWRP
System image size shrunk for being able to flash this on a smaller system partition, mainly caused by vendorizing
Removed dm-verity
Removed rctd (LG's root checker tool daemon)
Enabled opt-encrypt, it's your choice now if you want to encrypt your phone, it's no more forced. TWRP now is capable of decryption (both AOSP and stock) since a few versions
VoLTE and VoWiFi critical OP partition separate download, flashable via TWRP (Download / MD5: add01810ddb6da99ace26645acfb5d97)
Separate OP Partition download available here
Installation
What you need
Unlocked Bootloader[/URL]
Working TWRP installed [Link to newest unofficial TWRP]
When you need Root, flash latest Magisk afterwards [Download]
The zip!
How to install
When you are still on Nougat,
you should start fresh: Reboot to recovery using button combo or reboot app (needs root; btw, Magisk offers this possibility too: Menu -> Modules -> three dot menu top right - Reboot to recovery)
Then flash this latest TWRP.img via image flashing function in TWRP, reboot to recovery again (for fully working new recovery) and do a backup, then copy this backup to your PC.
Then initiate a factory reset. Wipe your system partition too in TWRP advanced wiping menu, copy the 20i firmware zip to your SD and install it. Reboot and enjoy
From Oreo:
For clean install: Factory reset and wipe system
You can also keep your data by simply dirty flashing the zip. *Be aware that problems may occure, maybe you need to do a factory reset to start fresh*
Flash the 20i zip, then Magisk zip when you need root, then reboot to System = you're DONE
At the first time you boot to system, it can be TWRP says No OS installed. You can ignore it.
If TWRP asks if you want to install SU, hit no (in newest TWRP SU is disabled, and the option to install the TWRP app is disabled too.)
Just give a thanks if you like the zip! :good:
@christopherrrg wrote a "little guide" for the peoples, who may ever have thought about going back to h33 original (rooted or not) sw. Give him some thanks pls, he's now a few nerves lost in this procedure i can imagine :good: thanks!
Here it is:
Okay so the steps below are for AFTER using the WTF thread to convert device and unlock bootloader; these steps are for canadian model users who would prefer to go back to stock canadian kdz with working root and twrp intact.
Step 1 - Attach converted US998 (bl unlocked and twrp installed) to LGUP.
Step 2 - PARTITION DL the canadian kdz but do not include recovery.
Step 3 - Let phone boot right from kdz flash and it will automatically boot TWRP.
Step 4 - While in TWRP; 1st factory reset AND AFTER format data then reboot recovery. (If not done TWRP has mount issues with cache and or system.)
Step 5 - After TWRP is rebooted flash no-verity-opt-encrypt-6.0.zip + lg-rctd-disabler-1.0.zip and afterwards flash magisk.
Step 6 - While still in TWRP use the option to power device down.
Step 7 - Attach device to PC while holding vol+ and it will automatically start download mode.
Step 8 - PARTITION DL the canadian kdz again EXCEPT uncheck everything BUT stock recovery; let it flash and reboot.
Step 9 - Should reboot 3 - 4 times.
Step 10 - Once booted to setup; get past then activate USB debugging, also open magisk and click yes as many times as it asks you. (Magisk remains because only RECOVERY is flashed at this point)
Step 11 - Download TWRP and rename to just twrp then place it in the root directory of your internal storage.
Step 11 - Connect device to android debug bridge, and start a shell with 'adb shell' command.
Step 12 - then type 'su' and hit enter in order to gain root privilege. (Will have to click accept on super user on device)
Step 13 - then type 'dd if=/sdcard/twrp.img of=/dev/block/bootdevice/by-name/recovery'
If done correctly you should see flashing (almost like fastboot) however you will not have anything happen to your device graphically SO open magisk and click modules then click reboot to recovery and profit!
You should be on H933 kdz with TWRP and root.
However for some weird reason, cloud is correct as the battery drain is abysmal. My phone used to go from 9am 100% to about 60% by the time I get home at 5pm. Today it's gone down to 22% from 100% at 9am and it's only 2pm. @cloud1250000's brain was mostly picked for this so he deserves any and all credit; I just confirmed and wrote this up for reference.
Enjoy!
Credits to @cloud1250000
hey, it's cold out there, what about a chilled-out evening on an open fire and flashing new software on your phone...? a tester is welcome this doesn't brick your phone...
I edited this right out. For my excitement I skipped almost every single thing in the thread and I apologize however I'm willing to test and will report my findings right away!
ok, link follows via pm :good:
christopherrrg said:
I edited this right out. For my excitement I skipped almost every single thing in the thread and I apologize however I'm willing to test and will report my findings right away!
Click to expand...
Click to collapse
Someone else PM'ed me so we have two testers.
seadersn said:
LG Joan H933 GLOBAL CANADA 20G ROM
DO NOT USE THIS ZIP FOR MODEL CONVERSIONS!Hi!
This Rom is 100% Stock. Most recent TWRP should first be installed. Then you can install this Rom and have Oreo with working TWRP.
This needs testing first, please hit me a PM for getting the link.
This zip is created from the original KDZ (H93320g_00_OPEN_CA_OP_0910.kdz). It contains almost the complete 20G firmware, but the partition table rewriting part and recovery image (beside five to eight other images) is removed. I changed the system.img, so you do not have to reinstall TWRP (recovery-from-boot.p deleted) when ROM once booted. I also changed the partition size of system.img, so the vendorized people can install this too without having problems because of a too small system partition.
This is a continuation of westwood24's idea and work, I've updated it to the newest fw version and edited it a bit. I followed his idea and made this for users who can not take OTA's because they have Custom Recovery / Root installed.
Features
Stock build made from official KDZ
Stock Build.prop
Unrooted
system.img modified to keep TWRP
System image size shrunk for being able to flash this on a smaller system partition, mainly caused by vendorizing
Removed dm-verity
Removed rctd (LG's root checker tool daemon)
Enabled opt-encrypt, it's your choice now if you want to encrypt your phone, it's no more forced. TWRP now is capable of decryption (both AOSP and stock) since a few versions
Installation
What you need
Unlocked Bootloader [How to do]
Working TWRP installed (should be installed already, otherwise you wouldn't need this zip )[Link to newest unofficial TWRP]
When you need Root, Latest Magisk [Download]
The zip!
How to install
When you are still on Nougat,
you should start fresh: Reboot to recovery using button combo or reboot app (needs root; btw, Magisk offers this possibility too: Menu -> Modules -> three dot menu top right - Reboot to recovery)
Then flash this latest TWRP.img via image flashing function in TWRP, reboot to recovery again (for fully working new recovery) and do a backup, then copy this backup to your PC.
Then initiate a factory reset. Wipe your system partition too in TWRP advanced wiping menu, copy the 20G firmware zip to your SD and install it. Reboot and enjoy
From Oreo:
For clean install: Factory reset and wipe system
You can also keep your data by simply dirty flashing the zip. *Be aware that problems may occure, maybe you need to do a factory reset to start fresh*
Flash the 20G zip, then Magisk zip when you need root, then reboot to System = you're DONE
At the first time you boot to system, it can be TWRP says No OS installed. You can ignore it.
If TWRP asks if you want to install SU, hit no (in newest TWRP SU is disabled, and the option to install the TWRP app is disabled too.)
Rom Version
Android Version: 8.0 Oreo
Android security patch level: 2018-09-1
Just give a thanks if you like the zip! :good:
You want to help me with a [donation?] Not asking for it, I have fun doing this for you, but feel free...
Click to expand...
Click to collapse
Please can you explained me something, you wrote DO NOT USE THIS ZIP FOR MODEL CONVERSIONS!, but we must convert the H933 to US988 in order to install TWRP and root. So now I can install it, go back from US988 to H933 and keep TWRP and root ?
Thanks
so actually; as the above user is mentioning I attempted a partition DL flash of the kdz minus recovery and it constantly boots to recovery after flash (which i'm sure is totally normal as stock will not boot with custom recovery without no verity etc) buuuuut my stupid behind didn't flash those and assumed it would not work so decided to panic and flash the us998 kdz back in order to restore my backup and I think I screwed up my download mode as it now shows download mode for 2 seconds then reboots right into recovery; I believe I may have corrupted my laf partition and am now currently working on getting back to a functioning device; luckily the bootloader is still unlocked and I can still flash things as system and data both mount no problem.
my apologies for the lengthly message but or anyone else who is planning to test please remember if you're flashing back from US998 to H933 not to do as i've done and remember no verity etc so it can at least boot so you can THEN flash this zip here.
after all of that i've still got nothing to report as flashing it seems to look great but because I kdz back to us998 i'm afraid to use this zip until I get a booting phone again; also please dont take this as me flaming or anything. i'm sure i'll fix my device with fastboot soon and shall resume testing.
christopherrrg said:
so actually; as the above user is mentioning I attempted a partition DL flash of the kdz minus recovery and it constantly boots to recovery after flash (which i'm sure is totally normal as stock will not boot with custom recovery without no verity etc) buuuuut my stupid behind didn't flash those and assumed it would not work so decided to panic and flash the us998 kdz back in order to restore my backup and I think I screwed up my download mode as it now shows download mode for 2 seconds then reboots right into recovery; I believe I may have corrupted my laf partition and am now currently working on getting back to a functioning device; luckily the bootloader is still unlocked and I can still flash things as system and data both mount no problem.
my apologies for the lengthly message but or anyone else who is planning to test please remember if you're flashing back from US998 to H933 not to do as i've done and remember no verity etc so it can at least boot so you can THEN flash this zip here.
after all of that i've still got nothing to report as flashing it seems to look great but because I kdz back to us998 i'm afraid to use this zip until I get a booting phone again; also please dont take this as me flaming or anything. i'm sure i'll fix my device with fastboot soon and shall resume testing.
Click to expand...
Click to collapse
Thanks for the update, good luck recovering the phone. Maybe ou can try LG software from recovery ....
[email protected] said:
Please can you explained me something, you wrote DO NOT USE THIS ZIP FOR MODEL CONVERSIONS!, but we must convert the H933 to US988 in order to install TWRP and root. So now I can install it, go back from US988 to H933 and keep TWRP and root ?
Thanks
Click to expand...
Click to collapse
Yes you must be on a global Canadian kdz that is BEFORE this version.
when you convert back make sure you use partition DL and uncheck recovery; then when you flash canadian kdz and boot up flash dm no verity and the other zip to make stock kdz boot with twrp still intact; then once system boots at least once you reboot into twrp with the master reset combo and then use the zip provided by these gentlemen. ( at least now that my phone is down for the moment this is my theory ) heh:silly:
christopherrrg said:
Yes you must be on a global Canadian kdz that is BEFORE this version.
when you convert back make sure you use partition DL and uncheck recovery; then when you flash canadian kdz and boot up flash dm no verity and the other zip to make stock kdz boot with twrp still intact; then once system boots at least once you reboot into twrp with the master reset combo and then use the zip provided by these gentlemen. ( at least now that my phone is down for the moment this is my theory ) heh:silly:
Click to expand...
Click to collapse
Thanks again, but flashing back the H933 will relock the bootloader ?
[email protected] said:
Thanks again, but flashing back the H933 will relock the bootloader ?
Click to expand...
Click to collapse
nope! it remains unlocked.
I did manage to recover my device and my download mode (thanks to Matts amazing WTF guide.)
so give me about an hour or so and i'll retry; just going to take a quick shower.
Edit - had quite a few issues. Can't seem to get TWRP to actually work after doing partition DL all except recovery. (TWRP acts as if there is no system and when I try to boot it just reboots back into recovery.) Almost as if my Canadian device WANTS to stay US998 lol I got some issues to sort but will report back once I figure out how to make twrp flash AFTER full Canadian kdz, not sure if it's possible to flash recovery without fastboot is it?
recovery *would* be flashable with a rooted system and the dd (diskdump) command from within booted android.
so h933 is a device which needs conversion. this zip can then only be used when:
- you converted your h933 to us998 to get the fastboot commands and install twrp etc.
- your phone is then *converted back* to h933 with original h933 kdz, but with keeping twrp via partition dl mode of lgup.
- this way you lose fastboot commands (which normaly shouldn't be needed anymore), but can keep twrp and flash roms.
this method should work. because bootloader remains unlocked and is writable by twrp, even if you are on full h933 firmware, except recovery partition.
looks like we really need to work this out, carefully not that one of you nice testers have a non working phone because of this zip used in the wrong place (with us998 kdz installed) and moment (before full h933 kdz is installed with keeping twrp).
we need to try too, if this zip is installable on a converted to us998 phone and then at least boots as usual, or if sth. gets mixed up then (because it then has mixed partitions, ⅔ of the phones partitions are h933 fw then, and ⅓ is us998 partitions).
christopherrrg said:
nope! it remains unlocked.
I did manage to recover my device and my download mode (thanks to Matts amazing WTF guide.)
so give me about an hour or so and i'll retry; just going to take a quick shower.
Edit - had quite a few issues. Can't seem to get TWRP to actually work after doing partition DL all except recovery. (TWRP acts as if there is no system and when I try to boot it just reboots back into recovery.) Almost as if my Canadian device WANTS to stay US998 lol I got some issues to sort but will report back once I figure out how to make twrp flash AFTER full Canadian kdz, not sure if it's possible to flash recovery without fastboot is it?
Click to expand...
Click to collapse
this may be because of a differing partition table. *may*, i don't know this. i would like to have such a device for intensive testing... or visit canada and a person who's willing to drink much beer while testing this out :good:
seadersn said:
recovery *would* be flashable with a rooted system and the dd (diskdump) command from within booted android.
so h933 is a device which needs conversion. this zip can then only be used when:
- you converted your h933 to us998 to get the fastboot commands and install twrp etc.
- your phone is then *converted back* to h933 with original h933 kdz, but with keeping twrp via partition dl mode of lgup.
- this way you lose fastboot commands (which normaly shouldn't be needed anymore), but can keep twrp and flash roms.
this method should work. because bootloader remains unlocked and is writable by twrp, even if you are on full h933 firmware, except recovery partition.
looks like we really need to work this out, carefully not that one of you nice testers have a non working phone because of this zip used in the wrong place (with us998 kdz installed) and moment (before full h933 kdz is installed with keeping twrp).
we need to try too, if this zip is installable on a converted to us998 phone and then at least boots as usual, or if sth. gets mixed up then (because it then has mixed partitions, ⅔ of the phones partitions are h933 fw then, and ⅓ is us998 partitions).
Click to expand...
Click to collapse
I got my phone fully working again and my backup restored. (US998)
So I think what I'm going to attempt today is flashing FULL canadian kdz (fresh stock including recovery) and let it boot then I'm gonna try to dd the recovery to get TWRP access.
And go from there.
I got your PM and will need to pull out my nexus 4 for telegram but will set it up after work today and join you guys.
---------- Post added at 01:17 PM ---------- Previous post was at 01:15 PM ----------
seadersn said:
this may be because of a differing partition table. *may*, i don't know this. i would like to have such a device for intensive testing... or visit canada and a person who's willing to drink much beer while testing this out :good:
Click to expand...
Click to collapse
Heheh I'm willing to drink much beer wish I had my 2nd device because I'd have mailed you guys this H933 to crack.
We will get it soon, a lot more H933 people coming out of hiding really helps. ?
V
[email protected] said:
Thanks for the update, good luck recovering the phone. Maybe ou can try LG software from recovery ....
Click to expand...
Click to collapse
What actually got me out of the loop was Westwoods stock US998 TWRP ROM zip. I believe it restored my LAF partition and download mode worked no problem in order to use LGUP.
However these issues were of my own accounts; essentially from step 1 this is what the full procedure I assume will be like for us H933 users.
Step 1. Convert H933 to US998 and unlock bootloader using WTF guide.
Step 2. Using LGUP, 'REFURBISH' US998 device back into H933 kdz (accept partition layout changes) [attempted to use partition DL with all partitions minus recovery; however stock system won't boot with custom recovery unless rooted and no decrypt and dm verity flashed before system boots {failed to try this due to panic and forgetfulness so this may work but I'd like to attempt using dd from fresh stock also.}]
Step 3. Attempt dd recovery flash on bootloader unlocked H933 due to missing fastboot etc.
Step 4. Hope for profit? ?
I also apologize to you all for the lengthly posts as well but from all my years here on this website it's reading through the users problems where solutions are generally found so even though I followed wrong directions at first it's up to show everyone how I messed up and can be avoided.
christopherrrg said:
V
What actually got me out of the loop was Westwoods stock US998 TWRP ROM zip. I believe it restored my LAF partition and download mode worked no problem in order to use LGUP.
However these issues were of my own accounts; essentially from step 1 this is what the full procedure I assume will be like for us H933 users.
Step 1. Convert H933 to US998 and unlock bootloader using WTF guide.
Step 2. Using LGUP, 'REFURBISH' US998 device back into H933 kdz (accept partition layout changes) [attempted to use partition DL with all partitions minus recovery; however stock system won't boot with custom recovery unless rooted and no decrypt and dm verity flashed before system boots {failed to try this due to panic and forgetfulness so this may work but I'd like to attempt using dd from fresh stock also.}]
Step 3. Attempt dd recovery flash on bootloader unlocked H933 due to missing fastboot etc.
Step 4. Hope for profit? ?
I also apologize to you all for the lengthly posts as well but from all my years here on this website it's reading through the users problems where solutions are generally found so even though I followed wrong directions at first it's up to show everyone how I messed up and can be avoided.
Click to expand...
Click to collapse
absolutely ok, the more info the better so when one wants to stay stock h933, steps are
step 1: jep
step 2: jep, partition dl with *recovery excluded* to h933 kdz (after unlocking via us998). twrp should be present and bootable after that.
step 3: boot recovery, format data, reboot to recovery, flash opt-encrypt, no verity and make sure, /system/recovery-from-boot.py is deleted or renamed. and eventually flash magisk and then boot to rom, jep.
could imagine that this works, but, i know too little about frankensteined phones. there may be hassles and hiccups. first boot up and test, then trying a restore, in hope it will be succesful :good:
seadersn said:
absolutely ok, the more info the better so when one wants to stay stock h933, steps are
step 1: jep
step 2: jep, partition dl with *recovery excluded* to h933 kdz (after unlocking via us998). twrp should be present and bootable after that.
step 3: boot recovery, format data, reboot to recovery, flash opt-encrypt, no verity and make sure, /system/recovery-from-boot.py is deleted or renamed. and eventually flash magisk and then boot to rom, jep.
could imagine that this works, but, i know too little about frankensteined phones. there may be hassles and hiccups. first boot up and test, then trying a restore, in hope it will be succesful :good:
Click to expand...
Click to collapse
WOW; there it is.
Format Data. Another neglected procedure on my end grrr.
Saves the whole issue of using DD period.
And would explain why TWRP also half worked.
Gonna give it another crack as soon as I'm home. I'll also have telegram set up as to not spam this thread much further.
@cloud1250000 has posted a way to have a rooted canadian ROM https://forum.xda-developers.com/lg...odem-to-converted-us998-t3824769/post77613655 but from his instructions. He said he installed magisk to the canadian system to ensure root in order to use adb shell to install twrp. But I can't for the life of me figure out how he kept magisk but nothing else... so maybe he can help us.
No matter what I do after conversion of US998; H933 will not boot with TWRP on stock unless it's 100% stock. (Even after attempting dm verity, no encrypt and root) by trying your advice and tinkering with a bit of my own. LGUP also still reports the H933 device as a US99820d
Basically if he can help explain how he got magisk on there or I can figure it out then unfortunately at the moment we can't really flash this as we need a working recovery and sadly he's the only Canadian user reported so far having working twrp, root and lte working no problem.
Thing's I've tried so far:
- converted US998 to H933 with PARTITION DL and unchecked RECOVERY; recovery sticks however after formatting data then rebooting into recovery I then remove /system/recovery-bak (may have spelt that wrong but you get what I mean) I try flashing no encrypt and dm verity then flash root everything works (no red error messages of any kind) Boots back to recovery.
- converted US998 to H933 with PARTITION DL and made sure ALL checkboxes were checked. Phone booted but obviously no working recovery and no (at the current moment) known method of rooting without fastboot commands.
So sadly until we figure that I think we're stuck. ?
Will PM you my telegram info in the next few minutes.
So...
I have no clue why but when going back to the h933 from the us998... There's an extra partition called OP where, I assume, information about the carriers/modem can be found.
You should be aware that in canada now... there's no carrier locked phone anymore... so my guess is... this OP partition is configured on the first boot by looking at the sim that was inserted in the phone.
The problem.
TWRP doesn't have the command to setup the OP partition correctly and the phone do send this command to the recovery on first boot..
(found by looking at recovery log)
So what I did was...
1. Keep TWRP and use LGUP to go back to H933.
2. Boot into twrp and flash all needed zip (root + the other 2)
3. Flash the stock recovery and allow the phone to setup the OP partition correctly upon reboot (there will be a weird circle with "erasing" text on the screen)
4. Boot in the phone and launch the magisk app. Say yes a bunch of time.
5. Use a rooted adb shell to flash back twrp.
6. Profit/Enjoy
In my original guide, I did flash a bunch of partition that I got from a working h933.. so maybe it's missing some steps in order to work.
https://forum.xda-developers.com/lg...rted-us998-t3824769/post77613655#post77613655
Good luck.
cloud1250000 said:
So...
I have no clue why but when going back to the h933 from the us998... There's an extra partition called OP where, I assume, information about the carriers/modem can be found.
You should be aware that in canada now... there's no carrier locked phone anymore... so my guess is... this OP partition is configured on the first boot by looking at the sim that was inserted in the phone.
The problem.
TWRP doesn't have the command to setup the OP partition correctly and the phone do send this command to the recovery on first boot..
(found by looking at recovery log)
So what I did was...
1. Keep TWRP and use LGUP to go back to H933.
2. Boot into twrp and flash all needed zip (root + the other 2)
3. Flash the stock recovery and allow the phone to setup the OP partition correctly upon reboot (there will be a weird circle with "erasing" text on the screen)
4. Boot in the phone and launch the magisk app. Say yes a bunch of time.
5. Use a rooted adb shell to flash back magisk.
6. Profit/Enjoy
In my original guide, I did flash a bunch of partition that I got from a working h933.. so maybe it's missing some steps in order to work.
https://forum.xda-developers.com/lg...rted-us998-t3824769/post77613655#post77613655
Good luck.
Click to expand...
Click to collapse
Yeah I got lost on your step about dd recovery I was like uh wait how did he retain root?!
Thanks so much for your input! Very much appreciated.:highfive:
Also if we figure this out; that's an enormous contribution towards us getting custom ROMs working; thank you again!