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.
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.
So, as we all must know by now, the Note 4 Retail version got the CID conversion, and now we have access to root.
But I have no such thing, because when I was messing with TWRP I couldn't flash SuperSu or Emotion r21. This resulted in a bootloop, and since I couldn't find a working way to get out of the bootloop, I decided to wipe the phone. The only issue is that I somehow accidently uninstalled android itself, leaving my phone without a system.
And now, I have used some files from http://forum.xda-developers.com/not...mware-firmware-kernel-modem-recovery-t2942937
To be more specific, I tried to flash the "Stock restore" file, as that seemed to be the best option. I got about 98% of the way through it with Odin before I got a write-denied error.
And that's strange because I have my phone in developer mode.
And now, if I plug my phone in, it gives me a screen telling me that I must use the Verizon repair assistant application on my computer, although it doesn't recognize my phone unless its normally booted up.
Hitting the power button brings me to a download mode like screen, with the text in the top left, but a picture in the middle that tells me to use Verizons repair assistant.
The screen says "Software Update Failed ... Your device didn't update successfully. Use the Verizon Software Repair Assistant on a computer to repair your device and complete the update."
Booting into recovery mode doesn't work
Booting into download mode does work, however it doesn't allow me to flash anything through Odin.
I have a Verizon Note 4 N910V Retail (w/ CID change), on 5.1.1 and latest bootloader
EDIT: Also, Odin doesn't recognize when the phone is plugged in, but the pc does. The pc doesn't know what it is though.
Odin has recognized my phone after I left it off over night
Does anybody have any idea on how to fix this? There has to be a way, since its not a bricked phone
Any help is greatly appreciated
Did you try to use verizon repair assistant?
Sent from my SM-N910V using XDA-Developers mobile app
PapaDocta said:
Did you try to use verizon repair assistant?
Click to expand...
Click to collapse
Yes,but it refuses to recognize that my phone is plugged in
UPDATE: I flashed TWRP and i forgot to uncheck auto-boot, but it did get me out of Verizons restrictive boot. Also, Android is now present , just needing repairs
EDIT: Android is starting! Hopefully is someone else does this incredibly stupid and reckless use of TWRP like I did, they'll know how to fix it (to an extent). Sorry if this thread was more of a waste of space since I just fixed it myself (miraculously).
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.
Hi Everyone,
I have a 5T running android 9 - completely stock. The device is SIM free, I have never customised it at all - if anything it's never been connected to a PC even.
A few days ago I was using my phone as normal (on whatsapp) but it completely froze. It now boots up to the "Your device is corrupt and cannot be trusted and may not work properly" - it freezes on start up and won't work at all.
- I can get to the fastboot screen
- I can get to the recovery screen to install from ADB
The fastboot screen says in red - device state - locked.
The device is a clean, un-customised phone. Only a few days prior I checked for any OTA updates but I haven't received android 10 yet.
I haven't flashed phone firmware or anything for years now. (By years, I literally mean years - back in the Nokia 8210 days). My only other experience of flashing firmware was with Samsung phones and 'debranding' them.
As I was not trying to root the device or anything - how do I fix this issue? I've searched the forums but I cannot fine a scenario similar to mine therefore I'm a bit confused as to what to do to resolve it.
I've tried to sideload this - oneplus.com/uk/support/softwareupgrade/details?code=PM1574156155944 via recovery but it says installation failed.
Any help appreciated thanks!
Sounds like you're straight out of luck to recover any data if your device is completely stock, as to unlock your bootloader to access encrypted data would mean a factory reset. You could try try one of the unbrick tools using the guide here. You will lose your data.
I tried the unbrick tool here - forum.xda-developers.com/oneplus-5t/how-to/oneplus-5t-unbricking-tool-confirmation-t3733012
... and it doesn't work. The phone now boots to a blank screen with a constant white LED.
Could this be a hardware issue?
I'm not too concerned about losing my data - already gave up on trying to keep my data when the problem first occurred!
After the 4th use of the unbrick tool (each time it completes successfully) I was finally able to boot into the phone.
I got as far as setting the region but then it wouldn't find any wifi networks. It then completely froze on this screen and is now back to "your device is corrupt and cannot be trusted" and will continually try to boot and freeze on the oneplus logo. Sometimes it will boot to a blank screen with a white LED.
Has anyone else had this issue? I'm definitely suspecting a hardware issue now...
oneplus5t_ said:
After the 4th use of the unbrick tool (each time it completes successfully) I was finally able to boot into the phone.
I got as far as setting the region but then it wouldn't find any wifi networks. It then completely froze on this screen and is now back to "your device is corrupt and cannot be trusted" and will continually try to boot and freeze on the oneplus logo. Sometimes it will boot to a blank screen with a white LED.
Has anyone else had this issue? I'm definitely suspecting a hardware issue now...
Click to expand...
Click to collapse
Problem fixed?
unfortunately not. Any ideas on next steps?
That's an odd issue for sure. My only idea would be installing TWRP and maybe formatting from there and using fix permissions etc. to see if it has any effect.
I've done some googling to try and understand "TWRP" but I'm not sure I fully understand. Are there any forum posts I can refer to?
- phone has been flashed several times
- before this whole saga dev mode was enabled, but only to reduce animation scale - USB debugging was never enabled
- the phone has always been stock / sim free - never rooted
Thanks
Can you get into recovery? If yes then try connecting to a pc whilst in recovery as it should let you open your phones internal storage on PC but im not too sure if stock recovery allows it, (TWRP) does. Then copy whatever files you need. Let us know if you can get into fastboot mode aswell
It sounds similar to an issue I have just experienced with a friends 5T. In my case it's a hardware issue (seems like Wi-Fi has died). Just for kicks try to flash the Android 7 firmware. For some reason it allowed me to boot the phone fine and use it, albeit without any Wi-Fi. I sideloaded OOS 4.7.6 and that seems to be the last version 7. You could also use the older unbrick software. Academic I fear as I think you have a hardware issue.
Hello Samsung Galaxy A70 users!
I come to you with a request for help. Well, a few days ago I got my hands on a Samsung Galaxy A70, which for some time did not want to start the system when trying to boot, but only turned on and off over and over again every 20 seconds. He also often stopped at the Samsung Galaxy A70 logo and did not attempt to boot the system at all. So I figured I'd reinstall the latest software by Odin. The previously described problems still occur after correctly uploading a clean system.
Anyone know what I should do to solve the problem of the phone rebooting itself and its reluctance to boot the system? From myself I will only add that the OEM is blocked, because I have no chance to get into the operating system and to be able to disable this lock.
You can add more information, like the software version you have flashed, which spftware the phone worked previously on, a picture from your bootloader (so we can figure out what may have happened to the phone that made it useless).
Stock recovery logs are useful too, but you gotta read it on your own.