Hey,
first of all sorry for my bad english. I really hope anyone understand the problem and can help me
I have tried the following steps to create the zip:
1. downloaded the actually FTF
2. renamed ROM.ftf to ROM.zip
3. extracted the system.sin
4. extract the system.sin to ext4 via Flashtool 0.9.12.1
Then occurred the first problem. I could not open the ext4 file with any tool from XDA.
So I searched for other options to create the zip and tried the following steps:
1. installed the FTF on the smartphone i prefer
2. installed the doomkernel with dual-recovery
3. started a twrp backup
4. copied the syststem.ext4.win to my harddrive
5. extrated the system.ext4.win and put it together with the META-files and the updater-script
Butevery time when i tried to flash this file, i received the error "error set_perm aborted ... 7"
I get the same message when I tried to flash the ROM from @krabappel2548
http://forum.xda-developers.com/showthread.php?t=2440408
Is there a problem with the recovery?
Can anyone help me?
greetZ,
Daniel
http://bit.ly/19HouFo
The first hit, that's what you need to read, learn and try,
Its a bit more complicated that what you have tried so far
Thanks for the quick response and the info.
But how would I proceed without tools? And the second question is, why can not I install the ROM from krabappel?
DanielGiGi said:
Thanks for the quick response and the info.
But how would I proceed without tools?
Click to expand...
Click to collapse
You need to install the tools. Either install a dual boot linux machine or a virtual Linux machine. Read post 3 of that thread
And the second question is, why can not I install the ROM from krabappel?
Click to expand...
Click to collapse
Because of this
Code:
== Information ==
Only for Unlocked bootloaders!!
You don't have an unlocked bootloader is my guess
At this time, the bootloader was unlocked. Now I have made a TA recovery and everything is stock
But I will try it later one more time with the kitchen when i'm at home.
Thank you for your help. I will give you a feedback.
all hd
It does not work. I have installed a Linux client. Then I unzipped the system.sin via flashtool. After that I received a system.ext4, which I can not open in the KITCHEN.
Please help me.
DanielGiGi said:
It does not work. I have installed a Linux client. Then I unzipped the system.sin via flashtool. After that I received a system.ext4, which I can not open in the KITCHEN.
Please help me.
Click to expand...
Click to collapse
rename it to system.img.
Its in the instructions for the kitchen thread
by mistake i deleted the whole data includeing os and now unable to send zip file to internal memory of my rooted moto x
please help me
Sir,
Please wait until mods will move this thread to the device specific forum.
For reply or more questions please register an account on XDA forums.
Stand by
Good luck
XDA Visitor said:
by mistake i deleted the whole data includeing os and now unable to send zip file to internal memory of my rooted moto x
please help me
Click to expand...
Click to collapse
You can restore original firmware using RSD Lite no problem . But You need to download your retail version Firmware and Make small change in xml file then you can install it.
Please follow the instructions and thread :
http://forum.xda-developers.com/moto-x/general/guide-moto-x-return-to-100-stock-using-t2446515
you can download your firmware from here:
http://www.filefactory.com/folder/dd05c058d3ff8dbe/?sort=created&order=DESC&show=100&page=1
Thanks
MAhesh
You shouldnt need RDS... Im Guessing you have custom recovery? Should be able to boot into recovery and use adb to push a rom, or if your recovery supports it use adb sideload to load a rom straight from your comp.
plenty of info on bothe the adb push and adb sideload commands on google.
Or just use fastboot to flash a ROM manually.
thanks a ton
Issue resolved i have done using adb
Hello, my Pure Edition has TWRP recovery on it and is on MM. Does anyone have a simple guide and download link to factory images for it? I want to revert it back to stock everything but Googling it gives me confusing guides for Lollipop. If I flashed Lollipop over Marshmallow, will it brick the device? I need to do this ASAP! Thanks.
https://firmware.center/firmware/Motorola/Moto X (2nd gen-2014)/Stock/XT1095/
It's a fastboot flash, so you have to extract the zip and put the files in the directory where your adb and fastboot are. Open a command window in that folder and https://www.youtube.com/watch?v=kS0eVAfpBIo
Flipz77 said:
https://firmware.center/firmware/Motorola/Moto X (2nd gen-2014)/Stock/XT1095/
It's a fastboot flash, so you have to extract the zip and put the files in the directory where your adb and fastboot are. Open a command window in that folder and https://www.youtube.com/watch?v=kS0eVAfpBIo
Click to expand...
Click to collapse
Thanks! This did the trick.
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.
Trying to root my Pixel 3aXL with LineageOS 17.
I tried to install Magisk following this guide https://magisk.download/root-pixel-3a-3a-xl/
I am stuck in Fastboot now.
''bootslot: b
enter reason: error boot prepare''
SOLVED
dadu1257 said:
Trying to root my Pixel 3aXL with LineageOS 17.
I tried to install Magisk following this guide https://magisk.download/root-pixel-3a-3a-xl/
I am stuck in Fastboot now.
''bootslot: b
enter reason: error boot prepare''
Click to expand...
Click to collapse
What the heck, this one was tuff. There were really less documentation and disinformation around.
So the situation is: How do I get Magisk Root on LineageOS 17?
- Do NOT use the ''stock'' boot.img as said in the magisk official tutorial for my phone. Since you have your Custom ROM you want your boot.img from your specific LineagaeOS (don't look for ''custom boot.img for lineage'' you can find here and there.)
- To get the right boot.img check your LIneageOS installation folder, unzip and look for ''payload.bin''.
- Extracting payload.bin to get boot.img doesnt work with 7zip. For me these steps worked well. When you have the right boot.img you can just follow the guide on magisk for your phone.
Get Payloader Dumber (github)
Get/Install Python (customize installation folder to an accessible place)
Extract Payload Dumper to Python Folder
Copy Payload.bin File from your CustomROM to Python Folder
Open Command Prompt there
Run "python -m pip install -r requirements.txt"
Run "python payload_dumper.py payload.bin"
Voila
(taken from https://www.youtube.com/watch?v=L4AGMqJStEI)
Hope this helps
dadu1257 said:
- Do NOT use the ''stock'' boot.img as said in the magisk official tutorial for my phone. Since you have your Custom ROM you want your boot.img from your specific LineagaeOS (don't look for ''custom boot.img for lineage'' you can find here and there.)
Click to expand...
Click to collapse
Great that you got it solved, but I just want to add a clarification:
The "stock" boot image file that the instructions talk about is simply the untouched (stock) boot image of whatever ROM you are currently using. The instructions even mention that you should extract it from your ROM zip if using a custom ROM...
:good: