TWRP only - JiaYu S3 Questions & Answers

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.

Related

[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

[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.

[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

[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.

[Guide] LG G5 Back to Life [Download mode] [LG Flash tool] [Unknown model in LGUP]

Overview::​Well, something bad happened to my phone (H830), then LGUP said unknown device. I tried many tools, different KDZ but all went failed
What Actually happened in my case:​
I had mm stock 10d ROM then I upgraded to 20a using LGUP KDZ method by using uppercut trick. I wanted to enjoy Fulmics 1.5 (for my H830), but was newbie so had no idea about rooting it and installing (Because all available guides were actually complexed or I was impatient to read other things except main procedure). So I did something strange and Fulmics was installed over 20a ROM, because I was unable to wipe internal storage due to that decryption thing.
So I thought, I should go back to stock by using LGUP and retry the procedure with more focus. This time LGUP didn’t know my phone, not with that uppercut too. I thought that’s because I unlocked bootloader and must first try to lock it, and try again with LGUP. I retried with locked bootloader and failed again.
(Remember, LGUP or any other tool have nothing to do with back to stock thing. You can go back to stock whether you are bootloader locked or unlocked, it has no power of stopping you.)
Possible Cases:​So I will not waste the time. Possible cases:
1: LG G5 stuck on download mode and it is now not being recognized by LGUP and you can’t do anything, because no other tool is available.
2: You installed a custom ROM and now LGUP is not recognizing it. You want to go back to stock and can’t do it.
3: Anything bad happened during flashing process, PC restarted, phone went off or whatever. And now you can’t bring it back to life.
¬ Or
Other cases you faced.
Read 4th post before proceeding,
Before asking a question, first, see FAQ in 3rd post. In that way you can save a lot of time.
For Video Guide refer to 4th Post
Things You need:
​1: LG UP
2: Uppercut
3: Drivers
4: Stock ROM for your device.
All Herehttps://forum.xda-developers.com/lg-g5/development/uppercut-lgup-loader-g5-variants-t3511295
5 : LG Flash tool (the one used to bring LG G2, G3 back to stock).
I used 20a KDZ because I had it already and it was nougat with vulnerability to root and flash TWRP.
6: LG Firmware extract tool
In 2nd post
Most tools can be found in attachments of 2nd post.
Process:​
First:
Uninstall all other tool, previous driver (including other phone’s too). Restart PC
Just to avoid problems. I tried this process many times on Windows 10 64-bit and it always worked for me. So it has no problems with new Windows OS.
Now follow procedure in exact order.
1: Install LG drivers.
Put Phone in download
(Hold Vol+ and connect to PC while it was powered off).
Wait until it finishes installing drivers. Change COM Port to 41.
{
"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"
}
( Refer here for changing this, If you can’t understand that.)
Now DC it from PC and keep it staying in Download mode.
2: Install LG Flash tool and copy megalock.dll to installation directory or it won’t work.
3: Install LGH-H830_DLL, LGH850_DLL and LGUP_Store_Frame_Ver_1_14_3.
4: Extract LG Firmware Extract and copy Stock KDZ to that folder.
5: Run WindowsLGFirmwareExtract.exe
A: Click on “KDZ file” open and select stock KDZ.
B: Mark File Name. It will select all files. Click on extract KDZ button. Wait till finished. Now quit the program.
6: Run LG Flash tool. Select Manual mode. Click “…” for dll and select LGUPc.dll from that KDZ extracted folder.
A: Click on add button of S/W, Select “All Files” from pop up window. Now ““.KDZ”” file will be shown, select that ““.KDZ”” file, press open button, click on “OK”
B: Begin download by pressing that big “Yellow Right Arrow”. Wait until it finishes loading.
C: Connect phone when LG Flash tool says “Waiting for connection”. Make sure phone is in download mode and COM port is 41.
D: After a while it should fail the process, that’s fine. Just DC Phone, do not turn it off.
7: Exit LG Flash tool and Run it again. Select Manual Mode. This time select LGUP_H830.dll (Select as per your model e.g H850.dll for International variant) from LGUP
(Download it from 2nd post, then extract and select as dll for this step only.)
Folder. On S/W section first click on “Remove All” to erase old selected KDZ from tool and select “.DZ” (not “.KDZ”) as S/W from extracted KDZ ROM.
A: Press ok, Select on big “Yellow right arrow”. This will be loaded quickly. Connect the phone again. This time the process will get started. Wait till it gets completed.
Note: This flashing process will go up to 150% so don’t get nervous or don’t DC phone.
B: Phone will be restarted automatically. A big “2” will be shown. Wait till it gets converted into “3” and tool will say pass.
if so pull battery and start phone normally.
Or
If it is not converted into 3: Happened to me for first time.
(First Quit LG Flash tool)
Pull battery, reboot again into download mode. Run Uppercut, say “Yes” to consent, LGUP will be started automatically, Now LGUP will recognize the phone. Click on upgrade, Press “…” and browse stock KDZ ROM and select “.KDZ” stock ROM (not “.DZ”)
Select Upgrade because Refurbish won't work with uppercut.
Press Start. Download will get started. Wait until it finishes. Now Your Phone is back to life.
Ask If anything wrong happened, I will try my best to help. I used this method on my device, LG G5 T-Mobile variant AKA H830. It should work for others.
Hit Thanks, if I helped you.
If I forgot to give credit to anyone who is related with these tools, please let me know and I will be happy to name them.
Attachments. See below.
LGUP_H830.dll is for H830 variant only. You need .dll file specified for your variant.
LGUP_H850.dll --> Here
Either Download files from Attachments or Use MEGA mirror
DLL for other Variants
To get dll for other models please refer here
(This doesn't have dll for all G5 variants but should ease to some users) (Huge thanks to @codefire for awesome website)
FAQ​
I got confused on which Flash tool to use and with this megalock stuff?
Ans: Thanks, you asked, Just download LG Flash Tool attached in 2nd post, unzip, install tool, there will be a megalock.dll too, copy that to installation folder (by default that's "C:\LG\LGFlashTool") and overwrite, (written in install.instructions too inside zip).
This method isn't working for me, what shall I do?
Ans: The possible reasons, for that not working, might be,
A: You didn't installed drivers properly, try uninstalling old drivers and restarting after that.
B: LG COM PORT isn't set to COM41, here is guide for that.
C: And Most important, You are not following steps in the order in which they are written, so read carefully.
I followed the method and now my phone is totally live but now I want to root my device and have TWRP, so I can have full freedom with this phone. Can you give me any thread for that?
Ans: Nice question. There's a lots of nice threads out there here's a thread currently covering H830 only but you are welcomed to try this on H850 and let me know if this works so that I can update the thread.
Can I lock my bootloader again so I can take OTA updates?
Ans: First of all, always remember, bootloader has nothing to do with OTA. It means that if your phone is flashed with stock rom without any root or TWRP and bootloader is unlocked, you can take OTA uodates without any brick. So there is no connection between OTA and bootloader.
But if you still want to lock bootloader, here's the process. Make sure drivers are installed and minimal adb & fastboot is installed too.
Take battery out, put it back, hold vol- and connect phone to pc with data cable, it will boot into fastboot. Enter command in adb & fastboot cmd windows,
Code:
fastboot oem lock
fastboot reboot
Your phone will now try to boot into system, if stock rom is installed phone will boot without any issue else you will have to flash stock kdz again.
Where I can download stock KDZ or dll for my LG Phone (other than G5)
Ans: Most LG Phone KDZs can be found at this website.
First of All:​After Flashing let me know about your experience by answering the poll, this will help me in updating this post. Also tell me about you experience in comments.
Disclaimer:​
Before proceeding, remember I’m not responsible for anything bad happened to your device by following this or any of my guide. I’m just trying to help. So always do it on your own risk…
Don’t blame me or Any other developer.
All tools here are developed by different personalities. I’m just providing a guide on using these tool. Always say thanks to me and them. And If possible, donate them. They really deserve it.
Thanks be to:
@AutoPrime for All.
@Hyelton for post on LG Flash tool.
@bullghost for lg firmware extractor.
YouTube video not being played directly here (as well). So here's a link to YouTube for that Video
https://www.youtube.com/watch?v=dMzEcyVwQiM
Video for tutorial:
megalocks.dll file?
I'm trying your method as described above but my issue into your explanation I can't locate the megalocks.dll file to put into the lg flash tool. lil help? I'm having issues with H830 being recognized in LGUP to flash back to stock. ok found it and downloaded it and dropped it into the flash tool folder.
I got a little confused on which Flash tool to use and with the megalock part but everything worked just as described. thank you for your help!!! I'm on a Tmo G5 (H830) and had no issues.
I followed all the steps. LGflashtool got stuck on 10 per cent and failed after 63sec. Same thing on LGbridge it got stuck on 10 per cent. And LGUP wouldnt recognise it. It's on com41. The phone is stuck in download mode. No recovery. What can I do please?
x.0ni.x said:
I'm trying your method as described above but my issue into your explanation I can't locate the megalocks.dll file to put into the lg flash tool. lil help? I'm having issues with H830 being recognized in LGUP to flash back to stock. ok found it and downloaded it and dropped it into the flash tool folder.
Click to expand...
Click to collapse
Is it fixed? If not you can download flash tool from 2nd post.
isholay said:
I followed all the steps. LGflashtool got stuck on 10 per cent and failed after 63sec. Same thing on LGbridge it got stuck on 10 per cent. And LGUP wouldnt recognise it. It's on com41. The phone is stuck in download mode. No recovery. What can I do please?
Click to expand...
Click to collapse
Have you followed it as described. You have to do the process 2 times with lg flash tool and after that with lgup (only if you stuck with big 2).
Please read care-fully..
Tell me if it worked or not.
dksoni411 said:
Have you followed it as described. You have to do the process 2 times with lg flash tool and after that with lgup (only if you stuck with big 2).
Please read care-fully..
Tell me if it worked or not.
Click to expand...
Click to collapse
Finally, it has come back to life. I retried it using LGflashtool but this time I used stock Nougat rom for Vofadone UK cos my phone was simlocked to Vodafone UK. I was using MM rom for 3 Networt cos I wanted to install xposed framework which aint compatible with Nougat.
Thanks to everyone who helped to make my phone come back to life esp the created of this thread.
dksoni411 said:
Have you followed it as described. You have to do the process 2 times with lg flash tool and after that with lgup (only if you stuck with big 2).
Please read care-fully..
Tell me if it worked or not.
Click to expand...
Click to collapse
I tried your process 4 times to no avail. my computer can't recognize the device. I'm done trying. Thanks for trying to help. But I'm just gonna sell it on ebay for like $200 as a damaged device. I've tried everything and I don't need the stress of rooting anymore. this phone did it in for me and rooting devices. Anyone want a H830 for the low price of $200? i kid! BUt ya selling this thing. thanks guys.
x.0ni.x said:
I tried your process 4 times to no avail. my computer can't recognize the device. I'm done trying. Thanks for trying to help. But I'm just gonna sell it on ebay for like $200 as a damaged device. I've tried everything and I don't need the stress of rooting anymore. this phone did it in for me and rooting devices. Anyone want a H830 for the low price of $200? i kid! BUt ya selling this thing. thanks guys.
Click to expand...
Click to collapse
Good luck with that. :?
OP, I would like to make a suggestion. Could you please include screenshots to illustrate the steps. That will help people to better understand the steps and to make sure no step is missed as this is happening to lots of people lately. With that it will save you from replying to posts of missed steps and make the thread clean. Thank you once again.
isholay said:
OP, I would like to make a suggestion. Could you please include screenshots to illustrate the steps. That will help people to better understand the steps and to make sure no step is missed as this is happening to lots of people lately. With that it will save you from replying to posts of missed steps and make the thread clean. Thank you once again.
Click to expand...
Click to collapse
Sure !
x.0ni.x said:
I tried your process 4 times to no avail. my computer can't recognize the device. I'm done trying. Thanks for trying to help. But I'm just gonna sell it on ebay for like $200 as a damaged device. I've tried everything and I don't need the stress of rooting anymore. this phone did it in for me and rooting devices. Anyone want a H830 for the low price of $200? i kid! BUt ya selling this thing. thanks guys.
Click to expand...
Click to collapse
Try to use USB2.0 port,don't use USB3.0 port.I ues USB2.0 port will stay in BIG 2,when I use USB3.0 port,I can pass it.
Thank you so much for this tutorial
Now I don't have to worry about getting bricked anymore
Prabin Dhital said:
Thank you so much for this tutorial
Now I don't have to worry about getting bricked anymore
Click to expand...
Click to collapse
Welcome..
Thank you so much man! :good: I managed to brick my phone yesterday while trying to root it... and this just brought it back to life!!! You're my new hero... :victory:
I'm now on H83020a, looking to root. If I fail and brick it again, can I just bring it back to life with this method again?
Btw, do you have any tips on best method to root H83020a?
d3th.m0nk3y said:
Thank you so much man! :good: I managed to brick my phone yesterday while trying to root it... and this just brought it back to life!!! You're my new hero... :victory:
I'm now on H83020a, looking to root. If I fail and brick it again, can I just bring it back to life with this method again?
Btw, do you have any tips on best method to root H83020a?
Click to expand...
Click to collapse
Flash Fulmics 2.0 rom
d3th.m0nk3y said:
Thank you so much man! :good: I managed to brick my phone yesterday while trying to root it... and this just brought it back to life!!! You're my new hero... :victory:
I'm now on H83020a, looking to root. If I fail and brick it again, can I just bring it back to life with this method again?
Btw, do you have any tips on best method to root H83020a?
Click to expand...
Click to collapse
You are welcome.
Here is the thread I wrote to root h830 on v20a. You can try
https://forum.xda-developers.com/tmobile-lg-g5/how-to/guide-root-twrp-lg-g5-using-t3580264
I'm still working on it so write your experience and suggestion for the thread after trying...
And off course you can bring your phone back to life for everytime, as long as you can access that download mode.

Categories

Resources