{
"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"
}
BlissRoms comes with a wide selection of customization options from around the Android community as well as unique options developed by our team. With so many options available, you’ll find it hard not to enjoy the Blissful experience.
Our focus is to bring the Open Source community a quality OS that can run on all your devices as a daily driver, syncing your apps + settings + customization's across all platforms you run Bliss on.
BlissRoms Download
Code:
-Make sure you are on the latest OOS 11
- Dump the BlissROM zipfile through payload_dumper
- flash the partition images with the following commands
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash odm odm.img
fastboot flash system system.img
fastboot flash vbmeta vbmeta.img
fastboot flash vendor vendor.img
- Reboot and #StayBlissful
Create Bug Report on our Issues Tracker
BlissRoms Github
BlissRoms Gerrit
Kernel Source
| Website | Blog | Facebook | Twitter | Instagram | Telegram Group | Telegram Channel | Docs
If someone wants to donate, please do so via this PayPal link
Thank you for using BlissRoms! And as always: #StayBlissful
reserve
reserve too
How do i dump the BlissROM zipfile through payload_dumper?
This new way of flashing roms has caught me off guard.
What is a payload dumper anyway?
mrdreamers4u said:
How do i dump the BlissROM zipfile through payload_dumper?
This new way of flashing roms has caught me off guard.
What is a payload dumper anyway?
Click to expand...
Click to collapse
The following link will explain what it is and how to extract it.
Extract Android OTA Payload.bin File using Payload Dumper Tool
Learn how to dump and extract Android OTA Payload.bin file to get the boot.img (for rooting with Magisk), vendor.img, and other other partition images.
www.thecustomdroid.com
Also you can flash with twrp if you use a flash drive to host the file since decryption no longer works.
srgrusso said:
The following link will explain what it is and how to extract it.
Extract Android OTA Payload.bin File using Payload Dumper Tool
Learn how to dump and extract Android OTA Payload.bin file to get the boot.img (for rooting with Magisk), vendor.img, and other other partition images.
www.thecustomdroid.com
Also you can flash with twrp if you use a flash drive to host the file since decryption no longer works.
Click to expand...
Click to collapse
So I want to grab the payload.bin from the blissrom zip and "dump" that through payload dumper?
mrdreamers4u said:
So I want to grab the payload.bin from the blissrom zip and "dump" that through payload dumper?
Click to expand...
Click to collapse
Yes
srgrusso said:
Yes
Click to expand...
Click to collapse
I did it but the only file it did not dump was the odm.img from the installation list. did i do something wrong?
mrdreamers4u said:
I did it but the only file it did not dump was the odm.img from the installation list. did i do something wrong?
Click to expand...
Click to collapse
You should be ok. Those are generic instructions. I will update the instructions.
Code:
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash system system.img
fastboot flash vbmeta vbmeta.img
fastboot flash vendor vendor.img
srgrusso said:
You should be ok. Those are generic instructions. I will update the instructions.
Click to expand...
Click to collapse
So pretend the odm.img is not in the installation list and do it in the order you still have it in?
mrdreamers4u said:
So pretend the odm.img is not in the installation list and do it in the order you still have it in?
Click to expand...
Click to collapse
Yes
srgrusso said:
Yes
Click to expand...
Click to collapse
Great thanks I'm going to try right now.
BTW if i screw up somehow can i still use my twrp backup to restore back to where i was?
mrdreamers4u said:
Great thanks I'm going to try right now.
BTW if i screw up somehow can i still use my twrp backup to restore back to where i was?
Click to expand...
Click to collapse
You still need to format data when switch android versions. If it doesn't work you can flash the rom with twrp but you need to use otg for the file.
srgrusso said:
You still need to format data when switch android versions. If it doesn't work you can flash the rom with twrp but you need to use otg for the file.
Click to expand...
Click to collapse
Can i flash this rom like this guy does in this video? (i wish i could just flash it in twrp the normal way LOL)
(starts at 5:17 in the video)
Sorry I'm new to this method i appreciate you patience with me.
mrdreamers4u said:
Can i flash this rom like this guy does in this video? (i wish i could just flash it in twrp the normal way LOL)
(starts at 5:17 in the video)
Sorry I'm new to this method i appreciate you patience with me.
Click to expand...
Click to collapse
You can try it. Basically the problem with twrp is decryption doesn't work with A13. The way I get around this is that I put the rom file on a flash drive and flash from the usb port. If you don't have a flash drive you can try formating data and put the rom file on the phone and flash. In the video they just disable encryption which may not matter to you.
srgrusso said:
You can try it. Basically the problem with twrp is decryption doesn't work with A13. The way I get around this is that I put the rom file on a flash drive and flash from the usb port. If you don't have a flash drive you can try formating data and put the rom file on the phone and flash. In the video they just disable encryption which may not matter to you.
Click to expand...
Click to collapse
You mean a flash drive dongle like in this pic?
and just flash in twrp almost like normal but with full wipe first?
im just confused because the instructions say fastboot flash img which make me think to use fastboot on pc like in the video.
mrdreamers4u said:
You mean a flash drive dongle like in this pic?
and just flash in twrp almost like normal but with full wipe first?
im just confused because the instructions say fastboot flash img which make me think to use fastboot on pc like in the video.
Click to expand...
Click to collapse
Yes, like normal. This is the way I flash roms for the fajita and guacamole.
srgrusso said:
Yes, like normal. This is the way I flash roms for the fajita and guacamole.
Click to expand...
Click to collapse
Ok now were cooking LOL!!
So do i take these individual img files i dumped from the rom and flash those in twrp each after a full wipe then reboot or do i just full wipe in twrp and flash the blissrom zip then reboot?
mrdreamers4u said:
Ok now were cooking LOL!!
So do i take these individual img files i dumped from the rom and flash those in twrp each after a full wipe then reboot or do i just full wipe in twrp and flash the blissrom zip then reboot?
Click to expand...
Click to collapse
Just flash the Blissrom zip like before. Everything is the same as before except the location of the rom zip.
Right on Thanks!!
Related
Thanks to agentdr8! He made a Linux version for you guys! Download link below!
Like every developer says:
I AM NOT HELD RESPONSIBLE FOR ANYTHING THAT HAPPENS TO YOUR DEVICE!
Click to expand...
Click to collapse
What is FFW?
FFW is a script written in batch that will automatically wipe your phone, leaving no traces of the past install.
Click to expand...
Click to collapse
What does it do?
I'll pretty much sum it up like this, it erases the boot, system, userdata, cache, webtop, preinstall, and reboots the phone.
Click to expand...
Click to collapse
Notice:
There are two versions, Fastboot & Moto-Fastboot, I don't know the difference but I made a script for each version. The whole package is there, just download, extract, and run the batch file!
Click to expand...
Click to collapse
Instructions:
1. Download any of the two versions.
2. Boot into recovery.
3. Wipe the Dalvik cache.
4. Wipe the cache.
5. Factory reset/data your phone.
6. Boot into fastboot.
7. Run the script.
8. Your done!
You can now install any ROM you choose! Be carefull for hard/soft bricks, installing the wrong ROM can ruin your phone!
Click to expand...
Click to collapse
Screenshots:
Fastboot Full Wipe
{
"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"
}
Moto-Fastboot Full Wipe
Download:
Multiupload is now useless! Download everything from Mediafire!
Newest!
FFW Linux: 3.2
New-
FB Full Wipe: 2.1
MFB Full Wipe: 2.0
Older-
FB Full Wipe: 1.1
MFB Full Wipe: 1.0
Click to expand...
Click to collapse
Mini key
x.0 Moto-Fastboot (Windows)
x.1 Fastboot (Windows)
x.2 Fastboot (Linux)
Click to expand...
Click to collapse
Who helped make it?
Alaq - Me - The script.
CaelanT -This.
agentdr8 - The Linux version of the script!
Click to expand...
Click to collapse
Build 2.0/2.1:
Code:
-Fixed devices check
--Now there is a pause to allow you to see if your phone is connected correctly or not
Build 1.0/1.1:
Code:
-Full Wipe text logo added
-Echo used to give info
-Pause used to give user a last minute choice to wipe or not
-Pause used to give user a choice to reboot phone or not
-Formats:
--boot
--system
--userdata
--cache
--webtop
--preinstall
Thread Edits/Revisions:
12/31/11- OP Created
12/31/11- Pictures added
Script Edits/Revisions:
12/29/11- Fastboot Full Wipe Created
12/30/11- Moto-Fastboot Full Wipe Created
Alaq said:
What is FFW?
What does it do?
Notice:
Instructions:
Screenshots:
Fastboot Full Wipe
Moto-Fastboot Full Wipe
Download:
Who helped make it?
Click to expand...
Click to collapse
Thanks for the script.
Sent from my MB860 using Tapatalk
Alaq said:
There are two versions, Fastboot & Moto-Fastboot, I don't know the difference but I made a script for each version. The whole package is there, just download, extract, and run the batch file!
Click to expand...
Click to collapse
Moto-Fastboot is just like Fastboot except that it can handle larger flash image files, such as the webtop image (which is too big for Fastboot to handle).
MJPollard said:
Moto-Fastboot is just like Fastboot except that it can handle larger flash image files, such as the webtop image (which is too big for Fastboot to handle).
Click to expand...
Click to collapse
Alright, thanks for the info. I guess Moto-Fastboot is better, but I'll keep both versions up for the people that want them...
Thanks! Great script.
Why not rebooting into the recovery at the finish ? (you want to flash roms at the end ..)
Thank you ! looks great !
PakaPakaxz said:
Why not rebooting into the recovery at the finish ? (you want to flash roms at the end ..)
Thank you ! looks great !
Click to expand...
Click to collapse
You know I thought of that... But in all of my searching I haven't found any command that would do it... I tried "moto-fastboot reboot recovery"... Thanks for the idea though, I'll figure it out eventually!
I think you'd have to use the following arguments:
boot your_recovery.img
I can't remember exactly, but i think that's it.
itsonlym3 said:
I think you'd have to use the following arguments:
boot your_recovery.img
I can't remember exactly, but i think that's it.
Click to expand...
Click to collapse
That would be kinda hard since this doesn't flash a recovery...
Alaq said:
That would be kinda hard since this doesn't flash a recovery...
Click to expand...
Click to collapse
i tried it with one i had, it doesn't reboot. i thought it would, my bad.
It's alright, thanks for trying though!
Build 2 now out! Not much upgraded, just added a confirmation screen so you can make sure your phone is connected properly.
Alaq said:
Build 2 now out! Not much upgraded, just added a confirmation screen so you can make sure your phone is connected properly.
Click to expand...
Click to collapse
dropbox barfing saying too much traffic
dicksteele said:
dropbox barfing saying too much traffic
Click to expand...
Click to collapse
Uploaded to Multiupload! Go check the OP for new download links.
Posting so I can use this later and refer people to this as well.
Excellent!!!
Thanks.
Perfect !!
Sent from my MB860 using xda premium
Alaq, hope you don't mind but I modded your script for linux users. See attached.
Linux fastboot binary included as well.
agentdr8 said:
Alaq, hope you don't mind but I modded your script for linux users. See attached.
Linux fastboot binary included as well.
Click to expand...
Click to collapse
Nice! I'll add it to the op!
{
"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"
}
THIS IS A PROXY THREAD Creator and Maintainer is pershoot
This is CWM for the ASUS Transformer Pad (TF701T – Macallan).
-You must be unlocked (use ASUS’s unlock tool to perform this)
-You must be on 10.26.1.18 bootloader (updating to ASUS’s latest 4.3 release will install this)
For complete Info and Download: VISIT HERE
***Once there, check out the Recent Entries on the right side of the page for latest updates***
-Unlock your device using the ASUS Unlock tool.
-Boot in once and execute: adb reboot bootloader
Fastboot:
To boot the recovery:
fastboot boot recovery.img
To permanently flash the recovery:
fastboot flash recovery recovery.img
Source:
https://github.com/pershoot/android_device_asus_tf701t
https://github.com/pershoot/android_kernel_asus_tf701t
https://github.com/CyanogenMod/android_bootable_recovery
Creator and Maintainer:
@pershoot
Video Tutorial
Video Tutorial Thanks @wwjoshdew
Ah just saw screenies. Nice job pershoot.
Why is the version still 6.0.4.6?
CWM 6.0.4.7
OP Updated
Feb/2 OP updated
Small question: my device is on 10.26.1.17. Updating to the latest official 4.3 will definitely wipe the CWM recovery, and probably will make some of the apps not running any more (not mentioning loosing root, etc..)
Is it possible to install the CWM on such a ROM version (10.26.1.17) ? I've just tested booting it and booting (and using it as a backup) works.
I was on 6.0.4.6 and i used flashify to update. Worked fine.
hetzbh said:
Small question: my device is on 10.26.1.17. Updating to the latest official 4.3 will definitely wipe the CWM recovery, and probably will make some of the apps not running any more (not mentioning loosing root, etc..)
Is it possible to install the CWM on such a ROM version (10.26.1.17) ? I've just tested booting it and booting (and using it as a backup) works.
Click to expand...
Click to collapse
Both cromix and cm11 will require the latest bootloader to eliminate compatibility issues it is recommended to flash to the latest asus firmware
Sent from my SGH-T889 using XDA Premium 4 mobile app
@AngryDinosaur - I made a video on how to install Custom Recovery on your Transformer Pad TF701T!
http://www.youtube.com/watch?v=3IBN1YkBp3g
wwjoshdew said:
@AngryDinosaur - I made a video on how to install Custom Recovery on your Transformer Pad TF701T!
http://www.youtube.com/watch?v=3IBN1YkBp3g
Click to expand...
Click to collapse
included in the post alongside the screenshots. Thanks a lot!!!
OP updated 2/16, installation video tutorial included. Thanks to @wwjoshdew
recovery updated with baseline build and sorted dock sd card functionality and usbdisk functionality.
@pershoot I'd love for this recovery to include touch screen drivers. That way at least aroma could use the touch screen. Any ideas how to compile with the standard drivers included?
sbdags said:
@pershoot I'd love for this recovery to include touch screen drivers. That way at least aroma could use the touch screen. Any ideas how to compile with the standard drivers included?
Click to expand...
Click to collapse
i'll look in to it...
I'm getting a weird error I've never seen before trying to flash something with fastboot. :
fastboot flash recovery recovery.img
target reported max download size of 643825664 bytes
error: cannot load 'recovery.img' : No error
Any ideas?
lortay78 said:
I'm getting a weird error I've never seen before trying to flash something with fastboot. :
fastboot flash recovery recovery.img
target reported max download size of 643825664 bytes
error: cannot load 'recovery.img' : No error
Any ideas?
Click to expand...
Click to collapse
Make sure recovery.img is in the same folder as fastboot and you are running the cmd prompt from that folder.
sbdags said:
Make sure recovery.img is in the same folder as fastboot and you are running the cmd prompt from that folder.
Click to expand...
Click to collapse
Duh, I have platform-tools in my path so I can run them from anywhere. I forgot to cd to the directory. Thanks for airing out my brain fart.
lortay78 said:
Duh, I have platform-tools in my path so I can run them from anywhere. I forgot to cd to the directory. Thanks for airing out my brain fart.
Click to expand...
Click to collapse
Very common mistake that happens to the best of us
updated.
Hi,
I spent hours trying to get this to work before discovering there are two missing steps in the OP's instructions.
There's a shell script that calls an application that restores the stock boot loader on every boot.
You have to delete it.
Steps:
1. Root.
2. Install Root Explorer.
3. Go into /etc
4. Delete install_recovery.sh
5. Go into /system
6. Delete recovery-from-boot.p
You have to delete the files. You can't just rename them or change the extension because the system actually searches the filesystem for a file whose contents matches an MD5 hash and will find it if you rename it.
After you do this, THEN follow OP's instructions.
P7 - Easy Update and Adjust
Hello friends
I have built a tool for our phone.
Included are the following options:
::. [1] - Stock Firmware-Update with TWRP
::. [2] - Flash Recovery.img
::. [3] - Flash boot.img
::. [4] - Delete set_immutable.list / Full root
::. [5] - Start Recovery
::. [6] - Start Fastboot
::. [7] - Reboot Phone (in fastboot and ADB)
This tool simplifies working with adb / fastboot and flash the firmware, a recovery.img or Boot.img
Changelog:
Code:
22/12/2015 V1.3:
* Version without recovery.img
* Deleted automatic restart after flashing recovery or boot .img
17/05/2015 V1.3:
* New menu Item: Flash boot.img
* Translation "improved"
23/11/2014 V1.2:
* Now Supported P7-L00, L05, L07, L09, L10 (included recovery is for L10! - i dont know if L00... Use the same).
16/10/2014 V1.1:
* Fully translated to English
* stockrecovery.img included
* At the start of the program is checked whether this is in the correct directory
Downloads:
Code:
22/12/2015: [ATTACH]3585481._xfImport[/ATTACH]
17/05/2015: [ATTACH]3317262._xfImport[/ATTACH]
23/11/2014: [ATTACH]3035237._xfImport[/ATTACH]
16/10/2014: [ATTACH]3018266._xfImport[/ATTACH]
15/10/2014: [ATTACH]3016196._xfImport[/ATTACH]
Instructions:
Code:
1. Insert P7-Easy_Update_and_Adjust.exe into your ADB Folder.
2. If you want to flash a special recovery put the .img File into the "recovery" Folder.
3. If you want to flash a special boot.img put the .img File into the "boot" Folder.
4. Now you can start...
On start of this tool a recovery folder will be created with stockrecovery.img in it.
This is the folder who you can put in all your recoverys. If you will be flash a recovery you see a menu of all and can choose yours.
For "[4] - Delete set_immutable.list / Full root" - You need Busybox on your Phone! Download and install it from Playstore.
Descriptions:
Code:
ADB Mode: Phone is complete booted up and USB debugging is enabled.
On your phone MTP or HiSuite mode must be enabled - Non mass storage.
Recovery Mode: Phone is in recovery e.g. TWRP.
Fastboot Mode: Phone is in bootloader.
Screenshots:
{
"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"
}
If someone needs help, says me know in this thread.
Use @ your own risk!
regards,
87Insane
87insane said:
Hello friends
I have built a tool for our phone.
Click to expand...
Click to collapse
Looks good!
I can help with translations if you want.
GawDroid said:
Looks good!
I can help with translations if you want.
Click to expand...
Click to collapse
Hi,
english is no problem...only my time is the problem.
But tomorrow, i think its ready. THX for your help with ADB shell.
Sent from my HUAWEI P7-L10 using XDA Free mobile app
Hi,
does it mean that by using your tool I will be able to flash a new factory ROM (dload\Update.app format), even if I had put a TWRP recovery to my P7?
Without changing back the TWRP to stock recovery?
ctibor said:
Hi,
does it mean that by using your tool I will be able to flash a new factory ROM (dload\Update.app format), even if I had put a TWRP recovery to my P7?
Without changing back the TWRP to stock recovery?
Click to expand...
Click to collapse
Yes...no...
This tool makes what you make manuelly. Go back to stock, flash, and back to twrp. With backup and delete immutable after update.
Instructions are in this tool...you can easy try this...i hade to do this manuel.
Sent from my HUAWEI P7-L10 using XDA Free mobile app
ctibor said:
Hi,
does it mean that by using your tool I will be able to flash a new factory ROM (dload\Update.app format), even if I had put a TWRP recovery to my P7?
Without changing back the TWRP to stock recovery?
Click to expand...
Click to collapse
Are you checked that and be happy? I would like to create a tool that can use anybody and need ideas from you and other users
what about this:
Recovery_P7_all.exe v 1.4
http://4pda.ru/forum/index.php?showtopic=573880&st=2240#entry35842662
habbaz said:
what about this:
Recovery_P7_all.exe v 1.4
http://4pda.ru/forum/index.php?showtopic=573880&st=2240#entry35842662
Click to expand...
Click to collapse
the tool I do not know. do you have experience with it? unfortunately I can not speak Russian.
87insane said:
the tool I do not know. do you have experience with it? unfortunately I can not speak Russian.
Click to expand...
Click to collapse
no, i don't know Russian language.
but you can use the Google translator.
habbaz said:
no, i don't know Russian language.
but you can use the Google translator.
Click to expand...
Click to collapse
Yes i do this but i cant open a exe file in my Android. Its a Russian exe file...iam safety ^^
Hi, did someone tested the tool? ( the first one) does it work? Because I want to install TWRP and I don't want to risk ?
If your bootloader is open, no Problem.
Put the twrp recovery .img in the recovery folder and choose flash recovery.
Only ADB and fastboot commands. If you have trouble - Plesse give me a info.
Does this program works alone? Do I need android SDK? Thank you for support!
luca3011 said:
Does this program works alone? Do I need android SDK? Thank you for support!
Click to expand...
Click to collapse
On my first post you can see it.
Instructions:
1. Insert P7-Easy_Update_and_Adjust.exe into your ADB Folder.
2. If you want to flash a special recovery put the .img File into the "recovery" Folder.
3. Now you can start...
This tool needs ADB and fastboot.
Thank you so much!
to me it does not work
I always have, only this
I want this
palokm said:
to me it does not work
I always have, only this
I want this
Click to expand...
Click to collapse
What do you want to do? If you want the second your phone has to be in ADB mode.
You are in fastboot mode ...
ADB mode = phone complete bootet with USB debugging activated.
I can not get into the ADB
palokm said:
I can not get into the ADB
Click to expand...
Click to collapse
Can you explain me what are you doing?
Wich phone do you have - L10 or another?
I'd like you to explain
but I do not know English
I use a translator
I have a L10
Do instructions
Root by Magisk
Click Here For MR0
Click Here For MR1
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot reboot
If you get this error
Your device is corrupt. It can’t be trusted and may not work properly.
Use a terminal app or use computer and type this.
su
reboot "dm-verity enforcing"
MR0 rooted to MR1 failed to install workaround
If you're already on rooted MR0 and OTA installation failed for the MR1 Update.
You must boot into fastboot mode and flash MR0 stock boot.img , vendor.img , system.img then check for update follow instructions below.
https://s3.amazonaws.com/cheryl-factory-images/aura-p-global-3040.zip
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot flash vendor_a vendor.img
fastboot flash vendor_b vendor.img
fastboot flash system_a system.img
fastboot flash system_b system.img
fastboot reboot
Fixed link
I managed to capture the OTA... All I got was payload.bin. How do extract my own boot.img so I can patch it?
I googled how to extract bin files. Install python on your PC. There's a package that will unpack the payload.bin file.
Thanks for this! Was stuck at work when I pulled the OTA and couldn't do it myself. Saved me a few steps
This saves us time. Razer won't put the image on the developer portal for another week
The problem I have is it now says my device is corrupt even after side loading the whole OTA file. Still got the error right after the side loading.
Guys, the payload.bin doesn't contain the full images. It contains bdiff delta files. YOU CANNOT TYPICALLY FLASH THE IMAGES EXTRACTED FROM THE PAYLOAD.
You need to patch the previous factory images with the diff. I'm downloading the update now and will gladly post a stock boot image when I get it (and if nobody else does it before )
Not really needed now though thanks to OP
Edit: Major version upgrades do appear to have flat images, but that shouldn't be an expectation. Always check the patch method in the metadata (extractor programs should at least write this to the console) is image and not bdiff.
Flippy125 said:
Thanks for this! Was stuck at work when I pulled the OTA and couldn't do it myself. Saved me a few steps
Click to expand...
Click to collapse
th3cavalry said:
The problem I have is it now says my device is corrupt even after side loading the whole OTA file. Still got the error right after the side loading.
Click to expand...
Click to collapse
Use a terminal app or use computer and type this.
su
reboot "dm-verity enforcing"
i need erase user data? i get boot loop after flashing boot.img
FellpeSoares said:
i need erase user data? i get boot loop after flashing boot.img
Click to expand...
Click to collapse
are you sure that you are installing it on pie?
RKBD said:
are you sure that you are installing it on pie?
Click to expand...
Click to collapse
yes
{
"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"
}
Is anyone having issues with Google Pay? I have been passing Safety Net with no issue. I even removed all of my modules and still can't make a payment with Google Pay. I noticed the only way to get it working is to go to Magisk Manager and check "Magisk Core Only Mode" so I can then use it. Anyone else having this issue?
Edit:
Razer Phone 2 Android 9
Magisk 18.1
Warrior1988 said:
Root by Magisk
https://drive.google.com/file/d/1eHBPo2YZBWPe6zIe5sTct5SfbHQZUPa5/view?usp=drivesdk
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot reboot
If you get this error
Your device is corrupt. It can’t be trusted and may not work properly.
Use a terminal app or use computer and type this.
su
reboot "dm-verity enforcing"
Click to expand...
Click to collapse
I did the same way but after flashing the patched boot its booting normaly but i am still stuck in bootanimation.
If i flash again stock boot img works normaly.
what can be the reason for that ?
Best Regards
SimpleGek
CurtisMJ said:
Guys, the payload.bin doesn't contain the full images. It contains bdiff delta files. YOU CANNOT TYPICALLY FLASH THE IMAGES EXTRACTED FROM THE PAYLOAD.
You need to patch the previous factory images with the diff. I'm downloading the update now and will gladly post a stock boot image when I get it (and if nobody else does it before )
Not really needed now though thanks to OP
Click to expand...
Click to collapse
I must of gotten lucky then. I extracted the boot.img from the payload.bin then used magisk to patch the boot.img for root. No issues so far.
rogeriskira said:
I must of gotten lucky then. I extracted the boot.img from the payload.bin then used magisk to patch the boot.img for root. No issues so far.
Click to expand...
Click to collapse
It is certainly possible from what I can tell. Most probably a guarantee when there's an OTA to the next version of Android(deltas would probably be bigger than a flat image). I'm more implying that this shouldn't be an expectation. If you tried to patch the boot.img extracted from the payload in the OTA for O-MR0 to O-MR2 there would most definitely have been problems, for instance.
So 'twas just a warning. That WAS lucky
Alright, so, I'm gonna be the one to ask the stupid question. All a completely stock user has to do to get root now (on an unlocked RP2) is... Update to Android Pie normally, unlock the bootloader, and then follow the OP?
CurtisMJ said:
It is certainly possible from what I can tell. Most probably a guarantee when there's an OTA to the next version of Android(deltas would probably be bigger than a flat image). I'm more implying that this shouldn't be an expectation. If you tried to patch the boot.img extracted from the payload in the OTA for O-MR0 to O-MR2 there would most definitely have been problems, for instance.
So 'twas just a warning. That WAS lucky
Click to expand...
Click to collapse
Do you working now with diff ? so how i understand diff means that we need merge RP2 with RP0 boot.img ?
simplegek said:
Do you working now with diff ? so how i understand diff means that we need merge RP2 with RP0 boot.img ?
Click to expand...
Click to collapse
Ok, so the OTA packages work like this:
The package has some metadata and a number of "payloads"(concatenated in a single file)
There is one sub-payload per partition in a firmware slot(A or B)
The metadata specifies the checksums, sizes etc of each payload, along with a patch method
The patch method tells the update engine how it should go about patching the matching partition with the payload.
Most of the time this patch method will be a bdiff(binary diff).
When its bdiff, the payload is not a full image, hence the previous image is required. This previous image can be extracted from a factory image, and the diff combined with it to form a flat image which you can flash directly (and patch with magisk)
SOMETIMES (like with a major upgrade where a diff will likely be larger than a image) the patch method is image, where the payload is a flat disk image of the partition which is simply written to the partition.
The Pie update evidently contained a flat boot image. So in this case, you DO NOT need to merge the images. But with with subsequent smaller updates, we likely will need to do that.
Thank you for the Intensive information.
Can you tell then , What propably can be my Problem , that i am stucking at the Bootanimation with patched boot.img(Magisk).
Hi guy's here's a short and simple guide on how to patch your own boot.img with Magisk.
Recommended to patch your own image read this
Grab the latest Platform Tools HERE
Code:
1. Download a stock Oxygen OS ROM Zip from [URL="https://www.oneplus.com/support/softwareupgrade/details?code=PM1574156267635"]Here[/URL] Or the general section of XDA many users post links to the latest builds.
2. Download [URL="https://androidfilehost.com/?fid=818070582850510260"]payload_dumper-win64.zip[/URL] And extract/copy it to Desktop.
3. Extract your payload.bin from the stock rom zip and copy it into the payload_input folder.
4. Run the payload_dumper exe.
5. When it's finished open the payload_output folder and copy the boot.img to Desktop keep it there as a backup.
6. Copy the same boot.img to your internal storage on your phone.
7. Install the magisk manager APK from here: [URL="https://github.com/topjohnwu/Magisk"]Magisk Manager[/URL]
8. Open Magisk Manager choose install and select "Select and Patch a file" Or if you wish to use beta release go to settings > Update Channel and switch to beta and then back to Install "Select And Patch A File"
9. Navigate to where you copied your boot.img on the phone.
10. Once it's patched you'll have an magisk_patched.img on your phone in the the Downloads folder.
11. Copy that image to your fastboot folder on your PC and flash it with fastboot flash boot magisk_patched.img
Done!
As always I'm not responsible for any issues your device might have or if your cat sets on fire.
Credits:
topjohnwu for Magisk/Manger
geminids14 for payload_dumper-win64
Nice, that is what we need .. Thanks Liam
How can i load twrp? Fastboot boot command, didnt work
DevrimSeven60 said:
How can i load twrp? Fastboot boot command, didnt work
Click to expand...
Click to collapse
Ask in the TWRP thread
Not working for me get a error file is to large to download when try to flash
dajumper said:
Not working for me get a error file is to large to download when try to flash
Click to expand...
Click to collapse
You're on OB1? It worked fine for me I flashed it multiple times already
I think I know the issue try updating your fastboot files from here: https://developer.android.com/studio/releases/platform-tools
liam_davenport said:
You're on OB1? It worked fine for me I flashed it multiple times already
I think I know the issue try updating your fastboot files from here: https://developer.android.com/studio/releases/platform-tools
Click to expand...
Click to collapse
Still the same
Im already rooted with bootimg having lat pie release. Is it possible to flash Android Q on top of last pie release and be rooted? Again I am rooted with magisk, not having twrp.
To update I always flash full updat from local, not reboot, install magisk to other slot and I was ready to go.
Will this work with Q update?
Not working for me. Both sims dissapear and phone keeps FC.
pister said:
Not working for me. Both sims dissapear and phone keeps FC.
Click to expand...
Click to collapse
Issue is on your end, I've flashed this multiple times no issue.
Working perfectly here I've clean flashed and redownloaded from the link and flashed. I've noticed sometime magisk causes sims to not show on boot before reboot the device and they should show again.
{
"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"
}
I see that when I root, both IMEIs disappears. Very strange
Sent from my [device_name] using XDA-Developers Legacy app
error 1 (or 7 kinstalldeviceopenerror) with 52 and 3.3.1-4 ???
what are the proper steps to cleanflash
pister said:
I see that when I root, both IMEIs disappears. Very strange
Click to expand...
Click to collapse
Mine both show. Not sure why yours have disappeared
liam_davenport said:
Mine both show. Not sure why yours have disappeared
Click to expand...
Click to collapse
Don't know. Tried to root by myself and the same happened
Sent from my [device_name] using XDA-Developers Legacy app
NateDev said:
error 1 (or 7 kinstalldeviceopenerror) with 52 and 3.3.1-4 ???
what are the proper steps to cleanflash
Click to expand...
Click to collapse
If you have twrp already you don't need this I posted this for people that want root without using twrp, Just flash magisk 19.4 in twrp
There is a few guides in this forum section with all info you need on how to flash etc
Weird.. Flashing patched file would always result in bootloop. Restore to boot. IMG fixed it
mgear356 said:
Weird.. Flashing patched file would always result in bootloop. Restore to boot. IMG fixed it
Click to expand...
Click to collapse
You flashed it on Open beta 1?
liam_davenport said:
You flashed it on Open beta 1?
Click to expand...
Click to collapse
Yup open beta 1
Great thanks!
But can we update OTA to B2 with this?
@liam_davenport I'm sorry for the noob question, I just got my OP 7 Pro and never used one before, also, I've been away from everything root related for a long time.
Do I need to unlock the bootloader first in order to do this?