The screen reads;
Bootloader
30.04
Err: A5, 70, 00,00,23
Battery Ok
Ok to Program
Transfer Mode:
USB
Any advice?
Your answer is literally all over these forums, but all you need to do is download the sbf 2.3.32 from the mydroidworld forums
http://www.mydroidworld.com/forums/droid-x-discussion/
Then flash it...
^ Pretty much what he said, I had the same problem although VZW replaced my phone because for some reason at the exact same time mine failed the update, I lost network connectivity after I reflashed via RSD. VSW told me that somehow my signal radio got fried...
On DX number 4 since release so far heh.
Related
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.
I wanted to share this story since I've seen many threads saying it was OK and "Easy" to convert your Verizon Xoom to Wifi only...
My Verizon Xoom (with 4G), MZ602, is only rooted, and running CWM, but otherwise stock and running IMM76L. I wanted to try the Jellybean wifi update, figuring I'd seen many "GEDify your XOOM" postings, I thought I'd try..
Before I began, I copied what data I needed from the internal storage space to my laptop. I then booted into CWM and did a backup, just in case, as I've read you can restore your CWM backup to get back to where you were...
I fastboot flashed the MZ604 files, erased cache, etc, and booted up. Everything seemed fine, so I connected wifi, and pulled the first OTA update. It installed, but when finished it rebooted. That is where things went totally wrong... My Xoom would hang at the red M dual core screen. While fastboot and RSD modes worked, recovery did not. When trying to enter recovery, it appeared as if it was going to go in, but hung with the last line on the screen saying ODM Fuse: 1. I tried reflashing the MZ604 ROMs, same thing. So I tried flashing back to the MZ602 roms. Again, the same. Using either the fastboot files, or RSDLite & SBF files available.
I spent over a day searching, reading, and trying things trying to get back to recovery figuring I could just restore the backup I made via CWM and be ok. But all of the threads I read about fixing the stuck at M screen wanted you to boot into recovery, which of course my XOOM would hang on. I found threads (including this one -> HERE) referencing flashing a 1.35-everest.reflash.sbf via RSDLite to fix it. I couldn't find a working link!! ( finally found -> HERE ).
That Everest SBF was the key to getting past hanging on the Red M/Dual Core screen. Once using it, I was able to flash CWM, so I tried restoring my backup, but did not have 3G/4G radio. MEID and IMEI were reported as "unknown".
----------------------------------------
long story short... to get back working... including having the Xoom report the MEID, IMEI, Mobile Network info, 3G signal (not in a 4G area at the moment), on an MZ602 ROM I did the following...
1. used the fastboot files for HLK75D from Moto's site to flash my xoom.
2. Using RSDLite, flashed 1.35-everest.reflash.sbf (found -> HERE )
3. Follow P3's instructions at -> http://www.mydroidworld.com/topic/9179-motorola-xoom-322-recovery-images/#post106459
4. manually apply each OTA update via USB OTG cable. I booted between each update, skipped any setup, and went into settings to see if MEID/IMEI were still reported. I also did a factory reset between applying each update. NOTE: I imagine you can setup wifi and check for updates, but my xoom often reported "no update found" when trying to check via wifi)
I have not been able to confirm 3G/4G data works, as I do not subscribe to data for this device (and I haven't moved the SIM from my Thunderbolt over to the Xoom), BUT, at least the Xoom now reports MEID, IMEI, network as Verizon, and network type as eHRPD:13 as the network type.
[EDIT:] I have confirmed both 3G and 4G data are working today (Using the sim from my thunderbolt).[/EDIT]
----------------------------------------
So, now I'm back to working IMM76L, stock, nothing on it, and I haven't rooted it yet... Because I'm in the process of moving, I can't do any more work on my Xoom until possibly tomorrow (if I get free time during the work day).
What I'd like to try, now that I've got IMM76L on it is...
1. flash CWM and restore my backup again and see if it works, and if I have 3G/4G data.
[EDIT:] This was successful, and I have 3G/4G data, and back to where I was before I started[/EDIT]
2. depending on #1, get adventurous enough to try flashing the MZ604 ROM, and try Jellybean, and if it gets stuck on the red M, flashing the everest sbf file.
hello everyone
phone: i9505
I few weeks ago i rooted my phone (no problem) made a back up using rom manager on sdcard.
I decided to restore my phone with the back up i had made. Once it had finished restoring, I rebooted phone, go to unlock the screen and i am spammed with messages like: unfortunately process com.google.process.gapps has stopped and so on. Could not use phone because there was so many messages coming up!
my friend advised me to re-root it so i did, the problem didnt go away......
searched google found no answer to my problem
I thought un-rooting will solve the problem so I downloaded latest stock uk firmware (4.4.2) from sammobile, ran odin, put MD5 file in PDA, successfully un-rooted but when i turn my phone on now there is some writing on the top left corner it says (its pretty hard to make out it goes so fast):
REBOOT MODE = 0X684E39A6
POWER ON REASON = 0X1 (key power on)
CABLE: 0X00
DEBUG LEVEL MID
BOARD REV: 11
MSM CHIP REV 2
MSM HW ID: 0X71B0E1
BOOTLOADER VERSION: I9585XXEGNG8
BOOTLOADER AP SWAEV: 4
SPEED BIN: 2
ACPU PVS:2
SERIAL NUM:0X07FF9243
when i put my phone in dowload mode it says all this^ as well
after unrooting i went to setting and did a factory reset
ive tried rooting again, then unrooting but my phone doesnt seem fully unrooted? it says im on official, i also noticed i cant place widgets on screen
i tried google search but could not find an answer, mainly because i dont know what to search for but i know somethings not right
i just want my phone back to how it was, for now
if you need anymore info please let me know!
thanks in advanced!
Have you tried this guide to installing stock? I used this and it worked fine.
http://forum.xda-developers.com/showthread.php?t=2265477
There's a bit at the bottom about bootloops, I don't remember if I had one but I know I had to flash it anyway due to a problem I had after flashing the stock rom, so to be safe you should probably flash that after stock is flashed on as well.
lichking21st said:
Have you tried this guide to installing stock? I used this and it worked fine.
http://forum.xda-developers.com/showthread.php?t=2265477
There's a bit at the bottom about bootloops, I don't remember if I had one but I know I had to flash it anyway due to a problem I had after flashing the stock rom, so to be safe you should probably flash that after stock is flashed on as well.
Click to expand...
Click to collapse
thanks for the reply
ill try this and seee how it goes! i hope it gets it sorted
Hi guys
I have LTE sm-n9005 32gb from Holland (PHN).
As the Lollipop leaked i flashed it and got an error, hidden.ext4 FAILED!!
Of course phone rebooted and was showing the logo for a long time, so i just plugged the battery off, gave it a few seconds time and put it back.
Phone booted, was working but with glitches (bad reception and no 3G, only GSM or LTE).
I left it as is and now, when the Polish 5.0 was out so i flashed it. This time it went through and showed me PASS! sign, but phone is stuck at logo.
I can't enter recovery, i flashed TWRP and could not wipe because the TWRP failed to mount /data partition.
Then i though maybe i have partition problems, so i flashed MSM8974.pit but nothing changed.
Any idea how to recover the phone?
Solved
Cool that so many people tried to help, but anyway i managed to recover the phone by flashing this ROM
https://mega.co.nz/#!IVAykBTD!-LGw1U9ajSSLPylhdrGVxJzCY5B6_rW0-z3dXWJgSmM
Then on top of it i flashed the Polish Lollipop and it worked. The data from the phone is lost, but the phone itself works like before.
But there was one problem before, and it exists now too: the 3G or 4G networks are not supported. Phone fails to connect, but the GSM one works as expected good.
Did anyone have this problem with the note 3 (EU) ?
Very funny you are. What do you think, people are just sitting here waiting to answer your questions ? Patience.
But you are the 4 millionth person to have this issue, so there are definitely fixes out there, you just have to do some searching.
Hi All,
So, I have spent 2 days trying to get my Galaxy s8+ back to normal. However, I seem to only have made it worse. It all happened when I decided to change the /data partition from ext4 to another format and then back again to get the /data partition to mount in TWRP after flashing Pascal Rom. However when I rebooted, nothing worked, no boot up screen, no recovery, no life, but all I could get was download mode. It then must of froze up after another restart and I couldn't get anything for 12 hours or so.
The next step I tried once i got download mode again was to flash stock firmware for the G955F, I can't remember the version of this firmware, but I still had nothing change. So then i flashed the latest firmware from SamFirm's downloading client, which was G955FXXU2CRF7 - Australian Optus Branded Firmware (OPS). I was able to get as far as the "hello start screen" and then my phone restarted, it then tried to upgrade my system again, then started "erasing" and then it rebooted and I still had the same issue, nothing but download mode and still no recovery, it still wouldn't turn on. So I flashed the latest International/Unbranded Australian firmware (XSA) - G955FXXU3CRGH, still the same result. I now can't go back to the OPS version of firmware because I get the Check error with the bootloader (since it's a more recent version), so I can't go backwards. I also can only flash "Official Binaries" now. Oh and to make things worse, I read that Odin Option "Nand Erase" just erased user data, so I thought I might as well try it, and as a result, I now can't flash even the (XSA) firmware because of ODIN failing and I now have an "An Error has Occurred while updating the device software. Use the emergency recovery function in the smart switch PC Software.". I am a bloody idiot :good: . Oh, I have tried multiple versions of Both Samsung Kies & Smart Switch (Which both had the option for "recovery & initialisation"), however, I get a message that my device is unsupported after adding in my device model and S/N. I tried a PIT file and then found out it's now included in all the latest firmware img files.. so yeah lol. Fun times. Soooo I feel like I am out of Options, nothing I do is working. The worst of all this is my wife is not happy haha which means after years of tinkering with android phones (flashing custom ROMS, Kernels, Root Solutions, e.c.t ), this may be the end of the road for me if I can't fix this phone. I really hope this thread isn't true too : https://forum.xda-developers.com/galaxy-s8+/help/sm-g955fd-access-download-mode-t3748228
So Please, someone help me out if it is at all fixable even if it requires opening the phone up lol.
The stats i have on download mode are the following:
RMM State as Prenormal
OEM Lock: OFF
FRP Lock: OFF
CARRIER_ID: OPS (which is super weird because it only accepts XSA to be flashed :S )
Secure download: Enabled
System Status: Custom
Warranty Void: 1
Current Binary: Samsun Official
If you need more, just let me know.
Ok, quick update: I have got rid of the error that I mentioned. I managed to flash XSA firmware again, it went to the blue Andriod is updating the system screen, then started "erasing" then rebooted and nothing again, still only download mode available. Nothing happens when I try to turn it on or try recovery mode.
This firmware you mentioned XSA - G955FXXU3CRGH i would double check. As far as I know Australia doesn't have a version 3 bootloader yet whether unbranded.telstra or Optus.
Quick Update: Maybe Fixed now!
Even though no one has replied yet, as it's only been an hour or so. I just wanted to let anyone else know who is experiencing a similar issue in the future on how to possibly fix it.
This was a real nightmare, however quick disclaimer, I am not responsible for any damage incurred to your device/property by following my instructions.
So the way I have fixed it, is I flashed the AP file only (from the firmware zip i had downloaded from SamFirm) with "Auto Reboot" Off. When ODIN finished, I held the Vol Down + power button, to reset it. It gave me a blue "No Command" Screen, I then waited and it then went black and the recovery screen appeared. I cleared the cache, rebooted to bootloader, which it didn't turn back on, so I left it because I thought it was the same thing. Came back 10 mins later and turned it on (or hard restarted, can't remember) and it worked. It booted!
I did soon learn it looks like it was having a charging problem because it had no charge and kept telling me there was water in the port (even though it was dry), I restarted it again after putting it on a wireless charging pad and it is seeming fine so far with the USB charger. So big note to anyone in the future, that it could be possibly bugging out with charging as well if you can't get it back on. I did have the device tell me here and there the last two days that there was water in the port when it was off. So kinda weird.
I know this all sounds a little hocus pocus, superstitious almost, but hey, my phone is working, so maybe replicating my actions may just help lol. :cyclops:
spawnlives said:
This firmware you mentioned XSA - G955FXXU3CRGH i would double check. As far as I know Australia doesn't have a version 3 bootloader yet whether unbranded.telstra or Optus.
Click to expand...
Click to collapse
Oh right, well, I did hear that SamFirm is not supported anymore, as that's where that firmware came from. Maybe it's dishing out incorrect firmware now? Possible the structure of where ever it is getting its firmware from (pretty sure it's pulled from samsung) has possibly been altered?
Just for reference I use www.updato.com for downloading firmware it is usually up to date. No reference to the firmware you mentioned (not for Australia anyway)
The screenshot I took: Imgur link:
https://imgur.com/a/lqyzWW7
Interesting I'll keep a lookout for it. Still on nougat 7.0 (XSA) no plans to upgrade yet until some issues are fully resolved ( out of beta stage that is ).
spawnlives said:
Interesting I'll keep a lookout for it. Still on nougat 7.0 (XSA) no plans to upgrade yet until some issues are fully resolved ( out of beta stage that is ).
Click to expand...
Click to collapse
Yeah, it's seeming to work now, but my fast charge isn't working. However, my other oreo ROM didn't work with fast charge either. So i am unsure if it is my phone or an orio bug :/ lol
Well at least you got it working and not using as a door stop
that was really sad story man.....
spawnlives said:
Well at least you got it working and not using as a door stop
Click to expand...
Click to collapse
Yeah haha, so glad it's not a door stop haha