Database Users

[HOW-TO] Install 2.1 + Fastboot + Recovery + Custom ROMs on GT540! (n00b friendly!)

A WARNING: IN THE EVENT OF A BRICKED DEVICE, I AM NOT RESPONSIBLE! YOU DO THIS AT YOUR OWN RISK. KDZ UPDATER WILL BRICK YOUR PHONE IF NOT USED PROPERLY. SO FOLLOW THESE INSTRUCTIONS CAREFULLY!!!
So, you want to install custom recovery and custom ROMs? Well, you're in the right place. Follow this guide to it's exact instructions, and you will be fine.
You will need:
A computer running Windows (Sorry Mac & Linux users!)
Your phones USB cable. (If you don't have one, you can see a list of them here on Amazon)
We will need a couple of downloads first, so download these files:
V20C Orange France Fastboot ROM (It doesn't matter that it's Orange France, we are replacing the software anyway, I recommend this one as it fixes some calling issues by flashing a new baseband (or Radio).
KDZ Updater
Also, make sure you have your drivers installed. If you don't, get the .zip from here and install all 3 .exe files that are in the zip.
Now to install the Fastboot ROM!
First of all, extract KDZ Updater to the desktop. Then run the msxml.msi file to install the MSXML Parser that is needed to run KDZ. A window should then pop up that looks like this:
{
"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"
}
^^Select install now.
But if this comes up:
It is already installed, and you can close the window.
Once that is sorted, open up KDZ_FW_UPD.exe (Windows Vista/7 users, make sure to right click and select RUN AS ADMINISTRATOR!)
Change the type of flash by selecting the 'Type' dropdown box and select 3GQCT (SUPER IMPORTANT!)
And make sure PhoneMode is set to DIAG.
Click the
icon and select the KDZ file you downloaded earlier.
Prepare the phone by enabling USB Debugging by going to Settings>Applications>Development>Enable USB Debugging, also go into Settings>SDCard & Phone Storage and make sure 'Mass storage only' is unticked. Then connect the phone to the computer via USB cable and let Windows install any drivers it needs.
Click 'Launch software update' and do not use your computer until the update is complete. The update will take roughly 10-20 mins to complete. Your phone should reboot automatically.
Installing recovery:
You have multiple choices to choose from.
ClockworkMod Recovery 2.5.1.8 (Recommended)
ClockworkMod Recovery 4.x (Recommended but you may run into incompatible .zip files, download the recovery_clockwork_x.x.x.x_swift.zip file)
Amon RA 2.2.1 (Recommended)
Amon RA 1.7.0.1 (Not recommended due to incompatibility with zip files and recovery backups. Also .zips must be signed)
Download the recovery image of your choice (I strongly recommend Clockwork 2.5.1.8)
Next put your phone in Fastboot mode by rebooting then holding Camera+Power, make sure USB Cable is plugged in. Also let Windows search Windows Update for drivers.
Download fastboot.exe from here: http://adf.ly/2M8Hi and extract it to the desktop. Also put the recovery image you downloaded onto the desktop too.
Be sure to have your fastboot drivers installed, if you use Vista/Windows 7 then the driver should be auto-downloaded from Windows Update, if you use XP or the drivers won't install from Windows Update, then look at this.
Open a command prompt and type the following:
Code:
cd Desktop
fastboot devices (if you see ? fastboot then your device is recognized)
fastboot flash recovery name_of_recovery.img
fastboot reboot
When fastboot says rebooting, hold down HOME and wait. You should see clockwork pop up. Recovery is now on your phone. You can delete the fastboot, kdz and recovery file from your pc because we won't be needing them again. Unless you need to use fastboot.exe again, but just download the fastboot.zip again if you need it) The other files, we don't need.
(NOTE: If your phone reboots with no boot logos (LG logo and animation), or when you flash recovery and it doesn't come up, follow the steps found here. Thanks to fishears for the post!)
Now, installing custom ROMs. Pick any ROM you'd like from the ROM Development section, if you can, get the recovery version, it is much easier to install. Determine if it is a recovery backup, or update.zip
Recovery backups usually contain some .img files and a nandroid.md5 file. The folder containing these files will need to go in the sdcard\clockworkmod\backup folder. Flash them by going to Backup/Restore>Restore>Then pick the backup folder.
Recovery update.zips contain three (or four) files/folders:
boot.img (file)
install-busybox.sh (file, only appears in SOME ROMs)
system (folder)
META-INF (folder)
DO NOT EXTRACT THESE, just put the .zip file on your sdcard, then go into recovery and go to install .zip from sdcard>choose .zip>pick the .zip you downloaded. (NOTE FOR SWIFTDROID: You MUST put the update-cm-xxxxx.zip file found in the SwiftDroid_x.x.x.x_Recovery.zip on your sdcard for it to install!!!)
If you need any help, PM me or reply to this thread.
Don't forget to say
if I helped!
Enjoy!
Want to go 'advanced'? Check out this guide resizing your partitions so you can have more app space!
(Also, if a mod could sticky this thread I would be very thankful. Cheers!)

great work man.. only regret you did not post this earlier for me,as i took about 2 days to flash my phone for first time.. lol
found that helped me using recovery.

scribbclubber said:
great work man.. only regret you did not post this earlier for me,as i took about 2 days to flash my phone for first time.. lol
found that helped me using recovery.
Click to expand...
Click to collapse
lol, I was going to post it for a while because most of it was a reply to another post, but only just got round to doing it and it only took about 1 hour to re-write, but hopefully it will save some time by not having to explain it again and again to first time flashers (when they appear lol) Also might do a boot logo and recovery repair one too so users can sort that out too as there isn't a clear guide with pics on XDA. Also, i'm going to contact Decad3nce and see if we can get this stuck.

effortless. said:
...
V20C Orange France Fastboot ROM (It doesn't matter that it's Orange France, we are replacing the software anyway, I recommend this one as it fixes some calling issues by flashing a new baseband (or Radio)....
Click to expand...
Click to collapse
I have a few theoretical questions about this. Firstly, what calling issues does this fix? My current configuration is based off a v20d Baltic fastboot kdz, and has no problems. What difference would it make if I were to flash this v20c Orange, and restored a backup of my current software, if any(difference)? Lastly, is there any way to chech what baseband/radio a kdz flashes, if possible, without flashing it? I would be glad if I learned something new today, thanks.

nutterbg said:
I have a few theoretical questions about this. Firstly, what calling issues does this fix? My current configuration is based off a v20d Baltic fastboot kdz, and has no problems. What difference would it make if I were to flash this v20c Orange, and restored a backup of my current software, if any(difference)? Lastly, is there any way to chech what baseband/radio a kdz flashes, if possible, without flashing it? I would be glad if I learned something new today, thanks.
Click to expand...
Click to collapse
It is meant to include a fix for calling while connected to 3G. Me and many other users encountered a problem where we could not recieve calls on 3G. I flashed this and my problem was gone. Also, i'm unsure how to check the baseband firmware, in 2.2 ROMs, this is visible, but I looked in the build.prop, and it was a set text (under ro.ril.baseband I think) but yes, you could flash this KDZ, restore backup and all would be well. But if you needed the modified partitions, just use the tutorial that is in my signature, then flash backup.

Good idea
effortless. said:
lol, I was going to post it for a while because most of it was a reply to another post, but only just got round to doing it and it only took about 1 hour to re-write, but hopefully it will save some time by not having to explain it again and again to first time flashers (when they appear lol) Also might do a boot logo and recovery repair one too so users can sort that out too as there isn't a clear guide with pics on XDA. Also, i'm going to contact Decad3nce and see if we can get this stuck.
Click to expand...
Click to collapse
yep well said, when they appear and post without using search bar...lol think that i've did it myself but i used to save improtant notes and like that no need to search again and again, the thread should be stuck for noobs..
the guides are already here but posted on different threads and not at start, so agree that pics alongside instruction is a good idea.

Do I need recovery_clockwork_4.0.1.4_swift, that is on Mur4ik's site, to install SwiftDroid_v2.0_RC4, or I can use recovery clockwork 2.5.1.8 that I already have on my phone?

EDIT:Nvm, fixed it.

Added info on making sure 'Mass storage only' is unchecked before using KDZ to solve some peoples issues with the phone not being detected.

Noob friendly? hardly.
THis has no information on rooting. does the phone need to be rooted? is this flash pre rooted? how to root?
Lack of information everywhere, sorry.

DamDSx said:
Noob friendly? hardly.
THis has no information on rooting. does the phone need to be rooted? is this flash pre rooted? how to root?
Lack of information everywhere, sorry.
Click to expand...
Click to collapse
Obviously if you needed to root then I would have included the steps. Also around 99% of custom ROMs are rooted anyway.

I have a rooted and already updated to 2.1.
Would this still work?

KenifJambo said:
I have a rooted and already updated to 2.1.
Would this still work?
Click to expand...
Click to collapse
Of course, you would have to do this anyway if you want to install custom ROMs

This should be added to mygt540.com
Sent from my GT540 RSpec using XDA App

Danzano said:
This should be added to mygt540.com
Sent from my GT540 RSpec using XDA App
Click to expand...
Click to collapse
It already has been lol

In 2.1, you can check baseband in hidden menu.
Sent from my GT540 using Tapatalk

Will this also work with the GO version of the GT540?
As my girlfriend have this i she want to run Cyanogenmod because the phone is terrible slowly.

Aktivehate said:
Will this also work with the GO version of the GT540?
As my girlfriend have this i she want to run Cyanogenmod because the phone is terrible slowly.
Click to expand...
Click to collapse
As far as I am aware, it works perfect, GO is just some branding from some providers.
^^ Could someone back me up on this,
Thanks

Well that's good to know, i had one with 1.6 but made some things go wrong with the drivers, and the usb settings in android, but know i have this guide so i am gone try it.
When I tried it i had some trouble with the kdz flasher, but i did'nt knew of the msxml stuff and it was with windows 7.

Could someone upload another fastboot rom,preferably a version v20a or v20b
Sent from my GT540 using XDA App

Read through noob guides but still having problems with the auto BL unlock

I've been thinking about it for a while but decided to give it a try today . The step that tells me to hold up I get but then how so I power down to activate fastboot ?
Sent from my Atrix-4G, stock 2.3.4 (rooted)

DopeHack said:
I've been thinking about it for a while but decided to give it a try today . The step that tells me to hold up I get but then how so I power down to activate fastboot ?
Sent from my Atrix-4G, stock 2.3.4 (rooted)
Click to expand...
Click to collapse
hold volume down button while booting up, then hold volume up after fastboot is selected to activate it.
after that, you use fastboot commands on your computer.

But I was using the automatic unlocker . I still need to put in commands myself?
Sent from my Atrix-4G, stock 2.3.4 (rooted)

DopeHack said:
But I was using the automatic unlocker . I still need to put in commands myself?
Sent from my Atrix-4G, stock 2.3.4 (rooted)
Click to expand...
Click to collapse
Did you ask in that thread?
Sent from my MB860 using xda premium

DopeHack said:
But I was using the automatic unlocker . I still need to put in commands myself?
Click to expand...
Click to collapse
I believe the automatic unlocker will pause and should give clear instructions ask you to do specific things that have to be done by a human (power down and reboot into certain mode, etc), you just need to follow these instructions. After that, you just hit enter to continue.
If you are unable to follow these instructions, probably it's too much for you...
To reboot into fastboot, for example: press the power button, to turn off the phone; then hold the volume down button, press the power button again, you'll see "Fastboot", then release volume down, press volume up, you enter the "fastboot" mode

Too much for me lol I know how to get to all the menus that its telling me to go to but nothing else happens. the guide said nothing about typing in anything which is why I choose it. Especially since the automatic root worked easy as pie ...
Sent from my Atrix-4G, stock 2.3.4 (rooted)

You want help, laugh when people who are trying to help say it might be too much for you, yet you provide us close to absolute no information.
What guide are you following? We might know, but it still is your job to provide a link.
What is the step you are stuck at?
Why, what isn't going according to plan? What do you see happening in your sceen / phone?
If you can't explain properly, provide some screenshots.
You say you can get to all the menus it tells you to, yet in the first step you can't seem to get into fastboot. Your speech is unclear and what you want is hard to understand.
My opinion is you aren't ready to unlock your bootloader. You know very little about your phone or how it works. That's the community's fault really, with all these automatic scripts, which are really nice if you know what you're doing, but end up promoting easy ignorance in people like you.
I just hope in a month or two you are not one of those writing "OMG, please, I arrempted to downgrade by SBF and know my phone won't boot, what gives???"
Read up on some information a learn how these things work. It is the best you can do. Owning an android device and modding it can be great fun, but it does require some effort on your part. If I were you, I would learn how to unlock my bootloader with pudding, just to understand what is actuallly going on.
Either that, or you can learn how to ask for help properly and politely. Your choice.
Also, wrong section, This is not Q&A.

My girlfriend was rushing me so I tried to type up something quick but I used this
http://forum.xda-developers.com/showthread.php?t=1182871
As you can see like I can see it does not say I need to type anything in the cmd (which I have seen in YouTube videos and isn't that hard) but thought hey automatic sounds good so I gave it a try I don't have any problems getting the phone to fast boot or rsd as I've used the stock recovery to clear cache in an attempt to fix something. The part I'm stuck at is step 6
You are right I don't know alot about android which is why I didn't start messing with my phone the day I got it but I've been all over this site (well the atrix at least) and YouTube.
I appreciate any help and sorry for the misplaced thread
Sent from my Atrix-4G, stock 2.3.4 (rooted)

DopeHack said:
My girlfriend was rushing me so I tried to type up something quick but I used this
http://forum.xda-developers.com/showthread.php?t=1182871
Click to expand...
Click to collapse
this one is better
http://forum.xda-developers.com/showthread.php?t=1302423
doesnt give you the soft brick i think

So, let's see if I got this, you are having trouble at the part it says it should restart? Or before that? After you choose the number and press enter, what happens?
This could be a driver problem... If windows is not recognizing a device, it's common... Which windows are you using? I used to have some problems on XP and vista...

Newbleeto said:
So, let's see if I got this, you are having trouble at the part it says it should restart? Or before that? After you choose the number and press enter, what happens?
This could be a driver problem... If windows is not recognizing a device, it's common... Which windows are you using? I used to have some problems on XP and vista...
Click to expand...
Click to collapse
Right where it says it should restart and go into fastboot nothing happens I could hold that power button all day. I knew vista would bring an issue into the mix cause it never made the sound for connecting the phone but the SD cards show up
Sent from my Atrix-4G, stock 2.3.4 (rooted)

sanriver12 said:
this one is better
http://forum.xda-developers.com/showthread.php?t=1302423
doesnt give you the soft brick i think
Click to expand...
Click to collapse
This is the one I read before thanks hopefully my girlfriend will disappear for a hour or two (she doesn't want me to ruin my phone) so I can work on it .
so with this one I can use fauxs 1.3 or 1.45Ghz kernal with cm7 I've been craving that ice cream sandwich ..
Sent from my Atrix-4G, stock 2.3.4 (rooted)

Computer is down for a while seems like it wasn't meant to be but Im still going to get it done
Sent from my Atrix-4G, stock 2.3.4 (rooted)

I actually had to use a Vista system to get this to work.
Now, when the instructions say it should "Restart", at that point, have you been in "Fastboot" yet? Have you been to the part where you have to enter your "Unique ID"?
This is important to know because throughout the bootloader-unlocking process the phone should be restarted a couple of times. It sounds like you have at least gotten through the part where it flashes "Pudding" but it sounds like you haven't done the "fastboot" part yet.
Are you referring to "Step 6" in the actual post or within the script? If the power button does not work then just pull the battery. As long as it is not in the process of doing something you should be fine.
I also want to point out that the program you are using only requires that you type in your Unique ID, everything else is automated, not to mention the file contains everything you need including adb, fastboot, RSDlite, Superuser, Pudding, and a working recovery so it makes it very easy for the end user to not have to find everything on their own. The script unlocks the bootloader, roots your phone, and flashes CWM recovery.
Either way, please provide more details if you are still having issues. Good luck.
DopeHack said:
Right where it says it should restart and go into fastboot nothing happens I could hold that power button all day. I knew vista would bring an issue into the mix cause it never made the sound for connecting the phone but the SD cards show up
Sent from my Atrix-4G, stock 2.3.4 (rooted)
Click to expand...
Click to collapse

live4nyy said:
I actually had to use a Vista system to get this to work.
Now, when the instructions say it should "Restart", at that point, have you been in "Fastboot" yet? Have you been to the part where you have to enter your "Unique ID"?
This is important to know because throughout the bootloader-unlocking process the phone should be restarted a couple of times. It sounds like you have at least gotten through the part where it flashes "Pudding" but it sounds like you haven't done the "fastboot" part yet.
Are you referring to "Step 6" in the actual post or within the script? If the power button does not work then just pull the battery. As long as it is not in the process of doing something you should be fine.
I also want to point out that the program you are using only requires that you type in your Unique ID, everything else is automated, not to mention the file contains everything you need including adb, fastboot, RSDlite, Superuser, Pudding, and a working recovery so it makes it very easy for the end user to not have to find everything on their own. The script unlocks the bootloader, roots your phone, and flashes CWM recovery.
Either way, please provide more details if you are still having issues. Good luck.
Click to expand...
Click to collapse
I wasn't blaming vista I was just saying cause I've had problem with that is in the past.
I've basically done nothing haven't flashed or wiped my phone yet I was basically stuck at or around the first step cause it first asks for RSD protocol and then it says restart phone but the power button has no effect why in that mode nd when I pull the battery to manually put it in fast boot nothing happens nd I get some kind of batch error when it trays to get my unique id...
But got the computer back today so I'm gonna work on it again
Thanx for help ... will update you guys when I can

sanriver12 said:
this one is better
http://forum.xda-developers.com/showthread.php?t=1302423
doesnt give you the soft brick i think
Click to expand...
Click to collapse
Actually, I followed the method you linked (old netbook running XP) and got a softbrick on the automatic reboot after flashing pudding. I was so busy watching RSD Lite do its thing that I didn't catch that my phone had actually rebooted; it selected fastboot mode on its own so I was able to issue the unlock command. It took.

"7.Plug your device into your computer. RSD Lite should recognize your device and say “Model: NS Flash Olympus” and “Connected…” The acronym 'NS' may be different for your device people!!"
its not doing this(i have rsdlite 4.5.5 because i cant find 5.5)
edit: got on to next problem

Thanks everyone
{
"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"
}
Sent from Atrix 4G running CM7 ICS Final @ 1.2Ghz

If cpu not recognizing ur device in fastboot try restarting ur cpu. If u updated drivers u have to restart the cpu before it will see ur device.
Sent from my MB860 using xda premium

[Q] SM-T530NU Android version 5.0.2

I had my Tab 4 rooted with CF auto root and was happy!.
Over about 3 months it seemed there were some performance issues so I used super su to un-root, and went for a factory re-set.
I tried to do a software update once back up and running but, got the pop-up telling me it couldn't up-date b/c of knox (actually said system has been altered etc..)
So,,,,,
I plugged into my samsung keys and to update and next thing I knew I had gone from KitKat 4.4.2 to Android 5.0.2.
This also changed my build number, to LRX22G.T530NUUEU1BOE5.
I WANT MY ROOT BACK, , , question is HOW?
None of the numbers aside from model number (SM-T530NU) match up with the CF auto-root now, as they did before.
I'd like to be rooted before heading back to Lagos Nigeria on Monday 6/22/2015,, but I don't want to brick this thing prior to leaving and end up tab-less.
ANYONE HAVE TIME TO HELP?:fingers-crossed:
[email protected]

rnerger said:
I had my Tab 4 rooted with CF auto root and was happy!.
Over about 3 months it seemed there were some performance issues so I used super su to un-root, and went for a factory re-set.
I tried to do a software update once back up and running but, got the pop-up telling me it couldn't up-date b/c of knox (actually said system has been altered etc..)
So,,,,,
I plugged into my samsung keys and to update and next thing I knew I had gone from KitKat 4.4.2 to Android 5.0.2.
This also changed my build number, to LRX22G.T530NUUEU1BOE5.
I WANT MY ROOT BACK, , , question is HOW?
None of the numbers aside from model number (SM-T530NU) match up with the CF auto-root now, as they did before.
I'd like to be rooted before heading back to Lagos Nigeria on Monday 6/22/2015,, but I don't want to brick this thing prior to leaving and end up tab-less.
ANYONE HAVE TIME TO HELP?:fingers-crossed:
[email protected]
Click to expand...
Click to collapse
It's really easy to root 5.0.2 (I have the exact same model). What you need to do is flash TWRP through Odin and immediately boot into recovery and install superSU. Actually I think the download link is broken on that thread, so here is a working link. Download the tar file to your PC, and download the zip file from here and save to your tablet. I'll write more detailed instructions in a minute
---------- Post added at 11:09 AM ---------- Previous post was at 11:05 AM ----------
OK so once you have the files where they need to be, power off your tablet and boot it into download mode. Run Odin on your PC. Make sure to disable the auto-reboot option in Odin, this is crucial. Flash the recovery tar file with the AP button. Now when the flashing is done, your tablet will not automatically reboot (good), but just sit there, the only way to tell it's done is when Odin says it's done (Pass or Reset). Power off the tablet manually, then immediately boot into recovery (home, power, vol+). Install that superSU zip file. Boot system normally, run the superSU app and follow the prompts. Congrats, you're rooted on lollipop.

Sry to ask but, could you??? do a step by step?? for the worried
Or point me to the location of where something along a step by step is posted already. I'm not bad on computers but android I'm still a serious noob.

How to root a 10.1 Tab 4 also links for 8.0, 7.0
This should work provided you use the correct recovery for your model
Preparation: Read everything and make sure you understand. I attached Odin v3.09, v3.10.6, v3.10.7 and 3.11.1. Odin 3.11.1 is recommended. Download the one you want and extract the zip to PC desktop. Also on the tablet enable usb debugging and mock locations in developer settings. Make sure you have the proper USB drivers for your PC. A quick note on file names: development code names for the Tab 4 series are as follows: matisse = 10.1, millet = 8.0, degas = 7.0
Download the twrp-3.0.0.9_matisse_20160314-0843.tar file (this is a twrp recovery that works for wifi, 3g, and lte 10.1 models) and save to PC. Download the superSU zip file and save to tablet storage. Obviously save the files somewhere easy to remember, and easy to navigate to.
Power off tablet. Boot into download mode (hold vol-, home, and power all at once in that order), then hit vol+ to continue
Run Odin. Connect tablet via USB. Hit AP button in Odin, select the TWRP tar file
Disable the "Auto-Reboot" and "Re-Partition" options in Odin, this is critical to success
Flash (click start). When it's done, the progress bar will be full and Odin should say something like "RESET!"
Hold the power button to power down the tablet. Then immediately hold vol+, home, and power (all at once, in that order) to boot into recovery. THIS MUST BE DONE BEFORE REBOOTING NORMALLY!
Install the SuperSU zip file that is saved to your tablet (tap the install option in TWRP, navigate to the zip file).
Reboot system (normal reboot). When android is booted, run the superSU app and follow the prompts; i.e. update the binary if it asks you to, choose normal install, be patient while it installs (takes a while) and reboot if it tells you to
Accompanying screenshots:
Step 3:
{
"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"
}
Step 4:
Step 5:
Step 7:
Tab 4 8.0 TWRP: Tab 4 8.0 unified TWRP (remember millet = 8.0; matisse = 10.1)
Tab 4 7.0 TWRP: SM-T230/NU/T231 (credit to sub77), SM-T230NT (Philz), SM-T235/Y (credit to CTXz), SM-T237P use Philz
Credit of course goes to sub77 for the 10.1, 8.0, and 7.0 TWRP builds, CTXz for TWRP for degaslte moonbutt74 for Philz CWM, and to chainfire for all things superSU. I'm just trying to help and/or point people in the right direction

USB and Remote installation
Prior to getting started should USB debugging be enabled? As well as Allow mock installations??

rnerger said:
Prior to getting started should USB debugging be enabled? As well as Allow mock installations??
Click to expand...
Click to collapse
Yes

Double-checking
Hi and thanks for this info! This is my first post here.
I am seeking to root my SM-T530NU so that I can [attempt to] remote control the device using AirDroid for my business. Currently, I am stuck with TeamViewer which works reasonably well enough but comes with a *very* pricey license north of $60 a month which I am having a hard time stomaching. However- I need to have full mirror over the web, so I am stuck with TV unless I can find another option. (Open to suggestions here.)
Anyhow- I want to try and root the device, however I have never rooted before and am somewhat confused by the info I am finding. Your post here just says I need to match the model number, while others I have come across claim that I need to match the build number as well. In my case, the build number is: LRX22G.T530NUUEU1BOE5.
Please clarify on whether or not the method you posted above should work on this build. If you could also direct me to a good resource for what I need to do to back up my device in case root attempt bricks it, that would be much appreciated as well!

mcmarturano said:
Anyhow- I want to try and root the device, however I have never rooted before and am somewhat confused by the info I am finding. Your post here just says I need to match the model number, while others I have come across claim that I need to match the build number as well. In my case, the build number is: LRX22G.T530NUUEU1BOE5.
Please clarify on whether or not the method you posted above should work on this build. If you could also direct me to a good resource for what I need to do to back up my device in case root attempt bricks it, that would be much appreciated as well!
Click to expand...
Click to collapse
This method will root your device, it's intended for all 10.1 models, but I have the exact same model and firmware as you and this is how I rooted. Flash this file through Odin in case you somehow brick, but if you follow the directions you'll be fine and won't need it
Back up any files, media, etc you have stored on internal storage, but again, you shouldn't need this, it's just to be safe

Thanks for the link to the file! I've been trying to use Odin and so far... no go. I disabled Windows Defender, switched to a shorter stock USB cord from Samsung. When I hit "Start" it initiates, then just gets stuck on recovery.img and nothing happens.
I've also tried Heimdall and can't seem to get that to work either. When I go to save the PIT, it fails. I was also reading a recent thread on github about an issue with newer bootloaders,, so maybe that is the problem with Heimdall.
One thing that might be a problem..? I have an Asus Transformer and am using the USB port on the keyboard because I don't have a micro-to-micro cord. Could that be it?
I wish that Odin would just work... any thoughts on what else to try?

mcmarturano said:
One thing that might be a problem..? I have an Asus Transformer and am using the USB port on the keyboard because I don't have a micro-to-micro cord. Could that be it?
Click to expand...
Click to collapse
I don't know exactly what your setup here is but it sounds like you're doing something wrong. It should be tablet > USB cable > USB port on either laptop or PC:
Also Odin has been known to be finicky it's best to use the USB cable that came in the box with the tablet. That said, any usb to micro usb cable capable of transferring files to/from the tablet in normal android should theoretically be able to work with Odin, I've rarely had issues using different cables.
I've never needed to use Heimdall so unfortunately I can't help you there, although I can say it should not be needed for this task.

mcmarturano said:
Thanks for the link to the file! I've been trying to use Odin and so far... no go. I disabled Windows Defender, switched to a shorter stock USB cord from Samsung. When I hit "Start" it initiates, then just gets stuck on recovery.img and nothing happens.
I've also tried Heimdall and can't seem to get that to work either. When I go to save the PIT, it fails. I was also reading a recent thread on github about an issue with newer bootloaders,, so maybe that is the problem with Heimdall.
One thing that might be a problem..? I have an Asus Transformer and am using the USB port on the keyboard because I don't have a micro-to-micro cord. Could that be it?
I wish that Odin would just work... any thoughts on what else to try?
Click to expand...
Click to collapse
Hi . You must run guide from here http://androidxda.com/flash-samsung-stock-rom-using-odin Only instead stock rom you must to use this recovery http://android.comtek-wiebe.de/OpenRecovery/openrecovery-twrp-2.8.6.0-matisse_wifi_3g_lte.tar .
Download to device to external sdcard this file http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133 .
Go to recovery and install tis zip from external sdcard .
Reboot .
Now you have root .

Meh nevermind
---------- Post added at 10:52 AM ---------- Previous post was at 10:38 AM ----------
mcmarturano said:
I wish that Odin would just work... any thoughts on what else to try?
Click to expand...
Click to collapse
It appears the tar file for version 2.8.7.0 is malfunctioning, did you try the 2.8.6.0 tar file?
I just flashed the 2.8.6.0 tar file through Odin successfully, I guess there just must be some problem with the 2.8.7.0 file unfortunately

TWRP 2870 fixed

Yes- That is my basic setup. I have the micro-USB port on the tablet connected to a regular USB port on the computer using the cord that came from Samsung. At first I tried another cord I had that was longer, then learned the length/quality of the cord could cause FAIL, so then I tried the stock cord. Unfortunately, that did not work either.
I was just wondering if the problem might be the USB port. First off, I had trouble at first getting the tablet to connect properly.... it kept connecting/disconnecting. What I tried to remedy this issue was to remove the port driver from Device Manager and reboot the computer to re-install it. After that, the tablet stayed connected... but still FAIL on flashing the recovery image.
The device I'm trying to flash from is a Asus Transformer Book... it has two USB ports- a regular 3.0 port connecting through the keyboard and a mini port on the screen/motherboard component. Since these two components can detach from one another, I'm just wondering if maybe the connection isn't good enough for Odin.
I have another laptop I can try to flash from, so I guess I will try that next. Unless you have any other thoughts/suggestions?
Thanks again for your help!

mcmarturano said:
Yes- That is my basic setup. I have the micro-USB port on the tablet connected to a regular USB port on the computer using the cord that came from Samsung. At first I tried another cord I had that was longer, then learned the length/quality of the cord could cause FAIL, so then I tried the stock cord. Unfortunately, that did not work either.
I was just wondering if the problem might be the USB port. First off, I had trouble at first getting the tablet to connect properly.... it kept connecting/disconnecting. What I tried to remedy this issue was to remove the port driver from Device Manager and reboot the computer to re-install it. After that, the tablet stayed connected... but still FAIL on flashing the recovery image.
The device I'm trying to flash from is a Asus Transformer Book... it has two USB ports- a regular 3.0 port connecting through the keyboard and a mini port on the screen/motherboard component. Since these two components can detach from one another, I'm just wondering if maybe the connection isn't good enough for Odin.
I have another laptop I can try to flash from, so I guess I will try that next. Unless you have any other thoughts/suggestions?
Thanks again for your help!
Click to expand...
Click to collapse
Setup is OK, were you using 2.8.7.0 or 2.8.6.0? Try 2.8.6.0 if you haven't already

repey6 said:
TWRP 2870 fixed
Click to expand...
Click to collapse
OK I will try that too. Thanks!

thisisapoorusernamechoice said:
Setup is OK, were you using 2.8.7.0 or 2.8.6.0? Try 2.8.6.0 if you haven't already
Click to expand...
Click to collapse
SUCCESS! 2.8.6.0 worked like a charm. Thanks a million!

Still have not done this but intend to soon. What about UN-root??
Is there a special way that I will have to go about UN-rooting ???

I just got the SM-T537A variant for my wife, will this procedure work for that model as well?

PDADoc said:
I just got the SM-T537A variant for my wife, will this procedure work for that model as well?
Click to expand...
Click to collapse
No, sorry, you can't have a custom recovery or custom kernel on that model because of the locked bootloader. I think people have been routing that model with towelroot or kingroot

TWRP only

HELP please!
My Jiayu S3 (2gb) got some malware and I tried a factory reset without any change.
Next I was prompted to upgrade so I downloaded the new version and clicked on install. That took me to the TWRP screen and that's where I'm stuck! I can move around on that screen but I can't get back to the system. Whenever I reboot, it takes me back to that screen.
Thus, I can't connect the phone to my computer to install a new rom. Is it possible to do so from TWRP? or do I have a brick?
Any help will be greatly appreciated, thanks

masterpointer said:
HELP please!
My Jiayu S3 (2gb) got some malware and I tried a factory reset without any change.
Next I was prompted to upgrade so I downloaded the new version and clicked on install. That took me to the TWRP screen and that's where I'm stuck! I can move around on that screen but I can't get back to the system. Whenever I reboot, it takes me back to that screen.
Thus, I can't connect the phone to my computer to install a new rom. Is it possible to do so from TWRP? or do I have a brick?
Any help will be greatly appreciated, thanks
Click to expand...
Click to collapse
Hi masterpointer,
You can almost always un-brick S3 with MTK SP Flash tool, but then, you need a firmware (with scatter file) to flash, and, you need to decide to flash KK or LP. If previously you ran KK and go LP (or, for some reason, other way around), you must use "upgrade firmware" instead of just "download" in tool. That's because KK and LP partition layout differ. You can find S3 firmwares and MTK SP Flash tool instructions in various places. Personally, I would perhaps recommend RC5 jiayu.de until a much anticipated MM upgrade arrives.
Just curious: what firmware did you run that would allow/suggest to upgrade/install resulting in getting stuck? Of course, some upgrade/install procedures may expect stock, not custom, recovery.
TWRP should give you adb, and you can always restore stock recovery put on SD card from there with 'dd'.

Dior DNA said:
Hi masterpointer,
You can almost always un-brick S3 with MTK SP Flash tool, but then, you need a firmware (with scatter file) to flash, and, you need to decide to flash KK or LP. If previously you ran KK and go LP (or, for some reason, other way around), you must use "upgrade firmware" instead of just "download" in tool. That's because KK and LP partition layout differ. You can find S3 firmwares and MTK SP Flash tool instructions in various places. Personally, I would perhaps recommend RC5 jiayu.de until a much anticipated MM upgrade arrives.
Just curious: what firmware did you run that would allow/suggest to upgrade/install resulting in getting stuck? Of course, some upgrade/install procedures may expect stock, not custom, recovery.
TWRP should give you adb, and you can always restore stock recovery put on SD card from there with 'dd'.
Click to expand...
Click to collapse
Thanks for trying to help.
However, I'm no expert so, for a start, I don't know what "KK" and "LP" refer to.
I do have a firmware (20150205-141543 (unzipped)) complete with a scatter file and I also have the MTK SP Flash Tool. I can copy the firmware to the external SD card (unzipped or zipped?) but how do I proceed from there? Please

masterpointer said:
Thanks for trying to help.
However, I'm no expert so, for a start, I don't know what "KK" and "LP" refer to.
I do have a firmware (20150205-141543 (unzipped)) complete with a scatter file and I also have the MTK SP Flash Tool. I can copy the firmware to the external SD card (unzipped or zipped?) but how do I proceed from there? Please
Click to expand...
Click to collapse
KK=KitKat aka Android 4.4.4
LP=Lollipop aka Android 5.1.1
20150205-141543 for sure will be KitKat.
Where did you get firmware?, it seems very old, older than anything I can find on needrom.
Are you sure you do not want to flash something newer? I suggest Lollipop RC5 from Jiayu.DE (to be found there).
You need to have unpacked files on PC for MTK SP Flash Tool to load the scatter file.
If you upgrade KK->LP then use "upgrade firmware" instead of "download".
Good luck!

I managed to flash my S3 Plus using Flash Tools in order to replace the useless rom published on Feb this year.
Having downloaded TWRP 3.0.0.0 on my pc I'm trying to install it on my phone using Flash Tools but I don't know how to open the .img file.
Can anyone help me please?

I tried many times following the process for TWRP but I got the answer
FAILED (remote: download the partition "recovery" is not allowed)
What is wrong?
Please HELP ...

masterpointer said:
HELP please!
My Jiayu S3 (2gb) got some malware and I tried a factory reset without any change.
Next I was prompted to upgrade so I downloaded the new version and clicked on install. That took me to the TWRP screen and that's where I'm stuck! I can move around on that screen but I can't get back to the system. Whenever I reboot, it takes me back to that screen.
Thus, I can't connect the phone to my computer to install a new rom. Is it possible to do so from TWRP? or do I have a brick?
Any help will be greatly appreciated, thanks
Click to expand...
Click to collapse
Apparently you tried to perform an OTA update (over the air). Unfortunately, this will only work with Stock revovery. So - flash the original recovery.img with Sp flash Tool. Power on the phone again. Perform the OTA again.
Gesendet von meinem Telekom Puls mit Tapatalk

Blackcrown said:
Apparently you tried to perform an OTA update (over the air). Unfortunately, this will only work with Stock revovery. So - flash the original recovery.img with Sp flash Tool. Power on the phone again. Perform the OTA again.
Gesendet von meinem Telekom Puls mit Tapatalk
Click to expand...
Click to collapse
Sorry for the delay with my response. I have been away the last 2 or 3 weeks.
I'm afraid no luck.
I copied the raw zip files (JY-S3-2 and JiayuS2-5.1_20160121-212346_PC)) both from NeedRom. In TWRP I click on Install, select ext. card and click on one of the zip files and then when I swipe to "flash the screen" it starts processing, then shows some error messages and finally a red "Failed" message appears. The same thing happens when I click on other rom.
I have also tried to copy all the unzipped files from an old rom i had (20150205-141543) to the external card, but that doesn't seem to do anything.
I'm obviously doing something wrong. Is it possible to get a step-by-step instructions of how to flash a rom via TWRP? I'm fairly certain that the phone is ok if I can only get the system reinstalled.
Hoping you can help

@masterpointer: Ok, so I got it wrong. You don't try OTA but want to flash a zip from recovery. The steps you've taken seem fine to me, except: do not unzip the files because TWRP will take care of that.
I suspect that you use the wrong version of TWRP recovery. I will get back to you later in the evening (Central European time), when I can access my home PC, and tell you the name of the TWRP recovery file I used.

Blackcrown said:
@masterpointer: Ok, so I got it wrong. You don't try OTA but want to flash a zip from recovery. The steps you've taken seem fine to me, except: do not unzip the files because TWRP will take care of that.
I suspect that you use the wrong version of TWRP recovery. I will get back to you later in the evening (Central European time), when I can access my home PC, and tell you the name of the TWRP recovery file I used.
Click to expand...
Click to collapse
Thanks, looking forward to hearing from you. I really would like to fix it. I loved that phone...!

Well, I see a bit clearer now. Looking closer at the ROMs that you mentioned:
masterpointer said:
I copied the raw zip files (JY-S3-2 and JiayuS2-5.1_20160121-212346_PC)) both from NeedRom. In TWRP I click on Install, select ext. card and click on one of the zip files and then when I swipe to "flash the screen" it starts processing, then shows some error messages and finally a red "Failed" message appears. The same thing happens when I click on other rom.
Click to expand...
Click to collapse
These ROMs (at least the second one, the first one I don't know) cannot be flashed with TWRP at all; they are meant to be flashed with SP Flash Tool. It's not TWRP's fault.
To flash with TWRP is easier, but you have to find a zip that is meant to be flashed from recovery. Usually these zips are provided as updates to an existing ROM. However, an update is not a full install, and since I don't know the last working configuration of your phone I recommend a clean install of a full ROM by the means of this ugly, but effective Flash Tool.
Don't use the ROM mentioned above; go for the "S3 RC5", date 04/21/2016, on Needrom. It's from the folks of jiayu.de and from there you can move on later to flash one of the shiny new Android 6 ROMs.
If you never flashed with SP Flash Tool - there's this tuturial How to flash a rom on jiayu s3 on XDA. Unfortunately, before you start flashing, you have to install the preloader driver, which is a bit of a hassle, if you use Windows 8 or 10. I found another tutorial Windows 10 MTK VCOM USB Drivers for 32 & 64 bit + Driver install tutorial which looks newbie friendly.

Many thanks for the explicit explanation. That should keep me busy for a while! I'll have a go and let you know how I fare...
Once again, thank you!
Blackcrown said:
Well, I see a bit clearer now. Looking closer at the ROMs that you mentioned:
These ROMs (at least the second one, the first one I don't know) cannot be flashed with TWRP at all; they are meant to be flashed with SP Flash Tool. It's not TWRP's fault.
To flash with TWRP is easier, but you have to find a zip that is meant to be flashed from recovery. Usually these zips are provided as updates to an existing ROM. However, an update is not a full install, and since I don't know the last working configuration of your phone I recommend a clean install of a full ROM by the means of this ugly, but effective Flash Tool.
Don't use the ROM mentioned above; go for the "S3 RC5", date 04/21/2016, on Needrom. It's from the folks of jiayu.de and from there you can move on later to flash one of the shiny new Android 6 ROMs.
If you never flashed with SP Flash Tool - there's this tuturial How to flash a rom on jiayu s3 on XDA. Unfortunately, before you start flashing, you have to install the preloader driver, which is a bit of a hassle, if you use Windows 8 or 10. I found another tutorial Windows 10 MTK VCOM USB Drivers for 32 & 64 bit + Driver install tutorial which looks newbie friendly.
Click to expand...
Click to collapse

Ok, here's what I've done:
1. downloaded and installed the drivers (as per the Windows site) and the Rom you recommended (Jiayu_S3_5.1.1_rc5_flashtool.rar. Please note the ".RAR" extension!!! - No problems
2. I also downloaded the latest flashtools file. However, that needed a password (which was shown) to unzip it, but the shown password does not work! However, I have Flashtools_v5.1452.00 already installed so I used that.
3. opened flash-tool.exe, clicked on Scatter-loading and then on the MTK6752_Android_scatter.txt
4. opened the Download only box and selected "Firmware upgrade"
5. clicked on Options/Download and ticked "DA and DL with checksum.
6. clicked on Download...
...and this is where the story ends! The screen simply greys out and stays like that until I click on Stop. No yellow progress line appears. Nothing happens.
Am I doing something wrong?
masterpointer said:
Many thanks for the explicit explanation. That should keep me busy for a while! I'll have a go and let you know how I fare...
Once again, thank you!
Click to expand...
Click to collapse

Blackcrown said:
Well, I see a bit clearer now. Looking closer at the ROMs that you mentioned:
These ROMs (at least the second one, the first one I don't know) cannot be flashed with TWRP at all; they are meant to be flashed with SP Flash Tool. It's not TWRP's fault.
To flash with TWRP is easier, but you have to find a zip that is meant to be flashed from recovery. Usually these zips are provided as updates to an existing ROM. However, an update is not a full install, and since I don't know the last working configuration of your phone I recommend a clean install of a full ROM by the means of this ugly, but effective Flash Tool.
Don't use the ROM mentioned above; go for the "S3 RC5", date 04/21/2016, on Needrom. It's from the folks of jiayu.de and from there you can move on later to flash one of the shiny new Android 6 ROMs.
If you never flashed with SP Flash Tool - there's this tuturial How to flash a rom on jiayu s3 on XDA. Unfortunately, before you start flashing, you have to install the preloader driver, which is a bit of a hassle, if you use Windows 8 or 10. I found another tutorial Windows 10 MTK VCOM USB Drivers for 32 & 64 bit + Driver install tutorial which looks newbie friendly.
Click to expand...
Click to collapse
Hi again.
Just realised that the following screen appears in the tutorial (after the "Options/Download/check DA and DL"). The items on my screen stay the same
Preloader
MBR
EBR1
UBOOT
Those items (apart from the "Preloader") do not appear on my screen at any stage. I assume that has got something to do with the lack of further progress?

masterpointer said:
6. clicked on Download...
...and this is where the story ends!
Click to expand...
Click to collapse
This is, where the flashing begins! AFTER clicking download, connect the phone to your computer. Phone must be switched OFF. As soon as you connect it, Windows will recognize the switched-off phone (provided that you successfully installed the preloader VCOM driver) and start the flashing indicated by the yellow bar. If the phone is not recognized, start Windows again, then use another USB port and/or try another USB cable.
masterpointer said:
Hi again.
Just realised that the following screen appears in the tutorial (after the "Options/Download/check DA and DL"). The items on my screen stay the same
Preloader
MBR
EBR1
UBOOT
Those items (apart from the "Preloader") do not appear on my screen at any stage. I assume that has got something to do with the lack of further progress?
Click to expand...
Click to collapse
No. The person who made the tutorial used some screenshots from another phone. That's all. However, you should untick the "Preloader" image in SP Flashtool before hitting Download. The preloader is working (that's why you can connect to the phone) and should not be flashed again for safety reasons.

Blackcrown said:
This is, where the flashing begins! AFTER clicking download, connect the phone to your computer. Phone must be switched OFF. As soon as you connect it, Windows will recognize the switched-off phone (provided that you successfully installed the preloader VCOM driver) and start the flashing indicated by the yellow bar. If the phone is not recognized, start Windows again, then use another USB port and/or try another USB cable.
No. The person who made the tutorial used some screenshots from another phone. That's all. However, you should untick the "Preloader" image in SP Flashtool before hitting Download. The preloader is working (that's why you can connect to the phone) and should not be flashed again for safety reasons.
Click to expand...
Click to collapse
No luck, I un-ticked the preloader but as soon as I hit the download button, everything simply greys out. I have attached a screenshot for your perusal. I'm stuck!
{
"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"
}

masterpointer said:
No luck, I un-ticked the preloader but as soon as I hit the download button, everything simply greys out. I have attached a screenshot for your perusal. I'm stuck!
Click to expand...
Click to collapse
more info: Initially I had set the "download only" box to "firmware upgrade", but when I unticked the "preloader" as you suggested, the "firmware upgrade" automatically reverted to "download only" (I hadn't noticed). Same end result, though.

masterpointer said:
more info: Initially I had set the "download only" box to "firmware upgrade", but when I unticked the "preloader" as you suggested, the "firmware upgrade" automatically reverted to "download only" (I hadn't noticed). Same end result, though.
Click to expand...
Click to collapse
After SPFlashtools now is working, there are 3 possible things wrong. The bad luck is, that none of this gives a feedback, so you can only mess around.
- Most possible is, that the VCOM driver for your windows isn´t installed correctly. Take care, each windows versions needs a different driver! Reinstall it.
- As Blackcrown already said, try all USB ports with all available cable.
- Some of the S3 needs, that you press volume button after connecting the switched off phone.
Good luck.

1testi said:
After SPFlashtools now is working, there are 3 possible things wrong. The bad luck is, that none of this gives a feedback, so you can only mess around.
- Most possible is, that the VCOM driver for your windows isn´t installed correctly. Take care, each windows versions needs a different driver! Reinstall it.
- As Blackcrown already said, try all USB ports with all available cable.
- Some of the S3 needs, that you press volume button after connecting the switched off phone.
Good luck.
Click to expand...
Click to collapse
It works!!!!!!!
I thought I had to wait until being told by SP-FT to connect the phone. You last message made me think that maybe it should be connected BEFORE hitting the download button. So I did that and...Bob's-your-uncle.
I can't thank you enough for all your help. Wish I would get the opportunity to reciprocate. Many, many thanks.

1testi said:
After SPFlashtools now is working, there are 3 possible things wrong. The bad luck is, that none of this gives a feedback, so you can only mess around.
- Most possible is, that the VCOM driver for your windows isn´t installed correctly. Take care, each windows versions needs a different driver! Reinstall it.
- As Blackcrown already said, try all USB ports with all available cable.
- Some of the S3 needs, that you press volume button after connecting the switched off phone.
Good luck.
Click to expand...
Click to collapse
It works!!!!!!!
I thought I had to wait until being told by SP-FT to connect the phone. You last message made me think that maybe it should be connected BEFORE hitting the download button. So I did that and...Bob's-your-uncle.
I can't thank you enough for all your help. Wish I would get the opportunity to reciprocate. Many, many thanks.

[Flashtool] How to flash the Sony Xperia Z5 Compact with stock ROM [Flashtool]

Over the past couple of days, I have been experiencing various issues with flashtool. Using the internets help and many hours of my time I managed to fix most of these problems that occurred for me. Although there are hundreds of Flashtool step by step instructions, I thought it would be best for an updated and more in depth on what you should be aware of first before clicking "Flash".
Firstly, I do not take responsibility for any device broken or damaged since there is ALWAYS a minute chance of your device bricking.
Lets start, shall we?
Things Needed
Z5 Compact
Original Cable (or any cable actually that is working and can transfer files)
Flashtool 0.9.22.3
Sony Xperia Z5 Compact Stock Rom
Okay to start off.. Yes, this should work with other phones however I am not providing the stock roms for those, it takes a simple google search to find them ie. "Sony Xperia Z5 Stock Rom ftf"
You don't need the latest stock rom either since you can update once the phone is setup depending on if you have access to OTA updates (Over the Air).
Step 1.
Download flashtool if you haven't already. If you have an older version of flashtool, uninstall it and make sure all old files are gone for good and also be sure the new one is fully installed. I prefer to use the magnet link on the website (for torrents) since using uploaded.net takes forever.
Step 2a.
If you're on Windows 8/8.1/10 then please take note to this specific paragraph, any other OS skip to 2b Windows 8/8.1 like to have its security tight, so they block you from installing drivers with unsigned certificates to "keep your computer from harm" but just go ahead and follow the instructions to allow your computer install these drivers. If the drivers aren't installed correctly, then you won't be flashing anything today Okay, go to Settings>General and then click on 'Restart Now' under 'Advanced Startup'.
{
"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"
}
This will restart your PC. It will then take you to a screen that gives you various options. On Windows 8 you will see 'Troubleshoot' and on Windows 8.1 you will see 'Start-up Settings'. Select either that appears. This will take you to another page that will ask to restart windows in order to use some advanced startup features, just click 'Restart'. If it already takes you to the page without restart, or if your computer just restarted and you're getting the options of what to select, make sure you select 'Disable driver signature enforcement'.
Your computer should now restart with driver signature enforcement disabled. Now, go ahead and carry on with the instructions in 2b!
Step 2b.
Navigate to the 'drivers' folder where you installed Flashtool. If you cant remember where you installed it, the default directory should be in "C:\Flashtool". Open 'Flashtool-drivers.exe' and install:
Flashmode Drivers
Fastboot Drivers
Z5 Compact Device Driver (Or whatever your device is)
Now we have successfully installed the drivers for flashtool and our device!
Step 3.
Find the stock rom you downloaded, copy and paste it into your firmwares folder in flashtool. For me, this is in "C:\Users\Matty\.flashTool\firmwares". People have been saying to delete the folders inside the firmwares folder, do not do this as the flash might not work.
Step 4.
Note
If you're running 64bit, I recommend you to not use Flashtool64.exe at first, just use the standard 'Flashtool.exe'. If you dont get an icon on your desktop from the setup, just navigate to the folder in the directory you installed it in, then right click and click send to desktop so you can access it easy
Step 5.
Open Flashtool from your newly created shortcut on your desktop. Click the Flash icon, then click Flashmode, then hit Ok. Click your Firmware on the left to start off with. You might have to hit the firmware dropdown until it gets to the actual firmware like so:
If you want to remove all your data, where it says Wipe, hit all the boxes. (APPS_LOG, DIAG, SSD, USERDATA). Then click Flash. You will now see "Preparing files for flashing" on your screen. Be very patient, and in the meantime, turn your phone off ready to enter Flashmode. Make sure your phone is switched off and NOT plugged.
When you see this box come up on your computer, It's probably time to connect the USB to your computer, and enter flashmode on your phone.
Plug the USB into your computer
(TRY USB 2.0 FIRST, SOME REASON NO USB 3.0 PORT WORKED FOR ME+MANY OTHER PEOPLE HAD PROBLEMS WITH USB 3.0 I.E loader.sin errors)
Entering Flash Mode
Hold the Volume Down button and plug the USB cable from your computer into your phone. You should hear the Windows noise it makes to say the device is connected to the PC. If any extra drivers are needed to complete the flash it could take longer for the flash to start. You should then see a constant green light in the top right of your device, gently put it somewhere without unplugging the charger and let Flashtool do the hard work
Step 6.
Leave the device for no longer than 30 minutes. However, if you're unsure be safe and leave it for a full hour, go out have a nice brew, do a tap and dance and come back and it should be done. The only reason it would get stuck is because you unplugged the phone during the Flash, or if the cable somewhat died throughout the operation. If so, repeat the instructions in hope your device will be as good as new
Flashtool will now let you know when it is done. It will say "Flashing finished, please uplug and start your phone."
If it says that, hooray! You have successfully flashed your phone with stock rom!
If not and you get an error before it even wants to flash, or throughout the process you get an error, post it below and I'll take a look. I'm not very good but I know quite a few errors.
END OF TUTORIAL
I just thought I'd help the community out in a way that I can, since I'm bad at like everything else lol.
Peace folks :highfive: :cyclops:

Great write-up! I know it probably would have helped me months ago for something like this to exist. For anyone coming here for info, it also took me three PC's before I found one that played well with flash tool. Also if you ever get a failure, reboot PC, phone, and try again. Persistence pays off.

civicsr2cool said:
Great write-up! I know it probably would have helped me months ago for something like this to exist. For anyone coming here for info, it also took me three PC's before I found one that played well with flash tool. Also if you ever get a failure, reboot PC, phone, and try again. Persistence pays off.
Click to expand...
Click to collapse
Thanks buddy! I suppose the old saying does work.
"Have you tried turning it off and on again?" Works mostly for me lol

If you're on Windows 8/8.1
Click to expand...
Click to collapse
on Windows 10 to
Good work

ciopik said:
on Windows 10 to
Good work
Click to expand...
Click to collapse
I'll add that now, thanks man

The firmware folder is not detected by Flashtool although I have put it in the correct folder...
I have tried hundred of times, i just dont understand

you dont need unlock bootloader for stock kernel\rom right?

If you want to upgrade you better use Xperia companion.
If you want to downgrade and use FlashTool and if you have a problem you better have unlocked bootloader.

Guys,
This is a good tutorial. but I met a dead end, i got " processing partition.sin finished with errors" message, any suggestion?
Thanks for the help, this is my first time flashing
Regards

I am facing same issue i have xperia z5 dual unlocked bootloader i have installed flashtool and drivers correctly and i have placed the ftf firmware in given directory also but flashtool not showing any thing but for m4 aqua i am able to see the ftf firmware please help me
---------- Post added at 09:36 AM ---------- Previous post was at 09:32 AM ----------
EMJI79 said:
The firmware folder is not detected by Flashtool although I have put it in the correct folder...
I have tried hundred of times, i just dont understand
Click to expand...
Click to collapse
Same problem here:crying:

when i get to step 6 it starts flashing but then my phone just switch on on itself and the process stop

my IMEI become unknown,
please help

hi, can i do this on Z5C Docomo (SO-02H)?
also can i flash global rom on that...?

Hey guys.
I have a Z5 Compact (E5823) that's stuck on android version 5.1.1. It never shows any available updates in the Software Update screen. I'd like to get it on 6.0 in the least just for the better permissions system it contains.
In searching for a way to update it, naturally I found this page and all the helpful info it contains. I've never been steered wrong by XDA in the past. I've always found information on this site helpful, and it works.
I've downloaded Flashtool.
I've followed all of the instruction for installation, including the annoying driver installation process for Windows 8.1.
I've downloaded multiple firmwares from Xperifirm.
I can get everything happening, and it looks to work when looking at the Flashtool screen. It says it's complete (just like the little image at the bottom of the initial post).
Nothing seems to have happened to the phone. I boot it back up and it's still running the same old 5.1.1. Flashtool runs through it's process very fast, as in a few seconds, not the half an hour suggested.
The phone came from Hong Kong as far as I can tell. It may have been a refubished phone, I can't be sure. I'm trying to get the Customised AU version 6.0 software on it.
What am I doing wrong? I don't know what else to try, and it's annoying me. PLEASE HELP.
Thanks. Paul.

plazmafire said:
Hey guys.
I have a Z5 Compact (E5823) that's stuck on android version 5.1.1. It never shows any available updates in the Software Update screen. I'd like to get it on 6.0 in the least just for the better permissions system it contains.
In searching for a way to update it, naturally I found this page and all the helpful info it contains. I've never been steered wrong by XDA in the past. I've always found information on this site helpful, and it works.
I've downloaded Flashtool.
I've followed all of the instruction for installation, including the annoying driver installation process for Windows 8.1.
I've downloaded multiple firmwares from Xperifirm.
I can get everything happening, and it looks to work when looking at the Flashtool screen. It says it's complete (just like the little image at the bottom of the initial post).
Nothing seems to have happened to the phone. I boot it back up and it's still running the same old 5.1.1. Flashtool runs through it's process very fast, as in a few seconds, not the half an hour suggested.
The phone came from Hong Kong as far as I can tell. It may have been a refubished phone, I can't be sure. I'm trying to get the Customised AU version 6.0 software on it.
What am I doing wrong? I don't know what else to try, and it's annoying me. PLEASE HELP.
Thanks. Paul.
Click to expand...
Click to collapse
You better ask your question in the Z5 section, you're more likely to have answers and it's the same process (sorry I don't remember guq I did at the time I had the phone).
Sent from my HTC U12+ using XDA Labs

EMJI79 said:
You better ask your question in the Z5 section, you're more likely to have answers and it's the same process (sorry I don't remember guq I did at the time I had the phone).
Sent from my HTC U12+ using XDA Labs
Click to expand...
Click to collapse
Will do.
Thanks.

Hey, man, I used 9.18.5 and it worked

Mamada. said:
Hey, man, I used 9.18.5 and it worked
Click to expand...
Click to collapse
Any idea where I can find a good copy of version 9.18.5?

Hey,
I'm experiencing an issue with Flashtool.
Last weekend I successfully rooted my Z5C with the "How to root Z5C - the new, less painful way"-guide.
Finally the Z5C was flashed with Nougat (Customized DE) and rooted with Magisk (rooted with SuperSU first, but then switched to Magisk), even with working TA partition.
After reading that the Australian Stock ROM doesn't have battery drain issues, I tried flashing that one. Unluckily I'm always getting the following error:
17/059/2019 18:59:25 - ERROR - Processing of system.sin finished with errors.
17/059/2019 18:59:25 - INFO - Ending flash session
17/059/2019 18:59:25 - ERROR - ERR_SEVERITY="MINOR";ERR_CODE="0017";ERR_DYNAMIC="80090012";
Now I can't boot my phone and TWRP seems to be gone too, so I can't restore the backup I did beforehand.
Any idea how to fix this error?
EDIT:
If anyone wonders: I managed to make it work by downloading the firmware again and using a different USB-cable on a different USB-port. Can't say which of those things exactly helped.