Omni Rom build #10 USB mass storage issue!!! - HTC Pico (Explorer)

I don't think it will work for all, just try and see. :laugh:
story:
I've just flash the new build of omni rom and i notice that the mass storage is not working,so I search app for alternative............. just found Multi Mount SD-card Lite on Playstore, well..... it works.
so here's the Instruction to activate USB mass storage on OMNI rom build #10:
and see attachment.
1. Download Multi Mount SD-card Lite on Playstore and install
2. Allow root permission.
3. Check MTP fix.
4. Reboot. done.
(bad eng)
Press thanks if i help :good:

ayan_feo04 said:
I don't think it will work for all, just try and see. :laugh:
story:
I've just flash the new build of omni rom and i notice that the mass storage is not working,so I search app for alternative............. just found Multi Mount SD-card Lite on Playstore, well..... it works.
so here's the Instruction to activate USB mass storage on OMNI rom build #10:
and see attachment.
1. Download Multi Mount SD-card Lite on Playstore and install
2. Allow root permission.
3. Check MTP fix.
4. Reboot. done.
(bad eng)
Press thanks if i help :good:
Click to expand...
Click to collapse
no need of app
go to settings>storage>USB computer connection>tick mass storage

I'm not sure multi-mount would be required. I've already posted why MTP doesn't work in build #10 and how it can be fixed & also why I wouldn't focus on supporting UMS.
MTP will be fixed in next build, and you can setprop till the next build is released.
Also, as far as the second post in this thread is concerned, this is/was not intended for CM11.

Related

[recovery] CWM for Betelgeuse v0.3 - Now with USB support

I have made some modifications to the famous ClockworkMod recovery that enable to chose internal storage or sd-card for backup and flashing. I think this is quite useful. I also want to try to add usb-drives to this list, but that will take some more coding.
The source code is availlable in my gihub.
WARNING: USB does not seem to be hotplugable. Plug before boot and don't remove till reboot. I managed to get a complete lockup (had to remove battery to get out) by not obeying this.
USB Disk must have exactly one vfat partition.
Download v0.3:
Image file
update.zip (flash with ClockworkMod as included in CM7)
Changelog
v0.3
- Add USB support
v0.2
- Based on ClockworkMod Recovery v3.0.2.8
- Add menu items to chose sd or internal drive
Your idea is great and keep up!!! I'll flash your recovery when its become more stable. I just make it usable after lots of problems and I want to brick it again. I think you understood me.
Sent from my Folio 100 using Tapatalk
Dual boot command in CWM possible ?
MBlaster
First of all, thank you for your work and efforts.
Since you seem to be familiar with adding features to CWM, I have one question : would it be possible to add a menu-entry for choosing an alternative boot (like for example ubuntu installed on a SD-Card ...) ?
Regards,
eRaph
v0.3
- Add USB support
Have Fun!
mblaster said:
I have made some modifications to the famous ClockworkMod recovery that enable to chose internal storage or sd-card for backup and flashing. I think this is quite useful. I also want to try to add usb-drives to this list, but that will take some more coding.
The source code is availlable in my gihub.
WARNING: USB does not seem to be hotplugable. Plug before boot and don't remove till reboot. I managed to get a complete lockup (had to remove battery to get out) by not obeying this.
USB Disk must have exactly one vfat partition.
Download v0.3:
Image file
update.zip (flash with ClockworkMod as included in CM7)
Click to expand...
Click to collapse
Thanks for this job. Just a question: what is the procedure for recovery update ? I start with a stock rom rooted and with recovery from foliomod1.4 installed via ADB.
Thanks
miazza
Hello to everybody. I need this recovery but the links are boken. can someone help by reaupload or send as PM.
Thanks

[ROM] CyanogenMod 9 for LG Optimus Net (P690)

This is CyanogenMod 9 created by me
What works:
- everything
What doesn’t work:
- Offline charging (can't work good)
- Camera
- Youtube HQ
- Funny sim (can't be fixed)
Gapps:
http://goo.im/gapps/gapps-ics-20120429-signed.zip
Rom:
http://lgics.altervista.org/
Source device folder: https://github.com/lgics/cm_device_lge_p690
Screenshoots:
Thanks:
diogobuique for donate me money for buy the phone
lupohirp for source of cm9 for optimus one
adfad666 for help with cm9
Code Aurora Forum for kernel
Cyanogenmod team
Prerequisites:
Back up your contents of the sd card to PC
Root your phone
Install a recovery Clockworkmod
enter in recovery
Enable USB-MS toggle: Copy ROM.zip and GAPPS.zip
Disable USB-MS
Skip to the Installation section
Installation:
Enter recovery
Make a nandroid back up
Make full wipe (except wipe sd) for the first time installation
Flash from ZIP: Select ROM and reboot
Flash GAPPS and reboot
Have fun!
I heard that you could fix bt and cam by adding files to \system?
need other thing to do that add file on /system
markolino631 said:
need other thing to do that add file on /system
Click to expand...
Click to collapse
How? could you be a bit more specific??
We really need the camera especially for us IG users. My phone is useless without a cam.
Sent from my LG-P690 using xda premium
And how do i know if my sim is a funny sim?
Thanks
need the right libcamera for the camera! is funny sim if the telephone doesn't read you sim
markolino631 said:
need the right libcamera for the camera! is funny sim if the telephone doesn't read you sim
Click to expand...
Click to collapse
how will it be done???
vicfirth_23 said:
how will it be done???
Click to expand...
Click to collapse
If we will not have a developer that will work on this phone this phone will be only a good phone with stock rom guys
if i have this phone i should be fix the errors first but i don't have this phone...
Ready to help.
@Marko If you can fix this rom we can check out the bugs.......
markolino631 said:
Cyanogenmod 9, Android ICS 4.0.4, My kernel modified! All for the LG Optimus Net (P690)
What works:
- Full H/W acceleration with new adreno drivers, 3D (yamato)
- Calls, SMS, MMS, 3G/2G, Mobile data
- Wireless, Bluetooth tethering
- Data limit, IPv4, IPv6
- Stereo audio, headset
- GPS, Sensors, Lights, Touch screen
- Usb Mass storage, Usb debugging
- Browser, GMail, GPlay
What doesn't work:
- Wifi tethering & USB tethering, Offline charging: needs usb driver update from 3.0 kernel
- FM Radio: not implemented in CM yet
- Youtube HQ: needs OpenMaX(omx) libraries for armv6
- Camera
- Funny SIM (128k USIMs)
- Bluetooth
Releases aren't usefull for daily usage if you want to use camera and bluetooth.
It is almost fast!
Download rom: http://www.mediafire.com/?2vp9425z39hto4b
Screenshoots:
Thanks:
lupohirp for source of cm9 for optimus one
adfad666 for help with cm9
Code Aurora Forum for kernel
Cyanogenmod team and Android for ICS and for kernel .35 for chic
Prerequisites
Back up your contents of the sd card to PC
Root your phone
Install a recovery Clockworkmod
enter in recovery
Enable USB-MS toggle: Copy ROM.zip and GAPPS.zip
Disable USB-MS
Skip to the Installation section
Installation
Enter recovery
Make a nandroid back up
Make full wipe (except wipe sd) for the first time installation
Flash from ZIP: Select ROM and reboot
Flash GAPPS and reboot
Have fun!
Click to expand...
Click to collapse
Thanks marko....Admire your works....hope you will clear the bugs soon....nice to see you here....
Marko, I flashed the ROM on first page but it freezes on the boot logo, pls help.
you have done all wipe? wipe all and mount /system format /system?
markolino631 said:
you have done all wipe? wipe all and mount /system format /system?
Click to expand...
Click to collapse
Yes Marko, all your previous versions I was able to flash successfully but not this one.
it's strange! for other works
markolino631 said:
it's strange! for other works
Click to expand...
Click to collapse
I was able to install it properly now. I redownloaded the rom. Previous one was corrupt.
Corrupted?
amolebirje1982 said:
I was able to install it properly now. I redownloaded the rom. Previous one was corrupt.
Click to expand...
Click to collapse
Which is the corrupted one?
abhishek046 said:
Which is the corrupted one?
Click to expand...
Click to collapse
no, I mean the file I downloaded earlier it was not completely downloaded. I redownloaded and then flashed, no problems then.

[hltexx][hlte][CWM Advanced Edition] PhilZ Touch

Main thread + features + install instructions + dev support
http://forum.xda-developers.com/showthread.php?t=2201860
PhilZ Touch is a CWM Advanced Edition that adds all the features you could ever miss in CWM
It is a well proven recovery for many phones
It also adds a full touch interface a completely configurable GUI
Please give your feedback, what works, and any bug you could encounter
Read the features, and check if you are missing something
Also, do not forget to read about the powerful aroma file manager integration and double tap shortcut
Download links
Last version can be found here:
Galaxy Note 3 LTE International
Now: one common recovery for all: hlte
http://goo.im/devs/philz_touch/CWM_Advanced_Edition
The below specific variants are no more updated, use hlte common variant
- hltexx
For older bootloader, use versions before 6.13.0
Click to expand...
Click to collapse
Big thanks to @eybee1970 for the first flash
To @Chenglu for guide in dtbTool + support in fixing mount usb storage
To TeamWin for the primitive device tree
To @wanam for his help in compiling kernels
Reserved
Info:
Kernel compiled from sources update3
No sensors flashing: fast boot in recovery
Root allowed
Selinux enforced mode preserved
Built in NTFS/Exfat kernel module support for fast backups
Recovery: based on cm-11.0 kitkat branch
More info:
At worst, it would bootloop and you have to know how to get out of a bootloop, that's it
But you're still warned: Read Post 1
Credits to @Chenglu for parts of the ramdisk
Can you build a version for SM-N9005 hlte?
regards
Great your here! Best recovery option! Now can you get some of your buddies to push us an aosp rom??
Sent from my SM-N9005 using XDA Premium 4 mobile app
First, someone has to flash it so that we debug it
The risks are a boot hand so you need odin to flash another recovery
Either selinux missing permissions I will add later or needed graphics.c
Waiting for feedback
Yay \(^o^)/
I've been waiting for you Phil
Welcome
Sent from my Note 3 powered by Omega v4.0
Vocaloid fan? Check out this thread!
cool to see you here, mate
EDIT: ok, I flashed it
- CWM zip to flash Recovery does not work (at least for me...)
- ODIN flashable works
- CWM Touch Recovery works, no issues so far
Thx.
The warnings in post 1 are for noobs
So do not be do scared others
Phil3759 said:
The warnings in post 1 are for noobs
So do not be do scared others
Click to expand...
Click to collapse
post above yours
eybee1970 said:
cool to see you here, mate
EDIT: ok, I flashed it
- CWM zip to flash Recovery does not work (at least for me...)
- ODIN flashable works
- CWM Touch Recovery works, no issues so far
Thx.
Click to expand...
Click to collapse
Are you kidding?
It works?
LoL
Never thought on first release. This has no device tree. I built near from scratch, based on twrp broken device tree for cwm
Big thanks. I am removing noob warnings in op so that we start debugging where needed
:thumbup::thumbup:
Phil3759 said:
Are you kidding?
It works?
LoL
Never thought on first release. This has no device tree. I built near from scratch, based on twrp broken device tree for cwm
Big thanks. I am removing noob warnings in op so that we start debugging where needed
:thumbup::thumbup:
Click to expand...
Click to collapse
I have to thank you...I don't like TWRP, so I used CWM so far...but as I use Sammy Flip Cover, it is really hard to handle volume buttons....now I don't need them any more
EDIT: Thx for mentioning me in OP...but please correct my nick ...its a funny kind of my initials (A.B.) and the number behind is quite clear I guess
Phil3759 said:
Info:
Kernel compiled from sources update3
No sensors flashing: fast boot in recovery
Root allowed
Selinux enforced mode preserved
Built in NTFS/Exfat kernel module support for fast backups
Recovery: based on cm-11.0 kitkat branch
More info:
At worst, it would bootloop and you have to know how to get out of a bootloop, that's it
But you're still warned: Read Post 1
Credits to @Chenglu for parts of the ramdisk
Click to expand...
Click to collapse
Nice to see this ramping-up :good:
Obvious warning that should be added to the top post - like every single custom (non-Samsung) recovery so far, this is also tripping the Knox flag.
eybee1970 said:
I have to thank you...I don't like TWRP, so I used CWM so far...but as I use Sammy Flip Cover, it is really hard to handle volume buttons....now I don't need them any more
EDIT: Thx for mentioning me in OP...but please correct my nick ...its a funny kind of my initials (A.B.) and the number behind is quite clear I guess
Click to expand...
Click to collapse
Fixed with your correct nick
- is backup to exfat extrnal sd ok?
- mount usb storage and OTG USB?
- format usb otg in exfst/ntfs/ext4/ext2?
- boot into recovery is fast?
- time/date?
If all ok I will clean it and release other variants
Phil3759 said:
Fixed with your correct nick
- is backup to exfat extrnal sd ok?
- mount usb storage and OTG USB?
- format usb otg in exfst/ntfs/ext4/ext2?
- boot into recovery is fast?
- time/date?
If all ok I will clean it and release other variants
Click to expand...
Click to collapse
- will test backup...right now not enough free space on external sd
- usb storage mounting does not work
- won't test format
- boot in recovery is fast enough - same as before on regular CWM
- time/date not showing up correctly...for me it is 10.05 am now and it shows up 20.12 pm though I set the correct timezone
Phil3759 said:
Fixed with your correct nick
- is backup to exfat extrnal sd ok?
- mount usb storage and OTG USB?
- format usb otg in exfst/ntfs/ext4/ext2?
- boot into recovery is fast?
- time/date?
If all ok I will clean it and release other variants
Click to expand...
Click to collapse
Backup to extsdcard (fat) OK : Time 20min
Backup usb otg OK : Time 10 min
don't try format
boot in recovery speed time seem to be the same as normal cwm
time/date : in cwm I had 23h29 instead of 14h32 (I'm in france), in backup name the date is false (01_01_1970)
aromafm feature not working.
i have /aromafm/aromafm.zip in the clockworkmod folder on internal storage and sdcard...
Philz touch can´t found this folder...
"now clockworkmod/aromafm/aromafm.zip in storage paths"
i started aromafm.zip via install zip -> Choose zip from /sdcard -> clockworkmod -> aromafm -> aromafm.zip and this work it...
go in the sdcard folder ... -> empty! no data found on internal storage...
external storage is this problem too.
regards
Sakaschi
tr72 said:
Backup to extsdcard (fat) OK : Time 20min
Backup usb otg OK : Time 10 min
don't try format
boot in recovery speed time seem to be the same as normal cwm
time/date : in cwm I had 23h29 instead of 14h32 (I'm in france), in backup name the date is false (01_01_1970)
Click to expand...
Click to collapse
Many thanks
Can you verify mount usb storage on pc for external sd?
Sakaschi said:
aromafm feature not working.
i have /aromafm/aromafm.zip in the clockworkmod folder on internal storage and sdcard...
Philz touch can´t found this folder...
"now clockworkmod/aromafm/aromafm.zip in storage paths"
i started aromafm.zip via install zip -> Choose zip from /sdcard -> clockworkmod -> aromafm -> aromafm.zip and this work it...
go in the sdcard folder ... -> empty! no data found on internal storage...
external storage is this problem too.
regards
Sakaschi
Click to expand...
Click to collapse
Check data/media/0 stories in FAQ
storage set to /data/media/0 is selected....
Phil3759 said:
Many thanks
Can you verify mount usb storage on pc for external sd?
Check data/media/0 stories in FAQ
Click to expand...
Click to collapse
I can't check, I'm on mac. Try with virtual machine without success but it's not a good test.
Find an old flashdrive to try some format :
vfat : OK
extfat : OK on windows (VM), not on mac (ask to initialise the disc)
ntfs : OK
Don't have the driver to test the other.

[Recovery][OFFICIAL] TWRP 2.8.4.0

Team Win Recovery Project 2.x, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
CHANGELOG for 2.8.4.0:
-Add flashing of boot and recovery images via the TWRP GUI (Find the Images button on the Install page)
-Fix some MTP related crashes and bugs
-Eliminate TWRP toggling USB IDs during boot if MTP is enabled
-Fix various adb sideload issues
-Improve threading of actions
-Eliminate separate thread for screen timeout
-Update libblkid to 2.25.0
-Use power button as back button on watch themes for easier navigation
-Add mutex locking to data manager
-Improve custom theme handling on encrypted devices
-Allow the stock theme to be offset by build flags so we can center a lower res theme on a higher res screen especially for watches with round screens
CHANGELOG for 2.8.3.0:
-MTP will now tell the host PC that storage is removed instead of disabling MTP completely
-MTP will now report the correct max file size based on the file system in use to the host PC (may fix transfer of large files)
-Update and improve fix permissions and make fixing contexts optional
-Update SuperSU in TWRP to 2.40 and update install process
-Make TWRP work properly on AArch64 (Nexus 9 is now built in true 64-bit binaries and libraries)
-Attempt to set correct permissions and contexts on all files placed in storage so backups will show in Android
-Fix kernel panic during MTP start on some devices
-Support unicode fonts on devices with True Type Font support
-Fix slider value not showing sometimes (vibration settings page)
-Toggle MTP off during adb sideload to set correct USB IDs
-Reduce library requirements for 5.0 L decrypt
-Other minor fixes and improvements
Note: Starting with TWRP 2.8.2.0 and higher, adb sideload uses a new sideload method originally implemented in AOSP recovery. You will need the latest adb binaries to use sideload in these newer versions of TWRP. The version required is 1.0.32. You can find the version by running "adb version" on your computer. The new sideload feature no longer stores the zip on your device. Instead, a fuse file system is created in RAM and the zip is streamed from your computer. This puts less wear and tear on storage and ensures that large zips will not fill up all of your RAM. The sideload may spit an error on your PC side, but the zip should install just fine on your device.
CHANGELOG for 2.8.2.0:
-Pull in all changes from Android 5.0 lollipop into TWRP
-Add decrypt support for Android 5.0 lollipop encrypted partitions including automatic decrypt when the default_password is in use
-Revert some changes to exFAT that were breaking exFAT support on some devices
-Other minor fixes and updates
Note: At this time we do not have a GUI representation for pattern unlock. You can still decrypt patterns though by translating the pattern dots to numbers. The pattern dots correspond to numbers in the following pattern:
1 2 3
4 5 6
7 8 9
So an upper-case L would translate to a password of 14789 entered on the keyboard. Eventually we plan to add a proper pattern unlock to TWRP but it is a relatively low priority at this point.
CHANGELOG for 2.8.1.0:
-MTP fixes and improvements - you can now copy zips to the root of storage - thanks to _that
-TrueType Font support - optional as it takes up a decent amount of space so may not be available on all devices - thanks to Tassadar
-Temperature support - thanks to bigbiff
-Various other bugfixes and tweaks
Over the course of the last year or so, bigbiff has worked to migrate various Java functions from Android's MTP implementation to bring you a fully C++ based MTP implementation that allows you to transfer files to both emulated storage and Micro SD cards. It's confirmed to work on various Nexus devices but we may have to make some changes on other devices to keep Windows happy. Windows is very picky about USB IDs and its drivers. We have tested it on Windows 7 and 8 as well as Ubuntu 14.04 Trusty. MTP is enabled by default, but we do toggle it off and on automatically during certain operations such as if you choose to wipe a storage partition. You can enable or disable MTP under the mount menu in TWRP. For more about what MTP is here.
Note: Due to a weird bug with our MTP setup, you cannot copy a zip file to the root of storage with Windows. You can change the .zip to something else like .txt and then copy it to the root and rename the file back to .zip once it's copied to the device. You can also copy the zip into any subfolder.
Command line support is also now available. You can perform various OpenRecoveryScript commands via the adb shell. Depending on what you are doing you may wish to do a "twrp set tw_mtp_enabled 0" and then reboot to prevent the MTP auto toggle from killing your adb interface. You can use this option to create and restore backups, wipe, install zips, and more. Via adb shell, type twrp followed by a space then enter the OpenRecoveryScript command and hit enter. Find more OpenRecoveryScript commands here.
DEVICE TREE- link
DOWNLOAD
TWRP OFFICIAL PAGE -LINK
INSTALLATION
FOLLOW STEPS ON DOWNLOAD PAGE
BUGS
If you have found a bug, please consider posting it to our github issues log. It's pretty much impossible for us to keep up with the more than 40 threads that we have for the devices that we "directly" support. If you have a significant problem that cannot be answered in this thread, your best bet is to PM me directly, contact us via our website, or find us in our IRC channel below. If you see someone that's struggling, feel free to point it out to us. We need your help to help us keep track of all of our devices! Thanks!
SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this LINK
CREDITS @varun.chitre15 for kernel source
XDA:DevDB Information
[Recovery][OFFICIAL] TWRP 2.8.4.0, ROM for the Sony Xperia L
Contributors
Rohan purohit
ROM OS Version: 5.0.x Lollipop
Version Information
Status: Stable
Created 2015-01-27
Last Updated 2015-01-30
Reserved
RESTORING / CHANGING TO PHILZ OR IN-BUILT KERNEL RECOVERY
STEPS :
-Go to flashtool
-flash ftf ( any firmware is ok )
-(i dont want to flash complete ftf? , do as shown in attachment)
-so what have we done is just flash FOTAKERNEL partition and exclude everything else, so only twrp is wiped
-now ul have d recovery with the kernel
cheers,
Can it be merged with custom kernel? Like ThunderZap.
Why do you provide a boot image? This is not the way to go. Build a recovery image and flash it to the FOTAKernel partition (/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel) instead. Using boot images is bad, given each ROM has a different ramdisk and the kernel modules may not match, causing stuff like WiFi, BT etc to break.
Olivier said:
Why do you provide a boot image? This is not the way to go. Build a recovery image and flash it to the FOTAKernel partition (/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel) instead. Using boot images is bad, given each ROM has a different ramdisk and the kernel modules may not match, causing stuff like WiFi, BT etc to break.
Click to expand...
Click to collapse
ok thanks i'll do that asap !
Nice! Tried on CM12 Beta 6 by Varun and it boots fine and all, but it can't Wipe. It says the partitions aren't found...
Hope you can fix it and keep this project up. I think TWRP is the best recovey.
the_biu said:
Nice! Tried on CM12 Beta 6 by Varun and it boots fine and all, but it can't Wipe. It says the partitions aren't found...
Hope you can fix it and keep this project up. I think TWRP is the best recovey.
Click to expand...
Click to collapse
give me recovery log .. but i did try wipe and it had worked !
Rohan purohit said:
give me recovery log .. but i did try wipe and it had worked !
Click to expand...
Click to collapse
How do I get the Recovery's log?
In the mean time, this is what I get when try to do a Wipe: http://i.imgur.com/1TsLA9A.jpg
the_biu said:
How do I get the Recovery's log?
In the mean time, this is what I get when try to do a Wipe: http://i.imgur.com/1TsLA9A.jpg
Click to expand...
Click to collapse
Advanced > copy log to SD!! Btw it says factory reset complete d! I think it's successful , check it..
Code:
adb shell dd if=/sdcard/recovery.img of=/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel
Click to expand...
Click to collapse
You're forgot "adb su" before that, this command didn't work without root permissions.
AdvantageDD said:
You're forgot "adb su" before that, this command didn't work without root permissions.
Click to expand...
Click to collapse
Yes u need su if ur using terminal ..if PC then u don't need it!
Anyway I'll add it thanks!
Rohan purohit said:
Advanced > copy log to SD!! Btw it says factory reset complete d! I think it's successful , check it..
Click to expand...
Click to collapse
I did it and it's not. When I swipe to Wipe this message appears in 1 sec., when it should take a while to show because Wipe takes a few more than 1 sec. Also when I boot all my files and everything is still there.
I'm unable to get the log. It gets copied to the phone, but everytime I restart the file is erased. Also adb sideload is not working...
Any tip?
Rohan purohit said:
Yes u need su if ur using terminal ..if PC then u don't need it!
Anyway I'll add it thanks!
Click to expand...
Click to collapse
This is from ADB, without su it said "Permission denied".
Seems like recovery don't work with ThunderZap 4.12 - it can't mount anything. And i can't copy log to sd because sd isn't mounted.
Yes wipe bug is confirmed.. And su too.. I'm busy now so couldn't test myself.. I'll update post tmo..
Yeah guys before you do the FOTAKernel code make sure you tap "adb root" so you get permissions!
ADB and Root is on ... Permission Denied ...
jakubekw1997 said:
ADB and Root is on ... Permission Denied ...
Click to expand...
Click to collapse
Download Terminal Emulator from Play Store, then open it and type su so it get root access, then type:
dd if=/sdcard/recovery.img of=/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel
That's how I did it. It worked...
AdvantageDD said:
This is from ADB, without su it said "Permission denied".
Seems like recovery don't work with ThunderZap 4.12 - it can't mount anything. And i can't copy log to sd because sd isn't mounted.
Click to expand...
Click to collapse
I'm facing this issue as well. nothing seems to be mounted. used terminal emlator to flash fotakernel.
jakubekw1997 said:
ADB and Root is on ... Permission Denied ...
Click to expand...
Click to collapse
Try this go to Dev options and root access to both apps and adb.. And im waiting on official support wherein we'll just have to use their app to flash!
Correct command to use from adb:
Code:
adb shell
su
dd if=/sdcard/recovery.img of=/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel
Don't forget to allow "Root access" from "Apps and ADB" in "Developer Options"

[ROM][UNOFFICIAL][Oreo 8.1] AOSP Extended for Mi Mix (lithium)

I was quite disappointed to find that my favourite ROM from my old phone was not available for the Mi Mix. So I took some time to research how to compile roms and built this for the community to enjoy.
Download AEX v5.8 here: https://www.androidfilehost.com/?w=files&flid=285169
EAS version with pepsy kernel: https://androidfilehost.com/?fid=1322778262904030327
Recommended TWRP here: http://www.mediafire.com/file/lv7sncx1np9d41u/twrp-3.2.1-raupe-blunden-15.1-updated.img
Sources:
https://github.com/AospExtended
https://github.com/PsyMan47/Pepsy-Kernel
https://github.com/PsyMan47/lithium
https://github.com/PsyMan47/msm8996-common
Requires global firmware 8.8.30. Nano Opengapps is recommended, but has Webview patches so you can install any version you like.
Everything works as it should, but unfortunately I'm no developer and won't be able to do feature requests or fix bugs. That being said, if and when the main AEX code base gets updated I will provide new builds. This was mainly a project for me to learn a bit more about Linux, Github and Android in general and I provide this with no guarantees of anything.
Big thanks to Psy_Man for his device tree that enabled me to build this.
Another great rom is revived!
New build with webview patches, you can now install whatever version of opengapps you like
https://www.androidfilehost.com/?fid=1322778262903988659
Inkypen said:
New build with webview patches, you can now install whatever version of opengapps you like
https://www.androidfilehost.com/?fid=1322778262903988659
Click to expand...
Click to collapse
Noice, thanks for your efforts.
Had anyone tried this?
Is everything working?
How is the battery life?
sexlord89 said:
Had anyone tried this?
Is everything working?
How is the battery life?
Click to expand...
Click to collapse
it's working good according to some users who've tried it.
New version up, last build had some random intermittent bugs. This new version uses the same kernel as the official SD821 aex roms, so everything works exactly like official version. This has on screen nav bar by default so no messing around with settings. Nano opengapps is recommended, but has webview patches you can install any version you like.
https://www.androidfilehost.com/?fid=1322778262903989778
Can anyone tell me DOES Magisk and SystemLess Xposed Work on this rom?
I use Magisk myself, works fine. I don't use Xposed so I have no idea
Wowwwwzer nice and smooth..so far so good !! Thanks ,!!!:??
TWRP Error code 7 happened...
Why it need MiUi to install?
00hobin said:
TWRP Error code 7 happened...
Why it need MiUi to install?
Click to expand...
Click to collapse
Hi there,
I don't understand your question "Why it need MiUi to install?".
But here's the suggestion, flash this twrp and try again : http://www.mediafire.com/file/lv7sncx1np9d41u/twrp-3.2.1-raupe-blunden-15.1-updated.img
heindrix said:
Hi there,
I don't understand your question "Why it need MiUi to install?".
But here's the suggestion, flash this twrp and try again : http://www.mediafire.com/file/lv7sncx1np9d41u/twrp-3.2.1-raupe-blunden-15.1-updated.img
Click to expand...
Click to collapse
This time error code 6 happened. I attached log file
Error code 7 is assert error (device does not match) in installer script, usually down to incorrect TWRP version. Error 6 is some other error in installer script, unfortunately your attached recovery log is no longer available. Does your device have MIUI installed or you coming from a different ROM?
Inkypen said:
Error code 7 is assert error (device does not match) in installer script, usually down to incorrect TWRP version. Error 6 is some other error in installer script, unfortunately your attached recovery log is no longer available. Does your device have MIUI installed or you coming from a different ROM?
Click to expand...
Click to collapse
I'm coming from crDroid. I fully wiped except internal storage, but that error happened. I'll try again.to coming from MIUI
00hobin said:
I'm coming from crDroid. I fully wiped except internal storage, but that error happened. I'll try again.to coming from MIUI
Click to expand...
Click to collapse
Coming from CrDroid Oreo and using latest twrp (the one by raupe and blunden which file name ends with updated or some such) you should have no trouble...
00hobin said:
I'm coming from crDroid. I fully wiped except internal storage, but that error happened. I'll try again.to coming from MIUI
Click to expand...
Click to collapse
It makes no sense, if you already have crdroid installed then all the messy parts of getting rid of MIUI has already been done. If you reinstall MIUI, then it automatically encrypts storage and you will have to format (not wipe) data to move to a different ROM.
Best thing I can suggest is to wipe (not format) everything apart from internal storage. Then reboot into recovery and then try to install the ROM. I suspect error 6 might have something to do with not being able to mount /vendor partition. Make sure you have the updated raupe+blunden TWRP, I believe the official version doesnt mount /vendor as well as having touch screen issues with some variants of mi mix.
00hobin said:
I'm coming from crDroid. I fully wiped except internal storage, but that error happened. I'll try again.to coming from MIUI
Click to expand...
Click to collapse
Flash TWRP (twrp-3.2.1-raupe-blunden-15.1-updated.img) -> Boot into TWRP -> Swipe to Allow Modifications -> Cancel when TWRP asks for password -> Go To Wipe -> Press Format Data button and type YES and press enter -> Go To Wipe -> Press Advanced Wipe button -> Select all partitions except USB OTG and swipe to wipe -> Go to Mount -> Press Select Storage button and choose Internal Storage and press OK -> Press Mount USB Storage button -> Plug phone to PC -> Copy all files you want to flash from PC -> Unmount and unplug from PC -> Go to Mount -> Mount all partitions except USB OTG -> Flash all files you want to flash -> Throw the phone as far as you can -> BOOM
Inkypen said:
It makes no sense, if you already have crdroid installed then all the messy parts of getting rid of MIUI has already been done. If you reinstall MIUI, then it automatically encrypts storage and you will have to format (not wipe) data to move to a different ROM.
Best thing I can suggest is to wipe (not format) everything apart from internal storage. Then reboot into recovery and then try to install the ROM. I suspect error 6 might have something to do with not being able to mount /vendor partition. Make sure you have the updated raupe+blunden TWRP, I believe the official version doesnt mount /vendor as well as having touch screen issues with some variants of mi mix.
Click to expand...
Click to collapse
Problem solved.
New version up with September security update: https://www.androidfilehost.com/?fid=1322778262903998959

Categories

Resources