Att flipout, I tried flashing rom without Blur and have PASS. After that when I turn on my device I have:
critical error:
CC00
DBAD
after some seconds
Bootloader
91.10
Err: A5,90,56,00,22
I tried flashing other roms, but again have PASS.
After some flasing, battery of my flipout is low and I can't flash it again.
And now battery is NOT CHARGING.
Yeah, I'm getting the same thing. Tried flashing other ROMs, but have the same outcome. Not sure what else to do, except give up and move on.
Edit: After some intensive research over the past few hours, I've found the fix! The other SBF files are not signed for the AT&T Flipout, so they fail the signature check when booting up. I found the official AT&T Flipout SBF after a while, and flashed it. It worked! My Flipout booted on the first try.
Can't post links, but google "flipout mb511 at&t firmware". Mine was the first link to come up.
Hi,
a friend Brought me a Motorola Milestone 2 which had been sent to him, however it was asking me/him for a motoblur account, so I entered mine and it said name/password was incorrect, so I decided to flash it after many attempts to hard reset etc etc
used RSD Lite 4.7+patch and 5.6 with a few of the softwares found in the super firmwares thread but to no avail I got a "code group XX" verification failed and my screen shows "critical error DEA1"
I've tried many firmwares since then however none of the work
I can't get into "android recovery mode" as soon as I put the battery in, I get code corrupt battery ok to program etc etc
I have bootloader 70.13
don't know what firmware was on it, as I had no access to the system
what to do?
PS: I have read many threads about this and tried everything.
I have had a Defy+ for a year and in general it has run without issue. I recently had a problem with being unable to get a GPS fix and Motorola advised me to do a factory reset. This appeared to work in respect that I got my GPS fix back but my phone would randomly reboot. It seemed to reboot when the data signal was poor. Motorola said it was most likely an app. It wasn't because after another factory reset it kept rebooting without me installing any of my own apps. I gave up and have gone back to my old Defy which works fine (with the same SIM card I had in the Defy).
Tonight I decided to get my Defy+ back to it's original state to see if that made any difference as I had tinkered with a few of the system apk files. Having looked up on here I have installed RSD Lite, Motorola drivers, downloaded the UK retail 2.3.6 rom from here http://sbf.droid-developers.org/phone.php?device=28 and put the Defy+ in Bootloader mode. Running RSD Lite in administrator mode and with the SBF file renamed to Defy.sbf and in the PC root directory I get the following error log :
22:31:43, June 23, 2014
Line: 902
ERROR: The file selected is an invalid superfile.
Please enter in a valid superfile.
File: D:\GitProjects2\hdt_windows_flash\flash\code\flashdll\PST_FP_FlashFileIO.cpp
22:31:43, June 23, 2014
Line: 552
ERROR: The superfile specified does not exist
File: D:\GitProjects2\hdt_windows_flash\flash\code\flashdll\FlashHdlr.cpp
Device ID: 0
On the face of it the SBF file appears to be possibly invalid. But I can't see anywhere else to get it from.
It's ages since I tinkered with the Defy so I am a bit rusty on this. Anyone any ideas?
I'm facing Baseband Unknown and IMEI Null issue since around a month. Tried everything, but nothing fixed it. Here's the list of what I've tried:
http://forum.xda-developers.com/zenfone-5/help/zenfone-5-a500cg-zenfone-6-a600cg-t3354645
http://forum.xda-developers.com/showpost.php?p=66560381&postcount=60
http://forum.xda-developers.com/showpost.php?p=67032039&postcount=16
http://forum.xda-developers.com/zenfone-5/help/rewrite-imei-null-00049-zenfone-5-t3389046
Downgraded to JB, then upgrade to KK then LP (No fix). Downgraded back to KK (Currently on .54).
I also got help from @prathmesh pande and @paktepu both guys did a lot of help (Thank you guys! :good::good: ) but at the end problem is still same. I also tried installing RAW firmware via Intel Phone Flash Tool but still problem is same. This post proved a little helpful but at this command: sec_provision_v1.1.0.2.exe -c%COM% -i2 %IMEI1% %IMEI2% -u3 28943447 -u1 28943447 the CMD window gets stuck (blinking and blinking) and after around half an hour, shows error message. @paktepu asked me to try it on 32-bit system as the sec-provision file isn't compatible with 64-bit system. So I did, this time it game me the same error message instantly. Here's the log (added *** in place of original IMEI):
Code:
INPUT ARGUMENTS:
----------------
COMPORT = 3
IMEI1 = *******************
IMEI2 = ********************
unlock_val = 3
unlock_val = 1
----------------
unlock_code_test = 28943447
unlock_code_boot = 00000000
unlock_code_sec = 28943447
unlock_code_NO = 00000000
unlock_code_NS = 00000000
unlock_code_SP = 00000000
unlock_code_CP = 00000000
unlock_code_SM = 00000000
ATAT_load_ipicom_dll
SIGN_load_signmod_dll
ATAT_setup_interface (Comport=3)
ATAT_disable_powersave
ATAT_ipicom_send
> [email protected]
ATAT_ipicom_recv
- IPICOM_recv returned (-1) error. ### ERROR ###
- Expect OK: FAILED! ### ERROR ###
ATAT_disable_inputecho
ATAT_ipicom_send
> ate0
ATAT_ipicom_recv
- IPICOM_recv returned (-1) error. ### ERROR ###
- Expect OK: FAILED! ### ERROR ###
ATAT_code_verify (Id=3, Length=8, ...)
ATAT_ipicom_send
> [email protected]:code_verify(3,{48,48,48,48,48,48,48,48})
ATAT_ipicom_recv
- IPICOM_recv returned (-1) error. ### ERROR ###
ERROR: [email protected] data parse error! ### ERROR ###
- Expect OK: FAILED! ### ERROR ###
ATAT_close_interface
Library unloaded: "IPICOM.dll".
Library unloaded: "signing_module.dll".
So, basically I did almost everything but still there's no fix. If any of you guys have any different method to fix, please let me know, it'd be a huge help. Thanks in advance!
Probably it seems to be a hardware issue,u shud submit ur device to service center.
I can't suggest more becaus i never faced such issue.I am out of ideas now.Sorry
(I assumed u tried flashing Lollipop RAW FW too)
Hi,
Use my app Zenfone Assist to restore the Jelly Bean RAW Firmware, and after restoring the RAW firmware, DO NOT BOOT TO JELLY BEAN, install the stock Lollipop or CyanogenMod 13.1.
This steps fixed the IMEI for most of people that asked me help.
Okay. Now downloading these files. (As the internet is slow, it'd take me whole day and night to download these) Will report back tomorrow.
Yes, it was bundled with Debrick package.
is your phone already rooted ? usb debugging enabled ? grant root access ?
Yes. Everything except Bootloader Unlock.
Nope didn't worked for me
@dgadelha Unfortunately bro, still the same. I followed this procedure and your CM13.1 procedure very perfectly and even monitored every command. Each and every command finished with OKAY and FINISHED but at the end, on your CM13.1, Baseband and IMEI are still same.
Well, then my suggestion is: restore the RAW firmware, do a factory reset (to make your phone look unmodified), and send to an ASUS repair center, they can handle that.
If I may ask, how did you get this error in the first place?
That's disappointing. If I send the phone to Repair Center they'd take a lot of time, nearly a month and I can't afford a month without my phone. So what I'm gonna do now is use the phone until I finish with it then I'd send it to them. Anyways thanks for help.
I was on Big ROM then. The phone was in my pocket, I felt vibration. The phone re-booted. I didn't checked for any problems or causes then. After around half an hour I felt vibration again, this time I checked and there was no signal. IMEI null and Baseband Unknown.
Did you check BIG ROM user if they have same problem with you?
If you want to run the Rewrite Successfully, look at the baseband... if the baseband not null, it can be rewrited, just try again
i know you said you have tried everything, but i have a suggestion, if you want to try it, or you could've already tried it, but here my suggestion, you are on KK .54 now right? try jump to MM using RR rom directly without upgrading to LL and check if you got 0049 imei, if you can get that 0049, downgrade to LL n try rewrite imei. hope it helps, cause this helped me b4
@dgadelha your and @paktepu 's methods worked! Phone is up and running again! Thank you guys! Hats off to you devs, and to all!
Nice to see ur problem has been solved
Btw Did u sent ur fone to service center?Or any one of the methods worked for u?
Thats cool.
@prathmesh pande No coz I can't live a day without a Smartphone.
So, here's the Final Answer courtesy of @paktepu @dgadelha @prathmesh pande . If all the tools fail. Read this post. This guide by Douglas (I'd recommend you installing Lollipop instead of CM coz I got IMEI on LP, tried CM but no) may not get you IMEI and Baseband back. After this you'd get either the same or Generic IMEI. In case of generic IMEI, follow this nice guide to write IMEI and if the IMEI is still null, Switch off your phone and leave it for 2-3 hours (DO NOT PUT IT ON CHARGE), turn it back on, you'd probably get Generic 0049 IMEI (I got generic IMEI the same way as previously it was null), now you can successfully write the Original one with the same guide. If still you didn't get your phone fixed, contact devs not me coz they're the path-makers, I'm just a driver.
1 more thing! After all this, you may not get to connect with Wi-fi, so simply Root your phone with Zenfone Assist by Douglas, Install BusyBox and download Wifi MAC changer, Open the app, Write Original MAC Address in New MAC Address and Tap HARD CHANGE, done!
So my girlfriend's phone, a Huawei Y625-U51 after she took the battery (I suspect during an update but she doesn't know) got soft bricked, all I get when I turn the phone on is a DataBackup screen and multiple processes failure notifications.
I tried to wipe/factory reset but I'm still greeted by the same screen and errors.
I tried installing an update rom from the website and some I found online but I get an error saying: "cannot install this package over newer build" so I tried to edit the date on the build.prop file but then I get a signature error.
The phone is not rooted and I would prefer not to have to (but I really don't care that much).
Also the screen glass is cracked so they gave her the bull**** "no warranty because of damage" excuse.
Could someone please help?
Edit: Found a solution, flashed the system using some production line software or something, you may close the thread.
Can you help me? I have the same issue, what software did you use?
I need more information about your solution, please.
Enviado desde mi XT1097 mediante Tapatalk
Bump.
I used this tutorial and some files I found somewhere I don't remember:
Tutorial
still in it
I tried to flash the phone with ETS... still no sucess. I get an error @85% while flashing the huawei
Here's a pic of my actual error
***oi64.tinypic.com/2w23evp.jpg