This should work in the event you've bricked your device. it should put your device into download mode.
From what i've read, this device will boot into UnBrickable mode by default.
Please try this app i've developed from a Linux computer. it should upload download mode. If it does not, then we can go from there, it may require removing the case and tapping a grounded connection.
Instructions:
You will need:
A linux computer with Java installed
A Windows computer with Odin and Drivers installed
Download the Galaxy Player resurrector onto a Linux computer: http://code.google.com/p/hummingbird-hibl/downloads/list
Launch the Resurrector
Connect device to a powered USB hub connected to a Linux(debian based) computer
observe a picture of a microchip in the resurrector
Select S5PC111 from the dropdown list
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
click the Resurrection button while holding the download mode combination
observe download mode on-screen
unplug the powered USB hub from the Linux computer and move it to a Windows computer
reflash software with Odin
This process will be streamlined in the future.. We are working with two issues that slow things down
Heimdall is not operating on this device currently. This is the reason you must use a Linux and Windows Computer
To speed this proces up, you may use a Virtual Machine inside the Linux
environment to utilize Odin from Windows on the same computer.
The SBL has not yet been modified to directly upload Download Mode
Please leave feedback. I do not own one of these devices, however I am troubleshooting problems with the resurrector as they are reported.
The UnBrickable Resurrector Revision36 contains a modified SBL. If this works properly, you should see this when you plug in a device which is turned off.
Select S5PC111, then click Perform Resurrection. Your device should be in Download Mode. Let me know if this works or not. Also, let me know what's on the screen.
Get the newest Resurrector here: http://hummingbird-hibl.googlecode.com/files/UnBrickableResurrectorR36.jar
AdamOutler said:
No case removal. Just turn it off, plug it in, and it should be able to upload download mode.
Click to expand...
Click to collapse
Sent from my SAMSUNG-SGH-I897 using Tapatalk
[button press] anyway
Begin Resurrection Sequence
Requesting Permission to access device
Please wait.... Uploading..
-------------------------------------------------------------
Hummingbird Interceptor Boot Loader (HIBL) v2.1
Copyright (C) Rebellos 2011
-------------------------------------------------------------
SMDK42XX,S3C64XX USB Download Tool
Version 0.20 (c) 2004,2005,2006 Ben Dooks <[email protected]>
Interceptor Injection Complete. Injecting modified SBL
SMDK42XX,S3C64XX USB Download Tool
Version 0.20 (c) 2004,2005,2006 Ben Dooks <[email protected]>
SBL Injection Failure
failed to find device
Begin Resurrection Sequence
Requesting Permission to access device
Please wait.... Uploading..
-------------------------------------------------------------
Hummingbird Interceptor Boot Loader (HIBL) v2.1
Copyright (C) Rebellos 2011
-------------------------------------------------------------
SMDK42XX,S3C64XX USB Download Tool
Version 0.20 (c) 2004,2005,2006 Ben Dooks <[email protected]>
Interceptor Injection Complete. Injecting modified SBL
SMDK42XX,S3C64XX USB Download Tool
Version 0.20 (c) 2004,2005,2006 Ben Dooks <[email protected]>
SBL Injection Failure
Alright, seriously.... don't post unless you have results. This is a development thread. This is not off topic or general. I subscribe to these threads. I write software. I need testing. I don't need 3 posts relating to your plans of turning your device off, plugging it in, and clicking a button. All I need to know is if it worked or not. If it doesn't work, post the log. If it does work, say it worked. I don't need any more information or pictures. For God sakes... this is a VERY simple task... plug it in, click a button. . I don't need information about kernels, your kids, or people announcing that they're going to plug their God damn device into a computer and click a button... then never do.
Alright. Thank you for adding that information Johnson. Also, thank you to the moderator for cleaning up 2 pages of text.
Unfortunately, the device is not UnBrickable by default, however it does tend to brick into UnBrickable Mode quite frequently. If your device is bricked, When in UnBrickable Mode, the device will appear off, however it will try to connect to Windows. However, you will likely not have the appropriate drivers so the device will try to connect, then turn back off. If you do have the proper drivers, it will connect and the screen will stay black.
When working with any device in a questionable state, it's always best not to trust what's on the screen. Use the UnBrickable Resurrection tool in the following link.
Click here if you have a bricked device: http://forum.xda-developers.com/showthread.php?p=20196008#post20196008
I'm closing this thread as the development work is over. We are only waiting on a complete firmware flash from Samsung. Currently we are missing the following partitions:
RECOVERY
DATAFS
USERFS
GANG
If anyone can help obtaining these partitions, it would be very helpful. Please create a topic here in the Development forum with the raw dumps or put them in TAR format for an Odin Package.
I'm reopening this thread to get more results
I need help getting the following information:
1. Download Terminal Emulator to your Galaxy Player
2. Type the following
Code:
su
mount
3. copy and paste the results of the mount command here.
I know it's not the same output you need, but can be usefull: http://forum.xda-developers.com/showpost.php?p=19700588&postcount=402
This has been done. This is all that's left
2: use market app Terminal Emulator and run the following commands on the device
Code:
su
dd if=/dev/block/mmcblk0p16 of=/mnt/sdcard/data.rfs
dd if=/dev/block/mmcblk0p15 of=/mnt/sdcard/cache.rfs
dd if=/dev/block/mmcblk0p10 of=/mnt/sdcard/efs.rfs
Another method for those of you with Linux or any type of SSH terminal like the windows tool puTTY, is to use an app like SSHDroid then SSH in to your device and copy-paste the code block in.
3: copy the files "data.rfs", "cache.rfs" and "efs.rfs" from your SDCard. put them onto your computer and compress them to save space. They will compress down quite a bit.
4. host them somewhere they can be deleted... a personal mediafire account or PM me for access to my server.
I can make an Odin3 1-Click back-to-stock from there.
Deleted!!!
Problems
I have a samsung galaxy player 5.0 and I try to unbricked by fallowing your tutorial and it detect my device it said:"S5PC110 DETECTED !" and when I hit Perform Resurrection and said:"Failed to write 1310730 bytes" I try using the "Galaxy Player S5PC111 and it didn't work" then I try to use "S5PC110 GALAXY S and it didn't work" Please Help
---------- Post added at 10:34 PM ---------- Previous post was at 10:33 PM ----------
My Model is a YP-G70CWY/XAA galaxy player 5.0
NeoSmart said:
I have a samsung galaxy player 5.0 and I try to unbricked by fallowing your tutorial and it detect my device it said:"S5PC110 DETECTED !" and when I hit Perform Resurrection and said:"Failed to write 1310730 bytes" I try using the "Galaxy Player S5PC111 and it didn't work" then I try to use "S5PC110 GALAXY S and it didn't work" Please Help
---------- Post added at 10:34 PM ---------- Previous post was at 10:33 PM ----------
My Model is a YP-G70CWY/XAA galaxy player 5.0
Click to expand...
Click to collapse
The flash will only work once. If you've clicked the flash button, you must disconnect the device and try again. Also, I know you're using a VM, which is a bad idea, so use bootcamp and boot directly into Ubuntu.
This is what i get ever time i try to unbrick my samsung galaxy player, if there is something i can do to fix this, please help me.
Begin Resurrection Sequence
Requesting Permission to access device
Please wait.... Uploading..
-------------------------------------------------------------
Hummingbird Interceptor Boot Loader (HIBL) v2.1
Copyright (C) Rebellos 2011
-------------------------------------------------------------
SMDK42XX,S3C64XX USB Download Tool
Version 0.20 (c) 2004,2005,2006 Ben Dooks <[email protected]>
Interceptor Injection Complete. Injecting modified SBL
SMDK42XX,S3C64XX USB Download Tool
Version 0.20 (c) 2004,2005,2006 Ben Dooks <[email protected]>
SBL Injection Failure
failed to find devicefailed to find device
Begin Resurrection Sequence
Requesting Permission to access device
Please wait.... Uploading..
-------------------------------------------------------------
Hummingbird Interceptor Boot Loader (HIBL) v2.1
Copyright (C) Rebellos 2011
-------------------------------------------------------------
SMDK42XX,S3C64XX USB Download Tool
Version 0.20 (c) 2004,2005,2006 Ben Dooks <[email protected]>
Interceptor Injection Complete. Injecting modified SBL
SMDK42XX,S3C64XX USB Download Tool
Version 0.20 (c) 2004,2005,2006 Ben Dooks <[email protected]>
SBL Injection Failure
failed to find devicefailed to find device
Begin Resurrection Sequence
Requesting Permission to access device
Please wait.... Uploading..
-------------------------------------------------------------
Hummingbird Interceptor Boot Loader (HIBL) v2.1
Copyright (C) Rebellos 2011
-------------------------------------------------------------
SMDK42XX,S3C64XX USB Download Tool
Version 0.20 (c) 2004,2005,2006 Ben Dooks <[email protected]>
Interceptor Injection Complete. Injecting modified SBL
SMDK42XX,S3C64XX USB Download Tool
Version 0.20 (c) 2004,2005,2006 Ben Dooks <[email protected]>
SBL Injection Failure
failed to find devicefailed to find device
Sometimes it does that to me and I just keep trying 'till it works. Make sure you have the correct device selected too.
Related
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Introduction:
After months of research and development, both hardware and software... I'm happy to announce UnBrickable Mod is a matter of modifing your phone once, with a single small wire. From that point on, you can click a button to unbrick. This can even be applied to a phone which is already bricked.
This video applies, but on the Fascinate, you must hold the POWER button during the entire flashing sequence.
Instructions
You Must have UnBrickable Mod applied to your device. If you're not sure, run this tool under Linux: http://forum.xda-developers.com/showthread.php?t=1257434
This currently only works for Linux based computers or Windows based computers with proper drivers installed, with a Linux Virtual Machine, Get Ubuntu here: http://www.ubuntu.com , Get Virtualbox Here: http://www.virtualbox.org/wiki/Downloads
You must have Java installed on your computer: http://www.java.com/en/download/
Unbricking:
1. Apply UnBrickable Mod to your device: http://forum.xda-developers.com/showthread.php?t=1288093
2. Run ModeDetect to verify your phone is in the proper mode: http://forum.xda-developers.com/showthread.php?t=1257434
You should see this while you hold the power button:
3. Run UnBrickable Resurrector: http://forum.xda-developers.com/attachment.php?attachmentid=710199&stc=1&d=1315173984 This will only work on linux currently. Install Linux or dual boot if you have windows.
If you are still holding the power button, you should see this on Mode Detect.
You can now disconnect your phone and move to a windows computer to use Odin or any other Samsung tool, or use Heimdall One-Click from Linux. Keep holding the power button!
4. Run Heimdall One-Click: http://forum.xda-developers.com/showthread.php?t=1288130 (or odin3 one-click),
5. repeat steps 2 and 3 with bootloader flashing enabled (Heimdall One-Click has a safety mechanism which requires you to flash once before flashing bootloaders).
conclusion
You've unbricked the unbrickable Fascinate.. This should not have been difficult. If it was, you should learn teh computer better... Really. And with that said, I'm happy to announce that you no longer have to flash with a fear of bricking.
HIBL
The HIBL is the key to resurrecting a S5PC110 based processor. I'm going to let Rebellos explain the inner workings of the Hummingbird Interceptor Bootloader. It's really quite amazing. While my work is more hardware and high level tasks like making things into one-clicks, Rebellos' work involves reverse software engineering, assembly language, and more...
Tools
Windows32 command line app and drivers http://forum.xda-developers.com/attachment.php?attachmentid=709292&stc=1&d=1315091523
Linux one-click Resurrector: http://forum.xda-developers.com/attachment.php?attachmentid=705515&stc=1&d=1315091523
4SEP11: added 32 bit, miscellanious impovements to visuals
6SEP11: removed additional commands
Okay, so, what is Hummingbird Interceptor Boot Loader (HIBL)?
Basically: It allows to load any amount of data (limited by size of RAM block, the biggest one single block available is 256MB) through USB connection with PC under any specified address into memory and then execute it. This can be fastboot Bootloader+OS image for example.
Technically: It does consist of 2 pieces fused together - BL1_stage1 and BL1_stage2.
Each stage starts from 16bytes (4 ARM WORDs) of secure boot header. In stage1 these are mandatory, in stage2 they can be random (nulled them in my code), so EntryPoint of each stage does start at its 0x10 offset.
BL1_stage1, loaded under 0xD0020000 address, is short code, digitally signed by Samsung. It has been released to break "Chain of Trust" and alter Secure Boot into Non-Secure Boot process. Literally stage1 just do some compare operations and then jumpout to BL1_stage2. (Yes, I also see no point of releasing hardware secured CPU version together with software which is bypassing it's security)
BL1_stage2, must be placed at 0xD0022000 address (it's fused together with stage1 into HIBL, so it's at 0x2000 offset of HIBL.bin) it is unsigned because Secure Boot Context, prepared by iROM (BL0) has been already ignored by stage1.
Its FASM_ARM sourcecode:
http://code.google.com/p/hummingbir...unk/HummingBirdInterceptorBootloader/HIBL.ASM
This is where the code start real work, it does begin with standard ARM core jump vector table (just to keep stick to standard, these aren't used anyway).
1. It does use I9000 BL1_stage2 functions (init_system) which I linked to it, these are used to init DMC controllers, as to this point code is executing in and working with very tiny, 96KB iRAM space, after calling this function it turns all 512MB of RAM available.
2. Make sure DMC is configured properly (write some value to address 0x40~~ memory space, then read it and compare with previously written)
3. Reinit iRAM heap to the BL0 initial state (to convince it USB dload mode haven't been called yet), by storing and restoring UART pointer only (to keep debug output flowing properly)
4. Call iROM usb_downloader function.
5. Read the address where downloaded data has been placed.
6. Jump into this address.
This, properly used provides similiar debug output (similiar, because its outdated testlog)
������������������������������������������������������������������������
Uart negotiation Error
----------------------------------------
Hummingbird Interceptor Boot Loader (HIBL) v1.0
Copyright (C) Rebellos 2011
----------------------------------------
Calling IBL Stage2
DONE!
Testing BL3 area
DONE!
iRAM reinit
DONE!
Please prepare USB dltool with BL3
Starting download...
0x00000000
Desired BL3 EP: 0x40244000
Download complete, hold download mode key combination.
Starting BL3...
//OUTPUT BELOW IS COMING FROM SBL
Set cpu clk. from 400MHz to 800MHz.
IROM e-fused - Non Secure Boot Version.
Click to expand...
Click to collapse
It opens infinite capabilities. Instead of SBL to unbrick, Uboot can be loaded, or any armlinux kernel. It's all up to you - XDA Developers.
Will a Wubi install of linux work? Certain windows programs prevent me from making the jump to linux again. Though I wish i could.
mentose457 said:
Will a Wubi install of linux work? Certain windows programs prevent me from making the jump to linux again. Though I wish i could.
Click to expand...
Click to collapse
Yes. You can use WUBI. That is the same as normal "side-by-side" or "dual boot" installation of Ubuntu but you can delete Ubuntu from within Windows.
Note: The hardware mod must be performed first in order to use the set of software above
I was informed last night that this is the ONLY recovery method available for the Fascinate. If you've got a dead brick, you have no other options at this time other then sending it to the manufacturer for a replacement.
So I just got this phone today. I noticed Cyanogenmod 7 Supports this device and they have a stable build. Was like hearing My b-day was tomorrow. I got excited and started reading the Full update Guide just to see if some steps might be different then the Vibrant and Galaxly S 4G. I wasn't going to worry about a backing it up because simply.....this is a brand new phone just taken out of the box. There was nothing to backup, however there's allot I'd like taken off (Bloat)
The following steps are what I have completed:
Green = Steps I've done.
Red = Steps I haven't done.
Installing the ClockworkMod Recovery
If the Samsung Galaxy S II already has the ClockworkMod Recovery installed, skip this section.
Warning: Installing a custom recovery image on the Samsung Galaxy S II will void the warranty.
Download codeworkx's kernel with the ClockworkMod Recovery and the Heimdall Suite:
codeworkx's Kernel with the ClockworkMod Recovery 4.0.1.4: Download
md5: xxx
Windows:
Heimdall Suite 1.3.1: Download
NOTE: The Heimdall Suite requires the Microsoft Visual C++ 2010 Redistributable Package installed on the computer, which can be downloaded here.
Ubuntu 32bit:
Heimdall Suite 1.3.1 Command-line Binary: Download
Ubuntu 64bit:
Heimdall Suite 1.3.1 Command-line Binary: Download
Mac OS X:
Heimdall Suite 1.3.1: Download
NOTE: The source code for the Heimdall Suite is available on Github.
Windows ONLY:
Power off the Samsung Galaxy S II and connect the microUSB to the computer but not the Samsung Galaxy S II.
Boot the Samsung Galaxy S II into download mode by holding down Home & Volume Down while connecting the microUSB to it.
Run the included zadig.exe in the drivers folder of the Heimdall Suite.
From the menu, choose Options » List All Devices.
From the drop down, select Samsung USB Composite Device or Gadget Serial.
Click Install Driver.
NOTE: A prompt may appear warning that the installer is unable to verify the publisher of the driver. Ignore it and select "Install this driver anyway."
Heimdall can now be used safely on the Windows computer.
NOTE: For more information about the Heimdall Suite, please read the included README.txt.
Power off the Samsung Galaxy S II and connect the microUSB to the computer but not the Samsung Galaxy S II.
Boot the Samsung Galaxy S II into download mode by holding down Home & Volume Down while connecting the microUSB to it.
Untar codeworkx's kernel into the Heimdall directory.
On the computer, open terminal and run the following command from the Heimdall directory:
heimdall flash --kernel zImage
A blue transfer bar will appear on the phone showing the kernel being transferred. The device will reboot automatically.
The Samsung Galaxy S II now has the ClockworkMod Recovery installed. Continue to the next section.
======================================================================================
The phone then went into download mode, while in download mode it changed to this...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Now This is where I stand:
Cannot boot into Recovery
Cannot boot into Download Mode
Cannot flash anything using Odin
No button combo's help get into anything
Phone will not boot normaly
The only 2 things I have yet to try:
A MicroUSB Jig (Which is in the mail as I type this)
A ROM that could possibly be loaded using Heimdall
What is a brother to do!!
Really? No one has anything to say? Not even a "send it back" OR "your screwed" type of reply..... Alllllllright. I'ma just buy a new one then.
Sharpie603 said:
So I just got this phone today. I noticed Cyanogenmod 7 Supports this device and they have a stable build. Was like hearing My b-day was tomorrow. I got excited and started reading the Full update Guide just to see if some steps might be different then the Vibrant and Galaxly S 4G. I wasn't going to worry about a backing it up because simply.....this is a brand new phone just taken out of the box. There was nothing to backup, however there's allot I'd like taken off (Bloat)
The following steps are what I have completed:
Green = Steps I've done.
Red = Steps I haven't done.
Installing the ClockworkMod Recovery
If the Samsung Galaxy S II already has the ClockworkMod Recovery installed, skip this section.
Warning: Installing a custom recovery image on the Samsung Galaxy S II will void the warranty.
Download codeworkx's kernel with the ClockworkMod Recovery and the Heimdall Suite:
codeworkx's Kernel with the ClockworkMod Recovery 4.0.1.4: Download
md5: xxx
Windows:
Heimdall Suite 1.3.1: Download
NOTE: The Heimdall Suite requires the Microsoft Visual C++ 2010 Redistributable Package installed on the computer, which can be downloaded here.
Ubuntu 32bit:
Heimdall Suite 1.3.1 Command-line Binary: Download
Ubuntu 64bit:
Heimdall Suite 1.3.1 Command-line Binary: Download
Mac OS X:
Heimdall Suite 1.3.1: Download
NOTE: The source code for the Heimdall Suite is available on Github.
Windows ONLY:
Power off the Samsung Galaxy S II and connect the microUSB to the computer but not the Samsung Galaxy S II.
Boot the Samsung Galaxy S II into download mode by holding down Home & Volume Down while connecting the microUSB to it.
Run the included zadig.exe in the drivers folder of the Heimdall Suite.
From the menu, choose Options » List All Devices.
From the drop down, select Samsung USB Composite Device or Gadget Serial.
Click Install Driver.
NOTE: A prompt may appear warning that the installer is unable to verify the publisher of the driver. Ignore it and select "Install this driver anyway."
Heimdall can now be used safely on the Windows computer.
NOTE: For more information about the Heimdall Suite, please read the included README.txt.
Power off the Samsung Galaxy S II and connect the microUSB to the computer but not the Samsung Galaxy S II.
Boot the Samsung Galaxy S II into download mode by holding down Home & Volume Down while connecting the microUSB to it.
Untar codeworkx's kernel into the Heimdall directory.
On the computer, open terminal and run the following command from the Heimdall directory:
heimdall flash --kernel zImage
A blue transfer bar will appear on the phone showing the kernel being transferred. The device will reboot automatically.
The Samsung Galaxy S II now has the ClockworkMod Recovery installed. Continue to the next section.
======================================================================================
The phone then went into download mode, while in download mode it changed to this...
Now This is where I stand:
Cannot boot into Recovery
Cannot boot into Download Mode
Cannot flash anything using Odin
No button combo's help get into anything
Phone will not boot normaly
The only 2 things I have yet to try:
A MicroUSB Jig (Which is in the mail as I type this)
A ROM that could possibly be loaded using Heimdall
What is a brother to do!!
Click to expand...
Click to collapse
Are you sure that your phone is a SGS2 (GT-I9100)?
I can not recognize much similarity with my SGS2 with the one on your picture.
If CWM recovery mode is still working, you can try to flash a Custom ROM as zip file from your internal SD card.
If not ... hmm ... ever tried to make an emergency recovery using KIES?
Please post your question in CyanogenMod thread !
Good luck to find an alternative for bringing your phone back to the shop and buying a new one.
Its a Samsung Galaxy S II (T989) Its the USA model.
And there is no custom recovery installed on this what so ever.
Never had a custom rom installed
Never installed a custom recovery
Never even got to turn it on from out of the box.
How do I go about an emergency recovery using Kies?
Your phone is not the international Samsung Galaxy SII! This forum is for GT-I9100, I think yours is AT&T or other version, something like GT-I9103(not sure). Search the forum, you're in the wrong forum for sure.
The 9100 has a hardware home button, I don't see any on yours.
Mine is the T989
then to be honest dude youve ****ed up. Youve tried installing something from a totally different model because you didnt check the model numbers. You dont have a i9100 phone, its totally different
your phone forum is here http://forum.xda-developers.com/forumdisplay.php?f=1329
I didnt install anything. I plugged the phone into the charger and this is what it did. Right from taking it out of the box
MOD please delete this post, I have reposted in the correct thread.
Hi guys, I wanted to try this database system, so I'm expanding upon this thread: http://forum.xda-developers.com/showthread.php?t=2272066
Introduction
CASUAL will guide you through the process. Put your device into “Developer Mode>USB Debugging”. Click the do it button. If you experience a problem, PLEASE USE THE PASTEBIN button to post a log. Just press Ctrl+L then Pastebin and fill out the information.
Overview
You are expected to be STOCK.... Stock anything, but stock. If you are not stock and have a custom recovery, this will cause you to only be able to flash back to stock using Odin or Heimdall. Be stock. You will need to download and execute the CASUAL application below. Then click the Do It! button. You need Java. Do you have Java?. The exploit was developed by Elite Recognized Developer Ralekdev and packaged by AdamOutler.
note: if it fails, try turning everything off and back on, then run it again before posting for help.
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. 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:
Code:
sudo apt-get install openjdk-7-jdk dpkg
Mac Users: Mac works easier than any other system at the time of this systems. Please report problems.
Download
CASUALnightly No You Verizon! Always use the highest revision with the latest date. To run CASUAL you need Java. Do you have Java?
For nightly builds click here: http://goo.im/devs/AdamOutler/VZWGalaxyNote2
Help and Troubleshooting
Are you having a problem? First check this post out for remedial troubleshooting. . If that doesn't fix it, then press CTRL+L, press the Pastebin button, come back here and press CTRL+V to paste your log. Don't hit the donate button, that doesn't fix it. Donate only if you feel it's worth donating to. Use CTRL+L and then hit Pastebin and paste the log here if you need help.
Jailbreak video for Windows users only!
This video desmonstrates CASUAL used with Odin to flash the Galaxy Note 2 firmware. Thanks to DroidModderX. While the video uses an old version the procedure is mostly the same.
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. While the video uses an old version, the procedure is mostly the same.
image
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
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.
31July13: initial release
XDA:DevDB Information
CASUAL- NO You Verizon, a Tool/Utility for the Verizon Samsung Galaxy Note II
Contributors
AdamOutler, jrloper, loglud
Version Information
Status: Testing
Current Beta Version: No You Veriz
Beta Release Date: 2013-07-31
Created 2013-07-31
Last Updated 2013-08-02
Very nice work
MY DIRTY LIL NOTE 2
couldnt get the latest nightly to fully load. recog device connection but the do it wouldnt work because the top of the app stayed on loading... please wait.
edit: diff build shows the top, but says disconnected on the bottom. fml
all the videos say to use windows 7. can it work with vista?
master0fursinz said:
all the videos say to use windows 7. can it work with vista?
Click to expand...
Click to collapse
yeah, it should work with Vista. @jrloper could tell you more if there are driver issues.
idkwhothatis123 said:
couldnt get the latest nightly to fully load. recog device connection but the do it wouldnt work because the top of the app stayed on loading... please wait.
edit: diff build shows the top, but says disconnected on the bottom. fml
Click to expand...
Click to collapse
I'm also having this problem. Any help Adam?
Edit: This is what you're looking for http://forum.xda-developers.com/showthread.php?t=2272066
Hi,
I'm currently running Windows 8.1 64 bit and my phone is the Samsung Galaxy Note II android version 4.1.2 stock, model SCH-i605, and baseband version i605vramc3. After downloaded the latest nightly build, the .jar file opened and gave the following error in the application:
There was a problem while excuting the command.
C:\Users\Zack\AppData\Local\Temp\CASUALZack-2013-12-26-17.09.35\adbexe devices
Then it repeated this same error every second or so infinitely until the application was closed. It did this whether the phone was connected, disconnected, in USB debugging mode, in download mode, etc. I have tried everything and I continually get this same error with the "Do It' button greyed out and disabled.
Next I downloaded the previous two builds, and I found that the December 13 build did not get this error and actually found my phone. However, after I clicked "Do It" and confirmed the warning, It rebooted my phone into download mode like it is supposed to. My phone then went into download mode like usual. However, the CASUAL program then said:
looking for download mode devices..........................................................
And kept on looking without ever finding my phone, and every minute or so it came up with a prompt asking why it can't find my device. I also found that my phone would not exit this download mode without doing a battery pull.
Next I retried the entire process with both builds using (a) 3 different USB cords, (b) 3 different computers running windows 8.0 and 7, and (c)every possible USB port on each computer. These options all gave the same exact results.
I have tried everything I can think of but it is not working! Has anyone encountered this problem before or do you have any proposed solutions?
Thanks so much!
Zack
Still can't figure it out.
http://pastebin.com/W3W1HwJi
I keep getting a libusb error -12 at the start and then it ends up failing.
Really need help here. Verizon was trying to force update me and I had to turn it off and go back to my old phone till I can get this done.
Thank you Adam!!
BrickeD?
Hi guys.
I am certain I followed all instructions to the letter, but I have ended up rendering my Note 2 pretty much useless. CAUSAL informed that the device would be started in android but then the next thing my phone displayed was:
"System software not authorized by Verizon Wireless has been found on your phone. Please turn off your phone and go to the nearest Verizon Wireless store for help."
Can I restore my device to the previous state?
thanks
Tried the second time around with CASUAL R570 and got error.
http://pastebin.com/Gpss6vtZ
UPDATE: Gave up hopes (for now) of rooting SCH-i605 running KitKat. Flashed stock rom and revived the device.
Spy26 said:
Tried the second time around with CASUAL R570 and got error.
http://pastebin.com/Gpss6vtZ
UPDATE: Gave up hopes (for now) of rooting SCH-i605 running KitKat. Flashed stock rom and revived the device.
Click to expand...
Click to collapse
There isn't a root method for ND7 4.4.2. for the i605. Also, the bootloader hasn't been able to be unlocked since MJ9 4.3.
mirror
Hosed my phone... infinite bootloop at sammy logo, couldn't get into recovery had to odin a stock image and start over... Had one hell of a time tracking down the casual jar file.
As of this moment the download link in this thread is bad.
the download link in THIS thread, now points to DevHost but the files are not the ~29MB jar file you expect. It is now a 3.5MB exe file that appears to be "shady as hell". All the other download decoy buttons at Dev-host take you to fake java update downloads and other seriously shady looking corners of the interweb.
Additionally goo.im is on holiday...
As such I have posted this temporary Mirror of the .jar file I had in my archives:
http://tweakedrom.com/Other_Files/Note_2.php
(The jar file MD5 appears to be the same as one the developer posted to Dev-Host.)
Outler, if you want me to take this mirror down just let me know.
Cannot find the download to casual sch-i605. All download links I can find lead to nowhere.
mjmplus said:
Cannot find the download to casual sch-i605. All download links I can find lead to nowhere.
Click to expand...
Click to collapse
Well you could go to his very own YouTube video and use the links there
If you want to repost this guide to other websites, please let me know before you repost.
For Chinese users: 中文版教程将会在dospy发布。
Click to expand...
Click to collapse
So after you unlock the bootloader successfully, you definitely want to install custom ROM, or at least root the phone, right?
Here's the guide about rooting Nokia 3.2 / 4.2.
This guide could probably work on Nokia 6.2 / 7.2 in the future.
Step 1: Unlock the bootloader
https://forum.xda-developers.com/nokia-4-2/how-to/guide-how-to-unlock-bootloader-nokia-4-2-t3962402
For Nokia 3.2, you'll need to read this as well: https://forum.xda-developers.com/nokia-3-2/how-to/guide-how-to-trigger-nokia-3-2-to-edl-t3962841
Step 2: Acknowledge current slot
You have two methods.
Method 1: After USB debugging enabled, execute this command:
Code:
adb shell getprop ro.boot.slot_suffix
Method 2: Under fastboot mode, execute this command:
Code:
fastboot getvar current-slot
We assume the current slot is b.
Step 3: Trigger the phone to EDL mode again
There's a hidden command in aboot known as "fastboot reboot-emergency".
However, normal fastboot binary doesn't have that command at all, so we need to compile a binary or hack the binary.
For Windows users, I've provided the fastboot binary that can use this command, and I renamed it to edl-fastboot.exe. You can download it on the attachment below.
For macOS/Linux distro users, I'm afraid you have to fork the source code, edit related content and compile yourself.
So with this special version of fastboot binary, we can boot the phone to EDL mode directly:
Code:
edl-fastboot.exe reboot-emergency
But wait, why didn't you mention this command when you released bootloader unlock guide?
That's because, if you attempt to use this command under locked bootloader, bootloader will response "Permission denied, auth needed. " and refuse to proceed the command.
I don't know how the authentication is done yet, but it's definitely not something that average developers can access to.
Click to expand...
Click to collapse
Step 4: Use partition manager to dump the partition
If you've came so far when unlocking the bootloader, you have already know the great partition manager.
Still, we assume the COM port number is 8 (COM8).
When the partition list appears, find "boot_b" (or boot_a if the current slot is a), right click on it, choose "Manage Partition Data" and click "Read Data". Then fh_loader binary will dump the boot image to your PC.
For Windows users, it's located at
Code:
%AppData%\Qualcomm\QFIL\COMPORT_8
Where %AppData% is actually C:\Users\your_user_name\AppData\Roaming .
The filename looks like this: ReadData_emmc_Lun0_0x3a000_Len65536_DT_07_09_2019_13_55_54.bin
Now close the partition manager, your phone will exit EDL mode and boot normally.
If you're interested in dumping full eMMC storage, you may want to read this: https://forum.xda-developers.com/android/general/guide-how-to-dump-write-storage-t3949588
Step 5: Install Magisk Manager and patch the boot image you dumped
I think everyone who reading this guide knows where to download Magisk Manager.
Copy the boot image you dumped with QFIL to Download directory in your phone's internal storage, and rename it to boot.img for your convenience.
In case you don't know how to patch, read this guide: https://topjohnwu.github.io/Magisk/install.html#boot-image-patching
Step 6: Flash patched boot image and reinstall Magisk for ensurance
After you pulled patched boot image from your phone, reboot your phone to fastboot mode, then execute these commands:
Code:
fastboot flash boot magisk_patched.img
fastboot reboot
Note, temporarily boot method introduced back for old A/B devices like Nokia 7 Plus no longer works on Nokia 3.2 / 4.2 - it will boot your phone to Qualcomm 900E mode.
Once your phone booted to normal OS, open Magisk Manager, and reinstall Magisk and required runtime to make the root much more effective.
You may want to read this guide if you want to inherit root along with OTA update: https://topjohnwu.github.io/Magisk/tutorials.html#ota-installation
Extra info about custom rom:
I've tested PHH-Treble GSI on Nokia 4.2 and it made me disappointed.
The vendor compatibility is worse than FIH made Android Phones.
You may want to read this for more details: https://github.com/phhusson/treble_experimentations/wiki/Nokia-4.2
Next preview: Stock firmware reinstallation guide. Note, Nokia 3.2 / 4.2 are not made by FIH, so OST LA no longer works on both devices.
Special thanks:
@topjohnwu for Magisk
Wingtech for leaking prototype units
Reserved
not detected
my pc doesn't detect the phone when its in edl mode. before people start asking I unlocked the bootloader by enabling oem unlock in the phone settings.
I have a TA-1156 (a 3.2 variant) that has a different mainboard layout. For quite a while, I tried in vain to bring it into EDL mode - until I just tried the fastboot command "flash unlock" which worked.
I guess I should have tried that right away as I did have the OEM unlocking option in the developer setup.
Anyway, now I'm unlocked but can't access the partitions with the QFIL partition manager. I suspect the phone expects a different programmer than prog_emmc_firehose_8937_ddr.
I can enter EDL mode easily now with the patched fastboot exe. The correct driver is active and QFIL detects the phone. However, as soon as I follow the instructions by setting the programmer, and then try to start the partition manager, the phone stops responding.
After a while, I get a "sahara" error about no reply from the phone.
I wonder if someone has a stock boot.img of the Nokia 3.2 (build 00EEA) lying around ...
Here is someone else's photo of the mainboard (I just realized that it's actually from hikari_calyx!) but on mine, the right one of the test points you marked in your 3.2 variant does not exist, so I edited it out in the photo:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
JFDee said:
Anyway, now I'm unlocked but can't access the partitions with the QFIL partition manager. I suspect the phone expects a different programmer than prog_emmc_firehose_8937_ddr.
Click to expand...
Click to collapse
My guess was right. Now I'm able to reply to myself with a solution.
I tried a different prog_emmc_firehose_8937_ddr than the one provided by @hikari_calyx in the unlock thread
There is a programmer with the same name in this firmware:
sprout-015B-0-00WW-B01 .rar
It's provided by @bouyhy01 in his rooting thread.
The size of the programmer file is slightly different:
Code:
hikari_calyx: 428,936 bytes
Firmware: 428,944 bytes
Long story short: the different programmer worked in QFIL, so the partition manager worked as well, I got my own boot image, patched, flashed and had root - finally ... Thanks for all the research work, hikari_calyx and bouyhy01 !
Attached is the working programmer file, in case anyone else stumbles upon the same problem. By the way, my phone has the October security patch installed which is currently the latest available.
View attachment prog_emmc_firehose_8937_ddr_from_fw.zip
.
JFDee said:
Here is someone else's photo of the mainboard (I just realized that it's actually from hikari_calyx!) but on mine, the right one of the test points you marked in your 3.2 variant does not exist, so I edited it out in the photo:
View attachment 4867461
Click to expand...
Click to collapse
I guess the only point can be connected to the ground, for example, the RF shield is grounded.
JFDee said:
Attached is the working programmer file, in case anyone else stumbles upon the same problem. By the way, my phone has the October security patch installed which is currently the latest available.
View attachment 4869373
.
Click to expand...
Click to collapse
Thanks for info. Mine Nokia 3.2 is a prototype unit, so I don't know the situation of other versions of Nokia 3.2.
Hello, I have tried this manual for rooting Nokia 4.2 with last security update of 5th of November. After 5 step (flashing patched boot image) my phone try to reboot and then asked for factory reset (Can't load android system - Your data may be corrupt). After making factory reset there were no root at all.
What can i do next ?
PS. It's strange enough when i download boot_b image it was 63.4 Mb snd when i have patched it by Magisk manager - the size od magisk_patched.img became 10.2 Mb
My dear users,
As soon as I ran TronScript (r/tronscript) with the auto restart option, I received a message stating that Windows could not boot. After loading Hiren's Boot CD into my Ventoy drive, it now says "Your PC could not start properly" with error code 0x0000001.
The following are the contents of my Ventoy drive:
A boot CD for Hiren is included,
This is HP.
Windows 11 Installation media.
I would appreciate any help you could provide to fix my computer as soon as possible.
woodalexa7878 said:
My dear users,
As soon as I ran TronScript (r/tronscript) with the auto restart option, I received a message stating that Windows could not boot. After loading Hiren's Boot CD into my Ventoy drive, it now says "Your PC could not start properly" with error code 0x0000001.
The following are the contents of my Ventoy drive:
A boot CD for Hiren is included,
This is HP.
Windows 11 Installation media.
I would appreciate any help you could provide to fix my computer as soon as possible.
Click to expand...
Click to collapse
Run Startup Repair from a recovery disc. If you do not have a recovery disc, you can use installation media.
By means of RUFUS create a bootable USB-stick containing the Windows version / edition you want to have installed and boot from USB-stick created to install it.
Since you have Ventoy, you could try booting from the Hiren live CD and try to download a fresh copy of Win11 over wayback (if your pc has nothing of important in it), even tho firsthand it could be better to get another spare usb stick and flash Ventoy on it all over again and then paste the win11 iso file over the brand new usb stick.
In case there's personal data you'd like to save over the C:/ drive, using any linux live usb iso could be of help on mounting the partition and save whatever you could find on another removable media.
Wondering why Hiren’s BootCD PE (Preinstallation Environment) should get used: it's based on Windows 10 PE x64. There are no official updates after November 2012.
xXx yYy said:
Wondering why Hiren’s BootCD PE (Preinstallation Environment) should get used: it's based on Windows 10 PE x64. There are no official updates after November 2012.
Click to expand...
Click to collapse
2021 ..
https://www.hirensbootcd.org/files/HBCD_PE_x64.iso
xXx yYy said:
Wondering why Hiren’s BootCD PE (Preinstallation Environment) should get used: it's based on Windows 10 PE x64. There are no official updates after November 2012.
Click to expand...
Click to collapse
If that won't go (also, disregarding the whole update cycle...i'm sure 2012 wasn't even the date of release for win10, let alone a forked version), then a linux live usb iso should directly be of help.
Updates, EOLs versions, and whatever stay out of the question since here it's about restoring a pc to it's former state.
Since it's all a matter to use the ruined machine's specs as a host for running a live iso and grab a win11 iso off the internet and drag it on another usb flash drive (with Ventoy installed aswell):
then what matters is that the machine gets saved and that win11 gets restored back.
IMO it never does make sense to make use of a Windows Recovery Environment ( WinRE ) - what Hiren's PE by nature is - to repair a corrupted Windows OS, because user most times doesn't know 1. what the error code reported by Windows means - as that's the case here, and 2. what 3rd-party app of those dozens that came bundled with Hiren's PE ( see here: https://www.hirensbootcd.org/hbcd-v120/ ) lastly to use to fix the given problem : Re-installing Windows OS from the scratch is the only time-saving method I know of to immediately have a properly running Windows machine. And this is correctly done by a Windows Preinstallation Environment ( WinPE ) what supports these features
Batch files and scripts, including support for Windows Script Host (WSH), and ActiveX Data Objects (ADO), and optional support for PowerShell.
Applications, including Win32 application programming interfaces (APIs) and optional support for HTML Applications (HTA).
Drivers, including a generic set of drivers that can run networking, graphics, and mass storage devices.
Image capturing and servicing, including Deployment Image Servicing and Management (DISM).
Networking, including connecting to file servers using TCP/IP and NetBIOS over TCP/IP via LAN.
Storage, including NTFS, DiskPart, and BCDBoot.
Security tools, including optional support for BitLocker and the Trusted Platform Module (TPM), Secure Boot, and other tools.
Hyper-V, including VHD files, mouse integration, mass storage and network drivers that allow Windows PE to run in a hypervisor.
and more aren't in fact needed.
Better going straight to the point and reinstall win11 fresh (like i mentioned before) since the message given by OP's machine just went:
"Your PC could not start properly"
Since OP did mention it has a "Windows 11 Installation media" inside their Ventoy stick, they could try to solve it that way by doing the whole booting process again.
If the Installation Media won't go, then it's better taking a win11 .iso on the go (of course, again, using a spare usb. Would spare making this message longer).
Xploit Machine said:
2021 ..
https://www.hirensbootcd.org/files/HBCD_PE_x64.iso
Click to expand...
Click to collapse
As I can see the versions 2012 and/or 2021 - you linked to - differ only in amount of bundled 3rd-party progs ( mostly freeware ). But this wasn't the point.
Hello,
As soon as I also ran TronScript (r/tronscript) with the auto restart option, I received a message stating that Windows could not boot. After loading Hiren's Boot CD into my Ventoy drive, it now says "Your PC could not start properly" with error code 0x00001.
Error code 0x00001 ( 0x0000001 ? ) usually occurs when Windows PC users attempt to update or install a Windows OS on their devices. Make use of the Windows built-in System File Checker function to deal with your issue.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}