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.
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 all, so I have Verizon's Pixel XL. I have unlocked it successfully and had rooted. I asked on the forums about upgrading the OTA update and was told it was fine. After doing so, I noticed my SuperSU was gone (although I might have lost it earlier and not noticed). So after trying to get it back and keeping getting stuck, I bit the bullet and ADB sideloaded the factory image from google (NDE63X) and got it able to boot up. Yay.
So then I ran the 'adb reboot bootloader' command, then verified my device was connected with 'fastboot devices' and finally I ran 'fastboot boot boot-to-root.img'. And here I am, stuck on the splash screen again.
So I looked around and saw some mentions of people that had used older versions of Chainfire's SuperSU. I tried the newer one (2.78 SR3) and the same thing happened. I do see that there is a SR5, but I also see Chainfire's comment "Do not use the SuperSU ZIP on work-in-progress TWRP releases for Pixel, it will not work - use the model specific links above instead.
I can get it to run just fine without using chainfire's supersu...but then I don't have the supersu app or any real gains from having rooted.
So, I feel like I must be doing something wrong. Any suggestions?
@smokeydriver,
You probably should update your Android SDK package. This problem can also be caused by an obsolete fastboot.
cam30era said:
@smokeydriver,
You probably should update your Android SDK package. This problem can also be caused by an obsolete fastboot.
Click to expand...
Click to collapse
I can give it a shot, but I only installed minimal adb yesterday on my new laptop. Thanks!
smokeydriver said:
I can give it a shot, but I only installed minimal adb yesterday on my new laptop. Thanks!
Click to expand...
Click to collapse
I understand. Here's the thing: I don't know if minimal has up to date ADB and fastboot for Android 7.1.1.
cam30era said:
I understand. Here's the thing: I don't know if minimal has up to date ADB and fastboot for Android 7.1.1.
Click to expand...
Click to collapse
The OTA update I took only got me to a new version of 7.1, not 7.1.1 (from NDE63P to NDE63X). It still shows an available update to 7.1.1 which I have *not* done.
Try using the Unified Toolkit. It saved me from having a bootloop disaster when I tried upgrading from 7.1.1 due to poor instruction availability around the web. It should fix whatever problem you are having, even if that means flashing the factory image first again.
Nitemare3219 said:
Try using the Unified Toolkit. It saved me from having a bootloop disaster when I tried upgrading from 7.1.1 due to poor instruction availability around the web. It should fix whatever problem you are having, even if that means flashing the factory image first again.
Click to expand...
Click to collapse
I've tried, but keep getting an error 21 code that it can't install...I tried this with SR5 and SR2.
How I Rooted
Personally, I'd flash to latest OTA via Unified Android Toolkit before starting this process.
Then use Minimal ADB to flashboot boot twrp.img (The Alpha2 Version)
AT this point you should already have 2 zips on your phone, TWRP-RC1 and SuperSU v5.
Flash TWRP, then SuperSU.
Reboot into OS, confirm root, give it 5 minutes.
Reboot back to Recovery and flash Kernel if desired.
Do not flash root with RC-1 (thats why we flashed root while using Alpha2 adb twrp.img), do not restore backups made with Alpha2 using RC1 or vic versa. AKA Backup and Restore with same version of TWRP.
FreeSoftwareServers said:
Personally, I'd flash to latest OTA via Unified Android Toolkit before starting this process.
Then use Minimal ADB to flashboot boot twrp.img (The Alpha2 Version)
AT this point you should already have 2 zips on your phone, TWRP-RC1 and SuperSU v5.
Flash TWRP, then SuperSU.
Reboot into OS, confirm root, give it 5 minutes.
Reboot back to Recovery and flash Kernel if desired.
Do not flash root with RC-1 (thats why we flashed root while using Alpha2 adb boot.img), do not restore backups made with Alpha2 using RC1 or vic versa. AKA Backup and Restore with same version of TWRP.
Click to expand...
Click to collapse
Ok, I must be doing something wrong on a very basic level. It gave me error 21 (signature verification error) when trying to use the unified android tookit to install 7.1. Anyways, I'll just move on and skip that step and see what happens.
Flashing SuperSU SR5 works just fine with TWRP RC1. All you have to do is delete the file you're told to before flashing.
Dees_Troy said:
How to install SuperSU SR5 on TWRP RC1: In TWRP tap on Advanced -> File Manager and scroll to and select the fstab.marlin or fstab.sailfish file and then delete it.
Click to expand...
Click to collapse
FreeSoftwareServers said:
Personally, I'd flash to latest OTA via Unified Android Toolkit before starting this process.
Then use Minimal ADB to flashboot boot twrp.img (The Alpha2 Version)
AT this point you should already have 2 zips on your phone, TWRP-RC1 and SuperSU v5.
Flash TWRP, then SuperSU.
Reboot into OS, confirm root, give it 5 minutes.
Reboot back to Recovery and flash Kernel if desired.
Do not flash root with RC-1 (thats why we flashed root while using Alpha2 adb twrp.img), do not restore backups made with Alpha2 using RC1 or vic versa. AKA Backup and Restore with same version of TWRP.
Click to expand...
Click to collapse
I transferred those 2 files to my download folder on my phone, ran the twrp.img script, and then when I go in...the file names are not normal. Everything is random letters and numbers. Again, I feel like I'm making some stupid basic mistake that I don't understand (and I've rooted plenty of phones).
spotmark said:
Flashing SuperSU SR5 works just fine with TWRP RC1. All you have to do is delete the file you're told to before flashing.
Click to expand...
Click to collapse
So I go in TWRP to advanced, file manager, and I don't see the names of those files. Are they buried in a folder?
smokeydriver said:
So I go in TWRP to advanced, file manager, and I don't see the names of those files. Are they buried in a folder?
Click to expand...
Click to collapse
You have TWRP RC1 installed?
spotmark said:
You have TWRP RC1 installed?
Click to expand...
Click to collapse
Nope...stuck before that. I'm using Minimal ADB to flashboot boot twrp.img (The Alpha2 Version)...but then I go to the sd card and it's all random letters and numbers...so I can't install twrp rc1.
smokeydriver said:
Nope...stuck before that. I'm using Minimal ADB to flashboot boot twrp.img (The Alpha2 Version)...but then I go to the sd card and it's all random letters and numbers...so I can't install twrp rc1.
Click to expand...
Click to collapse
Ah, I see. I misunderstood. I thought you were just under the impression that you couldn't flash SU with RC1. My apologies.
Ok, so can someone tell me why I am getting stuck with 1 thing. I go to my stock recovery and into ADB sideload. When I tell it the file, it keeps failing to verify whole-file signature. What is wrong with this one step?
Or alternatively...when I'm in TWRP Alpha 2- why are all the files within the sdcard random letters and numbers?
smokeydriver said:
Nope...stuck before that. I'm using Minimal ADB to flashboot boot twrp.img (The Alpha2 Version)...but then I go to the sd card and it's all random letters and numbers...so I can't install twrp rc1.
Click to expand...
Click to collapse
Twrp is not decrypting you're data. Try rebooting twrp from fastboot a second time.
toknitup420 said:
Twrp is not decrypting you're data. Try rebooting twrp from fastboot a second time.
Click to expand...
Click to collapse
Son-of-a B#[email protected]#$. It asks me to 'decrypt data' by entering a password. I had hit cancel. What's the password??
smokeydriver said:
Son-of-a B#[email protected]#$. It asks me to 'decrypt data' by entering a password. I had hit cancel. What's the password??
Click to expand...
Click to collapse
Never mind...it's my 4 digit password that's used when my finger unlock doesn't work. Ugh- I knew it was something simple and dumb I was doing!
smokeydriver said:
Ok, so can someone tell me why I am getting stuck with 1 thing. I go to my stock recovery and into ADB sideload. When I tell it the file, it keeps failing to verify whole-file signature. What is wrong with this one step?
Or alternatively...when I'm in TWRP Alpha 2- why are all the files within the sdcard random letters and numbers?
Click to expand...
Click to collapse
Can I ask you how you fixed this? I'm having the same issue and this post popped up on Google.
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?
Hi,
Googled a while and looked around in the forum but did not find anyone with the exact same issue as me so here goes.
Maybe someone could tell me where exactly I am doing wrong.
I have a LG Nexus 5X, latest Oreo 8.1 official update.
I want to install a custom kernel to improve performance and/or battery life.
Never rooted or anything like that so I googled around to know what to do.
So I unlocked the bootloader and flashed the latest TWRP custom recovery (v3.2.1-0).
The first strange thing unlike what I kept reading in tutorials and forums is that, although I did reboot directly into recovery after flashing TWRP, and completed flashing TWRP using its interface, I was never able to reboot into TWRP unless I flashed it again. As if TWRP could not avoid being overridden by the stock recovery. So to get back to TWRP I always have to:
reboot into the bootloader: adb reboot bootloader
flash TWRP: flash recovery twrp-3.2.1-0-bullhead.img
reboot bootloader: fastboot reboot
immediately start into to bootloader (power + vol down)
choose 'Recovery Mode' from there
Which seemed odd, that TWRP wouldn't 'stick', although I was not root yet.
Which gets me to the second part. All I wanted was to root my phone.
So after not finding a consistent way to do it - it seemed every website I visited gave me slightly different instructions to do so, I took the chance and did the following:
download latest SuperSU flashable zip file (v2.82) and copy it to internal storage
go through the process I describe in the list above to get into TWRP
install SuperSU zip file (via Install TWRP option, logs seemed ok, warned me it would take a while to boot again)
reboot, wait until it boots
But the phone got stuck in the boot screen - OS does not start to load - for at least half an hour.
Luckily, probably because the OS did not load, TWRP was not overridden and so I have access to it.
My main problem at this point is that, as a newbie on this, I am not sure what can I do in TWRP to try to restore the OS.
I have tried to restore a Nandroid backup I performed before all this, and also tried to Wipe Data / Cache and Dalvik.
Both did not work - OS still won't load.
What can I do at this point? Wipe System partition? Wouldn't that delete my Nandroid backup?
Maybe 'sideload' (not sure if the right term) an official google image for my Nexus?
Sorry again if questions like this can be easily found around the forum, but from the threads I checked I did not bump into the exact same scenario...
Thank you in advance
So in the meantime I have wiped system partition, no success either.
Ended up restoring my Nandroid backup and sideloading the latest OTA from Google, which successfully restored my phone.
Of course TWRP was overridden once again.
So back to the start: can anybody help me out on the best way to permanently flash TWRP and root the phone?
Thanks!
Forget SuperSU - Use Magisk to root your phone. As for TWRP getting overwritten - any time you take an update from Google, it will generally (if not always) restore the stock recovery. The way to get around that is to download the entire current update from Google and then use fastboot to flash the individual parts (system.img / boot.img / radio.img / vendor.img)
jbaumert said:
Forget SuperSU - Use Magisk to root your phone. As for TWRP getting overwritten - any time you take an update from Google, it will generally (if not always) restore the stock recovery. The way to get around that is to download the entire current update from Google and then use fastboot to flash the individual parts (system.img / boot.img / radio.img / vendor.img)
Click to expand...
Click to collapse
Well yes, the last time I expected TWRP to be gone since I have applied the whole image, and I wouldn't expect otherwise. My problem is that TWRP is always getting overridden each time I reboot my phone. Do you have any idea why?
Regarding Magisk, I will look around to see how to use it. Could you point me in the right direction?
Also I think I read somewhere that the kernel I wanted to flash in the end - Franco's Kernel - required SuperSU and did not work with Magisk. Am I wrong?
disacrol said:
Well yes, the last time I expected TWRP to be gone since I have applied the whole image, and I wouldn't expect otherwise. My problem is that TWRP is always getting overridden each time I reboot my phone. Do you have any idea why?
Regarding Magisk, I will look around to see how to use it. Could you point me in the right direction?
Also I think I read somewhere that the kernel I wanted to flash in the end - Franco's Kernel - required SuperSU and did not work with Magisk. Am I wrong?
Click to expand...
Click to collapse
Here's the guide stickied that should walk you through the TWRP install. https://forum.xda-developers.com/nexus-5x/general/guides-how-to-guides-beginners-t3206930
Just curious you are using "fastboot flash recovery ....." and not "fastboot boot recovery...."? The "boot" method doesn't do the install.
As for Magisk. There is a whole forum dedicated to it - https://forum.xda-developers.com/apps/magisk - Short story install the latest stable version (16.0) and call it good. I haven't had any issues with recent kernel builds including Franco, EX, etc.... One thing to keep in mind is that Magisk always gets flashed after the kernel install as it does some patching of the boot.img as part of its process.
jbaumert said:
Just curious you are using "fastboot flash recovery ....." and not "fastboot boot recovery...."? The "boot" method doesn't do the install.
Click to expand...
Click to collapse
Yes, flash, not boot.
Thanks a bunch for all your help. I didn't meant to be lazy to start by reading sticked topics, but it's so much new information for a newbie that I didn't exactly know where to start. Thanks again for sharing the links.
I'm not sure if you got this fixed. But if not, first fastboot boot twrp. Then flash supersu or magisk. Then boot back into the bootloader from twrp and fastboot flash twrp. That'll solve the problem.
Sent from my [device_name] using XDA-Developers Legacy app
jd1639 said:
I'm not sure if you got this fixed. But if not, first fastboot boot twrp. Then flash supersu or magisk. Then boot back into the bootloader from twrp and fastboot flash twrp. That'll solve the problem.
Click to expand...
Click to collapse
I tried that but I'm getting no luck with SuperSU, always gets me in a bootloop (actually, technically not a loop since it remains Frozen with the Google logo)
I'll give magisk a try and come back with feedback. Maybe it has something to do SuperSU incompatibility with Oreo 8.1..
disacrol said:
I tried that but I'm getting no luck with SuperSU, always gets me in a bootloop (actually, technically not a loop since it remains Frozen with the Google logo)
I'll give magisk a try and come back with feedback. Maybe it has something to do SuperSU incompatibility with Oreo 8.1..
Click to expand...
Click to collapse
What version of super su are you using? Use 2.82 SR 3 or 5
Sent from my [device_name] using XDA-Developers Legacy app
jd1639 said:
What version of super su are you using? Use 2.82 SR 3 or 5
Click to expand...
Click to collapse
V2.82 Stable, not Service Release. Is the last stable not compatible with Oreo? Official website is not specific about it, so I just assumed it was ok.
disacrol said:
V2.82 Stable, not Service Release. Is the last stable not compatible with Oreo? Official website is not specific about it, so I just assumed it was ok.
Click to expand...
Click to collapse
3 or 5 work on Oreo. I'm not sure about stable. I don't use it.
Sent from my [device_name] using XDA-Developers Legacy app
SR5 worked like a charm. I just wish there was a compatibility matrix somewhere in their website to avoid so many forum threads and misinformation on the subject and avoid all the hustle. The whole process is dead simple but it took me days and tailored help from you guys to figure this one out.
Thanks again to all of you for your assistance.
i had that issue with a nex 6 and flashing supersu fixed it. when i got a 6p i tried the same and get stuck on the boot logo and had to sideload factory firmware to get back to go. i have a 5x on the way maybe i will try magisk.
so after i flash twrp reboot the bootloader, i open twrp and flash supersu sr5 and all is well, no more disappearing act for twrp and no more stuck on the "google"?
hello,
my device is bootlooping after i tried flashing magisk and twrp. How can i fix this?
mikachu182 said:
hello,
my device is bootlooping after i tried flashing magisk and twrp. How can i fix this?
Click to expand...
Click to collapse
try to flash stock boot.img and recovery.img
sonn3 said:
try to flash stock boot.img and recovery.img
Click to expand...
Click to collapse
Same issue. So how would we go about flashing properly?
Search for recovery.img and boot.img in stock rom and flash in fastboot mode.
mikachu182 said:
hello,
my device is bootlooping after i tried flashing magisk and twrp. How can i fix this?
Click to expand...
Click to collapse
Did you select close avb 2.0 in twrp and factory reset?
mikachu182 said:
hello,
my device is bootlooping after i tried flashing magisk and twrp. How can i fix this?
Click to expand...
Click to collapse
We would need further details on which device (region) which MIUI version (number, android, region) you were on when you attempted to install Magisk. Of course we assume here you had unlocked your bootloader first, otherwise any attempt to flash anything will result in bootloop.
Many have successfully rooted on Android 9 regardless of MIUI version.
Complication often comes with Chineses devices from what I read, Global not so much so if you are on Global device consider yourself lucky
Easiest root is probably to flash LR team TWRP If you can still access fastboot mode (voloume - + power) version 09.24 or 11.04 if you are on Android 9 or version 12.10 if you are on Android 10. Note that you probably have more chances of success being on Android 9.
And use the root feature from WITHIN that TWRP to install root on your device.
You have a complete guide of the steps to reproduce here:
Guide
I have tested on Android 9, EEA device, EEA rom MIUI 11.0.2.0 and it works without an issue if you follow the guide provided above.
If you still want to manually flash Magisk from any other recovery, make sure to use version 19.04 which seems to have the higher odds of success (update afterward from Manager).
Also as mentioned by @wang1chung do not forget to close avb 2.0.
Myself I also had RM Force encrypt option used (just in case) even if not mentionned in the thread.
But unlike what was suggested in those threads I did not wipe data.
That said since I do not want to have TWRP to stick for now, I actually want it to automatically be replaced by stock recovery all went fine for me, and Magisk is there.
And when I need TWRP for something I just flash it again and do my stuff.
Hope this helps.
Good luck!
Same problem here. Luckly fastboot was still working (vol down + power after Redmi logo gets off). Then, I've downloaded stock ROM, and tryied manually execute fastboot commands, without success. Then, I've found a .bat file inside the root folder of the stock ROM .tar.gz archive, then executed the .bat file. Phone is working back. So, whats the catch about install Magisk? Any tips?
allxdadev said:
Same problem here. Luckly fastboot was still working (vol down + power after Redmi logo gets off). Then, I've downloaded stock ROM, and tryied manually execute fastboot commands, without success. Then, I've found a .bat file inside the root folder of the stock ROM .tar.gz archive, then executed the .bat file. Phone is working back. So, whats the catch about install Magisk? Any tips?
Click to expand...
Click to collapse
Personally I used the hassle-free method pressing the button to root directly from within the LR-TWRP (09.24, or 11.04 on Android 9 MIUI), swiped, then pressed that other provided button to close AVB 2.0, swiped and it worked on first attempt.
Of course TWRP got replaced on first reboot by system recovery, but I dont care as I do not want it to stick on my device. I just flash it again when I need it.
Magisk stayed, updated it from Manager (well manager updated first to that new ugly theme.... yurk!), then Magisk updated, no problem.
Note that I am on EU Phone running EEA MIUI 11.0.2.0. You might get a different outcome with other devices/roms.
Side note, LR-TWRP 09.24 installs Magisk 19.04 which has been reported numerous time to work on most Android 9 MIUI regional versions. LR-TWRP 11.04 howevers installs Magisk 20.0 fyi.
Hope this helps,
Regards,
regarding the thread title, i had the same problem. right when i was about to retart everything all over from 0, i was glad i was able to just go into twrp and just unroot. rebooted and it started as if nothing hsppended. now i jjust gotta find which module made me bootloop.
try this n give us the result