General :: Unbrick HTC One S - Flashing Boot Images Failed
Nov 27, 2013
How to unbrick my one s. I can get into recovery but i cant do anything else. I have tried flashing multiple boot images from the bootloader but i get the same failed message every time i try to flash a rom. I dont have s off but i am rooted and supercid.
Every time I try I get a 'boot failed' then 'error at line 390' installation failed, aborted etc. If I try to reboot it just sticks on the HTC incredible screen. I've tried using Rom manager and directly from recovery. Re downloaded files. Maybe related but any kernels I tried stick on the same screen?
i was trying to unbrick my old cliq by flashing the original firmware and it failed idk why and it wont dectect it any more and the phone has a black screen and only the keys light up any way to save my old cliq??
my SE Xperia Pro .I was flashing it to CM10 , flashed the core but that was the last thing done successfully. Clock work Mod recovery didn't launch , so firmware even didn't started to install. Now by switching it on I just get nice picture "xperia free project" and depressing dark after it. I cant launch recovery, SEUS at the first time stopped working very quickly, the second time said that there is modified software there, and thirdly ,at last, didn't recognize my phone at all. Can i do something with it, excepting using it like a brick?
I have an Huawei Ascend y210d on which I installed CWM recovery. After that I installed a custom ROM, but now I want to flash its official firmware.But its official firmware is not installing. It got told using Huawei firmware Indian version downloaded from Huawei. I am using this procedure:
(1)First copy dload (in dload folder update.app file is present) folder to the root of the SDcard
(2)Then turn off your device pick out battery then again insert battery
I am on twrp recovery version 2.1.3 and to upgrade to 22.214.171.124 I used the Google .im app but even after the message showing that recovery was flashed successfully, when I reboot into recovery I still see the 2.1.3 twrp only..So I tried flashing it with terminal emulator but it didn't work.This error shows up every time failed scanning partitions failed with error : - 1
I tried putting the .img file in the root folder as well but it didn't work..I tried naming the root of sd card as storage/emulated/legacy, storage/ emulated / 0, /sdcard, etc but it keeps on giving this error every single time!
I flashed Omega rom today for my galaxy note 2. It uses Aroma installer which i think could be the problem. Basically I cant boot into recovery. The rom is also very laggy where people on its development thread are praising it stability! The device will stay on the 'Samsung galaxy note II gt17100' bootscreen when i try to.boot into recovery.
My Samsung Note 10.1(N8000) got stuck on boot screen at stock. No recovery only download mode. I don't know why, it was flat for about 2 weeks before I noticed.
Roms always and still flash successfully if I get the right version of odin, i think i have about 15 different odins from trying to fix this.
Things I've tried:
1.Flash stock rom 2.Flash custom recovery 3.Flash different versions of both 7+ 4.Re-partition and repeat 1-3 5.Wipe the memory and repeat 4 with many many roms
why my tablet stopped the first time and why no roms are working to recover it. What is happening here? Is it corrupt memory or motherboard etc hardware? Is there a god .pit file or god rom that could work to make something happen? What should i try now?
This shows a successful flash which had no effect on the tablet afterwards
I unlocked my bootloader a month before and I didn't know how to relock it back so I searched and found this website >>androidgadgematic I followed everything it mentioned and after finished installation, I hold on the boot button, the green light indicator blinked once and vibrated once but after that gave no respond. I didn't unroot my phone before doing the relock procedure. Now, I really don't know what to do because I searched google but none. I indeed need a step by step procedure to save my phone. How to boot my phone now, or else it is dead. I don't have if any method to reinstall ALL system files, no matter kernel, firmwares via my pc as long as it can helo my phone to boot up.
I am trying to use RSD Lite to SBF to 2.2 OTA but it keeps on giving me the dreaded Failed flashing process. Failed flashing process. (0x7100); phone connected. I am running Windows 7 x64 and have the latest Moto drivers installed (4.7.1) and am running RSD Lite 4.8. I put my phone in bootloader mode and connected my USB. It is showing iup in port 1, but I am also getting a lot of N/A values. Is this normal?
IMEI/ESN/MEID: N / A Technology: N / A Software Version: N / A Flex Version: N / A Bootloader Version: v0x003001 DRM Version: N / A
I choose the SBF file and click start and it immediately gives me that error message. Very frustrating.
I've been struggling to get my Nexus One up and running with the Sense UI. I unlocked the bootloader and rooted it (it all worked as far as I can tell) but whenever I try and flash a new ROM onto the phone I get the error E: no signature E: verification failed I have tried many different ROMs from Cyanogen mod and just a standard Nexus One ROM, but I've had no luck in getting this to work. Plus, when I just return to the original state, my WiFi is out of commission and as an AT&T subscriber (I have two lines so it's not the end of the world), I rely heavily on WiFi for my nexus.
I'm trying to update from Villian 5.3 to 10.2. But keep getting E:corrupt file messages and E:verification failed. I followed the tutorial that's how I was able to do 5.3, but don't matter. How many times I download it 10.2 just keeps coming up with the same message when I try to flash it, usual the file it claims is corrupted is different for different downloads, never had this before with any flashing I've done.
I'm un-rooting my phone using OMJ's guide in the everything root related guide, and I'm getting a "Failed Flashing Process" error in RSD Lite.
I am running as admin, I have the correct drivers (I recently rooted...), I have the sbf in C: .... yet it fails.
The error says " Failed Flashing Process. Failed Flashing Process. Interface BP: Error flashing subscriber unit. Device API Error: 0xE0030009 Command: ADDR (0xE0231009); phone connected"
I am going to try flashing SPRecovery to see if I can at least get to a working point.
SPRecovery worked. It boots into 2.1 and has SPRecovery as the recovery. I still want to get it to stock, so I am going to try and download the stock sbf again (it doesn't have a checksum so I have no way of knowing if it is good or not...) .... here goes nothing!
I just had this problem and I've seen other people having the same issue. I found the solution, at least for me, so I thought I'd share it. I was trying to flash the SPrecovery spf file using RSD Lite, but it would fail immediately. I found someone else on another forum who discovered that the file had to be in the root of his C: drive for this to work. I gave it a shot and it worked with no problems. This seems really strange. I think he was running Vista. I'm running Vista 64-bit. I was already running RSD Lite as administrator, so that alone didn't help. Moving the file to the root of C:
So I have looked around xda etc. Cant find a simple answer (hoping there is). So long story I am on a rooted Evo. I was trying to flash cm6 via rom manager. I kept getting error 7's. So I found the PC36IMG.zip followed the directions. I am now in bootloader. Tried (many times) to run nandroid. But it gives me the error while flashing boot image for all 3 backups.
I've got the rooted 2.1, easy. I've got all the java and adk and what not I got the flash_image and recovery.img. The command prompts all work fine till the last command, (I've tried 2 different chain of commands both work until a certain point).
adb shell mount -o rw,remount /dev/block/mtdblock3 /system adb push recovery.img /sdcard adb push flash_image /system/bin adb shell chmod 755 /system/bin/flash_image adb shell flash_image recovery /sdcard/recovery.img (After this one it says it cannot find flash recovery or image, cant exactly remember.)
- Open the Terminal and copy and paste the following commands with the phone connected to your computer. - adb shell [hit enter] - su [hit enter] - flash_image recovery /sdcard/recovery-RA-eris-v1.6.2.img (once again not found but I believe I followed correctly) this the end of commands the first half worked fine.
I should have just left it as it was out of the box..So after attempting to install a custom rom (4.4.2 Play edition)my s4 is stuck at the Samsung I9505 boot screen. I wiped the 'Dalvik cache' 'System' and 'cache' partitions in TWRP as I was following along with a Youtube video (that didn't work). When I tried to flash the custom ROM it automatically said failed. After giving up and turning on the phone I found that I'm stuck at this screen.
Have I bricked the phone? $550 could have gone down the drain just like that. I don't want to touch it without any advice and make everything worse. My only hope now is that I've managed to wipe the original software and it has nothing to boot from.
Why did the ROM install fail in the first place? I had it copied on the SD card. It was zip file.I can still access TWRP just fine and my SD shows up with the custom ROM still there, it's just whenever I hit install it fails in under a second.
I rooted my phone using erisuser1's rooting for dummies method - this went off without a hitch, I followed the instructions to the T. I put several custom ROMs on my SD card (using the USB, and properly ejecting the phone as a drive) including KaosFroyo v37 and v38, CELBFroyo 3.6, PlainJaneT2_V2, and Vanilla_Tazz_19.I tried flashing each of them (following the wipe of the system info and the Dalvik cache) and all but the PlainJane got stuck in bootloops that lasted a long time. I waited anywhere from 15 minutes to a few hours, and none of the others ever loaded up. I'm fine using the PlainJane and happy to have the other features of root but am wondering if there's any advice or suggestions as to why none of the other ROMs worked for me?
Every time I flash a different Kernel my Evo goes into a boot loop. I am using RA-Recovery, and wiping Data/cahe and dalvik before flashing. I flashed a new ROM and was able to install Kernel one time, any more than that and the Boot loop starts, even if i flash the first kernel that did work it still loops on me. I was on Clockwork and changed over to RA, that did not help, tried both BFS and CFS and no change. Tried Kingx 8 and 9, netarchys 4.18 and 4.19. I flashed 3.28.651.1 then netarchy's 4.1.9 and it started the BL, then reflashed 3.28 and tried kingx 9 and it worked, I'm beginning to wonder if there is something with netarchy's kernels that my Evo doesnt care for? I should add that this time when wiping i only wiped cache and dalvik and left the data alone. I suppose the only real way to find the culprit is to test out all the variables.
I have an eris flashed with PB00IMG and I believe I have root access. I am able to remove apps through terminal. I cannot get the google maps to update. I have removed maps.apk, htcnavi.apk and com.google.android.maps.jar. I have removed these separately and all together. I have been able to get it to update before, but I reflashed the PB00IMG because I could not get youtube videos to play without the stock browser. I got the youtube videos working again but cannot remember how to get the maps to update again. I wanted to try flashing different roms. I have downloaded a couple, placed them on the sdcard, and booted but I cannot get them to boot.
i'm trying to root my (chinese) tablet (like title). i've used nanospic.ro page_id=12[/url] WM8850 RootBurner v1.1.0.
So i put files into sd and reboot tablet. After the text "root complete" i removed sdcard and my tablet opened. I knew immediately that I could not access the to settings cause the icon was passing and text becomed com.android.settings. when i try to open it, an error message. So i try another time to root device but it won't open itself.. i turn on it and remain on loading gif..
The terminal was mistakenly brick while I introduced changes to the file build.prop. Now the only way to turn on, is flashing the firmware again (putting the original file from fastboot does't work). I wanted to know how to transfer the firmware zip file to internal memory because the device is not recognized as FTP.
For the past 2 hours I have been searching this site and reading about Rooting and Flashing new ROM's etc. and I'm still having trouble. I downloaded Cyanogen 6.0.0 and when the phone re booted it got stuck at the Cyanogen boot animation screen, and when I pulled the Battery and rebooted in to recovery I was able to restore everything and now the phone works again.
So first off, how long should it take after downloading a new ROM to boot back up with the new ROM installed? And how can I save the ROM in to the SD card? And when I go to DL Cyanogen it asks which home application I should use and gives me ADWlauncher and Launcher 2 as options.
I am using a rooted verizon LG G2. I rooted the device with ioroot 25 and installed TWRP 126.96.36.199 using AutoRec. (AutoRec - KitKat Recovery Installer - xda-developers, Here's a forum if you're unfamiliar with AutoRec)
Whenever I try to flash Cyanogenmod 11, TWRP says the flash is successful. I then go to reboot the device and I'm stuck in a boot loop of LG's logo. During the flash, TWRP mentioned that no MD5 file was found, which may or may not be related to the issue I'm having. During the bootloop, I booted back into recovery using the keys on the back of the phone and restored Stock LG KitKat. I've tried using multiple versions of CM 11, nightlies and snapshots. I'm stuck using TWRP 188.8.131.52 because AutoRec is one of the only methods I've had success with when installing a custom recovery.
Actually I am in a deep trouble, I bought Micromax a90s a month ago , It is really a very good phone. I rooted it and was very happy but 1 day ago I was trying to add new fonts to it & It got bricked I don't have any backup.I have no sources to send it to service centre. how can I repair it myself, Unbrick ?