Totally non device related but I'm lost as where to ask this and since this is the m9 is the only thing I own with a decide thread I'm hoping someone here can just point me in the right direction. I own a Verizon ellipsis 7 tablet and as far as I'm aware, an MTK device. I use the MTK tools to create a custom cwm for my tablet which is pretty easy with just about any MTK device. Everything went good but I let my curiosity get the best of me. There is no dev support anywhere for this device so I decided to see if CM12 from a similar device would work and now I'm sitting with a hard brick. The device will not boot past the initial powered by Android boot logo and it just loops. Goes to that screen and sits for 20 seconds and repeats. Now I know all about getting a phone into bootloader mode or download mode yada yada to flash stock firmware but I can't get this thing to boot into anything but the loop. When plugging it in to charge it shoes the off charging icon and then tries to turn on by its self and continues the loop. I've literally tried everything google could possibly turn up and I can't find anything that can get this thing to boot into bootloader mode or even suspend in pre-boot mode (if that's what it's called). If ANYONE may have any advice, even if it's just a better place to post for help, I'd really really appreciate it.
Related
All,
I have used my GS3 for awhile now without issue. I'm abroad for the forseeable future, so I've only been using it for Wi-Fi calling and internet/apps. Regardless, Kies NEVER worked for me, and my computer never recognized the USB device. Up until recently, I've just used my iPod for music, so no problem.
Fast forward and my friend, who also has a GS3, tried to update my drivers and root/flash my phone so I can drag and drop files the way he does with his. I let him do this because I'm newb to this, and because he assured me he knew what he was doing as he'd done it to his and his girlfriend's phone.
As it turns out, he has an international version (he used ToolKit instead of QCom ToolKit) and he tried to root the wrong files to my phone. At first, I thought it was hard-bricked (which really puts me in a tough position since I won't be back in the States until January), but I don't think even his root attempt worked properly.
So where I'm at now:
The phone will not boot up. When I turn it on I get the Samsung Galaxy S III logo, but android never loads. The phone will charge via USB and the wall.
I can access recovery bootup
I can access download bootup (the ability to do the two above lead me to believe it isn't hardbricked, I read on these forums, if I can get to download bootup then it's probably fix-able)
I've combed the forums and the internet, in general, for a fix. I downloaded the factory restore settings from samsung-updates (sorry if I cannot plug this site, it's not intentional, simply to provide as much info as possible), but Odin always "FAIL"s when I attempt to apply it.
Additionally, I've attempted to recover via recovery bootup/reset, and then load the factory restore setting via Odin. This did load them, but the phone did not boot up.
QM ToolKit was acknowledging the phone, so I attempted to boot the correct files using ToolKit (the ALLINONE option) and this worked correctly, as expected via QM ToolKit. But still the phone would not boot up.
The phone sits at a black screen after the GSIII logo with the blue LED lit up.
Any tips or advice would be appreciated. I'm in quite a situation.
sadly i have the same problem, this happened randomly and cant get my device to boot
If you Odin tmo stock image tar and odin recognized your device and all went well then boot into stock recovery factory reset then reboot. It should boot up if all is well. When you plug to pc does your computer recognizes it?
Sent from my SGH-T999 using xda app-developers app
Provided your boot loader and download manager partitions are working(as it appears to be the case) you can get your phone back to a "working" state.
What I suspect happened is that at some point during the process of playing with it, your partition table got hosed and now android is borked. I would recommend re-partitioning it but I don't have enough info around me and available to give you instructions to do so. I'll do some digging and try to get back to you.
I had or have (yet to be decided) a sprint galaxy s6. It was rooted with a twrp recovery. The last action I took before I had a problem was re-download the stock antivirus Lookout. After it installed i ran it and lookout instructed me to switch off my unlock oem and unknown sources and I think the develop settings all together. After doing that I restarted my phone. Here is where my problem separates from the others and becomes quite a bit different... The Phone will boot up to the Samsung powered by Android screen then the red letter frp lock comes up and it shuts off and continues on the boot loop. It will not boot up into recovery when it is attempted it acts in the same manner as just turning it on. Normally not a giant issue because the phone DOES boot up into download mode. But the hits keep coming. No computer I have attempted to connect it to will read my phone. I've installed every Samsung driver i can think of but i will re investigate if i had a clue which ones are necessary. Currently it will say USB device not recognized and and the driver reads unknown device. So if anyone knows how to fix it please any suggestion or ideas will b tried.
i tried to install lineageos on my asus zenfone 2 ze551ml. I must confess that I really messed things up because i didnt put lineage os on it before wiping.... anyways, I cant access the bootloader, but my phone does turn on and show the asus logo and that powered by android thing, in white tho, which is since I activated bootloader. Since the Screen turns on it doesnt seem to fit the definition of hardbricked, but I cant access bootloader either so it doesnt seem to be softbricked. What can/should i do now? When holding Power and volume up it just vibrates and does nothing, but when i just press power it gets stuck in the booting screen, i can turn it off though. I dont want to make things worse since everyone seems to warn me of using hardunbrick methods when the screen still does turn on... I own the zenfone 2 ze551ml, it wasnt rooted and i recently downgraded to lollipop since otherwise i couldnt have used asus' bootloaderunlock tool.
EDIT: I now have followed some tutorials, I have used the xfstk tool and i got to the point where I can choose between normal boot, power off, recovery, and reboot to recovery. I can also detect it via cmd and fastboot devices. Now unfortunately I can't flash a ROM with the Asus flash tool because "Error #1" and I cant put anything on it in general. I've come to the point where I just decided that i will take the next opportunity that will make this stupid thing work again and that my next phone will just be a oneplus because of the far better support from customroms etc. Anyways, does anyone have a clue how to fix it? if it runs lineageos afterward or the stock rom doesnt matter anymore, but it should work afterwards. Thanks! (in cmd, when im trying to flash something it would just say (command write failed (no error)))
So my phone has been this way since Nov 2017, there are files that I need access to and would truly appreciate some guidance
I was experiencing issues with the bluetooth on nextbit previously so I installed a new rom after flashing the device. Once the rom also gave issues I decided to revert back to the Nextbit 7 OS and one fine day when the phone restarted it wouldnt go past the "nextbit" splash screen. Tried installing the OS again however the PC wouldnt recognize the phone anymore, switched laptop to a Mac and got the same issue
Any help would be greatly appreciated
It wont let me post a URL link. I have taken www out hopefully it allows to view the video, shows exactly whats wrong
youtube.com/watch?v=ImIk5CErWf0
It looks there's something wrong with the system boot, since it's reaching the blue boot-animation and it stays there (probably before loading the adb stuff). Fortunately u did unlock the bootloader and that annoying initial screen may be helpful this time, did u try to reach recovery or fastboot mode from there (pressing some volume key)? It's pretty hard for it to be broken there too and in such a case I would think about some hardware fault. Anyway from the recovery (I hope u have TWRP, if not install it with fastboot) you should be able to do whatever u want, including recovering your files or (re)installing a rom
Hello, im a noob here, tho i've crawled my share. To keep this short, i had lineageos 16 running on my OnePlus 5t, and decided to change it up to another os based on Android 10. Maybe i deleted a partition i shouldnt have or something, because i installed the os, but when i boot it i get the "hello" screen, i press that and get a white screen with a swirling "just a minute" that is infinite.
The worst part is that for whatever reason. i can no longer boot into recovery or fastboot modes! so i can't seem to do anything about my situation with my own skill set. I'm hoping someone in the community can help. can i boot the phone from an otg cable and install twrp? i just don't know what to do. Thanks
Re-flash Stock ROM by means of QFIL ( read: Qulacomm Flash Image Loader ).
QUOTE=jwoegerbauer;83396525]Re-flash Stock ROM by means of QFIL ( read: Qulacomm Flash Image Loader ).[/QUOTE]
I'll def look into it, read about it. So it has the ability to flash the phone even without recovery or fastboot mode? download mode and edl mode dont seem to work either. i can pretty much just get 2 screens into the initial first time load, every times since it never moves past that point, just a white screen "just a sec" lmao, and a swirling circle. thats about all i can do that i'm aware of at this point. i tried the unbricking tool, but the phone never shows up properly in device mode, so that i can update drivers and continue that line of directions.
i'm gonna be so upset if im like the only person around who was able to brick his oneplus so that it can never be fixed...