Database Info

KYOCERA ECHO RECOVERY IMAGE!!!! Full list of Kyocera Echo Tools

First things first, let me give credit where credit is due!
ZergRush - For creating his script to root the echo; and also giving Saridnour the Tools to create is "Kyocera Echo 1-Click" root method.
Saridnour - For his committed work to Hear the Echo (Our Kyocera Echo Website) and creating the recovery image from scratch pretty much!
KyoceraEchoHax - For Advertising the site and helping us to obtain over 200 members in one month (and growing)
Me - For bringing all these random people together
-------------------------------------------------------------------------------------------------
Okay, now to the good stuff
Here is Saridnour's OneClick Root for the Kyocera EchoHERE
The main problem poeple have is the fact that they use USB tethering! YOUR TETHERING MUST BE OFF or this will not work. tethering uses the ADB servers making it unusable while it is active. TURN TETHER OFF!!
Instructions from Saridnour:
Tool will do it all.. You just need to install the Kyocera Echo drivers from their site (links on the tool)
Let me know if you find issue or bugs. I did this pretty quick and hacked out most of it sitting at TacoTime for dinner last night. lol. The FC's drove me nuts until today and think this should be stable for everyone now. No FC's for me in some time. I did the online update as well without issues, but don't reccomend it just yet although the tool can revert you right back if need be.
Usage:
1- Extract files to your computer, open it, and click Rootme.
Thats about it. Follow the steps and you should be golden. And yes.. These will be the driods you were looking for!
-------------------------------------------------------------------------------------------------
Next is Saridnour FULLY FUNCTIONAL recovery image, it has been tested by multiple people and this is the official release! you can get it HERE
Post from Saridnour on the Original Site:
Well at long last, the Recovery Image is now complete and ready for public Release!
.
Thanks to all the donators, beta testers and those who helped this along the way. I will update this as needed to help the install process and give thanks where needed. I was very rushed getting this up as I wanted it out on Halloween.. the ultimate echo treat!! But we all know what happens when we rush..
BUT the file was done and tested prior to so its just the presentation that was rushed
.
A BIG thank you to Na’ven Enigma for sharing some of her websites bandwidth and hosting the files. She wanted to make sure everyone was able to get instant access to the recovery. Please give her a BIG thank you!
.
.
Only known issue is that you cannot mount the device as a usb drive to copy files. This is a common issue with CWM and should have little to no impact as our echo has removable Micro SD cards.
.
.
To install:
-Follow the directions given in the script (IE: Install the drivers from Kyocera for the Echo, Install the driver that is launched from the script (it's not part of the standard echo drivers)
.
- Make sure it is booted to the os and that debug is turned on: (phone settings -> applications -> development -> USB debugging)
.
- Extract the archive to a folder (IE : the Desktop of your computer)
.
- Run the script “SAR_Recovery.bat” (From within the folder noted above ON YOUR PC)
.
- Follow the prompts given, read what it is asking/telling you and take that action (very short and simple)
.
- Exit from the script and you should be done with the upgrade.
.
- Install from the marketplace “Quick Boot” (free) to allow you to boot into recovery as there are no hardware keys known at this time. You can also use ADB if you can’t access the OS, just send this command: ADB reboot recovery.
.
- Backup your device, Find a rom and have FUN!'
.
.
If you can't boot the OS prior to install:
If you can only see the Kyocera bootloader screen and not boot the OS you need to do this another way. Its still easy and you will just need to follows the steps above up to running the script and install the included driver (or from withint the folder you extracted, install the driver) and then connect your device in bootloader mode (Kyocera screen with yellow light on) and from the pc, ope a command prompt, change to the directory that you extraced the files and type this command " Fastboot devices" it should return ??? meaning it can see your device. IF NOT YOU DO NOT HAVE the drivers loaded, are not in bootloader mode, or your usb is not connected [Bad canle/port/etc]). Once it can see your device type "Fastboot flash recovery recovery.img" and it will install CWM. You will then need to run "fastboot boot recovery.img" to boot into recovery. From there you can install your new rom from HTE.
.
.
Note: The whole process takes less than 5 min. If it hangs, has an issue or you are unsure what it did. Give it another couple minutes, pull the plug, reboot and try again. You can not hurt your phone running this as if the install fails or currupts the recovery image, you only need to reboot to the os and the bootloader to correct the issue and this is what this script does to begin with
.
Don’t forget to donate if you find this of use!
.
Enjoy
-------------------------------------------------------------------------------------------------
Now I will ask you all a favor.
So in the last month or so our site (Hear the Echo) has gone from 20 members in the first week to 200+ 3 weeks later. This is great and horrible at the same time. Our bandwidth cannot support 200 people (it wasn't expected to grow so fast). So I please ask you all to donate to HTE and Saridnour. I ask for HTE because we need to expand our Bandwidth because the site has had a minimum of 2-8 members joining DAILY and we cannot hold on much longer (we have about 5 MB left until the site shuts down for the rest of this week, the bandwidth restarts at the beginning of the next month). So PLEASE donate to us. Also, I say Saridnour because I would not be posting right now if it wasnt for his committment and effort for the site. Thank you Saridnour SO MUCH MAN!
Thanks for reading everyone,
Ognimnella (AKA BFG SgtRecon on HTE)

# Bump #
Sent from my PG86100 using XDA App

Great job guys!! I tried to donate, but HTE came up Error and Sardinuor showed the paypal donate, but cannot complete the process. Please check the donation links....

opm said:
Great job guys!! I tried to donate, but HTE came up Error and Sardinuor showed the paypal donate, but cannot complete the process. Please check the donation links....
Click to expand...
Click to collapse
Hey thank you so much for the support, just click the HTE name again and it should be functional! And I will get in contact with Saridnour very soon about finding someway to link his paypal also, again thank you so much

My brother had root with Android 2.2 (z4root method), but the 2.3.4 update caused his phone to not boot up and he got a replacement. Knowing what I know now, I could of used fastboot to flash the recovery.img...
So I'm gonna go try this! Instead of using "Saridnours" method, couldn't we just use this?
Revolutionary - zergRush local root 2.2/2.3 [22-10: Samsung/SE update] - xda-developers
Anyways, I'm gonna try this. So now I can update my old video! lol
http://www.youtube.com/watch?v=cG2DtNAHZR8&hd=1

That if the base of saridnours one click root!
disturb3d1 said:
My brother had root with Android 2.2 (z4root method), but the 2.3.4 update caused his phone to not boot up and he got a replacement. Knowing what I know now, I could of used fastboot to flash the recovery.img...
So I'm gonna go try this! Instead of using "Saridnours" method, couldn't we just use this?
Revolutionary - zergRush local root 2.2/2.3 [22-10: Samsung/SE update] - xda-developers
Anyways, I'm gonna try this. So now I can update my old video! lol
http://www.youtube.com/watch?v=cG2DtNAHZR8&hd=1
Click to expand...
Click to collapse
Sent from my PG86100 using XDA App

AWESOME
Had a few issues with the drivers at first.. But I stepped away, cleared my mind, and tried again and all worked wonderfully! My Echo is now running like a dream!
THANK YOU ognimnella, and Saridnour!! I will donate when I have a little cash to spare!

Kyocera Echo
These are cool phones ! Rock Solid Gorilla glass no scratch surface and can be used as brass knuckles Thanks for root . Now we need some cool roms .Mine is stuck on 2.2.1 stock and will not take the gingerbread update . it would be nice if someone could capture that update and make it our first full flashed rom . You can pick up an echo CHEAP on Ebay . Got mine for 84 bucks and its super fast snapdragon processor and loads of program memory make it a cool toy . STill i had hopes of using it as a Donor Reciever but no luck with Paid Cdma . Hope SOme developers grap these sweet phones .

Android Sooner Single Fastboot Interface wrong platform??
I get "Android Sooner Single Fastboot Interface is the wrong driver for this platform" So what is the right one for the echo. Also when i try fastboot devices I don't get the ??? just another blank space. My device shows up as "Unidentified device or unknown device too. I feel this is the last thing preventing me from un-bricking my phone so if anybody has any can help me i would greatly appreciate it.
I used SAR recovery and i get all the way to the point where I'm in bootloader mode, the amber light is on, and I'm waiting on devices. So I'm out of ideas.

Peezly said:
I get "Android Sooner Single Fastboot Interface is the wrong driver for this platform" So what is the right one for the echo. Also when i try fastboot devices I don't get the ??? just another blank space. My device shows up as "Unidentified device or unknown device too. I feel this is the last thing preventing me from un-bricking my phone so if anybody has any can help me i would greatly appreciate it.
I used SAR recovery and i get all the way to the point where I'm in bootloader mode, the amber light is on, and I'm waiting on devices. So I'm out of ideas.
Click to expand...
Click to collapse
Its been so long since I had this phone idek man. See if you can find saridnour and ask for his help
Sent from my HTC Evo 3D using XDA

I wish that somebody will find the way to flash echo to boostmobile.
Sent from my not Echo using Tapatalk 2 Beta-6

are there any custom ROM
---------- Post added at 01:46 PM ---------- Previous post was at 01:46 PM ----------
could we get a forum?

jamcar said:
are there any custom ROM
---------- Post added at 01:46 PM ---------- Previous post was at 01:46 PM ----------
could we get a forum?
Click to expand...
Click to collapse
Google it
Sent from my PC36100 using Tapatalk 2 Beta-6

Hi, my echo stuck on kyocera logo screen. It was working fine. I tried to update the latest version of android and when it installing it stopped.. then here I am stuck at kyocera logo.. any help?

zerotechservice said:
Hi, my echo stuck on kyocera logo screen. It was working fine. I tried to update the latest version of android and when it installing it stopped.. then here I am stuck at kyocera logo.. any help?
Click to expand...
Click to collapse
Do u know how to use adb and fastboot.?
Sent from my PG86100 using XDA

i got into the HTE part. what next? i have alot of option. I choose reboot echo now.
Now still stuck on kyocera logo

I'm trying but...
I am having to go through cmd to do this and I get as far as "Fastboot Devices" and it says "acess denied". What am I doing wrong?

after installing drivers it stuck on *wating device* have same on both pc, have change usb ports and restar pc, same thing
how can i flash recovery by adb?

Flash Kernel

i have the problem that my sound is to low. i flashed feacore kernel but is not better. i read that a vitaly kernel is better for more higher sound but i dont understand how i install it. There a wrote :
To activate it you need to edit the build.prop file with this :
Code:
debug.gr.swapinterval=0 to build.prop
What the guys mean? Can anyone write a step by step list how i can flash kernel on my KQE stockrom? it seemd that is not the same way like a feacore kernel flash
HHHHEEEEELLLLLPPPPP!!!!!!

asc1977 said:
i have the problem that my sound is to low. i flashed feacore kernel but is not better. i read that a vitaly kernel is better for more higher sound but i dont understand how i install it. There a wrote :
To activate it you need to edit the build.prop file with this :
Code:
debug.gr.swapinterval=0 to build.prop
What the guys mean? Can anyone write a step by step list how i can flash kernel on my KQE stockrom? it seemd that is not the same way like a feacore kernel flash
HHHHEEEEELLLLLPPPPP!!!!!!
Click to expand...
Click to collapse
Ask in your device forum. Anyway for build prop, it is at the system folder and a text file. Find the line that you need to edit and edit it. It its not there, add it.
Sent from my SGH-T959 using xda app-developers app

or has anyone a tip for a kernel which change volume higher which i can flash with odin or cwm or something else. a kernel without change thing in any txt files, only flashing

Goto /system/build.prop and add the line with a text editor. Reboot. That's it.

m_atze said:
Goto /system/build.prop and add the line with a text editor. Reboot. That's it.
Click to expand...
Click to collapse
must i change the kernel before or after this or can i do this anyway

asc1977 said:
i have the problem that my sound is to low. i flashed feacore kernel but is not better. i read that a vitaly kernel is better for more higher sound but i dont understand how i install it. There a wrote :
To activate it you need to edit the build.prop file with this :
Code:
debug.gr.swapinterval=0 to build.prop
What the guys mean? Can anyone write a step by step list how i can flash kernel on my KQE stockrom? it seemd that is not the same way like a feacore kernel flash
HHHHEEEEELLLLLPPPPP!!!!!!
Click to expand...
Click to collapse
to edit build.prop use Notepad++ or a tool from Market to edit it on your phone directly i.e. build.prop Editor then restart phone
usually to flash a kernel you have to enter download/ fastboot mode by a key combination at phone startup and flash it by
Code:
fastboot flash boot boot.img
better is to test the kernel before by this
Code:
fastboot boot boot.img
by this way in case of some problems just restart/remove battery and you revert to previous status (it means the new kernel will boot but never flashes on phone memory)
to work this you need Android SDK and USB drivers
remember : never flash a kernel not made for your phone because of a possible hardware failure
better is to get informed before to do that

ruscan.calin said:
to edit build.prop use Notepad++ or a tool from Market to edit it on your phone directly i.e. build.prop Editor then restart phone
usually to flash a kernel you have to enter download/ fastboot mode by a key combination at phone startup and flash it by
Code:
fastboot flash boot boot.img
better is to test the kernel before by this
Code:
fastboot boot boot.img
by this way in case of some problems just restart/remove battery and you revert to previous status (it means the new kernel will boot but never flashes on phone memory)
to work this you need Android SDK and USB drivers
remember : never flash a kernel not made for your phone because of a possible hardware failure
better is to get informed before to do that
Click to expand...
Click to collapse
what is please the fastboot. i know recovery modus and download modus and what i have to do with this codes????

asc1977 said:
what is please the fastboot. i know recovery modus and download modus and what i have to do with this codes????
Click to expand...
Click to collapse
well take a look here for a tutorial but do not flash anything at this time spend some days searching/ reading about these problems the secret word is search this site has good tutorials for almost everything !

ruscan.calin said:
well take a look here for a tutorial but do not flash anything at this time spend some days searching/ reading about these problems the secret word is search this site has good tutorials for almost everything !
Click to expand...
Click to collapse
ok i taste it and hope i can

So after a lot readings i flashed skyhigh Kernel 1.4d. My Volume is perfekt loud and the System runs :thumbup:
Sent from my GT-I9001 using xda app-developers app

thx for the tip

Has someone a tip for a louder kernel like skyhigh? Its loud but i want louder the sound is good but in navi it can be louder
Sent from my GT-I9001 using xda app-developers app

[GUIDE][CM Port][ MT6589 only] Port CyanogenMod 10.2/11 for all MT6589 devices

@chrmhoffmann compiled first ever CyanogenMod for his Wiko Stairway which is a MT6589 device and made it possible for other MT6589 users to taste CM. Since then many are porting it to their MT6589 device and many are requesting to make a port for their device. So, I have made a guide here to make it easier for them to port themselves. You should give proper credits to respected developers and hit thanks before posting on XDA.
NOTE:I have made a list of already ported CM roms in #2 post below , if your device is not listed there download any of the ported CM rom and follow this guide to port it to your device
This is the guide to port CM 10.2/11 for all MT6589 devices.Read carefully and follow each step correctly otherwise CM won't boot
Tools Required:
1) Archive Manger (winrar,winzip,7zip)
2) boot.img Unpack Repack Tools
http://forum.xda-developers.com/showthread.php?t=1587411(For Linux)
http://forum.xda-developers.com/showthread.php?t=2036528(For Windows)
NOTE:
For CM 11 the same proceedure is followed but the stock boot.img must be having kernel with binder.c patched and SELinux enabled (This feature can be bypassed but binder.c patch is must otherwise CM 11 won't boot)
Guide:
1) First get your stock rom and download any ported CM 10.2/11 rom from #2 post below
2) Get boot.img from your phone(stock rom) and boot.img from downloaded CM-ROM.zip
3) Unpack both of them to get ramdisk and kernel of both.
4) Repack CM's ramdisk and stock kernel (your phone's) to get a new boot.img
5) Extract system folder from your phone(stock rom) and system folder from downloaded CM-ROM.zip
6) Copy and replace these files from stock to CM,
=> /lib/modules/ -> all files
=> /framework/ -> CustomProperties.jar
mediatek-common.jar
mediatek-framework.jar
mediatek-op.jar
secondary-framework.jar
=> Also all the files mentioned in the below link ( A great thanks to Kashifmin for providing this )
https://github.com/kashifmin/android_device_micromax_a116/blob/master/proprietary-files.txt
7) Now take the modified CM system folder and the new boot.img and make a zip archive with normal deflate compression ( are default in 7zip)
8) Open the newly created zip archive and downloaded CM-rom.zip .Now drag and drop the META-INF and file_contexts from downloaded CM-rom.zip to newly created zip archive.
9) Now flash the new zip using recovery (CWM/TWRP)
10) Enjoy !!
CREDITS:
@michfood for his Boot unpack/repack utils for WINDOWS.
@bgcngm for his Boot unpack/repack scripts for LINUX.
@kashifmin for his proprietary-files.txt
@kashifminfor guiding me.
@chrmhoffmann For bringing the first ever CM10.2 for an MT6589 device.
@XpLoDWilD
@Dr-Shadow
OmniROM project.

Available CM port builds for MT6589
CM 10.2 builds:
Wiko Stairway / MMX Canvas 4 (A210) -> http://forum.xda-developers.com/showthread.php?t=2467400
MMX Canvas HD (A116) -> http://forum.xda-developers.com/showthread.php?t=2673367
XOLO Q700/Q700i -> http://forum.xda-developers.com/showthread.php?t=2675963
LAVA 458Q / XOLO Q600 / CROSS A88 -> http://forum.xda-developers.com/and...-cross-a88-t2814034/post54103404#post54103404
CUBOT GT99 / Cherry Apollo / XYZ X1 -> http://forum.xda-developers.com/and...cubot-gt99-t2834832/post54542482#post54542482
CM 11 builds:
Wiko Stairway / MMX Canvas 4 (A210) -> http://forum.xda-developers.com/showthread.php?t=2676086
MMX Canvas HD (A116) -> http://forum.xda-developers.com/showthread.php?t=2676896
ACER liquid e2 v370 -> http://forum.xda-developers.com/showthread.php?t=2766290
MMX Canvas Magnus (A117) -> http://forum.xda-developers.com/canvas-magnus/development/rom-cyanogenmod-11-canvas-magnus-a117-t2790957
MMX Canvas 2+ (A110Q) / Fly IQ450 -> http://forum.xda-developers.com/mic...-2-cyanogenmod-11-port-canvas-2-plus-t2750867
MMX Canvas Turbo (A250) -> http://forum.xda-developers.com/canvas-turbo/development/rom-cyanogenmod-11-canvas-turbo-t2780905
If CM for any MT6589 device is missing here , PM me. I will add here.

i try but always stuck on boot splash, no boot up.. pleash help thanks

Uhm.... I guess I can't port cm10.2 over stock jb4.2.1 rom, right?
I ask because I first looked for cm10.1 to port, but to my surprise, I didn't find any cm10.1 builds for any mt6589 on google.

@polfrank you can port CM 10.2 using stock 4.2.1 rom. First you have to download any CM 10.2 Rom from above and follow guide to port. You can even port above CM 11 Roms if you have a working kernel source for your device
Sent from my iris458Q using XDA mobile app

@limam27 boot loop occurs if 1) boot.IMG is badly repacked 2) any file is missing from your device stock rom which has to be copied to CM ROM as mentioned in the guide. Check them first . Also Check whether you are getting errors during unpack and repack of boot.IMG.
Sent from my iris458Q using XDA mobile app

Hmm, I'm stuck on my brand's splash screen too. I don't get to see the boot animation, and as you mention I get errors during both unpacking and repacking. But it said that the file was copied though.... I 'll search for another way to upack and repack on Google and come back.
Edit: pfff, seems like the only way to do it on windows was the one you provided...

Which CM version you are trying to port ?
If have Linux use unpack scripts to unpack/repack boot.img
Windows always gave me errors.
Sent from my iris458Q using XDA mobile app

4shreyas said:
Which CM version you are trying to port ?
If have Linux use unpack scripts to unpack/repack boot.img
Windows always gave me errors.
Sent from my iris458Q using XDA mobile app
Click to expand...
Click to collapse
I chose the CM10.2 from Wiko Stairway.
Yes, I'm now setting a Virtual Machine with Linux 14. And I'll try the unpack scripts from there. Let's see...
UPDATE:
OK, i ended up doing a clean install of ubuntu.
I upacked both images SUCCESS.
I repacked using stock kernel.img and CM ramdisk folder, SUCCESS.
I Install boot.img through CWMrecovery, it now gets past boot logo(Cubot white screen) but I think that before it would enter bootanimation the screen becomes a weird mass of colours, as if the screen was broken. It lasts for 1 second, then it restarts.
ps. I can successfully go to recovery with power+volUP If i like..
Any ideas?

You should get CM boot animation even if you use stock boot.img but won't boot. Did u correctly replace all required files in rom ? Do a clean one. Check if you can get logcat. Send me the logs
Sent from my iris458Q using XDA Premium 4 mobile app

4shreyas said:
You should get CM boot animation even if you use stock boot.img but won't boot. Did u correctly replace all required files in rom ? Do a clean one. Check if you can get logcat. Send me the logs
Sent from my iris458Q using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I think I used wrong kernel.img. I repacked, will flash soon and come back to report.
EDIT: Are you sure that I have to use the META-INF folder from the CM rom? It gives me status 7 error.... (I also used the META-INF from a rom for my device, unfortunatelly it uses aroma, but it seems to install properly..)
EDIT2: I think that now I repacked the correct components of boot.img. It seems to get past the Cubot white splash screen, but after this, I get a black screen, but I can see that the screen is on, I can see the backlight. [I will try again with the CM META-INF-->still fails]
ps. Seems like I have to learn how to get a logcat if I wanna make use of your help... I'll be back in some hours.
----------------------------------------------------------------------
To sum up:
I have packed the new boot.img and replaced the needed files in the rom.
1) With the CM's META-INF folder I can't install, status 7 error.
Finding update package...
Opening update package...
Installing update...
assert failed: getprop("ro.product.device") == "stairway || getprop("ro.build.product") == "stairway"
E: Error in /sdcard/experiment/cm102last.zip
(Status 7)
Installation aborted.
Click to expand...
Click to collapse
2) With the stock rom's META-INF it seems to install propperly.
After reboot from recovery it goes to a black screen and stays there. I tried to logcat (adb logcat -v long > port.txt) but it just says:
[email protected]:/home/pol/Documents/sdk/platform-tools# adb logcat -v long > port.txt
- waiting for device -
Click to expand...
Click to collapse
If i write adb devices it says :
[email protected]:/home/pol/Documents/sdk/platform-tools# adb devices
List of devices attached
0123456789ABCDEF offline
Click to expand...
Click to collapse
When I am on recovery I get:
[email protected]:/home/pol/Documents/sdk/platform-tools# adb devices
List of devices attached
CWM-ZTE-V967S recovery
Click to expand...
Click to collapse
---------------------------------------------------------------------------------------------------------------
CONCLUSION: I managed to install the new boot.img and rom but it stops on a black screen, right after it passes from the white logo screen. And now, I need your ideas...
ps. I repeated the porting process from the beginning to make sure that I didn't make any mistakes... again, the same result.
--------------------------------------------------------------------------------------------------------------
NEW UPDATE: IT BOOTED!! but how....? Here it is........
I just replaced the boot.img from the wiko stairway flashable zip with the boot.img I created with repacking my phone's kernel and CM's ramdisk.
SO, I just changed the boot.img !!!! Testing.......
-------------------------------------------------------------------------------------------------------------
Testing results: buggy mobile network and sound not working. I guess this is why all those files are needed to be copied. I think I ll start copying..... But I wonder...what did I do wrong earlier while copying,,,?

You will get status 7 error because it is a security feature which doesn't allow to flash one device's ROM to other. You have to edit using any text editor and remove first line in the update-script found in meta-inf/com/Google/android/
Also don't use other rom's meta-inf as they have different symbolic links which may not boot the device.
Your phone's modules will be different from wiko's. That's why you got buggy audio and network. Replace all the mentioned files.
sent from my iris458Q using XDA mobile app

Okay, after some hours of trial and error I copied all the porting files provided in the op, except 2:
-libjpeg.so - When I port this from stock, Cm boots, but cannot show images, every single image, including the bootanimation is black.
-libmedia.so - When I port this from stock, Cm stays in the bootanimation forever. (No bootloop, just bootanimation forever)
-------------------------------------------------------------------------------------------------------------------------------------
The "extra" bugs that I have are:
1. No sound from the speaker (but yes in the headphone).
2. Weak signal. I don't know if this is normal. It has 1 bar and sometimes it has 0 and says no service. Also, the name of the tile in the QuickSettings is 20201 (weird...). I also get a message when the rom boots and it says: "Restricted Access changed. Data service is blocked." This appears sometimes at random too.
3. USB storage doesn't work through Android.... ( I don't know if this is normal too). When I plug it on PC it just charges. (Note: I now see that other devices have this problem too. I found a partial workaround in the MMX Canvas HD cm10.2 section)
PS. Would logcat help in any of these problems?
--------------------------------------------------------------------------------------------------------------------------------
I moved on, and took some adb logcats.
1. I took the audio.txt as follows: started logcat, pressed play on the apollo widget, pressed pause, stopped logcat
2. I took the signal.txt as follows: started logcat (while on Airplane mode), disable Airplane mode (from quickSettings tiles), enable mobile data, disable mobile data, enable Airplane mode, stop logcat

I'll look at logs meanwhile I never had problem with signal, speaker audio and images. To get USB storage working add these lines to build.prop and reboot
persist.sys.usb.config=mass_storage,adb
persist.sys.usb.config=mtp,adb
For signal issue , did u replace your modem.IMG in CM ROM ?
For image issue try those 2 files from wiko ROM.
Edit:
Try to freshly port CM once again as given in guide with some changes in meta-inf and build.prop as I gave. If you still have problems then report here.
I couldn't debug audio log but in signal log > network is disconnected as data is enabled and even it's saying messaging settings are false. There may be issue with modem.img
sent from my iris458Q using XDA mobile app

Thanks for the USB storage tip. At least the internal SD can be seen now by the computer.
Images are OK now with the lib of CM.
For signal issue I copied modem.IMG from stock into the CM rom, and still having problems.
Btw, I just created a new thread for my device, I hope this is not a problem.
http://forum.xda-developers.com/and...cubot-gt99-t2834832/post54542482#post54542482

Cheers !! I'll add your device in the ported list. As I said previously all necessary files should be replaced in CM to be bug free except major BT,camera,hwcomposer,FM,GPS,2nd Sim bugs.
Also USB storage is buggy now as SD card is unmounted in mass storage mode but not mounted on PC and when disconnected from PC it doesn't get mounted and you have to reboot to get it working on android. Also mtp mode sometimes doesn't work
sent from my iris458Q using XDA mobile app

Nice!
The only file missing is /lib/libmedia.so and I 'm starting to think that this may be the cause of the sound bug. But when I copy it from the stock rom, I get boot problems...
Anyway, thanks for your help, and sorry that I messed up/spammed your thread. I think the most important part of the job is done..! Good job!
EDIT: I think I sort of fixed the mobile network issue. I used a modem.img from another version of stock rom and it seems to work. However I still get the error "Restricted Access changed. Data service is blocked." But I have full signal and 3G! It's something!

Restricted access notification occurs if you enable or disable data and turn on/off airplane mode and phone and it is not a issue I think. It may be cyanogenMod's security message or something.
Also try libmedia.so from other
Stock rom which you said above.
sent from my iris458Q using XDA mobile app

thanks for repley
4shreyas said:
@limam27 boot loop occurs if 1) boot.IMG is badly repacked 2) any file is missing from your device stock rom which has to be copied to CM ROM as mentioned in the guide. Check them first . Also Check whether you are getting errors during unpack and repack of boot.IMG.
Sent from my iris458Q using XDA mobile app
Click to expand...
Click to collapse
I want to port my device MT6589T JB 4.2 to cm11 kitkat but I do not know how to activate the binder c in the boot.img.
I've tried without a binder c install process always aborted status 7
please help thank you

Hello @limam27
@Iimam27 said:
I want to port my device MT6589T JB 4.2 to cm11 kitkat but I do not know how to activate the binder c in the boot.img.
I've tried without a binder c install process always aborted status 7
please help thank you
Click to expand...
Click to collapse
You can't patch binder.c from boot.IMG. You must be having kernel source for your device and you must patch binder.c in kernel. If you don't have kernel source then its almost impossible to get KitKat. See if your device clones have kernel source for their device. Else look for almost similar specs device with same processor. My device has mt6589m but no source from vendor. I used similar mt6589m device's source to build kernel. Now CM 11 is booting but no display due to different GPU config. So it's really hard if you don't have source. Try with CM 10.2 first .
EDIT- Previously I have told why you get status 7 error. So read whole thread before posting here. Good luck
Sent from my iris458Q using XDA Premium 4 mobile app

[RECOVERY]TWRP 3.1.0.0 - FIsH for FLEX 2

TWRP 3.1.0.0 with FIsH for our FLEX 2
Tested on h955 and it's still a BETA
Requirements
Here are the pre-requirements you have to met!
If you can't get them: Close this page and FORGET it (until the day you met those reqs)!
Here are the 2 simple requirements you have to met:
1. root by SuperSU >=v2.76 (greater or equal v2.76)
--> to test this requirement just start the installer of FIsH with --check (see next lines) which will check for all requirements and abort if its not possible
--> for many devices - if not all - this means you HAVE TO downgrade/install LL. It also means that you have to upgrade your SuperSU to this version by e.g. FlashFire if you have a lower version installed!
--> SU by phh is NOT supported => It needs a modified /boot and this would void the boot signing chain!
--> Magisk is NOT supported => It needs a modified /boot and this would void the boot signing chain!
--> I will NOT provide downgrading guides there are plenty of them so search and read.
--> I will NOT provide any guides in rooting your device
--> Before you think about downgrading to LL read about ANTI-ROLLBACK protection some devices and may have! Anti-Rollback means you CAN NOT downgrade - it would HARD-BRICK your device (wtf thinking the vendors who we are?? Is this even legal?!)! Check that before!!
2. you have to be able to disable SELinux in your booted Android
--> You do NOT need to set SELinux permanently to permissive. Just CHECK if you COULD get it MANUALLY. If you can get it OK. If not.. you obviously have not full root access but check the forums maybe there is something you can do about this.
--> I will NOT provide any guides enabling SELinux but some lines later you will see how u can execute the very simple check
--> to test this requirement just start the installer of FIsH with --check (see next lines) which will check for all requirements and abort if its not possible
Those above are hard facts so it may NEVER work with MM. Google has changed the way on how the boot chain will be verified and that means changes in /system will void it from now on.
If MM can get fully rooted somehow/somewhen on your device with SuperSU installed and you are able to disable SELinux the method will work there as well.
If you can not meet ALL of the above 2 requirements lay down and cry.
For the others: calm down and read on!
You can simply test those both requirements by downloading the FIsH package and execute the installer with the following test parameter:
./install.sh --check
This way nothing get installed but you will see if it would work on your device or not.
Limitations!
Keep in mind what I said above: FIsH does NOT unlock your bootloader!
That means with TWRP-in-FIsH you can NOT:
Install a custom ROM like CM/Lineage (this will modify boot = SOFT-BRICK)
Install a custom Kernel (this will modify boot = SOFT-BRICK)
Install a custom recovery (this will modify recovery = may SOFT-BRICK)
In short: do nothing which modifies boot or recovery partitions. Those changes will BREAK your boot signing chain.
You can of course flash everything which is modifying /system /data only (e.g. xposed, Audio mods, etc...)
You're able to backup and restore as well of course and doing any other modifications which you may can't while the Android system is running.
Download
READ THE REQUIREMENTS above before proceeding!
Then UNDERSTAND the requirements before proceeding! <-- omg this is crucial important!!!! Ensure that you really do not skip this step!
READ THE LIMITATIONS above before proceeding!
Then UNDERSTAND the limitations before proceeding! <-- omg this is crucial important!!!! Ensure that you really do not skip this step!
... and NEVER ask for ETA's!
if you can say:
Yes! I have read and totally understood the limitations AND the requirements!
then proceed. Otherwise read again until you got it.
Keep in mind that this is a HACK. It may soft-brick your device. you have been warned!
The concept is the same for all models but again no guarantees here for anything.
There is ALWAYS a risk and you should better backup what you do not want to loose before starting downloading this.
Download
Installation (Linux)
You can just install any newer version over an old one.
boot Android and connect USB cable
download the newest version to your PC and open a terminal in that directory
tar xzf TWRP-in-FIsH*.tgz
cd android_FIsH
./install.sh
check the output of that script. you should not see any errors there (hopefully)
Installation (Windows)
use FWUL or be patient.. maybe i or someone else release an installer... maybe...
First run (no PC required)
This FIsH gets installed PERMANENTLY! That means:
You can boot up TWRP the same way as described here again without re-installing.
If you re-install your STOCK image you have to re-install TWRPinFIsH as well.
reboot Android
you should now see: LED goes from blue to GREEN
NOW directly when u see this GREEN LED press VOLUME DOWN and do NOT release
wait until the device vibrates and the LED changed to RED. Then release the Volume Down button.
Wait until FIsH completed and TWRP should be shown --> This means FIsH has done it's job well!
This is a good time to do a full backup isn't it ? Manually mount the SYSTEM partition as it gets not auto mounted atm and do a full backup
reboot from here (safely ignore the msg "no OS installed" and reboot anyways) and you should see Android booting (hopefully ... if not see bottom)
Daily Usage (no PC required)
reboot Android
you should now see: LED goes from blue to GREEN
NOW directly when u see this GREEN LED press VOLUME DOWN and do NOT release
wait until the device vibrates and the LED changed to RED. Then release the Volume Down button.
Wait until FIsH completed and TWRP should be shown --> This means FIsH is doing it's job still very well
AGAIN: keep your mind up! You HAVE to ensure that whatever you do and whatever you flash -> NEVER TOUCH BOOT/RECOVERY! If you flash a ZIP ensure first that it do not modify them! Otherwise you WILL softbrick. You have been warned (several times now)
Trouble / Bootloop fix
if you encounter a bootloop (should never happen but who knows) you have 3 choices at least:
Option 1a: (TWRP-Bootloop) Within TWRP open Advanced -> File Manager -> Goto: /system/su.d and click "select" button -> Delete
Option 1b: (TWRP-Bootloop) From your PC: adb shell rm -rf /system/su.d/
Important: Catch the fish log (see next topic)
Option 2 (this works also for a bootloop without twrp): boot into download mode and use LGLaf to get a shell
then:
setenforce 0 <-- if that doesn't work you may have to do a FULL restore to stock
mount -oremount,rw /system
rm -rf /system/su.d/
reboot. You are out of the bootloop.
Important: Catch the fish log (see next topic)
Option 3: Last resort: Reflash STOCK. sorry.. there is always a risk..
Catch the FIsH logs
when in TWRP (or other ramdisk providing adb shell):
adb shell "cat /cache/fish/fish.log"
adb shell "cat /tmp/recovery.log"
OR - when in Android:
adb shell "su -c cat /cache/fish/fish.log"
adb shell "su -c cat /cache/fish/fish.log.old"
adb shell "su -c tar cvzf recoverylogs.tgz /cache/recovery"
adb pull recoverylogs.tgz
Upload the output to https://paste.omnirom.org and paste the link in the IRC channel (see next topic)
Support / IRC Channel
IRC means Internet Relay Chat and you will get best support here only.
Choose how to get in:
PC (HexChat and Pidgin are only 2 of them! This list is not complete!)
Android (Yaaic, AndChat, HoloIRC, AndroIRC are only a few of them! This list is not complete!)
Web (KiwiIRC-Web,FreenodeWebchat])
When you have to choose a channel it is: #Carbon-user
When you will be asked for a server network choose: freenode
Known issues (may never get fixed)
Due to the fact that FIsH is a BRUTAL hijack of the booting process several things may not work as expected.
This will normally not harm anything but you have to know about.
ZIP / ROM flashing:
omg really you wanna hear that again? OK: DON'T TOUCH BOOT / RECOVERY. And you be safe.
When you try to install a ROM it will modify at least BOOT. That means soft-brick!
When you try to install a custom Kernel.. omg really? It will definitively SOFT-BRICK! Maybe you should read the limitations again??
When you try to install a ZIP like xposed, supersu, Vipermod and others ensure that those are not modifying BOOT or RECOVERY partitions. For those mentioned it would be very unlikely but who knows.
FIRMWARE partition:
cannot be mounted - even not manually. You have to live with it.
Double Tap to wakeup (in TWRP):
Unfortunately this cannot work in TWRP-in-FIsH due to the nature of this hijack. You have to live with it.
Credits (without them - no FIsH!!!)
If you feel that someone / you is missing on this list lemme know!
Chainfire for SuperSU! This is the main part of FIsH.
TeamWin for TWRP
@cray_Doze, @dssmex, @Aaahh and @KeiranFTW for their hijack implementations (e.g. https://forum.xda-developers.com/showthread.php?t=2608408, first steps to a G4 hijack)
steadfasterX for the android FIsH !
Here is the h955 device tree for building TWRP with omnirom minimal sources - https://github.com/jarno83/android_device_lge_h955
Here are TWRP logs from backups and restoring if anyone interested - https://github.com/jarno83/twrp_logs

Changelog
29.04.2017 - TWRP-3.1-in-FIsH-v2.0_LGFLEX2_LL_BETA3.zip
Latest FIsH source code and fixes.
3.04.2017 - TWRP-3.1-in-FIsH-v2.0_LGFLEX2_LL_BETA2.zip
Fixed the RESTORE issue - thanks to SteadfasterX
Used latest FIsH source code.
Went to zip format, now a pit smaller.
2.04.2017 - TWRP-3.1-in-FIsH-v2.0_LGFLEX2_LL.tar.gz
The fishfood is TWRP 3.1.0.0 it uses 15c stock kernel for now. And has a problem with restoring.

What is TESTED
BACKUP and RESTORING /system and /data partitions - OK
Xposed V87 - flashes ok with twrp and works - http://dl-xda.xposed.info/framework/sdk22/arm64/
Tested Device List
H955 running 5.1.1 15c ROM
H950 running 5.1.1 PR ROM - thanks to iDefalt

Congrats
Have you seen the XDA template for FIsH?
https://forum.xda-developers.com/an...ack-to-boot-want-device-t3578373/post71567825
.
Sent from my LG-H815 using XDA Labs

steadfasterX said:
Congrats
Have you seen the XDA template for FIsH?
https://forum.xda-developers.com/an...ack-to-boot-want-device-t3578373/post71567825
.
Sent from my LG-H815 using XDA Labs
Click to expand...
Click to collapse
Ok, thanks Didn't saw that

So anyone tested it yet ? TWRP booting ?
I have my phone in repair center atm cant test anything.

Yes, I have it on my h955 and twrp boots fine. I tested system backup and restore, now working. Flashed xposed also ?
Sent from my LG-H955 using XDA-Developers Legacy app

/data backuped and restored with success ?
Sent from my LG-H955 using XDA-Developers Legacy app

Ok so now what? What is the next step? On road To install custom rom or custom kernel.

dadaa1 said:
Ok so now what? What is the next step? On road To install custom rom or custom kernel.
Click to expand...
Click to collapse
SteadfasterX is developing some stuff... so maybe on day we will have a possibility to use full custom roms.
But for now we have a custom recovery
If someone is willing to cook something interesting that can work with not touching the boot or recovery partitions... then well I would call it a custom rom

In theory it should work on a H950PR? So I can at least test it

maucvs said:
In theory it should work on a H950PR? So I can at least test it
Click to expand...
Click to collapse
Hi, I think it will work. You'll need to be rooted and You can give it a try ?
Sent from my LG-H955 using XDA-Developers Legacy app

It should work..
I already tried this on h950 but there is dead android with red '!' ..
For some reason it wont boot into the fishrecovery and goes to the recovery partition..
Ill try smth when i have time.

adds08 said:
It should work..
I already tried this on h950 but there is dead android with red '!' ..
For some reason it wont boot into the fishrecovery and goes to the recovery partition..
Ill try smth when i have time.
Click to expand...
Click to collapse
Seams like the twrp I build is not liking h950
Sent from my LG-H955 using XDA-Developers Legacy app

I'll try to make h950 tree and build a test twrp.
Sent from my LG-H955 using XDA-Developers Legacy app

adds08 said:
It should work..
I already tried this on h950 but there is dead android with red '!' ..
For some reason it wont boot into the fishrecovery and goes to the recovery partition..
Ill try smth when i have time.
Click to expand...
Click to collapse
Can you test this... made a h950 test tree. The twrp boots on my h955 also.

ergo911 said:
Seams like the twrp I build is not liking h950
Click to expand...
Click to collapse
I had a similar issue for the g4 and here it was FIsH because it was too slow for some devices . I will release a new FIsH release which improves speed dramatically asap.
.
Sent from my LG-H815 using XDA Labs

Thanks ?

ergo911 said:
Thanks ?
Click to expand...
Click to collapse
Ok so please use git pull to get the latest updates!
Lemme know if you have any trouble.
.
Sent from my LG-H815 using XDA Labs

ergo911 said:
Can you test this... made a h950 test tree. The twrp boots on my h955 also.
Click to expand...
Click to collapse
Works like a charm on my H950. Thanks! The only issue is TWRP booting time, but it's should be right that, if I understand correctly.
Thank you!

[ROM] Unofficial LineageOS 16.0 PQ3A.190801.002] for ZTE Blade S6 (P839F30)

Code:
[I]DISCLAIMER[/I]
[COLOR="red"]Do not mirror my builds![/COLOR] Please post a link to this thread instead.
All information and files — both in source and compiled form — are provided on an as is basis.
No guarantees or warranties are given or implied. The user assumes all risks of any damages
that may occur, including but not limited to loss of data, damages to hardware, or loss of
business profits. Please use at your own risk. Note that unless explicitly allowed by the
warranty covering your device, it should be assumed that any warranty accompanying your
device will be voided if you tamper with either the system software or the hardware.
Introduction
This is my unofficial build of LineageOS 16.0 for the ZTE Blade S6 aka P839f30.
This is the first alpha release, so be aware that issues could arise.
I have tested this version with my AS variant device. Other variants have to be tested.
Click to expand...
Click to collapse
Features
working:
phone: calls, sms, data.
wifi
bluetooth
sensors
gps: mostly I have used the energy saving mode
sound
camera: rear with flash and front.
torch
headphone detection
swap back and menu button
light: button backlight, brightness control and adaptive brightness, breath light (notification and/or battery)
not working:
SELinux is permissive.
We have to test to find out.
Click to expand...
Click to collapse
Installation instructions
It is best to have installed the latest stock rom beforehand, so modem and all other vendor stuff is up to date.
If you like you can use this mod to have a unified data partition, please proceed with caution.
You will need TWRP or any other custom recovery.
Reboot into recovery and do a nand backup.
Do a factory format.
Download Rom and put it on your phone or use adb sideload.
Install the rom and then clear cache and dalvik cache.
optional: install su and/or gapps (preferable pico).
Click to expand...
Click to collapse
Changelog:
25.05.2021 - new release:
los security patch level 05.05.2021
revert some kernel changes from the last release
add some cpu governors and cpu hotplug
now with Boeffla WakeLock Blocker and other things
wireguard kernel support
22.12.2019 - 1st beta release:
los security patch level 05.12.
kernel supports EU device variant
add autosmp hotplug
add cpu governors blu_active, darkness, lionfish and relaxed
Revert CwMcu sensor driver from SU6 kernel release
24.10.2019 - 2nd alpha release:
los security patch level 05.10.
CwMcu sensor driver from SU6 kernel release, with wake lock disabled
wifi mac is loaded anyway, remove the loading in the wifi driver
give bluetooth a null mac address, to overcome force close error
kang gps from oppo
04.10.2019 - 1st alpha release:
los security patch level 05.09.
initial release of pie
Click to expand...
Click to collapse
Downloads
new release - 25.05.2021:
Google Drive.
first beta release - 22.12.2019:
Google Drive or here.
second alpha release - 24.10.2019:
Google Drive or here.
first alpha release - 04.10.2019:
Google Drive or here.
If you want root use the lineage addon package found here - download arm version.
Install it after flashing the rom or download your favourite root package and install it.
Click to expand...
Click to collapse
Sources
device
msm8916-common
vendor
kernel
Click to expand...
Click to collapse
FAQ
Here you will find some answers to common question which could arise.
Q: How to give root access to an app or adb?
A: First install the su extra package from Lineage OS or any other su tool you like. Then go into settings and about device, click there multiple times on the build number until you unlocked the developer options. Go to developer options and look for root access.
Q: I thing I found an issue, what to do now?
A: Do a logcat or grab a dmesg while having the issue, otherwise we can't say what is happening. Report as much info as possible. Quote your stock rom your device shipped with or which device variant you possess.
Click to expand...
Click to collapse
Thanks To/Credits
Code:
*aquaris-dev team
*aymende7
*PacMM79
*LineageOS team
*many others
XDA:DevDB Information
Unofficial LineageOS 16.0 [PQ3A.190801.002] P839F30, ROM for the ZTE Blade S6
Contributors
lightwars
ROM OS Version: 9.x Pie
ROM Kernel: Linux 3.10.x
Based On: LineageOS 16.0
Version Information
Status: Beta
Current Beta Version: 20191213
Beta Release Date: 2019-12-22
Created 2019-10-04
Last Updated 2019-12-22

many thanks for the new version, i will tested later :good: :highfive:
Hello, works on my ZTE Blade S6 Plus (p839f50)
but only with a fixed updater-script
from Folder: lineage-16.0-20191002-UNOFFICIAL-p839f30.zip\META-INF\com\google\android
the bold text must delete and than save the file
after the start my phone , i have a error message with bluetooth is deactivated
updater-script - original
https://filehorst.de/d/crqjwnjI
updater-script - fixed
https://filehorst.de/d/cbmctorj

new update is in the op.
just small changes and updated security patch level.

Anybody tested with EU device?
... at the moment no time to test myself (to much effort to keep my other devices up-to-date ), just wanted to ask if anybody already tested on EU device (and forgot to post ).
Gtz
Kurt

Kurt Krummbein said:
... at the moment no time to test myself (to much effort to keep my other devices up-to-date ), just wanted to ask if anybody already tested on EU device (and forgot to post ).
Click to expand...
Click to collapse
Answer my own request, gave it a try, didn't boot, screen stayed black and device went into fastboot-mode ... restored my nandroid-backup of stock-EU-B15 .
Next time, i format system and just install rom without gapps and addon-su.
Gtz
Kurt

Kurt Krummbein said:
Answer my own request, gave it a try, didn't boot, screen stayed black and device went into fastboot-mode ... restored my nandroid-backup of stock-EU-B15 .
Next time, i format system and just install rom without gapps and addon-su.
Gtz
Kurt
Click to expand...
Click to collapse
Hello Kurt,
please, if you find the time to do another test. Download the attached zip extract the boot.img and copy it to your device, flash it with twrp right after installing the lineage zip through twrp. report back if something different happens.
I splited the dtb from the zImage and attached the almost stock eu dtb, so maybe we are lucky. But I have not find any big differences in analyzing the dts of EU vs AS and kernel defconfigs EU vs AS.
I can show this files too, if somebody has a better understanding of this.

lightwars said:
Hello Kurt,
please, if you find the time to do another test. Download the attached zip extract the boot.img and copy it to your device, flash it with twrp right after installing the lineage zip through twrp. report back if something different happens.
I splited the dtb from the zImage and attached the almost stock eu dtb, so maybe we are lucky. But I have not find any big differences in analyzing the dts of EU vs AS and kernel defconfigs EU vs AS.
I can show this files too, if somebody has a better understanding of this.
Click to expand...
Click to collapse
Hi!
Well, i loaded the def's and config's into WinMerge and did a compare ... in the def's there are some different addresses, but i have now clue what the meaning of that all is :angel:. The config files look like beeing from different kernel versions, there are some options which don't exist in both, one is modularised, the other is not ... all in all quite strange.
Ok, i made a try with the boot_eu.img:
- Made a factory reset
- Flashed the LOS.zip
- Wiped caches
- unzipped the boot.img
- copied it to boot partition with dd if=boot_eu.img of=/dev/block/bootdevice/by-name/boot
- reboot
... screen goes black, one buzz .... nothing. One the PC the fastboot device appears and that's it. I was looking for tombstones, but couldn't find any ... they are stored to /data/tombstones, are they? I'm not sure, the kernel i getting up high enough to mount /data.
Cheers
Kurt
P.S.: one thing i forgot to mention ... i coulnd't find the "OEM unlock" swich in the stock system anywhere and the bootloader seems to be quite dumb, many commands from fastboot just end in a "command unknown", perhaps there's something left to do on my side (tweak in build.prop etc ... googleed for it no result ).

Kurt Krummbein said:
Ok, i made a try with the boot_eu.img:
- Made a factory reset
- Flashed the LOS.zip
- Wiped caches
- unzipped the boot.img
- copied it to boot partition with dd if=boot_eu.img of=/dev/block/bootdevice/by-name/boot
- reboot
... screen goes black, one buzz .... nothing. One the PC the fastboot device appears and that's it. I was looking for tombstones, but couldn't find any ... they are stored to /data/tombstones, are they? I'm not sure, the kernel i getting up high enough to mount /data.
Click to expand...
Click to collapse
Thanks for testing. You used the reboot system button of twrp I guess. Have you tried to reboot by pressing the power button?
I can think of two things: There is some flag in the kernel source which is called download_mode. I have seen that some devices have different default values! At the moment the value is 0, devices like the ones from bq with msm8916/msm8939 used this too, but devices from oppo with msm8939 uses a value of 1 as default. We can try this one.
Or there is a mask, which defines the restart reason so to speak says the device which mode to boot to. Here we have some differences in the meaning of the bits, a different bit shifting is used.
I can not really think that one of these causes your device to boot into download mode, because the recovery uses the same kernel on both region variants...

lightwars said:
Thanks for testing. You used the reboot system button of twrp I guess. Have you tried to reboot by pressing the power button?
I'll give that one a try .
Hope my device is not "going over the Wupper" LOL (this one has to come somewhen ...)
Click to expand...
Click to collapse
Ok, tried it ... same result. Then did a (perhaps a bit wired) test, just restored boot from my nandroid-backup. With this, the white ZTE bootscreen comes up and after some seconds it reboots to twrp.
Perhaps the dumb-bootloader refuses to boot with AS keys ... otherwise it wouldn't boot recovery. Strange puzzle.
Cheers
Kurt

Kurt Krummbein said:
Ok, tried it ... same result. Then did a (perhaps a bit wired) test, just restored boot from my nandroid-backup. With this, the white ZTE bootscreen comes up and after some seconds it reboots to twrp.
Perhaps the dumb-bootloader refuses to boot with AS keys ... otherwise it wouldn't boot recovery. Strange puzzle.
Cheers
Kurt
Click to expand...
Click to collapse
It is okay to do some unusual testings. I was doing this sort of things also, back then.
I'm not sure I get you, when you write about AS keys. Do you mean the fingerprint in the build.prop? I think I used the ones from the eu version. Maybe they build in some kind of kernel version check inside the bootloader, but only for the eu and other versions.
The cause is, that android needs an advanced kernel, so we can not use the stock kernel to boot newer android version like nougat, oreo or pie.
Sorry, I can not be of much help here, because I do not have a device with eu or some other region version. But we can try do some changes, if you like to do some more testing and maybe get something like a log, last_kmseg or ramoops. We should look to activate some of them.

Hello @Kurt Krummbein,
if you find the time please post the info you get by issuing this commands in the adb shell or on your phone in a terminal:
Code:
su
cat /sys/zte_board_id/board_id
cat /proc/device-tree/model
cat /proc/device-tree/compatible
Do this on your rom or stock rom you are using a the moment. Thank you.
For reference mine output is this:
Code:
Blade-S6:/ # cat /sys/zte_board_id/board_id
wrbA
Blade-S6:/ # cat /proc/device-tree/model
Qualcomm Technologies, Inc. MSM 8939 MTP
Blade-S6:/ # cat /proc/device-tree/compatible
qcom,msm8939-mtp qcom,msm8939 qcom,mtp
It could be that the eu variant uses another device tree inside the kernel, because the bootloader request that, but we have only this model available.

lightwars said:
Hello @Kurt Krummbein,
if you find the time please post the info you get by issuing this commands in the adb shell or on your phone in a terminal:
Code:
su
cat /sys/zte_board_id/board_id
cat /proc/device-tree/model
cat /proc/device-tree/compatible
Do this on your rom or stock rom you are using a the moment. Thank you.
For reference mine output is this:
Code:
Blade-S6:/ # cat /sys/zte_board_id/board_id
wrbA
Blade-S6:/ # cat /proc/device-tree/model
Qualcomm Technologies, Inc. MSM 8939 MTP
Blade-S6:/ # cat /proc/device-tree/compatible
qcom,msm8939-mtp qcom,msm8939 qcom,mtp
It could be that the eu variant uses another device tree inside the kernel, because the bootloader request that, but we have only this model available.
Click to expand...
Click to collapse
Mine is:
cat /sys/zte_board_id/board_id
wrbA-EUROPE
cat: /proc/device-tree/model: No such file or directory
cat: /proc/device-tree/compatible: No such file or directory
ls /proc/device-tree
/proc/device-tree: No such file or directory
Attached my build.prop ... perhaps this sheds some light .
Thx
Kurt

Kurt Krummbein said:
Mine is:
cat /sys/zte_board_id/board_id
wrbA-EUROPE
cat: /proc/device-tree/model: No such file or directory
cat: /proc/device-tree/compatible: No such file or directory
ls /proc/device-tree
/proc/device-tree: No such file or directory
Attached my build.prop ... perhaps this sheds some light .
Thx
Kurt
Click to expand...
Click to collapse
Sorry for that, I forgot that the stock kernel did not expose the device tree.
But I think I remeber the info about the model is in the logcat after boot up...
Please try this ones in a terminal on the phone or via adb shell, they should work.
Code:
su
Blade-S6:/ # cat /sys/devices/soc0/hw_platform
MTP
Blade-S6:/ # cat /sys/devices/soc0/soc_id
239

lightwars said:
Sorry for that, I forgot that the stock kernel did not expose the device tree.
But I think I remeber the info about the model is in the logcat after boot up...
Please try this ones in a terminal on the phone or via adb shell, they should work.
Code:
su
Blade-S6:/ # cat /sys/devices/soc0/hw_platform
MTP
Blade-S6:/ # cat /sys/devices/soc0/soc_id
239
Click to expand...
Click to collapse
mine is:
cat /sys/devices/soc0/hw_platform
MTP
cat /sys/devices/soc0/soc_id
268
cat /sys/devices/soc0/image_version
10:LRX22G:eng.root.20150808.123811
Gtz
Kurt

Kurt Krummbein said:
mine is:
cat /sys/devices/soc0/hw_platform
MTP
cat /sys/devices/soc0/soc_id
268
cat /sys/devices/soc0/image_version
10:LRX22G:eng.root.20150808.123811
Gtz
Kurt
Click to expand...
Click to collapse
Fantastic! Here we have an explanation. Your device reports 268 as id which equals to msm8929 and I have a device with id 239 which is msm8939. The kernel only holds a device tree blob (dtb) for the id 239. I thought that the variant were very similar, so last time I used a dtb from the eu release but only for id 239. Attached I have added a dtb for id 268. Please test this rom with that boot image.
Again, just unpack the bootASEU.img and copy it to your device, flash it after installing the lineageos zip.
Please make a backup beforehand and report back, when you have time. Happy trying out.

lightwars said:
Fantastic! Here we have an explanation. Your device reports 268 as id which equals to msm8929 and I have a device with id 239 which is msm8939. The kernel only holds a device tree blob (dtb) for the id 239. I thought that the variant were very similar, so last time I used a dtb from the eu release but only for id 239. Attached I have added a dtb for id 268. Please test this rom with that boot image.
Again, just unpack the bootASEU.img and copy it to your device, flash it after installing the lineageos zip.
Please make a backup beforehand and report back, when you have time. Happy trying out.
Click to expand...
Click to collapse
One step ahead ! Phone is booting with the new boot.img ... but ends with a bootloop.
Highest was one boot with start of the setup-wizard, but after setting language to "Deutsch (Deutschland)" (and several "Bluetooth is not working" messages) it went around again. Couldn't get logs yet ... well see :
Cheers
Kurt

Kurt Krummbein said:
One step ahead ! Phone is booting with the new boot.img ... but ends with a bootloop.
Highest was one boot with start of the setup-wizard, but after setting language to "Deutsch (Deutschland)" (and several "Bluetooth is not working" messages) it went around again. Couldn't get logs yet ... well see :
Cheers
Kurt
Click to expand...
Click to collapse
Yeah! Would be best to build the dtb from source, rather than attaching just the right one to the kernel...
The bluetooth message can be made silent, by the way what build you are using? I think the first build has not the fix for the message. The build.prop should contain this line:
Code:
ro.boot.btmacaddr=00:00:00:00:00:00
and the message should not appear.
I hope there are not any preferences with could only be applied to msm8939 and not to msm8929.

@Kurt Krummbein
Here is my latest build or just grab the boot.img from the attachment. Which has a dtb for msm8929 build from source.
Maybe this will boot without any bootloop.

lightwars said:
@Kurt Krummbein
Here is my latest build or just grab the boot.img from the attachment. Which has a dtb for msm8929 build from source.
Maybe this will boot without any bootloop.
Click to expand...
Click to collapse
For which version is your latest build? the eu?
Thanks
BR Slawo

slawoko said:
For which version is your latest build? the eu?
Thanks
BR Slawo
Click to expand...
Click to collapse
AS and hopefully EU.