[Completed] A Unique Bootloop? (Challenge) - XDA Assist

Okay so I have a bit of a situation and looking for some helpful advice, I'm not a complete novice but I seem to have gotten myself VERY stuck.
The Specifications:
Samsung Note 3 (rooted)
TWRP
Safe Strap
Rebooted recently and was in TWRP and accidentally chose "Recovery", phone now continuously Reboots into Recovery Mode in the upper left of the screen. I've tried to do the Volume Up + Power + Home button to no avail and every other combination I can think of, resulting in The same .. Reboot Recovery Option in the top left after about 10 seconds it Vibrates twice and reboots again.
I can't access TWRP, can't access Stock Recovery, Can't plug it into a PC as it just reboots over and over again after it gets power. Read a few things about Fastboot (Don't know if Note 3 Supports that, and Maybe Odin but I can't see how I'm to flash anything if it just immediatly reboots as soon as I plug it in)
HELP!

XDA Visitor said:
Okay so I have a bit of a situation and looking for some helpful advice, I'm not a complete novice but I seem to have gotten myself VERY stuck.
The Specifications:
Samsung Note 3 (rooted)
TWRP
Safe Strap
Rebooted recently and was in TWRP and accidentally chose "Recovery", phone now continuously Reboots into Recovery Mode in the upper left of the screen. I've tried to do the Volume Up + Power + Home button to no avail and every other combination I can think of, resulting in The same .. Reboot Recovery Option in the top left after about 10 seconds it Vibrates twice and reboots again.
I can't access TWRP, can't access Stock Recovery, Can't plug it into a PC as it just reboots over and over again after it gets power. Read a few things about Fastboot (Don't know if Note 3 Supports that, and Maybe Odin but I can't see how I'm to flash anything if it just immediatly reboots as soon as I plug it in)
HELP!
Click to expand...
Click to collapse
Hi, thanks for using XDA assist!
First, please create an account so you can post in other forums.
Here is your device's main forum area:
(You should bookmark this)
http://forum.xda-developers.com/galaxy-note-3
After creating your account, you can post your question here:
http://forum.xda-developers.com/galaxy-note-3/help
The experts for your device are located there and will be able to help.
Good luck!

Related

Cannot boot into recovery

i have a Galaxy Tab 2 7.0 p3113.
i used heimdall to flash CWM into the tablet.
after what seemed like a succesful flash, my tablet rebooted. but for some reason, it would only go as far as showing the galaxy tab logo. it seems stuck there. i could not turn the unit off. i would hold the power button to force shutdown, but it always starts right back up. it seemed like i could only shut it down if it was connected to my mac while holding down the power button. i can however, boot into download mode.
after consulting google, it seems like the appropriate step was to restore the unit to stock. problem is, i can't seem to boot into recovery. i'm being told by the internet that to boot into recovery, i need to hold [power] and [volume down] until it turns on and then release [power] but keep on holding [volume down] and CWM will load. but nothing happens.
i know this is a total noob post, but i've been scouring the web for two days. i'm at my wits end. any help would be greatly appreciated.
I think recovery mode accessed via volume up+power if you could not so use download mode to flash stock or so to return to normal operation
Sent from my GT-I9100 using xda app-developers app
I press the power and UP ( button next to the power button) I normally hold BOTH buttons down at once and let the boot cycle process twice just to make sure i am going into recovery .....so i see the white samsung text twice i mean. It may take around 10 seconds to complete the process. Then release BOTH keys at once.
The battery needs a good charge for it to work.. Try charging over night before you try it via the mains supply.
Holding the power button and down will bring you into download mode and thats what you use for an odin/heimdall flash.
Hope that works for you
Let us know how you get on .....
Thanks. The battery of the gtab2 drained overnight, so i've got it charging back up now. Will definitely post my results when i have something.
Thank you guys. I'm able to boot into recovery now.
But unfortunately, i still need a little guidance on my original problem. And that problem being that my gtab2 will not startup. After rebooting, it gets stuck on the logo screen. It also plays a startup audio clip. But after that, it just displays the startup logo screen. It does not go into the animation screen and start.
I should also mention that when i plug my gtab2 into my computer, no drives show up.
My question now is, if i were to select [wipe data/factory reset] in CWM, would this restore my gtab2 to it's original factory state? Or would I need to flash a ROM for this? And if i need to flash a ROM, could i place a ROM on a microsd card and flash from there?
*********UPDATE*************
Everything is fine (so far).
I went poking around CWM and realized that I had put a cyanogenmod 9 update.zip in the root of the internal sd card before all this happened. So i went back to cyanogenmods wiki on how to install it on my gtab2 and followed the rest of the instructions on flashing it and VOILA!! I have my gtab2 back.
you should use ODIN instead CWM.
CWM is not designed specifically for Gtab2.

[Completed] Android boot loop - is my device dead?

Hello All,
This is my first post at this forum.
I've come to a point where I'm on the verge of giving up.
A few days ago my Nexus 5 entered a boot loop without me doing anything special with it - it was just in my pocket.
All see is the google logo for a few seconds , then the screen goes down for a few more, and back to the google logo.
I'm able to go into fastboot by hold down the volume down (only) button when this happens, but the boot loop happens when I choose to boot into recovery mode.
My device has an unlocked bootloader.
I have fast boot access and no ADB (ADB wait-for-device doesn't work).
Went over a tutorial from androidforums.com and flashed a completely new image using fastboot.
The entire process worked, but the phone is still at the same state.
I've read that there is and issue with the power button on these devices - so I tried all methods of knocking it against stuff without success.
I've taken it to a lab nearby and the guy there was sure it was the power button. He said he fixed about 50 of these already - after a few hours he called me up and said he had replaced the power button 3 times and he's giving up.
in short , this is the current situation :
1. Device stuck in bootloop - only google logo is seen
2. can boot into fastboot (and have fastboot access from PC) but can't boot into recovery
3. flushing a stock succeeds but won't help
4. power button seems o.k.
I am about to call this a bricked phone and look for a new one but something inside me tells me that this might still be a software issue and can be fixed.
I would be happy to know if there is a way to know what is failing in the boot sequence. or maybe load a debug application on to the device to check the HW. I've yet to find any help in that direction.
I'm a software eng. working in the cellular comm. field, so I'm up for anything that anyone has in mind.
Thanks,
Ran.
XDA Visitor said:
Hello All,
This is my first post at this forum.
I've come to a point where I'm on the verge of giving up.
A few days ago my Nexus 5 entered a boot loop without me doing anything special with it - it was just in my pocket.
All see is the google logo for a few seconds , then the screen goes down for a few more, and back to the google logo.
I'm able to go into fastboot by hold down the volume down (only) button when this happens, but the boot loop happens when I choose to boot into recovery mode.
My device has an unlocked bootloader.
I have fast boot access and no ADB (ADB wait-for-device doesn't work).
Went over a tutorial from androidforums.com and flashed a completely new image using fastboot.
The entire process worked, but the phone is still at the same state.
I've read that there is and issue with the power button on these devices - so I tried all methods of knocking it against stuff without success.
I've taken it to a lab nearby and the guy there was sure it was the power button. He said he fixed about 50 of these already - after a few hours he called me up and said he had replaced the power button 3 times and he's giving up.
in short , this is the current situation :
1. Device stuck in bootloop - only google logo is seen
2. can boot into fastboot (and have fastboot access from PC) but can't boot into recovery
3. flushing a stock succeeds but won't help
4. power button seems o.k.
I am about to call this a bricked phone and look for a new one but something inside me tells me that this might still be a software issue and can be fixed.
I would be happy to know if there is a way to know what is failing in the boot sequence. or maybe load a debug application on to the device to check the HW. I've yet to find any help in that direction.
I'm a software eng. working in the cellular comm. field, so I'm up for anything that anyone has in mind.
Thanks,
Ran.
Click to expand...
Click to collapse
Hello, and welcome to XDA!
It does sound like a hardware issue and it could be the power button, except for one thing: wouldn't a held down power button in fastboot cause a shutdown as well? Maybe not, but I thought I'd ask that.
At any rate, better to get an opinion from someone who actually has the deivce. Please create an account (so you post in other forums) and then post in this thread (can copy and paste from here):
> Google Nexus 5 > Nexus 5 Q&A, Help & Troubleshooting > [HELP THREAD] Nexus 5
Hope this helps, and good luck!

[Completed] Can't boot into download mode Samsung Galaxy S7

Ok, I bought a galaxy s7 from my friend, because he was getting a new phone, but I discovered that wifi wasn't working at all, so I thought it had to do something with the firmware and I decided to flash the rom with odin, with a newer version of the firmware.
This is where all my problems started, when I restarted my phone for the first time I noticed that the startup/booting animation was some weird ****, not like the usual one (the samsung logo) but was a weird loud animation with the letters of MTK, in that moment what came to my mind was that I just could be a custom rom or just a custom boot animation, so I didn't gave it too much attention, I continued to do what I was gonna do and tried to boot my phone into download mode with the classic normal method , Volum Down+Home+Power, when I tried this apparently It didn't work, I could stay there pressing the buttons for like 5 minutes and nothing would happen, and once I would release them, the phone would turn on and do the weird animation and boot like normal, at this point I was already worried so I proceded to Root my phone with KingRoot and install an app to manually boot my phone into download mode, it didn't worked. After hours of searching for a solution I found about ADB and I did all the steps to boot my phone from there, still nothing, when I typed the "abd reboot download mode" or something like that, the phone would just restart and do the ****ing weird animation again, so I tried booting into recovery mode and when I tried to do it, an android robot would appear laying on the ground with his chest open, and the words "No command". When I would press the home button the phone would react and send me to the recovery mode, normal.
So I'm begging you guys for help, since I don't know what to try now.
It looks like the download mode or maybe the firmware is broken, and I can barely do something without the download mode, pls help.
What I've tried so far:
-Basic 3 buttons method (can't remove battery, it's an s7)
- ADB method
- ADB fastboot method
- Vol Up+Vol Down+Home+Power
- Can't do anything with Odin since I need download mode
- Tried to install twrp recovery mode from ADB but says that It didn't found the file
If someone knows a solution for this please tell me what I can do.
Hello,
Welcome to XDA.
Try posting your question in the forum linked below.
http://forum.xda-developers.com/galaxy-s7/help
The experts there may be able to help.
Register a XDA account in order to post and reply in the forums. Good luck.

[Completed] Galaxy S5 booting into recovery and download problems

My galaxy s5 has a broken volume Up button, and it mostly hasn't been a problem up to this point. I could reboot into recovery and download using advanced reboot or ADB whenever I needed to, but then I bricked my phone with a faulty Lineage OS update. I can now turn the phone on, but it gets stuck on the Samsung logo, never progressing. I can't boot into recovery to recover a backup or flash a safe Lineage zip because my phone's Volume Up button is broken. I cant boot into download to flash using ODIN because after I get to the warning screen, I can't confirm I want to go into download mode with the Volume Up button. Is there any way to force boot into Download or Recovery (maybe using some computer program or something like it) so I can fix the OS and get out of a bricked phone? I don't care about loosing data since I knew the risks going in and have plenty of backups. So far, the only "solutions" I have found have required the phone's ADB (which I cannot access since I cannot boot up the phone), and a promising program that force boots Download mode through a charging cable (which I couldn't download because it was marked as "potentially dangerous" to my computer, A.K.A. a virus).
Repairing the phone's volume button is very complicated and expensive, so that is not an option. Getting a new phone is an option, but it is the option of last resort. Is there anything I can do to salvage this phone?
Hi there and welcome to assist,
I would suggest, get the power button replaced, because you'll get locked out, when battery runs out or phone turns off!
You'll have to create an account to post in the main forums if you have any other questions.
> Samsung Galaxy S 5 > Galaxy S 5 Q&A, Help & Troubleshooting
Good luck

Redmi note 9 softbricked

Hello, i do not know where to post this but i really need help solving this issue.
I was installing twrp on my Redmi note 9 (merlin) and once the set up was done my phone rebooted to twrp, but it took time (a lot of time).
And i could not resist the urge of pressing the power button to restart it, problem is miui was not starting and it was stuck at the boot logo, i figured out it was a great idea to press the power button again, but it booted up on twrp, wich worked but the screen seem to be frozen and doesn't register any tap on the screen or anything, and now each time i press the power button no matter how, it either boots on my broken twrp recovery, or boots on my absolutely destroyed os.
PS: No matter how hard i try it seem to be impossible for me to access fastboot too...
kyaaa_ said:
Hello, i do not know where to post this but i really need help solving this issue.
I was installing twrp on my Redmi note 9 (merlin) and once the set up was done my phone rebooted to twrp, but it took time (a lot of time).
And i could not resist the urge of pressing the power button to restart it, problem is miui was not starting and it was stuck at the boot logo, i figured out it was a great idea to press the power button again, but it booted up on twrp, wich worked but the screen seem to be frozen and doesn't register any tap on the screen or anything, and now each time i press the power button no matter how, it either boots on my broken twrp recovery, or boots on my absolutely destroyed os.
PS: No matter how hard i try it seem to be impossible for me to access fastboot too...
Click to expand...
Click to collapse
I was able to get this issue fixed by :
1 Installing adb
2 Opening cmd inside adb folder
3 Entering "adb devices" while the device was connected
4 Then entering "adb reboot bootloader" while the device was still connected
5 Once the device was in bootloader mode i installed miFlash and downloaded this rom : mifirm.net/download/4163
5.1 If you have an error with the drivers, create a folder named log inside of the said miFlash folder
5.2 Also make sure that the path to the rom is not too long (i heard that miFlash had problems handeling long paths)
6 Once everything was set up i just hit flash and flashed the rom onto the phone
7. You're done ! You successfully repaired your phone and saved him from the depth of hell!
If you have any problems or need precision on certain points make sure to ask me in this thread so that other people can get help too.
i had flashed k20pros dtbo img file by mistake and my phone is not even turning on and no fastboot no recovery what to do please help!!!

Categories

Resources