Database Develop

[GUIDE][UB] Install CWM Recovery in Xperia T JB 4.3

Code:
Description:
Your warranty is now void.
I am not responsible if you brick your phone during the process.
Flash it at your own risk.
Sony’s mid range device Xperia T has been recently updated to Android 4.3 Jelly Bean. In the recent past Sony remained quite fair with the users in terms of Software updates keeping its promise at top, the Android Jelly Bean 4.3 update started reaching out the users taking the device one stop close to KitKat that is under investigation / testing by Sony at the moment. Well, the new firmware definitely needs new methods to run a CWM Recovery inside and a new method to get rooted as well. For those who have updated their devices to this new firmware and are now looking for a compatible CWM recovery, they have spotted the right place at the moment.
Here are some important installation instructions and pre-requisites:
This guide is only for Sony Xperia T. Do not try this on any other model, please check your device’s model in Settings > About Device.
The CWM recovery is only for Sony Xperia T running stock or stock based Android 4.3 [9.2.A.1.199] or [9.2.A.0.295].
Check your firmware version in Settings > About Device and make sure that it matches the one mentioned above.
You must have installed Android ADB & Fastboot drivers. Follow this link http://techbeasts.com/2013/12/18/install-android-adb-fastboot-drivers-quickly-with-minimal-tool-on-windows-pc/.
Your device must have an unlocked bootloader. Follow this link to unlock bootloader http://techbeasts.com/2013/12/18/how-to-unlock-bootloader-of-sony-xperia-devices-guide/
Please make sure that your phone’s battery is charged at least over 60%. This is highly recommended in order to prevent any power issues during the recovery flashing process.
Backup all your important data before flashing CWM.
Backup your current system using a custom recovery (CWM or TWRP) if you’ve flashed one. This is recommended in case something goes wrong with CWM installation, you can use the custom recovery and return to the old working state of your system.
Enable USB debugging mode on your device. Get it in Settings > Developer Options > USB Debugging mode.
Use working data cable to establish connection between your PC and Phone.
Alright! Follow this guide to the letter now.
How to Install CWM Recovery on Sony Xperia T:
Download Stock Kernel with CWM Recovery here http://www.mediafire.com/download/xwjdwcmpomn6wth/kernel_sj.elf
You will get a kernel_sj.elf file. Just rename it to Kernel.elf
Place the Kernel.elf file in the Minimal ADB & Fastboot folder that you created using our ADB & Fastboot Quick Setup Guide.
If you are using Android ADB & Fastboot full package, you can place the downloaded Kernel.elf file in the Fastboot folder or in the Platform-tools folder.
Open the folder where you placed the Kernel.elf file.(E.g Minimal ADB & Fastboot or Fastboot or Platform Tools).
Press and hold the shift key and right click on an empty area within the folder, and click on “Open Command Window Here”.
Turn off your Xperia T completely.
Now press the Volume Up Key and while keeping it pressed plug in the USB cable.
You should see a blue light in the notification light of your phone, that means your device is now connected in Fastboot mode.
Now type the following command: fastboot flash boot Kernel.elf
Hit Enter and it will quickly flash CWM recovery in your Sony Xperia T.
Once recovery is flashed, now issue this command Fastboot Reboot
Your device will reboot now(even if your device does not reboot do it manually). As soon as you see the Sony logo, and the pink LED, press Volume Up key to enter recovery.
Congrats! You should now see the custom recovery.
That’s All with the recovery installation. In case you got any queries or face any difficulties regarding this post, please feel free to stop by the comment box below and let me know. I will get back to you as soon as possible. Thanks all.

Attachments

Xperia V won't go into recovery

Hey there. I'm having a bit of an issue regarding the recovery on my phone. I rooted it quite some time ago but now I'd like to upgrade it to Kitkat 4.4.4 but when I try to enter recovery mode, it just boots normally. I have installed ROM Manager some time ago and I believe I may have changed my recovery, but it was either CWM or TWRP so there's nothing else. I tried using the "Boot into recovery" option but the phone won't go into recovery. I tried many different combinations upon boot but none have worked. Can someone help me, I'm running 4.3 9.2.A.1.210. I have USB Debugging enabled.
Cheers.

Most (or even all) of the custom roms have built-in recovery. So, if you want to flash some custom rom, you extract the "boot.img" from the zip and flash it via FlashTool using fastboot mode (to put Xperia V into fastboot mode hold volume up button while connecting the phone to tbe pc and the led should turn blue. If it turns green then try holding the other volume button.). And then you just select the lightning icon in FlashTool, choose fastboot mode, on the right side in the middle is an option to flash kernel and just find the boot.img you extracted and select it. Keep in mind that your bootloader must be UNLOCKED and you must install fastboot drivers before doing this.
Btw...your phone will stay in the fastboot mode only for a couple of seconds so you have to be quick...I always find the boot.img first, then put my phone into fastboot mode and then just select the image to flash it.
Sent from my Xperia V using XDA Free mobile app

2 Bootloader??

hi guys
ive a strange behavior with my Z1 (C6903).
i was trying some roms and prepared them for multiROM.
after i had problems with a rom i flashed via EMMA (XperiaFlashtool) FW 14.6.A.0.368 and the "TA Update". i recogniced that i wasn able to get into the AOSP-recovery, but if i press the button-combination Power+VolDown i get a bootscreen with "Sony" in the middle and "Xperia" at bottom, after then the phone seems to restart and presents me the bootscreen but just with "Sony" in the middle, then the Rom starts to start ....
this strange behavior makes it hard to get into TWRP.
it seems the phone starts its standard-bootloader and then starts another one
can someone help me to get again to "normal" state?

with flashtool friend relock bootloader and repair with pc compagnion sony !!!

i relocked bootloader with flashtool, but i cant do anything in PC Compagnion

You could try using fastboot to flash a fresh boot.img. This will get rid of the multirom.
1. Download a kernel (without multirom) you want to use.
2. Extract the boot.img from the zip file to the fastboot folder.
3. Power off and unplug your phone completely.
4. Hold the volume-up button and while holding it connect it to your computer.
5. Your notification LED will be blue if done correctly.
6. Open up fastboot and type in the following code:
Code:
fastboot flash boot boot.img
If it's a non-stock one you should unlock the bootloader again.
P.S.
You don't have two bootloaders, the bootloader is the thing that loads the kernel. Multirom uses the kexec hardboot patch to boot another kernel over the one that is already running, skipping the bootloader part. So it is most likely just multirom screwing up.

thx, m8 ^^
it seems your answer is the best choise ^^
i tried many things, but also flashing via fastboot wasnt so easy at first. it was very strange, it seemed that flashing was allways redirected to the second kernel/rom. after some tries i got it to work as "normal" again. i hope its "normal" now, cause i dont trust my phone anymore after this crazy jorney xD
yea, i think i screwed something up with MultiROM combined with DualRecovery ^^"

..
You could try using fastboot to flash a fresh boot.img. This will get rid of the multirom.
1. Download a kernel (without multirom) you want to use.
2. Extract the boot.img from the zip file to the fastboot folder.
3. Power off and unplug your phone completely.
4. Hold the volume-up button and while holding it connect it to your computer.
5. Your notification LED will be blue if done correctly.
6. Open up fastboot and type in the following code:
Code:
fastboot flash boot boot.img
If it's a non-stock one you should unlock the bootloader again.
P.S.
You don't have two bootloaders, the bootloader is the thing that loads the kernel. Multirom uses the kexec hardboot patch to boot another kernel over the one that is already running, skipping the bootloader part. So it is most likely just multirom screwing up.
Click to expand...
Click to collapse

[HOW TO] A simple way to ROOT your remix mini

I've made a pre-rooted boot image for Remix Mini. With this image, you can ROOT your Remix Mini without using UART/TTL cable.
Features:
1. Flash the boot image to root the device, without opening the cover.
2. Systemless root: the files in /system are unmodified. You are able to receive future OTA updates (in theory).
3. Factory Reset Protection: you can do Factory Reset in Remix OS or in Recovery mode without lossing root status.
Prerequisite:
A Remix Mini with stock ROM (Tested on my RM1G 8GB & RM1CL)
USB Male To Male cable
Android platform tools (fastboot & adb) on your computer
Steps: (Warning: Backup your data before doing anything)
1. Power on your Remix Mini, press F2 to enter Recovery mode.
2. Choose "reboot to bootloader" and press Enter key, then your Remix Mini will enter fastboot mode.
3. Plug the male to male USB cable into the UPPER USB port on your Remix Mini, then connect it to your computer.
4. Open command line (cmd on your Windows PC, or Terminal on your Mac, etc.), and check the device's connection with following command:
Code:
fastboot devices
5. Flash the boot image with following command:
Code:
fastboot flash boot <path to the boot.img>
6. When completed, reboot your Remix Mini with following command:
Code:
fastboot reboot
7. Your Remix Mini should reboot to Remix OS normally. Install Root Checker from Play Store or via USB drive to check root status.
Known issues:
It seems that SuperSU is not fully compatible with Remix OS. When an app is requesting root access, the dialog of SuperSU is invisable. You are not able to approve or deny the request, and app is hanging. There is a workaround, you can let SuperSU approve or deny all the requests without asking, and later change the per-app settings through SuperSU app.
Back to stock (Unroot or unbrick):
You may using Remix Mini factory image and Allwinner LiveSuite tool (just google them) to reflash your device to stock ROM.
Download link:
(Remove extra spaces in links. I can't post links right now - sorry.)
Code:
Dropbox: h t t p s :/ / www . dropbox . com/s/jmhpv0vq7nq83hq/remixmini_rooted_bootimg.zip?dl=0
Baidu: h t t p : / / pan . baidu . com/s/1bpcq3Iv Password: xn9s

@JustinLu123
Thanks a bunch! Works like a charm on my 16G Remix Mini.
As for the SuperSU invisible popup - try resetting SuperSU data or fiddling with windowed/fullscreen mode of SuperSU/other app. For me the popup works just fine.

Thanks for making this boot image public! It makes rooting a lot more simple.
Although I'm curious how you accomplished it. Is the original boot image not signed by JIDE? Does the Mini not check the authenticity of this signature?
If the boot image is signed and the Mini does check the signature, how could this modified boot image be put together (without having access to JIDE's private signing key)?
If there's no signature check, then how come that nobody (who already rooted the Mini and could read out the boot image from the Mini itself) published the original Mini boot image before? There's a huge Android modding community and modding boot images has a long history with a lot of docs and resources online. So once the original image became accessible, adding SuperSU (or whatever rooting solution one chooses) to an existing image is something that has been done before for lots of phones/tablets/etc..

Boot image can be extracted from publicly available official Mini ROMs used for manual install.
I guess he just pulled the boot.img, extracted it, modified and then repacked.
I've had this idea too, just didn't think it's worth the time since UART method was okay for me.
Since Mini has an unlocked bootloader you can just flash any boot image you want.
If you'll try to flash an update zip from Mini recovery, it has to be signed and follow some more requirements.
Happily, Justin overrode this by rebooting into bootloader.
Sadly, the original boot.img is automatically restored upon reboot... :/
If anyone knows what to do to make it stick, let me know.
Also, since Justin managed to root it via fastboot, maybe now it'll be possible to install Magisk?

@bit2
The bootloader of Remix Mini is unlocked, so we can extract and modify the boot image, and then flash it back though fastboot mode.
@Vioner
Yes, I extracted the boot image from latest OTA update package ver 2.0.805.
I didn't see the boot.img restored upon reboot. But the boot image may be replaced by OTA updates in the future. Just flash it again if it happens.

@JustinLu123
I've flashed your boot image like 10 times. It doesn't persist, so I went back to UART method.
Guys, please test for yourself if it persists.

@Vioner
Sorry to hear that the method isn't working on your device.
I've been using this boot image on my 2 Remix Minis (model RM1G and mode RM1CL) for 1 month+ and it does persist. I didn't see any drawback upon reboot or shutdown.

@Vioner
Which version of ROM are you using? I'm using ROM ver. 2.0.805.

@JustinLu123
2.0.807 - the most recent

@Vioner
I had reflashed / unbricked my device using Phoenix Suite with "verity_block" unchecked. The "verity_block" looks like the feature to secure the boot image. Maybe that makes the modified boot image persist on my device.

Let's see if it persists for others.
Maybe it's just like you said with verity check.

@JustinLu123
 @Vioner
i can't see any device in "FASTBOOT DEVICES"
PhoenixSuit 1.0.8 installed. USD Debug mode (the two settings on)
Windows 10 x64
What i'm doing wrong?

If you have USB debugging enabled, you may try entering fastboot mode through adb:
adb reboot bootloader
@Poeta

@JustinLu123
Have tried Recovery, choose the Bootloader... No fastboot devices detecter
I have tried that too... After enter in the bootloader... No fastboot devices detected.
Fastboot devices empty in the "Fastboot devices"

@Poeta
It looks like a driver issue. Try uninstall Phoenix Suite driver and install generic driver for fastboot device in Windows' Device Manager.

Hi
When i choose reboot to bootloader , it restarts and then its stuck on with Jide Logo
am i supposed to see some screen ?I did a factory reset but didnt help.
when i check fasboot devices its blank does not show any ?
Remix mini is detected using Phoenix Suite under usb debug mode
i tried adb reboot bootloader also it restarts remix mini but again stuck in boot loader..
How do i fix this ?
If i replace boot.dmg in the factory image and restore will it work ?

sunny5055 said:
Hi
When i choose reboot to bootloader , it restarts and then its stuck on with Jide Logo
am i supposed to see some screen ?I did a factory reset but didnt help.
when i check fasboot devices its blank does not show any ?
Remix mini is detected using Phoenix Suite under usb debug mode
i tried adb reboot bootloader also it restarts remix mini but again stuck in boot loader..
How do i fix this ?
If i replace boot.dmg in the factory image and restore will it work ?
Click to expand...
Click to collapse
I think that Jide logo is the fastboot.
@JustinLu or @JustinLu123 that is true?

It is @Poeta

Vioner said:
It is @Poeta
Click to expand...
Click to collapse
Then in that case not sure why i dont see anything under fastboot..
The drivers must be correct because i was able to use "adb reboot bootloader" this.
Anyone has the drivers link which have used and working ? I can try using windows 10 or osx again with those drivers.

Tried to run this from my phone using a microusb cable...
Didn't work. Can't get the phone to detect the mini.
So there's that.

[Nokia 1] Guide on acquiring root on Android 10 Stock ROM

Hey everyone, I no longer have this device, but, I guarantee that these steps will work and not brick your device if you follow them correctly!
PC side:-
1) Download the latest OTA update of android 10 for the Nokia 1 from here
https://android.googleapis.com/packages/ota-api/package/8f064e008ca0bb6616e4506f9c9c0f1d68257347.zip
2) Extract this file and you should see quite a few images, then copy the boot.img to your desktop for safety
Nokia 1 side:-
1) Update your Nokia 1 to the latest os either from the system update in settings or just copy over the .zip file we downloaded to a micro sd and apply the update from recovery
2) after you are on the latest update and no other updates are available, download the magisk canary apk from magisk GitHub and then install it
3) After that, copy the boot image we extracted earlier from the pc to the phone, then patch the copied boot image
4) After it's done flashing copy the patched image (from Downloads) to your pc
5)
PC side:-
1) Load any of the scatter files you have for the Nokia 1, the one from the stock rom is recommended
2) Load it in SP Flash tools
3) After that uncheck everything except the boot partition to be flashed
4) You will see a path of where the stock boot image is loaded from, if you click on it, a window will open asking you to select the boot image
5) select the patched boot image we copied to the pc earlier
and clock select
6) then click on the download button
Nokia 1 Side:-
1) Hold both volume up and volume down buttons together and connect it to your PC
PC side:-
1) It will begin flashing the boot image and will display a success message
Nokia 1 side:-
After it flashes successfully turn your device on and open magisk app, there it should say that magisk is installed
Credits to @GuyGotMadNameGame for the inspiration!

Reserved

Reserved!

Method mentioned in the OP worked 100% for me! Thanks for the amazing tip

I got hold of a discarded device and got it up running. Most of the above mentioned steps I could follow. Problem I have is that the download from the SP tool does not start. I think the exact steps for success must be slightliy different since somewhere else the method to bring the device into "download mode" is pressing volume-up and power simultaneously, not volume-up and volume-down.
What I did and what seems approximately the method for MTK devices is to power down the device and after pressing download in the SP tool to connect the device via USB. But it didn't start.
What could be wrong? Are there perhaps other prerequisites to fulfil, like unlocked bootloader? I was not yet able to achive that either.

linuxteddy said:
I got hold of a discarded device and got it up running. Most of the above mentioned steps I could follow. Problem I have is that the download from the SP tool does not start. I think the exact steps for success must be slightliy different since somewhere else the method to bring the device into "download mode" is pressing volume-up and power simultaneously, not volume-up and volume-down.
What I did and what seems approximately the method for MTK devices is to power down the device and after pressing download in the SP tool to connect the device via USB. But it didn't start.
What could be wrong? Are there perhaps other prerequisites to fulfil, like unlocked bootloader? I was not yet able to achive that either.
Click to expand...
Click to collapse
You need to have MTK USB drivers on your pc, and, I always held down volume up+down while device was fully off and then connected cable and it worked for me, not sure why it isn't working for your device

Hausemaster said:
You need to have MTK USB drivers on your pc, and, I always held down volume up+down while device was fully off and then connected cable and it worked for me, not sure why it isn't working for your device
Click to expand...
Click to collapse
Yeah, works better now. MTK drivers are included in Linux currently, but I needed to add my user to group dialout. Then the pressing of vol up and down worked.
I need to work out why the device told me at boot time that the verification failed (red state). I will try again, with option "keep forced encryption" off in Magisk.

linuxteddy said:
Yeah, works better now. MTK drivers are included in Linux currently, but I needed to add my user to group dialout. Then the pressing of vol up and down worked.
I need to work out why the device told me at boot time that the verification failed (red state). I will try again, with option "keep forced encryption" off in Magisk.
Click to expand...
Click to collapse
Hmm that shouldn't be happening, are you on latest firmware on your Nokia 1? As the boot.img from the link is for the latest Android 10 build

Hausemaster said:
Hmm that shouldn't be happening, are you on latest firmware on your Nokia 1? As the boot.img from the link is for the latest Android 10 build
Click to expand...
Click to collapse
Yes, the device is on the latest FW. Funny is, that after the failure I flashed the boot.img from the link, and the device boots again. That's prove, that the boot.img fits as well as the flashing procedure is working. The only culprit possible seems to be Magisk patching the boot.img.
What about the instructions given here: https://forum.xda-developers.com/t/unlocking-rooting-nokia-1-stock-rom-guide.3832230/post-77399813 ? I tried to unlock the bootloader, and it went as far as the command "fastboot oem key <md5>". Is it possible that it tampered the system? I could not unlock since the option in the developer settings is greyed out.

linuxteddy said:
Yes, the device is on the latest FW. Funny is, that after the failure I flashed the boot.img from the link, and the device boots again. That's prove, that the boot.img fits as well as the flashing procedure is working. The only culprit possible seems to be Magisk patching the boot.img.
What about the instructions given here: https://forum.xda-developers.com/t/unlocking-rooting-nokia-1-stock-rom-guide.3832230/post-77399813 ? I tried to unlock the bootloader, and it went as far as the command "fastboot oem key <md5>". Is it possible that it tampered the system? I could not unlock since the option in the developer settings is greyed out.
Click to expand...
Click to collapse
Did you try using both magisk canary and stable, also don't use mtp to transfer boot images, it damages them sometimes, also, don't unlock bootloader it worked fine when I did it with a locked bootloader for me...

Hausemaster said:
Did you try using both magisk canary and stable, also don't use mtp to transfer boot images, it damages them sometimes, also, don't unlock bootloader it worked fine when I did it with a locked bootloader for me...
Click to expand...
Click to collapse
I will try to use both. But how disable mtp? Do I need to transfer by SD card or cloud, bluetooth even?

linuxteddy said:
I will try to use both. But how disable mtp? Do I need to transfer by SD card or cloud, bluetooth even?
Click to expand...
Click to collapse
Transfer by Sd card is the safest

Hausemaster said:
Transfer by Sd card is the safest
Click to expand...
Click to collapse
I decided to md5-check the boot.img (patched an unpatched), and it all matches between PC and device. Therefore, I tried the Magisk 24.2 version (from stable) instead of the 24.3 canary. And now: It works.
Thanx a lot!

linuxteddy said:
I decided to md5-check the boot.img (patched an unpatched), and it all matches between PC and device. Therefore, I tried the Magisk 24.2 version (from stable) instead of the 24.3 canary. And now: It works.
Thanx a lot!
Click to expand...
Click to collapse
No problem, hope you have fun!