Well I decided to go completely back to stock and update through Verizon's OTA's until I get 4.1.2 before I try the minitab rom again. Well I odin'd back with no issues, got the first OTA installed and it worked fine. Got the newest one and it seemed to install just fine, but when I tried to boot it up it was bootlooping on the note ii logo. Pretty much try to boot up for maybe half a second and then start over. I tried to Odin back to stock again but it's failing on the boot.img. I am really hoping that installing the newest OTA didn't corrupt it but that's the way it seems, I am trying to dl the full restore without keeping the bootloader unlocked and see if that works. Thing that pisses me off is I have flashed probably fifty roms through all my phones yet never once bricked. Now the first time I take an OTA I have a $600 paperweight.
Well I tried the full restore in Imnuts' thread and it's still failing at boot.img so I am guessing I am screwed. Now the question is will Verizon send me a new one under warranty since it was something from them that caused it. Odin just shows this:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CI605_I605VRLJB_I605VRALJB_CL414933_HWID04_HW_Rev0406_low_ship_user.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> boot.img
<ID:0/003> NAND Write Start!!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
dmonger11b said:
Well I tried the full restore in Imnuts' thread and it's still failing at boot.img so I am guessing I am screwed. Now the question is will Verizon send me a new one under warranty since it was something from them that caused it. Odin just shows this:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CI605_I605VRLJB_I605VRALJB_CL414933_HWID04_HW_Rev0406_low_ship_user.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> boot.img
<ID:0/003> NAND Write Start!!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Try this
http://forum.xda-developers.com/showthread.php?t=2280680
Sent from my SCH-I605 using XDA Premium HD app
dmonger11b said:
Well I decided to go completely back to stock and update through Verizon's OTA's until I get 4.1.2 before I try the minitab rom again. Well I odin'd back with no issues, got the first OTA installed and it worked fine. Got the newest one and it seemed to install just fine, but when I tried to boot it up it was bootlooping on the note ii logo. Pretty much try to boot up for maybe half a second and then start over. I tried to Odin back to stock again but it's failing on the boot.img. I am really hoping that installing the newest OTA didn't corrupt it but that's the way it seems, I am trying to dl the full restore without keeping the bootloader unlocked and see if that works. Thing that pisses me off is I have flashed probably fifty roms through all my phones yet never once bricked. Now the first time I take an OTA I have a $600 paperweight.
Click to expand...
Click to collapse
It's been a while since I've done any troubleshooting, but checkout this thread by Adam Outler called "DON'T ACCEPT OTA UPDATES" in the Verizon Galaxy Note II General section. I'm aware that you aren't experiencing this specific problem, but it's possible that it may fix your boot loop problem.
If you happen to get your phone back up and running, I'd suggest checking out the Verizon Galaxy Note II Android Development section, because there are a couple of flashable stock 4.1.2 ROMs available. There're basically the OTA 4.1.2, but modified so that users with unlocked bootloaders can flash it as though they are accepting the OTA 4.1.2 without loosing root and their unlocked bootloaders.
larry_thagr81 said:
It's been a while since I've done any troubleshooting, but checkout this thread by Adam Outler called "DON'T ACCEPT OTA UPDATES" in the Verizon Galaxy Note II General section. I'm aware that you aren't experiencing this specific problem, but it's possible that it may fix your boot loop problem.
If you happen to get your phone back up and running, I'd suggest checking out the Verizon Galaxy Note II Android Development section, because there are a couple of flashable stock 4.1.2 ROMs available. There're basically the OTA 4.1.2, but modified so that users with unlocked bootloaders can flash it as though they are accepting the OTA 4.1.2 without loosing root and their unlocked bootloaders.
Click to expand...
Click to collapse
Awesome thank you. Worked perfectly. I feel kinda embarrassed I didn't look in Adam's thread. But the issue was caused by something a little different than what he warned against. Either way phone booted back up. Definitely irritated I didn't look better,
Glad I could point you in the right direction.
Related
Ok so by daughter let her boyfriend try to root her phone well this guy messed her phone all up he flashed a sprint image onto a verizon phone.
So it's not fully bricked yet I was able to use this post http://forum.xda-developers.com/showthread.php?t=2024207 and put verizon image back onto the phone after about 58 times I used Root66 stock VRALJB 4.1.1 12/2/12 it boots but it seems the radio is still messed up it has a big circle with a line threw it where the signal bar would be and there is no info Min,PRL,network. if I try and flash I605_VRALJB_Restore.tar.md5
if fails at radio if i try and flash sch-i605-16gb.pit it fails. If I try and do this it fails do to the pit http://forum.xda-developers.com/showthread.php?t=2272066. and throws up a error about catch and dev catch. this is all new to me but with all the helpful post on xda it's gotten
me this far. so Is there any way to fix this phone or is it shot
http://forum.xda-developers.com/showthread.php?p=35833930
There is a thread with all the vzw modems, but I can't find it right now . The third post in this thread has a section titled add ons and it has the most current vzw modem. Try flashing that in recovery and see if you get a signal
thanks that helped now to figure out how to fix the pit
zeroloop said:
thanks that helped now to figure out how to fix the pit
Click to expand...
Click to collapse
In the first linked thread you posted, in section 1b use the Root66 and the pit file. That should work
And just a side note, only use files and info for the vzw sch-i605. Do not try anything from a different carrier's version of the note2. Nothing good will come of it
Ok this is what happens when i try and flash the pit sch-i605-16gb.pit from the above post
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003>
<ID:0/003> Re-Partition operation failed.
<ID:0/003> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
This is what happens when i try and use oden to go back to CI605_I605VRLJB_I605VRALJB_CL414933_HWID04_HW-Rev0406_low_ship_user.tar.md5
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I605_VRALJB_Restore.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> boot.img
<ID:0/003> NAND Write Start!!
<ID:0/003> cache.img
<ID:0/003> hidden.img
<ID:0/003> modem.bin
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<ID:0/003> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
that kid did a good job on her phone smh
zeroloop said:
Ok this is what happens when i try and flash the pit sch-i605-16gb.pit from the above post
that kid did a good job on her phone smh
Click to expand...
Click to collapse
Are you using the Root66 and pit file at the same time in Odin? If you are just using the pit file, use both and see what happens
flashing another carriers modems is a big no no....tell your daughter to dump the dumbass!! lol
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> root66_VZW_stock_system.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003>
<ID:0/003> Re-Partition operation failed.
<ID:0/003> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
droidstyle said:
flashing another carriers modems is a big no no....tell your daughter to dump the dumbass!! lol
Click to expand...
Click to collapse
I was hoping you would see this thread and chime in. Is there any chance of hope for this guy?
yea this guy she is dating is a real job smh
like Boosted was asking any hope for me or is this a waste of my time I'm a big noob with all this I know how to read and that's what has got me this far and the help of Boosted. but no matter what i do the pit fails and it fails at radio in the flash and at this moment it says baseband version unkown and still shows no network even after flashing the modem and it says it took it
zeroloop said:
yea this guy she is dating is a real job smh
like Boosted was asking any hope for me or is this a waste of my time I'm a big noob with all this I know how to read and that's what has got me this far and the help of Boosted. but no matter what i do the pit fails and it fails at radio in the flash and at this moment it says baseband version unkown and still shows no network even after flashing the modem and it says it took it
Click to expand...
Click to collapse
I guess the better question is since it is your daughter's phone, you did get insurance on it, right? If so, get a hammer and beat the hell out of it to take out your frustration about the boyfriend. Then call verizon and say you need a new phone because your daughter says she "dropped her phone." Pay the deductible and call it done
Well that's why I'm here or i would have took a sledge hammer to it but I got the phone from a friend. so if i cant fix it I'm sol
zeroloop said:
Well that's why I'm here or i would have took a sledge hammer to it but I got the phone from a friend. so if i cant fix it I'm sol
Click to expand...
Click to collapse
Quite a few years ago I got a phone from a friend and I called and they let me add insurance to it. I broke it like 3 months later and got a replacement. It can't hurt to call and find out
ancDis and
ok will try that Monday
Ok called them they will not do anything not there phone so they will not cover it at all so guess it's trash unless someone has anymore ideas
zeroloop said:
yea this guy she is dating is a real job smh
like Boosted was asking any hope for me or is this a waste of my time I'm a big noob with all this I know how to read and that's what has got me this far and the help of Boosted. but no matter what i do the pit fails and it fails at radio in the flash and at this moment it says baseband version unkown and still shows no network even after flashing the modem and it says it took it
Click to expand...
Click to collapse
I will do some digging around but its not looking good.
droidstyle said:
I will do some digging around but its not looking good.
Click to expand...
Click to collapse
ok thanks for all the help
Yep, he really fubar'd it. He must have flashed both Sprint rom + Sprint radio. People often flash roms built for other carriers with no issues, but if you flash a Sprint radio on a VZW phone, your odds of bricking increase exponentially. I would make the boyfriend buy a new phone and be done with it.
Sent from my SCH-I605 using Tapatalk 2
I have searched everywhere (Not just XDA Forums) for a solution to my issue. Noe is to be found. Help me Android Geniuses, you are my only hope.
I Rooted my Verizon Note 2 LTE with Casual, and installed a sexy new ROM. I was loving it, till I realized I was no longer connected to the network. Not to worry! I had backed everything up using TWRP, so I restored the efs partition. Hmm, that didn't work.
Fast forward to me trying to flash my device back to stock, and it failing over and over (my flash count was at 18). Every time it failed in exactly the same spot: Modem.bin
Finally tried the "Root66" ROM, and it worked. However, my device is still rooted, no modem, no imei, and it still says minimum of 1 flash, and that I'm using custom ROM. Considering I have to warranty this phone, I need it back to stock for real. Can anyone help??
ODIN Log:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I605_VRALJB_Restore.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> boot.img
<ID:0/004> NAND Write Start!!
<ID:0/004> cache.img
<ID:0/004> hidden.img
<ID:0/004> modem.bin
<ID:0/004> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
ArcelasTheNoob said:
I have searched everywhere (Not just XDA Forums) for a solution to my issue. Noe is to be found. Help me Android Geniuses, you are my only hope.
I Rooted my Verizon Note 2 LTE with Casual, and installed a sexy new ROM. I was loving it, till I realized I was no longer connected to the network. Not to worry! I had backed everything up using TWRP, so I restored the efs partition. Hmm, that didn't work.
Fast forward to me trying to flash my device back to stock, and it failing over and over (my flash count was at 18). Every time it failed in exactly the same spot: Modem.bin
Finally tried the "Root66" ROM, and it worked. However, my device is still rooted, no modem, no imei, and it still says minimum of 1 flash, and that I'm using custom ROM. Considering I have to warranty this phone, I need it back to stock for real. Can anyone help??
ODIN Log:
Added!!
Enter CS for MD5..
Check MD5.. Do not unplug the cable..
Please wait..
I605_VRALJB_Restore.tar.md5 is valid.
Checking MD5 finished Sucessfully..
Leave CS..
Odin v.3 engine (ID:4)..
File analysis..
SetupConnection..
Initialzation..
Get PIT for mapping..
Firmware update start..
boot.img
NAND Write Start!!
cache.img
hidden.img
modem.bin
FAIL!
All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
hey bro, have you unlocked the bootloader? if so and you're trying to go back to stock try the alternative stock odin file from imnuts.
EDITuno: http://www.androidfilehost.com/?fid=9390225151984927096
theres the link to his alt restore odin package. idk if that'll help fix the modem.bin failure, but it should help someway. hope it does! if you need anymore help you can pm me if you need to.
I'm curious to what rom you flashed. Was it for a Verizon note 2? If you get no network, try flashing the modem in recovery. That should solve it
Link for modem download.
http://www.androidfilehost.com/?fid=22946563261203878
Follow droidstyle's guide. Read his thread.
http://forum.xda-developers.com/showthread.php?p=34891181
EDIT: Just realized you are making multiple threads for the same question. Sorry dude, that's my only rule. No more help. Also noticed that you flashed an international rom. Good job :thumbup: This is why you are supposed to READ before flashing
Sent From My Sticky Note, Too?
Not needed
I apoligze if it looks like I posted this question multiple times. I was told to post in a different forum, but figured more info=better.
I returned my phone to Best Buy, replacement in a few days. So thank you for all the help, next time I'll be more careful.
i have a galaxy s 4 verizon i have mdk and i have tried unrooting it because my friend tried rooting it while i was gone and messed up the process but im using odin3.07 and im getting this.
<ID:0/007> Removed!!
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> SCH-I545_MDK_562219_Stock_Restore.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> sbl1.mbn
<ID:0/007> NAND Write Start!!
<ID:0/007> sbl2.mbn
<ID:0/007> sbl3.mbn
<ID:0/007> rpm.mbn
<ID:0/007> aboot.mbn
<ID:0/007> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1
my phone says start [224,1440]
sw rev. check fail : fused 5, binary 1
and ive tried 2 other stock files and i still get the same thing i even tried a Me7 to please help
Im slightly confused?
You were still on MDK, the original firmware the phone shipped with after this long, but you were not rooted?
Your sure you were still on MDK?
I haven't played with odin a ton, but odin anything but MDK if that is really what your on. That is the ONLY firmware that has a bootloader bypass to allow a full custom recovery. Later base bands cannot, and must use safestap which only allows roms based on the kernel of the phones latest update (no aosp, cm, custom kernels, ect...)
More recent updates blow a fuse in the phone and once that fuse is blown you can only flash the current or newer updates, and there is no current way to go back to the MDK firmware.
How did you friend try and flash? What went wrong?
From the log, I hope I am wrong, but it looks like your friend already updated you phone.
But I believe it failing at aboot and complaining about fuses and binary switches is exactly what that means...
If he flashed Mk2 or MJ7 in an attempt to follow the info on rooting those, then those will be the only one you can currently restore to, in which case look up the guide on how to update to MJ7 and root, and follow the links for the MJ7 odin file, saferoot & safestrap.
Wait for someone else to confirm though. Hopefully I am wrong, and I would hate to lose an MDK device on my advice
scryan said:
Im slightly confused?
You were still on MDK, the original firmware the phone shipped with after this long, but you were not rooted?
Your sure you were still on MDK?
I haven't played with odin a ton, but odin anything but MDK if that is really what your on. That is the ONLY firmware that has a bootloader bypass to allow a full custom recovery. Later base bands cannot, and must use safestap which only allows roms based on the kernel of the phones latest update (no aosp, cm, custom kernels, ect...)
More recent updates blow a fuse in the phone and once that fuse is blown you can only flash the current or newer updates, and there is no current way to go back to the MDK firmware.
How did you friend try and flash? What went wrong?
From the log, I hope I am wrong, but it looks like your friend already updated you phone.
But I believe it failing at aboot and complaining about fuses and binary switches is exactly what that means...
If he flashed Mk2 or MJ7 in an attempt to follow the info on rooting those, then those will be the only one you can currently restore to, in which case look up the guide on how to update to MJ7 and root, and follow the links for the MJ7 odin file, saferoot & safestrap.
Wait for someone else to confirm though. Hopefully I am wrong, and I would hate to lose an MDK device on my advice
Click to expand...
Click to collapse
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> COMBINATION_I545VRUAME7_I545VZWAME7_690088_REV06_u ser_low_ship_MULTI_CERT.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> sbl1.mbn
<ID:0/007> NAND Write Start!!
<ID:0/007> sbl2.mbn
<ID:0/007> sbl3.mbn
<ID:0/007> rpm.mbn
<ID:0/007> aboot.mbn
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> VRUAMDK_NoWipe.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> NON-HLOS.bin
<ID:0/007> NAND Write Start!!
<ID:0/007> aboot.mbn
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Im using Odin v1.85
this what i get from trying mdk and me7
scryan said:
Im slightly confused?
You were still on MDK, the original firmware the phone shipped with after this long, but you were not rooted?
Your sure you were still on MDK?
I haven't played with odin a ton, but odin anything but MDK if that is really what your on. That is the ONLY firmware that has a bootloader bypass to allow a full custom recovery. Later base bands cannot, and must use safestap which only allows roms based on the kernel of the phones latest update (no aosp, cm, custom kernels, ect...)
More recent updates blow a fuse in the phone and once that fuse is blown you can only flash the current or newer updates, and there is no current way to go back to the MDK firmware.
How did you friend try and flash? What went wrong?
From the log, I hope I am wrong, but it looks like your friend already updated you phone.
But I believe it failing at aboot and complaining about fuses and binary switches is exactly what that means...
he said he followed this youtube video https://www.youtube.com/watch?v=uii_mYm8IGE
If he flashed Mk2 or MJ7 in an attempt to follow the info on rooting those, then those will be the only one you can currently restore to, in which case look up the guide on how to update to MJ7 and root, and follow the links for the MJ7 odin file, saferoot & safestrap.
Wait for someone else to confirm though. Hopefully I am wrong, and I would hate to lose an MDK device on my advice
Click to expand...
Click to collapse
he said this is the youtube video he followed to do it https://www.youtube.com/watch?v=uii_mYm8IGE
A1C_Malone said:
he said this is the youtube video he followed to do it https://www.youtube.com/watch?v=uii_mYm8IGE
Click to expand...
Click to collapse
Yeah that is the root method for the latest official firmware...If you had MDK you had the oldest firmware avalible (really really good thing)
Do you know if he used odin at all? are you sure you were on MDK originally? This would mean that you got the phone when it first came out and never took an update?
Again, it looks like your phone was updated to MK2 or MJ7, the latest official firmware. If that is true only one of those two restore files will work with odin as you can only odin to what you currently have or newer...
If you don't ever care about custom recovery and only want root, you probably fix it by downloading MJ7, and using odin to flash that. (As I said, the thread on how to update to MJ7 and install safestrap/HD11 will have a link for that file and is on the first page)
IF YOU HAD MDK AND WANT CUSTOM RECOVERY DO NOT FLASH ANYTHING WITH ODIN OTHER THEN MDK. Wait till someone smarter then me can help you figure it out, and make sure your friend hasn't already updated you beyond being able to go back to MDK.
scryan said:
Yeah that is the root method for the latest official firmware...If you had MDK you had the oldest firmware avalible (really really good thing)
Do you know if he used odin at all? are you sure you were on MDK originally? This would mean that you got the phone when it first came out and never took an update?
Again, it looks like your phone was updated to MK2 or MJ7, the latest official firmware. If that is true only one of those two restore files will work with odin as you can only odin to what you currently have or newer...
If you don't ever care about custom recovery and only want root, you probably fix it by downloading MJ7, and using odin to flash that. (As I said, the thread on how to update to MJ7 and install safestrap/HD11 will have a link for that file and is on the first page)
IF YOU HAD MDK AND WANT CUSTOM RECOVERY DO NOT FLASH ANYTHING WITH ODIN OTHER THEN MDK. Wait till someone smarter then me can help you figure it out, and make sure your friend hasn't already updated you beyond being able to go back to MDK.
Click to expand...
Click to collapse
where can i download mj7 or mk2 stock i have a verizon s4
Sounds like you may want to follow this... If a newer firmware was attempted to be flashed..http://forum.xda-developers.com/showthread.php?t=2579278. IF NO LONGER MDK AVAILABLE FOLLOW THOSE STEPS.
A1C_Malone said:
where can i download mj7 or mk2 stock i have a verizon s4
Click to expand...
Click to collapse
use Kies and get a factory clean install
Ok, so here is the deal.
I have the Samsung Galaxy Mega 6.3 with U.S Cellular (SCH-R960) and I have run into some problems. What I did was try to root. Flashed CWM Recovery in Odin and when I tried to boot back up again, I was stuck in bootloop. So I tried to revert back to stock by flashing the stock firmware for my phone in Odin, the problem is, everytime I try and do that, I get this:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9200XXUCNC2_I9200OLBCNC1_I9200XXUCNC2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> sbl1.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Also, on the phone screen it says
SECURE CHECK FAIL: sbl1
I can boot into recovery and also into download mode. Although if I try to just boot the phone normal it just stays on the Samsung Galaxy Mega logo screen. I have tried sideloading a .zip and that also fails.
Does anyone have any idea of how to fix this? Any help would be greatly appreciated.
Deleted cause by my noob. Sorry
Sent from my Nexus 7 using Tapatalk
yusopa said:
Why you dont try go to galaxy mega thread to get help. I think you face something big what we call knox problem. You cant root your device before you know your device surely. Samsung provide new bootloader with knox right now.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Thought this was the Mega forum? And yes I know about knox I bricked an S3 because of it but I didn't think it was added until 4.3?
the firmware you are trying to flash (which is i9200) is not for your us cellular version of mega (which is r960).
find the correct one then proceed.
yusopa said:
Why you dont try go to galaxy mega thread to get help. I think you face something big what we call knox problem. You cant root your device before you know your device surely. Samsung provide new bootloader with knox right now.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
jk0l said:
the firmware you are trying to flash (which is i9200) is not for your us cellular version of mega (which is r960).
find the correct one then proceed.
Click to expand...
Click to collapse
I'm not using it as a phone anymore, just kinda as a tablet. So does it matter that it isnt the r960 firmware?
vBIGLEWISv said:
Ok, so here is the deal.
I have the Samsung Galaxy Mega 6.3 with U.S Cellular (SCH-R960) and I have run into some problems. What I did was try to root. Flashed CWM Recovery in Odin and when I tried to boot back up again, I was stuck in bootloop. So I tried to revert back to stock by flashing the stock firmware for my phone in Odin, the problem is, everytime I try and do that, I get this:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9200XXUCNC2_I9200OLBCNC1_I9200XXUCNC2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> sbl1.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Also, on the phone screen it says
SECURE CHECK FAIL: sbl1
I can boot into recovery and also into download mode. Although if I try to just boot the phone normal it just stays on the Samsung Galaxy Mega logo screen. I have tried sideloading a .zip and that also fails.
Does anyone have any idea of how to fix this? Any help would be greatly appreciated.
Click to expand...
Click to collapse
Try with samsung kies to revert back to stock..See it helps or not.
Carnage said:
Try with samsung kies to revert back to stock..See it helps or not.
Click to expand...
Click to collapse
Kies doesn't work either. It wont connect and when I try manually it wont accept my S/N. I'm stuck here I'm not sure what to do.
I am also found ths problem. Kies also not working... Bad experience..
Bro grab the right firmware for the phone just cause its not gonna be used as a phone does not mean that you don't have to have the correct **** for the phone lol
Sent from my sgh-i527 with xda premium 4
HOPSIN-KAT KEYBOARDS IS NOW UP AND RUNNING CHECK EM OUT OVER AT THE CANDY SHOP!
http://forum.xda-developers.com/showthread.php?p=52221912
vBIGLEWISv said:
Kies doesn't work either. It wont connect and when I try manually it wont accept my S/N. I'm stuck here I'm not sure what to do.
Click to expand...
Click to collapse
Are you really cannot boot into download mode?..vol down+power button..try power on the device,remove the battery,put it back again,and quickly press the download mode combination keys (vol down+power button) see it boots to download mode or not..if its boot, grab your latest firmware and flash it via odin. About the kies,try to uninstall and download the latest version of kies solve it..
EDIT:I have search your firmware and don't find any link.you have to wait until the firmware for your specific model number released by Samsung.
hopsin4444 said:
Bro grab the right firmware for the phone just cause its not gonna be used as a phone does not mean that you don't have to have the correct **** for the phone lol
Sent from my sgh-i527 with xda premium 4
HOPSIN-KAT KEYBOARDS IS NOW UP AND RUNNING CHECK EM OUT OVER AT THE CANDY SHOP!
http://forum.xda-developers.com/showthread.php?p=52221912
Click to expand...
Click to collapse
Thats the problem the stock firmware doesnt exist for my phone or at least I cant find it.
well then, thats unfortunate. im sorry.
so its certain that theres no way for you to go back to stock.
edit:
actually, try to wipe data and cache in recovery then reboot.
if it still bootloops, then I recommend you patiently wait until the stock firmware for your phone is released.
So, I'm obviously quite new here. I rooted my Note 2 back when I first got it about 2 years ago lol. Had it rooted with 4.1.2 on it and some old version of cleanrom.
Having the Note 4 Pre-Ordered, I decided to un-root my phone and update it in case someone wants to buy it off of me.
Basically I unrooted, added new stock rom to it, now it is stuck in bootloop and I cannot boot into recovery.
__________________
What have I done?
1) UnRooted from SuperSU
2) Wipped it in the system settings and TW recovery (CleanROM was still on it)
-
Since it still had the cleanrom on it, I went over to SamMoible to download my version of the stock 4.1.2 Firmware
I ran it in odin and everything went perfect, and it rebooted and now it's stuck in a bootloop. I CANNOT boot it into recovery from PWR+HOME+UVOL
-
Now I've tried running through adb to boot it into recovery and that did not work. I'm guessing because USB Debugging cannot be on with the phone fresh like this.
I can boot it into download, and I've tried re-adding that same stock rom onto the phone and it fails everytime.
I downloaded another SCH-605 4.1.2 stock rom, and it still fails just like the other one.
Log from Odin:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> KIES_HOME_I605VRAMC3_I605VZWAMC3_1098177_REV04_user_low_ship.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> boot.img
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
Can anyone help me? I have no clue on what to do and I cannot find anything online with someone having this same issue.
Thanks a ton!
If you haven't seen it already, you should check out Droidstyle's restore guide at this link: ( http://forum.xda-developers.com/showthread.php?p=34891181). His guide has links and detailed instructions on how to restore back to stock. (go to section 1b for instructions on how to restore back to stock 4.1.2).
As far as ODIN failing... From what I've read, you should connect your phone to a usb 2.0 port on the computer rather usb 3.0, so try different ports. Also make sure to run ODIN as administrator. I've also read that trying different usb cables and disabling antivirus programs can help when ODIN fails.
As you probably know, Android build 4.1.2 is the last build for our phones that allows us to unlock the bootloader... so I would personally restore it back to 4.1.2 and leave it there. I think it would have more value on Swappa if you're going to sell it there.
Hope this helps and Good luck!
mattnmag said:
If you haven't seen it already, you should check out Droidstyle's restore guide at this link: ( http://forum.xda-developers.com/showthread.php?p=34891181). His guide has links and detailed instructions on how to restore back to stock. (go to section 1b for instructions on how to restore back to stock 4.1.2).
As far as ODIN failing... From what I've read, you should connect your phone to a usb 2.0 port on the computer rather usb 3.0, so try different ports. Also make sure to run ODIN as administrator. I've also read that trying different usb cables and disabling antivirus programs can help when ODIN fails.
As you probably know, Android build 4.1.2 is the last build for our phones that allows us to unlock the bootloader... so I would personally restore it back to 4.1.2 and leave it there. I think it would have more value on Swappa if you're going to sell it there.
Hope this helps and Good luck!
Click to expand...
Click to collapse
Hey, I tried changing the ports and made sure it was a 2.0 port.
Still getting the FAIL from odin at the same spot.
EDIT; I ENDED UP FIXING IT WITH SOME HELP FROM MY DAD lol
We had to put a new Pit file on it and re-partition it.
Thanks everyone!
w4sp said:
EDIT; I ENDED UP FIXING IT WITH SOME HELP FROM MY DAD lol
We had to put a new Pit file on it and re-partition it.
Thanks everyone!
Click to expand...
Click to collapse
That's great. I was actually about to suggest some more ideas... and one was to make sure you were using the pit file if you weren't.... lol
Good to hear you got it fixed!!
w4sp said:
Hey, I tried changing the ports and made sure it was a 2.0 port.
Still getting the FAIL from odin at the same spot.
Click to expand...
Click to collapse
I've tried with the new pit file, tried to repartition, using stock_mc3_recovery.tar.md5 and I keep coming across an error. Any ideas?
thewhitespicsk8r said:
I've tried with the new pit file, tried to repartition, using stock_mc3_recovery.tar.md5 and I keep coming across an error. Any ideas?
Click to expand...
Click to collapse
What version of Android is your phone currently running? If it's on 4.3 or 4.4.2, then you can't use ODIN to downgrade back to 4.1.2 because of locked bootloader.
If you can post the error report you're getting in ODIN, it will be useful to assist others with helping you troubleshoot.
mattnmag said:
What version of Android is your phone currently running? If it's on 4.3 or 4.4.2, then you can't use ODIN to downgrade back to 4.1.2 because of locked bootloader.
If you can post the error report you're getting in ODIN, it will be useful to assist others with helping you troubleshoot.
Click to expand...
Click to collapse
I was using 4.4.2 before it crashed.... I know I can't go back to 4.1.2 because it's locked, and I can't seem to figure out why it won't let me go back to the stock software.. I've tried nearly everything.
This is the error:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I605VRUFND7_I605VZWFND7_I605VRUFND7_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> SingleDownload.
<ID:0/004> sboot.bin
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Even at that, if I use sch-i605-16gb for the pit file, I still get nothing
thewhitespicsk8r said:
I was using 4.4.2 before it crashed.... I know I can't go back to 4.1.2 because it's locked, and I can't seem to figure out why it won't let me go back to the stock software.. I've tried nearly everything.
This is the error:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I605VRUFND7_I605VZWFND7_I605VRUFND7_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> SingleDownload.
<ID:0/004> sboot.bin
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Even at that, if I use sch-i605-16gb for the pit file, I still get nothing
Click to expand...
Click to collapse
When you say that you've tried nearly everything to fix it... hopefully you haven't ODIN flashed any other stock firmware onto the device that was from different phones-- if so, you may have messed up the bootloader. Here's a link to the 4.4.2 firmware if you need it, but I bet you got your file from there already.
You've probably tried this... but you could try flashing just the firmware without the pit file to see if that might work. You could also try to flash them both at the same time to see if that might work.
The most common fixes I've read for ODIN errors are to try other USB ports (the ones on the back of the computer near the power supply seem to be good choices and use a usb 2.0 port), try other USB cables (preferably the original one that came with the phone if it's in good shape), turn off Anti virus programs/ firewalls, make sure you are running ODIN as Administrator. Here's a thread that might provide some other tips for ODIN problems: (GUIDE--Troubleshoot a failed ODIN flash). It's for a different phone, so don't use any of the files linked in the thread...... but the tips provided should be helpful for troubleshooting.
If ODIN version 3.07 isn't working, you could try a newer version of ODIN. Here's some links to other ODIN versions that you might try: Download link for ODIN 3.09 ; Download link for ODIN 3.10.0. ~~With the newer ODIN versions, they have replaced the "PDA" slot with "AP"--so the .tar firmware file goes into AP in the newer ODIN. ****(For reference--Here's the XDA Thread where XDA recognized contributor -CALIBAN666- posted these links to newer ODIN versions. Hit the thanks button for him ****
---------------
If you can't get the restore to work with ODIN, you could always try Samsung Kies to see if it can fix the device...
Where to download Kies -- http://www.samsung.com/us/kies/
Emergency Firmware Recovery using Kies 3 -- http://www.samsung.com/us/support/faq/FAQ00059169/81100
I hope that some of this info helps and that you can get it fixed. Good luck!!