Related
After my last attempt to put some ROM to keep a stable, result is the following - when i try to go in "Download Mode" , at the top left appears a text "KeyPressed,1". I search here, in Google, but nothing.. I think my phone is HARD BRICKED I'm asking for your help, i know you are erudite people, and only you can help me! Thank you, for listening my problem! Thank you!
So am I right that you can't boot your phone? What happens when you turn on your Phone ? Bootloop?
KUN1 said:
So am I right that you can't boot your phone? What happens when you turn on your Phone ? Bootloop?
Click to expand...
Click to collapse
Ive got the exact same problem
Ill explain my problem in more depth
phone bootsup and flashes a pic of the android then goes into recovery mode so cant geto normal phone operations
under advanced , log it says checked for extendedcommand...skipped exection of extendedcommand, file not found...
other interesting thing to note center button does not work ie using only voulume and power switch but the touchscreen back button works
when I try to put in dl mode it does show yellow android but has keypressed,1 on screen as well ,
Computer knows that devise is there but doesn't show it up and Oden 1.7 sometimes picks it up but doesn't successfully update files says it failed
Thanks for your interest
have a read here http://forum.xda-developers.com/showpost.php?p=30415128&postcount=1
Hi guys, i gonna tell you about how my i9001 was stuck in a bootloop. Maybe you could help me. I'm sick of it.
Cause: I installed cm10 and cwm5 or 6 as recovery and upgrade my device using Ota Updater. When I restarted my i9001, it got stuck in a bootloop.
What my i9001 can display: It can access to rampdump mode and download mode. In case I try to turn on my i9001 or access to recovery mode the Samsung logo/word is shown twice and stops showing anything else. It often gets stuck showing the typical grey battery flat (with a loading stopped) and the black screen alternately. This is caused when I a disconnect the USB cable from my computer/laptop.
Attempts: i've tried everything except for the right solution. Lots of forum threads and nothing works for me. I've tried:
1.- Boot_loader for device boot.
2.- I've flashed an stock rom: XXKQP, and 2 more: BVKPC y XXKQ1. Each one are official.
3.- And then recovery-clockwork-5.5.0.4 and -6.0.1.2.
4.- I've tried, then, flashing feamodrecovery 1.2.
5.- Nothing works for me.
I've been using Odin 4.43. AriesVE in OPS section and when flashing these roms: one package. For recovery packages: one package and pda (I tried these two options).
I can't reach at recovery mode. Any help would be greatly appreciated. Greetings!
have a look here http://forum.xda-developers.com/showpost.php?p=30415128&postcount=1
When phone boots there's nearlz always a solution
Sent from my GT-I9001 using xda app-developers app
slow--welder59, any of these solutions helped me. I tried with any other combination of combos but nothing happened. I didn't know to use adb method. I installed adb drivers but it didn't detect my device. When I entered to download mode and pressed Install (in the program) tried to download something but it stopped.
Any suggestion?
Can anyone help me? I want to exhaust all possible options.
zerohhorez said:
Can anyone help me? I want to exhaust all possible options.
Click to expand...
Click to collapse
What happens when you try to format data from recovery...?
If you get some errors, write them here...
If everything goes well, then it is not what im expecting (in that case problem is probably easier to solve)...
sava92ns said:
What happens when you try to format data from recovery...?
If you get some errors, write them here...
If everything goes well, then it is not what im expecting (in that case problem is probably easier to solve)...
Click to expand...
Click to collapse
The problem is just this. I cannot go to recovery mode. Just shows Samsung twice and powers off.
zerohhorez said:
The problem is just this. I cannot go to recovery mode. Just shows Samsung twice and powers off.
Click to expand...
Click to collapse
Can you open 'Download mode'?
sava92ns said:
Can you open 'Download mode'?
Click to expand...
Click to collapse
Yes I can, and that's the reason why I don't give up hope. However, I've tried installing some stock roms and recoveries and nothing worked for me.
Try one of the following (or both even if your desperate):
http://forum.xda-developers.com/showthread.php?t=1922505 (broodROM RC5 download link) [recomended]
http://broodplank.net/old/flashsamsungi9001.php (skip chapter 5 as it doesn't apply) [if that doesn't work]
edit:: USB Drivers: http://forum.xda-developers.com/showthread.php?t=961956
stepie22, thank you for your help. Nothing worked for me.
First link: another typical manual for installing a stock rom via Odin. During the process my device powered off. It was supposed to reboot. After the process ended, i disconnected it from PC and its screen showed a grey empty battery (with a loading in the middle) and word "Samsung" alternatively.
Second link: this was the solution for my first brick. Then, my device showed this yellow triangle. This second time is annoying me. I haven't found any solution to change, at least, the behaviour of my device.
Any other different solution? Thnks guys.
zerohhorez said:
Then, my device showed this yellow triangle.
Click to expand...
Click to collapse
See this ... if that is the triangle, find that part on the wiki page.
Maybe your device got the eMMC Bug?
Normally your Device would be hardbricked if you "over" flashed.
If nothing works out try this:
Have a look in this thread:
http://forum.xda-developers.com/showthread.php?t=2224029
Download CWM Recovery 6.0.2.8 ODIN Package and flash it in "Download Mode" the regular way (AriesVE.ops and onepackage).
Then maybe you are able to enter Recovery Mode again...
This might be not your problem, but you could give it a try:
Some people had issues with rebooting in recovery, so there is a fix in this post
http://forum.xda-developers.com/showpost.php?p=24831012&postcount=1330
Hopefully one helps you!
Greetings
Howdy there.
First off, this is not "just another bricked Note thread".
I got this thing from a friend who did not have a clue what he did with it, but he told me he tried to "root it or something" He didn't have any files left, or any memory what he used.
I have for weeks tried every single trick in the book, followed every tutorial, and it shows no sign of coming to life any time soon.
When I got it, it just got stuck on the Samsung flash screen. I couldn't get into any sort of recovery, but I got into download mode, so I tried reflashing the stock firmware with ODIN, but it got stuck on NAND WRITE START for 2 hours, and then failed. All Kies processes were killed, I double checked.
After that, it only shows the "Firmware update failed, start emergency recovery mode in kies"
Kies does not support initialization for N7000, doubted it would have worked anyways.
After this, I went on to read about the brick bug for N7000
Since then I have tried repartitioning the device with all kinds of pit files, I have tried installing about 20 different firmwares, I have tried installing just a kernel, both stock and others, and NOTHING works.
Some pit files get stuck in DO NOT TURN OFF DEVICE for 6-24 hours, until I have disconnected or battery has run out, and some fail by themselves after 20 minutes.
Firmwares get stuck at NAND WRITE START, and fail after about an hour
Kernels fill up the bar with the green dots showing it's doing something but as soon as the log says "NAND Write Start" it gets stuck.
Is there ANYTHING still worth testing, before throwing it in the well? I will not go to a service center and pay to fix a spare phone that will lay in a box until I MIGHT need it some day.
It doesn't matter if my storage space goes down to only 500mb space with some sort of repartitioning, nothing matters. I just want it to run.
I do not have any recovery, and I haven't successfully installed any,
Basically the only thing I can do, is get to Download mode, and the only program so far finding it is ODIN.
I am very thankful for any help, and don't hesitate checking if I forgot something very basic, I might just as well have forgot something very important, but I feel I have tried everything.
Thank you!
-Jimi
It is exactly this: just another bricked Note thread.
ThaiDai said:
It is exactly this: just another bricked Note thread.
Click to expand...
Click to collapse
Well, okay then. Thanks for clearing that up.
I just figured that it's something worse since NOTHING works, hence the "not just another" meaning "not just the same as the others". Atleast I thought it meant that. Perhaps my English isn't so good. Oh well.
I have read dozens of other threads about this where people have been able to get into recovery mode, repartition, or flash a new kernel, or at least SOMETHING, but mine just blocks everything.
-Jimi
Okay then, let's simplify the question/request.
Is there ANY way at all to scan or/and repartition my emmc?
WITHOUT a recovery.
WITHOUT it accepting anything through ODIN, not even the standard pit file, or any of the custom ones I have tried from another thread.
WITHOUT adb.
I can only get to Download Mode.
Heimdall seemed to understand my phone a bit, but couldn't flash anything.
Kernels got stuck at 100%
Factoryfs got stuck at 4%
Recovery got an error "finishing the packet" or something.
Could I use Heimdall to scan or repartition my emmc maybe?
If you are unable to Odin flash a recovery or stock rom then there's no other way. If you found other methods but is still unsuccessful then your phone is dead anyways.
I have seen the NAND write stuck error sometimes goes away on a different PC. If the memory is not already broken but worth a try.. Also use original USB cable, main PC usb port, odin 1.85.
nokiamodeln91 said:
I have seen the NAND write stuck error sometimes goes away on a different PC. If the memory is not already broken but worth a try.. Also use original USB cable, main PC usb port, odin 1.85.
Click to expand...
Click to collapse
Nah, I think the memory is broken.
I have only tested with odin 1.75, but on 3 different PCs
My laptop with Win 8.1
My old computer with XP
And my work computer with Win 7 home
Still, I do not want to give up!
In my frustration I started to flash everything and anything that just had a N7000 tag on it, and somehow somewhere something happened.
I do not have the "firmware failed, use kies recovery" message anymore.
I am instead getting the Samsung splash screen, but it freezes there, I can't do anything.
And also, if my device is off, I can charge it! The battery shows up, but then it freezes with the circle in it before it fills with green to show how much it is charged, but now it atleast accepts charge. Before it didn't.
But I still wonder if I could not scan and repartition my phone with anything else than recovery mode? Perhaps I could flash a repartitioned custom Pit file with Odin if I could just scan it somehow?
I got a similar problem with my uncle's Note. It was working fine all these years, until last month when I rooted it to upgrade it to 5.1. The phone worked for over a month post upgrading.
However, now, when I power it up, nothing happens, absolutely nothing. If I connect it to a power source, the offline battery charging symbol comes up saying 100%. Recovery mode doesnot work, though I can go in Download mode.
I tried a couple of stock ROM images through ODIN. They were flashed successfully, but the issue persists. Looks like another dead Note.
froyoguy said:
I got a similar problem with my uncle's Note. It was working fine all these years, until last month when I rooted it to upgrade it to 5.1. The phone worked for over a month post upgrading.
However, now, when I power it up, nothing happens, absolutely nothing. If I connect it to a power source, the offline battery charging symbol comes up saying 100%. Recovery mode doesnot work, though I can go in Download mode.
I tried a couple of stock ROM images through ODIN. They were flashed successfully, but the issue persists. Looks like another dead Note.
Click to expand...
Click to collapse
Which rom was this?
AutumQueen92 said:
Which rom was this?
Click to expand...
Click to collapse
Thanks for your reply. Couldn't check it until last night. I was running NightOwl when this happened. Last night, I thought something and flashed the same Philz recovery through Odin and some how it worked.
I have started realizing that it is a hardware issue, since the device does not start without being connected to a power source. 1 out of 20 tries take me into recovery (of course while the device is connected to the charger, or else the screen is always black).
However, the recovery doesn't stay too long. I tried flashing a newer version of NightOwl, but while the recovery is still opening the package, the phone restarts .
One weird thing is that the phone doesn't starts without being connected to the PC or the charger. But when connected, within seconds, the offline charging screen says 100%, which is making me believe something is wrong with the hardware.
Part of the "hardware" is your battery...
I was using the Cyanogen version made by Hazou. It was working great but occasionally(a month or so) it got stuck in a bootloop and I cleared the dalvik cache which fixed it.
This time it turned off while cleaning the cache possibly due to battery (I dont know how much battery was left).I turned on the phone and it was in the same bootloop. I soft reset it but it didnt turn on. So I tried every method to get to the fastboot mode or anything else.
Nothing. Its almost dead. Except that the green led turns on if I turn on the phone. When soft reset it turns of and turns on again. When I try fastboot mode it turns off, turns on and then goes off.
My PC recognizes the device as MEDFIELD sometimes, nothing else.
I tried the unbrick script but couldn't get it to work. It doesn't find my device and just goes to twenty.
Need your help. I will be grateful for your help and thanks in advance.
If nothing else. Do tell me how I can retrieve my data. Thanks
Update:I managed to get the midfield drivers installed. The unbrick tool closes after 30 seconds of working. The phone restarts and then nothing.
Rsdlite is showing the midfield device now as well.
I tried flashing a stock version via rsdlite but it gave the error that it failed to switch to fastboot mode.
I did a soft reset and then immediately pressed the camera button and connected the USB cable and ran the unbrick script. The same thing happened and the window closed after a few seconds. The phone still dead.
Danish78 said:
I was using the Cyanogen version made by Hazou. It was working great but occasionally(a month or so) it got stuck in a bootloop and I cleared the dalvik cache which fixed it.
This time it turned off while cleaning the cache possibly due to battery (I dont know how much battery was left).I turned on the phone and it was in the same bootloop. I soft reset it but it didnt turn on. So I tried every method to get to the fastboot mode or anything else.
Nothing. Its almost dead. Except that the green led turns on if I turn on the phone. When soft reset it turns of and turns on again. When I try fastboot mode it turns off, turns on and then goes off.
My PC recognizes the device as MEDFIELD sometimes, nothing else.
I tried the unbrick script but couldn't get it to work. It doesn't find my device and just goes to twenty.
Need your help. I will be grateful for your help and thanks in advance.
If nothing else. Do tell me how I can retrieve my data. Thanks
Update:I managed to get the midfield drivers installed. The unbrick tool closes after 30 seconds of working. The phone restarts and then nothing.
Rsdlite is showing the midfield device now as well.
I tried flashing a stock version via rsdlite but it gave the error that it failed to switch to fastboot mode.
I did a soft reset and then immediately pressed the camera button and connected the USB cable and ran the unbrick script. The same thing happened and the window closed after a few seconds. The phone still dead.
Click to expand...
Click to collapse
same situation here... i already gave up since a year
I got the same here.
Sent to Motorola repair and they told there wasn't anything to do.
Tryied the unbrick(http://forum.xda-developers.com/showthread.php?t=2390573), but didn't work.
BUT
Today, i gave another chance to it, and did it again, in Windows 7(was using windows 10 before).
IT WORKED!
Now it's fine again
Just made it 2 hours ago haha
So, download this:
forum.xda-developers.com/attachment.php?attachmentid=2161740&d=1375522827
Install the .exe, BUT, when the pop up appears asking "will a ... be connected...", connect the cellphone in USB WITH THE CAMERA BUTTON PRESSED(AND DON'T RELEASE IT UNTIL YOU FINISH ALL THIS TUTORIAL).
After installing, execute the unbrick.bat as administrator(WITH THE CAMERA BUTTON PRESSED)
Wait some minutes until done(WITH CAMERA BUTTON PRESSED)
Good luck, ressurrected mine today 1 monthe after giving up.
diguincoutoreis said:
I got the same here.
Sent to Motorola repair and they told there wasn't anything to do.
Tryied the unbrick(http://forum.xda-developers.com/showthread.php?t=2390573), but didn't work.
BUT
Today, i gave another chance to it, and did it again, in Windows 7(was using windows 10 before).
IT WORKED!
Now it's fine again
Just made it 2 hours ago haha
So, download this:
forum.xda-developers.com/attachment.php?attachmentid=2161740&d=1375522827
Install the .exe, BUT, when the pop up appears asking "will a ... be connected...", connect the cellphone in USB WITH THE CAMERA BUTTON PRESSED(AND DON'T RELEASE IT UNTIL YOU FINISH ALL THIS TUTORIAL).
After installing, execute the unbrick.bat as administrator(WITH THE CAMERA BUTTON PRESSED)
Wait some minutes until done(WITH CAMERA BUTTON PRESSED)
Good luck, ressurrected mine today 1 monthe after giving up.
Click to expand...
Click to collapse
could you give more details how you did that ? I'll tried but it gives me USB I/O Error after a while and then stucks :/ also there is no .bat in the zip, i'll tried another one from a moto unbrick zip here on xda
diguincoutoreis said:
I got the same here.
Sent to Motorola repair and they told there wasn't anything to do.
Tryied the unbrick(http://forum.xda-developers.com/showthread.php?t=2390573), but didn't work.
BUT
Today, i gave another chance to it, and did it again, in Windows 7(was using windows 10 before).
IT WORKED!
Now it's fine again
Just made it 2 hours ago haha
So, download this:
forum.xda-developers.com/attachment.php?attachmentid=2161740&d=1375522827
Install the .exe, BUT, when the pop up appears asking "will a ... be connected...", connect the cellphone in USB WITH THE CAMERA BUTTON PRESSED(AND DON'T RELEASE IT UNTIL YOU FINISH ALL THIS TUTORIAL).
After installing, execute the unbrick.bat as administrator(WITH THE CAMERA BUTTON PRESSED)
Wait some minutes until done(WITH CAMERA BUTTON PRESSED)
Good luck, ressurrected mine today 1 monthe after giving up.
Click to expand...
Click to collapse
screenshot added
micash said:
screenshot added
Click to expand...
Click to collapse
Worked?
Mine got some errors too on the bat, but after that it revived.
(maybe the usb error was that you left the camera button, it need to be holded all time since the first step of the SoC exe installer. The green light have to be turned on all the process)
unfortunately not. did you have the same error? could you send me your .bat file and stuff you used?
i held the button the whole process pressed. maybe wrong i dont know
---------- Post added at 12:05 PM ---------- Previous post was at 12:02 PM ----------
diguincoutoreis said:
Worked?
Mine got some errors too on the bat, but after that it revived.
(maybe the usb error was that you left the camera button, it need to be holded all time since the first step of the SoC exe installer. The green light have to be turned on all the process)
Click to expand...
Click to collapse
how long does it took until it finished? what to do when the process is done? normal turn on? maybe my battery is empty, i dont see that its charging or something, i got only a black screen and that greed led.
micash said:
screenshot added
Click to expand...
Click to collapse
micash said:
unfortunately not. did you have the same error? could you send me your .bat file and stuff you used?
i held the button the whole process pressed. maybe wrong i dont know
---------- Post added at 12:05 PM ---------- Previous post was at 12:02 PM ----------
how long does it took until it finished? what to do when the process is done? normal turn on? maybe my battery is empty, i dont see that its charging or something, i got only a black screen and that greed led.
Click to expand...
Click to collapse
Not too long. Maybe 2 minutes.
Yeah, after the .bat finishes, it restarted with the motorola logo and like a normal first time flash.
The battery will be empty, it won't recharge until you ressurect it(and will took a very long time this recharge).
Used this that i posted to you.
diguincoutoreis said:
Not too long. Maybe 2 minutes.
Yeah, after the .bat finishes, it restarted with the motorola logo and like a normal first time flash.
The battery will be empty, it won't recharge until you ressurect it(and will took a very long time this recharge).
Used this that i posted to you.
Click to expand...
Click to collapse
still that USB I/O ERROR thingy :/
Hello, I am in the same situation.
MEDFIELD device identified, but without sucess in unbrick.bat procedure with camera button pressed.
My log just have XFST-LOGs, in screenshot i can see XFSTK-PROGRESS.
Someone can help me?
I tried to update my SM-N9600 that was stuck on android 8.1, it wont show any update so i tried to install this firmware https://www.sammobile.com/samsung/galaxy-note9/firmware/SM-N9600/ANC/download/N9600ZHS5ETI1/396464/ and followed the odin instrucions.
It turns out it failed at the end and i got a blue screen with the message "an error has occurred while updating the device software use the emergency recovery function" which i don't have so i kinda panic and used this frphijacker software which sent me to where i am now, stuck at boot screen and the phone will won't even turn off, wont connect to the computer with usb cable either.. i hope when the battery drain i could turn it on recovery mode but i'm uncertain..
Would really appreciate any info or any help
just wanted to say to any admin that they can close or remove this thread. After the battery died i could turn on the phone in download mode and after a couple tries with different firmwares i finally managed to solve the issue.. kinda of a pain in the ass and scary af since i'm like user level so.. thanks anyway!
eris_zan said:
just wanted to say to any admin that they can close or remove this thread.
Click to expand...
Click to collapse
Thread closed per OP request.