My Canvas 2 A110 was hard bricked as I tried to install a custom ROM. So, I tried to flash stock ROM using SP Flash. I downloaded stock rom, opened SP Flash, selected first 5 checkboxes and recovery, chose recovery image, clicked download, connected phone. The red progressbar came to 100%, but then an error msg popped up (See attachment, I have circled the things I felt are important) saying "Failed to send sync data to DA in initialization stage!"
Related
The Problem:
When I select Clockwork Recovery Mod from the three button process, the phone reboots and the entire system gets a factory data reset.
What did I do wrong?
My mobile is rooted and running a Jelly Bean Rom. I did a Factory Data Reset from the system i.e. from within android not from Clockworkmod recovery menu and since then this problem has occured. It appears that factory data reset command is stuck somewhere in the boot.
Current Condition:
The Mobile is running perfectly fine without any problems. I can reboot and turn off the phone and it will load Android Jelly Bean Rom smoothly. The problem only happens when I try to access Clockworkmod recovery.
Solutions tried so far
I tried to reflash Clockworkmod image update from Mobile Uncle MKT tools, it rebooted the mobile and did a factory data reset of the system. The same thing happens no matter how many times I try.
I couldn't reflash Clockworkmod using rom manager as it does not recognize by device.
Was it working fine before?
Yes Clockworkmod was working absolutely perfect. I installed various roms from it and did backup of stock rom and even twice restored the stock rom.
Phone Specifications:
It is a local variant of a phone found in Germany going by the name of Mobistel Cynus T2 and as Micromax A110 Canvas 2 in India.
Would greatly appreciate any help.
You will be OK
Not psychic, but I think you loaded an incompatable version of CWM and then flashed, a buddy of mine just went through this, he didn't pay close enough attention or maybe its just some weird stuff in the universe-HA!
Ok, you are probably in recurring boot cycle, if you can get phone into boot mode, you know the combination of keys to be able to flash something!
Get to your computer and find the original OS that it came with out of the box, it will be a large download, it could be anywhere from 480 meg to darn near a gig.
Go get Odin 3.07 is the latest I think, anyway use Odin to flash the original OS. Start from out of the box fresh. It wouldn't hurt to stop by the play store after set up and get Triangle Away, it gets rid of the counter that is tripped when a custom rom is flashed.
Good Luck.
Fixed
1). Download the Stock Recovery Rom and CWM recovery Rom for Qmobile Noir A10 from here.
2). Download Mobile Uncle Tool from Play Store.
3). Rename the Stock Recovery Rom to "Recovery.img" and place it on the root of the SD Storage.
4). Open Mobile Uncle, grant it super user access and from its menu select Recovery Update.
5). Then select the Recovery.img (mentioned under the SD Card header), after which Mobile Uncle tool will prompt for a "Reboot in Recovery Mode" to which yes should be selected. If you have accidently selected "no" then you can select Reboot in Recovery from the main menu of the tool.
6). After the Reboot the mobile may not enter into Stock Recovery Mode and instead perform a Factory Data Erase of the android system so don't panic and repeat steps from 2-5. It happened with me therefore I am mentioning it here.
7). After you have successfully entered the stock recovery mode, reboot you mobile phone and let it load the Android Operating System.
8). Now rename the CWM Recovery Rom to "Recovery.img" and using it replace Stock Recovery Rom, mentioned in step 3, on the mobile's SD Card.
9). Open Mobile Uncle Tool again and repeat step no.5.
10). Upon reboot, your phone will be in CWM recovery mode.
Now do the robot dance and look like an idiot.
Have a Verizon Samsung Galaxy Note II (SCH-i605). Took the latest OTA update to VRUEMJ9. Have since rooted and installed SafeStrap and was happily running N3BULA ROM, when I decided to explore a bit and tried to flash Alliance ROM. Now I'm stuck on the Samsung boot screen and can go no further. I am able to access Android system recovery, but when I try to 'apply update from external storage' I get 'E:signature verication failed' message. Tried to flash to stock via Odin, but unsuccessful. Shows Added in Odin but nothing happens when I select the .pit file or the .tar file. This is a work issued phone, so any help to get up and running would be greatly appreciated!
Brantosapien said:
Have a Verizon Samsung Galaxy Note II (SCH-i605). Took the latest OTA update to VRUEMJ9. Have since rooted and installed SafeStrap and was happily running N3BULA ROM, when I decided to explore a bit and tried to flash Alliance ROM. Now I'm stuck on the Samsung boot screen and can go no further. I am able to access Android system recovery, but when I try to 'apply update from external storage' I get 'E:signature verication failed' message. Tried to flash to stock via Odin, but unsuccessful. Shows Added in Odin but nothing happens when I select the .pit file or the .tar file. This is a work issued phone, so any help to get up and running would be greatly appreciated!
Click to expand...
Click to collapse
Have you performed a "wipe data" option from the recovery after flashing the alliance ROM (it wipes your user data)?
Because I just visited the alliance ROM thread ( http://forum.xda-developers.com/showthread.php?t=2032447 and in the install instructions its mentioned so.
Better take a little time and properly read the install instructions during flashing..
Sent from my GT-I9070 using Tapatalk
dagger said:
Have you performed a "wipe data" option from the recovery after flashing the alliance ROM (it wipes your user data)?
Because I just visited the alliance ROM thread ( http://forum.xda-developers.com/showthread.php?t=2032447 and in the install instructions its mentioned so.
Better take a little time and properly read the install instructions during flashing..
Sent from my GT-I9070 using Tapatalk
Click to expand...
Click to collapse
I never had that option. I've flashed numerous ROMS before and am pretty meticulous when it comes to following instructions. It appeared to have a custom flash script which allowed me to pick what I did and didn't want to install. I tried to keep it mostly stock and when it completed, it automatically rebooted (didn't give me an option to 'wipe data') and now leaves me stuck on the Samsung Boot Screen. I was able to flash the .pit file via Odin, but keep getting a 'MD5 hash value is invalid' when I try to flash the .tar file.
Brantosapien said:
I never had that option. I've flashed numerous ROMS before and am pretty meticulous when it comes to following instructions. It appeared to have a custom flash script which allowed me to pick what I did and didn't want to install. I tried to keep it mostly stock and when it completed, it automatically rebooted (didn't give me an option to 'wipe data') and now leaves me stuck on the Samsung Boot Screen. I was able to flash the .pit file via Odin, but keep getting a 'MD5 hash value is invalid' when I try to flash the .tar file.
Click to expand...
Click to collapse
You should enter into recovery and then manually wipe data..
Also if that thing doesnt work, then have a look at this thread which explains how to go back to stock rom..
In addition,
A. Why doesnt Odin work?
Did you unextract the tar and pit from the rar/zip so that odin could recognize the files as suggested in dagger's link in section 1b step 2?
Did you install samsung drivers on your computer properly? You may use this toolkit for that
B. Rescue by CWM
Signature verification failed is caused (I think) by stock samsung recovery's choosiness, if you are sure you downloaded the zip correctly. What zip did you exactly try to flash?
So now, you may want to flash a cwm recovery or a kernel that contains cwm inside. Flashing usually uses adb using fastboot. Search "flashing a recovery image" or "flashing a kernel" where your chosen kernel should have cwm inside. cwm usually does not put out that signature verification error.
Remember:
You can access recovery mode through an app or by pressing a button combo when turning your phone on. Device specific.
Stock samsung recovery can wipe data.
CWM can also wipe data, and is the preferred installation method for most/all custom roms. And it can make a nandroid backup.
If ever you do choose to flash, you'll need the toolkit to install adb/fastboot drivers, but maybe since yours in locked bootloader the adb thing might not work.
Hope this helps
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.
I have a problem with my HTC 626g (MTK 65xx), I had a custom rom installed on it for several months, everything worked without a problem, but yesterday after the reset the phone fell into the bootloop, when trying to enter the TWRP phone turned on the system and not recovery, bumping into the bootloop.
I tried to flash the stock system through SP Flash Tool, there were no errors on the computer, everything went well and finally the message "Download Ok", but after turning on the phone it turned out that nothing was flashed, the phone tried to turn on the previous system and still had bootloo.
I decided to format the phone and then flash the stock system, it turned out that I still can not flash anything, that is - on the computer everything looks good, but the phone itself behaves as if I did not flash anything.
Currently the phone has no system, recovery, fastboot mode, etc., the phone has only Meta Mode when connected to the computer, SP Flash Tool still detects it, but I can not do anything, I tried to format the whole phone and then flash the preloader, I tried to flash the preloader itself, preloader with the system, preloader and then the rest of the system, etc., but I have nothing, after Meta Mode, the phone does not react to anything, and in SP Flash Tool I do not have any errors, each time it looks like a correct system flashing.
Can I still do anything with this phone?
I had bricked my phone (UleFone Note 8) when trying to install a GSI. Phone kept bootlooping.
However, have managed to get it to "communicate" with SP Flash Tool.
Have followed the instructions at https://androidmtk.com/flash-stock-rom-using-smart-phone-flash-tool
However, when I try to download the stock rom, it gives the error:
Error 3154: BROM ERROR: S_DA_SDMMC_WRITE_FAILED (3154)
everytime I try to download. As per instructions given at https://www.gizmoadvices.co...
I have tried using a different cable, different USB port, but no luck.
Guess my only option is to format before download, but I don't know how to correctly format. I really wouldn't want to end up messing the situation more by selecting any wrongly guessed parameters for format.
Would really appreciate some help on this, pls.