Database Info

[Q] Help soft bricked?

So here's what happened. I tried to install CWM 6.0.1.2 using EZ Recovery and it rebooted into ODIN with the words, could not do normal boot, in red. When I reboot it, it would just go back to the ODIN screen, so I tried to use the root 66 method. At first, it would get to system.img.ext4, but the green bar would barely move and be stuck there for 30 minutes. I would try again by taking out the USB cord, rebooting phone (maybe bad idea?). I did it again and it would be stuck there. I tried different USB ports on my laptop. Some will get to system.img and be stuck or get to recovery.img and say fail. Is my phone hard bricked or is there something else I can do? Thanks!

I also tried it on a different computer and it gets stuck on boot.img instead. Any help would be greatly appreciated!

It seems like using the older version of Odin gave me more consistent results. I now always get to system.img before it fails. The green bar gets 1/3 of the way then says failed.
<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> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> boot.img
<ID:0/004> NAND Write Start!!
<ID:0/004> recovery.img
<ID:0/004> system.img.ext4
<ID:0/004> Complete(Write) operation failed.
<ID:0/004> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
Is there anyway to get it to be successful?

[Q] Galaxy Exhilarate stuck during emergency recovery

First off, I am a complete Android/PC noob (have used solely apple products until this phone, and an Acer aspire comp. i got 2 weeks ago).
I have been using the Exhilarate with android GB, and wanted to upgrade to ICS. I downloaded Samsung Kies, backed up my phone, and began the firmware upgrade, however once the progress reached 70%-80%, the device came unplugged. after restarting the phone, it is stuck on a screen that says:
upper left corner of screen:
Odin Mode
Product Name:SGH-I577
Custom Binary Download: YES(2 counts)
Current Binary: Custom
Center of screen:
Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again.
When I reconnect and attempt to do the emergency firmware recovery using kies, it completes the downloading of the file for firmware emergency recovery, but once it moves on to "proceed to firmware emergency recovery", it stops working (the progress bar is stuck at 0%)
After waiting a little while, the emergency recovery closes, and a message shows saying:
Notice-F PC failed to recognize the mobile phone. Please follow the guide shown below to try again
I gave up on kies, and did some searching of my own. I downloaded the latest version of Odin, as well as the Clockworkmod-Blaze-4G.tar. I made sure there was nothing Kies-related running on my computer, opened up Odin, loaded the clockwork .tar, turned the phone on into download mode (it says Warning!, asks if I want to go into download mode, and then returns to the Odin Mode screen once I say yes). the device is shown as added to odin, I clicked start, and it seemed to be working, and then a big red FAIL appeared in the top left box, and the message box said:
<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> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> recovery.img
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I have tried re-installing drivers, different versions of the .tar file (i think they are diff. versions, but not completely sure) rebooting the device many many times, among other things. If anyone has any idea of where to go from here, i would be EXTREMELY grateful.
thank you guys

One more thing
OP here still:
I tried again with a different version of Odin. this time it failed once again, but got a bit further. (everything else was the same):
<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> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> recovery.img
<ID:0/004> NAND Write Start!!
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
also, I have only checked the Auto reboot box in odin. All others were left blank

I am having a very similar problem with my SGS3 - were you able to solve your problem? If so, can you share how you did?

Galaxy Note 10.1 GT-N8000 Stuck in Bootloop, Can't Access Recovery

Hello all,
My tablet note 10.1 N8000 (3G, Wi-Fi, 16 GB) suddenly got stuck in bootloop. I was not trying to flash anything when it did so, nor did I flashed anything recently before the bootloop (although it seemed to constantly freeze before the bootloop when trying to switch between my two whatsapp accounts that I have using Titanium Backup which allows creating more than one account in all apps).
I did however root the device when I bought it in 2012 and it was the only time I did so, and I still have USB debugging mode on.
The device would bootloop in the first Samsung logo most of the time, but on rare occasions it would move to the second animated logo and get stuck repeating the animation forever.
I can only access Odin Download mode, but cannot access recovery mode (when I try to do so, it shows the first Samsung logo, then attempts to go into recovery but only shows a lit black screen then reboots).
Here are the steps I did (might help some of you, but unfortunately didn't help me):
1) I tried flashing a custom recovery (CMW, Philz touch, TWRP, and stock recovery) through Odin (Odin 3 version v3.10.6):
- Put the .tar file in AP slot then put device in download mode (power key + volume down), then plug device into my computer.
- Check only auto restart and F. time reset.
- Here's what it says after flashing:
Code:
<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> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Removed!!
<ID:0/003> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
2) I tried flashing stock rom through Odin:
(Roms I tried: N8000XXCMF1, N8000XXUDOF1, N8000XWALG7, N8000XXCMA2, N8000XXUDOF1)
- I put the .tar.md5 file in AP and follow same steps above, here's what Odin says after flashing:
Code:
<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> tz.img
<ID:0/003> NAND Write Start!!
<ID:0/003> sboot.bin
<ID:0/003> system.img
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> cache.img
<ID:0/003> hidden.img
<ID:0/003> modem.bin
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Removed!!
<ID:0/003> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
3) I tried following the post here:
http://forum.xda-developers.com/galaxy-note-10-1/general/n8000-stuck-samsung-logo-t3212923
I followed everything until the part where I have to access recovery (because I could not access recovery still to flash rom from recovery). Here's what it says in Odin after it's done:
Code:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9300_Repair_efs.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> 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> SingleDownload.
<ID:0/003> recovery.img
<ID:0/003> NAND Write Start!!
<ID:0/003> efs.img
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Removed!!
<ID:0/003> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
But again it did not work even though it always says "PASS"! And I also tried flashing stock rom after trying this method through Odin, shows success but still stuck in bootloop.
I don't know what else to try really. I will not take it to support to fix it, either I fix it myself or use it as a cutting board.
If anyone has any ideas please reply. I'm sure there are more things to try.
EDIT:
- Is there a way to clear cache without accessing recovery (since I can't access it)? Lots of people say it worked after clearing cache.
- Is Nand erase all an option? I wish someone would explain it in details instead of telling me not to do it without saying exactly why.
- Could the problem be in hardware? How can I know if so?

NaND ERASE WILL KILL THE PRODUCT .

JJEgan said:
NaND ERASE WILL KILL THE PRODUCT .
Click to expand...
Click to collapse
So you mean that it will erase everything even the Odin download mode and the Samsung logo? Why would they include this option then? I don't see any practical use of it :/

No help?

RHAddict said:
So you mean that it will erase everything even the Odin download mode and the Samsung logo? Why would they include this option then? I don't see any practical use of it :/
Click to expand...
Click to collapse
Odin is a tool that we are able to borrow .
You could try recovery via KIES .

RHAddict said:
No help?
Click to expand...
Click to collapse
HI RHAddict,
It happened to my Note GT-N8000, if a Hardware failure. If you send to SAMSUNG service center it will cost u around US$ 200 for motherboard replacement. But i manage to find a mobile service center, the technician said it only 1 of the chip in motherboard out of service. I got my tablet fixed just US$ 50-60. Now is working as is it before.
TQ

My Samsung 8010 has just gone exactly the same way. Cannot enter recovery mode, just get a blank lit screen for a second then goes back into a reboot cycle and never gets past the Samsung logo. Did you get anywhere with fixing it, or have you given up? Was thinking of taking mine to a service centre, but probably not worth it?

Galaxy S7 G930W8 won't start, won't take stock ROM nor TWRP

Hello all,
I have a Samsung Galaxy S7, from Rogers but unlocked, version SM-G930W8 that I bought second hand.
Phone was rooted, I factory reset it to prepare it for my wife, then installed apps and moved data and everything.
Turned the phone off and put it aside, the next day I bought a new Nano SIM, turned it ON and I got "Custom binary blocked by FRP lock".
I downloaded G930W8VLU1APG1_G930W8OYA1APG1_XAC tried flashing via ODIN and got this:
<ID:0/004> Odin engine v(ID:3.1203)..
<ID:0/004> File analysis..
<ID:0/004> skip file list for home binary
<ID:0/004> param.bin
<ID:0/004> Home Binary Download
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> sboot.bin
<ID:0/004> cm.bin
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
On the phone I had: SW REV. CHECK FAIL. DEVICE: 2. BINARY: 1
Tried: twrp-3.0.2-4-herolte.img.tar with Odin
It goes all the way through but fails at the end with this message:
<ID:0/004> Odin engine v(ID:3.1203)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> recovery.img
<ID:0/004> RQT_CLOSE !!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
On the phone I had: Custom Binary(Recovery) Blocked by FRP Lock
Also I have tried multiple computers, multiple cables, multiple versions of ODIN, ...
Now the phone is stuck at the Samsung screen and won’t turn on or off, until the battery dies.
Tried Smart Switch but it asks for the serial number, which I do not have. (There is just IMEI on the back of the phone)
Not sure but I think somehow after the factory reset the OEM Unlock got disabled.
Any help is greatly appreciated.

Did you ever figure this out? I'm facing the same thing and hoping my phone isn't bricked.
https://forum.xda-developers.com/galaxy-s7/help/potentially-bricked-s7-flat-custom-t3583502

This will fix and let you flash.
1) Open Odin, place all the necessary files into their slots.
2) Go the the options tab, make sure "Auto Reboot" IS ticked.
3) Press "start", but as soon as you do, hold down Vol down+Home+Power on your phone.
Odin will fail and your phone will reboot into download mode again.
Now press "Start" in Odin again, and your phone should flash without a problem.
This might take a few attempts to get right, but I hope it helps.

[Guide] Quick root and TWRP for the Galaxy A20 (Android 9,10 & 11)

WARNING: Rooting your phone may be dangerous.
Rooting a device may void the warranty on the device. It may also make the device unstable or if not done properly, may completely brick the device. XDA-Developers or the author does not take any responsibility for your device. Root at your own risk and only if you understand what you are doing!
This method should root your Samsung Galaxy A20 and install TWRP (all models except SM-A205U).
For Android 10 go here
https://forum.xda-developers.com/galaxy-a20/how-to/android-10-q-guide-a20-t4095589
For a20e (a202) go here.
https://forum.xda-developers.com/ga...overy-twrp-3-4-0-0-galaxy-a20e-a202f-t4141767
Find your build number in software information.
The number will help you decide on the recovery to download.
A205GUBS5ATA1 means S5
Many thanks to @Agrim720
@Gollo99
@crazo7924
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

1. On phone developer options in settings unlock OEM and enable usb debugging. Connect phone to PC
2. Reboot into download mode by holding down both Vol up and Vol down then press vol up to continue (you may need to long press volume up to unlock the bootloader for some devices)
3. Use Odin to flash recovery.tar into the AP slot.
Android 9 U2 recovery: https://mega.nz/#F!o1UBiCwJ!MNb4kNtLyjLlDSUlWGRRKQ
Andoid 9 U3 recovery: https://mega.nz/#F!IoVlUKqD!CsF24n9_yxuMcR3TaCRZkQ
Android 9 U4 recovery (dark mode with MTP for U4, S4 and higher) : https://mega.nz/#F!4osxTSza!8InrMR8p0Ph_FazeEpfskw
Android 9 U4 Recovery (light mode for U4, S4 or higher) : https://mega.nz/folder/I0FWAYhZ#7Txl_DqV5_QbM7KeZF1UiA
Android Q recovery v3: https://mega.nz/folder/w5syHQbb#vm7XzXKlbRaDl1nDTMuuCg
Android 11 recovery
78.9 MB file on MEGA
mega.nz
4. Reboot the A20 into TWRP and mount everything that you can.
5. Format Data (not just wipe) - don't restart
6. Flash View attachment Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip
7. Wipe both caches and Reboot into Recovery (for Android 10 you will need to flash Magisk 20.4)
8. Reboot system and enter all your data
To reboot into TWRP, hold down"vol up" and "power" during reboot.
Backup boot data and system so you can restore them if you need to.

Useful links
GSIs
https://forum.xda-developers.com/galaxy-a20/how-to/gsi-galaxy-a20-t3964546
Ultimate Pie ROM
https://forum.xda-developers.com/ga...ltimate-pie-rom-samsung-a20-variants-t4063399
Ripper Kernel
https://forum.xda-developers.com/galaxy-a20/development/kernel-ripper-kernel-v1-0-t4020627

physwizz said:
1. Connect phone to PC
2. Reboot into download mode by holding down both Vol up and Vol down then press vol up to continue
3. Use Odin to flash recovery.tar from here https://mega.nz/#F!ww9mXIAK!8lgKf3RM9qqBsSelVX_Lsg into the AP slot
4. Reboot the A20 into TWRP and mount everything that you can.
5. Format Data (not just wipe) - don't restart
6. Flash View attachment 4975463
7. Wipe both caches and Reboot into Recovery
8. Reboot system and enter all your data
To reboot into TWRP, hold down"vol up" and "power" during reboot.
Backup boot data and system so you can restore them if you need to.
Click to expand...
Click to collapse
i have the s6 and i use this method step by step.after first boot i try to make reboot to recovery but the phone stuck in the boot screen with some words in the top ..its dead...now when iam start to using odin to flash the stock rom A205FXXU2ASFA i got this messge..i used odin v3.13 and then v3.14.1 but its the same
this is the mesge i got..any help?
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Added!!
<ID:0/004> Odin engine v(ID:3.1401)..
<ID:0/004> File analysis..
<ID:0/004> Total Binary size: 4979 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> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> NAND Write Start!!
<ID:0/004> SingleDownload.
<ID:0/004> sboot.bin
<ID:0/004> param.bin
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

hooooossamq said:
i have the s6 and i use this method step by step.after first boot i try to make reboot to recovery but the phone stuck in the boot screen with some words in the top ..its dead...now when iam start to using odin to flash the stock rom A205FXXU2ASFA i got this messge..i used odin v3.13 and then v3.14.1 but its the same
this is the mesge i got..any help?
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Added!!
<ID:0/004> Odin engine v(ID:3.1401)..
<ID:0/004> File analysis..
<ID:0/004> Total Binary size: 4979 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> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> NAND Write Start!!
<ID:0/004> SingleDownload.
<ID:0/004> sboot.bin
<ID:0/004> param.bin
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Check developer options

U2 U3 and U4 recovery.tar files now available

the link to the U4 file shows a .ds_store file
D:

djxpro said:
the link to the U4 file shows a .ds_store file
D:
Click to expand...
Click to collapse
fixed

Unfortunately, I still can't restore my system.
The data partition will restore but the system partition will result in being& stuck on the boot screen.?

hooooossamq said:
i have the s6 and i use this method step by step.after first boot i try to make reboot to recovery but the phone stuck in the boot screen with some words in the top ..its dead...now when iam start to using odin to flash the stock rom A205FXXU2ASFA i got this messge..i used odin v3.13 and then v3.14.1 but its the same
this is the mesge i got..any help?
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Added!!
<ID:0/004> Odin engine v(ID:3.1401)..
<ID:0/004> File analysis..
<ID:0/004> Total Binary size: 4979 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> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> NAND Write Start!!
<ID:0/004> SingleDownload.
<ID:0/004> sboot.bin
<ID:0/004> param.bin
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
I was used an older stock rom u2. I downliad the same s6 update and the fkashing works :good:

I have a A205G on ARO-A205GUBS5ATA1-20200206101500 firmware (february security partch)
Can i install TWRP? What version do I install?

Help me Please
I have a huge question, I own an A205G (DS)
with baseband: A205GNDXU1ASE2 and build: A205GUBU1ASE8 (April 2019 security patch)
Can I install TWRP on this model? What version do I install?
U2, U3, U4 recovery?
U1 is not there.
Sorry for my bad English, I use google translator
by the way, it asks me for automatic update:
A205GUBS5ATA1 / A205GGOWT5ATA1 / A205GNDXS5ATA2 with security patch February 1, 2020.
recommendation?
update automatically and then install twrp?
Thanks for clarifying my questions!

3ndr1ckk1 said:
I have a huge question, I own an A205G (DS)
with baseband: A205GNDXU1ASE2 and build: A205GUBU1ASE8 (April 2019 security patch)
Can I install TWRP on this model? What version do I install?
U2, U3, U4 recovery?
U1 is not there.
Sorry for my bad English, I use google translator
by the way, it asks me for automatic update:
A205GUBS5ATA1 / A205GGOWT5ATA1 / A205GNDXS5ATA2 with security patch February 1, 2020.
recommendation?
update automatically and then install twrp?
Thanks for clarifying my questions!
Click to expand...
Click to collapse
You can download u2 from here
https://www.full-repair-firmware.com/search?q=A20

u4 recovery file hangs in odin 3.14 all developer options set USB Debug and OEM should i be using a modified version or a lower version of odin to complete the flash

SPARTAN_TECH said:
u4 recovery file hangs in odin 3.14 all developer options set USB Debug and OEM should i be using a modified version or a lower version of odin to complete the flash
Click to expand...
Click to collapse
What is your build number?

Sorry for such a noob question but what is the difference between U2, U3, and U4 recoveries? I'm buying an A20 in a couple of days and i want to root it and i've never heard of recoveries like that in all my years of flashing roms.

N1ghtr08d said:
Sorry for such a noob question but what is the difference between U2, U3, and U4 recoveries? I'm buying an A20 in a couple of days and i want to root it and i've never heard of recoveries like that in all my years of flashing roms.
Click to expand...
Click to collapse
What is your build number in software information?

My build number is "A205GUBS5ATA1". Which one do I use? I'm relatively new to the rooting community, so apologies for the question.

froidlesprit said:
My build number is "A205GUBS5ATA1". Which one do I use? I'm relatively new to the rooting community, so apologies for the question.
Click to expand...
Click to collapse
U4

froidlesprit said:
My build number is "A205GUBS5ATA1". Which one do I use? I'm relatively new to the rooting community, so apologies for the question.
Click to expand...
Click to collapse
Try the bin 5 one