How to? 7.0 Stock ROM Kernel with Mass Storage Gadget & FUSE support - Huawei P9 Questions & Answers

Hi all,
my Huawei P9 is running Android 7.0 (EMUI 5.0.1) rooted.
As "Build" is shown "NRD90M test-keys", but as this doesn't correspond to any of what I have seen as valid build numbers so far, I guess this is wrong and somehow related to the Nandroid backup restore I did after upgrading this phone from Android 6 to 7... Anyway, my question is this:
What's the best option for me now to make this phone mass storage mode compatible?
The USB Mass Storage Enabler app claims that the current kernel does not support Mass Storage Gadget & FUSE and thus the app won't function.
So it seems that I need a new kernel.
- Is there a kernel available that I can use to simply substitute my current kernel?
- Can / should I easily compile my own one? (I have done that 15 years ago with Linux kernels, since then no kernel compilation experience anymore). If so, where do I start?
- Do I have to use a custom ROM? Which one do you recommend for that feature to work and for a lightweight system with high performance, flashable without muhc hassles from my current status?
Thanks a lot!

i think you updated to a beta firmware,
this thread may help,
good luck

Du you mean, a non-beta will contain the necessary kernel options?

daniel908 said:
Du you mean, a non-beta will contain the necessary kernel options?
Click to expand...
Click to collapse
not sure, but some had similar issues with the nougat beta.

[Post deleted] - sorry, didn't find a delete button, so just deleted the content.

On another P9 with Android 7.0 / EMUI 5.0.1 (Build-Nr EVA-L09C432B394) the USB Mass Storage Enabler app also doesn't work for the same reason.
So I think that beta (if it really is one - the Nandroid backup title of the system with build number shown above has the same string in its directory name - maybe when restoring the Nandroid backup, that string is written into the "Build" field?) is NOT the reason for the mode not working.
Anyone here who uses that app and has USB storage mode support on a (rooted) stock Android 7.0 / EMUI 5.0.1 on a P9?

The app says (Google Play) that it works only on "selected" Samsung and Sony devices (btw, it"s rated only 3.5)
I just tried (Magic zRainbow v3 which is based on v394 and rooted Magisk), it says it doesn't find the lun file and not compatible with the kernel. IMO, it can't work here (I don"t know would it work with AOSP firmwares instead of stock).
Btw if you really restored TWRP backup from MM (EMUI 4.1) to N (EMUI 5), you are lucky that you didn't (soft) brick the phone

The app worked very well on my older P9... so it's not really limited to "selected Samsung and Sony devices".
I didn't get a notice about missing LUN file, but kernel incompatibility message was shown here, too. However, as far as I know the kernel can be replaced easily by flashing a new kernel? Question is then only, how to get my hands on a compatible kernel. Compile my own one? I have never done this with Android.
Or is there any other method to enable mass storage mode for the microSD card, so I can sync my stuff easily with the Mac on a daily schedule without having to remove the card from the phone everytime?
I tried other (e.g. MTP-based) sync solutions, but they all fail badly (either crash or take ages) when keeping those about 2.000.000 small JPEG files in sync that I need on the phone's microSD card. Those files are virtual tours / gigapixel image tiles, that I host on the phone to be able to present those virtual tours to clients without carrying a computer with me).

Related

kexec for HP TouchPad (WORKING release!)

kexec is now fully working!
Kexec host kernel: https://github.com/willcast/ubuntu-kernel-tenderloin branch is "kexec"
Graphical bootloader: https://github.com/willcast/kexecboot
Compiled host kernel uImage UPDATED: https://docs.google.com/file/d/0B4WUjKii92l2RHJoNE93c2dVRlU/edit?usp=sharing
THE ATTACHED KERNEL PATCH (decomp_copy_atags.diff) _MUST_ BE APPLIED for ANY kernel to be bootable FROM kexec.
YouTube: http://www.youtube.com/watch?v=ko_4cOj_5iM
Kexec kernel and OS installation is best performed through SmackMe2, which is available in its own thread on this site.
I have no idea what you are saying, but keep up the great work!
Keep up the good work man , one question with you work in the future can we delete web os from the touchpad forever?
I imagine that's already possible. Use lvm to delete all the logical volumes not tied to another OS and then delete the uImage.webOS symlink. That deletes webOS, frees mostof its space and removes it from the moboot menu.
If you choose to do that, though, using the doctor to restore WEBOS will be even more difficult because you'll have to wipe out everything AND potentially need to "unbrick" your TP (using the method involving NovaCom, the small boot image ripped from the doctor and a string of LVM commands that is posted on sone or other forum.)
Lvm? Can you make a tutorial? How to remove webos from touchpad?
Thank you
Before this is complete or posted for testing, I think we will need a tutorial and links to files of how to fix the tp from a full brick such as issues with removing and restoring webos.
Great job if your boot loader works as planned we will have a full multi-boot device with a few restrictions(drivers for untested ports, etc).
Keep it up.
Sent from my cm_tenderloin using xda app-developers app
Awesome that you're resuming development castrwilliam! Can't help you with kexec though, sorry. I hang around in the Motorola Defy forums and some developers like Quarx have tried pursuing the kexec route in order to load custom kernels onto the Defy, might be worthwhile to throw him a PM. Would be great to have a more flexible bootloader!
I anyone needs a full restore, this thread helped me out. I followed the instructions when I screwed up and doctored without removing partitions. I believe WebOS Doctor handles repartitioning, so it should work:
http://forum.xda-developers.com/showthread.php?t=1426244
WORKING (but non-Kexec) Android multiboot for TouchPad.
DON'T TRY ANYTHING UNTIL YOU HAVE READ THE WHOLE POST!!
Beta 2 Updated with support for my Froyo Qcom kang.
I created a script that can install multiple versions of Android on the HP Touchpad, side by side, such that they can be selected at the MoBoot menu and operate independently. The script modifies them, on the Touchpad itself, to work with the new names for the partitions.
I want your feedback on this installer. It is used in the same way as ACME Installer but only shares one line of actual code with it (and it also uses the same binaries and config files on the initial ramdisk image, but they are Open Source so that should'nt matter.) I'll be posting this on XDA in a minute, my username there is also "castrwilliam".
If you do choose to use (TEST!) this:
- You need to create a folder on your media partition (the one that is shown when you select USB mode) with the following zips:
moboot [moboot_0.3.5.zip]
(the rest are optional but I recommend using them all so that you can help me test everything)
Froyo Test [Froyo-2.2.1-Qcom-Kang-Touchpad-a0.1-incl-gapps.zip]
CM7 alpha3.5 [update-cm-7.1.0-tenderloin-a3.5-fullofbugs.zip]
CM9 latest nightly [cm-9-xxxxxxxx-NIGHTLY-tenderloin.zip]
CM10 latest preview [cm-10-xxxxxxxx-EXPERIMENTAL-tenderloin-FOR_LIMITED_TESTING_ONLY_CAM.zip]
2.3.x gapps [gapps-gb-xxxxxxxx.zip]
4.0.x gapps [gapps-ics-xxxxxxxx.zip]
4.1.x gapps [gapps-jb-xxxxxxxx.zip] MAKE SURE not to use 4.2 gapps!
(NO Android Recovery will work yet, so don't try. It will reject TWRP and CWM at least.)
- If you already have Android and/or Moboot and/or native Linux (Ubuntu, etc.) installed:
* back up any data on your media volume. webOS should back up your apps for you.
* make both a nandroid (which WON'T work to restore in a multiboot config, but if you go back to single boot, it will be fine) and a Titanium backup [which should be portable to the same OS.]
* run ACMEUninstaller and then run SmackMe-Installer.
* if you have native Linux, backup your /etc and /home (I recommend the lovely GNU tar and gzip/bzip2). That should be the majority of what to keep.
* ALSO uninstall any native Linux you may be using after you back it up.
* lastly unzip and novacom boot the SmackMe-Installer.
If you don't already have Android, MoBoot OR native Linux, just:
* back up any data on your media volume. webOS should back up your apps for you.
* then unzip and novacom boot the SmackMe-Installer.
youtube demo:
http://www.youtube.com/watch?v=8Hhy20lzhR4&feature=youtu.be
File should be attached. Report bugs by PM'ing me, or posting in this thread
Can i remove webos with this multiboot? And stay only on android and ubuntu?
This is strictly an installer. I was going to write a webOS removal script. However, android doesn't have the needed binaries. That leaves me two options: make another thing like SmackMe to do it or do it under whatever version of native Ubuntu you are running. Either way, I really don't want to have to test it myself. If I need to I'll have to doctor my touchpad EVERY TIME I do it. That's a lot of doctoring and a lot of flash write wear. So the answer is basically "find me a dev that wants to remove webos too. They'll either make you one or beta test mine." Sorry man.
Amazing keep up the good work castrwilliam !
Strange request
Hey, does anyone here still have the 2011 Froyo (2.2.1) system dump for Touchpad? It wasn't CM6, just something that HP accidentally released and someone over at Rootzwiki dumped. I'm posting this here because I have no account and they'd think I'm a noob there. All the links are down to it and I want to try messing around with its files, just for kicks. Maaaaybe I can get it to boot, and add support for it to the SmackMe installer, so at least I can have *four* versions of Android on my touchpad.
http://forum.xda-developers.com/showthread.php?t=1234381
You know, 'cause I'm just that crazy.
Wow it's been hard to find it but i think this is the good dump:
http://download.digiex.net/Consoles/Tablets/HP-Touchpad-Android2.2.1-Disk-Images.zip
sources:
http://digiex.net/downloads/downloa...hpad-android-2-2-1-system-image-download.html
it's alive! (sorta)
Somebody on XDA found a link that I thought was dead. It was the mmc dump of someone who had Froyo leaked by HP onto their fire-sale Touchpad.
FAQ:
"Obviously nobody wants this. Everybody's running Jelly Bean."
That's exectly why I did it. My point is to do the most outrageous and downright unnecessary things possible with commonplace hardware.
"What doesn't work?"
Rotation, sound, wi-fi, softkeys (i.e. Home, Back, Menu, Search.)
"What does work?"
Camera (OH HAYULL YA), touchscreen, battery reading, power button, volume button (but it dosen't matter b/c sound is borked).
"I can haz Modded Froyo?!"
Not yet.
YouTube: http://www.youtube.com/watch?v=zX29IcTIB14
Hah awesome work, I think you hold the record of most different OS'es on one device now! It looks quite functional already.
Oh and about the "Obviously nobody wants this. Everybody's running Jelly Bean." quote, I only run WebOS and your Ubuntu 12.10 port on the TP!
As soon as I get my power button sorted out I am on this!
Sent from my slim_tenderloin using xda app-developers app
Hey everyone! Froyo here!
I've just zipped up my Froyo kang such that it will work if flashed from SmackMe, and if you're crazy enough to run it alone, hopefully also Android recovery.
sound works!!
The Wi-Fi works now BUT YOU NEED A STATIC IP ADDRESS. (problems with dhcpcd)
The buttons are hacked to work (by my new shell script: /system/bin/buttond, check it out) as follows:
Volume Down is Back
Volume Up is Menu
Center is Home.
Obviously once the audio works (if ever) that will be an issue. My embarrassing secret (at least probably to the devs here) is that I don't know Java. That makes it difficult to mod on any touchscreen buttons...
The real audio library is /system/lib/libaudioflinger.real.so and the stub one (default via a symlink) is /system/lib/audioflinger.so. Using the real one causes bootloops.
Auto rotation still won't function.
Google Apps and even Facebook are included in this ROM. (It's not CM6.) So are some potentially geeky Qualcomm apps.
Don't set up your Google Account during first boot, because it will ask you to slide the keyboard open. That sounds pretty impossible onn this device. Set it up from Settings later, and you shouldn't have that issue.
UPDATED due to install issues with actual Android Recovery. Redownload.
Download Initial Version (Alpha Minus-One-Point-One): https://www.dropbox.com/s/wcs2mra8aedj1hf/Froyo-2.2.1-Qcom-Kang-Touchpad-a0.1-incl-gapps.zip
Download Second Version (Alpha 0.2): https://www.dropbox.com/s/t1cptjj5i02epas/Froyo-2.2.1-Qcom-Kang-Touchpad-a0.2-incl-gapps.zip
^^^
I wanted to try froyo soo bad when I heard about those dumps last year (I think) lol. I still want to try it.
Now, if I read correctly, I can flash this from TWRP/CWM right?
jacobas92 said:
^^^
I wanted to try this soo bad when I heard about it last year lol. I still want to try it.
Now, if I read correctly, I can flash this from TWRP/CWM right?
Click to expand...
Click to collapse
It should work from that. I only tried with my SmackMeInstaller from the last page. That said... MAKE A NANDROID, because it WILL delete your current Android install, and if anything goes wrong (or even if it works but you see a CWM/TWRP error/warning), tell me and I'll fix it.
castrwilliam said:
It should work from that. I only tried with my SmackMeInstaller from the last page. That said... MAKE A NANDROID, because it WILL delete your current Android install, and if anything goes wrong (or even if it works but you see a CWM/TWRP error/warning), tell me and I'll fix it.
Click to expand...
Click to collapse
Ok, thanks!

problems after flashing - 4.4.4 / odin / SU SUPER / SD-RAM not recognized

I have bought a S3 –LTE to replace my old S3 – LTE with spider web and broken frame.
OLD: GT-I9305 with Android 4.4.4, Build: KTU84P.I9305XXUFNL1
NEW: GT-I9305 with Android 4.4.4, Build: KTU84P.I9305XXUFOB2
I use the S3 for business and partially private but not for videos/music or games.
I use the phone / contacts / calender
I use gmail
I use whatsapp
I use the camera / dropbox
That’s it 99%
I copied the OLD data / apps to the NEW and added all whatsapp files/pictures …. IT WORKED !! - I should have stopped here......
But: Leaving me with 13 GB of 16GB in use (like with the OLD S3) and leaving the 64GB of SDRAM-card unused.
So I tried to install and use SDK Manager from REBELLOS / KINGO SUPER USER from KING SOFT / FOLDER MOUNT (ROOT) from MADMACK.
The KINGO SU was installed with no problems and no messages but it seemed as if it did not work.
The FOLDER MOUNT therefore did not work and I got regular system messages that google play store had to be stopped.
So I RESET TO FACTORY DEFAULT.
Then I tried CF-AUTO ROOT with Version I9305XXUFNL1_I9305VD2FNL1_VD2 together with ODIN.
This worked directly with no problems and no error messages.
But here I had the same problem I get error messages from GOOGLE PLAY STORE STOPPED. Even if I disable KNOX as SU-SUPER says.
Plus: the NEW S3 does not recognize my 64GB SDRAM anymore. I tried the 64 GB in three different SAMSUNG phones and it displayed 59 GB free there but not in my NEW S3 there it says 0.
So maybe someone can help me .
First: Do I need to get rid of the SU / ROOTed Version of my system or do I need to add additional apps and software ? What should I do ?
Second: I would like to move my old apps and data to the NEW S3
Third: I would like to move my apps and data to the unused SDRAM card.
And then there is still the question regarding the "custom binary counter: 2" and "KNOX Warranty void : 1"
What is the best way to go forward (or better backward...) ?
Best regards, Erich
First off, i want to clarify some terminology:
1. SDRAM =/= SD-Card. SDRAM = Synchronous dynamic random-access memory and SD-Card = Secure Digital Card.
2. It is SuperSU not SU-SUPER
3. custom binary counter is the number of flashes the phone underwent
4. KNOX warranty void bit is useless since i imagine your phone is out off warranty. 0x0 is not triggered, 0x1 is triggered. Think of it as a fuse in electronics and electricity.
Onwards to the actual steps i say you should do (beware, you have the newer bootloader, so i'm not that well-informed about what you can do, so bear with me):
[-find a way to downgrade to the pre-KK bootloader, if not go bellow
-flash through ODIN a KK firmware I9305XXUFOL2_I9305TPLFOL2_TPL, the region doesn't matter, then re-root it and try to force install the latest version of Play Store by uninstalling it and reinstalling it manually;] not really recommended;
- my recommended way:
1. flash a recovery through ODIN using the thread HERE;
2. get yourself a ROM from HERE, whichever you fancy, it doesn't matter.
3. get yourself the latest modem from HERE just to be safe;
4. get yourself AGNi PureSTOCK from HERE for a more customisable device;
5. or as an alternative, check out THIS thread for a stock 4.1.2 ROM with 4.1.2 GOOD bootloader. Then, if you succeed in installing and reverting to the old bootloader, then follow the steps above from 1 to 4.
6. ??? PROFIT.
If you successfully finished the above steps and have a working and stable device, use Samsung's Smart Switch app to transfer all of your stuff from the old S3 to the new one.
On the way, you may actually repair the SD card detection on the new S3.
I do not recommend using the External SD Card for applications because it is way slower than the internal one. I recommend using it as just storage. Make sure to clear cache (Settings-General-Storage, tap on Cached data and then on OK) every week.
Some apps use the external SD card as data storage, although it depends how the app is written. For the apps that support it, just go to Settings-General-Application Manager and swipe from the right to the left and then check whatever app you want to move the data to the external SD card
SDK Manager from REBELLOS is useful for developers only
Folder Mount is useful only if you have games that require you install their massive data to the internal SD card and you don't have enough space.
And as a small piece of advice, clarify stuff; "13 GB of 16GB in use" might mean two things: 13/16gb used or 13/16gb free.
Hope my 'small' post helps you.
thank you for your time and help - Alexander
Alexander_the_B0ss said:
First off, i want to clarify some terminology:
1. SDRAM =/= SD-Card. SDRAM = Synchronous dynamic random-access memory and SD-Card = Secure Digital Card.
2. It is SuperSU not SU-SUPER
3. custom binary counter is the number of flashes the phone underwent
4. KNOX warranty void bit is useless since i imagine your phone is out off warranty. 0x0 is not triggered, 0x1 is triggered. Think of it as a fuse in electronics and electricity.
Onwards to the actual steps i say you should do (beware, you have the newer bootloader, so i'm not that well-informed about what you can do, so bear with me):
[-find a way to downgrade to the pre-KK bootloader, if not go bellow
-flash through ODIN a KK firmware I9305XXUFOL2_I9305TPLFOL2_TPL, the region doesn't matter, then re-root it and try to force install the latest version of Play Store by uninstalling it and reinstalling it manually;] not really recommended;
- my recommended way:
1. flash a recovery through ODIN using the thread HERE;
2. get yourself a ROM from HERE, whichever you fancy, it doesn't matter.
3. get yourself the latest modem from HERE just to be safe;
4. get yourself AGNi PureSTOCK from HERE for a more customisable device;
5. or as an alternative, check out THIS thread for a stock 4.1.2 ROM with 4.1.2 GOOD bootloader. Then, if you succeed in installing and reverting to the old bootloader, then follow the steps above from 1 to 4.
6. ??? PROFIT.
If you successfully finished the above steps and have a working and stable device, use Samsung's Smart Switch app to transfer all of your stuff from the old S3 to the new one.
On the way, you may actually repair the SD card detection on the new S3.
I do not recommend using the External SD Card for applications because it is way slower than the internal one. I recommend using it as just storage. Make sure to clear cache (Settings-General-Storage, tap on Cached data and then on OK) every week.
Some apps use the external SD card as data storage, although it depends how the app is written. For the apps that support it, just go to Settings-General-Application Manager and swipe from the right to the left and then check whatever app you want to move the data to the external SD card
SDK Manager from REBELLOS is useful for developers only
Folder Mount is useful only if you have games that require you install their massive data to the internal SD card and you don't have enough space.
And as a small piece of advice, clarify stuff; "13 GB of 16GB in use" might mean two things: 13/16gb used or 13/16gb free.
Hope my 'small' post helps you.
Click to expand...
Click to collapse
Hi Alexander , "small post" ..... => thank you :good:
Clarify 1 to 3 = ok.
Clarify 4 = This S3 is brand new with 2 years of warranty.
Thank you for the rest, but I will give my two S3-LTE to a pro - he will do the job. It have already spend too much time for this.
There are so many "if", "maybe", "test this" and "be aware off" so that I think that someone with knowledge will to the job over an evening.
But one last thing I would like to add: "Profit ???"
- I bought an S3 because I have a crandle for the S3 in my car.
- I bought an LTE because I use it very often as hotspot with my laptop. (this works perfect). In this aspect the S3-LTE is much faster than the standard S3.
- I could not find any S3-LTE with an internal memory bigger than 16 GB.
I already use the "Settings-General-Application Manager " and switched all apps to external memory card - if possible. But this does not really do a lot.
My internal memory uses 13 GB from 16 GB available (read directly after reboot) so there is only 3GB available and I get error messages that there is not enough memory available if I have too many programs open.
=> Therefore I would like to use the external memory card (64GB SD-CARD) for whatsapp, dropbox,... with app and data. And for this I need the SuperSU or something similar.
Thank you for your help and clarification.
Erich

[PATCH]**Adoptable storage enabler** MARSHMALLOW

As you may all know Samsung disabled the Adoptable storage function. Even the well known S7 hack doesn't work on some Samsung devices.
Well now it's back...
Thanks to some legwork (no pun intended) by @longshanks197 we now have a workable solution.
I have created this patch to fix the issue by patching the boot image and replacing sm.jar in system.
This will enable the adoptable storage feature in Settings>Storage
This should work for pretty much any Samsung device running Marshmallow
I advise making a backup with TWRP before proceeding.
NOTE: Due to Samsung's modifications the combined storage capacity may show as incorrect, ignore this and pay attention to the separate internal and external capacity which is correct.
INSTALL:
Copy the zip below to your device then install with TWRP.
adoptable_storage_enabler_ashyx
For information how to enable adoptable storage see the guide below:
how-to-use-adoptable-storage-on-android-6-0-marshmallow
This may also be worth a read for more info:
guidelines_for_marshmallow_users_formatting/
DONATE ME HERE IF YOU WANT TO BUY ME A BEER OR HIT THE THANKS BUTTON IF I HELPED YOU
.
Nice job!
I'll flash it tomorrow.
It works!!!
Thanks!!!
ashyx said:
As you may all know Samsung disabled the Adoptable storage function. Even the well known S7 hack doesn't work on some Samsung devices.
Well now it's back...
Thanks to some legwork (no pun intended) by @longshanks197 we now have a workable solution.
I have created this patch to fix the issue by patching the boot image and replacing sm.jar in system.
This will enable the adoptable storage feature in Settings>Storage
This should work for pretty much any Samsung device running Marshmallow
I advise making a backup with TWRP before proceeding.
NOTE: Due to Samsung's modifications the combined storage capacity may show as incorrect, ignore this and pay attention to the separate internal and external capacity which is correct.
INSTALL:
Copy the zip below to your device then install with TWRP.
adoptable_storage_enabler_ashyx
For information how to enable adoptable storage see the guide below:
how-to-use-adoptable-storage-on-android-6-0-marshmallow
This may also be worth a read for more info:
guidelines_for_marshmallow_users_formatting/
DONATE ME HERE IF YOU WANT TO BUY ME A BEER OR HIT THE THANKS BUTTON IF I HELPED YOU
.
Click to expand...
Click to collapse
Sorry to post this whole thread again, but an easier way for beginners is to use the Root Essentials tool in the Google Play Store.
The link for the Root Essentials application.
I have personally used this on my own Samsung Device which runs on Marshmallow so far.
ParadoXGodzillA said:
Sorry to post this whole thread again, but an easier way for beginners is to use the Root Essentials tool in the Google Play Store.
The link for the Root Essentials application.
I have personally used this on my own Samsung Device which runs on Marshmallow so far.
Click to expand...
Click to collapse
It doesn't work or didn't work(until I released this patch) on all Samsung devices. It also requires a rooted device.
Also how do you propose as easier, what is easier than flashing a zip in recovery?
Also please stop spamming my threads.
ashyx said:
It doesn't work or didn't work(until I released this patch) on all Samsung devices. It also requires a rooted device.
Also how do you propose as easier, what is easier than flashing a zip in recovery?
Also please stop spamming my threads.
Click to expand...
Click to collapse
Sorry if I have spammed your threads by reposting what you have already said or stuff you have released, but I have tried the Root Essentials method on about ten Samsung Devices. It does require a rooted device which is actually true. But flashing a device will require a custom recovery because Samsung Stock Recoveries cannot actually process these flash files by itself. So, one way or another, you will have a custom firmware running even though you just want to have adoptable storage.
ParadoXGodzillA said:
Sorry if I have spammed your threads by reposting what you have already said or stuff you have released, but I have tried the Root Essentials method on about ten Samsung Devices. It does require a rooted device which is actually true. But flashing a device will require a custom recovery because Samsung Stock Recoveries cannot actually process these flash files by itself. So, one way or another, you will have a custom firmware running even though you just want to have adoptable storage.
Click to expand...
Click to collapse
Here's the flow:
Root essentials - Twrp>root>install root essentials>run app
Adoptable patch - TWRP> install patch
Also as I already stated, even if it does work now(after releasing this patch), root essentials only originally worked for Samsung S7 devices and not for most other Samsung devices.
ashyx said:
Here's the flow:
Root essentials - Twrp>root>install root essentials>run app
Adoptable patch - TWRP> install patch
Also as I already stated, even if it does work now(after releasing this patch), root essentials only originally worked for Samsung S7 devices and not for most other Samsung devices.
Click to expand...
Click to collapse
Ok, I got it.
Even though the Root Essentials method is a longer way of doing it, there is a lot of features to it. I'm just saying this because the guy who made this application, actually took some time and I'm trying to get his work to be known that he at least tried to do something for Samsung users.
On my Samsung TAB A 8 with the latest patches, I was able to use the built-in GUI to choose between adopting the SD as internal memory or treating it as external storage. I was also able to use the sm commands to place in "mixed 50" mode so that I can have both internal memory and external storage.
isketerol said:
On my Samsung TAB A 8 with the latest patches, I was able to use the built-in GUI to choose between adopting the SD as internal memory or treating it as external storage. I was also able to use the sm commands to place in "mixed 50" mode so that I can have both internal memory and external storage.
Click to expand...
Click to collapse
Without using any patches or apps?
100% stock. No patches or apps
isketerol said:
100% stock. No patches or apps
Click to expand...
Click to collapse
So you're saying Samsung are now including adoptable storage as standard?
I have not seen this news posted anywhere. [emoji55]
What is the build number of this firmware?
Is this true they added adoptable storage in the stock firmware??
Only certain stock Tab As have this capability. The T580 for example does not have it.
OK. Here are the details:
Model: SM-T350
Version: Android 6.0.1
Security Patch: November, 2016
Kernel: 3.10.49-9331721
Build: MMB29M.T350XXu1BPL1
SE: SEPF_SECMOBILE_6.0.1_0030
Security Software: ASKS v1.2_161011
KNOX 2.6
This is a completely stock Samsung TAB A 8 that I bought within the last three weeks. It received all of the updates as OTA.
I have inserted a Sandisk Ultra 128 GB micro-SDXC card. I used the "sm" tools to split it into 64 GB Internal storage and 64 GB external storage. The storage wizard recognized this as "new" cards and allowed me to manage the storage.
To test this, I have downloaded all of the TellTales games I have bought with all of their episodes. They are starting to fill the adopted SD partition. All of them are running fine.
isketerol said:
OK. Here are the details:
Model: SM-T350
Version: Android 6.0.1
Security Patch: November, 2016
Kernel: 3.10.49-9331721
Build: MMB29M.T350XXu1BPL1
SE: SEPF_SECMOBILE_6.0.1_0030
Security Software: ASKS v1.2_161011
KNOX 2.6
This is a completely stock Samsung TAB A 8 that I bought within the last three weeks. It received all of the updates as OTA.
I have inserted a Sandisk Ultra 128 GB micro-SDXC card. I used the "sm" tools to split it into 64 GB Internal storage and 64 GB external storage. The storage wizard recognized this as "new" cards and allowed me to manage the storage.
To test this, I have downloaded all of the TellTales games I have bought with all of their episodes. They are starting to fill the adopted SD partition. All of them are running fine.
Click to expand...
Click to collapse
Does the combined storage report correctly?
Can you post a couple of screen shots?
if you have root, then Link2SD seems just about as good as adoptable.
My options without rooting? (T580) I am reluctant to root as I will lose updates.
chemie99 said:
if you have root, then Link2SD seems just about as good as adoptable.
My options without rooting? (T580) I am reluctant to root as I will lose updates.
Click to expand...
Click to collapse
You can still install updates via odin.
ashyx said:
You can still install updates via odin.
Click to expand...
Click to collapse
Except there is no source I have found of the stock firmwares.
chemie99 said:
Except there is no source I have found of the stock firmwares.
Click to expand...
Click to collapse
It's EVERYWHERE, sammobile, Samsung updates, samfirmware, updato to name a few!

OTG: TabS2 T810, rooted, 'aftermarket' stock Android 7.0 flashed, otg doesn't work

the title pretty well describes it. I've also disabled knox and have set SELinux to permissive.
symptom: plug in otg cable, put on thumb drive....nothing. search in file manager - nothing.
I've messed with, er, personalized the tablet and honestly can't recall all I've done, but USB OTG once worked and now doesn't. I've played with many of the 'troubleshooter' apps from the store [all useless, IMO, because all they say is yes or no].
Kernel support is there but no devices are recognized. The .xml file is present in system/etc/permissions or whatever the correct path is.
I've tried 2 different OTG cables and two different thumbdrives.
I've tried with selinux permissive and enforcing
I've rebooted both with and without the otg usb drive attached.
where can i look? are there any troubleshooting tools that give actual information?
i'm reasonably intelligent (PhD in physics) but not all that savvy with android (which, btw, i hate ) but i was once a unix sysadmin, so i fear no cli.
device is rooted, twrp installed if i recall correctly. completely unwilling to change kernels (unless there's a stock 7.1 or 8 )
thoughts? suggestions?
<rant>
[why do i hate android? why take a Ferrari and fix it so it will only go 50 mph? this is powerful hardware and software, but we're all treated like little children with no root control, hoops to jump through to change selinux, Samsung's god-awful knox, etc. etc. And android networking needs to get out of the 80s. DOS/Novell was better. i want to share drives from my tablet, and i want to mount drives from my PC so the contents are as available as the internal memory.]
</rant>
Using N4N 1.3 kernel with stock I6, TWRP, rooted using Magisk and OTG working flawless in my T810.
Read the changes: https://forum.xda-developers.com/tab-s2/development/kernels-n4n-i6-i5-710-715-810-815-t3700601

[ROM][Pie] Unofficial LineageOS 16.0

This is an unofficial build of LineageOS 16.0 for the Motorola razr I, (XT890/SMI).
Lots of thanks to Hazou. This rom is based on his los-14 rom and I got help from him with los-16.
This rom has full hardware support and should run stable. It has been tested by me in daily use. I'm using the rom without google apps, but with microg. Installing google apps requires some apps to move to data partition because of limited system size. See install description for more info.
Special Features
-All features of Hazous 14.1 rom
-MicroG signature spoofing patch is included.
-Adaptive icons can be disabled in homescreen settings.
I can include more features if requested
Known Bugs
-The camera preview image sometimes shakes at random
Download
https://mega.nz/#F!5fBWlIAQ!Jlq9Bj789iJ0iIIptK00tg
Update
If you already run an earlier version of this rom, just boot to twrp and install the latest flashable zip file
Install
1. Backup everything you don't want to loose.
2. Download and install TWRP 3.2.3 (download in attachments. Can be flashed with fastboot or with another recovery)
3. If you come from another rom do a full wipe with twrp
4. Download and install the rom flashable zip (download from mega.nz link is in section download)
5. If you want to install opengapps or need system partition space for other things. Install the move_to_data.zip file from the attachments. This will move the Webview and the LatinIME app to data partition.
6. Choose one of the following options:
-either install google apps (download form https://opengapps.org/. Choose x86 9.0 nano or pico)
-or install MicroG (can be installed with the unofficial installer https://forum.xda-developers.com/android/development/microg-unofficial-installer-t3432360) this is lighter in ram and cpu usage but you will get problems with google chrome and other apps
7. If you want root access install the addonsu-16.0-x86.zip (download in the attachments)
8. Reboot the phone. First reboot will take some time
Changelog
Code:
20191018:
fixed problem with sms receiving
20191012:
mobile network connection works now after boot
Fixed problems with network switching
Show taps option is working now
intel art extension enabled
Call recording enabled
text relocation warnings disbaled
(untested) encryption. Needs special configuration (see below)
20190819:
SELinux is now enforcing
Notification access feature enabled
solved crashes with houdini emulated apps
20190713:
usb configuration works properly
battery light works now
July security patches
20190704:
first stable release of this rom
DATA Encryption
If you want to enable data encryption this would break the pds partition backup. To prevent this, the cache partition can be used as backup location:
-edit /system/bin/pdsbackup.sh
-change PDS_FILE=/data/misc/pds/pdsdata.img to PDS_FILE=/cache/misc/pds/pdsdata.img
-resize data partition in TWRP:
Code:
umount /data
umount /sdcard
e2fsck -f /dev/block/mmcblk0p17
resize2fs /dev/block/mmcblk0p17 1367079
-reboot the phone
XDA:DevDB Information
unonfficial LineageOS 16.0, ROM for the Motorola RAZR i
Contributors
julianwi, Hazou
Source Code: https://github.com/julianwi/android_device_motorola_smi/tree/lineage-16.0
ROM OS Version: 9.x Pie
ROM Kernel: Linux 3.0.x
Based On: LineageOS
Version Information
Status: Stable
Stable Release Date: 2019-08-19
Created 2019-07-04
Last Updated 2019-08-19
This if I did not expect it, I'll try to see how it goes. Thank you.
Download links and install description are up now. Download from mega.nz because xda download section is broken at the moment. I'm waiting for your test reports
It's really great works, thank you!!
I quickly tried and found several points.
- USB connection with PC
All USB connection option including File Transfer, USB tethering, PTP are grayed out.
Disabling/Enabling android debug in setting didn't work.
- Wifi with storage encryption
When you enable storage encryption, WiFi always become disabled, not be able to enable.
Just FYI, it required deleting /system/bin/pdsbackup.sh AND reducing partition size of 'data' (/dev/block/mmcblk0p17).
- SElinux
Although it is designated as permissive in device.mk, it's actually worked as "disabled".
I'm not sure it's related or not, however, when building "user build", it's failed with "ERROR: permissive domains not allowed in user builds".
I know "user build" is not officially supported in Lineage release, however, it's really helpful if we can do it for AFW usage.
Previously I could use Lineage 14.1 smi build for AFW and safetynet app with user build.
BTW, performance is really great, seems to be almost same as Lineage 11.
dumkm said:
It's really great works, thank you!!
I quickly tried and found several points.
- USB connection with PC
All USB connection option including File Transfer, USB tethering, PTP are grayed out.
Disabling/Enabling android debug in setting didn't work.
Click to expand...
Click to collapse
I also noticed that. Will see how this can be fixed. It is just a problem with the option dialog. Usb connection works fine. As a workaround you can set a default USB configuration in developer options
dumkm said:
- Wifi with storage encryption
When you enable storage encryption, WiFi always become disabled, not be able to enable.
Just FYI, it required deleting /system/bin/pdsbackup.sh AND reducing partition size of 'data' (/dev/block/mmcblk0p17).
Click to expand...
Click to collapse
I have not tested storage encryption yet. Will have a look at it later
dumkm said:
- SElinux
Although it is designated as permissive in device.mk, it's actually worked as "disabled".
I'm not sure it's related or not, however, when building "user build", it's failed with "ERROR: permissive domains not allowed in user builds".
I know "user build" is not officially supported in Lineage release, however, it's really helpful if we can do it for AFW usage.
Previously I could use Lineage 14.1 smi build for AFW and safetynet app with user build.
Click to expand...
Click to collapse
I think lineage trust doesn't differentiate between permissive and disabled. Selinux support is planned for future releases
Thank you for quick check.
Regarding USB connection, I also confirmed that Ubuntu can recognize as external storage with above option, besides Windows still does not recognize. Maybe depending on my environment.
Also I noticed that Chrome, Chrome Beta and Chrome Canary (therefore another Chrome based apps such as Maps Go) always crash. This is also maybe my environment only, though. BTW, I could install MicroG, besides couldn't install OpenGapps 9.0 pico due to partition size limit.
Additionally, I couldn't find any LED settings, currently LED is always off during charge or any notification.
dumkm said:
Thank you for quick check.
Regarding USB connection, I also confirmed that Ubuntu can recognize as external storage with above option, besides Windows still does not recognize. Maybe depending on my environment.
Also I noticed that Chrome, Chrome Beta and Chrome Canary (therefore another Chrome based apps such as Maps Go) always crash. This is also maybe my environment only, though. BTW, I could install MicroG, besides couldn't install OpenGapps 9.0 pico due to partition size limit.
Additionally, I couldn't find any LED settings, currently LED is always off during charge or any notification.
Click to expand...
Click to collapse
Notification Led should work. Can be configured under settings->apps and notifications->notifications->notification light. I don't know what happened with the battery light. It will hopefully come back if I upgrade the driver to hidl.
Google Chrome is a known problem with MicroG. It requires official gapps. I will check if some of the unprivileged lineage apps can be moved to data partition to make place for google apps
Newbie question
Hi all, I know someone who's selling her old RAZR i XT890 and I'm interested (for experimental reasons but also the oddity that it's Intel powered). I've never owned a RAZR i so I've got some questions:
-The phone is from 2012 so quite old and has 1GB RAM, does it work well with this Lineage 16? Because usually newer software would perform bad on older SoC (I used to have iOS 7 on iPhone 4 back in the day and it was painfully slow compared to 6).
-On Lineage 16, can it run any Android app as a standard new Android Pie phone? I ask because this is an Intel x86 CPU, so can it still run Android apps as normal or are most of them only designed for ARM and therefore unusable?
If I get the good news, I may buy the phone and try this Lineage OS custom ROM.
Regarding LED, maybe it became working after modifying some option of notification light. Battery connection light is still always off.
Regarding opengapps, I moved webview and LatinIME from app directory to external SD in TWRP, then installed as normal app after system boot. Webview worked fine besides LatinIME always crash. I'm using different IME, so it's no problem. With this environment, opengapps nano can be installed, then Chrome, Maps and other google apps worked.
dumkm said:
Regarding LED, maybe it became working after modifying some option of notification light. Battery connection light is still always off.
Regarding opengapps, I moved webview and LatinIME from app directory to external SD in TWRP, then installed as normal app after system boot. Webview worked fine besides LatinIME always crash. I'm using different IME, so it's no problem. With this environment, opengapps nano can be installed, then Chrome, Maps and other google apps worked.
Click to expand...
Click to collapse
That's good. Than we can make a flashable zip to automatically move and symlink them to data partition.
I will provide a new build till end of the week with improved usb and notification LED implementation. I already got it working in my local setup
flameseewa said:
Hi all, I know someone who's selling her old RAZR i XT890 and I'm interested (for experimental reasons but also the oddity that it's Intel powered). I've never owned a RAZR i so I've got some questions:
-The phone is from 2012 so quite old and has 1GB RAM, does it work well with this Lineage 16? Because usually newer software would perform bad on older SoC (I used to have iOS 7 on iPhone 4 back in the day and it was painfully slow compared to 6).
-On Lineage 16, can it run any Android app as a standard new Android Pie phone? I ask because this is an Intel x86 CPU, so can it still run Android apps as normal or are most of them only designed for ARM and therefore unusable?
If I get the good news, I may buy the phone and try this Lineage OS custom ROM.
Click to expand...
Click to collapse
Newer android versions have been designed while keeping low ram devices in mind. Ram hungry special features like the picture in picture mode are excluded from builds for older device. So the situation is much better then on iOS. But a newer phone would run better thought.
Most android apps are available for x86. But some are still arm only and get automatically emulated. The intel houdini emulator integrates these apps natively into the system but they are a bit slower then x86 apps. These are for example Skype and a few unity based games
julianwi said:
Newer android versions have been designed while keeping low ram devices in mind. Ram hungry special features like the picture in picture mode are excluded from builds for older device. So the situation is much better then on iOS. But a newer phone would run better thought.
Most android apps are available for x86. But some are still arm only and get automatically emulated. The intel houdini emulator integrates these apps natively into the system but they are a bit slower then x86 apps. These are for example Skype and a few unity based games
Click to expand...
Click to collapse
Thanks for the response. So I should be alright with it then, hopefully. I just hope it won't lag on that old SoC. I'd love if you could upload a quick video of it in action.
TWRP error 70
julianwi said:
This is an unofficial build of LineageOS 16.0 for the Motorola razr I, (XT890/SMI).
Lots of thanks to Hazou. This rom is based on his los-14 rom and I got help from him with los-16.
This rom has full hardware support and should run stable. It has been tested by me in daily use. I'm using the rom without google apps, but with microg. I don't know how smooth it runs with official gapps.
Special Features
-All features of Hazous 14.1 rom
-MicroG signature spoofing patch is included.
-Adaptive icons can be disabled in homescreen settings.
I can include more features if requested
Known Bugs
-Mobile cell connection doesn't connect after boot. You have to turn airplane mode on and off to let it work.
-selinux is set to permissive for now (reduced security)
Please report more bugs if you test this rom
Install
1. Backup everything you don't want to loose.
2. Download and install TWRP 3.2.3 (download in attachments. Can be flashed with fastboot or with another recovery)
3. If you come from another rom do a full wipe with twrp
4. Download and install the rom flashable zip (download from mega.nz https://mega.nz/#!ICwXRC6D!VZqe3o5zeWbmMiZvka_BtUTW5T_V7_OdMS57Oe9CbMk)
5. Choose one of the following options:
-either install MicroG (can be installed with the unofficial installer https://forum.xda-developers.com/android/development/microg-unofficial-installer-t3432360)
-or install google apps (download form https://opengapps.org/. Choose x86 9.0 pico)
6. If you want root access install the addonsu-16.0-x86.zip (download in the attachments)
7. Reboot the phone. First reboot will take some time
XDA:DevDB Information
unonfficial LineageOS 16.0, ROM for the Motorola RAZR i
Contributors
julianwi, Hazou
Source Code: https://github.com/julianwi/android_device_motorola_smi/tree/lineage-16.0
ROM OS Version: 9.x Pie
ROM Kernel: Linux 3.0.x
Based On: LineageOS
Version Information
Status: Stable
Stable Release Date: 2019-07-04
Created 2019-07-04
Last Updated 2019-07-05
Click to expand...
Click to collapse
I've installed the OS without problems, but when i try to get GApps Pico or any other version TWRP prompt error 70. How should i proceed? There is any additional configuration needed?
Kazvko said:
I've installed the OS without problems, but when i try to get GApps Pico or any other version TWRP prompt error 70. How should i proceed? There is any additional configuration needed?
Click to expand...
Click to collapse
Yes, system partition size is limited on this phone. To install GApps some files need to be moved to data partition.
I created a flashable zip to automate this process. Take a look at the modified install description in the first post
New build is up now.
flameseewa said:
Thanks for the response. So I should be alright with it then, hopefully. I just hope it won't lag on that old SoC. I'd love if you could upload a quick video of it in action.
Click to expand...
Click to collapse
Sorry don't have enough time to make a video in the near future. Maybe someone else can record a video of it
I could confirm that notification LED and USB storage works fine with lineage-16.0-20190713-UNOFFICIAL-smi. Thanks.
Still WiFi with storage encryption does not work.
julianwi said:
New build is up now.
Sorry don't have enough time to make a video in the near future. Maybe someone else can record a video of it
Click to expand...
Click to collapse
Alright, thanks. I bought my friend's RAZR i and I am planning to use it as a daily driver with this ROM (I'm a light user anyway), I can't thank you enough for making this LineageOS for such an old device. I wonder if such a recent Lineage has been developed for the 2011 Atrix, haven't seen one.
I have questions though, firstly I've never used a custom ROM before, can I simply follow the instructions on this thread to get it working, or is there anything that has to be done beforehand like rooting? Secondly, are any other OSs successfully booting on this x86 phone, as I can't find it on XDA? (it surprisingly hasn't gotten much attention as a hackable device like HTC HD2 or Nokia N900 got).
dumkm said:
I could confirm that notification LED and USB storage works fine with lineage-16.0-20190713-UNOFFICIAL-smi. Thanks.
Still WiFi with storage encryption does not work.
Click to expand...
Click to collapse
I know, haven't looked at the storage encryption for now. It will maybe be in the next update next month
flameseewa said:
Alright, thanks. I bought my friend's RAZR i and I am planning to use it as a daily driver with this ROM (I'm a light user anyway), I can't thank you enough for making this LineageOS for such an old device. I wonder if such a recent Lineage has been developed for the 2011 Atrix, haven't seen one.
I have questions though, firstly I've never used a custom ROM before, can I simply follow the instructions on this thread to get it working, or is there anything that has to be done beforehand like rooting? Secondly, are any other OSs successfully booting on this x86 phone, as I can't find it on XDA? (it surprisingly hasn't gotten much attention as a hackable device like HTC HD2 or Nokia N900 got).
Click to expand...
Click to collapse
If the phone never had a custom rom yet, you have to unlock the bootloader first. Description is in this thread: https://forum.xda-developers.com/showthread.php?t=1928551
julianwi said:
If the phone never had a custom rom yet, you have to unlock the bootloader first. Description is in this thread: https://forum.xda-developers.com/showthread.php?t=1928551
Click to expand...
Click to collapse
That's an old guide, will everything still work?
flameseewa said:
That's an old guide, will everything still work?
Click to expand...
Click to collapse
Yes, it should still work the same. If some links are outdated you can google them yourself
Thank you for bringing my old RAZR i back to life! I really appreciate the time and effort you spent for this obselete phone. Looking forward for more updates and for a bug free ROM. Using it now
dumkm said:
- Wifi with storage encryption
When you enable storage encryption, WiFi always become disabled, not be able to enable.
Just FYI, it required deleting /system/bin/pdsbackup.sh AND reducing partition size of 'data' (/dev/block/mmcblk0p17).
Click to expand...
Click to collapse
I'm not sure if I misunderstood but when you said "it required deleting....." and "reducing partition size of data", did you mean you can get WiFi to work if you do those things? I'm no expert at these but I can atleast apply the "fix" (if it really is) given that you guide me, if it's okay with you. Thanks!

Categories

Resources