Database Users

[TUTORIAL] How to Flash Stock Motorola Fastboot files

Welcome to my first tutorial! Please make suggestions in this thread on how to improve it. I will try to be a comprehensive as possible but also as general as possible since flashing firmware to Motorola phones is a pretty consistent process.
Disclaimer:
Please note, like almost everything else on XDA-Developers.com doing this process without fully understanding it can possibly brick the phone (although if it probably already is) thus, I cannot be held liable for any damages caused by following this process.
In other words, the person performing the work performed in this post is fully responsible for their actions on this phone.
/Disclaimer
Before starting with the flashing a Motorola phone, please review the following information:
In most cases firmware versions CANNOT be downgraded
Firmware from other regions can sometimes be flashed, but not always, this is why it is always recommended to stick with the same firmware branch that is already on the phone
The phone that will be flashed should be fully charged, the fastboot flashing process only allows for phones that are over 50 or 60% to be flashed.
If the phone that is trying to be flashed is under 50 or 60%, purchase a "factory adapter" - http://shop.teamblackhat.info/Factory-Adapters-motadapt.htm or make one - http://forum.xda-developers.com/showthread.php?t=1077414
Use a USB 2.0 port that is directly connected to the motherboard of the computer (preferably on the back of a desktop, or internal ports on a laptop)
Now, prepare the computer for the flashing process
Download the latest Motorola USB & Charging Drivers from http://www.motorola.com/Support/CA-EN/Support-Home/USB-Drivers-and-PC-Charging-Drivers
Download the latest available RSD Lite software (~6mb) - As of March 4th 2013, it is 6.1.4 and can be downloaded from here : http://d-h.st/KNN
Ensure the computer can detect the phone in fastboot mode (I have seen a number of problems with different versions of Windows, if it doesn't work on one PC, try a different one). To perform the test, power off the phone completely and boot it into fastboot mode. Unfortunately since Motorola phones are all built uniquley, this tutorial cannot cover all of the different methods to boot a phone in fastboot, but the most common method is to hold the VOLUME UP button and VOLUME DOWN button while pressing POWER. A menu will most likely appear, use the VOLUME DOWN button and navigate to "AP Fastboot", now press the VOLUME UP button. The phone should say it is OK to Program like in the following screen
{
"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"
}
Next, connect the USB cable to the computer, it should detect and install a driver. Check in device manager for a "Mot Single ADB Interface" under ADB Interface. If it is not listed, try to force the drivers to look in the "C:\Program Files\Common Files\Motorola Shared\Mobile Drivers\Drivers" folder.
Once the driver is loaded, open up RSD Lite and the internal codename should be listed under one of the ports. In RAZR HD (GSM) it says Fastboot VANQUISH_U S.
At this point, I would recommend to download the firmware to the computer that will be used for the flashing (once the phone is detectable in RSD Lite, that is a good indication the computer can detect the phone, navigate to http://motofirmware.center and locate the correct firmware and version that should be loaded on the phone. If the firmware is not listed there, please put a request into the firmware team (supply the default.prop and build.prop files). They are pretty good with locating firmware! The firmware files are generally large (ranging anywhere between 200mb and 1500mb) so now would be a good time to top-up that phone charge (if possible). If it isn't possible to charge the phone, don't worry, the phone will automatically turn off if it doesn't detect a flashing process after a few minutes.
Flashing Time!
Once the preparation has completed, flashing is very straightforward. Extract the downloaded firmware files to a folder on your hard disk, then use RSD Lite to load the XML file up. Power on the phone into fastboot mode again, and plug in the phone into an internal USB port on the computer, then press the start button. If everything is successful the phone should begin booting into the stock system. The flashing process usually takes 10-20 minutes depending on the size of the files and the power of the phone. If there are any failures, be sure to read the "Before getting started" section again, and hopefully someone on the forum can help recover the phone with you!

Re: [TUTORIAL] How to Flash Stock Motorola Fastboot & SBF files
danifunker said:
Welcome to my first tutorial! Please make suggestions in this thread on how to improve it. I will try to be a comprehensive as possible but also as general as possible since flashing firmware to Motorola phones is a pretty consistent process.
Disclaimer:
Please note, like almost everything else on XDA-Developers.com doing this process without fully understanding it can possibly brick the phone (although if it probably already is) thus, I cannot be held liable for any damages caused by following this process.
In other words, the person performing the work performed in this post is fully responsible for their actions on this phone.
/Disclaimer
Before starting with the flashing a Motorola phone, please review the following information:
In most cases firmware versions CANNOT be downgraded
Firmware from other regions can sometimes be flashed, but not always, this is why it is always recommended to stick with the same firmware branch that is already on the phone
The phone that will be flashed should be fully charged, the fastboot flashing process only allows for phones that are over 50 or 60% to be flashed.
If the phone that is trying to be flashed is under 50 or 60%, purchase a "factory adapter" - http://shop.teamblackhat.info/Factory-Adapters-motadapt.htm or make one - http://forum.xda-developers.com/showthread.php?t=1077414
Use a USB 2.0 port that is directly connected to the motherboard of the computer (preferably on the back of a desktop, or internal ports on a laptop)
Now, prepare the computer for the flashing process
Download the latest Motorola USB & Charging Drivers from http://www.motorola.com/Support/CA-EN/Support-Home/USB-Drivers-and-PC-Charging-Drivers
Download the latest available RSD Lite software (~6mb) - As of March 4th 2013, it is 6.1.4 and can be downloaded from here : http://d-h.st/KNN
Ensure the computer can detect the phone in fastboot mode (I have seen a number of problems with different versions of Windows, if it doesn't work on one PC, try a different one). To perform the test, power off the phone completley and boot it into fastboot mode. Unfortunatley since Motorola phones are all built uniquley, this tutorial cannot cover all of the different methods to boot a phone in fastboot, but the most common method is to hold the VOLUME UP button and VOLUME DOWN button while pressing POWER. A menu will most likley appear, use the VOLUME DOWN button and navigate to "AP Fastboot", now press the VOLUME UP button. The phone should say it is OK to Program like in the following screen
Next, connect the USB cable to the computer, it should detect and install a driver. Check in device manager for a "Mot Single ADB Interface" under ADB Interface. If it is not listed, try to force the drivers to look in the "C:\Program Files\Common Files\Motorola Shared\Mobile Drivers\Drivers" folder.
Once the driver is loaded, open up RSD Lite and the internal codename should be listed under one of the ports. In RAZR HD (GSM) it says Fastboot VANQUISH_U S.
At this point, I would recommend to download the firmware to the computer that will be used for the flashing (once the phone is detectable in RSD Lite, that is a good indication the computer can detect the phone, navigate to http://sbf.droidevelopers.org and locate the correct firmware and version that should be loaded on the phone. If the firmware is not listed there, please put a request into the firmware team (supply the default.prop and build.prop files). They are pretty good with locating firmware! The firmware files are generally large (ranging anywhere between 200mb and 1500mb) so now would be a good time to top-up that phone charge (if possible). If it isn't possible to charge the phone, don't worry, the phone will automatically turn off if it doesn't detect a flashing process after a few minutes.
Flashing Time!
Once the preperation has completed, flashing is very straightforward. Extract the downloaded firmware files to a folder on your hard disk, then use RSD Lite to load the XML or SBF file up. Power on the phone into fastboot mode again, and plug in the phone into an internal USB port on the computer, then press the start button. If everything is sucessful the phone should begin booting into the stock system. The flashing process usually takes 10-20 minutes depending on the size of the files and the power of the phone. If there are any failures, be sure to read the "Before getting started" section again, and hopefully someone on XDA can help recover the phone with you!
Click to expand...
Click to collapse
Would be best to download the files before entering the bootloader... I heard some nasty stories bout battery emptying out in BL/recovery and it messed up while flashing.
Charge up the phone before flashing and have the files ready prior to flashing.
Sent from my XT925 using xda app-developers app

saloums7 said:
Would be best to download the files before entering the bootloader... I heard some nasty stories bout battery emptying out in BL/recovery and it messed up while flashing.
Charge up the phone before flashing and have the files ready prior to flashing.
Sent from my XT925 using xda app-developers app
Click to expand...
Click to collapse
Yes, I understand what you're saying, but I've seen a lot of nightmare PCs out there recently, so I want to do a compatibility check before you end up downloading a large file and not being able to use it.

danifunker said:
Yes, I understand what you're saying, but I've seen a lot of nightmare PCs out there recently, so I want to do a compatibility check before you end up downloading a large file and not being able to use it.
Click to expand...
Click to collapse
Works like a charm. Thank you.

danifunker said:
Yes, I understand what you're saying, but I've seen a lot of nightmare PCs out there recently, so I want to do a compatibility check before you end up downloading a large file and not being able to use it.
Click to expand...
Click to collapse
Good point good thing I have unlimited bandwidth so that doesn't affect me too much
Sent from my XT925 using xda app-developers app

If you have "battery low" during flashing, and you can't make the phone boot, just discharge it completely and then plug the phone into charger (it will charge in "emergency mode" without booting).

Thanks for this post....after issues with CM 10 and no GPS....I flashed back to Rogers/Fido 4.1.2. very happy....here is hoping if there are any future updates this ROM will auto update. Or I can wish for a working CM 10.1 some day
Sent from my XT925 using xda app-developers app

shredrex said:
Thanks for this post....after issues with CM 10 and no GPS....I flashed back to Rogers/Fido 4.1.2. very happy....here is hoping if there are any future updates this ROM will auto update. Or I can wish for a working CM 10.1 some day
Sent from my XT925 using xda app-developers app
Click to expand...
Click to collapse
Hi shredrex, I am also having the same problems and I want to flash back to rogers/fido 4.1.2. May I know where you got your files from? I would really appreciate it!!

taeotut said:
Hi shredrex, I am also having the same problems and I want to flash back to rogers/fido 4.1.2. May I know where you got your files from? I would really appreciate it!!
Click to expand...
Click to collapse
I posted the wrong link in the original tutorial, thanks for flagging it.
Check this site : http://sbf.droid-developers.org/
Good luck!

i´m trying to install the telcel firmware and also used 2 different computers with the lastest drivers and rds lite 6.1.4
I followed all the steps and doesn´t work for me I´ve got the next error
failed flashing process. unknown fastboot command getvar
Help me please

Hi danifunker, I am new to Motorola and I have the RAZR i (XT890). I'm making two guides related to helping new people to Motorola phones here . May I link your guide here, of course giving full credit? I basically would like to recommend new users to the RAZR i to read good guides like this before they brick their phone. We get about 5 bricks a day over there!

gorefrausto said:
i´m trying to install the telcel firmware and also used 2 different computers with the lastest drivers and rds lite 6.1.4
I followed all the steps and doesn´t work for me I´ve got the next error
failed flashing process. unknown fastboot command getvar
Help me please
Click to expand...
Click to collapse
The firmware you downloaded has a .xml file in it. Remove the line with Getvar in it, and try to flash again.

elcacho said:
The firmware you downloaded has a .xml file in it. Remove the line with Getvar in it, and try to flash again.
Click to expand...
Click to collapse
Thanks, now I´m installing the firmware

elcacho said:
The firmware you downloaded has a .xml file in it. Remove the line with Getvar in it, and try to flash again.
Click to expand...
Click to collapse
Can we have this put into the tutorial please.
Also, as for the OP in general, thanks for putting this here; its not so clear elsewhere on this section of the forum and everything that is useful to a Motorola noob is specifically for the XT926... even the blog posts linked to. I had a lot of anxiety over trying this in the past because things as fundamental as this, concerning Motorola and these phones in particular as well, are scattered and disorganised in various places on the internet. Its frustrating and makes one want to shy away from trying things out for fear of not being able to return to stock or bricking their device. I come from an SGS2 which had no fastboot to worry about, for example, and even though the RAZR HD forum had few participants when I first got mine, there was still a lot to be confused about and to shy away from.

Im trying to flash the filmware to my phone cause my camera stopped working shortly after i updated my droid razr to 4.1.2, and when i did the ap fastboot filmware update, everything comes back like it already was should i remove everything from my phone and try again?
Edit: My Safestrap is gone, and now i have no service..
Edit Again: Service restored after i removed everything, another problem tho. Camera still wont initialize now

Firmware Motorola V9 bootloader 04.C1
Dear XDA members, need firmware in Portuguese with the Motorola V9 bootloader 04.C1. I thank you.

Thanks for detailed instuctions! Worked perfectly for Motorola XT862.

Ok to program option
I have been running 4.2.2 aokp unofficial, and its been awesome.. i need to flash back to stock because im going to be selling my phone soon, when i try to use mattlgraf's utility i always get the unable to mount error message.. im going to be trying this option aswell, but I have a feeling it wont work because i dont get the "OK to program" in AP Fastboot, if you have any idea why this is happening just reply to this post, thanks for all the material guys.
---------- Post added at 11:05 AM ---------- Previous post was at 10:58 AM ----------
thetigerag said:
I have been running 4.2.2 aokp unofficial, and its been awesome.. i need to flash back to stock because im going to be selling my phone soon, when i try to use mattlgraf's utility i always get the unable to mount error message.. im going to be trying this option aswell, but I have a feeling it wont work because i dont get the "OK to program" in AP Fastboot, if you have any idea why this is happening just reply to this post, thanks for all the material guys.
Click to expand...
Click to collapse
I got an error message that said "Failed flashing process. Unknown fastboot command" im not sure if this is due to the new firmware because of running 4.2.2 or what.. any information would be appreciated - Thanks.

Use MATT's utility v1.2
Look for the v 1.2 and give it a try.
I was able to go back to stock ICS on the xt925 (Rogers)

itzik_man said:
Look for the v 1.2 and give it a try.
I was able to go back to stock ICS on the xt925 (Rogers)
Click to expand...
Click to collapse
Yes, 1.20 was the utility i originally used.
I get the error message 'fastboot' is not recognized as an internal or external command, operable program or batch file. multiple times, then it takes me back to the main screen.
---------- Post added at 10:45 PM ---------- Previous post was at 10:04 PM ----------
Got it all worked out, thanks guys.

Root/TWRP/SD Fix/Init d/FlashPlayer/ADBlocking/debloating the SM-T900 / T900UEUAND4

Update 10/30/2014
There's no need to go back to the "B3" version any longer. The T900UEUANI1 is available on SamMobile, to be flashed w. Odin.
The cf-auto-root listed as "B3" on chainfire's site will work.
Note, I have not created any of this, please thank the original developers in their posts. This is simply a compilation of available info needed to have the most complete and working SM-T900, Samsung Galaxy Tab Pro 12.2.
The sole purpose is to make you save time. However, I'm not saying this will work, and it might even brick your device, but that risk is yours to take. However, it worked for me, so why shouldn't it... Trust the steps, there's a reason for this madness. Believe me when I say it; I've learned the hard way, and it has not been a pleasant journey.
If your SD cards looses necessary rw privileges it seems like not even a backup will correct them, even after wiping the SD cards and formatting data.
If you haven't yet upgraded from B3 to D4, I recommend you to do this first! There are major improvements between the two versions.
1. Rooting:
First flash the P900XXUANB3-RecoveryImg (forgetting this will create a softbrick, and you will have to start over, also use the Odin 3.07, supplied, I have not tested with the later 3.09)
then flash CF-Auto-Root-v2wifi-v2wifixx-smt900
for detailed method and files see: http://androidcentral.us/2014/05/root-galaxy-tab-pro-12-2-sm-t900/
I forgot, it's important to use original cables directly connected to the PC, a docking station connection, or an EOM cable might be a reason for flash failure.
2. install TWRP:
Flash openrecovery-twrp-2.7.1.0-v1awifi
link: http://forum.xda-developers.com/showthread.php?t=2679825
3. disable Knox:
Open SuperSU and answer yes to disabling KNOX
4. fix SD-card issue in KitKat 4.4:
Download and run JRummy's "SD KitKat Fixer" from market. I had no luck with any other comfortable fixing apps.
5. important!:
reboot into recovery and wipe both External and Internal SD, as well as Formatting Data. Don't forget to backup all files you want to keep onto your PC! for later re-installation. I know this must feel hard, but I sincerely advice you you follow this step. Most apps are not KitKat ready, as of now, and won't allow you to download or access the data if you haven't prepared your SD's in advance.
6. init d support:
Download and install Stericson's BusyBox from market
Download and install Uni-init v1.0
link: http://forum.xda-developers.com/showthread.php?t=1933849
7. Flash Player support:
Download and install fixed AdobeFlashPlayer 11.1
link: http://forum.xda-developers.com/google-nexus-5/help/guide-how-to-play-flash-video-android-4-t2548001
If you're using Dolphin Browser, also install the Dolphin JetPack, and modify Settings/Web Content/Flash Player/ to Always On.
8. ADBlocking:
Dowload and flash LATEST_MoaAB_ADBlocking_Super
link: http://forum.xda-developers.com/showthread.php?t=1916098
9. De-bloating:
for de-bloating at a maximum you can disable numerous of the Samsung apps, by pushing the three dots, upper right corner, while in the apps-screen mode.
Also, don't forget to un-check the de-bloated apps from auto-update in Play Store, as well as in the Samsung update if you signed up for this service.
10. (Re)-nstall your apps
You're done, and it's time to restore or download all the apps you need and it will work in KitKat 4.4
None of the modified stock ROM's currently available seem to mount correctly. If something goes wrong, you will most likely loose your SD card privileges. The original T900UEUAND4 stock ROM can be found here: http://www.sammobile.com/firmwares/3/?download=29102. Just unzip and flash with Odin, then start again with step 1.
Also, due to lack of time, I will not be able to monitor this post. I hope you will help one another out with clarifications, or anything I might have missed.
Best of luck,

Delete

Very nicely laid out. I've already done all this, but it's great to see a guide for new comers that may not know what to do. Thank you.

Thank you for the guide and gathering everything together. I just wanted to throw this out there, I followed the directions exactly....and I could not get mine to root. It would continually soft brick and a screen full of odd colors would come up every time. I read on the CF Auto Root thread that others had the same issue. One determined individual said he did it 10 times and it finally worked. Soooo....I continued to do it. And it finally worked, trying nothing different each time.
I tried 2 different computers, a win7 and win8, installed Kies to make sure drivers were there. Used official and another cable. I tried everything I could think of. In the end I would say as long as you're following the directions just keep trying.
http://forum.xda-developers.com/attachment.php?attachmentid=2591013&d=1392923580
That's a link to the P900XXUANB3-RecoveryImg that my friend and I both used before getting root. Thanks again for the guide arcadia2uk!

So I was able to root and install TWRP but after an app caused some issues I went to wipe cache and brick. Flashed stock and had to do factory reset. However, I learned that attempting to restore a backup or wipe cache or do factory reset via twrp causes brick. Have to use Odin to flash back to factory. I also had to use the German region and lost my symbols on keyboard.
................edit..............
I updated kies and reinstalled all the drivers and flashed the cellular south firmware...All is well and current. Rooted, twrp, having fun.

Hi,
I followed all instructions but Flashing was successfully only after USB driver update. This is my story:
My Tab Pro 12 has ND4 stock.
Downgrade P900XXUANB3-RecoveryImg with Odin.
Then flash CF-Auto-Root-v2wifi-v2wifixx-smt900.
All Odin task stucked at Cache and after a few minutes screen got attached frightening picture
{
"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"
}
.
Then tab not booted.
Tried this http://forum.xda-developers.com/showpost.php?p=54576936&postcount=63
and tried different usb ports, cables.
But no success.
Then I installed latest Kies3 (started only the usb driver in tools menu) then restart Win7 and after then all right.
Odin flashed CF root.
Best wishes I hope this helps!

deleted

robert1968 said:
Hi,
I followed all instructions but Flashing was successfully only after USB driver update. This is my story:
My Tab Pro 12 has ND4 stock.
Downgrade P900XXUANB3-RecoveryImg with Odin.
Then flash CF-Auto-Root-v2wifi-v2wifixx-smt900.
All Odin task stucked at Cache and after a few minutes screen got attached frightening picture
.
Then tab not booted.
Tried this http://forum.xda-developers.com/showpost.php?p=54576936&postcount=63
and tried different usb ports, cables.
But no success.
Then I installed latest Kies3 (started only the usb driver in tools menu) then restart Win7 and after then all right.
Odin flashed CF root.
Best wishes I hope this helps!
Click to expand...
Click to collapse
The fix is actually put the m
Sent from my HTC One_M8 using Tapatalk

I don't know if it will help anyone else, but I just flashed TWRP 2.8 on my Galaxy Tab Pro 12.2 wifi with "D4" firmware using odin and it worked and I was able to make successfully a backup. Below is a link to the recovery I flashed. Of course your mileage may vary so do it at your own risk.
http://teamw.in/project/twrp2/244

The easiest way to debloat it is probably via titanium backup's batch mode actually.

Oh boy I just mess up my Tab.... It's stock in the firmware error screen. Will try to flash stock firmware as soon as I get WiFi, reflashing stock via Odin should fix it as I read right?
Fingers crossed: say yes please!
Edit: it boots with stock fw now is back to normal except that can't access or boot into recovery mode. Any help or a working recovery file? Thanks in advance
Sent from my HTC One using Xparent BlueTapatalk 2

saruba said:
Oh boy I just mess up my Tab.... It's stock in the firmware error screen. Will try to flash stock firmware as soon as I get WiFi, reflashing stock via Odin should fix it as I read right?
Fingers crossed: say yes please!
Edit: it boots with stock fw now is back to normal except that can't access or boot into recovery mode. Any help or a working recovery file? Thanks in advance
Sent from my HTC One using Xparent BlueTapatalk 2
Click to expand...
Click to collapse
try flashing the latest TWRP 2.8.1.1 with Odin. You can also download Quick Boot (Reboot) from Play Store, that will facilitate the booting process.

arcadia2uk said:
try flashing the latest TWRP 2.8.1.1 with Odin. You can also download Quick Boot (Reboot) from Play Store, that will facilitate the booting process.
Click to expand...
Click to collapse
Yey! U R the man! Thanks so much it works flawlessly!
I think I have 2 different recovery files and they both doesn't work I don't know why I got them from twrp site... Anyways just to let you know I've done every thing with Odin 3.09 so yeah I'm confirming that it works fine.
Sent from my HTC One using Xparent BlueTapatalk 2

[Root] CFAutoRoot For SM-T807T/SM-T807P + Firmwares

Note: I did not make any of these root methods. Credits of the people who confirmed/ported cfautoroot is at the end of this post. I got permission to post these root methods here as most of the discussion happened in the General thread. I am not responsible for any damages done to your device. This will trip knox as always and this root method is only for the TMobile and Sprint Tab S 10.5! You've been warned!
Root is now available for these devices! Hope you enjoy and hopefully this should get some development going!
CFAutoRoot for SM-T807T(Tmobile)
Ripx88 confirmed T805 Cfautoroot works for SM-T807T, but you may have a broken recovery. He also confirmed that Twrp and Philz CWM for SM-T805 also works on the SM-T807T. Thanks to him!
Download: http://download.chainfire.eu/477/CF...-Auto-Root-chagalllte-chagallltexx-smt805.zip
CFAutoRoot For SM-T807P (Sprint)
Goriell ported Cfautoroot to this model. Props to him! Still awating for others to confim.
Download: https://mega.co.nz/#!eoB3TbxI!fdUUK-GJFfDx7ietfosnxxHHB2WN4tV0SGieQsdL9tA
Mirror: https://docs.google.com/file/d/0B5DZenb7A53cQldyRGw2TWhBeVk/edit?usp=docslist_api
Odin Download
http://forum.xda-developers.com/showthread.php?p=33970642
How to install
Make sure that in settings>general>security reactivation lock is OFF
edan1979 said:
Follow these instructions to the letter. Do not touch any buttons or checkboxes that are not listed below to touch!
- Download and unzip the CF-Auto-Root-....zip file (see posts below this one)
- If you end up with a recovery.img and cache.img file, you've extracted twice. You need to end up with a .tar.md5 file - don't extract that one
- (USB) Disconnect your phone from your computer
- Start Odin3-vX.X.exe
- Click the PDA (AP in odin v3.x) button, and select CF-Auto-Root-....tar.md5
- Put your phone in download mode (turn off phone, then hold VolDown+Home+Power to boot - if it asks you to press a button to continue, press the listed button, or run adb reboot download command)
- (USB) Connect the phone to your computer
- Make sure Repartition is NOT checked
- Click the Start button
- Wait for Android to boot
- Done (if it took you more than 30 seconds, you need practise!)
NOTE: Sometimes the device does *not* boot into recovery mode and root your device. Just do the entire procedure again if this happens. If it still will not install root and such, make sure that in Odin "Auto Reboot" is not checked. Then after flashing, manually shutdown your device and boot with VolUp+Home+Power button to boot into recovery manually. This will start the install process.
New to Samsung? Unfamiliar with Odin? Think all the above is a hassle? Get used to it. It's very simple, and us Samsung folk use Odin (or Mobile ODIN ) for everything! It's so very very convenient once you get used to it. Notice the 30 second comment above? For experienced users, the entire process indeed takes only 30 seconds!
Flashing with Odin
1. Put your phone into download mode. To do this turn the phone off and then press volume down+home button+power button at the same time. You will then get a warning saying press up to continue and down to cancel, press volume up and you are now in download mode
2. Start Odin
3.At this point please make sure that ONLY TWO OPTIONS TICKED are "Auto Reboot" and "F.Reset Time" (otherwise you could end up with a very expensive paperweight)
{
"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"
}
4. If there was only one tar file when you extracted the firmware put it in the PDA section.This just means this file contains the PDA+PHONE+CSC all in one firmware
If there are three files they should have one of PDA/PHONE/CSC in their names look for this and put them in the corresponding section.
5. Plug your device into the computer, wait for the drivers to install and then wait for the ID:COM section to turn blue.
6.ONCE AGAIN CHECK YOU HAVE NOT TICKED RE-PARTITION OR PUT IN A PIT FILE
7.Press start and the flash will begin, once this has started do not remove the usb cable or turn of your computer or the device the phone will reboot once the flash has finished.
Click to expand...
Click to collapse
Thanks:
-Chainfire for Cfautoroot method
-Ripx88 for confirming root working on T807T. Helped ALOT!
-goriell for explaining how to port and porting it to SM-T807P. Helped ALOT!
-Samsung
-Samsung updates for firmware... took me 14 hours to download and mirror
-Many many more
-Tkkg1994 for help on somethings

Post from main thread.
CF-Auto-Root is the root for "rooting beginners" and those who want to keep as close to stock as possible. CF-Root is meant to be used in combination with stock Samsung firmwares, and be the quickest and easiest way for your first root. In essence, it does nothing but install and enable SuperSU on your system, so apps can gain root access.
Donate
CF-Root and CF-Auto-Root have been available for many devices (over 50 different models !) and have clocked over 9 million downloads. This is not even counting custom ROMs that include CF-Root (non-Auto) kernels. Don't be a leech, buy me a beer (and use the "Thanks" button!). Imagine if every user had donated me $1...
What's installed
- SuperSU binary and APK
- Stock recovery (note that any other recovery you may have installed will be overwritten !)
What's the difference between CF-Auto-Root and CF-Root, and/or other root solutions ?
CF-Root (non-Auto) are manually built rooted kernels and/or flashables that usually provide more than "just root". CF-Auto-Root is built on an automated system that I am constantly improving that takes a stock recovery image and returns an automated rooting packages. These packages are designed to install and enable SuperSU on your device, so apps can gain root access, and nothing more.
The difference with many other rooting solutions is that those will often install a custom recovery for you (I am personally moving away from custom kernels and recoveries, for various reasons), while with CF-Auto-Root you will end up with a stock recovery again.
Not included - custom recovery
A custom recovery like CWM or TWRP is not included.
Not included - Triangle Away
Triangle Away can be used to reset the flash counter after installing CF-Root. The flash counter keeps track of how many custom firmwares you have flashed, as this voids warranty. (No idea what this about ? Read up on it, you will want to use this !)
Not included - adbd Insecure
As this CF-Root does not include a custom kernel, adb shell does not have root access by default (you can still get it by typing su inside the shell), nor is adb remount supported, nor will adb push and adb pull work on system files. adbd Insecure can be used to remedy this situation. (No idea what this is about ? Don't worry about it !)
CF-Auto-Root homepage
http://autoroot.chainfire.eu/

Bugs.
WIFI Bug Fix: In root explorer go into system/etc/dhcpcd/dhcpcd-run-hooks
It needs to have permissions fixed to "execute" by "user" "group" and "others" by using your favorite file explorer
this will fix your "obtaining ip address loop" without having to ever use static ip address- goriell

You know what.. here is the kernel and stock recovery for the SM-T807T.
Bop! https://mega.co.nz/#F!PwwT3JLQ!KHZNbb3ddgfStcdcB4rmlQ
Firmware to SM-T807T: https://mega.co.nz/#!ylYEBA4D!yWUPtuT60dLCIy_zCN_rqnN2L319oZYSCSFtOC_Pv6Q
Firmware for SMT807P: https://docs.google.com/file/d/0B5DZenb7A53caXhNQkhMb0NkMFU/edit?usp=docslist_api
Bop! Recovery and boot image for SMT807P: https://www.dropbox.com/sh/h5zw61wdn6rx319/AADS2Wb8OFDw3DxpuES7GI2Va?dl=0
Incase anything goes wrong Enjoy

Will look into this later this evening. I have been patiently waiting for a root method for my Sprint Tab S, so I'm really hoping this pans out. Thanks for posting the info!

wosiek said:
Will look into this later this evening. I have been patiently waiting for a root method for my Sprint Tab S, so I'm really hoping this pans out. Thanks for posting the info!
Click to expand...
Click to collapse
Please let me know if it works smoothly. I'm still in the process of tweaking it and looking for bugs.

Anyone have the firmware for the T807P? I see the T807T is up there, but think us Sprint users would need the correct firmware correct or we can run the TMo variant and be fine? Just want to confirm. If that is all we need. I'll go ahead with the process right now.

gorriel said:
Please let me know if it works smoothly. I'm still in the process of tweaking it and looking for bugs.
Click to expand...
Click to collapse
Hey do you have the firmware downloaded? If so can you mirror it for us? I dont have an extra 14 hours to download and upload the firmware

Tried to download the CFAutoRoot file (Sprint SM-T807P) from the link in the OP, but the webpage couldn't be found.
Anyone else experience similar behavior?

wosiek said:
Tried to download the CFAutoRoot file (Sprint SM-T807P) from the link in the OP, but the webpage couldn't be found.
Anyone else experience similar behavior?
Click to expand...
Click to collapse
Works fine for me. Are you on att? Mirror to google drive will be coming. Standby

Yeah, the WAN at the office is managed by ATT. Are they notorious for having issues with MEGA?
I'll try downloading again from home this evening - meant to do that last night, but it fell off my radar.

wosiek said:
Yeah, the WAN at the office is managed by ATT. Are they notorious for having issues with MEGA?
I'll try downloading again from home this evening - meant to do that last night, but it fell off my radar.
Click to expand...
Click to collapse
Att blocks mega because of the history of mega and copyright claims. Ill make another mirror with google drive.

For anyone having trouble with the T807P root please post information on what happened and I will try to troubleshoot it. It is suppose to be a quick and easy CFAutoRoot using ODIN. I will say that it doesn't work if you are trying to use Odin on a virtual machine. It will stop as it tries to upload the cache.img. There is something about virtual machines that blocks it or Odin just doesn't like.

Uploading Sprint firmware now Will also upload the boot.img amd recovery if a dev wants them.

CFAutoRoot For SM-T807P (Sprint)
Can you host the
CFAutoRoot For SM-T807P (Sprint) on something other than mega, Like Drive or Dropbox please. I have Time Warner and i can't download it for some reason.

kingakuma said:
Can you host the
CFAutoRoot For SM-T807P (Sprint) on something other than mega, Like Drive or Dropbox please. I have Time Warner and i can't download it for some reason.
Click to expand...
Click to collapse
Will do hold on

DUHAsianSKILLZ said:
Will do hold on
Click to expand...
Click to collapse
Thank you my good sir.

kingakuma said:
Thank you my good sir.
Click to expand...
Click to collapse
Here ya go https://docs.google.com/file/d/0B5DZenb7A53cQldyRGw2TWhBeVk/edit?usp=docslist_api

DUHAsianSKILLZ said:
Here ya go https://docs.google.com/file/d/0B5DZenb7A53cQldyRGw2TWhBeVk/edit?usp=docslist_api
Click to expand...
Click to collapse
Thank you worked great with Odin 3.09

I can only access odin download mode, i can't access any recovery, how can I flash back to stock?

[GUIDE]SM-T710 6.0.1 Marshmallow Installation and fast DL link

This guide has been made for sm-t710, but you can follow it for any model (t715, t810 and t815) by just using the right Odin flashable TWRP file and Odin flashable firmware file for your device.
Here you have the link(for sm-t710):
T710XXU2CPD9_T710BTU2CPD9_BTU.zip
Just downloaded from www.sammobile.com T710XXU2CPD9_T710BTU2CPD9_BTU/ and re-uploaded to MEGA.
Tested and working on my spanish sm-t710, in my case I had my device rooted and with TWRP, as well as a 5.1.1 Optimal Rom.
After following this instructions, somehow i didn't loose any personal data or installed aplication, so this guide will just update our device from lollipop rom to Marshmallow BUT we will loose root AND TWRP, just follow the guide to reinstall TWRP and root after update. If you didn't had root before following this guide, you can root the tab before of after it, but I recomend you to first install TWRP and backup personal data before following this guide.
Instructions:​Requirements:​->Root the tablet. (Recomended)
->Install TWRP (Recomended but I think it isn't needed)
->Enable USB Debugging on your tab.
->Make sure you have Samsung drivers installed on your PC.
->Download and extract the zip file to get the firmware file which is in .tar.md5 extension.
->Download and extrat Odin from here: Odin3_v3.10.7.zip
Installation:​1->Turn off your tab and boot it into the Download Mode. To do this, turn off your device and then press and hold Volume Down + Home + Power buttons simultaneously for 2-3 seconds. When you see the warning screen with a yellow triangle sign, press the Volume Up/Down key to enter Download/Odin mode.
2->Download the required Odin.zip file and extract the file on your PC. You will get the Odin3_v3.10.7.exe file. Open it as the administrator to get to the Odin window.
3->Connect your Galaxy device to the computer using the USB cable.
4->When you connect the device, the ID: COM port on Odin will turn Blue. You’ll also see“Added!!” message to indicate successful connection. If Odin des not detect your tab, try to reinstall drivers, try another usb cable and another usb port.
5-> Check "AP" box and click on AP. A window will pop up, just go to the folder where you extracted the firmware and select T710XXU2CPD9_T710BTU2CPD9_HOME.tar.md5 file (name may vary according to device model)
6->Now Odin is checking MD5 and will freeze for a minute or so, but don't worry, just let Odin work.
7->Click on the "Options" section and make sure that only the Auto Reboot and F. Reset Time boxes are checked. (Do not, in any case, check Re-Partition box).
8->Now, click the Start button on Odin to begin firmware installation.
10->Once you get a PASS! message on Odin, your device will restart. It’s the green signal that indicates a successful installation.
11->Once our device restarts, you can disconect it.
12-> Enjoy Marshmallow :fingers-crossed: on our Tab s2 (First boot will last for some minutes, just be patient! :laugh: )
TWRP installation:​1->Download TWRP from this THREAD according to your device (Lollipop 5.X.X just works fine). Thanks to ashyx.
2->Flash with odin following steps 2 to 11 from above.
12->Enjoy Marshmallow with TWRP!
ROOT:​1->Download the SuperSu TWRP flashable ZIP from this THREAD (don´t extract it) and put in on the root of the internal sd by conecting the device to pc.
2->Turn off our device.
3->Hold HOME+VOL UP+POWER until TWRP screen apears.
4->If it says something about reading-only mode, just swipe that whtie triangles from below.
5->On the main menu, select "Install" and click on the SuperSu zip, then swipe to confirm flash.
6->Reboot and enjoy Marshmallow with TWRP and root! :highfive: :good:

will this method trip knox if you dont root or install twrp (void warranty?) thanks

nolook said:
will this method trip knox if you dont root or install twrp (void warranty?) thanks
Click to expand...
Click to collapse
No it will not, you are installing stock firmware.

nolook said:
will this method trip knox if you dont root or install twrp (void warranty?) thanks
Click to expand...
Click to collapse
Hi, this isn't a modified (untouched)firmware file, so if you flash with odin it may not trip knox warranty. I'm not completely sure, as I had knox warranty void before. The problem comes when you try to flash anything non-official files with Odin (modified roms, root or twrp), these files will trip the knox flag for sure.

thanks for the replies im new to flashing samsung devices (coming from nexus)..
one other question...my CSC is XAC (canadian) will that stay the same if i flash this UK rom? ive read some have had issues with wifi with flashing other region roms...TIA

I recommend you guys try out http://www.apkmirror.com/apk/samsun...elease/good-lock-24-0-7-android-apk-download/ . It is awesome. Tablet feels like a Nexus.

Just upgraded my T710 from 5.1.1 to 6.0.1 with user data untouched. TWRP, root and Xposed all reinstalled successfully. One thing worth mentioning is that for SuperSu, Latest version (BETA-SuperSU-v2.71-20160331103524.zip) instead of Stable version has to be used.

I am in India ?? and I want to update my tab s2 8.0 to m so when is Ota coming and will the UK rom trip the know meter being it frortanother region????? Answer fast

Androbots said:
I am in India ?? and I want to update my tab s2 8.0 to m so when is Ota coming and will the UK rom trip the know meter being it frortanother region????? Answer fast
Click to expand...
Click to collapse
If you bother to read the thread you'd know it won't trip knox if it's unmodified Samsung firmware. Also, telling people to answer quick is rude. Please learn to read the thread before you ask questions, and learn this is a forum, people will answer as they see the question and when they have time.
Sent from my SM-G935V using Tapatalk

How will installing this affect devices running in different regions? Will we start getting the UK updates from now on? Does this affect Wi-Fi in some way?
Sent from my SM-T710 using XDA-Developers mobile app

Can you install this on the t810? Might be as dumb question but they are identical?

If you FACTORY RESET AFTER installing SuperSu, You will need to reflash the marshmallow image again to re-root.

there're no news for the T810?

No files available for T810 yet... Just wait a little longer
Sent from my LG-D855 using Tapatalk

so is wifi 5g working?

mk89pwnz said:
so is wifi 5g working?
Click to expand...
Click to collapse
Not on mine.
Sent from my SM-G935V using Tapatalk

All appears well. Region info seems fine, Netflix plays fine. Google Finds my location fine. Anything else need to be checked?
Sent from my SM-T710 using Tapatalk

Unless I'm doing something wrong 5g seems to be working for me
5g
{
"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"
}
2.4g
Sent from my SM-T710 using Tapatalk

kylemccracken said:
How will installing this affect devices running in different regions? Will we start getting the UK updates from now on? Does this affect Wi-Fi in some way?
You may not be able to connect to any Wireless N 5G networks as the UK uses another frequency range for that, however mine keeps appearing, then vanishing, so I'm not sure what that's all about
Another thing I noticed, it does NOT allow you to format your SD card as internal storage. I'm running Cm13 on an LF v400 that allows formatting a fast enough SD card as internal, so I'm not sure if that's some work done by the CM team or if Samsung has disabled this feature. It was my understanding that even Lollipop was supposed to do this but neither tablet will, so I thought at least Marshmallow 6 or 6.0.1 would, but with this UK ROM, I am unable to do so.
---------- Post added at 09:04 PM ---------- Previous post was at 09:01 PM ----------
miguimercadob said:
Hi, this isn't a modified (untouched)firmware file, so if you flash with odin it may not trip knox warranty. I'm not completely sure, as I had knox warranty void before. The problem comes when you try to flash anything non-official files with Odin (modified roms, root or twrp), these files will trip the knox flag for sure.
Click to expand...
Click to collapse
I rooted mine without tripping Knox... at least until it asked me if I wanted to disable Knox alerts, then it tripped the flag. I had rooted it twice before, without disabling and Knox was still flagged 0, so if you root it, DO NOT CHOOSE TO DISABLE THE WARNINGS ABOUT KNOX.
---------- Post added at 09:10 PM ---------- Previous post was at 09:04 PM ----------
kylemccracken said:
How will installing this affect devices running in different regions? Will we start getting the UK updates from now on? Does this affect Wi-Fi in some way?
I believe it the update app checks the model and build number, so it's most likely you'll get the UK updates. You can always reflash the official US one once we get it (or which ever country you're from) and then it'll update the proper region
Click to expand...
Click to collapse
Click to expand...
Click to collapse

My gripe about not being able to format the SD card as Internal is pretty legit. Other devices it gives you both options when you format the SD card: Portable or as Internal storage.
The Galaxy Tab S2 with the UK firmware does NOT have the option.
You can, however, turn USB debugging on, authenticate the computer, and:
adb shell
sm list-disks
take note of the disk named, it should only list one like "disk:166:190"
type sm partition disk:166:190 private (To utilize the whole disk as internal)
or
type sm partition disk:166:190 private mixed 50 (To use 50% of the disk as internal and 50% portable) This method will show two disks when you plug the device into the computer, while the other aforementioned option will only show one - the now larger internal disk.

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.