can't flash a CWM recovery on my wife's E980 using Freegee....Mine is the white one and I had no loki issues with it...everytime you flsays:
"checking if loki-ifying is needed/dev/block/platform/msm_sdcc. /by-name/boot needs lokifying. [-] Failed to find function to patch.
Error loki-ifying the boot image. "
yes I did use Freegee already and install CWM. When I booted it gave me this...I can't install any ROMS. yet my other G Pro (white) is fine and hasn't given me any issues. RIght now I'm stuck with it booting into clockwork by itself. And I would like to use TWRP but the version that comes with Freegee doesn't work right on the damn screen. If it's not bootlooping into Clockwork then it gets frozen at the LG screen with something about security crap. and the funny part is...I used Freegee both times.
EDIT: used LGFlashTool to bring it back..but she wants a custom ROM and every recovery I flash to it either
1. used this recovery. tried flashing using a CWM recovery that I used from Freegee http://forum.xda-developers.com/showthread.php?t=2552611
freezes at the LG screen with a SECURITY ERROR on the left corner of the screen (flashtools will fix)
2. When I do successfully flash a recovery using Freegee and I get it to boot into CWM it won't come back out of CWM it will boot automatically into it (LGflashtools will fix)
3. the freegee TWRP in won't work right with the touch screen.
Yes I saw that there are 2 topics similar to this, but they are G2's. Mine is an AT&T E980 that i'm having issues with.
I had exactly this same problem. I'm also on AT&T E980 and could not find a fix anywhere for this phone. I flashed back to stock so many times that I was ready to just get rid of it. What I finally noticed was that, if I flashed back to stock and took the update to E98010P, I could flash TWRP through FreeGee and the touch would work. I also used VooDoo OTA to preserve root through the update. I don't know if it was necessary, but it didn't cause me any problems and everything worked.
I have no idea why CWM stopped working and I could not use Phil's recovery either, but the whole experience has been maddening and I have never had so many problems with a phone before. Hope this helps.
i have the same annoying problem!
can someone help?
after the rom flash was done i've got the error so i immediately restored my backup
EdgarSnyder said:
I had exactly this same problem. I'm also on AT&T E980 and could not find a fix anywhere for this phone. I flashed back to stock so many times that I was ready to just get rid of it. What I finally noticed was that, if I flashed back to stock and took the update to E98010P, I could flash TWRP through FreeGee and the touch would work. I also used VooDoo OTA to preserve root through the update. I don't know if it was necessary, but it didn't cause me any problems and everything worked.
I have no idea why CWM stopped working and I could not use Phil's recovery either, but the whole experience has been maddening and I have never had so many problems with a phone before. Hope this helps.
Click to expand...
Click to collapse
so...Root using the old firmware...voodoo OTA then update?...and then restore root and then Freegee should work fine with TWRP?
ive installed the twrp recovery and the flash completed , but the idiot checked the MD5 than skipped it than finished and on the bottom line just did NOTHING!
what the hell!
what is going on with this phone! so frustrating ...
Yeah, I went back to stock, rooted and installed FreeGee and Voodoo, then took the update and flashed TWRP thru FreeGee.
Sent from my LG-E980 using xda app-developers app
and?
no you can install whatever rom you want?
amirnew said:
and?
no you can install whatever rom you want?
Click to expand...
Click to collapse
No, i'm pretty sure on the firmware i'm running (not sure what you're running) can only flash touchwiz based ROMS. No Cyanogenmod, AOSP or anything not based on samsung's stock UI
stanleyopar2000 said:
No, i'm pretty sure on the firmware i'm running (not sure what you're running) can only flash touchwiz based ROMS. No Cyanogenmod, AOSP or anything not based on samsung's stock UI
Click to expand...
Click to collapse
i've tryied flashing custom 4.1.2 rom... and my phone is e980 from att
amirnew said:
i've tryied flashing custom 4.1.2 rom... and my phone is e980 from att
Click to expand...
Click to collapse
wrong thread. it was meant for this one
http://forum.xda-developers.com/showthread.php?p=51529974
stanleyopar2000 said:
can't flash a CWM recovery on my wife's E980 using Freegee....Mine is the white one and I had no loki issues with it...everytime you flsays:
"checking if loki-ifying is needed/dev/block/platform/msm_sdcc. /by-name/boot needs lokifying. [-] Failed to find function to patch.
Error loki-ifying the boot image. "
yes I did use Freegee already and install CWM. When I booted it gave me this...I can't install any ROMS. yet my other G Pro (white) is fine and hasn't given me any issues. RIght now I'm stuck with it booting into clockwork by itself. And I would like to use TWRP but the version that comes with Freegee doesn't work right on the damn screen. If it's not bootlooping into Clockwork then it gets frozen at the LG screen with something about security crap. and the funny part is...I used Freegee both times.
EDIT: used LGFlashTool to bring it back..but she wants a custom ROM and every recovery I flash to it either
1. used this recovery. tried flashing using a CWM recovery that I used from Freegee http://forum.xda-developers.com/showthread.php?t=2552611
freezes at the LG screen with a SECURITY ERROR on the left corner of the screen (flashtools will fix)
2. When I do successfully flash a recovery using Freegee and I get it to boot into CWM it won't come back out of CWM it will boot automatically into it (LGflashtools will fix)
3. the freegee TWRP in won't work right with the touch screen.
Yes I saw that there are 2 topics similar to this, but they are G2's. Mine is an AT&T E980 that i'm having issues with.
Click to expand...
Click to collapse
Ok I have used CWM from FreeGee and used the Carbon (http://forum.xda-developers.com/showthread.php?t=2439911) ROM and it does not need lokifying for my AT&T E980. It loads fine. I'm looking for a way to fix the lokifying thing though as I can't flash too many ROMs, a lot need lokifying.
I've personally had no issues on my E980 using TWRP flashed by FreeGee, but you can always try the "hacked" TWRP provided by @madmack
http://forum.xda-developers.com/showpost.php?p=45497511&postcount=235
chp said:
I've personally had no issues on my E980 using TWRP flashed by FreeGee, but you can always try the "hacked" TWRP provided by @madmack
http://forum.xda-developers.com/showpost.php?p=45497511&postcount=235
Click to expand...
Click to collapse
+1
Always used Madmack's hacked TWRP for anything that requires loki and it works flawlessly.
Sent from my 4.4 Sphinx REMOD LG-E980
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
Hello,
So, i was trying to install root on my LG G4, version H815 (no letters/numbers after)
I did successfully unlocked my bootloader (info message on left top corner when booting) - official LG unlock
Booted into TWRP - twrp-3.0.2-0-h815 from ADB
- Installed UPDATE-SuperSU-v2.46.zip (which is located on internal storage) from TWRP - https://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip
- Clear cache (dalvik)
- Reboot
Phone started booting, and got stuck on the LG logo
I did try to get it recognized in download mode and I did try to enter recovery mode (but I didn't install TWRP, only boot into it.. so I was left with the "default" one)
My phone doesn't enter recovery mode (I get the dead android bot with red exclamation mark)
At this step, somehow ADB recognized my phone, and I tried installing SuperSU again, and once again same thing happened.. I got stuck on LG logo
After this until now, I'm not able to:
- see my phone in ADB
- download mode with LGFlashTool2014.exe to flash .kdz "Europe OPEN H81510D.kdz" - getting error on LG Mobile Support Tool - "Upgrade stopped due to an error'"
I was following this: http://forum.xda-developers.com/g4/general/guide-lg-g4-stock-firmware-to-stock-kdz-t3107848
Currently I'm trying all the steps from here http://forum.xda-developers.com/g4/help/lg-g4-stuck-bootloop-t3268734
I just wanted to ask, is there a better way? Is there a working way?
Thanks, any help appreciated!
What firmware were you on? LP or MM. If the firmware was MM then you should have used SU 2.52 otherwise you end up as you are now.
Sent from my LG-H815 using Tapatalk
Stransky said:
What firmware were you on? LP or MM. If the firmware was MM then you should have used SU 2.52 otherwise you end up as you are now.
Sent from my LG-H815 using Tapatalk
Click to expand...
Click to collapse
I was on MM didn't saw that part..
Thanks for pointing it out!
BrainCrasher said:
I was on MM didn't saw that part..
Thanks for pointing it out!
Click to expand...
Click to collapse
You should also have flashed any custom kernel first that will allow you to not boot but install TWRP and then easily root. To flash firmware for G4 we use LG UP, nor Flashtool2014 and Mobile Support Tool ( G4 is not even compatible with it! It says on their website that you have to download LG Bridge)
I fixed it by using LG Bridge
- Update error recovery option
It installed android 6.0 on it
Then I used BETA-SuperSU-v2.67-20160121175247.zip for root, and everything seems to be fine
Thanks for your help!
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?
I did the following
1. Downgraded to V30b-EUR-XXX with LGUP. Went smooth.
2. Rooted phone sucessfully with kingroot.
3. Got a shell with "adb shell"
4. "su"
5. Filled the recovery-partition with zeros from /dev/zero with dd
6. Installed twrp3.2.3-0 with dd on recovery-partition
When I boot into Marshmallow, all is fine. When I boot into recovery, I'm informed about a necessary factory reset. I say "Yes" both times, then the LG Logo and some tiny text is displayed and afterwards the screen goes dark. The LED is blinking blue and red; the only way out of this is to remove the battery.
If I do a factory reset from within marshmallow, the result is the same.
What can I do now? Should I flash a stock recovery with dd? But where to get it? Or should I flash an older version of twrp?
Hello,
Last time when I downgraded, I also rooted with KingRoot, but I installed the "Flashify" full version, ( on the ROM of course ) and I flashed the twrp with the flashify as "recovery". This is working.
NetDog75 said:
Hello,
Last time when I downgraded, I also rooted with KingRoot, but I installed the "Flashify" full version, ( on the ROM of course ) and I flashed the twrp with the flashify as "recovery". This is working.
Click to expand...
Click to collapse
Excuse me, but I'm not able to decipher that. What is flashify? What means "on the ROM of course"? Can you give more information please.
- flashify is an application.
- on the ROM = when the phone booted and the operation system is working, you can use your phone... example for phone calls. As you wrote: "boot into Marshmallow"
So, downgrade again, and boot into Marshmallow, use the kingroot, than install the flashify application. You can flash the twrp with the mentioned Flashify application, than reboot to recovery.
NetDog75 said:
- flashify is an application.
- on the ROM = when the phone booted and the operation system is working, you can use your phone... example for phone calls. As you wrote: "boot into Marshmallow"
So, downgrade again, and boot into Marshmallow, use the kingroot, than install the flashify application. You can flash the twrp with the mentioned Flashify application, than reboot to recovery.
Click to expand...
Click to collapse
Don't had to downgrade, because I was in V30b. Got root, installed flashify and flashed twrp - the first time 3.2.3, then 2.8.0. Same result as before.
From what version of android did you install what version of twrp?
Hi,
I use the twrp3.2.3 and no problem.
I'm not expert, I just can recommend some steps...
Maybe good idea to flash again the stock ROM. You can find here on the forum many step by step guide for this. ( tools and steps )
It seems your phone recovery partition is not OK....
I have no more idea...
@theuving, why did you decide to zero out the recovery partition? I don't know but that may be part of the problem. Since you were connected via adb was it not possible to use fastboot? Flashing the recovery via that should(?) have also worked.
If the recovery partition is messed up you might have to start over. Not sure though as I haven't experienced that problem.
ZTE Axon 7 A2017U, /e/ v0.1 ROM, microG (NoGapps), Multiboot, XDA Legacy
marcdw said:
@theuving, why did you decide to zero out the recovery partition? I don't know but that may be part of the problem. S
Click to expand...
Click to collapse
It's the same partition where I flashed twrp, so the zeros are already overwritten with something else ...
Seriously: Zeroing the partition before writing to it was mentioned in a thread about the installation of a "bumped" recovery.
NetDog75 said:
Hi,
I use the twrp3.2.3 and no problem.
Click to expand...
Click to collapse
OK, that is the version I used also. What android version was installed when you flashed the recovery? Mine is stock V30b.
Hi,
I'm not sure, because I changed to 8.1 (oreo).
Maybe V30N.....
I am having the same problem. There is no "unlock bootloader" in the developer options, and adb reboot bootloader just starts into android again. I might have to reflash the stock firmware, but nowhere in the install instructions for twrp does it say that you first have to unlock the bootloader, and nowhere does it even mention that there might not be such an option. This is genuinely strange.