[ROM] [H918] 10p Debloated Rom Flashable Zip - fast as nuts no lag w Pixel Launcher - LG V20 ROMs, Kernels, Recoveries, & Other Developm

The link below is a DEBLOATED flashable zip of the LG V20 10p ROM. I extracted it from the latest 10p KDZ file using kdztools and python 2.7 on Windows. I built the ROM from the extraction using Superrs kitchen version 3 on Linux.
Tons of bloat removed.
I purposely didn't remove WiFi calling, VPN files, and LG Update center in case you want to install some LG apps.
I have added the Google Pixel Launcher because it's so quick. It's optional to use if you want to or not.
I used Superr's kitchen to debloat this plus some manual cut and paste.
READ ALL WARNINGS BEFORE PROCEEDING
This rom is not rooted but you can flash magisk or SuperSU to root it. It does not flash recovery. It does not encrypt.
Using magisk it works with both Samsung and Android [email protected] which is the main reason I built it.
Issues: none i know of but let me know please! Also, see warnings below
TO DO's: you tell me
Flash at your own risk. I'm not responsible if your device gets bricked.
10p Warnings based on what we know:
WARNING #1 You must flash the 10p modem and bootloader for this to work. If you don't you will soft brick.
WARNING #2 Once you go to 10p modem and bootloader you can't go back to previous versions. If you try you will HARD brick your device.
WARNING #3 10P rom only works with 10p modem and 10p bootloader. Any other combo SOFT bricks.
WARNING #4 TWRP backups of previous versions will not restore correctly once you are on 10p. When you restore a previous version (10k and before) you will soft brick. You can unbrick by just installing the 10p ROM, modem, and bootloader over the top of your restore *****Restores and Backups of 10p roms work just fine.
BOTTOM LINE: Going to 10p is a TOTAL commitment and there probably will never be a way to go back. That said, I'm on 10p and so far it works great.
Version 3 changes: fixed a mic issue
ROM Links:
Drive: https://drive.google.com/open?id=0B3y-9RMsaMSbVnZ5eHZDSjhuUUk
Get 10p Modem and 10p bootloader here:
https://forum.xda-developers.com/v20/development/firmware-twrp-flashable-bootloader-modem-t3547268
*****Be sure to thank the OP on that thread!*****
Clean install instructions: twrp backup, wipe, install ROM, install 10p modem, install 10p bootloader, install root of your choice, reboot
Dirty install works fine over Weta ROM or NATF ROM, but not over aosp or lineage roms: twrp backup, install ROM, install 10p modem, install 10p bootloader, install root of your choice, reboot. Note: when you dirty flash you do lose any system apps you had before but your data partition is retained.
Enjoy. Please give thanks if this ROM is helpful for you.

First!

The latest magisk version works? I'm on rooted 10k and i'm going to dirty flash this later.
Sent from my LG-H918 using Tapatalk

peekeesh said:
The latest magisk version works? I'm on rooted 10k and i'm going to dirty flash this later.
Sent from my LG-H918 using Tapatalk
Click to expand...
Click to collapse
yes sir. I can confirm that Magisk 13.3 works like a champ for me. Magisk 13.xx has always needed to be reinstalled like once every two weeks for me, no matter what ROM I am on. Samsung and Google [email protected] both work nicely too on this rom.
Note: when you dirty flash you do lose any system apps you had before but your data partition is retained.

peekeesh said:
The latest magisk version works? I'm on rooted 10k and i'm going to dirty flash this later.
Sent from my LG-H918 using Tapatalk
Click to expand...
Click to collapse
Remember you need to flash 10P bootloader and modem and there is no going back to 10K afterwards.
Sent from my LG-H918 using Tapatalk

texasaggie1 said:
yes sir. I can confirm that Magisk 13.3 works like a champ for me. Magisk 13.xx has always needed to be reinstalled like once every two weeks for me, no matter what ROM I am on. Samsung and Google [email protected] both work nicely too on this rom.
Note: when you dirty flash you do lose any system apps you had before but your data partition is retained.
Click to expand...
Click to collapse
Ok thanks for confirming..?
Bxlegend, thanks for the reminder.
Sent from my LG-H918 using Tapatalk

bxlegend said:
Remember you need to flash 10P bootloader and modem and there is no going back to 10K afterwards.
Sent from my LG-H918 using Tapatalk
Click to expand...
Click to collapse
It's an all out commitment lol

Can you post a list of what you removed?

gig'em!

sdc177 said:
gig'em!
Click to expand...
Click to collapse
Yes sir !!

texasaggie1 said:
The link below is a DEBLOATED flashable zip of the LG V20 10p ROM. I extracted it from the latest 10p KDZ file using kdztools and python 2.7 on Windows. I built the ROM from the extraction using Superrs kitchen version 3 on Linux.
Tons of bloat removed.
I purposely didn't remove WiFi calling, VPN files, and LG Update center in case you want to install some LG apps.
I used Superr's kitchen to debloat this plus some manual cut and paste.
READ ALL WARNINGS BEFORE PROCEEDING
This rom is not rooted but you can flash magisk or SuperSU to root it. It does not flash recovery. It does not encrypt.
Using magisk it works with both Samsung and Android [email protected] which is the main reason I built it.
Issues: none i know of but let me know please! Also, see warnings below
TO DO's: you tell me
Flash at your own risk. I'm not responsible if your device gets bricked.
10p Warnings based on what we know:
WARNING #1 You must flash the 10p modem and bootloader for this to work. If you don't you will soft brick.
WARNING #2 Once you go to 10p modem and bootloader you can't go back to previous versions. If you try you will HARD brick your device.
WARNING #3 10P rom only works with 10p modem and 10p bootloader. Any other combo SOFT bricks.
WARNING #4 TWRP backups of previous versions will not restore correctly once you are on 10p. When you restore a previous version (10k and before) you will soft brick. You can unbrick by just installing the 10p ROM, modem, and bootloader over the top of your restore *****Restores and Backups of 10p roms work just fine.
BOTTOM LINE: Going to 10p is a TOTAL commitment and there probably will never be a way to go back. That said, I'm on 10p and so far it works great.
ROM Links:
Drive: [ https://drive.google.com/file/d/0B3y-9RMsaMSbRWNEUzJMZkwyUk0/view?usp=drivesdk [/url]
Get 10p Modem and 10p bootloader here:
https://forum.xda-developers.com/v20/development/firmware-twrp-flashable-bootloader-modem-t3547268
*****Be sure to thank the OP on that thread!*****
Clean install instructions: twrp backup, wipe, install ROM, install 10p modem, install 10p bootloader, install root of your choice, reboot
Dirty install works fine over Weta ROM or NATF ROM, but not over aosp or lineage roms: twrp backup, install ROM, install 10p modem, install 10p bootloader, install root of your choice, reboot. Note: when you dirty flash you do lose any system apps you had before but your data partition is retained.
Enjoy. Please give thanks if this ROM is helpful for you.
Click to expand...
Click to collapse
Latest version uploaded

So happy to see more love for my beloved v20 going to dirty flash tomorrow and see how things go. One question I have is why for any reason would someone wanna go back to 10k? Does this update have any flaws that would make someone regret updating? New updates are always good right?
If anybody has dirty flashed from MEGAROM with no problems please let us know.
MEGAROM h918 10k

Deodex?
Great job on this, any chance for a deodex version so ee try some of the mods for this masterpiece?

Still_living714 said:
So happy to see more love for my beloved v20 going to dirty flash tomorrow and see how things go. One question I have is why for any reason would someone wanna go back to 10k? Does this update have any flaws that would make someone regret updating? New updates are always good right?
If anybody has dirty flashed from MEGAROM with no problems please let us know.
MEGAROM h918 10k
Click to expand...
Click to collapse
well, the main reason to stay on 10k would be that you're guaranteed to be able to root and TWRP. if you make a mistake and lose TWRP for whatever reason while on 10p, you're fscked. you can wait for root, but I doubt it's coming any time soon

Bluetooth performance seem to be on point in this one as opposed to 10k!

custommsp said:
Any comments on bluetooth pairing and performance? There are pairing issues in 10k with certain devices.
Thanks.
Click to expand...
Click to collapse
So you're on 10K ? Then there's a good chance you flashed the 10K KDZ from lg-firmwares.com, or one of the TWRP zips from xda. The KDZ for 10K is messed up, just look inside it and see. Among other things, it contains a misc.bin (not supposed to be there) which overwrites the one (unique) on you phone, thus erasing your WLAN mac address and other stuff, possibly affecting Bluetooth.
Before I bricked, I noticed this when I used my phone as FTP server, the IP address would change at every reboot. At that time I didn't know why, but assumed it was just some temporary bug with the stock rom.
LG screwed up again.
Edit: OK, @me2151 has just informed me that the problem might not have been caused by wiping misc partition after all. There may been some confusion on the matter. But remains to be seen I guess. @dimm0k may have some input.
Nope seems it it the case like I first said. More info.

need root to try this stuck on 10p sadly

Does xposed work? If so which one is recomended for 10p?

custommsp said:
Any comments on bluetooth pairing and performance? There are pairing issues in 10k with certain devices.
Thanks.
Click to expand...
Click to collapse
what pairing issues are you having and with what devices? I don't recall having any Bluetooth issues when I was on 10k
askermk2000 said:
So you're on 10K ? Then there's a good chance you flashed the 10K KDZ from lg-firmwares.com, or one of the TWRP zips from xda. The KDZ for 10K is messed up, just look inside it and see. Among other things, it contains a misc.bin (not supposed to be there) which overwrites the one (unique) on you phone, thus erasing your WLAN mac address and other stuff, possibly affecting Bluetooth.
Before I bricked, I noticed this when I used my phone as FTP server, the IP address would change at every reboot. At that time I didn't know why, but assumed it was just some temporary bug with the stock rom.
LG screwed up again.
Edit: OK, @me2151 has just informed me that the problem might not have been caused by wiping misc partition after all. There may been some confusion on the matter. But remains to be seen I guess. @dimm0k may have some input.
Click to expand...
Click to collapse
I'm not entirely sure how a messed up misc partition would affect Bluetooth in general, as I'm usually using my phone to connect to headphones or car stereo, but with a messed up misc partition your Bluetooth address is no longer what it was when you first unboxed the device. see my post here if you're curious about the misc partition https://forum.xda-developers.com/showpost.php?p=73439967&postcount=14

De-bloat removes clock app. Without this there's no alarm. Can you add it back?
Sent from my SM-T810 using Tapatalk

Related

[ROM][STOCK][DEBLOATED][5.1.1] Samsung Galaxy Tab A 7.0 LTE 2016 (SM-T285)

This is a custom Rom I made for the Samsung Galaxy Tab A 7.0 LTE (SM-T285), which suits my tastes.
If you have suggestions, send me a PM.
UPDATE 09/07/2016
================
A newer version that runs "root" (sepolicy constrained) scripts can be found here:
http://forum.xda-developers.com/android/development/rom-samsung-galaxy-tab-7-0-lte-2016-sm-t3455788
Use the above version instead if you want to experiment with features like apps 2 sdcard.
Modifications:
* Based on LMY47V.T285XXU0APCN
* Stock Boot and Recovery (Not much choice since the bootloader is locked)
* Removed Touchwiz launcher and redundant samsung apps (Hancom office, Kidzone), replaced with Trebuchet
* Enabled r/w to the external SD Card
Installation Instructions:
Odin or Heimdall Required.
--FLASH AT YOUR OWN RISK--
1. Make sure to backup of your data and have a copy of your stock Rom in case something goes wrong.
2. Make sure your device is OEM unlocked. (Enable Developer settings and Enable the OEM unlock settings)
3. Extract ZIP file below and flash the tar.md5 file using ODIN, for details on this kindly look for instructions in the xda site.
4. For Heimdall you can use 7zip to extract the system.img from the tar.md5 and just flash the system.img itself.
Link:
Download from Mega
jaritico said:
thanks, but what does after download zip? recovery mode or download mode? and how got it? this root t285?
Click to expand...
Click to collapse
Thanks, but what does after download zip? recovery mode or download mode? and how got it? this root t285?
Click to expand...
Click to collapse
You have to go to download mode and then use Odin to flash. Unfortunately this does not root the T285.
jedld said:
This is a custom Rom I made for the Samsung Galaxy Tab A 7.0 LTE (SM-T285), which suits my tastes.
If you have suggestions, send me a PM.
Modifications:
* Based on LMY47V.T285XXU0APCN
* Stock Boot and Recovery (Not much choice since the bootloader is locked)
* Removed Touchwiz launcher and redundant samsung apps (Hancom office, Kidzone), replaced with Trebuchet
* Enabled r/w to the external SD Card
Installation Instructions:
Odin or Heimdall Required.
--FLASH AT YOUR OWN RISK--
1. Make sure to backup of your data and have a copy of your stock Rom in case something goes wrong.
2. Make sure your device is OEM unlocked. (Enable Developer settings and Enable the OEM unlock settings)
3. Extract ZIP file below and flash the tar.md5 file using ODIN, for details on this kindly look for instructions in the xda site.
4. For Heimdall you can use 7zip to extract the system.img from the tar.md5 and just flash the system.img itself.
Link:
Download from Mega
Click to expand...
Click to collapse
Says I need the encryption key and if I do not have it to contact the developer ......
TopTongueBarry said:
Says I need the encryption key and if I do not have it to contact the developer ......
Click to expand...
Click to collapse
Sorry, updated links, try again and see if it works.
jedld said:
Sorry, updated links, try again and see if it works.
Click to expand...
Click to collapse
Yes, downloading now. Thanks.
Hi,
Anyone tried Pokemon Go update 0.37 with this ROM? The update fails to start for me. It prompts device/os version is incompatible.
I reverted back to version 0.35 and it works fine.
venomrat said:
Hi,
Anyone tried Pokemon Go update 0.37 with this ROM? The update fails to start for me. It prompts device/os version is incompatible.
I reverted back to version 0.35 and it works fine.
Click to expand...
Click to collapse
Yeah the newest version checks for xposed and a bunch of other things. Actually a lot of people were pissed that they did this. You'd probably need to revert back to stock if you want to play. Only systemless root and xposed with magisk works for Pokemon go now.
jedld said:
Yeah the newest version checks for xposed and a bunch of other things. Actually a lot of people were pissed that they did this. You'd probably need to revert back to stock if you want to play. Only systemless root and xposed with magisk works for Pokemon go now.
Click to expand...
Click to collapse
Also if you want more details on what is going on search google for "pokemon go safetynet". Basically most custom roms and not just this device should fail the test.
jedld said:
This is a custom Rom I made for the Samsung Galaxy Tab A 7.0 LTE (SM-T285), which suits my tastes.
If you have suggestions, send me a PM.
UPDATE 09/07/2016
================
A newer version that runs "root" (sepolicy constrained) scripts can be found here:
http://forum.xda-developers.com/android/development/rom-samsung-galaxy-tab-7-0-lte-2016-sm-t3455788
Use the above version instead if you want to experiment with features like apps 2 sdcard.
Modifications:
* Based on LMY47V.T285XXU0APCN
* Stock Boot and Recovery (Not much choice since the bootloader is locked)
* Removed Touchwiz launcher and redundant samsung apps (Hancom office, Kidzone), replaced with Trebuchet
* Enabled r/w to the external SD Card
Installation Instructions:
Odin or Heimdall Required.
--FLASH AT YOUR OWN RISK--
1. Make sure to backup of your data and have a copy of your stock Rom in case something goes wrong.
2. Make sure your device is OEM unlocked. (Enable Developer settings and Enable the OEM unlock settings)
3. Extract ZIP file below and flash the tar.md5 file using ODIN, for details on this kindly look for instructions in the xda site.
4. For Heimdall you can use 7zip to extract the system.img from the tar.md5 and just flash the system.img itself.
Link:
Download from Mega
Click to expand...
Click to collapse
Hello and thank you for your work with this device. Currently I am looking for a bypass for the factory reset protection on my sm t280. I have flashed the stock md5 file 3+ times attempting to do a complete data wipe and reset, and this doesnt remove the lock. Any ideas?
BadReligion420 said:
Hello and thank you for your work with this device. Currently I am looking for a bypass for the factory reset protection on my sm t280. I have flashed the stock md5 file 3+ times attempting to do a complete data wipe and reset, and this doesnt remove the lock. Any ideas?
Click to expand...
Click to collapse
To FRP unlock you have to go to developer settings and switch oem unlock to false. The stock rom should have it unless you are using a carrier locked version that I a! not aware of.
jedld said:
To FRP unlock you have to go to developer settings and switch oem unlock to false. The stock rom should have it unless you are using a carrier locked version that I a! not aware of.
Click to expand...
Click to collapse
please excuse my ignorance, but am i able to do this with out being able to login? the person i purchased it from doesnt have the original owners gmail and pw.
---------- Post added at 05:59 PM ---------- Previous post was at 05:57 PM ----------
BadReligion420 said:
please excuse my ignorance, but am i able to do this with out being able to login? the person i purchased it from doesnt have the original owners gmail and pw.
Click to expand...
Click to collapse
I just downloaded a stock recovery for a sm t285, and was going to attempt to flash to the 280. havent yet, do you feel that would be a safe thing to attempt? not looking to brick.
BadReligion420 said:
please excuse my ignorance, but am i able to do this with out being able to login? the person i purchased it from doesnt have the original owners gmail and pw.
---------- Post added at 05:59 PM ---------- Previous post was at 05:57 PM ----------
I just downloaded a stock recovery for a sm t285, and was going to attempt to flash to the 280. havent yet, do you feel that would be a safe thing to attempt? not looking to brick.
Click to expand...
Click to collapse
FRP is specifically designed to prevent flashing if you can't login to the device. You won't be able to flash unless the person has turned off oem unlock beforehand. I am not aware of any method to bypass this on this device.
Also the T280 and T285 have slightly different hardware so using a different recovery image is not recommended. Also since both devices have a locked bootloader, I highly doubt you can even change the recoveries from stock as I would imagine samsung using different keys for both. At the worst case it still always possible to reflash them back to stock if you do want to try
AARGH! If I had only waited and not sold my so difficult to get SM-T285M (to TTB)....sheesh never thought there would be this much progress
bang head live and keep learning
mac231us said:
AARGH! If I had only waited and not sold my so difficult to get SM-T285M (to TTB)....sheesh never thought there would be this much progress
bang head live and keep learning
Click to expand...
Click to collapse
And thank you so much for selling it. I don't speak enough Spanish to make the ordeal of getting one of the T285M's from so america worthwhile. I was planning on sticking with my T239M for awhile, then I saw your T285M on ebay.
I've dirty flashed jedld's T285 debloated rom, then dirty flashed his T285 tinker rom on top of that. Both onto my T285M. Working flawlessly. Wished he'd kept the mail app, but without touchwiz I guess that wasn't possible.
Something else they blocked in the kernel or with SElinux on the T285M is screen mirroring. Can only cast directly from apps.
Still I am happy overall. Now looking for a castrated version of daemonsu!
TTB
TopTongueBarry said:
And thank you so much for selling it. I don't speak enough Spanish to make the ordeal of getting one of the T285M's from so america worthwhile. I was planning on sticking with my T239M for awhile, then I saw your T285M on ebay.
I've dirty flashed jedld's T285 debloated rom, then dirty flashed his T285 tinker rom on top of that. Both onto my T285M. Working flawlessly. Wished he'd kept the mail app, but without touchwiz I guess that wasn't possible.
Something else they blocked in the kernel or with SElinux on the T285M is screen mirroring. Can only cast directly from apps.
Still I am happy overall. Now looking for a castrated version of daemonsu!
TTB
Click to expand...
Click to collapse
no need for a castrated version. Full ROOT is available soon now.
http://forum.xda-developers.com/showpost.php?p=68777842&postcount=27
Double Aargh...salt on my wounds ttb
Now my contact in S. America will not even reply to me
Contemplating on getting the Samsung J max 7.0 dual sim...yes no U.S lte but has an 8mp camera and a flash...similar to the T285 otherwise...can't say how many times I needed the flash for photos or even if for looking at labels peering into dim areas behind a monitor or tv..maybe end up in same pickle of no root...will see (number is SM-T285YD so it is based off the T285 it seems-maybe a Latin American version soon?)
Also trying to get the T705M from another source but taking forever...low hopes think it will come through
TopTongueBarry said:
And thank you so much for selling it. I don't speak enough Spanish to make the ordeal of getting one of the T285M's from so america worthwhile. I was planning on sticking with my T239M for awhile, then I saw your T285M on ebay.
I've dirty flashed jedld's T285 debloated rom, then dirty flashed his T285 tinker rom on top of that. Both onto my T285M. Working flawlessly. Wished he'd kept the mail app, but without touchwiz I guess that wasn't possible.
Something else they blocked in the kernel or with SElinux on the T285M is screen mirroring. Can only cast directly from apps.
Still I am happy overall. Now looking for a castrated version of daemonsu!
TTB
Click to expand...
Click to collapse
got another one - white color ...as a gift...God Bless - great device battery life is just incredible - nothing fancy but does its job...keeping this one (had it since early November) gave up on the 705m
Is this ROM compatible with Google Safetynet? I can't seem to log into Pokemon GO since I installed Tinker edition, so I'm thinking to switch to this one instead.
Haven't tried it but it should work.
Is the root part contained in boot.img or in system.img? In other words, when using Heimdall I should flash both system.img and boot.img, isn't it?
I'm getting bootloops with CM13, Omni and I don't know how I got Tinker working, I kind of remember flashing boot.img, then wiping, then flashing system.img, then wiping again.
EDIT: got this one working too by flashing boot.img (Heimdall complains it cannot receive confirmation msg) reboot into download again, then flashing system.img (this time heimdall does reboot the phone). however, pokemon go still wont connect due to google's safetynet compliance.
I'll try flashing recovery in case it is TWRP the one clashing with Safetynet.
PD: I didn't backup stock at the beggining of the process so I'm pretty much screwed with Pokemon until I can afford a new phone. But if someone has a stock ROM for T285MUBU0API2, please ping me.
EDIT2 Got pokemon working. I reinstalled TWRP (this ROM's recovery is the stock one, of course), then flashed unSU. It removed SuperSU binary and Google SafeNet got working again. I can't believe that, after so much hours I've put into finding the best custom ROM for this crappy phone, 95% of the time was spent in trying to get Pokemon GO running. I'm close to 40, FML.

[ROM] H910 v10r - stock

*** WARNING ***
Do NOT flash this on an H918, you will brick your phone.
This is for the AT&T H910 ONLY​
Thanks to @toastyp for the dump of 10r.
Thanks to @askermk2000 for the kernel. Dude doesn't even have a V20 anymore, but he jumped in and helped when I lost my dev environment to build the kernel. That is what XDA is supposed to be about. Seriously man, huge thanks.
With that said, this is the v10r firmware + boot + system. For now, it is possible to dirty flash this, but if there are a lot of posts about problems, I will force a wipe in the zip since most people will be coming from 10m or even earlier (I think NATF is based on 10l, and I don't know what WETA is based on).
So, please, just backup your data and do a clean install
This is 100% stock v10r, bloat and all. It is ARB 0, so if you don't like it, you can go back to any older version.
This include v1.0 of the mk2000 kernel, please check his thread here for any updates.
Also, the 10r firmware doesn't work with 10m or lower system images -- 10p or 10q only. Since there are no custom ROMs currently that are based on 10p, 10q, or 10r, there is no reason to flash JUST the firmware without boot and system.
If you choose to dirty flash, then you MUST reinstall Magisk or SuperSU before rebooting. If you don't, then your data will be encrypted when the phone boots.
With the new firmware, the engineering aboot is able to init the screen correctly so the nasty warning message is clearly visible. This is the same warning as before, but it was garbled and you couldn't read it. Ignore it... your phone will boot.
Download here.
SHA: 5451146030393e490dcfba3558b620badefe75cd
-- Brian
Awesome work wi'll be trying this later
Awesome! Thank you!
runningnak3d said:
Thanks to @crackness for the dump of 10q before he rooted his device.
Thanks to @askermk2000 for the kernel. Dude doesn't even have a V20 anymore, but he jumped in and helped when I lost my dev environment to build the kernel. That is what XDA is supposed to be about. Seriously man, huge thanks.
With that said, this is the v10q firmware + boot + system. For now, it is possible to dirty flash this, but if there are a lot of posts about problems, I will force a wipe in the zip since most people will be coming from 10m or even earlier (I think NATF is based on 10l, and I don't know what WETA is based on).
So, please, just backup your data and do a clean install
This is 100% stock v10q, bloat and all. It is ARB 0, so if you don't like it, you can go back to any older version.
Also, the 10q firmware doesn't work with 10m or lower system images -- 10p or 10q only. Since there are no custom ROMs currently that are based on 10q, there is no reason to flash JUST the firmware without boot and system.
You will need to reinstall Magisk or SuperSU.
With the new firmware, the engineering aboot is able to init the screen correctly so the nasty warning message is clearly visible. This is the same warning as before, but it was garbled and you couldn't read it. Ignore it... your phone will boot.
Download here.
SHA: 6bbc1bc160baff3f44bd6b68b27b10324b0d087d
-- Brian
Click to expand...
Click to collapse
If I wanted to root, I could download this to my H91010q and go back to stock?
Apologies in advance if already obvious, but can someone on 10j or 10k flash this without first being on p or q?
The reason I ask is that you mentioned this "It is ARB 0, so if you don't like it, you can go back to any older version." and " 10q firmware doesn't work with 10m or lower system images -- 10p or 10q only."
My build number is NRD90M and my software version is H91810j.
I just want confirmation that this will work without me having to upgrade my firmware first.
Thanks for all your hard work!
@Jburd23 This does not root your phone. You flash this in TWRP if you are already rooted and want to upgrade to 10q.
@Quiksmage Yes, you can flash this no matter what version you are on. It includes system, so your current system will be wiped. It also contains the rest of the 10q firmware.
-- Brian
runningnak3d said:
@Jburd23 This does not root your phone. You flash this in TWRP if you are already rooted and want to upgrade to 10q.
@Quiksmage Yes, you can flash this no matter what version you are on. It includes system, so your current system will be wiped. It also contains the rest of the 10q firmware.
-- Brian
Click to expand...
Click to collapse
I should have also added the following. I can go back to a j based firmware after flashing this, correct?
It doesn't flash the modem/bootloader?
Sorry about the repeated questions, but I just want to be absolutely sure I don't end up in a place where I can't go back to the rootable firmware. Thanks
Nice to see some love for our v20, nice work.
Quiksmage said:
I should have also added the following. I can go back to a j based firmware after flashing this, correct?
Click to expand...
Click to collapse
Yes, you can revert to any older firmware. However, I don't know of any that was dumped. The H910 doesn't have a KDZ so the only way to get new (or older) firmware, is to have someone that hasn't rooted dump it.
If you are currently on 10j, then use the patched LG UP to dump your phone so that you will have a copy of the complete 10j firmware (minus an untouched system). At least that way you can flash back to it if you want. I only have dumps of 10m, 10p, and 10q. If you do dump your phone, please zip up the firmware and send it to me. You just need the files that are in this 10q zip.
It doesn't flash the modem/bootloader?
Click to expand...
Click to collapse
Yes it does. When a post says firmware + boot + system, the firmware is the bootloader, modem, hypervisor, trustzone, etc.... Boot is the kernel, and system is the actual Android install.[/quote]
Sorry about the repeated questions, but I just want to be absolutely sure I don't end up in a place where I can't go back to the rootable firmware. Thanks
Click to expand...
Click to collapse
Don't quite understand this question. You don't lose TWRP if you flash this, so you can root with Magisk again. Also, ALL H910 firmware is currently rootable. The H910 and the unlocked US996 are the last two V20s that can be rooted on the latest firmware.
-- Brian
Hey Brian, that was my fault. I thought I had read H918 v10q. The t-mobile variant cannot go back once updated past K. Apologies!
First post updated to 10r with mk2000 v1.0 kernel.
-- Brian
runningnak3d said:
Thanks to @toastyp for the dump of 10r.
Thanks to @askermk2000 for the kernel. Dude doesn't even have a V20 anymore, but he jumped in and helped when I lost my dev environment to build the kernel. That is what XDA is supposed to be about. Seriously man, huge thanks.
With that said, this is the v10r firmware + boot + system. For now, it is possible to dirty flash this, but if there are a lot of posts about problems, I will force a wipe in the zip since most people will be coming from 10m or even earlier (I think NATF is based on 10l, and I don't know what WETA is based on).
So, please, just backup your data and do a clean install
This is 100% stock v10r, bloat and all. It is ARB 0, so if you don't like it, you can go back to any older version.
Also, the 10r firmware doesn't work with 10m or lower system images -- 10p or 10q only. Since there are no custom ROMs currently that are based on 10p, 10q, or 10r, there is no reason to flash JUST the firmware without boot and system.
You will need to reinstall Magisk or SuperSU.
With the new firmware, the engineering aboot is able to init the screen correctly so the nasty warning message is clearly visible. This is the same warning as before, but it was garbled and you couldn't read it. Ignore it... your phone will boot.
Download here.
SHA: 5451146030393e490dcfba3558b620badefe75cd
-- Brian
Click to expand...
Click to collapse
You should really put a device check in the updater-script.... I couldve sworn this said H918 (8 and 0 look VERY similar on mobile), flashed it, full hard-bricked it.....
Qualcomm HS-USB QDLoader 9008
RIP
Tiny line in updater-script would have prevented this
Tilde88 said:
You should really put a device check in the updater-script.... I couldve sworn this said H918 (8 and 0 look VERY similar on mobile), flashed it, full hard-bricked it.....
Qualcomm HS-USB QDLoader 9008
RIP
Tiny line in updater-script would have prevented this
Click to expand...
Click to collapse
As much as I like and appreciate your work, you screwed up dude lol its ok to admit it
Sent from my LG-H910 using Tapatalk
@Tilde88 I did use an assert line at first, but I got tired of having to keep editing it and adding additional checks.
H910 || US996 || H915 || elsa || H910a
I am pretty sure that covers all the possibilities now, so I should probably put it back -- but at the end of the day, just have to be careful.
I could understand misreading the H910 on the forum post, but the zip file as well? That is an awful lot of seeing 8 instead of 0.....
I am sorry you toasted your device. Even if you bought it used, as long as it is still under the 2 year warranty, LG will fix it.
I am updating the first post with a big red warning....
-- Brian
runningnak3d said:
@Tilde88 I did use an assert line at first, but I got tired of having to keep editing it and adding additional checks.
H910 || US996 || H915 || elsa || H910a
I am pretty sure that covers all the possibilities now, so I should probably put it back -- but at the end of the day, just have to be careful.
I could understand misreading the H910 on the forum post, but the zip file as well? That is an awful lot of seeing 8 instead of 0.....
I am sorry you toasted your device. Even if you bought it used, as long as it is still under the 2 year warranty, LG will fix it.
I am updating the first post with a big red warning....
-- Brian
Click to expand...
Click to collapse
Lol I don't blame you at all. I flashed it, I did it. It will get repaired and I have other phones, so not a big deal. I meant it mostly for others. 2nd phone I brick in 10 years (other one was the HTC touch pro2 back in windows mobile days). I just hope there will be root for 10q in a few weeks, BC I'm sure lg will send a refurb with that.
As for the recovery, I saw the file and just flashed, who needs to read anyway lmao. /s
Anyway, thanks for your work. It flashed beautifully, and its a great way to update
Ok flashed and running decent. But twrp asked for encrypt password. Wasnt encrypted. I can get past it but its showing 0mb for internal storage. Anyone else get this? Any idea how to fix it? I flashed supersu but it wont install I'm thinking because of this error.
You flashed SuperSU before rebooting or after?
-- Brian
runningnak3d said:
You flashed SuperSU before rebooting or after?
-- Brian
Click to expand...
Click to collapse
The initial reboot? After. I went through setup and got everything done. Went back into twrp. Asked for a password to decrypt. I can hit cancel to get past it. Flashed supersu. Rebooted. No su app or root. I'm guessing because twrp thinks data is encrypted.
TWRP thinks your data is encrypted because it IS encrypted. If you don't flash SuperSU or Magisk before rebooting, then /data gets encrypted on the first boot. Now that it is encrypted, the only way to fix it is to format data in TWRP.
There is no way for you to back it up now either.
-- Brian
runningnak3d said:
TWRP thinks your data is encrypted because it IS encrypted. If you don't flash SuperSU or Magisk before rebooting, then /data gets encrypted on the first boot. Now that it is encrypted, the only way to fix it is to format data in TWRP.
There is no way for you to back it up now either.
-- Brian
Click to expand...
Click to collapse
Eh a wipe/format isnt the end of the world. Save my pics onto external and do it. Thanks for the help man and for the Rom. She is smooth. Btw I saw you thank askermk2000 for the kernel. Is that the same one as in a thread of its own? I was thinking of flashing his updated 1.1 version but if its the same I wont bother. Thanka again.

[ROM][STOCK][TWRP ZIP] Sanders Stock 7.1.1 rooted NPS26.116-61

Announcement: due to life complications in the form of a fire while I was away, all my current development for this phone has ceased until further notice. at some point I will start back up. but I digress;
AEX started messing up on my phone and I was able to use a friends laptop to flash the stock rom and made this verrrrrrry poorly made, yet functional dirty stock flashing zip.
its just a dd of the important partitions for stock rom, with magisk'd boot.img (you need the manager) and @Jleeblanch 's Resurected kernel v3.3
ONLY TESTED ON xt1806 US SINGLE SIM VARIANT. TRY AT YOUR OWN RISK
(but honestly if you can flash the NPS26.116-61 xml.zip from fastboot, this should boot)
known issues:
friggen borked the echo commands. didnt care enough to fix. it still tells you what its doing
doesnt install magisk manager
requires about 5 gb of free space on /sdcard during zip installation
features:
Boots to android
pre-rooted
everything from @Jleeblanch 's stock kernel:
Features
+ Passes SafetyNet
+ Magisk works as intended (including modules)
+ AnyKernel2 format
+ WireGuard support (more info)
+ Disabled CRC's on data blocks (30% increase in performace)
+ Fsync On/Off support
+ Added additional I/O Schedulers (Zen, SIO, FIOPS)
+ Increased zram compression streams
+ Tuned adrenoboost (disabled by default)
+ TCP Advanced Congestion Control
+ KCAL Color Control
+ Sound Control (by @flar2)
+ Linux-stable (wip)
+ CAF updates (wip)
+ Works same as stock (or better?
Click to expand...
Click to collapse
)
TL;DR
DOWNLOAD (1.7gb)(gdrive)
Instructions:
wipe data if coming from another rom
MOUNT DATA
install zip
ignore informative errors
-the ones that say unknown command
-ALSO THE FAULTY ERROR TWRP GIVES ABOUT AN ABSENT OS, ignore that'un too
--others might not need be ignored
download & install magisk manager
hit the thanks button maybe? im not even asking for a beer. and man i need one
enjoy
thank you to @Jleeblanch , if youre not ok with me including your kernel let me know and ill take it down sorry for not pre-checking
rom belongs to lenovorola, flash at your own risk not responsible for your stupidity and ignorance yada yada yada dont sue me
"yada yada yada dont sue me" lmao
Nice one. It's nice to have a option like that. Kudos.
vaporwavie said:
"yada yada yada dont sue me" lmao
Nice one. It's nice to have a option like that. Kudos.
Click to expand...
Click to collapse
thanks, gotta cover your ass yaknow? and yea someone released a "guide" to do it in the general section and didnt even try his own work lol. pretty sure thats called a suggestion not a guide
anywho figured someone else might need it in a pinch like i did.
One Debloated Version is interesting
Without the risk of sounding dumb, can someone please explain to me the difference between NPS26.116-61 and NPS26.116-45-5? I have the XT1806 in the US (3GB\32GB)...How many variants of this phone exist?!
smokinjoe2122 said:
Without the risk of sounding dumb, can someone please explain to me the difference between NPS26.116-61 and NPS26.116-45-5? I have the XT1806 in the US (3GB\32GB)...How many variants of this phone exist?!
Click to expand...
Click to collapse
NPS26.116-61 has December 1 security patch, updated thermal configs, and camera updates, just google the rest of the maintenance release notes.
XT1802 to XT1806
Usually the variations are the GSM bands, which models have NFC / DTV, single / dual sim, etc.
No worries on the kernel, glad to see it put to good use
This worked like a charm, thank you!
Hello,
Thank you for making this ROM.
My Moto somehow lost both the IMEI's and faced no network issues.
After trying everything, your ROM worked for me and had resolved all the issues in it.
NOTE: We didn't had any backup of any kind but this ROM still saved the day.
Thank you!
Continuing to rise and modify the different variants of rom stock? how they did with the moto g older? As a collection of stock ROMs
For example:
https://forum.xda-developers.com/moto-g/4g-development/rom-stock-motorola-4g-lollipop-rom-t3142816
Please kindly upload it on any other cloud storage .
I can't open the zip it's giving me some error
Can this be dirty flashed over stock, rooted NPS26.116-45 in order to get the latest security patch?
I'm computerless at the moment if anyone could mirror for the guy having issues downloading it would be appreciated (all I have is gdrive anyway) sorry man
jp0469 said:
Can this be dirty flashed over stock, rooted NPS26.116-45 in order to get the latest security patch?
Click to expand...
Click to collapse
This only flashes /system /oem /and boot. It shouldn't mess with anything on DATA. It's safe to try, but I'd recommend backing up just in case.
I'm 90% sure it would work, as a dirty update. I've used it to dirty reflashes the whole system and not data and it worked fine. just be aware that magisk is weird ever since v15. Reflashes of it may be necessary.
Lost my IMEI by flashing custom roms too
ekamran said:
Hello,
Thank you for making this ROM.
My Moto somehow lost both the IMEI's and faced no network issues.
After trying everything, your ROM worked for me and had resolved all the issues in it.
NOTE: We didn't had any backup of any kind but this ROM still saved the day.
Thank you!
Click to expand...
Click to collapse
hi, @ekamran
I also experienced you issue, no IMEI so no network, tried everything even this one. Still no IMEI. What are the things you tried prior to this to recover your IMEI? THanks.
gebcruz06 said:
hi, @ekamran
I also experienced you issue, no IMEI so no network, tried everything even this one. Still no IMEI. What are the things you tried prior to this to recover your IMEI? THanks.
Click to expand...
Click to collapse
Hey, This ROM is the only thing that has recovered my IMEI.
Before this, I had been in situation where my phone was stuck in BootLoader Mode only and couldn't even access Recovery Mode.
Then I had tried to flash the official firmware via Fastboot method of which some files installed and some didn't but fortunately, I regained access to Original Recovery Mode.
Then I had flased TWRP again and then flashed this ROM.
Everything sorted.
Thanks for developer
And keep it up
Does it work for the Indian variant
Ae3NerdGod said:
Announcement: due to life complications in the form of a fire while I was away, all my current development for this phone has ceased until further notice. at some point I will start back up. but I digress;
AEX started messing up on my phone and I was able to use a friends laptop to flash the stock rom and made this verrrrrrry poorly made, yet functional dirty stock flashing zip.
its just a dd of the important partitions for stock rom, with magisk'd boot.img (you need the manager) and @Jleeblanch 's Resurected kernel v3.3
ONLY TESTED ON xt1806 US SINGLE SIM VARIANT. TRY AT YOUR OWN RISK
(but honestly if you can flash the NPS26.116-61 xml.zip from fastboot, this should boot)
known issues:
friggen borked the echo commands. didnt care enough to fix. it still tells you what its doing
doesnt install magisk manager
requires about 5 gb of free space on /sdcard during zip installation
features:
Boots to android
pre-rooted
everything from @Jleeblanch 's stock kernel:
)
TL;DR
DOWNLOAD (1.7gb)(gdrive)
Instructions:
wipe data if coming from another rom
MOUNT DATA
install zip
ignore informative errors
-the ones that say unknown command
-ALSO THE FAULTY ERROR TWRP GIVES ABOUT AN ABSENT OS, ignore that'un too
--others might not need be ignored
download & install magisk manager
hit the thanks button maybe? im not even asking for a beer. and man i need one
enjoy
thank you to @Jleeblanch , if youre not ok with me including your kernel let me know and ill take it down sorry for not pre-checking
rom belongs to lenovorola, flash at your own risk not responsible for your stupidity and ignorance yada yada yada dont sue me
Click to expand...
Click to collapse
What is the use of flashing oem.
We only need boot and system . is there any risk in flashing OEM.img
ANDROID O said:
What is the use of flashing oem.
We only need boot and system . is there any risk in flashing OEM.img
Click to expand...
Click to collapse
i had changed the moto stock font. no risk, i think only the stock rom uses it normally. contains moto apps and stuff. when you flash an xml.zip it flashes it. i had originally tried to include the modem partition too but it was giving me issues. this is a stock rom so i included stock files, if you had somehow wiped or corrupted oem, stock rom (and possibly others) might not work correctly so i included it.

Don't flash Magisk 17.0+ ***on STOCK ROM***

Updated OP since this thread became useful to track if magisk works with our stock ROM.
The most recent version you can use at the moment is magisk 16.7 and magisk manager 5.8.3.
I suggest that you change the update channel to custom and set the address to 127.0.0.1
For the most recent Magisk version:
mickey36736 said:
I tested 19.3 on B01 oreo and it still bootloop.
Click to expand...
Click to collapse
Thanks for checking @mickey36736
rzarectha said:
It bootloops
Click to expand...
Click to collapse
I don't have any problems on Magisk 17.0 - safetynetpass on AEX(O), NitrogenOS(P) and PE(P) :cyclops:
Open Manager and update. Download latest stable one and flash it. Reboot.
raystef66 said:
I don't have any problems on Magisk 17.0 - safetynetpass on AEX(O), NitrogenOS(P) and PE(P) :cyclops:
Open Manager and update. Download latest stable one and flash it. Reboot.
Click to expand...
Click to collapse
mine bootlooped on stock. I'm naive enough to wait for the big update also, I got it from the beta channel. I'll try the stable and see what happens. I was assuming it's the same build
update: it bootloops on stock no matter what channel (stable/beta) you get it from.
I'll try to get a mod to help me change the OP title, I can't seem to be able to do it myself.
rzarectha said:
mine bootlooped on stock. I'm naive enough to wait for the big update also, I got it from the beta channel. I'll try the stable and see what happens. I was assuming it's the same build
update: it bootloops on stock no matter what channel (stable/beta) you get it from.
I'll try to get a mod to help me change the OP title, I can't seem to be able to do it myself.
Click to expand...
Click to collapse
You can change the OP tittle by pressing Go Advanced button next to the Save button when editing the OP post.
Not only on stock...
I am on LOS 14.1, saw the update notification, did update, and now also a bootloop...
I installed the zip of an earlier version to no avail.
Prophet 5 said:
I am on LOS 14.1, saw the update notification, did update, and now also a bootloop...
I installed the zip of an earlier version to no avail.
Click to expand...
Click to collapse
use the uninstaller zip first
Try 17.1. supposedly solves the bootloops.
bootloops are easily fixed by using the uninstaller first.
koftheworld said:
Try 17.1. supposedly solves the bootloops.
Click to expand...
Click to collapse
Nope, it doesn't. I'm on B35 and it still bootloops. Had to use the uninstaller to remove and revert to v16.7
KwesiJnr said:
Nope, it doesn't. I'm on B35 and it still bootloops. Had to use the uninstaller to remove and revert to v16.7
Click to expand...
Click to collapse
You have to use the uninstaller first and then flash 17.1.
Too late for me. I was on last years' Darkrom (LOS14.1 based, really stable, so no recent backup) and immediately got a bootloop which I'm still working to recover from... :crying:
pnin said:
Too late for me. I was on last years' Darkrom (LOS14.1 based, really stable, so no recent backup) and immediately got a bootloop which I'm still working to recover from... :crying:
Click to expand...
Click to collapse
Did you use the magisk uninstaller? If not, just reflash your bootloader
koftheworld said:
Did you use the magisk uninstaller? If not, just reflash your bootloader
Click to expand...
Click to collapse
Excuse my ignorance but how would reflashing the bootloader help. Doesn't Magisk modify the boot image?
I figure that if flashing the uninstaller and then flashing v17.1 still results in a bootloop I (personally speaking) would go into TWRP and manually remove any Magisk related directories/files, maybe flash the uninstaller again (might catch something I missed), and then dirty flash Dark ROM (fresh boot image). Flash Magisk 17.x afterward.
That said, I am a non-Magisk kind of guy (not present on any ROMs or devices) so I might not know what I'm talking about. [emoji16]
Dark ROM. FTW. [emoji41]
ZTE Axon 7 A2017U, AospExtended v4.6 ROM, LlamaSweet 0.5 Kernel, microG (NoGapps), Multiboot, XDA Legacy
marcdw said:
I (personally speaking) would go into TWRP and manually remove any Magisk related directories/files, maybe flash the uninstaller again (might catch something I missed), and then dirty flash Dark ROM (fresh boot image).
Click to expand...
Click to collapse
Care to clue me in on those directories/files? I'm having a hard time here, dirty flashing my previous ROM, getting up to setup and then have something fail catastrophically over and over again...
I have even had to restore recovery through fastboot mode now. :silly:
I did not flash Magisk 17.x on Stock B35 (stayed with v16.4), but installing the latest Magisk Manager (v5.9.1) resolved the previous SafetyNet Check errors
Using stock anything above and v17.0 will bootloop using stock,
Just my 2cents, if that your issue just do the following:
-Download v16.7 first in case you don't have it yet, and move it to the SDCard.
* Head back to TWRP
* Flash v16.7 or your preferred release.
* You're good to go.
pnin said:
Care to clue me in on those directories/files? I'm having a hard time here, dirty flashing my previous ROM, getting up to setup and then have something fail catastrophically over and over again...
I have even had to restore recovery through fastboot mode now. :silly:
Click to expand...
Click to collapse
Not sure to be honest. Last time I had Magisk was around v15.x. When I initially rooted my Moto Magisk was part of the process. Even though the stock ROM is using SuperSU it seems I didn't fully remove Magisk. I have the following remnants visible in TWRP...
/data/magisk
/data/magisk.img
and files in /data/adb/
Not sure why everything is failing so badly on your end. I can't test things on my Axon 7 since I use DualBoot Patcher where Magisk is a no go.
Moto G5S Plus XT1806, MSM-Xtended v2.5 ROM, MultiROM, XDA Legacy
So I have managed to fully restore the phone, including updating Magisk to v17.1 (v16.0 didn't work at all, v14 did).
Apart from Goggle Messages that is, which FC whenever I try to start it (both current and past versions).
I was careful with Magisk in the past, I will be even more so in the future. No dot zero releases for me from now on. Thanks for your tips, people.
pnin said:
So I have managed to fully restore the phone, including updating Magisk to v17.1 (v16.0 didn't work at all, v14 did).
Apart from Goggle Messages that is, which FC whenever I try to start it (both current and past versions).
I was careful with Magisk in the past, I will be even more so in the future. No dot zero releases for me from now on. Thanks for your tips, people.
Click to expand...
Click to collapse
I'm not currently having Magisk issues, but Google Messages, after the recent update, does the same here. Gave up on it & switched to Textra.
New beta version released. Still bootloop

Fire TV Stick 4K (mantis) Prerooted Stock Images [6.2.8.1_r3]

As usual, this WILL void your warranty and I am NOT responsible for anything you do with this. Installing it properly won't brick your Fire TV, but doing stupid things with it might.
First, you must be unlocked. You can follow the instructions here for making that happen.
If you are first starting, you should first unlock, then install this ROM, and THEN install Magisk for root or any other addons. This rom uses addon.d to preserve Magisk and any other addons, but any system modifications like Magisk, gapps, etc, that you have installed prior to this ROM will NOT be preserved.
If you've already unlocked and installed Magisk, then after installing this ROM you need to reinstall Magisk in TWRP.
Starting with 6.2.6.6, Magisk is always installed.
Beyond that, Magisk and any other addons will be preserved as you flash newer roms. Consequently, if you would like to remove root, you will need to wipe /system in TWRP prior to installing this ROM. That will prevent it from being restored when installing the ROM.
Thanks to @k4y0z and @xyz` for the unlock.
NEVER FLASH A STOCK ROM >= 6.2.8.0 AFTER FLASHING 6.2.8.1_r2 OR LATER! THIS WILL BLOW AN EFUSE.
Changelog and Downloads:
October 24, 2021 - 6.2.8.1_r3 (md5sum: 3795edc2d640932a88da39da8a0811c5)
July 17, 2021 - 6.2.8.1_r2 (md5sum: e9e37a2d485a3397df041938818421e9)
This includes updated tz firmware to fix the device locking up when trying to play video.
April 3, 2021 - 6.2.8.0_r1 (md5sum: 2efdfc5728caba2953a351a082023a59)
December 26, 2020 - 6.2.7.7_r1 (md5sum: b835e29bb29458004063121a422c1bf7)
May 3, 2020 - 6.2.7.1_r1 (md5sum: 56ec885e5bd258682c90e8f08371301d)
November 10, 2019 - 6.2.6.8_r1 (md5sum: 8cdc16239df36c8640004232918c5477)
October 19, 2019 - 6.2.6.6_r1 (md5sum: df8f3d033fddf66a1b4aa3a6b228196b)
Starting with this version, Magisk will always be installed.
This includes updated tz firmware to fix LICENSE_ERROR with Prime video.
October 13, 2019 - 6.2.6.5_r1 (md5sum: bdde0303d8db5495ac6dc2aaf476d2f4)
Awesome!! Thanks!!
@rbox,
Quick question,
Initial unlocking and rooting was successful. However, I did what I usually do which is update Magisk using the manager and after the reboot, it is looping @ the amazon image. Any idea?
vasir13 said:
@rbox,
Quick question,
Initial unlocking and rooting was successful. However, I did what I usually do which is update Magisk using the manager and after the reboot, it is looping @ the amazon image. Any idea?
Click to expand...
Click to collapse
From the unlock page:
Important information
Don't flash boot/recovery images from FireOS (FlashFire, MagiskManager etc.)
rbox said:
From the unlock page:
Important information
Don't flash boot/recovery images from FireOS (FlashFire, MagiskManager etc.)
Click to expand...
Click to collapse
Yes .... I know ... called selective reading .... I got into TWRP and will try your image now ...
Happy to see the pre-rooted roms from you on mantis! It's starting to feel like the good old days again
Thank you, I feel safer already.
Any idea what version of gapps would work on this? Also, any idea if installing nanodroid, patched playstore & patching the ROM for signature spoofing be dangerous (as in bugger up the BL/TWRP)?
Awesome. This community is great.
Does this work for european (Italian) Sticks? (Prime video, Alexa etc etc).
Regards and Thanks a bunch!
Hi,
I successfully installed the hacked bootloader and TWRP a few days ago, but I did not do anything else. I was still on the original 6.2.5.8 version.
Today I wanted to flash the prerooted 6.2.6.5 and I can't manage to boot it (and since I did not expect problems, I did not make a backup of the old system). I cannot go past the "firetv" boot logo and in this stage "adb logcat" is not yet working, so I don't see any logs.
First boot was just installing the ROM. Second boot with previously wiping Cache / Dalvik. Finally I wiped also data (and Cache/Dalvik again). I cannot get past the boot logo.
So what can I do? Was there a firmware update between 6.2.5.8 and 6.2.6.5, which I need and is not included in the prerooted image? I'm just guessing since I cannot explain anything else...
Thanks Tim
tehlers said:
So what can I do? Was there a firmware update between 6.2.5.8 and 6.2.6.5, which I need and is not included in the prerooted image? I'm just guessing since I cannot explain anything else...
Click to expand...
Click to collapse
Have you compared the md5 of the download (push the md5file + ROM and let TWRP check this during install)?
Sus_i said:
Have you compared the md5 of the download (push the md5file + ROM and let TWRP check this during install)?
Click to expand...
Click to collapse
Yes, I have checked MD5 on my notebook after download, but not after pushing the file to the stick. I will do that now and post it here (with edit). But I doubt this being the issue.
EDIT: MD5 of the zip in the stick is also ok.
tehlers said:
EDIT: MD5 of the zip in the stick is also ok.
Click to expand...
Click to collapse
Ok. The prerooted Rom should be a full stock update, rbox said that a few days ago.
Any hardware damages or missing parts on your stick?
Edit: Have you flashed the magisk.zip behind the ROM?
Sus_i said:
Ok. The prerooted Rom should be a full stock update, rbox said that a few days ago.
Any hardware damages or missing parts on your stick?
Click to expand...
Click to collapse
The hardware is fully ok. The installation of hacked BL worked very smoothly and the stick did work with the original firmware until I flashed the prerooted one today. I have two guesses, but I don't know how to proceed:
1. I know there are sometimes firmware updates on specific fire OS versions, which need to be installed for later versions (for example version 5.2.6.7 on fireTV 2 [sloane]). So if I need a firmware update for 6.2.6.5 (from 6.2.5.8) I should probably flash 6.2.5.8 back and let the fire OS do the first update.
2. Or there is something left from the old version (in one of the partitions) which prevents this version from booting. This would mean that you need to be already on 6.2.6.5 (or at least on a higher version than me), that this ROM works.
In both cases, I would probably recover when getting the original firmware version 6.2.5.8 from somewhere.
EDIT: As I said in the first post, I did not do anything with the original ROM, except flashing the hacked BL and TWRP, no Magisk or whatever.
Best
Tim
tehlers said:
The hardware is fully ok. The installation of hacked BL worked very smoothly and the stick did work with the original firmware until I flashed the prerooted one today. I have two guesses, but I don't know how to proceed:
1. I know there are sometimes firmware updates on specific fire OS versions, which need to be installed for later versions (for example version 5.2.6.7 on fireTV 2 [sloane]). So if I need a firmware update for 6.2.6.5 (from 6.2.5.8) I should probably flash 6.2.5.8 back and let the fire OS do the first update.
2. Or there is something left from the old version (in one of the partitions) which prevents this version from booting. This would mean that you need to be already on 6.2.6.5 (or at least on a higher version than me), that this ROM works.
In both cases, I would probably recover when getting the original firmware version 6.2.5.8 from somewhere.
Best
Tim
Click to expand...
Click to collapse
OK :good:
Have you installed the magisk.zip behind the rom? May be it won't start without that? You may try that...
May be that dm-verity and/or SELinux enforcing is a problem without magisk, as magisk take care of that automatically...
No mouse Emulator support in TWRP with the 4K stick?
How do you install the rom if you don't have USB OTG cable?
Sus_i said:
OK :good:
Have you installed the magisk.zip behind the rom? May be it won't start without that? You may try that...
May be that dm-verity and/or SELinux enforcing is a problem without magisk, as magisk take care of that automatically...
Click to expand...
Click to collapse
Yes, that's it. Magisk needs to be installed after the "prerooted" image! Now the stick boots up!
Amazing, thank's!
I thought a prerooted image is prerooted.
@rbox: It would be nice, if you could mention this in the first post.
T1inkering said:
No mouse Emulator support in TWRP with the 4K stick?
How do you install the rom if you don't have USB OTG cable?
Click to expand...
Click to collapse
for example with ADB / TWRP Commands, something like that...
Code:
adb push ~/Desktop/mantis-6.2.6.5-rooted_r1.zip /sdcard/
adb push ~/Desktop/Magisk-v19.3.zip /sdcard/
adb reboot recovery
adb shell
twrp install /sdcard/mantis-6.2.6.5-rooted_r1.zip
twrp install /sdcard/Magisk-v19.3.zip
twrp wipe cache
twrp wipe dalvik
reboot -p
tehlers said:
Yes, that's it. Magisk needs to be installed after the "prerooted" image! Now the stick boots up!
Amazing, thank's!
I thought a prerooted image is prerooted.
@rbox: It would be nice, if you could mention this in the first post.
Click to expand...
Click to collapse
It is mentioned.. but not thats an issue without flashing magisk
Sus_i said:
It is mentioned.. but not thats an issue without flashing magisk
Click to expand...
Click to collapse
That's what I mean. It's not mentioned that you need Magisk in any case (to boot the image as such *and* probably also to get root [which is not prerooted then?]).
Thanks again!
puppinoo said:
Awesome. This community is great.
Does this work for european (Italian) Sticks? (Prime video, Alexa etc etc).
Regards and Thanks a bunch!
Click to expand...
Click to collapse
I reply to myself and happy to confirm I installed this "generic" image to my US Stick 4K and after I accept terms of use *Italian* Alexa and Prime video seem to wotk fine.
If I remember well my previous image was the 6.2.5.8 (basically the one I installed when the exploit for Fire TV Stick 2 (Tank) was released but can't be 100% sure.
Now I have to try it on my *Italian* Stick 4k (bought on amazon.it).
Amazing and thanks a lot again.
Puppinoo.
So great to see @rbox 'es prerooted roms for the Fire TV Stick 4k
There are some things that I am not familiar with:
1. What is magisk for and what if I don't install it?
2. Does root not work without magisk?
On the older Fire TV Devices we did never have to install magisk or so and it was prerooted with rboxes roms and root was working. Why is everybody talking about magisk? Can magisk break anything or be critical like xposed was on the Fire TV 2 box? I remember that xposed framework was a pretty messy issue for recent Fire TV 2 (Sloane) pre-rooted roms. Magisk seems to go deeply into the system, similar to xposed framework, isn't it?

Categories

Resources