Hi Guys,
I upgraded few days ago to HTC one from nexus 4. (Simfree unlocked version)
Since then I have hit the check update millions of times with no joy.
I currently have no need to custom rom or root (mainly because bank apps do not work).
So I decided to do some reading and found that Norway version has the update.
I want to keep stock up want 4.2.2 now! As I write this my device is downloading and updating
I followed this guide to unlock BL
http://forum.xda-developers.com/showthread.php?t=2314582
used the revone-0.2.1 file
Once this was done I followed the guide to change my super CID from HTC-WWE "HTC__001" to HTC-Nor "HTC__Y13"
http://forum.xda-developers.com/showthread.php?t=2315247
fastboot oem writecid HTC__Y13
Then reboot the phone and checked and there was a small update (1.7mb or something) then the phone rebooted and I checked update and found it!!!! 4.2.2 :victory:
Took few mins to download and then update took 10mins
I then went back into fastboot and put my CID back to normal
fastboot oem writecid HTC__001
I wanted to lock the BL again but android 4.2.2 has a security feature which you get a pop up like SuperSU to grant permission but this box does not come up on the HTC one ( did for my Nexus)
"
[email protected]:/data/local/tmp $ ./revone -l
./revone -l
revone v0.2.1
Gaining root access (thanks to Dan's motochopper)...Segmentation fault (core dum
ped)
139|[email protected]:/data/local/tmp $
"
I can live with not locking BL for now untill people figure out what version of SDK/app is needed to re-lock BL.
But hey 4.2.2 on UK HTC one
I will do a video later.
Thanks
p.s this method kept all my data with no issues.
If any one figures out how I can re-lock BL let me know
If any one wants pics or wants me to check anything, let me know.
I confirm this working , now 4.2.2 ,thanks
Did you go s off as well or just unlocked bootloader
I think I set s-on again but still unlocked
Ronaldo_9 said:
I think I set s-on again but still unlocked
Click to expand...
Click to collapse
I guess my question is do you have to have s off in order to change the cid
---------- Post added at 12:20 PM ---------- Previous post was at 11:58 AM ----------
NOFSBIGE said:
I guess my question is do you have to have s off in order to change the cid
Click to expand...
Click to collapse
did not work for me
NOFSBIGE said:
I guess my question is do you have to have s off in order to change the cid
Click to expand...
Click to collapse
Yes you do as you write to the phone.
Ronaldo_9 said:
Yes you do as you write to the phone.
Click to expand...
Click to collapse
yeah it didnt work... oh well guess patience is what I need haha
NOFSBIGE said:
yeah it didnt work... oh well guess patience is what I need haha
Click to expand...
Click to collapse
If your boot loader is unlocked then why no s-off?
Nice.
Would appreciate a video as I'm a noob.
Theres already a thread/guide on how to unlock..change your Cid etc
dahmmy said:
Theres already a thread/guide on how to unlock..change your Cid etc
Click to expand...
Click to collapse
You mean this one?
Is that basically what this is?
Changing the CID so that you can identify as a different HTC one?
I've got a One with the original CID as Orang001 changed to HTC__001 & HTC__Y13 and nothing. am I doing something wrong?
{
"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"
}
Doesn't matter followed instrutions here http://forum.xda-developers.com/showthread.php?t=2305490 and sorted now
thanks anyway
There's already enough guides on how to unlock the bootloader and change the CID... Its really not very difficult.
@Ronaldo_9
You need to be rooted to use revone on hboot 1.54. Try using fastboot oem lock. That should set your bootloader to relocked. Really though there's no reason to do so.
My problem was I needed to flash a stock 1.28 ruu as the stock EE wouldnt give me updates no matter what CID I put. Once I did the ruu problems all solved.
Related
We can stay on the 5.0/5.0.2 bootloader (motoboot.img) and partition table (gpt.bin) and flash rooted 5.1 images using MoFo as well as the 5.1 kernel and radios using fastboot. Details for the XT1096 are here:
http://forum.xda-developers.com/showpost.php?p=61685122&postcount=46
Do not take the 5.1 OTA - flash manually!!!
If you upgrade to the 5.1 bootloader and partition table - YOUR COPY OF MOFO.EXE WILL NO LONGER WORK FOR YOUR DEVICE!!!!
There was a little bit of weirdness when I flashed the rooted image and tried to go into recovery to wipe cache - the dead android kept flashing at me and I couldn't get into the recovery menu. So then I flashed the 5.1 recovery. It is working fine now. I think I will flash back to 5.0 and then reflash it to see if that happens again.
{
"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"
}
Excellent news! Thanks @JulesJam!
We all learned a lot with our prior MoFo experience, so here's hoping the features are added to the 5.1 ROM with less troubleshooting this time.
Where is the rooted copy you used?
Can the mofo crew just update the binary to read the new gpt?
d33dvb said:
Can the mofo crew just update the binary to read the new gpt?
Click to expand...
Click to collapse
I am not sure what you are talking about.
MoFo.exe relies on an exploit to trick the bootloader to allow you to flash an unsigned system image. According to maiko1, the exploit was patched in the 5.1 bootloader. Supposedly he is working on trying to find an exploit in the 5.1 bootloader that he can use to do the same thing but only time will tell if he can find one.
Legacystar said:
Where is the rooted copy you used?
Click to expand...
Click to collapse
I didn't post it anywhere yet b/c of the issues I was having. @mikeoswego has a rooted image that he baked useful features into. When he posts his, I will just flash that and see how it works. He has a thread in the Android Development section of this forum where he posts his images.
http://forum.xda-developers.com/showpost.php?p=61702833&postcount=215
JulesJam said:
I am not sure what you are talking about.
MoFo.exe relies on an exploit to trick the bootloader to allow you to flash an unsigned system image. According to maiko1, the exploit was patched in the 5.1 bootloader. Supposedly he is working on trying to find an exploit in the 5.1 bootloader that he can use to do the same thing but only time will tell if he can find one.
Click to expand...
Click to collapse
I thought it was that it could not verify your device because of the way it read your info on the device. I assumed he used a zero day he had to attack the verification step of fastboot. I had thought about attacking in this manner. I mean, without busybox, can we try normal Linux shell privilege escalation attacks for this kernel version just like a desktop Linux machine? Are there any previous root methods and how they were obtained? I still say at this point, it would be great to be told what the exploit was, even without code.
---------- Post added at 05:01 AM ---------- Previous post was at 05:00 AM ----------
So it was specific to the bootloader, do we know at which version it became patched?
d33dvb said:
So it was specific to the bootloader, do we know at which version it became patched?
Click to expand...
Click to collapse
Its worked on all versions from 4.4.4 on up but according to maiko1, not on 5.1.
double post.
d33dvb said:
I still say at this point, it would be great to be told what the exploit was, even without code.
Click to expand...
Click to collapse
I think if the exploit has been patched, he should release what the exploit was as there is no harm at this point in releasing that information. Someone should ask him to do that.
The exploit was posted awhile ago according to jcase. What maiko didn't do was post his code for mofo because he owns that. If you want more info pm or tweet jcase.
Just 1 week ago i got a screen that inform me that there is an update for my moto x force.
I am not rooted, and my warranty is not void.
When i agree to reboot, phone reboots in recovery, and after 20% it stops and showing the android logo with message "error" . I can't update my phone i'm stucked. I tried also to clear cache but no way.
{
"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"
}
I'm from Italy and i buyed this phone 1 year ago from Amazon. This phone comes from France.
P.s. I'm sorry for my certainly bad english.
bootloader must be unlocked at some point maybe already came unlocked bootloader.
I have the same problem!
My bootloader is open.
sam00561 said:
bootloader must be unlocked at some point maybe already came unlocked bootloader.
Click to expand...
Click to collapse
Why i have to unlock my bootloader? I am completely stock and i don't want to loose my warranty.
This is a official update i received it last week
LoTableT said:
Why i have to unlock my bootloader? I am completely stock and i don't want to loose my warranty.
Click to expand...
Click to collapse
So what is your type?
What did your step ? Flashing new firmware via fastboot or OTA
If you did flashing via fastboot, I'm worried your MTX is XT1585, so you have to unlock bootloader.
My device a xt1580 EU
Flash via OTA (file 59MB)
And bootloader is unlocked.
frey.derico said:
So what is your type?
What did your step ? Flashing new firmware via fastboot or OTA
If you did flashing via fastboot, I'm worried your MTX is XT1585, so you have to unlock bootloader.
Click to expand...
Click to collapse
Yes it is XT1585. So i'll wait nougat upgrade for flashing a new firmware via fastboot
LoTableT said:
Why i have to unlock my bootloader? I am completely stock and i don't want to loose my warranty.
This is a official update i received it last week
Click to expand...
Click to collapse
I think your boot loader came unlocked is what I mean
sam00561 said:
I think your boot loader came unlocked is what I mean
Click to expand...
Click to collapse
But....it's impossible! I never touched anything.....why my bootloader is unlocked??!?!? I used warranty last month ago for replace micro usb port and they sayed anything about bootloader
LoTableT said:
But....it's impossible! I never touched anything.....why my bootloader is unlocked??!?!? I used warranty last month ago for replace micro usb port and they sayed anything about bootloader
Click to expand...
Click to collapse
I could be wrong you can check by entering into fastboot mode Iff it says device unlocked status 3 or some some thing like that then it is unlocked otherwise their is some other problem. I will leave a link for how you can boot into fastboot.
http://www.teamandroid.com/2015/01/08/enter-moto-x-fastboot-mode/
sam00561 said:
I could be wrong you can check by entering into fastboot mode Iff it says device unlocked status 3 or some some thing like that then it is unlocked otherwise their is some other problem. I will leave a link for how you can boot into fastboot.
http://www.teamandroid.com/2015/01/08/enter-moto-x-fastboot-mode/
Click to expand...
Click to collapse
It says my device is locked so i don't know why i can't update...
I think you may have to leave it and just wait for the official nougat update which is arriving quite soon for our phones. Hopefully you will be able to install that one. Iff not you can consider manually flashing it through fastboot.
sam00561 said:
I think you may have to leave it and just wait for the official nougat update which is arriving quite soon for our phones. Hopefully you will be able to install that one. Iff not you can consider manually flashing it through fastboot.
Click to expand...
Click to collapse
Every time i switch on the screen, update screen pops-up..... it's stalker me xD
It's a little bit annoying but ftw ill' wait nougat update
LoTableT said:
Every time i switch on the screen, update screen pops-up..... it's stalker me xD
It's a little bit annoying but ftw ill' wait nougat update
Click to expand...
Click to collapse
You can disable the update notification until nougat arrives but then you will have to re enable the notification to get the new update.
http://www.droidviews.com/disable-ota-notifications-android-devices/
sam00561 said:
You can disable the update notification until nougat arrives but then you will have to re enable the notification to get the new update.
http://www.droidviews.com/disable-ota-notifications-android-devices/
Click to expand...
Click to collapse
Thanks man.....really appreciated
There is any news about nougat update for us?
LoTableT said:
Thanks man.....really appreciated
There is any news about nougat update for us?
Click to expand...
Click to collapse
It should be released anytime soon I think the people with droid turbo 2 maybe already have it. I will have to wait until the firmware is released on xda to manually flash it because I am rooted but you should get it soon as it becomes available.
{
"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"
}
AutoScript for Install MM and Downgrade NT 100% Safe (no bricks, no efs lost)
Unlock Bootloader
Donwload your firmware
Unzip AutoScript and Firmware in the same folder
Power Off device
Conect in Fastboot Mode ( Power Vol - )
Run Script for Flash Firmware or Downgrade Firmware
Enjoy !!!
Download - https://drive.google.com/open?id=0B85AHa9iZYzfdjh0bU05TU1NTk0
core720 said:
AutoScript for Install MM and Downgrade NT 100% Safe (no bricks, no efs lost)
Unlock Bootloader
Donwload your firmware
Unzip AutoScript and Firmware in the same folder
Power Off device
Conect in Fastboot Mode ( Power Vol - )
Run Script for Flash Firmware or Downgrade Firmware
Enjoy !!!
Download - https://drive.google.com/open?id=0B85AHa9iZYzfdjh0bU05TU1NTk0
Click to expand...
Click to collapse
Hello mate, this is for those who updated to noguat via ota and your bootloader is updated to nougat to download to MM? Thanks to see if you make a rom like you did on the bike x 2014
regards
iron maiden said:
Hello mate, this is for those who updated to noguat via ota and your bootloader is updated to nougat to download to MM? Thanks to see if you make a rom like you did on the bike x 2014
regards
Click to expand...
Click to collapse
Yes, use DOWNGRADE script
I tested the downgrade script yesterday. It does his job, but after that there are no OTA's possible because of the missing modem downgrade.
I fixed it for a fully downgrade: https://drive.google.com/file/d/0B134drJ4-Ed0MHQ5aE1wUmp5eFk/view?usp=drivesdk
Use that file only with a unlocked Bootloader!!!!!
I donwngrade and install again firm and ota and perfect no problem
Can we get this to work on the normal moto z?
Thanks so much, works fine. Don't like nugat, too much battery drain and memory use compare to MM, so I'm back to 6.0.1 now
core720 said:
AutoScript for Install MM and Downgrade NT 100% Safe (no bricks, no efs lost)
Unlock Bootloader
Donwload your firmware
Unzip AutoScript and Firmware in the same folder
Power Off device
Conect in Fastboot Mode ( Power Vol - )
Run Script for Flash Firmware or Downgrade Firmware
Enjoy !!!
Download - https://drive.google.com/open?id=0B85AHa9iZYzfdjh0bU05TU1NTk0
Click to expand...
Click to collapse
sorry, I don't understand how to use. my phone it's lock in bootloop
Bootloader unlocked?
core720 said:
Bootloader unlocked?
Click to expand...
Click to collapse
yes, unlocked.
Work?
Did this work even if the bootloader is already on Nougat? Or does this only work on MM bootloaders?
i23u8 said:
Did this work even if the bootloader is already on Nougat? Or does this only work on MM bootloaders?
Click to expand...
Click to collapse
If the phone is unlocked, it should work.
-=MoRpH=- said:
If the phone is unlocked, it should work.
Click to expand...
Click to collapse
My phone is bootloader unlocked. Tried it but not getting past the boot logo. The bootloader version remains the same (nougat) and everything flashes fine.
Did u use the script from the first post? Or the one that I uploaded?
I used the zip from the first post.
I'm now trying the recent batch file you uploaded but it's failing on flashing gpt
---------- Post added at 04:28 PM ---------- Previous post was at 04:22 PM ----------
-=MoRpH=- said:
Did u use the script from the first post? Or the one that I uploaded?
Click to expand...
Click to collapse
It now restarts over and over again and displays "Erasing" with the green Android icon.
I have a Koodo (which is owned by Telus, and on the same tkpca software channel) Moto Z Play, and I've recently sideloaded the Nougat OTA from this thread here. Everything works just fine, but I've realized this might affect me getting future OTAs from my carrier. If I were to download the last Marshmallow firmware from Telus and downgrade using this script, would I run into any issues with this script? Would I run into any issues with OTA updates as well? I'm considering downgrading so I can obtain future OTAs through my carrier again.
Edit: Downgrade to Marshmallow using the included DOWNGRADE FIRMWARE.bat was successful. Thank you very much for writing this script.
This worked for me perfectly, I used @-=MoRpH=-'s version from the comments
Will this work from a stable LOS install? Is it possible to then sideload OTAs?
EDIT: Nevermind, I should learn to read.
It does work for moto z 1650-03?
This is the Pixel's TOOL ALL IN ONE Discussion Thread more info and download go to the Original Thread
TOOL ALL IN ONE
{
"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"
}
ADVANCED OPTIONS
FUNCTIONS
Install Drivers
Install Drivers
Unlock Bootloader
Lock Bootloader (use carefully)
Flash TWRP Recovery
Flash Stock Recovery
Flash Stock Factory Image
Automatic ROOT
Install APKs
Uninstall APKs
Take a Screenshot
Take a Screen Reocrd
Flash Partitions
Erase All Data (This function can decrypt the phone)
Reboot Phone
Update the Tool to latest version
Update Adb and Fastboot to latest version
Set Adb and Fastboot priviliges in system wide
Install Zip directly from PC (Required TWRP on phone)(These functions work perfectly on my pc but i have perfect adb drivers on my pc and perfect TWRP on my phone)
Flash Fastboot ROM
Delete downloaded files
ADB File Manager
DEVICE LIST
If you want you can send a request to add a new device here:
New Device Request Form
Device List
DOWNLOAD
Original Thread
DONATE LINK
If you want to support the project please consider making a donation, thanks.
Finally i got a solution for Nexus and Pixel Factory Image flash, now it works perfectly
Nice looking tool.
I'm surprised by the lack of comments on this thread. I'm looking at getting a Pixel 2 5". Is it this easy to just plug in and use this tool to root?
typhoonikan said:
Nice looking tool.
I'm surprised by the lack of comments on this thread. I'm looking at getting a Pixel 2 5". Is it this easy to just plug in and use this tool to root?
Click to expand...
Click to collapse
I'm surprised too, I do not know the reason sincerely
neat, been in debate on flashing but it doesnt seem like theres anything besides recovery and kernels. Wonder why the pixels have such a low rom rate. Even my pixel c doesnt have a root/rom option still.
tevil said:
neat, been in debate on flashing but it doesnt seem like theres anything besides recovery and kernels. Wonder why the pixels have such a low rom rate. Even my pixel c doesnt have a root/rom option still.
Click to expand...
Click to collapse
Perhaps because the cost has become excessive? Or maybe because there is no more reason to do modding? There are no more a rom like CyanogenMod
thank you!! :good::good::good::good: i have been hoping for something like this to be released. been missing the nexus toolkit. hopefully its working well. :fingers-crossed:
I'm interested in trying to see if this will actually unlock my bootloader
---------- Post added at 09:09 AM ---------- Previous post was at 09:05 AM ----------
My OEM unlocking has been greyed out and I haven't been able to unlock bootloader so I can root. Could this help me?
BrianMDenby said:
I'm interested in trying to see if this will actually unlock my bootloader
---------- Post added at 09:09 AM ---------- Previous post was at 09:05 AM ----------
My OEM unlocking has been greyed out and I haven't been able to unlock bootloader so I can root. Could this help me?
Click to expand...
Click to collapse
You need to enable oem unlock in developer options and then you will able to unlock your bootloader
mauronofrio said:
You need to enable oem unlock in developer options and then you will able to unlock your bootloader
Click to expand...
Click to collapse
Oh okay, I still can't do that. Always greyed out.
BrianMDenby said:
Oh okay, I still can't do that. Always greyed out.
Click to expand...
Click to collapse
If it's greyed out, then u have to do a factory reset. However, it still wont unlock it.
I had the same problem when I was trying to unlock my phone's bootloader, but it failed every time, so I'm just waiting if anyone is able to unlock it.
My phone's (Pixel 2) Android version is 8.1.0 and patch level is March 5, 2018.
Let me know if it works out for you.
Thanks
ahmadhas said:
If it's greyed out, then u have to do a factory reset. However, it still wont unlock it.
I had the same problem when I was trying to unlock my phone's bootloader, but it failed every time, so I'm just waiting if anyone is able to unlock it.
My phone's (Pixel 2) Android version is 8.1.0 and patch level is March 5, 2018.
Let me know if it works out for you.
Thanks
Click to expand...
Click to collapse
Sounds like you guys got the Verizon model Pixels?
Sent from my Pixel 2 using Tapatalk
BrianMDenby said:
Oh okay, I still can't do that. Always greyed out.
Click to expand...
Click to collapse
Verizon phone?
usernametaken53 said:
Verizon phone?
Click to expand...
Click to collapse
Yes, sadly, lol
usernametaken53 said:
Verizon phone?
Click to expand...
Click to collapse
BrianMDenby said:
Yes, sadly, lol
Click to expand...
Click to collapse
Verizon branded can't get their bootloaders unlocked at all :/
My phone is carrier locked, if I unlock it, can I enable oem? I'm on ee
Connor1744 said:
My phone is carrier locked, if I unlock it, can I enable oem? I'm on ee
Click to expand...
Click to collapse
I don't know it, but maybe it can work
Hi all,
Did any1 tried to downgrade security patch using this tool??? (Pixel 2)
There once was a window...
BrianMDenby said:
Yes, sadly, lol
Click to expand...
Click to collapse
Connor1744 said:
My phone is carrier locked, if I unlock it, can I enable oem? I'm on ee
Click to expand...
Click to collapse
There was a brief period of time where a bunch of us got our VZW Pixel 2's bootloaders unlocked, the mega thread is here https://forum.xda-developers.com/pixel-2/help/maybe-stupid-question-verizon-pixel-2s-t3726294/post74983838#post74983838, but from what I've read the firmware was patched in February that closed this window/loophole. Also carrier unlocked != bootloader unlocked, it just means you can use it on any carrier's network. Has nothing to do with OEM Unlock in Developer Options. Hope that helps.
With the new update a i make a new recovery flasher option for devices with project treble. Test it and told me if it works
Hi, i succed to gain temp root acces in my device (bootloader allowed no) which running in latest oreo firmware. This exploit uses CVE-2019-2215 for 3.18 kernel. I also succed to setup magisk manager from this thread. I hope this exploit can help you to backup your TA.img before unlocking bootloader.
Btw, i need someone to be a tester for this exploit, i will send it if you want to be a tester.
{
"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"
}
mufidmb38 said:
Hi, i succed to gain temp root acces in my device (bootloader allowed no) which running in latest oreo firmware. This exploit uses CVE-2019-2215 for 3.18 kernel. I also succed to setup magisk manager from this thread. I hope this exploit can help you to backup your TA.img before unlocking bootloader.
Btw, i need someone to be a tester for this exploit, i will send it if you want to be a tester.
Click to expand...
Click to collapse
Hello and congratulations for succeding with that!
I recently received a bootloader locked G8231 and I'd be willing to test your exploit on it. Now I have both an unlockable and a non-unlockable (Japanese Docomo release) units. I read through the link you posted and seems pretty interesting to say the least. I'd like to hear more about your version of the exploit, and I'd like to contribute by testing it on either model.
Feel free to reply or PM me.
Can i know and have the way to temporary root xperia xzs. I badly need it to improve the performance of my device. Thankyou so much
Hah, I just updated my thread from about a year ago on the subject of getting temp root. Though it seems like nothing has been publicly released on this thread here, so hopefully my post will still prove to be helpful (I found an already-built version of the exploit that just happens to work right out of the box on the XZs with stock Oreo!)
nlra said:
Hah, I just updated my thread from about a year ago on the subject of getting temp root. Though it seems like nothing has been publicly released on this thread here, so hopefully my post will still prove to be helpful (I found an already-built version of the exploit that just happens to work right out of the box on the XZs with stock Oreo!)
Click to expand...
Click to collapse
Wow it's great to hear something other than crickets here
After waiting over a month for a reply, I didn't have much hope for this thread.
Luckily, my XZs is still locked
I will definitely attempt your method and report back (as soon as I find a bit of time).
UPDATE:
Thanks a lot for the find @nlra !! The exploit works like a charm on latest Oreo. And YES, I just dumped the TA partition on my XZs.
Go ahead and read this comment in his post.
dinosaur99 said:
Wow it's great to hear something other than crickets here
After waiting over a month for a reply, I didn't have much hope for this thread.
Luckily, my XZs is still locked
I will definitely attempt your method and report back (as soon as I find a bit of time).
UPDATE:
Thanks a lot for the find @nlra !! The exploit works like a charm on latest Oreo. And YES, I just dumped the TA partition on my XZs.
Go ahead and read this comment in his post.
Click to expand...
Click to collapse
Hello, could you tell me the procedure for temproot my xzs SO-03J docomo device please? Thank you in advance.
AlexHunt099 said:
Hello, could you tell me the procedure for temproot my xzs SO-03J docomo device please? Thank you in advance.
Click to expand...
Click to collapse
As far as I remember, I copied the mentioned file su98-memory-kallsyms to /data/local/tmp and made it executable. I can't test it now but it's probably something like this:
adb push su98-memory-kallsyms /data/local/tmp
adb shell chmod 755 /data/local/tmp/su98-memory-kallsyms
adb shell /data/local/tmp/su98-memory-kallsyms
Afterwards I can just run /data/local/tmp/su98-memory-kallsyms from a terminal app.