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!!
First of all, I am not new to flashing, rooting and etc. I have helped many of my friends with custom roms and etc so flashing and Odin is not something I know nothing about.
However, I was asked by my friend that his S2 was running slow and wanted me to put a custom rom on there. So I did the usual thing of using the ZergRush method to give him root access and I tested Superuser with Root Checker and everything was fine. So I went to install a custom recovery (Phil's CWM) via Odin and using the latest tar file from Phil's website but this is where things didn't go according to plan.
When I hit the Start button in Odin, it did the normal thing of writing to the NAND but instead of taking the usual 8-10 seconds, it took a lot longer. I actually waited 20 minutes and nothing was happening. There was no indication on the S2 that anything was happening and Odin was still stuck on the NAND Writing with all the buttone grayed out. So I waited a bit longer and after 30 min I decided to close Odin and try again, but when I try to get into Download Mode, I got the message 'Software Update Fail'. I tried to flash the custom recovery again but when it gets to the NAND Write, it instantly goes to 'Fail'.
Out of the 8 Samsung phones I have rooted and put a custom rom on, this is the first time this has happened. I searched the forum but most of it point to a bricked phone. I know at this point is is pretty critical that I do not try any random thing and asking you guys for any advice. I have tried flashing with a different version of Odin and also on different computers but gave me the same result. So any help would be much appriciated.
Hopper8's 'Odin troubleshooting' guide; search for it. You need to try everything in that thread over & over & over, only way you're fixing it is if you get a successful Odin flash away. In particular flashing the 3 part firmware might fix it.
Given the alternative - motherboard replacement or new phone - keep trying stuff, these cases are sometimes fixed by persevering (for whatever reason the first 8 stock rom flashes you try don't work but the 9th does, etc)
Thanks for the information MistahBungle, I have tried most of what has been said but I have not tried the leaked rom for the i9100. I will definately give this a shot.
No worries The rationale with flashing the 3 part is it will wipe the phone & hopefully remove any 'remnants' of what was previously on the phone which might be causing issues. If that doesn't work, download a bunch of stock roms from Samfirmware (carrier/country doesn't matter, just make sure you DL I9100 firmwares) & start flashing, this sometimes solves problems like this as I mentioned in my PP. Good luck.
MistahBungle said:
No worries The rationale with flashing the 3 part is it will wipe the phone & hopefully remove any 'remnants' of what was previously on the phone which might be causing issues. If that doesn't work, download a bunch of stock roms from Samfirmware (carrier/country doesn't matter, just make sure you DL I9100 firmwares) & start flashing, this sometimes solves problems like this as I mentioned in my PP. Good luck.
Click to expand...
Click to collapse
Just giving you an update. The 3 part leaked rom did the trick! I been flashing for a few years now but never ever had Odin go wrong so this is a new experience for me. I really appricate your help with this, was so worried I stuffed up a friends phone.
Good news then No worries, glad you got it sorted (& you've still got a friend ). Yeah, that's a handy trick the 3 part, it's bailed a few people out. Don't forget to thank Hopper's OP in his thread.
Z-Blade said:
Just giving you an update. The 3 part leaked rom did the trick! I been flashing for a few years now but never ever had Odin go wrong so this is a new experience for me. I really appricate your help with this, was so worried I stuffed up a friends phone.
Click to expand...
Click to collapse
Good to see you got it working, always like hearing of people getting their (or not their own in your case) phone back to life
MistahBungle said:
Good news then No worries, glad you got it sorted (& you've still got a friend ). Yeah, that's a handy trick the 3 part, it's bailed a few people out. Don't forget to thank Hopper's OP in his thread.
Click to expand...
Click to collapse
Thanks for keeping on referring my thread, the more people it can help the better I'm working 6 days a week for now so haven't much time to go on Q&A and help out. Also thanks for before, I think you know what I'm referring to. Much appreciated. :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.
Just when I had my phone dialed in just the way I wanted than I screw things up. Have The Verizon Galaxy S4 and had the Mk1 build on it and rooted to the Galaxy nk2 build. Also had Hyperdrive 20 installed. Really enjoyed the phone and its performance. Thought I would move some files around using Kies....Boy that was a mistake. As soon as i plugged the phone int my laptop and brought up Kies there was a message on the Kies screen that I needed to update the software. I thought it was the Kies Software. Oh no it was the phones. Anyway I got the Nk1 update 4.4.2 and that put it the phone into a bootloop. I got the phone working by do a factory reset but lost root and everything else. And the phone has lost a lot of its functionality, ie, the auto rotation doesn't work along with some other things that i just work around. I tried to restore using Odin, but keep getting a fail message, and I never bothered to see what the fail code was.
I think what Im needing is the Nk1 software to plug into Odin so I can start over. But I've been wrong before.
If someones got a minute could you give me the steps to rebuld the phone back to where I had it before. Im sure I left out something, or for that matter if Im S.O.L. I can understand that.
Thanks
I was having issues with my phone after I installed the wrong build of a rom or program, and I spent hrs and hrs and hrs looking for the right files for odin in order to get the phone working, but failed, then I came across my old usb storage that had all the files that I needed, since I have been through this a few times in the past, and it worked, got the phone back up to speed. I actually saw this post and subscribed to it to see if some one would post the file link but since no one did and I just happen to find my old ones, I will try to send them to ya, your phone should be working today buddy. Give me a few to get the files out.
tater510 said:
Just when I had my phone dialed in just the way I wanted than I screw things up. Have The Verizon Galaxy S4 and had the Mk1 build on it and rooted to the Galaxy nk2 build. Also had Hyperdrive 20 installed. Really enjoyed the phone and its performance. Thought I would move some files around using Kies....Boy that was a mistake. As soon as i plugged the phone int my laptop and brought up Kies there was a message on the Kies screen that I needed to update the software. I thought it was the Kies Software. Oh no it was the phones. Anyway I got the Nk1 update 4.4.2 and that put it the phone into a bootloop. I got the phone working by do a factory reset but lost root and everything else. And the phone has lost a lot of its functionality, ie, the auto rotation doesn't work along with some other things that i just work around. I tried to restore using Odin, but keep getting a fail message, and I never bothered to see what the fail code was.
I think what Im needing is the Nk1 software to plug into Odin so I can start over. But I've been wrong before.
If someones got a minute could you give me the steps to rebuld the phone back to where I had it before. Im sure I left out something, or for that matter if Im S.O.L. I can understand that.
Thanks
Click to expand...
Click to collapse
Go to the How to Root NK1 thread in the general section and flash the ODIN NK1 image through ODIN, voilà
Im trying to get the files for sharing but having issues, these files will revert the phone back to stock, but with the new root method, it should be a 1 min process to root it.
---------- Post added at 10:33 PM ---------- Previous post was at 10:09 PM ----------
Ok I found the thread that has the files and instructions http://forum.xda-developers.com/showthread.php?t=2735172 , scroll to where it says full wipe, and fallow those, I did that one on weds and didnt work, prob using wrong pit file,message me your email and I will email you the pit file to use, but other than that, the pda file has the same name than the one I have "ALL_VZW_I545VRUFNC5_I545VZWFNC5_1151670_REV06_user_low_ship_MULTI_CERT.tar.md5" and my pit file name is "JFLTE_USA_VZW_16G.pit" . Hope this helps. Remember this will put you at very stock, but just do the new rooting method, should take less than a min. Any issues just message me and Ill see what I can do.
Okay, I don't really know if i'm aloud to start a new thread for this but I'm going to see what happens.
Okay, I'm fairly new to rooting and flashing. I've flashed maybe 4 phones with custom roms and everything went fairly smoothly. I just got a Galaxy S8+ Sprint SM-G955u and was attempting the sampwnd root method on here. I thought I was following the directions to a T but apparently I wasn't because I got a fail pretty much right off the bat. Now my phone will not whatsoever. I am able to get it into download mode but that is it. No recovery mode no nothing. I have tried flashing the stock firmware but I get the same result. A fail pretty much right off the bat. I am running odin as admin, I've tried flashing the files individually as well as all together in both regular odin and comsey odin and I still just get the same failed result . Please tell me what ive done wrong and please please tell me i'm not screwed.
haven't rooted anything in a while but i used to do all my phones, do the normal 3 things when you fail, 1) re download the files 2) look around for more odins that other people are saying works and 3) try different cables, this is the dumb reason i have failed many flashes so don't overlook this. you can get into download mode so you're not screwed yet. best of luck
Thats really the best advice giving your situation. Ive had scenarios in the past where each one of those fixed my problems
Well sprint phones dont have root or custom roms as far as i see, but, maybe the other lines do. But if you really screwed up...try selecting nand erase all option and use the stock rom. Thats always been my last resort, and it always worked