Database Users

[Q] Note 2 Stuck in Bootlop, Failing to flash root in Odin

Hi there,
I'm trying to fix my sister's Note 2. It is stuck in bootloop. I've rooted my GS2 without any problems, but odin is failing with the Note 2. Here's what I get:
<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.img
<ID:0/003> NAND Write Start!!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Some more info: trying to flash "cwm6-root-note2.tar" as the PDA file, and also unsure whether the phone currently runs on stock 4.2 or 4.3, im unable to check since it's stuck in bootloop. I realize there might be a whole new problem if its on 4.3, was just wondering what my best option is right now. I've done some reading here on XDA and can't figure out whats the best thing to do.
Any input is greatly appreciated!

Sorry wrong forum, you're in the galaxy s4 forum...try reposting over in the Note 2 forums
Sent from my SAMSUNG-SGH-I337 using Tapatalk

[Q] [GT-I9506] Can't flash any recovery via Odin

Just bought a phone, already upgraded to latest Lollipop firmware from Samsung.
Knox warranty is 0x0.
Now I want to flash Cyanogenmod, and first I tried to install recovery (CWM/TWRP). Downloaded odin 3.09.3, did everything according to tutorial, odin says everything is ok:
<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)
Phone reboots into samsung firmware. Turning it off and holding vol up + home + power on brings stock recovery, no changes.
What should I do? Maybe bootloader is locked somehow? How to check and unlock? I did it once on a Nexus 10 tablet. Thanks!

Uncheck auto-reboot in Odin before flashing. That should fix it.

Lennyz1988 said:
Uncheck auto-reboot in Odin before flashing. That should fix it.
Click to expand...
Click to collapse
Thank you. Helped!

[Q] Having issues booting up my N9005 after a failed 5.0 Official Lollipop Update

Hello, I have tried updating my N9005 to the latest firmware 5.0 provided on Sammobile. After attempting to flash it via ODIN, the following error occurs:
<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> sbl1.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> aboot.mbn
<ID:0/003> rpm.mbn
<ID:0/003> tz.mbn
<ID:0/003> sdi.mbn
<ID:0/003> NON-HLOS.bin
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
<ID:0/003> Added!!
Retried this step several times, but i have received the same error.
Following a few instructions found on the XDA forums, I tried using PIT file in order to re-partition.
The phone now reboots but will not go past the first boot screen "Samsung Galaxy Note3 N9005".
I tried pulling out the battery and performing a factory reset (along with wiping caches), but the situation is still the same after rebooting the device.
Also I have noticed that upon accessing "recovery mode", a error stating " Failed to mount /system (Invalid argument)" error is displayed.
I'm pretty new at upgrading phones and I've bought this phone recently and was unaware of the consequences of flashing ROMS via Odin.
The initial fw. on the device was 4.4.2 Official Samsung. Is there any way that I can make the phone reboot normally with fw. 4.4.2? Or any other firmware for that matter?
Thanks in advance.

AndreiRonaldo said:
Thanks in advance.
Click to expand...
Click to collapse
Reflash the firmware again now via ODIN without the .pit file.

Joku1981 said:
Reflash the firmware again now via ODIN without the .pit file.
Click to expand...
Click to collapse
I've tried that several times without success. But the issue was fixed. Apparently the PIT file I was using did not match the ROM i was flashing. I just had to find a matching pair of both ROM and PIT and now I've successfully booted my device. Hope that this thread might help others in need for answers to similar questions.

Alright, this is taking alot more than i had expected, after finally managing to boot my device, I've noticed that flashed rom behaves awfully, my phone is stuttering, and i have no sound. Also, my IMEI is displayed as "Unknown" in the "Status'" section of the device's Settings. Any suggestion on how to fix this issue?

flash the stock the rom you have before

Stuck in bootloop from trying to downgrade from 5.0 to 4.2

As the title says, I tried to downgrade from lollipop 5.0 to 4.2 because I've had several issues and I also wanted to get root. I think part of my mistake was I wiped data/factory reset before I flashed AP. Any help would be much appreciated, as I have been at this for the past five hours. I added some info below that might help below. Thanks
- I cannot boot into recovery and get the message (Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again)
- CP is the only thing that will flash and CSC also fails
- model number is g900a AT&T
- I have used Odin 3.10.7 and 3.09, but no luck
<ID:0/003> Odin engine v(ID:3.1100)..
<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> boot.img
<ID:0/003> NAND Write Start!!
<ID:0/003> recovery.img
<ID:0/003> persist.img.ext4
<ID:0/003> system.img.ext4
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

Did you try to repair him via kies?Maybe would help.
Sent from my D6503 using Tapatalk

Hey I have also experienced the same thing before, I was panicking that time, so I fixed it by flashing the old zip file, if that does not work try following the instructions your phone gave eg. Go to kies

VoltexYT said:
Hey I have also experienced the same thing before, I was panicking that time, so I fixed it by flashing the old zip file, if that does not work try following the instructions your phone gave eg. Go to kies
Click to expand...
Click to collapse
Kies and kies3 are both not recognizing my device. I heard it could be because of usb debugging, but I can't boot into my phone to check.

Allek84 said:
Did you try to repair him via kies?Maybe would help.
Sent from my D6503 using Tapatalk
Click to expand...
Click to collapse
Both kies and kies3 are not recognizing my device.

SM-G930A Bricked after trying to unroot.

Currently stuck with a Bricked Galaxy S7 that is in a Recovery Boot-loop. I tried flashing the stock firmware to the device and it failed.
Here is the Odin log:
<ID:0/003> Odin engine v(ID:3.1203)..
<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> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
The Screen after this failure displays the "Downloading, Do not turn off target" screen. And in small red font in the upper left corner of the screen the statement, "SW REV CHECK FAIL : [system]fused 3 > Binary 1" is shown. I don't have any clue where to go from here so any suggestions would be lovely.
Cheers,
Declan

DecDaddy said:
Currently stuck with a Bricked Galaxy S7 that is in a Recovery Boot-loop. I tried flashing the stock firmware to the device and it failed.
Here is the Odin log:
<ID:0/003> Odin engine v(ID:3.1203)..
<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> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
The Screen after this failure displays the "Downloading, Do not turn off target" screen. And in small red font in the upper left corner of the screen the statement, "SW REV CHECK FAIL : [system]fused 3 > Binary 1" is shown. I don't have any clue where to go from here so any suggestions would be lovely.
Cheers,
Declan
Click to expand...
Click to collapse
I ran into same issue. Just hold power button until phone shuts down, power up into download mode and Odin flash the stock firmware for your phone again. It's a soft brick. Be sure you have correct firmware.

Currently stuck with a Bricked Galaxy S7 that is in a Recovery Boot-loop. I tried flashing the stock firmware to the device and it failed.
Here is the Odin log:
<ID:0/003> Odin engine v(ID:3.1203)..
<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> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
The Screen after this failure displays the "Downloading, Do not turn off target" screen. And in small red font in the upper left corner of the screen the statement, "SW REV CHECK FAIL : [system]fused 3 > Binary 1" is shown. I don't have any clue where to go from here so any suggestions would be lovely.
Cheers,
Declan
Click to expand...
Click to collapse
Same issue here - phone bricked. Odin or the Download mode of the phone fails with 1 of several errors. I have found that only 1 version of Odin works with my SM-G930A now. The last trick I think I have in the bag here is to pry off the back of the phone and make sure the stock firmware I am trying to use i the one that matches the device...
I have tried these stock images (easily google-able):
- ATT_G930AUCS2APF2
- G930AATT1APB5_User_Binary
The only version of Odin that works is the one I used to root the SM-G930A phone:
- Odin PrinceComsy.exe
It can only flash the root file:
- Samsung_G930x_QC_Rooted_BOOT.TAR
I have tried so many different versions of Odin, I think I am going cross eyed. If anyone has a solution for a phone that is looking bricked, please give me a shout out.
Thanks,
Aaron

aaron99 said:
Same issue here - phone bricked. Odin or the Download mode of the phone fails with 1 of several errors. I have found that only 1 version of Odin works with my SM-G930A now. The last trick I think I have in the bag here is to pry off the back of the phone and make sure the stock firmware I am trying to use i the one that matches the device...
I have tried these stock images (easily google-able):
- ATT_G930AUCS2APF2
- G930AATT1APB5_User_Binary
The only version of Odin that works is the one I used to root the SM-G930A phone:
- Odin PrinceComsy.exe
It can only flash the root file:
- Samsung_G930x_QC_Rooted_BOOT.TAR
I have tried so many different versions of Odin, I think I am going cross eyed. If anyone has a solution for a phone that is looking bricked, please give me a shout out.
Thanks,
Aaron
Click to expand...
Click to collapse
I fixed my phone.
Answer for my case:
1. Load into Recovery mode
2. Reset factory defaults/wipe phone.
3. Clear cache
4. Reset factory defaults/wipe phone a 2nd time just for fun
5. Reboot phone
6. My phone loaded a long time through at the AT&T loading screen (it appeared locked, but was not)
- NOTE: You can always hard reset it and try to get through the AT&T loading screen
7. Go through Android/Samsung/AT&T welcome wizard
8. Root the phone: See permanent root section here: http://forum.xda-developers.com/ver...-to-notes-root-install-xposed-unroot-t3411039
- This root process side loads Chainfire's SU tool
-- NOTE: This is where things become unconventional, since my phone was not working with Google Play Services nor did the Google Store app work (I tried everything... they just would not work)
9. Open Chainfire's SU tool, go to the app's settings:
- enable SU at boot
- instead of "prompt", set app to auto-accept root access requests (normally this is stupid since some other random app could automatically acquire root access, but in this case, I was not in this state for very long. I actually had to do this because the system would not pop up notifications for apps requesting root access)
10. On a PC, download Chainfire's Flashfire app (I used this: eu.chainfire.flash_0.53-53_minAPI17(armeabi-v7a,x86)(nodpi)_apkmirror.com.apk)
11. In a Windows command prompt running as adminitrator, put the APK from step #10 into the same root.bat folder used in step #8
12. With the phone connected (with Samsung USB drivers installed of course), run this command from that folder: adb install -r eu.chainfire.flash_0.53-53_minAPI17(armeabi-v7a,x86)(nodpi)_apkmirror.com.apk
13. Open app drawer and run Flashfire
14. Follow this guide from step #1 through step #9 (because my phone will not work with Odin nor the boot loader listed on step #10 of the guide): http://www.droidviews.com/install-deodexed-debloated-stock-rom-on-att-galaxy-s7-sm-g930a/
- If steps are followed through step #9, the phone will be in Download mode
15. Hard reset phone and boot into Recovery mode
16. Repeat steps #1-5 from my steps listed above to reset factory settings / wipe the phone again
17. Phone reboots and will appear to hang... Just wait. Wait and wait. It will load.
18. Go through Welcome wizard...
This time, all apps work, due to the ROM image used during step #14. This slimmed down ROM image has fully functional stock apps, which is great because that is now set as as the factory image for any future Recovery mode factory resets. Life saver! ...or more like a phone saver for me.
Hopefully this helps someone else.
-Aaron

aaron99 said:
I fixed my phone.
Answer for my case:
1. Load into Recovery mode
2. Reset factory defaults/wipe phone.
3. Clear cache
4. Reset factory defaults/wipe phone a 2nd time just for fun
5. Reboot phone
-Aaron
Click to expand...
Click to collapse
I know this is an old thread, but im having this problem after attempting to root to stock and im stuck on the samsung custom logo with recovery booting in the top left corner. the main problem though is i cant boot to recovery mode, it simply wont let me