Database Users

Note 3 root attempt failed and ruined my phone!

Hey guys,
I've come to this forum to ask you guys for help cause im out of ideas!
I wanted to root my Galaxy note 3 SM-I9005 through Odin using CF-Auto-Root-hlte-hltexx-smn9005.
When I did my phone got stuck in download mode, and it coulden't boot it normally, it would automaticly go to download mode.
So I decided to download some official Samsung firmware and download it on my Note 3 using Odin. But in the last like 90% it fails!
<ID:0/006> hidden.img.ext4
<ID:0/006> FAIL! (Size)
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I now get a message saying ''Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again''
So I wanna do that and what do you know... Kies just sais ''connecting'' all the time and then it doesnt connect. So what do I do now? im lost for ideas..
Please help!

U downloaded a software that did not match your partition sizes.
Download a unbranded firmware for your country
Sent from my SM-N9005 using XDA Premium 4 mobile app

Yair1991 said:
Hey guys,
I've come to this forum to ask you guys for help cause im out of ideas!
I wanted to root my Galaxy note 3 SM-I9005 through Odin using CF-Auto-Root-hlte-hltexx-smn9005.
When I did my phone got stuck in download mode, and it coulden't boot it normally, it would automaticly go to download mode.
So I decided to download some official Samsung firmware and download it on my Note 3 using Odin. But in the last like 90% it fails!
<ID:0/006> hidden.img.ext4
<ID:0/006> FAIL! (Size)
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I now get a message saying ''Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again''
So I wanna do that and what do you know... Kies just sais ''connecting'' all the time and then it doesnt connect. So what do I do now? im lost for ideas..
Please help!
Click to expand...
Click to collapse
Ideally you need to download the same firmware that was ON THE PHONE before you started messing with it. I repeat, the firmware ON THE PHONE and not the N9005 for your country (the phone could have been a N9005 Hong-Kong with 16GB flash and you might be as well in UK).

puja_kusmana said:
I deleted/ommited "0" in the prefix of phone number in the Lists ...! and now It Works .......! from Reject from List Operating Mode, both in Call Blocker and in SMS Blocker !
Cooooool ; Great....!
Grazie molto! crino !
Click to expand...
Click to collapse
This happen to me this past weekend and I assume was caused by USB 3.0... Take out the battery, and boot in download mode, and flash same firmware stock you have in your phone before messed up, and do it on USB 2.0
This solved my issue.
For the root, installed TRW recovery and boot on it, the recovery ask you that you are not rooted and root the phone for you more than easy...
Cheers
Enviado desde mi SM-N9005 mediante Tapatalk

[q] problem with my s4

Hy Guys! so recently i have bought a galaxy s4 and i think it is the i9505 model becouse under the battery it is nothing written...
So i have seen that the phone dosen't get a lot of signal and i have seen that the KERNEL was modified, also when i boot up my phone in the left corner it says written with red : KERNEL IS NOT SEANDROID ENFARCING" and with yellow "SET WARANTY BIT : KERNEL", also in the "DOWNLOAD MODE" ABOVE THE NORMAL WRITING IT SAYS GRAYED OUT : WRITE PROTECTION : ENABLED" AND "eMMC BRUST MODE ENABLED" so i tried downloading the stock firmwere from sammobile.com for it and in odin it always give me a big fail when i try to write the stock firmwere, all the settings are setted to default i have not changed anything ! .
So this is the log :
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9505XXUFNB8_I9505COAFNB1_I9505XXUFNB8_HOME.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> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> sbl1.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL! (Auth)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
and after it on the left corner of the screen of my S4 it writes with RED :
"START [224, 1440]"
'SECURE CHECK FAIL : sbl1"
please help me i dont know that much

Why do you only think its an i9505? Isnt that something you should confirm before buying?
The model number is in the about phone section
Why have you flashed a rom when you arent sure what model you have?
Is kies installed?
What firmware was the phone originally on?

DSA said:
Why do you only think its an i9505? Isnt that something you should confirm before buying?
The model number is in the about phone section
Why have you flashed a rom when you arent sure what model you have?
Is kies installed?
What firmware was the phone originally on?
Click to expand...
Click to collapse
Thx for replay! so my phone when i bought it was on the 4.4.2 Kit Kat and that is the firmwere that i wanted to flash to it, i am saying that I am not shure what model is becouse in the model section it was writen i9505 but I was not 100% shure....
when ODIN gived me the error that i showed you the phone could not boot up any more, only the LED blinked permanently with blue so i have flashed with succes using ODIN the CWM and using CWM i have sucessfuly instaled Cyanogenmod now, but i wanted on the original stock Samsung firmwere .
I have tried reflashing now but no succes
P.S :
I dont think that the phone was on the original 4.4.2 by samsung becouse it had a wierd bootlogo. and in the rom i could delete stock apps
AND YES i have KIES instelled

In the download mode you can find your model number. So make sure you have an i9505 before you flash.
Almost all Odin errors can be resolved by the following:
- Different usb port
- Different cable
- Reinstall drivers
- Make sure Kies is not running in the background.

This ^

thx
Lennyz1988 said:
In the download mode you can find your model number. So make sure you have an i9505 before you flash.
Almost all Odin errors can be resolved by the following:
- Different usb port
- Different cable
- Reinstall drivers
- Make sure Kies is not running in the background.
Click to expand...
Click to collapse
Hey ! I have tried reinstalling the drivers, changhing the cable and the usb port also i tried another PC but it still dosen't work

Have you disabled kies in your task manager

DSA said:
Have you disabled kies in your task manager
Click to expand...
Click to collapse
YES I have ! I dunno what to do )

festy22 said:
YES I have ! I dunno what to do )
Click to expand...
Click to collapse
Mate ,
Use this app to find out what you have....
https://play.google.com/store/apps/details?id=org.vndnguyen.phoneinfo&hl=en
works great.

[Q] AT&T Galaxy S5 Update G900AUCU2ANG3 - Issues after update

I have tried searching and do not see anyone with a similar issue. I was previously rooted with TowelRoot, but somehow my phone not only allowed the G900AUCU2ANG3 update today to download, but also allowed it to install. I know I should have removed TR before continuing, but stupid stuff like that happens when you see the update waiting when you first wake up and don't have contacts in or glasses on...
I can fully restore my phone to normal use, other than wifi. For whatever reason, the failed update shows to have changed the baseband, but I have no ability to connect to a wifi network, and despite about 15 factory resets since this morning, my device status still shows "Custom." Here is exactly what I see when I go into Download Mode (or as close as I can replicate it):
ODIN MODE
PRODUCT NAME: SM-G900A
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
REACTIVATION LOCK(KK): OFF
KNOX WARRANTY VOID: 0x0
QUALCOMM SECUREBOOT: ENABLE (CSB)
RP SWREV: S1, T1, R1, A2, P1
UDC START
At this point, I can't find anyone with an NG3 stock firmware to use with Odin, and Odin keeps failing because the old firmwares won't pass the authorization stage. I attached the Odin screenshot to this post in case someone has other ideas. I can actually use my phone (not bricked), but wifi will not connect even though it can see various open and secure networks. I get an error stating "Failed to Obtain IP" when trying to connect to networks with "Very Strong" signal strength (I can see the AP from my desk).
Thus, I really need to be able to do 1 of 2 things:
1) Restore it to stock myself so I can have wifi, or
2) Be able to get it to show "System Status: Official" so that the local AT&T Device Service Center I drive by twice a week taking my kid to hockey practice will plug it in and update it and restore it. They managed to save my wife's Note 3 from a fairly bad soft brick / boot loop issue, but I also know that the "Custom" thing will pretty much guarantee they don't work on it.
Thanks in advance.

..

fffft said:
Writing a full stock firmware image, followed by a factory data reset will remove the custom status. So that would satisfy No. 2.
As to your first wish, I find it hard to believe that you couldn't find an ATT firmware image anywhere. There are dozens of firmware sites and I can only assume that you just did a short or cursory search. If you spend a few minutes with Google you can surely locate any ATT firmware version that has been release longer than one day.
Either way, use Odin to write a firmware image as the fastest way to resolve the situation. If you have difficulties, try this guide
If the problem persists, then you need to provide us with more details. Notably, the verbatim Odin error log, along with the exact file name you are trying to write and a detailed, step by step description of how you are using Odin.
.
.
Click to expand...
Click to collapse
I definitely have searched high and low for a stock version (both before the original post and just now) that will work with the failed update G900AUCU2ANG3. No one has a stock firmware I can find, and I cannot find any method by which to downgrade to an older version that I can find, such as G900AUCU1ANCE.
Here is what my phone says in Settings --> About device:
Baseband Version:
G900AUCU2ANG3
Build Version:
KOT49H.G900AUCU2AND3
File name I'm trying (but know won't work...not the newest baseband): G900AUCU1ANCE_G900AATT1ANCE_G900AUCU1ANCE_HOME.tar
Odin Error Log:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G900AUCU1ANCE_G900AATT1ANCE_G900AUCU1ANCE_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> aboot.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Added!!
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> aboot.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)

..

fffft said:
The additional information definitely helps. But it's still a drop in the bucket. You didn't give us a detailed, step by step description of how you are using Odin e.g. what version of Odin you are using , which line you entered the firmware file line on (e.g. AP, PDA, etc) and so forth. And most importantly, did you try the procedure that I linked to in my last post?
We can't see your phone and these details are important as any one of them could cause failure. So we need to check off each item that you are doing.
Nominally the Odin error you posted says that your bootloader refused the firmware version you tried to write. More likely it is a timing error from a marginal USB cable or port. Odin is well known as tempermental with respect to USB timing. Try a different USB cable (yes, really. and yes, it is important. don't skip this step) and different USB port.
Most critically, ensure that you are entering download mode by removing the phone battery, then replacing it and using the volume down + home +power key sequence. And also important, if the first Odin write fails, do not close the Odin window. Instead remove the phone battery again, go into download mode again and then hit write again in the open Odin window. Inevitably, the second attempt will then succeed.
Try the very good procedure that is listed here <---- click on the link
Odin can be frustrating, but with a modicum of patience and attention to detail you will succeed. Good luck
.
Click to expand...
Click to collapse
I ended up going to the local AT&T Device Support Center (luckily it's about 2 miles from the ice rink at which my son practices) and they flashed it back to stock with no problems. She said I was one of 4 people that day who had issues with that particular update, and since my Knox Warranty showed 0x0, she thankfully ignored the "Custom" on device status. All is well and I have a clean backup in Kies if needed in the future and TowelRoot back on the device to kill some bloat. Thanks!

Can I get a flashable G900AUCU2ANG3? I am selling the phone and they want it stock and updated. I can't flash it back to stock. I didn't update it but it gives me the same Odin error as though I was trying to downgrade. Used to be able to downgrade it and do whatever I wanted when I was tinkering with getting SuperSU to stick after update. I've made no major changes. Did something come down from Samsung that locks Odin? I froze Knox and thought that might have something to do with it so I thawed it and factory reset after unrooting. No good.
Long story short I'd like an Odin flashable latest firmware to see if it will take. Sorry I don't have more info right now but the buyer has the phone right now.

Is my phone soft bricked? recoverable at all? Samsung Galaxy Grand Prime

I made the mistake of rooting my phone a quick way using the kingroot app along with superuser. I wasnt aware that restarting the phone would frp lock it. I restarted the phone yesterday and next thing you know im stuck on a screen with a big yellow triangle and black exclamation point in the middle that has text above it that reads: "Custom Binary Locked. FRP Locked"
I quickly found out it was due to using the kingroot app. So every time i tried to power on the phone, the same message came up and i wasnt able to do anything. I came upon the method of using Odin 3.10.7 to flash the stock firmware back onto the phone and hard resetting it; which i have tried and failed.
First i downloaded Odin and the firmware I needed from sammobile.com and extracted them both and proceeded but i keep getting this:
<ID:0/006>Added!!
<OSM>Enter CS for MD5..
<OSM>Binary Check MD5..Do not unplug the cable
<OSM>Please wait..
<OSM>Checking MD5 finished successfully...
<OSM>Leave CS
<ID:0/006>Odin engine v(ID:3.1100)..
<ID:0/006>File Analysis
<ID:0/006>Setup Connection..
<ID:0/006>Initialization
<ID:0/006>Get PIT for mapping..
<ID:0/006>Firmware update start..
<ID:0/006>SingleDownload.
<ID:0/006>aboot.mbn
<ID:0/006>NANDWrite Start!!
<ID:0/006>sbl1.mbn
<ID:0/006>rpm.mbn
<ID:0/006>tz.mbn
<ID:0/006>hyp.mbNON-HLOS.bin
<ID:0/006>sec.dat
<ID:0/006>boot.img
<ID:0/006>recovery.img
<ID:0/006>system.img.ext4
<ID:0/006>FAIL! (Ext4)
<ID:0/006>
<ID:0/006>Complete(Write) operation failed.
<OSM>All threads completed. (succeed 0 / failed 1)
The screen in my phone had read:
ODIN MODE
PRODUCT NAME: SM-G530T
CURRENT BINARY: CUSTOM (Which Now reads Smasung Official after many attempts)
SYSTEM STATUS: CUSTOM OS (Which now read official)
FRP LOCK: ON
QUALCOMM SECUREBOOT: ENABLE (CSB)
RP SWERV: S1, T1, H1, R1, A1, P1
SECURE DOWNLOAD: ENABLE
AFTER THE FAILED DOWNLOADS IT READS UNDER:
VOLUME SIZE IS TOO BIG 4362240 < 4546560
ODIN: Invalid id ext4 image
Below it reads Downloading....Don Not Turn Off Target
I have tried Odin several times and gotten the same messages. I was thinking maybe the file was too big? because it says volume size too big. There is no other place other than sammobile though to download my firmware. Although now, it shows that the system is somehow partially flashed on my phone because it reads samsung official on the top of the screnn when put in download mode; but now also when i try to power the phone on instead of the custom binary message it reads: An error has occured while updating the device software. Use the emergency recovery function in the smart switch PC software.
I have downloaded Kies 3 and smart switch all of which read that my device is unsupported and when i try the device initialization function it ssays my s / n is incorrect. The S/ N is the serial number right?
Pleasehelp. Is my phone recoverable?

I repeatedly get the volume size is too big message.

Soft Bricked S5

Bought a S5 (SM-G900AZ) "unlocked" cricket phone intending to use it on AT&T, it was running 5.0 and I got root then started disabling some of the bloat via 'no bloat' app, all was well, then I restarted, after the splash it displayed the setting up android window, then went to setting up apps, then it got stuck in a loop where it rebooted repeatedly at this step, never actually starting. I let it retry for a while, dropped the battery and tried again to no avail. Next I put it into the menu so i could do a wipe and clear the cache which I did then restarted, same result. figured I had boned it up and would need to reflash the factory distro to reinstate some of the bloat I disabled. I downloaded the correct firmware of 5.0 from Samsung opened Odin and selected the AP check box, located the Samsung file, it checked the MD5 then I hit start, FAILED.
From ODIN
<ID:0/004> Added!!
<ID:0/004> Odin engine v(ID:3.1005)..
<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> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL! (Auth)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
On the Phone
ODIN MODE
Product Name: SM-G900AZ
Current Binary: Custom
System Status: Custom
Reactivation Lock: OFF
Knox Warranty Void: 0x1 (4)
Qualcomm Secureboot: Enable (CSB)
AP Swrev: S1, T2, R1, A3, P1
Secure Download : Enable UDC Start
SW Rev Check Fail : [aboot]Fused3 >Binary 2
What does the Fused and Binary numbers mean?
Do I need to attack this from another angle?
Any ideas on how to get the factory software back on this thing?
Thank you for reading and any help you can provide.

bump

This is also my problem in my SM-G900I, i cant update to official marshmallow firmware because it always does the same as yours. Even in lollipop firmware still the same result, always failed. I already tried everything, factory reset, all odin version etc but still same result.
In odin 3.10.7 im stuck in this for almost 1 hour (see attached). I tried 5 times and still the same.
hope someone can help us.....:crying::crying::crying::crying:

The assasin said:
hope someone can help us.....:crying
Click to expand...
Click to collapse
He has a name, and called official Samsung service center.

SOLVED
So after a lot of reading and a suggestion elsewhere, it's alive, I hope this can help you as well 'The assasin'
DL Samsung Kies
Update kies, and usb divers [Tools : Reistall Device Driver]
With your phone booted in to Download Recovery [push Power + Home + Vol Down] then [Vol Up to confirm] then connect to the USB.
Now the USB cable should keep it powered up, you can remove the battery and read the Mod # and SN #
In Kies go to [Tools : Firmware Upgrade and Initialization]
Put in your Mod # [ok]
Put in your SN # [ok]
Click ok on all the confimation boxes.
It will download the correct software from Samsung then push it to the phone and restart, pay attention as it asks you to remove and replace the cable after restart, incidently if you removed the battery eariler to read the Mod # / SN # then when it resets it wont restart, if you happen to walk away.
Put in the battery and power it up, mine rebooted a couple times then booted normally starting back at the Welcome screen, I was able to re root and make some of the changes I was trying to make and now have a working phone.
I hope this helps others.

BrweckedS5 said:
SOLVED
So after a lot of reading and a suggestion elsewhere, it's alive, I hope this can help you as well 'The assasin'
DL Samsung Kies
Click to expand...
Click to collapse
The first software that every fresh S5 owner gets related with, this is KIES..
Every one assumes that you failed in all known ways and then you started this topic.