Related
I seem to have bricked my Galaxy Tab 10.1 with LTE that was just purchased from Verizon a couple of days ago.
This all started as an attempt to root the phone so that I could get Netflix working (root required to install that Asus Transformer patch that some seem to need). Here is the process that I went through in order to install CWM:
Prerequisites:
Downloaded ODIN3 1.85.
Downloaded CWM 4.0.0.4 for the Galaxy Tab 10.1.
Plugged the tablet into my PC (Windows 7 Ultimate SP1 x64) while booted into the OS to confirm that drivers worked and it was detected properly.
Plugged the tablet into my PC (Windows 7 Ultimate SP1 x64) while booted into the "Download Mode" to make sure that drivers worked and it was detected properly.
Main Process:
Launched ODIN3 (ran as administrator).
From within ODIN3, clicked on the "PDA" button and selected the MD5 file for the CWM 4.0.0.4 image.
Booted my Galaxy Tab 10.1 into "Download Mode".
Confirmed that the Galaxy Tab 10.1 said "Waiting USB Cable".
Plugged the Galaxy Tab 10.1 into my PC via USB.
Confirmed that the ODIN3 application detected the USB device.
Confirmed the Galaxy Tab 10.1 changed from "Waiting USB Cable" to "Connected! Press the [Start] of Odin3!!"
From within ODIN3, clicked on the "Start" button.
Result:
The patching process completed without any errors. I then shut down the device and then started back up and tried to boot into recovery mode. Nothing - just a blank screen.
I then thought that I might have to install the CWM from the Android Market in addition to flashing the ROM (this might have been an incorrect assumption but I am not very experienced in this process) so I downloaded and installed it. I then tried to flash the recovery ROM via the Clockwork application but it complained about not having superuser access.
At this point I figured I was in a bit over my head and I decided to just reset the device to factory defaults (assuming that it would reset to the stock boot loader as well). I then initiated the factory reset process from within Android, the device reset itself, I got the Samsung Galaxy Tab 10.1 logo and then nothing - a blank screen.
Ugh - I think I just bricked my device and I am not quite sure how to get the stock recovery ROM back on there (I think I am going to be sick).
If anyone could give any advice on how to get me out of this situation or post the stock recovery ROM from the Verizon 4G Galaxy Tab I would greatly appreciate it.
Can you boot into recovery manually(volume down and power button)? If you can (try doing a factory restore from within recovery) or as long as the device lights up there is a good chance you will be able to bring it back and be okay. also did you root the device?
tenbeau said:
Can you boot into recovery manually(volume down and power button)? If you can (try doing a factory restore from within recovery) or as long as the device lights up there is a good chance you will be able to bring it back and be okay.
Click to expand...
Click to collapse
Thanks for your reply, but when trying to boot into recovery (Volume Up + Power Button) all I get is a blank screen. The only area I can now get into is the "Download Mode".
dfxdeimos said:
Thanks for your reply, but when trying to boot into recovery (Volume Up + Power Button) all I get is a blank screen. The only area I can now get into is the "Download Mode".
Click to expand...
Click to collapse
Well that is still good. Just put the tab into download mode and Odin it back to the original stock rom with super user.
Update:
I was able to get my tablet back from the brink late yesterday evening by doing the following:
Taking the CWM 4.0.0.4 image that was giving me the checksum error, extracting it from the tar.md5 file, and putting it back in a regular tar file.
Flashing the newly created .tar file back to the device via ODIN3.
I am still unable to boot into recovery mode (I just get a blank screen) but the main ROM booted and the system is usable. Unfortunately I don't have a backup of my stock recovery ROM to restore to the device.
Does anyone know if it still exists on the device somewhere that it can be pulled from and then reflashed?
Thanks to everyone for their responses and lack of mockery.
I've done the same thing. I did all my root research, flashed, then after it didn't work realized that it was for the wifi only version. I didn't know the 4g version was only 7 days old!
Once developers work on the tablet a little bit they'll have a fix for everything. We just need to wait at this point.
Somebody will likely have a full odin flash available soon.
dfxdeimos said:
Update:
I was able to get my tablet back from the brink late yesterday evening by doing the following:
Taking the CWM 4.0.0.4 image that was giving me the checksum error, extracting it from the tar.md5 file, and putting it back in a regular tar file.
Flashing the newly created .tar file back to the device via ODIN3.
I am still unable to boot into recovery mode (I just get a blank screen) but the main ROM booted and the system is usable. Unfortunately I don't have a backup of my stock recovery ROM to restore to the device.
Does anyone know if it still exists on the device somewhere that it can be pulled from and then reflashed?
Thanks to everyone for their responses and lack of mockery.
Click to expand...
Click to collapse
Hey there... Can you elaborate on your 'extraction' process?
I too, did something similar -- here's my story:
I just got my 10.1 4G LTE and was able to root it using the exploit.zip file (I think someone referred to it as the '3G' method). I didn't use ODIN at all, just rebooted in stock recovery (power up then upon seeing Samsung logo, press Vol+) and applied the .zip file. I know I had root because I was able to install and use titanium backup and root explorer.
Unfortunately, I saw another comment in a thread that said to download the ROM manager and install CWM recovery through that application. In my haste I did so and now, all I get is a continual boot loop at the Samsung logo. I can get nowhere past this. I tried holding down the power key for 10 secs and it appears to power down, but then it shortly starts back up again.
If I power up and hit Vol+ when seeing the Samsung logo, I do see the two icons (the right icon says "Downloading")... When I select the left icon, it screen blanks out and boot loops - shouldn't I see the recovery menu? I have not tried selecting the Downloading icon just cause I'm not sure what's beyond that step.
I have not been able to boot up completely, as some have said they were able to do. I've not used ODIN, and it seems like the way to go, but just wanted to get advice from those who know more than me, prior to making another mistake.
Maybe it's a quick fix to boot? Another key combo I don't know about?
Any help would be GREATLY appreciated!
Thanks
i did the same thing and have the same problem
djohnasantiago said:
Hey there... Can you elaborate on your 'extraction' process?
I too, did something similar -- here's my story:
I just got my 10.1 4G LTE and was able to root it using the exploit.zip file (I think someone referred to it as the '3G' method). I didn't use ODIN at all, just rebooted in stock recovery (power up then upon seeing Samsung logo, press Vol+) and applied the .zip file. I know I had root because I was able to install and use titanium backup and root explorer.
Unfortunately, I saw another comment in a thread that said to download the ROM manager and install CWM recovery through that application. In my haste I did so and now, all I get is a continual boot loop at the Samsung logo. I can get nowhere past this. I tried holding down the power key for 10 secs and it appears to power down, but then it shortly starts back up again.
If I power up and hit Vol+ when seeing the Samsung logo, I do see the two icons (the right icon says "Downloading")... When I select the left icon, it screen blanks out and boot loops - shouldn't I see the recovery menu? I have not tried selecting the Downloading icon just cause I'm not sure what's beyond that step.
I have not been able to boot up completely, as some have said they were able to do. I've not used ODIN, and it seems like the way to go, but just wanted to get advice from those who know more than me, prior to making another mistake.
Maybe it's a quick fix to boot? Another key combo I don't know about?
Any help would be GREATLY appreciated!
Thanks
Click to expand...
Click to collapse
any help would be greatly appreciated
By extraction I mean that I used WinRAR to extract the image file from the tar.md5 file and compressed it back into a tar file. I then flashed it via ODIN. This got rid of the checksum error and allowed me to boot into the normal ROM. Recovery mode was still messed up though.
Here is the link to all the Samsung factory firmware with instructions on how to load that you need. Hope this helps. Follow me! to the bottom of that page.
tdavis42 said:
Here is the link to all the Samsung factory firmware with instructions on how to load that you need. Hope this helps. Follow me! to the bottom of that page.
Click to expand...
Click to collapse
Thanks, but they don't have the firmware for the SCH-I905 yet...
tdavis42 said:
Here is the link to all the Samsung factory firmware with instructions on how to load that you need. Hope this helps. Follow me! to the bottom of that page.
Click to expand...
Click to collapse
There is no Verizon GTab 10.1 firmware there, the model # is SCH-I905
You guys seem to be flashing the recovery meant for the wifi version, which, as you can see, does not work with the mobile network models...
Before following a rooting guide, make sure that the method is proven to work on the mobile network version...
Sent from my GT-P7510 using Tapatalk
http://forum.xda-developers.com/showthread.php?t=1205639
Try this thread. It's meant for the LTE recovery.
This is a ODIN flashable for VZW LTE Tab 10.1 ONLY for working CWM recovery.
I'll add another post with the stock recovery also for the LTE version.
STOCK RECOVERY for VZW LTE Tab 10.1 ODIN Flashable. (HC-3.1 LTE)
Hope this helps anyone that needs it or made the same mistake I did. This only fixes if you used Rom Manager to Flash recovery (that is made for the non-LTE version) and get the black screen when trying to get into recovery.
I'll try to dump my entire stock F/W today and post that someplace too for people that are totally hosed like I was yesterday. (Boot/System/etc/etc)
http://www.mediafire.com/?3bznb9x3fdiv64n
I just made another ODIN file.. this one has the recovery, boot, and system if someone can test it. It is rooted and has the CWM recovery but stock other than that.
Hope this helps someone.
mattj949 said:
http://www.mediafire.com/?3bznb9x3fdiv64n
I just made another ODIN file.. this one has the recovery, boot, and system if someone can test it. It is rooted and has the CWM recovery but stock other than that.
Hope this helps someone.
Click to expand...
Click to collapse
Matt, would you mind making one of these without root and with the stock recovery? A complete return to its fresh out-of-the-box state?
I used your recovery image and was able to install it via ODIN, but now I need to unroot so I can return this thing.
Thanks for all of your work up to this point!
Scott
Might be easier to unroot it locally but yes I can.. I'll try to make one tomorrow.
mattj949 said:
Might be easier to unroot it locally but yes I can.. I'll try to make one tomorrow.
Click to expand...
Click to collapse
Do you mean via the command line? I don't want you to work on it if it's not necessary. I just need to lock this sucker back up before I have Verizon replace it!
Hi all!
I have a Samsung Galaxy S2 which I since a week cannot start. It get stuck on the black/white samsung logo. I cannot enter recovery mode, nothing happens when releasing the power button after pressing volumeup+home+power buttons. I can however reach download mode. I'm not sure what caused this problem, one day I just couldn't start it. I read on forums that many similar problems seem to have occurred when upgrading android but I'm not sure this is the case here (unless the phone made an automatic update while I was asleep). I'm not sure what version of android I'm running, but I'm pretty sure it is at least the ICS.
I would like to hard reset my phone if possible. It seems to be easiest through the recovery mode which I cannot get into.. I read things about Odin, connecting the phone to the computer and downloading android to the phone but haven't quite grasped it. Could anyone explain this option for me or point me in the right direction? Are there other options?
I would appreciate any help, especially since my 1-year warranty expired a month ago!
Best regards,
Marcus
marlu873 said:
Hi all!
I have a Samsung Galaxy S2 which I since a week cannot start. It get stuck on the black/white samsung logo. I cannot enter recovery mode, nothing happens when releasing the power button after pressing volumeup+home+power buttons. I can however reach download mode. I'm not sure what caused this problem, one day I just couldn't start it. I read on forums that many similar problems seem to have occurred when upgrading android but I'm not sure this is the case here (unless the phone made an automatic update while I was asleep). I'm not sure what version of android I'm running, but I'm pretty sure it is at least the ICS.
I would like to hard reset my phone if possible. It seems to be easiest through the recovery mode which I cannot get into.. I read things about Odin, connecting the phone to the computer and downloading android to the phone but haven't quite grasped it. Could anyone explain this option for me or point me in the right direction? Are there other options?
I would appreciate any help, especially since my 1-year warranty expired a month ago!
Best regards,
Marcus
Click to expand...
Click to collapse
Sounds like the symptoms of a NAND RW corruption. Try this http://forum.xda-developers.com/showthread.php?t=1457458
Hi Marcus,
I had the same problem few days back.
If it's not broken by you trying something fancy, the best solution is to take it to service centre. If you have rooted your device, had installed some custom firmware or are not willing to visit the service centre for some other reason, please read ahead.
All I did was,
Installed USB connectivity drivers through Kies.
Installed ODIN 1.83
Ensured that Kies or any of its processes are not running in background.
Downloaded the official SGS2 firmware
Flashed the firmware through ODIN.
It took around 10 minutes for the full process and I was having my mobile up and running. Using ODIN sounds scary initially if you haven't used it. I have slowly started gaining confidence in it after using it a few times.
Please note that though the process is well proven to be safe, there is still an amount of risk involved.
Sent from my GT-I9100
Download a siyah kernel(like v4.0.1) .tar file and flash through odin.
See if that makes it boot/lets you into recovery.
Adarzannh said:
Sounds like the symptoms of a NAND RW corruption. Try this http://forum.xda-developers.com/showthread.php?t=1457458
Click to expand...
Click to collapse
I appreciate all of your answers!
Adarzannh: I tried the guide but when flashing using odin I get stuck on:
<ID:0/003> NAND Write Start!!
both when trying to flash the recovery package and the kernel. Any clues?
mananbdesai: where do I find the "official SGS2 firmware"?
theunderlining: is it enough just to flash a new kernel or do I afterwards need to flash ROM too?
marlu873 said:
Adarzannh: I tried the guide but when flashing using odin I get stuck on:
NAND Write Start!!
both when trying to flash the recovery package and the kernel. Any clues?
Click to expand...
Click to collapse
A couple of things..ensure KIES is not running on your computer in the background. If possible delete it completely. Also ensure your phone is connected to a USB port directly on the computer and not via a hub or to a USB port on a keyboard or something. Odin is a finicky s/w..so..
Also, try different versions. If v1.85 doesn't work try v3.4
marlu873 said:
mananbdesai: where do I find the "official SGS2 firmware"?
Click to expand...
Click to collapse
Go to sammobile.com or a sticky in the Original Android Development section here..has links to all the stock firmwares.
marlu873 said:
theunderlining: is it enough just to flash a new kernel or do I afterwards need to flash ROM too?
Click to expand...
Click to collapse
Lol at underlining. if you flash a custom kernel like siyah, you'll be rooted and get CWM. Using that you can install a custom ROM.
Sent from my GT-I9100 using xda app-developers app
And youll be safe from the 4.0.4 brickbug if you flash siyah.
You flash a kernel for various reasons like it has emmc cap disabled,you can tweak it etc.
You can flash siyah kernel and stop there.Or you can move onto a custom rom.
Whatever,when its done-backup your efs and make a nand backup.
And yesterday I was downgrading my wifes phone onto 4.0.3.I was using odin and kept getting "failed".After 3 attempts I realised I hadnt put the phone into download mode..........how stupids that......lol
hi there, just wondering, after Flashing the stock firmware through ODIN, do you lose everything in your phone? i need to get all the notes that I have in my phone (notes from the samsung stock apps). I dont have any external sd card in the phone. thanks in advance for the reply.
enquiry
marlu873 said:
Hi all!
I have a Samsung Galaxy S2 which I since a week cannot start. It get stuck on the black/white samsung logo. I cannot enter recovery mode, nothing happens when releasing the power button after pressing volumeup+home+power buttons. I can however reach download mode. I'm not sure what caused this problem, one day I just couldn't start it. I read on forums that many similar problems seem to have occurred when upgrading android but I'm not sure this is the case here (unless the phone made an automatic update while I was asleep). I'm not sure what version of android I'm running, but I'm pretty sure it is at least the ICS.
I would like to hard reset my phone if possible. It seems to be easiest through the recovery mode which I cannot get into.. I read things about Odin, connecting the phone to the computer and downloading android to the phone but haven't quite grasped it. Could anyone explain this option for me or point me in the right direction? Are there other options?
I would appreciate any help, especially since my 1-year warranty expired a month ago!
Best regards,
Marcus
Click to expand...
Click to collapse
Hi there sir,
Has the problem solved ? Care to share the solution ?
Thanks.
i had the same exact problem, i tried flashing with odin n stock firmware but stuck in NAND write start, i didnt try flashing with PIT & repartition though, i couldnt be bothered anymore, so i took it to samsung service plaza, they told me the problem is in the main PCB (hardware issue), so all they did was replace that n it got fixed! i didnt pay because it's still under contract/ carrier warranty
Can you get into downloading mode? It's by hold and pressing volume down+home+power
Sent from my GT-I9100 using xda premium
it seems for some strange reason the phone wont turn on now. Wheni plug it in i get the blue flashing dot but its faint. Tried download mode and nothing.
same problem
araz.rozh said:
Can you get into downloading mode? It's by hold and pressing volume down+home+power
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
my phone is stuck at the bootlogo too. but mine is rooted n running on biftor rom (jellybean) pls how do i flash with odin? thanks
help pls.
Pls guys I have the same problem but like I said earlier mine occurred while I waS tRyna backup my ROM. Plss can I get a detailed guide on how to flaSh my samsung galaxy SII GT19100. ItS verion; jelly bean 4.12.Its rooted n runs on a custom ROM( biftor). Plss guys help. Thank you.
tatchero said:
Pls guys I have the same problem but like I said earlier mine occurred while I waS tRyna backup my ROM. Plss can I get a detailed guide on how to flaSh my samsung galaxy SII GT19100. ItS verion; jelly bean 4.12.Its rooted n runs on a custom ROM( biftor). Plss guys help. Thank you.
Click to expand...
Click to collapse
I had a similar problem, stuck at boot with Biftor v12, which happened after I tried to update SuperSU binary through CWM/TWRP. I don't know why it stuck at boot and why it wouldn't reboot to Recovery. Download mode was still working, so I had no choice but to flash new kernel through ODIN and see if it works.
So if your symptoms sound similar to mine, here's what I did to be able to boot again:
I REPEAT, SIMILAR TO MINE. MY SOLUTION MIGHT NOT NECESSARILY APPLY TO YOURS.
1. Download a suitable kernel in tar.md5 format. I used PhilZ-cwm6 v4.93.6 for XWLSN firmware (see OP http://forum.xda-developers.com/showthread.php?t=1877270)
2. Download ODIN, if you don't have it, found here http://forum.xda-developers.com/showthread.php?t=2189539
3. Once installed, boot your phone in Download mode by pressing Vol Down+Home+Power together until you see a warning dialog. Press Vol UP to get into download mode.
4. Make sure ODIN is running, and NO KIES processes are running.
5. Connect your phone with USB cable to your PC.
6. In ODIN, you should see a COM port with yellow background.
7. Click the PDA button ONLY.
8. Select the kernel file you downloaded.
9. Press Start and nothing else.
10. If everything went as expected, your phone should reboot after a while with a working Recovery.
Only do the steps if you are absolutely sure. This worked for me, and I hope it gives some tips for your problem as well.
Flash-IS-Bright said:
I had a similar problem, stuck at boot with Biftor v12, which happened after I tried to update SuperSU binary through CWM/TWRP. I don't know why it stuck at boot and why it wouldn't reboot to Recovery. Download mode was still working, so I had no choice but to flash new kernel through ODIN and see if it works.
So if your symptoms sound similar to mine, here's what I did to be able to boot again:
I REPEAT, SIMILAR TO MINE. MY SOLUTION MIGHT NOT NECESSARILY APPLY TO YOURS.
1. Download a suitable kernel in tar.md5 format. I used PhilZ-cwm6 v4.93.6 for XWLSN firmware (see OP http://forum.xda-developers.com/showthread.php?t=1877270)
2. Download ODIN, if you don't have it, found here http://forum.xda-developers.com/showthread.php?t=2189539
3. Once installed, boot your phone in Download mode by pressing Vol Down+Home+Power together until you see a warning dialog. Press Vol UP to get into download mode.
4. Make sure ODIN is running, and NO KIES processes are running.
5. Connect your phone with USB cable to your PC.
6. In ODIN, you should see a COM port with yellow background.
7. Click the PDA button ONLY.
8. Select the kernel file you downloaded.
9. Press Start and nothing else.
10. If everything went as expected, your phone should reboot after a while with a working Recovery.
Only do the steps if you are absolutely sure. This worked for me, and I hope it gives some tips for your problem as well.
Click to expand...
Click to collapse
Hi Flash-IS-Bright
I have the exact same problem with SuperSU on my rooted Galaxy S2. I updated the SuperSU app, and when I opened it, it recommended me to update the binary, I selected the CWM/TWRP option and then my phone tried to reboot but is now stuck. It can only access download mode.
In doing the process above, you only flashed the kernel? Did this totally work? And all your apps/messages were left intact on your phone?
Any help is appreciated.
peshmann said:
Hi Flash-IS-Bright
I have the exact same problem with SuperSU on my rooted Galaxy S2. I updated the SuperSU app, and when I opened it, it recommended me to update the binary, I selected the CWM/TWRP option and then my phone tried to reboot but is now stuck. It can only access download mode.
In doing the process above, you only flashed the kernel? Did this totally work? And all your apps/messages were left intact on your phone?
Any help is appreciated.
Click to expand...
Click to collapse
when ur updating the binary u should always choose the 'Normal' thing instead of the 'CWM/TWRP' one ma8
if u flash a kernel it will not delete anything on ur phone, all u have to do is to select the right kernel like 'Philz' for example (if ur on a stock JB firmware) and flash the same through 'ODIN' and reboot ur phone
Sun90 said:
when ur updating the binary u should always choose the 'Normal' thing instead of the 'CWM/TWRP' one ma8
if u flash a kernel it will not delete anything on ur phone, all u have to do is to select the right kernel like 'Philz' for example (if ur on a stock JB firmware) and flash the same through 'ODIN' and reboot ur phone
Click to expand...
Click to collapse
Thanks for your help. I've originally had Jeboo 1.2 kernel on my phone and tried to reflash that again through Odin. It passed, however I'm still encountering the same problem of the bootloop.
Would flashing a different kernel help? I'm on stock JB firmware but with a Jeboo kernel. I am happy to try another kernel (if that would not brick my phone)
Do you have any other suggestions to help me solve this?
Again thanks for your help
peshmann said:
Thanks for your help. I've originally had Jeboo 1.2 kernel on my phone and tried to reflash that again through Odin. It passed, however I'm still encountering the same problem of the bootloop.
Would flashing a different kernel help? I'm on stock JB firmware but with a Jeboo kernel. I am happy to try another kernel (if that would not brick my phone)
Do you have any other suggestions to help me solve this?
Again thanks for your help
Click to expand...
Click to collapse
You could try flashing hawkerpaul's kernel wiper first and then install another stock kernel like PhilZ or Apollo, and see if that helps.
Neat Rom lite,suddenly struck in boot loop after 1 month of operation.
Dear All,
I have installed the "I9100XWLSZ_NeatROM_Lite_v5.0.1" custom rom and after 1 month of successful usage, today suddenly the phone was dead.(probably due to autoupdates over wifi) . I tried to reboot, but didnt. Tried to restart but got stuck in the logo screen with yellow triangle.
Tried to enter recovery mode, but no use. Only download mode is possible.
Tried to flash the stock rom using odin, but no use, Nand write failed.
Can somebody help me how to come out of this situation. Shall I install a different kernal and see?
Regards,
Maka11
Hi Guys,
Sorry to bother you with this, but I'm out of ideas...
I decided to root my i9100 using this guide9.
As I was doing this, the recovery rom would reboot when using the volume buttons to navigate (only on the first "page") - This was easily worked around by using the touchscreen, but now I'm wondering if this was the start of my issues...
I applied the SU busy box installer, and got root. I installed rom manager, and noticed that it seemed to lock up when doing certain things. I put this down to CWM saying there was no official mod for the i9100.
The next day I decided to try and install a CM10.1 nightly, so I took a backup, wiped cache and data, and applied the rom and gapps.
When I rebooted, the phone wouldn't finished booting, it just sat at the initial logo screen.
After that, I tried following this recovery guide but the odin flash failed at around 80% (I retried and the same happened again).
Since then I've had difficulty getting in to recovery mode. I've tried flashing various stock roms with odin, and trying to restore with Kies.
In Kies I get as far as it conencting to the phone in download mode, but it pops up a "notice" in a foreign language - presumably Korean (and I can't copy the text to even attempt a google translation).
I tried flashing Siyah-s2-v5.0.1 to get a different recovery - that seemed to have a garbled progress bar, before hanging when I tried to wipe /data again.
When I use odin to flash a stock rom - is it supposed to restore absolutely everything? I'm not sure how I'm still getting problems if this is the case. Any ideas on what to try next?
(The current stock rom I'm try ing to use is this one)
Let me know if I'm missing any info, and thanks in advance for any help.
Using rom manager would have been the start of your problems-not the temp cwm recovery in the rooting guide.
If you can boot into download mode then I would download LP7 stock rom, disable kies and flash that with Odin.
{go back to your iphone since you are an android noob}
Thanks for the reply.
Rom manager didn't work properly for me, so I stopped using it. I used the temp cwm recovery to install the CM nightly.
I can boot in to download mode, but I've already tried an LP7 rom, - as with the others, it doesn't boot.
Any ideas on how to tell why it isn't booting? logcat doesn't seem to want to to work. Not sure if it's broken / too early in the boot process / etc
Silly Billy said:
Thanks for the reply.
Rom manager didn't work properly for me, so I stopped using it. I used the temp cwm recovery to install the CM nightly.
I can boot in to download mode, but I've already tried an LP7 rom, - as with the others, it doesn't boot.
Any ideas on how to tell why it isn't booting? logcat doesn't seem to want to to work. Not sure if it's broken / too early in the boot process / etc
Click to expand...
Click to collapse
I9100 right?
Try this:
- Download this ROM.
- Kies installed? uninstall it, re install it. Close it all up with Task manager (3 or 4 applications running).
- Flash ROM via Odin (CSC, MODEM, PHONE).
- If that doesn't fly, try another usb port & usb cable. Another PC would also be recommended.
- Repeat the process.
- Still no luck? try flashing a previous siyah version.
- No go? repeat all the above.
- Let us know how you did.
gastonw;37017081- Download this ROM.[/QUOTE said:
Thanks, I'll give it a go. (Will take a while for the file to download from hotfile...).
Are odin images for stock roms supposed to restore the stock recovery, or do they leave that alone?
Click to expand...
Click to collapse
As a matter of interest, how far did you go with Phistachios repair guide.
{go back to your iphone since you are an android noob}
Silly Billy said:
Thanks, I'll give it a go. (Will take a while for the file to download from hotfile...).
Are odin images for stock roms supposed to restore the stock recovery, or do they leave that alone?
Click to expand...
Click to collapse
Focus on getting a ROM to boot.
That ROM will install stock recovery.
gastonw said:
Let us know how you did.
Click to expand...
Click to collapse
For some reason, I can't get Odin to flash that rom - it just hands for a while at the start of data.img, before saying "Complete(Write) operation failed."
There a .pit file in the archive, although the link says not to repartition (so I didn't).
Some roms seem to get written, some don't, I'm not sure why...
theunderling said:
As a matter of interest, how far did you go with Phistachios repair guide.
Click to expand...
Click to collapse
Odin failed about 80% through flashing (step 4, after taking the ICS steps). I tried flashing the kernel afterwards, which flashed, but didn't help with my boot issues.
gastonw said:
Focus on getting a ROM to boot.
That ROM will install stock recovery.
Click to expand...
Click to collapse
Of course, I was just trying to get a better understanding of how things work - I'd settle for anything booting right now.
I was meaning how far did you go with his guide.He says (near the end) to flash a bootloader/kernel/rom.
You can try everything in his guide, but understand about the risks involved with pit and bootloaders.
{go back to your iphone since you are an android noob}
theunderling said:
I was meaning how far did you go with his guide.He says (near the end) to flash a bootloader/kernel/rom.
You can try everything in his guide, but understand about the risks involved with pit and bootloaders.
{go back to your iphone since you are an android noob}
Click to expand...
Click to collapse
He's right.
Keep trying, consider pit files & bootloaders as a last resort.
Tried everything?
Used another usb cable for the flash? tried in another PC? tried in a laptop?
Are you sure kies is all shut down?
I've read about so many people having the same issue than you, they keep on flashing as in trial & error and most times they come out winners.
GL!
gastonw said:
He's right.
Keep trying, consider pit files & bootloaders as a last resort.
Tried everything?
Used another usb cable for the flash? tried in another PC? tried in a laptop?
Are you sure kies is all shut down?
I've read about so many people having the same issue than you, they keep on flashing as in trial & error and most times they come out winners.
GL!
Click to expand...
Click to collapse
I guess I'll keep at it then.
I'd tried another cable with kies shut down. Just tried a different machine, and flashed the ROM you suggested with heimdall. It flashed without complaining (unlike odin), but I'm still getting a boot loop.
Looking at the initial recovery guide I was following - I suspect that I might've flashed the bootloader (the guide shows in bold which file goes in which box, so I probably loaded them all). Maybe this is the source of my troubles...
I also noticed that heimdall can pull data from the phone too - if I can pull and mount these, am I likely to find any useful log files?
For completeness (and anyone else who finds themselves with the same issue): It seems I hit the EMMC brick bug, which rendered some of my EMMC storage unusable.
This helpful chap came up with a workaround to partition around the dead space. (Please read the post carefully and make sure this really is your problem before flashing!)
That method will let you know what part of your memory is corrupted. It's done via recovery as far as I remember.
Did you bring your device back to life?
Sent from the little guy
gastonw said:
That method will let you know what part of your memory is corrupted. It's done via recovery as far as I remember.
Did you bring your device back to life?
Click to expand...
Click to collapse
Yes, that's right. IIRC, I flashed a working recovery with Odin, then did most of the work from adb shell.
I got my device back to life for the most part. I get the occasional hang but haven't investigated much (have since bought a Nexus 4, so not using the S2 so much).
Just thought I'd share for the next poor soul who has the same problem
Please help. I have a Samsung Galaxy SII i777 (AT&T) that is constantly rebooting. It gets to the "Galaxy SII" logo and restarts itself. It started doing this while the phone was on the charger and was running slow. I decided to restart my phone and it hasn't worked since.
The phone has the stock firmware and has never been rooted. I am new to flashing anything to a phone. Can someone walk me through how to get my phone usable again? I downloaded Odin3 v3.09, but am completely lost on what to do next. Also, is there any way to recover my pictures?
Thank you for your help.
It might help to boot to recovery (power and both volume buttons) and wipe data and cache. You would not lose your pictures but you'd have to reinstall all your apps.
Sent from my GT-p511x
As Sharon stated your best bet would be to boot into recovery.
I believe to do this on the s2 you'll press and hold the up volume key and the power key until you see the Samsung logo then release the power key and hold volume up until android system recovery loads. If that doesn't work then try again with both volume keys.
One in the recovery do as Sharon suggested and if that doesn't work check to see what's on your SD card and if you're OK with losing whatever data isn't backed up I would recommend doing a factory data reset.
If your still having issues you could try doing an emergency firmware recovery with the Samsung kies software or flashing stock ROM.
Other than that you can contact Samsung and see if you're still under warranty for repair if its hardware related.
Hope this helps. Good luck with getting the phone up and running
Sent from CM 10.2 optimized sph-l710
@TKEBH964,
I'm not sure that performing a wipe data/factory reset from within recovery will solve your problem. It is, however, the first thing to try. It will not remove your photo album, so that will be safe.
Please post your results. If wiping doesn't solve the problem, then we will be happy to help you with the troubleshooting process.
sharonbw said:
It might help to boot to recovery (power and both volume buttons) and wipe data and cache. You would not lose your pictures but you'd have to reinstall all your apps.
Sent from my GT-p511x
Click to expand...
Click to collapse
I tried this and the phone says "Deleting cryption meta data" then goes back to the reboot loop it was doing before.
ShadowCodes said:
As Sharon stated your best bet would be to boot into recovery.
I believe to do this on the s2 you'll press and hold the up volume key and the power key until you see the Samsung logo then release the power key and hold volume up until android system recovery loads. If that doesn't work then try again with both volume keys.
One in the recovery do as Sharon suggested and if that doesn't work check to see what's on your SD card and if you're OK with losing whatever data isn't backed up I would recommend doing a factory data reset.
If your still having issues you could try doing an emergency firmware recovery with the Samsung kies software or flashing stock ROM.
Other than that you can contact Samsung and see if you're still under warranty for repair if its hardware related.
Hope this helps. Good luck with getting the phone up and running
Sent from CM 10.2 optimized sph-l710
Click to expand...
Click to collapse
Holding volume up doesn't do anything. I did try with volume down and it get "Warning custom OS can cause critical problems in phone and installed applications. If you want to download a custom OS, press the volume up key. Otherwise, press the volume down key to cancel." Cancel will restart phone to infinite boot loop again. When I continue it says "ODIN MODE" at the top shows the green android guy and says "Downloading... Do not turn off target !!" The phone never downloads anything and will stay in that state forever.
creepyncrawly said:
@TKEBH964,
I'm not sure that performing a wipe data/factory reset from within recovery will solve your problem. It is, however, the first thing to try. It will not remove your photo album, so that will be safe.
Please post your results. If wiping doesn't solve the problem, then we will be happy to help you with the troubleshooting process.
Click to expand...
Click to collapse
I can't seem to get the phone to do a factory reset.
What next?
TKEBH964 said:
I tried this and the phone says "Deleting cryption meta data" then goes back to the reboot loop it was doing before.
Click to expand...
Click to collapse
This indicates nand read/write corruption.
Holding volume up doesn't do anything. I did try with volume down and it get "Warning custom OS can cause critical problems in phone and installed applications. If you want to download a custom OS, press the volume up key. Otherwise, press the volume down key to cancel." Cancel will restart phone to infinite boot loop again. When I continue it says "ODIN MODE" at the top shows the green android guy and says "Downloading... Do not turn off target !!" The phone never downloads anything and will stay in that state forever.
Click to expand...
Click to collapse
Download mode is used in conjunction with Odin3 and a windows computer to install both stock and custom firmware.
I can't seem to get the phone to do a factory reset.
What next?
Click to expand...
Click to collapse
There is a very specific instruction set for clearing nand r/w corruption. Before I give you the instructions, I need to know which operating system was on your phone. Had you updated to the latest firmware, UCMD8 4.1.2 Jelly Bean? Or was it still on an earlier version?
creepyncrawly said:
This indicates nand read/write corruption.
Download mode is used in conjunction with Odin3 and a windows computer to install both stock and custom firmware.
There is a very specific instruction set for clearing nand r/w corruption. Before I give you the instructions, I need to know which operating system was on your phone. Had you updated to the latest firmware, UCMD8 4.1.2 Jelly Bean? Or was it still on an earlier version?
Click to expand...
Click to collapse
I bought my phone in April of 2012 and have never updated it, basically because I didn't want to deal with something going wrong. A lot of good that did me...
I really appreciate your help.
TKEBH964 said:
I bought my phone in April of 2012 and have never updated it, basically because I didn't want to deal with something going wrong. A lot of good that did me...
I really appreciate your help.
Click to expand...
Click to collapse
AT&T didn't release ICS 4.0.3 UCLE5 until about June of 2012, so I'm going to assume that you still have Gingerbread, either the original 2.3.4 UCKH7, or the 2.3.6 UCKK6 firmware.
1)Go to this post and download the Tar version of Siyah 2.6.14 Kernel. Use Odin3 v1.85 which you can get from near the top of the Download Repository and flash it in the PDA slot without ticking Re-Partitioning.
How to use stand-alone Odin3 to flash firmware:
Follow and recheck each of the following steps. Do them in order listed, as some steps are dependent on previous steps. Instructions are for Odin3 v1.85. It should work with any version of Odin, but some details, like color of items, may be different.
1.) Open Odin on the Windows Desktop.
2.) Have the USB cable plugged into USB port on the computer, but *Not* plugged in to the phone.
3.) Shut the phone off.
4.) While holding down the vol+ & vol- keys, plug micro-usb plug into phone.
5.) In Odin, you should get the yellow box under where it says ID:COM with the text 0:[COMx], and in the Message area, <ID:0/00x> Added!! where x is some number, usually 1-8.
6.) In Odin, make sure Auto Reboot and F. Reset Time are checked and all other items are not checked.
7.) Click on the PDA button. Browse to the tar file you want to install and select it so its path appears in the text edit box next to the button.
8.) Make sure the check box next to the PDA button is checked.
9.) Click the Start button.
10.) You should see the green progress bar advancing.
11.) When completed, you will get a "PASS"
Click to expand...
Click to collapse
2) Successful? Next, flash the full stock Gingerbread distribution from the Download Repository, from the section headed I777UCKH7-CL503881 Stock Binaries including the bootloaders and everything, in the PDA slot.
3) If that is successful and the phone boots normally, you are done. If it is not, then enter recovery and perform a wipe data/factory reset. If still not, then:
4) Download the SBL Bootloader from the Download Repository. Flash it as PDA in ODIN, without ticking Re-Partitioning.
5) Flash the Kernel, as in step 1.
6) Flash the full stock Gingerbread distribution, as in step 2.
If you are unable to get any of these to flash successfully (you don't get a PASS), first you should assume a bad port, or bad cable, and try other ports, other cables, even another pc.
I'm doubt you would have damaged memory, but just in case, here is the info.
(If you can get no flash to succeed, then you may have damaged eMMC memory. In case it is damaged memory, see this post from Mobile Tech Videos.)
creepyncrawly said:
AT&T didn't release ICS 4.0.3 UCLE5 until about June of 2012, so I'm going to assume that you still have Gingerbread, either the original 2.3.4 UCKH7, or the 2.3.6 UCKK6 firmware.
1)Go to this post and download the Tar version of Siyah 2.6.14 Kernel. Use Odin3 v1.85 which you can get from near the top of the Download Repository and flash it in the PDA slot without ticking Re-Partitioning.
2) Successful? Next, flash the full stock Gingerbread distribution from the Download Repository, from the section headed I777UCKH7-CL503881 Stock Binaries including the bootloaders and everything, in the PDA slot.
3) If that is successful and the phone boots normally, you are done. If it is not, then enter recovery and perform a wipe data/factory reset. If still not, then:
4) Download the SBL Bootloader from the Download Repository. Flash it as PDA in ODIN, without ticking Re-Partitioning.
5) Flash the Kernel, as in step 1.
6) Flash the full stock Gingerbread distribution, as in step 2.
If you are unable to get any of these to flash successfully (you don't get a PASS), first you should assume a bad port, or bad cable, and try other ports, other cables, even another pc.
I'm doubt you would have damaged memory, but just in case, here is the info.
(If you can get no flash to succeed, then you may have damaged eMMC memory. In case it is damaged memory, see this post from Mobile Tech Videos.)
Click to expand...
Click to collapse
I was successful with step 1!! Thank you very much.
I am attempting step 2, but am a bit confused (sorry). There are 4 files under the heading "I777UCKH7-CL503881 Stock Binaries."
Which is the correct file?
I777UCKH7-CL503881-Full.7z
I777UCKH7-REV02-home-low-CL503881.tar.md5.7z
I777UCKH7-CL503881-Parts-NoBL.7z
I777UCKH7-CL503881-Bootloaders.7z
Again, I apologize for being slow at this, but I really appreciate your help.
TKEBH964 said:
I was successful with step 1!! Thank you very much.
I am attempting step 2, but am a bit confused (sorry). There are 4 files under the heading "I777UCKH7-CL503881 Stock Binaries."
Which is the correct file?
I777UCKH7-CL503881-Full.7z
>>>I777UCKH7-REV02-home-low-CL503881.tar.md5.7z<<<
I777UCKH7-CL503881-Parts-NoBL.7z
I777UCKH7-CL503881-Bootloaders.7z
Again, I apologize for being slow at this, but I really appreciate your help.
Click to expand...
Click to collapse
It's the one marked above. Download, unzip, and use I777UCKH7-REV02-home-low-CL503881.tar.md5 in the PDA slot of Odin.
creepyncrawly said:
It's the one marked above. Download, unzip, and use I777UCKH7-REV02-home-low-CL503881.tar.md5 in the PDA slot of Odin.
Click to expand...
Click to collapse
THANK YOU!!!
I did exactly as you said and everything appears to be normal again. All my pictures are still there too! I did make sure I did a backup of them all this time though. I do have to re-install all of my apps, but that's no biggie.
Again, THANK YOU, THANK YOU, THANK YOU!!!!
TKEBH964 said:
THANK YOU!!!
I did exactly as you said and everything appears to be normal again. All my pictures are still there too! I did make sure I did a backup of them all this time though. I do have to re-install all of my apps, but that's no biggie.
Again, THANK YOU, THANK YOU, THANK YOU!!!!
Click to expand...
Click to collapse
Pleased to be able to help.
Now you can use odin to flash the latest stock firmware. I would definitely recommend this. At the bottom of the page in the Download Repository, UCMD8 4.1.2 Jelly Bean.
(Optional) If you want, you can then root the phone, and then possibly install custom firmware. If you decide to and need help with it, study the guides, and then ask.
Hi, ad the title says i've bricked my player
I was on cm12 and tried to flash stock ROM from odin
I fkashed two times, the first one i got a bootloop, the second one the device got bricked :crying: , i can't do anything, it won't turno on or go into download mode :crying:
Please hekp me!
I've found a guide which tells about a program called unbrickble rezurrector, but i can't find the jar...
PLease help me i miss my player :crying: :crying:
Do you think that a USB jig will do the trick?
edoardog said:
Hi, ad the title says i've bricked my player
I was on cm12 and tried to flash stock ROM from odin
I fkashed two times, the first one i got a bootloop, the second one the device got bricked :crying: , i can't do anything, it won't turno on or go into download mode :crying:
Please hekp me!
I've found a guide which tells about a program called unbrickble rezurrector, but i can't find the jar...
PLease help me i miss my player :crying: :crying:
Click to expand...
Click to collapse
To power your device all the way off plug it in and hold power until the battery logo comes up.
Then unplug it and hold power, home, and volume down to boot into download mode.
Use odin (https://www.google.com/url?sa=t&rct...=ewT0JrvKAjyPbAfN2FyCTQ&bvm=bv.91071109,d.eXY) to flash the stock firmware form here:
http://forum.xda-developers.com/showthread.php?t=2192488
Androprise said:
To power your device all the way off plug it in and hold power until the battery logo comes up.
Then unplug it and hold power, home, and volume down to boot into download mode.
Use odin (https://www.google.com/url?sa=t&rct...=ewT0JrvKAjyPbAfN2FyCTQ&bvm=bv.91071109,d.eXY) to flash the stock firmware form here:
http://forum.xda-developers.com/showthread.php?t=2192488
Click to expand...
Click to collapse
hi, I've managed to make it boot into recovery by using unbrickable resurrector... now i've got another problem, I can't flash stock rom :crying:
I've followed adam outler guide to recover from a brick, but odin won't flash on the player! it just says SetupConnection..
<ID:0/004> Can't open the serial(COM) port! I can only make it go to download mode, and if I unplug it from the pc it shuts... I don't know what to do!
i don't think that the drivers are the problem, i can flash on my galaxy tab 3...
edoardog said:
hi, I've managed to make it boot into recovery by using unbrickable resurrector... now i've got another problem, I can't flash stock rom :crying:
I've followed adam outler guide to recover from a brick, but odin won't flash on the player! it just says SetupConnection..
<ID:0/004> Can't open the serial(COM) port! I can only make it go to download mode, and if I unplug it from the pc it shuts... I don't know what to do!
i don't think that the drivers are the problem, i can flash on my galaxy tab 3...
Click to expand...
Click to collapse
My player has sometimes had this problem with Odin 3.07. It has always worked fine with Odin 1.85 however. I have attached the Odin zip just extract it and run. If it still doesn't work try installing Samsung Kies (or re-install) to get the USB driver. Should that fail install the samsung mobile USB Driver (also attached).
Kies Link (Use Kies 2.6): http://www.samsung.com/us/kies/
Androprise said:
My player has sometimes had this problem with Odin 3.07. It has always worked fine with Odin 1.85 however. I have attached the Odin zip just extract it and run. If it still doesn't work try installing Samsung Kies (or re-install) to get the USB driver. Should that fail install the samsung mobile USB Driver (also attached).
Kies Link (Use Kies 2.6):
Click to expand...
Click to collapse
ok, thank you very much for your help
i managed to flash stockrom but the player won't turn on i don't know what happend
after it ends flashing it just shuts, it won't rebot... i don't know
edoardog said:
ok, thank you very much for your help
i managed to flash stockrom but the player won't turn on i don't know what happend
after it ends flashing it just shuts, it won't rebot... i don't know
Click to expand...
Click to collapse
I'm in a similar situation (bricked after cm12, no recovery, have let the battery die, gathering info on what to do next).
Here's a total guess, maybe the repartitioning for the cm12 is messing up the stock rom (did you have "repartition" checked in odin?) have you tried flashing cm11 or 12 instead of stock?
Also if this doesn't work try flashing with the pit file which can be found lower down on the same post as the stock ROMs.
TheRealBubba said:
I'm in a similar situation (bricked after cm12, no recovery, have let the battery die, gathering info on what to do next).
Here's a total guess, maybe the repartitioning for the cm12 is messing up the stock rom (did you have "repartition" checked in odin?) have you tried flashing cm11 or 12 instead of stock?
Click to expand...
Click to collapse
Hi, each time i flash in odin i check repartition and load the pit file...
how do I flash CM11 or CM12? I can't put it in recovery...
I think we are in the same situation, i was thinking... can't we make a CM11 or CM12 flashable tar file? i don't know if it's possibile, i'm a newbie and know only a little of android and similar OS...
uff, if the galaxy payer could only boot in recovery we could be able to flash one rom to fix it!
sorry for my bad english
edoardog said:
I think we are in the same situation, i was thinking... can't we make a CM11 or CM12 flashable tar file? i don't know if it's possibile, i'm a newbie and know only a little of android and similar OS...
uff, if the galaxy payer could only boot in recovery we could be able to flash one rom to fix it!
sorry for my bad english
Click to expand...
Click to collapse
I couldn't get mine into recovery either. I couldn't even get proper download mode. But, I used odin3 v1.85 (I also tried kies, and re-installing that may have installed drivers that turned out to be necessary, windows spent a lot of time searching for drivers... I'm a linux guy, I don't really understand how/why windows needs to spend 10 minutes searching for the same drivers again and again - whatever), and tried flashing lots of things, assorted pit files, roms and recoveries...
Eventually I managed to install a stock rom that I got from the first post in this thread:
http://forum.xda-developers.com/showthread.php?p=39188127
It installed correctly, but booted into an animation bootloop.
I cannot flash cwm on to it. When I boot into recovery I get the (stock?) android 3e recovery, and a screen full of red telling me that cache does not exist. None of the four options, reboot, install update zip from sd, wipe data/factory reset, wipe cache, do anything.
Stuck there now.
TheRealBubba said:
I couldn't get mine into recovery either. I couldn't even get proper download mode. But, I used odin3 v1.85 (I also tried kies, and re-installing that may have installed drivers that turned out to be necessary, windows spent a lot of time searching for drivers... I'm a linux guy, I don't really understand how/why windows needs to spend 10 minutes searching for the same drivers again and again - whatever), and tried flashing lots of things, assorted pit files, roms and recoveries...
Eventually I managed to install a stock rom that I got from the first post in this thread:
http://forum.xda-developers.com/showthread.php?p=39188127
It installed correctly, but booted into an animation bootloop.
I cannot flash cwm on to it. When I boot into recovery I get the (stock?) android 3e recovery, and a screen full of red telling me that cache does not exist. None of the four options, reboot, install update zip from sd, wipe data/factory reset, wipe cache, do anything.
Stuck there now.
Click to expand...
Click to collapse
I'm going to try to flash that, thank you for your respond... Windows can be relly slow in seraching driver, linux is a lot faster XD, yesterday i tried to flash my galaxy player from JODIN3, which is basically ODIN for LInux, the problem is, after it ends, it says SUCCESS!! but the player won't boot... Maybe the battery is dead this happens everytime I flash the pit and stock rom, ODIN says success but then it shuts, giving no life signs
This is a really strange problem even I tryed to flash everything (from kernels, to recovery, to stock roms and the bootloader which posted AdamOutler) we need to ask to an experienced dev what maybe has happend, ecause i relly have no idea
edoardog said:
I'm going to try to flash that, thank you for your respond... Windows can be relly slow in seraching driver, linux is a lot faster XD, yesterday i tried to flash my galaxy player from JODIN3, which is basically ODIN for LInux, the problem is, after it ends, it says SUCCESS!! but the player won't boot... Maybe the battery is dead this happens everytime I flash the pit and stock rom, ODIN says success but then it shuts, giving no life signs
This is a really strange problem even I tryed to flash everything (from kernels, to recovery, to stock roms and the bootloader which posted AdamOutler) we need to ask to an experienced dev what maybe has happend, ecause i relly have no idea
Click to expand...
Click to collapse
I'll look into JODIN3, messing around with Windows is so painfull. I would skip flashing the pit, just odin the one thing. I've also found that if odin fails flashing something, everything else I try flashing afterwards will fail. The only success I've had has been with disconnecting everything, plugging the device back into the PC, the starting odin new.
I've gotten a working gingerbread ROM, from here:
http://meticulus-development.com/index.php/galaxy-player-5-0-2/galaxy-player-5-0-stock-roms/
(irritating finding the download link among all the malware bull**** and "windows support" popups, it required registering for 4shared, but a throwaway email works)
The recovery is still a native samsung android 3e, and it took me a while to figure out that the "select" key wasn't the power button, but the home softkey... That might have been true of the last one I had flashed, the one that bootlooped, maybe I could have wiped... anyway. I've got a working gingerbread GP5.0 I can give my daughter (if I can avoid the temptation of putting cwm and then cm11 on it).
TheRealBubba said:
I'll look into JODIN3, messing around with Windows is so painfull. I would skip flashing the pit, just odin the one thing. I've also found that if odin fails flashing something, everything else I try flashing afterwards will fail. The only success I've had has been with disconnecting everything, plugging the device back into the PC, the starting odin new.
I've gotten a working gingerbread ROM, from here:
http://meticulus-development.com/index.php/galaxy-player-5-0-2/galaxy-player-5-0-stock-roms/
(irritating finding the download link among all the malware bull**** and "windows support" popups, it required registering for 4shared, but a throwaway email works)
The recovery is still a native samsung android 3e, and it took me a while to figure out that the "select" key wasn't the power button, but the home softkey... That might have been true of the last one I had flashed, the one that bootlooped, maybe I could have wiped... anyway. I've got a working gingerbread GP5.0 I can give my daughter (if I can avoid the temptation of putting cwm and then cm11 on it).
Click to expand...
Click to collapse
Thank you very much! I'll try and flash, I'm curious to see if this one works! downloading right naw!!
TheRealBubba said:
I'll look into JODIN3, messing around with Windows is so painfull. I would skip flashing the pit, just odin the one thing. I've also found that if odin fails flashing something, everything else I try flashing afterwards will fail. The only success I've had has been with disconnecting everything, plugging the device back into the PC, the starting odin new.
I've gotten a working gingerbread ROM, from here:
http://meticulus-development.com/index.php/galaxy-player-5-0-2/galaxy-player-5-0-stock-roms/
(irritating finding the download link among all the malware bull**** and "windows support" popups, it required registering for 4shared, but a throwaway email works)
The recovery is still a native samsung android 3e, and it took me a while to figure out that the "select" key wasn't the power button, but the home softkey... That might have been true of the last one I had flashed, the one that bootlooped, maybe I could have wiped... anyway. I've got a working gingerbread GP5.0 I can give my daughter (if I can avoid the temptation of putting cwm and then cm11 on it).
Click to expand...
Click to collapse
Actually it didn't work DDD: whatever thank you very much for trying helping me, I think I need to change the entire device XD, but i was thinking... maybe if I install the usa rom on my INTL do you think that it may work, i've read that it works but the home button won't be recognized... dunno
I'm gonna try, as we say in italy, rotto per rotto, I will try and install
edoardog said:
Actually it didn't work DDD: whatever thank you very much for trying helping me, I think I need to change the entire device XD, but i was thinking... maybe if I install the usa rom on my INTL do you think that it may work, i've read that it works but the home button won't be recognized... dunno
I'm gonna try, as we say in italy, rotto per rotto, I will try and install
Click to expand...
Click to collapse
Hmmm, I think the US/Intl might not be super important, since all you really want is to get a working recovery on there. I got one of those GB roms on, then was able to flash cwm. I don't think you need to be able to use the rom, but installing it make odin able to flash cwm. Once cwm was on I installed the cm11 xip and all is good.
Good luck with yours.
TheRealBubba said:
Hmmm, I think the US/Intl might not be super important, since all you really want is to get a working recovery on there. I got one of those GB roms on, then was able to flash cwm. I don't think you need to be able to use the rom, but installing it make odin able to flash cwm. Once cwm was on I installed the cm11 xip and all is good.
Good luck with yours.
Click to expand...
Click to collapse
I still have the same results, the player won't boot after finishing flashing... oh well, thank you very much for your help
Maybe i'll buy another one, it's a very cool device
TheRealBubba said:
I couldn't get mine into recovery either. I couldn't even get proper download mode. But, I used odin3 v1.85 (I also tried kies, and re-installing that may have installed drivers that turned out to be necessary, windows spent a lot of time searching for drivers... I'm a linux guy, I don't really understand how/why windows needs to spend 10 minutes searching for the same drivers again and again - whatever), and tried flashing lots of things, assorted pit files, roms and recoveries...
Eventually I managed to install a stock rom that I got from the first post in this thread:
http://forum.xda-developers.com/showthread.php?p=39188127
It installed correctly, but booted into an animation bootloop.
I cannot flash cwm on to it. When I boot into recovery I get the (stock?) android 3e recovery, and a screen full of red telling me that cache does not exist. None of the four options, reboot, install update zip from sd, wipe data/factory reset, wipe cache, do anything.
Stuck there now.
Click to expand...
Click to collapse
If the stock recovery is not working try flashing a CWM recovery for the GB ROMS.
For the Intl Player with the hardware button this one should work
http://forum.xda-developers.com/showthread.php?t=1414565
You need the Odin file to flash then recovery should work.
Do a cache wipe, factory data reset, and wipe the Dalvik cache.