Related
My wife and I both have Thunderbolts. I have not had this problem with mine so I am curious as to if anyone else has had a problem or if maybe she just has a bad tbolt. When she is on a call just out of nowhere the person on the other end can not hear her. This has happened when she has talked to multiple people and she has had good reception when it happens. This happened stock and on BAMF so I dont think it is a ROM problem. Anyone else having a similar thing happen, or do you think she has a bad tbolt?
I have not heard of this being a widespread issue, and I keep up with a lot of the Android forums. Sounds like a dud phone to me.
That's what I was thinking as well. Looks like its back to stock then Verizon for that bolt
I've had this problem from day 1. A bunch of different techs from VZW have looked into it and changed stuff on the backend and still no luck. :-(
Sent from my Thunderbolt using XDA Premium
davidbudd1, PLEASE let me/us know if swapping out the TB and/or the SIM fixed the issue for you! Here is a thread on Android Central that we've been trying to do some testing about this issue:
http://forum.androidcentral.com/htc-thunderbolt/71734-can-you-hear-me-now.html
I'll keep you posted on what they tryband if it fixes it. I don't have a problem with this on mine, only my wife's phone. My buddy has a tbolt also and his doesn't have this problem. So to me it sounds like a bad phone.
Thank you SO much, I really appreciate it!
Sent from my Thunderbolt using XDA Premium
Hey man, any updates on this? I just went to VZW to get my phone swapped out and of course they said NO again because they couldn't reproduce the issue with 2 quick test calls.
Sent from my Thunderbolt using XDA Premium
Well I took her phone back to stock, and now she has been using since and it hasn't happened.again since. So I'm wondering if something didn't quite flash right.
PorscheGuy said:
I've had this problem from day 1. A bunch of different techs from VZW have looked into it and changed stuff on the backend and still no luck. :-(
Sent from my Thunderbolt using XDA Premium
Click to expand...
Click to collapse
And the VZW guys are better at this than XDA members?
davidbudd1 said:
Well I took her phone back to stock, and now she has been using since and it hasn't happened.again since. So I'm wondering if something didn't quite flash right.
Click to expand...
Click to collapse
I had that happen with mine the first time I tried to root it. ADB crashed on me in the middle of the process. I rebooted and started again and it appeared to finish, but I was experiencing that issue. I rolled everything back to stock and reran the root from scratch, I've had no problems since.
I have this problem as well. Althought it doesn't happpen often.
Sent from my ADR6400L using XDA Premium App
I was going to reroot it on my day off and see what happens
jab818 said:
And the VZW guys are better at this than XDA members?
Click to expand...
Click to collapse
OMG of course not!!! But unfortunately us XDA members don't have access to VZW's back-end systems. :sad: Haha, you think that could be our next project?! :smile:
Sent from my Thunderbolt using XDA Premium
jab818 said:
I had that happen with mine the first time I tried to root it. ADB crashed on me in the middle of the process. I rebooted and started again and it appeared to finish, but I was experiencing that issue. I rolled everything back to stock and reran the root from scratch, I've had no problems since.
Click to expand...
Click to collapse
Hmmm, I wonder if I should try that? I have the stock RUU sitting on the root of my SD card (with a bak extension of course) in case the store could swap my phone tonight.
Sent from my Thunderbolt using XDA Premium
davidbudd1 said:
I was going to reroot it on my day off and see what happens
Click to expand...
Click to collapse
Oh, I thought you said that it happened on stock also?
Sent from my Thunderbolt using XDA Premium
i have the same problem on my tbolt, people say they can hardly hear me
jab818 said:
I had that happen with mine the first time I tried to root it. ADB crashed on me in the middle of the process. I rebooted and started again and it appeared to finish, but I was experiencing that issue. I rolled everything back to stock and reran the root from scratch, I've had no problems since.
Click to expand...
Click to collapse
OK, I remember having an issue when I originally rooted also, so I used the shipped RUU to go back to out-of-the-box stock and then reran the root process, etc, and then restored my nandroid backup. I'll make some test calls this afternoon and then report back!
so if i download the the ruu it came with and flash it will it unroot an turn it back to stock?
snowbdr89 said:
so if i download the the ruu it came with and flash it will it unroot an turn it back to stock?
Click to expand...
Click to collapse
Yes. Here is the link to the thread and download: http://forum.xda-developers.com/showthread.php?t=975888
Do I flash it via hboot an do I have to rename the zip?
I flashed back to stock this morning to test something and noticed there was a 19Mb update. After updating I rebooted the phone and checked a few more times to make sure there were no more updates. When I went into 'Download' to flash a new rom this is the screen I was presented with. After I chose to enter to Download mode that was the 2nd screen I had. Just thought it was funny and would share.
+1
Wulfegang is the man. Everyone give him a kiss to remove the butterflies from his stomach!
:*
Wulfegang said:
I flashed back to stock this morning to test something and noticed there was a 19Mb update. After updating I rebooted the phone and checked a few more times to make sure there were no more updates. When I went into 'Download' to flash a new rom this is the screen I was presented with. After I chose to enter to Download mode that was the 2nd screen I had. Just thought it was funny and would share.
Click to expand...
Click to collapse
Was that the whole point of the update lol?
Sent from my SAMSUNG-SGH-I997R using xda premium
theROMinator said:
Was that the whole point of the update lol?
Sent from my SAMSUNG-SGH-I997R using xda premium
Click to expand...
Click to collapse
Looks like it loads new bootloaders on our phone.... Making it easier to go from this update to GB soon I would think...
Sent from my Samsung Infuse 4G - 1.6ghz
SSJ_Gomike said:
Looks like it loads new bootloaders on our phone.... Making it easier to go from this update to GB soon I would think...
Sent from my Samsung Infuse 4G - 1.6ghz
Click to expand...
Click to collapse
We could only imagine...
Sent from my SAMSUNG-SGH-I997R using xda premium
theROMinator said:
We could only imagine...
Sent from my SAMSUNG-SGH-I997R using xda premium
Click to expand...
Click to collapse
Samsung is warning us of the power of the devs!
Successful XDA devs are successful... xP
Could someone please upload this bootloader zip ? I would like to try them with this GB leak to see if it gets rid of rainbows.
Sent from my SAMSUNG-SGH-I997 using XDA App
Removing the download for the bootloaders so people won't try flashing them and brick devices left and right. They were only intended for serious devs who know what they are doing. Sorry.
Could you also upload the whole update package? Thanks for the bootloaders.
Sent from my SAMSUNG-SGH-I997 using XDA App
Considering that we haven't ever been able to flash dumped BLs from the Rogers ROM, having the update package to look at would be highly beneficial to figure out how to flash the bootloaders.
This is a similar download mode screen to the SGSII - keeping count of how many custom ROMS you run/flash. Keeping in mind if you phone needs to go some where to be serviced there maybe a document of how they can check this counter. A USB JIG cleared this on the SGSII & my jig works fine on my Infuse so I can imagine it will still clear it.
Infiniti350GT said:
This is a similar download mode screen to the SGSII - keeping count of how many custom ROMS you run/flash. Keeping in mind if you phone needs to go some where to be serviced there maybe a document of how they can check this counter. A USB JIG cleared this on the SGSII & my jig works fine on my Infuse so I can imagine it will still clear it.
Click to expand...
Click to collapse
If that's the reason, then that's a REALLY smart way to track if you flash a custom "OS", as Samsung would say.
If it's as simple as using a USB JIG to clear it, then we should be in the clear.
Well i guess this finally gives me a reason to pick one up......
Entropy512 said:
Considering that we haven't ever been able to flash dumped BLs from the Rogers ROM, having the update package to look at would be highly beneficial to figure out how to flash the bootloaders.
Click to expand...
Click to collapse
It may be a bit before i could actually get a dump of the update package (considering i have n idea how to even begin to do that). i just had hernia surgery this morning and not really feeling up to doing much in the way of dev work lol. i will let everyone know when i am feeling better and maybe someone could walk me through it on IRC.
+1 got the upload prompt and uploaded something
Boot loaders flashed fine, now have the new download screen with warning. Still had rainbows and cannot access recovery when used with leaked GB. Otherwise no issues.
Sent from my SAMSUNG-SGH-I997 using XDA App
Wulfegang said:
It may be a bit before i could actually get a dump of the update package (considering i have n idea how to even begin to do that). i just had hernia surgery this morning and not really feeling up to doing much in the way of dev work lol. i will let everyone know when i am feeling better and maybe someone could walk me through it on IRC.
Click to expand...
Click to collapse
No problem - honestly someone like gtg might be better as far as finding that update, I'm not sure where to look myself!
cruiserbax said:
Boot loaders flashed fine, now have the new download screen with warning. Still had rainbows and cannot access recovery when used with leaked GB. Otherwise no issues.
Sent from my SAMSUNG-SGH-I997 using XDA App
Click to expand...
Click to collapse
I was curious about this, thanks for the info!
Also in case anyone wants to know, after flashing the leaked GB with this BL the download screen still reports official Samsung Binary as the current.
This is just a short term observation: when I flashed the leaked GB with the old BL I got hard reboots when apps accessed GPS (speed test, maps, co pilot) 1 out of 10 times. With these BL's I am at 18 hours using all of those apps without any reboots. Though it could have just been reflashing that fixed it. I did not use TB or anything to restore app data usher time, both times I went back to stock first.
Sent from my SAMSUNG-SGH-I997 using XDA App
I just downloaded the BLs. Do I convert file (with both BLs) to .tar to odin flash?
Sent from my SAMSUNG-SGH-I997 using XDA Premium App
Not having issue other than rainbows ... May keep current BLs
Sent from my SAMSUNG-SGH-I997 using XDA Premium App
So just being bored, i decided to flash a t-mobile rom, via clockwork rom manager, now the skyrocket wont even power on. So thanks Rom Manager for the bricked phone, Bad Buisness....
First sorry to hear that man. Ive never trusted rom manager to flash, I always use clockwork mod. Have you tried pulling the battery and try to get into download mode?
Sent from my SAMSUNG-SGH-I727 using xda premium
immor2al said:
So just messing around, i decided to flash a t-mobile rom, via clockwork rom manager, now the skyrocket wont even power on. So thanks Rom Manager for the bricked phone, Bad Buisness....
Click to expand...
Click to collapse
Why would you blame ROM Manager for your mistake?
A. Anytime you flash anything (even if its the correct ROM flashed the correct way (CWM)) you always assume responsibility yourself.
B. You flashed a T-mobile ROM on your AT&T Skyrocket. If done right, it usually works, but it still adds extra risk.
C. You said you were "just messing around". Anyone that doesn't want a bricked phone should take flashing or modifying anything serious...not just messing around.
D. Most of the ROMS you are supposed to flash on the SkyRocket give detailed directions in the OP. Any I have sen all say to use CWM and give great instructions.
I don't see how any of this is ROM Managers bad business? Hopefully this will be a good tale of precaution for others before they brick their phone not paying attention. Sorry to hear about your phone, but take the blame for yourself...not ROM manager.
scott14719 said:
Why would you blame ROM Manager for your mistake?
A. Anytime you flash anything (even if its the correct ROM flashed the correct way (CWM)) you always assume responsibility yourself.
B. You flashed a T-mobile ROM on your AT&T Skyrocket. If done right, it usually works, but it still adds extra risk.
C. You said you were "just messing around". Anyone that doesn't want a bricked phone should take flashing or modifying anything serious...not just messing around.
D. Most of the ROMS you are supposed to flash on the SkyRocket give detailed directions in the OP. Any I have sen all say to use CWM and give great instructions.
I don't see how any of this is ROM Managers bad business? Hopefully this will be a good tale of precaution for others before they brick their phone not paying attention. Sorry to hear about your phone, but take the blame for yourself...not ROM manager.
Click to expand...
Click to collapse
+ 1 well explained.
Sent from my SAMSUNG-SGH-I727 using Tapatalk
+2 I use rom manager quite often. For fixing permissions. And when I'm to lazy to boot to cwm myself...NEVER had a single issue with it. Sounds lke mabye rom manager is perhaps not the red handed bandit in this soap opera.........but remember if all else fails blame canada.....LOL just joking ay. I have no problem with Canadians ay.
LordGeek said:
+ 1 well explained.
Sent from my SAMSUNG-SGH-I727 using Tapatalk
Click to expand...
Click to collapse
Thanks. I'm not trying to give the guy a hard time. He just bricked (atleast soft-bricked) his phone so I'm sure he really is pissed. But blaming an app for it when it isn't the apps fault starts alot of confusion. If something really is wrong with an app, we all need to know about it so it can be tested / fixed/ avoided / reported / etc...If the fault is with the phone's owner than the phone's owner needs to take responsibility for the problem and stop blaming the creators of useful apps (and ROMS) for the problems.
immor2al said:
So just messing around, i decided to flash a t-mobile rom, via clockwork rom manager, now the skyrocket wont even power on. So thanks Rom Manager for the bricked phone, Bad Buisness....
Click to expand...
Click to collapse
It bricked because ROM manager doesn't recognize the recovery on the skyrocket. It's something in the first line of the app.
Although, I might agree with you and blame ROM manager also if it let you flash a ROM while it couldn't detect a recovery. That's just straight up ****ty oversight on the developer.
Sent from my SAMSUNG-SGH-I727 using Tapatalk
Never use ROM manager to flash roms on the skyrocket
Sent from SKYROCKET
NexusMod 4.0
Romracer 0.3
But it does not do that. U have to let it install the T-Mobile gs2 recovery to flash anything
Well of course its my fault...i have flashed the kang Roms from there and a couple other ones...i am aware of the risks..ive been programming for years....but goddam a hard brick!! WTF. ...phone won't even power up....so i will fix it any...and maybe sell..i just went and got a Note..lol
Sent from my SAMSUNG-SGH-I717 using xda premium
immor2al said:
Well of course its my fault...i have flashed the kang Roms from there and a couple other ones...i am aware of the risks..ive been programming for years....but goddam a hard brick!! WTF. ...phone won't even power up....so i will fix it any...and maybe sell..i just went and got a Note..lol
Sent from my SAMSUNG-SGH-I717 using xda premium
Click to expand...
Click to collapse
Report on how the battery is and if it is too big
immor2al said:
Well of course its my fault...i have flashed the kang Roms from there and a couple other ones...i am aware of the risks..ive been programming for years....but goddam a hard brick!! WTF. ...phone won't even power up....so i will fix it any...and maybe sell..i just went and got a Note..lol
Sent from my SAMSUNG-SGH-I717 using xda premium
Click to expand...
Click to collapse
LOL you sir is speshel
Sent from my SAMSUNG-SGH-I727 using Tapatalk
The note is toooo big to be a primary phone. You may not be happy if you are gonna use it that way. Good luck...
i honestly love it, i had bought my wife one and she loves it, it fits my hands perfect. It operates almost identical to the skyrocket, will post later about battery, comparable to a stock Skyrocket i would imagine, but i cant wait to get my root on, sKyrocket is still my favorite.... most powerful phone out hands down! I am so pissed that it bricked that way what a bunch of crap....definetly best to stay away from clockwork rom manger download section...(KICKING MYSELF) oh...I know how to use thats not what happend..but it was a new rom i had not seen..cant even remember the name...thats what i get for not reading up on it more...So for all the noobies out there...
read...read...read..and then if u dont get it read it again!!...ahhh f_ck my life...lol..might fix it then donate
Sent from my SAMSUNG-SGH-I717 using xda premium:thumbup:
http://www.narrygsm.com/narrygsm/node/95
they want 50 online to do it plus shipping, i think ill buy thw riff box and jig and do it myself..lol
Sent from my Galaxy LTE Note via xda premium apk
immor2al said:
http://www.narrygsm.com/narrygsm/node/95
they want 50 online to do it plus shipping, i think ill by thw riff box and jig and do it myself..lol
Sent from my SAMSUNG-SGH-I717 using xda premium
Click to expand...
Click to collapse
Try Samsung first. Tell them it just derped one day when you tried to turn it on. If they believe you, it might take a week or two but you'll get another phone. Samsung will just fix it and give it to the next person that has a warranty replacement as a "referbished" unit. They won't lose money and you will get a new phone. That is if they believe you.
still a 200 dollar deductible..i could probably smoose out of it...but i would actually like to fix it my self..just for the experience.....oh and the Rom was called Ziggy and Mobstergunz..(minimal triumph.v1.02..state away from that ****
Sent from my SAMSUNG-SGH-I997 using xda premium
immor2al said:
still a 200 dollar deductible..i could probably smoose out of it...but i would actually like to fix it my self..just for the experience.....oh and the Rom was called Ziggy and Mobstergunz..(minimal triumph.v1.02..state away from that ****
Sent from my SAMSUNG-SGH-I997 using xda premium
Click to expand...
Click to collapse
That's not a i727 ROM, what the hell did you download?
Sent from my SAMSUNG-SGH-I727 using Tapatalk
Its a T-Mobile Rom....You can flash T-Mobile Roms on the SkyRocket...I never had an issue till now....I think its posted wrong..and I have seen it on my Nook...and my 10.1 and an Infuse all in rom manager....I thought it was a T989 rom...."I was wrong like Ron White"...but mobiletechvideos will get me going again...www.mobiletechvideos.com
Sent from my SAMSUNG-SGH-I717 using xda premium
Good luck man. Sucks that happened!
Sent from my SAMSUNG-SGH-I727 using XDA
Here is the zip file to apply to the 2.3.5 fxz, to make RSDlite flash the FXZ files properly, from the ICS leak. The steps are the same as they were for the 2.3.6 fix. Just unzip these files over top of the original fxz files.
+++++++++++++++++++++++NOTE++++++++++++++++++++++++++++++++++++++++++++
I have pulled these files, so that no else attempts to flash the fxz and brick thier phone. DO NOT ASK FOR THE FILES, I will not give them out knowing what happens to those on ICS that try to fxz back to GB.
Damn you are so on point ..... Starting to think Jim is like 10 people.....
hankbizzo5 said:
Damn you are so on point ..... Starting to think Jim is like 10 people.....
Click to expand...
Click to collapse
LOL... You forget I had to think of several ways to possibly break this before I posted it for the rest of the world, so if there were issues, I knew what to do... How do you think I was able to flash that whole process 4 times... I built this yesterday afternoon, before I even started the process of testing the OTA out. I HAD to make sure we could flash back, so we were not like the OG Atrix guys, who can't flash an SBF now.
Thank You Jim, you are awesome.
jimbridgman said:
LOL... You forget I had to think of several ways to possibly break this before I posted it for the rest of the world, so if there were issues, I knew what to do... How do you think I was able to flash that whole process 4 times... I built this yesterday afternoon, before I even started the process of testing the OTA out. I HAD to make sure we could flash back, so we were not like the OG Atrix guys, who can't flash an SBF now.
Click to expand...
Click to collapse
I really hope you know how much we appreciate you being a huge asset to the atrix 2 ..... Even with the sgiii you did not leave us hanging.....Think we would be close to a chicken with his head cut off running around without you.....
There would be no way I would ever update without option to downgrade.....
Getting this added to the Noobs post as well!
Has been added along with intructions!
I'm might be using these soon. I lose data and service with the ics leak every thirty minutes, sometimes less.
Sent from my MB865 using Tapatalk 2
leifemagnuson said:
I'm might be using these soon. I lose data and service with the ics leak every thirty minutes, sometimes less.
Sent from my MB865 using Tapatalk 2
Click to expand...
Click to collapse
Sounds like a bad Sim card. I'm not trying to clutter, just trying to help out so he can stay on ics.
Sent from my MB865 using xda premium
I assume I can get away with just wiping data and cache, then flashing boot and system from 2.3.6 for a quick unbrick.
lkrasner said:
I assume I can get away with just wiping data and cache, then flashing boot and system from 2.3.6 for a quick unbrick.
Click to expand...
Click to collapse
nope I tried... You might even need that recovery.img to bring you back to GB recovery first... I had to do that one time...
jimbridgman said:
nope I tried... You might even need that recovery.img to bring you back to GB recovery first... I had to do that one time...
Click to expand...
Click to collapse
hmm, what didn't work about it? just won't boot. Recovery makes some sense, but what else is even flashed other than webtop, which I don't care about
lkrasner said:
hmm, what didn't work about it? just won't boot. Recovery makes some sense, but what else is even flashed other than webtop, which I don't care about
Click to expand...
Click to collapse
the first time it would not boot, because the lbl file and the mbm were not loaded, and it is critical in this move back.... they have done something to the BL, to make flashing a little harder. I did a hex dump and a decompile of the new mbm file and it has a spot in it that looks like a check for correct lbl file being loaded from the fastboot flash.
The issue with the recovery is because it flashes a new recovery, and that was on the second time I had to flash the fxz, due to a bad root...
hankbizzo5 said:
I really hope you know how much we appreciate you being a huge asset to the atrix 2 ..... Even with the sgiii you did not leave us hanging.....Think we would be close to a chicken with his head cut off running around without you.....
There would be no way I would ever update without option to downgrade.....
Click to expand...
Click to collapse
+1, Jim I've said it before; thank you for always being here for us!
Sent from my MB865 using Tapatalk 2
tmease1 said:
Sounds like a bad Sim card. I'm not trying to clutter, just trying to help out so he can stay on ics.
Sent from my MB865 using xda premium
Click to expand...
Click to collapse
Mmmm i don't think so i kinda have the same issue. But i love ics so i guess i wouldn't turn back to gb
Sent from my MB865 using xda premium
This fxz file is for All atrix 2 or only for the att atrix 2?
Sent from my MB865 using xda premium
Before attempting to fxz back make sure you upgrade RSDlite to the latest version, 5.7 or later.
Sent from my SAMSUNG-SGH-I747 using xda premium
jimbridgman said:
Before attempting to fxz back make sure you upgrade RSDlite to the latest version, 5.7 or later.
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
is that all the problem is? I would still like to know what you did the first 4 times you restored, whatever that crazy process was. I can risk a brick today, my replacement comes anyways, but many others have already been totally screwed.
lkrasner said:
is that all the problem is? I would still like to know what you did the first 4 times you restored, whatever that crazy process was. I can risk a brick today, my replacement comes anyways, but many others have already been totally screwed.
Click to expand...
Click to collapse
Me too... I have no idea why I can do it... I am pretty sure this is the same thing that the hk leak has in it. It is what we all feared.
I wonder if I have a dev phone, but my bootloader still has the A in its revision... My last replacement It seemed esier to use kexec than on other phones...
Sent from my SAMSUNG-SGH-I747 using xda premium
This is very weird, I have just redone the whole process 2.3.5 to 2.3.6 and ICS, and nothing strange happened (knock on wood).
I used the file from my signature.
shinydesert said:
This is very weird, I have just redone the whole process 2.3.5 to 2.3.6 and ICS, and nothing strange happened (knock on wood).
I used the file from my signature.
Click to expand...
Click to collapse
Did you use my patch to patch the 2.3.5 fxz for the ICS leak that I posted yesterday?
I am thinking the secret is using a script and not RSDlite. That is how I always restore my phone is with my own scripts, that I was getting ready to release before all this started.
Jim
I just hard bricked my sgs3. FIRST TIME EVER!! I've been flashing roms,kernels, etc since the MyTouch3.
Little back story.....
I flashed the LSmooth - Linaro 4.2.1 Jelly Bean Rom with CWM6. I noticed that I could not find my nandroid backups. Searched XDA and saw a thread that stated that TWRP is compatible with 4.2.1 and it will move the internal /sdcard from /0 back to its original file location, etc, etc. I went to GooManager, downloaded the twrp.tar (d2vzw), then went to MobileOdin, loaded the .tar file and flashed.
BOOM!!! No power, DOA. dead ass!! :crying::crying:
(( FACE SLAP )) then I remembered via build.prop it was configured as "maguro" and not "d2vzw". So, I'm assuming that since I failed to edit the build.prop before flashing the d2vzw TWRP recovery, it bricked my phone.
-- No power via wall, usb
-- No download / recovery mode
-- NOTHING!
My question is, if I were to call in and ask for a warranty exchange, what is the likely hood of Verizon troubleshooting, reviving my phone and figuring it out that its been rooted?
Or, should I just send my phone to someone that can JTAG it for me?
kuntri said:
I just hard bricked my sgs3. FIRST TIME EVER!! I've been flashing roms,kernels, etc since the MyTouch3.
Little back story.....
I flashed the LSmooth - Linaro 4.2.1 Jelly Bean Rom with CWM6. I noticed that I could not find my nandroid backups. Searched XDA and saw a thread that stated that TWRP is compatible with 4.2.1 and it will move the internal /sdcard from /0 back to its original file location, etc, etc. I went to GooManager, downloaded the twrp.tar (d2vzw), then went to MobileOdin, loaded the .tar file and flashed.
BOOM!!! No power, DOA. dead ass!! :crying::crying:
(( FACE SLAP )) then I remembered via build.prop it was configured as "maguro" and not "d2vzw". So, I'm assuming that since I failed to edit the build.prop before flashing the d2vzw TWRP recovery, it bricked my phone.
-- No power via wall, usb
-- No download / recovery mode
-- NOTHING!
My question is, if I were to call in and ask for a warranty exchange, what is the likely hood of Verizon troubleshooting, reviving my phone and figuring it out that its been rooted?
Or, should I just send my phone to someone that can JTAG it for me?
Click to expand...
Click to collapse
You can send it to verizon as they'll have no clue what hapoened since a jtag will just be a fresh like new install showing no sing of it ever modified.
Sent from my SCH-I535 using xda app-developers app
Honest answer they won't know what happened.
Second honest answer? Grow a pair and pay for your mistake.
Sent from my SCH-I535 using xda app-developers app
I hard bricked mines before christmas.. Tried to flash cwm touch img through adb.. Sent my phone to mobiletechvideos paid 60 bucks paid extra for rush processing and express return shipping. Total was 95 bucks tookn10bdays from day sent to day received
iSheep... iSheep... Meowww that's Apple VZW GSIII
kuntri said:
I just hard bricked my sgs3. FIRST TIME EVER!! I've been flashing roms,kernels, etc since the MyTouch3.
Little back story.....
I flashed the LSmooth - Linaro 4.2.1 Jelly Bean Rom with CWM6. I noticed that I could not find my nandroid backups. Searched XDA and saw a thread that stated that TWRP is compatible with 4.2.1 and it will move the internal /sdcard from /0 back to its original file location, etc, etc. I went to GooManager, downloaded the twrp.tar (d2vzw), then went to MobileOdin, loaded the .tar file and flashed.
BOOM!!! No power, DOA. dead ass!! :crying::crying:
(( FACE SLAP )) then I remembered via build.prop it was configured as "maguro" and not "d2vzw". So, I'm assuming that since I failed to edit the build.prop before flashing the d2vzw TWRP recovery, it bricked my phone.
-- No power via wall, usb
-- No download / recovery mode
-- NOTHING!
My question is, if I were to call in and ask for a warranty exchange, what is the likely hood of Verizon troubleshooting, reviving my phone and figuring it out that its been rooted?
Or, should I just send my phone to someone that can JTAG it for me?
Click to expand...
Click to collapse
I don't have an answer for your question but I would like to ask one. Did the build.prop change cause the phone to brick because it made Goo Manager download the wrong file, Mobile ODIN to flash it wrong/to the wrong place, or something else I'm totally missing? This is just a new one to me and I try to stay up on this stuff so I don't end up with a brick myself. Thanks.
JBO1018 said:
I don't have an answer for your question but I would like to ask one. Did the build.prop change cause the phone to brick because it made Goo Manager download the wrong file, Mobile ODIN to flash it wrong/to the wrong place, or something else I'm totally missing? This is just a new one to me and I try to stay up on this stuff so I don't end up with a brick myself. Thanks.
Click to expand...
Click to collapse
Yes goo manager downloads recovery based on your build prop and such that's why it's always bad at the same time to change it if you aren't careful.
Sent from my SCH-I535 using xda app-developers app
nosympathy said:
Honest answer they won't know what happened.
Second honest answer? Grow a pair and pay for your mistake.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Number 1, I need my phone for work. (plus i know people in the wireless industry)
Number 2, You tough talking on the internet. LOL!
GoonAssJuan said:
Yes goo manager downloads recovery based on your build prop and such that's why it's always bad at the same time to change it if you aren't careful.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Thanks Bro! Now I know! I've been doing this too long to miss that.
JBO1018 said:
I don't have an answer for your question but I would like to ask one. Did the build.prop change cause the phone to brick because it made Goo Manager download the wrong file, Mobile ODIN to flash it wrong/to the wrong place, or something else I'm totally missing? This is just a new one to me and I try to stay up on this stuff so I don't end up with a brick myself. Thanks.
Click to expand...
Click to collapse
I downloaded the d2vzw TWRP recovery and flashed it before changing my build.prop from maguro to d2vzw. smh
DROID3R said:
I hard bricked mines before christmas.. Tried to flash cwm touch img through adb.. Sent my phone to mobiletechvideos paid 60 bucks paid extra for rush processing and express return shipping. Total was 95 bucks tookn10bdays from day sent to day received
iSheep... iSheep... Meowww that's Apple VZW GSIII
Click to expand...
Click to collapse
Instead, I called my VZW Account Rep(when i used to work BBYMobile), told them what happened. $12 Next day ....
reason why I didnt choose MobileTech,
1. I am unsure of the wait time
2. I need my cell for work
3. $12 Next day vs. $60-$95 10 Day wait ... ehhhhh
I do appreciate the comment and response, though. Thanks Bro~
GoonAssJuan said:
You can send it to verizon as they'll have no clue what hapoened since a jtag will just be a fresh like new install showing no sing of it ever modified.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
I was wondering because my vzw rep was unsure. i was going to invest in mobiletech , but i was unsure about the wait time and not having a phone for a few days to weeks. if it was TMO or ATT, yea I would have sent it because I can find me a prepaid GSM phone and use that temporarily. Oh well, thanks for the response!
Actually, I just hard bricked my s3 a couple hours ago as well! My situation is a little different though! Earlier today I received my OTG cable in the mail from eBay....long story short, this thing just destroyed my phone....turns out I'm not the only one who's had this happen! People, please be careful, don't do what I did and buy a cheap OTG cable! There seems to be some confusion as to whether it's the cable or the phones that are the cause of the problem....just google it.... OTG hard brick.....you'll see what I'm talking about!
Sent from my ADR6400L using Tapatalk 2
Thank God for the almighty sdcard with my nandroid backup from yesterday! Should be getting my replacement s3 on Saturday, then to root and restore!
kuntri said:
Instead, I called my VZW Account Rep(when i used to work BBYMobile), told them what happened. $12 Next day ....
reason why I didnt choose MobileTech,
1. I am unsure of the wait time
2. I need my cell for work
3. $12 Next day vs. $60-$95 10 Day wait ... ehhhhh
I do appreciate the comment and response, though. Thanks Bro~
Click to expand...
Click to collapse
Maybe if you need your phone for work you shouldn't be so careless with it. Just saying.
Sent from my SCH-I535 using xda app-developers app
nosympathy said:
Maybe if you need your phone for work you shouldn't be so careless with it. Just saying.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
It would appear that you show... *adjusts sunglasses* no sympathy.
Sent from my SCH-I535 using xda premium
Obaterista93 said:
It would appear that you show... *adjusts sunglasses* no sympathy.
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
In keeping with my name...WOW! Never heard that one before!
I have been called the asshole of XDA more than a few times for a reason
Sent from my SCH-I535 using xda app-developers app
nosympathy said:
In keeping with my name...WOW! Never heard that one before!
I have been called the asshole of XDA more than a few times for a reason
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Hey, somebody's gotta do it.
Sent from FBI Headquarters
nosympathy said:
In keeping with my name...WOW! Never heard that one before!
I have been called the asshole of XDA more than a few times for a reason
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
ur good man, i cringe anytime I see a send back to vz related question as this guy is how carriers can justify locking these phones down, or one of the reasons.
not that ethics and the internet go together but what op has done is wrong and it hurts this community.
vmancini3 said:
Actually, I just hard bricked my s3 a couple hours ago as well! My situation is a little different though! Earlier today I received my OTG cable in the mail from eBay....long story short, this thing just destroyed my phone....turns out I'm not the only one who's had this happen! People, please be careful, don't do what I did and buy a cheap OTG cable! There seems to be some confusion as to whether it's the cable or the phones that are the cause of the problem....just google it.... OTG hard brick.....you'll see what I'm talking about!
Sent from my ADR6400L using Tapatalk 2
Thank God for the almighty sdcard with my nandroid backup from yesterday! Should be getting my replacement s3 on Saturday, then to root and restore!
Click to expand...
Click to collapse
Happened to a lot and can't even be Jtagged. Burns out the PCIM and non repairable as per Josh at Mobile Tech.
vmancini3 said:
Actually, I just hard bricked my s3 a couple hours ago as well! My situation is a little different though! Earlier today I received my OTG cable in the mail from eBay....long story short, this thing just destroyed my phone....turns out I'm not the only one who's had this happen! People, please be careful, don't do what I did and buy a cheap OTG cable! There seems to be some confusion as to whether it's the cable or the phones that are the cause of the problem....just google it.... OTG hard brick.....you'll see what I'm talking about!
Sent from my ADR6400L using Tapatalk 2
Thank God for the almighty sdcard with my nandroid backup from yesterday! Should be getting my replacement s3 on Saturday, then to root and restore!
Click to expand...
Click to collapse
Dang bro! My replacement came in this afternoon (3p est) and I posted this yesterday night ( i think) ... I havent messed with that OTG cable, but good looking out.
prdog1 said:
Happened to a lot and can't even be Jtagged. Burns out the PCIM and non repairable as per Josh at Mobile Tech.
Click to expand...
Click to collapse
Wow!