my phone had down grand to 1.86,
and i forgot that the OTA can not be do that!
and noe what i got is:
SVF : 105:1:2
FAILED TO BOOT 0X1000
ENTERING NvFLASH RECOVERY
and after show this message, it keep turn off, and i need to put out the battery!
and i had see a lot of thread about this problem, and i still get confuse!!
is it a hard brick or soft brick???
if its a soft brick, can it be save it back???
i saw some member in adx said it can be use the command to start the fastboot mode, but how??? please help~! i found a lot of thread in adx, but i still very confuse! can someone tell me and teach me??? please !!!
Do you have a Unlocked Bootloader?
Sounds like a hard brick to me
P.S. Post your questions in the Q&A section. Thanks
if nvflash recovery is your only option it's a hard brick.
sorry for your loss
ClearFire said:
Do you have a Unlocked Bootloader?
Sounds like a hard brick to me
P.S. Post your questions in the Q&A section. Thanks
Click to expand...
Click to collapse
i remember that i havent unlock my phone, i just use OTA to up to att 2.3.4!
and i down to 1.26(yea, not 1.83, is 1.26), i got this problem....
hard brick??........i want to die......
eeww said:
i remember that i havent unlock my phone, i just use OTA to up to att 2.3.4!
and i down to 1.26(yea, not 1.83, is 1.26), i got this problem....
hard brick??........i want to die......
Click to expand...
Click to collapse
Yeah... guess you didn't see the big sticky at the top of the dev forum that says to not flash a earlier .sbf file once you have updated to Gingerbread. Sorry, but you are bricked.
eeww said:
my phone had down grand to 1.86,
and i forgot that the OTA can not be do that!
and noe what i got is:
SVF : 105:1:2
FAILED TO BOOT 0X1000
ENTERING NvFLASH RECOVERY
and after show this message, it keep turn off, and i need to put out the battery!
and i had see a lot of thread about this problem, and i still get confuse!!
is it a hard brick or soft brick???
if its a soft brick, can it be save it back???
i saw some member in adx said it can be use the command to start the fastboot mode, but how??? please help~! i found a lot of thread in adx, but i still very confuse! can someone tell me and teach me??? please !!!
Click to expand...
Click to collapse
Hard brick
Its a Hard Brick I've had this happen to my atrix too
Sent from my SAMSUNG-SGH-I777 using XDA App
RMA it go to the Motorola website service and repair, state it won't turn on. It took a few business days before they looked at my phone. In total I was using my old dumb phone for a week.
I did the same thing you did... Something went wrong when I used a friends Cheap knock off Car charger. Corrupted most of the OS. I did a factory reset certain things didn't work like the lock screen and the home button then I SBF'd up to 2.3.4. Still some things didn't work so I downgraded to 1.26 (BIG MISTAKE).
hard brick. just RMA it to motorola. state that it doesn't turn on. you should get a new phone within a week.
Related
Motorola Atrix 4G At&t show error"SVF:105.1:2 Failed to boot 0X1000"
whn i try to downgrade to v2.3 to v2.2.2 after flashing show this message
how can i solve it pls any 1 give me the solution
post it here
There is no fix. You are hard-bricked.
Sent from my MB860 using XDA App
Pull the battery and try:
Press and hold vol down while you turn on your phone until "fastboot" tag show up in your screen the release vol down and press vol up once to enter to fastboot
Check if it work?
bivrat said:
Motorola Atrix 4G At&t show error"SVF:105.1:2 Failed to boot 0X1000"
whn i try to downgrade to v2.3.4 to v2.2.2 after flashing show this message
how can i solve it pls any 1 give me the solution
post it here
Click to expand...
Click to collapse
Sent from my MB860 using XDA App
thr is no option like this............
just show this error and shut off the phone.............
SVF:105.1:2 Failed to boot 0X1000
any other solution...............'
How it happened? After flashing a SBF by RSD? Did you were bootloader unlocked before?
Sent from my MB860 using XDA App
There is no fix. You are hard Bricked.
Insurance will cover, AT&T store MIGHT if you say it happened when installing gingerbread update I guess.
The reason I was asking was due to the2dcour stated:
the2dcour said:
yes but you will get 0x1000 error. Don't freak out, it will let you boot in to fasboot and unlock. In fact, if you boot directly into fastboot after flash you wont even seen the 0x1000 probably. This has worked for multiple people that flashed 2.3.4 official sbf or official OTA 2.3.4 . As always, not guaranteeing anything for your specific phone.
Click to expand...
Click to collapse
BUT THAT APPLIED FOR A SPECIFIC PROCEDURE AFTER FLASHING BY RSD 2.3.4 WITH PUDDING SBF
IF YOU FLASHED A MOTO SBF WITHOUT PUDDING AFTER BEEN "UNLOCKED" SO THEN YES IS A HARD BRICK
Sent from my MB860 using XDA App
mramirezusa said:
The reason I was asking was due to the2dcour stated:
BUT THAT APPLIED FOR A SPECIFIC PROCEDURE AFTER FLASHING BY RSD 2.3.4 WITH PUDDING SBF
IF YOU FLASHED A MOTO SBF WITHOUT PUDDING AFTER BEEN "UNLOCKED" SO THEN YES IS A HARD BRICK
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
Well, there are enough warnings which say not to downgrade from 2.3.4. Except the SBF with Pudding. And if you ignore those warnings, that's what you get.
Sorry dude, it is your own fault. Phone is bricked....
whn i try to flashing .sbf using rsd mode thn it happen to me.............. so how can i solved by own............... i dnt unlocked it by bootloader
so thr no solution to recover my phone.............
bivrat said:
whn i try to flashing .sbf using rsd mode thn it happen to me.............. so how can i solved by own............... i dnt unlocked it by bootloader
so thr no solution to recover my phone.............
Click to expand...
Click to collapse
Nope. No fix. Sorry
so now wht can i do............ can i claim to motorola warranty...... they can solved it............. or no 1 can solved it...........
The warranty "should' cover it.
But like everyone already said there are multiple warnings not to downgrade once using the official 2.3.4 update for this very reason. If I recall correctly it even said so in the text message I received that informed me of the update.
My Atrix has the same situation, someone find a solution?
There is no solution for a hard brick.
Sent from my MB860 using XDA App
pls chk this link hope ur prob will solved http://forum.xda-developers.com/showthread.php?t=1182871
motorola atrix mb860 now a paper waight
phone was already rooted using gingerbreak. attempted update through settings and it would download but fail to install.
i had install cwm, everything was fine.
but think i tried a update file, that gave me the failed to boot 2 with motorola logo.
well was spending endless time on forums trying to understand what, mistake i did.
and tried the rsd lite and using preinstall rsd lite file. then got the failed to boot 0x1000 no os detected. with 14 options, and nothing seem to work.
no file would work. batter wont charge even tryed to hard charge cutting charger and going strait to battery ...
IF ANYONE KNOWS A FIX.. please inform me.
I didnt have this much a hard time with my htc vivid ...
IF THERE IS NO FIX , I WILL HAVE FUN SMASHING THE THING ..
anyways .
thankx for your time, hope to hear something good..
celticpayne said:
phone was already rooted using gingerbreak. attempted update through settings and it would download but fail to install.
i had install cwm, everything was fine.
but think i tried a update file, that gave me the failed to boot 2 with motorola logo.
well was spending endless time on forums trying to understand what, mistake i did.
and tried the rsd lite and using preinstall rsd lite file. then got the failed to boot 0x1000 no os detected. with 14 options, and nothing seem to work.
no file would work. batter wont charge even tryed to hard charge cutting charger and going strait to battery ...
IF ANYONE KNOWS A FIX.. please inform me.
I didnt have this much a hard time with my htc vivid ...
IF THERE IS NO FIX , I WILL HAVE FUN SMASHING THE THING ..
anyways .
thankx for your time, hope to hear something good..
Click to expand...
Click to collapse
You have a soft brick and can recover. I don't have time to find the links for you right now, but search for soft brick solutions.
You have a very common error with a common solution.
http://youtu.be/QiZdY9rw-uo
celticpayne said:
phone was already rooted using gingerbreak. attempted update through settings and it would download but fail to install.
i had install cwm, everything was fine.
but think i tried a update file, that gave me the failed to boot 2 with motorola logo.
well was spending endless time on forums trying to understand what, mistake i did.
and tried the rsd lite and using preinstall rsd lite file. then got the failed to boot 0x1000 no os detected. with 14 options, and nothing seem to work.
no file would work. batter wont charge even tryed to hard charge cutting charger and going strait to battery ...
IF ANYONE KNOWS A FIX.. please inform me.
I didnt have this much a hard time with my htc vivid ...
IF THERE IS NO FIX , I WILL HAVE FUN SMASHING THE THING ..
anyways .
thankx for your time, hope to hear something good..
Click to expand...
Click to collapse
Where you in the process of unlocking your bootloader?
how unbrick the hard bricked Atrix 4g. (svf 105:1:2 failed to boot 0x1000 entering nv
bivrat said:
Motorola Atrix 4G At&t show error"SVF:105.1:2 Failed to boot 0X1000"
whn i try to downgrade to v2.3 to v2.2.2 after flashing show this message
how can i solve it pls any 1 give me the solution
post it here
Click to expand...
Click to collapse
I got security boot key for my atrix 4g and used nvflash to encrypt it and now i got my hard bricked atrix back as it was before hard bricking. Process is too easy but nobody knows here on this site. if anyone want to unbrick the hard bricked atrix 4g then please contact me on. Cheers Motorola AT&T
Hi just hard brick my atrix and i get the messege 0x1000 Failed to boot
Entering recovery mode NVFLASH, to the moment there no solution for this.
Or there developers working on a fix for this...
lhenriquezc said:
Hi just hard brick my atrix and i get the messege 0x1000 Failed to boot
Entering recovery mode NVFLASH, to the moment there no solution for this.
Or there developers working on a fix for this...
Click to expand...
Click to collapse
No, no fix and no developers are working on a fix because it doesn't look possible and energy/demand is better spent on developing roms since people shouldn't be hard bricking with all the warnings. Sorry.
lhenriquezc said:
Hi just hard brick my atrix and i get the messege 0x1000 Failed to boot
Entering recovery mode NVFLASH, to the moment there no solution for this.
Or there developers working on a fix for this...
Click to expand...
Click to collapse
You have no option to enter fastboot? How are you sure that it is a hard brick instead of a soft brick?
I think is hard brick because i googled an it said when you got this messege:
"0x1000 Failed to boot
Entering recovery mode NVFLASH"
there no way to get back to recovery. i held about some that motorola can do it
but the warranty applied only to EU and i am from Santo Domingo. Of course i'd like
to find a way to get it back...
dont give up.
i bricked mine by mistake also. let keep the thread alive till someone comes up with a way. im not giving up on my atrix!!!!!
davidroger said:
i bricked mine by mistake also. let keep the thread alive till someone comes up with a way. im not giving up on my atrix!!!!!
Click to expand...
Click to collapse
This thread should die. There's all these warning all over the place! And I doubt a dev is willing to hard brick their device to try and find a solution.
Sent from my MB860 using XDA App
disapointed with developers
i usually cometo xda for very good apps and tweks....and all the goodies that this site offers, but when i thod that devs will be able to help out on HARD BRICKED ATRIX,seem as no one here care about offering real help to all of us with this terrible issue...i am not blaming no one for my own problems ,but lets face it...who else could help me with this issue...only you devs could do it and you now it....my question is when will you try to do it... i know there are real good devs here that can help us ...but that is only up to them...
No, the devs can't fix hard bricks. They would have fixed their own phones if they could have. You broke your device, period. Don't play with things before understanding them, and don't risk breaking your phone if you are going to cry when this happens.
Sent from my MB860 using xda premium
minchaca5 said:
i usually cometo xda for very good apps and tweks....and all the goodies that this site offers, but when i thod that devs will be able to help out on HARD BRICKED ATRIX,seem as no one here care about offering real help to all of us with this terrible issue...i am not blaming no one for my own problems ,but lets face it...who else could help me with this issue...only you devs could do it and you now it....my question is when will you try to do it... i know there are real good devs here that can help us ...but that is only up to them...
Click to expand...
Click to collapse
-.- did you not see all the warning all over the place?
Sent from my MB860 using XDA App
I actually hard bricked my device when I was unlocking the bootloader. But that was fixable because the automaded progeam had an option to fix a hard brock while unlocking the bootloader. What exactly were you doing to cause the hard brick?
i ca see you just talk and comment BEACAUSE you dont have a hardbricked atrix
---------- Post added at 03:30 AM ---------- Previous post was at 03:25 AM ----------
in stead of sending critics plese sit on my problem ....THEN SPEACK ABOUT IT
No, I comment on threads to see if I can help people. I really do hope they can found a way past hard bricks. I mean, there has for rio be a way with all these devs around.
Sent from my atrix using XDA App
DEVS PLESAESE WAKE UP
i got same problem.hard brick my atrix i just bought 3 days ago.
Failed to boot (0x1000)", followed by a quick "NVFlash" message then it shuts off.
getbingmail said:
i got same problem.hard brick my atrix i just bought 3 days ago.
Failed to boot (0x1000)", followed by a quick "NVFlash" message then it shuts off.
Click to expand...
Click to collapse
What were you doing right before you bricked it. I'm no dev but I may get a thread started about ways people have bricked their phones so people know what not to do, and maybe get devs to pay more attention to this subject.
Sent from my MB860 using XDA App
Sell it for spare pieces and buy another one.
Sent from my OC'd Motorola™ Atrix®
chilango plase shut up¡¡¡¡
Fix?
I had this same problem last night, I was attempting to unlock the bootloader when I was on stock gingerbread. If that's what you were doing I can help you. If not, I think you're out of luck. When that "failed to boot message" came up on mine, I googled like crazy and found that most people said it was a hard brick. so I tried to fastboot anyway and it worked, then I just went into my command prompt and did the fastboot oem unlock, it worked and my phone is now working fine, unlocked.
Looks like I'll be keeping this one stock.
The nvflash hard brick only happens if you flash the wrong sbf. after updating to gingerbread you cannot downgrade through sbf flashing. Instead of sbf flashing you should use fruitcakes. There is a fake hard brick by unlocking your bootloader when you have gingerbread installed. This is fixable by fastboot unlocking. simply put if you
get a failed to boot error like that and can't get into either fastboot or rsd mode you have a hard brick
Sent from my MB860 using xda premium
Hi Guys,
I'm guessing that there's nothing that can be done but last hope!
Last night i was trying to update my Gf's Optimus One with little success using KDZ, got to the point where it wouldnt boot, so flashed the original ROM back to it, during the process after a few minutes it gave an error code and the Flash was unsuccessful. Thought' id' reboot the phone into Emergency and try the flash again - it errored pretty much straight away - Pulled battery from phone - reinserted it and now nothing!
The phone will not respond to power on, USB insert, etc Just completely dead..
Im guessing i know the answer already - but is there anything that can bring this back from the dead.... Seriously in the Doghouse!
Cheers
Paul
This is Dev section , please post in general section !!
Sent from my LG-P500
Sorry - Can a mod please move this to the correct place.
Don't u have warranty???
Sent from my LG-P500 using Tapatalk
I bricked my phone the same way.
I was trying to flash the original russian Gingerbread with LGMDP and there was a cable connection problem... I chose to erase all data before flashing (EFS Erase ALL). If only mobile devices had BIOS...
No hope, unfortunately. You have to connect your chipset to a computer and manually write all data... Or send to LG Service Center. Just hope they'll fix it for free... (They can't detect how you wiped device's boot loader if all the flash memory is empty)
paulrgod said:
Hi Guys,
I'm guessing that there's nothing that can be done but last hope!
Last night i was trying to update my Gf's Optimus One with little success using KDZ, got to the point where it wouldnt boot, so flashed the original ROM back to it, during the process after a few minutes it gave an error code and the Flash was unsuccessful. Thought' id' reboot the phone into Emergency and try the flash again - it errored pretty much straight away - Pulled battery from phone - reinserted it and now nothing!
The phone will not respond to power on, USB insert, etc Just completely dead..
Im guessing i know the answer already - but is there anything that can bring this back from the dead.... Seriously in the Doghouse!
Cheers
Paul
Click to expand...
Click to collapse
read downgrading details along with error thread it will definately come back to life http://forum.xda-developers.com/showthread.php?t=1038338
http://forum.xda-developers.com/showthread.php?t=883314
shhbz said:
read downgrading details along with error thread it will definately come back to life http://forum.xda-developers.com/showthread.php?t=1038338
http://forum.xda-developers.com/showthread.php?t=883314
Click to expand...
Click to collapse
Thanks for the links - i was working my way through the second one at 3am this morning.. Yes - i've even tried Shaking it
The P500 community has produced some wonderful guides and looking at it seems like the device is almost impossible to Brick completely, just how this happened i havn't a clue, seems ive managed the almost impossible..
I'd more than likely be able to ressurect it if it responded to anything at all - but no power, and nothing when the USB is inserted, no vibration, no lights, no signs of life...
the phone may be under warranty, but ive got to dig out the reciept - and i cant even begin to think where that is..
Well anyway i've had to buy her a replacement today - ended up with a Samsung Galaxy Mini as they dont stock the Optimus one anymore. Closest thing i could find.
Cheers for the help guys - i guess next effort will be warranty repair.
dude pls try uninstallin all the lg drivers usb etc etc and then try it again...it happend to me but ive still managed to ressurect it so try this and after send it to warranty
Hi, everyone, I've recently HARD BRICKED my Samsung Galaxy MODEL: T959V with T-mobile. First off, I got pattern locked on my phone, yea I know I'm an idiot, LOL. Next I totally forgot my gmail password so I could not log back into my phone. So then I next decided to flash back to stock with odin 1.7 and T959UVJFD. tar file from this thread: http://forum.xda-developers.com/showthread.php?t=1047087. As a result, my phone would boot to the loading screen with the dashed circle and a battery display in the background and thus would not finish booting all the way. So I figured I would do more research and found that people would try flashing with the Eugene_2E_JK2_Froyo from this thread: http://forum.xda-developers.com/showthread.php?t=833024&page=49 and after flash back to stock. After I flashed with the Eugene rom this was when the phone completely died and would not turn on. I tried the take out the battery, holding down and up volume button and plugging into computer method but the computer would not detect it anymore. Now I don't know what to do. It won't turn on anymore and can't boot into download mode. Please help.. Thanks, and appreciate it.
I just got bricked too...Went to update my vibrant that was on eclair still...Try to update to froyo on Samsung Kies Mini...download went fine...then when finished...it wouldnt turn on....just ordered a JIG....should be here Tuesday...http://www.amazon.com/SainSmart-Don...73JQ/ref=sr_1_1?ie=UTF8&qid=1321751047&sr=8-1
and yes...my family on XDA...i tried every finger combination to try to get to download mode...Sitting outside waiting for ups as we speak...
You might need to look into a jtag, I wouldnt give up getting into download even if the screen is black. Some members have had sucess by pulling the battery, sim card and letting the vibrant settle for an hour or so. reset in odin and keep trying, your phone wont respond but odin may recognize it by the yellow com bubble.
im guessing u've tried this:
http://forum.xda-developers.com/showthread.php?t=848737
also read post #5 in this thread:
http://forum.xda-developers.com/showthread.php?t=1352334
be sure u understand what he says: he's basically just pretending the screen doesnt work and holding the buttons for the amount of time it would take to enter download mode. even tho the screen never responds, odin will suddenly recognize the phone. u can tell when this happens cuz that box in odin turns yellow. then flash JFD like normal or whatever ur gonna do.
good luck
Thanks for replying everyone.
Sugartibbs : I've been working on this all day. Yea, I definitely can't get it to work on odin. It's not being recognized at all. where can i get a jtag?
crypkilla : Yea I definately tried those two things already. I've searched all over the forum. I think it's time to take it in..... LOL. Is there a difference between the two models T959UV vs. T959V, in terms of the stock rom I was originally suppose to use?
that's a bummer.
i havent had a completely unresponsive phone before, but ive thought ive been pretty screwed a few times and the only other thing i know is that ive read people say that they've tried the same thing a hundred times and on the hundred and first time it worked and that's been my experience.
be sure and post if u do get lucky and fix it.
ascensi0n said:
Thanks for replying everyone.
Sugartibbs : I've been working on this all day. Yea, I definitely can't get it to work on odin. It's not being recognized at all. where can i get a jtag?
crypkilla : Yea I definately tried those two things already. I've searched all over the forum. I think it's time to take it in..... LOL. Is there a difference between the two models T959UV vs. T959V, in terms of the stock rom I was originally suppose to use?
Click to expand...
Click to collapse
You flashed wrong ROM and you're in wrong forum.
T-mobile Vibrant is T959
T-mobile Galaxy S 4G is T959V
T959UV is just a baseband not model number.
Sent from my T959 using XDA App
Yea I figured that I flashed the wrong rom after....so is there a way to fix it?
ascensi0n said:
Yea I figured that I flashed the wrong rom after....so is there a way to fix it?
Click to expand...
Click to collapse
First you need to get to download mode. Then try this
http://forum.xda-developers.com/showthread.php?t=1353176
Sent from my T959 using XDA App
ascensi0n said:
Yea I figured that I flashed the wrong rom after....so is there a way to fix it?
Click to expand...
Click to collapse
LOL i did the same thing ended up selling the phone :laugh:
Guys
My phone was modded -cyanogenmod rc1-. I used it for months and there was no problem until one day.Once I opened my phone it was just blank screen.Also there is no light on keys.Also I can't get into hboot or clockwork mode screen.I am not really good at these technical problems.But somehow I modded it What can be the problem if it is not a device problem? How can I fix it?
I have already searched for similar problems but I couldnt understand the detailed explanations.
Please explain for a newbie
Thanks for your help.
Take out your battery, plug it back in while holding Vol down + power and see will it get into HBoot
kemoba said:
Take out your battery, plug it back in while holding Vol down + power and see will it get into HBoot
Click to expand...
Click to collapse
it was good to try something new but it didnt work.still just the backlight, nothing on the screen.
Then probably it's something wrong with the data itself, you probably installed some bad app that bootlooped your phone, your only option is to give some logcat to us or to reinstall the rom and start all over again, maby its time for an update, flash elelinux 2.3.7
kemoba said:
Then probably it's something wrong with the data itself, you probably installed some bad app that bootlooped your phone, your only option is to give some logcat to us or to reinstall the rom and start all over again, maby its time for an update, flash elelinux 2.3.7
Click to expand...
Click to collapse
how can i do these if i cant go into flashing screens which you get into pressing vol and power buttons.can you show me some way?
btw thanks for you help : )
bartified said:
how can i do these if i cant go into flashing screens which you get into pressing vol and power buttons.can you show me some way?
btw thanks for you help : )
Click to expand...
Click to collapse
Oops sorry but this post was ment to the guy that has a bootloop on elelinux 2.2, if you cant get into HBoot then either you hard bricked your phone or there is something wrong with your screen...
what can be the possible solution for hard bricked phone then : )
I dont think it's a hard brick since you would atleast get to HERO sign (i think) but if it is a hard brick then your only option is JTag..
kemoba said:
I dont think it's a hard brick since you would atleast get to HERO sign (i think) but if it is a hard brick then your only option is JTag..
Click to expand...
Click to collapse
no no i cant get anything.only black screen.i cant see anything and i cant access to recovery mods or hboot screen.
How do you know you are not getting into HBoot if your screen is lets say malfunctioning ? I think there is a better possibility for a screen failture then a hard brick, it's not easy to hard brick a phone, and it's inpossible if you were just using your phone on CM7, only way to brick it is a failed HBoot/Radio update... I'd get a new screen there, or it could be the motherboard that failed.