Related
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?
Intel Android Devices Root / Temp Recovery Session
social-design-concepts said:
Disclaimer:
Before you proceed to the rooting instructions below, please read this disclaimer:
XDA-DEVELOPERS.COM and I are not responsible for what you are doing to your device. You understand and agree that you are doing this at your own risk.
as for warranty the rule of thumb is if you root you should always consider your warranty voided : i will make no claim otherwise on the subject.
i am just a simple hobbyist from Cinti. OH USA i have no intention to buy devices or users getting mad that they were under some impression this wouldn't void the warranty.
if you root you should always consider your warranty voided
Click to expand...
Click to collapse
Tethered Temporary CWM / TWRP Recovery Session :
Note : This is a Temporary CWM / TWRP Recovery Session for some Intel Devices with locked bootloaders.
This recovery is not installed to the devices and has to be launched from a computer ( tethered ) each time you need to access the CWM / TWRP Recovery. . .
WARNING : This Temporary CWM / TWRP Recovery Session is for some Intel Devices with locked boot loaders.
It is not intended for installing custom roms as if the devices has a locked bootloader the device will fail to boot the unsigned images
Intel Fastboot Tethered Temporary Recovery Session Launcher download :
Current Version : IntelAndroid-FBRL-07-24-2015.7z
Generic Instructions for use better instructions coming later just wanted to get the thread up :
notes :
make sure you have downloaded and installed the adb / fastboot drivers for your device . . .
make sure you have enabled developer options / adb debugging under settings on your device . . .
make sure you have download the latest : UPDATE-SuperSU-vX.Xx.zip and place it on your internal or external_sd
1 : download and extract IntelAndroid-FBRL-07-24-2015.7z some where on your computer.
2 : double click the launcher.bat file to start , type " ACCEPT " case sensitive without quotes to continue
check that the tool is reporting as either :
DEVICE STATUS: ADB-ONLINE
DEVICE STATUS: FASTBOOT-ONLINE
If " DEVICE STATUS: UNKNOWN " please check your cable connection and driver installation under Windows Device Manager
If " DEVICE STATUS: UNAUTHORIZED " please check if your devices is displaying an authorization prompt be sure to check Always allow from this computer and then press ok
3 : select the trigger to launch the Temporary CWM Recovery Session support fastboot oem triggers are :
T1 oem startftm ( very few devices support this command , but its the original used so )
devices supported : coming soon
T2 oem backup_factory ( limited devices support this command )
devices supported : coming soon
T3 oem stop_partitioning ( should work on alot of kitkat builds )
devices supported : coming soon
T4 oem stop_partitioning ( probably works on all devices that are supported (Jellybean , KitKat , Lollipop) )
devices supported : coming soon
4 : after selecting the trigger your device should reboot in to fastboot and begin to copy files to your device
note : if your device hangs at the waiting-for-device screen and you see droidboot CMD Waiting on your devices double check that the fastboot driver installed correctly.
note : if you see unknown oem command the trigger isn't supported by your device.
5 : The temporary cwm recovery session should be started at this point select install zip from the recovery menu using vol up / vol down to navigate and power to select
6 : select install zip from sdcard / external_sd depending on where you placed the file and select the UPDATE-SuperSU-vX.Xx.zip you downloaded earlier
7 : confirm the installation
8 : after install completes reboot your device
note :
some devices have limited space under /system and the supersu app wont install
if you don't see the supersu app on your device attempt to install it from the playstore
more than likely the su binary installed correctly but there want enough room on the device for the app.
This recovery uses the CWM Recovery @vampirefo built for the Dell Venue 8 3830 NoModem original thread : Dell Venue 8, CWM, unsecure boot/recovery
You know it's annoying to find this on so many other forums. with other people taking credit for it. sad face : (
APPRECIATE MY WORK, I DON'T DRINK, SO CLICK HERE DONATE NOW AND BUY ME COFFEE
XDA:DevDB Information
Intel Android FBRL, Tool/Utility for the Android General
Contributors
social-design-concepts
Version Information
Status: Stable
Created 2015-07-28
Last Updated 2015-07-28
Supported Devices List / Trigger
Supported Devices List / Trigger
Acer :
B1-730 T2
B1-730HD T2
A1-830
A1-840FHD T3
A1-840 (HD) T3
Asus :
ME170C T2 & T3
ME176C T2 & T3
Dell :
Venue 7 3730 / Venue 8 3830 All Triggers Should Work
Venue 7 3740 / Venue 8 3840 T3
Venue 7 3741 / T3
Venue 8 7840 T3
Iview :
i700 T2 & T3
Kurio :
Xtreme 7 Only had a chance to test trigger T3
Odys :
intellitab 7
Nabi:
Dreamtab model IN08A trigger T3 reported working
Prestigio :
MultiPad Thunder 7.0i
Tesla :
L7 Tablet T3
Tesco :
Op3n Dott 8 T2 & T3
Toshibia :
Excite 7 T3
Links to devices specific threads / forums
Links to devices specific threads / forums
If you have created a devices specific thread / forum for your devices please PM the link so that i can post a link to it here to make it easier to help new users . . . . Please put Intel Device Specific Thread in the supject . Thank You .
The Concept / Source Code
The Concept / Source Code
Collected Device Dumps / Captured OTA Updates
Collected Device Dumps / Captured OTA Updates
Generic / Tips for Unbricking
Generic / Tips for Unbricking
Ahh!
Just my luck lol. Had a feeling I would end up bricked for some reason, maybe I jinxed myself.
Anyways... everything was going ok, I selected trigger 3 to try first, reboots to droidboot (with "waiting for fastboot command") then I select recovery and get android dude laying down with a red exclamation point coming out his belly and it just said "no command" now I am soft bricked, only getting the USB symbal with the white line under it. Please help!
GeeKerGurL said:
Just my luck lol. Had a feeling I wouls end up beicked for some reason, maybe I jinxed myself.
Try to manually boot to droidboot
Anyways... everything was going ok, I selected trigger 3 to try first, reboots to droidboot (with "waiting for fastboot command") then I select recovery and get android dude laying down with a red exclamation point coming out his belly and it just said "no command" now I am soft bricked, only getting the USB symbal with the white line under it. Please help!
Click to expand...
Click to collapse
We can remote around 1130pm est and I'll get you running v8 correct?
Sent from my XT907 using XDA Free mobile app
social-design-concepts said:
We can remote around 1130pm est and I'll get you running v8 correct?
Sent from my XT907 using XDA Free mobile app
Click to expand...
Click to collapse
Yeah 3830. Thanks a bunch. Now what do I have to do to remote? I am on a win7 PC with 1gig that is so slow I wanna scream. Also I am in another timezone so how long would that be from now?
GeeKerGurL said:
Yeah 3830. Thanks a bunch. Now what do I have to do to remote? I am on a win7 PC with 1gig that is so slow I wanna scream. Also I am in another timezone so how long would that be from now?
Click to expand...
Click to collapse
1 hour 30 minutes
Sent from my XT907 using XDA Free mobile app
social-design-concepts said:
1 hour 30 minutes
Sent from my XT907 using XDA Free mobile app
Click to expand...
Click to collapse
Okie dokie. Ill be here.
social-design-concepts said:
We can remote around 1130pm est and I'll get you running v8 correct?
Sent from my XT907 using XDA Free mobile app
Click to expand...
Click to collapse
Woot!!!YA! no need, I got it back all by myself just had to boot with vol down and go back through the process and everything copied fine and worked this time! :good: thanks a ton for offering to help me though buddy!
BTW trigger 3 works for the 3830 V8 no modem
WOOOHOOOOHOOOOWOOOO! root check cleared, I am SOO happy to finally have root on this thing. Besides my minor hiccup for whatever reason this method was pie too! YAHOO. I went from about to cry to jumping around happy like a crazy person haha.
recovery fstab
What needs to be change for jb 4.2.2?
I am able to open and edit the file.
b.g.
whgarner said:
What needs to be change for jb 4.2.2?
I am able to open and edit the file.
b.g.
Click to expand...
Click to collapse
recovery.fstab may or may not need to be edited for some devices especially if the device doesn't use by label partitioning. What device do you have?
Sent from my XT907 using XDA Free mobile app
asus aa3-600
I have an asus aa3-600-ur10
android 4.2.2
Intel Celeron J1850 Quad-core 2 GHz
21.5" Full HD (1920 x 1080) 16:9
Intel HD Graphics with Shared Memory
2 GB, DDR3 SDRAM
500 GB HDD
The problem I'm having is no usb debugging, only debugging via lan. I can get adb to work but not working with fastboot in the bootloader(droidboot). I have a post about it in this section, search for "aa3-600"
b.g.
Hi, SDC
I know this has been ask before, I searched and couldn't find the answer though, I would like to get the source code for the launchers , I use the Linux version of this method, cause I don't have windows, and would like to convert the recovery.launcher triggers and so forth into a shell script rather that use binary file.
If you have a shell script already can you post it if not, can you post or give me a link to your binary files source code?
tomtom1265 said:
Hi, SDC
I know this has been ask before, I searched and couldn't find the answer though, I would like to get the source code for the launchers , I use the Linux version of this method, cause I don't have windows, and would like to convert the recovery.launcher triggers and so forth into a shell script rather that use binary file.
If you have a shell script already can you post it if not, can you post or give me a link to your binary files source code?
Click to expand...
Click to collapse
I'm going to post the source after I finish getting the thread put together I just wanted to get it up yesterday.
As for doing it through shell scripts the reason its binary is because if /system is mounted or any prebuilt binary has a dependency on a shared library it makes it extremely difficult some times impossible to stop services and unmount /system and such.
But I hope to have everything finish by the end of the day.
Sent from my XT907 using XDA Free mobile app
whgarner said:
I have an asus aa3-600-ur10
android 4.2.2
Intel Celeron J1850 Quad-core 2 GHz
21.5" Full HD (1920 x 1080) 16:9
Intel HD Graphics with Shared Memory
2 GB, DDR3 SDRAM
500 GB HDD
The problem I'm having is no usb debugging, only debugging via lan. I can get adb to work but not working with fastboot in the bootloader(droidboot). I have a post about it in this section, search for "aa3-600"
b.g.
Click to expand...
Click to collapse
You use Linux or windows? If Linux, you may need to use my fastboot binary, anyway if using Linux while in fastboot mode use terminal type lsusb.
Do you see your device listed?
Sent from my T1 using XDA Free mobile app
Root!
Thank you for this!
I successfully rooted my V8 3830 KK4.4 V1.33 no modem with T3 - in about 4 mins. tops.
FYI:
I connected and launched the launcher from the IntellAndroid-FBRL folder. Typed ACCEPT and got the green screen. Chose T3. The tablet rebooted into fastboot and files where loaded, But then fastboot turned red and said "device unauthorized" when CWM popped onto my tablet. (maybe it's suppose to do that, DK) and yes, US debugging was on, I flashed the SU zip, rebooted, all is well. SU updated and working fine. I was able to remove all the crapwear. :laugh:
thank you SDC!
Quick question - Do any of the intel devices have unlocked bootloader?? Thought I read somewhere somebody was able to install a factory 4.3 or 4.2 on a Dell venue and the bootloader unlocked?
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!
Please link for ZTE K3DX-V5G firmware.
ZTE K3DX-V5G firmware
Why do you need ZTE K3DX-V5G firmware?
Is there something wrong with your device?
Do you recommend buying the ZTE K3DX-V5G?
The brand name is V5 or ZTE or Guan or Mango.
It is the same device, manufatured by V5 and sold by ZTE, Guan and Mango.
Guan K3DX-V5G
https://deviceatlas.com/device-data/devices/guan/k3dx-v5g/28213760
BangGearWatch | ZTE V5G-K3DX
https://www.banggearwatch.com/pricetracker/zte-v5g-k3dx-5-5-inch-3gb-1369255/
The price was €64 at BangGood, for a short time.
The price was €70 at MyeFOX.
V5 K3DX-V5G 3GB RAM 32GB ROM Qualcomm Snapdragon 617 1.5GHz Octa Core FHD Display 5.5 inches Android 5.1 4G LTE Smartphone
https://www.myefox.fr/telephones/v5...a-core-fhd-ecran-55-pouces-android-5-g-223880
K3DX-V5G supports naked-eye 3D and eye-tracking.
It has a K3DX display with column interlaced mode.
Therefore is fully compatible with PhereoRol3D app.
https://github.com/JackDesBwa/PhereoRoll3D
Get the latest release here
https://github.com/JackDesBwa/PhereoRoll3D/releases
Have you tried PhereoRol3D ?
BootStomp and DR.CHECKER
Your phone has a locked bootloader.
You need to run these two tools: DR.CHECKER and BootStomp.
DR.CHECKER : A Soundy Vulnerability Detection Tool for Linux Kernel Drivers.
It is a single script!
This repo contains all the sources, including setup scripts. Now with an Amazing UI to view the warnings along with corresponding source files.
https://github.com/ucsb-seclab/dr_checker
BootStomp
https://seclab.cs.ucsb.edu/academic/publishing/#bootstomp-security-bootloaders-mobile-devices-2017
Did you manage to root ZTE K3DX-V5G ?
Partitions table
Get an excellent partitions table of ZTE K3DX-V5G
This format is ideal for recovery.
Device Info HW
https://play.google.com/store/apps/details?id=ru.andr7e.deviceinfohw&hl=en_US
NOTE - Find attached the partitions table of SuperD D1 (SuperD C1001). It is another device with Naked-eye 3D and eye-tracking.
Do you own a ZTE K3DX-V5G ?
You do not own a ZTE K3DX-V5G, do you?
V5 K3DX V5G Smartphone Unboxing (3D Video Camera)
https://www.youtube.com/watch?v=KkQhQszdSYs
Mango K3DX-V5G
https://v.youku.com/v_show/id_XMjgxMDI4OTcyOA==.html
3D Dongdong APP: Over 10,000 3D movies provided
http://en.k3dx.com/prolist/7/17.html
Thank you for many information about it.
I did not own it now due to it heat up too much compare with SD 625 / 636 phone.
Discussion V5 K3DX-V5G at russian 4pda forum
Discussion V5 K3DX-V5G
http://4pda.ru/forum/index.php?showtopic=944204
There is new firmware available from chinese versions (latest 1.3)
Firmware in China
http://www.shuajibao.com/rom/Zte/23777
Version 1.3 is not official. It is a custom ROM by this russian guy... Sidorovvitalik.
But development has already stopped because he is selling his ZTE V5 K3DX-V5G.
K3DX V5G stockrom
Please can someone upload the stockrom.
After scouring the internet for hours, I stumbled upon this post:
https://4pda.ru/forum/index.php?showtopic=944204&st=220
And guess what, I found the firmware for the device! Eventually, I was able to fix my bricked K3DX V5G, and here it is:
https://yadi.sk/d/TSjrTYbKBV4KWA
What I did was:
1. Decompressing the file
2. Flashing it with fastboot
3. Device resurrected!
Fastboot commands:
Code:
fastboot flash:raw boot boot.img
fastboot flash system system.img
edit: found out that it is a clone of ZTE v5 pro N940SC
Ma'am/Sir. Can i ask what usb driver did you use to detect your k3dx-v5g? Because mine is not detecting. Thanks in advance.
Ma'am/Sir. Can i ask what usb driver did you use to detect your k3dx-v5g? Because mine is not detecting. Thanks in advance.
asce16 said:
Ma'am/Sir. Can i ask what usb driver did you use to detect your k3dx-v5g? Because mine is not detecting. Thanks in advance.
Click to expand...
Click to collapse
Are you on Linux or Windows?
Ma'am/Sir. What usb driver did you use to detect your k3dx v5g phone? I cant find compatible to mine, my pc cant detect my k3dx v5g phone. Plsss. Send link. Thanks in advance.
B83C said:
Are you on Linux or Windows?
Click to expand...
Click to collapse
Window.
B83C said:
Are you on Linux or Windows?
Click to expand...
Click to collapse
Also ma'am/sir. can i ask a little favor? Can you send me full guide how to flash this file. Plssss
asce16 said:
Also ma'am/sir. can i ask a little favor? Can you send me full guide how to flash this file. Plssss
Click to expand...
Click to collapse
Hmm well, have u tried peeking at the device manager when you phone is connected to your PC in fastboot mode?
If there's an entry showing your device you will need grab a fastboot binary to flash the firmware.
Here's a link to the tool called minimal ADB and Fastboot: here
You will also need to extract the firmware to somewhere in your drive.
Having done all the extraction and installation,
and since you're on Windows, you should do:
Bash:
\path\to\fastboot flash:raw boot \path\to\boot.img
\path\to\fastboot flash system \path\to\system.img
where \path\to\fastboot points to the path where you have extracted/installed the tool (or if you have added its path to the PATH environment variable, you can avoid the hassle to write the full path), and \path\to\boot.img and system.img points to absolute path of the extracted firmware.
Then, you are good to go!
B83C said:
Hmm well, have u tried peeking at the device manager when you phone is connected to your PC in fastboot mode?
If there's an entry showing your device you will need grab a fastboot binary to flash the firmware.
Here's a link to the tool called minimal ADB and Fastboot: here
You will also need to extract the firmware to somewhere in your drive.
Having done all the extraction and installation,
and since you're on Windows, you should do:
Bash:
\path\to\fastboot flash:raw boot \path\to\boot.img
\path\to\fastboot flash system \path\to\system.img
where \path\to\fastboot points to the path where you have extracted/installed the tool (or if you have added its path to the PATH environment variable, you can avoid the hassle to write the full path), and \path\to\boot.img and system.img points to absolute path of the extracted firmware.
Then, you are good to go!
Click to expand...
Click to collapse
Ma'am/sir. Thanks, it's fix now. Thanks for the help. Godbless and stay safe.
Hello, in case you are looking for a twrp image for the device, here's one I have ported myself:
TWRP_N940Sc_V3
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
B83C said:
Hello, in case you are looking for a twrp image for the device, here's one I have ported myself:
https://www.mediafire.com/file/0547s4g8hdojctq/TWRP_N940Sc_V3.img/fileTh
Click to expand...
Click to collapse
Thankyou! Uhm is there any custom rom? Can you please port a custom rom or upload please i really need it[/url]
John072021 said:
Thankyou! Uhm is there any custom rom? Can you please port a custom rom or upload please i really need it[/url]
Click to expand...
Click to collapse
I regret to tell you that, no. Currently I have been using the phone as a debian server, since the LCD has been inadvertently broken ( I exerted too much force on it ). Moreover, the device doesn't recognize its battery, which suggests that I might have broken some part of it. Therefore, I have kinda lost any hopes for it. Plus, my linux machine is not powerful enough to build an android OS ( what do you expect much from an intel celeron? ).
PS: I might do it once I get my hands on a much powerful one, or maybe a powerful enough VPS? I am not quite sure but currently I am still in high school, meaning that I may or may not have time....
Best regards,
B83C
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.