Right, so you’ve got your bootloader unlocked and/or custom ROM flashed and now want to get everything back to stock. The stock TrackID and the Like app don’t work (ERROR 5) however due to the DRM stuff.
So here’s your workaround. All you do is to get the trackID.apk off market and push/ replace it to system so it works. You wouldn’t get DRM back though, but this is as close as you’ll get to the stock thing. There may be alternate ways to do this but this tutorial lists the exact way I did it (trying to avoid root and custom kernels).
The result was that I finally did get TrackID working on stock firmware after relocking the bootloader. Furthermore, it did work after an OTA update as well. I did use an Xperia Pro MK16i but since everything is rather general, it should work on any phone.
What you'll need:
Yaffey
Flashtool
A .zip extractor (would recommend 7-zip)
The attached TrackID.apk
Unlocked bootloader
Fastboot drivers (You may have installed it while unlocking your bootloader. If you haven’t, go here and start at step 8 and end at 15)
Step 1: Flashing stock firmware.
1. Find the required .ftf firmware file.
2. Download and install Flashtool/
3. Use this guide understand how Flashtool works and flash the downloaded firmware.
Now you should have stock firmware running on the phone. It doesn’t have root and neither do we need it as long as we still have the unlocked bootloader.
Step 2: Creating an edited .IMG file (which has the working TrackID.apk)
Note: You don’t need your phone for this step so keep it aside for now.
4. Using 7-zip (or whatever) extract the contents of the .ftf file that you just flashed onto the phone to a folder- you’ll find several .sin files.
5. Open Flashtool. Got to Advanced> SIN Editor and browse to the system.sin file you just extracted. Hit ‘Dump data’. You’ll find that it just created a system.yaffs2 file in the same folder which had the .sin file. Close Flashtool.
{
"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"
}
6. Now, download and open up Yaffey. Click the open tab and browse to the system.yaffs2 file and open it. Close the summary tab.
7. Expand the ‘app’ tab, find trackid.apk and delete it.
8. Highlight the ‘app’ tab again and click import. Import the trackid.apk file which is attached below.
9. Find the apk you just imported and edit the properties to what’s shown in the pic (-rw-r--r--). Hit OK.
10. Now click ‘Save As’ option and type in the ‘.img’ extension before you save it anywhere you like. Close Yaffey. You’ve created the .IMG file.
Step 3. Flashing the .IMG file via fastboot.
11. Switch off your phone and connect it via fastboot mode. Was holding menu while inserting the cable on the MKI6i but might be different based on your phone model. You should get the blue light once it’s connected.
12. Open command prompt wherever you have fastboot drivers installed. Enter this command - fastboot.exe -i 0x0fce getvar version (just to verify that you’re properly connected, you should get some response back)
13. Now hit fastboot.exe flash system C:\system.img (OR WHEREVER YOU HAD SAVED THE .IMG FILE, I saved it in C:\)
14. Let it do its work and you’re done. Hit fastboot.exe reboot , remove the cable and wait till your phone boots.
TrackID should work fine now and all that’s left to do is to relock your bootloader. Follow Bagus’s thread by flashing the file via Flashtool and you’re done. Completely stock, Track ID works and the bootloader is locked.
FAQs
Why the long process? Can’t I just flash the file via CWM recovery?
Like I said, I wanted to stick to as much ‘stock’ as possible. Hence didn’t feel like rooting it or flashing a custom kernel etc. Stock firmware, edited stock system.img was as close to stock I could get. But if you do feel that an alternate method may suit you better, feel free to do so.
I get a ‘Failed’ error in step 13?
Make sure your bootloader is unlocked. If you did relock it earlier, then unlock it again using the instructions on the SE page, complete this tutorial and relock it. Doesn’t really matter how many times you unlock/relock.
Why use the TrackID.apk you provided?
The attached apk is the latest version and I edited the icon image to make it look like that of the stock TrackID. (There is a difference in the icon image of the one present stock on the phone and the app you get off market). If the icon image doesn’t matter to you, you can use any TrackID.apk file. But make sure it isn’t the stock app which requires the DRM bit as it’ll be nothing but a huge waste of time then.
PS. As the attached .apk is edited, you may get an error message if you try installing it as a user app. Follow the tutorial and you should be fine. It may be fine for flashing via CWM as well but I haven’t tested that.
Such a long process, and just to get TrackID working? Are ya freakin’ crazy mate?
Umm, yes I am.
Will FB music like app work as well?
It should as it’s linked to TrackID. Would appreciate if someone reports back on whether it does or not.
Would this bring back warranty?
Well, that is the main reason I decided to do it in the first place. After doing this, mine was covered under warranty, and they sent me a new device as something was wrong with the memory card reader of the old one. But again, I may have been lucky as they may have other ways to check the DRM status.
PS. This is my first tutorial on XDA. It’s just me sharing what I’d done to make sure my phone gets covered under warranty. I will not be responsible if your phone doesn’t get covered under warranty or if you managed to mess up the steps mentioned. This tutorial, and any tutorial for that matter, should be carried out at your own risk.
Why don't you just install TrackID from Play Store?
And FB Music Like button requires DRM keys if I am not mistaken.
Someguyfromhell said:
Why don't you just install TrackID from Play Store?
And FB Music Like button requires DRM keys if I am not mistaken.
Click to expand...
Click to collapse
Well, the idea was to replace the TrackID system app with the one that works instead of having two of them in the app drawer. To me, it was more of a pre-warranty situation and I just felt the need to get everything as much 'back to stock' as possible.
As for the FB Like, I'm really not sure and did mention as well that it's not tested. I remember coming across somewhere that the both are interlinked or something, so just thought that might work as well, not sure though.
Can someone just replace the market trackid widget back to the stock one?
Sent From My Sony Xperia Arc S
Related
Hope I'm not stepping on any toes, but here goes.
Are you these guys?
{
"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"
}
but you want to be these guys?
Okay, so you've read Mills' instructions and sort of understand them.
1. Download the CWM recovery from multiupload
2. Boot off of that file (DO NOT FLASH): fastboot boot recoveryPLAY.img
3. Copy this to your memory card and flash it with the booted recovery
4. Reboot and test root
Click to expand...
Click to collapse
Right? Okay, let me translate all that for you.
First things first, you need to unlock your bootloader. To do so
Mills00013 said:
Obtain a bootloader unlock code. Right now the only way to get one is through ashergray or myself. This will change soon but for now its limited in release.
Once you have your code, follow the unlock instructions on either Sony's website directly or by following the instructions here. Please note that you already have your code at this point so if you follow the instructions please disregard anything telling you to obtain a code. These are for GSM models.
Click to expand...
Click to collapse
So kindly ask one of them for your unlock code, and my best suggestion would be to get everything ready so you can unlock the bootloader and flash the booted recovery all in one go.
So download the recoveryPLAY.img and set it aside.
Then download the RootXperia.zip and set it on your SD card in the root directory. So in the main F:\ folder.
Download the drivers and fastboot.exe here http://www.multiupload.com/RS6367SQMT
Okay, we got everything. Follow these instructions http://www.theandroidsoul.com/how-to-unlock-bootloader-xperia-arc-play-neo-pro/ starting at step 6 but please read my notes below also
at step 7, you will hold down the SEARCH button and plug the USB cable into your phone.
When you go to look for the Driver in Step 10 of the guide look for the one on the list that says "Android Bootloader Interface 2.0.10.2 Google, Inc. c:\?????\oem28.inf", that's the one I used.
Once the drivers installed you can locate fastboot and run it, but do this in the command prompt. So you know, go to Start > Run..> type in "cmd" and your command prompt comes up. Type in "cd\" to get to your root directory, then type in "cd c:\documents and settings\.....whateverfolder you have fastboot.exe sitting in"
So Step 13 of the guide, you're in the ...\fastboot\ folder, you can now type in fastboot.exe -i 0x0fce getvar version and that will tell you if you're connected. If you get a <waiting for device> you probably loaded the wrong driver. </life>
If not, then you got the 0.3, so continue with unlocking your bootloader in step 15. Put in your command and the key you got from some really helpful people.
Okay, so you just unlocked the bootloader, awesome. Don't close any windows. Now remember that "recoveryPLAY.img" we set aside? Go get it and move it into the same folder that you have fastboot.exe in.
# Boot off of that file (DO NOT FLASH): fastboot boot recoveryPLAY.img
Click to expand...
Click to collapse
Okay, with your command prompt still open and your recoveryPLAY.img in the same folder as fastboot.exe, type in "fastboot.exe boot recoveryplay.img"
Copy this to your memory card and flash it with the booted recovery
Click to expand...
Click to collapse
In about 10 seconds the screen on your phone will change, you will now see the recovery screen on your PLAY. The volume buttons are UP and DOWN, the power button is ENTER or SELECT. So navigate through the menus to install .zip from SD card, and look for the RootXperia.zip (we put it on your SD card earlier remember?). So you found it, Select it, it will run, the phone will tell you life is great, so scroll up to the top and back out until you see the option to reboot your phone.
Reboot and test root
Click to expand...
Click to collapse
Select Reboot and once you come up, go to the Android market and download something that requires Root, such as Titanium Backup or ROM Manager.
Finally, thank everyone involved for making this happen. Here http://forum.xda-developers.com/showthread.php?t=1098131
I did this on Windows XP, so I'm not sure if everything is exactly the same for any other Windows OS. Mods, feel free to move, delete or what you please with this thread.
Thanks a lot!!
Sent from my R800i using XDA App
Oh, my, gosh! THANK YOU SO MUCH! You don't know how much this means to me!
Thanks 4 dummie guide for noob people like me!!!!!
“S1Boot Fastboot” under the head “Other devices” i dont have that in my device manager
i cant seem to find "Android Bootloader Interface 2.0.10.2 Google, Inc. c:\?????\oem28.inf"
either...
my device manager says:
Android ADB interface under Android Phone
and
PCI input Device under "Other Devices"
To find s1 boot, you need the BLUE LED on
Sent from my Xperia PLAY R800i using XDA App
yea, i know
blue led light is still on
Thank you very very much for this simple and easy to follow guide. I have a very basic knowledge of all of this and many of the guides posted required I fill in gaps I didn't know how to fill.
Thank you!
Android ADB interface under properties says 2.0.10.2 Google
but i tried to update it with the folder and it said it was up to date....
In the cmd windows type in fastboot.exe -i 0x0fce getvar version
If a value is returned, it means the phone is correctly connected
Sent from my Xperia PLAY R800i using XDA App
dont know wtf i was doing but it finally connected to the phone, bootloader unlocked! just installed rootxperia.zip file bout to see what happens next.
hmm
i hit the power button (select) to reboot system but nothing happens. just momentarily turns screen off and on. i cant select anything now... stuck in clockworkmod recovery app
should i just unplug battery and replug?
KGB920 said:
hmm
i hit the power button (select) to reboot system but nothing happens. just momentarily turns screen off and on. i cant select anything now... stuck in clockworkmod recovery app
should i just unplug battery and replug?
Click to expand...
Click to collapse
to clarifie things - the search button is [select] on the play
FYI, the original method for obtaining unlock codes from Ashergray or Mills has been blocked by Sony. Now, the only way to unlock has to be done through Allejandrissimo, and costs money.
A free solution is being worked on, but we are nearly back to square one as far as unlocking goes.
crono141 said:
FYI, the original method for obtaining unlock codes from Ashergray or Mills has been blocked by Sony. Now, the only way to unlock has to be done through Allejandrissimo, and costs money.
A free solution is being worked on, but we are nearly back to square one as far as unlocking goes.
Click to expand...
Click to collapse
how much money?
because I'm getting so tired of running out of space every time I download an app
Halfway down the page Androhero has a (non-rooted) way to free up space (it works, I have anout 100 apps with 100mbs free)
http://forum.xda-developers.com/showthread.php?t=1194570
Sent from my R800x using XDA App
Bump for helpfullness and newbie R800X'ers.
does this still work?
thirday_95 said:
does this still work?
Click to expand...
Click to collapse
No.
tq mates, such info
First:
Warning! This is only for A70B/A70IT2 Honeycomb model, It won't work on Froyo model!
Here is a package that enables unofficially SDE menu in recovery and install a rooted stock firmware with busybox and SuperUser.Apk
Pre-Requisite:
- Adb must be enabled on tablet and PC driver+adb command must be working. You can test on pc with "adb shell", it should give you a '$' prompt. If you don't have this, first make it work. There are multiple links around to help if needed.
Instructions:
- Unzip files on your pc in adb.exe directory.
- Launch enable_sde.bat on your pc. It's better to do it in a cmd.exe window, you'll be able to copy-paste log here if anything goes wrong.
- Follow instructions in the cmd window. Basically, script reboots tablet multiple times, you have to press enter when tablet is completely booted each time.
- Congratulation, your device is sde enabled and has a rooted sde firmware. Please read below for more information.
Upgrades:
If you already installed a first version and enabled sde already, here is how to install new rooted firmware:
- Optional: flash updated stock firmware. I always recommend to match stock firmware, it avoids dalvik-cache rebuilds and bootloaders may have been updated in new firmwares.
- Boot rooted firmware. You should be running rooted firmware if you want upgrade script to work. To be sure of that, you should see SuperUser app in your apps menu.
- Unzip files on your pc in adb.exe directory
- Launch upgrade.bat (or upgrade.sh for linux)
- Tablet reboots at the end to rooted firmware and should be upgraded to new version.
SDE information:
1) What is SDE?
SDE (Special Developer Edition) is basically a dual boot mechanism. It allows us to dual boot Archos stock firmware and our custom ones.
2) How does it work ?
I won't give much details on how to use it, I should do a separate topic about this one someday. Until then, here is some basic information:
- At the end of this script, you are booted with sde firmware, superuser should be in your start menu and you should be root with adb or any root app.
- If you reboot or boot, press volume up while booting, it will display the dual boot menu. Select "Developer Edition", it will start the rooted build (check here point 9 to see how it looks).
- If you missed volume key or don't do anything during reboot, you will go back to unrooted stock firmware. You have to press the volume up key during boot to get the boot menu.
- Warning: booting stock firmware is harmless except that you will loose your SuperUser.apk preferences. As it's not part of stock firmware, Android clears it.
- You can boot straight to rooted firmware by deleting the stock firmware kernel in recovery. Check here, do point 4,5, and on screen 6, select "Remove Android Kernel". Make sure that you have properly working SDE firmware before doing that. If you want to re-enable back stock firmware, just flash it from recovery again.
Downloads:
3.2.80 can be downloaded here: Mirror 1 (Mediafire), Mirror 2 (Sendspace).
3.2.81 can be downloaded here: Mirror 1 (SendSpace) (bat fixed)
Sorry, Mediafire no longer let me upload without signup, if you know one good upload location without registration and allowing more than 200 MB, let me know.
*reserved*
Registered just to say thank you!
Worked like a charm, and no problems using the shell script (I run Arch Linux)
Keep up the good work!
Thanks
I mean real thanks
Sent from my ARCHOS 70it2 using xda premium
EDIT:
Beautiful man, beautiful. Works splendidly
Thanks again
LeTama
Have a beer or two on me, 84G89322WT2139701.
Thanks again for your Rom.
Hi mrew42,
Thanks a lot! Much appreciated!
Tomorrow, my 70b return at home
I testing that !
but my 70bit2 is with 3.2.81
Letama, can you may be make the same for 3.2.81?
Yes, it will come soon...
3.2.81 is up and instructions on first post updated if you upgrade.
Great
http://www.jbmm.fr/?p=27601
{
"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"
}
cajl said:
Great
Click to expand...
Click to collapse
Nice job! Thanks for the article on jbmm!
Thanks, will try it out soon.
Thanks letama, this is just what I wanted. Awsome work!
I think there is an error in upgrade.bat and enable_sde.bat for 3.2.81.
The line that reads:
adb push android_32.ext4.update /media/
should read:
adb push android_32.ext4.update /data/media/
Also, upgrade.bat is missing the line that says:
adb shell rm /data/local.prop
Keep up the good work and thanks again.
ColinTaylor said:
I think there is an error in upgrade.bat and enable_sde.bat for 3.2.81.
The line that reads:
adb push android_32.ext4.update /media/
should read:
adb push android_32.ext4.update /data/media/
Click to expand...
Click to collapse
Ah! Right! Thanks for pointing it, I'll fix that and re-upload when I find time to do it.
Also, upgrade.bat is missing the line that says:
adb shell rm /data/local.prop
Click to expand...
Click to collapse
Yes, this is normal, this one is only needed when enabling sde first time. local.prop is coming from temp root and won't be there anymore.
I finally had time to try it out tonight, all seemed to be installed fine, but I don't see the Superuser in the apps list... I can boot into developers fw menu though. Did I miss something or should I just try to reinstall the SDE again by running that bat file again?
No, as ColinTaylor said, there is a typo in script, you just need to push the ext4.update at root of storage.
Just type this command in the directory you unzipped the files:
Code:
adb push android_32.ext4.update /data/media/
then boot sde.
Hello
As i have read your post about how to root 3.2.81, the instructions seems to confuse me, but what do you mean by adb? im sorry im kinda new at this ,please let me know thanks!
hello, first of all thanks for your work.
I am having some problems with the upgrade file.
it says that it cannot stat 'zImage':no such file or directory
and secondly it cannot open the kernel file (no such file or directory) mkf lashimage failed.
could you please provide some help with this?
thanks!
lozano.markp said:
Hello
As i have read your post about how to root 3.2.81, the instructions seems to confuse me, but what do you mean by adb? im sorry im kinda new at this ,please let me know thanks!
Click to expand...
Click to collapse
adb is a developer tool from android sdk that let you execute commands on your tablet from your PC. You have to install android sdk to get it, you need to enable it on the tablet and have a proper driver.
OK, I just did another rescue script, it's using the files from the final release but it will install them one at a time using your computer instead of trying to install the rom.
THIS GUIDE IS FOR WINDOWS ONLY!
If someone else wants to convert it for Linux/OSX feel free but please make a new thread with a similar format to the title as this one but with [Linux/OSX]
Bear in mind this script will also install the compatible TWRP version 3.0.2.0 which will work with the final OOS3 and also with the new codebase in CM13 unless you sideload the complete rom in which case that will install the default OnePlus recovery. You can always install TWRP using the files within after this anyway
Anyone who wants to give it a go can download it at the link below, remember IT'S NOT A FLASHABLE ZIP, it's the files packaged into a zip.
Download here from Android FileHost : https://www.androidfilehost.com/?fid=24580943222146240
Carry out the following instructions as I have entered them.
Unpack the zip file into a folder, possibly on your desktop so you can see all the files easily.
Reboot your phone into fastboot mode by holding down the VOLUME UP button while holding the POWER button until you see fastboot mode show, obviously make sure you have connected the phone to your computer via usb cable.
If you have not unlocked your phone then immediately go watch the video below to find out how to do so then come back and continue the instructions from step 4.
https://www.youtube.com/watch?v=KZaajUEybNM
Open an elevated prompt window in the folder you unpacked the zip into (elevated means it has administrator privileges), to do this, right click in the folder (not on a file) while holding the SHIFT key, then choose "Open command window here", see below:
{
"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"
}
You may be prompted to allow admin privileges, say yes.
In the command window you opened type the following:
fastboot devices
You should then see something similar to the screenshot below:
If you don't see a number followed by fastboot then you need to install or re-install your drivers. (I've uploaded the latest version to Android FileHost here : Download, remember to restart the computer before proceeding)
If you do see something similar to the above, then type the following into the command window:
fixoos
Then press enter, now adb will flash the different new versions of the partitions needed to either install the rom or reboot into the new version of TWRP.
It should look like this (I've shrunk the text to try to fit it all in) :
The last 2 steps in the script are going to flash the new compatible TWRP as your recovery partition and then it will also reboot into that version of TWRP.
All of this presumes that you were able to copy whichever rom you want to install onto your phone.
If you did not copy the rom onto your phone then download it the link below :
https://www.androidfilehost.com/?fid=24580917854994435
Copy the file into the same folder as the rest of the files and then run the following in the command window :
adb sideload OnePlus2Oxygen_14_OTA_019_all_1606041303.zip
(If you start typing the filename and press TAB it should autocomplete the name as long as the zip file is in the same folder as you opened the command window in)
Now press enter and ADB should install the full release rom itself, bear in mind, this will NOT include the new TWRP as TWRP is not a part of the default rom.
Please post any problems you have below, however, as long as you follow the instructions properly you should be ok.
djsubterrain said:
OK, I just did another rescue script, it's using the files from the final release but it will install them one at a time using your computer instead of trying to install the rom.
THIS GUIDE IS FOR WINDOWS ONLY!
If someone else wants to convert it for Linux/OSX feel free but please make a new thread with a similar format to the title as this one but with [Linux/OSX]
Bear in mind this script will also install the compatible TWRP version 3.0.2.0 which will work with the final OOS3 and also with the new codebase in CM13 unless you sideload the complete rom in which case that will install the default OnePlus recovery. You can always install TWRP using the files within after this anyway
Anyone who wants to give it a go can download it at the link below, remember IT'S NOT A FLASHABLE ZIP, it's the files packaged into a zip.
Download here from Android FileHost : https://www.androidfilehost.com/?fid=24580943222146240
Carry out the following instructions as I have entered them.
Unpack the zip file into a folder, possibly on your desktop so you can see all the files easily.
Reboot your phone into fastboot mode by holding down the VOLUME UP button while holding the POWER button until you see fastboot mode show, obviously make sure you have connected the phone to your computer via usb cable.
If you have not unlocked your phone then immediately go watch the video below to find out how to do so then come back and continue the instructions from step 4.
https://www.youtube.com/watch?v=KZaajUEybNM
Open an elevated prompt window in the folder you unpacked the zip into (elevated means it has administrator privileges), to do this, right click in the folder (not on a file) while holding the SHIFT key, then choose "Open command window here", see below:
You may be prompted to allow admin privileges, say yes.
In the command window you opened type the following:
fastboot devices
You should then see something similar to the screenshot below:
If you don't see a number followed by fastboot then you need to install or re-install your drivers. (I've uploaded the latest version to Android FileHost here : Download, remember to restart the computer before proceeding)
If you do see something similar to the above, then type the following into the command window:
fixoos
Then press enter, now adb will flash the different new versions of the partitions needed to either install the rom or reboot into the new version of TWRP.
It should look like this (I've shrunk the text to try to fit it all in) :
The last 2 steps in the script are going to flash the new compatible TWRP as your recovery partition and then it will also reboot into that version of TWRP.
All of this presumes that you were able to copy whichever rom you want to install onto your phone.
If you did not copy the rom onto your phone then download it the link below :
https://www.androidfilehost.com/?fid=24580917854994435
Copy the file into the same folder as the rest of the files and then run the following in the command window :
adb sideload OnePlus2Oxygen_14_OTA_019_all_1606041303.zip
(If you start typing the filename and press TAB it should autocomplete the name as long as the zip file is in the same folder as you opened the command window in)
Now press enter and ADB should install the full release rom itself, bear in mind, this will NOT include the new TWRP as TWRP is not a part of the default rom.
Please post any problems you have below, however, as long as you follow the instructions properly you should be ok.
Click to expand...
Click to collapse
Linux version -> http://forum.xda-developers.com/oneplus-2/help/linux-fixing-script-boot-looping-oos-3-t3395736
Most threads are really old, so I am starting a new one.
And one of better ones was just locked and deleted
I have Xperia Z2 D6503 with locked bootloader.
Sadly at this moment pretty much every single thread you find is 5+ years old and most links are dead.
You can find those files online but question is are those same files you need.
You might download the wrong file with same name.
So I will either update the links if I find the files or I will link the best root method if any at this present time.
And if you have any files or info to share, do so here.
So far,as of creation of this thread, nothing is available.
Ok so I will just update you with news.
I found everything I wanted from Russian folks at 4pda, simply put, once again Russians come trough when no one else could.
Spoiler: My rant
Funny thing, I always knew I should learn Russian and German, for doing things no one else can and fixing stuff, those two places/nations are simply THE best.
LIterally every time I needed something I found it on a Russian website, and every time I needed to fix something, some cool German helped out.
I am attaching the archive with all files needed to root the Xperia Z2 with locked bootloader, with instructions inside, do this at your own risk as usual.
Btw since I plan to host these files forever they should be available at all times as long as these hosts dont remove em.
Please dont contact me if they don't work, I only keep them there, I dont have them on my PC
Spoiler: DL here
Mega
Spoiler: DL here
Yandexdisk
https://disk.yandex.com/d/O-C06nagysIqQg
So I managed to root my Xperia Z2 with locked bootloader !
{
"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 would like to document my little journey here for anyone who might need help.
So first flashed the stock firmware by downloading it via XperiFirm+5.6.2+(by+Igor+Eisberg)
But that tool only downloads "File" files, it downloaded 4 of them, but you need only one FTF file.
So I used FlashTool 0.9.34.0(also called Sony Mobile Flasher by Androxyde), it has a tool, Tools > Bundles > FILESET decrypt and by following the Youtube video I used that tool to create the FTF file I needed but for some reason the FlashTool put that FTF file in C:\Users\USERNAME\.flashTool\firmwares
I also needed to install the the drivers for my phone as well as fastboot drivers, this is covered in the original guide that I included in the archive above.
Steps 7,9 and 10.
Btw sorry if I skip something I did, you can fill in the gaps, I'm sure.
Anyways after FlashTool detected my device I flashed the stock firmware(23.5.A.1.291).
Then comes the moment of rooting.
So all the drivers are installed, files are there and nicely organizd, I am ready.
I opened both guides, the original one and Russian one translated to English.
Turned out both added up together to create the ultimate guide, I will explain why in a minute.
-Put the files on SD, check;
-Rename the 575 kernel files extension to .TFT , check;
-Turn off the phone, check;
-FlashTool is opened and waiting,check;
-At this moment I actually clicked on lightning bolt icon, then I clicked Flashmode and then under Source folder I located the folder where 575.tft kernel file is located.
Then I selected THE FOLDER
After that under Firmwares, the 575 kernel shows up and I go trough drop down arrows to click on it 23.5.A.0.575.
Then I click on kernel.sin in Content section.
Then under Device filter I double click and find Xperia Z2;
-At this point I slide the Firmware Selector window to the right and I don't close it, so I can see the console and what Flashtool is reporting, the console would be the part where Flashtool is writing something, all that text under those big icons(lightning bolt,BLU,lock,key..)
-After that I hold the volume down and connect the USB cable to the phone
And I notice Flashtool tells me phone is connected in flashmode
-I click Flash in the Firmware Selector window that was still open
-It does its thing and reports success.
-I disconnect the phone and close the Flashtool as Russian instructions also recommend it, dont skip this
-I turn on the phone, all boots fine and I do check the kernel by opening the service menu(dial *#*#7378423#*#* and find Service info, first line Phone software version at the end theres .575)
Actually at this point I had minor ****pants moment, Service menu wouldn't open instantly, took about 20 seconds
-Then I proceeded to flash the recovery
But here I ran into the problem, error adb server version (40) doesn't match this client (36)
That is because 3 files inside Recovery_for_MM575-291>files folder, named
adb.exe , AdbWinApi.dll , AdbWinUsbApi.dll
need to be replaced with version 40.
So I browsed online and downloaded platform-tools_r28.0.2-windows
Here is where you can find more versions
adb-win/SDK_Platform-Tools_for_Windows at master · awake558/adb-win
adb.exe fastboot.exe. Contribute to awake558/adb-win development by creating an account on GitHub.
github.com
Theres a readme that tells you what file is what version.
So I extracted the archive and inside the platform-tools folder I found the 3 files, copied them and replaced those files I mentioned earlier located in Recovery_for_MM575-291>files .
-After that I run the install.bat without admin right actually and it all goes smooth.
-Instantly phone rebooted into recovery which made me smile
Also I pressed any key to continue and that closed the install.bat window that opened earlier on the computer.
-Then I installed SuperSU, no problem there.
-I press the arrow to go back,
-And find and finally install 291 kernel.
-After that I click reboot button
-Phone reboots without any issues.
Boom, rooted.
Hope and wish you all the best with rooting yours.
According to my experience and reanalyzing current status, I could give this as a permanent order for moving from Locked Bootloader to having a Magisk rooted ROM.
(Any error might be corrected, if an explanation is given.)
1) Flashtool's Flashmode
Flash D6503_23.5.A.0.575_kernel.ftf (which includes loader.sin and kernel.sin)
2) Backup TA partition with backupTA_v2 by Jens Andersen (XDA: rayman, Twitter: @droidray, GitHub: EnJens)
3) Reset to factory defaults
4) Unlock Bootloader
https://developer.sony.com/develop/open-devices/get-started/unlock-bootloader/
5) Flashtool's Flashmode
Flash D6503_23.5.A.0.575_kernel.ftf (which includes loader.sin and kernel.sin) again
6) Change recovery with (NEW)_Recovery_for_MM575-291v5 by executing its install.bat
Stay on Stock ROM:
Booting into TWRP
7) Flash root (SuperSU only)
UPDATE-SuperSU-v2.76-20160630161323.zip
8) Flash Z2_23.5.A.1.291_Marshmallow_Kernel_Flasher.zip by moman2000
Change to LineageOS:
7) Wipe cache, dalvik cache, data and system
8) Format data (for encryption removal)
9) Reboot into Fastboot mode
TWRP - Reboot to Bootloader
Flashtool - Fastboot mode
ADB - adb reboot bootloader
Volume down + Power on
10) Flash new kernel extracted from LineageOS
fastboot flash boot boot.img (fastboot flash:raw boot boot.img)
11) Flash new TWRP (twrp-3.3.1-sirius-20200221.img)
fastboot flash recovery recovery.img
12) Reboot into recovery for verification (Failsafe)
fastboot boot recovery.img
13) TWRP
Flash ROM
Flash Magisk
14) TWRP or as Magisk module
Install GApps or microG
change to ftf not tft!!!!
also great guide and thanks for the links and files basically everything
kakashi7593 said:
..it has a tool, Tools > Bundles > FILESET decrypt and by following the Youtube video...
Click to expand...
Click to collapse
Hi, Pls kindly give that youtube video link if it is still alive. I wanna know how to convert those downloaded file in to ftf format.
Rgds
I removed the bootloader warning on my S20+ and attached the .tar file you need to flash in the AP slot. Also wrote a quick guide how to do it yourself for other models or to personalize it.
I found a guide, original credit to this youtube video.
As a result I personally modifed several files in photoshop to remove all the bootloader unlocked warnings, etc, and also to remove all non-english text on the download screen, etc.
All you need to do if you have my exact phone is to
0. Make sure you have SM-G985F/DS (S20+) phone ONLY. Otherwise, skip to create your own assets or see if another user added your phone into this thread.
I. Boot into DL mode (either boot into TWRP and click download, or turn off phone and turn it on and hold VolUP+Power until it goes to recovery, or VolDn+Power and insert USB)
II. flash the file attached, up_param.tar that I have attached, under the AP tab in Odin. Yes, AP NOT BL!!
Success!
It might seem like boot is longer, but it's the same time, it's just now 3 separate screens are all the same one instead of extra screens with errors.
{
"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"
}
ABOUT THE MOD:
Changed this to just black, thus removing it:
Changed these 3 screens to the one after it (and positioned them perfectly):
Also changed some other ones by removing things like WARNING! and non-english text.
e.g.
In case you want to do it for other phones, I don't know if it's the same assets so I would NOT recommend to flash my exact file, but rather create your own using my assets I attached that I created. Open the original file in photoshop and you can do whatever you want to it.
To modify other phones, you need:
A. 7-zip Z-std (ZS) version (regular 7-zip doesn't work)
B. Odin (attached, or find it on XDA)
C. (Optional) Photoshop or photo editor app
HOW TO MODIFY OTHER PHONES ASSETS:
1. First extract up_param.lz4 using 7-zip ZS.
2. Now extract up_param.bin to its own folder.
3. Modify the assets however you like. You can personalize literally however you like, modify these pictures in any way and you get your own boot screens.
4. Open up_param.bin using 7-zip ZS FM (open and choose default as 7-Zip ZS FM, navigate to it),
5. Drag and drop your modified files into up_param.bin
6. Right-click and choose 7-zip ZS > Add to archive
7. Choose a tar archive and click OK
Then just do the first steps I & II at the top of this post to finish the flash.
Hope it helps!
Please add that it is only for Exynos version. On snapdragon it will not work
lukjod said:
Please add that it is only for Exynos version. On snapdragon it will not work
Click to expand...
Click to collapse
Not quite. It will work on Chinese variant that can unlock bootloader and anything that can unlock bootloader.
WILL NOT WORK ON US/CA DEVICES, DON'T TRY! (Bootloader will likely never be unlocked on those devices.)
Only use this if you have unlocked bootloader/rooted.
Use common sense.
Hope it helps.
p.s. I have an exynos version for the root. I'd rather have 8gb ram and unlocked bootloader than US locked bootloader trash with 12gb ram. That said I'd rather have a 5+ year old device than to not be able to unlock the bootloader/root.
Later I'm going to modify these screens with a dimmer version. I always hate rebooting my phone at night with that ultra bright glaring logo.
xbt- said:
Not quite. It will work on Chinese variant that can unlock bootloader and anything that can unlock bootloader.
WILL NOT WORK ON US/CA DEVICES, DON'T TRY! (Bootloader will likely never be unlocked on those devices.)
Only use this if you have unlocked bootloader/rooted.
Use common sense.
Hope it helps.
p.s. I have an exynos version for the root. I'd rather have 8gb ram and unlocked bootloader than US locked bootloader trash with 12gb ram. That said I'd rather have a 5+ year old device than to not be able to unlock the bootloader/root.
Click to expand...
Click to collapse
Well, I have EUR version of Z Flip 3 with snapdragon, rooted and with unblocked bootloader. Simply this way is ONLY valid for Samsung Exynos chipset and not for SNAPDRAGON. There is no up_param in Snapdragon.