Android Stuck on boot logo - Android Q&A, Help & Troubleshooting

Sorry if this is in the wrong thread, not sure where to put it,
I own a NATPC M009s x2.
I rooted it today and was hoping to install the cwm.
I had to install the driver manually so i tried to install it through the recovery mode
However after I did this the device wouldnt boot up past the boot logo and im not too sure what to do.

Unfortunately this is a soft bricked device now. You can either try to use ADB to attempt rebooting into recovery.
EDIT: If you do not have cwm successfully flashed, (this is based off of previous experience) there is no way to fix this. Please correct me if I am wrong, I rooted my first phone and factory reset it through the stock rom without a recovery. Sent the phone into a boot loop. I did write a program (Mango Tools) to help fix this however, it can be found on mellowdev.net It is being updated atm but wouldnt mind emailing it to you if you PM me.
Sent from my Nexus 4 using xda premium

Related

[Q] possible bricked lg ls670(optimus s)HELP

My son, in all his wisdom didnt see a need for the custom recovery or nandroid. Except now his phone wont boot so I am unable to get an adb shell. It is stuck at lg boot screen. I can get to the stock recovery which is s-on apparently. I do have backups of the stock img files. system, boot, recovery, etc. He said he was trying to add a custom kernel to the boot img via adb when he encountered the problem. Is it possible currently to flash a new kernel and or rom via the stock recovery? I cant seem to get past the verification. Any help is greatly appreciated.....
Go to stickies on forum and you will see what you have to do.. you need KDZ updater and the stock image.. that's what worked for me..
Sent from my LS670 using XDA App
Hi again everyone, Ive managed to brick my optimus s. It wont boot, charge, flash buttons or connect to pc. Is there any hope for my phone? If so, please share. Thanks

installing eclipse .4 from p3 preroot

i tried to use the recovery and install it but i got stuck in a boot loop. so then i sbfed back to froyo then rooted it then installed the recovery then updated it and got stuck on the "dual core" boot loader. im not sure what im doing wrong. i would post in the thread but i cant since i dont have enough posts
Same exact thing happened to me today. What i did was pull the battery and booted it back up in recovery (power button and down volume button) and did a factory reset. booted it back up and it seemed to work right.
tried that im on my 2nd round of sbf root recovery reflash. of this doesnt work im going to bed i have a 15 hour double shift tomorrow
thanks stx that worked. if anyone can post in the thread that there is a possible bug in flashing this from the p3 preroot it would be cool. it would also be cool if anyone knew how i could sync with facebook too
gnuworldorder said:
i tried to use the recovery and install it but i got stuck in a boot loop. so then i sbfed back to froyo then rooted it then installed the recovery then updated it and got stuck on the "dual core" boot loader. im not sure what im doing wrong. i would post in the thread but i cant since i dont have enough posts
Click to expand...
Click to collapse
Did you wipe data before installing? Also could you confirm the MD5 Hash
917649e16b63d99a7ec30e3c6b6f02b3 Eclipse_v0.4.zip
installed it many times from the prerooted confirms it works fine just make sure you wipe once you get into recovery and my sure you plug your phone into the wall before getting into recovery because it will not boot into recovery and get stuck in motorola logo without being plugged in
after I factory reset it it booted fine.
Sent from my DROID X2 using XDA App

[Q] Bricked Prime, fixed but still has a problem

Hi, so I bought a used TF201 from someone that had already rooted and put CM10 on the tablet. However, idiot me decided to factory reset using the system settings instead of going into the CWM and doing a factory reset. This put me into a CWM loop, as I could only boot into CWM recovery mode. I used this guide to unbrick my device, and it worked. However, the problem is that everytime I want to update CM10 to a new nightly, I get stuck in CWM recovery again, and have to apply the fix every time. Is there any way to fix this? I don't want to have to do the unbricking every time I update CM10. Thanks!
yeee707 said:
Hi, so I bought a used TF201 from stock someone that had already rooted and put CM10 on the tablet. However, Idiot me decided to factory reset using the system settings instead of going into the CWM and doing a factory reset. This put me into a CWM loop, as I could only boot into CWM recovery mode. I used this guide to unbrick my device, and it worked. However, the problem is that everytime I want to update CM10 to a new nightly, I get stuck in CWM recovery again, and have to apply the fix every time. Is there any way to fix this? I don't want to have to do the unbricking every time I update CM10. Thanks!
Click to expand...
Click to collapse
Stop using CWM. That is what is causing all your problems. Go to TWRP website and get ICS version. Make sure you don't flash the jellybean version on your ICS bootloader or you might brick it.

Need Some Help!

So I'd been having some problems lately with my phone hanging on the Samsung screen on boot. Been running CM11 1/1/2014 nightly most recently. Decided to try using TWRP instead of CWM. That didn't seem to help my issue, so I tried installing CWM again. I used an app called Recovery Tools to download the touch version of CWM. After it said it installed, I tried to boot into recovery and got the error "Unauthorized software found. Please contact Verizon." (paraphrased a little).
Doing some research it looks like that error typically comes up when the bootloader is locked. Now, obviously I had my bootloader unlocked (well, Loki'd) because I was running CM11. Any help fixing this? I'm able to bypass the warning screen on boot if I hold down vol up + power like I'm going into download mode, but then hit vol down to cancel to boot up the phone. Once booted everything is ok, but any reboot just brings that up again. Using ROM manager to flash CWM recovery seems to work ok and it says its installed, but same issue. So does trying to flash TWRP from Goo.
If I were to run this tool that I used to root and loki before (http://forum.xda-developers.com/showthread.php?t=2301720) to install a recovery, would I be able to get everything going again? I think that somehow the recovery I installed wasn't Loki'd, although I picked the right one for my device.
Thank you in advance for any replies.
The fix I found was by pure dumb luck. I ended up trying to flash a recovery with Odin. Odin failed but reboot back into the os. I then used the twrp manager app from the playstore (mainly because goomanager wasn't downloading the recovery at the time) to flash the latest twrp recovery and all was good. Even though Odin failed at flashing the recovery I still think it helped somehow. I haven't thought much about why but I might have to now.
Sent from my SCH-I545 using Tapatalk
You could probably try using ODIN to get back to stock MDK and then Re-Root and install a recovery after.
Edit: And then flash CM11 again.
Sent from my SCH-I545 using Tapatalk
Will this one-click stock ROM work?
http://www.rwilco12.com/downloads.p... S4 (Verizon) (SCH-I545)/Stock ROMs/One-Click
or, which of the files on this page are what I would want? (about 1/3 of the way down for SCH-I545)
http://www.droidviews.com/how-to-install-latest-official-firmware-on-samsung-galaxy-s4-all-models/
I was actually able to reflash TWRP w/ their app from the Play Store. Still get a lot of boot hangs on the Samsung logo though. Seemed to happen less with CWM, but now I'm too scared to try to install a different recovery. I appreciate all your help guys.

[solved]Bricked my tablet? Galaxy tab3v SM T113

What had happened:
I got a free tablet, decided to **** around with it....
so, i decided to use odin to flash TWRP recovery with it..
however.. when i try to get to recovery mode, it only shows a ! mark.
therefore, i tried to flash a rooted system image. it worked.
then, with my newly found rooted device, i tried to fix my recovery by
attempting to use cwm.... i pressed on to "boot to recovery", and now its
stuck on a infinite loop, booting to the ! mark. the only thing i can access is download mode.
so.. how do i fix it? feel free to ask any qns i will try to provide the infomation needed.
thanks.
Well, the problem here seems to be that you messed up with the boot or the system files, maybe your bootloader is blocked so you need root to flash a custom recovery or ROM and to unlock the bootloader, you should first check the CWM supported devices list before actually flashing Clockwork recovery!
Try to flash a full stock rom through fastboot mode.
Sent from my VF-895N using XDA Free mobile app
Well i did what u did and got it fixed.. thanks for your help.. really appreciate it

Categories

Resources