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
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 all...
I saw this thread already on other forums, but there was not enough detail to explain the trouble, so this topic.
I am affraid there is a trouble on some devices when you update to 2.3.4 (GENERIC GLOBAL) then downgrade to 2.3.2 (GENERIC GLOBAL) with the reason of ROOT them, battery looks dead, but is not.
I saw on the forum in two different devices already, and yesterday it happened to me as well.
So I tell you what I've done, and I really hope there will be a solution.
- my phone (MT15i) shown me a message, that there is a new software available. I wanted to try how is that, so I made a system backup, relocked the bootloader and then I updated via SEUS. Everything was fine, with it, except that little problem, that I wanted my baby to be rooted.
- downgraded to 2.3.2 (GENERIC GLOBAL) via SE Flashtool 2.9.1, to complete the GingerBreak treathment (I've done this due to the locked bootloader)
- GingerBreak has been successfuly completed, phone restarted, battery were on 0%, I knew this can be normal, so I switched off, removed the battery for 1 min and restarted.
- And the nightmare began: THE BATTERY STAYS ON 0% and the phone goes off. If I plug the device to the mains, stays on, looks like is charging, but it does not.
I've tryied other battery same issue. I tried my batteries in other NEO, the were perfectly fine.
Funy is, I unlocked the bootloader again, and I can do any operation with my phone like such a ClockWork Recovery or flashing it, but I can not start the ANDROID O/S a without mains.
Please guys help me, and those who have the same experience with Arc/Neo/X10.
Many many thanks.
Remove battery, and put it back after 10 minutes.
I have tried even for two hours. Nothing changed, same issue, but thank you anyway..
Also "battery calibration etc battery stats wipe?
Yes my friend. All of these things I tried. Even reflashed sytem and boot images with fastboot (I guess this has nothing to do with bootloader, but I gave a try)... No changes..
broken bootloader, search this forum...
Enough information is on these forums about rooting without needing to relock the bootloader, like RootXperia method.
That very day there was not solution yet for the latest S/W update about rooting it. But I already tried many solution I can find here, but there is no luck.
Your problem, but your spreading false information. Rooting method has been available before 2.3.3 and is same for all FWs
No matter which FW you have anyone can root if they have unlocked bootloader, just get RootXperia.zip and install via recoveryNeo.img
Search
Yeah, the thing is, I wanted to relock my bootloader, and doing the OTA update. From 2.3.2 to 2.3.4. Please read what I wrote again. And that time I did not found anything about rooting the 2.3.4.
Cheers
Raoa said:
No matter which FW you have anyone can root if they have unlocked bootloader, just get RootXperia.zip and install via recoveryNeo.img
Search
Click to expand...
Click to collapse
I's it true?
Sent from my MT15i using Tapatalk
battery 0%
taaviu said:
I's it true?
Sent from my MT15i using Tapatalk
Click to expand...
Click to collapse
Yeah i've rooted all my FWs with RootXperia.zip
OTA is if you have locked bootloader, the whole method of going back to 2.3.2 is to not unlock bootloader and get root. To go through that with already unlocked bootloader is like going around when you could go straight.
The reports of, oh wait... this is not the first time OTA bricks phones. Wasn't it with 2.3.3 Arc update as well. So why do people fall to same trap?
Really there's enough relevant information on Arc forum, read up before doing something you don't need to do. It's a phone so thrashing around with flashing in any random way will end with bricked phones. It's your fault for not reading up and thinking well. SE might do something stupid with all these people bricking their phones in ways and for a reason they should not.... for customer protection. That would suck for us all.
Raoa said:
Yeah i've rooted all my FWs with RootXperia.zip
OTA is if you have locked bootloader, the whole method of going back to 2.3.2 is to not unlock bootloader and get root. To go through that with already unlocked bootloader is like going around when you could go straight.
The reports of, oh wait... this is not the first time OTA bricks phones. Wasn't it with 2.3.3 Arc update as well. So why do people fall to same trap?
Really there's enough relevant information on Arc forum, read up before doing something you don't need to do. It's a phone so thrashing around with flashing in any random way will end with bricked phones. It's your fault for not reading up and thinking well. SE might do something stupid with all these people bricking their phones in ways and for a reason they should not.... for customer protection. That would suck for us all.
Click to expand...
Click to collapse
What can we do?
I have a unlock bootlander.
Scroll down this forum and you'll see http://forum.xda-developers.com/showthread.php?t=1254409 Get a new battery or connect USB wires to - and + battery connectors and try it or send it to repairs.
Unless any dev finds yet another method to unbrick this new batch of phones then nothing else can be done.
Raoa said:
broken bootloader, search this forum...
Enough information is on these forums about rooting without needing to relock the bootloader, like RootXperia method.
Click to expand...
Click to collapse
I can confirm is not bootloader problem
Maybe is something with trim area.
This can be fixed but if you have warranty is better to send it to SE
Anyway if someone want to try this method to repair the trim area please contact me by PM.
Also anyone with working locked or unlocked NEO I need some trim area backups to acn repair others phones.
Please if you want to help send me a PM, the backup process is as easy as connect in flashtool by pressing back key
Raoa said:
Scroll down this forum and you'll see http://forum.xda-developers.com/showthread.php?t=1254409 Get a new battery or connect USB wires to - and + battery connectors and try it or send it to repairs.
Unless any dev finds yet another method to unbrick this new batch of phones then nothing else can be done.
Click to expand...
Click to collapse
Rember this was my same problem Raoa,, you told me to reflash with a difernt ftf file,,, problem was fixed there and then,,,
Sent from my MZ604 using xda premium
I am not so certain it is the exact same situation, Kormatoes. IF it's not a bootloader problem then I don't know what it is.
IF this would be fixed as easily as flashing a full working FW... well worth a try, nonetheless.
It is not a randomly flashing around and I DO WANTED my bootloader to be relocked and not open it again.. I used to flash my phone without any problem. I never had any problem repair anything. Since SonyEricsson and then Xperia exists, I know what to do with them if they are sick. I had enough experience, and I know you can find solutions on the forum, this is why you can see that from my posting history, that since I am member of XDA, never had stupid questions. I knew what to do when phone was bricked because of unlocked bootloader+over the air update. It is a simple accident that can happen to anyone. And here I asked for solution not for meaningless words, where some people try to show how brilliant and perfect they are. This is a development website, we are here to help for eachother or on those who needs help. So please stop to sue anyone, and help or please just do not reply for threads that you think is stupid, moderators/operators will deal with those. Just keep the rules of the website.
BTW, this MUST be a software problem, as I tested the battery, works perfectly in other devices, the phone is all okay about the 'elctrovise'
As I saw this on ARC's forum as well, this happened there in same way: Update to 2.3.4 then downgrade to any of the previous S/W versions, caused this. So I think this situation will incrase soon, this why I thing we need to find a solution as well. I normally working with Linux/ubuntu laptops. I had simular issue, but then was just the battery. Now... I dont know.
laceex said:
It is not a randomly flashing around and I DO WANTED my bootloader to be relocked and not open it again.. I used to flash my phone without any problem. I never had any problem repair anything. Since SonyEricsson and then Xperia exists, I know what to do with them if they are sick. I had enough experience, and I know you can find solutions on the forum, this is why you can see that from my posting history, that since I am member of XDA, never had stupid questions. I knew what to do when phone was bricked because of unlocked bootloader+over the air update. It is a simple accident that can happen to anyone. And here I asked for solution not for meaningless words, where some people try to show how brilliant and perfect they are. This is a development website, we are here to help for eachother or on those who needs help. So please stop to sue anyone, and help or please just do not reply for threads that you think is stupid, moderators/operators will deal with those. Just keep the rules of the website.
BTW, this MUST be a software problem, as I tested the battery, works perfectly in other devices, the phone is all okay about the 'elctrovise'
As I saw this on ARC's forum as well, this happened there in same way: Update to 2.3.4 then downgrade to any of the previous S/W versions, caused this. So I think this situation will incrase soon, this why I thing we need to find a solution as well. I normally working with Linux/ubuntu laptops. I had simular issue, but then was just the battery. Now... I dont know.
Click to expand...
Click to collapse
I have the ****ed same problem!!
batery 0%....
i tried flash to other versions and no get solution..
wipe batery stats none
.......
ANY IDEA?
anikill3010 said:
I have the ****ed same problem!!
batery 0%....
i tried flash to other versions and no get solution..
wipe batery stats none
.......
ANY IDEA?
Click to expand...
Click to collapse
I am affraid we still have to wait until more people will have the same problem. Right now there is no solution, only to leave on charger. Why not. A little retro. Just like a landline phone
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.
Hi all,
I have looked for a similar post, I found out that many people experienced something like that trying unlocking their phones, but I haven't found out any solution.
Here is my situation:
I have tried to unlock my s5830 (orange spain carrier), I have used a method which it seems to be dangerous for the phone, but of course I have found out it was dangerous after I have already tried it
Anyway after I discovered the unlock number contained in the perso.txt file in the efs folder, my phone restarted without service once and after that it went in a bootloop mode, it goes on a download mode, but there is no way to get back recovery mode or a normal boot.
I flashed the s5830 several times with many firmware, but no one worked, and the phone is still stuck in an infinite loop, in which I am not even able to see the samsung logo coming out at the very beginning.
I know many phones got bricked in this way, I wanted to know if anybody has been able to recover the phone or if anybody know any possible solution.
And if not, do you know if the warranty is covering this problem? I just got the phone a couple months ago; i have unlocked other devices before, but this is the first time I have experienced a problem so I am quite new about warranty as well. Please HELP ME
Merry Christmas guys!!!
Thanks in advance
sfrat said:
Hi all,
I have looked for a similar post, I found out that many people experienced something like that trying unlocking their phones, but I haven't found out any solution.
Here is my situation:
I have tried to unlock my s5830 (orange spain carrier), I have used a method which it seems to be dangerous for the phone, but of course I have found out it was dangerous after I have already tried it
Anyway after I discovered the unlock number contained in the perso.txt file in the efs folder, my phone restarted without service once and after that it went in a bootloop mode, it goes on a download mode, but there is no way to get back recovery mode or a normal boot.
I flashed the s5830 several times with many firmware, but no one worked, and the phone is still stuck in an infinite loop, in which I am not even able to see the samsung logo coming out at the very beginning.
I know many phones got bricked in this way, I wanted to know if anybody has been able to recover the phone or if anybody know any possible solution.
And if not, do you know if the warranty is covering this problem? I just got the phone a couple months ago; i have unlocked other devices before, but this is the first time I have experienced a problem so I am quite new about warranty as well. Please HELP ME
Merry Christmas guys!!!
Thanks in advance
Click to expand...
Click to collapse
if you can get into download mode im guessing there is some hope for you.
go here: http://droidangel.blogspot.com/2011/05/samsung-galaxy-ace-s5830-original-stock.html
look for: S5830XXKP9
and make sure you have odin 4.38 and flash with that.
try to install cwm and install a customrom
Sent from my GT-S5830 using xda premium
sfrat said:
Hi all,
I have looked for a similar post, I found out that many people experienced something like that trying unlocking their phones, but I haven't found out any solution.
Here is my situation:
I have tried to unlock my s5830 (orange spain carrier), I have used a method which it seems to be dangerous for the phone, but of course I have found out it was dangerous after I have already tried it
Anyway after I discovered the unlock number contained in the perso.txt file in the efs folder, my phone restarted without service once and after that it went in a bootloop mode, it goes on a download mode, but there is no way to get back recovery mode or a normal boot.
I flashed the s5830 several times with many firmware, but no one worked, and the phone is still stuck in an infinite loop, in which I am not even able to see the samsung logo coming out at the very beginning.
I know many phones got bricked in this way, I wanted to know if anybody has been able to recover the phone or if anybody know any possible solution.
And if not, do you know if the warranty is covering this problem? I just got the phone a couple months ago; i have unlocked other devices before, but this is the first time I have experienced a problem so I am quite new about warranty as well. Please HELP ME
Merry Christmas guys!!!
Thanks in advance
Click to expand...
Click to collapse
with the cellphone off, put out ur baterry for a minute, then maintain ur finger into the volume down button and the power button tell a friend or if u can alone insert the batery while quickly pressing volume down and power button to get into download mode, and flash.
Hehehe,bootloop is horrible,you just have to get in download mode & flash with 2.3.4 firmware with Odin,just that steps and you save your SGA.
I got bootloop many times and Odin saved me.
Sent from my SGA
robinandroid said:
try to install cwm and install a customrom
Sent from my GT-S5830 using xda premium
Click to expand...
Click to collapse
he cant go back in recovery mod............
If you can go to recovery mode than you can just wipe the data and cache. This saved me many times. Otherwise on what ever OS you may be , just create new user name after removing samsung android drivers. Login from new user name and than re install drivers again and now flash your phone from firmware which was installed on your phone before you bricked it. This helped me a few times.
dr_vishal said:
If you can go to recovery mode than you can just wipe the data and cache. This saved me many times. Otherwise on what ever OS you may be , just create new user name after removing samsung android drivers. Login from new user name and than re install drivers again and now flash your phone from firmware which was installed on your phone before you bricked it. This helped me a few times.
Click to expand...
Click to collapse
hey guys thanks for the answers, but unfortunately i am not able to reach the recovery mode, my phone just reach the download mode.....i will try with the xxkp9, even if i have already tried it...I guess i have tried at least 15 firmwares without any success
Helping to make your Christmas Merry
It seems that you've already received a lot of help for unbricking your device. So I'll try to help out in unlocking your phone after you finished unbricking it.
This is the method I personally used on my locked Ace:
http://forum.xda-developers.com/showthread.php?t=1335548
It's perfectly safe. 100%.
King Kaze said:
if you can get into download mode im guessing there is some hope for you.
look for: S5830XXKP9
and make sure you have odin 4.38 and flash with that.
Click to expand...
Click to collapse
I have tried the XXKP9 again, it is not working, as usual Odin ends to load the firmware and then it goes back in the endless loop mode....there is no chance to get it back?
franzks said:
It seems that you've already received a lot of help for unbricking your device. So I'll try to help out in unlocking your phone after you finished unbricking it.
This is the method I personally used on my locked Ace:
http://forum.xda-developers.com/showthread.php?t=1335548
It's perfectly safe. 100%.
Click to expand...
Click to collapse
thank you very much I will follow your advice...IF I will be able to get my phone back which seems impossible =(
@dr_vishal
Thank you first of all, I have tried to uninstall and reinstall the android device driver, but it doesn't seems to be the problem, Odin ends with a "PASS" at the end, I guess there still is comunication in the between the two devices...
Hopefully it will be a Merry Christmas =)
It's not impossible. I'm relatively new here but I have noticed quite a few "bricked" threads already. Most of them (if not all) have been able to fix their device. I haven't seen a single person permanently brick their device, so I would guess that your chances of fixing it are really high. Just be patient and keep describing your situation and more experienced help will certainly arrive. I'd really like to help out but I have no idea how to fix it as I have not experienced bricking my phone yet.
Anyway, if the method for unlocking I suggested works for you kindly press the Thanks Button. Merry Christmas!
franzks said:
It's not impossible. I'm relatively new here but I have noticed quite a few "bricked" threads already. Most of them (if not all) have been able to fix their device. I haven't seen a single person permanently brick their device, so I would guess that your chances of fixing it are really high. Just be patient and keep describing your situation and more experienced help will certainly arrive. I'd really like to help out but I have no idea how to fix it as I have not experienced bricking my phone yet.
Anyway, if the method for unlocking I suggested works for you kindly press the Thanks Button. Merry Christmas!
Click to expand...
Click to collapse
Thank you franzks!
I promise I will try your method and I am positive it will works, but I need to get my phone back...so I will add few new information I have found out talking to a friend of mine which has my same device and the same carrier as well.
The version built-in is:
GINGERBREAD.BVKQ9
S5830BVKQB
[email protected]#1
Any suggestion about the firmware I am suppose to flash in?
I am actually passing through all the version contained in the address droidangel you gave me...at the moment no one is working...I will keep trying...
sfrat said:
Thank you franzks!
I promise I will try your method and I am positive it will works, but I need to get my phone back...so I will add few new information I have found out talking to a friend of mine which has my same device and the same carrier as well.
The version built-in is:
GINGERBREAD.BVKQ9
S5830BVKQB
[email protected]#1
Any suggestion about the firmware I am suppose to flash in?
I am actually passing through all the version contained in the address droidangel you gave me...at the moment no one is working...I will keep trying...
Click to expand...
Click to collapse
Guys,
I am out of ideas, I have tried each single firmware I have seen around internet, no one is working, any tip or advice or suggestion?
I messed up with the efs, and I guess that's all, the phone is gone....now it needs a JTAG or whatever is its name....
maybe to get the warranty still valid I should broke totally the phone over charging it....??
sfrat said:
Guys,
I am out of ideas, I have tried each single firmware I have seen around internet, no one is working, any tip or advice or suggestion?
I messed up with the efs, and I guess that's all, the phone is gone....now it needs a JTAG or whatever is its name....
maybe to get the warranty still valid I should broke totally the phone over charging it....??
Click to expand...
Click to collapse
Did you try that?
http://forum.xda-developers.com/showthread.php?t=1153310
just a thought
a lot of people have talked about reflashing it and all but have you managed to get into the recovery mode at all once you have reinstalled the rom with odin? if you can get to that you just need to hit factory reset, wipe cache and wipe dalvik and normaly after that it will work fine... so far ive been stuck in soft brink 3 times and each time doing the wipes from the recovery mode has worked...
Pinting said:
Did you try that?
http://forum.xda-developers.com/showthread.php?t=1153310
Click to expand...
Click to collapse
I've tried to use the oneclick, but it seems it doesn't recognize the phone, since, i guess, it's made for a galaxy s.
The others are not my case, since I am able to get download mode, and all these are made to can get it back.
Anyway I found out a post in which the people were talking about the s5500, which apparentely is similiar to my device, and the owners of that model experienced a similar problem doing the same process....anyway in that post the people needed to use a Jtag, which is the only way to get it back....so I though it could be the same solution for my problem...but I don't know anybody with Jtag, so the only way is contacting the service center.
thanks anyway, when I will be back at home after Christmas I will try to find the ticket and I will probably try to get it back in warranty, since is preatty new...
@torchwolfery
I am not able to reach recovery mode, there is no way to get it back, even flashing the phone with different firmwares, all I got is download mode, and apparently that is completely pointless...since the only change in the phone behavior is that if i install a certain firmwares it doesn't even have the back-light working when it is stuck in bootloop.
Warranty is your only hope (as it was mine once and it worked).
I didn't think it was possible to brick these phones. There I have tried so much to try and brick it but I have not been able to as it still always goes into 'download' mode. The only advice I can give you is double check that you are using the correct version of Odin which is v4.38 and that you use cooper v1.0 as your OPS. If dont mind me asking, but exactly what did you do or do you remember the steps you took to brick it? What buttons are you using for 'recovery' mode.
Also please clarify if Odin is going in a loop or does the phone come on and then keeps rebooting? If it is the phone that keeps rebooting, then wiping cache and data partition should do the trick. This can be done by going into recovery mode (which I am aware you cannot get into) or if you can manage to get into the dialler quick enough before the reboot, by dialling *7267*3855# and that should format the relevant partitions (data and cahce) and bring it back to factory settings. Without further info, I cannot really tell exactly what the situation is.
The fact that you are getting 'download' mode, I dont think that it is bricked because it will still allow you to write the relevant directory/files to the relevant blocks. Either way, would be interested to know.
Hi!
I just had the weirdest experience with my sgsii
I have been using the unofficial vsync patched cm10 rom for this modelfor the last month or so.
I have been updating at least one per week but this week I decided to give my phone a break and not flash it... i am actually really busy at job.
Suddenly tonight, the phone looked like when you have a SOD... so i just pulled the battery.
Now, it does not pass from the first logo stage, just prior to start booting.
I cannot access cwm recovery either, but download mode seems to work-
Now the odd thng is that i am attempting to flash somethng to get the phone working but it gets stuck in the step "NAND Write start!".... it goes no furter than that...
I have chosen the options auto reboot and f.reset time.
a pda file, phone and csc file from the eaked jb rom.....
The system I am attempting to flash from is a windows 7 pro 64 bit.... and odin is Odin3 v1.85...
Please, tell me i didnt get a brick and there is a way tofix it... :crying:
EDIT: Desperated, i tried to flash latest jb leak again, and chose the pit file that comes with it, which re-partitions the phone...
After 20 minutes not responding, i pulld the battery out... now i cannot even enter download mode....nothing....nada....
Sounds like you bricked it, good job.
Sent from my GT-I9100 using Forum Runner
GFXi0N said:
EDIT: Desperated, i tried to flash latest jb leak again, and chose the pit file that comes with it, which re-partitions the phone...
After 20 minutes not responding, i pulld the battery out... now i cannot even enter download mode....nothing....nada....
Click to expand...
Click to collapse
too bad never repartition unless you make your own pit file with heimdall .. if you would've wait a couple hours I just pmed you.
and for other people instead of flashing samsung's bricksquadroms you can flash CM9 resurrection edition. http://forum.xda-developers.com/showthread.php?t=1419102
Make a pit file with heimdall of your own device. Don't trust pitfile that comes with a rom.
I re-partitioned my device and i got like 3GB intern memory back.
There's probably a way to get your device alive. it isn't the mmc cap bug so. search some threads on xda about brickbugs etc of galaxy phones and you'll find people who hardbricked and unbricked their device.
Probably usb jig could get you into download mode i'm not sure though. Or else jtag. Ask some people over there they will know it
I will try to revive it with jig.... i must find the thingy though.,..... if not.. i will send it to the service but i'm not sure i'm on warranty....
Being not patient made me f*ck it up bad....
Any clue on how to recover a phone after re-partitioning.... i really don't know where to start...
EDIT: JIG does not switch it on either... why did i have to re-partition?!??!?!?!?!?!
That was a dumb move....... any more ideas?
If you cant enter recovery or download mode you have no choice but to JTAG repair or mobo replacement.
Hard brick.... on its way to service
Wish me luck..
Mobo replacement it is, this incident will at least teach you to be patient, I explained you my problem in PM, I waited for 1 week for USB jig to arrive from eBay then flashed stock ROM. I trust the f/w it came with the most.
Sent from my GT-I9100 using xda app-developers app
Sh4Dy said:
Mobo replacement it is, this incident will at least teach you to be patient, I explained you my problem in PM, I waited for 1 week for USB jig to arrive from eBay then flashed stock ROM. I trust the f/w it came with the most.
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
USB JIG didn't work at all..... I have one and it was not able to boot the phone ....
Isn't this kind of brick fixable with Jtag?
Sent from my GT-I9100
Ok, before I repartitioned, making the problem worse, I was experiencing some kind of R/W problem..... there was something odd with the nand because I was able to boot in download mode, but not in recovery (CWM) mode....
Then, when I plugged the phone to the computer, Odin was able to recognize the phone.
I followed some thread around XDA to flash 4.1.2 leak from sammy and when I hit the "Start" button in Odin, it would not pass from the first stages, revealing that R/W or I/O problem.... the internal nand was, somehow broken.... it didn't read or write properly.... so, even If i could find a workaround, I would have lost some internal storage (some posts talk about around 3 Gb or something similar as lost space in these cases).... that is IF i had been able to fix it..... but then, that's what warranty is for..... so I gave it a last (dumb) try..... including the pit file, which attempted a format, which ended messing (i would say the f. word) everything up.
The good side is that unable to even boot, at least i lost the blue loading bar the vsync patched cm10 mod has in the first bootup screen.... which could have revealed to sammy that I was tempering with unofficial roms....
Lesson learned: Be patient people: But also, don't think this could not happen to you: The phone was perfectly working the last time I saw it... and I even was making some phone calls and browsing the internet.... I mean... it gave no prior symptoms or warnings... I t just died..... I guess I have to be glad I'm not one of those people whose phone gets caught up on fire on their pockets for malfunctioning.....
Now waiting for it to come back revived from samsung..... I have hope
hope it will be able to recover
Great: After losing the phone and past almost three months, samsung says the phone has been manipulated and the warranty is voided....
I wasn't able to flash back an original firmware prior to sending it to the tech service.....
What do you recommend me to do?
I guess paying for the repair would be quite expensive....
GFXi0N said:
Great: After losing the phone and past almost three months, samsung says the phone has been manipulated and the warranty is voided....
I wasn't able to flash back an original firmware prior to sending it to the tech service.....
What do you recommend me to do?
I guess paying for the repair would be quite expensive....
Click to expand...
Click to collapse
Well what is it you expect us to say, some secret magic word that will fix it for free?
The choice is pay for it to be fixed or dont.
So no magic word or secret passphrase so they will upgrade my device to a SGSIV for free?
Damn.....
I'm asking for advice, since I'm convinced the brick was not caused by flashing anything.....
Does anyone have any experience with this in the past to know more or less how expensive bill could I be facing for the repair?
GFXi0N said:
So no magic word or secret passphrase so they will upgrade my device to a SGSIV for free?
Damn.....
I'm asking for advice, since I'm convinced the brick was not caused by flashing anything.....
Does anyone have any experience with this in the past to know more or less how expensive bill could I be facing for the repair?
Click to expand...
Click to collapse
Dude, it WAS caused by flashing something.
Initially your device wasn't "bricked" and was likely a kernel issue and possibly a dirty usb data connection.
The point when it was bricked was when you tried flashing the pit file, had bad connection and you then pulling battery. This f**ked your nand chip up and only way to fix it is to replace motherboard.
You will need to either purchase a mobo replacement and replace it yourself or pay somebody to purchase/replace it for you. Probably looking at around £100.
When bricks happen, you really need to BRICK it before claiming warranty.
I've got a couple of guys here that own a PhD in bricking.
Brick is the new flash.
Sent from the little guy
Jig wasn't working
Flashing anyting.. even just a recovery wasn't working
FLashing official didnt work
Flashing CM didnt work either
Tested different cables and different ports
It was f*cked up already... anyway: 4 samsung devices owned: 3 gave problems of hardware..... that cannot be a coincidence...
Repartitioning erased my tracks, if anything... because the 3 key combo for recovery was working until then..... but either way they managed to access the memory somehow, I guess.....
GFXi0N said:
anyway: 4 samsung devices owned: 3 gave problems of hardware..... that cannot be a coincidence....
Click to expand...
Click to collapse
Maybe a PEBCAK?
GFXi0N said:
Jig wasn't working
Flashing anyting.. even just a recovery wasn't working
FLashing official didnt work
Flashing CM didnt work either
Tested different cables and different ports
It was f*cked up already... anyway: 4 samsung devices owned: 3 gave problems of hardware..... that cannot be a coincidence...
Repartitioning erased my tracks, if anything... because the 3 key combo for recovery was working until then..... but either way they managed to access the memory somehow, I guess.....
Click to expand...
Click to collapse
Don't blame the phone, blame the user.
Yeah, sure... anyway... thanks for the help... I hope some day you need it and someone will come not trying to mocking you..... anyway... this is the trend around here lately...
Happy trolling