Database Users

D800 - I just can't get CloudyG2 working no matter what I do...

I've been having issues with my phone, and I'm not sure if this is a HW issue or not, but no matter what I do, either I lose recovery or get a security error. I poked around and found some instructions in the CloudyG3 thread. They're for 3.0 but I would guess 3.3 wouldn't be different enough to brick this thing. Can't remember who the quote is from, I just copy/pasted it, but here it is:
Some of you sent me a PM asking for the install instructions on D800 and this is how you install CloudyG2 3.0:
Downloads:
1. Download CloudyG2 3.0 - https://www.androidfilehost.com/?fid=95897840722646001
2. Download Patch - https://mega.co.nz/#!sVY0mRTb!qn7S9B...3m_QpMQkgzunn0
3. Download Signal Patch - https://dl.dropboxusercontent.com/u/...l_Variants.zip
4. Download LP Baseband - http://blastagator.ddns.net/modem.php - d800-30f-modem-blastagator-signed.zip
5. Download KK Bootstack - http://blastagator.ddns.net/bootloader.php - bootstack-d800-KK_20c-blastagator-signed.zip
6. Optional: Download JB Bootstack in case if you want to revert the installation process and go back to your current ROM - http://blastagator.ddns.net/bootloader.php - bootstack-d800-JB_10d-blastagator-signed.zip
Flashing Process:
1. Backup the existing ROM (including EFS, Modem, etc.) in TWRP - very important and copy it over to the computer, just in case!
2. Wipe System + Data + Cache + Dalvik Cache - Do NOT select internal storage as it contains all your downloaded files + backups!
3. Flash KK Bootstack (downloaded from Step 5)
4. Flash LP Baseband (downloaded from Step 4)
5. Flash CloudyG2 3.0 (downloaded from Step 1) - Leave the default in Aroma when you have to pick the variant. Do NOT reboot the device as the patch installation (next Step) is very important.
6. Flash Patch (dowloaded from Step 2) - Select your variant.
7. Flash Signal Patch (downloaded from Step 3)
8. Reboot
Enjoy!
Click to expand...
Click to collapse
I'm guessing I have the incorrect files, most of the links I found in the thread with these instructions didn't seem to work so I Googled for them, maybe I don't even have the correct files. I took a screenshot in cmd of the exact filesizes.
Any help would be greatly appriciated!

level5music said:
I've been having issues with my phone, and I'm not sure if this is a HW issue or not, but no matter what I do, either I lose recovery or get a security error. I poked around and found some instructions in the CloudyG3 thread. They're for 3.0 but I would guess 3.3 wouldn't be different enough to brick this thing. Can't remember who the quote is from, I just copy/pasted it, but here it is:
I'm guessing I have the incorrect files, most of the links I found in the thread with these instructions were dead mega.co.nz links so maybe I don't even have the correct files. I took a screenshot in cmd of the exact filesizes.
Any help would be greatly appriciated!
Click to expand...
Click to collapse
you want to install cloudy g2 3.3?
this is whati did
used to root http://www.droidviews.com/easily-root-lg-devices-using-the-one-click-root-script/ if you are on lollipop it gets stuck at 90% twice after 3 attemps same stuck at 90% rebooted and it was rooted
then on playstore i used autorec canat remeber if it says v2.. but for lollipop installed and it checked my device and its said it was ready. so i just clicked twrp and it installed twrp then i downloaded blastogator twrp and installed cloudy g2 3.3 on d800 unlocked... sorry if you were refferimg to another version of cloudy..

raptorddd said:
you want to install cloudy g2 3.3?
this is whati did
used to root http://www.droidviews.com/easily-root-lg-devices-using-the-one-click-root-script/ if you are on lollipop it gets stuck at 90% twice after 3 attemps same stuck at 90% rebooted and it was rooted
then on playstore i used autorec canat remeber if it says v2.. but for lollipop installed and it checked my device and its said it was ready. so i just clicked twrp and it installed twrp then i downloaded blastogator twrp and installed cloudy g2 3.3 on d800 unlocked... sorry if you were refferimg to another version of cloudy..
Click to expand...
Click to collapse
Coming off a fresh TOT flash, I root with towelroot, flash TWRP using AutoRec, flash bootloader, then flashed Cloudy. It will boot at first, but then I run into "black screen of death" or security errors or when trying to boot to recovery, I'll run into similar issues. Does Blastagator's TWRP make the difference here?

level5music said:
Coming off a fresh TOT flash, I root with towelroot, flash TWRP using AutoRec, flash bootloader, then flashed Cloudy. It will boot at first, but then I run into "black screen of death" or security errors or when trying to boot to recovery, I'll run into similar issues. Does Blastagator's TWRP make the difference here?
Click to expand...
Click to collapse
no not really, but i do know that we had to use 2871 cause newer version were wiping f2fs, so now latest build its working but i dont think it has something to do .... am sorry i just got mine like a week ago and mine was in lollipop.. so i know nothing about coming from other version of android. dont even know whatsa tot flash.. i still need to learn alot..
check here and see if you can find a way to fix this good luck
http://forum.xda-developers.com/lg-g2/general/05-10-index-guides-fixes-roots-t3218178

level5music said:
Coming off a fresh TOT flash, I root with towelroot, flash TWRP using AutoRec, flash bootloader, then flashed Cloudy. It will boot at first, but then I run into "black screen of death" or security errors or when trying to boot to recovery, I'll run into similar issues. Does Blastagator's TWRP make the difference here?
Click to expand...
Click to collapse
I had the exact problem happen to me ....... I got the black screen of death .... phone wouldnt boot ....... and when i used the kk bootloader i would lose recovery ..... I was coming from kk to CloudyG2 ....
This is how i solved.
1. Flashed back to stock, stumproot to root Autorec v1 for bootloader
2. used Flashify to upgrade to 2.8.7.1 ( its now 2.8.7.3)
3. Downloaded n used bumpted LP bootstack and flashed blastagator stripped rom (its in flashable zip and installs everythin including modem .... patches etc EVERYTHING) http://forum.xda-developers.com/att-g2/development/rom-stock-lollipop-30b-stripped-t3144195
4. Downloaded kk bootstack , CloudyG2 3.3 and clean flashed in recovery
I have been enjoying Cloudy ever since ...... D800

Thanks all, got it running! Cloudyfa has done some absolutely brilliant work here with this ROM, as well as xdabbeb with the advanced camera driver and xCam. I'm usually a vanilla-or-nothing guy with my Android ROMs but this one is quick and power efficient. The KitKat ROM that shipped with the phone was super bloated and gross, but I'll admit LG UX 4.0 isn't really that offensive, plus I like the goodies like Multi-Window and QuickRemote. Once I disabled/hid some of the remaining LG bloat, it's surprisingly pleasant and not really that far from AOSP aesthetically. Again, cheers to those who provided the assist on this one for me!
... now my only question is, should I try CloudyG3?

TWRP backups available for download?

Hi there,
my 802 is running on TWRP after I updated to the latest stock ROM (30D Europe Open). Unfortunately due to problems mentioned in another thread I cannot install a custom ROM currently. Does anyone here have a mirror for me where I can download a TWRP backup of the stock ROM?
Thank you in advance

If you can't install a custom rom, what makes you think you can install a stock? It's pretty easy.

Very helpful... I flashed the latest KDZ on the G2, rooted it and installed TWRP 3.0.2.0, so far so good (believe it or not I flashed a dozen other android devices before). However when I try to install a Marshmallow ROM it gives me Error 7, so that means that getprop.device or so doesnt bring the correct value up. Now when I tried to switch to an older TWRP which is supposed to not have that Error 7 issue (2.7.0.0) I get an error saying I am missing the Loki files in the tmp folder. Now I do not know how to get around the Error 7 (the fix that is mentioned on here didnt work for me, brings up Error 6 instead) I would like to return to a stock backup.
How about giving me actual advice or leaving and letting other people help?
Edit: Booted in Download Mode and flashed v30D KDZ with the 2014 LG Flashtool. Works with Stock ROM for now

Having problem rooting my Axon 7 A2017U

Hey guys, first of all sorry about my english, im french.
So my problem is: I tried rooting my Axon 7 A2017U many times, with different guides. I always end up with a softbricked phone, having to restore to stock using MiFlash.
My bootloader is unlocked, i have stock recovery and stock rom for now.
Whenever i flash TWRP, either the signed one (from @tenfar) or unsigned (and up to date) ones, i can't go past the menu saying something like "your phone cant be checked for corruption, please lock your phone [...]" it just freeze. i did read somewhere that i should flash chainfire's root or a special .zip that, i guess, disabled some check that could prevent booting a phone with unsigned stuff/edited system (after flashing TWRP, so it could boot) that didn't work out. i think i found that information in some LineageOS thread here on XDA.
My ultimate goal would be to get a rooted stock nougat 7.1.1, up to date TWRP recovery and to be able to switch to LineageOS to try it out soon.
For what it is worth, i rooted many phones over the years, so while i'm no expert, i should be able to follow most of the steps you give me.
Thanks alot!

What version of TWRP did you flash first?

I have the same root problem i can not install in twrp install in twrp ok but su application displays no root cause i have latest twrp

KwesiJnr said:
What version of TWRP did you flash first?
Click to expand...
Click to collapse
this
https://forum.xda-developers.com/axon-7/development/recovery-official-twrp-zte-axon-7-t3515715
And @tenfar's signed one

KwesiJnr said:
What version of TWRP did you flash first?
Click to expand...
Click to collapse
this
https://forum.xda-developers.com/axon-7/development/recovery-official-twrp-zte-axon-7-t3515715
And @tenfar's signed one

Okay. Download and flash this one alone via fastboot and see what happens. This is one the I personally use. It is required for any of the newer versions to work properly.
twrp-3.0.2-2-a2017u.img
You can choose to rename it to just recovery.img, then:
1. fastboot flash recovery recovery.img
or
2.
if you choose to work with the same filename:
fastboot flash recovery twrp-3.0.2-2-a2017u.img
Select reboot to recovery from the bootloader menu now and try again.
Either way, should work fine. I know you mentioned you knew the basics, but just want to be sure.
Also forgot to mention. If TWRP works but you still can't get your phone to boot, you need to follow this guide here
You can start from the part that says:
-----------------------------------------------------
UPDATING FROM B20_Boot / B20 / B27 / B29 / B15(N)
-----------------------------------------------------
Again, that's the ROM I personally use if I want to go back to stock, not the one from the ZTE site.

Gonna try it and give feedback. thanks for taking time to help!
edit: im downloading the rom from the link you shared.
like you said, i can get TWRP to boot but not the phone.
So if i use full stock from ZTE, it can't boot with modified recovery?
edit 2: i don't know what worked, i think it might be the bootstack. or the rom by DrakenFX. now i can boot to the rom with a TWRP recovery installed. It worked, but i soft bricked again trying to flash SuperSU. So now i'm retrying with an updated TWRP.

I haven't tried that yet, but I really suspect that's the reason you're having problems. I rarely use pure stock ROMs. Like you, I'm not an expert in Android Development so I can't tell you why. Just been a flashaholic for years so made a few observations.

Which supersu are you installing? If you're swiping to the right in twrp, you need to install the dm-verity zip or supersu 2.79. There's some issues with newer builds.

Everything is working like a charm! Now im going to finally give lineageOS a try
I used Chainfire's SuperSU 2.79 stable.
Edit : Everything is working flawlessly! I'm running the lastest LineageOS nightly with root (Chainfire's 2.79). Followed their instruction and installation was smooth as butter. I should also point out i flashed the lastest official TWRP which seems more stable than the one @KwesiJnr suggested. The one he suggested was giving me some "can't read X partition" in red text everywhere in the log section, which the official one doesn't do. It was doing his job properly anyway though.
I can't thank @KwesiJnr enough, it helped me find the single mistake i was making.

lololo2 said:
Everything is working like a charm! Now im going to finally give lineageOS a try
I used Chainfire's SuperSU 2.79 stable
Click to expand...
Click to collapse
Glad you're up and running root. :good:

lololo2 said:
Everything is working like a charm! Now im going to finally give lineageOS a try
I used Chainfire's SuperSU 2.79 stable.
Edit : Everything is working flawlessly! I'm running the lastest LineageOS nightly with root (Chainfire's 2.79). Followed their instruction and installation was smooth as butter. I should also point out i flashed the lastest official TWRP which seems more stable than the one @KwesiJnr suggested. The one he suggested was giving me some "can't read X partition" in red text everywhere in the log section, which the official one doesn't do. It was doing his job properly anyway though.
I can't thank @KwesiJnr enough, it helped me find the single mistake i was making.
Click to expand...
Click to collapse
Yeah, like I mentioned before that was the base TWRP you needed to flash first, before any of the newer ones. You weren't intended to use it indefinitely.
There's a lot of Dev love for our device now and support is growing ... exciting new ROMs cropping up. Don't hesitate to try them out.

How to restore my Recovery-mode (TWRP)

I ran some troubles whilst was turning my android version 4.4.4 into a 8.1, TWRP helped me with the whole process (if it wasn't by those guys i'd have a bricked phone for sure). While fixing things and figuring out all the misstepped nuances on my end it come to my understandment that TWRP 2.7.1, while funcional, was flawed; since the newer versions could get rid of the necessity of dealing with adb and some weird glitches that not even 5.53785% of the internet community has dealt (or at least expressed) in the past. Errors like "broken pipes" or closed doors on a DMZ connection were spreading the adb sideload route that i had avaliable. For that reason i decided to upgrade TWRP, followed these instructions to the heart paying attention to the warning that 2.8.4 version would be needed if i want a recover-mode route for said upgrade, which made me go for the googleplay manner. My mistake was not backuping the image of the working 2.7.1 version which was in place, i've neglected such feature and gone straight to the 'download and flash' an image, which i opted for getting the 2.8.4 planning on upgrading the remanescent versions directly on recovery-mode. I never came to celebrate such accomplishment since the change of 2.7.1 to 2.8.4 via rooted TWRP app made my recovery-mode to BSoD. Ever since i've tried downgrading to 2.7.1 again to see if would at least return to the old point but i ran outta luck here. Whats the best course of action to take right now? Straight up overwrite it using this. Delete and reinstall?
TLDR::: had TWRP 2.7.1, without making backup of the working stance, installed 2.8.4 image via googleplay official app (rooted), got as result? a bricked, black recover-mode screen. Atempted to reroll to 2.7.1 by downloading it on said app, didn't worked, BSoD stay still when recovery-mode is choosen. What to do to get, if not the newest version of TWRP, at least the 2.7.1 back?

First, flash the latest stock OS (Android 5.1.1), then flash the latest TWRP (twrp-3.2.1-0-mako.img) and proceed with flashing selected rom from there.
Edit: don't use some 3rd party flashing tools, they tend to be broken and/or oudated.

n0b0dy666 said:
First, flash the latest stock OS (Android 5.1.1), then flash the latest TWRP (twrp-3.2.1-0-mako.img) and proceed with flashing selected rom from there.
Edit: don't use some 3rd party flashing tools, they tend to be broken and/or oudated.
Click to expand...
Click to collapse
Thing is: i'm now using nitrogen 8.1 Oreo, which i manage to flash via a working 2.7.1 TWRP plus the flashing tool that i've used was the one provided and advised by TWRP team themselves, the one official on googleplay. I'm up to downgrade android 8.1 to 5.1.1 but how to do it? (considering that i can't access the recovery-mode)
EDIT: perhaps you're saying for me NOT to use something like this?

I always use Skipsoft android toolkit to flash stock/custom roms.
https://forum.xda-developers.com/ne...olkit-skipsoft-android-toolkit-nexus-t1995688

This thread is over :victory:
This problem is now solved. Thank you both for taking time to express some light on my troubles, thanks for answering my plea.
HOWTO: Talking with a correspondent of official TWRP i was advised to download and flash on the official app (googleplay app, just as before) the previous version version 2.7.0 (considering my last working version was 2.7.1) to see the results. It managed to get me back a working recovery-mode screen and from there, i made the needed IMG backup and recovery backup before following the next step: downloading 3.2.1 straight from 2.7.0 (bold, if you'd ask me, but since i got 2.7.0img backup saved this time, i feared no trouble :highfive and IT WORKED!

Unable to install custom roms

I have a Tab E 8 (SM-T377P) and I cannot get any version of TWRP new than 2.8.7.0 to flash, Magisk will not flash, and no custom roms will install.
I've tried both lineage 15.1 and 16, both the standard and GO versions.
It's on stock firmware, 5.1
I rooted with cfautoroot with Odin 3.10.7.
Hopefully someone has an idea on what I need to do.
:edit:
I was able to get magisk installed by rerooting with cfautoroot and then doing a full unroot and restoring bootimage with supersu. Still can't install any roms though

So I was able to update to Nougat using the rom posted in this thread. It was the ONLY place I was able to find the stock firmware. I was hoping that installing 7.1.1 would put me on a new bootloader/kernel that might allow me to install an Oreo rom.
Still, the only TWRP that I can get to boot is the one posted in this thread, which is 2.8.7. The dev posted links to 3.0.2-1 that do not work, but I've tried multiple different versions of TWRP, and they all boot loop and I have to reinstall 2.8.7 via Odin.
All roms say that they are intended for SM-T377P and cancel, although my device is exactly that.

So, after doing a total wipe and flash back to stock 7.1.1 using Odin, I was able to boot back into Download mode and install the latest version of the TWRP posted in this thread - https://forum.xda-developers.com/ga...official-lineageos-16-0-galaxy-tab-e-t3847488
Still won't let me install a custom rom though...

Alright got it up and running on Lineage 16.
I bought this off of eBay to use as a dashboard for my smart home. When I opened it and put it into download mode for the first time, I noticed that it said it was running a custom binary even though everything looked bone stock, it wasn't even rooted. I didn't pay it any mind and went about trying to root it and install TWRP as the dew guides stated. Nothing would work, so I decided to upgrade it to stock 7.1 since it was on 5.1. After I did this, I noticed that in download mode it stated that it was on stock binary and I was able to update to the most recent TWRP for this device. Then I was able to install Lineage and all is well now.
This thread doesn't appear to be getting any traction, but I figured I'd update it in case someone searches a similar issue in the future.

Krunk_Kracker said:
Alright got it up and running on Lineage 16.
I bought this off of eBay to use as a dashboard for my smart home. When I opened it and put it into download mode for the first time, I noticed that it said it was running a custom binary even though everything looked bone stock, it wasn't even rooted. I didn't pay it any mind and went about trying to root it and install TWRP as the dew guides stated. Nothing would work, so I decided to upgrade it to stock 7.1 since it was on 5.1. After I did this, I noticed that in download mode it stated that it was on stock binary and I was able to update to the most recent TWRP for this device. Then I was able to install Lineage and all is well now.
This thread doesn't appear to be getting any traction, but I figured I'd update it in case someone searches a similar issue in the future.
Click to expand...
Click to collapse
Thank you for documenting your progress.
I am in a similar situation.
I am the original owner of my t377p.
I'm going to try your steps to see if it will work for me.
UPDATE:
Flashing back to Stock and starting the process all over again, as you described above--fixed the problem. I am now running LineageOS16.
Thank you!

I'm glad it worked for you!
That's exactly why I updated the thread, I knew I wouldn't be the last one have this odd issue.

Do you have a copy of twrp the servers are down and I've been trying for week to download it