Files: please go to source (I'm a newbie, can not post a link that I've posted on tinhte.vn). Google search: "CWM và ROOT, cảm nhận Philips s398" tinhte.vn
Translated by Google:
Comments received after the 3-day preliminary purchase: Quite satisfied, configure and monitor rational (in this price range is too good 2.670K), with 2040 mAh battery, but even better to use (2 days with average call heard -Ability, 3G off, read on wifi), however, this is not your battery Xenium as some mistakenly believe.
CWM and ROOT: Due to the new phone, post less, to delve 2 days, rotate enough genre (so people do not have the technology) Root are you new to this. Root with MTK chip is not difficult, but the difficulty is that we can not flash, change through Origin Recovery, so the Root software reports failure. So that is my only had to install custom recovery.
Read the article Readback ROM quite confusing to people outside the majors. I'll share what I've done before on this machine for convenience.
1. Download the file as above, unpack.
2. Run FlashTool.exe. Select Download only mode (default available then)
3. Scatter loading: select the file in the folder scatter Modified CWM (not built anything more or less)
4. Turn off the phone (remove the battery). Plug the USB cable. Click Download in FlashTool. You've finished installing CWM.
5. Now you can use the software automatically Root machines will not be comfortable Failed again. The program automatically with the Root or Unroot is.
Root finished you can learn more by MTKDroidTool Backup original ROM machine. When necessary, Flash back to the original ROM, then flash back to the original Recovery is the original machine and then.
One more thing, with a longer warranty, when his need Unroot, the original Flash no one detected. As hard brick machine, not even the Flash ROM (ability death Main) then nobody found out you have a computer or install Custom ROM Root. So there is nothing to fear losing the warranty.
DO IT WITH YOUR OWN RISK
Related
I recently purchased a used Galaxy tab 10.1 I/O, and it had already received the 3.1 OTA update.
Now i want root access for various reasons, and can't seem to find a clear guide on how to do so.. I've found plenty about how to do so on the original 3.0 rom, and that it will carry through the 3.1 update, or for the regular version Galaxy Tab 10.1, but it's my understanding the ROMs were fairly different between the I/O and the retail version and that attempting to cross-pollinate root methods may not be a good idea
although I've rooted and ROMed my fair share of HTC devices and Nooks i'm a little more apprehensive with this unit, as it's my first android device to lack an SD card slot of some sort, so bricking seems like a much worse possibility
The best guide ever is in the development section, it works for your device.
http://forum.xda-developers.com/showthread.php?t=1239185
follow the guide its very easy and worked fine for me
I Return triumphant, and gentlemen, i must say you were incorrect.
The I/O edition does not give you the option to access recovery at any point, even with the Pwr+VOL DN boot.
You can put it into download mode, and certianly use ODIN to install the recovery rom, but you will have no method to actually access recovery to push zip files.
thanks to some quick self education on using fastboot, i was able to root successfully.
To those of you in a similar situation who stumble upon this thread, i invite you to visit:
http://droidbasement.com/db-blog/?p=2439
There you can download CWM in a .img format for use with fastboot.
This link is where you can download fastboot:
http://forum.xda-developers.com/attachment.php?attachmentid=596615&d=1305443483
and you'll need to install PDANet for Android to get the fastboot drivers:
http://junefabrics.com/android/
I belive you'll also need ADB installed from the Android SDK. i do have it installed on this computer, but did not use the ADB command at any point, just fastboot.
Instructions:
1. Download fastboot, PDANet for android, and the recovery image. You'll also need "Samsung_Galaxy_Tab_10.1_root.zip" found in Root.zip from the retail version instructions.
2. Copy the "Samsung_Galaxy_Tab_10.1_root.zip" to the tablet, and and power it off. Disconnect the USB connection
3. Unzip fastboot zip into it's own folder, and then copy your recovery.img file into the same folder.
4. Start the install of PDANet. It will ask you if you want to install drivers about half way through. say yes, and select "Samsung" when the time comes. it will install some drivers and then ask you to try and connect. windows may flare up and say they're unsigned. accept anyway.
5. watch this friendly video on how to start fastboot on your tablet:
http://www.youtube.com/watch?v=sR7vE4IueaU
"fastboot!"
Basically the same as the steps outlined for the retail version, but you will go to the usb icon instead of the box.
6. once the tablet is in fastboot, connect the USB cable. PDA net will recognize it as an ADB connection and try and load itself. it will fail, that's fine. Let the installer exit completely.
7. Open a command line in windows, and get it to the directory fastboot.exe and your recovery image are in.
8. run your fastboot command. i only used it temporarlily, so my command was:
"fastboot boot recovery-cwm_5.0.2.7-sam-tab-10.1.img"
9. the tablet should now boot into the recovery image presented. hooray! follow the remaining instructions from the retail version root, using recovery to load the "Samsung_Galaxy_Tab_10.1_root.zip" and reboot.
10. Once you've done all that, select to reboot. The tablet will reboot. i took the opportunity to disconnect the cable.
11. "Superuser" should now be in your apps, and you're rooted!
Extra Step: Download "Rom Manager" by clockwork from the android market, and install it. from here, opt to flash recovery. Once that's complete, you can now access recovery by launching that program and simply hitting "Reboot into Recovery"
I have no use for this myself but it's not often someone comes back and posts a complete howto on solving their own initial issue. I wish more people would do this. Thanks button clicked.
I just ran into this exact problem and only found this thread after figuring it out on my own. I figured my IO tab just didn't like having clockwork mod installed, but it certainly booted it. I nearly ruined it by accidentally wiping my rom trying to get it to boot at all. I had to repush my install files to the insternal memory using adb after I was able to boot into recovery with fastboot.
I haven't looked around too much (seeing as I only JUST got the damn thing to boot a rom) but is there a fix to that, perhaps installing the retail bootloader?
I'd hate to have to use fastboot everytime my rom doesn't boot. I've gotten used to wiping and installing roms from wherever I am on my other android devices.
I'm not familiar enough with the device to be able to give you a definite answer, but i imagine adding a bootloader from the retail version would give you the recovery option instead of fastboot.
personally, i'm a little more fond of having fastboot around right now, as it's easy enough to get into recovery when flashing things with it, and the bootloader for the I/O is unlocked... i can think of a few fun things to do in the future if i can load any ROM i want into memory, test it, and move on if it's no good... i may even give some of the ICS dailies a try thanks to this.
Always several ways of doing things... glad you got it worked out.
http://forum.xda-developers.com/showpost.php?p=15735928&postcount=2
RootzFan,
that method is flashing an entirely new rom, down to 3.0, just to gain root access and open recovery so you can then return to 3.1.. it has the added byproduct of installing touchwiz.
IMHO, my way is a little cleaner as there is actually zero flashing needed, and you get to keep everything active and installed.
i recommend just going for custom roms - it comes already rooted - yBoot into recovery and flash a custom ROM
I have the IO tab myseldf and have been flawlessly running GalaxyTask custom ROM - http://forum.xda-developers.com/showthread.php?t=1340064
shane86 said:
I recently purchased a used Galaxy tab 10.1 I/O, and it had already received the 3.1 OTA update.
Now i want root access for various reasons, and can't seem to find a clear guide on how to do so.. I've found plenty about how to do so on the original 3.0 rom, and that it will carry through the 3.1 update, or for the regular version Galaxy Tab 10.1, but it's my understanding the ROMs were fairly different between the I/O and the retail version and that attempting to cross-pollinate root methods may not be a good idea
although I've rooted and ROMed my fair share of HTC devices and Nooks i'm a little more apprehensive with this unit, as it's my first android device to lack an SD card slot of some sort, so bricking seems like a much worse possibility
Click to expand...
Click to collapse
oh, def not the best method... just saying it is nice that there are alternatives.
self delete
Fun Stuff.
I've been all through the old threads and googled the hell out of this...
I've recently been released from iHell and have to start all over as a noob again.
I successfully rooted my I-777 with entropy512's OneClick Odin method. Then re ran the OTA t back to 2.3.6. I am still rooted. (YAY!!!!!)
Anyway it was strongly suggested that I run a nandroid backup before flashing a new ROM. I went to the market, searched nandroid and was presented with CWM ROM manager. After install, on first run, it wanted to install CWM Recovery (which I thought could only come from a kernel but anyway). It appeared to have done so, but when I attempt to run the ROM backup it errors:
Code:
E:failed to verify whole-file signature
E:signature verification failed
I'm also getting errors in 3e:
Code:
--Copying Media Files ...
Successfully coppied media files
# manual mode #
--Updating Application...
Successfully updated application
-- applying multi-CSC...
installing multi-CSC
Can't access to '/system/csc/ATT/system/'.
successfully applied multi-csc.
Another strange behavior (not necessarily an error): Last night, prior to rooting, I was able to do to download mode with my USB cable plugged into EITHER the computer OR a USB power adapter / charger. Today, after root and ROM manager, I can only get to Download mode when plugged in to the computer. (caused a bit of panic till I took a couple deep breaths and began to trouble shoot)
I'm not a huge fan of flashing anything without a (relatively) virgin backup. I fear I may be stuck at root for a bit.
So questions:
1. Did ROM manager ACTUALLY install CWM R? Or do I have to flash the kernel to get it?
2. Is there a better way to gain a full file system image? I've seen a few users say that ROM manager and other GUI's add a layer of complexity and possibly error to the backup process.
2a. Is there a CLI in Android? (even an app to do CLI?) If so , can I interact direclty with the OS that way?
3. Is there a place to get a clean OS install if I get all A.D.D. and go ahead and flash without the backup and then screw the pooch? (Or if I want to virginize for any reason?)
I am planning to follow creepyncrawly's post to flash if I can work this out:
http://forum.xda-developers.com/showthread.php?t=1311081
I am dieing without my WiFi hotspot.
There are warnings in several places in the I777 forums to not use ROM Manager. It's not compatible with the I777 phone.
Yes, you have to have a custom kernel to have working ClockworkMod Recovery.
There is no way to do a nandroid backup of the stock kernel. You can do a nandroid backup of the stock file system by installing a custom kernel with CWM Recovery.
You can restore the original UCKH7 binaries with or without root by using Entropy512's Return/Unbrick to Stock, and there is also a UCKK6 available in that thread, so no need for a stock nandroid backup. The main reason for a nandroid backup is to backup the modifications that you have made.
So use the guide to install a custom kernel. I would suggest Entropy512's latest daily driver, especially if you plan to run the stock ROM for any length of time. Then do a nandroid backup. Then you can move forward to installing a custom rom if you want, or whenever you want.
SeniorGato said:
it wanted to install CWM Recovery (which I thought could only come from a kernel but anyway)
Click to expand...
Click to collapse
Somehow ROM Manager can try to run its own version of CWM - I have never seen this work properly.
I'm also getting errors in 3e:
Code:
--Copying Media Files ...
Successfully coppied media files
# manual mode #
--Updating Application...
Successfully updated application
-- applying multi-CSC...
installing multi-CSC
Can't access to '/system/csc/ATT/system/'.
successfully applied multi-csc.
Click to expand...
Click to collapse
Odd, that looks like the initial power-on CSC flash, shouldn't happen after that.
Another strange behavior (not necessarily an error): Last night, prior to rooting, I was able to do to download mode with my USB cable plugged into EITHER the computer OR a USB power adapter / charger. Today, after root and ROM manager, I can only get to Download mode when plugged in to the computer. (caused a bit of panic till I took a couple deep breaths and began to trouble shoot)
Click to expand...
Click to collapse
This is working as intended, not sure why you were able to enter DL mode on a charger (shouldn't have happened), unless it was not an official charger. The resistors in iDevice chargers make the phone think a real PC is connected, not a charger.
So questions:
1. Did ROM manager ACTUALLY install CWM R? Or do I have to flash the kernel to get it?
Click to expand...
Click to collapse
ROM Manager sort-of-installed a nonfunctional version of CWM. Only one that works properly is in-kernel CWM. (Read through Development, also read through Creepy's guides on flashing kernels without tripping the flash counter)
2. Is there a better way to gain a full file system image? I've seen a few users say that ROM manager and other GUI's add a layer of complexity and possibly error to the backup process.
Click to expand...
Click to collapse
Nandroid from CWM itself - the instructions for entering CWM and using it properly are in codeworkx'x CWM thread in Development.
2a. Is there a CLI in Android? (even an app to do CLI?) If so , can I interact direclty with the OS that way?
Click to expand...
Click to collapse
This is why Android is so popular with tinkerers - while the GUI is heavily customized, shell access is almost identical to a vanilla Linux system. Google "ADB" for more info. ADB only works in recovery on custom kernels.
3. Is there a place to get a clean OS install if I get all A.D.D. and go ahead and flash without the backup and then screw the pooch? (Or if I want to virginize for any reason?)
I am planning to follow creepyncrawly's post to flash if I can work this out:
http://forum.xda-developers.com/showthread.php?t=1311081
Click to expand...
Click to collapse
You answered your own question right there - his guides link my stock kernel/system dumps.
I suggest spending a day or two reading through the various threads in Development, and reading the FAQ in general, there is a LOT of reading material and even if it goes over your head the first time, you'll start absorbing it and it'll make more sense the next time around. The fact that you are proceeding cautiously is a good start.
Oops... Apparently I wasn't "all through" the forums enough huh? I didn't see any warnings about ROM Manager... but thanks I'll dump it.
Everything else you say makes sense. Thanks!!! I'm still trying to translate what I know about the iOS FS and jailbreaking to what I need to learn about Android. Ugh...
@ entropy
Ya the CSC thing, I've been multi-tasking all day and for the life of me I can't remember why I was even in 3e. It wasn't for a restore, thats for sure.
I had assumed that the development threads were the real high level stuff (as it is on iOS forums the "DEV's" speak in code and their conversations can strip the hair of a noob's head. I figured I'd start slow, with (what I assumed would be) the lower level stuff. I'll head over to the dev threads now.
Thanks again!!!
SeniorGato said:
@ entropy
Ya the CSC thing, I've been multi-tasking all day and for the life of me I can't remember why I was even in 3e. It wasn't for a restore, thats for sure.
I had assumed that the development threads were the real high level stuff (as it is on iOS forums the "DEV's" speak in code and their conversations can strip the hair of a noob's head. I figured I'd start slow, with (what I assumed would be) the lower level stuff. I'll head over to the dev threads now.
Thanks again!!!
Click to expand...
Click to collapse
Usually the threads for ROMs/kernels have enough to be useful in the first posts. Even if it goes over your head the first few times, you'll get ideas for Google search terms to play with like Odin and Heimdall.
Also there's a FAQ in General.
So i just decided to join the rest of the world and get myself a rectangle. so i researched the 1 to 200 dollar range for weeks until i found my new shiny metal friend with great specs and a price that wouldn't keep me up at night. the le max 2 x829. but i love tech and was really looking forward to pushing this phone and learn about all it could do! i was really excited.
Until i started to learn about the many confusing programs needed to install custom roms or make a recovery file. things like that All of which need like 6 different programs all of which seem to need some other program in order to functional. I can't seem to even find a starting point! I HAVE NEVER FELT THIS STUPID IN MY ENTIRE LIFE. Someone please help. what programs do i need for a new os ? How does adb fit into the chain of programs needed to mod android? is twrp the first program needed? how does it all sort...fit to gather? Thanks for any help!
Man, honestly this forum is made to help people, but also people should use the search button. This question has been answered a million times already.
Long story short:
- Connect the phone to the PC and install the drivers (including ADB)
- Unlock bootloader (usually it's already unlocked)
- Download TWRP on your PC
- Install TWRP following the developer's steps
- Download your custom ROM
- Put the ROM on the internal memory
- Boot into TWRP
- Install the new ROM according to the instructions given by the developer and you're done...
valy_cta said:
Man, honestly this forum is made to help people, but also people should use the search button. This question has been answered a million times already.
Long story short:
- Connect the phone to the PC and install the drivers (including ADB)
- Unlock bootloader (usually it's already unlocked)
- Download TWRP on your PC
- Install TWRP following the developer's steps
- Download your custom ROM
- Put the ROM on the internal memory
- Boot into TWRP
- Install the new ROM according to the instructions given by the developer and you're done...
Click to expand...
Click to collapse
including adb? what other drivers do i need? xposed? supersu? ...i have done my research by the way...its just not making alot of sense..thats all. i know all you old pros have probably been at it for years but i never even held a smartphone until 6 days ago ha ha
valy_cta said:
Man, honestly this forum is made to help people, but also people should use the search button. This question has been answered a million times already.
Long story short:
- Connect the phone to the PC and install the drivers (including ADB)
- Unlock bootloader (usually it's already unlocked)
- Download TWRP on your PC
- Install TWRP following the developer's steps
- Download your custom ROM
- Put the ROM on the internal memory
- Boot into TWRP
- Install the new ROM according to the instructions given by the developer and you're done...
Click to expand...
Click to collapse
Also how do you download twrp on you're pc ? it won't let me i have it on my phone but it just keeps leading me to a website to download again.
Serialjwalker said:
Also how do you download twrp on you're pc ? it won't let me i have it on my phone but it just keeps leading me to a website to download again.
Click to expand...
Click to collapse
Do you have it installed on the phone or just downloaded? If it's installed, jump over that step. If it's just downloaded, connect the phone to the pc by cable, transfer the files :cyclops:
I understand your concern. It's because there are a few ways of doing it, and so novices might be confused when comparing two different tutorials.
This one is very complete: https://forum.xda-developers.com/le-max-2/how-to/protocol-backup-stock-rom-flash-stock-t3517151
1. Connect your phone, it is supposed to install drivers automatically.
1.1 If not, you'll need to google it, but I believe this toolkit will help you. In fact, this tool is capable of doing all the process for you by simply clicking on some buttons.2. Install ADB Drivers. There are a few options and it is basically
2.1 @greenManGaming recommends 15 seconds ADB installer.
2.2 (Alternative) Minimal ADB and Fastboot. I've used this one.
2.3 (Alternative) ADB and Fastboot (newer) or Universal ADB and Fastboot (older) from the same dev.
OBS: I'm not sure if the toolkit requires or not one of these options to work properly or if it already does this task.3. Download TWRP (on your computer).
3.1 Follow the instructions from the official page. In short, put the img into the ADB folder.4. Follow the commands in the the tutorial mentioned.
4.1 In short, unlock the bootloader, boot twrp, complete backup, reboot into the system, copy the backup to your PC/Cloud service, get back to fastboot mode, flash twrp, then flash your ROM.
OBS: Suggestion for only booting TWRP at the first time is perfectly optional, you can flash it since the beginning but in this case you wouldn't be able to backup the original recovery and everything as the phone came, in case you need go back to request an RMA.
razmth said:
I understand your concern. It's because there are a few ways of doing it, and so novices might be confused when comparing two different tutorials.
This one is very complete: https://forum.xda-developers.com/le-max-2/how-to/protocol-backup-stock-rom-flash-stock-t3517151
1. Connect your phone, it is supposed to install drivers automatically.
1.1 If not, you'll need to google it, but I believe this toolkit will help you. In fact, this tool is capable of doing all the process for you by simply clicking on some buttons.2. Install ADB Drivers. There are a few options and it is basically
2.1 @greenManGaming recommends 15 seconds ADB installer.
2.2 (Alternative) Minimal ADB and Fastboot. I've used this one.
2.3 (Alternative) ADB and Fastboot (newer) or Universal ADB and Fastboot (older) from the same dev.
OBS: I'm not sure if the toolkit requires or not one of these options to work properly or if it already does this task.3. Download TWRP (on your computer).
3.1 Follow the instructions from the official page. In short, put the img into the ADB folder.4. Follow the commands in the the tutorial mentioned.
4.1 In short, unlock the bootloader, boot twrp, complete backup, reboot into the system, copy the backup to your PC/Cloud service, get back to fastboot mode, flash twrp, then flash your ROM.
OBS: Suggestion for only booting TWRP at the first time is perfectly optional, you can flash it since the beginning but in this case you wouldn't be able to backup the original recovery and everything as the phone came, in case you need go back to request an RMA.
Click to expand...
Click to collapse
more questions....twrp will only load onto my phone and not my pc? also there are no adb driver folders just an exe. what do i do about that?
someone tell me how to delete this thread...i am just going to sell my smartphone i can't look at it anymore. every thing i try to do with it it resists every single inch of the way. nothing works according to instructions. i thought this would be fun but its hell... i give up! ...it wins going to trade this thing for the first 30 dollar burner phone i can find
Huge drama for nothing. Sell the thing, it's obviously not for you. If you can't follow some simple instructions, then it's better to sell it to some guy who likes to try at least.
valy_cta said:
Huge drama for nothing. Sell the thing, it's obviously not for you. If you can't follow some simple instructions, then it's better to sell it to some guy who likes to try at least.
Click to expand...
Click to collapse
maybe they are laid out to be simple but nothing is working as instructed. i have been at it for a week . so far installing firefox is the best i can seem to do lol simple? theres nothing simple about the gangbang of programs you need to do stuff on these phones. none of which can actually be compelled to function under any circumstances at least for me.
Serialjwalker said:
maybe they are laid out to be simple but nothing is working as instructed. i have been at it for a week . so far installing firefox is the best i can seem to do lol simple? theres nothing simple about the gangbang of programs you need to do stuff on these phones. none of which can actually be compelled to function under any circumstances at least for me.
Click to expand...
Click to collapse
If you are not familiar with giving commands with command prompt, installing drivers and needed software (android studio or minimal adb install) then you are in for a challenge, if you are not willing to learn its better to sell the phone or use it with de preinstalled android.
i find myself quite skilled( have flashed several brands of phoned in the last 5 years) and it took me a couple of days to figure out what to do and how to install twrp and my first rom, there are no one click shortcuts for this phone
Why need to install rom? It already work.
Serialjwalker said:
more questions....twrp will only load onto my phone and not my pc? also there are no adb driver folders just an exe. what do i do about that?
Click to expand...
Click to collapse
Did you try watching different videos to have a big picture of the process? It would be the first step. Even if you don't understand English, simply watch it. You'll see what would happen after each action.
Then check the written tutorial. Not a big issue at all. Really. Even for newbies, I've been one when I had a Galaxy 5, my first android that doesn't even needed to flash a custom ROM.
Whether you think you can, whether you think you can't, you're right.
The command to load the TWRP will be done on your PC, however, only your phone will load it. In short, you'll be commanding your phone through your PC.
When you install Minimal ADB and Fastboot, it will install its files in a default folder. Inside its default folder is where you should place the TWRP image.
Sent from my Le X820 using Tapatalk
Hey everyone,
So! I bought a Sony Xperia 1 (J8110-2019) phone from someone on Facebook Marketplace at a very solid price of £250 (RRP is still £850 in the UK) due to the seller describing it as 'in retail demo mode' so they lowered the price. I jumped the gun thinking I was getting a solid deal and just stupidly assumed it to be a feature I could just disable with *#*#73556673*#*#- me believing I was some insane developer with mad coding skills where in realityI had once flashed and rooted my Xperia XZ back in 2016. [Insert 'Hackerman' meme]
Yes... I am fully aware I'm a complete idiot for not doing a full assessment on the phone and am now having to learn a very important lesson from this situation!!
It seems to have a Store Front firmware installed and unsure what firmware to download and flash? I've tried some of the official stock ROMs from XperiFirm and it just continues to boot into constant 10-second cycles of demo videos making general functionality like phone calls pretty much impossible. without interruption. I've tried Customized and UK Service Provider Firmware such as EE and O2 but it always goes back into Store mode.
I was hoping if anyone would have or could elaborate on how to make an executable system flash zip for a 2019 Xperia 1? When I extract files from XperiaFirm ROMS (FTF,ZIP,SIN etc), I don't seem to get any META-INF files and thus cant make the proper .zip that TWRP needs to successfully flash a new repacked stock ROM? It always ends in a boot loop."
Here are some key points to hopefully give you some background:
I've installed TWRP successfully and have attempted to use 3 official firmware to flash whilst in recovery but have been unsuccessful each time with 'Invalid .ZIP format'. I've only a few times got booted whilst bundling together FTF files via Flashtool and doing it that way round but only ever seems to solve half the problem
I can't use the SinExtract feature in Flashtools as the SIN file errors as not being supported yet to use different file versions.
I can't use PRFCreator as it errors as the FTF file being unsupported (Due to it being new I assume)
I attempted to create my own META-INF>Updater-script but am unable to identify what partition my phone would use for mounting on "/dev/block". I only ever seem to get MANIFEST.MF from the files and nothing else. On my XZ I think I used something like:
(package_extract_file("boot.img", "/dev/block/mmcblk0");
package_extract_file("system.sin","/dev/block/platform/msm_sdcc.1/by-name/system");
Click to expand...
Click to collapse
I have been able to install Magisk for rooting and verified.
I have used Minimal ADB and Fastboot to install programs like TWRP, SuperSu, Magisk but have never attempted, nor would I even know how to wipe my phone completely and install a clean stock ROM - is this possible?
All drivers, software, and systems are correct and up to date (as far as I am aware)
Would installing the' Service Exchange Firmware' be recommended (if I ever make it that far!) due to it being StoreFront?
I checked the IMEI number to see if it was blacklisted/blocked and it's all good. Not lost or stolen.
Thank you for your time to read and wallow in my woes with me my lovelies! Any help would be GREATLY appreciated you magnificent beasts! x
Bump x
...
the last chance... :good:
I got my new phone working today. It's a Sony Xperia 1 IV (XQ-CT72)
In my opinion, it's one of a very few that are the best options available right now for anyone who wants 1) the ability to root their device, 2) a headphone jack, and 3) an SD card slot.
Step 1 was to go ahead and install all the updates that were coming in over the air. This may not always be the best course of action, as moving to a firmware that is "too new" may get you to a version that is incompatible with currently available tools. However, as unlocking your bootloader usually disables Over-the-Air updates, this can save time later if you want an up-to-date device. (Step 1a here may be to verify the device works with your mobile network; I didn't verify this until I was up and running with root, and had a moment of mild panic when the mobile provider rep told me it's not compatible, even though I was 99% sure it was(turns out it is, and it's working fine, despite their refusal to acknowledge it)).
Step 2 is to grab a copy of XperiFirm(I used v 5.6.5). This allows you to pull a copy of the firmware from Sony's servers. There are other ways, but XperiFirm essentially gives you all the information to find the appropriate version for your device. Choosing the wrong firmware could result in "bricking" your device. Mine was running 64.1.A.0.869.
Step 3 is to use Sony Dump Tool, aimed at the "boot####.sin" file from the firmware to dump it to a .IMG file.
Step 4 is to copy or move that dumped image onto an Android device with the most recent version of Magisk installed(v25.2 as of this writing).
Step 5 is to use Magisk from within Android to patch the boot.img file with the Magisk magic.
Step 6 is to copy/move that patched image file back to a computer with Android "platform tools" installed. I'm using platform tools version 34.0.1-9680074.
Step 7 is to place your device into "bootloader mode".
Step 8 is to use the command fastboot flash boot BOOT.IMG where "BOOT.IMG" is your patched boot image.
Step 9 is to boot into Android and check your Magisk application to see if it worked.
The only thing not included here(which was causing me some problems at one point) is to install drivers for your device straight from Sony. This can be a little difficult, because Windows doesn't want to play nice with this sort of thing. It's essentially a full manual install of the driver via .INF file. Windows update is useless.
Happy rooting!
I was thinking rooting my Xperia 1 1V.
Many yrs ago android rooting was much easier, I know Google have since patched many of the loopholes and refined android security of the yrs.
Having used Huawei and Honor devices without root or even the possibility of rooting (bootloader codes unavailable) before coming back to Xperia, I got used to not having root.
Reading your description while very clear and straightforward, for me, rooting nowadays just seems like so many hoops to jump through.
I just rooted mine now