Related
THIS THEME IS ONLY FOR THE BELL ATRIX. IT REQUIRES YOU TO HAVE A DEODEXED SYSTEM.
Disclaimer: I am not responsible for any softbricking that may happen to your device. I have tested it on my phone only.
I am releasing a Gingerbread theme I made for the Bell Atrix . Please let me know if you find any bugs that I haven't so far.
The next version will have the carrier removed from the notification bar, but for now its just invisible because of the black text.
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"
}
Download:
CWM install zip (OLYEM U4 1.4.2):
BellGingerbread1.3-CWM.zip
Manual install files (OLYEM U4 1.4.2):
BellGingerbread-V1.3.zip
_________________________________________
Old Versions (Bell 0.37.4):
BellGingerbread-V1.2(with scripts).zip
Installation:
First you need to have deodexed your system files. This can be done by following the instructions in this thread:
[script][SCRIPT] OLYEM_U4 1.4.2 Telstra/Bell FULL Deodex for OLYEM 1.4.2
OR
[script] Deodexed files for Bell for Bell 0.37.4.
CWM
1. Download the CWM zip
2. Place the still compressed zip onto your SD card
3. Boot into recovery and install zip
Manual
1. Download the manual files package and extract it
2. Put the files from the install files directory in the root directory of your SD card
3. Run this code in ADB
Code:
adb shell
su
mount -o rw,remount /dev/block/mmcblk0p12 /system
cp -f /sdcard/framework-res.apk /system/framework/
cp -f /sdcard/services.jar /system/framework/
cp -f /sdcard/blur-res.apk /system/framework/
sync
reboot
Uninstall:
For CWM method:
1. Download the CWM backup BellGingerbread1.3-CWM-BACKUP.zip
2. Follow instructions for CWM install but use the backup zip
For manual method:
1. Download backup files BackupFilesBell-OLYEM1.4.2.zip
2. Follow instructions from the manual install but use the backup files
For install script (V1.2 Only):
1. Run RESTORE.BAT
Extras:
Gingerbread Keyboard: [MOD] Gingerbread Keyboard on Atrix!
Nexus Boot Animation (Much better then the Telstra one):
1. Download the bootanimation.zip
2. Put the bootanimation.zip in the root directory of your SD card
3. Run this code in ADB
Code:
adb shell
su
mount -o rw,remount /dev/block/mmcblk0p12 /system
cp -f /sdcard/bootanimation.zip /system/media/
sync
reboot
Chnagelog:
1.3 (Newest Version)
- OLYEM U4 1.4.2 Support
- Darker notification pulldown
1.2
- Added transparent notification pulldown
- Removed lock screen animation
1.1
- Added Gingerbread animations
1.0
-Original Release
Cool, I like. Are you planning on maybe making a couple different themes too?
Sent from my MB860 using XDA App
Thank you soo much! I have been waiting for something to start happening with the bell atrix's.
3 requests which im not sure are possible...
-different animations
-gingerbread screen off animation (looks like turning of a tv)
-power controls in pulldown menu??
Keep it up. Gonna try this as soon as i get home. Im assuming there is a thread on how to deodex system.
For now I'm going to keep working on this theme, maybe I'll make more later. I'm adding animations in the next version which should be out soon, and I am looking into the power controls in the notifications menu. Unfortunately its not possible to get the shutoff animation, I liked it a lot on my Desire Z, but that was actually running gingerbread.
script please or CWM
would you be able to make a script for this theme or a CWM update.zip for easy installation thanks and keep up the good work. im so happy that someone is finally creating something for the bell atrix.
Silent8Strike said:
For now I'm going to keep working on this theme, maybe I'll make more later. I'm adding animations in the next version which should be out soon, and I am looking into the power controls in the notifications menu. Unfortunately its not possible to get the shutoff animation, I liked it a lot on my Desire Z, but that was actually running gingerbread.
Click to expand...
Click to collapse
alright, i look forward to it
erik10002 said:
would you be able to make a script for this theme or a CWM update.zip for easy installation thanks and keep up the good work. im so happy that someone is finally creating something for the bell atrix.
Click to expand...
Click to collapse
i don't know what the OP's plan are, but i'd be happy to throw together a script that can do this for everyone
i haven't messed around making CWM stuff yet, so i can't promise anything there, but probably later tonight i'll post a script that can do this
we need more devs like you guys. gives me confidence in the community. Keep up the good work.
raybond25 said:
i don't know what the OP's plan are, but i'd be happy to throw together a script that can do this for everyone
i haven't messed around making CWM stuff yet, so i can't promise anything there, but probably later tonight i'll post a script that can do this
Click to expand...
Click to collapse
that would be awesome, i tried to do it through adb this morning but wasn't working for me and a script makes installing anything a heck of a lot easier.
also i have [THEME] Black Bar Bell. (Gingerbread) by toughbax on my phone, will there be any problems installing this over it?
thanks
Im gonna try the zip tonight. No rush but you think it will be up tonight?
erik10002 said:
that would be awesome, i tried to do it through adb this morning but wasn't working for me and a script makes installing anything a heck of a lot easier.
also i have [THEME] Black Bar Bell. (Gingerbread) by toughbax on my phone, will there be any problems installing this over it?
thanks
Click to expand...
Click to collapse
No, there will be no problems installing over, because you completely replace both files that are used to create the other theme. The script will be up around 10 tonight probably, got a bunch of things to do at school tonight.
Sent from my MB860 using XDA App
blunted09 said:
Im gonna try the zip tonight. No rush but you think it will be up tonight?
Click to expand...
Click to collapse
I won't upload a flashable .zip for use with cwm because I don't know how, maybe in the future, just not tonight. However, I will be uploading a .bat file later tonight around 10, so you will just be able to run that off of your pc.
Sent from my MB860 using XDA App
Awesome, I will wait for the bat file and try it tonight. Thanks again.
Sent from my MB860 using XDA Premium App
I'll see what I can do about making a zip to flash in cwm tonight when I get home from work in a few hours.
Silent8Strike said:
I'll see what I can do about making a zip to flash in cwm tonight when I get home from work in a few hours.
Click to expand...
Click to collapse
well, i just got a script working, and it makes a backup for the user too, i'm just about to make a recovery script that will restore the backup to the device, just in case the user doesn't like the theme, or if something happens to make it brick
i soft-bricked myself once because i made an absolutely retarded typo in my script the first time, and copied the files to the wrong directory, lmfao. that's fixed now obviously
raybond25 said:
well, i just got a script working, and it makes a backup for the user too, i'm just about to make a recovery script that will restore the backup to the device, just in case the user doesn't like the theme, or if something happens to make it brick
i soft-bricked myself once because i made an absolutely retarded typo in my script the first time, and copied the files to the wrong directory, lmfao. that's fixed now obviously
Click to expand...
Click to collapse
ALL DONE - install script will create a backup of your current (soon to be old) theme before installing new theme. Restore script will re-install your old theme to your device.
MUST BE DEODEXED STILL, JUST BECAUSE ITS A SCRIPT DOESN'T CHANGE THAT.
*NOTE* if the script runs through and says "Device not found" under everything, its probably because USB debugging got interrupted. I ran into this a whole bunch of times, and ran into device not found a few, but whenever that happens, if you simply run the script again right after, it will work (has been replicated by myself).
If you run into any problems further than that easily fixable one, you're probably not deodexed and rooted. If you have further problems feel free to PM me.
with the new bell SBF that was leaked will this still work? thanks
raybond25 said:
ALL DONE - install script will create a backup of your current (soon to be old) theme before installing new theme. Restore script will re-install your old theme to your device.
MUST BE DEODEXED STILL, JUST BECAUSE ITS A SCRIPT DOESN'T CHANGE THAT.
*NOTE* if the script runs through and says "Device not found" under everything, its probably because USB debugging got interrupted. I ran into this a whole bunch of times, and ran into device not found a few, but whenever that happens, if you simply run the script again right after, it will work (has been replicated by myself).
If you run into any problems further than that easily fixable one, you're probably not deodexed and rooted. If you have further problems feel free to PM me.
Click to expand...
Click to collapse
thanks man!! so where can i get the script from? i don't see any links
erik10002 said:
with the new bell SBF that was leaked will this still work? thanks
Click to expand...
Click to collapse
to be honest i'm not sure about that .sbf
unless you've already flashed it and can confirm that it works, then i would recommend that your wait until it's confirmed.
also - this will work with the new .sbf provided we can get root for the new Bell firmware. i would suggest waiting until root is completed to update, just so you can keep adding mods like this to it.
and yes - this theme should work on the new sbf, if you're on it and have root access.
aliafi90 said:
thanks man!! so where can i get the script from? i don't see any links
Click to expand...
Click to collapse
yeah, uploading now will edit this post with link in 2mins
EDIT: heres the link
For all you Shotputterz heres the factory image we've been waiting for
assuming you have debug mode enabled, ADB and fastboot working properly
EDIT 1: REUP'D CWM mod
EDIT 2: reordered process to make more sense
Method:
1. Download the Beta CWM mod from rootzwikis credit to birdman EDIT:REUP'ED http://d-h.st/Fdp
2. Using fastboot, DO NOT FLASH Clockwork mod just use the syntax
"fastboot boot 'File path of clockwork mod image'
Note* this will boot directly into the recovery without permanently writing to the recovery and boot partition on the eMMC on the Nexus Qs board
3. Download the posted CWM factory backup posted
4. make the directory on the device and adb push the backup folder (unzipped) to /sdcard/clockworkmod/backup while in CWM recovery
*The device should show up in "adb devices" while in the CWM recovery*
5. *TEXT WILL BE REALLY SMALL! Now navigate with the Scroll wheel to backups and restore and tap the mute button to select.
*IF SOMETHING IS SELECTED IN ERROR THERE IS NO BACK BUTTON JUST REBOOT AND REDO FASTBOOT BOOT*
6. Now select restore and select the image folder
7.blah blah CWM Freaking MAGIC
8. Your Q is back to factory state
If someone wants to PM me or show me how to package this in a nicer CWM zip to install with a script let me know
http://d-h.st/yeo
*Note* I am NOT responsible if you brick your already bricked Nexus Q*
You sir get a beer, since my 2nd (dev) Q won't arrive until later this week, and mine was a shot put until this post.
If you happen to be in NYC before I move to SF, you get three beers.
Hoppy ones.
I am moving to SF
Did the reflash go smoothly?
fiveipads said:
I am moving to SF
Did the reflash go smoothly?
Click to expand...
Click to collapse
No unfortunately it didn't--I blew away all partitions other than bootloader so I can't, to my knowledge at least, push the zip since I can't adb.
I've got factory recovery, boot, system imgs but the system img won't push out because of fastboot's apparent inability to handle files that large (1GB exactly I believe).
...I guess I have to patiently await my second Q but the point of having two was to *use* one and have one for dev... rather than have one as a heavy reminder of my overzealous endeavors...
Hopefully I can give it more time while on this SF trip...
Boot into the cwm bootloader with fastboot without flashing. Adb will be enabled and you can push files the files while your in adb recovery. Try that and flash it.
Sent from my SPH-D710 using xda app-developers app
Does our Q's have internal memory.. if not wouldn't it be possible to run back up of off otg memory stick if recovery would support it
Sent from my Galaxy Nexus using xda premium
fiveipads said:
Boot into the cwm bootloader with fastboot without flashing. Adb will be enabled and you can push files the files while your in adb recovery. Try that and flash it.
Sent from my SPH-D710 using xda app-developers app
Click to expand...
Click to collapse
The problem I'm having is that ADB is not responding from CWM... at least not on a Windows machine. The drivers are fine as ADB was working in normal mode before my issue sprung up.
EDIT: As suspected Virtual Ubuntu on a Win host didn't see the device, Physical Ubuntu had no issue. NQ reloaded.
fiveipads said:
Boot into the cwm bootloader with fastboot without flashing. Adb will be enabled and you can push files the files while your in adb recovery. Try that and flash it.
Sent from my SPH-D710 using xda app-developers app
Click to expand...
Click to collapse
Can we do this by say pushing the file to the download folder and then installing from zip?
And i know slightly off topic but once we've installed some apks for example, what's currently the best interface to use to navigate through the apps and use them?
How do I make a directory on Nexus Q
fiveipads said:
For all you Shotputterz heres the factory image we've been waiting for
assuming you have debug mode enabled, ADB and fastboot working properly
Method:
1. Download the posted CWM factory backup posted
2. make the directory on the device and adb push the backup folder (unzipped) to /sdcard/clockworkmod/backup
http://d-h.st/yeo
Click to expand...
Click to collapse
In step 2 you say make a directory for the file that is posted below. How do I create a directory on the Nexus Q? Currently my Q is stuck in a bootloop after trying to launch CWM from a Galaxy Nexus. If you could post command codes that would be awesome!
I figured it out. You can just follow step #4 and in CWM you can push the CWM Factory img to the /sdcard/Download/ folder and use CWM to unzip and launch.
Could someone please provide me the beta cwm image for Nexus Q? The links are all circular and point to
http://goo.im/devs/birdman/CWM-steelhead-beta.img
Which is dead...
discoltk said:
Could someone please provide me the beta cwm image for Nexus Q? The links are all circular and point to
http://goo.im/devs/birdman/CWM-steelhead-beta.img
Which is dead...
Click to expand...
Click to collapse
I've been trying to get ahold of this image too! Anyone?? anyone?? Bueller???
WildSatchmo said:
I've been trying to get ahold of this image too! Anyone?? anyone?? Bueller???
Click to expand...
Click to collapse
Me as well...not sure why I got this damn thing...lol
The edit didn't prompt an email to me even though I'm following the thread, so those of you looking for the clockworkmod beta image please take note that OP was kind enough to provide a working link to the image.
Thanks fiveipads!
Can someone post full backup please?
caioketo said:
Can someone post full backup please?
Click to expand...
Click to collapse
The link at the bottom still works for me...
http://d-h.st/yeo
..
ok this is really bothering me, i've restored with this factory image several times, and I have to do it again right now and I cannot seem to push this file folder to /sdcard/clockworkmod/backup
what am i doing wrong..
it should be:
adb push NexusQFactoryImage /sdcard/clockworkmod/backup/ (assuming the file is in same folder as adb which it is)
that's it right.... the extracted folder contents in a folder.. not the zip.. so i dont understand why this is not working. Everytime I go to CWM and try to restore it tells me nothing to restore...
what really bothers me is that i've done this a hundred times, and never had this problem..
UKROB86 said:
ok this is really bothering me, i've restored with this factory image several times, and I have to do it again right now and I cannot seem to push this file folder to /sdcard/clockworkmod/backup
what am i doing wrong..
it should be:
adb push NexusQFactoryImage /sdcard/clockworkmod/backup/ (assuming the file is in same folder as adb which it is)
that's it right.... the extracted folder contents in a folder.. not the zip.. so i dont understand why this is not working. Everytime I go to CWM and try to restore it tells me nothing to restore...
what really bothers me is that i've done this a hundred times, and never had this problem..
Click to expand...
Click to collapse
BUMP.. stuck in CWM unable to get a restorable file.. no idea why...
Download OneClickRestore (it's the factory image straight from Google with the needed fastboot files included)
Extract zip to OneClickRestore
Unplug Nexus Q
Plug in Nexus Q and place hand on it til the leds turn red then remove hand
Launch "flash-all.bat" from the OneClickRestore folder
You may need to do a full reset, it's hit or miss
Another option is push & flash (Nexus Q)uantum Singularity Project RTS ROM from CWM and again may need to hard reset.
RTS is
Based on stock 4.0.4 build IAN67K
Deodexed
Zip aligned
init.d Support
bash support
Busybox updated
Prerooted
Superuser
Updated Keymap (Home=Home, End=Back, Delete=Menu, Insert=Visualizer)
Lokifish Marz said:
Download OneClickRestore (it's the factory image straight from Google with the needed fastboot files included)
Extract zip to OneClickRestore
Unplug Nexus Q
Plug in Nexus Q and place hand on it til the leds turn red then remove hand
Launch "flash-all.bat" from the OneClickRestore folder
You may need to do a full reset, it's hit or miss
Another option is push & flash (Nexus Q)uantum Singularity Project RTS ROM from CWM and again may need to hard reset.
RTS is
Based on stock 4.0.4 build IAN67K
Deodexed
Zip aligned
init.d Support
bash support
Busybox updated
Prerooted
Superuser
Updated Keymap (Home=Home, End=Back, Delete=Menu, Insert=Visualizer)
Click to expand...
Click to collapse
The problem with putting Quantum singularity project on is that I can't turn on ADB debug, because i use a bluetooth mouse and keyboard, don't have an OTG mouse/keyboard, so somehow I need to be able to connect with adb to setup a bluetooth connected mouse/keyboard
I was thinking to install stock image, and then without wiping install Quantum SIngularity Project over top to preserve the settings for usb debug, on.
what's confusing to me is that i've restored the stock image many times before, and never had a problem.. that's why im wondering what the problem is.. if im typing something wrong.
I used the OneClickRestore as you said, and im just booting it up now
EDIT: didn't get past boot logo, i'll try again
So just to confirm this OneClickRestore is loading the stock nexus Q img right? I've never used it before I usually manually do it
EDIT: still stuck at the nexus q logo before home screen
do you see any error in my commands of trying to push the stock img folder (original post) to "/sdcard/clockworkmod/backup" ? I've done it many times before never had a problem
The Short Directions
download DroidX2_Root_2012.exe
(self extracting batch file)
watch the video By: Tomsgt
turn phone on
phone- enable usb debugging (menu/system settings/apps/developer options)
connect phone to pc
phone- change usb mode to charge only or pc mode (pull down from top notification bar
pc- start program, (click on DroidX2_Root_2012.exe)
just follow on screen instructions
these are the details, but most is click enter on keyboard
a file is pushed to your phone with adb
phone will reboot to fastboot, all you will see on phone is moto boot logo dualcore screen
click enter on pc
two files will be flashed to phone
phone will reboot
when it has completed reboot
click enter on pc
phone will reboot again
when phone has completed reboot
click enter on pc
files will be pushed to phone with adb
phone will reboot
phone will reboot to android recovery
press both volume buttons when you see ! in a triangle with android andy
wipe cache using volume buttons to scroll, select with power button
when complete, select reboot with power button
Done.
if you want to know more, see the other options, read info below
bhigham/beh and I have modified root method
based on New root method for stock 2.3.4 (621/622) found (Droid2, R2D2)
5 Options
a self extracting batch file Mirror: DevDB backup - 2021
regular batch file
linux/slitaz boot image file, (like ezSBF) Mirror: DevDB backup -2021
manual using adb/moto-fastboot
Voodoo method uses 2.3.4 sbf and other rooting method
I have tested and they work
Watch Video
By: Tomsgt
How this works
phifc said:
There's an exploit in loadpreinstall.sh. It compares md5 sum files of preinstalled apps and if they're different, copies the md5 to the local cache. The preinstall just has an empty file in app/ so it will parse the md5 for it. Instead of an md5 sum, it contains a local.prop that allows adb root shell. So the system thinks it's copying the md5sum to the cache when it bounces off the symlink and overwrites the /data/local.prop, giving adb root on next reboot
Click to expand...
Click to collapse
Basic Instructions/steps for Batch files and Slitaz
first you need to be on 2.3.5/1.3.418
VRZ_MB870_4.5.1A-DTN-200-18_1FF_01.sbf (not .zip) MD5 Sum: 2F746145401FA9E921C1DEC2339A473E
SBF and update.zip here http://forum.xda-developers.com/showthread.php?t=1703640
moto drivers need to be installed (for batch root only)
turn phone on
enable usb debugging (system/apps/developer options)
connect to pc
change usb mode to charge only or pc mode
start program, see instructions specified with the option you chose
there are on screen instruction, but this is what will happen
a file is pushed to your phone with adb
phone will reboot to fastboot, all you will see on phone is moto boot logo dualcore screen
click enter
two files will be flashed to phone
phone will reboot
when it has completed reboot
click enter
phone will reboot
when phone has completed reboot
click enter
files will be pushed to phone with adb
phone will reboot
when phone has completed reboot
click enter
files will be pushed to phone with adb
phone will reboot to recovery
press both volume buttons when you see ! in a triangle with android andy
wipe cache using volume buttons to scroll, select with power button
when complete, select reboot with power button
Done.
when running the batch file or slitaz you may see these errors
rm failed for /data/preinstall_md5/magic.md5 no such file or directory
no root.img.gz no such file or directory
rm failed for /data/preinstall_md5/magic.md5 read only file system
that is fine, it will still work
and bsr/system recovery will be installed
Root DX2 2.3.5 batch file in self extracting exe
DroidX2_Root_2012.exe
download
double click on DroidX2_Root_2012.exe to start
follow onscreen instructions
note: first reboot, goes to a nonlabeled fastboot mode, all you will see is moto boot logo dualcore screen just click enter to flash files
Root DX2 2.3.5 batch file
DX2_Batchroot.7z
download file
extract with 7zip
double click on rootdx2.bat to start
follow onscreen instructions
note: first reboot, goes to a nonlabeled fastboot mode, all you will see is moto boot logo dualcore screen
slitaz boot img, like ezSBF
Droid2_D2G_DX_DX2-RootCD-2012.iso
has options for D2, D2G, DX, and DX2
1KDS said:
Don't let the word Linux scare you, this is just a cd you burn, nothing installs to your pc. Once you burn this CD you are ready to SBF flash anywhere you have a computer, no net connection needed to download any files.
This is an .iso file. It is a complete Linux operating system that you will download, burn to CD (or USB) then boot your pc from CD or USB, this allows your pc to reboot into a different operating system.
Click to expand...
Click to collapse
1KDS said:
Instructions (Mac):
Download .iso
Use Disk Utility (built in) to burn iso file to a CD (instructions)
Shut computer down
Hold c key, push power and hold c until you see the Linux OS start
Hit enter at the yellow "boot baby... boot" screen
You will see yellow dots for 3-5 minutes then the script will start
Instructions (Windows):
Download .iso
Burn iso image to a disk (Instructions, Windows 7 - Vista and XP) or (Load to a USB flash drive)
Reboot PC
Hit F12 (sometimes F8 or esc) during boot to go to boot menu (possibly google search how to boot your specific pc from CDROM)
Select boot from CDROM (or USB if you used a flash drive)
Hit enter at the yellow "boot baby... boot" screen
You will see yellow dots for 3-5 minutes then the script will start
Live USB Instructions (Windows):
(Instructions from pendrivelinux.com)(thanks)
Download UNetBootin for Windows
Download your favorite Linux ISO
Double click the Unetbootin Executable to start the program
(1) Click the Diskimage radio box
(2) browse to select your ISO
(3) Set your target USB drive
(4) click OK to start the creation
{
"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"
}
(5) After the USB drive is done select reboot.
(6) During boot enter the boot menu and change USB to boot first, save and reboot.
(7) When booting from UNetbootin select SliTaz
________________________________________________
You will now be in the script and ready to flash.
Click to expand...
Click to collapse
manual method may update this later
you need
moto-fastboot.exe not fastboot.exe found in batch files
adb files found in batch files
Petes root tools http://www.psouza4.com/Droid3/
root.img found in batch files
instructions
extract any .zip or .gz
move all files to same folder like C:root to make it easy
Enable USB debugging on phone
open command prompt
enter
Code:
cd/
cd c:root
adb shell rm /data/preinstall_md5/magic.md5 ( don't worry if you see an error)
adb shell ln -s /data/local.prop /data/preinstall_md5/magic.md5
boot phone to fastboot
run commands
Code:
moto-fastboot.exe flash preinstall root.img
moto-fastboot.exe reboot
let phone boot complete, then reboot again (reboot just replaces the local.prop, but the old local.prop is still in memory, till second reboot)
command
Code:
adb shell
should give you a root prompt # (instead of $)
run petes root tools, zerg rush, or superoneclick
then you rooted
VooDoo Method
1 start with full stock 2.3.4/1.3.380,if you have rooted with anything other than Pete's Root Tools*, have altered/deleted stock file, or if you are already on 2.3.5/1.3.418 you have to SBF
SBF to full stock 2.3.4/1.3.380 (VRZ_MB870_4.5.1A-DTN-150-30_1FF_01.sbf)
read How to SBF an X2, ezSBF DX2, and Common X2 Questions and Answers
if you don't want to lose data, don't wipe data (although it is recommended), unless you bootloop
if you bootloop you have no choice, but to wipe data via stock recovery see Common X2 Questions and Answers
2 Root with Pete's Root Tools
3 install Voodoo OTA Root Keeper, backup su, then temp unroot (keeps backup)
4 install update 2.3.5/1.3.418 , (Blur_Version.1.3.380.MB870.Verizon.en.US.zip)**
a via over the air or
b download, place in sd card root (not in a folder)
md5 B127D3AF93FD6A75C3A3D897C6D0FCD1
and install via stock recovery see Common X2 Questions and Answers
5 restore root with Voodoo
*zergrush may remove stock files, to root, causing update to fail
**updates are named by the version they are updating
md5 checksum windows / android
Magic MD5 Root 2.3.4 for D2, R2D2, D2G, DX and 2.3.5 for DX2 - Google Docs
sd_shadow's [Collection] of Links: FAQs, Guides, Rooting, SBFs, ROMs... - Google Docs
updates
09 aug 12 added video
11 aug 12 edited name to magic md5, added voodoo links
16 Oct 12 new link to Pete's
09 Feb 2013 added clickable link to options files - Google Docs/ reworded some
12 March 2013 moved things around...
27 March 2015 converted thread to DevDB
16 Oct 2021 DevDB Archived new link
16 Oct 2021 Google links no longer working
XDA:DevDB Information
[Root] Droid X2 (MB870) - 2.3.5/1.3.418 magic md5 method, Tool/Utility for the Motorola Droid X2
Contributors
sd_shadow, bhigham, phifc, among others
Version Information
Status: Stable
Created 2015-03-27
Last Updated 2015-03-27
Thank christ, now hopefully some of those older 2.3.4 based roms can be updated. I've been wondering why this has taken so long, glad it's finally out.
They won't be upgraded to this kernel. All the cm based roms are going to stay at 2.3.4 as dzk has said he isn't going to update. And there is only one other currently new ROM and it's already at 2.3.5. Liberty and molten are no longer being developed so they aren't going anywhere.
Sent from my DROID X2 using xda app-developers app
Maximinus I said:
They won't be upgraded to this kernel. All the cm based roms are going to stay at 2.3.4 as dzk has said he isn't going to update. And there is only one other currently new ROM and it's already at 2.3.5. Liberty and molten are no longer being developed so they aren't going anywhere.
Sent from my DROID X2 using xda app-developers app
Click to expand...
Click to collapse
Well then, at least it will make installing Eclipse easier. No more SBF to 2.3.4, root, temp unroot, update, reroot. Now it should just be SBF 2.3.5, root. yay!
thanks for the guide!
Made a video of me doing this if you want to add it to op.
https://www.youtube.com/watch?v=sHVCOkFMYAE&feature=youtube_gdata_player
Sent from my DROID BIONIC using Tapatalk 2
great, will do that
Sent from my DROID2 using xda app-developers app
I've been working on this for 2 days.
I SBF to 2.3.5, then use various methods listed to root it and flash Eclipse. However I lose root, and can't root again. When I try to root Eclipse, root can't be acquired, and no files can be pushed to /system/bin. One more try tonight, then I give up. I'm out of ideas. Can't update and carry root from 2.3.4 with RootKeeper since I don't have service.
Scur827 said:
I've been working on this for 2 days.
I SBF to 2.3.5, then use various methods listed to root it and flash Eclipse. However I lose root, and can't root again. When I try to root Eclipse, root can't be acquired, and no files can be pushed to /system/bin. One more try tonight, then I give up. I'm out of ideas. Can't update and carry root from 2.3.4 with RootKeeper since I don't have service.
Click to expand...
Click to collapse
Use the stock recovery and flash the update from there. Don't need to get the ota. And use root keeper. The update can be found in the link on the op.
Sent from my Nexus 7 using Tapatalk 2
haven't seen this problem, but
you could try removing root files, that are no longer needed
with terminal emulator or adb shell
su
rm /data/preinstall_md5/magic.md5
rm /system/preinstall/md5/magic.md5
rm /system/preinstall/app/magic
Sent from my DROID2 using xda app-developers app
Tomsgt said:
Use the stock recovery and flash the update from there. Don't need to get the ota. And use root keeper. The update can be found in the link on the op.
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
Nope. I can't update from recovery either. My phone is a bit off, I have a wholethread about it.
sd_shadow said:
haven't seen this problem, but
you could try removing root files, that are no longer needed
with terminal emulator or adb shell
su
rm /data/preinstall_md5/magic.md5
rm /system/preinstall/md5/magic.md5
rm /system/preinstall/app/magic
Sent from my DROID2 using xda app-developers app
Click to expand...
Click to collapse
Nope, doesn't help. I'm going through the process manually using adb right now, at it seems to me that after flashing Eclipse the root.img I'm using isn't valid with Eclipse on 2.3.5. Specifically, here's what I'm doing and here's what's happening...
adb shell ln -s /data/local.prop /data/preinstall_md5/magic.md5 (no error)
adb reboot-bootloader (no error)
moto-fastboot flash preinstall root.img (sending 'reinstall'... okay, whiting 'preinstall'... okay)
moto-fastboot reboot (no error)
adb reboot (no error)
adb shell mount -o remount,rw /dev/block/system /system (mount: Operation not permitted)
So, I think the root image doesn't work with something, though I'm still noobish with it all. Maybe I'll try some different ones...
sd_shadow said:
haven't seen this problem, but
you could try removing root files, that are no longer needed
with terminal emulator or adb shell
su
rm /data/preinstall_md5/magic.md5
rm /system/preinstall/md5/magic.md5
rm /system/preinstall/app/magic
Sent from my DROID2 using xda app-developers app
Click to expand...
Click to collapse
The batch file already attempts to remove those files, right before rebooting into recovery to have the cache wiped. So unless something failed in the batch file, those files should already be deleted.
---------- Post added at 08:41 AM ---------- Previous post was at 08:21 AM ----------
Scur827 said:
Nope. I can't update from recovery either. My phone is a bit off, I have a wholethread about it.
Nope, doesn't help. I'm going through the process manually using adb right now, at it seems to me that after flashing Eclipse the root.img I'm using isn't valid with Eclipse on 2.3.5. Specifically, here's what I'm doing and here's what's happening...
adb shell ln -s /data/local.prop /data/preinstall_md5/magic.md5 (no error)
adb reboot-bootloader (no error)
moto-fastboot flash preinstall root.img (sending 'reinstall'... okay, whiting 'preinstall'... okay)
moto-fastboot reboot (no error)
adb reboot (no error)
adb shell mount -o remount,rw /dev/block/system /system (mount: Operation not permitted)
So, I think the root image doesn't work with something, though I'm still noobish with it all. Maybe I'll try some different ones...
Click to expand...
Click to collapse
I have a thought on something that might work, but it will require a bit of work on your part. One of the steps in rooting batch file, is putting the local.prop file back to normal, which no longer gives adb root access.
If you are indeed able to root stock 2.3.5, then here is what I would suggest trying, (but I don't know if the local.prop file will get overwritten by flashing eclipse)
SBF to stock 2.3.5
Root stock 2.3.5 using any method that will work for you.
Install ES File manager
enable root permissions (up to root, root explorer, and possibly mount file system)
go to /data and open up local.prop (ES Note editor works well)
In the allow all adb line, change the 0 to 1, and save the file.
Reboot, and make sure that file still has 1 for allow all adb.
if so, try flashing eclipse, and see if adb shell has root access. If so, then you can push the necessary files to get root.
Don't know if this will work or not, as I am not sure of where the local.prop file actually comes from, so it might get regenerated. But, if you want to try it, you are welcome to.
I checked to see if local.prop would survive an sbf, and it does not, but I am not sure about with a custom rom.
Very good idea, I'll try it tonight.
Droid X2 > Rooted 2.3.45> Tapatalk
Problems getting it to work
Friends, Thanks for taking the time to post these instructions, I love these forums!
I have a question, I have tries to do this twice using the "Root DX2 2.3.5 batch file in self extracting exe"
But have had no luck, as I am still stock (2.3.5. & 1.3.418 MB870)
It fails to push SU to the phone, and give the errors mentioned in the instructions, but root checker tells me I'm still not rooted.
I feel like I have taken my time, and read through the instructions as I went along, but I guess I'm missing something somewhere.
I (we all) have waited a long time for a root method for the DX2, now it looks like we may have one, but I can't get it to work.
I would be thankful for any advice or help given.
Thanks in advance!
wipe cache, before trying again
be sure to let phone finish booting, before pressing continue
after flashing files in fastoot, phone needs to reboot twice
before pushing su
may want to try slitaz boot img
---> Thank you SD_Shadow!
Thanks my friend, SU granted!
Finally!
Thanks again!
.....Happy camper!
great, did you use the slitaz boot image,
or was it not rebooting the 2 times after flashing
It was hanging on the 2nd reboot.
I just let it sit there this time, and it eventually cycled through to completion.
Now I guess I'm going to either nandroid, or buy Titainium Backup (full),
I want to start learning how to flash roms, while keeping my phone safe and secure.
Thanks again for your advice!
PS~Can you offer a short list of essential root tools/apps? Thanks!
titanium, is a must
if you are going to flashing different roms
sms backup +
is good for backing up call log and texts
and a home launcher
like go launcher, launcher pro, or adw launcher there are more
great for restoring apps and widgets icons after flashing a new rom
remember to backup launcher before
try nova launcher, on ics roms
edit: also will want a file manager or root browser with rw (read/write)
lots of them out there, needed to move system file and change permissions
Sent from my DROID X2 using xda premium
Tomsgt said:
Made a video of me doing this if you want to add it to op.
https://www.youtube.com/watch?v=sHVCOkFMYAE&feature=youtube_gdata_player
Sent from my DROID BIONIC using Tapatalk 2
Click to expand...
Click to collapse
WTF why wont this work, hahahaha i yelled that at my laptop
i had this youtube playing in the background and i hear you say
"well we're going to turn on USB debug..."
facepalm....
thank you for the help.
Welcome to SystemRW by lebigmac
This script removes the read-only lock of all partitions embedded in the super partition of your stock firmware. This allows you to debloat all unnecessary system apps, customize your device to your liking and make MIUI run as smooth as silk!
MIUI 12 is great but it's a little bit bloated and some bugs here and there.
Developed on Xiaomi Poco X3 NFC and works like a charm over here!
Visit project thread
{
"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"
}
can it work for vendor too ?
I really want to flash files that request mount system and vendor
@Abdullah.Csit
Yes the script makes all partitions (system, vendor, product...) that are embedded in your super.img read-write-able and adds extra space to them so you can write data to them later. Then it merges these modified partitions back into a single brand new super_fixed.img and flashes it to your device. Works in both custom recovery and in Android operating system.
User data is not affected.
Now it's possible to modify for example the default.prop or the init.rc and make many more customizations to your device if you know what you're doing. Make sure to always back up an important system file before modifying it. This way you can always restore the original file from recovery and remove the bootloop if something goes wrong.
In the worst case scenario you can always flash a new super.img
placeholder
after 2 days long battle with numerous attempts to install Ubuntu on my windows PC I was finally successful, only to find out:
Spoiler: boring, but it happened
- that RW enabling script can't save super image to my phone sdcard (permission denied)
- that I have to make backup of super partition manually and let the RW enabling script "eat that"
- that my phone super partition is somewhat damaged and RW enabling script ended always with error that it can't resize vendor because it is too big (maybe it wasn't really damaged, but I had already flashed RW vendor provided by another user and it somewhat (probably) collided with the tools used)
- that super.img from fastboot version of MIUI ROM can't be used directly with RW enabling script, because for whatever reason it complained, that that is not an super image
- that I have to flash that clean fresh super.img from fastboot version of MIUI ROM via fastboot to my phone with edited flash script (so it doesn't overwrite my data and recovery partition) and make a backup of it in recovery
- and that backup of clean fresh flashed super.img from fastboot version of MIUI ROM of was finally accepted by RW enabling script, that did it magic, only to find out:
- that final flashing process of fixed super.img to my phone freeze at third section from all seven (now there I was really afraid that my EMMC died because of extensive flashing)
Was that all Mr. Murphy?
- so I had excellent idea that I can obviously use my recovery to flash that fixed super image, easiest thing in the world, right?
- but Ubuntu and Mr. Murphy proved me wrong, because I was able to copy on my phone storage/sdcard anything but that fixed super.img (don't ask me why it didn't even started copying, I'm no Linux user, and that MTP error was pretty alien to me)
- so I had to somehow copy that fixed super.img from newly created Linux space to my Windows space, from where I was so sure I can finally transfer it to my phone internal memory and finally have flashed it where it belongs
- but anything that I writed in Ubuntu to my Windows disks mysteriously disappeared after one click on the file (created on Ubuntu) in Windows ()
- thanks to my rented cloud storage somewhere on the internet I was able to upload that fixed super.img (way faster (thanks to my very fast optic line) than any other solution available to me at that time)
- after reboot to Windows downloaded it and finally was able to upload to my phone from Windows, flash it to super partition via recovery
- and finally re-flashed all need components for my custom ROM and after all that it finally booted into Android
- uff, anyway - it can be done, and it is RW for system, vendor and product
- so thanks @lebigmac for providing possibility
- now we need to persuade TWRP/OFOX maintainers that they can enable again wipe system option (of course it would be only active on RW enabled super partition)
sorry @jeryll that you had to go through so much trouble because I only made Linux only version :/
I am working hard on version 1.15 right now and that should also work for Windows and Mac users as well. I'll try to release it ASAP
To flash the original super.img which you extracted from the Xiaomi fastboot ROM you can simply do:
Code:
fastboot flash super super.img
This should not overwrite your user data.
The good thing about the Poco is it's very forgiving. I must've flashed my super partition at least two dozen times already and it still works like a charm
lebigmac said:
sorry @jeryll that you had to go through so much trouble :/
I am working on version 1.5 right now and that should also work for Windows and Mac users
Click to expand...
Click to collapse
nothing to be sorry for, it was an battle and I won, hopefully new version will be more user friendly + Windows version will be the sweet bonus (for me), thanks again for making this possible
Hey jeryll new universal version available HERE
This should make things easier for the windows and macintosh folks
Today I uploaded the new v1.26 to the project thread
How do you guys like the script so far? Any issues with the Poco X3 NFC? I've only tested it with Android 10 so far but it should also work with Android 11
Hey I recently installed custom rom on my one plus 7t pro(hotdog) . I done it by flashing system, product, boot, etc seperately . When i used your tool it create a super_fixed.bin file . I don't know how to install (I think it is corrupted i tried payload dumper and 7zip to seperate system file from it). What should i do ? Please Help.
Shadirvan said:
Hey I recently install havoc is rom on my one plus 7t pro . I done it by patching system, product, boot, etc seperately . I don't have a super.img how can I convert system to RW without super img
Click to expand...
Click to collapse
I don't have a working twrp for my device
Shadirvan said:
Hey I recently installed custom rom on my one plus 7t pro(hotdog) . I done it by flashing system, product, boot, etc seperately . When i used your tool it create a super_fixed.bin file . I don't know how to install (I think it is corrupted i tried payload dumper and 7zip to seperate system file from it). What should i do ? Please Help.
Click to expand...
Click to collapse
probably experiencing the same thing but whats happening is i cant install anything because for some reason, /system cannot r/w
sorry for bad english
Shadirvan said:
Hey I recently installed custom rom on my one plus 7t pro(hotdog) . I done it by flashing system, product, boot, etc seperately . When i used your tool it create a super_fixed.bin file . I don't know how to install (I think it is corrupted i tried payload dumper and 7zip to seperate system file from it). What should i do ? Please Help.
Click to expand...
Click to collapse
Shadirvan said:
I don't have a working twrp for my device
Click to expand...
Click to collapse
Hi @Shadirvan
It is recommended to always use latest official version of my script (currently v1.32 - new version coming soon!).
Please keep in mind that my SystemRW script was designed for stock firmware and not for custom ROM. Custom ROM's should have r/w capability by default. If your custom ROM doesn't offer this functionality straight out of the box then you should rethink why you even installed it in the first place. Just my 2 ¢
I cannot tell you what you should or shouldn't do but I can tell you what you can do:
You can manually flash super_fixed.bin to your super partition like this:
Bash:
adb reboot bootloader
fastboot flash super super_fixed.bin
Please report back your results. Good luck!
davepayra said:
probably experiencing the same thing but whats happening is i cant install anything because for some reason, /system cannot r/w
sorry for bad english
Click to expand...
Click to collapse
Hello @davepayra
Please tell me more about your device and send me your log files from script folder at
/data/local/tmp/systemrw_1.32/log/
And you can send me some screenshots to better illustrate what you are talking about.
Thanks.
lebigmac said:
Hi @Shadirvan
It is always recommended to use latest version of my script (currently v1.32 - new version coming soon!).
Please keep in mind that my SystemRW script was designed for stock firmware and not for custom ROM. Custom ROM's should have r/w capability by default. If your custom ROM doesn't offer this functionality straight out of the box then you should rethink why you even installed it in the first place. Just my 2 ¢
I cannot tell you what you should or shouldn't do but I can tell you what you can do:
You can manually flash super_fixed.bin to your super partition like this:
Bash:
adb reboot bootloader
fastboot flash super super_fixed.bin
Please report back your results. Good luck!
Hello @davepayra
Please tell me more about your device and send me your log files from script folder at
/data/local/tmp/systemrw_1.32/log/
And you can send me some screenshots to better illustrate what you are talking about.
Thanks.
Click to expand...
Click to collapse
hi, i have a few questions because i did something wrong about installing custom rom
1. is there any way i can flash corvus os again because it says error 1: cant install zip file?
2. is there a possibility that my twrp version prevents me to r/w in system partition?
3. if ever my system partition doesn't have os installed, should i first install vendor image, then proceed to custom recovery to install corvus os (if vendor image enables writing on system partition because ive read a thread that says by reflashing broken firmware, all partitions can return to their normal state and continue r/w in system partition)
davepayra said:
hi, i have a few questions because i did something wrong about installing custom rom
1. is there any way i can flash corvus os again because it says error 1: cant install zip file?
2. is there a possibility that my twrp version prevents me to r/w in system partition?
3. if ever my system partition doesn't have os installed, should i first install vendor image, then proceed to custom recovery to install corvus os (if vendor image enables writing on system partition because ive read a thread that says by reflashing broken firmware, all partitions can return to their normal state and continue r/w in system partition)
Click to expand...
Click to collapse
Hi. I would suggest you install official stock firmware on your device. Check your device subforum here at XDA on how to do this. Then afterwards you can try my script if you want to make your device fully read/write-able. Good luck!
lebigmac said:
Hi. I would suggest you install official stock firmware on your device. Check your device subforum here at XDA on how to do this. Then afterwards you can try my script if you want to make your device fully read/write-able. Good luck!
Click to expand...
Click to collapse
thankyou sir. i will do that. best wishes to me
after doing this sir, do i have to unlock my bootloader again to flash custom rom or there is no other way?
also, will i be able to keep my twrp or should i still flash it again?
What an immaculate, well written and commented script! Easy to know what it does and why.
Worked a treat on my rog 5s pro.
Thread has been closed! The account of the author of this thread has been permanently suspended. Please, I ask everybody not to promote a banned user or his website, blog, work etc on XDA. Thanks very much for your cooperation.
Regards
Oswald Boelcke
Senior Moderator
EDIT: The latest update to Newflasher (v52) built in the functionality to keep user data intact as a prompt while flashing.
Version 52 is out!
- version 52 (01.10.2021)
Implemented userprompt for keeping userdata, thanks @OhayouBaka for figuring out! Removed bootloader log retrieval
In short explanation all files marked with NOERASE inside update.xml is in relation to factory reset, so skiping files marked with NOERASE preserves userdata while flashing. Thanks OhayouBaka for figuring that out! Now newflasher have yes no promp for keeping userdata or making clean installation with factory reset. Bootloader log is removed since I found nothing usefull there.
Click to expand...
Click to collapse
As some people here who have owned previous Xperia devices may already know, to keep data while flashing firmware in Newflasher, you have to delete the userdata.sin file in the firmware folder.
However on the Xperia 1 III, this has changed.
If you only delete userdata.sin, your data partition will be corrupt and you will be forced to factory reset and lose all your data.
To prevent this from happening, not only do you have to delete userdata.sin, but also appslog.sin, diag.sin and metadata.sin from the firmware folder as well.
Found this by checking the update.xml file in the firmware folder, all required sin files to delete are listed as "<NOERASE>".
Unfortunately I had to learn this the hard way, but hopefully this post will save Xperia 1 III owners in the future from accidentally being forced to factory reset their devices when using Newflasher.
If you need the full instructions on flashing firmware that this guide compliments, check this thread: https://forum.xda-developers.com/t/flashing-a-xperia-1-iii-without-unlocking.4326235/
OhayouBaka said:
As some people here who have owned previous Xperia devices may already know, to keep data while flashing firmware in Newflasher, you have to delete the userdata.sin file in the firmware folder.
However on the Xperia 1 III, this has changed.
If you only delete userdata.sin, your data partition will be corrupt and you will be forced to factory reset and lose all your data.
To prevent this from happening, not only do you have to delete userdata.sin, but also appslog.sin, diag.sin and metadata.sin from the firmware folder as well.
Found this by checking the update.xml file in the firmware folder, all required sin files to delete are listed as "<NOERASE>".
Unfortunately I had to learn this the hard way, but hopefully this post will save Xperia 1 III owners in the future from accidentally being forced to factory reset their devices when using Newflasher.
If you need the full instructions on flashing firmware that this guide compliments, check this thread: https://forum.xda-developers.com/t/flashing-a-xperia-1-iii-without-unlocking.4326235/
Click to expand...
Click to collapse
First of all, thank you very much for this research.
If i understood right, i can update device this way and it will be essentially the same as updating the device via OTA, right ?
DennisDD78 said:
First of all, thank you very much for this research.
If i understood right, i can update device this way and it will be essentially the same as updating the device via OTA, right ?
Click to expand...
Click to collapse
I believe so, all your data, apps, etc will still stay as it was before the update.
OhayouBaka said:
I believe so, all your data, apps, etc will still stay as it was before the update.
Click to expand...
Click to collapse
And all system settings should remain ?
By the way, just wanted to clearify something, you mentioned about update.xml file in the firmware folder, should i edit it somehow before flashing, or just delete those four files from f/w folder ?
DennisDD78 said:
And all system settings should remain ?
By the way, just wanted to clearify something, you mentioned about update.xml file in the firmware folder, should i edit it somehow before flashing, or just delete those four files from f/w folder ?
Click to expand...
Click to collapse
Yeah system settings will remain too. Just leave update.xml alone, dont delete it. Only delete the four files that I mentioned from the f/w folder.
OhayouBaka said:
Yeah system settings will remain too. Just leave update.xml alone, dont delete it. Only delete the four files that I mentioned from the f/w folder.
Click to expand...
Click to collapse
Thank you, dear friend!
Much appreciated to your help. Just flash mine back to latest factory firmware to receive OTA and everything looks fine for now. System settings and installed app data are saved with no problem.
so I had to jump through a few threads to figure out the details on how to update a magisk rooted x1m3 to the latest firmware without wiping(dirty flash). Figured I'd write out the steps here for others benefits
1 - download the firmware with Xperifirm
2 - download newflasher and extract to the firmware folder
3 - delete the following files from the firmware folder for no wipe dirty flash - userdata.sin, appslog.sin, diag.sin and metadata.sin. Skip this step if you're using Newflasher v52 and above
4 - download UnSin and extract to the firmware folder
5 - in the firmware folder, drag and drop boot_X-FLASH-ALL-*.sin into unsin.exe, and it will generate a boot_X-FLASH-ALL*.img in the same folder
6 - copy the boot_X-FLASH-ALL*.img onto your phone's sdcard somewhere.
7 - using magisk manager, install magisk and use the "select and patch a file" method. Select the boot_X-FLASH-All*.img file. This will generate a magisk_patched*.img onto your phone's sdcard
8 - download and extract platform-tools. Copy the magisk_patched*.img file from your phone's sdcard into the platform-tools folder on the computer. Rename the file to simply "magisk_patched.img"
9 - back up the phone(since still no real TWRP and titanium backup has been broken for a long time, I've been using Swift Backup)
10 - shut down the phone, plug in a usb-c cable to the computer, then while holding the volume DOWN button, plug in the usb-c cable to the phone. The LED indicator should be GREEN indicating FLASHMODE
11 - open up cmd prompt, and navigate to the firmware folder from step 1. Type in the following command
Code:
newflasher set_active:a
then hit enter. You should see result like this
{
"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"
}
12 - in windows explorer, navigate to the firmware folder, and double click on newflasher.exe(phone should still be in FLASHMODE). Respond to the prompts - n gordongate, p power off, n trim
13 - wait for the flashing of the new firmware to finish
14 - disconnect the phone from the usb cable, and power it back up. Check and make sure you have all your data/apps/etc. At this point it should boot into the rom just fine, but won't have root access and magisk will show that its not installed
15 - power off the phone again. This time, press the volume UP button while plugging in the USB-C cable. LED indicator should be BLUE for FASTBOOT
16 - open up a new cmd prompt, navigate to the platform-tools folder. Type
Code:
fastboot devices
and hit enter to confirm your phone is connected. Should respond with an alphanumeric number and the term fastboot
17 - type the following commands into cmd prompt
Code:
fastboot flash boot_a magisk_patched.img
fastboot flash boot_b magisk_patched.img
fastboot reboot
18 - DONE. Your phone should be on the new firmware with root and all your data/apps/etc
props to @Miustone, @OhayouBaka, @Forbesii for the original instructions. I just sort of put it all in one place
fingers crossed a great dev will come along and give us TWRP soon!
Does r / o and r / w work in Root Explorer?
Edited the original post to include the info that Newflasher has been updated with this functionality built in.
Hi, is there any way I can unlock the /system partition?
Does this allow us to mount the system partition as R/W?
largo2 said:
Hi, is there any way I can unlock the /system partition?
Does this allow us to mount the system partition as R/W?
Click to expand...
Click to collapse
With root only, i guess.
DennisDD78 said:
With root only, i guess.
Click to expand...
Click to collapse
Hello, of course my Xperia 1 iii is root.
Sorry, I'm using Google Translate
Sure wish there was a delete post button. It's a forum and I can't delete my own posts. Way to go, internet.
HowDoIVoIP said:
tony, I appreciate the guide but having never rooted or flashed a sony device, can I follow your guide to a T or do I sort of have to follow the main guide by Miustone as well as yours?
For example, he mentions installing "Fastboot" and "Flashmode" drivers by rebooting Windows 10 and installing them with Driver Signature Enforcement disabled. You didn't mention this, so I'm just trying to determine if I need to sort of follow both guides.
Click to expand...
Click to collapse
tonysunshine said:
so I had to jump through a few threads to figure out the details on how to update a magisk rooted x1m3 to the latest firmware without wiping(dirty flash). Figured I'd write out the steps here for others benefits
1 - download the firmware with Xperifirm
2 - download newflasher and extract to the firmware folder
3 - delete the following files from the firmware folder for no wipe dirty flash - userdata.sin, appslog.sin, diag.sin and metadata.sin. Skip this step if you're using Newflasher v52 and above
4 - download UnSin and extract to the firmware folder
5 - in the firmware folder, drag and drop boot_X-FLASH-ALL-*.sin into unsin.exe, and it will generate a boot_X-FLASH-ALL*.img in the same folder
6 - copy the boot_X-FLASH-ALL*.img onto your phone's sdcard somewhere.
7 - using magisk manager, install magisk and use the "select and patch a file" method. Select the boot_X-FLASH-All*.img file. This will generate a magisk_patched*.img onto your phone's sdcard
8 - download and extract platform-tools. Copy the magisk_patched*.img file from your phone's sdcard into the platform-tools folder on the computer. Rename the file to simply "magisk_patched.img"
9 - back up the phone
10 - shut down the phone, plug in a usb-c cable to the computer, then while holding the volume DOWN button, plug in the usb-c cable to the phone. The LED indicator should be GREEN indicating FLASHMODE
11 - open up cmd prompt, and navigate to the firmware folder from step 1. Type in the following command
Code:
newflasher set_active:a
then hit enter. You should see result like this
View attachment 5423107
12 - in windows explorer, navigate to the firmware folder, and double click on newflasher.exe(phone should still be in FLASHMODE). Respond to the prompts - n gordongate, p power off, n trim
13 - wait for the flashing of the new firmware to finish
14 - disconnect the phone from the usb cable, and power it back up. Check and make sure you have all your data/apps/etc. At this point it should boot into the rom just fine, but won't have root access and magisk will show that its not installed
15 - power off the phone again. This time, press the volume UP button while plugging in the USB-C cable. LED indicator should be BLUE for FASTBOOT
16 - open up a new cmd prompt, navigate to the platform-tools folder. Type
Code:
fastboot devices
and hit enter to confirm your phone is connected. Should respond with an alphanumeric number and the term fastboot
17 - type the following commands into cmd prompt
Code:
fastboot flash boot_a magisk_patched.img
fastboot flash boot_b magisk_patched.img
fastboot reboot
18 - DONE. Your phone should be on the new firmware with root and all your data/apps/etc
props to @Miustone, @OhayouBaka, @Forbesii for the original instructions. I just sort of put it all in one place
fingers crossed a great dev will come along and give us TWRP soon!
Click to expand...
Click to collapse
tony, I appreciate the guide but having never rooted or flashed a sony device, can I follow your guide to a T or do I sort of have to follow the main guide [email protected] Miustone as well as yours?
For example, he mentions installing "Fastboot" and "Flashmode" drivers by rebooting Windows 10 and installing them with Driver Signature Enforcement disabled. You didn't mention this, so I'm just trying to determine if I need to sort of follow both guides.
HowDoIVoIP said:
tony, I appreciate the guide but having never rooted or flashed a sony device, can I follow your guide to a T or do I sort of have to follow the main guide [email protected] Miustone as well as yours?
For example, he mentions installing "Fastboot" and "Flashmode" drivers by rebooting Windows 10 and installing them with Driver Signature Enforcement disabled. You didn't mention this, so I'm just trying to determine if I need to sort of follow both guides.
Click to expand...
Click to collapse
Yeah you will want to follow @Miustone 's guide first. I wrote mine assuming the phone has already been bootloader unlocked and rooted and the PC is setup already
tonysunshine said:
Yeah you will want to follow @Miustone 's guide first. I wrote mine assuming the phone has already been bootloader unlocked and rooted and the PC is setup already
Click to expand...
Click to collapse
Well thanks anyway, dude. I just followed most of his tutorial through step 4 all the way to fastboot flash boot_b magisk_patched.img
and then I just followed you with fastboot reboot without doing fastboot -w to wipe it. Well, it was wiped anyway. I guess I don't know what I expected. Lost everything and it's still not ****ing rooted - at least according to Youtube Vanced.
Ugh. This blows. We need better instructions. What was the point of flashing exactly when all it did was ERASE everything and not even grant you root?
Now I don't know what to do. I didn't even get to your "newflasher" here because I was following main guide and I stopped at the end of step 4 like like others said. I only wanted root. I didn't want to flash a new ROM.
Edit: Re-installed Magisk and now I can grant superuser. I still think these instructions need to be clearer for those of us who haven't rooted anything in thousands of years.
Unfortunately when you unlock your bootloader it will wipe the phone no matter what.
Will the tutorial in the first post also work on the Xperia Ace 3?
tonysunshine said:
so I had to jump through a few threads to figure out the details on how to update a magisk rooted x1m3 to the latest firmware without wiping(dirty flash). Figured I'd write out the steps here for others benefits
1 - download the firmware with Xperifirm
2 - download newflasher and extract to the firmware folder
3 - delete the following files from the firmware folder for no wipe dirty flash - userdata.sin, appslog.sin, diag.sin and metadata.sin. Skip this step if you're using Newflasher v52 and above
4 - download UnSin and extract to the firmware folder
5 - in the firmware folder, drag and drop boot_X-FLASH-ALL-*.sin into unsin.exe, and it will generate a boot_X-FLASH-ALL*.img in the same folder
6 - copy the boot_X-FLASH-ALL*.img onto your phone's sdcard somewhere.
7 - using magisk manager, install magisk and use the "select and patch a file" method. Select the boot_X-FLASH-All*.img file. This will generate a magisk_patched*.img onto your phone's sdcard
8 - download and extract platform-tools. Copy the magisk_patched*.img file from your phone's sdcard into the platform-tools folder on the computer. Rename the file to simply "magisk_patched.img"
9 - back up the phone(since still no real TWRP and titanium backup has been broken for a long time, I've been using Swift Backup)
10 - shut down the phone, plug in a usb-c cable to the computer, then while holding the volume DOWN button, plug in the usb-c cable to the phone. The LED indicator should be GREEN indicating FLASHMODE
11 - open up cmd prompt, and navigate to the firmware folder from step 1. Type in the following command
Code:
newflasher set_active:a
then hit enter. You should see result like this
View attachment 5423107
12 - in windows explorer, navigate to the firmware folder, and double click on newflasher.exe(phone should still be in FLASHMODE). Respond to the prompts - n gordongate, p power off, n trim
13 - wait for the flashing of the new firmware to finish
14 - disconnect the phone from the usb cable, and power it back up. Check and make sure you have all your data/apps/etc. At this point it should boot into the rom just fine, but won't have root access and magisk will show that its not installed
15 - power off the phone again. This time, press the volume UP button while plugging in the USB-C cable. LED indicator should be BLUE for FASTBOOT
16 - open up a new cmd prompt, navigate to the platform-tools folder. Type
Code:
fastboot devices
and hit enter to confirm your phone is connected. Should respond with an alphanumeric number and the term fastboot
17 - type the following commands into cmd prompt
Code:
fastboot flash boot_a magisk_patched.img
fastboot flash boot_b magisk_patched.img
fastboot reboot
18 - DONE. Your phone should be on the new firmware with root and all your data/apps/etc
props to @Miustone, @OhayouBaka, @Forbesii for the original instructions. I just sort of put it all in one place
fingers crossed a great dev will come along and give us TWRP soon!
Click to expand...
Click to collapse
What about deleting all the .ta files? I think this is a precautionary step so that the bootloader is not messed with in the case that you install an older firmware. My understanding is that if the bootloader is downgraded with those .ta files from older firmware, this will cause a brick.