Well here is something that I hope is the start of some hardcore hacking.
This is an ODIN that I created of stock-rooted ED1 for the DROID Charge. In the course of making this, I bricked my charge (first attempt failed in ODIN) and then created a working ODIN that un-bricked it. I then upgraded to ED2 (I confirmed that I lost root as well) so I could test if this will downgrade back to ED1 and it worked and I have root again!
Instructions for ODIN (for those who are unfamiliar with it):
1. Open ODIN.
2. Put the phone into download mode. Do this by powering off your phone, pulling out the battery, and then holding volume down while connecting it to your pc. A giant yellow triangle should be on the phone's screen and it should say 'Downloading...' ODIN should say 'Added!!' and one of the boxes will be yellow and say '0:[COM#]'
3. Click the button labeled 'PDA' and locate the file you are wanting to flash. For emphasis: YOU MUST USE THE PDA BUTTON!
4. Click start. Do not disconnect the phone while it is flashing, it can cause some serious damage.
5. Wait.
6. When finished, unplug the phone, put the battery back in and power up the phone.
Every time I've flashed this, the phone booted straight into recovery. Just select reboot (press home) and it boots up normally. It should probably be recommended to wipe data and cache afterwards, but I didn't and all of my data stayed in tact.
Multiple people have reported that this works. Use at your own risk. I am not responsible for anything that happens to your phone if this doesn't work.
Thanks to imnuts for the HOW-TO thread on creating ODIN builds.
Download here.
Download ODIN here.
to my redbull habit if you feel the need.
I feel dumb for asking, but what are you using to flash this to the phone? I've never used anything other than simple one click root programs, so if you could give a little more detail I'd be happy to try it out.
Download Odin here: http://goo.gl/52aY1
Download Drivers here: http://goo.gl/Tbcca
Download stockrootedED1-20110517.tar.md5 http://goo.gl/kD3Ld
1. Open Odin3 v1.30
2. Remove battery,Hold Vol down. Connect USB to computer and phone then press power. It should take you to a yellow android.
3. Click PDA Button
4. choose stockrootedED1-20110517.tar.md5
5. Click on the Start button
6. Don't Touch and allow the phone to reboot
7. If its taking a while to start DONT PANIC, its perfectly normal
Thanks for the guide, but it doesn't do anything for me, seems like Odin doesn't even know my phone is there. When I plug it in I get the Verizon media manager link to pop up though.
I edited my first post with a link to ODIN and instructions. I guess I'm a little slow with the typing because you beat me to it medjam, but you left out the step of putting the phone into download mode.
Works for me, though the first time I rebooted I didn't have any network reception. Another reboot fixed that.
Wish I could get rid of the "system update available" pop up, but at least I'm rooted again. Thanks!
that's awesome...I gonna try this right now....If i brick my phone I will just swap it out a vzw..They are tarded and can't tell the difference any ways. Will report back once I finish.
Zeek215 said:
Works for me, though the first time I rebooted I didn't have any network reception. Another reboot fixed that.
Wish I could get rid of the "system update available" pop up, but at least I'm rooted again. Thanks!
Click to expand...
Click to collapse
Once rooted go into your build.prop file and every thing that says ED1 change it to ED2...that should quit the nagging to update. Then restart your phone
Credit goes to Jt3 for that info as he posted it in the Charge forum at android central.
Zeek215 said:
Works for me, though the first time I rebooted I didn't have any network reception. Another reboot fixed that.
Wish I could get rid of the "system update available" pop up, but at least I'm rooted again. Thanks!
Click to expand...
Click to collapse
AWESOME!!! So glad to help!
Very nice!
I know that this will kick start the development of this device now that everybody can haz root.
so just to be clear here, this will bring you back from ED2 down to ED1. Does this method require you to have already rooted while you were on ED1 and then upgraded to ED2 and lost it or will this work for everyone?
Thanks in advance
streetlightman said:
so just to be clear here, this will bring you back from ED2 down to ED1. Does this method require you to have already rooted while you were on ED1 and then upgraded to ED2 and lost it or will this work for everyone?
Thanks in advance
Click to expand...
Click to collapse
Should work for everyone. My Charge that I just ran it on was never rooted before.
das7771 said:
that's awesome...I gonna try this right now....If i brick my phone I will just swap it out a vzw..They are tarded and can't tell the difference any ways. Will report back once I finish.
Click to expand...
Click to collapse
They certainly can tell. Don't send back a phone because you broke it. That makes ALL of us look like assholes and promotes the disturbing trend of locking bootloaders. Be an adult.
Sent from my SCH-I500 using XDA App
jt1134 said:
They certainly can tell. Don't send back a phone because you broke it. That makes ALL of us look like assholes and promotes the disturbing trend of locking bootloaders. Be an adult.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
OH OK...Well let me make change my statemet to be more adult like. If i brick my phone I will just go buy another full price so I don't seem like an asshole. I hope this pleases you Sir....
Hey guys. First off, I'm psyched to see this come out.
When I try to do it, I get a driver installation failure telling me that the serial driver was not found and then ODIN never seems to see the phone. This is on W7.
Any help?
teddykgb715 said:
Hey guys. First off, I'm psyched to see this come out.
When I try to do it, I get a driver installation failure telling me that the serial driver was not found and then ODIN never seems to see the phone. This is on W7.
Any help?
Click to expand...
Click to collapse
Did you install the drivers that came with the phone?
wynalazca said:
Did you install the drivers that came with the phone?
Click to expand...
Click to collapse
I thought so, I can connect to USB storage, etc. I'll check it out.
Well this worked perfectly only thing that was different from your instructions was that my com ID was '0[COM12] instead of '0:[COM7]...So no one freak out if yours if different it's just what is being used by your comp. Much thanks to the OP for this..You need to set up a donation link so I can donate for this outstanding work.
teddykgb715 said:
I thought so, I can connect to USB storage, etc. I'll check it out.
Click to expand...
Click to collapse
I think the issue is that my damn work laptop is locked down pretty tight so it won't let all the drivers install. Unlike many here, I'm actually not an IT professional so I can't circumvent it. I'll just have to try it at home tonight.
das7771 said:
Well this worked perfectly only thing that was different from your instructions was that my com ID was '0[COM12] instead of '0:[COM7]...So no one freak out if yours if different it's just what is being used by your comp. Much thanks to the OP for this..You need to set up a donation link so I can donate for this outstanding work.
Click to expand...
Click to collapse
You're welcome! I'm very glad to help get this development stuff going. Also, there should be a donate button in the OP.
Related
i flashed SCH-I500_USCC_DI14_REL.tar.md5。When I use odin Installation cmw ,the phone stopped at the samsung splash screen does not work. How can I do?
qq25 said:
i flashed SCH-I500_USCC_DI14_REL.tar.md5。When I use odin Installation cmw ,the phone stopped at the samsung splash screen does not work. How can I do?
Click to expand...
Click to collapse
You also need to flash the pit file. If you follow the instructions in this thread, it will tell you exactly what to do. You don't use Odin to install CWM, btw.
Phidelt82 is correct.
Start with that thread. That will get you back to stock.
Then this thread. How to Mod My MEZ. That will get you started from Stock to get Rooted and install CWM and then its your choice of ROM and Theme if you choose.
please please please.. read. read and read everything twice. go slow and have patience.
And ask questions. I do not get a chance to post so much at the moment but always willing to help where I can if I can.
now my phone can not to work。I press step by step, and now my phone finish except call 911, any other phone cannot dial, what reason be?
Need to activate?How should do?
qq25 said:
Need to activate?How should do?
Click to expand...
Click to collapse
Just cool down. Your phone is booting. It works. I don't work for USCC so I'm not exactly sure how it works but I don't know if you would have to activate it again. I suggest you take the phone to the store and tell them it stopped working. They will probably get it all fixed up for you there. Since it's stock right now you shouldn't have any problems (=
PS: In the future, don't dial 911 to 'test' whether you phone works or not.. 0_o
dcow90 said:
Just cool down. Your phone is booting. It works. I don't work for USCC so I'm not exactly sure how it works but I don't know if you would have to activate it again. I suggest you take the phone to the store and tell them it stopped working. They will probably get it all fixed up for you there. Since it's stock right now you shouldn't have any problems (=
PS: In the future, don't dial 911 to 'test' whether you phone works or not.. 0_o
Click to expand...
Click to collapse
thanks ,i use this phone in china ^_^ 。
qq25 said:
thanks ,i use this phone in china ^_^ 。
Click to expand...
Click to collapse
Why would you be using a US Cellular phone in China?
phidelt82 said:
You also need to flash the pit file. If you follow the instructions in this thread, it will tell you exactly what to do. You don't use Odin to install CWM, btw.
Click to expand...
Click to collapse
Woah, what do you mean you don't use Odin to install CWM? The newb guide
http://forum.xda-developers.com/showthread.php?t=931169
says "
1.Shut phone off, pull battery out and leave it out.
2.Run odin (assuming you have it installed)
3.Load the cwm-recovery-all.tar file into the PDA spot"
And i've read like 15 other how tos that all say the same thing. That sounds like you install CWM with odin.
What this is:
A package to return your device to a completely stock state. It differs from h8rift's packages in that it includes a PIT file to repartition your phone. This is especially useful for those who accidentally flashed the wrong PIT (cough... bella) or screwed up their partitions some other way.
Is this dangerous?:
No. The PIT file I created has been tested and confirmed working by myself.
Instructions:
1) Make sure the drivers for the Infuse 4G are installed (installing Kies is the best way to accomplish this)
2) Download and unzip GTG's_Ultimate_Unbrick.zip
3) Run Odin3 v1.7.exe as administrator
4) Place your phone into download mode (pull battery, replace battery, press and hold both volume buttons while plugging in the USB cable)
5) Make sure your phone shows up in Odin as COM##
6) Click the PIT button and choose infuse.pit (and make sure Re-Partition is checked)
7) Click the PDA button and choose PDA_UCKD5.tar.md5
8) Click the PHONE button and choose PHONE_UCKD5.tar.md5
9) Press Start
10) In the rare case that it finishes and your phone proceeds to boot loop, pull the battery, replace it, press and hold both volume keys and then press and hold the power key, keep holding all three buttons until 3e recovery comes up, select "delete all user data", and finally select "reboot system now".
----Download----
GTG's_Ultimate_Unbrick.zip (183MB)
I do this for fun so you shouldn't feel any obligation to donate, but here's a link if you want to. Donations of any amount are very much appreciated.
This is the reason I like my infuse! You are awesome and so are the others I've been infused since day one and can't wait for more!people gtg is awesome
I'm a fan now
Sent from my SAMSUNG-SGH-I997 using XDA Premium App
And it's up! Go ahead peeps! Try to brick this sucker! HAHA, you CAN'T anymore! Muhahaha!
gtg465x said:
And it's up! Go ahead peeps! Try to brick this sucker! HAHA, you CAN'T anymore! Muhahaha!
Click to expand...
Click to collapse
Awesome work GTG, this is why I donated to you!
this is why you got my donation. you were helpful before you even got the phone, this is very good news.
Was the difference just Odin 1.7? I never understood why there are so many Odins .
h8rift said:
Was the difference just Odin 1.7? I never understood why there are so many Odins .
Click to expand...
Click to collapse
Difference between what? Don't think the Odin version makes a difference. Just decided to include 1.7 lol.
gtg465x said:
Difference between what? Don't think the Odin version makes a difference. Just decided to include 1.7 lol.
Click to expand...
Click to collapse
Did you dd the bml2 partition to get the .pit? I'm just curious where that .pit came from. Great work on this btw!
Thanks!
-h8
h8rift said:
Did you dd the bml2 partition to get the .pit? I'm just curious where that .pit came from. Great work on this btw!
Thanks!
-h8
Click to expand...
Click to collapse
Yeah, dded the bml2 partition and then had to remove dead space with a hex editor to get Odin to recognize it.
gtg465x said:
What this is:
A package to return your device to a completely stock state. It differs from h8rift's packages in that it includes a PIT file to repartition your phone. This is especially useful for those who accidentally flashed the wrong PIT (cough... bella) or screwed up their partitions some other way.
Is this dangerous?:
No. The PIT file I created has been tested and confirmed working by myself.
Instructions:
1) Make sure the drivers for the Infuse 4G are installed (installing Kies is the best way to accomplish this)
2) Download and unzip GTG's_Ultimate_Unbrick.zip
3) Run Odin3 v1.7.exe as administrator
4) Place your phone into download mode (pull battery, replace battery, press and hold both volume buttons while plugging in the USB cable)
5) Make sure your phone shows up in Odin as COM##
6) Click the PIT button and choose infuse.pit (and make sure Re-Partition is checked)
7) Click the PDA button and choose PDA_UCKD5.tar.md5
8) Click the PHONE button and choose PHONE_UCKD5.tar.md5
9) Press Start
----Download----
GTG's_Ultimate_Unbrick.zip (183MB)
I do this for fun so you shouldn't feel any obligation to donate, but here's a link if you want to. Donations of any amount are very much appreciated.
Click to expand...
Click to collapse
So would this have solved all of my problems? LOL
At least now my phone will be back next week with the official Samsung touch, ready for eBay... hehe :-(
bella92108 said:
So would this have solved all of my problems? LOL
At least now my phone will be back next week with the official Samsung touch, ready for eBay... hehe :-(
Click to expand...
Click to collapse
Yes, you didn't give me enough time though.
gtg465x said:
(cough... bella)
Click to expand...
Click to collapse
Ohh hehe, that's meeeeee!
What's this button do that says "Do you want to reformat and partition c:\? - Confirm? Yes\No" ...
I guess I'll just click YES, it sounds nice... hehe.
Ugh... I can almost fit my entire foot in my mouth at this point
gtg465x said:
Yes, you didn't give me enough time though.
Click to expand...
Click to collapse
HEHE, I'm impatient. Well that and it's my $440 on the line and I got Sammy to agree to let me RMA it and send me a new one, so when an option like that is presented I had to jump on it. At least now I can blindly fu#$ up my new phone without fear of consequence. hehe. It's like the 60's for my Infuse!
bella92108 said:
HEHE, I'm impatient. Well that and it's my $440 on the line and I got Sammy to agree to let me RMA it and send me a new one, so when an option like that is presented I had to jump on it. At least now I can blindly fu#$ up my new phone without fear of consequence. hehe. It's like the 60's for my Infuse!
Click to expand...
Click to collapse
woa woa woa, dont get ahead of your self. there is still atleast one wayto f- up the phone beyond the ability to recover. messing with bootloaders! dont do that! lost1 posted some in his extra files but im not willing to test them, are you? please if you do post results but im not recomending it and if they dont work odin doesnt work either! so dont try bootloaders for other phone or anything!
Dani897 said:
woa woa woa, dont get ahead of your self. there is still atleast one wayto f- up the phone beyond the ability to recover. messing with bootloaders! dont do that! lost1 posted some in his extra files but im not willing to test them, are you? please if you do post results but im not recomending it
Click to expand...
Click to collapse
HAHA if you would have asked me before I sent the phone back to Samsung I would have tested for ya. Of course if you said to fix my phone by submerging it in vegetable oil for 15 minutes might recover it I just might have as far gone as that thing was, hehe.
bella92108 said:
HAHA if you would have asked me before I sent the phone back to Samsung I would have tested for ya. Of course if you said to fix my phone by submerging it in vegetable oil for 15 minutes might recover it I just might have as far gone as that thing was, hehe.
Click to expand...
Click to collapse
that might not be as harmfull as you think. i have seen vegtable oil used to submerge an entire mother board into for cheap liquid cooling(not a permanant way to do it, it is damaging but will run for a while). demineralized/deionized water works as well (water is an excelent insulator of electricity with the highest dielectric strength that i know of if it has no contaminants in it, tap water is full of minerals that act as electrolytes)
but yeah if you flashed the bootloaders and the phone still went into download mode that would be considered a suscessful bootloader flash
He might be updating, but I to can confirm link is down.......
My bad. Back up.
As always GTG , you are the ****in man.
Not sure if this is the proper section for this but thought I would post this here as I'm sure it would highly assist people in development and other tasks. This is the button combinations you need to enter each mode.
ODIN/Download Mode
Make sure your device is completely off
Key Combos: Volume Down + Home
While holding both of them simultaneously press the Power button until you see a disclaimer on the screen
Then let go of all the buttons and press Volume Up to accept the disclaimer
Once the green robot is visible on the screen this indicates that handset is in now ODIN/Download mode
Recovery Mode
Make sure your device is completely off
Key Combos: Volume Up + Home
While holding both of them simultaneously press the Power button
As soon as the phone vibrates, let go of the Power button but keep holding Volume Up + Home
When you see the "Samsung Galaxy S III" logo (not just the word "Samsung"), right after that, the next screen you should see is your recovery
Don't let go of Volume Up + Home until you see your recovery
Updated OP to correct that Samsung devices do not have a "Fastboot" mode. ODIN mode replaces this and the ODIN software is basically a set of fastboot commands which is the only way to communicate to the device on a low level. Just a little FYI for everyone.
Heimdall should also work ,and it's cross-platform, unlike Odin. But somebody with a phone should test it to make sure it does.
http://forum.xda-developers.com/showthread.php?t=755265
Thanks for this handy information.
Since I am not at all familiar with Odin and how it works, could you ad a description of the steps to take in order to use Odin to flash an image file to the Galaxy S III? I watched a video on rooting, but the author never really showed much of the Odin screen on his PC and didn't say anything at all about how to use it. So far I keep reading to "use the PDA button", and I have the files downloaded and ready to go, but I don't want to make any mistakes.
Zoandroid said:
Thanks for this handy information.
Since I am not at all familiar with Odin and how it works, could you ad a description of the steps to take in order to use Odin to flash an image file to the Galaxy S III? I watched a video on rooting, but the author never really showed much of the Odin screen on his PC and didn't say anything at all about how to use it. So far I keep reading to "use the PDA button", and I have the files downloaded and ready to go, but I don't want to make any mistakes.
Click to expand...
Click to collapse
Check out the video linked in this thread: http://forum.xda-developers.com/showthread.php?t=1759980&highlight=heimdall
Happy rooting
Thanks. I guess it's really pretty simple after all.
I've seen some posts where folks had Odin still chewing on the process after 45 minutes. What do you recommend one do in that instance?
Zoandroid said:
Thanks. I guess it's really pretty simple after all.
I've seen some posts where folks had Odin still chewing on the process after 45 minutes. What do you recommend one do in that instance?
Click to expand...
Click to collapse
In 99% of cases such as that it is likely the fault of a bad USB cable or the computer itself. First try another cable, if still the same try to get access to something like a laptop and try there, usually USB ports work fine on laptops.
satadru said:
Heimdall should also work ,and it's cross-platform, unlike Odin. But somebody with a phone should test it to make sure it does.
http://forum.xda-developers.com/showthread.php?t=755265
Click to expand...
Click to collapse
You would think so but I haven't seen anyone have any luck with Heimdall on Verizon. If someone out there has gotten it to work, would appreciate some sort of guide.
open1your1eyes0 said:
In 99% of cases such as that it is likely the fault of a bad USB cable or the computer itself. First try another cable, if still the same try to get access to something like a laptop and try there, usually USB ports work fine on laptops.
Click to expand...
Click to collapse
Thanks. Luckily, I did not have this issue, and your thread here allowed me to root easily on the first try (I did use the OEM USB cable, having read that sometimes prevented problems for others). So thanks a lot for this thread. I am one of a presumed many who came here as this thread was spawned from a divergence on a previous root thread. Glad I did.
I did have an issue with Rom Manager while trying to flash CWM Recovery. It hung on the first attempt and I had to reboot the phone, but then it worked the second time. The only remaining anomaly I have here is that the nandroid I made is dated 1970. I'd like to know if others are having the same issue, and await some announcement for a fix. Does CWM Recovery actually have a support site? If so I'll post there about it.
Zoandroid said:
Thanks. Luckily, I did not have this issue, and your thread here allowed me to root easily on the first try (I did use the OEM USB cable, having read that sometimes prevented problems for others). So thanks a lot for this thread. I am one of a presumed many who came here as this thread was spawned from a divergence on a previous root thread. Glad I did.
I did have an issue with Rom Manager while trying to flash CWM Recovery. It hung on the first attempt and I had to reboot the phone, but then it worked the second time. The only remaining anomaly I have here is that the nandroid I made is dated 1970. I'd like to know if others are having the same issue, and await some announcement for a fix. Does CWM Recovery actually have a support site? If so I'll post there about it.
Click to expand...
Click to collapse
Happy to help.
And the date bug is a known problem with both CWM and TWRP recovery so far so don't worry too much for now and it won't affect it's use, just an annoyance. No ETA on a fix just yet but check in ROM Manager for an updated version possibly.
open1your1eyes0 said:
Happy to help.
And the date bug is a known problem with both CWM and TWRP recovery so far so don't worry too much for now and it won't affect it's use, just an annoyance. No ETA on a fix just yet but check in ROM Manager for an updated version possibly.
Click to expand...
Click to collapse
What I would actually like to see is CWM offering to let us name the nandroid when creating it, as well as where to put it. From what I have read this date issue is long standing, yet I have never encountered it before using rooted Android devices for the past 2 years until just now. I wonder if it is just this phone model causing the issue?
Does the battery need to be pulled for Odin to be accessed?
How about updating the OP to mention that you must be powered off before pressing the key combinations to enter ODIN mode. Would have saved me a lot of time.
rigman said:
How about updating the OP to mention that you must be powered off before pressing the key combinations to enter ODIN mode. Would have saved me a lot of time.
Click to expand...
Click to collapse
Section 6 of my guide stickied at the top if page:
Step 3: Power device off, then hold the volume down/home/power keys until you see a yellow triangle, then press the volume up key to access "download mode"
delete
Added more details to OP to avoid confusion
Sadly, the date issue in CWM Touch Recovery has still not been corrected. I rename them after I make one ( but make sure not to put any spaces in the file name or it won't pass the MD5 check when using it later).
Zoandroid said:
Sadly, the date issue in CWM Touch Recovery has still not been corrected. I rename them after I make one ( but make sure not to put any spaces in the file name or it won't pass the MD5 check when using it later).
Click to expand...
Click to collapse
Appreciate the bump but please stay on topic of OP. If not related, please post in corresponding appropriate thread.
Zoandroid said:
What I would actually like to see is CWM offering to let us name the nandroid when creating it, as well as where to put it. From what I have read this date issue is long standing, yet I have never encountered it before using rooted Android devices for the past 2 years until just now. I wonder if it is just this phone model causing the issue?
Click to expand...
Click to collapse
The paid version of ROM Manager allows just that, to name and choose the storage location of your Nandroid backups.
Zoandroid said:
Sadly, the date issue in CWM Touch Recovery has still not been corrected. I rename them after I make one ( but make sure not to put any spaces in the file name or it won't pass the MD5 check when using it later).
Click to expand...
Click to collapse
I was curious as to why backups I'd named were failing seemingly at random. Thanks for the heads up. I wonder if this applies to renaming a backup and is therefore correctable by doing so with no spaces in the new name?
Sent from my SCH-I535 using xda premium
open1your1eyes0 said:
Appreciate the bump but please stay on topic of OP. If not related, please post in corresponding appropriate thread.
Click to expand...
Click to collapse
I was replying to a statement made in post #10 by the OP in his own thread. My apologies if it was deemed inappropriate.
I'm a noob but I'd been trying my best understanding to ROOT T959W, I'd followed the steps as described in one of the forums here using odin 1.7 and stock+Voodoo-T959VKJ1.tar and the update in sdcard but unfortunately I don't understand, no matter what i do, when the phone turns on it shows the Recovery mode, I'm however able to boot into the downlod mode and my phone is detectable.
The phone was I guess bricked onetime but i'd used oneclick unbrick and it went back fine.
Please help me to at least get it to a running state not necessarily root.
I don't know if this is right, what should i do next ? Flash the rom CM9 ? or have i messed up ? :S
THANKS A TON!
Attached is a preview.
It seems a little odd. Did you clear everything and not flash a rom?
Sent from my SGH-T999 using xda premium
So you have the "W" phone from Wind and you flashed the bootloader? I can clearly see the Tmobile logo, which shouldn't be on a Wind phone. Just hold on, don't flash anything else and give a few, I'm working with bhundven at this very moment to try and dump my bootloader. Your phone still turns on, there is hope but the more you start clicking all over, etc the more damage you can do, so please wait.
getochkn said:
So you have the "W" phone from Wind and you flashed the bootloader? I can clearly see the Tmobile logo, which shouldn't be on a Wind phone. Just hold on, don't flash anything else and give a few, I'm working with bhundven at this very moment to try and dump my bootloader. Your phone still turns on, there is hope but the more you start clicking all over, etc the more damage you can do, so please wait.
Click to expand...
Click to collapse
Sure, I will be waiting, Yes it shows the Tmobile logo and when I connect it to Odinv1.85 it tells me this phone is T959V but infact its a wind mobile.
I'll be waiting for you guys and will be more than willing to donate.
cheers!
zaryan said:
Sure, I will be waiting, Yes it shows the Tmobile logo and when I connect it to Odinv1.85 it tells me this phone is T959V but infact its a wind mobile.
I'll be waiting for you guys and will be more than willing to donate.
cheers!
Click to expand...
Click to collapse
The T959V in odin is just a label in the ini file in the same directory.
You can change that to say anything you want.
I really recommend taking the time now to remove odin, and it's drivers, and install heimdall.
Look around in the wiki for help on that one.
bhundven said:
The T959V in odin is just a label in the ini file in the same directory.
You can change that to say anything you want.
I really recommend taking the time now to remove odin, and it's drivers, and install heimdall.
Look around in the wiki for help on that one.
Click to expand...
Click to collapse
After i replaced the drivers, and ran flash in heimdall, it gives me an error - I ran T959VUVKJ6_STOCK-UVKJ6-One-Click.jar
"Local and device PIT files don't match and repartition wasn't specified
Ending session...
Rebooting device "
zaryan said:
After i replaced the drivers, and ran flash in heimdall, it gives me an error - I ran T959VUVKJ6_STOCK-UVKJ6-One-Click.jar
"Local and device PIT files don't match and repartition wasn't specified
Ending session...
Rebooting device "
Click to expand...
Click to collapse
I didn't say to run it, yet. I'm making a new oneclick for t959w. Hang tight.
bhundven said:
I didn't say to run it, yet. I'm making a new oneclick for t959w. Hang tight.
Click to expand...
Click to collapse
Sure will be waiting
zaryan said:
Sure will be waiting
Click to expand...
Click to collapse
Me and Brian are working on it. He had to go out for a bit, so waiting for him to get back on IRC and I'm testing it and risking bricking my phone for the good of the 959W users, so please be patient until we have a test package that can restore the bootloaders, param's, everything full for a "W" model. I found a very complicated work around to get out of the loop but I rather wait till we have the 1 click tested and it's easier to use and do.
For now, the standard 1 click should get you back to stock, just don't flash the bootloader at all.
getochkn said:
Me and Brian are working on it. He had to go out for a bit, so waiting for him to get back on IRC and I'm testing it and risking bricking my phone for the good of the 959W users, so please be patient until we have a test package that can restore the bootloaders, param's, everything full for a "W" model. I found a very complicated work around to get out of the loop but I rather wait till we have the 1 click tested and it's easier to use and do.
For now, the standard 1 click should get you back to stock, just don't flash the bootloader at all.
Click to expand...
Click to collapse
You are awesome! It worked like charm, thank you getochkn and xda-dev
zaryan said:
You are awesome! It worked like charm, thank you getochkn and xda-dev
Click to expand...
Click to collapse
Glad I was able to help but I couldn't have done any of this with the guidance of bhundven and others from Team Acid. Hopefully I'll have the true stock modem our phone came with soon, full stock recovery, etc and be able to put out a full package to help people who are bricked or want to go back to stock.
getochkn said:
Me and Brian are working on it. He had to go out for a bit, so waiting for him to get back on IRC and I'm testing it and risking bricking my phone for the good of the 959W users, so please be patient until we have a test package that can restore the bootloaders, param's, everything full for a "W" model. I found a very complicated work around to get out of the loop but I rather wait till we have the 1 click tested and it's easier to use and do.
For now, the standard 1 click should get you back to stock, just don't flash the bootloader at all.
Click to expand...
Click to collapse
any luck with the 1 click for the T959W yet? I am more than willing to donate also, my phone is stuck in download mode only so I desperately need this!!!!
munsen55 said:
any luck with the 1 click for the T959W yet? I am more than willing to donate also, my phone is stuck in download mode only so I desperately need this!!!!
Click to expand...
Click to collapse
Give me a few mins, let me see what I can do.
getochkn said:
Give me a few mins, let me see what I can do.
Click to expand...
Click to collapse
Please bro i have the same problem
please can you help me with the t959w bootloader or 1click solution
MY BAD, PLEASE MOVE THIS TO THE CORRECT SECTION. I'M REALLY SORRY.
Hello!, my mother bought this phone for her in the US and from day 0 it has been having problems. She couldn't use wifi or bluetooth for example, and sometimes it just kept restarting till it worked again, but without any connectivity functions, except mobile data.
I tried to fix this updating the phone using Samsung Smart Switch to the last build (AQL1) but now the phone is stuck on the boot screen no matter what I do.
Tried flashing with Odin, it worked, but the phone is still on boot loop. I read somewhere in this forum that you can install an older version of the bootloader to take the phone out of this hell and I did it, using the build AQK2 bootloader but no luck, same problem.
Also, the phone doesn't have USB debugging enable nor OEM unlock either. I can access both recovery and download mode though.
At this point I'm out of ideas, can someone help me with this one?
Thanks in advanced.
fefin
fefin said:
MY BAD, PLEASE MOVE THIS TO THE CORRECT SECTION. I'M REALLY SORRY.
Hello!, my mother bought this phone for her in the US and from day 0 it has been having problems. She couldn't use wifi or bluetooth for example, and sometimes it just kept restarting till it worked again, but without any connectivity functions, except mobile data.
I tried to fix this updating the phone using Samsung Smart Switch to the last build (AQL1) but now the phone is stuck on the boot screen no matter what I do.
Tried flashing with Odin, it worked, but the phone is still on boot loop. I read somewhere in this forum that you can install an older version of the bootloader to take the phone out of this hell and I did it, using the build AQK2 bootloader but no luck, same problem.
Also, the phone doesn't have USB debugging enable nor OEM unlock either. I can access both recovery and download mode though.
At this point I'm out of ideas, can someone help me with this one?
Thanks in advanced.
fefin
Click to expand...
Click to collapse
Have you reached out to Samsung yet?
Mr. Orange 645 said:
Have you reached out to Samsung yet?
Click to expand...
Click to collapse
Thanks for answering. Where I live there is not a single Samsung Service, only at like 1800km from here, that's why I'm trying to solve this by myself but seems that this is a hard one... I hope someone can help me to deal with this as it was a big investment :/
Thanks again!, if someone knows a way to help please tell me.
fefin
fefin said:
Thanks for answering. Where I live there is not a single Samsung Service, only at like 1800km from here, that's why I'm trying to solve this by myself but seems that this is a hard one... I hope someone can help me to deal with this as it was a big investment :/
Thanks again!, if someone knows a way to help please tell me.
fefin
Click to expand...
Click to collapse
I mean have you called or emailed Samsung?
Mr. Orange 645 said:
I mean have you called or emailed Samsung?
Click to expand...
Click to collapse
No I haven't, I will give a try soon through web chat.
I mean, this shouldn't be happening, it's a brand new phone, all over the internet are people with the same problems as me and looks like so far there is no solution.
Maybe it's a faulty phone/hardware? My knowledge is not enough in this matter.
See you!,
Federico.
I need a couple things from you
1. What model does it say on the back of the phone i understand you posted it in the header but please for safety sake .
2. Go into download mode for me so i can see what carrier it lists
3. Try wiping data cache in recovery
Sent from my SM-G955U1 using XDA-Developers Legacy app
allenjthomsen said:
I need a couple things from you
1. What model does it say on the back of the phone i understand you posted it in the header but please for safety sake .
2. Go into download mode for me so i can see what carrier it lists
3. Try wiping data cache in recovery
Sent from my SM-G955U1 using XDA-Developers Legacy app
Click to expand...
Click to collapse
Thanks for answering!, here it goes:
1. It says SM-G955U1
2. Carrier: XAA
3. Done, still the same.
An update from my last post:
After a few bootloops the FRP screen showed up, as the phone can't use wifi yet I managed to access using mobile data and enabled the USB debugging, but after trying to enable wifi the phone froze and went on bootloop again, so still the same but with the USB debugging enabled. I'm currently on the build AQK2.
Thanks again, and I hope we can fix this.
Update 2:
I cleared the cache, after a few bootloops the phone actually boots (gets to the lock screen), and it restarts again while the message "Android is starting" is loading, so now it's a different type of bootloop I guess. It does the same even in safe mode.
I will turn it off for now.
fefin said:
Thanks for answering!, here it goes:
1. It says SM-G955U1
2. Carrier: XAA
3. Done, still the same.
An update from my last post:
After a few bootloops the FRP screen showed up, as the phone can't use wifi yet I managed to access using mobile data and enabled the USB debugging, but after trying to enable wifi the phone froze and went on bootloop again, so still the same but with the USB debugging enabled. I'm currently on the build AQK2.
Thanks again, and I hope we can fix this.
Update 2:
I cleared the cache, after a few bootloops the phone actually boots (gets to the lock screen), and it restarts again while the message "Android is starting" is loading, so now it's a different type of bootloop I guess. It does the same even in safe mode.
I will turn it off for now.
Click to expand...
Click to collapse
Ok i want you to do a couple things for me
1.Download this file http://updato.com/firmware-archive-select-model?record=F837B5F2EC0611E7A5F9FA163EE8F90B this is the latest update for the G955U1
2. extract the zip file using 7zip so you have 5 .tar.md5 files
3. go to the CSC_OYM_G955U1OYM2AQL1_CL12513005_QB15986651_REV00_user_low_ship_MULTI_CERT.tar.md5 and right click on the file and goto 7-zip and then click open archive
4. you will see a file called DREAM2QLTE_USA_SINGLE.pit i want you to extract it to the folder you have Odin in if not quick search forums for it
5. Open odin and go to the the pit tab it will do a pop up just click ok and ignore
6. click the pit button and find the pit file that you extracted and select it
7. now go to options tab
8.check to make sure you have auto reboot, re-partition, and f reset timer checked
9.Load BL,AP,CP,CSC in respective slots on right side
10. click start and let the phone flash, as soon as it is done hold volume up bixby and power button wait for recovery to load and wipe data and factory reset.
11. reboot and let it boot if you are still in a bootloop after these steps pm me and i will help you the last way i know how to fix these phones.
allenjthomsen said:
Ok i want you to do a couple things for me
1.Download this file http://updato.com/firmware-archive-select-model?record=F837B5F2EC0611E7A5F9FA163EE8F90B this is the latest update for the G955U1
2. extract the zip file using 7zip so you have 5 .tar.md5 files
3. go to the CSC_OYM_G955U1OYM2AQL1_CL12513005_QB15986651_REV00_user_low_ship_MULTI_CERT.tar.md5 and right click on the file and goto 7-zip and then click open archive
4. you will see a file called DREAM2QLTE_USA_SINGLE.pit i want you to extract it to the folder you have Odin in if not quick search forums for it
5. Open odin and go to the the pit tab it will do a pop up just click ok and ignore
6. click the pit button and find the pit file that you extracted and select it
7. now go to options tab
8.check to make sure you have auto reboot, re-partition, and f reset timer checked
9.Load BL,AP,CP,CSC in respective slots on right side
10. click start and let the phone flash, as soon as it is done hold volume up bixby and power button wait for recovery to load and wipe data and factory reset.
11. reboot and let it boot if you are still in a bootloop after these steps pm me and i will help you the last way i know how to fix these phones.
Click to expand...
Click to collapse
Sadly it didn't work. The phone is still loading till "android is starting" sign and then restarting again.
I will write you so you can help me through pm, could this be a faulty hardware?
I'd like to know the other solution too.
I will tell you all what todo as a last resort.
IF YOU CHOOSE TO DO THIS I TAKE NO RESPONSIBILITY IF YOUR DEVICE STOPS WORKING OR DOES NOT TURN ON!!!
Follow all previously said steps i outlined but when you go into the options tab select nand erase all also then flash device.
Sent from my SM-G955U1 using XDA-Developers Legacy app
try installing PartCyborgRom
@fefin -Sorry to hear that you're having issues - But I'd like to clear one thing up - Your comment that this is an issue "all over the internet" sim isn't true... I don't know how many Millions of S8 / S8+ have been sold - But your post is the first that I've ever heard of anything like this... I concur with the recommendation that you call or Chat with Samsung Technical Support - Preferably before you find the phone completely unable to Boot into Download Mode - Get Samsung to help you - or you may risk voiding the warranty if Samsung determines that you are ultimately responsible for the state of the phone ??
Sent from my SM-G955W ??
allenjthomsen said:
I will tell you all what todo as a last resort.
IF YOU CHOOSE TO DO THIS I TAKE NO RESPONSIBILITY IF YOUR DEVICE STOPS WORKING OR DOES NOT TURN ON!!!
Follow all previously said steps i outlined but when you go into the options tab select nand erase all also then flash device.
Sent from my SM-G955U1 using XDA-Developers Legacy app
Click to expand...
Click to collapse
Thanks for your help! Much appreciated.
DR25 said:
try installing PartCyborgRom
Click to expand...
Click to collapse
Thanks for your suggestion, I will look into it.
shaggyskunk said:
@fefin -Sorry to hear that you're having issues - But I'd like to clear one thing up - Your comment that this is an issue "all over the internet" sim isn't true... I don't know how many Millions of S8 / S8+ have been sold - But your post is the first that I've ever heard of anything like this... I concur with the recommendation that you call or Chat with Samsung Technical Support - Preferably before you find the phone completely unable to Boot into Download Mode - Get Samsung to help you - or you may risk voiding the warranty if Samsung determines that you are ultimately responsible for the state of the phone
Sent from my SM-G955W
Click to expand...
Click to collapse
Thanks for answering!, sorry for my late response.
Well, if you check samsung's official forum there are a few threads with 15+ pages of people complaining about wifi issues (https://us.community.samsung.com/t5/forums/v3_1/forumtopicpage/board-id/GS8QA/thread-id/862/page/1 and https://us.community.samsung.com/t5/forums/v3_1/forumtopicpage/board-id/GS8QA/thread-id/30601/page/1) about bootloop problems, (https://us.community.samsung.com/t5...id/GS8QA/thread-id/3920/highlight/true/page/1) also there is a post on another webpage talking about bootloops on this model and how to fix them (https://thedroidguy.com/2017/12/sol...p-issue-s8-turns-screen-remains-black-1079013).
I know it's not representative, as you said, millions of phones has been sold, but what I meant when I said "all over the internet" is that you can easily find people with this same problem. This shouldn't be happening, not on any phone even less on such an expensive phone.
I think the phone is officially dead, I took it to a well known local technician and even him couldn't fix it. My nearest official samsung service is 1600km away. On the other hand, my aunty got for herself an S8 and it's working perfect, so it's just bad luck for my mom I guess.
The phone had issues since she bought it (wifi and bluetooth didn't worked at all, but she is not really a tech person so she thought it was fine), the phone was working with some bootloops from time to time and after a while it fell from and got a little crack on the top but it didn't change the behavior of the phone, it was still ****ed up. That's the thing, because of the crack I'm pretty sure they won't take it back or even try to fix it (for free at least), they will say the problem is because of the fall. I'd been reading a lot about this and seems that I'm pretty screwed D:
I will sell the phone for parts. At least I will recover 60% of the initial investment.
fefin said:
That's the thing, because of the crack I'm pretty sure they won't take it back or even try to fix it (for free at least), they will say the problem is because of the fall. I'd been reading a lot about this and seems that I'm pretty screwed D:
I will sell the phone for parts. At least I will recover 60% of the initial investment.
Click to expand...
Click to collapse
If you have some 'proof' the problem existed, before the crack, and can prove when the crack occurred, or reasonable determinate approximation, small claims court will vindicate you, and Samsung will have to pay.
Sad to say would take a little time of yours to get them there, but it is an easy process, and with reasonable ability to determine/evidence those two things, a sure win.
But still a PITA.