With Sunshine unlocking droid Turbo Bootloader I will be moving on to making ROM's not just an img. please see my Forum on XDA here and my Website Computerfreek.com Here for more info.
I will continue to do MOFO support for the next month or so as users make the switch.
Computerfreek274_Turbo_lollipop (SU4TL-44)
Also On my website Computerfreek.com Now has updated help and support how to setup stuff like adaway,Boot anamation, Dpi and more. Also I will be posting Pre-Released images there days be for there on XDA. There will also be images some custom images that will not ever be listed on here on XDA for I will not support them. So please check out the site it is still a work in progress but it is getting there. As of right now I did not get custom IMG listed and the newest ver is still 1.6 and it is listed below.
This Firmware upgrade to 5.1 SU4TL-44 from 4.4.4! VIA Mofo.
If you took the OTA 5.1 update you out of luck as you where told not to on here over and over. Go check out sunshine root maybe coming soon for locked 5.1 users.
If this software somehow kills your phone I am not to be held liable.
PLEASE BACKUP YOUR DATA 1st For the best speed and no bugs if you are coming from 4.4.4 for the 1st time I recommend that you backup your photos,music and other data. and when you get to step 3 wipe Data and cache. It is not a must but for me to give you support this is a must.
Thanks to @firstEncounter for his great post and images. Thank you @mattlgroff for his help and everyone who sent me links to the OTA and Full ver.
Thanks to http://motofirmware.center/files/ for hosting stock lollipop IMG's so I an update missing or outdated system files I had.
Big Thanks for PON-3 Audio mod from @mrchezco1995 and his forum is here
Please support better battery stats and give a big thanks over on there forum here. The better battery stats companion app installed in 1.4 will only work with paid ver of bbs from google play.
Thank you guys so much.
Features:
Stable! - I don't publish images without exhaustively testing them. If you have any issues to report, reply to this post and either myself or the community will rally to help fix the issue.
Much better battery life! - This image focuses on battery savings without compromising performance. Your phone will last much longer while running this system image.
Multiple versions - Custom version from DPI dpi higher resolution to Custom fonts
Fast! - This image is lean, fast, and enhanced for performance.
No bloat! - All bloat that is available on the Play Store has been removed. Extra files (like help videos and help audio files) have also been removed.
Optional adblocking! - Adblocking via AdAway that can be toggled on and off.
Now with Pon-3 Audio/ V4A - Increase the volume and the quality of audio output from the Droid Turbo by enabling VIPER4Android which comes bundled in this system image.
Enabled for XPOSED Updated to newest ver. - This system image has been enabled for the XPOSED framework as well as includes BusyBox.
For better support I have removed old versions on here my focus is to have better support for all of you starting from 1.5+
Please Read! If your not on Kernel Version 3.10.40-perf-g90ddf4a Sept 1st 2015 Please Download and flash all .IMG files in this zip here. To find the kernel build go to settings > About phone. Most of you guys will need to update!
Computerfreek274_TurboPop_1.6 Update. 11/07/2015
Now With Turbo 2 Command Center. Screenshot
Download 1.6 Here
Change Log.
Updated .img files in 1..6 No need to download Img pack when upgrading from KK or to update your kernel,modem,etc... all files are updated 1.6 Zip.
Cleaned up some more junk from system
Updated some apps.
Removed music2 aka google music.
Samsung Sans Font IMg's has the IOS9 emojis.
Turbo 2 Command Center
Download 1.5B Here Updated 10/16/2015 Base on SU4TL-44
Download 1.5 Here 10/5/2015
Custom fonts in 1.4 I will update 1.5 as needed.1.4 Download Here.
All Files and IMG's files that are needed to install my IMG are Zipped with all my system images from ver 1.3 and up Just download 1.4 or 1.3 and unzip open the help file and do a step by step install.
Please Read 09/12/2015 For Android Pay support and Setup please see Post #3
You can still download 1.3 and 1.3A here.
[/URL].
1.5B Change Log 10/16/2015.
Updated to SU4TL-44
Updated Xposed
Boosted overall audio and mixer profile updated
Fix Pon-3 audio buffer for large audio high bit rate files buffer from 32m to 48m
Few other tweaks also see 1.5 for more info. This has all the tweaks from 1.5 and 1.5 is the best battery and fast running ver to date.
1.5 Change Log 10/5/2015
Removed more junk like maps and stuff as you have updated ones from market.
Added for more Tweaks for faster GPU and CPU and more memory.
In call VOL boosted default was max 3 now max 10.
Better GPS.
Battery Seems much better with memory fixes.
1.4 Change Log 6/12/2015
Android Pay Support Please see post #3 For more info.
Custom Fonts There will be 1.4 img with custom fonts. More to come check one of the last post for more info.
Some Of the changes listed here is from 1.3A
PowerSave Is in all from 1.3A and up.
Removed some more bloat.
SuperSU is the stable ver.
Xposed to newest ver Please uninstall your old xposed.apk be for you flash.
HDR Camera setting is fixed as of 1.3A
Updated some system files.
Tweaked GPS a bit for faster lock.
PON-3 updated
Fixed audio profiles for PON-3 to match are turbo for a more stable PON-3 audio.
Updated Mixer Profiles for better audio.
mixer_paths updated louder audio as we had in my ver of KK. 09/02/2015 I had to make a new one for Lollipop as the old mods did not work.
updated to work better with the turbo Pon-3.
There is now a set of 1.4 Pure/MAX IMG's also for none Verizon users only.
More help and support can be found on my website at Computerfreek.com for full install and updates Or read below.
How to install
See Post number 2. http://forum.xda-developers.com/showpost.php?p=61636340&postcount=2.
To setup DPI,Adaway and more.
To install system img via mofo see post 2.
Setup Adaway Install AdAway from Play Store. Run AdAway (don't download hosts files yet) and go to settings - preferences. Check 'allow redirections' and under 'target hosts file' select '/data/host Then go back and hit update host files.
Xposed In Pre-installed and setup just install the mods you like to use.
On Pon-3 V4A Open Pon 3 and check the sound devices you like to enable.
Setting up an custom boot animation place bootanimation.zip under /data/local/moodle/bootanimation.zip for more info or watch this small video on how to. https://www.dropbox.com/s/lom6zduant...rding.mp4?dl=0
For 493 Builds to fix the ambient display being off set you must install xposed MOD app settings found here or download it from inside of xposed. and set moto diplay to 640 DPI. If you need more help check the forums here.
Flashing from KitKat to Lollipop
This is a nice well written guide by @Purpeltendire Thank you @Purpeltendire Thank you for this great guide.
If you are new or upgrading and need more help I updated help and info on my website also at computerfreek.com
Steps to flash from KitKat to Lollipop - This assumes that you're currently using a rooted KitKat image already, and have used mofo to get root.
BACK UP ANY DATA YOU DO NOT WISH TO LOSE.
YOU ARE ULTIMATELY RESPONSIBLE FOR ANY LOST FILES OR DEVICE PROBLEMS.
Make sure you have a good hour or two set aside, at the minimum. It’s probably not a great idea to try this right before work or class.
Install mofo, ADB, and fastboot on your computer if you haven't already. On Windows, I like using this for ADB/fastboot.
Download the image of your choice.
Download 5.1_images.zip. Extract the files, and put them into the same directory as fastboot. Next, boot into your phone's bootloader (turn the phone on by holding power and volume down), and flash each file seperately using fastboot:[/FONT]
Code:
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash radio radio.img
fastboot flash recovery recovery.img
fastboot erase ddr
Now open mofo_gui.bat, and flash the system image you downloaded:
Code:
mofo flash Your_imagename_here.img
Once that finishes, you want to try to boot the phone. Select Boot to System from the bootloader and then go grab a snack - chances are, it will sit at the Motorola boot screen for some time. After about five minutes, press and hold power to turn the phone off.
Next, boot into the bootloader again and select Recovery. You will likely get a "Dead Android" screen with "No Command." To bypass this, hold power and tap volume up (if that method does not work after a few tries, hold volume up and press power).
Now that you're in recovery, you're wiping both data (factory reset) and cache. Wipe cache first - this may take a very long time (20-30 minutes), especially if you've never done it before. Wipe data/factory reset second. If you're feeling paranoid, wipe everything again.
From recovery, boot to the bootloader. From bootloader, boot to system. This first boot might take some time as well.
Assuming all went well, you should see a Lollipop setup screen within 10-15 minutes. Congratulations!
Remember that your device is now in “like new and improved” mode. You’ll need to restore your apps and settings from wherever you backed them up to, and you'll still need to get the APKs for Xposed and AdAway. Again, nobody else is responsible for any of your lost data.
[FONT=Arial[/FONT]
For more help see Computerfreek.com
Android Pay Setup and Support. 9/28/2015
Update The updated android pay from google market is no longer working with root so if you flash back to an rooted img after setting up this one android pay will stop working.
9/30/2015
For Working android play and info please go to this forum I have made an IMG with tweaks and more here with working android pay.
Tomsgt said:
just talked with the dev behind moforoot and he said that mofo was patched in android 5.1 but he may look into other ways to get around it.
Click to expand...
Click to collapse
This was stated in another thread. I don't know if you heard, but I'm holding on that there's still hope. Is there still a possibility to be able to make a rooted image? I'm really hoping that we'll be able to have root with lollipop, but at the same time, I don't want you to put in all this time and effort for nothing.
Sent from my XT1254 using XDA Free mobile app
There's a lot of places with the ota, try one of them
Jaocagomez said:
There's a lot of places with the ota, try one of them
Click to expand...
Click to collapse
he needs the firmware img's
Michaelmansour1997 said:
he needs the firmware img's
Click to expand...
Click to collapse
Those will be released in the following days
Jaocagomez said:
Those will be released in the following days
Click to expand...
Click to collapse
noooo i need them today to fix my paperweight
Ahhhhh! I can barely wait!
Downloading the update NOW.. How do I get a dump and copy of the firmware OFF the turbo? Where is it located.. Using ES File Explorer to access /
MoPhoMike said:
Downloading the update NOW.. How do I get a dump and copy of the firmware OFF the turbo? Where is it located.. Using ES File Explorer to access /
Click to expand...
Click to collapse
I am far from the skill level of any rom creator but every google guide I've found seems to indicate root (even temporary root) is required to do a system dump. Is temporary root possible on the lolipop update? If theres another way, please post a guide @computerfreek274 so one of the people who has updated is able to easily help us out and get the ball rolling.
Correct me if I'm wrong, but can't you simply extract the system.img from the OTA zip using this method? http://forum.xda-developers.com/showthread.php?t=2497883
TheSt33v said:
Correct me if I'm wrong, but can't you simply extract the system.img from the OTA zip using this method? http://forum.xda-developers.com/showthread.php?t=2497883
Click to expand...
Click to collapse
Yes but I like to get ahold of a system dump. I been working on the ota today.
Pretty stoked!
Sent from my XT1254 using Tapatalk
siegesoldier said:
I am far from the skill level of any rom creator but every google guide I've found seems to indicate root (even temporary root) is required to do a system dump. Is temporary root possible on the lolipop update? If theres another way, please post a guide @computerfreek274 so one of the people who has updated is able to easily help us out and get the ball rolling.
Click to expand...
Click to collapse
If you Google it there was a way to do it without root. I do not care if it is a system.img dump like that. If you can just copy the system folder to your sd card i do not think you will need root for that use es file man and send it my way that will be great.
Want to make sure so if you have root via MOFRO then you should wait and not install the OTA and wait for new System Image from the Freek!!!
computerfreek274 said:
Yes but I like to get ahold of a system dump. I been working on the ota today.
Click to expand...
Click to collapse
Gotcha. Well unless someone has had luck with Kingroot (early reports said that it didn't work), I don't think that will be possible.
EDIT: Nevermind. It's totally possible. I'll try to track down someone who can get it to you.
computerfreek274 said:
If you Google it there was a way to do it without root. I do not care if it is a system.img dump like that. If you can just copy the system folder to your sd card i do not think you will need root for that use es file man and send it my way that will be great.
Click to expand...
Click to collapse
Pulling /system with adb should be easy and noob-proof.
Sent from my LG-E400 using XDA Free mobile app
TheSt33v said:
Correct me if I'm wrong, but can't you simply extract the system.img from the OTA zip using this method? http://forum.xda-developers.com/showthread.php?t=2497883
Click to expand...
Click to collapse
there are no system img's in the ota, its a flashable zip not an xml
Is this what we're looking for?
http://forum.xda-developers.com/droid-turbo/general/lollipop-5-1-coming-23-11-38-t3146663/page4
I have the restore firmware ... where should I host it?
VRZ_XT1254_SU2-12_12_1FF.xml.zip
Click to expand...
Click to collapse
http://forum.xda-developers.com/droid-turbo/general/droid-turbo-lolipop-firmware-t3147979
Related
Hola peoples!!! Ok so I just thought I'd create my own thread on this matter. Mustangtim started one in apps and themes (and here is the link to that thread) but since I'm taking over this project it was brought to our attention that this should be in the dev section as its no longer just an app.. I am actually tearing .imgs apart trying to figure out what the deuce.
FIRST OFF THIS IS A WORK IN PROGRESS, WE ARE NOT YET FULLY SUPPORTED. HOWERVER I'M DOING MY BEST TO CHANGE THAT.
Secondly if you want to help get this started please visit the market and grab the app here. Its a $3 dollar app for unlimited amount of roms, based on your SD card storage capacity anyway. And speaking of which you need AT LEAST a class 4 or better SD card to make this run smoothly.
Also feel free to visit the forums at http://forum.init2winitapps.com/
Ok so here it is, Boot Manager Pro. Its been a long time coming for the g2x to dual boot. First off let me say long story short, I currently have a bootable SD Rom, known as ROM1. I have yet to be able to recreate my findings tho. But it works and it doesnt brick at all. However it is a bit laggy on my class 4 SD card. Luckily I've already done my research on this project as there are many threads of such awesome info so I'm just going to be lazy about it and quote the good people of xda versus re-writing it based off of their info.
ChrisDDD said:
So here's a very basic description of how it works... It doesn't partition your SD card, it just creates a folder of its own, and then sub-folders to hold the different roms you install. When you install a rom, it basically creates images of the usual Android partitions - system, data, cache, & boot. These are standard .img files, just like the ones Clockwork creates when you do a backup. After the images are created and wiped (formatted, which you should do initially) it installs your rom into these essentially the same way as Clockwork installs a rom to your phone's actual partitions. I assume it modifies the kernel that comes with each rom to mount the image files on the SD card instead of the phone's partitions.
When you want to boot a rom, it just replaces your current boot image with the modified one and restarts the phone. With the modified boot image, the system, data and cache images on the SD card are mounted to the correct locations and Android starts up none the wiser. The rom will initially run a little slow, because the SD card is slower than the internal memory, but after things get cached it speed up considerably.
When you want to reboot to another rom, or back to the phone's rom, Boot Manager again swaps boot images that mount the desired rom's partitions (in the case of the phone's rom) or files (in the case of an SD card installed rom).
When you first run Boot Manager, it makes a Clockwork flash able backup of your current boot image, which you can flash if a rom hangs or loops on startup. Alternatively, you can also simply boot into recovery and do an advanced restore, choosing just the boot image to restore from a backup. It accomplishes the exact same thing.
It can be a little hit or miss, with some roms just plain refusing to start through Boot Manager, but it does work and when it does, it's pretty amazing given what it's actually doing.
Click to expand...
Click to collapse
So basically upon installing the app you need to setup your phone so that way you can properly install a ROM, follow these steps:
1. Go into the supersu(or superuser app) and then go to settings then disable logging or click none.
2. Then go into the BMP app and press the menu button on your phone, not the app, and go to settings. Once in settings put a check mark in force large boot.img, screen on during install, and then go into variables, leave tegra alone but change the sdcard block to show mmcblk1p1. Then press finish and let the app restart. By the way I didnt change any of the sizes of the .imgs but feel free to do so. But be warned do not decrease the size of the system.img only increase it, if desired.
3.Then after you've done the above you need to setup the phone rom. Click on 'Setup Phone' under phone rom and follow that process to setup your phone rom.
4. Once your phone rom is setup you may begin to install a zip to rom1 or rom2 or whatever slot you want. This is the tricky part. I have done tons of reading and most people say that if your using CWM, which us g2x'ers do, then you will probably have a better chance of getting a bootable rom by restoring from a nandroid backup you did versus installing new.
5. So after you decide which path you will take, nandroid backup or fresh rom install, choose install. If you choose a fresh rom, wipe system, data, and cache right away. If nandroid, then wipe after the install.
6. Now once you have clicked install put your phone down, DONT MESS WITH YOUR PHONE AT ALL! PUT IT DOWN AND WALK AWAY OR SOMETHING! Don’t mess with it, text from it, xda from it, dont even use the screen as a mirror!!!! lol seriously the app is picky and while under the .img creation process you want nothing to mess that up or you will not get it booted. You may however drag down the notifications bar to follow the progress of the install.
7. Once its complete, tap the install complete notification in the notification bar and let the app do its thing to finalize the install and get you back to your rom selection screen. Now if you did a nandroid back up here is where you click 'manage slot' and then factory reset the backup you did. Just do it, dont ask why.
7.1 Also so if you desire to install gapps and/or possibly a different kernel, now would be the time to do so while your here. I have read mixed reviews of doing this process right after the rom installs. However when I set up my rom1, I booted into it first all happily then realized I had no gapps. So I had to reinstall BMP on rom1 then boot back to phone rom and then I installed GB gapps and had no issues booting back into rom1.
8. Once the above steps are done if your feelin lucky go ahead and tap on boot the rom you installed, and if all goes well it will boot up.
9. If it boots up you need to post confirmation here!!! Provided info such as phone rom and the info on the sd rom you used and slot number and such.
Hopefully it will just work for you. I have done all the above steps using HFP 2.1 as my phone rom and only been able to get 1 bootable rom. Being it was for testing I used HFP as my phone rom and as well as my rom1.
So if the above steps dont wortk out for you and your boot lopped or what ever, then turn your phone off and reboot into cwm. You have 2 options to resolve the boot issue you just created. 1, you may go to restore then advanced restore then restore your boot. Or 2. select install a zip and nav to the bootmanager folder then phone rom then flash the update zip there.. then reboot and you should be back at your phone rom.
Here is a basic run down of everything that I have done so far:
When I first started working on this project I wasn’t doing any dev'ing to change any of the stuff in the boot.img. I just changed settings in the app per all the research I did. So when all was said and done I restored HFP 2.1 to ROM1 and it actually booted!! And it works lovely btw.. I can still boot into this rom today. I then decided to pass the word and ways that I created the working rom1, well I nor anyone else I passed the info to was able to get it working. Only one other person was able to confirm that rom1 works but only after I copied all my rom1 info and sent it to him for testing.. and he was able to boot into my created rom1… As I see it, it was a blue moon event that I have yet to repeat. So I thought eff it lets do some dev'in so I unpacked the boot.img from rom1 then compared that to the unpacked boot.img from rom2 that I created in my trial and error experiences. So in doing so I noticed 4 differences; 1, the mount points obviously, 2, in the sbin folder had a ueventd file from the working rom1 was a text file viewable by gedit in ubuntu. In rom2 it was just a non-readable file. 3, in the init.rc file was also missing a chmod command for system, (the command is in rom1 but not rom2) and 4, there was a ueventd.tegra file that was in rom1 that wasn’t in rom2, but everything else is the same. So I decided to plug and play with the differences to see if she boots and no go. I don’t understand why its boot looping because I am using the same rom as phone rom as for rom1 and rom2. So it boot looped. So I had to restore my boot.img many times in cwm.
So then I said eff it lets do some more research, then I noticed in the .zips folder plus the individual rom folder there are .zips that will let you flash via cwm if you get boot loops and 'should' get you booting to your desired sdrom. I then tried that way and no go.. so then I opened up the zip and had a look at the internals.. first there is the moveboot.sh file that the app runs in cwm flash the given boot.img. I then checked out the meta-inf and opened up the updater-script thinking that the app wasn’t actually flashing the boot.img which is why it loops... Well I think im half way right. However the script itself is lil dodgy... first thing I noticed was at the end of the script they have a command to cp the log from /tmp to /sdcard/bootmanager well the command was wrong so it never copied the log. So I fixed that. I also saw that the assert command was pointing to ‘boot’ instead of mmcblk0p5, so I changed that too. Then I decided to do away with the assert command and the moveboot.sh file they have going on to utilize the same functions that the kernel zips use, which is a kernel folder that holds the boot.img and a run_program that dd's the boot.img to 0p5. plus I even updated the update-binary that the file uses. I used the one from the g2x nullifier as I know that one was made for our phone and should have no issues.. plus there was a noticeable difference in the sizes of the provided binary to that replaced binary. So with the updated.zip file I then rebooted into cwm to flash that being that I was using a different command to flash the boot.img as well as the other changed stuff and still it boot looped. So as of now the only thing I don’t think ive done was grab the boot.img from rom1 then change the mount points, only change that, and then use that for rom2 and see if it boots. I don’t think I’ve done that yet. But every dam process I do I get boot loops. So basically I have came to the conclusion that it’s now NOT a boot.img issue being that I have done everything to change the boot.img and to make sure it flashes, which it does indeed and now creates the log too… I think maybe it has issues with the system.img as that’s what comes next in the boot process. But that’s just my hypothesis. I won’t be able to confirm this till I liberate rom1’s boot.img then change the mount points to point to rom2 and then see if it boots.. if it don’t work then that would mean to me that there is an issue with system.img created. But that’s just my hypothesis…
What I don’t understand is why the eff when I didnt hack the app I got a working sd-rom, but when I do change some stuff with it still don’t work!!???!! I guess maybe ill just edit/hack the apk to see what’s up.. This is getting way more complicated than it needs to be, since it worked prior to all my major changes to the script its using for flashing and the boot.img and what not. Anyone have any ideas feel free to add them.
My next steps are to edit rom1 boot.img one last time to change the mount points to point to rom2 and then if that’s a no go then it’s got to be the system.img that’s getting created. By the way this whole process I have only been restoring my nandroid backup for HFP 2.1. I have not attempted to flash new as with thru my research more times than not people would get a bootable rom via restoring versus flashing new.. so if anyone wishes to experience an sd rom let me know, ill send you a link to download my rom1 to get it going. Mind you that its not perfect and you need a class 4 or better sdcard. Everything works but it just takes a bit longer to load things and get things cached as its on the sdcard and not nand. Also if you have any input or are wishing to help pm me I need more heads to get this sorted as I can’t be the only one who knows how to edit scripts and unpack imgs and such. Either way I will continue to do this until I get it right damit!!! Oh and I just ordered a class 10 sdcard to help with this process…
That was copied from the other thread that mustangtim started. Last night when I went home the first thing I did was change the mount points on rom1 to reflect rom2, I changed nada else, then I tried to boot it... it boot looped. So maybe its a permissions issue or the system.img.
So just as a proof of concept and before anyone calls bs on my work/findings Here is the link to my rom1 that boots and is HFP2.1. *Update, 'm just going to
leave it on my DB for now till I find something better I guess. xda wont let me attach the file since its 233MB. Oh well here is the link :
Code:
[URL="http://db.tt/eBZwrOrs"][U][B]Here it is, my Rom1 HFP 2.1[/B][/U][/URL].
I have also attached my updated script file to flash back to rom1, for now.
The boot.img points to rom1 instead of phone rom, ill add to phone rom
as well, just not the now. :) Feel free to flash this via cwm versus
restoring...
Also this is part of the this: the ‘.zips’ folder you need to replace the file in
that folder as well. It’s an update file for rom1 to flash the boot.img.
..
If you’re going to use this you need install a random rom to rom1 then replace those created files in rom1 with these files in the 7z file..
So I am doing this new thread to get the devs or people with know how to help me out with my findings. I have edited the boot.img so much I could pretty much re-write everything in there by now including using magic to create to my own kernel eff!! lol jk but seriously I need people with knowhow to provide confirmation of go or no go. Basically I have people whom have helped out but It seems that I'm the only one who has dug this far into this app(unless i've been misinformed) and I have no one on my level to talk with except the init2winit devs. Which are very helpful btw.
And lastly:
Conap said:
Guys if it's failing to make the boot.img first make sure your using the market version....others have released cracked versions of our app which they broke...if your using the actual market version just send me a pm or email [email protected] and send your log.txt from BootManager folder on sdcard and we'll get it straightened out. Thanks.
Click to expand...
Click to collapse
or post here or PM me, I'm always down to help out.
Also thanks go to the init2win team, Gflam and Conap as they started this app. and as well to Mustangtim as he brought me into the light of BMP.
So you got all that???!!!??? Now lets get this party started and get full support for dual booting. I will not rest until I get this working. Thanks for your time and possible assistance.
Ok so since I have a book above I thought this is a good place for links and such...
So just incase anyone is curious, here is the Official Boot Manager Manual
Here is a nice link for Tips and Tricks while Installing ROM's that so far has good info to help you watch via adb what the BMP is doing in its creation process.
Some FAQs:
When should I set up my phone ROM?
Set up your phone ROM EVERYTIME you install a new ROM to your phone so you can get back to your phone ROM and won't get stuck on your SD ROM.
My SD ROM seems to lag how can I fix this?
SD ROM lagging may be due to a few things which all have easy fixes. First fix is that most of you have class 2 cards which are what usually come with your phones. These have a much lower read/write then cards of a higher class, we recommend a class 6 card or above. Another easy solution is overclocking merely install a better kernel and use CPU Boost (or any other overclock app) to overclock your phone.
Can I nandroid my SD ROM slots?
Yes and no you can't nandroid them in the traditional sense of the word using recovery but this app works as a recovery for your SD ROM slots and you can back up your ROM slots within the app in the Manage Installed ROMs section which works as a nandroid for your slots by fully backing up your slots to your sdcard which can later be restored.
What if I want to change the sizes of my images, how may I determine the individual sizes easily?
Easiest way is to open up terminal emulator in your app drawer. Type 'su', then grant permissions if need be, then type 'df -h' and it will display such information. You may also use adb in the same fashion. Connect via usb, open up command prompt/terminal and get adb connected and then type 'df - h' again and the same info will show. I will say this again just because, do not decrease the size of your system.img ever! Unless you want mad issues!
Here is the changlog link and just for heck of it the info based on that link:
Code:
V3.2.6
Fixed DroidX/Droid2 Install issue
Fixed UI theme issues
Fixed issue with spaces in name of pic when selecting photo for screen shot
V3.2.5
Fix to allow continue of install if no boot.img is found.
V3.2.4
Added support for HTC Rezound
Added support for rom's with multiple boot.img's
Added support for rom's made for multiple phones
AutoDetect sdcard for usb mounting
Fix for installing ICS gapps
Optimized SDRom Install process
Added support for Motorola RAZR
Added install queue
V3.2.3
Fixed issues with rom's not showing when on emmc on Droid Incredible
Fixed issues with not showing correct booted rom in app
More improvements to sms sync(all rom's will need updated app for changes to apply)
Fix issues with loader
Fixed issue with switching to backup server when main server goes down
Fixed 1x1 widget to show unlimited rom slots
Added 2x2 widget that works with unlimited rom slots
V3.2.2
Fixed force close for img's over 1Gb when resizing
Fixed current booted rom displaying correctly on gnex
Fixed issue with wrong busybox downloading on gnex which should fix alot of install/boot issues
V3.2.1
Fix for errors causing installs to fail.
Fix for some of the licensing stuff.
Removed sdbooster prefs from Galaxy Nexus(Since they don't have sdcard).
V3.2
Changed 4 sd slots to infinite slots!
Galaxy Nexus Support
Sms and Call Log synced between ROMs (you choose what ones too also requries updating boot manager in all slots)
License Check extended to a week
ROMs do not need market installed for boot manager to run (requires updating boot manager in all slots)
Hide su toasts (superuser elite only)
Fix for force close when setting screen shot in MIUI rom's
Thunderbolt defaulted to force large boot.img
Fixed unsupported device using a key
Manually setting variables only accepts numbers
V3.1.1
Fix for various force closes in rom installs and Nand restores
V3.1
Added su binary check
User selectable colors for everything
Better navigation (press title for quick action)
Added compatability for new twrp backups
Better compatiblitlity with memory tweak scripts(i.e. supercharger script and liquids default scripts)
Fix for install process being killed by android
Fix for some themes erasing img's
Fix more force closes during install
Force smaller boot.img option in settings(Fix for some phone's who's boot.img won't fit on the phone after BootManager edit's it)
Improved gapps checker
Improved security
Boot Manager now accepts keys pay for by paypal (see http://init2winitapps.com/stories/BootManager.html)
Added Evo 3d GSM Support
Added notifcation sound/vibrate for finished install (turn on in settings)
Improved data check
V3.0.3
Fix some force closes
V3.0.2
Added backup server (Sorry our server dropped out)
Fixed some force closes
2nd init fixes for Liquid's ROMs
V3.0.1
Last minute UI fixes
V3.0
UI Completely redone
Includes screen shot of each slot
Custom Info
Custom Dialogs
Custom Animations
Custom everything!
Bug Fixes
Added Droid 2 Global support
Screen shot with long press of search
V2.2.1
Bug fixes in file browsers
File browsers only show relevent files
Kernel installer fix
Droid 2 bug fix
V2.2
New security (more advanced and requires data only once a day)
Installs no longer require data
Added Italian translation thanks Black-Ice
Droid X support
Droid 2 support
Fixed status bar notifications
Fixed phone rom rebooter if gapps aren't installed
Bug fixes
V2.1
Restore android_secure to sd from nandroids
Added TWRP nandroid support
Added CWM tar nandroid support
Added Spanish translation
Made widgets easier to use
SD Booster added (Change SD read cache for better preformance)
Added current settings to manually set variables.
Added option to keep screen on during install in settings
Fixed usb layout
Updated Security
Bug Fixes
V2.0
Install now runs from the foreground (status bar)
Restore Nandroids to slots also in the foreground
User can cancel installs as they run
4 new themes added including one by apophis9283
Some phones such as tb moved to new install code (Fix for some sense rom's)
V1.3
Added third theme to app (Red Theme)
Added 4x1 widget and new widget styling
Fixed in app messenger
Added support for Htc Evo 3D
Added support for Htc Sensation
Added Support for Htc Incredible 2
Added Support for Htc Incredible S
Added Support for Htc Desire S
Added support for LG Ally
V1.2
Added option to reboot to phone rom to install gapps in license check dialog
Better error checking and error logging
Automatically install's ext2 libs if not present
Moved Set Names to Manage rom's
Fix for add-on's not installing correctly
Better compatiblility for rom's that use data2ext or apps2sd(user must set larger img's in manual variables)
Trash cleaner added to extras
Better Fix for WiFi issues on Droid 1
Added display to show what rom you are booted into
Fix for updater-script not found errors
Added support for Htc NexusOne
Added support for Htc MyTouch4G
More compatiblity for ext4 support
V1.1
Fix WiFi issues on Droid 1
Fix bug in rom installer for setting permissions correctly
Fix bug for cache size not setting correctly in setting variables manually
Fix for decimals entered into partition sizes causing force close
Fix force close in widget
Fix force closes in installer
Added Wipe data/Factory reset to Manage Rom's section
Added code to show what file's are being unzipped in dialog
Added support for rom's that extract files to sdcard so the files actually end up on your sdcard
Added support for Htc Desire (apps2sd and data2sd rom's support is experimental. Please email if you test it and it works/doesn't work)
Added support for Htc Inspire4g
Added support for Htc DesireHD
Added option to use ext4 filesystem if rom's support it-Experimental Won't work with all rom's.
Added log.txt file to sdcard to log errors during install
V1.0
Initial Release
YEZZZ
glad to finally see this here!
jookdakang23 said:
glad to finally see this here!
Click to expand...
Click to collapse
indeed... hopefully it wont be before too long that I get this app fully supported for us!
This app will be extremely useful for G2X owners and makes the G2X more versatile and desirable.
da-pharoah said:
indeed... hopefully it wont be before too long that I get this app fully supported for us!
Click to expand...
Click to collapse
idk how you get it booted. lol i keep getting bootloops
jookdakang23 said:
idk how you get it booted. lol i keep getting bootloops
Click to expand...
Click to collapse
Are you using the files I supplied or the ones that BMP created for you?
Woo hoo good job bud
Sent from my LG-P999 using xda premium
x0xhellx0x said:
Woo hoo good job bud
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
LOL thanks bro.... Go Team Hellfire!!!!
da-pharoah said:
Are you using the files I supplied or the ones that BMP created for you?
Click to expand...
Click to collapse
i remember requesting the files but think you ever sent them
jookdakang23 said:
i remember requesting the files but think you ever sent them
Click to expand...
Click to collapse
no we had a miscommunication due to our avail times and GB's lacking ability to utilize two accounts on gtalk.... I have posted those files in the op however...
First, I want to thank everyone who has helped with us on this app. Second, I know I picked the right man for the job, did you see that OP! All kidding aside, a lot of you know I write for ACS under screen name artifintel. I just had too much on my plate to give this project the attention and direction it needs. The right guy is in charge, he's a stand up person and very knowledgeable with this app. Good luck everyone!
[email protected]
I tried installing CM9, it didnt work, stuck on first boot screen after the LG logo.
I'm using rooted stock 2.3.4
Rafase282 said:
I tried installing CM9, it didnt work, stuck on first boot screen after the LG logo.
I'm using rooted stock 2.3.4
Click to expand...
Click to collapse
what rom are using as phone rom? and you installed to rom1?
da-pharoah said:
what rom are using as phone rom? and you installed to rom1?
Click to expand...
Click to collapse
As phone rom i;m using rooted stock 2.3.4 v21y
The to rom1 I installed CM9 kang from oiwan with gapps and harsh kernel
Rafase282 said:
As phone rom i;m using rooted stock 2.3.4 v21y
The to rom1 I installed CM9 kang from oiwan with gapps and harsh kernel
Click to expand...
Click to collapse
and no bootloop you say?? well then it may be the stock rom your using... The app is very picky and if you get a bootloop, I feel that those can get booted with tweaks... but stuck on lg screen is just no bueno.. Try a different rom... maybe one that has its partitions at ext3 format just to try it.. I think owains rom uses ext4, but I could be wrong. I havent fully researched his rom yet..
hands down, a badass app...
SiL3nTKiLL said:
hands down, a badass app...
Click to expand...
Click to collapse
lol +1 for sure!
da-pharoah said:
I think owains rom uses ext4, but I could be wrong. I havent fully researched his rom yet..
Click to expand...
Click to collapse
positive on ext4
Computerfreek274's System Image
for the Verizon Droid Turbo
This image is based on the XT1254 Verizon 21.44.12 rooted stock image with native WiFi tether/hotspot enabled, and is meant to be flashed using MOFOROOT.
Features:
Keep your data! - You will not need to reinstall any applications or lose any data as this method only replaces the phone's system partition.
Stable! - I don't publish images without exhaustively testing them. If you have any issues to report, reply to this post and either myself or the community will rally to help fix the issue.
Much better battery life! - This image focuses on battery savings without compromising performance. Your phone will last much longer while running this system image.
Fast! - Breathe new life into your Droid Turbo, this image is lean, fast, and enhanced for performance. I draw from the well-documented tweaks of the community, including stuff like V6 Supercharger.
No bloat! - All bloat that is available on the Play Store has been removed. Extra files (like help videos and help audio files) have also been removed.
Optional adblocking! - Adblocking via AdAway that can be toggled on and off.
Optional ViPER4Android! - Increase the volume and the quality of audio output from the Droid Turbo by enabling VIPER4Android which comes bundled in this system image.
Enabled for XPOSED! - This system image has been enabled for the XPOSED framework as well as includes BusyBox.
1.5.5A
1.5.5A All in one V4A See Changelog for more info.
Download Here
MD5: e07886cfe0be7348a10627c50a019b7d
1.5.5A All in one Without V4A See Changelog for more info.
Download Here
MD5: 22500511e09451245c92bc15dd926539
1.5.5A All in one V4A With 493 Dpi test build Please see note below.
Download Here
MD5: b8baaf983bf82ed541de2b9d999a267c
This build has a DPI of 493 stock was 640 is gives you a lot more room on the screen also 5 rows on the home page. But this will make the moto display (active display) off-centered!!! this is the black clock screen when you wave your hand over. there is a fix to there you have to use xposed.
Fix for moto display in DPI 493 build.
Install "App Settings" from Xposed repository (or google it)
Set the DPI to 640 for Moto Display app.
Unlock button and clock will be unaffected!
Credits to Dareal and Jaocagomez
1.5.4a + AdAway
Download Here
MD5: 0e1411b1e5be9c580e5ce0e0fe9a9e35
1.5.4a + AdBlock Host Files
Download Here
MD5: b1f25360a939a201b1532762000f708b
1.5.4a
Download Here
MD5: 1cbc6a02e4c4e995f65612039b7965dd
Instructions:
Check your system version. Go to Settings -> System -> About Phone -> System version; make sure that you're on the system version 21.44.12.quark_verizon.verizon.en.US before starting. This is a requirement for using MOFOROOT. If you're not on this most recent version, download and install the Verizon system update by going to Settings-> System -> System updates -> Check for system updates.
Check your operating system. The MOFOROOT method can only currently be ran on Windows and Linux. If you are on OS X, you can set up a virtual machine using VirtualBox running the current (15.04) version of Ubuntu. This tutorial will help you get it set up. If this step applies to you, the rest of the steps need to be completed in your virtual machine, NOT OS X.
Download and install the drivers for your device. You have to make sure that your computer can recognize your phone first. Depending on your operating system, any of these links should be able to get you set up: Motorola, AndroMods, RootJunky.
Download the system image from this thread. Before you try to flash the system image, please cross reference the MD5 hash, or else you may brick your phone!
Ensure you can connect to your device via ADB and fastboot. Download and install Android Debug Bridge (ADB) on your operating system. It is included in the Android SDK. This is an awesome guide to installing fastboot - use it. Once both are installed, plug your phone in and open a command prompt. By either adding adb/fastboot to your path, or navigating to the downloaded directories, run adb devices to see if your computer recognizes your phone. Reboot the phone into bootloader mode by following these directions. Once you've connected your device to your computer while in this mode, try running fastboot devices from the terminal to make sure that your computer recognizes your phone while in this mode (this is the mode you will need to be in when using MOFOROOT).
Ensure that you have Python on your machine. MOFOROOT is written in Python, so Windows users will have to make sure that they have Python 2.7.9 downloaded and installed.
Download MOFOROOT. This system image is meant to be flashed using MOFOROOT. Ensure that you've paid for and downloaded the de-facto rooting method from their website. Please note that this method provides a utility that allows us to flash pre-rooted system images to our phone, but does not turn write protection off. Motorola/Verizon has locked down this device's bootloader and enabled write protection, so any changes made to the system partition outside of this method will be only temporary and disappear after reboot. Development on this phone may feel like we have to jump through so many hoops - that's because we do. You should be able to download and run mofoverify from their site, which will give you a link to be able to pay for and download the mofo utility.
FLASH THE IMAGE! After all of those steps, you can finally connect your phone to your computer in bootloader mode (checking to see that it's recognized using fastboot devices) and run mofo flash path_to_the_downloaded_system.img. This is the original XDA mofo instructions, read and follow them if you have any issues. If you're having problems with using MOFOROOT via VirtualBox[/URL on OS X (using [URL="http://www.ubuntu.com/download/desktop"]Ubuntu as your guest OS), here's a thread where some issues were discussed. If mofo stops on you and doesn't make it to 100%, just press the up arrow and then enter to restart it. Do not plug your phone into a USB 3.0 port as this happens far more on USB 3.0. I have flashed multiple IMGs and some of them stopped and I had to restart it. So just give it time.
CLEAR THE CACHE BEFORE RESTARTING! After you have flashed the system image using MOFOROOT, you MUST wipe the cache before rebooting. You can follow these instructions if you don't know how to do it. Failing to wipe the cache may result in your phone not booting. You should still be able to get to the bootloader menu if you get caught in a bootloop, and clearing the cache should fix your issue.
Reboot and PROFIT! Congratulations! You're finished. The first phone reboot may take about 10 minutes. Do not freak out and just let it finish. The next steps are optional if you'd like to set up ad blocking, ViPER4Android, or XPOSED.
Setup ad-blocking. This system image has AdAway pre-installed (if it doesn't, you can download it). Open AdAway and go into Preferences and click on Target host file and set it to /data/data/hosts from the pop up menu. Go back and hit Download files and apply ad blocking. If Super User asks for permission, grant it. Also say yes to the system link on the first-time setup. Restart your phone. You should now not see most ads! You can disable this at any time by going into AdAway and pressing Disable ad blocking. If you would like to manage ad-blocking on a per-app basis, you can disable AdAway and use MinMinGuard for Xposed. Thank you @pjsockett for the tip.
Setup ViPER4Android. ViPER4Android (V4A) is pre-installed. Open the app and enable it and set it up. Do NOT check the box Force Enable V4A and run V4A in FX Compatible Mode. Without running in FX Compatible Mode, the Facebook app will not play audio on videos. PLEASE NOTE: Enabling V4A will negatively impact battery life.
Setup the XPOSED framework. Download and install the XPOSED framework installer. I have done all the hard work in this image to get the XPOSED framework to work without any extra steps. If XPOSED is not working for you, please follow the first few steps of this guide.
I do my best to support this, but we all have lives that demand our attention. Anyone is free to contribute to this project and discuss development or features right on this thread. The community behind this system image is pretty awesome. Big thanks to @savagebunny for giving me the drive, info, and support to keep working on V4A. Thanks also to @paintba11er89 for the AdAway suggestion and helping me organize this OP. Huge thanks to paintba11er89 for the help with a very clean OP he used his time to rewrite this post to help me and others so please thank him.
This is only the first step to THE NEXT BIG THING!
DISCLAIMER: I AM NOT RESPONSIBLE IF YOU BRICK / RUIN YOUR PHONE IN ANY WAY.
BASIC COMPUTER SKILLS REQUIRED.
Help:
Read the instructions - There's a lot of great guidelines in there that will answer most questions that you have. If you have issues with Google Apps or Services stopping more than once after you've booted, refer to step 9 in the instructions to clear the phone's cache. Additionally, check out this video that may help with this issue. If you're still having issues, you may have to factory reset and format your data partition to start over clean. That's obviously not optimal, but that's the price that we pay for not having a fully unlocked bootloader.
Changelog:
1.5.5A All in one With AdAway system link, xposed, with or without V4A
Fixed GPU 2x faster benchmark for the GPU video.
Fixed the lag on launcher.
Fixed WiFi scan times. Part of the power saving.
Fixed and updated Build.prop
Removed some startup's apps.
I am removing 1.5.5 on OP and going to replace it with 1.5.5A as there was some bugs With the GPU. So please upgrade to 1.5.5A. Sorry I did not see the drop in 1.5.5 in the GPU speed.
Remember if you do not like adaway just do not set it up. Or if your doing an custom host file it place it in /data/data.
i will keep doing an None V4A for now till i find a way to fix the USB audio out. This is used for amps.
Custom paid ver builds will be updated soon and I will PM you all the links soon.
1.5.4a + AdAway
Download Here
MD5: 0e1411b1e5be9c580e5ce0e0fe9a9e35
1.5.4a + AdBlock Host Files
Download Here
MD5: b1f25360a939a201b1532762000f708b
1.5.4a
Download Here
MD5: 1cbc6a02e4c4e995f65612039b7965dd
1.5.3a + ViPER4Android + Ad-Blocking
Download Here
MD5: e9a272b16506ea62067f055151b61886
1.5.3a + ViPER4Android
Download Here
MD5: 944c745d906f85a858608691ec9446ec
1.5.3 + ViPER4Android + Ad-Blocking
Download Here
MD5: 74efbb3f6e4a21c4b3dcfb492dcc6d99
1.5.3 + ViPER4Android
Download Here
MD5: 9d8543abb8a65b0a697c4b504c0224d3
1.52a + Verizon Visual Voicemail + Ad-Blocking
Download Here
MD5 : ce71e58308f5f7e4e727ae0a7bdc9e98
1.52a + Verizon Visual Voicemail
Download Here
MD5: 2750328e905c71d6a4c7ec1dbd27254e
1.5.2a + Ad-Blocking + ViPER4Android
Download Here
MD5: b4c060813dc08ea20ead2400a1c7becb
1.5.2a + ViPER4Android
Download Here
MD5: 77a6a4cef997992cbc8970518d0f0e76
Is this different then the build on the other thread by Ekkoria because that one is working for me right now.
Does this have full root? Or is it the same as the initial release albeit with the hot spot tethering?
Many Thanks
There are those of us who appreciate the all time consuming work you put in for others.
Thanks again :good:
XF1ber said:
Is this different then the build on the other thread by Ekkoria because that one is working for me right now.
Click to expand...
Click to collapse
I used the stock rooted image from here This IMG is for users on Verizon with an unlimited data 29.99. All others with family share plan or other data plan on Verizon you already get hotspot as part of your plan.
Thanks for your work, hope to see more updates to this!
Thank you for this
Thank you for this, a super good start for the situation were in.
If possible could you incorporate a mixer_paths.xml for louder volumes and incorporate adaway? or an updated host file from adaway?
Seems to me one of those ad removal apps had an option in it to symlink a host file? think something like that would work if it were in the system apps dir, but updating to /data somewhere?
thanks again for all your hard work
PS - Remove that damned boot sound maybe?
Slartibartfast_ said:
Thanks for your work, hope to see more updates to this!
Click to expand...
Click to collapse
WiFi tether works ! What else do you plan on doing? I only really wanted tether to work.
GhostRider5666 said:
WiFi tether works ! What else do you plan on doing? I only really wanted tether to work.
Click to expand...
Click to collapse
To be honest, tethering is not even on my list as my employers pay my bill and it includes tethering.
I'm looking for some xposed modules, adaway, titanium backup and other perks of rooting.
Slartibartfast_ said:
To be honest, tethering is not even on my list as my employers pay my bill and it includes tethering.
I'm looking for some xposed modules, adaway, titanium backup and other perks of rooting.
Click to expand...
Click to collapse
I would like more but I have multiple phones I can use.
this gave me wifi tether. however whenever i try to connect to the hotspot it is saying Limited Connection, and I am unable to use.
-Michael_ said:
Thank you for this, a super good start for the situation were in.
If possible could you incorporate a mixer_paths.xml for louder volumes and incorporate adaway? or an updated host file from adaway?
Seems to me one of those ad removal apps had an option in it to symlink a host file? think something like that would work if it were in the system apps dir, but updating to /data somewhere?
thanks again for all your hard work
PS - Remove that damned boot sound maybe?
Click to expand...
Click to collapse
I will look into the audio boosting if someone can pre-edit the XML I can place it in faster.
acetkbez said:
this gave me wifi tether. however whenever i try to connect to the hotspot it is saying Limited Connection, and I am unable to use.
Click to expand...
Click to collapse
Mine works just fine.
You need to turn your phone off and back on go to WiFi hotspot change ssid and password/key . then start it. You got something locked up with your hotspot if you can not change the settings.
acetkbez said:
this gave me wifi tether. however whenever i try to connect to the hotspot it is saying Limited Connection, and I am unable to use.
Click to expand...
Click to collapse
Working fine I have tested it over and over on 2 phones. My guess is it is windows set the password on the phone longer under wifi hotspot settings and reboot windows. it is working i did not do anything to tether just a bypass. So that is on your side. if that don't work connect something other like an tablet or other laptop.
computerfreek274 said:
Working fine I have tested it over and over on 2 phones. My guess is it is windows set the password on the phone longer under wifi hotspot settings and reboot windows. it is working i did not do anything to tether just a bypass. So that is on your side. if that don't work connect something other like an tablet or other laptop.
Click to expand...
Click to collapse
Its working fine on my phone, I changed the network name and everything.
computerfreek274 said:
Working fine I have tested it over and over on 2 phones. My guess is it is windows set the password on the phone longer under wifi hotspot settings and reboot windows. it is working i did not do anything to tether just a bypass. So that is on your side. if that don't work connect something other like an tablet or other laptop.
Click to expand...
Click to collapse
I tried on my tablet and a macbook and it didn't connect either. I'm not able to change the wifi name or password either.
If it matters I had previously installed the rootjunky image and then put your file over it?
Could that be why it isn't working?
I favorited this thread!
computerfreek274 said:
I will look into the audio boosting if someone can pre-edit the XML I can place it in faster.
Click to expand...
Click to collapse
This is the one the moto maxx guys are using with success, credit to them. I just extracted it from their flashable zip
https://www.dropbox.com/s/66wxkjx40bdbbc9/mixer_paths.xml?dl=0
-Michael_ said:
This is the one the moto maxx guys are using with success, credit to them. I just extracted it from their flashable zip
https://www.dropbox.com/s/66wxkjx40bdbbc9/mixer_paths.xml?dl=0
Click to expand...
Click to collapse
if you can write a mini tutorial to flash it on droid turbo Rooted phones i can credit you and include your text.
Jaocagomez said:
if you can write a mini tutorial to flash it on droid turbo Rooted phones i can credit you and include your text.
Click to expand...
Click to collapse
Sorry, I cannot. I don't have access to a Linux box ATM to build it into the img. the creator of this thread was to incorporate it into the img he's building for all of us to flash using mofo root.
If we had write off its as simple backing up the original /system/etc/mixer_paths.xml and dropping in the new one, then setting permissions and your done. But that's not our situation YET.
Sent from my XT1254 using Tapatalk
DEV DIGITEL PRESENTS
Stock 7.0 Magisk Debloated/Deodexed + Mods
Whats Included:
Magisk Version 13.xx <- Passes Safety-net As of 8/19/17
BusyBox Pre-built into system + Magisk Module
3minit Clock / 3minit Battery @OvrDriVE For spending the time to get the SystemUI Corrected!
Stock Htc Apps From HTC U11 : Gallery, Music, MMS, Htc Sense Home, Htc weather, Htc Clock , Internet, Camera
Shortcutter App Added - For endless quick tiles
SystemUI Tuner - Made by Local XDA Dev Zach
Hotspot Mod
****Many other tweaks etc, all Gplay apps and things that can be dl from google play were removed****
Before we move any further lets get this outta the way, I AM NOT LIABLE FOR WHAT MAY HAPPEN TO YOUR DEVICE, You remove my liability by proceeding any further and downloading / installing any software or mod developed by @Team DevDigitel. Worst Case, RUU back to stock and try again!
So 1st, always make a backup and be prepared to restore your device and possibly brick it. I am not liable for your device or the effects of this software, please use at your own risk. And feel free to report bugs and submit feedback as well as help resolve some issues we are working on!
STEPS
1) Unlock Bootloader - Go to HTC DEV SITE AND FOLLOW STEPS AND RETURN HERE ONCE UNLOCKED
2.) Flash the TWRP RECOVERY.img
Using fastboot while in bootloader mode
use command: "recovery.img is name of twrp recovery or rename to match"
Fastboot flash recovery recovery.img
3.) Make sure your using the newset twrp. No longer encryption issues!
4.) Go now to install in twrp and choose the rom.zip you downloaded and flash it to the device. After flash completes you need to reboot device and allow the 1st boot to complete. Due to being deodexed and 1st boot, this will take 5 - 10 minutes to complete just wait!
5.) Reboot and Enjoy and, Also dont forget to hit the Thanks button !!
ROM Downloads:
Revision 3 : DevDigitel_1.32.651.6_7.0R3
https://www.androidfilehost.com/?fid=817550096634793725
Twrp Recovery :
http://forum.xda-developers.com/bolt/development/recovery-twrp-touch-recovery-t3519304
This was built using the stock image that comes pre-loaded to the HTC BOLT
This was rebased; The Updated Rom is Based off Stock Version 1.32.651.6 De-odexed by Bad Boys Team
@OMJ Thank you for providing the necessary files and de-odexing for this base!
The device must be bootloader unlocked and TWRP recovery used to flash.
S-OFF is not required but recommended ( No radio included with this rom)
RUU to latest version 1st to obtain latest radios without S-OFF
Please do not redistribute my work without giving proper credits to all involved as well as asking permission to host such work 1st! Thanks!
Contributors:
@OMJ - General Help + Newest Base for Rom.
@OvrDriVE - Smali / xml files related to SystemUI mods / General Support
@topjohnwu - magisk
@Captain_Throwback -twrp , root
@Chainfire - root[/CENTER]
Reserved
Reserved
Is this build of TWRP fully working? I only ask because the other 2 builds up until now have had certain things broken...
bdizzle1686 said:
Is this build of TWRP fully working? I only ask because the other 2 builds up until now have had certain things broken...
Click to expand...
Click to collapse
This twrp does not decrypt htc encryption still.
while using the decrypted boot.img it can access all features
backup/restore etc.
using on a encrypted storage will not work still. atleast until captain throwback comes back with the correct mods needed.
New link is up, located a few issues and removed them.
Boot.img was being pre-rooted and was causing a hang, no longer a issue.
The setup wizard has been removed, the default homescreen was cleaned, almost all bs apps are gone, ill update with a newer version here soon.
Just need to flash the su zip after first boot, the fingerprint and service issues shouldnt be present in this build anymore.
old system size was well over 12gb. Now it's at a healthy 8gb debloated.. What a difference.
delete please
Is hot-spot unlocked?
Revived for any Htc bolt users out there, ill update some good screenshots here in a few!!
Hope this helps someone out!! Hit the Thanks on OP if it did!!
Screenshots added to the Post / Pay attention to status bar, I made sure to include some with 3Minit battery options and different locations.
Re-uploading Rom with some apps moved to User-data instead of System/App; Cleaning up scripts and removing dead directories.
htc themes account
htc themes account not working..not updating either not installing after 19/8/17 update
How can i deal with the problem of getting hot on my phone?:crying:htc 10 evo
stream1027 said:
How can i deal with the problem of getting hot on my phone?:crying:htc 10 evo
Click to expand...
Click to collapse
a lot of it has to do with the design of the phone being its metal. Unfortunately its not something im able to deture much. You could reduce temps some by under-clocking the processor or reducing the amount of use the processor is going through, kernel auditor or similar apps give you the ability to scale back the cpu, but you will take a performance hit doing so. A case at least removes some of the heat transfer to your hands but inst much of a "fix"
does this rom have radio
adnanagha said:
htc themes account not working..not updating either not installing after 19/8/17 update
Click to expand...
Click to collapse
has there been a fix for this i am having the same problem
also have been having trouble with certain apps crashing on my htc bolt
Can I use hot-spot freely with this?
Sent from my 2PYB2 using Tapatalk
This rom has band 8 activated?
this rom work on htc 10 evo ??
Team DevDigitel Presents:
Stock With Goodies =)
This is a stock based rom based on the QI5, QK3, QL9, RA6, and It is Pre-rooted with SuperSu, Heavy Debloat and some slight adds, this is just the basic start, Moded boot animations and removal of all carrier info that is not sprint, so non sprint users... well sorry, this is the sprint side of things.. if you want to flash this and you are non sprint, go ahead and do so, then after phone has fully booted one time, put phone in download mode and flash your carriers csc, please do not request support in this thread for porting to other carriers.
WHAT YOU NEED:
You must have already Rooted your device with SamFail, You also will need FlashFire and Busy-Box installed and some common sense!
FlashFire : https://play.google.com/store/apps/details?id=eu.chainfire.flash&hl=en
(OR)
SAFE STRAP TWRP: https://forum.xda-developers.com/ga...covery-locked-nougat-7-1-1-safestrap-t3772765
Busy-Box: https://play.google.com/store/apps/details?id=com.jrummy.busybox.installer&hl=en
Okay here lets get started, and oh wait..
And as always, I can not be held liable for the damage or malfunction of your device using these files, you proceed at your own risk and remove my liability by continuing to the downloads portion of this post!
STEPS:
Step 1: Insure Busybox is installed into system directly. I prefer /system/xbin
Step 2: Install FlashFire and grant it root permission
Step 3: Click the Little RED + button in the bottom right corner and choose Flash ZIP or OTA
Step 4: Navigate to where you have downloaded my rom and select it.
Step 5: Check the box next to ( Mount / System read / Write) then hit the check mark in top right corner
Step 5.5: If you are not already on my rom, you must choose WIPE and do a full wipe, this is deodexed and the old data needs removed, this also needs to be put at the top of the flash list to be done 1st just click and hold on the wipe and drag it to the top.
Select the following : Wipe System Data, 3rd Party apps, Dalvik Cache, Cache Parition.
Step 6: Hit the FLASH button at the bottom and hold on for the ride! If all goes well you should have installed TeamDevDigitel rooted stockish rom and enjoying yourself.
Step 7: Hit the thanks button at the bottom of the post and keep checking back here for updates!!! Photos attached to post to see how things should look on boot-up and during install using FlashFire.
Please Join The Telegram Group For Faster Communication!! Group ID: t.me/DevDigitel
Please See Changelog in Post #3 for more information about the ROM versions
DOWNLOADS BELOW:
U3/RA6 & Newer BOOTLOADER/FIRMWARE
Download Links:
U3_DevDigitel_BRB4_V1: Feb Sec Patch
Link 1: https://www.androidfilehost.com/?fid=890129502657595794
U3_DevDigitel_RA6_V1: Jan Sec Patch
Link 1: https://www.androidfilehost.com/?fid=890129502657583230
U2/QJB & Newer BOOTLOADER/FIRMWARE
Download Links:
U2_DevDigitel_QL9_V1: Dec Sec Patch
Link 1: https://www.androidfilehost.com/?fid=746010030569947345
U2_DevDigitel_QK3_V2: Nov Sec Patch
Link 1: https://www.androidfilehost.com/?fid=745849072291696990
U2_DevDigitel_QK3_V1: Nov Sec Patch
Link 1: https://www.androidfilehost.com/?fid=745849072291696564
U1/QI5 OR OLDER BOOTLOADER/FIRMWARE
Download Links:
U1_DevDigitel_QI5_V5: Oct Sec Patch
Link 1: https://www.androidfilehost.com/?fid=673791459329058731
U1_DevDigitel_QI5_V4: Oct Sec Patch
Link 1: https://www.androidfilehost.com/?fid=817906626617943327
U1_DevDigitel_QI5_V3: Oct Sec Patch
Link 1: https://www.androidfilehost.com/?fid=817906626617941853
U1_DevDigitel_QI5_V2: Oct Sec Patch
Link 1: https://www.androidfilehost.com/?fid=673791459329055952
Status : Stable
BUGS / KNOWN ISSUES:
*Pop-up While being plugged into pc saying device can not be used, this is normal just dismiss and use as normal.
*Certain Apps do not work due to being rooted; SamsungPay, SHealth, SecureFolder and others are effected by this.
some apps now working with tima=0
*If you get stuck in setup wizard, please click back and go forward again, if it still wont proceed just reboot phone and it will make it through the setup. This happens randomly for setups it seems.
If you are having audio issues : go to /system/etc/mixer_paths_tavil.xml and change to mixer_paths_tavil.xml.bak2 and take the mixer_paths_tavil.xml.bak and remove the .bak off of it. This essentially turns off the dual speaker mod, but shouldn't need to be done, some apps just may not like dual speaker mod?
Removed This pre-built in feature on BRB4 due to many apps not supporting dual audio this way.
Developer:
@Team DevDigitel
Contributor(s)
Special Thanks to These guys for getting ROOT!
- @partcyborg
- @me2151
- @elliwigy
Donations: Thank you guys for the support and donation, I hope you guys have enjoyed the work ive provided and continue to benefit from it. Please join telegram group if you guys have any issues or feel free to hit me up at [email protected]
@fiver5 (Gifted Ad Free)
@Mediocrates (Gifted Ad Free)
Team Dev Digitel Recommended & Tested Mods & App Links:
Boot Animations MOD:https://forum.xda-developers.com/sp...s/mod-boot-animations-root-flashfire-t3691310
3Minit Battery MOD: https://forum.xda-developers.com/sp...es/mod-3minit-battery-root-flashfire-t3694694
Surround Sound Mod: https://forum.xda-developers.com/galaxy-note-8/themes/note-8-soundmod-magisk-module-t3677719
SystemUI Tuner APP : https://forum.xda-developers.com/sp...app-systemui-tuner-root-root-options-t3688773
Weta-Mod APP : https://forum.xda-developers.com/tmobile-galaxy-note-8/themes/mod-weta-1-4-t3705882
FlashFire APP : https://play.google.com/store/apps/details?id=eu.chainfire.flash&hl=en
Safe-Strap APP: https://forum.xda-developers.com/ga...covery-locked-nougat-7-1-1-safestrap-t3772765
Busybox APP : https://play.google.com/store/apps/details?id=com.jrummy.busybox.installer&hl=en
Shortcut Master APP : https://play.google.com/store/apps/details?id=org.vndnguyen.shortcutmaster.lite&hl=en
Rom ToolBox : https://play.google.com/store/apps/details?id=com.jrummy.liberty.toolbox&hl=en
Viper4Android : https://forum.xda-developers.com/galaxy-note-8/themes/snapdragon-viper4android-t3685936
Changelog
Please pay attention to how files are labeled as this is to help insure you have chosen the correct firmware for your device. The U1 or U2 will be to determine if your device has been updated or not to the newer bootloader. This will forever lock your device to the newer revision bootloader U2 and you no longer can flash U1 roms or use their data from backups. Please insure you either update and flash U2 or if you are still on U1 and you bootloop and cant recover, restore using a u1 firmware or choose to flash the latest firmware.
#####################U1 FIRMWARES##########################
U1_DevDigitel_QI5_V2 -
Deodexed stock sprint QI5 Base - Using Superrs Kitchen
Bundled Sprint CSC with matching apps to restore VVM, Wi-Fi Calling and Sprint Zone
Removed carrier data for non Sprint devices
Further removed non essential market apps
Injected Latest SuperSU and BusbyBox parts
Removed KNOX Based Apps
SeLinux Set to permissive,Dm Verity Patched (Due to using Eng boot.img)
U1_DevDigitel_QI5_V3 -
Removed Additional Bloat
Now able to un-check apps on the main setup wizard
Init.d & SU.d Support added to system ( Without Kernel dependencies)
Added 3Minit Battery Mod
Zip-aligned Apps after changes were made for optimization.
ADB Mount/Remount Mod
Killed IZAT reporting/logging app
U2_DevDigitel_QI5_V4 -
Added Viper4Arise, Viper4AndroidFX, Viper4AndroidXHIFI (Viper4Arise you will have to install driver via app and reboot to use , this breaks V4A)
Added Custom DDC, Kernel, Profiles For all 3 Viper Apps to use, Compiled from all their builds, 130+ options easy!
Added Users Mode for multiple users - Click Profile icon in the status-bar / quick toggles to setup additional users. Max of 5
Disabled multiple device loggers, this should increase battery life, increase performance Aka Mild Build.prop tweak
Debloated more non-sprint services
Added Google Photos - Google Lens Feature ( Pixel 2 pure google feature)
Probably other things ive forgotten to mention....
U1_DevDigitel_QI5_V5 -
All Builds now set to mount system RW / wipe system files only without user-data
Added Full Busy-box Run Parts to insure no mods would fail to be implemented.
Patched imsservice.apk to hide the RCS and VOLTE icons, no need to use 3rd party app to hide.
Added DexDesktopmode to system for Dex desktop docks
Changes to build.prop to include fix for SHealth Security and other Knox blocked apps
Removal of more non sprint services ( Multi-Carrier items)
Modem For AQI5: Flash with Odin after flashing rom. Don't/Wont wipe anything
Link:https://www.androidfilehost.com/?fid=817906626617958621
#####################U2 FIRMWARES##########################
U2_DevDigitel_QK3_V1 -
First Release on latest November Security Patch. I believe I have moved everything over that was built into the revision 5 build and merged it with the latest firmware after de-odex
Modem For BQK3: Flash with Odin after flashing rom. Don't/Wont wipe anything
Link:https://www.androidfilehost.com/?fid=817906626617952674
U2_DevDigitel_QL9_V1 -
Dec Security Patch - Minor additional debloat, fixes for non facing issues.
Based on Sprint QL9, This is to replace the QLA variant used for dec patching ( Prev. Based on Tmo Firmware)
Modem For BQL9: Flash with Odin after flashing rom. Don't/Wont wipe anything
Link:https://www.androidfilehost.com/?fid=817906626617958620
#####################U3 FIRMWARES##########################
U3_DevDigitel_BRA6_V1 -
Jan Security Patch -Based on Sprint BRA6 Firmware, DeOdexed, Surround Sound Mod Added & Modded to work with Viper.
Moved all mods from Previous Version.
Modem For BRA6: Flash with Odin after flashing rom. Don't/Wont wipe anything
Link: https://www.androidfilehost.com/?fid=962187416754460857
U3_DevDigitel_BRB4_V1 - FINAL 7.1.1 BUILD
Feb Security Patch -Based on Sprint BRB4 Firmware, DeOdexed, Surround Sound Mod REMOVED, You must remove extension from the mod to activate now.
Modem For BRB4: Flash with Odin after flashing rom. Don't/Wont wipe anything
Link: https://www.androidfilehost.com/?fid=673956719939832589
Haha !!! 1st! Can't wait to give this a go. Thank you for your hard work! You rock!
Well ive narrowed down the camera to a issue with the updater script and the links/perms to the hardware for camera. Not sure where to start as the stock img and the eng img built very different scripts.. gonna have to play around some and see.
WOO!!! Glad to see you got it working before me!
I wanna go for a ride.. I'm buckling up!
Sent from my SM-N950U1 using XDA-Developers Legacy app
Was thinking about flashing but first wanna confirm. There is currently 2 things that don't work, the flashlight and camera? Is that correct still? Because I use those 2 daily lol
powerstroke said:
Was thinking about flashing but first wanna confirm. There is currently 2 things that don't work, the flashlight and camera? Is that correct still? Because I use those 2 daily lol
Click to expand...
Click to collapse
Yes that's correct
Both are still not working. I'm still just in testing phase that it's flashing with flashfire and booting correctly for multiple people. Wiping data etc and it still works. Looking for fc's etc. I'm working on redoing the scripts in hope the cam and flash are just tied to the perm/metadata/symlinks auto generated by my tool
Team DevDigitel said:
Yes that's correct
Both are still not working. I'm still just in testing phase that it's flashing with flashfire and booting correctly for multiple people. Wiping data etc and it still works. Looking for fc's etc. I'm working on redoing the scripts in hope the cam and flash are just tied to the perm/metadata/symlinks auto generated by my tool
Click to expand...
Click to collapse
Ok, I'll wait to flash then because I use both daily lol
It didn't flash for me per the op. Suggestions?
Sent from my SM-N950U1 using XDA-Developers Legacy app
treoarx said:
It didn't flash for me per the op. Suggestions?
Sent from my SM-N950U1 using XDA-Developers Legacy app
Click to expand...
Click to collapse
What happened? I'm thinking you would need to have selected wipe system and data and placed it at the top 1st because you are coming from a non deodexed Rom and i completely forgot about this step as I've been on deodexed myself for some time and it wouldn't effect me. If you want to give it another go that would be what would cause the issue.
Team DevDigitel said:
What happened? I'm thinking you would need to have selected wipe system and data and placed it at the top 1st because you are coming from a non deodexed Rom and i completely forgot about this step as I've been on deodexed myself for some time and it wouldn't effect me. If you want to give it another go that would be what would cause the issue.
Click to expand...
Click to collapse
10 4
Sent from my SM-N950U1 using XDA-Developers Legacy app
Glad to see you over here. Still using your V20 rom until I can upgrade to the N8.
well great news! got everything sorted out, decided to start from scratch and deodex my own base, added the sprint files needed for wfc and the sprint zone stuff, figured out the perms and links and got camera and the flash fixed! uploading a new version now. will be ready in 30min!
op will be updated with correct process to install as well
Team DevDigitel said:
well great news! got everything sorted out, decided to start from scratch and deodex my own base, added the sprint files needed for wfc and the sprint zone stuff, figured out the perms and links and got camera and the flash fixed! uploading a new version now. will be ready in 30min!
op will be updated with correct process to install as well
Click to expand...
Click to collapse
Looking forward to downloading once uploaded, thanks for fixing the bugs
OP HAS BEEN UPDATED AND FRESH DL LINK IS AVAILABLE!
Make sure to review steps as they have changed, and i have attatched photos to op of the way flashfire should look.
Thanks so much for your hard work!
One question - I'm not rooted (yet); does flashing this (and hence being rooted) limit us to charging up to only 80%?
Thanks in advance!
altimuh said:
Thanks so much for your hard work!
One question - I'm not rooted (yet); does flashing this (and hence being rooted) limit us to charging up to only 80%?
Thanks in advance!
Click to expand...
Click to collapse
Yes once rooted we are stuck at max 80% charge
Ok thanks - just got my note 8 on Saturday and I'm dying to root it. I'm just having a hard time accepting a 20% loss lol.
Hopefully the masterminds figure out a way to overcome that.
Few days ago as expected, official users (who is using CN-EN official ROMs) of Le Pro 3 AI (further mentioned "x7") got an OTA update to the latest release of EUI 6.0.030S.
The miracle that expected was not appeared. It is still based on Android 6.0.1 (Marshmallow).
The ROM is still not localized for other countries, it contains only CN and EN languages.
And there still many bloatware of LeEco services that is very annoyance.
But first of all, the apps inside are now more optimized and as I see, they starting and function faster then previously.
Ok, let's go to the main part - links =)
The Official Site where you can download the ROM based on OTA update scheme is HERE. Also you can download a copy of OTA package from HERE.
But if you want to download faster, you can use my clouds where I'm continuously holding the most of Official ROMs for x7.
---> MEGA (follow into the folder called "original_stock")
---> FEX
Inside my clouds you can find that the ROM filenames contains not only a version but also an appropriate suffix (_OTA or _FASTBOOT). It's used to separate the ROMs by the installation method.
The FASTBOOT prepared ROMs contains an installation scripts (.BAT for Windows and .SH for Linux/Mac) for not only full installation (with clearing of User Storage), but also for update (without clearing of User Storage).
Please be careful, don't even try to install via FASTBOOT without clearing of User Storage, if you currently have functioning non Official multilingual EUI like 5.9.027S (faked as 028S in menu "About phone") or other non official!!! If you'll do this you will get many conflicts in settings and apps.
I expect that the FASTBOOT updating instructions are widely known, but remind them once more:
1) Enable the "Developer options" menu by clicking on "Build number" 7 times in the "About phone"
2) In the "Developer options" menu, turn on "OEM unlocking" and "USB debugging"
3) Connect the phone to the computer with a USB cable
4) Run one of the installation scripts from the folder of the unpacked firmware
5) Immediately upon startup, allow on the phone screen the "USB debugging" permission for your computer, preferably within the checkbox "always trust this device"
6) Wait until the installation process finishes (15-20 mins), calmly referring to the fact that the phone itself will reboot into FASTBOOT mode, and also please ignore the Sparse format error message (it's normal)
7) The phone itself will reboot into a new OS ... the first launch will be very long
Please feel free to ask anything here about the installation process, cloud links etc.
But be ready that I'm not fast answering.
Any other questions including the comparison of EUI versions performance and functionality will be ignored by me.
We still have the device that is highly secured with unknown protection mechanism and that gets us unable to build any quality custom ROM. =|
thank you
I should have researched before buying the device kk was already "lost" trying to find a customized rom for him. this part of the text: "We still have the device that is highly secured with unknown protection mechanism and that gets us unable to build any quality custom ROM. =| " , clarified me a lot
I istalled it but it does not have google play store?
azizo07 said:
I istalled it but it does not have google play store?
Click to expand...
Click to collapse
ROM does not have Google applications. You need install it. I think this still working in this version: https://forum.xda-developers.com/le-pro3/leeco-le-pro3-a1-model-x651-guides-development--and-mods/automated-installer-gapps-morelocale2-t3752576
Ok installed the 30s mod version from https. ://4pda.ru/forum/index.php?showtopic=895159&st= 2020#entry77308634
and it includes gapps.
You can install another launcher to get rid of ads.
There is no root for this rom, right?
azizo07 said:
Ok installed the 30s mod version from https. ://4pda.ru/forum/index.php?showtopic=895159&st= 2020#entry77308634
and it includes gapps.
You can install another launcher to get rid of ads.
There is no root for this rom, right?
Click to expand...
Click to collapse
030S mod is based on APKs of 030S with few modifications... but it also runs the old Boot from version 027S... so it may have some unexpected behavior...
yes, all of these ROMs have no root... but with mods based on Boot of 027S version you can use a temporary root (one time booting into TWRP) for further system modifications and then back to boot with native stock kernel and modified system will run good (expect the problems with apps you may cause by modifications)
hi, how i can install this ROM if I use a non official Rom? I mean, I recived this phone yesterday with a 028s (stable) that is non official, and I want to install this official ROM.
Help please
My cell phone has brick
You have some rom to fix it?
Does the NFC work on this rom? I had 028s before but the NFC was disabled.
Hi im install rom eui 6.0.030s "https://4pda.ru/forum/index.php?showtopic=895159&st=2020#entry77308634"]https://4pda.ru/forum/index.php?showtopic=895159&st=2020#entry77308634 But me phone have in antutu 50000 . Ealier was 100000. What is wrong i see Stock-thermal.zip but i cant dowload . plise help
can't see inside the package "4) Run one of the installation scripts from the folder of the unpacked firmware"
or can i use rename the package to update.zip and run on the system update?
cyzarine said:
can't see inside the package "4) Run one of the installation scripts from the folder of the unpacked firmware"
or can i use rename the package to update.zip and run on the system update?
Click to expand...
Click to collapse
What you can't see? The scripts?
You need to look at the contains of unpacked ROM zip that have suffix "FASTBOOT" in filename. There must be files with names like "x7_fastboot_tool.bat" and "x7_fastboot_tool_noUser.bat" and also same files with ".sh" extensions for Linux.
For installation to start you need to run one of this scripts. To run from CLI (CMD), not by double-clicking on it.
what's the score in antutu in new rom ? I have 50000....
dilnix,
I've downloaded the FULL_X7_X7-CN-FN-KGXCNFN6003009091S-6.0.030S.zip which don,t have the fastboot tools.
Do you have instructions to install this?
Big thank you!
cyzarine said:
dilnix,
I've downloaded the FULL_X7_X7-CN-FN-KGXCNFN6003009091S-6.0.030S.zip which don,t have the fastboot tools.
Do you have instructions to install this?
Big thank you!
Click to expand...
Click to collapse
This is an OTA package. But it's buggy, my try to make a direct update from 028S to this 030S with OTA way was failed, and I heart many reviews about same behavior.
So I think the best way to update is to use Fastboot with scripts and executable provided in my package that contains "_FASTBOOT" suffix in filename.
From there you can use script "x7_fastboot_tool_noUser.bat" (or .sh option in Linux) to make update to 030S (only from clean stock 025S, 026S or 028S, not from fake 027S or any mod) without clearing of Userdata Storage.
Or you can use script "x7_fastboot_tool.bat" (or .sh option in Linux) to make a new installation of 030S with clearing of Userdata Storage (from any other previous ROM).
If you can't download by my links provided in topic, please write here and I'll try to solve this.
grzegorzkuc said:
what's the score in antutu in new rom ? I have 50000....
Click to expand...
Click to collapse
My x650 shows 87000 in antutu on 030S. I can't know what is reason you having less.
Currently my Le pro 3 ai is on non official 5.9.27s I have to downgrade it to 5.9.25s.what should I do. Further I want to update my device to eui 6.0.30s. Any help is highly appreciated .
I think that is 027s custom rom better than this 028s. I recommend you to not change anything.
Sent from my LEX657 using Tapatalk
AmanS99 said:
Currently my Le pro 3 ai is on non official 5.9.27s I have to downgrade it to 5.9.25s.what should I do. Further I want to update my device to eui 6.0.30s. Any help is highly appreciated .
Click to expand...
Click to collapse
As an example of this way how to move into stock 028S with flashing first 025S and then just update to 028S (or 030S if you want) I prepared a video half of year ago. HERE
I understand that not all processes there are perfect... for example I used ADB to push ROM instead of MTP that is much faster =)
But if you have experience and you sure in other option of processing the steps explained in this video - enjoy and good luck.
Hope it will help somebody.
P.S.: Now I have some trouble with focus (can't focus larger then 120 cm) in stock Camera on EUI 030S and have a plan to get 028S back just for testing of Camera and focus processing.
P.S.2.: If you will have desire to get back into custom 027S you had earlier, you always can make it. It's available on both forums (XDA & 4pda). But you need to know, that changing of using between clean stock and custom ROMs is always requires you to clean a Userspace too.
Thanks for your reply . But I want to ask is there is risk of getting brick if anything goes wrong.