I tried to put this in the bootloader thread but I do not have enough posts. I am rooted, stock using the Casual root method after flashing the alternate method in the original thread. I had to use the alternate method because I first rooted using the root66 image that left me with a still locked bootloader. I tried to unlock the bootloader but kept getting a FAIL in Odin at the sboot.bin and that locked my phone. The alternate method rebooted the phone because it does not have a sboot.bin.....
I now have a rooted phone that says the baseband is VRALJB, as well as the build that shows VRALJB. I downloaded all of the files in the bootloader thread and started from scratch. When I flashed the "baseline bootloader" along with the "pit" I got another FAIL in oden when it got to the sboot.bin... There is a message in the beginning of the download thread that says not to flash anything that has a sboot.bin with it... In the first steps of the instructions it says to download the baseline file, WHICH has a sboot.bin. I am really confused.... When I go thru the Casual I get the NOOB message at the end. I thought I had to have the VRALJB baseband, Which I have? Whats UP??????? I have read probably 100 pages of the unlock bootloader thread and have tried to uninstall everything and download again. Made sure my drivers are good, etc... I have a rooted phone that works fine, but I would like to unlock the BL so I can flash different roms later as well as install a recovery.... Thanks for any ideas here....GA
Which thread are you following? Can you link it?
Sent from my SCH-I605 using Tapatalk 2
kintwofan said:
Which thread are you following? Can you link it?
Sent from my SCH-I605 using Tapatalk 2
Click to expand...
Click to collapse
Here it is: www.xda-developers.com/.../unlock-the-verizon-samsung-galaxy-note-ii- bootloader-xda-developer-tv/
You probably used the unlock method for VRALJB when your phone came with (or was updated to) VRALL4. There are two unlock methods and the first won't work if your phone has an updated bootloader.
Follow this guide, and it works fine from the newest OTA. http://forum.xda-developers.com/showthread.php?t=2118348
imnuts said:
You probably used the unlock method for VRALJB when your phone came with (or was updated to) VRALL4. There are two unlock methods and the first won't work if your phone has an updated bootloader.
Click to expand...
Click to collapse
That was what I thought he was doing too
Sent from my SCH-I605 using Tapatalk 2
shrike1978 said:
Follow this guide, and it works fine from the newest OTA. http://forum.xda-developers.com/showthread.php?t=2118348
Click to expand...
Click to collapse
Thanks I will try this in the morning... Even though my phone now shows VRALJB in the Baseband Version and the Build number it did in fact have the other number before I had to flash the alternate method to reboot. VRALL4 I think it was... I thought if the baseband was changed I had to use the method for that number.....GA
GaryAlpusa1 said:
Thanks I will try this in the morning... Even though my phone now shows VRALJB in the Baseband Version and the Build number it did in fact have the other number before I had to flash the alternate method to reboot. VRALL4 I think it was... I thought if the baseband was changed I had to use the method for that number.....GA
Click to expand...
Click to collapse
No what matters is your boot loader which is still LL4.
Sent from my SCH-I605 using Tapatalk 2
if im not mistaken adams new method works for both bootloaders correct? if thats the case why not close the old thread to eliminate this issue??
Success
Used the new jailbreak method this morning.. I am pleased to say that it works fine. This after a very frustrating 3 days and having to reflash my phone a couple of times. Thanks to everyone who replied and especially the developers who spend their time helping noobs like me. GA:good:
Just an FYI, the baseband version is the modem/radio and has nothing to do with which version of firmware you are on.
Thanks. That explains why I was having so much trouble. All is well now. G
Sent from my SCH-I605 using xda app-developers app
error using casual
Was hoping someone could help! Im trying to root my Verizon note 2 with casual "no you verizon". Im on build vramc3 and am completely stock. Everytime I try I see error "no partition in indentifier 60". Ive been trying for about a week now. I've tried two different windows 7 pcs and multiple cables. Someone please help!
rwdybuck said:
Was hoping someone could help! Im trying to root my Verizon note 2 with casual "no you verizon". Im on build vramc3 and am completely stock. Everytime I try I see error "no partition in indentifier 60". Ive been trying for about a week now. I've tried two different windows 7 pcs and multiple cables. Someone please help!
Click to expand...
Click to collapse
You really need to start your own thread in the help section for this if you havent already
Sent from my SCH-I605 using XDA Premium HD app
Related
I tried the casual and everything else, i tried 4 computers, 25+ usb ports and 5 different usb cables, I cant post in the dev forum cuz im new.
I bought a Note 2 it had 4.1.2 on it, i used odin and and root66 file and im bnot on 4.1.1 with baseband I605VRAJLB but casual always fails after it downloads the pit and tries to install it.
HELP anyone, i need to use this phone on tmobile.
What method ate toy using and are you getting any error messages?
Sent from my SGH-T889 using xda app-developers app
PeteKT said:
I tried the casual and everything else, i tried 4 computers, 25+ usb ports and 5 different usb cables, I cant post in the dev forum cuz im new.
I bought a Note 2 it had 4.1.2 on it, i used odin and and root66 file and im bnot on 4.1.1 with baseband I605VRAJLB but casual always fails after it downloads the pit and tries to install it.
HELP anyone, i need to use this phone on tmobile.
Click to expand...
Click to collapse
I might be wrong but to my understanding, if you have OTA 4.1.2, it won't unlock the bootloader. Because I tried doing it on a 4.1.2 after it recieved the OTA, and it wouldn't root/unlock. After going through every step, I got stuck on the samsung boot loop. So i took out a different device and it had 4.1.1 on it. Did the exact same thing and boom..
wythyntime said:
I might be wrong but to my understanding, if you have OTA 4.1.2, it won't unlock the bootloader. Because I tried doing it on a 4.1.2 after it recieved the OTA, and it wouldn't root/unlock. After going through every step, I got stuck on the samsung boot loop. So i took out a different device and it had 4.1.1 on it. Did the exact same thing and boom..
Click to expand...
Click to collapse
http://www.xda-developers.com/andro...otloader-unlock-achieved-casual-tool-updated/
SchefMarcus said:
http://www.xda-developers.com/andro...otloader-unlock-achieved-casual-tool-updated/
Click to expand...
Click to collapse
it does not work for the latest VRAMC3 firmware. adam and crew are currently working on a fix.
wythyntime said:
I might be wrong but to my understanding, if you have OTA 4.1.2, it won't unlock the bootloader. Because I tried doing it on a 4.1.2 after it recieved the OTA, and it wouldn't root/unlock. After going through every step, I got stuck on the samsung boot loop. So i took out a different device and it had 4.1.1 on it. Did the exact same thing and boom..
Click to expand...
Click to collapse
droidstyle said:
it does not work for the latest VRAMC3 firmware. adam and crew are currently working on a fix.
Click to expand...
Click to collapse
i used that method for 4.1.2 and it worked fine for me.
using the CASUAL jailbreak method and i get the error after it downloads the pit file and tries to write it, I can post the exact message but ill have to brick the phone again.
The error i get is
Downloading device's PIT file...
PIT file downloaded successful.
uploading recovery 100%
ERROR: Failed to confirm end of file transfer sequence!
ERROR: recovery upload failed!
the phone gets the loop mode and loops the samsung text, i have to flash the original .pit file top get the phone to boot up now.
____
is there anyway for me to get back to 4.1.2 without an active verizon sim?
What are you on right now? When I tried to flash 4.1.2 and it didn't work, I flashed the pit file and got the phone running at 4.1.2. all without a simcard in the slot.
there was a new CASUAL that was uploaded last night and it worked for me but the thread has been closed now since they are having problems with it. I did get an error the first time i tried it but the second time it was able to root, unlock and add twrp to my phone.
Wheer did you get the new casual from all i see is 465b version
PeteKT said:
Wheer did you get the new casual from all i see is 465b version
Click to expand...
Click to collapse
There is a link in the casual thread to the new one but it is now locked. I tried it last night when it was still open. The version was 478B, not sure if you can still download it or not.
Downloaded and it worked, it unlocked my phone i can use my tmobile sim but i cant change the APN settings, any help??
Noob here, thanks in advance for any help. I have a rooted vzw note 2 through Odin root66, I've tried unsuccessfully to flash a new rom, always get the dreaded yellow triangle from big brother. I need to unlock the bootloader but am still a bit timid in exploiting things. I've tried flashing with clockwork mod and goo, with the same result, and manage to return to root using Odin root66 etc... I wonder if I can use casual since I'm already rooted? I'm on stock Os 4.1.1, so close and yet so far away from flashing... any help appreciated, thanks
avatarzan said:
Noob here, thanks in advance for any help. I have a rooted vzw note 2 through Odin root66, I've tried unsuccessfully to flash a new rom, always get the dreaded yellow triangle from big brother. I need to unlock the bootloader but am still a bit timid in exploiting things. I've tried flashing with clockwork mod and goo, with the same result, and manage to return to root using Odin root66 etc... I wonder if I can use casual since I'm already rooted? I'm on stock Os 4.1.1, so close and yet so far away from flashing... any help appreciated, thanks
Click to expand...
Click to collapse
You have to use Causal if you want to flash a rom. Rooting just gives you root access, to flash a rom your bootloader has to be unlocked and you have to have a custom recovery installed. Thats what Casual does, it unlocks your bootloader and installs you first custom recovery for you. Once that is done you will be able to flash roms, not before.
How did you miss that? Its written in all the guides.
Sent from my SCH-I605 using XDA Premium HD app
missed it
shangrila500 said:
You have to use Causal if you want to flash a rom. Rooting just gives you root access, to flash a rom your bootloader has to be unlocked and you have to have a custom recovery installed. Thats what Casual does, it unlocks your bootloader and installs you first custom recovery for you. Once that is done you will be able to flash roms, not before.
How did you miss that? Its written in all the guides.
Sent from my SCH-I605 using XDA Premium HD app
Click to expand...
Click to collapse
I rooted before I ever found this forum...so I missed it....until now. My question is can I use Casual now that I'm rooted? I don't want to brick....I'm running stock rom and rooted and what I've read doesn't address my situation...or I totally missed it if it does...
Mahalo for your reply
avatarzan said:
I rooted before I ever found this forum...so I missed it....until now. My question is can I use Casual now that I'm rooted? I don't want to brick....I'm running stock rom and rooted and what I've read doesn't address my situation...or I totally missed it if it does...
Mahalo for your reply
Click to expand...
Click to collapse
I wish you could. I didn't see the Casual One Click until 5 minutes after I rooted. When you try casual, it will check your bootloader and give you a long message saying a lot of things that basically call you dumb for not reading. I'm currently trying to return to stock but I can't extract an .xz file to get it back to stock because it fails at sboot.bin. Sorry man
Yogurt HBI said:
I wish you could. I didn't see the Casual One Click until 5 minutes after I rooted. When you try casual, it will check your bootloader and give you a long message saying a lot of things that basically call you dumb for not reading. I'm currently trying to return to stock but I can't extract an .xz file to get it back to stock because it fails at sboot.bin. Sorry man
Click to expand...
Click to collapse
It sounds like I am in that boat. There has to be some sort of fix for this right? It has been a long week for me this time rooting, wow.
Yogurt HBI said:
I wish you could. I didn't see the Casual One Click until 5 minutes after I rooted. When you try casual, it will check your bootloader and give you a long message saying a lot of things that basically call you dumb for not reading. I'm currently trying to return to stock but I can't extract an .xz file to get it back to stock because it fails at sboot.bin. Sorry man
Click to expand...
Click to collapse
If it fails at sboot.bin use the alternative recovery ROM in droidstyles guide and flash it in Odin.
As far as I knew you can use CASUAL to unlock, you just have to use the newest version.
Sent from my SCH-I605 using XDA Premium HD app
Same problem
I brought this VZW Note 2 off of craigslist and it was already rooted. I was wanting to flash jelly beans v19 and tried to install TWRP but CWM was already installed and I really forgot what I did its been 10 hours already following guides and the only thing that works is odin, pit and root66 but anything else I try after getting the phone back up fails and root66 would not pass the last several times but this last time it did. I suspect the bootloader is locked but I'm rooted. I want to clear everything and install a fresh rom since I don't know the history and the phone was freezing and glitchy but I did not check see what rom the previous owner had installed and by the way Im a total newb but really have been seaching threads to solve this before posting but with no luck. Any help much appreciated
jmc71 said:
I brought this VZW Note 2 off of craigslist and it was already rooted. I was wanting to flash jelly beans v19 and tried to install TWRP but CWM was already installed and I really forgot what I did its been 10 hours already following guides and the only thing that works is odin, pit and root66 but anything else I try after getting the phone back up fails and root66 would not pass the last several times but this last time it did. I suspect the bootloader is locked but I'm rooted. I want to clear everything and install a fresh rom since I don't know the history and the phone was freezing and glitchy but I did not check see what rom the previous owner had installed and by the way Im a total newb but really have been seaching threads to solve this before posting but with no luck. Any help much appreciated
Click to expand...
Click to collapse
Flash Root66 or the alternative restore with the NAND erase box in Odin checked. If it won't flash just the ROM in Odin try flashing the ROM + the PIT by following the instructions in droidstyles guide in Android Development.
You would do better to make your own thread too.
Sent from my SCH-I605 using XDA Premium HD app
official Rom should be rolling out as we speak!
bigmixxx said:
official Rom should be rolling out as we speak!
Click to expand...
Click to collapse
hmm dont see the zip or an article yet on sammobile
monkeyass408 said:
hmm dont see the zip or an article yet on sammobile
Click to expand...
Click to collapse
Hit Sammobile and search firmware. Then type i605...And boom....
Yea its there
Sent from my SCH-I605 using xda app-developers app
I downloaded the file last night. However, please don't odin it, it will lock your bootloader.
I'm not worried about the bootloader as all I need the 4.3 for is gear support...do you load the zip in the bootloader spot, the pda spot, or phone spot in odin?
Sent from my SCH-I605 using xda app-developers app
_jfo_ said:
I'm not worried about the bootloader as all I need the 4.3 for is gear support...do you load the zip in the bootloader spot, the pda spot, or phone spot in odin?
Sent from my SCH-I605 using xda app-developers app
Click to expand...
Click to collapse
Just to warn you. If this locks your bootloader, its probably locked forever a la the S4 and N3. If you previously used a custom recovery, you will no longer have this option, likely ever again with this phone. In addition, getting Hashcode to develop SS for this phone is unlikely in my opinion because we've been unlocked for so long and the phone is over a year old. Many times users take root and unlocked bootloaders for granted, thinking that if they take the OTA, someone will figure out how to reunlock or reroot the phone, the former is HIGHLY unlikely. If you can wait a day, someone will likely post an unmodified flashable zip of the newest OTA that won't jeopardize your unlocked bootloader. If you truly don't care about losing this option for good, then by all means go ahead and odin the OTA, the PDA slot should do it.
So this is what I am pondering. I'm running cleanrom which is no longer supported; should I stick with 4.2 forever or take the 4.3 build from verizon ?
mlin said:
Just to warn you. If this locks your bootloader, its probably locked forever a la the S4 and N3. If you previously used a custom recovery, you will no longer have this option, likely ever again with this phone. In addition, getting Hashcode to develop SS for this phone is unlikely in my opinion because we've been unlocked for so long and the phone is over a year old. Many times users take root and unlocked bootloaders for granted, thinking that if they take the OTA, someone will figure out how to reunlock or reroot the phone, the former is HIGHLY unlikely. If you can wait a day, someone will likely post an unmodified flashable zip of the newest OTA that won't jeopardize your unlocked bootloader. If you truly don't care about losing this option for good, then by all means go ahead and odin the OTA, the PDA slot should do it.
Click to expand...
Click to collapse
mlin said:
Just to warn you. If this locks your bootloader, its probably locked forever a la the S4 and N3. If you previously used a custom recovery, you will no longer have this option, likely ever again with this phone. In addition, getting Hashcode to develop SS for this phone is unlikely in my opinion because we've been unlocked for so long and the phone is over a year old. Many times users take root and unlocked bootloaders for granted, thinking that if they take the OTA, someone will figure out how to reunlock or reroot the phone, the former is HIGHLY unlikely. If you can wait a day, someone will likely post an unmodified flashable zip of the newest OTA that won't jeopardize your unlocked bootloader. If you truly don't care about losing this option for good, then by all means go ahead and odin the OTA, the PDA slot should do it.
Click to expand...
Click to collapse
Well....I flashed it and now my phone is stuck in an endless bootloop. It flashes to the "Galaxy Note II" screen for about one second, then reboots and does the same thing over and over...I can still put it into download mode, but cannot boot it into recovery...ODIN says it cant open the Serial (COM) port to my phone....ugh
jake21 said:
So this is what I am pondering. I'm running cleanrom which is no longer supported; should I stick with 4.2 forever or take the 4.3 build from verizon ?
Click to expand...
Click to collapse
There are more than just those two options. You can stay on clean ROM til a rooted, stable OTA flashable is posted. Beans is working on that now I believe. That way you'll have the same experience that the OTA gives, but you'll retain the option to root or even flash a different ROM should you desire. Beans will also be updating his custom ROM build to my knowledge based on this new OTA.
How do I track this? I mean is there a thread that Bean post to that will indicate wehn this is ready ?
mlin said:
There are more than just those two options. You can stay on clean ROM til a rooted, stable OTA flashable is posted. Beans is working on that now I believe. That way you'll have the same experience that the OTA gives, but you'll retain the option to root or even flash a different ROM should you desire. Beans will also be updating his custom ROM build to my knowledge based on this new OTA.
Click to expand...
Click to collapse
jake21 said:
How do I track this? I mean is there a thread that Bean post to that will indicate wehn this is ready ?
Click to expand...
Click to collapse
Check here: http://forum.xda-developers.com/showpost.php?p=48286377&postcount=1
_jfo_ said:
Well....I flashed it and now my phone is stuck in an endless bootloop. It flashes to the "Galaxy Note II" screen for about one second, then reboots and does the same thing over and over...I can still put it into download mode, but cannot boot it into recovery...ODIN says it cant open the Serial (COM) port to my phone....ugh
Click to expand...
Click to collapse
any tips or is my phone probably bricked?
_jfo_ said:
any tips or is my phone probably bricked?
Click to expand...
Click to collapse
If you can get to download mode it's not bricked. Try doing a factory reset in stock recovery or figure out why your drivers aren't recognizing the device.
akellar said:
If you can get to download mode it's not bricked. Try doing a factory reset in stock recovery or figure out why your drivers aren't recognizing the device.
Click to expand...
Click to collapse
I cant get to stock recovery, unfortunately. The device IS being recognized (its showing up in the [ID:COM] spot) but for some reason after flashing Odin seems to have stopped talking to the device...
This is the message I get in ODIN when connecting the device
"<ID:0/004> Added!!"
As the release of 4.3 is now unleashed into the world. Going to retitle the original post title to make this the general discussion thread.
Enjoy 4.3
_jfo_ said:
I cant get to stock recovery, unfortunately. The device IS being recognized (its showing up in the [ID:COM] spot) but for some reason after flashing Odin seems to have stopped talking to the device...
This is the message I get in ODIN when connecting the device
"<ID:0/004> Added!!"
Click to expand...
Click to collapse
That should mean its ready to flash. But you tried already, right? What exactly happened? Did Odin finish successfully or was there an error?
Finally got my 4.3 update around 1pm today! I've been waiting for the update solely for the Galaxy Gear full functionality. Nice Christmas gift :good:
_jfo_ said:
I cant get to stock recovery, unfortunately. The device IS being recognized (its showing up in the [ID:COM] spot) but for some reason after flashing Odin seems to have stopped talking to the device...
This is the message I get in ODIN when connecting the device
" Added!!"
Click to expand...
Click to collapse
You need to flash the PIT file in Odin. The same thing happened to me.
Sent from my SCH-I605 using XDA Premium 4 mobile app
Hey wont framaroot grant me root access i didnt delete it or my other mods i put to sleep without deleteing i hate odin and wont mess with it but i hate the green battery logo and pull down green icons i want um back blue any thoughts
sent from my bone stock note 2
So I tried to root my Note 2 today. I had rooted it once before using Casual this past summer, but due to circumstances i had to get a new one.The replacement came in today, and i tried to root it with the same methods. I believe my mistake was using Casual while i had 4.3 installed on my device. I'm not TERRIBLY android savvy, but i knew enough to know that if i ****ed up i should stop while i'm ahead and ask you guys.
tl;dr
Long story short, while using Casual to root my Note 2 with 4.3 on it, i got this message
ERROR: Failed to confirm end of file transfer sequence!ERROR: recovery upload failed!ERROR: Failed to send end session packet!waiting for device
waited for a good 30 minutes, nothing was changing, turned off phone and now it's bricked, looping at the "Samsung Galaxy Note 2" Splash screen.
I believe i have to use Odin for something but i could really use some help and reassurance before i continue.
Needless to say i will be jamming f5 on my thread until everything is resolved!
Thanks in advance!
mzaric said:
So I tried to root my Note 2 today. I had rooted it once before using Casual this past summer, but due to circumstances i had to get a new one.The replacement came in today, and i tried to root it with the same methods. I believe my mistake was using Casual while i had 4.3 installed on my device. I'm not TERRIBLY android savvy, but i knew enough to know that if i ****ed up i should stop while i'm ahead and ask you guys.
tl;dr
Long story short, while using Casual to root my Note 2 with 4.3 on it, i got this message
ERROR: Failed to confirm end of file transfer sequence!ERROR: recovery upload failed!ERROR: Failed to send end session packet!waiting for device
waited for a good 30 minutes, nothing was changing, turned off phone and now it's bricked, looping at the "Samsung Galaxy Note 2" Splash screen.
I believe i have to use Odin for something but i could really use some help and reassurance before i continue.
Needless to say i will be jamming f5 on my thread until everything is resolved!
Thanks in advance!
Click to expand...
Click to collapse
UPDATE: Since i posted this, i tried to flash a stock firmware on Odin (4.1.2 i believe) and it failed halfway through the procedure. with nothing more to be done, i reset my phone, and where before it was just bootlooping, it now shows me an entirely different screen reading "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
Since then i have tried a different firmware file, still 4.1.2, Odin get's to the very end of the procedure, and crashes at what i assume is the reboot portion. Desperately need assistance!
You can't flash anything other than 4.3 if you have the 4.3 bootloader.
akellar said:
You can't flash anything other than 4.3 if you have the 4.3 bootloader.
Click to expand...
Click to collapse
OH. That makes a lot of sense....
I will try to flash a 4.3 firmware right now. Will i need some sort of .pit file or something to fix the initial bootloop? Or is that problem just totally blown out of the water at this point?
mzaric said:
OH. That makes a lot of sense....
I will try to flash a 4.3 firmware right now. Will i need some sort of .pit file or something to fix the initial bootloop? Or is that problem just totally blown out of the water at this point?
Click to expand...
Click to collapse
I cant seem to find the file anywhere. Only on terafile via SamMobile, but the download link doesn't seem to work.
What are my options as far as this bootloader go?
Did you look in the general section at the unbricker thread?
Sent from my MB886 using xda app-developers app
palmbeach05 said:
Did you look in the general section at the unbricker thread?
Sent from my MB886 using xda app-developers app
Click to expand...
Click to collapse
I did a bunch of searches on the site as i was f****ing my phone up, systematically. Im really sorry if this thread doesn't go here, i just didn't know who else to ask
YES!
Found the proper 4.3 file, flashed it via Odin. Everything is stock and ready. If anybody wishes to help me root it from here or point me in the right direction that'd be great but other than that, thanks for letting me post here and thanks to those who helped me out!
mzaric said:
YES!
Found the proper 4.3 file, flashed it via Odin. Everything is stock and ready. If anybody wishes to help me root it from here or point me in the right direction that'd be great but other than that, thanks for letting me post here and thanks to those who helped me out!
Click to expand...
Click to collapse
Currently the only way to root your OTA 4.3 Note 2 is to use saferoot, read this thread carefully
http://forum.xda-developers.com/showpost.php?p=48392009&postcount=1
Sent from my SCH-I605 using Tapatalk
I found myself in the same situation. Where might I find the PIT file? I can't reboot the phone to get the PIT file because it's soft bricked like mzaric's phone was. I'm using Mac OS X so I'm having to use JOdin3 to flash the stock 4.3 firmware back, but without the PIT file I can't continue and I've searched endlessly to find the PIT file. Also a somewhat related question, I heard JOdin isn't good for flashing big files, but I have no alternative, is the stock firmware which is 1.1gb too big to flash?
EDIT: I sadly didn't search hard enough thank you droidstyle for the guide. But my next question is I'm unsure of what version the phone is because when I originally tried to do the CASUAL unlock I believe it was on 4.1.2, but I think it softbricked to begin with because it was 4.3. Should I just try doing the 4.1.2 and if it doesn't take, retry with the 4.3?
If you flashed n7100 firmware you are screwed. If not just Odin back to stock. You were on 4.1.2 if you were unlocked using casual. Don't go to 4.3
Sent from my SCH-I605 using Tapatalk
I was flashing a rom onto my galaxy s4 and I've noticed that it couldn't receive OTA updates before but I never updated so it didn't affect me much until today when I tried flashing a rom and the code turned red and it says SW REV. Check FAIL: fused:5. Binary: 3, I also tried using odin downloader to flash VRAUME7 back onto it but said it encountered a error in line 27. After I tried using Kies downloader to update the software but it says firmware upgrade encountered an issue please select recovery mode in Kies but when I used recovery mode in keis it says it encountered a problem while updating, I'm out of ideas could someone please help
af_nm said:
I was flashing a rom onto my galaxy s4 and I've noticed that it couldn't receive OTA updates before but I never updated so it didn't affect me much until today when I tried flashing a rom and the code turned red and it says SW REV. Check FAIL: fused:5. Binary: 3, I also tried using odin downloader to flash VRAUME7 back onto it but said it encountered a error in line 27. After I tried using Kies downloader to update the software but it says firmware upgrade encountered an issue please select recovery mode in Kies but when I used recovery mode in keis it says it encountered a problem while updating, I'm out of ideas could someone please help
Click to expand...
Click to collapse
Fused 5 means you need to flash either mj7 or mk2 .
I'd do the full wipe at this point. If one doesn't work right at first... Try the other. Do you recall which your phone was on prior to this?
Sent From My Verizon S4
af_nm said:
I was flashing a rom onto my galaxy s4 and I've noticed that it couldn't receive OTA updates before but I never updated so it didn't affect me much until today when I tried flashing a rom and the code turned red and it says SW REV. Check FAIL: fused:5. Binary: 3, I also tried using odin downloader to flash VRAUME7 back onto it but said it encountered a error in line 27. After I tried using Kies downloader to update the software but it says firmware upgrade encountered an issue please select recovery mode in Kies but when I used recovery mode in keis it says it encountered a problem while updating, I'm out of ideas could someone please help
Click to expand...
Click to collapse
so what is your base build number?
what rom were you trying to flash
are you loki'd or safestrap?
decaturbob said:
so what is your base build number?
what rom were you trying to flash
are you loki'd or safestrap?
Click to expand...
Click to collapse
Yea I don't know either.. I just saw that Odin error then I saw me7. Figured op tried flashing the wrong one. It is a bit confusing though with no actual info to go on.
Sent From My Verizon S4
decaturbob said:
so what is your base build number?
what rom were you trying to flash
are you loki'd or safestrap?
Click to expand...
Click to collapse
Verizon SCH-I545
a rom called premium but I didn't even get to download it before the red code started
and lastly I rooted using loki'd, sorry for the lack of info
af_nm said:
Verizon SCH-I545
a rom called premium but I didn't even get to download it before the red code started
and lastly I rooted using loki'd, sorry for the lack of info
Click to expand...
Click to collapse
OK well if you can get back into download mode then flash the MDK tar . I'm not really sure if you were flashing a rom in Odin or a custom recovery but in any case if all else fails.... Odin mdk
Sent From My Verizon S4
With the new knox security trying to flash a prior firmware will trip the flag so it's advised to be careful when flashing images via Odin. Flash an earlier version that doesn't take and you'll lose the warranty on your phone.
Hit thanks if I helped you out. Doing a little bit of reading goes a long way. Sent via tapatalk.
would reinstalling the pit files work?
odin mdk
Mistertac said:
OK well if you can get back into download mode then flash the MDK tar . I'm not really sure if you were flashing a rom in Odin or a custom recovery but in any case if all else fails.... Odin mdk
Sent From My Verizon S4
Click to expand...
Click to collapse
I ended up trying to flash using odin mdk and even that refused to work is there anything else I can try
af_nm said:
I ended up trying to flash using odin mdk and even that refused to work is there anything else I can try
Click to expand...
Click to collapse
I have to admit, I am really confused by your posts. I have no idea what you were, or are, trying to do. Are you SURE you were on MDK? If you weren't on MDK, you need to Odin back to the build you were on.
Sent from my NCC-1701 using Tapatalk 4
riker147 said:
I have to admit, I am really confused by your posts. I have no idea what you were, or are, trying to do. Are you SURE you were on MDK? If you weren't on MDK, you need to Odin back to the build you were on.
Sent from my NCC-1701 using Tapatalk 4
Click to expand...
Click to collapse
same here, I'm not sure what he has or what he has done........
decaturbob said:
same here, I'm not sure what he has or what he has done........
Click to expand...
Click to collapse
I know it... It we can know exactly where you were before. Like did you have this s4 since new when they shipped with mdk? Did u root it yourself then Loki? Install cwm or twrp? Things are kinda confusing. Just figured you were on mdk but I've seen stranger posts on here when in the end the op actually didn't have mdk or wasn't even on e Verizon s4.
Sent From My Verizon S4
Mistertac said:
I know it... It we can know exactly where you were before. Like did you have this s4 since new when they shipped with mdk? Did u root it yourself then Loki? Install cwm or twrp? Things are kinda confusing. Just figured you were on mdk but I've seen stranger posts on here when in the end the op actually didn't have mdk or wasn't even on e Verizon s4.
Sent From My Verizon S4
Click to expand...
Click to collapse
The OP says that it said "Fused:5" means he is on MJ7 or MK2. It may have been on MDK and Loki'd at one point, but it's now MJ7/MK2 and needs to be recovered using one of those ROM images - NOT MDK.
k1mu said:
The OP says that it said "Fused:5" means he is on MJ7 or MK2. It may have been on MDK and Loki'd at one point, but it's now MJ7/MK2 and needs to be recovered using one of those ROM images - NOT MDK.
Click to expand...
Click to collapse
Yea good call I think I was actually confusing posts when I was responding earlier. Forgot about the fused 5. Thanks .
Sent From My Verizon S4
riker147 said:
I have to admit, I am really confused by your posts. I have no idea what you were, or are, trying to do. Are you SURE you were on MDK? If you weren't on MDK, you need to Odin back to the build you were on.
Sent from my NCC-1701 using Tapatalk 4
Click to expand...
Click to collapse
No it was shipped with vruame7 and I was never able to update after I rooted so it's always been on vraume7 I used loki'd when I rooted. Ive tried using mj7 and mk2 and used this http://forum.xda-developers.com/showthread.php?t=2507253. when I ran it in odin it ran until it stopped at system.img.ext4 followed by complete(Write) operation failed and on the top left of my phone it says START [224,1440] and BAR [240,1440]
af_nm said:
No it was shipped with vruame7 and I was never able to update after I rooted so it's always been on vraume7 I used loki'd when I rooted. Ive tried using mj7 and mk2 as well but I can't find one that will work
Click to expand...
Click to collapse
If it came with VRUAME7 then you didnt use the Loki method to root. If you want help you should post more logs/info. Like your last sentence "Ive tried using mj7 and mk2 as well but I can't find one that will work" can you elaborate on that? Saying you cant find one that works suggests you've found ones that dont work. But what does "don't work" consist of? It could be "write error", md5 mismatch, "PIT partition not found", "SW Rev check fail..", wrong file etc.
Check that the Odin tar file name says "VRUEMJ7" or "VRUEMK2" in it and ends in tar.md5 and make sure the md5 matches. If that fails then post back with logs/info that will actually assist us in helping you troubleshoot
Sent from my SCH-I545 using XDA Premium 4 mobile app
Surge1223 said:
If it came with VRUAME7 then you didnt use the Loki method to root. If you want help you should post more logs/info. Like your last sentence "Ive tried using mj7 and mk2 as well but I can't find one that will work" can you elaborate on that? Saying you cant find one that works suggests you've found ones that dont work. But what does "don't work" consist of? It could be "write error", md5 mismatch, "PIT partition not found", "SW Rev check fail..", wrong file etc.
Check that the Odin tar file name says "VRUEMJ7" or "VRUEMK2" in it and ends in tar.md5 and make sure the md5 matches. If that fails then post back with logs/info that will actually assist us in helping you troubleshoot
Sent from my SCH-I545 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
No I converted my SD card to EXFAT and downloaded the root onto the rom so I was mistaken I didn't use loki sorry. I just ran this factory image which is for mj7 http://forum.xda-developers.com/showthread.php?t=2507253. I confirmed it was for mj7 after the MD5 file downloaded and ran it using odin, it went fine until it got to system.img.ext4 followed by complete(Write) operation failed and on the top left of my phone it says START [224,1440] and BAR [240,1440] in red and the flash failed. I hope this is more helpful
af_nm said:
No I converted my SD card to EXFAT and downloaded the root onto the rom so I was mistaken I didn't use loki sorry. I just ran this factory image which is for mj7 http://forum.xda-developers.com/showthread.php?t=2507253. I confirmed it was for mj7 after the MD5 file downloaded and ran it using odin, it went fine until it got to system.img.ext4 followed by complete(Write) operation failed and on the top left of my phone it says START [224,1440] and BAR [240,1440] in red and the flash failed. I hope this is more helpful
Click to expand...
Click to collapse
Yes thats much better, gives a lot more info that we can use to help Follow the directions I give here and download and use the pit file I uploaded in this thread, you can find it towards the bottom under the "Full-wipe" directions. Post back and let us know if it worked or if you need more help. Hope this helps.
Surge1223 said:
Yes thats much better, gives a lot more info that we can use to help Follow the directions I give here and download and use the pit file I uploaded in this thread, you can find it towards the bottom under the "Full-wipe" directions. Post back and let us know if it worked or if you need more help. Hope this helps.
Click to expand...
Click to collapse
So I followed the directions to flash the system.img.ext4 file and I already extracted it and am uploading it using heimdall. I have the pit file ready and I put the system.img.ext4 in under SYSTEM, added then removed it but it won't let me flash once it's removed and if I do flash with it on there it says ERROR: Failed to access device. libusb error: -12. I have deleted kies and reinstalled Samsung drivers, any ideas
af_nm said:
So I followed the directions to flash the system.img.ext4 file and I already extracted it and am uploading it using heimdall. I have the pit file ready and I put the system.img.ext4 in under SYSTEM, added then removed it but it won't let me flash once it's removed and if I do flash with it on there it says ERROR: Failed to access device. libusb error: -12. I have deleted kies and reinstalled Samsung drivers, any ideas
Click to expand...
Click to collapse
Driver issue 99% of the time make sure you've uninstalled all Samsung drivers. Use windows' control panel option to uninstall programs and make sure all kies, samsung, and verizon related stuff is uninstalled. Then reboot the pc, let your phone install the drivers for your pc, and try using a different usb port with the stock oem cable. Also make sure adb isn't running in the background
Sent from my SCH-I545 using XDA Premium 4 mobile app