Database Develop

[Q] CM10 4.1.2 flash to P.A.C True All in 1 ROM v22 error

downloaded all the goodies, gapps, rom, everything, went into CWM recovery (photon Q) followed steps exactly as followed, idk what the hell happened. Everything is wiped, tried rsd lite 5.7 with batakang stock and i get XML error every time. Ive flashed many roms since atrix 4g came out and so on, Can anyone please oblige me on this issue, im not a complete noobie.
asser failed: getprop("ro.product.device") == "xt925"
blah blah blah
E: error in /sdcard/Downloads/pac-mb886v22.zip
(status 7)
Installation aborted.
Any Help

BFRAPV42 said:
downloaded all the goodies, gapps, rom, everything, went into CWM recovery (photon Q) followed steps exactly as followed, idk what the hell happened. Everything is wiped, tried rsd lite 5.7 with batakang stock and i get XML error every time. Ive flashed many roms since atrix 4g came out and so on, Can anyone please oblige me on this issue, im not a complete noobie.
asser failed: getprop("ro.product.device") == "xt925"
blah blah blah
E: error in /sdcard/Downloads/pac-mb886v22.zip
(status 7)
Installation aborted.
Any Help
Click to expand...
Click to collapse
You must either A: install cwm (razr hd); or B: extract the zip, then go to Meta-inf > Com > Google > Android > Updater-Script, change "updater-script" to "updater-script.txt" then delete all the assert lines at the top, then save as "updater-script.file" then rename it to "updater-script" with no file extension again, and put it back in the same directory as the previous updater-script was, then repack the zip and install it. (I'm talking to you in detail because you apear to be new with one post, no offense if you know how to script it with note pad++ without detailed instructions. )

flashing error
Codex01 said:
You must either A: install cwm (razr hd); or B: extract the zip, then go to Meta-inf > Com > Google > Android > Updater-Script, change "updater-script" to "updater-script.txt" then delete all the assert lines at the top, then save as "updater-script.file" then rename it to "updater-script" with no file extension again, and put it back in the same directory as the previous updater-script was, then repack the zip and install it. (I'm talking to you in detail because you apear to be new with one post, no offense if you know how to script it with note pad++ without detailed instructions. )
Click to expand...
Click to collapse
i was on here prior but its been a while i appreciate the help. my issue theres no system on my AHD so how to get pacman rom redownloaded to my pc and no im not super BA at scripting. ya i can delete a few getvar lines to flash back to stock jb and start over again but syste.img wont even flash there while in AP Fastboot.
Thanks man
Trying to go to stock jb now, i had root and have unlocked bootloader, when usign rsd lite v5.7 i flash the xml after editing it and taking the 2 getvar lines out and now system wont flash, it says phone "Fail flashing process" "system.img" phone returned fail. flashing everything fine till it gets to the system.img file.

(Originaly Posted By: SkeevyDude)
Instructions Install Stock Fastboots JB
Download the respective fastboot zip you want to use
Extract the zip
Open a terminal to the extracted zips directory
Reboot into fastboot
Type the following commands in this order
fastboot flash boot boot.img
fastboot flash devtree device_tree.bin
fastboot erase system -w !
fastboot flash system system.img
fastboot -w
fastboot erase cache !
fastboot reboot
Don't use RSD Lite, its too complicated.

Codex01 said:
(Originaly Posted By: SkeevyDude)
Instructions Install Stock Fastboots JB
Download the respective fastboot zip you want to use
Extract the zip
Open a terminal to the extracted zips directory
Reboot into fastboot
Type the following commands in this order
fastboot flash boot boot.img
fastboot flash devtree device_tree.bin
fastboot erase system -w !
fastboot flash system system.img
fastboot -w
fastboot erase cache !
fastboot reboot
Don't use RSD Lite, its too complicated.
Click to expand...
Click to collapse
And the erase commnds with ! don't work for us.
I installed CM10.1 by manually formatting /system and /data before flashing. Can't fail a build.prop check if there is no build.prop to check

stock jb
skeevydude said:
And the erase commnds with ! don't work for us.
I installed CM10.1 by manually formatting /system and /data before flashing. Can't fail a build.prop check if there is no build.prop to check
Click to expand...
Click to collapse
so i downloaded stock att jb rom from xda, went to the directory C:\user\costco\desktop and to the stock jb folder open command prompt and typed the code.(phone is in fast boot currently as well) Cmmnd prompt says is not recognized as an external or internal command,operable program or batch file. Maybe my head is just to busy to focus i must be messing up somewhere. You guys are so freaking awesome for being patient with me and helping me, ill buy the brews haha
Not an issue with bootloader already unlocked i assume cause once im back on stock im gonna be 1000 times more careful when rerooting again to get back where i was.

idk if its terminal for vista or if its the download i got, i got it from a link on here from, I leave the "getvar lines on the xml file when i do it through terminal right?

Check out my reply in this post. I had the same problem and got it figured out...
http://forum.xda-developers.com/showthread.php?t=2209660
Atrix HD - PACman ROM
RSD wouldn't flash system.img for some reason and wouldn't exit AP fastboot mode until I successfully flashed. So with the working fastboot files (check out skeevydudes posts, don't use the SDK fastboot) make a folder w fastboot.exe, fastboot api, the stock zip for rsd (remove the getvar and system.img lines of course), epinter's recovery (skeevydude made a recovery flash that contains this), and system.img (extracted from the stock RSD flash zip). Then open terminal or command prompt. cd to the folder you just made... fastboot flash system system.img then it will reboot when it flashes, reboot back to AP fastboot and then cd to fold again and then fastboot flash recovery recovery.img Then from epinter's CWM you can flash the ROM as instructed in the OP wo having to edit anything. Please excuse my mess doing all this from my phone

Droid4Drew said:
Check out my reply in this post. I had the same problem and got it figured out...
http://forum.xda-developers.com/showthread.php?t=2209660
Atrix HD - PACman ROM
RSD wouldn't flash system.img for some reason and wouldn't exit AP fastboot mode until I successfully flashed. So with the working fastboot files (check out skeevydudes posts, don't use the SDK fastboot) make a folder w fastboot.exe, fastboot api, the stock zip for rsd (remove the getvar and system.img lines of course), epinter's recovery (skeevydude made a recovery flash that contains this), and system.img (extracted from the stock RSD flash zip). Then open terminal or command prompt. cd to the folder you just made... fastboot flash system system.img then it will reboot when it flashes, reboot back to AP fastboot and then cd to fold again and then fastboot flash recovery recovery.img Then from epinter's CWM you can flash the ROM as instructed in the OP wo having to edit anything. Please excuse my mess doing all this from my phone
Click to expand...
Click to collapse
no man its all good i need all the tutorial help i can get, never have bricked a phone and worried i did so, i can make sense of most of it but my head is full of tht sdk stuff, trying to forget it and get this working, i feel like an idiot asking for step by step crap but how am i to get it quicker than asking for a little help. learning from this is major for me. Thanks man hopefully i get it ok.

still no bueno
BFRAPV42 said:
no man its all good i need all the tutorial help i can get, never have bricked a phone and worried i did so, i can make sense of most of it but my head is full of tht sdk stuff, trying to forget it and get this working, i feel like an idiot asking for step by step crap but how am i to get it quicker than asking for a little help. learning from this is major for me. Thanks man hopefully i get it ok.
Click to expand...
Click to collapse
still a no go, have the new folder with all 5 items needed, pulled up command prompt and its giving same issue. F WORDDDDDDDDDs
C:\Users\Costco>fastboot flash system system.img
'fastboot' is not recognized as an internal or external command,
operable program or batch file.
same error.

You need these fastboot binaries in the folder also, sorry I couldn't think of the word binaries earlier when I was typing... This I what I ment by the exe and api, just put the two files from the windows folder of the zip into the folder you made and try again... http://www.batakang.com/ftp/devs/mattlgroff/snapdragon-fastboots.zip
Atrix HD - PACman ROM

Droid4Drew said:
You need these fastboot binaries in the folder also, sorry I couldn't think of the word binaries earlier when I was typing... This I what I ment by the exe and api, just put the two files from the windows folder of the zip into the folder you made and try again... http://www.batakang.com/ftp/devs/mattlgroff/snapdragon-fastboots.zip
Atrix HD - PACman ROM
Click to expand...
Click to collapse
i have the snapdragon fastboot .exe and .api in the folder already. along with the system.img , epinters recovery.img and MB886_att-user-4.1.1-9.8.0Q-97_MB886_FFW-20-27-release-keys-ATT-US_BuildA
i took a screen shot of the directions you gave with the command prompt open and the folder with the files in it but couldnt upload it unfortunately.

Make sure adb.exe and fast boot.exe are set to run as admin. Right click them and set them to be admin. Then try again.
Sent from my MB886 using xda app-developers app

TTLayland said:
Make sure adb.exe and fast boot.exe are set to run as admin. Right click them and set them to be admin. Then try again.
Sent from my MB886 using xda app-developers app
Click to expand...
Click to collapse
fastboot.exe is admin api doesnt have an option in advanced for run as admin, i opened terminal and cd to where the file was on c: drive and typed [fastboot flash system system.img] hit entere and it worked but the phone never rebooted after it completed, when i typed [fastboot flash recovery recovery.img] with is epinters recovery it says ERROR cannot load recovery.img

Scratch that I'm actually replying to this from stock jb, thank all you guys for all the help.
Sent from my MB886 using xda app-developers app

So my advice worked?
Sent from my MB886 using xda app-developers app

Ya it work but It wouldn't with battery under 60% when I charged it up it flashed with ease. I'm on stock 4.1.1 gonna try epinters cwm to flash and then finally pacman
Sent from my MB886 using xda app-developers app

BFRAPV42 said:
Ya it work but It wouldn't with battery under 60% when I charged it up it flashed with ease. I'm on stock 4.1.1 gonna try epinters cwm to flash and then finally pacman
Sent from my MB886 using xda app-developers app
Click to expand...
Click to collapse
I found that the advice I gave you was the only thing that was not in the instructions. Good stuff that you got it working though.
Sent from my MB886 using xda app-developers app

Got a ? about Atrix HD flashed with Pac Man v22
I flashed Pac Man and everything looks great, and works well tiny lag issues but I love it so thank you to all the devs involved.
But...I have seemed to lose root access. I have tried to reinstall the root access with one click and it stops at Daemon started successfully *
any ideas thanks in advance!

Install a superuser zip through cwm.
Sent from my PACMAN MATRIX HD MAXX

[GUIDE] How to update to Android M-Preview-2 from V1 without loosing your data

If you are in M-preview-1 and don't want to lose your dat/apps you can follow this guide, after that, you'll havw M-preview-2 installed and a rooted device.
Firstly, you need to have a pc with adb working. There are several wyas to achive that, but I presume that if you are already in M preview V1, you have it.
Then, you need to have an unlocked bootloader, again I assume that you have it.
======Skip this is you have adb and unlocker bootloader===========
In any case, in linux there is a very trivial way to get both things (probably in windows and mac is more or less the same):
In a terminal:
sudo apt-get install android-tools*
Then plug your N5 to your computer with a usb cable (depuration mode enable), check that everything is working fine:
sudo adb devices
Then;
sudo adb reboot bootloader
sudo fastboot oem unlock
Then reboot
========================================================
Again, if you are not coming from M-preview-1 I do not recommend this method
1. Download M-preview-2 from this page.
2. Download twrp from here.
3. Create a folder, move twrp to that folder and extract M-preview-2 to the same folder (no sudir, all the files in the same folder), extract again image-hammerhead-MPZ79M.zip in the same folder.
4. Download Despair kernel in your device.
5. Download SuperSU beta 2.49 in your device.
Now, we are ready to flash everything:
6. Open a terminal and cd to the folder where you keep everything from previous steps.
7. Plug your device using a usb cable
8. Type the following commands in the terminal (if you are not in Linux, use the same commands but without "sudo"):
sudo device (just to check that adb ·see your device)
sudo adb reboot bootloader
sudo fastboot flash bootloader bootloader-hammerhead-HHZ12h.img
sudo fastboot flash boot boot.img
sudo fastboot flash radio radio-hammerhead-M8974A-2.0.50.2.26.img
sudo fastboot flash system system.img (this step takes a while)
sudo fastboot flash cache cache.img
sudo fastboot flash recovery twrp-2.8.7.1-hammerhead.img
9. Reboot in recovery (just using the vol up or down and the on buttom).
10. Flash Despair kernel
11. Flash SuperSU
12 Wipe Dalvik and cahe (just in case)
13. Reboot

Flashing over preview 1 won't bring additional issues?

migueldbr said:
Flashing over preview 1 won't bring additional issues?
Click to expand...
Click to collapse
Of course II'm still testing, but it seems that there is not new bugs (yet).

All I did was edit flash-all.sh, removed the '-w', then run it Anyone who has flashed the first version will already have the tools installed.
I wouldn't recommend using alternate kernels as they won't be designed for preview 2.

does your guys system app crash if you open data usage (set language to something except english) ?

tugler said:
does your guys system app crash if you open data usage (set language to something except english) ?
Click to expand...
Click to collapse
Yes

I just did a clean flash via fastboot manually. Booting now. I ain't got time for issues.

Is there a reason the OP links to TWRP 2.8.6.1 instead of the latest version (2.8.7.1)?

Anyone else having trouble flashing the despair kernel? I'm getting assert failed: getprop("ro.product.devices") (Status 7) when trying to flash. I tried sideloading and got the same errors followed by E: Error in /tmp/update.zip. Clearly I'm doing something wrong. Any ideas?

6spdsc4 said:
Anyone else having trouble flashing the despair kernel? I'm getting assert failed: getprop("ro.product.devices") (Status 7) when trying to flash. I tried sideloading and got the same errors followed by E: Error in /tmp/update.zip. Clearly I'm doing something wrong. Any ideas?
Click to expand...
Click to collapse
I'm still transferring my nandroid backup to my PC and haven't tried yet, but it's possible that the kernel won't flash on preview 2 because it's not yet updated for preview 2. As @TonyHoyle said, it's probably not a great idea to use one until they've specifically been updated for preview 2.

TonyHoyle said:
All I did was edit flash-all.sh, removed the '-w', then run it Anyone who has flashed the first version will already have the tools installed.
I wouldn't recommend using alternate kernels as they won't be designed for preview 2.
Click to expand...
Click to collapse
can u explain more detailed?

Flashable zip for multirom
flashable zip to use with multirom, please ?

As TonyHole suggested, just remove the -w; basically this will do: (you can do below on a command line as long as you are in the extracted TGZ file and in the hammerhead-MPZ79M folder/directory)
fastboot flash bootloader bootloader-hammerhead-HHZ12h.img
fastboot reboot-bootloader
fastboot flash radio radio-hammerhead-M8974A-2.0.50.2.26.img
fastboot reboot-bootloader
fastboot update image-hammerhead-MPZ79M.zip
This works for me no issues as data is left intact but everything else is updated ; suggesting NOT to do this from an Android L to Android M Preview 2 and do a proper wipe
This will rebuild the ART app optimize on reboot
OP: Next time make a guide for doing STOCK update FIRST ; save the kernel and root for a SEPERATE post or a seperate section in the post

Hellscore kernel works great
Clean flash
I don't understand why any one would do a dirty dirty install with a preview no less
Sent from my Nexus 5 xda-dev app

The OTA is out and it will do the same process end result as the dirty flash method I did, keeps Data and app rebuild on reboot.

NPS_CA said:
The OTA is out and it will do the same process end result as the dirty flash method I did, keeps Data and app rebuild on reboot.
Click to expand...
Click to collapse
Do you have a link?
Sent from my Nexus 5

Is there zip file available
Sent from my Nexus 5 using XDA Premium 4 mobile app

thesebastian said:
Do you have a link?
Sent from my Nexus 5
Click to expand...
Click to collapse
Is this a real question?
Sent from my Nexus 5 using Tapatalk

Ben36 said:
Is this a real question?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Yeah I was asking about the official OTA. Since only the link for Shamu was captured so far.
Sent from my Nexus 5

thesebastian said:
Yeah I was asking about the official OTA. Since only the link for Shamu was captured so far.
Sent from my Nexus 5
Click to expand...
Click to collapse
Surely if you go about phone. System update. Then you'll either have it or not if it's been pushed out to your device?
Sent from my Nexus 5 using Tapatalk

BLU R2 LTE??? unlock/rootable?

I picked up a BLU R2 LTE (16g/2GB version) for dirt, Build: BLU_R0170WW_V7.0.04.01. Is it even remotely possible to unlock and root this thing or am I stuck with a bone stock android?

DaGoo_Balls said:
I picked up a BLU R2 LTE (16g/2GB version) for dirt, Build: BLU_R0170WW_V7.0.04.01. Is it even remotely possible to unlock and root this thing or am I stuck with a bone stock android?
Click to expand...
Click to collapse
It apparently is.
https://forum.xda-developers.com/r1-hd/development/unofficial-lineageos-14-1-t3689435/post75020813

Thanks. Looks like I have plans for NYE

I managed to root the phone by unlocking the bootloader with fastboot, then using Magisk in conjunction with the boot image file dumped by ipdev in this post.
Unlock your bootloader by running
Code:
fastboot oem unlock
Copy the blur2-boot.img file available here to your phone.
Install Magisk Manager, then generate a patched version of the blur2-boot.img file using the app.
Copy the patched version back to your computer and flash it to the boot partition with
Code:
fastboot flash boot /path/to/patched_boot.img
After this you should have root via the Magisk Manager app.

somed4ze said:
I managed to root the phone by unlocking the bootloader with fastboot, then using Magisk in conjunction with the boot image file dumped by ipdev in this post.
Unlock your bootloader by running
Copy the blur2-boot.img file available here to your phone.
Install Magisk Manager, then generate a patched version of the blur2-boot.img file using the app.
Copy the patched version back to your computer and flash it to the boot partition with
After this you should have root via the Magisk Manager app.
Click to expand...
Click to collapse
You would be better off to patch my boot image and fastboot boot it.
Then backup your boot image, patch it with magisk, and flash that one back to the device.
Code:
adb shell su -c "dd if=/dev/block/mmcblk0p7 of=/sdcard/blur2-boot.img"
This keeps things clean, just incase you are using a boot image that is different from your own device. Plus you have a "stock" boot image backup if you ever need it.
Not a bad idea to grab recovery also.
Code:
adb shell su -c "dd if=/dev/block/mmcblk0p8 of=/sdcard/blur2-recovery.img"
Sent from my ford using XDA Labs
BLU R2 LTE files. Link

somed4ze said:
I managed to root the phone by unlocking the bootloader with fastboot, then using Magisk in conjunction with the boot image file dumped by ipdev in this post.
Unlock your bootloader by running
Code:
fastboot oem unlock
Copy the blur2-boot.img file available here to your phone.
Install Magisk Manager, then generate a patched version of the blur2-boot.img file using the app.
Copy the patched version back to your computer and flash it to the boot partition with
Code:
fastboot flash boot /path/to/patched_boot.img
After this you should have root via the Magisk Manager app.
Click to expand...
Click to collapse
Does it matter if I get the 1gb ram/16gb flash or 2gb ram/32gb flash, or will this work on both? I was planing on ordering this one. Thanks!

bobsmithy said:
Does it matter if I get the 1gb ram/16gb flash or 2gb ram/32gb flash, or will this work on both? I was planing on ordering this one. Thanks!
Click to expand...
Click to collapse
The size of memory "shouldn't" matter.

Braunish said:
Hi there, am trying to root this phone also. Stumbled upon your thread and had a question. If I take the 3 image files (recovery, boot, system) that are included at mediafire site (that you included in your post) and replace the same 3 image files in stock rom, would that work to root the phone? Thank you for any help, I've tried kingoroot, kingroot, and framaroot to no avail.
Click to expand...
Click to collapse
Read back few post on this thread. They discuss successful root method.
Basically unlock bootloader and use majisk manager to patch boot.img and flash patched image with fastboot.

Root R2 Plus w/ BLU R0190WW V7.0.04.01 GENERIC 11-02-2018
DaGoo_Balls said:
Thanks. Looks like I have plans for NYE
Click to expand...
Click to collapse
Hi there, I recently got a Blu R2 Plus and am aiming to root. I used the boot-sign.img that came with that ROM version in title (9447 KB) when patching with Majisk Manager and came up with a patched file of 9.57 MB size. Is there a way to test this ROM, or can you verify that is the same sizes you dealt with when you went through this process. Thank you for any information. It took me a while and a factory reset before I could get majisk manager installed to patch the correct boot-sign.img file.

Hi There copy img file to where on phone
To where do I copy the image file on the phone that gets "patched" by Majisk?
"Copy the blur2-boot.img file available here to your phone."
Thank you very much,
Michael
somed4ze said:
I managed to root the phone by unlocking the bootloader with fastboot, then using Magisk in conjunction with the boot image file dumped by ipdev in this post.
Unlock your bootloader by running
Code:
fastboot oem unlock
Copy the blur2-boot.img file available here to your phone.
Install Magisk Manager, then generate a patched version of the blur2-boot.img file using the app.
Copy the patched version back to your computer and flash it to the boot partition with
Code:
fastboot flash boot /path/to/patched_boot.img
After this you should have root via the Magisk Manager app.
Click to expand...
Click to collapse

Braunish said:
To where do I copy the image file on the phone that gets "patched" by Majisk?
"Copy the blur2-boot.img file available here to your phone."
Thank you very much,
Michael
Click to expand...
Click to collapse
If I understand correctly.
You have adb and fastboot installed.
You have a boot image that works for your device and tested it by using fastboot to boot it. let's call it working_boot.img
You have MagiskManager installed.
The next steps:
adb push working_boot.img /sdcard Doesn't really matter where you put it.
Open MagiskManager
Tap on Install
Select Install
Select Patch Boot Image File
Tap on Internal storage Note: If Internal storage is not displayed. Tap on the 3-dot menu (upper right corner) and select Show SD card.
Scroll down and tap on working_boot.img
When Magisk is done patching the image file, select CLOSE
You can close MagiskManager as well.
adb pull /sdcard/magiskmanager/patched_boot.img
Reboot to bootloader and fastboot boot patched_boot.img
Open MagiskManager. You should see that Magisk is installed and active.
Now that you have temporary root, you have some options.
The easiest way would be to open MagiskManager and use the Direct install option. This will pull, patch and install a patched boot.img to the device.
Unless the the original working_boot.img used is the correct one for your device.
The safer way, pull the stock_boot.img I normally grab recovery also from the device.
For BLU R2 LTE
Code:
adb shell su -c "dd if=/dev/block/mmcblk0p7 of=/sdcard/BLUR2-boot.img"
adb shell su -c "dd if=/dev/block/mmcblk0p8 of=/sdcard/BLUR2-recovery.img"
adb pull /sdcard/BLUR2-boot.img
adb pull /sdcard/BLUR2-recovery.img
Then patch it and fastboot boot it to make sure it works.
After that you can either use MagiskManager Direct install or fastboot to flash the new patched_boot.img.

Bricked my device, used SP Flash Tool to update - Now no OTA?
I hope this is on topic enough to not start a new thread and dirty up the R1 forum
I ended up bricking my Blu R2 LTE by messing with a core APK causing it to boot loop. I didn't have a backup, so I had to resort to using SP Flash Tool to flash back to the only stock rom I could find online. Linked from the post here: www[.]getdroidtips[.]com/nougat-firmware-blu-r2-lte/
The reflash went just fine, but now I noticed I seem to be "stuck" at the January patch level / v01 build, and I'd like to bring it back up to the latest build and use the latest dump you provided w/ Magisk to re-root it again. I've tried all the tricks to get it to try to discover the updates, but nothing is working. It's been about 5 days now with no update offered.
Any idea how I can get it to either accept new OTA releases or where I could find a newer stock rom to reflash?
Thanks for your great work!
Oryx

Just got this phone and should have checked the mediafire link posted by ipdev. -_- Does anyone still have a copy or willing to share a link for me to get it or another method, theres really not much when it comes to this model. I would greatly appreciate it. Must have root to use a blu.

8milerd said:
Just got this phone and should have checked the mediafire link posted by ipdev. -_- Does anyone still have a copy or willing to share a link for me to get it or another method, theres really not much when it comes to this model. I would greatly appreciate it. Must have root to use a blu.
Click to expand...
Click to collapse
These links do not work? Link Direct download links are from MediaFire. Click on the name of the file.
I try to use direct download links from MediaFire. There servers can normally handle it. You do not have to navigate ads and redirects with direct download links.
---------- Post added at 04:58 AM ---------- Previous post was at 04:35 AM ----------
HornyOryx said:
I hope this is on topic enough to not start a new thread and dirty up the R1 forum
I ended up bricking my Blu R2 LTE by messing with a core APK causing it to boot loop. I didn't have a backup, so I had to resort to using SP Flash Tool to flash back to the only stock rom I could find online. Linked from the post here: www[.]getdroidtips[.]com/nougat-firmware-blu-r2-lte/
The reflash went just fine, but now I noticed I seem to be "stuck" at the January patch level / v01 build, and I'd like to bring it back up to the latest build and use the latest dump you provided w/ Magisk to re-root it again. I've tried all the tricks to get it to try to discover the updates, but nothing is working. It's been about 5 days now with no update offered.
Any idea how I can get it to either accept new OTA releases or where I could find a newer stock rom to reflash?
Thanks for your great work!
Oryx
Click to expand...
Click to collapse
A while back , I had to do a factory reset to get an OTA. Then I had to un-root it to get the OTA to flash.

Anyone got trouble rooting?

Anyone noticed that can't root with magisk the p20 pro or it just me?

Yes! There is a way to extract the boot image, use Magisk to patch it, then flash that boot image via fastboot. I'm actually waiting for someone with experience to advise on these items:
1. Can I extract the boot image from my phone directly? If so, can someone point me in the direction of the software to do so?
2. If I can't extract directly, do I need to use the update file from Firmware Finder that matches my current firmware exactly? I'm running B155, but there seems to be slight variations in the naming for some of the available firmware.
3. After I get all of this completed successfully, how do I verify that the image is good to use to avoid bricking the phone?
Thanks in advance to anyone that could help!

sarichter said:
Yes! There is a way to extract the boot image, use Magisk to patch it, then flash that boot image via fastboot. I'm actually waiting for someone with experience to advise on these items:
1. Can I extract the boot image from my phone directly? If so, can someone point me in the direction of the software to do so?
2. If I can't extract directly, do I need to use the update file from Firmware Finder that matches my current firmware exactly? I'm running B155, but there seems to be slight variations in the naming for some of the available firmware.
3. After I get all of this completed successfully, how do I verify that the image is good to use to avoid bricking the phone?
Thanks in advance to anyone that could help!
Click to expand...
Click to collapse
This guide has everything you should need. https://topjohnwu.github.io/Magisk/install.html
1. No, unless rooted
2. Find either the same FW you are on, or extract from a OTA.
3. Not sure on that one, it's always worked for me.

purple patch said:
This guide has everything you should need. https://topjohnwu.github.io/Magisk/install.html
1. No, unless rooted
2. Find either the same FW you are on, or extract from a OTA.
3. Not sure on that one, it's always worked for me.
Click to expand...
Click to collapse
Thank you so much! Do you have any idea where I can get the OTA or at least figure out in specificity which OTA on Firmware Finder is correct? It sounds like it needs to be 100% exact to avoid issues / bricking.
---------- Post added at 03:12 PM ---------- Previous post was at 02:18 PM ----------
purple patch said:
This guide has everything you should need. https://topjohnwu.github.io/Magisk/install.html
1. No, unless rooted
2. Find either the same FW you are on, or extract from a OTA.
3. Not sure on that one, it's always worked for me.
Click to expand...
Click to collapse
OK... so I was able to extract the RAMDISK.IMG file but I can't patch it because Magisk Manager hangs after I install it. Is there a way to patch the RAMDISK.IMG file manually or via PC?

OK... so if anyone who is having trouble rooting... this is what I did to get root.
1. Be sure to download the firmware you are CURRENTLY on to avoid any possible issues.
2. Extract the RAMDISK.img file from the post above: https://topjohnwu.github.io/Magisk/install.html
3. Obtain a previously patched RAMDISK file to get an initial Magisk install on your phone first. There is one on XDA floating around named CLT-29-MAGISK.img.
4. Boot into FASTBOOT and then get to a CMD window with your ADB tools and use the command "fastboot flash ramdisk CLT-29-MAGSIK.img"
5. Reboot the phone and download Magisk Manager 5.5.5.
6. After installing Magisk Manager 5.5.5, install the next two upgraded versions while INSIDE Magisk Manager until you get to 7.1.x.x.
7. Click INSTALL on the Magisk option and let Magisk Manager patch your freshly extracted RAMDISK.img file from Step 2.
8. Copy that RAMDISK.img file to your PC.
9. Boot into FASTBOOT and then get to a CMD window with your ADB tools and use the command "fastboot flash ramdisk patched_boot.img"
10. Reboot and you'll have root!

sarichter said:
OK... so if anyone who is having trouble rooting... this is what I did to get root.
1. Be sure to download the firmware you are CURRENTLY on to avoid any possible issues.
2. Extract the RAMDISK.img file from the post above: https://topjohnwu.github.io/Magisk/install.html
3. Obtain a previously patched RAMDISK file to get an initial Magisk install on your phone first. There is one on XDA floating around named CLT-29-MAGISK.img.
4. Boot into FASTBOOT and then get to a CMD window with your ADB tools and use the command "fastboot flash ramdisk CLT-29-MAGSIK.img"
5. Reboot the phone and download Magisk Manager 5.5.5.
6. After installing Magisk Manager 5.5.5, install the next two upgraded versions while INSIDE Magisk Manager until you get to 7.1.x.x.
7. Click INSTALL on the Magisk option and let Magisk Manager patch your freshly extracted RAMDISK.img file from Step 2.
8. Copy that RAMDISK.img file to your PC.
9. Boot into FASTBOOT and then get to a CMD window with your ADB tools and use the command "fastboot flash ramdisk patched_boot.img"
10. Reboot and you'll have root!
Click to expand...
Click to collapse
Not sure why people struggle with this. The guy who started this thread has a copypasta guide he posted and could have followed. You should post your post in guide section for others I guess.

purple patch said:
Not sure why people struggle with this. The guy who started this thread has a copypasta guide he posted and could have followed. You should post your post in guide section for others I guess.
Click to expand...
Click to collapse
People struggle because the firmware is from 100 different regions, all with different release dates, there is no official TWRP that works 100% correctly with encryption, and Magisk changed the standard install method. I'm not surprised that people are having a tough time figuring out what to do so they don't brick their phone. This thing isn't cheap!

Dirty Flash December Update

This is probably a dumb question... I have the Google store unlocked Pixel 4XL. I'm currently on the October factory image. I want to update to the December update.
Is there any reason I can't just dirty Flash the December update factory image and then use Magisk to patch the boot image from the factory update?
Or is there and easier way to get to the new update for unlocked Pixels that doesn't include the alternate method in the guide section of the forums?

ihuntinde said:
This is probably a dumb question... I have the Google store unlocked Pixel 4XL. I'm currently on the October factory image. I want to update to the December update.
Is there any reason I can't just dirty Flash the December update factory image and then use Magisk to patch the boot image from the factory update?
Or is there and easier way to get to the new update for unlocked Pixels that doesn't include the alternate method in the guide section of the forums?
Click to expand...
Click to collapse
Having an "unlocked" phone doesn't necessarily mean it is bootloader unlocked. Just wanted to confirm you are bootloader unlocked already. If yes, just d/l the December full image (make sure to get the RIGHT ONE) and edit the flash-all.bat to remove the wipe flag. You will lose root, but if you extract the boot.img from the image beforehand, patch it with Magisk Manager and put it in your adb folder before starting, you just run the script, boot back to fastboot and then flash the patched boot.img. May sound a bit complicated, but patching the image and pre-placing it before you start makes things go quicker. Good luck! :good:

v12xke said:
Having an "unlocked" phone doesn't necessarily mean it is bootloader unlocked. Just wanted to confirm you are bootloader unlocked already. If yes, just d/l the December full image (make sure to get the RIGHT ONE) and edit the flash-all.bat to remove the wipe flag. You will lose root, but if you extract the boot.img from the image beforehand, patch it with Magisk Manager and put it in your adb folder before starting, you just run the script, boot back to fastboot and then flash the patched boot.img. May sound a bit complicated, but patching the image and pre-placing it before you start makes things go quicker. Good luck! :good:
Click to expand...
Click to collapse
Thanks for the reply. I can confirm that I have an unlocked bootloader.

Just as a point of frustration........
for the last 24 hours I've been fighting this issue with must be flashed in fastbootd... so, i download the new platform-tools... replace my existing platform-tools... all is good, right?
NOPE....
I have another platform-tools on my C: drive... that is assigned in my Path Variable... so it's trying to use the old platform tools... GRRRRR...
needless to say, i'm all fixed up now. Probably didn't have to stay up until 2:00am trying to get back to the October update...

So.. for those that need it, here are my exact steps for a bootloader unlocked Pixel 4XL bought from the Google Store:
1. Download full factory image from here: https://developers.google.com/android/images#coral (10.0.0 (QQ1B.191205.012.A1, Dec 2019))
2. Extract the zip file, open the zip inside of that extracted folder and copy the boot.img to your phone's Downloads folder.
2a. I used a usb cable to my PC and put the phone in File transfer / Android Auto to do this)
3. In Magisk Manager, click Install. Click Install again in the popup. Choose Select and Patch a File.
4. Find the boot.img that you copied to your phone's Download folder. Select it.
5. Copy the magisk_patched.img file from your phone's Download folder to the unzipped factory image folder.
5a. Refer to 2a above. You may have to disconnect the usb cable and reconnect. For some reason, my PC wasn't refreshing the folder with the patched file until I did this.
6. With your phone connected and in File transfer mode. Open a command prompt in the folder you unzipped the factory image to.
6a. You may be able to shift and right-click then click Open Command Prompt window here. That will open the command prompt at that exact folder instead of having to navigate to it through the command prompt. If you are a newer version of Windows 10, you may only see the Powershell option. I am not sure if Powershell will work. However, to get to a "command prompt" to be able to run the flash-all and fastboot commands. Simply type cmd and hit <enter>. Then you can use the adb, flash-all, and fastboot commands as explained below. ** WARNING: I DID NOT USE POWERSHELL, USE AT YOUR OWN RISK **
6b. Type adb reboot bootloader.
7. Remembering this is a dirty flash (i.e, keeping all of your data) edit the flash-all.bat file in any type of editor (even notepad). Look for the line that says fastboot -w update image-coral-qq1b.191205.012.a1.zip and remove the -w. So, the line just above echo Press any key to exit... should look like this:
7a. fastboot update image-coral-qq1b.191205.012.a1.zip
8. Wait for the flashing to finish and for your phone to reboot and fully boot back up.
9. Once it's connected, put your phone in File Transfer usb mode again.
10. Open a command prompt and type adb reboot bootloader
10a. See 6a
11. Once the phone is in fastboot mode, type fastboot flash boot magisk_patched.img
12. Once that is done, type adb reboot.
You should now be on the December update and rooted.
If you get the error that says "should be flashed in fastbootd", I can confirm that you do not have a new enough version of fastboot.exe. You can do one of two things. First, download the latest platform tools from here: https://developer.android.com/studio/releases/platform-tools
1. Either hunt down every copy of your platform-tools folder (I had multiple for some dumb reason) and consolidate to just one, then update your platform-tolls. Then update your system environment variables and point it to this new folder (making sure it's the only folder pointing to a platform-tools version).
2. Download the new version and copy the fastboot.exe and adb.exe directly into the folder with the flash-all.bat. This will guarantee you are using the correct version.
Hope this helps someone...

ihuntinde said:
Just as a point of frustration........
for the last 24 hours I've been fighting this issue with must be flashed in fastbootd... so, i download the new platform-tools... replace my existing platform-tools... all is good, right?
NOPE....
I have another platform-tools on my C: drive... that is assigned in my Path Variable... so it's trying to use the old platform tools... GRRRRR...
needless to say, i'm all fixed up now. Probably didn't have to stay up until 2:00am trying to get back to the October update...
Click to expand...
Click to collapse
This happens more than you know. Glad you got it sorted. Next time (in a couple of weeks) it will be a snap.