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.
Related
Hello Ace users.
Just figured I would post this in case anyone else out there was thinking about the 2.3.6 update for Nordic counties. I just spent the morning Flashing it VIA Odin, because I never made a Factory back-up before flashing CM7 some time ago, and I am quite happy with it.
Okay, here's the procedure on how to manually upgrade the Samsung Galaxy Ace GT-S5830 to Android 2.3.6 Gingerbread using the stock ROM S5830XXKPP in 11 simple steps. So you know Android 2.3.6 Gingerbread is not yet available for all Galaxy Ace users, except in Russia. Don’t be scared when the phone boots in Russian, you can change that in the locale and text option under settings.
Here’s what you need:
Download the stock ROM S5830XXKPP, I got mine from SamMobile.com. You have to create a free account and navigate a few confusing pages but it can be found. You’ll find it at the bottom of the ROM list for the Ace; it’s the one for Nordic countries.
Grab the ODIN Multi Downloader v4.38 and OPS File: Cooper_v1.0.ops
To Flash with Odin:
- For Windows PC’s with USB driver / Kies installed.
- A USB cable for your phone
- Make a back-up copy of all important files stored on your phone, you are going to lose everything otherwise
Ready to start?
1. Download the S5830XXKPP ROM and extract it to your desktop. The password is “samfirmware.com”. When extracted you’ll see: “S5830XXKPP_S5830XXKPP_S5830SERKPP_HOME.tar.md5” this is what you need.
2. Extract and run Odin v4.38 on your desktop.
3. On ODIN click the OPS button and select the Cooper_v1.0.ops file on it.
4. Hit the One package checkbox option
5. Select and load the S5830XXKPP_S5830XXKPP_S5830SERKPP_HOME.tar.md5 in the One package field
6. Set the Samsung Galaxy Ace in Download Mode:
Turn the OFF the phone then press Volume Down+Power+ Middle buttons simultaneously and the phone will then reboot into download mode. Press the volume up button to begin download mode.
7. Connect the phone to PC and you’ll see on ODIN a window with “COM Port” turn to yellow. It means connected and ready.
8. Begin the flashing by hitting the 'Start' button.
9. It will take 5 minutes to complete and the word "PASS" will display once it finishes.
10. Unplug the phone from the PC, and go into Recovery Mode by pressing Home + Power Button, then select Wipe Data / Factory Reset. Reboot Phone.
11. Last, change the default Russian language to your Region by going to settings and then locate the locale and text icon, then pick your native language.
{
"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"
}
I am not responsible if you break your phone, this is for educational purposes only.
Thanks to Droid Angel for help with the TUT.
-SGA- said:
Hello Ace users.
Just figured I would post this in case anyone else out there was thinking about the 2.3.6 update for Nordic counties. I just spent the morning Flashing it VIA Odin, because I never made a Factory back-up before flashing CM7 some time ago, and I am quite happy with it.
Okay, here's the procedure on how to manually upgrade the Samsung Galaxy Ace GT-S5830 to Android 2.3.6 Gingerbread using the stock ROM S5830XXKPP in 11 simple steps. So you know Android 2.3.6 Gingerbread is not yet available for all Galaxy Ace users, except in Russia. Don’t be scared when the phone boots in Russian, you can change that in the locale and text option under settings.
Here’s what you need:
Download the stock ROM S5830XXKPP, I got mine from SamMobile.com. You have to create a free account and navigate a few confusing pages but it can be found. You’ll find it at the bottom of the ROM list for the Ace; it’s the one for Nordic countries.
Grab the ODIN Multi Downloader v4.38 and OPS File: Cooper_v1.0.ops
To Flash with Odin:
- For Windows PC’s with USB driver / Kies installed.
- A USB cable for your phone
- Make a back-up copy of all important files stored on your phone, you are going to lose everything otherwise
Ready to start?
1. Download the S5830XXKPP ROM and extract it to your desktop. The password is “samfirmware.com”. When extracted you’ll see: “S5830XXKPP_S5830XXKPP_S5830SERKPP_HOME.tar.md5” this is what you need.
2. Extract and run Odin v4.38 on your desktop.
3. On ODIN click the OPS button and select the Cooper_v1.0.ops file on it.
4. Hit the One package checkbox option
5. Select and load the S5830XXKPP_S5830XXKPP_S5830SERKPP_HOME.tar.md5 in the One package field
6. Set the Samsung Galaxy Ace in Download Mode:
Turn the OFF the phone then press Volume Down+Power+ Middle buttons simultaneously and the phone will then reboot into download mode. Press the volume up button to begin download mode.
7. Connect the phone to PC and you’ll see on ODIN a window with “COM Port” turn to yellow. It means connected and ready.
8. Begin the flashing by hitting the 'Start' button.
9. It will take 5 minutes to complete and the word "PASS" will display once it finishes.
10. Unplug the phone from the PC, and go into Recovery Mode by pressing Home + Power Button, then select Wipe Data / Factory Reset. Reboot Phone.
11. Last, change the default Russian language to your Region by going to settings and then locate the locale and text icon, then pick your native language.
I am not responsible if you break your phone, this is for educational purposes only.
Thanks to Droid Angel for help with the TUT.
Click to expand...
Click to collapse
seems like you are toooooooooo late to do something with the phone
i bet 95% of peoples know this thing and also this firmware was announced by sampro ages ago
I just know there was a couple of Noobs around wanting to go back to Samsung Firmware but no idea how... This is for them, not the 95% who already know how.
When I read the topic subject, I thinked that a new special method is needed for flashing the S5830XXKPP ROM.
I think 95% of galaxy.ace.xda.users have already known this, thanks
Hi.
This is the stock ROM I have flashed: French stock: G1XXKPQ
http://forum.xda-developers.com/showthread.php?t=1531850
I flashed the 2.3.6 stock ROM with Odin 1.85. And used Odin again to flash the TerraSilent 1.3.5 custom kernel. Then I have CWM custom recovery. And for the 2.3 GB ROM, I can see I have root (adb shell, su is okay).
Now I can't find out what to do as next step. I have looked at several AOSP ROMS' threads in the development forum, and still got no clue.
I tried the following:
1.
Download the following ROM: [ROM][YPG1][4.2.2] Paranoid-Android 3.60 - With HALO - 6/26/13
http://forum.xda-developers.com/showthread.php?t=2340544
And put it to the SDCARD. BTW, I have no external SDCARD installed.
In the CWM recovery, I chose to install this .ZIP file, the process is failed as follows:
{
"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"
}
The on screen text is OCR'ed by human flesh as follows:
Code:
ClockWork Mod Recovery v5.0.2.7
-- Installing: /sdcard/ROM/pa_ypg1-3.60-26JUN2013-201457.zip
Finding update package...
Opening update package...
Installing update...
assert failed: getprop("ro.product.device") == "ypg1" || getprop("ro.build.product") == "ypg1"
E:Error in /sdcard/ROM/pa_ypg1-3.60-26JUN2013-201457.zip
(Status 7)
Installation aborted.
As the message hints, I run similar commands in "adb shell" within the stock 2.3.6 ROM:
# getprop ro.product.device
getprop ro.product.device
YP-G1
# getprop ro.build.product
getprop ro.build.product
YP-G1
Click to expand...
Click to collapse
("adb shell" on Windows will have all commands echoed back, hence the stupid repeated command lines)
I don't know if this result is related to that assert performed in recovery. Just for the record. And I believe "YP-G1" is definitely "not equal" to "ypg1". But this is a safe assert. If this failed, probably there is something not expected by the ROM installer, so I understand cancelling installation is the correct thing. But how to pass the test and enable installation anyway?
2.
Then I downloaded this "preflash" zImage as mentioned in this most recent CM10.1 ROM thread:
http://forum.xda-developers.com/showthread.php?t=2333769
I have found several threads linking to this "preflash" zImage. It is somewhat quite mysterious. I don't know what does this "preflash" indicate: under what condition indeed does this "preflash" procedure to be performed?
I have come across the "MTD based ROM" jargon while searching everywhere. I have no idea of that. But I just want to get the AOSP likes to be installed onto the device. This "preflash" kernel seems to be just for such task.
Any way, I flashed it using TerraSilent's CWM recovery. The device is stuck at the samsung logo. So I reboot to Ubuntu to use heimdall to flash the zImage raw file.
By the way, can I pack zImage into .tar file and flash using Odin? heimdall tends to get messed up, and install its driver in Windows tends to mess even more, this tool definitely is not recommended to casual user).
So after flashing using heimdall, the device enters boot loop, the "samsung" logo did apear for three times, then the recovery screen just flashed away, even too fast to peek for the on screen message, I have to capture it by recording a video, and here is the frame extracted from the video:
Again the on screen text is OCR'ed by human flesh as follows:
Code:
CWM-based Recovery v6.0.1.2
Waiting for SD Card to mount (20s)
SD Card mounted...
Verifying SD Card marker...
SD Card marker not found...
Checking Internal SD Card marker...
Internal SD Card marker not found... continuing anyways.
-- Installing:
Finding update package...
E:unknown volume for path []
E:Can't mount
Installation aborted.
At last I'm still with that French stock 2.3.6... Any help would be appreciated and sorry for the lengthy gossips I have put here.
Well I figured out... It turns out after flashing the "preflash" zip, you MUST NOT reboot, but instead go on to flash the ROM itself.
And another important thing: you must restore /efs after flashing back to stock using Odin.
Initially I just can't get such hints from all those ROM threads in the development forum. Maybe it's too obvious. But it certainly is not so obvious for we Chinese people, as I searched in Chinese, I can find many have done exactly the same I did (lol). Anyway from the Chinese forums I finally get to it.
I have made a record of all the flashing procedures and put it here, hope it will help some avoid searching all over the world to get started from scratch.
Samsung Galaxy S Player WLAN 4.0, YP-G1 International (Intl.) version flashing notes
====================================================================================
I use Windows 7 X64 to perform the following operations.
Part 0: Backup /efs (to your computer)
I don't know what this really means, but it is REQUIRED for later flashing, so don't rush to the flashing.
I use adb shell to make backup:
# tar cf /sdcard/efs.tar /efs
And pull it to your PC and keep it safe:
C:\> adb pull /sdcard/efs.tar .
(This is just an example, your backup and restore approach can be different)
Part 1: Revert to stock Android 2.3 (Gingerbread)
I believe this can be performed as long as you have download mode available, and this should be a good start if you think you have totally messed up with your device.
Files you need:
a. Samsung mobile driver: http://forum.xda-developers.com/showthread.php?t=2038555
For the 1.5.25.0 driver installation, the install wizard says it some error occurred at the end. But it seems no harm.
b. Odin flashing tool: (download link is the same as a.) I use Odin 1.85 for the YP-G1 device.
c. The 2.3.6 stock ROM: http://forum.xda-developers.com/showthread.php?t=1531850
I picked G1XXKPQ, version 2.3.6. Since my device is bought from China, it is compatible.
Also download the "Pit" file, again for my YP-G1 from China, I choose the "Intl" version.
Steps:
1. Put your device into download mode:
a. Shutdown deivce entirely, and pull battery and re-install to be sure
b. Key combinations: PRESS and HOLD: HOME button and Volume Down button. Then additionally, press and hold POWER until "Download mode" appears on device screen.
2. Connect your device to PC, let the system recognize new devices and install drivers.
3. To further make sure, you can disconnect the device, pull out its battery. And enter download mode, then connect to PC again.
4. Open Odin tool, this needs Administrator privilege, if Odin detects your device, it will display some message like "<ID:0/008> Added!!", and there is a blank text field under the "ID:COM" label turning to yellow color and showing a COM port number.
Then on the Odin GUI, select two files:
a. Click "PIT" button, locate your downloaded ".pit" file. This will cause the "Re-Partition" option to be selected automatically.
b. Click "PDA" button, locate your ROM, which is a .tar.md5 file, like: YP-G1FullRestoreIntl2.3.6.tar.md5
c. Click "Start" and wait until the device reboots.
Sometimes Odin is stuck at "SetupConnection", then retry: find a better cable (should not be too long), find a better USB port on your PC (USB 2.0 possibly can be preferred over USB 3.0). Retry by restarting from Step 1.
5. After device reboots, it enters the Android recovery automatically, and you can see some RED text saying "mount failed" alike. Just choose "wipe data/factory reset" and then reboot.
Now you are stock.
Part 2: The TerraSilent custom kernel (with custom recovery ClockWork Mode, CWM)
The stock Android recovery cannot be used to flash custom stuff, so you need to flash a custom recovery first.
Steps:
1. Download TerraSilent custom kernel: http://forum.xda-developers.com/showthread.php?t=1643384
I choose 1.3.5, which comes with CWM v5.0.2.7
The odin flashable kernel file is: TerraSilent_intl-1.3.5.tar
2. Shutdown device, and enter download mode again, and connect it to the PC, open up Odin, DO NOT touch the "PIT" button, only the PDA button, and choose custom kernel file. Then punch "Start".
3. This should be quick, and device reboots automatically, but you will find nothing new in your stock Gingerbread ROM.
Part 3: Restore your /efs folder
Like part 0:
C:\> adb push efs.tar /sdcard/
Then "adb shell" to the device, and "su" if necessary:
# tar xf /sdcard/efs.tar -C /
(Again your restore approach can be different)
Part 4: Get 4.x AOSP ROM and flash:
This is the time you transform your Android 2.3 player into an AOSP based Android 4.x ROM, so it's a little tricky (in fact the tricky stuff includes above /efs backup & restore thing)
I'm taking this CM9 as an example: http://forum.xda-developers.com/showthread.php?t=2213152
Because in this thread it mentions you MUST restore /efs for this ROM install to succeed, otherwise it will fail. (I have attached a photo of the failed install for reference.)
1. From this thread, download two files:
a. cm-9-20130402-kernel-preflash.zip
b. cm-9-20130408-UNOFFICIAL-ypg1.zip
Put both to device's /sdcard. And REMOVE your external Micro SD card if any.
2. Shutdown your device. Addtionally pull and re-install the battery for sure. Then you need to enter the recovery.
The key combinatoins for entering recovery:
PRESS and HOLD: HOME button and VOLUME UP button.
Additionally, press and hold power button. When the screen lights up, release POWER button, but keep HOME and VOLUME UP pressed.
As you are in the CWM recovery, this is from the TerraSilent custom kernel, version is v5.0.2.7.
a. Perform some wiping:
- wipe data/factory reset
- wipe cache partition
- advanced, - Wipe Dalvik Cache
b. Then install:
- install zip from sdcard, - choose zip from sdcard, --> select the .zip ROM file and confirm.
Sometimes the /sdcard won't mount, i.e., after choosing "- choose zip from sdcard", nothing can be found there.
Then I pull the battery and repeat it. Probably the files will show up.
Flash in the following order, don't reboot after the first .zip is flashed:
a. cm-9-20130402-kernel-preflash.zip
b. cm-9-20130408-UNOFFICIAL-ypg1.zip
When flashing the second one, the device will reboot automatically. Wait patiently until the device stays at a "new" custom recovery, which shows its version as "CWM-based recovery v6.0.1.2". Then you have completed all. Here you can flash the GAPPS package, if you have put it at your /sdcard before.
PS. "GAPPS" packges download: http://goo.im/gapps/
Please match the version, e.g., CM10.1 is "Jelly Bean" 4.2 (JB), CM9 is "Ice Cream Sandwich" (ICS).
Part 5: Other AOSP based ROMS.
From now on, you don't need that "cm-9-20130402-kernel-preflash.zip" file when flashing other AOSP based ROMS.
Just put the .zip ROM file at /sdcard, and reboot into custom recovery, wipe as needed, and install.
Attached is a photo showing how it fails to install the CM9 ROM if /efs was not restored:
Wow this is a full fledged guide on how to flash cm9, cm10 and cm10.1. I will add this to the all-in-one when I'll get some time.
Envoyé depuis mon Nexus 7 avec Tapatalk
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
How To Root Galaxy Win or Galaxy Grand Quattro (GT-I8552)
Best viewed in a Web browser. The pictures won't appear as intended in the XDA app.
One of the bit.ly/shortened URLs linked in this guide which directly leads to the download page of the file may be blocked by a security feature. They're all safe. Once you click a link you may be warned by your browser for accessing the URLs, but fortunately, the Warning page has a part where there's an option to proceed with accessing the page, just proceed and click the link. See example below.
bitly suggests that you
Change the original link, and re-shorten with bitly
Close your browser window
Notify the sender of the URL
Or, continue at your own risk to: http://download.clockworkmod.com/drivers/SAMSUNG_USB_Driver_for_Mobile_Phones.exe[/COLOR]
If you get no warnings, much better. Let's proceed.
The Preparation : Before you start, make sure that . . .1) You have a PC / Laptop running Windows Platform
2) Samsung USB Driver for Mobile Phones (click to DL from clockworkmod.com) is installed
3) Phone battery power is at least 70%. That's good enough to not run out of power during this whole process.
4) Its USB Debugging is enabled (Settings > Developer Options > USB Debugging)
5) You have a USB Cable to establish a connection between the phone & your computer
6) You have the files needed. Keep three files in one folder.
- twrp_2.8_material - 9185 KB (click to DL directly from its dev's (Gody) MediaFire drive)
- Odin3-v3.09.zip - 972 KB (click to DL from sammobile.com's MEGA shared cloud storage) This software runs only on Windows platform.
- SuperSU_v1.94.zip - 1,703 KB (click to DL direclty from chainfire website)7) A copy of that flashable zip file "SuperSU" must be saved in your phone's memory, internal or external .
1st Step : Flashing TWRP Recovery Via OdinWhat is Recovery? | The Two Android Recovery Agents (CWM & TWRP)
Here, we will use TWRP Recovery. We will install it on the device using the Odin software.
Required: your phone, Windows PC, USB cable, Odin, and TWRP (.tar file)
1) Boot phone to "Odin Mode, a.k.a. Download Mode" by pressing the buttons at the same time: Volume Down, Power, & Home. When the device vibrates, immediately release the Power button while still pressing the other two until the Download Mode's warning screen appears.
{
"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"
}
2) Press the "Volume Up" button to continue to Odin Mode
3) In your computer, using WinRar or 7-zip, extract the Odin zip file, then run Odin3 v3.09.exe as Administrator
4) Connect your phone to your PC via USB. It should say "Added" on Odin.
5) On Odin, click the "AP" button, find and select the "twrp_2.8_material.tar"
6) Click "Start" to proceed in flashing the TWRP Recovery. *This takes about a minute.
7) It's partially finished when it says RESET! with these three lines in the message box.
RQT_CLOSE !!
RES OK !!
Removed!!
Then, phone will reboot automatically to OS.
8) Sometimes it takes a few more seconds after the phone has rebooted for you to be able to completely close Odin. Just wait for Odin to change its status from RESET! to PASS! and say All threads completed. (succeed 1 / failed 0), as shown in the picture below.
Then, you may click Exit and disconnect cable.
TWRP 2.8.5.0 Recovery is now installed.
And this is how to boot to "Recovery Mode". Press the buttons at the same time: Volume Up, Power, & Home. When the device vibrates, immediately release the Power button while still pressing the other two until the SAMSUNG boot-screen appears. See photo instructions below.
By the way, see the pictures below for the difference between the Galaxy Win's stock recovery and TWRP's recovery.
Important : NANDroid Backup
At this point, with TWRP Recovery installed, you can now create a NANDroid backup. It's a backup of literally everything in your phone - System, Cache, Data, EFS, and Boot. It is considered to be the top priority of things to do before messing with your phone i.e. flashing ROMs, kernels, or apps. After you create a backup, the backup file would be located in "sdcard0/TWRP/BACKUPS/" for internally saved backup, and "extSdCard/TWRP/BACKUPS/" if it's saved to the external memory. This file can also be transferred to a different storage, say a hard-disk, if you need to have more space on your phone for something else. You may skip to the actual rooting part. But, in case you do want to create a backup just follow the simple steps below. 1) Boot phone to Recovery Mode
2) Select Backup
3) This part lets you name the backup file with whatever name you want, choose whether to save it internally or externally, and pick which stuff you'd like to backup. And when you're ready, swipe to backup.
*This may take 5-10 minutes depending on how big your whole current installation is.
4) Once done, you may proceed with the 2nd part of this rooting guide.
2nd & Final Step: Flashing SuperSUSuperSU allows for advanced management of Superuser access rights for all the apps on your device that need root.
Required: your phone, and SuperSU (.zip file)
1) Boot phone to Recovery Mode
2) Select Install
2) Locate the zip file SuperSU
3) Go ahead and swipe to install SuperSU *This takes just 5-10 seconds.
4) Reboot System
You now have root access. Good luck!
Important Reads After Rooting An Android Device:
What Is A Nandroid Backup and How Exactly Does It Work?
TriangleAway – Reset Flash Counter Tool
11 Things To Do After Rooting Your Android Smartphone | RootMyAndroid.Org
Suggested ROM:
COSMIC 2.0 ROM (released 4/27/15) (CM10). Rated to be the most stable custom ROM for the device.
Originally developed for Galaxy Core Duos by dev abhi922, then ported by dev gody420 to work on Grand Quattro.
Hey mate, thanks a lot! Your guide is very clean and objective. Links shown properly. You did a good job!
But I'm still facing a problem on my I-8552B. Whichever Recovery I try to flash, I keep getting a black screen.
I tried the one you posted and the 6.0.3.7 version, but nothing different. :/
Thanks! I'm as glad that this guide is helpful to us who need it.
When does this black screen appear?
What have you done so far?
Sent from my GT-I8552
The phone is working properly, I can boot into the system normally. But after I flash any custom recovery via Odin (all I tried, so far), and boot into recovery (phone off, VOL +, Home and PWR boot), I get a black screen.
I've read that people are getting this issue on devices bought after July/14...
Please refer to this thread for more ideas.
http://forum.xda-developers.com/showthread.php?t=2977978
Best of luck!
Sent from my GT-I8552
Hi. .when my galaxy win was rooted, the task manager was deleted. Is there a way to recover it plz. .tnx
Sent from my GT-I8552 using XDA Free mobile app
[Root ,Easy ,Fast No Pc! ]
:angel:Visit the link: http://forum.xda-developers.com/grand-quattro/general/root-grand-quattro-win-duos-t3091676
Good Share
Thanks for clear share;
1- Odin3-v3.09.zip link dead
2- I download the v3.07 and It works only AP = PDA
3-I like the TWRP screen
Thanks again
i'm too having the same problem..after flashing custom recovery, the screen goes black when i try to enter recovery mode
Samsung Galaxy Win GT-I8552B
Excellent tutorial, but I could not install SuperSU, my phone model is
Samsung Galaxy Win GT-I8552B
Version: 4.1.2
Can you help me?
Best regards
Roosevelt Paz Garcia
I am stuck at 'starting adb sideload features' in adb sideload. Please suggest what to do?
I am not getting the install option on the recovery boot
someone help plz
No need to unlock bootloader for samsung ???
Is it??
Samsung Galaxy Core Prime
SM-G360T
{
"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"
}
The all in one solution for this phone.
Reinstall Android
"Odin" is a Samsung's tool to make changes for Samsung Devices by using Computer to make changes for your phone, we need Windows OS to make changes for this Samsung Galaxy Core Prime Phone, and make sure that you've installed Samsung Drivers on your Computer Windows OS before you begin to use "Odin".
To Enter Recovery:> Press together [Home Button + Volume Up + Power] Until Recovery Screen appears.
To Enter Odin mode:> Press together [Home Button + Volume Down + Power] Until Odin Screen appears.
- Restore your Phone to original Factory:
Run Odin app, and make sure you're on Odin mode on your phone, connect the cable and press Volume Up button for the Phone, this time will enter Downloading mode for Odin, now the Odin app should list the phone connection, and make sure the "Auto Reboot" and "F. Reset Time" are selected before beginning next steps. Click on AP/PDA button and choose the proper Firmware for the Device, after scanning completes, click on Start button to begin the installation. Do not disconnect the connection cable while processing the progress, after the progress finishes, your phone will show up the new freshly installed OS.
- Install Custom Recovery:
A "Custom Recovery" is a different Recovery made by people which have it's own name called, in here we're trying to Install "TWRP Recovery" version, this will allow us more control of the Device to make changes.
Run Odin app, and make sure you're on Odin mode on your phone, connect the cable and press Volume Up button for the Phone, this time will enter Downloading mode for Odin, now the Odin app should list the phone connection, and make sure the "Auto Reboot" and "F. Reset Time" are selected before beginning next steps. Click on AP/PDA button and choose the proper Recovery for the Device, after scanning completes, click on Start button to begin the installation. Do not disconnect the connection cable while processing the progress, after the progress finishes, your phone will automatically restart to Android OS.
- Root your Phone OS
There're many ways to Root the Android OS, and we're choosing the availability modes and the safest way for Samsung Galaxy Core Prime, So a Custom Recovery must be already installed to Root the Android OS, So save and copy the "Magisk.zip" to your Device Storage or Secondary storage and then Enter Recovery, Tap on Install and browse to "Magisk.zip" file, Swipe to Install and Tap on Reboot to OS, make sure you don't let "TWRP" to Install it's own SuperUser. If you couldn’t root your OS by this way, you may try again and wipe Dalvik/Cache in Recovery or you may reinstall the Recovery to a different versions.
Download Link: Samsung Galaxy Core Prime (SM-360T) Zipped File
The Zipped File contains Instructions and plus:
- Samsung Galaxy Core Prime SM-G360T Stock Firmware (TMB-G360TUVU1APG2-20160729133007.zip)
- Drivers for Samsung Devices
- Samsung's Odin Tool
- Custom "TWRP" Recovery version 3.2.3-0 (twrp-3.2.3-0-cprimeltemtr)
- Magisk version 18.1 SuperUser / or check the latest Magisk version here
_______________________________
Have a Nice Try!
_______________________________
Go and check about your device in settings before you do any task.
Stock Firmware for (SM-G360T): TMB-G360TUVU1APG2-20160729133007.zip
Baseband version: G360TUVU1APG2
_______________________________
Will the all in one back up work on the SM-G360T1 with Baseband version G360T1UVU1AOFA
hatchet13rydin69 said:
Will the all in one back up work on the SM-G360T1 with Baseband version G360T1UVU1AOFA
Click to expand...
Click to collapse
No, Don't do that! this can be risky! yours is Metropcs version of Samsung Galaxy Core Prime.
My Zipped file contains Stock ROM OS "G360TUVU1APG2" and it is for T-Mobile version of Samsung Galaxy Core Prime. (just beside the Recovery image, which is compatable with both T-Mobile and Metropcs)
Be sure to match both the Baseband code of your Phone and the Stock file.
Go to About Phone and search for your exactly baseband code number, it's better to download from the official sites.
Have a nice try
iPlasm said:
No, Don't do that! this can be risky! yours is Metropcs version of Samsung Galaxy Core Prime.
My Zipped file contains Stock ROM OS "G360TUVU1APG2" and it is for T-Mobile version of Samsung Galaxy Core Prime. (just beside the Recovery image, which is compatable with both T-Mobile and Metropcs)
Be sure to match both the Baseband code of your Phone and the Stock file.
Go to About Phone and search for your exactly baseband code number, it's better to download from the official sites.
Have a nice try
Click to expand...
Click to collapse
That's what I thought. Just wanted to make sure before doing something stupid and brick in my phone as this is my daily driver. I appreciate your help and all the hard work you and all the other devs put in to give the android community the know how and ability to run their devices the way they were meant to be ran. Keep up the hard work. I'm sure I speak for more than myself when I say that your work and dedication is greatly appreciated.
hatchet13rydin69 said:
That's what I thought. Just wanted to make sure before doing something stupid and brick in my phone as this is my daily driver. I appreciate your help and all the hard work you and all the other devs put in to give the android community the know how and ability to run their devices the way they were meant to be ran. Keep up the hard work. I'm sure I speak for more than myself when I say that your work and dedication is greatly appreciated.
Click to expand...
Click to collapse
You're welcome!
This phone has a little support, I will post anything if I did something for this Samsung Galaxy Core Prime
iPlasm,
iPlasm said:
You're welcome!
This phone has a little support, I will post anything if I did something for this Samsung Galaxy Core Prime
iPlasm,
Click to expand...
Click to collapse
That would be awesome. :fingers-crossed: I appreciate your time and effort. If you need anything tested for 360t1 I'd be happy to help in anyway I can.
hi is this stock firmware? please confirm. My Camera keeps saying failed. I cleared Cache & data, rebooted and nothing helps.
I made a quick update to most recent version, Link Download updated.
Thanks and Enjoy