INFO
I sold my P10 Lite, based on Huawei's decision to no longer provide bootloader unlock codes.
For a generic version of this project (ADB-Overlay) have a look at this thread.
The latest build of this project is still available.
---
Hello together,
here is a toolkit for the P10 Lite, it's designed to work primary with root (THE MOST TIME) so be careful what u are doing, specially if u are using the "Explorer". (Deleting the wrong file/folder on root lvl, could bring u in bad trouble!)
-
To all who used already my P9 Lite toolkit, there is currently not all available which u know from the old version, but i'll extend this toolkit in the next days. So, no worries about missing functions, they'll appear in some of the next builds.
-
About the usage,
- For a basic UI-Help just press F1
- If ur device is not detected u can switch off the "Device check" on the "Disclaimer" view (If u own a P10 which is not detected pls share a screenshot of the "adb devices -l" (l = lowercase L) command)
- U can also switch the (su -c) usage off (in the explorer view), BUT! after u performed any action which requires root, the trigger will be automatically switched on. (There is no other option, because my dll know only, use root or don't do so... There is no use root part-wise)
But anyways, i'm NOT responsible for any damage to your device!
Little preview of what u get
{
"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"
}
Tested Devices
Huawei P10 Lite [WAS-LX1A] [SINGLE-SIM]
Requirements
Platform: x86/x64 (Windows)
Frameworks: min. .NET 4
(Installed ADB/Fastboot driver)
Download
Mirror: See attachments
Mirror #1: GoogleDrive
XDA:DevDB Information
WAS-Lxx [EU] Toolkit, Tool/Utility for the Huawei P10 Lite
Contributors
k1ll3r8e
Version Information
Status: Stable
Current Stable Version: 0.0.0.5
Stable Release Date: 2018-08-01
Created 2018-03-30
Last Updated 2018-08-15
How-To
[Q:01] My device is not recognized by the toolkit?
1. Make sure NO adb-server is running!
2. U need to start ur device in android with enabled USB-Debugging (see the screenshot)
(Only in adb mode my toolkit can detect ur device)
3. Make sure that u granted adb access on ur device
(A popup will appear on the device and asks u to grant access.)
Try also to restart the toolkit after u granted access on ur device.
U can also check the device state by opening a cmd/terminal prompt and typing:
Code:
cd path\to\the\toolkit\adb
adb devices -l
check if ur device is listed as follows:
XXXXXXXXXXXXXXX device product:WAS-Lxx model:WAS-Lxx device:XXXXXXX
If ur device can't boot into Android or still didn't get detected, well, just deactivate the "Device Check" on the "Disclaimer" tab. And follow the description.
[Q:02] What does the Lxx Cxxx Bxxx mean?
The Lxx is the device model, the Cxxx is the region/operator identifier and the Bxxx is the build number.
Here is a short list about the regions/operators
ID (Cxxx) = Region/Operator | custom.bin (content)
----------------------------------------------------------------------------------------------------------------------------------------------------
C02 = Vodafone
C10 = Russia
C21 = Telefonica / O2
C40 = Czech Republic Telefonica / O2
C55 = Italia TIM
C66 = VIPmobile | vip/rs
C86 = Spain Yoigo
C109 = Amena/Orange
C112 = Latin America
C113 = Wind/Italy | wind/it
C121 = Türkei
C123 = Switzerland
C150 = T-Com | dt/de
C151 = India
C185 = North-Africa/Middle-East | hw/meafnaf
C209 = Asia (Pacific)
C212 = Iusacell/Nextel
C249 = Serbia Telekom
C432 = Nordic-European | hw/eu
C470 = Asia (Pacific)
C605 = Colombia
C637 = Spain
C636 = Asia-Pacific | hw/spcseas
C675 = India
C706 = New Zealand
C900 = GLOBAL
More comming soon...
Big THX for some of those "identifier" goes to:
@lost3
@baduncle
[Q:03] I want share my custom.bin & oeminfo, what i need to do?
U can get the files via the "Dual-/Single-SIM -> Export" or u can do the following steps (root required).
Open an terminal/cmd prompt and navigate to ur adb installation or the toolkit directory (path/to/the/toolkit/adb) and type the following commands.
Code:
adb shell
su
cat /data/custom.bin > /storage/emulated/0/custom.bin.bak
dd if=/dev/block/platform/hi_mci.0/by-name/oeminfo of=/storage/emulated/0/oeminfo.img.bak
exit
exit
adb pull /storage/emulated/0/custom.bin.bak custom.bin.bak
adb pull /storage/emulated/0/oeminfo.img.bak oeminfo.img.bak
Now u have 2 files, the custom.bin.bak and the oeminfo.img.bak just zip them and upload them to GoogleDrive or DropBox, etc. and share the link in this thread.
[Q:04] How can i manually boot into a specific mode?
Bootloader:
[device] = Turn the device off - Connect it to the PC - Press and hold: [Vol-]
[adb] = adb reboot bootloader
[fastboot] = fastboot reboot bootloader
E-Recovery:
[device] = Turn the device off - Connect it to the PC - Press and hold: [Vol+]
[adb] = N/A
[fastboot] = N/A
Recovery:
[device] = Turn the device off - Disconnect it from the PC - Press and hold: [Vol+ Power]
[adb] = adb reboot recovery
[fastboot] = N/A
Normal Boot:
[device] = Power button / Power button menu
[adb] = adb reboot
[fastboot] = fastboot reboot
Update Mode:
[device] = Turn the device off - Disconnect it from the PC - Press and hold [Vol+ Vol- Power]
[adb] = N/A
[fastboot] = N/A
[Q:05] Does the Dual-Sim upgrade survive an OTA?
Yes, the Dual-Sim modification will stay until u flash another oeminfo.
[Q:06] I upgraded to Dual-SIM and there is only one IMEI shown?
That's absolute normal... Because, u had a single-sim device before, so the device hold only one IMEI and the 2cd sim will use the same IMEI as the 1st sim or as shown the "0000000000000000".
Changelog
2018-08-01 - 0.0.0.5
* Added a Remote-Desktop
* Added a "partition selector" (recovery [Nougat], recovery_ramdisk [Oreo])
* Added a rooting option for Oreo
* Fixed a few bugs
* Realigned a few container
2018-04-21 - 0.0.0.4
* Added on the Device-Info view the BusyBox check
* Added the Phone control
* Added the Root menu (just waiting for permissions to include a zip)
* Added some features to the Explorer "View" menu (e.g. Sync with Treeview, Layout, Sort)
* Added a Display-Trigger to the "Power-Button" menu
2018-04-10 - 0.0.0.3
* Fixed a crash which appeared during device connection on the Explorer view
* Switched the whole window stuff to my new GlassWindow
* Added a AlphaChannelSlider (left beside the [--] button) for those which don't like transparent windows
* Added a Device-Info view
2018-04-01 - 0.0.0.2
* Fixed the icon bug (Big Icons, List)
* Re-positioned the "View" menu and made 2 of them, one for each view
* Refactored the "Button" layout, that they match now with the rest of the dark theme
* Added a fallback color "#2C2C2C" for those who got maybe the error message that the Glass-Effect couldn't be applied
* Added the "Shell-Tools" menu
* Added the 1st tweak (Pro-Mode)
Bug-Tracker
*FIXED in 0.0.0.2
- Noticed already the missing icons in the "Explorer" (Big Icons + List)
(Bug is already solved and will be fixed in the next version)
Known-Issues
- The "Explorer" "Big Icons" looking a bit ugly, that's because the p/invokes won't give me the "Extra Large" icons... I still work on it, so maybe it's fixed in the next version.
--
Drag 'n' Drop on any Explorer view, from outside the Application won't work until u run everything as Admin... That's a Windows UAC restriction and based on the fact, that we need the right's to create/delete/modify files/folders under Win8++ on the system HDD. (Like ADB pull for export of the oeminfo and custom.bin)
Missing Tweaks from the P9 Lite Toolkit
- As the screenshot shows, i managed to activate the "Double-Tap" menu, but that's all... The Double-Tap it self doesn't work... So there will be no "tweak" for this. - (Additional Info: The Double-Tap works^^ But ONLY on the lock-screen... And ONLY to turn the screen off... What a joke...)
- USB-OTG, is not available because, so far i know, u need a special kernel for it. (Which i can't provide, atm)
- AppTwin, because it should be enabled on any P10 Lite by default
Little - Update (1+2+3+4)
- I added a screenshot of the upcoming release, with integrated "Phone" control. (Currently only Call/Dial works)
- Added another screeny, now (Call/Dial/Add) is possible. Add, needs still interaction on the device side, like which "provider" (Device, Google, etc.) u want to choose. Dial, will insert the number in the default dialer, or it gets captured by any USSD protection. Call, will immediately start a call to the provided number.
- Just tested to send USSD-Codes like "*#06#", but it seems that u really have to type them... Even sending "*#06" and manually type the "#" doesn't work... U have to delete and re-type the whole USSD-Code...
- Added the final look of the "Phone". (At least, Add, Call, Dial, Hang-Up) is now possible.
For those which also use XAML, here are the control-button-geometries i created:
Menu-Button
Code:
<Path Fill="{Binding Foreground, RelativeSource={RelativeSource AncestorType={x:Type Button}}}">
<Path.Data>
<GeometryGroup>
<EllipseGeometry Center="2,2" RadiusX="1.5" RadiusY="1.5"/>
<EllipseGeometry Center="7,2" RadiusX="1.5" RadiusY="1.5"/>
<EllipseGeometry Center="12,2" RadiusX="1.5" RadiusY="1.5"/>
<EllipseGeometry Center="2,6" RadiusX="1.5" RadiusY="1.5"/>
<EllipseGeometry Center="7,6" RadiusX="1.5" RadiusY="1.5"/>
<EllipseGeometry Center="12,6" RadiusX="1.5" RadiusY="1.5"/>
<EllipseGeometry Center="2,10" RadiusX="1.5" RadiusY="1.5"/>
<EllipseGeometry Center="7,10" RadiusX="1.5" RadiusY="1.5"/>
<EllipseGeometry Center="12,10" RadiusX="1.5" RadiusY="1.5"/>
<EllipseGeometry Center="7,14" RadiusX="1.5" RadiusY="1.5"/>
</GeometryGroup>
</Path.Data>
</Path>
Call-Button
Code:
<Path Data="M 1.25,5.55 A 8.5,8.5 0 1 1 0.75,7 Z M 5,9 8,13 13,5" Stroke="{Binding Foreground, RelativeSource={RelativeSource AncestorType={x:Type Button}}}" StrokeThickness="1"/>
Hang-Up-Button
Code:
<Path Data="M 1.25,5.55 A 8.5,8.5 0 1 1 0.75,7 Z M 5,13 13,5 M 5,5 13,13" Stroke="{Binding Foreground, RelativeSource={RelativeSource AncestorType={x:Type Button}}}" StrokeThickness="1"/>
Dial-Button
Code:
<Path Stroke="{Binding Foreground, RelativeSource={RelativeSource AncestorType={x:Type Button}}}" StrokeThickness="1">
<Path.Data>
<GeometryGroup>
<EllipseGeometry Center="9,9" RadiusX="8.5" RadiusY="8.5"/>
<EllipseGeometry Center="6,5" RadiusX="0.5" RadiusY="0.5"/>
<EllipseGeometry Center="9,5" RadiusX="0.5" RadiusY="0.5"/>
<EllipseGeometry Center="12,5" RadiusX="0.5" RadiusY="0.5"/>
<EllipseGeometry Center="6,8" RadiusX="0.5" RadiusY="0.5"/>
<EllipseGeometry Center="9,8" RadiusX="0.5" RadiusY="0.5"/>
<EllipseGeometry Center="12,8" RadiusX="0.5" RadiusY="0.5"/>
<EllipseGeometry Center="6,11" RadiusX="0.5" RadiusY="0.5"/>
<EllipseGeometry Center="9,11" RadiusX="0.5" RadiusY="0.5"/>
<EllipseGeometry Center="12,11" RadiusX="0.5" RadiusY="0.5"/>
<EllipseGeometry Center="9,14" RadiusX="0.5" RadiusY="0.5"/>
</GeometryGroup>
</Path.Data>
</Path>
Delete-Button
Code:
<Path Data="M 0,7.7 5,2 16,3 16,12 5,13 Z M 8,5 13,10 M 8,10 13,5" Stroke="{Binding Foreground, RelativeSource={RelativeSource AncestorType={x:Type Button}}}" StrokeThickness="1"/>
WAS-LX1AC432B204dual
oeminfo
WAS-LX1AC432B206dual
oeminfo
I tested it on my WAS-LX1 C10 DS/ It works.
Perfect
Thank you !
rom issue
Dear Developer!
I suffering with a strange problem, i also opened a question thread about:
https://forum.xda-developers.com/p10-lite/help/please-help-fix-issue-t3805333
I'm not tried your toolkit yet, but i guess it maybe could help me... First: I would like to ask you what do you think about my issue(?). Probably you are much more technical than me, if you were able to create a toolkit for p10 lite... Should i try to fix my phone with your toolkit or can you suggest me any method? Do you have any idea what I could do?
Thanks you in advance!
Greets, NSX
nsx82 said:
Dear Developer!
I suffering with a strange problem, i also opened a question thread about:
https://forum.xda-developers.com/p10-lite/help/please-help-fix-issue-t3805333
I'm not tried your toolkit yet, but i guess it maybe could help me... First: I would like to ask you what do you think about my issue(?). Probably you are much more technical than me, if you were able to create a toolkit for p10 lite... Should i try to fix my phone with your toolkit or can you suggest me any method? Do you have any idea what I could do?
Thanks you in advance!
Greets, NSX
Click to expand...
Click to collapse
Use only stock ROMs for now, cuz there's no daily driver Customs for P10 Lite yet. Stock Oreo is really good. You can use HwOTA to flash stock ROMs.
nsx82 said:
Dear Developer!
I suffering with a strange problem, i also opened a question thread about:
https://forum.xda-developers.com/p10-lite/help/please-help-fix-issue-t3805333
I'm not tried your toolkit yet, but i guess it maybe could help me... First: I would like to ask you what do you think about my issue(?). Probably you are much more technical than me, if you were able to create a toolkit for p10 lite... Should i try to fix my phone with your toolkit or can you suggest me any method? Do you have any idea what I could do?
Thanks you in advance!
Greets, NSX
Click to expand...
Click to collapse
Heyho,
the "NRD-testkeys" are normally an issue with the "cust" partition. That means that ur oeminfo doesn't match with ur "cust" version. Let me explain... If u switch from SS to DS u change the device model (ID - Lx1 -> L21) this causes some problems on the "cust", because there is only one folder existent. The folder matching to the device u had before the switch. So all settings like "phone/umts" etc. are now invalid and can't be found under this model (ID). Because the folder simply doesn't exists.
How to fix it?!
U have to install/flash a complete stock rom via dload. - Get u FOR EXAMPLE an oeminfo like "L21AC432B183" and the rom "L21AC432B183", now u have to flash the oeminfo and straight after it, via dload, the FW upgrade.
-
During the flash of the "L21AC432B183" the system will check that u have "now" a L21 and will align the "cust" to that device.
Hope i could help u to understand how things work
Regards,
Sebastian
k1ll3r8e said:
Heyho,
the "NRD-testkeys" are normally an issue with the "cust" partition. That means that ur oeminfo doesn't match with ur "cust" version. Let me explain... If u switch from SS to DS u change the device model (ID - Lx1 -> L21) this causes some problems on the "cust", because there is only one folder existent. The folder matching to the device u had before the switch. So all settings like "phone/umts" etc. are now invalid and can't be found under this model (ID). Because the folder simply doesn't exists.
How to fix it?!
U have to install/flash a complete stock rom via dload. - Get u FOR EXAMPLE an oeminfo like "L21AC432B183" and the rom "L21AC432B183", now u have to flash the oeminfo and straight after it, via dload, the FW upgrade.
-
During the flash of the "L21AC432B183" the system will check that u have "now" a L21 and will align the "cust" to that device.
Hope i could help u to understand how things work
Regards,
Sebastian
Click to expand...
Click to collapse
Thank you very much for your help. im going to try all of this on next weekend, because workdays i have to use my phone.
greets, NSX
---------- Post added at 12:18 PM ---------- Previous post was at 11:59 AM ----------
k1ll3r8e said:
If u switch from SS to DS u change the device model (ID - Lx1 -> L21) this causes some problems on the "cust", because there is only one folder existent.
Click to expand...
Click to collapse
just a quick question: lx1 is single sim and l21 for dual sim?
Because i had a dual sim model but my sw version was lx1
did i misunderstood something?
btw, i having a very strange problem with the phone, out of the box. seems like a sw render problem. for example in nova launcher i have strange animation distortion and diatorted masking. i was hoping it will be fixed too with changing the rom but this problem still exist.. do you thing it can be because of some wrong factory software inatallation?
thanks, NSX
nsx82 said:
Thank you very much for your help. im going to try all of this on next weekend, because workdays i have to use my phone.
greets, NSX
---
just a quick question: lx1 is single sim and l21 for dual sim?
Because i had a dual sim model but my sw version was lx1
did i misunderstood something?
btw, i having a very strange problem with the phone, out of the box. seems like a sw render problem. for example in nova launcher i have strange animation distortion and diatorted masking. i was hoping it will be fixed too with changing the rom but this problem still exist.. do you thing it can be because of some wrong factory software inatallation?
thanks, NSX
Click to expand...
Click to collapse
Heyho,
np
-
Yes, the "Lx1" are always the SS and the "L[1-9]1" are the DS variants. - Btw. u can't see the "real ID" under "Settings -> Info" to see the "real ID" u have to look in the "current" oeminfo.
-
I wrote a tool for this kind of tweaking/exploring, have a look at it, u can get it here
EDIT:
About the issue with the display/animations, it could also be a problem with the HW... I have seen a few forum posts about "factory delivered" broken chips etc.... Maybe there is something else wrong, if it was really from the 1st day u got it.
Regards,
Sebastian
Little Update
Heyho together
-
Here is a little preview of the upcoming update.
* Added a Remote-Desktop (touch, swipe and keyboard are working so far)
* Improved the speed
* Fixed a few minor bugs
Release should be in 2-3 days
Version 0.0.0.5 is online!
Regards,
Sebastian
k1ll3r8e said:
[Q:03] I want share my custom.bin & oeminfo, what i need to do?
U can get the files via the "Dual-/Single-SIM -> Export" or u can do the following steps (root required).
Open an terminal/cmd prompt and navigate to ur adb installation or the toolkit directory (path/to/the/toolkit/adb) and type the following commands.
Code:
adb shell
su
cat /data/custom.bin > /storage/emulated/0/custom.bin.bak
dd if=/dev/block/platform/hi_mci.0/by-name/oeminfo of=/storage/emulated/0/oeminfo.img.bak
exit
exit
adb pull /storage/emulated/0/custom.bin.bak custom.bin.bak
adb pull /storage/emulated/0/oeminfo.img.bak oeminfo.img.bak
Now u have 2 files, the custom.bin.bak and the oeminfo.img.bak just zip them and upload them to GoogleDrive or DropBox, etc. and share the link in this thread.
Click to expand...
Click to collapse
I guess your Q&A kind of answers my question, though I want to be absolutely sure:
Sharing your oeminfo (and/or custom.bin) file(s) with others, does not give away any personal/unique info. I checked my oeminfo with a HexEditor and it seems to include my Firmware upgrade history (at least the last two updates), IMSI (only SIM/Network Operator - unless I overlooked something), and those hmac/&token values. With these infos nobody should be able to "do bad stuff" - am I right?
Please correct me if I'm wrong. Thanks in advance for any input, cheers!
callmeWhiskers said:
I guess your Q&A kind of answers my question, though I want to be absolutely sure:
Sharing your oeminfo (and/or custom.bin) file(s) with others, does not give away any personal/unique info. I checked my oeminfo with a HexEditor and it seems to include my Firmware upgrade history (at least the last two updates), IMSI (only SIM/Network Operator - unless I overlooked something), and those hmac/&token values. With these infos nobody should be able to "do bad stuff" - am I right?
Please correct me if I'm wrong. Thanks in advance for any input, cheers!
Click to expand...
Click to collapse
Heyho,
if you would have used my OEMInfo Tools, you would have seen that those values are no secret.
-
For example, the FW builds are needed to determine the current OS and if needed, the fallback/restore versions. Also the HMAC is needed for the OTA (the HMAC is used in conjunction with your IMEI, so the HMAC alone, is worth nothing). There is also a "Tamper-State" when and how often you unlocked/rooted your device.
But so far i saw, there are no "personal" data, like the IMEI or the SIM-Card Number. Maybe they are stored as one of those checksums (md5/sha1).
Regards,
Sebastian
k1ll3r8e said:
if you would have used my OEMInfo Tools, you would have seen that those values are no secret.
-
For example, the FW builds are needed to determine the current OS and if needed, the fallback/restore versions. Also the HMAC is needed for the OTA (the HMAC is used in conjunction with your IMEI, so the HMAC alone, is worth nothing). There is also a "Tamper-State" when and how often you unlocked/rooted your device.
But so far i saw, there are no "personal" data, like the IMEI or the SIM-Card Number. Maybe they are stored as one of those checksums (md5/sha1).
Click to expand...
Click to collapse
Thank you very much for clarifying and shedding some light on this, Sebastian!
From what I've read, reconstructing (files) from checksums doesn't (really/easily) work - though in theory (if enough additional parameters are given, and IMEI/IMSI are kind of short strings) it could be reverse engineered - unless I interpreted my research findings wrong :victory:
I assume it's safe though
Liebe Grüße nach Delmenhorst!
Hi world(first post since android(previous windows mobile member of xda)),
I have P10 lite for almost a year(not rooted for warranty issues).
I wanted to perform a stock firmware backup before I endulge in rooting/custom ROM.
Is that possible with TWRP(with or without rooting), and are there any how-to's?
Sorry for being such a newbie, just like to upgrade to 8.0 and revert back to stock in case of a problem or warranty issues.
Thank you.
Recovery
Related
Because nobody of us wants to read over 60 Pages about the Beta Release of Froyo for Galaxy S, i decided to create a litte Thread with all necessary Infos.
Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Ripped from Cyanogen. Thank you. ;-)
BEFORE YOU GO:
- PLEASE UPDATE KIES TO NEWEST VERSION!
- READ THE WHOLE POST BEFORE FLASHING TO AVOID PROBLEMS!
- YOU SHOULD ONLY FLASH TO JPC IF YOU ARE AN EXPERIENCED USER!
- MAKE A BACKUP OF YOUR /efs FOLDER!
IF YOUR PHONE DOESNT SUPPORT 3-BUTTON RECOVERY/DOWNLOAD-MODE, DON'T FLASH! IF THE FLASH FAILS, YOU MIGHT NOT BE ABLE TO REFLASH IT!
JPC WILL CHANGE YOUR PRODUCT CODE, THERE MIGHT BE PROBLEMS WITH NETWORK LOCKED PHONES! READ THE FAQ!!!
BELL USERS, please read the whole FAQ before doing anything here described!
Here´s a nice Demo Video about JPC from User arkhanist:
http://www.youtube.com/watch?v=J1i01yXuamc
Good Work!
------------------------------------------------------------------
HOWTO FLASH TO JPC USING KIES IN TEST MODE:
- Make sure your Phone is fully charged!
- Open Kies and connect your Galaxy S
- Open the Firmware Update Window and press CTRL+ALT+U+P (for activating Test Mode)
- Close the Update Window, but don´t close whole Kies Software. Let it run while doing the next Step.
- Run regedit and edit the following entries: (Screenshot Only one of the entries had all of the necessary fields.)
Code:
[HKEY_CURRENT_USER\Software\Samsung\Kies\DeviceDB\[COLOR="red"][B]X[/B][/COLOR]]
"SoftwareRevision"="I9000XXJF3/I9000OXAJF3/I9000XXJF3/I9000XXJF3"
"ProductCode"="GT-I9000HKDXEU"
"HIDSWVER"="I9000XXJF3/I9000OXAJF3/I9000XXJF3/I9000XXJF3"
"DEVCONINFO"=""
[COLOR="Red"]X[/COLOR] = Device Number
NOTE: BELL Users have to change the Model Name from "GT-i9000m" to "GT-i9000".
NOTE: If there are more than 3 Numbers, just delete all of them and open the Firmware Update Window in Kies, and close it again. Kies will recreate required entries.
- Open the Firmware Update Window again
- Now you should be able to Update to JPC Firmware
- Follow onscreen Instructions
AFTER FLASHING TO JPC ITS NECESSARY TO DO A DATA/FACTORY RESET FROM RECOVERY (Volume up + Home + Power). OTHERWISE YOUR PHONE WILL DO MYSTERIOUS THINGS!!!
DON'T INSTALL THE NEW TASK MANAGER FROM SAMSUNG APPS, IT WILL KILL YOUR SYSTEM. IF YOU´VE DONE IT, ONLY A FACTORY RESET WILL BRING YOUR SYSTEM BACK TO LIFE!
------------------------------------------------------------------
JPC FIRMWARE FOR FLASHING WITH ODIN:
http://www.multiupload.com/LVY75LHMNT
Thanks to Richthofen!
Howto from the sticky BIG FAQ Thread:
- Make sure your Phone is fully charged!
- Open ODIN. (And close Kies, if you have it open. It is important to have ODIN open BEFORE connection the phone via USB!)
- Select the PDA/Modem/CSC/.PIT files in Odin. (.PIT and PDA are required. CSC and Modem are HIGHLY recommended. They may be necessary depending on the PDA! Try flashing all three BEFORE reporting bugs, if you only used one initially!)
- Remove the SD card and SIM card from the phone.
- Turn the phone into the download mode by pressing and holding VolumeDown+Home+Power.
- Connect your phone with your computer and wait until the drivers are installed.
- If the drivers are installed, click Start.
- The phone will be flashed and once it’s finished, it will boot up. (Do NOT disconnect the usb-cable, remove the battery or otherwise interrupt this process!)
- You have successfully flashed your phone.
- Do a Data/Factory Reset
------------------------------------------------------------------
ADDITIONAL DOWNLOADS:
Odin v1.3: http://rapidshare.com/files/417198468/Odin3_v1.3.zip
PIT 803: http://rapidshare.com/files/417198470/s1_odin_20100803.zip
------------------------------------------------------------------
HOWTO ROOT JPC FIRMWARE:
http://www.multiupload.com/GJEZ1OT9NN
- CLOSE KIES!!!
- Extract and copy update.zip to /sd of phone
- Run Odin with Auto Reboot UN-checked, loading the i9000_Kernel.tar as PDA
- Put the phone into download mode and flash the i9000 Kernel.
- Pull the battery. reboot into recovery mode and flash the update.zip you put in the root folder of your sdcard.
- Pull the battery again, reboot into download mode again.
- Run Odin with Auto Reboot checked, loading the I9000XXJPC_KERNEL.tar as PDA
- Reboot
Source: http://forum.xda-developers.com/showthread.php?t=769308
Thanks to vibez!
Tested two times by me, working Solution.
------------------------------------------------------------------
HOWTO APPLY LAGFIX TO JPC FIRMWARE:
Source: http://forum.xda-developers.com/showthread.php?t=760571
Thanks to RyanZA!
Tested two times by me, working Solution.
Quadrant: ~2000
Linpack: ~14 MFlops
------------------------------------------------------------------
FAQ:
1. Can i flash to JPC if any Lagfix is applied to my Phone?
- Yes, you can. But after Flashing you have to do a Data/Factory Reset at Recovery.
2. My Galaxy S hangs after Boot Animation / is vibrating every few seconds. Whats wrong?
- Goto Recovery (Volume Up + Home + Power) and do a Data/Factory Reset. Now it should start correctly.
3a. Cannot connect my Galaxy S to Kies.
- Close all running Apps on your Phone. Kies does not work with Launcher Pro because its a running app, so you have to remove it.
- Disable USB-Debugging
3b. Cannot connect my Galaxy S to Kies. MTP Application on my Phone is crashing on and on.
- Backup Your Internal SD data
- Unmount your Internal SD (Menu -> Settings -> SD-Card...)
- Format It
- Remount
- Plug in USB and it should work when plugged back in
4. My Calendar-App / Internet Browser is ****ed after restoring Data from Titanium Backup.
- Don´t do this, Froyo Data seems to be incompatible to 2.1 Data!
- Goto Settings -> Applications -> Manage Applications -> All and clear the Calendar / Internet Browser Data manually. Should work for other Apps, too!
5. Is it worth to flash to JPC from JM6?
- Simply, YES!
6. Some Apps at the Market seems to be missing.
- Look for "Eris Market Fix" at the Market. ;-)
7. My Phone asks me for a Unlock Code. Product Code has changed to KOR. What to do?
- Your Phone have to be rooted! Busybox is required!
- Start->Run-> cmd
- Change to your SDK\tools Directory e.g cd C:\Program Files (x86)\Android SDK\tools
- adb shell
- su
- cd /efs
- ls -al
If now nv_data.bak AND nv_data.bak.md5 are displayed, do the next few steps marked with (a)
If now .nv_data.bak AND .nv_data.bak.md5 are displayed (dot before filenames), do the next few steps marked with (b).
(a)- mv nv_data.bin nv_data.jpc
(a)- mv nv_data.bin.md5 nv_data.jpc.md5
(a)- mv nv_data.bak nv_data.bin
(a)- mv nv_data.bak.md5 nv_data.bin.md5
(a)- reboot
(b)- mv nv_data.bin nv_data.jpc
(b)- mv nv_data.bin.md5 nv_data.jpc.md5
(b)- mv .nv_data.bak nv_data.bin
(b)- mv .nv_data.bak.md5 nv_data.bin.md5
(b)- reboot
Now your Phone shouldn´t ask for a Code.
8. Where to get the Unlock Code for my Device?
See this Tutorial: http://forum.xda-developers.com/showthread.php?t=770499
9. 3G Connection isn´t working on BELL Phones.
- Select Mobile networks
- Select Access Point Names.
- Press Menu to add a New APN setting.
- Fill in the following settings:
* Name: Bell
* APN: pda.bell.ca
* Proxy: web.wireless.bell.ca
* Port: 80
* Username: <Not set>
* Password: <Not set>
* Server: <Not set>
* MMSC: http://mms.bell.ca/mms/wapenc
* MMS proxy: web.wireless.bell.ca
* MMS port: 80
* MMS protocol: WAP 2.0
* MCC : 302
* MNC : 610
* APN type : <Not set>
Authentication type: not set
APN Type: internet + mms
- Press Menu and Save.
------------------------------------------------------------------
HOWTO GET INTO RECOVERY:
- Turn off your Phone
- Hold VOLUME UP + HOME Buttons
- While holding VOLUME UP + HOME Buttons press POWER Button until Display lights up, then release only POWER Button
- Still hold VOLUME UP + HOME until you got into Recovery
- Release all Buttons
------------------------------------------------------------------
HOWTO GET INTO DOWNLOAD-MODE:
- Turn off your Phone
- Hold VOLUME DOWN + HOME Buttons
- While holding VOLUME DOWN + HOME Buttons press POWER Button until you reach Download-Mode
- Release all Buttons
{
"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"
}
Supported Android OS Languages:
- Bulgarian
- Cestina
- Dansk
- Deutsch (Deutschland, Österreich, Schweiz)
- English (Australia, Ireland, New Zealand, South Africa, United Kingdom, United States)
- Espanol (Espana, Estados Unidos)
- Francais (France, Suisse)
- Hrvatski
- Italiano
- Latvian
- Lithuanian
- Magyar
- Nederlands (Belgie, Nederland)
- Polski
- Portugues
- Romana
- Slovencina
- Slovenian
- Suomi
- Svenska
- Türkce
- Exxnvika
- Pyccknn
- Cpnckn
- Ykpaihcbka
- Korean
------------------------------------------------------------------
Supported SWYPE Languages:
- US English
- UK English
- Deutsch
- Francais
- Espanol
- Italiano
- Nederlands
- Portugues Europeu
- Polski
- Korean
- Türkce
Source: My own Phone. Samsung Galaxy S i9000 (unbranded) bought at amazon.de
------------------------------------------------------------------
HOWTO CLEAN YOUR PHONE FROM UNWANTED STUFF:
ONLY PROCEED IF YOU KNOW WHAT YOU´RE DOING! THIS IS VERY DANGEROUS AND CAN **** UP YOUR ANDROID!
- Start -> Run -> cmd
- Change to your SDK\tools Folder e.g. cd C:\Program Files (x86)\Android SDK\tools
- adb shell
- su
- Accept granting Root Privileges at your Phone
- cd system/app
- rm unwantedapp.* e.g. rm MiniDiary.*
Standard Apps:
AccountAndSync.apk/odex -> The app in the drawer, not the settings.
AddToHome.apk/odex
AudioPostcard.apk/odex
Avatar.apk/odex -> The app that launches Avatar in the video player.
BuddiesNow.apk/odex
Dlna.apk/odex [Allshare]
FlashPlugin.apk/odex
GoGo.apk/odex
Infoalarm.apk/odex [Daily Briefing]
KindleStub.apk/odex
Layer-samsung.apk/odex
MediaHub.apk/odex
Memo.apk/odex
Mini Diary.apk/odex
MobiTV.apk/odex
MyAccountStub_4-5-10.apk/odex
Myfiles.apk/odex
Sims3_Samsung_Embed_Launcher.apk/odex
slackerradio.apk/odex
Swype-Tips.apk/odex
Telenav.apk/odex
thinkdroid.apk/odex [ThinkFree Office]
vvm-signed.apk/odex -> T-Mobile Visual Voicemail [can be re-downloaded from the market. for some reason that version is the preferred one.]
VoiceRecorder.apk/odex
VoceDialer.apk/odex
Writeandgo.apk/odex
TouchwizWidgets:
Day.apk/odex
DualClock.apk/odex
SamsungWidget_Calenderclock.apk/odex
SamsungWidget_Feedandupdate.apk/odex
SamsungWidget_stockclock.apk/odex
SamsungWidget_Weatherclock.apk/odex
Source: http://forum.cyanogenmod.com/topic/3319-stock-apps-that-can-be-deleted-post-root/
------------------------------------------------------------------
Thanks alot was gonna ask if some one could do this
Awesome stuff!
Thanks!
Works great,
Great, thanks for this usefull thread
And just because i also dont want to read all 50 pages of the other thread:
Is it worth an upgrade from jm6 (2.1) or should i still wait if i want a froyo firmware as stable as the latest eclair firmwares?
thanks
I was on JM6, too.
I thinks its worth. Froyo rockz!
Many thanks Aery!
Any help would be appreciated.
As far as i know i have followed all tutorials correctly.
My phone will not mount in Kies using Kies Mode, mass storage is fine and Tethering is also fine.
Any ideas ?
For the help list:
My Internet browser is f*cked after a restore from Titanium Backup.
Goto Settings -> Applications -> Manage Applications -> All - > Internet
Then choose Clear data. Should work then!
lordjubblydave said:
Any help would be appreciated.
As far as i know i have followed all tutorials correctly.
My phone will not mount in Kies using Kies Mode, mass storage is fine and Tethering is also fine.
Any ideas ?
Click to expand...
Click to collapse
same here .
it doesn´t work... on kies mode.
GXFX said:
same here .
it doesn´t work... on kies mode.
Click to expand...
Click to collapse
Looks like were both stuck for a while.
Out of interest, why do Samsung not do OTA Updates ?
Will Kies change my CSC if I do it like this?
lordjubblydave said:
Looks like were both stuck for a while.
Out of interest, why do Samsung not do OTA Updates ?
Click to expand...
Click to collapse
yeah ;/
and samfirmwares sad that is dangerous to flash it with odin so....
I don´t know , but it´d be really awesome !
Kies isn´t A **** . It is THE **** --'
Is this working on Bell I9000M?
Maybe someone can post instruction for those who are using Bell and dont have the 3 button combo.
Thanks
Can someone plse make a vid ??
did not work for me when i go into test mode as well it tells me the latest version is JH2 which i have i changed ever thing in the 3 reg files and left the last one blank
SOOOOOO.
Basically i can never upgrade my firmware officially, due to a crap Samsung App.
I guess i will just have to wait for a good custom rom.
This sucks balls, hell even my old G1 is running froyo (Cyanogenmod 6)
This is the only problem i have with my phone
lordjubblydave said:
SOOOOOO.
Basically i can never upgrade my firmware officially, due to a crap Samsung App.
I guess i will just have to wait for a good custom rom.
This sucks balls, hell even my old G1 is running froyo (Cyanogenmod 6)
This is the only problem i have with my phone
Click to expand...
Click to collapse
gonna try to flash with odin.
i´ll report soon as i can.
where I can find this "X = Device Number"?
EFS (IMEI) Backup tool N910U/F/L/K/C/P/T/G/H/R/6W/8W N915G(note4 Edge)(support to other variant soon)
{
"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 simple EFS backup tool. We are very well knowing about what EFS is and why it is MUST to backup on every rooted device. If you don't know then Read this.
Right now this tool support only SM-910U and support to other variant will be added when it is available.
Download :
Pro Version
XDA version (free)- Attached at end of this post.
Difference between Free/Play store
-Both version makes backup in same format and no difference in backup.
-Free version will save file in MyEFS and if you make next backup it will replace older one. While play store version everytime creates new folder with date ,Time and your IMEI stamp so you can keep multiple backup as well no confulsion about which backup is made when and on which device. Also it makes copy of build.prop so you can get idea you were on which ROM when backup created)
-On free version you have to select option according your device model, if you select wrong your EFS backup will be wrong On play store version it will auto detect your model and make backup accordingly. In case your model not supported it will give warning msg.
-Play store version give notification in case backup not created OR you select wrong model and will have option to contact developer in such case.
-Weekly Auto backup feature available on play store version.
This tool using generic name of partition block and you can restore with simple adb shell
dd if=/path of backup files/ of=/partition block according your device
ChangeLog
1.0 - Initial release for N910U
1.1 - Updated for making backup of other efs related partition as well added support for N910F (all 1.0 user request to make new backup with new version)
1.2 - Added support for N910K
1.3 - Added support for N910C
1.4 - Added support for N910P
1.5 - Added support for N910T and N910G
1.6 - Added support for N910H/R/W8/6W
1.7 - Added support for N910L
1.8 - (Major Update - Recommended for all to update)
-Added support for N9100
-Backup location changed to IntSD/MyEFS for ready to use Pro version (now both have same location)
-Now it removes old backup before creating new backup to insure that created backup is new. still you can check date of created files)
1.9 - Added support for N915G (Note4 Edge)
2.0 - Added support for system less root. New UI.
XDA:DevDB Information
Dr.Ketan IMEI Tool, ROM for the Samsung Galaxy Note 4
Contributors
dr.ketan
ROM OS Version: 4.4.x KitKat
Version Information
Status: Stable
Created 2014-11-19
Last Updated 2017-04-05
EFS Info
What is EFS
This part of the device contains some important and some basic info related to our device identity like Bluetooth MAC address, wireless devices MAC addresses, product code (also in the nv_data.bin) and the very main IMEI address (nv_data.bin), programming parameters for the device such as your account information (phone number, etc), data provisioning parameters, and a whole bunch of other things. So you can guess it's will be different for each device and one can't use others. In latest samsung device this information store in other partition so requires to make backup of that partition too.
How it can corrupt :
- Any bad flashing, mishandling system modification can cause this.
- Also It can be corrupted by downgrading stock ROM. If you flash any old ROM on newer ROM it can corrupt EFS. Basically newer ROM believed to have new kernel that changes EFS data which older Modems can't read and results to fail in reading IMEI.
Impact on device/How I know I have corrupted EFS
When there is EFS partition is corrupted, device loses IMEI and due to this device can't gets connected to network. Baseband info also sometimes shows unknown.
-Check your IMEI in setting / by dialling *#06# if it is null OR if it starts with 0049** then IMEI is generic and corrupted. In Normal case IMEI which you can see in device setting or dialing *#06# is exactly same you can see on bill/box/sticker under battery compartment
-If you are unable to connect to network in spite of correct IMEI, chance are
A. Your device is Locked to specific Network OR
B. Your device is banned due to tempered IMEI
-If your AP,CP,CSC all are correct and even you are getting error (unknown CSC XXX) on kies update, it may be due to corrupt Product code in EFS. Read This for detail.
What care should i take
Before flashing anything, first thing you should do is to make EFS backup. Every person who have rooted device should make EFS backup earliest and place it to safer place on PC and /Cloud.
If you are on older ROM, make EFS backup on older ROM as well make another after upgrading ROM too.
If you have already updated to newer ROM, make backup on current ROM.
Exit "Permanent Safe Mode" This condition represent with loss of IMEI + yellow text box on homescreen with device info.here is Screenshot
Here is different method to remove it.
Method1 :
Open root explorer.
Navigate to /efs/FactoryApp/
Open "factorymode" file as Text and edit it:
Change this:
Code:
OFF
To:
Code:
ON
Open "keystr" file as Text and edit it:
Code:
OFF
To:
Code:
ON
Reboot device.
Method2:
Open Terminal emulator
Write the following:
Code:
su
Then click enter. It will ask for super user permission, give it permissions.
Write the following & click enter:
Code:
rm /efs/FactoryApp/keystr
Write the following & click enter:
Code:
rm /efs/FactoryApp/factorymode
Write the following & click enter:
Code:
echo -n ON >> /efs/FactoryApp/keystr
Write the following & click enter:
Code:
echo -n ON >> /efs/FactoryApp/factorymode
Write the following & click enter:
Code:
chown 1000.1000 /efs/FactoryApp/keystr
Write the following & click enter:
Code:
chown 1000.1000 /efs/FactoryApp/factorymode
Write the following & click enter:
Code:
chmod 0744 /efs/FactoryApp/keystr
Write the following & click enter:
Code:
chmod 0744 /efs/FactoryApp/factorymode
Reboot your device
Method3
Install attached safemode_exit apk as regular app. Open from drawer - Grant su permission - Reboot when asked.
e:failed to mount /efs(invalid argument) error with bootloop
This condition usually happens with using unsupported tool (usually from play store).
To recover this, needs to use adb shell
Code:
adb shell
mke2fs / dev/block/mmcblk0p[COLOR="Red"]x[/COLOR]
mount-w-t ext4 / dev/block/mmcblk0p[COLOR="red"]x[/COLOR] / efs
x means your device EFS partition number
PS : It needs CWM and busybox installed.
Other model user have rooted device contact me to add support for their device.
no work for 910k
Thanks dr ketan.
Sent from my SM-N910U using Tapatalk
What is with N910F ?
19stephan77 said:
What is with N910F ?
Click to expand...
Click to collapse
Do you have N910F with root access?
Sent from my SM-N900 using xda premium
dr.ketan said:
Do you have N910F with root access?
Sent from my SM-N900 using xda premium
Click to expand...
Click to collapse
Dr, for SM-910F if i could help..
friedrich420 said:
Dr, for SM-910F
Click to expand...
Click to collapse
Can you make some space on Inbox so i can send msg?
Thank you.
dr.ketan said:
Can you make some space on Inbox so i can send msg?
Thank you.
Click to expand...
Click to collapse
yep.. i keep forgetting..
i have n910K with root
Thanks doc!
This basic thing and most important thing! :thumbup:
With this, This tool will help people.
..hope it will decrease the number of people reporting: I lost my imei or I lost network connectivity after so and so...how can I.... ?
Sent from my Note ? using xda premium
Hopefully people will read this.
[quote name="dr.ketan" post=56004124]Do you have N910F with root access? <br />
<br />
<br />
Sent from my SM-N900 using xda premium[/QUOTE]<br />
<br />
Dr, for SM-910F if i could help..<br/>
Yes I have N910F rootet. Does it work?
910F is ready. Will update soon
Sent from my SM-N900 using xda premium
Great. Thank you. Upload today?
19stephan77 said:
Great. Thank you. Upload today?
Click to expand...
Click to collapse
I am waiting report for one more model. I will update tomorrow
Looking forward to this on my 910T
dr.ketan said:
I am waiting report for one more model. I will update tomorrow
Click to expand...
Click to collapse
Any possibilties with N910G? I just rooted it, if I'm can be of any help...
Tool updated
ChangeLog
1.1 - Updated for making backup of other efs related partition as well added support for N910F
All 1.0 user request to make new backup with new version
Play store version may take 3-4 hrs to appear new update
.
{
"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 XDA Developer
Here another port of flymeos from member:MROM
I saw it on Another website and want to share it with you
The new port has many improvements ....
IAM NOT RESPONSIBLE FOR ANY DAMAGE OR DATA LOSS FROM YOUR PHONE
Thanks for topsecret78 for get rom source and change details
Source for rom and autor of rom
http://bbs.gfan.com/android-8205458-1-1.html
Flyme version: Flyme 4.5.4.3R (trial version)
Android Version: 5.0.2
Fit models: Sony Z1
Change details ========================== ======================
Update fixes
[Contact]
Some models feature increased SIM card contacts
[Setup]
Click Clear data repair some models only restart problem
Fixed problems with some models automatically correct time
Each page repair settings ">" button too far left
Repair Storage automatically change settings problem
【information】
Fix import SIM card information being given problem
【other】
Repair backup data put out the screen after hibernation, there can not complete the backup problem
Synchronization Flyme latest code
[Precautions]
1: need to unlock
Hide virtual key ways: Edit the system in the build.prop find qemu.hw.mainkeys = 0 change the 0 to 1 to restart the phone
Click to expand...
Click to collapse
Changelog
CHECK DOWNLOAD PAGE FOR CHANGELOG
here some pics
Another screenshots here
Click to expand...
Click to collapse
So we Reach the download part
Note : looks like flyme 5 is officially maintained by (machao) member on (gfan) forum and latest builds will be found HERE
flyme 4.5.4.3 beta Google Drive
Downloaded it?! Let's install it and taste flyme
First ensure your bootloader is unlocked
1. Put Zip file on your sdcard
2. Restart your phone into your favourite recovery
3. Backup your data
4. Wipe (System,Data,cache,dalvik cache) not important to wipe internal memory
5. Install Zip from sdcard
6.restart system
First start will take 5 up to 10 min so don't think it's bootloop
TESTED ON C6903
After start let it 2 min and restart to install Su
You can download it from official website or you can use kingroot or kingo to root
Please sent permission to download file rom.
You can download now
Hit thanks if you like it
abdo.war said:
You can download now
Hit thanks if you like it
Click to expand...
Click to collapse
Where are kernel sources? You can't post a rom without posting kernel sources. Also, could you post a link to rom sources too. Thanks.
I am not the builder of this rom
I found his rom patched on another website
And he doesn't provide any source for the rom
He only put github link of flymeos sources but I haven't found our kernel resources there
If you want the link I will post it
He also patched this rom for Z2 ,3 ,1C
https://github.com/FlymeOS
I am still new in XDA... So if I am wrong just teach me
abdo.war said:
I am not the builder of this rom
I found his rom patched on another website
And he doesn't provide any source for the rom
He only put github link of flymeos sources but I haven't found our kernel resources there
If you want the link I will post it
He also patched this rom for Z2 ,3 ,1C
https://github.com/FlymeOS
I am still new in XDA... So if I am wrong just teach me
Click to expand...
Click to collapse
Doesn't matter who the builder is: posting roms without kernel sources is not allowed. For your sake you should post kernel sources or the mods will close this thread.
Report thread to mods to close it
I am sorry but I am still new here
abdo.war said:
Report thread to mods to close it
I am sorry but I am still new here
Click to expand...
Click to collapse
I am not going to report you, but rules are rules. They are part of GPL license...
Source for rom and autor of rom
http://bbs.gfan.com/android-8205458-1-1.html
Translate from google
Flyme version: Flyme 4.5.4.3R (trial version)
Android Version: 5.0.2
Fit models: Sony Z1
Change details ========================== ======================
Update fixes
[Contact]
Some models feature increased SIM card contacts
[Setup]
Click Clear data repair some models only restart problem
Fixed problems with some models automatically correct time
Each page repair settings ">" button too far left
Repair Storage automatically change settings problem
【information】
Fix import SIM card information being given problem
【other】
Repair backup data put out the screen after hibernation, there can not complete the backup problem
Synchronization Flyme latest code
[Precautions]
1: need to unlock
Hide virtual key ways: Edit the system in the build.prop find qemu.hw.mainkeys = 0 change the 0 to 1 to restart the phone
hello guys I m getting error while flashing this rom on c6902 getting this error ("E:Error executing updater binary in zip '/external_sd/ROMS/flymeOS_C6903_4.5.4.3R.zip)
Need help plzzz..
markakash said:
hello guys I m getting error while flashing this rom on c6902 getting this error ("E:Error executing updater binary in zip '/external_sd/ROMS/flymeOS_C6903_4.5.4.3R.zip)
Need help plzzz..
Click to expand...
Click to collapse
Try to flash boot.IMG file
Connect your phone in Fastboot mode by press volume up while connecting to pc
By flashtool or using
Factbook command
fastboot flash boot boot.IMG
Then reboot
fastboot reboot
Click to expand...
Click to collapse
Then try to install it
I installed rom from flashfire but it's dangerous
link to download in fisrt post
https://drive.google.com/file/d/0B3yReeEdHxbWSkFrYmhXbjJRaE0/view
or
http://pan.baidu.com/s/1pJXPr8R
I tested and work xperia Z1 C6903
---------- Post added at 16:30 ---------- Previous post was at 16:21 ----------
Info from source
"According to the competition regulations to place the file and naming 2: According to the rules without built-root themselves into the brush to 3: L39h and C6902 brush into no signal extraction system \ etc \ firmware \ c6x02 in the documents covering the intake system \ etc \ firmware can restart"
and
"Please read the complete message painted machine
ROM tested before release because of personal consequences Brush problems caused not bear
Built-in networking to promote the software, please support the author can then run reservations can also uninstall (as some promotion app requires placing it under the system needs to RE Manager Entering system / app Delete)
Prohibit secondary modified to personally thank all publication reproduced, please indicate support oil"
Since this is based on CM12 meaning android 5.0.2
Does this have any slow charging issues?
Rom update to Flyme 4.5.4.4R
Change details ========================== ======================
Update fixes
[Contact]
All models support SIM card contacts
【camera】
Repair photographs sound problems can not be closed
Added (some models) Set the option to save photos to SD card
【music】
Repair song not normally know the songs matching problem
【other】
Living repair service hotel category loading problems
Synchronization Flyme latest code
[Precautions]
1: need to unlock
Hide virtual key ways: Edit the system in the build.prop find qemu.hw.mainkeys = 0 change the 0 to 1 to restart the phone
Link to download
http://pan.baidu.com/s/1jGYfpdG
1: According to the competition regulations to place the file and naming
2: According to the rules without built-root themselves into the brush to
3: L39h and C6902 brush into no signal extraction system \ etc \ firmware \ c6x02 in the documents covering the intake system \ etc \ firmware can restart
What about C6902??
abdo.war said:
Try to flash boot.IMG file
Connect your phone in Fastboot mode by press volume up while connecting to pc
By flashtool or using
Factbook command
Then try to install it
I installed rom from flashfire but it's dangerous
Click to expand...
Click to collapse
whare boot.IMG??
msamsameemo said:
whare boot.IMG??
Click to expand...
Click to collapse
In the Zip file
Rom update to Flyme 4.5.4.5 R
<<Source>>
========================== Change details======================
Change Log | Flyme 4.5.4.5R
Change Log | Common Controls
* Repair: AM, PM call record mode, information sessions and other interface should be in the morning, afternoon issue
Change Log | Desktop
· Fix: probability system user interface restart the phone after being given problem
Change Log | Other
· Optimization: the latest code sync Flyme
[Precautions]
1: need to unlock
Hide virtual key ways: Edit the system in the build.prop find qemu.hw.mainkeys = 0 change the 0 to 1 to restart the phone.
Download:
http://pan.baidu.com/share/link?shareid=3411624397&uk=3845504875
topsecret78 said:
Rom update to Flyme 4.5.4.5 R
<<Source>>
========================== Change details======================
Change Log | Flyme 4.5.4.5R
Change Log | Common Controls
* Repair: AM, PM call record mode, information sessions and other interface should be in the morning, afternoon issue
Change Log | Desktop
· Fix: probability system user interface restart the phone after being given problem
Change Log | Other
· Optimization: the latest code sync Flyme
[Precautions]
1: need to unlock
Hide virtual key ways: Edit the system in the build.prop find qemu.hw.mainkeys = 0 change the 0 to 1 to restart the phone.
Download:
http://pan.baidu.com/share/link?shareid=3411624397&uk=3845504875
Click to expand...
Click to collapse
What's the password?
Abu Badr said:
What's the password?
Click to expand...
Click to collapse
you don't need this link i already uploaded it to google drive go to
download at first post under screenshots
i have uploaded too iuni os if you want i can post it
Click to expand...
Click to collapse
{
"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"
}
Credits: @duraaraa (great guy from Xda), @inside!out, @VirusPlus, HRT Chinese team, Maximo76
1. Download this file
Ver. 1.6 ---------------------------> DOWNLOAD
2. Extract in a directory on your PC Rayglobe_Knife.exe
3. Launch this exe
XDA:DevDB Information
[Tool] Rayglobe Mate 8 Italian Knife, Tool/Utility for the Huawei Mate 8
Contributors
acer73, Inside!out, Virusplus, HRT Chinese Team, Maximo76
Source Code: http://forum.hdblog.it/index.php?/topic/49051-italian-knife-tool-by-hdblogit-huawei-mate-8/
Version Information
Status: Alpha
Created 2016-01-17
Last Updated 2016-02-06
Reserved
HELP
************************************************** ***********************************************
--------- User Manual HUAWEI MATE 8 Italian knife by Raimondo Martire (aka acer73) V1. 2 ----------
*
*
================================================== ========================================
**************The following points can be activated only with ADB and FASTBOOT active
**
*****0: FIRST START
*****1: BOOTLOADER
*****2: Recovery
*****3: Root
*****4: gapps
*****5: debrand
6: UNBRICK
7: EXTRA
8: Download EMUI
9: Thread Huawei Mate 8 on HDBlog.it
**
*****Q: Donate and Thanks? HELP (hdblog.it) X: CLOSE
================================================== ========================================
*
Before you start remember stop/freeze the antivirus because it may interfere with the download
*
================================================== ========================================
*
MENU 0: First Start
*
In this menu, 'there are two preliminary operations are the driver installation
for the proper functioning of the options adb and software download Hisuite.
Remember not to jump the menu '"First start"
because you will need to verify that you have properly enabled the option "USB debugging" in the menu 'developer
*
================================================== ========================================
*
MENU 1: Bootloader
*
In this menu 'you can use a fast tool for a fee ($4) to unlock the bootloader.
Huawei also provides for an option to unlock via email.
More information in this forum
*
NB. Unlocking the bootloader is necessary if you want to use all options of this tool
*
================================================== ========================================
*
MENU 2: Recovery
*
* 2-1 * The recovery TWRP need to install zip unsigned and root.
* 2-2 * The stock is recovery available with Huawei rom
*
================================================== ========================================
*
MENU 3: Root
*
The root, from the English "root", is a process derived from Linux and applied on
Android to get superuser rights and thus have unrestricted access to the system and to
right to modify it at will by real developers.
It is not nothing but to overcome a barrier and open the huge iron gates behind
which hides the world of modding and custom ROMs.
IMPORTANT: For the root must install the TWRP recovery and have the boot decrypt
*
================================================== ========================================
*
MENU 4: gapps
*
You can install Gapps for Huawei chinese rom. Please consider to decrypt boot before
*
================================================== ========================================
*
MENU 5: debrand
*
It really a pleasure to present this function for switch beetween chinese AL10 model to European L29 Model
*
================================================== ========================================
*
MENU 6: UNBRICK
*
It 'a menu' emergency and experimental enabled only when the smartphone is in brick state
*
================================================== ========================================
*
MENU 7: Extra
*
In this menu, 'there are more frequent reboots: recovery, bootloader and the possibility for the user
to flash their own recovery or a boot image. The files must be placed in the directory
USER
*
================================================== ========================================
*
MENU 8: Download EMUI
*
This menu 'will be active for download roms stock EMUI of the Chinese model.
*
================================================== ========================================
*
MENU 9: Thread Huawei Mate 8 on HDBlog.it
*
Italian forum when I've published first my work
*
================================================== ========================================
*
MENU D: Donate
*
This tool and 'released for purely private. Any commercial use without permission
the author will be prosecuted according to law.
If you want to keep this tool active currency the possibility to donate to the purchase of space
Web and to give me comfort with a glass of good Italian wine
*
================================================== ========================================
*
Menu?: Help
*
To choose the menu 'for help and' exclusively in Italian
*
================================================== ========================================
*
MENU X: Close
*
Closes this tool
Changelog
1.5
Smaller exe
Rayglobe Twrp recovery Multilanguage
1.3
New Twrp multilanguage
Remake Extra section with 2 new stuff
thank you for your help
I have a problem against the software does not recognize my mate 8 I have this red message <waiting for device>, and when I run a command prompt my device is recognized without problems
You are the hero we need, we just didn't know it! Massive thanks for your work mate.
lorenzw said:
thank you for your help
I have a problem against the software does not recognize my mate 8 I have this red message <waiting for device>, and when I run a command prompt my device is recognized without problems
Click to expand...
Click to collapse
You have driver problem. Have you used driver that I punt in first start command?
Extensive help please
Just looking for some more detailed help, ill post the issues I have with understanding.
Sorry if some things I ask are basic or stupid, I have never had an android phone and haven't had the opportunity to check your tool out with a phone yet.
acer73 said:
*
MENU 0: First Start
*
In this menu, 'there are two preliminary operations are the driver installation
for the proper functioning of the options adb and software download Hisuite.
Remember not to jump the menu '"First start"
because you will need to verify that you have properly enabled the option "USB debugging" in the menu 'developer
*
Click to expand...
Click to collapse
So I just need to run this command (after enabling USB debugging) and that will download everything I need to run the commands?
acer73 said:
*
MENU 1: Bootloader
*
In this menu 'you can use a fast tool for a fee ($4) to unlock the bootloader.
Huawei also provides for an option to unlock via email.
More information in this forum
*
NB. Unlocking the bootloader is necessary if you want to use all options of this tool
*
Click to expand...
Click to collapse
So whats this first menu do?
Link me to these two places?
acer73 said:
*
MENU 2: Recovery
*
* 2-1 * The recovery TWRP need to install zip unsigned and root.
* 2-2 * The stock is recovery available with Huawei rom
*
Click to expand...
Click to collapse
What do these mean?
TWRP will be installed on it if I select one?
Then what does the stock one do? Remove TWRP?
acer73 said:
*
MENU 3: Root
*
The root, from the English "root", is a process derived from Linux and applied on
Android to get superuser rights and thus have unrestricted access to the system and to
right to modify it at will by real developers.
It is not nothing but to overcome a barrier and open the huge iron gates behind
which hides the world of modding and custom ROMs.
IMPORTANT: For the root must install the TWRP recovery and have the boot decrypt
*
Click to expand...
Click to collapse
How do I get boot decrypt?
acer73 said:
*
MENU 4: gapps
*
You can install Gapps for Huawei chinese rom. Please consider to decrypt boot before
*
Click to expand...
Click to collapse
Once again, what is decrypt boot?
What happens if I dont have decrypt boot and I do this?
Also what GAPPS are included?
acer73 said:
*
MENU 5: debrand
*
It really a pleasure to present this function for switch beetween chinese AL10 model to European L29 Model
*
Click to expand...
Click to collapse
Basically this will flash the european rom on the phone?
Does it work the other way as well, european to chinese?
acer73 said:
*
MENU 6: UNBRICK
*
It 'a menu' emergency and experimental enabled only when the smartphone is in brick state
*
Click to expand...
Click to collapse
So if I brick my phone this will be able to fix it most of the time?
What kind of things does it do?
acer73 said:
*
MENU 7: Extra
*
In this menu, 'there are more frequent reboots: recovery, bootloader and the possibility for the user
to flash their own recovery or a boot image. The files must be placed in the directory
USER
*
Click to expand...
Click to collapse
So this menu gives the user the option to boot into different modes?
acer73 said:
*
MENU 8: Download EMUI
*
This menu 'will be active for download roms stock EMUI of the Chinese model.
*
Click to expand...
Click to collapse
What does this do? Flash the chinese rom?
Does that mean the chinese to international rom wouldnt work backwards, you need to use this one to do it?
So I just need to run this command (after enabling USB debugging) and that will download everything I need to run the commands?
So whats this first menu do?
Link me to these two places?
Install correct adb driver. remember to activate usb debug in developer menu
What do these mean?
TWRP will be installed on it if I select one?
Then what does the stock one do? Remove TWRP?
Twrp in a custom recovery to flash unsigned zip
How do I get boot decrypt?
In menu 3
Once again, what is decrypt boot?
What happens if I dont have decrypt boot and I do this?
Also what GAPPS are included?
Micro GApps package for chinese rom
Basically this will flash the european rom on the phone?
Does it work the other way as well, european to chinese?
Yes european rom work on chinese model
So if I brick my phone this will be able to fix it most of the time?
What kind of things does it do?
So this menu gives the user the option to boot into different modes?
You can boot in recovery or fastboot mode. Some command can be made in recovery mode other one in bootloader mode
What does this do? Flash the chinese rom?
Does that mean the chinese to international rom wouldnt work backwards, you need to use this one to do it?
Yes you can flash from chinese to european and return to chinese
Hello,
I made this tool for Honor6 and inside!out port it for Honor7 later. We both now merged our tools into one HONOR MultiTool and we still keep it "open" in .bat so anyone can use/port it for other models. I don't get why you "close" it with .exe format.
I see that you add me and inside!out as contributors but i don't want make changes into your OP, so please give me and inside!out the right credits of your port on our work into OP and your Tool.
This is the original HONOR6 MultiTool Thread and this is the port for HONOR7 MultiTool Thread.
Thank you!
Hi I know several people have already asked this, but when I run first run I just get waiting for device. In device manager there's no missing drivers. I can't see where you have the adb driver located. Is it possible to post a link to the correct driver? I was able to install hiSuit, but not able to get the device detected. Does anyone have any other ideas?
hisuite actually has the USB drivers included...
davoidd said:
Hi I know several people have already asked this, but when I run first run I just get waiting for device. In device manager there's no missing drivers. I can't see where you have the adb driver located. Is it possible to post a link to the correct driver? I was able to install hiSuit, but not able to get the device detected. Does anyone have any other ideas?
Click to expand...
Click to collapse
I am in the same situation as Davoidd and I still have not found the solution.
I'm on Windows 10 and Hisuite and adb drivers are installed
all orders that I make are not allowed via fastboot with Rayglobe Italian Knife
but I can flash the TWRP via fastboot without using Rayglobe Italian Knife
Can I use your tools for Factory Reset Protection (FRP) rest?
VirusPlus said:
Hello,
I made this tool for Honor6 and inside!out port it for Honor7 later. We both now merged our tools into one HONOR MultiTool and we still keep it "open" in .bat so anyone can use/port it for other models. I don't get why you "close" it with .exe format.
I see that you add me and inside!out as contributors but i don't want make changes into your OP, so please give me and inside!out the right credits of your port on our work into OP and your Tool.
This is the original HONOR6 MultiTool Thread and this is the port for HONOR7 MultiTool Thread.
Thank you!
Click to expand...
Click to collapse
Sorry mate. I created this thread as you can see with right credits in the first time and put your name also in contributors. I put your name in contributors in this way xda system send you an email and you can verify work just because you have choose to not receive Pm so no possibility to contact you. I don't think only to give credit in OP and tool . I'll upload new version with credit in OP according your right desire and I've modified first image for better visibility. :good:
copysat said:
Can I use your tools for Factory Reset Protection (FRP) rest?
Click to expand...
Click to collapse
No, I don't test for it. Use this option only in an emergence fase
jbmc83 said:
hisuite actually has the USB drivers included...
Click to expand...
Click to collapse
Yes right
lorenzw said:
I am in the same situation as Davoidd and I still have not found the solution.
I'm on Windows 10 and Hisuite and adb drivers are installed
all orders that I make are not allowed via fastboot with Rayglobe Italian Knife
but I can flash the TWRP via fastboot without using Rayglobe Italian Knife
Click to expand...
Click to collapse
Yes you can flash in fastboot with this command
fastboot flash recovery twrp.img
I'll see in tool why some user don't flash. Only a test if you wright
adb devices
you see a number?
acer73 said:
Yes you can flash in fastboot with this command
fastboot flash recovery twrp.img
I'll see in tool why some user don't flash. Only a test if you wright
adb devices
you see a number?
Click to expand...
Click to collapse
yes i see a number , with adb in fastboot i can flash twtrp.img with the firmware NXT-AL10_C00B129SP02 I also have with your made tool a backup of oeminfo but with the firmware NXT-AL10C00B137 I can't flash twrp.img ! (failed command not allowed)
At present I am under the firmware NXT-AL10_C00B129SP02 with TWRP and SuperSu
lorenzw said:
yes i see a number , with adb in fastboot i can flash twtrp.img with the firmware NXT-AL10_C00B129SP02 I also have with your made tool a backup of oeminfo but with the firmware NXT-AL10C00B137 I can't flash twrp.img ! (failed command not allowed)
At present I am under the firmware NXT-AL10_C00B129SP02 with TWRP and SuperSu
Click to expand...
Click to collapse
I'll change tool to ver 1.0.0.1 try with this . I'm sure that now you can flash without problem
https://www.androidfilehost.com/?fid=24369303960690339
happy to report that ur tool saved me a lot of work @acer73 im now on L29 firmware with decrypted boot, twrp and supersu installed, everything running smoothly. so far no issues with notifications, but still watching out for this...
Sent from my Huawei Mate 8 using Tapatalk
{
"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"
}
Hello friends,
I am with Flyme 6, which is developed for the LG G2.
It supports all variants.
Supports all languages.
Android version is 6.0.1
How to flash：
1.Flash the CAF boostacks.
2.Root and Flash the bumped twrp recovery.
3.Wipe.
4.Flash the Flyme 6 Rom.
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.4.x
ROM Firmware Required: CAF
Based On: LineageOS
Version Information
Status: Testing...
Current Beta Version: 6.7.7.31R beta
Screenshots :
Screen Video :
https://www.youtube.com/watch?v=ETIHLoGxlVQ&t=80s
Download :
http://openrom-dl.flyme.cn/2771457/20170801/1501602480038/flyme_LG-D802_bise_6.7.7.31R-beta.zip
Good use
and for the gapps and root?
can you provide the proppers gapps and root method?
thank
Sent from my LG-D802 using Tapatalk
---------- Post added at 10:31 AM ---------- Previous post was at 10:29 AM ----------
i have already flash current version but no have idea bout gapps and rooting method
Sent from my LG-D802 using Tapatalk
jpunkers said:
and for the gapps and root?
can you provide the proppers gapps and root method?
thank
Sent from my LG-D802 using Tapatalk
---------- Post added at 10:31 AM ---------- Previous post was at 10:29 AM ----------
i have already flash current version but no have idea bout gapps and rooting method
Sent from my LG-D802 using Tapatalk
Click to expand...
Click to collapse
Gapps and root are not found.
Gapps : opengapps.org ARM/6.0/Pico or Nano
Root : https://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip?retrieve_file=1 Flash from Recovery.
since it base lineage, am i rit? ok thanks bro
Sent from my LG-D802 using Tapatalk
Is it not possible that on android is 7?
(im not speak english - google translate)
its awsome 6.0.1 thanks dev
and for all variant or just 802???
I think you should change the filename to something that doesn't include "d8xx" i almost thought the rom is just for d802 but it includes all vairants and also could you add a translation of aroma to english .(if it's just THAT(aroma) in chinese not the rom XD).
i'm sure everyone will appreciate that
trying the rom now
Huzaifashaikh0012 said:
I think you should change the filename to something that doesn't include "d8xx" i almost thought the rom is just for d802 but it includes all vairants and also could you add a translation of aroma to english .(if it's just THAT(aroma) in chinese not the rom XD).
i'm sure everyone will appreciate that
trying the rom now
Click to expand...
Click to collapse
Could you kindly share how well it works once you tried it ?
Huzaifashaikh0012 said:
I think you should change the filename to something that doesn't include "d8xx" i almost thought the rom is just for d802 but it includes all vairants and also could you add a translation of aroma to english .(if it's just THAT(aroma) in chinese not the rom XD).
i'm sure everyone will appreciate that
trying the rom now
Click to expand...
Click to collapse
Thank you for your thought to change! If you have the opportunity to cast a Screenshot, I will add the subject.
Worth it!
Pag96 said:
Could you kindly share how well it works once you tried it ?
Click to expand...
Click to collapse
At first i thought the performance would be dull because of good appearance but the rom does maintain them both
didn't measure the full battery life but it's better than the stock one's for sure
The sound is pretty low though.(count as a bug ..my speakers are good )
no problem in connectivity the gps is good
thumbs up for the ROM :good:
Try this but stuck on logo screen (ls980)
Aures Batna said:
Try this but stuck on logo screen (ls980)
Click to expand...
Click to collapse
I had the same problem while installing..
I restarted the phone by long pressing the power button(10sec). And then it worked fine after reboot .
I did that on a vs980 though you could try .
Huzaifashaikh0012 said:
At first i thought the performance would be dull because of good appearance but the rom does maintain them both
didn't measure the full battery life but it's better than the stock one's for sure
The sound is pretty low though.(count as a bug ..my speakers are good )
no problem in connectivity the gps is good
thumbs up for the ROM :good:
Click to expand...
Click to collapse
Thank you for your tests, bro
do you have any work arround to change the theme store to english ?
Why we need flash caf bootstack?
Cant i just wipe data and flash rom?
I get random reboots on this ROM model no. D802 and yes you have to wait 20 - 25 minutes for first boot.
---------- Post added at 12:59 AM ---------- Previous post was at 12:58 AM ----------
stalvekio said:
Why we need flash caf bootstack?
Cant i just wipe data and flash rom?
Click to expand...
Click to collapse
because it needs lollipop bootloader. So flash CAF.
I'm on cloudy 3.3 right now.
Do I need to change my bootloader and flash caf or not?
Try it.
Hi, i'm install the rom last day. Device D802TR, stock rom lollipop.
I'm applying root very difficult because first time root my device. Not worked "One Click Root" method. How did i do. Found the how make root and twrp method, using step by step this;
1- Install lg drivers for pc,
and device mount pc usb debugging. OneClickRecovery extract the " C:\1>"
opened the one click recovery folder the cmd.exe
2 -
- C:\1> adb.exe devices -> results my device
- C:\1> adb.exe push busybox /data/local/tmp/ && adb.exe push lg_root.sh /data/local/tmp && adb.exe push UPDATE-SuperSU-v2.46.zip /data/local/tmp
- Unplug usb cable and close phone. Volume Up button press after plug the usb cable
open the phone download mode, and back to cmd screen.
- C:\1> Ports.bat -> device mount com port view.
- C:\1> SendCommand.exe \\.\COM7 (my device com7 port)
- # sh /data/local/tmp/lg_root.sh dummy 1 /data/local/tmp/UPDATE-SuperSU-v2.46.zip /data/local/tmp/busybox
- unplug usb cable and long press power button.Restarting phone and screen message
"upgrading Android" and after 5-10 second showing lg logo screen.
.. And open the phone, install root checker the play store. Open app check,operation succesfully,
my phone is now root.
3 - Install twrp official app, RebootRecovery(qbanin) in phone.
Copying files (caf bootstack, flyme rom, opengapps nano) in device download folder.
twrp application run and agree. And run RebootRecovery application, reboot the device open twrp.
Backup system,data,modem etc. (Making a NANDroid Backup). Reboot and exit twrp(because copying backup files the pc).
Install "root browser" the play store. Copy the files my pc.
again reboot recovery app, device open twrp.
Wipe -> advanced wipe (only dont select internal storage). Back the main menu.
Install -> flymeos file swipe the flash (flashing time maybe less 1.5 minute)
(Note: I did for the first time, i did not add other files. Because i'm beginner.)
Finally finished file flash and show the flymeos installation application.
Language is chinese, only click right bottom text, after again chinese words (me not understand chinese language,
very scary my face), other phone install translate application and take photo translate chinese words,
after a while I saw it for the first time english words.
This sentence "Save log file" and click show chinese text and little chinese word,click word.
This will not happen, and found youtube video.
Watc the video, I'm on the right path. Interesting for me.
Again click bottom right and show the list. Click top words, begin the installation.
install finish and reboot press. Reboot device showing lg logo and show flymeos boot animation.
As for me wait 6-7 minute. And me thinking not opening system, little scary. Because not install caf boostacks file
and opengapps file. But; And the system opening on.
Language selection screen, select lang, finally words I know. Click next,next etc. Start connected without a question.
Close gsm internet connection, select wifi and password (no my language keyboard, CZ and EN, but not found "I, ı").
Continue the installlation and final.
Show Lock Screen, slide the open.Tap to settings (Insist on using chinese applications, of course meizu account).
Anyway do not write more...
Once again install Flymeos. And add file flashing time, rom, gapps, supersu (but not install supersu).
Result ;
# LED Not working (only plug charger orange color working)
# Knock on/ Knock off not working
# Change the Device MAC Adress (interesting)
# GSM LTE very low, usualy lost
# GSM 3G low
# Keyboard Not Support Turkish(for english not char "I and ı" )
# Sometime touch home button restart device.
# Screen button layout do not change, (Back left, middle home, right recent apps) and background
color not chance.(Why no diversity)
# Camera disgrace.
# Sound exit not cool(Even worse)
# Sms message receive (lock screen) show notification and wake up screen, (show buttons read, delete) but buttons not work.
Touch read button notification lost, nothing ! slide and open lock screen but again nothing.Open message box No unread posts.
# Open contacts and 1 number adding Black list, and touch recent apps button, restart.
# Positive action : Moore battery life, this morning %100, take 10 photo and 2 sms write, 2 call (total 4 minute), 8 restart after %91.
Questions :
# Caf boostacks why need ? (Me not flash boostacks)
# Some said it took 20 minutes to installation. (Me 1-2 minute)
# First Boot time 6-7 minute (short or long ? i don't know)
# Why urge use local application (I guess Meizu ports rom)
that's all for now. I think today wipe system, and install LineageOs 14.1 (now downloading files).
dtonkz , this is the best test report i have never seen before here
First boot time 20minutes
Keyboard not change ( change but always rebot)
Battery bad or normal
Permance good
Knock on off not work
Led not work
D 802
Sory my bad English
And sound boost mod https://mega.nz/#!KwJlG...5HxJ4__FiRUvkVMZifbilHU