Database Users

Cannot update firmware on stock Sprint Hero

Please help out my coworker has a stock Hero on sprint and we are unable to update the firmware. I was able to update mine, our demo and one other co-worker's phone but on hers, every time I actually go into the firmware update it states no updates available. Sadly we work for a sprint store and hers is the only one giving us an error. I've already gone to the point of wiping the device to restore to factory but with no avail. Aside from having her swap out the phone at our repair center, I wanted to see if anyone has had the same problem and was able to get passed it. I saw a couple of posts stating to use the RUU utility, but on a stock rom that we already "RTN'd" I don't know how that would help. Any help would be greatly appreciated.

I've seen something similar. A coworker of mine just got a hero last week (after the MR release) and her phone shows the older software version but it will not recognize a firmware update is needed. I checked the phone's awake time and it was low, indicating the messaging app was not keeping the phone awake or draining the battery so I assumed it must not need the MR update even though it shows the old software version.

A couple others have metioned this... For some reason, some phones shipped with older firmware, version 1.22.651.1 instead of 1.29.651.1. Doing a hard reset on the 1.22 version wouldn't help, but updating the firmware to the 1.29 should. After that, check for the official MR.
You can find the file over here:
ftp://xda:[email protected]_Hero_C_Sprint_1.29.651.1_signed_release.exe
http://forum.xda-developers.com/showthread.php?t=559622

the guy at the sprint store (3rd party store) where i got mine from , his hero will not update or even flash back to the stock sprint ruu everytime it downloads the update and goes to apply it it shuts the phone down and thats it no reboot have to pull the batt to get it to power back on again

I had the same problem. I got my Hero on the first day it came out. Every time I tried to download the firmware update it would say no update available. Took it to the Sprint store and no luck either. They finally swapped out my original Hero for a new one and I was past my 30 days.

[Q] Bricked verizon lg g2 by install software update, don't know what to do

Hi guys, I got my LG G2 a few months ago and it was my first android phone. Since I always jailbroke my apple devices I decided to root my lg g2. Everything worked fine until last week when I was prompted to install a software update. I thought this might mess up the phone since it was rooted so I postponed it until later in the day to give me time to research, but I forgot to postpone the update again and it went through at the scheduled time. Now when I turn my phone on, the lg logo is displayed, and then I get a boot certification verify error. I don't really know what that means but I can't do anything, no recovery, no download mode. I started to follow this tutorial but am stuck at what files to download. I do not know if I have the 10b, 11a, or 12b variant, and I can't find a way to check it without turning the phone on, which I can't do. I'm really lost at what to do at this point, I can't follow the only guide that might fix my phone. Is there another way to solve this issue or find which variant I have? Would verizon accept it back to fix or replace it since it's been rooted? I've read some people saying they unrooted their phone and then returned it to the carrier, is it possible to do that in my situation? I really need some help guys.

TBH: I would call Verizon, and tell them the phone was bricked by the update- hope they don't notice it was rooted when they warranty it. Problem is, if they do you get charged full amount for phone. I'd consider if you have insurance to just claim it on insurance.

try download lg support tool from lg website http://www.lg.com/uk/support/software-manuals
plug the device and wait for the software to recognize ur version.

I downloaded and installed it, but it won't recognize by phone. I have installed the drivers for it

ok.
try to follow this guide http://forum.xda-developers.com/showthread.php?t=2681089
and the files download from here:http://downloads.codefi.re/autoprime/LG/LG_G2/VS980/Stock_Firmware/10B_Partitions
lets try this virsion and see what happend..
download the 10B zip file and the dll file too http://downloads.codefi.re/autoprime/LG/LG_G2/VS980/Stock_Firmware

now it doesn't boot at all, not even to the lg logo. Additionally the partitions don't show up in ubuntu any more. I guess i'm completely screwed now?

Stock SM-N9005 Restarting 4-5 times a day - need some advice

Hi,
I have been having a ongoing problem with my Galaxy Note 3 N9005 in where after the 5.0 upgrade (stock over air) it has been restarting pretty much 4-5 times during the day, and a number of times while even just sitting on the desk doing nothing.
Since I am still on contract with my supplier in NZ, I took the phone back to get repaired, in which Samsung sent it back to state "Software corruption, reloaded software".
I didn't believe them, but hoped it was correct - but sure enough the same thing happened. So I once again took it back, where they have once again told me the same thing. It is now the third time I have done this, with Samsung saying the same thing!
Now I am at wits end, and have asked for replacement, but I am being told "It is due to your google account being corrupt, and it is causing software corruption....." *sigh*
So now not only is Samsung just not helping, they are blaming my Google accounts for causing the issue. Which btw - I didn't setup the last time, and still it restarted - but they are ignoring that fact!
Anyway - the advice I want to get is has anyone else had the same issue with the Galaxy Note 3 after upgrading? I know there is no way to rollback 5.0 to old version, but did anyone fix the issue by Root and then adding another ROM (I don't want to root this phone, but to be honest I also can't afford right now to replace so I am looking at options)
Right now I am facing a ongoing battle with Samsung and my provider to replace the phone, but they are fighting it a lot and to be honest I have lost my patience so I am thinking to just drop them, root/flash new Rom, and then go to another provider - and probably never buy Samsung again when I can finally upgrade.
(used to love Samsung products but this behavior I have had is certainly making me think twice before I touch them again)

Since they refuse to accept warranty you can try to flash twrp. Then clear everthing(system/caches). Then back to stock with odin. There might be leftover of corrupted files that could cause reboot.
But later they have a better reason not to accept your phone, knox tripped.
And you can actually downgrade to 4.4.2. Just flash firmware of the same csc to be safe.
Sent from my SM-N920C

Do you have memory card installed? if so then scan you memory card for possible viruses.

Actually I have this issue too before.
Even if I left it lying on the table, it can restart by itself.
I tried to update to latest PB1 rom, the update failed, the phone restart while ODIN updating.
So I use Kies recovery and got it working again.
After that, i tried again update to PB1 rom using ODIN. and now no issues at all.
I dont know which one did the trick whether update to PB1 or KIES recovery.
Goldendawn said:
Hi,
I have been having a ongoing problem with my Galaxy Note 3 N9005 in where after the 5.0 upgrade (stock over air) it has been restarting pretty much 4-5 times during the day, and a number of times while even just sitting on the desk doing nothing.
Since I am still on contract with my supplier in NZ, I took the phone back to get repaired, in which Samsung sent it back to state "Software corruption, reloaded software".
I didn't believe them, but hoped it was correct - but sure enough the same thing happened. So I once again took it back, where they have once again told me the same thing. It is now the third time I have done this, with Samsung saying the same thing!
Now I am at wits end, and have asked for replacement, but I am being told "It is due to your google account being corrupt, and it is causing software corruption....." *sigh*
So now not only is Samsung just not helping, they are blaming my Google accounts for causing the issue. Which btw - I didn't setup the last time, and still it restarted - but they are ignoring that fact!
Anyway - the advice I want to get is has anyone else had the same issue with the Galaxy Note 3 after upgrading? I know there is no way to rollback 5.0 to old version, but did anyone fix the issue by Root and then adding another ROM (I don't want to root this phone, but to be honest I also can't afford right now to replace so I am looking at options)
Right now I am facing a ongoing battle with Samsung and my provider to replace the phone, but they are fighting it a lot and to be honest I have lost my patience so I am thinking to just drop them, root/flash new Rom, and then go to another provider - and probably never buy Samsung again when I can finally upgrade.
(used to love Samsung products but this behavior I have had is certainly making me think twice before I touch them again)
Click to expand...
Click to collapse

Munawar Mehmood said:
Do you have memory card installed? if so then scan you memory card for possible viruses.
Click to expand...
Click to collapse
Thanks - but no I don't - these are the first things I did when it started happening.
When it started happening I did factory reset, removing memory card, factory reset again, didn't restore backup from google... etc etc - so the general admin tech stuff.
Because under warranty (2 year contract) I didn't want to do anything more so sent to provider to get dealt with (into my 22 months of 24 months). For the last 4 months it has been to them a number of times for the same thing.
Now each time they send it back they claim "software corrupt" and that there is no hardware issue. So doing a software root and mod change for me is a hope - and probably not a good one - that the Stock 5.0 is the problem on this phone. And only going down this road because I am coming out of the warranty and right now I have a phone I can't really use, and damn Samsung won't support it or fix it (which is really all I want them to do!!) sigh

syamsoul said:
Actually I have this issue too before.
So I use Kies recovery and got it working again.
Click to expand...
Click to collapse
Thanks for this information, because in fact you are not the first time I have read this but I am not sure what the Kies recovery is - is there some instructions you have because maybe that is what should try, because I have seen other people on Google state this has helped them with restarting, but that was usually after Mod fix. Maybe there is something in the 5.0 update on GN3 that might cause this?

Rosli59564 said:
Since they refuse to accept warranty you can try to flash twrp. Then clear everthing(system/caches). Then back to stock with odin. There might be leftover of corrupted files that could cause reboot.
But later they have a better reason not to accept your phone, knox tripped.
And you can actually downgrade to 4.4.2. Just flash firmware of the same csc to be safe.
Sent from my SM-N920C
Click to expand...
Click to collapse
Thanks I didn't think from what I was reading that you could backwards - in fact Samsung have just down right refused, which is all I have asked them to do in the last two times - "Just flash back to the version that was on there last 4.4.2. because that didn't cause any issues!" However, they are stating very firmly that you can not rollback or re-flash back to a previous version.
Is there any instructions which are for the 9005? I have seen for the 900 but the instructions state very clearly you can't use them for 9005.

Goldendawn said:
Thanks I didn't think from what I was reading that you could backwards - in fact Samsung have just down right refused, which is all I have asked them to do in the last two times - "Just flash back to the version that was on there last 4.4.2. because that didn't cause any issues!" However, they are stating very firmly that you can not rollback or re-flash back to a previous version.
Is there any instructions which are for the 9005? I have seen for the 900 but the instructions state very clearly you can't use them for 9005.
Click to expand...
Click to collapse
Just flash the firmware with odin. Factory reset in recovery after it's done. That's it. There are a lots of threads about going down such this:
http://forum.xda-developers.com/gal...o-downgrade-lollipop-to-kitkat-t2990262/page2
I suggest you read through before you go further. They are mixed results. Some successful. Some did not. That is why it is better to flash the same csc firmware.
I even able to downgrade my S6 from 6.01 to 5.1.1 without issue but of course it's different phone.
Sent from my SM-N920C
---------- Post added at 08:38 PM ---------- Previous post was at 08:15 PM ----------
I sent you a PM.
Sent from my SM-N920C

Sigh.. Bootloop problem out of nowhere

My Nexus 6p was definitely one of the batches that should not have passed QC... soft power button, phone shutting down with plenty of battery left and today all of a sudden, while I was using the phone, phone restarts and get stuck in a bootloop...
Phone is not rooted and the bootloader locked... its out of warranty but I called google support anyway and they directed me to Huawei .. luckily, they will fix it for free..
IF you are having the same problem, call google up and hold them accountable for this bull****

Same deal here but i bought my 6p from best buy along with geek squad protection plan. Rather than send me another 64gb 6p, they've given me a gift card for the price at the time of purchase. At the moment only 32gb versions are available on best buy dot com. I'm not totally opposed to the 32gb version but I'm not excited about it. It took 3 days from the time I submitted my RMA request to get an email telling me this gift card b.s.
I haven't returned anything yet. Not sure what to do. I really liked that phone.

i had my first bootloop today. i just did a force restart and it booted normal. should i be concerned ?
ps.
phone is only 2 weeks old, and with stock ota update 7.1.1 (rooted)

puddi said:
i had my first bootloop today. i just did a force restart and it booted normal. should i be concerned ?
ps. phone is only 2 weeks old, and with stock ota update 7.1.1 (rooted)
Click to expand...
Click to collapse
I wouldn't be. Sounds like you are unlocked and rooted. Just keep a good backup on your PC (including EFS) and enjoy your phone.

puddi said:
i had my first bootloop today. i just did a force restart and it booted normal. should i be concerned ?
ps.
phone is only 2 weeks old, and with stock ota update 7.1.1 (rooted)
Click to expand...
Click to collapse
Rooted or not and having a backup or not won't fix this unfixable bootloop. I have one in my possession I'm trying to restore and nothings working. Random reboots a week prior to it going into this bootloop. I've done a bunch of research and it's not good.

thesparky007 said:
My Nexus 6p was definitely one of the batches that should not have passed QC... soft power button, phone shutting down with plenty of battery left and today all of a sudden, while I was using the phone, phone restarts and get stuck in a bootloop...
Phone is not rooted and the bootloader locked... its out of warranty but I called google support anyway and they directed me to Huawei .. luckily, they will fix it for free..
IF you are having the same problem, call google up and hold them accountable for this bull****
Click to expand...
Click to collapse
Do you have the Huawei contact info? I have tried to go through the online support but I have yet to hear anything in a number of days. Same problem here, bootloop out of no where.

galakanokis said:
Do you have the Huawei contact info? I have tried to go through the online support but I have yet to hear anything in a number of days. Same problem here, bootloop out of no where.
Click to expand...
Click to collapse
Call them here 1-888-5HUAWEI

thesparky007 said:
Call them here 1-888-5HUAWEI
Click to expand...
Click to collapse
Thanks, much appreciated.

I just went through the same thing. Waiting on the RMA box to arrive so it can be sent back.
Sent from my Nexus 6 using XDA-Developers Legacy app

Same here...happened just this morning. I can't get into recovery and I can ONLY boot into bootloader. I am on full stock with a locked bootloader running 7.1.1. I got off the phone with a Huawei rep and she stated it could be due to a Google update and that they will try and downgrade it on their end. Strange cause I was already running the latest 7.1.1 (unless a new update was released his morning).
Here's what I tried to no avail:
-unlocked bootloader and tried to flash stock rom/recovery
-tried flashing custom recovery (twrp)
-tried booting into temp customer recovery (twrp)
-tried flashing 7.0 stock
I have re-locked the bootloader and will have to send it in. What a real bummer, I have managed to get out of a softbrick (unless this device is truly bricked ???) on many, many device since the T-Mobile G1, but I am at wits end with this device.

Going through the RMA process now, thanks again for the number.
I have heard it mentioned that flashing back to 6.0.1 might work, has anyone tried? I did flash all the way back to 7.0 with no luck.

tried flashing back to 6, 6.01 and 7.0 but it still persists. get it exchanged or repaired

It's now several phones a day... At what point does either Huawei or Google fess up to root cause? The one question I have is are all of these hard bricks on phones running nougat??
Sent from my Nexus 6 using XDA-Developers Legacy app

uzi132 said:
Same here...happened just this morning. I can't get into recovery and I can ONLY boot into bootloader. I am on full stock with a locked bootloader running 7.1.1. I got off the phone with a Huawei rep and she stated it could be due to a Google update and that they will try and downgrade it on their end. Strange cause I was already running the latest 7.1.1 (unless a new update was released his morning).
Here's what I tried to no avail:
-unlocked bootloader and tried to flash stock rom/recovery
-tried flashing custom recovery (twrp)
-tried booting into temp customer recovery (twrp)
-tried flashing 7.0 stock
I have re-locked the bootloader and will have to send it in. What a real bummer, I have managed to get out of a softbrick (unless this device is truly bricked ???) on many, many device since the T-Mobile G1, but I am at wits end with this device.
Click to expand...
Click to collapse
You aren't alone obviously. These phones seem to be little time bombs where the boot loop issue is concerned. Mine goes into bootloops every time I flash an update or new ROM or attempt to restore a backup. I expect to hardbrick this phone at some point. It just hasn't happened yet.

Completely forgot about this thread. Huawei swapped out my motherboard with a 128 Gb (I had sent a 64 Gb). I actually quite happy my phone bricked itself. Haha

My 6p started rebooting last night and no matter what I did, couldn't get it to boot. Only bl mode worked. This thing has been one problem after another, so I went and got an iPhone this morning. Maybe one day Google will finally start making products that last more than one year, but hasn't happened yet and I'm tired of it.

andrewnelson23 said:
My 6p started rebooting last night and no matter what I did, couldn't get it to boot. Only bl mode worked. This thing has been one problem after another, so I went and got an iPhone this morning. Maybe one day Google will finally start making products that last more than one year, but hasn't happened yet and I'm tired of it.
Click to expand...
Click to collapse
On the same boat. Mine's stuck on bootloop, no recovery. 1 year is pretty good considering I've only had the device for 3 months...

Nexus 6p here in the UK, Got the OTA update yesterday and it caused crashes immediately. Had two crashes when it immediately rebooted and seemed ok. A third one soon followed and got stuck in a boot loop, a few minutes after it fixed it self and seemingly working fine. An hour later i was playing a game and it just locked, screenfroze and a buzzing noise from the speakers before going into a boot loop. Left it for a few hours while at the cinema and nothing.
Bought directly from Google and still under warranty. Interestingly though, i bought my 6p in March 2016, I then had to RMA it a few months later as the USB C port randomly broke I will be doing my second RMA in less than a year. When checking my IMEI the google support operative actually stated I was under warranty till August 2018. So a 30 month warranty. Got a new one coming out so if anyone develops this problem give them a ring.

New phone received, sent old one off. Checked it just before i did, still stuck in boot loop.

Narom88 said:
New phone received, sent old one off. Checked it just before i did, still stuck in boot loop.
Click to expand...
Click to collapse
That's way too common with this phone. Thinking about moving on to something else.

Remove the latest (broken) OTA package from the SM-G928V

Hey all,
I'm trying to get my brother's Verizon S6 Edge+ out of a bootloop due to the lastest OTA gone bad.
My thinking is if I could find that OTA somewhere online, I could ODIN it in, and maybe clear it the problem. I don't know if that'll work, but I can't test my theory because I can't find the OTA for download anywhere.
Smart Switch doesn't work because even though I can get into Download Mode and run Smart Switch's Emergency Recovery all I want, I enter the model number SM-G928V and it asks for the S/N next. No matter what I try, nothing works. I've gone through the logs, pulled serial number from the build.prop. I've tried everything on the original packaging. I've tried the IMEI and all the barcodes right before entering Download Mode - just no S/N registers.
I can reflash the old firmware, PJ3, on there via ODIN, and each time I reflash it tries to install the OTA again. It runs through the update up to 32% and then I get a droid guy on his back with a yellow triangle - every. single. time.
I don't understand where the heck this OTA is stored and how the hell I can zero it out or remove it. I've tried popping in a new PIT, repartitioning, etc. Hell, I've tried a NAND RE-WRITE (against everyone's cries this is a terrible idea).
Does anyone have the very latest G928VVRS3BPL3 that was pushed Dec 29, 2016 to VZW S6 Edge+ devices? I'm even willing to PayPal for a good copy that will ODIN into the VZW S6 Edge+...
Alternatively, if you don't have a copy of PL3, do you know of anyway I could ADB my way into wiping the corrupt PL3 patch away? I can't seem to ADB right now, but maybe you know a trick I don't? I'm thinking I could perhaps zero out the instructions that initiate the patch at launch or something? If I can simply boot up - fantastic, but I'm in this infinite boot loop of installing PL3 to 24% and going belly-up.
I'm almost embarrassed to say I PAID for a copy of PJ3... but I can't find this latest Dec 1st security update patch anywhere on the web.
The phone is out of warranty. Contrary to Verizon store morons (sorry!), my brother didn't try to root the phone. He doesn't know how to do any of that stuff. The OTA is corrupt - plain and simple. Knox isn't even tripped. They accused him of trying to root the thing - heh.
Since the phone is out of warranty, no one will fix it for him. I'm his only hope, and I'm not much of a hope right now.
You're MY only hope.
This is a great phone, too. I feel bad for the guy. He woke up to his phone dead one morning. That's it.