as title,i had tried to flash using speedmod,hydra but still no hope
N7000 rm on an AT&T Note will brick your phone.
And it likely already has. ..
OP. ...you will need a JTAG repair for the device.
Very sorry, but insufficient research has caused you to kill your device.
Im surprised that you did this after being a member here for nearly 2 years, but I suppose that bad sh** happens to everyone at some point.
Flashing of that rom has deleted your partitions, and removed your boot partition and download mode. USB function is gone as well.
Ranger got it. ...your phone is hard bricked.
Search for "JTAG" repair in the search box.....g
Related
Hello,
I reciently rooted my samsung galaxy s2. I tried a few roms so i could get used to the system or restoring etc. However i encountered a problem whilst having a peek at an alpha jellybean rom, where i noticed that my CWM app on the phone had vanished? I attempted the restore using the 3 button combo and found that i kept recieveing E: can't mount/ E: can't cache messages whilst on the restore screen. i could find my latest restore on my sd card however it wouldnt restore. I believe the CWM was removed from my phone which caused it to not work. I was then stuck in a bootloop. no matter what i done, boot to a stock rom via odin, try the different CF roms i and try to put CWM back on to the phone? I read a post on here from someone who had the same problem, who was told it looked as though there is a problem with the partitions. i followed a tutorial and used odin to put Latona 20110114.pit on the phone. it said i would get a blank screen once this has done and i needed to remove then place the battery back in the phone then put it into download again. This didnt happen!! I done as instructed and now my phone wont go into recovery mode, download mode or even boot loop. I fear i have completely bricked my phone so i am trying to use oneclick heimdall to sort it however my PC keeps saying i need admin rights to install it which i have.
Can someone please help me out. I am new to this so please go easy on me.
many thanks
If you have no signs of life from the phone, it's probably cactus.
You might as well try a jig (but unlikely to work; still try one tho). Only option is service centre & hope they can't tell/don't care you've been messing with it & fix it under warranty or JTAG repair by a 3rd party repairer, at your cost obviously; will be cheaper than having Samsung/an authorised repairer fix it if they refuse warranty service which they're quite within their rights to do.
edinsam said:
i followed a tutorial and used odin to put Latona 20110114.pit on the phone.
Click to expand...
Click to collapse
First result of searching suggests that's meant for the I9003. Good job.
HA
Hello,
Awe well then. never mind eh, whats done is done! Its totally bricked so i thought i would chance my luck by sending it back to O2 for repair. I was reading the only other way to get the phone running again was to take it to bits and hook it up for some stock flashing. so heres hopping they sort it!
lesson learnt!!!
I've got a very definite hard brick situation going on. A few weeks ago I was using my phone, browsing Tapatalk and downloading something with the Dropbox app, and the phone went completely unresponsive (screen on but frozen, no response to any touches), came back after a few seconds, then froze completely. I powered off and tried to reboot, it hung on the boot animation. Not a bootloop, just hanging there. I powered off again and booted into CWM and tried to restore from my backup. It threw a couple errors which unfortunately I don't remember much about, and honestly, I can't remember now if they came up before or after I started the restore. It started restoring, but got hung up restoring system. After waiting what seemed like forever but was probably more like 10 minutes I very hesitantly powered off and went back into recovery, this time attempting to reflash the rom I was using. More or less the same thing, it started but just hung up during the install. I powered off again, intending to put my phone into download mode and try to flash something via Odin, but the poor guy had had enough and wouldn't even power back on. I left it charging overnight, but it never came back on and I've since bought a new phone. However, if it seems to anyone that it would be worthwhile to try a jig or jtag service, I wouldn't mind keeping this phone as a spare. Truth is, I actually miss it.
I was running WanamLite 12.5, which is XWLPX, 4.0.4, with SpeedMod K3-32. I had tried out a couple of what were then pretty much new JB leaks just before the bricking, I know I tried out Omega and Disaster, but I only kept them on for a few hours each time. All of the kernels I've used since 4.0.4 have been considered "safe".
Anyway, again, based on what I've described does anyone think there's a chance of unbricking my phone without replacing the motherboard?
shockwaverider said:
I've got a very definite hard brick situation going on....
Anyway, again, based on what I've described does anyone think there's a chance of unbricking my phone without replacing the motherboard?
Click to expand...
Click to collapse
Firstly, there is no such thing as a "hard brick" for same reason there is no such thing as a "soft brick". There is just "bricked" and no in between, your device is either bricked or it isnt.
What n00bs call "soft bricked" is just when they cant figure out how to get system to boot. Your device is bricked when it wont power on or if it powers on you cant use download/recovery to flash working rom/kernel.
In your case it sounds like you have had a hardware failure and thus will need to get the part fixed/replaced or maybe whole board. To answer your question though, yes you should first try a USB jig to see if you can get device to wake up in download mode and then try again to flash kernel ready for restoring backup or flashing new rom. If this fails then you will need to get it fixed.
TheATHEiST said:
Firstly, there is no such thing as a "hard brick" for same reason there is no such thing as a "soft brick". There is just "bricked" and no in between, your device is either bricked or it isnt.
What n00bs call "soft bricked" is just when they cant figure out how to get system to boot. Your device is bricked when it wont power on or if it powers on you cant use download/recovery to flash working rom/kernel.
In your case it sounds like you have had a hardware failure and thus will need to get the part fixed/replaced or maybe whole board. To answer your question though, yes you should first try a USB jig to see if you can get device to wake up in download mode and then try again to flash kernel ready for restoring backup or flashing new rom. If this fails then you will need to get it fixed.
Click to expand...
Click to collapse
yada yada yada I've heard some developers use "unbrick". Go tell 'em there's no such a thing.
And stop worrying about semantics.
Thanks for the replies. I understand that a so-called "soft brick" isn't really a brick per se, but when even articles in the XDA portal throw around the terms "soft" and "hard" bricks, I would say that the genie is out of the bottle and these terms have, for better or worse, entered the common parlance. I do, however, appreciate the input and quite possibly this is simply a hardware issue, although I will, when time allows, try to wake the phone up with a jig.
gastonw said:
yada yada yada I've heard some developers use "unbrick". Go tell 'em there's no such a thing.
And stop worrying about semantics.
Click to expand...
Click to collapse
BS!
If thats the case link me one single post where any respected dev refers to a system boot issue as a "soft brick".
The only conceivable time they would refer to that is simply to try and help a n00b and it was quicker to refer to it in that way then to explain things.
You can only "unbrick" if your device is "bricked" and having a rom or kernel issue resulting in a system not booting is not "bricked", Its as simple as that.
I have a SGH-I747M 4.1.1 Galaxy S3.
I used the Unified Toolkit and rooted/installed CWM, backuped and ready for a new ROM.
As I was installing this custom ROM (Pardus HD), and error popped up and it was aborted, (still in the CWM main menu)
but having only the said custom ROM zip file in the internal memory,
I figured I just shut down and download a fresh copy of the ROM.
and put it in an external SD card then power on the phone back into recovery.
Only thing is it wont power on anymore, the screen is just black, plugging in USB and computer just makes connected/disconnected noise.
(Devices say its "Qualcomm HS-USB DQLoader 9008")
Also tried taking out putting in the battery.
(I know my mistake is I never re-installed the backup) I've run out of ideas, please help.
I have a very similar problem. I had my battery checked thinking that could be the problem. My battery shows that is no good. I tried a new one and still nothing. I can't help but think if it were a missing program it would still come on at least. Lucky for me its covered under insurance. I'd still like to know what happened and if I could fix it.
I'd like to know too if I could fix it myself, other than ''the jig'' or a repair service. currenty trying to revive it still
edit: currently trying this Heimdall thing, goodluck to me...
Have you checked the battery? If I wasn't sending mine back on an insurance claim I would take it apart. I have a Motorola that has a fuse next to the battery under the back of the case. Seems dumb, I know but how could changing the rom "short" out my battery. Dumb again I always thought bricking was only being able to bring up recovery.
I think the battery is fine, as CWM was still running after the error.
That's pretty much what happened to me. Maybe we got to the same problem 2 different ways. Hope you get it figured out.
THIS IS GT-I9300 SECTION..
c'mon there was an stickie on top of this section for you..
HERE.. http://forum.xda-developers.com/forumdisplay.php?f=1705
Your problem is that you flashed a rom for gt-i9300 (International) and you have some U.S. variant of s3. That in most cases bricks the phone.
Probably time for a service center visit.
Hello,
I have a Samsung Galaxy S2.
After reading this post http://forum.xda-developers.com/showthread.php?t=2382579 I decided to root my phone.
So I went ahead and started with this step http://forum.xda-developers.com/showthread.php?t=1118693 because I was unsure if I had a kernel with the MMC-SUPERBRICK-BUG.
After I flashed CWM-SuperSU-v0.97.zip using Odin version 1.85 and after the phone rebooted it was stuck at the "triangle screen" for a few seconds then the display went black and I couldn't do anything further.
Up to this point the phone was still accessible in download mode (volume up, power and center button). I believe this is called "download mode". Sorry but I am a complete noob with rooting phones, etc...
So I panicked and took the phone to a repair shop (big mistake). The guy ran it in download mode then tried to flash something onto the phone (I think he used all 4 fields: Bootloader, PDA, Phone and CSC.
Then, in the middle of the operation, Odin froze when writing "setting up connection". Then the phone died ! pressing the 3 famous buttons does nothing and the phone just stays dead.
I had to leave the phone there as the guy said they will try to bypass stuff and try to connect to the CPU directly (sorry again if this sounds noobish). I did update my modem firmware and my computer BIOS in the past... but I guess this one was more complicated.
At the shop, they asked me to check again in 3 days. I am lost here. I don't know what to do anymore.
Is the phone hard bricked ? Should they bear all expenses for what they did ? I would bring back my phone and try something like this http://forum.xda-developers.com/showthread.php?t=1878255 or even a stock flash but I am afraid I cannot do that as the phone isn't even powering up anymore after they tried to repair it at the shop.
Any advice is appreciated.
Nope. You borked it. You tried to flash custom firmware to the phone & obviously failed spectacularly at it. Instead of trying to flash it yourself via download mode (which you could easily have done unless the NAND was borked), you paid them to do it. Sometimes flashes go bad. Sounds like that's what happened in this case.
Reading between the lines they sound like they're going to try & JTAG it (or have someone else do it). And if that fails I presume they'll change motherboards. You could always get the phone back & take it to someone who does JTAGs if that shop doesn't themselves.
MistahBungle said:
Nope. You borked it. You tried to flash custom firmware to the phone & obviously failed spectacularly at it. Instead of trying to flash it yourself via download mode (which you could easily have done unless the NAND was borked), you paid them to do it. Sometimes flashes go bad. Sounds like that's what happened in this case.
Reading between the lines they sound like they're going to try & JTAG it (or have someone else do it). And if that fails I presume they'll change motherboards. You could always get the phone back & take it to someone who does JTAGs if that shop doesn't themselves.
Click to expand...
Click to collapse
Yes I know I failed at it
Or maybe the shop technician is the one who broke it. At least when I had the phone with me I was still able to boot in Odin mode.
Do you think I could have recovered my phone if I had kept it with me and it was booting in download mode ?
I feel so pissed that I took it to that shop. I just wish I hadn't panicked and I had tried, instead, to fix it at home by asking for more help.
Anyway I still haven't paid them anything so far.
We agreed that they will pay for the motherboard because I brought in a working phone (that would power up at least). The owner of the shop was nice enough to agree that he would only charge me fees for installing new software on the phone (even if they have to change the motherboard) because he knows the phone was booting in Odin mode when I came in to the shop and his technician flashed the wrong firmware.
I also wrote down the board serial number so I can be sure they changed it (if they say they did that). So you are telling me the phone can still be fixed ? What does JTAG mean ?
Even if it is fixed I think I will be too scared to try and root it again. Unless I can understand in advance, step by step, what I need to do and what file version(s) I need to use.
Ok, I got my phone today in good working condition.
According to the shop, they had to replace an IC (I don't know what damaged the IC, I am assuming this happened when they tried to electrically jolt the phone) then JTAG it to get it to work again. They charged me a small fee (and they did end up bearing more than 50% of the expenses) because I brought in a phone that was booting in download mode and they take responsibility for what happened after that (flashing wrong files which caused the phone to completely stop booting).
Anyway, long story short, this was my first attempt to root a mobile phone and I learned my lesson.
I am running the following:
Model Number: GT-I9100
Android Version: 4.0.3 (which I will need to upgrade to 4.1.2 of course)
Baseband Version: I9100XXLPW
I know you will say read the sticky posts or the guides but the truth is, that's exactly what I did (you can see the links to the guide I tried to follow in my original post) and I still ended up failing at rooting/installing cyanogen on my phone right after installing Clockwork Mod.
The truth is I am scared to try again and mess up the phone. So this time I would rather be safe than sorry.
What can I do, this time, to safely root it and install a mod like Cyanogen.
Detailed steps are appreciated:
- Do I need to upgrade to 4.1.2 before rooting as 4.0.3 might have the superbrick bug ?
- How to backup the phone.
- Odin version to use, ClockWork Mod version to use, Cyanogen version to use
- How to connect the phone, how to reboot in download mode and all the necessary actions to avoid bricking my phone.
No spoon feeding aloud on XDA.better to read and learn how to do this and that but before you flash anything after learning how to do that learn how to fix it if it doesn't work. :thumbup:
andrewwright said:
No spoon feeding aloud on XDA.better to read and learn how to do this and that but before you flash anything after learning how to do that learn how to fix it if it doesn't work. :thumbup:
Click to expand...
Click to collapse
Fair enough, I figured I'd get that reply from someone and it's normal to be honest.
I decided not to try anything on my phone before I re-read the guides and be sure I know what I am doing.
I will also keep the phone running on stock firmware (after upgrading to JB 4.1.2) to check the battery consumption behavior which, I hope, will be fine since someone tampered with my phone's electronic components at the shop.
Posted so that people don't need to keep posting if they are bricked.
What is a brick?
A "brick" is a term used to identify when a device has failed and becomes about
as useful as a brick. Bricks also come in two forms, soft brick and hard brick. Which
Will be covered later on.
What causes a brick?
Many things can cause a brick. A bootloader flash
going wrong, ROM flashes failing, the eMMC bug,
hardware failing etc. But just because you're bricked,
doesn't mean you can't resurrect it.
Soft bricks
Soft bricks are the most common bricks of all,
they usually occur when a ROM/Kernel flash goes wrong
and results in an incomplete filesystem. When
this happens you cannot boot in to Android, instead
you will get either A) A bootloop or
B) Hanging at the Samsung splash screen.
Recovering from soft bricks
Recovery from soft bricks aren't usually a difficult task.
First you must find out if you can access recovery or download mode.
If you can, you can use either one of those tools to start the flash
again and hope it completes. If it fails again you can decide if there
is an issue with either the phone or your flashing method and
work with the community on resolving your issue.
Hard bricks
Hard bricks are horrible. They are the hardest to
overcome and are the most dangerous and are usually caused by:
A) A bad bootloader flash leading to corruption
B) The eMMC brickbug destroyed your chip leaving you with a dead
device.
If A) occurs, you would need to perform a JTAG resurrection
on it, you can either do this yourself or your phone can be taken
in to an independent repair shop to have them do it. They will
likely flash the bootloader again through the JTAG interface
and revive your phone.
If B) occurs then I'm sorry, but you're done for. The chip is damaged.
You may get lucky with the brickbug and only have your /data partition
corrupt, if this happens you can find custom PIT files (partition table)
to work around the corrupt sectors of the chip. You will lose
some storage space, but at least you get your phone back. The
other side of the brickbug is the phone no longer powers on at all,
in this case, you need a new phone/motherboard.
Avoiding the eMMC bug
Not all of the SII phones were affected by this bug,
but without downloading an app to check, there is no way
of telling so it is better to just play it safe by default.
The bug is caused due to a particular erase command
used in the ICS (4.0.x) kernels and recoveries. So it is,
in essence, best to avoid ANY ROM based on ICS.
In saying this, avoid Firefox OS until a safe kernel
is released for it.
There's no such thing a 'soft brick'. A bricked phone is one that doesn't boot. At all. And is not recoverable by normal means (I.E a JTAG or motherboard replacement/some other kind of hardware fix). If the phone bootloops & recovery or download mode are available, unless the NAND is stuffed, it ain't bricked.
MistahBungle said:
There's no such thing a 'soft brick'. A bricked phone is one that doesn't boot. At all. And is not recoverable by normal means (I.E a JTAG or motherboard replacement/some other kind of hardware fix). If the phone bootloops & recovery or download mode are available, unless the NAND is stuffed, it ain't bricked.
Click to expand...
Click to collapse
Soft brick = Recoverable without professional intervention.
Hard brick = Not recoverable. A paperweight.
Just do a search engine search on "soft bricks" .
http://www.techychat.com/2013/04/08/soft-brick-vs-hard-brick-vs-broken/
http://forum.xda-developers.com/showthread.php?t=2258628
http://tutorialfor-android.blogspot.co.uk/2012/09/how-to-fix-soft-brick-on-android.html
http://androidfannetwork.com/2013/05/02/fix-your-soft-bricked-att-samsung-galaxy-s4/
Still no such thing?
Lol.....smartypants.........can you edit the bit about "you need a new phone".
You only need a new motherboard.....not the whole phone lol.
theunderling said:
Lol.....smartypants.........can you edit the bit about "you need a new phone".
You only need a new motherboard.....not the whole phone lol.
Click to expand...
Click to collapse
Sure I will do, however usually a new mobo costs roughly the same as a new device.
It depends how you go about it.You could theoretically sell your phone as unbootable on ebay,and use the money to buy a 2nd hand working phone,and end up paying a £20 difference.
Or you could be lucky and get a working motherboard for free off me lol.
Samsungs motherboards are a ripoff,and as time goes on they will become worthless....which serves everyone right involved with the distribution of them lol.
theunderling said:
It depends how you go about it.You could theoretically sell your phone as unbootable on ebay,and use the money to buy a 2nd hand working phone,and end up paying a £20 difference.
Or you could be lucky and get a working motherboard for free off me lol.
Samsungs motherboards are a ripoff,and as time goes on they will become worthless....which serves everyone right involved with the distribution of them lol.
Click to expand...
Click to collapse
Yeah that's true. I've updated the OP nonetheless.