Hello,
I received a used Vega Sky a800s (IM-A800s LTE) Korean device which had stock jb 4.1.2. It had issues like battery draining fast and getting damn hot while using network (3g, WiFi). I thought a lightweight custom ROM would solve these problems. So I rooted it using frama root application and flashed a downloaded compatible CWM.img 6.x with Rashr-flash tool application. All went smoothly and I got root access and could boot to CWM. I made a back up of my device, booted to android and copied the backup to my SD card. Then I again booted to CWM, erased everything and flashed a MiUi JB ROM I have downloaded. The ROM has been made for a800s which is my device. Flashing had no problem everything went smoothly no error message. But then the phone is not booting it shows error Messene "Kernal Panic" in a blue background. I can't boot to CWM but only fastboot mode can be activated. I tried all possible solutions but still my device is bricked.
1) I tried to flash backed up boot.IMG through fastboot. It gave error "remote error (unknown reason).
2) I downloaded the latest stock firmware in .bnix format to tried flashing with their IE flash method. It gives an error message with some symbols but I can't understand it.
3) I tried various other things but failed.
I think the problem is in boot partition which I can't access or flash.
Please help me to get my device back to life?
Thank you in advance.
Solved by myself
Finally I found a way HURRAY... My VEGA SKY is back to life..
Here I'll post what I did so someone in the same boat may be helped.
? If you accidentally bricked your phone by some error of flashing or whatever, you can get the brick back to life by this method. But you should have the followings to do that.
01. Your device must support fastboot and it should be able to boot to fastboot.
02. You have the drivers installed in your PC and be able to connect your device.
03. You should have the backup of your phone copied to PC. (Else you should have a backup in phone storage and the particular recovery (CWM in my case) in .IMG format saved in your PC.
OK. This is what I did.
01. Connect the device to PC in fastboot mode.
02. Run this command to check whether itbis connected properly.
fastboot devices
It will show your device as 'a number' and mode as 'fastboot'
03. Copy recovery.img (from backup or elsewhere) to the same folder as your fastboot folder.
04. Run this command.
fastboot boot recovery.IMG
(recovery.img should be the name of your recovery)
This will send the recovery to devices RAM and farce it to boot using this recovery.
Device will boot into recovery (CWM in my case)
Now you can restore through your device as usual.
That's it.?
Glad you got it solved. I'll close this thread.
Related
9020 – Eur model. Was 2.3.3, but upgraded to 2.3.4 after one day.
I followed the Unlockr guide, and followed the following, before deviating!!Can someone help me recover from this recover from this?
Bootloader successfully unlocked
Then it all went pear shaped!!
IV. Flash a Custom Recovery Image
1. Download the custom recovery image and save it to your computer: DONE
ClockworkMod Recovery for Nexus S
2. Copy the recovery.img file inside the tools folder of the sdk (so it is in the same folder as fastboot.exe) DONE
3. Then in the command prompt that should still be open, type the following with hitting enter at the end of
each line:
fastboot flash recovery recovery.img DONE
This is where for some insane reason (moment of madness) I deviated and don’t know how to get out of it. I rebooted and it went into clockwork mod. I couldn’t get out of it so I thought I would flash a backed up nanroid rom (2.3.1) which I down loaded. Big mistake, as it boots then freezes after 1minute.
I then booted into recovery (clockwork mod) and wiped cache, and pretty much everything else. Now the phone hangs on the google start page, recovery (clockwork mod) says there’s misc missing, cache missing etc....Cant flash any new rom. Can get to recovery but that’s about it.
I need some help to fix it!
mittu1 said:
9020 – Eur model. Was 2.3.3, but upgraded to 2.3.4 after one day.
I followed the Unlockr guide, and followed the following, before deviating!!Can someone help me recover from this recover from this?
Bootloader successfully unlocked
Then it all went pear shaped!!
IV. Flash a Custom Recovery Image
1. Download the custom recovery image and save it to your computer: DONE
ClockworkMod Recovery for Nexus S
2. Copy the recovery.img file inside the tools folder of the sdk (so it is in the same folder as fastboot.exe) DONE
3. Then in the command prompt that should still be open, type the following with hitting enter at the end of
each line:
fastboot flash recovery recovery.img DONE
This is where for some insane reason (moment of madness) I deviated and don’t know how to get out of it. I rebooted and it went into clockwork mod. I couldn’t get out of it so I thought I would flash a backed up nanroid rom (2.3.1) which I down loaded. Big mistake, as it boots then freezes after 1minute.
I then booted into recovery (clockwork mod) and wiped cache, and pretty much everything else. Now the phone hangs on the google start page, recovery (clockwork mod) says there’s misc missing, cache missing etc....Cant flash any new rom. Can get to recovery but that’s about it.
I need some help to fix it!
Click to expand...
Click to collapse
If you have recovery, then you are fine. Just flash a rom. Flash the stock rom if you want. Any rom. Then you should be fine.
Sorted!! The solution was found here:
http://forum.xda-developers.com/archive/index.php/t-992114.html
New ROM up and running, no issues so far.
I have the Nexus S from Telus.
It was rooted, unlocked, running CM7. However I've been having issues with it freezing and decided I want to go back to the stock rom.
I ended up downloading what I thought was stock ROM for my phone (Stock GRH78 Nandroid Backup in this Tutorial http://forum.xda-developers.com/showthread.php?t=884093) however after it flashed my phone, I ended up with a phone which was essentially stuck in Airplane mode, would not connect to Telus. I'm guessing that it has the wrong radio for my phone/carrier?
So then I ended up finding a zip file someone posted Stock-GRJ22-i9020A-unsigned which should have worked, I ended up flashing the zip file from recovery.
It said it installed fine. Rebooted, and now the phone just cycles the Samsung Loading screen endlessly.
I tried to go back to recovery, and it gives me yellow triangle with !.
Is there any way to flash the recovery image back to the phone?
I plug the phone in and the PC won't recognize a device.
I installed the Android SDK
Ran the command adb devices, no devices attached to the PC.
I tried fastboot devices - blank
I don't know how I'll be able to get files back onto the phone SD Card for flashing etc...
I had the exact problem two days ago...flashed an image that jacked my phone up. Wouldn't boot past the google logo. Sat there indefinitely.
Read this thread and see if you can get it work. In a nutshell, you need the PDA net drivers installed. Since PDA net can't install the app on your phone (because it's not booted into an OS) leave the install program in limbo and voila, fast boot will work. From there, push the recovery.img (google Clockworkmod recovery image), boot into recovery and you are off to the races.
This is, of course, assuming you already have a ROM image on your internal SD card you can flash to get back up and running. I'm not sure how to install a .zip image ROM if you can't gain access to your SD card.
http://forum.xda-developers.com/showthread.php?t=1303522
Good luck, I know the feeling. It blows.
Ah, just found out how to install a file on a phone that won't boot.
You do need to flash CWM recovery first though.
http://forum.xda-developers.com/showpost.php?p=18437305&postcount=2
Good news! I tried a factory reset/data wipe and rebooted the phone.
It doesn't hang anymore, all functions restored and the phone is working on Telus again!
I guess I had to format data, clear cache, before the flash of the rom.
So relieved.
Issue has been solved!
OP Junior MemberThanks: 0
2 posts Joined: Sep 2014
I have a Motog 1040 tx.
I have unlocked the boot loader through Motorola's website
I have SuperSU installed. I have verified using an app the phone is rooted.
This my problem installing clockword mod...
When I go through the commands in terminal manager. It says recovery. IMG not found.
I've downloaded clockwordmod recovery peregrine for my phone model and renamed
it recovery.IMG and placed it in the sdcard memory card root.
I've tried placing flash image in my sdcard root as well and used that method as well.
Anyone know what I'm doing wrong? The sd card is listed as sdcard1 on my device. I've also noticed that there is an emulated sdcard listed.
You can flash recovery in fastboot mode by using the command fastboot flash recovery nameoffile.img
How do I go about doing that?
Make sure the phone is not connected to a USB cable. Press and hold both volume buttons, press and hold power for a few seconds, release all buttons and you should be in fastboot mode.
What do I do once in fastboot mode? Where do I enter the command and where do I place the recovery.img
Have a look here: http://forum.xda-developers.com/showthread.php?t=2577043
I need confirmation that you've placed adb and fastboot in the platform tools folder?
Fastboot doesn't work in command prompt. Is this due to windows 8.1 64 bit...?
Fastboot and mfastboot should work in Win7 by installing drivers.
Win8 is a little trickier: http://forums.team-nocturnal.com/index.php/topic/1362-how-to-adb-fastboot-in-windows-xp-7-81-10/
OK... So I got fastboot working. I flashed clockwordmod recovery peregrine....I flashed clockwordmod mod recovery no touch.... I've flashed twrp...... Successfully.....they're the right version for my phone. Even though I've sucesssfully flashed .... My recovery is still stock. What am I doing wrong if it is saying I've successfully flashed the recovery IMG though it doesn't change?
Very good
deltadiesel said:
OK... So I got fastboot working. I flashed clockwordmod recovery peregrine....I flashed clockwordmod mod recovery no touch.... I've flashed twrp...... Successfully.....they're the right version for my phone. Even though I've sucesssfully flashed .... My recovery is still stock. What am I doing wrong if it is saying I've successfully flashed the recovery IMG though it doesn't change?
Click to expand...
Click to collapse
After it flashes successfully, disconnect the USB cable, and boot into recovery using the volume buttons.
audit13 said:
After it flashes successfully, disconnect the USB cable, and boot into recovery using the volume buttons.
Click to expand...
Click to collapse
Awesome it worked. Here's my other issue now though. Because I edited a file and inputted a string incorrectly in the root folder I had to install my stock ROM. Since reinstalling the stock ROM I have next to no memory left on my device. When I used mfastboot I did not clearvuser data so I wouldn't loose everything on my phone. What can I do about this. Will installing the custom ROM for my device clear this up?
I don't think a custom ROM is going to help you get back your memory.
Install Titanium backup. Backup your apps and data, do a full wipe of data, cache, and Dalvik and check memory usage. If that doesn't help, do a full wipe of everything, install the ROM, and restore from your Titanium backup. Just make sure to save your titanium backup folder to your PC before doing the full system wipe.
Backstory: I tried to load Cyanogenmod on my phone; but first I had to load TWRP recovery in order to get to load it. This is where the issue came; I decided to go the easy route and attempted to install it through Flashify (an app on the Google Play store); upon restarting my phone; it was bricked. I went into EVERYTHING, when I tried to go into recovery it would just send me through the bootloop and then send me to AP Fastboot.
Confused, I called Motorola; and was notified and Flashify had removed my prevoius recovery and failed to but TWRP resulting in this.
Issue: So what I did is I got the CWM recovery specific for my phone (XT926) and went into ADB fastboot and typed "fastboot flash cwm.img", from my ADB folder of course. Then when I booted into recovery, nothing happened; it would just send me through the bootloop again. Please help.
angrygamer1023 said:
Backstory: I tried to load Cyanogenmod on my phone; but first I had to load TWRP recovery in order to get to load it. This is where the issue came; I decided to go the easy route and attempted to install it through Flashify (an app on the Google Play store); upon restarting my phone; it was bricked. I went into EVERYTHING, when I tried to go into recovery it would just send me through the bootloop and then send me to AP Fastboot.
Confused, I called Motorola; and was notified and Flashify had removed my prevoius recovery and failed to but TWRP resulting in this.
Issue: So what I did is I got the CWM recovery specific for my phone (XT926) and went into ADB fastboot and typed "fastboot flash cwm.img", from my ADB folder of course. Then when I booted into recovery, nothing happened; it would just send me through the bootloop again. Please help.
Click to expand...
Click to collapse
Try another recovery / another version. Did the trick for me and you have nothing to lose
I have 2 XT925s. I bricked one to the point that I could boot to fastboot but could not even get into stock recovery. I was running stock 4.4.2.
I did the following.
I got the DROID_RAZR_HD_Utility_1.41. I used the TWRP 2.7.1.0 in that utility specifically for XT925.
I used fastboot to manually flash TWRP into the recovery partition.
DO NOT reboot past boot menu. Right after flashing, boot into recovery. That should give you TWRP.
I used TWRP to Install CM11 snapshot. I had to manually flash into the modem partition, the modem file also obtained from the above utility. You will need to flash in gapps for 4.4.2.
That recovered the bricked phone.
Of note, I was able to flash TWRP in the other phone. Backed it up. Transfered the backed up OEM ROM into the phone running CM. And get it to run stock ROM.
I now have one running CM11, and one running stock 4.4.2. I'm just comparing battery life. I've noticed CM11 has a smaller memory footprint than stock 4.4.2.
Cheers
did not work for me anywhere to be found stock 4.4.2 recovery img for 926?
Hello!
I wanted to update my oneplus 8 from 11.0.4.4 to newest version. OTA was not working idk why. I had magisk in place and I patched magisk to second partition or something like that [I dont remember how it was called] - I'm sure this is the reason of the problems. I turned off devices and wanted to boot into recovery, but suddenly it boot into Qualcomm crash dump mode with message: Attempted to kill init! exitcode: 0x00007f00 do_exit - that's all. I can't boot the system, I can;t boot into recover, I flashed patched boot, I flashed recovery - none of these works. Fastboot is present and recognized by PC.
First question can I do some backup through fastboot? To be honest I was not prepared for such problems. APKs are not even such a problem I care more about photos, documents and other data.
Can I flash some rom and restore phone back to life without wiping my personal data?
Please can you help me? I tried with some tutorials, but no success...
Maybe an idea would be to load TWRP recovery and then do backup, but how to boot into recovery when even after flashign recovery or booting via fastboot it enters in qualcoom crash dump mode. Something must be corrupted, but is it possible to fix some partition just in order to flash recovery to do backup of the files?
Okay I managed to get back to normal - since like I mentioned i patched the magisk into second slot, then probably this corrupted something. What has helped me is this: fastboot --set-active=b
It was not working via powershell I had to launch CMD and then it worked I switched slot to "b" and phone booted normally.
Hi, I'm facing the same problem but probably not for the same cause.
I'm right now on PE12 (with PE recovery) and wanna install TWRP recovery to then move on another A12 based ROM (Evox).
Basically my goal is to replace PE recovery with TWRP. So when trying to install twrp after downloading the ZIP file onto the phone, when I fastboot the img file, it sends me to the crash Dump mode.
How can I fix this? please note I have no issue booting to the main OS.