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!
Related
I recently tried to root my Galaxy tab 10.1 "4G" that I got from Rogers using the files under the 4G portion in the Look Here First thread. Went into recovery to flash kernal and recovery files okay. Rebooted.
Then the bad stuff started: Boot screen loop.
After doing some more research it seems the reason why this happened is because the Rogers device is actually not a 4G device but a 3G device. Accordingly flashing the 4G files onto a 3G device has most likely caused this.
I am able to boot using the volume down + power button, however I cannot access recovery mode. I can access Downloading mode with Odin recognizing it. I tried to see if I was able to flash CWM onto it with no avail with the following screen
My guess is that it is due to flashing an incompatible Kernel... sigh.
So now I ask you gurus, is my Galaxy Tab 10.1 fully bricked or is there some other way I can unbrick this?
Thanks in advance.
I am going to assume that since you are able to get into download mode that you are not hard bricked but just soft bricked. In which case there must be some files that you can flash with odin to get you back to a stock version of honeycomb...or actually rather be able to flash another kernal through odin.
Again im not sure with how flashing with the gtab since I havent flashed anything on mine yet but I have experience flashing different kernals on my captivate and that was what happened to me numerous times.
That was my first thought too when I realized Download mode was still accessible. The file I tried was Overcome's CWM recovery file so that's one possibility why it was not able to go through. I would try flashing various kernels to see if I can get anywhere but I have yet to find any stock/relevant kernels to do so.
UPDATE: ... I apparently had KIES running in the background so I closed that and bam, it is now able to enter recovery mode. I did a factory reset, cache wipe and all but it still is not able to boot up. I reckon I still require a proper kernel. It still is impossible to access the device's internal storage however so I am not able to simple drag and drop the necessary files.
Is there a way of doing this via ODIN as is the only method I have available?
teamovercome net
Install new Recovery, then skip to restoring stock mod, I am doing it right now, hope it works. Was looking for solutions all day nothing else is there
did the very same thing when I first got my Rogers Tab: follow the Overcome guide exactly and all will be well again -- flash the re-stock package first, then jump straight to the latest Overcome 2.2.0 with the CWM and you can use Pershoot's kernel too if you wish.
lgsshedden said:
did the very same thing when I first got my Rogers Tab: follow the Overcome guide exactly and all will be well again -- flash the re-stock package first, then jump straight to the latest Overcome 2.2.0 with the CWM and you can use Pershoot's kernel too if you wish.
Click to expand...
Click to collapse
have you updated to the new 3 version? I did the update, one major issue was Browser was not syncing with chrome, gives an error, I am gonna try a full wipe and see, just wondering if anyone found something wrong with Ver. 3.
MyNameIsDan_ said:
That was my first thought too when I realized Download mode was still accessible. The file I tried was Overcome's CWM recovery file so that's one possibility why it was not able to go through. I would try flashing various kernels to see if I can get anywhere but I have yet to find any stock/relevant kernels to do so.
UPDATE: ... I apparently had KIES running in the background so I closed that and bam, it is now able to enter recovery mode. I did a factory reset, cache wipe and all but it still is not able to boot up. I reckon I still require a proper kernel. It still is impossible to access the device's internal storage however so I am not able to simple drag and drop the necessary files.
Is there a way of doing this via ODIN as is the only method I have available?
Click to expand...
Click to collapse
I have the exact same problem and i was wondering how do you close KIES while not being able ti boot because i need to go to recovery mode and everywhere i have looked there has been no answer.
Alecn8r7 said:
I have the exact same problem and i was wondering how do you close KIES while not being able ti boot because i need to go to recovery mode and everywhere i have looked there has been no answer.
Click to expand...
Click to collapse
KIES is a program that's running on your PC. I would hazard a guess that you just need to close it as you would with any program. The op was apparently connected to the computer when trying to get into recovery mode. If you're not connected to the computer when you hold power and volume - and you get the two options. Recovery on the left, download mode on the right. Choose the one on the left with the volume -button and start recovery when it's highlighted with volume +
Hope this helps.
Sent from my GT-P7510 using XDA Premium HD app
MyNameIsDan_ said:
I recently tried to root my Galaxy tab 10.1 "4G" that I got from Rogers using the files under the 4G portion in the Look Here First thread. Went into recovery to flash kernal and recovery files okay. Rebooted.
Then the bad stuff started: Boot screen loop.
After doing some more research it seems the reason why this happened is because the Rogers device is actually not a 4G device but a 3G device. Accordingly flashing the 4G files onto a 3G device has most likely caused this.
I am able to boot using the volume down + power button, however I cannot access recovery mode. I can access Downloading mode with Odin recognizing it. I tried to see if I was able to flash CWM onto it with no avail with the following screen
My guess is that it is due to flashing an incompatible Kernel... sigh.
So now I ask you gurus, is my Galaxy Tab 10.1 fully bricked or is there some other way I can unbrick this?
Thanks in advance.
Click to expand...
Click to collapse
Ok,...I see that there is enough info posted to get you back up... but just an FYI.. this device has a seperate recovery and kernel...in other words.. to root you just need to Odin a compatible recovery and then install the correct binaries to gain root access.
This device is so simple to root... I have an e4gt..and that device(until framaroot)..was a pain.. it's recovery is part of the kernel.. not only that, but it can be implemented different ways into the kernel
Back on topic..... locate a recovery.. Odin it... reboot.... boot to recovery.. flash root zip... If you have flashed something wrong but still have Odin mode.. like said above.. flash the stock rom or if you can't find it... flash the recovery(for the device) then boot to it and then put a custom rom on...
Gil81- You do realize the post you replied to was made back in January?
Sent from my GT-P7510 using XDA Premium HD app
All,
I kinda ran into an issue after i was trying to upgrade to ICS on my Galaxy S II.
I downloaded the ROM that Faryaab posted on http://forum.xda-developers.com/showthread.php?t=1544487 .
SInce i upgraded to Android 2.3.6 before using the information from Intratech in the http://forum.xda-developers.com/showthread.php?t=1075278 post i also installed CF-Root 5.
Using CWM version 3 i installed the new firmware that Faryaab posted.
I placed the extracted tar.md5 file in a firmware folder on the phone's SD card. At the start of the install i selected "Keep CF-Root"
But after the phone rebooted one and continued with the install i briefly saw an error.
After this the phone rebooted again but froze at the "Samsung Galaxy SII" bootsplash.
I am still abale to get into CWM Recovery but í don't seem to be able to install another ROM or do anthting else.
Also i'm unable to install any updates using Odin3 v1.85 but this is probably due to the fact that i have CWM installed.
The same go's for "Odin3_v3.04" and "Odin Multi Downloader v4.28".
Unfortunately i'm a complete NOOB when it comes to this as i haven't played around enough to really know exactly what i'm doing.
I tried to explain everything i did as precice as possible and i hope someoone can help me!
I can't make a lot of sense of your post, but you don't mention download mode once.
I don't know how you've managed to flash something with "CFM version 3" (whatever that is) nor why you'd want to keep a GB kernel with an ICS ROM (that won't work).
Sorry for the confusion.
I used CWM version 3, i just noticed i made a typo.
I think the kernel is my mistake. I flashed the new ICS firmware before upgrading the Kernel...
Right now i'm unable to use Odin (for as far as i can determine).
I;m able to startup in download mode (power+volume up+home) at which point i am able to get into CWM Recovery (part of CF-Root).
That is all, im completely stuck with what i know.
Shuichi Nozaki said:
Sorry for the confusion.
I used CWM version 3, i just noticed i made a typo.
I think the kernel is my mistake. I flashed the new ICS firmware before upgrading the Kernel...
Right now i'm unable to use Odin (for as far as i can determine).
I;m able to startup in download mode (power+volume up+home) at which point i am able to get into CWM Recovery (part of CF-Root).
That is all, im completely stuck with what i know.
Click to expand...
Click to collapse
Download mode is volume down and home and power.
Volume up and home and power is recovery mode.
ctomgee said:
Download mode is volume down and home and power.
Volume up and home and power is recovery mode.
Click to expand...
Click to collapse
Then that's probably my problem!
I'm going to try that right away!
Thanks for your help!
I'll post a reply if/how i get everything working again.
Shuichi Nozaki said:
Then that's probably my problem!
I'm going to try that right away!
Thanks for your help!
I'll post a reply if/how i get everything working again.
Click to expand...
Click to collapse
Thats indeed turned out to be it!
I was able to flash a new ROM and new Firmware and everything is working again and running on Android 4.0.3 now
---Make sure you have the drivers installed for your SGP 5.0 USA (capacitive buttons)----
-This has worked for me whenever I enter boot-loop during installing a ROM.
-Download a stock firmware (this one is for US ((capacitive buttons)) Samsung Galaxy Player 5.0): http://forum.xda-developers.com/showthread.php?t=1520728
-Download a .pit file/partition file (contains it for all SGP's): http://forum.xda-developers.com/showthread.php?t=1472897&goto=nextnewestz
-Boot into downloading mode (Volume down first, then power button, release when an triangle and Android guy using a shovel is shown)
-Open up odin
-Click on "PDA", and select "ueki8_min.tar.md5", that should be the stock ROM you downloaded (where ever you saved it), then click "PIT" and select your SGP 5.0 .pit file, which should read "G70-GalaxyPlayer5.0-8gig.pit"
-Press "Start", the process should take 2-5 minutes, it might freeze at some point in time but it's still working. You will know it's finished when it says "PASS" in the first, top right box.
-Then boot into recovery mode (Volume UP, then power), but what is important is that you release the second the triangle/android shovel is gone and shows a black screen or else it will go to a battery charging.
-Then you select "Wipe data/factory reset" and "Wipe cache partition", then "reboot system now" and then your SGP should be able to boot at this point.
*An extra note, the stock ROM I linked is rooted, but it's basically the same as STOCK ROM, with all the Samsung Bloatware.
And to remove the root, you have to get Root Browser from the Play Store and delete "Superuser.apk" in "System/app" and delete "su binary" in "system/bin. After you delete those two files, reboot and you should be unrooted.
(tell me if there is a problem with my guide, or if you have a problem.)
I have followed the instructions but I can't boot into recovery for some reason it only bootloops when I try using the stock rom. entropy kernel + rom is fine but stock rom and kernel only cause boot loops :/
Nevermind i'm ok lol messed around with it for about 20 mins and eventually got it working. Not even sure how to explain how i did it
Silvrsun said:
I have followed the instructions but I can't boot into recovery for some reason it only bootloops when I try using the stock rom. entropy kernel + rom is fine but stock rom and kernel only cause boot loops :/
Nevermind i'm ok lol messed around with it for about 20 mins and eventually got it working. Not even sure how to explain how i did it
Click to expand...
Click to collapse
lol it's k.
Old(ish) thread but since someone used it recently and may in the future might I recommend you note that any attempt to resurrect a device will be best accomplished using a STOCK Samsung usb cable. Speaking from many experiences it is very possible that a device will not be recognized using the pc tools without the stock cable. Just a recommendation. Thanks.
I have search for days to figure out how to unbrick my sgp 5, this however is the most complete and simple guide that have fix my problems after several bricks trying to install custom roms while the forum as down, with bad info on google. I would like to add to make sure that KIES is installed as the drivers become unrecognizable after a brick. Thanks for this post, hardest thing was finding the exact files for the US version as there several out there, the ones you listed worked perfectly together and recovery mode takes a few tries.
KIES
samsung . com/us/support/owners/product/YP-G70CWY/XAA
No one should ever use the pit that comes with that zip file!
Sent from my SAMSUNG-SGH-I577 using xda app-developers app
galax5 said:
---Make sure you have the drivers installed for your SGP 5.0 USA (capacitive buttons)
Click to expand...
Click to collapse
Well how do I make sure I have these drivers?
I have a boot loop when charging device when off and device attempts to load the charging status system.
Anyway I recently installed a new ROM and kernel and the capacitive buttons are dead now (their leds are still on, but they don't actually do anything).
I thought finding out about the driver you were talking about might lead me to a solution.
Does the Odin Version matter?
galax5 said:
-
-Open up odin
-Click on "PDA", and select "ueki8_min.tar.md5", that should be the stock ROM you downloaded (where ever you saved it), then click "PIT" and select your SGP 5.0 .pit file, which should read "G70-GalaxyPlayer5.0-8gig.pit"
-Press "Start", the process should take 2-5 minutes, it might freeze at some point in time but it's still working. You will know it's finished when it says "PASS" in the first, top right box.
Click to expand...
Click to collapse
I remember when I was attempting to root the SGP5 the first time, I ran into trouble with using too new of an odin version. Do you remember which version you used for this? I've tried 1.7&1.85 but to no effect....
AndItsBricked said:
I remember when I was attempting to root the SGP5 the first time, I ran into trouble with using too new of an odin version. Do you remember which version you used for this? I've tried 1.7&1.85 but to no effect....
Click to expand...
Click to collapse
1.85 works fine for me. Check to see if your drivers are properly installed
I have a boot loop when charging device when off and device attempts to load the charging status system.
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
Hey peeps
Ok I've been at this for two straight days now in order to try and unbrick this Telus Fascinate SGH-T959P
My buddy initially attempted to flash it with something and really messed it up to the point that even the battery wouldn't charge.
I don't even care if I get it to stock.. an amazing Rom/Kernel combo will also work.
So this is where I am today... and I have spent the last two days non-stop trying to fix this thing...I have been through sooo many forums posts and websites my brain is about to cook.
Software I am using
Odin v1.7 and v1.83.. I try to use the newest one.. just in case.
ADB / SDK installed and am able to push files across to the sdcard in my phone... everything seems good in that dept
Files that have got me to where I am today
T959TLJL3 Froyo original firmware (apparently)... but can not flash all of the files from the package ..zimage and a few others just fail to flash
s1_odin_20100512.pit file (Have atlas_v2.2.pit also but haven't had as much success with it)
SGH-T959-Stock_plus_voodoo_CwM_2.3.4v2
su-2.3.6.3-efgh-signed
I can successfully boot the phone into download mode every single time using the volume up and down while plugging in the usb cable
Also if i just hit the power button I get a Telus 4G / Samsung splash screen and then the phone boots into CwM Voodoo Recovery v3.0.2.8x (Orange??)
In the CwM recovery mode, I can now finally mount all partitions and it looks like things will flash.
Now that I've finally got this phone to this point, I don't want to mess it up.
I want to make sure I have the right files to complete this little project.
Need some direction from the pros.. Am I able to flash a custom rom now ? And if so, what one is best to use.
From this point how can I revert to stock? Do I have the right files ? And how since Odin fails to flash the ones I have.
I figured going to stock first was easier, then use Kies to update it.
Show me the way
Thanks.
jROC
Wow... I got it .. Finally... After I figure out exactly what I used for files.. I will let you know.
All I can tell you right now is that I was flashing a single files at a time then powering down and coming back into download mode to flash the next file.
Right now the phone is all booted up and Running Android v2.3.3 (GB LKG2) and even tho the phone is actually a T959P.. the boot screen shows up as a T959D. Interesting.
jroc99 said:
Wow... I got it .. Finally... After I figure out exactly what I used for files.. I will let you know.
All I can tell you right now is that I was flashing a single files at a time then powering down and coming back into download mode to flash the next file.
Right now the phone is all booted up and Running Android v2.3.3 (GB LKG2) and even tho the phone is actually a T959P.. the boot screen shows up as a T959D. Interesting.
Click to expand...
Click to collapse
Can you send me the T959P stock files please
robbylaw said:
Can you send me the T959P stock files please
Click to expand...
Click to collapse
No single file that I downloaded was able to flash the phone.
I ended up flashing individual files... and kinda had to mix and match, but was able to get the phone booting back into Android OS
However the phone was missing the EFS folder with IMEI info and such..
Still was not able to recover it 100%.
Message me with your email and I will try to send what I used.
jroc99 said:
No single file that I downloaded was able to flash the phone.
I ended up flashing individual files... and kinda had to mix and match, but was able to get the phone booting back into Android OS
However the phone was missing the EFS folder with IMEI info and such..
Still was not able to recover it 100%.
Message me with your email and I will try to send what I used.
Click to expand...
Click to collapse
i messaged you
Ok peeps... If anyone is looking for a firmware file to get their phone booting back into droid I have one that works.
Works on Telus T959P
I have dropbox setup and can share with you that way, just message me.
I need a copy
Sent from my GT-P5113 using xda app-developers app
I've been trying to unbrick an T959P as well, have it so i can also boot into CWM (from SGH-T959-Stock_plus_voodoo_CwM_2.3.4v2) but can never get it too boot into the OS. Tried several files to revert it back to stock but so far nothing has worked. Any hints would be appreciated, thanks in advance
To do it, get this file.
https://gofile.io/?c=tJd0Pd
Then get odin v1.85
https://gofile.io/?c=WHkZHO
Launch odin with admin powers (sudo/su for linux, or whatever).
Then click PDA and select the tar.md5 file and start.
Hopefully it soft bricked not hard bricked.
Fury_Phoenix said:
To do it, get this file.
https://gofile.io/?c=tJd0Pd
Then get odin v1.85
https://gofile.io/?c=WHkZHO
Launch odin with admin powers (sudo/su for linux, or whatever).
Then click PDA and select the tar.md5 file and start.
Hopefully it soft bricked not hard bricked.
Click to expand...
Click to collapse
I posted that in 2013 the device is long gone, thanks for the input though.
draekko said:
I posted that in 2013 the device is long gone, thanks for the input though.
Click to expand...
Click to collapse
Do you have twrp or cwm for the phone?
Fury_Phoenix said:
Do you have twrp or cwm for the phone?
Click to expand...
Click to collapse
I don't have the phone or any software related to that phone. That post was from 7 years ago.