Related
How to install clockworkmod recovery:
Edit: Fixed install zip from sdcard bug
Method 1: Needs root
The first method is preferable for those who have root access on their Micromax A90. Those who do not have a rooted device should follow Method 2 instead.
1. Download cwmr_v5.5.0.4 (fixed).zip and unzip/extract it. After extracting move both the files to the root directory of your SD card.
2. Install mu7577.apk and run it. After that give the program root permissions if asked and tap Recovery Update.
3. Select recovery.img from SD card then tap the ok button.
4. Now you can reboot to recovery.
Congrats!
Method 2: SP Flash Tool method, root not required
1. Download MTK6575 Drivers.zip and unzip/extract on your Windows PC, just run InstallDriver.exe to install drivers.
2. Download cwmr_v5.5.0.4 (fixed) + scatter.zip and SP_Flash_Tool_v3.1220.02_FOR_S101A.zip , unzip/extract them.
3. Now open extracted SP Flash Tool folder and run Flash_tool.exe
4. Click on "Scatter-loading" button which is on the right side below Downloading Agent. A new window will open. Browse to the extracted cwmr_v5.5.0.4 (fixed) + scatter folder and select MT6575_Android_scatter_emmc.txt file.
5. Flash tool will populate the Map file on the application window. You will see multiple entries. Uncheck all entries except for RECOVERY.
6. Now click on "Download". Warning message will occur, but ignore that and click Yes.
7. You will see in the status bar below "Searching", now connect your phone (without battery inserted) via the USB cable.
8. Wait for the process to finish and then you will get a window showing green circle.
Congrats You have flashed CWMR!
Note: If you get any error in SP Flash Tool, then recheck your MTK drivers installation or manually install them through device manager.
Booting into CWM recovery is the same as in the stock recovery. Switch on the phone with "Volume Up" and "Power" button Pressed. The Phone will boot into CWM!
I have also attached the the Stock Recovery.zip.
dear brother are you tested it ! please post some screenshot here with A90.
BHARDIK said:
dear brother are you tested it ! please post some screenshot here with A90.
Click to expand...
Click to collapse
Yes bro I have tested it!
I will post the screenshots soon
please also post here STOCK ROM full firmware , because if we failed then we need to restore i try custom recovery maybe 10 times always failed then need to go service center for restore. if you add stock firmware then we no need to worry about any experiment.
Presently I also don't have the stock rom or stock dump of micromax a90, I am currently running a self modded rom.
Follow this guide http://forum.xda-developers.com/showthread.php?t=1981107 to make a dump/backup of rom
Sent from my A90 using xda app-developers app
i have ROMDUMP back up , take backup using terminal emulator type onandroid and he done , but no boot and recovery image on this back up.
but i dont know how to restore it using sp flash tool ?
BHARDIK said:
i have ROMDUMP back up , take backup using terminal emulator type onandroid and he done , but no boot and recovery image on this back up.
but i dont know how to restore it using sp flash tool ?
Click to expand...
Click to collapse
bro follow my guide to dump the rom, by that guide you will get the complete dump i.e all flash files such as boot.img, recovery.img, system.img, mbr.img, logo.img, etc and there i have also written the complete procedure to restore the dump using sp flash tool
Sent from my A90 using xda app-developers app
THANX
The guide is great....CMW installed in minutes...thanx a lot...waiting for custom rom
airjordanthehacker said:
bro follow my guide to dump the rom, by that guide you will get the complete dump i.e all flash files such as boot.img, recovery.img, system.img, mbr.img, logo.img, etc and there i have also written the complete procedure to restore the dump using sp flash tool
Sent from my A90 using xda app-developers app
Click to expand...
Click to collapse
in your method when i try to add script in GS_Script.apk select file but no any file saw there
and second question is this method is working for Micromax A90s MTK6577 devices also ?
BHARDIK said:
in your method when i try to add script in GS_Script.apk select file but no any file saw there
and second question is this method is working for Micromax A90s MTK6577 devices also ?
Click to expand...
Click to collapse
extract BackupTool_*.zip to the root of your sd card after that only you will be able to see the script in load script option.
and i have not tested this script on mtk6577 but it should work for it.
Sent from my A90 using xda app-developers app
hey guys here is micromax FTP server site here u find all micromax android mobile stock ROM all the version of realesed + original flasher and imei writing tolls for MTK 65166 TO MTK6577 ! is it good for you guys ?
***
user id = mxlive [ in small latter ]
password = [email protected] [ M capital its not (O) its (0) zero ]
best way to use this !
you need Firefox browser for this, in Google chrome its not working !
just copy past this given id and password if you not understand !
and then use Internet Download Manager for downloading anything ! for better downloading speed !
Is there any Jellybean custom ROM for the A90?
No Abhi Still no sign of any ! Custom ROM ! for A90 and A90s both just have CWM !!!!
BHARDIK said:
hey guys here is micromax FTP server site here u find all micromax android mobile stock ROM all the version of realesed + original flasher and imei writing tolls for MTK 65166 TO MTK6577 ! is it good for you guys ?
***
user id = mxlive [ in small latter ]
password = [email protected] [ M capital its not (O) its (0) zero ]
best way to use this !
you need Firefox browser for this, in Google chrome its not working !
just copy past this given id and password if you not understand !
and then use Internet Download Manager for downloading anything ! for better downloading speed !
Click to expand...
Click to collapse
thanks!
BHARDIK said:
No Abhi Still no sign of any ! Custom ROM ! for A90 and A90s both just have CWM !!!!
Click to expand...
Click to collapse
Has anyone tried flashing ROMs of similar devices like Karbonn A18?
Sent from my Galaxy Nexus using Tapatalk 2
provide URL please
Please provide URL Please?
Micromax Stock Rom & Flasher site FTP or otherwise please!
Can anyone post or tell me where I can get Micromax Stock Rom & Flasher from their site or otherwise please? I'd like to reflash to stock state instead of just removing CWM.
airjordanthehacker said:
extract BackupTool_*.zip to the root of your sd card after that only you will be able to see the script in load script option.
and i have not tested this script on mtk6577 but it should work for it.
Sent from my A90 using xda app-developers app
Click to expand...
Click to collapse
Hi, it woks with NGM Legend ? (mtk 6575 phone)
Still no sign of any custom ROM?
Anyway, which device has a similar config as the A90. I'll try flashing it's custom ROM.
Custom Rom ICS 4.0.6
Dear All,
See my thread here for Custom Rom
My mobile is - NXG Phablet.
Its specifications match to A90.
Check - ics 4.0.6 custom rom in my thread and download.
but use your A90 ics 'boot.img'.. means, replace your 'boot.img' in the downloaded file and rezip and flash through CWM recovery.
after boot it will come in Russian language. (because it is for Star N8000 - russian forum). so change language to english in settings. also , default launcher is SPB shell - Russian version. so install another launcher and use.
Rom is very good.
check here in CUSTOM ICS area.
http://forum.xda-developers.com/showthread.php?p=32932373
Happy Testing.
Ace 2 Gt-i8160L LATIN. How to install CM?
When I install CM, don't wok sim-card and not IMEI.
Restore IMEI don't helped.
This is modem or hw problems, i think.
Sorry my english is bad.
...
Replace tee folder in rom zip /system/lib with the one from stock rom
Sent from my GT-I8160 using Tapatalk
1) backup tee folder
2) On build.prop change all GT-I8160L to GT-I8160 (without L)
3) all wipes factory/cache/dalvik
3) Install CM_Xversion
4) Whith roo explorer replace tee folder
Enjoy.
2) also can delete assert :/
4) you can just replace in zip before flashing (just sayin)
Sent from my GT-I8160 using Tapatalk
When to alter ROM
teddytsen said:
2) also can delete assert :/
4) you can just replace in zip before flashing (just sayin)
Sent from my GT-I8160 using Tapatalk
Click to expand...
Click to collapse
Am located in New Zealand, and hence using model i8160L, running stock JB ROM
Am trying to modify / install Maclaw CM KK ROM -- but am having problems
-- it "reads" the ROM and "immediately" (afaik) but aborts installation
-- NO ERROR MESSAGES come up for any indication as to why it's aborting
Am trying to do the following -- appreciate any feedback to correct procedure if I'm making eny errors
(i) omitting any and all references to L in 8160L string -- should I restrict it to any particular lines? -- using Build.Prop Editor
-- the Settings/About Device shows it as an 8160, rather than an 8160L after the Build.Prop changes, but the boot screen still shows it as the 8160L -- but at least I don't get the error message about trying to install ROM on wrong device
(ii) before attempting installation, downloading the latest ROM, unzipping the ROM using 7zip, deleting "tee" folder
-- and pasting tee folder from the stock JB ROM installed on my phone
(iii) re-zipping the ROM using 7zip -- I notice I get a different MD5 to that llsted on the download page
(iv) attempting to flash the modified ROM in Recovery mode, but it aborts
Don't know enough to know if install procedure tries to validate the "to be installed" ROM's MD5 and aborts since it's different from that on the download page
Don't know what purpose of tee folder is -- is it to connect to local carrier?
How about if I try to install "unmodified" ROM (in its unmodified form) and once it's installed, if it does (?), replace the tee folder at that later stage, to check for ability to connect to carrier?
Do I need to unlock the SIM card first --- as that's also something I haven't done
(naturally, I've backed up and able to restore to what I had before attempting the install)
KiwiCool60a said:
Am located in New Zealand, and hence using model i8160L, running stock JB ROM
Am trying to modify / install Maclaw CM KK ROM -- but am having problems
-- it "reads" the ROM and "immediately" (afaik) but aborts installation
-- NO ERROR MESSAGES come up for any indication as to why it's aborting
Am trying to do the following -- appreciate any feedback to correct procedure if I'm making eny errors
(i) omitting any and all references to L in 8160L string -- should I restrict it to any particular lines? -- using Build.Prop Editor
-- the Settings/About Device shows it as an 8160, rather than an 8160L after the Build.Prop changes, but the boot screen still shows it as the 8160L -- but at least I don't get the error message about trying to install ROM on wrong device
(ii) before attempting installation, downloading the latest ROM, unzipping the ROM using 7zip, deleting "tee" folder
-- and pasting tee folder from the stock JB ROM installed on my phone
(iii) re-zipping the ROM using 7zip -- I notice I get a different MD5 to that llsted on the download page
(iv) attempting to flash the modified ROM in Recovery mode, but it aborts
Don't know enough to know if install procedure tries to validate the "to be installed" ROM's MD5 and aborts since it's different from that on the download page
Don't know what purpose of tee folder is -- is it to connect to local carrier?
How about if I try to install "unmodified" ROM (in its unmodified form) and once it's installed, if it does (?), replace the tee folder at that later stage, to check for ability to connect to carrier?
Do I need to unlock the SIM card first --- as that's also something I haven't done
(naturally, I've backed up and able to restore to what I had before attempting the install)
Click to expand...
Click to collapse
md5 sum change probably because you uncompressed and re-compressed file.
no you dont have to unlock carrier.
use total commander and delete first 3 lines in updater-script.(all before mount.. bahblablah) and then compress it, then try.
btw it doesnt show any status errors?
When to alter ROM cont'd
teddytsen said:
md5 sum change probably because you uncompressed and re-compressed file.
no you dont have to unlock carrier.
use total commander and delete first 3 lines in updater-script.(all before mount.. bahblablah) and then compress it, then try.
btw it doesnt show any status errors?
Click to expand...
Click to collapse
MANY MANY thanks for your very prompt reply, and further information
"status errors" -- as a result of ?? -- no status errors evident after rebooting with modfified Build.Prop
had lots of "fun" on my previous efforts with custom ROMs -- played with several on a Huawei G300 I had --
-- but, gee, this is an ongoing learning process -- now to learn about updater script !!!
(only learnt about Total Commander from your post - despite its high rating -- but note others have used other things for "text editing")
(but have discovered some TUTs on xda)
Reading more carefully through the posts I see it may be possible to flash the ROM, and then later, substitute the tee folder supplied in the Maclaw ROM with the stock JB one -- right?
I'll definitely learn more about updater-script, but I'll try to flash the ROM again without modifying the ROM === OK?
KiwiCool60a said:
MANY MANY thanks for your very prompt reply, and further information
"status errors" -- as a result of ?? -- no status errors evident after rebooting with modfified Build.Prop
had lots of "fun" on my previous efforts with custom ROMs -- played with several on a Huawei G300 I had --
-- but, gee, this is an ongoing learning process -- now to learn about updater script !!!
(only learnt about Total Commander from your post - despite its high rating -- but note others have used other things for "text editing")
(but have discovered some TUTs on xda)
Reading more carefully through the posts I see it may be possible to flash the ROM, and then later, substitute the tee folder supplied in the Maclaw ROM with the stock JB one -- right?
I'll definitely learn more about updater-script, but I'll try to flash the ROM again without modifying the ROM === OK?
Click to expand...
Click to collapse
-Dont care about ro.build.model. once assert is deleted you dont have to change it. And its not mandatory.
-I recommended total commander just because its the only root browser i have that shows the assert in 3 lines exactly. Unless es etc. You can also use other editors ^.^
-like when installation is aborted, it says status 7(or 0 etc)
Sent from my GT-I8160 using Tapatalk
Many thanks -- now for the "rest" and time for tee
teddytsen said:
-Dont care about ro.build.model. once assert is deleted you dont have to change it. And its not mandatory.
-I recommended total commander just because its the only root browser i have that shows the assert in 3 lines exactly. Unless es etc. You can also use other editors ^.^
-like when installation is aborted, it says status 7(or 0 etc)
Sent from my GT-I8160 using Tapatalk
Click to expand...
Click to collapse
Many thanks!! KK installed -- that was the "fascinating" thing -- no status errors on previous failed attempt at installation -- nothing
but now it's installed -- with GApps added, and now to "worry" about the rest of it all
unsurprisingly -- if tee does what I think it does -- but I can't find a TUT on that anywhere
-- so currently, I can't connect to my local carrier, so it's currently not a :"phone" as such
even more frustratingly, computer found phone when it was first plugged in, but now seems to have lost it!! time to reboot system
-- and, it's been a while since I used CM but I can't find extsdcard!!
Cm file manager?
Settings-general settings-access mode- root
Sent from my GT-I8160 using Tapatalk
Permissions
teddytsen said:
Cm file manager?
Settings-general settings-access mode- root
Sent from my GT-I8160 using Tapatalk
Click to expand...
Click to collapse
sorry, not used to that one -- for that matter, I tend to stay away from things affecting the system I don't know
so I'm lost in permissions in different apps -- can't find "paste" in CM file, and can't find RW permissions in ES!!
But you're being exceptionally patient! thanks, heaps
Lot easier than I thought -- and MANY thanks again
KiwiCool60a said:
sorry, not used to that one -- for that matter, I tend to stay away from things affecting the system I don't know
so I'm lost in permissions in different apps -- can't find "paste" in CM file, and can't find RW permissions in ES!!
But you're being exceptionally patient! thanks, heaps
Click to expand...
Click to collapse
Actually, it's a lot easier than I thought -- working phone, with KK installed -- without need to unlock carrier!!
Many thanks for the guidance, patience ....
and, of course, to the ROM developers
Repeated problems with Maclaw KK ROM
KiwiCool60a said:
Actually, it's a lot easier than I thought -- working phone, with KK installed -- without need to unlock carrier!!
Many thanks for the guidance, patience ....
and, of course, to the ROM developers
Click to expand...
Click to collapse
Many thanks for past help with intall procedure -- but have had repeated problems of late -- last installed ROM on March 9th -- could install several versions prior to that date, and use them successfully, but since then have been unable since I repeatedly get "Error searching for networks", and hence cannot connect to carrier, and hence unable to use phone as phone, though other functions seem to work OK, -- any ideas??
Hello, i have one question.
I have a Samsung Galaxy Tab 3 7.0 ( SM-T113 ) i can't find any rom and root package for my pad.
Maybe someone can help me?
I support this request. The T113 is a new device. I was thinking of getting me a cheap t110, but the t113 is also cheap. If it would be possible to root this I would take it.
Rooting SM-T113
Hello everybody
I struggled to root my Samsung Galaxy Tab 3 Lite
(SM-T113). So I decided to shared my experience and writing this tuto.
Of course, this is "a non standart" device, and elements for rooting
SM-T110 or SM-T210 didn't work. Android version of this device is 4.4.4
Methodology and tries :
I have proccured myself the Samsung official firmware (here). This image
allow me to get back during beetwen the experimentations. I tried several
experimentation and restore the device after each fail.
Installing with Odin the Clockworkmod (CWM) for SM-T110 , for SM-T210, and
SM-T211. (Has preconnised here) Each time, when loading the CWM, I got a little
(1 ascii character) exclamation mark at the top-left of the screen. The device
didn't boot on recovery
Installing with Odin the (TWRP) for SM-T110. Same symptom
Installing philz_touch : against the message with only the red exclamation
mark.
I conclude of checked of some signature before executing recovery.
Using Kingo root application : software try to root during 20 minutes and
finaly fail.
Using Towel root application : The device isn't reconized
Conclusion: Security breach for rooting have been fixed in this version of android
I have downloaded UPDATE-SuperSU-v2.46 for android. The idea is to push this
application by the standart android update way. (native recovery).
Sending the zip archive 'as is' => failure to check the whole archive
Re-sign the archive with the autosign tools => failure to check footer of archive
Rewriting the update-script (see here) and (here) and auto-sign the archive
: failure to check footer
I am procured myself some pre-rooted image. Odin fail to import them. (and I
have no succed to use heimdall for linux on my debian)
I have try to improve the official samsung Image by adding root manually , using
simg2img and make_ext4fs. Odin fail at the same point
It's remaining me two way : Or I try to generated a correct update file, or I
try to understood why odin fail to import prerrooted system and my custom
image. I choosed the second option.
The offical update is splited by several blocks, each block having is own
header. A master header provide global information about the image (number of
blocks, size, ...). I have putting some spies in simg2img and
observate the headers of official update and of my custom uptate. Result is
surprising : It is missing 4 bytes by headers. in custom update. According to
samsung orginal update, missing values seem to be constant. I suppose it's a 'magic
number', checked by the device to be sure the 'good' update is applied. So I
modifed this headers in make_ext4fs for adding the missing constants. My custom update is now
accepted by my devices, and I got root (!)
I will now describe how to generate and import this update.
DISCLMAIMER
I or Xda-developers are not responsable of any damage one your device, in particular if you bricked it
You waranty will probably void
Rooting device may lead to some dysfonctionnement, or may open some security breach. You are the only responsable.
1. What do you need :
Your device, and a cable to connect it to your PC
A Windows distribution, with Odin (www (dot) samsungodindownload (dot) com/) and the samsung drivers (www (dot) samsung (dot) com/us/support/owners/product/SM-T110NYKAXAR#")
A Linux distribution, with the appropriate compilation package (build-essential), and with git.
A way to transfers big files beetwen your Linux and your Windows.
The Official samsung update (best-tech-reviews (dot) com/update-sm-t113-t113xxu0aoa4-android-4-4-4-2152 or rapidgator (dot) net/file/7140bfdc421eea86eda5a5cbca00216e)
The UPDATE-SuperSU-v2.46 in zip format (download (dot) chainfire (dot) eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip?retrieve_file=1") (or root program for your android)
Method assume you never installed root on your device
2. Generate the update
Uncompress the Samsung official image.
Code:
unzip image_official.zip
tar -xf image.tar.md5
Uncompress and make_ext4fs and simg2img (here)
Code:
cd ..
git clone https:// github.com/YuLaw/ext4-utils.git
cd ext4_utils
Download and applied the patch (see attachment)
Code:
patch -p1 < ../patch_ext4_utils.diff
Build ext4_utils
Code:
make
Extract the image
Code:
cd ..
unzip DBT-T113XXU0AOA4-20150121104149.zip
tar -xf T113XXU0AOA4_T113OXA0AOA4_HOME.tar.md5
ext4_utils/simg2img system.img system.img.raw
Mount the image
Code:
mkdir mount_point
sudo mount -o loop,rw system.img.raw mount_point
unzip the UPDATE-SuperSU-v2.46
Code:
mkdir UPDATE-SuperSU-v2.46
mv UPDATE-SuperSU-v2.46.zip UPDATE-SuperSU-v2.46/
cd UPDATE-SuperSU-v2.46/
unzip UPDATE-SuperSU-v2.46.zip
cd ..
Now, copy common file and armv7 one the mount_point. If you use an other
device, replace the armv7 repository by the appropriate repository according
to your device processor. You can refer to the
UPDATE-SuperSU-v2.46/com/google/android/update-binary to find them.
Code:
sudo cp UPDATE-SuperSU-v2.46/armv7/{su,supolicy} mount_point/xbin
sudo cp UPDATE-SuperSU-v2.46/armv7/su mount_point/xbin/daemonsu/
sudo cp UPDATE-SuperSU-v2.46/armv7/libsupol.so mount_point/lib
sudo mkdir mount_point/etc/init.d
sudo cp UPDATE-SuperSU-v2.46/common/99SuperSUDaemon mount_point/etc/init.d
sudo cp UPDATE-SuperSU-v2.46/common/Superuser.apk mount_point/app
sudo mv mount_point_app/etc/install-recovery.sh mount_point/etc/install-recovery.bak
sudo cp UPDATE-SuperSU-v2.46/common/install-recovery.sh mount_point/etc
sudo chmod 0755 mount_point/xbin/daemonsu
sudo chmod 06755 mount_point/xbin/su
sudo chmod 0755 mount_point/xbin/supolicy
sudo chmod 0644 mount_point/lib/libsupol.so
sudo chmod 0755 mount_point/etc/install-recovery.sh
sudo chmod 0744 mount_point/etc/init.d/99SuperSUDaemon
sudo chmod 0644 mount_point/app/Superuser.apk
We will regenerate the file system. Do not umount them. If patch on
ext4_utils is not applied, you shall applied it now.
Code:
mkdir output
sudo ext4_utils/make_ext4fs -s -a system -l 1500M output/system.img mount_point
cd output
tar -cf system.img system.img.tar
md5sum -t system.img.tar >> system.img.tar
mv system.img.tar system.img.tar.md5
You can now transfert this file to your windows operating system.
3. Android prepartion
You must ensure your device is allowed to install apk from untrusted source. See
in option/application or in developper menu option
Connect the android to you pc.
Boot your android device into downloading mode. On SM-T113 Samsung galaxy Tab3 lite,
press power, volume down and pad when booting.
Run odin, ensure Repartion is NOT checked, and select the AP (PDA) button. (The
only checked case is autoreboot and F.Reset time) Load the previously generated
file and click start.
Your android device may now reboot and install the root application.
Congratulation, you have now rooted your device. You can clean up the downloaded files.
4. One of these step fail, what I can do to come back. :crying:
You may import with odin the official samsung firmware or proceed to a factory return from the recovery.
5. May I eat my devices if I can't root it ?
Samsung user manual say to not do it.
samsung tab 3 sm-t113 root
Thank for the update about for the root. But I don't have Linux and I don't know how to use Linux too. It's there a way without Linux
If you don't have linux, you can try using Cygwin. This is a linux like environment running on Windows.
or if you find my solution is too complicated, I do it for you.
Warning: before following the next step, ensure your device is Samsung Galaxy Tab 3 Lite SM-T113
Simply download the file :
https://drive.google.com/file/d/0Bwao3SgtdOPPYm9XNF8wQXEyWjg/view?usp=sharing
unzip file and upload it to you device with Odin
Nb: This file will remain on my google drive until I need space or until I decide to remove it. (in a long time)
grizzlyfute said:
If you don't have linux, you can try using Cygwin. This is a linux like environment running on Windows.
or if you find my solution is too complicated, I do it for you.
Warning: before following the next step, ensure your device is Samsung Galaxy Tab 3 Lite SM-T113
Simply download the file :
unzip file and upload it to you device with Odin
Nb: This file will remain on my google drive until I need space or until I decide to remove it. (in a long time)
Click to expand...
Click to collapse
Thank you for your great work!!
Do you think the package will work also with Tab3 lite SM-T116? (Sm-t116 should have only the 3g module more than sm-t113)
Root Worked
Thanks for the your great effort grizzlyfute.
Worked perfectly and finally got my device rooted
beodev said:
Do you think the package will work also with Tab3 lite SM-T116? (Sm-t116 should have only the 3g module more than sm-t113)
Click to expand...
Click to collapse
No. Package will erase the system partition, including configuration file (/system/etc), and probably some drivers. Importing the SM-T113 package will probably put the 3G module out of service.
I suggest you to procure an 'official firmware' for your device (see in Settings/about for the exact version) and follow procedure in post#3.
grizzlyfute said:
No. Package will erase the system partition, including configuration file (/system/etc), and probably some drivers. Importing the SM-T113 package will probably put the 3G module out of service.
I suggest you to procure an 'official firmware' for your device (see in Settings/about for the exact version) and follow procedure in post#3.
Click to expand...
Click to collapse
I tried to follow your linux-instructions (by using cygwin, with an official sm-t116 firmware), but something go wrong (i think cygwin doesn't know batch commands like "sudo", or "su" etc..).
I put your md5 file to my sm-t116: the results is that the device is rooted, but no network connection works (Wi-Fi too) .
I jump back to the original firmware, maybe in the future someone will develop the firmware for the sm-t116 version.
Thank you for the Help
Thanks buddy! It works! :good:
Just got my t113 today and now rooted. Awesome!
Light at end of tunnel
grizzlyfute said:
...
Warning: before following the next step, ensure your device is Samsung Galaxy Tab 3 Lite SM-T113
Simply download the file :
https://drive.google.com/file/d/0Bwao3SgtdOPPYm9XNF8wQXEyWjg/view?usp=sharing
unzip file and upload it to you device with Odin
...
Click to expand...
Click to collapse
FABULOUS!!! And thank you! And have i said fabulous? And thank you??? And this, only for giving me rooting hope!
I am a proud user of a gt-i9100 for a few years, rooted/unlocked/custom rom(ehndroix), so, all the 9 miles, but, that´s the phone... And since i am not very proficient when it comes to using odin, and if you don´t write all the steps, i am like a fish out of water (can´t breathe or swim) and i am afraid to do some wrong step.
So, when you say upload it to your device, which will be the parameters in ODIN?
Edit: I confirm, it works, i was afraid of doing something wrong and brick the thingy, but its working fine, thanks to odin and pda and this developpers work!:victory:
!! Thanks !!
I followed these instructions step-by-step on my SM-T113, but for some reason the device would always fail to receive the image I'd built (Odin would just sit there saying NAND Write Start! for a while, then fail. So I tried downloading your precompiled version... and what do you know, it worked straight away.
Thanks a ton, HUGE help!
(q)how to root tab sm-t116nu ?
please help me
cjmac said:
I followed these instructions step-by-step on my SM-T113, but for some reason the device would always fail to receive the image I'd built (Odin would just sit there saying NAND Write Start! for a while, then fail. So I tried downloading your precompiled version... and what do you know, it worked straight away.
Thanks a ton, HUGE help!
Click to expand...
Click to collapse
Sorry for the delay.
I encountered the same problems before I make the patch. Cause of the problem is the file generated by ext4_utils tools is not immediately compatible with the sm-t113 device. I have to add constants in the encapsulation headers for the device to accept the file. You can see details in the patch provided.
To determine theses constants, I put some spies in simg2img and extracts the official firmware. It is not exclude these values change in function of the device.
For the sm-t116, I suggest to open an other thread. I think the works can be picked up and adapted.
wifi issues?
Thanks for your work!
I have successfully rooted my tablet, but its now not connecting to a weak wifi signal it was previuosly connecting to. In fact, it previuosly rratd the same signal as "fair".
Is this connected in any way to the rooting package, and can be resolved somehow?
Hello, thanks for your help! now, i have my Samsung SM-T113 rooted.
but, there any way to put the cmw?
I want to make a backup image and not as .... thanks
Anyone know if this way working in model SM-T113NU ?
Samsung official image ?
grizzlyfute said:
2. Generate the update
Uncompress the Samsung official image.
Click to expand...
Click to collapse
I don't understand what is the "Samsung official image" :
i don't see it neither in the 1. What do you need : list , nor in attached files
I thought it could be "The Official samsung update ", but its name is not "image_official.zip" I see in the first line of code, and moreover I see "unzip DBT-T113XXU0AOA4-20150121104149.zip" in the following lines.
any chance to make more easy the way to get root? btw I have the variant SM-T133NU 4.4.4 KK please!
Minimalistk0 said:
any chance to make more easy the way to get root? btw I have the variant SM-T133NU 4.4.4 KK please!
Click to expand...
Click to collapse
I second that! Rooted custom rom highly appreciated! I'd even pay some bucks
FINALLY!
We Present To You
SamPWND!
Root for the USA Variants of the S8 & S8 Plus Devices!
(This thread will focus only on the S8+)
This thread had been closed/locked until further notice. The thread and links should remain active and the thread has served it's purpose. You will need to search the thread if you have any questions pertaining to root or any errors/issues that you are facing. The other reason I have decided to close the thread is because it has gone off topic one too many times, people like to argue and debate and MODS have had to come in here 1 too many times to clean it up so as to make life easier, I will just shut it down. Please do not bombard me with PM's for root assistance because if it has been answered in this thread already (and it most likely has) I will just direct you to search in the thread if I am able to respond at all.
ALSO, please do not utilize our firmware/root files/method without gaining permission first or I will ask for the thread to be removed/locked. Just because the thread gets closed does not mean we didn't spend a lot of time to get to this point.
Thank you and enjoy SamPWND root!
DISCLAIMER:
We are not responsible for any damage done to your device as no one is "forcing" you to root your phone! If you are not sure of how to follow instructions or use ADB then I would suggest waiting for someone to help you or that you read up on how these things work before diving head first. The ENG system is not very stable when it comes to root as well as it has a ton of tools and binaries not available on stock devices so we are not responsible if you break something while on any firmwares but especially while on the ENG firmware.
DISCLAIMER 2:
Please do not take our work and post it elsewhere. We spent a lot of time on this for people to take it and use it as if it is their own. With that being said, if you have a better process for something or find any issues/errors, please PM myself or one of the listed contributors of this root method, do NOT post it directly in the thread because it causes confusion. We know with 100% certainty the files and method presented WORK. If it is not working for someone there are a number of possible reasons why. If users start modifying our files/scripts and posting them and you decide you are going to use someone else's files/scripts, do not post in our threads asking for us to help you because we will have no idea what was modified or changed and will just tell you to use the original files.
Returning to Stock:
- It is possible to return to 100% stock and it is very EASY to do.
- This is the reason why I provide both Normal, and Comsey ODIN's.
- All you need is a full stock 4 files firmware of your choice.
- Extract those files. Open ODIN and select the 4 files in their respective slots.
* IF YOU GET ERRORS such as model mismatch, start with 1 partition at a time to find out which one is throwing the error. (In my experience, it is the BL file that causes the error.) Once you find the culprit, throw that partition into the other ODIN. (For example, the BL file is giving an error in Comsey ODIN, throw the BL file in NORMAL ODIN and flash it by itself.)
* Typically you might have to throw individual partitions into either of the ODIN's but in the end you will be back on full stock firmware.
What doesn't work while rooted?
- On ANY ROOTED device, anything that utilizes "SafetyNet" will NOT work.
- Magisk and/or SuHide will NOT work. Our bootloader is still locked and these two modify the boot.img which would cause our devices to not boot up and having to start the root process over again, you have been warned!
- Systemless root also does NOT work. Again, this patched the boot.img which we cannot do because of our locked bootloader.
- Battery currently only charges to 80%. There are a few that feel it legit doesn't charge fully but others are claiming they get the same amount of life as they did with a 100% battery so the 80% might just be a visual issue or "fake" when it is really at 100%. Either way, we are still looking into this.
Main Contributors:
@elliwigy
@Harry44
@akiraO1
@BotsOne
@GSMCHEN
@jrkruse (for uploading system.img.ext4 and his root zip for the part 2 instructions)
@V0idst4r (for help in creating a "1 click" method for part 1!)
Initial Description on the process:
We are essentially flashing a modified 4 file firmware package in ODIN and then utilizing a few binaries in conjunction with SU binary and a permissive kernel. We will then be running some ADB commands and in order to have a fully working, amazing root with all things working we will be utilizing a stock system.img & a root script in conjunction with Flashfire. If you want to know all the technical details, you can take apart the files if you would like. It is released, so it is no longer a secret!
PART 1 Instructions: NEW
Flashing SamPWND 4 Files Firmware:
1) Download the PART 1 FILES Listed Below (this includes SamPWND_Root.zip and Initial ODIN 4 Files FIRMWARE and ODIN's if you do not already have them.)
2) Extract the 4 Files ODIN Firmware Package (also extract the ODIN's if you do not have them already.)
3) Open Comsey ODIN and select each partition and then select the files from the 4 File Firmware Package you extracted (BL goes in BL slot, AP in AP, CP in CP & CSC in CSC.) The options you select in ODIN shouldn't matter but I typically select F. Reset Time, Auto Reboot, Re-Partition, Nand Erase All & Update Bootloader.
4) Press Start and Wait for it to Finish. Once it finishes, if it boots into stock recovery simply select "Reboot System"
Take a breather, the ODIN portion is done (unless you have to start over for some reason...)
Now the NEW Root Process:
1) Once the phone is booted up, make sure you have ADB Enabled and connected to your PC. It should have prompted you to accept USB debugging as soon as it booted up.
2) Unzip the SamPWND_Root.zip
3) Double click "step1"
4) Wait for it to finish and once it reboots and comes back on you will be rooted with SuperSU!
5) Continue to PART 2 for "EVEN BETTER ROOT"
* It is a Windows bat file so not sure if it works on MAC. If you can't run bat files, use the OLD instructions.
* The bat will take about 30 seconds to run it's course. This is due to giving enough time for the remount script to mount the system as RW.
PART 1 Instructions: OLD
1) Download the PART 1 FILES Listed Below (this includes Systemroot + ADB zip, Initial ODIN 4 Files FIRMWARE and ODIN's if you do not already have them)
2) Extract the 4 Files ODIN Firmware Package, Also extract the ODIN's if you don't have them already.
3) Open Comsey ODIN and select each partition and then select the files from the 4 File Firmware Package you extracted (BL goes in BL slot, AP in AP, CP in CP & CSC in CSC.) The options you select in ODIN shouldn't matter but I typically select F. Reset Time, Auto Reboot, Re-Partition, Nand Erase All & Update Bootloader.
4) Press Start and Wait for it to Finish. Once it finishes, if it boots into stock recovery simply select "Reboot System"
Take a breather, the ODIN portion is done (unless you have to start over for some reason...)
Now the ADB Process to actually Root:
1) Extract the Systemroot + ADB zip listed below in an easy to find directory.
2) Make sure phone is connected to PC and ensure USB Debugging is enabled.
3) In the folder you extracted, you should see a "cmd-here" file. Double click it and it should open up an ADB cmd window.
4) Now we will start with the ADB commands:
- Type
Code:
adb push systemroot /data/local/tmp
What it will look like:
C:\Users\Thomas\Desktop\Minimal ADB and Fastboot>adb push systemroot /data/local/tmp
/data/local/tmp/systemroot/: 8 files pushed. 0 files skipped. 10.0 MB/s (7072263 bytes in 0.673s)
- Type
Code:
adb shell chmod -R 7777 /data/local/tmp
What it will look like:
C:\Users\Thomas\Desktop\Minimal ADB and Fastboot>adb shell chmod -R 7777 /data/local/tmp
C:\Users\Thomas\Desktop\Minimal ADB and Fastboot>
- Type
Code:
adb shell setsid su
What it will look like:
C:\Users\Thomas\Desktop\Minimal ADB and Fastboot>adb shell setsid su
(It will be blank with the blinking cursor, move to next step)
- Type
Code:
id
(you should at this point see that your are in a root shell!)
What it will look like:
id
uid=0(root) gid=0(root) groups=0(root),1004(input),1007(log),1011(adb),1015(sdcard_rw),1028(sdcard_r),3001(net_bt_admin),3002(net_bt),3003(inet),3006(net_bw_stats),3009(readproc) context=u:r:shell:s0
- Type
Code:
echo /data/local/tmp/systemroot/remount2.sh > /sys/kernel/uevent_helper
What it will look like:
echo /data/local/tmp/systemroot/remount2.sh > /sys/kernel/uevent_helper
(Again, it will be blank with a blinking cursor after you type the command in, move to next step)
- WAIT ABOUT 30 SECONDS BEFORE MOVING TO THE NEXT COMMAND
- Type "
Code:
mount
" (you should now see rw next to rootfs and system partitions)
What it will look like:
mount
(After we type in mount, we are looking for the below two items to say rw like they do in the next two lines)
rootfs on / type rootfs (rw,seclabel,size=1586716k,nr_inodes=396679)
/dev/block/sda19 on /system type ext4 (rw,seclabel,relatime)
- Type
Code:
sh /data/local/tmp/systemroot/root.sh
What it will look like:
sh /data/local/tmp/systemroot/root.sh
rm: /system/bin/install-recovery.sh: No such file or directory
cp: /system/bin/.ext/.su: No such file or directory
chmod: /system/bin/.ext/.su: No such file or directory
chcon: /system/bin/.ext/.su: No such file or directory
touch: '/data/.supersu': Permission denied
/data/local/tmp/systemroot/root.sh[55]: can't create /data/.supersu: Permission denied
chmod: /data/.supersu: No such file or directory
C:\Users\Thomas\Desktop\Minimal ADB and Fastboot\NEWSAMPWNDFILES>
5) If you followed all of the above commands to the T, your device will reboot and you will have SuperSU installed.
6) Install Flashfire from the Play Store.
7) Up to this point, you are on an ENG system.img with root that doesn't function the way we would like it to. This means you will feel a vibrate every time you try to gain SU access as well as it will take quite a while for an SU prompt. You can stay on this root if you would like to experiment with the ENG system, but outside of that I would HIGHLY recommend you proceed to the STEP 2 PROCESS.
PART 2 Instructions:
1) Download the PART 2 FILES listed below (this includes the system.img.ext4 and the add CSC Systemroot zip both provided courtesy of @jrkruse , view post #195 for specifics on what these are but essentially they are stock QD2 system.img and the zip has multi CSC, root, and a bunch of other goodies!)
2) Extract the System.img.ext4 zip and place that actual "system.img.ext4" onto the Internal SD Card (might work from external but some users have reported issues with chainfires root.zip and FF with external sd cards, this is not a fault of the SamPWND files/process.)
3) Place the entire Add CSC Systemroot zip onto Internal or Externdal SD Card (THIS FILE DOES NOT NEED TO BE UNZIPPED, THROW THE WHOLE ZIP FILE ONTO SD CARD OR INTERNAL)
4) Open Flashfire and grant it root when it prompts you. IF FLASHFIRE IS NOT LOADING FILES AND YOU JUST SEE A CIRCLE OR LIKE ITS CONSTANTLY LOADING, PUT THE PHONE IN AIRPLANE MODE AND THEN GO BACK INTO FLASHFIRE AND THE FILES SHOULD NOW APPEAR.
5) Press the + sign and select "Flash Firmware Package" & navigate to where you placed the system.img.ext4 and select it
6) Press the + sign and select "Flash ZIP or OTA" & navigate to where you placed the Add CSC Systemroot zip and select it, select Mount System as r/w
7) Press the + sign and select "Wipe" and select System data, 3rd party apps, Dalvik cache, Cache partiton, Cache Partiton format
8) Now, long press on "Wipe" and make sure it is on the top by dragging it. The order should be Wipe, Flash Firmware Package & finally Flash ZIP or OTA
9) Make sure the "Everoot" is disabled!
10) Flash away!
If you followed all of PART 1, then followed all of PART 2, then you will be updated to QD2, rooted with busybox (and have some other goodies) and the phone will be running great! Root will be stable and snappy as ever. Adaway, Root Checker, V4A etc. etc. are now all possible.
XDA:DevDB Information
S8 Plus SamPWND ROOT, ROM for the Samsung Galaxy S8+
Contributors
elliwigy
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 4.x
ROM Firmware Required: Android 7.0, Any Current Firmware
Based On: Stock Touchwiz
Version Information
Status: Beta
Current Stable Version: 1
Stable Release Date: 2017-08-19
Current Beta Version: 1
Beta Release Date: 2017-08-19
Created 2017-08-19
Last Updated 2017-08-19
DOWNLOADS SECTION:
PART 1 FILES:
SamPWND_Root.zip
https://mega.nz/#!8YcgTSwI!hIfbdJZ466sr1AyfiHLdtr1p-To0QdthTPDmVwtv0dc
Initial ODIN 4 Files FIRMWARE
https://mega.nz/#!5cUjnCwK!Zgw5_CaINbES08gwDzl7yMN0N4nzm56Fa12ow-gppKA
Mirror: https://www.androidfilehost.com/?fid=961840155545589828
AFH MD5: 73720c409782b751355b9443a003a6e8
Normal + Comsey ODIN
https://mega.nz/#!cFN2DD4C!I7AT4TgNSzBp7Py0UhC7pHZ0M4WDQhEC5qj2xD_qluM
Systemroot + ADB zip - OLD
https://mega.nz/#!1MVDhZxQ!Wd4Umvju1sS1DAe-jBcTue9NKSJ4co0I2gwiyC3c2pE
PART 2 FILES: (Potentially will be providing a rom.zip soon that will have latest updated U1 with multi CSC pre-rooted with other goodies)
system.img.ext4
https://www.androidfilehost.com/?fid=817550096634794132
Add CSC Systemroot
https://www.androidfilehost.com/?fid=745425885120757028
For more info on these files please see @jrkruse post located here:
https://forum.xda-developers.com/showpost.php?p=73489978&postcount=925
THANK HIM WHILE YOU'RE AT IT!
@elliwigy @Harry44 @akiraO1 @BotsOne
These months these four people are very hard, and I very relaxed!! lol
Cool Job!
GSM CHEN said:
@[email protected]@[email protected]
These months these four people are very hard, and I very relaxed!! lol
Click to expand...
Click to collapse
haha but we know it wouldnt be possible without you man
Dam it, if I wasnt drunk, and tired, I eould vet myself out of bed and do this now, lol. Thanks for all your hard work.
One thing i would suggest would be to either put the commands that need to be typed in as bold face type or im not sure if its possible on here, as im on my phone atm, but there are Code/code tags avaiable that will make them easier to copy and paste.
Again, thanks for this......I did not think it was going to be possible. This will be my morning present when i wake up, feels like Xmas.......
theboz1419 said:
Dam it, if I wasnt drunk, and tired, I eould vet myself out of bed and do this now, lol. Thanks for all your hard work.
One thing i would suggest would be to either put the commands that need to be typed in as bold face type or im not sure if its possible on here, as im on my phone atm, but there are Code/code tags avaiable that will make them easier to copy and paste.
Again, thanks for this......I did not think it was going to be possible. This will be my morning present when i wake up, feels like Xmas.......
Click to expand...
Click to collapse
to be honest its late haha, threw it together lol ill try to tidy it up when i get time lol
Awesome can't wait to try this out soon!
elliwigy said:
to be honest its late haha, threw it together lol ill try to tidy it up when i get time lol
Click to expand...
Click to collapse
You are forgiven, lol. I figured it would be out in the morning, just not this early in the morning.
You guys should have gotten some sleep you may need it after this weekend.
What a nice thing to wake up to when I'm getting ready to head to work at 530 in the morning lol. Can't wait to give this a shot once I get off work 12 hours later. Thanks for everything devs.
S8 thread will be posted tomorrow, too late to do it tonight
You guys are the ****. Thanks for all of your hard work.
Just want to know if Knox will be triggered or not? Please also add this to the first post [emoji397]
Where's the best place to get the stock firmware we might need just in case? As far as best download speed etc.
Wow,. I honestly didn't think it was possible. Amazing accomplishment ellwigy.
Sent from my SM-G955W using XDA-Developers Legacy app
powerstroke said:
Where's the best place to get the stock firmware we might need just in case? As far as best download speed etc.
Click to expand...
Click to collapse
I got mine here... Took awhile to download... Someone gave me the link in the 955U1 thread
http://updato.com/firmware-archive-select-model?record=F6B451FD73EE11E7963AFA163EE8F90B
Also do we need to back up our EFS/Imei stuff? I know its recommended when flashing roms in recovery but our bootloader is locked.... Is there a way to back up without root?
Edit* I asked about the backup before in a previous thread but didn't get an answer.... Sorry to ask again
Techvir said:
Just want to know if Knox will be triggered or not? Please also add this to the first post [emoji397]
Click to expand...
Click to collapse
Knox is not triggered
Kjc99 said:
I got mine here... Took awhile to download... Someone gave me the link in the 955U1 thread
http://updato.com/firmware-archive-select-model?record=F6B451FD73EE11E7963AFA163EE8F90B
Click to expand...
Click to collapse
And this will work with Sprint S8+ Correct? Lastly, since the latest update which included Sprint LTE Plus calling. We will still manage to have that feature after root right? Because boy do I enjoy being able to browse the internet and being on a call at the same time again lol
powerstroke said:
And this will work with Sprint S8+ Correct? Lastly, since the latest update which included Sprint LTE Plus calling. We will still manage to have that feature after root right? Because boy do I enjoy being able to browse the internet and being on a call at the same time again lol
Click to expand...
Click to collapse
If you have the system.img for the latest update then correct, if not and you want those features with root you will have to download the AP and CSC from thw firmware you want
powerstroke said:
And this will work with Sprint S8+ Correct? Lastly, since the latest update which included Sprint LTE Plus calling. We will still manage to have that feature after root right? Because boy do I enjoy being able to browse the internet and being on a call at the same time again lol
Click to expand...
Click to collapse
I have the U1 model so I'm not sure...
Edit* Deleted
Hii. I am ankit.
I have downloaded custom rom and twrp recovery.
Now i want to get back to stock rom and stock recovery in my phone.
And also wants to use official updates of phone's software.
Can anyone help?
1.Download the odin
2.Download rome orginal a50
Windows
The easiest way for Windows is to just use Odin. This is a nice tutorial on how to restore to stock with it.
Linux
If you use Linux and don't want to bother with trying to use something like Wine to run Odin, the following steps are for you.
Get the firmware
You can use something like updato.com, but from my experience it failed 2 separate 4 hour downloads, and the download speeds are abysmal, so I can't recommend.
I use samloader, the only caveat with it is that you can only get the latest firmware for a region (because Samsung only saves the latest one), you'll need to use something else for older versions.
1.1 Install samloader, following their instructions
1.2 Get your Model number, it should look something similar to GT-I8190N, if you don't know it, here is a link on how to find it (it's made for stock firmware, but it should still point you in the right direction)
1.3 Get your region (you might be able to install from any region, but I think it's safest if it's the region from which the phone is bought), here you can find a good list of available regions
1.4 Check the latest firmware version available. Use the following command, and replace the model and region with your values
Code:
$ samloader -m GT-I8190N -r BTU checkupdate
The output should be something like this:
Code:
I8190NXXAMJ2/I8190NBTUAMJ1/I8190NXXAMJ2/I8190NXXAMJ2
1.5 Download the firmware, whose name you got from step 1.4. Use the following command, again replacing the values with your own
Code:
$ samloader -m GT-I8190N -r BTU download -v I8190NXXAMJ2/I8190NBTUAMJ1/I8190NXXAMJ2/I8190NXXAMJ2 -O .
After it has finished downloading, the output should look something like this:
Code:
downloading GT-I8190N_BTU_1_20131118100230_9ae3yzkqmu_fac.zip.enc2
[################################] 10570/10570 - 00:02:02
1.6 Final step is to decrypt the downloaded firmware. To do so, use the following command, while again, changing your values. Important: after the -V, you put in a number, that number is dependent on the file you downloaded from step 1.5. If the file ends with .enc4, replace the number 2 with the number 4, if it ends with .enc2, leave it at 2.
Code:
$ samloader -m GT-I8190N -r BTU decrypt -v I8190NXXAMJ2/I8190NBTUAMJ1/I8190NXXAMJ2/I8190NXXAMJ2 -V 2 -i GT-I8190N_BTU_1_20131118100230_9ae3yzkqmu_fac.zip.enc2 -o GT-I8190N_BTU_1_20131118100230_9ae3yzkqmu_fac.zip
Unzip the firmware archive. You should do so in a new folder, as a lot of files will be extracted.
Code:
unzip GT-I8190N_BTU_1_20131118100230_9ae3yzkqmu_fac.zip
Extract the files from the files, you got in step 2 (yeah, there are archived files inside an archive). The following command does just that, you can simply copy-paste it
Code:
for file in *.tar.md5; do tar -xvf $file done
Finally, flash all of the resulting .img and .bin files. On how to find which file goes where, use these instructions. If you use Heimdall for flashing, in that link you can also instructions for it.
Syndamia said:
Windows
The easiest way for Windows is to just use Odin. This is a nice tutorial on how to restore to stock with it.
Linux
If you use Linux and don't want to bother with trying to use something like Wine to run Odin, the following steps are for you.
Get the firmware
You can use something like updato.com, but from my experience it failed 2 separate 4 hour downloads, and the download speeds are abysmal, so I can't recommend.
I use samloader, the only caveat with it is that you can only get the latest firmware for a region (because Samsung only saves the latest one), you'll need to use something else for older versions.
1.1 Install samloader, following their instructions
1.2 Get your Model number, it should look something similar to GT-I8190N, if you don't know it, here is a link on how to find it (it's made for stock firmware, but it should still point you in the right direction)
1.3 Get your region (you might be able to install from any region, but I think it's safest if it's the region from which the phone is bought), here you can find a good list of available regions
1.4 Check the latest firmware version available. Use the following command, and replace the model and region with your values
Code:
$ samloader -m GT-I8190N -r BTU checkupdate
The output should be something like this:
Code:
I8190NXXAMJ2/I8190NBTUAMJ1/I8190NXXAMJ2/I8190NXXAMJ2
1.5 Download the firmware, whose name you got from step 1.4. Use the following command, again replacing the values with your own
Code:
$ samloader -m GT-I8190N -r BTU download -v I8190NXXAMJ2/I8190NBTUAMJ1/I8190NXXAMJ2/I8190NXXAMJ2 -O .
After it has finished downloading, the output should look something like this:
Code:
downloading GT-I8190N_BTU_1_20131118100230_9ae3yzkqmu_fac.zip.enc2
[################################] 10570/10570 - 00:02:02
1.6 Final step is to decrypt the downloaded firmware. To do so, use the following command, while again, changing your values. Important: after the -V, you put in a number, that number is dependent on the file you downloaded from step 1.5. If the file ends with .enc4, replace the number 2 with the number 4, if it ends with .enc2, leave it at 2.
Code:
$ samloader -m GT-I8190N -r BTU decrypt -v I8190NXXAMJ2/I8190NBTUAMJ1/I8190NXXAMJ2/I8190NXXAMJ2 -V 2 -i GT-I8190N_BTU_1_20131118100230_9ae3yzkqmu_fac.zip.enc2 -o GT-I8190N_BTU_1_20131118100230_9ae3yzkqmu_fac.zip
Unzip the firmware archive. You should do so in a new folder, as a lot of files will be extracted.
Code:
unzip GT-I8190N_BTU_1_20131118100230_9ae3yzkqmu_fac.zip
Extract the files from the files, you got in step 2 (yeah, there are archived files inside an archive). The following command does just that, you can simply copy-paste it
Code:
for file in *.tar.md5; do tar -xvf $file done
Finally, flash all of the resulting .img and .bin files. On how to find which file goes where, use these instructions. If you use Heimdall for flashing, in that link you can also instructions for it.
Click to expand...
Click to collapse
Sorry sir but I don't know how to use linux.
Could you tell me easy way.
_Ankit_Chahar said:
Sorry sir but I don't know how to use linux.
Could you tell me easy way.
Click to expand...
Click to collapse
Do you have a Windows PC if so download latest Odin an latest firmware file for your phone also download Samsung USB Drives install USB Drives on you PC extract Odin an extract file's from firmware zip place file's in Odin folder start Odin click on where it says AP in Odin the file will pop up click on AP file an repeat for BL ,CP, an CSC files an click on start . Should be all good .
_Ankit_Chahar said:
Sorry sir but I don't know how to use linux.
Could you tell me easy way.
Click to expand...
Click to collapse
https://forum.xda-developers.com/t/guide-how-to-downgrade-to-android-9.4096323/ Same procedure, just use newest Android version.
Watch this video How to Flash Samsung Galaxy ROM ( Firmware ) with ODIN
Hey there. I'm also having kinda same problem. I recently upgraded my Galaxy A50 to latest January 2021 updates but after that my touch is not working. I tried to install old firmware : 'A505FDDU5BTF1 INS' which helps me to fix the problem in past but now I can't install it. I tried it with odin many times but it keeps saying "SW REV. CHECK FAIL (BOOTLOADER) DEVICE 6, BINARY 5" something like that. Can anyone help me out here???
Details of my Galaxy A50 :
Model number : SM-A505F/DS
Serial number RZ8M51R73AE
One UI version 2.5
Android version 10
Baseband version A505FXXS6BUA6
AP : A505FDDS6BUA6
CP : A505FXXS6BUA6
CSC : A505FOLM6BUA6
Model : SM-A505F/DS
Please inform me if anyone can on [email protected]
Any help will be really appreciated. Thank you in advance.
SudanTmz said:
Hey there. I'm also having kinda same problem. I recently upgraded my Galaxy A50 to latest January 2021 updates but after that my touch is not working. I tried to install old firmware : 'A505FDDU5BTF1 INS' which helps me to fix the problem in past but now I can't install it. I tried it with odin many times but it keeps saying "SW REV. CHECK FAIL (BOOTLOADER) DEVICE 6, BINARY 5" something like that. Can anyone help me out here???
Details of my Galaxy A50 :
Model number : SM-A505F/DS
Serial number RZ8M51R73AE
One UI version 2.5
Android version 10
Baseband version A505FXXS6BUA6
AP : A505FDDS6BUA6
CP : A505FXXS6BUA6
CSC : A505FOLM6BUA6
Model : SM-A505F/DS
Please inform me if anyone can on [email protected]
Any help will be really appreciated. Thank you in advance.
Click to expand...
Click to collapse
Make u sure to use Binary 6 rom, U cannot flash binary 5 rom... thats why it didnt work. u wanted to use binary 5 rom
peter couniaz said:
Do you have a Windows PC if so download latest Odin an latest firmware file for your phone also download Samsung USB Drives install USB Drives on you PC extract Odin an extract file's from firmware zip place file's in Odin folder start Odin click on where it says AP in Odin the file will pop up click on AP file an repeat for BL ,CP, an CSC files an click on start . Should be all good .
Click to expand...
Click to collapse
After that could I use knox services like secure folder etc.
_Ankit_Chahar said:
After that could I use knox services like secure folder etc.
Click to expand...
Click to collapse
Yes you should be able to use secure folder after going back to official firmware .
kisvagen said:
Make u sure to use Binary 6 rom, U cannot flash binary 5 rom... thats why it didnt work. u wanted to use binary 5 rom
Click to expand...
Click to collapse
And if for example, I want to go back to Android 9, which is binary 5 and my A50 is Android 11, binary 7, is there any way I can ignore the binary or something?