I have Galaxy S3 LTE,i have flashed 5 to 6 ROM's in my device. The ROM which i like most comes with a stock kernel and i wish to use Boeffla kernel.What are steps that i should do? I'm really afraid of doing something terribly wrong.
JackRIPx said:
I have Galaxy S3 LTE,i have flashed 5 to 6 ROM's in my device. The ROM which i like most comes with a stock kernel and i wish to use Boeffla kernel.What are steps that i should do? I'm really afraid of doing something terribly wrong.
Click to expand...
Click to collapse
1.Download ODIN.
2.Download the Kernel
3.Open the downloaded md5 file in PDA
4.Make sure only Auto Reboot & F. Reset Time are ticked
5.Put your phone into download mode & plug in
6.Press Start.. Done
Fantassy123 said:
1.Download ODIN.
2.Download the Kernel
3.Open the downloaded md5 file in PDA
4.Make sure only Auto Reboot & F. Reset Time are ticked
5.Put your phone into download mode & plug in
6.Press Start.. Done
Click to expand...
Click to collapse
I seemed to have downloaded in .zip format instead of .tar,will it work?
JackRIPx said:
I seemed to have downloaded in .zip format instead of .tar,will it work?
Click to expand...
Click to collapse
When it is a ZIP you can flash it via recovery , is it a .tar file , you have to put it in ODIN
Related
Hello All,
Please look at these steps, is it will work?:
1. Root tablet without flashing CWM ( [HOWTO] Root the Galaxy Tab 2 7" without flashing the bootloader )
2. Install Mobile Odin and flash CWM (Without increasing custom count)
3. Backup current firmware in CWM (Because I cannot find original firmware for my region (SEK)
4. Install CM9/10, any other custom ROM
5. Restore backup of original firmware with CWM
And now is one more question: How to flash original bootloader (and where to get it?) without increasing custom counter?
I just rooted and flashed CM9 with my Tab 2 7.0. few days ago!!
Here is the steps I would like to share with you:
1. Use Task Manager to kill all Kies background programs, e.g. Kies.exe, KiesTrayAgent.exe, KiesPDLR.exe...
2. Enable USB debugging in the Tab and connect to PC
3. Use the DebugfsRoot_v1.8.n95.zip from this post
4. Run RootDebugfs_n95.bat in command prompt with administrator right
5. Just few clicks and wait for the Tab to reboot twice
6. Now the Tab is already rooted, install Mobile Odin from Play store and install the CWM recovery by Mobile Odin
7. Reboot Tab in CWM and flash CM9 & Gapps
cyfgeorge said:
I just rooted and flashed CM9 with my Tab 2 7.0. few days ago!!
Here is the steps I would like to share with you:
1. Use Task Manager to kill all Kies background programs, e.g. Kies.exe, KiesTrayAgent.exe, KiesPDLR.exe...
2. Enable USB debugging in the Tab and connect to PC
3. Use the DebugfsRoot_v1.8.n95.zip from this post
4. Run RootDebugfs_n95.bat in command prompt with administrator right
5. Just few clicks and wait for the Tab to reboot twice
6. Now the Tab is already rooted, install Mobile Odin from Play store and install the CWM recovery by Mobile Odin
7. Reboot Tab in CWM and flash CM9 & Gapps
Click to expand...
Click to collapse
Thanks a lot!
But question about restoring stock recovery still active... I need to know where to get original recovery from Samsung and how to flash it (I do not want lose varanty if something happens with tablet )
Did you try to search the stock rom from www.samfirmware.com?
cyfgeorge said:
Did you try to search the stock rom from www.samfirmware.com?
Click to expand...
Click to collapse
Sure, but there is no ROM for Ukraine . Also looking it on the samsung-updates.com with same negative result.
If you have p3100(wifi+gsm) download P3100XWBLF5 (it's Russia 4.0.4 ) extract with winrar,and you will find recovery.img inside,and flash it with Mobile Odin.It works 100% ,I have tested myself.You can flash with Mobile Odin any recovery you want,not only CWM,you can flash any official recovery.img ,just extract it from your rom with winrar.
Cheers!
Thanks!
I have GT-P3110, but i think that recovery same for all regions and it can be extracted from any ROM for 3110. Is i am right?
Sent from my GT-P3110 using xda app-developers app
Yes,unpack any rom for p3110 ,and extract recovery.img from it,put on your sdcard (internal or microsd) open Mobile Odin,and select Open recovery,and flash it.It will work 100%.
Cheers!
viasat said:
Yes,unpack any rom for p3110 ,and extract recovery.img from it,put on your sdcard (internal or microsd) open Mobile Odin,and select Open recovery,and flash it.It will work 100%.
Cheers!
Click to expand...
Click to collapse
I can't extract md5 files, help..?
and btw mobile odin isn't compatible with my tab so I'll try odin. :S
Bibicp said:
I can't extract md5 files, help..?
Click to expand...
Click to collapse
*.md5 file is tar archive. You can change extension from *.md5 to *.tar and unpack it (for ex; with using WinRar). Also you can use Total Commander for unpacking.
P.S. Will try this method in a week or little bit later. (I am on Vacation and dont have any laptop)
Convert .img file to .tar.md5 for use in flashing Odin ( with odin in it )...
INSTRUCTION:
1. Download and extract it.
2. Move the .img file in the folder
3. Click ''ImgToTar.Md5'' and the converting process should running
4. Click ''odin'' and odin will popup
5. Start your flashing process with ease....
Don't forget to say thanks...
****in A bro! Thanks a lot
Thanks a lot.
고맙습니다,
Translation: thank you,
can i flash ultra compression tar file? or normal compression file
salim7685 said:
Convert .img file to .tar.md5 for use in flashing Odin ( with odin in it )...
INSTRUCTION:
1. Download and extract it.
2. Move the .img file in the folder
3. Click ''ImgToTar.Md5'' and the converting process should running
4. Click ''odin'' and odin will popup
5. Start your flashing process with ease....
Don't forget to say thanks...
Click to expand...
Click to collapse
Thanks big time
hello hope you are fine
i have galaxy s6 sm -g920f
it was running on 5.1..1 G920FXXU2BOGE
tried to install marshmallow XEF-G920FXXU3DPAD-20160223100452 via odin
my fone stuck and dont boot
when i tried to flash 5.1.1 again with 4 files it fail to flash bootloader
in recovery mode it was still MM recovery and written dm-verify verification failed need to check dRK first ... ?
what the problem please any solution ???
sorry for my bad english
Hmm. Let's try this.
1. Go to recovery->wipe everything.
2. Reflash stock rom through odin.
2a. If it fails at cm.bin or any other .bin file or hidden.img file just delete them from the .tar file using 7zip.
3. If it still fails. Google "G920F pit file" and flash it with that file.
3a. If that STILL fails. Remove all files from the .tar file and just leave system.img and sboot.bin(or img not sure).
4. Now reflash and enjoy! . If anything fails after all my steps. Copy and paste the odin log and I will try to figure out something else.
ProtoDeVNan0 said:
Hmm. Let's try this.
1. Go to recovery->wipe everything.
2. Reflash stock rom through odin.
2a. If it fails at cm.bin or any other .bin file or hidden.img file just delete them from the .tar file using 7zip.
3. If it still fails. Google "G920F pit file" and flash it with that file.
3a. If that STILL fails. Remove all files from the .tar file and just leave system.img and sboot.bin(or img not sure).
4. Now reflash and enjoy! . If anything fails after all my steps. Copy and paste the odin log and I will try to figure out something else.
Click to expand...
Click to collapse
thx bro i'll try and give you feed back
hi
I think i killed my note 3 neo (sm-n7505) by rooting attempt without getting proper education or necessary backup and tools!
If someone can help, pls....
i am not going to explain EVERYTHING what i did but important.(i think)
1 Rooted
2 Verified with ROOT CHECK
3 Installed BUSY BOX
5 TWRP installation failed. (Installed a Fake one!. It damaged everything)
4 NO BACKUP ( I made a backup but somehow it wiped away!) (forgot to double check!)
6 "NAND ERAZE ALL" CHECKED IN ODIN AND EXECUTED while CF-Autoroot! (wrong! wrong! wrong!)
CURRENT SITUATION/WHAT I HAVE NOW/WHAT CAN I DO ?
SYSTEM IS NOT DEAD COMPLETELY(?)
I CAN 'ON' IT BUT END WITH A BOOT LOOP
I CAN GO TO RECOVERY MODE
I CAN GO TO DOWNLOAD/ODIN MODE
I HAVE ACCESS IN EXTERAL SD CARD
EXTERNAL SD CARD HAS THE FOLLOWING:
CF AUTOROOT hllte-hlltexx-smn7505.zip
kyleopen-cwm-v3.tar.md5
Super SU V2.52.zip
BETA-SuperSU-v2.52.zip
SR3-SuperSU-v2.79-SR3-20170114223742.zip
---------------------------------------------------------------------
me.twrp.twrpapp-22.apk.md5
---------------------------------------------------------------
BOOT LOADER
SM-N7505-4.4.2.zip
SM-N7505_BOOT_5.1.1.ZIP
SM-N7505_BOOT_5.1.1.ZIP
-------------------------------------------------------------
StockROM and Custom ROM
Galaxy-Note-3-Neo-SM-N7505-Full-Factory-rom-4.4.2.zip
Note-4-Mini10 N7505.zip
Note-5-ROM.zip
NoteRom V4 SM-N750 Only.zip
cm-12.1-20160809-UNOFFICIAL-hllte.zip
----------------------------------------------------------------------------
There is "full budle of the ANDROID SDK
(Android-studio-bundle-162.3871768-windows)
There is "minimal_adb_fastboot_v1.4.2_setup on my pc"
installed samsung usb driver
--------------------------------------------------------------------------------
I Cannot Successfully Execute ANY of the above in Recovery Mode
Here the the text at the top of the reovery Screen
[Andorid system recovery (3e> LMY47X.N7505POUDOK2 ]
and
Here is the info at the bottom
#MANUAL MODE #
--Applling Multi-CSC...
Applied the CSC-code : KSA
Successfully applied multi -CSC.
---------------------------------------------------------------
When i execute any zip, it end-up with some error messages
"Signature verification failed"
"footer is wrong"
and restart the device or bootloop!
-------------------------------------------------------------
CAN I FIX THE DEVICE? OR NO NEED TO WASTE MY TIME AND BUY A NEW ONE?
Thank you
Shihab
here is the link it lead me here
trendblog(dot)net(slash)fix-soft-bricked-android-device-first-aid-guide
@1978shihab
Hi
Try downloading your firmware from sammobile.com based on your country code and flash it with Odin while your phone in Download Mode, in Odin, check f.reset time and auto reboot, don't check any thing else.
The firmwares link:
https://www.sammobile.com/firmwares/sm-n7505/SM-N7505/
SAM MOBILES FILE FAILED BUT "Galaxy-Note-3-Neo-SM-N7505-Full-Factory-rom-4.4.2.zip "
The file from sammobile (dot-com) did NOT FIX the issue of my note3 neo sm-n750; but with the old file, i tired before, ( "Galaxy-Note-3-Neo-SM-N7505-Full-Factory-rom-4.4.2.zip" from filehost(dot)com fixed the issue.
Why i failed before with the same file?
Actually i copied the "...full-factory ROM.. .zip" into an sd card and tried to 'install from the external sources' option in phone's recovery.
why?
As you know, the Odin only allow .tar,.md5,.smd .gz, .tgz formats; NOT ZIP file. I thought the recovery program can extract the zip file from the external SD card and do the rest . So i didn't try to extract it manually.
The zip file from sammobile contains only one md5 file. I tried it with odin's AP button and executed but failed with some error messages.
So I extracted "...full-factory ROM.. .zip file" (once i left), and I got AP, BL, CP, CSC files. then I selected and executed each file with ODIN's desired buttons and It gave my SM-N7505 a new life.
Anyway, Thank you very much dear Mr.MigoMujahid for spending time to help me
God Bless you
shihab
1978shihab said:
The file from sammobile (dot-com) did NOT FIX the issue of my note3 neo sm-n750; but with the old file, i tired before, ( "Galaxy-Note-3-Neo-SM-N7505-Full-Factory-rom-4.4.2.zip" from filehost(dot)com fixed the issue.
Why i failed before with the same file?
Actually i copied the "...full-factory ROM.. .zip" into an sd card and tried to 'install from the external sources' option in phone's recovery.
why?
As you know, the Odin only allow .tar,.md5,.smd .gz, .tgz formats; NOT ZIP file. I thought the recovery program can extract the zip file from the external SD card and do the rest . So i didn't try to extract it manually.
The zip file from sammobile contains only one md5 file. I tried it with odin's AP button and executed but failed with some error messages.
So I extracted "...full-factory ROM.. .zip file" (once i left), and I got AP, BL, CP, CSC files. then I selected and executed each file with ODIN's desired buttons and It gave my SM-N7505 a new life.
Anyway, Thank you very much dear Mr.MigoMujahid for spending time to help me
God Bless you
shihab
Click to expand...
Click to collapse
Hi Mr-Shihab
To flash a zip with recovery, then it has to be a flashable zip, it should be built in a specific way so the recovery can work with it, and the zip you have is a normal compressed files, so it can't be flashed at all with recovery, also note that the zip you downloaded from sammobile might be corruptedly downloaded, because sammobile offer a clean roms, anyway, you can also use samsung-firmware.org, it's a trusted site as well.
Ps: that md5 file you got works the same as the 4 files you downloaded after.
God bless you too
Had the same issue with a note 3 neo once, completely bricked it and couldn't flash stock firmware. Went to odin recovery mode as it is called (or something like that) and just put in some information found once you take the battery out and it did its thing and bam it is working.
RAZERZDAHACKER said:
Had the same issue with a note 3 neo once, completely bricked it and couldn't flash stock firmware. Went to odin recovery mode as it is called (or something like that) and just put in some information found once you take the battery out and it did its thing and bam it is working.
Click to expand...
Click to collapse
There is Odin download Mode and there is Recovery Mode!!, which one do you mean?! ?
Also Recovery Mode is to flash files or wipe, and Odin Download mode is to flash files with Odin, how did you input anything there?!!
MigoMujahid said:
There is Odin download Mode and there is Recovery Mode!!, which one do you mean?!
Also Recovery Mode is to flash files or wipe, and Odin Download mode is to flash files with Odin, how did you input anything there?!!
Click to expand...
Click to collapse
There is a recovery mode (not the one where you flash your roms and replace with twrp) in kies (my bad for not saying that) that reflashes the whole phone, you could literally erase the recovery or the kernel and you'd still be able to recover it which you can check out here
Hello guys! I'm trying to install a patched boot.img file from my Samsung Galaxy A03 for root but I can't. Every time in download mode when I want to flash the magisk_patched file renamed to boot.img and compressed to boot.tar with Odin, I get 3 types of errors:
The first is that during the flash, Odin for no reason suddenly crashes
The second is that I get a message from succeed 0/failed1
The last is that the program freezes on SetupConnection while the cable is well connected from the PC to the phone.
No ports defect is present in my opinion because the phone is perfectly detected when it is in normal mode and I can freely access its storage on my PC.
I have a phone with version number A035GXXU1AVC1 and I downloaded the correct firmware for my phone here: https://samfw.com/firmware/SM-A035G/AMO/A035GXXU1AVC1
The steps I went through are:
1) Enable developer mode and enable OEM unlock to unlock payload boot
2) Unlock the bootloader in the Download Mode
3) Download the firmware from the given link
4) Installed Magisk latest version on the phone
5) Extract the files from the downloaded firmware AP file with Winrar and make an isolated copy of the boot.img
6) Move this isolated copy of boot.img into the phone to patch it with Magisk
7) Once patched, no errors in Magisk
8) Move the patched copy to the PC then rename it to boot.img and create a tar file containing this patched boot.img
9) Open Odin and in Downloade Mode try flashing the patched boot.tar file but that's where it gets stuck and Odin errors show up
Feox said:
Hello guys! I'm trying to install a patched boot.img file from my Samsung Galaxy A03 for root but I can't. Every time in download mode when I want to flash the magisk_patched file renamed to boot.img and compressed to boot.tar with Odin, I get 3 types of errors:
The first is that during the flash, Odin for no reason suddenly crashes
The second is that I get a message from succeed 0/failed1
The last is that the program freezes on SetupConnection while the cable is well connected from the PC to the phone.
No ports defect is present in my opinion because the phone is perfectly detected when it is in normal mode and I can freely access its storage on my PC.
I have a phone with version number A035GXXU1AVC1 and I downloaded the correct firmware for my phone here: https://samfw.com/firmware/SM-A035G/AMO/A035GXXU1AVC1
The steps I went through are:
1) Enable developer mode and enable OEM unlock to unlock payload boot
2) Unlock the bootloader in the Download Mode
3) Download the firmware from the given link
4) Installed Magisk latest version on the phone
5) Extract the files from the downloaded firmware AP file with Winrar and make an isolated copy of the boot.img
6) Move this isolated copy of boot.img into the phone to patch it with Magisk
7) Once patched, no errors in Magisk
8) Move the patched copy to the PC then rename it to boot.img and create a tar file containing this patched boot.img
9) Open Odin and in Downloade Mode try flashing the patched boot.tar file but that's where it gets stuck and Odin errors show up
Click to expand...
Click to collapse
Feox said:
The last is that the program freezes on SetupConnection while the cable is well connected from the PC to the phone.
Click to expand...
Click to collapse
I had the above issue myself, and after searching I found this answer and it actually worked, even though it seems silly.
ethical_haquer said:
I had the above issue myself, and after searching I found this answer and it actually worked, even though it seems silly.
Click to expand...
Click to collapse
Sorry for the late reply, I was busy with several other things... When I try the steps in the answer you gave me, I now have Odin freezing on File analysis with versions 3.13.1 and 3.14.4. With the version I was using, 3.10.6, Odin suddenly started crashing instantly this time rather than displaying the errors mentioned in my first message in this thread... I don't know what to do... I tried to Root a Samsung Galaxy A02s, an A12 and before that an old Huawei Y6 from 2014 years ago and I had the same problem every time which is that Odin gives me random errors like what I present for this A03...
Feox said:
Sorry for the late reply, I was busy with several other things... When I try the steps in the answer you gave me, I now have Odin freezing on File analysis with versions 3.13.1 and 3.14.4. With the version I was using, 3.10.6, Odin suddenly started crashing instantly this time rather than displaying the errors mentioned in my first message in this thread... I don't know what to do... I tried to Root a Samsung Galaxy A02s, an A12 and before that an old Huawei Y6 from 2014 years ago and I had the same problem every time which is that Odin gives me random errors like what I present for this A03...
Click to expand...
Click to collapse
So you are following the official installation instructions? I'm pretty sure you don't have to:
Feox said:
5) Extract the files from the downloaded firmware AP file with Winrar and make an isolated copy of the boot.img
Click to expand...
Click to collapse
as the official installation instructions for a Samsung device running A9 or higher say:
"
Unzip the firmware and copy the AP tar file to your device. It is normally named as AP_[device_model_sw_ver].tar.md5
Press the Install button in the Magisk card
If your device does NOT have boot ramdisk, check the “Recovery Mode” option
Choose “Select and Patch a File” in method, and select the AP tar file
Start the installation, and copy the patched tar file to your PC using ADB:
adb pull /sdcard/Download/magisk_patched_[random_strings].tar
DO NOT USE MTP as it is known to corrupt large files.
"
It doesn't sound like you have to isolate the boot.img.
Oh OK thanks man! I go try tonight to make a patched OS with Magisk with the entire AP file. What I have do is patch only the boot.img IN the AP file.
And last question. How to know if the phone have ramdisk? Ramdisk is the RAM or nothing to see?
Feox said:
Oh OK thanks man! I go try tonight to make a patched OS with Magisk with the entire AP file. What I have do is patch only the boot.img IN the AP file.
And last question. How to know if the phone have ramdisk? Ramdisk is the RAM or nothing to see?
Click to expand...
Click to collapse
Just read the official installation instructions I linked to. I only copied part of it and pasted it here so you could see it.