Created with MagiskManager 5.6.3
Code:
fastboot flash boot boot.img
Tested on My Project FI X4
Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards, fires, rigged elections,
* thermonuclear war, or you getting fired because the alarms failed and you could not call in.
Please
* Ensure you have an advanced understanding of this device before flashing it! YOU are choosing to make these modifications or your own free will.
*/
Download Here
Will try out tomorrow. Thanks!
Can you explain how to get the boot.img from the phone? I would like to try patching it myself.
And do you know if the boot.img is the same across different firmware versions and different versions of the phone?
opcode1300 said:
Created with MagiskManager 5.6.3
Tested on My Project FI X4
Click to expand...
Click to collapse
I assume that fastboot flashing this requires that the bootloader be unlocked, right? With my original Moto X Dev Edition, I did not need to worry about voiding the warranty...
---------- Post added at 05:42 PM ---------- Previous post was at 05:33 PM ----------
Zarxrax said:
Can you explain how to get the boot.img from the phone? I would like to try patching it myself.
And do you know if the boot.img is the same across different firmware versions and different versions of the phone?
Click to expand...
Click to collapse
I assume that the OP may have unlocked the bootloader, installed TWRP, installed Magisk, then backed-up the boot partition with TWRP, extracted the boot image from the backup.... Maybe
If I root my phone using the magisk method, will I still be able to use Google play books to read my audiobooks I've purchased or does rooting break those features?
Sent from my moto x4 using Tapatalk
I wish there was more info in here. There isn't a lot of information on prerequisites etc. I've had a hundred android phones an the process to root is different in all. Do I need to unlock the bootloader first, and is it only certain buildnumbers that this works for?
I think this post has been abandoned by OP, and probably should be closed.
Nickdroid86 said:
I wish there was more info in here. There isn't a lot of information on prerequisites etc. I've had a hundred android phones an the process to root is different in all. Do I need to unlock the bootloader first, and is it only certain buildnumbers that this works for?
Click to expand...
Click to collapse
out of those 100 android phones.
90 of those phones would need
bootloader unlock
custom recovery
flash Magisk or Super SU in custom recovery
10 of those phones would need
bootloader unlock
flash pre-rooted boot.img
also, if you had searched you would have found this.
https://forum.xda-developers.com/moto-x4/how-to/guide-how-to-root-moto-x4-install-twrp-t3806460
munchy_cool said:
out of those 100 android phones.
90 of those phones would need
bootloader unlock
custom recovery
flash Magisk or Super SU in custom recovery
10 of those phones would need
bootloader unlock
flash pre-rooted boot.img
also, if you had searched you would have found this.
https://forum.xda-developers.com/moto-x4/how-to/guide-how-to-root-moto-x4-install-twrp-t3806460
Click to expand...
Click to collapse
I'm not sure that I'd say 90, over the past few years I've had Suzanne of phones and I haven't had to mess with the bootloader. My question still remains unanswered. I'm not finding prerequisites for these mods and if 8.1 is compatible and needs certain build number. Not looking to brick my new phone which seems to be common in the Moto x4 section.
Nickdroid86 said:
I'm not sure that I'd say 90, over the past few years I've had Suzanne of phones and I haven't had to mess with the bootloader. My question still remains unanswered. I'm not finding prerequisites for these mods and if 8.1 is compatible and needs certain build number. Not looking to brick my new phone which seems to be common in the Moto x4 section.
Click to expand...
Click to collapse
name some of those devices which you rooted without unlocking the bootloader?
munchy_cool said:
name some of those devices which you rooted without unlocking the bootloader?
Click to expand...
Click to collapse
Basically any device compatible with kingroot, and some newer devices who's bootloader cannot be unlocked. That's why they make workarounds.
Nickdroid86 said:
Basically any device compatible with kingroot, and some newer devices who's bootloader cannot be unlocked. That's why they make workarounds.
Click to expand...
Click to collapse
and people complain about Chainfire selling SuperSU to the Chinese.
anyways,
unlock bootloader
install TWRP
flash magisk
works with all moto x4 as long as you can unlock the bootloader.
Nickdroid86 said:
I'm not sure that I'd say 90, over the past few years I've had Suzanne of phones and I haven't had to mess with the bootloader. My question still remains unanswered. I'm not finding prerequisites for these mods and if 8.1 is compatible and needs certain build number. Not looking to brick my new phone which seems to be common in the Moto x4 section.
Click to expand...
Click to collapse
What you're saying doesn't make sense. To say you have had that many Android phones too is confusing to us. We are here to assist.
Everything @munchy_cool said.
munchy_cool said:
out of those 100 android phones.
90 of those phones would need
bootloader unlock
custom recovery
flash Magisk or Super SU in custom recovery
10 of those phones would need
bootloader unlock
flash pre-rooted boot.img
also, if you had searched you would have found this.
https://forum.xda-developers.com/moto-x4/how-to/guide-how-to-root-moto-x4-install-twrp-t3806460
Click to expand...
Click to collapse
Way to put the entitled little prick in his place. I never ask questions because I can find the answer with a Google search every single time. I am a pretty good (semi-ethical) hacker and a great pot grower because of Google and the multitude of repeat, "dumb", and actually really useful questions asked by lazy rich kids. I consider guys that respond as you did to be a sort of forum vigilante. Munchy cool is cool with me.
moto XT1900-1
Can someone provide me mmcblk0.img of moto XT1900-1
Related
A few of us purchased the Dev Edition and it appears there are some things where clarification is required concerning the three "R's":
1. Rooting: I understand this wonderful rooting exercise is successful: http://forum.xda-developers.com/showthread.php?t=2290798. I would think since the Dev Edition is unlocked, an owner would only utilize Step 3, and NOT the kernel exchange section. Correct?
2. ROMing: Since the ROMS were created using the Loki enabled system, does this affect ROMing the Dev Edition since it is already unlocked? What does a user need to do? Or, does it not matter? Do the Loki enabled ROMS work on a Dev Edition?
3. Recovery: Again, it appears TWRP and CWM are Loki adjusted, so does this affect recovery on the Dev Edition and restoring? Also, is there a Stock Factory Image which will NOT turn the phone back to a locked bootloader? Or, does the one which exists OK to use?
I only ask these questions since a few of us are somewhat confused.
Thanking you in advance!
markwebb said:
A few of us purchased the Dev Edition and it appears there are some things where clarification is required concerning the three "R's":
Click to expand...
Click to collapse
I've been thinking about buying the Verizon S4 Dev Edition phone, but have been hesitant due to not knowing how simple it would be to root. Is it as simple as just running MotoChopper? Or is there a better way?
Being that the bootloader on this phone is truly unlocked, can you install the current versions of CWM or TWRP that are LOKI enabled, and will it work on this phone? I haven't seen any compiled versions that were non-loki (standard).
Same question goes for kernels too.
The first batch of Dev phones sold out in less than 24 hours, so I'd expect some of the people that have them would start posting their experience with it here soon. At least, I hope so!
Root failed when just applying the Motochopper step! It says it installs correctly and then it reboots and SuperSu is installed and then I checked for an upgrade which it took. However, it says it cannot install binary, there is a problem and closes.
I uninstalled SuperSu and tried a few times to root again but it doesn't work.
My phone states:
Kernel Version: 3.4.0-562219 dated May 15th
Build Number: JDQ439.I545OYUAMDK
Baseband: I545OYUAMDK
Must be something we can do....
markwebb said:
Root failed when just applying the Motochopper step! It says it installs correctly and then it reboots and SuperSu is installed and then I checked for an upgrade which it took. However, it says it cannot install binary, there is a problem and closes.
I uninstalled SuperSu and tried a few times to root again but it doesn't work.
My phone states:
Kernel Version: 3.4.0-562219 dated May 15th
Build Number: JDQ439.I545OYUAMDK
Baseband: I545OYUAMDK
Must be something we can do....
Click to expand...
Click to collapse
I wonder if step 2 and 4 are still required? (swapping kernels)
Even though the bootloader is unlocked, the kernel may still have root blocked?
guyd said:
I wonder if step 2 and 4 are still required? (swapping kernels)
Even though the bootloader is unlocked, the kernel may still have root blocked?
Click to expand...
Click to collapse
It sounds like it. But wouldn't swapping kernels render the Dev Edition to a retail version? Kinda defeats the purpose, no? Or, am I missing something?
The question is: Does the Dev Edition have the same kernel as the Retail Edition? If so, then it would make sense to swap kernels. I think we need the devs to weigh in.
markwebb said:
It sounds like it. But wouldn't swapping kernels render the Dev Edition to a retail version? Kinda defeats the purpose, no? Or, am I missing something?
The question is: Does the Dev Edition have the same kernel as the Retail Edition? If so, then it would make sense to swap kernels. I think we need the devs to weigh in.
Click to expand...
Click to collapse
From what I've been able to gather, Samsung has put in place a SetUID restriction on the stock release kernel via CONFIG_SEC_RESTRICT_SETUID. Apparently the D2 prerelease kernel doesn't have this restriction in place. That seems to be why flashing that is required prior to using MotoChopper to gain root. What I can't figure out is why you can flash the release DK afterwards and still keep root?
On the T-Mobile and Sprint S4 they've been able to remove the SetUID restriction on their latest DL release kernel by recompiling the kernel source with the SetUID restriction commented out
Thanks for the thoughts and analysis. Hopefully someone will find an alternate
root method for the dev edition since it has been available for a week and it sold out in less than twenty four hours, somebody with know how must have purchased it and is tinkering as we speak.
I would hate to render it back to a retail version otherwise.
Sent from my SCH-I545 using xda app-developers app
markwebb said:
Thanks for the thoughts and analysis. Hopefully someone will find an alternate
root method for the dev edition since it has been available for a week and it sold out in less than twenty four hours, somebody with know how must have purchased it and is tinkering as we speak.
I would hate to render it back to a retail version otherwise.
Click to expand...
Click to collapse
I think I may have found a solution. With the Developer Edition we have an unlocked bootloader, so there is no need to use loki. I was looking for a non-loki patched (normal) recovery that could be flashed in Odin. I think I found one here http://forum.xda-developers.com/showthread.php?t=2322675. Look for the "Latest version can be found here" link, not the "loki patched" link. The filename is : Philz_touch_5.06.6-jfltevzw.tar.md5
If this works like it did in previous unlocked Samsung devices, then we should be able to flash the custom recovery in Odin, and then boot into recovery afterwards to flash SuperUser. From there, we're rooted.
If I had my dev edition S4, I'd test it out myself. But I'm still waiting for them to get back in stock!
Great..am somewhat game to try. Well report back. Thanks!!
Sent from my SCH-I545 using xda app-developers app
IT WORKED...somewhat!!! When it boots, I now get Samsung Custom and unlocked symbol and I am in Philz Touch Recovery backing up the image.
As expected, the backup image is 4GB+ (saved on external card of course).
However, I can't update binary for root.
You, sir, are a genius...thanks so much..almost there!
Not really rooted though. Can't update binary and when in Root Explorer I can explore most folders but Root checker says I am not rooted.
Now what do I do? LOL
markwebb said:
IT WORKED...somewhat!!! When it boots, I nLet me know how it goes ow get Samsung Custom and unlocked symbol and I am in Philz Touch Recovery backing up the image.
As expected, the backup image is 4GB+ (saved on external card of course).
However, I can't update binary for root.
You, sir, are a genius...thanks so much..almost there!
Click to expand...
Click to collapse
Did you flash SuperSU from recovery via the zip file? (from this thread) http://forum.xda-developers.com/showthread.php?t=1538053. Look for the UPDATE-SuperSU-v1.41.zip file in the download section.
This should give you root after flashing in recovery! If you can't get root in a root app after flashing this file, then the kernel is blocking root. You can thank Samsung for adding that in the DK kernel.
You can easily work around this by flashing a custom kernel!
Let me know how it goes.
guyd said:
Did you flash SuperSU from recovery via the zip file? (from this thread) http://forum.xda-developers.com/showthread.php?t=1538053. Look for the UPDATE-SuperSU-v1.41.zip file in the download section.
This should give you root after flashing in recovery! If you can't get root in a root app after flashing this file, then the kernel is blocking root. You can thank Samsung for adding that in the DK kernel.
You can easily work around this by flashing a custom kernel!
Let me know how it goes.
Click to expand...
Click to collapse
BINGO!!!!!!!!!!!! THANKS!!!!
Now we need a thread/tutorial started for the Dev Edition Owners on how to do this!!
markwebb said:
BINGO!!!!!!!!!!!! THANKS!!!!
Now we need a thread/tutorial started for the Dev Edition Owners on how to do this!!
Click to expand...
Click to collapse
Do you now have root with the stock DK kernel, or did you flash a custom kernel?
Root with stock kernel.
Sent from my SCH-I545 using xda app-developers app
markwebb said:
Root with stock kernel.
Sent from my SCH-I545 using xda app-developers app
Click to expand...
Click to collapse
Now I know exactly what I need to do when I get mine!
Thanks for testing it out on your device
guyd said:
Now I know exactly what I need to do when I get mine!
Thanks for testing it out on your device
Click to expand...
Click to collapse
You are welcome. Now, the next question: Can we flash the ROM's which are Loki adjusted?
markwebb said:
You are welcome. Now, the next question: Can we flash the ROM's which are Loki adjusted?
Click to expand...
Click to collapse
Good question. From what I have seen thus far, the recovery is the piece that has to be Loki adjusted to allow it to be flashed on a locked bootloader. I don't think the ROM cares one way or the other. The only thing I still have questions about is the kernel. Is the kernel in the Developer Edition different than the carrier version?
guyd said:
Good question. The only thing I still have questions about is the kernel. Is the kernel in the Developer Edition different than the carrier version?
Click to expand...
Click to collapse
How do I/we find out? If you have any suggestions, let me know. I have gone this far and sweated.
markwebb said:
How do I/we find out? If you have any suggestions, let me know. I have gone this far and sweated.
Click to expand...
Click to collapse
If we could get an MD5 of the Developer DK kernel (boot.img), and compare it to the MD5 of a completely stock DK kernel (boot.img). Or maybe compare the kernel build numbers? I dunno, just throwing some ideas out.
just smashed my oneplus one so the other half has gave me her z2,
managed to root it on 4.4.4 and have Clockwork Recovery,
it so much more difficult to flash roms...
basically im looking for a rom with good battery life and good camera mods,
can some one just give me the heads up, do i still need to downgrade to 4.4.2 do i need to install dual recovery
and any tips on roms
cheers
based on what you wrote i'm assuming to rooted through unlocking your bootloader, which has voided your warranty and resulted in losing your DRM keys, now you don't have to downgrade for anything. that is required if you don't have a rooted phone and need to root without unlocking bootloader.
now you can simply flash any new rom. there are multiple choices, but only two lollipop roms available right now based on stock, Existez Y and Moonwalker Provolution, both are available in development section. personally i'm using Existenz Y as the black design in Provolution was not exactly my cup of tea, and it has some terrific options as ambient display and changing navbar size inbuilt without the need of xposed. otherwise there are multiple AOSP and CM based ROMS available in both development and orig development section. for flashing steps please read them on OP of each rom, and go through the threads properly before asking for them in new posts or threads.
thank you very much for writing back to me , yes i have unlocked the bootloader ,
reading Exstez topic it mentions about flashing latest firmware and adding dual recovery?
just checked Moonwalkers
You Must To Be Sure You Are On Firmware .726[LP] Or .28[LP]
Click to expand...
Click to collapse
sutty86 said:
thank you very much for writing back to me , yes i have unlocked the bootloader ,
reading Exstez topic it mentions about flashing latest firmware and adding dual recovery?
Click to expand...
Click to collapse
That is required if you are on LB and have dual recovery. i dont think if you have unlocked bootloader you need dual recovery. you can use normal recovery to flash. anyway dual recovery is available for UB also so you can use that. provides you with more option and i personally prefer that.
sutty86 said:
just checked Moonwalkers
Click to expand...
Click to collapse
Yes for moonwalker its recommended that you come from LP base. but i'm not sure how you can go back to stock after unlocking your BL. can't flash stock FTF normally as it might brick the device. might want to check sticky threads for getting to LP on unlocked bootloader. creating a prerooted firmware might help you in that. since i have a locked BL dont really know a lot about that part.
Just a heads up, since you unlocked your boot Loader the camera low light performance will be significantly bad and other Sony exclusive apps might not work. Hopefully you backed up TA partition.
Is anyone already working on porting TWRP to our u11 life? If not, I might try building for us all. Let me know so I don't waste my time.
Thanks!
dpryor88 said:
Is anyone already working on porting TWRP to our u11 life? If not, I might try building for us all. Let me know so I don't waste my time.
Thanks!
Click to expand...
Click to collapse
Dont think it would be considered wasting your time.
I'm here if you need anything I can offer to assist in this.
twinnfamous said:
Dont think it would be considered wasting your time.
I'm here if you need anything I can offer to assist in this.
Click to expand...
Click to collapse
Thanks dude!
I'll start tomorrow maybe after I get off work if I'm not too tired. No promises
I just want this to be like my old m8. An active community though I realize we aren't dealing with a flagship here, I'm still going to try to contribute somehow.
dpryor88 said:
Thanks dude!
I'll start tomorrow maybe after I get off work if I'm not too tired. No promises
I just want this to be like my old m8. An active community though I realize we aren't dealing with a flagship here, I'm still going to try to contribute somehow.
Click to expand...
Click to collapse
Nice to see some development interest for this phone!
Maybe it's too early to know but recovery for T Mobile variant will be the same as Android One?
Sent from my Huawei P9 powered by BlueWei [emoji41]
If I had the device I'd take a gander at making a recovery. I'd even make a CWM just for the fun of it if possible. Keep in mind I've never ported a recovery but I don't imagine the process is that difficult.
Marsou77 said:
Nice to see some development interest for this phone!
Maybe it's too early to know but recovery for T Mobile variant will be the same as Android One?
Click to expand...
Click to collapse
My guess is that the Android One variant will have A/B partitions for seamless updates, so there's going to be a different recovery and install method. All devices endorsed by Google since the launch of the Pixel use the new partition table and this results in difficulty in 3rd party development. Pixel doesn't have an official LOS ROM yet and just got official Magisk last month. It's going to be a rough start, but the community will grow.
Sent from my Mi A1 using XDA Labs
We are able to unlock the bootloader, Which means we can go Super CID. With Super CID we can flash (in DL mode) a magisk patched boot.img , and achieving root access. So next will be porting a recovery........ Get to work.
cbrown245 said:
We are able to unlock the bootloader, Which means we can go Super CID. With Super CID we can flash (in DL mode) a magisk patched boot.img , and achieving root access. So next will be porting a recovery........ Get to work.
Click to expand...
Click to collapse
You don't need SuperCID to flash a boot.img. That's simply incorrect.
Also, there was a link posted in the U11 TWRP thread to a test TWRP build for the U11 Life. Not sure if anyone tried it, but there were also device files uploaded, so it's probably a good place to start.
@sabpprook
Captain_Throwback said:
You don't need SuperCID to flash a boot.img. That's simply incorrect.
Also, there was a link posted in the U11 TWRP thread to a test TWRP build for the U11 Life. Not sure if anyone tried it, but there were also device files uploaded, so it's probably a good place to start.
@sabpprook
Click to expand...
Click to collapse
Technically yes and no , there arent any Tmobile boot img's floating around, so it has to be another GSM boot img. To ensure there are no hiccups being SuperCID wouldn't hurt.
cbrown245 said:
Technically yes and no , there arent any Tmobile boot img's floating around, so it has to be another GSM boot img. To ensure there are no hiccups being SuperCID wouldn't hurt.
Click to expand...
Click to collapse
I repeat: SuperCID has nothing to do with flashing a boot.img. You can literally flash any boot.img that fits on your device (with a proper header & dtb) if the bootloader is unlocked. CID isn't involved. In fact, SuperCID leads to issues with Carrier customization on newer devices, and RUUs will only flash on devices with the correct CID, not SuperCID. I think that happened around the time of the M9 Marshmallow or Nougat update.
In fact, you don't even have to flash the boot.img. You can simply fastboot boot it, and you should still be able to achieve root. And then you can back up the stock boot.img so there IS a T-Mobile boot.img "floating around." If someone just downloads one of the RUUs from Easy Firmware, uses the Decrypt Tool to extract it, and then Magisk to patch it, it should be possible to dump all of the stock T-Mobile device partitions.
Haven't seen you around since the Evo LTE. But I may be getting the U11 Life pretty soon, so I should be able to contribute in some way or form to the development of the device.
Anyone try that test TWRP build in the u11 thread yet? I'm thinking about it..
dpryor88 said:
Anyone try that test TWRP build in the u11 thread yet? I'm thinking about it..
Click to expand...
Click to collapse
u know the risks I looked through the source it has sd660 not 630. So I'm not sure what would happen but we won't know till someone finds out. Also I'm not sure if all the partition info would be the same.
twinnfamous said:
u know the risks I looked through the source it has sd660 not 630. So I'm not sure what would happen but we won't know till someone finds out. Also I'm not sure if all the partition info would be the same.
Click to expand...
Click to collapse
Yeah I'm not gonna chance it haha.
dpryor88 said:
Yeah I'm not gonna chance it haha.
Click to expand...
Click to collapse
Let me know how it goes
twinnfamous said:
Let me know how it goes
Click to expand...
Click to collapse
No I said I'm not going to haha. I'll wait
dpryor88 said:
No I said I'm not going to haha. I'll wait
Click to expand...
Click to collapse
OK my fault got excited and didn't read it rite
---------- Post added at 04:39 AM ---------- Previous post was at 04:18 AM ----------
dpryor88 said:
No I said I'm not going to haha. I'll wait
Click to expand...
Click to collapse
I paid the 15 dollars from easy firmware hopefully it's not a scam website and real files. I'm down loading one now. I'll keep you posted
dpryor88 said:
Yeah I'm not gonna chance it haha.
Click to expand...
Click to collapse
You don't even have to flash it. Just fastboot boot it from the bootloader and see if it works. That makes literally zero changes to your device. Nothing to risk at all.
Also, if you're not willing to soft brick your device for the purpose of testing, then there's no way you'll ever have a working TWRP.
twinnfamous said:
OK my fault got excited and didn't read it rite
---------- Post added at 04:39 AM ---------- Previous post was at 04:18 AM ----------
I paid the 15 dollars from easy firmware hopefully it's not a scam website and real files. I'm down loading one now. I'll keep you posted
Click to expand...
Click to collapse
It's a real website, and the files are all real. If you grab the combined signed RUU for the 617 region, you should be able to patch the extracted boot.img with Magisk for root.
Captain_Throwback said:
You don't even have to flash it. Just fastboot boot it from the bootloader and see if it works. That makes literally zero changes to your device. Nothing to risk at all.
Click to expand...
Click to collapse
Good call haha. Not sure what I was thinking. I'll give it a shot tomorrow.
Captain_Throwback said:
You don't even have to flash it. Just fastboot boot it from the bootloader and see if it works. That makes literally zero changes to your device. Nothing to risk at all.
Also, if you're not willing to soft brick your device for the purpose of testing, then there's no way you'll ever have a working TWRP.
It's a real website, and the files are all real. If you grab the combined signed RUU for the 617 region, you should be able to patch the extracted boot.img with Magisk for root.
Click to expand...
Click to collapse
Thanks and I'm willing to do anything it takes. I know the brick won't be forever I've been getting HTC since the evo days. I really do appreciate all your help.
My phone has the I545VRSGPL1 bootloader, and i cannot find any gosh dang way to unlock the bootloader and reinstall a custom bootloader. I have been trying for months now and it still wont work. I've used Odin and heimdall, I've even used flashing apps from google play and other apk downloading sites, but none of it seems to be working.
I cannot afford another phone, and the locked bootloader has put undesirable myriads of stress on my days. if anyone can help, please do so.
JacoTheWaco said:
My phone has the I545VRSGPL1 bootloader,.......
Click to expand...
Click to collapse
Unfortunately the Bootloader for the PL1 Firmware is Locked up and cannot be Unlocked.
There's no way to downgrade the Firmware past the OC1...
Sorry to give you the bad news.
~~~~~~~~~~~~~~~
I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.
Ibuprophen said:
Unfortunately the Bootloader for the PL1 Firmware is Locked up and cannot be Unlocked.
There's no way to downgrade the Firmware past the OC1...
Sorry to give you the bad news.
~~~~~~~~~~~~~~~
I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.
Click to expand...
Click to collapse
thanks for the help!
Ibuprophen said:
Unfortunately the Bootloader for the PL1 Firmware is Locked up and cannot be Unlocked.
There's no way to downgrade the Firmware past the OC1...
Sorry to give you the bad news.
~~~~~~~~~~~~~~~
I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.
Click to expand...
Click to collapse
OK... I'm gonna look some more, but I need to ask. I was given one of these yesterday with PL1 already on it. I can use Kingroot to get root sort of (titanium can't uninstall any system apps apparently) and I was wondering. Should I just run the debloat ADB script or can I now access the phone using ODIN and flash an already debloated touchwiz ROM? Maybe LineageOS? Or do I just need to find any ROM that says it's OK for OC1 and follow those instructions?
wrenhal said:
OK... I'm gonna look some more, but I need to ask. I was given one of these yesterday with PL1 already on it. I can use Kingroot to get root sort of (titanium can't uninstall any system apps apparently) and I was wondering. Should I just run the debloat ADB script or can I now access the phone using ODIN and flash an already debloated touchwiz ROM? Maybe LineageOS? Or do I just need to find any ROM that says it's OK for OC1 and follow those instructions?
Click to expand...
Click to collapse
Instead of using kingroot, use wonder share mobile go pro I think it's called to root PL1 instead. You can use flash fire v0.53 to flash touchwiz based ROMs only. Lineage OS is out, as is CM, and AOSP due to the locked bootloader. You can't even install a custom recovery, you're stuck with using flash fire and touchwiz ROMs. There are some debloated touchwiz ROMs, I think stang5litre ROM might be one. Most ROMs for this phone are based on the OC1 and OF1 firmware. To boot them, you need to downgrade or partially downgrade your bootloader to either OC1 or OF1. However, I think you can just flash stang5litre ROM with flash fire and it'll automatically get you to OF1. I just got this phone myself a few months ago, so I'm still trying to figure out this locked bootloader mess.
StoneyJSG said:
Instead of using kingroot, use wonder share mobile go pro I think it's called to root PL1 instead. You can use flash fire v0.53 to flash touchwiz based ROMs only. Lineage OS is out, as is CM, and AOSP due to the locked bootloader. You can't even install a custom recovery, you're stuck with using flash fire and touchwiz ROMs. There are some debloated touchwiz ROMs, I think stang5litre ROM might be one. Most ROMs for this phone are based on the OC1 and OF1 firmware. To boot them, you need to downgrade or partially downgrade your bootloader to either OC1 or OF1. However, I think you can just flash stang5litre ROM with flash fire and it'll automatically get you to OF1. I just got this phone myself a few months ago, so I'm still trying to figure out this locked bootloader mess.
Click to expand...
Click to collapse
Yes,it works well,i am using it now that i talk,but is there any way to make my phone in Android 6.0.1???I have read all the stuff things and i feel like a donkey with heavy weight in my back!!!!I mean i have read a lot of stuff and i dont know what to do,can someone do me a favour and tell me how to.do it???I will do even a downgrade is is possible!!!!I dont care about my phone is going to be hard bricked or soft broken by my punch!!!I wanna do it that android 6.0.1!!!
ford1234 said:
Yes,it works well,i am using it now that i talk,......
Click to expand...
Click to collapse
Unfortunately there's no option for any Android 6 or above for the I545 device with a locked Bootloader.
I've got one that's in the same boat and stuck with Android 5 with the Debloated stock development called the stang5litre.
If any attempts at forcing anything other than the Stock Firmware for this device will ultimately Hard Brick it...
~~~~~~~~~~~~~~~
UNLESS asked to do so, PLEASE don't PM me regarding support. Sent using The ClaRetoX Forum App on my SM-G900V device.
Ibuprophen said:
Unfortunately there's no option for any Android 6 or above for the I545 device with a locked Bootloader.
I've got one that's in the same boat and stuck with Android 5 with the Debloated stock development called the stang5litre.
If any attempts at forcing anything other than the Stock Firmware for this device will ultimately Hard Brick it...
~~~~~~~~~~~~~~~
UNLESS asked to do so, PLEASE don't PM me regarding support. Sent using The ClaRetoX Forum App on my SM-G900V device.
Click to expand...
Click to collapse
Who cares!!!!I wanna hard brick it,just to try how to go on a marshmallow Android!!!
Thank you for answering me
If you have any idea how to do it,share it
ford1234 said:
Who cares!!!!I wanna hard brick it,just to try how to go on a marshmallow Android!!!
Thank you for answering me
If you have any idea how to do it,share it
Click to expand...
Click to collapse
Amen
Here was a Guide. Someone said people don't care about Me or My Work so...
Feedback is always welcome! <3
Miustone said:
Feedback is always welcome! <3
Click to expand...
Click to collapse
I could not find the
GSI "Starter Pack" (From Google) from this link.
Could you please be more specific and tell us which GSI will work (Android 12, 11, or 10, and ARM64+GMS, ARM64, x86_64+GMS, or x86_64.). Thanks.
I want to unlock my bootloader and root my 3 iii but I have read something about needing to back up and restore DRM keys otherweise some camera features and other stuff wont work anymore. Is that something that needs to be done on this phone and also, what exactly is the GSI stuff? It looks like that is an entire rom or something. Do we need to flash/install that? I am fine with the stock firmware. Im out of my element with this Sony stuff.
[email protected] said:
I could not find the
GSI "Starter Pack" (From Google) from this link.
Could you please be more specific and tell us which GSI will work (Android 12, 11, or 10, and ARM64+GMS, ARM64, x86_64+GMS, or x86_64.). Thanks.
Click to expand...
Click to collapse
Hey, the "Starter Pack" is just another Name for the Google Zip which includes GSI and vbmeta. We are on ARM64 and GMS means GApps are included. Please read a bit about how Treble and GSIs are working and start from there. x86_64 btw. is the Dekstop Platform (Like Intel or AMD PCs). Basic knowledge
Don't want to make this an Info/Wiki Thread or so...
Hippie459MN said:
I want to unlock my bootloader and root my 3 iii but I have read something about needing to back up and restore DRM keys otherweise some camera features and other stuff wont work anymore. Is that something that needs to be done on this phone and also, what exactly is the GSI stuff? It looks like that is an entire rom or something. Do we need to flash/install that? I am fine with the stock firmware. Im out of my element with this Sony stuff.
Click to expand...
Click to collapse
That Informations are old and obsolete. Hardware works just fine after unlocking (On all Xperias since 2019), DRMs can be restored like i wrote in the Guide. We are using OLED HDR Displays. So don't care about Bravia or such stuff. Only Netflix and Video Enhancements aside from the Creator Mode are not working if unlocked. But AOSP is here and ROMs are also coming based on SODP and AOSP (With Mainline Kernels (Or GKI)) Please also read about Treble and GSIs before You start! It's a thing since Android 8 on all Android Devices. So it will be good to know! GKIs are also coming to all Android Devices soon...
How can I convert Xperia 1 IIi Docomo SO-51b to Global version?
You can try to use another (EU/US) Firmware with NewFlasher but no warranty that it will work @nchmaster
You should check the Basebands compatibility before so make sure You're flashing a Firmware that works with Your Countries Bands.
Miustone said:
You can try to use another (EU/US) Firmware with NewFlasher but no warranty that it will work @nchmaster
You should check the Basebands compatibility before so make sure You're flashing a Firmware that works with Your Countries Bands.
Click to expand...
Click to collapse
Many thanks!!! How can i check the baseband?
What's the role of GSI?
MK73DS said:
What's the role of GSI?
Click to expand...
Click to collapse
And is it needed to simply root the phone?
Hippie459MN said:
And is it needed to simply root the phone?
Click to expand...
Click to collapse
No it isn't. That's why I am asking. I got my Xperia 1 iii a few weeks ago (before this tutorial) and did the exact same steps but without the GSI thing and everything works fine.
MK73DS said:
No it isn't. That's why I am asking. I got my Xperia 1 iii a few weeks ago (before this tutorial) and did the exact same steps but without the GSI thing and everything works fine.
Click to expand...
Click to collapse
Perfect. I tried to ask that before and was just told to read up on GSI. That wasnt any real help to my question. lol I was looking it over and it looked like it was a really vanilla version of android more less for app developers so I was c onfused if it was in fact needed to simply root the phone.
Hippie459MN said:
Perfect. I tried to ask that before and was just told to read up on GSI. That wasnt any real help to my question. lol I was looking it over and it looked like it was a really vanilla version of android more less for app developers so I was c onfused if it was in fact needed to simply root the phone.
Click to expand...
Click to collapse
You missed the Point of GSIs...
Treble-Enabled Device Development A/AB ROMS
Treble-Enabled Device Development A/AB ROMS
forum.xda-developers.com
I asked what it was exactly and do we need to install it for the root process. By the way, it is not needed for the rooting process. I have successfully rooted the phone so thank you for the tutorial.
Just a suggestion, you should maybe add that after you flash the edited boot image to A and B and you reboot the phone, you will have to reinstall Magisk just to save some possible confusion as its no longer installed from being wiped during the bootloader unlock process.
Hippie459MN said:
I asked what it was exactly and do we need to install it for the root process. By the way, it is not needed for the rooting process. I have successfully rooted the phone so thank you for the tutorial.
Just a suggestion, you should maybe add that after you flash the edited boot image to A and B and you reboot the phone, you will have to reinstall Magisk just to save some possible confusion as its no longer installed from being wiped during the bootloader unlock process.
Click to expand...
Click to collapse
Sorry for the confusion! I hadn't time to give a good answer...
And I will realize your Suggestion about the order of steps. Thread Updates will come after I wake up
Hope the Guide is better now! Let Me know if You have additions!
Miustone said:
Hope the Guide is better now! Let Me know if You have additions!
Click to expand...
Click to collapse
Hi sorry I'm still confused, could you copy over name of the exact zip you are saying we should download?
https://imgur.com/a/ZXnMEeY
Which one is the "starter" pack.
Kylewolf said:
Hi sorry I'm still confused, could you copy over name of the exact zip you are saying we should download?
https://imgur.com/a/ZXnMEeY
Which one is the "starter" pack.
Click to expand...
Click to collapse
The "starter" pack is just another name for either gsi_gms_arm64-...zip or aosp_arm64-...zip. If you want Google apps then you choose gsi_gms_arm64-...zip, if you do not want Google apps then choose aosp_arm64-...zip. Both of these zip files contain only the system.img and vbmeta.img.
[email protected] said:
The "starter" pack is just another name for either gsi_gms_arm64-...zip or aosp_arm64-...zip. If you want Google apps then you choose gsi_gms_arm64-...zip, if you do not want Google apps then choose aosp_arm64-...zip. Both of these zip files contain only the system.img and vbmeta.img.
Click to expand...
Click to collapse
Sorry I guess I'm a bit new to this, the phone will still be running a version of the stock rom after this guide with an unlocked bootloader and magisk right?
Kylewolf said:
Sorry I guess I'm a bit new to this, the phone will still be running a version of the stock rom after this guide with an unlocked bootloader and magisk right?
Click to expand...
Click to collapse
GSI means General System Image. Systems are the Main OS You are using. Flash a GSI and it isn't Stock anymore... Don't replace the System If You want to keep Stock!