Related
Here we have a collection of RUUs, firmware, untouched system backups, and stock rooted ROMs...
Latest RUU
Sprint_HTC_One_M9_4.27.651.4_RUU
0PJAIMG RUUs
0PJAIMG_Sprint_HTC_One_M9_4.27.651.4_RUU.zip
0PJAIMG_Sprint_HTC_One_M9_3.41.651.41_RUU.zip
0PJAIMG_Sprint_HTC_One_M9_3.41.651.21_RUU.zip
0PJAIMG_Sprint_HTC_One_M9_3.41.651.13_RUU.zip
0PJAIMG_Sprint_HTC_One_M9_3.41.651.4_RUU.zip
0PJAIMG_Sprint_HTC_One_M9_2.11.651.19_RUU.zip
0PJAIMG_Sprint_HTC_One_M9_2.6.651.11_RUU.zip
0PJAIMG_Sprint_HTC_One_M9_1.32.651.30_RUU.zip
0PJAIMG_Sprint_HTC_One_M9_1.32.651.17_RUU.zip
*credit to @Rydah805 for the 1.32.651.17 RUU
Rename to 0PJAIMG.zip, copy to sd card, boot into download mode, it should scan card & prompt to install
***NOTE*** S-ON users can ONLY flash signed firmware!!!
Firmware
4.27.651.4 Signed Firmware from OTA, removed recovery (fastboot flashable): https://www.androidfilehost.com/?fid=457095661767155280
4.27.651.4 Modified Firmware from RUU, removed recovery (fastboot flashable): https://www.androidfilehost.com/?fid=817550096634761570
4.27.651.4 Modified Firmware from RUU, removed recovery & boot (fastboot flashable): https://www.androidfilehost.com/?fid=745425885120723749
4.27.651.4 Full Firmware from RUU (fastboot flashable): https://www.androidfilehost.com/?fid=817550096634761569
Previous Firmware
3.41.651.41 Modified Firmware from RUU, removed recovery (fastboot flashable): https://www.androidfilehost.com/?fid=385035244224405571
3.41.651.41 Modified Firmware from RUU, removed recovery & boot (fastboot flashable): https://www.androidfilehost.com/?fid=385035244224405569
3.41.651.41 Full Firmware from RUU (fastboot flashable): https://www.androidfilehost.com/?fid=385035244224405570
3.41.651.31 Modified Firmware from RUU, removed recovery (fastboot flashable): https://www.androidfilehost.com/?fid=385035244224398913
3.41.651.31 Modified Firmware from RUU, removed recovery & boot (fastboot flashable): https://www.androidfilehost.com/?fid=529152257862681927
3.41.651.31 Full Firmware from RUU (fastboot flashable): https://www.androidfilehost.com/?fid=385035244224398912
3.41.651.21 Modified Firmware from RUU, removed recovery (fastboot flashable): https://www.androidfilehost.com/?fid=529152257862669390
3.41.651.21 Modified Firmware from RUU, removed recovery & boot (fastboot flashable): https://www.androidfilehost.com/?fid=529152257862669389
3.41.651.21 Full Firmware from RUU (fastboot flashable): https://www.androidfilehost.com/?fid=529152257862669388
3.41.651.13 Signed Firmware from OTA for S-ON users(fastboot flashable): https://www.androidfilehost.com/?fid=24651430732238190
3.41.651.13 Modified Firmware from OTA, removed recovery (fastboot flashable): https://www.androidfilehost.com/?fid=24651430732238219
3.41.651.13 Modified Firmware from OTA, removed recovery & boot (fastboot flashable): https://www.androidfilehost.com/?fid=24651430732238218
3.41.651.13 Full Firmware from RUU (fastboot flashable): https://www.androidfilehost.com/?fid=24686680535467780
3.41.651.4 Full Signed Firmware from OTA (fastboot flashable): https://www.androidfilehost.com/?fid=24407100847294492
3.41.651.4 Modified Firmware from OTA, removed recovery (fastboot flashable): https://www.androidfilehost.com/?fid=24407100847294493
3.41.651.4 Modified Firmware from OTA, removed recovery & boot (fastboot flashable): https://www.androidfilehost.com/?fid=24407100847294494
2.11.651.19 Full Firmware from OTA (fastboot flashable): https://www.androidfilehost.com/?fid=24052804347811177
2.11.651.19 Modified Firmware from OTA, removed recovery (fastboot flashable): https://www.androidfilehost.com/?fid=24052804347811176
2.11.651.19 Modified Firmware from OTA, removed recovery & boot (fastboot flashable): https://www.androidfilehost.com/?fid=24052804347811175
2.11.651.19 Radio only from OTA (fastboot flashable): https://www.androidfilehost.com/?fid=24052804347811174
2.6.651.11 Full Firmware from OTA (fastboot flashable): https://www.androidfilehost.com/?fid=24052804347767489
2.6.651.11 Modified Firmware from OTA, removed recovery (fastboot flashable): https://www.androidfilehost.com/?fid=24052804347770518
2.6.651.11 Modified Firmware from OTA, removed recovery & aboot (fastboot flashable): https://www.androidfilehost.com/?fid=24052804347767490
2.6.651.11 Radio only from OTA (fastboot flashable): https://www.androidfilehost.com/?fid=24052804347767491
1.32.651.30 Full Firmware from OTA (fastboot flashable): https://www.androidfilehost.com/?fid=95916177934554030
1.32.651.30 Modified Firmware from OTA, removed recovery & aboot (fastboot flashable): https://www.androidfilehost.com/?fid=95916177934554191
1.32.651.30 Radio only from OTA (fastboot flashable): https://www.androidfilehost.com/?fid=95916177934554197
1.32.651.17 Full Firmware from RUU (fastboot flashable): https://www.androidfilehost.com/?fid=95916177934552130
1.32.651.17 Radio only from RUU (fastboot flashable): http://206.174.247.158/public/android_dev/1.32.651.17_radio_only.zip
*credit to @deakelem for the .17 radio zip, thx!
Flash Firmware via bootloader (requires micro sd card)....
-rename firmware to 0PJAIMG.zip
-copy 0PJAIMG.zip to ext_sd card
-boot into bootloader or download mode
-it will scan your ext_sd card, then ask if you want to start the update
-press volume up & let it do it's thing...
Flash Firmware via fastboot, no ext sd card needed...
-rename firmware to firmware.zip
-copy firmware.zip to your sdk folder
-boot into bootloader or download mode
-plug in usb
-select fastboot option (screen should say fastboot usb)
-type fastboot oem rebootRUU
-when u see the black screen w/ HTC, type fastboot flash zip firmware.zip
-when it's done, type fastboot reboot
OTAs
OTA_HIMA_WHL_N70_SENSE80_SPCS_MR_Sprint_WWE_4.27.651.4-3.41.651.41_release_500479.zip
OTA_HIMA_WHL_M60_SENSE70_SPCS_MR_Sprint_WWE_3.41.651.4-2.11.651.180_release_470372.zip
OTA_HIMA_WHL_L51_SENSE70_SPCS_MR_Sprint_WWE_2.11.651.19-2.6.651.11_R3_release_449495.zip
OTA_HIMA_WHL_L51_SENSE70_SPCS_MR_Sprint_WWE_2.6.651.11_R3-1.32.651.30_R_release_439101.zip
OTA_HIMA_WHL_L50_SENSE70_SPCS_Sprint_WWE_1.32.651.30_R-1.32.651.17_R2_release_427417.zip
Stock Rooted ROMs
Before flashing this Stock Rooted ROM or making any system change, make sure you have done a clean SYSTEM IMG BACKUP using TWRP 2.8.6.0 or newer!!! See post# 2 for more information.
Stock Rooted 3.41.651.41 ROM
Bad_Boyz_Sprint_ONE_M9_4.27.651.4_stock_rooted.zip
-SuperSu & BusyBox added
Previous Stock Rooted ROMs
Bad_Boyz_Sprint_ONE_M9_3.41.651.41_stock_rooted.zip
Bad_Boyz_Sprint_ONE_M9_3.41.651.31_stock_rooted.zip
Bad_Boyz_Sprint_ONE_M9_3.41.651.21_stock_rooted.zip
Bad_Boyz_Sprint_ONE_M9_3.41.651.13_stock_rooted.zip
Bad_Boyz_Sprint_ONE_M9_3.41.651.4_stock_rooted.zip
Bad_Boyz_Sprint_ONE_M9_2.11.651.19_stock_rooted_deodexed.zip
Bad_Boyz_Sprint_ONE_M9_2.6.651.11_Deodexed_Stock_Rooted.zip
Bad_Boyz_Sprint_ONE_M9_2.6.651.11_Stock_Rooted.zip
Bad_Boyz_Sprint_ONE_M9_1.32.651.30_Deodexed_Stock_Rooted.zip
Bad_Boyz_Sprint_ONE_M9_1.32.651.30_Stock_Rooted.zip
Bad_Boyz_Sprint_ONE_M9_1.32.651.17_Stock_Rooted.zip
-SuperSu & BusyBox added
-unsecure boot.img
-init.d support
XDA:DevDB Information
[RUU][Firmware][Stock Rooted ROM][Stock Backup]Sprint HTC One M9 | 1.32.651.17, ROM for the Sprint HTC One (M9)
Contributors
OMJ, chas123, benny3
ROM OS Version: 7.x Nougat
Version Information
Status: Stable
Stable Release Date: 2015-04-05
Created 2015-04-05
Last Updated 2017-08-02
Reserved
here is a nice batch tool from @Sneakyghost I edited for Sprint...(Tasker_1.2.8.bat was edited, and stock Sprint recovery added).
original thread can be found from HERE, go give him a thanks!
Extract to folder & run Tasker_1.2.8.bat
DOWNLOAD Android_Tasker_1.2.8_Sprint_M9
Sneakyghost said:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The "Android_Tasker" Batch Tool - a thing i am using for myself since 2012 and which i am sharing just because i have it. It is neither good nor special, but its the way i work and people who follow the instructions here might find it easier to use the same setup as we do.
It also has the "FUU" method included - details on that method will be added at a later stage. We do not consider the FUU a good option to flash Firmware anymore because we realized that getting away from ADB and Fastboot with toolkits makes troubleshooting harder at a later stage - people relying entirely on toolkits and tools will mostly not understand what is happening and helping there is much harder.
Since everything i do basically works out of the C:\Android\com path, all my zipped-up stuff extracts to that location. The FUU and the Task-Batch-Script both work from that location. This is simply to enable easier and faster creation of new zip’s if they all use the same base structure.
If you prefer to work from a different location. you can specify a different path in the installer. However, the batch scripts do not adjust automatically, which means if you use another path, you might need to open up the scripts in an editor and adjust some paths manually.
Preview:
DOWNLOAD
MD5: 84A4968A9C698FA328A6C13DCB1D764F
The installer is just a simple WinRAR self extracting archive - there is NOTHING BAD in there i swear! Open it with WinRAR 5 and look inside. You will see if you don't trust me.
Changelog:
1.2.8
Splash1 converter works now. Flashing Splash1 now needs a reboot to Bootloader - it's not working in Download Mode! (limited DD support on the M9 and general flashing system changes).
Swapped out recoveries for newer versions.
Finally added the complete file set from RUU 3.0.1.15 - the newest M9 RUU. ADB and Fastboot are identical to the previous version from Llabtoofer though.
Screenrecord removed - can’t be bothered figuring out why it doesn’t work anymore. Probably SELinux and general Android 5.x security like with the screenshot function. Not really needed either. There are other solutions.
1.2.7
Swapped out recoveries for newer versions.
Swapped out ADB and Fastboot for a newer pack (thanks @LlabTooFeR) - now this Tool is fully M9 compatible and even flashes large RUU.zips.
1.2.6
Changed everything to M9 files and methods. I HOPE I didn't oversee anything. Please test carefully!
Added stock_recovery_1.32.401.8.img
Added TWRP Recovery 2.8.6.0 fixed version from Captain_Throwback SOURCE Post #2 Beta version
Added original HIMA Splash1 - S-OFF phones only!
Previous versions:
1.2.5
Added TWRP Recovery 2.8.5.2 from Captain_Throwback (All M8 devices)
Fixed Recovery Screenshot option (20)
1.2.4
Added newer RUU structure (2.0.16.2014 - from 4.16.1540.8 Dev Edition RUU)
Added Stock Recovery 4.16.401.10.img (WWE)
Changed the License and SFX texts again (Installer) - never happy with it.
1.2.3
Fixed some serious crap nobody reported. I just found out myself.
Added Stock Recovery 4.16.1540.8 (sorry still don't have the WWE recovery, but i guess they are identical)
Added TWRP 2.8.4.0 from the M8 tree of Dees_Troy.
1.2.2
Added Stock Recovery3.28.401.7
1.2.1
Added Microsoft's vcredist_x86_2008_SP1.exe to the installer because the ARUWizard is build on the x86 Visual Studio 2008 runtime. This resolves the "side-by-side configuration" error.
Added 3.28.401.6 stock recovery and splash
Added newer RUU structure (doesn't do any difference though, just keeping it up to date)
Added TWRP 2.8.0.3 (it still has slight issues with MTP which will be fixed soon but for now, this is good enough)
Changed a few lines in the script (minor, cosmetical stuff)
Updated the INFO PDF (option 24)
Known Issues:
Kernel Flashing needs fixing - can only work in fastboot now due to SELinux and related crap.
The partition Dumper is not correctly working, probably also due to SELinux.
Anyone used to like @squabbi's fully GUI based toolkit? He's picked it up on the M9 as well - maybe you like GUI better than commandline. Then head over here: http://forum.xda-developers.com/showpost.php?p=59949972&postcount=1
Click to expand...
Click to collapse
Reserved
*IMPORTANT INFO* taken from this thread!!!
Captain_Throwback said:
Frequently Asked Questions (FAQ)
1. Why is this device different than my previous HTC device?
With the M9, HTC has moved to a block-based OTA system. This means that even mounting system as read-write (as TWRP typically does during startup checks) will nullify the device's ability to take an OTA. Any other changes to the system partition will also cause an OTA to fail (even if that check is removed from the OTA zip) due to "unexpected contents."
2. Which version of TWRP am I supposed to use?
Right now, the latest official version (2.8.7.0) is the best version to use.
3. Why is there a "System" backup option and a "System Image" backup option now?
The "System" option is the standard tar backup. The "System Image" option is only relevant if your system is unmodified. This allows you to make a fully stock backup that can be restored later to take an OTA.
NOTE: If you are using a FAT32-formatted card, a "System Image" backup will fail, due to the 4GB file limit on that format. For a successful System Image backup, NTFS or exFAT-formatted storage must be used (either SD card or USB-OTG)
4. How am I supposed to root?
If you would only like to root via SuperSU, after making a stock backup, flash the BETA version of SuperSU posted here which properly mounts system, even when TWRP has it mounted read-only.
5. I tried to install x ROM, but it won't boot. Should I use TWRP 2.8.5.0 to flash it?
No, you shouldn't. You should use the version of TWRP recommended above. If the ROM updater-script is done properly, even if your device has system mounted read-only, the ROM should still flash fine. If your ROM chef/team has chosen to mount the partitions some other way, then you may have to mount system manually in order for the ROM to flash successfully. This can be done in the Mount menu, by unchecking the "Mount system as read-only" box and then checking the box next to System to mount it. The very act of booting 2.8.5.0 will change the system checksum, making it impossible to get a fully stock backup.
6. So what's the proper procedure to root without breaking OTA?
There is no way to take an OTA after you root. However, prior to rooting, you can take a fully untouched system image backup with TWRP, which can be used to restore a fully stock system to the device in order to take an OTA.
7. How do I backup stock recovery prior to flashing TWRP?
You can't. The "fastboot boot" command appears to be disabled on the M9's ABOOT, so TWRP must be fastboot flashed over stock recovery. The firmware zip included in the OTA will include a usable stock recovery image. That can be extracted and flashed after stock system is restored so that the OTA can be applied.
8. How do I restore stock system so that I can accept an OTA?
Check the "Mount system as read-only" box in the Mount menu.
Restore stock "System Image" backup (This will only work if you've made a System Image backup prior to making any modifications to /system). As of the official 2.8.6.1 version, it is no longer necessary to fastboot flash the stock system image.
NOTE: If you made a stock system backup with one of the Beta TWRP versions, you will have to rename the backup file in the backup folder manually from "system.emmc.win" to "system_image.emmc.win" for the new official TWRP to see it as a "System Image" backup rather than a "System" backup. Otherwise, you'll get an error that the backup can't be restored because system is read-only.
Fastboot flash stock recovery (fastboot flash recovery recovery_signed.img)
NOTE: It is also possible to restore stock recovery via the TWRP GUI. Rename the stock recovery file to "recovery.emmc.win" and place in the backup folder with the stock system image. Recovery will then show as a restore option. MAKE SURE YOU REALLY WANT TO DO THIS, AS TWRP WILL BE GONE WHEN YOU REBOOT OUT OF RECOVERY!!
Reboot to system, install OTA.
9. What if I have an RUU? Do I need to worry about all this OTA nonsense?
Not if you don't care about losing all your data. If you're S-ON and have an RUU available for your exact variant (model ID and CID must match) and software number (main version must be the same or newer), then you can get back to a fully stock state by relocking (fastboot oem lock) and flashing an RUU. However, if you'd prefer to take an OTA to keep your data intact, the method stated above is how to do so. Or, you can just run a custom ROM and wait for your ROM chef to update their ROM to the latest software (though you'll still have to find a way to update your firmware if you're not S-OFF)
10. After I go through all this and successfully apply an OTA, how do I make sure I have a clean starting point again?
After the OTA is applied and TWRP is flashed, it will once again detect an untouched system, which will mount system read-only and allow you to make a fully stock backup and start the process over again, this time with the new base.
11. How do I get that new stock theme from the Screenshots tab?
See here.
12. What if I'm unlocked but unrooted and don't have access to a computer? How can I install TWRP?
See here.
Hima-Specific Peculiarities/Issues
IT IS NOT RECOMMENDED TO USE ANY VERSION OF TWRP PRIOR TO 2.8.6.0. The previous version(s) mount system read-write and will break the system checksum on initialization, making it impossible to get a fully stock system backup.
As of TWRP 2.8.6.0, in order to preserve system intergrity to complete a fully stock system backup, system is mounted as read-only. Starting with the official TWRP 2.8.6.1, TWRP will detect whether system is unmodified and give you the option to leave it as read-only or mount it read-write. The box to select/deselect this option is in the "Mount" menu.
Current TWRP "bugs" for Hima
One cannot simply flash zips larger than 2GB (upstream bug)
Battery may read 66% when booting into recovery (plugging into USB appears to correct this issue)
Touch may occasionally stop working when using AROMA (may be related to device overheating)
Beta Versions
These versions will include fixes not currently merged into the official source. The new beta naming convention with always start with the official base, followed by author (in this case, me) and beta version. This should help to eliminate some of the version number confusion of previous betas.
Beta Changelog:
Code:
[I][URL=http://forum.xda-developers.com/devdb/project/dl/?id=13383]2.8.7.1_CPTB-B1[/URL][/I]
[SIZE="2"]Includes all official 2.8.7.0 & [URL="http://forum.xda-developers.com/one-m9/orig-development/recovery-twrp-touch-recovery-t3066720/post61580654"]2.8.7.1 test build[/URL] patches, and the following additional patch(es):[/SIZE]
[LIST]
[*][URL=https://gerrit.omnirom.org/12728][WIP] gui: stock theme rework[/URL]
[*][URL=https://gerrit.omnirom.org/14003]Update CUSTOM_LUN_FILE from AOSP USB config[/URL]
[*][URL=https://gerrit.omnirom.org/14002]Update path for libcryptfs_hw to proper variable[/URL]
[*][URL=https://gerrit.omnirom.org/14009]Properly set sys.usb.config when ums is enabled.[/URL]
[*][URL=https://gerrit.omnirom.org/13971]Add seclabel to recovery service[/URL]
[*][URL=https://gerrit.omnirom.org/11756]Allow devices to override USB init[/URL][/LIST]
Older Beta versions (current official version is newer):
Code:
[SIZE=2][I][URL="http://forum.xda-developers.com/devdb/project/dl/?id=13016"]2.8.6.1_CPTB-B2[/URL][/I]
[SIZE="1"]Includes all CPTB-B1 patches, and the following additional patch(es):[/SIZE]
[LIST]
[*][URL="https://gerrit.omnirom.org/13818"]Fix ORS scripts displaying an error after completing[/URL][/LIST]
[I][URL="http://forum.xda-developers.com/devdb/project/dl/?id=13015"]2.8.6.1_CPTB-B1[/URL][/I]
[SIZE="1"]Includes the following patches not yet merged to the official:[/SIZE]
[LIST]
[*][URL=https://gerrit.omnirom.org/12728][WIP] gui: stock theme rework[/URL]
[*][URL="https://gerrit.omnirom.org/13746"]minuitwrp: fix crash when taking a screenshot.[/URL]
[*][URL="https://gerrit.omnirom.org/13747"]partition: recreate tw_internal_path(/data/media/0), after wipe media from data or format /data.[/URL]
[*][URL="https://gerrit.omnirom.org/13793"]Fix system read only behavior during boot[/URL][/LIST]
[/SIZE]
Device specific page on our website
Download link to current and past versions
Click to expand...
Click to collapse
Reserved
Thanks J.
Thanks for this. Going to save a lot of headaches.
solver404 said:
Thanks for this. Going to save a lot of headaches.
Click to expand...
Click to collapse
thx for the stock backup!
For some strange reason my dialer does not work i cannot receive calls nor make them
same here with the dialer
londawg314 said:
same here with the dialer
Click to expand...
Click to collapse
Are you using the stock rooted rom or the system backup?
Macropoutsis said:
Are you using the stock rooted rom or the system backup?
Click to expand...
Click to collapse
I am using the stock ROM .. I backed up my ROM and flashed this ROM .. I than returned to my backup and the dialer works fine ..
Do changes to the /system partition persist a reboot with this or do we need to wait for S-OFF for that?
StickyEyez said:
For some strange reason my dialer does not work i cannot receive calls nor make them
Click to expand...
Click to collapse
londawg314 said:
same here with the dialer
Click to expand...
Click to collapse
I'll have to test it when I get the chance...not sure why it wouldn't work, as it's stock from dump
m03sizlak said:
Do changes to the /system partition persist a reboot with this or do we need to wait for S-OFF for that?
Click to expand...
Click to collapse
not sure, I'll have to test this too, may need to wait for s-off
OMJ said:
I'll have to test it when I get the chance...not sure why it wouldn't work, as it's stock from dump
not sure, I'll have to test this too, may need to wait for s-off
Click to expand...
Click to collapse
about the dialer. this actually happened to me the first time with the stock rom after i rooted before i tried flashing any roms.
londawg314 said:
about the dialer. this actually happened to me the first time with the stock rom after i rooted before i tried flashing any roms.
Click to expand...
Click to collapse
Good to know, add that to the list of bugs on the stock rom
Sent from my unknown using XDA Premium 4 mobile app
londawg314 said:
about the dialer. this actually happened to me the first time with the stock rom after i rooted before i tried flashing any roms.
Click to expand...
Click to collapse
Same here. I ended up having to do 3 factory resets before things stabilized.
I have the same issue too. However I did not have this issue with the stock unrooted version. I had to go back to my backup to get the phone working again.
OP updated w/ RUU & extracted firmware!!! credit to @Rydah805 thx bro!
OMJ said:
OP updated w/ RUU & extracted firmware!!! credit to @Rydah805 thx bro!
Click to expand...
Click to collapse
Rydah and I got that RUU link
question bro
how do you decrypt the RUU?
flex360 said:
Rydah and I got that RUU link
question bro
how do you decrypt the RUU?
Click to expand...
Click to collapse
http://forum.xda-developers.com/one-m9/development/dev-how-to-extract-one-m9-rom-dump-image-t3062808
Read before continue:
http://forums.yuplaygod.com/threads/15124/
http://forum.xda-developers.com/showpost.php?p=63197935
http://forum.xda-developers.com/android/software-hacking/wip-selinux-capable-superuser-t3216394
Requirements:
Completely stock, untouched device (OnePlus One).
Unlocked bootloader.
Rooted boot images:
cm-12.1-YOG7DAS2K1-bacon-boot-debuggable-rooted.img
Usage:
Download the rooted boot image that matches with your installed build.
Flash using fastboot:
Code:
fastboot flash boot XXX.img
Install the SuperUser manager app: https://play.google.com/store/apps/details?id=me.phh.superuser
Profit!
To take incremental OTA:
Download the stock boot image that matches with your installed build. Either extract from signed fastboot flashable zips or get from this thread.
Flash using fastboot:
Code:
fastboot flash boot XXX.img
You should be able to take & install the OTA, if /system isn't tampered previously.
Note:
The rooted boot images are based on official boot-debuggable images & super-bootimg by @phhusson.
The whole thing is in alpha stage & still WIP, so expect bugs.
Not all apps are compatible with systemless root approach, so root access mayn't be visible to them.
Please provide detailed feedback to me, @phhusson & the concerned app developer.
Reserved for future v1.
Reserved for future v2.
I read the second and third links, but had to sign up to get the first (not with it at this time) and I'm kinda confused. What exactly is wrong with the "old way" of rooting? Is it just for things like Android pay to work or is there other benefits?
Sent from my LG-D800 using Tapatalk
@FlashHappy78
In a nutshell, traditional rooting method modifies the /system partition. As a consequence, subsequent OTAs will fail. In case of Cyanogen OS devices, it may be easier to grab the full signed zip later & update manually, but for others they need to re-flash the stock system.img to take the OTA.
In this new approach, only the boot image is modified but /system is untouched. Thus any event/application that verifies the integrity of /system partition (like OTA, Android Pay etc.) is ready to be executed on top of the rooted device without any hitch.
If OTA contains an updated boot image, then user need to re-flash the stock boot image first which is considerably easy to re-flash than the whole system.img.
I've always been under the assumption that oem OTA updates usually break root anyways, plus patch whatever exploits were used to gain root (especially from OEM's like Samsung and LG), so because of that, I never take OTA updates unless they come from custom ROM devs.
Anyways, thanks for the clarification. I don't use android pay and I use only custom ROMs, so this probably isn't for me then. Thanks again mate.
Sent from my LG-D800 using Tapatalk
Do you have any systemless image for CM13? I tried to find a way to change the : cm-13.0-ZNH0EAS2JK-bacon-boot-debuggable.img for myself but no luck, I will have to come back to it next week.
Do you have any links to suggest?
poulopoulosa said:
Do you have any systemless image for CM13? I tried to find a way to change the : cm-13.0-ZNH0EAS2JK-bacon-boot-debuggable.img for myself but no luck, I will have to come back to it next week.
Do you have any links to suggest?
Click to expand...
Click to collapse
Flash supersu at least the stable 2.64
poulopoulosa said:
Do you have any systemless image for CM13? I tried to find a way to change the : cm-13.0-ZNH0EAS2JK-bacon-boot-debuggable.img for myself but no luck, I will have to come back to it next week.
Do you have any links to suggest?
Click to expand...
Click to collapse
As suggested by @hellcat50, I'll not provide any more update on this as newer SuperSU can patch the boot image on the fly.
TLDR: It's here and it may eat your data, and you will lose SuperSU root if currently installed. READ the install instructions carefully!
Pixel XL
Pixel
DO NOT RESTORE DATA FROM alpha builds of TWRP using RC1. You will probably lose all data including internal storage. If you need to restore a data backup from an alpha build, reinstall the alpha and restore using the alpha and make a new backup using RC1.
Note: Do not use if you have multiple users (including a guest user)
File Based Encryption (FBE) can be a bit tricky. If a restore doesn't work correctly, it can trigger an automatic wipe of your data. Sometimes TWRP will fail to prompt you to enter your password or otherwise fail to set up decrypt properly. If this happens, reboot TWRP. It seems to be some kind of timing issue and I haven't had time to track it down yet.
Pixel devices have 2 "slots" for ROMs / firmware. TWRP will detect whichever slot is currently active and use that slot for backup AND restore. There are buttons on the reboot page and under backup -> options to change slots. Changing the active slot will cause TWRP to switch which slot that TWRP is backing up or restoring. You can make a backup of slot A, switch to B, then restore the backup which will restore the backup of A to slot B. Changing the slot in TWRP also tells the bootloader to boot that slot.
The zip install method installs TWRP to both slots.
Installation:
If you already have TWRP installed: Download the latest zip and install the zip using TWRP.
If you do not already have TWRP installed: Download both the img and the zip. Copy the zip to your device. You will need to have fastboot binaries and the correct drivers installed. Power off your device completely. Hold volume down and turn on the device. Your device should now be in the bootloader. Connect the device to your PC. Open a command window and run the following command from the proper location:
fastboot boot path/to/twrp.img
This will temporarily boot TWRP on your device. If you are using a lockscreen pin/pattern/password and do not get prompted to enter your passord, reboot to the bootloader and try again. Go to install and browse to the zip and install the zip. If you are currently rooted with SuperSU, you will need to reflash the stock boot image before installing TWRP. After installing the stock boot image, follow the instructions for installing TWRP. Once TWRP is installed, grab the very latest SuperSU released on 2015-11-15 or later and install SuperSU.
If you accidently flash TWRP to your device using fastboot instead of temporarily booting the image, you will need to download the latest factory image for your device and reflash the boot image.
NOTE about 3.2.1-0: This version will decrypt Android 8.1, however the new image is built in Android 8.1 and may not be compatible with SuperSU and/or Magisk until they update their stuff. I have not tested. Good luck.
3.2.1-1 has working decrypt with the February security patch!
3.2.1-2 fixes some zip install errors
3.2.3-1 supports decrypting Android 9.0 Pie even with a pin / pattern / password set
How to install SuperSU SR5 on TWRP RC1: In TWRP tap on Advanced -> File Manager and scroll to and select the fstab.marlin or fstab.sailfish file and then delete it.
You're the man! Props for all the hard work you've put into this.
TY!!!!
Awesome. I might have to wait a bit to install but glad to see the Pixel getting twrp.
Sent from my Pixel XL using Tapatalk
Wow, and so it begins. Thanks!
Thank you!!
Nice!!! Awesome job @Dees_Troy
Sent from my Pixel XL using Tapatalk
I just installed the IMG w/out issue.
I can't find the zip in TWRP file manager to flash though.
Everything looks encrypted.
EDIT: It went through on the 4th try of flashing the IMG, now I can see my /sdcard and install the zip.
But somehow this killed my OS.
Just flashed the flash-all.bat after removing -w so it doesn't wipe.
Now I'll try TWRP install again.
EDIT 2: Okay, after restoring to stock, the TWRP install went fine.
Maybe it didn't like my elementalx kernel or the existing root. The OP did mention something about root conflicts, I guess it may prevent TWRP installs too? But now I have OS *and* TWRP.
And I'm getting "Unspecified Error" when trying to copy my EFS backup from /sdcard/twrp/backup to my local computer. I am able to copy other non-TWRP files though.
.
.
.
Does a full backup on Pixel include System Image and Vendor Image? I don't recall seeing these on other devices.
Or do I just back up boot, system and data like usual?
***Hey ya'll, don't forget to back up EFS at least once and copy it to your computers!
Yea! Worked perfect!!!
Would the flashable SuperSU v2.78 SR3 zip work?
Looked it up and because of conflicting init binaries between TWRP and the current root method, it just wouldn't work.
While we're still on or near the first page of the thread, I'd like to clarify the whole EFS backup thing.
It's completely unnecessary. You don't need to do it. But the option is there (so no one asks where it went!)
Both the modemst1 and modemst2 partitions are merely a caching area for your modem firmware. They do not contain sensitive data like IMEI, or anything important. You can wipe them and they will be regenerated from scratch! Have no fear, your IMEI cannot be destroyed through means of bad flashes!
The issue with these partitions however is that should they ever become corrupt, the modem firmware will panic and fail to load - this is why you see your IMEI missing in such a case. The modem firmware simply refused to load due to encountering corrupt data. By clearing your modemst partitions (writing zeros to them), your modem firmware would happily load and regenerate the partitions, bringing back full call support & a visible IMEI.
Okay, I have TWRP + OS working fine after restoring to stock (getting rid of kernel + root).
Now to just wait for custom ROM's to drop. Thanks guys.
The ability to restore EFS was pretty important on some older phones.
Yep just want to let ya guys know might want return to stock before doing this. Besides that all good. Good job TWRP team! :good:
CZ Eddie said:
Okay, I have TWRP + OS working fine after restoring to stock (getting rid of kernel + root).
Now to just wait for custom ROM's to drop. Thanks guys.
The ability to restore EFS was pretty important on some older phones.
Click to expand...
Click to collapse
Are you rerooting after getting TWRP to work? Have you tried a backup and restore yet?
kirschdog1 said:
Are you rerooting after getting TWRP to work? Have you tried a backup and restore yet?
Click to expand...
Click to collapse
FYI on OP - A SuperSU update will be required to allow TWRP and SuperSU to co-exist.
kirschdog1 said:
Are you rerooting after getting TWRP to work? Have you tried a backup and restore yet?
Click to expand...
Click to collapse
yes
no
I stubbornly flashed v2 root and got boot hang so I put the phone up for the night.
delete
CZ Eddie said:
yes
no
I stubbornly flashed v2 root and got boot hang so I put the phone up for the night.
Click to expand...
Click to collapse
Do we still flash root the same way after we install TWRP? Or is there an su zip to flash?
Hooray! Cheers!
About this project
This project provides repackaged Stock Oreo roms that can be flashed by TWRP. Modifications from stock are listed below.
As we are now moving into the Oreo world, I've decided that now is a good time to make a few changes to how things were done previously with Nougat. Please pay attention to the next few sections.
Modifications from stock
Note - It seems that I can't get DM-verity nor forced encryption disabled. The location of the fstab.qcom file is no longer in the Boot image. I found a similar file in the system image, but changing that appears to have had no effect. In order to disable these, use Magisk. UPDATE - Resolved since soak test 2, and soak test 1 with Aroma installer
DM-verity is disabled
Forced encryption of the data partition is disabled. It is still possible to encrypt the partition if you wish (optional with Aroma installer)
The partition table and boot loader are not included, which makes it safer to up/down-grade.
Do not attempt to apply standard OTAs over these builds. They'll probably fail, worst case they will brick your phone
Differences from previous Nougat builds
These roms are suitable for all channels. Previously there was separate firmware for different regions (e.g. retin had a separate build from retus), but as a general rule you are safe with any region's firmware.
I have now started using the Aroma installer for Oreo builds. Some of the below is now customisable at install time. Aroma installer zips will have "-aroma" in their filename.
The modified boot logo will no longer be included in the rom download. A separate zip will be provided to just flash the modified logo.
EFS will be erased on install! If your persist is intact, EFS will recreate itself. With the amount of exposure that the lost IMEI issue has had, all should be very familiar with the importance of backing up persist and EFS. And those that have had a compromised persist, will know that they should be hanging on to their EFS backups for dear life. Full details of the issue and solution (for those with intact persist) is here: Fix Persist, resolve IMEI=0, Volte, 4G, Explanation, Requirements From my perspective, the EFS is erased installing OTAs for a reason. I don't know what it is myself, but the folks at Motorola build it into their OTAs and they know far better than I do.
As a mitigation to the risk of people forgetting/losing their EFS and / or Persist backups, I will have a very crude backup system integrated into the zips. However, it will take some skill / knowledge to restore from these backups, and they should not be relied upon over the long term. Refer to the second post for more details.
Important information if downgrading to Nougat and Custom Oreo roms
The Oreo roms will change the ownership of specific files and folders in the /persist folder. As a result of this, stock Nougat will have issues such as lost IMEI, no Volte, no 4G, etc. In order to overcome these issues, either follow the instructions in the link above, or flash the following zip in TWRP.
potter-stock-persist-fix.zip
Additionally, the latest Nougat builds with the Aroma installer will apply the persist fix when installed.
Another potential issue is that, as a result of various partitions being updated, the new Oreo blobs may not be compatible with existing Nougat roms (stock or custom), or even current Custom Oreo roms. This may result in issues such as the fingerprint reader not working, etc.
UPDATE: Some custom roms are now using the Oreo blobs. However, if you require the older Nougat blobs, you can downgrade through one of the following methods:
1) install one of the latest Stock Nougat TWRP flashables. This will ensure that all affected partitions are compatible with Stock Nougat and Custom Oreo roms. You can get these from this thread here:
[Nougat][Stock][Rom] TWRP Flashable Stock Builds
2) install one of the firmware-only zips from the below folders. Note that if this results in other odd behaviour, you may need to install and boot into a full stock Nougat firmware as above. The main benefit of these zips is that they are much smaller, ~50MB rather than ~1.4GB.
https://www.androidfilehost.com/?w=files&flid=273039
potter-firmware-92-14.zip is for retin, retla, retbr
potter-firmware-93-14.zip is for retus, retapac, reteu
Out of respect for the purpose of this thread, please keep questions about whether or not to use Nougat or Oreo firmware for particular custom ROMs in the thread for the custom ROM you are trying to use. I do not support other custom ROMs - the maintainers of those custom ROMs should provide guidance.
Usage
Steps to flash
Ensure you have the latest TWRP
Download an appropriate zip from one of the links below
Copy to the phone or SD card
BACKUP YOUR DATA, INCLUDING EFS AND PERSIST
Flash the zip via TWRP
Optionally flash Magisk etc - NOTE - in order to disable dm-verity and forced encryption you must flash magisk before rebooting Resolved since Soak Test 2 and Soak Test 1 Aroma installer, Magisk is optional
Reboot
Profit?
How you can help with new builds
If your phone gets an OTA notification for a build that has not been released, please pull it and share it in this thread:
When the notification is received, allow your phone to download the OTA
Power off and boot into recovery
Go to Advanced -> File Manager
Navigate to /cache
There will be a file Blur_Version_x.y.z.potter.blah.zip - Note - Oreo OTAs may not be named this way, they may be named according to the version of the rom that is currently installed
Copy it to internal storage or the sdcard
Copy to PC (optional)
Upload to Mega, Google Drive, wherever
Share the link
You can also remove the file from the /cache folder to prevent any auto-updates from happening.
Latest versions
The 85-13 series is released to most channels except retus, and the last update was to 85-17-2.
The 85-17 series is released to the retus channel.
However, all releases can be used with all channels.
Official Oreo OPSS28.85-17-6-2 (Oreo 8.1, 1 February 2019 security patches) - Aroma Installer
Android File Host - potter-twrp-flashable-OPSS28.85-17-6-2-aroma.zip
Official Oreo OPSS28.85-17-6 (Oreo 8.1, 1 February 2019 security patches) - Aroma Installer
Android File Host - potter-twrp-flashable-OPSS28.85-17-6-aroma.zip
All versions that I have created will be placed in this folder (or the Archive sub-folder) at Android File Host:
Android File Host - Potter TWRP Flashable Stock Oreo
Modified Boot Logo
Optional, only needs to be flashed once. Replaces the warning screen with the standard logo. Can't hide the N/A. If you want to hide the N/A, go to the themes forum.
potter-logo.zip
Kernel Sources
Kernel sources are provided by Motorola:
https://github.com/MotorolaMobilityLLC/kernel-msm/
XDA:DevDB Information
Potter Oreo TWRP Flashable, ROM for the Moto G5 Plus
Contributors
NZedPred
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 3.x
Version Information
Status: Stable
Created 2018-08-17
Last Updated 2019-12-28
FAQs
Frequently Asked Questions
What is the 'very crude backup system integrated into the zips'?
This is a script that is run at the start of the install. It's purpose is very simple - it creates "dd backups" (i.e. bit-perfect images) of the modemst1/2 and persist partitions. They are stored in your sdcard as "backup_yyyymmddHHMMSS_modemst1.img", etc., where yyyymmddHHMMSS represents the date and time the script was run.
For this to work, your data partition must be mounted. I haven't included any checks for this (I'm not really a shell script person - it would take me hours to get this sort of thing right) - this is what puts the "crude" in "very crude backup system". UPDATE - the aroma installers now check that data is mounted, and abort the install if not. Most of the time the data partition will be mounted in TWRP, so this will work 99% of the time. Caution should still be applied, and you should still copy these or any other backups to cloud storage to be safe.
OK, so if I needed to use these backups, how do I restore them?
To restore these, you will have to reboot into TWRP and open up a shell or use adb. The commands to restore each partition are as follows (replacing yyyymmddHHMMSS with the appropriate values of course):
Code:
dd if=/sdcard/backup_yyyymmddHHMMSS_modemst1.img of=/dev/block/bootdevice/by-name/modemst1
dd if=/sdcard/backup_yyyymmddHHMMSS_modemst2.img of=/dev/block/bootdevice/by-name/modemst2
dd if=/sdcard/backup_yyyymmddHHMMSS_persist.img of=/dev/block/bootdevice/by-name/persist
Note that these commands are very powerful, and applied incorrectly can result in you bricking your phone if you overwrite the wrong partition.
So are dm-verity and forced encryption now not able to be disabled?
OK some history... Nougat had fstab (file system table) in the boot image. So in those days, I would open up the image, and edit the fstab.qcom file, do the appropriate changes, repack the boot image, and all is fine.
Now, under Oreo, the fstab file is not in the boot image, it's under /system/vendor/etc/fstab.qcom or similar. Editing that file appears to have no effect. For now, Magisk is the easiest way of disabling both, but you must make sure to install it immediately after installing the rom and before rebooting.
Update - this is now resolved in the second Oreo soak test download. dm-verity is still disabled in the boot image, but a completely different way. Once this is done, disabling forced encryption works as expected.
Which partitions are modified?
The short of it is this - boot, system and 'firmware'-related partitions. None of the bootloader partitions are updated. The full list of partitions that are written is:
modem
fsg
dsp
boot
system
oem
Note that this list applies to the Nougat and Oreo flashable zips.
TWRP is no longer installed after flashing this
I believe this is related to dm-verity (see above). You will have to first reinstall TWRP via fastboot. When TWRP is back, install magisk immediately after installing the rom, and before rebooting.
I'm having problems with an Oreo custom rom after installing this rom, what can I do?
Refer to the OP, the section about downgrading to Nougat - the same approach applies. Oreo Custom roms will have been based upon the available Nougat blobs that were available. As the blobs have been updated in the Oreo release, the issue is that they are not compatible. So install a full TWRP Nougat zip and then install your Oreo Custom rom.
Dirty or clean flash?
I did a dirty flash, as I came from the latest Nougat stock rom. Keep in mind that this is nothing more than the OTA applied to the previous Nougat build and packaged into a TWRP zip. So, as long as you have come from (the latest) Stock Nougat, you should be able to dirty flash, as that would be the use-case for the OTA. If you were on another rom, clean flash required.
Once you are on one of these builds, you can dirty flash subsequent builds. Again, this would be just like flashing one OTA after the other. Also note that these builds are complete in their own right, you don't need to incrementally flash - you can flash the latest to get the full install.
My device was encrypted, and I really need to decrypt it. How can I do this?
Sorry, but the only way is to format the data partition. That means you will need to backup your data, and your internal storage as well (/sdcard). After backing up, use TWRP to format the partition. From the TWRP main menu, select Wipe > Format Data. Then follow the on-screen instructions.
Is it 32 bit or 64 bit
32 bit. We've known this would be the case for a long time.
How can I create flashable zips myself?
I created the guide below, and it has been updated for Oreo. A word of warning, it is not for the faint of heart. You will need to have a good understanding of the Linux command line, and be able to understand the techniques that are being taught, rather than expecting that the process is a 'step-by-step'. Adaptability is key here.
[GUIDE] Creating TWRP Flashbale Stock roms
What are the new Aroma zips?
The aroma zips use the Aroma installer. Some of you may have seen the Aroma installer for Open Gapps. The key here is that I, as the packager, can build in selection options into the installer. It's all available as a nice GUI for the users to pick and choose from the options I've provided. Here are the options that are available:
Do backups - does the backups as mentioned earlier in the FAQs.
Erase EFS - erases modemst1 and modemst2, as described in the first post. Also DDR is erased, but I'm not sure what purpose that has but it may as well go together with these.
Install Firmware - installs the following partitions - modem, fsg, dsp; each of these has something to do with hardware / connectivity.
Install System - Installs the following partitions - boot, system, oem.
Apply patches - as long as Install System is selected, will install the patched boot image with dm-verity disabled, and will edit the fstab (filesystem table) to disable forced encryption.
On soak test 2 or later, I have my IMEI but no signal. What can I do?
In all cases where this has happened, the user's phone has relied upon an EFS backup for IMEI, due to flashing another persist. In these cases, it appears that the only way to get a signal is to use the firmware (i.e. modem, fsg, dsp - refer previous FAQ) from soak test 1. We're probably seeing here that the EFS does in fact need to be recreated to be valid. Unfortunately for these users, by not having their own persist, they are stuck with an old EFS and the newer firmwares appear to not work.
To do this
if you are already on Soak Test 2 or later, download the Soak Test 1 firmware download at either of these links:
Android File Host - oreo-soak1-firmware.zip
Dropbox - oreo-soak1-firmware.zip
If you are on Soak Test 1, install Soak Test 2 or later / official aroma installer and de-select firmware
My fingerprint is not working on my custom ROM
Refer to the thread for your custom ROM, and ask questions there. In short, Nougat and Oreo firmware are not compatible with each other. Many custom ROMs are now using Oreo firmware, whereas previously (before October 2018) pretty much all custom ROMs were using Nougat firmware. It's messy now, but please ask the questions in the right place (which is NOT this thread).
My touchscreen isn't working after flashing, even within TWRP
This seems to happen somewhat rarely, although I don't know what the cause is. As it affects TWRP as well, and TWRP uses the 'modem' partition for getting its firmware blobs, I guess it's possible that this particular partition is getting a conflicting modification whilst flashing, which is causing problems (but this is purely speculation on my part).
To solve, fastboot flashing the stock ROM appears to work. It may also be possible whilst in TWRP to manually flash the partitions via ADB, but that takes a bit of work and knowledge. Until someone can truly work out what's happening and the minimum required to fix it, stick with fastboot.
Update - refer to post #3 for the latest information about this issue.
Touch screen unresponsive even in TWRP
The below post has the latest information on the Touch Screen Unresponsive issue
Likely Cause
From the testing that I've done to reproduce the issue, as far as I can tell the issue is that Stock Oreo is not able to be safely applied over the top of old builds of Stock Nougat. Furthermore, it doesn't seem to matter if you were on Custom ROMs after you were last on Stock Nougat, just what Stock Nougat build you were on last.
Avoiding the Issue
Again the key here is what build of Stock you were on last (and I guess booted into). So, if you were never on Stock Oreo, and you aren't sure what version of Stock Nougat you were on last, then the safest path to getting these builds working is to first flash the latest Nougat Stock ROM.
Get the latest from this thread: [Nougat][Stock][Rom] TWRP Flashable Stock Builds
Once you have flashed the latest Nougat, boot once to make sure everything is working. After that, you should be able to safely upgrade to Oreo.
Fixing the Issue
If you have been affected by the issue, most people have been able to get back the touch screen functionality by flashing a fastboot version of the ROM. However, as long as you have a PC handy you will be able to flash using TWRP as well via adb, using the steps detailed below. A third option is to connect a USB Mouse via an USB OTG adapter.
Note that for either method via TWRP, you cannot use the versions of the ROM with the Aroma installer, as the mouse is not supported within, and there is no way of providing input by adb.
Downloads
The 92-14 or 93-14 versions should be suitable. They are in these links (these do not erase EFS, so for the paranoid, you will retain your IMEI):
twrp-flashable-potter-NPNS25.137-92-14-no-erase-modemst.zip
twrp-flashable-potter-NPNS25.137-93-14-no-erase-modemst.zip
TWRP Commands
Once in TWRP, connect your USB cable. To copy the downloaded file into your internal storage (adapt the filename for the version you downloaded):
Code:
adb push twrp-flashable-potter-NPNS25.137-92-14-no-erase-modemst.zip /sdcard/
If you want to backup, you can do this via the command line as well. I haven't tested this myself, but the commands are available here: https://www.pocketables.com/2014/10/using-twrps-new-adb-interface.html
The example provided uses the following to back up system, data and boot, and compress:
Code:
adb shell twrp backup SDBOM
You will need to do a clean flash, so these commands will wipe data / factory reset and then install
Code:
adb shell
twrp wipe data
twrp install /sdcard/twrp-flashable-potter-NPNS25.137-92-14-no-erase-modemst.zip
reboot
After the reboot, you should have your touch screen functionality back. Then reboot to recovery, and install Oreo as normal. If for any reason the Oreo flash doesn't work, try the steps again, but rather than installing the latest Oreo, install an earlier one.
Awesome bro...
You Rock...
you even included auto backup of efs and persist ... wow thats very thoughtfull and nice of you...
hatsoff..
:good::good:
Thanks dude, downloading
Edit: working like a charm, again thanks.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Thanks for uploading. Two questions though...
1. which one would be suitable for retin? (India)
2. Are there any bugs?
working for retin also thnx
Question: I'd like to flash this, but I'm planning to roll back in the future to take the OTA back up to O. If I restore nougat system, boot, persist, recovery, oem will that still be possible? I see some other stuff in the zip like adspo.bin, fsg.mbn, and modem. Not sure if those it lead to OTA failures or a brick.
also, nice job on the persist/efs script!
Worked on retin also thanks. Great work!!!!
I'm pretty sure forced encryption of the data partition is still enabled.
pfonck said:
I think forced encryption of the data partition is still enabled (formatting the data partition in TWRP does not help).
Click to expand...
Click to collapse
If that's the case magisk is probably needed to turn it off. Sorry, but I've only tested it with magisk installed. Moto have changed the fstab location, I thought I got it but maybe it's cosmetic and doesn't do anything. Will update OP when I get a chance.
NZedPred said:
If that's the case magisk is probably needed to turn it off. Sorry, but I've only tested it with magisk installed. Moto have changed the fstab location, I thought I got it but maybe it's cosmetic and doesn't do anything. Will update OP when I get a chance.
Click to expand...
Click to collapse
Yes, when you do;
rom installation > format data > flash magisk
everything is okay
verified.
Did Moto make Oreo 64bit?
redbeard1083 said:
Question: I'd like to flash this, but I'm planning to roll back in the future to take the OTA back up to O. If I restore nougat system, boot, persist, recovery, oem will that still be possible? I see some other stuff in the zip like adspo.bin, fsg.mbn, and modem. Not sure if those it lead to OTA failures or a brick.
also, nice job on the persist/efs script!
Click to expand...
Click to collapse
Good question, and this is something that I needed to consider before doing this, in case everyone installed this and we'd have no path to get to official Oreo.
Refer to the section in the OP "Important information if downgrading to Nougat". Basically you need to follow all of that to be able to get notification of the OTAs. Once the official public Oreo OTA is available, I will then put together a zip based upon the pre-requisite nougat rom with the official Oreo OTA.
I also believe that one or both of the 1 July 2018 and/or 1 August 2018 patches were announced, but neither were for Oreo. I do intend to keep Nougat up to date as well in its thread.
NZedPred said:
Good question, and this is something that I needed to consider before doing this, in case everyone installed this and we'd have no path to get to official Oreo.
Refer to the section in the OP "Important information if downgrading to Nougat". Basically you need to follow all of that to be able to get notification of the OTAs. Once the official public Oreo OTA is available, I will then put together a zip based upon the pre-requisite nougat rom with the official Oreo OTA.
I also believe that one or both of the 1 July 2018 and/or 1 August 2018 patches were announced, but neither were for Oreo. I do intend to keep Nougat up to date as well in its thread.
Click to expand...
Click to collapse
How did a recovery come in? with volume - and power enters and I say without command
JC Pzy said:
How did a recovery come in? with volume - and power enters and I say without command
Click to expand...
Click to collapse
I've only just added something to the FAQ (post 2) that covers this. Sorry, it was unexpected and didn't come up when I was testing as I always had magisk installed. Follow these steps:
TWRP is no longer installed after flashing this
I believe this is related to dm-verity (see above). You will have to first reinstall TWRP via fastboot. When TWRP is back, install magisk immediately after installing the rom, and before rebooting.
NZedPred said:
I've only just added something to the FAQ (post 2) that covers this. Sorry, it was unexpected and didn't come up when I was testing as I always had magisk installed. Follow these steps:
TWRP is no longer installed after flashing this
I believe this is related to dm-verity (see above). You will have to first reinstall TWRP via fastboot. When TWRP is back, install magisk immediately after installing the rom, and before rebooting.
Click to expand...
Click to collapse
I do not have a PC to reinstall the recovery
NZedPred said:
Good question, and this is something that I needed to consider before doing this, in case everyone installed this and we'd have no path to get to official Oreo.
Refer to the section in the OP "Important information if downgrading to Nougat". Basically you need to follow all of that to be able to get notification of the OTAs. Once the official public Oreo OTA is available, I will then put together a zip based upon the pre-requisite nougat rom with the official Oreo OTA.
I also believe that one or both of the 1 July 2018 and/or 1 August 2018 patches were announced, but neither were for Oreo. I do intend to keep Nougat up to date as well in its thread.
Click to expand...
Click to collapse
Maybe I'll try tweaking the zip to see if we can run it without the stuff we can't easily backup/restore with twrp. I'll take a stab at it shortly and let you know what happens if we flash just system, boot, and OEM.
redbeard1083 said:
Maybe I'll try tweaking the zip to see if we can run it without the stuff we can't easily backup/restore with twrp. I'll take a stab at it shortly and let you know what happens if we flash just system, boot, and OEM.
Click to expand...
Click to collapse
You can give it a go, but I've already done some very brief testing. Using the Nougat modem partition on the Oreo system results in things like 3G only, fingerprint not working.
JC Pzy said:
I do not have a PC to reinstall the recovery
Click to expand...
Click to collapse
I'm guessing you don't have root either? If you did, you could try installing it from a shell from within the rom:
Code:
su
dd if=/path/to/twrp.img of=/dev/block/bootdevice/by-name/recovery
First question is the title basically, wanna flash miui if i happen to not like PE. Can i flash it with twrp?
Second question, If I flash PE without any custom kernels. And flash miui after that. Will i have my original kernel? Or does flashing custom roms change to a custom kernel?
Sorry a bit new to this. Thanks for your time.
1 - Yes, you can flash miui with twrp, just use rom recovery package.
2 - Any rom zip package comes bundled with the kernel. flashing will install the kernel contained in the package.
csleo17 said:
1 - Yes, you can flash miui with twrp, just use rom recovery package.
2 - Any rom zip package comes bundled with the kernel. flashing will install the kernel contained in the package.
Click to expand...
Click to collapse
What is rom recovery package?
thanks for your time man
ParsaMrrelax said:
What is rom recovery package?
thanks for your time man
Click to expand...
Click to collapse
Android devices predominantly followed by following partitions!
/system
/boot
/recovery
/vendor
/storage
/persist
/ta (in xperia)
/overlay (optional)
now RECOVERY (beside parition name) refers to a operating system DESIGNED ONLY to change size of these partitions (ADVANCE) and basic need to spread out(FLASH) operating system according to command by package in certain partitions. -- TWRP is one OUTSTANDING Recovery project over the years. back in old days Philztouch recovery was also popular for Xperia models-
the term "rom recovery package" means, READ ONLY MEMORY ( a android operating system File ) Designed for RECOVERY TO READ and spead the data in /system + / boot & /data partitions for your Poco (or any android based) for boot in to android operating system.
MIUI mainly releases TWO filetypes of SAME ROMS , for example miui10.3.6 has
1. RECOVERY ROM (1.6gb) (to be flashed by TWRP
2. FASTBOOT ROM (2.8gb) which can be flashed by FLASHER running on WINDOWS based System (some times iMac too)
3. Android devices uses many types of processor, SNAPDRAGON processors are famouss (poco uses Snapdragon or SD845) hence Two type of Flashers can be USED to FLASH POCO, 1 MI FLASH (RECOMENDED) (supports Two Mods, on fastboot rom, fastboot & EDL) or QUALCOMS QLOADER flasher (ADVANCE and NOT RECOMENDED)
coming back to twrp,
all custom roms are designed keeping in mind that RECOVERY (such as TWRP) will be FLASHING it on ANDROID DEVICE. so the sequence of flashing such roms are like
1. flashing vendor firmware , from a. vendor firmware , download from https://mirror.akhilnarang.me/MIUI/b...r-firmware.zip
b. flashing pixel experience ROM ( you should also try Crdroid and Havoc)
c. flashing google apps from openapps.org (take arm64>android9.0>MICRO package and hit download) 250+mb filesize
d. (optional) optimus drunk kernel (check development forum for post)
e. flashing magisk18.3.zip (if you want your Device to WAKEUP ROOTED)
now answering you question
1. YES YOU CAN TOGGLE BETWEEN MIUI AND CUSTOM ROMS, but don't make it habit! there is always chance for you to BRICK your device. also you will loose all your data if MIUI uses Encryption method which TWRP cannot READ to operate /data partition. then you must RE FORMATE /data partition via twrp in order to make it accesable for custom rom(s)
2.ANY TIME WHEN TWRP FLASH ANY ROM, MIUI OR ANY CUSTOM ROM, THE OLD KERNEL IS OBSOLETE AND NEW ONE IS PLACED thats why you need to flash magisk everytime you clean flash any rom in order to get root access
please do ask if you need any clarification
might be a old thread.
but i installed a custom rom on my moms phone but i thinking going back to stock. the custom rom is old and has scroll problems...
but i see stable miui has no updates. but can i flash official miui rom from twrp over the custom lingeos rom?
or is it better to update her phone to a more recent custom rom.
either way she will lose her data. plus camera has bugs but i never had the time with work and she working to put it back in a mint working state. cause the scrolling being broking is fuking stupid
tought about miui stable. just to flash it true trwp.
or update it to a more recent custom rom.