Database Users

Help with phone stuck in download mode

Hi everyone
I am hoping someone can help me with my phone.
My phone was running 2.1 JF3 and i wanted to upgrade to 2.2 JPY firmware through kies.
I had previously installed a lagfix when i first got the phone but could not remember which one and couldnt find the original thread so i figured i will do the update wipe everything and be up and running.
So, the kies update failed just hanged at 0% when flashing.
So i went the odin route with JPY and this also is hanging.
After reading abit more some people have suggested that JPY does not include the dbdata info if it is damaged so i have tried JPU update with 3 files and 512.pit / repartition selected.
When i try this i get:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9000XXJPU-REV03-PDA-low-CL747761.tar.md5 is valid.
<OSM> MODEM_I9000XXJPU.tar.md5 is valid.
<OSM> GT-I9000-CSC-MULTI-OXAJPU.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> 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> boot.bin
<ID:0/004> Removed!!
<ID:0/004> Complete(Write) operation failed.
The update hangs at boot.bin with what looks like the start of a blue progress bar below the yellow triangle.
Phone is now stuck with only download mode available.
Can anyone suggest something else for me to try?
It seems like a problem with partition / dbdata i think.
I have the dbdata.rfs.tar file and think i may try this with odin but not sure where to put it.
Any suggesions greatly appreciated.
Many Thanks for reading

Did you definately have the 512 .pit file slected and re-partition selected when you did your flash? If so then I would guess that you must have been using a lagfix which converted your file system from RFS to something else (EXT4 maybe?) and now Odin can't write to it. Personally I have no idea how to fix this, it would probably help if you can find details of which lagfix you had installed as then the dev of the lagfix may be able to advise you. I'll be watching this thread to see what the fix is!

Thanks for the reply, that doesnt sound too good but does make sense.
The lagfix probably did involve switching filesystems, i remember i did it through ADB maybe 5 - 10 lines of code though to be honest didnt fully understand the implications of what it was doing. i know i had issues with not being able to install some software due to size issues even though i had plenty of space on the internal and external sd card.
If i find time later ill have another trawl
I have just retried the flash with 512 and repartition as i listed above and the same result.

download something that has 3 files and PIT and also contains 'dbdata' i think JM8 has this or even darkys 9.2 resurrection (odin version)
i had the same issue and darkys 9.2 fixed it... flash it thru odin (onnly comes in 1 file)
select PIT (512) and tick re-partition. that should do it..
flashing over a lagfix is not good, but it is fixable....

Hi guys, i tried darkys resurrection and JM8, both were prety much the same as when i tried the JPU rom (3 files + 512 pit partition selected). I tried a few others as well but every one would hang at the start.
After another failed flash, eventually the phone went off completly and died. Couldnt get back to download mode. tried removing battery, charging etc.
So i looked up my nearest service centre luckily 30mins away in bradford and went there. I told them a kies update had gone wrong, they were not suprised at all and said it happens all the time. They looked at it and said it would need to be sent to another service centre as it was totally dead where they have a tool to "force the update on to the chip". He also said "i've no idea how it got into this state" Me too !
So i just have to wait for them to get back to me, as there is no physical damage it should be covered under warranty at no extra cost. Looks like im stuck with a trusty nokia for a week !

[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.

Stuck in bootloop and not even ODIN wants to work! Help!

Hi,
My wife's phone SM-G935F started to bootloop after a normal update. It goes to the loading screen (IMG 1) and just stays there. The only thing I can do from there is VolDown+Power to reset or Voldown+Home+Power to Recovery mode.
Can't access factory reset mode, and the only other thing i've been able for it to show is the light-blue screen with the "!" simbol and "Try using Smart Switch Recovery..." which didn't work.
IMG1= https://s11.postimg.org/w6vna4mwz/20161029_180455.jpg
I Don't exacly know the region of the phone, but i think it is the Trinidad and Tobago one (International unlocked bought from B&H).
Anyone knows how to know region from a cell you can't boot?
Also don't know if OEM was active or not, but i think this is the problem. If i can't boot the cell, hoy to disable OEM prot?
When I try to ODIN it shows this:
http://postimg.org/image/4yyt2sd1b/
And then it FAILS
I don't know what more to do.
My odin active options are:
Auto Reboot
F. Reset Time
And the phome screen goes from this:
http://postimg.org/image/qwqoiu2nz/
To displaying this
http://smg.photobucket.com/user/brava/media/20150902_012011_zpsjm9lr9np.jpg.html
Just instead of RECOVERY, it says BOOT.
I successfully updated the bootload so the "!" simbol and "Try using Smart Switch Recovery..." screen isn't showing anymore, but the bootloop is still going. Cant update the AP, CP not CSC.
Anyone has any idea what can i do?
This phone was running Marshmelow, never had been rooted and never used custom roms in it. It was only 3 months old. Think of the children
Thanks

smart switch will work if you download the drivers to your computer. this step is necessary to allow smart switch to see your phone.
then use smart switch, click on more, emergency recovery, then device initialization.
followinstructions, it should take about 5 minutes to recover your phone, if you have input the correct information.

Cosmic Blue said:
smart switch will work if you download the drivers to your computer. this step is necessary to allow smart switch to see your phone.
then use smart switch, click on more, emergency recovery, then device initialization.
followinstructions, it should take about 5 minutes to recover your phone, if you have input the correct information.
Click to expand...
Click to collapse
Does the phone needs to be in download mode? or in the loading screen is ok?
Only 3 options I have are:
Boot screen (galaxy screen)
Powered Off
Download mode.
I can't reach any other screens.
Thanks!

Sedado77 said:
Does the phone needs to be in download mode? or in the loading screen is ok?
Only 3 options I have are:
Boot screen (galaxy screen)
Powered Off
Download mode.
I can't reach any other screens.
Thanks!
Click to expand...
Click to collapse
Loading screen is fine as long as smart switch can see your phone, the procedure should work.
I was in the same position once.

what have u chosed in odin? this look like bootloader is broken

Cosmic Blue said:
Loading screen is fine as long as smart switch can see your phone, the procedure should work.
I was in the same position once.
Click to expand...
Click to collapse
Smart Swich is working as ****. it doesn't load the recovery screen even if the phone is not connected
Any idea how to make it work=?
Windows 7 x64 here.

<ID:0/003> 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..
<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/003> Odin engine v(ID:3.1101)..
<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> sboot.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> param.bin
<ID:0/003> cm.bin
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Here is my ODIN log when I try to BT/AD my phone.

Sedado77 said:
Here is my ODIN log when I try to BT/AD my phone.
Click to expand...
Click to collapse
This is the case when i try to AD everytime. I'm quite sure my problem is the region of the firmware, but i can't know WHICH firmware to download. I called the US store where i bought it and they told me it was from Vietnam.
Got the Vietnam Stock Firmware (XXV) and it still is "Blocked by FRP Lock" when it tryies to do the recovery.img file...
Anyone knows how to get the region of the phone from the serial/imei or any other meens whith a soft bricked phone?
I tried SmartSwitch but it had the same problem. I think it used the region from the BL/CSC i flashed to it instead of the original one...
Also, the radio from the Vietnam version didn't match my phone...
Any ideas?
I can't take it to the manufacturer, i bought it online from H&M in the US and I live in South America.
HELP!!!:crying::crying:

load Odin 3.1.2.3
load Samsung_G935x_QC_Rooted_BOOT.TAR
Power off Phone ( hold Power + Vol down) ..... hold Power+Home+Vol down to enter Download mode....
connect S7 Edge to Computer ( DL Mode)
open Odin as an Administrator (!!) - right click on Odin-
put "Samsung_G935x_QC_Rooted_BOOT.TAR" in Odin
Flash
if it won`t work... try a samsung kernel... without root

I have same problem as OP help ? I had 7.0 update but it only made my phone restart, now i flashed official with odin and now stuck in bootloop... can only seem to access download mode, smart switch if i try connect says my phone is not supported.. what the hell to do now ???

Problems Flashing

T-Mo On5 Pro (I think lol
So I flashed pegasis and reborn. Turns out that they both have sound issues and the camera doesn't work on either.
So I tried to flash the recovery from one of the other threads, nothing.
Tried to reflash pagasis and reborn, nothing.
I can get to TWRP which is awesome but now even ODIN can't push anything.
<ID:0/006> 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/006> Odin engine v(ID:3.1203)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> SingleDownload.
<ID:0/006> boot.img
<ID:0/006> recovery.img
<ID:0/006> system.img
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/006> Removed!!
<ID:0/006> Added!!
At this point, I'm stuck and need a little bit of help (to at least go back to stock). Thanks!

I had this issue as well and what i did was use samsung kies to go back to stock since phone got semi-bricked and i could only enter download mode, since you have access to twrp you can try and flash the superstars rom which is stable and pretty much bug free

Echo_0408 said:
I had this issue as well and what i did was use samsung kies to go back to stock since phone got semi-bricked and i could only enter download mode, since you have access to twrp you can try and flash the superstars rom which is stable and pretty much bug free
Click to expand...
Click to collapse
Well, I guess I can grab Kies in the meantime.
Where did you grab the superstars ROM and the stock ROM? I just want to make sure camera and phone work lol.

Rom:
https://forum.xda-developers.com/sa...to/stock-rom-on5-flashable-metro-pcs-t3476919
Stock:
https://www.androidfilehost.com/?fid=24723757092307323
Remember that kies flashes the up to date stock rom so there's no need to download the stock one in my opinion

Echo_0408 said:
Rom:
https://forum.xda-developers.com/sa...to/stock-rom-on5-flashable-metro-pcs-t3476919
Stock:
https://www.androidfilehost.com/?fid=24723757092307323
Remember that kies flashes the up to date stock rom so there's no need to download the stock one in my opinion
Click to expand...
Click to collapse
Great now I have "An error has occurred while updating the device software. Use the emergency recovery function in the Smart Switch PC software" on the On5.
I have to grab that to fix it so I can use Kies? or do I just use that now? :crying:
EDIT: So I can still drop it into download mode. But Kies and Smart Switch recognize that something is getting added. What am I missing for recovery? ...
Also - SOS send halps!

I've also been there, place your On5 on download mode and go to kies, Tools, firmware upgrade and initialisation it will ask for device model and s/n (everything can be found behind the battery) oh and type everything in CAPS

Echo_0408 said:
I've also been there, place your On5 on download mode and go to kies, Tools, firmware upgrade and initialisation it will ask for device model and s/n (everything can be found behind the battery) oh and type everything in CAPS
Click to expand...
Click to collapse
Failed to run firmware update. Unknown Error Occurred. Thanks for you all your help in this matter. I think it might be dead. lol

I'm sorry friend but I have no idea to what to do next I've semi-bricked this phone more times than I can count and managed to bring it back to life every time, maybe it's the variant? I have the sm-g550t or t-mo variant..

Echo_0408 said:
I'm sorry friend but I have no idea to what to do next I've semi-bricked this phone more times than I can count and managed to bring it back to life every time, maybe it's the variant? I have the sm-g550t or t-mo variant..
Click to expand...
Click to collapse
Thanks for messaging back every time though It's the T-Mo version as well. I'm really at a loss at this point. Going to try one more time this weekend and see what I get. :cheers:
Oh man - I don't know what happened but it finally recovered. I think doing it at home made the difference. Thanks!