Related
I am real close to confirming a FIX to at the least get MY hermes and other outta being stuck in limbo. Quick Run Down: I HAD my HERMES stuck it Bootloader Mode, well it would get stuck everytime I tried to flash the OS ROM with WM6 (the offical ROM from HTC site)The upgrade process would start, but then it would get stuck at 11% EVERYTIME!! I could get it back at all!! It was stuck in Tri Color Mode!! But a guy I know(guy I bought the Hermes from) is a MASTER at this stuff. He knew more than ANYONE here and he doesnt even use a HERMES?? Anyways I am gonna try my method 1 more time to confirm that it works!! But here is the kicker I have NO GSM after recovering from this HORRIBLE error!! So if you want ur hermes back to use the wifi at least, STAY TUNED!!
NOTE: My METHOD isnt the casuse of the NO GSM, I think I did that when i messed up flashing my OS ROM
But I do NEED to know on how to get my radio back?? I now have a NO GSM error when I turn my hermes on!! I am using the Official WM6 ROM from HTC
nicknowsky said:
I am real close to confirming a FIX to at the least get MY hermes and other outta being stuck in limbo. Quick Run Down: I HAD my HERMES stuck it Bootloader Mode, well it would get stuck everytime I tried to flash the OS ROM with WM6 (the offical ROM from HTC site)The upgrade process would start, but then it would get stuck at 11% EVERYTIME!! I could get it back at all!! It was stuck in Tri Color Mode!! But a guy I know(guy I bought the Hermes from) is a MASTER at this stuff. He knew more than ANYONE here and he doesnt even use a HERMES?? Anyways I am gonna try my method 1 more time to confirm that it works!! But here is the kicker I have NO GSM after recovering from this HORRIBLE error!! So if you want ur hermes back to use the wifi at least, STAY TUNED!!
NOTE: My METHOD isnt the cause of the NO GSM, I think I did that when i messed up flashing my OS ROM
Click to expand...
Click to collapse
The reason the official ROM died at 11% is because around 11% the radio portion of the ROM (radio.nb inside the nbh file) is being flashed to the device. Simple remedy to this to get your device booting into windows mobile is to flash an OS only ROM (nearly ALL the cooked WM6 versions are OS only...but you can make any ROM OS only using duttys nbh tool). This will get you back into window mobile but your problem is that the device has a corrupted radio flash on it.
The problem, as i have already explained in your other thread about this, is that since your flash procedure was halted by you accidentally resetting the computer halfway through a flash the radio portion of the flashing process was probably interrupted and therefore you have most likely caused an irreversible corruption of the radio area.
Unfortunately for you this is probably the only way now to permanently brick your device, as in the device is no longer a phone it is a pda only......in my opinion still a brick.
As I have already explained the only thing to try is (once your device is bootable) to try and flash a radio only ROM.......if this doesnt work im sorry but you have no options, unless you can actually get physically at the chip with JTAG or some other hardware flasher.
The tone of your post in this thread, this post AND this post suggests that we on this forum have not been forthcoming to help you fix your problem......not true. And regrarding your 'Fanboys' rant earlier had you actually read the wiki and un-bricking threads you would see that ALL the info required to revive a hermes (if it is indeed recoverable) has been well documented for over a year now.
NO this method has BROUGHT me outta Tri-color mode twice already, everyone who seems to have this problem has a COMPLETELY USELESS Hermes it wont even turn on, at the leaset MY way will get u back into Windows Mobile, (it worked for me)
yes...as i said in this sentence above:
This will get you back into window mobile but your problem is that the device has a corrupted radio flash on it.
Click to expand...
Click to collapse
Again your device still has a corrupted radio thus isnt working correctly. Having a Tytn which has a non-existant radio is as bad as a total brick.
OKAY if AND when you are able to START the UPDATE process, meaning you see the PROGRESS BAR appear on your HERMES and ur computer. PULL THE USB CABLE AND as FAST AS HUMANLY possible hit the SOFT RESET button!!!
I mean AS SOON AS YOU SEE THE PROGRESS BAR appear on ur HERMEs, You gotta yank out the USB and HIT RESET SUPER FAST, it will shock ur HERMES and bring you back into Windows Mobile!!!!!
nicknowsky said:
OKAY if AND when you are able to START the UPDATE process, meaning you see the PROGRESS BAR appear on your HERMES and ur computer. PULL THE USB CABLE AND as FAST AS HUMANLY possible hit the SOFT RESET button!!!
I mean AS SOON AS YOU SEE THE PROGRESS BAR appear on ur HERMEs, You gotta yank out the USB and HIT RESET SUPER FAST, it will shock ur HERMES and bring you back into Windows Mobile!!!!!
Click to expand...
Click to collapse
Please explain to us all what good that will do? Your radio area is still corrupt.
Now I dunno I have NO GSM, big deal, that is FIXABLE and I dunno if this IS the CAUSE of having NO RADIO
IF YOU WANT to at the LEAST HAVE A Hermes to BEGIN to FIX give it a try, , I have BROUGHT MY HERMES outta be stuck in TRI COLOR Mode 3 times by following this METHOD, I didnt have a GSM but I dunno what the cause of that is, you might have to flash a RADIO or whatever to get that BACK, but if you want the HERMES back to AT least play with GIVE it A SHOT
ffs, READ.....
NO GSM and an error during flash points to a PERMENANTLY dead radio area on the device...ie NOT ABLE TO FIX THIS.
when your computer was reset it resulted in a failed radio flash...dead radio. There is no way to fix this.
nicknowsky said:
OKAY if AND when you are able to START the UPDATE process, meaning you see the PROGRESS BAR appear on your HERMES and ur computer. PULL THE USB CABLE AND as FAST AS HUMANLY possible hit the SOFT RESET button!!!
I mean AS SOON AS YOU SEE THE PROGRESS BAR appear on ur HERMEs, You gotta yank out the USB and HIT RESET SUPER FAST, it will shock ur HERMES and bring you back into Windows Mobile!!!!!
Click to expand...
Click to collapse
Did not work on my hermes
who said anything about Dead Radio?? I dunno if thats the case I see NO GSM thats it, I know nothing further. If you are so wanting to help now, WHY didnt you DO a better job of helping me earlier?? Now ur saying my phone is busted, I dunno whatever I will deal with it, STEP UP dude and help out BETTER, you wanna be all this fourm than SHOW IT
koorosh_bsboys said:
Did not work on my hermes
Click to expand...
Click to collapse
u gotta do it as soon as the BAR APPEARS, instantly when u see 0% pull it and do a soft reset, 3 times I have gotten outtta TRI COLOR SCREEN
nicknowsky said:
who said anything about Dead Radio?? I dunno if thats the case I see NO GSM thats it, I know nothing further. If you are so wanting to help now, WHY didnt you DO a better job of helping me earlier?? Now ur saying my phone is busted, I dunno whatever I will deal with it, STEP UP dude and help out BETTER, you wanna be all this fourm than SHOW IT
Click to expand...
Click to collapse
NO GSM.....................what do you think that means???? NO GSM shows the radio portion of the device is corrupted, the radio stack is responsible for the phone functions on the device...the GSM functions.
The directions i showed earlier are IDENTICAL to what im saying now......since it hasnt worked your device is not fixable. Booting into windows is easy to achieve but you wont be getting back the phone functions any time soon.
-----------------------------------
Final post since you BLATANTLY don't understand the device or what you are doing...hence how you ended up in this position.
nicknowsky said:
who said anything about Dead Radio?? I dunno if thats the case I see NO GSM thats it, I know nothing further. If you are so wanting to help now, WHY didnt you DO a better job of helping me earlier?? Now ur saying my phone is busted, I dunno whatever I will deal with it, STEP UP dude and help out BETTER, you wanna be all this fourm than SHOW IT
Click to expand...
Click to collapse
Your method did not help me, but thanks anyway dude.
I think you should load hardspl on your device and then try flash any radio.
so read the WIKI and i wish your phone will be just fine. but mine is screwed up
NO no nonono You mnisunderstood me, I know WHAT NO GSM is I was refering to what YOU said in a previous post about my RADIO and how It is DEAD forever and what not< True be told, it might be I dunno, and ya know what I WANT to send it into HTC for repairs, thats what I have wanted to do since the start of my comedy of errors, I know what ur saying but you should help me IN COMPLETE n00b terms and showed me then what you actually thought i could of done, and I know u will say thats what you did, but u could of done it better
koorosh_bsboys said:
Your method did not help me, but thanks anyway dude.
I think you should load hardspl on your device and then try flash any radio.
so read the WIKI and i wish your phone will be just fine. but mine is screwed up
Click to expand...
Click to collapse
I am in the process of reading UP on what I should do bout my RADIO, I might try that, dunno yet I am not done fixing my Hermes, but I WANT to send it in for repairs thats whats best
chillax dude
jaysus boy,will you ever relax, read the posts fully and use ALL the resources available in the forum as well as the excellent wiki site.anyone, including noobs can, if they follow the guides,flash the os/radio of their hermes with more or less complete confidence.Mr vanx himself produces some of the best and most idiot proof guides available but i suppose a few get thru!
do not abuse the good nature and generosity of the rom gods in this forum 'cos you broke your phone,read widely,chose carefully and make your choice.if you cant fix it then send it away and get a proffesional to fix it if possible.
good luck then
nicknowsky said:
..but you should help me IN COMPLETE n00b terms and showed me then what you actually thought i could of done, and I know u will say thats what you did, but u could of done it better
Click to expand...
Click to collapse
hey.. bro, nobody owes you a living... don't sound so ungrateful.. the fact that mrvanx came to share his knowledge is good enuf.. please be polite..
my 2 cents..
kipe said:
hey.. bro, nobody owes you a living... don't sound so ungrateful.. the fact that mrvanx came to share his knowledge is good enuf.. please be polite..
my 2 cents..
Click to expand...
Click to collapse
Here here... Well said.
The type of brick help was requested with is well documented - and while "the fix" the OP described in this post may work for him - it's more likely to cause more problems if someone innocently tries this on an unbrickable phone. Interrupting a flash is always bad advice - and a little reading up on No-GSM bricks would have been a start - or the FAQ on "getting stuck in the tricolour screen!"
There is no such thing as "shocking" a device back into life. You've been watching to much ER where they defibralate humans - doesn't work with electronics generally
There is restoring an OS image, there is (if you're lucky) recovering from intermittent bad blocks by doing a couple of flashes but it's much safer to just flash the bits you need by carefully making the .nb files required using dutties NBH tool then making your own NBH to flash containing just an OS image or just a radio image - or whatever you want to try to flash. If a flash gets stuck - it's getting stuck for a reason and that reason needs investigating before trying things which are known to cause bricks in the first place hence you strip the image down and see what flashes and what doesn't. If noobs don't recognise problem solving techniques - then they haven't read enough before trying to show off an upgraded phone to their mates and should stick to manufacturers updates only. Harsh but in my opinion true.
Sorry, I'm about to have a late night rant...
The reason many experienced users don't always reply to calls for help immediately is because all the information known is well discussed and well documented and people get tired of effectively cutting and pasting solutions to "noobies" just flashing an image not knowing what could happen and what to do if the worst happens and what to do when it all goes wrong. The front page of this forum usually has 3 requests for help on it to solve a brick issue - and generally all 3 are the same type of brick so should an experienced poster have to post the same thing in three threads? No.
Even worse - many newbies don't start with the obvious basics like flashing HardSPL or they end up with a brick and then try to unbrick it by doing so many other things that they end up with a hybrid brick and don't even know what steps they did to make it! Sadly, I feel that if people can't be arsed to read up on stuff and just want to have the very latest thing to show off with - then they deserve the brick they get (and should sell it real cheap on ebay so I can buy them up!) At the end of the day - everything on these forums should be considered experimental and non-supported. If you want full support - go to your network, HTC or Microsoft and PAY for it. If you want to join a community who loves experimenting and discussing the issues then join in, support the forum (make some donations to the good people who keep things ticking) and most importantly learn about your device.
My first upgrade was well over a year ago - and it took me about 2 months of research into de-bricking - and plenty of bookmarking - before I even attempted it so I knew what could go wrong and at least what steps to take to recover my own device if it happened.
Have I bricked my phone? - Of course while experimenting with cooking roms - I've unbricked them using others posts and the wiki here and I've never had to ask how to do it - but I have had to spend several hours reading (with lots of patience and learning a lot in the process) but at least when I flash I know the risks and don't just scream that I used <insert whatever ROM> here created by <insert poster> and it bricked my hermes therefore it must be <insert poster who released the ROM> fault. Nor to I slag off things that don't work - be it ROMs, procedures or advice.
The advice to anyone who is a noob really is to read, read and read - Do your research and know about your device before you tinker with it. Not to the level of being able to explain what each GPIO carries - but at least to understand the different parts of the device - the different images and what to do if any part of those images doesn't quite work properly (ie - bricks)
And if it does brick... DON'T DO ANYTHING until you know why it's bricked and have read the unbricking threads and the wiki. Someone WILL respond if you list what you've tried and what happened when you tried it. They don't respond to "help, I flashed xxx and it doesn't work."
The wiki and unbrick threads might be long but virtually every brick is covered and it's better to know about bricks before you end up holding one in your hand
Rant over.
Hello
I wanted flash the rom of my atrix Orange France, with France rom retail,
The Atrix is soft brick
Unable to launch rsd mode or ...
When I pressed the button down one sees displayed nv flash and the phone turn off
If I press the top button, it starts in fastboot
What should I do.
thank you
PS : Sorry for my English
do you have experience with fastboot.
This worked for me in a similar sounding softbrick. http://forum.xda-developers.com/showthread.php?t=1182871 Check to make sure that this applies to your situation first though.
I was at the beginning of a stock rom 2.3.4 orange Fr.
I erase the rom and put a rom 2.3.4 fr.
The phone has never been amended (unlock, costum rom, root...)
bonez565 said:
This worked for me in a similar sounding softbrick. http://forum.xda-developers.com/showthread.php?t=1182871 Check to make sure that this applies to your situation first though.
Click to expand...
Click to collapse
Its not working :/
I made a video to show the problem
http // www youtube com / watch?v=HlSP6odb_Ro
Is it nv flash? If so it is currently unfixable. Here is a quote from a recent thread that I posted.
Erebus671 said:
okay, I am seeing this alot, but everyone else unit seems to shut off before anything can happen, mine does not, it simply stays on. That being said, I am conducting an experiment, since my ATRIX was afflicted I baught a new one because I liked the webtop idea, so im charging my new one to 100% and then im going to swap out batteries and check the results. Has anyone seen any evidence at all that might suggest a possible fix? I will update you guys on the results of my experiment once completed, hopefully I can come across something that will lead someone to a fix if not find one myself.
Click to expand...
Click to collapse
I recently hard bricked my phone after flashing CyanogenMod 10. I know that CyanogenMod doesn't even touch the bootloader but somehow I ended up with a very expensive paperweight. But luckily Samsung Care replaced the motherboard in my phone and now my phone is good as new. But that doesn't mean that I'm gonna refrain from flashing or rooting. I've been rooting since 2 years now & this is the first time I've ever hard bricked the phone. But this experience really did scare me. So, to avoid it, in future, I wanna know all about hard brick. So please answer my following questions:
1) What exactly is hard brick?
2) Possible ways in which one could end up with a hard bricked phone? (Mainly SGS3)
3) Possible ways of recovery from hard brick?
Thanks a lot in advance. I want this thread to be a complete source of information to anyone who is new to flashing & needs DO's & DONT's of flashing properly.
saurabh_goyal93 said:
I recently hard bricked my phone after flashing CyanogenMod 10. I know that CyanogenMod doesn't even touch the bootloader but somehow I ended up with a very expensive paperweight. But luckily Samsung Care replaced the motherboard in my phone and now my phone is good as new. But that doesn't mean that I'm gonna refrain from flashing or rooting. I've been rooting since 2 years now & this is the first time I've ever hard bricked the phone. But this experience really did scare me. So, to avoid it, in future, I wanna know all about hard brick. So please answer my following questions:
1) What exactly is hard brick?
2) Possible ways in which one could end up with a hard bricked phone? (Mainly SGS3)
3) Possible ways of recovery from hard brick?
Thanks a lot in advance. I want this thread to be a complete source of information to anyone who is new to flashing & needs DO's & DONT's of flashing properly.
Click to expand...
Click to collapse
1: You hardbricked your phone if you can't power it on at all. That means no Recovery and no Download mode. No lifesign at all.
A softbrick on the other hand is the situation that your phone powers up but stucks at a certain point and you can`t boot it up to the OS. However Recovery and/or Download Mode is still accessible, so you can flash a ROM, which usually solves the problem.
2: If you screw up the Bootloader. How can you screw up the bootloader? If you flash the bootloader through Odin there is always the chance that during the flash process your OS crashes or you by accident disconnect the USB cable. Although I heard cases where people hardbricked their phones during flashing a ROM through CWM (like in your case). This however doesn't make sense because like you already said most ROMs don't touch the Bootloader, so even if something happens during the flashing process, you should still be able to get at least to Download Mode. So with cases like that I assume that it is a hardware failure of some sort.
3: If you screwed up the bootloader then you can bring your phone back to life by using JTag. There are people who do this for a little money, so if you don't have warranty anymore, this is the way to go because it's a lot cheaper than replacing the mainboard.
Thanks a lot
Thanks for such an informative reply. Really appreciate it.
Scarface1991 said:
1: You hardbricked your phone if you can't power it on at all. That means no Recovery and no Download mode. No lifesign at all.
A softbrick on the other hand is the situation that your phone powers up but stucks at a certain point and you can`t boot it up to the OS. However Recovery and/or Download Mode is still accessible, so you can flash a ROM, which usually solves the problem.
Click to expand...
Click to collapse
I know the symptoms. But what exactly is a hard brick? Hardware is burned out? Software isn't able to communicate with hardware? Like, what happens exactly inside the phone?
Scarface1991 said:
2: If you screw up the Bootloader. How can you screw up the bootloader? If you flash the bootloader through Odin there is always the chance that during the flash process your OS crashes or you by accident disconnect the USB cable. Although I heard cases where people hardbricked their phones during flashing a ROM through CWM (like in your case). This however doesn't make sense because like you already said most ROMs don't touch the Bootloader, so even if something happens during the flashing process, you should still be able to get at least to Download Mode. So with cases like that I assume that it is a hardware failure of some sort.
Click to expand...
Click to collapse
How can one screw up during bootloader update/flash? The process takes like 5 seconds!!
Plus Samsung Galaxy S3 GT-I9300 doesn't allow flashing of any other device's bootloader.(Yeah yeah, I was about to flash GT-I9305's bootloader on mine by mistake!) Odin stops automatically during flashing. I don't know whether it is a security feature by phone or odin but whatever it is, it ROCKS!
saurabh_goyal93 said:
Thanks for such an informative reply. Really appreciate it.
I know the symptoms. But what exactly is a hard brick? Hardware is burned out? Software isn't able to communicate with hardware? Like, what happens exactly inside the phone?
Click to expand...
Click to collapse
The Bootloader is the first thing that is loaded when you power up your phone. If you screw up the bootloader your phone won`t boot up at all. This is caused by the user of the phone, that`s why people say: "Your hardbricked your device".
If your hardware fails to function properly because of whatever reason then it`s not a hardbrick but simply a hardware failure. It is in most cases not caused by the user (except if someone would be dumb enough to overclock CPU/GPU to a ridiculous high level)
How can one screw up during bootloader update/flash? The process takes like 5 seconds!!
Plus Samsung Galaxy S3 GT-I9300 doesn't allow flashing of any other device's bootloader.(Yeah yeah, I was about to flash GT-I9305's bootloader on mine by mistake!) Odin stops automatically during flashing. I don't know whether it is a security feature by phone or odin but whatever it is, it ROCKS!
Click to expand...
Click to collapse
Look at the XDA Q&A Threads. There are several cases a day where people have problems flashing something on their phones because Odin fails for some reason. That`s why I would use Odin only when it`s really necessary. When I had my first Smartphone (Samsung Wave) I flashed a lot of stuff on it and one time the flash tool just reported an error and that`s it (bootloader was screwed). I don't know why it failed until this day. So flash a bootloader only if it`s absolutely necessary because this is the most dangerous thing that you can do to your device.
I hard bricked my phone by rushing to install a new ROM before i had to leave for work. Later when I retraced my steps I realized that I made a stupid and critical mistake. I installed a ROM for a Galaxy S2 onto my Galaxy S3.
The installation appeared to be going smoothly. When it was complete I pressed the "reboot now" button. My phone turned off and never turned back on.
Now the phone has no signs of life. No Power, No Recovery, No download mode, No drivers when I plug it into a computer USB port. The computer does recognize that some kind of USB device is connected to it though. Which is what makes me believe that the phone is not dead and must be repairable.
I've done research and it appears that there are 3 options. (Please let me know if there are more)
Option #1: Pay someone to perform a JTAG repair service.
Option #2: Attempt to boot into recovery using a JIG.
Option #3: Play dumb and return my phone under warranty.
Questions
Option #1: is there a kit you can buy to perform this JTAG repair yourself? I will be more careful in the future but I don't want to be helpless if this ever happens again.
Option #2: I find conflicting advice here. Will this help my phone? eBay sellers warn that a JIG will not help a phone boot into download mode if it doesn't even power on at all. Has anyone attempted this with a phone in the same condition as mine? if so, what was the outcome?
Option #3: The easy way out . But also the defeated unhonest route I would rather avoid. It seems that most people reporting a phone in this condition never explain how they fixed their phone. What do they do?
My phone is still under warranty. Will they be able to detect that I caused the malfunction if I tell a lie that this just happened one day after charging the phone over night?
What do people do when their warranty has expired?
Please let me know how you handled this?
I hope this at least helps someone prevent what I did. Take your time!
I look forward to any advice
Sent from my SGH-I747M using xda app-developers app
fullycompletely said:
I
This is I9300 forum if you do not have I9300 this is the wrong forum and any advice may not apply to your phone .
You say >>>>>
SGH-I747M
Option #1: Pay someone to perform a JTAG repair service.
That may work but it depends upon the actual problem .
Option #2: Attempt to boot into recovery using a JIG.
Dirt Cheapo always worth a try .
Option #3: Play dumb and return my phone under warranty.
It will be either rejected for warranty or repaired .
Questions
Option #1: is there a kit you can buy to perform this JTAG repair yourself?
YES use GOOGLE search .
I will be more careful in the future but I don't want to be helpless if this ever happens again.
But JTAG is no magic solution .
helpless is a simple fact of reading the faqs and guides after its broken .
Option #2: I find conflicting advice here. Will this help my phone? eBay sellers warn that a JIG will not help a phone boot into download mode if it doesn't even power on at all. Has anyone attempted this with a phone in the same condition as mine? if so, what was the outcome?
READ the JTag thread .
My phone is still under warranty. Will they be able to detect that I caused the malfunction if I tell a lie that this just happened one day after charging the phone over night?
What do people do when their warranty has expired?
Phone is not old enough for no warranty but warranty refused then you pay .
Click to expand...
Click to collapse
fullycompletely said:
I hard bricked my phone by rushing to install a new ROM before i had to leave for work. Later when I retraced my steps I realized that I made a stupid and critical mistake. I installed a ROM for a Galaxy S2 onto my Galaxy S3.
The installation appeared to be going smoothly. When it was complete I pressed the "reboot now" button. My phone turned off and never turned back on.
Now the phone has no signs of life. No Power, No Recovery, No download mode, No drivers when I plug it into a computer USB port. The computer does recognize that some kind of USB device is connected to it though. Which is what makes me believe that the phone is not dead and must be repairable.
I've done research and it appears that there are 3 options. (Please let me know if there are more)
Option #1: Pay someone to perform a JTAG repair service.
Option #2: Attempt to boot into recovery using a JIG.
Option #3: Play dumb and return my phone under warranty.
Questions
Option #1: is there a kit you can buy to perform this JTAG repair yourself? I will be more careful in the future but I don't want to be helpless if this ever happens again.
Option #2: I find conflicting advice here. Will this help my phone? eBay sellers warn that a JIG will not help a phone boot into download mode if it doesn't even power on at all. Has anyone attempted this with a phone in the same condition as mine? if so, what was the outcome?
Option #3: The easy way out . But also the defeated unhonest route I would rather avoid. It seems that most people reporting a phone in this condition never explain how they fixed their phone. What do they do?
My phone is still under warranty. Will they be able to detect that I caused the malfunction if I tell a lie that this just happened one day after charging the phone over night?
What do people do when their warranty has expired?
Please let me know how you handled this?
I hope this at least helps someone prevent what I did. Take your time!
I look forward to any advice
Sent from my SGH-I747M using xda app-developers app
Click to expand...
Click to collapse
try a USB Jig. only a few £ off ebay etc.
Dear All,
Before I start, please forgive the repetition, as I know this issue comes up a lot but I've searched all over and can't find a solution for my circumstance. If there's a post I've missed, please direct me there...:fingers-crossed:
I recently received a Lumia 800 with a Qualcomm bootloader, sim-locked to a UK network. The first thing I did was use NSSPro to remove the simlock, which was successful, but I also wanted to debrand and try a custom ROM..
I read round the issue a fair bit and was going to go down the Linux 'dd' route when I spotted the Windows flashing utilties. Ever keen for an easy life, I went ahead and flashed my handset with FunkyRom, apparently making two fatal errors; not backing up my partitions in Linux and not using Linux to do the flash. Laziness stopped me backing up and I'm aware I deserve what I get for that, but the warnings about flashing in Windows were a little harder to spot and I only found those after the event.
ANYWAY....
Unsurpisingly it turns out, the Windows flash bricked the 'phone. I can get it into Qualcomm bootloader mode in Windows and Linux, I can read the partition map (attached), flash it in NSSPro, 'dd' it in Linux and flash it with the Windows tools, but it won't boot past the Nokia logo. After initial flashing the battery went haywire as well and wouldn't hold it's charge much beyond ten minutes. The battery is fine, I have swapped it out for a new one and it works fine in another 'phone, so I'm not sure what that was about. One other thing to note is I've never been able to hard reset it after flashing, the combination of button presses does nothing, no matter how long I hold them down, all that happens is the 'phone reboots if I release the power button.
I've tried many reflashes, replacing the third partition etc but I think I'm just laying s**t on top of s**t now and would appreciate some guidance. I don't think it's terminally bricked because I can still read/write from/to it in Linux, NSSPro etc, but I'm normally a Nokia N9 man, so this partition structure is unknown, I don't know what I'm looking for.
Any help much appreciated, with the note that I realise I ballsed up not making a backup, so you can skip telling me I'm a fool, I'm getting that enough from the missus..!
Sorry for the looong first post,
Squid
Not sure about fixing it as I have the 710, but Im pretty sure you could RMA to the place you bought it, and they would be too lazy to do full checks on what you did to it, send it back to Nokia and send you a replacement
I've bricked tablets and GPUs and phones and RMA'd, and not once have they ever questioned what I did
One phone I RMA'd I'd flashed a German ROM to and everything was stuck in German, UK company just walked me through factory resetting it on the phone, didn't work obviously, so they gave me a new one
Just an idea if you can't fix it yourself
Other options would be taking it to a local phone repair store who have tools to flash bricked phones, there have been a few here who didn't read the "DO NOT FORMAT" posts, and hit the format button bricking their phones, took it to a repair store who flashed it back to a working state for them
Good luck
Hi and thanks for the reply.
I'll be honest, I'm a Nokia N9 man myself, I was hoping to unlock this one as a spare's spare (it looks and feels familiar), so I'm unlikely to be taking it for repair if I can't get it going myself, but it's interesting to hear you've never been questioned about any DIY work you may have done, I've always thought they'd be hot on that...?
I am holding out for a technical hint or two on something I may have borked during the flash itself, and whether that might be recoverable, after all I can get to the bootloader, just whatever I flash on top (FunkyRom, Rainbow Mod etc) just don't load. Also, why doesn't hard reset work on this 'phone? I have questions but I've run out of brains for answers.
Are there generic full partition dumps available to dd in Linux that would be like a vanilla image? Are there specific partitions that may be the problem? If it gets to the Nokia logo but no further, how far in the booting process has it come?
Squid
Hi John,
Maybe you can try this: http://forum.xda-developers.com/showpost.php?p=47076870&postcount=2
Otherwise I can download an original rom for you, maybe you can flash that with nss, just let me/us know.
Greetz,
Rataplan said:
Hi John,
Maybe you can try this: http://forum.xda-developers.com/showpost.php?p=47076870&postcount=2
Otherwise I can download an original rom for you, maybe you can flash that with nss, just let me/us know.
Greetz,
Click to expand...
Click to collapse
Brilliant, I'll take a look at the NSU first, thanks!
Rataplan,
No joy with the NSU Retail I'm afraid. Do you think you could let me have an original ROM please as mentioned? After that, I guess it goes to the bin..
John
Ok, gonna download and upload this evening, keep you informed.
Greetz,
Rataplan said:
Ok, gonna download and upload this evening, keep you informed.
Greetz,
Click to expand...
Click to collapse
Great, thanks!
john smash said:
Great, thanks!
Click to expand...
Click to collapse
Ok John, you can download the rom here: https://dl.dropboxusercontent.com/u/9417919/rm-801.7z , the rom is based on RM801_059L8M3_1750.0805.8773.12220, I also suggest to read this: http://forum.xda-developers.com/showthread.php?t=1457341 and
this: http://forum.dailymobile.net/index.php?topic=77419.0
Greetz,
Many thanks, I'll try it later. I have actually tried those threads you linked previously but I'll take another look.
Cheers,
John
Hey there Rataplan,
No dice I'm afraid. I can't get the phone connected in anything other than Qualcomm mode, so I can't use NCS to flash. I can use NSSPro to flash a file with .nb extension but not the files you uploaded. NSU Retail asks me to connect in Qualcomm mode then doesn't recognise the phone once I do that.
I just don't understand how if I can get to the Qualcomm bootloader, why flashing RainbowMod or FunkyRom/FunkyRom lite doesn't work, do you have any suggestions? Is there a way to check if any of my partitions are corrupted?
JS
EDIT - Just read this post - http://forum.xda-developers.com/showpost.php?p=29583840&postcount=2 and renamed the boot.img of the ROM you uploaded. Now my 'phone shows a 'Three UK' splash screen, then the nokia logo, but still doesn't load. Is there a way to know what stage of the boot the 'phone is getting to before it hangs?
Ha! Got it!
Using the extract and rename method I flashed the 11412 firmware (oldest one in Navifirm) for product code 059M062 and bingo! It boots and there's no simlock...
Thanks for all your help Rataplan, 'phone revived!
:victory:
Great, I know it had to work, that's why I gave you an copy of an older rom, I'm glad you solved it yourself , take care next time.
Greetz,
Rataplan said:
Great, I know it had to work, that's why I gave you an copy of an older rom, I'm glad you solved it yourself , take care next time.
Greetz,
Click to expand...
Click to collapse
Will do..
I've changed my product code with NSSPro but if I try to flash any later ROMS then it goes back to being borked. I can always recover to this ROM now but I'm wondering why I can't upgrade?
john smash said:
Will do..
I've changed my product code with NSSPro but if I try to flash any later ROMS then it goes back to being borked. I can always recover to this ROM now but I'm wondering why I can't upgrade?
Click to expand...
Click to collapse
I have to take a look at your product code, did you try Nokia Update Retrailer.
The original product code was 059L7C6, I've successfully flashed it with a ROM for product code 059M062 and confusingly, I've written the product code 059L7C2 with NSSPro..
Does it bork it if you try to update it through Zune ?
*Detection* said:
Does it bork it if you try to update it through Zune ?
Click to expand...
Click to collapse
Hey,
Just plugged it into Zune now and it's offering me 7.10.7740.16. Question: Does using Zune overwrite the Qualcomm bootloader? Once that's gone I know I can't get any custom ROMS loaded on here..
Thanks,
JS
For those who may be interested:
I've got a working Lumia now, flashed with a 12220 firmware on a UK product code but that's it, I can't get anything more up to date on there. Every time I flash something more recent I get stuck at the Nokia screen. In addition, I get the same result with any of the custom ROMs, they just won't load. Could my hardware version be preventing the upgrade? Any ideas..?
JS
john smash said:
Hey,
Just plugged it into Zune now and it's offering me 7.10.7740.16. Question: Does using Zune overwrite the Qualcomm bootloader? Once that's gone I know I can't get any custom ROMS loaded on here..
Thanks,
JS
Click to expand...
Click to collapse
No the update doesn't overwrite the bootloader, I flashed the unlocked bootloader to mine and have flashed custom & stock & custom & stock in that order and everything stayed unlocked
Hey guys !
Well...
Yesterday, I decided to flash a new ROM on my aunt's SII...
It wasn't the first time I did this : my own phones have all been flashed, I know how it works !
But... I got a problem ! While I was wiping the data/cache, the phone got stuck on this step. Then, shut down. And now, it doesn't boot anymore. Screen stays black. I did everything I found on the web : tried to boot on recovery and on download mode, tried to press the buttons to get into these modes and inserting the battery while pressing, tried to connect it on USB (not even detected)...
After some researches, I found out that it was a eMMC problem...
Anyway, in a nutshell, my phone is hard bricked. What can I do ?
Thanks.
rohecla said:
Hey guys !
Well...
Yesterday, I decided to flash a new ROM on my aunt's SII...
It wasn't the first time I did this : my own phones have all been flashed, I know how it works !
But... I got a problem ! While I was wiping the data/cache, the phone got stuck on this step. Then, shut down. And now, it doesn't boot anymore. Screen stays black. I did everything I found on the web : tried to boot on recovery and on download mode, tried to press the buttons to get into these modes and inserting the battery while pressing, tried to connect it on USB (not even detected)...
After some researches, I found out that it was a eMMC problem...
Anyway, in a nutshell, my phone is hard bricked. What can I do ?
Thanks.
Click to expand...
Click to collapse
what stock firmware version was the Phone when u did the wipe from recovery (if it was on ICS 4.0.4 then ur phone will be bricked because of the kernel of ICS4.0.4 being plagued with the 'EMMMC' brick bug and only a JTAG or a MB replacement is the solution for it) .
JTAG won't work; motherboard replacement or bin.
I think it was 4.0.4...
Motherboard replacement is the only thing I can do ?
Mate.... Samsung KNOWS this is a problem.......I'd try for warranty repair/replacement.....if the phone is less than two years old, you have a good chance......
Just remember to 'act dumb' at the service center..... Tell them you were trying to use kies to update from ICS and the phone died...... If it is the emmc brickbug, there's NO WAY they can check what os was on ur phone or whether you'd rooted or modified it in any way.....right now it's an unrecoverable (expensive) paperweight........
This might be my S2, or it might be my W...but it's definitely CM
Yeah, I saw this is a quite common problem... But often, it's just a soft brick. In my case, it's a hard brick...
And warranty expired two months ago...
Well, it's unlikely to succeed, but you could try emailing Samsung explaining your situation regarding expired warranty and going on to explain that updating with kies is a 'normal' procedure and that it's that 'normal' Samsung provided procedure plus the 'unstable' OS version (having read on the internet about 4.0.4 brickbug) that have killed a phone that would otherwise be working today. Stress the point that the ICS firmware AND kies were both supplied by Samsung for official (end user) use on Samsung devices......see what they say.....can't hurt right?
This might be my S2, or it might be my W...but it's definitely CM
Yeah, they're going to honour an expired warranty. That happens all the time
Mb....I *did* say right at the start that it probably wouldn't work..... But what has he got to lose?
Lol.....they *might* be suffering from an excess of Xmas and new year goodwill.......
This might be my S2, or it might be my W...but it's definitely CM
I have twice super bricked my two SGS-2s.... EMMC bug is one hell of a pain in ass. You have to let go some SD card space, but u can revive you phone using the URL in my signature. I revived both my phones losing about a GB space in one and a couple GBs in other. Good Luck
alvinasnow said:
but u can revive you phone using the URL in my signature
Click to expand...
Click to collapse
People have said he needs a new motherboard.Do you know something they dont?.
S4 victim
The problem is that I can't flash anything ! The phone simply doesn't turn on ! No recovery mode, no download mode, nothing ! It doesn't even charge !
Yes try this link from alvinasnow
http://forum.xda-developers.com/showthread.php?t=1667886
So far as I know if you only connect your phone normally if it os charging then it already has some kind of connection with the pc I believe its adb.
But since you dont have warranty you can give it a shot to save money so just give it a try and read carefully. I was surprised when I got this phone, that samsung would make a big mistake like that its a just shame.
Edit: i dont know or you need jtag or riff and I will not test it cause I dont have a superbrick phone with mmc cap erase.
But just open device manager on the pc and connect the phone and see if there is a new device connected.
In my opinion my previous phone has one of the best options to make it unbrickable
It was nvflash but it sucked.nvidia wouldnt release sources.
Gooodluck with your phone
Sent from my GT-I9100 using Tapatalk
Which part of this phone needs a motherboard replacement are you lot having trouble comprehending ?
OK...For all the slow kids who keep posting to this thread (including the OP); this phone needs a new motherboard. No threads promising magical fixes are going to work, there is no other way to fix this.
Is this clear now or do I have to make another post in bolded caps to make it really clear ?
There is a SLIGHT chance that if a JTAG recovery house can boot a kernel via JTAG (I do not know if RIFFBox can do this or not), they can use the solution that the Kindle Fire community used. (This was a recent discovery 2-3 months ago)
The problem is, I have attempted to provide information on this solution to these JTAG houses with no response. I don't know if they can boot a modified kernel via JTAG or not.
Currently:
All Exynos4 devices that are Superbricked are unrecoverable, as Samsung refuses to provide any way to boot these from USB, and anyone who could develop a solution hasn't responded (since most dead devices are long gone at this point...)
All Qualcomm-based Samsungs that are Superbricked are hosed too
Kindle Fires that are Superbricked are recoverable as of 2-3 months ago thanks to some discoveries by Oranav that were used by Hashcode to develop a recovery solution. This solution can't be used on Samsung Exynos4 devices as it depends on the ability to boot the device from USB.
And folks...... @Entropy512 needs to be listened to.......he is the dev who has done the most research into this issue and (somebody cmiiw) was the one who discovered the "emmc cap erase" command was the culprit. I think he also wrote the original (much copied) 'got brickbug' app which tells you if your phone is affected or not. If what he says doesn't work, then as @MistahBungle says, the ONLY OTHER OPTION is a new motherboard........
This might be my S2, or it might be my W...but it's definitely CM
Well...
I think I'm just going to call the insurance, and see what they can do ! Even if my warranty is now void, they may replace the phone !
Thank you all !