(notes)backup official firmware - Upgrading, Modifying and Unlocking

hi i opened this thread for explain how to backup your official firmware.
first downgrade your phone so that kies will detect an upgrade for you.
Now read on to see how to save the
firmware files during kies upgrade process.
On your pc, check the option
"Show hidden files"
Now connect your phone to pc via kies to begin the firmware upgrade.
Kies will begin to download the
firmware files...
The files will be saved in tmp files called "tmpA4CE.tmp" or other names
you can find it easily.
In Windows 7, this
tmp file is located at,
C:\Users\ * \AppData
\Local\Temp or type temp in run command.
(* is the pc user
session name, e.g. C:
\Users\chenna
\AppData\Local
\Temp)
When download iscomplete, kies
decompresses this tmp file into a zip folder and begins the firmware upgrading process.
The folder has same name as the tmp file but now with an extention of zipfolder.
When kies begins the upgrade process
starting from 1% until
it reaches 100%, quickly copy the "zipfolder" to your desktop.
You have about 2 to 3 minutes to do this.
Kies will delete the folder once upgrade is 100% (completed).
The "zipfolder" contains all the firmware files kies has used to upgrade
your phone.
Now you have a backup of official firmware from kies.
This is also useful in case kies fails to
complete the upgrade process.
Just use the saved files and manually flash your phone using odin or multiloader.
IF YOU LIKE THIS POST PLEASE PRESS THANKS

Related

[Q] How do I restore Samsung official firmware?

Hello,
I have a rooted Galaxy Gio (GT-S5660) with CWM and CM10.1 (from
Maclaw). I now need to restore it to factory firmware,
but am running into a brick wall no matter what I try.
I have downloaded S5660XXKTK_S5660COVKS1_COV.zip and tried with
Odin but that fails (don't remember the error message). And
anyway, it seems really unnecessary to boot into Windows to do
this, one should be able to do it all from Linux.
Is there any way to restore factory firmware using adb/fastboot?
adb connect to the phone etc., but fastboot doesn't work, it just
gets stuck in the "< waiting for device >" state.
(Yes, of course I run the adb/fastboot commands as root.)
I haven't found any tutorials/howtos on how to do this in Linux,
can anyone write one or point me in the right direction?
Or, if Odin is the only way, what files do I need to download to
make it all work? Obviously S5660XXKTK_S5660COVKS1_COV.zip isn't
enough.
I have tried the instructions found at android.gs, androidaddition.com
and mobotechie.com (seems I'm not allowed to post links...) but
nothing works.
Thanks,
Have u tried with .ops file in odin ?
U extract S5660XXKTK_S5660COVKS1_COV.zip , right ?
Sent from my GT-S5660 using Tapatalk 2
Gyovany96 said:
Have u tried with .ops file in odin ?
U extract S5660XXKTK_S5660COVKS1_COV.zip , right ?
Click to expand...
Click to collapse
No I did not extract the S5660XXKTK_S5660COVKS1_COV.zip , I've assumed it's supposed to be used as-is, just like custom ROMs.
But there is no .ops file in the archive:
Code:
$ unzip -t S5660XXKTK_S5660COVKS1_COV.zip
Archive: S5660XXKTK_S5660COVKS1_COV.zip
testing: S5660XXKTK_S5660XXKT6_S5660COVKS1_HOME.tar.md5 OK
testing: SS_DL.dll OK
No errors detected in compressed data of S5660XXKTK_S5660COVKS1_COV.zip.
And no .ops file in the .tar.md5 file within the archive either:
Code:
$ unzip -xp S5660XXKTK_S5660COVKS1_COV.zip S5660XXKTK_S5660XXKT6_S5660COVKS1_HOME.tar.md5 | tar tvf -
-rw-rw-rw- a.oldak/0 18784256 2012-03-04 09:18 amss
-rw-rw-rw- a.oldak/0 459132 2012-03-21 09:40 arm11boot
-rw-rw-rw- a.oldak/0 6451200 2012-03-21 09:40 boot.img
-rw-rw-rw- a.oldak/0 19116032 2011-10-14 15:08 csc.rfs
-rw-rw-rw- a.oldak/0 786432 2012-03-21 10:11 mibib
-rw-rw-rw- a.oldak/0 566888 2012-03-21 10:11 oemsbl
-rw-rw-rw- a.oldak/0 368640 2012-03-21 10:11 qcsbl
-rw-rw-rw- a.oldak/0 6864896 2012-03-21 09:40 recovery.img
-rw-rw-rw- a.oldak/0 212430848 2012-03-21 09:40 system.rfs
Now what?
http://www.4shared.com/rar/ttIilfrh/Odinv442GIO_v10ops.html
Put .tar.md5 file in one package and flash. Don't forget .ops file
Sent from my GT-S5660 using Tapatalk 2
Gyovany96 said:
URL removed since I'm a new user and as such not permitted to post links...
Put .tar.md5 file in one package and flash. Don't forget .ops file
Click to expand...
Click to collapse
So, I'm supposed to extract the .tar.md5 file from the .zip file, separately download a .ops file from some completely other site (riddled with ads and popups and requiring registration, btw), and create a new .zip file containing the .tar.md5 file and the .ops file? Is that correct, or do I need to bundle more files into the new .zip file?
And in Odin (version 3.07), should I add the file as a PIT, Bootloader, PDA, PHONE, or CSC?
1. Put phone in download mode
2. Use odin 4.42 (is in archive I gave u)
3. Click on ops and navigate to .ops file ( also it's in archive )
4. Check one package file , then click on "one package file" and select .TAR.MD5 file
5. Fash !!
P.S. I am on mobile and I'm not sure about buttons NAME...I hope u can do it
EDIT : Here another link without registration http://hotfile.com/dl/140235732/ec749d2/?lang=ro
Sent from my GT-S5660 using Tapatalk 2
Gyovany96 said:
1. Put phone in download mode
2. Use odin 4.42 (is in archive I gave u)
3. Click on ops and navigate to .ops file ( also it's in archive )
4. Check one package file , then click on "one package file" and select .TAR.MD5 file
5. Fash !!
P.S. I am on mobile and I'm not sure about buttons NAME...I hope u can do it
EDIT : Here another link without registration (removed as I'm not allowed to post links...)
Click to expand...
Click to collapse
Well, that almost worked. I put the phone in download mode, connect it to a USB port, start Odin, the phone is detected as COM8, I add the .ops file, check "One Package" box, and add the .tar.md5 file. Odin has up until this point replied with this in the Message box:
Code:
<1> Added!!!
<1> Detected!!!
Check MD5 Filename : S5660XXKTK_S5660XXKT6_S5660COVKS1_HOME.tar
Open File Name : S5660XXKTK_S5660XXKT6_S5660COVKS1_HOME.tar
Check MD5 ...
Tail MD5 : 7BCD76F2AA8BB985AC91E3DE94CFA784
Image MD5 : 7BCD76F2AA8BB985AC91E3DE94CFA784
Check MD5 ... ok
The I click the Start button in Odin. The Message box is cleared, and this appears:
Code:
<5> StartThread Detected : 0
<6> StartThread Detected : 0
<7> StartThread Detected : 0
<8> StartThread Detected : 0
And after a few more seconds, this line is added:
Code:
<1> --- cannot open the usb serial port. code: 32
It doesn't matter whether I start Odin as Administrator or a regular user, the phone is detected but the "error 32" appears when trying to flash. The phone is the only thing connected to any USB port.
Any ideas?
1.Usb debugging was checked ?
2.You have samsung drivers installed ?
Sent from my GT-S5660 using Tapatalk 2
Gyovany96 said:
1.Usb debugging was checked ?
2.You have samsung drivers installed ?
Click to expand...
Click to collapse
1. USB debugging was not checked. Is it supposed to be?
2. Kies was installed, I guess perhaps drivers come along with that? I just deinstalled Kies, and now Odin doesn't detect the phone any more. Should I install just some drivers and not Kies? If yes, which drivers, where do I find them?
Kies will install drivers automatically.
Hmm....I had this problem with an I9000 and solved it with a ROM than contains 3-files package.
Search a ROM with 3 files
EDIT: If your phone can still boot check Usb debugging and then try flash again
Sent from my GT-S5660 using Tapatalk 2
Gyovany96 said:
Kies will install drivers automatically.
Hmm....I had this problem with an I9000 and solved it with a ROM than contains 3-files package.
Search a ROM with 3 files
EDIT: If your phone can still boot check Usb debugging and then try flash again
Click to expand...
Click to collapse
The phone can still boot, and USB debugging is activated.
To solve the error code 32 problem, people on forums suggest killing Kies using the Task Manager, and trying out different USB ports and making sure I use the USb cable that came with the phone. Well, I have tried reinstalling Kies, rebooting, deinstalling Kies but keeping the USB drivers, different USB cables and different USB ports, but no luck... nothing works. The phone is not detected by Odin any more.
It is detected by adb under Linux, though, so USB is still working.
When searching for a 3 file ROM I found the pages
www modaco com /topic/361399-latest-odin-309-odin-185-odin-183-all-versions-samsung-rom-flashing-tools/
and
www modaco com /topic/361286-18072013-latest-samsung-usb-drivers-for-mobile-phones-15270-win-87xp-adb-fastboot/
so I downloaded the latest Samsung USB driver, and made sure I was using an Odin version compatible with my phone.
And still, now after reinstalling Kies, Odin does not even detect the phone any more. Windows chimes when the phone is plugged in, but it does not appear in Odin, regardless of whether I start Odin before or after plugging in the phone, and regardless of whether I run Odin as administrator or not.
Seriously, is there no way to do all this using adb and fastboot under Linux? I get more and more homicidal when I have to spend time using Windows.
I sent you PM
EDIT : http://hotfile.com/dl/106492222/cc53f0f/S5660_XXKB9_OXXKB8.rar.html download this
http://droidangel.blogspot.ro/2011/05/procedure-how-to-flash-updateupgrade.html this is tutorial
Gyovany96 said:
I sent you PM
EDIT : (URL removed as I don't have permission to post them... moronic forum rules...) download this
(URL removed as I don't have permission to post them... moronic forum rules...) this is tutorial
Click to expand...
Click to collapse
Well, I finally managed to flas in Samsung stock firmware.
The instructions on the page
nguyenkieuhung1984 blogspot se /2012/01/how-to-upgrade-samsung-galaxy-gio-s5660_13.html
comes closest to describing what I did, except I used S5660XXKTK_S5660COVKS1_COV.zip and GIO_v1.0.ops .
I don't really know what I did to resolve the USB connections problems, but hey, when using Windows it's all trial-and-error, right?
First, install, deinstall and reinstall Kies a couple of times, and inbetween installs try the Odin procedure described in the nguyenkieuhung1984 blog mentioned above. And download the very latest Samsung USB drivers (I used 1.5.27.0) and install that. Repeat these steps until you feel like vomiting all over your keyboard. Oh, and install Odin 4.42 too while you are at it. And keep SS_DL.dll and GIO_v1.0.ops in the same folder as the Odin executable file. I don't know if it matters, but getting Windows to work is 80% magic, 15% luck and 5% skills, so why not?
Then reboot to Linux, read mails, surf, code, whatever is needed to regain sanity.
Reboot into Windows, install Kies again, including the bundled USB driver. After Kies has installed, verify that the Samsung USB driver version is still 1.5.27.0 and not whatever version came with Kies (I think Kies came with 1.5.23.0 ?). Anyways, 1.5.27.0 is what's on my system now, along with Kies 2.5.3.13043_14.
Start Kies and close it. Do NOT go into Task Manager to kill off any Kies processes; at least I didn't. Other tutorials tell you to, at least if you run into the error code 32 problem. Well, I didn't have that problem on my 30th attempt (on attempts 10-29 I did, though...).
Follow the steps on the nguyenkieuhung1984 blog mentioned earlier in this post, replacing filenames if needed (like I did, I mentioned that at the start of this post...).
The phone might now enter a reboot loop (mine did). Press and hold the Power and Home buttons to reboot the phone into the bootloader(?), and there you wipe settings and caches (two different wipes if I remember correctly).
The phone should now boot to stock firmware. Enjoy Android 2.3.6 or whatever Samsung ROM you selected.
It's recomended to "wipe data/factory reset" in recovery mode after you flash a stock ROM. But, enjoy ROM finally
Sent from my GT-S5660 using Tapatalk 2

[HOW TO] Extract Rom.zip From RUU

Extracting ROM files from HTC RUU
Official HTC ROM updates are released as RUU (ROM Update Utility), which you run on your (Windows) PC to get the target device updated automatically.
Some of the big brains in the Android community release RUUs re-packaged into signed update files,
which in turn allow for whatever ROM customization you can imagine.
In this how to I will explain how to extract ROM files from a RUU image,
which you can then customize and use to flash your device without the fear of a new bootloader possibly making your device unrootable.
Requirements :
Windows PC,
Microsoft Process Monitor,
File Archiver capable of extracting ZIP files(eg, 7ZIP),
Official HTC RUU for your Android device.
The process of extracting ROM files from a RUU is really straightforward.
The idea behind it is that the self-contained update utility first needs to unpack the update payload into a temporary folder before pushing it onto the device.
This is when we grab the ROM file...
1. download the official RUU
2. start Process Monitor.
3. press CTRL+L
4. change "Architecture" to "Process Name"
5. leave the "is" field as it is
6. in the empty field copy and paste the name of your
RUU file (eg, RUU_Ace_Sense30_S_HTC_WWE_3.12.405.1_Radio_12.65.60.29_26.14.04.28_M_release_225512_signed.exe)
7. click "Add"
8. change "Process Name" to "Path"
9. change "is" to "Contains"
10. in the blank field type "rom.zip" (without quotes)
11. click add
Click "OK" to set the filter and then run the RUU file.
Once the utility starts switch back to Process Monitor and look for an entry in the "Path" column that ends with "\rom.zip".
Right click on that line and select "Jump to..."
this will open a Windows Explorer window in the folder which contains the zipped ROM files
Copy the "rom.zip" file to some other folder, outside of the temp RUU folder tree (eg, desktop)
Once copied, close Process Monitor and the RUU utility.
The copied "rom.zip" file contains the following files:
android-info.txt - list of CIDs this RUU will flash to,
boot.img - root file system image,
hboot (followed by a version string) - boot-loader update,
radio.img - radio driver update,
recovery.img - recovery partition image,
splash1_Hero_320x480.nb0 - boot loader splash image,
system_rel.img - system partition image,
userdata.img - data partition image.
You can now, among many other things, root the ROM
and then flash the updated boot.img and all the other image files on to your device using Recovery​
it doesnt work... the process monitor colum is all blank after running RUU... there are no processes listed
munnibhai said:
it doesnt work... the process monitor colum is all blank after running RUU... there are no processes listed
Click to expand...
Click to collapse
you mst be doing something wrong i double checked the method and it still works fine for me..
make sure your environment is set up correctly and run everything as administrator or disadle uac in windows..
thanks for the reply, let me check it again...
i will post back to u
rom.zip corrupted
I followed the directions and like another post in here procmon shows a blank screen. I went to task manager and opened processes and saw when it ran then clicked open file location and found it. I did this twice and both zips are corrupt. (used winzip)
error [D:\android apps\EVO root\EVO\rom.zip]: start of central directory not found; Zip file corrupt.
Possible cause: file transfer error
when I close the RUU all the files in that folder disappear so you have to leave the RUU running while you copy the zip file or it's gone.
At least that's what I saw.
update to last post
I found a zip repair tool and was able to repair and extract the 1.10.653.2 RUU rom capture. I will have to try to run it later. If anyone gets corrupted zip error, Zip Repair pro will repair it.
To get the rom zip without any errors just run the ruu.exe file, when the box with a picture of a phone pops up, click start on pc, type in "run" and click on run then in that box that pops up, type in %temp% and click ok. Another window pops up then just scroll down to the most recent folder and rom.zip will be in there, if not it will be in the next folder.
Hi,
when I try to open the rom.zip I get an error message, it just said it cannot open with 7zip and with windows it says its invalid.
I tried downloading the RUU multiple times but still the same error. I rune the RUU as administrator.
Tried copying it over to different locations and then open it.
RUU_ENRC2B_U_JB_45_O2_UK_1.14.206.13_Radio_3.1204.167.31_release_289474_signed
HTC ONE X+
Thank you
Update:
I used Zip Repair Pro.. however there is no boot.img inside the repaired zip -_-
For those which have problem with making Process Monitor detect RUU temp folder, make sure You add whole file name of RUU including .exe at the end.
Jmcclue's steps, work perfectly, Thank you post #7
htc RUU Rom
Inside 4ndroid said:
Extracting ROM files from HTC RUU
Official HTC ROM updates are released as RUU (ROM Update Utility), which you run on your (Windows) PC to get the target device updated automatically.
Some of the big brains in the Android community release RUUs re-packaged into signed update files,
which in turn allow for whatever ROM customization you can imagine.
In this how to I will explain how to extract ROM files from a RUU image,
which you can then customize and use to flash your device without the fear of a new bootloader possibly making your device unrootable.
Requirements :
Windows PC,
Microsoft Process Monitor,
File Archiver capable of extracting ZIP files(eg, 7ZIP),
Official HTC RUU for your Android device.
The process of extracting ROM files from a RUU is really straightforward.
The idea behind it is that the self-contained update utility first needs to unpack the update payload into a temporary folder before pushing it onto the device.
This is when we grab the ROM file...
1. download the official RUU
2. start Process Monitor.
3. press CTRL+L
4. change "Architecture" to "Process Name"
5. leave the "is" field as it is
6. in the empty field copy and paste the name of your
RUU file (eg, RUU_Ace_Sense30_S_HTC_WWE_3.12.405.1_Radio_12.65.60.29_26.14.04.28_M_release_225512_signed.exe)
7. click "Add"
8. change "Process Name" to "Path"
9. change "is" to "Contains"
10. in the blank field type "rom.zip" (without quotes)
11. click add
Click "OK" to set the filter and then run the RUU file.
Once the utility starts switch back to Process Monitor and look for an entry in the "Path" column that ends with "\rom.zip".
Right click on that line and select "Jump to..."
this will open a Windows Explorer window in the folder which contains the zipped ROM files
Copy the "rom.zip" file to some other folder, outside of the temp RUU folder tree (eg, desktop)
Once copied, close Process Monitor and the RUU utility.
The copied "rom.zip" file contains the following files:
android-info.txt - list of CIDs this RUU will flash to,
boot.img - root file system image,
hboot (followed by a version string) - boot-loader update,
radio.img - radio driver update,
recovery.img - recovery partition image,
splash1_Hero_320x480.nb0 - boot loader splash image,
system_rel.img - system partition image,
userdata.img - data partition image.
You can now, among many other things, root the ROM
and then flash the updated boot.img and all the other image files on to your device using Recovery​
Click to expand...
Click to collapse
this is good working 100% thank you :good:
i_4_u89 said:
this is good working 100% thank you :good:
Click to expand...
Click to collapse
no problem and please instead of saying thanks please remember to hit the thanks button on threads first post..
works great, to bad you cant open the zip file
jpwhre said:
works great, to bad you cant open the zip file
Click to expand...
Click to collapse
You can open the zip. Go back a page n try the way i said.
jmcclue said:
You can open the zip. Go back a page n try the way i said.
Click to expand...
Click to collapse
note path is desktop (last post showed from temp folder) and i still get same results. did some searching and aperantly htc now signs their zip files and they can't be opened anymore. having usb issues that causes fastboot force close errors and need to be able to flash boot.img thru flashify app to return it to stock. ran the htcguru reset rom that uses aroma installer to return to stock that lets me take ota's but i get qualcom location force close and other custom roms give me issues forcing me to reset phone to stock every few days with guru installer. flashing recovery in fastboot is a chore as well. I have s-off and can keep it, but doing fastboot oem lock wont relock the bootloader, even though it shows success in cmd line. i can cid and super cid with fastboot.
it leaves me at a point where i really need to pull everything out of the rom.zip file and it wont open.
pic 1, 7zip wont open archive on desktop
pic 2, how i get recovery to flash
pic 3, results from running RUU
i have to reboot device, set comand to reboot bootloader, set command to flash recovery all faster than phone will do all commands to get it to flash, and RUU doesnt work that fast. i know im on sprint with htc one m7, but google search "extract htc zip" "extract rom.zip" both lead to this thread as top result. no other searches will tell me how to open the archive, except one that resulted in "htc signed zips can no longer be opened"
you're more than welcome to give it a go
http://forum.xda-developers.com/showthread.php?t=2795856 Sprint_HTC_One_m7wls_5.05.651.2_RUU.exe
Did HTC change the way they create the exe? I don't find it, the biggest file is data1.cab file that I can't extract.
I'm trying to extract the stock rom for an ATT HTC One Mini (m4) because RUU keeps crashing on me and won't install. I am also rooted with S-off.
If anybody can help me get the stock m4 rom so I can go back to stock, I would really appreciate it.
SyPete said:
Did HTC change the way they create the exe? I don't find it, the biggest file is data1.cab file that I can't extract.
I'm trying to extract the stock rom for an ATT HTC One Mini (m4) because RUU keeps crashing on me and won't install. I am also rooted with S-off.
If anybody can help me get the stock m4 rom so I can go back to stock, I would really appreciate it.
Click to expand...
Click to collapse
No they didn't change it. Some ruu's use a different format requiring the use of a tool called unruu instead of trying to capture the zip file when using the exe (I just learned this today). I've gone ahead and used unruu and the resulting zips have been put in a single tar file. you can download it from here for about 30 days after which ill have to delete the file. also i dont know which zip has what in it.
hi
master how to open Zip firmware !!?
i want to open zip firmware (PM60IMG.zip Desire 400)with 7zip ! but shows below error :
"can not open file PM60IMG.zip az archive "
how to pass this encryption ?
gandolf007 said:
hi
master how to open Zip firmware !!?
i want to open zip firmware (PM60IMG.zip Desire 400)with 7zip ! but shows below error :
"can not open file PM60IMG.zip az archive "
how to pass this encryption ?
Click to expand...
Click to collapse
https://github.com/kmdm/ruuveal/tree/f4936338f19841c75edafbe7e622242105cb39aa

[Q] how to extract rom file from kies

Hi all,
just having some problems flashing my tab 10.1 3 p5220.
Kies is refusing to do it as I suspect it is because the rom in it is
currently a german one.
Now, how do I intercept the rom file after kies has downloaded it but
before it attempts to install it and fails?
I seem to remember being able to do this on the htc and assume
we can do the same with the samsung. This way I hope I can I
reflash it via odin.
Many thanks in advance,
Andrew
Just download a firmware from sammobile and flash through odin
BennyCat said:
Now, how do I intercept the rom file after kies has downloaded it but
before it attempts to install it and fails?
Click to expand...
Click to collapse
Not sure if you've managed it now?
Anyway here is how you do it, also may be useful for others too, I've done this in the past, although I was doing an emergency recovery instead of an upgrade, this works either way.
I take absolutely no credit for this:
Here is a guide to save the firmware during your kies update,so u can save that firmware for future use .i just copy paste this from some where else
1. On your pc, windows explorer, check the option "Show hidden files, folders, and drivers".
2. Now connect your phone to pc via kies to begin the firmware upgrade.
3. Kies will begin to download the firmware files...
a. The files will be saved under a tmp file called "tmp****.tmp"
(NB: **** can be any letters or numbers, e.g. In my two times of upgrade via kies,
first timethe tmp files was "tmpA4CE.tmp", and on the second it was "tmpD900.tmp"
b. In Windows 7, this tmp file is located at, C:\Users\*\AppData\Local\Temp
(NB: * is the pc user session name, e.g. C:\Users\Spacks\AppData\Local\Temp)
4. When download is complete, kies decompresses this tmp file into a folder called
"tmp****.tmp.zipfolder" and begins the firmware upgrading process.
a. The folder has same name as the tmp file but now with an extention of .zipfolder.
(So scroll through the folders in the same directory to locate it).
b. When kies begins the upgrade process starting from 1% until it reaches 100%,
quickly copy the "tmp****.tmp.zipfolder" to your desktop.
You have about 2 to 3 minutes to do this. Kies will delete the folder once upgrade is 100% (completed).
5. The "tmp****.tmp.zipfolder" contains all the firmware files kies has used to upgrade your phone.
Now you have a backup of official firmware from kies. This is also useful in case kies fails to complete the upgrade process.
Click to expand...
Click to collapse
:good: Credit to & quoted guide by blackperl @ androidforums.com :good:

Samsung Galaxy Tab 3 7.0 SM-T210 problem

I recently found my old tablet and it had kingoroot installed and then I flashed stock rom to my tablet but now it randomly restarts and every time i try to setup it i got error "Unfortunately, the process com.android.systemui has stopped" and "settings has stopped"
Here is the tutorial I followed:
Code:
The following instructions are for Windows only. Please don't use a virtual machine as these can cause problems communicating with the device. There is an alternative method for Linux or macOS. Just tell me if you aren't on Windows, I can easily change the instructions. Please make sure you have Windows set to display all file extensions. This can really help for debugging purposes.
First we need to download the tool that downloads the stock firmware. It's called SamFirm and it downloads it using Samsung's servers. You can download the latest version [here](http://forum.xda-developers.com/attachment.php?attachmentid=3803841&d=1467715462). Please also make sure you have the [Microsoft Visual C++ 2008](https://download.microsoft.com/download/1/1/1/1116b75a-9ec3-481a-a3c8-1777b5381140/vcredist_x86.exe) and [Microsoft Visual C++ 2010](https://download.microsoft.com/download/5/B/C/5BC5DBB3-652D-4DCE-B14A-475AB85EEF6E/vcredist_x86.exe) x86 Redistributable packages installed. Now to download the tool that flashes to the devices different partitions. On most devices you use a tool called fastboot, but Samsung devices aren't like most devices (excluding the Galaxy Nexus). This tool is called Odin, it's Windows only and leaked from Samsung so you need to get it from a trusted source. You can download the latest version [here](https://build.nethunter.com/samsung-tools/Odin_3.12.3.zip). Extract the "Odin_3.12.3.zip" file. You should now have a folder called "Odin_3.12.3". Treat this as your working directory and download all other files to this folder. While you're here, extract the contents of "SamFirm_v0.3.6.zip" into this folder.
Now to download the stock firmware. Open "SamFirm.exe" and make sure "Auto" is checked and "Manual" and "Binary Nature" isn't checked. In "Model" put `SM-T210` and in "Region" put `BTU`. Click "Check Update" and wait for it to find the firmware on the server. Now check "Check CRC32" and "Decrypt automatically". Then click "Download" and save it. Let it finish downloading, checking, and decrypting. Once it finishes you can now close SamFirm. Extract the zip file it gave you. You should now have a single file ending in `.tar.md5` (you may also have `.dll` file, ignore it). This tar.md5 file is your firmware. Do not modify it. If you have more than one .tar.md5 file, tell me.
Now shutdown the device and then hold the Volume Down, Home/Bixby, and Power buttons. This should put the device into download mode. Accept any warnings then plug the device in. Open "Odin.exe" from the "Odin_3.12.3" folder. In the log, it should say `Added!` and have a blue COM thing near the top, meaning it detected your device. If it didn't detect it, then you may need to configure drivers (you can ask me for the drivers if you need them). Click the "Option" tab and make sure "F. Reset Time" and "Auto Reboot" is enabled. Also check the checkbox next to the "AP" button and then click the button. Select the tar.md5 file. Now click "Start" in Odin.
It should now reboot and go to the boot animation. If it doesn't boot in 15 minutes, shutdown the device. Then hold the Volume Up, Home/Bixby, and Power buttons. Then use the keys to select "Factory reset". Please note this will wipe all user data. Once it finishes you can select "Reboot" and now it should boot correctly.
I have been battling with this problem so long I only wanted to root my tablet to have some fun with root required apps
Any help with the problem? I only need to root the device or get it to work with stock rom

lg g7 stuck in firmware update page

hello, i was upgrading from lgup but the common file is not recognized (check new dll..)....
2. please how can i make recognizable common file? i copied in model folder under program files (x86)... but after failed the common folder disappear
please help
Please state clearly what your problem is.
1. Is the phone stuck on the firmware update page and you do not know how to get out and reboot? Answer: disconnect the phone from the pc and hold vol-down and power up to when the phone reboots.
2. Are you asking how to install the correct dll for lgup so that it will recognize the lg g7? Answer: uninstall completely lgup and reinstall it; download this dll https://drive.google.com/open?id=1U2FjURLlPxsYHyh3dDHyNvWMYRgjs4Ck and put it in the directory C:\Program Files (x86)\LG Electronics\LGUP\model\common (create the directory if you don't have it); connect the phone (you need to have installed the lg drivers last version 4.2.0); run the lgup that should recognize your phone.

Categories

Resources