Sooo.... I had the OTA to kitkat, lost my root, decided i wanted it back. Downgraded to 4.3 and rooted, safestrap all of that succesfully. Ran it for about 2-3 weeks, figured i'd go and follow the rest of the directions to get back to kitkat, turns out i messed it up good. I still have the nc5 build but the mk2 baseband and 4.3.
Now, whatever the heck i did, i tried a factory reset then tried to flash a stock 4.3 over it just to really clean it up, turns out, it didnt like that. Now kies will not even recognize the device, and when i tried surge's mk2 restore, it fails. I haven't been able to find a 4.4.2 stock to re-odin and try that. I obviously did search and still am searching at this moment but i must be blind or something.
Now i have a phone that says "firmware failed, please connect to kies and run a repair" or whatever. When i try to odin to the mk2, it says "sw rev. check fail : fused 6 binary 5" which i assume has something to do with the build number/bootloader for kitkat thats still on my phone. Am I screwed or is this recoverable? Thanks peoples.
I really need my phone for work. It's used numerous times to make calls because i'm in a service technician position. I can't go without it for even 1 weekday, if i can't get this figured out by sunday at noon, i will have to bite it and get a new phone. Cannot be phoneless on monday. It would literally cause me to lose my job.
Odin this full wipe http://forum.xda-developers.com/showthread.php?t=2735172
Sent from my OtterX running SlimKat 4.4.3 using Tapatalk
joshuabg said:
Odin this full wipe http://forum.xda-developers.com/showthread.php?t=2735172
Sent from my OtterX running SlimKat 4.4.3 using Tapatalk
Click to expand...
Click to collapse
I've tried it about 4 times now, 1 time it got to about 80% done then failed at write for persdata or something of the sort. The other 3 times it stops within 10 seconds. I'm not sure what else to do. It doesn't seem like there is anything else i can do to be honest. I might be effed.
On try #21, still no go. Ugh
BlueForce64 said:
On try #21, still no go. Ugh
Click to expand...
Click to collapse
Are you trying the same file over and over again? If so, maybe you got a bad download. Did you check the MD5 checksum to see if it matches? Maybe you could try downloading it again.
Sent from my NCC-1701
Yeah i am, but it fails at different points. The same 3 different points though. I'll try to re-dl it and try again. Anything is worth a shot at this point. Otherwise someone can get a free broken s4 if they want lol
Finally achieved success. It took about 40 times but it finally went through. The last 10 were tried with a new dl, i just didnt give up, the one time it worked i made sure i ran odin in administrator. I had an odin going without administrator so i loaded up a new one with it on and right when the 1st one failed i started the second one up and it had the blue progress bar go all the way to the right side of the screen and come back around through the left eventually running into itself, as soon as the progress bar began to overlap the screen it was also saying invalid response for bar length or something in the upper left text until that went down screen and started back on the top. In any case, woohoo it's working! Thanks guys, guess i won't need a new phone yet.
Related
I have been trying to update my S4 (vruame7) to the latest. I'm willing to lose root. The issue I'm having though is one that NOBODY seems to have mentioned anywhere: It started where I couldn't update over the air as the update fails. So I tried to update it with Kies on my mac but the program says I need more memory on my phone even though I already have it. This prompted me to unroot my phone and do the update again, but the issue is still there. So I tried booting into recovery and that worked. I decided then to reboot my phone and add CWM touch via ROM toolbox Pro. It said it worked fine, but now I cannot boot into the recovery mode. It just goes straight into ODIN mode and it won't prompt me to confirm it or not. I get into a very soft boot loop if I try and reboot though Rom Toolbox Pro to go into the recovery. I will land in ODIN and then unless I tell the phone manually to go into ODIN and then NOT proceed than it will be in a soft boot loop. So far I've tried unrooting and using Kies, Rooting and trying to load CWM onto my phone and failing, causing OTA to not be able to even start installing, and I've yet tried to go into safe mode and try to reset my phone that way. I might have to do that. if anyone has any other ideas I am open to that.
Your on me7 so you half to use safestrap that's the on way you can have a recover...... You probably half to Odin your phone back to me7 for the update to work. You can't use cwm or twrp on me7, unless u have safetrap installed and the its a version of twrp in it
hyperdrive powered s4
ebsk8er06 said:
Your on me7 so you half to use safestrap that's the on way you can have a recover...... You probably half to Odin your phone back to me7 for the update to work. You can't use cwm or twrp on me7, unless u have safetrap installed and the its a version of twrp in it
hyperdrive powered s4
Click to expand...
Click to collapse
Thanks. I've got safestrap installed sucessfully (it was so easy), and I'm now trying to install the update by wiping my phone and then doing it. I'll see if that works.
Well, it looks like I may have wiped my phone too far as I'm stuck at the Samsung custom logo and It's not booting farther. i can get into odin but I have a mac, so what do I do?
beez1717 said:
Well, it looks like I may have wiped my phone too far as I'm stuck at the Samsung custom logo and It's not booting farther. i can get into odin but I have a mac, so what do I do?
Click to expand...
Click to collapse
Heimdall is like odin but its mac.compatible
Hit thanks if I helped you out. Doing a little bit of reading goes a long way. Sent via tapatalk.
Use oden or Heimdall (guess its a Mac thing) to flash back to stock and then you can take the update. You haven't bricked yet but it sounds like you are getting close so be careful.
beez1717 said:
Well, it looks like I may have wiped my phone too far as I'm stuck at the Samsung custom logo and It's not booting farther. i can get into odin but I have a mac, so what do I do?
Click to expand...
Click to collapse
Sounds like you did a full wipe on non safe side "stock rom" of safestrap so your gonna have to flash a whole factory image cause it all gone the whole os
So after working for hoursx and hours, of working at it, I finally found http://sonofgeektalk.wordpress.com/2013/06/13/heimdall-on-a-mac/ <-- that webpage and it helped walk me through using Helmdall and it worked after much fiddling and discovering that I had to plug in my phone AFTER it got into odin but BEFORE I confirmed I wanted to be in odin. I then had to not wipe the phone clean but just do the install with the right files. It worked and I'm so happy. Now to see if I can update the darn phone. Don't know if I can or not but hey, I've got my phone back up and running and that's a GOOD thing.
I don't care about root as much as I care about getting the latest software if it provides enhancements I like, or security features I want. I think that root is fun, but it can be a pain in the butt as I just saw. Now that I know how to do the whole shtick, I should be able to do a lot more with my phone. I remember when I had to learn the ins and outs of my old Xperia Play. Horrible battery life and sub-par graphics chip but an awesome phone that had an awesome utility that could do just about anything with the phone with minimal work.
Looks like the system is updating itself just fine using OTA. What a LONG workaround I had to do. Thank you all for helping me teach myself a lot more about my phone
I'm having trouble trying to update as well. I unrooted and did a factory reset but the update still fails. What should I be trying?
Sent from my SCH-I545 using xda app-developers app
beez1717 said:
So after working for hoursx and hours, of working at it, I finally found http://sonofgeektalk.wordpress.com/2013/06/13/heimdall-on-a-mac/ <-- that webpage and it helped walk me through using Helmdall and it worked after much fiddling and discovering that I had to plug in my phone AFTER it got into odin but BEFORE I confirmed I wanted to be in odin. I then had to not wipe the phone clean but just do the install with the right files. It worked and I'm so happy. Now to see if I can update the darn phone. Don't know if I can or not but hey, I've got my phone back up and running and that's a GOOD thing.
I don't care about root as much as I care about getting the latest software if it provides enhancements I like, or security features I want. I think that root is fun, but it can be a pain in the butt as I just saw. Now that I know how to do the whole shtick, I should be able to do a lot more with my phone. I remember when I had to learn the ins and outs of my old Xperia Play. Horrible battery life and sub-par graphics chip but an awesome phone that had an awesome utility that could do just about anything with the phone with minimal work.
Click to expand...
Click to collapse
I think the problem here was that you tried to take an official update AFTER you messed with your phone... you should take this as a lesson to always flash back to stock before trying any 'official' updates, or better yet just have some patience for the updated files to show up here on the forums so you don't have to deal with OTAs at all. I don't really see the big rush to get the newest MI1 update anyway, it really doesn't provide any huge benefits at all and plus will possibly void your warranty through that stupid Knox thing if you try to root.
One thing I've learned is use patients dont jump the gun and if your not sure before you do something look here cause someone has already screwed up so the right way will be here somewhere and video will be on youtube!!
I got a Note 2 yesterday, bought it used. I turned it on, everything seemed normal. I took it to Verizon, they activated it for me in the store, and while I was there, the lady activating it also accepted an OTA software update. I have no idea what version I was on, or what the OTA was. When I got home, the phone shut down as part of the OTA, and everything appeared normal. The little android with a box screen came up, cycled through the progress bar, etc. However, when it was done, the phone rebooted, and froze on the "Samsung Galaxy Note II" screen. I gave it a while, then battery pulled, tried everything I could think of. Couldn't get into the recovery menu. It would get to Odin, but that was it. Anyways, after a very stressful night working on it, I found the thread here:
http://forum.xda-developers.com/showthread.php?t=2040264
I downloaded the "Alternate Restore Mirror" link, put the phone in download mode, and installed from Odin on my computer. The phone booted up, everything worked beautifully.
Then, tonight at work, I checked for software updates, and was informed that there was an available update. I downloaded and installed it(I think the phone said it was 7MB?), and THE SAME THING HAPPENED. Phone is frozen on the "Samsung Galaxy Note II" screen. I plugged it into my laptop, put it in download mode, and did exactly what I did this morning. Odin says everything was successful, and reboots the phone. But it hangs on the "Samsung Galaxy Note II" screen, no matter what I do. I've tried searching, and followed every guide on how to unbrick it I can find, but no matter what software package I use, it fails on "sboot.bin". The only one that will work and not fail is the "Alternate" in the link above, but when I use that one I still have a bricked phone.
I -really- need advice here, guys. I'm in way over my head.
So, a little more information. If I have a ROM that doesn't have an sboot.bin attached to it, it will write just fine and not show any errors. However, the phone will hang up on the "Samsung Galaxy Note II" screen. If I write a ROM that tries to write sboot.bin, it fails. Every time.
Maybe try following the "return to stock" section of this thread:
http://forum.xda-developers.com/showthread.php?t=2024207
This thread includes the .pit which should not only restore the factory rom, but restore the factory system partitions. This had worked for me in the past when I was stuck in a situation where nothing would boot.
Jiggabitties said:
Maybe try following the "return to stock" section of this thread:
http://forum.xda-developers.com/showthread.php?t=2024207
This thread includes the .pit which should not only restore the factory rom, but restore the factory system partitions. This had worked for me in the past when I was stuck in a situation where nothing would boot.
Click to expand...
Click to collapse
I did. When it tries to write either image, it fails on sboot.bin. Every image that includes sboot.bin fails on sboot.bin so far. I -really- don't know what to do.
after you do whatever with odin, can you get into recovery? you need to wipe cache and dalvik. at least thats the problem i had when i used odin to go back to stock
viper31573 said:
after you do whatever with odin, can you get into recovery? you need to wipe cache and dalvik. at least thats the problem i had when i used odin to go back to stock
Click to expand...
Click to collapse
No. I can get into Odin mode, but that's it. I took the phone to Verizon today, and they're going to send me a warranty replacement(Gotta love total equipment coverage). Now, though, I'm scared that when they get the phone they're going to charge me for whatever reason, so I'm still trying to figure this out.
So, no matter what image I flash, if it has sboot it fails. Period, no ifs ands or butts. So I think my problem is sboot? Which I think is the bootloader? For what it's worth, the rest of the image always seems to write just fine, and if I write an image with no sboot file, it goes swimmingly, but hangs on the "Samsung Galaxy Note II" screen, and I can't get into recovery.
skiahmutt said:
No. I can get into Odin mode, but that's it. I took the phone to Verizon today, and they're going to send me a warranty replacement(Gotta love total equipment coverage). Now, though, I'm scared that when they get the phone they're going to charge me for whatever reason, so I'm still trying to figure this out.
So, no matter what image I flash, if it has sboot it fails. Period, no ifs ands or butts. So I think my problem is sboot? Which I think is the bootloader? For what it's worth, the rest of the image always seems to write just fine, and if I write an image with no sboot file, it goes swimmingly, but hangs on the "Samsung Galaxy Note II" screen, and I can't get into recovery.
Click to expand...
Click to collapse
not sure what else to tell you that would help
viper31573 said:
not sure what else to tell you that would help
Click to expand...
Click to collapse
Well, the best place I can think to start is to nail down exactly what's happening, then try to figure out WHY it's happening. Once I know the what and why, the solution should be apparent. While I'm not against someone chiming in with a fix that works but I don't understand, I'm here to learn, and would like to come to a better understanding of the issue.
First: what is sboot.bin?
Second: do I need a specific sboot.bin for a specific ROM?
Third: what can cause sboot.bin to fail?
Fourth: is there a way to push just sboot.bin to the phone through Odin or other software?
Fifth: am I fixating on sboot.bin when it's not my issue?
Sixth: did you really read my whole post and get to this point? Wow, thanks! I appreciate you taking the time to try and help me, folks like you are what make the community so strong!
I don't understand a thing you posted. I just came to offer a fix that worked for me on a similar problem. Sorry it doesn't help you. Hopefully someone comes along that can help you
Sent from my SCH-I605 using Tapatalk
viper31573 said:
I don't understand a thing you posted. I just came to offer a fix that worked for me on a similar problem. Sorry it doesn't help you. Hopefully someone comes along that can help you
Sent from my SCH-I605 using Tapatalk
Click to expand...
Click to collapse
No worries. Thanks for the effort at least!
Okay, a bit of an update... I unzipped and removed sboot from a couple of the ROMs I have, and they flashed successfully, but the phone still hangs on the "Samsung Galaxy Note II" screen... I feel like I'm on the verge of figuring this out, I -know- it's got something to do with sboot now.
Can I write JUST a bootloader to the phone without writing anything else? If so, how?
if u were on 4.1.2 b4 u went to verizon, and the person there accepted a ota update while setting your n2 up, it could of been the 4.3 update which has the knox bootloader in it, and theres no going back from that. thats probably why the s.boot is failing
also try flashing the pit file.
mike7728 said:
if u were on 4.1.2 b4 u went to verizon, and the person there accepted a ota update while setting your n2 up, it could of been the 4.3 update which has the knox bootloader in it, and theres no going back from that. thats probably why the s.boot is failing
Click to expand...
Click to collapse
I think it was the 4.3 update. So, what's the knox bootloader, and what ROM can I flash to the phone that'll work with the knox bootloader?
I've seen a lot of posts here on how to unroot from SS and then upgrade. I had read the documents plenty of times with no luck. None. I spent over 3 hours trying to figure it out. All of the methods would not work for me.
What I had to do was make sure my modem matched up with ME7's baseband. Once I did that, I tried the update. It kept saying it was the NC5 update but it kept coming up with a recovery failed message. I said screw it and plugged it into my computer via Kies. Voila, it was as simple as that for me. Well, relatively speaking. I hope this can help someone in the future. Once it installed, it took away root and SS. I suppose it was kind of like ODIN flashing it? I ended up still doing a factory reset to clear the old data though. If I did something wrong here as well, please let me know. I've been crack flashing for a while and don't exactly consider myself an expert but I'd like to try to give back to this community! Good luck! :good:
As the title states, my Verizion SCH-i545 will lockup, shutdown and be unresponsive for long peroids of time ( read 24-96 hrs ) , unable to even take a charge.
What i think happened: I was trying to push boot loader files into my Kindle Fire HD 7" and *whoops* forgot to unplug my phone from the USB cord where it was charging merrily away. Since then I have gotten it to turn on a small handful of times - the most recent was after a 3 day wait for the battery to discharge and then it decided to accept a charge, worked for around 20 hours and then locked up again. Since that point it has been unresponsive.
I'm thinking that these boot loader files may have overwritten primary-boot and possibly secondary-boot sectors and sometimes the secondary-boot backup partition catches, and sometimes it doesn't.
I know what you all are thinking, and the guys I'm deployed with tell me the same thing - send it in as an insurance claim and get a new one. Well screw that, especially if I can get it done myself. I've also read that this is a possible hard-brick ( i don't think so since I can get something from it, sometimes ) and in need of a RIFF box to get this done properly.
At our last port, I was in the XDA-DEV chat room on snoonet and someone mentioned that the aboot.img may be disfigured or completely screwed, but being in port, I was fairly drunk and didn't save the log from that chat like I should have, does this sound right?
Can anyone give me any guidance as to what is going on with my phone and how to fix it? I have a stock Samsung ROM image on the way out here shipped from the states, but that's about a week away, at least. Will this be enough to fix it? Is there anything I can do to get my phone back operational in the mean time?
Thanks in advance.
http://forum.xda-developers.com/showthread.php?t=2735172
This is a link to the full wipe and no wipe nc5 tar images. Nc5 is the latest official firmware (4.4.2). These files are to be flashed with Odin. You can try the no wipe first so you don't lose your data but you might need the full wipe which will return you to total factory stock. I don't know how the network speeds are where you're deployed but be warned, these are big files.
joshm.1219 said:
http://forum.xda-developers.com/showthread.php?t=2735172
This is a link to the full wipe and no wipe nc5 tar images. Nc5 is the latest official firmware (4.4.2). These files are to be flashed with Odin. You can try the no wipe first so you don't lose your data but you might need the full wipe which will return you to total factory stock. I don't know how the network speeds are where you're deployed but be warned, these are big files.
Click to expand...
Click to collapse
I appreciate the super quick reply. I know that I'm still running MDK base band but if I can still root the NC5 and reinstall my Hyperdrive, I'll be ecstatic about this. Maybe at our next port I'll be able to download some of these images, but if the image that I have coming from the states will work, then I'll just run with that.
As far as downloading goes, it's a no go out here. Satellite internet that barely allows me to browse XDA, let alone download a GB worth of files.
And as far as wiping? I have no qualms, I've already shed my tears over wiping my phone and somehow my SD card got corrupted and I lost all of my pre-deployment pictures with my family. I've already shed my tears and lost everything that I can lose on that phone. At this point I just want to get it working again. As a sort of GFY to Samsung who told me I needed to send it in to them to have it fixed with authorized samsung equipment and authorized samsung techs.
Anyways, thanks for the quick reply, once I get my image from the states and give that a whirl I'll report back here if it worked. if not, I'm just waiting for our next port to download some of these images and try try again.
breakneat said:
I appreciate the super quick reply. I know that I'm still running MDK base band but if I can still root the NC5 and reinstall my Hyperdrive, I'll be ecstatic about this. Maybe at our next port I'll be able to download some of these images, but if the image that I have coming from the states will work, then I'll just run with that.
As far as downloading goes, it's a no go out here. Satellite internet that barely allows me to browse XDA, let alone download a GB worth of files.
And as far as wiping? I have no qualms, I've already shed my tears over wiping my phone and somehow my SD card got corrupted and I lost all of my pre-deployment pictures with my family. I've already shed my tears and lost everything that I can lose on that phone. At this point I just want to get it working again. As a sort of GFY to Samsung who told me I needed to send it in to them to have it fixed with authorized samsung equipment and authorized samsung techs.
Anyways, thanks for the quick reply, once I get my image from the states and give that a whirl I'll report back here if it worked. if not, I'm just waiting for our next port to download some of these images and try try again.
Click to expand...
Click to collapse
Man that's rough now I see why you have to have it shipped. Hope it works.
Op makes good on promise! Op replies!
My files got here the other day, and I was able to reflash with MJ7 firmware. After that I spent a solid 2 hrs ( had to pay off people to download these files - limited computer time and what not ) downloading Safestrap and Saferoot and then subsequently installing an old copy of Hyperdrive ( RLS 14 ). Could I have just flashed Hyperdrive with Odin and been okay? Or did I have to have a stock firmware to repair the issue? BTW, thats 7MB in 2 hours.
Also, I've been reading up on Hyperdrive RLS 17, and it says that I've got to flash NC5 firmware before I do RLS 17? With Safestrap, would I just flash NC5 into the stock slot, and then HD 17 into a subsequent slot? Or could I do like I did with HD14 and flash right into the stock slot with no apparent issues.
BTW, you being the only respondent to this post, I thank you lots for your help.
Had been running Hyperdrive rls 20 on what was a "backup" phone so I was unfortunately getting careless loading roms. At any rate, I attempted to upgrade to HD rls 21 and ran into a problem on reboot. The phone was extremely slow and I kept getting an error message "com.android.keyguard quit" or words to that effect. At this point I was still able to get into recovery (stock) and download. So I tried to flash release 21 several times without success. Out of frustration, I tried to download (odin) so-called emergency repair roms. They were 4.2 or 4.3. Subsequently I recall reading some time ago that there is a real (unrecoverable) problem that occurs if you ever try to go backwards from 4.4 to 4.3. My guess is that I am experiencing that "real problem" right now, because all I can get is "Firmware upgrade experience a problem; use Kies etc..." I tried Kies and it can not connect with the device. So not able to get into recovery and not able to get into download. Is the situation beyond hope. Please advise.
Can you get to stock recovery? You could try doing a factory reset from there at least...
ammjr71 said:
Can you get to stock recovery? You could try doing a factory reset from there at least...
Click to expand...
Click to collapse
Thanks for your response. No, I can not get into stock recovery, safestrap, or download mode. All startups go directly to the yellow warning "there is a problem with your firmware update". I think it is a goner but I just wanted to check and see if there was some trick (or miracle) I had overlooked. Looks like I have a new paperweight.
Yep, you are screwed. Never use the wrong Emergency Files.. Also, RLS 21 Needs another ZIP to function. Its the step after the actual ROM flash...