Debloated Rom For The Fire TV Stick 4K 6.2.7.1 93/6.2.7.7 Revised
NOTE: Firmware versions after 6.2.7.7 will not work with this debloated rom. It's been a few months since I've updated this guide so be cautious with installing this. The latest fw implements an efuse to prevent downgrading.
IMPORTANT!!!
NEVER FLASH A STOCK ROM >= 6.2.8.0 AFTER FLASHING 6.2.8.1_r2 OR LATER! THIS WILL BLOW AN EFUSE.
Steps: Boot into TWRP from either the OTG cable or through an ADB command by enabling ADB debugging in My Fire TV, Developer Options. After booting into TWRP, make sure to wipe system, dalvik, and cache before flashing but before doing any of that take a backup of the system image, vendor image, boot and finally your data. After restoring remember Amazon will automatically have a verification to sign you in again because of security reasons.
XDA:DevDB Information
Debloated Rom For Fire TV Stick 4K (6.2.7.1 93/6.2.7.7)
Contributors
Skel40
ROM OS Version: 6.2.7.7 Debloated Rom. Based off the Stock Image of 6.2.7.1/93. 6.2.7.7 Pre-rooted Image.
ROM Firmware Required: 6.2.7.7 and less, efuse is now blown in version 6.2.8.0
Version Information
6.2.7.7 Revised
Debloated Latest Rom with 146 applications left out of the 171 installed with this new version found in /system/priv-app. The folder lists the removed files along with built in build.prop tweaks. (New) I moved the rom to MEGA for easier access. A little bit more packages have been added back for stability reasons. The package, com.amazon.tv.turnstile is the problem when pairing remotes so the issue is fixed!
6.2.7.1 93
Debloated Rom with 126 applications in priv-app, same information as above. With Build.prop Tweaks and no boot animation on reboot. Read the Changelog in the 6.2.7.1 93 Rom below for more information in the Removed Files Folder.
Issues: Prime Video is still having problems downloading and installing an additional app after installing it from the Amazon Appstore. The incremental updates won't work on 6.2.7.1 93 because of attempting to update to 6.2.7.7
Current Stable Version: Revised Version 1.1 6.2.7.7
Stable Release Date: 2021-01-04 (6.2.7.7 revised)
Created 2020-04-18
Last Updated 2021-01-04
Debloated Rom 6.2.7.1 93 with Removed Files: https://drive.google.com/drive/folders/1bmZwmkyJw4e7Y9cjtiAfdr0KuQnA-CHK?usp=sharing
Debloated Rom 6.2.7.7 MEGA Revised 1.1
642.99 MB folder on MEGA
36 files and 45 subfolders
mega.nz
Changelog of 6.2.7.1 93
With this downgraded release of 6.2.7.1 93, expect a few problems with several packages that I've removed for a reason:
Changelog of the 6.2.7.1 93 Debloated Version (FTVLaunchX/Accessibility features are working)
The apps that aren't working is solely because of the missing "System Components" update
* Amazon FreeTime won't work
* IMDB won't work (Use the Free section on the Fire TV Home UI for Free Movies/TV)
* News won't work
* Updating won't go through unless you choose to upgrade to the latest OS (Meaning it'll keep downloading 6.2.7.7 but will fail because of otacerts.zip being removed)
* Build.prop Tweaks are added to this rom, use a computer to transfer the prop file if you choose not to have the tweaks yourself.(My post can be found here: https://forum.xda-developers.com/fire-tv/general/fire-tv-stick-4k-tweaks-root-keyboard-t4064269)
* Make a TWRP backup before flashing this rom of the following partitions: System Image, Boot, Data, and Vendor Image in case you want to go back however you want
* Most of things if not many of the packages and files are gone for maximum storage as possible (Removed Files can be found on the OP of this page)
* Please note that the mbcache.db file is a storage decreaser, use these commands for chmod 0 and make the file frozen with 0 MB
adb connect 192.168.x.x (change it to your IP)
adb shell
su
cd /data/data/com.amazon.tv.launcher/databases
rm mbcache.db*
touch mbcache.db
touch mbcache.db-shm
touch mbcache.db-wal
chmod 0 mbcache.db*
ls-all
To re-enable
adb connect 192.168.1.101 (change it to your IP)
adb shell
su
cd /data/data/com.amazon.tv.launcher/databases
rm mbcache.db*
touch mbcache.db
touch mbcache.db-shm
touch mbcache.db-wal
chmod 660 *.db
chmod 600 *.db-*
* All three files are zeros. Reboot and you'll now see more increased storage.
* Amazon Home will throw an error so enable Do Not Disturb in Settings
* Magisk is pre-installed, and the System is in RW mode.
* The Setup Wizard SHOULD go through no matter what. No need to worry about being stuck
Changelog of 6.2.7.7 Revised
* Magisk is pre-installed, and the System is also in RW mode.
*Priv-app, app, and media have been modified for debloating with a list of every file I've removed and being able to download the removed files as an apk without unzipping.
*Added Build tweaks except for the no boot animation
*Added packages back for stability
This guide is outdated but can still be flashed with this neat trick I learned from AFTVnews' guide about VoiceView found here:
How to Skip Software Updates during Initial Setup or Factory Reset on a Fire TV, Firestick, or Fire TV Cube
Since the latest software update for Fire TV devices is blocking the ability to use custom launchers, you may want to avoid updating a new or factory reset Fire TV.
www.aftvnews.com
I've pulled the 1.2 version to see what's wrong with the rom. Wip will be soon when I have time available
So far everything seems good .
Can you write the command to make a Backup
An how to restore over adb shell?
0815hoffi said:
Can you write the command to make a Backup
An how to restore over adb shell?
Click to expand...
Click to collapse
I just used a usb mouse hooked to a little hub I got off Amazon for about 6 or 7 dollars to use TWRP
Ok.
Thanks
0815hoffi said:
Ok.
Thanks
Click to expand...
Click to collapse
I used this one : https://www.amazon.com/gp/product/B07SZTHPPR/ref=ppx_yo_dt_b_asin_title_o07_s00?ie=UTF8&psc=1
I have been using your rom and it seems real snappy and smooth. So far no problems.
brick00444 said:
Tried it and am stuck on black fire tv screen. I will unbrick and try again in a bit.
Got it going, I wasn't on the 6.2.7.1 the first time and it didn't work. Updated using the 6.2.7.1 rom you posted in another thread then used your backup. So far everything seems good .
Click to expand...
Click to collapse
Maybe Skel40 should add a boot.img (suitable to his rom backup), in order to avoid such problems.
Sus_i said:
Maybe Skel40 should add a boot.img (suitable to his rom backup), in order to avoid such problems.
Click to expand...
Click to collapse
Updated the OP with the boot.img on Google Drive! Thank you!
brick00444 said:
Tried it and am stuck on black fire tv screen. I will unbrick and try again in a bit.
Got it going, I wasn't on the 6.2.7.1 the first time and it didn't work. Updated using the 6.2.7.1 rom you posted in another thread then used your backup. So far everything seems good .
Click to expand...
Click to collapse
Ok flashing the rom I posted on the other forum with this backup erases the modifications done for debloating due to the zip acting like its an update therefore re-adds the deleted apps I deleted myself!!!!! Try downloading the boot.emmc.win and boot.emmc.win.sha2 with the debloated rom you downloaded, and restore the boot.img along with the system image, vendor image. (Put the boot.emmc.win and boot.emmc.win.sha2 inside the ftvs4kdebloatedv1.0 folder IF downloaded already) Before doing this, wipe /system, data, and cache THEN restore the system image, vendor image, and boot! Get back to me as soon as possible!!!!
Skel40 said:
Ok flashing the rom I posted on the other forum with this backup erases the modifications done for debloating due to the zip acting like its an update therefore re-adds the deleted apps I deleted myself!!!!! Try downloading the boot.emmc.win and boot.emmc.win.sha2 with the debloated rom you downloaded, and restore the boot.img along with the system image, vendor image. (Put the boot.emmc.win and boot.emmc.win.sha2 inside the ftvs4kdebloatedv1.0 folder IF downloaded already) Before doing this, wipe /system, data, and cache THEN restore the system image, vendor image, and boot! Get back to me as soon as possible!!!!
Click to expand...
Click to collapse
The first time I tried it, I was on an older rom version. When I used your backup it was stuck at the black fire tv screen. I was able to get into TWRP and flash your 6.2.7.1 rom you posted then used your backup and it worked great. I should have made that clear. Sorry for that. That being said, with the new files you listed can a person use your backup on another rom version " say 6.2.6.8 " or should it be on 6.2.7.1.? I have another 4k stick I might have time tomorrow to test the new method on.
brick00444 said:
Twith the new files you listed can a person use your backup on another rom version " say 6.2.6.8 " or should it be on 6.2.7.1.? I have another 4k stick I might have time tomorrow to test the new method on.
Click to expand...
Click to collapse
A backup with boot.img should work, without it won't.
Can it be restored without otg .
Twrp Commandline?
Sus_i said:
A backup with boot.img should work, without it won't.
Click to expand...
Click to collapse
Thank you
Have tried this rom to pass updating configuration screen on my Fire TV 4k without success. Restored this rom from TWRP without a problem but stucked again at configuration updating screen.
WarrenDen said:
Have tried this rom to pass updating configuration screen on my Fire TV 4k without success. Restored this rom from TWRP without a problem but stucked again at configuration updating screen.
Click to expand...
Click to collapse
Any solution to skip updating screen?
Yes you must decompile com.amazon.tv.oobe.apk
with APK Easy Tool.
!!!!! For Sure save a backup of this file !!!!
and customize NativePageProvider.smali file
Replace the Update command like
Lines
??????? 》with NOP
example attached , decompile it and compare the file to understand how it works
than compile with APK Easy Tool and replace the file over twrp.
------‐-----------'
Easy way delete com.amazon.tv.oobe.apk over twrp.
Pair remote with use of TV-CEC Remote.
An then do the Configuration.
But then it is not possible to enable adb over the settings.
Can be done in twrp maybe.
in TWRP type:
echo -n 'mtp,adb' > /data/property/persist.sys.usb.config
echo '' >> /system/build.prop
echo '# Enable ADB' >> /system/build.prop
echo 'persist.service.adb.enable=1' >> /system/build.prop
echo 'persist.service.debuggable=1' >> /system/build.prop
echo 'persist.sys.usb.config=mtp,adb' >> /system/build.prop
Reboot
Do it at your own Risk!!!!!
If it works, run.
adb shell settings put global setup_wizard_has_run 1
adb shell settings put secure user_setup_complete 1
adb shell settings put global device_provisioned 1
To set oobe succesfully run.
----‐---------
Own Risk you can try replace com.amazon.tv.oobe.apk with the attached file, run the Setup Wizard and After that copy back the backuped com.amazon.tv.oobe.apk to /system/priv-app/com.amazon.tv.oobe/com.amazon.tv.oobe.apk
0815hoffi said:
Yes you must decompile com.amazon.tv.oobe.apk
with APK Easy Tool.
!!!!! For Sure save a backup of this file !!!!
and customize NativePageProvider.smali file
Replace the Update command like
Lines
??????? 》with NOP
example attached , decompile it and compare the file to understand how it works
than compile with APK Easy Tool and replace the file over twrp.
------‐-----------'
Easy way delete com.amazon.tv.oobe.apk over twrp.
Pair remote with use of TV-CEC Remote.
An then do the Configuration.
But then it is not possible to enable adb over the settings.
Can be done in twrp maybe.
in TWRP type:
echo -n 'mtp,adb' > /data/property/persist.sys.usb.config
echo '' >> /system/build.prop
echo '# Enable ADB' >> /system/build.prop
echo 'persist.service.adb.enable=1' >> /system/build.prop
echo 'persist.service.debuggable=1' >> /system/build.prop
echo 'persist.sys.usb.config=mtp,adb' >> /system/build.prop
Reboot
Do it at your own Risk!!!!!
If it works, run.
adb shell settings put global setup_wizard_has_run 1
adb shell settings put secure user_setup_complete 1
adb shell settings put global device_provisioned 1
To set oobe succesfully run.
----‐---------
Own Risk you can try replace com.amazon.tv.oobe.apk with the attached file, run the Setup Wizard and After that copy back the backuped com.amazon.tv.oobe.apk to /system/priv-app/com.amazon.tv.oobe/com.amazon.tv.oobe.apk
Click to expand...
Click to collapse
Should work even for 4k Fire TV? Or only for 2 gen?
@dadme
I have played around this with 4k , and it works.
But with the Restrictions i Described.
This i have testet 4k.
Flashable 4k Twrp zip attached.
It delete oobe and amazon launcher and install leanbacklauncher.
try it at your own risk
Error in zip fixed, please redownload
0815hoffi said:
@dadme
I have played around this with 4k , and it works.
But with the Restrictions i Described.
This i have testet 4k.
Flashable 4k Twrp zip attached.
It delete oobe and amazon launcher and install leanbacklauncher.
try it at your own risk
Click to expand...
Click to collapse
Thanks for the info! I make a try on the weekend. Restrictions.. I don;t have Amazon Prime... Just for Kodi and HBO Go. And mirroring phone display..
That would be another question. In case of an software update, the process of decompile and patching will probably have to be restarted?
Related
Since removing ads from browser and apps was one of the main reasons to root my DX I decided to make this tutorial. Problem is you can't just install AdAway (link) and run it because after a reboot you'll have to do it again. This method is keeping the ads away even after a reboot. Remember that you'll have to update AdAway-hosts files regularly.
All credits go to Yasir Javed Ansari. I only finetuned the method he described a little bit. Because his post is somewhere in another thread it seemed right to make a tutorial for it in the themes and apps section.
First of all you'll need a properly rooted DX with superuser 3.1.3 installed. See here for a zip to install superuser and busybox or here to download a pre-rooted 1.18 stock deodexed rom with superuser and busybux installed provided by infernal77. I'm using this rom on my DX and removed a lot of bloatware with Aroma (link) right after flashing the rom. Credits go to merovig for sharing info about flashable superuser/busybox-zip and Aroma and of course to infernal77 for providing his deodexed stock rom. Although it seems that this method shouldn't be necessary when using a deodexed rom I couldn't get it to work without using the command lines, so I decided to share it anyway.
In settings - power, uncheck 'fast boot'.
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/data/hosts'.
Reboot to recovery and then mount /system and mount /data.
While in recovery-mode connect the device to a PC and open a command prompt.
Type:
adb shell
cd system/etc
rm hosts
ln -s /data/data/hosts hosts
Disconnect the device from PC and reboot.
Now you can run AdAway: download files and apply ad blocking.
Done!
Nice one, added to Index.
@op, Good job.
Although my tutorial was word by word the same, apart from maybe few spelling mistakes. ;p
Above is required for Stock Rom which is rooted.
On custom and rooted Rom , you don't need to perform above steps as system is write permitted so running ad away normally works fine.
Regards
Yasir
Sent from my HTC Desire X
Hehe I know, the only thing I added was the /etc
Problem is that when I install for example infernals rooted stock deodexed rom, and then I install AdAway and hosts files, they don't survive a reboot. When I redirect the hosts file to /data/data/hosts AdAway states it can't create the symlink. That's why I still use your method even on a pre-rooted rom.
nightcrow said:
Hehe I know, the only thing I added was the /etc
Problem is that when I install for example infernals rooted stock deodexed rom, and then I install AdAway and hosts files, they don't survive a reboot. When I redirect the hosts file to /data/data/hosts AdAway states it can't create the symlink. That's why I still use your method even on a pre-rooted rom.
Click to expand...
Click to collapse
This symlink method(not mine) is present in ad away FAQs. So credit to the app team.
Sent from my HTC Desire X
Nice guide, first time I'm adfree, even after a reboot
did anyone get it working on desire x... mine still shows ads in apps...
I don't know, after all I'm an amateur, but the problem nightcrow described about how stuff goes back to stock after a reboot is something that happens a lot with the DX's - same thing with the bloatware. I had to remove the bloat apps from a rom.zip and flash that to avoid the problem. Seems to me there is some kind of security built in that goes beyond the norm. Otherwise I don't see why apps like Titanium work to remove apps (even after reboot) for example on most other phones, but not the DX.
Meherzad, I followed the instructions posted by nightcrow and it works for me ... try again, reboot and open an app you know normally has ads to check if it works.
Failed first time (forgot to uncheck fast boot:banghead. Reinstalled and did everything again, now works flawlesly.
ok.. working great......
nightcrow said:
Since removing ads from browser and apps was one of the main reasons to root my DX I decided to make this tutorial. Problem is you can't just install AdAway (link) and run it because after a reboot you'll have to do it again. This method is keeping the ads away even after a reboot. Remember that you'll have to update AdAway-hosts files regularly.
All credits go to Yasir Javed Ansari. I only finetuned the method he described a little bit. Because his post is somewhere in another thread it seemed right to make a tutorial for it in the themes and apps section.
First of all you'll need a properly rooted DX with superuser 3.1.3 installed. See here for a zip to install superuser and busybox or here to download a pre-rooted 1.18 stock deodexed rom with superuser and busybux installed provided by infernal77. I'm using this rom on my DX and removed a lot of bloatware with Aroma (link) right after flashing the rom. Credits go to merovig for sharing info about flashable superuser/busybox-zip and Aroma and of course to infernal77 for providing his deodexed stock rom. Although it seems that this method shouldn't be necessary when using a deodexed rom I couldn't get it to work without using the command lines, so I decided to share it anyway.
In settings - power, uncheck 'fast boot'.
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/data/hosts'.
Reboot to recovery and then mount /system and mount /data.
While in recovery-mode connect the device to a PC and open a command prompt.
Type:
adb shell
cd system/etc
rm hosts
ln -s /data/data/hosts hosts
Disconnect the device from PC and reboot.
Now you can run AdAway: download files and apply ad blocking.
Done!
Click to expand...
Click to collapse
have no idea how to write in command prompt
umo4u said:
have no idea how to write in command prompt
Click to expand...
Click to collapse
Windows button+R>Type cmd>enter
It doesn´t works for me...It may wont work because i have superuser v3.2?
Might be but I'm not sure. I'm on 3.1.3 and it works fine. Although getting ADB to work in twrp recovery is a bit of a struggle for now.
What exactly doesn't work for you?
nightcrow said:
Might be but I'm not sure. I'm on 3.1.3 and it works fine. Although getting ADB to work in twrp recovery is a bit of a struggle for now.
What exactly doesn't work for you?
Click to expand...
Click to collapse
you can do same in advanced-> execute command (or maybe shell - do not remember the exact naming)
adb was not working for me, too.
nightcrow said:
Might be but I'm not sure. I'm on 3.1.3 and it works fine. Although getting ADB to work in twrp recovery is a bit of a struggle for now.
What exactly doesn't work for you?
Click to expand...
Click to collapse
Why do you need ADB when you have TERMINAL in twrp. Just wondering
Anyhow, ADB will be fixed soon
Thanks for the tutorial works great with Superuser 3.2. Just to clarify something, should I leave "fast boot" mode off now?
Michael
michpan said:
Thanks for the tutorial works great with Superuser 3.2. Just to clarify something, should I leave "fast boot" mode off now?
Michael
Click to expand...
Click to collapse
I think you can turn it on.
If you'll not access recovery... when you need recovery, turn fast boot off...
Sent from my hTC branded muffin
Tried every method...but I'm unable you protect my backups in titanium backup
To protect*
How I solved this problem on my Moto G LTE
Shantanu Baviskar said:
Tried every method...but I'm unable you protect my backups in titanium backup
Click to expand...
Click to collapse
I carefully read this thread: [Help] Titanium Backup PRO - protected archive not working.
So I modified file /system/etc/permissions/platform.xml according http://jrummy-apps.com/fix-sdcard-on-kitkat/ and make new file /data/local/userinit.sh with this content:
Code:
#!/system/bin/sh
busybox mount -o remount,rw /
chmod 770 /mnt/media_rw
See the attached archive root.zip which I made for you it is pretty straightforward.
You should have move your TiB backup folder on this path: /mnt/media_rw/sdcard1/TitaniumBackup
You will be able to protect backup archives in Titanium Backup Pro then.
PS: If /data/local/userinit.sh doesn't start automatically in your ROM you can use for example Scripter feature in ROM Toolbox Pro and import userinit.sh script and set it as Start at boot.
_jis_ said:
I carefully read this thread: [Help] Titanium Backup PRO - protected archive not working.
So I modified file /system/etc/permissions/platform.xml according http://jrummy-apps.com/fix-sdcard-on-kitkat/ and make new file /data/local/userinit.sh with this content:
Code:
#!/system/bin/sh
busybox mount -o remount,rw /
chmod 770 /mnt/media_rw
See the attached archive root.zip which I made for you it is pretty straightforward.
You should have move your TiB backup folder on this path: /mnt/media_rw/sdcard1/TitaniumBackup
You will be able to protect backup archives in Titanium Backup Pro then.
PS: If /data/local/userinit.sh doesn't start automatically in your ROM you can use for example Scripter feature in ROM Toolbox Pro and import userinit.sh script and set it as Start at boot.
Click to expand...
Click to collapse
Although in the case of Note 4 it didn't work right off the bat, I made it work a little different thanks to your idea. For some weird reason the script just doesn't get executed at boot (neither the *.sh file, nor as a script, through ROM Toolbox) but I was able to use the 2 lines in the script and made a task (in Tasker) which executes the shell command at boot. Everything else is straight forward and TiBu can now protect backups.
As a mention for those interested in replicating all these: the suggested SD card fix made by rummy applies EXACTLY the same changes as the SDFix so you can use either of them. Again, thanks for your reply and the great idea! :good:
nacos said:
I was able to use the 2 lines in the script and made a task (in Tasker) which executes the shell command at boot. Everything else is straight forward and TiBu can now protect backups.
Click to expand...
Click to collapse
Great, this is another example how to execute script at boot
I solved this problem on all my phones (Moto G LTE and Samsung Galaxy Note 2 and Samsung Galaxy W) but not on my tablet Nexus 7 2013 nor on internal emulated SD card nor on attached OTG USB flash disk. This is example where pure Stock Google Android ROM sucks
_jis_ said:
Great, this is another example how to execute script at boot
I solved this problem on all my phones (Moto G LTE and Samsung Galaxy Note 2 and Samsung Galaxy W) but not on my tablet Nexus 7 2013 nor on internal emulated SD card nor on attached OTG USB flash disk. This is example where pure Stock Google Android ROM sucks
Click to expand...
Click to collapse
This update addresses the issue mentioned before about init'd scripts not executing at boot. OK, here is the issue (specific to Qualcomm's Snapdragon) and the working solution - thanks to alexndr. I've tested it and it's working, however it doesn't work directly with <X.sh> text files, instead the script must be packaged in a flashable zip and flashed from recovery. Once I did that, it worked like a charm! The 98mediarw file in the screenshot uses the same script as previously mentioned; The 98 before the file name assigns a higher execution priority - I used 98 for testing purposes, it clearly doesn't need that. :good:
nacos said:
OK, here is the issue (specific to Qualcomm's Snapdragon) and the working solution - thanks to alexndr.
Click to expand...
Click to collapse
Oh, at first I thought that you post something what helps me with my tablet:
_jis_ said:
I solved this problem on all my phones but not on my tablet Nexus 7 2013 nor on internal emulated SD card nor on attached OTG USB flash disk.
Click to expand...
Click to collapse
But this is just another example how to execute script at boot
none of these methods are working. Is it because I'm using a Custom ROM?
What are you trying to achieve? What exactly is your environment?
nacos said:
What are you trying to achieve? What exactly is your environment?
Click to expand...
Click to collapse
I have Motorola Moto E (CM11 Stable build by percy_g2) and I'm trying to protect my backups in TiB but I'm getting error "Sorry, the operation failed." It used to be the same in stock ROM. And one more question, is this bug fixed in Lollipop versions of Android?
To answer you questions, no, this is not a bug, it's by design, also it's not happening because you're using a custom ROM, but rather because all OEM's (Google being probably the worst of all) are pushing towards more and more restrictive software & hardware environments, also supported by laws meant to discourage the users from modifying original configurations. Why? Dirty politics, I won't get into that but if you keep your eyes wide open you'll see and understand A LOT! Oh, by the way...to expect for Lollipop to be less restrictive and more fun (to customize) would be naive! Nuff said, let's have some fun!
There are multiple parts to this fix/diagnostic. Don't skip any point and follow these instructions rigorously, otherwise it won't work!!! Let's take them one by one:
Is you platform.xml file (under system/etc) modified to allow read/write access to media_rw (mnt/media_rw)? If not, apply the patch using SDFix from Google Store.
TiBu backup folder must be set to mnt/media_rw/externalSD/Titaniumxxx (if you don't have externalSD than use your internal storage instead, pointing to TiBu folder) - but, for right now, you won't be able to set this path because currently TiBu doesn't have access to media_rw, due to media_rw not being given the right permissions by the system. That's exactly what mediarw script does.
In order for init.d to execute the mediarw script at every boot, you need to insure that you do have init.d support AND it's working. This is how you verify:
(3a) Do you see the folder system/etc/init.d? If yes, go to (3b), if no, you don't have init.d support! That's another fix entirely.
(3b) If you see the 00test file in the init.d folder navigate to /data and open up the file called Test.log - that tells you that init.d is installed and working. If you have a Qualcomm's Snapdragon and you do have the init.d folder but it doesn't execute any script at boot, see the fix in post #6.
(3c) If you don't care about setting up init.d support, you can still run the script at boot, as a shell command using Tasker - see post #4
Once you're sure that all the above are set correctly, flash the attached file from recovery. Reboot, navigate to system/etc/init.d and confirm the presence of the mediarw script in the init.d folder
Reboot again, then navigate to mnt/media_rw and check that permissions for media_rw have been set to 770 - :fingers-crossed: mission accomplished, my friend! :fingers-crossed: If, on the other hand, the permissions for media_rw are still set at 700, then something went wrong. Go back and check every step again, otherwise...
Open up TiBu, set the backup folder path as instructed in #2 and verify that your backups can be protected. Voila!!
nacos said:
To answer you questions, no, this is not a bug, it's by design, also it's not happening because you're using a custom ROM, but rather because all OEM's (Google being probably the worst of all) are pushing towards more and more restrictive software & hardware environments, also supported by laws meant to discourage the users from modifying original configurations. Why? Dirty politics, I won't get into that but if you keep your eyes wide open you'll see and understand A LOT! Oh, by the way...to expect for Lollipop to be less restrictive and more fun (to customize) would be naive! Nuff said, let's have some fun!
There are multiple parts to this fix/diagnostic. Don't skip any point and follow these instructions rigorously, otherwise it won't work!!! Let's take them one by one:
Is you platform.xml file (under system/etc) modified to allow read/write access to media_rw (mnt/media_rw)? If not, apply the patch using SDFix from Google Store.
TiBu backup folder must be set to mnt/media_rw/externalSD/Titaniumxxx (if you don't have externalSD than use your internal storage instead, pointing to TiBu folder) - but, for right now, you won't be able to set this path because currently TiBu doesn't have access to media_rw, due to media_rw not being given the right permissions by the system. That's exactly what mediarw script does.
In order for init.d to execute the mediarw script at every boot, you need to insure that you do have init.d support AND it's working. This is how you verify:
(3a) Do you see the folder system/etc/init.d? If yes, go to (3b), if no, you don't have init.d support! That's another fix entirely.
(3b) If you see the 00test file in the init.d folder navigate to /data and open up the file called Test.log - that tells you that init.d is installed and working. If you have a Qualcomm's Snapdragon and you do have the init.d folder but it doesn't execute any script at boot, see the fix in post #6.
(3c) If you don't care about setting up init.d support, you can still run the script at boot, as a shell command using Tasker - see post #4
Once you're sure that all the above are set correctly, flash the attached file from recovery. Reboot, navigate to system/etc/init.d and confirm the presence of the mediarw script in the init.d folder
Reboot again, then navigate to mnt/media_rw and check that permissions for media_rw have been set to 770 - :fingers-crossed: mission accomplished, my friend! :fingers-crossed: If, on the other hand, the permissions for media_rw are still set at 700, then something went wrong. Go back and check every step again, otherwise...
Open up TiBu, set the backup folder path as instructed in #2 and verify that your backups can be protected. Voila!!
Click to expand...
Click to collapse
(Please ignore that screenshot. I didn't properly read your msg in blue text)
I couldn't understand post #4 so can you please describe it more deeply? :crying: btw I don't have 00test but a file named 00banner. And can you tell me how to use tasker properly?
Sorry for butting in on this thread. I found it by searching because I too can no longer protect a backup in my tibu Pro. I used to be able to but not anymore and I'm not sure why.
I'm on a rooted nexus 5 running stock 4.4.4.
Reading your instructions I went looking for platform.xml and found it. When I checked its properties I got, see screenshot. Don't know what to modify to mount it as you say. I'm in ES Explorer.
Can you help?
Thanks.
And here is a screenshot in root Explorer
Update your tb to 7.0.1 and now you can protect backups ? this thread should get closed now
Closed? Why? Just because a shortcut is available doesn't mean there is nothing to learn from wondering around, my friend!
After all, this is exactly what XDA is: a huge data base available to those who are willing to learn and dare to wonder around, wouldn't you agree?
Hi,
what started as an Idea seems to be working now. For once i wanted a phone that has warranty for more than two weeks (or at least a chance for warranty).
DISCLAIMER:
Do all of this at your own risk. Even though we will not be flashing a custom recovery, technically the warranty is lost the moment you root your phone.
None of the Tools is actually written by me, i just tinkered a bit and came up with this tutorial.
1. You will need
- Galaxy A3 (mine was an A300FU but i guess every one that can be rooted without flashing should do) on Lollipop (5.0.2).
- Minimal ADB or some other software that brings debugging drivers and adb.
- KingRoot 4.60+
- SuperSu-ME (from play Store or an older version is also fine) or any other way to go from the Kinguser Root Management to SuperSU
- Deodexed apks matching you phone model
- Flashfire Beta
- Xposed Installer, I used 3.0alpha4
- Xposed bridge for Samsung lollipop I used xposed-v75-sdk21-arm-arter97-snapdragon_requestConcurrentGC
2. If something goes wrong:
- Odin and a stock LOLLIPOP ROM for your device!
This is Important: Since we dont have a custom recovery, whenever something goes wrong the only rescue is going back to a stock rom and thereby wiping. If everything works in the first go there will be no wipe.
3. Rooting
First we need to root. Thanks to KingRoot thats very easy and just a matter of waiting. Install KingRoot (has to be 4.60+ for Lollipop), Click try to Root, wait for it, done. Know we need to get rid of the KingRoot stuff again and install SuperSU (FlashFire does not support KingUser but SuperSU) thats what we need SuperSU-ME for. There Will be some Left overs since KingRoot converts itself to a system app, you can remove this with Titanium Backup or a ROM Toolbox of you choice.
4. Deodexing
Next step is gonna be Deodexing. This one is a little Tricky without a Custom Recovery. Flashing the Deodex using FlashFire will leave you stuck at the Boot Logo.
Unpack the Flashable Deodex zip. you#ll find a META-INF and a system folder. Copy the system folder (or rename it, doesnt matter) to your SDcard or the phone memory using USB. At this point you can also copy the two Xposed files (zip+apk). Next we need USB Debugging. Install the minimal ADB, browse to the install location and start "adb devices" once (this will start the daemon). Now take your phone, browse to settings / phone info and tap the build number like 10 times (this gives you developers options) now go to settings / developers options and enable USB debugging.
Connect you phone via USB. This hould bring up a dialog granting your PC permission to connect. Click Yes.
Connect to the phone and request root using
Code:
adb shell
su
Now turn on the phones screen there should be a root request, allow it.
Next is the following commands, assuming the location of the extracted system folder is /storage/extSdCard/deodex_system
Code:
mount -o rw,remount /system
rm -Rf /system/app
rm -Rf /system/priv-app
rm -Rf /system/framework
cp -R /storage/extSdCard/deodex_system/* /system
chown -R root:root /system/app
chown -R root:root /system/priv-app
chown -R root:root /system/framework
chmod -R 755 /system/app
chmod -R 755 /system/priv-app
chmod -R 755 /system/framework
rm -Rf /data/dalvik-cache/*
reboot
This will replace all system apks with the deodexed ones, sets the right owner and permissions, clears the dalvik cache and reboots. Booting is gonna take a while and then you're enjoying you're rooted, deodexed stock ROM without flashing anything so far. So now about installing Xposed.
Don't be to slow with thus step. Deleting the three folders will make the phone go crazy and at some point reboot, you should be done by then.
Edit: I did this on a second device now, for some reason the remount did not work. In this case try disabling SElinux (http://forum.xda-developers.com/devdb/project/dl/?id=12178) and then remount.
5. Xposed
Install the XposedInstaller apk file like any other app, no need to start it yet. Next install FlashFire and launch it (granting root access) now select the Option "OTA or ZIP" in Flashfire and select the flashable Xposed zip you downloaded earlier. No further settings needed just hit Flash! The next reboot is again gonna take a while, but after that you can launch the Xposed Installer and start Installing Modules. We're done.
Whenever you do a factory reset (from the recovery), You need to root again using Kingroot, replace it with SuperSU and install Xposed again.
Once more, I did not develop any of the tools mentioned, all credits to their respective authors.
Cheers,
prometh
Edit: I did not try too many modules yet but Wanam for lollipop works just fine and that useless S Whatever bar is a thing of the past
Hi.
I already have a rooted Galaxy A3 (A300FU) and I have TWRP as my recovery so my warranty is already gone and I'm not too worried about that. However I have had no success at trying to deodex my rom to be able to install xposed.
Would it be possible to just flash the deodexed and the xposed zip from TWRP? And with regards to the deodexed zip would it matter if I flash it over the top of my current rom when I'm using a carrier rom rather than the BTU unlocked rom?
Squall88uk said:
Hi.
I already have a rooted Galaxy A3 (A300FU) and I have TWRP as my recovery so my warranty is already gone and I'm not too worried about that. However I have had no success at trying to deodex my rom to be able to install xposed.
Would it be possible to just flash the deodexed and the xposed zip from TWRP? And with regards to the deodexed zip would it matter if I flash it over the top of my current rom when I'm using a carrier rom rather than the BTU unlocked rom?
Click to expand...
Click to collapse
I think this would be a question for the deodex thread I linked but heres my 5 cents: The procedure in your case should be Flashing Deodex (eventually also gapps_replacement from that thread if you get Google Apps FCs) flashing Xposed, booting, installing the xposed installer. The Deodexed zip is meant to be flashed on top of your system. What I described is basically doing manually what the deodex zip file would do (deleting copying...). Since you have twrp already, I guess a system backup wouldn't hurt.
Many thanks for the help. I'll make a nandroid backup of system first just in case and then give it a go.
Thanks again.
Impossible with my SG A3 A300FU
Hello, I already have the root and TWRP installed, but if I try to type the command line with ADB it doesn't work and if I flash the zip, it doesn't work too. Any Idee ? With the first or the second method boot loop with the samsung logo !!
darwin345 said:
Hello, I already have the root and TWRP installed, but if I try to type the command line with ADB it doesn't work and if I flash the zip, it doesn't work too. Any Idee ? With the first or the second method boot loop with the samsung logo !!
Click to expand...
Click to collapse
If you try the adb commands whats the exact error? Permission Problems? Anyway the Command line should do nothing else than flashing the zip file (I dont know what the zip file wipes after flashing but I assume its dalvik and cache).
Great work prometh696 !!! I managed to get xposed on my A5 with knox 0x0 !!!
Some other steps I followed to get it for my A500FU; first I extracted my own system folders system/app/, system/framework/ & system/priv-app/ with root explorer to my ext SD card and then copied it to my computer.
On the computer I batch deodexed those folders with joeldroid's batch deodexer:
http://forum.xda-developers.com/and.../script-app-joeldroid-lollipop-batch-t2980857
Had some issues there as not every Java version seems to deliver the deodexed folders without errors; more details in that topic.
Then I followed your adb commands and installed xposed, and as you said, knox didn't change and is still 0x0 !!!
Thanks again !!!
---------- Post added at 01:30 PM ---------- Previous post was at 01:06 PM ----------
prometh696 said:
If you try the adb commands whats the exact error? Permission Problems? Anyway the Command line should do nothing else than flashing the zip file (I dont know what the zip file wipes after flashing but I assume its dalvik and cache).
Click to expand...
Click to collapse
The command lines are for copying the deodexed apks (so not in a zip). The zip is for xposed and is flashed by flashfire.
But as he already got TWRP (and thus knox 0x1) I see no use for him to use your method anyway
prometh696 said:
If you try the adb commands whats the exact error? Permission Problems? Anyway the Command line should do nothing else than flashing the zip file (I dont know what the zip file wipes after flashing but I assume its dalvik and cache).
Click to expand...
Click to collapse
When I type the first command line after this one "rm -Rf /system/priv-app" or this one "rm -Rf /system/framework" I don't know when exactly my phone reboot and bootloop on samsung logo (dynamic one) ???
My mobile restart before end of commands line
Hi,
your solution seems really good but my mobile (A300FU) is retarting before I typed all commands line.
Do you know a solution ?
Maybe cause I've no ExtSDcard and use the internal card ?
Thank you for your help !!
Regards
Virtua
update : I tried with trwp and made the necessary but the mobile does not boot.
This phone is a mess
It's the first time I can't do what I want with a phone. All posts seems to be a hoax. ;( ;(
Whenever you do a factory reset (from the recovery), You need to root again using Kingroot, replace it with SuperSU and install Xposed again.
Click to expand...
Click to collapse
This is actually incorrect unless root is systemless.
Root remains in system, and so does xposed. A factory reset does not touch the system partition.
You lose root after a reset because you need to reinstall superuser. If you make it a system app you won't lose root even after a reset.
The same with xposed just reinstall the apk.
OK to start off this thread is meant to continue the work done in the thread here huawei-ascend-xt2-h1711 their were some good people working on stuff their but most seem to have moved on.
I decided to pick up the Elate this week from Best Buy and thought it might be time to start a new thread on rooting and restoring the Cricket version of this phone.
Rooting the H1711z Huawei Elate
First step is to unlock your bootloader at Huawei here > https://emui.huawei.com/en/unlock_detail
Well it seems Huawei is no longer unlocking the bootloader so you need to pay DC Unlocker to unlock your bootloader
follow the instructions posted here >> https://forum.xda-developers.com/honor-7x/how-to/how-to-unlock-huawei-bootloader-removal-t3780903
Also please make a backup of your own boot.img as soon as you flash TWRP before flashing the patched _boot.img provided
~Huge thanks to @aslezak for these instructions~
Root instructions: (I used Magisk Manager v5.5.3 boot.img patching to create the boot.img)
here is the stock boot.img for the Elate H1711z
I am not responsible if you brick your device. I didn't brick mine, but if you don't type the correct commands you could be in trouble
Copy this patched_boot.zip to your sdcard. You can download it from the device directly if that's easier. Insert the sdcard into the phone if it wasn't there already (e.g. if you downloaded from a computer).
Reboot phone into fastboot. The easiest way is, if phone is on, unplug phone from USB, hold power button / select "Power Off". Hold VolDown+Power. Phone will boot into fastboot mode.
(skip this step if you've already flashed TWRP) Flash TWRP into your recovery partition. The link was provided in an earlier post by yuweng twrp-xt2-v3.img
plug usb cable in (from phone to computer). From your computer / cmd.exe window, cd \adb:
fastboot devices #make sure computer adb/fastboot sees your device
fastboot flash recovery twrp_xt2_v3.img
Boot into TWRP. From the above step, you should "fastboot reboot", immediately unplug phone from USB, then
With the phone unplugged from the computer, hold VolUp+Power. Release power after the device reboots. It might take a couple tries .. select reboot from eRecovery if that starts instead. Alternatively you can boot into recovery through adb via "adb reboot recovery".
Tap "Keep Read Only" when TWRP starts.
Tap "Install", then tap "Install Image" at the bottom. Browse (Up a Level) then "external_sd"
If you unzipped the patched_boot.zip you will see patched_boot.img here. Select it.
Select "boot" (uncheck "recovery") partition to flash.
Swipe to confirm Flash
Tap "Reboot" once it's completed.
You should be rooted!
Note: if Magisk Manager does not appear in your list of installed applications, download & install it from here latest Magisk Manager. Without this, you won't be prompted to allow root!
Click to expand...
Click to collapse
Note: Magisk Manager will update you to version 16 on first run, it's OK to update in fact feel free to flash it in recovery before you reboot if you want it.
A couple notes about twrp_xt2_v3.img
when you start TWRP choose keep system read only - Unless your planing to restore a backup then choose to make system writable
You cannot backup or restore /data (it's encrypted so don't even try)
Do not use Wipe / factory reset or format data unless you have a good working backup of your userdata partition that you dd to your external_sd yourself see below
From TWRP / adb shell
paste these commands
dd if=/dev/block/bootdevice/by-name/userdata | bzip2 -9f > /external_sd/userdata.img.bz2
to restore--> bzip2 -dc /external_sd/userdata.img.bz2 | dd of=/dev/block/bootdevice/by-name/userdata
dd if=/dev/block/bootdevice/by-name/system | bzip2 -9f > /external_sd/system.img.bz2
to restore--> bzip2 -dc /external_sd/system.img.bz2 | dd of=/dev/block/bootdevice/by-name/system
again thanks go to aslezak
When choosing a backup always prefer the image instead of the stock files (system image - custom image - vendor image are best )(Never choose both system and system image at the same time it's too big and a waste of time and space)
when you exit TWRP do not choose to install the twrp app
Also be sure and thank aslezak for his post here > https://forum.xda-developers.com/showpost.php?p=75115521&postcount=286
Notes on booting up the phone (from power off)
Bootloader (fastboot) = power + volume down + USB hooked to pc
eRecovery = power + volume up + USB hooked to PC
TWRP = power + volume up
Restoring your phone to Stock
We now have the B120 Stock dload update See here >> https://forum.xda-developers.com/showthread.php?p=76902495&highlight=dload#post76902495
I've created a Stock Rom to easily return your phone to Stock Factory Settings (b120)
Warning this will completely Wipe your phoneTo Install
1) Download and copy the H1711z_stock_ROM_v2.zip to your external_sd
2) Boot to TWRP recovery
3) Go to Settings check Use rm -fr instead of formatting / Wipe / Format Data / Type "yes" to confirm
4) Choose Home / Install /Select storage Micro sd / H1711z_stock_ROM_v2.zip / swipe to install
5) when it finishes choose the wipe cache button and then reboot and choose Do not Install
Your phone is now back to stock
Extra's By Request
Here's the XT2_Stock_Rom and XT2_Magisk_ Rom here > https://androidfilehost.com/?w=files&flid=266256
If you like to try my CleanRom for the Elate I uploaded it here >> Elate.CleanRom.v2.zip
flashing instructions are the same as the stock file above
here's whats added/removed
Apps deleted from /Data/hwinit/:
Google Editor Slides
Google Editor Sheets
Google Editor Docs
Apps deleted from Cust:
the entire h1711 folder
AT&T Remote Support
myAT&T
AT&T Visual Voicemail
AT&T Hot Spots
Google Talkback
OMACP
Apps deleted from System:
Amazon shopping
App select
Call Protect
CricketWiFiManager
Device Help
Deezer
Facebook
Facebook App Installer
Facebook app manager
Gmail
Google Duo
Google Chrome
Google Drive
Google Maps
Google Play Photos
Google Play Video
Google Play Music
Google Text to Speech Engine
Ignite
Lookout
myCricket
Protect Plus
Setup & Transfer
Added
FX Root File Manager (as a system App)
Magisk V16 (as a system App)
QuickBoot Reboot (as a system App)
I didn't include Xposed because it's useless without a decrypted Data partition
Note: To remove the Cricket bootanimation, use the FX File Manager with root permission and rename
..\system\version\special_cust\H1711z\cricket\us\media\bootanimation.zip" to bootanimation.zi_ and reboot
I got tired of seeing the error in twrp_v3 about not mounting patch_hw and fixed it ->> Here
you can unzip it and flash it to recovery with TWRP or fastboot
NOTE: added by scrungydoolittle I had a problem with the bz2 image. I prefer to not run it through bz2
dd if=/dev/block/bootdevice/by-name/userdata /external_sd/userdata.img
to restore--> dd if=/external_sd/userdata.img of=/dev/block/bootdevice/by-name/userdata
dd if=/dev/block/bootdevice/by-name/system /external_sd/system.im
to restore--> dd if= /external_sd/system.img of=/dev/block/bootdevice/by-name/system
Of course, the downside is you need a fairly large external sd card.
@scrungydoolittle Please edit you post and remove the Quote of the first post
also the file you posted is not for this phone please remove the link
as to you having problems with the bz2 image they work fine if you follow the instructions
I instructed the user to create their OWN backup of userdata before they format / wipe their data partition
this file most likely contains the users IMEI and should not be shared.
clsA said:
@scrungydoolittle Please edit you post and remove the Quote of the first post
also the file you posted is not for this phone please remove the link
as to you having problems with the bz2 image they work fine if you follow the instructions
I instructed the user to create their OWN backup of userdata before they format / wipe their data partition
this file most likely contains the users IMEI and should not be shared.
Click to expand...
Click to collapse
O.k. I removed the link. It was for the H1711 AT&T phone as it turns out.
And I don't think that image has the IMEI in it, because it is clearly the /system image, and I don't think that data is stored in that partition.
Otherwise all of the posted system images would have the same issue...
scrungydoolittle said:
O.k. I removed the link. It was for the H1711 AT&T phone as it turns out.
And I don't think that image has the IMEI in it, because it is clearly the /system image, and I don't think that data is stored in that partition.
Otherwise all of the posted system images would have the same issue...
Click to expand...
Click to collapse
Thanks ...yeah the userdata contains the IMEI not the system.img
Sent from my LG-H910 using Tapatalk
I would not share a userdata backup unless it was after a factory reset and before I entered any personal account information or data. Agree with you on that
I'd love to see a reliable reference that says userdata contains the IMEI or if you know specifically where it's stored, because l thought IMEI is stored in a totally different partition.
clsA said:
Thanks ...yeah the userdata contains the IMEI not the system.img
Sent from my LG-H910 using Tapatalk
Click to expand...
Click to collapse
divineBliss said:
I would not share a userdata backup unless it was after a factory reset and before I entered any personal account information or data. Agree with you on that
I'd love to see a reliable reference that says userdata contains the IMEI or if you know specifically where it's stored, because l thought IMEI is stored in a totally different partition.
Click to expand...
Click to collapse
IMEI is stored in data/data/com.android.phone
Thank you
Found the IMEI in
/data/data/com.android.phone/shared_prefs/
com.android.phone_preferences.xml on my H1611 after your post.
I'm guessing the IMEI is copied from another partition, but the fact that it's in /data is news to me.
I wonder if the IMEI is in the above file after a factory reset , but I'm not planning to find out anytime soon .
People, be careful sharing your userdata partition backups and other sensitive data containing partition backups out there - unless of course you don't give a crap about security - which you should preface up front so as to not mislead uninformed people of the risks involved in sharing those sensitive data partitions.
clsA said:
IMEI is stored in data/data/com.android.phone
Click to expand...
Click to collapse
It sure would be nice to get one of these stock flash zip's for the H1711 XT2. Would this zip work on it?
clsA said:
Restoring your phone to Stock
I've created a Stock Rom to easily return your phone to Stock Factory Settings (b120)
Warning this completely Wipe your phoneTo Install
1) Download and copy the H1711z_stock_ROM_v2.zip to your external_sd
2) Boot to TWRP recovery
3) Go to Settings check Use rm -fr instead of formatting / Wipe / Format Data / Type "yes" to confirm
4) Choose Home / Install /Select storage Micro sd / H1711z_stock_ROM_v2.zip / swipe to install
5) when it finishes choose the wipe cache button and then reboot and choose Do not Install
Your phone is now back to stock
Click to expand...
Click to collapse
freedomwarrior said:
It sure would be nice to get one of these stock flash zip's for the H1711 XT2. Would this zip work on it?
Click to expand...
Click to collapse
Nice.
What partitions does this install?
And can you make this for the H1711 At&T phone?
freedomwarrior said:
It sure would be nice to get one of these stock flash zip's for the H1711 XT2. Would this zip work on it?
Click to expand...
Click to collapse
No don't use this on the XT2
I / you need system/boot/recovery/ and cust.img files from a XT2 to build it.
Sent from my LG-H910 using Tapatalk
clsA said:
No don't use this on the XT2
I / you need system/boot/recovery/ and cust.img files from a XT2 to build it.
Sent from my LG-H910 using Tapatalk
Click to expand...
Click to collapse
If I send you (or point you to )
system
boot
recover
and cust images could you create one?
The image for system is available, a patched bootloader that installs magisk, an unpatched boot loader, the recovery and e recovery are the same.
I'd like to see 2 flashable zips.
1. that does stock
2. that installs twrp and magisk.
I have all those, but I'm not sure how to make the zip. Is it simply a matter of opening it in a zip prgram and replacing the mentioned image files
with appropriate ones?
scrungydoolittle said:
If I send you (or point you to )
system
boot
recover
and cust images could you create one?
The image for system is available, a patched bootloader that installs magisk, an unpatched boot loader, the recovery and e recovery are the same.
I'd like to see 2 flashable zips.
1. that does stock
2. that installs twrp and magisk.
I have all those, but I'm not sure how to make the zip. Is it simply a matter of opening it in a zip prgram and replacing the mentioned image files
with appropriate ones?
Click to expand...
Click to collapse
I have the Stock system.img and erecovery.img
put the others in a google drive and I'll build them
clsA said:
I have the Stock system.img and erecovery.img
put the others in a google drive and I'll build them
Click to expand...
Click to collapse
Here is the cust.img I just pulled from my XT2 using the dd command.
https://drive.google.com/open?id=1euUHZiJrzfyUVNqgOT76rTk45clPwv9F
Here is a copy of the stock boot I have had sitting on my hard drive.
https://drive.google.com/open?id=1-dAJuwgYdM9F3fBn4dU3x9s74SucocBP
And here is a copy of patched boot (with magisk) if you need it.
https://drive.google.com/open?id=1Tfb7zkcX6auoYEVnMLKDN6tibfzHSPEW
And thank you in advance for doing this! :good:
freedomwarrior said:
Here is the cust.img I just pulled from my XT2 using the dd command.
https://drive.google.com/open?id=1euUHZiJrzfyUVNqgOT76rTk45clPwv9F
Here is a copy of the stock boot I have had sitting on my hard drive.
https://drive.google.com/open?id=1-dAJuwgYdM9F3fBn4dU3x9s74SucocBP
And here is a copy of patched boot (with magisk) if you need it.
https://drive.google.com/open?id=1Tfb7zkcX6auoYEVnMLKDN6tibfzHSPEW
And thank you in advance for doing this! :good:
Click to expand...
Click to collapse
Files are uploading now > https://www.androidfilehost.com/?w=files&flid=257749
Instructions are the same
Backup anything on internal storage it will be wiped
To Install
1) Download and copy the Rom to your external_sd
2) Boot to TWRP recovery
3) Go to Settings check Use rm -fr instead of formatting / Wipe / Format Data / Type "yes" to confirm
4) Choose Home / Install /Select storage Micro sd / your_rom.zip / swipe to install
5) when it finishes choose the wipe cache button and then reboot and choose Do not Install
Your phone is now back to stock
Click to expand...
Click to collapse
after flashing the Magisk rom install the magisk manager and update to v16 (or whatever the newest is)
Awesome! Thank you so much for these. They will definitely come in handy! Much Appreciated!! :good::
clsA said:
OK to start off this thread is meant to continue the work done in the thread here huawei-ascend-xt2-h1711 their were some good people working on stuff their but most seem to have moved on.
Does this wipe out the recovery, and relock the bootloader, or will the bootloader remain unlocked, and twrp remain in place?
Thanks for the XT2 versions.
I decided to pick up the Elate this week from Best Buy and thought it might be time to start a new thread on rooting and restoring the Cricket version of this phone.
Rooting the H1711z Huawei Elate
First step is to unlock your bootloader at Huawei here > https://hwid5.vmall.com/CAS/portal/...ndex&loginChannel=22000000&reqClientType=2023
Also please make a backup of your own boot.img as soon as you flash TWRP before flashing the patched _boot.img provided
~Huge thanks to @aslezak for these instructions~
Note: Magisk Manager will update you to version 16 on first run, it's OK to update in fact feel free to flash it in recovery before you reboot if you want it.
A couple notes about twrp_xt2_v3.img
when you start TWRP choose keep system read only - Unless your planing to restore a backup then choose to make system writable
You cannot backup or restore /data (it's encrypted so don't even try)
Do not use Wipe / factory reset or format data unless you have a good working backup of your userdata partition that you dd to your external_sd yourself see below
From TWRP / adb shell
paste these commands
dd if=/dev/block/bootdevice/by-name/userdata | bzip2 -9f > /external_sd/userdata.img.bz2
to restore--> bzip2 -dc /external_sd/userdata.img.bz2 | dd of=/dev/block/bootdevice/by-name/userdata
dd if=/dev/block/bootdevice/by-name/system | bzip2 -9f > /external_sd/system.img.bz2
to restore--> bzip2 -dc /external_sd/system.img.bz2 | dd of=/dev/block/bootdevice/by-name/system
again thanks go to aslezak
When choosing a backup always prefer the image instead of the stock files (system image - custom image - vendor image are best )(Never choose both system and system image at the same time it's too big and a waste of time and space)
when you exit TWRP do not choose to install the twrp app
Also be sure and thank aslezak for his post here > https://forum.xda-developers.com/showpost.php?p=75115521&postcount=286
Notes on booting up the phone (from power off)
Bootloader (fastboot) = power + volume down + USB hooked to pc
eRecovery = power + volume up + USB hooked to PC
TWRP = power + volume up
Restoring your phone to Stock
I've created a Stock Rom to easily return your phone to Stock Factory Settings (b120)
Warning this will completely Wipe your phoneTo Install
1) Download and copy the H1711z_stock_ROM_v2.zip to your external_sd
2) Boot to TWRP recovery
3) Go to Settings check Use rm -fr instead of formatting / Wipe / Format Data / Type "yes" to confirm
4) Choose Home / Install /Select storage Micro sd / H1711z_stock_ROM_v2.zip / swipe to install
5) when it finishes choose the wipe cache button and then reboot and choose Do not Install
Your phone is now back to stock
By request I have also added the XT2_Stock_Rom and XT2_Magisk_ Rom here > https://www.androidfilehost.com/?w=files&flid=257749
Click to expand...
Click to collapse
Does this wipe out the recovery, and relock the bootloader, or will the bootloader remain unlocked, and twrp remain in place?
Thanks for the XT2 versions.
scrungydoolittle said:
Does this wipe out the recovery, and relock the bootloader, or will the bootloader remain unlocked, and twrp remain in place?
Thanks for the XT2 versions.
Click to expand...
Click to collapse
Really ?? You quoted the first post again
Flashing a Rom will never relock your bootloader
All 3 roms wipe TWRP
Sent from my LG-H910 using Tapatalk
@scrungydoolittle,
I was going to say the same.. .. The reason for clsAs comment is.. .
It's considered bad practice to post the OP or any other long posts unnecessarily. It makes it extremely difficult and annoying for others to wade past the huge quoted post to see what you said.
You can just quote the relevant part of a post (as I did below), refer to post 1 as the OP, or put a link to the post you are referring to.
Hopefully this explanation will get you to edit your last post and reconsider quoting long posts in the future.
Thanks
PS: Consider the fact that some of us read forums via email, XDA forum app, and browsers on mobile devices which have limited screen real estate and require more scrolling than a large desktop monitor.
clsA said:
Really ?? You quoted the first post again
...
Click to expand...
Click to collapse
I'm hoping for some help in rooting my Elate. I was able to get the unlock code from Huawei. I downloaded the ADB and Fastboot drivers from the Android Tutorials page.
ADB recognizes my device when in normal mode. But when I reboot into Bootloader mode, the device is not recognized. It does not show up in Windows device manager and the command "adb devices" is null. I can't get past this point which is clearly a driver problem.
I also have installed and uninstalled Hi-suite a number of times.
Does anyone have any advice? Thanks.
How to flash phh's system arm64-A/B GSI on the Redmi 9's (lancelot) dynamic system partition
All the development credits for this GSI go to @phhusson. For more information head over to his thread.
Bugs:
• Auto brightness (works with an overlay)
• Brightness slider
• Headphone jack
• Offline charging?
• VoLTE?
For bug fixes refer to Post #2 or search for reported bugs on Phh's treble experimentations issues tracker on GitHub.
What is working:
Everything else
WARNING:
Only proceed if you know what you are doing! Be aware of the risks associated to unlocking your bootloader. Ensure to have the MIUI Fastboot ROM downloaded to restore your device in case it soft bricks. All your data will be deleted during the process so a backup is essential. Charge your device to at least 50% before proceeding.
Requirements:
1) Unlocked bootloader here
2) Latest Android platform tools here
3) MIUI stock recovery (maintain it to be able to boot into userspace fastboot)
4) Xiaomi fastbootd drivers here
5) Phh-Treble GSI (Use a system-arm64-ab-gapps) here
6) vbmeta.img here
Steps:
Run the commands below within the platform-tools folder after enabling debugging in Developer settings on your phone.
1) adb devices (to authorize debugging)
2) adb reboot bootloader (to boot into fastboot mode)
3) fastboot reboot fastboot (to boot into userspace fastboot)
4) fastboot flash system system.img
5) fastboot -w
6) fastboot flash vbmeta vbmeta.img (use attached null vbmeta to disable avb)
7) fastboot reboot
Notes:
• First time boot takes 1 minute. phh's GSI has root by default however the logical system partition is read only. Any system mods should be done as Magisk modules systemlessly. A patched boot.img may cause bootlooping on Android 11 GSIs however Magisk now works fine even on R GSIs on MTK devices, thanks to @topjohnwu!
• System can be RW such as to push overlays. Thanks to the great phhusson!
• A better way to disable Android Verified Boot is by running below command using a stock vbmeta image file:
Code:
fastboot --disable-verification flash vbmeta vbmeta.img
Fixes:
I'll post fixes to bugs as suggested by users in this thread here.
• Brightness slider and headphone jack [Credit to @M47Z and @Shas45558] — Run code below in root ADB shell or any Terminal app on your phone:
Code:
su
setprop persist.sys.qcom-brightness $(cat /sys/class/leds/lcd-backlight/max_brightness)
setprop persist.sys.overlay.devinputjack true
reboot
• Note that CAOS by @eremitein has the above fixes integrated and is based on phhusson's AOSP.
How is the performance .any lag ?
Once you boot there are no lags. FYI my device is only 3 GB RAM. I just observed that booting is a little faster with the lighter Phh-Treble system installed as compared to Havoc. Maybe that's something for you to consider.
nielsync said:
Once you boot there are no lags. FYI my device is only 3 GB RAM. I just observed that booting is a little faster with the lighter Phh-Treble system installed as compared to Havoc. Maybe that's something for you to consider.
Click to expand...
Click to collapse
Is your headphones work??is brightness work?
Headphones not working but good enough BT audio works with speakers. Haven't tested in call audio on BT earphones though. Also not sure about USB-C audio output. Someone who has tested can share with us. Brightness is also broken.
I need testers
I built the overlay but I need testers to see if the overlay is working
Overlay link : github.com/mehdiFa-web/overlay
Mido2222 said:
I built the overlay but I need testers to see if the overlay is working
Overlay link : github.com/mehdiFa-web/overlay
Click to expand...
Click to collapse
Edit: Not working. Refer to post #18 for info.
Mido2222 said:
I built the overlay but I need testers to see if the overlay is working
Overlay link : github.com/mehdiFa-web/overlay
Click to expand...
Click to collapse
how did you pushed it into /vendor/overlay/ ?
I get the permission denied error everytime with adb and with any root file explorer on the phone too.
kW_ said:
how did you pushed it into /vendor/overlay/ ?
I get the permission denied error everytime with adb and with any root file explorer on the phone too.
Click to expand...
Click to collapse
I didn't test it I just build it . You should have root just copy it into your phone's /system/overlay/, and set permission to rw-r--r-- / 0644. If you can't then maybe we can't edit system partition . You can use root explorer.
Well. I can't change permissions and copy it. I have seen that other roms doesn't have read only on the system partition so i will try it later. Lineageos is one of these roms maybe.
Gsi will not boot with magisk_patch boot.img.....
So no root access......
How you push file into system or vendor??
Shas45558 said:
Gsi will not boot with magisk_patch boot.img.....
So no root access......
How you push file into system or vendor??
Click to expand...
Click to collapse
Phh-Treble has root so you are good to go. On the other hand without flashing a custom recovery I got root on Havoc-OS through flashing the patched boot image and even installed a module in Magisk manager without any issues. Its just that the way the system partition is mounted on these new phones released with Q makes it almost impossible to modify it. Let a genius surprise us.
nielsync said:
Phh-Treble has root so you are good to go. On the other hand without flashing a custom recovery I got root on Havoc-OS through flashing the patched boot image and even installed a module in Magisk manager without any issues. Its just that the way the system partition is mounted on these new phones released with Q makes it almost impossible to modify it. Let a genius surprise us.
Click to expand...
Click to collapse
In my case when I flash patch boot my gsi wili not boot....
What gsi are you use?? Give the link plz
@nielsync
So im a genius nd going to surprise you if anyone wants to modify system partition then custom recovery is must required e.g in Twrp mount /system , /vendor then go to file manager in twrp i forgot the name of tab in which you ll find the filemanager you can find it yourself lmao ,then select the file by finding in ur storage nd then copy and paste it in desired location and then after pasting go to path where you pasted it,Select it and give it 0644 permissions and restart ..Boom.( I think root is necessary because without root the changes revert )
Abdul [email protected] said:
@nielsync
So im a genius nd going to surprise you if anyone wants to modify system partition then custom recovery is must required e.g in Twrp mount /system , /vendor then go to file manager in twrp i forgot the name of tab in which you ll find the filemanager you can find it yourself lmao ,then select the file by finding in ur storage nd then copy and paste it in desired location and then after pasting go to path where you pasted it,Select it and give it 0644 permissions and restart ..Boom.( I think root is necessary because without root the changes revert )
Click to expand...
Click to collapse
File manager is in Advanced tab of TWRP. In theory and in devices released with the now old partition structure it was that simple. You have a right to claim anything Mr. Genius You seem to be ahead of even @Dees_Troy and his team over at TWRP despite this wonderful explanation!
Shas45558 said:
In my case when I flash patch boot my gsi wili not boot....
What gsi are you use?? Give the link plz
Click to expand...
Click to collapse
I've used both Phh-Treble and Havoc-OS and can confirm that Magisk works on both without any issues. My boot image was already patched on MIUI so I only installed the manager application each time after flashing the GSI. See screenshots of Magisk Manager on Phh-Treble below.
Mido2222 said:
I built the overlay but I need testers to see if the overlay is working
Overlay link : github.com/mehdiFa-web/overlay
Click to expand...
Click to collapse
no it does not work
i mount the gsi system file on linux via loop disk...
then i place your apk /system/overly/
but the brightness is not work...
you can mount raw img file on linux ......
first creat folder on root via this cmd..
sudo mkdir /mnt/system
mount system.img via this cmd
sudo mount system.img /mnt/system
now you can edit system.img via root permission via this cmd...
sudo nautilus
now a file manager pop up with root
go to /mnt/system
copy your file where you want...and unmount via this cmd...
sudo umount /mnt/system
Thanks @Shas45558 for confirming that, it's still difficult to mod the installed system on the phone itself. I tried and got a 'permission denied' error via terminal in a custom recovery.
nielsync said:
Thanks @Shas45558 for confirming that, it's still difficult to mod the installed system on the phone itself. I tried and got a 'permission denied' error via terminal in a custom recovery.
Click to expand...
Click to collapse
That's why I use pc with Linux and do the above things to puss the file inside system.img....