In need of help returning to stock . Tried using odin 3 to load i605vramc3 but stopped by fail message in top left of odin screen. on phone downloading screen binary is samsung official but system status is custom. any help is appreciated.
coltblue said:
In need of help returning to stock . Tried using odin 3 to load i605vramc3 but stopped by fail message in top left of odin screen. on phone downloading screen binary is samsung official but system status is custom. any help is appreciated.
Click to expand...
Click to collapse
You need to post the output of Odin or tell us where it failed.. without more information it's kind of hard to tell you what is going on.
If no more information I would just tell to try again
lacoursiere18 said:
You need to post the output of Odin or tell us where it failed.. without more information it's kind of hard to tell you what is going on.
If no more information I would just tell to try again
Click to expand...
Click to collapse
after attempt 4 of odin. fail message on first square. complete ( write) operation failed.<osm> all threads completed.(succeed 0 / failed 1 ).
those are the only readings that is see from odin. not sure aware of more output readings.
coltblue said:
those are the only readings that is see from odin. not sure aware of more output readings.
Click to expand...
Click to collapse
coltblue said:
after attempt 4 of odin. fail message on first square. complete ( write) operation failed.<osm> all threads completed.(succeed 0 / failed 1 ).
Click to expand...
Click to collapse
Are you positive you are in Download Mode? Also make sure you do not have Kies installed. Also might want to try to reinstall Samsung drivers after uninstalling them. After that reboot your computer and let them install
lacoursiere18 said:
Are you positive you are in Download Mode? Also make sure you do not have Kies installed. Also might want to try to reinstall Samsung drivers after uninstalling them. After that reboot your computer and let them install
Click to expand...
Click to collapse
yes it was in downloading mode. tried deleting kies and usb drivers then download of new usb drivers after pc restart. now getting usb device not recognized.
after new usb drivers and trying odin again i received the fail message . cant open the serial (com) port
coltblue said:
after new usb drivers and trying odin again i received the fail message . cant open the serial (com) port
Click to expand...
Click to collapse
Sounds like a usb error. Try another
i got the usb error solved by deleting kies and installing seperate usb drivers. found 2 different .tar files to use in the pda section but cant locate a proper .pit file. the ones that i havve searched for lead to broken or bogus links.
coltblue said:
i got the usb error solved by deleting kies and installing seperate usb drivers. found 2 different .tar files to use in the pda section but cant locate a proper .pit file. the ones that i havve searched for lead to broken or bogus links.
Click to expand...
Click to collapse
Pit....
https://www.dropbox.com/s/ka9a0x6juscjwfc/sch-i605-16gb.pit
Thanks for the link. Still no luck though.Problem originated from a missing su binary from a superuser app that didnt update. tried to flash the original rom to correct the problem but it didnt work out. probably time to just get a new note. thanks for the help.
coltblue said:
Thanks for the link. Still no luck though.Problem originated from a missing su binary from a superuser app that didnt update. tried to flash the original rom to correct the problem but it didnt work out. probably time to just get a new note. thanks for the help.
Click to expand...
Click to collapse
@coltblue,
That pit file lacousier18 linked you should have worked if you are ODIN'ing the correct .tar restore file. You didn't say which Android build you are currently on while trying to restore back to 4.1.2. If you ever installed stock factory builds of 4.3+, then you won't be able to ODIN back to 4.1.2 because your bootloader would have been locked... (you probably know, but any factory stock firmware 4.3 and above permanently locks the bootloader for our Note 2's).
If you were on 4.1.2 bootloader when things got messed up, then you should be able to restore your phone back to 4.1.2 and reroot with CASUAL.
If you were on factory stock 4.3 MJ9 (and just rooted) when things went wrong, you'll have to restore back to MJ9 and root again with saferoot.
There's currently no root method for factory stock 4.4.2.
Either way, you can find Droidstyle's guide at this link:
http://forum.xda-developers.com/showthread.php?p=34891181
He has all the links for files needed to restore your phone back to 4.1.2 or 4.3.
If Droidstyle's guide helps you, please make sure to hit the thanks button for him. He spent a lot of time putting the guide together for us.
Good luck.
mattnmag said:
@coltblue,
That pit file lacousier18 linked you should have worked if you are ODIN'ing the correct .tar restore file. You didn't say which Android build you are currently on while trying to restore back to 4.1.2. If you ever installed stock factory builds of 4.3+, then you won't be able to ODIN back to 4.1.2 because your bootloader would have been locked... (you probably know, but any factory stock firmware 4.3 and above permanently locks the bootloader for our Note 2's).
If you were on 4.1.2 bootloader when things got messed up, then you should be able to restore your phone back to 4.1.2 and reroot with CASUAL.
If you were on factory stock 4.3 MJ9 (and just rooted) when things went wrong, you'll have to restore back to MJ9 and root again with saferoot.
There's currently no root method for factory stock 4.4.2.
Either way, you can find Droidstyle's guide at this link:
http://forum.xda-developers.com/showthread.php?p=34891181
He has all the links for files needed to restore your phone back to 4.1.2 or 4.3.
If Droidstyle's guide helps you, please make sure to hit the thanks button for him. He spent a lot of time putting the guide together for us.
Good luck.
Click to expand...
Click to collapse
i have tried i605vrufnd7 , and KIES_HOME_I605VRAMC3_I605VZWAMC3_1098177_REV04_ , but not the other 2. i coouldnt find a working link for the others. i shall try them and report back thank you.
success ! odin finally accepted stock 4.1.1 but showed a warning triangle saying not official software on the phone screen. ran 4.4.2 through odin and it worked first try. phone restarted , booted up and loaded 4.4.2 . never lost any settings contacts or data! the big thing i did different was using odin on my desktop with a new usb cable and using the usb 3.0 port. Thanks for all the help !
coltblue said:
success !....
Click to expand...
Click to collapse
Glad to hear that you got it restored. It sounds like you were initially running factory 4.4.2 Kit Kat when you had tried to root it to start with.
If you're re on stock 4.4.2 VRUFND7 , then unfortunately - - you can not root the device or unlock the bootloader because there's no rooting method or bootloader unlock method that works right now. You also won't be able to use Odin to downgrade to any of the other Android builds because of lock downs implemented with the 4.4.2 Kit Kat software. The good news is that your phone should run fine on stock 4.4.2 and you can use it again.
Keep your eyes open for new rooting methods.... you never know, someone might figure out how to root it yet.
mattnmag said:
Glad to hear that you got it restored. It sounds like you were initially running factory 4.4.2 Kit Kat when you had tried to root it to start with.
If you're re on stock 4.4.2 VRUFND7 , then unfortunately - - you can not root the device or unlock the bootloader because there's no rooting method or bootloader unlock method that works right now. You also won't be able to use Odin to downgrade to any of the other Android builds because of lock downs implemented with the 4.4.2 Kit Kat software. The good news is that your phone should run fine on stock 4.4.2 and you can use it again.
Keep your eyes open for new rooting methods.... you never know, someone might figure out how to root it yet.
Click to expand...
Click to collapse
stock is ok for now. just didnt like it to be a paperweight. ill watch for new rooting methods in the future too. Thanks.
Thanks!!!
mattnmag said:
@coltblue,
That pit file lacousier18 linked you should have worked if you are ODIN'ing the correct .tar restore file. You didn't say which Android build you are currently on while trying to restore back to 4.1.2. If you ever installed stock factory builds of 4.3+, then you won't be able to ODIN back to 4.1.2 because your bootloader would have been locked... (you probably know, but any factory stock firmware 4.3 and above permanently locks the bootloader for our Note 2's).
If you were on 4.1.2 bootloader when things got messed up, then you should be able to restore your phone back to 4.1.2 and reroot with CASUAL.
If you were on factory stock 4.3 MJ9 (and just rooted) when things went wrong, you'll have to restore back to MJ9 and root again with saferoot.
There's currently no root method for factory stock 4.4.2.
Either way, you can find Droidstyle's guide at this link:
http://forum.xda-developers.com/showthread.php?p=34891181
He has all the links for files needed to restore your phone back to 4.1.2 or 4.3.
If Droidstyle's guide helps you, please make sure to hit the thanks button for him. He spent a lot of time putting the guide together for us.
Good luck.
Click to expand...
Click to collapse
After 3 weeks of my note being dead, got it back thanks to your post and links, my story was different but it work!!! Freaking love this forum!!!
Phsyclone79 said:
After 3 weeks of my note being dead, got it back thanks to your post and links, my story was different but it work!!! Freaking love this forum!!!
Click to expand...
Click to collapse
These guys are really helpful!
Phsyclone79 said:
After 3 weeks of my note being dead, got it back thanks to your post and links, my story was different but it work!!! Freaking love this forum!!!
Click to expand...
Click to collapse
Cool. Glad you got it fixed. :thumbup:
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??
I did the OTA update from M1I to MJ7 and read somewhere that the M1I root method would work. It made my phone unbootable. Obviously the M1I file I have won't work now. I need the MJ7 odin file now or else my phone is a paperweight until then.
Someone else did this 2, you can't use this method because it FLASHES A ROOTED Ml1 Rom....... Odin file still has not been posted yet
Sent From My Hyperdriven S4
ebsk8er06 said:
Someone else did this 2, you can't use this method because it FLASHES A ROOTED Ml1 Rom....... Odin file still has not been posted yet
Sent From My Hyperdriven S4
Click to expand...
Click to collapse
Yeah I thought I read that it would still work. I'll just have to wait for the Odin file
I am in the same boat, my phone is unbootable and I am waiting for the MJ7 odin file or my replacement phone
villainous said:
I am in the same boat, my phone is unbootable and I am waiting for the MJ7 odin file or my replacement phone
Click to expand...
Click to collapse
thankfully i have an iphone i can use for now. surprisingly i went to boot up my phone just now and it went through almost the whole boot process. it's stuck on the verizon splash. last night it would just go straight into odin.
I am not so lucky as to have a backup phone
I should look for a cheap 4g phone to keep in a drawer for such occasions. Hopefully an MJ7 file is made available soon so I can recovery my files before my new phone arrives.
villainous said:
I am not so lucky as to have a backup phone
I should look for a cheap 4g phone to keep in a drawer for such occasions. Hopefully an MJ7 file is made available soon so I can recovery my files before my new phone arrives.
Click to expand...
Click to collapse
I'm sure it will. In a few days. I'm surprised the verizon repair tool doesn't have MJ7.... maybe that'll take a while too.
antisomnic said:
thankfully i have an iphone i can use for now. surprisingly i went to boot up my phone just now and it went through almost the whole boot process. it's stuck on the verizon splash. last night it would just go straight into odin.
Click to expand...
Click to collapse
You might be able to get it into recovery and manually use the update.zip.
It is reported that at least a few people have been able to get out of the state you are in my using a manual update.
tech_head said:
You might be able to get it into recovery and manually use the update.zip.
It is reported that at least a few people have been able to get out of the state you are in my using a manual update.
Click to expand...
Click to collapse
yeah i actually did that and have been using my s4 for a few days
open1your1eyes0 posted [ODIN][TAR] Complete Device Wipe/Repartition and Emergency Recovery for VRUEMJ7 Build in the dev forum.
This is an ODIN factory image similar to the one posted here but this is an emergency recovery image that will help you recover and restore your device from nearly ANY possible soft-brick by entirely wiping, refreshing, and repartitioning your device to out-of-box OEM firmware.
WARNING: Please use this with caution as this will wipe your ENTIRE device with no chance of restoring back old data afterwords!
How to Use
Download file from: http://www.androidfilehost.com/?fid=23203820527944861
Unzip file to your computer (desktop or some location)
Use ODIN v3.09 to flash in AP section once your device is connected
Click to expand...
Click to collapse
And joderme has a VRUEMJ7 no wipe ODIN image available in dev too.
--OctOS Powered VZW GS4 Dev Edition
antisomnic said:
yeah i actually did that and have been using my s4 for a few days
Click to expand...
Click to collapse
So I rooted and updated to MJ7 all went well. Then tried to install twrp not realizing it wont work. Now I'm stuck into download mode and yellow triangle. Is there not a way to odin back to stock since I have this update. Need help.
mickrg123 said:
So I rooted and updated to MJ7 all went well. Then tried to install twrp not realizing it wont work. Now I'm stuck into download mode and yellow triangle. Is there not a way to odin back to stock since I have this update. Need help.
Click to expand...
Click to collapse
Untested, but you can unzip the attached and flash it in ODIN - it's the stock MJ7 recovery. With a bit of luck that'll get you repaired.
If not, flash the no-wipe MJ7 ROM from the Android Development forum, but that'll probably cause you to lose root.
Bait-Fish said:
open1your1eyes0 posted [ODIN][TAR] Complete Device Wipe/Repartition and Emergency Recovery for VRUEMJ7 Build in the dev forum.
And joderme has a VRUEMJ7 no wipe ODIN image available in dev too.
--OctOS Powered VZW GS4 Dev Edition
Click to expand...
Click to collapse
wrong post
Awesome
You know... I don't post much if at all on xda. Mostly im an intel junkie but I have to say after bricking my 24 hour old MJ7 s4 and fully recovering it using this post you guys are ****ing AWESOME!
FYI The exact steps I took were as follows using windows 8.1 pro x64
downloaded Samsung_USB_Driver_for_Mobile_Phones_v1.5.14.0
downloaded Odin3 v3.07
downloaded ALL_I545VRUEMJ7_I545VZWEMJ7_1937946_REV06_user_low_ship_MULTI_CERT.tar.md5
Install Samsung_USB_Driver_for_Mobile_Phones_v1.5.14.0 drivers
Ran odin as administrator, left defaults checked and chose PDA ALL_I545VRUEMJ7_I545VZWEMJ7_1937946_REV06_user_low_ship_MULTI_CERT.tar.md5
(Windows hangs when trying to first browse the file, WAIT)
plugged phone in and got instant com green and hit start. Waited 20 mins and it all went through successfully.
USERS NOTE:
The first computer I tried just absolutely would not flash this phone. Drivers where correct etc it just seemed like it dropped connection. Tried 3 separate usb ports one even off a powered hub and all failed on the system flash. Changed computers and followed the same setup and went first try. If it fails try and try again. Changing different ports, computers, and or drivers helps if you get failure messages.
Thanks to all of you!
SmOoThEm said:
You know... I don't post much if at all on xda. Mostly im an intel junkie but I have to say after bricking my 24 hour old MJ7 s4 and fully recovering it using this post you guys are ****ing AWESOME!
FYI The exact steps I took were as follows using windows 8.1 pro x64
downloaded Samsung_USB_Driver_for_Mobile_Phones_v1.5.14.0
downloaded Odin3 v3.07
downloaded ALL_I545VRUEMJ7_I545VZWEMJ7_1937946_REV06_user_low_ship_MULTI_CERT.tar.md5
Install Samsung_USB_Driver_for_Mobile_Phones_v1.5.14.0 drivers
Ran odin as administrator, left defaults checked and chose PDA ALL_I545VRUEMJ7_I545VZWEMJ7_1937946_REV06_user_low_ship_MULTI_CERT.tar.md5
(Windows hangs when trying to first browse the file, WAIT)
plugged phone in and got instant com green and hit start. Waited 20 mins and it all went through successfully.
USERS NOTE:
The first computer I tried just absolutely would not flash this phone. Drivers where correct etc it just seemed like it dropped connection. Tried 3 separate usb ports one even off a powered hub and all failed on the system flash. Changed computers and followed the same setup and went first try. If it fails try and try again. Changing different ports, computers, and or drivers helps if you get failure messages.
Thanks to all of you!
Click to expand...
Click to collapse
Where can I grab ALL_I545VRUEMJ7_I545VZWEMJ7_1937946_REV06_user_low _ship_MULTI_CERT.tar.md5 ??
emtownsend said:
Where can I grab ALL_I545VRUEMJ7_I545VZWEMJ7_1937946_REV06_user_low _ship_MULTI_CERT.tar.md5 ??
Click to expand...
Click to collapse
http://www.androidfilehost.com/?fid=23203820527944861
Bait-Fish said:
open1your1eyes0 posted [ODIN][TAR] Complete Device Wipe/Repartition and Emergency Recovery for VRUEMJ7 Build in the dev forum.
And joderme has a VRUEMJ7 no wipe ODIN image available in dev too.
--OctOS Powered VZW GS4 Dev Edition
Click to expand...
Click to collapse
antisomnic said:
Yeah I thought I read that it would still work. I'll just have to wait for the Odin file
Click to expand...
Click to collapse
antisomnic said:
I did the OTA update from M1I to MJ7 and read somewhere that the M1I root method would work. It made my phone unbootable. Obviously the M1I file I have won't work now. I need the MJ7 odin file now or else my phone is a paperweight until then.
Click to expand...
Click to collapse
Just an FYI. Whenever you take an OTA from the Carrier it's written so you cannot revert back to an earlier build or a soft and possible hard brick can occur. This has been discussed numerous times in various forums. You were lucky this time.
I had no success with roms (im new to all of this, but i was able to root) and already unrooted.. I just want to clean my phone up for good. I tried installing the 4.3 OTA update and got an error most likely thanks to some safestrap crap still on my phone.
I also tried this..http://forum.xda-developers.com/showthread.php?t=2301259 but the zip file for the MI1 build is corrupt or empty or whatever but it wont work...
So I dont care if i lose data at this point, i just want to go back to stock and be able to get the 4.3 OTA update. Please help!
also, I already have odin v3.07 on my computer.
DITTO!!
Dekdo said:
I had no success with roms (im new to all of this, but i was able to root) and already unrooted.. I just want to clean my phone up for good. I tried installing the 4.3 OTA update and got an error most likely thanks to some safestrap crap still on my phone.
I also tried this..http://forum.xda-developers.com/showthread.php?t=2301259 but the zip file for the MI1 build is corrupt or empty or whatever but it wont work...
So I dont care if i lose data at this point, i just want to go back to stock and be able to get the 4.3 OTA update. Please help!
also, I already have odin v3.07 on my computer.
Click to expand...
Click to collapse
Im WITH YOU ON THIS.. I need to know everything, step by step. This 4.3 update crap is the DEVIL!!!
The method you are using is an issue or the browser you are using to download is creating an issue.
I downloaded the file in that link and did not have an issue.
Dekdo said:
I had no success with roms (im new to all of this, but i was able to root) and already unrooted.. I just want to clean my phone up for good. I tried installing the 4.3 OTA update and got an error most likely thanks to some safestrap crap still on my phone.
I also tried this..http://forum.xda-developers.com/showthread.php?t=2301259 but the zip file for the MI1 build is corrupt or empty or whatever but it wont work...
So I dont care if i lose data at this point, i just want to go back to stock and be able to get the 4.3 OTA update. Please help!
also, I already have odin v3.07 on my computer.
Click to expand...
Click to collapse
If that's not working for you, then you need to retry the download. If it continues to be corrupt, then you need to try a better network.
I've sent people to Panera and Starbucks to fix problems they're having with getting good downloads.
The only other reason for the download from that thread to fail is when you're not on a MI1 build when you start. You can't flash MI1 on anything later.
ok so got the download to work..
started the flash and then it read "FAIL" and my phone was stuck downloading and now its stuck in emergency mode even after pulling the battery. I cant boot to anything else. HELP
Dekdo said:
ok so got the download to work..
started the flash and then it read "FAIL" and my phone was stuck downloading and now its stuck in emergency mode even after pulling the battery. I cant boot to anything else. HELP
Click to expand...
Click to collapse
Have any updates? Were you able to fix the issue? Im kinda in the same situation.
Dekdo said:
ok so got the download to work..
started the flash and then it read "FAIL" and my phone was stuck downloading and now its stuck in emergency mode even after pulling the battery. I cant boot to anything else. HELP
Click to expand...
Click to collapse
You flashed the wrong software for your phone, and must find an image that matches your phone or use the recovery assistant to repair it.
You can't go backwards. I.e. flashing MDK on a ME2 phone.
You can't install custom recovery other than on MDK.
I was originally trying to just go to the new kitkat rom, i believe that was CM11 or something of the sort. But for some reason i cannot do anything with my phone when it comes to installing or changing the recovery. Odin fails every time. One-Click-Root fails every time (which i think is what i used from the beginning to root). I even upgraded ROM manager to pro so i could try the touch based recovery and it will not successfully install a recovery that i can boot into even though it says that it has and shows(ed) the current recovery being the most up-to-date version. And now since ive tried several different today, i have lost root somehow...even thought i just had it and didnt change anything with the root process...just trying to regain even the stock recovery. Basically what happens if i try to boot into recovery mode is it tries for half a second then boots to ODIN mode and in the top left corner it says failed normal boot or something of the sort.
Can someone point me in the right direction? would a factory reset within the android OS help anything? every thing is backed up, so that wont be an issue as far as apps/data and important files goes.
The phone still boots to my "rooted" 4.3 that i have installed, just dont have root privelages any longer...the phone still works as normal...just cant do anything root based...like run titanium backup or supersu, and even ROM manager is NOW giving me an error when trying to install a custom recovery.
I would like to restore to stock MDK so i can start from scratch and install the CM11 KitKat Rom if at all possible...
So you were mdk and loki'd correct...
safestrap powered Hyperdrive 12
decaturbob said:
So you were mdk and loki'd correct...
safestrap powered Hyperdrive 12
Click to expand...
Click to collapse
MDK yes, the loki part im not sure of...but i did try to do that again since having this problem...with no success...
MURD3RD said:
MDK yes, the loki part im not sure of...but i did try to do that again since having this problem...with no success...
Click to expand...
Click to collapse
you would have to to use the loki process to gain root and install the custom recovery at the time. I really can't help as I got into the S4 with ME7 base and been using safestrap.
i also tried following this link
http://forum.xda-developers.com/showthread.php?t=2290798
and it doesnt get past the first ODIN step and gets a fail
attached are some snips of the ODIN screen when it fails
decaturbob said:
you would have to to use the loki process to gain root and install the custom recovery at the time. I really can't help as I got into the S4 with ME7 base and been using safestrap.
Click to expand...
Click to collapse
you got a link to a good working Loki tutorial?
Here's a link to the stock mdk tar file. This will totally wipe your phone. http://www.sxtpdevelopers.com/showthread.php?t=237
Ryno77 said:
Here's a link to the stock mdk tar file. This will totally wipe your phone.
Click to expand...
Click to collapse
i did find that link before and am currently downloading it...but it is taking forever...everything else i download is blazing fast (50Mb D/L speed here at my buddies apartment) but yet this file is only downloading at 50KB/s...and is showing over 9-10 hours for the download to be complete...does anybody have a faster download source?
i know my connection is phenomenal since i downloaded a 9 gig file last night from a different source and it took under an hour...this .tar is less than 2 gigs...shouldnt take that damn long...
i also tried flashing the recovery .tar.md5 from that link...same exact result...
Questions and Help issues go in Q&A and Help section
Thread moved
Thanks
FNSM
kennyglass123 said:
Questions and Help issues go in Q&A and Help section
Thread moved
Thanks
FNSM
Click to expand...
Click to collapse
THANKS!!!
I knew i hadn't put it in the right place...hopefully it'll get more view here...and i can get this thing sorted out
so right now the screen shows (phone)--(yellow triangle)--(computer) and says "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again"
this is after trying to install the stock restore .tar files in the link mentioned above...the device will NO LONGER boot the os and goes to this screen every time. I can still get it into download (Odin) mode though.
MURD3RD said:
i also tried following this link
http://forum.xda-developers.com/showthread.php?t=2290798
and it doesnt get past the first ODIN step and gets a fail
attached are some snips of the ODIN screen when it fails
Click to expand...
Click to collapse
The "fail (auth)" means that you're likely no longer running an MDK bootloader. It's refusing to load the MD2 that's used by Loki.
Do you get the same failure when you try to flash the stock MDK ROM image? What text shows up on your phone when you try to flash the stock?
Since you're stuck at the "Firmware upgrade encountered an issue." it indicates that the bootloader rejected a flash, which means you may have somehow updated to MI1 or later. The message on the phone when the flash fails will tell for sure.
k1mu said:
The "fail (auth)" means that you're likely no longer running an MDK bootloader. It's refusing to load the MD2 that's used by Loki.
Do you get the same failure when you try to flash the stock MDK ROM image? What text shows up on your phone when you try to flash the stock?
Since you're stuck at the "Firmware upgrade encountered an issue." it indicates that the bootloader rejected a flash, which means you may have somehow updated to MI1 or later. The message on the phone when the flash fails will tell for sure.
Click to expand...
Click to collapse
i can't remember what exactly the messages were right now...but currently Kies is trying a recovery "upgrade and initialization"...hopefully this works and my phone can at least be usable again...and THEN ill get back at trying to get the new KitKat, lol
MURD3RD said:
i can't remember what exactly the messages were right now...but currently Kies is trying a recovery "upgrade and initialization"...hopefully this works and my phone can at least be usable again...and THEN ill get back at trying to get the new KitKat, lol
Click to expand...
Click to collapse
You won't be on MDK, so no KitKat.
k1mu said:
You won't be on MDK, so no KitKat.
Click to expand...
Click to collapse
but i have had no problem flashing back to get rooted when i first got the device...even though several threads said it couldnt be done...all i need is to get back to stock and start from scratch...at least i hope this is the case. If it goes ahead and installs the newest 4.3 update...and i truly cant change it due to no exploits yet...then i guess ill have to wait...lol, it could be worse, haha
so kies just finished doing its thing and the phone booted up and is now running 4.3 MK2
MURD3RD said:
so kies just finished doing its thing and the phone booted up and is now running 4.3 MK2
Click to expand...
Click to collapse
That means you lost the mdk bootloader and can only use Safestrap to boot custom rooms :/ you will need to root via saferoot in the development thread first. Then load Safestrap which only has one ROM that currently works (hyper drive 12).
gnubian said:
That means you lost the mdk bootloader and can only use Safestrap to boot custom rooms :/ you will need to root via saferoot in the development thread first. Then load Safestrap which only has one ROM that currently works (hyper drive 12).
Click to expand...
Click to collapse
EDIT: well nevermind...i think i was just crazy to think something different...i am definitely running the latest release of 4.3 from vzw...fml...well at least it can still be rooted. Is there any development for KitKat on the new MK2 software? Ill do some searching around...
i do remember, however, doing something that a tutorial said specifically not to do...and it worked anyway...even though several people responding to the thread said not to do or it would brick the phone...o well i guess...if i find the link ill post it up...
gnubian said:
That means you lost the mdk bootloader and can only use Safestrap to boot custom rooms :/ you will need to root via saferoot in the development thread first. Then load Safestrap which only has one ROM that currently works (hyper drive 12).
Click to expand...
Click to collapse
would you happen to have a link to the safestrap tutorial? i cant seem to locate it...im gunna do some more searching, but if you had a link at the ready, that'd be awesome!!!
EDIT: Found it...no worries
gnubian said:
That means you lost the mdk bootloader and can only use Safestrap to boot custom rooms :/ you will need to root via saferoot in the development thread first. Then load Safestrap which only has one ROM that currently works (hyper drive 12).
Click to expand...
Click to collapse
so i found the thread for this ROM and it doesnt say anything about being able to run on MK2 build...can anyone shed some light on this? it only says MJ7...
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