So I started having trouble after flashing a rom. The old infinite htc boot logo. The troubling part was when I tried to reboot to recovery and TWRP blackscreened and device turned off.
I tried re-flashing recovery.img with identical results.
Now my phone locked while attempting a fastboot flash boot.img with a known working boot.img just in case the rom I flashed had a corrupt boot image.
I left the cmd window open and its been "sending boot.img" for about forty-five minutes now. I am terrified to ctrl+c the command or restart my device.
So boned or no boned?
On a scale of one to boned how boned where do I fall on the bonage spectrum?
Any ideas on what to do next, or if rebooting to fastboot is safe?
You have to wait the final of the sending.
Probably your USB cable is *****d up, and i'm advising you because i had the same issue.
A flash of a boot.img was of 15 mins.
Tried fastboot erase cache to get back into twrp?
----------------------o('_')o----------------------
Sent from an HTC One with using xda app:
TrickDroid ROM 9.1.0
Bulletproof 4.3
Afraid to stop the current fastboot operation to try to clear cache. Tried running from another window and it just sits there, cursor blinking, like its waiting for the other operation to complete.
Waiting for it to complete seems fruitless as its been almost two hours now for a 5836kb flash.
-update-
Okay so I took a couple valium and quickly switched out the usb cable. The cmd window running the flash operation crashed, but fastboot on the device became responsive again. I feel like this is a fact that might be useful to others in the future.
Fastboot stalls out--don't panic, just disconnect the usb cable...
I'm still scared to reboot it, even to reboot to fastboot. Is fastboot part of boot.img? If this botched op boned up my boot.img is it possible that fastboot might not work after a reset?
Gonna give cache erase a shot and report results.
Cache erase worked fine.
Is there anything else I can do to minimize risk before rebooting to recovery? Anything important that -needs- to be done?
hypocritelecteur said:
Cache erase worked fine.
Is there anything else I can do to minimize risk before rebooting to recovery? Anything important that -needs- to be done?
Click to expand...
Click to collapse
After the cache's erase you can boot in recovery.
Guich said:
After the cache's erase you can boot in recovery.
Click to expand...
Click to collapse
Phone still reboots right after TWRP logo is displayed!
hypocritelecteur said:
Phone still reboots right after TWRP logo is displayed!
Click to expand...
Click to collapse
So, reflash the latest TWRP (2.0.6.1), do an erase cache and retry.
Yeah, I tried that before posting but for sake of thoroughness I did it again.
erased cache
reflashed m7 twrp
erased cache
Going to try CWM now.
Really appreciate the guidance and support in a problem you have no personal stake in. Being on the receiving end of the goodwill of strangers makes me all warm and tingly.
Also switched USB cables and did a fastboot reboot to make sure commands were being passed on... nothing wrong on that front.
Guich said:
So, reflash the latest TWRP (2.0.6.1), do an erase cache and retry.
Click to expand...
Click to collapse
Aaaand CWM worked for whatever reason.
Odd, since I've never had a problem with TWRP before but plenty with CWM... Every duck has its day I guess.
---
Well... CWM loads properly but executing any command that touches phone data causes a reboot.
Factory reset -> reboot
Install zip from sdcard -> reboot
Trying sideload next... it goes into sideload mode fine. I'm guessing that as soon as it tries to write something it will reboot, but I'll have to wait till I've re-downloaded and double checked md5s like a paranoid bastard first.
adb sideload ohdeargod.zip
---
Hmm, wiping cache partition alone works.
--
Noticed that on booting into CWM it displays the message:
Warning: No file contexts.
--
formating /system alone works
formatting dalvik causes reboot
formatting data causes reboot
--
sideload seems to have worked although its taking a long time to boot. I'll give it another 15 minutes.
Which firmware are you running?
Guich said:
So, reflash the latest TWRP (2.0.6.1), do an erase cache and retry.
Click to expand...
Click to collapse
Guich said:
Which firmware are you running?
Click to expand...
Click to collapse
Aaaand bingo gringo. It's booted.
Its a tmo m7. I haven't touched firmware afaik.
Resolved just in time for me to take it sailing today and drop it into lake Huron.
hypocritelecteur said:
[snip]....drop it into lake Huron.
Click to expand...
Click to collapse
Say whhhhhhhaaaaattttt?
Sent from my Nexus 10 using Tapatalk 4
altimax98 said:
Say whhhhhhhaaaaattttt?
Sent from my Nexus 10 using Tapatalk 4
Click to expand...
Click to collapse
Okay so I have a brand new HTC TMO One I got last week and its waterlogged. I drilled a hole in the back of the case to drain it and then left it on the radiator to make sure all that moisture is gone. I can't get it to post to TWRP.
Please help.
Deciding after recent events that XDA can be a dangerous place for sarcasm. So--thanks all, problem solved, no, no phone was damaged during the making of this thread. It was just my business partner, Lloyd, who fell in and became waterlogged. No amount of drilling or radiator baking could revive him.
Please help.
Related
Was installing android revolution 10.0 and when it finished it wen't back to CWM. It said something about maybe loosing root and I accidentally backed out and it tried rebooting. Now its stuck in some sort of bootloop and it tries to boot into ROM but it turns off and then trys to boot reecovery. the screen flashes CWM for a second but then it turns off again and trys to boot. I can get to Hboot and selecting recovery there makes the same thing happen.
xXxG0dzRAgexXx said:
Was installing android revolution 10.0 and when it finished it wen't back to CWM. It said something about maybe loosing root and I accidentally backed out and it tried rebooting. Now its stuck in some sort of bootloop and it tries to boot into ROM but it turns off and then trys to boot reecovery. the screen flashes CWM for a second but then it turns off again and trys to boot. I can get to Hboot and selecting recovery there makes the same thing happen.
Click to expand...
Click to collapse
Can you format data?
fastboot erace cache
skinsfanbdh said:
fastboot erace cache
Click to expand...
Click to collapse
This worked. Should I try flashing ARHD again? its the only ROM on my SD card. Or should I be able to boot in to my current ARHD ROM that I tried installing before this happened?
Also at the bottom of CWM i get can't mount /cache/recovery/command and a few other can't mount log and can't open logo. before your solution I reflashed CWM using fastboot. Don't know if thoes things will cause an issue
xXxG0dzRAgexXx said:
This worked. Should I try flashing ARHD again? its the only ROM on my SD card. Or should I be able to boot in to my current ARHD ROM that I tried installing before this happened?
Click to expand...
Click to collapse
im running ARHD 10 now i would try to reflash or maybe you got a bad download
---------- Post added at 11:20 PM ---------- Previous post was at 11:20 PM ----------
oh and its running absolutely perfect btw
skinsfanbdh said:
im running ARHD 10 now i would try to reflash or maybe you got a bad download
---------- Post added at 11:20 PM ---------- Previous post was at 11:20 PM ----------
oh and its running absolutely perfect btw
Click to expand...
Click to collapse
I was on trickdroid before. I think it had to do with me rebooting and not selecting the fix root option.
reflashed and aroma got stuckk after installing. just did adb reboot and seeing whats happening next. wish me luck. :x
Let your phone cool down before trying aroma again but mine froze at 100% twice. First time got stuck at boot animation. second time it booted but it stayed at boot animation for a while
Sent from my HTC One using xda premium
skinsfanbdh said:
Let your phone cool down before trying aroma again but mine froze at 100% twice. First time got stuck at boot animation. second time it booted but it stayed at boot animation for a while
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
Well I flashed it and it got stuck at boot animation for about 20 minutes. Flashed it once more and it did what it did the first time. I noticed that aroma completely crashes before finishing and thats how it all started the first time. It goes back to recovery. So just flashed it again right now and got it to completely go through. Back to HTC One screen though. Gonna see if it boots or not.
Still at boot screen for a long time. :x
skinsfanbdh said:
fastboot erace cache
Click to expand...
Click to collapse
Hi guys, I'm pretty new to this. Can some one explain how to erase cache?
xXxG0dzRAgexXx said:
Well I flashed it and it got stuck at boot animation for about 20 minutes. Flashed it once more and it did what it did the first time. I noticed that aroma completely crashes before finishing and thats how it all started the first time. It goes back to recovery. So just flashed it again right now and got it to completely go through. Back to HTC One screen though. Gonna see if it boots or not.
Still at boot screen for a long time. :x
Click to expand...
Click to collapse
the first boot is slow ..not 20 min though, more like 3-5 min
emil.kako said:
Hi guys, I'm pretty new to this. Can some one explain how to erase cache?
Click to expand...
Click to collapse
You remember how you had to do fastboot to unlock bootloader? go to that folder where you have your adb files and what not, then you need to Shift + right click while in the white space of that folder and click "open command window here." With your device connected in the command window just type "fastboot erase cache" and that'll work.
If you never had to unlock bootloader you probably had to do this already to install a recovery.
BTW Still stuck at HTC One screen. Might try flashing trickdroid 5.6 from my computer if thats possible... And as a last resort wipe data and install if that doesn't work.
xXxG0dzRAgexXx said:
You remember how you had to do fastboot to unlock bootloader? go to that folder where you have your adb files and what not, then you need to Shift + right click while in the white space of that folder and click "open command window here." With your device connected in the command window just type "fastboot erase cache" and that'll work.
If you never had to unlock bootloader you probably had to do this already to install a recovery.
BTW Still stuck at HTC One screen. Might try flashing trickdroid 5.6 from my computer if thats possible... And as a last resort wipe data and install if that doesn't work.
Click to expand...
Click to collapse
Does anyone know how i'd be able to do this using a mac?
edit: Nvm, i got it. Trying to reflash the rom now. Thanks for the help!
Just decided to wipe SD card and try ARHD again. Man I should have never tried to flash a 4.2.2 ROM yet.
No idea how to do it on Mac. Look up how to use fastboot on Mac
I got it to install correctly after erasing the cache. The first reboot took like 3-4 mins but it finally went through and it's working perfect now. Not sure what happened the first time
emil.kako said:
I got it to install correctly after erasing the cache. The first reboot took like 3-4 mins but it finally went through and it's working perfect now. Not sure what happened the first time
Click to expand...
Click to collapse
Lucky you. Im still trying to get this to work. I stay on boot screen for 20 minutes and for the 10th time im trying to flash ARHD but it keeps getting stuck. This is ridiculous.
finally I got it to boot up. Had to wipe my phone though for it to work. Lost a lot of stuff. :/
I attempted to OTA update my stock Nexus 6 to 5.1 last night, setting it aside to do its thing and went to bed. When I turned the phone on this morning it went into the boot animation which just goes on indefinitely. I have attempted to clear the cache which did nothing. I was wondering if there is a work around without having to wipe the phone and thus lose all my data.
I have seen the first boot take up to 20 minutes you didn't turn off before then did you?
Sent from my Google N6 on VZ
No I left it in my pocket on my commute to work and tried to restart the phone over 2 hours later
Andrew_3 said:
No I left it in my pocket on my commute to work and tried to restart the phone over 2 hours later
Click to expand...
Click to collapse
Leave it booting for over 20 minutes. If it isnt booting after that, it isnt going to.
The next option is using fastboot to wipe the phone.
fastboot erase cache
fasboot erase userdata
Agreed 20 minutes is probably too long but I wanted to understand how long he was waiting. I know I get crazy impatient
Sent from my Google N6 on VZ
So left it over 20 mins and it did nothing. I have installed the 15 seconds ADB installer with all the drivers. Fastboot can recognise the device but the code >adb devices can't find anything! I even plugged in my Nexus 9 which works just fine with no result.
If during the upgrading process you used the command "fastboot erase cache" and received the message "did you mean format?" or something like that, then you need toflash the cache.img.
"fastboot flash cache chache.img"
I was stuck in a infinite boot animation at one point also. Did the above, and the phone booted in 15 seconds.
Andrew_3 said:
So left it over 20 mins and it did nothing. I have installed the 15 seconds ADB installer with all the drivers. Fastboot can recognise the device but the code >adb devices can't find anything! I even plugged in my Nexus 9 which works just fine with no result.
Click to expand...
Click to collapse
adb devices won't find fastboot devices. Adb works only in android or recovery. Fastboot only works in bootloader.
I didn't do the upgrade myself it was OTA!
Won't re flashing the image wipe the phone though?
Andrew_3 said:
I didn't do the upgrade myself it was OTA!
Won't re flashing the image wipe the phone though?
Click to expand...
Click to collapse
Yes, it will, but at this point, you either have a phone that won't boot, or the possibility of a phone that will afterwards, which one do you want?
I'd flash the image and see what you get. It's a small tradeoff at the moment.
Oh, and RootSU, like the new avatar!
My friend got the exact same problem - tried the OTA update, and after that the phone is stuck at the boot animation. I tried to clear cache/factory reset, and once it even booted up, but after showing the android logo it displayed something like "services stopped" (it was too fast to read carefully) and it powered down. And now no matter what I do, it stays on the boot animation. Is there anything I can do about it without my friend loosing his warranty?
PS. And when I tried the "fastboot erase cache" it displayed the "did you mean format?". Where can I find the "cache.img" to flash - and will it void the warranty?
Edit: Ok - I have flashed the Cache.img - now the phone boots quite fast, but immediately after the "android" logo I get "exchange services stopped", and "Print spooler stopped" with an "ok" that I can't click :/
Edit2: If I would have to flash the whole rom, which one should I choose? LMY47 - D, E, I ?
Edit 3: I have flashed the "I" version, and my friends phone works again
Hey everyone,
I've rooted my Nexus 6 device and tried to modify some of the partitions on the device (logo, aboot, boot).
The device has gone bricked but as that's not the first time it is done I guessed it's a soft brick and can easily be fixed downloading a factory ROM for the Nexus.
I did that, and both Marshmallow and Lollipop were stuck on boot (the colored circles which eventually form the "Android" title).
I also tried custom ROMs, but nothing helped (got to the same point were the colored circles jump infinitely).
I tried to flash the ROM both via fastboot and via the recovery menu.
The bootloader is accessible and unlocked. However, it still doesn't work.
Before I rush to JTAG experiments, does anyone have any idea how to solve this? (or at least, some ideas which aren't mentioned above).
Needless to say, I was wiping the cache everytime I flashed the ROMs.
Sincerely,
Adam.
doadam said:
Hey everyone,
I've rooted my Nexus 6 device and tried to modify some of the partitions on the device (logo, aboot, boot).
The device has gone bricked but as that's not the first time it is done I guessed it's a soft brick and can easily be fixed downloading a factory ROM for the Nexus.
I did that, and both Marshmallow and Lollipop were stuck on boot (the colored circles which eventually form the "Android" title).
I also tried custom ROMs, but nothing helped (got to the same point were the colored circles jump infinitely).
I tried to flash the ROM both via fastboot and via the recovery menu.
The bootloader is accessible and unlocked. However, it still doesn't work.
Before I rush to JTAG experiments, does anyone have any idea how to solve this? (or at least, some ideas which aren't mentioned above).
Needless to say, I was wiping the cache everytime I flashed the ROMs.
Sincerely,
Adam.
Click to expand...
Click to collapse
Did you also first reflash the bootloader when flashing stock firmware? Also fastboot ersae system and fastboot format cache before flashing anything.
gee2012 said:
Did you also first reflash the bootloader when flashing stock firmware? Also fastboot ersae system and fastboot format cache before flashing anything.
Click to expand...
Click to collapse
Yes, I also reflashed the bootloader. The room itself comes with a "flash-all.sh" script which did not work as well.
I also tried to fastboo erase system and fastboot format cache (both with the recovery feature and the fastboot feature) but it did not work....
Same outcome - waiting on the colored circles.
doadam said:
Yes, I also reflashed the bootloader. The room itself comes with a "flash-all.sh" script which did not work as well.
I also tried to fastboo erase system and fastboot format cache (both with the recovery feature and the fastboot feature) but it did not work....
Same outcome - waiting on the colored circles.
Click to expand...
Click to collapse
Did you flash the following img`s manualy in fastboot:
system
userdata
boot
recovery
cache
Flash-all.batt isn`t working for a longer time now allready.
gee2012 said:
Did you flash the following img`s manualy in fastboot:
system
userdata
boot
recovery
cache
Flash-all.batt isn`t working for a longer time now allready.
Click to expand...
Click to collapse
Just tried this order. I've been waiting up for 40+ minutes for the phone to boot, however it still loops on these circles.
If it matters - I just tried the 6.0.1 ROM (I've been working on 6.0.0 previously).
doadam said:
Just tried this order. I've been waiting up for 40+ minutes for the phone to boot, however it still loops on these circles.
If it matters - I just tried the 6.0.1 ROM (I've been working on 6.0.0 previously).
Click to expand...
Click to collapse
Your best bet is to run a logcat as it is booting to see where it is hanging. Your issue was messing with the partitions. Not a wise thing to do.
zelendel said:
Your best bet is to run a logcat as it is booting to see where it is hanging. Your issue was messing with the partitions. Not a wise thing to do.
Click to expand...
Click to collapse
Already thought about that - however adb keeps waiting for a device and shows nothing...
Code:
*adamdo**~**shamu-mmb29k**adb logcat
- waiting for device -
So, I followed this thread, used unsu, and things just as described in there:
https://forum.xda-developers.com/apps/magisk/switching-supersu-to-magisksu-t3625579
The thing is, I flashed LineageOS's boot.img which I had, though... now, my phone will get past the "SAMSUNG" logo, and the warranty bit kernel notification thing on the top left... and it'll automatically reboot, and then boot again to download mode, I can boot to recovery mode, everything except the actual system...
Just a guess (I've not checked the link): go to recovery and wipe cache and dalvik before reboot to system.
wilsonhlacerda said:
Just a guess (I've not checked the link): go to recovery and wipe cache and dalvik before reboot to system.
Click to expand...
Click to collapse
Unfortunately, nope..
Jasiniok said:
So, I followed this thread, used unsu, and things just as described in there:
https://forum.xda-developers.com/apps/magisk/switching-supersu-to-magisksu-t3625579
The thing is, I flashed LineageOS's boot.img which I had, though... now, my phone will get past the "SAMSUNG" logo, and the warranty bit kernel notification thing on the top left... and it'll automatically reboot, and then boot again to download mode, I can boot to recovery mode, everything except the actual system...
Click to expand...
Click to collapse
Did you back up the boot in twrp before u do that?
I had similar problems before but i immediately gave up to use and just restore my boot partition from working one
Kglim said:
Did you back up the boot in twrp before u do that?
I had similar problems before but i immediately gave up to use and just restore my boot partition from working one
Click to expand...
Click to collapse
Nope, I didn't xD. But yeah, luckily I didn't have a lot of pictures and things(Even tho i could back them up), but yeah, I installed a even newer rom(unofficial). Thanks a lot for helping/trying to help!
Jasiniok said:
Nope, I didn't xD. But yeah, luckily I didn't have a lot of pictures and things(Even tho i could back them up), but yeah, I installed a even newer rom(unofficial). Thanks a lot for helping/trying to help!
Click to expand...
Click to collapse
I think you could save ur data partitiin and sjust system wipe and dirty flash for carry yiur data.
Good luck to ya!!! :fingers-crossed:
Long story short, I hard-bricked this thing to Hell. I'm in Download mode and have QFIL but I don't have a saved fstab so I can't flash the rom properly.
Someone wanna kindly post one, please??
Much obliged.
jake5253 said:
Long story short, I hard-bricked this thing to Hell. I'm in Download mode and have QFIL but I don't have a saved fstab so I can't flash the rom properly.
Someone wanna kindly post one, please??
Much obliged.
Click to expand...
Click to collapse
What firmware are you on?
kountry83 said:
What firmware are you on?
Click to expand...
Click to collapse
Heh. So, after a long day i neglected to plug my phone in to charge before the battery totally died and now it's stuck in a bootloop. This seems to be a somewhat common issue with this phone when it's been modded. Understandable but managable quirk. Usually I can just fastboot flash boot and it seems to resolve the problem, then I reboot-bootloader (after a successful boot) and re-flash my magisk_patched boot. For some reason, my stock boot image trick didn't work so I tried again, specifying boot_a and boot_b, just to make sure i hit the right slot. Still no luck. So I pulled out the heavy guns and ran flashall.bat (edited to NOT delete userdata). Being tired, annoyed, frustrated, in a hurry at 1:30AM, and tired of re-flashing this damn thing, I realized as it rebooted to a BLACK DEATH SCREEN that I really fu***d up and flashed MATA Q.032 update!
So currently it's boned.
But it automatially seems to be dropping itself into DOWNLOAD mode so I believe that means I should be able to use QFIL to restore partitions and upload at least enough partitions to get into a fastboot-able state and then run the correct flashall of the latest AURA CHERYL2.
jake5253 said:
Heh. So, after a long day i neglected to plug my phone in to charge before the battery totally died and now it's stuck in a bootloop. This seems to be a somewhat common issue with this phone when it's been modded. Understandable but managable quirk. Usually I can just fastboot flash boot and it seems to resolve the problem, then I reboot-bootloader (after a successful boot) and re-flash my magisk_patched boot. For some reason, my stock boot image trick didn't work so I tried again, specifying boot_a and boot_b, just to make sure i hit the right slot. Still no luck. So I pulled out the heavy guns and ran flashall.bat (edited to NOT delete userdata). Being tired, annoyed, frustrated, in a hurry at 1:30AM, and tired of re-flashing this damn thing, I realized as it rebooted to a BLACK DEATH SCREEN that I really fu***d up and flashed MATA Q.032 update!
So currently it's boned.
But it automatially seems to be dropping itself into DOWNLOAD mode so I believe that means I should be able to use QFIL to restore partitions and upload at least enough partitions to get into a fastboot-able state and then run the correct flashall of the latest AURA CHERYL2.
Click to expand...
Click to collapse
This struck a chord with me as I'm currently suffering from the same bootloop problem and I'm using the same fix kind of, except when it happens I use "fastboot restart recovery" from the bootloader and then flash a boot.img backup I have on my SD. My last phone was a MATA and I still have the images in my SDK directory, definetly going to clean it up now