Hi all, so I went to flash Franco kernel on my n4, and I clicked on nexus 4 kernels, but somehow ended up going to the page with the gnex kernels, and flashed that instead. I didn't realize that till after I bricked my phone when I went on my friends phone and then checked the page. Idk how that happened that I was directed to the gnex kernel page, but I was. So anyway, I hard bricked my phone and wondering if There's any way to save it? It won't even boot up, or go into bootloader mode, or anything. please help?? Thanks!
Try holding volume down and then plugin your usb cable in your pc. Worked for me and mine is still hardbricked! Maybe you can get into fastboot and restore
lowtje said:
Try holding volume down and then plugin your usb cable in your pc. Worked for me and mine is still hardbricked! Maybe you can get into fastboot and restore
Click to expand...
Click to collapse
it doesnt even turn on, and i have a mac :/ i have no way to get into fastboot mode
It doesn't turn on? What did you mean? Do you see the Google logo when you press the power button? Try holding volume keys and power to get to fast boot.
Try downloading the drivers from the pdanets software. I think they have a Mac version which will enable you to use fast boot on Mac. Go to Google factory images page and download the nexus 4 image. Unzip it and use flash the boot image by using the fastboot command : fastboot flash boot boot.IMG
Sent from my Nexus 4 using xda app-developers app
Ieatnoobs said:
It doesn't turn on? What did you mean? Do you see the Google logo when you press the power button? Try holding volume keys and power to get to fast boot.
Try downloading the drivers from the pdanets software. I think they have a Mac version which will enable you to use fast boot on Mac. Go to Google factory images page and download the nexus 4 image. Unzip it and use flash the boot image by using the fastboot command : fastboot flash boot boot.IMG
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
like i mean that no matter how long i hold the power button, the phone doesnt turn on. its just a black screen. no logo, no boot anumation, nothing. i cant even boot into fastboot or recovery, so i cant do any fastboot commands
Maybe the battery is dead? Try charging it?
Sent from my Nexus 4 using xda app-developers app
Melad360 said:
like i mean that no matter how long i hold the power button, the phone doesnt turn on. its just a black screen. no logo, no boot anumation, nothing. i cant even boot into fastboot or recovery, so i cant do any fastboot commands
Click to expand...
Click to collapse
Leave it in the charger overnight. And try to use an high amp charger like the ipad one
Sent from my iPad using Tapatalk HD
lowtje said:
Leave it in the charger overnight. And try to use an high amp charger like the ipad one
Sent from my iPad using Tapatalk HD
Click to expand...
Click to collapse
it was at 95% when i bricked it though, theres no way the battery is dead :/
so i called google about replacing it, they said that they will email the original buyer (my dad) to authorize an exchange, so i might be able to get a new n4
Melad360 said:
so i called google about replacing it, they said that they will email the original buyer (my dad) to authorize an exchange, so i might be able to get a new n4
Click to expand...
Click to collapse
Not to sound like an asshole or anything but to be completely honest, I kinda hope Google doesn't replace that phone of your for free. You messed it up by not double checking everything twice before clicking that confirm button when you went to flash a new kernel. You knew that if you messed up your phone is dead. But now Google has to shell out a new phone because YOU messed up, not Google.
Gonna ruin it for people that actually did get a defected device...
Melad360 said:
so i called google about replacing it, they said that they will email the original buyer (my dad) to authorize an exchange, so i might be able to get a new n4
Click to expand...
Click to collapse
Not cool. You need to fix this yourself.
What were you thinking flashing stuff to your phone but not having the ability to use fastboot and other dev tools? If you're going to intentionally gut out the functionality of your phone, have the tools and willingness to deal with problems! This isn't Google's fault, don't leave them with the bill!
Sent from my Nexus 4
waffleman911 said:
Not to sound like an asshole or anything but to be completely honest, I kinda hope Google doesn't replace that phone of your for free. You messed it up by not double checking everything twice before clicking that confirm button when you went to flash a new kernel. You knew that if you messed up your phone is dead. But now Google has to shell out a new phone because YOU messed up, not Google.
Gonna ruin it for people that actually did get a defected device...
Click to expand...
Click to collapse
how can i double check something that doesnt have a device model on it? it simply says "Franco.kernel nightly r-number.zip", i dont know how i managed to end up on the gnex kernel list, when i specifically clicked on nexus 4 kernels. that was beyond my control, its not like i made a stupid mistake on purpose. i double checked everything, making sure i was on the right xda page, and i downloaded a zip file not an img file, etc, i did everything i could do, yet little things slip
Melad360 said:
how can i double check something that doesnt have a device model on it? it simply says "Franco.kernel nightly r-number.zip", i dont know how i managed to end up on the gnex kernel list, when i specifically clicked on nexus 4 kernels. that was beyond my control, its not like i made a stupid mistake on purpose. i double checked everything, making sure i was on the right xda page, and i downloaded a zip file not an img file, etc, i did everything i could do, yet little things slip
Click to expand...
Click to collapse
Post the url you click that forwarded you to the gnex page. I'd be willing to bet that it says up top in orange, something along the line of "gnex>android development>gnex kernels"
Did you read the comments of that thread?
When you were in TWRP/CWM, the name of the file didn't hint at either gnex or nexus 4? It should have, if I'm not mistaken. There are always few ways to double check the file you downloaded.
Melad360 said:
how can i double check something that doesnt have a device model on it? it simply says "Franco.kernel nightly r-number.zip", i dont know how i managed to end up on the gnex kernel list, when i specifically clicked on nexus 4 kernels. that was beyond my control, its not like i made a stupid mistake on purpose. i double checked everything, making sure i was on the right xda page, and i downloaded a zip file not an img file, etc, i did everything i could do, yet little things slip
Click to expand...
Click to collapse
But this is Google's fault?
Sent from my iPad 4
k everyone calm down. I am sure all of us made that stupid mistake someday. None of us are perfect humans. We learn from mistakes. At least thats what we are suppose to do. Anyway, glad it worked out for OP.
So...it won't turn on at all? Did you someone flash a bootloader or something?
Maybe JTAG it. Hire somebody who knows how to use that technology and you could get it restored.
Melad360 said:
how can i double check something that doesnt have a device model on it? it simply says "Franco.kernel nightly r-number.zip", i dont know how i managed to end up on the gnex kernel list, when i specifically clicked on nexus 4 kernels. that was beyond my control, its not like i made a stupid mistake on purpose. i double checked everything, making sure i was on the right xda page, and i downloaded a zip file not an img file, etc, i did everything i could do, yet little things slip
Click to expand...
Click to collapse
Obviously this isn't the case because the links work just fine..
Sent from my Nexus 4 using Tapatalk 2
I`m calling google to tell them not to give a free phone to that guy! He should be charged every penny for the new phone!
Not to troll the OP, but man I'm seeing these threads all the time now and it's seriously annoying and down right fraudulent!
If you buy a new car, drive it off the lot and wreck it five miles down the road while breaking every traffic law known to man, you can not bring the heap of metal and plastic back to the dealership and demand another.
YOU voided your warranty! YOU flashed third party firmware! YOU improperly flashed third party firmware and bricked your device as a result. Do not blame Google, Franco, or anyone else for YOUR mistake!
Google has no responsibility for your device now, they guarantee that it works from the factory in the condition they sold it in. Once you click 'Yes' in the bootloader to unlock your device, you're on your own should you screw up... That's what that message is telling you!
I, for one, enjoy getting a nice phone at a great price. People like you are the reason carriers and OEMs charge $600+ now! Take responsibility for breaking it... Perhaps next time you should read, then when you think you know enough, read some more!
Spoiled children...
Sent from my Nexus 4 using xda premium
Related
So i accidently bricked my phone trying to update my modwm to the newest froyo one.
Now I keep trying too odin back to stock but it wont work. Ive bricked before and used my laptop and it restored but now it doesnt work on my laptop nor my desktop. They either both say the device is unknown or it connects and when I try to flash it either freezes on file analyses or param.
Im going to go to the sprint store later today and try to get a new one. When I try to turn my phone on i get the little phone arrow computer sign. Do you think if I tell them that my phone froze so I took out the battery and that happened they will believe me? Idk how much of rooting the sprint employees know. Should I deny everything?
You will likely need to tell the tech that you had some bugs (force closes or something) and tried to do a reset through recovery mode and ended up with a non-working phone. Techs will likely know a bit about rooting and roms, especially if they have their own android phone. They also know that rooting and 3rd party roms void your warranty and they are supposed to deny claims where the phone was running 3rd party roms.
Can they tell if I rooted it just by the phone to computer sign? I went to a sprint store earlier and they told me to go to the corperate store because he didnt know what that meant.. Also I bought it from bestbuy so if sprint doesnt cover it would bestbuy?
sasha101 said:
Can they tell if I rooted it just by the phone to computer sign? I went to a sprint store earlier and they told me to go to the corperate store because he didnt know what that meant.. Also I bought it from bestbuy so if sprint doesnt cover it would bestbuy?
Click to expand...
Click to collapse
Bestbuy won't cover it. And if you plan on exchanging the phone, you'll have to go to the Sprint Corporate center. I bricked my phone the other day and it was only a $35 exchange for a new Samsung Epic. I only had to wait a day for a new one. They won't give you a new battery or SD card, so make sure to hold on to those.
Sorry about your phone.
If the phone is off can you hold the 1 button on the keyboard and power button and does a yellow downloading screen come on?
Sent from my SPH-D700 using XDA App
tphillips78 said:
If the phone is off can you hold the 1 button on the keyboard and power button and does a yellow downloading screen come on?
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
I don't think it would matter, truthfully. If the computer doesn't recognize the phone to begin with, putting the phone into download mode won't have any effect.
acer1096xxx said:
I don't think it would matter, truthfully. If the computer doesn't recognize the phone to begin with, putting the phone into download mode won't have any effect.
Click to expand...
Click to collapse
Different usb cable maybe? If sasha101 can get into download mode the phone isn't bricked and there is at least still hope. Maybe re downloading odin and other files as well. Just a thought.
Sent from my rooted Samsung Epic 4Gless device running ViperRom Trinity V3.0.3 using XDA App
I usually have to rotate between the different pits (512, 513, 528, and no pit) before I can get it to succesfully flash, so this is something you can try.
I would definitly try a different cable. I wasn't able to use odin to load 2.1 and in fact I bricked (I think). Tried 2 different cables and tried someone else's pc. NO go. Went back to the best set of directions I had found, redownloaded all the software needed, borrowed my wife's cable and started over. Everything worked like I was told it should. I really believe I had cables. Will try to find a new good one for the next time I try Odin.
Good luck and Marry Christmas.
George MacDonald
Sent from my SPH-D700 using XDA App
Randyshear on youtube explains this process flawlessly very informative
Sent from my SPH-D700 using XDA App
Umm.. if its not recognizing your phone you either didn't download the drivers; or they didn't install right. So.. (re)install them..
If this doesn't work its your cable; you'll need a new one.
Also; android isn't bricked until you can't get into download mode anymore.
Just because it doesn't boot doesn't mean its not bricked.
Sent from my SPH-D700 using XDA App
So I sent my phone into samsung the other week to get reflashed after a ota update bricked it, I have the samsung vibrant like everyone else in this section hehe
They fixed it and sent it back, I started flashing some custom roms and then i flashed a custom kernel, Odin froze and I wanted, tryed to reset the phone and OH CRAP! there was the dreaded pc to phone screen I had before I sent it in, I was like oh no! So I got mad and let it sit for a hour, I looked online and bought a jig to get it back(im glad I did, i might need it later) I havent got the jig yet either since this was last night. I plugged the phone back into my pc, and ding ding it recognized it on that screen and it didnt before I sent it to samsung. I was able to odin from that thing, I was so happy and rejoiced! has anyone ever been able to? I bricked it again on purpose and did the same thing over too, so samsung must of changed something
devilsrogue said:
So I sent my phone into samsung the other week to get reflashed after a ota update bricked it, I have the samsung vibrant like everyone else in this section hehe
They fixed it and sent it back, I started flashing some custom roms and then i flashed a custom kernel, Odin froze and I wanted, tryed to reset the phone and OH CRAP! there was the dreaded pc to phone screen I had before I sent it in, I was like oh no! So I got mad and let it sit for a hour, I looked online and bought a jig to get it back(im glad I did, i might need it later) I havent got the jig yet either since this was last night. I plugged the phone back into my pc, and ding ding it recognized it on that screen and it didnt before I sent it to samsung. I was able to odin from that thing, I was so happy and rejoiced! has anyone ever been able to? I bricked it again on purpose and did the same thing over too, so samsung must of changed something
Click to expand...
Click to collapse
don't know, but that PC to Phone screen IS the download mode, you can just connect your phone to PC and odin from that screen
No its not, download mode has the android sweeping up rubble, that is the softbrick screen lol
devilsrogue said:
No its not, download mode has the android sweeping up rubble, that is the softbrick screen lol
Click to expand...
Click to collapse
From what I've read, you can ODIN back to stock even when on that screen so it is pretty much like download mode.
Hmmm, why didnt it work before? i couldnt get it do anything until samsung sent it back to me, Odd....hmmmm
This is 10000% true. I've done it
sahil04 said:
From what I've read, you can ODIN back to stock even when on that screen so it is pretty much like download mode.
Click to expand...
Click to collapse
Sent from my SGH-T959 using XDA App
Sometimes takes several tries. It usually doesn't work until you start to get really scared around attempt #5-6.
Sent from my SGH-T959 using XDA App
I have had it non responsive on the pc-to-computer screen. If this happens you just do the battery pull hold 2 button then plug into the computer to get it into download mode......but you also may need to hit the home and menu button to get it to be responsive. Or- just get the jig..............
devilsrogue said:
No its not, download mode has the android sweeping up rubble, that is the softbrick screen lol
Click to expand...
Click to collapse
Can I say told ya?
When you see the phone to PC screen just hold the power button and the volume up/ down until you see the symbol for the second time then plug your USB into your phone and the COM port should show up.
Sent from my SGH-T959 using XDA Premium App
Ive bricked my Nexus 4. It was my fault.
Ive been reading around for a solution. I get the Download USB device in task manager, and a USB input device while the red light comes on after holding the power button. No fast boot, screen activity or vibrations.
Ive read that a few people have sent in their Nexus 4's for RMA's while they have bricked custom ROMs installed, none of them seem to post how the RMA went. Do google check for this sort of thing, or just flash a new firmware onto it once they receive it, or have people been charged for the cost of repairing it?
yolo-swag said:
Ive bricked my Nexus 4. It was my fault.
Ive been reading around for a solution. I get the Download USB device in task manager, and a USB input device while the red light comes on after holding the power button. No fast boot, screen activity or vibrations.
Ive read that a few people have sent in their Nexus 4's for RMA's while they have bricked custom ROMs installed, none of them seem to post how the RMA went. Do google check for this sort of thing, or just flash a new firmware onto it once they receive it, or have people been charged for the cost of repairing it?
Click to expand...
Click to collapse
Are you able to boot to bootloader or recovery mode? If you can, you can probably revive it.
How did you do it? Sounds like you flashed a kernel for another device.
joshnichols189 said:
How did you do it? Sounds like you flashed a kernel for another device.
Click to expand...
Click to collapse
Flashed Franco Kernel. Im 90% sure it was the correct one, but I clearly did something wrong.
scream4cheese said:
Are you able to boot to bootloader or recovery mode? If you can, you can probably revive it.
Click to expand...
Click to collapse
No. I just get the red light, nothing else.
yolo-swag said:
Ive bricked my Nexus 4. It was my fault.
Ive been reading around for a solution. I get the Download USB device in task manager, and a USB input device while the red light comes on after holding the power button. No fast boot, screen activity or vibrations.
Ive read that a few people have sent in their Nexus 4's for RMA's while they have bricked custom ROMs installed, none of them seem to post how the RMA went. Do google check for this sort of thing, or just flash a new firmware onto it once they receive it, or have people been charged for the cost of repairing it?
Click to expand...
Click to collapse
Try opening up the phone and unplugging the battery, plugging it back in and try turning on the phone. Its worked for some people with the RLOD
Sent from my Nexus 7 using xda premium
speedygonzo said:
Try opening up the phone and unplugging the battery, plugging it back in and try turning on the phone. Its worked for some people with the RLOD
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Would that have any different result than just leaving it for a week? I left it at home while I went back to uni, so the battery will be dead when I get back. Don't want to make it obvious i've opened it.
yolo-swag said:
Would that have any different result than just leaving it for a week? I left it at home while I went back to uni, so the battery will be dead when I get back. Don't want to make it obvious i've opened it.
Click to expand...
Click to collapse
Well its not really hard if you try to open it, just take your time, and from what I've seen in the forums, its helped many users. You shouldn't have to worry about making it look obvious that you've opened the phone. You only have to remove 4 screws, and that's including the 2 on the actual battery.
Sent from my Nexus 7 using xda premium
Update:
Google accepted my RMA. They have removed their hold on the money, I returned the phone on the 16th.
I have not had any communications back from google about my RMA.
yolo-swag said:
Update:
Google accepted my RMA. They have removed their hold on the money, I returned the phone on the 16th.
I have not had any communications back from google about my RMA.
Click to expand...
Click to collapse
Google for some reason is being very generous with RMA's. On the playstore website it states that RMA's for defects can only be done in the first 15 days after purchase, after that it has to be sent to LG for repairs. But I've seen people RMA a device up to 4 months after getting it. Not sure why they are being so generous unless the Nexus 4's are having a really large failure rate and they are just being nice.
I just bought a 32GB Nexus 7 2 Gen and i can't get to home screen without force closed apps. It seems like the hardware is broken on mine, but before i head over to bestbuy for replacement i thought it could be a bad flash on ASUS part. As soon as i connect to wifi, it says that there is update, it restarts, but i get the yellow triangle thingie with error written below it. I thought i could try to flash the factory image, but i can't find it. I'm pretty sure it should be online, but i could be wrong. So, does somebody have the link with the factory image of the newest Nexus 7?
bormasina said:
I just bought a 32GB Nexus 7 2 Gen and i can't get to home screen without force closed apps. It seems like the hardware is broken on mine, but before i head over to bestbuy for replacement i thought it could be a bad flash on ASUS part. As soon as i connect to wifi, it says that there is update, it restarts, but i get the yellow triangle thingie with error written below it. I thought i could try to flash the factory image, but i can't find it. I'm pretty sure it should be online, but i could be wrong. So, does somebody have the link with the factory image of the newest Nexus 7?
Click to expand...
Click to collapse
As of right now, google has not made the factory image available.
Take it back. Sure you may be able to fix it now and its probably just software related, but that's not a good sign and could just set you up for future issues.
Sent from my Nexus 4 using xda premium
Hmmm... connected mine to wifi first, and had 2 updates. A small one right after the connection to wifi, and a larger 51Meg after getting the tablet somewhat setup.
Maybe boot into recovery and do a factory reset?
lupin_iii said:
As of right now, google has not made the factory image available.
Click to expand...
Click to collapse
That is what i thought. I'm browsing from corporate network, so i thought the corporate network is playing tricks on me ...
michaelg1030 said:
Take it back. Sure you may be able to fix it now and its probably just software related, but that's not a good sign and could just set you up for future issues.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
That is what i'm afraid of, i got lazy and thought i could fix it my self if it is only bad flash ... But, you are right, batter safe than sorry ... Funny, i couldn't even play with it ...
Deathman20 said:
Hmmm... connected mine to wifi first, and had 2 updates. A small one right after the connection to wifi, and a larger 51Meg after getting the tablet somewhat setup.
Maybe boot into recovery and do a factory reset?
Click to expand...
Click to collapse
Well, i can't get into recovery either ... Hmm
bormasina said:
That is what i'm afraid of, i got lazy and thought i could fix it my self if it is only bad flash ... But, you are right, batter safe than sorry ... Funny, i couldn't even play with it ...
Well, i can't get into recovery either ... Hmm
Click to expand...
Click to collapse
Well, i'll take that back, i can get into recovery since it fails right after the first update (inside the recovery), so when i press volume up i see that the small update is messed up ...
I forgot that i need to press volume up, not "power + volume up" ... So, BestBuy here i come ...
Ok, I've looked around for the answer and from what I've ready, I don't think I can do this but I want to make sure I properly understand what I have read.
My phone came stock with AT&T's MF3, i was able to successfully root and debloat the phone without issues. I was very careful the entire process and everything works perfectly. But then what did I do? I modded the build.prop (it was late and I was tired... I shouldn't have done it) file without thinking "I don't have a recovery method if this fails"... I KNEW there was no MF3 firmware available for recovery in Kies, and I knew no one has found an workable solution in Odin... But these didn't cross my mind that night. So, when I rebooted my phone, it would go past the samsung boot logo but never show AT&T's logo. The screen goes black after the Samsung logo, the remains black. After about 10 - 20 seconds the LED at the top left of the phone will turn on blue and throb. If I plug my phone into a USB port, it will try to install drivers as "MTP USB Device" but fail. The longer I leave the phone the warmer it gets regardless of whether or not it's plugged in.
I can boot into Download Mode and Stock Recovery
I've tested the drivers with my wife's phone and everything works as expected
I can boot into Stock Recovery and sideload files (I tried to flash an OTA file another user hosted here, it was sent via ADB sideload but it failed due to my debloating the /system/apps folder)
I've tried using stock recovery to flash a zip file to replace build.prop, but failed (not signed by samsung)
I've successfully flashed the "MF3_BTL_FIX" file another user created to kick a person out of the yellow triangle, when Kies fails.
I've tried best buy, but the samsung specialist will not even plug my phone into their computer
I have a backup build.prop, I just can't figure out how to get it on my phone without a custom recovery.
So, is there any way to replace the build.prop file with Odin/Heimdall or flashing or sideloading something from stock recovery?
My wife has the same phone, so I can also get files from her phone if I need to.
Any help or advice (even if it's "you have to wait for MF3 to be released in kies") would be greatly appreciated.
I'd find another bestbuy and see if you have better luck there.
jd1639 said:
I'd find another bestbuy and see if you have better luck there.
Click to expand...
Click to collapse
I think this is my best option too, but the next closest best buy is 1.5 hours from this one.... Getting time to go there will be the hardest part for me... that's what I get for living in the middle of nowhere...
dustyhughes said:
I think this is my best option too, but the next closest best buy is 1.5 hours from this one.... Getting time to go there will be the hardest part for me... that's what I get for living in the middle of nowhere...
Click to expand...
Click to collapse
Road trip!
jd1639 said:
Road trip!
Click to expand...
Click to collapse
HAHAHA! seriously! "Come on Kids, we're going on a field trip for science... COMPUTER science!"
But really, I may be heading out there Friday. They actually have 2 full stores there and 2 "mobile" stores.... I guess I'll see if I can get someone in one of those places to help.
Did you try a factory reset in Stock recovery?
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
graydiggy said:
Did you try a factory reset in Stock recovery?
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Unfortunately, yes... It formats /data and /cache... it doesn't touch /system at all (from what I could tell), so the build.prop isn't restored to factory.
What stinks is, I believe ALL i have to do is replace that ONE file! Granted it's a major file... but still, ONE file, keeping me from booting to the OS. I've even been tempted to send it to one of the guys that does the jtag repairs, but to be honest I don't know enough about what they do to know if it would even help or if I could trust them (I assume I could from what little I've read)...
I may just have to go best buy hunting.
dustyhughes said:
Unfortunately, yes... It formats /data and /cache... it doesn't touch /system at all (from what I could tell), so the build.prop isn't restored to factory.
What stinks is, I believe ALL i have to do is replace that ONE file! Granted it's a major file... but still, ONE file, keeping me from booting to the OS. I've even been tempted to send it to one of the guys that does the jtag repairs, but to be honest I don't know enough about what they do to know if it would even help or if I could trust them (I assume I could from what little I've read)...
I may just have to go best buy hunting.
Click to expand...
Click to collapse
I assume you're referring to mobiletechvideos.com and I didn't use them for jtag however I used them to fix a power button and they are awesome!
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
HiTideBlastoise said:
I assume you're referring to mobiletechvideos.com and I didn't use them for jtag however I used them to fix a power button and they are awesome!
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
I know I've heard of mobiletechvideos before, and I know they would be trust worthy, I've heard GREAT things about them... The other place I saw unbricking phones I ran across on youtube, they have a link to an ebay store (if you search ebay for "Unbrick Service Hard Bricked Samsung Galaxy S4 i337" you'll find them). They are actually a whole lot cheaper than mobiletechvideos, which is one of the reasons I looked into them and also why I'm suspicious. Not to discredit them at all, because I personally don't know what kind of work they do.
I don't even know if Jtag will allow them to fix my build.prop file. The ebay place says if the phone doesn't boot normally after doing a repair, they will restore the latest stock ROM and since i'm on MF3, well... They couldn't do much. It also makes me suspicious that in their ebay description it says:
------------------------------------------------------
By purchasing this auction you agree to the following.
1. Jtag service will avoid your warranty.
2. There is no guaranty 100% to fixed your phone, but we do our best.
3. If the phone can not fix, we will refund only $ 30.00, minus $5.80 for shipping cost.
4. If you claim for any problem after successful unbricked the phone, you need to send it back for inspection. Because we tested it before ship.
-------------------------------------------------------
I mean, some of the wording used makes me uncomfortable... I could just be paranoid, the address on the auction IS Carrollton, Texas after all
Just thought I'd update everyone... never found a fix myself, but I did drive to the next nearest best buy with my phone in the yellow triangle mode and the guy said he knew exactly what to do. He was very friendly, knowledgeable, and helpful... He even knew how to get the phone in download mode We talked a bit, he never asked about what I may have done to the phone, but during our conversation I had told him I had backed everything up and he kind of winked and said he would take care of me. It seemed like he knew what happened, but he didn't say anything, and the "head Samsung rep", his boss was right there talking with us too. He did a full restore, and I was up and running in 10 minutes. If you get a friendly and knowledgeable employee it's pretty painless.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
This is great to hear. Glad you got it fixed. That road trip was worth it
jd1639 said:
This is great to hear. Glad you got it fixed. That road trip was worth it
Click to expand...
Click to collapse
Thanks! I'm really glad to get it back. The road trip was well worth it. My wife and I decided to make a date out of it, we went to a nice restaurant while we were out without the kids, something they wouldn't have enjoyed and we wouldn't normally go to with them
Sent from my SAMSUNG-SGH-I337 using xda app-developers app