Discussion in 'Android Devices' started by xthedakmanx, Jul 25, 2013.
Herp derp, I figured out what was going on >_< neeevermind lol
I was just looking at this phone today, I think since you got it I will too! Lol. Is yours 4g lte?
Sent from my HTCEVOV4G using Tapatalk 4 Beta
Oh no. Unfortunately, I don't do ROMS that I know will give me problems. I don't have warranty. Or maybe I do? I don't know. Good thing you had it.
@youngSWi I think most US S3s have 4G LTE including Virgin Mobile.
Yush ^_^ All the Virgin Mobile ones are LTE
You have a 30 day or something warranty when you get the phone >.< Sucks I have to wait a few more days, but oh well lol
I think you have a year of warranty, but it's probably really limited.
I had my Evo 3D for months before I realized my voicemail didn't work and after trying everything the only solution Virgin had was to reactive my account with a new phone, and they were willing to swap my Evo for another because of the 1 year warranty.
Unless you purchase additional protection the stock 1 year manufacturer warranty covers manufacturing defects, not user error.
Meh...I've done that with them for years and they haven't said a single thing about it
I just say it wont turn on, buttons don't work, etc etc, and they send me a replacement with no hassle
I think Virgin Mobile has a one year factory warranty where if you call them they'll send you a phone (but I think it's refurbished) just tell them it shut off and it won't turn back on I don't think they can check root
Please don't discuss receiving a phone that you borked and then lying to get a replacement. One word: Fraud!
Its not fraud it's a factory warranty and I didn't root my intercept or triumph so I didn't violate anything
Happened for the second time T_T
Now I'm out of a phone for a week...
DO NOT FLASH ANY, AND I MEAN ANY KERNEL IN RECOVERY RIGHT NOW
Your original post , before editing, stated that YOU bricked your phones before asking for a warranty replacement. The manufacturer 1 year warranty does not cover anything else but manufacturing defects. Not user caused problems, it's called taking one for the team. Let's not turn this into a semantical debate.
If the kernel is made for the sprint variant it should be flashing to the right partition.... "block 7"
At&t, T-mobile & Verizon variant kernels may be flashing it to the wrong block (e.g. block 5)
/dev/block/mmcblk0p5 = aboot (this is part of our boot loader partitons, if you try to write a kernel to mmcblk0p5 it will definitely brick your phone...)
Check Here for mount point and partition name reference.
uh i dont really see the point of this thread, its filled with misinformation. you are/were trying to use flash_image, thats for MTD devices (think pre-gingerbread when ext4 became the norm). you were flashing to a partition that isnt the boot kernel partition (all the sgs3's share the exact same partition layouts). and you dont flash zImage's you flash boot.img, flashing a zImage only is bound to be a bad idea
WELLLLLLLLL....Some install scripts actually do just install the zkernel. They extract the boot.img, put it the file in, and repack it right there. I do it on a few of my roms, as it's kinda the easiest way to keep things updated (Same script I posted in the OP), and it's perfectly fine on most phones to do so.
What I (finally) figured out what was happening was that somehow I kept downloading files for the wrong variant of the GS3, (DERP) and it was writing to 05 instead of the 07 one.....Although, it still doesn't really explain why it would just full on brick it, but meh.
yes, and those use koush's anykernel, teh updater script you posted did not have that.
The thread seems to have run his course. Also, we don't condone warranty fraud. By modifying the software, you take full responsibility for your actions. If you have any questions or concerns, feel free to send a pm my way.