Related
hey guys/girls, so im fixing my friends phone it is a canadian Samsung galaxy note 3 (SM-N900W8) it is locked to rogers.
here is what he told me.
"I downloaded an emulator so I can play old games on it, I opened it and it didn't work so I rebooted my phone. but now it just powers on for about 8 seconds then shuts down. after about 3 hours it turned on so I went back on to the emulator and my phone started rebooting again."
it has been 3 weeks since this happened and it just keeps rebooting.
now, when I try reboot it in into recovery it stays on for 8 seconds then shuts down again. it wont even boot into the recovery.
when i try to reboot it into download mode it gets in for about 3 seconds then shuts down.
I have tried flashing cwm and twrp but download mode shuts down. the computer cant detect it quick enough.
I have checked the buttons and they were fine. not jammed.
the phone was not rooted(he wouldn't let me root it)
I need help with this. im stuck. please help me.
I thank you in advance
Hi
Thanks for writing to us at XDA Assist. Please standby while we have your thread/question moved to the appropriate sub-forum for your device.
For future reference you can find your device sub-forum here (bookmark/subscribe this):
Samsung Galaxy Note 3
Within that section you will find a dedicated q&a sub-forum (this is where your thread is going to be moved to):
Galaxy Note 3 Q&A, Help & Troubleshooting
Good luck!
Transmitted via Bacon
Try wiping system, data, cache, dalvik from your recovery if you can manage it. Also try removing SD-card if present. Some more info would be helpful for anyone trying to help you.
Hit Home, Power Up, and the Home button.
Then you'll be at the download/restart screen. After that, hit down to restart.
Thanks but i tried all of that and niether worked
Try odin
You can always download your official firmware from
sammobile.com/firmwares/
and flash it with Odin to fix bootloop problems.
Hey again. So my ZF3D is still stock, and today got a notification for an update. i hit ok and went on a walk with my wife (were trying to get a kid evicted from my wifes belly) and when i got back it is and has been stuck in fastboot mode. I have tried shutting it down and starting it up regularly, no love. I have tried starting it into recovery and nothing happens, it just jumps back into fastboot. When i try to manually go into fastboot mode it just returns to the screen its stuck at. ASUS loading screen with FASTBOOT MODE!!! and the battery percentage at the top in blue, no other options to choose from or scroll through.
Any suggestions on how to fix? I will keep looking through the forums here and hopefully ill either find the answer or get a response quickly.
Thanks in advance, and as always, you guys are awesome.
Nick
edit: I think you're in the wrong section if you have the ZS570KL. Check out that section of xda for more info here
Install TWRP from fastboot mode (I suppose you could flash stock recovery instead if you wanted). Reboot into recovery, plug usb cord in and your sdcard will become accessible. Download whichever firmware version you want, you'll probably have to edit the updater-script to allow the install, but that's just removing ~7 lines of code. Copy it to your sdcard and select it via the "install" section. Then wipe cache & dalvik and reboot.
So, about 6mos ago, my Nexus 10 stopped working and I couldn't get it back working...eventually moved onto a new tablet, which now I hate....
Anyway, I figured I'd head back to my N10 because I loved it. However, one of the reasons I left it was because it was stuck in bootloop and I was pretty sure it was bricked.
The bad news, I have followed MANY, if not ALL, of the suggestions on getting it back, I just cannot get it to boot. The good news, fastboot connects with the tablet. So, some specifics:
The tablet WILL boot into fastboot and I can send commands and the tablet is unlocked (also, I believe someone said they had issues because they had an older version of ADB and Fastboot. I'm pretty sure I downloaded the 'most current' version 1.4.3). So, with that, I was able to do the fastboot erase functions, such as cache, userdata, system, etc... and then also load the bootloader (mantafm01) and also send the stock .zip file (image-mantaray-....) and the tablet appears to load everything fine. Thumbs up, right? However, when it reboots it stops at the 'erasing' android bot and will not pass that. I left the tablet in that state for a few minutes all the way up to 3 days...no success.
I also tried the above using Wugfresh only to have the same thing occur. So, basically, I am stuck at 'erasing' and I don't know what to do. I feel confident that the tablet has the ability to be brought back to life, I just cannot figure out how/why all of the attempts lead to the same issue.
What I can also tell you is that while fastboot 'sees' the tablet, the tablet does not appear as a device in "My Computer" like it normally did when connecting via USB. I am using the original USB cable and have tried on multiple computers, all to no avail. I've downloaded/installed the drivers, as instructed on many links. Also, while I can get to the 'Recovery Mode' by pressing Power, Volume Up, Volume Down, if I choose "Recovery Mode" on the tablet, it reboots and goes to the 'erasing' screen. I have tried flashing TWRP on the tablet using fastboot as well. And, sometimes, not all the time, the TWRP blue/black screen appears but it will not progress past that screen (i.e., it doesn't go into recovery).
So, if you can, please help. I believe I have followed all of the instructions, but I have to be missing something or not following something correctly. I'm stoked that it looks like it's only soft-bricked, I just can't get it un-bricked.
Thanks in advance!
Looks like you are trying hard to find a solution. I think it may be helpful if you try to manually install the o/s rather that using Wugfresh and report back any errors. See
https://androidforums.com/threads/guide-how-to-flash-a-nexus-factory-image-manually.706533/ At step 11 I would flash the individual image files and also follow the instructions re erasing and flashing userdata.
AFAIK you will not see an Android device when using Fastboot - Android hasn't loaded at this stage.
Thanks peterk-1. Unfortunately, this does not work. I followed the steps, with the exception of the radio file as my Nexus 10 is wi-fi only. It goes through the stock image update perfectly fine and reboots itself. At that point, it's back to the moving android at the 'erasing' screen.
One thing to note with the link you provided; no where does it indicate flashing a recovery, stock or custom. Now, I've tried flashing stock, TWRP and CWM and none seem to work. TWRP comes closest with the black/blue splash screen, but will not open further.
Any other suggestions would be appreciated.
You did go to the posted link? I quote:
Step 8: We now want to wipe the device. Use the following commands in order:
........
fastboot erase recovery
............
Step 11: We will now flash the system, boot, and recovery ..........................................
fastboot flash recovery recovery.img
Unfortunately, same result...
Hi,
First timer here. I was just following these instructions trying to get Lineage on my new Mi A1. I can't post a link, but it's the official tissot guide.
I got to the Format Data step, where it complained that it can't unmount /data since resource is busy (although the previous step was done). There was a message saying the resource will likely not be useable until a reboot is performed, so I went ahead and did one. I suspect my error might have been here - I rebooted using the Vol - and Power buttons. Ever since it was stuck in the android one loading screen. Other than that all steps before went fine. I even have a backup.
Now I saw some other posts saying that I should just reboot into recovery and do something from there, but I can't get it to boot that way. Any button combination results in the same stuck finish. `adb reboot bootloader` throws `error: no devices/emulators found`. `fastboot' doesn't see any devices. I also saw something about the Mi Flash Tool, but I don't have a Mi account set up on the phone or even a Windows PC :crying:.
In how deep trouble am I? Is there anything I can still try? At this point I don't even know how to shut the phone down ...
Edit: upon further reading I think the phone won't boot in fastboot mode, but just does an ordinary boot. First it warns me to lock the bootloader, then it shows a Mi screen with `Unlocked` displayed at the bottom, and then it goes to the android one page where it freezes, regardless of how I reboot it.
I've solved my issue. I'm extremely ashamed to have made an account here and have this be my first post but: it's important to keep pushing the volume and power buttons until you see the fastboot menu on screen!!! Otherwise it will just perform a normal boot ...
Context
I was attempting to root my nothing phone (1). I initially got stuck into a boot loop after Flashing the patched boot image & rebooting the phone. I was following the tutorial here. I then followed this guide to attempt to get my phone out of the bootloop. I was able to access the adb & fastboot commands but the phone would keep restarting. I then started "STEP 4: Flash the Nothing Phone 1 firmware via the Fastboot commands" and failed to flash the odm partition. I stupidly ignored the very important warning to not exit the process halfway. I fastboot rebooted and then was greeted with a screen with: the nothing logo in the middle unmoving, the "powered by android" phrase, and nestled into the top left corner in very small font, "--any key to continue". The front of the text was cut off from the rounded corner of the screen.
Now:
When I press any of the buttons on the phone, the phone will go black and then immediately do a short vibration and turn right back on to that screen. If I hold the power and volume down buttons, the same thing happens even after holding it for almost 5 minutes. I can shut off the screen by holding just the power button for a few seconds but the phone will only turn on with the original error I had. When accessing the console on both my windows 10 PC and Linux laptop, the adb and fastboot commands are no longer able to detect a device. Neither of my computers can detect that the phone is even plugged in.
What I've tried:
I tried using a USB 3.0 fix: but failed
Running the commands on Linux: failed
nothing phone(1) fastboot flash by @sh4tteredd: failed
a slew of others that I've forgotten by now.
A common theme between the failures of all of my fixes is that the phone will not be detected by my computers. This was not a problem before I bricked the phone.
What are some solutions that might help me here?
Don't blame yourself. The phone hard bricks if you look at it wrong. This forum has several posts about the issue. Only solution is to send it to a support center.
coomac said:
Don't blame yourself. The phone hard bricks if you look at it wrong. This forum has several posts about the issue. Only solution is to send it to a support center.
Click to expand...
Click to collapse
no, this isnt hard brick. hard brick= no recovery, no fastboot, only edl
Gamer_Mida said:
no, this isnt hard brick. hard brick= no recovery, no fastboot, only edl
Click to expand...
Click to collapse
Did you read the post? There is no recovery or fastboot in this state. There are several posts and videos of this on this forum. I even posted one myself.
coomac said:
Did you read the post? There is no recovery or fastboot in this state. There are several posts and videos of this on this forum. I even posted one myself.
Click to expand...
Click to collapse
if it appears on the screen in fastboot press any button to turn off, it means that the bootloader is accessible, even if attached to the pc it does this thing, it is always accessible, therefore, it is not in hard brick
anyway it happened to me too, I know you also tried the usb 3.0 port, but this thing happened to me on another phone, I just changed the port and it worked (on the same pc)
It doesn't appear on the screen in fastboot. It's not the same as what you got on your Xiaomi phone even though the text is the same. Here you go. I don't mean to be rude but a quick search would have saved us this discussion.