Related
I'm new to this forum and quite a newbie. I have not rooted my phone or unlocked my bootloader. I have just always been happy with the OTA updates. I tried doing the newest update to Android 4.3. When the phone tried to reboot after installing the update, the phone got stuck on the HTC quietly brilliant screen. It wouldn't leave that screen at all, even after leaving it overnight.
I am able to boot into the bootloader. I tried to load a ROM using fastboot, but it didn't work. I am S-ON and don't really want to change anything on my phone in that sense. Is there any way that I can install the stock ROM for 4.3 to get my phone working again? If so, where can I find the files for that?
Thanks
Did you try a factory reset?
Flash~a~holic!
Yes I did try a factory reset. It did not work. It still got stuck on the same screen.
If your phone is stock then take it to a sprint store with a service center, tell them exactly what you posted here and I'm sure they can flash it for you and get it working again. If the OTA broke it.... they should fix it.
I actually went to a Sprint store and they sent for a replacement phone, so I will at least get it resolved sometime. They told me it would take a week though, so I was hoping there was something I could do that would fix it and get me a working phone quicker. Thanks for your suggestions though!
When you took it too sprint what did they say i have the same problem does anyone know how to fix this
---------- Post added at 09:16 PM ---------- Previous post was at 09:14 PM ----------
i reverted to stock updated to 4.3 then re rooted and applied the viperboy system re writeable viper mod and then restarted it and now its stuck here
krayziecali said:
When you took it too sprint what did they say i have the same problem does anyone know how to fix this
---------- Post added at 09:16 PM ---------- Previous post was at 09:14 PM ----------
i reverted to stock updated to 4.3 then re rooted and applied the viperboy system re writeable viper mod and then restarted it and now its stuck here
Click to expand...
Click to collapse
As far as I know there is no reason to to use system write btw it's for the older versions not 4.3
bigdaddy619 said:
As far as I know there is no reason to to use system write btw it's for the older versions not 4.3
Click to expand...
Click to collapse
Damn it so how do i get out of the HTC quietly brilliant screen im i gonna have to take it to sprint its rooted and it shows "This build is for Developer message"
krayziecali said:
Damn it so how do i get out of the HTC quietly brilliant screen im i gonna have to take it to sprint its rooted and it shows "This build is for Developer message"
Click to expand...
Click to collapse
Hold the power button until the light stop blinking then when it start to reboot hold the vol down button and it will bring you to bootloader once the boot to twrp and sideload a rom
bigdaddy619 said:
Hold the power button until the light stop blinking then when it start to reboot hold the vol down button and it will bring you to bootloader once the boot to twrp and sideload a rom
Click to expand...
Click to collapse
my back and home keys just keep blinking and it never reboots
got it into boot loader will try a rom
Keep holding power til they stop blinking
Hi guys so this is a little embarrassing but I'm fairly certain sprint update has bricked my phone. Sprint pushed the update to 4.4 2 nights ago for me and everything was going fine. My phone is rooted and custom recovery so I slapped on the stock recovery to process the update. The update starts off fine and dandy until about halfway through the dreaded red triangle/exclamation mark popped up. I instantly cursed and watched as my phone entered into an infinite boot loop. I thought it might have worked at first because the lock screen popped up, but when you unlock the phone the white htc logo is still there and the phone reboots after 10 seconds. So after making sure something went astronomically wrong with the update, I went into the boot loader and adb pushed twrp back onto the phone. the update somehow updated my hboot to 1.55 so my s-off is now s-on and I have no wawy to tell if the kernal for the phone is functioning. My only guess to this matter is that the boot sector for the phone is corrupt, but I tried to restore the stock twrp backup i have, and nothing. It boots, the lockscreen unlocks, but it still reboots. Now it was unlocked long enough for me to get into settings and see that it wiped ALL of my phones id info. All the meid, meie, carrier, everything is blank. So it seems that the phone crashed somewhere in the update where it was in the process of wiping things? I then tried to flash a completely different rom on there to see how that went. I first tried viperone 5.0.0 then the newer 5.8.0 and neither would boot (waited 1 hour each to make sure). Then I tried arhd 61 and again, no boot. So I'm not quite sure where to go from here. My stock backups aren't working at restoring, new rom flash isnt working, I can't take it into sprint to check on it since its rooted, I can't update the kernel due to s-on (correct me if im wrong). I'm smart enough to know when I'm out of my depth and I'm clearly trying to tread water in the middle of the ocean in this instance. So please if someone could give me a hand I would appreciate it so much.
xanex18 said:
Hi guys so this is a little embarrassing but I'm fairly certain sprint update has bricked my phone. Sprint pushed the update to 4.4 2 nights ago for me and everything was going fine. My phone is rooted and custom recovery so I slapped on the stock recovery to process the update. The update starts off fine and dandy until about halfway through the dreaded red triangle/exclamation mark popped up. I instantly cursed and watched as my phone entered into an infinite boot loop. I thought it might have worked at first because the lock screen popped up, but when you unlock the phone the white htc logo is still there and the phone reboots after 10 seconds. So after making sure something went astronomically wrong with the update, I went into the boot loader and adb pushed twrp back onto the phone. the update somehow updated my hboot to 1.55 so my s-off is now s-on and I have no wawy to tell if the kernal for the phone is functioning. My only guess to this matter is that the boot sector for the phone is corrupt, but I tried to restore the stock twrp backup i have, and nothing. It boots, the lockscreen unlocks, but it still reboots. Now it was unlocked long enough for me to get into settings and see that it wiped ALL of my phones id info. All the meid, meie, carrier, everything is blank. So it seems that the phone crashed somewhere in the update where it was in the process of wiping things? I then tried to flash a completely different rom on there to see how that went. I first tried viperone 5.0.0 then the newer 5.8.0 and neither would boot (waited 1 hour each to make sure). Then I tried arhd 61 and again, no boot. So I'm not quite sure where to go from here. My stock backups aren't working at restoring, new rom flash isnt working, I can't take it into sprint to check on it since its rooted, I can't update the kernel due to s-on (correct me if im wrong). I'm smart enough to know when I'm out of my depth and I'm clearly trying to tread water in the middle of the ocean in this instance. So please if someone could give me a hand I would appreciate it so much.
Click to expand...
Click to collapse
Oh man.. this is rough. If you can get into fastboot, I would say try RUUing. That's what always fixed my problems haha
Sent from my HTCONE using Tapatalk
---------- Post added at 11:08 PM ---------- Previous post was at 11:04 PM ----------
I recommend this RUU
http://forum.xda-developers.com/showthread.php?t=2658910
Sent from my HTCONE using Tapatalk
Bairdog35 said:
Oh man.. this is rough. If you can get into fastboot, I would say try RUUing. That's what always fixed my problems haha
Sent from my HTCONE using Tapatalk
---------- Post added at 11:08 PM ---------- Previous post was at 11:04 PM ----------
I recommend this RUU
http://forum.xda-developers.com/showthread.php?t=2658910
Sent from my HTCONE using Tapatalk
Click to expand...
Click to collapse
I will Definitely check it out. I was hesitant to try an RUU because all the ones I was looking at were talking about flashing modded kernels and needing s-off and such. But I will definitly try it and update if it works.
Bairdog35 said:
Oh man.. this is rough. If you can get into fastboot, I would say try RUUing. That's what always fixed my problems haha
Sent from my HTCONE using Tapatalk
---------- Post added at 11:08 PM ---------- Previous post was at 11:04 PM ----------
I recommend this RUU
http://forum.xda-developers.com/showthread.php?t=2658910
Sent from my HTCONE using Tapatalk
Click to expand...
Click to collapse
Alright mate, I'm gunna need a mailing address to send my first born son to. You are a god send with that link. It worked perfectly
xanex18 said:
Alright mate, I'm gunna need a mailing address to send my first born son to. You are a god send with that link. It worked perfectly
Click to expand...
Click to collapse
I'm glad it worked ?
Sent from my HTCONE using Tapatalk
I hard bricked mine s3 mini (yes, yes, i know...) and it won't boot at all. I've bought usb jig, but didn't help to boot in download mode. What now? [emoji20]
DomagojR said:
I hard bricked mine s3 mini (yes, yes, i know...) and it won't boot at all. I've bought usb jig, but didn't help to boot in download mode. What now? [emoji20]
Click to expand...
Click to collapse
There's nothing else you could do - unless you have the equipment in order to JTAG it. Either claim warranty on it or search for repair stores nearby.
You think so? When I connect it to the pc, it keeps connecting and disconnecting, if that helps... There's nothing more to try?
DomagojR said:
I hard bricked mine s3 mini (yes, yes, i know...) and it won't boot at all. I've bought usb jig, but didn't help to boot in download mode. What now? [emoji20]
Click to expand...
Click to collapse
Give it back to your seller, they won't know that it's rooted and they would probably replace it. Don't bother trying to get it out of hard brick.
KoolKid98189 said:
Give it back to your seller, they won't know that it's rooted and they would probably replace it. Don't bother trying to get it out of hard brick.
Click to expand...
Click to collapse
Yeah, softbrick is easy to fix, but hardbrick means you've got a hard brick instead of a phone now xD Do what he said ^ and don't admit nothing, just say that suddenly it broke down
Haha and you both think that there is no chance that they will somehow see that custom binary and other things that avoid warranty?
DomagojR said:
Haha and you both think that there is no chance that they will somehow see that custom binary and other things that avoid warranty?
Click to expand...
Click to collapse
We have hope xD
So, there is a possibility?
DomagojR said:
So, there is a possibility?
Click to expand...
Click to collapse
Well, if the phone can't boot up and the guys aren't technicians, then yes, there is a pretty good chance noone will know what you've done to your phone!
DomagojR said:
Haha and you both think that there is no chance that they will somehow see that custom binary and other things that avoid warranty?
Click to expand...
Click to collapse
Well if they can't switch it on then they can't see the custom binary...?
---------- Post added at 07:58 PM ---------- Previous post was at 07:54 PM ----------
koragg97 said:
Yeah, softbrick is easy to fix, but hardbrick means you've got a hard brick instead of a phone now xD Do what he said ^ and don't admit nothing, just say that suddenly it broke down
Click to expand...
Click to collapse
Yeah, that happened with my S3 mini, it had semi hard brick... Well it could go into download mode and I flashed all kinds of stock ROMs, recoveries and params and it made no change whatsoever! How did I know this? I tried flashing stock recovery and when I booted into recovery, it just showed TeamWin splash screen for 1 second and shut off. So I determined that the eMMC chip is screwed up! I tried a repair shop but they gave up so I spoke to Amazon customer service saying that my phone just won't turn on so they gave me a free replacement (no quibbles) with a free complementary upgrade to first class. I just drained the battery by leaving it on download mode so they wouldn't easily found out! The contract of sales lies with the seller, not for you to wait a month for the manufacturer to fix it. Since then I haven't rooted it as I'm scared that it could brick again. That's why I wanted an official KitKat upgrade which Samsung don't give for bs reasons!
But what if they are able to fix it with jtag box or something?
KoolKid98189 said:
Well if they can't switch it on then they can't see the custom binary...?
---------- Post added at 07:58 PM ---------- Previous post was at 07:54 PM ----------
Since then I haven't rooted it as I'm scared that it could brick again. That's why I wanted an official KitKat upgrade which Samsung don't give for bs reasons!
Click to expand...
Click to collapse
You can just use VRoot. It's easy to achieve root with it After rooting and installing a custom recovery ALWAYS do a nandroid backup before trying to flash or modify ANYTHING! That's what I do and never spend more than 10 mins (the time required to restore my nandroid) with a bricked phone
koragg97 said:
You can just use VRoot. It's easy to achieve root with it After rooting and installing a custom recovery ALWAYS do a nandroid backup before trying to flash or modify ANYTHING! That's what I do and never spend more than 10 mins (the time required to restore my nandroid) with a bricked phone
Click to expand...
Click to collapse
But the thing is that I had KitKat by Maclaw for a while. Then one evening it was charging and it just died without warning. It was dead for one day and then it switched on but it just showed bootlogo and switched off. That's when I realised it was semi hard bricked.
KoolKid98189 said:
But the thing is that I had KitKat by Maclaw for a while. Then one evening it was charging and it just died without warning. It was dead for one day and then it switched on but it just showed bootlogo and switched off. Then when I realised it was semi hard bricked.
Click to expand...
Click to collapse
That's why I stick with stock-based custom ROMs, zero or very little or minor bugs. No problems with me so far
This also happened to me. Without warning. I have the same experience as the OP. I keep hearing the connecting/disconnecting sound on my laptop when I connect it to my laptop.
koragg97 said:
That's why I stick with stock-based custom ROMs, zero or very little or minor bugs. No problems with me so far
Click to expand...
Click to collapse
But then wouldn't I lose the warranty? And Maclaw's CM11 ROM was the best, I miss out on so many good features on stock and it's so much slower than CM11. I just don't want to end up having another bricked S3 mini though.
---------- Post added at 03:02 PM ---------- Previous post was at 03:01 PM ----------
hleotangco said:
This also happened to me. Without warning. I have the same experience as the OP. I keep hearing the connecting/disconnecting sound on my laptop when I connect it to my laptop.
Click to expand...
Click to collapse
Don't bother trying to revive it if it's hard bricked. Because they won't find out about the root if they can't turn it on.
KoolKid98189 said:
But then wouldn't I lose the warranty? And Maclaw's CM11 ROM was the best, I miss out on so many good features on stock and it's so much slower than CM11. I just don't want to end up having another bricked S3 mini though.
---------- Post added at 03:02 PM ---------- Previous post was at 03:01 PM ----------
Don't bother trying to revive it if it's hard bricked. Because they won't find out about the root if they can't turn it on.
Click to expand...
Click to collapse
thats the thing tho. my warranty just expired last month. now im thinking if i should buy a moto g. i just have to live without the sd card...
hleotangco said:
thats the thing tho. my warranty just expired last month. now im thinking if i should buy a moto g. i just have to live without the sd card...
Click to expand...
Click to collapse
Oh, void or just finished?
KoolKid98189 said:
Oh, void or just finished?
Click to expand...
Click to collapse
finished. I only have a year warranty for my phone. After it ended, I terminated my contract with my carrier cause it's more cost effective for me to just use pay-as-you-go sims...
Hey there everyone, here to report unfortunate news about my g4 has died all out. Was using it to navigate using maps to a job yesterday, when suddenly my phone reboots and gets in boot loop. I take off battery to boot up phone back on, but turns out it doesn't at all respond to turn on, I try the hard master reset buttons to then boot to twrp but not even that responds. Weird cuz I had 40 percent battery left, connected phone to my charger and three more and no response at all in boot up or even sign of life. What can I do?
I have the same problem, phone wont respond at all and it was doing a boot loop, now it just wont turn on or respond to charging/no led light, nothing.
What are my options?
Rooted/No Insurance.
ExhumedWolf said:
I have the same problem, phone wont respond at all and it was doing a boot loop, now it just wont turn on or respond to charging/no led light, nothing.
What are my options?
Rooted/No Insurance.
Click to expand...
Click to collapse
That's weird how this has happened when i was running completely stock rom 10n rooted. Sucks that my screen has a very thin hairline crack which T-Mobile told me that LG won't accept it for warranty since it has physical damage.
Is there a way to restore the phone to complete stock using download mode? I'm in the same boat and now need to research a solution before returning to T-Mobile. This happened to a friend, too.
In my case, I was playing Fallout Shelter, the phone froze, so I did a battery pull. Now it won't boot up. Sometimes I can get it to go as far as the "Android is upgrading screen, " but then it either freezes again or goes into a bootloop. Tried booting into TWRP, but it either won't, or it'll freeze while inside before I can attempt to restore a backup or anything.
partylikeaninjastar said:
Is there a way to restore the phone to complete stock using download mode? I'm in the same boat and now need to research a solution before returning to T-Mobile. This happened to a friend, too.
In my case, I was playing Fallout Shelter, the phone froze, so I did a battery pull. Now it won't boot up. Sometimes I can get it to go as far as the "Android is upgrading screen, " but then it either freezes again or goes into a bootloop. Tried booting into TWRP, but it either won't, or it'll freeze while inside before I can attempt to restore a backup or anything.
Click to expand...
Click to collapse
Tried to boot in download mode and haven't been able since this occured. Nothing at all works for me in booting up to anything through the buttons, hopefully you can get DL mode working so you can get your g4 working back to normal.
wadamean said:
Tried to boot in download mode and haven't been able since this occured. Nothing at all works for me in booting up to anything through the buttons, hopefully you can get DL mode working so you can get your g4 working back to normal.
Click to expand...
Click to collapse
When I tried, I was able to boot into download mode, I didn't have any KDZ or whatever downloaded already or the flash tool in order to actually do anything so it was pointless, but it appears to boot into DL mode with no issue. For all I know, though, even though it booted into DL mode, it could have been completely frozen and unresponsive.
I think I found a thread with instructions and a link to the KDZ I need to download. Going to give this a try when I get home from work in twelve hours. If that fail, it's off to T-Mobile I go....
I have the same issue. I was browsing G+ then the phone just froze and now I can't get it to boot up or get into twrp. It will only boot loop.
Edit 1: I got my phone to boot and did a factory reset but it just ended up freezing and rebooting just like before. I'm going to try and get into twrp and flash the 10n stock then go to t-mobile to try and get them to get me a new one. I have insurance but the phone just randomly died, no dropping, didn't get it wet, so I don't want to have to pay a deductible.
http://forum.xda-developers.com/g4/general/guide-lg-g4-stock-firmware-to-stock-kdz-t3107848
---------- Post added at 02:25 PM ---------- Previous post was at 02:23 PM ----------
That's to the lasted 10n version boot loader,DO NOT I REPEAT DO NOT FLASH THE BOOTLOADER TO A LOWER VERSION THEN YOU ALREADY HAVE! you will be beyond ****ed and not even lg can help you at that point..the bootladers have backwards protection to if you haven't updated to marshmallow flash the 10n bootloader( the most lasted bootloader for lp) and you should be fine.the lg flash tool should be included but be careful guys..I can't stress enough how important it is you flash the right BL..you will perma brick
mr turtle droid said:
http://forum.xda-developers.com/g4/general/guide-lg-g4-stock-firmware-to-stock-kdz-t3107848
---------- Post added at 02:25 PM ---------- Previous post was at 02:23 PM ----------
That's to the lasted 10n version boot loader,DO NOT I REPEAT DO NOT FLASH THE BOOTLOADER TO A LOWER VERSION THEN YOU ALREADY HAVE! you will be beyond ****ed and not even lg can help you at that point..the bootladers have backwards protection to if you haven't updated to marshmallow flash the 10n bootloader( the most lasted bootloader for lp) and you should be fine.the lg flash tool should be included but be careful guys..I can't stress enough how important it is you flash the right BL..you will perma brick
Click to expand...
Click to collapse
Thanks for the reminder. That's the thread I found and I also already made a mental note to flash the right image. My friend had this same problem and the person she tasked with fixing her phone flashed the wrong image and perma bricked her. Fortunately, T-Mobile still replaced her phone, though.
Sent from my LG-D851 using Tapatalk
mr turtle droid said:
http://forum.xda-developers.com/g4/general/guide-lg-g4-stock-firmware-to-stock-kdz-t3107848
---------- Post added at 02:25 PM ---------- Previous post was at 02:23 PM ----------
That's to the lasted 10n version boot loader,DO NOT I REPEAT DO NOT FLASH THE BOOTLOADER TO A LOWER VERSION THEN YOU ALREADY HAVE! you will be beyond ****ed and not even lg can help you at that point..the bootladers have backwards protection to if you haven't updated to marshmallow flash the 10n bootloader( the most lasted bootloader for lp) and you should be fine.the lg flash tool should be included but be careful guys..I can't stress enough how important it is you flash the right BL..you will perma brick
Click to expand...
Click to collapse
That's true and I have not flashed nothing at all and only remained all on 10n rom and bootloader and modem. Yet this still happened to me.
My phone lives!
partylikeaninjastar said:
My phone lives!
Click to expand...
Click to collapse
That's amazing news!!!!
Actually, I take it back. It stopped working after an hour and started doing the same thing. On my way to T-Mobile in a bit.
Sent from my LG-D851 using Tapatalk
partylikeaninjastar said:
My phone lives!
Click to expand...
Click to collapse
partylikeaninjastar said:
Actually, I take it back. It stopped working after an hour and started doing the same thing. On my way to T-Mobile in a bit.
Sent from my LG-D851 using Tapatalk
Click to expand...
Click to collapse
Let us know how it goes with T-Mobile. I was planning on getting my phone back to stock and then going to T-Mobile. I haven't had any luck bringing my phone back.
WillDeC said:
Let us know how it goes with T-Mobile. I was planning on getting my phone back to stock and then going to T-Mobile. I haven't had any luck bringing my phone back.
Click to expand...
Click to collapse
No hassle at all. Surprisingly. He just asked me what happened, then ordered my replacement to be delivered. Will have a new phone on Tuesday.
Sent from my LG-D851 using Tapatalk
WillDeC said:
Let us know how it goes with T-Mobile. I was planning on getting my phone back to stock and then going to T-Mobile. I haven't had any luck bringing my phone back.
Click to expand...
Click to collapse
I have great news everyone! Today I was cleaning my room. And just moved my g4 around onto my bed and then I see that the screen comes on saying I need to charge it. Which then I plug in and it charges now. I then wait a good while, get it to magically boot onto twrp. So excited and only option was to wipe all except the storages. I did, then flashed 10n rom again, not its back to life with no issues. Need to go to T-Mobile to connect it back on.
partylikeaninjastar said:
No hassle at all. Surprisingly. He just asked me what happened, then ordered my replacement to be delivered. Will have a new phone on Tuesday.
Sent from my LG-D851 using Tapatalk
Click to expand...
Click to collapse
Good to hear. I just want to try and get it to stock. Sometime I can get to boot twrp and don't want to have to deal with them questioning about if they try and factory reset it or something.
WillDeC said:
Good to hear. I just want to try and get it to stock. Sometime I can get to boot twrp and don't want to have to deal with them questioning about if they try and factory reset it or something.
Click to expand...
Click to collapse
Reason why this issue has occurred is most likely in my opinion because of xposed. There is versions that work and those that aren't so stable in certain devices. What I advise you to do is boot into twrp when you get the chance, wipe all except the storages. You will notice how stable the phone gets and won't be bootlooping, which is what I noticed. Then flash whatever rom you have. Boot up, skip all intro steps, download the zip to get it to stock so you get the replacement. Keep telling T-Mobile that maybe at the moment it seems stable but it does this and you have gotten so fed up with it and won't be leaving until a replacement takes place. Either warranty or at store.
wadamean said:
Reason why this issue has occurred is most likely in my opinion because of xposed. There is versions that work and those that aren't so stable in certain devices. What I advise you to do is boot into twrp when you get the chance, wipe all except the storages. You will notice how stable the phone gets and won't be bootlooping, which is what I noticed. Then flash whatever rom you have. Boot up, skip all intro steps, download the zip to get it to stock so you get the replacement. Keep telling T-Mobile that maybe at the moment it seems stable but it does this and you have gotten so fed up with it and won't be leaving until a replacement takes place. Either warranty or at store.
Click to expand...
Click to collapse
I've never put xposed on this phone. I put twrp, rooted and was using a debloated rom. I had actually removed root so I could use android pay. It was working fine then just froze and constant reboots and freezing. I've only been able to get into twrp once without it freezing and rebooting,
WillDeC said:
I've never put xposed on this phone. I put twrp, rooted and was using a debloated rom. I had actually removed root so I could use android pay. It was working fine then just froze and constant reboots and freezing. I've only been able to get into twrp once without it freezing and rebooting,
Click to expand...
Click to collapse
You shouldn't have removed root and just used root cloak so that android pay thinks your unrooted. That's what I have been using. Because debloated roms always come injected with root and at times it becomes their core use within to function. When you get the chance to boot into twrp. Wipe all except storages and then reflash.
I tried flashing the marshmallow update that was just released (a very, very idiotic move) I flashed it the first time and all seemed well; everything flashed with no errors, and it rebooted. Well, upon reboot, I get the dreaded Factory Reset Status 2. Okay, no big deal, I just realized that I forgot to select "BOARD DL". I got to try to flash again, this time selected BOARD. Now, I get a dodownloaderror at 18s. Every time. I have tried everything, battery pulls, reflashing, I even tried reflashing ZV6 (this is probably what dug my grave). Nothing. I can still boot to recovery and DL mode, but nothing is working. I didn't put a stock img on my internal storage, so sideloading from recovery isn't an option either.
I am such an idiot. Now I have a paperweight, and it is going to cost me several hundred, if not a thousand, dollars to end my contract on the brick and then go out and buy a new phone.
Does anyone have an methods that I haven't tried?
Did I mention that I am a huge idiot?
ironbesterer said:
I tried flashing the marshmallow update that was just released (a very, very idiotic move) I flashed it the first time and all seemed well; everything flashed with no errors, and it rebooted. Well, upon reboot, I get the dreaded Factory Reset Status 2. Okay, no big deal, I just realized that I forgot to select "BOARD DL". I got to try to flash again, this time selected BOARD. Now, I get a dodownloaderror at 18s. Every time. I have tried everything, battery pulls, reflashing, I even tried reflashing ZV6 (this is probably what dug my grave). Nothing. I can still boot to recovery and DL mode, but nothing is working. I didn't put a stock img on my internal storage, so sideloading from recovery isn't an option either.
I am such an idiot. Now I have a paperweight, and it is going to cost me several hundred, if not a thousand, dollars to end my contract on the brick and then go out and buy a new phone.
Does anyone have an methods that I haven't tried?
Did I mention that I am a huge idiot?
Click to expand...
Click to collapse
Same here..
Why are you both flashing MM? Is there an official image to flash?
EmSeeMAC said:
Why are you both flashing MM? Is there an official image to flash?
Click to expand...
Click to collapse
That's why I'm an idiot. It's not an official .TOT.
ironbesterer said:
That's why I'm an idiot. It's not an official .TOT.
Click to expand...
Click to collapse
I fixed mines using LG UP
http://forum.xda-developers.com/sprint-g4/development/howto-downgrade-to-zv6-upgrade-to-t3265976
This should help you fix the dreaded 2
If you can boot into download mode, flash the ROM for your phone on sammobile
Just say you installed an update and it bricked your phone if it's still under warranty. I dunno how many times I botched my G Flex 2 and LG replaced it (ATT model).
Why is it gonna cost you $1000.00. At worst you just buy another phone.
But the cheapest is to add TEP and bring it in. You might want to brick it hard enough that they cannot see that it was every rooted though
He fixed it
ironbesterer said:
I tried flashing the marshmallow update that was just released (a very, very idiotic move) I flashed it the first time and all seemed well; everything flashed with no errors, and it rebooted. Well, upon reboot, I get the dreaded Factory Reset Status 2. Okay, no big deal, I just realized that I forgot to select "BOARD DL". I got to try to flash again, this time selected BOARD. Now, I get a dodownloaderror at 18s. Every time. I have tried everything, battery pulls, reflashing, I even tried reflashing ZV6 (this is probably what dug my grave). Nothing. I can still boot to recovery and DL mode, but nothing is working. I didn't put a stock img on my internal storage, so sideloading from recovery isn't an option either.
I am such an idiot. Now I have a paperweight, and it is going to cost me several hundred, if not a thousand, dollars to end my contract on the brick and then go out and buy a new phone.
Does anyone have an methods that I haven't tried?
Did I mention that I am a huge idiot?
Click to expand...
Click to collapse
Okay, if you can get to download mode, then use the 'send_command' batch file to adb push a stock image to /dev/media/0/ then dd it.
---------- Post added at 05:55 PM ---------- Previous post was at 05:52 PM ----------
mswlogo said:
Why is it gonna cost you $1000.00. At worst you just buy another phone.
But the cheapest is to add TEP and bring it in. You might want to brick it hard enough that they cannot see that it was every rooted though
Click to expand...
Click to collapse
Hahaha this.
With a bootloader that's totally locked down you can just say that you accepted an OTA and your battery died while it was flashing and now your phone is screwed.
agentfusion said:
Okay, if you can get to download mode, then use the 'send_command' batch file to adb push a stock image to /dev/media/0/ then dd it.
---------- Post added at 05:55 PM ---------- Previous post was at 05:52 PM ----------
Hahaha this.
With a bootloader that's totally locked down you can just say that you accepted an OTA and your battery died while it was flashing and now your phone is screwed.
Click to expand...
Click to collapse
It would be close to a thousand to pay off my current device (around $300 owed on it) and then go out and buy a new one. But, with autoprime and awesomeslayerg's help, I got my phone back to normal.
I'm glad I seen this before I tried that