Hello everyone, long time luker and user of xda, first post.
I have had a droid bionic that has been soft bricked for a few months and have finally had time to try and fix it. I do not know exactly which version it was on because I had the bionic shortly and it has been a while since it was usable.
Useful information for what version it is on:
I know it was on gingerbread
Fastboot Flash Mode (s) 0A.61
Regular turn on yields "M" logo with Dual Core Technology under it and nothing more
How I bricked it:
I was rooted and had bootstrap installed. I think I had clock work mod recovery and wiped data cache etc, I forget if I had already flashed a custom rom or not, but from recovery I clicked restart system and I have been stuck.
What I have tried:
1, Plugging it in to a computer while it is in Fastboot Flash Mode to 4 different computers with 20+ Cables with the battery charger (I have another bionic that I charged the battery with) and it either does nothing or tells me the device has malfunctioned
2. Go to stock recovery (I am mostly sure it is stock, has "reboot system now, apply update from sdcard, wipe data/factory reset, wipe cache partition) and wiping data/factory reset and wipe cache partition, then reboot system now, and waited 10 minutes on the "M" logo where it has been stuck
3. From Recovery mentioned in step 2, instal update 905 zip file yields:
__ Install /sdcard ...
Finding update package...
Opening update package...
Verifying update package...
Installing update...
assert failed: file_getprop ("/system/build.prop", "ro.biuld.fingerprint") == verizon/targa_vzw/cdma_targa:2
File_getprop("/system/build.prop", "ro.build.fingerprint"_ == "verizon/targa_vzw/cdma_targa:2.3.4/5.5.1_84_DBN-74/12:user/release-keys"
E:Error in /temp/sideload/package.zip
(Status 7)
Installation aborted.
I am not sure if I am on .902, but I don't know how to check. I think I had just wipe data cache etc before installing the custom rom is what brought me to the soft brick. I tried to provide as much information as possible. I have tried many other guides and looked for previous update zips to try since I can't get any computer to see it, but all have lead to broken mediafile links or expired dropbox links. Any help is appreciated. Let me know if there is anyway that I can give you more information
Thank you for your time,
Travis
As far as fastboot goes, try plugging the phone in while in fastboot mode and then restart the computer with the phone still plugged in. That's what it took for me before the phone was recognized
Thank you for your attempt. I found out after I had it fixed the problem was a bad charging port that only works part of the time. If I would have known that before I messed with the software and bricked it, I could have returned it. Oh well, lesson learned.
Related
I'm trying to fix my friends G1, I hold the camera button and power button and only get into the hard reset screen.
I've tried ALT + L and wipe date/factory reset then reboot system now and nothing. All I can get is that hard reset screen.
Also in the system recovery at the bottom it says E: Cant open /cache/recovery/command.
Any ideas? I wanna try to get this thing up and working again. It's bone stock, never got rooted or changed in any way.
nbturbos said:
I'm trying to fix my friends G1, I hold the camera button and power button and only get into the hard reset screen.
I've tried ALT + L and wipe date/factory reset then reboot system now and nothing. All I can get is that hard reset screen.
Also in the system recovery at the bottom it says E: Cant open /cache/recovery/command.
Any ideas? I wanna try to get this thing up and working again. It's bone stock, never got rooted or changed in any way.
Click to expand...
Click to collapse
I would try loading the original DREAIMG.nbh file onto the sdcard and then try the bootloader option and see if the presence of the nbh file "forces" it to go into bootloader....
Otherwise, I'm pretty stumped...
I've just got a similar problem.
The ONLY thing I can do is entering the Android System recovery (2e) menu.
If I try powering off the phone and:
-Holding home = android system recovery with the reboot system now, apply sdcard:update.zip wipe data/factory reset and wipe cache partition options.
-holding camera = same thing.
It seems like whatever I try with the little android experience I have and reding on forums high and low, I cannot get ADB working, it doesn't list my device OR connect using adb devices and adb shell.
When trying fastboot It's just waiting for device.
If I try installing from sdcard with the alt-s option it either says verification error (custom roms) or with the signed OTA/original roms it starts/stops like this:
E:Can't open /cache/recovery/command
-- Install from sdcard...
Finding update package...
Opening update package...
Verifying update package...
Installing update...
Installation aborted.
This is VERY frustrating for me since I have NO idea what version is on it, the 1.5 or 1.6 original rom or some custom rom.
It seems like it's a "standard" rom onboard, but since I cannot get pass the "!" screen whatsoever, ADB doesn't work and fastboot is just waiting for better weather or something, I cannot verify ANYTHING.
I also have a Hero wich is flawless with ANY rom I trow at it, recovery image and radio.
So Any ideas on how to fix this ?
Heh, I really hope there is someone out there that REALLY can help me with this.
Thank you
bump ? someone ???
anyone ?
Plz come up with a solution, I've read and read, but nothing......
btw. I don't like the S.E. k850 !!!
hello
what happened to the phone in the end ? have you managed to unbrick it ?
If holding camera button while powering on gets you to recovery chances are your home button is stuck
Sent from my HTC Vision using xda premium
simple camera + power
any way to fix a hard brick? no bootloader, no recovery...just the g1 screen lol i flashed a spl before radio and it killed it
sure, if you jtag it!
other than that.... nothing
Damn! LOL meh,it had a good life. Time to move on to newer phones.
Sent from my Incredible using XDA
Hi all.
I've used standart OS for a long time and I decided to install CM10 (JB) using Clockwork Recovery 6.0.1.8.
First of all, have installed Clockwork and put CM10 and Gapps in sdcard.
After that, i start tablet in recovery mode and 've installed CM10 via Clockwork. Without rebooting, i have installed Gapps also via Clockwork.
But i forgot to wipe device before that
So after rebooting i got animated video with triangles. Waiting for 20 minutes... nothing. After 30, i switched off device pressing power button.
After switching it on, there is that triangles...
I have entered to recovery and wipe all data, but device freezed on cleaning cache. I had no choice and reboot it.
But he kept silence, lol. Nothing happened, black screen. Recovery also didn't work.
Connecting to PC... Found XPA device (or not XPA, i forgot). So i googled about it and download and install special driver.
Now device defines as NVIDIA USB Boot-recovery driver for Mobile devices.
Odin cant see the device, ofc. Recovery isn't working.
nvflash --sync:
Code:
Nvflash started
rcm version 0X4
Command send failed (usb write failed)
(After this comand, device autounplugged)
I don't know what to do, please help me to recover my brick.
kudos on the full and clear report.
but too many parallel threads for same issue
http://forum.xda-developers.com/showthread.php?p=31177035
eskimono said:
Hi all.
I've used standart OS for a long time and I decided to install CM10 (JB) using Clockwork Recovery 6.0.1.8.
First of all, have installed Clockwork and put CM10 and Gapps in sdcard.
After that, i start tablet in recovery mode and 've installed CM10 via Clockwork. Without rebooting, i have installed Gapps also via Clockwork.
But i forgot to wipe device before that
So after rebooting i got animated video with triangles. Waiting for 20 minutes... nothing. After 30, i switched off device pressing power button.
After switching it on, there is that triangles...
I have entered to recovery and wipe all data, but device freezed on cleaning cache. I had no choice and reboot it.
But he kept silence, lol. Nothing happened, black screen. Recovery also didn't work.
Connecting to PC... Found XPA device (or not XPA, i forgot). So i googled about it and download and install special driver.
Now device defines as NVIDIA USB Boot-recovery driver for Mobile devices.
Odin cant see the device, ofc. Recovery isn't working.
Could you tell us what kernel are you using? Apparently, from what i read in this forum cm10 with old HC kernel will not brick while wipe. Thanks.
nvflash --sync:
Code:
Nvflash started
rcm version 0X4
Command send failed (usb write failed)
(After this comand, device autounplugged)
I don't know what to do, please help me to recover my brick.
Click to expand...
Click to collapse
Could you tell us what kernel are you using? Apparently, from what i read in this forum cm10 with old HC kernel will not brick while wipe. Thanks.
Hi everyone,
I seem to have nothing but trouble when it comes to installing OTA updates for my Gear Live, and am wondering if anyone can help me.
It all started when the Android 5.1.1 update notification arrived on my Gear Live some time ago. I eagerly installed it, and expected it to install without any problems. Unfortunately, the update reached around 30%, before displaying the Android mascot with a red exclamation mark. I managed to restart the watch, and re-downloaded and installed the update. The same thing happened, except, it was stuck in a boot loop :crying:
I contacted Samsung Australia who took the watch in for repairs (it took them 4 weeks). I was pretty happy to see the watch working again, and running the 5.1.1 update.
Just yesterday, I received a notification that an update is ready to be installed. I swiped and hit install. The watch rebooted, and began the installation. Again, reaching 30% before failing and displaying the Android mascot with the red exclamation mark. I am yet again stuck in a boot loop. I managed to tap the Android mascot, which brought up the Android System Recovery. It said
"Installation aborted.
OTA failed! Please power off the device to keep it in this state and file a bug report!"
I have cleared the cache, and have wiped the data through recovery. This seems to allow the watch to boot up, however, the process repeats itself when I try to update it again.
Does anyone know why the update would be failing, especially after it has already been repaired by Samsung, and how I can fix it myself (I don't really want to be without a watch again for 4 weeks)?
Thanks,
Tim
Did you try the live restore tool? (read the whole thread)
Brendo said:
Did you try the live restore tool? (read the whole thread)
Click to expand...
Click to collapse
I attempted to use it, however, it was unable to detect my device.
Update: I attempted the update again, which failed. However, instead of wiping the data, I navigated to 'Install via ADP' (or the likes), which brought up an error message:
Verifying current system...
"/system/priv-app/ClockworkHomeGoogle/ClockworkHomeGoogle.apk" has unexpected contents.
E:Error in @/cache/recovery/block.map
(Status 7)
Installation aborted.
OTA failed! Please power off the device to keep it in this state and file a bug report!
Click to expand...
Click to collapse
tims1710 said:
I attempted to use it, however, it was unable to detect my device.
Update: I attempted the update again, which failed. However, instead of wiping the data, I navigated to 'Install via ADP' (or the likes), which brought up an error message:
Click to expand...
Click to collapse
Try a different usb cable? (ie official, not a cheap one)
My watch always took a few goes to get detected by adb
tims1710 said:
I attempted to use it, however, it was unable to detect my device.
Update: I attempted the update again, which failed. However, instead of wiping the data, I navigated to 'Install via ADP' (or the likes), which brought up an error message:
Click to expand...
Click to collapse
I had that exact error yesterday when I was trying to install new OTA update. I flashed back to KMV78Y(from live restore tool v2) Don't use v3 it has corrupted file and breaks bluetooth.
Try to manually flash using fastboot. I wouldn't recommend trying to flash recovery partition from live restore tool since you can end up with a broken OTA and broken adb sideload. Also, don't try to flash TWRP into recovery partition. Loading it into ram memory is fine though.
Anyways, to manually flash using fastboot, you need to open console and go to directory of Gear live restore tool. Make sure your watch is in bootloader mode, not recovery. Type fastboot flash boot 78Yboot.img and then fastboot flash system 78Ysystem.img Do factory reset just in-case and upgrade your way up to latest firmware.
Post in wrong section, its 1st gen. Please move
So recently I decided to unlock my bootloader and flash CM12 on my Moto G 1st gen
Everything went fine till a friend told me to download and install Xposed. As I launched the app and hit frame work it mentioned creating a backup before installing so I did using TWRP. From there I rebooted the phone and thats where I ran into problems, it started to bootloop. After many hours (3 days to be exact) I still cant get it out of this state.
I thought I fixed it by reflashing, but apparently it just flashed it onto a seperate partition and the new ROM didnt work well (Notification bar didnt pull down right, no home button or multi-task). Since it didnt work I tried to wipe it and reflash but that apparently wouldnt boot, then I lost the ability to access recovery.
ADB doesnt find the device, I think usb debugging got disabled at some point.
I need some help on how to unbrick this, I'm 4 days in and still out of luck. Please!
Nobody?
You can´t access the recovery at all? When i get into a bootloop i need to do a little trick to enter recovery; hold down the power button for several seconds until it reboot, then as soon as the screen turns black hold the power button and volume down for 5 seconds to enter into bootloader. Then enter recovery from the bootloader, do a full wipe and install a stable rom. If you can´t connect the phone to the pc, take the sd card out and put it on another phone so you can connect it to a pc to transfer a stable rom for flashing on your phone.
Sorry this is late, completely forgot I post this. I can now get into recovery although some features dont work as the phone has nothing else on it. Got a USB OTG cable today and going to try mount cm12 that way.
Update : Using TWRP mount I now have files on the device (Data, boot, sys, system) which I didnt have before. Although I'm now getting a E:unable to mount '/system' but TWRP says Successful. Any thoughts?
Update 2 : Flashed it another 2 times, that seemed to fix it. Now no SIM detected.
Recently I tried out the Nougat preview on my EVA-L09C636. It was ok but seeing as there was a problem with fonts and I'd lost root access, I began thinking about going back to MM.
To prepare for downgrade I tried using srktool to bring TWRP back (and I think this is my big mistake as srktool uses a TWRP made for MM, not N, is that right?). After I tried to restore TWRP I noticed "not recognised" errors when I connected my phone to PC again.
System recovery using hajuuk's Firmware Updater and HiSuite looked like it would complete but near the end of the process (the restoring system part) HiSuite aborted itself saying my device wasn't supported. This has left my P9 is in an unusable state where the only thing I can access is fastboot. Also I can't turn off my phone - holding down power simply makes it reboot then get stuck at the "Your device ... can't be trusted / Your device is booting now" screen.
Reading around a bit I attempted to unbrick it without any luck:
1. downloaded EVA-L09C636B152 update.zip from http://forum.xda-developers.com/p9/development/rom-stock-rom-eva-l19c636b168-t3419586 and installed Snoop05's 15 seconds ADB Installer.
2. extracted images from update.zip using Huawei Update Extractor and did
Code:
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash cust cust.img
then tried rebooting holding volume up + power several times (but never got past untrusted device boot screen).
3. extracted contents of update.zip to folder 'dload' on a blank sd card, trying to force update several times by rebooting and holding down power + volume up + volume down (still never get past the screen saying my device is booting).
At this point I'd be happy to get anything happening on my phone - Marshmallow, Nougat or even some other ROM so I can use my device again.
Any ideas? I'm on EVA-L09 C636.
i2ectcf said:
Recently I tried out the Nougat preview on my EVA-L09C636. It was ok but seeing as there was a problem with fonts and I'd lost root access, I began thinking about going back to MM.
To prepare for downgrade I tried using srktool to bring TWRP back (and I think this is my big mistake as srktool uses a TWRP made for MM, not N, is that right?). After I tried to restore TWRP I noticed "not recognised" errors when I connected my phone to PC again.
System recovery using hajuuk's Firmware Updater and HiSuite looked like it would complete but near the end of the process (the restoring system part) HiSuite aborted itself saying my device wasn't supported. This has left my P9 is in an unusable state where the only thing I can access is fastboot. Also I can't turn off my phone - holding down power simply makes it reboot then get stuck at the "Your device ... can't be trusted / Your device is booting now" screen.
Reading around a bit I attempted to unbrick it without any luck:
1. downloaded EVA-L09C636B152 update.zip from http://forum.xda-developers.com/p9/development/rom-stock-rom-eva-l19c636b168-t3419586 and installed Snoop05's 15 seconds ADB Installer.
2. extracted images from update.zip using Huawei Update Extractor and did then tried rebooting holding volume up + power several times (but never got past untrusted device boot screen).
3. extracted contents of update.zip to folder 'dload' on a blank sd card, trying to force update several times by rebooting and holding down power + volume up + volume down (still never get past the screen saying my device is booting).
At this point I'd be happy to get anything happening on my phone - Marshmallow, Nougat or even some other ROM so I can use my device again.
Any ideas? I'm on EVA-L09 C636.
Click to expand...
Click to collapse
did you wiped data, cache, dalvik?
snapdesign said:
did you wiped data, cache, dalvik?
Click to expand...
Click to collapse
Hi! I'm not sure how to wipe data, cache or dalvik, because when I upgraded to Nougat this apparently removed TWRP.
Also I'm wondering if trying to use srktool to reinstall TWRP for 6.0 might have corrupted my 7.0 phone?
Is there any way to wipe data, cache, and/or dalvik now? Or are there other things I could try to unbrick?
Although my phone was in a pretty bizarre state - it would get hot and sit on the booting now screen until battery died - I was able to use DC Phoenix to make it boot up again. At that point it had no themes and only KitKat-esque icons. A reset and upgrade later icons and themes work and I'm back on stock Marshmallow. Here's an outline:
1. Google "Huawei Bricked phone repair guide with DC Phoenix", go to the first result and look at the instructions (I can't post URLs yet).
I used Method 1. But note! The newer versions of DC Phoenix are missing a feature that the instructions make clear you have to use. To get the original version used in their guide, you have to download the latest version of DC Phoenix, open it on your PC, then click "Enter Support Area" which logs you in to a download section. Find "DC Unlocker Softwares", "DC_Phoenix", then download DC_Phoenix_v14.rar and run that instead. Whether it's Method 1 or 2 make sure you complete it - i.e. the fastboot flash step AND a step they call "flashing in upgrade mode."
(Also note that for DC Phoenix you want to feed it the oldest version of firmware available for your phone, in my case b152. This is because themes and icons won't be fixed until it receives the next version of firmware as an update.)
2. Once I did the fastboot and upgrade flash, I did a system reset from the Settings app trying to get themes and current icons again. (This didn't work but doesn't do any harm or might have helped somehow further down the line).
3. I used hajuuk's Firmware Updater and HiSuite to upgrade to the next version of firmware available (in my case b168).
3. All fine and your phone is back to stock - icons look nice again and local themes are back. To get the original icons layout, go to Recents, hold down on the Trash Icon, show system apps, and Clear Data for Huawei Home.
i2ectcf said:
Although my phone was in a pretty bizarre state - it would get hot and sit on the booting now screen until battery died - I was able to use DC Phoenix to make it boot up again. At that point it had no themes and only KitKat-esque icons. A reset and upgrade later icons and themes work and I'm back on stock Marshmallow.
Click to expand...
Click to collapse
Thanks for sharing! You saved me!