[Q] Note bricked - Not starting - Galaxy Note GT-N7000 Q&A, Help & Troubleshooting

Hey,
Well, I have bricked my Note like many others. The only weird thing is that the Note is not even starting anymore. At first there was no problem, I could boot the device. After a reboot (hour after flashing rom) the device didn't go past the boot screen anymore. It could also not load recovery. It could get into download mode, but I was not able to flash a kernel to read out the device in CMD.
After that however, the device didn't boot anymore and it only displayed the batery when it was loading. However, after some hours, even the batery didn't appear while loading. So, is this some kind of ultra brick? It didn't do anything anymore

Try connecting to odin in blind mode. Ie do same as you would nornally do to go to download mode and see if odin can connect.

Also tried that, but it did not work

My condoleances on your brick.

JohanR91 said:
Hey,
Well, I have bricked my Note like many others. The only weird thing is that the Note is not even starting anymore. At first there was no problem, I could boot the device. After a reboot (hour after flashing rom) the device didn't go past the boot screen anymore. It could also not load recovery. It could get into download mode, but I was not able to flash a kernel to read out the device in CMD.
After that however, the device didn't boot anymore and it only displayed the batery when it was loading. However, after some hours, even the batery didn't appear while loading. So, is this some kind of ultra brick? It didn't do anything anymore
Click to expand...
Click to collapse
Try this
http://forum.xda-developers.com/showthread.php?t=1257434
To force your phone into Download mode !

Try some helpful link like this one bud -http://forum.xda-developers.com/showthread.php?t=1661590

Related

[Q] Phone not booting

Hi all,
I use CM12 from MacLaw in combination with TWRP 2.8.1.0 recovery for about 3 weeks now.
Yesterday the phone didn't respond properly, was very very slow and I basically couldn't use the phone. It felt like the CPU was at 100% all the time, so unlocking the phone, calling and so was nearly impossible. A reboot (battery removal) didn't solve it, also the pin code for the sim card came after a few minutes while usually this will come right after starting.
So eventually I did a factory reset from the menu as I did on other occasions just to get rid of this kind of problems.
Well, right after the Samsung s3 mini logo I get the TWRP logo and it will be stuck in there, I see it blinking every few seconds and that's it. When I connect the phone to USB I hear it connecting-disconnecting every few seconds (bing-bong, bong-bing sound).
After a while I flashed TWRP using Odin again, this didn't give any problem but it will still hang in this TWRP loop.
I found some references to this problem but no real solutions. Someone suggested to use ADB but I don't know how to do that, nor could I find a suitable guide on this.
Can anyone help me? Or is it bricked somehow?? I suspect not, download mode is still working.
Thanks for any help!

Hard bricked Wiko Rainbow

Hello,
First of all, sorry for my english as it is not my mother language
I've tried today flashing CM13 on my Wiko Rainbow, but I either failed following the instructions or the files I had were corrupted, leading to a never-ending boot.
I don't know if it was already a soft-brick back then, as the phone turned off while booting just after the installation, but 40min after it (obviously because of en empty battery, which was at 37% before installation)
At first, when the phone was plugged into the computer, the phone was booting up, showing the charging icon for a few seconds, and then was going into the infinite boot for 10 seconds, and then rebooting for the same process.
When I was charging the phone on a wall plug, the phone was just in an infinite loop.
The problem was that, when I did the Volume down + Volume up + power thing, I had a choice between Factory mode and Custom mode, but both of them led me to a black screen, and the phone powered off.
I then searched how to install a custom recovery with a soft-bricked phone, and I got a tutorial on SP Flash Tool, that told me to use a MT6582 scatter file, and to select only a Recovery. I downloaded a TWRP for my phone, and then started download, retracted the battery and plugged the phone on the computer.
I got this message : "brom error s_fthnd_file_is_not_loaded_yet"
The software told me to format the Flash, which I did, and this error now became this : "BROM ERROR : S_DL_GET_DRAM_SETTING_FAIL (5054)"
The thing is that now, the soft brick is now a hard brick, and I can't get the phone to boot anymore, adb doesn't recognize my device, and after installing and reinstalling my phone drivers, no solution came out yet, so I'm hopping that you'll find a solution to help my problem
Thanks.
Regards.
MichelFou said:
Hello,
First of all, sorry for my english as it is not my mother language
I've tried today flashing CM13 on my Wiko Rainbow, but I either failed following the instructions or the files I had were corrupted, leading to a never-ending boot.
I don't know if it was already a soft-brick back then, as the phone turned off while booting just after the installation, but 40min after it (obviously because of en empty battery, which was at 37% before installation)
At first, when the phone was plugged into the computer, the phone was booting up, showing the charging icon for a few seconds, and then was going into the infinite boot for 10 seconds, and then rebooting for the same process.
When I was charging the phone on a wall plug, the phone was just in an infinite loop.
The problem was that, when I did the Volume down + Volume up + power thing, I had a choice between Factory mode and Custom mode, but both of them led me to a black screen, and the phone powered off.
I then searched how to install a custom recovery with a soft-bricked phone, and I got a tutorial on SP Flash Tool, that told me to use a MT6582 scatter file, and to select only a Recovery. I downloaded a TWRP for my phone, and then started download, retracted the battery and plugged the phone on the computer.
I got this message : "brom error s_fthnd_file_is_not_loaded_yet"
The software told me to format the Flash, which I did, and this error now became this : "BROM ERROR : S_DL_GET_DRAM_SETTING_FAIL (5054)"
The thing is that now, the soft brick is now a hard brick, and I can't get the phone to boot anymore, adb doesn't recognize my device, and after installing and reinstalling my phone drivers, no solution came out yet, so I'm hopping that you'll find a solution to help my problem
Thanks.
Regards.
Click to expand...
Click to collapse
You're going to need the firmware (not just TWRP) to fix your phone. Have you been able to download it?
Hovatek said:
You're going to need the firmware (not just TWRP) to fix your phone. Have you been able to download it?
Click to expand...
Click to collapse
using SP Tool gives directly through the USB

Phone memory seems to be read only

As I said in the title. The phone's memory seems to be read only.
I can access the fastboot mode of the phone and issue commands like flashing the recovery but it doesn't seem to update anything on the phone even though I get the "OKAY" message.
My phone is unlocked and until last night I was running CyanogenMod on it just fine. But now I can't flash a new recovery or access it. I have TWRP installed but everytime I try to boot into recovery the phone gets stuck on the logo screen and flashes every couple of seconds.
If I try to start my phone normally I get the cyanogenmod logo on start up (even after flashing stock) and the phone never actually boots up.
Anyone had the same problem before? If you need more details I'll reply ASAP.
My phone is the retail European XT1068 Dual Sim. Thank you in advance for any help.
Same issue here (I'm MrPowerGamerBR on Reddit), the more I read about trying to fix this issue, the more I start thinking "this phone is dead, move on..."
There isn't no fix for this, the only way to fix is replacing the logic board.

Nokia 8 almost dead! TA-1004

Hey
yesterday i almost bricked or maybe bricked my phone. Accidentally changed partition from B to A. Today my phone boot only to nokia logo and stuck on it
Many hours readed about this phone back to life. Recover mode not work, fastboot mode not work. This phone one chance to turn off is completly battery discharge.
If no chance to get back this phone to normal i will get throw it to trash
Classic example of a softbrick can't really call it a hardbrick tbh. PM me all of the details and I'll later make a tutorial if we manage to fix it up.
mati5000 said:
Hey
yesterday i almost bricked or maybe bricked my phone. Accidentally changed partition from B to A. Today my phone boot only to Nokia logo and stuck on it
Many hours reading about this phone back to life. Recover mode not work, fastboot mode not work. This phone one chance to turn off is completely battery discharge.
If no chance to get back this phone to normal i will get throw it to trash
Click to expand...
Click to collapse
I did the same thing.
- Downgrade to Oreo
- unlocked officially bootloader
-fastboot boot twrp.img
booted to twrp- Flashed zip on both slot with latest twrp
Changed slot A to slot B and
we have same problem.
How did you solve your issue?
Did you wait for battery-drain?
Or other combination of buttons.
I tried all the button-combination without success.
Hope you could give advice
Regards
Edit: How to solve!
I simply waited until the battery ran out
When battery was completely dead and no Nokia-logo any more
Then I charged the battery 3% juice without booting
and from there I entered recovery-mode with the help of a USB cable.
Holding the volume+ button while connecting the USB-cable
From TWRP-recovery I changed to the other inactive slot
and whooala, that's it!
I have OEM unlocked my nokia 8 boot loader by nokia official method ,
Then I decide to flash twrp and magick
When boot twrp it give an error that locked
Then I checked some forums and find a way ,
I do what is guided in that forum
Change boot slot b to a ... and I flashed twrp then I flash rom , at the end of flash slide to reboot , then I reboot but after that there is no response in device it went blank and black.....
If I connected to PC in some flash tool it show hs com 3008 and connecting sound in pc but mobile being blank and i cant even get to fast boot mode becoz device get blank ( while connected in pc if I power on or hold power but connection sound will come from my pc but no device or unknown device )
Pls help friends, really dunno what to do
Pls help !
Respond soon pls
Same as me bro.. my ta 1004 is dead after unlocking bootloader official method. And i flash boot twrp and magisk. But my phone always bootlop. I try to flash with ost la. An qfil to recover. But i stuck in download mode. And i try to flash with twrp slide load .
And my phone is dead now.. i can do anithing. My phone can turn on now... i charge it .. but still not respond
Anyone help me

stuck on boot loop after flashing with Odin, please help I'm freaking out here

[SOLVED: Just downloaded latest version of Odin from Sammobile. What a relief!]
Hey guys, this is my first post so please forgive me for any mistakes.
My Note, unlocked SM-960U1, was stuck on June 1 security patch so I decided to flash to this month's firmware:
N960U1UEU2CSH2 for XAR
This got me stuck in a boot loop, which is now causing me to panic. I tried going to download mode and flashing it again but then another issued appeared:
it got stuck on a blue screen with the android and "erasing" I used HOME_CSC This isn't even supposed to erase anything!!!
I tried going on recovery mode but It didn't show up. I went to download mode then, and chose restart. That led me to the recovery mode and I chose restart again, and it showed me this:
#Reboot Recovery Cause is [[odin]RebootRecoveryAfterOdinDL]#
Support SINGLE-SKU
Block-Based OTA
Supported API: 3
# MANUAL MODE v1.0.0#
Rebooting...
That just froze and never rebooted! NO other commands work now. I am freaking out. The phone is hot also. Please someone help out!
Update
I can go on download mode now, but if I choose reset it sends me to the boot screen and then I see a dead android for a split second, then I'm in recovery mode. I can do nothing useful in there and restarting just freezes again
AppleToaster said:
I can go on download mode now, but if I choose reset it sends me to the boot screen and then I see a dead android for a split second, then I'm in recovery mode. I can do nothing useful in there and restarting just freezes again
Click to expand...
Click to collapse
you might have your terminology backwards. There isnt a button in download mode to reset the phone, there is one in recovery tho.
Anyways, if you can get to download mode, youre likely gonna be just fine. Just download a fresh copy of your firmware and flash it with Odin with your phone in download mode
Battery Drained
AppleToaster said:
I can go on download mode now, but if I choose reset it sends me to the boot screen and then I see a dead android for a split second, then I'm in recovery mode. I can do nothing useful in there and restarting just freezes again
Click to expand...
Click to collapse
I know it's been a year, but I recently experienced the issue. So this is for...someone else? lol
If you had a PASS on Odin and yet you stuck on boot loop, chances are your battery is drained, and it might not successfully boot to run configuration and deletion. Connect it to a power source, it might prompt it to the boot loop but do it regardless. After like 15-30 mins, you should see the battery charging indicator. You should be good!

Categories

Resources