i had an issue updating from one CNA nightly to a newer one the other day, and was left with no option but to flash the original .sbf for my version of the phone & carrier etc. That worked fine, and i have a bootable stock phone, but when trying to install any rom, either through CWM recovery or fastboot, i get issues.
if i try through CWM the correct method, i get stuck on the Moto Dual Core screen forever, until i battery pull and have to sbf flash through RSD Lite again.
If i try through Fastboot, i get error Failed to process command flash: xxxxxxxxxx error (0x0003)
can anyone help please? i've been using various CM7/9 ROMS for months now, and cant deal with being stuck back on MotoBlur stock junk
many thanks in advance!
ishamm said:
i had an issue updating from one CNA nightly to a newer one the other day, and was left with no option but to flash the original .sbf for my version of the phone & carrier etc. That worked fine, and i have a bootable stock phone, but when trying to install any rom, either through CWM recovery or fastboot, i get issues.
if i try through CWM the correct method, i get stuck on the Moto Dual Core screen forever, until i battery pull and have to sbf flash through RSD Lite again.
If i try through Fastboot, i get error Failed to process command flash: xxxxxxxxxx error (0x0003)
can anyone help please? i've been using various CM7/9 ROMS for months now, and cant deal with being stuck back on MotoBlur stock junk
many thanks in advance!
Click to expand...
Click to collapse
Reflash the gingerbread pudding .sbf, you're bootloader isn't unlocked anymore.
Sent from my MB860 using xda premium
the sbf i flashed was from the pudding page, and i unlocked the bootloader again fine, have the unlock sign on the Moto boot logo, just cant get any further than that with ROMs anymore..
EDIT: i am also getting the issue when flashing any kernels,
I can flash a recovery through fastboot, which it says is successful, but when i try to boot into recovery i get failed to boot 2, entering RSD mode.
Related
logo_q1.jpg daw failed [BRICKED] please help
I flashed a GB ROM using odin mobile trying revert from ICS after I found out about the possible superbrick, when it rebooted, all I saw was logo_q1.jpg daw failed in green letters
I can get into recovery, and can only flash SGN_XX_OXA_KJ1_FACTORYFS, but same thing after it finishes.
PLEASE HELP!!!
ok i finally got the green jpg failed error to go by flashing Abyss kernel. but now it just gives me a yellow triangle and CWM, but CMW is unable as it is stuck in boot loop.
Use PC ODIN to flash a stock GB rom!! Put in PDA section of ODIN. Well, just follow instructions in Drketan's thread in Android Development section.
**PC ODIN calls for Download Mode, I assume you can get to it because you can get to recovery (download mode is Volume Down)**
BOOM
i was able to flash a stock rom and get it working, i was figured it out right before you posted.
thanks
now I have to fix the green logo_q1.jpg draw failed. but it doesnt boot into the rom
DJTJ said:
i was able to flash a stock rom and get it working, i was figured it out right before you posted.
thanks
now I have to fix the green logo_q1.jpg draw failed. but it doesnt boot into the rom
Click to expand...
Click to collapse
After you ODIN the stock GB rom it should boot up fine. If it doesn't, boot into recovery (on the STOCK GB) rom and wipe data and cache. This will ensure you are starting fresh and getting rid whatever that green logo fail is. I'm not sure what that is.
Hello y'all. I tried installling another ROM on my phone (was using Cyanogen 7 SDSL) but I think I messed up somewhere (bricked my phone).
So I followed the steps in the sticky (Flashing on KDZ with battery and SIM out). With this, I managed to boot the stock ROM, yet no logo and boot animation shows up.
When trying to flash something else with fastboot (tried different ones), it eithers give a "too many links" error, or gets stuck on waiting on device (happens when I use the AIO toolkit). Also sometimes KDZ pops up an error too, then says finished, or gets stuck while flashing.
Also worth of note, I can't even boot Recovery (I flash it successfully on fastboot, it just doesn't boot on phone).
I searched through the entire forum, googled my problems and tried EVERYTHING, yet I'm still stuck. Anyone care to help? Sorry if it's confusing.
TL;DR
-Tried flashing another ROM, bricked phone.
-Un-bricked it by following the sticky, boot stock 2.1 (tried alot of files; euro+fast, V20a, V20b, out.kdz, France20V...)
-When booting the phone, no logo/animation shows
-When flashing recovery, it doesn't work on phone.
-When flashing custom ROM through fastboot, it gives "too many links" error, then bricks phone.
-When flashing custom ROM through AIO toolkit, it freezes on "waiting for device"
P.S. I have all the drivers installed, I have tried with the "Android modem" devices enabled and disabled, I tried all modes on KDZ, I tried changing the USB ports (only 2 on the back of PC, tried both) and still no go.
Thanks in advance.
Use aio toolkit cmd version, bcoz gui has lots of bugs right now.
Sent from my LG-GT540 using xda app-developers app
Still no luck. No matter what I do, it either "bricks" the phone (only download mode works), or it gives the "too many links" error.
Sigh.
sargeta said:
Still no luck. No matter what I do, it either "bricks" the phone (only download mode works), or it gives the "too many links" error.
Sigh.
Click to expand...
Click to collapse
i've had similar error once...
try to flash other size bootloader (appsbl) via fastboot
Managed to flash CM6 2.2.1 Utopia (miroslav's I thinki). Any other ROM bricks the phone.
Also, no boot logo/animation at all. (Yes, as I said, tried flashing V20A/B and out.kdz numerous times).
once you have fastboot , do not flash via kdz again !
also, try to flash different bootloader (appsbl) sizes (example 180mb)
then flash recovery , and then try rom's , that are recovery made (backups)
Gi guys.
I have a problem. I want to install a Custom ROM on my Motorola Dey Mini (XT320) - TNBST_4_0A.1F.10RPS_flex_WE_Orange_Poland - using RSD Lite. I'm following the tutorial - running RSD Lite, opening the ROM file, turning my phone on into the recovery mode, connecting it to computer, clicking "Start" in RSD Lite. Then, unfortunately, the ROM isn't flashed The process is failed, there is an information about this:
"Failed flashing process. Failed flashing process. Unable to retrieve interface handle. (0x7027); phone connected"
What do I have to do to successfully flash my Motorola Defy Mini?
Please, help me!
Its not a custom rom and you must not boot into recovery. You must have your phone turned on normally and then click start. It will reboot to flash mode automatically.
Sh0m1 said:
Its not a custom rom and you must not boot into recovery. You must have your phone turned on normally and then click start. It will reboot to flash mode automatically.
Click to expand...
Click to collapse
I'm doing like you wrote and still the same...
Edit: All happy now, a change of pc solved the problem of not detecting the device!
Hi all! I have another challenge for you!
Right, I've got myself in a tizz with my Defy +. While updating between CM10.1 versions I found myself in a situation where I couldn't get past the boot animation. So I loaded the TWRP restore I had made prior to updating...
Except it wouldn't, instead it came up with 'Failed' each time I tried any of the TWRP backups I had created. So the next step was to wipe partitions and start flashing various ROMs until I found one what worked. Except they didn't work either. Eventually I thought the best idea would be to just turn the phone off and see where I was with booting.
So power on, boot logo, blue light, red light then... nothing. Just the boot logo static. Went into the custom bootloader to go into recovery again, nothing. Pressing Custom recovery simply loops back to the top bootloader screen.
Ok next step, flash .sbf and start from scratch. So into the Moto bootloader it is to plug in and flash except... it's no longer detected by my computer.
"Ok" I think, "We'll just flash files from the SD card after I use an external SD card reader.
Except now when I enter Moto recovery to flash the TWRP recovery I get:
-- Install /sdcard ...
Finding update package...
Opening update package...
Verifying update package...
E:failed to verify whole-file signature
E:signature verifiaion failed
Installation aborted
So to recap:
1) Tried to flash and update, failed
2) Tried to recover, recoveries wouldn't write (I think this is becaue I'd changed to EXT4 on /data and /cache and had forgotten to go back to EXT3 before trying to recover)
3) Tried to boot, epicly failed
4) Tried to flash .sbf, Defy+ won't appear in RSDLite 5.7 with latest driver
5) Tried to flash from SD card, sig verification failed
6) Googletastic for the last four days
Notes:
a) I CAN charge the Defy+ using the wall charger but I get '?' for the battery level indicator but...
b) In Cmod bootloader 2.1 (Which I can use a little) it shows the correct battery level
c) I /was/ getting some errors with not being able to mount /cache from the moto recovery but I've since used the cmod bootmenu 2.1 to set it back to ext3 and it's all happy now, those errors aren't appearing
d) Plugging in my Defy red lens I get W8 x64 detecting the correct portal drivers and such but when I go to moto bootloader this device also doesn't appear in RSDLite
e) Both devices prompt windows to install a Motorola Flash Interface driver in Device Manager when plugged in in moto bootloader mode and neither device appears in RSDLite despite the fact the program is running in Admin mode
f) Looking at the logs in bootloader, it appears that I might not have formatted anything from ext4 to 3, everything I select in the cmod bootmenu returns .E:Error in /system/... , (Result: Invalid arguement) , Done..
So at the moment I think I need to acheive one of the following:
1) Find a file that allows me to write any useful data to /system like a recovery or some of those bootmenu files that passes the signature verification
2) Find a way to troubleshoot RSDLite so I can actually flash .sbf and get out of this hellhole
Many regards!
Alexis
If your custom recovery is not working, then you cannot do anything other than flash an sbf(nothing except data and cache wipe can be done via stock recovery): this is due to the locked boot loader(recoveries cannot be simply flashed from the stock recovery as you're trying to do)
Sent from my MB526 using Tapatalk 2
Success (ish)!
Yes I swapped to a different machine and then upgraded the version of RSD Lite installed on it from 4.7 to 6.1.5
[URL="http://forum.gsmhosting.com/vbb/f166/rsdlite-6-0-mtk-patch20-rsd-lite-6-0-a-1545012/index2.html#post8988239"]http://forum.gsmhosting.com/vbb/f166/rsdlite-6-0-mtk-patch20-rsd-lite-6-0-a-1545012/index2.html#post8988239
And flashed the 'lower' of the two .sbf's from the links on this forum for the British variant. After a DEA1 error (Phone is dead, code corrupt and all the bad things) I managed to flash the file.
As of yet I've not managed to get out of the bootloop but I've not carried out the requisite steps as mentioned in the "So you think you've bricked your Defy/Defy+" thread.
Lessons learned:
1) Motorola drivers and RSD Lite are pennickety, you will probably need to mix them up in order to get them to behave properly
2) If all else fails, use a different computer
3) You will probably need to flash over and over, while making every effort to not muck them up. Be aware the efuse system only has limited uses before it's useless though...
My saga continues, from no USB support hopefully to a fully working device again
In the end switching PC then doing the factory reset from moto recovery let the phone boot, all standard but the dodgy USB stuff at the first post is what sent me away from the right track.
Hi there! I have this question which I'd love to have answered because I've been on this issue for around 2 days straight.
Long story short:
Tried to flash custom recovery using fastboot, didn't work because bootloader locked
Kept on trying the unlocker apps, none of them even installed fully (THIS WAS WHEN I WAS STILL ON LOLLIPOP)
Somehow, at some point, I just randomly rebooted and BOOM THERE WAS TWRP (Sorry, I don't remember how exactly I managed that. As far as I remember, I was only using fastboot and nothing else)
Flashed CM 14.1 unofficial, device gave an error message regarding boot.img (something like "could not load boot.img"
Used stock ROM to flash OTA Android 6.1
Now the Asus unlocker app downloads but on reboot it says "error: unlock fail !!!"
Obviously, fastboot is unable to flash a recovery right now. I tried ignoring the error message and rebooting to recovery to stop the device from loading the stock recovery again but the device still loads the stock recovery.
I'm really tired
P.S: NO, there is no Enable OEM option in my Developer Options menu and YES, I have all the drivers necessary.
Did you get anywhere with this? I have a similar problem except that I couldn't flash Android 6.1 because the vendor had flashed WW 5.0.2 on a CN phone without also updating the CN recovery to WW. So the update failed its consistency check.
I've got TWRP on there now, but can't unlock the bootloader in 5.0.2 - I think this is why TWRP can't flash anything. It can't see the update files, won't switch to external SD, etc. .
I also found and tried flashing a WW recovery but that didn't work either. I'm wondering now if I got the 615 software by mistake.