Related
I made this for all the people that seem to be having issues with rooting their phone, installing the recovery partition, and installing the new rom.
This is an all-in-one package. It's about 200MB. Includes the original root rom, recovery image, the new rom (2.1OTA rom that was just released today), as well as a few extras. It's a batch script to automate the entire process.
Here's the README file:
Code:
These are automated scripts to root your Eris phone with Android 1.5 (NOT 2.1 LEAK!!!!!)
YOU NEED THE ANDROID SDK IN ORDER FOR THIS TO WORK!
If you don't have the SDK working, visit guide on the forums for instructions.
INSTRUCTIONS:
Unzip this file to your \tools\ directory of your Android SDK. Then run one of the following files:
install_root.bat
------------------------
This script will do the following:
1) Install the root image onto your phone
2) Install the recovery partition onto your phone
3) Install the current rom using the recovery partition
install_extras.bat
------------------------
This script will do the following:
1) Install live wallpapers
2) Install the Nexus Launcher
3) Install the Nexus photo gallery
4) Remove HTC Lockscreen
5) Install wireless tethering
NOTE!
------------------------
1) NOT ALL LIVE WALLPAPERS YOU FIND IN THE MARKET WILL WORK!
2) You cannot use the Nexus photo gallery when in the Nexus Launcher, it will crash
These scripts were put together by GrdLock.
Credit for all of the included files goes to ivan, amon, jcase, and everyone else
who chipped in!
Install this by unzipping it into your \tools\ directory of your Android SDK, then run install_root.bat.
I'm not running Windows so I didn't test this, but I proof read it like 10 times, and I'm 99.99% sure it should work 100%. If anyone gets any errors using it, post and I'll fix them immediately. Make sure USB debugging is turned on before running it.
You can download the whole package here: http://www.multiupload.com/Y7UC8UU2JE
-------------------------------------------------------------------
If you just want the 2.1OTA rooted rom, you can download that here: http://www.multiupload.com/YP1BIUOF60 (this rom includes busybox, the otacert fix, and a few other minor things)
I also put together an update. This will update you to the new 2.1 OTA leak "official" without wiping. Wipe your dalvik and that's it. Do a nand backup first though just incase! http://www.multiupload.com/3OPZCD6NRA
GrdLock said:
I made this for all the people that seem to be having issues with rooting their phone, installing the recovery partition, and installing the new rom.
This is an all-in-one package. It's about 200MB. Includes the original root rom, recovery image, the new rom (2.1OTA rom that was just released today), as well as a few extras. It's a batch script to automate the entire process.
Here's the README file:
Code:
These are automated scripts to root your Eris phone with Android 1.5 (NOT 2.1 LEAK!!!!!)
YOU NEED THE ANDROID SDK IN ORDER FOR THIS TO WORK!
If you don't have the SDK working, visit guide on the forums for instructions.
INSTRUCTIONS:
Unzip this file to your \tools\ directory of your Android SDK. Then run one of the following files:
install_root.bat
------------------------
This script will do the following:
1) Install the root image onto your phone
2) Install the recovery partition onto your phone
3) Install the current rom using the recovery partition
install_extras.bat
------------------------
This script will do the following:
1) Install live wallpapers
2) Install the Nexus Launcher
3) Install the Nexus photo gallery
4) Remove HTC Lockscreen
5) Install wireless tethering
NOTE!
------------------------
1) NOT ALL LIVE WALLPAPERS YOU FIND IN THE MARKET WILL WORK!
2) You cannot use the Nexus photo gallery when in the Nexus Launcher, it will crash
These scripts were put together by GrdLock.
Credit for all of the included files goes to ivan, amon, jcase, and everyone else
who chipped in!
Install this by unzipping it into your \tools\ directory of your Android SDK, then run install_root.bat.
I'm not running Windows so I didn't test this, but I proof read it like 10 times, and I'm 99.99% sure it should work 100%. If anyone gets any errors using it, post and I'll fix them immediately. Make sure USB debugging is turned on before running it.
You can download the whole package here: http://www.multiupload.com/09DM1FI1D1
md5: 535c300411cd47acd319e667fee8cf16
-------------------------------------------------------------------
If you just want the 2.1OTA rooted rom, you can download that here: http://www.multiupload.com/5HH0H1M4T1 (this rom includes busybox, the otacert fix, and a few other minor things)
md5: 6d95e5e8846c6912fda42c54daa0cb34
I also made a kernel-only update that can be flashed without wiping anything: http://www.sendspace.com/file/5ptpmc
md5: cc4e95034dc7e8adaa776483251952bf
Click to expand...
Click to collapse
Thanks....I will be using this on the wifes (soon to be mine) phone tonite as with the new OTA update I now feel my phone is stable enough for her not to freak out over
appreciate your work....
does the script disable OTA's ?
rvpartsguy said:
Thanks....I will be using this on the wifes (soon to be mine) phone tonite as with the new OTA update I now feel my phone is stable enough for her not to freak out over
appreciate your work....
does the script disable OTA's ?
Click to expand...
Click to collapse
Yes, I built the otacert fix into the rom.
Thanks for all your work grid, and all the others that have worked on this. Just got a new refurb the other day and was going to tackle rooting this weekend, gonna make the task so much easier.
Can you please explain what was fixed? Thanks again for your work.
The current rom is a rooted rom using the new 2.1 leak that was just released today, which is SUPPOSEDLY the "official" 2.1 update from Verizon.
What setting should be used for the phone, HTC Sync, USB, Mount SD, or nothing?
Nothing. Just connect it to your USB, and enable USB debugging. Don't mount your sdcard.
Does the market work now?
(I recall hearing that the market wouldn't work because of the test/dev certificate that was in the leaked rom)
The market will work if it doesnt work now, itll work when the OTA comes out.
Grd, this looks fantastic. I've been patient so far, and haven't upgraded to the leaked or original rooted 2.1 builds, but with the news of the latest one (and initial reports saying that it's mostly bug-free), I'm ready to take the plunge. This should be a huge help to me.
A couple of questions:
Does the big package (the 200MB one) include jcase's ROM (bare-bones basic), or yours with the tweaks? I ask because you mentioned removing pdfviewer, which I use.
Also, has anyone else gone through this process yet? Call me timid, but I'm not too keen on being the first one.
K0CAW said:
Grd, this looks fantastic. I've been patient so far, and haven't upgraded to the leaked or original rooted 2.1 builds, but with the news of the latest one (and initial reports saying that it's mostly bug-free), I'm ready to take the plunge. This should be a huge help to me.
A couple of questions:
Does the big package (the 200MB one) include jcase's ROM (bare-bones basic), or yours with the tweaks? I ask because you mentioned removing pdfviewer, which I use.
Also, has anyone else gone through this process yet? Call me timid, but I'm not too keen on being the first one.
Click to expand...
Click to collapse
It includes my rom. You should be able to restore pdfviewer if you need it though. I can post the files in a bit.
Great. I was pretty sure that the apps could be reinstalled if needed, but wanted to confirm. I'm downloading the package now, so I'll keep you updated. I'm pretty excited about this, since I'm still at stock 1.5.
Issues, Well first It copied the PB image fine, it didnt reboot the phone i had to manually do it with vol -, now im on step two installing amons image, it transfers but it cant start files\flash_image, no such file or directory and then it cant chmod it cause its not there.
Could you copy/paste the command prompt text you're seeing? (you gotta right-click the cmd window and select Mark)
Installing Amon's Recovery Image.
1545 KB/s (3926016 bytes in 2.480s)
cannot stat 'files\flash_image': No such file or directory
Unable to chmod /system/bin/flash_image: No such file or directory
flash_image: not found
-
Finished
Your phone will now reboot and test the recovery partition.
Press any key to continue . . .
Ahh, crap...
http://www.sendspace.com/file/obtx2w
Download that file, put it in the \tools\files\ directory, then try again and let me know.
I think I got delete-happy removing some temp files and deleted flash_image by accident.
Worked great
I just went through the install.bat file and everything worked 100% just as promised. I have not installed any of the extras yet. Thanks for the great work!
flash_image was it worked a treat its in amon_ra now was trying manually and came across it missing, went to post it and you had just now
One suggestion before letting adb copy the 2.1 rooted img to the phone have it delete the PB so users dont accidently click on it. Just a lil cleanup to help things out. So far its flashing 2.1 rooted I will let you know about the first error, ill go back through it again and get it to recreate.
Hi just asking if anyone knows any links or archives or anything i can read through, im looking to build my own ROM. any help would be much appreciated and dont mind donating to someone that can help me start to learn.
Thanks
Well, first of all you need to be able to compile Android. This is pretty easy and it's explained directly in the developers google website. If you're not running a Nexus One or a Nexus S, you can't actually compile a working android copy for your own phone "as is" from AOSP. Because of this, you firstly need to change / create some dirs and files in order to add the support for your particular device. I'd start searching on CM repositories for this (I've got the Nexus One and thus I don't have such problems).
After you've compiled Android for your device and your changes (for example root), you'll have some disk images (you can find them all under out/target/product/PHONE_MODEL/, they are the .img files). You can directly flash them via fastboot ("fastboot flash boot boot.img" etc.). You can though create an update.zip file, and this can be made extracting the system.img file in a folder. Remember that you'll have to recreate the symlinks (to toolbox and/or busybox if you want to include it in your build) and set permissions, as zip doesn't save the permissions of the files once compressed.
Thus so far, if you succeed making every single step you should have your ROM on your phone
Ok since there is a new house of moto and some of the instructions have changed I am deleting the old instructions go here http://www.droidrzr.com/index.php/topic/28162-house-of-moto-20/ and follow Samuri's instructions if you get stuck I will still attempt to help you out I am not going to re write all the instructions again. Trying to piece it together will cause more confusion then help. Please read then re-read his instructions they are all you need after all he created the house of moto. If you cant figure it out pm me or post here and I will try to help the best I can. Here are his instructions for quick reference but you have to got to the above link to download everything.
ALL CREDIT GOES TO SAMURI HL FOR CREATING THIS AWESOME TOOL.
Please do yourself a favor and read, read again, and read one more time before installing and using this tool. If it's set up correctly, it's very easy to use. But if you don't follow directions, it'll either not work or not do what you expect. Failure to read and follow the directions is NOT a defect of the tool!
Mission statement for tool:
This will allow users to have a user friendly framework automation tool for new Motorola devices. Easily customized for any device that allows RSD or fastboot flashing of custom scripts that perform various functions. Most notably is when a user screws something up and the phone no longer boots (so called soft bricking). The KEEP DATA and/or FULL scripts can restore the partitions of the phone to minty factory fresh in the event that your phone doesn't boot.
WARNING: Upgrades from 1.4 are NOT supported. Install CLEAN. You have been warned.
SETUP:
Required Steps
o) You MUST have the latest Motorola USB driver installed: http://lmgtfy.com/?q...rola USB driver
o) Download: HouseOfMoto_2.0.zip
o) Extract the HouseOfMoto folder in the zip to your hard drive. IMPORTANT: Make sure no spaces are in the path. (Windows users should extract it to C:\)
o) Download the support file for your device and extract into your HouseOfMoto directory. (see device support below)
o) Download your FXZ from here: http://sbf.droid-developers.org/ [Site is back, BUT, very limited. It'll take time to repopulate it]
o) Add the FXZ files to your HouseOfMoto\FXZ_xtYYY directory. (see Adding the FXZ below)
Optional Steps
o) If root exists for your device, add the files to the root folder. Make sure run.bat and/or run.sh exists.
CLARIFICATION: When I say "if root exists for your phone" I'm referring to a root exploit that has a run.bat script in order to install root. If that doesn't exist for your phone, or your root exploit does not have a run.bat, this does not apply to you. This is ONLY for adding an option to root your phone to the House of Moto menu as a convenience option. It is NOT a required step.
Linux/Mac Notes:
o) You may need to chmod +x HouseOfMoto.sh
o) You may need to run HouseOfMoto.sh as sudo
Usage:
o) Your phone MUST be in AP Fastboot mode. Try holding volume down and pressing the power button when the phone is off.
o) Run the HouseOfMoto.bat or HouseOfMoto.sh in your HouseOfMoto directory
o) On first run:
Enter your device model (xt926, xt875, etc)
For Windows: Select flash mode: rsd or fastboot
o) Flash mode on Windows can be changed from the main menu
o) Phone model can be changed from the main menu
o) Select the script you wish to flash
o) Follow directions!
Adding the FXZ:
This part confuses a LOT of people so I'm going to use the FXZ for the xt926 as an example of how this should work. Obviously you'll need to use the proper FXZ for your device, but, the concept is generally the same.
This is a point that many get wrong so please follow this carefully...
When you open your VRZ_XT926_9.8.1Q-79-1_CFC.xml.zip file, you will see a directory inside it. You must go INTO the directory inside the zip. There you will see a whole bunch of files. Select them all, and extract them into the FXZ_xt926 folder. All the files must be at the root of the FXZ_xt926 folder, NOT in a sub folder within it. If you have this:
HouseOfMoto\FXZ_xt926\VRZ_XT926_9.8.1Q-79-1_CFC.xml\boot.img
It's wrong. If instead you have this:
HouseOfMoto\FXZ_xt926\boot.img
It's correct.
DEVICE SUPPORT:
o) xt875
o) xt907
o) xt912
o) xt926
o) xt1030
o) xt1080
NOTES:
o) xtYYY is the device model...i.e. xt1058, xt895, etc
DA FAQ:
Q: What flash mode should I pick?
A: Whether you use RSD or fastboot is a personal choice and completely up to you. If you have problems flashing in one mode, you can switch to the other and try again to see if you get better results.
SUPPORT:
If I tell you to create a log and post it, you are to run the CreateLOG.bat file to your c:\HouseOfMoto directory and post the results in this thread.
OP Plz update on Houseofmoto v1.4 when creating the FXZ version only the phone model, (i.e. FXZ_xt1080) Is needed. Also the Thread name needs to be [GUIDE] Return to stock and stickty IMO
You are a Godsend. The House of Moto website was pretty confusing.
Just want to make sure I'm understanding this right. I rooted my Maxx with PwnMyMoto. I also made some modification to allow for wifi tethering. I'm pretty sure I want to return to 100% stock, so that I can receive OTA updates. I can use House of Moto to accomplish this, and my Maxx will be like it was, fresh outta the box?
Ansky11 said:
Just want to make sure I'm understanding this right. I rooted my Maxx with PwnMyMoto. I also made some modification to allow for wifi tethering. I'm pretty sure I want to return to 100% stock, so that I can receive OTA updates. I can use House of Moto to accomplish this, and my Maxx will be like it was, fresh outta the box?
Click to expand...
Click to collapse
Yes what is better is you can choose the save data fxz and it will return you to stock but leave all your apps and data alone.
Which flash mode do we use? Fastboot [snapdragon]?
bigv5150 said:
** Moderators if this is in the wrong forum please move it also be advised I have contacted Samuri and he is fine with me posting this information.
ALL CREDIT GOES TO SamuriHL
Ok guys we have root this is great but I keep seeing guys having problems with installing it jcase has been great in evolving the root apk to accommodate us. I just thought I would try to lend some assistance because I know he is busy and a lot of us aren't as computer savvy as these guys. If you didn't have a bionic then you may not know who Samuri is but he made a tool for bionic owners it was great and very useful. He has since moved on from the bionic but after I contacted him about a tool for the Maxx he as usual came through. He created a Moto tool for several of the new devices and old. It is located here---> http://www.droidrzr.com/index.php/topic/28162-house-of-moto/ This tool will let you fxz full or fxz save data. If you don't know the difference fxz full will wipe the phone to out of the box fresh. Save data will install just the system but not touch your user data ie apps, wallpaper etc. Now to the good news any one that is having an issue still with root download use the above tool and use the fxz save data option it will wipe out root and you can start fresh. It will give you back your stock recovery as well. I had no problem with root but I tested this to make sure it would work. I just re-rooted the whole process took less than 15 minutes.
Below I will give instructions for the laymen if you find the instructions a little confusing in the House of Moto. If you get stuck PM me and I will try to help I am no genius when it comes to this but I have made most of the mistakes and learned from them. If I can't figure it out then you will have to contact the creator Samuri. But be forewarned he has little patience for stupidity. This is the reason I am taking the time to do this to assist him with the less knowledgeable. Remember he no longer owns a moto phone he did this out of the goodness of his heart.
Set up and installation:
1) install the House of Moto 1.2
2) Run it and let it extract to c:\HouseOfMoto it does this automatically
3) Create an FXZ_xxx_xtYYY directory where xxx is the FXZ version (MR4, 98.72.22, etc) and xtYYY is your device (xt926, xt875, etc) it should look like this FXZ_12.7.7_xt1080. You can go here---> http://sbf.droid-developers.org/ and download the FXZ for your device
4) Add the FXZ files to your new FXZ_xxx_xtYYY directory
5) Add the scripts for your device to your rsd_scripts and/or fastboot_scripts directories. See Adding support for an xtYY device. The scripts are at the bottom of the first post under support just find your phone download and execute, it will put them in the proper file in the house of moto.
6) the next step talks about root but we don't need that since we have an apk to re-root so I disregarded this step.
Using the House Of Moto:
1) Run the HouseOfMoto.bat in your c:\HouseOfMoto directory be advised if you make a desktop short cut of the run bat. file it will throw an error stating you need to install rsd which is already installed in the tool. You have to run the House of moto bat. file from within the house of moto folder.
2) On first run: Enter your device model (xt926, xt875, etc) Select flash mode: rsd, fastboot [snapdragon], or fastboot [omap]
3) flash mode can be changed from the main menu
4) device model can be changed from the main menu
5) Select the script you wish to execute ie. Full FXZ Save Data FXZ
6) Follow directions!
There are further instructions in the above thread for creating the FXZ file. I will say this simply when you create the FXZ file it should not have a file folder inside it. Meaning the FXZ file you placed in the House of Moto will say if you have a maxx FXZ_12.7.7_xt1080. When you open this file it shoud contain the whole FXZ not another file you have to open. So extract the FXZ then cut and paste it in the FXZ folder if you don't you will get an error.
This is what your house of moto should look like when you open it:
fastboot_scripts---> will contain Full_xt1080(or whatever phone you use) and Keep-data_xt1080 (or whatever phone you use)
FXZ_12.7.7_xt1080--->again when you open this file you should see the FXZ files not a folder that you have to access.
root
rsd
rsd_scripts---> will contain Full_xt1080(or whatever phone you use) and Keep-data_xt1080 (or whatever phone you use)
utils
flashmode
House of Moto
phone--->you will not see this until you type in what phone you want to use in step 2 above under using the house of moto
Just to sum things up the above tool will put everything where it needs to be except the FXZ that you have to do yourself. Good luck this is truly a useful tool.
One more thing I sent Samuri the xml files for the moto x (verizon and at&t models) also the mini and ultra he said the xml files are so close it was ridiculous. This is a quote from Samuri for being able to use this tool with an ultra mini or moto x
An anonymous donor sent me the xt1030, xt1058, and xt1060 FXZ xml's. They all use the same files as the xt1080 in their respective FXZ's. It's just a matter of me renaming the xt1080 scripts a bunch of times for the different models and packaging them up. Or if people need it before I get them posted, take the xt1080 package and rename the 4 scripts to xt10xx depending on your model and it'll work just fine. Moto's making my life a lot easier that's for sure! In fact I'll write a batch file so that if I ever have to change them for any reason it'll just create them all. LOL.
Click to expand...
Click to collapse
Dammit. I knew I'd be the one idiot.
Followed to the letter and when I run the .BAT, I get :
"Warning: Please check input file. Either XML format is wrong or image files associated with it are missing."
Any ideas that an idiot may be able to follow along with?
FIGURED IT OUT:
Didn't save to C drive. saved it to desktop.
Trying to do this but it seems to fail to install recovery even though it says successful. Tried to download fxz file a couple times and it always gives errors on unpacking, which may be issue.
It was successful at destroying my sim card though.... I have no service now.
One thing to keep in mind that stumped me for a few was the model number. When you go to download the FXZ file the droid maxx is xt1080m. You don't use that as your model number you type into house of moto. Just use xt1080.
Difficulties with howto...
Sorry guys,
I'm having a hell of a time but I have a problem related to this. At current my phone took the OTA while I was rooted and its now boot-looped. I'm trying to revert to the stock firmware, and someone suggested this option. I'm having problems with the step here:
5) Add the scripts for your device to your rsd_scripts and/or fastboot_scripts directories. See Adding support for an xtYY device. The scripts are at the bottom of the first post under support just find your phone download and execute, it will put them in the proper file in the house of moto.
This step is odd, what scripts are you supposed to add to the RSD/Fastboot scripts? Where do I get the scripts? From the FXZ passage?
Qb411 said:
Sorry guys,
I'm having a hell of a time but I have a problem related to this. At current my phone took the OTA while I was rooted and its now boot-looped. I'm trying to revert to the stock firmware, and someone suggested this option. I'm having problems with the step here:
5) Add the scripts for your device to your rsd_scripts and/or fastboot_scripts directories. See Adding support for an xtYY device. The scripts are at the bottom of the first post under support just find your phone download and execute, it will put them in the proper file in the house of moto.
This step is odd, what scripts are you supposed to add to the RSD/Fastboot scripts? Where do I get the scripts? From the FXZ passage?
Click to expand...
Click to collapse
the scripts are near the bottom of the post where you download houseofmoto, scroll down til you see Support in bold. theres a link for xt1080 scripts, just download them and place them in the correct folder.
hmmmm
beelow319 said:
the scripts are near the bottom of the post where you download houseofmoto, scroll down til you see Support in bold. theres a link for xt1080 scripts, just download them and place them in the correct folder.
Click to expand...
Click to collapse
I had trouble with this when I chose fastboot omap and did the "keep data" option. It went through said it flashed stuffs, but I still had root. I changed it to fastboot snapdragon and did it again and then it worked. I have a Droid Maxx and used Pwnmymoto a month ago, which flashed my recovery, thus the need to fixor that.
---------- Post added at 07:07 PM ---------- Previous post was at 06:46 PM ----------
the3dolla said:
I had trouble with this when I chose fastboot omap and did the "keep data" option. It went through said it flashed stuffs, but I still had root. I changed it to fastboot snapdragon and did it again and then it worked. I have a Droid Maxx and used Pwnmymoto a month ago, which flashed my recovery, thus the need to fixor that.
Click to expand...
Click to collapse
Also, just FYI, update went fine and hotspot still works, guess I won't worry about adaway working until an easy root method is found, so I can unroot easier for kitkat.
Just chiming in to say if you all need anything let me know. I've helped a lot of people today get their MAXX back to stock so they can take the ota. Seems to be working once people get it setup properly.
Sent from my Xoom using Tapatalk 4
Post for easy access later.
Sent from my DROID MAXX via Tapatalk 4.
BMWPower06 said:
Which flash mode do we use? Fastboot [snapdragon]?
Click to expand...
Click to collapse
I have the same question.
Kinda stuck. Tried using the flash with data for my XT1080 and the screen says waiting on device. I know i did something wrong but not sure what. Any help would be appreciated.
Device is plugged in via USB. I think I have everything in the right folders. Can I just close the command prompt window without hurting the phone?
Ok I updated the instructions I wrote these instructions with the first house of moto and the naming of the fxz changed. Your FXZ file in house of moto should look like this FXZ_xt1080 or what ever phone you are using not FXZ_12.7.7_xt1080. Sorry for the confusion if you were having a problem with house of moto finding the FXZ this is why.
If this was an issue for anyone I am sorry to be honest I stopped checking this thread a while ago. I created this thread on Sept. 19 and kept trying to tell people to download the tool even if they did not need it, better to safe then sorry. I kept checking but no posts or ?'s so after a month or so seeing no one posting here I figured no one cared or wanted this tool and I forgot about it until I received a pm a few days ago. If you have a question I will try to help but please give me as much info as possible.
bigv5150 said:
Ok I updated the instructions I wrote these instructions with the first house of moto and the naming of the fxz changed. Your FXZ file in house of moto should look like this FXZ_xt1080 or what ever phone you are using not FXZ_12.7.7_xt1080. Sorry for the confusion if you were having a problem with house of moto finding the FXZ this is why.
Click to expand...
Click to collapse
That got me passed my issue. Phone rebooted and now its updating. We'll see what happens from here. Thanks for the update.
In regards to what flash mode to use its rsd for the fxz keep data or full fxz. If you want to run fast boot commands then you would chose fastboot snapdragon.
daca1001 said:
That got me passed my issue. Phone rebooted and now its updating. We'll see what happens from here. Thanks for the update.
Click to expand...
Click to collapse
You should be good now this tool is awesome you will use it again and again trust me. You will do something stupid to your phone and have a DOH!!! moment and this will fix it.
I am attempting to apply an update of stock amazon 4.5.3 on apollo and there are three files being symlinked that are missing from my 3.2.3.2 device. Can anyone be so kind as to provide the following three files?
/data/misc/DxHDCP.cfg
/data/misc/audio/wcd9320_mad_audio.bin
/mnt/sqfs/fonts
The last one is a folder, so if someone could provide the folder and its contents recursively, that would be most helpful.
I don't have an Apollo so can't directly help with your request. However, I believe you need to be at 3.2.6 before upgrading to Sangria vs flashing a complete image. Maybe it's just those 3 files but could be others or different versions of identically named files. Smarter people in these forums can correct if I misspoke.
gbgadgets said:
I am attempting to apply an update of stock amazon 4.5.3 on apollo and there are three files being symlinked that are missing from my 3.2.3.2 device. Can anyone be so kind as to provide the following three files?
/data/misc/DxHDCP.cfg
/data/misc/audio/wcd9320_mad_audio.bin
/mnt/sqfs/fonts
The last one is a folder, so if someone could provide the folder and its contents recursively, that would be most helpful.
Click to expand...
Click to collapse
Did you manage to fix it using my tips?
p1gl3t said:
Did you manage to fix it using my tips?
Click to expand...
Click to collapse
I greatly appreciate the tips!! However, the time I have to mess with the device is quite random. I ended up having a problem restoring a backup and had to format the data, sdcard, etc partitions. I did have the backup also stored on a separate drive, so I got back up and running on a 'close to stock', rooted, xposed, gapps, etc 14.3.2.3.2 version. From there I went ahead and tried to update all but the bootoader to 14.3.2.6. This was successful and so I backed that up. Then I went ahead and re-tried the .zip you had posted for 14.4.5.2, and sure enough it flashed great. So, I am enjoying this fireos with unlocked bootloader, custom recovery, root, and gapps. I am sure I will try cm11, cm12, and aosp lolli as they come out, but for now, things are quite glorious with this device.
The devs around here (you included) are doing amazing things with this stuff. I really appreciate the teaching moments you guys (and gals) share too. What a great community.
Hi All,
I am interested in any ROM, preferably based on LOS, that has no GAPPS pre-installed?
Is there any such? nougat, oreo, and whatever P is... doesn't matter.
A follow-up question for the more technically advanced than I: why is this such a problem for PH1? I believe the PIXEL phones also have A/B partitions, and are supported by LOS
Thanks!
lleo_ said:
Hi All,
I am interested in any ROM, preferably based on LOS, that has no GAPPS pre-installed?
Is there any such? nougat, oreo, and whatever P is... doesn't matter.
A follow-up question for the more technically advanced than I: why is this such a problem for PH1? I believe the PIXEL phones also have A/B partitions, and are supported by LOS
Thanks!
Click to expand...
Click to collapse
The number of developers fixing issues on the pixel vs this phone is astounding...
rignfool said:
The number of developers fixing issues on the pixel vs this phone is astounding...
Click to expand...
Click to collapse
I do recognize that, but given similarities between devices, would not be possible to adopt the work done by those developers. Granted that I ask this with the knowledge of a noob.
To follow up are you saying that there is no such as GAPPS-less ROM for PH1?
lleo_ said:
I do recognize that, but given similarities between devices, would not be possible to adopt the work done by those developers. Granted that I ask this with the knowledge of a noob.
To follow up are you saying that there is no such as GAPPS-less ROM for PH1?
Click to expand...
Click to collapse
There are... But they come and go as far as updates and such...
The demand is for Google... And moar features without losing Google...
Now... What you can do/try is wander over to the Project Trebble area... I would assume that you will find a plethora of development...
You're gonna be wading in some unknown territory... And it'll be a mystery as to what works... And whether it's fixable... Good luck
EDIT: or... You can magisk yourself... And try NanoMod... I think that disables a ton of Google stuff and puts FOSS stuff in it's place...
Sir! Thank You for your post. At first I thought it was a joke, but I learned something today. The concept and related work of project Treble bypassed me. I have already a GApps-less LOS on my Ph1. Again thanks!
Don't know if this applies, but lots of ppl are successfully running GSIs on the Essential.
Maybe some of them are GAPP-less?
@lleo_ another thing you can always do, is run Stock Android and Debloat it and run it Gapp Free, just like any custom rom...
As they say YMMV (Your Mileage May Vary), and I found Stock Oreo to be more stable on the Essential, so I debloated it, made it Deodex and patched for Signature Spoofing and of course Gapp Free. I still have the Gboard, Contacts, Messeges, and Phone, but these can be removed and replaced easily, any and everything Google can be taken out.
See the screen shot...
DoR3M3 said:
@lleo_ another thing you can always do, is run Stock Android and Debloat it and run it Gapp Free, just like any custom rom...
As they say YMMV (Your Mileage May Vary), and I found Stock Oreo to be more stable on the Essential, so I debloated it, made it Deodex and patched for Signature Spoofing and of course Gapp Free. I still have the Gboard, Contacts, Messeges, and Phone, but these can be removed and replaced easily, any and everything Google can be taken out.
See the screen shot...
Click to expand...
Click to collapse
Hey can you explain how to debloat, is there a script for it. How do you patch it and deodex it.
Thanks
arjunv said:
Hey can you explain how to debloat, is there a script for it. How do you patch it and deodex it.
Thanks
Click to expand...
Click to collapse
These steps below, you're probably going to wonder, why do I need to Deodex and Signature Spoof just to debloat? Good point, you don't, but then you can only get so far away from Google in your system by not doing this. The point to this method is to have Signature Spoofing support in Android, where you can better utilize microg support, to have it as the alternative instead of Google.
The Deodex and Nanodroid-patcher support, only need to be performed if you are running Stock Android, or a ROM that has not been Deodex and doesn't support Signature Spoofing. This also doesn't have to be done, if you still want to run the Google Services/Framework.
If you only want to Debloat, then follow the Debloat section below.
For the Deodex, YMMV (Your Mileage May Vary), but it's been working great for me, so here goes!
I did this on Stock Oreo 8.1.0 which has both odex and vdex files in /system/framework, so I followed the VDEX method mentioned below.
This is going to be easy if you're a Linux User/Geek, if you are running Windows and have never done anything like this, and if you have both odex and vdex files on your phone in /system/framework, then I can do this for you if you want, unless you want to get into learning this.
If you want me to, then in TWRP, click Mount and click on System at the top to mount it and then run this command in the command prompt, I'm assuming you have adb/fastboot installed...
adb pull /system/framework framework If that doesn't work, it typically ends up being, adb pull /system/system/framework framework
I'm assuming your device is arm64, so then look in the directory; framework/oat/arm64/ or /arm, and attach the services.vdex file and I'll patch it for you.
Deodex & Signature Spoofing
1. Check /system/framework, do you see both .odex and .vdex files?
2. If you have both .odex and .vdex files follow the guide under VDEX, if you only have .odex files, then follow the ODEX section. Don't be confused by the guide as only having either services.vdex or services.odex. You are looking to see if all the files are one or the other or both.
https://gitlab.com/Nanolx/NanoDroid/blob/master/doc/DeodexServices.md
3. If you have both files and need to follow the VDEX method in Windows, then you'll need cygwin as stated on the vdexExtractor Github, and install zlib-devel from the cygwin installer. cygwin as stated on the site is a collection of GNU and Open Source tools, this allows you to compile the vdexExtractor source in Windows into the running program.
https://www.cygwin.com/
4. If you have to do the ODEX method the baksmali.jar and smali.jar are already built, there's a download for them on the GitHub page, and you'll need to have Java JRE installed.
http://www.oracle.com/technetwork/java/javase/downloads/jre8-downloads-2133155.html
Whether I'm patching it, or you follow one of the methods I've described, once this is done, you'll need to download the latest NanoDroid-patcher. This is what patches the Deodex ROM to apply signature spoofing support.
https://forum.xda-developers.com/apps/magisk/module-nanomod-5-0-20170405-microg-t3584928 - Stable Download (Nanolx)
Be sure to also grab NanoDroid-fdroid if you don't have F-droid installed. You might want to also grab NanoDroid-microG while you're at it, if you want to go for a real system Google Debloat too, but any concerns, or issues, please post on Setialpha's NanoDroid post for any microg support.
As soon as you're done with the Deodex steps, at the bottom the tutorials clearly state; unmount /system and flash the NanoDroid-Patcher, so uncheck System that you checked before in Mount, and now install/flash NanoDroid-patcher, TWRP > Install
If the device is not rooted, then make sure to root it with Magisk. Personally I find it best with the Essential to now boot to the bootloader, then boot back into TWRP. In TWRP flash NanoDroid-fdroid if you grabbed it, then the boot.img and then Magisk, then boot into the System.
Debloating Apps Systemlessly
1. Open Magisk Manager - Downloads - search for Debloater, then you should see Debloater (Terminal Emulator).
2. Reboot
3. Now you'll need a terminal emulator in Android because Debloater (Terminal Emulator) runs from the command line, it doesn't have a GUI. I recommend using Termux, it's a very powerful terminal emulator with lots of things going on about it. If you didn't install F-Droid as I mentioned before, then you should of noticed on the NanoDroid download link NanoDroid-fdroid, download this and flash/install it in TWRP.
4. Now with F-Droid, open it, go to Settings and turn on Expert mode and check Privileged Extension, then close and reopen F-Droid. Next, search for and install Termux.
5. Open Termux and at the command prompt type su for superuser access. On a side note, if you don't know, or have never used Termux, press and hold Vol UP on the phone and tap q on the keyboard which will give you some short cut options. But you'll want to go online to their Wiki and learn about the power of Termux.
6. Now simply type debloat and remove what you want. Remember if you make a mistake, you have Option 4 to reinstall what you removed by mistake.
That's all there is to Deodex, Signature Spoof Patching and Debloating apps systemlessly in Android.
If the VDEX/ODEX methods don't work for some strange reason, then you'll want to explore using SuperR's Kitchen to Deodex the rom, and most people recommend you get the donate version for better features and support.
https://forum.xda-developers.com/ap...dows-linux-superr-s-kitchen-v3-0-0-0-t3601702
Good Luck
DoR3M3 said:
These steps below, you're probably going to wonder, why do I need to Deodex and Signature Spoof just to debloat? Good point, you don't, but then you can only get so far away from Google in your system by not doing this. The point to this method is to have Signature Spoofing support in Android, where you can better utilize microg support, to have it as the alternative instead of Google.
The Deodex and Nanodroid-patcher support, only need to be performed if you are running Stock Android, or a ROM that has not been Deodex and doesn't support Signature Spoofing. This also doesn't have to be done, if you still want to run the Google Services/Framework.
If you only want to Debloat, then follow the Debloat section below.
For the Deodex, YMMV (Your Mileage May Vary), but it's been working great for me, so here goes!
I did this on Stock Oreo 8.1.0 which has both odex and vdex files in /system/framework, so I followed the VDEX method mentioned below.
This is going to be easy if you're a Linux User/Geek, if you are running Windows and have never done anything like this, and if you have both odex and vdex files on your phone in /system/framework, then I can do this for you if you want, unless you want to get into learning this.
If you want me to, then in TWRP, click Mount and click on System at the top to mount it and then run this command in the command prompt, I'm assuming you have adb/fastboot installed...
adb pull /system/framework framework If that doesn't work, it typically ends up being, adb pull /system/system/framework framework
I'm assuming your device is arm64, so then look in the directory; framework/oat/arm64/ or /arm, and attach the services.vdex file and I'll patch it for you.
Deodex & Signature Spoofing
1. Check /system/framework, do you see both .odex and .vdex files?
2. If you have both .odex and .vdex files follow the guide under VDEX, if you only have .odex files, then follow the ODEX section. Don't be confused by the guide as only have either services.vdex or services.odex. You are looking to see if all the files are one or the other or both.
https://gitlab.com/Nanolx/NanoDroid/blob/master/doc/DeodexServices.md
3. If you have both files and need to follow the VDEX method in Windows, then you'll need cygwin as stated on the vdexExtractor Github, and install zlib-devel from the cygwin installer. cygwin as stated on the site is a collection of GNU and Open Source tools, this allows you to compile the vdexExtractor source in Windows into the running program.
https://www.cygwin.com/
4. If you have to do the ODEX method the baksmali.jar and smali.jar are already built, there's a download for them on the GitHub page, and you'll need to have Java JRE installed.
http://www.oracle.com/technetwork/java/javase/downloads/jre8-downloads-2133155.html
Whether I'm patching it, or you follow one of the methods I've described, once this is done, you'll need to download the latest NanoDroid-patcher. This is what patches the Deodex ROM to apply signature spoofing support.
https://forum.xda-developers.com/apps/magisk/module-nanomod-5-0-20170405-microg-t3584928 - Stable Download (Nanolx)
Be sure to also grab NanoDroid-fdroid if you don't have F-droid installed. You might want to also grab NanoDroid-microG while you're at it, if you want to go for a real system Google Debloat too, but any concerns, or issues, please post on Setialpha's NanoDroid post for any microg support.
As soon as you're done with the Deodex steps, at the bottom the tutorials clearly state; unmount /system and flash the NanoDroid-Patcher, so uncheck System that you checked before in Mount, and now install/flash NanoDroid-patcher, TWRP > Install
If the device is not rooted, then make sure to root it with Magisk. Personally I find it best with the Essential to now boot to the bootloader, then boot back into TWRP. In TWRP flash NanoDroid-fdroid if you grabbed it, then the boot.img and then Magisk, then boot into the System.
Debloating Apps Systemlessly
1. Open Magisk Manager - Downloads - search for Debloater, then you should see Debloater (Terminal Emulator).
2. Reboot
3. Now you'll need a terminal emulator in Android because Debloater (Terminal Emulator) runs from the command line, it doesn't have a GUI. I recommend using Termux, it's a very powerful terminal emulator with lots of things going on about it. If you didn't install F-Droid as I mentioned before, then you should of noticed on the NanoDroid download link NanoDroid-fdroid, download this and flash/install it in TWRP.
4. Now with F-Droid, open it, go to Settings and turn on Expert mode and check Privileged Extension, then close and reopen F-Droid. Next, search for and install Termux.
5. Open Termux and at the command prompt type su for superuser access. On a side note, if you don't know, or have never used Termux, press and hold Vol UP on the phone and tap q on the keyboard which will give you some short cut options. But you'll want to go online to their Wiki and learn about the power of Termux.
6. Now simply type debloat and remove what you want. Remember if you make a mistake, you have Option 4 to reinstall what you removed by mistake.
That's all there is to Deodex, Signature Spoof Patching and Debloating apps systemlessly in Android.
If the VDEX/ODEX methods don't work for some strange reason, then you'll want to explore using SuperR's Kitchen to Deodex the rom, and most people recommend you get the donate version for better features and support.
https://forum.xda-developers.com/ap...dows-linux-superr-s-kitchen-v3-0-0-0-t3601702
Good Luck
Click to expand...
Click to collapse
Thank you so much for a detailed post
DoR3M3 said:
@lleo_ another thing you can always do, is run Stock Android and Debloat it and run it Gapp Free, just like any custom rom...
As they say YMMV (Your Mileage May Vary), and I found Stock Oreo to be more stable on the Essential, so I debloated it, made it Deodex and patched for Signature Spoofing and of course Gapp Free. I still have the Gboard, Contacts, Messeges, and Phone, but these can be removed and replaced easily, any and everything Google can be taken out.
See the screen shot...
Click to expand...
Click to collapse
Stoked to see two things here...1.) the answer to the question I was searching for about running my Essential with no gapps...and 2.) your choice in file explorers!