Develop Bugs

[Update] Pre-rooted stock 6.2.1 update (secure and unsecure boot images)

I've put together a rooted version of the stock 6.2.1 update if anyone wants to have at it. I flashed this on my own Fire with TWRP and it boots and runs fine, but I haven't done any other testing. Shouldn't need to wipe /data if you're coming from a 6.2 system, not sure about other ROMs like CM. Of course, I highly recommend you make a backup before flashing (good habit, and all that). To install just put it onto your Fire's /sdcard partition, boot into TWRP and install the zip. Note that TWRP will complain that it can't find the /misc or /sd-ext partitions. This is normal, those partitions don't exist on the Fire, but it won't affect the installation.
I downloaded the stock zip from the link in this post: http://forum.xda-developers.com/showpost.php?p=20509203&postcount=91 and then I changed the following from the stock zip file:
Removed the bootloader and recovery.img updates
Removed the backup_data.zip because it doesn't make sense, really (it looks like it just extracts to /backup/, but if you flash it it will wipe your /data partition?)
Added busybox, Superuser and the su binary. Should be properly symlinked and permissions set correctly.
Modified the updater-script for the above things.
Additionally, if you have the Market installed you may need to re-install it after updating since Amazon didn't do this as a patch - it just formats /system and replaces it. If you updated the Market manually then the newer version should survive in /data/app. Also, if you installed any custom frameworks or libraries (e.g. the maps framework to use Google Currents and whatnot) then you'll need to reinstall those. Basically, anything you added or modified on /system will be gone.
Edit: Thanks sadlius for pointing me to dsixda's kitchen! I've added a version with an unsecure boot image (so you get root by default on a shell). I'll leave the old one in case anyone would prefer the secure boot image. I've also uploaded the boot image itself for anyone who might have already flashed the secure 6.2.1 zip. I tried it with fastboot and it booted up fine, so you can test it first with:
Code:
fastboot boot 6_2_1rootboot.img
If it works, you can flash it (permanently overwrites your current boot partition) with:
Code:
fastboot flash boot 6_2_1rootboot.img
Downloads
MOD EDIT: Links no longer valid so removed.
Multiupload, courtesy sadlius:
update-6.2.1-rooted-secureboot.zip
Stock rooted update 6.2.1, secure boot image
update-6.2.1-rooted-unsecureboot.zip
Stock rooted update 6.2.1, unsecure boot image
Multiupload, courtesy intel352 (md5's should be the same):
update-6.2.1-rooted-secureboot.zip
Multiupload:
6_2_1rootboot.img Unsecure 6.2.1 boot image
Original Downloads:
Removed these so Dropbox won't yell at me anymore ​

First attempt at installing I get:
E:Cannot load volume /misc!
E:Cannot load volume /misc!
E:Unable to stat '/sd-ext/.'
E:Cannot load volume /misc!
E:Unable to open zip file.
But I think I know what the problem is. Will attempt again in a few minutes. Or as soon as TWRP relinquished control of my KF back to me.

You sir are a good Man....

sadalius said:
First attempt at installing I get:
E:Cannot load volume /misc!
E:Cannot load volume /misc!
E:Unable to stat '/sd-ext/.'
E:Cannot load volume /misc!
E:Unable to open zip file.
But I think I know what the problem is. Will attempt again in a few minutes. Or as soon as TWRP relinquished control of my KF back to me.
Click to expand...
Click to collapse
I got the "Cannot load volume /misc!" error, too, but it seems to be okay anyway. The KF simply doesn't have a /misc partition.
Curious that it can't open the zip, though, but I'll wait until after your second attempt to try troubleshooting.

sadalius said:
First attempt at installing I get:
E:Cannot load volume /misc!
E:Cannot load volume /misc!
E:Unable to stat '/sd-ext/.'
E:Cannot load volume /misc!
Click to expand...
Click to collapse
I have seen the same errors when I installed TWRP. It didn't seem to make a difference to it loading.
All but the last line.
E:Unable to open zip file.
Click to expand...
Click to collapse
I think that is the real error.

I got it figured out. Somehow, the file was corrupted when I transferred it to the KF. Deleted it and re-transferred, it took it that time. Will report any positives or negatives once I get back to the actual OS and play around with it.
Thanks a bunch!!
---------- Post added at 02:28 PM ---------- Previous post was at 02:20 PM ----------
Yes. Everything I've tried so far works great!!
I do have one question though. I used to cook my own roms from OEM releases back when I had an HTC hero. May I ask what you used to root this with?

isn't 6.2 is latest ? where did 6.2.1 came from?

HI,
is there someway for me to flash this using fastboot? Because im stuck in fastboot and can't get out of it!

sadalius said:
I got it figured out. Somehow, the file was corrupted when I transferred it to the KF. Deleted it and re-transferred, it took it that time. Will report any positives or negatives once I get back to the actual OS and play around with it.
Thanks a bunch!!
---------- Post added at 02:28 PM ---------- Previous post was at 02:20 PM ----------
Yes. Everything I've tried so far works great!!
I do have one question though. I used to cook my own roms from OEM releases back when I had an HTC hero. May I ask what you used to root this with?
Click to expand...
Click to collapse
I do it manually. The update had a .bin extension but it was really a .zip, so I renamed it, extracted it, and made the modifications I wanted (like adding su/Superuser). Then I just re-zipped it.
Don't know if it's the most "efficient" way to do it, but it's straightforward enough and it's how I've always done it...

Wonder if dsixda's android kitchen would work on it. If it would, it would automatically make the boot.img unsecured through the root process. Not sure if it will handle it though.

tes5884 said:
HI,
is there someway for me to flash this using fastboot? Because im stuck in fastboot and can't get out of it!
Click to expand...
Click to collapse
Edit: Pointed out in another post - the system image might be too big to flash via fastboot (like I said, I've never actually tried to use these). If you can get into fastboot you can try flashing a recovery, though, and then use that to try dd'ing the system image over or something.
Edit 2: Took down links since I exceeded my Dropbox bandwidth.

Can anyone verify this works? I mean the 6.2.1 pre rooted update zip
Sent from my Triumph using XDA App

dueltothedeath said:
Can anyone verify this works?
Sent from my Triumph using XDA App
Click to expand...
Click to collapse
Yes, I can. Works pretty well too. You'll get some error messages, but those shouldn't be an issue. When I installed it those error messages kind scared me, but once someone explained them, I felt a little better.

sadalius said:
Yes, I can. Works pretty well too. You'll get some error messages, but those shouldn't be an issue. When I installed it those error messages kind scared me, but once someone explained them, I felt a little better.
Click to expand...
Click to collapse
Anychance you could explain them to me? Working for me as well just curious what they mean.

sadalius said:
Wonder if dsixda's android kitchen would work on it. If it would, it would automatically make the boot.img unsecured through the root process. Not sure if it will handle it though.
Click to expand...
Click to collapse
Maybe I'll look into that tonight or tomorrow when I've got some time. I actually didn't know that the kitchen created an unsecured boot image for you. Thanks!

fbm111 said:
Anychance you could explain them to me? Working for me as well just curious what they mean.
Click to expand...
Click to collapse
When I first tried to install I got these error messages:
E:Cannot load volume /misc!
E:Cannot load volume /misc!
E:Unable to stat '/sd-ext/.'
E:Cannot load volume /misc!
E:Unable to open zip file.
since the kindle fire does not have a /misc volume or /sd-ext/ partition, it would give those errors. Those are nothing to worry about. The last error, Unable to open zip file was a real error, but it was cause when I transferred the file to flash to the KF, it got corrupted somehow. I just deleted it from the kindle using file expert and re-transferred it then tried flashing again. All was well at that point. I still got the cannot load volume /misc! and unable to stat '/sd-ext' but like I said, those do not exist on the kindle, thus the messages. But it still installs correctly.
---------- Post added at 05:05 PM ---------- Previous post was at 04:49 PM ----------
eldarerathis said:
Maybe I'll look into that tonight or tomorrow when I've got some time. I actually didn't know that the kitchen created an unsecured boot image for you. Thanks!
Click to expand...
Click to collapse
I took a quick look at it with your rom. It recognizes everything you've done to the ROM thus far. Have a look:
Android OS version : 2.3.4
Device : blaze
Model : Full Android on Blaze or SDP
ROM Name : L27.12.1-P1_QUANTA_20110422_quantaonly-1027-gefdcdf8
Rooted (Superuser.apk + su) : YES
Rooted (unsecured boot.img) : NO
BusyBox installed : YES
BusyBox run-parts support : NO
Apps2SD (Apps to EXT) enabled : NO
/data/app enabled : NO
Custom boot animation allowed : NO
Nano text editor installed : NO
Bash shell support : NO
/system/framework is deodexed : YES
/system/app is deodexed : YES
radio.img found : NO
ROM will wipe all data : NO
I don't have time to try it out with the stock rom, if I get time tomorrow I'll give it a go to see if it will work with it or not to make the boot.img unsecured. This maybe just what the doctor ordered to keep a stock rooted rom.

I flashed it and I don't really notice much of a difference, although my android market still works even tho this update obviously removed it as a system app but the update in /data/app still works.

sadalius said:
I took a quick look at it with your rom. It recognizes everything you've done to the ROM thus far. Have a look:
Android OS version : 2.3.4
Device : blaze
Model : Full Android on Blaze or SDP
ROM Name : L27.12.1-P1_QUANTA_20110422_quantaonly-1027-gefdcdf8
Rooted (Superuser.apk + su) : YES
Rooted (unsecured boot.img) : NO
BusyBox installed : YES
BusyBox run-parts support : NO
Apps2SD (Apps to EXT) enabled : NO
/data/app enabled : NO
Custom boot animation allowed : NO
Nano text editor installed : NO
Bash shell support : NO
/system/framework is deodexed : YES
/system/app is deodexed : YES
radio.img found : NO
ROM will wipe all data : NO
I don't have time to try it out with the stock rom, if I get time tomorrow I'll give it a go to see if it will work with it or not to make the boot.img unsecured. This maybe just what the doctor ordered to keep a stock rooted rom.
Click to expand...
Click to collapse
I just tried using dsixda's kitchen to modify the boot image and it looks like it worked. I can boot it in fastboot at least! I'm going to package it up and try flashing it for some testing. Thanks a lot!
neilrl79 said:
I flashed it and I don't really notice much of a difference, although my android market still works even tho this update obviously removed it as a system app but the update in /data/app still works.
Click to expand...
Click to collapse
It seems like a lot of little changes, so far. You can remove things from your carousel by long pressing them, and you can restrict certain access to your one-click and stuff. It also looks like the "Device" menu in settings got a little facelift because it lists "Application Storage" and "Internal Storage" separately (which I don't think it did before).

I flashed 6.2.1 unsecured .zip via twrp and received two E:Cannot load volume /misc! errors. I then wiped cache and dalvik, and booted up. Everything including Voodoo OTA root works fine. As you said though, google market was obliterated. I am about to put it back.
Edit: after sticking vending.apk back in /system/app and fixing permissions it appears everything is 100% back to order including market and running 6.2.1. I can't thank you enough. 6.2.1 feels much snappier, although it might be a placebo effect.

does this work if i am already on 6.2.1?

Ace 2 Gt-i8160L LATIN. How to install CM?

Ace 2 Gt-i8160L LATIN. How to install CM?
When I install CM, don't wok sim-card and not IMEI.
Restore IMEI don't helped.
This is modem or hw problems, i think.
Sorry my english is bad.

...
Replace tee folder in rom zip /system/lib with the one from stock rom
Sent from my GT-I8160 using Tapatalk

1) backup tee folder
2) On build.prop change all GT-I8160L to GT-I8160 (without L)
3) all wipes factory/cache/dalvik
3) Install CM_Xversion
4) Whith roo explorer replace tee folder
Enjoy.

2) also can delete assert :/
4) you can just replace in zip before flashing (just sayin)
Sent from my GT-I8160 using Tapatalk

When to alter ROM
teddytsen said:
2) also can delete assert :/
4) you can just replace in zip before flashing (just sayin)
Sent from my GT-I8160 using Tapatalk
Click to expand...
Click to collapse
Am located in New Zealand, and hence using model i8160L, running stock JB ROM
Am trying to modify / install Maclaw CM KK ROM -- but am having problems
-- it "reads" the ROM and "immediately" (afaik) but aborts installation
-- NO ERROR MESSAGES come up for any indication as to why it's aborting
Am trying to do the following -- appreciate any feedback to correct procedure if I'm making eny errors
(i) omitting any and all references to L in 8160L string -- should I restrict it to any particular lines? -- using Build.Prop Editor
-- the Settings/About Device shows it as an 8160, rather than an 8160L after the Build.Prop changes, but the boot screen still shows it as the 8160L -- but at least I don't get the error message about trying to install ROM on wrong device
(ii) before attempting installation, downloading the latest ROM, unzipping the ROM using 7zip, deleting "tee" folder
-- and pasting tee folder from the stock JB ROM installed on my phone
(iii) re-zipping the ROM using 7zip -- I notice I get a different MD5 to that llsted on the download page
(iv) attempting to flash the modified ROM in Recovery mode, but it aborts
Don't know enough to know if install procedure tries to validate the "to be installed" ROM's MD5 and aborts since it's different from that on the download page
Don't know what purpose of tee folder is -- is it to connect to local carrier?
How about if I try to install "unmodified" ROM (in its unmodified form) and once it's installed, if it does (?), replace the tee folder at that later stage, to check for ability to connect to carrier?
Do I need to unlock the SIM card first --- as that's also something I haven't done
(naturally, I've backed up and able to restore to what I had before attempting the install)

KiwiCool60a said:
Am located in New Zealand, and hence using model i8160L, running stock JB ROM
Am trying to modify / install Maclaw CM KK ROM -- but am having problems
-- it "reads" the ROM and "immediately" (afaik) but aborts installation
-- NO ERROR MESSAGES come up for any indication as to why it's aborting
Am trying to do the following -- appreciate any feedback to correct procedure if I'm making eny errors
(i) omitting any and all references to L in 8160L string -- should I restrict it to any particular lines? -- using Build.Prop Editor
-- the Settings/About Device shows it as an 8160, rather than an 8160L after the Build.Prop changes, but the boot screen still shows it as the 8160L -- but at least I don't get the error message about trying to install ROM on wrong device
(ii) before attempting installation, downloading the latest ROM, unzipping the ROM using 7zip, deleting "tee" folder
-- and pasting tee folder from the stock JB ROM installed on my phone
(iii) re-zipping the ROM using 7zip -- I notice I get a different MD5 to that llsted on the download page
(iv) attempting to flash the modified ROM in Recovery mode, but it aborts
Don't know enough to know if install procedure tries to validate the "to be installed" ROM's MD5 and aborts since it's different from that on the download page
Don't know what purpose of tee folder is -- is it to connect to local carrier?
How about if I try to install "unmodified" ROM (in its unmodified form) and once it's installed, if it does (?), replace the tee folder at that later stage, to check for ability to connect to carrier?
Do I need to unlock the SIM card first --- as that's also something I haven't done
(naturally, I've backed up and able to restore to what I had before attempting the install)
Click to expand...
Click to collapse
md5 sum change probably because you uncompressed and re-compressed file.
no you dont have to unlock carrier.
use total commander and delete first 3 lines in updater-script.(all before mount.. bahblablah) and then compress it, then try.
btw it doesnt show any status errors?

When to alter ROM cont'd
teddytsen said:
md5 sum change probably because you uncompressed and re-compressed file.
no you dont have to unlock carrier.
use total commander and delete first 3 lines in updater-script.(all before mount.. bahblablah) and then compress it, then try.
btw it doesnt show any status errors?
Click to expand...
Click to collapse
MANY MANY thanks for your very prompt reply, and further information
"status errors" -- as a result of ?? -- no status errors evident after rebooting with modfified Build.Prop
had lots of "fun" on my previous efforts with custom ROMs -- played with several on a Huawei G300 I had --
-- but, gee, this is an ongoing learning process -- now to learn about updater script !!!
(only learnt about Total Commander from your post - despite its high rating -- but note others have used other things for "text editing")
(but have discovered some TUTs on xda)
Reading more carefully through the posts I see it may be possible to flash the ROM, and then later, substitute the tee folder supplied in the Maclaw ROM with the stock JB one -- right?
I'll definitely learn more about updater-script, but I'll try to flash the ROM again without modifying the ROM === OK?

KiwiCool60a said:
MANY MANY thanks for your very prompt reply, and further information
"status errors" -- as a result of ?? -- no status errors evident after rebooting with modfified Build.Prop
had lots of "fun" on my previous efforts with custom ROMs -- played with several on a Huawei G300 I had --
-- but, gee, this is an ongoing learning process -- now to learn about updater script !!!
(only learnt about Total Commander from your post - despite its high rating -- but note others have used other things for "text editing")
(but have discovered some TUTs on xda)
Reading more carefully through the posts I see it may be possible to flash the ROM, and then later, substitute the tee folder supplied in the Maclaw ROM with the stock JB one -- right?
I'll definitely learn more about updater-script, but I'll try to flash the ROM again without modifying the ROM === OK?
Click to expand...
Click to collapse
-Dont care about ro.build.model. once assert is deleted you dont have to change it. And its not mandatory.
-I recommended total commander just because its the only root browser i have that shows the assert in 3 lines exactly. Unless es etc. You can also use other editors ^.^
-like when installation is aborted, it says status 7(or 0 etc)
Sent from my GT-I8160 using Tapatalk

Many thanks -- now for the "rest" and time for tee
teddytsen said:
-Dont care about ro.build.model. once assert is deleted you dont have to change it. And its not mandatory.
-I recommended total commander just because its the only root browser i have that shows the assert in 3 lines exactly. Unless es etc. You can also use other editors ^.^
-like when installation is aborted, it says status 7(or 0 etc)
Sent from my GT-I8160 using Tapatalk
Click to expand...
Click to collapse
Many thanks!! KK installed -- that was the "fascinating" thing -- no status errors on previous failed attempt at installation -- nothing
but now it's installed -- with GApps added, and now to "worry" about the rest of it all
unsurprisingly -- if tee does what I think it does -- but I can't find a TUT on that anywhere
-- so currently, I can't connect to my local carrier, so it's currently not a :"phone" as such
even more frustratingly, computer found phone when it was first plugged in, but now seems to have lost it!! time to reboot system
-- and, it's been a while since I used CM but I can't find extsdcard!!

Cm file manager?
Settings-general settings-access mode- root
Sent from my GT-I8160 using Tapatalk

Permissions
teddytsen said:
Cm file manager?
Settings-general settings-access mode- root
Sent from my GT-I8160 using Tapatalk
Click to expand...
Click to collapse
sorry, not used to that one -- for that matter, I tend to stay away from things affecting the system I don't know
so I'm lost in permissions in different apps -- can't find "paste" in CM file, and can't find RW permissions in ES!!
But you're being exceptionally patient! thanks, heaps

Lot easier than I thought -- and MANY thanks again
KiwiCool60a said:
sorry, not used to that one -- for that matter, I tend to stay away from things affecting the system I don't know
so I'm lost in permissions in different apps -- can't find "paste" in CM file, and can't find RW permissions in ES!!
But you're being exceptionally patient! thanks, heaps
Click to expand...
Click to collapse
Actually, it's a lot easier than I thought -- working phone, with KK installed -- without need to unlock carrier!!
Many thanks for the guidance, patience ....
and, of course, to the ROM developers

Repeated problems with Maclaw KK ROM
KiwiCool60a said:
Actually, it's a lot easier than I thought -- working phone, with KK installed -- without need to unlock carrier!!
Many thanks for the guidance, patience ....
and, of course, to the ROM developers
Click to expand...
Click to collapse
Many thanks for past help with intall procedure -- but have had repeated problems of late -- last installed ROM on March 9th -- could install several versions prior to that date, and use them successfully, but since then have been unable since I repeatedly get "Error searching for networks", and hence cannot connect to carrier, and hence unable to use phone as phone, though other functions seem to work OK, -- any ideas??

[FIX] FED-Patcher v7 (ForceEncrypt Disable Patcher)

Hello everybody,
I created a tool for the nexus 9 that gets rid of the ForceEncrypt flag in a generic way (meaning it should work no matter what rom you are on). It does that by patching the currently installed boot.img.
Background
The Android CDD (Compatibility Definition Document) suggests that all devices SHOULD enable full disk-encryption (FDE) by default. Even though I support every step towards more security I have to criticize this approach. FDE comes at a price. Encryption takes time because some component has to de- and encrypt the stuff on the disk at some point and in the case of the nexus 9 (aka flounder) it's the CPU's task. Even though the nexus 9's CPU has 2 pretty fast cores you can still easily feel the difference between FDE in the on- or off-state. The I/O is faster and boot-times take only half as long. (I did not do any measurements)
There is an ongoing discussion about this topic in cyanogenmod's gerrit. Although it's a fun read it is pretty clear that this exchange of views is not going anywhere near a useful outcome.
Because performance is important to me and my tablet does not need the extra security I created the FED-Patcher (ForceEncrypt Disable Patcher)
How does it work?
FED-Patcher is a simple flashable ZIP that is supposed to be run in a recovery that has busybox integrated (like TWRP or CWM). This is what it does:
Checks if your device is compatible
Dumps the currently installed boot.img.
Unpacks the dump of your currently installed boot.img. The unpacking process is done via a self-compiled, statically linked version of unmkbootimg.
It patches the filesystem tables which include the force-encrypt flags. This process will change "forceencrypt" to "encryptable".
Then it patches the filesystem tables to not use dm-verity. This is done by removing the "verify" mount-parameter.
Creates a new boot.img. The unpacking process is done via a self-compiled, statically linked version of mkbootimg.
Flashes the modified boot.img
Supported devices
HTC Nexus 9 WiFi (flounder)
HTC Nexus 9 LTE (flounder_lte)
Motorola Nexus 6 (shamu)
Version History
v1 - Initial version with HTC Nexus 9 WiFi (flounder) support
v2 - Added Motorola Nexus 6 (shamu) support
v3 - Added support for HTC Nexus 9 LTE (flounder_lte)
v4 - Added support for signed boot-images
v5 - Changed error handling to compensate for missing fstab files. Some roms seem not to ship with the complete set of boot-files from AOSP.
v6 - FED-Patcher will enforce the same structure for the patched boot.img that the original boot.img had. Additionally, the kernel commandline will also be taken over. This should fix pretty much every case where devices would not boot after patching.
v7 - FED-Patcher will now disable dm-verity in fstab to get rid of the red error sign on marshmallow roms.
What do I need to make this work?
A supported device (Your nexus 9)
An unlocked bootloader
An already installed ROM with forceencrypt flag. (like cyanogenmod CM12.1)
A recovery that includes busybox (TWRP, CWM)
How do I use it?
Make a thorough, conservative backup of your data if there is any on your device
Go into your recovery (TWRP, CWM)
Flash fed_patcher-signed.zip
If your device is already encrypted (You booted your ROM at least once) you need to do a full wipe to get rid of the encryption. This full wipe will clear all your data on your data-partition (where your apps as well as their settings are stored) as well as on your internal storage so please, do a backup before. If you don't do a backup and want to restore your data... well... Call obama.
How do I know if it worked?
Go into your "Settings"-App. In "Security", if it offers you to encrypt your device it is unencrypted. If it says something like "Device is encrypted" it indeed is encrypted.
IMPORTANT: If you update your ROM you have to run FED-Patcher again because ROM-updates also update the boot-partition which effectively removes my patch. So, if you are on CM12.1 for example and you used my patch and do an update to a newer nightly you have to run FED-Patcher again. If you don't do so Android will encrypt your device at the first boot.
Is it dangerous?
Well, I implemented tons of checks that prevent pretty much anything bad from happening. But, of course, we're dealing with the boot-partition here. Even though I tested FED-Patcher quite a lot there is still room for crap hitting the fan.
Screenshot
Scroll down to the attached thumbnails.
Credits
* pbatard for making (un)mkbootimg (dunno if he is on xda)
* @rovo89 for his xposed framework - I used some of his ideas by reading the source of his xposed installer flashable ZIP for FED-Patcher.

Thanks for creating this! In theory, would this work for the Nexus 6 as well? It would seem like it's a similar process.

itlnstln said:
Thanks for creating this! In theory, would this work for the Nexus 6 as well? It would seem like it's a similar process.
Click to expand...
Click to collapse
Hey there,
yes, it would probably work because the process itself is pretty generic. The only real difference between devices is the device-path for the boot-partition as well as the path(s) for the fstab-file(s) inside the boot.img. Nothing that cannot be done - but I don't have a device for testing. If you feel adventurous I can do a nexus6 (shamu) version for you for testing. I will double check so it should not eff up your device .
EDIT: Not to forget, the nexus 9 is a 64bit device. mkbootimg as well as unmkbootimg are compiled for 64bit. I have to rebuild those two programs for 32bit to make them work for 32bit devices.

If you have time for a N6 build, that would be great. If not, it's not a big deal since there seems to be more support for that device.

itlnstln said:
If you have time for a N6 build, that would be great. If not, it's not a big deal since there seems to be more support for that device.
Click to expand...
Click to collapse
Well, it's pretty much done. Do you want to test a version that does not actually flash anything but do everything else - just to see if it works correctly?

Absolutely!

itlnstln said:
Absolutely!
Click to expand...
Click to collapse
Alright, here you go!
If no error occurs there will be the already modified boot.img file in your temp-directory of your nexus 6. You can send me this file to be completely sure that everything went according to plan. Here is the adb-command:
Code:
adb pull /tmp/fed_patcher/boot-new.img
If all goes well I will upload the new version with nexus 6 (shamu) support tomorrow.
Good night!

gladiac said:
Alright, here you go!
If no error occurs there will be the already modified boot.img file in your temp-directory of your nexus 6. You can send me this file to be completely sure that everything went according to plan. Here is the adb-command:
Code:
adb pull /tmp/fed_patcher/boot-new.img
If all goes well I will upload the new version with nexus 6 (shamu) support tomorrow.
Good night!
Click to expand...
Click to collapse
Thanks! It seemed to work OK. Here's the boot image.

itlnstln said:
Thanks! It seemed to work OK. Here's the boot image.
Click to expand...
Click to collapse
Thanks for your help! I just updated the flashable ZIP in the first post. Enjoy

gladiac said:
Thanks for your help! I just updated the flashable ZIP in the first post. Enjoy
Click to expand...
Click to collapse
You're the best! Thanks!

I noticed in op it says "4 pretty fast cores". This puppy only has 2 cores. Just throwing it out there for readers that don't know. I'm sure it was just a minor oversight.
Sent from my Nexus 9

madbat99 said:
I noticed in op it says "4 pretty fast cores". This puppy only has 2 cores. Just throwing it out there for readers that don't know. I'm sure it was just a minor oversight.
Sent from my Nexus 9
Click to expand...
Click to collapse
Hi,
you are right, thanks. I just fixed the text in the op.

Hey everybody,
I will enable support for the Nexus 9 LTE (flounder_lte) this afternoon in FED-Pather v3. If you want other devices to be supported please tell me. Is there a list of android devices that have forced encryption?

So this works great, leaving device unencrypted. But anyone having issues with apps crashing? Most especially Google Play Services?

femmyade2001 said:
So this works great, leaving device unencrypted. But anyone having issues with apps crashing? Most especially Google Play Services?
Click to expand...
Click to collapse
This problem is new to me. My patch only modifies the boot-image so that it does not enforce encryption. It is merely a flag in fstab that gets changed and should not have anything to do with crashing apps. Anyway, do you have a logcat?

Hey everybody,
v3 is here with HTC Nexus 9 LTE (flounder_lte) support!
Enjoy

I'm getting an error with my N9 (WiFi). When I try flashing in TWRP, it throws this error:
! Unpacking failed
=> unmkbootimg return value: 0
E: Error executing updater binary in zip...
All I did was go into fastboot, flash the updated image for LMY48M, then go into TWRP to flash the fix. I even went back into fastboot to try re-flashing the boot.img.

itlnstln said:
I'm getting an error with my N9 (WiFi). When I try flashing in TWRP, it throws this error:
! Unpacking failed
=> unmkbootimg return value: 0
E: Error executing updater binary in zip...
All I did was go into fastboot, flash the updated image for LMY48M, then go into TWRP to flash the fix. I even went back into fastboot to try re-flashing the boot.img.
Click to expand...
Click to collapse
Hi, sorry to hear that. I will have a look into the boot.img that gets shipped with LMY48M. Not sure what is going on here.

itlnstln said:
I'm getting an error with my N9 (WiFi). When I try flashing in TWRP, it throws this error:
! Unpacking failed
=> unmkbootimg return value: 0
E: Error executing updater binary in zip...
All I did was go into fastboot, flash the updated image for LMY48M, then go into TWRP to flash the fix. I even went back into fastboot to try re-flashing the boot.img.
Click to expand...
Click to collapse
Alright - unmkbootimg fails because the boot.img that google ships has 256 Bytes of extra data (it is probably signed or something) at the beginning. If you strip that off it works correctly:
Code:
dd if=boot.img of=boot-stripped.img bs=256 skip=1
Well, this was unexpected. But nothing that cannot be dealt with. I will make my flashable ZIP search for the offset of the boot.img-signature inside the dumped boot.img and strip of the preceding data. The rest of the process should work as usual.

itlnstln said:
I'm getting an error with my N9 (WiFi). When I try flashing in TWRP, it throws this error:
! Unpacking failed
=> unmkbootimg return value: 0
E: Error executing updater binary in zip...
All I did was go into fastboot, flash the updated image for LMY48M, then go into TWRP to flash the fix. I even went back into fastboot to try re-flashing the boot.img.
Click to expand...
Click to collapse
Hi @itlnstln,
I just made a new version which should do the trick. I tested the new functionality to the best of my knowledge. If the script fails for some reason it wont flash anything - so the probability for actual damage is very low. Do you feel adventurous xD?
Please tell me if it worked for you or not.

[Q] Root LCA44B

As of build LCA44B the /system partition is no longer ext4, but squashFS. As I understand it this is a read-only file system, and there's no way to mount it as r/w.
Is it possible to somehow achieve root anyway? I've tried to extract the system.img from the LCA44B OTA package, and then converting it to ext4 to be able to fastboot flash it. That didn't work and I don't know if it's because it's impossible to do, because I did something wrong or because I'm on a windows machine with cygwin/ported UNIX tools binaries.
I've been struggling with this for the last couple of days, and I started out with absolutely 0 knowledge about anything regarding this kind of stuff. I still don't know enough to figure it out, but if anyone could point me in the right direction I think I might be able to.
Any help or knowledge is appreciated!

Latest thing I've tried:
1. Running sdat2img on the .dat files in the LCA44B OTA.
2. Running unsquashfs on the .img that sdat2img created to be able to make changes.
3. Adding su binaries and other files needed for root to the working directory.
4. Running mksquashfs on the working directory.
5. Flashing the new .img using Motorola's fastboot.
I really don't understand why this isn't working. Unless there's some hidden error in any of the tools I'm using, or if the bootloader somehow reacts to the fact the the new system.img is a few kb larger than the old one, I don't see a reason as to why this shouldn't work. What happens when I reboot after flashing is: The watch starts booting, showing the Motorola logo and vibrating for a split second. It then, instead of continuing to the bootanimation, reboots into recovery. The only thing I can see from there is that it seems to have a problem with mounting the cache partition.
Again, any help or knowledge is appreciated.
Sent from my A0001 using Tapatalk

Rooted HTC 10 - cannot mount /system - root incomplete ?

Hi folks,
I need your help.
A few days ago I have received my brand new HTC 10. I updated to latest Android 7 Nougat and began to root remaining stock.
I followed the official guide and unlocked the bootloader, flashed latest TWRP (3.1.1.0) and SuperSU v.2.82SR1 and even got S-OFF by SunShine.
System is up an running and readily booting but...
Fact is I cannot mount /system in TWRP without the option "read-only". When I try to install apps via TWRP I get repeated messages saying "Failed to mount '/system' (Invalid argument) " and usually the apps do not install properly - flashed apps do not show up in the system after reboot.
In the system I have tried to rename a file audio_effects.conf (this is needed to install Viper4Android) in the folder /vendor/etc/ on the device but the folder is strictly read only. Any attempts to mount the folder as RW (using "adb shell", "su", "mount -o remount,rw /system" and similar) have failed. I have tried to gain access to files in the system folder using Root Explorer and Total Commander but the files remain strictly read only. I just get error messages trying to change file attributes, permissions,names).
SuperSU seems to work and according to Root Checker I am properly rooted but I doubt this. Somehow /system seems to be locked and not accessible.
Any ideas what I could do ?
Many thanks for your help ! :good:

Well, I simply flashed Viper10 ROM and the issue was gone.
Feel free to suggest solutions to the problem as somebody else might come accross this thread struggling with a similar issue. I believe the issue was caused by an incompatibility between the latest Android Nougat and the last available TWRP.

Buddha1979 said:
Well, I simply flashed Viper10 ROM and the issue was gone.
I believe the issue was caused by an incompatibility between the latest Android Nougat and the last available TWRP.
Click to expand...
Click to collapse
No, it's not an incompatibility issue.

Does anyone know what is causing this? I been running into a similar type issue where I get an error trying to flash ROM's. Tried to do a TWRP backup and it failed to back up data. I do a factory reset and data format and it seems to fix some things but still have trouble flashing ROM's. I was able to restore a nandroid but have ran into this issue a few times. I am on Viper magisk.

plz help a noob
LibertyMonger said:
Does anyone know what is causing this? I been running into a similar type issue where I get an error trying to flash ROM's. Tried to do a TWRP backup and it failed to back up data. I do a factory reset and data format and it seems to fix some things but still have trouble flashing ROM's. I was able to restore a nandroid but have ran into this issue a few times. I am on Viper magisk.
Click to expand...
Click to collapse
I also just recently updated to nougat and when i tried to root using the latest (TWRP 3.0.3-11) it seems I get stuck on a screen with red text that says, "This build is for development purpose only . Do not distribute outside of htc without htc's permission."
I know this is not the original question but was hoping someone with more experience could help instead of starting a new thread :/
Thanks much!

I just ran the latest Verizon RUU and I am still getting this error when trying to flash Viper10_5.9.0_MAGISK. Seems system is not mounting, I don't know I will appreciate any help Thank you.