Related
As I said, the phone is not currently bricked. I can do a normal boot into the OS and Download Mode, however recovery is a different story.
I believe the issue stems from the latest OTA update to version VS98026A. I had a custom ROM on here before, but the developer stopped support so I went back to stock doing a complete wipe through TWRP, including both caches, system, data, and internal storage. I then flashed the stock Verizon ROM for version 24A, rooted, temp unrooted to take the OTA for VoLTE, restored root, and installed TWRP. I have been unable to boot into recovery AT ALL. I have tried through the TWRP manager app and ADB. Both times I was simply presented with a fastboot screen stating processing commands eternally, I let it sit there for a good 10 minutes to be sure. I also tried different versions of TWRP, but they all either failed entirely and just rebooted normally or gave me fastboot.
I have access to ADB terminal on my PC, the TWRP manager app, fastboot (I know, not ideal), and download mode. I can flash most parts of the system through ADB, with a little help. I have the basics down.
I've got backups of everything from when I had TWRP on here before, even my EFS. Any suggestions, no matter how drastic, are welcome.
UPDATE: I've used fastboot to replace my boot, aboot, laf, and recovery partitions. Now when I enter recovery, I'm presented with the android with the red exclamation triangle, but no recovery options.
Just to try it I put TWRP back on and I still get fastboot.
Starcruiser322 said:
As I said, the phone is not currently bricked. I can do a normal boot into the OS and Download Mode, however recovery is a different story.
I believe the issue stems from the latest OTA update to version VS98026A. I had a custom ROM on here before, but the developer stopped support so I went back to stock doing a complete wipe through TWRP, including both caches, system, data, and internal storage. I then flashed the stock Verizon ROM for version 24A, rooted, temp unrooted to take the OTA for VoLTE, restored root, and installed TWRP. I have been unable to boot into recovery AT ALL. I have tried through the TWRP manager app and ADB. Both times I was simply presented with a fastboot screen stating processing commands eternally, I let it sit there for a good 10 minutes to be sure. I also tried different versions of TWRP, but they all either failed entirely and just rebooted normally or gave me fastboot.
I have access to ADB terminal on my PC, the TWRP manager app, fastboot (I know, not ideal), and download mode. I can flash most parts of the system through ADB, with a little help. I have the basics down.
I've got backups of everything from when I had TWRP on here before, even my EFS. Any suggestions, no matter how drastic, are welcome.
UPDATE: I've used fastboot to replace my boot, aboot, laf, and recovery partitions. Now when I enter recovery, I'm presented with the android with the red exclamation triangle, but no recovery options.
Just to try it I put TWRP back on and I still get fastboot.
Click to expand...
Click to collapse
Was there ever a resolution to this?
I believe I might be having the same issue.
Sent from my LG-VS980
Well, it was sort of resolved for me. If you follow the steps in THIS THREAD, you better hope you have enough battery to last through the process. If you do, great, you'll have your phone back in running order soon enough. A bit of Linux experience helps with this.
After my battery died it refused to come back on, and I brought it to the Verizon store and told them I woke up one day and it wouldn't turn on.
They replaced it under warranty.
I assume other major carriers would do the same.
Is your phone still under warranty? What model and carrier?
After a bit of searching, I did confirm that the 26A update locks the bootloader and implements tighter security policies.
My S6 edge is in a bootloop. I put off the 5.1.1 OTA for a while when my wifi would not turn on. Rebooted, still didnt work. I decided to do the update. installation went great but now its in a boot loop. I flashed the firmware (BOG7) using Odin. It worked. The phone was back on again but then it shut off after a few hours.
Its been stuck in the bootloop again. I flashed BOG7 again. Ive Flashed BOG9. Ive flashed the stock PIT. Ive tried ADB sideload. Smartswitch and Kies do not recognize the device. Of course, Ive wiped cache and factory reset. Attempted booting in safemode. All flashes were successful but when it reboots, It says "erasing" and goes to bootloop (Samsung powered by android).... Drivers are installed and working. MTP is not installed and I cant find the file.
Please .
same problem
I'm having the same problem with boot loop on g925v stock. I'm wondering if the op or anyone else can help!
No mater what I do, phone reboots after almost exactly 1min9 sec. Just enough time to select a language, but not get past the next "activation" screen.
Background: Phone has never been rooted, at first was on og5 and started freezing on the verizon logo, so I factory data reset, and after that nothing has really changed. knox has not been tripped, frp not tripped
First I tried flashing og5 with odin,
(of course checked md5, and odin=pass, then after flashing, I always tried several combinations of booting to recovery for wipe cache partition/ factory reset / and also power down by holding volume down and power button, then select boot in safe mode)
Then tried flashing og7, still boot loop
then tried flashing og9, 3 times, again, also many attempts of factory data reset/ wipe cache partition / safe mode.
I am starting to think this may be a hardware problem, BUT unfortunately I do not have samsung warranty available on this phone so I am pretty much stuck messing with it.
In researching the issue, I have run across quite a few similar freeze/boot loop problems all over the web, and never any real solutions, for both g925v, g920v, and other s6 models. I've also seen a stock s6 g920v that freezes randomly, flashing stock og9 never helped, owner was planning to replace the battery and see if that helps (I have not heard back).
I've tried looking at the boot log but I'm no expert. I know I can't downgrade, but I'm wondering if there is anything I can do with adb, or any other bootloaders that I could try flashing over the og9 (even if just temporarily, assuming I will flash stock og9 again after).
Thanks for any encouragement, help or advice.
I finally gave up on my GS6 Edge because upon carefully taking it apart for the 3rd time I noticed physical damage up by the wifi receiver and SIM card slot. My advice would be to try the things I tried (above) and, if it's not a hardware issue, it may fix the problem. Good luck.
beefriendly said:
I'm having the same problem with boot loop on g925v stock. I'm wondering if the op or anyone else can help!
No mater what I do, phone reboots after almost exactly 1min9 sec. Just enough time to select a language, but not get past the next "activation" screen.
Background: Phone has never been rooted, at first was on og5 and started freezing on the verizon logo, so I factory data reset, and after that nothing has really changed. knox has not been tripped, frp not tripped
First I tried flashing og5 with odin,
(of course checked md5, and odin=pass, then after flashing, I always tried several combinations of booting to recovery for wipe cache partition/ factory reset / and also power down by holding volume down and power button, then select boot in safe mode)
Then tried flashing og7, still boot loop
then tried flashing og9, 3 times, again, also many attempts of factory data reset/ wipe cache partition / safe mode.
I am starting to think this may be a hardware problem, BUT unfortunately I do not have samsung warranty available on this phone so I am pretty much stuck messing with it.
In researching the issue, I have run across quite a few similar freeze/boot loop problems all over the web, and never any real solutions, for both g925v, g920v, and other s6 models. I've also seen a stock s6 g920v that freezes randomly, flashing stock og9 never helped, owner was planning to replace the battery and see if that helps (I have not heard back).
I've tried looking at the boot log but I'm no expert. I know I can't downgrade, but I'm wondering if there is anything I can do with adb, or any other bootloaders that I could try flashing over the og9 (even if just temporarily, assuming I will flash stock og9 again after).
Thanks for any encouragement, help or advice.
Click to expand...
Click to collapse
Hello XDA,
I'm not sure if this is the right spot to ask about this, lemme know if it is.
Right, time to get to the problem I'm facing.
I've got an Asus ZC500TG in this year's August, rooted it the same month, and everything was working fine until last night.
After doing a basic procedure of using TWRP 2.8.7.0 to flash Infinix Hot 2 AOSP port(was working for me many times), the device decided to just boot into recovery even though i pick 'boot to system'.
The bad news don't stop there either. When I plug my phone with USB while it's powered off, instead of going into the ROM part that shows the battery symbol and charges... it goes back into recovery instead?
Also, doing the keystroke(holding power+volume up), instead of going into bootloader mode(the thing that lets you pick between recovery, fastboot and normal boot), it also boots to recovery instead.
If i boot to fastboot through TWRP, it boots into fastboot fine, but that's pretty much it. Fastboot and recovery modes is the only thing I can access.
Even though I was with the rooting community ever since I've had my first smartphone in 2012, I've never experienced such an issue where the only thing bootable is either Recovery or Fastboot using the said recovery.
Here's what I've tried so far:
-Wiping cache/dalvik cache/system/data;
-flashing a known working stock ROM;
-Trying to sideload it using TWRP's ADB sideload, seemed to check out and came back to same issue;
-Trying to flash/sideload custom ROMs I know should function properly, same issue occured;
-Flashing stock recovery back and attempt to flash stock ROM, also failed;
-tried to wipe /system, /data, /cache and /dalvik-cache using fastboot, then flashing ROM using recovery, also failed;
-looking up anything that's related to it, mostly fraud websites and/or Russian websites suggesting to do what I did already.
Has anyone ever encountered this, and is there a possible fix to this?
Thanks in advance to all your answers.
-MrRubikon
Help me zenfone go zc500tg zoovd my phone is wrong root then total dead can not live
antho111 said:
Help me zenfone go zc500tg zoovd my phone is wrong root then total dead can not live
Click to expand...
Click to collapse
I have some problem,,
,,somebody can give solution pleace,,!?
I do apologise if I give too much information; I try to be thorough in documenting my methods and include as much information as possible so we can maybe skip some of the "what does it do when you ..." and the "did you try this" questions.
So I have been reading through these forums for the past few hours... Earlier today a friend gave me her AT&T Galaxy S5 to try and fix. When I received it, it would boot straight into recovery. She was on version G900AUCS4DQD1. I can say for nearly 100% certain that this lady knows nothing about modding her devices, so I am absolutely confident that this problem doesn't stem from her attempting to root the 6.0.1 firmware she was on, install custom recovery, or anything anywhere close to that. She said she had taken it to an AT&T Store and they were unable to fix the device; although I'm sure all they did was do a factory reset through recovery and when that didn't work they just said "Well, it's broke, come buy a new device." Either way, the information in bootloader mode doesn't show anything outside of what it's supposed to ... Current Binary is Samsung Official, System Status is Official, Reactivation Lock is off, and most importantly the KNOX Warranty Void flag is showing 0x0.
As I said, when I got it, the phone would boot straight to recovery by only person the power button to turn it on; but download mode was accessible via the option in recovery and by holding Vol-Down + Home during boot. Attempting to boot into safe mode, holding Vol-Down during boot results in nothing different than if I don't hold Vol-Down... sometimes it boots all the way to system where it reboots on Optimizing Apps, and sometimes it doesn't even clear the colorful animated Samsung Boot logo. While in recovery, the device is not visible in Windows Explorer. If I open my command line and type "adb devices" the S5 doesn't how up. However, if I select "Apply update from ADB", THEN type adb devices, it shows up as <device serial #> sideload. Attempting to issue the command "adb shell" while visible to adb results in "error: closed" being returned. Now, because I've been using the OnePlus 3T I have become somewhat familiar with bootloader mode and the fastboot command, and I don't know if Samsung devices are SUPPOSED to respond to the command "fastboot devices" while in bootloader/download mode, but I can say for 100% certain this one doesn't.
Remembering everything I learned when I owned the S4 AND after doing research on what firmware versions I could safely flash if my device was on 6.0.1, the first thing I went searching for was Odin and the factory firmware. I used the thread "G900AUCS4DQD1 ** FULL ODIN UPDATE ** v6.0.1 by toutanje to find the firmwares to download. I have also used the method and files in the thread "[Unbrick] Fix All For Samsung S5 AT&T (SM-G900A) Lollipop 5.1.1 by Birkyjon. Whichever method I use, all the files load and flash without incident in Odin. Before I attempt to boot to system, I boot into recovery and wipe cache and do a factory reset. (I have attempted do boot both with and without a factory reset after flashing the firmware in Odin) After doing that, obviously I hit reboot now... the phone passes the initial Galaxy S5 Logo, it goes to the multicolored Samsung Logo, then the AT&T screen, and SOMETIMES it boots into system, where it sits at the "Optimizing Apps, x out of 210." It will count up to around 30-40 or so, then reboot. After that initial boot where it gets to Optimizing Apps, all boots after that are unpredictable... as in, maybe it will make it back to Optimizing Apps, maybe it won't even make it to the AT&T boot screen before it restarts itself. Once it does that, I can boot back to recovery, do another factory reset, and it will make it to Optimizing Apps again every time. About the only thing I haven't tried was to attempt to flash the firmware via the "Apply update from ADB" option, though I honest don't see the point after everything else which has failed.
One last thing I have seen in my research so far but am unable to test: could these issues be caused by a bad battery? Being that I have no idea how the battery life on this particular device has been, I have no reference as to whether it has been draining incredibly fast, acting normal, or even just flat out dropping massive amounts or so at once.. I seem to remember noticing when I placed it on charge this afternoon, the device only had around 6%, and while connected to only a 1A charging brick, the percentage had magically jumped from 6% to upwards of 35% in what seemed like 3-4 minutes. I can't confirm for certain how long it was charging as I was also wrangling my two toddlers at the time and could have possibly just lost track of how much time had actually gone by...
Any ideas as to the issue I am facing? Any help would be much appreciated! Thanks guys!
I have this exact game problem with my wife's s5. I never got any type of response, I hope you do. I'm still having this problem as well.
A unique thing I've experienced with the bramble is that any soft reboot will soft brick the phone. Flashing the same factory image (with -w removed) doesn't seem to fix it.
I had a method of fixing it that worked 100% of the time. I'd flash a factory image from the same month, but for a different carrier. Boot up normally, then flash back to my carrier, root, etc.
It appears this method doesn't work anymore since there is only one factory image for May.
I got a random soft reboot today and now I can't get back. I've used ADB to disable magisk, though it shouldn't matter since I've just been flashing stock factory images that are not rooted so should not enable magisk anyway.
what i'm seeing is the phone will boot up and immediately say "powering off"
I've also tried flashing the April image and both versions of the March image. I've tried sideloading OTA to May. Nothing seems to work.