{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Okay, firstly, this all started when I flashed the new Sense 7 Insert Coin Rom. My phone would not boot up after having turned off/lost battery.
Here is a list of the problems:
1. Cannot boot into recovery, gives purple loading text and then bootloops again
2. When charging it charges for 5-10 seconds minimum and then bootloops
3. The device has turned on before during these bootloops once before
4. The device could be left charging all night and bootloops all night, no way to power down
5. Upon attempting to power the device on after 12 hours of charging it has no battery charge left
6. Cannot flash a new recovery for some reason (via cmd)
7. Tried flashing TWRP, CWM and PhilZ again, none worked all resulting with the error code 'error: cannot load recovery.img' having put the code 'fastboot flash recovery recovery.img' with no results
8. Device can only boot into bootloader, nothing else.
9. And also, the above CMD error too..
I have been without my phone for 3 days now and having tried all the possible options I knew of this was my last resort.
Hope someone has a solution, thanks
I had a similar issue with my device. Turned out that the flash storage had died.
Took it in to my operator and they replaced it with a refurbished HTC One
Had to pay because the phone had some nicks and scratches.
Mat214 said:
I had a similar issue with my device. Turned out that the flash storage had died.
Took it in to my operator and they replaced it with a refurbished HTC One
Had to pay because the phone had some nicks and scratches.
Click to expand...
Click to collapse
Oh dear... was hoping this wasn't serious. Thanks.
Matthew.One said:
Oh dear... was hoping this wasn't serious. Thanks.
Click to expand...
Click to collapse
not so much a solution, but it sounds to me like your battery is dead dead, as in you need a new battery, if the phone is dyiong pretty much as soon as you unplug it from the charger then it has to be the battery, and as a safety feature, you cant flash anything with a battery that low, which would also explain the flashing error your getting.
Related
Yo.
After countless hours of just trying to unlock the damn fastboot/hboot whatever, I finally did it, flashed the recovery, then a custom OS. But I forgot to do the hboot downgrade s-off thing, and now it's stuck on the HTC logo and doesn't boot. I was supposed to try the IncS Downgrade script http://forum.xda-developers.com/showthread.php?t=1373697
But this requires me to be booted up in a rom, which is kinda silly I guess because it restarts into fastboot afterwards.
But anyway, phone doesn't get recognized on the script when I'm allready in fastboot, and I've been trying all kinds of fixes and I'm about to lose it.
So I'm giving up and asking if anyone got a solution while I still got some of my sanity left :silly:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This is all I'm seeing atm.
ruckus92 said:
Yo.
After countless hours of just trying to unlock the damn fastboot/hboot whatever, I finally did it, flashed the recovery, then a custom OS. But I forgot to do the hboot downgrade s-off thing, and now it's stuck on the HTC logo and doesn't boot. I was supposed to try the IncS Downgrade script http://forum.xda-developers.com/showthread.php?t=1373697
But this requires me to be booted up in a rom, which is kinda silly I guess because it restarts into fastboot afterwards.
But anyway, phone doesn't get recognized on the script when I'm allready in fastboot, and I've been trying all kinds of fixes and I'm about to lose it.
So I'm giving up and asking if anyone got a solution while I still got some of my sanity left :silly:
This is all I'm seeing atm.
Click to expand...
Click to collapse
Extract boot.img from custom Rom zip file, place in PC's fastboot directory. Enter fastboot mode on phone. Type
Code:
fastboot flash boot boot.img
and restart.
THAAAAAAAAAAAAAAAAAAAAAAAAAANK YOOOOOOOOOUUUUUUUUUUUUUUUU!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! that just made my day bro:good:
I have the same problem ... I did that but when I restart I must do it again !!
Sent from my Incredible S using xda premium
Fshtiwi said:
I have the same problem ... I did that but when I restart I must do it again !!
Sent from my Incredible S using xda premium
Click to expand...
Click to collapse
Make sure you are typing the command correctly and not just fastboot boot boot.img
Here is the situation I have an HTC ONE (M7) Here which does absolutely nothing but show this message...
It does not have usb debugging enabled and adb will not register it. I can however connect to it via fastboot....
Ive gotten as far as unlocking the bootloader... But now cannot seem to get any further as everything I have read uses ADB and i cannot get it to recognize ADB Device.
Basically from what i am reading.... Is flash custom recovery such as TWRP (Which i have downloaded) and i want to just reinstall stock rom etc. Not trying to root or anything here, just simply trying to reinstall factory software for HTC One (M7) - Telus Canada to hopefully resolve the issue.
Please any help is greatly appreciated I have been up now for nearly 20 Hours trying to get this done.
Exactly like this
dugie33 said:
Here is the situation I have an HTC ONE (M7) Here which does absolutely nothing but show this message...
It does not have usb debugging enabled and adb will not register it. I can however connect to it via fastboot....
Ive gotten as far as unlocking the bootloader... But now cannot seem to get any further as everything I have read uses ADB and i cannot get it to recognize ADB Device.
Click to expand...
Click to collapse
Because you are boote din bootloader mode. ADB can't work when in bootloader mode, only from custom recovery or from a booted rom + usb debug on. Here a nice table I made last week to explain the same thing to another guy:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Basically from what i am reading.... Is flash custom recovery such as TWRP (Which i have downloaded) and i want to just reinstall stock rom etc. Not trying to root or anything here, just simply trying to reinstall factory software for HTC One (M7) - Telus Canada to hopefully resolve the issue.
Click to expand...
Click to collapse
Post the output of "fastboot getvar all" (remove your imei and sn before posting)
Ok so I just tried flashing CM10 to my Droid 4 and messed something up. The flash failed using SafeStrap TWMP so after previously backing up the Previous stock ROM and Data I tried restoring it. Well. Now the phone won't do jack like the Motorola M logo appears and then goes blank I have left it for an hour with no luck I can't charge the phone up enough to actually finish a APFASTBOOT and unlock the bootloader so...I don't know whats going on someone please help me! :crying:
Ikuto500 said:
Ok so I just tried flashing CM10 to my Droid 4 and messed something up. The flash failed using SafeStrap TWMP so after previously backing up the Previous stock ROM and Data I tried restoring it. Well. Now the phone won't do jack like the Motorola M logo appears and then goes blank I have left it for an hour with no luck I can't charge the phone up enough to actually finish a APFASTBOOT and unlock the bootloader so...I don't know whats going on someone please help me! :crying:
Click to expand...
Click to collapse
Booting from AP fastboot to charging mode
If the Device will only boot to AP Fastboot and it says Battery Low
Connect the phone/Device ato a Wall Charger (not PC)
-In AP Fastboot Mode hold Volume down& power buttons at the same time for +10 seconds
- When screen goes black...release power button
-Then IMMEDIATELY press and hold Vol - and Vol+ to boot to Boot Menu.
- In Boot Menu scroll down with volume down to BP Tools, press volume up to select
- Device should boot to Charging Mode with battery icon
- Once battery is charged, try flashing in AP Fastboot again
This will only work if battery charging Firmware is still preset and not corrupted
If Motorola Device will not boot to Charging Mode, a Fastboot cable will be needed.
What is a Fastboot Cable
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my KFFOWI using Tapatalk
I actually have my D4 bricked at this time and always charge the battery using a pin charger
hearkenoath said:
I actually have my D4 bricked at this time and always charge the battery using a pin charger
Click to expand...
Click to collapse
is that a question?
Sent from my KFFOWI using Tapatalk
Nope sir. I just wanted to share that for me was useful extract the battery and charge it with an universal charger (pins)
Hello to all!
Two years after I bought my awesome 6/128 ZUK Z2 Pro ("international" rom, android 6.0.1, ZUI 2.1.120, no updates), I decided to mess with it. After getting some trouble done, I flashed via QFIL the stock 1.9 (possibly updated to 2.5 yet? not sure...) and the SuperSU, which I couldn't flash on stock ZUI 3.1.194. Last two days I was trying to find a way to flash TWRP but I couldn't, because I tried through fastboot and it always told me "waiting for device". I could only boot TWRP through the "fastboot -i 0x2b4c boot recovery-TWRP-3.0.2-20160712-ZUK_Z2_PRO-CN-wzsx150.img", as it was described at a guide here (BTW, guys thanks a lot for everything you share with us!). But still, it didn't let me install some roms I've tried (AOSP 6.7, AOSP 7.0), because "Updater process ended with ERROR:7". Also, after flashing the SuperSU, I couldn't open the stock recovery, it automatically redirected me to fastboot.
My (big) problem started when I randomly chose "Boot to FFBM" through fastboot, so the "All Failed" screen was appeared. It couldn't be so bad, but is behaved like having a bad stroke, and the "buttons" on the bottom or anything else, can't be selected or scrolled properly. After rebooting (holding the power button), it sent me there, again. So now, it is impossible to boot at the rom. I can still boot into bootloader, but it doesn't recognize QFIL yet, in order to install the rom again. I can also boot into twrp via the "fastboot -i 0x2b4c boot recovery-TWRP-3.0.2-20160712-ZUK_Z2_PRO-CN-wzsx150.img", but nevertheless i cannot install another rom.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I mean, I REALLY need your help, otherwise I had to buy another phone! (I'm stuck with my mother's, old J5 2015 for now)
I still cannot boot into stock recovery, and I can install nothing from that twrp. I think my only hope is, if you know another command through powershell, which my phone can obey (except it often tells me "waiting for device"). Or else, this would be the hard way for me of learning what "hard-brick" is.
Thanks in advance for your time, sorry for grammar/spelling mistakes, I would really appreciate any help given! :crying:
Images:
Oh, unfortunately the images aren't shown, I hope they are here:
For some reason they aren't shown, I got them by a shareable link in google Drive.. If anyone is interested in helping me, I can send the images private. In fact, I would even pay some bucks for this!
Ok, I noticed that there are also many "bricked" (or not) cases from another members here that haven't be answered, but since I found the solution for my case I'm leaving the thread for anyone who possibly need it:
https://zukfans.eu/community/thread...-read-this-before-creating-a-new-thread.7603/
In my case, the answer was on the last Q & A, about the accidentally stuck to the FFBM mode, so I just thanked this guy. Have a nice day!
I need help.
The problem?My phone is bricked AF.
Where it started:So, a few days ago I was flashing custom ROMS on my Redmi 9C, at this point everything was good, although I did brick the phone twice, I was able to get it back up and running again using MTK Bypass and SP Flash tool.
You see, 2 days ago I stupidly it was a good idea to flash a custom ROM (Arrow OS) on top of another one (DotOS) ~I'm not a noob, I KNEW this probably wasn't going to work~. I thought it would work since it's still using the same base but shortly after flashing when I restarted my phone there was nothing, no boot logo, no sound, no vibration, nothing.
I couldn't boot to fastboot or anything, it wouldn't respond to ANY input.
At this point I already knew well how to fix the issue but this time it didn't work at all.
The first attempt kinda worked, I was able to bypass auth and flash but after like 2 seconds the flash tool stopped, and I got a STATUS_EXT_RAM_EXCEPTION error and after that I tried to reflash. It did get detected by the bypass tool a few times but after that every time I plug my phone into my pc, I get this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
and I see this in device manager:
Libusb won't even detect it.
I tried driver after driver, I switched the cable, I tried a different computer, I waited a day, I read thread after thread, installed python, tried tool after tool, but to no avail.
I tried all sorts of button combinations but the only one that does anything is vol+ and pwr but that just makes it disconnect and reconnect to my pc with the same results.
I watched a bunch of videos about it and tried every method but still, no luck. I am confused where they say remove the battery because some do and some don't, but I can't really do that in my current position anyway...
I know there are MANY similar threads on this, but I haven't been able to find anything to help me in this situation.
I've tried all sorts of solutions but now I just don't know any more.
Please. Help. Would really appreciate it.
I had a similar brick yesterday, when I tried to use mtkclient but it only got halfway. As far as I understand, the system was actually on, but it got stuck in a state where it wouldn't respond to anything.
What fixed it was power cycling the device by disassembling it, and disconnecting and reconnecting the battery (search for battery replacement videos). The idea is from this comment by bkerler, the author of mtkclient. I guess my warranty really is void now.
(Another thing I considered was power cycling it by waiting for the battery to run out, and then recharging it. But I've no idea if this might have got it into a state where it wouldn't even charge, so I didn't do it.) I'll avoid mtkclient from now on when possible, and prefer to use fastboot or a recovery for flashing.
I am a noob; no guarantee that I'm right about anything (other than that my phone works now), nor that your situation is identical to mine.
Here is solution if you are not noob,
Post in thread 'HARDBRICKED REDMI 9C ANGELICA NO BOOT NO RECOVERY NO FASTBOOT ONLY VIBRATES' https://forum.xda-developers.com/t/...-fastboot-only-vibrates.4494095/post-88308869