[Q] rom help please!! - AT&T, Rogers, Bell, Telus Samsung Galaxy S III

okay so i have 5 files that came with a stock gs3 i747 recovery folder, and im trying to place them in odin to fix my soft bricked phone. the files start with...
AP
BL
CP
CSC
D2.pit
i know where d2, csc, and bl go on odin, but im not sure about the other 2... please help someone :/

Is the bootloader from the recovery older than the bootloader on your phone? IMHO, confirm the bootloader version on the phone before attempting to flash.
Attempting to downgrade a 4.3 bootloader or flashing an incompatible mode/bootloader combination could brick your phone.
Are the files in a tar.md5 format? Think this is the only format that Odin will recognize.

audit13 said:
Is the bootloader from the recovery older than the bootloader on your phone? IMHO, confirm the bootloader version on the phone before attempting to flash.
Attempting to downgrade a 4.3 bootloader or flashing an incompatible mode/bootloader combination could brick your phone.
Are the files in a tar.md5 format? Think this is the only format that Odin will recognize.
Click to expand...
Click to collapse
im not 99 percent sure of the current bootloader on the phone right now, but my closest guess would be the bootloader from the I747UCUEMJB package i downloaded cause i used this package in the past to fix my phone which was soft bricked like it is now. oh and i figured out where to place everything on odin, but when i start it ends up failing.. heres the text im getting.
<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> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> sbl1.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> sbl2.mbn
<ID:0/005> sbl3.mbn
<ID:0/005> aboot.mbn
<ID:0/005> FAIL! (Auth)
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

<ID:0/005> aboot.mbn
<ID:0/005> FAIL! (Auth)
Looks like you are trying to downgrade the bootloader.

so i loaded the recovery from the folder in odin, and now my phone was on the att logo screen for at least 3 mins, then i went through setup and its saying theres an application preventing wifi from working.

What boot loader and modem are on your phone?

"UPDATE" i booted the phone in safe mode to check if there was an app blocking my wifi from turning on, and it still didnt work. so that means i need to reinstall my 4.3 firmware right?

I think you need a modem to match your bootloader.

Related

[Q] [SprintGNEX] BrickedGoogle boot screen, all my flashes seem to take, though.

Just as it says in the title. I flashed an AOKP nightly, like I do, and within a day, I had nothing but the black and white google screen. I figured it it was a bad flash, I would have had that right off the bat. I've followed every "flash back to stock" tutorial I can find, My guess is that it has to do with flashing over to a 4.2.2 rom, and then trying to ODIN back to practically every stock I could find.
Here's the weirdness: all the flashes, both fastboot and ODIN *appear* to work just fine, then no full reboot.
What the hell did I do, and what can I do to fix it? Even if I can just get it to appear locked so I can get it back to Sprint, that would be awesome.
Have you tried the Galaxy Nexus Toolkit?
I've tried that toolkit, and Wugfresh. In wugfresh, you can boot an new boot image without flashing it. When I do that, I can get past the logo, but to a black screen.
Fastboot flashing gets me the same results.
Did your phone overheat on 4.2.2? If so, you may have damaged the GPU. Can you get into Recovery? I'm thinking that the 3D GPU is damaged, but the 2D is still operational. Perhaps you can edit a ROM to force 2D rendering before flashing it.
The only available modes are fastboot and download. Main android and recovery will not boot. It's possible I overheated it, but I don't OC. I'm nowhere cool enough to edit a reom in the way you just described. I just tried to flash a GA02 image I found through fastboot, and noticed that the baseband versions haven't changed, and when I "fastboot oem lock", I still got a unlocked padlock on the Google screen.
When I tried to get into recovery, it hung on the TWRP screen (I've flashed stock recovery several times). ADB recognized the phone, and I was able to "adb reboot", but straight to an unresponsive black screen. It's like there is nothing there.
Can you post the output of Odin Mode (Downloading...)?
I will tomorrow. Until then, Last thing I did was let it try to get to recovery. it did, but froze after a couple of seconds of menu selection.
Odin output
<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> recovery.img
<ID:0/005> NAND Write Start!!
<ID:0/005> system.img
<ID:0/005> userdata.img
<ID:0/005> boot.img
<ID:0/005> radio-cdma.img
<ID:0/005> bootloader.img
<ID:0/005> radio-lte.img
<ID:0/005> Transmission Complete..
<ID:0/005> Now Writing.. Please wait about 2 minutes
<ID:0/005> Receive Response form LOKE
<ID:0/005> RQT_CLOSE !!
<ID:0/005> RES OK !!
<ID:0/005> Removed!!
<ID:0/005> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
Click to expand...
Click to collapse

Soft Bricked? Help

Flashed stock firmware on the bootloader section of ODIN instead of PDA on COMPLETE accident... Phone doesnt boot, but My phone goes to download mode.. but now it wont flash the firmware under PDA, what are my steps?
if i turn on normally it just goes to screen that says ( choose recovery or kies, ) but there no option to choose recovery
( was stock before )
do i need to ODIN flash a bootloader? If so I havent been able to find one
Thanks!!!!!!
Now when i try to ODIN flash stock firmware properly i get :
<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> aboot.mbn
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Pretty sure you will have to Odin the correct boot loader if it's not letting you flash the firmware from PDA.
I'm just not sure what to flash there. I know of 4 separate bootloaders that we have:
aboot - Application Secondary Bootloader
Sbl1
Sbl2 - Secondary Bootloaders 1-3
Sbl3
My best guess from what I've been looking at would be to flash the aboot.mbn from the stock firmware. But it is purely a guess and I wouldn't feel comfortable trying it unless someone can confirm.
But maybe that can at least help you or someone else find the correct answer if nothing else. I'll look some more and will let you know if I find anything.
The Verizon guys have done a lot of work with their bootloaders since theirs is locked by the carrier. You may find some info in their forum too.
Sent from my SGH-T999V using xda premium
Thanks that sounds like the right direction hopefully.someone can chime in further with which files to Odin flash

im stuck on download mode

im trying to restore my phone back to full factory (removing root,recovery) everything back to stock and i got the samsung image and im getting fail on odin what can i do?
crimedave1987 said:
im trying to restore my phone back to full factory (removing root,recovery) everything back to stock and i got the samsung image and im getting fail on odin what can i do?
Click to expand...
Click to collapse
<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> sbl2.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
as what i remember when i brought my phone over 2 months ago i think i have the latest FW and i had to flash a zip to downgrade the SW VER.
and rooted now i just went to DOWNLOADING MODE and tried flashing the stock rom and i got whats above i cant get to to recovery or nothing
nevermind its fixed (cable issue)
crimedave1987 said:
nevermind its fixed (cable issue)
Click to expand...
Click to collapse
Just came across your thread.
Thanks for posting your solution.
Yes, the usb cord can be, and is often the culprit.
No doubt reading this thread will help others that find themselves in a similar situation

Help with Odin error

Hello everyone.
Recently I flashed the Note4Mini Rom available here in the forum. I really like it. Only had a couple of minor issues, however it had a huge issue for me: I couldn't play Hearthstone with it.
So I decided to flash back to the Stock Rom. I downloaded the Portuguese version for my Smartphone (SM-N7505), since I am Portuguese, but when I try to flash it via Odin this is my log file.
<ID:0/005> Odin engine v(ID:3.1005)..
<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> SingleDownload.
<ID:0/005> sboot.bin
<ID:0/005> NAND Write Start!!
<ID:0/005> boot.img
<ID:0/005> recovery.img
<ID:0/005> system.img
<ID:0/005> modem.bin
<ID:0/005> cache.img
<ID:0/005> hidden.img
<ID:0/005> FAIL!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
And I get the error saying that there was a problem flashing the software and to connect to kies and do the phone recovery thingy. That doesn't work. Kies does not detect the phone (Yes, I installed the drivers and tried both Kies2 and Kies3 and I'm running everything as admin)
Any help will be appreciated I kinda need the phone. I also had it rooted and TWRP installed. I don't know if I still have it after trying to flash the stock ROM but I can't access it anyway.
Cheers.
Quaekk said:
Hello everyone.
Recently I flashed the Note4Mini Rom available here in the forum. I really like it. Only had a couple of minor issues, however it had a huge issue for me: I couldn't play Hearthstone with it.
So I decided to flash back to the Stock Rom. I downloaded the Portuguese version for my Smartphone (SM-N7505), since I am Portuguese, but when I try to flash it via Odin this is my log file.
<ID:0/005> Odin engine v(ID:3.1005)..
<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> SingleDownload.
<ID:0/005> sboot.bin
<ID:0/005> NAND Write Start!!
<ID:0/005> boot.img
<ID:0/005> recovery.img
<ID:0/005> system.img
<ID:0/005> modem.bin
<ID:0/005> cache.img
<ID:0/005> hidden.img
<ID:0/005> FAIL!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
And I get the error saying that there was a problem flashing the software and to connect to kies and do the phone recovery thingy. That doesn't work. Kies does not detect the phone (Yes, I installed the drivers and tried both Kies2 and Kies3 and I'm running everything as admin)
Any help will be appreciated I kinda need the phone. I also had it rooted and TWRP installed. I don't know if I still have it after trying to flash the stock ROM but I can't access it anyway.
Cheers.
Click to expand...
Click to collapse
Check whether you are trying to install a downgraded firmware. It will not allow you to downgrade your firmware.
Ok I solved it. I flashed TWRP using odin and it worked and then the phone rebooted into TWRP and showed an error ( which I couldn't read because it was too fast) and then booted into a fully working android (The ROM I was trying to flash). The phone is now 100% working. Thanks for the help anyway.
Actually this issue happen from latest 10 FW, I always flash custom recovery or root to solve it.

Samsung T320 Bootloop / ODIN Help

Hope someone can assist here, feel like I have tried everything, and cannot get the issue resolved. Have spent 10+ hours, but many of the resources are outdated, or the links are no longer valid for downloads - understandable since a 6 year old device.
Took out my T320 after a while, and figured I would use it, turns out still on KitKat, so not much you can do with it. Figured I'd root, then flash Colt or Lineage on the Tab Pro.
Root was successful, TWRP recovery was successful as well, but then the flash was not working and caused a bootloop issue. Long story short, I am only able to get into Download mode, and unable to flash the stock US firmware, because I cannot find a working link anywhere.
ODIN allows me to flash BL, but get the error below when I select a tar to flash in the AP. Hope someone knows what the export below could point to as to why I cannot flash Lineage or Colt.
First part is for the BL - which is successful, second one is the ROM, which is a fail.
Nutshell -
Bootloop but able to get into Download mode
Cannot access Recovery
Kies does not recognize but ODIN does
<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> SingleDownload.
<ID:0/005> recovery.img
<ID:0/005> NAND Write Start!!
<ID:0/005> RQT_CLOSE !!
<ID:0/005> RES OK !!
<ID:0/005> Removed!!
<ID:0/005> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
<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> SingleDownload.
<ID:0/005> PK
<ID:0/005> NAND Write Start!!
<ID:0/005> FAIL!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
@xcobrax81 as you don't have the firmware yet try samfirm_reborn tool.
Search for it, doesn't have to be installed.
I guess you can take the canadian version, but I'm not sure as I live in Europe.
Get rid of Kies IMO it causes to much problems, just use Samsungs USB device drivers instead. That's what I do and it works fine.
Don't understand which ROM you were trying to flash with Odin as you said you don't have stock firmware.
Any custom ROM can only be flashed via TWRP.
Btw, which one did you try?
On my T325 I use 3.4.0-0.
bmwdroid said:
@xcobrax81 as you don't have the firmware yet try samfirm_reborn tool.
Search for it, doesn't have to be installed.
I guess you can take the canadian version, but I'm not sure as I live in Europe.
Get rid of Kies IMO it causes to much problems, just use Samsungs USB device drivers instead. That's what I do and it works fine.
Don't understand which ROM you were trying to flash with Odin as you said you don't have stock firmware.
Any custom ROM can only be flashed via TWRP.
Btw, which one did you try?
On my T325 I use 3.4.0-0.
Click to expand...
Click to collapse
Thanks for the guidance, I'll try that this week. Tried Colt and Lucid (the top 2 I found on this forum)
But I think it's more me than any issues with the ROMs

Categories

Resources