http://www.lg.com/global/support/opensource/opensource.jsp < ORIGINAL LG SOURCE CODE LOCATION.
MIRRORS TO ALL SOURCE CODES
On this LG official source code site, LG technical team members are literally responding to requests sent by L9 users worldwide. They have already released source codes for following L9 Variants, but we dont know if any developer is really working on it or not.
LGP760
LGP768F
LGP768G
LGP769
LGP769BK
According to wkpark here, earlier LG have leaked the RSA keys and signing tools, inside source codes for P920/SU760. Its too sad to see, we even dont have anyone good enough who can test above source codes and make custom roms with unlocked bootloaders and modified kernels. Can anyone share more information on this?
==========================================
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This is strange. I downloaded the source code for P769BK. It seems everything needed to build the stock ROM (with instructions in README) is there. Why no body is building, say CM 9/10 and all different variants of ROM based on top of this is beyond me. Maybe this device is not popular? Or maybe this phone is still relatively new, so developers will arrive in the future. My previous phone is from Samsung and there are just too much custom ROMs from XDA-developpers to choose from.
I would say that its popular period has only just begun. Same happened with the Galaxy S Blaze 4G; First few initial months were empty, then developer interest in the device slowly but surely poured in.
mrmathematica said:
This is strange. I downloaded the source code for P769BK. It seems everything needed to build the stock ROM (with instructions in README) is there. Why no body is building, say CM 9/10 and all different variants of ROM based on top of this is beyond me. Maybe this device is not popular? Or maybe this phone is still relatively new, so developers will arrive in the future. My previous phone is from Samsung and there are just too much custom ROMs from XDA-developpers to choose from.
Click to expand...
Click to collapse
Thats what I wondering since long time.
AwesomeTurtle said:
I would say that its popular period has only just begun. Same happened with the Galaxy S Blaze 4G; First few initial months were empty, then developer interest in the device slowly but surely poured in.
Click to expand...
Click to collapse
We all know this device is powerful but not popular. But looking at the negligence of developers to this device in spite of available source codes, it seems this device cursed.
Because LG links (kdz/sources) are disappearing suddenly, I downloaded all source codes and uploaded to MIRRORS and kept in one place since a month or more (20 Jan). So if LG plays smart we still have sources. But sadly, no one seem to even notice or discuss it, hence this thread.
CLEAR INSTRUCTIONS TO BUILD ROM AND KERNEL IN P769_README.txt FILE
P769_README.txt P769 V11A
------------------------------------
How to build
1. Android build
(1) Get the android base source code.
- Download the original android source code ICS 4.0.4 (android-4.0.4_r1.1) from http://source.android.com/source/downloading.html
(2) Overwrite modules that you want to build.
- Untar opensource packages of LGP769_ICS_Android.tar.bz2 into downloaded android source directory
- And, merge the source into the android source code
(3) Run the build scripts.
- You have to add google original prebuilt source(toolchain) before running build scripts.
- Run the following scripts to build android
a) source build/envsetup.sh
b) lunch full-eng
c) make -j4
* When you compile the android source code, you have to add google original prebuilt source(toolchain) into the android folder
* "-j4" : The number, 4, is the number of multiple jobs to be invoked simultaneously.
2. Kernel Build
- Untar using following command at the android folder:
tar xvfj LGP769_ICS_Kernel.tar.bz2
- change directory to kernel root
cd kernel
- make configuration:
make u2_p769_defconfig ARCH=arm
- make kernel zImage:
make ARCH=arm CROSS_COMPILE=../prebuilt/linux-x86/toolchain/arm-linux-androideabi-4.4.x/bin/arm-linux-androideabi- zImage
3. You can download TI omx open source from TI web site (http://omapzoom.org).
The location of TI omx open source is android/hardware/omx directory in android source.
I'm trying to release AOSP and AOKP roms, but have not enough time to do it right now. Stay tuned.
cmahendra said:
Thats what I wondering since long time.
We all know this device is powerful but not popular. But looking at the negligence of developers to this device in spite of available source codes, it seems this device cursed.
Click to expand...
Click to collapse
Hopefully not.
Because LG links (kdz/sources) are disappearing suddenly, I downloaded all source codes and uploaded to MIRRORS and kept in one place since a month or more (20 Jan). So if LG plays smart we still have sources. But sadly, no one seem to even notice or discuss it, hence this thread.
Click to expand...
Click to collapse
If no one else, I can try. But I don't really have the expertise to do it. Even rooting this one following Lulus method took me a day. So don't count on me. I might get stuck easily.
cmahendra said:
CLEAR INSTRUCTIONS TO BUILD ROM AND KERNEL IN P769_README.txt FILE
P769_README.txt P769 V11A
Click to expand...
Click to collapse
If the builded kernel can be flashed, this mean that it's signed and maybe we can grab the rsa key..
As far as I understood, the tool makes a "zImage" and i don't think it's flashable since the zImage is inside the boot.img, and we must sign the boot.img to flash it.
Edit: seems like we can boot/flash a zImage with fastboot
http://forum.xda-developers.com/showpost.php?p=7351290&postcount=3
If this works, we don't need unlocked BL to flash a custom kernel..
sguerrini97 said:
If the builded kernel can be flashed, this mean that it's signed and maybe we can grab the rsa key..
As far as I understood, the tool makes a "zImage" and i don't think it's flashable since the zImage is inside the boot.img, and we must sign the boot.img to flash it.
Edit: seems like we can boot/flash a zImage with fastboot
http://forum.xda-developers.com/showpost.php?p=7351290&postcount=3
If this works, we don't need unlocked BL to flash a custom kernel..
Click to expand...
Click to collapse
It doesn't work that way.
You can compile kernel, repack boot.img, flash it easily but you'll end up with security error and semi bricked phone.
We need to find a way to unlock bootloader or way to sign custom kernel first.
Lelus said:
It doesn't work that way.
You can compile kernel, repack boot.img, flash it easily but you'll end up with security error and semi bricked phone.
We need to find a way to unlock bootloader or way to sign custom kernel first.
Click to expand...
Click to collapse
I know that we can't flash the boot.img without unlocked bootloader, but if we compile the original kernel from source we should get the "zImage", can we boot or flash it with fastboot? If not, why they released source and a guide to compile the kernel?
sguerrini97 said:
I know that we can't flash the boot.img without unlocked bootloader, but if we compile the original kernel from source we should get the "zImage", can we boot or flash it with fastboot? If not, why they released source and a guide to compile the kernel?
Click to expand...
Click to collapse
you CAN flash boot.img with locked bootloader, you won't be able to boot it and will need to restore you phone.
They released source because they have to comply with GPL,
Lelus said:
you CAN flash boot.img with locked bootloader, you won't be able to boot it and will need to restore you phone.
They released source because they have to comply with GPL,
Click to expand...
Click to collapse
There's always 2nd-init. It just make things harder (for noob like me at least), but not impossible. Look at TEAM LGICS's port of CM9! I think it works at least on p760 and p765.
Also with the locked bootloader, didn't they break GPL in sprite anyway:
http://gpl-violations.org/faq/sourcecode-faq.html
Section `` What are "scripts used to control installation"? '' :
Please note that this is of special practical importance in the case of embedded devices, since the executable program(s) need to be somehow installed onto the device. If the user is not given a way to install his own (modified) versions of the program, he has no way of exercising his freedom to run modified versions of the program.
Click to expand...
Click to collapse
I have already compiled the kernel from source but I have been told that it will cause a "security error" and that I would have to reflash. I'm not a really good developer but clemsyn taught me a few tricks
If there is a way to sign the boot.img to enable it to pass the security test, please post the instructions and I will try it on my phone. BTW, I only plan to change the zimage at the moment. Is it confirmed that only changing the zimage in the boot.img triggers the security error?
http://forum.xda-developers.com/showpost.php?p=38595867&postcount=5
We need a brave man to try whether this `patched bootloader' works.
Maybe someone who has already semi-bricked his phone with mirrored-screen/touch already can be the guinea pig?
Lelus said:
you CAN flash boot.img with locked bootloader, you won't be able to boot it and will need to restore you phone.
They released source because they have to comply with GPL,
Click to expand...
Click to collapse
I know it will hang on security error, I tried a recovery.img long time ago.
But as far as I understood "fastboot boot zImage" will directly boot a zImage without flash it, and the zImage have not to be signed to work, am I right?
sguerrini97 said:
I know it will hang on security error, I tried a recovery.img long time ago.
But as far as I understood "fastboot boot zImage" will directly boot a zImage without flash it, and the zImage have not to be signed to work, am I right?
Click to expand...
Click to collapse
I think zImage would still need to be signed but can't say that for sure.
R: Are there any Developer to work on L9 Source Codes?
pinoyto said:
I have already compiled the kernel from source but I have been told that it will cause a "security error" and that I would have to reflash. I'm not a really good developer but clemsyn taught me a few tricks
If there is a way to sign the boot.img to enable it to pass the security test, please post the instructions and I will try it on my phone. BTW, I only plan to change the zimage at the moment. Is it confirmed that only changing the zimage in the boot.img triggers the security error?
Click to expand...
Click to collapse
Can you share the zImage to let me try it?
Edit: if it's not for p760 or if you want to try it yourself, use the fastboot tutorial and try to boot it.
Code:
fastboot boot zImage
Inviato dal mio LG-P760 con Tapatalk 2
sguerrini97 said:
Can you share the zImage to let me try it?
Edit: if it's not for p760 or if you want to try it yourself, use the fastboot tutorial and try to boot it.
Code:
fastboot boot zImage
Inviato dal mio LG-P760 con Tapatalk 2
Click to expand...
Click to collapse
I have a p769. I'm kinda hesitant to try it since I'm a newbie in developing. Can I just do a kdz flash if I mess it up?
From the instructions given by LG itself, can someone please compile this?
LGP769BK(Optimus L9)_Android_ICS_P769v10e
This will help us to get P769v10e KDZ also to flash.
pinoyto said:
I have a p769. I'm kinda hesitant to try it since I'm a newbie in developing. Can I just do a kdz flash if I mess it up?
Click to expand...
Click to collapse
That command should only attempt to boot the zImage, it will not flash it so if something goes wrong you should be able to reboot normally with the power button, but I didn't tested it to confirm. If you can build the p760 zImage, I can try it
Related
Congratulation to all who's been waiting for this!
First things first! Be careful, I'm not to blame if you brick your device.
WARNING - See the second post for reported problems
This ROMs are for the North American aka US devices (YP-GI1CB), if you have an international device (YP-GI1CW), you should go to this thread which was created by our good friend zebluk. Also there is a wonderful tutorial how to flash the rooted image in that thread, so you can follow it (but use the image from this thread). All credits to zebluk!
So..
-------------
When downloading from the mirrors, be warned, I have not checked them, you should check their integrity by calculating their sha1 hashes and comparing with ones I am providing for each file.
Here is the PIT file.
Here is the STOCK FACTORYFS ROM (size: ~260 MiB, sha1: 709ea3a1594fe4776065308a198e120129652b38)
Mirrors:
Mirror by ECLK09 (password: XDA-DEV)
Here is the STOCK KERNEL (size ~5.2 MiB): sha1: 25235a0ed6ad42cab1743b8f1c141248efb25647)
Mirrors:
Mirror by ECLK09 (password: XDA-DEV)
-------------
And here is the ROOTED STOCK ROM (size: ~260 MiB, sha1: 64ec57e6254b3c24ad7740b0c2bcad3a6e4bd26c)
Mirrors:
Mirror by ECLK09 (password: XDA-DEV)
-------------
Password for all the 7zip archives: XDA-DEV
First you should un-7zip your downloaded file, there you will have directoriy with a descriptive name and a tarball archive inside.
You can flash these tarball (without extracting) using Odin v3.04 (Attached) or extract the image file from the tarball archive and flash using Heimdall v1.3.1 (don't use the 1.3.2 version). I've personally tried flashing only with Heimdall under Linux, but Odin should work too.
If you are using Windows and you don't have device drivers, download them from here.
@Good Guy User:
DepositFiles is not the best filesharing service but works well for me, feel free to create mirrors and share links in PM, I'll post them here.
Greetz to: Entropy512 for showing the correct road, zebluk for help and advices, baruch6132 for flashing my untested rooted kernel and dumping the factoryfs, zaclimon and baladev for helping, Benjamin Dobell and Glass Echidna for Heimdall, jazzor for ext4_utils, William Enck for split_bootimg.pl, ECLK09 for providing mirrors for uploaded files, Green Day for being awesome, all who have helped or held breath for this, and to you!
Possible problems and workarounds
There are reported cases when the wi-fi stopped working after flashing the rooted factoryfs. And there are two reported solutions:
1. Backup the contents of /system/etc/wifi before flashing to restore them after flashing if you experinece the wi-fi problem. (This is the recommended way)
2. Flash the kernel.
---------------------------------
Added:
As it turned out in the International version (YP-GI1CW) thread, the highly possible reason for this is that there are slightly different versions of the devices. The full code of my device is YP-GI1CB/XAA. If your version is not the XAA (there is, for example, YP-GI1CB/XEG), just backup the contents of your /system/etc/wifi directory before flashing, then rewrite them back if you lose wifi after rooting.
Apologies if this is a dumb question, but I'm having trouble figuring out which version to use. I bought my device in the US from a retail store, so I'm assuming it's the US version, but my model number (both under the battery and in the "About Device" section) just says "YP-GI1". The android version is 2.3.6, and kernel is 2.6.35.7-CL1. Any ideas on how to find out if this is a CB or CW device?
Thanks a ton
direwolf1 said:
Apologies if this is a dumb question, but I'm having trouble figuring out which version to use. I bought my device in the US from a retail store, so I'm assuming it's the US version, but my model number (both under the battery and in the "About Device" section) just says "YP-GI1". The android version is 2.3.6, and kernel is 2.6.35.7-CL1. Any ideas on how to find out if this is a CB or CW device?
Thanks a ton
Click to expand...
Click to collapse
I'm pretty sure that it's the US version YP-GI1CB.
There are two reported cases when the wifi stopped working after flashing the rooted factosyfs.
Please report if you have successfully flashed and rooted without problems, so we can know if those two cases were exceptions due to some still unknown reason or there is a real problem. Thank you.
I'm an idiot--found the model number and it is indeed a US device. I'd like to download this and root it, but now I'm worried about the wifi issue. Any new reports?
Root successful, everything works fine
This is the first time I have rooted using Odin. I followed the instructions on the 4.2 Int. rooting page linked in the top (this is the US version, and I did use the files on this thread). Everything works great, wifi included. I installed AdAway and removed all of the Samsung bloat. Sorry about the pic quality, my nexus 7 vga camera is all that I have near me lol.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hi, could you help me please! This is the firs time for my rooting a SGP 4.2. Can I root it using windows 7? I'm now downloading all the files attached by alice, but (here's the problem) I don't know what I should do with its.
AngelBoutto said:
Hi, could you help me please! This is the firs time for my rooting a SGP 4.2. Can I root it using windows 7? I'm now downloading all the files attached by alice, but (here's the problem) I don't know what I should do with its.
Click to expand...
Click to collapse
Follow the tutorial here (but use the ROM in this thread). It's how I did it. This was my first time using this method as well. The only file you need is the modified (aka rooted) ROM. Works great.
EDIT: NM I still had a nexus 7 tar in the same directory that I confused. Please ignore and thanks to all who got this root to work. Cant wait to we have kernels and such that support voodoo sound.
The second post (problems and solutions) has updated.
Users who have experienced the wifi problem after rooting, can you please write here you full device code (e.g. mine is YP-GI1CB/XAA) so we can know whether the problem is the existence of slightly different versions of the same device.
To find out your revision, enter in terminal getprop ril.product_code.
alice90 said:
The second post (problems and solutions) has updated.
Users who have experienced the wifi problem after rooting, can you please write here you full device code (e.g. mine is YP-GI1CB/XAA) so we can know whether the problem is the existence of slightly different versions of the same device.
To find out your revision, enter in terminal getprop ril.product_code.
Click to expand...
Click to collapse
My model is: YP-GI1CB/XEG
Think you know how I solved my wifi Problem. Kernel Flash and usb jigg
I rooted it using these instructions and it worked like a charm. Wifi is working great. Only issue I had was that my device seemed a little finicky when I was trying to get it into download mode, but I figured it out eventually. Thanks so much for this!
sedelman said:
Follow the tutorial here (but use the ROM in this thread). It's how I did it. This was my first time using this method as well. The only file you need is the modified (aka rooted) ROM. Works great.
Click to expand...
Click to collapse
I finish to install the rom rooted, but I think doesn't work for me. all in my device is the same, and and check with a rooted checker and said your device isn't rooted.
AngelBoutto said:
I finish to install the rom rooted, but I think doesn't work for me. all in my device is the same, and and check with a rooted checker and said your device isn't rooted.
Click to expand...
Click to collapse
Find the SuperSU app in the menu (it should be there if you flashed successfully) and open it, it will ask a question about replacing the su, confirm it.
Then try to install something that requires root and check whether it works.
Many thanks.
Complete success with Odin 3.04.
I was confused initially with Heimdall and mistakenly tried to load factoryfs.img as a Heimdall package which returned an error about a missing factoryfs.xml file. "factoryfs.img" is not a Heimdall package. If you want to use Heimdall simply to flash the factoryfs.img, I recommend using the command line.
heimdall flash --factoryfs factoryfs.img
No problems with WiFi after the upgrade as my device is YP-GI1CB/XAA, although I backed up my /system/etc/wifi folder just in case.
Thanks.
Finally!!! I did! But, now my problem is the RAM! in a few minutes the level of RAM is on the top! And my device start to be frozen for period of time... Could someone help me with that? Someone of you know if we can find ROM's modified?
AngelBoutto said:
Finally!!! I did! But, now my problem is the RAM! in a few minutes the level of RAM is on the top! And my device start to be frozen for period of time... Could someone help me with that? Someone of you know if we can find ROM's modified?
Click to expand...
Click to collapse
Try rebooting.I had the same problem as you then i rebooted and the problem went away.
kvn7918 said:
Try rebooting.I had the same problem as you then i rebooted and the problem went away.
Click to expand...
Click to collapse
I restart my device almost 5 times a day! The RAM runaway! When I open Skype, well in 30 second my device start to restart automatically.
i have a problem i use this rom the root rom, now my player the home button dont work any one have same problem please let me know model numbe yp-gi1
Hi all, after a great effort and lot of work finally i got cm9 compile from source working in my s7 model 105.
this is a more stable version it still has some bugs that i'm trying to solve, help is welcome.
I used kernel from jotamj from another forum and i use asturel device files to get it started, asturel files is for the slim so i had to made some changes in the files, thanks to them.
For a long time i hope for a update from huawei but notthing came, people at huawei suck, they dont give any suport to there clients, so i and other had to do it in order to have cm9 or cm10 in huawei s7.
this work on:
my s7 model=105, it may work on 104 and in 106, probably will not work on s7 slim
what works:
-wifi
-bluetooth
-audio
-gps
-google play (solve, install gaps file)
-streaming (must install flash player 11)
do not work:
-camera
-usb mount on pc
how to install:
first do a backup, IMPORTANT , backup first ( in case same thing go wrong)
copy file zip to sdcard
boot on cwm and install zip file
reboot and wait 4 to 5 minutes, if anything goes wrong restore from backup.
version 53 (more stable)
link: https://docs.google.com/file/d/0B9OIKoN0knUtSGNfVWpOSjBqNEE/edit?usp=sharing
to solve google play install gaps
link: https://docs.google.com/file/d/0B9OIKoN0knUtUTdSQUpERHhfYTg/edit?usp=sharing
help is welcome,
install on your device, test what work and what does not, google for solutions on the bugs you find, post solution here, i will aplly it to the next version, that way we can have a cm9 working 100% in very little time
in the case you can post, write a message to me.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
to do next:
-correct google play (solved)
-camera
test it
hal_2000
Huawei isn't to blame I think. I don't think there are many QSD8250 devices that made it past Gingerbread. Acer (Liquid, Liquid E) and HTC (Desire) left their devices on Froyo. Dell (Streak 5) moved up to Gingerbread.
I have given my S7 away to a family member and won't be changing the firmware, but thanks for putting this together.
That's a weird looking ro.build.fingerprint you have there. Fix in cm.mk for build. Play Store also freaks out if you have a date too far from the present.
xaueious said:
Huawei isn't to blame I think. I don't think there are many QSD8250 devices that made it past Gingerbread. Acer (Liquid, Liquid E) and HTC (Desire) left their devices on Froyo. Dell (Streak 5) moved up to Gingerbread.
I have given my S7 away to a family member and won't be changing the firmware, but thanks for putting this together.
That's a weird looking ro.build.fingerprint you have there. Fix in cm.mk for build. Play Store also freaks out if you have a date too far from the present.
Click to expand...
Click to collapse
Hi xaueious, when i bought my s7 it came with android 2.1, some time after huawei lunch android 2.2 for asia, i had to wait for a suedish user to hack it and lunch it for europe, they could lunch android 2.3 but they where not interest, that why i said huawei suck, other manufactures realeases updates for they clients, but not huawei.
the fingerprint of the build has to do with the system i came up with to test things, i started with asturel base devices files but that is for the slim, so i had to test what option worked or not, it took dozens of test and tries, to get it to work.
i got the google play problem solve, see post 1, and streaming to
I'm close to get a 100% working rom.
test it if you can, and help me solve the bugs if you find any, enjoy.
hal_2000
I installed your rom on my s7-105 but now it's not starting proper anymore. I see the word ANDROID and I can hear a small click every second but nothing more... what's wrong?
---------- Post added at 04:07 PM ---------- Previous post was at 03:53 PM ----------
After a re-boot I get the message "Update failed! Please retry!" No matter which key combination I try (vol+ & power, menue&green&power, oder vol+&vol-&power) this is all that I get!!!!!!! HELP PLEASE!!! What can I do now?????? How can I get back into CWM to reinstall a rom??????
after some try & error I found out that with the key combination back&red key & power I can make the device to boot, I see the words Ideos and later android again but that's all. It's not going on. I have no idea how I can install an older rom now....
grka said:
I installed your rom on my s7-105 but now it's not starting proper anymore. I see the word ANDROID and I can hear a small click every second but nothing more... what's wrong?
---------- Post added at 04:07 PM ---------- Previous post was at 03:53 PM ----------
After a re-boot I get the message "Update failed! Please retry!" No matter which key combination I try (vol+ & power, menue&green&power, oder vol+&vol-&power) this is all that I get!!!!!!! HELP PLEASE!!! What can I do now?????? How can I get back into CWM to reinstall a rom??????
after some try & error I found out that with the key combination back&red key & power I can make the device to boot, I see the words Ideos and later android again but that's all. It's not going on. I have no idea how I can install an older rom now....
Click to expand...
Click to collapse
Sounds like a boot loop. What ROM did you come from? You should be coming from Android 2.2, not 2.1.
Here's a list of stock firmware to use: http://johnnyparanoia.blogspot.co.uk/2012/04/huawei-s7-tablet-firmware-list.html
Install procedure for stock: http://www.androidtablets.net/forum...d-2-2-2-dual-camera-s7-s7v100r001c98b021.html
xaueious said:
Sounds like a boot loop. What ROM did you come from? You should be coming from Android 2.2, not 2.1.
Here's a list of stock firmware to use: http://johnnyparanoia.blogspot.co.uk/2012/04/huawei-s7-tablet-firmware-list.html
Install procedure for stock: http://www.androidtablets.net/forum...d-2-2-2-dual-camera-s7-s7v100r001c98b021.html
Click to expand...
Click to collapse
To be honest, I can't say it for sure which one I had. In the status menue it said "2.1 update 1" Whatever this means. I had problems to install the clockworkmod I finally found this ROM: rom tri_zet. With that I could install clockworkmod and reboot the tablet into recovery mode. Then I installed this rom here and run into the problem.
Last night I finally managed to install the official swedish ROM 2.2.2. With that my tablet is running again.
Do you think with that one I could make another try to install this rom now? How can I install the clockworkmode now? Maybe the tri_zet rom was the cause of the problem...
grka said:
To be honest, I can't say it for sure which one I had. In the status menue it said "2.1 update 1" Whatever this means. I had problems to install the clockworkmod I finally found this ROM: rom tri_zet. With that I could install clockworkmod and reboot the tablet into recovery mode. Then I installed this rom here and run into the problem.
Last night I finally managed to install the official swedish ROM 2.2.2. With that my tablet is running again.
Do you think with that one I could make another try to install this rom now? How can I install the clockworkmode now? Maybe the tri_zet rom was the cause of the problem...
Click to expand...
Click to collapse
Hi grka, i tryed tri_zet but i didnt liked so i used the swedish ROM 2.2.2 until recently.
My advice install cwm 6.0.1, backup and then when install, clear cache and data, then intall my rom it should work
If you get problems again restore from bacup.
1º install the rom, let it boot, after sucessul boot install gaps to make goople play work.
If you need more help ask.
hal_2000
hal_2000 said:
Hi grka, i tryed tri_zet but i didnt liked so i used the swedish ROM 2.2.2 until recently.
My advice install cwm 6.0.1, backup and then when install, clear cache and data, then intall my rom it should work
If you get problems again restore from bacup.
1º install the rom, let it boot, after sucessul boot install gaps to make goople play work.
If you need more help ask.
hal_2000
Click to expand...
Click to collapse
Can you please tell me where to download cwm 6.0.1 and how to install it? I spend some hours with downloading different files and trying to install them without success.
grka said:
Can you please tell me where to download cwm 6.0.1 and how to install it? I spend some hours with downloading different files and trying to install them without success.
Click to expand...
Click to collapse
Hi, follow this steps:
1-boot in fastboot, with device power down, click vol up+home+power , fastboot apears in screen
2-connect s7 to pc
3-extract the zip file
4-in a dos text console inside the dir where are the files execute: "fastboot flash recovery s7-recovery-v601.img"
5-to reboot "fastboot reboot"
to go to cwm, with device power down, menu+call (green key) + power on
this commands work in a windows xp, never tryied in win 7 or 8.
More help ask,
hal_2000
Hal2000 can you provide a fastboot flashable system.img?
Thank you i will test your Rom next week.
threader said:
Hal2000 can you provide a fastboot flashable system.img?
Click to expand...
Click to collapse
Hi threader, i didnt save the img file, so i compile one today with my 53 source files, here is the link: https://docs.google.com/file/d/0B9OIKoN0knUtSXU5Tm9XZUYzYms/edit?usp=sharing
one question. do you know how i can have (make) a system.img file in ext2 format, insted of a yaff2 ?
Hal_2000
I think there is a flag to make the userdata ext4 , but do not make it ext2! It is prone to dataloss if not unmounted properly, it is better to compile in ext3 and 4 support in to the kernel. But i believe if im not mistaken i have seen options to make ext images in the codeaurora sources
Under BoardConfig.mk, TARGET_USERIMAGES_USE_EXT4
Relevant: https://groups.google.com/forum/?fromgroups=#!topic/android-building/wdV3GIe_XC4
The update.zip should be sufficient for most users. Shouldn't need to provide fastboot images.
build/core/Makefile contains the rules to generate the boot, userdata,
and system images. The choice of file system for the two latter is
determined by the setting of the TARGET_USERIMAGES_USE_EXT[234]
variables, so to get ext4 for your system and userdata images you can
say
TARGET_USERIMAGES_USE_EXT4 := true
in e.g. BoardConfig.mk.
Click to expand...
Click to collapse
For the usb mount, I don't really know how to fix this at all, but the is the Acer Liquid similar? https://github.com/thepasto/liquidCM_devicetree/blob/master/acer/liquid/BoardConfig.mk
BOARD_USE_USB_MASS_STORAGE_SWITCH := true
TARGET_USE_CUSTOM_LUN_FILE_PATH := "/sys/devices/platform/msm_hsusb/gadget/lun"
(lun path needs to be fixed to match S7. I remember changing this when I kanged recovery)
xaueious said:
Under BoardConfig.mk, TARGET_USERIMAGES_USE_EXT4
Hi xaueious, thanks for those tips, always learning in this forum.
One question, is there a manual where i can learn about all the options of config files in cm9 or cm7 ?
hal_2000
Click to expand...
Click to collapse
hal_2000 said:
xaueious said:
Under BoardConfig.mk, TARGET_USERIMAGES_USE_EXT4
Hi xaueious, thanks for those tips, always learning in this forum.
One question, is there a manual where i can learn about all the options of config files in cm9 or cm7 ?
hal_2000
Click to expand...
Click to collapse
I'm not an expert at CM. I just worked on building one very specific platform and know where some files are... But from what I know...
For Android platform: http://elinux.org/Android_Build_System and https://android.googlesource.com/platform/build/+/master/core/build-system.html
If you modify specific packages, mm and mmm are nice tools to use. For building, make otapackage does a lot more crap than just making the target images (make bootimage, make systemimage). Enabling CCACHE is supposed to help with build speed too. Also consider stripping the unnecessary languages during development, and stuff builds a lot faster (PRODUCT_LOCALE flag), because a ton of time is spent building together strings.
Originally build options are mostly in /build/. CM has some new options in there, but I am not sure if they add new ones elsewhere. Other things to pay attention to are the .prop options that CM has added. Those things are littered all over and don't have documentation, but at least git commits are easy to follow.
Click to expand...
Click to collapse
Hi, thank you,
Just in case someone else as same question, TARGET_USERIMAGES_USE_EXT4 in cm9 only acepts ext4 no ext2 or ext3, i tryied all tree options.
Great tips, as always thank for taking the time to anser my questions.
hal_2000
Just installed on my S7 107 Australian version. Excellent work hal_2000. I think after install your rom , i hear some times a crackling sound.
Waiting for a fix for camera
kosmasgr said:
Just installed on my S7 107 Australian version. Excellent work hal_2000. I think after install your rom , i hear some times a crackling sound.
Waiting for a fix for camera
Click to expand...
Click to collapse
Hi, kosmasgr, the audio same times gives a click, is a little bug, the device source i used is from asturel and his files are for the slim version, i'm trying to fix the camera its more critical then the audio bug.
enjoy cm9.
hal_2000
The click is a problem from kernel that Huawei provided for 2.2.2. Kernel source is generic for both version fat and slim.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Team Win Recovery Project (TWRP) is an open-source software custom recovery image for Android-based devices. It provides a touchscreen-enabled interface that allows users to install third-party firmware and back up the current system, functions often unsupported by stock recovery images. It is, therefore, often installed when rooting Android devices, although it isn't dependent on a device being rooted to be installed.
Notes for themers: In addition to the udpated theme, we have introduced a theme version variable to the TWRP theme system. If the theme version does not match the version that TWRP expects, TWRP will reject the custom theme and load its stock theme. This change will ensure that people who update TWRP without updating their theme will still have a workable recovery. We have removed libjpeg support. The stock theme was only using a jpeg image for the splash / curtain. This change means that any custom themes will no longer be able to use jpeg images. It also means that tools used to repack recovery images with a different curtain / splash will need to be updated to use the new method.
Version number notes: For a while we’ve been using a 4 digit version number and reserved the 4th digit for device-specific updates. For instance, we find and fix a device-specific issue like decryption of data on Nexus 5, we would release that as a 2.8.7.1. After a while, some people would start asking where 2.8.7.1 was for other devices. So, going forward we have decided to change the numbering scheme to 3.0.0-2, etc. Our hope is that this version numbering scheme will more clearly identify that the 4th digit does not indicate a version change for the code base.
We need your help! The bulk of TWRP work is done by 3 people on a volunteer basis. We have pushed most of our device files to our github and we have a gerrit instance. If you have the ability, please help us maintain our official devices and/or add your device to our official device list. Thanks in advance!
DOWNLOAD:
Note this is a very early build. Feel free to report bugs.
twrp*.img (DO NOT FLASH OR TRY TO BOOT THIS, SOFT BRICK CAN OCCUR)
Fastboot Flashing Code (Boot only, not flash!)
Code:
[CENTER]fastboot boot twrp*.img[/CENTER]
BUGS:
/EVERYTHING > IT NOT EVEN BOOTS AND MIGHT SOFT BRICK YOUR PHONE
If you have found a bug, please consider posting it to our github issues log. It's pretty much impossible for us to keep up with the more than 40 threads that we have for the devices that we "directly" support. If you have a significant problem that cannot be answered in this thread, your best bet is to PM me directly, contact us via our website, or find us in our IRC channel below. If you see someone that's struggling, feel free to point it out to us. We need your help to help us keep track of all of our devices! Thanks!
SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
Kernel source: Prebuilt stock kernel
RESERVED
The command is wrong, it should be:
fastboot boot recovery twrp*.img
Haven't tried it yet as I'm already rooted but may soon.
Dahenjo said:
The command is wrong, it should be:
fastboot boot recovery twrp*.img
Haven't tried it yet as I'm already rooted but may soon.
Click to expand...
Click to collapse
No, I haven't wrote it wrong.
You mean "fastboot flash recovery twrp*.img".
But like I wrote, we will for now just boot it
Our device got treble (A/B) so our recovery is intergrated into the kernel, which means that if you'll flash it you will not be able to boot anymore.
I'd like to hear from somebody if it works, I can't test it as I not yet unlocked the bootloader.
jeffreyvh said:
No, I haven't wrote it wrong.
You mean "fastboot flash recovery twrp*.img".
But like I wrote, we will for now just boot it
Our device got treble (A/B) so our recovery is intergrated into the kernel, which means that if you'll flash it you will not be able to boot anymore.
I'd like to hear from somebody if it works, I can't test it as I not yet unlocked the bootloader.
Click to expand...
Click to collapse
Sorry, I thought it needed 'recovery' in the command either to boot twrp or to flash it.
So when we have an official working TWRP what command will we use to install it?
Maybe some other brave soul will give it a try.
No it doesnt.
And booting TWRP is safe, as it won't install anything to you're phone! It is only temporary, as you boot it.
The Moto Z3 Play (almost the same specs) also use this method. You can take a look at their forum
Ok, thanks.
jeffreyvh said:
No it doesnt.
And booting TWRP is safe, as it won't install anything to you're phone! It is only temporary, as you boot it.
The Moto Z3 Play (almost the same specs) also use this method. You can take a look at their forum
Click to expand...
Click to collapse
Hi, thanks for bringing it up. I have tried to boot the TWRP but it does not work. It simply reboots to system.
Is there anything more I should do beside rebooting to bootloader and executing command?
washoq said:
Hi, thanks for bringing it up. I have tried to boot the TWRP but it does not work. It simply reboots to system.
Is there anything more I should do beside rebooting to bootloader and executing command?
Click to expand...
Click to collapse
As far as I know you shouldn't do more then this, I'll probably just unlock my bootloader
Ah and can you write me the exact command which you have been using?
Thanks for testing!
jeffreyvh said:
As far as I know you shouldn't do more then this, I'll probably just unlock my bootloader
Ah and can you write me the exact command which you have been using?
Thanks for testing!
Click to expand...
Click to collapse
Yeah, sure, this are commands I have used:
Code:
adb devices
adb reboot bootloader
fastboot devices
fastboot boot twrp-3.2.3-1-lake.img
Image file was in adb folder.
One more thing. After I've tried above I couldn't boot to system normally (it always booted to stock recovery). Only executing 'fastboot boot recovery twrp-3.2.3-1-lake.img' booted to system.
So I thought it is common problem when you need to use 'fastboot continue' to go to system but after using this command I was not able to boot system at all, even boot recovery command
was not working (it gave me an error). Eventually I was forced to do factory reset from stock recovery and it did the trick, system booted normally. So unfortunately I must say it is not safe to even boot this recovery.
However I am willing to help/test as long as I am able to recover using factory reset.
jeffreyvh said:
And booting TWRP is safe, as it won't install anything to you're phone! It is only temporary, as you boot it.
Click to expand...
Click to collapse
I tried this too last night (using command: 'fastboot boot twrp-3.2.3-1-lake.img') with same result requiring a factory reset, it boots to system then on next reboot got the "Can't Load Android System" error repeatedly with the only apparent option to do a factory reset which wipes everything.
However, I just saw in OP of this G6+ thread that flashing the gpt.bin from the firmware may fix partition table corruption likely causing that, so will try that first next time before doing a factory reset. Command is: 'fastboot flash gpt.bin'.
I suggest you take down the link until either you can unlock & test or one of us willing guinea pigs can, but I don't think posting it publicly totally untested was a good idea. You could PM myself, Washoq, or others who volunteer here with a private link, then when it's safely functional enough for a few of us then it post again publicly for fine-tuning. Appreciate your efforts but let's try to proceed more cautiously.
washoq said:
Yeah, sure, this are commands I have used:
Code:
adb devices
adb reboot bootloader
fastboot devices
fastboot boot recovery twrp-3.2.3-1-lake.img
Image file was in adb folder.
One more thing. After I've tried above I couldn't boot to system normally (it always booted to stock recovery). Only executing 'fastboot boot recovery twrp-3.2.3-1-lake.img' booted to system.
So I thought it is common problem when you need to use 'fastboot continue' to go to system but after using this command I was not able to boot system at all, even boot recovery command
was not working (it gave me an error). Eventually I was forced to do factory reset from stock recovery and it did the trick, system booted normally. So unfortunately I must say it is not safe to even boot this recovery.
However I am willing to help/test as long as I am able to recover using factory reset.
Click to expand...
Click to collapse
Hey, I see the problem. Like I already thought....
In my post is "fastboot boot twrp-3.2.3-1-lake.img" not include recovery!
Try this command and let me know, sorry if it sounds rude. But I told it was safe with my command, and you didn't use my command.
Thank you very much for testing, I really appreciate that!
Dahenjo said:
I tried this too last night (using command: 'fastboot boot twrp-3.2.3-1-lake.img') with same result requiring a factory reset, it boots to system then on next reboot got the "Can't Load Android System" error repeatedly with the only apparent option to do a factory reset which wipes everything.
However, I just saw in OP of this G6+ thread that flashing the gpt.bin from the firmware may fix partition table corruption likely causing that, so will try that first next time before doing a factory reset. Command is: 'fastboot flash gpt.bin'.
I suggest you take down the link until either you can unlock & test or one of us willing guinea pigs can, but I don't think posting it publicly totally untested was a good idea. You could PM myself, Washoq, or others who volunteer here with a private link, then when it's safely functional enough for a few of us then it post again publicly for fine-tuning. Appreciate your efforts but let's try to proceed more cautiously.
Click to expand...
Click to collapse
I edited the OP and putted there clear warnings
I leave the download link there yet for people who might wanna help me
jeffreyvh said:
Hey, I see the problem. Like I already thought....
In my post is "fastboot boot twrp-3.2.3-1-lake.img" not include recovery!
Try this command and let me know, sorry if it sounds rude. But I told it was safe with my command, and you didn't use my command.
Thank you very much for testing, I really appreciate that!
Click to expand...
Click to collapse
Not rude at all, no problem. It is actually my mistake. I wrote from my memory. I used command without 'recovery' as I copied it from your post.
Sorry for this. confusion. I will correct my post. So basically we are at the same place. Dahenjo confirmed that it does work like I described.
Still I am willing to test when you deliver new version with some fixes. Good luck
I also tried to boot the TWRP image, but nothing happened except a reboot of the g7 Plus to the system. Did I do something wrong?
Code:
C:\adb>adb devices
List of devices attached
ZY225CQ6T7 device
C:\adb>adb reboot bootloader
C:\adb>fastboot devices
ZY225CQ6T7 fastboot
C:\adb>fastboot boot twrp-3.2.3-1-lake.img
downloading 'boot.img'...
OKAY [ 0.880s]
booting...
OKAY [ 5.188s]
finished. total time: 6.068s
I would like to install Magisk. Is it possible to do this in a different way?
jeffreyvh said:
I edited the OP and putted there clear warnings
I leave the download link there yet for people who might wanna help me
Click to expand...
Click to collapse
So I got Moto to finally release kernel source. Where you have your device tree for lake? I got the kernel just about ready, but am curious what you used for device tree before I start my own.
Long story short, I'm trying to get TWRP working and bootable for you guys (I am picking up the device in the coming weeks). But I'd like to get things going for you guys in the meantime. I currently own Beckham and Evert (both very similar devices) so I know a little about these devices.
Jleeblanch said:
So I got Moto to finally release kernel source. Where you have your device tree for lake? I got the kernel just about ready, but am curious what you used for device tree before I start my own.
Long story short, I'm trying to get TWRP working and bootable for you guys (I am picking up the device in the coming weeks). But I'd like to get things going for you guys in the meantime. I currently own Beckham and Evert (both very similar devices) so I know a little about these devices.
Click to expand...
Click to collapse
Thanks for working on this, Joshua. OP hasn't said how they produced it, but it was untested causing a soft brick/factory reset for a few of us who tried it with the proper command line syntax for booting.
I was experimenting but am not a dev, began a porting guide but it didn't cover differences on newer A/B phones with recovery integrated into the boot.img so I couldn't follow it. However, along the way I tried booting both G6+ (evert) and Z3 Play (beckham) official TWRPs, which didn't work, just ended up back at bootloader, but didn't cause any further problems from simply booting.
I'll be glad to test if/when something is ready, and thanks again for helping us out. I already have root using this procedure without TWRP, but it'd be nice to do nandroids and I assume/hope we'll see some ROMs someday, perhaps RR for Lake.
Dahenjo said:
Thanks for working on this, Joshua. OP hasn't said how they produced it, but it was untested causing a soft brick/factory reset for a few of us who tried it with the proper command line syntax for booting.
I was experimenting but am not a dev, began a porting guide but it didn't cover differences on newer A/B phones with recovery integrated into the boot.img so I couldn't follow it. However, along the way I tried booting both G6+ (evert) and Z3 Play (beckham) official TWRPs, which didn't work, just ended up back at bootloader, but didn't cause any further problems from simply booting.
I'll be glad to test if/when something is ready, and thanks again for helping us out. I already have root using this procedure without TWRP, but it'd be nice to do nandroids and I assume/hope we'll see some ROMs someday, perhaps RR for Lake.
Click to expand...
Click to collapse
From what I hear it's just a ported version, which is fine. I'll finish putting together a device tree in the coming days and the kernel and should have a build for testing soon. I'll link it here when I got a build for testing so we can get a bootable build going.
Jleeblanch said:
From what I hear it's just a ported version, which is fine. I'll finish putting together a device tree in the coming days and the kernel and should have a build for testing soon. I'll link it here when I got a build for testing so we can get a bootable build going.
Click to expand...
Click to collapse
Thanks for your work. I am also willing to test when you have possibly working build.
Jleeblanch said:
From what I hear it's just a ported version, which is fine. I'll finish putting together a device tree in the coming days and the kernel and should have a build for testing soon. I'll link it here when I got a build for testing so we can get a bootable build going.
Click to expand...
Click to collapse
Hi, my build wasn't ported. I used the zImage from the stock kernel which I extracted. The device tree I made was based of the Z3 Play device tree. I probably know why it was causing this issue. It has something to do with encryption, when I'll have my new Linux Machine set up I'll take a look at this. And also this time I will be downloading the full omni source, instead of the minimal one required to build only TWRP. It could be the case that this is causing issues as well.
Nice to see some more devs coming over to this device. It's a pretty decent phone, the only downside for me is the battery but I'm glad we've got this rapidly fast 28W fast charging.
Anyways, when I'll have my Linux environment set up. I'll upload the device tree to GitHub including the extracted kernel image I've used.
[ROOT][UNLOCKED] Wiko Ride - bootloader unlocked, mtk-su'able, & $35 at wally world
Just found this phone on the list of mtk-su'able devices and grabbed one, and to my surprise the bootloader is unlocked as well. Comes with Pie. I haven't been able to build a TWRP that runs on it, but I just dd'ed the boot partition and patched it offline with Magisk and dd'ed it back. It's only a 2GB/16GB phone but worth the price to have a real rooted phone again vs having to deal with temproots.
rlrevell said:
Just found this phone on the list of mtk-su'able devices and grabbed one, and to my surprise the bootloader is unlocked as well. Comes with Pie. I haven't been able to build a TWRP that runs on it, but I just dd'ed the boot partition and patched it offline with Magisk and dd'ed it back. It's only a 2GB/16GB phone but worth the price to have a real rooted phone again vs having to deal with temproots.
Click to expand...
Click to collapse
I was just thinking about picking one of these up today! They have them in stock at a local walmart. I found an article on getandroidtips that links to a GSI ROM.
Do you think the GSI ROM will actually work on the Wiko Ride without TWRP? Do you just flash the zip using the stock recovery?
columbustalley said:
I was just thinking about picking one of these up today! They have them in stock at a local walmart. I found an article on getandroidtips that links to a GSI ROM.
Do you think the GSI ROM will actually work on the Wiko Ride without TWRP? Do you just flash the zip using the stock recovery?
Click to expand...
Click to collapse
Yeah, I've since given the phone away but IIRC you don't even need the mtk-su, you just unlock the bootloader and flash whatever you want. I flashed with fastboot, not having a working TWRP. @tecknight managed to build a TWRP that almost worked before I kinda lost interest. You do have to sign the images using the AVB process, but IIRC it doesn't care who signed them, just that they're signed. I can look through my notes for more details. You'll definitely learn a lot about how AVB works if nothing else, and the phone seems very hard to accidentally brick.
I *think* I have dd dumps of every partition from before I changed anything saved somewhere.
rlrevell said:
Yeah, I've since given the phone away but IIRC you don't even need the mtk-su, you just unlock the bootloader and flash whatever you want. I flashed with fastboot, not having a working TWRP. @tecknight managed to build a TWRP that almost worked before I kinda lost interest. You do have to sign the images using the AVB process, but IIRC it doesn't care who signed them, just that they're signed. I can look through my notes for more details. You'll definitely learn a lot about how AVB works if nothing else, and the phone seems very hard to accidentally brick.
I *think* I have dd dumps of every partition from before I changed anything saved somewhere.
Click to expand...
Click to collapse
That's great! So I just grab the zip for the GSI ROM... sign it with AVB... then I can flash it with fastboot? I think I'll pick one up tomorrow and give it a go. I'll backup all my partitions before I do anything. If I get stuck I'll let you know thanks for the great info!
I got it working! Got root using the mtk-su then backed up all the partitions using a script on github. Enabled bootloader unlock in settings then from PC did fastboot flashing unlock. Flashed the vbmeta.img using fastboot to disable AVB checks. Wiped system then flashed the arm64 Android 10 GSI a/b ROM to system using fastboot. Everything working as expected so far!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
back up all partitions with script on github
columbustalley said:
I got it working! Got root using the mtk-su then backed up all the partitions using a script on github.
Click to expand...
Click to collapse
which github script is that ? I am trying to do the same thing ! :highfive:
s4goa said:
which github script is that ? I am trying to do the same thing ! :highfive:
Click to expand...
Click to collapse
I used the project called dump-android-partitions. It worked in Cygwin on Windows 10 for me. It requires root on your device as well.
partn BAK sh script
columbustalley said:
It requires root on your device as well.
Click to expand...
Click to collapse
https://codeload.github.com/for2ando/dump-android-partitions/zip/master
looks like a good option for
adb shell
columbustalley said:
I got it working! Got root using the mtk-su then backed up all the partitions using a script on github. Enabled bootloader unlock in settings then from PC did fastboot flashing unlock. Flashed the vbmeta.img using fastboot to disable AVB checks. Wiped system then flashed the arm64 Android 10 GSI a/b ROM to system using fastboot. Everything working as expected so far!
Click to expand...
Click to collapse
So I also got lineage 17.1 up and running pretty well. Did you have any luck getting open gapps installed? No amount of searching produced a twrp for Wiko ride and I even started down the rabbit hole of maybe making my own twrp device tree and compiling from source but then I noticed the android 10 branch of twrp is still wip so that sounds like a bad idea. Maybe manual install through adb and temp root?
aroganone said:
So I also got lineage 17.1 up and running pretty well. Did you have any luck getting open gapps installed? No amount of searching produced a twrp for Wiko ride and I even started down the rabbit hole of maybe making my own twrp device tree and compiling from source but then I noticed the android 10 branch of twrp is still wip so that sounds like a bad idea. Maybe manual install through adb and temp root?
Click to expand...
Click to collapse
I actually use this phone without any google play services. I use F-Droid and Aurora for managing apps. Sorry about that mate!
There might be an easy solution though. If you use a GSI ROM that comes with gapps pre-installed everything should work fine in theory right?
Search google for this image and give it a try. It's the gapps version of the ROM that I currently use.
Havoc-OS-v3.7-20200709-Official-GApps-a64-ab.img.xz
This is absolutely incredible! Normally Pie Bootloader's are locked (as well as Android 8+). To see this is absolutely amazing! If anyone needs custom tools made I can provide a link as well as the source code to build the tools
TheExploitedOne said:
This is absolutely incredible! Normally Pie Bootloader's are licked (as well as Android 8+). To see this is absolutely amazing! If anyone needs custom tools made I can provide a link as well as the source code to build the tools
Click to expand...
Click to collapse
It is pretty great to see an "unlicked" ; ) bootloader on such a cheap device. Unfortunately they are now out of stock in all of the stores in my area and I don't see it listed on the Walmart website anymore. Hopefully they ship another batch!
Thanks for all the info. I’ll definitely check out havoc. I’m completely new to android and the custom rom scene so this has been a great learning experience. So far it’s a fantastic little retroarch emulation device for the money.
aroganone said:
Thanks for all the info. I’ll definitely check out havoc. I’m completely new to android and the custom rom scene so this has been a great learning experience. So far it’s a fantastic little retroarch emulation device for the money.
Click to expand...
Click to collapse
You'll absolutely love the journey too I started at a young age (14 and I'm 22 now) in the hacking scene. It's been absolutely incredible with what I've learned about Android as well as getting to build a custom rim from the sources with my own modifications
---------- Post added at 08:32 PM ---------- Previous post was at 08:32 PM ----------
columbustalley said:
It is pretty great to see an "unlicked" ; ) bootloader on such a cheap device. Unfortunately they are now out of stock in all of the stores in my area and I don't see it listed on the Walmart website anymore. Hopefully they ship another batch!
Click to expand...
Click to collapse
I meant locked lol
Try checking out Amazon they usually have them
columbustalley said:
I actually use this phone without any google play services. I use F-Droid and Aurora for managing apps. Sorry about that mate!
There might be an easy solution though. If you use a GSI ROM that comes with gapps pre-installed everything should work fine in theory right?
Search google for this image and give it a try. It's the gapps version of the ROM that I currently use.
Havoc-OS-v3.7-20200709-Official-GApps-a64-ab.img.xz
Click to expand...
Click to collapse
So I ended up trying (arm64 boots, a64 doesn't):
Havoc-OS-v3.7-20200709-Official-GApps-arm64-ab.img.xz
I get all the way to the every end of setting up all the google account and setting and it hangs on: All Set. "Swipe up to get started". Eventually it just goes to sleep.
Rebooting it loads for a while and then hangs on the havoc logo. Any ideas or any other images with gapps cooked in that I can try? I've wiped data and cache.
Some screen shots:
aroganone said:
So I ended up trying (arm64 boots, a64 doesn't):
Havoc-OS-v3.7-20200709-Official-GApps-arm64-ab.img.xz
I get all the way to the every end of setting up all the google account and setting and it hangs on: All Set. "Swipe up to get started". Eventually it just goes to sleep.
Rebooting it loads for a while and then hangs on the havoc logo. Any ideas or any other images with gapps cooked in that I can try? I've wiped data and cache.
Some screen shots:
Click to expand...
Click to collapse
I've actually had a similar issue but I assumed it was because of some mistake I made during the process. I got a second Wiko Ride on Ebay and ran through the steps again and discovered that you need to do a full wipe with the SP Flash Tool. Be very careful though because you could lose your MEID and MAC. Make sure to back up all partitions before using the "Format all + download" function. After I did the full format with SP Flash Tool I restored the nvram and nvdata partitions from my backup. You need to edit an XML to accomplish this there are guides on Youtube. Here are some other notes that I made during the process mind you it's not comprehensive as it doesn't even have the SP Flash Tools steps but it may help you.
Unlock bootloader in developer options
Boot into fastboot
#fastboot flashing unlock
Install mtk-easy-su and magisk
#adb install mtk-easy-su.apk
#adb install magisk.apk
Set magisk to "auto"
Backup nvram and nvdata partitions using cygwin and dump-android-partitions.sh
#./dump-android-partitions.sh -s SERIALNUMBER nvram
#./dump-android-partitions.sh -s SERIALNUMBER nvdata
Unlock SIM using Miracle Thunder
Boot into fastboot
#fastboot --disable-verification flash vbmeta vbmeta.img
#fastboot erase system
#fastboot flash system .\Havoc-OS-v3.7-20200709-Official-arm64-ab.img
#fastboot -w
#fastboot reboot
0
columbustalley said:
I've actually had a similar issue but I assumed it was because of some mistake I made during the process. I got a second Wiko Ride on Ebay and ran through the steps again and discovered that you need to do a full wipe with the SP Flash Tool. Be very careful though because you could lose your MEID and MAC. Make sure to back up all partitions before using the "Format all + download" function. After I did the full format with SP Flash Tool I restored the nvram and nvdata partitions from my backup. You need to edit an XML to accomplish this there are guides on Youtube. Here are some other notes that I made during the process mind you it's not comprehensive as it doesn't even have the SP Flash Tools steps but it may help you.
Unlock bootloader in developer options
Boot into fastboot
#fastboot flashing unlock
Install mtk-easy-su and magisk
#adb install mtk-easy-su.apk
#adb install magisk.apk
Set magisk to "auto"
Backup nvram and nvdata partitions using cygwin and dump-android-partitions.sh
#./dump-android-partitions.sh -s SERIALNUMBER nvram
#./dump-android-partitions.sh -s SERIALNUMBER nvdata
Unlock SIM using Miracle Thunder
Boot into fastboot
#fastboot --disable-verification flash vbmeta vbmeta.img
#fastboot erase system
#fastboot flash system .\Havoc-OS-v3.7-20200709-Official-arm64-ab.img
#fastboot -w
#fastboot reboot
Click to expand...
Click to collapse
So I need a nudge in the right direction. Where do I get/extract/create the scatter file? I've backed up every partition manually but I'm a bit stuck on the part where you need to load the scatter file for SP Flash Tool.
aroganone said:
So I need a nudge in the right direction. Where do I get/extract/create the scatter file? I've backed up every partition manually but I'm a bit stuck on the part where you need to load the scatter file for SP Flash Tool.
Click to expand...
Click to collapse
If you've got the MT65xx use MTK Droid Tools
TheExploitedOne said:
If you've got the MT65xx use MTK Droid Tools
Click to expand...
Click to collapse
tried it but MTK Droid Tools apparently doesn't support newer chips. It pulled the following data but didn't generate the block data.
Hardware : MT6761V/CAB
Model : W-U300
Build number : treble_arm64_bvN-userdebug 10 QQ3A.200705.002 eng.crossg.20200713.132209 test-keys
Build date UTC : 20200713-132131
Android v : 10
Baseband v: MOLY.LR12A.R3.MP.V31.3.P39
Kernel v : 4.9.117+ ([email protected]) (Android (4691093 based on r316199) clang version 6.0.2 (https://android.googlesource.com/toolchain/clang 183abd29fc496f55536e7d904e0abae47888fc7f) (https://android.googlesource.com/toolchain/llvm 34361f192e41ed6e4e8f9aca80a4ea7e9856f327) (based on LLVM 6.0.2svn)) #2 SMP Fri Nov 1 14:21:38 CST 2019
I found stock firmware with the scatter file here but not sure how much I trust it:
https://romprovider.com/wiko-u300-firmware/
I also was looking at a newer tool : Wwr MTK
but haven't tried it yet.
I know it's an old phone. The LG G5. But I bought it because my Galaxy died, the G5 was cheap, you can run Lineage OS on it! But wait! No you can't! You'll never make it past loading the custom recovery file. The guide on Lineage's website is worthless, as it's from before 8.0 Oreo. LG patched the that hole closed tighter than a... a.. <insert good simile here>. I have tried every way in the world to get into this phone. I've looked at every thread here. Dirtycow doesn't work. You can't revert back to 7.x Nougat anymore. It can't be done. LG won't let you in.
I have dreamed of escaping google's clutches. It's really important to me. But I can't afford to buy some $250+ dollar phone that may or may not have a working exploit right now.
This time I gambled and lost, so I'm asking for help. Does anyone know of any way I might salvage the situation? I'd be open to buying a phone with Lineage already on it, if it were reasonably priced. I'd also be open to paying someone else to install it on this LG G5, but I have serious doubts you'd be able to. Any help or advice to get Lineage would be greatly appreciated!
bennylava said:
I know it's an old phone. The LG G5. But I bought it because my Galaxy died, the G5 was cheap, you can run Lineage OS on it! But wait! No you can't! You'll never make it past loading the custom recovery file. The guide on Lineage's website is worthless, as it's from before 8.0 Oreo. LG patched the that hole closed tighter than a... a.. <insert good simile here>. I have tried every way in the world to get into this phone. I've looked at every thread here. Dirtycow doesn't work. You can't revert back to 7.x Nougat anymore. It can't be done. LG won't let you in.
I have dreamed of escaping google's clutches. It's really important to me. But I can't afford to buy some $250+ dollar phone that may or may not have a working exploit right now.
This time I gambled and lost, so I'm asking for help. Does anyone know of any way I might salvage the situation? I'd be open to buying a phone with Lineage already on it, if it were reasonably priced. I'd also be open to paying someone else to install it on this LG G5, but I have serious doubts you'd be able to. Any help or advice to get Lineage would be greatly appreciated!
Click to expand...
Click to collapse
Hey, easy man. There's some things you should consider before giving up on a phone. The quick search i did on Google let me know that this device can be bootloader unlocked, and rooted. At this point, I may ask: Is your device linked in someway with Verizon? Did you unlocked its bootloader? did you manage to install TWRP with no issues? Maybe you´re lucky enough to find a way out yourself. I'll try to help you in everything i can.
eduardvi995 said:
Hey, easy man. There's some things you should consider before giving up on a phone. The quick search i did on Google let me know that this device can be bootloader unlocked, and rooted. At this point, I may ask: Is your device linked in someway with Verizon? Did you unlocked its bootloader? did you manage to install TWRP with no issues? Maybe you´re lucky enough to find a way out yourself. I'll try to help you in everything i can.
Click to expand...
Click to collapse
Thanks! I could really use the help. I have unlocked the bootloader. Made it that far. But I haven't been able to root it because all the root exploits seem to have been patched out by the time I got the phone. It's running Android 8.0. It is a U.S Tmobile phone.
Here's where my progress ground to a halt: I can't get that LG program, LGup, to flash 7.0 to the phone. It gives me an error saying "Error - Invalid KDZ file". Well that's odd, I got that KDZ file from LG's official website. They have a section where they keep all the old stock ROMs.
Maybe I'm wrong here, but I think this part is absolutely necessary. You must install 7.0 Nougat in order to roll back the changes LG made when they patched up the recovery mode. Otherwise you can't install a custom recovery file, which is vital. No custom recovery file = no Lineage. Looking forward to your reply !
bennylava said:
Thanks! I could really use the help. I have unlocked the bootloader. Made it that far. But I haven't been able to root it because all the root exploits seem to have been patched out by the time I got the phone. It's running Android 8.0. It is a U.S Tmobile phone.
Here's where my progress ground to a halt: I can't that LG program, LGup, to flash 7.0 to the phone. It give me an error saying "Error - Invalid KDZ file". Well that's odd, I got that KDZ file from LG's official website. They have a section where they keep all the old stock ROMs.
Maybe I'm wrong here, but I think this part is absolutely necessary. You must install 7.0 Nougat in order to roll back the changes LG made when they patched up the recovery mode. Otherwise you can't install a custom recovery file, which is vital. No custom recovery file = no Lineage. Looking forward to your reply !
Click to expand...
Click to collapse
Here is what i found out. Considering your device is LG G5 H830, with android 8.0, it seems you cant install TWRP straight on. However, there is still something you can try. At this point I may ask: can you enter Fastboot Mode? this your only hope to actually root the phone, and then flash TWRP.
Check if you actually can enter fastboot. If you can, then try to send some basic commands like "fastboot devices" "fastboot reboot". I say this because some devices have Fastboot mode disabled on oem, rendering on useless fastboot. Hope this is not your case. Also, post here your exactly fingerprint version (your rom version). It has to be exactly the same one, otherwise it might soft-brick your phone. Maybe you can flash a patched boot image of your actual rom to then flash twrp.
eduardvi995 said:
Here is what i found out. Considering your device is LG G5 H830, with android 8.0, it seems you cant install TWRP straight on. However, there is still something you can try. At this point I may ask: can you enter Fastboot Mode? this your only hope to actually root the phone, and then flash TWRP.
Check if you actually can enter fastboot. If you can, then try to send some basic commands like "fastboot devices" "fastboot reboot". I say this because some devices have Fastboot mode disabled on oem, rendering on useless fastboot. Hope this is not your case. Also, post here your exactly fingerprint version (your rom version). It has to be exactly the same one, otherwise it might soft-brick your phone. Maybe you can flash a patched boot image of your actual rom to then flash twrp.
Click to expand...
Click to collapse
I can indeed send "fastboot devices" and "fastboot reboot", and it does work. The device will be listed in the command window on the computer, and the phone will reboot if you enter the command "Fastboot reboot".
As for the fingerprint version, here's what I was able to accomplish via a terminal in Manjaro Linux. Is this the full fingerprint?
[[email protected] ~]$ adb devices
List of devices attached
LGH8305d6bec71 device
[[email protected] ~]$ adb shell getprop ro.build.fingerprint
lge/h1_tmo_us/h1:8.0.0/OPR1.170623.032/182251913485f:user/release-keys
[[email protected] ~]$
bennylava said:
I can indeed send "fastboot devices" and "fastboot reboot", and it does work. The device will be listed in the command window on the computer, and the phone will reboot if you enter the command "Fastboot reboot".
As for the fingerprint version, here's what I was able to accomplish via a terminal in Manjaro Linux. Is this the full fingerprint?
[[email protected] ~]$ adb devices
List of devices attached
LGH8305d6bec71 device
[[email protected] ~]$ adb shell getprop ro.build.fingerprint
lge/h1_tmo_us/h1:8.0.0/OPR1.170623.032/182251913485f:user/release-keys
[[email protected] ~]$
Click to expand...
Click to collapse
Its seems you were lucky enough. I checked your rom build and compared it with the only rom on your phone that can be rolled back. It totally matchs the anti-rollback v01 firmware 8.0, so you still can roll-back to Nougat if you try the firmware version H83020c, wich you can download over here:
Fastboot-Flashable rom:
Codefire - Listing of H83020c
KDZ Format rom:
http://dl02.gdms.lge.com:5006/dn/downloader.dev?fileKey=FWAAZHZF92MNARE76685PNJ/H83020o_00_0205.kdz
Its seems the first one it's Fastboot-Flashable, so you should know what to do next if the KDZ Rom doesn't work. However, check this website and compare the rom build yourself, just to be clear about it:
Download T-mobile LG G5 H830 Stock kdz firmware H83030C
Download T-mobile LG G5 H830 Stock kdz firmware H83030C -
www.mylgphones.com
The first link has 3 flashable roms there. including KDZ and fastboot format. Make sure to try them all if one doesnt work
If both methods are useless to roll back to Nougat, dont hesitate to tell me. There's still a workaround available.
To be clear, the phone needs to be in "Firmware update" mode in order to use flashboot to flash that Fastboot rom, correct? That's where a "Firmware update" message appears on the screen, and it's encircled by two arrows. It's in the middle of the screen, and it's not small like when you're using fastboot.
I ask because iirc, KDZ files require the use of LGup, that LG official program.
bennylava said:
To be clear, the phone needs to be in "Firmware update" mode in order to use flashboot to flash that Fastboot rom, correct? That's where a "Firmware update" message appears on the screen, and it's encircled by two arrows. It's in the middle of the screen, and it's not small like when you're using fastboot.
I ask because iirc, KDZ files require the use of LGup, that LG official program.
Click to expand...
Click to collapse
It needs to be in firmware update mode only if you are flashing a kdz rom through Lg official flashtool. If you are going to flash through fastboot, you have to make sure your PC recognizes your device sending "fastboot devices". The fastboot flashable room is right in the first link (.zip file, 1,6 GB size file)
The one I'm seeing says it's 1.9 Gigabytes in size. It's #15 on that list, and it's called:
LG-H83020c-Flashable.COMPLETE-ARB01.zip
Correct?
Just wanna be clear on this, the last thing we need is a brick lol
bennylava said:
The one I'm seeing says it's 1.9 Gigabytes in size. It's #15 on that list, and it's called:
LG-H83020c-Flashable.COMPLETE-ARB01.zip
Correct?
Just wanna be clear on this, the last thing we need is a brick lol
Click to expand...
Click to collapse
That should be it. Download it and check it has all partitions (boot, system, recovery, etc...)
You are probably gonna have to flash each partition manually (for example, if you are flashing system, you should write "fastboot flash system system.img" and so on)
Below is a pic of everything that came in that zip file, just to make sure we're on the same page and I've got everything necessary.
I must admit that I'm a little intimidated by flashing each individual component in that zip file. I understand that you can just tell it "Flash this thing!" and it will do it. But how does it know where exactly to flash the new thing? How does it know not to just write it over the previous item you just flashed?
Next question: What all needs to be flashed individually? As you can see, there are a total of 28 entries shown in the pic. But the folders "bootloader" and "META.INF" both contain a lot of stuff. Do you just flash bootloader and META.INF, and it already knows to flash everything the folder contains?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
bennylava said:
Below is a pic of everything that came in that zip file, just to make sure we're on the same page and I've got everything necessary.
I must admit that I'm a little intimidated by flashing each individual component in that zip file. I understand that you can just tell it "Flash this thing!" and it will do it. But how does it know where exactly to flash the new thing? How does it know not to just write it over the previous item you just flashed?
Next question: What all needs to be flashed individually? As you can see, there are a total of 28 entries shown in the pic. But the folders "bootloader" and "META.INF" both contain a lot of stuff. Do you just flash bootloader and META.INF, and it already knows to flash everything the folder contains?
Click to expand...
Click to collapse
You don't have to write "fastboot flash" 28 times. You can just write "fastboot flash all". But I'd rather flashing manually.
Ignore the META-INF folder. You can't flash any file inside there. You should only flash every file ending in "xx. Img* such as boot.img or. system.img.
This zip contains that folder because it was meant to be flashed through recovery, but if you try to do that, the recovery will not do it, or it will cancel installation, as there is a line that checks your actual fingerprint to avoid Rolling back.
So the command to flash that whole bootloader file at once is "flashboot flash all bootloader"? And it won't care that it's a folder, and not a .img file?
I see what you mean about flashing the .img files that are below the "bootloader" folder in that pic I posted. To me it makes sense that it would flash those. But as you said, you should only flash every file ending in .img and "bootloader" is actually a folder, even if it is full of those files. So I just want to be clear on how exactly to flash that bootloader file.
Sorry about all the newb questions lol. Once I see your reply here, I'm going to attempt the flash. After that, hopefully I won't need any more help.
bennylava said:
So the command to flash that whole bootloader file at once is "flashboot flash all bootloader"? And it won't care that it's a folder, and not a .img file?
I see what you mean about flashing the .img files that are below the "bootloader" folder in that pic I posted. To me it makes sense that it would flash those. But as you said, you should only flash every file ending in .img and "bootloader" is actually a folder, even if it is full of those files. So I just want to be clear on how exactly to flash that bootloader file.
Sorry about all the newb questions lol. Once I see your reply here, I'm going to attempt the flash. After that, hopefully I won't need any more help.
Click to expand...
Click to collapse
Let's try something a little bit easier first. As you say you unlocked bootloader, maybe you can flash the full rom through recovery. Copy the rom to a sdcard and try that first, maybe you will save yourself a lot of headaches doing this first.
I've bought two H830's and got both to TWRP/LOS ROM no problem. Regardless of your current official build on your phone, you can rollback to version 30c and dirtycow from there to get TWRP. You can get necessary tools/info from here.
0. (If you havn't already...) Enable OEM unlock in settings and unlock bootloader/fastboot
1. Use LGUP tool to clean flash an official 30c version (H83030c_00_0813.kdz) build to your LG H830
2. Dirtycow exploit to get TWRP
3. Use TWRP to install
Let me know how it shakes out
Also an important note, you CANNOT flash directly the recovery via fastboot to get TWRP, only the H850 can do that, NOT the H830. That's something important no one ever brings up. You must use the dirtycow exploit.
EDIT: Oh yeah, and I recommend using UPPERCUT to flash the kdz file since LGUP is such broken trash.
eduardvi995 said:
Let's try something a little bit easier first. As you say you unlocked bootloader, maybe you can flash the full rom through recovery. Copy the rom to a sdcard and try that first, maybe you will save yourself a lot of headaches doing this first.
Click to expand...
Click to collapse
So just put the zip file on my external SD card, and then tell flashboot to...? Or somehow use only the phone itself to flash the rom? Sorry I'm afraid I'm having trouble following along as I've never done this before.
But as per your instructions, the rom (the whole zip file) is now on the external storage SD Card.
Or did you mean to extract the zip file to a folder, and put that on the SD card? My next question would be thus:
What is the exact command to begin flashing, once I have everything in it's proper place? I did a little experiment where I tried to flash one of the files individually. The Linux terminal gave me the following error:
[[email protected] Desktop]$ cd bootloader
[[email protected] bootloader]$ fastboot flash aboot.img
unknown partition 'aboot.img'
fastboot: error: cannot determine image filename for 'aboot.img'
[[email protected] bootloader]$
As you can see, the bootloader folder is on the desktop, with many .img files inside it. Just as the pic in post #11 shows. Inside the bootloader folder is a .img file called "aboot.img". And for some reason fastboot "cannot determine the image filename for aboot.img"
DrowningInFreedom said:
EDIT: Oh yeah, and I recommend using UPPERCUT to flash the kdz file since LGUP is such broken trash.
Click to expand...
Click to collapse
Thank you for the reply! I've got two questions for you:
1. Do you have a link to the version of LG UP that you'd recommend using? It seems that there are many links out there in the wild, and some of them are to old versions. I'm not sure exactly which one I should use.
2. How exactly do you use Uppercut with LG Up? I got Uppercut, but it didn't seem to do anything when I double clicked on it. It just sat there. Is it like some kind of addon or modification to LG up? Or is it supposed to open as it's own program. Thanks!
Use the files provided by codefire , Launch UPPERCUT which will then hook into and launch LGUP automatically (All it does is make LGUP work without errors)
DrowningInFreedom said:
Use the files provided by codefire , Launch UPPERCUT which will then hook into and launch LGUP automatically (All it does is make LGUP work without errors)
Click to expand...
Click to collapse
Here's what happened when I tried to flash the right 80320a file (Nougat):
Any idea why it would say that?