So i know their are a lot of posts regarding the issue with cwm 3.0.0.5, but i cant figure it out, and i've tried everything from pd15img, to trying to flash cwm 3.0.0.6 using fastboot...everything i could find here or anywhere.
mt4g
hboot-0.86.0000
s=off
microp-0429
radio-26.03.02.26_m
cwm-3.0.0.5
{
"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"
}
pic isnt of my phone, but i have the same error with cwm, nothing will install, nothing will wipe, gives "error formatting /boot", waits for a while then restarts cwm if i try to format system or cache. i cant restore anything be it factory, or cm7, or iced glacier, or any of the other roms, i get the same error as in the image above. when i try using fastboot from the bootloader it recognizes the fastboot device, but i get "(status malformed (1 bytes))" when i try to flash cwm 3.0.0.6, or any older version, it goes for a while filling the bar usually half way, then it errors out. when i try to use adb, well adb doesnt recognize it anyway i try.
I'll provide any more information, can anyone help, or has anyone had the same problem and succesfully fixed?
Edit-I know it says in the image cwm 3.0.0.6, but like i said, not my phone. i'm using 3.0.0.5 and have the same errors
Go to the development section and read through the post labeled semi brick been up yada yada.
Sent from my HTC Glacier using XDA App
First of all, you can't use fastboot since you don't have the engineering SPL.
It sounds to me that your recovery may be corrupt. Try flashing CWM 3.0.0.6 via ADB or even in terminal emulator. Once you know your recovery is good, you can further diagnose why ROMs won't flash. It's probably the recovery, but it could also be a corrupt SD card or a corrupt ROM file download.
http://forum.xda-developers.com/showthread.php?t=952433&page=3
read phatless's entry. Do what he says and download the flash_image and rename it. I just did it through the terminal and its working fine. you have to do this first because if you dont the terminal wont be able to find recovery.img
mustk1ll20 said:
Go to the development section and read through the post labeled semi brick been up yada yada.
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
been through that, like i said i looked through everything, been at it for hours. i've been trying to find a link to the engineering hboot but only partial luck, i found hboot_dhd.nb0 but have no idea what to do with it. i cant get adb to recognize the phone because it freezes at the splash screen and wont boot into android. i tried adb and fastboot in, hboot, fastboot, cwm, and the splash screen and it wont recognize my device. fastboot will recognize my device everywhere except the splash screen. idk i tried multiple sd cards, and downloaded the roms multiple times.
The eng boot is in the ultimate perm root and s=off in the development section. Along with instructions. Its sticky.
Here is the link to just download the eng http://www.megaupload.com/?d=NN5726Z8
In that original post I suggested option posted some steps to get the eng installed. So give those a try.
Sent from my HTC Glacier using XDA App
mustk1ll20 said:
The eng boot is in the ultimate perm root and s=off in the development section. Along with instructions. Its sticky.
Here is the link to just download the eng http://www.megaupload.com/?d=NN5726Z8
In that original post I suggested option posted some steps to get the eng installed. So give those a try.
Click to expand...
Click to collapse
I agree, definitely get the 0.85.2007 SPL installed, then you can use fastboot to install CWM. That is the absolute most reliable method to install your recovery, so you'll know for sure it will be good then.
Related
So I read the "If your HTC Glacier is bricked, read this" and my situation doesn't seem to apply to it being bricked OR not bricked. (photo attached)
{
"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 wanted to downgrade from 2.3.4 to 2.2 and followed this guide by Setherio:
http://forum.xda-developers.com/showthread.php?t=1178912
I followed this guide religiously and everything worked until the point of the actual downgrade. (Fastboot Downgrade Step 8)
The 'Manual Downgrade' didn't work for me, so I tried the 'Fastboot Downgrade' and on Step 8 I arrived at the black screen with gray HTC logo, but with 4 exclamation points in a triangle on each corner.
I'm not able to hard reset or even get into Hboot. I also tried using the cmd line code (>fastboot-windows flash zip StockRom.zip) one more time like the guide said, but got the error:
C:\android-sdk\platform-tools>fastboot-windows flash zip StockRom.zip
sending 'zip' (319593 KB)... OKAY
writing 'zip'... INFOadopting the signature contained in this image...
INFOsignature checking...
FAILED (status read failed (Too many links))
I've tried rebooting via cmd line and I only get the black screen with HTC logo.
Though, when I unplug my phone from the computer I get a quick glimpse of Hboot:
I'm at a loss of how to proceed and would greatly appreciate help!
Thanks,
L
Try placing the 2.3.4 PD15IMG.zip on the SD then boot into boot loader. If that does nothing, I'm as lost as you. Sorry.
invasion2 said:
Try placing the 2.3.4 PD15IMG.zip on the SD then boot into boot loader. If that does nothing, I'm as lost as you. Sorry.
Click to expand...
Click to collapse
I can't access bootloader
"fastboot reboot" might bring you out of RUU flash mode and back into normal mode.
[edit] It won't. Here's an explanation, why:
http://forum.xda-developers.com/showthread.php?p=23497027
You need to flash /misc partition with something that will not have the RUU flag set.
So just download and flash the correct RUU.
And then you'll be able to download a correct ZIP file, because if you failed the manual mode - most likely you're trying to flash a bad ZIP, screwing up your phone in process. But I believe the phone isn't dead yet.
Make sure to check/verify that the md5 checksum of the PD15IMG.zip matches where you got the file.
Sent from my HTC Glacier using XDA
PD15IMG.zip
if , you need to get the PD15IMG.zip file on your phone , and the phone cannot power on , get a micro sd adapter and plug it in your computer if you have a 5-1 card reader .
My a500 cannot perform factory reset or flash rom, and reflash recovery doesn't update the recovery, even i tried to flash bootloader using apxflasher it stuck at stage 2...
here is the situation.
im using teamwin recovery, recently i couldnt flash any rom, nor wipe all partition.
every times i flash rom or wipe partition, reboot, my tablet will back a previous state, is like every times i reboot my tab, it will restore to a "backup"
i called it restore is because all the changes i made after reboot will gone.
i tried to flash other recovery using the fasboot, it doesnt replace the teamwin recovery.
i tried use apxflasher to flash bootloader again, i get stucked in stage 2 uploading image
{
"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"
}
finally i tried flash the euus, but i got N/A for the new image version and stuck at there.
Anyone can help me with this?
chinseng85 said:
My a500 cannot perform factory reset or flash rom, and reflash recovery doesn't update the recovery, even i tried to flash bootloader using apxflasher it stuck at stage 2...
here is the situation.
im using teamwin recovery, recently i couldnt flash any rom, nor wipe all partition.
every times i flash rom or wipe partition, reboot, my tablet will back a previous state, is like every times i reboot my tab, it will restore to a "backup"
i called it restore is because all the changes i made after reboot will gone.
i tried to flash other recovery using the fasboot, it doesnt replace the teamwin recovery.
i tried use apxflasher to flash bootloader again, i get stucked in stage 2 uploading image
finally i tried flash the euus, but i got N/A for the new image version and stuck at there.
Anyone can help me with this?
Click to expand...
Click to collapse
When you tried the EUUS did you follow the flowchart in the second post of this thread? http://forum.xda-developers.com/showthread.php?t=1816560
I just ran a EUUS fine following the flowchart - But had a result similar to yours when I didn't unzip the EXE and fill in the CPUID.txt file.
I'm in the same situation, no way to get the v8 UNL BL, stops at stage 2 (BT's apxflashtool) and "3/4 recovery" with AfterOTA TOOL.
I shall try the EUUS flashing (will delete your internal memory), but now I'm very busy so I renounced..
The EUSS file flashing should help
Wedee said:
When you tried the EUUS did you follow the flowchart in the second post of this thread? http://forum.xda-developers.com/showthread.php?t=1816560
I just ran a EUUS fine following the flowchart - But had a result similar to yours when I didn't unzip the EXE and fill in the CPUID.txt file.
Click to expand...
Click to collapse
yes i did unzip it to a folder, and put in my cpuid. i got my cpuid from dmesg dump
MadMav88 said:
I'm in the same situation, no way to get the v8 UNL BL, stops at stage 2 (BT's apxflashtool) and "3/4 recovery" with AfterOTA TOOL.
I shall try the EUUS flashing (will delete your internal memory), but now I'm very busy so I renounced..
The EUSS file flashing should help
Click to expand...
Click to collapse
im not sure why i cant get the new image version. tried on winxp and win7
chinseng85 said:
yes i did unzip it to a folder, and put in my cpuid. i got my cpuid from dmesg dump
im not sure why i cant get the new image version. tried on winxp and win7
Click to expand...
Click to collapse
Couple of ideas to try...
Make sure that when that screen comes up there is not a second window it spawned hiding behind it... For me when it got to that screen I saw another window pop, and it was hidden behind the main, the popup window walks you thru the next steps of setting APX mode, plug in cable, hit ok......
Another thing to try is Right click the PBJ20upgrade.exe and choose "Run as Administrator"
Finally download a new copy... when you unzip it you should end up with Several files and then two folders /Image and /usbpcdriver. The /Image folder has all the img files it needs to install. In the root there is a file called version.cfg that when I view inside it seems to have the info that the program uses to tell what version it is going to install... Hazzard a guess that if that file is missing it might not know what its going to install.
After accidentally flashing the wrong MIUI ROM (Prime instead of 4G from Xiaomi's site), I've had problems trying to flash the correct ROM and a custom recovery ROM. The MIUI Updater and Mi Recovery methods just don't work, as all the zip files raise errors. I've now managed to root the device, but all my attempts to install a custom recovery ROM have failed. I've tried various methods, the most recent one being fastboot flashing the recovery.img file. The process acts like it's been successful, but when I try to boot into recovery mode by pressing vol+ and power, I see an interface that looks like a default/factory interface. I've seen it on previous attempts, so I know flashing TWRP has been unsuccessful. Does anybody know what it is and how I can replace it with TWRP?
{
"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"
}
jsp_1983 said:
After accidentally flashing the wrong MIUI ROM (Prime instead of 4G from Xiaomi's site), I've had problems trying to flash the correct ROM and a custom recovery ROM. The MIUI Updater and Mi Recovery methods just don't work, as all the zip files raise errors. I've now managed to root the device, but all my attempts to install a custom recovery ROM have failed. I've tried various methods, the most recent one being fastboot flashing the recovery.img file. The process acts like it's been successful, but when I try to boot into recovery mode by pressing vol+ and power, I see an interface that looks like a default/factory interface. I've seen it on previous attempts, so I know flashing TWRP has been unsuccessful. Does anybody know what it is and how I can replace it with TWRP?
Click to expand...
Click to collapse
So you can boot into MIUI?
If you can, are you then trying to install a custom recovery and flash another rom?
Which recovery do you go into now?
siddjazz said:
So you can boot into MIUI?
If you can, are you then trying to install a custom recovery and flash another rom?
Which recovery do you go into now?
Click to expand...
Click to collapse
After spending all of yesterday on the issue, I finally managed to fix it late last night. Counter-intuitively, my device required a Chinese ROM rather than a Global ROM. In the end I was able to root the device, eventually flash the correct version of TWRP (there's conflicting advice out there on using the 88047 and 86047 versions) and then eventually flashing a multi-language version of MIUI from Xiaomi.eu. It was a very, very painful experience, though.
Still, if I try to boot into recovery using vol+ and power, like so many guides advise, I'm presented with that unusual menu. I don't know what it is. The only way I can boot into recovery is via MIUI's Updater option. Ideally, I'd like to have the phone do what it's supposed to do when booting to recovery, but I'm just thankful that it's working again. This all came about because Gearbest sold it with their own adware-riddled version of MIUI.
Try VOL UP + VOL DOWN and then the power button.
Hey guys,
i recently bought a OP2 from Ebay which is bricked (Stuck on bootloop). The phone wasn't able to boot into Recovery. Only thing worked was Fastboot. I managed to get stock recovery to work using this Guide (Method 3):
https://forums.oneplus.net/threads/updated-28-06-2016-mega-unbrick-guide-for-a-hard-bricked-oneplus-2.347607/
Unfortunately it still stucks in a bootloop. I tryed flashing serveral Stock-ROM's. Does anyone know a solution to fix this?
ADB Sideload give me this output (everytime at around 94%)
{
"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'm kind of new to this.
Greedings
Kynie
Make sure to update the fastboot/bootloader to the newer 3.0/hydrogenos version as all newer ROMs require this to boot.
How can i do this? I have stock bootloader v. 1.0 installed and not able to flash via fastboot cause the phone is locked. Cannot unlock because i'm not able to turn the phone on.
Then just use the standard Qualcomm flash-mode to restore the phone to factory OxygenOS 3.0.2. The utility and 3.0.2 full OTA zip required can be found in this forum if you search.
Then just use the standard Qualcomm flash-mode to restore the phone to factory OxygenOS 3.0.2. The utility and 3.0.2 full OTA zip required can be found in this forum if you search.
Click to expand...
Click to collapse
Thanks for the information. The OTA zip file do I have already. Sadly I can't find such an utility you are talking about. The only thing I found was a chineese (or I think it's chineese) tool which I already tryed but not worked. This tool just brings the stock recovery v 1.0 to life.
Or do you mean a diffrent tool?
In a similar position to you. Phone was working fine (only received it today and tried to get CM13 on it)
My bootloader is unlocked, but phone will no longer boot up, or go into recovery.
I can get it into FastBoot, but it doesn't show up anymore in ADB devices. When in fastboot, the device shows as "Android Device, Marshall London Bootloader interface"
If I switch the phone off and check Device manager it just shows as unknown device and then windows gives me an error message that its not functioning properly.
I have tried to follow this guide https://forums.oneplus.net/threads/...ck-guide-for-a-hard-bricked-oneplus-2.347607/
but it won't allow me to update the device driver, even if I turn off signature for drivers.
The only thing I can get to load is Fastboot. I did at one point have a little penguin on the screen, but haven't replicated that again.
Can anyone help? I'm pulling out my hair
Are you sure you didn't just boot it up into fastboot-ish mode? To be able to flash using that tool you mustn't boot up the phone, make sure it's of and hold volume up when connecting the USB cable, this way the phone will enter chinese factory flash mode at which you can flash using the chinese tool. Also the drivers require you to disable driver signature in windows to install since it's not signed.
Got it working in the end. I just ran the application without bothering with the USB driver stuff and it detected the phone. Then flashed the stock rom and it's now booted.
Still can't get CM13 installed, as I get the error 7 in recovery and that's what got me in the mess!
Sent from my ONE A2003 using Tapatalk
I turned driver signature of and installed drivers succesfully. I run the chineese tool and it finishes succesfully but the phone is still in bootloop. This is frustrating...
Hello do you have find à solution ??
hi, yesterday mi moto g4 xt1621 was working well but today when i switch it on it didn't show me the boot logo and started in fastboot mode
{
"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"
}
so i tried to went to the recovery and it gave me an error which said: "start up failed:
your device didn't start up successfully.
use the software repair assistant on computer to repair your device.
connect your device to your computer to get the software repair assistant
AP Fastboot Flash mode (secure)
Fastboot reason: failed to initialize partition table
error: no bootimage found. skip to fastboot
boot up failed
i tried a lot of things, when i connected it to my pc recognizes it as Fastboot athene_13mp S
and i didn't get the software repair assistant
and
i don't know what to do if someone could help me, I would be very grateful
have you found the solution
adithya11198 said:
have you found the solution
Click to expand...
Click to collapse
unfortunately i haven't found the solution yet
System lost perhaps?
It seems that the boot image was lost or erased on your phone, at least you still keep the Bootloader right? it's still alive, so there's a way to solve it, yet, this means the procedure may be hard, but you can make it boot again but your files will be erased since flashing a rom by fastboot usually clears all User Data, follow the steps from here https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761 but Skip the Blank Flash files, you won't need them (thankfully) I hope this solve your problem
Omega Adrek said:
It seems that the boot image was lost or erased on your phone, at least you still keep the Bootloader right? it's still alive, so there's a way to solve it, yet, this means the procedure may be hard, but you can make it boot again but your files will be erased since flashing a rom by fastboot usually clears all User Data, follow the steps from here https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761 but Skip the Blank Flash files, you won't need them (thankfully) I hope this solve your problem
Click to expand...
Click to collapse
Thank you Omega Adrek i will try this :fingers-crossed:
Question: I don't have the boot loader unlocked. Is there a problem with that?
null2025 said:
Thank you Omega Adrek i will try this :fingers-crossed:
Question: I don't have the boot loader unlocked. Is there a problem with that?
Click to expand...
Click to collapse
Since the Link contains the Stock Moto G4/G4 Plus rom, you shouldn't have any problem with the Bootloader being locked or unlocked, so try it out and hopefully it will make Android boot once again
Omega Adrek said:
Since the Link contains the Stock Moto G4/G4 Plus rom, you shouldn't have any problem with the Bootloader being locked or unlocked, so try it out and hopefully it will make Android boot once again
Click to expand...
Click to collapse
Ok thanks adrek, i'm going to try it when my PC recognizes my smartphones again, it's another problem which I have but I don't want to bother you with that
Rom flashing failed . What should I do?
adithya11198 said:
Rom flashing failed . What should I do?
Click to expand...
Click to collapse
As the message says, it can't find a bootlogo. (usually logo.bin). If you've got a locked bootloader, you must have all key partitions, including logo.bin on the same patch level (and as such you may have to flash all partitions).
Which firmware did you try to flash and what flashing commands did you use, and can you show us the outputs of said commands?
This will help You : https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761
thank you
Omega Adrek said:
It seems that the boot image was lost or erased on your phone, at least you still keep the Bootloader right? it's still alive, so there's a way to solve it, yet, this means the procedure may be hard, but you can make it boot again but your files will be erased since flashing a rom by fastboot usually clears all User Data, follow the steps from here https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761 but Skip the Blank Flash files, you won't need them (thankfully) I hope this solve your problem
Click to expand...
Click to collapse
Thank you really much omega adrek, it worked, my moto g4 owe you its life