Guess I'll start at the beginning so nothing gets left out. I was rooted on OC1, downloaded FlashFire to update to OF1 . Flashed it, the phone rebooted and got stuck on the black Samsung Custom screen. I've tried to flash tar files of OC1 and everytime I put it or any kind of tar file in the AP slot of Odin, Odin becomes unresponsive and closes. I tried to load up the SD Card with OC1 and OF1 Roms and tried to flash those to see if that would do anything. The phone always says (in recovery at the bottom of the screen)- Manual mode, applling multi-csc...applied the csc-code-vzw. Then says below that, remove failed file '/system/csc_contents'(read-only file system. At the top it says Android system recovery so I'm assuming that's custom, I know its not Safestrap so I guess its FlashFires recovery? Anyway, when I try to flash a ROM it says,E:footer is wrong E:signature varification fail. I'm at a loss as to how to get the phone back, if its possible. I was always told that if the phone powers up, its recoverable, just not sure how. Any advice would be awesome, I've been messing with this thing since early yesterday and I really need my phone back!
....It seems as though I have stock recovery. Is there a way to flash a recovery through Odin?
have you tried using ODIN with I545_Downgrade_tC1.tar from [How-To] Update to I545_OF1 - 5.0.1 and KeepRoot by muniz_ri? ODIN tends to get stuck for a bit while loading the tar, as it is reading a 2gb file. You should probably leave ODIN alone for a few minutes after loading, and if it still has problems, maybe re-download ODIN or use a different comp.
Thanks for the response. I did try that file, actually that was the first one I tried but it didn't work. Actually while I was typing this I downloaded another Odin, put the OC1 neutered tar file and did what you said, left it sitting in AP. After 5 mintues or so it worked!!! I've been messing with this phone going on 3 days now and as I'm typing the phone has rebooted and now is in the setup wizard!! Thanks for the reply!
Related
I finally decided to update my AT&T Galaxy Note this Sunday. I already had a root on GB, so I decided to update to a ROM with root. I chose bigfau's {ROM}{UCLF6} Official ICS Stock Odexed, Deodexed, Rooted, Zipaligned, CRT ROM for the Note. However, when I went to update via Odin, I found out that I needed CWM.
Therefore, I found a GB rom with CWM, and installed that via Odin.
Then the phone restarted. It started just as normal, and I placed the ICS ROM (see above) on the internal SD card. I then restarted to CWM (this was the first time I had started CWM on this phone). I went and installed the ICS ROM via CWM. Apparently it came out fine (according to the screen). So I went all the way up, back to the original menu.
I chose the reboot option.
It rebooted, and the Samsung logo appeared.
The logo disappeared. And reappeared with more brightness.
So far, still normal.
Then the screen went black. No buttons I pushed did anything, no matter how long they were held. Only a battery reset would let me do anything with the phone. I took out the battery and put it back in, and restarted it in download mode, then re-flashed it with GB. Nothing happened. I re-flashed GB w/ CWM. Then I went back to CWM and tried installing ICS again. Same thing happened.
I went around looking for some helpful post on AndroidAuthority and XDA. Nothing.
I've run out of ideas.
So today, I ask for help.
Any help leading to a solution is appreciated.
If the .tar file using Odin did not restore the device, you can attempt the direct push of the recovery software from samfirmware.com.
That is the official website for firmware images, and the rom will contain "all " of the device files....and will restore the device if possible.
If the official method fails ....you may need a JTAG repair.
But since download mode still works, then the official restore will too ....g
The file is zipped!
gregsarg said:
If the .tar file using Odin did not restore the device, you can attempt the direct push of the recovery software from samfirmware.com.
That is the official website for firmware images, and the rom will contain "all " of the device files....and will restore the device if possible.
If the official method fails ....you may need a JTAG repair.
But since download mode still works, then the official restore will too ....g
Click to expand...
Click to collapse
Thank you, however, the file from samfirmware.com is a zip file, which I believe I'd need CWM to install (Odin only accepts tar files, as far as I can tell). However, when I unzipped it, I found a .tar.md5 file and a dll. What should I do now?
For clarification, I can't access the internal SD without it functioning, and I don't have access to a microSD card.
Unzip the file you got. The .tar file is in there.
I already did that.
I already did that. Like I said in the previous post, it contains a .tar.md5 and a .dll. What should I do next?
(Thanks for the suggestion, anyways)
the .tar.md5 is called a tarball and has the pda file, csc file, and modem file. just put the tarball in the pda section of Odin3 and flash. Make sure Kies isn't running in the background. Reboot is checked but nothing else is.
Just getting back ...
Many thanks for jumping in ranger ....
It sounds like the OP has it now ??
Time will tell I suppose ....g
So, after having my gnex, and being ruined by the automated flashing utility, I tried to root my note 2 Verizon. So, I first went and flashed to the stock 4.1.2 and then tried to put cwm on it via odin. Wont do it. Tried copying the files to the sd card and doing it locally, no go. So, I tried the automated one. Well, that seems to have put my phone into a constant loop where only Odin mode works. So, I started to flash the stock rom again via odin, and I get to the end of the flash, and it fails right at the end. I cant tell whats wrong. The phone gets all the way over too. It just fails. Ideas?
Also, side note, I also forgot to uncheck the repartition button in Odin when I did the last step. I did have the PIT file in there though for the mapping.
note 2 trouble
I used an online place to fix my note 2. Kind of a bummer but I had to ask for help. I used mobiletechvideos.com. give them a look online and a call and maybe they can help.
Hey all,
First, I just wanted to say that I have searched high and low for a solution to this already without much success, so I'm coming to you guys in sheer desperation; normally these forums and/or Google turn up the answer pretty quickly, but for once I am thoroughly stumped, so I'm coming to you sages for help.
tl;dr: After failing to unlock the bootloader through Odin (failure at sboot.bin), I re-installed a previously-working stock VRALJB ROM through Odin only to be met with a frozen Samsung boot logo and an inability to enter into recovery mode. I can get the phone into download mode, but that's it. Leaving the phone on for hours has given me no results, just the Samsung logo.
Background
Before I did anything last night that caused this current situation, the phone was running an unlocked/rooted (but otherwise stock) VRALJB ROM since I purchased it second-hand back in 2013. Actually, the bootloader may not have been unlocked as I had assumed, because what started all of this was me deciding it was time for a newer, better-optimized ROM. It was certainly rooted, as I had no issues running and granting root privileges to CWM and flashing the recovery loader. This was something I have done a dozen times for other people's phones (ah, hubris), so when everything appeared to be in order for me to boot into CWM's recovery mode, I did so, but was immediately greeted with Verizon's wonderfully-annoying Yellow Triangle-o-Death. I guess that's what I get for assuming the bootloader was unlocked.
I wasn't too worried; I had already backed up everything prior to attempting this, and I had Odin and my stock ROM ready to go should anything happen. So, I did exactly that: booted into download mode, connected the phone to Odin, and installed the stock VRALJB ROM. After about 6 minutes, the phone restarted and booted into a fresh, new stock version of Jelly Bean. There were no issues with the install, and the phone was working just as it should.
Where the problem started
So, now that I knew that the bootloader had never in fact been unlocked, I began searching down the process needed to unlock it so that I could then install a custom ROM. I began following the steps found on galaxynote2root.com's page for the SCH-I605, including downloading the "GalaxyNote2UnlockVerizon" archive will all the necessary tools (CASUAL, SuckItVerizon, etc).
**NOTE**: I know, now, that there were other, better options that existed and that I should have taken that path instead, but as it had been about a year since I had attempted any kind of flashing on my phone, I was rusty on the most current best-practices for unlocking the bootloader, and just went with the first tutorial I found that matched my phone model/firmware.
I loaded up Odin, included the option to re-partition with the included .pit file, placed the BootloaderBaseline2.tar.md5 file in the Bootloader section, and hit start. Everything was going great until Odin reached the infamous sboot.bin part of the bootloader; it failed at that moment, giving me the usual error message:
<ID:0/004> sboot.bin
<ID:0/004> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
"Okay, no biggie," I thought to myself. I must have done something wrong, or maybe the bootloader baseline file was corrupt.
Assuming I had just soft-bricked my phone, I went ahead and reset Odin, loaded up the sch-i605-16gb.pit file, the stock VRALBJ ROM I had just successfully installed 20 minutes earlier, told Odin to erase everything, and hit start.
Odin had no problem re-installing the ROM. It went through the entire process again in about 7 minutes, and I was happy to see the Samsung logo pop up at the end. Only problem was, though, that the Samsung logo stayed there.
"Damn it," I thought. So, I let it sit for a while, thinking that maybe something was happening in the background, but after 10 minutes, the logo was still there. Obviously, something had gone wrong in the install, so I decided I would boot into recovery mode, clear the cache, and to a factory restore now that the ROM was "successfully" installed.
Except I can't get into recovery mode. When I do the usual Volume Up-Home Button-Power Button combo, the Samsung logo appears as it should, but stops right there; it will not enter recovery mode.
Okay, so I can't fix it that way. I'll just go ahead and re-install the ROM through Odin again. After all, I had just used this exact same .md5 ROM file only an hour earlier and the phone booted fully and I had zero issues; so, I knew that the ROM file itself wasn't corrupted.
So I tried re-installing the ROM again through Odin, but got the same result: Samsung logo, with no ability to enter recovery. I tried again and again, and even went and downloaded another copy of the stock VRALBJ ROM in the hopes that maybe something was wrong with the one I was using.
Nope. Same results.
So now my phone is bricked, and I'm at a loss as to how to get it back. I have yet to try newer ROMs, only because I don't want to update to a newer stock version and lose the ability to unlock the bootloader; after all, the entire point behind last night's excursion into madness was so that I could load a custom ROM.
That said, if installing a newer stock ROM from Samsung/Verizon is the only way of fixing this, I will do it, but I was hoping there was another way that may allow me to stay on the VRALBJ ROM as a stepping-stone to another custom ROM.
I appreciate any help I can get, and I apologize for the wall of text, but I know how important background information is when trying to diagnose and fix these kind of problems, so I assumed you guys wouldn't mind
I hope someone has some advice for me. I've been racking my brain for three days trying to figure out this problem.
Bought a g900t from ebay that only bootlooped to samsung screen. DL mode and recovery both booted fine.
Tried just wiping everything in recovery - nothing but bootloop.
Tried getting custom recovery on via heimdall - no dice. PIT failed to download. (This issue is not related to Kies - different machines to avoid interference.)
Tried KIES 'Firmware Upgrade and Initialization'. KIES said it was successful. Bootloop.
Odin-ed both ANCH and CNK2 firmware. Both were successful according to Odin. After each flash, the phone restarted in recovery and went directly to the android image with the blue sphere and a loading bar underneath. Started to load something, then rebooted directly back to recovery with android, and over and over and over.... (20-30 times before I pulled battery).
The phone now will not boot to recovery (only to above mentioned recovery loop). DL mode still comes up.
Tried Kies again, and it pretends like it is going to install but once I press start nothing happens.
I can't find a ROM with clearly labeled extractable partitions, and I can't find the proper partition name list, so I am not going to start trying to force-flash the partitions through heimdall (don't want to get the aboot and boot mixed up, e.g.) if I can even get heimdall to work.
You need to use Odin to go back to stock. I have no clue what firmware the phone is currently on but it's most likely lollipop. Here is a link for the 5.0 download http://forum.xda-developers.com/showthread.php?t=3034334
I use Odin 3.07 and have not had issues for years. Download the stock rom from the link mentioned and extract it somewhere easy to find. Once you extract it you will end up with a .tar file. Open Odin
Put phone in download mode and plug it in.
Make sure the COM tab lights up.
Click on pda and find the .tar file you extracted. Once found click open or double click it.
Odin will freeze while it loads the .tar file so be patient and don't freak out.
Wait til you see the file location load in the pda tab.
Once file loads up click start and profit.
Good luck!
Sent from my SM-G900T using XDA Free mobile app
Hi,
Thanks for the reply. As I mentioned above in the fifth paragraph, I tried two different firmwares through Odin.
I took the phone to BestBuy the other day and one of the Samsung Experience Center staff spent well over an hour reflashing the stock firmware using their setup and the phone still won't get past either a standard bootloop (first screen) or a recovery bootloop. He suggested sending it in under warranty (Knox still reads 0x0) and so it went out in the mail yesterday. Hopefully I get a functioning phone back.
On the bright side, the S.E.C. inside BestBuy seems to be a viable option for those who have a brick and don't have access to Odin/Heimdall.
This firmware is the unmodified Lollipop (Android 5.0) firmware downloaded through Samsung Kies. In case you need a copy of the firmware so that you don't have to keep downloading it through Kies, I'm providing you with a copy via the link below. It's odin flashable. Use the "AP" or "PDA" button to flash it onto your phone.
1. Download the stock Android 5.0 ROM (Lollipop) - Sprint N900P ONLY! - androidfilehost.com/?fid=24391638059060029
2. Download the official Samsung Kies. - samsung.com/in/support/usefulsoftware/KIES/
3. Download Odin 3 or later. - samsungodindownload.com/download/
4. Open Samsung Kies, and connect your phone. Wait for it to install the needed drivers.
5. Open Odin and make sure that it says it's "Added!"
6. Click the "AP" button and open the downloaded ROM.
7. Wait for it to finish verifying the checksum.
8. Make sure that "Auto Reboot" and "F. Reset Time" are the only boxes checked. (The default)
9. Click "Start" and wait for it to go. (Sometimes it gets stuck when it says "Setup Connection" and then you need to unplug your phone and restart Odin. - BE CAREFUL! Make sure it really is stuck or you'll brick your phone!)
10. [Optional] Flash TWRP (twrp.me) or CWM. (clockworkmod.com) TWRP is more free than CWM in the sense that the CWM ROM Manager has a payware version. If you're feeling generous towards those who spend countless hours each day for fun and to make your life a bit easier, throw them a few bucks. Both are freely available.
WARNING: Odin can brick your phone if you don't know what you're doing. If you break it, just buy another $800 device. I'm providing these instructions and the ROM without any warranty. You do with them what you feel is best.
That this is a zip file, it is not seen my Odin.
THANK YOU THANK YOU THANK YOU! You helped me save what I thought was a dead phone with this!
Is there a mod to change the launcher to 5x4
mac01843 said:
That this is a zip file, it is not seen my Odin.
Click to expand...
Click to collapse
Not sure if you've figured it out yet but you'll have to extract the .tar file from the zip, then Odin will be able to see it, the .tar file that is.
Thank you, thank you, thank you. This totally saved my bacon after a moron at the Sprint Store (and perhaps me for letting him look at it) replaced the SIM and then said that there was nothing they could do for the phone since it had been rooted.. now I have a way to reactivate the phone before switching back to a decent ROM.
This worked like a charm!
Anyone have a mirror?
I get a 404.
Also, will this upgrade my baseband from OC5 to OK2? I am having issues with CM12.1 nightly where I am not getting LTE and I was hoping upgrading the baseband could help. A bit of a noob here so any sort of suggestion would be helpful.
can I keep it unlock?
Can I keep my KITKAT 4.4.2 NOTE 3 Sprint unlocked after updating this stock firmware? I'm newbie and English is not my mother tongue.
Yes you can!
Anyone? On CM as well and would looove to have an Odin flashable Stock ROM
tusker559 said:
I get a 404.
Also, will this upgrade my baseband from OC5 to OK2? I am having issues with CM12.1 nightly where I am not getting LTE and I was hoping upgrading the baseband could help. A bit of a noob here so any sort of suggestion would be helpful.
Click to expand...
Click to collapse
Or maybe point me (us) in the direction of finding something similar?
Anyone else getting invalid MD5 checks in ODIN with this one? Does anyone have an valid download link? Trying to switch back to Stock so I can pull the 6.0 OTA and fix my GPS issues.
Edit:Georgia Mirror is valid
So I used the process, flashed over to stock and had the phone boot up to the Updating 292 Apps then rebooted and now it's sitting on the yellow Sprint boot screen. Blue LED fading in and out with the screen going brighter for a second with a light vibrate at the same time. Has been like that for several minutes now and not sure if I should try to flash again or what. Anyone have any advice?
iletumi said:
So I used the process, flashed over to stock and had the phone boot up to the Updating 292 Apps then rebooted and now it's sitting on the yellow Sprint boot screen. Blue LED fading in and out with the screen going brighter for a second with a light vibrate at the same time. Has been like that for several minutes now and not sure if I should try to flash again or what. Anyone have any advice?
Click to expand...
Click to collapse
Same here. Been waiting about 10 minutes now watching the Sprint screen do the exact same thing.. Giving it another 10 or 15 minutes just to make sure then I guess I'll try again?
Update #1: Tried again and still stuck. I'm at a loss. Pissed at myself for not having a backup since my SD card went down. Anyone with any guidance would save me.
Update #2: Pulled battery. Rebooted into stock recovery and did a factory reset. Phone booted up. Crisis averted.
how did you access the georgia mirror?
404 error on file link.
Nevermind. Tried again and it downloaded.
misterkatanga said:
Same here. Been waiting about 10 minutes now watching the Sprint screen do the exact same thing.. Giving it another 10 or 15 minutes just to make sure then I guess I'll try again?
Update #1: Tried again and still stuck. I'm at a loss. Pissed at myself for not having a backup since my SD card went down. Anyone with any guidance would save me.
Update #2: Pulled battery. Rebooted into stock recovery and did a factory reset. Phone booted up. Crisis averted.
Click to expand...
Click to collapse
Factory reset and it works now! Thank u!!!!