My phone have message failed to boot 0x1000 Entering NVFLASH RECOVERY MODE
I can use Factory Cable in NVFLASH RECOVERY MODE after blank screen
My computer found connection to atrix but I can't flash bootloader to atrix
I found message "Nvflash started rcm version 0X4 Command send failed (usb write failed)"
Help me pls
You should really check the date on your PC...
shoman24v said:
You should really check the date on your PC...
Click to expand...
Click to collapse
it is fine if he is in Thiland.
And to OP, sorry I have no idea, maybe some one will be able to help, as far as I know, a hard brick is game over.
aj009 said:
My phone have message failed to boot 0x1000 Entering NVFLASH RECOVERY MODE
I can use Factory Cable in NVFLASH RECOVERY MODE after blank screen
My computer found connection to atrix but I can't flash bootloader to atrix
I found message "Nvflash started rcm version 0X4 Command send failed (usb write failed)"
Help me pls
Click to expand...
Click to collapse
You don't have the SBK so you can not repair your phone. Send it in for service is all you can do with out an SBK, the error you receive is because you did not enter a correct SBK so it is terminating the connection and preventing flash to the phone
Tao_Man said:
it is fine if he is in Thiland.
Click to expand...
Click to collapse
so in thailand, they are already 543 years in the future?
i figured since this is a non-dev QUESTION in the dev section, i see no harm in going off topic.
aj009 said:
My phone have message failed to boot 0x1000 Entering NVFLASH RECOVERY MODE
I can use Factory Cable in NVFLASH RECOVERY MODE after blank screen
My computer found connection to atrix but I can't flash bootloader to atrix
I found message "Nvflash started rcm version 0X4 Command send failed (usb write failed)"
Help me pls
Click to expand...
Click to collapse
Sorry, if you're only option is NVFLASH ie (no fastboot) then it's not fixable. Try your luck with motorola warranty or spend a few hundred on a new phone.
Pirateghost said:
so in thailand, they are already 543 years in the future?
i figured since this is a non-dev QUESTION in the dev section, i see no harm in going off topic.
Click to expand...
Click to collapse
Well to go further off topic, they did not go forward they went backwards and started their calendar 543 years before ours.
Buddha not Jesus, if you follow.
Pretty cool that next year will be 2555, we will have to wait till 2111 for a triple digit again, of course we did just have 2000... Ok sorry...no more off topic
Wow, guys really? This is completely the wrong forum. There should be no reason people should be responding anymore. Thread should be closed.
kshiuan said:
Wow, guys really? This is completely the wrong forum. There should be no reason people should be responding anymore. Thread should be closed.
Click to expand...
Click to collapse
+100000000
thank you very much
aj009 said:
My phone have message failed to boot 0x1000 Entering NVFLASH RECOVERY MODE
I can use Factory Cable in NVFLASH RECOVERY MODE after blank screen
My computer found connection to atrix but I can't flash bootloader to atrix
I found message "Nvflash started rcm version 0X4 Command send failed (usb write failed)"
Help me pls
Click to expand...
Click to collapse
I am in the same situation...if you get any new information, please post here.
I tried like you, all the possibilities to relive my Atrix but without success.
I'm sure that it will pass this 0x4 error the problem will be solved.
Thanks in advance.
check these 2 threads out
http://forum.xda-developers.com/showthread.php?t=1160408
http://forum.xda-developers.com/showthread.php?t=1165154
and that whole date thing is probly for a cracked copy of windows to get passed the 30day grace period. set date in the future prior to install then set back after you install.
Nice job at resurrecting a 2 month old thread.
Once again - HARD BRICKS CANNOT BE FIXED. Send your phone to Motorola.
Actually you CAN fix a hard brick. Here's how. Turn OFF your phone. Throw it down the stairs. Call Motorola (or your carriers insurance company) and tell them your phone is broken. Tell them it looks as if someone threw it down the stairs. Send it to them, they send you a new phone.
edit: yes this is a joke but I thought I'd put this edit in just to say, in all seriousness, that insurance fraud or any other kind of nasty business is of course frowned upon and I im in no way supporting it nor is XDA or its subsidiaries.
Title is very misleading
Sent from my MB860 using xda premium
Phalanx7621 said:
Actually you CAN fix a hard brick. Here's how. Turn OFF your phone. Throw it down the stairs. Call Motorola (or your carriers insurance company) and tell them your phone is broken. Tell them it looks as if someone threw it down the stairs. Send it to them, they send you a new phone.
edit: yes this is a joke but I thought I'd put this edit in just to say, in all seriousness, that insurance fraud or any other kind of nasty business is of course frowned upon and I im in no way supporting it nor is XDA or its subsidiaries.
Click to expand...
Click to collapse
Holy moly! This works. Motorola sent me a brand new BMW as a replacement device for my broken Atrix.
Sent from my MB860 using XDA App
Here's me in the company
"failed to boot 0x1000
Entering NVFLASH RECOVERY MODE
Which procedure can wake Atrix 4G AT & T
I made Cable Factory
007nikica said:
Here's me in the company
"failed to boot 0x1000
Entering NVFLASH RECOVERY MODE
Which procedure can wake Atrix 4G AT & T
I made Cable Factory
Click to expand...
Click to collapse
You can't. It's called a brick for a reason. Once you go brick, you never go back.
Well...If you know someone from Motorola then ask for the sbk value and share it here.
On the next day you'll know what to do and you'll have a working ATRIX again.
gabriel612 said:
I am in the same situation...if you get any new information, please post here.
I tried like you, all the possibilities to relive my Atrix but without success.
I'm sure that it will pass this 0x4 error the problem will be solved.
Thanks in advance.
Click to expand...
Click to collapse
Same here, if anybody ever finds a solution please share, there are still a lot o broken hearts over this...
---------- Post added at 09:59 PM ---------- Previous post was at 09:53 PM ----------
xploited said:
Nice job at resurrecting a 2 month old thread.
Once again - HARD BRICKS CANNOT BE FIXED. Send your phone to Motorola.
Click to expand...
Click to collapse
A lot of people still have this problem and not everybody is able to send the phone to Motorola for various reasons. And if it bothers you so that people seek help in such situation you missed the point of this forums.
Related
I know there is threads about this, but I am having troubles, I will be willing to donate $20 to anyone who can help me. I am hoping it will be relatively easy............. I shouldn't have said that.
I loaded a bad framework-res.apk on my phone, and now it won't boot.
I have read DG's thread on recovering from the brick, but I can't figure out how to make it work.
In order to get the framework loaded I used root explorer to copy it over, because I couldn't get ADB to push the file. (I know, if I couldn't get ADB to work why would I muck with it....)
Now the first step in his guide is to boot into fastboot and wait for adb to work, then use superoneclick and hit 'shell root'
well, I can load into fastboot, but adb consistently says "error: device not found" or it doesn't list anything when I check devices. The troubles I was having before with adb were with pushing files, I could still see the device and pull files.
When I did the superoneclick step it ended up freezing the program, and I am not sure what is supposed to happen with fastboot but all it said was starting fastboot protocol support then did nothing.
I would be very grateful to anyone who can help me with this problem, I do have a backup framework on my computer and on the external sd card in the phone.
One thing I should note is that I did originally boot into the recovery mode, but all i did from there was reboot the phone (and go into fastboot mode).
Please help me! I have learned my lesson.
does the phone turn on
Do you have USB debugging enabled?
If you do, its possible to use adb by selecting Early USB Enumeration from boot menu. If not, you'll need to reflash using an SBF.
Come to my gtalk id texasdude11 and I'll help you out on chat.
Sent from my MB860 using Tapatalk
brian2220 said:
does the phone turn on
Click to expand...
Click to collapse
from what i gather, it turns on, but won't fully boot into android.
by that token, early USB enumeration will allow ADB to work on the phone usually, but in this case i believe debugging was turned off before his device was bricked. so, he can't boot into full android UI, and also can't use ADB to push the restore files because debugging is off.
i've seen this problem with one person before, but i couldn't find a way to force debugging on without going into the UI, if someone can chime in with a way to turn debugging on without initial ADB access, or UI then this problem is solved and more than one person is helped.
Although - he can just reflash if he's on AT&T, if he's on Bell then he's SOL
brian2220 said:
does the phone turn on
Click to expand...
Click to collapse
Sorry, I obviously suck at giving info.
The phone boots but not past the moto screen, I get the flashing red lights and it reboots. I can get into recovery and fastboot (though I suspect fast boot isn't work right since it freezes almost instantly), I also cant see the device in adb while trying fast boot (or anything else for that matter). I could before it bricked.
raybond25 said:
from what i gather, it turns on, but won't fully boot into android.
by that token, early USB enumeration will allow ADB to work on the phone usually, but in this case i believe debugging was turned off before his device was bricked. so, he can't boot into full android UI, and also can't use ADB to push the restore files because debugging is off.
i've seen this problem with one person before, but i couldn't find a way to force debugging on without going into the UI, if someone can chime in with a way to turn debugging on without initial ADB access, or UI then this problem is solved and more than one person is helped.
Click to expand...
Click to collapse
I think debugging was on, but I was also in USB data mode (the one above none). And yes, I am the poor Bell SOL'er.
toughbax said:
Sorry, I obviously suck at giving info.
The phone boots but not past the moto screen, I get the flashing red lights and it reboots. I can get into recovery and fastboot (though I suspect fast boot isn't work right since it freezes almost instantly), I also cant see the device in adb while trying fast boot (or anything else for that matter). I could before it bricked.
Click to expand...
Click to collapse
hold the volume up and the power button together and see if u can get into RSD engineering screen
and just follow this and flash everything over
http://forum.xda-developers.com/showthread.php?t=991072
Id download RSD 5 and one of the sbf files 1.26 or 1.52 and boot phone into rsd(power button+volume up) and flash the sbf
lsxrx7 said:
hold the volume up and the power button together and see if u can get into RSD engineering screen
and just follow this and flash everything over
http://forum.xda-developers.com/showthread.php?t=991072
Click to expand...
Click to collapse
blaque72 said:
Id download RSD 5 and one of the sbf files 1.26 or 1.52 and boot phone into rsd(power button+volume up) and flash the sbf
Click to expand...
Click to collapse
the problem is that he's on Bell, so there's no sbf for us poor Bell users to flash to yet.
raybond25 said:
the problem is that he's on Bell, so there's no sbf for us poor Bell users to flash to yet.
Click to expand...
Click to collapse
Blah guess I should be more observate when trying to help my apologies hope someone on bell helps him
blaque72 said:
Blah guess I should be more observate when trying to help my apologies hope someone on bell helps him
Click to expand...
Click to collapse
yeah, i don't think he explicitly said that, but i just PM'ed him because i guessed that that was the case and it was, i'm on Bell and ima see what i can do
I HAVE BEEN SAVED. Thank you all for your quick help. I am now up and running again and I have learned from my mistakes.
Kudos to Kenneth for his amazingly quick response and supplying me with an idiot proof script to get my phone back to exactly where it was. YOU DA MAN!
Honorable mention to raybond25 for the quick response and solution as well, YOU DA CANADIAN MAN!
toughbax said:
I HAVE BEEN SAVED. Thank you all for your quick help. I am now up and running again and I have learned from my mistakes.
Kudos to Kenneth for his amazingly quick response and supplying me with an idiot proof script to get my phone back to exactly where it was. YOU DA MAN!
Honorable mention to raybond25 for the quick response and solution as well, YOU DA CANADIAN MAN!
Click to expand...
Click to collapse
What was the solution?
shawnbuck said:
What was the solution?
Click to expand...
Click to collapse
NO IDEA.
Kenneth made me a script that did it all for me all I did was hit the space bar a few times.
Basically the problem seemed to be on this side of the keyboard.....
Moved to Q&A
Please post this script so that we may use this in the future
yes, please post the script toughbax or kenneth so that all can benefit from it, i already bricked and returned one atrix and cant afford to brick another. thanks in advance toughbax and kenneth
erik10002 said:
yes, please post the script toughbax or kenneth so that all can benefit from it, i already bricked and returned one atrix and cant afford to brick another. thanks in advance toughbax and kenneth
Click to expand...
Click to collapse
The problem is that the script that ken wrote for the OP only restores the framework-res.apk file, and nothing else. If you really need this to recover from soft brick in the first place I'm not sure if you have the ability to edit it the way that is required.
Sent from my MB860 using XDA App
raybond25 said:
from what i gather, it turns on, but won't fully boot into android.
by that token, early USB enumeration will allow ADB to work on the phone usually, but in this case i believe debugging was turned off before his device was bricked. so, he can't boot into full android UI, and also can't use ADB to push the restore files because debugging is off.
i've seen this problem with one person before, but i couldn't find a way to force debugging on without going into the UI, if someone can chime in with a way to turn debugging on without initial ADB access, or UI then this problem is solved and more than one person is helped.
Although - he can just reflash if he's on AT&T, if he's on Bell then he's SOL
Click to expand...
Click to collapse
Freaking beautiful. Early USB enumeration was just what I needed to fix my f*ck up.
Hi, sorry for my English but I'll go make an effort, i have this problem in motorola atrix 4G AT&T update OTA a gingerbrand 2.3.4 "SVF: 105 : 1 : 2 faliled to boot 0x1000 Enthering NvFlash recovery mode" This message is for 1 second and then the screen turns dark, will not let me access to any recovery mode, I read and try all forms of power and volume up and volume down and not recognized by the pc via usb
this phone was a gift from a friend who died recently and I feel very sad for having ruined much appreciate if you can tell me how to solve thanks
enriqueleonet said:
Hi, sorry for my English but I'll go make an effort, i have this problem in motorola atrix 4G AT&T update OTA a gingerbrand 2.3.4 "SVF: 105 : 1 : 2 faliled to boot 0x1000 Enthering NvFlash recovery mode" This message is for 1 second and then the screen turns dark, will not let me access to any recovery mode, I read and try all forms of power and volume up and volume down and not recognized by the pc via usb
this phone was a gift from a friend who died recently and I feel very sad for having ruined much appreciate if you can tell me how to solve thanks
Click to expand...
Click to collapse
Unfortunately, it looks as if you've hard bricked your device. See the following warning thread for more information. You'll have to send the device back to retail or purchase a new one.
Make sure that you do not attempt to flash SBF files aside from the Pudding bootloader unlocker once you get your new device. As always, hacking away at your phone is dangerous-- be careful!
Also, please post questions in the Q & A section. I've moved your thread for you this time. Good luck with your device... I'm sorry you're stuck with a paperweight.
me too i am very sad
who can help us
kennethpenn said:
Unfortunately, it looks as if you've hard bricked your device. See the following warning thread for more information. You'll have to send the device back to retail or purchase a new one.
Make sure that you do not attempt to flash SBF files aside from the Pudding bootloader unlocker once you get your new device. As always, hacking away at your phone is dangerous-- be careful!
Also, please post questions in the Q & A section. I've moved your thread for you this time. Good luck with your device... I'm sorry you're stuck with a paperweight.
Click to expand...
Click to collapse
This is painful and difficult to accept that a phone can not be recovered by software problems, this will be my first and last motorola, should send a global warning not to buy a phone with a data structure so weak
CanJian said:
me too i am very sad
who can help us
Click to expand...
Click to collapse
development pls help ..thx.
enriqueleonet said:
This is painful and difficult to accept that a phone can not be recovered by software problems, this will be my first and last motorola, should send a global warning not to buy a phone with a data structure so weak
Click to expand...
Click to collapse
nvidia and motorola have the software available to fix the phone, obviously, or else there wouldn't be a nvflash function in the first place.
they just haven't made it available to the public. =\
it is very logical to think that motorola and Nvidia have the solution to the problem that is not available to the public, I have contacted the people of Motorola and they say I do not know, if anyone knows where I can send my atrix team repair I would appreciate
kennethpenn said:
Unfortunately, it looks as if you've hard bricked your device. See the following warning thread for more information. You'll have to send the device back to retail or purchase a new one.
Make sure that you do not attempt to flash SBF files aside from the Pudding bootloader unlocker once you get your new device. As always, hacking away at your phone is dangerous-- be careful!
Also, please post questions in the Q & A section. I've moved your thread for you this time. Good luck with your device... I'm sorry you're stuck with a paperweight.
Click to expand...
Click to collapse
I would like to consult you on the method of farctory cable, and how do I read but I have no information on what to do after connecting the cable factory at Atrix only speak of sbk but no details
http://forum.xda-developers.com/showthread.php?t=1182871
What happened was I was trying to root my kindle fire HDX with this thread. http://forum.xda-developers.com/showthread.php?t=2689121
I put in "adb reboot bootloader" and it was fine.
After, I put in "fastboot -i 0x1949 flash boot boot.img" and that's where stuff went downhill. Basically my kindle just got stuck at the kindle fire logo, where the kindle is "silver" and the "fire" is orange with the gradient of light going across it.
It was stuck on waiting for device for 10 minutes, so I shut it down by holding the power for 30 seconds and disconnected it.
Ever since then, when I restart the kindle, it just shows the kindle fire shining logo and that's it. I can't do anything else.
I'm very new to this kind of stuff, was doing this with the help of my friend, but now we're both stumped.
Any help would be really helpful. If I could factory reset, I would, so there's a lot of stuff I'm willing to do and part with the info on this kindle. I just want it to be working again.
Thank you for reading this and any help at all would be greatly appreciated!
Edit: Oh, and if it helps, I was running 14.3.2.2 instead of 14.3.2.1.
I didn't think it would make that big of a difference, but I definitely learned my lesson.
uberiyer1 said:
What happened was I was trying to root my kindle fire HDX with this thread. http://forum.xda-developers.com/showthread.php?t=2689121
I put in "adb reboot bootloader" and it was fine.
After, I put in "fastboot -i 0x1949 flash boot boot.img" and that's where stuff went downhill. Basically my kindle just got stuck at the kindle fire logo, where the kindle is "silver" and the "fire" is orange with the gradient of light going across it.
It was stuck on waiting for device for 10 minutes, so I shut it down by holding the power for 30 seconds and disconnected it.
Ever since then, when I restart the kindle, it just shows the kindle fire shining logo and that's it. I can't do anything else.
I'm very new to this kind of stuff, was doing this with the help of my friend, but now we're both stumped.
Any help would be really helpful. If I could factory reset, I would, so there's a lot of stuff I'm willing to do and part with the info on this kindle. I just want it to be working again.
Thank you for reading this and any help at all would be greatly appreciated!
Edit: Oh, and if it helps, I was running 14.3.2.2 instead of 14.3.2.1.
I didn't think it would make that big of a difference, but I definitely learned my lesson.
Click to expand...
Click to collapse
If you can reboot into the bootloader again, it might be worth it to try the same commands, but with the boot.img pulled from 14.3.2.2.
S_transform said:
... but with the boot.img pulled from 14.3.2.2.
Click to expand...
Click to collapse
I don't think this matters... if the HDX 8.9 is anything like the HDX 7, the boot.img file is identical in both the 13.3.2.1 and 13.3.2.2 versions. I did a binary-compare when 13.3.2.2 was released, and they're bit-for-bit identical. FYI.
[Edit] However, there is significant difference in the boot.img between versions 13.3.1.0 and 13.3.2.1. [/Edit]
tl3 said:
I don't think this matters... if the HDX 8.9 is anything like the HDX 7, the boot.img file is identical in both the 13.3.2.1 and 13.3.2.2 versions. I did a binary-compare when 13.3.2.2 was released, and they're bit-for-bit identical. FYI.
[Edit] However, there is significant difference in the boot.img between versions 13.3.1.0 and 13.3.2.1. [/Edit]
Click to expand...
Click to collapse
I was not aware, thanks for the heads up!
No, the root method in my thread unfortunately is non-working. I intended for boot.img to be flashed when the "fastboot" screen is showing. Unfortunately, the hdx does not go into fastboot like its sister device the HD 2013. Reading earlier posts in the thread would show you that it does not work.
But this is puzzling. Did you use a fastboot cable? If not then it was not my root method that bootlooped your device, and you should be able to get a replacement. If you DID use a factory cable, I can help you fix it.
Sent from my KFSOWI, 11.3.2.1, rooted, Amazon stuff replaced with Google Services.
Mineturtle33 said:
No, the root method in my thread unfortunately is non-working. I intended for boot.img to be flashed when the "fastboot" screen is showing. Unfortunately, the hdx does not go into fastboot like its sister device the HD 2013. Reading earlier posts in the thread would show you that it does not work.
But this is puzzling. Did you use a fastboot cable? If not then it was not my root method that bootlooped your device, and you should be able to get a replacement. If you DID use a factory cable, I can help you fix it.
Sent from my KFSOWI, 11.3.2.1, rooted, Amazon stuff replaced with Google Services.
Click to expand...
Click to collapse
how can you help fix with a fastboot cable??
jjrizzelcincy said:
how can you help fix with a fastboot cable??
Click to expand...
Click to collapse
Did you use a fastboot cable or not. If you didnt, it wasnot my root method that killed your device, and if you did, it still might not have been. It depends on whether the tablet's "fastboot" screen appeared when you used the cable. If so, i can help you recover it.
So...
•did you use a fastboot cable?
If yes
•did a fastboot screen pop up?
Sent from my KFSOWI, 11.3.2.1, rooted, Amazon stuff replaced with Google Services.
Mineturtle33 said:
Did you use a fastboot cable or not. If you didnt, it wasnot my root method that killed your device, and if you did, it still might not have been. It depends on whether the tablet's "fastboot" screen appeared when you used the cable. If so, i can help you recover it.
So...
•did you use a fastboot cable?
If yes
•did a fastboot screen pop up?
Sent from my KFSOWI, 11.3.2.1, rooted, Amazon stuff replaced with Google Services.
Click to expand...
Click to collapse
i am only asking how you might go about fixing his problem to learn something new about the device ,that is why i asked you how you would go about that with a fastboot cable your root method did not brick my device
jjrizzelcincy said:
i am only asking how you might go about fixing his problem to learn something new about the device ,that is why i asked you how you would go about that with a fastboot cable your root method did not brick my device
Click to expand...
Click to collapse
If you want me to fix it you need to answer the questions or I can't help you. I'm doing my best.
Sent from my Galaxy Nexus using Tapatalk
Mineturtle33 said:
If you want me to fix it you need to answer the questions or I can't help you. I'm doing my best.
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
again i did not brick my device
using your root method
my device got bricked by an error in safestrap
i did a wipe data factory reset and this when i went to reflash the rom on the rom slot and it kept saying flash failed and that there were 0 mb on the sdcard i even pushed the rom back to the sdcard from adb but it would not flash and when i went to reboot it gave me a warning saying no os found or something like that so i tried and tried to make another rom slot and tried to restore a backup but it would not let me saying 0mb of storage available
so that's my story and now i dont have adb and im stuck at the gray kindle fire logo with only mtp showing but not fully installing but with a fastboot cable i got QHSUSB_BULK at first but after some booting over and over again i got it into QHSUSB_DLOAD with a driver installed on windows and i can see it connected to Linux as well with an id and everything in lsusb from a terminal that is about where my knowledge ends
but with the right devs we could get this working like the evo 3d and a bunch
of other HTC devices that were fixed that way and even get s-off through that QHSUSB_DLOAD mode but i dont have the knowledge to write something like that up or how to issue the proper commands in Linux or what partitions to write to or even the proper chmod to make so im stuck with a nice little paper weight as of now with no devs on board it's looking a bit grim for me
jjrizzelcincy said:
again i did not brick my device
using your root method
my device got bricked by an error in safestrap
i did a wipe data factory reset and this when i went to reflash the rom on the rom slot and it kept saying flash failed and that there were 0 mb on the sdcard i even pushed the rom back to the sdcard from adb but it would not flash and when i went to reboot it gave me a warning saying no os found or something like that so i tried and tried to make another rom slot and tried to restore a backup but it would not let me saying 0mb of storage available
so that's my story and now i dont have adb and im stuck at the gray kindle fire logo with only mtp showing but not fully installing but with a fastboot cable i got QHSUSB_BULK at first but after some booting over and over again i got it into QHSUSB_DLOAD with a driver installed on windows and i can see it connected to Linux as well with an id and everything in lsusb from a terminal that is about where my knowledge ends
but with the right devs we could get this working like the evo 3d and a bunch
of other HTC devices that were fixed that way and even get s-off through that QHSUSB_DLOAD mode but i dont have the knowledge to write something like that up or how to issue the proper commands in Linux or what partitions to write to or even the proper chmod to make so im stuck with a nice little paper weight as of now with no devs on board it's looking a bit grim for me
Click to expand...
Click to collapse
Oh my god I'm an idiot. I thought you were the op. *facepalm* sorry for the trouble.
Sent from my Galaxy Nexus using Tapatalk
Mineturtle33 said:
Oh my god I'm an idiot. I thought you were the op. *facepalm* sorry. For the trouble.
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
NOPE you are stuck helping me now lol
jjrizzelcincy said:
NOPE you are stuck helping me now lol
Click to expand...
Click to collapse
I'll look into it. But as of now I'm a bit busy. Sorry.
Sent from my Galaxy Nexus using Tapatalk
Mineturtle33 said:
I'll look into it. But as of now I'm a bit busy. Sorry.
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
the only way i see a fix for mine since the fastboot cable did not help me get into fastboot mode is if we some how manage to get some devs over here which seems unlikely at this point but i still have hope one falls on a devs lap sometime soon
Hi all, I was in the process of trying to put Android 5.0 on my Verizon G3. I was following this thread:http://forum.xda-developers.com/verizon-lg-g3/general/howto-update-to-stock-lollipop-23a-t3044398. I downgraded to 10b, upgraded to 12b and then the last step, which is when things went wrong is I was upgrading to 23b (5.0) via the Action Launcher method and when the device when to boot back up to install the update it failed.
Im now stuck to where I can not power up the device, I get the LG screen and it says "Secure Boot Error/Certificate Error".. something along those lines. I lost the ability to get into download mode, it tries and then shows the boot error screen before going black.. the notification lights also flash amber and blue. The only thing I can get into is Recovery mode by Volume down + power but I tried every option.. safe mode, wipe cache, factory reset, usb debug mode all give me the boot error screen before going black.
Any suggestions before I trash the device?
I don't know how to get out of that situation, but if you post in the Verizon G3 Q&A section, someone might have some ideas.
Otherwise, I'd go to a Verizon store, tell them that you received am OTA update and left your phone like that.
roirraW "edor" ehT said:
I don't know how to get out of that situation, but if you post in the Verizon G3 Q&A section, someone might have some ideas.
Otherwise, I'd go to a Verizon store, tell them that you received am OTA update and left your phone like that.
Click to expand...
Click to collapse
This is the VZW G3 Q&A no?
I called tech, said I received an update and wasn't sure what happened but the phone wont start now, its going through insurance with the $100 deductible but my concern now is, the tech said if they find it was modded in any way I would be charged $300. The phones not rooted or anything, just a bad file I tried to apply I guess through Action Launcher. But with the notification lights flashing different colors and a boot error message I feel busted lol.
If I can somehow fix the phone I would like to try. I've been in bad situations with other devices and have always found a way out, but this being my first LG device I'm feeling lost and worried its too late.
Cyber Warrior said:
This is the VZW G3 Q&A no?
I called tech, said I received an update and wasn't sure what happened but the phone wont start now, its going through insurance with the $100 deductible but my concern now is, the tech said if they find it was modded in any way I would be charged $300. The phones not rooted or anything, just a bad file I tried to apply I guess through Action Launcher. But with the notification lights flashing different colors and a boot error message I feel busted lol.
If I can somehow fix the phone I would like to try. I've been in bad situations with other devices and have always found a way out, but this being my first LG device I'm feeling lost and worried its too late.
Click to expand...
Click to collapse
Blame Tapatalk. Sorry about that, LOL.
I understand. Don't blame me if I'm wrong, but I doubt if they'll be able to tell. First thing they'll do is put it back to Stock with some advanced tool of their, and I'm sure it'll wipe internal storage where the file was.
roirraW "edor" ehT said:
Blame Tapatalk. Sorry about that, LOL.
I understand. Don't blame me if I'm wrong, but I doubt if they'll be able to tell. First thing they'll do is put it back to Stock with some advanced tool of their, and I'm sure it'll wipe internal storage where the file was.
Click to expand...
Click to collapse
lol. yeah I hope so, at this point I really would like to just fix it though so I dont get stuck paying insurance.
Cyber Warrior said:
lol. yeah I hope so, at this point I really would like to just fix it though so I dont get stuck paying insurance.
Click to expand...
Click to collapse
Maybe when all this rooted stock LG Lollipop news and ROM-making dies down some, bump this thread if noone more knowledgeable comes along and shares some info in the meantime.
Sorry man. Good luck!
Cyber Warrior said:
lol. yeah I hope so, at this point I really would like to just fix it though so I dont get stuck paying insurance.
Click to expand...
Click to collapse
This is for the g2 but I believe it will work. You'll need to run linux or a linux live cd and find the correct files for vs985. Theyre on autoprimes site. If you cant find them reply to this and ill track down the url.
http://forum.xda-developers.com/showthread.php?t=2582142
That should work , I bricked my g2 and was able to fix it using
Fastboot commands, I'm thinking you can use adb commands
And fix your phone. You basically have to push .img files to
The phone through adb. Good luck
Edit, I could always swap mother boards for under two hundred
And just don't even go through your insurance. Check eBay and
Amazon they sell them.
hawkswind1 said:
This is for the g2 but I believe it will work. You'll need to run linux or a linux live cd and find the correct files for vs985. Theyre on autoprimes site. If you cant find them reply to this and ill track down the url.
http://forum.xda-developers.com/showthread.php?t=2582142
Click to expand...
Click to collapse
Yeah I was looking at that last night.. I wouldn't have to be rooted though? I'll see if I can find the files I need. I've never run Linux before but its worth a shot. I was kind of discouraged when I read about a similar G3 user who tried the process with no luck.
Alright I found these.. http://forum.xda-developers.com/verizon-lg-g3/general/reference-stock-img-files-t2966958
Would those do? And what mode would I put the device in? The computer does not recognize the phone..download mode won't work and recovery mode options won't work either. I'm familiar with adb and fastboot but if someone could post the commands I need it would be helpful..in the meantime I'm going to try and see if I can find them myself. Thanks
Cyber Warrior said:
Alright I found these.. http://forum.xda-developers.com/verizon-lg-g3/general/reference-stock-img-files-t2966958
Would those do? And what mode would I put the device in? The computer does not recognize the phone..download mode won't work and recovery mode options won't work either. I'm familiar with adb and fastboot but if someone could post the commands I need it would be helpful..in the meantime I'm going to try and see if I can find them myself. Thanks
Click to expand...
Click to collapse
Does your phone even show as qhsusb_bulk or similar in device manager while in Linux? Make sure you use the img's from the firmware you were installing when you had the problem. I assume 23B. The commands are in the link I posted above but keep in mind they are for the G2. It's likely to DD commands, ie. partition locations are different on the G3, I don't know the correct ones. Maybe some research can dig them up. Doesn't look too bad assuming you can get linux to recognize the phone in some form, which it should and that you're able to verify the location of the partitions for G3. Wish I could be more help. It was a long time ago when I went through this on the G2
Cyber Warrior said:
This is the VZW G3 Q&A no?
I called tech, said I received an update and wasn't sure what happened but the phone wont start now, its going through insurance with the $100 deductible but my concern now is, the tech said if they find it was modded in any way I would be charged $300. The phones not rooted or anything, just a bad file I tried to apply I guess through Action Launcher. But with the notification lights flashing different colors and a boot error message I feel busted lol.
If I can somehow fix the phone I would like to try. I've been in bad situations with other devices and have always found a way out, but this being my first LG device I'm feeling lost and worried its too late.
Click to expand...
Click to collapse
I've never had to do insurance for a bad update.
I have TEC and in those cases where there is absolutely no damage, I get a replacement for free.
YMMV but I wouldn't pay $100.
hawkswind1 said:
This is for the g2 but I believe it will work. You'll need to run linux or a linux live cd and find the correct files for vs985. Theyre on autoprimes site. If you cant find them reply to this and ill track down the url.
http://forum.xda-developers.com/showthread.php?t=2582142
Click to expand...
Click to collapse
Hi I have Linux up and running.. can you help me with what files I need please?
Cyber Warrior said:
Hi I have Linux up and running.. can you help me with what files I need please?
Click to expand...
Click to collapse
It's a bit confusing the way it's written in the guide. I believe you use the 23b files in your case. Reread it to be sure.
The files are here- http://forum.xda-developers.com/verizon-lg-g3/general/reference-stock-img-files-t2966958
More files here if needed http://downloads.codefi.re/autoprime/LG/LG_G3
I'm not even sure my phone is being recognized..at least nothing pops up. I'm not familiar with terminal commands in linux. At this point I'm lost.. I messaged auto prime to see if he could help out. I'm not even sure where to begin converting that g2 guide for use with the g3.
For the hek of it I'm putting the android SDK on Linux just to see if I can get fastboot to recognize the phone.
http://forum.xda-developers.com/lg-g3/general/fix-unbrick-lg-g3-stuck-qualcomm-hs-usb-t2933853 you can try this from Windows if your phone is showing up as Qualcomm in device manager.
dwheimerl said:
http://forum.xda-developers.com/lg-g3/general/fix-unbrick-lg-g3-stuck-qualcomm-hs-usb-t2933853 you can try this from Windows if your phone is showing up as Qualcomm in device manager.
Click to expand...
Click to collapse
IS there a driver to get my phone to be recognized as Qualcomm?? I think i found a way to fix mine but i need the driver
danetbra63 said:
IS there a driver to get my phone to be recognized as Qualcomm?? I think i found a way to fix mine but i need the driver
Click to expand...
Click to collapse
Qualcomm driver is on this page.. 252-253 http://forum.xda-developers.com/showthread.php?t=2582142&page=252
Good luck, I was able to get the phone recognized as qhsusb_bulk, then as qualcomm 9008 but eventually gave up after spending over 2 days researching and trying different methods before i threw in the towel.. I even had help via remote access to my computer with no luck. Check the thread I linked there were a few guys willing to help out.
My replacement G3 actually arrived today.. still cant believe I hard bricked a device.
Cyber Warrior said:
Qualcomm driver is on this page.. 252-253 http://forum.xda-developers.com/showthread.php?t=2582142&page=252
Good luck, I was able to get the phone recognized as qhsusb_bulk, then as qualcomm 9008 but eventually gave up after spending over 2 days researching and trying different methods before i threw in the towel.. I even had help via remote access to my computer with no luck. Check the thread I linked there were a few guys willing to help out.
My replacement G3 actually arrived today.. still cant believe I hard bricked a device.
Click to expand...
Click to collapse
What's the next step after the 9008? i made it that far but idk what to do next.
danetbra63 said:
What's the next step after the 9008? i made it that far but idk what to do next.
Click to expand...
Click to collapse
I'm assuming using the tool to push the img files but I didn't get that far.
I downloaded the new leaked pie version of android for the Galaxy s9+ and after realizing it was buggy, lacking some features i needed, i tried going back to oreo and messed up somewhere. I used odin do get oreo and that worked, then while starting back up, it said i had to factory reset it and after turning the phone back off, i keep getting stuck on the ss rdx screen where it asks to back up to sd card or computer and cant get off that no matter what i do. Ive tried backing up to sd card and nothing happens. Any help would be appreciated.
I had this same problem..... I'm on an s9+ on Xfinity service. I could boot the phone back up by pressing and holding a combo of power and volume down I believe but the phone would boot up and be locked up on the sign-on screen (it wouldn't pull up the keypad to let me enter the pin code). I also couldn't shut down the phone or boot it into download mode or into recovery. I ended up hooking it up to my computer via usb and sending an adb command to fastboot into download mode. Luckily that worked and I could then use Odin and reflash stock firmware. I already had developer mode and usb debugging mode enabled prior to the phone locking up on me.
---------- Post added at 01:21 PM ---------- Previous post was at 01:01 PM ----------
I also found this by digging through Google:
https://forum.xda-developers.com/galaxy-s8+/help/samsung-s8-sm-g955uzkatmb-boot-error-t3726832
Hope this helps.
Libdawg said:
I had this same problem..... I'm on an s9+ on Xfinity service. I could boot the phone back up by pressing and holding a combo of power and volume down I believe but the phone would boot up and be locked up on the sign-on screen (it wouldn't pull up the keypad to let me enter the pin code). I also couldn't shut down the phone or boot it into download mode or into recovery. I ended up hooking it up to my computer via usb and sending an adb command to fastboot into download mode. Luckily that worked and I could then use Odin and reflash stock firmware. I already had developer mode and usb debugging mode enabled prior to the phone locking up on me.
---------- Post added at 01:21 PM ---------- Previous post was at 01:01 PM ----------
I also found this by digging through Google:
https://forum.xda-developers.com/galaxy-s8+/help/samsung-s8-sm-g955uzkatmb-boot-error-t3726832
Hope this helps.
Click to expand...
Click to collapse
Samsung phones do not have "fastboot" mode. What you did is issue the adb command
adb reboot bootloader OR download OR recovery OR edl
If adb wasn't already pre-enabled then this would not have worked, however flashing a combination or eng boot would have enabled adb mode.
billa said:
Samsung phones do not have "fastboot" mode. What you did is issue the adb command
adb reboot bootloader OR download OR recovery OR edl
If adb wasn't already pre-enabled then this would not have worked, however flashing a combination or eng boot would have enabled adb mode.
Click to expand...
Click to collapse
Dude... Way to ressurect an old thread..
InsanePostman said:
Dude... Way to ressurect an old thread..
Click to expand...
Click to collapse
I replied to a message dated 10-04-2018 it's not from 1999 lol
thank you
billa said:
I replied to a message dated 10-04-2018 it's not from 1999 lol
Click to expand...
Click to collapse
and your reply is still relevant... even another year later. I'm in the same boat and was confused about the fastboot reference, but appreciate the info from everyone.
*side note*
"Way to ___" posts and comments rarely add any value and usually have the opposite effect intended... instead calling someone else out or pointing out a misconduct you end up looking like a condescending prick. And now I've got dirty hands as well and seem like a know it all for calling out this know it all. The high road is always a better path.
God bless relevant ressurectable threads. Unlike Pet Cemeteries... sometimes dead is NOT better : )
HT
HTidwell said:
and your reply is still relevant... even another year later. I'm in the same boat and was confused about the fastboot reference, but appreciate the info from everyone.
*side note*
"Way to ___" posts and comments rarely add any value and usually have the opposite effect intended... instead calling someone else out or pointing out a misconduct you end up looking like a condescending prick. And now I've got dirty hands as well and seem like a know it all for calling out this know it all. The high road is always a better path.
God bless relevant ressurectable threads. Unlike Pet Cemeteries... sometimes dead is NOT better : )
HT
Click to expand...
Click to collapse
I see, so anyone posting a relevant reply to a thread regardless if it's new or old, is now called a "know it all" by your name calling.
Interestingly I couldn't find in the xda rules anything that prohibits anyone from posting a reply if it's one year or older.
I'll just leave it at that, and let the moderators decide.