I had a problem with my phone I couldn't go into CWM and I din't have superSU privileges anymore. So I tried doing a reset and it didn't boot up only to custom OS install screen and I tried using odin to install S4 stock I337UCUAMDL_I337ATTAMDL_I337UCUAMDL_HOME.tar.md5 and i get FAIL. can someone please help me with this.. I am also going to try another computer.
Also, redownload the tar file. It could be a bad download.
jd1639 said:
Also, redownload the tar file. It could be a bad download.
Click to expand...
Click to collapse
ok will try that.
here are the messages that I am getting
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I337UCUAMDB_I337ATTAMDB_I337UCUAMDB_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<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> aboot.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)
2nd message
ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I337UCUAMDL_I337ATTAMDL_I337UCUAMDL_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<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> aboot.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)
what firmware were you running when the issue began? MDL, MF3? sounds like maybe you took the update?
xBeerdroiDx said:
what firmware were you running when the issue began? MDL, MF3? sounds like maybe you took the update?
Click to expand...
Click to collapse
I think that is where the problem started. I tried 2 computers and the same problem. I am redownloading the stock firmware again.
jimsond said:
I think that is where the problem started. I tried 2 computers and the same problem. I am redownloading the stock firmware again.
Click to expand...
Click to collapse
If you had mf3 on, no amount of odin is going to help.
jimsond said:
I think that is where the problem started. I tried 2 computers and the same problem. I am redownloading the stock firmware again.
Click to expand...
Click to collapse
You must have taken the update to MF3. Essentially, you will not be allowed to downgrade firmware back to older versions. The way Samsung is writing the bootloader is there a monotonic counter only going in one direction, up. So if the bootloader has been updated to the latest version by an OTA, you can't revert it back. Currently I believe there is no workaround, but we have some awesome devs on this site so keep your fingers crossed.
jimsond said:
I had a problem with my phone I couldn't go into CWM and I din't have superSU privileges anymore. So I tried doing a reset and it didn't boot up only to custom OS install screen and I tried using odin to install S4 stock I337UCUAMDL_I337ATTAMDL_I337UCUAMDL_HOME.tar.md5 and i get FAIL. can someone please help me with this.. I am also going to try another computer.
Click to expand...
Click to collapse
What exactly did you do that caused the problem?
What exactly is the state of your phone now? Can you boot up or not? Please be clear.
jeffreii said:
What exactly did you do that caused the problem?
What exactly is the state of your phone now? Can you boot up or not? Please be clear.
Click to expand...
Click to collapse
I tried the update but it didn't finish. The phone was working but I couldn't go into cwm recovery. I also tried to use TWRP to go into recovery could that be the problem? would this work http://forum.xda-developers.com/showthread.php?t=2360859
jimsond said:
I tried the update but it didn't finish. The phone was working but I couldn't go into cwm recovery. I also tried to use TWRP to go into recovery could that be the problem? would this work http://forum.xda-developers.com/showthread.php?t=2360859
Click to expand...
Click to collapse
You tried what update? What do you mean it didn't work? What do you mean you tried to go into both recoveries? You can only have one on your phone at any given time. Tell me exactly what you did. DETAILS.
Also, again, exactly what is the state of your phone right now? What does it do when you turn it on and what exactly is the problem.
Please try to be clear.
jeffreii said:
You tried what update? What do you mean it didn't work? What do you mean you tried to go into both recoveries? You can only have one on your phone at any given time. Tell me exactly what you did. DETAILS.
Also, again, exactly what is the state of your phone right now? What does it do when you turn it on and what exactly is the problem.
Please try to be clear.
Click to expand...
Click to collapse
HI I just tried this http://forum.xda-developers.com/showthread.php?t=2360859 and how I am able to boot into my phone. How can I tell you if the update over the air did anything? I know there was a problem with the update over the air. The last thing I did was a factory data reset and format SD card. So now I can use the phone and if I try to go into CWM turning of the phone and holding power, up volume and home and it doesn't go in cwm just go to downloading screen. I take out the battery and power up and it works. I think the phone now is not rooted. So should I try to root or try to use odin and install Stock Firmwares..
P.S in kies the current firmware version PDA:MF3 / PHONE:MF3 / CSC:MF3 (ATT)
jimsond said:
HI I just tried this http://forum.xda-developers.com/showthread.php?t=2360859 and how I am able to boot into my phone. How can I tell you if the update over the air did anything? I know there was a problem with the update over the air. The last thing I did was a factory data reset and format SD card. So now I can use the phone and if I try to go into CWM turning of the phone and holding power, up volume and home and it doesn't go in cwm just go to downloading screen. I take out the battery and power up and it works. I think the phone now is not rooted. So should I try to root or try to use odin and install Stock Firmwares..
Click to expand...
Click to collapse
Go into settings, about device, and see what your build number is. If it ends in mf3 you have the update. If it ends in mdl or mdb then you don't and you can still use Odin. If it's mf3 Odin is not going to work.
jimsond said:
HI I just tried this http://forum.xda-developers.com/showthread.php?t=2360859 and how I am able to boot into my phone. How can I tell you if the update over the air did anything? I know there was a problem with the update over the air. The last thing I did was a factory data reset and format SD card. So now I can use the phone and if I try to go into CWM turning of the phone and holding power, up volume and home and it doesn't go in cwm just go to downloading screen. I take out the battery and power up and it works. I think the phone now is not rooted. So should I try to root or try to use odin and install Stock Firmwares..
Click to expand...
Click to collapse
Please don't take offense to this, but you need to hear it:
You have a serious problem - and it's not your phone - it's you. You clearly are not well-versed on what you are doing to your phone. You seem to be just trying things to see if they'll work and a common result is a bricked and unrecoverable phone. Just take a look at the Q & A forums and see how many threads there are about people who didn't read, research, and understand before attempting something...and now they are desperate for help. Your thread is one of those.
You have not yet given a clear indication of what you did to cause your problem in the first place, nor have you explained clearly what your problem was and the current state of your phone. You then asked "should I try this?" and before anyone told you whether or not it was a good idea, you tried it anyways.
You need to step away from your phone and take some time to read, research, and understand what's going on. You don't even know how to tell if your phone is rooted. It seems like you've completely lost your recovery mode, and now you want to try more stuff. You will be lucky if you don't ruin your phone if you keep it up.
You need to read all of this and understand it before you continue:
http://forum.xda-developers.com/showthread.php?t=2301762
http://forum.xda-developers.com/showthread.php?t=2314494
http://forum.xda-developers.com/showthread.php?t=2387577
Once you finish reading that, you'll understand how dangerous your current situation is. Phones on MF3 firmware have no way to recover to stock and, quite often, if you brick your phone there is currently no way to fix it...so you'll have a $650 paperweight.
jd1639 said:
Go into settings, about device, and see what your build number is. If it ends in mf3 you have the update. If it ends in mdl or mdb then you don't and you can still use Odin. If it's mf3 Odin is not going to work.
Click to expand...
Click to collapse
It look like I have mf3 So I f__k up. The phone is working
jimsond said:
It look like I have mf3 So I f__k up. The phone is working
Click to expand...
Click to collapse
Good to hear the phone is working. I wouldn't mess with it any more.
jeffreii said:
Please don't take offense to this, but you need to hear it:
You have a serious problem - and it's not your phone - it's you. You clearly are not well-versed on what you are doing to your phone. You seem to be just trying things to see if they'll work and a common result is a bricked and unrecoverable phone. Just take a look at the Q & A forums and see how many threads there are about people who didn't read, research, and understand before attempting something...and now they are desperate for help. Your thread is one of those.
You have not yet given a clear indication of what you did to cause your problem in the first place, nor have you explained clearly what your problem was and the current state of your phone. You then asked "should I try this?" and before anyone told you whether or not it was a good idea, you tried it anyways.
You need to step away from your phone and take some time to read, research, and understand what's going on. You don't even know how to tell if your phone is rooted. It seems like you've completely lost your recovery mode, and now you want to try more stuff. You will be lucky if you don't ruin your phone if you keep it up.
You need to read all of this and understand it before you continue:
http://forum.xda-developers.com/showthread.php?t=2301762
http://forum.xda-developers.com/showthread.php?t=2314494
http://forum.xda-developers.com/showthread.php?t=2387577
Once you finish reading that, you'll understand how dangerous your current situation is. Phones on MF3 firmware have no way to recover to stock and, quite often, if you brick your phone there is currently no way to fix it...so you'll have a $650 paperweight.
Click to expand...
Click to collapse
Thanks for your input I have a hard time saying on paper what was my problem. I like to talk things out and I use the link that you posted and I have root now..
Related
I attempted to use Odin to factory reset my phone.
Here's a list of the things i've done or installed...
~CWMrecovery using Odin
~ROM Manager
~Got to the recovery reboot screen with the green font where I could make a
nandroid backup. I did that.
~Made a titanium backup.
~Was attempting to flash Dl09 and Stupidfast.. Kept bumping into problems with the SD card mount. Got that to work by pulling the physical SD and putting it back it right at error screen.
~And got another error upon finally attempting to Flash Dl09
And now i'm just trying to give my Fascinate a complete factory resest to start fresh with a little more subject knowledge.. (thanks to these forums )
SO as i'm in Odin with proper files for reset... PIT and PDA VZW
It fails claiming:
<ID:0/006> Added!!
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> Enter CS for MD5..
<ID:0/006> Check MD5.. Do not unplug the cable..
<ID:0/006> Please wait..
<ID:0/006> Checking MD5 finished Sucessfully..
<ID:0/006> MD5 hash value is invalid.
<OSM> All threads completed. (succeed 0 / failed 1)
So I try to use CWMrecovery once again...
and my every time it says it works, so I go to pop the battery back in
and turn the phone on and I'm stuck at the black and white Samsung logo.
I've left it sitting there for fifteen minutes now to no avail...
I'm kinda scared, but i'm keeping my cool.. Please help?
Make sure you are flashing all your md5 files into the "PDA" in Oden, regardless of what they are, they need to be flashed that way.
This is exactly how i'm doing it...
Still getting that fail
I just tried DI01package3.tar.md5 and there is a long download now taking place onto my phone.
We'll see if this works... if it doesn't....... Suicide?
That worked!
First relief i've felt in three days!
Got my phone functional again. Wiped though...
If I wanted to get SupahClean and stupid fast again from this point would anyone recommend a process??
You can use ODIN to flash the DL09 ROM. It includes everything. Here's a link:
http://forum.xda-developers.com/showthread.php?t=908451
Then you can root.
http://forum.xda-developers.com/showthread.php?t=913470
Then you can install Superclean and the Stupidfast.
modus81 said:
You can use ODIN to flash the DL09 ROM. It includes everything. Here's a link:
http://forum.xda-developers.com/showthread.php?t=908451
Then you can root.
http://forum.xda-developers.com/showthread.php?t=913470
Then you can install Superclean and the Stupidfast.
Click to expand...
Click to collapse
Here's a better link for rooting DL09:
http://forum.xda-developers.com/showthread.php?t=913670&highlight=rooting+version
Thanks to both of you guys. I'm going to try it now!
I'll post again if I have issues
The root worked perfectly.
But I want to be very careful this time.. haha.
What is the best way to go about installing Superclean and Stupidfast?
Flash them using CWM
Hey guys just looking for any help if at all possible.
My install has been anything but smooth. I had many issues actually getting cyanogenmod on to the phone in the first place ( seems the help out there doesn't really cover the international i9505 very well, where it does you often just hit a brick wall)
In anycase i finally got it onto the phone and was looking for an explanation as to why the phone is not detecting my carrier. I mean its just not detecting it at all. I have made some strange findings when looking through the phone. It doesn't know what baseband i'm on for example.
Now for the real problem. After all the hassle of getting CM onto the phone i decided to reboot it to see if that would pick up my carrier. Now the phone takes AGES (2-5 mins) to boot up, some times it hangs. The phone functions fine when it boots.
I used CWM recovery to install CM because TWRP just would not work, infact CWM recovery was a pain in the arse too, the only way i could get it to boot into recovery mode was to download the rom manager app and use its widget to boot into recovery because manually trying it just resulted in multiple hangs.
This is the first time i have rooted/flashed an android device so i may be making some rookie errors here but this is bordering on stupid now.
Cwm and which version?
Sent from my GT-I9505 using xda app-developers app
mkhattat said:
Cwm and which version?
Sent from my GT-I9505 using xda app-developers app
Click to expand...
Click to collapse
i9505-cwm-recovery-6.0.3.2-4. Its the 28th's nightly also. Im trying to get it to see my o2 version of the s4. I installed gapps from zip straight after CM but i havn't used it. might the problem be there?
i have reinstalled CWM and flashed a new CM nightly from here.
http://forum.xda-developers.com/showthread.php?t=2317040
I still cant get access to my mobile network (UK o2). When i flash cyanogen it says please insert sim yadayada. Any help on this would still be very much appreciated :crying:
Possibly a corrupt EFS partition? If you flash stock ROM can you get signal and baseband back?
Sent from my GT-I9505 using XDA Premium HD app
TouchWiz king of ROMs ..... dont careeee CM bla bla bla
This is really bad im still in need of help sadly. I am trying to flash stock firmware from sammobile.com. It has the o2 uk one i need. I am using odin to do it following this guide youtube dot com/watch?v=hZTTTk7vbVM
The problem now is that it fails to flash (using odin 3.06) . Kies doesnt even recognise my device....this is a disaster so far
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9505XXUBMF8_I9505O2UBMG1_I9505XXUBMF8_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> sbl2.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> sbl3.mbn
<ID:0/005> rpm.mbn
<ID:0/005> aboot.mbn
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
So i have soft bricked my phone. It wont boot up instead it gets to a screen that says "Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again" Kies doesnt recognise my phone so thats out.
I cant get into recovery mode it just gives the same message. In download mode when i try to use odin to flash the previously mentioned stock rom it fails. Im at a loss and i am badly in need of help now
Try this sir. Post #9 http://forum.xda-developers.com/showthread.php?p=46143562
Sent from my GT-I9505 using xda app-developers app
phrazersco said:
So i have soft bricked my phone. It wont boot up instead it gets to a screen that says "Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again" Kies doesnt recognise my phone so thats out.
I cant get into recovery mode it just gives the same message. In download mode when i try to use odin to flash the previously mentioned stock rom it fails. Im at a loss and i am badly in need of help now
Click to expand...
Click to collapse
User Odin version 1.85
Sounds to me like you have a corrupted EFS, just as the poster above mentioned. Did you do a full wipe before you tried to Odin back to Stock ROM?
donalgodon said:
Sounds to me like you have a corrupted EFS, just as the poster above mentioned. Did you do a full wipe before you tried to Odin back to Stock ROM?
Click to expand...
Click to collapse
no i have not done a full wipe. I have been on holiday for the past week and got home yesterday. Im still looking for a fix for this people!
phrazersco said:
no i have not done a full wipe. I have been on holiday for the past week and got home yesterday. Im still looking for a fix for this people!
Click to expand...
Click to collapse
Look no further, because the full wipe is the fix, like it or not.
My newbness is screwing me here i know it. The phone is fresh from the o2 shop so i dont have anything to lose, how do i do a full wipe?
I have had some progress on my own. I downloaded a new .tar stock firmware from sammobile, the BTU version. This time odin flashed it no problem what-so-ever. So if anyone reading this gets the same problem mine was with the o2uk firmware on sammobile.
I have a new problem though, the phone just doesnt get past the samsung logo at boot. it doesnt freeze as i can see the blue glow round the samsung logo pulse but it just never boots. left it for ah hour after first flashing and nothing. I removed battery etc etc but wont get past this point. Is this full wipe easy to do?
phrazersco said:
My newbness is screwing me here i know it. The phone is fresh from the o2 shop so i dont have anything to lose, how do i do a full wipe?
I have had some progress on my own. I downloaded a new .tar stock firmware from sammobile, the BTU version. This time odin flashed it no problem what-so-ever. So if anyone reading this gets the same problem mine was with the o2uk firmware on sammobile.
I have a new problem though, the phone just doesnt get past the samsung logo at boot. it doesnt freeze as i can see the blue glow round the samsung logo pulse but it just never boots. left it for ah hour after first flashing and nothing. I removed battery etc etc but wont get past this point. Is this full wipe easy to do?
Click to expand...
Click to collapse
Boot into the stock recovery and do a factory reset. It'll cure your problem. The first boot can take a long time, 5 minutes, so let it do it's thing
jd1639 said:
Boot into the stock recovery and do a factory reset. It'll cure your problem. The first boot can take a long time, 5 minutes, so let it do it's thing
Click to expand...
Click to collapse
Thanks guys im back into my phone and its all working normal again!
Did i do something wrong by rooting then installing cyanogen mod the way i did? i mean it worked i just didnt have my phone network. kept saying insert SIM. was i supposed to unlock the carrier or something? i though cyanogen did all that.
Still looking for that last bit of advice people. Is there something i should have done before rooting/flashing to unlock my phone from o2uk or was i correct in thinking CM10.2 unlocked the phone also? if i was incorrect is there any help i can be given with respects to this? Thanks again.
hello all,
this is my first post so be gentle with me lol. I'm trying to reinstall the stock ROM on my att i1337 gs4 using Odin and i keep getting this error message.
Code:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I337UCUAMDL_I337ATTAMDL_I337UCUAMDL_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
I'm leaving tomorrow morning to go out of state and i really need help with this. This all happened because i rooted my phone and uninstalled some of the att bloatware but ever since then, i couldnt open my gallery or use my gps or svoice or anything like that because the stupid text to speech engine kept failing. I just want my phone to work, i dont want this stupid root and ive tried everything to get rid of it. I'm at a loss and i really need help. If i could pay someone to help me i seriously would because ive never been so frustrated before in my life.
PLEASE HELP!!!!!!!!!!!!!!!!!!!!!!!!!!!!! :crying: :crying: :crying: :crying: :crying: :crying:
MY PHONE WILL NOW NOT START UP
irootbeer said:
hello all,
this is my first post so be gentle with me lol. I'm trying to reinstall the stock ROM on my att i1337 gs4 using Odin and i keep getting this error message.
Code:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I337UCUAMDL_I337ATTAMDL_I337UCUAMDL_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
I'm leaving tomorrow morning to go out of state and i really need help with this. This all happened because i rooted my phone and uninstalled some of the att bloatware but ever since then, i couldnt open my gallery or use my gps or svoice or anything like that because the stupid text to speech engine kept failing. I just want my phone to work, i dont want this stupid root and ive tried everything to get rid of it. I'm at a loss and i really need help. If i could pay someone to help me i seriously would because ive never been so frustrated before in my life.
PLEASE HELP!!!!!!!!!!!!!!!!!!!!!!!!!!!!! :crying: :crying: :crying: :crying: :crying: :crying:
MY PHONE WILL NOW NOT START UP
Click to expand...
Click to collapse
Was your Baseband MF3? or MDL? If you are trying to ODIN back while on MF3 it will not work....your best bet is to take it to a Best Buy and see the Samsung Experience Desk and see if they can reflash it for you.
Tremulant1 said:
Was your Baseband MF3? or MDL? If you are trying to ODIN back while on MF3 it will not work....your best bet is to take it to a Best Buy and see the Samsung Experience Desk and see if they can reflash it for you.
Click to expand...
Click to collapse
its an MF3, I bought the phone off of craigslist, will bestbuy still help me with this?
irootbeer said:
its an MF3, I bought the phone off of craigslist, will bestbuy still help me with this?
Click to expand...
Click to collapse
At this point, best buy is your only option. Running MF3 you're not supposed to mess with recoveries, bootloaders, or custom firmware (unless using Safe Strap). So you can go there and lie your ass off and see if they can reflash it for you....make up a good story hopefully you get lucky.
Tremulant1 said:
At this point, best buy is your only option. Running MF3 you're not supposed to mess with recoveries, bootloaders, or custom firmware (unless using Safe Strap). So you can go there and lie your ass off and see if they can reflash it for you....make up a good story hopefully you get lucky.
Click to expand...
Click to collapse
Hey man i really appreciate the help, like you dont know how much youve saved me lol, id still be running around freaking out if it werent for you. But the funny thing is, I was using safestrap, i guess i just f****d something up while i was deleting bloatware. Now about the story, do you think they would buy it if i told them that something messed up and i tried to restore it, but the phone shut off halfway through, so now it wont start back up? I know theres a way to check some number and if they see something then they wont mess with it, so will that affect me at all? Also since it was rooted do you think theyll notice that too? I mean, I figure it would be pretty hard to do so since the phone is so messed up at the moment. I dont want to go in there and have them tell me that they wont do anything because I will flip some major s**t. I dont want to walk out of there with a $700 paperweight lmfao
irootbeer said:
Hey man i really appreciate the help, like you dont know how much youve saved me lol, id still be running around freaking out if it werent for you. But the funny thing is, I was using safestrap, i guess i just f****d something up while i was deleting bloatware. Now about the story, do you think they would buy it if i told them that something messed up and i tried to restore it, but the phone shut off halfway through, so now it wont start back up? I know theres a way to check some number and if they see something then they wont mess with it, so will that affect me at all? Also since it was rooted do you think theyll notice that too? I mean, I figure it would be pretty hard to do so since the phone is so messed up at the moment. I dont want to go in there and have them tell me that they wont do anything because I will flip some major s**t. I dont want to walk out of there with a $700 paperweight lmfao
Click to expand...
Click to collapse
No problem man, i'd hate to be in that situation so if I can help...I will. You can def. use that story, just don't mention anything about rooting or uninstalling bloat. I would assume that they can't check for anything because the phone wont start up. Hopefully you didn't hard brick it...if that's the case then not much you can do except try and send it out for a JTag...but even then I don't know if you can with MF3.
The best lies have some kernel of truth buried in them. Tell them you just purchased the phone from someone off craigslist, and when you got home with it, you realized that most of the apps and functions weren't working at all. Might just get lucky.
Tremulant1 said:
No problem man, i'd hate to be in that situation so if I can help...I will. You can def. use that story, just don't mention anything about rooting or uninstalling bloat. I would assume that they can't check for anything because the phone wont start up. Hopefully you didn't hard brick it...if that's the case then not much you can do except try and send it out for a JTag...but even then I don't know if you can with MF3.
Click to expand...
Click to collapse
Well im not familiar with what hard bricking is but the phone still kind of works. I mean i can turn it on and off and i can open up the recovery and custom os downloading screens by holding all the buttons down or whatever. So far all I've seen is that this damn MF3 update is more evil than satan himself. Im seriously regretting not trading for the T-Mobile version and unlocking it. But whats done is done i guess. Hopefully theres something they can do, Ill just stick to my restoring issue story, ive noticed the people at best buy dont really give two ****s about anything (well at least my best buy) but anyways, thanks for the help man, I really appreciate it
jt1019 said:
The best lies have some kernel of truth buried in them. Tell them you just purchased the phone from someone off craigslist, and when you got home with it, you realized that most of the apps and functions weren't working at all. Might just get lucky.
Click to expand...
Click to collapse
This might seriously work, but Im not 100% that it would, I got the phone several weeks ago and the lady i traded it with left the damn password on it like an idiot. So i had to go in there and get it restored after i spent 30 minutes convincing the guy that i didnt steal it
But I might definitely try this if the same person isnt working the counter, because this might help me if they find out its rooted, I can just play the dumb card and tell them that i had no idea.
lmfao its so evil and genius that it just might work
Thanks!!! :laugh:
If you were using safestrap don't you have another ROM slot that is working fine? Did you only have the stock ROM?
Sent from my GT-I9505 using xda app-developers app
irootbeer said:
Hey man i really appreciate the help, like you dont know how much youve saved me lol, id still be running around freaking out if it werent for you. But the funny thing is, I was using safestrap, i guess i just f****d something up while i was deleting bloatware. Now about the story, do you think they would buy it if i told them that something messed up and i tried to restore it, but the phone shut off halfway through, so now it wont start back up? I know theres a way to check some number and if they see something then they wont mess with it, so will that affect me at all? Also since it was rooted do you think theyll notice that too? I mean, I figure it would be pretty hard to do so since the phone is so messed up at the moment. I dont want to go in there and have them tell me that they wont do anything because I will flip some major s**t. I dont want to walk out of there with a $700 paperweight lmfao
Click to expand...
Click to collapse
Have you took it to best buy yet? If not restart the phone, but while it is turning on hold POWER HOME and VOLUME DOWN while starting your phone. When you get the screen asking for a custom os, press cancel which I am pretty sure is volume down. That will start your phone. You will still not be able to restore your phone, or access recovery. Be careful what you do with root because if you mess it up you can't fix it. In super SU's settings, there is a full unroot option. Press that. Go through the process. After that, go to your settings, and do a "factory reset." It won't work. It will take you to the failed ODIN screen again. Leave it like that when taking it in to best buy and say you can't start it. Its just a good idea to remove root incase they do manage to start it up.
Sent from my SAMSUNG-SGH-I337 using Tapatalk 4
---------- Post added at 11:57 PM ---------- Previous post was at 11:54 PM ----------
irootbeer said:
Well im not familiar with what hard bricking is but the phone still kind of works. I mean i can turn it on and off and i can open up the recovery and custom os downloading screens by holding all the buttons down or whatever. So far all I've seen is that this damn MF3 update is more evil than satan himself. Im seriously regretting not trading for the T-Mobile version and unlocking it. But whats done is done i guess. Hopefully theres something they can do, Ill just stick to my restoring issue story, ive noticed the people at best buy dont really give two ****s about anything (well at least my best buy) but anyways, thanks for the help man, I really appreciate it
Click to expand...
Click to collapse
Hard bricking is when your phone won't light up at all and there is no sign of life. You're fine - it still kinda works. Your phone isn't even "bricked", your recovery is just fried.
Sent from my SAMSUNG-SGH-I337 using Tapatalk 4
I apologize if my situation is here somewhere. I have read through so many forums and can't find what I need, plus I am sort of new at this. So here goes.
I rooted my Samsung I337 about 8 months ago for the first time. I can't remember exactly how, but I followed a thread here to do it. It worked perfectly! I then flashed the Golden Eye rom to it through TWRP. I have loved it since then. I did a back up of my original rom on my phone from the start. Well, I decided yesterday to unroot it. I followed the directions from a thread here and it seems to have worked except that when I turn it on, the custom screen is first. However, I have no supersu and when I try to get rooting apps it tells me I need to root my phone. So I assume it worked.
Well, I have used it for a day and now remember why I rooted it in the first place. I want to put it back but can't seem to do that. I downloaded Odin, connected my phone, and when I try and download the file to it, it fails. This is what I get.
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CF-Auto-Root-jflte-jfltexx-gti9505.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Odin v.3 engine (ID:7)..
<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> recovery.img
<ID:0/007> NAND Write Start!!
<ID:0/007> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
The only thing I can see is that I am told the COM port should be yellow and mine is blue. Does that make a difference? What could the issue be? Any help would be awesome!
Ok, I figured it out. I went about it a different way. Odin wasn't working for me so I went the route of Motochopper and it worked perfectly.
Now, my question is, before I rooted again I wanted to upgrade from 4.2.2 to 4.3. However, every time it tried, it failed. Each time it would download the update it would reboot to TWRP and then I would get the "something interrupted the download" so it wouldn't finish. How would I get around that? How do I get the update?
traderkat64 said:
Ok, I figured it out. I went about it a different way. Odin wasn't working for me so I went the route of Motochopper and it worked perfectly.
Now, my question is, before I rooted again I wanted to upgrade from 4.2.2 to 4.3. However, every time it tried, it failed. Each time it would download the update it would reboot to TWRP and then I would get the "something interrupted the download" so it wouldn't finish. How would I get around that? How do I get the update?
Click to expand...
Click to collapse
Don't. Getting the update will lock your bootloader and you won't get TWRP and any ROM freedom anymore. If you want 4.3, use the StockUp ROM or something. Then you can still switch to something like Google Edition 4.4.2 or any other ROM if you ever want to.
DeadlySin9 said:
Don't. Getting the update will lock your bootloader and you won't get TWRP and any ROM freedom anymore. If you want 4.3, use the StockUp ROM or something. Then you can still switch to something like Google Edition 4.4.2 or any other ROM if you ever want to.
Click to expand...
Click to collapse
Ok, I won't update!! Thanks!!!!
I have been literally sitting in front of my PC for hours on end to try and resolve this issue. I cant get back my current firmware now even. Just stuck on the recovery mode. I flashed NCG kernal and it went through as normal, however, all it does not is after the samsung loading sign it goes back into system recovery. I have tried everything from cache wipe to factory reset, system reboot, everything! it just does the same thing - goes back into recovery mode- it is getting really frustrating for me. I would really appreciate it if someone could tell me exactly how to get out of it and use the phone as normal again.
I am on sm-g900v
G900VVRU2BOG5
Verizon mobile S5
I have tried to flash almost all the available ROMS and nothing works everytime this come up: ( i am using the latest Kies drivers, Odin 3.10.6, etc)..
<OSM> Please wait..
<OSM> ALL_VZW_G900VVRU1ANCG_G900VVZW1ANCG_964333_REV00_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Added!!
<ID:0/007> Odin engine v(ID:3.1005)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Set PIT file..
<ID:0/007> DO NOT TURN OFF TARGET!!
<ID:0/007> Get PIT for mapping.. - i have the pit file and if i use it to flash i get the same output failed completion.
<ID:0/007> Firmware update start..
<ID:0/007> SingleDownload.
<ID:0/007> aboot.mbn
<ID:0/007> NAND Write Start!!
<ID:0/007> FAIL! (Auth)
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
PLEASE HELP. THANK YOU
You are on the latest OTA of BOG5. The bootloader is completely locked down and you cannot root, downgrade, or flash anything. You are stuck with the phone as is. You will have to find the BOG5 full stock firmware .tar file and flash that through ODIN to get your phone back.
Damn!!!!
do you know any links from where i can download the BOG5 firmware from?
I am having the exact same issue. Any help is appreciated!
I am also stuck with the same issue on my S5. I attempted to flash the NCG Kernel from Android 5.0 using the file referenced in here: androidbiits.com/root-verizon-samsung-galaxy-s5-sm-g900v-android-4-4-4-kitkat/ (sorry I can't post links yet). Now my phone can't leave recovery mode. Did you guys figure out where to get the BOG firmware or how to fix this issue?
You need to reinstall the BOG5 firmware on the S5 again. You can download it via sammobile.com You can pay £5.40 approx if your from UK and download the firmware quicker within an hour otherwise be prepared to wait 11 hours minimum for download to complete.
So I managed to get mine back working by using the VZW-G900VVRU2BOG5-20150813111348.zip firmware downloaded from Sammobile.com and flashing using Odin3.
Used the first firmware on Sammobile firmware page for model SM-G900V
Unzipped the file and flashed the .md5
Back up and running.
Hope this helps someone.
wgafsck said:
I am having the exact same issue. Any help is appreciated!
Click to expand...
Click to collapse
jac1985 said:
I am also stuck with the same issue on my S5. I attempted to flash the NCG Kernel from Android 5.0 using the file referenced in here: androidbiits.com/root-verizon-samsung-galaxy-s5-sm-g900v-android-4-4-4-kitkat/ (sorry I can't post links yet). Now my phone can't leave recovery mode. Did you guys figure out where to get the BOG firmware or how to fix this issue?
Click to expand...
Click to collapse
smn216 said:
You need to reinstall the BOG5 firmware on the S5 again. You can download it via sammobile.com You can pay £5.40 approx if your from UK and download the firmware quicker within an hour otherwise be prepared to wait 11 hours minimum for download to complete.
Click to expand...
Click to collapse
Seriously, do none of you have even the basic, simple ability to look through these forums at all? The answer to your question is right here in the Verizon Galaxy S5 General forum:
http://forum.xda-developers.com/verizon-galaxy-s5/general
You simply scroll down to the fourth thread and see that it is this one:
http://forum.xda-developers.com/verizon-galaxy-s5/general/g900vvru2bog5-factoryodintarimage-t3179527
The title of the thread is literally "G900VVRU2BOG5_Factory_Odin_Tar_Image. Good Lord!
landshark68 said:
Seriously, do none of you have even the basic, simple ability to look through these forums at all? The answer to your question is right here in the Verizon Galaxy S5 General forum:
http://forum.xda-developers.com/verizon-galaxy-s5/general
You simply scroll down to the fourth thread and see that it is this one:
http://forum.xda-developers.com/verizon-galaxy-s5/general/g900vvru2bog5-factoryodintarimage-t3179527
The title of the thread is literally "G900VVRU2BOG5_Factory_Odin_Tar_Image. Good Lord!
Click to expand...
Click to collapse
Hey man, I am new here. I was freaking out the other night because everything I was trying was failing. I understand with a little more patience and effort I could have found this. Then again with a little more research before attempting to root I probably would have avoided the whole issue. I messed up, my bad.
Seriously, do none of you have even the basic, simple ability to look through these forums at all?
Click to expand...
Click to collapse
Same here, in fact it was my first time posting and I was also kind of lost. In any case, thanks for the lesson and the links.
wgafsck said:
Hey man, I am new here. I was freaking out the other night because everything I was trying was failing. I understand with a little more patience and effort I could have found this. Then again with a little more research before attempting to root I probably would have avoided the whole issue. I messed up, my bad.
Click to expand...
Click to collapse
Understood. It just gets very old and frustrating answering the same questions over and over again, and questions for which the answer is already readily available. Glad you got it straightened out, and that you realized more research before embarking on your adventure would have helped. When it comes to messing around with an expensive piece of hardware like these smart phones, it's best to think of the carpentry line - measure twice, cut once. Read, read, read, and make sure you know what you are doing before you do it when it comes to rooting and modding your phone.
Thanks a million! I thought my phone is toasted.