Related
Hey folks, i recently upgraded to a galaxy S III, i was told i could get money off if i sent my galaxy S back, upon doing a factory reset of the galaxy S it no longer boots.
the logo comes up but the screen stays black, the soft keys light up when you press the home button but nothing else seems to work.
I have tried booting into recovery mode, but it just appears to do a normal boot, however, download mode does seem to work. is there a way to recover from download mode please? i have seen a few other posts about flashing or using custom roms, but i dont think my operator will accept it with a custom rom on.
Many Thanks
Matthew
Woody07 said:
Hey folks, i recently upgraded to a galaxy S III, i was told i could get money off if i sent my galaxy S back, upon doing a factory reset of the galaxy S it no longer boots.
the logo comes up but the screen stays black, the soft keys light up when you press the home button but nothing else seems to work.
I have tried booting into recovery mode, but it just appears to do a normal boot, however, download mode does seem to work. is there a way to recover from download mode please? i have seen a few other posts about flashing or using custom roms, but i dont think my operator will accept it with a custom rom on.
Many Thanks
Matthew
Click to expand...
Click to collapse
just look at your section (gt-9000) one and find flashable stock rom via ODIN, i should take just 3 minutes to recover your phone.
doing this will not void the warrenty or anything will it?
ok i have downloaded odin, and a firmware, but odin gives me the following error:
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Can't open the serial(COM) port.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
any idea what im doing wrong?
Woody07 said:
ok i have downloaded odin, and a firmware, but odin gives me the following error:
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Can't open the serial(COM) port.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
any idea what im doing wrong?
Click to expand...
Click to collapse
read http://forum.xda-developers.com/showthread.php?t=1654297
or go sammobile now search for i9000 that give you list of stock ROMs for your phone
also search on site corresponding Odin and instructions
i got the rom form there but i couldnt find odin or any instructions, there was a download link to some tool but it didnt work
Woody07 said:
i got the rom form there but i couldnt find odin or any instructions, there was a download link to some tool but it didnt work
Click to expand...
Click to collapse
link to Odin and pit file
or here to get an idea how to search for flash program
prerequisites :
-Kies to install drivers
-Android SDK is good because you need adb/ fastboot utilities
so you are to:
-install Kies then restart PC
-install Android sdk
-connect phone to PC activate usb debugging on phone previously then enter from command prompt (cmd.exe)
Code:
adb devices
if you get output/anwer that's ok your phone is connected to pc and drivers are set
-open phone in download/fastboot mode then use Odin to flash firmware from sdcard
(search youtube for a tutorial to learn how to flash by Odin)
thanks, i was told that kies interferes with the virtual port which was why it couldnt start the connection, also a lot of the tutorials i have seen refer to multiple files, but the firmwares i have dowloaded have all been just 1 tar file, does this go in the PDA section?
Woody07 said:
thanks, i was told that kies interferes with the virtual port which was why it couldnt start the connection, also a lot of the tutorials i have seen refer to multiple files, but the firmwares i have dowloaded have all been just 1 tar file, does this go in the PDA section?
Click to expand...
Click to collapse
firstly load pit file then add to PDA that tar ( in fact that tar is an archive that will unpack when you load it to PDA section )
ok i have tried to do the cmd thing but i get this :
C:\Users\Woody>adb devices
'adb' is not recognized as an internal or external command,
operable program or batch file.
when you say activate usb debugging, is that something i need to do on the fone? because the fone wont boot
Woody07 said:
ok i have tried to do the cmd thing but i get this :
C:\Users\Woody>adb devices
'adb' is not recognized as an internal or external command,
operable program or batch file.
when you say activate usb debugging, is that something i need to do on the fone? because the fone wont boot
Click to expand...
Click to collapse
yes usb debugging on phone... if not don't care about skip this step
if you installed android sdk... go in sdk folder ~ \android-sdk\platform-tools\ there is adb.exe and fastboot.exe open cmd.exe in this folder ! (or add adb to path but not now )
so open cmd.exe in adb.exe folder the simple way is to use Total Commander and navigate to adb.exe folder then from Commands menu choose Open command prompt window now you just opened cmd in adb folder
because your phone is not starting is not useful to check
adb devices
is not working now but you have to start phone in fastboot/download mode and enter from cmd
Code:
fastboot devices
by this way you check your phone was seen by PC
now it's time to flash by Odin don't forget to install Kies previously
it seems to be working, maybe all i needed was SDK. it seemed to do the update ok according to odin, but the fone its self doesnt seem to be doing anything, theres just a picture of a box and a droid on the screen
Woody07 said:
it seems to be working, maybe all i needed was SDK. it seemed to do the update ok according to odin, but the fone its self doesnt seem to be doing anything, theres just a picture of a box and a droid on the screen
Click to expand...
Click to collapse
android sdk is very important without it you have no adb interface so no chance to communicate
can you start phone ? or it restarts in recovery mode ? if so wipe everything data/cache/Dalvik-cache then restart
also try to remove battery...
ive buggered it, odin said it had done the flash but then it just kept turning its self off and on again, i left it for 5 minutes to see if it would boot but it didnt so i pulled the battery out, now theres a symbol of a fone, with a triangle and a pc, and it wont do anything
Woody07 said:
ive buggered it, odin said it had done the flash but then it just kept turning its self off and on again, i left it for 5 minutes to see if it would boot but it didnt so i pulled the battery out, now theres a symbol of a fone, with a triangle and a pc, and it wont do anything
Click to expand...
Click to collapse
can you enter recovery mode ? I suppose you never had a custom ROM on this phone ..
also post a screenshot from Odin maybe something is wrong there...
ive never had a custom rom on this fone, i pulled the battery out and put it back in, its gone back to download mode so im trying again, it came up with some errors last time but i just ignored them, ill let you know what they are when it done it....
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
http://www.freeimagehosting.net/6nes1
http://www.freeimagehosting.net/r4xax
ive cleared the cache on the fone, and tried to wipe data/factory reset and it said E:format_volume: rfs format failed on /dev/block/st.l10
Woody07 said:
Click to expand...
Click to collapse
now I see you have to flash again by Odin but un-check re-partition
also unpack firmware file and tell me what's inside
boot.bin
cache.rfs
factoryfs.rfs
modem.bin
para,.lfs
sbl.bin
zImage
My Samsung Galaxy Note Pro 12.2 WiFi (SM-P900) got soft bricked after following a rooting tutorial i found by googling How to root SM-P900. I think the problem was that i used a too old (or wrong) version of Odin, but im not sure. While i was flashing the auto-root through Odin the screen turn of. After that it showed the "firmware upgrade encountered an issue. please select recovery mode in kies and try again" standard Samsung Message. I tried to reinstall the firmware through kies but with no luck.
[SOLUTION]
1. First I downloaded the correct firmware, from Sammobile. In my case it was Nordic Contries, cause i live in Denmark. Pick the one that suite you!!
2. Then i booted my first NotePro to download mode. It took my some tries, to get it working. First hold the power button. When the "Firmware Upgrade Encountered An Issue..." message turns off, in the same second, release the power button, and now select all three (Power + Volume Down + HomeKey). (You have to release the power button and press it again to make it work (At least for me)
3. Now install the stock firmware and your tablet is now working again.
4. (Optional) If you want to root your device and it didn't work the first time. Make sure you use the same Odin as showed in the tutorial.
invalid ext4 image
madsthines said:
My Samsung Galaxy Note Pro 12.2 WiFi (SM-P900) got soft bricked after following a rooting tutorial i found by googling How to root SM-P900. I think the problem was that i used a too old (or wrong) version of Odin, but im not sure. While i was flashing the auto-root through Odin the screen turn of. After that it showed the "firmware upgrade encountered an issue. please select recovery mode in kies and try again" standard Samsung Message. I tried to reinstall the firmware through kies but with no luck.
[SOLUTION]
1. First I downloaded the correct firmware, from Sammobile. In my case it was Nordic Contries, cause i live in Denmark. Pick the one that suite you!!
2. Then i booted my first NotePro to download mode. It took my some tries, to get it working. First hold the power button. When the "Firmware Upgrade Encountered An Issue..." message turns off, in the same second, release the power button, and now select all three (Power + Volume Down + HomeKey). (You have to release the power button and press it again to make it work (At least for me)
3. Now install the stock firmware and your tablet is now working again.
4. (Optional) If you want to root your device and it didn't work the first time. Make sure you use the same Odin as showed in the tutorial.
Click to expand...
Click to collapse
i AM FACING A PROBLEM HERE, PLEASE HEALP!
First I have download "P905XXUANAE_P905OXXANA7_P905XXUANA7_HOME.tar. md5" for my Galaxy Note Pro 12.2 SM-P905. But unfortunately the file did not work for me and after all the long installation process odin says failed. and the last line on my device is
"ODIN : Invalid ext4 image"
so, after seeing that I thought the downloaded file ("P905XXUANAE_P905OXXANA7_P905XXUANA7_HOME.tar.md5 ") may be corrupted. then I download again another file from sammobile website for my note pro SM-P905 and that is "P905XXUANC3_P905BTUAND2_P905XXUANA7_HOME.tar. md5" but when tried to install by odin after long time same condition happen again. Odin says failed, and my device last line was Invalid ext4 image.
what is the problem?
how to flash SM-P905?
where is the exact proper flash file for my SM-P905?
Please Healp!!!
ornobohornish said:
i AM FACING A PROBLEM HERE, PLEASE HEALP!
First I have download "P905XXUANAE_P905OXXANA7_P905XXUANA7_HOME.tar. md5" for my Galaxy Note Pro 12.2 SM-P905. But unfortunately the file did not work for me and after all the long installation process odin says failed. and the last line on my device is
"ODIN : Invalid ext4 image"
so, after seeing that I thought the downloaded file ("P905XXUANAE_P905OXXANA7_P905XXUANA7_HOME.tar.md5 ") may be corrupted. then I download again another file from sammobile website for my note pro SM-P905 and that is "P905XXUANC3_P905BTUAND2_P905XXUANA7_HOME.tar. md5" but when tried to install by odin after long time same condition happen again. Odin says failed, and my device last line was Invalid ext4 image.
what is the problem?
how to flash SM-P905?
where is the exact proper flash file for my SM-P905?
Please Healp!!!
Click to expand...
Click to collapse
1. You may want to try using:
http://samsung-updates.com/
instead of samfirmware, if you're experiencing corrupted downloads from the latter (but it's not very probable... see pt 3)
2. At the moment I am testing new firmware revision, downloaded from samsung-updates: P905XXUAND1 for NEE region. It flashed fine. Also, for most of the time I have used P905XXUANC3 firmware for DBT region (Germany - even if I am not a German, I do not really care about csc stuff, and I got used to the fact that the newest firmwares were always released for DBT region first on my old "standard" Note 10.1). It was flashing fine, too.
3. The problem seems, however, lie not in the firmware, but in your hardware - or at least in the way it is handled by Odin or drivers. Note that *.tar.md5 archive contain md5 checksum concatenated to the very end of archive. When you're selected firmware file in Odin (in a PDA section), it probably took a longer while before the file appeared as selected - this is because meanwhile Odin is checking the checksum (and for that purpose, he has to read whole 1.5Gig file...). So: If Odin allowed you to flash the tar.md5 file - then it was NOT corrupted, otherwise it won't even be possible to start the process as of file wrong checksum!
4. THere is another possibility - that something bad happened to your pit section (it has been overwritten in result of flashing firmware for a wrong device) and your nand partition table is corrupted, which may probably result in an impossibility of flashing files or impossibility of mounting filesystems... I cannot help then, I have never faced such a problem in practice myself.
5. Pt 4, however, seems to be less possible than pt 3.
- Have you ever flashed any firmware with success?
- what do you mean by "long installation process"? A 10 minutes? An hour? Half-a-day?
- Have you been observing Odin while flashing? It's indicating which partition is being flashed atm - can you tell on which firmware part (system? hidden? cache?) did it fail?
- Try using different version of Odin (an older one, guess 3.07? not sure however - the one which has "PDA" section instead of a single-letter names)
- Try flashing from different PC
- use usb 2.0 port instead of 3.0 ones.
- try using different usb cable (I guess it'll may be the hardest thing to check because the cable seem to be quite unique )
Grateful to you...
esgie said:
1. You may want to try using:
http://samsung-updates.com/
instead of samfirmware, if you're experiencing corrupted downloads from the latter (but it's not very probable... see pt 3)
2. At the moment I am testing new firmware revision, downloaded from samsung-updates: P905XXUAND1 for NEE region. It flashed fine. Also, for most of the time I have used P905XXUANC3 firmware for DBT region (Germany - even if I am not a German, I do not really care about csc stuff, and I got used to the fact that the newest firmwares were always released for DBT region first on my old "standard" Note 10.1). It was flashing fine, too.
3. The problem seems, however, lie not in the firmware, but in your hardware - or at least in the way it is handled by Odin or drivers. Note that *.tar.md5 archive contain md5 checksum concatenated to the very end of archive. When you're selected firmware file in Odin (in a PDA section), it probably took a longer while before the file appeared as selected - this is because meanwhile Odin is checking the checksum (and for that purpose, he has to read whole 1.5Gig file...). So: If Odin allowed you to flash the tar.md5 file - then it was NOT corrupted, otherwise it won't even be possible to start the process as of file wrong checksum!
4. THere is another possibility - that something bad happened to your pit section (it has been overwritten in result of flashing firmware for a wrong device) and your nand partition table is corrupted, which may probably result in an impossibility of flashing files or impossibility of mounting filesystems... I cannot help then, I have never faced such a problem in practice myself.
5. Pt 4, however, seems to be less possible than pt 3.
- Have you ever flashed any firmware with success?
- what do you mean by "long installation process"? A 10 minutes? An hour? Half-a-day?
- Have you been observing Odin while flashing? It's indicating which partition is being flashed atm - can you tell on which firmware part (system? hidden? cache?) did it fail?
- Try using different version of Odin (an older one, guess 3.07? not sure however - the one which has "PDA" section instead of a single-letter names)
- Try flashing from different PC
- use usb 2.0 port instead of 3.0 ones.
- try using different usb cable (I guess it'll may be the hardest thing to check because the cable seem to be quite unique )
Click to expand...
Click to collapse
Dear Sir,
I am so surprised to see that somebody response me for the core of his heart! I am so pleased to realize that some body look at my problem very attentively! sir, thank you!
so,
** I have tried using different usb cable to flash
** I have tried both 3.9 or 3.7 odin
** I have tried different pc to flash
** I have used 2.0 or 3.0 both usb cable
** I have tried both kies3 or previous kies
** I am giving here the whole odin texts which
was shown
"<ID:0/008> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> P905XXUANC3_P905BTUAND2_P905XXUANA7_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/008> Odin v.3 engine (ID:8)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Get PIT for mapping..
<ID:0/008> Firmware update start..
<ID:0/008> sbl1.mbn
<ID:0/008> NAND Write Start!!
<ID:0/008> aboot.mbn
<ID:0/008> rpm.mbn
<ID:0/008> tz.mbn
<ID:0/008> sdi.mbn
<ID:0/008> NON-HLOS.bin
<ID:0/008> boot.img
<ID:0/008> recovery.img
<ID:0/008> system.img.ext4
<ID:0/008> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/008> Removed!!
<ID:0/008> Added!!"
** Long installation process means 5-7 minutes! (I think it is normal, sorry)
** yes, I have used all high end android devices and all was rooted, installed cwm recovery, custom room, so I have experience well on android I am not new to play with android operating system. even now I am also using Note 3 with Omega custom rom and working great.
** I am thinking may be the problem is about pit. and I don't know where I will find a .pit file for SM-P905. some how may be the pit of my note pro is corrupted. i don't know actually I am not a developer!
Here all you wanted to know!
Dear Sir please help me to make alive my Galaxy Note Pro!
Please!!!
screen shot!
after the failed flashing operation all the time my devices shows, i am giving a screen shot!
Downloaded 3 Firmware
Already I have downloaded 3 rom, (because I thought the firmware file was corrupted) but by studying your post I know now when ever odin accept any firmware that means the rom file is not corrupted! thanks!
P905XXUANAE_P905DBTANA6_DBT.zip
P905XXUANAE_P905OXXANA7_BTU.zip
P905XXUANC3_P905BTUAND2_BTU.zip
i have download this 3 files!
Ok, we shall try to flash firmware otherwise, using more advanced method.
Note that if ur knox isn't yet tripped - it WILL trip it, breaking your warranty (in this case it's better to send the device to service center - i suppose something's broken...). If it is tripped, you have nothing to lose...
1. Download:
http://www67.zippyshare.com/v/25492738/file.html
do not rename the file, it should be named recovery.img
2. Using this tool
http://forum.xda-developers.com/showthread.php?t=2446269
convert provided recovery.img to tar.md5 format
3. Flash it with odin (it should take a few sec to finish and it should succeed as recovery seems to flash ok on your device)
4. Enter recovery mode by holding power+home+vol up. Warning should appear about warranty and then custom recovery should appear on screen..
5. Using touch menu seek thru options and thru wipe menu format the system partition, as well as wipe/format data and cache (any errors?). Leave the device for a moment...
6. Simultanously, open one of 2+ gig tar.md5 firmwares (i recommend to choose one which you tried to flash with odin in your last trial) downloaded from sammobile with winrar or 7zip (if error about bad end of file appears ignore it) and extract system.img.ext4 somewhere...
7. Download simg2img from post #19
http://forum.xda-developers.com/showthread.php?t=2191930&page=2
and use it to convert sparse image extracted from firmware tar.md5 (system.img.ext4) to raw image (let's say output file is called system.img)
8. Copy system.img to root of empty micro sd card (fat32 or exfat formatted). Check if it has been copied correctly. Put the micro sd card into device. Reboot recovery once again
9. Advanced -> terminal/console -> use default directory ( / ), console window should open. Using simple onscreen keyboard input:
dd if=/external_sd/system.img of=/dev/block/mmcblk0p23
Be careful - if ur on P905 the last number should be "23", inputting otherwise may result in unrecoverable hard brick!!! Also, process may take a LONGER while, like 10 mins, its ok, even if there is no progress indicator. Youll know it finished when keyboard will show back again (any errors here??)
10. Reboot AGAIN to recovery, go to Mounts menu, tick system, data and cache (does tick within system work?)
11. Go to terminal as in pt 9, but this time enter:
restorecon -R /cache
restorecon -R /data
restorecon -R /system
(errors?)
12. Reboot into system and cross yer fingers
mismatch
esgie said:
Ok, we shall try to flash firmware otherwise, using more advanced method.
Note that if ur knox isn't yet tripped - it WILL trip it, breaking your warranty (in this case it's better to send the device to service center - i suppose something's broken...). If it is tripped, you have nothing to lose...
1. Download:
http://www67.zippyshare.com/v/25492738/file.html
do not rename the file, it should be named recovery.img
2. Using this tool
http://forum.xda-developers.com/showthread.php?t=2446269
convert provided recovery.img to tar.md5 format
3. Flash it with odin (it should take a few sec to finish and it should succeed as recovery seems to flash ok on your device)
4. Enter recovery mode by holding power+home+vol up. Warning should appear about warranty and then custom recovery should appear on screen..
5. Using touch menu seek thru options and thru wipe menu format the system partition, as well as wipe/format data and cache (any errors?). Leave the device for a moment...
6. Simultanously, open one of 2+ gig tar.md5 firmwares (i recommend to choose one which you tried to flash with odin in your last trial) downloaded from sammobile with winrar or 7zip (if error about bad end of file appears ignore it) and extract system.img.ext4 somewhere...
7. Download simg2img from post #19
http://forum.xda-developers.com/showthread.php?t=2191930&page=2
and use it to convert sparse image extracted from firmware tar.md5 (system.img.ext4) to raw image (let's say output file is called system.img)
8. Copy system.img to root of empty micro sd card (fat32 or exfat formatted). Check if it has been copied correctly. Put the micro sd card into device. Reboot recovery once again
9. Advanced -> terminal/console -> use default directory ( / ), console window should open. Using simple onscreen keyboard input:
dd if=/external_sd/system.img of=/dev/block/mmcblk0p23
Be careful - if ur on P905 the last number should be "23", inputting otherwise may result in unrecoverable hard brick!!! Also, process may take a LONGER while, like 10 mins, its ok, even if there is no progress indicator. Youll know it finished when keyboard will show back again (any errors here??)
10. Reboot AGAIN to recovery, go to Mounts menu, tick system, data and cache (does tick within system work?)
11. Go to terminal as in pt 9, but this time enter:
restorecon -R /cache
restorecon -R /data
restorecon -R /system
(errors?)
12. Reboot into system and cross yer fingers
Click to expand...
Click to collapse
according to your link there is no file, named "recovery.img" but the file name is "libwfdsm.so"
DAAAAMN wrong link copied.
Wait a sec, I'll upload it in a while. Until then, you may start doing steps 6-8.
EDIT:
Here u go
http://www47.zippyshare.com/v/40021725/file.html
PS: using above method (a similiar one, to be exact...), figured out on my own to be exact, I have managed to unroot and revert to fully-stock state my old Note10.1, which I was not able to flash straight via Odin at all because the port's been broken, so I was able to send it to service center without any worries (at least related to the possibility of detecting the customization by the service) The difference is that you are able to flash files via Odin - except the system - but also that my device was booting at the very beginning, and yours not. Neverthless, with appropriate modifications, it should work on P905 too - or at least explain what's the reason of your issues.
Don't want to worry you, but as of now i am considering physical NAND damage as the most possible cause of the issue... But that's a theory only. Good luck.
problem solved!
esgie said:
DAAAAMN wrong link copied.
Wait a sec, I'll upload it in a while. Until then, you may start doing steps 6-8.
EDIT:
Here u go
http://www47.zippyshare.com/v/40021725/file.html
PS: using above method (a similiar one, to be exact...), I managed to unroot and revert to fully-stock state my old Note10.1, which I was not really able to flash straight via Odin because the port's been broken. The difference is that you are able to flash files via Odin - except the system - but also that my device was booting at the very beginning, and yours not. Neverthless, with appropriate modifications, it should work on P905 too - or at least explain what's the reason of your issues.
Don't want to worry you, but as of now i am considering physical NAND damage as the most possible cause of the issue... But that's a theory only. Good luck.
Click to expand...
Click to collapse
my dear sir, don't know how but my note pro start up automatically. before some minutes on my display "unauthorized operation occur, please restart you device" was showing. so after pressing ok, device tried to restart but it was stuck on recovery mode. so i started my device manually. when I pressed reboot from recovery everything was fine and still now it is working properly!
I don't know is going gone on my device. but is a mystery for me!
one thing, after trying to fix my devices long time my note pro battery was empty and i could not able to charge because it was stuck on download mode. after searching i got a boot image.tar.md5 for SM-P905. and install that Samsung logo appear, and device started charging. and after charge a few, It was start up!
now when I am connecting it with my pc, kies says I need to update my device. but previously my device was updated the latest software. I am giving the screen shot!
what will I do now? just update via kies and star to operate my device normally?
ornobohornish said:
my dear sir, don't know how but my note pro start up automatically. before some minutes on my display "unauthorized operation occur, please restart you device" was showing. so after pressing ok, device tried to restart but it was stuck on recovery mode. so i started my device manually. when I pressed reboot from recovery everything was fine and still now it is working properly!
I don't know is going gone on my device. but is a mystery for me!
one thing, after trying to fix my devices long time my note pro battery was empty and i could not able to charge because it was stuck on download mode. after searching i got a boot image.tar.md5 for SM-P905. and install that Samsung logo appear, and device started charging. and after charge a few, It was start up!
now when I am connecting it with my pc, kies says I need to update my device. but previously my device was updated the latest software. I am giving the screen shot!
what will I do now? just update via kies and star to operate my device normally?
Click to expand...
Click to collapse
Did I understood well that after emptying the battery of the non-working device out and recharging it back again at least a little, the device started to work again? Seems like... eeee...? some voltage circulating through the mainboard was the cause?
Well, I bet it was faulty or somehow corrupted boot.img (as it was the only partition you have flashed between the time the device seemed damaged and time the device started to work again), but I am not sure what really happened.
As to the firmware update question: from the screenshot attached I can see that you are now running XXUNAE firmware. Proposed XXUNC3 is a newer one so in general it is recommended to do the update. However, we cannot be sure anyhow if your device will not react in a same way as before. However, current updates seems to be minor ones (they concentrate on security policies and not on features...) so my recommendation is to leave it alone, at least until some more important update...
ohh nooo! befor reading you reply I was tried to update my device by kies. but same thing happen here. stuck on Invalid ext4 image!
i am so tired
esgie said:
Did I understood well that after emptying the battery of the non-working device out and recharging it back again at least a little, the device started to work again? Seems like... eeee...? some voltage circulating through the mainboard was the cause?
Well, I bet it was faulty or somehow corrupted boot.img (as it was the only partition you have flashed between the time the device seemed damaged and time the device started to work again), but I am not sure what really happened.
As to the firmware update question: from the screenshot attached I can see that you are now running XXUNAE firmware. Proposed XXUNC3 is a newer one so in general it is recommended to do the update. However, we cannot be sure anyhow if your device will not react in a same way as before. However, current updates seems to be minor ones (they concentrate on security policies and not on features...) so my recommendation is to leave it alone, at least until some more important update...
Click to expand...
Click to collapse
emergency firmware recovery start on kies but also stuck on "invalid ext4 image" and my my pc says to go service center! giving two screen shot!
ornobohornish said:
emergency firmware recovery start on kies but also stuck on "invalid ext4 image" and my my pc says to go service center! giving two screen shot!
Click to expand...
Click to collapse
My recommendation: repeat the procedure Ive posted earlier. Well se what happens
It looks like some part of your nand may be physically corrupted... and unwriteable.
before closing my notebook I am just hit the "CF-Auto-Root-viennalte-viennaltexx-smp905.tar" and surprisingly saw after successfully install the root file by Odin, my device start-up again. but problem is "unfortunately Samsung keyboard stopped" sowing. so I have install google stock keyboard and without Samsung keyboard it is running properly. though it is now working properly without samsung keyboard but I am little bit unhappy with my new Note Pro, I have just purchased this 3-6-14 and to day 5-6-14. I can not even look at thish properly because after purchasing it is disturbing! many thanks dear sir!
now I will try again with your instruction!
can not find "simg2img"
esgie said:
Ok, we shall try to flash firmware otherwise, using more advanced method.
Note that if ur knox isn't yet tripped - it WILL trip it, breaking your warranty (in this case it's better to send the device to service center - i suppose something's broken...). If it is tripped, you have nothing to lose...
1. Download:
http://www67.zippyshare.com/v/25492738/file.html
do not rename the file, it should be named recovery.img
2. Using this tool
http://forum.xda-developers.com/showthread.php?t=2446269
convert provided recovery.img to tar.md5 format
3. Flash it with odin (it should take a few sec to finish and it should succeed as recovery seems to flash ok on your device)
4. Enter recovery mode by holding power+home+vol up. Warning should appear about warranty and then custom recovery should appear on screen..
5. Using touch menu seek thru options and thru wipe menu format the system partition, as well as wipe/format data and cache (any errors?). Leave the device for a moment...
6. Simultanously, open one of 2+ gig tar.md5 firmwares (i recommend to choose one which you tried to flash with odin in your last trial) downloaded from sammobile with winrar or 7zip (if error about bad end of file appears ignore it) and extract system.img.ext4 somewhere...
7. Download simg2img from post #19
http://forum.xda-developers.com/showthread.php?t=2191930&page=2
and use it to convert sparse image extracted from firmware tar.md5 (system.img.ext4) to raw image (let's say output file is called system.img)
8. Copy system.img to root of empty micro sd card (fat32 or exfat formatted). Check if it has been copied correctly. Put the micro sd card into device. Reboot recovery once again
9. Advanced -> terminal/console -> use default directory ( / ), console window should open. Using simple onscreen keyboard input:
dd if=/external_sd/system.img of=/dev/block/mmcblk0p23
Be careful - if ur on P905 the last number should be "23", inputting otherwise may result in unrecoverable hard brick!!! Also, process may take a LONGER while, like 10 mins, its ok, even if there is no progress indicator. Youll know it finished when keyboard will show back again (any errors here??)
10. Reboot AGAIN to recovery, go to Mounts menu, tick system, data and cache (does tick within system work?)
11. Go to terminal as in pt 9, but this time enter:
restorecon -R /cache
restorecon -R /data
restorecon -R /system
(errors?)
12. Reboot into system and cross yer fingers
Click to expand...
Click to collapse
dear sir,
in your link nowhere i found "simg2img"! I searched all the page number 9 but no where I found "simg2img"!!!
help please
---------- Post added at 10:28 AM ---------- Previous post was at 10:01 AM ----------
able to download simg2img from this link: http://web.djodjo.org/?a=download:android:tools:x86_linux:ext4tools
but how to use it to convert sparse image extracted from firmware tar.md5 (system.img.ext4) to raw image (let's say output file is called system.img)?
how to use simg2img?
Will this work with the SM-P900?
esgie said:
9. Advanced -> terminal/console -> use default directory ( / ), console window should open. Using simple onscreen keyboard input:
dd if=/external_sd/system.img of=/dev/block/mmcblk0p23
Be careful - if ur on P905 the last number should be "23", inputting otherwise may result in unrecoverable hard brick!
Click to expand...
Click to collapse
Hi Esgie.
I'm assuming that most of this would work for the SM-P900 (wifi only) version too? What would I use for the dd command in step 9?
Thanks for your help.
Jo Pop
ornobohornish said:
before closing my notebook I am just hit the "CF-Auto-Root-viennalte-viennaltexx-smp905.tar" and surprisingly saw after successfully install the root file by Odin, my device start-up again. but problem is "unfortunately Samsung keyboard stopped" sowing. so I have install google stock keyboard and without Samsung keyboard it is running properly. though it is now working properly without samsung keyboard but I am little bit unhappy with my new Note Pro, I have just purchased this 3-6-14 and to day 5-6-14. I can not even look at thish properly because after purchasing it is disturbing! many thanks dear sir!
now I will try again with your instruction!
Click to expand...
Click to collapse
I had same problem, install rom from greece. Some roms from sammobile and samsung firmware are giving errors, I have tested polish and british giving "odin: invalid ext4 image" error. After installing greece one everything works flawlessly, samsung keyboard also.
Solved
Had to unzip the file.
I'm trying to upgrade from 4.3 NC1 to 4.4 NE1, using the file "I535VRUDNE1_I535VZWDNE1_VZW.zip" from this thread: http://forum.xda-developers.com/showthread.php?t=2795659
- USB debugging is on
- Samsung Drivers installed
- KIES / Verizon programs not installed
- I'm in download mode
- Tried ODIN 3.04, 6, 7, 8.5 and the latest 3.09.
The second I hit the button, it fails 'instantly' with these messages. It doesn't check for md5 or anything, the file is the way I downloaded it (.zip).
Code:
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<OSM> All threads completed. (succeed 0 / failed 1)
Any help is greatly appreciated!! I'm out of guesses here. Google comes up all purple now, I've been checking online for similar problems. Anywhere from a different USB cord to a different USB port. No dice.
The device does connect, but it fails instantly - it's like it doesn't even try to flash the stock ROM. COM3 comes up as blue.
Did you unzip the file to a .tar or .tar.md5? Unzip the zip file, then select that file in pda box, it should work. I just did this same exact thing
Sent from my SCH-I535 using Tapatalk
dakota-boy said:
Did you unzip the file to a .tar or .tar.md5? Unzip the zip file, then select that file in pda box, it should work. I just did this same exact thing
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
Grrrr. I feel like an idiot. Thank you buddy, flashing now.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
[ROOT] How to root and install CWM for SAMSUNG GALAXY CORE 2 (SM-G355H) [Super Su][2015]
This tutorial is about how to root samsung galaxy core 2 with Super Su but not king user.if you were searching for the Super Su app that will be installed after rooting then you have came to right tutorial.ok now lets start
:art-1::
first of all we have to install CWM recovery in our phone to install CWM recovery follow the steps
step-1: Download Odin3-v3.04.zip and CWM_6.0.3-1.zip file,extract both zip files.
step-2: Now connect your phone and make sure debugging mode is enabled from developer option of your phone and then open Odin and click on PDA and select the recovery.tar.md5(it is inside the CWM_6.0.3.zip you will see after you extract the zip) and click on start button.
step-3:It will take little time to complete the process and your phone will reboot. now your phone will be installed will custom recovery mode i.e CWM. now move to :art-2::
(installing CWM recovery mode in you phone is not only the reason to support the rooting using a zip file but it has very useful feature inside it,actually we are installing CWM recovery mode first because the stock reovery mode doesnot supports to root phone to install SuperSu.So to support everything we are installing CWM recovery mode).
:art-2::
Now in this part we will root our phone.so follow the steps.
step-1: download the UPDATE-SuperSU-Pro-v2.46.zip and copy it to your sdcard.
step-2: switch-off your phone and then press volume-up buttom + home buttom + power buttom at once and the phone will turn on with a little red exclamation symbon on top-left side , wait for few seconds after that CWM recover mode will be open and then select install zip > choose zip from sdcard and select UPDATE-SuperSU-Pro-v2.46.zip and reboot your phone.
step-3: congrats!!! your phone is now rooted and SuperSu will be installed
IF ANY PROBLEM ARISES FEEL FREE TO ASK
IF THIS HELPS YOU GIVE ME A THANK
jasbinkarki said:
(installing CWM recovery mode in you phone is not only the reason to support the rooting using a zip file but it has very useful feature inside it,actually we are installing CWM recovery mode first because the stock reovery mode doesnot supports to root phone to install SuperSu.So to support everything we are installing CWM recovery mode).
Click to expand...
Click to collapse
You can also root the phone in stock recovery. Via stock built in binary update and update script. Or you can change the mode via update zip or application uses root access.
If U use binary update shell some process won't be able to finish just because of the SE Linux - ( enforcing,permissive ) , TWRP and latest CWM uses full SElinux
It's not working for me. Please help.
Hi, not sure what I'm doing wrong. Followed the steps you provided. Below is the log of the process. I have a Samsung Galaxy Core 2.
Edit: Realised a difference between yours in the screenshot and mine, your ID:COM = 0:[COM3] and mine is 0:[COM7]. Whether this is relevant or not, I don't know. How to fix it, I don't know.
Code:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> recovery.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Complete(Write) operation failed.
<ID:0/007> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
Thanks in advance for help.
P.S: Sorry in advance if the problem was stupid...
Run for galaxy core 2 duos ?
Does this work for Samsung Core II G355M ?
same happened to me
minor help for newbies
After complete day tiring research on this thread. i found a solution to problem faced by all.
in part 1 after step 1 just switch off your phone and reboot it using power button + volume down + menu button.
then continue it using volume up button.
then connect it to pc.
and complete above procedure from step 2 itself.
it worked for me.
---------- Post added at 09:10 PM ---------- Previous post was at 09:05 PM ----------
ccnh95 said:
Run for galaxy core 2 duos ?
Click to expand...
Click to collapse
Yes it works. i have tested it. go for it. any help needed then ask
The easiest and working root
Download this : http://forum.xda-developers.com/attachment.php?attachmentid=2936385&d=1410667995
Put it on your SD card in your phone
Turn off your phone
Hold VOLUME UP, POWER BUTTON AND START BUTTON at the same time!
A "boot menu" will pop up, and select "Apply update from external storage" and find the file I listed above and select it
Wait...and after a while your phone will be rooted.
Enjoy
Hi,
Just tried the same u did and suffers failure , but u can prevent this by connecting your phone with the downloading mode via Odin( for that u have to do. ( volume down + home + power button ). Now do the same step as u did earlier... U will get pass
To , [unicornsbreakwind ]
jasbinkarki said:
[ROOT] How to root and install CWM for SAMSUNG GALAXY CORE 2 (SM-G355H) [Super Su][2015]
This tutorial is about how to root samsung galaxy core 2 with Super Su but not king user.if you were searching for the Super Su app that will be installed after rooting then you have came to right tutorial.ok now lets start
:art-1::
first of all we have to install CWM recovery in our phone to install CWM recovery follow the steps
step-1: Download Odin3-v3.04.zip and CWM_6.0.3-1.zip file,extract both zip files.
step-2: Now connect your phone and make sure debugging mode is enabled from developer option of your phone and then open Odin and click on PDA and select the recovery.tar.md5(it is inside the CWM_6.0.3.zip you will see after you extract the zip) and click on start button.
step-3:It will take little time to complete the process and your phone will reboot. now your phone will be installed will custom recovery mode i.e CWM. now move to :art-2::
(installing CWM recovery mode in you phone is not only the reason to support the rooting using a zip file but it has very useful feature inside it,actually we are installing CWM recovery mode first because the stock reovery mode doesnot supports to root phone to install SuperSu.So to support everything we are installing CWM recovery mode).
:art-2::
Now in this part we will root our phone.so follow the steps.
step-1: download the UPDATE-SuperSU-Pro-v2.46.zip and copy it to your sdcard.
step-2: switch-off your phone and then press volume-up buttom + home buttom + power buttom at once and the phone will turn on with a little red exclamation symbon on top-left side , wait for few seconds after that CWM recover mode will be open and then select install zip > choose zip from sdcard and select UPDATE-SuperSU-Pro-v2.46.zip and reboot your phone.
step-3: congrats!!! your phone is now rooted and SuperSu will be installed
IF ANY PROBLEM ARISES FEEL FREE TO ASK
IF THIS HELPS YOU GIVE ME A THANK
Click to expand...
Click to collapse
I'm stuck in part 2, second step. When I choose that zip file it gives me this error:
E: Can't open /tmp/sideload/package.zip (STATUS: 255)
Then mobile restarts. But phone is not rooted!!!
I tried kingoroot zip too but it gives the same error.
Help please.
Thanks!
jasbinkarki said:
[ROOT] How to root and install CWM for SAMSUNG GALAXY CORE 2 (SM-G355H) [Super Su][2015]
This tutorial is about how to root samsung galaxy core 2 with Super Su but not king user.if you were searching for the Super Su app that will be installed after rooting then you have came to right tutorial.ok now lets start
:art-1::
first of all we have to install CWM recovery in our phone to install CWM recovery follow the steps
step-1: Download Odin3-v3.04.zip and CWM_6.0.3-1.zip file,extract both zip files.
step-2: Now connect your phone and make sure debugging mode is enabled from developer option of your phone and then open Odin and click on PDA and select the recovery.tar.md5(it is inside the CWM_6.0.3.zip you will see after you extract the zip) and click on start button.
step-3:It will take little time to complete the process and your phone will reboot. now your phone will be installed will custom recovery mode i.e CWM. now move to :art-2::
(installing CWM recovery mode in you phone is not only the reason to support the rooting using a zip file but it has very useful feature inside it,actually we are installing CWM recovery mode first because the stock reovery mode doesnot supports to root phone to install SuperSu.So to support everything we are installing CWM recovery mode).
:art-2::
Now in this part we will root our phone.so follow the steps.
step-1: download the UPDATE-SuperSU-Pro-v2.46.zip and copy it to your sdcard.
step-2: switch-off your phone and then press volume-up buttom + home buttom + power buttom at once and the phone will turn on with a little red exclamation symbon on top-left side , wait for few seconds after that CWM recover mode will be open and then select install zip > choose zip from sdcard and select UPDATE-SuperSU-Pro-v2.46.zip and reboot your phone.
step-3: congrats!!! your phone is now rooted and SuperSu will be installed
IF ANY PROBLEM ARISES FEEL FREE TO ASK
IF THIS HELPS YOU GIVE ME A THANK
Click to expand...
Click to collapse
Thanks for this. I'll be testing it out on my gf's phone this weekend. Hope to extend the battery life and give the phone some much needed new life.
com.android.phone
i have a samsung galaxy core 2 , model: SM-G355H/DS, SSN: -G355H/DSGSMH...it is powered by "android"....currently my phone has prompted me with a message: "Unfortunately, the process com.android.phone has stopped."......how do I activate it to start working again....i cannot access any of the information on the phone.....PLEASE HELP!....
mamadenniec said:
i have a samsung galaxy core 2 , model: SM-G355H/DS, SSN: -G355H/DSGSMH...it is powered by "android"....currently my phone has prompted me with a message: "Unfortunately, the process com.android.phone has stopped."......how do I activate it to start working again....i cannot access any of the information on the phone.....PLEASE HELP!....
Click to expand...
Click to collapse
I recommend u to do a factory reset! Make sure u backup ur data!
Press and hold: vol up+home buttom+power to go into recovery n wipe cache n factory reset this will solve ur problem
There is an easier way to root core 2
I will post soon
---------- Post added at 09:47 PM ---------- Previous post was at 09:44 PM ----------
I have a soution for the rooting problem. U have to do it with Kingroot zip file.
Requirements:
1. Galaxy Core 2
2. Custom or Stock Recovery(which they have lol)
3. Kingroot zip file
REMOVE SPACES FROM THE LINK PLZ
Download Kingroot zip file here in XDA thread: http: //dl-1.va.us .xda-developers. com /2/9/3/6/3/8/5/UPDATE-Kinguser-3.4.0.zip?key=-LqV9wsG96QMaSvqnl7jsg&ts=1462290490
Method:
1. Place the Kingroot zip file in your external SD card
2. Boot into recovery ( Power Down + Home Button + Power)
3. Select "Apply update from sd card" and choose Kingroot zip file
Wait for flashing and CONGRATS your Core 2 is Rooted
LIKE ME IT WILL HELP ME BECOME MORE HELPFUL
TechSTER™
---------- Post added at 09:53 PM ---------- Previous post was at 09:47 PM ----------
I have a soution for the rooting problem. U have to do it with Kingroot zip file.
Requirements:
1. Galaxy Core 2
2. Custom or Stock Recovery(which they have lol)
3. Kingroot zip file
REMOVE SPACES FROM THE LINK PLZ
Download Kingroot zip file here in XDA thread: http: //dl-1.va.us .xda-developers. com /2/9/3/6/3/8/5/UPDATE-Kinguser-3.4.0.zip?key=-LqV9wsG96QMaSvqnl7jsg&ts=1462290490
Method:
1. Place the Kingroot zip file in your external SD card
2. Boot into recovery ( Power Down + Home Button + Power)
3. Select "Apply update from sd card" and choose Kingroot zip file
Wait for flashing and CONGRATS your Core 2 is Rooted
LIKE ME IT WILL HELP ME BECOME MORE HELPFUL
TechSTER™
Unable to root, as when trying SSU, it just reboots with an error, which I cannot even read.
try vroot 100% working if not then change my name
Sent from my SM-G900H using XDA Premium 4 mobile app
FruitNuggets said:
Thanks for this. I'll be testing it out on my gf's phone this weekend. Hope to extend the battery life and give the phone some much needed new life.
Click to expand...
Click to collapse
Please:i need to know how to root my sm-g355h without a pc and external sd card
problem in rooting!
hi
i am a beginner and when i tried rooting my galaxy core 2 phone according to your steps i happened to see these messages..
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> recovery.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Complete(Write) operation failed.
<ID:0/004> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
it says operation failed and succeed 0
what may be the problem
please help me
unicornsbreakwind said:
Hi, not sure what I'm doing wrong. Followed the steps you provided. Below is the log of the process. I have a Samsung Galaxy Core 2.
Edit: Realised a difference between yours in the screenshot and mine, your ID:COM = 0:[COM3] and mine is 0:[COM7]. Whether this is relevant or not, I don't know. How to fix it, I don't know.
Code:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> recovery.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Complete(Write) operation failed.
<ID:0/007> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
Thanks in advance for help.
P.S: Sorry in advance if the problem was stupid...
Click to expand...
Click to collapse
did u people find solution to the above specified problem??
Thanks a lot. My phone was G355HXXU0AOE4 firmware and only your update v2.46 could root it.
Repair Firmware
This site contains
1. Full repair firmware
2. Combination firmware
3. Fix dm verity
4. Root instructions and unpatched boot images
A20
https://www.full-repair-firmware.com/search?q=A20
A20e
https://www.full-repair-firmware.com/search?q=A20e
A20s
https://www.full-repair-firmware.com/search?q=A20s
All models
https://www.needromarab.com/1/122/SAMSUNG
physwizz collection
A collection of guides, kernels and ROMs. Guides Complete Guide to the A20 GSIs for the A20 Quick Root and TWRP for the A20 Making my First Kernel for the A20 A20 Rooting Guide Making Your Own ROM Making Your Own Version of QwizzROM-a20...
forum.xda-developers.com
Information and Guides from the above website
1. Full repair firmware
Problems Solved This Firmware
Update android version.
Fix Camera.
Fix Invalid IMEI And Baseband.
Fix Wifi and Bluetooth.
Fix custom binary blocked by frp lock.
Fix standing on the logo.
Fix storage space.
Fix slow device.
Fix sensors.
Solve the problem of high temperature.
Fix applications stop working.
Fix restarting the device.
delete pattern or password.
Fix hide Imei.
Fix baseband unknown.
Remove root.
wipe data.
wipe cache.
hard reset.
Fix sound problems.
Firmware Galaxy A20:
Important Notice: Please Inform us in case of any dead link, Or any flashing error you get when using these files, So we can check and replace, Send an Facebook with details to: Contact us
Warning: This firmware A20*** use to repair software smartphone problem and it will clean everything on your smartphone so you have to backup your data, don’t try to flash your device with this firmware if it work prefect. if you use pit file please make sure 16GB or 8GB or 32GB, Because the 8GB Pit file don’t work with 16GB or 32GB and the same for 16GB or 32GB Pit File make sure you use the Correct ROM for your device.
To flash your Samsung galaxy smartphone, you need Odin software made available to the Samsung Galaxy users for flashing a range of things including firmware, custom recovery, CF-Auto-Root and more. Odin software performs a clean install that means; it removes the old firmware and flashes a new one,Backup your data before start flashing you smartphone.
Here you find all the latest android os for the Galaxy A20 SM-A205GN, if you want to flash your device with the newest Samsung software. Before downloading, make sure you check your exact model number. You can download the most recent Galaxy A20 firmwares for free, or check out our cheap but fast download options.
Important tools to work flash android update:
Drivers: USB Samsung Galaxy
Odin
How To Flash Galaxy A20
Extract the Firmware A20*** By 7z or winrar You should get 5 files (BL-AP-CP-CSC-Home CSC).
Download Odin.
Add each file to it's respective field in Odin v3.13.3. Use CSC_** if you want to do a clean flash (lost data) or HOME_CSC_** if you want to keep your apps and data (unformat).
Reboot Phone in Download Mode (press Volume Down + Volume Up and connect the Type-C USB cable to device).
wait until you get a blue sign in Odin.
Add the files to BL - AP - CP - CSC
Do NOT tick any extra boxes. The only options to be ticked are F.Reset Time and Auto-Reboot.
Click the start button, wait for Odin to say 'PASS' in a GREEN box. Once the flash is complete, your phone will reboot, and you can disconnect your phone from the PC.
Now you have the latest android version
2. Combination firmware
Samsung Galaxy A20 Combination Firmware is a stable program for complex and sophisticated tasks. You can flash the device using this developer program to conduct a test that shows you the results of the phone check. It is really important that this particular firmware Samsung A20*** can:
Bypass or remove Google Account Protection
Bypass or remove Samsung Account Protection
Remove RMM Protection
Repair IMEI
Write Cert
Fix Boot loop
Enable USB Debugging
Unlock Network
Important tools:
Drives USB Galaxy
Odin Tool
How To Flash Combination File:
1-Extract the Combination By 7z or WinRAR You should get 1 file .
2-Boot your phone to Download Mode ( Volume Down + Volume Up and connect the Type-C USB cable to device ).
3-Open Odin Tool and wait to get a blue sign in Odin.
4-Add the file Combination to AP.
5-Do NOT tick any extra boxes.
6-Click the start button, wait for Odin to say 'PASS'.
3. Fix dm verity
What is the DRK or DM-Verity for device a20***
DRK Is an acronym DEVICE ROOT KEY It is an encrypted number for the device and It is positioned when manufacturing by Samsung.
When we turn on the device, the device checks this encrypted number to check if the system is original or not.
Fix DM-Verity (DRK) Galaxy A20
Reasons for the appearance of DRK problem
This problem occurs when we flash the ROM that does not match the device in terms of the version Bashband, Or when flashing a custom ROM by a custom recovery (TWRP) Or by the stock rom For example, Stock ROM but a language has been added to it In this case, the encrypted number will check the status of the system When the system does not match the number, this error will occur, A red write will appear in the recovery mode (dm-verity Verification failed).
Problems resulting from DRK / DM-Verity
-Stop at the Samsung logo.
-Automatic boot to the recovery mode.
-Restart the device.
Warning before starting
-Charge the device battery to a level above 50%.
-Download the files according to the type of device and must not differ any characters.
-Agree that all steps are at your own risk.
Important tools to fix drk
Drives USB Galaxy
Patched Odin Tool 3.13.1
How To Flash Fix DRK A20***:
1-Download Firmware and Extract by 7z or WinRAR.
2-When extracting files, rename the file AP_A205U1 Then delete the extension .md5
3-Open AP File then Extract the system file.
4-Now create an archive of the system file that we extracted previously by a program 7z.
5-Choose the file format .tar Then, create the file.
6-Download Fix Drk file.
7-Now we have two files (DRK File,SYSTEM.tar File).
8-Boot your phone to Download Mode(press Volume Down + Volume Up and connect the Type-C USB cable to device).
9-Open Odin Tool and wait to get a blue sign in Odin.
10-Add the DRK File to BL.
11-Do NOT tick any extra boxes.
12-Click the start button, wait for Odin to say 'PASS'.
13-Boot your phone to Download Mode again.
14-From odin tool Add the SYSTEM File to AP.
15-Click the start button, wait for Odin to say 'PASS'.
16-Then the device will work without problems.
17-In case of any problems please Contact us.
4. Root instructions and unpatched boot images
Root features:
1-Modify or delete files or applications of the operating system.
2-Run programs that require root permissions.
3-Change the basic fonts within the Android system.
4-Move applications from device memory to external memory.
5-Installation of Custom rom.
6-Fix errors DRK and DM-Verity.
Cons of the root:
1-Loss of phone warranty.
2-Some applications do not work due to root (bluestacks root / dr fone root).
3-Stand on the company logo as a result of misuse.
4-The operating system crashed due to deletion or modification of important system files.
important warning:
Installation and use of the root android is entirely at your own risk and we do not take any responsibility for device failure.
In older versions of the Android system such as Jelly Bean and KitKat was using apps (kingroot / kingo root / framaroot / iroot / root king / towelroot) To get root permissions either in new versions such as Lollipop, Marshmallow, Nougat, Pie and future versions of the Android system, these applications do not work.
What is the difference between SuperSU and Magisk
VS
The main difference between Magisk and SuperSU is how the root works on Android. Based on what the user wants to do.
We will first talk about supersu root how to get the root where it installs itself within the system files It changes the system files and adds new files to the system partition on the phone, but with the enhancement of Google to protect Android it has become difficult to do so that the amendment to the partition of the Android system to send an alert to applications that are trying to detect the presence of root.
Google SafetyNet monitors the operating system from any manipulation, and when it detects any manipulation in the Android operating system, most applications will not work and will not send you OTA updates.
What about Magisk is one of the most important features that does not touch system files, but modifies the boot partition instead so that it can trick safetyNet service and show that everything is normal and allows Magisk Manager to fully control the root settings.
Notes before root process
Charge the battery well before use.
Use the original USB cable that came with the device.
Use the laptop at work to avoid electricity problems.
You should focus well to protect the binary of your device.
The following protections must be disabled (FRP - OEM - RMM/KG) Follow the following article to learn How to Disbled FRP and OEM for device Samsung Galaxy.
Files required for root work
-Samsung Driver USB
-Odin Tool
-Magisk Manager
-Root A20xxx file
How To Root Galaxy A20xxx android Pie 9.0
1-Download Drivers, Odin and A20xxx Root files for Pie 9.0 Depending on your device version.
2-Install the drivers on your device.
3-Install the Magisk Manager app on your Phone.
4-Transfer the boot file to the device's memory after extracting the file.
5-The entire file name will become boot.img.
5-Open the Magisk Manager app.
6-Open the application settings and from the option Patched Boot Output Formate We choose .img.tar.
7-We return to the main interface of the application And we click on install a new window will appear we choose install too.
8-A new window will appear titled Select Patched We choose the second option Patch Boot Image File.
9-Locate the boot file and give the application access rights.
10-Patch Boot will take some time about 5 minutes.
11-After the process is finished navigate to the MagiskManager folder or Download folder you will see the file named patched_boot.img.tar (mroot A20xxx).
12-Copy the file to your computer and open the Odin tool.
13-Of the box AP We choose the file (patched_boot.img.tar).
14-Boot your device into download mode press Volume Down + Volume Up and connect the USB cable.
15-Press Start to flash the boot file.
16-After the flash is done, you will be asked to work factory reset.
17-It will take about 10 minutes to boot the Android system.
18-After the boot is complete we install the Magisk Manager application.
19-After installing the app you need to reboot your device with Magisk to get root permissions, Open the Magisk app and from the options at the top of the app we choose Modules and then we press the three points above and we choose Reboot.
20-You can check for root access through the root checker app.
21-In case you encounter any problems please feel free to contact us
22-If you want to unroot or revert to the offical firmware, you can read the following article: Full Firmware For Device Samsung Galaxy
If you find this useful please comment.
Can you please provide me the unpatched boot file for A205fxxs6ata2 so i can unlock my phone and install twrp
Maybeyou said:
Can you please provide me the unpatched boot file for A205fxxs6ata2 so i can unlock my phone and install twrp
Click to expand...
Click to collapse
Use the patched one from here
https://forum.xda-developers.com/galaxy-a20/how-to/root-a205xx-october-patchu3-t4005335
Thank you very much I will try it and post results
didn't work, odin says fail
Maybeyou said:
didn't work, odin says fail
Click to expand...
Click to collapse
Have you unlocked bootloader on developer options
Instructions here
https://forum.xda-developers.com/galaxy-a20/how-to/root-samsung-galaxy-a20-rooting-guide-t3954872
Phone: A20s - a207f
Phone: A20s - a207f
I used A207FXXS2ASL3 from full-repair-firmware.com/search?q=A20s
Issue
Secure check fail: boot.img
Skybluescreen: Security Error: This phone has been flash with unauthorized software & is locked. Call your mobile operator blah blah blah.
I could still use my phone if I flash the original AP(BL_A207FXXS2ASL3_CL17088050_QB28240904_REV00_user_low_ship_MULTI_CERT.tar.md5)(3gb+) using ODIN
Flashing the boot.tar(11.8mb) that comes from (AP->boot.img.lz4>boot.img>from magisk_patched>compressed it to tar) gives me the issue.
Anyone knows how can I bypass the "Skybluescreen: Security Error" ?
silksong23 said:
Phone: A20s - a207f
I used A207FXXS2ASL3 from full-repair-firmware.com/search?q=A20s
Issue
Secure check fail: boot.img
Skybluescreen: Security Error: This phone has been flash with unauthorized software & is locked. Call your mobile operator blah blah blah.
I could still use my phone if I flash the original AP(BL_A207FXXS2ASL3_CL17088050_QB28240904_REV00_user_low_ship_MULTI_CERT.tar.md5)(3gb+) using ODIN
Flashing the boot.tar(11.8mb) that comes from (AP->boot.img.lz4>boot.img>from magisk_patched>compressed it to tar) gives me the issue.
Anyone knows how can I bypass the "Skybluescreen: Security Error" ?
Click to expand...
Click to collapse
As far as I know, no one has been able to root the a207
Has anyone had any luck flashing the combination firmware to SM-A205YN? Using Odin 3.14.1 patched I get error on phone screen "Please get the approval to use factory binaries (PIT)"
Odin log is:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin engine v(ID:3.1401)..
<ID:0/004> File analysis..
<ID:0/004> Total Binary size: 2294 M
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004>
<ID:0/004> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Cheers
btw my baseband version is A205YNDVU2ASF2 if that makes a difference
magnafunk said:
Has anyone had any luck flashing the combination firmware to SM-A205YN? Using Odin 3.14.1 patched I get error on phone screen "Please get the approval to use factory binaries (PIT)"
Odin log is:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin engine v(ID:3.1401)..
<ID:0/004> File analysis..
<ID:0/004> Total Binary size: 2294 M
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004>
<ID:0/004> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Cheers
btw my baseband version is A205YNDVU2ASF2 if that makes a difference
Click to expand...
Click to collapse
Have you unlocked bootloader and ticked usb debugging
Yep sure have
magnafunk said:
Yep sure have
Click to expand...
Click to collapse
I also have 205yn
I used full firmware no probs
What are you trying to do?
I can install full firmware but not combination. I want to network unlock. Telstra are basically not answering phones at the moment and the online services don't work if Knox is tripped
magnafunk said:
I can install full firmware but not combination. I want to network unlock. Telstra are basically not answering phones at the moment and the online services don't work if Knox is tripped
Click to expand...
Click to collapse
All Telstra operations are locked down in India.,
Combination files
physwizz said:
Repair Firmware
This site contains
1. Full repair firmware
2. Combination firmware
3. Fix dm verity
4. Root instructions and unpatched boot images
A20
https://www.full-repair-firmware.com/search?q=A20
A20e
https://www.full-repair-firmware.com/search?q=A20e
A20s
https://www.full-repair-firmware.com/search?q=A20s
All models
https://www.needromarab.com/1/122/SAMSUNG
Click to expand...
Click to collapse
Has anyone tried the combination files from an has had any luck getting OEM unlock to work ?
Combination files
peter couniaz said:
Has anyone tried the combination files from an has had any luck getting OEM unlock to work ?
Click to expand...
Click to collapse
Well I guess no one has an answer for this question . Or with the locked Bootloader it just wouldn't flash I'll give it a shot . An see .
peter couniaz said:
Well I guess no one has an answer for this question . Or with the locked Bootloader it just wouldn't flash I'll give it a shot . An see .
Click to expand...
Click to collapse
If boot is locked, you can't flash any firmware except what is made for your model.
peter couniaz said:
Well I guess no one has an answer for this question . Or with the locked Bootloader it just wouldn't flash I'll give it a shot . An see .
Click to expand...
Click to collapse
long press volume up to unlock bootloader from blue screen