Hi!
I just build CM13 from source for flo and it's not booting at all, it just hangs on the google logo forever (it's not the kernel, another kernel doesn't work either) the only reason I can think of is that the blobs I used don't work, I used the one from themuppets (https://github.com/TheMuppets/proprietary_vendor_asus/tree/cm-13.0/flo) and the only difference I see is that they come from a MMB29Q build and the build I am building is MOB30J
Can anyone help me with this because I'm clueless...
Thanks
noahvt said:
it just hangs on the google logo forever
Click to expand...
Click to collapse
It looks like another 'rm -rf /' and erased 'persist' partition
But seriously, let's check last_kmsg. Start the OS and when boot process stops, turn it off and then as quickly as possible turn it back on to TWRP recovery.
Next run adb shell cat /proc/last_kmsg > last_kmsg
If the log is empty, then you did not do it 'as quickly as possible' - in less than 2 seconds - and repeat it all over again. Post the log.
Incidentally, a better alternative to the reboot acrobatics is UART logging.
k23m said:
It looks like another 'rm -rf /' and erased 'persist' partition
But seriously, let's check last_kmsg. Start the OS and when boot process stops, turn it off and then as quickly as possible turn it back on to TWRP recovery.
Next run adb shell cat /proc/last_kmsg > last_kmsg
If the log is empty, then you did not do it 'as quickly as possible' - in less than 2 seconds - and repeat it all over again. Post the log.
Incidentally, a better alternative to the reboot acrobatics is UART logging.
Click to expand...
Click to collapse
Managed to pull it off with 1% battery but here it is: View attachment last.txt Using notepad++ I can see lots of grabage in there, not sure if it's normal lol
noahvt said:
Managed to pull it off with 1% battery but here it is: View attachment 3765650 Using notepad++ I can see lots of grabage in there, not sure if it's normal lol
Click to expand...
Click to collapse
It's not normal, RAM bit-decay is visible already - you need to be faster in the off/on trick. Also, keep it booting longer, 33 seconds of logging is not enough. Give it 2+ minutes to boot.
k23m said:
It's not normal, RAM bit-decay is visible already - you need to be faster in the off/on trick. Also, keep it booting longer, 33 seconds of logging is not enough. Give it 2+ minutes to boot.
Click to expand...
Click to collapse
OK, I gave it 3 minutes and was able to grab the log without garbage in it lol:
noahvt said:
OK, I gave it 3 minutes and was able to grab the log without garbage in it lol:
Click to expand...
Click to collapse
Excellent log!
Now, note the following FS conflicts (+more):
Code:
[ 3.564270] F2FS-fs (mmcblk0p23): Magic Mismatch, valid(0xf2f52010) - read(0x8c00)
[ 3.564392] F2FS-fs (mmcblk0p23): Can't find valid F2FS filesystem in 1th superblock
Do this: install the official CM 13 to restore the default FS and then try your own CM, OK?
k23m said:
Excellent log!
Now, note the following FS conflicts (+more):
Do this: install the official CM 13 to restore the default FS and then try your own CM, OK?
Click to expand...
Click to collapse
That didn't fix it unfortunately (tried: install official > Wipe > Install my cm And Install Official > Install my cm)
noahvt said:
That didn't fix it unfortunately (tried: install official > Wipe > Install my cm And Install Official > Install my cm)
Click to expand...
Click to collapse
Remember "fastboot getvar all" from ''rm -rf /' :laugh: - let me see it again...
k23m said:
Remember "fastboot getvar all" from ''rm -rf /' :laugh: - let me see it again...
Click to expand...
Click to collapse
Here you go:
noahvt said:
Here you go:
Click to expand...
Click to collapse
Very well, then let's look at the subsequent errors:
[ 66.347076] init: cannot find '/system/bin/irsc_util', disabling 'irsc_util'
[ 66.347229] init: cannot find '/system/bin/rmt_storage', disabling 'rmt_storage'
[ 66.347351] init: cannot find '/system/bin/bridgemgrd', disabling 'bridgemgrd'
[ 66.347534] init: cannot find '/system/bin/thermald', disabling 'thermald'
....
[ 66.357330] init: cannot find '/system/bin/sensors.qcom', disabling 'sensors'
[ 66.357513] init: cannot find '/system/bin/mpdecision', disabling 'mpdecision'
[ 66.357666] init: cannot find '/system/bin/mm-qcamera-daemon', disabling 'qcamerasvr'
Click to expand...
Click to collapse
Please describe all of the build's components, links and dependencies.
k23m said:
Very well, then let's look at the subsequent errors:
[ 66.347076] init: cannot find '/system/bin/irsc_util', disabling 'irsc_util'
[ 66.347229] init: cannot find '/system/bin/rmt_storage', disabling 'rmt_storage'
[ 66.347351] init: cannot find '/system/bin/bridgemgrd', disabling 'bridgemgrd'
[ 66.347534] init: cannot find '/system/bin/thermald', disabling 'thermald'
....
[ 66.357330] init: cannot find '/system/bin/sensors.qcom', disabling 'sensors'
[ 66.357513] init: cannot find '/system/bin/mpdecision', disabling 'mpdecision'
[ 66.357666] init: cannot find '/system/bin/mm-qcamera-daemon', disabling 'qcamerasvr'
Please describe all of the build's components, links and dependencies.
Click to expand...
Click to collapse
I think I found the problem, these 'missing' binaries are there in "device/Asus/flo/proprietary/bin" but not in "out/target/product/flo/system/bin" wth why isn't it copying them over....
Related
Archos 97 Root and custom recovery step by step n00b guide.
Download files
rkflashtool http://sourceforge.net/projects/rkflashtool
ARCHOS 97 Titanium HD custom recovery from http://androtab.info/clockworkmod/rockchip/rk3066/
Edit rkflashtool.c, add 0x300a line
if (!(h = libusb_open_device_with_vid_pid(c, 0x2207, 0x290a)))
if (!(h = libusb_open_device_with_vid_pid(c, 0x2207, 0x281a)))
if (!(h = libusb_open_device_with_vid_pid(c, 0x2207, 0x300a)))
fatal("cannot open device\n");
Click to expand...
Click to collapse
comile rkflashtool with libusb
sudo apt-get install libusb-1.0-0-dev
gcc -o rkflashtool rkflashtool.c -lusb-1.0 -O2 -W -Wall -s
connect tablet USB to PC
power off tablet
hold volume- and insert charging cable
release volume- after screen turns on
dump system
sudo ./rkflashtool r 0x00154000 0x00100000 > system.loop
edit system, disable install-recovery.sh
sudo mount -o loop system.loop /loop
cd /loop/etc
sudo chmod 644 install-recovery.sh
flash system back to device
sudo ./rkflashtool w 0x00154000 0x00100000 < system.loop
backup original recovery and flash CWM recovery.img
sudo ./rkflashtool r 0x00010000 0x00008000 > recovery.backup
sudo ./rkflashtool w 0x00010000 0x00008000 < recovery.img
reboot to recovery (hold volume-, connect power cable)
donwload and install SuperSU.zip
Maybe you can add to the tutorial, howto restore the original content, so that it looks like "untouched".
starbright_ said:
Maybe you can add to the tutorial, howto restore the original content, so that it looks like "untouched".
Click to expand...
Click to collapse
Flash "recovery.backup" back you made in step 8. and delete super user app, that's it.
Though nobody checks those things anyway.
Additional info on partition offsets
MACHINE_MODEL:ARCHOS 97 TITANIUMHD
MACHINE_ID:007
MANUFACTURER:RK30SDK
MAGIC: 0x5041524B
ATAG: 0x60000800
MACHINE: 3066
CHECK_MASK: 0x80
KERNEL_IMG: 0x60408000
#RECOVER_KEY: 1,1,0,20,0
CMDLINE: console=ttyFIQ0 androidboot.console=ttyFIQ0 init=/init initrd=0x62000000,0x00800000
mtdparts=rk29xxnand:
[email protected](misc),
[email protected](kernel),
[email protected](boot),
[email protected](recovery),
[email protected](backup),
[email protected](cache),
[email protected](kpanic),
[email protected](system),
[email protected](userdata)
Click to expand...
Click to collapse
Does this work on the Familypad 2? If not, are there any known methods to achieve root on the Familypad 2?
Thanks.
Moved Files
The Repository has been removed; what do you from this point?
GIgantorFNS said:
The Repository has been removed; what do you from this point?
Click to expand...
Click to collapse
it wasn't http://sourceforge.net/p/rkflashtool/code/HEAD/tree/trunk/
GIgantorFNS said:
The Repository has been removed; what do you from this point?
Click to expand...
Click to collapse
Thank you! It's there; beit that this is my first time rooting a tablet-I have NO idea what I do after this point!
Hmm.... I can't mount system.loop !
Everything works fine. but if i try to mount system.loop i'll get no access.
If i type in:
sudo mount -o loop system.loop /loop
Ubuntu tells me /loop does not exist.
Where is the error?
Can someone help?
THX LaGra
all working file. thank you for your tuto
:laugh:
LaGra said:
sudo mount -o loop system.loop /loop
Ubuntu tells me /loop does not exist.
Click to expand...
Click to collapse
you need to create /loop folder first.
Originalas said:
you need to create /loop folder first.
Click to expand...
Click to collapse
Sorry, but still not working.
Where i have to create that folder?
Linux is not my best.
my english too......
I have put an update on the tablet from archos. Maybe is that my fail.
LaGra said:
Sorry, but still not working.
Where i have to create that folder?
Click to expand...
Click to collapse
Try
sudo mkdir -p /mnt/loop
sudo mount -o loop system.loop /mnt/loop
Originalas said:
Try
sudo mkdir -p /mnt/loop
sudo mount -o loop system.loop /mnt/loop
Click to expand...
Click to collapse
Thanks a lot for your help.
Now its working. :good:
Hi, I can't get through number 5, ie dump system with "sudo ./rkflashtool r 0x00154000 0x00100000 > system.loop".
Every time I get "rkflashtool: fatal: cannot open device". Tablet is in recover mode and connected through USB.
The only difference - I'm using Linux Mint 14. Is that the problem?
type in terminal
lsusb
does your device show up in the list? Is it under name "0x2207, 0x300a"? or something like "Google Android"?
Check drivers, try differrent USB port, if tablet doesn't show up in the list at all.
If it's under other name, not "0x2207, 0x300a", then you haven't entered flashing mode properly.
Turn off tablet, connect usb, hold volume down button and connect power supply without releasing volume down for 10s. Then try lsusb again.
Originalas said:
type in terminal
lsusb
does your device show up in the list? Is it under name "0x2207, 0x300a"? or something like "Google Android"?
Check drivers, try differrent USB port, if tablet doesn't show up in the list at all.
If it's under other name, not "0x2207, 0x300a", then you haven't entered flashing mode properly.
Turn off tablet, connect usb, hold volume down button and connect power supply without releasing volume down for 10s. Then try lsusb again.
Click to expand...
Click to collapse
Thanks a lot for your reply.
In normal mode it shows as "Bus 003 Device 008: ID 0e79:14ad Archos, Inc.", but it doesn't show at all in recovery mode.
What might be the problem?
Ok, now i can go into CWM.
Superuser is installed. But if I start the tablet it does not boot
anymore!
Everytime it goes back to recovery menu.
nyboy1 said:
Thanks a lot for your reply.
In normal mode it shows as "Bus 003 Device 008: ID 0e79:14ad Archos, Inc.", but it doesn't show at all in recovery mode.
What might be the problem?
Click to expand...
Click to collapse
you haven't set tablet to flash mode.
Originalas said:
Turn off tablet, connect usb, hold volume down button and connect power supply without releasing volume down for 10s. Then try lsusb again.
Click to expand...
Click to collapse
Originalas said:
you haven't set tablet to flash mode.
Click to expand...
Click to collapse
Hi, thanks for your reply. I managed to get to number 6 now)
[email protected]:~$ sudo mkdir -p /mnt/loop
[email protected]:~$ sudo mount -o loop system.loop /mnt/loop
mount: according to mtab /home/ubuntu/system.loop is already mounted on /mnt/loop as loop
[email protected]:~$ cd /loop/etc
bash: cd: /loop/etc: No such file or directory
Can't understand where mistake was made. I'd appreciate your help. Thank you.
Well, if you created mount in /mnt/loop, path should be like
cd /mnt/loop/etc
You can use graphical file explorer, to check directories too..
Located in /dev/block, may be useful
Code:
mmcblk0p1 -> /xloader
mmcblk0p2 -> /round (-empty-)
mmcblk0p3 -> /nvme
mmcblk0p4 -> /misc
mmcblk0p5 -> /splash (-empty-)
mmcblk0p6 -> /oeminfo
mmcblk0p7 -> /reserved1 (-empty-)
mmcblk0p8 -> /reserved2 (-empty-)
mmcblk0p9 -> /splash2
mmcblk0p10 -> /recovery2 (-empty-)
mmcblk0p11 -> /recovery
mmcblk0p12 -> /boot
mmcblk0p13 -> /modemimage
mmcblk0p14 -> /modemnvm
mmcblk0p15 -> /modemnvm2
mmcblk0p16 -> /system
mmcblk0p17 -> /cache
mmcblk0p18 -> /cust
mmcblk0p19 -> /userdata
I took this info opening the direct accesses in /dev/block/platform/hi_mci.1/by-name
To extract the boot or recovery img with dd:
Code:
adb shell
su
dd if=/dev/block/mmcblk0p11 of=/sdcard/recovery.img
dd if=/dev/block/mmcblk0p12 of=/sdcard/boot.img
TheProd said:
To extract the boot or recovery img with dd:
Code:
adb shell
su
dd if=/dev/block/mmcblk0p11 of=/sdcard/recovery.img
dd if=/dev/block/mmcblk0p12 of=/sdcard/boot.img
Click to expand...
Click to collapse
I already extracted recovery.img But i can't unpack it, i use unyaffs.exe but i get "broken image file" D:
Same with the other *.img files
Code:
BOARD_KERNEL_CMDLINE vmalloc=512M k3v2_pmem=1 mmcparts=mmcblk0:p1(xloader),p3(n
me),p4(misc),p5(splash),p6(oeminfo),p7(reserved1),p8(reserved2),p9(splash2),p10
recovery2),p11(recovery),p12(boot),p13(modemimage),p14(modemnvm1),p15(modemnvm2
,p16(system),p17(cache),p18(cust),p19(userdata);mmcblk1:p1(ext_sdcard)
BOARD_KERNEL_BASE 00000000
BOARD_PAGE_SIZE 2048
BOARD_RAMDISK_ADDR 01400000
Unpacking ramdisk to "/ramdisk/" . . .
Compression used: gzip
2085 blocks
Done!
Boot.img unpacked, K3V2 uses ARMv7 Instruction Set. Let's see if we can't get something cooking already
I unpacked recovery and boot too
Sent from my HUAWEI P6-U06 using xda app-developers app
Good show, unless your planning on beginning work on a Custom Recovery what are you going to gain by unpacking the recovery.img?
I see your working on a CM port, so wish you all the best on that. I'll be porting MIUIv5 for the Ascend P6 as I did for a few other devices, also going to have another crack at porting Flyme OS since I already ported 90% to my previous device.
Best Regards,
s89
I unpacked boot and recovery to get info for BoardConfig.mk
Ty
Sent from my HUAWEI P6-U06 using xda app-developers app
If you've already got a build environment setup you may aswel build CWM from CM sources, we have more then enough information here to proceed. Even more convenient considering you have the recovery.img unpacked. Google "Build CWM Cyanogenmod" for more info. Failing that i'll setup a build environment and do so myself tomorrow evening.
Best Regards,
s89
I'm setting up the enviroment to build CWM, i hope to get it done in a few hours, anyways, i got bad news. My laptop screen broke today, and i send it to repair tomorrow and i don't know how much time will take :/
S34Qu4K3 said:
I'm setting up the enviroment to build CWM, i hope to get it done in a few hours, anyways, i got bad news. My laptop screen broke today, and i send it to repair tomorrow and i don't know how much time will take :/
Click to expand...
Click to collapse
Aww man that's unfortunate, wishing a speedy recovery for said laptop aha. Are you continuing the build on another machine or using an external monitor for the meantime?
Best Regards,
s89
Stickman89 said:
Aww man that's unfortunate, wishing a speedy recovery for said laptop aha. Are you continuing the build on another machine or using an external monitor for the meantime?
Best Regards,
s89
Click to expand...
Click to collapse
I got an small laptop and a pc, i have to install linux and will continue working (i think) i expect to be at least 1 week without my laptop (maybe i got it with screen broken ultil i wait the new screen)
Dam git sync, so ****ing long
Just a question, if i have in my .fstabfile the partition routes this way:
Code:
/dev/block/platform/hi_mci.1/by-name/sdcard
I have to change it to
Code:
/dev/block/mcblk....
In BoardConfig.mk or can i let it original? Looks the same for me, /dev/block/platform/hi_mci.1/by-name/ points the mcblk, i want to be sure
S34Qu4K3 said:
Just a question, if i have in my .fstabfile the partition routes this way:
Code:
/dev/block/platform/hi_mci.1/by-name/sdcard
I have to change it to
Code:
/dev/block/mcblk....
In BoardConfig.mk or can i let it original? Looks the same for me, /dev/block/platform/hi_mci.1/by-name/ points the mcblk, i want to be sure
Click to expand...
Click to collapse
EXT SDCard Mounts at:
Code:
/dev/block/mmcblk1p1
so your recovery.fstab should be setup like...
Code:
/sdcard vfat /dev/block/mmcblk1p1
So yup it needs to be changed to the second option.
I'm still syncing too... -.- ...zZzZzZzZz tired
Best Regards,
s89
Stickman89 said:
EXT SDCard Mounts at:
Code:
/dev/block/mmcblk1p1
so your recovery.fstab should be setup like...
Code:
/sdcard vfat /dev/block/mmcblk1p1
So yup it needs to be changed to the second option.
I'm still syncing too... -.- ...zZzZzZzZz tired
Best Regards,
s89
Click to expand...
Click to collapse
But /dev/block/platform/hi_mci.1/by-name/sdcard points to /dev/block/mmcblk1p1, so it shouldn't be necessary (i'll use /dev/block/mmcblk1p1 style, to be sure anyway)
In 4 hours, i leave my lapton in the shop, in another hour, i got it repaired (115€ D
I've built CWM from CM sources. Haven't tried it as of yet though.
Flash at your OWN risk. I will not take responsibility for any actions taken by the user in combination with the provided file... By downloading this image your accepting full liability for any issues that should arise as a result of undergoing ANY flashing/modding on YOUR device.
Removed for the time being! Do not use...
Best Regards,
s89
Stickman89 said:
I've built CWM from CM sources. Haven't tried it as of yet though.
Flash at your OWN risk. I will not take responsibility for any actions taken by the user in combination with the provided file... By downloading this image your accepting full liability for any issues that should arise as a result of undergoing ANY flashing/modding of your device.
Best Regards,
s89
Click to expand...
Click to collapse
My repo still 93% ;___;
Why you don't make a thread posting it??
Good job bro
We can try recoverys without flash using fastboot? Like the kernel?
S34Qu4K3 said:
My repo still 93% ;___;
Why you don't make a thread posting it??
Good job bro
We can try recoverys without flash using fastboot? Like the kernel?
Click to expand...
Click to collapse
I've tried "fastboot boot recovery.img" to no avail. The output is as follows...
Output:
Code:
downloading 'boot.img'...
OKAY [ 0.193s]
booting...
FAILED (remote: invalid command)
finished. total time: 0.194s
As you can see... It's expecting a boot.img so this command is only available for booting ramdisk & kernel.
Stickman89 said:
I've tried "fastboot boot recovery.img" to no avail. The output is as follows...
Output:
Code:
downloading 'boot.img'...
OKAY [ 0.193s]
booting...
FAILED (remote: invalid command)
finished. total time: 0.194s
As you can see... It's expecting a boot.img so this command is only available for booting ramdisk & kernel.
Click to expand...
Click to collapse
So, we have to flash it... Bad bad...D:
I tried fastboot boot recovery recovery.img but i get:
Code:
fastboot boot recovery recovery.img
cannot load 'recovery'
I don't think that command is applicable until post flash as according to cyanogenmod documentation:
Code:
Installing recovery using fastboot
You can use fastboot to install your recovery image to the device.
Installing ClockworkMod Recovery on the device
Connect the device to the computer via USB.
Make sure the fastboot binary is in your PATH or that you place the downloaded image in the same directory as fastboot.
Open a terminal on your PC and reboot the device into fastboot mode by typing adb reboot bootloader or by using the hardware key combination.
Once the device is in fastboot mode, verify your PC sees the device by typing fastboot devices
If you don't see your device serial number, and instead see "<waiting for device>", fastboot is not configured properly on your machine. See fastboot documentation for more info.
Flash ClockworkMod Recovery onto your device by entering the following command: fastboot flash recovery your_recovery_image.img where the latter part is the name of the file you downloaded.
Once the flash completes successfully, reboot the device into recovery to verify the installation. This can be done by typing fastboot boot your_recovery_image.img.
Note: Some ROMs overwrite recovery at boot time so if you do not plan to immediately boot into recovery to install CyanogenMod, please be aware that this may overwrite your custom recovery with the stock one.
Please help! After successful downgrade from 4.4.2 to 4.1.2, my tab 3 refuses to charge while turned off. Stuck at the stage of starting to charge where you have the battery symbol and a circle inside it. Even when cable is removed it won't go unless restarted by long pressing the power button. <br />
<br />
It charges well when powered on but not otherwise! Every other thing is working normal.<br />
<br />
Could it be that the downgrade has tampered with the charging software. <br />
<br />
What can I do please?<br/>
moyaya02 said:
Hi All,
Can anybody confirm I can use CM guides below to get my data connection back?
wiki*cyanogenmod*/index.php/Upgrade_Rogers_Dream_Radio
and
wiki*cyanogenmod*/index.php/Full_Update_Guide_Rogers_Dream_EBI1_to_CyanogenMod
reading these guides and others, they all seem oriented towards Rogers phones??? I am afraid there will be incompatabilities because my phone is a T-mobile Dream G1, bought on ebay Nov, 2008, and running on Rogers network since then. I lost Data connectivity to Rogers network and can not activate GPS.
My other settings are:
CM 2.4.14.1... and 120 applications ..... and
DREA100 PVT 32B
Hboot 0.95.0000
CPLD-4
Radio-2.22.19.26I
Sept 2 2008
Serial 0
PS I think these two links are very legit..so I modified them as shown to allow for posting ( I am a new user).... if the mods do not like that, please remove.
Click to expand...
Click to collapse
You are using the kitkat bootloader with a jellybean kernel. That's why charging isn't working as usual. A customized kernel "may" be a possible fix, but there isn't one for that.
gr8nole said:
You are using the kitkat bootloader with a jellybean kernel. That's why charging isn't working as usual. A customized kernel "may" be a possible fix, but there isn't one for that.
Click to expand...
Click to collapse
I just online edited T21x kernel source: https://github.com/kumajaya/android...mmit/d5a4627819a66fc38c7e53fba3c3f3b220127571 and https://github.com/kumajaya/android...mmit/c6fb6f677aa195b07348eb7777322ca956f9c44c
ketut.kumajaya said:
I just online edited T21x kernel source: https://github.com/kumajaya/android...mmit/d5a4627819a66fc38c7e53fba3c3f3b220127571 and https://github.com/kumajaya/android...mmit/c6fb6f677aa195b07348eb7777322ca956f9c44c
Click to expand...
Click to collapse
Excellent!! Compiling now to test. Thanks.
Edit:
@ketut.kumajaya It didn't do anything differently than before. It does recognize "charging" mode and charging begins.
Normally, when charging while powered off, then black battery icon will appear for a few seconds, then the green partially filled battery icon will appear while charging and the screen will soon go blank.
With the new KK firmware, the black battery icon never goes away (probably is charging though) and the screen never turns off. Even if you unplug it, the black battery icon stays and the screen stays on which requires a manual reboot.
@gr8nole With 4.1.2 ROM?
ketut.kumajaya said:
@gr8nole With 4.1.2 ROM?
Click to expand...
Click to collapse
Yes. I tried using the init binary from kk kernel and it worked better for charging offline, but screen was black on normal bootup.
gr8nole said:
Yes. I tried using the init binary from kk kernel and it worked better for charging offline, but screen was black on normal bootup.
Click to expand...
Click to collapse
Maybe the init binary try to find lpcharge string in kernel command line. I'll try to find a way to manipulate kernel command line on boot.
@gr8nole I have upgraded my bootloader to KitKat and start experience your issue :laugh: I managed to fix it, boot stock KitKat in low power mode by changing init.42 to init.44 https://github.com/kumajaya/android...npack-boot.img/boot.img-ramdisk/sbin/init#L15 . I'll find the source of problem soon or later I believe my "Read LPM state from KitKat bootloader" still needed.
@gr8nole Please check http://review.cyanogenmod.org/#/c/74120 I'm not sure it's applicable for stock ROM.
Great. You guys are working on it. Sorry I'm a bit new to android and don't know much of those stuffs. Gotta wait till solution comes. Thanks to you all for putting effort into finding the solution
Does it mean the downgrade didn't downgrade the boot loader also? Is it possible to get the JB boot loader and flash it alone?
@gr8nole
Make sure you merge my last 2 commits https://github.com/kumajaya/android_kernel_samsung_lt02/commits/master and then change lpm.rc to:
Code:
on early-init
start ueventd
write /sys/class/power_supply/battery/batt_lp_charging 1
on init
export PATH /sbin:/vendor/bin:/system/sbin:/system/bin:/system/xbin
export LD_LIBRARY_PATH /vendor/lib:/system/lib
export ANDROID_ROOT /system
export ANDROID_DATA /data
export EXTERNAL_STORAGE /sdcard
symlink /system/etc /etc
mkdir /sdcard
mkdir /preload
mkdir /system
mkdir /data
mkdir /cache
mkdir /efs
mkdir /tmp
mkdir /dbdata
mkdir /mnt 0775 root root
mount ext4 /dev/block/mmcblk0p14 /system ro wait noatime
mkdir /data/log 0777
chmod 0666 /dev/log/radio
chmod 0666 /dev/log/main
chmod 0666 /dev/log/event
class_start default
service debuggerd /system/bin/debuggerd
service ueventd /sbin/ueventd
critical
#service console /bin/sh
service console /system/bin/sh
console
service playlpm /system/bin/playlpm
user root
service immvibed /system/bin/immvibed
oneshot
service lpmkey /system/bin/lpmkey
user root
# adbd is controlled by the persist.service.adb.enable system property
service adbd /sbin/adbd
disabled
# adbd on at boot in emulator
on property:ro.kernel.qemu=1
start adbd
on property:persist.service.adb.enable=1
start adbd
on property:persist.service.adb.enable=0
stop adbd
I confirm above solution works on Tab 3 8.0 stock 4.2.2 and CM 11 ROM, KitKat bootloader.
Technical explanation, from http://review.cyanogenmod.org/#/c/74120/ :
"The new KitKat bootloader populate "androidboot.mode=charger" command line in LPM, init will ignore "early-fs" and "boot" action, and try to trigger "charger" action: https://github.com/CyanogenMod/android_system_core/blob/cm-11.0/init/init.c#L1212-L1242 Without this patch, lpm service will never be executed".
ketut.kumajaya said:
@gr8nole
Make sure you merge my last 2 commits https://github.com/kumajaya/android_kernel_samsung_lt02/commits/master and then change lpm.rc to:
Code:
on early-init
start ueventd
write /sys/class/power_supply/battery/batt_lp_charging 1
on init
export PATH /sbin:/vendor/bin:/system/sbin:/system/bin:/system/xbin
export LD_LIBRARY_PATH /vendor/lib:/system/lib
export ANDROID_ROOT /system
export ANDROID_DATA /data
export EXTERNAL_STORAGE /sdcard
symlink /system/etc /etc
mkdir /sdcard
mkdir /preload
mkdir /system
mkdir /data
mkdir /cache
mkdir /efs
mkdir /tmp
mkdir /dbdata
mkdir /mnt 0775 root root
mount ext4 /dev/block/mmcblk0p14 /system ro wait noatime
mkdir /data/log 0777
chmod 0666 /dev/log/radio
chmod 0666 /dev/log/main
chmod 0666 /dev/log/event
class_start default
service debuggerd /system/bin/debuggerd
service ueventd /sbin/ueventd
critical
#service console /bin/sh
service console /system/bin/sh
console
service playlpm /system/bin/playlpm
user root
service immvibed /system/bin/immvibed
oneshot
service lpmkey /system/bin/lpmkey
user root
# adbd is controlled by the persist.service.adb.enable system property
service adbd /sbin/adbd
disabled
# adbd on at boot in emulator
on property:ro.kernel.qemu=1
start adbd
on property:persist.service.adb.enable=1
start adbd
on property:persist.service.adb.enable=0
stop adbd
I confirm above solution works on Tab 3 8.0 stock 4.2.2 and CM 11 ROM, KitKat bootloader.
Technical explanation, from http://review.cyanogenmod.org/#/c/74120/ :
"The new KitKat bootloader populate "androidboot.mode=charger" command line in LPM, init will ignore "early-fs" and "boot" action, and try to trigger "charger" action: https://github.com/CyanogenMod/android_system_core/blob/cm-11.0/init/init.c#L1212-L1242 Without this patch, lpm service will never be executed".
Click to expand...
Click to collapse
It works!!! I tested it with my 4.1.2 SvelteNole rom and it seems to behave just like it did before new bootloader. Excellent!
I used your blackhawk 2.1 and only changed out the zImage and made the lpm.rc change.
boot.img is attached so you can post it in your thread so you get the proper credit.
Thanks @gr8nole We fixed it faster than expected
Wow! Good work! So it can work on mime now? How do I flash it? With TWRP custom recovery?
odifek said:
Wow! Good work! So it can work on mime now? How do I flash it? With TWRP custom recovery?
Click to expand...
Click to collapse
http://forum.xda-developers.com/galaxy-tab-3/development-7/kernel-4-1-2-kernel-kitkat-bootloader-t2897313
dont charge offline
Friends i flashed the kernel three times but to me it doesnt works... my tablet continues dont charge offline... Please, someone give me a help???
I have substratum working on 2 other modded moto devices but can't get it to work on this XT1952-4. I am running Descendant-4.0.1_a64_ab Pie. The substratum version is one thousand twenty two. My device is successfuly rooted using @Spaceminer modded phh root. I have Magisk on the other 2 devices. If anyone has any ideas on this I would appreciate it. Thanks
Motomizer said:
I have substratum working on 2 other modded moto devices but can't get it to work on this XT1952-4. I am running Descendant-4.0.1_a64_ab Pie. The substratum version is one thousand twenty two. My device is successfuly rooted using @Spaceminer modded phh root. I have Magisk on the other 2 devices. If anyone has any ideas on this I would appreciate it. Thanks
Click to expand...
Click to collapse
I think that I have a solution if you can run a command from termux or adb for me.
Code:
ls /system/bin | grep .sh
Give me the output of that. I'll probably need you to send me a file afterwards, but I need to get the name of it first. I'll recognize it when I see it. If you get a special character error, drop the dot off of sh.
Wow, I wasn't expecting the legend himself replying. I don't have termux so I will get on the computer and do adb
It says cannot access '/system/bin'
I installed termux and got the following result:
crash_dump32
lshal
phh-on-boot.sh
rw-system.sh
twrp.sh
Motomizer said:
I installed termux and got the following result:
crash_dump32
lshal
phh-on-boot.sh
rw-system.sh
twrp.sh
Click to expand...
Click to collapse
Rename phh-on-boot.sh to phh-on-boot.txt and send it to me. Use the paperclip to attach it. Use a root explorer to copy it to your sdcard first. Or from termux...
Code:
su
cp /system/bin/phh-on-boot.sh /sdcard/phh-on-boot.sh
You can also concatenate it and pipe the output to a text file like this...
Code:
su
cat /system/bin/phh-on-boot.sh > /sdcard/phh-on-boot.txt
Spaceminer said:
Rename phh-on-boot.sh to phh-on-boot.txt and send it to me. Use the paperclip to attach it. Use a root explorer to copy it to your sdcard first. Or from termux...
Code:
su
cp /system/bin/phh-on-boot.sh /sdcard/phh-on-boot.sh
You can also concatenate it and pipe the output to a text file like this...
Code:
su
cat /system/bin/phh-on-boot.sh > /sdcard/phh-on-boot.txt
Click to expand...
Click to collapse
Ok, I copied and renamed the file easily with a file manager. I can't find a paperclip symbol anywhere to attach it. Is there a post quota to allow attachments?
Motomizer said:
Ok, I copied and renamed the file easily with a file manager. I can't find a paperclip symbol anywhere to attach it. Is there a post quota to allow attachments?
Click to expand...
Click to collapse
I believe there is a quota. 10 if I'm not mistaken. Just use the code button "#" and paste the text of it in a reply.
Spaceminer said:
I believe there is a quota. 10 if I'm not mistaken. Just use the code button "#" and paste the text of it in a reply.
Click to expand...
Click to collapse
[#!/system/bin/sh
[ "$(getprop vold.decrypt)" = "trigger_restart_min_framework" ] && exit 0
if [ -f /vendor/bin/mtkmal ];then
if [ "$(getprop persist.mtk_ims_support)" = 1 ] || [ "$(getprop persist.mtk_epdg_support)" = 1 ];then
setprop persist.mtk_ims_support 0
setprop persist.mtk_epdg_support 0
reboot
fi
fi
#Clear looping services
sleep 30
getprop | \
grep restarting | \
sed -nE -e 's/\[([^]]*).*/\1/g' -e 's/init.svc.(.*)/\1/p' |
while read -r svc ;do
setprop ctl.stop "$svc"
done
if grep -qF android.hardware.boot /vendor/manifest.xml || grep -qF android.hardware.boot /vendor/etc/vintf/manifest.xml ;then
bootctl mark-boot-successful
fi
]
Motomizer said:
[#!/system/bin/sh
[ "$(getprop vold.decrypt)" = "trigger_restart_min_framework" ] && exit 0
if [ -f /vendor/bin/mtkmal ];then
if [ "$(getprop persist.mtk_ims_support)" = 1 ] || [ "$(getprop persist.mtk_epdg_support)" = 1 ];then
setprop persist.mtk_ims_support 0
setprop persist.mtk_epdg_support 0
reboot
fi
fi
#Clear looping services
sleep 30
getprop | \
grep restarting | \
sed -nE -e 's/\[([^]]*).*/\1/g' -e 's/init.svc.(.*)/\1/p' |
while read -r svc ;do
setprop ctl.stop "$svc"
done
if grep -qF android.hardware.boot /vendor/manifest.xml || grep -qF android.hardware.boot /vendor/etc/vintf/manifest.xml ;then
bootctl mark-boot-successful
fi
]
Click to expand...
Click to collapse
Try this and see if it works. Place the file on your internal storage, then open up termux and run the following commands.
Code:
mount -o remount,rw /
mv /sdcard/phh-on-boot.txt /sdcard/phh-on-boot.sh
cp -f /sdcard/phh-on-boot.sh /system/bin
chmod 0755 /system/bin/phh-on-boot.sh
reboot
After rebooting, see if substratum will work.
For future reference, the code brackets work like so on XDA...
Code:
The text goes here...[/CODE ← Close this with another bracket. "]"
[CODE]The text goes here...
The bracket was closed, so now it looks different.
This helps formatting when working with scripts.
Spaceminer said:
Try this and see if it works. Place the file on your internal storage, then open up termux and run the following commands.
Code:
mount -o remount,rw /
mv /sdcard/phh-on-boot.txt /sdcard/phh-on-boot.sh
cp -f /sdcard/phh-on-boot.sh /system/bin
chmod 0755 /system/bin/phh-on-boot.sh
reboot
After rebooting, see if substratum will work.
For future reference, the code brackets work like so on XDA...
Code:
The text goes here...[/CODE ← Close this with another bracket. "]"
[CODE]The text goes here...
The bracket was closed, so now it looks different.
This helps formatting when working with scripts.
Click to expand...
Click to collapse
I knew that file I sent you didn't look right, but didn't know how to fix it. Thanks for the code bracket lesson and your patience. Unfortunately the code you had me run in termux didn't get substratum working. So you know, when I first ran into problems on this g7 play I copied the substratum apk over to my z play to see if the package was corrupt but it works fine there. Same with the themes.
Motomizer said:
I knew that file I sent you didn't look right, but didn't know how to fix it. Thanks for the code bracket lesson and your patience. Unfortunately the code you had me run in termux didn't get substratum working. So you know, when I first ran into problems on this g7 play I copied the substratum apk over to my z play to see if the package was corrupt but it works fine there. Same with the themes.
Click to expand...
Click to collapse
Can you check the build number on substratum? Find it in your app list and check near the bottom of it's info. Should look something like the attached screenshot. I'll see what I can dig up about it.
Spaceminer said:
Can you check the build number on substratum? Find it in your app list and check near the bottom of it's info. Should look something like the attached screenshot. I'll see what I can dig up about it.
Click to expand...
Click to collapse
I was trying to send a screenshot of the app info but I guess I can't do that yet, either. Next to the i in a circle at the bottom it reads:
version one thousand twenty two
They spell it out instead of using numerical digits. I have seen it like that even on older versions.
There is more information at ApkMirror. It's even compatible with Android 10. I didn't know that.
@Spaceminer
Could it be that Descendant-4.0.1_a64_ab Pie doesn't have OMS support? I did a full xda search on that and got no results. When I have time I will install another gsi rom and see what happens.
Motomizer said:
@Spaceminer
Could it be that Descendant-4.0.1_a64_ab Pie doesn't have OMS support? I did a full xda search on that and got no results. When I have time I will install another gsi rom and see what happens.
Click to expand...
Click to collapse
It's been quite awhile since I've tested descendant. That could be the case but I doubt it. OMS should be baked into the source code. I have been wrong before though. I'll see what I can find about that.
Spaceminer said:
It's been quite awhile since I've tested descendant. That could be the case but I doubt it. OMS should be baked into the source code. I have been wrong before though. I'll see what I can find about that.
Click to expand...
Click to collapse
I was just at the descendant telegram group and asked about OMS support. Dil3mma4 himself answered and said that they never really cared about substratum, nor do they now.
Motomizer said:
I was just at the descendant telegram group and asked about OMS support. Dil3mma4 himself answered and said that they never really cared about substratum, nor do they now.
Click to expand...
Click to collapse
I think this is the answer. It looks like it's unsupported.
Hey folks! I unlocked my FireTV stick and was able to install TWRP following the amazing guide by @k4y0z (https://forum.xda-developers.com/t/unlock-root-twrp-unbrick-fire-tv-stick-2nd-gen-tank.3907002/).
I can boot into TWRP just OK.
I am using adb shell to issue TWRP commands. (I don't have an OTG cable with power input).
I began by flashing stock ROMs by @0815hoffi from here (https://forum.xda-developers.com/t/...-7-ota-zip-launcher-replacement-root.4155489/).
Then I tried installing pre-rooted images by @rbox (https://forum.xda-developers.com/t/fire-tv-stick-2-tank-prerooted-stock-images-5-2-7-3_r1.3912271/) along with magisk.
Here are the general steps I followed while flashing these images :
1. wiping everything. I suspect my first issue here :
Code:
$ adb shell
$ twrp wipe cache
$ twrp wipe data
$ twrp wipe dalvik
$ twrp wipe /system
~ # twrp wipe cache
Formatting Cache using make_ext4fs...
Failed to mount '/cache' (No such device)
Done processing script file
Click to expand...
Click to collapse
~ # twrp wipe /system
Formatting System using make_ext4fs...
Failed to mount '/system' (No such device)
Done processing script file
Click to expand...
Click to collapse
~ # mount /cache
mount: mounting /dev/block/mmcblk0p12 on /cache failed: No such device
Click to expand...
Click to collapse
~ # stat /dev/block/mmcblk0p12
File: '/dev/block/mmcblk0p12'
Size: 0 Blocks: 0 IO Block: 4096 block special file
Device: ch/12d Inode: 5332 Links: 1 Device type: b3,c
Access: (0600/brw-------) Uid: ( 0/ root) Gid: ( 0/ root)
__bionic_open_tzdata: couldn't find any tzdata when looking for localtime!
__bionic_open_tzdata: couldn't find any tzdata when looking for GMT!
__bionic_open_tzdata: couldn't find any tzdata when looking for posixrules!
Access: 2010-01-01 00:17:58.000000000
Modify: 2010-01-01 00:17:57.000000000
Change: 2010-01-01 00:17:57.000000000
Click to expand...
Click to collapse
2. push images to /sdcard
Code:
$ adb push update-kindle-full_tank-288.6.6.4_user_664657620.bin /sdcard/firm.zip
update-kindle-full_tank-288.6.6.4_user... 6.1 MB/s (532252995 bytes in 83.009s)
3. Install image
adb shell
~ # twrp install /sdcard/firm.zip
Installing zip file '/sdcard/firm.zip'
Checking for Digest file...
Skipping Digest check: no Digest file found
[amonet] Remove boot patch...
[amonet] OK
Patching system image unconditionally...
Copying preloader_prod.img to boot partition 0 for secure device...
script succeeded: result was [][amonet] Install boot patch...
[amonet] OK
[amonet] Install recovery patch...
[amonet] ALREADY_INSTALLED
Done processing script file
Click to expand...
Click to collapse
4. `adb shell reboot`
They all install just OK. But in all cases, every time I do `reboot` in `adb shell` after `adb install` commands, it boots and gets stuck on 'fireTV Stick' logo.
At first I thought maybe it takes time to boot for first time, but I let it go for as long as half an hour and still no good.
I tried wiping cache and dalvik before rebooting too, no avail (had same could not mount /cache prompt).
I am pretty sure I am doing something stupid, I'd really appreciate any help. I'll be happy if I get it back to a working state, I do not really need root. This all started because the stick went into bootloop outta nowhere. My initial finding pointed at a failed update, see :
https://twitter.com/i/web/status/1393963756426698756
Maybe try with 5.2.7.7
ftvs2k-5.2.7.7
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
0815hoffi said:
Maybe try with 5.2.7.7
ftvs2k-5.2.7.7
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
Click to expand...
Click to collapse
Thanks @0815hoffi , that's actually the very first image I tried with from your thread.
Looking back, I think there's something wrong with my partitions.
If I see logs of other people from these threads, it says
script succeeded: result was [ALL DONE][amonet] Install boot patch...
Click to expand...
Click to collapse
Whereas for me, it says
script succeeded: result was [][amonet] Install boot patch...
Click to expand...
Click to collapse
This may mean that my flash is not successful, right? It's same everytime I flash.
I wonder, is there a way to bring everything to a clean state?
Given your expertise in amonet, @k4y0z from the thread and this comment, do you have a suspicion of what could be going wrong?
It looks like like it indeed were messed up partitions. My initial plan was to flash GPT fix in DL mode (by @k4y0z : link). But I thought might as well play with few things if am anyway going to re-do everything.
I started by going deleting directories manually (e.g. `rm -rf /system`). My plan was to manually flash each partition through fastboot.
Before that I attempted
Code:
fastboot format all
and received a bunch of errors, specifically
Code:
Formatting is not supported for file system with type ''.
Though format didn't work, I decided to wipe anyway
Code:
fastboot -w
It finished with few errors, but looked like it created those directories which I deleted earlier. So I rebooted to TWRP and did
Code:
twrp wipe data
Re-flashed @0815hoffi 's image and luckily it booted into "Optimising storage" screen. Post boot-up it appears to be working OK so far. Had an issue with wifi, but restart fixed it.
tl;dr
Code:
rm -rf /cache
rm -rf /data/dalvik
rm -rf /system
fastboot format userdata # errors
fastboot -w # completed but some errors
twrp wipe data
twrp install <img.zip>
reboot
EDIT : Looks like @Sus_i and @racega went through a similar journey and ended up with a similar fix. Good to know the fix is reproducible. Here's their posts : https://forum.xda-developers.com/t/...ck-2nd-gen-tank.3907002/page-61#post-83031003
saurabhshri said:
It looks like like it indeed were messed up partitions. My initial plan was to flash GPT fix in DL mode (by @k4y0z : link). But I thought might as well play with few things if am anyway going to re-do everything.
I started by going deleting directories manually (e.g. `rm -rf /system`). My plan was to manually flash each partition through fastboot.
Before that I attempted
Code:
fastboot format all
and received a bunch of errors, specifically
Code:
Formatting is not supported for file system with type ''.
Though format didn't work, I decided to wipe anyway
Code:
fastboot -w
It finished with few errors, but looked like it created those directories which I deleted earlier. So I rebooted to TWRP and did
Code:
twrp wipe data
Re-flashed @0815hoffi 's image and luckily it booted into "Optimising storage" screen. Post boot-up it appears to be working OK so far. Had an issue with wifi, but restart fixed it.
tl;dr
Code:
rm -rf /cache
rm -rf /data/dalvik
rm -rf /system
fastboot format userdata # errors
fastboot -w # completed but some errors
twrp wipe data
twrp install <img.zip>
reboot
EDIT : Looks like @Sus_i and @racega went through a similar journey and ended up with a similar fix. Good to know the fix is reproducible. Here's their posts : https://forum.xda-developers.com/t/...ck-2nd-gen-tank.3907002/page-61#post-83031003
Click to expand...
Click to collapse
Usually when this corrupted partitions happen you may try the command:
fastboot format userdata
followed by :
adb shell
(to call twrp#)
Then :
twrp wipe data
twrp wipe system
twrp wipe cache
twrp wipe dalvik
Then adb push the rom, gapps/magisk to /sdcard
twrp install nameofyourrom.zip
twrp install gappsxx.zip
Let it boot once and go back and update magisk via recovery.
(adb reboot recovery once permissions set or use powermenu little vic apk for quickness)
Another method I found which works good with fireos is :
When faced with corrupted/encrypted partition issues and/or unable to mount/format data issues
goto advanced wipe
select change file system
change it to EXT2
it will format data and data should appear become mount
hit back and change to EXT4 Filesystem again.
Then push rom and any other zips etc to /sdcard and install in usual way.
Good you got it working
Regards
Thank you for writing this down @Bertonumber1, I am sure it'll be very helpful to people who will encounter such situation in future.
Bertonumber1 said:
select change file system
change it to EXT2
it will format data and data should appear become mount
hit back and change to EXT4 Filesystem again.
Click to expand...
Click to collapse
I sincerely wish I could have done this. But I don't have an OTG with power input and deliveries are closed due to the pandemic. I was issuing TWRP commands through adb. I'll keep this in mind for future!
Thanks!
saurabhshri said:
Thank you for writing this down @Bertonumber1, I am sure it'll be very helpful to people who will encounter such situation in future.
I sincerely wish I could have done this. But I don't have an OTG with power input and deliveries are closed due to the pandemic. I was issuing TWRP commands through adb. I'll keep this in mind for future!
Thanks!
Click to expand...
Click to collapse
Ah I see, I'm sure the twrp can be commanded to repair change file systems. However, you are correct it is much easier via otg mouse or keyboard.
Regards