Somebody please help! I am racking my brain on why i cannot load the OA6 full restore onto my sprint G900P. I had no problem restoring the leaked NKD Lollipop and have been running on it for some time. When i load the new software Odin 3.09 loads all the files and when its done the stock recovery does dot boot it stays at the samsung splash screen and freezes when it says " opening recovery" and never loads or continues.
The second thing that is strange is is it will not allow me to revert back to the stock NE5 firmware either. I am basically stuck on the NKD firmware. Some instruction would help, thank you.[/QUOTE]
Related
Hi.
Well I have a U.S. Cellular SCH-R530 I received from a friend. He already upgraded to 4.3 OTA and I figured I would try to root the phone so I could install custom roms. I downloaded Odin and downloaded cwm 6.0.4.5. I put the phone in download mode and tried flashing cwm.. Well Odin failed, I cannot boot back into the Android OS and I have the screen with the message: "firmware upgrade encountered an issue, etc.". I pulled the battery and put the phone in download mode and I have try flashing cwm again, flashing USCC stock rom and I still get a fail in Odin 3.07 & 3.09. I did use PDA or AP in Odin when I tried to flash both the cwm and the stock 4.3 rom. At this point, I'm trying to figure out how to get the s3 working again.
Nevermind fixed my issue. Please delete thread.
Hi,
Being a newbie to this flashing thing. I rooted/SUsered and I had Google Apps running ok on 4.2.2 Android happily on this GT-i9502 from China...
Then I decided to try and update to 4.3. Dumb.
It's current state is: If I try to re install 4.3 latest factory stock in Odin 3.07 it fails at SYSTEM bit. then I have to put CWM back onto it to get it to do anything again (It goes into that yellow triangle screen only.)
I've tried wiping cache etc. But still no joy with Firmware restore from PC - Odin. I'm now in a cycle of Fail firmware restore then CWM to un-Brick it slightly… I can get into CWM but normal start up is just the China UNICOM splash screen then blank…
Also I might have formatted the data a few times…
I didn't do a back up of 4.2.2 either, I know I'm an idiot. :crying:
On the downloading screen in ODIN mode it says
CURRENT BINARY: Custom
SYSTEM STATUS: Custom
WARRANTY BIT: 1
Have I really messed it up?
Also if I try to install 4.2.2 official stock again it says: Unsupported Version
What can I try next? Flashtool?
Thanks
D
Hello everyone, I need some help here.
I downloaded the latest from sammobile
G900PVPU3CPG1_G900PSPT3CPG1_G900PVPU3CPG1_HOME.tar .md5
and ODIN v3.12.3
I placed the tar file in the AP slot, installed everything, I receive the final okay and the phone reboots to the stock samsung boot animation, and just sits.
Does anyone have any idea why I can't seem to get past the boot animation?
I can pull the battery and install TWRP, and boot to recover fine, but no matter how long the device will NOT get past the boot animation.
Is it possible that I have a bad download? Can I "downgrade" to PE2, without risk of bricking the device somehow?
thanks
Before clicking Start on odin, did you uncheck everything else (autoreboot, f-reset time, re-partition)? I followed all the steps here for that same firmware. It worked for me on first try. Also, did you download the appropriate version for your phone? From what I can see there are 4 versions on sammobile, VMU, SPR, XAS, and BST. I have a Virgin mobile phone, so i got the one with product code VMU.
welp I went back to old tried and true V3.09 and used PE2, and then let it boot after a LONG TIME. Then I upgraded to PG1 using the update feature in "about device".
Not sure why I could not use the latest PG1 tar file, direct from sammobile.
Curious though, has anyone been able to "downgrade back to lollipop, just in case? Or has Samsung locked it down.
I tried to go back to OA6, and also OK4 and I got a fail (red) in ODIN using both sammobile stock files.
Amd4life said:
welp I went back to old tried and true V3.09 and used PE2, and then let it boot after a LONG TIME. Then I upgraded to PG1 using the update feature in "about device".
Not sure why I could not use the latest PG1 tar file, direct from sammobile.
Curious though, has anyone been able to "downgrade back to lollipop, just in case? Or has Samsung locked it down.
I tried to go back to OA6, and also OK4 and I got a fail (red) in ODIN using both sammobile stock files.
Click to expand...
Click to collapse
You may have to boot into recovery and factory reset once ODIN has successfully flashed. Should boot after that.
Sent from my SM-G900P using XDA-Developers mobile app
Hey guys I need some help please. I am a bit of a noob and was trying to flash the PartCyborgRom using the BootLoopEdition firmware onto my originally G955U (which I had flashed with the G955U1 FW a while ago). And after I flashed the PartCyborgRom AP file through Odin, nothing happened as in the instructions, so I tried resetting the phone and continued to next step (not a good idea on my part) then I loaded the BL file and midway through that Odin gave me a "FAIL!" and the phone is stuck on Download Mode with the following error "SW REV CHECK FAIL : [system]Fused 2 > Binary 1".
I tried going back to stock and flashing all of the stock fw through Odin, but anytime I try to flash anything I get that same error. If I try to reboot the phone normally it tries to upgrade system but looks like nothing is on the phone anymore and is on bootloop. I am not sure what to do, did I **** up really bad and brick my phone?
I can't even get back into Recovery mode! It simply goes on a boot loop where it doesn't find anything in the system.
PS. when I tried to flash the PartCyborgRom my S8+ was on the latest G955U1 fw.
sebisuarez10 said:
Hey guys I need some help please. I am a bit of a noob and was trying to flash the PartCyborgRom using the BootLoopEdition firmware onto my originally G955U (which I had flashed with the G955U1 FW a while ago). And after I flashed the PartCyborgRom AP file through Odin, nothing happened as in the instructions, so I tried resetting the phone and continued to next step (not a good idea on my part) then I loaded the BL file and midway through that Odin gave me a "FAIL!" and the phone is stuck on Download Mode with the following error "SW REV CHECK FAIL : [system]Fused 2 > Binary 1".
I tried going back to stock and flashing all of the stock fw through Odin, but anytime I try to flash anything I get that same error. If I try to reboot the phone normally it tries to upgrade system but looks like nothing is on the phone anymore and is on bootloop. I am not sure what to do, did I **** up really bad and brick my phone?
I can't even get back into Recovery mode! It simply goes on a boot loop where it doesn't find anything in the system.
PS. when I tried to flash the PartCyborgRom my S8+ was on the latest G955U1 fw.
Click to expand...
Click to collapse
You are trying to flash old firmware. It sounds like you are already on firmware with the v2 bootloader and you're trying to flash firmware with rhe v1 bootloader. You need a stock firmware that has a 2 before the last four digits of the firmware name.
Firmware
It should be all well and good flashing stock firmware with the number 2, but I can't find any on XDA and any links outside either fail or try to make you pay because it's over 2GB... If anyone has a copy and space on their google drive, I'd be very grateful for a valid download link!
btuck812 said:
It should be all well and good flashing stock firmware with the number 2, but I can't find any on XDA and any links outside either fail or try to make you pay because it's over 2GB... If anyone has a copy and space on their google drive, I'd be very grateful for a valid download link!
Click to expand...
Click to collapse
Try sammobile.com.
Free download of the latest firmwares but might be a little slow.
Does anyone have a stock tar file for SGH-I577, I missed to update version on my old phone which was at gingerbread & the manual firmware update (nightlies) did not flash properly.
The phone is stuck at Samsung logo and At&T does not pop up. I need the stock firmware to unroot and try the upgrade again.
Appreciate your help with this.