Hi everyone, I'm done and out of any ideas. Never before have I bricked my phone . Now I don't know what to do. Played before only with Samsung phones, they were waaay easier to play with.
Let me tell you my story:
1. Got P9 Lite with L21C22B120 rom (brand C22 from Poland)
2. No newer version available, decided to debrand / apply newer - flashed L21C432B161 (~3GB update.app), info showed L21C900B161 - need to change oeminfo etc.
3. [SRK Tool ] Unlocked bootloader and installed TWRP
4. [SRK Tool + TWRP] Built Root method via adb sideload failed, so installed SuperSu via TWRP from another source - success
5. [SRK Tool] Flashed oeminfo C432 Europe - success, but after that info showed C432B161 without L21
6. Flashed once more with the same B161 firmware - perfect info L21C432B161 but UI theme and icons got corrupted like that: https://forum.xda-developers.com/p9-plus/help/wrong-icons-c900-to-c432-failed-im-t3490561 and tried to flash mentioned hw_folder with SRK Tool.
7. [TWRP] Played with wipe / factory reset - couldn't boot anymore, TWRP showed "No OS installed" and "unable to mount /data" (it had 0MB, couldn't wipe it)
8. Then RESCUE MODE showed up and still I can't pass by it - exactly like here: https://forum.xda-developers.com/p8lite/help/stuck-rescue-mode-screen-please-help-t3244872 - only fastboot&rescue available.
What I have tried several times:
1. Flashing firmware C432B161 and C432B120 - failure at 5% (incompatibility)
2. Fastboot flash boot.img, recovery.img, system.img and cust.img (extracted from B120 and B161)- success, still rescue mode loop
3. Locking and unlocking bootloader with SRK Tool, flashing stock recovery and TWRP - success, still unable to load any recovery
4. Fastboot flashing FW_hifi.img - FAILED <remote: command not allowed>
Summary:
1. Looped Rescue mode shows: Please update system again, Func no : 8 (hifi image), Error no : 1 (security verify failed)
2. Fastboot&Rescue mode shows: Phone unlocked, FRP Unlock. Fastboot works.
3. Flashing main images doesn't change enything, can't flash corrupted(?) hifi image.
4. Maybe there is something wrong with my Bootloader? Is it truly unlocked? SRK Tool shows bootloader "unlocked" but many of the fastboot commands (i.e. getvar or oem) return "Failed, remote: command not allowed"
Any ideas in any of your clever or experienced heads? Should I try to flash that magical hifi image somehow or to flash some "compatibile" firmware (don't know which one wouldn't return that error).
Tried some fastboot commands, seems like I have found the reason for ROMs incompatibility:
fastboot getvar rescue_version
rescue_version: rescue0.3
finished. total time: 0.071s
fastboot getvar rescue_phoneinfo
rescue_phoneinfo: VNS-C432B161
finished. total time: 0.011s
fastboot oem get-product-model
...
(bootloader) hi6250
OKAY [ 0.011s]
finished. total time: 0.013s
fastboot oem get-psid
...
(bootloader) SN:BUC4C16929(...)
(bootloader) IMEI:863126032(...)
(bootloader) IMEI:863126032(...)
OKAY [ 0.011s]
finished. total time: 0.012s
fastboot getvar vendorcountry
vendorcountry: hw/eu
finished. total time: 0.010s
fastboot oem check-rootinfo
...
(bootloader) old_stat: SAFE
(bootloader) now_stat: SAFE
(bootloader) change_time: 0000000000
(bootloader) Check System: Decode fail
OKAY [ 0.018s]
finished. total time: 0.020s
fastboot oem get-build-number
...
(bootloader) :VNS-C432B161
OKAY [ 0.012s]
finished. total time: 0.013s
fastboot oem device-info
...
FAILED (remote: Command not allowed)
finished. total time: 0.013s
What happened to L21 model in my build and model number? Is it corrupted?
Install os manually via adb mounting boot system and the other two things (i don't remember all and i don't have any link)
You can go to Twrpmeticulus?
Thanks guys! I flashed Meticulus TWRP - still couldn't enter it but accidentally discovered the (weird) way. I could go to it only with USB cable connected to computer and by pressing Vol+, Vol- and Power simultaneously, releasing them upon Huawei Logo. From there (TWRP) I rooted my device (adb sideload SuperSU 2.65), replaced oeminfo file via this tutorial - https://forum.xda-developers.com/huawei-p9lite/how-to/request-oeminfo-c432-p9-lite-t3427386 - and voila, I could finally flash C432B161 ROM without incompatibility error. Problem solved, hifi error gone of course.
Hi, I recently downloaded the OTA Nougat update for the Moto G4 phone but instead of completing the process it showed the android man on his side suggesting something went wrong. I tried to restart the phone and it would not boot up, instead being stuck in a boot loop. I have read many videos in an attempt to try and get the phone working again on stock firmware but everything I read seems to have the requirement that USB debugging has been enabled in the Developer settings.
Unfortunately this was not something I enabled as I did not envisage there being any kind of problem with the update as it was the official OTA update of Nougat. I have downloaded what I believe to be the official marshmallow stock firmware for my phone which is the athene_13mp XT1622 16gb P2A variant but I can't figure out how I can install it. When on the bootloader screen on the phone, when I type 'adb devices' on the command prompt no device is listed, however if I type 'fastboot devices' it does list the serial number of my phone followed by the word 'fastboot'. Could anyone be kind enough to point me in the right direction of what I can do from here (if anything). I tried a live chat with someone from Lenovo support and they were absolutely useless.
Apologies if this is answered elsewhere, I tried a search and couldn't find anything to help me.
Thank you
adavies said:
Hi, I recently downloaded the OTA Nougat update for the Moto G4 phone but instead of completing the process it showed the android man on his side suggesting something went wrong. I tried to restart the phone and it would not boot up, instead being stuck in a boot loop. I have read many videos in an attempt to try and get the phone working again on stock firmware but everything I read seems to have the requirement that USB debugging has been enabled in the Developer settings.
Unfortunately this was not something I enabled as I did not envisage there being any kind of problem with the update as it was the official OTA update of Nougat. I have downloaded what I believe to be the official marshmallow stock firmware for my phone which is the athene_13mp XT1622 16gb P2A variant but I can't figure out how I can install it. When on the bootloader screen on the phone, when I type 'adb devices' on the command prompt no device is listed, however if I type 'fastboot devices' it does list the serial number of my phone followed by the word 'fastboot'. Could anyone be kind enough to point me in the right direction of what I can do from here (if anything). I tried a live chat with someone from Lenovo support and they were absolutely useless.
Apologies if this is answered elsewhere, I tried a search and couldn't find anything to help me.
Thank you
Click to expand...
Click to collapse
First of all, "adb devices" doesn't work on the bootloader. The adb app only works in recovery or while booted into the system. Secondly, is your bootloader unlocked? How you proceed depends on that. If you still want to install Nougat there are a couple of options. Let me know your current bootloader status. Above all, don't panic and do something rash.
Here is a link to your phone's stock firmware" https://www.filefactory.com/file/5c...24.139-23.4_cid50_subsidy-DEFAULT_CFC.xml.zip
Hi, thank you for your reply. On the bootloader screen it says :
AP Fastboot Flash Mode (Secure)
BL: B0.0E(*) (sha-4986429, 2016-04-13 14:23:47)
Baseband: M8952_70009.08.03.48R ATHENE_EMEA_CUST
Product/Variant: athene_13mp XT1622 16GB P2A
Serial Number : (is it safe to post this here? Is it needed?)
CPU: MSM8952
eMMC: 16GB SKHYNIX HAG4a2 RV=08 PV=E4 FV=00000000000000E4
DRAM: 2GB SKHYNIX LP3 DIE=8GB M5=06 M6=03 M7=00 M8=1F
Console (NULL): null
Battery OK
oem_locked
Software status: Official
Transfer Mode: USB Connected
Not sure if you need all the info, the only thing I left off was the serial number as I don't think you need that. As you can see the OEM is locked and as I can't boot up the phone I don't know another way to unlock it. Just an update to this as well. Since my original post I followed a guide on YouTube to try and use something called 'Minimal ADB and Fastboot' and it seemed like it was running through the process of installing all the files as lots of data was passing through the CMD window but when it finished the phone just went back to the green Android man fallen over with 'No command.
Thanks again for any help you can ofer, it is really appreciated.
Also thank you for the link to the firmware, I just checked and this is the same file that I already downloaded so I do at least have peace of mind that I selected the right one.
Your phone is probably fixed already. Try to boot with Vol- pressed to enter the bootloader and then select the option that boots to system (not recovery). Recovery screen with "no command" simply means that the "boot to recovery" flag is set and there is no OTA file in phone's memory. After booting once selecting the correct option in the bootloader screen your phone will be back to normal.
_wyrm said:
Your phone is probably fixed already. Try to boot with Vol- pressed to enter the bootloader and then select the option that boots to system (not recovery). Recovery screen with "no command" simply means that the "boot to recovery" flag is set and there is no OTA file in phone's memory. After booting once selecting the correct option in the bootloader screen your phone will be back to normal.
Click to expand...
Click to collapse
Hi, thanks for your reply, sadly I have tried all the options from the bootloader with no success, they do the following:
START - tries to reboot (white screen with blue moto logo) and eventually comes back to android man fallen over with 'No command' underneath
RESTART BOOTLOADER - Just takes me back to the same bootloader screen immediately
RECOVERY MODE - Takes me back to android man fallen over with 'No command' underneath
POWER OFF - turns it off (obviously lol)
FACTORY MODE - tries to reboot (white screen with blue moto logo) and eventually comes back to android man fallen over with 'No command' underneath
BARCODES - displays white screen with four barcodes relating to IMEI, SKU, DATE and SERIAL NUMBER
BP TOOLS - tries to reboot (white screen with blue moto logo) and eventually comes back to android man fallen over with 'No command' underneath
QCOM - tries to reboot (white screen with blue moto logo) and eventually comes back to android man fallen over with 'No command' underneath
BOOTLOADER LOGS - Doesn't do anything when I click the power button on this option but shows some yellow text on the screen that says 'Fastboot reason: Volume down key pressed'
That is all the options I have then, none seem to resolve the problem.
Thank you
Also, I'm not sure if this is relevant but when I ran the flashstock.bat file to try and install the files from XT1621-XT1622-XT1642_ATHENE_MPJ24.139-23.4_cid50_subsidy-DEFAULT_CFC.xml, I noticed as the text scrolled up the CMD window that there was several mentions of:
slot count not found
slot suffixes not found
has-slot system not found
invalid signed image
These lines appear several times, I'm not sure if this is part of the problem or not. If the CMD window didn't automatically close I would have copied and pasted exactly what it says.
Thanks again
Open a command prompt instead of double clicking the bat file. Also make sure you have motorola adb drivers installed, or use motorola's flash tool, RSDLITE, instead of flashing with the bat file.
adavies said:
Hi, thank you for your reply. On the bootloader screen it says :
AP Fastboot Flash Mode (Secure)
BL: B0.0E(*) (sha-4986429, 2016-04-13 14:23:47)
Baseband: M8952_70009.08.03.48R ATHENE_EMEA_CUST
Product/Variant: athene_13mp XT1622 16GB P2A
Serial Number : (is it safe to post this here? Is it needed?)
CPU: MSM8952
eMMC: 16GB SKHYNIX HAG4a2 RV=08 PV=E4 FV=00000000000000E4
DRAM: 2GB SKHYNIX LP3 DIE=8GB M5=06 M6=03 M7=00 M8=1F
Console (NULL): null
Battery OK
oem_locked
Software status: Official
Transfer Mode: USB Connected
Not sure if you need all the info, the only thing I left off was the serial number as I don't think you need that. As you can see the OEM is locked and as I can't boot up the phone I don't know another way to unlock it. Just an update to this as well. Since my original post I followed a guide on YouTube to try and use something called 'Minimal ADB and Fastboot' and it seemed like it was running through the process of installing all the files as lots of data was passing through the CMD window but when it finished the phone just went back to the green Android man fallen over with 'No command.
Thanks again for any help you can ofer, it is really appreciated.
Click to expand...
Click to collapse
TRY THIS BEFORE DOING ANYTHING ELSE: Boot to recovery. While at the dead robot, while holding down the Power key, press and release*the Volume Up key, then release Power.. This takes you into the actual recovery menu. scroll to "wipe data/ factory reset". Then do a factory reset and reboot. It may go ahead and complete your attempt to install Nougat.
[/B]When you are at the bootloader, do you still get your device serial number at the command "Fastboot devices" from your pc? If so you can unlock your bootloader if you so desire. Link to unlock instructions: https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
If you can't get flashstock.bat to work then you can flash your stock ROM. in the sequence below. You will need to extract the ROM to your PC and follow the instructions below:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot oem config carrier vzw
fastboot oem fb_mode_clear
Also, you don't ever need to share your serial number. Finally, the baseband shown is the original Marshmallow stock baseband which tells me that your attempt to flash Nougat failed.
If you have doubts or questions ask first.
---------- Post added at 06:02 PM ---------- Previous post was at 05:33 PM ----------
Alternative if you really want Nougat. Works without unlocking bootloader:
https://forum.xda-developers.com/moto-g4-plus/how-to/android-7-0-install-nougat-official-t3531612
_wyrm said:
Open a command prompt instead of double clicking the bat file. Also make sure you have motorola adb drivers installed, or use motorola's flash tool, RSDLITE, instead of flashing with the bat file.
Click to expand...
Click to collapse
Hi, thank you for your reply, I just downloaded and tried the RSD Lite software. It detected my phone on Port number 1 as 'Fastboot athene_13mp S' and I selected the 'flashfile.xml' and pressed start. Unfortunately it stopped with the status 'Failed flashing process. 3/27 flash partition "gpt.bin" -> Phone returned FAIL.' Does anyone know how to get round this?
Thank you
pastorbob62 said:
TRY THIS BEFORE DOING ANYTHING ELSE: Boot to recovery. While at the dead robot, while holding down the Power key, press and release*the Volume Up key, then release Power.. This takes you into the actual recovery menu. scroll to "wipe data/ factory reset". Then do a factory reset and reboot. It may go ahead and complete your attempt to install Nougat.
]
Click to expand...
Click to collapse
Thanks for your assistance, I have tried wiping the data and doing a factory reset but it still fails to boot unfortunately.
adavies said:
Thanks for your assistance, I have tried wiping the data and doing a factory reset but it still fails to boot unfortunately.
Click to expand...
Click to collapse
Did you manually flash the fastboot images in the sequence provided?
If that doesn't work, I would send it back to Motorola. If it isn't in warranty, well, rip.
pastorbob62 said:
TRY THIS BEFORE DOING ANYTHING ELSE: Boot to recovery. While at the dead robot, while holding down the Power key, press and release*the Volume Up key, then release Power.. This takes you into the actual recovery menu. scroll to "wipe data/ factory reset". Then do a factory reset and reboot. It may go ahead and complete your attempt to install Nougat.
[/B]When you are at the bootloader, do you still get your device serial number at the command "Fastboot devices" from your pc? If so you can unlock your bootloader if you so desire. Link to unlock instructions: https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
If you can't get flashstock.bat to work then you can flash your stock ROM. in the sequence below. You will need to extract the ROM to your PC and follow the instructions below:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot oem config carrier vzw
fastboot oem fb_mode_clear
Also, you don't ever need to share your serial number. Finally, the baseband shown is the original Marshmallow stock baseband which tells me that your attempt to flash Nougat failed.
If you have doubts or questions ask first.
---------- Post added at 06:02 PM ---------- Previous post was at 05:33 PM ----------
Alternative if you really want Nougat. Works without unlocking bootloader:
https://forum.xda-developers.com/moto-g4-plus/how-to/android-7-0-install-nougat-official-t3531612
Click to expand...
Click to collapse
I do still get the serial number when running 'fastboot devices', do you think unlocking the bootloader might be the answer? I went through te steps yesterday to get the code, was a little put off by voiding the warranty though. With regards to running the commands one at a time, I think I am now getting a bit confused on the correct procedure of where to run the commands from. I have tried running it from the folder for 'Minimal ADB and fastboot' (this folder contains all the files from the stock firmware folder as well which I copied and pasted in there) and also directly from the stock firmware folder itself. I will paste the results of each below (sorry to confuse the issue, my head is fried now, lol).
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
ZY223H6QF4 fastboot
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem fb_mode_set
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
OKAY [ 0.005s]
finished. total time: 0.006s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash partition gpt.bin
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slotartition: not found
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.016s]
writing 'partition'...
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.049s
C:\Program Files (x86)\Minimal ADB and Fastboot>
I stopped after the second line as the text above suggests to me that part has failed so no point continuing. When running directly from the firmware folder I get the following :
C:\Users\andrew\Desktop\XT1621-XT1622-XT1642_ATHENE_MPJ24.139-23.4_cid50_subsidy-DEFAULT_CFC.xml>fastboot devices
ZY223H6QF4 fastboot
C:\Users\andrew\Desktop\XT1621-XT1622-XT1642_ATHENE_MPJ24.139-23.4_cid50_subsidy-DEFAULT_CFC.xml>fastboot oem fb_mode_set
...
OKAY [ 0.005s]
finished. total time: 0.006s
C:\Users\andrew\Desktop\XT1621-XT1622-XT1642_ATHENE_MPJ24.139-23.4_cid50_subsidy-DEFAULT_CFC.xml>fastboot flash partition gpt.bin
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.008s]
writing 'partition'...
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.062s
C:\Users\andrew\Desktop\XT1621-XT1622-XT1642_ATHENE_MPJ24.139-23.4_cid50_subsidy-DEFAULT_CFC.xml>
Again this seems to fail also but with some slightly different messages. Interesting that it failed on the gpt.bin part as this was also mentioned when it failed on RSD Lite.
If the firmware is Android 6 and you at some point flashed Android 7 (or tried to), then its safe to edit the .xml file and remove the reference to gpt.bin, and start the flashing proccess again. This error happens when you try to downgrade the phone firmware.
_wyrm said:
If the firmware is Android 6 and you at some point flashed Android 7 (or tried to), then its safe to edit the .xml file and remove the reference to gpt.bin, and start the flashing proccess again. This error happens when you try to downgrade the phone firmware.
Click to expand...
Click to collapse
Yes this whole problem started when I used the phone to check if there were any updates. It said that the Nougat update was available and so I downloaded it on the phone and pressed the button on the phone to install it. This then failed and was the start of all my problems.
I have edited the 'flashfile.xml' file and removed the line <step MD5="e12b1a18da98b9502c735ce6ca192217" filename="gpt.bin" operation="flash" partition="partition"/>, however, it then failed with the message 'Failed flashing process. 5/26 flash boot "boot.img" -> Phone returned FAIL'. Any ideas please?
Thank you
adavies said:
Yes this whole problem started when I used the phone to check if there were any updates. It said that the Nougat update was available and so I downloaded it on the phone and pressed the button on the phone to install it. This then failed and was the start of all my problems.
I have edited the 'flashfile.xml' file and removed the line <step MD5="e12b1a18da98b9502c735ce6ca192217" filename="gpt.bin" operation="flash" partition="partition"/>, however, it then failed with the message 'Failed flashing process. 5/26 flash boot "boot.img" -> Phone returned FAIL'. Any ideas please?
Thank you
Click to expand...
Click to collapse
As long as you can still access the bootloader there is still hope. Did you go through with the entire procedure to unlock your bootloader? If so, can you flash a custom recovery such as TWRP 3.1.0? (fastboot flash recovery "name of the recovery file") After you have done that you can flash any custom ROM you desire.
Also, I suggest you take some time to read through the forums for both the G4 and the G4+. It is obvious from your questions that you haven't done so. There are solutions posted that WILL work for you but you MUST take the time to research and read. Doing so will save a lot of time and keep you from bricking your phone.
adavies said:
Yes this whole problem started when I used the phone to check if there were any updates. It said that the Nougat update was available and so I downloaded it on the phone and pressed the button on the phone to install it. This then failed and was the start of all my problems.
I have edited the 'flashfile.xml' file and removed the line <step MD5="e12b1a18da98b9502c735ce6ca192217" filename="gpt.bin" operation="flash" partition="partition"/>, however, it then failed with the message 'Failed flashing process. 5/26 flash boot "boot.img" -> Phone returned FAIL'. Any ideas please?
Thank you
Click to expand...
Click to collapse
AFAIK, this one isnt safe to skip.. Im out of ideas, sorry. Try another usb cable just in case.. but if it keeps failing at the same point you will probably need to send it to motorola service.
pastorbob62 said:
As long as you can still access the bootloader there is still hope. Did you go through with the entire procedure to unlock your bootloader? If so, can you flash a custom recovery such as TWRP 3.1.0? (fastboot flash recovery "name of the recovery file") After you have done that you can flash any custom ROM you desire.
Also, I suggest you take some time to read through the forums for both the G4 and the G4+. It is obvious from your questions that you haven't done so. There are solutions posted that WILL work for you but you MUST take the time to research and read. Doing so will save a lot of time and keep you from bricking your phone.
Click to expand...
Click to collapse
Hi, I did not go through the entire procedure to unlock the bootloader because I'm not sure that I can. Every guide I have read about this says about enabling developer options so that I can 'Allow OEM unlock' but I can't do that if I can't turn the phone on .
This is how far I get (I removed the actual unlock code as I don't know if that should remain confidential):
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
ZY223H6QF4 fastboot
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem get_unlock_data
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
(bootloader) Unlock data:
(bootloader) 3A45210207590559#
(bootloader) 5A593232334836514634004D6F746F2047200000#
(bootloader) 8470D59C544F993609337B23DD2E2F5ACA719924#
(bootloader) 09900801000000000000000000000000
OKAY [ 0.114s]
finished. total time: 0.116s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem unlock UNLOCK CODE WAS HERE
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
(bootloader) WARNING: This command erases all user data.
(bootloader) Please re-run this command to continue.
OKAY [ 0.011s]
finished. total time: 0.012s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem unlock UNLOCK CODE WAS HERE
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
(bootloader) Check 'Allow OEM Unlock' in Android Settings > Developer
(bootloader) Options
OKAY [ 0.012s]
finished. total time: 0.013s
C:\Program Files (x86)\Minimal ADB and Fastboot>
adavies said:
Hi, I did not go through the entire procedure to unlock the bootloader because I'm not sure that I can. Every guide I have read about this says about enabling developer options so that I can 'Allow OEM unlock' but I can't do that if I can't turn the phone on .
This is how far I get (I removed the actual unlock code as I don't know if that should remain confidential):
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
ZY223H6QF4 fastboot
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem get_unlock_data
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
(bootloader) Unlock data:
(bootloader) 3A45210207590559#
(bootloader) 5A593232334836514634004D6F746F2047200000#
(bootloader) 8470D59C544F993609337B23DD2E2F5ACA719924#
(bootloader) 09900801000000000000000000000000
OKAY [ 0.114s]
finished. total time: 0.116s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem unlock UNLOCK CODE WAS HERE
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
(bootloader) WARNING: This command erases all user data.
(bootloader) Please re-run this command to continue.
OKAY [ 0.011s]
finished. total time: 0.012s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem unlock UNLOCK CODE WAS HERE
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
(bootloader) Check 'Allow OEM Unlock' in Android Settings > Developer
(bootloader) Options
OKAY [ 0.012s]
finished. total time: 0.013s
C:\Program Files (x86)\Minimal ADB and Fastboot>
Click to expand...
Click to collapse
If a redownload of the stock images and a new USB cable and flashing of the images doesn't work, I'd just send it back to Motorola.
negusp said:
If a redownload of the stock images and a new USB cable and flashing of the images doesn't work, I'd just send it back to Motorola.
Click to expand...
Click to collapse
You may be right. He has not successfully unlocked the phone so therefore his warranty should still be good.
---------- Post added at 04:18 PM ---------- Previous post was at 03:51 PM ----------
adavies said:
Hi, I did not go through the entire procedure to unlock the bootloader because I'm not sure that I can. Every guide I have read about this says about enabling developer options so that I can 'Allow OEM unlock' but I can't do that if I can't turn the phone on .
I don't understand why you can't flash the stock ROM. Your baseband version is still on stock. That said if you want to continue trying give this a shot: https://forum.xda-developers.com/moto-g4-plus/how-to/xt1643-ota-nougat-t3483943 This will bring you up to Nougat the latest release. It does not require an unlocked bootloader and has been used on your model.
Or here: https://forum.xda-developers.com/moto-g4-plus/how-to/xt1644-stock-marshmallow-to-nougat-t3540022
Otherwise I would go ahead and do a warranty return. Your warranty should still be okay since you did not go through with unlocking the bootloader.
Click to expand...
Click to collapse
hello
i had a beautiful and full working P9 Lite, VNS-L21 Dual Sim with stock Android 7.0.
wanted to downgrade to MM, but i got it bricked
boot unlocked, flashed TWRP, then OEM file and then Official (all from here : http://www.htcmania.com/showthread.php?t=1261335)
after starting official MM flashing by VOL+, VOL- and POWER, got error "Software install failed!" and dead from that moment.
flashed different TWRP and tried to boot into recovery by VOL+ and POWER, but nothing
also flashed different versions of 6.0 and 7 by fastboot, nothing. at some point boot got locked back, but unlocked it again.
disassembled, disconnected battery, nothing.
ready to try any ideea you think may be lucky.
thanks
If you're getting fastboot try and unlock your bootloader, install twrp for mm. Try and download your firmware eg L21C532B160, leave it in the zip format, place on your SD card, then boot into TWRP and flash the zip file. That should do the trick.
Sent from my HUAWEI VNS-L21 using Tapatalk
Install revolution recovery flash oem and dload c432
@slaughta8868, @Dimitardt - thanks, but in that situation only DC Phoenix or Furious Resurrector could get me out. These 2 progs are able to write absolutely anything into phone, and all needed partitions. Also able to revive by testpoint. i had access to Furious Resurrector and now phone is alive again.
but got this error, no matter what firmware is written.
any idea ?
photo fastboot http://imgur.com/a/vqoJM
C:\AndroidADB>fastboot oem get-build-number
...
(bootloader) :VNS-L21C432B130
OKAY [ 0.000s]
finished. total time: 0.000s
C:\AndroidADB>fastboot oem check-rootinfo
...
(bootloader) old_stat: RISK
(bootloader) now_stat: SAFE
(bootloader) change_time: 1470987496
OKAY [ 0.000s]
finished. total time: 0.000s
thanks
https://forum.xda-developers.com/hu...torial-rollback-n-to-mm-c432-devices-t3563955 try this
I have the same problem with my VNS-L31. Tried to rollback and it just turned off at 99% or 100% and now it does not turn back on. I can only access fastboot through the PC. No dload or recovery. Tried flashing separate system.img, boot.img etc. files but it does not work. Is there really no way other than Furious Resurrector or DC Phoenix to flash the full UPDATE.APP through fastboot? Is there no package, custom ROM, whatever, which has an android-info.txt inside?
i got same problem. after flash no vibration, no display, only fastboot accessible:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem get-build-number
...
(bootloader) :EVA-L09C432B136
OKAY [ 0.005s]
finished. total time: 0.006s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem check-rootinfo
...
(bootloader) old_stat: RISK
(bootloader) now_stat: RISK
(bootloader) change_time: 1463672304
OKAY [ 0.008s]
finished. total time: 0.010s
nbkappa said:
@slaughta8868, @Dimitardt - thanks, but in that situation only DC Phoenix or Furious Resurrector could get me out. These 2 progs are able to write absolutely anything into phone, and all needed partitions. Also able to revive by testpoint. i had access to Furious Resurrector and now phone is alive again.
but got this error, no matter what firmware is written.
any idea ?
photo fastboot http://imgur.com/a/vqoJM
C:\AndroidADB>fastboot oem get-build-number
...
(bootloader) :VNS-L21C432B130
OKAY [ 0.000s]
finished. total time: 0.000s
C:\AndroidADB>fastboot oem check-rootinfo
...
(bootloader) old_stat: RISK
(bootloader) now_stat: SAFE
(bootloader) change_time: 1470987496
OKAY [ 0.000s]
finished. total time: 0.000s
thanks
Click to expand...
Click to collapse
Can you show me test point image VNS-L31 please?
Test point
Here test point image
Hi,
I would like to ask you about a support in programming my "old" Redmi 3s, becase I want to have a newer Android version on the device
The device has Android 6.0.1 MMB29M, MIUI10 Global 9.3.28 Beta, kernel: 3.18.20-g89abe5f.
When I enter fastboot mode, I do not see any version of fastboot, only "picrure of bunny" with FASTBOOT.
Bootloader is arelady unlocked (as in bellow logs).
After when I flashed TWRP and I tried boot twrp.img, I got info:
FAILED (remote: dtb not found)
I tried with available the oldest one as I found on page Redmi3s-Land is twrp-3.1.1-0-land.img , and also tried with the newest one twrp-3.6.2_9-0-land.img.
ISSUE:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 0.403s]
booting...
FAILED (remote: dtb not found)
finished. total time: 0.487s
BOOTLOADER:
I have unlocked bootloader:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem device-info
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: true
(bootloader) Charger screen enabled: true
(bootloader) Display panel:
OKAY [ 0.016s]
finished. total time: 0.017s
What I should do to fix this issue and to enter TWRP:
FAILED (remote: dtb not found)
?
Ahh.. I fouded solution. :/ :/
Commands:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot boot twrp.img
calls twrp.img file from above folder, not from Redmi 3s interal flash, where I copied a new twrp.img to programming.
So simply I moved "right" file of twpr inside to folder "Minimal ADB and Fastboot", and then commands works an issue FAILED (remote: dtb not found) doest apperas.