Hi guys,
I tried to root my phone and installed the "One-Click lag fixed"
Then, my phone get into trouble
So, I can power on my phone and it stuck at the "Galaxy S" pages. Not loading into the system. Then, after it keep loading on that page for a while, the screen turn black and if I touch the 4 button that are placed under the screen, they glow. If I press the power off, it will restart itself and stuck at the "Galaxy S" page again.
Here I have downloaded the (1) ODIN v1.3 (2) s1_odin_20100512.pit and (3) T959UVJI6.tar
I open the ODIN exe, press volume up and down button then plug my phone to my computer, then my phone showed an Andriod digging the ground.
Then I added s1_odin_20100512.pit next the PIT option and T949UVI6.tar under PDA option. And click Start
Here's what the ODIN showed:
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<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> cache.rfs
<ID:0/003> factoryfs.rfs
<ID:0/003> modem.bin
<ID:0/003> zImage
<ID:0/003> Removed!!
<ID:0/003> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/004> Added!!
<ID:0/004> Removed!!
Also, ODIN showed PASS; therefore, I unplug my phone from the computer
however, when I am done with ODIN and my phone reboot itself. The same thing happened. It stuck at the "Galaxy S" page
What did I do wrong!?
Thanks everyone.
sounds like a busybox issue. try this flashable version in recovery mode then reboot. :
Related
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?
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?
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?
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.
Hi all,
My S7 (rooted) appears to be stuck in a bootloop. Last night, I was using it as normal and set it down to charge overnight.
Woke up this morning, recurring bootloop. Tried to get into recovery, but just got a 'Downloading' screen. Tried to flash a stock firmware (vol down key etc) but got
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1101)..
<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> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
For info, it's rooted, running a custom rom and until yesterday was working fine. No new software has been installed in the past couple of weeks, no settings have been changed.
Any ideas as to how I can get the phone working again?
The "Downloading..." screen is where you need to be to flash stock with ODIN
Make sure to use ODIN 3.12.3 minimum version
I'll give it a go when I get home from work and report back. Seems I was using an older version of Odin (3.11.1). I now have 3.12.3.
Thanks for the reply.
So I loaded a BL, AP, CP & CSC file into Odin (stock 7.0 firmware based on my phone carrier).
Clicked Start:
<ID:0/003> Odin engine v(ID:3.1203)..
<ID:0/003> File analysis..
<ID:0/003> skip file list for home binary
<ID:0/003> param.bin
<ID:0/003> modem_debug.bin
<ID:0/003> Home Binary Download
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003>
<ID:0/003> FAIL! (DeviceInfo)
<OSM> All threads completed. (succeed 0 / failed 1)
Doesn't seem to like what i'm doing.
<ID:0/003> FAIL! (DeviceInfo)
Do you have a green/blue COM port lit up at the top of ODIN when you connect the phone?
Tried a different USB lead / port?
The Com port info shows in blue. Tried on two different PCs, 2 different official cables, 4 different USB ports.
Getting a bit further:
<ID:0/003> Odin engine v(ID:3.1207)..
<ID:0/003> File analysis..
<ID:0/003> skip file list for home binary
<ID:0/003> param.bin
<ID:0/003> modem_debug.bin
<ID:0/003> Home Binary Download
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<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> cm.bin
<ID:0/003> FAIL!
Any thoughts?