Hello everyone,
after a failed attempt to replace my Custom rom with a RUU rom (BIG MISTAKE - flashing procedure stopped at 5% with ERROR [294] : INVALID VENDOR), the phone stuck at the bootloader screen (and I think that this is normaI) but there is no way to enter the usb host mode (by holding camera + volume down + power) in order to re-install HSPL (gold card) and flash a Custom rom again. Seems like the Usb mode has been locked in some way. Is it normal?
Phone buttons are working (I tried to enter usb host mode before starting flashing attempt and I did it).
Here's some information from the bootloader screen:
http://i47.tinypic.com/2efrdx0.jpg
I really don't know what to do... is there a way to have my phone working again?
Thank you
Solved by myself. This forum section is dead.
Related
I was able to root my droid then I was going to try to unlock the boot loader so I could flash a custom ROM. Well the owner of the phone couldn't get it to unlock so he tried flashing CM using RSD.
It failed, it was stuck on this screen;
Invalid Flash Mode (S) (Flash failure)
0A.6C
To return to normal mode - first press power key to power down
Device is LOCKED, Status Code:0
Battery Low
Cannot Program
Connect USB
Data Cable
So I used this walkthrough to try and remedy the problem;
http://forum.xda-developers.com/showthread.php?t=1549625
Then I started getting this screen;
Invalid Flash Mode (S) (boot failure)
0A.6C
To return to normal mode - first press power key to power down
Device is LOCKED, Status Code:0
Battery Low
Cannot Program
Connect USB
Data Cable
Invalid CG OTV (CC: System): Invalid SP Data
Invalid CG Version (CC: System)
Invalid CG OTV (CC: System)
After a lot of reading, I found out I'd need a factory cable to remedy the situation. I believe the phone is wiped and can't boot into an OS and that is why it is getting stuck. So I used the following links to build my own;
http://www.droidforums.net/forum/droid-labs/146492-how-why-make-your-own-motorola-factory-cable.html
http://forum.xda-developers.com/showthread.php?t=1077414
After completing the cable and plugging it in I am now getting this screen;
AP Fastboot Flash Mode (S) (Flash Failure)
0A.66
Device is LOCKED. Status Code: 0
Battery OK
OK to Program
Connect USB
Data Cable
At this point I believe I fixed his problem, keep in mind, I'm coming into this process after it got stuck in the fastboot loop. So I start trying to use the following link to unlock the bootloader so I can try to flash back to stock(which by the way, I can't for the life of me find a stock ROM to flash).
I am using this link https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-b
I installed the latest Motorola drivers, I then installed Android SDK tools through the command prompt, I am now trying to get the device ID of the phone so I can unlock it and flash a ROM.
Even though I installed the Moto drivers, my computer isn't detecting the device, it is coming up as unknown in the device manager, I was going to manually assign the drivers to the USB device but I can't find the 32bit drivers to do that and what I downloaded from MOTO is an .exe that installs, I'm assuming several drivers for different devices.
Now I went into the command prompt to see if fastboot.exe can see the device plugged in, because prior to this fastboot problem his computer would at least show his IMEI even though he couldn't get it to display the unlock data.
I'm not getting anything, I'm guessing the jump to PIN 1 to 4 is correct but it doesn't know it's plugged into a computer? Even though my computer knows SOMETHING is plugged in. I'm lost, rooting and building ROMS for my Samsung devices was so much easier.
C:\Windows\system32>cd C:\Users\mk1daily\Desktop\androidsdk\adt-bundle-windows-x
86-20130219
C:\Users\mk1daily\Desktop\androidsdk\adt-bundle-windows-x86-20130219>"SDK Manage
r.exe"
C:\Users\mk1daily\Desktop\androidsdk\adt-bundle-windows-x86-20130219>cd C:\Users
\mk1daily\Desktop\androidsdk\adt-bundle-windows-x86-20130219\sdk\platform-tools
C:\Users\mk1daily\Desktop\androidsdk\adt-bundle-windows-x86-20130219\sdk\platfor
m-tools>fastboot devices
C:\Users\mk1daily\Desktop\androidsdk\adt-bundle-windows-x86-20130219\sdk\platfor
m-tools>fastboot.exe devices
AP Fastboot Flash Mode (S) (Flash Failure)
0A.66
Device is LOCKED. Status Code: 0
Click to expand...
Click to collapse
I have the same problem except that the battery is depleted. Any help would be greatly appreciated!
Great Gizmos said:
I have the same problem except that the battery is depleted. Any help would be greatly appreciated!
Click to expand...
Click to collapse
You will need to build a factory cable using the links I posted or buy a factory cable. They are $10 on eBay. The factory cable bypasses looking for a battery and will let you flash a rom. I get the "Battery OK, OK to Program" on my phone but it isn't showing up on my computer, that's my issue.
Try THis
If you are having trouble changing the battery while stuck at the Fash Failure Screen
Try this - Plug in the phone to a AC outlet. While at the Flash Failure screen, Hold down the Volume Up and Power button at the same time to turn off the phone. After the phone flashes (turns off), let go of the buttons and then quickly hold down both the up and down buttoms and the power button. A new menu will appear, with many different options (boot options). Select [Normal Powerup]. this will try to boot up the phone, notice it is low on battery, and start charging. IT will change to the screen with a outline of a battery being charged.
Hope this helps
Eighthourblink said:
If you are having trouble changing the battery while stuck at the Fash Failure Screen
Try this - Plug in the phone to a AC outlet. While at the Flash Failure screen, Hold down the Volume Up and Power button at the same time to turn off the phone. After the phone flashes (turns off), let go of the buttons and then quickly hold down both the up and down buttoms and the power button. A new menu will appear, with many different options (boot options). Select [Normal Powerup]. this will try to boot up the phone, notice it is low on battery, and start charging. IT will change to the screen with a outline of a battery being charged.
Hope this helps
Click to expand...
Click to collapse
^^Not my problem at all.
So I bought the factory cable, it came in today and the device registers on my computer as MOT Single ADB Interface.
I also get this when I check for devices using command.
C:\Users\Josh\Desktop\androidsdk\sdk\platform-tools>fastboot.exe devices
01547AE90900B014 fastboot
I still can't get this command to work;
C:\Users\Josh\Desktop\androidsdk\sdk\platform-tools>fastboot.exe oem get_unlock_
data
...
FAILED (remote: unsupported command)
finished. total time: 0.006s
I tried flashing the XML file that I believe is stock and it fails; I attached it as rsdscreen.jpg
I'm completely lost, hoping someone can shed some light. At this point, I don't even care if it is a stock ROM or a custom ROM, I just want something that works.
Phone fixed
I FIXED MY PROBLEM!!
I bought the factory cable on eBay and rebooted into fastboot mode.
Like for cable;
Can't post link because I'm a new user, if you want the link PM me.
Then I downloaded Matt Groff's Utility here;
Can't post link because I'm a new user, if you want the link PM me.
Followed the instructions, got the phone back to stock ICS
Phone had to be wiped using his utility but I don't care, phone is unbricked and all my pictures and stuff are on the SD card anyways. Kudos to Matt Groff.
I bricked my MT6577-based phone. I ran an app which re-partitions the drive, and this stopped the phone from booting -- the initial boot splash screen appears (in this case an Android icon), but it doesn't get to the point where it loads the OS (which would be represented by an Android icon where the droid's eyes and 'jetpack' light up).
I have placed the phone in recovery mode (power+vol up), and connected this to my PC (Windows 7). The PC does not recognise the phone and flags up an "unknown device" (code 43), so I cannot do anything with the flash tool or MTK tools.
I'm assuming that the original ROM is still intact, but can anyone confirm: is this phone recoverable? I should point out that it appears not to be possible to get a copy of the stock ROM for this device, I have searched at length with no success.
If it's dead without the ROM, a single line to the effect will put my mind at rest at least
Reinstall the drivers and then connect your phone in recovery mode
Use yuweng's ctr recovery porting tool and get the custom recovery
Then in wipe menu, wipe data and emmc partition then try
Otherwise you'll need the stock rom to he flashed by flashtool
Press thanks :good: if I've helped :highfive:
Hi, i ****ed up yesterday night.
I have a Honor 7 which was rooted with TWRP. I tried to unroot it and go back to stock recovery to be able to update from 5.1 to 6.0 MM.
So i flashed with the stock recovery, but when the phone turned back on, recovery was broke.
Now i can't neither go into recovery mode or fastboot mode, so i can't flash anything anymore.
When i do the buttons combination to enter in recovery, i'm in rescue mode saying "func no11 (recovery image)
The phone is still able to boot on stock B140, but enable usb debug doesn't change anything.
I don't know if anyone got a solution or has the problem before, i've been looking into it all night long without success, i hope it's not a permanent brick
Thanks for reading me, and sorry for my english
Turn off phone, connect phone to pc then immediately after that hold power and vol down. You should be able to boot into fastboot?
Sadly it's not working. Looks like recovery mode and fastboot mode have been erased or something, my phone can only boot on Android, nothing else, so i basically can't root it/update/install recovery :/
Try to factory reset it.
If that doesn't work, let it completely discharge until it doesn't turn on. Charge it and then try to enter bootloader.
Can you enter eRecovery?
Hi, thanks for your reply
I can't enter in erecovery/recovery, and when i try to enter in the bootloader, instead of having "fastboot and rescue mode", i only have "rescue mode" with error 11 (no recovery image) then error 2.
USB debug is enabled, but my computer doesn't detect my phone in any way
Edit: The exact errors i have are:
Error!
Func NO: 11 (recovery image)
Error NO: 2 (load failed!)
Flash the stock recovery.img belongs to your current rom with multi-tool. Probably it'll be fixed.
@smbtirael to enter into bootloader mode just press and hold Vol Down button and simultaneously connect the phone to PC, if your PC is not detecting your device try installind Google USB drivers via SDK. If you get in bootloader mode then you know how to flash a recovery.
Hello!
My phone, Acer Liquid Z630s, recently had a problem and ended up shutting off as soon as it boots up. I turn it on, the Acer powered by Android white screen shows up then immediately shuts off. What was the problem here?
I couldn't access recovery mode either because it would also show up the same thing above then shut off immediately before it can even reach the recovery mode menu. But I could plug it in directly into download mode through SP Flash Tools because the phone vibrates when I hold down the volume up + power buttons (aka the recovery mode combination which was I think also the download mode combination). I downloaded the correct stock ROM off the Acer website (MT6753) and flashed it. The ROM was successfully flashed. But when I turned it on the screen lit up but it was just a blank black screen. It was lit up, but it was just dark black. I tried to wipe the system and flash the ROM again and at the end of the process, an error message appeared and I looked up the error code and this was exactly it:
"Error 6104
Message: BROM ERROR: S_SECURITY_SECURE_USB_DL_DA_RETURN_INVALID_TYPE (6104), MSP ERROR CODE : 0X00
Meaning: Wrong flash settings or firmware
Solution:
Ensure you set the correct Download-Agent in SP flash tool and are using a firmware for your exact model
Go to Options > Option > Connection > USB Speed > Full Speed
Go to Options > Option > Download > Untick DA DL All with Checksum"
I did what the solution told me, and as I tried to flash the ROM again, but I couldn't turn on my phone anymore. The volume up + power button combination no longer produces a vibration, and when I plug it into my computer it gets detected as a MediaTek USB Port (COM6) but SP Flash Tools no longer detects my phone and gives off this error:
"Error 0x13BE
Message: S_DL_GET_DRAM_SETTING_FAIL (0x13BE)
Meaning: The firmware you're trying to flash is either not compatible with your device or you have selected the wrong flashing settings
Solution:
Ensure that the file(s) you're trying to flash are actually for your exact phone model
Ensure you tick the boxes for only the files present in the ROM you're about to flash"
I don't know what to do at this point. Is it beyond salvation? But my phone still gets detected by my computer and it still produces the sound when you connect a device through the USB ports. Help me please.
Thank you in advance.
Hi , flash this firmware and in Sp Flash Tool set to Download only !!! When you Do Format + Download you lose your imei !
https://drive.google.com/uc?id=12CdmQaP8wi52RZO4jvjSikTWi2l4I1ZN&export=download
Teddy Lo said:
Hi , flash this firmware and in Sp Flash Tool set to Download only !!! When you Do Format + Download you lose your imei !
https://drive.google.com/uc?id=12CdmQaP8wi52RZO4jvjSikTWi2l4I1ZN&export=download
Click to expand...
Click to collapse
Hi there Teddy. Maybe you could help me. I was actually trying to make use of the same thing. SPFT. i flashed the stock rom. i tried rebooting it. seems that it has been bricked. I am using Starmobile Up Prime.
lexpizarro said:
Hi there Teddy. Maybe you could help me. I was actually trying to make use of the same thing. SPFT. i flashed the stock rom. i tried rebooting it. seems that it has been bricked. I am using Starmobile Up Prime.
Click to expand...
Click to collapse
Hi, If you flashed right stock firmware for your device correctly, your device it should not be bricked so I thing your flash file are not good.
Explain me what did you tried and which file you flashed?
Hello guys, I hope you all are doing fine,
So I have a bricked Nokia 3.1 Plus (When I try to boot I recieve "Your phone is corrupt, it cannot be trusted and will not boot) after a failed downgrade attempt from Android 10 to Android 9. I tried to access the recovery mode (Pressing Power Button+ Vol. Up while plugged in USB) But no luck.
OEM locked, USB debugging off and bootloader is Locked. Is there any way to fix that?
Your help is much appreciated!
hello
I have the same problem
please help