{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Your warranty is now void.
I am not responsible for bricked devices, dead SD cards, thermonuclear war.
Please do some research if you have any concerns about using custom ROMs/Kernels.
You are choosing to make these modifications, and if you point the finger at me for
messing up your device, I will laugh at you.
Lambda Kernel was my development start point in the LG G2 glorious period, now you're looking at a new "horizon of possibility" for the LeEco device family. This Kernel has been written from scratch since January 2017, resulting in a small, polished and minimal core that's migratable across Kernel revisions.
It follows the flash n' go principle, everything packed in the Kernel is already tweaked and ready to be used as a daily driver for everyone.
The downloads, contributors and source code are at the bottom of this post, it is recommended to read everything before flashing.
DEVEL: My own testing builds for certain features and tests. They aren't normally shared, although sometimes I publish them. If you see one of them, don't forget they are recommended for advanced users/developers only because of their potential changes that must be debugged before publishing a NIGHTLY version.
NIGHTLY: They are closer to the proper release version but still can have some errors or bugs to be reported and tested, they should be generally stable. Nightly doesn't mean it builds every night here since I don't use a build server, it means that is the regularly updated version.
SNAPSHOT: That's the version for the ones that don't want their devices to be lab rats for new features and staging changes. I don't know whether or not to say something is stable enough to be a SNAPSHOT but if you see one it's because it's been sometime running well.
Pretty straightforward once you get used to it, isn't it?
A general panorama for Lambda Kernel, always matching the latest release, in this case the NIGHTLY from 03-23-2018.
HOT ↠ Source-code changes for Lambda Kernel.
COLD ↠ Environment changes for Lambda Kernel.
Latest LA.HB Kernel base from CAF's upstream HOT
Minimal device tree stubs and OEM code HOT
Modular approach for EUI compatibility HOT
Built with Paranoid's patched GCC compiler HOT
Latest Wi-Fi qcacl-2.0 driver from CAF's upstream HOT
Refactored and update OEM sound code to catch up with CAF HOT
Removed the old WCD9330 sound driver dependencies HOT
Removed most of the OEM useless drivers to use the original ones from CAF HOT
Tailored down the preset configuration to reduce Kernel size HOT
Own headset detection code built on top of CAF HOT
Backports of the Android USB driver and gadget from LA.UM.5.5 (N) HOT
Patched battery type adjustments during charger code execution HOT
Corrected charging constants to charge safer with less heat dissipation HOT
Read this twice before flashing/posting!
Cod. 000:
State: Placebo!
Priority: Urgent.
Overview: The thread is under construction here as well.
Read this twice before flashing/posting!
Q. How to install this Kernel?
A. Download the version you'd like to use and flash using a custom recovery like TWRP.
Q. What ROMs does this Kernel support?
A. It supports the version explicitly mentioned in the file name and its "forks".
Q. Will this Kernel support my ROM in future?
A. I've no clue, will it probably be the default Kernel of those in future? You tell me...
Click the Downloads button above to go straight to Github releases page, find the appropriate file for your variant and flash it in recovery.
Many developers and people helped to bring the pieces of code needed to build the Lambda Kernel Project, some of them are listed below.
AlexDNS
Codeworkx
Dorimanx
Faux
FranciscoFranco
Myfluxi
SultanXDA
Source for Kernel at Github.
Source for AnyKernel2 at Github.
Guide and introduction to Lambda Kernel development at Github.
~ All project resources were built with free and open source software. ~~ Lambda Kernel trademark and logos are copyleft. ~~ This is a development thread, be polite. ~
Reserved
Reserved.
Reserved
Reserved.
For EUI, right? I'm curious how it runs but I'm on CM13 atm.
Sent from my LEX727 using XDA-Developers Legacy app
benjmiester said:
For EUI, right? I'm curious how it runs but I'm on CM13 atm.
Sent from my LEX727 using XDA-Developers Legacy app
Click to expand...
Click to collapse
I'm not sure if there are device and Kernel trees for CM13 on this device available (open source) to check whether it'd work or not. The Kernel shouldn't diverge much from stock and it may worth the shot. If it boots on stock, it boots on CM probably.
GalaticStryder said:
I'm not sure if there are device and Kernel trees for CM13 on this device available (open source) to check whether it'd work or not. The Kernel shouldn't diverge much from stock and it may worth the shot. If it boots on stock, it boots on CM probably.
Click to expand...
Click to collapse
Alright, I'll test it on a X727 (20s EUI). Just need to make a backup and cross my fingers lol.
Edit: The zip flashed correctly, but the phone just sits on the splash screen. I waited for about 10-12 minutes and didn't boot up or even reach the boot animation.
Ace42 said:
Alright, I'll test it on a X727 (20s EUI). Just need to make a backup and cross my fingers lol.
Edit: The zip flashed correctly, but the phone just sits on the splash screen. I waited for about 10-12 minutes and didn't boot up or even reach the boot animation.
Click to expand...
Click to collapse
Yeah, that was expected, that CAF merge introduced some pretty intrusive changes in device tree side of things, although none of them seem to hurt, splash screen stuck issues are usually something "minor" as the Kernel is still alive, probably trying to probe certain codec up but not being able to do so.
I may push another zip without the merge to query...
UPDATE: I'll be rolling a couple compilations with different changes, flashing in the version order will give better results. Please, check if /data/kernel_output.txt is present.
GalaticStryder said:
Yeah, that was expected, that CAF merge introduced some pretty intrusive changes in device tree side of things, although none of them seem to hurt, splash screen stuck issues are usually something "minor" as the Kernel is still alive, probably trying to probe certain codec up but not being able to do so.
I may push another zip without the merge to query...
UPDATE: I'll be rolling a couple compilations with different changes, flashing in the version order will give better results. Please, check if /data/kernel_output.txt is present.
Click to expand...
Click to collapse
I can't find that file. These are the only files in /data besides the folders.
Ace42 said:
I can't find that file. These are the only files in /data besides the folders.
Click to expand...
Click to collapse
So I wasn't generated at the ramdisk generation step, I've allocated the file, it will be in root right now.
Could you output the following:
Code:
ls -l /dev/block/bootdevice/by-name/boot
Code:
ls -l /system/lib/modules/
I'll push all builds to Drive, attachments aren't working quite well...
GalaticStryder said:
So I wasn't generated at the ramdisk generation step, I've allocated the file, it will be in root right now.
Could you output the following:
I'll push all builds to Drive, attachments aren't working quite well...
Click to expand...
Click to collapse
$ su
[email protected]_zl1:/data/data/com.termux/files/home # ls -l /dev/block/bootdevice/by-name/boot
lrwxrwxrwx root root 1970-03-22 08:01 boot -> /dev/block/sde18
[email protected]_zl1:/data/data/com.termux/files/home #
[email protected]_zl1:/data/data/com.termux/files/home #
ls -l /system/lib/modules/
-rw-r--r-- root root 11484 1970-03-10 00:35 ansi_cprng.ko
-rw-r--r-- root root 21644 1970-03-10 00:35 br_netfilter.ko
-rw-r--r-- root root 319628 1970-03-10 00:35 core_ctl.ko
-rw-r--r-- root root 7612 1970-03-10 00:35 evbug.ko
-rw-r--r-- root root 30740 1970-03-10 00:35 ghci-hcd.ko
-rw-r--r-- root root 32588 1970-03-10 00:35 gxhci-hcd.ko
-rw-r--r-- root root 62076 1970-03-10 00:35 jnl.ko
-rw-r--r-- root root 13916 1970-03-10 00:35 lcd.ko
-rw-r--r-- root root 56948 1970-03-10 00:35 mmc_block_test.ko
-rw-r--r-- root root 43732 1970-03-10 00:35 mmc_test.ko
-rw-r--r-- root root 2640 1970-03-18 01:00 modules.dep.bb
drwxr-xr-x root root 2017-01-05 15:31 qca_cld
-rw-r--r-- root root 19028 1970-03-10 00:35 rdbg.ko
-rw-r--r-- root root 20940 1970-03-10 00:35 spidev.ko
-rw-r--r-- root root 32116 1970-03-10 00:35 test-iosched.ko
-rw-r--r-- root root 45228 1970-03-10 00:35 ufs_test.ko
-rw-r--r-- root root 632820 1970-03-10 00:35 ufsd.ko
-rw-r--r-- root root 296948 1970-03-10 00:35 wil6210.ko
lrwxrwxrwx root root 2017-01-05 15:32 wlan.ko -> /system/lib/modules/qca_cld/qca_cld_wlan.ko
[email protected]_zl1:/data/data/com.termux/files/home #
Ace42 said:
$ su
[email protected]_zl1:/data/data/com.termux/files/home # ls -l /dev/block/bootdevice/by-name/boot
lrwxrwxrwx root root 1970-03-22 08:01 boot -> /dev/block/sde18
[email protected]_zl1:/data/data/com.termux/files/home #
[email protected]_zl1:/data/data/com.termux/files/home #
ls -l /system/lib/modules/
-rw-r--r-- root root 11484 1970-03-10 00:35 ansi_cprng.ko
-rw-r--r-- root root 21644 1970-03-10 00:35 br_netfilter.ko
-rw-r--r-- root root 319628 1970-03-10 00:35 core_ctl.ko
-rw-r--r-- root root 7612 1970-03-10 00:35 evbug.ko
-rw-r--r-- root root 30740 1970-03-10 00:35 ghci-hcd.ko
-rw-r--r-- root root 32588 1970-03-10 00:35 gxhci-hcd.ko
-rw-r--r-- root root 62076 1970-03-10 00:35 jnl.ko
-rw-r--r-- root root 13916 1970-03-10 00:35 lcd.ko
-rw-r--r-- root root 56948 1970-03-10 00:35 mmc_block_test.ko
-rw-r--r-- root root 43732 1970-03-10 00:35 mmc_test.ko
-rw-r--r-- root root 2640 1970-03-18 01:00 modules.dep.bb
drwxr-xr-x root root 2017-01-05 15:31 qca_cld
-rw-r--r-- root root 19028 1970-03-10 00:35 rdbg.ko
-rw-r--r-- root root 20940 1970-03-10 00:35 spidev.ko
-rw-r--r-- root root 32116 1970-03-10 00:35 test-iosched.ko
-rw-r--r-- root root 45228 1970-03-10 00:35 ufs_test.ko
-rw-r--r-- root root 632820 1970-03-10 00:35 ufsd.ko
-rw-r--r-- root root 296948 1970-03-10 00:35 wil6210.ko
lrwxrwxrwx root root 2017-01-05 15:32 wlan.ko -> /system/lib/modules/qca_cld/qca_cld_wlan.ko
[email protected]_zl1:/data/data/com.termux/files/home #
Click to expand...
Click to collapse
Thanks, that should be enough, see if the latest Experimental 3 boots after the quick fixes in anykernel. I'll add a wrapper to symlink the wlan module if needed. But first we need to force it boot up.
GalaticStryder said:
Thanks, that should be enough, see if the latest Experimental 3 boots after the quick fixes in anykernel. I'll add a wrapper to symlink the wlan module if needed. But first we need to force it boot up.
Click to expand...
Click to collapse
Success! It booted up.
Ace42 said:
Success! It booted up.
Click to expand...
Click to collapse
Thanks for testing it. The file kernel_output.txt is present in rootfs (/)?
Code:
cd /
cat kernel_output.txt
Code:
lsmod
Code:
dmesg
These should help to gather more on what is working or not.
http://pastebin.com/A3nBZ7gm
Ace42 said:
Success! It booted up.
Click to expand...
Click to collapse
and it boots with CM 13 but no wifi
Boots on slim rom as well
booted up here on my lex 720 Google Edition as well...[emoji122]
Sent from my LEX720 using XDA-Developers Legacy app
Okarina26 said:
booted up here on my lex 720 Google Edition as well...[emoji122]
Sent from my LEX720 using XDA-Developers Legacy app
Click to expand...
Click to collapse
Yup, seems that everyone is using the LeEco base Kernel so far, I know darkobas has a different Kernel source with a different tag from LA.UM (nougat) CAF tag, so I'd not encourage using this Kernel with Omni 7.1 if that's the case.
The modules didn't get injected, for some reason, I'll manage to patch this and then get rid of them.
New build 0.4 is up...
Could you be kindly so nice to talk about the features we will get with these kernel? Which configuration tool is recommended? Will it work with Cydras Rom?
... sent from my LEX720 with Tapatalk
GalaticStryder said:
Yup, seems that everyone is using the LeEco base Kernel so far, I know darkobas has a different Kernel source with a different tag from LA.UM (nougat) CAF tag, so I'd not encourage using this Kernel with Omni 7.1 if that's the case.
The modules didn't get injected, for some reason, I'll manage to patch this and then get rid of them.
New build 0.4 is up...
Click to expand...
Click to collapse
0.4 hangs on the splash screen just like 0.1. As soon as I revert to 0.3 it boots up to Android.
Related
So..... I've been fussing with the kernel these days.
I managed to add cwm recovery just by editing initramfs.
also, I could enable init.d support
I had a repacker script that only involves original zImage and edited initramfs folder and it made my work easier.
Now, I became greedy and I wanted to add cpu governor.
If I want to do so, I 've gotta actually compile the kernel from source.
I first used this command
export ARCH=arm
export CROSS_COMPILE=/home/xxxxxxxx/arm-2009q3/bin/arm-none-eabi
make venturi_kor_defconfig #I have Korean device
make menuconfig # at the menu, i located my initramfs folder
make -j2
I've got numerous errors no matter what toolchain I used.
arm-eabi-4.4.0
arm-eabi-4.4.3
arm-eabi-4.7
arm-2009q3
arm-eabi-linaro 4.6.2
arm-eabi-linaro 4.7
all the zImages created had similar sizes as the original ones but none of them passed samsung logo (they do boot into recovery though)
4.4.3 and 4.7 didn't even make zImage so I guess that's guaranteed failure.
But Samsung's YP-GB70 Opensource zip says that I should use arm-2009q3 and when I do, it still gives me error
I use 12.04 LTS 64bit
any suggestion please? I'm dire
stylemate said:
So..... I've been fussing with the kernel these days.
I managed to add cwm recovery just by editing initramfs.
also, I could enable init.d support
I had a repacker script that only involves original zImage and edited initramfs folder and it made my work easier.
Now, I became greedy and I wanted to add cpu governor.
If I want to do so, I 've gotta actually compile the kernel from source.
I first used this command
export ARCH=arm
export CROSS_COMPILE=/home/xxxxxxxx/arm-2009q3/bin/arm-none-eabi
make venturi_kor_defconfig #I have Korean device
make menuconfig # at the menu, i located my initramfs folder
make -j2
I've got numerous errors no matter what toolchain I used.
arm-eabi-4.4.0
arm-eabi-4.4.3
arm-eabi-4.7
arm-2009q3
arm-eabi-linaro 4.6.2
arm-eabi-linaro 4.7
all the zImages created had similar sizes as the original ones but none of them passed samsung logo (they do boot into recovery though)
4.4.3 and 4.7 didn't even make zImage so I guess that's guaranteed failure.
But Samsung's YP-GB70 Opensource zip says that I should use arm-2009q3 and when I do, it still gives me error
I use 12.04 LTS 64bit
any suggestion please? I'm dire
Click to expand...
Click to collapse
Hmmm. First make sure you downloaded source for the gingerbread kernel (2.6.35) and not froyo (2.6.32) - it should also be a zip.
Second 4.4.3 is what I use, so that's quite strange. I'll need complete output to see what the problem is.
Mevordel said:
Hmmm. First make sure you downloaded source for the gingerbread kernel (2.6.35) and not froyo (2.6.32) - it should also be a zip.
Second 4.4.3 is what I use, so that's quite strange. I'll need complete output to see what the problem is.
Click to expand...
Click to collapse
Hmm sorrry for not clarifying that. I'm certain that I got Gingerbread source and it said to use G++ toolchain for EABI. Which is arm-2009q3-68
I made a mistake saying that It gave me an error. they were warnings. zImages were succesfully made along with other modules but it just doesn't boot.
btw, do you know how to fix bootloop when recovery can't locate cache partition and can't even factory reset?
stylemate said:
Hmm sorrry for not clarifying that. I'm certain that I got Gingerbread source and it said to use G++ toolchain for EABI. Which is arm-2009q3-68
I made a mistake saying that It gave me an error. they were warnings. zImages were succesfully made along with other modules but it just doesn't boot.
btw, do you know how to fix bootloop when recovery can't locate cache partition and can't even factory reset?
Click to expand...
Click to collapse
Do you have the initramfs packed into the rom because Samsung kernels have the initramfs inside them.
Sent from my Nexus 7 using Tapatalk HD
zaclimon said:
Do you have the initramfs packed into the rom because Samsung kernels have the initramfs inside them.
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
....... hmmmmmm I'm having quite hard time comprehending that....... sorry
i first extracted initramfs from zImage, (you know by using magic number like 30 37 30 37)
Then I added cwm recovery from Entropy's source.
I repacked it to modified_ramdisk.cpio
Then I tried to compile kernel by samsung's open source zip (inside there were one tar.gz for platform and another for kernel)
I used those commands at the first post, using the right toolchain that the opensource specified.
I even located my initramfs directory in the GUI section of config.
What did I do wrong?
stylemate said:
....... hmmmmmm I'm having quite hard time comprehending that....... sorry
i first extracted initramfs from zImage, (you know by using magic number like 30 37 30 37)
Then I added cwm recovery from Entropy's source.
I repacked it to modified_ramdisk.cpio
Then I tried to compile kernel by samsung's open source zip (inside there were one tar.gz for platform and another for kernel)
I used those commands at the first post, using the right toolchain that the opensource specified.
I even located my initramfs directory in the GUI section of config.
What did I do wrong?
Click to expand...
Click to collapse
Oh sorry I meant kernel instead of ROM. Hmm why don't you take an initramfs from another source or copy-paste the scripts from your device and add the cwm binaries from entropy's?
Sent from my Nexus 7 using Tapatalk HD
stylemate said:
Hmm sorrry for not clarifying that. I'm certain that I got Gingerbread source and it said to use G++ toolchain for EABI. Which is arm-2009q3-68
I made a mistake saying that It gave me an error. they were warnings. zImages were succesfully made along with other modules but it just doesn't boot.
btw, do you know how to fix bootloop when recovery can't locate cache partition and can't even factory reset?
Click to expand...
Click to collapse
stylemate said:
....... hmmmmmm I'm having quite hard time comprehending that....... sorry
i first extracted initramfs from zImage, (you know by using magic number like 30 37 30 37)
Then I added cwm recovery from Entropy's source.
I repacked it to modified_ramdisk.cpio
Then I tried to compile kernel by samsung's open source zip (inside there were one tar.gz for platform and another for kernel)
I used those commands at the first post, using the right toolchain that the opensource specified.
I even located my initramfs directory in the GUI section of config.
What did I do wrong?
Click to expand...
Click to collapse
As far as I know, you didn't do anything wrong. The issue must be somewhere in the init scripts (init.<whatever>, recovery.rc, ueventd.<whatever>). Did you copy those from Entropy's ramdisk too? Which ones?
zaclimon said:
Oh sorry I meant kernel instead of ROM. Hmm why don't you take an initramfs from another source or copy-paste the scripts from your device and add the cwm binaries from entropy's?
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
I think I'm the only one with korean SGP5 initramfs source.....
anyway, I had a repacking script which doesn't bother with compiling the actual kernel.
I could make a kernel with just CWM recovery and it worked.
But I figured out that I had to compile the actual kernel to add governor or OC stuff... so......
Mevordel said:
As far as I know, you didn't do anything wrong. The issue must be somewhere in the init scripts (init.<whatever>, recovery.rc, ueventd.<whatever>). Did you copy those from Entropy's ramdisk too? Which ones?
Click to expand...
Click to collapse
Ho Thanks for your suggestion. I didn't copy the actual files of those scripts, I looked at his commit and saw those lines changed when he was adding CWM. So I just added or replaced few lines at recovery.rc
Then I copied bunch of files in sbin, which seemed necessary for the recovery.
I copied the clockworkmod image file
Then finally i copied the recovery.fstab
to misc/
I edited recovery.fstab several times to get mount and storage work.
So I think initramfs itself has no problem....... It got me a working kernel with CWM recovery.
But it's the problem when I actually try to compile kernel from the scratch.....
stylemate said:
Ho Thanks for your suggestion. I didn't copy the actual files of those scripts, I looked at his commit and saw those lines changed when he was adding CWM. So I just added or replaced few lines at recovery.rc
Then I copied bunch of files in sbin, which seemed necessary for the recovery.
I copied the clockworkmod image file
Then finally i copied the recovery.fstab
to misc/
I edited recovery.fstab several times to get mount and storage work.
So I think initramfs itself has no problem....... It got me a working kernel with CWM recovery.
But it's the problem when I actually try to compile kernel from the scratch.....
Click to expand...
Click to collapse
When you were just modifying the initramfs, did it boot normally then?
Mevordel said:
When you were just modifying the initramfs, did it boot normally then?
Click to expand...
Click to collapse
yes. very smoothly
I used linaro tool chain 4.6.2 and also arm-eabi-4.7 both worked fine when i just modified the initramfs with a simple script.
stylemate said:
yes. very smoothly
I used linaro tool chain 4.6.2 and also arm-eabi-4.7 both worked fine when i just modified the initramfs with a simple script.
Click to expand...
Click to collapse
Can you boot into CWM and (using adb shell) give me the output of
Code:
cat /proc/cpuinfo
ls -la /
Thanks.
Mevordel said:
Can you boot into CWM and (using adb shell) give me the output of
Code:
cat /proc/cpuinfo
ls -la /
Thanks.
Click to expand...
Click to collapse
Sorry I couldn't do anything because my device was hard bricked and I fixed it today 0.0
Hope you are still around here.
I can't run adb shell with my newly compiled kernel
computer does not detect my device and i tried plugging it in and out several times, killing adb server each time.
interesting thing is that i can't mount USB storage, system, efs or anything else in CWM recovery.
Only cache partition is mounted which is strange. I used same initramfs source for both working kernel and newly compiled kernel,
but i don't know what happened during the compiling process.
I tried compiling with the original intiramfs folder (not modified one) and <3e> recovery also gave me numerous errors like can't mount where, where, where, where.
so there mustn't be a problem in both init.rc-like scripts and ultimately initramfs. It's probably the compiling process and how I set up the compilation.
Do i have to check all lines in venturi_kor_defconfig......?
oh btw, sdcard can be mounted with original ramdisk compiled kernel also, just checked it now.
stylemate said:
Sorry I couldn't do anything because my device was hard bricked and I fixed it today 0.0
Hope you are still around here.
I can't run adb shell with my newly compiled kernel
computer does not detect my device and i tried plugging it in and out several times, killing adb server each time.
interesting thing is that i can't mount USB storage, system, efs or anything else in CWM recovery.
Only cache partition is mounted which is strange. I used same initramfs source for both working kernel and newly compiled kernel,
but i don't know what happened during the compiling process.
I tried compiling with the original intiramfs folder (not modified one) and <3e> recovery also gave me numerous errors like can't mount where, where, where, where.
so there mustn't be a problem in both init.rc-like scripts and ultimately initramfs. It's probably the compiling process and how I set up the compilation.
Do i have to check all lines in venturi_kor_defconfig......?
oh btw, sdcard can be mounted with original ramdisk compiled kernel also, just checked it now.
Click to expand...
Click to collapse
I mean from CWM on your repacked-but-not-compiled kernel -- the one you said worked.
Also, which exactly zip did you download from Samsung's site? You don't need to go through the defconfig as long as you got the right one.
Third, please only compile with 4.4.3 or the one Samsung recommends. Anything newer will probably not work.
Fourth, as to partitions, they are all formatted to RFS, right? And can you run in CWM (where everything mounts and is mounted):
Code:
mount
fdisk -l /dev/block/mmcblk0
Mevordel said:
I mean from CWM on your repacked-but-not-compiled kernel -- the one you said worked.
Also, which exactly zip did you download from Samsung's site?
Third, please only compile with 4.4.3 or the one Samsung recommends. Anything newer will probably not work.
Click to expand...
Click to collapse
1st
Processor : ARMv7 Processor rev 2 (v7l)
BogoMIPS : 99.40
Features : swp half thumb fastmult vfp edsp thumbee neon vfpv3
CPU implementer : 0x41
CPU architecture: 7
CPU variant : 0x2
CPU part : 0xc08
CPU revision : 2
Hardware : SMDKC110
Revision : 0000
Serial : 08c5603ec1690711
-rw-r--r-- 1 system system 118 Dec 25 12:19 default.prop
drwxr-xr-x 9 root root 2840 Jan 23 01:26 dev
drwxrwxr-x 1 radio system 0 Jan 23 01:26 efs
drwxr-xr-x 2 root root 0 Jan 23 01:26 emmc
lrwxrwxrwx 1 root root 11 Jan 23 01:26 etc -> /system/etc
-rwxr-xr-x 1 system system 1876 Dec 25 12:19 fota.rc
-rwxr-xr-x 1 system system 168364 Dec 25 12:27 init
-rw-r--r-- 1 system system 1677 Dec 25 12:19 init.goldfish.rc
-rwxr-xr-x 1 system system 30941 Dec 28 08:32 init.rc
-rwxr-xr-x 1 system system 30931 Dec 25 17:46 init.rc~
-rwxr-xr-x 1 system system 4489 Dec 25 12:19 init.smdkc110.rc
drwxr-xr-x 3 system system 0 Dec 25 12:19 lib
-rwxr-xr-x 1 system system 1419 Dec 25 12:19 lpm.rc
drwx------ 2 system system 0 Dec 26 16:21 misc
drwxrwxr-x 3 root root 0 Jan 23 01:26 mnt
drwxr-xr-x 2 root root 0 Jan 23 01:26 preload
dr-xr-xr-x 60 root root 0 Jan 1 1970 proc
-rwxr-xr-x 1 system system 410344 Dec 25 12:19 recovery
-rw-r--r-- 1 system system 2182 Dec 25 12:39 recovery.rc
drwxr-xr-x 3 system system 0 Dec 25 12:40 res
drwxr-xr-x 2 system system 0 Dec 26 16:31 sbin
drwxr-xr-x 2 root root 0 Jan 23 01:26 sdcard
drwxr-xr-x 12 root root 0 Jan 23 01:26 sys
drwxr-xr-x 1 root root 0 Jan 23 01:26 system
drwxrwxrwt 2 root root 60 Jan 23 01:26 tmp
-rw-r--r-- 1 system system 0 Dec 25 12:19 ueventd.goldfish.rc
-rw-r--r-- 1 system system 4245 Dec 25 12:19 ueventd.rc
-rwxr-xr-x 1 system system 1749 Dec 25 12:19 ueventd.smdkc110.rc
drwxrwxr-x 3 system system 0 Dec 28 08:33 vendor
init.rc~ file is the autocreated backup file that i forgot to erase
2nd
I downloaded YP-GB70-WW GB Opensource.zip
3rd
Yes I've been using the right toolchain that the readme file specified.
I have tried 4.4.3 too and many other toolchains.
4th
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
it's very normal... I had to fix this part of partition cause my partition was messed up beginning from block 12 but now it's perfect.
picture stolen from Siraki......
stylemate said:
1st
Processor : ARMv7 Processor rev 2 (v7l)
BogoMIPS : 99.40
Features : swp half thumb fastmult vfp edsp thumbee neon vfpv3
CPU implementer : 0x41
CPU architecture: 7
CPU variant : 0x2
CPU part : 0xc08
CPU revision : 2
Hardware : SMDKC110
Revision : 0000
Serial : 08c5603ec1690711
-rw-r--r-- 1 system system 118 Dec 25 12:19 default.prop
drwxr-xr-x 9 root root 2840 Jan 23 01:26 dev
drwxrwxr-x 1 radio system 0 Jan 23 01:26 efs
drwxr-xr-x 2 root root 0 Jan 23 01:26 emmc
lrwxrwxrwx 1 root root 11 Jan 23 01:26 etc -> /system/etc
-rwxr-xr-x 1 system system 1876 Dec 25 12:19 fota.rc
-rwxr-xr-x 1 system system 168364 Dec 25 12:27 init
-rw-r--r-- 1 system system 1677 Dec 25 12:19 init.goldfish.rc
-rwxr-xr-x 1 system system 30941 Dec 28 08:32 init.rc
-rwxr-xr-x 1 system system 30931 Dec 25 17:46 init.rc~
-rwxr-xr-x 1 system system 4489 Dec 25 12:19 init.smdkc110.rc
drwxr-xr-x 3 system system 0 Dec 25 12:19 lib
-rwxr-xr-x 1 system system 1419 Dec 25 12:19 lpm.rc
drwx------ 2 system system 0 Dec 26 16:21 misc
drwxrwxr-x 3 root root 0 Jan 23 01:26 mnt
drwxr-xr-x 2 root root 0 Jan 23 01:26 preload
dr-xr-xr-x 60 root root 0 Jan 1 1970 proc
-rwxr-xr-x 1 system system 410344 Dec 25 12:19 recovery
-rw-r--r-- 1 system system 2182 Dec 25 12:39 recovery.rc
drwxr-xr-x 3 system system 0 Dec 25 12:40 res
drwxr-xr-x 2 system system 0 Dec 26 16:31 sbin
drwxr-xr-x 2 root root 0 Jan 23 01:26 sdcard
drwxr-xr-x 12 root root 0 Jan 23 01:26 sys
drwxr-xr-x 1 root root 0 Jan 23 01:26 system
drwxrwxrwt 2 root root 60 Jan 23 01:26 tmp
-rw-r--r-- 1 system system 0 Dec 25 12:19 ueventd.goldfish.rc
-rw-r--r-- 1 system system 4245 Dec 25 12:19 ueventd.rc
-rwxr-xr-x 1 system system 1749 Dec 25 12:19 ueventd.smdkc110.rc
drwxrwxr-x 3 system system 0 Dec 28 08:33 vendor
init.rc~ file is the autocreated backup file that i forgot to erase
2nd
I downloaded YP-GB70-WW GB Opensource.zip
3rd
Yes I've been using the right toolchain that the readme file specified.
I have tried 4.4.3 too and many other toolchains.
Click to expand...
Click to collapse
Thanks. I edited my post after you quoted it. But from what you posted, everything looks in order. (A minor OCD is that you should delete init.rc~, but it shouldn't make a difference.)
It's somewhat a hunch, but try downloading the "YP-G1 US" source and compiling it with venturi_kor_defconfig,
And I'm not sure, as I don't have any of the Korean devices, but isn't there a difference between YP-G70 and YP-GB70? If so, then venturi may not even be the right config.
Mevordel said:
Thanks. I edited my post after you quoted it. But from what you posted, everything looks in order. (A minor OCD is that you should delete init.rc~, but it shouldn't make a difference.)
It's somewhat a hunch, but try downloading the "YP-G1 US" source and compiling it with venturi_kor_defconfig,
And I'm not sure, as I don't have any of the Korean devices, but isn't there a difference between YP-G70 and YP-GB70? If so, then venturi may not even be the right config.
Click to expand...
Click to collapse
DMB function and Camera is the major and maybe the only difference. But That doesn't really matter.
As long as i get bootable kernel I will be fine with it. Haha
Thank you, I will try with YP-G70 later.
Must be on VRUEMJ7 build and unrooted first!
Give these two a try and let us know which one works.
mod edit, vroot and kingo links removed per admin decision, site wide.
thought VROOT was a scam...
Yep
open1your1eyes0 said:
Just wanted to confirm you were on 100% stock not-rooted VRUEMJ7 build before?
Click to expand...
Click to collapse
Yes, its 100% stock. In fact, I had just reloaded to stock using the Verizon Repair tool becuase of my last failed attempt.
View attachment 2371104
TheJumpingBean said:
Yes, its 100% stock. In fact, I had just reloaded to stock using the Verizon Repair tool becuase of my last failed attempt.
View attachment 2371104
Click to expand...
Click to collapse
Excellent! :good:
Let's get a few more success posts and see which is the preferred method and I will make an official post about it.
???
wonger007 said:
thought VROOT was a scam...
Click to expand...
Click to collapse
This worked great for me. What do you mean by scam exactly?
---------- Post added at 12:24 PM ---------- Previous post was at 12:20 PM ----------
Also, this does not trip the Knox counter.
wonger007 said:
thought VROOT was a scam...
Click to expand...
Click to collapse
I heard the same. I would like to hear more feed back before trying it.
TheJumpingBean said:
Im trying to update the SU Binary, and it keeps failing. Is there a way to do this manually?
Click to expand...
Click to collapse
Possibly not since SELinux is likely blocking it. You might be able to do this with adb shell.
Also be aware you may have malware on your PC/phone now.
TheJumpingBean said:
Im trying to update the SU Binary, and it keeps failing. Is there a way to do this manually?
Click to expand...
Click to collapse
the process completed using the first method, but i dont see the chinese SU installed in my app drawer and no root access. I was able to install Super Su but it will not update as stated above.
Hmmm
joderme said:
Possibly not since SELinux is likely blocking it. You might be able to do this with adb shell.
Also be aware you may have malware on your PC/phone now.
Click to expand...
Click to collapse
Im still confused. The site that the file comes from is well known, has change logs and everything... Doesnt seem like it would be malware. Weird.
VRoot works, but like most are experiencing, cannot edit certain system files due to that pesky SELinux service. Maybe freezing the app/service with Titanium Backup would help.
However, I decided to use Kingo, seeing as everyone else had some success with VRoot, and I don't get any problems editing system files. Works perfectly. I used the emergency recovery wipe file and cleared the entire phone to MJ7, but I don't know how I stopped getting those notifications. I was actually getting them even when I didn't have root.
Anyone have the SuperSU Binary
joderme said:
Possibly not since SELinux is likely blocking it. You might be able to do this with adb shell.
Also be aware you may have malware on your PC/phone now.
Click to expand...
Click to collapse
Does anyone have the su binary for the latest SuperSU? Im willing to give it a try in shell.
Thx,
Maria
Also: Looks like the SU application is: com.noshufou.android.su-1.apk in the /data/app directory.
dothog said:
VRoot works, but like most are experiencing, cannot edit certain system files due to that pesky SELinux service. Maybe freezing the app/service with Titanium Backup would help.
However, I decided to use Kingo, seeing as everyone else had some success with VRoot, and I don't get any problems editing system files. Works perfectly. I used the emergency recovery wipe file and cleared the entire phone to MJ7, but I don't know how I stopped getting those notifications. I was actually getting them even when I didn't have root.
Click to expand...
Click to collapse
Did Kingo trip the knox warranty trigger?
Same results here. VROOT was successful, however SuperSU cannot update it's binaries.
Kingo
dothog said:
VRoot works, but like most are experiencing, cannot edit certain system files due to that pesky SELinux service. Maybe freezing the app/service with Titanium Backup would help.
However, I decided to use Kingo, seeing as everyone else had some success with VRoot, and I don't get any problems editing system files. Works perfectly. I used the emergency recovery wipe file and cleared the entire phone to MJ7, but I don't know how I stopped getting those notifications. I was actually getting them even when I didn't have root.
Click to expand...
Click to collapse
Did you reroot with Kingo? Didn't you try the other one first?
joderme said:
Did Kingo trip the knox warranty trigger?
Click to expand...
Click to collapse
No, not for me. Knox still shows 0x0 so far. I guess its where I have a totally clean slate. Im really thinking most people's problems is due to them using incomplete wipes, or by using recovery-done factory resets. Safestrap's factory reset tries to keep root, and itself, intact, so anyone who used that in preparation for update to MJ7 might have problems.
---------- Post added at 07:10 PM ---------- Previous post was at 07:05 PM ----------
TheJumpingBean said:
Did you reroot with Kingo? Didn't you try the other one first?
Click to expand...
Click to collapse
Yeah, I did VRoot, then reflashed the emergency recovery with Odin, then tried again with Kingo. I did that because I didn't see any people bothering with Kingo because VRoot worked fine for the most part.
I've just asked the mods to delete this thread as it's very likely causing people to infect their PCs and their phones.
VRoot and Kingo install a SuperSU program that has a network backdoor to China. You've given someone full control of your phone.
They also modify your PC's IE configuration, apparently for the same thing.
Why you can't replace the hacked SuperSU is because the malware won't let you.
These rooting programs may work, but they're closed-source and have behavior that can't be explained.
If I had installed this mistakenly, I'd wipe my phone *and* my PC and reinstall from scratch.
k1mu said:
I've just asked the mods to delete this thread as it's very likely causing people to infect their PCs and their phones.
VRoot and Kingo install a SuperSU program that has a network backdoor to China. You've given someone full control of your phone.
They also modify your PC's IE configuration, apparently for the same thing.
Why you can't replace the hacked SuperSU is because the malware won't let you.
These rooting programs may work, but they're closed-source and have behavior that can't be explained.
If I had installed this mistakenly, I'd wipe my phone *and* my PC and reinstall from scratch.
Click to expand...
Click to collapse
I think the less paranoid explanation is that the su app has an auto-update feature and since the app isn't hosted in the Play Store, a connection to a chinese server doesn't see all that unexpected.
Do not install
At this point I have every reason to believe there is a huge threat with rooting this way. The su binary starts a listening server and remains connected:
unix 3 [ ] STREAM CONNECTED 5629 3127/su /dev/com.mgyun.shua.su.daemon/server
unix 3 [ ] STREAM CONNECTED 11730 3118/.suv
---------- Post added at 01:55 PM ---------- Previous post was at 01:52 PM ----------
[email protected]:/dev # ls -la
ls -la
---------- root root 0 1970-03-11 22:45 .coldboot_done
drwx--x--x system system 1970-03-11 22:45 .secure_storage
-rw-r--r-- root root 66560 1970-03-11 22:45 __properties__
crw-rw-r-- system radio 10, 25 1970-03-11 22:45 alarm
crw-rw---- adb adb 10, 30 1970-03-11 22:45 android_adb
crw-rw-rw- root root 10, 21 1970-03-11 22:45 ashmem
crw------- nfc nfc 10, 34 1970-03-11 22:45 bcm2079x
crw-rw-rw- root root 10, 22 1970-03-11 22:45 binder
drwxr-xr-x root root 2013-11-04 13:26 block
crw------- bluetooth bluetooth 10, 224 1970-03-11 22:45 btlock
drwxr-xr-x root root 1970-03-11 22:45 bus
crw------- root root 10, 28 1970-03-11 22:45 ccid_bulk
crw------- root root 10, 29 1970-03-11 22:45 ccid_ctrl
drwxrwx--- u0_a247 u0_a247 2013-11-04 13:26 com.mgyun.shua.su
drwxr-xr-x root root 2013-11-04 13:43 com.mgyun.shua.su.daemon
crw------- root root 5, 1 1970-03-11 22:45 console
In all fairness that could be an update daemon.
DroidHaxxor said:
At this point I have every reason to believe there is a huge threat with rooting this way. The su binary starts a listening server and remains connected:
unix 3 [ ] STREAM CONNECTED 5629 3127/su /dev/com.mgyun.shua.su.daemon/server
unix 3 [ ] STREAM CONNECTED 11730 3118/.suv
---------- Post added at 01:55 PM ---------- Previous post was at 01:52 PM ----------
[email protected]:/dev # ls -la
ls -la
---------- root root 0 1970-03-11 22:45 .coldboot_done
drwx--x--x system system 1970-03-11 22:45 .secure_storage
-rw-r--r-- root root 66560 1970-03-11 22:45 __properties__
crw-rw-r-- system radio 10, 25 1970-03-11 22:45 alarm
crw-rw---- adb adb 10, 30 1970-03-11 22:45 android_adb
crw-rw-rw- root root 10, 21 1970-03-11 22:45 ashmem
crw------- nfc nfc 10, 34 1970-03-11 22:45 bcm2079x
crw-rw-rw- root root 10, 22 1970-03-11 22:45 binder
drwxr-xr-x root root 2013-11-04 13:26 block
crw------- bluetooth bluetooth 10, 224 1970-03-11 22:45 btlock
drwxr-xr-x root root 1970-03-11 22:45 bus
crw------- root root 10, 28 1970-03-11 22:45 ccid_bulk
crw------- root root 10, 29 1970-03-11 22:45 ccid_ctrl
drwxrwx--- u0_a247 u0_a247 2013-11-04 13:26 com.mgyun.shua.su
drwxr-xr-x root root 2013-11-04 13:43 com.mgyun.shua.su.daemon
crw------- root root 5, 1 1970-03-11 22:45 console
Click to expand...
Click to collapse
if we uninstall the Chinese SU app is the phone clean.. or do i need a full wipe?
Also my PC appears to RUN OK. looking for any malware but don't see any.
DroidHaxxor said:
At this point I have every reason to believe there is a huge threat with rooting this way. The su binary starts a listening server and remains connected:
unix 3 [ ] STREAM CONNECTED 5629 3127/su /dev/com.mgyun.shua.su.daemon/server
unix 3 [ ] STREAM CONNECTED 11730 3118/.suv
---------- Post added at 01:55 PM ---------- Previous post was at 01:52 PM ----------
[email protected]:/dev # ls -la
ls -la
---------- root root 0 1970-03-11 22:45 .coldboot_done
drwx--x--x system system 1970-03-11 22:45 .secure_storage
-rw-r--r-- root root 66560 1970-03-11 22:45 __properties__
crw-rw-r-- system radio 10, 25 1970-03-11 22:45 alarm
crw-rw---- adb adb 10, 30 1970-03-11 22:45 android_adb
crw-rw-rw- root root 10, 21 1970-03-11 22:45 ashmem
crw------- nfc nfc 10, 34 1970-03-11 22:45 bcm2079x
crw-rw-rw- root root 10, 22 1970-03-11 22:45 binder
drwxr-xr-x root root 2013-11-04 13:26 block
crw------- bluetooth bluetooth 10, 224 1970-03-11 22:45 btlock
drwxr-xr-x root root 1970-03-11 22:45 bus
crw------- root root 10, 28 1970-03-11 22:45 ccid_bulk
crw------- root root 10, 29 1970-03-11 22:45 ccid_ctrl
drwxrwx--- u0_a247 u0_a247 2013-11-04 13:26 com.mgyun.shua.su
drwxr-xr-x root root 2013-11-04 13:43 com.mgyun.shua.su.daemon
crw------- root root 5, 1 1970-03-11 22:45 console
In all fairness that could be an update daemon.
Click to expand...
Click to collapse
That's not a listening network server, it's a local RPC daemon. That may be how the su program talks to the new SuperSU program.
What do you see if you try
$ netstat -an | grep LISTEN
That will show you any existing network listeners that anyone could connect to.
$ netstat -an | grep ESTAB
will show you established connections.
Hi
I've finished fully automatic unbricker for Sony Xperia Tablet S!
Code:
It wouldn't be possible without xda users, xda community, especially:
deltaztek [SD source],
jappaj [shell access],
NerdiX [beta tester],
and all other users, who helped to get it working!
Source thread where manual solution has been discovered.
Ladies & Gentlemen...
S.onyXT.S [UNBRICKER] !
[What is this?]
S.onyXT.S [UNBRICKER] will unbrick your device firmware,
no need any shell/linux knowledge - step by step, everything automatic.
It will automatically download needed data.
Unbrick process includes:
downloading "magic SD" prepared image (237mb),
downloading proper update data,
decrypting, extracting update data,
auto making "magic SD" - no need win32imager etc.,
uploading update data to device,
at last - unbricking device - flashing system/hidden partitions.
[Requirements]:
- internet connection to download data ,
- adb drivers correctly installed,
- min. 2GB SD card.
[Changelog]:
Code:
[09.02.2014] v1.0:
- initial version.
[To-Do]:
Code:
- datapp flashing - vendor apps fix,
[Screenshots:]
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
[Download]:
Attached to this thread.
[Donate]:
Keep this project alive - don't forget to donate!
br
condi
current_version=1.0
LEGEND ONCE AGAIN....
If only we had something for out older Tabs
Oh well none the less one more step in the right direction
stifilz said:
LEGEND ONCE AGAIN....
If only we had something for out older Tabs
Oh well none the less one more step in the right direction
Click to expand...
Click to collapse
@condi i have a problem and a question....first the question...why when i type the letter in upper case the tools reboot? and when i type il lower case it say unity doesn't specified....but it continue ....how i must put the letter in up or lowercase? and i'm waiting the cold-booting write but it doesn't appear how much it will take?
masterchif92 said:
@condi i have a problem and a question....first the question...why when i type the letter in upper case the tools reboot? and when i type il lower case it say unity doesn't specified....but it continue ....how i must put the letter in up or lowercase? and i'm waiting the cold-booting write but it doesn't appear how much it will take?
Click to expand...
Click to collapse
hi masterchif,
you type drive letter only? or with ":" ?
br
condi
condi said:
hi masterchif,
you type drive letter only? or with ":" ?
br
condi
Click to expand...
Click to collapse
Only che letter in lowercase ....is important if it is in lower or upper? My tablet is brick I think is stopped in Sony logo....u can help me ? I bricked it while trying to install jb from tool flasher but something went wrong
Inviato dal mio Nexus 5 utilizzando Tapatalk
masterchif92 said:
Only che letter in lowercase ....is important if it is in lower or upper? My tablet is brick I think is stopped in Sony logo....u can help me ? I bricked it while trying to install jb from tool flasher but something went wrong
Inviato dal mio Nexus 5 utilizzando Tapatalk
Click to expand...
Click to collapse
I've just tried - it worked well. No matter if its uppercase or lowercase - it worked well for me.
What windows version you have?
The only problem occured, when I had opened windows explorer, with sd card opened,
or even with my computer - sd card volume became busy, and unbricker couldn't write.
But to get it work - you have only to close all explorer windows.
Could you make screenshot of the issue?
It write on SD but the problem is when I wait for cold boot....I'll wait 1 hrs and it doesn't appear..... My PC says unknown device and the tablet with the SD on stop on Sony logo no cold-booting write
Inviato dal mio Nexus 5 utilizzando Tapatalk
masterchif92 said:
It write on SD but the problem is when I wait for cold boot....I'll wait 1 hrs and it doesn't appear..... My PC says unknown device and the tablet with the SD on stop on Sony logo no cold-booting write
Inviato dal mio Nexus 5 utilizzando Tapatalk
Click to expand...
Click to collapse
Wait wait, what tablet model/version exactly you have?
WiFi tablet s , abile tryng ti install JB i got an error and when it reboot it stays on Sony logo then I try your tools only recovery mode
Inviato dal mio Nexus 5 utilizzando Tapatalk
masterchif92 said:
WiFi tablet s , abile tryng ti install JB i got an error and when it reboot it stays on Sony logo then I try your tools only recovery mode
Inviato dal mio Nexus 5 utilizzando Tapatalk
Click to expand...
Click to collapse
I'm sorry but solution is ONLY for 2nd tab gen - XPERIA TABLET S!
br
condi
O....sorry....but u can help me? I have problem with checking region ...I download 001 version that is mine but gives me always SKU error
Inviato dal mio Nexus 5 utilizzando Tapatalk
masterchif92 said:
O....sorry....but u can help me? I have problem with checking region ...I download 001 version that is mine but gives me always SKU error
Inviato dal mio Nexus 5 utilizzando Tapatalk
Click to expand...
Click to collapse
You have softed bricked your device by trying to install jb to your device
Reading is your friend google even more so
This recovery is for the xperia tab s not for the first sony tab s
By trying to install a firmware that does not fit your device nor has it ever
Next time try reading a little bit about the tools you are about to use on your device and what is needed
The sku error is because the device thinks the firmware your trying to flash is the same as the one previous an a conflict arises
So far there is no known recovery from this other than an offical sony repair centre
xperia m c1905 stock rooted lb
and sony XTS rooted stock j.b thanks djrbliss
dex9mm said:
You have softed bricked your device by trying to install jb to your device
Reading is your friend google even more so
This recovery is for the xperia tab s not for the first sony tab s
By trying to install a firmware that does not fit your device nor has it ever
Next time try reading a little bit about the tools you are about to use on your device and what is needed
The sku error is because the device thinks the firmware your trying to flash is the same as the one previous an a conflict arises
So far there is no known recovery from this other than an offical sony repair centre
xperia m c1905 stock rooted lb
and sony XTS rooted stock j.b thanks djrbliss
Click to expand...
Click to collapse
I see it now.....very disappointed with Sony.... I'll never buy a Sony tablet or smartphone !!! Now I try two more firmware but if I flashed the xperia tablet s in a tablet s I don't think that I can recover it right ?
Inviato dal mio Nexus 5 utilizzando Tapatalk
condi said:
Hi
I've finished fully automatic unbricker for Sony Xperia Tablet S!
[To-Do]:
Code:
- datapp flashing - vendor apps fix,
br
condi
current_version=1.0
Click to expand...
Click to collapse
hello friend
I saw that you removed the datapp lines in the script
as I wrote in the other topic, links to vendor directory are for a specific country
Sony factory script at first startup wants to choose country then obviously resets symlinks for specific directory.
Now my IR works with Panasonic and other tv... ir database seems well
I must clarify that after the manual procedure in dd mmcblk0p3(and 4), the tablet is not updating correctly in recovery. He wrote in mmcblk0p3 and mmcblk0p9 (vendor0 only), then check passed correctly.
Whether updating with jbr1 or jbr2 file is getting the same result, booted the system1 from mmcblk0p4 with jbr1 (not r2), i.e. not been updated, and sonys app not worked.
I had to dd if=/dev/block/mmcblk0p3(updated thru recovery) of=/dev/block/mmcblk0p4 to be the same, read the post of @jappaj to fix datapp symlinks, then the update went correctly thru recovery from jbr1 to jbr2
EDIT: maybe /data partition (/dev/block/mmcblk0p11) must be formated (factory reset) to triger sony's script to ask for country and autoset correct symlinks
I am waiting for tablet P unbricker release.
i beg you for same tool, but for tablet S !!))
im getting invalid drive specification
what does that mean
this dd.exe did not work as expecded. same problem on my win7 laptop
I have mostly rewritten the script for bash / linux shell
IT WORKED
THANKS @condi
PS: why not trying to use the SD-image to flash KitKat?
i mean, you can pull all mmc images and flash all mmc images via dd, why not writing a custom rom this way? the only problem is the kernel.
mounts of /dev/block/*
mmcblk0p1 -> /configs
-r--r--r-- 1 root root 64 Jan 1 2000 06590E37F8A647D989345317AAFF6A6C
-r--r--r-- 1 root root 242 Jan 1 2000 31850B1B-0DAB-42ce-A498-A73479B7B3EB
-r--r--r-- 1 root root 878 Jan 1 2000 calibration_rear.bin
-r--r--r-- 1 root root 63104 Jan 1 2000 CFBSMXHMUAF48EXTDTCSOH4BXXDDRBFG
-r--r--r-- 1 root root 132 Jan 1 2000 local.propmmcblk0p2 -> /params
-rw------- 1 root root 2 Jan 30 14:43 activate_done
lrwxrwxrwx 1 root root 57 Jan 30 14:43 countries.lst -> /datapp/vendor/vendor0/regioncodelist/SKU002000172608.lst
drwx------ 2 root root 4096 Jan 1 1970 lost+found
-rw-r--r-- 1 root root 33 Jan 30 14:43 region_checksum.txt
-rw-r--r-- 1 root root 9706 Jan 30 14:43 region.zip
-rw-rw-rw- 1 root root 2 Jan 30 14:43 selected_countrymmcblk0p3 -> /system
mmcblk0p4 -> /system (copy)
mmcblk0p5 -> /cache
(ls /cache/recovery)
-rw-r--r-- 1 root root 45 Jan 1 2000 last_install
-rw-r----- 1 root root 22626 Jan 1 2000 last_log
-rw------- 1 stth stth 18769 Jan 1 2000 logmmcblk0p6 -> not mounted (2MB, file system?, image not mountable as loop device)
mmcblk0p7 -> not mounted (64MB, file system?, image not mountable as loop device)
mmcblk0p8 -> not mounted (2MB, file system?, image not mountable as loop device)
mmcblk0p9 -> /datapp (vendor)
mmcblk0p10 -> /log
-rw-r--r-- 1 root root 18652 Jan 1 2000 recovery_abort.logmmcblk0p11 -> /data
judging the size of the unknown partitions, mmcblk0p7 could contain the kernel. probably we just have to find the file system on this partition. i guess, sony just skips a part or descrambles the partition while it shows the sony logo (which is always displayed, no matter if you boot into recovery, or the system) also, the hidden.img is flashed there... so... how to get it out?
what are the files in /configs? maybe keys or executables to decrypt the kernel?
does anybody have a log of a successful update in the logs (see mount list above)? is there any information about an updated kernel?
to get the mmc-images, just create the unbricker sd card (it does not break anything if you stop the script after the sd is written)
execute adb shell "/system/xbin/pwn"
then adb pull /dev/block/mmcblk*
on linux, you can mount them with
mount -o loop <image> <mountpoint>
some require root to view files
if anything is broken, we should be able to reflash all mmcblk-images which of couse should be backed up in advance
€:
today i scanned the sd image and the hidden.img seems, that the tablet would boot any kernel that is at position 0x00000400 on a sd card.
you may copy any image from OTA update.zip to that position and it should load it.
$ dd if=unbrick.img of=/dev/sdXXX
$ dd if=hidden.img of=/dev/sdXXX bs=512 seek=2
i tried the kernel from a tablet s on the xts and settings/about/kernel told me it worked!!
sadly, the data in hidden.img looks similiar to kernels of other SE devices, but is somehow scrambled
stth said:
IT WORKED
THANKS @condi
PS: why not trying to use the SD-image to flash KitKat?
i mean, you can pull all mmc images and flash all mmc images via dd, why not writing a custom rom this way? the only problem is the kernel.
mounts of /dev/block/*
mmcblk0p1 -> /configs
-r--r--r-- 1 root root 64 Jan 1 2000 06590E37F8A647D989345317AAFF6A6C
-r--r--r-- 1 root root 242 Jan 1 2000 31850B1B-0DAB-42ce-A498-A73479B7B3EB
-r--r--r-- 1 root root 878 Jan 1 2000 calibration_rear.bin
-r--r--r-- 1 root root 63104 Jan 1 2000 CFBSMXHMUAF48EXTDTCSOH4BXXDDRBFG
-r--r--r-- 1 root root 132 Jan 1 2000 local.propmmcblk0p2 -> /params
-rw------- 1 root root 2 Jan 30 14:43 activate_done
lrwxrwxrwx 1 root root 57 Jan 30 14:43 countries.lst -> /datapp/vendor/vendor0/regioncodelist/SKU002000172608.lst
drwx------ 2 root root 4096 Jan 1 1970 lost+found
-rw-r--r-- 1 root root 33 Jan 30 14:43 region_checksum.txt
-rw-r--r-- 1 root root 9706 Jan 30 14:43 region.zip
-rw-rw-rw- 1 root root 2 Jan 30 14:43 selected_countrymmcblk0p3 -> /system
mmcblk0p4 -> /system (copy)
mmcblk0p5 -> /cache
(ls /cache/recovery)
-rw-r--r-- 1 root root 45 Jan 1 2000 last_install
-rw-r----- 1 root root 22626 Jan 1 2000 last_log
-rw------- 1 stth stth 18769 Jan 1 2000 logmmcblk0p6 -> not mounted (2MB, file system?, image not mountable as loop device)
mmcblk0p7 -> not mounted (64MB, file system?, image not mountable as loop device)
mmcblk0p8 -> not mounted (2MB, file system?, image not mountable as loop device)
mmcblk0p9 -> /datapp (vendor)
mmcblk0p10 -> /log
-rw-r--r-- 1 root root 18652 Jan 1 2000 recovery_abort.logmmcblk0p11 -> /data
judging the size of the unknown partitions, mmcblk0p7 could contain the kernel. probably we just have to find the file system on this partition. i guess, sony just skips a part or descrambles the partition while it shows the sony logo (which is always displayed, no matter if you boot into recovery, or the system) also, the hidden.img is flashed there... so... how to get it out?
what are the files in /configs? maybe keys or executables to decrypt the kernel?
does anybody have a log of a successful update in the logs (see mount list above)? is there any information about an updated kernel?
to get the mmc-images, just create the unbricker sd card (it does not break anything if you stop the script after the sd is written)
execute adb shell "/system/xbin/pwn"
then adb pull /dev/block/mmcblk*
on linux, you can mount them with
mount -o loop <image> <mountpoint>
some require root to view files
if anything is broken, we should be able to reflash all mmcblk-images which of couse should be backed up in advance
€:
today i scanned the sd image and the hidden.img seems, that the tablet would boot any kernel that is at position 0x00000400 on a sd card.
you may copy any image from OTA update.zip to that position and it should load it.
$ dd if=unbrick.img of=/dev/sdXXX
$ dd if=hidden.img of=/dev/sdXXX bs=512 seek=2
i tried the kernel from a tablet s on the xts and settings/about/kernel told me it worked!!
sadly, the data in hidden.img looks similiar to kernels of other SE devices, but is somehow scrambled
Click to expand...
Click to collapse
That is just some great work. Were the kernel different? But anyway it could be secure for bootloader check if there is any. Cause it is a tablet s kernel. I have a kernel which have kexec built in for tablet s. I can give it to you for testing if you want. And if you wanna join our hangout, just pm me
Sent from my Sony Tablet S using Tapatalk
This is a port of stock the Nexus7 (Grouper) 4.1.2 ROM with the Nabi 2 OTA 2.4.6 as the base. Everything seems to be working but as the title says it is a beta and so not fully tested....FLASH AT YOUR OWN RISK!!!!
Couple of things to be aware of: You have to update some of the apps before they work (Chrome for instance) and when adjusting the brightness it is possible to turn the screen all the way black, don't panic, just slide it back to the right...oh, and if you try to skip turning on the wifi it still tries to connect but it will eventually time out. If anyone actually uses the Nabi camera I have found that the Nexus 7 Camera app from the play store will work, other ones might also but I tested that one. There are no HDMI settings right now because the Nexus didn't have that port but the HDMI does work.
Screenshot:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Instructions:
1. Make a full TWRP backup to external sdcard!!! AND make sure your backup works!!!
2. Download the zip and place it on your external sdcard.
3. Wipe everything except external sdcard.
4. Install the zip.
5. Wipe cache and davlik again for good measure.
6. Reboot and do a little happy dance!!! (First boot takes a while so don't freak after 30 secs, lol)
Download: Nabixus_beta0.1.zip , Mirror1, or Mirror2
MD5: b334707cf14b2ad4e552d6a7a3b48fcd
Let me know what you think, I know there's room for improvement....and I'll fix this post up some at some point, give me a break it's my first time!!
reserved
reserved 2
First! LOL. Glad you got it going. If you need any help or any stock files from my newly acquired Nexus 7, let me know. I can make a complete nandroid if needed.
Additional screenshots!
Can't spend too much time fooling around with it before the kids get up, but looks good for now! Thanks for the awesome work!
Just to report, all is well with the port. Just getting a bit of screen flicker but that is due to the low brightness level. It has gone away since I have raised it up all the way. All apps updating fine via Playstore and OTG USB working great as well. Side loading a lot of what I call my "Power Rooting Apps". This reminds me of the nexus 7 I just got LOL. Great job!
Dude! YOU ROCK....
Now when my son upgrades, I'll be able to use the nabi for kodi (xbmc) on the tv.
Sent from my Nexus 7 using Tapatalk
Awesome, can't wait till I have a moment free to give this a try!
Sent from my Nexus 10 using Tapatalk
@n3wt GREAT job, just wanted to know if I build CyanogenMod for Nexus 7 2012; could you port CyanogenMod over to Nabi?
katinatez said:
@n3wt GREAT job, just wanted to know if I build CyanogenMod for Nexus 7 2012; could you port CyanogenMod over to Nabi?
Click to expand...
Click to collapse
I've been trying to port CM the past few days and keep getting stuck at a never ending boot animation. So yeah, if you guys could give it a shot that would be great, lol.
katinatez said:
if I build CyanogenMod for Nexus 7 2012; could you port CyanogenMod over to Nabi?
Click to expand...
Click to collapse
maybe. aicjofs suggested that the kernel might be too different though. I have a cm with tablet ui for the Nexus that I was looking at but I'm toying with the idea of trying to get a working kernel compiled. ... That way we could just build a rom for the nabi.
It took a lot of hours to get to this point though so whatever comes next will be after a bit of rest.
I'm really happy that you guys are liking this one, feel free to take it and mod it and what not.
SMcC2 said:
I've been trying to port CM the past few days and keep getting stuck at a never ending boot animation. So yeah, if you guys could give it a shot that would be great, lol.
Click to expand...
Click to collapse
Do you have adb working?
ROFL
Anyone else get the email
"Hello from Google: Get the most out of your Nexus 7" ?
n3wt said:
Do you have adb working?
Click to expand...
Click to collapse
I had it working at one point, but don't remember how I had gotten there.
I've been using these links as resources:
How to Build CyanogenMod for Grouper
How to Port CyanogenMod to new Devices
Kernel Building for CyanogenMod
The instructions for building on Grouper say to pull the proprietary blobs from a device with CyanogenMod already installed. I don't have that option.
Note:
Your device should already be running a build of CyanogenMod for the branch you wish to build for the extract-files.sh script to function properly. Nexus users: While it maybe be tempting to run the script on stock Android, and in fact it may succeed, realize that some of the blobs CyanogenMod uses are modified or otherwise different from stock blobs (e.g. Adreno graphics libraries). Save yourself some trouble and install a copy of CyanogenMod on your device before extracting blobs.
Click to expand...
Click to collapse
The instructions for porting to new devices says
Create extract-files.sh and setup-makefiles.sh scripts to pull those blob files from the device using adb and put them in the right /vendor/ directory. There are plenty of examples available for other devices.
Create an .mk Makefile to copy those files to the $OUT folder during the build process and put them in the right place. Again, use other devices as a guide for what this Makefile should look like. An example filename might be BoardConfigVendor.mk
Make sure that the Makefile you just created is included from your main BoardConfig.mk via a command such as -include vendor/[vendor]/[codename]/BoardConfigVendor.mk. Again, existing devices can illustrate how this is done.
Click to expand...
Click to collapse
I don't think I'm getting everything when I do that and that's where my problem is...
maybe. aicjofs suggested that the kernel might be too different though.
Click to expand...
Click to collapse
The Nabi kernel should be based on AOSP, so that is the best ROM's to work with for best compatibility. AOKP, and CM being there own breed might need some kernel mods. For example on current Qualcomm devices CM is using CAF code and AOSP is using google kernel code. Just an example
Anyone else get the email
Click to expand...
Click to collapse
Could be this in build.prop.
ro.build.fingerprint=google/nakasi/grouper:4.1.2/JZO54K/485486:user/release-keys
or a special bit of code in email program.
Create extract-files.sh and setup-makefiles.sh scripts to pull those blob files from the device using adb and put them in the right /vendor/ directory. There are plenty of examples available for other devices.
Click to expand...
Click to collapse
Yeah you have to do it all manually(make proprietary-files.txt). I did it once but it was all manual, and I could have missed something, it took hours. I also remember having a failure pulling the firmware files in the /vendor directory. You can look at what I did in attached
@n3wt You should write up some of your secret sauce, would help those guys mimic what you did on other ROM's
aicjofs said:
Yeah you have to do it all manually(make proprietary-files.txt). I did it once but it was all manual, and I could have missed something, it took hours. I also remember having a failure pulling the firmware files in the /vendor directory. You can look at what I did in attached
Click to expand...
Click to collapse
I was afraid it might have to be done manually.
SMcC2 said:
I've been trying to port CM the past few days and keep getting stuck at a never ending boot animation. So yeah, if you guys could give it a shot that would be great, lol.
Click to expand...
Click to collapse
Same here LOL. I have been trying to port CleanRom 4.0.0 JB 4.3 from my Nexus 7 but am stuck at the 4 rotating orbs. I have the boot image decompiled and the complete System files from my Nexus 7 if anyone would like to give it a try.
aicjofs said:
@n3wt You should write up some of your secret sauce, would help those guys mimic what you did on other ROM's
Click to expand...
Click to collapse
Yes please, I have dissected the rom to see the differences and have gotten as far as I have so far. It is very time consuming for sure. I have 4.1.2 Modded to the bone at the moment.
In case anyone wants the info:Off my Nexus 7 Running CleanRom 4.0.0 4.3 JB.
Code:
(dev/block/platform/sdhci-tegra.3/by-name)
[email protected]:/ $ cat /proc/partitions
cat /proc/partitions
major minor #blocks name
7 0 2111 loop0
7 1 11466 loop1
7 2 9387 loop2
7 3 4190 loop3
7 4 28098 loop4
7 5 61362 loop5
7 6 8348 loop6
7 7 53046 loop7
179 0 31178752 mmcblk0
179 1 12288 mmcblk0p1
179 2 8192 mmcblk0p2
179 3 665600 mmcblk0p3
179 4 453632 mmcblk0p4
179 5 512 mmcblk0p5
179 6 10240 mmcblk0p6
179 7 5120 mmcblk0p7
179 8 512 mmcblk0p8
179 9 30014464 mmcblk0p9
179 32 2048 mmcblk0boot1
179 16 2048 mmcblk0boot0
254 0 2110 dm-0
254 1 11466 dm-1
254 2 9387 dm-2
254 3 4189 dm-3
254 4 28098 dm-4
254 5 61362 dm-5
254 6 8347 dm-6
254 7 53046 dm-7
7 8 2111 loop8
254 8 2110 dm-8
=============================================
[email protected]:/ $ ls -al /dev/block/platform/sdhci-tegra.3/by-name
ls -al /dev/block/platform/sdhci-tegra.3/by-name
lrwxrwxrwx root root 2014-10-04 12:29 APP -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2014-10-04 12:29 CAC -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2014-10-04 12:29 LNX -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2014-10-04 12:29 MDA -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2014-10-04 12:29 MSC -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2014-10-04 12:29 PER -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2014-10-04 12:29 SOS -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2014-10-04 12:29 UDA -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2014-10-04 12:29 USP -> /dev/block/mmcblk0p6
[COLOR=Red]=============================================[/COLOR]
[COLOR=DarkRed][B]( fstab.grouper )[/B][/COLOR]
[COLOR=Red]==================================[/COLOR]
# Android fstab file.
#<src> <mnt_point> <type> <mnt_flags> <fs_mgr_flags>
# The filesystem that contains the filesystem checker binary (typically /system) cannot
# specify MF_CHECK, and must come before any filesystems that do specify MF_CHECK
/dev/block/platform/sdhci-tegra.3/by-name/APP /system ext4 noatime,nodiratime,nodev,noauto_da_alloc wait
/dev/block/platform/sdhci-tegra.3/by-name/CAC /cache ext4 noatime,nodiratime,nosuid,nodev,data=writeback,noauto_da_alloc,nomblk_io_submit,errors=panic wait
/dev/block/platform/sdhci-tegra.3/by-name/UDA /data ext4 noatime,nodiratime,nosuid,nodev,data=writeback,noauto_da_alloc,nomblk_io_submit,errors=panic wait,encryptable=/dev/block/platform/sdhci-tegra.3/by-name/MDA
/dev/block/platform/sdhci-tegra.3/by-name/MSC /misc emmc defaults defaults
/dev/block/platform/sdhci-tegra.3/by-name/LNX /boot emmc defaults defaults
/dev/block/platform/sdhci-tegra.3/by-name/SOS /recovery emmc defaults defaults
/dev/block/platform/sdhci-tegra.3/by-name/USP /staging emmc defaults defaults
/devices/platform/tegra-ehci /storage/usbdisk vfat defaults voldmanaged=usbdisk:auto
[COLOR=Red]---------------------------------------------[/COLOR]
[B][COLOR=DarkRed]( fstab.grouper~ )[/COLOR][/B]
[COLOR=Red]-------------------------------------[/COLOR]
# Android fstab file.
#<src> <mnt_point> <type> <mnt_flags> <fs_mgr_flags>
# The filesystem that contains the filesystem checker binary (typically /system) cannot
# specify MF_CHECK, and must come before any filesystems that do specify MF_CHECK
/dev/block/platform/sdhci-tegra.3/by-name/APP /system ext4 ro wait
/dev/block/platform/sdhci-tegra.3/by-name/CAC /cache ext4 noatime,nosuid,nodev,nomblk_io_submit,errors=panic wait
/dev/block/platform/sdhci-tegra.3/by-name/UDA /data ext4 noatime,nosuid,nodev,nomblk_io_submit,errors=panic wait,encryptable=/dev/block/platform/sdhci-tegra.3/by-name/MDA
/dev/block/platform/sdhci-tegra.3/by-name/MSC /misc emmc defaults defaults
/dev/block/platform/sdhci-tegra.3/by-name/LNX /boot emmc defaults defaults
/dev/block/platform/sdhci-tegra.3/by-name/SOS /recovery emmc defaults defaults
/dev/block/platform/sdhci-tegra.3/by-name/USP /staging emmc defaults defaults
/devices/platform/tegra-ehci /storage/usbdisk vfat defaults voldmanaged=usbdisk:auto
SMcC2 said:
I was afraid it might have to be done manually.
Click to expand...
Click to collapse
Well look over the zip I posted maybe it can save some time.
DarkAngel said:
Same here LOL. I have been trying to port CleanRom 4.0.0 JB 4.3
Click to expand...
Click to collapse
Above 4.2 you will need SElinux support in kernel, so I don't 4.3 is going to work.
aicjofs said:
Well look over the zip I posted maybe it can save some time.
Above 4.2 you will need SElinux support in kernel, so I don't 4.3 is going to work.
Click to expand...
Click to collapse
I know but I had to try.
You think I could just ls the vendor file and copy it in to a text file with the right format?
Here is an example from my HTC...
[email protected]:/ $ cd system
[email protected]:/system $ cd vendor
[email protected]:/system/vendor $ ls */*
etc/audio_effects.conf
firmware/acdb.mbn
firmware/apps.mbn
firmware/bcm4335_prepatch.hcd
firmware/dsp1.mbn
firmware/dsp2.mbn
firmware/dsp3.mbn
firmware/efs1.mbn
firmware/efs2.mbn
firmware/efs3.mbn
firmware/htc61.mbn
firmware/htc62.mbn
firmware/htc63.mbn
firmware/htc64.mbn
firmware/htc65.mbn
firmware/htccdma.mbn
firmware/htcnvbak.mbn
firmware/htcrcust.mbn
firmware/htcrfnv.mbn
firmware/htcsmem.mbn
firmware/htcssmem.mbn
keymaster.b00
keymaster.b01
keymaster.b02
keymaster.b03
keymaster.mdt
firmware/mdm_acdb.img
firmware/q6.b00
firmware/q6.b01
firmware/q6.b03
firmware/q6.b04
firmware/q6.b05
firmware/q6.b06
firmware/q6.mdt
firmware/rpm.mbn
firmware/sbl1.mbn
firmware/sbl1_82.mbn
firmware/sbl1_92.mbn
firmware/sbl1_96.mbn
firmware/sbl2.mbn
eglsubAndroid.so
libEGL_adreno.so
libGLESv1_CM_adreno.so
libGLESv2S3D_adreno.so
libGLESv2_adreno.so
libq3dtools_adreno.so
power.msm8960.so
lib/libC2D2.so
lib/libQSEEComAPI.so
lib/libRSDriver_adreno.so
lib/libWVStreamControlAPI_L1.so
lib/libadreno_utils.so
lib/libbt-vendor.so
lib/libc2d30-a3xx.so
lib/libc2d30.so
lib/libgsl.so
lib/libllvm-a3xx.so
lib/libqc-opt.so
lib/librs_adreno.so
lib/librs_adreno_sha1.so
lib/libsc-a3xx.so
lib/libwvm.so
detection
recognition
[email protected]:/system/vendor $
Hello xda
Seems like I cannot erase all partitions properly. My phone have random reboots problem, and once it boots then it gets stuck at bootloader, so on every reboot I have to re-install OS. It does not matter whichever rom I try it still have same problem.
So what I tried is to erase all partitions in fastboot by command fastboot erase cache, system, etc etc and all other with success.
Then I use FlashOne1.9 to restore my phone completely to zero using QFIL with success installation but phone still kept rebooting, I tried to goto Recovery and here I still see TeamSpain TWRP 3.0.2 installed.
What can be wrong?
I erased all partitions manually + QFIL restore I thought completely erases everything but as I see still no.
Is there a way where I can delete all partitions and then recreate them one by one so there is not even a bit of any preinstalled softwares left.
I read deleting partitions in fastboot but felt it can be risky so I thought to ask a second opinion before proceeding.
Thank you
craftsvision said:
Hello xda
Seems like I cannot erase all partitions properly. My phone have random reboots problem, and once it boots then it gets stuck at bootloader, so on every reboot I have to re-install OS. It does not matter whichever rom I try it still have same problem.
So what I tried is to erase all partitions in fastboot by command fastboot erase cache, system, etc etc and all other with success.
Then I use FlashOne1.9 to restore my phone completely to zero using QFIL with success installation but phone still kept rebooting, I tried to goto Recovery and here I still see TeamSpain TWRP 3.0.2 installed.
What can be wrong?
I erased all partitions manually + QFIL restore I thought completely erases everything but as I see still no.
Is there a way where I can delete all partitions and then recreate them one by one so there is not even a bit of any preinstalled softwares left.
I read deleting partitions in fastboot but felt it can be risky so I thought to ask a second opinion before proceeding.
Thank you
Click to expand...
Click to collapse
here´s the patition table, if it is of any use for you...
lrwxrwxrwx 1 root root 16 Jan 1 00:12 aboot -> /dev/block/sde16
lrwxrwxrwx 1 root root 16 Jan 1 00:12 abootbak -> /dev/block/sde17
lrwxrwxrwx 1 root root 16 Jan 1 00:12 apdp -> /dev/block/sde29
lrwxrwxrwx 1 root root 16 Jan 1 00:12 bluetooth -> /dev/block/sde22
lrwxrwxrwx 1 root root 16 Jan 1 00:12 boot -> /dev/block/sde18
lrwxrwxrwx 1 root root 15 Jan 1 00:12 bootconfig -> /dev/block/sdf7
lrwxrwxrwx 1 root root 15 Jan 1 00:12 cache -> /dev/block/sda3
lrwxrwxrwx 1 root root 15 Jan 1 00:12 cdt -> /dev/block/sdd2
lrwxrwxrwx 1 root root 16 Jan 1 00:12 cmnlib -> /dev/block/sde25
lrwxrwxrwx 1 root root 16 Jan 1 00:12 cmnlib64 -> /dev/block/sde27
lrwxrwxrwx 1 root root 16 Jan 1 00:12 cmnlib64bak -> /dev/block/sde28
lrwxrwxrwx 1 root root 16 Jan 1 00:12 cmnlibbak -> /dev/block/sde26
lrwxrwxrwx 1 root root 15 Jan 1 00:12 ddr -> /dev/block/sdd3
lrwxrwxrwx 1 root root 15 Jan 1 00:12 devcfg -> /dev/block/sda6
lrwxrwxrwx 1 root root 15 Jan 1 00:12 devcfgbak -> /dev/block/sda7
lrwxrwxrwx 1 root root 16 Jan 1 00:12 devinfo -> /dev/block/sde21
lrwxrwxrwx 1 root root 16 Jan 1 00:12 dip -> /dev/block/sde14
lrwxrwxrwx 1 root root 16 Jan 1 00:12 dpo -> /dev/block/sde31
lrwxrwxrwx 1 root root 16 Jan 1 00:12 dsp -> /dev/block/sde13
lrwxrwxrwx 1 root root 15 Jan 1 00:12 factory -> /dev/block/sdf6
lrwxrwxrwx 1 root root 15 Jan 1 00:12 frp -> /dev/block/sda8
lrwxrwxrwx 1 root root 15 Jan 1 00:12 fsc -> /dev/block/sdf5
lrwxrwxrwx 1 root root 15 Jan 1 00:12 fsg -> /dev/block/sde7
lrwxrwxrwx 1 root root 15 Jan 1 00:12 fsg_gap -> /dev/block/sde8
lrwxrwxrwx 1 root root 15 Jan 1 00:12 hyp -> /dev/block/sde5
lrwxrwxrwx 1 root root 15 Jan 1 00:12 hypbak -> /dev/block/sde6
lrwxrwxrwx 1 root root 16 Jan 1 00:12 kernellog -> /dev/block/sdf14
lrwxrwxrwx 1 root root 16 Jan 1 00:12 keymaster -> /dev/block/sde23
lrwxrwxrwx 1 root root 16 Jan 1 00:12 keymasterbak -> /dev/block/sde24
lrwxrwxrwx 1 root root 15 Jan 1 00:12 keystore -> /dev/block/sda5
lrwxrwxrwx 1 root root 16 Jan 1 00:12 letvconfig -> /dev/block/sdf10
lrwxrwxrwx 1 root root 16 Jan 1 00:12 letveui -> /dev/block/sdf11
lrwxrwxrwx 1 root root 16 Jan 1 00:12 letvreserve -> /dev/block/sdf13
lrwxrwxrwx 1 root root 16 Jan 1 00:12 letvsecure -> /dev/block/sdf12
lrwxrwxrwx 1 root root 16 Jan 1 00:12 mdtp -> /dev/block/sde15
lrwxrwxrwx 1 root root 15 Jan 1 00:12 misc -> /dev/block/sda4
lrwxrwxrwx 1 root root 16 Jan 1 00:12 modem -> /dev/block/sde12
lrwxrwxrwx 1 root root 15 Jan 1 00:12 modemst1 -> /dev/block/sdf1
lrwxrwxrwx 1 root root 15 Jan 1 00:12 modemst1_gap -> /dev/block/sdf2
lrwxrwxrwx 1 root root 15 Jan 1 00:12 modemst2 -> /dev/block/sdf3
lrwxrwxrwx 1 root root 15 Jan 1 00:12 modemst2_gap -> /dev/block/sdf4
lrwxrwxrwx 1 root root 16 Jan 1 00:12 msadp -> /dev/block/sde30
lrwxrwxrwx 1 root root 15 Jan 1 00:12 persist -> /dev/block/sda2
lrwxrwxrwx 1 root root 16 Jan 1 00:12 pmic -> /dev/block/sde10
lrwxrwxrwx 1 root root 16 Jan 1 00:12 pmicbak -> /dev/block/sde11
lrwxrwxrwx 1 root root 16 Jan 1 00:12 recovery -> /dev/block/sde20
lrwxrwxrwx 1 root root 15 Jan 1 00:12 recoveryconfig -> /dev/block/sdf9
lrwxrwxrwx 1 root root 15 Jan 1 00:12 reserve -> /dev/block/sdd1
lrwxrwxrwx 1 root root 15 Jan 1 00:12 rootconfig -> /dev/block/sdf8
lrwxrwxrwx 1 root root 15 Jan 1 00:12 rpm -> /dev/block/sde1
lrwxrwxrwx 1 root root 15 Jan 1 00:12 rpmbak -> /dev/block/sde2
lrwxrwxrwx 1 root root 15 Jan 1 00:12 sec -> /dev/block/sde9
lrwxrwxrwx 1 root root 16 Jan 1 00:12 splash -> /dev/block/sde32
lrwxrwxrwx 1 root root 15 Jan 1 00:12 ssd -> /dev/block/sda1
lrwxrwxrwx 1 root root 16 Jan 1 00:12 sti -> /dev/block/sde33
lrwxrwxrwx 1 root root 16 Jan 1 00:12 system -> /dev/block/sde19cmd
lrwxrwxrwx 1 root root 15 Jan 1 00:12 xblbak -> /dev/block/sdc1
never blank partitions if you don´t have a backup anywhere, meaning: not part of qfil, stockrom customrom (zip or fastboot), not pulled from the/a phone(x820/29)
i would pull any single partitiom first (that are not part of roms etc.) and save it, you shoud be safe to restore the phone to the condidtion as it is now at least.
if you think one of theese could cause the problem, be sure to get the partition images from a working phone before you erase those!
also, backup your efs/qcn!
from what you tell it sounds like a harrdware fault but try! i would also try everything, had success the last time.
it bet it´s a x829, isn´t it?
i have some spare time the rest of the week and already helpded some xda users remotely. if you want i could (try) to help you too.
i´m an it guy, so this is my nature.
good luck
Yes you are correct i have x829, I bought it online from gearbest.com.
I dont know how this partition table can be useful and I dont even know how to use it.
I have backup of CN26s bootloader and Firmware made via TWRP. Stragnely CN26s boots everytime but have alot of random reboots.
If I install Hexagon Rom from here then it works fine for a day or two https://forum.xda-developers.com/le-max-2/development/rom-hexagonrom-nougat-t3594858
but as soon as its rebooted then I have to restore CN26s bootloader via TWRP then install Hexagon***.zip again and it will start again.
One more thing is that if I only restore bootloader of cn26s while already installed Hexagon then it is not stuck at bootloader screen anymore where it says LeeCo I am not jut a mobilephone blah blah but it also proceeds to Hexagon OS loading Animation but then its stuck there forever...!
If you can help then please tell me, I am willing too to try new things.
craftsvision said:
Yes you are correct i have x829, I bought it online from gearbest.com.
I dont know how this partition table can be useful and I dont even know how to use it.
I have backup of CN26s bootloader and Firmware made via TWRP. Stragnely CN26s boots everytime but have alot of random reboots.
If I install Hexagon Rom from here then it works fine for a day or two https://forum.xda-developers.com/le-max-2/development/rom-hexagonrom-nougat-t3594858
but as soon as its rebooted then I have to restore CN26s bootloader via TWRP then install Hexagon***.zip again and it will start again.
One more thing is that if I only restore bootloader of cn26s while already installed Hexagon then it is not stuck at bootloader screen anymore where it says LeeCo I am not jut a mobilephone blah blah but it also proceeds to Hexagon OS loading Animation but then its stuck there forever...!
If you can help then please tell me, I am willing too to try new things.
Click to expand...
Click to collapse
if you want, install teamviewer and send me your id and password in pm.
connect the phone to pc directly (no hub) and put into edl mode. i know you already did that procedure but i´d like to start from scratch - just to be sure.
we can save the qcn also with qpst so you don´t have to worry about loosing your imei.
open the folder where alll your files are.
i´ll have to check some things on your pc and download some files.
i´m cooking my meal now, then i´m ready. just keep pc and teamviewer on and i´ll login asap.
A.N.Droid said:
if you want, install teamviewer and send me your id and password in pm.
connect the phone to pc directly (no hub) and put into edl mode. i know you already did that procedure but i´d like to start from scratch - just to be sure.
we can save the qcn also with qpst so you don´t have to worry about loosing your imei.
open the folder where alll your files are.
i´ll have to check some things on your pc and download some files.
i´m cooking my meal now, then i´m ready. just keep pc and teamviewer on and i´ll login asap.
Click to expand...
Click to collapse
It would be really helpful of you make a video about the complete fix. I have a x821 in which I forgot to remove encryption before flashing a custom ROM and now in twrp there is a system image partition which is 4GB in size and is non accessible. I want to delete that but being inaccessible I an unable to do so.
Can you guide me on how to do that? Can you at least give me the step by step procedure to fix this issue?
Thanks in advance.
I have also problem of random reboots and fcs no mater what rom I flash.
Any one guide me what to do?
I have clean flashed though twrp.
Didn't use fastboot method? Any one can guide me on this ?
azzammalik said:
I have also problem of random reboots and fcs no mater what rom I flash.
Any one guide me what to do?
I have clean flashed though twrp.
Didn't use fastboot method? Any one can guide me on this ?
Click to expand...
Click to collapse
Heyyo, first off... Can you please state which version of TWRP you are running and if it is official or not?
Second, have you tried using wipe > format data > yes? I'd recommend doing that... But be warned it completely reformists the internal storage so you'll want to backup everything important off the device first and also have a PC with USB ready to flash ROM and Gapps.
Third, I would recommend flashing new device firmware to ensure it is proper for any ROM you install. I recommend for stability purposes to use x820 CN 30s which can be found on my LineageOS 15.1 for x2 thread.
Fourth, flash the ROM of choice and Gapps (and optionally root program of choice if you want Su rights).
For Oreo ROMs? I highly recommend MindTheGapps arm64 as OpenGapps is still of beta quality for Oreo ROMs and says so when you select it on the OpenGapps website as shown in the picture below. MindTheGapps link can also be found on my LineageOS for x2 thread.
As for which Oreo ROM I'd recommend? Every one has a little bit of difference from the last so I say try them out and see which suits your needs the best. They're all pretty darn good... Except for Resurrection Remix official. The maintainer of that put out one build and then bought a new smartphone and abandoned it lol so yeah avoid the official RR release...
Good luck! :good:
Thanks a lot brother
ThE_MarD said:
Heyyo, first off... Can you please state which version of TWRP you are running and if it is official or not?
Second, have you tried using wipe > format data > yes? I'd recommend doing that... But be warned it completely reformists the internal storage so you'll want to backup everything important off the device first and also have a PC with USB ready to flash ROM and Gapps.
Third, I would recommend flashing new device firmware to ensure it is proper for any ROM you install. I recommend for stability purposes to use x820 CN 30s which can be found on my LineageOS 15.1 for x2 thread.
Fourth, flash the ROM of choice and Gapps (and optionally root program of choice if you want Su rights).
For Oreo ROMs? I highly recommend MindTheGapps arm64 as OpenGapps is still of beta quality for Oreo ROMs and says so when you select it on the OpenGapps website as shown in the picture below. MindTheGapps link can also be found on my LineageOS for x2 thread.
As for which Oreo ROM I'd recommend? Every one has a little bit of difference from the last so I say try them out and see which suits your needs the best. They're all pretty darn good... Except for Resurrection Remix official. The maintainer of that put out one build and then bought a new smartphone and abandoned it lol so yeah avoid the official RR release...
Good luck! :good:
Click to expand...
Click to collapse
Million times thanks to you bro for answering with lot of details.
1. It's official latest twrp
2. Yes formatted a lot of times.
3. Yeah this is the method I didn't try yet. I will goto your thread and will download official firmware and will let you know after flashing official and afterwards any oreo rom.
4. Never tried any gapps other then opengapps maybe this will solve my problem. I will definitely try this method now.
I have almost flashed all oreo roms and every oreo rom is almost perfect for me except for this annoying bug. I am now heading towards your rom and will report you back after few hours because my mobile data is not that super fast and will download all required files and will flash it later in evening.
Thank you once again.
:fingers-crossed:
azzammalik said:
Million times thanks to you bro for answering with lot of details.
1. It's official latest twrp
2. Yes formatted a lot of times.
3. Yeah this is the method I didn't try yet. I will goto your thread and will download official firmware and will let you know after flashing official and afterwards any oreo rom.
4. Never tried any gapps other then opengapps maybe this will solve my problem. I will definitely try this method now.
I have almost flashed all oreo roms and every oreo rom is almost perfect for me except for this annoying bug. I am now heading towards your rom and will report you back after few hours because my mobile data is not that super fast and will download all required files and will flash it later in evening.
Thank you once again.
:fingers-crossed:
Click to expand...
Click to collapse
Heyyo, by chance is your TWRP version 3.2.1-2? That's the latest one I made and is required for the latest versions of LineageOS 15.1 for x2 as it has quota storage support for a minor boost to storage performance.
https://twrp.me/leeco/leecolemax2.html
Hope she works good for you!
ThE_MarD said:
Heyyo, by chance is your TWRP version 3.2.1-2? That's the latest one I made and is required for the latest versions of LineageOS 15.1 for x2 as it has quota storage support for a minor boost to storage performance.
https://twrp.me/leeco/leecolemax2.html
Hope she works good for you!
Click to expand...
Click to collapse
Hey,
I am here after 12 hours of usage.
Yes, I am using twrp 3.2.1-2.First flashed 30s firmware then flashed rom and gapps which you recommended and then magisk.
And to my amazement I had only 3 fcs right now which are too less then which I have faced before.
Also didn't reboot once in 12 hours but suddenly got 2 reboots in quick succession.
But still it's a lot more usable now as a daily driver for me just because of ya. Maybe problem will come back in a day or two as that happened before too.
But until then it's all OK for now.
A big thanks to you. .
Have a good day ahead
Cheers
Update: not even a single reboot or fc even after installing system less xposed. NO WORDS FOR YA. A BIG THANKYOU
2nd Update: 2nd day of usage. No more fcs. Single reboot. Perfect now.