yashsingh1/xdaforums huggingface dataset:
[Honor 5X Guides, News, & Discussion] faabricjs:
Hi mates, today i come with the unique guide for unbrick our Huanor GR5X phones :)

THIS GUIDE IS FOR FULLY BRICKED HUAWEI GR5/5X HONOR, ALL MODEL/VARIANT

ATENTION!!!

Files rawprogram0.xml and patch0.xml from my packcage its ONLY for the Huawei GR5 KII-L23 16GB VARIANT!!!

In order to continue with the tutorial, you must create your rawprogram and patch0 xml files

(mini tutorial bellow)

Ready? GO

1) Download my packcage (link MEGA)

2) Install QFIL Software. From my packcage, extract and move the folder 'Firmware' to C:\Program Files\Qualcomm\QPST\bin

3) Download and extract this .IMG files from ANY 5.1 full firmware UPDATE.APP for your model/variant

(Note: for KII-L23 is not necessary GPT.img)

GPT.img

BOOT.img

CUST.img

SYSTEM.img

TZ.img

MODEM.img

Place all img files in C:\Program Files\Qualcomm\QPST\bin\Firmware

4) Install Qualcomm drivers, Connect phone to pc, open Device Manager. If you see under com port Qualcomm USB loader or something along those lines. your good.

5) In QFIL software, if qualcomm driver are found it will say on top of QFIL software Qualcom USB loader 9008 (if say 9006,900E, you must put your phone into EDL mode with EDL Cable or EDL TEST POINT, google it)

6) Once you get the Qualcom USB loader 9008 on QFIL, you can continue

6) Select Build Type: click Flat Build

7) Select Programmer: browse to C:\Program Files\Qualcomm\QPST\bin\Firmware\prog_emmc_firehose_8939.mbn and select

8) Load XML: browse to C:\Program Files\Qualcomm\QPST\bin\Firmware and select "rawprogram0.xml" file, then select "patch0.xml" file.

9) Go to Tools and click Partition Manager

10) You will see a list with all files from partition table

11) To flash, you need select Boot.img in the list first, a mini windows will open, click on Load image and select the Boot.img placed on C:\Program Files\Qualcomm\QPST\bin\Firmware

Do the same with the rest of img files in THIS order

BOOT.img

CUST.img

SYSTEM.img

TZ.img

MODEM.img

12) Once you finish, close the partition manager. A message will appear and phone will reboot. If not, reboot manually

That's all :) enjoy!

FOR GR5 KII-L2X AND HONOR 5X KIW-L2X MODEL/VARIANT, FOLLOW THIS TUTORIAL

1) Download my packcage and exctract it

2) Open a cmd windows in 'Phyton + GPT Tools' folder

3) Type: GPTAnalyzer.py (drag and drop the GPT.img file previously downloaded from 5.1 firmware) and click Enter

4) Copy all results in cmd, paste on notepad and save as 'Partition0.xml' (start with <?xml version... and finish on </configuration>)

5) Type GPTParseTool.py -x (drag and drop the partition0.xml created) and click enter

6) Go to phyton folder and move all created files to C:\Program Files\Qualcomm\QPST\bin\Firmware

7) Now you can continue with the guide

Thats all my friends, hope you get a new life for your Huanor GR5X

PLEASE IF I HELP YOU, BUY ME A COFFE HERE :)
[Honor 5X Guides, News, & Discussion] faabricjs:
Reserved
[Honor 5X Guides, News, & Discussion] wsdyleon:
GOOD guide！someone will need it！

my question：does it work on the locked phone?
[Honor 5X Guides, News, & Discussion] faabricjs:
Thanks!

Locked and unlocked devices.
[Honor 5X Guides, News, & Discussion] snazzyman89:
My dear friend, there is no python tools folder in your package. i can't unbrick my phone with your xml files, its a KLL-L21.

Best of regards.
[Honor 5X Guides, News, & Discussion] Ibrahim Tariq:
I cant find python + GPT tools
[Honor 5X Guides, News, & Discussion] Ibrahim Tariq:
my device is not showing up I have removed the battery and connected the usb but nothing happens only the device vibrates and huawei logo apears but nothing on my pc
[Honor 5X Guides, News, & Discussion] hsheemi:
Here you will find all files needed and instructions

You have to open the phone and put it in EDL mode

Search Google for that

https://forum.hovatek.com/thread-31505.html
[Honor 5X Guides, News, & Discussion] hsheemi:
See my reply in previous post #8

---------- Post added at 02:15 AM ---------- Previous post was at 02:06 AM ----------

Can't we use Huiye Download Tool to flash all the images ?
[Honor 5X Guides, News, & Discussion] frenkensteinGSM:
what if i dont have system.img in my firmeware ? what should i do ? i have firehose from b321 can this be compatible with b330?

EDIT : i found the sys.img for b321
[Honor 5X Guides, News, & Discussion] frenkensteinGSM:
friends help me out i have KiW L21 superbricked unable to charge battery and he dont show up in device manager as qloader 9008
[Nexus 7 (2013) Android Development] ripee:
Reserved
[Nexus 7 (2013) Android Development] JT1510365:
Awesome! Keep up the great work and thank you for keeping this devices development alive:)
[Nexus 7 (2013) Android Development] ripee:
All credit to followmsi and flex1911 ;)
[Nexus 7 (2013) Android Development] dealpapa1:
oh yeah maga

make android great again
[Nexus 7 (2013) Android Development] DaCl88:
Is this the same ROM you can find in followmsi androidfilehost directory?

https://androidfilehost.com/?w=files&flid=289297

Yesterday I try the Ressurection Remix 7.0

Everything works fine.

But in Kodi i cannot use the h264 hardware decoder.

Have this Rom the same issue?
[Nexus 7 (2013) Android Development] ripee:
Since the sources I linked are followmsi's, yes this is the same rom, but built more recently to take advantage of the lineage commits added since followmsi's last build. Because of this, it will have the same h.264 bug in Kodi.
[Nexus 7 (2013) Android Development] gaja22:
Rom is working very well but I cannot flash Gapps. I chosen Pico 9.0 arm. Which one should I use ? Thank you !
[Nexus 7 (2013) Android Development] ripee:
Did you re-partition the memory, as described in the FAQ's in the OP?
[Nexus 7 (2013) Android Development] JT1510365:
Of course:)
[Nexus 7 (2013) Android Development] yourrealking:
To a person who has installed this ROM, I have one question. If the orientation is locked to Landscape, when you turn on the screen, does the screen start from landscape mode, or does it start from portrait mode and quickly rotates to landscape mode?

It does not happen on the official LOS 14.1, but it did happen with unofficial LOS 15.1. This rotation is problematic, because it often causes a significant delay when I turn on the screen, depending on the app I had been using.
[Nexus 7 (2013) Android Development] MartinX3:
Thx!

Will test this ROM! :D
[Nexus 7 (2013) Android Development] amityg:
Hello, my lock screen will be temporarily displayed in portrait then rotates to landscape.
[Nexus 7 (2013) Android Development] hlxanthus:
Quick question. A full data wipe? As in a full data partition wipe including rom backups, pictures, videos, personal files? Cant say I have ever hear of a rom requesting this and I have been flashing roms for a decade. Perhaps I am missing something. Is this only the first time I flash and then a dirty flash for daily builds?
[Nexus 7 (2013) Android Development] ripee:
A full data wipe cleans the data partition on which user apps and system settings reside. Your personal files are on the internal storage partition, which does NOT get wiped by TWRP when factory wiping.

Yes, clean flash prior to the first flash, then dirty flash subsequent builds.
[Nexus 7 (2013) Android Development] hlxanthus:
Read the OP's instructions again. It clearly says to wipe data and internal storage.
[Nexus 7 (2013) Android Development] JoliOS:
Hi and thanks for (the) pie. It works great for the main user but i have a strange problem with a secondary (or guest) user:

Whenever i switch to the secondary user the navigation bar (three buttons) disappears. The bar is not just hidden but seems to be really gone/killed. When switching back to the main user the bar is still missing and i need to restart to get it back. Any ideas?
[Nexus 7 (2013) Android Development] Goon818:
The pie ROM works great on my Nexus. Thank you so much. It's amazing. I hope you plan to add the security patches every month. Thx.
[Nexus 7 (2013) Android Development] ripee:
Yes, I have read the OP. Wiping both data and internal storage is for the sake of less experienced users who should be starting fresh no matter what rom they're coming from. As you have more experience, please use your judgment to wipe whatever you know needs to be wiped.
[Nexus 7 (2013) Android Development] chamo87:
the last update broken my system... i changed user, after change, swipe the lock screen, and black screen. Restart, booted up, go instant black screen. Reflash the last rom, booted up, black screen instantly. Reflash 0413 rom, no work very well
[Nexus 7 (2013) Android Development] JambaFee:
Same here (flo): Build 0422 leads to an endless dark screen after lineageos-logo. Build 0421 works.
[Nexus 7 (2013) Android Development] dansblackcat:
No issue for me on 422. Just tried a few reboots but all seems ok. Also upgraded TWRP to latest and it still booted fine.
[Nexus 7 (2013) Android Development] MaxPowerOne:
Is there a possibility that it will became an official or sort of build? I'm using a nexus 7 2013 as my daily tab, I need stability to be able to always use it for university work on the go. The lastest offcial lineageos build was 14 right, with 15 still unofficial? Do you guys think I should go with official? And, is it offcial still offcial as it's not directly supported no more?
[Nexus 7 (2013) Android Development] banksio:
Personally I doubt it, since NFC and the compass are buggy it can't be verified to be "stable". The unofficial builds are not much different though, in the case of this thread they're just official lineage sources built by people other than the lineage build bot.
[Nexus 7 (2013) Android Development] JambaFee:
Build 0422 not working

Same on my deb-device: Build 0422 hangs, build 0421 runs without any problem.
[Nexus 7 (2013) Android Development] dealpapa1:
Please try 0427 one
[Nexus 7 (2013) Android Development] Miho.Nightwalker:
Hi all. I cannot flash newer TWRP required. I'm getting error size too large. Any ideas? Edit : seems I got it working. TWRP 3.3.3.0. Edit 2 : Device not booting into any recovery now. Tried older TWRP to no avail, tried latest TWRP and it's the same. Stuck on Google logo. :( Edit 3 : Repartitioned the device successfully. It should be ok from here :) Edit 4 : Thank you Dev :) working ok
[Nexus 7 (2013) Android Development] djdarkknight96:
Ugh okay issue, USB broken. So can't partition unless I get it fixed... Anyone with a special trick? Shot in the dark, I already know the answer lol
[Nexus 7 (2013) Android Development] JambaFee:
Tried 0427 on flo - same behaviour: lineageos-logo appears, then "tablet starting", then grey screen (not black, if this is of any meaning). Are there logfiles I could provide?
[Nexus 7 (2013) Android Development] Tesju:
I cant flash -" addonsu-16.0-arm-signed.zip".can anyone help?thanks!
[Nexus 7 (2013) Android Development] Donlagos:
In this case there was no need to reflash, just wipe Cache/Dalvik and Cache in recovery is enough to fix the black screen problem
[Nexus 7 (2013) Android Development] Donlagos:
Thanks and great work this Rom to keep our flo/deb alive,

I found two bugs in the flo version:

1 - After playing with extreme power savings menu I can't get out of the dark settings anymore, I like the dark menu but no way to get out anymore.

2 - Using the built-in camera in this Rom I can't make a direct picture inside WhatsApp, I have to use the camera first.
[Nexus 7 (2013) Android Development] pitrus-:
1 - This is probably a fault in generic LineageOS strand and nothing that can be fixed here.

2 - Probably a camera HAL based incompatibility and hard to fix as there wont be any newer binaries released for this tablet.

Skickat från min ONEPLUS A3003 via Tapatalk
[Nexus 7 (2013) Android Development] dealpapa1:
wipe everything and use micro usb otg to install. rom only no play store nothing else. :silly:
[Nexus 7 (2013) Android Development] kcv_earner:
Upgraded from CM 14.1 without problem.

Thanks for this work.

Nexus7 Flo is up and running on LOS 16.0 now.

So far, no problems. :good:
[Nexus 7 (2013) Android Development] dendk:
Been following (lurking) reading the Dev work on the Nexus 7 flo for some time, have installed many a ROM on the device some good some bad, sometimes ending up with a blinking screen :) Now I have installed the unofficial 16 builds, thank you to everyone who contributes to the cause. So far it looks good, had issues with the pixel launcher (known issue) the advised re-partitioning worked well, installed latest twrp 3.3.0-0-flo, build 427 along with the the Full Gapps bundle and Magisk.
[Nexus 7 (2013) Android Development] Heinz-:
Screen always in landscape mode?

Hi,

at first thank you for further development of LineageOS for the old Nexus 7 "deb". I always use it in landscape mode and am often annoyed by turning it from itself to portrait mode. Is there any configuration file where I can set "always use landscape mode" globally in LineageOS 16? The screen auto rotation doesn't work. The tablet is rooted (of course :D ).

Thannk you,

Heinz
[Nexus 7 (2013) Android Development] AlesUlrych:
If the auto-rotation is working before you upgrade to LOS 16,

just after the new LOS 16 builds no longer, just reboot the tablet (or turn it off and on). It then works normally.

If your rotation has not worked for a long time, try the tutorial here: auto rotation fix

it helped me and still auto-rotation works. :)

Ales
[Nexus 7 (2013) Android Development] JambaFee:
I did as you said and it worked. After hours of reinstalling and configuring apps and a lot of reboots everything seemed to be fine but then after another reboot the device hung again. Finally I switched back to my last known good build 0421.
[Nexus 7 (2013) Android Development] shuvam.gayen:
how to add support for indian languages?
[Nexus 7 (2013) Android Development] Heinz-:
Thank you Ales for your quick answer! Indeed my tablet does not auto-rotate anymore since it got wet :rolleyes: a little bit. Seems to be an easy repair. Fortunately I recently bought a second Nexus 7 for testing. :D

But my question is how to fix the screen in landscape mode. There must be a onfiguration file where I can st the orintation globally.
[Nexus 7 (2013) Android Development] sidamos77:
[MENTION=5480152]followmsi[/MENTION]

Please find attached the logs from Unlegacy Pie EXPERIMENTAL-20190403-1141 and LOS 16.0 20190427-UNOFFICIAL-deb.

My deb goes to deep sleep with Unlegacy (0.6% battery/hour), but does not go to deep sleep ever with LOS (2% battery/hour).

LOS 14.1 went also to deep sleep (0.25% battery/hour, WiFi off during standby).

I'd love to use Pie on my deb, but standby battery is important for me.

Thanks!
[Nexus 7 (2013) Android Development] followmsi:
This topic has been discussed in AOSP/AEX thread before.

I have added wakelock fix for deb ( taken from mako device ) - this "fix" is disabled by default and needs enabled via kernel manager app.

Just activate and test .. it may improves your situation.

[MENTION=6005084]ripee[/MENTION]

Pls make LOS 16.0 test build with unlegacy kernel .. maybe it improves wakelock/ deep sleep topic for flo/deb devices.

They still use "older" kernel and earlysuspend ..

https://github.com/Unlegacy-Android/android_kernel_qcom_msm8960

For earlysuspend you need patches for system/core ..

https://github.com/Unlegacy-Android/android_system_core/commits/aosp-9.0

Sorry.. no time to drive this stuff.

Cheers
[Nexus 7 (2013) Android Development] ripee:
Changelog

Build 0501 for both variants

* Wakelock and earlysuspend added, as per followmsi's post #204. These are one-off changes for now. If they work well, followmsi will no doubt merge them into his repos.

* Synced with LineageOS sources.
[Nexus 7 (2013) Android Development] sidamos77:
You mean the "Msm_hsic_host Wakelock"? I enabled this in Kernel Adiutor, but it did not help. Maybe because I do not have a SIM card in my deb and have Airplane mode enabled (+ WiFi on) anyway.

---------- Post added at 10:56 PM ---------- Previous post was at 10:40 PM ----------

Something is wrong with this version. When I scroll (left to right in Nova launcher desktop or up and down in Nova launcher apps list), the rendering is out of sync with the screen refresh, meaning it is tearing.

Also happens in Chrome.

---------- Post added at 11:32 PM ---------- Previous post was at 10:56 PM ----------

LiveDisplay is also broken. Also auto brightness, I think.

I can fix the tearing 99% by deactivating HW Overlays in developer options.

On the bright side: my deb now goes to deep sleep. :)

I will report battery drain tomorrow.
[Nexus 7 (2013) Android Development] JambaFee:
Installed build 0501 on my deb device, this time the tablet booted without any problem. Unfortunately I didn't have root access anymore, rooting with magisk solved this problem.

But there are two new problems:

*) No access via USB from PC

*) No reboot into bootloader or recovery via power button. The device boots to system instead, accessing bootloader or recovery is only possible with the power/vol button combos.
[Nexus 7 (2013) Android Development] MaxPowerOne:
It works good! I only noticed a small graphic bug on the circle button in the bottom bar after youtube switching beetween portrait and landscape(clean install). How can I get root? It only shows adb not apps for root access.
[Nexus 7 (2013) Android Development] christnt:
I reverted to the previous version, from 4/27. As a consequence, no more tearing, nor glitches on round corners, and LiveDisplay works back again.

With both versions I have an issue with the camera, though.

It works well with the stock camera app, but is vertically split and very noisy and unsaturated on the right side while using with other apps such as Chromium-based Brave web browser (using in-app function to sync using QR code) and, for example, Dog Breed, an app that identify dog breeds from a picture you can take with the camera. I haven't test other situations.
[Nexus 7 (2013) Android Development] dendk:
Clean install or an upgrade...just curious I have not so much as a flicker with the rotation on build 427 on my newer Nexus 7 2013. But my other Nexus 7 2013 suffers from rotation and USB issues (Hardware problem).. Ended up putting rotation control pro on it.
[Nexus 7 (2013) Android Development] christnt:
Downgrade, without cleaning any caches.

Basically using the Install option in TWRP 3.3, selecting the zip and rebooting.

lineage-16.0-20190427-UNOFFICIAL-deb.zip

Size: 358.25MB (375650726B)

MD5: 4ba09cc594f3714baa20fb73465066e3

Type: zip / Store

File count: 11

Content size: 358.80MB (376230666B)

Compression ratio: 99%
[Nexus 7 (2013) Android Development] MaxPowerOne:
Is there a kernel for overclock compatible with this rom?
[Nexus 7 (2013) Android Development] followmsi:
Nice .. I saw your changes.

https://github.com/ripee/android_device_asus_flo/commit/5b56ea21676872cfe20b989875aa63b44269e874

You did use "my" kernel config for this build ?

We may test original unlegacy config as well ..

flo-deb-unlegacy-kernel-pie-20190502-unlegacy-config.zip

flo-deb-unlegacy-kernel-pie-20190502-followmsi-config.zip

This are standalone kernels .. but they do require pachted libsuspend to run properly, like in your 05/01 ROM.

For testing I did boot the followmsi config version on current AEX - without patched libsuspend - super slow graphics.

As well I made "pure" lineage-16.0 kernel .. without all the Franco/EX patches/features.

And the current "followmsi-aosp" kernel for comparison and easy switching.

The EX Pie version is located in the same gdrive folder.

flo-deb-lineage-kernel-pie-20190502.zip

flo-deb-followmsi-aosp-kernel-pie-20190502.zip

All kernels are TWRP flashable installer .. tested on AEX .. should run on all other ROM too.

Let's test a bit ..

Cheers
[Nexus 7 (2013) Android Development] sidamos77:
[MENTION=6005084]ripee[/MENTION], [MENTION=5480152]followmsi[/MENTION]

Not so good news: Although I have now 99% deep sleep on standby with build 0501 on my deb, it still drains 2%/hour on standby (0.6%/hour with Unlegacy, 0.25%/hour with LOS 14.1).
[Nexus 7 (2013) Android Development] lolcopter:
Can confirm screen tearing on the 0501 test build, as well as the blank screen issues on 0422 and 0427. Would like to revert back to 0421 but I deleted it already like a dummie, oh well. My blank screen issues were resolved (temporarily?) with a soft reboot. So no huge game stoppers or anything, but the screen tearing can get annoying. Thanks again for all the work you guys!

Edit: this is on flo fwiw
[Nexus 7 (2013) Android Development] followmsi:
Pls test the 2 unlegacy kernels above .. on your current 05/01 ROM.

I do own flo device only .. for this reason I am very limited in testing.

Deb device seems to have more "sleep issues" due to USB Modem for LTE.

The wakelock fix seems not to work properly, as you have tested.

On flo are certain apps blocking deep sleep .. sometimes.

If I stop those apps I get 10 days standby on flo device, using "my" normal kernel.

The EX kernel will take more juice as a lot of the dt2w .. etc. features are enabled by default.

My kernel does have the similar features, but disabled by default .. less juice.

The pure lineage kernel does not have any "features" but it may increase your battery life.

The EX kernel, lineage and followmsi kernel will require any other ROM, but not this lineage 05/01 build.

Just test a bit .. not sure if and when we can improve the situation for deb.

Cheers
[Nexus 7 (2013) Android Development] sidamos77:
Thanks, I'll test the 2 unlegacy kernels and report back.

BTW, could I flash the flo ROM? I do not need the cell radio anyway.
[Nexus 7 (2013) Android Development] AlesUlrych:
Hi,

I just found out that the LiveDisplay settings stopped working on the 0501 build. Display Mode Still: "Disable All Edits"
[Nexus 7 (2013) Android Development] jhford:
Glitchy touchscreen

I have 2 debs and i noticed this issue on one of them yesterday. It manifests itself while typing and scrolling and the screen flashes with each touch. I use the Swype keyboard and have for years. It's no longer supported yet still works flawlessly. I use it on my N910T also which is running Ripee's companion Pie ROM., which does not glitch. So, I thought it was a hardware issue and that I needed to open it up and reseat the ribbon cables. But I'm typing or struggling to Swype this post on my other deb and it is behaving identically. So, it's not hardware. I'm running 5/1, but I don't recall if 5/1 introduced it.

EDIT: I thought it might be browser specific; I've been trying Brave. But the issue is definitely system wide affecting all software and apps. The screen is almost unusable.
[Nexus 7 (2013) Android Development] sidamos77:
Build 0501, kernel from 0501: Deep Sleep = yes, 2%/hour, screen tearing

Build 0501, Unlegacy kernel with Unlegacy config: Deep Sleep = yes, 1.7%/hour, screen tearing, tablet overall slow

Build 0501, Unlegacy kernel with FollowMSI config: Deep Sleep = yes, 1.9%/hour, screen tearing

Build 0427, kernel from 0427: Deep Sleep = no, 2%/hour

Unlegacy Pie: Deep Sleep = yes, 0.6%/hour

LOS 14.1: Deep Sleep = yes, 0.25%/hour
[Nexus 7 (2013) Android Development] followmsi:
As it looks like the kernel replacement does not improve a lot ..

Pls test lineage version before 04/21 .. here we still use CAF sources and another device tree.

Are you able to determine the service/process/app which is draining battery on your deb ?

If you use tools like betterbatterystats .. do you see the "culprit" ?

Maybe this one ..

https://xdaforums.com/showthread.php?p=79439386
[Nexus 7 (2013) Android Development] sidamos77:
At least it goes to deep sleep since 0501. BBS or GSAM point to the kernel as the culprit.

I started my LOS Pie tests with version from 04/13. This also did not go to deep sleep and drained 2%/hour.

I find it strange that 0501 does go to deep sleep and still drains 2%/hour.
[Nexus 7 (2013) Android Development] followmsi:
If you check kernel wakelocks in bbs ?

What about sensors section in bbs ? .. what is listed here ?
[Nexus 7 (2013) Android Development] sidamos77:
Right now, I have installed Unlegacy again for comparison. But I remember checking wakelocks and sensors with LOS before 0501. There were no wakelocks and only acceleration sensor usage from Nova launcher.