Related
Hi,
My phone boots until the Motorola Logo (M in a red point) but doesn't do anything else. And every 5 minutes, it restarts and stops at the same place. No animation, just stops like that, a rock with a red point ...
My phone is a Motorola Razr I, updated with the last version of android, no unlock, no root, 8months old, just a lambda user, never tried to root or unlock ... I did nothing before it crashed, it was in my pocket, no wifi ... it stopped alone and on restart, the Red Point of Motorola of Death is back ...
I can start the fastboot menu, but only "Shutdown" works. "Normal Powerup", "Recovery", "BP Tool" or "Factory" write the same log :
Booting with [...]
Failed to lock fuse, code = 0xa0b23d
Failed to lock fuse, code = 0xa0b23c
Fuse read failed bank = 4 SEP_RETURN = 0xa0b23c
Fuse read failed bank = 4 SEP_RETURN = 0xa0b23c
Click to expand...
Click to collapse
I searched on Xda or with my friend Google, but nothing works because every indicated solution is used with a working recovery mode ...
Did you already meet this kind of problem ? Is it a hard brick ? Can I use my phone like a doorblocker ?
Thanks for your incoming help
LanceOmelette
PS :sorry for my english ... (swiss-french inside ...)
PPS : need more informations ? It will be a pleasure to give them ... if I know how to find it (android noob inside)
PPPS : I hope, I was clear in my description ...
LanceOmelette said:
Hi,
My phone boots until the Motorola Logo (M in a red point) but doesn't do anything else. And every 5 minutes, it restarts and stops at the same place. No animation, just stops like that, a rock with a red point ...
My phone is a Motorola Razr I, updated with the last version of android, no unlock, no root, 8months old, just a lambda user, never tried to root or unlock ... I did nothing before it crashed, it was in my pocket, no wifi ... it stopped alone and on restart, the Red Point of Motorola of Death is back ...
I can start the fastboot menu, but only "Shutdown" works. "Normal Powerup", "Recovery", "BP Tool" or "Factory" write the same log :
I searched on Xda or with my friend Google, but nothing works because every indicated solution is used with a working recovery mode ...
Did you already meet this kind of problem ? Is it a hard brick ? Can I use my phone like a doorblocker ?
Thanks for your incoming help
LanceOmelette
PS :sorry for my english ... (swiss-french inside ...)
PPS : need more informations ? It will be a pleasure to give them ... if I know how to find it (android noob inside)
PPPS : I hope, I was clear in my description ...
Click to expand...
Click to collapse
I would try reflashing the original firmware using Motorola's RSD Lite Flash Tool
if you are still on warranty send it back to the seller
totex71 said:
I would try reflashing the original firmware using Motorola's RSD Lite Flash Tool
Click to expand...
Click to collapse
Thanks Totex.I tried : the log is :
Getvar max-download-size
Downloading ...
downgraded security version
update gpt_main version failed
preflash validation failed for GPT
Fastboot command failed
Click to expand...
Click to collapse
and in RSD Lite :
Status : Failed flashing process 1/11 flash gpt "gp_signed" -> phone return FAIL
Click to expand...
Click to collapse
mmmmmh I presume it's bad ... very bad ... :crying:
Thanks ICuaI, I keep a small hope to not use this last advice
LanceOmelette said:
Thanks Totex.I tried : the log is :
and in RSD Lite :
mmmmmh I presume it's bad ... very bad ... :crying:
Thanks ICuaI, I keep a small hope to not use this last advice
Click to expand...
Click to collapse
Is there ICS or JB on it? and did you try to flash ics?. if so, try the latest jelly bean firmware
Which firmware did you try to flash? I think you need this one:
http://sbfdownload.droid-developers.org/smi/CFC_9.8.2I-50_SMI-26_S7_USASMIJBRTEU.xml.zip
It is retail eu jelly bean
via RazR I & Tapatalk 4
Thanks
but no ...
It didn't work ... now, it failed on step 2
Log on phone :
Getvar max-download-size
Downloading ...
Flashing gpt ...
OEM fb_mode_set
Fastboot command failed
Click to expand...
Click to collapse
which version of RSD-Lite do you use? What did you try?
Come on, tell us a little bit more. With "No it does not work" we cannot help you.
Ok ... sorry ... I will try to do my best :
RSD Lite 6.0 / Windows 8 / I presume Jelly Bean was my last version on my phone because I checked 1 day before for any update.
The informations on fastboot flash mode :
AP Fastboot Flash Mode (secure boot)
20.25 (sha - [...])
IFWI Info: 42.26
eMMC Info: Size 8GB
Barcode: [...]
Battery (Okay): 3.5v (temp 29.0)
Connect USB Data Cable
ROM-Key: Motorola-Key
Modem Status: Secure
Click to expand...
Click to collapse
I tried to flash my phone with the firmwire you gave me
Connect my phone on RSDLite with USB, Select the xml file and start the process. That stopped after few seconds on step 2
All others exemples found on Google to rescue my phone used the recovery mode or an other option given by the fastboot mode : the probem is every option in the fastboot mode (except Power Off) crashes my phone. So I didn't do lot of things finally ...
Can I give you more informations ?
LanceOmelette said:
Ok ... sorry ... I will try to do my best :
RSD Lite 6.0 / Windows 8 / I presume Jelly Bean was my last version on my phone because I checked 1 day before for any update.
The informations on fastboot flash mode :
I tried to flash my phone with the firmwire you gave me
Connect my phone on RSDLite with USB, Select the xml file and start the process. That stopped after few seconds on step 2
All others exemples found on Google to rescue my phone used the recovery mode or an other option given by the fastboot mode : the probem is every option in the fastboot mode (except Power Off) crashes my phone. So I didn't do lot of things finally ...
Can I give you more informations ?
Click to expand...
Click to collapse
Here's your problem. You need RSD 6.14. Other versions are too old to recognize the new Moto phones.
tatazeuz said:
Here's your problem. You need RSD 6.14. Other versions are too old to recognize the new Moto phones.
Click to expand...
Click to collapse
I just tried with RSD 6.1.4 and 6.1.5, same error : OEM fb_mode_set / Fastboot command failed.
I will go to my seller this afternoon and try to use my warrant.
Thanks for your help :-/
LanceOmelette said:
I just tried with RSD 6.1.4 and 6.1.5, same error : OEM fb_mode_set / Fastboot command failed.
I will go to my seller this afternoon and try to use my warrant.
Thanks for your help :-/
Click to expand...
Click to collapse
Go to the xml and delete the command that fails, in this case OEM fb_mode_set
It was an idea I found too but I didn't know the utility of this line and I didn't want to have a brocken version ...
But now my phone is in the hand of my seller ... I can only pray to have it as soon as possible ...
Thank you everybody for your help It was a pleasure to ask you a question The answers were fast and understable for me
I will give you the result of the investigation of my seller (2weeks to 1month) if I don't forget ...
LanceOmelette said:
It was an idea I found too but I didn't know the utility of this line and I didn't want to have a brocken version ...
But now my phone is in the hand of my seller ... I can only pray to have it as soon as possible ...
Thank you everybody for your help It was a pleasure to ask you a question The answers were fast and understable for me
I will give you the result of the investigation of my seller (2weeks to 1month) if I don't forget ...
Click to expand...
Click to collapse
I deleted fb_mode and it all flashes like it should. I think it just sets it up on fastboot or smth like that
Sorry for the delay, I'm on a trip around the world and I just received my phone back from the seller. But like I thought : no discussion, no message to give the reason or the solution. My phone is back, they made a big hardreset.
Thank you, everybody for your help. I learn some new things
Bye
Lance
Well I tried installing Titan Rom and then had to update the bootloader.
While fastboot didn't recognize my phone when i typed "adb devices" it still said it was connected, so I gave it a shot with the following instructions here.
http://forum.xda-developers.com/moto-g-2014/general/bootloader-update-t3060007
So I noticed that it erases modem 1 and 2.
I have wifi, but no network for my carrier to make calls or receive data.
My backup didn't reset the modem either. Phone is back to the way it was saved during TWRP backup, except for the modems/network.
Any suggestions?
Thanks.
hi
Mmm i will try to help you - tell me what version bootloader and recovery you have installed pls.
TWRP 2.8.6.0
bootloader v, can't tell you, trying different things to find out now.
TWRP 2.8.6.0
bootloader 0x4882
CindysD said:
Well I tried installing Titan Rom and then had to update the bootloader.
While fastboot didn't recognize my phone when i typed "adb devices" it still said it was connected, so I gave it a shot with the following instructions here.
http://forum.xda-developers.com/moto-g-2014/general/bootloader-update-t3060007
So I noticed that it erases modem 1 and 2.
I have wifi, but no network for my carrier to make calls or receive data.
My backup didn't reset the modem either. Phone is back to the way it was saved during TWRP backup, except for the modems/network.
Any suggestions?
Thanks.
Click to expand...
Click to collapse
I'm not sure what model of Moto G you have, but for the data problem, you'll have to input your API settings. Flashing will usually wipe them out. Go to Settings, More (under Wireless & Networks at the top), Cellular Networks, Access Point Names. There you should see your carrier. When you click on it, it will open and here you will need the settings for your carrier. If you give me your carrier, maybe I can tell you what to input or someone else here will surely have the same carrier.
Going back one step, where you see Network Operators, click on that and see if your operator comes up. If so, that may fix the phone problem when you select the carrier.
you probably flash the wrong ''modem NON-HLOS.bin'' file.
did you notes that in the download folder have 5 folder one for it device model?
Did you download the one for your's device exactly model?
If so it may be wrong...
Find a XML ROM of yours exactly device and flash again the ''modem NON-HLOS.bin''
to find the ROM search here
Use this commands but with the right file.
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
modemst1 and 2 is only erasing the temp stats of modem not erase the modem files.
Hello xda, it's me
I write to you because i need help, two weeks ago, i did a hard reset on the B853 update of my Huawei P7-L10 phone.
The circle grow, grow,... 10,20,...99%, then. Failed, witha brief error message : "Update failed" and "post_update_failed", (why ?)
I restarted then, i was on the B853 update. So, no problem.
I installed TWRP, with fastboot, and then in TWRP, i installed SuperSu. No problem at all.
I turn off to put my SIM card, i turn it on again. then, it's ask for sim pin, ok.
And, then, he ask me the Network code for sim card. A bit confused, i press "Cancel".
I go to the num pad, and wrtie *#06#, to get my IMEI... and it was a null IMEI. (so, 000000000000000)
So, i decide to reboot into fastboot, and write imei with it,
My fastboot screen say "PHONE Unlocked" in red.
I write in fastboot : "fastboot oem writeimei 123456456123153" (this is an example of imei, not mine, but got my imei on my original phone box)
Résult :
...
FAILED (remote: Command not allowed)
finished. total time: -0.000s
Click to expand...
Click to collapse
I tried, DC-Unlocker, with Manufactuer mode, then it won't detect my phone,
I tried, with adb and communication with modem,
I tried, TWRP to recover EFS partition (and, don't have EFS partition --' )
I tried, I tried, I tried, I googled for 1 week.
I'm tired to try and i ask for your help...
One more thing, i tried to recover with HiSuite Software, but our phone is not supported for that.. So, I give up with HiSuite.
One more other thing IMPORTANT : Before it happen, my /sdcard/ partition is in Read-Only Mode, and, i can just install Apps from Google Play. (because its installation path is in /data/)
Thanks a lot. And a big sorry for my really bad english
If you want more information please, tell me what you want ! I reaaallyy want my phone working again.
If you answer i will receive an email immédiatly, so i will answer fast. (exept if it's 3AM in belgium.. )
Thanks.
COLLETTE Loïc
News...
So, after no answer i tried to downgrade to B839, and there was no error, successfull B839 downgrade, then now i can use the internal storage ...
So, waiting for answer... thanks.
COLLETTE Loïc
how fix IMEI without HCU ??
Hi,
I'm trying to help a friend that tried to update his P9 Plus VIE-AL10 using the sdcard method and something went wrong; now the phone is stuck on bootloader;, but the screen doesn't turn on, nor any light...
The bootloader is locked.
My PC recognizes the phone and I can connect using fastboot but can't flash anything, I get:
fastboot flash boot BOOT.img
sending 'boot' (14962 KB)... OKAY [ 0.500s]
writing 'boot'... FAILED (remote: Command not allowed)
finished. total time: 0.500s
I tried different stock firmware versions, including the one that's still on the sdcard, same results..
None of the key combinations work... but if I keep pressed the PWR button when connected to the PC I get a disconnect/connect sound, so it must be rebooting...
I was able to fix a xiaomi redmi 3s by putting it in edl mode shorting a data pin with ground on the USB cable... is there any similar method for huawei phones?...
Any help would be great!
Best,
Gustavo Melo
Gusimelo said:
Hi,
I'm trying to help a friend that tried to update his P9 Plus VIE-AL10 using the sdcard method and something went wrong; now the phone is stuck on bootloader;, but the screen doesn't turn on, nor any light...
The bootloader is locked.
My PC recognizes the phone and I can connect using fastboot but can't flash anything, I get:
fastboot flash boot BOOT.img
sending 'boot' (14962 KB)... OKAY [ 0.500s]
writing 'boot'... FAILED (remote: Command not allowed)
finished. total time: 0.500s
I tried different stock firmware versions, including the one that's still on the sdcard, same results..
None of the key combinations work... but if I keep pressed the PWR button when connected to the PC I get a disconnect/connect sound, so it must be rebooting...
I was able to fix a xiaomi redmi 3s by putting it in edl mode shorting a data pin with ground on the USB cable... is there any similar method for huawei phones?...
Any help would be great!
Best,
Gustavo Melo
Click to expand...
Click to collapse
shorting pin will give you another mode ( huawei com 1.0) it like qload 9008 a serial mode ,you can't access to fastboot with this
you need a software to force the bootloader and install any soft like dc-pheonix ( it will cost you 15 euro for 72h of use)
don't use methode 2 of dc-pheonix if you will use it
if methode 1 dosent work ask me i will do an xml config file for you that can work with dc and help you to solve your problem
other pepole talk about funkyhuawei 2.0 i have not test it
makabress said:
shorting pin will give you another mode ( huawei com 1.0) it like qload 9008 a serial mode ,you can't access to fastboot with this
you need a software to force the bootloader and install any soft like dc-pheonix ( it will cost you 15 euro for 72h of use)
don't use methode 2 of dc-pheonix if you will use it
if methode 1 dosent work ask me i will do an xml config file for you that can work with dc and help you to solve your problem
other pepole talk about funkyhuawei 2.0 i have not test it
Click to expand...
Click to collapse
Hi,
So, dc-phoenix will work even if I can't turn on the phone to system or recovery?
Also, would it be possible to install any firmware, like a global or european firmware using this method?
Thank you,
Gustavo Melo
Gusimelo said:
Hi,
So, dc-phoenix will work even if I can't turn on the phone to system or recovery?
Also, would it be possible to install any firmware, like a global or european firmware using this method?
Thank you,
Gustavo Melo
Click to expand...
Click to collapse
If your phone is detected in fastboot ,than yes you can install any firmware
for ota update you will need to flash the oeminfo with srktool or dc-pheonix
makabress said:
If your phone is detected in fastboot ,than yes you can install any firmware
for ota update you will need to flash the oeminfo with srktool or dc-pheonix
Click to expand...
Click to collapse
Thank you for your help! I'll talk to the phone owner tomorrow to see if I should go down this route... is he agrees I'm sure I'll have some more doubts...
Thanks again,
Gustavo Melo
Gusimelo said:
Hi,
I'm trying to help a friend that tried to update his P9 Plus VIE-AL10 using the sdcard method and something went wrong; now the phone is stuck on bootloader;, but the screen doesn't turn on, nor any light...
The bootloader is locked.
My PC recognizes the phone and I can connect using fastboot but can't flash anything, I get:
fastboot flash boot BOOT.img
sending 'boot' (14962 KB)... OKAY [ 0.500s]
writing 'boot'... FAILED (remote: Command not allowed)
finished. total time: 0.500s
I tried different stock firmware versions, including the one that's still on the sdcard, same results..
None of the key combinations work... but if I keep pressed the PWR button when connected to the PC I get a disconnect/connect sound, so it must be rebooting...
I was able to fix a xiaomi redmi 3s by putting it in edl mode shorting a data pin with ground on the USB cable... is there any similar method for huawei phones?...
Any help would be great!
Best,
Gustavo Melo
Click to expand...
Click to collapse
Gusimelo said:
Thank you for your help! I'll talk to the phone owner tomorrow to see if I should go down this route... is he agrees I'm sure I'll have some more doubts...
Thanks again,
Gustavo Melo
Click to expand...
Click to collapse
ok ask me if you need more help
you are welecom
makabress said:
ok ask me if you need more help
you are welecom
Click to expand...
Click to collapse
Hi there... I took the plunge and used dc-phoenix... the phone is back to life! thank you very much for the tip!
Just one more thing: since I now have 72h hours to flash whatever I want, is there any firmware I can flash that turns the phone into an European version?... If so, will OTA updates work?
Best,
Gustavo Melo
Gusimelo said:
Hi there... I took the plunge and used dc-phoenix... the phone is back to life! thank you very much for the tip!
Just one more thing: since I now have 72h hours to flash whatever I want, is there any firmware I can flash that turns the phone into an European version?... If so, will OTA updates work?
Best,
Gustavo Melo
Click to expand...
Click to collapse
I think it will work if you change the oeminfo too
But backup your before this
Hi everybody, I have a little question regarding my P10.
The model of my phone is VTR-L09C521B101
Is there a way to flash this phone with VTR-L09C432 version?
or i need to flash with same model version (VTR-L09C521)?
Thnks
Yes, it is possible to 'rebrand'. The procedure is explained in the Mate 9 forum. It is not so easy and involves unlocking the bootloader.
Updating can be done with the Firmware Finder (Playstore).
M1chiel said:
Yes, it is possible to 'rebrand'. The procedure is explained in the Mate 9 forum. It is not so easy and involves unlocking the bootloader.
Updating can be done with the Firmware Finder (Playstore).
Click to expand...
Click to collapse
thanks for the answer!!
regarding bootloader, the phone shows this:
PHONE RELOCKED
FRP LOCK
ADB shows me that the phone is unlocked, the problem is when I try to send something to phone it shows:
Error Remote command not allowed.
any ideas?
thanks!
I've tried to reword the mate 9 instructions for the p10 here: https://forum.xda-developers.com/p10/help/rebrand-firmware-finder-t3685951
As for adb, what command are you trying? Do you see your phone if you type ADB Devices?
Quintman said:
I've tried to reword the mate 9 instructions for the p10 here: https://forum.xda-developers.com/p10/help/rebrand-firmware-finder-t3685951
As for adb, what command are you trying? Do you see your phone if you type ADB Devices?
Click to expand...
Click to collapse
Quintman, no the phone is not listed with adb devices command. I can only enter with fastboot.
Let me paste the commands that I have tried:
C:\adb>fastboot devices
WPG7N17320000978 fastboot
C:\adb>fastboot oem get-bootinfo
...
(bootloader) unlocked
OKAY [ 0.001s]
finished. total time: 0.001s
C:\adb>fastbot oem lock <my_unlock_code>
...
FAILED (remote: Command not allowed)
finished. total time: 0.016s
C:\adb>fastboot oem unlock <my_unlock_code>
...
FAILED (remote: Command not allowed)
finished. total time: 0.016s
C:\adb>fastboot oem relock <my_unlock_code>
...
FAILED (remote: stat not match)
finished. total time: 0.016s
The Strange thing is that in the phone shows PHONE RELOCKED, not unlocked as ADB shows.
Since I uploaded boot img of another version (C432) full OTA, could this be the problem? in this case what can I do?
thanks for your help!!
Could this be happening because of FRP Lock?, none of the software I have tried (DC-phoenix, chimera and Unlocker v2) worked. Im this close to throw this f*ckin phone to trash u.u
fmm1977 said:
Could this be happening because of FRP Lock?, none of the software I have tried (DC-phoenix, chimera and Unlocker v2) worked. Im this close to throw this f*ckin phone to trash u.u
Click to expand...
Click to collapse
edit: just found this in another thread "FRP Lock occurs when the phone has a firmware mismatch and or oem unlocking is not on in developer options"
Hmm, i've just checked my phone and in fastboot it says PHONE Locked, and FRP Unlock. I think that may be your issue. What exactly did you do to flash your phone with the other version? put an UPDATE.APP into a \Dload folder and 3 button update?
is your phone booting (guessing not). my guess is that you need to get a hold of your stock firmware file an flash that first.
Quintman said:
edit: just found this in another thread "FRP Lock occurs when the phone has a firmware mismatch and or oem unlocking is not on in developer options"
Hmm, i've just checked my phone and in fastboot it says PHONE Locked, and FRP Unlock. I think that may be your issue. What exactly did you do to flash your phone with the other version? put an UPDATE.APP into a \Dload folder and 3 button update?
is your phone booting (guessing not). my guess is that you need to get a hold of your stock firmware file an flash that first.
Click to expand...
Click to collapse
Ok, this is what I've done step by step:
1.- With the unlock code provided by huawei, I have unlocked my phone (my version is VTR-L09C521B101 stock)
2.- Once unlocked, I have downloaded another ROM version (VTR-L29C605B151) in the web page says this rom is for latin america), so with the Huawei Update Extractor, I have extracted all files.
3.- Via ADB/FASTBOOT, I sent the files to my phone, boot.img first and then the others. (big big mistake!)
4.- Rebooted the phone, and then keeps restarting at huawei logo.
5.- Seeing that it did´t worked, what I did was to lock the phone again thinking to send it to Huawei (at this point the phone shows as "unlocked" via fastboot commands, however when I start the phone in fastboot mode, in the screen shows "PHONE RELOCKED, FRP LOCK"
6.- Sent to huawei's service, they said that they cannot fix my phone because it was tampered/rooted.
7.- Right now all I need to fix my phone is to LOCK/UNLOCK again in order to rebrand it to L29 version, since the original stock rom dont exist (not as FULL OTA).
And that´s what I did so far my friend.
Questions:
1.- Is there a way to connect to my phone and change the oem info file? or something?
2.- Do I need to wait the stock rom to be released in order to reflash via Dload method?
3.- What if the stock ROM version of my phone is never released?
thank you for your answer my friend!!
Hmm ok. I am just not sure on your step 3, I've never heard of a method that involves a boot.img... what I would suggest, is to try and download the stock firmware files (need the larger full ota files), extract the update.app file and put on sd card in \dload.
Then hold down both volume up and down and power (3 button method)
It will try and flash the stock image back to the phone.
I just tried the Dload method and nothing happened (always stuck in 5%), now im going to try to use a smaller memory card (mine is 64 Gb). lood
U have disconnected the USB cable when u try 3 button update
berka38 said:
U have disconnected the USB cable when u try 3 button update
Click to expand...
Click to collapse
Yes sr!!