OK, back when kit Kat first come out I flashed a updated boot loader and when I rebooted the phone will no longer turn on. All I get is a red light. It seems I had a corrupted file. I can not get into recovery, and it seems I can't get into download mode either.
So here is my question. I read somewhere I can JTAG this phone and that will fix it. I'm unfamiliar with JTAG process so that's why I'm asking here.
Also, is there any other options?
Sent from my Nexus 5 using XDA Free mobile app
If you tried to flash a bootloader you most likely hard bricked your phone. Do you have a link to what you flashed? If you have to jtag check out mobiletechvideos.com. they've gotten very good reviews.
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
If you tried to flash a bootloader you most likely hard bricked your phone. Do you have a link to what you flashed? If you have to jtag check out mobiletechvideos.com. they've gotten very good reviews.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
I don't have the link because it was almost a year ago. I'm using a nexus 5 now but want to save this phone if possible. I'll check that out. Thanks
Sent from my Nexus 5 using XDA Free mobile app
Did you unlock the bootloader before flashing a new bootloader? I'm not sure if this makes a difference.
audit13 said:
Did you unlock the bootloader before flashing a new bootloader? I'm not sure if this makes a difference.
Click to expand...
Click to collapse
Yes, I was running PA ROM at the time. Its possible I flashed a boot loader for another phone. Lol it was early in the morning, and it was totally my fault. I'm just looking for a way to save it because its in mint condition, not even a scratch on it.
So if JTAG is the only option, I'll gladly pay for it as long as it will work.
But I was told with JTAG, or motherboard replacement is required to fix what was done.
Sent from my Nexus 5 using XDA Free mobile app
Related
My device won't boot up power or wont go to recovery mode. powering on has no vibrate feel and it stays black. I used liquid smooth.
Where did you get the liquid smooth rom?
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
What steps did you take when flashing
Have you tried download mode?
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
mg2195 said:
What steps did you take when flashing
Have you tried download mode?
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
Click to expand...
Click to collapse
I downloaded a 2.9 rom for att only
1. I wipe factory reset coming from different rom
2. I install liquid smooth
3. I install loki
4. hit reboot
5. it ask for fix for root, i slide it to fix.
6. bam! screen went black!
If all of this cant be fixed, I have to take it back to att for replacement and act dumb. I have last day to return today. 14 policy is about to expire 11:59. I had it since July 15.
If you can't even get any power and can't get into down load mode then you probably are not going to get it fixed. Have you tried odin and seen if it will recognize the device?
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
If you could get into download mode then your not in trouble just reflash stock via odin?
Sent from my SAMSUNG-SGH-I337 using xda premium
Odin do not detect my phone. It SOL! I went to att today. They told me it was SOL too because this device won't boot into recovery or download. Nothing was turning on. So it was replaced by warranty. I told them I rooted it (not playing dumb here at this time) and they replaced it.
Does rooting void warranty right? I don't get it? But I remember on another forums said rooting does not void warranty? Unless they see custom device and unlocked boot loader void warranty?
Can someone explain clearly?
Sent from my Nexus 7 using xda app-developers app
LeonKnight12 said:
Odin do not detect my phone. It SOL! I went to att today. They told me it was SOL too because this device won't boot into recovery or download. Nothing was turning on. So it was replaced by warranty. I told them I rooted it (not playing dumb here at this time) and they replaced it.
Does rooting void warranty right? I don't get it? But I remember on another forums said rooting does not void warranty? Unless they see custom device and unlocked boot loader void warranty?
Can someone explain clearly?
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
In almost any situation, operating a device in a way other than the manufacturer intended will void the warranty. In the case of AT&T's warranty, they may have explicit clauses against jailbreaking, rooting, and firmware modification in general. In the terms of the manufacturer's warranty, they might even allow for root, but I'm not sure on this. I once saw someone (reputable dev) post that rooting by itself is not an automatic void. They have to prove that what you did broke your device (which it sounds like what you did probably borked it).
If someone has a rooted device, and suddenly the battery explodes or the LED light stops working (on an otherwise stock rom), then it's kinda hard for them to point at "you rooted it" as being the problem.
But yeah, best to look up the verbage in the warranty, to be sure.
What ROM was on there before you flashed liquid?
And what recovery?
I ask because when flashing AT&T liquid on TWRP at least, you don't flash loki and you also don't get prompted to install root. Not even after a full wipe of EVERYTHING.
Sent from my SGH-I337 using xda premium
CZ Eddie said:
What ROM was on there before you flashed liquid?
And what recovery?
I ask because when flashing AT&T liquid on TWRP at least, you don't flash loki and you also don't get prompted to install root. Not even after a full wipe of EVERYTHING.
Sent from my SGH-I337 using xda premium
Click to expand...
Click to collapse
Google edition 4.3. Is this more likely caused by it? I wiped factory reset before flashing.
Sent from my Nexus 7 using xda app-developers app
Im sorry if I missed your answer to this i didnt see it. Can you put the phone into download mode or not. Holding power and audio up?
I'm not a master at this, but wouldn't a JIG put the phone automatically into download mode, if its not bricked that bad?
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
using a jig
r8revealed said:
wouldn't a JIG put the phone automatically into download mode, if its not bricked that bad?
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
a jig I've always used for my Infuse, does in fact kick the GS4 into DL mode.
Hey guys,
Just ordered a Nexus 4 online and waiting for it to be delivered. But had to ask a quick question, that is, how easy is it to brick the Nexus 4? And if so, can it be unbricked easily via software?
I am currently using a Motorola Defy + and it its almost unbrickable and can be recovered from any type of brick. So just curious
super noob bros said:
Hey guys,
Just ordered a Nexus 4 online and waiting for it to be delivered. But had to ask a quick question, that is, how easy is it to brick the Nexus 4? And if so, can it be unbricked easily via software?
I am currently using a Motorola Defy + and it its almost unbrickable and can be recovered from any type of brick. So just curious
Click to expand...
Click to collapse
Flash the wrong kernel is a really easy way to brick your nexus 4,and the only i know
Yep worst you can do is flash a kernel or ROM meant for a different device, but even that can usually be recovered by using download mode.
Sent using xda-developers app
Federico_96 said:
Flash the wrong kernel is a really easy way to brick your nexus 4,and the only i know
Click to expand...
Click to collapse
Chromium_ said:
Yep worst you can do is flash a kernel or ROM meant for a different device, but even that can usually be recovered by using download mode.
Sent using xda-developers app
Click to expand...
Click to collapse
You can easily recover if you have a nandroid backup though I think.
Fastboot erase bootloader will brick you pretty quickly
Sent from my Nexus 4 using xda app-developers app
In short, you really have to try to brick it. Even then, it takes some work to break it to the point that you can't fix it with fastboot. You won't hard brick it on accident. I don't consider a soft brick a brick of any sort when you can fix it in 15mins with fastboot.
Pretty much the only way to brick is flashing the wrong bootloader or flashing something that isn't a bootloader to the bootloader partition.
In a way yes. Although it isnt like samsungs download mode, it is kind of unbrickable if you do brick it you just go into the bootloader use a toolkit download the stock rom and it will do the rest for you
Thanks people. Much appreciated
There is a topic somewhere in these forums with a guide that uses a program called lgtool or lgetool (can't remember which)
Which even lets you recover from a bricked bootloader. Though it is a lengthy and technical process.
So at this moment it is physically impossible to brick your phone. Unless it is bricked from actual damage to the hardware
Sent from my Nexus 4 using xda app-developers app
Alex240188 said:
There is a topic somewhere in these forums with a guide that uses a program called lgtool or lgetool (can't remember which)
Which even lets you recover from a bricked bootloader. Though it is a lengthy and technical process.
So at this moment it is physically impossible to brick your phone. Unless it is bricked from actual damage to the hardware
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Yes there's a great guide by Gigadroid somewhere in the general section. Basically as long as you can get into download mode the phone can be recovered.
Sent from my Nexus 4 using xda-developers app
Yeah I don't understand why people view flashing a wrong kernel as bricked. If you can get into the bootloader in my opinion it's not bricked!
Bricked is when it's just that, the phone can only be used as a paperweight and doesn't turn on in any sort of fashion. So doing "fastboot erase bootloader" is what I call a brick, which you'd have to be really drunk or just a total moron to do. And flashing wrong bootloader, or being so lucky as to have a power outage in the spilt second it takes to flash a bootloader is one of those I view as brick.
Sent from my Nexus 4 using XDA Premium 4 mobile app
M3drvr said:
Yeah I don't understand why people view flashing a wrong kernel as bricked. If you can get into the bootloader in my opinion it's not bricked!
Bricked is when it's just that, the phone can only be used as a paperweight and doesn't turn on in any sort of fashion. So doing "fastboot erase bootloader" is what I call a brick, which you'd have to be really drunk or just a total moron to do. And flashing wrong bootloader, or being so lucky as to have a power outage in the spilt second it takes to flash a bootloader is one of those I view as brick.
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Maybe because if you flash an incorrect kernel you can't boot into the boot loader? Just a thought.
Sent from my Nexus 4 using Tapatalk 2
joshnichols189 said:
Maybe because if you flash an incorrect kernel you can't boot into the boot loader? Just a thought.
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
When does that happen? I've never had that happen. I just purposely flashed a wrong kernel and i can still get to bootloader and recovery...
M3drvr said:
When does that happen? I've never had that happen. I just purposely flashed a wrong kernel and i can still get to bootloader and recovery...
Click to expand...
Click to collapse
I saw a thread where someone flashed nexus 7 kernel on the nexus 4 and he had to buy a new device,but maybe Gigadroid wrote the guide after that thread
Federico_96 said:
I saw a thread where someone flashed nexus 7 kernel on the nexus 4 and he had to buy a new device,but maybe Gigadroid wrote the guide after that thread
Click to expand...
Click to collapse
I remember accidentally doing that on my galaxy Nexus. But twrp actually caught it and wouldn't allow me to install it. Kept errroring out.
Sent from my Nexus 4 using XDA Premium 4 mobile app
Harry GT-S5830 said:
Fastboot erase bootloader will brick you pretty quickly
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
This isn't a true fastboot command
But yes, this is a very hard device to brick, most everything is recoverable. But I'm sure there are plenty who find a way to do this, usually the ones who dive in head first and have bad luck.
Just be sure you read and understand before you try and beg for help
Sent from my Nexus 7 using Tapatalk 2
Get in fastboot mode..
Erase bootloader
Reboot
Profit??
Sent from my Nexus 4 using xda app-developers app
demkantor said:
This isn't a true fastboot command
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
Have you actually tried the command.
On the nexus 7 this was a valid fastboot command and there was a few instances of people bricking by erasing the bootloader then rebooting before flashing another one
It probably would be a good idea for Google to have removed the ability to erase the bootloader as there really is no need to erase it
Sent from my Nexus 4 using xda app-developers app
WOW after i sold my s4 and got nexus 4 im even loving nexus moreeeDDD i wish nexus 5 is awesome as this DD
My S4 is currently running MF3, i rooted while in MF3 so it was that soft root stuff without the bootloader. i figured it was time for an update to 4.3 so when i went to Unroot the phone it literally just sat at the Samsung Custom Screen. I tried to access the TWRP and restore that way, Nothing happend, i took it to best buy and tried to reflash it that way, their computer couldn't see my phone.
So my last option would be to connect it into Odin correct? Would this work or am i wasting my time?
Try Odin. There is a thread with the correct files.
Also, please do not talk about smashing or purposely damaging your phone for warranty. That is warranty fraud and is not allowed on XDA.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
graydiggy said:
Try Odin. There is a thread with the correct files.
Also, please do not talk about smashing or purposely damaging your phone for warranty. That is warranty fraud and is not allowed on XDA.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Lol True , sorry bout that. I'll give odin a try, i have the thread...just hoping this really works
It should work. Make sure you have your drivers and your device in DL mode when you connect it to your PC. Also use a back USB port.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
Hey fellas!
I am actually a N5 owner and using it without rooting it for past 6 months and pretty happy with that.Before N5 i had Galaxy S3 on which i tried a lot of things and learned about rooting,flashing..etc.
Now i have my friends N4 which always stuck at bootloop after update(that's what my friend told me) i tried clearing cache,factory reset from the stock recovery but all in vain.I have no drivers installed in my lappy just for info.
So, what info i have?
in recovery it is showing build no - KRT16S
Bootloader ver - MAK0Z30d
Baseband ver - M9615A-CEFWMAZM-2.0.1700.97
Secure Boot - enabled
Lock State - locked
What can i do?
U tell me!
Flash factory image, latest one
Update your recovery and try flashing again.
Maybe unlock the bootloader and flash the factory image with a toolkit
axlrvx said:
Maybe unlock the bootloader and flash the factory image with a toolkit
Click to expand...
Click to collapse
Flash the factor image with a tool kit? Why would you need that. Just flash it in fastboot.
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
Flash the factor image with a tool kit? Why would you need that. Just flash it in fastboot.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
To make all easier, not everyone knows how to flash images via fastboot. Both ways takes you to the same place.
axlrvx said:
To make all easier, not everyone knows how to flash images via fastboot. Both ways takes you to the same place.
Click to expand...
Click to collapse
Everyone should know how if they're messing with their phone
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
Everyone should know how if they're messing with their phone
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
That is your opinion, he can decide what to do, there's no only one solution.
This link can help you @Z3US911 http://forum.xda-developers.com/showthread.php?t=2015469
thank you guys for all your help.
I unlocked my bootloader and flashed stock image and it worked. ☺
Thank yaaaa!
Sent from my Nexus 5 using XDA Free mobile app
This is probably the worst thing that has happened but i rooted my gs4 and was trying to install a custom recovery but knowing my smart self i forgot to safestrap and like bricked my gs4. I am dealing with SECURE FAIL: KERNEL any suggestions??
R800x_user said:
This is probably the worst thing that has happened but i rooted my gs4 and was trying to install a custom recovery but knowing my smart self i forgot to safestrap and like bricked my gs4. I am dealing with SECURE FAIL: KERNEL any suggestions??
Click to expand...
Click to collapse
If you see this while booting into stock recovery, that can be ignored as we don't use the stock recovery for anything other than ota.
If you see this during normal boot, you would have to Odin back to stock and start over.
Well I can't boot into recovery I get this all the time
Sent from my Nexus 5 using XDA Free mobile app
Sent from my Nexus 5 using XDA Free mobile app
R800x_user said:
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
No, not recovery, ODIN mode. Volume down and power.
Even after Odin restoring I still get this screen
Sent from my Nexus 5 using XDA Free mobile app
Thanks for helping out, I have found a solution.
Sent from my Nexus 5 using XDA Free mobile app
R800x_user said:
Thanks for helping out, I have found a solution.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
What was it, in case others have similar problem--