Please, for the love of god, someone help me!!
I have spent the past 2 days trying to root my brand new Tab 2 (verizon) p3100 (android 4.1.2). I've tried every tutorial that I can find. I've tried various versions of Odin, various versions of heimdall, various versions of CWM and other rooting files. I get error after error. The device still works fine but it WILL NOT ROOT!!
I am currently trying to use Odin3 and CF Auto Root (my 100th attempt probably). Every time I use Odin, any version, any tar file, it fails with a "Fail! (Auth)" error. The message in download mode says "SECURE CHECK FAIL: recovery".
I've done a factory reset of the Tab. I've cleared cache. I've tried running Odin is an admin. I've tried different usb ports on my PC (Windows 7, 64bit).
It doesn't matter what I try, it always results in an error. This thing just WILL NOT ROOT!
Can anybody tell me what the problem is? Or another way to root? Please. This is driving me crazy!!
Thank you!!
Try this.
Huge problem
I found these instructions:
droidviews.com/how-to-root-and-install-cwm-twrp-recovery-verizon-galaxy-tab-2-sch-i705-on-ics-jelly-bean/
And finally got it to root. Then I got to the part where I installed the terminal emulator, granted it root access, and followed the instructions to install aboot.img. Then the Tab shut down, I thought it was going to reboot but it never started back up. Now I can't get it to turn on or go into recovery or download mode. Nothing. Everything was fine up to that point. Now nothing at all. How do I fix this??
ninasmith said:
I found these instructions:
droidviews.com/how-to-root-and-install-cwm-twrp-recovery-verizon-galaxy-tab-2-sch-i705-on-ics-jelly-bean/
And finally got it to root. Then I got to the part where I installed the terminal emulator, granted it root access, and followed the instructions to install aboot.img. Then the Tab shut down, I thought it was going to reboot but it never started back up. Now I can't get it to turn on or go into recovery or download mode. Nothing. Everything was fine up to that point. Now nothing at all. How do I fix this??
Click to expand...
Click to collapse
<facepalm>
Oh boy... WHY the heck did you flash a bootloader (totally unnecessary step to begin with) from a completely different device?!?! There is so much info on rooting P31xx here on XDA, describing several different methods in details, and yet you managed not only to find a way that is not even intended for your device, but to proceed with no understanding of the process whatsoever...
I would suggest to take a deep breath, and try again (and again) to get your tab started in download mode (hold Volume DOWN + Power until you see a warning screen). If you can do that, flash the proper ROM with Odin -- whatever version you can find, but the one for your device. Then promise yourself to NEVER do anything without at least a basic understanding of what you are doing.
If you can't get the download mode working, then look up the service centre. You have an option to play dumb and just say it suddenly died on you -- maybe, you get lucky and could claim the warranty.
EDIT: OK, I am really confused now... You specifically said you have a P3100, but you also mentioned Verizon. So, which one is it that you have -- GT-P3100, or SGH-i705??? These are very different devices! If you indeed have an i705, disregard what I said above (it's relevant to P3110), and start with this thread. It may not be as bad after all...
kt-Froggy said:
<facepalm>
Oh boy... WHY the heck did you flash a bootloader (totally unnecessary step to begin with) from a completely different device?!?! There is so much info on rooting P31xx here on XDA, describing several different methods in details, and yet you managed not only to find a way that is not even intended for your device, but to proceed with no understanding of the process whatsoever...
I would suggest to take a deep breath, and try again (and again) to get your tab started in download mode (hold Volume DOWN + Power until you see a warning screen. If you can do that, flash the proper ROM -- whatever version you can find, but the one for your device. Then promise yourself to NEVER do anything without at least a basic understanding of what you are doing.
If you can't get the download mode working, then look up the service centre. You have an option to play dumb and just say it suddenly died on you -- maybe, you get lucky and could claim the warranty.
Click to expand...
Click to collapse
It's not a different device. I have the Tab 2 from Verizon, which is the i705. I thought it was the same as a p3100 but I guess it's not because verizon locks it down more. The model number, listed in settings, is the i705. So I found these instructions and actually rooted it just fine using odin (finally). When it rebooted, I had super user and all was good. Until the part where it told me to do the aboot.img with the terminal emulator.
I have been trying for the past half hour and cannot get it to do ANYTHING. I've held down every combination of buttons and nothing at all. It will not turn on. It will not go into recovery. It will not go into download mode. Nothing. I plug it into the computer and it's not recognized by the PC (because it's not on). I've plugged it into the wall. Nothing. It will not do anything! I don't know what will happen if I try to take this back to Verizon.
ninasmith said:
It's not a different device. I have the Tab 2 from Verizon, which is the i705. I thought it was the same as a p3100 but I guess it's not because verizon locks it down more.
Click to expand...
Click to collapse
It's more clear now, thanks! I updated my post above, before I read your reply. i705 and P3100 are very different, not just because of customizations by VZW, but technically -- different CPU, chipset, radio module, everything.
One thing I can think of is to just leave it plugged in to the wall charger overnight, and try again. You might also want to ask your question in the respective thread that I linked above. But if you really can't get your tab to show any signs of life, you are out of luck, I guess...
BTW, here is another thread for you, related to unlocking the bootloader on i705.
kt-Froggy said:
It's more clear now, thanks! I updated my post above, before I read your reply. i705 and P3100 are very different, not just because of customizations by VZW, but technically -- different CPU, chipset, radio module, everything.
One thing I can think of is to just leave it plugged in to the wall charger overnight, and try again. You might also want to ask your question in the respective thread that I linked above. But if you really can't get your tab to show any signs of life, you are out of luck, I guess...
BTW, here is another thread for you, related to unlocking the bootloader on i705.
Click to expand...
Click to collapse
Thanks. Yeah I tried for about an hour. I had it plugged into the wall. It would not do ANYTHING at all. I took it back to Verizon and exchanged it. Now I just cross my fingers and hope they don't figure it out.
ninasmith said:
Thanks. Yeah I tried for about an hour. I had it plugged into the wall. It would not do ANYTHING at all. I took it back to Verizon and exchanged it. Now I just cross my fingers and hope they don't figure it out.
Click to expand...
Click to collapse
Good that they exchanged it for you. Better luck next time! Read those two threads I linked, it should give you enough info.
BTW, my apologies if I sounded like an a$$. To be fair, you said you had a P3100, and I didn't realize it was actually a different device until I noticed that you also mentioned Verizon. Looks like you tried to do the right thing, but somehow it went sideways. Well, sh!t happens...
Related
Forgive me if I'm posting in the wrong section. Forgive me if I'm not allowed to post here yet. Just forgive me in general. I don't want to be banned or anything like that. I'm Extremely interested in android development.
I made a working port of ClockworkMod Recovery v5.0.2.8 for the Pantech Crossover. I wanted to do this before I started tinkering around with porting cm7.2. So that I would have a way to backup, restore, and flash new roms, etc... Or else when I make a noob mistake like yesterday and have a non booting phone resulting in having to flash my old boot.img with fastboot...anyways..
DANGER: DRAGONS AHEAD
FLASH AT YOUR OWN RISK
YOU HAVE BEEN WARNED
The method I used to flash the recovery was:
1)adb push recovery.img /sdcard/recovery.img
2)flash_image recovery /sdcard/recovery.img
3)repeat step 2 (for some reason it gave me a read error out of memory the first time)
Here's the link to the custom recovery:
http :// dl. dropbox .com /u/20070520/ recovery.img
I know I'm not supposed to post links yet. Remove spaces
I just hope that there are others with the Pantech Crossover that are interested in this and the possible future development of custom roms.
Also if anyone knows if there is a good way to get ahold of koush let me know, so I can give him what he needs to hopefully add this to Rom Manager. I couldn't message him on github because he doesn't have an email set up with it
And while I'm at it. Here's the method for rooting your crossover. I'm not going to provide the files since they can easily be found with a google search.
1: Find a copy of gingerbreak.apk and copy it to your sd card
2: Enable usb debugging and allow installation of non market apps
3: Install gingerbreak
4: Root device with Gingerbreak
5: You can uninstall Gingerbreak when its completed.
Sent from my rooted PantechP8000 using XDA
Thanks so much for this! I have a friend with a crossover and is always looking for my help with making it work better. I realize this is a newer thread, I was wondering how things were coming along with CM? Anything I can do to help perhaps?
crap i need a rom to fix my crossover the buttons are no longer mapped after a hard reset. please help.
Slow
Well, it's been slow goings so far. I downloaded the open source files for the p8000 and it looks like they just built the original rom from a generic build. I've been trying to get a more customized build setup but I need to do some more reading so far. One of the problems is that instead of an akmd(2) binary for orientation and compass it uses three separate modules. Plus the hci_attach is a bit different as well and so is the bluetooth. So that significantly hampers the ease of even a basic port.
As far as the gentleman with the question about a rom to fix your device. The best I can do right now is to upload a clockwork mod backup after I do a factory reset. I don't get much time to work on this between my wife and daughter.
Also, do you have adb access to your device? Surely it wouldn't be too difficult to adb push the correct keymapping files back to your phone.
You say a hard reset messed up your mappings? What problems were you experiencing prior to the reset?
Crossover
Hello,
I just wanted to let you know that there are people watching your thread. I am very interested in this as my parents have Crossovers and have recently rooted and unlocked them (well, I did) and set them up to work on Net10.
The only issue I've noted is that there are some failures, like the Market refusing to install apps no matter what is done. I'm going to install your ClockworkMod in hopes that later it might be useful.
I realize there isn't a large development scene for the P8k yet, and maybe there won't be but it's always a great hope that those with the capabilities might take pity. I was almost thinking that it might be my foray into actually looking deeper at the code than the small bit I've done.
Kind Regards,
Kaylus
Yup
kaylus said:
Hello,
I just wanted to let you know that there are people watching your thread. I am very interested in this as my parents have Crossovers and have recently rooted and unlocked them (well, I did) and set them up to work on Net10.
The only issue I've noted is that there are some failures, like the Market refusing to install apps no matter what is done. I'm going to install your ClockworkMod in hopes that later it might be useful.
I realize there isn't a large development scene for the P8k yet, and maybe there won't be but it's always a great hope that those with the capabilities might take pity. I was almost thinking that it might be my foray into actually looking deeper at the code than the small bit I've done.
Kind Regards,
Kaylus
Click to expand...
Click to collapse
I haven't had any problems with the market refusing to install apps but I do sometimes run across the no connection error with the market when on wifi. Although I did notice this before I rooted my crossover. Sometimes disabling and re-enabling the wifi helps. I really do think it is a bug somewhere in the original rom.
As far as the custom recovery image. Everything seems to be working pretty good. I use it mainly for restoring previous backups. I would say I've restored my backup at least a dozen times. Occasionally it states there was an error restoring .android secure but I have yet to track that down. I need to double check the recovery.fstab to make sure I have everything set right for the mount points.
stevotdo said:
I haven't had any problems with the market refusing to install apps but I do sometimes run across the no connection error with the market when on wifi. Although I did notice this before I rooted my crossover. Sometimes disabling and re-enabling the wifi helps. I really do think it is a bug somewhere in the original rom.
Click to expand...
Click to collapse
I'm actually completely stuck at this point. I'm rooted, unlocked, different carrier, APN set correctly. I can access data and voice -- but it just hangs at "Downloading..." on the market. If I factory reset it works initially but after reboot it fails. I'm not quite sure why this occurs and if it is just this phone or a side-effect of using it on a different carrier.
Strangely Wi-fi doesn't resolve it.
As far as the custom recovery image. Everything seems to be working pretty good. I use it mainly for restoring previous backups. I would say I've restored my backup at least a dozen times. Occasionally it states there was an error restoring .android secure but I have yet to track that down. I need to double check the recovery.fstab to make sure I have everything set right for the mount points.
Click to expand...
Click to collapse
I'll give your recovery a run and let you know, if you manage CM7 let me know I know it's a big undertaking. Thanks for the response.
Market Error
As far as the Android Market hanging. I see a few references to it being cause by the .android_secure folder becoming corrupted on the sd card.
One temporary fix suggest moving all the installed apk's back to the phone memory and deleting the .android_secure folder. Then rebooting and moving those apps back to the sd card.
That seems like some wasted time if it doesn't happen to work. I would just turn the phone off, remove the sdcard, and restart (granted any apps that were moved to the sdcard wont work until it is reinserted.) Then I would try to download and install an app. If that works then shutdown, insert sd, and reboot.
I'm really curious if the problems with .android_secure that you and i are having aren't just more bugs in the original rom.
Just as a poster above me said, I am watching this thread and really appreciate everything you are doing. Thanks again.
Well I appreciate the support. I just hope to be able to offer a rom sometime soon. Unfortunately I won't have anymore free time till Tuesday
crimson12 said:
Just as a poster above me said, I am watching this thread and really appreciate everything you are doing. Thanks again.
Click to expand...
Click to collapse
Not an issue, life first, then android development.
Sent from my Galaxy Nexus using Tapatalk
Pantech Crossover Update
Ahhhhh check out the pantech support page for the crossover. They finally have the Gingerbread update.
http:// pantechusa. com/xupgrade/ remove spaces.
Which is great because I soft bricked my phone (don't ask) and this was going to be the only way to fix it.
stevotdo said:
Ahhhhh check out the pantech support page for the crossover. They finally have the Gingerbread update.
http:// pantechusa. com/xupgrade/ remove spaces.
Which is great because I soft bricked my phone (don't ask) and this was going to be the only way to fix it.
Click to expand...
Click to collapse
Oh hell yes finally. Thanks for the notice!
Sent from my Galaxy Nexus using Tapatalk
Mildly related, but have you figured out how to root the gingerbread ROM? I've tried ginger break to no avail.
Sent from my Galaxy Nexus using Tapatalk 2
anyone have a stock image of the 2.2 for android my phone came preupgraded to 2.3.6 and i would like to have it rooted over being on gingerbread since a root method hasnt been found yet for the new firmware
Bricked?
I tried to use the pantech provided gingerbread update this morning. It got about an eighth of the way through and failed. It instructed me to reboot while holding volume up and home and power. That put it in software updating mode. I tried the upgrade 3 more times, it failed at the same point each time. Now my phone is stuck in S/W Updating mode and I can't seem to get it out. I've tried pressing volume up and down for 10 seconds, and pressing volume down and home while powering on, nothing seems to make a difference. Any thoughts about how to at least get me back to froyo?
formattdd said:
I tried to use the pantech provided gingerbread update this morning. It got about an eighth of the way through and failed. It instructed me to reboot while holding volume up and home and power. That put it in software updating mode. I tried the upgrade 3 more times, it failed at the same point each time. Now my phone is stuck in S/W Updating mode and I can't seem to get it out. I've tried pressing volume up and down for 10 seconds, and pressing volume down and home while powering on, nothing seems to make a difference. Any thoughts about how to at least get me back to froyo?
Click to expand...
Click to collapse
Nevermind, bad usb cable.
formattdd said:
Nevermind, bad usb cable.
Click to expand...
Click to collapse
Glad you got it working!
Sent from my Galaxy Nexus using Tapatalk 2
Yeah now I'm having the same regrets as above. No root.
Sent from my PantechP8000 using XDA
I don't know where to post this, I'm coming here all panicked and retarded, so I'm apologizing in advance.
I literally bought my Galaxy S 4G from WIND (Canada) this morning. From what I understood, upgrading the OS was dangerous, all I wanted to do was root... I followed this guide: ht tp ://w ww.gal axyforum s.ne t/forum/off-topic-forum/5053-rooting-tutorial-here-posted-permission-t-mobile-galaxy-s-4g-gingerbread.html (remove spaces)
which I found in a post on these forums. Someone who also was on WIND said it worked fine for them... They were rooted. I foolishly tried it, everything seemed FINE. When I load CWM it can't mount my SD card. I don't know what to do, it's stuck in T-Mobile boot screen loop if I try to exit.. I literally just stopped crying. My dad is going to KILL me if he finds out I ****ed up the new phone I just bought HOURS ago. I don't know what the **** to do, I don't know what's wrong. I need help, please. Anybody know what I can do? I don't care about rooting, I just need my device to work. Please, someone, anyone with any idea, what should I do? I can get back into download mode, and CWM. Is there anything I can do there? There's a recovery guide pinned but it says it's for the T-Mobile version, which I read is the same, can I use that to fix my phone?
This is my first Android device, I've never owned one before. I don't know ****, I shouldn't have tried anything... I just got cocky and made a mistake. I'm usually very good with this kind of stuff. Please someone tell me if there's something I can do to fix this, please!
I'm sorry if I sound stupid, I'm trying not to, I'm just really panicky and stressed right now.
I've tried searching through the forums - I still am searching through them, I'm sorry if I missed a post that can help me.
EDIT: I found someone who is also stuck in a boot loop... He seems to have SD Card issues as well, but doesn't speak English very well, so I don't thing he was able to communicate what his issue was...
Quote:
Originally Posted by GMK63
.......(---------THAT WHAT I FOLLOWED .
But I did the first part and They said i should get the stuff I store on my SD Card to pull out a file (``12) In CWM, use your volume up/down positions to navigate, scroll down to "Install Zip From SDcard". Select with a click of the power button. Navigate to where you put sms-T959V-KJ6-v0.1.1-rc1-unsigned-update.zip (in the root of your SDcard) and select with the power button. Confirm you want to install.
``)
but it doesn't give me the option to go get it on my SDcard and Now my Phone just turns on and off with the samsung galaxy S logo plus T-mobile exclusive logo . The only possitive thing about all the damage is that I can still put my phone on dowload mode and I just think if someone knows how to get my phone back to it state they will need me to put it on download mode.
Thank you in advance for your Help, for replying and offering to help.
I appriciate it. My phone is Mobillicity carrier just like wind .[/B]
Then, user bhundven replies to him saying:
Ok, this is really simple. I've explained it in quite a few threads in the Galaxy S 4G forums in General, Q&A, and the Dev forum. I'm going to explain this, but in a way to be more general. So I'm being verbose in case anyone else with a T959W happens to run across this and has not tried anything yet.
Again, I'm not good with windows at all, and I prefer it that way.
If you're on windows, check out our wiki:
http://forum.xda-developers.com/wiki...xy_S/SGH-T959V
There is tons of help there for setting up heimdall on windows with all the right drivers and such.
Once you have heimdall setup get AntonX's latest cwm zip for his kernel.
This kernel is a BML kernel, and this guide I am giving you right now will help you get cm9 installed which is an MTD kernel. You can find out more about BML vs. MTD here.
Once you have downloaded AntonX's kernel, extract the zImage from it and open up the terminal/cmd prompt and navigate to the directory you extracted the zImage to.
Put your phone into Download Mode and type the following in the command prompt:
Code:
heimdall flash --kernel zImage
The heimdall program will flash this kernel+initramfs to the kernel partition and reboot the phone. Do not unplug the usb cable until you see the "Galaxy S" screen. When you see that screen, unplug the usb cable and remove the battery from the back.
Assuming you downloaded CM9 and put it on your sdcard already, you can get into recovery by holding the vol+ and vol-, then pressing the power button to turn the phone on. When you see the "Galaxy S" screen, let go of the buttons, and you should be in the recovery now.
This is where things get a little tricky. If you have not tried to do anything to your phone yet. This would be a great time to use the "Backup and Recovery" menu on CWM. Do a full backup.
The "assert 7" error that the previous person got was because the cwm install script (the updater-script) checks the already installed /system/build.prop's data against the "to be installed" build.prop to verify this rom can be installed. If it doesn't exist, then it moves forward.
So the first order of business is to wipe the /system partition. Go to "Mounts and Storage" and format the system partition.
Now go back to the main screen and do "Factory Reset/Wipe Data".
Now go "Install zip from sdcard" -> "choose zip from sdcard" -> and use the volume keys to select the zip file.
After the rom is installed, navigate back to the main screen and "Reboot the system now" if it doesn't reboot by itself.
When the phone reboots, because it is going from BML to MTD, it obviously can't just install the files to what would be an MTD partition if the kernel knows nothing about MTD. So it boots into the newly installed MTD kernel and continues the installation, which in the end will also reboot again.
The first boot is very slow. It is building a cache of all the pre-installed system applications. Let it sit for a while. I know it's tempting to go play with your phone right away, but resist if you can.
The next CM9 release will be on a different kernel, and albeit a much better rom.
I will also be adding OTA Asserts for SGH-T959W so that you will not have to wipe /system before installing the rom, but I do that still just for good measure. But this also means that your phone will work properly with the google play store.
If this still does not work, please let me know what went wrong and I will be happy to assist!
-Bryan
Is what Bryan is saying my solution? I don't think he understood the SD Card mount issue. Does anyone know how to fix that? I really hope to hear from you guys ASAP before my dad catches on... Please. I really need help. I'll search more in the morning, it's 1 AM here.
Okay well first of all.. GET A GRIP OF YOUR SELF
*slaps twice across the face
This phone is unbrickable so can you get in to download mode? (power off phone then when it's off hold the volume up and down buttons at the same time, while holding them down connect your phone to a usb cable)
A green android digging thing should show on your screen. Tell me when you get this far.
Sent from my HTC VLE_U using xda app-developers app
As a matter of fact, you don't entirely need a download mode screen to recover your device too. I've gotten to a pixelized colorful screen and thought my phone was done for, but Odin/Heimdall still recognized it, so I was able to recover my phone.
Calm down and as long as your phone can still be detected on your computer, you will be fine. Odin or Heimdall should be able to show that he device was "added" when you plug it in.
bkoon1218 said:
As a matter of fact, you don't entirely need a download mode screen to recover your device too. I've gotten to a pixelized colorful screen and thought my phone was done for, but Odin/Heimdall still recognized it, so I was able to recover my phone.
Calm down and as long as your phone can still be detected on your computer, you will be fine. Odin or Heimdall should be able to show that he device was "added" when you plug it in.
Click to expand...
Click to collapse
That's true, just make sure you have the drivers installed for the phone first and for the purpose of my method of recovery download Odin. If you did everything correctly you'll see a green light in Odin under recognized devices once you're in download mode
Sent from my HTC VLE_U using xda app-developers app
lonoguge said:
Okay well first of all.. GET A GRIP OF YOUR SELF
*slaps twice across the face
This phone is unbrickable so can you get in to download mode? (power off phone then when it's off hold the volume up and down buttons at the same time, while holding them down connect your phone to a usb cable)
A green android digging thing should show on your screen. Tell me when you get this far.
Sent from my HTC VLE_U using xda app-developers app
Click to expand...
Click to collapse
Thanks for the slaps, I needed them!
Yes! I think I am still able to get into download mode, atleast I was able to last night (After the loop issue). Also, I formatted (factory reset option or something?) my settings when I was in CWM last night assuming that would change it back to the way it was, or atleast fix the SD mount problem..I hope this doesn't cause any issues.
What should I do when I'm in download mode?
bkoon1218 said:
As a matter of fact, you don't entirely need a download mode screen to recover your device too. I've gotten to a pixelized colorful screen and thought my phone was done for, but Odin/Heimdall still recognized it, so I was able to recover my phone.
Calm down and as long as your phone can still be detected on your computer, you will be fine. Odin or Heimdall should be able to show that he device was "added" when you plug it in.
Click to expand...
Click to collapse
That's great news! It's nice to hear that someone who's phone was also messed was able to repair it.
lonoguge said:
That's true, *just make sure you have the drivers installed for the phone first and for the purpose of my method of recovery download Odin. *If you did everything correctly you'll see a green light in Odin under recognized devices once you're in download mode
Click to expand...
Click to collapse
Where can I get these drivers? Should I download the latest version of Odin?
I'll try this as soon as I get back from taking my little sister to school.
I just want to say again, this is the SGH-T959W from WIND in Canada. It's apparently the same hardware as the SGS4G from T-Mobile, just different software. I hope this isn't a problem.
Thank you both for replying so soon. After tossing and turning in bed for the last 5 hours, barely getting any sleep, it's such a relief to read these posts!
Obviously you didn't read too much if you bought the phone and tried to mess with it the same day. You would have seen if you went to the 2nd page of here and actually read something like this, http://forum.xda-developers.com/showthread.php?t=1552119 where I clearly say, it is it different, you will get boot looped, I am working on a package to fix it, and for anyone on a wind phone to hold on and wait.
I don't have time to try and help and fix every single wind phone in the world because people get too impatient and start flashing everything in the world from the first post they read. Odin and Heimdall fail at certain parts of flashing this phone. I am trying to give the Heimdall creator as much as I can to help fix this, so everyone telling to flash this or that package, it's not going to work, it will fail. I have verified this 100 times with Heimdall.
I can't put together a 1click package that fails flashing, that's why people are ending up in this position in the first place.
I can get your phone fixed but not right this second. There is no permanant damage done, and the less you just keep flashing random stuff, the more likely the chance I can help you fix it, but I'm busy, I run my own business and my paying customers come first as does my mortgage and bills before spending an hour teamviewed into someones pc to fix this.
So hang tight, I will try later to get this fixed, it's not screwed, quit flashing anything you find.
Past what getochkn just said (and please do ignore the "advice" given by people who don't experience with a T-959W), next time you see a "helpful" post on some site that starts off "get this from [the original source]" -- please, please take the time to read the original source.
Secondly, just because your phone has the a similar "trade name" as another phone doesn't mean they are even close to the same inside. Even the model numbers don't mean much. Firmware from a T-959 generally won't work on a T-959V, and, as you have found out, T-969V firmware can make a T-959W a nice paperweight for a while.
Thirdly, I just don't "get" why people even consider flashing their phone on the first day they own it, before they have any idea what it came with and what it can do, not to mention voiding their warranty before even the buyer's remorse period has expired.
While you're waiting for someone to bail you out, you might want to take the time to download Java, the Microsoft C++ executables, and a full version of Heimdall.
getochkn said:
Obviously you didn't read too much if you bought the phone and tried to mess with it the same day. You would have seen if you went to the 2nd page of here and actually read something like this, http://forum.xda-developers.com/showthread.php?t=1552119 where I clearly say, it is it different, you will get boot looped, I am working on a package to fix it, and for anyone on a wind phone to hold on and wait.
I don't have time to try and help and fix every single wind phone in the world because people get too impatient and start flashing everything in the world from the first post they read. Odin and Heimdall fail at certain parts of flashing this phone. I am trying to give the Heimdall creator as much as I can to help fix this, so everyone telling to flash this or that package, it's not going to work, it will fail. I have verified this 100 times with Heimdall.
I can't put together a 1click package that fails flashing, that's why people are ending up in this position in the first place.
I can get your phone fixed but not right this second. There is no permanant damage done, and the less you just keep flashing random stuff, the more likely the chance I can help you fix it, but I'm busy, I run my own business and my paying customers come first as does my mortgage and bills before spending an hour teamviewed into someones pc to fix this.
So hang tight, I will try later to get this fixed, it's not screwed, quit flashing anything you find.
Click to expand...
Click to collapse
THANK YOU THANK YOU THANK YOU THANK YOU THANK YOU!
I really didn't read enough, big mistake, I was just really cocky because I've modded almost every device I own (Wii, PSP, PS3, PS2 various and iDevices [mine, and friends]). Of course, they're all different (Not saying it's all the same thing! ), I just felt very confident because I've never had issues with anything before. At least this is a good learning experience, I've really been put in my pace. I always felt that bricking was something that happened to other people, it doesn't happen to me. I know that sounds stupid, but idk, that's just how I felt. I physically feel sick over this 'whole ordeal (Seriously), I'm such an idiot. >.<'
Thanks for the warning, I won't flash anything! I'm so relieved to hear that there's no permanent damage done, and to be able to speak to someone who's familiar with this specific problem and this specific model of the SGS4G, AND is willing to help me!
Do you know when you'll be able to help me? Of course, take your time, I completely understand that you have other stuff going on, I'm just wondering to see if I can maybe think of some cover up so my dad doesn't find out.
Also, I have a 14 day warranty, is it void now even though the root didn't work? I'm assuming it is.
Edit: Yup, if what jeffsf says is true, it's void.
jeffsf said:
Past what getochkn just said (and please do ignore the "advice" given by people who don't experience with a T-959W), next time you see a "helpful" post on some site that starts off "get this from [the original source]" -- please, please take the time to read the original source.
Secondly, just because your phone has the a similar "trade name" as another phone doesn't mean they are even close to the same inside. Even the model numbers don't mean much. Firmware from a T-959 generally won't work on a T-959V, and, as you have found out, T-969V firmware can make a T-959W a nice paperweight for a while.
Thirdly, I just don't "get" why people even consider flashing their phone on the first day they own it, before they have any idea what it came with and what it can do, not to mention voiding their warranty before even the buyer's remorse period has expired.
While you're waiting for someone to bail you out, you might want to take the time to download Java, the Microsoft C++ executables, and a full version of Heimdall.
Click to expand...
Click to collapse
I'm just very impatient sometimes. I really do enjoy doing this kind of stuff, it's fun for me. I just got really excited and wasn't thinking straight and just went out and tried rooting it. I've wanted an Android for a while now, and have always planned to root it to unlock it's full potential. I've never modded anything else day 1 (and never will again), this is the first time I've done this. I feel terrible about it.
Will do, thanks for helping, jeffsf.
If your still under 14 days return it with a stupid I don't know what happened look. If its stuck just on the tmob screen they most likely will never know what you did. Your other choice is to be a man and own up to it. Tell your dad and take your lumps. That choice is yours. Give it serious thought before you choose as it might define what type of person you end up becoming.
hechoen said:
If your still under 14 days return it with a stupid I don't know what happened look. If its stuck just on the tmob screen they most likely will never know what you did. Your other choice is to be a man and own up to it. Tell your dad and take your lumps. That choice is yours. Give it serious thought before you choose as it might define what type of person you end up becoming.
Click to expand...
Click to collapse
I feel like they might know. I'm willing to try it as a last resort, I'd like to give getochkn a shot first.
I'll tell my dad what happened after it's fixed. I just can't deal with him stressing me out about it more than I already am.
I will have a package probably tomorrow that will provide as detailed instructions as I can.
getochkn said:
I will have a package probably tomorrow that will provide as detailed instructions as I can.
Click to expand...
Click to collapse
Oh, wow! That's much sooner than I was expecting! Thanks for taking the time to do this for me, it really means a lot. Thank you so much getochkn!
Package and instructions here.
http://forum.xda-developers.com/showthread.php?t=1956025
getochkn said:
Package and instructions here.
http://forum.xda-developers.com/showthread.php?t=1956025
Click to expand...
Click to collapse
Thank you so much getochkn!
I read all the instructions before attempting this. But, I have a problem. Heimdall failed to flash. It said something about failing to retrieve the PIT or something? So, I tried again. Didn't work. So, I restarted my computer, and my phone.
Phone doesn't go into download mode, instead, I end up on a screen saying "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
What should I do?
BagelBreath said:
Thank you so much getochkn!
I read all the instructions before attempting this. But, I have a problem. Heimdall failed to flash. It said something about failing to retrieve the PIT or something? So, I tried again. Didn't work. So, I restarted my computer, and my phone.
Phone doesn't go into download mode, instead, I end up on a screen saying "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
What should I do?
Click to expand...
Click to collapse
That firmware screen should detect as download mode still in Heimdall. I have gotten that and reflashed from Heimdall before. Not sure why it's trying to download the pit, it should only do that when you tell it to download pit. Flashing shouldn't trigger that. See if Heimdall will detect it in that firmware recovery mode and I guess try again, otherwise your phone is really borked.
getochkn said:
That firmware screen should detect as download mode still in Heimdall. I have gotten that and reflashed from Heimdall before. Not sure why it's trying to download the pit, it should only do that when you tell it to download pit. Flashing shouldn't trigger that. See if Heimdall will detect it in that firmware recovery mode and I guess try again, otherwise your phone is really borked.
Click to expand...
Click to collapse
Thank you for the quick reply!
It worked! I really can't thank you enough! Thanks again for taking the time to do this!
I think it may have said "Uploading Pit" because it said it again this time, but it didn't encounter a problem when it did that.
I know I have 3 choices, the one I would like to choose is ICS. Would mind pointing me in the direction of an ICS ROM that's compatible with my device? I'm afraid to use something that may not work and mess up my phone again.
EDIT: Actually, I think I'll just stick with this. I just installed the twist kernal and the modem, everything works, I'm rooted and have recovery. I'd rather not mess with it until I'm more experienced with droids.
Thanks again everyone, especially you getochkn! I'm so relieved that my phone is working again! My dad didn't notice that I wasn't using the new phone I got, so I didn't have to cover up or anything.
Title speaks for itself.
I've been lurking the forums for a few months, so... Hi! My tech vocab is limited, but I catch on quickly. Please bare with me.
Anyways, Kies wanted me to upgrade my firmware on my 7.0, so like... Yeah. Stupid me didn't remember that the device was sitting in my lap and connected to my computer WHILE going through the upgrade, and I was feeling uncomfortable, and moved. By doing that, the USB unplugged from the device. I've tried going through with the upgrade via Kies after, but... Just no. Now my device is stuck on the "Firmware upgrade encountered an issue" screen, and no matter how many times I try to reboot it, soft reboot, entering download mode, it always, ALWAYS, goes back to that screen.
So, I plug it in again, and connect it to Odin. But... Wait! I don't have any of the files I need. So I look around and download files instructed by several people for my specific device, but I don't think I need them for this specific problem.
What exactly do I need to get, and how to I put it all together in Odin to make my device work again? I don't really care if all my files get deleted (although it would be great if I could keep them), I just need to get this resolved before Tuesday, since I have textbooks on it that I need for classes.
tl;dr I'm lost, and I need a push in the right direction.
Thanks in advanced!
First, I know how nerve racking this is so I am going to try, and help. I am new to Samsung, but I would think that a stock firmware flash from Odin would fix it. Look in the development forums for officials firmware, and download it. I would give you a link, but you forgot to post what model you have. It can be important. Good luck.
P.S. congrats on joining xda. Sorry it took this o bring you onboard.
Sent from my ADR6425LVW using Tapatalk 2
JeramyEggs said:
First, I know how nerve racking this is so I am going to try, and help. I am new to Samsung, but I would think that a stock firmware flash from Odin would fix it. Look in the development forums for officials firmware, and download it. I would give you a link, but you forgot to post what model you have. It can be important. Good luck.
P.S. congrats on joining xda. Sorry it took this o bring you onboard.
Sent from my ADR6425LVW using Tapatalk 2
Click to expand...
Click to collapse
Ah! Thanks! I can't believe I forgot to post my model ahaha;
p3113.
I'll go ahead and look in that thread. If I come across any other problems, I'll post them here.
Update: I've clarified that I can't enter download mode. How do I go about flashing with Odin if I can't do that?
I got that screen before. Flash again using ODIN and a full charged laptop, do not load any pit file.
churuchu said:
Ah! Thanks! I can't believe I forgot to post my model ahaha;
p3113.
I'll go ahead and look in that thread. If I come across any other problems, I'll post them here.
Update: I've clarified that I can't enter download mode. How do I go about flashing with Odin if I can't do that?
Click to expand...
Click to collapse
looks strange
switch off your device completely, now just press power button and volume "DOWN" button simultaneously and dont leave them.
well, it should not show the "SAMSUNG GALAXY TAB 2 7.0" thing and directly boots the screen into the download mode.
do you mean that, even on doing this too u get the error message as prescribed by you in your above comments--->"error updating firmwire" or something like that??? cz manufacturers first check your device is under warranty or not by entering into download mode(by checking the binary counter) and then booting and checking for root apps(some manufacturers dont check this thing, they just check binary counter)
well for entering into recovery mode u ve to do the reverse----->power button+volume "UP" button, but in this case you it should show that "SAMSUNG GALAXY TAB 2 7.0" thing, as soon as it display you should leave your power button but keep pressing your volume"UP" button.
do you mean even on doing this too you get the same error message?????
if yes, then it is likely that your device is permanently bricked(well, NOT SURE), but then you should consult to samsung for a replacement if its within warranty, else there may be some advanced users or software developers in this forum who may help you, i am just an amateur, sharing my experience with such devices.
Someone please please help me. I am in desperate need of a solution. And before I lay out the issue I am having, I would like to thank everyone for taking their time to read through my post and give their input. I truly appreciate it everybody. Much much thanks.
Just as a disclaimer, I've looked all over the internet, everywhere I can possibly find for days on end, and none of what I found worked for me. It feels like I tried everything there could be, and that is why I am coming here. Again, thank you.
So here's a little background information: I have a Verizon Samsung Galaxy S4 (SCH-I545). I got the phone over the summer, and as soon as I received the phone I was updated to the apparently dreadful VRUMAE7 update. There afterwards, I tried rooting the phone. I've had rooting experience before with decent success, and never ran into problems like I did. It took awhile for me root my S4, but after awhile I was able to successfully root it. Although, I'm pretty sure I may have done something wrong. You will see why shortly.
So a week or two back, my S4 prompted me to update to the next update. I believe it was Android 4.3 (VRUEMJ7). I was very excited for the update and tried running it. But every time I accepted the update and tried updating, my phone went into Recovery to download the new update and stalled out with an error. Thereafter I would have to reboot the phone to get it working again. After failing to update multiple times, I realized that it is probably because I messed up my root. So without doing much research, I simply tried flashing the stock firmware that came with my phone thinking it should work pretty flawlessly.
I have a Mac OS, so using VmWare Fusion with Windows 7, I downloaded Odin and booted up my phone on Recovery mode, downloaded the stock VRUMAE7 firmware I found online, and began flashing. But Odin threw me a error, so I tried rebooting my phone thinking it would go back to normal. BUT this time, it kept going into recovery mode with a yellow Triangle saying firmware was installed incorrectly, etc. I was so frustrated at this point, thinking that I truly may have bricked my phone.
I began on this long journey of going through all the sources I could find online possible, downloading every type of Verizon S4 firmware I can find, trying every Odin method possible, and spending long long hours of the night biting my fingers at my dreadful fate. I even tried flashing the stock PIT File along with my stock firmware, to see if that would fix it. But no luck. I also tried using a standard windows machine rather than VMware, still with no luck.
I ask you all to please suggest any ideas, thoughts, or inputs you possibly can. I am willing to try anything and everything at this point. Please do help. I appreciate you guys reading through my lengthy question, sorry for that. Just wanted to lay everything out.
Thank you very very much.
muazra said:
Someone please please help me. I am in desperate need of a solution. And before I lay out the issue I am having, I would like to thank everyone for taking their time to read through my post and give their input. I truly appreciate it everybody. Much much thanks.
Just as a disclaimer, I've looked all over the internet, everywhere I can possibly find for days on end, and none of what I found worked for me. It feels like I tried everything there could be, and that is why I am coming here. Again, thank you.
So here's a little background information: I have a Verizon Samsung Galaxy S4 (SCH-I545). I got the phone over the summer, and as soon as I received the phone I was updated to the apparently dreadful VRUMAE7 update. There afterwards, I tried rooting the phone. I've had rooting experience before with decent success, and never ran into problems like I did. It took awhile for me root my S4, but after awhile I was able to successfully root it. Although, I'm pretty sure I may have done something wrong. You will see why shortly.
So a week or two back, my S4 prompted me to update to the next update. I believe it was Android 4.3 (VRUEMJ7). I was very excited for the update and tried running it. But every time I accepted the update and tried updating, my phone went into Recovery to download the new update and stalled out with an error. Thereafter I would have to reboot the phone to get it working again. After failing to update multiple times, I realized that it is probably because I messed up my root. So without doing much research, I simply tried flashing the stock firmware that came with my phone thinking it should work pretty flawlessly.
I have a Mac OS, so using VmWare Fusion with Windows 7, I downloaded Odin and booted up my phone on Recovery mode, downloaded the stock VRUMAE7 firmware I found online, and began flashing. But Odin threw me a error, so I tried rebooting my phone thinking it would go back to normal. BUT this time, it kept going into recovery mode with a yellow Triangle saying firmware was installed incorrectly, etc. I was so frustrated at this point, thinking that I truly may have bricked my phone.
I began on this long journey of going through all the sources I could find online possible, downloading every type of Verizon S4 firmware I can find, trying every Odin method possible, and spending long long hours of the night biting my fingers at my dreadful fate. I even tried flashing the stock PIT File along with my stock firmware, to see if that would fix it. But no luck. I also tried using a standard windows machine rather than VMware, still with no luck.
I ask you all to please suggest any ideas, thoughts, or inputs you possibly can. I am willing to try anything and everything at this point. Please do help. I appreciate you guys reading through my lengthy question, sorry for that. Just wanted to lay everything out.
Thank you very very much.
Click to expand...
Click to collapse
Hi there,
it seems an easy problem but do it at your own risk I don't take responsibility of bricked device,etc
so lets go with what you need:
A- Odin [I believe you already have it]
B- stock rom go to this site:
androidayos.com/samsung-galaxy-s4-odin-stock-firmware/
and choose the suitable stock rom based on your Baseband version
C- Drivers installed for your device [if your mac/laptop recognizes your device then skip this step if not google it,download the drivers and install them]
IMPORTANT:Make sure you have 80% or more on battery
after you get these stuff install the device drivers as mentions in C then turn your device off and power it while holding volume up it should take you to download.now open odin and navigate it to the rom which you downloaded from B and flash it .wait for green color to appear and your back to your stock now it should open normally hope that I helped
I decided to root my Galaxy S8,and im pretty uneducated on how to do those sorts of things, but there is what looked to be an very easy tutorial (snapdragon).
while following those instructions, i missed the requirement of needing adb, and so odin(prince) failed. well, i disconnected my phone. took it out of download mode.
now its forever stuck in an infinite installing system update loop.
i checked for solutions online. go to commands, a factory reset. ect ect
except i get a:
#fail to open recovery_cause(missing file)
which leads me to believe i messed up my software, no biggie, i can just fix it though oden... right?
wrong. opening oden ive come to realize i can no longer get my phone into download mode, and neither does oden recognize my phone as a well... a phone.
so im at a loss of what exactly to do.
do i go through my provider, hoping they fix the issue?
do i wait for a solution here, one i might not have the skills to accomplish?
or do i pay out the pocket to get someone to fix this thing. i really dont know
OU812?? said:
I decided to root my Galaxy S8,and im pretty uneducated on how to.........
Click to expand...
Click to collapse
I don't have this device but, your best bet is to post this question within the following Q&A thread that's specific to your device and variants.
https://forum.xda-developers.com/showthread.php?t=3582142
Good Luck!
~~~~~~~~~~~~~~~
UNLESS asked to do so, PLEASE don't PM me regarding support. Sent using The ClaRetoX Forum App on my SM-G900T device.
OU812?? said:
I decided to root my Galaxy S8,and im pretty uneducated on how to do those sorts of things, but there is what looked to be an very easy tutorial (snapdragon).
while following those instructions, i missed the requirement of needing adb, and so odin(prince) failed. well, i disconnected my phone. took it out of download mode.
now its forever stuck in an infinite installing system update loop.
i checked for solutions online. go to commands, a factory reset. ect ect
except i get a:
#fail to open recovery_cause(missing file)
which leads me to believe i messed up my software, no biggie, i can just fix it though oden... right?
wrong. opening oden ive come to realize i can no longer get my phone into download mode, and neither does oden recognize my phone as a well... a phone.
so im at a loss of what exactly to do.
do i go through my provider, hoping they fix the issue?
do i wait for a solution here, one i might not have the skills to accomplish?
or do i pay out the pocket to get someone to fix this thing. i really dont know
Click to expand...
Click to collapse
Try to intsall smartThings on your pc or lap and then download drivers for your phone and it will autom.reopening to bootloader hope that will help i tried before