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
Related
Need Help here. i tried to factory reset with odin and suddenly i got bootloop so i tried to flash with existing rom that ive used once. but it keeps gives me fail message. tried to flash cwm also but still fail on me. tried new usb stock cable still the same.
here are the log message in odin
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9300XXDLIB_I9300OXFDLI1_I9300XXDLIB_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Added!!
<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> system.img
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
<ID:0/004> Added!!
<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> recovery.img
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
I cant use Kies to restore because i dont know the code.
i cant enter recovery
i dont know how to fix this thing.
ive read in some forum that my NAND might be corrupted..
please help
ive read in some forum that my NAND might be corrupted..
thats how it reads to me .
jje
yes it thought so. im trying to repartition the pit but it too so longg.. seems not working
Try flashing a 3 part stock ics Rom with pit file, let me know if this works please
Had the same problem tried everything posted in here and could't recover it now waiting on warranty replacement, seems this is way more common than I thought.
bligui said:
Had the same problem tried everything posted in here and could't recover it now waiting on warranty replacement, seems this is way more common than I thought.
Click to expand...
Click to collapse
Yes sorry - but pit error problem is related to faulty nand/emmc :crying:
re flashing dont make any difference at all
i sent my SGS3 to the Samsung Service Center. they tried to flash it but no luck so they asked me to leave the unit and replace the mainboard... waiting for it..
ive tried all pit, repartition, etc2.. i gave up
It seems I am not the only one....
Except take it to the health center (Samsung service center), does anyone have luck to fix it by Odin?! becuase I was using custom rom. I just think the Samsung might do the warranty recover with charges, which I don't really want to pay.. many thanks guys.
Sent from my GT-N7000 using xda app-developers app
kk12175 said:
It seems I am not the only one....
Except take it to the health center (Samsung service center), does anyone have luck to fix it by Odin?! becuase I was using custom rom. I just think the Samsung might do the warranty recover with charges, which I don't really want to pay.. many thanks guys.
Sent from my GT-N7000 using xda app-developers app
Click to expand...
Click to collapse
Got my phone back, they replaced the board. luckily its under full warranty. so i wont have to spent a cent...
jeffma said:
Got my phone back, they replaced the board. luckily its under full warranty. so i wont have to spent a cent...
Click to expand...
Click to collapse
So was this covered under warranty? What did you say went wrong with the phone?
voipman2012 said:
So was this covered under warranty? What did you say went wrong with the phone?
Click to expand...
Click to collapse
I said its hang on the samsung logo. when i was trying to factory reset. just act ordinary user that doesnt know how to root :laugh::laugh:
Evening All,
This is most definitely a cry for help from someone not new to Flashing Phones. I have been flash ROMS sicne the days of my HTC Desire. I have never encountered an issue up until recently.
My S3 was running perfectly fine on Android Revolution 16.5. I generally always charge my phone at work and at home so I always have it on. Last night my battery died as I left my charger at my girlfriends. After popping around and picking it back up I charged my phone. It booted up to give me a System UID's inconsistent error for no reason.
I did some searching around and attempted to rectify this matter with the various Factory Resets, Fix Permissions etc. and as far as I got was that I would get to the Samsung Logo and then it would hang.
After much dicking around with ARHD I decided to flash Stock Firmware from Sammfirmware.com. I did this using the Unbranded Firmware and going back to what my Galaxy S3 started with.
GT-I9300_BTU_I9300XXALF2_I9300OXAALF2_I9300XXLF2.tar.md5
This worked and I got safely back into my phone albeit with no signal/mobile network. I looked around and thought because my carrier is O2 I'll flash the O2 firmware. This didn't work so I went back to flashing the unbranded firmware again where I was on before I got this in ODIN:
<OSM> GT-I9300_BTU_I9300XXALF2_I9300OXAALF2_I9300XXLF2.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.
<ID:0/003> Added!!
I now an issue because bootup is stating my firmware upgrade has failed, and now ODIN refuses to reflash the MD5 file again. I just keep getting the same failure message. I am able to reboot into Download Mode and that is it.
Is anyone able to offer me any kind of assistance please?
Mobile Phone: Samsung Galaxy SIII i9300
Carrier: O2
Regards,
James
Lynchie87 said:
Evening All,
This is most definitely a cry for help from someone not new to Flashing Phones. I have been flash ROMS sicne the days of my HTC Desire. I have never encountered an issue up until recently.
My S3 was running perfectly fine on Android Revolution 16.5. I generally always charge my phone at work and at home so I always have it on. Last night my battery died as I left my charger at my girlfriends. After popping around and picking it back up I charged my phone. It booted up to give me a System UID's inconsistent error for no reason.
I did some searching around and attempted to rectify this matter with the various Factory Resets, Fix Permissions etc. and as far as I got was that I would get to the Samsung Logo and then it would hang.
After much dicking around with ARHD I decided to flash Stock Firmware from Sammfirmware.com. I did this using the Unbranded Firmware and going back to what my Galaxy S3 started with.
GT-I9300_BTU_I9300XXALF2_I9300OXAALF2_I9300XXLF2.tar.md5
This worked and I got safely back into my phone albeit with no signal/mobile network. I looked around and thought because my carrier is O2 I'll flash the O2 firmware. This didn't work so I went back to flashing the unbranded firmware again where I was on before I got this in ODIN:
<OSM> GT-I9300_BTU_I9300XXALF2_I9300OXAALF2_I9300XXLF2.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.
<ID:0/003> Added!!
I now an issue because bootup is stating my firmware upgrade has failed, and now ODIN refuses to reflash the MD5 file again. I just keep getting the same failure message. I am able to reboot into Download Mode and that is it.
Is anyone able to offer me any kind of assistance please?
Mobile Phone: Samsung Galaxy SIII i9300
Carrier: O2
Regards,
James
Click to expand...
Click to collapse
ODIN has now told me this:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> GT-I9300_BTU_I9300XXALF2_I9300OXAALF2_I9300XXLF2.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>
<ID:0/003> There is no PIT partition.
<ID:0/003> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
Guess its game over now then?
user flashed wrong file and damaged wiped pit . Or used wrong PIT or ticked repartition etc etc .
You need to flash the correct PIT file see multiple identical posts .
may help.
http://forum.xda-developers.com/showthread.php?t=1796062
JJEgan said:
user flashed wrong file and damaged wiped pit . Or used wrong PIT or ticked repartition etc etc .
You need to flash the correct PIT file see multiple identical posts .
may help.
http://forum.xda-developers.com/showthread.php?t=1796062
Click to expand...
Click to collapse
Hi,
Thanks but I can't even Flash the PIT File :
<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)
If its not the correct PIT file it will fail .
Looks a service centre job now .
jje
JJEgan said:
If its not the correct PIT file it will fail .
Looks a service centre job now .
jje
Click to expand...
Click to collapse
Well any suggestions on how to obtain the correct PIT file then?
Ta.
Lynchie87 said:
Well any suggestions on how to obtain the correct PIT file then?
Ta.
Click to expand...
Click to collapse
sammobile
.com
jje
Lynchie87 said:
Evening All,
This is most definitely a cry for help from someone not new to Flashing Phones. I have been flash ROMS sicne the days of my HTC Desire. I have never encountered an issue up until recently.
My S3 was running perfectly fine on Android Revolution 16.5. I generally always charge my phone at work and at home so I always have it on. Last night my battery died as I left my charger at my girlfriends. After popping around and picking it back up I charged my phone. It booted up to give me a System UID's inconsistent error for no reason.
I did some searching around and attempted to rectify this matter with the various Factory Resets, Fix Permissions etc. and as far as I got was that I would get to the Samsung Logo and then it would hang.
After much dicking around with ARHD I decided to flash Stock Firmware from Sammfirmware.com. I did this using the Unbranded Firmware and going back to what my Galaxy S3 started with.
GT-I9300_BTU_I9300XXALF2_I9300OXAALF2_I9300XXLF2.tar.md5
This worked and I got safely back into my phone albeit with no signal/mobile network. I looked around and thought because my carrier is O2 I'll flash the O2 firmware. This didn't work so I went back to flashing the unbranded firmware again where I was on before I got this in ODIN:
<OSM> GT-I9300_BTU_I9300XXALF2_I9300OXAALF2_I9300XXLF2.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.
<ID:0/003> Added!!
I now an issue because bootup is stating my firmware upgrade has failed, and now ODIN refuses to reflash the MD5 file again. I just keep getting the same failure message. I am able to reboot into Download Mode and that is it.
Is anyone able to offer me any kind of assistance please?
Mobile Phone: Samsung Galaxy SIII i9300
Carrier: O2
Regards,
James
Click to expand...
Click to collapse
u should flash firmware using multiple files... lyk bootloader, csc, pda.. etc..
for creating odin ready pack, search for splitfus in google..
Sent from my GT-S5360 using xda app-developers app
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.
Hey guys, I need some help. I was switching roms and I guess i must have deleted my storage. So I had no rom to install and no backup. I tried to odin back to stock and it failed. Now my phone will only boot to odin mode but it says firmware upgrade encountered a problem. I searched and searched for answers and tried many things but no solutions seem to work. I have tried one click MJ4 full restore, and one click NAB full restore and neither work. they fail. So what can I try next? I have been working on this for hours and I have to go to work in 5 hours and need my phone. Please help.
drunkensunday said:
Hey guys, I need some help. I was switching roms and I guess i must have deleted my storage. So I had no rom to install and no backup. I tried to odin back to stock and it failed. Now my phone will only boot to odin mode but it says firmware upgrade encountered a problem. I searched and searched for answers and tried many things but no solutions seem to work. I have tried one click MJ4 full restore, and one click NAB full restore and neither work. they fail. So what can I try next? I have been working on this for hours and I have to go to work in 5 hours and need my phone. Please help.
Click to expand...
Click to collapse
What was on your phone prior to this happening?
We need the back story up to when you started flashing 2 separate operating systems onto your device (JellyBean, MJ4, TouchWiz KitKat, NAB).
You mention that you were switching roms...what rom were you on, and to what rom did you try to flash?
Sent from my SM-N900P using Xparent BlueTapatalk 2
micmars said:
What was on your phone prior to this happening?
We need the back story up to when you started flashing 2 separate operating systems onto your device (JellyBean, MJ4, TouchWiz KitKat, NAB).
You mention that you were switching roms...what rom were you on, and to what rom did you try to flash?
Sent from my SM-N900P using Xparent BlueTapatalk 2
Click to expand...
Click to collapse
I was on this rom : http://forum.xda-developers.com/showthread.php?t=2567499 and was trying to switch to this rom:
http://forum.xda-developers.com/showthread.php?t=2696396
However I never even started the write because I deleted everything on accident prior to trying to write the rom. I was S-OFF and rooted and I believe I was on 4.3.
Oh then the first thing I did was try to odin this file: N900PVPUCNC5_N900PSPTCNC5_N900PVPUCNC5_HOME.tar.md5
That failed, then I tried the 2 previously mentioned one click odin stocks.
Oh and I was on TWRP 2.6.1 but now I have no recovery.
drunkensunday said:
Oh and I was on TWRP 2.6.1 but now I have no recovery.
Click to expand...
Click to collapse
Have you tried odin twrp to your phone maybe it doesn't like you not having any recovery?
Cheryl
drunkensunday said:
I was on this rom : http://forum.xda-developers.com/showthread.php?t=2567499 and was trying to switch to this rom:
http://forum.xda-developers.com/showthread.php?t=2696396
However I never even started the write because I deleted everything on accident prior to trying to write the rom. I was S-OFF and rooted and I believe I was on 4.3.
Click to expand...
Click to collapse
The MJ4 tar would've worked had you flashed it (you were on MJ4, JellyBean, but on a prerooted rom).
Having failed at MJ4, going with the NAB and NC5 (both KitKat), may have sent your system into a nosedive of confusion.
Tell me if you can get into download mode at all home + power + volume down).
Your version of TWRP is old, but that has nothing to do with this. You need to put your phone back to stock, then upgrade if you want to flash a KitKat rom.
The MJ4 tar file will put stock everything back on your phone, even recovery, so your TWRP will be gone...but you can get it back.
Let me know if you can get into download mode, and we can take it from there.
Sent from my SM-N900P using Xparent BlueTapatalk 2
I can get in to download mode, but it has a triangle with exclamation mak and it says "firmware upgrade encountered an issue. Please select recovery mode in Kies and try again. However the phone still comunicates with oden. The writting process starts but fails every time. I did the 1 click mj4 and it fails as well.
And I don't need to hold buttons to get to download, it's the only screen the phone goes to no matter what.
drunkensunday said:
I can get in to download mode, but it has a triangle with exclamation mak and it says "firmware upgrade encountered an issue. Please select recovery mode in Kies and try again. However the phone still comunicates with oden. The writting process starts but fails every time. I did the 1 click mj4 and it fails as well.
And I don't need to hold buttons to get to download, it's the only screen the phone goes to no matter what.
Click to expand...
Click to collapse
Please quote me when responding, if you don't mind. It let's me know that you've posted something.
As long as you can get into download mode, you can do something, hopefully.
A bricked device doesn't get into anything, won't even power into that screen. It's called brick for that reason.
What happens when you do volume up + power + home? Nothing, stock recovery, download mode, etc? Also, power down completely, and remove your SD card.
You can try...
1. Flashing the tar file via PC Odin in lieu of the one-click package (perhaps at this point not a possibility given that you've tried to flash the latest NC5 tar
2. Taking into Sprint where a root tolerant tech is available, and have them put the latest firmware on it for you, over-the-wire style (speak little, play clueless, Google around before going into the brick-and-mortar location
3. Flashing the NAB or NC5 tar, same way (you already have tried one or both of these I believe
Ultimately, option 2 may be your best hope.
Good luck!
Sent from my SM-N900P using Xparent BlueTapatalk 2
micmars said:
Please quote me when responding, if you don't mind. It let's me know that you've posted something.
As long as you can get into download mode, you can do something, hopefully.
A bricked device doesn't get into anything, won't even power into that screen. It's called brick for that reason.
What happens when you do volume up + power + home? Nothing, stock recovery, download mode, etc? Also, power down completely, and remove your SD card.
You can try...
1. Flashing the tar file via PC Odin in lieu of the one-click package (perhaps at this point not a possibility given that you've tried to flash the latest NC5 tar
2. Taking into Sprint where a root tolerant tech is available, and have them put the latest firmware on it for you, over-the-wire style (speak little, play clueless, Google around before going into the brick-and-mortar location
3. Flashing the NAB or NC5 tar, same way (you already have tried one or both of these I believe
Ultimately, option 2 may be your best hope.
Good luck!
Sent from my SM-N900P using Xparent BlueTapatalk 2
Click to expand...
Click to collapse
Here's the Odin log when I try flashing:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N900PVPUCNC5_N900PSPTCNC5_N900PVPUCNC5_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> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl1.mbn
<ID:0/003> rpm.mbn
<ID:0/003> tz.mbn
<ID:0/003> sdi.mbn
<ID:0/003> NON-HLOS.bin
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
drunkensunday said:
Here's the Odin log when I try flashing:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N900PVPUCNC5_N900PSPTCNC5_N900PVPUCNC5_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> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl1.mbn
<ID:0/003> rpm.mbn
<ID:0/003> tz.mbn
<ID:0/003> sdi.mbn
<ID:0/003> NON-HLOS.bin
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
remove battery from phone..... now with battery removed reinstall battery. boot to recovery by holding volume+ and power button simultaneously.
if you can access any type of stock recovery do a full wipe from it. not if you cant try rebooting computer . try usb in a different port. sometimes its something so simple. could even be a cord issue. do you have another cord to try? any micro usb will work.
kaos420 said:
remove battery from phone..... now with battery removed reinstall battery. boot to recovery by holding volume+ and power button simultaneously.
if you can access any type of stock recovery do a full wipe from it. not if you cant try rebooting computer . try usb in a different port. sometimes its something so simple. could even be a cord issue. do you have another cord to try? any micro usb will work.
Click to expand...
Click to collapse
I do not have any recovery at all. I tried 2 cords, I'll try the reboot of computer now. Does it matter I'm on a Mac using vmware for win 7?
drunkensunday said:
I do not have any recovery at all. I tried 2 cords, I'll try the reboot of computer now. Does it matter I'm on a Mac using vmware for win 7?
Click to expand...
Click to collapse
Are you using the USB 3.0 cord ... That's the only one I use for Odin
Sent from my SM-N900P using Xparent BlueTapatalk 2
Epix4G said:
Are you using the USB 3.0 cord ... That's the only one I use for Odin
Sent from my SM-N900P using Xparent BlueTapatalk 2
Click to expand...
Click to collapse
Yes, but in a usb 2.0 port if it matters....
Reboot and new port gave me a slightly different Odin log but still failed:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<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> sbl1.mbn
<ID:0/003> aboot.mbn
<ID:0/003>
<ID:0/003>
<OSM> All threads completed. (succeed 0 / failed 1)
drunkensunday said:
Reboot and new port gave me a slightly different Odin log but still failed:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<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> sbl1.mbn
<ID:0/003> aboot.mbn
<ID:0/003>
<ID:0/003>
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
you have all correct files? your sd card is out? if not remove sd card and try. also mac could be a issue idk im a windows guy. but http://forum.xda-developers.com/showthread.php?t=2369125 this thread shows how to unbrick you would need to run Linux virtual though.
kaos420 said:
you have all correct files? your sd card is out? if not remove sd card and try. also mac could be a issue idk im a windows guy. but http://forum.xda-developers.com/showthread.php?t=2369125 this thread shows how to unbrick you would need to run Linux virtual though.
Click to expand...
Click to collapse
I think either trying it from a Windows PC (shouldn't matter, but why not try) or carefully selecting a Sprint store (root friendly tech, knows what he or she is doing) for an over-the-wire update, are worth a shot.
Sent from my SM-N900P using Xparent BlueTapatalk 2
drunkensunday said:
Reboot and new port gave me a slightly different Odin log but still failed:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<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> sbl1.mbn
<ID:0/003> aboot.mbn
<ID:0/003>
<ID:0/003>
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
It is a possibility that you had a bad download and also are you using the odin you from chain fire when you rooted? I had the same problem last month. I spent 5 hours trying to figure it out. Turns out I just had a bad download.
Sent from my SM-N900P using xda app-developers app
Just got back from Sprint Store. They said my warrenty is void and there is nothing they can do. I guess I will redownload and try on a pc. I'll be back.... ugh.
drunkensunday said:
Just got back from Sprint Store. They said my warrenty is void and there is nothing they can do. I guess I will redownload and try on a pc. I'll be back.... ugh.
Click to expand...
Click to collapse
did you have tep? did you tell them what you tried?
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.