Database Users

broke something again

I didn't think that I'd ever brick my phone and NOT be able to recover it. I've got a real brick now. I don't have a dev cable another battery or an external charger. I wanted to unlock the bootloader. I made some kind of error and now I have SVF:105:1:2
Failed to boot 0x1000
no OS detected, going to RSD mode.
Battery too low to flash.
If i try for android recovery I get Magic Value mismatch in red letters followed by
Reading ODM fuse: 1
any way around this until I can figure out how to get the battery charged up?

How did you get this error?
Sent from my MB860 using XDA Premium App

Did you get it flashing pudding? If so all you need to to is type the fastboot commands and then fastboot reboot
Sent from my MB860 using XDA App

jruweaver said:
How did you get this error?
Sent from my MB860 using XDA Premium App
Click to expand...
Click to collapse
flashing zomgunlock-lite sbf. I just now have the unlocked bl 4.5.91 sbf that was posted in the forums. I have the full screen menu. I tried to use fastboot oem unlock but, it was not unlocking. will the phone charge without being turned on? I normally always use a wall usb charger or usb cable to computer to charge the phone turned on. I have rsd lite 5.3.1

Are you familiar with fastboot?
Sent from my MB860 using XDA Premium App

As far as i know, thats the code or hard bricking. Meaning "kaput"

I just unlock my bootloader with my battery at 30%. N now i have Ninja!!
Sent from my MB860 using XDA App

If you got it while flashing "pudding" and can still get into fastboot, then the fastboot OEM unlock should fix it.
Sent from my MB860 using XDA Premium App

jruweaver said:
If you got it while flashing "pudding" and can still get into fastboot, then the fastboot OEM unlock should fix it.
Sent from my MB860 using XDA Premium App
Click to expand...
Click to collapse
I got the SBF and now I'm waiting on an external battery charger to arrive. once thats here I'll be able to RSD the sbf. At least I haven't tried to downgrade the system. I'm seeing threads everywhere of hard bricks. This same error but without any of the options to fix anything, no menu options.

This happened to me. Borrow a charged battery..and choose option 2 for fastboot and type in the fastboot commands.
Sent from my MB860 using XDA App

defnow said:
This happened to me. Borrow a charged battery..and choose option 2 for fastboot and type in the fastboot commands.
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
which fastboot commands? the fastboot oem unlock? was it that or something else?

1. Charge the battery to full with an external charger
2. Turn off phone (of course is off )
3. Press vol down while you turn on
4. Wait until "fastboot" tag show up
5. Press vol up to select fastboot
6. Now you phone is in fastboot mode
7. Connect USB to pc
8. Now run fastboot commands as follow:
fastboot OEM unlock
It will show up your unique id #
re type
fastboot OEM unlock "your unique id#"
And then
fastboot reboot
By the way you must have fastboot command files
Easy way download my script AUTOMATIC_UNLOCKV3.3 and unzip to your hard disk and just run the file "fix.bat"
I hope it help
powerlifter450 said:
which fastboot commands? the fastboot oem unlock? was it that or something else?
Click to expand...
Click to collapse
Sent from my MB860 using XDA App

[Q] OTA bootloader issue????

okay, so Im new here, literally just traded my thrill for the atrix about an hour ago. Now, i see that there are people being bricked by trying to unlock their bootloader after the OTA update, it was already updated when i got it. So, my question is... what the hell can i do to unlock the bootloader and NOT brick my phone?? I would really like to unlock it. Also, if i do not unlock my bootloader, can i still install CWM and flash ROMs??

If you have an AT&T Atrix, use this (I received the phone with stock 2.3.4, 4.5.91)- http://forum.xda-developers.com/showthread.php?t=1182871 . Super easy and worked great for me.
If not, read the Noob guide on top of the General Forum.

You need to unlock the bootloader first before you can do anything.
Sent from my MB860 using XDA App

HustlinDaily said:
If you have an AT&T Atrix, use this (I received the phone with stock 2.3.4, 4.5.91)- http://forum.xda-developers.com/showthread.php?t=1182871 . Super easy and worked great for me.
If not, read the Noob guide on top of the General Forum.
Click to expand...
Click to collapse
i see a lot of people saying they are having issues but fixing it with the android recovery... how do i get into android recovery on this device?

Enzopreme said:
i see a lot of people saying they are having issues but fixing it with the android recovery... how do i get into android recovery on this device?
Click to expand...
Click to collapse
Have to either root and the install ROM Mangers from the market, or install Rom Racers via fastboot (in the dev section).
Unlocking bootloader is pretty easy. There's a stupid scrpit to do it now... see my signature for noob guide for links.
Sent from my MB860 using xda premium

okay, i followed the instructions to a "t", now my device reads
SVF:105:1:2
Failed to boot 0x1000
PwrReason: PWR_KEY_PRESS
Starting Fastboot Protocol support
PLEASE HELP!!!!

Enzopreme said:
okay, i followed the instructions to a "t", now my device reads
SVF:105:1:2
Failed to boot 0x1000
PwrReason: PWR_KEY_PRESS
Starting Fastboot Protocol support
PLEASE HELP!!!!
Click to expand...
Click to collapse
Need to enter fastboot mode and enter the command fastboot unlock or fastboot oem unlock.... or have you done that?
Sent from my MB860 using xda premium

Swiftks said:
Need to enter fastboot mode and enter the command fastboot unlock or fastboot oem unlock.... or have you done that?
Sent from my MB860 using xda premium
Click to expand...
Click to collapse
Fastboot mode = turn phone off
Hold power button.and volume down
Until u see. Fastboot then press volume up to select it should read starting fastboot protocal
Plug in your USB. Cable that came with the phone open terminal and type fastboot oemunlock
Then do it again with the unique I'd. And hit enter
Sent from my MB860 using xda premium

ltdanno360 said:
Fastboot mode = turn phone off
Hold power button.and volume down
Until u see. Fastboot then press volume up to select it should read starting fastboot protocal
Plug in your USB. Cable that came with the phone open terminal and type fastboot oemunlock
Then do it again with the unique I'd. And hit enter
Sent from my MB860 using xda premium
Click to expand...
Click to collapse
Yeah, what he said
Shows you how long its been since I unlocked mine.... May, June??? First day pudding came out, whenever that was.
Sent from my MB860 using xda premium

[Q]Brick ?

Hey , i havent touched my N7 forquit a while .. today i tryed to turn it on and found out it is out off power soi plugged it into my charger but when i tried to turn it up i passed the google logo and was stuck at the blackbean logo (when its connected to the charger it show the charging ani but turns off after 5 sec then i need to click the power bottom to see the charging ani again) and when i try to get into fastboot i cant . it just shows me the place where i can select between "start" , "recovery" and "fastboot" but it get stuc on that screen . i cant move anything or just hit "start" cuz it doesnt work either .
So am i bricked ? what can i do ?
i dont understand how that happened since i didnt touch it all week long .. (oh yea and the battery never charges it stays forever on the lowest point of the ani)

Leave it charge for a while without messing with it.
secondly it is not bricked, if it turns on any bit and if it shows anything on the screen it is not bricked.
I don't know why people keep using that word incorrectly, brick means that your device is basically a brick, a paperweight.
And that screen that says recovery etc IS where you fastboot from, that's the bootloader screen.
Sent from my Nexus 7 using xda premium

nodstuff said:
Leave it charge for a while without messing with it.
secondly it is not bricked, if it turns on any bit and if it shows anything on the screen it is not bricked.
I don't know why people keep using that word incorrectly, brick means that your device is basically a brick, a paperweight.
And that screen that says recovery etc IS where you fastboot from, that's the bootloader screen.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
OK , thank you .
still , l cant get to the fastoot and into the rom itself or recovery meaning i cant do nothing . how screwed am I ?

rkiller51 said:
OK , thank you .
still , l cant get to the fastoot and into the rom itself or recovery meaning i cant do nothing . how screwed am I ?
Click to expand...
Click to collapse
If you get to the menu that says "recovery" "start" "reboot bootloader" then you are in fastboot mode/bootloader.
Leave it charge a while and see if it works and if not you can flash a factory image or better yet, reflash your recovery and flash a ROM zip
Sent from my Nexus 7 using xda premium

nodstuff said:
If you get to the menu that says "recovery" "start" "reboot bootloader" then you are in fastboot mode/bootloader.
Leave it charge a while and see if it works and if not you can flash a factory image or better yet, reflash your recovery and flash a ROM zip
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
I cant . its in that mode but still stuck , flashing doesnt work and so is any kind of flashing .
what can i do ?

What error do you get when you try flash something by fastboot?
Sent from my Nexus 7 using xda premium

When you are 'stuck' in fastboot, you have a couple ways to go about it... one option and that is to run the N7 toolkit to get the N7 into recovery. From there you can restore your stuff, drop stuff onto your N7 to flash a new rom, etc...
http://forum.xda-developers.com/showthread.php?t=1809195
Basically you run the toolkit like you are going to root it. Then when you get past installing the USB drivers and such, IIRC there was an option to get into recovery.

Ughh, toolkits.
Sent from my Nexus 7 using xda premium

nodstuff said:
What error do you get when you try flash something by fastboot?
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
kpjimmy said:
When you are 'stuck' in fastboot, you have a couple ways to go about it... one option and that is to run the N7 toolkit to get the N7 into recovery. From there you can restore your stuff, drop stuff onto your N7 to flash a new rom, etc...
http://forum.xda-developers.com/showthread.php?t=1809195
Basically you run the toolkit like you are going to root it. Then when you get past installing the USB drivers and such, IIRC there was an option to get into recovery.
Click to expand...
Click to collapse
nodstuff said:
Ughh, toolkits.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
DOESNT wrok . i am stuck at "waiting forr device" .. annoying .
now that i charged all night i can move in bootloader screen ! but when i get into recovery it is stucked in google logo and hen i plug it to the PC / charger it just get stucked and i cant move it anymore or use any tool kit . its like the device is dead !
any ideas ?

Sounds like you need to fastboot the factory image to the device. Try multiple versions of fastboot. People have been reporting problems and switching to a new version of fastboot has helped.
Sent from my Nexus 7 using XDA Premium HD app

kkl0wn said:
Sounds like you need to fastboot the factory image to the device. Try multiple versions of fastboot. People have been reporting problems and switching to a new version of fastboot has helped.
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
How can i do that ?
- no recovery
- no fastboot (freez on plug)
- no boot
=nothing ?
or am i missing somthing ? i can think of a way to solve this . plz help !!

Try a new version of fastboot... possibly from one of the rootkits then follow these instructions....
http://forums.androidcentral.com/ne...ide-factory-image-restore-your-nexus-7-a.html
Sounds like you're in fastboot mode and the above should work. Possibly make a YouTube video to show us the problems.
http://forum.xda-developers.com/showthread.php?t=1929617 ( Here's a thread that shows what I mean. Some people have problems with certain fastboot versions.)
Sent from my Nexus 7 using XDA Premium HD app

Deleted Bootloader

Hello Guys!!
I have Problem.... yesterday I restarted My nexus 7 and it stopped working.... when i tried to turn it on, there appeared only google logo...
but today I tried to fix this problem and flash stock with fastboot, but there was problem with flashing boot and flashing bootloader.... and I by accident deleted bootloader with this command: fasboot erase bootloader....
so now my nexus 7 bricked verrrrry hard and it does nothing when i connect to charger, but when i connect to PC, computer says that usb device not recognised.... what to do??? is there any way to do it manually??

giokaxo said:
Hello Guys!!
I have Problem.... yesterday I restarted My nexus 7 and it stopped working.... when i tried to turn it on, there appeared only google logo...
but today I tried to fix this problem and flash stock with fastboot, but there was problem with flashing boot and flashing bootloader.... and I by accident deleted bootloader with this command: fasboot erase bootloader....
so now my nexus 7 bricked verrrrry hard and it does nothing when i connect to charger, but when i connect to PC, computer says that usb device not recognised.... what to do??? is there any way to do it manually??
Click to expand...
Click to collapse
If you had made nvflash blobs before your unfortunate fastbootery, then you should be able to restore the bootloader and partitioning. Otherwise you might be able to get a few $$$ on eBay if the screen is in good condition.

pokey9000 said:
If you had made nvflash blobs before your unfortunate fastbootery, then you should be able to restore the bootloader and partitioning. Otherwise you might be able to get a few $$$ on eBay if the screen is in good condition.
Click to expand...
Click to collapse
unfortunatelly not.... is there any way to fix this ptoblem except selling it??

You accidentally typed all that and hit enter? ???
Sorry to hear that.
Sent from my SGH-T989 using Tapatalk

kj2112 said:
You accidentally typed all that and hit enter? ???
Sorry to hear that.
Sent from my SGH-T989 using Tapatalk
Click to expand...
Click to collapse
Not only, ... erasing the bootloader is no problem as long as you do not reboot. Flashing a new bootloader before rebooting would have solved the situation.
Sent from my Nexus 7 using xda app-developers app

AndDiSa said:
Not only, ... erasing the bootloader is no problem as long as you do not reboot. Flashing a new bootloader before rebooting would have solved the situation.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
is there any solution to repair my nexus 7 :crying::crying:

If you've rebooted, it doesn't sound like there's any fix.
But I'm going off other comments. I'm no expert.
Sent from my SGH-T989 using xda app-developers app

bricked phone, tried everything

Ok, I've put my flame suit on, but I swear I have tried everything. I am not a developer level guy by any means, but I've been installing custom roms since the OG droid. But this time I got distracted and clearly made a foolish mistake. I was installing XDABBEB's new rom and I totally flaked out and installed the bootstrap and the rom in the same flash. it obviously didn't work and even though I read the instructions, I tried to restore my rom from a backup. Now the only thing I can do is boot into fastboot.
I've tried a number of ways to get TWRP or CWM back onto my phone so I can sideload a rom onto it, but every time I try to fastboot a recovery file it says that "remote: image is not a boot image" or something. What I have gathered from my research is that I cant install a custom recovery unless I am rooted.
/
So, without a custom recovery and only fastboot at my disposal, where do I go from here?

sfl007 said:
Ok, I've put my flame suit on, but I swear I have tried everything. I am not a developer level guy by any means, but I've been installing custom roms since the OG droid. But this time I got distracted and clearly made a foolish mistake. I was installing XDABBEB's new rom and I totally flaked out and installed the bootstrap and the rom in the same flash. it obviously didn't work and even though I read the instructions, I tried to restore my rom from a backup. Now the only thing I can do is boot into fastboot.
I've tried a number of ways to get TWRP or CWM back onto my phone so I can sideload a rom onto it, but every time I try to fastboot a recovery file it says that "remote: image is not a boot image" or something. What I have gathered from my research is that I cant install a custom recovery unless I am rooted.
/
So, without a custom recovery and only fastboot at my disposal, where do I go from here?
Click to expand...
Click to collapse
Phone model?
You can try to flash through LG Flash Tools

Swakiny said:
Phone model?
You can try to flash through LG Flash Tools
Click to expand...
Click to collapse
Thanks for the reply.
I have a VS980S. I have tried the LG flash tool, but I can't get any of the numerous LG drivers to recognize my phone. I even tried dd commands in Ubuntu, but all it would do is try and mount volume after volume making it impossible to use the interface,

sfl007 said:
Thanks for the reply.
I have a VS980S. I have tried the LG flash tool, but I can't get any of the numerous LG drivers to recognize my phone. I even tried dd commands in Ubuntu, but all it would do is try and mount volume after volume making it impossible to use the interface,
Click to expand...
Click to collapse
I'm in the same boat man. I tried flashing AOKP and it hung and I rebooted and everything but TWRP was gone. I'm in the process of trying the KDZ method right now.

markrulesallnow said:
I'm in the same boat man. I tried flashing AOKP and it hung and I rebooted and everything but TWRP was gone. I'm in the process of trying the KDZ method right now.
Click to expand...
Click to collapse
I hope it works for you. I tried that and flashing TWRP with fastboot but it said that it wasn't a valid boot image. A little research said that happens when your device is not rooted. But how can I root my phone from fastboot alone?

sfl007 said:
I hope it works for you. I tried that and flashing TWRP with fastboot but it said that it wasn't a valid boot image. A little research said that happens when your device is not rooted. But how can I root my phone from fastboot alone?
Click to expand...
Click to collapse
Try IOroot ... flash it true ADB !!

Denfic said:
Try IOroot ... flash it true ADB !!
Click to expand...
Click to collapse
I'll give a try and report back. But I have a feeling it won't work. I think I have the adb driver loaded but I can't get my computer to recognize any other of the drivers.

sfl007 said:
I'll give a try and report back. But I have a feeling it won't work. I think I have the adb driver loaded but I can't get my computer to recognize any other of the drivers.
Click to expand...
Click to collapse
when opening window in map .. try to tick adb service !!! It might recognize the phone that way !

​
Denfic said:
when opening window in map .. try to tick adb service !!! It might recognize the phone that way !
Click to expand...
Click to collapse
Sorry, what do you mean by "opening window in map"?

I was also in the same boat for 36 h, stuck on trwp recovery, no rom, no gaps in memory... I'm freely sailing now! I did this:
- press together power and lower button to get usb connecting screen, unplugged usb cable.
- LG tools installed and D-802 pilots {for me] installed, plug cable and check pilots again.
- launch in LG tools option for wrong install repair
- wait until the complete rom repair is installed, quite long, and then you win automatic reboot! You just loose root. Ioroot 25 again, that's all.
Hope it works for you chaps.

I had a similar issue. Follow this step by step. It even tells you when and how to install the drivers
http://www.droidviews.com/how-to-restore-lg-g2-to-stock-firmware/
Sent from my VS980 4G using xda app-developers app

Icfatpeople said:
I had a similar issue. Follow this step by step. It even tells you when and how to install the drivers
http://www.droidviews.com/how-to-restore-lg-g2-to-stock-firmware/
Sent from my VS980 4G using xda app-developers app
Click to expand...
Click to collapse
Yeh try this ... what i meant was when opening windows in adb-map ... windows -explorer !
But try the llink provided ...it will wake up your phone ..! :good:

Believe me before doing any thing using your pc just try to change the usb port first, then let it install the driver automatically(if you're using w7/8)
if windows xp just dont plug your phone remove the old LG driver and then plug your phone to another usb port that the one you have used it before with your phone and install the driver, and then proceed....
Why i am telling you this?
because i had almost the same problem with my galaxy note 2..... it wasn't recognizing my phone until i changed my usb port in download
mode and let it istall the driver......
hope it'll help.......... :good:

Icfatpeople said:
I had a similar issue. Follow this step by step. It even tells you when and how to install the drivers
http://www.droidviews.com/how-to-restore-lg-g2-to-stock-firmware/
Sent from my VS980 4G using xda app-developers app
Click to expand...
Click to collapse
Ok, when I try this the computer recognizes my phone as a "USB Modem Phone ADB port" in device manager. But when I follow the directions in the link above if fails at Step 24. It says the phone is not connected. It is asking for my phone to be in "Download mode" in step 17, but I can only get into Fastboot mode. Is that the issue?

Yeah it is. Have you tried getting it into download mode? I was able to when I was stuck with a fast boot
Sent from my VS980 4G using xda app-developers app
---------- Post added at 03:54 PM ---------- Previous post was at 03:53 PM ----------
Try holding the power until the phone is off. Then you should be able to get to download mode
Sent from my VS980 4G using xda app-developers app

Icfatpeople said:
Yeah it is. Have you tried getting it into download mode? I was able to when I was stuck with a fast boot
Sent from my VS980 4G using xda app-developers app
---------- Post added at 03:54 PM ---------- Previous post was at 03:53 PM ----------
Try holding the power until the phone is off. Then you should be able to get to download mode
Sent from my VS980 4G using xda app-developers app
Click to expand...
Click to collapse
Ok, as i understand it you have to hold volume up and plug the device in while its off. The problem I am having is that the phone is always on. Regardless of what mode I have it in, I can always see the back light glowing. I've searched for ways of truly turning the phone off, but I can't find any info.
Suggestions?

sfl007 said:
Ok, as i understand it you have to hold volume up and plug the device in while its off. The problem I am having is that the phone is always on. Regardless of what mode I have it in, I can always see the back light glowing. I've searched for ways of truly turning the phone off, but I can't find any info.
Suggestions?
Click to expand...
Click to collapse
Ok, hold power button until phone turn off, still holding until LG logo appear again, then the phone will turn off completly.
Turn off = Off
(First Off will take a long time, don't worry(about 40 seconds), don't forget: still holding the power button until LG logo appear and the phone Off)

Swakiny said:
Ok, hold power button until phone turn off, still holding until LG logo appear again, then the phone will turn off completly.
Turn off = Off
(First Off will take a long time, don't worry(about 40 seconds), don't forget: still holding the power button until LG logo appear and the phone Off)
Click to expand...
Click to collapse
ok, it seems like it goes off. the backlight appears to be off, but when I hold the volume up button and then plug it in, it immediately goes to fastboot. ugh.
can i use fastboot to send the phone to download mode? I'll start searching for that now.....

Have you tried this
http://forum.xda-developers.com/showthread.php?t=2477595
Sent from my VS980 4G using xda app-developers app

Icfatpeople said:
Have you tried this
http://forum.xda-developers.com/showthread.php?t=2477595
Sent from my VS980 4G using xda app-developers app
Click to expand...
Click to collapse
Holy cow. This might be the last piece of the puzzle. I will report back after trying this.