Hi there. Let me just start off by saying, despite my efforts, I still have next to no idea as to what I am doing.
My Phone: Galaxy SII i9100T (Australian Telstra variant), ICS 4.03
So today I decided to root my phone and install cyanogenmod 9 following a guide in a magazine (that was written for cyanogenmod 7 if that makes a difference). Initially it told me to root with SuperOneClick, but that wasn't working for my device as the program would eventually not respond.
After snooping around on the internet I eventually ended up rooting my phone (I think) with Odin 1.85 installing an image called CF-Root-SGS2_XW_NEE_LPG-v5.5-CWM5 under the PDA option (as per instructions of one particular website). That worked.
So then I consulted the magazine again, and it said to download the heimdall suite from the cyanogenmod wiki galaxy sII page, and run a program called zadig, list all devices, and change the 'Samsung Android' driver to whatever zadig installs. However, my phone did not come up as that, it came up as two other files, one with a driver called Modem, and the other with a driver that I cannot remember the name of. I can confirm that they were my phone and no other USB devices as they disappeared when I unplugged my phone. I chose the driver that wasn't called Modem. That seemed to work fine.
Next it said to install a clockworkmod image using the heimdall suite. The image was recovery-clockwork-5.5.0.4-galaxys2 ....I eventually got that to work.
However, no matter what I do now, I cannot get into the clockworkmod recovery screen to install cyanogenmod 9. Did I do something wrong? I think I may have made a mistake with zadig, as now it lists my phone as 4 devices: Samsung_Android, Samsung_Android, Samsung, and MTP.
I know this is an absolute mess of a situation, but I desperately need help. If I cant go through with the installation of cyanogenmod, can I at least reset everything back to normal like it was out of the box?
Any help would be very much appreciated.
You could e-mail the editor of the mag and complain
Sent from my GT-I9100 using xda premium
ultimatebestusername said:
Hi there. Let me just start off by saying, despite my efforts, I still have next to no idea as to what I am doing.
My Phone: Galaxy SII i9100T (Australian Telstra variant), ICS 4.03
So today I decided to root my phone and install cyanogenmod 9 following a guide in a magazine (that was written for cyanogenmod 7 if that makes a difference). Initially it told me to root with SuperOneClick, but that wasn't working for my device as the program would eventually not respond.
After snooping around on the internet I eventually ended up rooting my phone (I think) with Odin 1.85 installing an image called CF-Root-SGS2_XW_NEE_LPG-v5.5-CWM5 under the PDA option (as per instructions of one particular website). That worked.
So then I consulted the magazine again, and it said to download the heimdall suite from the cyanogenmod wiki galaxy sII page, and run a program called zadig, list all devices, and change the 'Samsung Android' driver to whatever zadig installs. However, my phone did not come up as that, it came up as two other files, one with a driver called Modem, and the other with a driver that I cannot remember the name of. I can confirm that they were my phone and no other USB devices as they disappeared when I unplugged my phone. I chose the driver that wasn't called Modem. That seemed to work fine.
Next it said to install a clockworkmod image using the heimdall suite. The image was recovery-clockwork-5.5.0.4-galaxys2 ....I eventually got that to work.
However, no matter what I do now, I cannot get into the clockworkmod recovery screen to install cyanogenmod 9. Did I do something wrong? I think I may have made a mistake with zadig, as now it lists my phone as 4 devices: Samsung_Android, Samsung_Android, Samsung, and MTP.
I know this is an absolute mess of a situation, but I desperately need help. If I cant go through with the installation of cyanogenmod, can I at least reset everything back to normal like it was out of the box?
Any help would be very much appreciated.
Click to expand...
Click to collapse
I suggest you restart from scratch following these steps:
1. read everything about flashing and rooting you can find on this site (read stickies first)
2. same as 1.
3. same as 1.
4. flash the latest stock firmware for your phone
5. root your phone
6. finally flash some other ROM
As a general rule, do not forget to take extra precautions when you flash anything: ALWAYS DO A NANDROID BACKUP IN CWM...
Performs a wipe date , factory reset , then follow the guide;
[GUIDE] ROOT/UNROOT Stock ICS Firmware without flashing unsecure kernel
Simple way to root and unroot stock kernel without flashing insecure kernel.
Don't worry about custom counter and yellow triangle, with this method they never appear, because we only rooting, it's a rooting script not a custom kernel.
This rooting script included Busybox installer.
Rooting
Download this File first and put in your SDCARD
- CWM via stock recovery ;( http://dl.dropbox.com/u/34053267/CWM.zip) , or download zip from http://clockworkmod.com/rommanager
- SU-Busybox-Installer.zip ( https://dl.dropbox.com/u/34053267/SU-Busybox-Installer.zip )
Reboot to recovery.
Choose apply update from external storage.
Choose CWM.zip and wait until CWM recovery appear.
Choose install zip from sdcard or external SD
Choose and Install SU-Busybox-Installer.zip
Reboot
You are done and now your device is Rooted
Method 2
CF_Root + stock kernel + [optional] Mobile Odin Free version
Here, you use an older CF_Root kernel, and flash your newer stock kernel
Quote:
First, get a CF_Root kernel from CF_Root thread here http://forum.xda-developers.com/showthread.php?t=1103399. Just get the nearest one to your ROM. You can download any ICS kernel, it will do the job for the root only purpose
Flash the CF_Root kernel with odin
Now, flash again your stock kernel with odin. You can get a stock kernel from lyriquidperfection thread http://forum.xda-developers.com/showthread.php?t=1619525
Do not forget to thank / donate to him
No stock kernels for you? use Mobile Odin free version (see below)
After flashing the stock kernel, root will usually stay and you will be reverted back to your stock recovery instead of CWM recovery
Long story short,
Even using a custom recovery I am unable to flash any rom Execpt stock, or a modified stock rom (using Etherealrom 2.4 right now)
And I was wondering if anyone has a dump from odin or Heimdall that I could use to try to flash CM to my device, weather it's cm9 or cm10,
it may help, as from there I may be able to flash other roms.
I'm not sure what wrong with my device, but even when returning to stock, my lock screen fails to engage with a 100% stock Heimdall / odin image,
Even ones I've used in the past with no problems. but everything else seems to work fine.
And be fore you ask,
yes I have tried the manual flashing steps shown on the cm9/10/11 pages,
yes, I have tried using the TerraSilent usa kernal (multiple versions)
yes, I have tired doing a full restore of the image, even with re-partitioning from a pit file
yes, I used the preflash before trying to install cm9/10/11, and tried the various toggles
yes, in the past I was able to flash cm9, but I was on stock for a while, then when trying to switch back, this happened.
yes, I have checked my EMS partition, and even tried manually rebuilding it,
The only way I can flash anything, including sock, and modified stock roms, is from my PC, via odin, or Heimdall
So I was wondering if someone with the USA galaxy player 4 could do a dump for me, and include the pit file,
so I could attempt to get CM installed that way?
I have a Verizon Note 2 running 4.4.2.
I successfully rooted it without unlocking the bootloader or flashing a custom recovery, everything was stock. Everything worked fine after and I was able to use root-requiring apps.
Then, after attempting to flash custom recovery, since the bootloader was locked, I am now stuck at the screen that says: "System software not authorized by Verizon Wireless has been found on your phone..."
I am able to enter recovery (the stock recovery) as well as go into download mode. Normally this wouldn't be a problem as I could just flash stock through Odin in download mode.
However, ever since the soft-brick Odin won't recognize my phone (the yellow COM square does not come up), which is strange because Odin recognized my Note 2 in download mode before this happened.
And even stranger is the fact that it is not a driver issue, as when I plug in my Note 2 in download mode I get a message from Windows 7 saying that the serial gadget device driver was found and installed successfully (and the phone also shows up in Device Manager in control panel as fully installed while in download mode.
Yet Odin won't recognize it.
I have spent days searching for an answer and have yet to come across an issue identical to mine (everyone seems to be able to just flash stock through Odin to fix this particular soft-brick, but Odin is not recognizing my device), so I finally decided to post here.
Any suggestions at all are welcome as I am somewhat desperate at this point. I'd just like to get it back to stock (or flash a custom rom, it does not matter as long as I can get the phone to work).
I would like to point out that I have already tried the following:
- Different USB ports
- Using different USB cables
- Uninstalling and reinstalling the drivers
- Wipe/Factory Reset in stock recovery
From what I can see, my only options are to either somehow get Odin to recognize the phone (suggestions welcome here), or somehow flash stock through the default recovery (if possible, again, any input is appreciated).
William31 said:
I have a Verizon Note 2 running 4.4.2.
I successfully rooted it without unlocking the bootloader or flashing a custom recovery, everything was stock. Everything worked fine after and I was able to use root-requiring apps.
Then, after attempting to flash custom recovery, since the bootloader was locked, I am now stuck at the screen that says: "System software not authorized by Verizon Wireless has been found on your phone..."
I am able to enter recovery (the stock recovery) as well as go into download mode. Normally this wouldn't be a problem as I could just flash stock through Odin in download mode.
However, ever since the soft-brick Odin won't recognize my phone (the yellow COM square does not come up), which is strange because Odin recognized my Note 2 in download mode before this happened.
And even stranger is the fact that it is not a driver issue, as when I plug in my Note 2 in download mode I get a message from Windows 7 saying that the serial gadget device driver was found and installed successfully (and the phone also shows up in Device Manager in control panel as fully installed while in download mode.
Yet Odin won't recognize it.
I have spent days searching for an answer and have yet to come across an issue identical to mine (everyone seems to be able to just flash stock through Odin to fix this particular soft-brick, but Odin is not recognizing my device), so I finally decided to post here.
Any suggestions at all are welcome as I am somewhat desperate at this point. I'd just like to get it back to stock (or flash a custom rom, it does not matter as long as I can get the phone to work).
I would like to point out that I have already tried the following:
- Different USB ports
- Using different USB cables
- Uninstalling and reinstalling the drivers
- Wipe/Factory Reset in stock recovery
From what I can see, my only options are to either somehow get Odin to recognize the phone (suggestions welcome here), or somehow flash stock through the default recovery (if possible, again, any input is appreciated).
Click to expand...
Click to collapse
Wow... I'm stumped too as to why Odin won't recognize the phone. What method did you use to try to flash the custom recovery and what recovery did you flash? (You probably know now, but just in case.... if you can get the phone restored to stock 4.4.2 again... then you can't flash a standard custom recovery onto the phone because of the bootloader being locked down. You can use the modified TWRP called Safestrap recovery if you root again... and can only flash 4.4.2 touchwiz roms with stock 4.4.2 kernel after you get rooted again).
When you rooted, all I can think of is that something may have corrupted the drivers somehow and that's now conflicting with ODIN. With the phone in download mode... have have you went into the PC's Device Manager and tried to delete/reinstall any Samsung related drivers, (make sure to look for hidden drivers.... click scan for hardware changes after deleting them and the computer should reinstall the correct drivers). Also... have you made sure no other conflicting programs (like Kies) are running in the background?
You might try to do a system restore to an earlier point on your PC where ODIN recognized the phone to see if that would work.
If ODIN version 3.07 isn't recognizing the phone, you could try a newer version of ODIN. Here's some links to other ODIN versions that you might try: Download link for ODIN 3.09 ; Download link for ODIN 3.10.0. ~~With the newer ODIN versions, they have replaced the "PDA" slot with "AP"--so the .tar firmware file goes into AP in the newer ODIN. ****(For reference--Here's the XDA Thread where XDA recognized contributor -CALIBAN666- posted these links to newer ODIN versions. Hit the thanks button for him ****
---------------
If you can't get the restore to work with ODIN, you could try Samsung Kies to see if it can fix the device...
Where to download Kies -- http://www.samsung.com/us/kies/
Emergency Firmware Recovery using Kies 3 -- http://www.samsung.com/us/support/faq/FAQ00059169/81100
I hope that some of this info helps and that you can get it fixed.
Good luck!
mattnmag said:
Wow... I'm stumped too as to why Odin won't recognize the phone. What method did you use to try to flash the custom recovery and what recovery did you flash? (You probably know now, but just in case.... if you can get the phone restored to stock 4.4.2 again... then you can't flash a standard custom recovery onto the phone because of the bootloader being locked down. You can use the modified TWRP called Safestrap recovery if you root again... and can only flash 4.4.2 touchwiz roms with stock 4.4.2 kernel after you get rooted again).
When you rooted, all I can think of is that something may have corrupted the drivers somehow and that's now conflicting with ODIN. With the phone in download mode... have have you went into the PC's Device Manager and tried to delete/reinstall any Samsung related drivers, (make sure to look for hidden drivers.... click scan for hardware changes after deleting them and the computer should reinstall the correct drivers). Also... have you made sure no other conflicting programs (like Kies) are running in the background?
You might try to do a system restore to an earlier point on your PC where ODIN recognized the phone to see if that would work.
If ODIN version 3.07 isn't recognizing the phone, you could try a newer version of ODIN. Here's some links to other ODIN versions that you might try: Download link for ODIN 3.09 ; Download link for ODIN 3.10.0. ~~With the newer ODIN versions, they have replaced the "PDA" slot with "AP"--so the .tar firmware file goes into AP in the newer ODIN. ****(For reference--Here's the XDA Thread where XDA recognized contributor -CALIBAN666- posted these links to newer ODIN versions. Hit the thanks button for him ****
---------------
If you can't get the restore to work with ODIN, you could try Samsung Kies to see if it can fix the device...
Where to download Kies -- http://www.samsung.com/us/kies/
Emergency Firmware Recovery using Kies 3 -- http://www.samsung.com/us/support/faq/FAQ00059169/81100
I hope that some of this info helps and that you can get it fixed.
Good luck!
Click to expand...
Click to collapse
So I tried recovering with Kies and it just kept throwing errors at me, then finally I just closed it and, am not quite sure why, but went into Odin and it worked! Apparently trying to recover with Kies somehow fixed the Odin issue and I was able to flash stock through Odin. Thanks so much!
You mentioned there was a way to flash a safestrap recovery and then flash touchwiz roms? Do you by chance have instructions on how I could do this, or links to this information...?
William31 said:
So I tried recovering with Kies and it just kept throwing errors at me, then finally I just closed it and, am not quite sure why, but went into Odin and it worked! Apparently trying to recover with Kies somehow fixed the Odin issue and I was able to flash stock through Odin. Thanks so much!
You mentioned there was a way to flash a safestrap recovery and then flash touchwiz roms? Do you by chance have instructions on how I could do this, or links to this information...?
Click to expand...
Click to collapse
Cool. Glad you got it fixed.
As you know, you can root with GhettoRoot from this thread: http://forum.xda-developers.com/showthread.php?p=57238246
Then can install Safestrap from this thread: http://forum.xda-developers.com/showthread.php?p=51616723
I've never used Safestrap because I can use regular custom recoveries like CWM and TWRP. I'm still on a 4.1.2 unlocked bootloader and currently running TrentsKKRom, Build #2...which is 4.4.2 based with stock kernel, so I think it would work with Safestrap.
I'd recommend reading through the Safestrap thread thoroughly and asking questions there to make sure you get everything installed correctly. I've read that with Safestrap, you need to make a backup of your Stock ROM first and save it somewhere safe, like to your computer and on your external sd card...so you can easily restore it if needed. (I'd also make a backup of the ESF in Safestrap if it lets you, then save it somewhere safe).
After you are rooted with Safestrap, you'll have to flash custom ROM's over the stock slot in Safestrap, as the other slots apparently don't work. Again, you're limited to only using Touchwiz ROM's with the stock kernel because of the bootloader still being locked.
Check out TrentsKKRom and Alliance build 30 . (I personally like Trent's build 2 best with the S5 clean theme). I've also found Trent's ROM to be really smooth without UI lagging, the Bluetooth works good with no stuttering, and it pairs well with my Sony Smartwatch 3. (Edit: If you do try Trent's ROM, you may need to install a couple apps.... Chainfire's Supersu app to control your root permissions (at least I needed to), and the FolderMount app to fix a KitKat internal storage mounting issue).
Have fun!!
Hi all
How exciting it is to see that so many people are so involved in improving or fixing their mobile devices.
I got some sort of a virus on my Samsung Galaxy S3 so decided to try to wipe it clean and load a more up-to-date version of Android on it. It had 4.3.?. On a Windows 7 PC, I downloaded the Skipsoft Unified Android Toolkit (version 1.4.5). I think now I didn't need to but probably succeeded in rooting my S3 with Kingo ROOT.
Next, using the toolkit and Odin, I think I succeeded in flashing the recovery-twrp-2.7.1.0-i9300.tar custom recovery.
My phone would only boot up with the stock Android.
I took me a while before I learnt about entering the recovery mode by holding the volume up, home and power-on buttons simulateously.
In the recovery mode, I used Wipe, Advanced, ticked all of the boxes and wiped everything on the phone.
Then, using the toolkit and Odin again, I flashed the same recovery-twrp-2.7.1.0-i9300.tar custom recovery I'd flashed before.
I still can't boot my phone. If I choose Reboot from twrp (v2.7.1.0) and then either System or Recovery, I just get, "No OS installed! Are you sure you wish to reboot?"
I can still enter either download or recovery modes but the latter is something of a hit and miss affair.
Using File Manager in the twrp I can see lots of files and directories so guess I managed to flash something.
Also, using Terminal Command I see that my prompt is a "#"so think I'm still rooted.
I know something about Unix and programming mainframe computers but am not an expert with mobile devices. I'd be so grateful if someone could please advise me as to what to do?
Mike
You wiped system partition ;-;
If you want stock rom you need to flash the stock rom by odin.
I recommend you to install a custom rom like Temasek or CM13, it's real easy just flash the zip.
Haha yes^ this guy is right
You might have to flash stock rom if you somehow wiped efs, most of the time custom roms doesn't include efs with them
Turga said:
You wiped system partition ;-;
If you want stock rom you need to flash the stock rom by odin.
I recommend you to install a custom rom like Temasek or CM13, it's real easy just flash the zip.
Click to expand...
Click to collapse
Thanks for your response, Turga and snkmv, below. I didn't know what efs was so looked it up on the net and found this worrying but expert explanation from ryanrazer and Rukbat in androidcentral ( http://forums.androidcentral.com/as...erstanding-cwm-backups-efs-partition-etc.html )
In twrp's recovery mode on my phone and using File Manager, I see that the directory /efs is empty (all files are shown in File Manager, right, including invisible files?)
I'd prefer to try to flash a custom ROM which includes efs rather than the stock ROM. Do Temasek or CM13 include efs or does another, reliable custom ROM?
Thanks again folks
Mike
I have a bricked phone, I don't even remember what I was doing to brick it. Probably installing some cyanogen version.
When it turns on, it first shows a black screen with "GT-I5500" large on the middle, with the SAMSUNG logo on the bottom, and stays there.
What could I try to unbrick it?
Thanks!
I installed JOdin (I have a Mac) and Heimdall (latest nightly build, since I run on a macOS High Sierra 10.13.6)
I found ROMS and etc here: https drive dort google dot com/drive/folders/1y3rvsNnveFkuRtC_We8hLMqmDAepaQ7b?usp=sharing
So I tried to flash using these settings:
PDA = JellyBread v4.5.zip (https drive dot google dot com/file/d/14ofWkgio7go406Y16FtkAn4bJ1B3w_DX/view?usp=sharing)
PIT = Europa_v1.0.ops (https drive dot google dot com/file/d/1WvZ5FAfjlM-AjSjrrRHrtkOrAe42XjVb/view?usp=sharing)
When I hit start, I get an error message saying that "The PIT file was corrupt. We cannot continue without a PIT file". JOdin attempts to get one, but it fails too.
Running JOdin from the terminal I see it trying to run "heimdall download-pit --output <filename>", so I tried to do it myself and this is what I get as output (resulted in a 0 bytes output file):
Code:
Initialising connection...
Detecting device...
Claiming interface...
Setting up interface...
libusbx: error [get_endpoints] error getting pipe information for pipe 1: unknown error
libusbx: error [darwin_set_interface_altsetting] could not build endpoint table
ERROR: Setting up interface failed!
Releasing device interface...
I wonder if someone here could please provide me with a PIT file for gt-i5500?
(Sorry for the weird links... new user restrictions ¯\_(ツ)_/¯ )
paulera888 said:
I installed JOdin (I have a Mac) and Heimdall (latest nightly build, since I run on a macOS High Sierra 10.13.6)
I found ROMS and etc here: https drive dort google dot com/drive/folders/1y3rvsNnveFkuRtC_We8hLMqmDAepaQ7b?usp=sharing
So I tried to flash using these settings:
PDA = JellyBread v4.5.zip (https drive dot google dot com/file/d/14ofWkgio7go406Y16FtkAn4bJ1B3w_DX/view?usp=sharing)
PIT = Europa_v1.0.ops (https drive dot google dot com/file/d/1WvZ5FAfjlM-AjSjrrRHrtkOrAe42XjVb/view?usp=sharing)
When I hit start, I get an error message saying that "The PIT file was corrupt. We cannot continue without a PIT file". JOdin attempts to get one, but it fails too.
Running JOdin from the terminal I see it trying to run "heimdall download-pit --output <filename>", so I tried to do it myself and this is what I get as output (resulted in a 0 bytes output file):
Code:
Initialising connection...
Detecting device...
Claiming interface...
Setting up interface...
libusbx: error [get_endpoints] error getting pipe information for pipe 1: unknown error
libusbx: error [darwin_set_interface_altsetting] could not build endpoint table
ERROR: Setting up interface failed!
Releasing device interface...
I wonder if someone here could please provide me with a PIT file for gt-i5500?
(Sorry for the weird links... new user restrictions ¯\_(ツ)_/¯ )
Click to expand...
Click to collapse
Hey, I'm the creator of the ROM collection thread, I can help you out with this. First off, can you get into Download Mode? I assume you can, since you're trying to use Odin. This is good, that means you can recover the brick. Next, I think JOdin will never work with this phone. This phone is very, very, finicky about the drivers and Odin version used. It seems to require a specific version to work, the one I linked - 4.28. As you can see here by XDA user Rickav, who tried to use newer Odin and Windows, it just doesn't work. We now know that this phone refuses to work with any Windows version newer than Windows 7, when Rickav reported that Win 10 was not able to work with the phone, but was successful with Win 7. If Win 10 doesn't work, MacOS has practically no chances of working.
So, you absolutely need to use either Windows XP, Vista, or 7 to be able to flash this phone in Download mode. Since you're on a Mac, you have a couple of options. The first is to use Boot Camp to dual boot Windows. This is optimal, but you may not like to do this, for various reasons. If you do not want to use Boot Camp, a virtual machine is also an option. You can download VirtualBox for free, and install Windows there. I would suggest using Windows 7 32-bit, or Windows XP, for maximum compatibility. If you do not know how to use VirtualBox, look up some tutorials, it's pretty easy to use. Then, when you have Windows installed in the VM, you can install the Odin 4.28 and and the Samsung USB Drivers from the backups thread.
When you have your VM (or dual boot, if you choose this) set up with the required software, you can start to recover the phone. I have found the most stable ROM is CM 7.2 (Android 2.3.7), so I would suggest flashing this. To use CM, you will first need a custom recovery. So, your first step is to use Odin to flash the ClockworkMod tar in the backups thread. Use Odin 4.28 (in backup thread), with the included ops file. After this, flash the AMSS-I5500LUYJPE.tar baseband, this is needed for custom ROMs to boot (otherwise, the custom ROM may bootloop) Next, go to the Philz Touch Recovery thread, and download 6.57.2. Put this zip on an sd card, insert sd into phone, boot into ClockworkMod, and flash the Philz Touch zip. This will overwrite the Clockwork recovery with Philz Touch. Philz is an improved version of Clockwork, and is also required to flash newer ROMs like CM 11. Once you have done this and have Philz Touch, download CM 7.2, put on sd, and boot into Philz. Go to wipe, and select prepare for new rom option, it will automatically wipe system, data, and cache. Next, flash the CM7.2 zip, and reboot. That should be it, and your phone should boot.
Sanras said:
Hey, I'm the creator of the ROM collection thread, I can help you out with this. First off, can you get into Download Mode? I assume you can, since you're trying to use Odin. This is good, that means you can recover the brick. Next, I think JOdin will never work with this phone. This phone is very, very, finicky about the drivers and Odin version used. It seems to require a specific version to work, the one I linked - 4.28. As you can see here by XDA user Rickav, who tried to use newer Odin and Windows, it just doesn't work. We now know that this phone refuses to work with any Windows version newer than Windows 7, when Rickav reported that Win 10 was not able to work with the phone, but was successful with Win 7. If Win 10 doesn't work, MacOS has practically no chances of working.
So, you absolutely need to use either Windows XP, Vista, or 7 to be able to flash this phone in Download mode. Since you're on a Mac, you have a couple of options. The first is to use Boot Camp to dual boot Windows. This is optimal, but you may not like to do this, for various reasons. If you do not want to use Boot Camp, a virtual machine is also an option. You can download VirtualBox for free, and install Windows there. I would suggest using Windows 7 32-bit, or Windows XP, for maximum compatibility. If you do not know how to use VirtualBox, look up some tutorials, it's pretty easy to use. Then, when you have Windows installed in the VM, you can install the Odin 4.28 and and the Samsung USB Drivers from the backups thread.
When you have your VM (or dual boot, if you choose this) set up with the required software, you can start to recover the phone. I have found the most stable ROM is CM 7.2 (Android 2.3.7), so I would suggest flashing this. To use CM, you will first need a custom recovery. So, your first step is to use Odin to flash the ClockworkMod tar in the backups thread. Use Odin 4.28 (in backup thread), with the included ops file. After this, flash the AMSS-I5500LUYJPE.tar baseband, this is needed for custom ROMs to boot (otherwise, the custom ROM may bootloop) Next, go to the Philz Touch Recovery thread, and download 6.57.2. Put this zip on an sd card, insert sd into phone, boot into ClockworkMod, and flash the Philz Touch zip. This will overwrite the Clockwork recovery with Philz Touch. Philz is an improved version of Clockwork, and is also required to flash newer ROMs like CM 11. Once you have done this and have Philz Touch, download CM 7.2, put on sd, and boot into Philz. Go to wipe, and select prepare for new rom option, it will automatically wipe system, data, and cache. Next, flash the CM7.2 zip, and reboot. That should be it, and your phone should boot.
Click to expand...
Click to collapse
Friend, thank you so much for your reply, I appreciate your effort in putting all those considerations and details together. You are a star! I will try it out with a VM and come back here with the results.
Sanras said:
r dual boot, if you choose this) set up with the required software, you can start to recover the phone. I have found the most stable ROM is CM 7.2 (Android 2.3.7), so I would suggest flashing this. To use CM, you will first need a cu
Click to expand...
Click to collapse
Sanras said:
Hey, I'm the creator of the ROM collection thread, I can help you out with this. First off, can you get into Download Mode? I assume you can, since you're trying to use Odin. This is good, that means you can recover the brick. Next, I think JOdin will never work with this phone. This phone is very, very, finicky about the drivers and Odin version used. It seems to require a specific version to work, the one I linked - 4.28. As you can see here by XDA user Rickav, who tried to use newer Odin and Windows, it just doesn't work. We now know that this phone refuses to work with any Windows version newer than Windows 7, when Rickav reported that Win 10 was not able to work with the phone, but was successful with Win 7. If Win 10 doesn't work, MacOS has practically no chances of working.
So, you absolutely need to use either Windows XP, Vista, or 7 to be able to flash this phone in Download mode. Since you're on a Mac, you have a couple of options. The first is to use Boot Camp to dual boot Windows. This is optimal, but you may not like to do this, for various reasons. If you do not want to use Boot Camp, a virtual machine is also an option. You can download VirtualBox for free, and install Windows there. I would suggest using Windows 7 32-bit, or Windows XP, for maximum compatibility. If you do not know how to use VirtualBox, look up some tutorials, it's pretty easy to use. Then, when you have Windows installed in the VM, you can install the Odin 4.28 and and the Samsung USB Drivers from the backups thread.
When you have your VM (or dual boot, if you choose this) set up with the required software, you can start to recover the phone. I have found the most stable ROM is CM 7.2 (Android 2.3.7), so I would suggest flashing this. To use CM, you will first need a custom recovery. So, your first step is to use Odin to flash the ClockworkMod tar in the backups thread. Use Odin 4.28 (in backup thread), with the included ops file. After this, flash the AMSS-I5500LUYJPE.tar baseband, this is needed for custom ROMs to boot (otherwise, the custom ROM may bootloop) Next, go to the Philz Touch Recovery thread, and download 6.57.2. Put this zip on an sd card, insert sd into phone, boot into ClockworkMod, and flash the Philz Touch zip. This will overwrite the Clockwork recovery with Philz Touch. Philz is an improved version of Clockwork, and is also required to flash newer ROMs like CM 11. Once you have done this and have Philz Touch, download CM 7.2, put on sd, and boot into Philz. Go to wipe, and select prepare for new rom option, it will automatically wipe system, data, and cache. Next, flash the CM7.2 zip, and reboot. That should be it, and your phone should boot.
Click to expand...
Click to collapse
Following your instructions and some other posts, I managed to get my GT-I5500 back to life; yay! I will leave some links and comments for those who might bump into this in the future. Thanks a lot
For some reason, I was not managing to boot the phone in recovery mode (it just kept stuck at the logo screen). In a nutshell, what I did was:
* Put CyanogenMod's zip in the sd card, card into the phone
* Using Odin, I flashed Clockworkmod into the phone, it rebooted into CWM's interface
* Wipe cache and user data
* Instal CyanogenMod from sdcard
* Happy days
These links were of great help:
Install Windows XP in VirtualBox (ready to use Virtual HD)
https://www.makeuseof.com/tag/download-windows-xp-for-free-and-legally-straight-from-microsoft-si/
VirtualBox extension to enable enable USB 2.0
https://www.techrepublic.com/article/how-to-enable-usb-in-virtualbox/
Actions sequence to get Odin to identify and interact properly with the phone
https://forum.xda-developers.com/t/...with-windows-as-virtualboxs-guest-os.1391189/
Install ClockworkMod Bootloader and Cyanogen 7 ROM to Samsung G5 I5500
https://forum.xda-developers.com/t/...d-cyanogen-7-rom-to-samsung-g5-i5500.1416190/
The "backup thread" with all the stuff for Galaxy 5 GT-I5500
https://forum.xda-developers.com/t/...rom-collection-for-galaxy-5-gt-i5500.3917603/
my gt-i5500 europe has the same error but i connect it to odin and my pc says that it doesn't recognize it and it shows the error code 10 can someone help me
progatillo said:
my gt-i5500 europe has the same error but i connect it to odin and my pc says that it doesn't recognize it and it shows the error code 10 can someone help me
Click to expand...
Click to collapse
First of all, are you using Windows XP, and the drivers +Odin from the backup thread? From what I remember, new versions of Windows don't seen to work with it, so you'll need to either setup a Virtual Machine or dig up an old of that you can run xp on.
Sanras said:
First of all, are you using Windows XP, and the drivers +Odin from the backup thread? From what I remember, new versions of Windows don't seen to work with it, so you'll need to either setup a Virtual Machine or dig up an old of that you can run xp on.
Click to expand...
Click to collapse
No i'm using Windows 10
progatillo said:
No i'm using Windows 10
Click to expand...
Click to collapse
Try using a Windows XP VM. Pass through the phone when it is in odin mode to the XP machine, then try to flash it using the XP VM and the drivers+odin provided.