[Q] Why can't I encrypt my device? - G 2014 Q&A, Help & Troubleshooting

Hello,
I've been trying to encrypt my device for a while now. It always just goes to the encrypting icon, then waits a second and boots into CM12.1 again. Now I've tried to use adb logcat, where I was able to find this when starting encryption, just after all the SIGKILLs:
E/Cryptfs ( 229): Cannot open real block device /dev/block/platform/msm_sdcc.1/by-name/userdata
E/Cryptfs ( 229): Unable to get crypt_ftr_info
E/Cryptfs ( 229): Cannot get size of block device /dev/block/platform/msm_sdcc.1/by-name/userdata
Click to expand...
Click to collapse
I'm using CM12.1 titan linked here. However, I'm fairly certain that this is not a ROM issue, I've had it on all ROMs. Any help would be greatly appriciated.
~ Robin

maybe it really is the encryption footer?
Robin.S said:
I've been trying to encrypt my device for a while now. It always just goes to the encrypting icon, then waits a second and boots into CM12.1 again. Now I've tried to use adb logcat
Click to expand...
Click to collapse
(I'm sorry but it won't let me post links yet, you'll have to fix them below to use, I stripped the schemes, put them between LINK uppercase, and italicized the link text)
I'm getting the same thing, I just tried with 20150505 nightly cm12.1, this seems to a be a known issue, but with very little real information as to the problem. I found LINK forum.cyanogenmod.org/topic/88973-moto-g-cm11-encryption-failed/ LINK this forum post going back to mid 2014, and LINK jira.cyanogenmod.org/browse/CYAN-4532 LINK the linked JIRA bug which seems to indicate that all the Moto G devices (falcon, peregrine, titan), possibly Moto X as well are affected, but nobody seems to know what causes this bug, only vague hints that it may be a "timing related issue" but no other clarifying information in the now more than a year since this bug was posted.
The obvious conclusion is that nobody is encrypting their devices, which I find bizarre. Once Motorola releases a 5.1 factory ROM for this device (which is supposedly imminent -- they've already released for G-2013 and X-2014 I believe), I'll flash it and test that one.
I used logcat -v long and saw the times, the process kills definitely come after the attempts to open the block device fails. I did a logcat -c in one shell and then a vdc cryptfs enablecrypto inplace <password> in another (this is what the encrypt UI initiates), and the after the resulting softboot (it keeps the adb shell alive, and system uptime continues, so this isn't a hard boot), a logcat shows the same sequence:
Code:
[ 05-06 20:06:03.897 230: 287 E/Cryptfs ]
Cannot open real block device /dev/block/platform/msm_sdcc.1/by-name/userdata
[ 05-06 20:06:03.897 230: 287 E/Cryptfs ]
Unable to get crypt_ftr_info
[ 05-06 20:06:03.898 230: 287 E/Cryptfs ]
Cannot get size of block device /dev/block/platform/msm_sdcc.1/by-name/userdata
and then the kills start.
At first, because of the apparent inability to get crypt footer (in the error message), I thought this was lack of the 16k footer mentioned in the aforementioned bug, but LINK review.cyanogenmod.org/#/c/86684/ LINK the patch to include it appears to be long incorporated in LINK github.com/CyanogenMod/android_device_motorola_titan/blob/cm-12.1/BoardConfig.mk LINK our board's version of this file.
However, as I write this, I notice that the size in BoardConfig.mk does not correspond to the one on the device:
Code:
$ readlink /dev/block/platform/*/*/userdata
/dev/block/mmcblk0p38
$ grep mmcblk0p38 /proc/partitions
259 6 5774208 mmcblk0p38
$ bc
((5930598400 / 1024) - 5774208) / 1024
16.9843750000
they appear to differ by slightly more than 16k (the size of the encryption footer). But yet /system corresponds exactly with the line from BoardConfig.mk:
Code:
$ readlink /dev/block/platform/*/*/system
/dev/block/mmcblk0p36
$ grep mmcblk0p36 /proc/partitions
259 4 1130496 mmcblk0p36
$ bc
1157627904 / 1024
1130496.0000000000
so now I'm thinking that really is the problem (the userdata partition needs to have its size extended by 16k). But then there is LINK forum.cyanogenmod.org/topic/104204-xt1039-cm12-nightly-20150123-encryption-of-data-partition-not-working-simply-warm-reboots/ LINK this forum post which claims that the same partition encrypts fine with the stock image.
I didn't factory reset when flashing cm12.1 (from a stock 5.x ROM), which I think recreates the partition (?) So, maybe the partition didn't get resized to the correct value. However if the stock ROM handles this case, I should think CM would too.
What about you? Did you factory reset (including /data) when you installed CM on your Titan? I saw no need to get rid of /data (although I did have to delete some things in /data/misc to get rotation working) when coming from stock ROM and wanted to avoid having to redo everything. Which worked fine... except for this

Related

[DEV][BUILD0 - PREALPHA]HW TEST: OMAPZoom AOSP 4.1.2 JZO54K

Hi Folks, Not to be left out of all the 4.1.2 Fun, Here's a little teaser of what's to come!
{
"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"
}
ROM STATUS: BUILD0 PREALPHA - OFFLINE - AWAITING UPDATE
Click to expand...
Click to collapse
NOTE: SEE THIS POST FOR THE LATEST DETAILED ROM INFORMATION
Click to expand...
Click to collapse
NOTE: SEE THIS POST FOR THE LATEST DEVELOPMENT INFORMATION
Click to expand...
Click to collapse
Now Go! We Make Rom Now!
NOTES: ETA? DON'T EVEN ASK! :laugh:
Great Work !
[BUILD0]Touchscreen, OpenGLES and CWM Test!
Hi Folks.
Feeling Adventurous? Then You Might want to have a quick go this OmapZoom AOSP 4.1.2 JZO54K That I've prepared It's in it very early stages but It would be help if some folks could give it blast and let me know if the TouchScreen functionality is working as my touchscreen hasn't worked for a long time and as such it is some I can't test. If the lastest version of Android wasn't enough of a draw, This rom also includes the work I've done with CWM Recovery.
BUILD INFORMATION AND DETAILS
What's BUILD0?
Good Question, Build0 ( Build Zero ) is pre-alpha release aimed at testing specific hardware functionality and software features.
Hardware - Working
Touchscreen (?!?) - The Drivers are installed so it "should" just work
Archos 3G / Huawei + Others 3G Dongles - The Hardware will be recognized but there is nothing implemented in Android user land as yet.
Hardware - Not Working
Everything else! - To be implemented in future builds[/QUOTE]
Software Information
The main software/driver focus of this build was getting the PowerVR Drivers to function to enable HW Acceleration. This has been achieved not only using the stock kernel modules ( as one would expect ) but also on test custom kernel builds. This is an area along with the Camera that has proved problematic when attempting previous ports and is something I wanted to solve early on.
Hacking On It!
Source Code Info : See Separate Post on building and source code info [ COMING SOON ]
Kernel Version : Archos Stock 3.0.21 - This will change in the next build to use a kernel with JellyBean Specific features plus some extra treats , For anyone interested in hacking on this current build I have included all the stock kernel modules, they can be found /system/lib/modules. Of course the kernel modules for most hardware is only half the story as many devices also require a binary firmware blob which is not included but can be grabbed from the Archos 3.0.25 Firmware.
StabilityThe build seems pretty stable overall but although the incorrect battery percentage do make a it wobble a little
Clockwork Mod Recovery - I will update the CWM thread with details regarding bugs and testing etc but just to say, It's seems fully functional with very few minor issues.
Installation - Please See The Installation Instructions For Details
Installation Guide
Installation Guide
STOP! HAVE YOU TAKEN A BACKUP OF YOUR IMPORTANT DATA
Although your existing data is not touched, It is advised you backup your data directory before proceeding.
Click to expand...
Click to collapse
ALL THE USUAL DISCLAIMERS APPLY, FILES ARE PROVIDED AS-IS AND WITHOUT WARRANTY ,
ITS YOUR DEVICE, YOUR RESPONSIBILITY, I'M NOT YOUR DAD!
Click to expand...
Click to collapse
Build0 - Requirements
Archos G9 SD Version
android sdk / android debug bridge ( adb )
SDE Enabled Firmware ( unofficial or official )
common sense.
NOTE: I've only tested this using Linux , The procedure should be the same on Windows but we don't know until we try.
Assumptions
1.You know how to flash a SDE initramfs and zImage either through the Developer Menu or using kd_flasher from the adb command line,
2.You know how to boot your device into the Special Developer Edition Firmware ( SDE )
3.You have setup adb correctly a your device is listed in the adb devices list.
Build0 - Installation Steps
1. Download and unpack the cwm boot image [ Hotfile :/archosg9-jzo54k-cwmboot.7z ]
2. Download and unpack the system image [ CURRENTLY OFFLINE - AWAITING UPDATE ]
3. Flash the unpacked zImage and initramfs.cpio.lzo using the [Recovery]/[Developer Edition Menu]/[Flash Kernel and initramfs] option in Archos recovery mode.
4. Reboot Into Developer Edition ; You should now see the Familiar CWM User Interface, You should see a couple of error messages regarding mounting /cache/recovery/command and /cache/recovery/log. This is expected.
5. use adb to push the unpacked system.img to the /._ directory on the device with the following command
Code:
[B]adb push system.img /._/system.img [/B]
NOTE: The system.img is 500MB in size and it may take some time for the transfer to be completed
6. When the file transfer is complete, reboot the device either using the CWM UI or adb reboot, The device should reboot back into CWM, The previous error messages will still present, Again this is the expected behaviour.
At this point, if everything is ok you should be able the use adb shell commands. Lets check the mount points using
Code:
[B]adb shell mount[/B]
The output should be as follows
Code:
rootfs on / type rootfs (rw)
tmpfs on /dev type tmpfs (rw,nosuid,relatime,mode=755)
devpts on /dev/pts type devpts (rw,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
none on /acct type cgroup (rw,relatime,cpuacct)
tmpfs on /mnt/asec type tmpfs (rw,relatime,mode=755,gid=1000)
tmpfs on /mnt/obb type tmpfs (rw,relatime,mode=755,gid=1000)
none on /dev/cpuctl type cgroup (rw,relatime,cpu)
/dev/block/mmcblk0p1 on /mnt/rawfs type rawfs (rw,relatime)
/dev/block/mmcblk0p4 on /._ type ext4 (rw,relatime,user_xattr,barrier=1,data=ordered)
/dev/block/loop0 on /system type ext4 (rw,relatime,user_xattr,barrier=1,data=ordered)
/sys/kernel/debug on /sys/kernel/debug type debugfs (rw,relatime)
If you see the message
Code:
- exec '/system/bin/sh' failed: No such file or directory (2) -
Then either you have not followed the instructions correctly or I've not typed them up correctly! Either way something's not right. See the troubleshooting section below for tips on how to check what's what.
7. Next we need to create a ext4 image for the cache and data partitions. This involves create an empty file with dd, loop mount the file as a block device using losetup then making the filesystem using mk2fs.ext2. Sounds like a lot of work. I thought so too, so all you need to do is run the following adb shell command
Code:
adb shell createfs
This will create a 500MB cache image and a 2GB data image. Again because of the file sizes involved this does take a couple of minutes to complete. Please be patient, when the command is completed the full output should look as follows
Code:
File System Image Creation Script - For Test Purpose Only
/dev/block/mmcblk0p4 /._
FileSystem Container /dev/block/mmcblk0p4 Mounted at /._.....
Checking Available Space.
Available Space : 5129
Creating cache image at /._/CAC With Block 500000
500000+0 records in
500000+0 records out
512000000 bytes (488.3MB) copied, 39.070434 seconds, 12.5MB/s
DD Returned 0 : Loop Mounting the raw image /._/CAC to /dev/block/loop1
Creating Ext FileSystem on /dev/block/loop1
warning: 287 blocks unused
Filesystem label=
OS type: Linux
Block size=1024 (log=0)
Fragment size=1024 (log=0)
125416 inodes, 499713 blocks
25000 blocks (5%) reserved for the super user
First data block=1
Maximum filesystem blocks=524288
61 block groups
8192 blocks per group, 8192 fragments per group
2056 inodes per group
Superblock backups stored on blocks:
8193, 24577, 40961, 57345, 73729, 204801, 221185, 401409
Creating data image at /._/DATA With Block 2000000
2000000+0 records in
2000000+0 records out
2048000000 bytes (1.9GB) copied, 175.243408 seconds, 11.1MB/s
DD Returned 0 : Loop Mounting the raw image /._/DATA to /dev/block/loop2
Creating Ext FileSystem on /dev/block/loop2
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
125184 inodes, 500000 blocks
25000 blocks (5%) reserved for the super user
First data block=0
Maximum filesystem blocks=4194304
16 block groups
32768 blocks per group, 32768 fragments per group
7824 inodes per group
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912
8. Reboot the device. The device will once a gain reboot into CWM Recovery. This time there should be no error messages. check everyhting is mounted and created correctly using
Code:
adb shell mount
The output should look as follows
Code:
rootfs on / type rootfs (rw)
tmpfs on /dev type tmpfs (rw,nosuid,relatime,mode=755)
devpts on /dev/pts type devpts (rw,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
none on /acct type cgroup (rw,relatime,cpuacct)
tmpfs on /mnt/asec type tmpfs (rw,relatime,mode=755,gid=1000)
tmpfs on /mnt/obb type tmpfs (rw,relatime,mode=755,gid=1000)
none on /dev/cpuctl type cgroup (rw,relatime,cpu)
/dev/block/mmcblk0p1 on /mnt/rawfs type rawfs (rw,relatime)
/dev/block/mmcblk0p4 on /._ type ext4 (rw,relatime,user_xattr,barrier=1,data=ordered)
/dev/block/loop0 on /data type ext4 (rw,nosuid,nodev,relatime,user_xattr,barrier=1)
/dev/block/loop1 on /cache type ext4 (rw,nosuid,nodev,relatime,user_xattr,barrier=1)
/dev/block/loop2 on /system type ext4 (rw,relatime,user_xattr,barrier=1,data=ordered)
/sys/kernel/debug on /sys/kernel/debug type debugfs (rw,relatime)
9. Congratulations You now have Jellyean and CWM Recovery running on you device
One Last time choose "reboot system now" from the cwm menu to taste those JellyBeans!
TROUBLESHOOTING
Ok you've got problems, nothing that cannot be worked around.
Investigating
Code:
- exec '/system/bin/sh' failed: No such file or directory (2) -
If you run into this error then I means that your system.img is not present on the device or has not been mounted correctly for some reason. because of the way the device recovery is setup at the minute adb still looks for it's shell binary in /system/bin this only exists if the system is mounted. Fortunately we still have a couple of adb commands at our disposal, namely pull and push, the work around this issue you do the following [ Example uses Bash Terminal on Linux ]
Code:
adb pull /sbin/busybox
chmod +x busybox # Linux Only - Make sure busybox is still executable
adb push /system/bin/sh
You should now be able to drop into an interactive shellk using
Code:
adb shell
A further trick to make sure you have access to all the commands is to symlink the contents of /sbin to /system/bin. like so
Code:
a s "ln -s /sbin/* /system/bin"
More Troubleshooting Soon! If folks get stuck.
Development Information
It turns out, perhaps unsurprisingly that the omapzoom.org aosp repo is the one for us!
I did some light changes to the blaze_tablet device tree, which mainly involved changing the word blaze to archos .
Once again I've got the powervr drivers loading successful, because archos are using the latest version we don't have to rip them off the device as the userland binaries in the device/ti/proprietary-open.git work fine.
As this is the very first build I've scaled everything back, so what you've basically got is a booting rom to hack on. Apart from the powervr drivers everything else is untested and presumed not working. Also the kernel needs rebuilding to include tracing.
If anyone fancies hacking on this, get the source from http://omapzoom.org and the archos device tree can be found on my github. place the device files in a device/ti/archos_tablet directory.
Use the jb-mr0-release branch, I had some trouble building the development branch (jb-mr0-dev), clearly someone has committed some breaking changes.....
One more for luck
Don't you just hate it when the op does this
zImage and initramfs.cpio.lzo
I flashed the zImage and initramfs.cpio.lzo, rebooted. No CWM menu, still SDE. What should I do next, try pushing system.img anyway?
stevemp
stevemp said:
I flashed the zImage and initramfs.cpio.lzo, rebooted. No CWM menu, still SDE. What should I do next, try pushing system.img anyway?
stevemp
Click to expand...
Click to collapse
Hi There,
That's very strange. This should have replaced the existing SDE Booting Procedure, I wouldn't push the system.img quite yet
I have a couple of questions?
What Model Tablet Do You Have?
Are you running An SDE Rom Already, If so which one?
Is your SDE Official or Unofficial?
Have You Removed The Android Kernel Using the Recovery Menu Option?
Did you flash using the Recovery/Developer Edition menu option?
Are you using Windows or Linux?
Can you elaborate on "Still SDE", Do You Mean It Booted into your existing Rom?
That should be good for starters,
Thanks
trevd said:
Hi There,
That's very strange. This should have replaced the existing SDE Booting Procedure, I wouldn't push the system.img quite yet
I have a couple of questions?
What Model Tablet Do You Have?
Are you running An SDE Rom Already, If so which one?
Is your SDE Official or Unofficial?
Have You Removed The Android Kernel Using the Recovery Menu Option?
Did you flash using the Recovery/Developer Edition menu option?
Are you using Windows or Linux?
Can you elaborate on "Still SDE", Do You Mean It Booted into your existing Rom?
That should be good for starters,
Thanks
Click to expand...
Click to collapse
Archos 80 G9 OMAP 4460 1.2 Ghz 512 Mb ram [email protected]_V04
Never mind, let tablet reboot CWM menu showed up. I thought supposed to reboot into SDE.
Jelly Bean boots but touch screen not working
stevemp
stevemp said:
Archos 80 G9 OMAP 4460 1.2 Ghz 512 Mb ram [email protected]_V04
I think SDE is official, not sure how to find out.
Windows 7 64 bit.
SDE -> Developer Edition Menu -> Flash Kernel & Initramfs -> copied zImage and initramfs.cpio.lzo rebooted -> held power button and volume down -> went back to SDE -> Developer Edition Menu -> still looks the same.
stevemp
Click to expand...
Click to collapse
Ok Thanks Again for the Feedback.
I think the official SDE is watermarked! I also think we might have our wires crossed and you've misunderstood ( more likely I've not explained clearly ) Just what this is. This does NOT replace the existing Archos Recovery Menus. On technical level it is an SDE Rom which can be booted between android and recovery effectively adding an extra boot mode to SDE, This sits apart from the Archos BootMenu Stuff.
I suppose a good way to think about it is in the following structure.
Code:
Archos Boot Menu
Android
Recovery
Developer Edition -----> Android
Recovery
So You actually load the developer edition to use this recovery. Flashing and Booting these Files won't affect any other Rom/Data on the Tablet as the Partitions are self contained in there own image files. So you can easily return to [email protected] by flashing a "Classic" initramfs and kernel.
If You still can't boot into CWM You might want to have a go with the alternative flashing method using adb. It's a lot easier than all that Vol+Down Stuff.
When Booted in android, run the following commands
Code:
adb push zImage /data/local/zImage
adb push initramfs.cpio.lzo /data/local/initramfs.cpio.lzo
adb shell "kd_flasher -i /data/local/initramfs.cpio.lzo -k/data/local/zImage"
adb shell "reboot_into sde"
Thanks Again
stevemp said:
Archos 80 G9 OMAP 4460 1.2 Ghz 512 Mb ram [email protected]_V04
Never mind, let tablet reboot CWM menu showed up. I thought supposed to reboot into SDE.
stevemp
Click to expand...
Click to collapse
Beat Me Too It, See my above post.... :victory:
Oh well stands as a good explanation
Jelly Bean
Boots into Jelly Bean, touch screen not working.
Awaiting further instructions.
stevemp
stevemp said:
Boots into Jelly Bean, touch screen not working.
Awaiting further instructions.
stevemp
Click to expand...
Click to collapse
OK Thanks for the test.... To use the classic phrase, It's not you It's me , I think I'm missing some layout files, Nice to hear you got it Booted.
One piece of probably useful information I've omitted! You can boot back into CWM using adb, while booted into JellyBean use
Code:
adb reboot recovery
Recovery should be fully working, You can flash zip i.e gapps CWM-SU etc, The sdcard mount point tries to mount the external sdcard as fat32 ( for now ).
once the external sdcard is mounted you should be able to run a backup
No more instructions at the minute I'm afraid but I'll get right on it.
Once again Thanks for the Testing and Feedback, It's been very useful.
Just for Archos Gen9 SD ?
why and what kind of gen9 ?
i have 3 gen 9
8" 1ghz 16 go
10" 1.5ghz 16go
10" 1.5ghz 250go
cajl said:
Just for Archos Gen9 SD ?
why and what kind of gen9 ?
i have 3 gen 9
8" 1ghz 16 go
10" 1.5ghz 16go
10" 1.5ghz 250go
Click to expand...
Click to collapse
Should be good for all Gen9 SD's and in time HD versions as well, Can't test with HD Versions because I don't have one! :laugh:
If you want i will be testing this afternoon on the HD
and if the dl is ok
stevemp said:
Boots into Jelly Bean, touch screen not working.
Awaiting further instructions.
stevemp
Click to expand...
Click to collapse
Hi!
Touch screen driver will be ok!
I think should be ok with the curent driver from 4.0.25 !
....just let time to trevd for add this stuff! :good:
surdu_petru said:
Hi!
Touch screen driver will be ok!
I think should be ok with the curent driver from 4.0.25 !
....just let time to trevd for add this stuff! :good:
Click to expand...
Click to collapse
All ready on it. missing /system/usr/idc ( input device configurations ) , they can be pull from an existing archos rom
For those who are interested.
http://source.android.com/tech/input/input-device-configuration-files.html
http://source.android.com/tech/input/touch-devices.html
I seem to recall the wireless xbox 360 pad being added using ( i think ) this method. I'll have a quick look, I might throw that in if its not too difficult
trevd said:
All ready on it. missing /system/usr/idc ( input device configurations ) , they can be pull from an existing archos rom
For those who are interested.
http://source.android.com/tech/input/input-device-configuration-files.html
http://source.android.com/tech/input/touch-devices.html
I seem to recall the wireless xbox 360 pad being added using ( i think ) this method. I'll have a quick look, I might throw that in if its not too difficult
Click to expand...
Click to collapse
Hi!
Thanks TREVD!
A very very very good job!!! :good:
My device is it now on Service Centre for reparation ( touchscreen issue! ) for 3 , 4 week!
I can't wait to test all your stuff!
Thank's again and good luck! :good:

[Q] Loop in bootanimation after update to CROMi-X 7.0.2

Hi to everyone.
I was updating my tab to the latest version of the ROM of sbdags.
Everything was fine until i reboot the tab to use it for the first time: loop in the boot animation and never come out from it.
I came from the previous version of the rom, the Cromi-x 6.1 with 10.26.1.18 bootloader.
The process i use to update was this:
1) wipe of data/factory reset, wipe with format /boot, wipe with format /system
2) Install the CWM recovery 6.0.5.0 and update the bootloader to 11.4.1.17 by flashing they with the file that you can find in the rom page.
3) repeat point 1
4) install the rom by flashing it from an SD. Complete the Aroma installer and answer to every option that it ask to me.
5) reboot the system and stuck in the bootanimation
I use the WW format cause i'm italian and i check the md5
What's wrong? I can go to recovery everytime i need and i have a backup just in case i need it.
Sdbags, i really want to offer you a beer for your work. I think i will do it in every case, but yes, kitkat on my tab would be great :victory:
Sorry for bad english. For every question, i'm here. Thanks a lot.
M.
aMachi said:
Hi to everyone.
I was updating my tab to the latest version of the ROM of sbdags.
Everything was fine until i reboot the tab to use it for the first time: loop in the boot animation and never come out from it.
I came from the previous version of the rom, the Cromi-x 6.1 with 10.26.1.18 bootloader.
The process i use to update was this:
1) wipe of data/factory reset, wipe with format /boot, wipe with format /system
2) Install the CWM recovery 6.0.5.0 and update the bootloader to 11.4.1.17 by flashing they with the file that you can find in the rom page.
3) repeat point 1
4) install the rom by flashing it from an SD. Complete the Aroma installer and answer to every option that it ask to me.
5) reboot the system and stuck in the bootanimation
I use the WW format cause i'm italian and i check the md5
What's wrong? I can go to recovery everytime i need and i have a backup just in case i need it.
Sdbags, i really want to offer you a beer for your work. I think i will do it in every case, but yes, kitkat on my tab would be great :victory:
Sorry for bad english. For every question, i'm here. Thanks a lot.
M.
Click to expand...
Click to collapse
Don't do step 3. Try it again please.
Try the default options first.
sbdags said:
Don't do step 3. Try it again please.
Try the default options first.
Click to expand...
Click to collapse
If default option are those who are pre-selected on the aroma installer i've already try it.
Also i try to do it without point 3. Nothing
Here a log of the installation of the rom
AROMA INSTALLER version 2.56
(c) 2012 by amarullz xda-developers
ROM Name : CROMi-Xenogenesis KitKat
ROM Version : 7.0.2 DEODEX
ROM Author : sbdags
Device : Asus Transformer TF701T
Start at : Mon Aug 25 20:30:02 2014
Thank you for installing CROMi-Xenogenesis KitKat 4.4.2!
Sit back and relax...
-----------------------------------------------------
This will take a few minutes!
Preparing File System...
about to run program [/sbin/umount] with 3 args
umount: can't umount /system: Invalid argument
run_program: child exited with status 1
about to run program [/sbin/umount] with 3 args
Formatting System....
Creating filesystem with parameters:
Size: 2147483648
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 8192
Label:
Blocks: 524288
Block groups: 16
Reserved block group size: 127
Created filesystem with 11/131072 inodes and 17193/524288 blocks
Tuning System....
about to run program [/tmp/tune2fs.ext4] with 6 args
tune2fs 1.41.12 (17-May-2010)
Tuning Data - Journaling Enabled.....
about to run program [/tmp/tune2fs.ext4] with 6 args
tune2fs 1.41.12 (17-May-2010)
Wiping Cache.....
Installing Core System.....
Installing Options...
Region Specific Files
- TF701 WW Build
Kernel Preparation
- sbdag's 11.4.1.17 Stock Modded Kernel
package_extract_file: no extras/kernel/sbmodded/701sb3.img in package
DPI Preparation
- 320 DPI
Resolution Preparation
- 2560x1600 res
Boot Animation
- Google Android-L
Launcher
- Asus Stock Launcher
Asus Apps 1
- Asus Email
- Asus Desk Clock & Widget
- Asus Weather & Time Widget
- Asus Splendid
- Asus Calculator
- Asus MyDictionary
- Asus Studio
Asus Apps 2
Google Apps 1
- Google Calendar
- Google Now and Voice Search
- Google Music
- News and Weather Genie
- YouTube
- Maps
- Hangouts
Google Apps 2
- Google Chrome
- Google Drive Docs
Misc Apps
- ES File Explorer
- AdAway installed
- Keyboard Manager
- Terminal Emulator
- Polaris Office
Installing CROMi-X System Tweaks.....
about to run program [/tmp/cromix-build-prop.sh] with 1 args
Tweaks and Scripts
- Browser2RAM enabled
- Ad Blocker enabled
- Zip Align Script installed
- Keyboard Dock Remapping installed
Building symlinks.....
Setting permissions.....
Installing BusyBox.....
about to run program [/system/xbin/busybox] with 4 args
Setting ROOT.....
DRM Options
- Google Video & Hulu+ DRM
Installing build.prop
about to run program [/sbin/sh] with 2 args
about to run program [/sbin/sh] with 2 args
Finalising ROM
about to run program [/sbin/umount] with 3 args
---------------------------------------
All Done!
Don't forget to follow @sbdags on Twitter
If you like it please donate to [email protected] on paypal
Enjoy CROMi-X!
script succeeded: result was [Enjoy CROMi-X!]
Installer Sucessfull (Status 0)
I don't know if this can be helpful, but if i restore the backup of the previous version of the rom everything work fine. I'm reading the discussion of the guy with the partition problem and i was wondering if maybe the problem was the same, but i don't think it.
Another time, sorry for bad english and thanks for all your work sdbags.
M.
That log is fine - everything is installed.
Read out the bootloader version from the bootloader screen to double check please.
Also you are rebooting after installing the bootloader and cwm package aren't you?
aMachi said:
If default option are those who are pre-selected on the aroma installer i've already try it.
Also i try to do it without point 3. Nothing
Here a log of the installation of the rom
AROMA INSTALLER version 2.56
(c) 2012 by amarullz xda-developers
ROM Name : CROMi-Xenogenesis KitKat
ROM Version : 7.0.2 DEODEX
ROM Author : sbdags
Device : Asus Transformer TF701T
Start at : Mon Aug 25 20:30:02 2014
Thank you for installing CROMi-Xenogenesis KitKat 4.4.2!
Sit back and relax...
-----------------------------------------------------
This will take a few minutes!
Preparing File System...
about to run program [/sbin/umount] with 3 args
umount: can't umount /system: Invalid argument
run_program: child exited with status 1
about to run program [/sbin/umount] with 3 args
Formatting System....
Creating filesystem with parameters:
Size: 2147483648
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 8192
Label:
Blocks: 524288
Block groups: 16
Reserved block group size: 127
Created filesystem with 11/131072 inodes and 17193/524288 blocks
Tuning System....
about to run program [/tmp/tune2fs.ext4] with 6 args
tune2fs 1.41.12 (17-May-2010)
Tuning Data - Journaling Enabled.....
about to run program [/tmp/tune2fs.ext4] with 6 args
tune2fs 1.41.12 (17-May-2010)
Wiping Cache.....
Installing Core System.....
Installing Options...
Region Specific Files
- TF701 WW Build
Kernel Preparation
- sbdag's 11.4.1.17 Stock Modded Kernel
package_extract_file: no extras/kernel/sbmodded/701sb3.img in package
DPI Preparation
- 320 DPI
Resolution Preparation
- 2560x1600 res
Boot Animation
- Google Android-L
Launcher
- Asus Stock Launcher
Asus Apps 1
- Asus Email
- Asus Desk Clock & Widget
- Asus Weather & Time Widget
- Asus Splendid
- Asus Calculator
- Asus MyDictionary
- Asus Studio
Asus Apps 2
Google Apps 1
- Google Calendar
- Google Now and Voice Search
- Google Music
- News and Weather Genie
- YouTube
- Maps
- Hangouts
Google Apps 2
- Google Chrome
- Google Drive Docs
Misc Apps
- ES File Explorer
- AdAway installed
- Keyboard Manager
- Terminal Emulator
- Polaris Office
Installing CROMi-X System Tweaks.....
about to run program [/tmp/cromix-build-prop.sh] with 1 args
Tweaks and Scripts
- Browser2RAM enabled
- Ad Blocker enabled
- Zip Align Script installed
- Keyboard Dock Remapping installed
Building symlinks.....
Setting permissions.....
Installing BusyBox.....
about to run program [/system/xbin/busybox] with 4 args
Setting ROOT.....
DRM Options
- Google Video & Hulu+ DRM
Installing build.prop
about to run program [/sbin/sh] with 2 args
about to run program [/sbin/sh] with 2 args
Finalising ROM
about to run program [/sbin/umount] with 3 args
---------------------------------------
All Done!
Don't forget to follow @sbdags on Twitter
If you like it please donate to [email protected] on paypal
Enjoy CROMi-X!
script succeeded: result was [Enjoy CROMi-X!]
Installer Sucessfull (Status 0)
I don't know if this can be helpful, but if i restore the backup of the previous version of the rom everything work fine. I'm reading the discussion of the guy with the partition problem and i was wondering if maybe the problem was the same, but i don't think it.
Another time, sorry for bad english and thanks for all your work sdbags.
M.
Click to expand...
Click to collapse
sbdags said:
That log is fine - everything is installed.
Read out the bootloader version from the bootloader screen to double check please.
Also you are rebooting after installing the bootloader and cwm package aren't you?
Click to expand...
Click to collapse
When i install cwm and bootloader package i reboot from cwm but i stuck in boot animation. The same that happen when i try to reboot after install the rom.
In bootloader screen i read
Android macallan-user BL released by WW_epad-11.4.1.17-20140711
aMachi said:
When i install cwm and bootloader package i reboot from cwm but i stuck in boot animation. The same that happen when i try to reboot after install the rom.
In bootloader screen i read
Android macallan-user BL released by WW_epad-11.4.1.17-20140711
Click to expand...
Click to collapse
Right and then you boot back to CWM, do a full wipe (you may need to wipe your internal sdcard so back it up first) and then flash the rom. After that it should boot fine.
If not please search xda for how to get a logcat and post one of it bootlooping please.
sbdags said:
Right and then you boot back to CWM, do a full wipe (you may need to wipe your internal sdcard so back it up first) and then flash the rom. After that it should boot fine.
If not please search xda for how to get a logcat and post one of it bootlooping please.
Click to expand...
Click to collapse
I try the first thing that you say but nothing, still loop in bootanimation.
I'll do a logcat through adb in the afternoon. Now i had some problem cause i can't mount usb storage through cwm for some reason. Late i'll find drivers or what's missing.
Maybe can help: when i reboot frequently cwm ask me if i want to fix root. It's normal?
Thanks you for your help.
aMachi said:
I try the first thing that you say but nothing, still loop in bootanimation.
I'll do a logcat through adb in the afternoon. Now i had some problem cause i can't mount usb storage through cwm for some reason. Late i'll find drivers or what's missing.
Maybe can help: when i reboot frequently cwm ask me if i want to fix root. It's normal?
Thanks you for your help.
Click to expand...
Click to collapse
That message is normal. Just a bug in CWM.
We need to find why you are bootlooping.
sbdags said:
That message is normal. Just a bug in CWM.
We need to find why you are bootlooping.
Click to expand...
Click to collapse
Ok, logcat is here.
Hope it can help.
aMachi said:
Ok, logcat is here.
Hope it can help.
Click to expand...
Click to collapse
OK You got some serious problems there. It would appear that your internal sdcard doesn't mount:
Code:
D/Vold ( 359): Volume sdcard state changing -1 (Initializing) -> 0 (No-Media)
D/Vold ( 359): *********** Success!! "ro.epad.mount_point.sdcard=/mnt/media_rw/sdcard"
D/Vold ( 359): Volume usbdrive state changing -1 (Initializing) -> 0 (No-Media)
D/Vold ( 359): *********** Success!! "ro.epad.mount_point.usbdrive=/mnt/media_rw/usbdrive"
I/Vold ( 359): opening the sysfs of TF701
E/Vold ( 359): lookupVolume usbdisk1 failed!
E/Vold ( 359): lookupVolume usbdisk2 failed!
E/Vold ( 359): lookupVolume sdreader failed!
D/Vold ( 359): checkUsbdisk sucess.
D/DirectVolume( 359): i:0 minor:48
D/Vold ( 359): Volume sdcard state changing 0 (No-Media) -> 2 (Pending)
D/DirectVolume( 359): i:1 minor:49
D/Vold ( 359): Volume sdcard state changing 2 (Pending) -> 1 (Idle-Unmounted)
@lj50036, @_that any suggestions for this one?
@aMachi - what is the SKU of your device? And you can restore a nandroid back to 4.3 and it works fine?
sbdags said:
OK You got some serious problems there. It would appear that your internal sdcard doesn't mount:
Code:
D/Vold ( 359): Volume sdcard state changing -1 (Initializing) -> 0 (No-Media)
D/Vold ( 359): *********** Success!! "ro.epad.mount_point.sdcard=/mnt/media_rw/sdcard"
D/Vold ( 359): Volume usbdrive state changing -1 (Initializing) -> 0 (No-Media)
D/Vold ( 359): *********** Success!! "ro.epad.mount_point.usbdrive=/mnt/media_rw/usbdrive"
I/Vold ( 359): opening the sysfs of TF701
E/Vold ( 359): lookupVolume usbdisk1 failed!
E/Vold ( 359): lookupVolume usbdisk2 failed!
E/Vold ( 359): lookupVolume sdreader failed!
D/Vold ( 359): checkUsbdisk sucess.
D/DirectVolume( 359): i:0 minor:48
D/Vold ( 359): Volume sdcard state changing 0 (No-Media) -> 2 (Pending)
D/DirectVolume( 359): i:1 minor:49
D/Vold ( 359): Volume sdcard state changing 2 (Pending) -> 1 (Idle-Unmounted)
@lj50036, @_that any suggestions for this one?
@aMachi - what is the SKU of your device? And you can restore a nandroid back to 4.3 and it works fine?
Click to expand...
Click to collapse
i've some problem to find the SKU code. I search on the box of the tablet but there are too many codes and i don't know what's the right. Can you give me an exemple of it?
Yes, i can restore to 4.3. In this right moment i'm writing with the tab with cromix 6. Everything seems to work fine.
In case like this you really know how much important is to do a backup..
aMachi said:
i've some problem to find the SKU code. I search on the box of the tablet but there are too many codes and i don't know what's the right. Can you give me an exemple of it?
Yes, i can restore to 4.3. In this right moment i'm writing with the tab with cromix 6. Everything seems to work fine.
In case like this you really know how much important is to do a backup..
Click to expand...
Click to collapse
SKU is just your country code - so if you have changed it it could be causing issues with the clean install.
US, WW, TW, CN, JP are the only 5 I know of.
So if you changed the bootloader from US to WW I heard another user reporting some issues.
But in your case I am at a loss as to how you can boot 4.3 but not 4.4.2 as you are apparently on a 4.4.2 compatible bootloader and recovery .......
sbdags said:
SKU is just your country code - so if you have changed it it could be causing issues with the clean install.
US, WW, TW, CN, JP are the only 5 I know of.
So if you changed the bootloader from US to WW I heard another user reporting some issues.
But in your case I am at a loss as to how you can boot 4.3 but not 4.4.2 as you are apparently on a 4.4.2 compatible bootloader and recovery .......
Click to expand...
Click to collapse
Ah, right, i understand. I am WW, and i use it in every installation that i've done on my eee pad, from the rooting process and the unlocking of bootloader to the change of the rom.
Now that i am on the previous version of your rom those are infos of kernel, firmware, ecc.
Android Version 4.3
Kernel Version 3.4.57-g47dbe4d [email protected]#1
Tue Dec 17 23.26.15 CST 2013
Build Number TF701T_CROMi-Xenogenesis-6.1-WW_DEODEX-ORIGINAL-10.26.1.18 020115_201310210002
In ROM Manager i can see that my Recovery still is the 6.0.5.0 version.
In bootloader i can see that it is "WW_epad-11.4.1.17-20140711"
Hope that this might be helpful and hope that i don't write anything of unsafe.
M.
aMachi said:
Ah, right, i understand. I am WW, and i use it in every installation that i've done on my eee pad, from the rooting process and the unlocking of bootloader to the change of the rom.
Now that i am on the previous version of your rom those are infos of kernel, firmware, ecc.
Android Version 4.3
Kernel Version 3.4.57-g47dbe4d [email protected]#1
Tue Dec 17 23.26.15 CST 2013
Build Number TF701T_CROMi-Xenogenesis-6.1-WW_DEODEX-ORIGINAL-10.26.1.18 020115_201310210002
In ROM Manager i can see that my Recovery still is the 6.0.5.0 version.
In bootloader i can see that it is "WW_epad-11.4.1.17-20140711"
Hope that this might be helpful and hope that i don't write anything of unsafe.
M.
Click to expand...
Click to collapse
NO that is expected but hat is not expected is why you can't boot 4.4.2. Let's wait for _that and lj50036 to cast their expert eyes over your issues.
sbdags said:
@lj50036, @_that any suggestions for this one?
Click to expand...
Click to collapse
This seems to be the core of the problem:
Code:
E/dalvikvm(13002): JNI posting fatal error: Native registration unable to find class 'com/android/internal/os/RuntimeInit'; aborting...
Check that the framework is correctly installed and the BOOTCLASSPATH is set correctly:
Code:
adb shell echo $BOOTCLASSPATH > bootclasspath.txt
adb shell ls -l /system/framework > framework.txt
_that said:
This seems to be the core of the problem:
Code:
E/dalvikvm(13002): JNI posting fatal error: Native registration unable to find class 'com/android/internal/os/RuntimeInit'; aborting...
Check that the framework is correctly installed and the BOOTCLASSPATH is set correctly:
Code:
adb shell echo $BOOTCLASSPATH > bootclasspath.txt
adb shell ls -l /system/framework > framework.txt
Click to expand...
Click to collapse
Ok, so maybe now i need some help.
I run adb in my pc then i type adb shell to run the remote shell interactively.
Then what i need to type?
Anyway if i type "ls -l /system/framework > framework.txt" the response is "No such file or directory"
Sorry for my n00b questions. Really hope to learn something here, and give a chance to reward everyone for the help.
aMachi said:
Ok, so maybe now i need some help.
I run adb in my pc then i type adb shell to run the remote shell interactively.
Then what i need to type?
Anyway if i type "ls -l /system/framework > framework.txt" the response is "No such file or directory"
Sorry for my n00b questions. Really hope to learn something here, and give a chance to reward everyone for the help.
Click to expand...
Click to collapse
The commands were supposed to be typed as is on your computer. However I think I missed to quote the "echo $BOOTCLASSPATH" - I want the bootclasspath of your device, not of your PC.
Anyway, if you type "adb shell" first and then "ls -l /system/framework" and you get back "No such file or directory" that's strange...
_that said:
The commands were supposed to be typed as is on your computer. However I think I missed to quote the "echo $BOOTCLASSPATH" - I want the bootclasspath of your device, not of your PC.
Anyway, if you type "adb shell" first and then "ls -l /system/framework" and you get back "No such file or directory" that's strange...
Click to expand...
Click to collapse
Ok so tomorrow i'll give you the result of this test. I hope that i learn how to right use this command.
Any other thing that i can do?
aMachi said:
Ok so tomorrow i'll give you the result of this test. I hope that i learn how to right use this command.
Any other thing that i can do?
Click to expand...
Click to collapse
Post screenshots of your cmd window so that they can see the actual input/output
berndblb said:
Post screenshots of your cmd window so that they can see the actual input/output
Click to expand...
Click to collapse
No need for a graphical screenshot - you can copy the text from the console window.

No LTE with Sprint

I have an HTC One M8, and I installed Cyanogenmod 12.1 (I followed their guide and did HTCdev Unlock). For a little while, LTE was working fine with my phone, but then about a couple of weeks ago, my LTE connection stopped working, and it hasn't worked since. So ultimately that's the problem I'm looking to solve.
I had backed up my HTC factory ROM and restored that to see if LTE would work there. That's when I found that it wants me to do an update, but the update reboots me into TWRP and doesn't work. My thought is that to solve this, I will need to apply the update somehow, and if that's the case, then I could use some help figuring out how to do that. (I'm trying to run "Update Profile".)
If you have other ideas of what I can do to fix LTE, then I'm open to hearing them as well.
Thanks!
You need to install stock recovery to enable the update to install.
Thanks for the response. I'm trying to work out from your signature links (thanks for those!) how to do that.
I found the link to the Stock Recoveries. In there, I found a bunch of different versions. The version numbers seemed to match my version-main: 2.16.651.4, so I should use Stock_2.16.651.4_recovery.img, correct?
And I'm back on CM now, so should I restore the stock before doing this? It seems so, since I don't know if the other recovery will be able to restore it.
So I will:
1) restore the stock ROM
2) flash the stock recovery
3) boot up and do the system update
4) update Profile and PRF (I'm hoping this fixes the LTE issue)
5) put TWRP back on
6) restore CM
Does this sound right? And to put TWRP back on, do I just do the same fastboot flash recovery command, but with the TWRP file?
Thanks so much for the help!
komi_9 said:
Thanks for the response. I'm trying to work out from your signature links (thanks for those!) how to do that.
I found the link to the Stock Recoveries. In there, I found a bunch of different versions. The version numbers seemed to match my version-main: 2.16.651.4, so I should use Stock_2.16.651.4_recovery.img, correct?
And I'm back on CM now, so should I restore the stock before doing this? It seems so, since I don't know if the other recovery will be able to restore it.
So I will:
1) restore the stock ROM
2) flash the stock recovery
3) boot up and do the system update
4) update Profile and PRF (I'm hoping this fixes the LTE issue)
5) put TWRP back on
6) restore CM
Does this sound right? And to put TWRP back on, do I just do the same fastboot flash recovery command, but with the TWRP file?
Thanks so much for the help!
Click to expand...
Click to collapse
Yup sounds correct except being you are on 2.16 there will be a few updates you will need to do to get current.
I went through the process, and each step went fine (you were right about having to update a few times), but LTE is still not working in CM when I switched back over. It is working on the Stock ROM side of things; that's how I did my OTA update. (At least it says LTE in the status bar, so I assume that's what it's using, as opposed to just defaulting to LTE but switching to 3G when LTE is not present.)
Any other suggestions that I should try? Could this be a Cyanogenmod issue? Should I ask in their forums?
And another question if I need to go through this again in the future. The stock software is now 4.(something). This doesn't match any of the Stock recovery version numbers in that zip file. Do I need to go locate the proper recovery, or can I use the latest (3.30.651.2)? (And what does the HK suffix on some of the recoveries mean?)
Thanks for the help again!
Any other suggestions that I should try? Could this be a Cyanogenmod issue? Should I ask in their forums?
Click to expand...
Click to collapse
I don't use CM so can't answer but yeah your best bet would be to ask in their forum.
And another question if I need to go through this again in the future. The stock software is now 4.(something). This doesn't match any of the Stock recovery version numbers in that zip file. Do I need to go locate the proper recovery, or can I use the latest (3.30.651.2)? (And what does the HK suffix on some of the recoveries mean?)
Click to expand...
Click to collapse
If you took all the update to make you current you should have the latest stock recovery. You can always pull the stock recovery from the latest Full Firmware zip.
HK = Harmon Kardon Edition
Do you use a custom ROM? Or do you have a suggestion of a different one? I'd like to experiment with something else to see if this is specific to CM.
komi_9 said:
Do you use a custom ROM? Or do you have a suggestion of a different one? I'd like to experiment with something else to see if this is specific to CM.
Click to expand...
Click to collapse
I use LeeDroid...never had any issues with it.
http://forum.xda-developers.com/htc-one-m8/development/rom-leedroid-one-m8-l-v1-0-5-t3019102
Sloth said:
I use LeeDroid...never had any issues with it.
http://forum.xda-developers.com/htc-one-m8/development/rom-leedroid-one-m8-l-v1-0-5-t3019102
Click to expand...
Click to collapse
I tried installing that, but I get an installer status 7 error. When I boot the phone up, it just takes me back into recovery. I'm not sure what's going on there.
komi_9 said:
I tried installing that, but I get an installer status 7 error. When I boot the phone up, it just takes me back into recovery. I'm not sure what's going on there.
Click to expand...
Click to collapse
Have you updated your twrp recently?
I have 2.8.7.0 downloaded from here: https://dl.twrp.me/m8/twrp-2.8.7.0-m8.img
I just remembered that I didn't do a full wipe. Could this be the problem? I was scared that it would wipe my personal data. If I've done a backup to an SD card, can I restore that and get back to my original set up with a full wipe?
komi_9 said:
I just remembered that I didn't do a full wipe. Could this be the problem? I was scared that it would wipe my personal data. If I've done a backup to an SD card, can I restore that and get back to my original set up with a full wipe?
Click to expand...
Click to collapse
Yes that might be the problem. A full wipe shouldn't wipe anything important.
If you have a backup and you need to use it you will be back to the ROM you made the backup of.
Sent from a Glade Plugin.
It still didn't work. I tried some of the steps advised here: http://forum.xda-developers.com/showthread.php?t=2728644
I did a factory reset from TWRP, then I specifically wiped the system folder, then I did a full wipe withing the Leedroid installer. Also, I put the Leedroid zip file in internal storage instead of my SD card. But regardless I get the same error. Here's my log file:
Code:
AROMA Installer version 2.70RC2
(c) 2013 by amarullz xda-developers
ROM Name : LeeDrOiD One M8 S7
ROM Version : V7.4.2
ROM Author : LeeDrOiD
Device : HTC One M8
Start at : Wed Oct 28 12:11:04 2015
I:emmc_scan_partitions:[partition_count:47] [allocat_num:128]
bad option "flags=display="Cache""
skipping malformed recovery.fstab line: /cache ext4 /dev/block/platform/msm_sdcc.1/by-name/cache flags=display="Cache"
bad option "flags=display="System""
skipping malformed recovery.fstab line: /system ext4 /dev/block/platform/msm_sdcc.1/by-name/system flags=display="System"
bad option "flags=encryptable=/dev/block/platform/msm_sdcc.1/by-name/extra"
skipping malformed recovery.fstab line: /data ext4 /dev/block/platform/msm_sdcc.1/by-name/userdata flags=encryptable=/dev/block/platform/msm_sdcc.1/by-name/extra
bad option "flags=display="Recovery""
skipping malformed recovery.fstab line: /recovery emmc /dev/block/platform/msm_sdcc.1/by-name/recovery flags=display="Recovery"
bad option "flags=display="Micro"
skipping malformed recovery.fstab line: /external_sd vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1 flags=display="Micro SDcard";storage;wipeingui;removable;andsec
bad option "flags=display="USB-OTG";storage;wipeingui;removable"
skipping malformed recovery.fstab line: /usb_otg vfat /dev/block/sda1 /dev/block/sda flags=display="USB-OTG";storage;wipeingui;removable
bad option "flags=display="SD-Ext";wipeingui;removable"
skipping malformed recovery.fstab line: /sd-ext ext4 /dev/block/mmcblk1p2 flags=display="SD-Ext";wipeingui;removable
recovery filesystem table in updater...
=========================
0 /tmp ramdisk (null) (null) 0
1 /misc emmc /dev/block/platform/msm_sdcc.1/by-name/misc (null) 0
2 /boot emmc /dev/block/platform/msm_sdcc.1/by-name/boot (null) 0
3 /devlog ext4 /dev/block/platform/msm_sdcc.1/by-name/devlog (null) 0
Now Flashing LeeDrOiD to your HTC One M8
Please be patient
1st boot may take a few minutes
about to run program [/sbin/mount] with 2 args
mount: mounting /dev/block/mmcblk0p47 on /data failed: Device or resource busy
run_program: child exited with status 255
about to run program [/sbin/mount] with 2 args
Extract scripts and tools
Wiping Data without /media
about to run program [/tmp/wipe.sh] with 1 args
Writing Data
about to run program [/tmp/fbrem.sh] with 1 args
chattr: stat /data/data/com.facebook.katana/databases/qe_db: No such file or directory
Writing System
about to run program [/sbin/mke2fs] with 6 args
mke2fs 1.42.9 (28-Dec-2013)
Discarding device blocks: 4096/688128528384/688128 done
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=0 blocks, Stripe width=0 blocks
172032 inodes, 688128 blocks
0 blocks (0.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=704643072
21 block groups
32768 blocks per group, 32768 fragments per group
8192 inodes per group
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912
Allocating group tables: 0/21 done
Writing inode tables: 0/21 done
Creating journal (16384 blocks): done
Writing superblocks and filesystem accounting information: 0/21 done
about to run program [/sbin/mount] with 2 args
Installing Hacked Linker
Carrier Selection
Sprint
Customising HTC Apps
Installing HTC Car & HTC Speak
Customising Widgets
Customising Google and Other Apps
Installing Google CloudPrint
Installing Google Drive
Installing Google Search
Installing Adaway
Installing Es File Explorer
Installing Facebook
Removing Kid Mode
Extras
Disabling Exchange Mail Security
about to run program [/tmp/tweaks.sh] with 4 args
ERROR: DataBase /data/data/com.android.providers.settings/databases/settings.db not found!
Applying Big Caller Photo
about to run program [/tmp/res_patch.sh] with 2 args
Processing /system/priv-app/Telephony/Telephony.apk
updating: resources.arsc (deflated 74%)
Zipaligning /system/priv-app/Telephony/Telephony.apk
Shrinking Nav Bar To 42 DPI
about to run program [/tmp/res_patch.sh] with 2 args
Processing /system/framework/framework-res.apk
updating: resources.arsc (deflated 77%)
Zipaligning /system/framework/framework-res.apk
about to run program [/tmp/res_patch.sh] with 2 args
Processing /system/priv-app/HtcContactsDialer/HtcContactsDialer.apk
updating: resources.arsc (deflated 79%)
Zipaligning /system/priv-app/HtcContactsDialer/HtcContactsDialer.apk
Creating toolbox symlinks
Installing busybox
set_perm: chown of /system/xbin/busybox to 0 1000 failed: No such file or directory
set_perm: chmod of /system/xbin/busybox to 755 failed: No such file or directory
script aborted: set_perm: some changes failed
set_perm: some changes failed
Installer Error (Status 7)
End at : Wed Oct 28 12:12:56 2015
komi_9 said:
It still didn't work. I tried some of the steps advised here: http://forum.xda-developers.com/showthread.php?t=2728644
I did a factory reset from TWRP, then I specifically wiped the system folder, then I did a full wipe withing the Leedroid installer. Also, I put the Leedroid zip file in internal storage instead of my SD card. But regardless I get the same error. Here's my log file:
Code:
AROMA Installer version 2.70RC2
(c) 2013 by amarullz xda-developers
ROM Name : LeeDrOiD One M8 S7
ROM Version : V7.4.2
ROM Author : LeeDrOiD
Device : HTC One M8
Start at : Wed Oct 28 12:11:04 2015
I:emmc_scan_partitions:[partition_count:47] [allocat_num:128]
bad option "flags=display="Cache""
skipping malformed recovery.fstab line: /cache ext4 /dev/block/platform/msm_sdcc.1/by-name/cache flags=display="Cache"
bad option "flags=display="System""
skipping malformed recovery.fstab line: /system ext4 /dev/block/platform/msm_sdcc.1/by-name/system flags=display="System"
bad option "flags=encryptable=/dev/block/platform/msm_sdcc.1/by-name/extra"
skipping malformed recovery.fstab line: /data ext4 /dev/block/platform/msm_sdcc.1/by-name/userdata flags=encryptable=/dev/block/platform/msm_sdcc.1/by-name/extra
bad option "flags=display="Recovery""
skipping malformed recovery.fstab line: /recovery emmc /dev/block/platform/msm_sdcc.1/by-name/recovery flags=display="Recovery"
bad option "flags=display="Micro"
skipping malformed recovery.fstab line: /external_sd vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1 flags=display="Micro SDcard";storage;wipeingui;removable;andsec
bad option "flags=display="USB-OTG";storage;wipeingui;removable"
skipping malformed recovery.fstab line: /usb_otg vfat /dev/block/sda1 /dev/block/sda flags=display="USB-OTG";storage;wipeingui;removable
bad option "flags=display="SD-Ext";wipeingui;removable"
skipping malformed recovery.fstab line: /sd-ext ext4 /dev/block/mmcblk1p2 flags=display="SD-Ext";wipeingui;removable
recovery filesystem table in updater...
=========================
0 /tmp ramdisk (null) (null) 0
1 /misc emmc /dev/block/platform/msm_sdcc.1/by-name/misc (null) 0
2 /boot emmc /dev/block/platform/msm_sdcc.1/by-name/boot (null) 0
3 /devlog ext4 /dev/block/platform/msm_sdcc.1/by-name/devlog (null) 0
Now Flashing LeeDrOiD to your HTC One M8
Please be patient
1st boot may take a few minutes
about to run program [/sbin/mount] with 2 args
mount: mounting /dev/block/mmcblk0p47 on /data failed: Device or resource busy
run_program: child exited with status 255
about to run program [/sbin/mount] with 2 args
Extract scripts and tools
Wiping Data without /media
about to run program [/tmp/wipe.sh] with 1 args
Writing Data
about to run program [/tmp/fbrem.sh] with 1 args
chattr: stat /data/data/com.facebook.katana/databases/qe_db: No such file or directory
Writing System
about to run program [/sbin/mke2fs] with 6 args
mke2fs 1.42.9 (28-Dec-2013)
Discarding device blocks: 4096/688128528384/688128 done
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=0 blocks, Stripe width=0 blocks
172032 inodes, 688128 blocks
0 blocks (0.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=704643072
21 block groups
32768 blocks per group, 32768 fragments per group
8192 inodes per group
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912
Allocating group tables: 0/21 done
Writing inode tables: 0/21 done
Creating journal (16384 blocks): done
Writing superblocks and filesystem accounting information: 0/21 done
about to run program [/sbin/mount] with 2 args
Installing Hacked Linker
Carrier Selection
Sprint
Customising HTC Apps
Installing HTC Car & HTC Speak
Customising Widgets
Customising Google and Other Apps
Installing Google CloudPrint
Installing Google Drive
Installing Google Search
Installing Adaway
Installing Es File Explorer
Installing Facebook
Removing Kid Mode
Extras
Disabling Exchange Mail Security
about to run program [/tmp/tweaks.sh] with 4 args
ERROR: DataBase /data/data/com.android.providers.settings/databases/settings.db not found!
Applying Big Caller Photo
about to run program [/tmp/res_patch.sh] with 2 args
Processing /system/priv-app/Telephony/Telephony.apk
updating: resources.arsc (deflated 74%)
Zipaligning /system/priv-app/Telephony/Telephony.apk
Shrinking Nav Bar To 42 DPI
about to run program [/tmp/res_patch.sh] with 2 args
Processing /system/framework/framework-res.apk
updating: resources.arsc (deflated 77%)
Zipaligning /system/framework/framework-res.apk
about to run program [/tmp/res_patch.sh] with 2 args
Processing /system/priv-app/HtcContactsDialer/HtcContactsDialer.apk
updating: resources.arsc (deflated 79%)
Zipaligning /system/priv-app/HtcContactsDialer/HtcContactsDialer.apk
Creating toolbox symlinks
Installing busybox
set_perm: chown of /system/xbin/busybox to 0 1000 failed: No such file or directory
set_perm: chmod of /system/xbin/busybox to 755 failed: No such file or directory
script aborted: set_perm: some changes failed
set_perm: some changes failed
Installer Error (Status 7)
End at : Wed Oct 28 12:12:56 2015
Click to expand...
Click to collapse
V7.4.2 is not the latest version...try the latest and see if it makes a difference. Usually status 7 error means the updater script is out of date (if I remember correctly).
When I do a full wipe I choose Advance Wipe then check the boxes next to cache/dal cache/data/system. From my experience wiping in twrp and then wiping again in Aroma usually causes problems. I prefer the twrp method myself.
I also put anything I'm going to flash on the EXT sdcard.
The 7.4.3 version is only available as a patch to 7.4.2 as far as I can tell. The full download is only available in 7.4.2. Or at least that's all I see.
Anyway, the point is moot now since I seem to have gotten LTE working. I went into APN settings and the option CDMA 0 was selected. Any of the other options pop me over to the Sprint LTE Internet option, but that one will just sit there and not work. I'm not quite sure how I got stuck on that APN. But oh well, since it's working now.
I really appreciate all the help! One day I might embark on trying out different ROMs again, but for now I'm happy that CM is working out OK.
Cool glad you got it sorted.

[SOLVED] *******PLEASE HELP ME!!!!!!!!!! - seems like i've got a permanent soft brick

Hello everybody im wondering if someone can help me
im trying to reinstall a rom to my HTC One m7
But everytime i try to use fastboot or RUU exe to unbrick it i get stuck at the signature verification part.
my phone info is as follows (bootloader):
*** TAMPERED ***
*** RELOCKED ***
*** Security Warning ***
M7_UL PVT SHIP S-ON RH
HBOOT-1.44.0000
RADIO-4A.13.3231.27
OpenDSP-v26.120.274.0202
eMMC-boot
Mar 7 2013,23:09:00-1
IF I TYPE IN FASTBOOT: fastboot getver version-main I receive: 1.28.61.7
My CID: ORANG001
TWRP recovery version: 2.8.7.0
I am able to unlock and relock at my own will using fastboot to relock and using HTC-Dev toekn .bin file to unlock via fastboot.
I am able install both TWRP and CWM recoveries... but when I enter recovery with (unlocked device) neither can mount the sdcard so i can copy a rom to the phone to install.
I am abdle to use adb to copy files to my internal storage but am not able to use the abd sideload as the TWRP recovery cannot seem to mount the sdcar or system or data
The phone is completely wiped and I dont know what else to do. I understand that if i was able to gain S-OFF then the signature verification would pass but is there a way to do this when I cant do anything but get into my bootloader and recovery?
Maybe its down to the RUU exe and zip files im using i dont know??? but it seems very hard to find a link to one that is for my phone.
any help would be very appreciated and links also please
HELP ME
SOLUTION
Quote:
Originally Posted by nkk71
Hey @basv81, I'm leaving this for you cause I'm probably not going to be online tonight:
I don't think you will be able to do this. TWRP and CWM, although they say "format", what it actually does is only wipe the contents of the partition. Since TWRP is unable to mount it, means it's really corrupt. not only /data/media (internal storage), but the whole /data partition.
If you read through this post: http://android-revolution-hd.blogspo...a-htc-one.html
You can clearly see it pretty much applies to your case: "E:Unable to mount '/data'" and e2fsck reporting error.
I would follow the repair instructions from that article, basically (while in recovery):
download this: http://goo.gl/pmZ9Mt, then
adb push mkfs.ext4 /tmp
adb shell
chmod 777 /tmp/mkfs.ext4
/tmp/mkfs.ext4 -b 4096 -O ^huge_file,^dir_nlink,^ext_attr,^resize_inode,^ext ra_isize -m 0 /dev/block/mmcblk0p37
that last command is quite long and not the easiest , so I recommend you type is in very slowly, and be particularly careful with extra or missing spaces, check the link above to make sure it's correct. (it didn't work for the other guy I mentioned cause I told him to copy/paste it, but that introduced an extra space which we both overlooked; so we had to solve it using e2fsck, which in your case is not able to fix the filesystem ).
Once formatting is complete, you need to recreate the /data/media folder, so while still in the adb shell:
mount /data
mkdir -p /data/media/0
then you can use adb push or sideload to get your phone working.
Good luck, and post back with hopefully positive results
Checked if my device was connected properly:
Code:
C:\Repair_HTC_One_m7ul>adb devices
adb server is out of date. killing...
* daemon started successfully *
List of devices attached
H*********** recovery
As that was the case I continued. First I read the topic nkk71 suggested: http://android-revolution-hd.blogspo...a-htc-one.html
First of all I pushed the downloaded mkfs.ext4 file to my device:
Code:
C:\Repair_HTC_One_m7ul>adb push mkfs.ext4 /tmp
3255 KB/s (3537143 bytes in 1.061s)
After that, I changed the file's permissions and executed it with the long command:
Code:
C:\Repair_HTC_One_m7ul>adb shell
~ # ←[6nchmod 777 /tmp/mkfs.ext4
chmod 777 /tmp/mkfs.ext4
~ # ←[6n/tmp/mkfs.ext4 -b 4096 -O ^huge_file,^dir_nlink,^ext_attr,^resize_inode,^extra_isize -m 0 /dev/block/mmcblk0p37
/tmp/mkfs.ext4 -b 4096 -O ^huge_file,^dir_nlink,^ext_attr,^resize_inode,^extra_isize -m 0 /dev/block/mmcblk0p37
mke2fs 1.41.12 (17-May-2010)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=0 blocks, Stripe width=0 blocks
1703936 inodes, 6815744 blocks
0 blocks (0.00%) reserved for the super user
First data block=0
208 block groups
32768 blocks per group, 32768 fragments per group
8192 inodes per group
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000
Writing inode tables: done
Creating journal (32768 blocks): done
Writing superblocks and filesystem accounting information: done
This filesystem will be automatically checked every 24 mounts or
180 days, whichever comes first. Use tune2fs -c or -i to override.
I mounted the /data folder and made directory /data/media/0. After that I quitted the shell.
Code:
~ # ←[6nmount /data
mount /data
~ # ←[6nmkdir -p /data/media/0
mkdir -p /data/media/0
~ # ←[6nexit
exit
I pushed the latest stable Cyanogenmod ROM to my device, including the corresponding Google Apps (so my android keyboard keeps working when I install it):
Code:
C:\Repair_HTC_One_m7ul>adb push cm-10.1.3-m7ul.zip /data/media/0
3284 KB/s (187979506 bytes in 55.886s)
C:\Repair_HTC_One_m7ul>adb push gapps-jb-20130812-signed.zip /data/media/0
3516 KB/s (100751136 bytes in 27.981s)
In twrp:
install
navigated to CM10.1.3 zip-file
installed CM10.1.3 zip-file
Rebooted to bootloader, so I can flash the boot.img again (AFTER installing CM)
Code:
C:\Repair_HTC_One_m7ul>fastboot flash boot boot.img
sending 'boot' (5558 KB)...
OKAY [ 0.993s]
writing 'boot'...
OKAY [ 0.514s]
finished. total time: 1.510s
Rebooted system to see if CM10.1.3 would start for first run. It did, YAY, so I rebooted to recovery again to install Google apps.
Entered recovery (twrp):
install
navigated to gapps zip-file
installed gapps zip-file
wiped cache/dalvik
Many, many thanks to @nkk71 for all support you've given. Without you I'd still be hopelessy stuck!
i rule123 said:
Many, many thanks to @nkk71 for all support you've given. Without you I'd still be hopelessy stuck!
Click to expand...
Click to collapse
glad you got it sorted, for future reference or anybody else that happens to check here, the "manual" formatting method is not really necessary, you can do it in TWRP
TWRP -> Wipe -> Format data -> type 'yes' (this will do a real format of your entire data partition)
I've mentioned it in the FAQ Sticky in particular on page 3
But happy everything worked out for you :good::good:
The links are dead. Could someone please update? I'm having the same issue and would like to use this solution.

flash recovery partition from android system/userland

I'm having trouble with fastboot (see my thread here: https://forum.xda-developers.com/xperia-xz1-compact/help/issues-fastboot-t3971227, maybe you can help). However, I can seem to flash sony signed software in sony-service mode using newflasher. That's nice, but I haven't used stock android in years. I am very used to lineageos without gapps---nice and clean. So, for me, until I get rid of stock and get a clean flash of lineage, I'm really not happy.
Given my state of affairs, I'm wondering about flashing one of the exploitable sony stocks and to get root, then flashing the recovery partition with twrp from userland. Then, potentially, i could boot to that recovery and maybe (idk) flash a new system ROM. Does anyone have any tips or suggestions?
It should work as you outlined.
Still having BL unlocked and not usable fastboot seems like a major disadvantage to me.
Did you try with different PC to see if it is not due to usb chipset or something?
Preferably using usb 2.0 only chipset?
Maybe trying that from different OSes too - linux vs win?
Thanks for the reply. I got the exploitable firmware downloaded and flashed as well as your renosploit kit. Hasn't found a root shell yet although I'm hopeful it will eventually (I haven't read the details but I understand that the underlying vuln is a race condition).
One question: I suppose that given that tmp root status, it should be possible to copy a su binary over and make root permanent, that would make experimentation easier, I think. And if whatever I try fails the first time I wouldn't want to have to wait for the race condition exploit every time I wanted to reboot. Am I on the right track? If so, I suppose I need to either compile or download a su binary and possibly a supersu.apk in order to manage it. Are those already available for the xz1 compact?
@apexofservice, planting su binary is possible into /oem for example, it would switch the user to root, but without any better permissions, due to selinux, so it is useless.
But since you have your BL unlocked, you do not need that. As soon as you have twrp, you can flash magisk to have root on runtime easily. Or just enter twrp to have root in recovery.
j4nn said:
@apexofservice, planting su binary is possible into /oem for example, it would switch the user to root, but without any better permissions, due to selinux, so it is useless.
But since you have your BL unlocked, you do not need that. As soon as you have twrp, you can flash magisk to have root on runtime easily. Or just enter twrp to have root in recovery.
Click to expand...
Click to collapse
Got it. Thank you for this detail. So you think my best bet is to just use the root shell to `dd` the twrp image directly to some /dev? And then I would just `adb reboot recovery` and in theory I'm good to go.
Cool. I got a root shell with your exploit kit. I've got two questions at this point.
1) If my bootloader unlock had fully succeeded, would I have expected to find all 0x0 in the TA partition? In fact, there is data in there, so I went ahead and downloaded it. I skimmed the data with xxd and there are some sections of 0x0 as well though.
2) Second question, I've read that xperia's don't have a proper "recovery" partition the way some other boards do. So is FOTAkernel actually where I want to write twrp.img? Also, it would seem that this info is actually encoded somewhere in the fastboot client since on a working fastboot, you can just say "flash recovery" and it knows what part of the disk to write to. Any info about partition layouts on lilac and xperia's in general would be greatly appreciated.
apexofservice said:
Cool. I got a root shell with your exploit kit. I've got two questions at this point.
1) If my bootloader unlock had fully succeeded, would I have expected to find all 0x0 in the TA partition? In fact, there is data in there, so I went ahead and downloaded it. I skimmed the data with xxd and there are some sections of 0x0 as well though.
2) Second question, I've read that xperia's don't have a proper "recovery" partition the way some other boards do. So is FOTAkernel actually where I want to write twrp.img? Also, it would seem that this info is actually encoded somewhere in the fastboot client since on a working fastboot, you can just say "flash recovery" and it knows what part of the disk to write to. Any info about partition layouts on lilac and xperia's in general would be greatly appreciated.
Click to expand...
Click to collapse
1 - The TA partition contains significant amounts of other information as well. So it won't be empty.
The standard way of dealing with it is to not mess with it at all.
2 - The FOTAkernel is the recovery.
2a - The partition layout can be found from the stock firmware image in the "partition-image-LUNZ_X-FLASH-ALL-C93B.sin" file where "Z" is the LUN number. Once you extract the SIN file, you're left with an EFI partition header.
I've attached a CSV file that contains the layout as specified in the "partition-image-LUN0_X-FLASH-ALL-C93B.sin" file.
The layout for LUNs 1 and 2 both contain a single 4MB partition for "xbl" and "xblbak" respectively, so they're not as interesting.
@pbarrette, thanks! I tried the naive approach:
Code:
d if=twrp-3.2.1-0-lilac-10-patchlevel-2018-05-05.img of=/dev/block/bootdevice/by-name/FOTAKernel <
60128+0 records in
60128+0 records out
30785536 bytes transferred in 2.100 secs (14659779 bytes/sec)
G8441:/data/local/tmp # sync
G8441:/data/local/tmp # sync
G8441:/data/local/tmp # reboot recovery
Alas, it just rebooted back to system. It did seem to take a bit longer, so it's possible that it tried to boot from FOTAKernel and failed then fell back to system. I've just got a new root shell so I can look in startup logs from dmesg to see if there's anything of interest.
Also, I'm probably missing something really obvious. Thanks for any insight!
Reading dmesg now, this seems quite relevant (I recall booting to recovery on my z3 compact by touching a file in /cache/recovery). I'll post it here but I'm still reading the dmesg.
Code:
[ 7.406109] bs_roots: recovery filesystem table
[ 7.406120] bs_roots: =========================
[ 7.406125] bs_roots: 0 /data ext4 /dev/block/bootdevice/by-name/userdata
[ 7.406130] bs_roots: 1 /oem ext4 /dev/block/bootdevice/by-name/oem
[ 7.406134] bs_roots: 2 /cache ext4 /dev/block/bootdevice/by-name/cache
[ 7.406139] bs_roots: 3 /rca ext4 /dev/block/bootdevice/by-name/appslog
[ 7.406143] bs_roots: 4 /idd ext4 /dev/block/bootdevice/by-name/diag
[ 7.406148] bs_roots: 5 /storage/sdcard1 vfat /devices/soc/c0a4900.sdhci/mmc_host*
[ 7.406153] bs_roots: 6 none swap /dev/block/zram0
[ 7.406157] bs_roots: 7 /persistent emmc /dev/block/bootdevice/by-name/frp
[ 7.406162] bs_roots: 8 /misc emmc /dev/block/bootdevice/by-name/misc
[ 7.406167] bs_roots: 9 /firmware vfat /dev/block/bootdevice/by-name/modem
[ 7.406172] bs_roots: 10 /bt_firmware vfat /dev/block/bootdevice/by-name/bluetooth
[ 7.406177] bs_roots: 11 /dsp ext4 /dev/block/bootdevice/by-name/dsp
[ 7.406182] bs_roots: 12 /persist ext4 /dev/block/bootdevice/by-name/persist
[ 7.406187] bs_roots: 13 /boot/modem_fs1 emmc /dev/block/bootdevice/by-name/modemst1
[ 7.406191] bs_roots: 14 /boot/modem_fs2 emmc /dev/block/bootdevice/by-name/modemst2
[ 7.406195] bs_roots: 15 auto auto /devices/soc/a800000.ssusb/a800000.dwc3/xhci-hcd.0.auto/usb*
[ 7.406199] bs_roots: 16 /qns ext4 /dev/block/bootdevice/by-name/Qnovo
[ 7.406203] bs_roots: 17 /tmp ramdisk ramdisk
[ 7.406206] bs_roots:
[ 7.408585] MR: Mounting /cache ourselves
[ 7.412318] EXT4-fs (sda53): recovery complete
[ 7.412666] EXT4-fs (sda53): mounted filesystem with ordered data mode. Opts:
[ 7.413213] MR: fopen() failed -/cache/recovery/command (No such file or directory)
[ 7.413219] MR: Unmounting /cache
[ 7.413959] MR: Fail to get command from /cache/recovery/command, trying /misc
[ 7.414272] MR: Unknown wipe command
[ 7.414280] MR: Buffer is empty from /dev/block/bootdevice/by-name/misc with command 0
[ 7.417568] MR: TA_MASTER_RESET value = 0
[ 7.418475] init: Service 'exec 3 (/sbin/mr)' (pid 605) exited with status 0 waiting took 0.022997 se
conds
[ 7.418513] init: starting service 'exec 4 (/sbin/ffu)'...
[ 7.418846] init: SVC_EXEC pid 609 (uid 0 gid 0+0 context u:r:recovery:s0) started; waiting...
[ 7.419833] init: Service 'exec 4 (/sbin/ffu)' (pid 609) exited with status 255 waiting took 0.001316
seconds
------
One more update, I did a sanity check that that dd command is actually overwriting FOTAkernel. It doesn't look like it's working:
Code:
G8441:/data/local/tmp # dd if=/dev/block/bootdevice/by-name/FOTAKernel of=FOTAKernel-extracted.img
131072+0 records in
131072+0 records out
67108864 bytes transferred in 0.812 secs (82646384 bytes/sec)
G8441:/data/local/tmp # chown shell:shell FOTAKernel-extracted.img
G8441:/data/local/tmp # dd if=twrp-3.2.1-0-lilac-10-patchlevel-2018-05-05.img of=/dev/block/bootdevice/by-name/FOTAKernel
60128+0 records in
60128+0 records out
30785536 bytes transferred in 2.037 secs (15113174 bytes/sec)
G8441:/data/local/tmp # sync
G8441:/data/local/tmp # sync
=/dev/block/bootdevice/by-name/FOTAKernel of=FOTAKernel-extracted-2.img <
131072+0 records in
131072+0 records out
67108864 bytes transferred in 0.846 secs (79324898 bytes/sec)
And there's no `diff` on the device, so I pulled the files back to a laptop then:
Code:
$ diff FOTAKernel-extracted-2.img FOTAKernel-extracted.img
$ diff FOTAKernel-extracted.img twrp-3.2.1-0-lilac-10-patchlevel-2018-05-05.img
Binary files FOTAKernel-extracted.img and twrp-3.2.1-0-lilac-10-patchlevel-2018-05-05.img differ
@j4nn @pbarrette doing some more reading, I found some interesting details about booting to recovery stored on FOTAKernel here:
https://twrp.me/sony/sonyxperiaxz.html
https://twrp.me/sony/sonyxperiaz3compact.html
Looks like you really need a kernel that has the ramdisk extraction setup. So I'm guessing that once I figure out why dd isn''t working as I expected (see above) that I need to overwrite the main stock kernel with an alternative.
Yes, a dd extraction of the partition will be different than the TWRP image.
That's because the TWRP image is only ~35MB, while "dd" is extracting the entire 64MB partition.
So, if you do a visual diff on the files, you should see that what's actually different is the fact that the partition extraction is filled with zeros after the end of the TWRP image.
You're doing a "reboot recovery", but have you tried:
1 - Turn the phone off
2 - Press and hold [Vol-Down].
3 - Press and hold [Power].
4 - Release [Power] at power on.
5 - Release [Vol-Down] when you see an actual boot screen (after the bootloader unlocked screen).
I don't remember the "reboot recovery" command ever working right for me.
Edit to add: That's also a really old version of TWRP that you seem to be using.
pbarrette said:
Yes, a dd extraction of the partition will be different than the TWRP image.
That's because the TWRP image is only ~35MB, while "dd" is extracting the entire 64MB partition.
So, if you do a visual diff on the files, you should see that what's actually different is the fact that the partition extraction is filled with zeros after the end of the TWRP image.
You're doing a "reboot recovery", but have you tried:
1 - Turn the phone off
2 - Press and hold [Vol-Down].
3 - Press and hold [Power].
4 - Release [Power] at power on.
5 - Release [Vol-Down] when you see an actual boot screen (after the bootloader unlocked screen).
I don't remember the "reboot recovery" command ever working right for me.
Edit to add: That's also a really old version of TWRP that you seem to be using.
Click to expand...
Click to collapse
Hot damn. Thanks, I'm booted to twrp!
Note: i was using the older version for android 8 since I'm currently on the android 8 exploitable rom!
apexofservice said:
@j4nn @pbarrette doing some more reading, I found some interesting details about booting to recovery stored on FOTAKernel here:
https://twrp.me/sony/sonyxperiaxz.html
https://twrp.me/sony/sonyxperiaz3compact.html
Looks like you really need a kernel that has the ramdisk extraction setup. So I'm guessing that once I figure out why dd isn''t working as I expected (see above) that I need to overwrite the main stock kernel with an alternative.
Click to expand...
Click to collapse
XZ1 compact never needed the recovery with this extraction stuff. But according to
https://twrp.me/sony/sonyxperiaxzpremium.html
XZ Premium (which is also yoshino platform, the same as xz1c is) seems to need that - but I am not sure if it is still valid.
It might got fixed even in xzp case with some bootloader update to have it working the same as with other yoshino phones.
Sorry for my late answer, it's good you already have it working.
But I still wonder about that usb problem with fastboot - have you tried a different pc with different usb controller, preferably usb 2.0 type (not 3.0 one)?
j4nn said:
XZ1 compact never needed the recovery with this extraction stuff. But according to
https://twrp.me/sony/sonyxperiaxzpremium.html
XZ Premium (which is also yoshino platform, the same as xz1c is) seems to need that - but I am not sure if it is still valid.
It might got fixed even in xzp case with some bootloader update to have it working the same as with other yoshino phones.
Sorry for my late answer, it's good you already have it working.
But I still wonder about that usb problem with fastboot - have you tried a different pc with different usb controller, preferably usb 2.0 type (not 3.0 one)?
Click to expand...
Click to collapse
I haven't yet. Well, I have sorta. When I first ran into issues, I tried it with a different laptop, got the same result. Now that laptop was also a thinkpad (although a newer model) and was also running debian linux. I don't have any computers with Windows. I was going to reboot this laptop with usb3.0 kernel mod blacklisted and only using hci but I didn't get around to it yet (especially once I got twrp flashed and working, then I mainly wanted to get started actually using the phone i bought ). However, if it were a usb thing, wouldn't we expect that newflasher would fail too? Still, it is very curious about the fastboot thing, however, so I'm willing to keep playing with it.
@apexofservice, I am not sure if blacklisting usb3 drivers would help. Sometime there may be present multiple usb ports, some connected to usb 3.0 host controller, others just usb 2.0 controller.
Even if newflasher works, it is not that simple, that fastboot should work too.
Fastboot (including it's usb support) is implemented in UEFI bootloader, the ABL component of it (Android Boot Loader).
So usb stack is implemented by UEFI fw.
While newflasher uses flash mode, which is running XFL - a linux (bare bone android) kernel, running the lilo/loader userspace application. So there is in my opinion quite good usb stack implemented by linux kernel.
So it can easily be some incompatibility within UEFI usb stack implementation used with fastboot.

Categories

Resources