UPDATE: new version available here http://forum.xda-developers.com/showthread.php?t=2272066.
FIRST!!! First jailbreak under the new 2012 DMCA Excemption that is. First "Android Jailbreak" ever... Gah that name erks me... Anyway, You’re here to legally Jailbreak your Verizon Galaxy Note 2.
Introduction
CASUAL will guide you through the process. Put your device into “Developer Mode>USB Debugging”. Click the do it button. This is not only the first release of this new Exploit, but it’s also a beta-test of CASUAL. I expect problems... however this will be addressed with updates. See the About CASUAL section below.
We decided to start a new thread becasue the old unlock method is tried and true on Windows with VRALJB. This method is based on a totally new exploit.
Overview
You are expected to be STOCK.... Stock anything, but stock. This will install a stock kernel and that may affect non-stock roms. You will need to download and execute the CASUAL application below. Then click the Do It! button. You need Java. Do you have Java?.
Windows 32/64 Users: CASUAL will put your device into Download Mode. It will automatically flash everything. If drivers are required, jrloper's CADI (CASUAL Automated Driver installer) will handle it. If Microsoft VC Redistributable is required, click next, next, next. Make sure you're connected to the internet.
Linux 32/64/raspberry pi Users There may be a permission escalation in order to install heimdall, either way sit back and relax. CASUAL automates the entire process.
Please run the following in a terminal first:
Mac Users: Mac works easierr than any other system at the time of this release on 32bit systems. Please report problems.
Download
CASUAL(R465b) Back Atcha Verizon CASUAL is used to automate the process. The exploit was developed by Elite Recognized Developer Ralekdev and packaged by AdamOutler. To run CASUAL you need Java. Do you have Java?
Jailbreak video for Windows users only!
This video desmonstrates CASUAL used with Odin to flash the Galaxy Note 2 firmware Thanks to DroidModderX.
Jailbreak video for LINUX only!
This video demonstrates the one-click CASUAL Linux Unlock method... at 2AM.. so don't expect me to be cheerful.
About CASUAL
CASUAL stands for Cross-platform ADB Scripting, Univeral Android Loader. CASUAL jar files are a wrapper for the CASUAL scripting language. CASUAL allows rapid and accurate deployment of hacks and exploits. At any time, if a serious problem is detected with any script, the kill-switch will be flipped and you will be brought to a support page (most likely here) so you can download the latest version. Otherwise for minor corrections, new CASUAL scripts can be deployed remotely.
Updates
CASUAL provides updates WAAAAY quicker than Verizon. As soon as I push an update to the Subversion repo it appears automatically in EVERY casual. See below for the change log.
25JAN13: Initial release.
25JAN13: put your device into download mode automatically on Windows. Windows users, let me know if this is annoying. -auto CASUAL update
26JAN13: Instruct Windows users to install the proper bootloader -- auto CASUAL update
26JAN13: more concise directions --auto CASUAL update
7MAR13: Initiated beta test of one-click operation on all platforms!
17MAR13: Cross-platform Heimdall is now in effect with CASUAL R311b
20MAR13: Removed mac blocker from script --auto CASUAL update.
6APR13: kill-switch activated as most of repository has been restructured and drivers/dependencies will not be deployed. This will be resolved soon with a new version.
7APR13: New version includes better driver support via jrloper's CADI and on-the-fly updates for drivers and more. 32/64bit Heimdall for Mac is now supported. Several irrelevant command line features were added as well.
18APR13: CASUAL R417 Several fixes with improved logging and pastebin support thanks to jrloper
2May13: killswitch for old versions implemented.
Ironically I probably wouldn't have noticed the hole used this time had they not added the blacklisting of the old versions. Looking at the code for that gave me a push in the right direction
Troubleshooting
70% of problems with CASUAL involve USB cables and USB ports. All other problems can be tracked back to Windows XP.
CASUAL Stops and my phone is in Odin Mode/Download Mode
Use a different USB cable and a different USB port. Personally, I have two USB cables which work for everything and anything but they fail when it comes to Odin/Download Mode.
CASUAL displays Disconnected and won't let me press the button
Put your device into ADB mode. Settings>Developer Options>USB Debugging
CASUAL is not working and it's not something above
Did you install drivers? If you installed drivers, you need to uninstall and delete them. You don't need them because Windows installs them. Actually, they're poisonous, and some drivers install themselves with a future date which causes them to be un-upgradable. This means, you've shot yourself in the foot. You can run Samsung Kies and do the troubleshoot connection wizard, or you can go to device manager and uninstall the driver + delete driver.
CASUAL is not working and I'm absolutely sure it's not a driver issue
Let everything sit for a bit. CASUAL will generally pop up a troubleshooting message.
If you're sure nothing has happened for the last 3 minutes, disconnect the USB and restart the device normally.
Restart your computer
Try again using a new stock USB cable, on a different USB port, preferably located in the back of the computer.
I just want to annoy you
First grab a hammer and go outside into the back yard and hit yourself repeatedly in the head. If you do not have a hammer, borrow one from your neighbor. If you don't have a yard, borrow one from your neighbor. If you don't have a head, mission accomplished.
Mac version will not be available tonight. I can continue troubleshooting on 1.3.2 to make it work sometimes, but we need Heimdall 1.4.2 built for Mac properly in order to add support.... and that would be the magic bullet. Any mac developers? Here's the source we need built: https://github.com/Benjamin-Dobell/Heimdall Just the command line "heimdall" app is required in mpkg format.
Re: Jailbreak Your Verizon Galaxy Note 2 -- Even after update
I'm still available for testing. I'll be up all night.
Sent from my SCH-I605 using XDA Premium HD app
U DA MAN
Thanks Adam!!!
I have had this phone for a week and the Verizon rep F'ed me up the arse by installing the latest update without even asking me about it.
I worked with your last instruction before I finally realized I was hosed and had no hope.
Imagine my surprise when you announce this update just yesterday!!!!!!!!
I will be working on this first thing in the morning. The only reason I am not doing this now is the king of beers has ahold of me. But not enough to keep me from expressing my gratitude. Expect a dontation!!!!!!!!!!!:victory:
any ideas what im doing wrong? im doing something obviously that im not supposed to be....
tried to use the windows version on the family computer.
that is the single most frustrating fail i have encountered.
---------- Post added at 12:43 AM ---------- Previous post was at 12:40 AM ----------
[email protected]|ice said:
any ideas what im doing wrong? im doing something obviously that im not supposed to be....
Click to expand...
Click to collapse
Yup. Same here.
Sent from my Nexus 7 using XDA Premium HD app
I'm sure I'm just noobing it up...
I flashed back to stock with the BAV baseline and Odin 3.07.
I ran Casual. Everything seems to go fine. Phone reboots to "Downloading, Do not turn off target!!" message.
I flash Suckit Bootloader, and get the following failure in Odin:
<ID:1/004> SetupConnection..
<ID:1/004> Initialzation..
<ID:1/004> Get PIT for mapping..
<ID:1/004> Firmware update start..
<ID:1/004> recovery.img
<ID:1/004> NAND Write Start!!
<ID:1/004> FAIL!
Should I bury my head in the sand in shame for an obvious mistake?
Psyanide said:
I'm sure I'm just noobing it up...
I flashed back to stock with the BAV baseline and Odin 3.07.
I ran Casual. Everything seems to go fine. Phone reboots to "Downloading, Do not turn off target!!" message.
I flash Suckit Bootloader, and get the following failure in Odin:
<ID:1/004> SetupConnection..
<ID:1/004> Initialzation..
<ID:1/004> Get PIT for mapping..
<ID:1/004> Firmware update start..
<ID:1/004> recovery.img
<ID:1/004> NAND Write Start!!
<ID:1/004> FAIL!
Should I bury my head in the sand in shame for an obvious mistake?
Click to expand...
Click to collapse
thats exactly what im seeing.
i was certain i was doing it all in the correct order.
Re: Jailbreak Your Verizon Galaxy Note 2 -- Even after update 26JAN13
I used the previous "jailbreak" and couldn't believe how simple you made it. Thank you! You do so much work for the entire android community without expecting anything in return. We are all so lucky to have someone as dedicated as you working for our cause. Keep doin your thing!
Sent From My Unlocked Note 2. Thanks Adam and everyone involved!
should we flash the bootloader and the odin rom at the same time or separably? Thx!
[email protected]|ice said:
thats exactly what im seeing.
i was certain i was doing it all in the correct order.
Click to expand...
Click to collapse
I saw your post as soon as I hit submit on mine. Same error. One odd thing: when I manually select download mode, I see a bit of text in the upper left. When this version of casual reboots to download mode, that text is missing. Not sure if it even matters, but I thought it worth noting...
Re: Jailbreak Your Verizon Galaxy Note 2 -- Even after update
Anyone who does get it working, post the instructions for the rest of us? Thank you in advance.
Sent from my Nexus 7. *sigh *
Psyanide said:
I'm sure I'm just noobing it up...
I flashed back to stock with the BAV baseline and Odin 3.07.
I ran Casual. Everything seems to go fine. Phone reboots to "Downloading, Do not turn off target!!" message.
I flash Suckit Bootloader, and get the following failure in Odin:
<ID:1/004> SetupConnection..
<ID:1/004> Initialzation..
<ID:1/004> Get PIT for mapping..
<ID:1/004> Firmware update start..
<ID:1/004> recovery.img
<ID:1/004> NAND Write Start!!
<ID:1/004> FAIL!
Should I bury my head in the sand in shame for an obvious mistake?
Click to expand...
Click to collapse
Sorry, New link http://d-h.st/Wyo My bad.. tried to get away with the old odin. We need a new one. Flash this with Odin.
^^^thank you Adam.
do you need any mirrors? These downloads are taking forever....... I can post them on my server if you want ?
I've flashed the BAV bootloader so far ...boots fine with stock.... casual didn't work so downloading it again.....
unlocked! Adam thank you so much, seriously. i know im just letters on a screen but i am indescribably grateful. thank you thank you!
Step 1: run Casual and follow instructions
Step 2: Casual will instruct you to flash baseline bootload (BAV baseline) in download/odin mode.
Step 3:Casual will instruct you to flash Baseline #2 + recovery (back atcha verizon)
step 4: profit.
[email protected]|ice said:
thats exactly what im seeing.
i was certain i was doing it all in the correct order.
Click to expand...
Click to collapse
[email protected]|ice said:
unlocked! Adam thank you so much, seriously. i know im just letters on a screen but i am indescribably grateful. thank you thank you!
Click to expand...
Click to collapse
Any tips? I got farther than last time, but Odin still hangs while flashing BackAtchaVerizon.tar.md5 with the following:
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> swagBoot
<ID:0/004> NAND Write Start!!
The phone appears to be getting the download, but after 5 minutes, no activity. I pulled battery and it rebooted fine, so no harm done.
Related
Gave my phone to a friend to root but he was unsuccessful with it so before it gets screwed up anymore thought I would try it. My Aria was really easy this one is a bit different.
My desktop won't run S2 says it is for galaxy S2 only.. Windows 7 64 bit. My laptop is windows 7 32 bit, it says the device is not plugged in. I installed SAMSUNG_USB_Driver_for_Mobile_Phones_V1.4.2.2 on the laptop but not sure if I need further drivers aside from Kies. I tried another kernel and now my laptop says the same thing as the desktop does.. S2 root application is for Samsung Galaxy S2 devices only.
Secondly the kernel he installed the phone doesn't like it so I can't make calls on it or do anything with it. I can still boot it into download mode but since he didnt take note of the original kernel that was on the phone it is making it difficult to backtrack. What should I do at this point? Keep trying another kernel till I find one that works or be best to just put the phone back (which may be hard since its unknown what kernel was on it)
Thanks
just re-flash your original firmware and yourll get your kernel back.
check here for firmwares
http://forum.xda-developers.com/showthread.php?t=1075278
or here for operater based ones
http://forum.xda-developers.com/showthread.php?t=1113928
root kernels
http://forum.xda-developers.com/showthread.php?t=1103399
Ok im not 100% sure i got your problem, but if you are able to enter download mode, cant' you just flash with odin, the lite'ning rom 6.1? This will already include the root and a stable custom kh3 (i started with this one as my first custom rom)
(be sure to reinstall Kies to put fresh drivers on your pc before, but also be sure to kill kies (not have it active in background) or it will block odin).
Rooting the S2 is very easy, you only need to put the cf-root kernel in the pda section of odin, doublecheck to NOT have "repartition" option active, and press start.
The S2root application is an alternative method that works, but requires more steps.
rembrandtlnx said:
Ok im not 100% sure i got your problem, but if you are able to enter download mode, cant' you just flash with odin, the lite'ning rom 6.1? This will already include the root and a stable custom kh3 (i started with this one as my first custom rom)
(be sure to reinstall Kies to put fresh drivers on your pc before, but also be sure to kill kies (not have it active in background) or it will block odin).
Rooting the S2 is very easy, you only need to put the cf-root kernel in the pda section of odin, doublecheck to NOT have "repartition" option active, and press start.
The S2root application is an alternative method that works, but requires more steps.
Click to expand...
Click to collapse
I can try, downloading it now and we'll see how it goes.
The firmware is not available on Samsungs site so Id have to find it else where is my guess.
greyclear said:
I can try, downloading it now and we'll see how it goes.
The firmware is not available on Samsungs site so Id have to find it else where is my guess.
Click to expand...
Click to collapse
you can find all the firmwares (original) in the "original SII android development" http://forum.xda-developers.com/showthread.php?t=1075278
Also if you want to try flash the lite'ning instead the original one , you can find the rom in the "S II android developement" of this forum http://forum.xda-developers.com/showthread.php?t=1095274
trying the lite'ing taking a while though so going to let it run. Ill update if any of this works or doesnt lol Thanks for the help
still loading, not sure if its stuck or what..give it another hour maybe it usually take this long?
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Litening_Rom_v6-1.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> factoryfs.img
<ID:0/006> modem.bin
It should usually take like 10-20 seconds..
Sent from my GT-I9100 using xda premium
Kinda figured as much was over 200 meg download so I expected it to take a little longer. Should I pull out the battery and try again?
this thread should get you bk to stcck
http://forum.xda-developers.com/showthread.php?t=1075278
this thread for root after.
http://forum.xda-developers.com/showthread.php?t=1103399
superhappyfuntimes
looks like you have kies running in background and blocking odin. Check That kies is not active in the System tray.
Also use Odin 1.83, you can find it in the original firmware thread i linked above.
Sent from my GT-I9100 using Tapatalk
yes was running in the background i closed it but no difference just sits there for a long time. i have odin 1.83. even kies doesnt see my phone
on stock firmware i didnt see anything for north america, just use a generic one?
well getting somewhere.. maybe. lite'ing took but when it boots I get all sorts of errors saying force close and if I try to bring up the download mode I get the recovery mode instead that I guess is built into the ROM but nothing fuctions there all I can do is scroll through options.
guess i have to take the phone back to the store odin doesnt even see the phone anymore neither does kies and the recovery section doesnt let me do anything I just get a triangle with an exclaimation point so I couldnt run any thing from SD card if i wanted to. What would I expect to hear from the store they going to charge me alot to repair it?
they took it back lol
greyclear said:
they took it back lol
Click to expand...
Click to collapse
What did they say?
Sent from my GT-I9003 using xda premium
They actually offered to root it for me LOL. They said it would void the warranty but I had it barely 24 hours and I told them a friend was trying to put a custom rom on it. I wasn't going to lie, it was a $200 phone I wasn't about to keep it if it didnt work anymore so I actually expected to be out just $200 bucks and cancel the phone contract as I just signed up with sprint, moved from ATT. Either way I didnt expect that outcome
greyclear said:
They actually offered to root it for me LOL. They said it would void the warranty but I had it barely 24 hours and I told them a friend was trying to put a custom rom on it. I wasn't going to lie, it was a $200 phone I wasn't about to keep it if it didnt work anymore so I actually expected to be out just $200 bucks and cancel the phone contract as I just signed up with sprint, moved from ATT. Either way I didnt expect that outcome
Click to expand...
Click to collapse
Lucky
Keep us informed if they fixed the problem or not ^^
I was asked to make this one-click to help simplify the process of restoring a stock factory build for our Note 8.0 users. At this time neither myself or @garwynn are planning on releasing a rooted One-Click.
This Odin One-Click.exe contains the Stock GT-N5110 XXDNE1 Bootloader, Kernel, Modem and ROM for the Samsung Galaxy Note 8 16GB Wi-Fi edition (GT-N5110). Yes, that means this comes with the full Knox Bootloader.
There has been no change to the ROM from the initial build released by Samsung.
This will NOT trigger the Yellow Triangle NOR will it increment the Odin flash count.
This one-click resets your whole device to the stock XXDNE1 experience, similar to a factory restore and it may wipe all data. It also contains the full bootloader and Knox.
Instructions:
1: Backup anything important and Disable any PINs.
During this process your device's software will be returned to the Stock setup. All system data will be lost. To be safe, it is best to archive your backup off your device, ie on your PC or Dropbox.
2: Install Samsung USB/Android drivers (if necessary).
Samsung Drivers Download Link
3: Download the XXDNE1 Stock ROM One-Click.
GT-N5110 XXDNE1 Full Restore Unrooted (Compressed Archive).exe (Resets user data)
4: Unzip One-Click ROM using 7zip (this package is a self-extracting exe you should just be able to double-click on it after download and it will do the rest).
5: Start the Odin One-Click.
Navigate to the location where the "GT-N5110 XXDNE1 Full Restore Unrooted.exe" was saved upon extract from the 7Zip archive.
Double-click on "GT-N5110 XXDNE1 Full Restore Unrooted.exe". *On Vista or newer, you may need to right-click on the file and Run as Administrator.
6: Place device in Download Mode.
- Power device completely off.
- Press and hold Volume Down, Home and Power buttons, all at the same time.
- Release the buttons only when the ‘Warning!!’ message appears.
- Press [Volume Up] to enter Download mode.
7: Connect USB cable to PC and device.
Odin should show a yellow COM port in the second column. If you do not see a yellow COM port, you may need to run the Odin One-Click as Administrator and/or unplug/plugin the USB cable after starting Odin One-Click.
8: Start Odin flash process.
Press [Start].
9: Complete - PASS!
Status should change to green PASS! At this point your device should automatically reboot.
The boot process will take slightly longer than usual during which time you'll see the Samsung logo screen.
Congratulations! You've flashed the Factory Restore XXDNE1 build!
XDA:DevDB Information
[ROM][ODIN] GT-N5110 XXDNE1 (Modem/Kernel/Bootloader/ROM - Full Restore - Unrooted), ROM for the Samsung Galaxy Note 8.0
Contributors
rwilco12
ROM OS Version: 4.4.x KitKat
Version Information
Status: Stable
Created 2015-02-09
Last Updated 2015-02-09
Download Link: rwilco12.com/forum/showthread.php?tid=762
n5100
Having trouble loading 4.4.2 bootlader through odin onto my n5100 would it be ok to flash this, then root it and then install the custom n5100 rom of my choice or would I be on tne wrong bootlader and mess my tab up TIA
johnnyk75 said:
Having trouble loading 4.4.2 bootlader through odin onto my n5100 would it be ok to flash this, then root it and then install the custom n5100 rom of my choice or would I be on tne wrong bootlader and mess my tab up TIA
Click to expand...
Click to collapse
I believe it would mess up your bootloader but I don't have a way to verify as I don't have the n5100. Sorry!
Sent from my SPH-L900 using Tapatalk
triangle away
Will this reset the flash counter and allow ota updates? Or do you need to reset flash counter before you do this?
capitoldach said:
Will this reset the flash counter and allow ota updates? Or do you need to reset flash counter before you do this?
Click to expand...
Click to collapse
This won't reset the counter but it won't increment it either. This is a 100% stock unrooted ROM so you'll be able to take OTA's again after flashing.
Can I side load this with ADB? I am currently bricked and looking to start over if I can get my N5110 to install another ROM.
Sent from my SGH-I317 using XDA Premium 4 mobile app
addison892 said:
Can I side load this with ADB? I am currently bricked and looking to start over if I can get my N5110 to install another ROM.
Sent from my SGH-I317 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
If you're bricked, how do you intend to use ADB?
styles420 said:
If you're bricked, how do you intend to use ADB?
Click to expand...
Click to collapse
I have full access to recovery and download modes.
I am unable to Odin and flash because of partition errors. I plan on using TWRP and the ADB option with Android SDk. Do you think this will work?
I have not been able to Odin . Pit files successfully and re-partition. I am hoping ADB will allow me to put the rom inside the current partitions and use TWRP to flash.
Just a thought. I really don't know what I am doing or how to fix it. But if I have download mode and recovery, I should be able to find a way.
I am currently in a bootloop to recovery.
Thanks for your response and any suggestions you may have.
Sent from my SGH-I317 using XDA Premium 4 mobile app
---------- Post added at 09:57 PM ---------- Previous post was at 09:48 PM ----------
I have followed the instructions posted here to the letter, but keep getting a FAIL! at the sboot.bin point shortly after starting one-click.
Sent from my SGH-I317 using XDA Premium 4 mobile app
addison892 said:
I have full access to recovery and download modes.
I am unable to Odin and flash because of partition errors. I plan on using TWRP and the ADB option with Android SDk. Do you think this will work?
I have not been able to Odin . Pit files successfully and re-partition. I am hoping ADB will allow me to put the rom inside the current partitions and use TWRP to flash.
Just a thought. I really don't know what I am doing or how to fix it. But if I have download mode and recovery, I should be able to find a way.
I am currently in a bootloop to recovery.
Thanks for your response and any suggestions you may have.
Sent from my SGH-I317 using XDA Premium 4 mobile app
---------- Post added at 09:57 PM ---------- Previous post was at 09:48 PM ----------
I have followed the instructions posted here to the letter, but keep getting a FAIL! at the sboot.bin point shortly after starting one-click.
Sent from my SGH-I317 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Unfortunately I don't know that this will work for you at this time. Essentially the one-click is a repackaged TAR. The TAR itself contains image files that correspond to specific partitions on your device. If the partitions on the device don't match up Odin is supposed to throw up a flag and stop the flash in order to prevent bricking the device.
I can't be 100% certain but given the fact it is stopping on sboot.bin, my guess is that the issues you are experiencing probably come from flashing a ZIP bootloader or ROM for another device. If that's the case we might be able to backtrack and undo what you've done so far but this won't work unless you have the right partition structures already in place.
I have spent hours trying to re-partition. The furthest I have gotten is where I am now... Stuck on Get PIT for mapping..
.. In ODIN. I am using the only PIT file for N5110 available on the entire World Wide Web!
☺
Sent from my SGH-I317 using XDA Premium 4 mobile app
hello, could someone please point me in the right direction. I've been trying to use this tool, I have access to stock recovery, when I factory reset it says it can't mount the /system. I tried this tool to reinstall every thing, but it fails at sboot.bin. all the research I've done leads me to believe this has something to do with the bootloader being locked, but I can't find anything about it, I keep getting lead back to this post. If anyone could point me where I need to be to figure this out I would really appreciate it.
Edit: I'm not sure what my problem was, but I eventually downloaded the stock 4.4.2 firmware and was able to flash through Odin and get up and running.
bookofjoshua said:
hello, could someone please point me in the right direction. I've been trying to use this tool, I have access to stock recovery, when I factory reset it says it can't mount the /system. I tried this tool to reinstall every thing, but it fails at sboot.bin. all the research I've done leads me to believe this has something to do with the bootloader being locked, but I can't find anything about it, I keep getting lead back to this post. If anyone could point me where I need to be to figure this out I would really appreciate it.
Edit: I'm not sure what my problem was, but I eventually downloaded the stock 4.4.2 firmware and was able to flash through Odin and get up and running.
Click to expand...
Click to collapse
can you point me in the direction of where you found stock 4.4.2 firmware, looked everywhere for odin flash file
redman2770 said:
can you point me in the direction of where you found stock 4.4.2 firmware, looked everywhere for odin flash file
Click to expand...
Click to collapse
For some reason they post the US version under Cellular South. You'll need to create a free account to download. It took about am hour for me to download with the free account.
http://www.sammobile.com/firmwares/download/30487/N5110UEU2CNE2_N5110XAR2CNE2_XAR.zip/
Does this clean up all the crap left over from many flashes & nandroid backups & restores? I find I have a lot of bits like old directories from previous meddling (mine) & would like to a real clean up back to pristine stock (so I can start meddling again, sort of from scratch so to speak.
Going to run it anyway (meddling again) to see what comes out the other end but was curious 'is all.
Error
This fails for me - on the tablet it says: sw rev. check fail. device:2, binary:1
Trying to flash back to stock after CM12
I've ran the app as administrator, see that is shows in the yellow box: 0:[COM4]
<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> sboot.bin
<ID:0/004>
<ID:0/004>
<OSM> All threads completed. (succeed 0 / failed 1)
I've got the SAME thing goin on as KJarlin does. I'm having to go through Parallels on my Mac as I do not have a Winblows machine. That shouldn't make any difference though. Does anyone have solution???
kjarlin said:
I've ran the app as administrator, see that is shows in the yellow box: 0:[COM4]
<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> sboot.bin
<ID:0/004>
<ID:0/004>
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
thewinelover said:
I've got the SAME thing goin on as KJarlin does. I'm having to go through Parallels on my Mac as I do not have a Winblows machine. That shouldn't make any difference though. Does anyone have solution???
Click to expand...
Click to collapse
Still no solution?
dopeismarcus said:
Still no solution?
Click to expand...
Click to collapse
+1
Same error.
Regards
kjarlin said:
This fails for me - on the tablet it says: sw rev. check fail. device:2, binary:1
Trying to flash back to stock after CM12
I've ran the app as administrator, see that is shows in the yellow box: 0:[COM4]
<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> sboot.bin
<ID:0/004>
<ID:0/004>
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
thewinelover said:
I've got the SAME thing goin on as KJarlin does. I'm having to go through Parallels on my Mac as I do not have a Winblows machine. That shouldn't make any difference though. Does anyone have solution???
Click to expand...
Click to collapse
dopeismarcus said:
Still no solution?
Click to expand...
Click to collapse
mcpterra said:
+1
Same error.
Regards
Click to expand...
Click to collapse
Not able to verify as I no longer have the Note 8 but if I remember correctly the error you are getting is due to your device having a newer bootloader than the one-click. Most of the time a new bootloader locks out flashing of older bootloaders.
Sent from my Nexus 5X using Tapatalk
Q&A for [GUIDE][VZW Edition]How to Root/Rom/Return to Stock the VZW Galaxy Note II!
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:
Help! Odin Bootloading Issue on Verizon Samsung Galaxy Note II
Used the Odin tool (which I've done in the past without issue) to bootload the 4.4.2 software onto my phone and it now just flashes the start-up banner. Worse, my computer no longer recognizes my phone as a valid device, so attempts to load something else will not work.
---------- Post added at 11:21 AM ---------- Previous post was at 10:26 AM ----------
ConvolutedSpeech said:
Used the Odin tool (which I've done in the past without issue) to bootload the 4.4.2 software onto my phone and it now just flashes the start-up banner. Worse, my computer no longer recognizes my phone as a valid device, so attempts to load something else will not work.
Click to expand...
Click to collapse
Okay, so, I've managed to get my device recognized by placing it in Odin Mode and reconnecting. I still can't bootload any software, though, it keeps resulting in failures. :crying:
ConvolutedSpeech said:
Used the Odin tool (which I've done in the past without issue) to bootload the 4.4.2 software onto my phone and it now just flashes the start-up banner. Worse, my computer no longer recognizes my phone as a valid device, so attempts to load something else will not work.
---------- Post added at 11:21 AM ---------- Previous post was at 10:26 AM ----------
Okay, so, I've managed to get my device recognized by placing it in Odin Mode and reconnecting. I still can't bootload any software, though, it keeps resulting in failures. :crying:
Click to expand...
Click to collapse
This previous thread post gives some tips that might help you fix your phone:
http://forum.xda-developers.com/showthread.php?p=56167850
mattnmag said:
This previous thread post gives some tips that might help you fix your phone:
http://forum.xda-developers.com/showthread.php?p=56167850
Click to expand...
Click to collapse
I appreciate your taking the time to reply to my post. I read over the tips you listed and tried those I hadn't already. I've switched my usb cord to every port on my computer. I've switched to different cords, oem and otherwise. I downloaded KIES, as per the last of your suggestions, and can't say how useful that may or may not be, as my device never would connect to the KIES interface. I've had many attempted firmware loads on my phone via ODIN, but all give me the unsuccessful write message. I've tried flashing TWRP, which I was pretty sure I already had on my phone, but still no bueno. It won't let me access TWRP if I do have it, and if I don't . . . well, there's that. I don't really know what else to do.
---------- Post added at 07:18 PM ---------- Previous post was at 07:10 PM ----------
ConvolutedSpeech said:
I appreciate your taking the time to reply to my post. I read over the tips you listed and tried those I hadn't already. I've switched my usb cord to every port on my computer. I've switched to different cords, oem and otherwise. I downloaded KIES, as per the last of your suggestions, and can't say how useful that may or may not be, as my device never would connect to the KIES interface. I've had many attempted firmware loads on my phone via ODIN, but all give me the unsuccessful write message. I've tried flashing TWRP, which I was pretty sure I already had on my phone, but still no bueno. It won't let me access TWRP if I do have it, and if I don't . . . well, there's that. I don't really know what else to do.
Click to expand...
Click to collapse
Oh, I also tried ODIN 3.7, 3.9, and 3.10.
@ConvolutedSpeech,
You can not install a custom recovery like TRWP on your phone after it got upgraded to 4.4.2 because the bootloader is locked with no current method for you to unlock it.
The only thing you can do right now is to restore the phone back to factory stock 4.4.2. There's a root method called GhettoRoot for 4.4.2, but no bootloader unlock method at present.
If you can post the log from Odin showing the error you're getting when trying to restore your phone, that will help others to help you. (I'm not sure why Kies couldn't see your phone, but I would uninstall it now or make sure it's totally disabled when running Odin again since the 2 programs can conflict).
I won't be able to respond for a while due to my job, but maybe someone else can help out.
mattnmag said:
@ConvolutedSpeech,
You can not install a custom recovery like TRWP on your phone after it got upgraded to 4.4.2 because the bootloader is locked with no current method for you to unlock it.
The only thing you can do right now is to restore the phone back to factory stock 4.4.2. There's a root method called GhettoRoot for 4.4.2, but no bootloader unlock method at present.
If you can post the log from Odin showing the error you're getting when trying to restore your phone, that will help others to help you. (I'm not sure why Kies couldn't see your phone, but I would uninstall it now or make sure it's totally disabled when running Odin again since the 2 programs can conflict).
I won't be able to respond for a while due to my job, but maybe someone else can help out.
Click to expand...
Click to collapse
Thank you for all of your time. From looking at the posts on Ghettoroot it looks like it requires being able to send files to your phone and put it in debugging mode . . . which I can't so much do, given my phone won't let me in it. Maybe there's a workaround I'm missing? I uninstalled Kies and reran ODIN. Here's a c/p of the log:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I605VRUFND7_I605VZWFND7_I605VRUFND7_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> sboot.bin
<ID:0/005> NAND Write Start!!
<ID:0/005> FAIL!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
If anyone can help it would be much appreciated! Thank you mattnmag, for all of your efforts, so far!
ConvolutedSpeech said:
Thank you for all of your time. From looking at the posts on Ghettoroot it looks like it requires being able to send files to your phone and put it in debugging mode . . . which I can't so much do, given my phone won't let me in it. Maybe there's a workaround I'm missing? I uninstalled Kies and reran ODIN. Here's a c/p of the log:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I605VRUFND7_I605VZWFND7_I605VRUFND7_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> sboot.bin
<ID:0/005> NAND Write Start!!
<ID:0/005> FAIL!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
If anyone can help it would be much appreciated! Thank you mattnmag, for all of your efforts, so far!
Click to expand...
Click to collapse
Crickets, huh?
@ConvolutedSpeech,
Can you confirm that you do have a Verizon Note 2 model SCH-I605?
Also, did you try to Odin flash any other device's firmware onto your phone (like the international N7100 firmware). If so, that would have overwritten your Verizon bootloader/firmware and you won't be able to use ODIN to restore your phone if that's the case.
If you do have the Verizon Note 2 and didn't accidentally flash another device firmware onto it , then you should be able to restore your phone back to Verizon factory stock 4.4.2.
Droidstyle's restore guide has step by step instructions on how to Odin restore the phone. If you're not flashing the pit file with the firmware tar file... then try that as well.
If it won't work on your computer and you have access to another computer (preferably one with Windows 7), then try the restore on that. Also... make sure you have a good download of the firmware.... you can grab the Verizon 4.4.2 firmware from here if you're not getting it from Sammobile already: http://www.sammobile.com/firmwares/download/30950/I605VRUFND7_I605VZWFND7_VZW.zip/
mattnmag said:
@ConvolutedSpeech,
Can you confirm that you do have a Verizon Note 2 model SCH-I605?
Also, did you try to Odin flash any other device's firmware onto your phone (like the international N7100 firmware). If so, that would have overwritten your Verizon bootloader/firmware and you won't be able to use ODIN to restore your phone if that's the case.
If you do have the Verizon Note 2 and didn't accidentally flash another device firmware onto it , then you should be able to restore your phone back to Verizon factory stock 4.4.2.
Droidstyle's restore guide has step by step instructions on how to Odin restore the phone. If you're not flashing the pit file with the firmware tar file... then try that as well.
If it won't work on your computer and you have access to another computer (preferably one with Windows 7), then try the restore on that. Also... make sure you have a good download of the firmware.... you can grab the Verizon 4.4.2 firmware from here if you're not getting it from Sammobile already:
Click to expand...
Click to collapse
Hey mattnmag,
Yes, I do have a Verizon Note 2 SCH-I605. No, I've been trying to flash the Sammobile sourced version of the download you link to, but I suppose I could try redownloading it, for giggles, one never knows. I'll check out the restore guide and see if I'm missing anything. The computer I'm using is running on Windows 7, but I guess I could try my laptop, which also runs on 7. I really do appreciate all the time you've spent trying to help me.
Thanks!
---------- Post added at 06:50 AM ---------- Previous post was at 06:44 AM ----------
ConvolutedSpeech said:
Hey mattnmag,
Yes, I do have a Verizon Note 2 SCH-I605. No, I've been trying to flash the Sammobile sourced version of the download you link to, but I suppose I could try redownloading it, for giggles, one never knows. I'll check out the restore guide and see if I'm missing anything. The computer I'm using is running on Windows 7, but I guess I could try my laptop, which also runs on 7. I really do appreciate all the time you've spent trying to help me.
Thanks!
Click to expand...
Click to collapse
OIC, haha, that's the guide I used to brick myself. Probably I missed something, but I can't see what, at this point.
---------- Post added at 07:05 AM ---------- Previous post was at 06:50 AM ----------
ConvolutedSpeech said:
Hey mattnmag,
Yes, I do have a Verizon Note 2 SCH-I605. No, I've been trying to flash the Sammobile sourced version of the download you link to, but I suppose I could try redownloading it, for giggles, one never knows. I'll check out the restore guide and see if I'm missing anything. The computer I'm using is running on Windows 7, but I guess I could try my laptop, which also runs on 7. I really do appreciate all the time you've spent trying to help me.
Thanks!
---------- Post added at 06:50 AM ---------- Previous post was at 06:44 AM ----------
OIC, haha, that's the guide I used to brick myself. Probably I missed something, but I can't see what, at this point.
Click to expand...
Click to collapse
AAAAAAAAAAAAAAAAAAGGGGGGGGGGGGGHHHHHHHHHHH!!!!!!!! Okay, either I'm a dumbass, or you're a genius, but at this point I don't care how you want to label it. Flashing the PIT file WITH THE firmware worked beautifully . . . I think . . . my phone is now starting up and I got a full load and pass in ODIN. OMG, tytytytyty! I love you! Hahahaha, yes, it's definitely starting up! Yayyy! F*** yeah, MY PHONE IS ALIVE!
LOL. I'm glad to hear you fixed it. Just to be sure you get a totally fresh start with nothing leftover... it may be a good idea to boot into stock recovery and wipe cache and complete a factory reset.
:thumbup:
mattnmag said:
LOL. I'm glad to hear you fixed it. Just to be sure you get a totally fresh start with nothing leftover... it may be a good idea to boot into stock recovery and wipe cache and complete a factory reset.
:thumbup:
Click to expand...
Click to collapse
Thanks! Based on the success of taking your previous advice, I'll have to do that! Have an AWESOME Thanksgiving!
Returning to stock
So I know that there are different instructions for returning to stock with odin after having taken the MJ9 4.3 OTA update, but I honestly don't remember if I did take the update. I have had this phone for so long, as well as other phones, and I just can't remember if I took it. Is there a way to either be able to tell if I did, or to return to stock safely regardless?
eve.ning_rose said:
So I know that there are different instructions for returning to stock with odin after having taken the MJ9 4.3 OTA update, but I honestly don't remember if I did take the update. I have had this phone for so long, as well as other phones, and I just can't remember if I took it. Is there a way to either be able to tell if I did, or to return to stock safely regardless?
Click to expand...
Click to collapse
When you go to your phone's System Settings/About Phone, what does it show under Android Version and Build Number? That may help you determine what you're running.
An easy way to confirm what bootloader you're on would be to boot into Odin Mode (Volume Down+Home Button+Power Button at the same time, then press volume up to continue to Odin Mode). If it looks like the picture I've attached of ODIN mode from my phone (which is running 4.1.2), then your bootloader would not be on 4.3 or 4.4.2 because there's nothing about Knox.
But... if you see anything about Knox when in Odin mode, then it will be on 4.3 or higher bootloader. If it's on 4.3 or higher, then you won't be able to downgrade back to 4.1.2 and would need to restore to stock 4.3 or 4.4.2 (depending on what build version your on).
In Odin mode it says
ODIN MODE
PRODUCT NAME: SCH-I605
CUSTOM BINARY DOWNLOAD (Yes, 1 counts)
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
It looks like you're still on 4.1.1 or 4.1.2 bootloader... since there's no mention of Knox. You should be able to follow section 1b in Droidstyle's Restore guide to restore the phone to factory stock 4.1.2 VRAMC3. This is the bootloader you'll want to stay on if you want to have the option to use Casual to unlock the bootloader and root/run custom ROM's. Your phone would probably be more valuable to others as well if you're going to sell it on Swappa.
Edit: Look into Chainfire's Triangle away app from the Play Store if you want to reset the Binary count back to 0. (And only use Triangle away on rooted 4.1.2 with unlocked bootloader for our phone... if you try it on 4.3 or 4.4.2, it may hard brick the device. Here's the XDA thread on Triangle Away if interested: http://forum.xda-developers.com/galaxy-s2/orig-development/2014-01-15-triangleaway-v3-26-t1494114
Thank you! So I was originally restoring to stock unrooted because For some reason my phone stopped allowing me to flash any ROM. I unrooted, then rooted with casual noyou, and I still can't flash any ROM. I have verified that I do have root, and I have tried with both CWM and TWRP, but nothing. Any idea what could be causing this? Or how to fix it? I am stuck on stock 4.1.1 now.
I'm not sure if any of the custom ROM'S in the development threads will work with a 4.1.1 base... (they might.. but I'm not sure). I would probably use Droidstyle's guide to Odin restore the phone to 4.1.2 VRAMC3, then would boot into stock recovery and wipe cache & complete a factory reset just to make sure you've got a totally clean slate to work from.
Then, I'd run CASUAL again to root and unlock the bootloader.
(Edit)... I'm also wondering if the custom recovery that you were using to try to flash the ROM could have been too old for the newer ROM'S... or the wrong custom recovery. Some ROM'S need a specific version of the custom recovery to work, so make sure you read through the thread of whichever ROM you want to flash and that you're using the recommended version of the recovery for that specific ROM.
soft bricked note 2?
i wanted to give my son my note 2 for christmas, but i didnt want him to have a rooted phone. i have unrooted and returned to stock a few note 2 phones with no problem, but ..... this time ive run into trouble. i put the proper files into the pda slot, hit start, i got a pass. but i think im on a bootloop. i cant get into recovery, but i can get back into download mode. i would really appreciate some help. this was gonna be his "big" gift and now im screwed thanks so much for all you guys do on this site. ive gotten so much help here.
take care and merry chrismas
Verizon note 2 Root problems.
I had my Note 2 SCH-I605 rooted before this, I bricked it and now its back to life but I can not get anything to work for root. I have tried odin,casual and kingo root and Ghettoroot. Odin says It has passed etc... and I never have root. Kingo says it works and that it has installed su but its never there. I have even checked with root checker to verify. And no root. I have the stock firmware (4.4.2) back on and I used odin to put the stock firmware back on. Can anyone shed any light on what I might be doing wrong.
chanelstout said:
i wanted to give my son my note 2 for christmas, but i didnt want him to have a rooted phone. i have unrooted and returned to stock a few note 2 phones with no problem, but ..... this time ive run into trouble. i put the proper files into the pda slot, hit start, i got a pass. but i think im on a bootloop. i cant get into recovery, but i can get back into download mode. i would really appreciate some help. this was gonna be his "big" gift and now im screwed thanks so much for all you guys do on this site. ive gotten so much help here.
take care and merry chrismas
Click to expand...
Click to collapse
I downloaded stock firmware then applied with odin. It was 4.4.2 if I find the link ill post as soon as I can.
Hey everyone,
I'm brand new at this, so please forgive me. Yesterday I followed directions to root after a security update at http://forum.xda-developers.com/galaxy-s4-verizon/general/how-to-root-i545vrufng6-t2905848 and, with only a few bumps, managed to get my device rooted and back up to speed on vrufng6. After having some trouble getting my build to go into permissive mode, I managed to get a safestrap partition installed and a backup put in place - things seemed to be running fine and dandy.
This morning I tried to install an unsupported version of cyanogenmod (I blame their site, they said that the verizon build had been included in an all-in-one version) and found that it was non-functional. No troubles though, I had a backup! Right? Wrong. As far as I can tell I accidentally saved the backup to the externalSD card and managed to do something to make it inaccessible -- safestrap says it can't load and finds no system information. Odin (which I used heavily in the initial downgrade-upgrade shuffle to reinstate root access) won't load the full recovery image provided in the original thread or any of the stock roms out on the internet.
So I've been trying to use the push update feature found in recovery mode (using adb, running windows 8.1 command prompt) and once it uploads I get an error message on the phone, and am back where I started from. I should mention that it doesn't seem like we S IV users have a fastboot option.
Is there a way to fix this? I can **sometimes** get into safestrap, but most times my options are download mode and recovery mode (letting it try to boot normally just hangs the device at Galaxy S 4 screen for awhile before a reboot.) When I do get through safestrap I can find my recovery image, but it won't mount, and the restart option warns me that I have no OS installed.
Again, I'm sorry if I'm not offering enough information. If anyone knows how to get this thing back to stock I would really appreciate a point in the right direction.
Can't you just use Kies to flash the stock firmware? That's what I did when I wound up with a non working os. I coudn't even load the os. Try Kies first.
backsidesmack said:
Can't you just use Kies to flash the stock firmware? That's what I did when I wound up with a non working os. I coudn't even load the os. Try Kies first.
Click to expand...
Click to collapse
backsidesmack -- Thanks for the response. I did try Kies, but might not have given it a fair shake. It won't find my device by its own volition, and when I enter the (correct) model and serial numbers for an emergency recovery it won't accept the input. I've tried each of the options under the tool menu, but it can't find my phone. Is there some secret to getting it to cooperate?
If you can get into download mode then flash the full wipe of this. http://forum.xda-developers.com/showthread.php?t=2735172 Don't forget this will WIPE all your data.
michaely123 said:
If you can get into download mode then flash the full wipe of this. http://forum.xda-developers.com/showthread.php?t=2735172 Don't forget this will WIPE all your data.
Click to expand...
Click to collapse
Hey this is DylanDeValera: in 3 hours I managed to lose my login credentials.
Just tried it with odin 3.09 -- here's the failure log:
<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> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
<ID:0/003> Added!!
Any pointers? Also didn't take it through adb sideload..
michaely123 said:
If you can get into download mode then flash the full wipe of this. http://forum.xda-developers.com/showthread.php?t=2735172 Don't forget this will WIPE all your data.
Click to expand...
Click to collapse
Just tried it with odin 3.09 -- here's the failure log:
<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> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
<ID:0/003> Added!!
Any pointers? I couldn't get it to work through sideload either; same error as before.
It's also probably time to confess that I'm running a windows 8.1 vm on a mac, to do all of this, but I managed to flash to a downgraded kernel and back up with the same setup.
going back to Kies, emergency firmware recovery won't show any options. How do you generate a recovery code?
Quick question. Which version of SafeStrap did you download and install?
ErisDev said:
Quick question. Which version of SafeStrap did you download and install?
Click to expand...
Click to collapse
3.75, which I believe added a button that would attempt to set enforcing mode to passive (instead of using terminal emulator for the same purpose).
I don't think it was any fault of its own - the latest verizon update removed the exploit that towelroot uses and also seemed to do something to disable setenforce 0, so I had to downgrade the firmware using the method posted above to get it to work. The safestrap boot also seemed to work fine, and claimed to successfully restore the backup I had made when I tested it.
DylanDevalera said:
3.75, which I believe added a button that would attempt to set enforcing mode to passive (instead of using terminal emulator for the same purpose).
I don't think it was any fault of its own - the latest verizon update removed the exploit that towelroot uses and also seemed to do something to disable setenforce 0, so I had to downgrade the firmware using the method posted above to get it to work. The safestrap boot also seemed to work fine, and claimed to successfully restore the backup I had made when I tested it.
Click to expand...
Click to collapse
You can only flash Cynanogenmod or any pure AOSP rom if you are on MDK, which you are not. Being on NG6, your only options for rom's are going to be Touchwiz based as we can't flash any kind of kernal. Having said that, you're only option now is going to be the NC5 full wipe Odin tar that is in the thread found here http://forum.xda-developers.com/showthread.php?t=2735172. It seems as if you've had problems flashing in Odin, I just returned my phone to NC5 stock this past weekend using the full wipe files found in the link so your issue, assuming you got good downloads, is either hardware (USB cable, port on p.c., port on phone) or you should try a different version of Odin. I used 3.10 and always have and it has always worked like a charm.
"It was for freedom that Christ set us free; therefore keep standing firm and do not be subject again to a yoke of slavery." - Galatians 5:1
DylanDevalera said:
As far as I can tell I accidentally saved the backup to the externalSD card
Click to expand...
Click to collapse
Why would you not save the backup to your external SD card?
ETA: Were you using Kies for Windows or Mac?
Seems to be some extra work needs to be done to use a VM:
Samsung Rooting with Odin / VirtualBox / OSX Lion
Using Odin in Mac OSX with Windows as VirtualBox's Guest OS
Hope you don't have a brick.
Tromatic said:
Why would you not save the backup to your external SD card?
ETA: Were you using Kies for Windows or Mac?
Seems to be some extra work needs to be done to use a VM:
Samsung Rooting with Odin / VirtualBox / OSX Lion
Using Odin in Mac OSX with Windows as VirtualBox's Guest OS
Hope you don't have a brick.
Click to expand...
Click to collapse
Yeah, the external backup comment was dumb on my part, I was misinterpreting safestrap's recovery methods. I think the trouble came from using an older version that ng6 was outsmarting.
Thanks for all the info on extra VM work. It did end up working without any extra help: turned out it was just an outdated version of odin, so the VM was functioning fine. It's always the most trivial things. I'm using parallels desktop FWIW. Kies was by way of mac.
liljoe727 said:
assuming you got good downloads, is either hardware (USB cable, port on p.c., port on phone) or you should try a different version of Odin. I used 3.10 and always have and it has always worked like a charm.
Click to expand...
Click to collapse
HOLY CRAP THANK YOU!! I was running 3.09, odin 3.10 fixed it on the first try. You.. If I could buy you a beer or something.. Thanks, really. to a layman it's always the most trivial little details.
Thanks again, you saved my phone.
Hi guys, new poster here. After researching the threads on here and on other sites, I can't seem to find the exact solution to fix this. I've got a U.S. version that when trying to update the stock ROM from Gingerbread 2.3.5 to 2.3.6, I accidentally booted up my device during the initial install process through Odin. When I did that my device went into the forced download mode with the "Phone triangle to PC " error screen. I'm not exactly sure where to go from here, as I can't get into the normal (maintenance) download mode or Recovery Mode.
When I first tried to install the 2.3.6 software, guided by the instructions in the following thread title (can't post the link since it's my first time, sorry), "[How to] Upgrade SGP 5.0 to Android v2.3.6" posted by Sanchezhacker on anything but ipod's website, here is what I ended up with:
<ID:0/005> Added!!
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<OSM> All threads completed. (succeed 0 / failed 1)
I'd like to be able to install 2.3.6 but I'm not exactly sure how to get out of the forced download mode first.
How do I get out of download mode and how can I install 2.3.6 from there?
Your input is greatly appreciated!!
Thank you, and God bless!!
International96 said:
Hi guys, new poster here. After researching the threads on here and on other sites, I can't seem to find the exact solution to fix this. I've got a U.S. version that when trying to update the stock ROM from Gingerbread 2.3.5 to 2.3.6, I accidentally booted up my device during the initial install process through Odin. When I did that my device went into the forced download mode with the "Phone triangle to PC " error screen. I'm not exactly sure where to go from here, as I can't get into the normal (maintenance) download mode or Recovery Mode.
When I first tried to install the 2.3.6 software, guided by the instructions in the following thread title (can't post the link since it's my first time, sorry), "[How to] Upgrade SGP 5.0 to Android v2.3.6" posted by Sanchezhacker on anything but ipod's website, here is what I ended up with:
<ID:0/005> Added!!
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<OSM> All threads completed. (succeed 0 / failed 1)
I'd like to be able to install 2.3.6 but I'm not exactly sure how to get out of the forced download mode first.
How do I get out of download mode and how can I install 2.3.6 from there?
Your input is greatly appreciated!!
Thank you, and God bless!!
Click to expand...
Click to collapse
Forced Download Mode only happens when there is something critically wrong with the current state of your Player. I recommend that you return to stock
http://www.4shared.com/zip/hFJmoXTiba/YP-G70-UEKI8-Stock-USA-Meticul.html?
Meticulus, I really appreciate your help, thank you for it.
Well, when I tried to download your file in the link you gave me, I waited until 4shared's wait to download timer ran out and here's the message I got once it did, "Sorry, the file link that you requested is not valid. Sign error."
Any ideas for a workaround?
International96 said:
Meticulus, I really appreciate your help, thank you for it.
Well, when I tried to download your file in the link you gave me, I waited until 4shared's wait to download timer ran out and here's the message I got once it did, "Sorry, the file link that you requested is not valid. Sign error."
Any ideas for a workaround?
Click to expand...
Click to collapse
I just tried it, and it works... I suggest that you sign up for 4shared. Then download...
Meticulus said:
I just tried it, and it works... I suggest that you sign up for 4shared. Then download...
Click to expand...
Click to collapse
I'm actually signed in to 4shared via my Facebook, but that shouldn't prevent it from letting me download, should it?
International96 said:
I'm actually signed in to 4shared via my Facebook, but that shouldn't prevent it from letting me download, should it?
Click to expand...
Click to collapse
I'll download and re-up it at androidfilehost.com...
downloading now...
International96 said:
I'm actually signed in to 4shared via my Facebook, but that shouldn't prevent it from letting me download, should it?
Click to expand...
Click to collapse
@International96
https://www.androidfilehost.com/?fid=24651442761498983
Meticulus said:
@International96
https://www.androidfilehost.com/?fid=24651442761498983
Click to expand...
Click to collapse
Alrighty, I just downloaded the ZIP file, unpacked it, now do I run it through Odin? I have Odin 1.85 installed. I tried to run it in Odin's software using the PDA tab, plugged my device in and linked the file to Odin and clicked "Start", here's the results I got,
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> YP-G70-UEKI8-Stock-USA-Meticulus.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<OSM> All threads completed. (succeed 0 / failed 1)
Not sure why it failed... Any suggestions?
To be honest, some step-by-step instructions would help me a lot. Thank you.
Just curious to see if there's any update on this? I'm still not sure how to install the md5 file to my SGP using Odin, like I had mentioned above.
International96 said:
Just curious to see if there's any update on this? I'm still not sure how to install the md5 file to my SGP using Odin, like I had mentioned above.
Click to expand...
Click to collapse
Sorry, busy lately but it looks like you did it properly. Normally all you have to do is put the *.md5 file in PDA and hit start. Looks like you did that and it still did not work. I suggest that you download the first tar ( not zip ) file here: http://forum.xda-developers.com/showthread.php?t=1445840
This is a custom kernel with a custom recovery in it. flash the .tar file the same way you did with the .md5 file. Click PDA; select the tar file; click start.
See if that succeeds. If it does, attempt to get into recovery like this :
https://www.youtube.com/watch?v=Uzu4uDTDL5k
NOTE: Video shows how to get to download mode but just use the opposite volume key to get to recovery.
Then let me know what happens....:highfive::highfive:
Meticulus said:
Sorry, busy lately but it looks like you did it properly. Normally all you have to do is put the *.md5 file in PDA and hit start. Looks like you did that and it still did not work. I suggest that you download the first tar ( not zip ) file here: http://forum.xda-developers.com/showthread.php?t=1445840
This is a custom kernel with a custom recovery in it. flash the .tar file the same way you did with the .md5 file. Click PDA; select the tar file; click start.
See if that succeeds. If it does, attempt to get into recovery like this :
https://www.youtube.com/watch?v=Uzu4uDTDL5k
NOTE: Video shows how to get to download mode but just use the opposite volume key to get to recovery.
Then let me know what happens....:highfive::highfive:
Click to expand...
Click to collapse
It's okay, thanks for the follow-up, I appreciate it. Well, I downloaded the .tar file, flashed it in Odin and here's what I got... Seems like it just loves to fail, haha.
<ID:0/006> Added!!
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<OSM> All threads completed. (succeed 0 / failed 1)
International96 said:
It's okay, thanks for the follow-up, I appreciate it. Well, I downloaded the .tar file, flashed it in Odin and here's what I got... Seems like it just loves to fail, haha.
<ID:0/006> Added!!
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Has Odin ever worked for you?
Meticulus said:
Has Odin ever worked for you?
Click to expand...
Click to collapse
Come to think of it, I don't believe it has. Except for the process of getting it bricked, with my dumb move to try and power it up in the middle of the install process of 2.3.6, haha. That was a bad move on my part. But no, it hasn't.
International96 said:
Come to think of it, I don't believe it has. Except for the process of getting it bricked, with my dumb move to try and power it up in the middle of the install process of 2.3.6, haha. That was a bad move on my part. But no, it hasn't.
Click to expand...
Click to collapse
Are you familiar with Ubuntu and running linux? If I were you, I get on a linux box and see what you can do with heimdall....:good:
Meticulus said:
Are you familiar with Ubuntu and running linux? If I were you, I get on a linux box and see what you can do with heimdall....:good:
Click to expand...
Click to collapse
I know a little bit about it but not a lot. I think I tried doing that once before but I didn't know exactly how to set it up.
Soft Bricked Samsung Galaxy Player 5.0
Hello,
First, I am sorry to jump in this thread, but I am having the exact problem listed in this thread. I picked up this player at a hamfest in NC. The battery was dead. But when I plugged it in to charge, the screen was black with a little phone symbol, an orange triangle, and a computer.
I have tried all the instruction that were posted, with the same results. So if you have any other suggestions I'd appreciate it.
thank you
Hey Johnny, I figured you've been busy, but I'm still out of service with my Galaxy Player, I'm not sure exactly how to go about using Ubuntu and running Linux. I really appreciate your help thus far, but it's been almost a month and still no luck with the darn device... Maybe it's time to look for a replacement, possibly..
lostnubie said:
Hello,
First, I am sorry to jump in this thread, but I am having the exact problem listed in this thread. I picked up this player at a hamfest in NC. The battery was dead. But when I plugged it in to charge, the screen was black with a little phone symbol, an orange triangle, and a computer.
I have tried all the instruction that were posted, with the same results. So if you have any other suggestions I'd appreciate it.
thank you
Click to expand...
Click to collapse
International96 said:
Hey Johnny, I figured you've been busy, but I'm still out of service with my Galaxy Player, I'm not sure exactly how to go about using Ubuntu and running Linux. I really appreciate your help thus far, but it's been almost a month and still no luck with the darn device... Maybe it's time to look for a replacement, possibly..
Click to expand...
Click to collapse
I'm sorry guys; I've owned my Galaxy Player 5 since 2011 and I have bricked it several times since then and I have never come across a situation that I could not bring the player back from but, as a (self taught)developer I am pretty good at diagnostic and evaluation procedures. The first step in that is to gather as much information about the problem as possible.
There is a program called heimdall that is like odin but it works on the linux command line that can give more information about what is happening during a flash and it "might" give you a better idea about what is the problem.
The biggest problem that I have run across with this device is that the partition table gets mangled some how and therefore odin does not know where to put data. This can ususally be fixed by flashing a custom kernel like Entropy's Daily Driver and then booting into recovery and using partition tools to carefully reconstruct the table...
Then again, the hardware may actually be damaged...
Meticulus said:
I'm sorry guys; I've owned my Galaxy Player 5 since 2011 and I have bricked it several times since then and I have never come across a situation that I could not bring the player back from but, as a (self taught)developer I am pretty good at diagnostic and evaluation procedures. The first step in that is to gather as much information about the problem as possible.
There is a program called heimdall that is like odin but it works on the linux command line that can give more information about what is happening during a flash and it "might" give you a better idea about what is the problem.
The biggest problem that I have run across with this device is that the partition table gets mangled some how and therefore odin does not know where to put data. This can ususally be fixed by flashing a custom kernel like Entropy's Daily Driver and then booting into recovery and using partition tools to carefully reconstruct the table...
Then again, the hardware may actually be damaged...
Click to expand...
Click to collapse
Sorry for the bump, but as of August I've been enrolled in the Computer Information Systems program at my local technical school, so I've been really busy with that here lately. We're about to learn how to run Linux using VirtualBox for the first time in our Operating Systems Concepts class. I figured I'd let you guys know so I can maybe get somewhere with fixing my GP using Heimdall while running Linux.
I really hope the hardware isn't damaged.
Update: I downloaded VirtualBox on my laptop this past week and was able to successfully install Linux. I just need to install Heimdall using VirtualBox.