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!
// edit // - just noticed I posted this in the i9100 thread, I'm sorry if someone can move this please.
Ok, so I rooted my Galaxy s2 last night and it went well, except I put a 9100 on it and my search/back button stopped working with any ROM i put on it. So after trying 20 different roms I went back to a stock ROM I downloaded.
Everything works well, and now i'm on a rooted kernel, except I cannot get into recovery/download mode by doing the 'button dance' anymore. The only way for me to get into recovery mode is to boot my phone up, use the widget "reboot widget root" to boot into recovery/download. Lets say I soft brick my phone installing something, I won't be able to boot into recovery since the OS isn't booting.
Any advice?
Thank you
I suggest you do a complete wipe for your phone and reformat the internal sdcard to get rid of any issues from flashing roms that were not suitable and then reflash with your preferred rom.
Since you have basically reset your phone everything should work properly now.
Isn't there another forum for your device? This thread is only for the international (unbranded) version, GT-I9100. Ask there and you'll be able to get better responses.
Sent from my GT-I9100 using xda app-developers app
Thread moved
Thread moved to the appropriate forum (I hope!!)
mr-moo said:
Ok, so I rooted my Galaxy s2 last night and it went well, except I put a 9100 on it and my search/back button stopped working with any ROM i put on it. So after trying 20 different roms I went back to a stock ROM I downloaded.
Everything works well, and now i'm on a rooted kernel, except I cannot get into recovery/download mode by doing the 'button dance' anymore. The only way for me to get into recovery mode is to boot my phone up, use the widget "reboot widget root" to boot into recovery/download. Lets say I soft brick my phone installing something, I won't be able to boot into recovery since the OS isn't booting.
Any advice?
Thank you
Click to expand...
Click to collapse
You lost the buttons because the rom you flashed contained the secondary bootloader for the I9100, which has different button combos. There are a couple of paths you can take. You can flash back to stock including bootloaders, and start over. Or you can first flash the I777 secondary bootloader using Odin, which will fix the button combos, and then use CLockworkMod Recovery to flash an I777 kernel. You might have to hell raise that rom. At that point you should be fixed.
You can get the files you need from the Download Repository, and the kernel from the development section. See the link in my Signature.
creepyncrawly said:
You lost the buttons because the rom you flashed contained the secondary bootloader for the I9100, which has different button combos. There are a couple of paths you can take. You can flash back to stock including bootloaders, and start over. Or you can first flash the I777 secondary bootloader using Odin, which will fix the button combos, and then use CLockworkMod Recovery to flash an I777 kernel. You might have to hell raise that rom. At that point you should be fixed.
You can get the files you need from the Download Repository, and the kernel from the development section. See the link in my Signature.
Click to expand...
Click to collapse
Ok, so it's been a while since I posted this thread. Since then, I've gathered the courage to attempt a re-flash. I've reflashed using ODIN and a different bootloader. Got that all taken care of and found myself a good stable copy of jellybam with CM10. Been using that for a while pretty successfully other then the battery life being sucked out and a couple random reboots.
Got rid of the SGS2 today and got myself an SGS3
mr-moo said:
// edit // - just noticed I posted this in the i9100 thread, I'm sorry if someone can move this please.
Ok, so I rooted my Galaxy s2 last night and it went well, except I put a 9100 on it and my search/back button stopped working with any ROM i put on it. So after trying 20 different roms I went back to a stock ROM I downloaded.
Everything works well, and now i'm on a rooted kernel, except I cannot get into recovery/download mode by doing the 'button dance' anymore. The only way for me to get into recovery mode is to boot my phone up, use the widget "reboot widget root" to boot into recovery/download. Lets say I soft brick my phone installing something, I won't be able to boot into recovery since the OS isn't booting.
Any advice?
Thank you
Click to expand...
Click to collapse
You might've had the stock from the 9100 still in your phone so you shoot clear cache, and factory reset your phone and then flash the stock ROM again. Hope this helps.
gainstatom said:
You might've had the stock from the 9100 still in your phone so you shoot clear cache, and factory reset your phone and then flash the stock ROM again. Hope this helps.
Click to expand...
Click to collapse
Past see that post right above yours? Yeah you know the one you would've had to read before you even posted this? That's be the one where he says he got rid of his sgs2. So unless he can mentally manipulate it via brain power, he won't need this advice. But thanks for playing!
Hey there,
I'm trying to get CyanogenMod on my friend's aging Vibrant. I first rooted, and then I attempted to install ClockworkMod through the stock recovery. At first it just restarted back to the stock recovery, so I installed it again, and boom- CWM. From there, I wiped, went to mount USB storage, and the drive didn't show up on my computer. I figured it needed to be rebooted, so I tried that. This time, it reverted BACK to stock recovery. I figured, okay, all I have to do is flash CWM again. It won't work anymore. I don't know what to do, because I can't flash CWM, a Rom, or even restore the original rom because I can't get into CWM.
Please help!
vindication84 said:
Hey there,
I'm trying to get CyanogenMod on my friend's aging Vibrant. I first rooted, and then I attempted to install ClockworkMod through the stock recovery. At first it just restarted back to the stock recovery, so I installed it again, and boom- CWM. From there, I wiped, went to mount USB storage, and the drive didn't show up on my computer. I figured it needed to be rebooted, so I tried that. This time, it reverted BACK to stock recovery. I figured, okay, all I have to do is flash CWM again. It won't work anymore. I don't know what to do, because I can't flash CWM, a Rom, or even restore the original rom because I can't get into CWM.
Please help!
Click to expand...
Click to collapse
Okay, I've never had this issue personally, nor have I read of anyone else having a similar issue. However, despite the lack of CWR, you can still restore the device back to stock via Odin. There is a guide on the usage of Odin that can be found here. Download links to the program along with the required .pit and .tar files can also be found in said guide. Once you've got the device restored, you can go through the process of installing CyanogenMod... But, keep in mind that the installation process is going to vary slightly depending on what version of CyanogenMod you wish to install. Are you trying to install CyanogenMod 7 (Gingerbread), 9 (Ice Cream Sandwich), 10 (Jellybean 4.1), or 10.1 (Jellybean 4.2)?
I know about Odin, but I'm on a Mac right now. I was really hoping there was a way around this so I didn't have to install Windows via Boot Camp. I'm planning on installing CM10.
vindication84 said:
I know about Odin, but I'm on a Mac right now. I was really hoping there was a way around this so I didn't have to install Windows via Boot Camp. I'm planning on installing CM10.
Click to expand...
Click to collapse
You could use Heimdall, an alternative to Odin that is compatible with OS X. You can download it here.
Now, in regards to the process of installing CM10, you could refer to this video... http://forum.xda-developers.com/showthread.php?t=1812882. Hopefully you won't get that weird CWR issue this time around. Let me know how it goes. :fingers-crossed:
No matter what, I can't get Heimdall to detect the phone. It just says "Failed to detect compatible download-mode device".
vindication84 said:
No matter what, I can't get Heimdall to detect the phone. It just says "Failed to detect compatible download-mode device".
Click to expand...
Click to collapse
Hmm... Perhaps this post might be of some help? Sorry, but I don't own a Mac, nor have I ever personally used Heimdall... So I've never had that issue before. However, a little Google searching uncovered a bunch of threads discussing this exact error. Perhaps a little digging may uncover your answer? Link. Again, best of luck dude.
Can you get back into the stock recovery and transfer files to the internal SD? If so, you need to flash update.zip(attached). It will add a custom recovery. You may need to flash it twice to get it to show up. From there, I would suggest you do the following: 1) wipe user data, cache and davlik(under advanced) 2) reboot recovery, if the stock recovery comes back, just reflash update.zip. 3) Flash whichever ROM you want on the phone, again, may take two flashes.
If you cannot add files to the internal SD, this solution won't work, in which case you'll have to play around a little more. I would suggest, as an alternate method, that you pull the battery and SD card. replace the battery and try to enter download mode. Try using Heimdal One-Click(http://forum.xda-developers.com/showthread.php?t=1278683). It's much easier than using Heimdal or Odin and will flash the Vibrant to stock. View the download mode shortcut below.
Side note: hardware shortcuts help a lot. If you don't know them, they are here:
Hold volume up + volume down + power =
1. When off, boots recovery
2. When on, reboots into recovery
Hold volume up + volume down +plug in computer USB = download mode.
^This is what you use for Odin and/or Heimdal. They won't recognize the device unless it's in download mode.
May also take a few tries.
Let me know how it goes and if you have any questions.
EDIT: You may need to have the phone on the stock ROM to flash that update.zip. I ran into that problem and couldn't figure out why it wasn't working for a long time. Don't update the vibrant to stock 2.2 to use the update.zip.
danvsullivan said:
Can you get back into the stock recovery and transfer files to the internal SD? If so, you need to flash update.zip(attached). It will add a custom recovery. You may need to flash it twice to get it to show up. From there, I would suggest you do the following: 1) wipe user data, cache and davlik(under advanced) 2) reboot recovery, if the stock recovery comes back, just reflash update.zip. 3) Flash whichever ROM you want on the phone, again, may take two flashes.
If you cannot add files to the internal SD, this solution won't work, in which case you'll have to play around a little more. I would suggest, as an alternate method, that you pull the battery and SD card. replace the battery and try to enter download mode. Try using Heimdal One-Click(http://forum.xda-developers.com/showthread.php?t=1278683). It's much easier than using Heimdal or Odin and will flash the Vibrant to stock. View the download mode shortcut below.
Side note: hardware shortcuts help a lot. If you don't know them, they are here:
Hold volume up + volume down + power =
1. When off, boots recovery
2. When on, reboots into recovery
Hold volume up + volume down +plug in computer USB = download mode.
^This is what you use for Odin and/or Heimdal. They won't recognize the device unless it's in download mode.
May also take a few tries.
Let me know how it goes and if you have any questions.
EDIT: You may need to have the phone on the stock ROM to flash that update.zip. I ran into that problem and couldn't figure out why it wasn't working for a long time. Don't update the vibrant to stock 2.2 to use the update.zip.
Click to expand...
Click to collapse
I already have the update.zip on the phone. I can get into the stock recovery and flash it (it says "replacing recovery with Clockwork" and everything), but every time I attempt to flash it, the phone reboots to the stock recovery. I can't add files to the internal SD because the only options are Reboot System Now, Reinstall Packages, Delete All User Data, and Delete Cache Data"
One-Click doesn't see the phone either. I'm starting to get really worried. Is there some sort of driver or something I need to have installed on the system?
SOLVED!
Alright, I finally figured it out. I'm exhausted, haha.
I finally just bit the bullet and installed Windows. I used ODIN, which was such a breeze. I wish I would have just done that in the first place.
Thanks for your help guys!
vindication84 said:
Alright, I finally figured it out. I'm exhausted, haha.
I finally just bit the bullet and installed Windows. I used ODIN, which was such a breeze. I wish I would have just done that in the first place.
Thanks for your help guys!
Click to expand...
Click to collapse
Glad to hear the good news!
Hope this time you'll be able to update the phone seamlessly, and your friend can enjoy a newly updated Vibrant. If you ever have any questions, don't hesitate to PM me. I'll try my best to help you out.
danvsullivan said:
Try using Heimdal One-Click(http://forum.xda-developers.com/showthread.php?t=1278683).
Click to expand...
Click to collapse
Although I had heard of Bay_wolf's AIO Vibrant Toolbox, which is also a one-click software (but only compatible w/Windows), I had never heard of "Heimdal One-Click". This is good to know about, and I've added the program to the The Official XDA Vibrant Bible Thread. I learn something new every day. Thanks!
vindication84 said:
Alright, I finally figured it out. I'm exhausted, haha.
I finally just bit the bullet and installed Windows. I used ODIN, which was such a breeze. I wish I would have just done that in the first place.
Thanks for your help guys!
Click to expand...
Click to collapse
Great news! You can follow the instructions I wrote out to install a custom ROM from stock. Just put all the files on the internal SD, wipe everything and flash update.zip and then the ROM and gapps.
If you have questions, you may PM me as well.
Good luck!
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
I received this verizon Galaxy Tab 10.1 as a gift and a project, but haven't been able to make any progress.
The tablet was bought from a taxi company that used it was in car entertainment. When booted, an app immediately starts up and removes the navigation bar. If you are fast enough, you can get to the settings and uninstall this app before it starts, or what I have found to be easier, just use shell commands to hit home and uninstall while the app tries to regain control.
The table is currently running 3.2, and cannot update over wifi, nothing happens.
Root was gained by an unknown method, but the SU app won't open up. I can access su through the shell however.
I have tried flashing a cwm recovery through ODIN which says is successful but if it is booted straight to the recovery it is still stock.
Flashing ROM's through ODIN appear to be successful, but just boots right back to the original rom and recovery.
Adding anything to the SD card or anywhere else accessable to the stock recovery does not work either because the SD card is reformatted to the original contents every time.
This also occurs with any apps that are installed, each one is removed when rebooted except for SU. And Rom Manager FC's when CWM is attempting to flash.
nvflash will not work either because the bootloader is locked.
I don't know much about the boot sequence for android, but I looked for any init. files that are out of the ordinary and cannot find anything.
I'm giving this tablet away when I finally figure it out, I just want to fix it. Any help would be awesome and let me know if I've left something out.
Even if no one has any specific suggestions, can someone post a PIT file for a SCH-i905? I have seen the stock firmware that can be flashed through ODIN but it does not stick on my unit.
Thanks!
Excuse my English but my original language is Spanish.
The default verizon tablet brings in recovery an option that reloads the original recovery. If units installed CWM via Odin must access the recovery option (Vol +) on 1st boot and enter the option to leave cmw (reboot) will give you the option of not recovering the recovery.
The other alternative is to flash via odin the original software look it by google "PDA_HC31_EG01Ba_AP352081user_CP1033580_LTE20110704_0708"
in this case the tab stay with the factory version.
if the team does not have SIM must type top left - top right - bottom left, bottom right and then vol + to unlock.
good look
This is the post that you are needing.
http://forum.xda-developers.com/showthread.php?t=1342995
Sent from my SM-N900V using XDA Premium 4 mobile app
i had the same problem but pulling the sim and unlocking as mentioned above helped a lot then went through the whole rooting process through odin and have not had any issues with anything reverting back to stock. only issue now is not very many roms for our model "bummer" all in all still a good droid tablet for what i paid lol if you still havent got it going let me know and i will give you all the directions and steps i used
I have tried installing PDA_HC31_EG01Ba_AP352081user_CP1033580_LTE2011070 4_0708 through Odin3.
I do boot directly into recovery after installing CWM, the stock recovery still persists. I have tried several times because I know sometimes it does not stick.
I have also tried flashing the factory image linked in that xda post "[ROM]EG01 - Factory STOCK ODIN Image - VZW LTE Tab 10.1".
Boots right back up and starts the same taxi cab show case media software it normally does.
One thing I did not note in the first post. I do have root access when the tablet is booted into the os, but I do not when the tablet is in recover. I dont know if this is unusual or not.
I can also install busy box, but have yet to find out his would be useful.
I also do not have access to nvflash, but I think this is normal because the bootloader is not unlocked.
http://forum.xda-developers.com/showthread.php?p=49924392
Might work for you too. This is a post I made in another thread.
Sent from my Nexus 4 using Tapatalk
baystallion said:
http://forum.xda-developers.com/showthread.php?p=49924392
Might work for you too. This is a post I made in another thread.
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
Awesome, I'll give this a go when I get home.
Was there a p4vzw twrp version some where in those links?
Looks like all of the ones referenced were 3g and wifi only.
Sidenote: I don't care if I keep 4g functionality or not, I will only be using this for wifi, if that makes fixing the problem any easier.
hsbr said:
Was there a p4vzw twrp version some where in those links?
Looks like all of the ones referenced were 3g and wifi only.
Sidenote: I don't care if I keep 4g functionality or not, I will only be using this for wifi, if that makes fixing the problem any easier.
Click to expand...
Click to collapse
Search for infamous AOKP 4.2 thread. I think it has twrp for p4vzw.
Sent from my GT-P7500 using Tapatalk
eushaun99 said:
Search for infamous AOKP 4.2 thread. I think it has twrp for p4vzw.
Sent from my GT-P7500 using Tapatalk
Click to expand...
Click to collapse
I was able to find the thread, thanks!
After downloading the odin flashable twrp, I tried first with Odin3, but it failed. Then I flashed with JOdin, this first pulled a PIT file from the tab then failed to repartition. If I ran it without repartitioning it said it was sucessful, but if I boot straight into recovery the stock android recovery still comes up.
I have a way to get a pit file now though, so that's nice.
hsbr said:
I was able to find the thread, thanks!
After downloading the odin flashable twrp, I tried first with Odin3, but it failed. Then I flashed with JOdin, this first pulled a PIT file from the tab then failed to repartition. If I ran it without repartitioning it said it was sucessful, but if I boot straight into recovery the stock android recovery still comes up.
I have a way to get a pit file now though, so that's nice.
Click to expand...
Click to collapse
Don't use the Odin way. First flash cwm recovery, then flash the twrp zip file.
Sent from my GT-P7500 using Tapatalk
eushaun99 said:
Don't use the Odin way. First flash cwm recovery, then flash the twrp zip file.
Sent from my GT-P7500 using Tapatalk
Click to expand...
Click to collapse
I can't flash CWM in the first place. I have listed all of the different methods I tried flashing CWM with in the OP.
hsbr said:
I can't flash CWM in the first place. I have listed all of the different methods I tried flashing CWM with in the OP.
Click to expand...
Click to collapse
Oh, then I can't help you then. Sorry.
Sent from my GT-P7500 using Tapatalk
hsbr said:
Even if no one has any specific suggestions, can someone post a PIT file for a SCH-i905? I have seen the stock firmware that can be flashed through ODIN but it does not stick on my unit.
Thanks!
Click to expand...
Click to collapse
Yes please i have an issue my tablet got stuck on samsung logo i tried to flash another rom because i cant fing any rom for this tablet US Callular
i905. Tab 2 10.1.
If any one can provide a stock odin or something to make this tablet work i would appreciated?