Related
I was rooted with CWM recovery. I odin flashed stock with root injected and then flashed via odin stock kernel and recovery. At this time I was able to pull the update and the device restarted to install. Upon 100% completion the device rebooted as I woudl expect but upon reboot it goes right back into the install, hits 100% and does the same thing. It appears Im stuck in a update boot loop. Has anyone else experienced this?
I did a odin restore with Stock 8013.tar with root injected but upon reboot once odin completes it goes right back into this update loop. Someone please help!!!!
ej_424 said:
I was rooted with CWM recovery. I odin flashed stock with root injected and then flashed via odin stock kernel and recovery. At this time I was able to pull the update and the device restarted to install. Upon 100% completion the device rebooted as I woudl expect but upon reboot it goes right back into the install, hits 100% and does the same thing. It appears Im stuck in a update boot loop. Has anyone else experienced this?
I did a odin restore with Stock 8013.tar with root injected but upon reboot once odin completes it goes right back into this update loop. Someone please help!!!!
Click to expand...
Click to collapse
Just flashed stock kernel and recovery via odin and same thing happens. Just after samsung logo on splash screen it goes into the android character with a percentage for an update being applied. It hits 100% and sits there for a couple minutes, reboots and does the same thing all over.
I"m desperate and need this to get fixed!!
ej_424 said:
Just flashed stock kernel and recovery via odin and same thing happens. Just after samsung logo on splash screen it goes into the android character with a percentage for an update being applied. It hits 100% and sits there for a couple minutes, reboots and does the same thing all over.
I"m desperate and need this to get fixed!!
Click to expand...
Click to collapse
I flashed the stock n8000 recovery file via odin and it booted me out of the update loop. I had to do it twice tho. I rooted via odin so our fixes may be different.
I used file posted here http://forum.xda-developers.com/showthread.php?p=30450339#post30450339 post 45
Hope this helps a little
ej_424 said:
I was rooted with CWM recovery. I odin flashed stock with root injected and then flashed via odin stock kernel and recovery. At this time I was able to pull the update and the device restarted to install. Upon 100% completion the device rebooted as I woudl expect but upon reboot it goes right back into the install, hits 100% and does the same thing. It appears Im stuck in a update boot loop. Has anyone else experienced this?
I did a odin restore with Stock 8013.tar with root injected but upon reboot once odin completes it goes right back into this update loop. Someone please help!!!!
Click to expand...
Click to collapse
ej_424 said:
Just flashed stock kernel and recovery via odin and same thing happens. Just after samsung logo on splash screen it goes into the android character with a percentage for an update being applied. It hits 100% and sits there for a couple minutes, reboots and does the same thing all over.
I"m desperate and need this to get fixed!!
Click to expand...
Click to collapse
Ok I'm backup and running. I had to flash "HighonAndroidCWMRecovery" via odin to get past the update loop. Any ideas why this woudl be? I'm running stock with root and custom recovery. If I flash stock recvoery again and attempt the update do you think the same thing will occur?
ej_424 said:
Ok I'm backup and running. I had to flash "HighonAndroidCWMRecovery" via odin to get past the update loop. Any ideas why this woudl be? I'm running stock with root and custom recovery. If I flash stock recvoery again and attempt the update do you think the same thing will occur?
Click to expand...
Click to collapse
This need not be so complicated follow directions here http://forum.xda-developers.com/showthread.php?t=1847054&page=6 see post 58 and 39
Stuck, can't restore factory settings
I tried to unroot my Galaxy note 10.1 wi-fi and have caused such damage that it won't boot up. I have tried to press the power and down volume and I either get the Black welcome screen stuck, requesting I download the md5 file (which I have tried and doesn't work) or asks to use Kies to boot, but my laptops won't even pick up the device, they recognizes that there is a new device connected but it can't read it!
In the top left hand corner it reads
ODIN MODE (in red letters)
Product name: GT-N8010
Customer binary: yes (20 counts)
Current Binary: Custom
System status: Custom
PLEASE HELP!!!!
Thanks in advance
bee_rob said:
I tried to unroot my Galaxy note 10.1 wi-fi and have caused such damage that it won't boot up. I have tried to press the power and down volume and I either get the Black welcome screen stuck, requesting I download the md5 file (which I have tried and doesn't work) or asks to use Kies to boot, but my laptops won't even pick up the device, they recognizes that there is a new device connected but it can't read it!
In the top left hand corner it reads
ODIN MODE (in red letters)
Product name: GT-N8010
Customer binary: yes (20 counts)
Current Binary: Custom
System status: Custom
PLEASE HELP!!!!
Thanks in advance
Click to expand...
Click to collapse
I have same Problem
My only response would be to go to sammobile and download as close to shipped rom as you can (must be for your region and carrier, if from carrier), updated rom is fine. Make sure the download ISN'T corrupted by doing an MD5 check.. Also before f;lashing, make sure you exit KIES as this can screw up the connection in ODIN.
Put in Download mode, hold down volume and power until it says a scary warning, ignore the warning and press up volume.
Flash with ODIN making sure re-partition ISN'T ticked, when it finishes flashing turn off power.
Go to recovery by holding up volume and power button until it goes into recovery.
Wipe data/cache and then wipe dalvik cache.
Reboot and see what happens.
Good luck.
ultramag69 said:
My only response would be to go to sammobile and download as close to shipped rom as you can (must be for your region and carrier, if from carrier), updated rom is fine. Make sure the download ISN'T corrupted by doing an MD5 check.. Also before f;lashing, make sure you exit KIES as this can screw up the connection in ODIN.
Put in Download mode, hold down volume and power until it says a scary warning, ignore the warning and press up volume.
Flash with ODIN making sure re-partition ISN'T ticked, when it finishes flashing turn off power.
Go to recovery by holding up volume and power button until it goes into recovery.
Wipe data/cache and then wipe dalvik cache.
Reboot and see what happens.
Good luck.
Click to expand...
Click to collapse
Not working, not go the Recovery Mode, Only Samsung Logo.
I'm having similar issue as Odin keeps failing when trying to flash ROM.
Does anyone know the commands to do it through ADB? I've done it before on my nexus7 but don't know the commands to exactly use for the note. I still can't get into recovery. Only can get into that ODIN mode. I have all drivers and Android ADB installed on PC.
It seems like nothing will write to the NAND. Although my flash count changes now showing my attempts. I might have no choice but to call Samsung and file a warranty claim. I just don't want to lose all the pictures and info that's in my tablet.
Well I got my tablet back yesterday from Samsung. They fixed it. The report showed they replaced some piece that burned out. I forgot the name of it. Unfortunately all my info and stuff was erased. So I had to reinstall everything manually. At least my tablet working like new again. So glad to have it back. Been like a month or so since I've been able to use it. My nexus 7 and galaxy s3 was holding me down in the meanwhile.
This note is a great device. IM seeing again why I've missed it so much. Works flawlessly on stock Tom.
downloaded twrp 3, was running 5.1.1 on my phone and rooted it. tried to flash a rom and got stuck in a bootloop, now I cant boot into twrp, or anything for that matter. All i can do is hold volume down and power and home and try to ODIN a new bootloader or such and it just fails. what do i do? but when I try to boot into TWRP it goes into a blueish screen with a White exclamation mark saying "An error has occurred while updating the device software. Use the Emergency recovery function in the smart switch PC software. I tried to do that but it didnt even recognize the device. At this point i dont care about the data, I just need a working device
Okay, so I attempted to unroot and flash the stock 5.0.2 software and I got a error on the download screen. It says SW REV. CHECK FAIL. DEVICE: 3. BINARY: 1.
If you have no knox install MM official then flash this kernel tar file (AP) https://drive.google.com/folderview?id=0B40ItdHKfkyQcTA5bnRPWDg0X28&usp=drive_web#list it will boot to mm 5min :good:
Btw you cann downgrade from 5.1.1 to 5.0.1 you just go up not down
zach616 said:
downloaded twrp 3, was running 5.1.1 on my phone and rooted it. tried to flash a rom and got stuck in a bootloop, now I cant boot into twrp, or anything for that matter. All i can do is hold volume down and power and home and try to ODIN a new bootloader or such and it just fails. what do i do? but when I try to boot into TWRP it goes into a blueish screen with a White exclamation mark saying "An error has occurred while updating the device software. Use the Emergency recovery function in the smart switch PC software. I tried to do that but it didnt even recognize the device. At this point i dont care about the data, I just need a working device
Click to expand...
Click to collapse
Happened to me a lot of times in the past few days trying to get MM, for some weird reason flashing Unikernel always works for me (takes me to recovery screen after, then i select 'reboot now'), and all my data, apps etc are still there
emcardle660 said:
Happened to me a lot of times in the past few days trying to get MM, for some weird reason flashing Unikernel always works for me (takes me to recovery screen after, then i select 'reboot now'), and all my data, apps etc are still there
Click to expand...
Click to collapse
will try and update. thank you. didnt work.
Okay guys so now I need a ROM to flash using ODIN. I tried to download from sammobile but the speeds are too damn slow. What I tried to flash was this file " G920TUVU1AOCG_G920TTMB1AOCG_G920TUVU1AOCG_HOME.tar.md5 " and i got the error 3 to 1.
Download Samfirm from here, XDA itself.
Run samfirm, enter model as G920F and your region code.
It will download from Samsung servers, so high speed.
Now flash using Odin the downloaded file by putting the phone in download mode, (vol down+home+power on).
How did it happen?
Did you try to flash the VOD 6.0.1 and got stuck towards the end at hidden.IMG failing the process?
If yes, then its a two minute job. Just open the 6.0.1 tar archive and look for hidden.IMG extract it anywhere and rename it from "hidden.img" to "hidden.img.tar".
Note flash this hidden.img.tar as AP in download mode, your phone should boot.
So, my Sprint S6 is currently in a boot loop after I deleted the operating system because I am an idiot. I can get into download mode, I use odin to flash recovery that I got from updato.com, and I get "Complete write operation failed." I get this every. damn. time. I'm about to lose my mind. I've tried different firmware files across different odin versions to nothing. I'm going to blow my brains out if nothing works. Please for the love of God help.
Edit: Currently downloading the file from Sammobile, 2 hours, God help me.
If you hold down volume down, home and power key simultaneously, then let go and reapply the split second the phone tries to reboot...
It's tricky, but doable.
Do you have TWRP or CWM?
Yes. TWRP is installed.
In my case, when flash twrp went into bootload, but then flash magisk (root), wipes caches and it was normal.
That's in a g920f.
After 3 days of trial and error i have managed to successfully root my Galaxy A30 on oneui 2.0 with Magisk and also installed a couple of Magisk Modules. Exposed installer also works and also managed to install some Modules to go along with it.
I tried to write a tutorial but it was hard to put some of the instructions into words so i gave up eventually.
[EDIT/UPDATE]
After so many requests to write instructions on how to root, ive decided to update the post with detailed instructions.
Here is a link to all the files you will need for rooting your galaxy A30 (SM-305F/DS) on Android 10
(Patched and Unpatched boot.img included) no system.img
https://drive.google.com/file/d/1OucSKAB1FOxHkeYRJaLD9uqvE--AE-lw/view?usp=drivesdk
[GUIDE FOR ROOTING YOUR DEVICE]
----- THIS WILL VOID YOUR WARRANTY AND I WILL NOT BE RESPONSIBLE FOR ANY DAMAGE THAT MIGHT HAPPEN TO YOUR DEVICE, SO PLEASE BE CAREFUL AND FOLLOW THE INSTRUCTIONS PROVIDED-----
-----you can activate secure folder after rooting by following instructions on this thread:
https://forum.xda-developers.com/ga...able-secure-folder-rooted-galaxy-a30-t4093435
------you will lose Samsung pass functionality but you can replace it with Google Autofill...........you won't even notice the difference
------ I recommend you download the full official firmware so that if something goes wrong you can restore your phone with the official firmware, you can download official firmware from: https://samfw.com/
[PREREQUISITE]
-Download the compressed zip from the link, and unzip the file contents.
https://drive.google.com/file/d/1OucSKAB1FOxHkeYRJaLD9uqvE--AE-lw/view?usp=drivesdk
-make sure you have the latest version of Odin and Samsung USB drivers for windows installed in your windows machine, you can download them from:
https://odindownload.com/download/
https://developer.samsung.com/mobile/android-usb-driver.html
-unlock the bootloader(BACK UP IMPORTANT DATA, THIS PROCESS WILL WIPE YOUR PHONE CLEAN), if you've already unlocked your bootloader you can skip this if you haven't unlocked your bootloader follow these
instructions:-
1. navigate to Settings => About phone => Software information => Tap on build number 7 times to activate developer settings.
2. Navigate back to the bottom of the main settings page and you will see Developer Options, open developer settings, and enable OEM Unlocking feature.
3.power of your phone, while powers off hold the Volume Up + Volume Down buttons and plug your USB cable, you will boot into download mode, now hold the Volume Up button for a few seconds and you should see a bootloader unlock prompt, now press Volume Up to unlock the bootloader.
4. After this process reboot your phone but don't set it up. just connect it to the internet and go activate the developer settings again and check the OEM Unlocking option, you should see that your bootloader is now unlocked.
[FLASHING MAGISK PATCHED IMAGE]
1. launch Odin program then go to "options" and untick the "auto-reboot" option. now load the files as to the corresponding sections in Odin, but in AP section load the Boot.tar file.
2.power off your phone, after power off Hold both Volume Up+Volume Down and plug in your USB cable, Confirm by pressing the volume up to boot into download mode. After this, you should see a Blue filled box in Odin indicating the device is successfully detected.
3. now click on the Start button in Odin to flash the files to the phone. if there won't be any error then you should see PASS in Odin after flashing is complete.
4. (BOOT INTO RECOVERY) Now hold the Volume Down + Power button until the screen is black. as soon as the screen turns black let go of the Volume Down and hold the Volume UP while still holding the power button, the phone will boot, then as soon see the screen flash( you will see) let go of the Power button while still holding the Volume UP Button. You will boot into recovery and see Updating System.
5.After the above process reboot back into recovery by following (Step 4) again and Wipe Data Then reboot your phone.
The phone might need to reboot itself twice so please be patient until you see the SAMSUNG boot animation
6.if your phone powers on successfully, download the latest version of Magisk Manager and install and open it, it will set up the Magisk environment and reboot your phone. after that,
Now your phone should be rooted. confirm by opening Magisk Manager
UPDATE (2021)
Sorry for not replying to recent post and not updating the root files as they where from android 10 February update back in 2020.
I dont own the galaxy A30 anymore.
I HAVEN'T TESTED ROOTING THE LATEST FIRMWARE SINCE I DON'T OWN THE DEVICE ANYMORE- SO IF IT WORKS PLEASE LET US KNOW OR IF YOU FIND A EFFICIENT WAY TO ROOT SHARE WITH THE COMMUNITY
To those who still need to root their Galaxy A30. IN 2021
1.Download the latest firmware from https://samfw.com/
2. Extract the firmware using 7zip
3. Move the boot.img/boot.tar file to your phone from the extracted files
4. Download latest version of Magisk manager from the official site and install.
5. Open Magisk > Install > select and patch a file > select the boot image from your device storage > lets go.
6. The patched boot image will be created in your downloads folder
7 . Copy the patched boot Img to your pc and compress the patched boot.img to .tar format using 7zip.
-If you patched a boot.tar file no need to compress it again to .tar format again
8. Flash the patched magisk boot.img. Follow instructions on how to UNLOCK BOOTLOADER AND FLASH PATCHED MAGISK BOOT IMAGE from the instructions in the previous unupdated post.
IF ANYTHING GOES WRONG YOU CAN ALWAYS FLASH THE STOCK BOOT IMAGE IF IT FAILS THEN FLASH THE STOCK ROM TO REGAIN FUNCTIONALITY
Nice work could you pm mirror link for the formware so that i can root it magisk canary. The samsung sites download speeds are too slow
how to root Galaxy A30 (SM-A305F/DS) Android*10. help me sir..
steavex said:
After 3 days of trial and error i have managed to successfully root my Galaxy A30 on oneui 2.0 with Magisk and also installed a couple of Magisk Modules. Exposed installer also works and also managed to install some Modules to go along with it.
I am planning to write a tuitoial later, upload the needed files and links and also to revive your phone in case of a bootloop or failed boot whithout loosing your data.
Click to expand...
Click to collapse
i've rooted successfully too,
but still need twrp to be able to install custom rom
or can i install custom rom via magisk or any method without twrp ?
sm-a305f/ds, android 10
EDIT: successfullt installed twrp, now i need good custom rom + how to install
tried lineage os 16 but cant boot to it
M7md_Ri said:
i've rooted successfully too,
but still need twrp to be able to install custom rom
or can i install custom rom via magisk or any method without twrp ?
sm-a305f/ds, android 10
Click to expand...
Click to collapse
Напиши, как делал....
rever58 said:
Напиши, как делал....
Click to expand...
Click to collapse
do exactly as written here:
https://forum.xda-developers.com/galaxy-a30/how-to/root-galaxy-a30-magisk-canary-relaese-t3936481
Anyone have new TWRP for android10?
M7md_Ri said:
do exactly as written here:
https://forum.xda-developers.com/galaxy-a30/how-to/root-galaxy-a30-magisk-canary-relaese-t3936481
Click to expand...
Click to collapse
Here is a link to all the files you might need for rooting your galaxy A30 (SM-305F/DS) on Android 10
(Patched and Unpatched boot.img included) no system.img
https://drive.google.com/file/d/1OucSKAB1FOxHkeYRJaLD9uqvE--AE-lw/view?usp=drivesdk
M7md_Ri said:
i've rooted successfully too,
but still need twrp to be able to install custom rom
or can i install custom rom via magisk or any method without twrp ?
sm-a305f/ds, android 10
EDIT: successfullt installed twrp, now i need good custom rom + how to install
tried lineage os 16 but cant boot to it
Click to expand...
Click to collapse
I've had the same problem too. TWRP for Android 9.0 works on Android 10 but with "cannot mount /system" error , "no OS detected" error and other backup faliures.
I did manage to successfully flash Havoc OS, but it didn't boot completely, i had a bootloop.
Id like to test out a few other GSI Roms but this is my main/only phone and every time i flash a Rom and it doesn't work id have to go through the hustle of restoring through Odin and setting up the phone again.
It would have been easier to test out Roms with a TWRP image that works with Android 10
steavex said:
I've had the same problem too. TWRP for Android 9.0 works on Android 10 but with "cannot mount /system" error , "no OS detected" error and other backup faliures.
I did manage to successfully flash Havoc OS, but it didn't boot completely, i had a bootloop.
Id like to test out a few other GSI Roms but this is my main/only phone and every time i flash a Rom and it doesn't work id have to go through the hustle of restoring through Odin and setting up the phone again.
It would have been easier to test out Roms with a TWRP image that works with Android 10
Click to expand...
Click to collapse
here is a working twrp for android 10, worked well with my sm-a305f:
https://forum.xda-developers.com/showpost.php?p=82030485&postcount=11
don't forget to flash dm verify by twrp
tell me when u install a custom rom successfully
need to know how to install. many times tried but failed.. please.. tq..
:good:
steavex said:
After 3 days of trial and error i have managed to successfully root my Galaxy A30 on oneui 2.0 with Magisk and also installed a couple of Magisk Modules. Exposed installer also works and also managed to install some Modules to go along with it.
I tried to write a tutorial but it was hard to put some of the instructions into words so i gave up eventually.
But Here is a link to all the files you might need for rooting your galaxy A30 (SM-305F/DS) on Android 10
(Patched and Unpatched boot.img included) no system.img
https://drive.google.com/file/d/1OucSKAB1FOxHkeYRJaLD9uqvE--AE-lw/view?usp=drivesdk
Click to expand...
Click to collapse
I tried it didn't work can you just give a brief tutorial...I really need to root my phone
Khaleed984 said:
I tried it didn't work can you just give a brief tutorial...I really need to root my phone
Click to expand...
Click to collapse
I have updated the post with a tutorial, hope you find it useful
Once I unlock the bootloader, can I enable Camera 2API Level 3 without rooting my device? I can't seem to find any relevant data anywhere else. Please help.
AchyutArjun said:
Once I unlock the bootloader, can I enable Camera 2API Level 3 without rooting my device? I can't seem to find any relevant data anywhere else. Please help.
Click to expand...
Click to collapse
You can't enable full camre2api, because the hardware dosent support level 3. It only supprts limited.
I've tried multiple times myself and couldn't get it to work
it can be applied on galaxy a30 model a305g? thanks!
Anyone tried rooting on Samsung A305GN Firmware?
cHawk said:
After 3 days of trial and error i have managed to successfully root my Galaxy A30 on oneui 2.0 with Magisk and also installed a couple of Magisk Modules. Exposed installer also works and also managed to install some Modules to go along with it.
I tried to write a tutorial but it was hard to put some of the instructions into words so i gave up eventually.
[EDIT/UPDATE]
After so many requests to write instructions on how to root, ive decided to update the post with detailed instructions.
Here is a link to all the files you will need for rooting your galaxy A30 (SM-305F/DS) on Android 10
(Patched and Unpatched boot.img included) no system.img
https://drive.google.com/file/d/1OucSKAB1FOxHkeYRJaLD9uqvE--AE-lw/view?usp=drivesdk
[GUIDE FOR ROOTING YOUR DEVICE]
----- THIS WILL VOID YOUR WARRANTY AND I WILL NOT BE RESPONSIBLE FOR ANY DAMAGE THAT MIGHT HAPPEN TO YOUR DEVICE, SO PLEASE BE CAREFUL AND FOLLOW THE INSTRUCTIONS PROVIDED-----
-----you can activate secure folder after rooting by following instructions on this thread:
https://forum.xda-developers.com/ga...able-secure-folder-rooted-galaxy-a30-t4093435
------you will lose Samsung pass functionality but you can replace it with Google Autofill...........you won't even notice the difference
------ I recommend you download the full official firmware so that if something goes wrong you can restore your phone with the official firmware, you can download official firmware from: https://samfw.com/
[PREREQUISITE]
-Download the compressed zip from the link, and unzip the file contents.
https://drive.google.com/file/d/1OucSKAB1FOxHkeYRJaLD9uqvE--AE-lw/view?usp=drivesdk
-make sure you have the latest version of Odin and Samsung USB drivers for windows installed in your windows machine, you can download them from:
https://odindownload.com/download/
https://developer.samsung.com/mobile/android-usb-driver.html
-unlock the bootloader(BACK UP IMPORTANT DATA, THIS PROCESS WILL WIPE YOUR PHONE CLEAN), if you've already unlocked your bootloader you can skip this if you haven't unlocked your bootloader follow these instructions:-
1. navigate to Settings => About phone => Software information => Tap on build number 7 times to activate developer settings.
2. Navigate back to the bottom of the main settings page and you will see Developer Options, open developer settings, and enable OEM Unlocking feature.
3.power of your phone, while powers off hold the Volume Up + Volume Down buttons and plug your USB cable, you will boot into download mode, now hold the Volume Up button for a few seconds and you should see a bootloader unlock prompt, now press Volume Up to unlock the bootloader.
4. After this process reboot your phone but don't set it up. just connect it to the internet and go activate the developer settings again and check the OEM Unlocking option, you should see that your bootloader is now unlocked.
[FLACHING MAGISK PATCHED IMAGE]
1. launch Odin program then go to "options" and untick the "auto-reboot" option. now load the files as to the corresponding sections in Odin, but in AP section load the Boot.tar file.
2.power off your phone, after power off Hold both Volume Up+Volume Down and plug in your USB cable, Confirm by pressing the volume up to boot into download mode. After this, you should see a Blue filled box in Odin indicating the device is successfully detected.
3. now click on the Start button in Odin to flash the files to the phone. if there won't be any error then you should see PASS in Odin after flashing is complete.
4. (BOOT INTO RECOVERY) Now hold the Volume Down + Power button until the screen is black. as soon as the screen turns black let go of the Volume Down and hold the Volume UP while still holding the power button, the phone will boot, then as soon see the screen flash( you will see) let go of the Power button while still holding the Volume UP Button. You will boot into recovery and see Updating System.
5.After the above process reboot back into recovery by following (Step 4) again and Wipe Data Then reboot your phone.
The phone might need to reboot itself twice so please be patient until you see the SAMSUNG boot animation
6.if your phone powers on successfully, download the latest version of Magisk Manager and install and open it, it will set up the Magisk environment and reboot your phone. after that,
Now your phone should be rooted. confirm by opening Magisk Manager
Click to expand...
Click to collapse
Anyone tried Rooting on Samsung A305GN firmware?
hi there i followed the steps all together but it keeps on stopping at
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1401)..
<ID:0/003> File analysis..
<ID:0/003> Total Binary size: 220 M
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> NAND Write Start!!
<ID:0/003> SingleDownload.
<ID:0/003> sboot.bin
<ID:0/003> param.bin
<ID:0/003> cm.bin
<ID:0/003> vbmeta.img
<ID:0/003> boot.img
<ID:0/003> modem.bin
please how to fix this problem.
i have all the downloaded files and done all the steps altogether.
how to fix SV REV. CHECK FAIL (BOOTLOADER) DEVICE: 5, BINARY 4
Works very well..!!
That worked for me on Android 10. Thanks..!!
Helo! I'm new here at FORUM. In a desperate attempt I decided to create an account here and try to solve my problem with a Samsung device.
It all started when I received a Samsung Galaxy Core 2 device to fix. It is stuck on the Samsung screen and does not start the system. I first tried to install the original ROM of the device with the correct binary through the Sammobile website using the Odin3 program. I tested about 4 different ROMS, but none of them worked.
After unsuccessfully trying to install the ROM I decided to restore the device using Hard Reset mode by pressing the correct key combination. And this is where I came across a very worrying problem. The correct options would be to show the Recovery options on the device's screen, but on this device they do not appear. The only thing that appears is the Android symbol with a red exclamation symbol. This screen appears for 3 seconds only ... after that the system restarts and returns to the Samsung screen again.
I've been trying to find a solution to this problem for a week and so far I haven't found anything.
I installed several features through Download Mode, but none of them were recognized by the system (All features were compatible with the model). Some of these features were Custom Recovery ... TWRP ... CWM .. Custom ROMS ... etc. I installed all of them through Odin3, but after the process was over and the phone restarted it didn't install because it jumped straight to the Samsung screen again.
Since no option on the Hard Reset screen was showing up, I decided to press a few keys at random to try to access an option. After a few attempts I finally managed to see some information. Now I come across written information: '' E: failed to mount / efs (invalid argument) '' https://ibb.co/FmBtv10 (Error Image).
And this is where it gets worse, because I don't know what that means. The only things I have left on the device is that message and nothing more. There are no more options to access.
I hope this device has a solution. I would be very grateful if someone could help me with this. Thanks for reading.
UserCroft said:
Helo! I'm new here at FORUM. In a desperate attempt I decided to create an account here and try to solve my problem with a Samsung device.
It all started when I received a Samsung Galaxy Core 2 device to fix. It is stuck on the Samsung screen and does not start the system. I first tried to install the original ROM of the device with the correct binary through the Sammobile website using the Odin3 program. I tested about 4 different ROMS, but none of them worked.
After unsuccessfully trying to install the ROM I decided to restore the device using Hard Reset mode by pressing the correct key combination. And this is where I came across a very worrying problem. The correct options would be to show the Recovery options on the device's screen, but on this device they do not appear. The only thing that appears is the Android symbol with a red exclamation symbol. This screen appears for 3 seconds only ... after that the system restarts and returns to the Samsung screen again.
I've been trying to find a solution to this problem for a week and so far I haven't found anything.
I installed several features through Download Mode, but none of them were recognized by the system (All features were compatible with the model). Some of these features were Custom Recovery ... TWRP ... CWM .. Custom ROMS ... etc. I installed all of them through Odin3, but after the process was over and the phone restarted it didn't install because it jumped straight to the Samsung screen again.
Since no option on the Hard Reset screen was showing up, I decided to press a few keys at random to try to access an option. After a few attempts I finally managed to see some information. Now I come across written information: '' E: failed to mount / efs (invalid argument) '' https://ibb.co/FmBtv10 (Error Image).
And this is where it gets worse, because I don't know what that means. The only things I have left on the device is that message and nothing more. There are no more options to access.
I hope this device has a solution. I would be very grateful if someone could help me with this. Thanks for reading.
Click to expand...
Click to collapse
When flashing your firmware using odin, try ticking nand erase. Nand erase erases boot
kernel
recovery
system
data
cache
.android_secure
datadata
wimax
efs
preload.
This should solve your mounting problem
Tab E said:
When flashing your firmware using odin, try ticking nand erase. Nand erase erases boot
kernel
recovery
system
data
cache
.android_secure
datadata
wimax
efs
preload.
This should solve your mounting problem
Click to expand...
Click to collapse
Thank you for your attention in answering my question.
I checked the box that says '' Nand Erase All ''. After the Firmware was installed the phone restarted to the Samsung screen again .... so I think it didn't work. Correct would be to restart with the Android logo, correct?
I tried to mark the other options as well ... such as '' Phone Bootloader Update '' ... '' Phone EFS Clear '', but none of them worked. The biggest problem is the reboot, because the files are not being loaded by the system to be installed .... when Odin restarts the cell phone it goes straight to the Samsung screen and from there it keeps loading forever.
Am I using the wrong USB cable or is a PC feature missing? I use a Samsung cable and the Drivers are installed on Windows. Samsung driver version is 1.5.61.0.
I'll be waiting for another suggestion.
Tab E said:
When flashing your firmware using odin, try ticking nand erase
Click to expand...
Click to collapse
UserCroft said:
Helo! I'm new here at FORUM. In a desperate attempt I decided to create an account here and try to solve my problem with a Samsung device.
It all started when I received a Samsung Galaxy Core 2 device to fix. It is stuck on the Samsung screen and does not start the system. I first tried to install the original ROM of the device with the correct binary through the Sammobile website using the Odin3 program. I tested about 4 different ROMS, but none of them worked.
After unsuccessfully trying to install the ROM I decided to restore the device using Hard Reset mode by pressing the correct key combination. And this is where I came across a very worrying problem. The correct options would be to show the Recovery options on the device's screen, but on this device they do not appear. The only thing that appears is the Android symbol with a red exclamation symbol. This screen appears for 3 seconds only ... after that the system restarts and returns to the Samsung screen again.
I've been trying to find a solution to this problem for a week and so far I haven't found anything.
I installed several features through Download Mode, but none of them were recognized by the system (All features were compatible with the model). Some of these features were Custom Recovery ... TWRP ... CWM .. Custom ROMS ... etc. I installed all of them through Odin3, but after the process was over and the phone restarted it didn't install because it jumped straight to the Samsung screen again.
Since no option on the Hard Reset screen was showing up, I decided to press a few keys at random to try to access an option. After a few attempts I finally managed to see some information. Now I come across written information: '' E: failed to mount / efs (invalid argument) '' https://ibb.co/FmBtv10 (Error Image).
And this is where it gets worse, because I don't know what that means. The only things I have left on the device is that message and nothing more. There are no more options to access.
I hope this device has a solution. I would be very grateful if someone could help me with this. Thanks for reading.
Click to expand...
Click to collapse
When flashing TWRP through odin, untick auto reboot, hold power Volume down and home button. You will see a black screen. Then immediately press power volume up home button. Then flash a custom rom. You ticked the bootloader update option, but Samsung core 2 doesn't have bootloader. Hope the nand erase fixed the mounting
Tab E said:
When flashing TWRP through odin, untick auto reboot, hold power Volume down and home button. You will see a black screen. Then immediately press power volume up home button. Then flash a custom rom. You ticked the bootloader update option, but Samsung core 2 doesn't have bootloader. Hope the nand erase fixed the mounting
Click to expand...
Click to collapse
Before I do this procedure I need to ask a few questions. Do I need any requirements to install TWRP? This phone has no ROOT and no other modifications.
Does the ROM that I am going to install need to be compatible with TWRP? I am trying to install an official Samsung ROM without modification.
I will try to use the version for the SM-G355H. The TWRP for this model is hard to find.
Just remembering that my recovery screen is dead, so I don't have access to anything in the device's Recovery options. I look forward to new answers so I can continue.
1. You need no requirements to flash twrp
2. Every rom for your device is compatible.
Just a few questions,
After nand erase and firmware flash, do you still have a corrupted recovery?
Does the firmware that you are flashing, and the model number in Odin mode match?
Tab E said:
When flashing TWRP through odin, untick auto reboot, hold power Volume down and home button. You will see a black screen. Then immediately press power volume up home button. Then flash a custom rom. You ticked the bootloader update option, but Samsung core 2 doesn't have bootloader. Hope the nand erase fixed the mounting
Click to expand...
Click to collapse
I followed those instructions you sent me. I used a TWRP file for the model SM-G355H (I hope it is compatible with this model). The file is called '' recovery.tar.md5 ''. I opened Odin Version 3.0.9 and deactivated the '' Auto Reboot '' option. I passed the TWRP file to the cell phone and did the commands you sent me. The phone restarts with a brief Android screen for 3 seconds and disappears. There are no commands to do. It goes to the Samsung screen again. So I think it didn't work for me.
I hit the keys the same way you told me to (I hope Lol)
You told me to install the custom rom. Is this done after installing TWRP and the phone restarts?
Tab E said:
1. You need no requirements to flash twrp
2. Every rom for your device is compatible.
Just a few questions,
After nand erase and firmware flash, do you still have a corrupted recovery?
Does the firmware that you are flashing, and the model number in Odin mode match?
Click to expand...
Click to collapse
Answering your first question: If you are referring to the error '' E: failed to mount / efs (invalid argument) '' yes. It appears after I press the volume button up or down as soon as the android screen appears (The recovery screen that appears only the symbol of the android lying with a red sign). I wish I could access this screen for a longer time, but it disappears quickly.
Answering your second question: I am using an official 4-part ROM. It corresponds to my country. SM-G355M G355MUBU0AQB1 ZTO G355MZTO0AQB1 OPEN BR ANDROID 4.4.2 FULL FLASH. The version of my Odin is 3.0.9. I heard that this version is the best for installing Android 4.4.2 KitKat systems, so I decided to use it.
Just one more question. Does the Cell Phone have to be 100% charged for this to work? I think I was at 60% when I tried the procedure.
Sorry for asking so many questions. I have little knowledge of the subject. If you can send me a tutorial on the internet in video or written so I can save your time feel free to send me. Thanks!
Sorry, I was busy for some days,
No, you don't need to fully charge your phone
Just found this on youtube, you can check it out
Your phone is g355hm, so I don't know if this recovery will work. If it works, then you can easily solve the problem with your mount points. I'll help you with that after you get twrp
TWRP Recovery 2.8.4.0 & 2.8.5.0 for Samsung Galaxy Core 2 SM-G355H/G355HN
Visit galaxynroms.blogspot.com. Disclaimer: I/XDA/is not responsible for any kind of damage to your device, or in case it explodes, etc. Please use it at your own risk! Whatever you do with your phone it's your own choice! Requirement: 1...
forum.xda-developers.com
Use the Odin tutorial
Tab E said:
Sorry, I was busy for some days,
No, you don't need to fully charge your phone
Just found this on youtube, you can check it out
Your phone is g355hm, so I don't know if this recovery will work. If it works, then you can easily solve the problem with your mount points. I'll help you with that after you get twrp
TWRP Recovery 2.8.4.0 & 2.8.5.0 for Samsung Galaxy Core 2 SM-G355H/G355HN
Visit galaxynroms.blogspot.com. Disclaimer: I/XDA/is not responsible for any kind of damage to your device, or in case it explodes, etc. Please use it at your own risk! Whatever you do with your phone it's your own choice! Requirement: 1...
forum.xda-developers.com
Use the Odin tutorial
Click to expand...
Click to collapse
Thank you for taking the time out of your day to help me. I figured you were busy these days, so I left a message for you to see and remember POST.
I had seen this video on Youtube before, but I saw it again and followed all the steps. I used the two versions of the TWRP for the model SM-G355HN and G355H through the link you sent me, but neither of them is being recognized by the device. I tested other different CWM versions like:
philz_touch_5.15.0-n7100.tar
philz_touch_6.09.6-n8020.tar
philz_touch_6.57.9-ghost
All of them were not recognized and loaded in recovery mode.
I was confused by a specific part of the video. After the STOCK ROM was sent by Odin, the phone restarts. (At that moment there was a cut in the video). I couldn't see what he did, but I decided it was just to turn the device off and on again in download mode to pass the CWM/TWRP.
Is it possible that the system is blocking the files that I am sending? Maybe an FRP lock? I don't know much about the android system, but I suspect that the device's BIOS does not accept any features via download mode. FRP Lock is for Android from 5.0, correct? My Android is 4.4.2 KitKat.
I have already used the main versions of Odin, including the modified versions. I used about 5 different STOCK ROMS and about 10 different versions of TWRP and CWM. Nothing works! I'm getting upset. : (
I'm running out of options. If you have any more suggestions feel free to answer me. Don't be in a hurry ... answer when you can.
Thanks!
One this is certain, FRP can't make any difference. In the video, after the flashing is complete, he immediately turned the phone back in download mode and flashed the custom recovery. As no reocvey works, extract your recovery.img from your firmware and use this one click TWRP porting tool. You will have mount pint issues, but just follow the above video if you are able to successfully able to boot the twrp you ported with this tool https://firmwarecare.com/spreadtrum-auto-twrp-recovery-porter-v1-2
Tab E said:
One this is certain, FRP can't make any difference. In the video, after the flashing is complete, he immediately turned the phone back in download mode and flashed the custom recovery. As no reocvey works, extract your recovery.img from your firmware and use this one click TWRP porting tool. You will have mount pint issues, but just follow the above video if you are able to successfully able to boot the twrp you ported with this tool https://firmwarecare.com/spreadtrum-auto-twrp-recovery-porter-v1-2
Click to expand...
Click to collapse
Thank you for sending the tool. This version does not support Android 4 KitKat. I downloaded version 1.0 (Version 1.0 supports Android 4). I used 3 Recovery.img files from 3 different STOCK ROMS and came across this error on Odin:
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1005)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> recovery.img
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
The versions used were 3.06 - 3.09 - 3.10.6 - 3.11.1 - 3.14.1 3B Patched. I converted Recovery to .tar and .md5, but none of them work. I even tried to use Recovery Original to ensure that the problem was not the conversion, but the original file did not give errors by Odin, so I ruled out the possibility of being the conversion.
I would like to mention something from the video above: His screen in Download mode describes the ROM as Custom. After he passes the FIRMWARE through Odin the information changes to Samsung Official. My information is not Custom ... it is Samsung Official, so I wouldn't know if the transfer was successful or not.
Would it work if I switched to Custom and then went back to Official again? (I'm just speculating. I don't know if that is valid or not.)
Could you answer some questions? There are doubts about the device and the recovery mode.
1 - Why doesn't my recovery screen give me options to access it ? (Just the error message)
2 - Why when I pass any FIRMWARE through Odin and the phone restarts, no process is done for the ROM to be installed normally?
3 - The recovery screen appears for 5 seconds only ... after that the phone restarts again. This is normal ?
4 - Is there any possibility that the system is blocking by default any modification made by Odin by installing FIRMARES or customized recoveries? (This would explain why the phone does not install anything.)
5 - Is it possible to correct the error '' E: failed to mount / efs (invalid argument) '' by passing the original Efs..tar.md5 file?
6 - What is the best version of Odin to install Android 4.4.2 KitKat systems?
Grateful!
Tab E said:
One this is certain, FRP can't make any difference. In the video, after the flashing is complete, he immediately turned the phone back in download mode and flashed the custom recovery
Click to expand...
Click to collapse
UserCroft said:
Thank you for sending the tool. This version does not support Android 4 KitKat. I downloaded version 1.0 (Version 1.0 supports Android 4). I used 3 Recovery.img files from 3 different STOCK ROMS and came across this error on Odin:
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1005)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> recovery.img
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
The versions used were 3.06 - 3.09 - 3.10.6 - 3.11.1 - 3.14.1 3B Patched. I converted Recovery to .tar and .md5, but none of them work. I even tried to use Recovery Original to ensure that the problem was not the conversion, but the original file did not give errors by Odin, so I ruled out the possibility of being the conversion.
I would like to mention something from the video above: His screen in Download mode describes the ROM as Custom. After he passes the FIRMWARE through Odin the information changes to Samsung Official. My information is not Custom ... it is Samsung Official, so I wouldn't know if the transfer was successful or not.
Would it work if I switched to Custom and then went back to Official again? (I'm just speculating. I don't know if that is valid or not.)
Could you answer some questions? There are doubts about the device and the recovery mode.
1 - Why doesn't my recovery screen give me options to access it ? (Just the error message)
2 - Why when I pass any FIRMWARE through Odin and the phone restarts, no process is done for the ROM to be installed normally?
3 - The recovery screen appears for 5 seconds only ... after that the phone restarts again. This is normal ?
4 - Is there any possibility that the system is blocking by default any modification made by Odin by installing FIRMARES or customized recoveries? (This would explain why the phone does not install anything.)
5 - Is it possible to correct the error '' E: failed to mount / efs (invalid argument) '' by passing the original Efs..tar.md5 file?
6 - What is the best version of Odin to install Android 4.4.2 KitKat systems?
Grateful!
Click to expand...
Click to collapse
Try switching to custom and then official.
1) actually, if there is something wrong with just the /efs partition, it shouldn't affect the recovery
2) looks like many partitions are corrupted
4) core 2 has no bootloader or any such protection to stop flashing
5) the efs file is included in the firmware, so it is flashed with the firmware.
Conclusion - looks like multiple partions are corrupted. Try to verify this by flashing any custom recovery or rom and check the status in Odin. Even after flashing a custom recovery, the status is stock, then there are definitely many corrupted partitions. If it's so, fixing it will be very tough
Tab E said:
Try switching to custom and then official.
1) actually, if there is something wrong with just the /efs partition, it shouldn't affect the recovery
2) looks like many partitions are corrupted
4) core 2 has no bootloader or any such protection to stop flashing
5) the efs file is included in the firmware, so it is flashed with the firmware.
Conclusion - looks like multiple partions are corrupted. Try to verify this by flashing any custom recovery or rom and check the status in Odin. Even after flashing a custom recovery, the status is stock, then there are definitely many corrupted partitions. If it's so, fixing it will be very tough
Click to expand...
Click to collapse
I will do as much as I can. Tomorrow I will contact you to say if something worked. If nothing goes well I will need to take the device for specialized maintenance. Thanks for the help, buddy. If I ever manage to solve this problem I will make a guide in FORUM showing how to fix it and give you the credits.
Tab E said:
Try switching to custom and then official.
1) actually, if there is something wrong with just the /efs partition, it shouldn't affect the recovery
2) looks like many partitions are corrupted
4) core 2 has no bootloader or any such protection to stop flashing
5) the efs file is included in the firmware, so it is flashed with the firmware.
Conclusion - looks like multiple partions are corrupted. Try to verify this by flashing any custom recovery or rom and check the status in Odin. Even after flashing a custom recovery, the status is stock, then there are definitely many corrupted partitions. If it's so, fixing it will be very tough
Click to expand...
Click to collapse
Unfortunately nothing went right, friend. I tested everything I could. I have no other options left. All the procedures were done, I followed all your suggestions, but nothing works. There is no doubt that all partitions are corrupted. You told me it would be very difficult to fix it, so I'm not even going to try. I did as much as I could with this device. I am not qualified for this, I am just a lay person who is trying to solve a complex problem.
If you think I can do this from home with some tool, tell me. If it’s too complex I’ll take it to a maintenance specialist.
Just one more question: I don't know which ROM has been installed on this device previously and which Binary of FIRMWARE. Will the Device only accept a FIRMWARE that has exactly the '' Same '' binary? For example ... I have a ROM with the PDA binary G355MUBS0AQC2 .... Will the System only accept exactly this value so that it can be installed?
I forgot to ask this at the beginning.
Sorry, I have no knowledge of using tools or fixing a device by repairing the hardware. Using the wrong binary doesn't make a difference on these older devices.
Tab E said:
Sorry, I have no knowledge of using tools or fixing a device by repairing the hardware. Using the wrong binary doesn't make a difference on these older devices.
Click to expand...
Click to collapse
I'm greatfull for your help.
Bye, buddy.