Related
Hey Everyone! So long story short, I ended up picking up a 8.9 tab and now we have a 100% confirmed working ClockworkMod Recovery!
So, quick and dirty instructions for users WITHOUT any form of CWM recovery on their device:
1) Download the attached ClockworkMod_Recovery_v5.5.0.4.tar
2) Reboot the tab into download mode
3) Fire up Odin 1.85 and put the ClockworkMod_Recovery_v5.5.0.4.tar in the PDA field.
4) Flash!
5) Reboot into ClockworkMod Recovery
Quick and dirty instructions for users WITH some form of CWM recovery on their device:
1) Download the attached ClockworkMod_Recovery_v5.5.0.4.zip to your device
2) Reboot the tab into recovery
3) Install the zip
5) Reboot
If, for any reason, you want to return to the stock recovery, simply download the P73xx_Stock_Recovery.tar and follow the instructions above (with odin)!
DISCLAIMER: THIS WILL NOT WORK WITH LTE TABS!
I kinda "bricked" my tab yesterday trying to create a recovery.
Now it just continually boots to the splash screen then restarts.
I can not get into recovery.
I can get into download.
I tried the ClockworkMod Recovery v5.0.2.6 but odin just hangs after setup connection.
Trying to download the stock recovery:
<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> recovery.img
<ID:0/003> NAND Write Start!!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Any ideas?
Thanks,
-dana
Thankfully Samsung devices are notoriously hard to brick
So is the tab still booting into the OS? Or are you ONLY able to get to download mode?
Also, what did you do to try and create a recovery and what did you flash? If I can understand what has been done I can help you get up and running again
As for Odin hanging at "Setup Connection" when you tried to flash my recovery, it is likely just coincidence more than anything. Odin isn't the most dependable application...well, it is and it isn't...but getting stuck at Setup Connection is a common issue.
First tell me what you did yesterday so we can figure out how to proceed. Then we'll go from there!
I kinda want to volunteer as I am familiar with ODIN coming from a Vibrant but what's stopping me is 3 questions with all due respect. What's the related thread you were talking about at the OP? Are you sure that is the right 8.9 Stock Recovery? How did you find it as there is (at least) no American ODIN image as of today (checked Samfirmware as of this post)?
nirogu325 said:
I kinda want to volunteer as I am familiar with ODIN coming from a Vibrant but what's stopping me is 3 questions with all due respect. What's the related thread you were talking about at the OP? Are you sure that is the right 8.9 Stock Recovery? How did you find it as there is (at least) no American ODIN image as of today (checked Samfirmware as of this post)?
Click to expand...
Click to collapse
Excellent -
This is the thread I was talking about in 10.1 section:
http://forum.xda-developers.com/showthread.php?t=1307242
The recovery is standard, regardless of region. In fact, with the exception of precompiled binary modules, the recovery is even identical to that of the 10.1 tab
What I have done here is repacked the recovery image with a vanilla build of clockworkmod. This should work on both the P7300 and the P7310.
Give it a shot and let me know how it goes!
Neither got flashed via ODIN, but I too tried to install CWM yesterday via the market app so my recovery is messed up to start with.
After trying to flash the two the tab wouldn't boot and I got an error about a failed update.
Flashed the bootloader file below with ODIN to get it to boot.
Code:
ID:0/010> Added!!
<ID:0/010> Odin v.3 engine (ID:10)..
<ID:0/010> File analysis..
<ID:0/010> SetupConnection..
<ID:0/010> Initialzation..
<ID:0/010> Get PIT for mapping..
<ID:0/010> Firmware update start..
<ID:0/010> recovery.img
<ID:0/010> NAND Write Start!!
<ID:0/010>
<ID:0/010> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Hmm ok...
So yesterday you tried the market CWM, which caused the tab not to boot at all? Then, you had to flash the bootloader to make it boot again?
I'm assuming you had a booting tab prior to trying to flash these files, but still had the borked recovery yes?
That is correct, but the recovery was fine when i got the device, I used it to root.
I know I should do a full flash but I don't want to lose all my stuff.
Also flahing the bootloader somehow removed the cwm ?script? That was forcing the tab to try and boot into the borked recovery on each boot.
Damn that app does a number on the poor tab...unfortunately the best course of action is really to completely restock the thing - flash an entire rom through Odin with a repartition.
Since you are able to boot, you can back up all your data with Titanium backup, then move the data off your internal storage and onto your computer in case it gets wiped by the Odin flash.
Now i really wish I had an 8.9 because I'm curious if someone who hasn't got the messed up recovery tries to flash my file if it will go through or fail like yours and the Geologist.
Any takers?
alterbridge86 said:
Now i really wish I had an 8.9 because I'm curious if someone who hasn't got the messed up recovery tries to flash my file if it will go through or fail like yours and the Geologist.
Any takers?
Click to expand...
Click to collapse
That'd be me. Once I backup my apps, I will (give me some minutes and I will post the result as an EDIT post). If it fails, worst case scenario would be flashing the Asian ODIN image since it is the only one available. That one displays everything in Chinese but I can change the language. Sidenote: Damn I wonder what is taking so long to bring an American ODIN image of the 7310 live???
nirogu325 said:
That'd be me. Once I backup my apps, I will (give me some minutes and I will post the result as an EDIT post). If it fails, worst case scenario would be flashing the Asian ODIN image since it is the only one available. That one displays everything in Chinese but I can change the language. Sidenote: Damn I wonder what is taking so long to bring an American ODIN image of the 7310 live???
Click to expand...
Click to collapse
Excellent! Let me know how it goes!
alterbridge86 said:
Excellent! Let me know how it goes!
Click to expand...
Click to collapse
It does not flash. This is what ODIN shows after following instructions:
<ID:0/010> Added!!
<ID:0/010> Odin v.3 engine (ID:10)..
<ID:0/010> File analysis..
<ID:0/010> SetupConnection..
<ID:0/010> Initialzation..
<ID:0/010> Get PIT for mapping..
<ID:0/010> Firmware update start..
<ID:0/010> recovery.img
<ID:0/010> NAND Write Start!!
<ID:0/010>
<ID:0/010> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
EDIT: Oh well...it's been a while since I last saw a "device-!-PC" screen.
EDIT 2: The "device-!-PC" screen vanished after one or two restarts as if nothing ever happened.
That's really weird, because I can even flash the p73xx stock recovery on my 10.1 tab and it at least goes through...it won't boot into recovery, as expected, but it at least FLASHES...
Maybe next question - are you guys using Odin 1.85? Also, are you using the driver from Kies or did you install a standalone driver? Try installing this driver:
http://www.multiupload.com/ISBTL9TADO
And then flashing after. It also may be worthwhile to switch USB ports after installing the new driver. Don't mind the p7510 in the file name, it works with multiple devices.
alterbridge86 said:
That's really weird, because I can even flash the p73xx stock recovery on my 10.1 tab and it at least goes through...it won't boot into recovery, as expected, but it at least FLASHES...
Maybe next question - are you guys using Odin 1.85? Also, are you using the driver from Kies or did you install a standalone driver? Try installing this driver:
http://www.multiupload.com/ISBTL9TADO
And then flashing after. It also may be worthwhile to switch USB ports after installing the new driver. Don't mind the p7510 in the file name, it works with multiple devices.
Click to expand...
Click to collapse
Yes, ODIN 1.85. Will install that driver and see how it goes.
EDIT: Same result as pointed earlier, even after installing the quoted driver and changing USB ports.
EDIT 2: Wait a second. I think I might have figured it out. This does not work on an encrypted system, right? I think I'll unencrypt and then try doing this.
EDIT 3: Nope, unencrypted or not, it does not flash. Same result.
Sent from my GT-P7310
Well, I have good news and bad news...lol
I was strolling through best buy this evening after dinner and made an impulse purchase...i'm now the new owner of a Galaxy Tab 8.9
EDIT (10/22/11): We're back open! Confirmed working STOCK recovery is in first post...confirmed working CWM recovery coming momentarily
EDIT 2 (10/22/11): And we're official. ClockworkMod is 100% working Enjoy guys!
Now on to my next project...making this thing FASTER
Confirmed working CWM-Recovery . Doing a NANDROID backup as of this post.
Working great, thanks.
Sent from my GT-P7310 using Tapatalk
Works perfectly on my gtab P7300 and ki1 rom.
Thanks for your job !
Now, wait noTW rom !
work perfectly on my gtab P7300 asia
AWeSOME
Thanks, working perfectly on my gtab 7300 as well. So glad you are one of us now, looking forward for your overcome roms
i have been trying to install stock Lollipop on my device. i have followed both http://www.androidpit.com/how-to-get-android-5-0-lollipop-on-the-galaxy-note-3 and http://techbeasts.com/2015/02/14/update-galaxy-note-4-n910f-android-501-lollipop-official/ to the letter. This is also my fourth or fifth time using Odin. Every attempt has failed. i have tried Odin 3.10, 3.09, and 3.07 and got the same results:
Code:
<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> sbl1.mbn
<ID:0/006> NAND Write Start!!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
My phone's download screen gave thisd message:
Code:
Secure Check Fail : sbl1
until i switched from "N9005XXUGBOB6_N9005XEOGBOA4_XEO" to "N9005XXUGBOA5_N9005XEOGBOA4_XEO" and also freezing any anti-theft app that may be locking my device somehow. Now the screen says:
Code:
Secure Check Fail : aboot
i am rooted (running Omega 24) and to be sure, i re-flashed auto-root
i have tried 4 different USB cables
No USB hubs, i am connected directly to my PC
Firewall, AntiVirus, and Anti Malware software are all off.
i have run Odin as admin
Reactivation Lock is not ticked
Some other things me screen says that may be of some help are:
Code:
QUALCOMM SECUREBOOT: ENABLE
followed by some coupling of letters and numbers and:
Code:
Write Protection: Enable
i am hoping that a factory reset can be my very last resort. i am contemplating reflashing my current Omega ROM and then retrying this.
Any ideas?
EDIT: Factory Reset did not change anything
Is your device unlocked or branded?
Joku1981 said:
Is your device branded or unlocked?
Click to expand...
Click to collapse
It should be unlocked. i unlocked it a while ago when i flashed my first ROM. i have been flashing Omega roms ever since. i cannot imagine my phone would lock itself back up...
billybag said:
It should be unlocked. i unlocked it a while ago when i flashed my first ROM. i have been flashing Omega roms ever since. i cannot imagine my phone would lock itself back up...
Click to expand...
Click to collapse
Odin gave you fail in the NAND. This mean that you have lost plenty of files in EFS. Try to restore your OMEGA backup.
Joku1981 said:
How you unlocked it? By IMEI or other method?
Click to expand...
Click to collapse
Damn, i don't remember. It seemed so long ago. i don;t suppose there is a way to check...
EDIT: while attempting a restore of a nandroid backup, i noticed something. The following backup files were missing:
.android_secure.vfat.tar and
.android_secure.vfat.tar.a
i REALLY appreciate your time and help, by the way. This is so frustrating. One person told me that they repartitioned and selected bootloader when they flashed, but was not advising me to do so.
billybag said:
i REALLY appreciate your time and help, by the way. This is so frustrating. One person told me that they repartitioned and selected bootloader when they flashed, but was not advising me to do so.
Click to expand...
Click to collapse
Do you have any EFS backup?
billybag said:
i REALLY appreciate your time and help, by the way. This is so frustrating. One person told me that they repartitioned and selected bootloader when they flashed, but was not advising me to do so.
Click to expand...
Click to collapse
If you want to flash stock LP, I would just bite the bullet and do it and first get a working system. Then install Recovery and re-root - I use TWRP.tar file so I can flash it in Odin and the SuperSU zip file that I then flash in Recovery.
You don't say which N3 you have but are you sure you have the right ROM for it?
Did you turn off the phone and remove the battery for a bit THEN go into download mode?
Are you using v3.09 of ODin PC?
I've done mine twice for other reasons since LP came out - I untick the auto-reboot so after I flash the stock firmware I can flash TWRP - then it's boot into Recovery and install my custom ROM (I use Temasek's CM12) PA GApps and the SuperSU.zip, then set up the phone - usually I then Restore only Data from my latest TWRP backup but on occasion I've DL'd Titanium from Ply and used that to Restore my apps from extSD.
Journyman16 said:
If you want to flash stock LP, I would just bite the bullet and do it and first get a working system. Then install Recovery and re-root - I use TWRP.tar file so I can flash it in Odin and the SuperSU zip file that I then flash in Recovery.
You don't say which N3 you have but are you sure you have the right ROM for it?
Did you turn off the phone and remove the battery for a bit THEN go into download mode?
Are you using v3.09 of ODin PC?
I've done mine twice for other reasons since LP came out - I untick the auto-reboot so after I flash the stock firmware I can flash TWRP - then it's boot into Recovery and install my custom ROM (I use Temasek's CM12) PA GApps and the SuperSU.zip, then set up the phone - usually I then Restore only Data from my latest TWRP backup but on occasion I've DL'd Titanium from Ply and used that to Restore my apps from extSD.
Click to expand...
Click to collapse
That is what i am having problems with. i know how to flash custom roms. i was also able to flash stock KK when it came out. It is stock lollipop that i cannot get to flash. i am using an SM-n9005 (tmobile). i am going to try different firmware downloads (CSCs) and see what that does.
Also, i have tried Odin versions 3.07, 3.09, and 3.10
billybag said:
That is what i am having problems with. i know how to flash custom roms. i was also able to flash stock KK when it came out. It is stock lollipop that i cannot get to flash. i am using an SM-n9005 (tmobile). i am going to try different firmware downloads (CSCs) and see what that does.
Also, i have tried Odin versions 3.07, 3.09, and 3.10
Click to expand...
Click to collapse
Do you know your original firmware? I'm wondering because some versions have different sized partitions and flashing another type causes fails. i.e. I had a HK S3 and had to flash a PIT file before I could use European firmware. Might it be something along those lines?
Have practically the same situation...
The furthest I've got is the following
Code:
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> sbl1.mbn
<ID:0/003> aboot.mbn
<ID:0/003> rpm.mbn
<ID:0/003> tz.mbn
<ID:0/003> sdi.mbn
<ID:0/003> NON-HLOS.bin
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
But again, with any version of odin and any firmware (lollipop or kitkat) i'm trying to flash, it stucks with
Code:
<ID:0/003> Complete(Write) operation failed.
PS I also have
Code:
QUALCOMM SECUREBOOT: ENABLE
Write Protection: Enable
and my phone was originally locked to spanish vodafone.
Sorry for the delay. i just got around to giving it another shot and it worked. i found an official, made for TMOBILE, version of the firmaware.
Code:
N900TUVUFOB6_N900TTMBFOB6_TMB
for anyone else that may be having trouble. You can find it here: http://www.sammobile.com/firmwares/download/43850/N900TUVUFOB6_N900TTMBFOB6_TMB/
i was using n9005 firmwares, which is usually fine except int his case i needed a tmo one.
Thanks again for everyone's input. Hopefully this post can help someone else out now.
Hi, my brother-in-law tried to root his phone but probably didn't know what he was doing with Odin and Kies. I tried to restore the phone with Kies3 but the phone is not recognized and I can't get a recovery code. I've tried the default option of booting into recovery mode and flashing with Odin as Administrator. I'm flashing following a guide on this forum using [Auto Reboot] [F. Reset Time] checked in the options and loading [AP] [CP] [CSC] first. Others have commented not to use the [BL] file. The problem is when I try to flash it fails and I get this message:
<ID:0/007> Odin engine v(ID:3.1100)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> SingleDownload.
<ID:0/007> boot.img
<ID:0/007> NAND Write Start!!
<ID:0/007> recovery.img
<ID:0/007> system.img.ext4
<ID:0/007> FAIL! (Auth)
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
On the screen of the phone it says:
UDC START
SYS REV CHECK FAIL : Refer 3 > Binary 1
SECURE CHECK FAIL : system
Click to expand...
Click to collapse
I've tried everything I could flashing each one by one [BL] [AP] [CP] and [CSC]. Apparently the only one that successfully flashed through was [CP]. The phone can boot into recovery mode fine, when I start the phone normally it just hangs on the Samsung Galaxy S5 screen. Any help in the right direction would be appreciated. I have pretty much GoogledFu'd all the information I can and am using the stock Samsung Galaxy S5 SM-G900A firmware. I have tried different USB ports, the stock Samsung USB cable, and an LG USB cable and that didn't help either.
To flash the firmware using Odin you need to put the phone in Download mode (Power + home + volume down) and not recovery mode. Select PDA/AP in Odin, select the firmware and then click start.
DigitalBeating said:
Hi, my brother-in-law tried to root his phone but probably didn't know what he was doing with Odin and Kies. I tried to restore the phone with Kies3 but the phone is not recognized and I can't get a recovery code. I've tried the default option of booting into recovery mode and flashing with Odin as Administrator. I'm flashing following a guide on this forum using [Auto Reboot] [F. Reset Time] checked in the options and loading [AP] [CP] [CSC] first. Others have commented not to use the [BL] file. The problem is when I try to flash it fails and I get this message:
On the screen of the phone it says:
I've tried everything I could flashing each one by one [BL] [AP] [CP] and [CSC]. Apparently the only one that successfully flashed through was [CP]. The phone can boot into recovery mode fine, when I start the phone normally it just hangs on the Samsung Galaxy S5 screen. Any help in the right direction would be appreciated. I have pretty much GoogledFu'd all the information I can and am using the stock Samsung Galaxy S5 SM-G900A firmware. I have tried different USB ports, the stock Samsung USB cable, and an LG USB cable and that didn't help either.
Click to expand...
Click to collapse
Yes, I already have done that and the only thing that writes successfully is the [CP] file. It fails to write to the NAND and does a FAIL! (Auth). Not sure what else I can do.
Alright I think I figured exactly what he did to the phone. Apparently AT&T locked the bootloader on Lollipop and his phone got upgraded to Lollipop while he was sleeping. So he tried to use Odin to flash the AP for the older KitKat back onto the S5 and this softbricked the phone. As far as I have read there is no way to downgrade back currently to KitKat to get root access. I'm trying to look for stock firmware for Lollipop but I can't find anything for this model. I assume if I flash it back to the latest Lollipop version functionality will be restored. Someone said something about flashing a kernel but I don't know. Not really sure what to do now since I can't find official Samsung S5 SM-G900A firmware to flash back either through the recovery or through Odin.
DigitalBeating said:
Alright I think I figured exactly what he did to the phone. Apparently AT&T locked the bootloader on Lollipop and his phone got upgraded to Lollipop while he was sleeping. So he tried to use Odin to flash the AP for the older KitKat back onto the S5 and this softbricked the phone. As far as I have read there is no way to downgrade back currently to KitKat to get root access. I'm trying to look for stock firmware for Lollipop but I can't find anything for this model. I assume if I flash it back to the latest Lollipop version functionality will be restored. Someone said something about flashing a kernel but I don't know. Not really sure what to do now since I can't find official Samsung S5 SM-G900A firmware to flash back either through the recovery or through Odin.
Click to expand...
Click to collapse
I am currently in the same boat. Please tell me you found a fix for this and if so, what was it? Any help is greatly appreciated.
@DigitalBeating and @Theamazingcorey
Here is an AT&T lollipop firmware.....
https://www.androidfilehost.com/?fid=24591000424940454
G900AUCU4COI5_ATT4COI5_v5.1.1_Repair_Firmware
I found it (by chance) on a Russian hosting site. They say it's a 'repair' firmware which means it is more than likely going to be more than one file (it'll probably be bootloader, modem and OS) So you'll have to load each file into it's respective Odin 'slot'.
If I understand how repair firmwares work, it should wipe and format the data partitions (instead of simply overwriting them) as it flashes. This will give the best chance of a successful flash.....
http://i.imgur.com/rVnFwJM.jpg
I cannot thank you enough, that seems to have fixed my problem. I though I was going to be stuck with a paperweight, lol.
Would you happen to know if there is a way to root the the AT&T S5 with 5.1.1?
Glad it worked fella.....
With regards to rooting, everything I've read on XDA indicates AT&T Lollipop can't be rooted....and the possibility of downgrading to achieve root is non existent.......
But there's a LOT if information on XDA, and I'll be the first to admit that I haven't read it all........
http://i.imgur.com/rVnFwJM.jpg
@Theamazingcorey just out of interest, can you confirm what files were inside the zip?
http://i.imgur.com/rVnFwJM.jpg
Thanks for the info. Sorry I was not able to get back to you sooner, I've been slammed these last couple of days. Have family coming into town this evening and between work and getting ready for their visit, I haven't had time to think straight, lol.
Hi, when trying to flash my Verizon S7 back to stock (with the correct verizon files) I got this odin log
<ID:0/003> Odin engine v(ID:3.1203)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
When trying to exit I got the "Software Update Failed" and when trying to flash again it's just a stuck bar on my screen. Not sure what to do and I'm kinda of new to this but I'd appreciate any help. Since then my phone has been stuck on the green screen since and whenever I press anything it just returns to the screen.
Any fast help would really be appreciated, it's been like this for hours and I'm not sure what to do ):
I'm gonna take a quick stab at this and say use the other CSC file, whichever one you haven't tried (either csc_vzw or home_csc_vzw).
Do not use the HOME_CSC file. Use the CSC and be sure that all of the images are in the correct spots in ODIN.
Was the device rooted? If so, you may not have gotten rid of all the root files, so it detects modified and won't flash.
Which firmware are you trying to flash? Were you on Nougat? We need more information.
Are you going from U firmware? I had to check repartition when I did.
ironbesterer said:
Do not use the HOME_CSC file. Use the CSC and be sure that all of the images are in the correct spots in ODIN.
Was the device rooted? If so, you may not have gotten rid of all the root files, so it detects modified and won't flash.
Which firmware are you trying to flash? Were you on Nougat? We need more information.
Click to expand...
Click to collapse
I was rooted through the steps found here
https://forum.xda-developers.com/ve...-to-notes-root-install-xposed-unroot-t3411039
I tried to flash back to stock and got the error after that. My phone's battery died and it's just sitting on my desk now );
Sayunoi said:
I was rooted through the steps found here
https://forum.xda-developers.com/ve...-to-notes-root-install-xposed-unroot-t3411039
I tried to flash back to stock and got the error after that. My phone's battery died and it's just sitting on my desk now );
Click to expand...
Click to collapse
Same thing here. I can only get into stock recovery with the error "dm-verity verification failed" (most options are disabled), and into bootloader, but unable to flash stock ROM; it just fails every time.
I'd be glad for a solution!
Don't forget the bootloader file too. I believe the root thread doesn't include the BL file in the instructions, but the error disappeared when I included the Bootloader.
azoller1 said:
Don't forget the bootloader file too. I believe the root thread doesn't include the BL file in the instructions, but the error disappeared when I included the Bootloader.
Click to expand...
Click to collapse
Mine still has the error when I included the bootloader file.
Another thing I should mention is in the top right it says "SW REV CHECK FAIL : [system] Fused 3 > Binary 1
I tried changing the wire, using the boot loader file, and changing usb ports. Lost here );
Sayunoi said:
When trying to exit I got the "Software Update Failed"
Click to expand...
Click to collapse
I tried going back to stock as well and am stuck on this screen. It says to use the Verizon Software Repair Assistant on a computer to repair it. I've only ever rooted a kindle fire so I don't know too much. Any way I can just get my phone back to normal?
JaffXsMan said:
I tried going back to stock as well and am stuck on this screen. It says to use the Verizon Software Repair Assistant on a computer to repair it. I've only ever rooted a kindle fire so I don't know too much. Any way I can just get my phone back to normal?
Click to expand...
Click to collapse
Really wondering the same thing =/
I think maybe I'm trying to flash back to an older version. Does anyone have a link for the latest Galaxy S7 stock rom?
Sayunoi said:
I think maybe I'm trying to flash back to an older version. Does anyone have a link for the latest Galaxy S7 stock rom?
Click to expand...
Click to collapse
You cannot flash a stock rom with an older bootloader than what ever you currently have on your phone. You can only Odin flash a stock rom with same or newer bootloader. So usually you cannot go to an older rom only newer.
Can I try flashing stock rom while in the Software update failed screen, or do I need to be in download mode?
Sayunoi said:
I tried changing the wire, using the boot loader file, and changing usb ports. Lost here );
Click to expand...
Click to collapse
Try re-downloading the firmware. Are you sure you had the right firmware downloaded? The error seems to be caused by some kind of mismatch between the software trying to be flashed and what software you currently have on your phone
Also, make sure you are using the non princecosmy Odin 3.12
When ever I try to flash stock onto my phone, i'm getting the error "SW REV CHECK FAILED : [aboot] fused 4 > binary 2" I don't know what any of this means. Could someone explain this? Also when trying to flash stock i'm in "System Update Failed" screen and a little bar appears at the bottom. Does this mean it is still able to download the stock rom at all? One last thing, if I were to try and flash G935U instead of G935V could that help? Any help would be nice
go to samfirm and download the latest firmware for the S7 that you have, try flashing with that. I had to put everything in it's place in odin and select reformat to unroot my phone. I ran into the dm_verification failed and the only option was to download the latest firmware and flash that.
JerseyDubbin said:
go to samfirm and download the latest firmware for the S7 that you have, try flashing with that. I had to put everything in it's place in odin and select reformat to unroot my phone.
Click to expand...
Click to collapse
Do you mean sammobile? https://www.sammobile.com/firmwares/database/SM-G935F/
That or http://samfirm.net/I believe.
My phone can go in the android system recovery <3e>
LRX22C. I337UCUGOC3
my phone is s4 sghi337 atnt
previously i had rooted and using flahsfire installed a stock based custom rom NB1
it got corrupted recently and phones stuck in bootloop
when i try to install a rom i get this error footer error and signature verification error
I REMEMBER THIS FORUM USED TO BE HELPFUL ITS BEEN WEEKS AND NOT A SINGLE RESPONSE * sorry
Odin is your only hope now. Hope you had developer mode and USB debugging turned on before the corruption.
Sent from my SM-G955U using XDA-Developers Legacy app
yep never turned that off but there is no OS how can ODIN help ? wont it brick it ? and how to use odin i am pretty good with adb
drickles said:
Odin is your only hope now. Hope you had developer mode and USB debugging turned on before the corruption.
Sent from my SM-G955U using XDA-Developers Legacy app
Click to expand...
Click to collapse
plus i am pretty sure when i try to connect via odin my pc doesnt even recognize it being connected only in recovery adb sideload the device is recognized but do tell how can i use ODIN
Nope It won't brick it. Odin is pretty much the best fall-to option for every Samsung device whenever stuff like this hapoen. If you said you had developer mode on and USB debugging on then Odin is your best choice. First get Odin. Then get the latest Samsung usb drivers. Install the drivers and I'm sure when you connect your phone to the pc while Odin is opened it would detects your phone. Then we'll be good to go forward
Sent from my SM-G955U using XDA-Developers Legacy app
drickles said:
Nope It won't brick it. Odin is pretty much the best fall-to option for every Samsung device whenever stuff like this hapoen. If you said you had developer mode on and USB debugging on then Odin is your best choice. First get Odin. Then get the latest Samsung usb drivers. Install the drivers and I'm sure when you connect your phone to the pc while Odin is opened it would detects your phone. Then we'll be good to go forward
Sent from my SM-G955U using XDA-Developers Legacy app
Click to expand...
Click to collapse
i have all the drivers but the phones in recovery its not on downloading page so odin wont detect right ?
even if it does what to do next if odin works how do i get the right firmware my phone is rooted
First of you need to get your phone in download mode. Im guessing you're on stock recovery so that won't be of much help. If only your recovery was twrp recovery. But then I know your variants come with locked bootloader's so that won't be possible. Turn your phone off and press the hot keys to get your phone into download mode then connect your phone to the pc and open Odin. If it detects then we download a stock firmware of your phone's rom and flash it using odin. You can get a firmware to flash for your device from here:
https://forum.xda-developers.com/showthread.php?t=2263533
Sent from my SM-G955U using XDA-Developers Legacy app
drickles said:
First of you need to get your phone in download mode. Im guessing you're on stock recovery so that won't be of much help. If only your recovery was twrp recovery. But then I know your variants come with locked bootloader's so that won't be possible. Turn your phone off and press the hot keys to get your phone into download mode then connect your phone to the pc and open Odin. If it detects then we download a stock firmware of your phone's rom and flash it using odin. You can get a firmware to flash for your device from here:
https://forum.xda-developers.com/showthread.php?t=2263533
Sent from my SM-G955U using XDA-Developers Legacy app
Click to expand...
Click to collapse
all the links are dead one more thing i have some roms downloaded but they are not in the tar or md5 format is there anyway around it while using odin
https://androidfilehost.com/?fid=95916177934552137
This is another link I found to a lollipop firmware for your phone. And about converting ROMs to tar files yh it's possible. Mostly they are just different compression methods and could be extracted and modified to make a .tar file. But it can be tricky and can **** up if you miss any step. Let's try and make that a last resort
Sent from my SM-G955U using XDA-Developers Legacy app
drickles said:
https://androidfilehost.com/?fid=95916177934552137
This is another link I found to a lollipop firmware for your phone. And about converting ROMs to tar files yh it's possible. Mostly they are just different compression methods and could be extracted and modified to make a .tar file. But it can be tricky and can **** up if you miss any step. Let's try and make that a last resort
Sent from my SM-G955U using XDA-Developers Legacy app
Click to expand...
Click to collapse
thanks man for the time being will download and let you know i have one stock rooted rom w bl was thinking to convert it to .tar or something but will use the lollipop before
y2kyasir said:
thanks man for the time being will download and let you know i have one stock rooted rom w bl was thinking to convert it to .tar or something but will use the lollipop before
Click to expand...
Click to collapse
i did download the rom put it odin everything went fine
<ID:0/005> SingleDownload.
<ID:0/005> aboot.mbn
<ID:0/005> sbl1.mbn
<ID:0/005> sbl2.mbn
<ID:0/005> sbl3.mbn
<ID:0/005> rpm.mbn
<ID:0/005> tz.mbn
<ID:0/005> boot.img
<ID:0/005> recovery.img
<ID:0/005> persdata.img.ext4
<ID:0/005> system.img.ext4
<ID:0/005> modem.bin
<ID:0/005> NON-HLOS.bin
<ID:0/005> cache.img.ext4
<ID:0/005> hidden.img.ext4
<ID:0/005> RQT_CLOSE !!
<ID:0/005> RES OK !!
<ID:0/005> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/005> Removed!!
and the phone is still stuck in bootloop usually after the samsung galaxy s4 logo atnt would appear or samsung animated logo would come its not its still stuck
i really need your help
y2kyasir said:
i did download the rom put it odin everything went fine
<ID:0/005> SingleDownload.
<ID:0/005> aboot.mbn
<ID:0/005> sbl1.mbn
<ID:0/005> sbl2.mbn
<ID:0/005> sbl3.mbn
<ID:0/005> rpm.mbn
<ID:0/005> tz.mbn
<ID:0/005> boot.img
<ID:0/005> recovery.img
<ID:0/005> persdata.img.ext4
<ID:0/005> system.img.ext4
<ID:0/005> modem.bin
<ID:0/005> NON-HLOS.bin
<ID:0/005> cache.img.ext4
<ID:0/005> hidden.img.ext4
<ID:0/005> RQT_CLOSE !!
<ID:0/005> RES OK !!
<ID:0/005> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/005> Removed!!
and the phone is still stuck in bootloop usually after the samsung galaxy s4 logo atnt would appear or samsung animated logo would come its not its still stuck
i really need your help
Click to expand...
Click to collapse
in my previous recovery i got it restart to bootloader this recovery KOT49H doesnt have it i cannot connect it to odin anymore is phone gone ???
Nope....on the contrary we are actually making progress. It's now shifted from a bootloader problem to a bootloop problem. I did some research and found out that the lolipop update was actually causing some bootloops on the s4 after installation. I'm going to dig in and try to find a fix for the bootloop. There are a lot of threads on xda addressing fixes for that problem. I'm sure we will find a working fix for it. You can try searching too.
Sent from my SM-G955U using XDA-Developers Legacy app
drickles said:
Nope....on the contrary we are actually making progress. It's now shifted from a bootloader problem to a bootloop problem. I did some research and found out that the lolipop update was actually causing some bootloops on the s4 after installation. I'm going to dig in and try to find a fix for the bootloop. There are a lot of threads on xda addressing fixes for that problem. I'm sure we will find a working fix for it. You can try searching too.
Sent from my SM-G955U using XDA-Developers Legacy app
Click to expand...
Click to collapse
trust me i am going through all the posts and what not as i said my phone would show up on odin and get into download mode previously but now it doesnt infact even when i try to install the
http://server14.stockroms.net/downl...ow_ship_MULTI_CERT.tar.md5.zip?token=83894183
from adb sideload it gives the same error as footer is wrong signature verification failed
drickles said:
Nope....on the contrary we are actually making progress. It's now shifted from a bootloader problem to a bootloop problem. I did some research and found out that the lolipop update was actually causing some bootloops on the s4 after installation. I'm going to dig in and try to find a fix for the bootloop. There are a lot of threads on xda addressing fixes for that problem. I'm sure we will find a working fix for it. You can try searching too.
Sent from my SM-G955U using XDA-Developers Legacy app
Click to expand...
Click to collapse
trust me i am searching like hell through out the internet i even got one rom and i flashed it and got my system recovery to
KOT49.I337UCUFNB1
and again thanks for the help you are putting in too one more thing i lost the option to boot in bootloader so i dont get the downloading page and no odin connectivity
i got into odin
Produc name : SGH -I337
BINARY : SAMSUNG OFFICIAL
SYSTEM STATUS : CUSTOM
KNOX KERNEL LOC : 0X0
CSB CONFIG LSB" 0X0
WRITE PROTECTION ENABLE
EMMC BURST MODE ENALED
I have tried all the roms all the forums https://forum.xda-developers.com/galaxy-s4-att/general/guide-odin-to-stock-updating-rooting-t2926642
https://forum.xda-developers.com/galaxy-s4-att/general/how-to-installed-custom-lollipop-rom-t3135396
nothing can make phone come out of the boot loop
y2kyasir said:
I have tried all the roms all the forums https://forum.xda-developers.com/galaxy-s4-att/general/guide-odin-to-stock-updating-rooting-t2926642
https://forum.xda-developers.com/galaxy-s4-att/general/how-to-installed-custom-lollipop-rom-t3135396
nothing can make phone come out of the boot loop
Click to expand...
Click to collapse
Ok let's review what we have going on so far. Sorry for being away for so long though. Have been tight for some time now. So now:
No recovery mode? And by that I mean no stock recovery mode?
No download mode?
Sent from my SM-G955U using XDA-Developers Legacy app
drickles said:
Ok let's review what we have going on so far. Sorry for being away for so long though. Have been tight for some time now. So now:
No recovery mode? And by that I mean no stock recovery mode?
No download mode?
Sent from my SM-G955U using XDA-Developers Legacy app
Click to expand...
Click to collapse
no i have download its available by pushing the down button and theres recovery android recovery kot49h.i337fnb1
but no rom will boot and the phone wont start
Can't he just flash the stock ODIN tar file for the NB1 bootloader or whatever bootloader he's on?