Whats Up Guys. Today I Present You With The Stock 10C ROM Deodexed For The H901 (T-Mobile Variant.) This is good for ROM developers who plan on modifying any system apps and such. This is also quite useful for when we flash Xposed. (Things tend to break and need fixing...)
BUILD INFORMATION
STATUS: STABLE
CREATED ON: 11/18/2015
LAST UPDATED ON: 01/07/2016
USER AGREEMENT:
Read everything in this thread before asking any questions
Feel free to use this ROM as a base, just give me proper credit and a heads up.
I will not be held liable for any damages you choose to do to your phone, including some that may (they won't unless modified) using my files.
Please do not post mirror links. I will provide them.
FEATURES:
Deodexed
Root
Latest Busybox
Latest SQLite 3
Based On The Latest V10 Software (10C)
Doesn't Reinstall Stock Recovery On Boot
No T-Mobile Spyware
Working Wi-Fi Calling (Even in airplane mode)
No Second Screen Bugs (Xposed)
Dirty Flash Compatible With All 10C ROMs
REQUIREMENTS:
An Unlocked Bootloader
TWRP
A TWRP Backup (Because I Won't Be Responsible For Any Damages/Losses)
Common Sense
Patience
WHAT'S NEW:
V. 1.3.1
Zip Signed. (This helps end users to ensure they have good, valid downloads and is better than simple md5 verification for validation of uncorrupted zips.)
Updated SuperSU to V. 2.66
PREVIOUS VERSIONS:
V. 1.3 - Download | Mirror
Completely Re-done
Fixed WiFi Hotspot and many more minor permission bugs (Thanks @siraltus)
Updated SuperSU to V. 2.65
V. 1.2.2
Patch file to restore build.prop to stock
V. 1.2.1
Updated Busybox V. 1.24.1
Updated SuperSU to V. 2.61
V. 1.2
Fixed WiFi connection issues (Thanks @siraltus)
Updated SuperSu to V. 2.60
V. 1.1
Removed "recovery-from-boot.p" to avoid stock recovery re-installing.
V. 1.0
Removed T-Mobile spyware (com.tmobile.pr.adapt)
LGWeatherService no longer force closing
KNOWN ISSUES:
System is partially odexed still due to some LG Apps having encrypted .odex files. To avoid unstoppable force close pop-ups, I had to
A: Leave some of the system odexed, keeping a complete system
or
B: Remove the apps that were buggy, but not have a complete system.
To clarify, the /system/framework and /system/app/LGWeatherService & /system/priv-app/LGEasyHome are odexed still. I can provide an deodexed framework separately for anyone who needs it, but beware, it will break the two odexed apps.
PLEASE BACKUP BEFORE INSTALLING. AFTER FIRST BOOT, REFLASH TWRP USING THE INSTRUCTIONS FROM THE TWRP THREAD. I'M NOT RESPONSIBLE FOR ANY DAMAGES OR MELTDOWNS, BUT I'M HERE TO HELP.
INSTALLATION INSTRUCTIONS:
Download 10C Deodexed V. 1.3.1
Copy The ZIP File To Your Device (If Downloaded From Another Device Such As A Computer)
Boot Into TWRP
In TWRP, Click The Install Tab
Select The ROM You Downloaded
Swipe To Confirm Flash
Reboot Once Completed.
DOWNLOADS:
H901 10C Deodexed V. 1.3.1 | Mirror
MD5= 1022153884767fb521113b95ea4b4e34
CREDITS:
@SuperR - Development Kitchen and Support
@Chainfire - SuperSU
@Stericson - Busybox
@osm0sis - Busybox
@tech128 - SQLite3
@KAsp3rd - TWRP
@siraltus - Help Fixing Permissions
THANKS ALSO TO:
@KOLIOXDA - For The VERY Kind Donation
Thanks For Stopping By,
Rydah805
Thanks for the deodexed build. Downloading now. Is this debloated as well?
Sent from my LG-H901 using Tapatalk
denson9874 said:
Thanks for the deodexed build. Downloading now. Is this debloated as well?
Sent from my LG-H901 using Tapatalk
Click to expand...
Click to collapse
Your welcome and no, not in this build. This was meant to keep it simple and offer a deodexed version. I will be entering ROM making soon so be on the lookout. Please backup before flashing.
Rydah805 said:
Your welcome and no, not in this build. This was meant to keep it simple and offer a deodexed version. I will be entering ROM making soon so be on the lookout. Please backup before flashing.
Click to expand...
Click to collapse
That's cool super excited to flash this build so I can finally get off stock lol Great job bro[emoji3] [emoji106] [emoji106] [emoji106]
Sent from my LG-H901 using Tapatalk
denson9874 said:
That's cool super excited to flash this build so I can finally get off stock lol Great job bro[emoji3] [emoji106] [emoji106] [emoji106]
Sent from my LG-H901 using Tapatalk
Click to expand...
Click to collapse
Let me know how she runs. Haha wish I was able to test before posting, on my way to T-Mobile to swap for one without a loose charging port. ???
Sent From My LG V10
Thank you.. Will flash soon.
Rydah805 said:
Let me know how she runs. Haha wish I was able to test before posting, on my way to T-Mobile to swap for one without a loose charging port. ???
Sent From My LG V10
Click to expand...
Click to collapse
Loose charging port? Wow. Yeah I think mine's too stiff lol. Downloaded and about to reboot and flash. Will report back soon
Sent from my LG-H901 using Tapatalk
denson9874 said:
Loose charging port? Wow. Yeah I think mine's too stiff lol. Downloaded and about to reboot and flash. Will report back soon
Sent from my LG-H901 using Tapatalk
Click to expand...
Click to collapse
Yeah, I can't even move the device without it dropping a connection.
Excited as this is my first Rom I've built with no help.
Sent From My LG V10
Nice job may give it a shot.any chance can verify three md5 . just want to make sure downloaded. Right
Sent from my non-Mega loved v10 H901.
could not flash it
Zugshad said:
Nice job may give it a shot.any chance can verify three md5 . just want to make sure downloaded. Right
Sent from my non-Mega loved v10 H901.
Click to expand...
Click to collapse
Sure, give me a few minutes.
Sent From My LG V10
matteosaeed said:
could not flash it
Click to expand...
Click to collapse
Really? What happened? Do you have a recovery log you can provide?
Sent From My LG V10
there is an error in the updater-script, assert get prop is for pplus and TWRP is reading the device as h901. Either removing the assert get prop or update the assert to get prop to h901 should fix the flashing issue.
View attachment 3547447 This is what it shows in twrp screen...
denson9874 said:
there is an error in the updater-script, assert get prop is for pplus and TWRP is reading the device as h901. Either removing the assert get prop or update the assert to get prop to h901 should fix the flashing issue.
Click to expand...
Click to collapse
KennyLG123 said:
View attachment 3547447 This is what it shows in twrp screen...
Click to expand...
Click to collapse
Ughhh, how did I miss that. ? thanks guys, I'm away from my work computer which has my tools setup, I'll fix it tomorrow. If anyone wants to try a test, I can edit the script and inject it into the current Rom (which would have the same results)
Sent From My LG V10
Rydah805 said:
Ughhh, how did I miss that. thanks guys, I'm away from my work computer which has my tools setup, I'll fix it tomorrow. If anyone wants to try a test, I can edit the script and inject it into the current Rom (which would have the same results)
Sent From My LG V10
Click to expand...
Click to collapse
I'm ok with waiting till tomorrow. Thanks
Rydah805 said:
Ughhh, how did I miss that. ? thanks guys, I'm away from my work computer which has my tools setup, I'll fix it tomorrow. If anyone wants to try a test, I can edit the script and inject it into the current Rom (which would have the same results)
Sent From My LG V10
Click to expand...
Click to collapse
I'm down for edited script.
Sent from my LG-H901 using Tapatalk
If anyone wants to fix the updater-script themselves, just open it and delete the first three lines where it asserts the device name.
I ended up fixing the script and flashing it myself as I won't have my replacement device til Friday, so I re-flashed TWRP and flashed the updated ROM. It flashed and is booting up right now. It's at the optimizing screen, sounds promising.
Rydah805 said:
I ended up fixing the script and flashing it myself as I won't have my replacement device til Friday, so I re-flashed TWRP and flashed the updated ROM. It flashed and is booting up right now. It's at the optimizing screen, sounds promising.
Click to expand...
Click to collapse
Well heck if you get it running i'll be game to reflash tonight. Thanks
Related
As it says the update for ASUS ICS, but CWM flashable.
*WARNING* If you are rooted, you will need OTA rootkeeper from Market to flash this patch, or flash superuser after rebooting at least once. Currently US and WW ROMs only.
--If someone has an update from another version (CN, etc.) that they want to use, PM me with a link to the file and I can build/edit a script for that too and add it in--
You should be on an odexed stock ROM (rooted of-course) in order for this to work. If you are on a custom ROM, don't bother, it won't work for you. You will need to wait for the dev of your ROM to make a patch or upgrade.
I set this up to only flash the kernal and the patches. Recovery will not be effected. This is confirmed working for me.
The US version -- http://www.mediafire.com/?3aa16qy7sh4t9m4
The WW version -- credit to Lizard -- http://www.mediafire.com/?nw4zgwvl3yug0tw
The TW version -- thanks to wai43 for the files -- http://www.mediafire.com/download.php?cfq6d5lug4q4sd8
I will not be responsible if you brick your tablet. This patch worked fine for me, but may not work for others.
If I'm on stock rooted ics... Should I full wipe? Or just wipe cache and flash over? Thanks
Sent from my Transformer TF101 using Tapatalk
Ep3n3wp said:
If I'm on stock rooted ics... Should I full wipe? Or just wipe cache and flash over? Thanks
Sent from my Transformer TF101 using Tapatalk
Click to expand...
Click to collapse
I didn't wipe anything. It worked fine for me. It works just like a normal update. You may need to be sure to have all the factory installed files though. I did the update from a full stock, rooted ROM. Worked great.
You sir are awesome. Worked perfectly.
For those like mE that edited thier system.
1. I flashed ics full over my set up to restore it without losing my settings.
2. Root keeper to keep root.
3. Flashed this update.
4. Used root keeper to restore root.
5. Profit????
tweaked said:
You sir are awesome. Worked perfectly.
For those like mE that edited thier system.
1. I flashed ics full over my set up to restore it without losing my settings.
2. Root keeper to keep root.
3. Flashed this update.
4. Used root keeper to restore root.
5. Profit????
Click to expand...
Click to collapse
Honestly, I don't know if we can profit from this... lol, but thanks is just fine. I've been dabbling in this crap for years, but I had to go back to the drawing board to get that script to work right. I hope that ASUS has their crap together and don't release a bunch of patches over the next few months, that would suck for all the devs. It is supposed to have some benefits, but I've been playing with this for a few hours and haven't seen anything amazing yet... I'm working on some thing based on this and will release soon.
BTW, for those with random reboot issues, I have yet to have experienced that -- since the original update. Anyway, just my 2 cents.
sent from my ASUS Transformer running modded ICS using Tapatalk
Sharpe351 said:
Honestly, I don't know if we can profit from this... lol, but thanks is just fine. I've been dabbling in this crap for years, but I had to go back to the drawing board to get that script to work right. I hope that ASUS has their crap together and don't release a bunch of patches over the next few months, that would suck for all the devs. It is supposed to have some benefits, but I've been playing with this for a few hours and haven't seen anything amazing yet... I'm working on some thing based on this and will release soon.
BTW, for those with random reboot issues, I have yet to have experienced that -- since the original update. Anyway, just my 2 cents.
sent from my ASUS Transformer running modded ICS using Tapatalk
Click to expand...
Click to collapse
I didn't have the reboot error either. I wasn't even going to install the update. But since you made it easy....
Thanks for the uneventful update.
I HAVE experienced RR on ICS; will see what happens.
The poll in the other thread does not lead me to believe that this update fixes all the problems that lead to random reboots.
Anyway, thanks.
Btw, I tried to capture the update blob but after I renamed it, it disappeared from the /cache
I was just curious as to what you did to the update to defang it.
Is removing the recovery enough?
Does it also carry a bootloader update which you also have to remove?
feisty_noodle said:
Thanks for the uneventful update.
I HAVE experienced RR on ICS; will see what happens.
The poll in the other thread does not lead me to believe that this update fixes all the problems that lead to random reboots.
Anyway, thanks.
Btw, I tried to capture the update blob but after I renamed it, it disappeared from the /cache
I was just curious as to what you did to the update to defang it.
Is removing the recovery enough?
Does it also carry a bootloader update which you also have to remove?
Click to expand...
Click to collapse
I packed only the boot.img in the file. All the other junk is gone. From what I saw in the unpacked boot.img, there appears to be minor changes in the files. Quite possibly updates.
sent from my ASUS Transformer running modded ICS using Tapatalk
Can you just add superuser binary and the app plus busybox to the user script? I'm curious how you could go about further de clawing this update for rooted users.. maybe not wipe the system xbin folder just amend it? I'm out of my element...
luna_c666 said:
Can you just add superuser binary and the app plus busybox to the user script? I'm curious how you could go about further de clawing this update for rooted users.. maybe not wipe the system xbin folder just amend it? I'm out of my element...
Click to expand...
Click to collapse
I backed up su with OTA RootKeeper then rebooted into CWR. I flashed the zip, rebooted and let the update "optimize [my] apps". Once that was done I was greeted with my usual homescreen. A toast notification informed me WebKey was granted SuperUser permission, as always happens on bootup.
Surprised, I launched SuperUser and saw a corresponding new entry in the log. I double checked my current version of su, which was found to be current. I'm assuming that a "No newer version of su available" means su (and thus root) wasn't removed during the upgrade.
I next launched OTA RootKeeper which oddly reported my TF101 was no longer rooted. Nonetheless I hit RESTORE and root is back: or rather OTA RootKeeper is happy now.
--L.
Patch good for Non US Firmware?
I have tried to flash this update but I get an asset failure. Could that be due to the fact that I am running stock WW ICS and not the US version?
error
I got the error in the image I tried a couple of options including the microsd.
https://www.sugarsync.com/pf/D7256720_703_699618527
Sorry I cant get the image to show.
Sharpe351 said:
I didn't wipe anything. It worked fine for me. It works just like a normal backup. You may need to be sure to have all the factory installed files though. I did the update from a full stock, rooted ROM. Worked great.
Click to expand...
Click to collapse
Did you do this in CWM or no? I dont have CWM installed dont really care to bc Im not flashing any ROMs until NVflash works on my sbk version
Sent from my Transformer TF101 using Tapatalk
avasman said:
I have tried to flash this update but I get an asset failure. Could that be due to the fact that I am running stock WW ICS and not the US version?
Click to expand...
Click to collapse
you have to be on a US firmware.
Sent from my Motorola Triumph on CM7 (my custom build) using Tapatalk
lemonoid said:
Did you do this in CWM or no? I dont have CWM installed dont really care to bc Im not flashing any ROMs until NVflash works on my sbk version
Sent from my Transformer TF101 using Tapatalk
Click to expand...
Click to collapse
this is not a ROM. Its a patch from Asus. Yes, it is cwm flashable.
Sent from my Motorola Triumph on CM7 (my custom build) using Tapatalk
carlvk said:
I got the error in the image I tried a couple of options including the microsd.
https://www.sugarsync.com/pf/D7256720_703_699618527
Sorry I cant get the image to show.
Click to expand...
Click to collapse
that is an assert failure. The update isn't happy due to the ROM you're running. if you aren't on a US ROM, it wont update.
Sent from my Motorola Triumph on CM7 (my custom build) using Tapatalk
Sharpe351 said:
that is an assert failure. The update isn't happy due to the ROM you're running. if you aren't on a US ROM, it wont update.
Sent from my Motorola Triumph on CM7 (my custom build) using Tapatalk
Click to expand...
Click to collapse
Aha, that'll be it I'm on ww.
Thanks for the help.
doesn't work for me (us tf).
sth about asusreader. maybe because i've deleted it and other stock apps...
oifi said:
doesn't work for me (us tf).
sth about asusreader. maybe because i've deleted it and other stock apps...
Click to expand...
Click to collapse
you need to be running a full ROM as stated in the OP.
Sent from my Motorola Triumph on CM7 (my custom build) using Tapatalk
Thank You
Sharpe thank you for this zip. I have a US B80 and the stupid update would start to install and then after getting about a 1/4 of the way it would freeze on the android with the exclamation point. Your zip solved that problem and so far no reboots or any weirdness. I do have one question about the update though, how do I stop the tablet from trying to take the OTA(it is persistent).
Thanks
Could someone post up the US ICS OTA file? I don't see it available on Lenevo's download site yet: http://download.lenovo.com/slates/think/tablet1/
It is on the Lenovo FTP
ftp://slatesftp:[email protected]/ThinkPadTablet_A310_03_0069_0130_US.zip
mandrsn1 said:
It is on the Lenovo FTP
ftp://slatesftp:[email protected]/ThinkPadTablet_A310_03_0069_0130_US.zip
Click to expand...
Click to collapse
upload it if you have it please the link is down now
Sent from my ThinkPad Tablet using Tapatalk 2
ker2gsr said:
upload it if you have it please the link is down now
Sent from my ThinkPad Tablet using Tapatalk 2
Click to expand...
Click to collapse
That link is still working for me. I don't have a service i can upload to right now.
mandrsn1 said:
That link is still working for me. I don't have a service i can upload to right now.
Click to expand...
Click to collapse
from your tablet or PC? no dropbox?
Sent from my ThinkPad Tablet using Tapatalk 2
ker2gsr said:
upload it if you have it please the link is down now
Sent from my ThinkPad Tablet using Tapatalk 2
Click to expand...
Click to collapse
Here a dropbox till its on the http:
http://dl.dropbox.com/u/11001249/ThinkPadTablet_A310_03_0069_0130_US.zip
US needs two update files if going the FTP site download route.....~A310~(291M) and ~A400~(4.9M).
eldata said:
US needs two update files if going the FTP site download route.....~A310~(291M) and ~A400~(4.9M).
Click to expand...
Click to collapse
I was able to download both from the FTP here: ftp://slatesftp:[email protected]/slates/think/tablet1/
Now the question I am wondering is... Is it worth it? Potentially sacrificing root and CWR? I have been running 0.0.7.3 CM9 build for many months now and am curious to what you all think.
Pros/Cons? I've heard battery life is terrible, which is odd because I feel like I have good battery life on the CM9 Port. Also... Is root completely gone? Does OTA Rootkeeper help? My biggest concern (I'd probably even lose root if it is fixed), does the pen work as advertised? Or is the infamous 'pen wonk' bug still present?
Pen wonk = writing notes for ~10-15 minutes, pen is suddenly not responsive. Sleep/waking the device fixes it usually. This has been present in every stock Honeycomb build as well as all the CM9 Port builds so I am very curious if this is fixed because I believe it is a hardware issue (Lenovo please prove me wrong). Any info would be much appreciated.
obscure.detour said:
Now the question I am wondering is... Is it worth it? Potentially sacrificing root and CWR? I have been running 0.0.7.3 CM9 build for many months now and am curious to what you all think.
Pros/Cons? I've heard battery life is terrible, which is odd because I feel like I have good battery life on the CM9 Port. Also... Is root completely gone? Does OTA Rootkeeper help? My biggest concern (I'd probably even lose root if it is fixed), does the pen work as advertised? Or is the infamous 'pen wonk' bug still present?
Pen wonk = writing notes for ~10-15 minutes, pen is suddenly not responsive. Sleep/waking the device fixes it usually. This has been present in every stock Honeycomb build as well as all the CM9 Port builds so I am very curious if this is fixed because I believe it is a hardware issue (Lenovo please prove me wrong). Any info would be much appreciated.
Click to expand...
Click to collapse
I was able to go from a rooted, CWM'd device (US 64GB) to a fully rooted device without CWM.
After a few painful steps to get an old busybox file restored and stock recovery enabled, the upgrade process was very simple and so far it is working very well with ICS. There hasn't been enough time to judge battery life yet....
Make sure you follow the instructions that other's have posted about using RootKeeper. That is the only thing I needed to use to restore root perfectly.
armondole said:
After a few painful steps to get an old busybox file restored and stock recovery enabled, the upgrade process was very simple and so far it is working very well with ICS.
Click to expand...
Click to collapse
I updated with CWR rather than reverting to stock recovery. Everything worked fine. However, it did get rid of the stock recovery.
armondole said:
I was able to go from a rooted, CWM'd device (US 64GB) to a fully rooted device without CWM.
After a few painful steps to get an old busybox file restored and stock recovery enabled, the upgrade process was very simple and so far it is working very well with ICS. There hasn't been enough time to judge battery life yet....
Make sure you follow the instructions that other's have posted about using RootKeeper. That is the only thing I needed to use to restore root perfectly.
Click to expand...
Click to collapse
That is good news about the ability to keep root. At least in keeping root, we should theoretically be able to restore CWR.
mandrsn1 said:
I updated with CWR rather than reverting to stock recovery. Everything worked fine. However, it did get rid of the stock recovery.
Click to expand...
Click to collapse
How were you able to update using CWR?
obscure.detour said:
That is good news about the ability to keep root. At least in keeping root, we should theoretically be able to restore CWR.
How were you able to update using CWR?
Click to expand...
Click to collapse
I commented out the lines of the update script that checked for "indigo" in build.prop.
so you're now on official ISC with Root AND CWM ??
it's a great news !
quyTam said:
so you're now on official ISC with Root AND CWM ??
it's a great news !
Click to expand...
Click to collapse
No, when ICS installed, it got rid of CWM.
mandrsn1 said:
I commented out the lines of the update script that checked for "indigo" in build.prop.
Click to expand...
Click to collapse
Do you mind posting how you did the whole install process? Thanks.
bigsnack said:
Do you mind posting how you did the whole install process? Thanks.
Click to expand...
Click to collapse
I did not have CWR to start.
I downloaded the update through the "update" menu on the device.
Update failed due to gps.conf being modified.
Reverted to what I thought was old gps.conf, update still failed.
Install CWR
Try update through CWR
Still fail, due to indigo being required in build.prop (this error is caused by CWR)
Commented out the Indigo lines in the update-script in the update
Flashed again
Still failed for gps.conf.
Commented out each line in update-script mentioning gps.conf
flashed again, it worked.
I take you flashed 310 first then 400?
Where is the script located?
bigsnack said:
I take you flashed 310 first then 400?
Where is the script located?
Click to expand...
Click to collapse
The update-script is in the META-INF/com/google/android folder in the zip. a # sign will comment out any line.
Do I put the number sign in the front?
bigsnack said:
Do I put the number sign in the front?
Click to expand...
Click to collapse
Here is the file i used
http://dl.dropbox.com/u/8479005/updater-script
Just FYI: https://forums.oneplus.net/threads/cm-11s-44s-ota-is-out.173057/
...didn't see the typical insta-thread here, heh.
Greetings friends,
Happy Weekend! Thanks to our buds at Cyanogen, a new OTA will be rolling out to your phones starting today. This new release includes some new fixes such as a resolved SSLv3 POODLE security issue and updated touchscreen firmware.
The OTA will be released slowly and therefore some regions might receive it before others. Once you’ve received your OTA please let us know what you think! Any further issues you may find can also be reported directly to Cyanogen.
Here’s a comprehensive list of changes you’ll find in this update:
Fixed issues with memory causing screen artifacts
Fixed issues with random reboots and instability
Fixed issues with WiFi and modem crashes
Fixed issues with Filesystem
Fixed issues with “black bar”
Fixed issues with persist partition corruption
Fixed issues with AT&T VoLTE
Click to expand...
Click to collapse
Edit: Forgot to mention... this includes a new modem, I know people are always interested in that.
As a side note, I've been running the build as part of an early access test for a few days now... has been extremely solid for me.
Edit again: LINKS!
• Link to the OTA: http://builds.cyngn.com/fota/incremental/bacon/cm-bacon-ac1ccf7921-to-5fa8c79c0b-signed.zip
MD5: 684bc3eb256f06a912505628551cba24
Super mini guide: As long as your system is stock, flash away in stock or custom recovery. I always re-flash the SuperSU zip immediately following, YMMV.
• Link to the OTA with a modified script (by @gianton) for installing regardless of system changes: https://mega.co.nz/#!EdBQ1Y4C!P85kyvVp1iR_I4IiuLKPxGBqskE3fueWe0OGAFidGEg
MD5: 3b5729b07200c0e53a02f6b1225fc79c
FAQ (since people are allergic to reading and searching):
1. ZOMG WHY NO WIFI AFTER OTA?: Because you used a custom kernel and didn't clean up your system files properly. Either follow that kernel threads instructions for OTA-prep'ing or flash back to that kernel.
2. I don't run CM 11S but I can totally flash this CM11S update, right?: No. If you want to flash the 44S OTA update, get yourself to CM11S 38R.
Zip file?
Inviato dal mio OnePlus One
Lolli......Oh wait <.< (Joke post)
Should have grab the zip.
hunter0389 said:
Should have grab the zip.
Click to expand...
Click to collapse
I did, but... as someone that hasn't tested for CM before, I'm not entirely clear on their position of a tester sharing. I wouldn't want to piss anyone off unnecessarily.
dmarden said:
I did, but... as someone that hasn't tested for CM before, I'm not entirely clear on their position of a tester sharing. I wouldn't want to piss anyone off unnecessarily.
Click to expand...
Click to collapse
I understand. Since the OTA is out, would you mind sharing the zip?
Got this link off Android Police article....
http://builds.cyngn.com/fota/incremental/bacon/cm-bacon-ac1ccf7921-to-5fa8c79c0b-signed.zip
blkhwkz said:
Got this link off Android Police article....
http://builds.cyngn.com/fota/incremental/bacon/cm-bacon-ac1ccf7921-to-5fa8c79c0b-signed.zip
Click to expand...
Click to collapse
Great, that makes me feel much better about posting it. I added your link to the OP.
If I update this new build will it break my root ?
vikramdhani said:
If I update this new build will it break my root ?
Click to expand...
Click to collapse
Not in any meaningful way. Just have the SuperSU zip on your phone and flash it after you flash the OTA.
going to be constantly refreshing for OTA. Currently on stock, unrooted, and planning on leaving it that way for now, can the zip be flashed in stock recovery?
dmarden said:
Great, that makes me feel much better about posting it. I added your link to the OP.
Click to expand...
Click to collapse
can i install with twrp?
zipper for TWRP?
mobbarley said:
going to be constantly refreshing for OTA. Currently on stock, unrooted, and planning on leaving it that way for now, can the zip be flashed in stock recovery?
Click to expand...
Click to collapse
I flashed it in TWRP, so I assume stock recovery is also fine.
nicola1989 said:
can i install with twrp?
Click to expand...
Click to collapse
Yes.
mittimus said:
zipper for TWRP?
Click to expand...
Click to collapse
The one in the OP is identical to the one I received as a tester and I flashed it in TWRP.
How do I keep root?
Sent from my A0001 using XDA Free mobile app
Crinkypops said:
How do I keep root?
Sent from my A0001 using XDA Free mobile app
Click to expand...
Click to collapse
I just keep the SuperSU zip on my phone and flash it immediately after the OTA whenever they come out.
dmarden said:
I just keep the SuperSU zip on my phone and flash it immediately after the OTA whenever they come out.
Click to expand...
Click to collapse
Perfect. Flashing now through TWRP.
Sent from my A0001 using XDA Free mobile app
mobbarley said:
going to be constantly refreshing for OTA. Currently on stock, unrooted, and planning on leaving it that way for now, can the zip be flashed in stock recovery?
Click to expand...
Click to collapse
If it contains "signed" it is flashable by stock too
Flashing the ZIP from AP did not work....going to reboot and try again.
reinert012 said:
Flashing the ZIP from AP did not work....going to reboot and try again.
Click to expand...
Click to collapse
Please also elaborate on "did not work" if it fails again... it's identical to the test build ZIP I received which flashed fine. Did you make any system modifications (if so, those will need to be reverted probably)?
OK everyone here is a taste of stock MM for you. This is a port from the Korean model of the v10 which has the same hardware we do this is basically untouched. Enjoy.
We are NOT responsible for bricked devices.
Features: Super SU, busybox, Korean apps removed
Fixed: apn's fixed, Data works like it should now.
Possible SDcard permissions fixed.
More unwanted apps removed
Bugs: fingerprint scanner is not yet working.
Camera Will Not Record: Most likely a PAL issie
DOWNLOADS
https://www.androidfilehost.com/?fid=24499762635997784
OLDER:
https://www.androidfilehost.com/?fid=24459283995315287
XDA:DevDB Information
Stock Marshmallow port, ROM for the T-Mobile LG V10
Contributors
thewalkingdude, Eliminater74, aclegg2011
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.10.x
Version Information
Status: Testing
Created 2016-04-08
Last Updated 2016-04-11
Reserved
Reserved
History: Let me explain how this port came about,
I am known for my Kernel development on the G3, I build a highly advanced custom kernel thats capable of reaching clock speeds of 3.03ghrz and gpu clocked up to 700mhz..
We are talking about a g3 here.. stock speed is 2.47 and gpu stock at 530mhz.. anyhow I build for 9 variants of the LG G3..
Which is d850/d851/d852/d855-32/d855-16/d856/f400/ls990/vs985 . Being a kernel dev, you learn what hardware goes with what..
For example: the D851/D856/F400/LS990 are all BCMD Devices. while the D850/D852/D855/VS985 are all WCNSS Devices.......
I know from experience that the f400 (Korean) is 100% same as the D851(T-Mobile).......
Same holds true on the V10 with the H901 and the F600, When I first tested it, I flashed the untouched boot.img and system.img,
and it booted fully with no issues.
I extracted the system and boot from the KDZ my self........
When I first booted, the only issue we had was keystore.. Keystore is tied into hardware..
So this is when @aclegg2011 stepped in.. He took the Stock LP H901 RoM's keystore and replaced the Stock F600 MM keystore......
He did some other changes too dealing with files.. and of course build.prop changes............
So here we bring you, The First UnOfficial Stock MM on your H901 T-Mobile V10 Device..........
Enjoy Peepz..................................
-=[ Project Was Done By ]=-
@Eliminater74 : For the Main Port and Idea, and Risking it all to make sure it worked.
@aclegg2011: For the file changes to make sure no FC happen and a few other things.
Screenshots:
Thanks a lot for sharing your work. Will flash and provide feedback
Sent from my LG-H901 using Tapatalk
Awesome I'll be flashing this as soon as I get off work today. Thanks for the hard work and sacrifices you've taken!
Been testing for half a day and can say its working pretty good. All essentials such as camera,phone calls data have been working just fine.can't think of any problems besides the listed finger print issue. Great work on this guys, it is pretty amazing the amount of work that has been put in and accomplished.
Oh sweet, thank you so much guys for the hard work so far. So just boot to recovery, nandroid, full wipe, and flash the zip?
update 1:
I atempted to flash but got an error 7 something about this is not a 6P
TIA
Does xposed work for this? If so, will test this when I get home
Sent from my debloated rooted LG V10 using Tapatalk
Wi-Fi calling / VOLTE?
Sent from my LG-H901 using Tapatalk
amoot329 said:
Does xposed work for this? If so, will test this when I get home
Sent from my debloated rooted LG V10 using Tapatalk
Click to expand...
Click to collapse
It should. Maybe someone will test that soon.
Lol I'm willing to try it. Need xposed for my game, hardly any keyboard have the autocorrect for Underworld Empire, the module Always Correct solves that.
Sent from my debloated rooted LG V10 using Tapatalk
kdoweb said:
Oh sweet, thank you so much guys for the hard work so far. So just boot to recovery, nandroid, full wipe, and flash the zip?
update 1:
I atempted to flash but got an error 7 something about this is not a 6P
TIA
Click to expand...
Click to collapse
I dunno what to tell you, 7 people tested it and it worked fine...
Nobody got that error your talking about.. and at least 3 people fully wiped and flashed..
I dirty flashed........ worked just as good..
Wooow....is amazing ...this official ..thanks
Sent from my LG-H901 using XDA-Developers mobile app
@kdoweb: Make sure you are on twrp 3.0 or above, it will not install if you are on anything lower.
@amoot329: xposed works, but it breaks the second screens incoming calls and contact widgets like it did when we first got xposed to work on our device.
@EJerVJerO: Unfortunately wifi calling, and VoLte is not present in this rom since it is from korean variant.
Ahh thx that was it I'm still on ver 2.85 I will update when I get home thx
I think it's funny, after 20 mins of this thread being made, T-Mobile tweeted about v10 mm official *finally* being released.
Sent from my Nexus 6 using XDA-Developers mobile app
aclegg2011 said:
I think it's funny, after 20 mins of this thread being made, T-Mobile tweeted about v10 mm official *finally* being released.
Sent from my Nexus 6 using XDA-Developers mobile app
Click to expand...
Click to collapse
Its bad when the users can beat T-Mobile to the release date.... I bet they get a move on when we Do the same with Android N when its release to KR............
Please how instal this..im using twrp not work install ..?
Sent from my VS985 4G using XDA-Developers mobile app
More details in the Verizon Note 4 forum here.
XDA:DevDB Information
EFIDroid, Kernel for the T-Mobile Samsung Galaxy Note 4
Contributors
abraha2d, m11kkaa
Source Code: https://github.com/efidroid
Kernel Special Features: UEFI, MultiBoot
Version Information
Status: Beta
Current Beta Version: 0.1
Beta Release Date: 2017-03-18
Created 2017-03-20
Last Updated 2017-03-31
THIS IS INCREDIBLE!! Greatest thing since sliced bread where is the donation link this an amazing piece of development 2nd lvl bootloader f yaaaa!!
vegoja said:
THIS IS INCREDIBLE!! Greatest thing since sliced bread where is the donation link this an amazing piece of development 2nd lvl bootloader f yaaaa!!
Click to expand...
Click to collapse
Believe me, I didn't do much work. You can donate to @m11kkaa, though. He's the developer of EFIDroid (if you didn't already know that...). I believe he has a donation link in his profile...
Sent from my Samsung Galaxy Note 4 using XDA Labs
This is great but is there a way to uninstall it (if necessary) and get back to the primary ROM (stock or Lineage OS) without losing data?
tried to do a bit of light research and couldn't find what's different between this and other preexisting multiboot solutions. I've been using Dual Boot Patcher for sometime without issues. Is this somehow better? and if so, how?
Mtotallywired said:
tried to do a bit of light research and couldn't find what's different between this and other preexisting multiboot solutions. I've been using Dual Boot Patcher for sometime without issues. Is this somehow better? and if so, how?
Click to expand...
Click to collapse
EFIDroid is what you would call a "second-stage bootloader". The main advantage over Dual Boot Patcher (at least for me) is that you no longer have to patch zip files before installing. Also, EFIDroid is more than just a multi-boot solution. Quoting @m11kkaa:
efidroid tries to focus on simplicity, and doesn't require any kernel modifications etc.
in general: well having such a powerful bootloader in your boot stage gives you lots of possibilities, like multiboot, replacements/additions for kernels/ramdisk/cmdline.
This project has a lot more potential than what's currently implemented. i.e. you can give samsung devices fastboot and sony devices a standalone recovery. Also you can natively boot GNU GRUB if you're into booting linux kernel's the desktop way.
Click to expand...
Click to collapse
The two solutions are similar enough that you can migrate your setup from Dual Boot Patcher to EFIDroid without losing any data. I'll try to post a guide later this week.
I was I under the impression dual boot required multiple ROMs running the same kernel... If that is the case a huge advantage efi has is each ROM having their own boot img. I'm currently running 3 ROMs a lollipop a marshmallow and of course a nougat. I really just wanted to see all 3 latest android os running flawlessly on 1 device. And I did just that hats off to the developer for this.
baharvey7817 said:
This is great but is there a way to uninstall it (if necessary) and get back to the primary ROM (stock or Lineage OS) without losing data?
Click to expand...
Click to collapse
There's an uninstall button in the app. Or, you could just flash the original boot.img via TWRP (basically what the uninstall button does).
I'm a noob...What is this? Where do I need to go to learn about why I would want this...Please explain lol
mlock420 said:
I'm a noob...What is this? Where do I need to go to learn about why I would want this...Please explain lol
Click to expand...
Click to collapse
you can look at their website, and then decide if you want this level of control over your phone.
http://efidroid.org/
Thanks for bringing us this tool. One thing I can't figure out...how do we Odin a different bootloader? I have DOK2 loaded now, and want to put Dr. Ketan's on the phone. The sub instructions say to Odin the BL and CP, as the ROM is generally generic. There us also a datafix and an essential fix that needs to be applied. Doing all of that is easy, but how do I keep two separate bootloaders (LP and MM) totally separate? If I flash a LP over a MM, my camera breaks, and if I flash a MM over LP, WiFi breaks. And I'm not talking about dirty flashes, a full system, data, and cache wipe 3x. Only Odin back to the base ROM keeps my phone happy.
1freedude said:
Thanks for bringing us this tool. One thing I can't figure out...how do we Odin a different bootloader? I have DOK2 loaded now, and want to put Dr. Ketan's on the phone. The sub instructions say to Odin the BL and CP, as the ROM is generally generic. There us also a datafix and an essential fix that needs to be applied. Doing all of that is easy, but how do I keep two separate bootloaders (LP and MM) totally separate? If I flash a LP over a MM, my camera breaks, and if I flash a MM over LP, WiFi breaks. And I'm not talking about dirty flashes, a full system, data, and cache wipe 3x. Only Odin back to the base ROM keeps my phone happy.
Click to expand...
Click to collapse
There's no way to have two different bootloaders. EFIDroid comes between the bootloader and the boot.img, so it has no control over the bootloader.
EDIT: EFIDroid may be able to emulate the behavior of another bootloader... you would have to ask @m11kkaa for details...
Where can I download this for T-mobile ??
Sent from my SM-N9300 using Tapatalk
CousinMikeyP said:
Where can I download this for T-mobile ??
Sent from my SM-N9300 using Tapatalk
Click to expand...
Click to collapse
Here is the LINK. You can see more info HERE
I downloaded and started up the EFIdroid unofficial apk but got the following message:
=====================================
Error
Can't load device info. Please check your connection.
/data/user/0/org.efidroid.efidroidmanager.debug/files/devices.json (No such file or directory)
override ota server try again
===============================================
Could you please explain what's going on? Seems that this version is different from the one i downloaded in March. Could it be that it's not getting root access? What can I do to get around this error?
baharvey7817 said:
I downloaded and started up the EFIdroid unofficial apk but got the following message:
=====================================
Error
Can't load device info. Please check your connection.
/data/user/0/org.efidroid.efidroidmanager.debug/files/devices.json (No such file or directory)
override ota server try again
===============================================
Could you please explain what's going on? Seems that this version is different from the one i downloaded in March. Could it be that it's not getting root access? What can I do to get around this error?
Click to expand...
Click to collapse
I will have to look into it... The EFIDroid app error messages are not exactly the most helpful kind. (Good thing the app is being phased out soon). That particular error message could mean many things, but most likely it's a connection issue. We will continue this in Slack.
Will this work on tw 7.0 if i was porting a rom. Also why wont aosp kernel work on tw.. i always thought tw was aosp with skin..
Go to back to the link posted above where you got the unofficial apk and go to post #83. The OP posted an apk there that works fine on our phone.
baharvey7817 said:
I downloaded and started up the EFIdroid unofficial apk but got the following message:
=====================================
Error
Can't load device info. Please check your connection.
/data/user/0/org.efidroid.efidroidmanager.debug/files/devices.json (No such file or directory)
override ota server try again
===============================================
Could you please explain what's going on? Seems that this version is different from the one i downloaded in March. Could it be that it's not getting root access? What can I do to get around this error?
Click to expand...
Click to collapse
RaySCLA said:
Go to back to the link posted above where you got the unofficial apk and go to post #83. The OP posted an apk there that works fine on our phone.
Click to expand...
Click to collapse
Tried what you suggested but it didn't work either. So, I chose the 'nuclear option': I wiped the phone completely then reinstalled the stock Marshmallow ROM. using Odin. After that i installed TWRP v3.0.2 (trltetmo) and Supersu v2.79 as well as Busybox v1.26. Only then was I able to install EFIDroid successfully. Now, I'm able to boot the stock rom as well as Resurrection Remix.
It seems that if your going to install EFIDroid you must have the phone rooted using SuperSU. Using Magisk to root your phone instead of SuperSu won't work (at least it didn't work in my case).
lowkeyst4tus said:
Will this work on tw 7.0 if i was porting a rom. Also why wont aosp kernel work on tw.. i always thought tw was aosp with skin..
Click to expand...
Click to collapse
This should work anywhere, regardless of ROM... But btw, it's a stretch to say TW is just a skin on top of AOSP. In fact, TW is probably the farthest you can get from AOSP... There's a lot of significant differences that make AOSP kernels incompatible with TW ROMs...