XT1097 Marshmallow TWRP not loading - X 2014 Q&A, Help & Troubleshooting

Hey everyone
I'm trying to root my XT1097 (Canadian on Wind Mobile) but I cant seem to get TWRP to install. Everytime I try to boot into recovery it just boots normally. I have been searching these forums (and the internet) for days and can't seem to find a solution. I did see one mention of some devices automatically replacing a custom recovery when trying to boot into recovery for the first time and needing to hold a specific key combo while booting to prevent this but as near as I can tell this device is not one of them. It sure seems to be acting that way though, am I missing something?
Here is the info
Moto X 2014 XT1097 on Wind Mobile in Canada
Unlocked bootloader
Dev options on with USB debugging enabled
"twrp-3.0.2-1-victara.img" is the file I am trying to use from the twrp website, which I believe is the correct one
I enter the following in cmd
E:\Programs\Android>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.328s]
booting...
OKAY [ 0.251s]
finished. total time: 0.578s
and it reboots normally. If I try this:
E:\Programs\Android>fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (9160 KB)...
OKAY [ 0.328s]
writing 'recovery'...
OKAY [ 0.407s]
finished. total time: 0.734s
Then select recovery on the phone, it just shuts off.
It says "Mismatched partition size (recovery)" in pink when I flash the recovery image but I read that that can be ignored if you use the first method.
Any help would be great!

Jackson604 said:
Hey everyone
I'm trying to root my XT1097 (Canadian on Wind Mobile) but I cant seem to get TWRP to install. Everytime I try to boot into recovery it just boots normally. I have been searching these forums (and the internet) for days and can't seem to find a solution. I did see one mention of some devices automatically replacing a custom recovery when trying to boot into recovery for the first time and needing to hold a specific key combo while booting to prevent this but as near as I can tell this device is not one of them. It sure seems to be acting that way though, am I missing something?
Here is the info
Moto X 2014 XT1097 on Wind Mobile in Canada
Unlocked bootloader
Dev options on with USB debugging enabled
"twrp-3.0.2-1-victara.img" is the file I am trying to use from the twrp website, which I believe is the correct one
I enter the following in cmd
E:\Programs\Android>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.328s]
booting...
OKAY [ 0.251s]
finished. total time: 0.578s
and it reboots normally. If I try this:
E:\Programs\Android>fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (9160 KB)...
OKAY [ 0.328s]
writing 'recovery'...
OKAY [ 0.407s]
finished. total time: 0.734s
Then select recovery on the phone, it just shuts off.
It says "Mismatched partition size (recovery)" in pink when I flash the recovery image but I read that that can be ignored if you use the first method.
Any help would be great!
Click to expand...
Click to collapse
You use Volume Up, not the power button to select Recovery. The mismatch is normal because you're flashing a non-stock recovery.

Wow I knew it was going to be something dead simple I was missing, thanks I'll give that a go when I get home!

Related

stock-device bricked itself (battery drained with pinned app, ecnrypted device)

Hi there,
tl;dr:
Basically, my problem seems to be, that any write-operation on my filesytems is refused:
C:\Users\cxx\Programme\adb-1.0.32>fastboot -w
Erase successful, but not automatically formatting.
File system type raw not supported.
Erase successful, but not automatically formatting.
File system type raw not supported.
Click to expand...
Click to collapse
I found threads about the same problem on Moto G 2013, where "Philz Recovery" was able to fix the partitioning and filesystems, but it seems that this does not exist vor Moto G 2014. And I don't even get any other than stock-recovery working.
TWRP site states: "Note many devices will replace your custom recovery automatically during first boot. To prevent this, use Google to find the proper key combo to enter recovery. " But I could not find any key combo to enter the recovery I just flashed (at least fastboot tells me so) Using "fastboot boot recovery.img" just shows a shortly flickering Motorola-logo every 10 seconds or so.
---
I am having severe issues with my Moto G (2014).
I found some reports of similar issues, but no solution described worked, and it seems I am the only one experiencing this on a stock device.
First some facts:
Device in use since 2 months
Encyption activated about a month ago, no problems
Yesterday, I used screen pinning feature to let my son play a game.
While he was playing, the battery drained until the device shut down.
I connected the device to a charger
After charging 30%, everything first seems normal, I have to enter my encryption PIN and boot process goes on, showing boot animation.
The problem:
At the point, where it would normally finish, the screen just gets black (while still being lit up). Nothing more will happen. The device will remain in this state forever or until the battery is completely drained again.
I first tried using the official methods for (factory) reset described on Motorolas website, they did not work (I am not allowed to post links here yet, google "/prod_answer_detail/a_id/99825/p/30,6720,9151" will show the URL)
Pressing 7-8 seconds restarts the phone, same situation.
Pressing 120 seconds restarts the phone several times, still not working.
I wanted to perform a factory reset, but starting recovery from bootloader only displayed "Boot Up Failed". Choosing "factory" or "bp tools" just started normal boot process. Barcodes seems to work, it shows barcodes.
So next step was unlocking the device to install TWRP. Fastboot displayed no errors, but then not TWRP, but normal recovery starts. Well, better than "Boot Up Failed".
When now performing a factory reset, this is displayed:
Code:
-- Wiping data...
Formatting /data...
E:
blkdiscard on partition /dev/block/pla
form/msm_sdcc.1/by-name/userdata failed
E:
blkdiscard on partition /dev/block/pla
form/msm_sdcc.1/by-name/cache failed
-- Wiping clogo...
Data wipe complete
Obviously, the partitions are untouched (or not there?), and the problem remains.
I also tried to erase cache and userdata using fastboot, there are no error messages, but after rebooting, I am still asked for encryption PIN, so it's basically the same.
I then tried to use adb sideload to flash cm12 nightly. But the device complains that the signature verification failed.
Now, I am not even able to lock the device again, while fastboot states, it would have succeeded.
I wanted to reinstall stock images as described on thetechrism.com (Google: restore-moto-g-2and-generation-2014-stock-lock-bootloader) but I have problems downloading as I only have mobile internet connection at this moment and the download from filefactory stopped two times at 200 MB and I have only about 1 GB traffic for the rest of the month.
I am stuck here, and getting desperate. Did my device brick itself?
I have CM12 and TWRP here, but just cannot get it flashed. This would be my preferred solution, but a reliable source for stock images would also be very nice.
Did anyone experience similar problems when the battery completely drained with a pinned app on an encrypted device?
Thanks in advance for any hint.
Regards
cxxxx
I was now able to download the original firmware.
But...it's the same :'(
I did every step to reinstall stock firmware. No error-messages, neither on console nor on device, everything seems to be fine.
But when I finally reboot, the device again asks for my encryption PIN and will fail to startup!
I still cannot wipe my userdata, still cannot flash a custom recovery...nothing. It's just a ******* brick.
I found one interesting error:
Code:
C:\Users\cxx\Programme\adb-1.0.32>fastboot -w
Erase successful, but not automatically formatting.
File system type raw not supported.
Erase successful, but not automatically formatting.
File system type raw not supported.
erasing 'userdata'...
OKAY [ 0.066s]
erasing 'cache'...
OKAY [ 0.065s]
finished. total time: 0.133s
How can I manually reformat my partitions in internal storage or how can I force automatically formatting?
Code:
C:\Users\cxx\Programme\adb-1.0.32>mfastboot flash partition gpt.bin
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.041s]
writing 'partition'...
OKAY [ 0.304s]
finished. total time: 0.347s
C:\Users\cxx\Programme\adb-1.0.32>mfastboot flash motoboot motoboot.img
target max-sparse-size: 256MB
sending 'motoboot' (2184 KB)...
OKAY [ 0.134s]
writing 'motoboot'...
(bootloader) flashing tz ...
(bootloader) flashing rpm ...
(bootloader) flashing sdi ...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
OKAY [ 0.954s]
finished. total time: 1.091s
C:\Users\cxx\Programme\adb-1.0.32>mfastboot flash logo logo.bin
target max-sparse-size: 256MB
sending 'logo' (697 KB)...
OKAY [ 0.087s]
writing 'logo'...
OKAY [ 0.044s]
finished. total time: 0.134s
C:\Users\cxx\Programme\adb-1.0.32>mfastboot flash boot boot.img
target max-sparse-size: 256MB
sending 'boot' (10200 KB)...
OKAY [ 0.458s]
writing 'boot'...
OKAY [ 0.599s]
finished. total time: 1.060s
C:\Users\cxx\Programme\adb-1.0.32>mfastboot flash recovery recovery.img
target max-sparse-size: 256MB
sending 'recovery' (10280 KB)...
OKAY [ 0.464s]
writing 'recovery'...
OKAY [ 0.607s]
finished. total time: 1.075s
C:\Users\cxx\Programme\adb-1.0.32>mfastboot flash system system.img_sparsechunk.0
target max-sparse-size: 256MB
sending 'system' (257587 KB)...
OKAY [ 9.899s]
writing 'system'...
OKAY [ 8.160s]
finished. total time: 18.063s
C:\Users\cxx\Programme\adb-1.0.32>mfastboot flash system system.img_sparsechunk.1
target max-sparse-size: 256MB
sending 'system' (256626 KB)...
OKAY [ 9.860s]
writing 'system'...
OKAY [ 8.230s]
finished. total time: 18.094s
C:\Users\cxx\Programme\adb-1.0.32>mfastboot flash system system.img_sparsechunk.2
target max-sparse-size: 256MB
sending 'system' (257136 KB)...
OKAY [ 9.874s]
writing 'system'...
OKAY [ 7.975s]
finished. total time: 17.853s
C:\Users\cxx\Programme\adb-1.0.32>mfastboot flash system system.img_sparsechunk.3
target max-sparse-size: 256MB
sending 'system' (230052 KB)...
OKAY [ 8.841s]
writing 'system'...
OKAY [ 7.559s]
finished. total time: 16.402s
C:\Users\cxx\Programme\adb-1.0.32>mfastboot flash modem NON-HLOS.bin
target max-sparse-size: 256MB
sending 'modem' (49356 KB)...
OKAY [ 1.941s]
writing 'modem'...
OKAY [ 0.854s]
finished. total time: 2.798s
C:\Users\cxx\Programme\adb-1.0.32>mfastboot erase modemst1
erasing 'modemst1'...
OKAY [ 0.012s]
finished. total time: 0.015s
C:\Users\cxx\Programme\adb-1.0.32>mfastboot erase modemst2
erasing 'modemst2'...
OKAY [ 0.013s]
finished. total time: 0.014s
C:\Users\cxx\Programme\adb-1.0.32>mfastboot erase modemst2
erasing 'modemst2'...
OKAY [ 0.014s]
finished. total time: 0.015s
C:\Users\cxx\Programme\adb-1.0.32>mfastboot erase cache
erasing 'cache'...
OKAY [ 0.016s]
finished. total time: 0.018s
C:\Users\cxx\Programme\adb-1.0.32>mfastboot erase userdata
erasing 'userdata'...
OKAY [ 0.041s]
finished. total time: 0.042s
C:\Users\cxx\Programme\adb-1.0.32>mfastboot erase userdata
erasing 'userdata'...
OKAY [ 0.020s]
finished. total time: 0.021s
C:\Users\cxx\Programme\adb-1.0.32>mfastboot reboot
rebooting...
finished. total time: 0.002s
I'm having the same problem...in fastboot mode, none of the actions that i've been made gave me no results... and the stock recovery give me the "blkdiscard on partition" message and the phone still no bootup
izaiasfilho said:
I'm having the same problem...in fastboot mode, none of the actions that i've been made gave me no results... and the stock recovery give me the "blkdiscard on partition" message and the phone still no bootup
Click to expand...
Click to collapse
We are not alone, see here:
http://forum.xda-developers.com/mot...ttery-left-t3085322/post60312526#post60312526
Bad news is, that the problem has not been solved and probably will not as it seems that it's hardware-failure of the flash-storage-(controller).
@cxxxx
I read about it on the moto forums, with users having lost write operations on their phone. And all had one thing in common, they had let the battery die out .
Lesson to be learnt : Never let Li ion batteries totally get drained.
One of the moto moderator told it on their forum to never let your battery totally die. I dont know how much of it rings true as I've let my phone discharged till death many times without any issues.
Same problem here.
After the battery gone once i did't manage to enter. Services errors at android home screen and i can't do recovery - wipe data - cache (all failed). The only thing that i manage is to unlock bootloader.
My question: I 'm thinking to send device for warranty (buying one month ago). Do you think that i 'll have problem with unlock bootloader at service. Somewhere i read that motorola have 2 year warranty for software no matter what. Is that real???
HardBricked unlocked stock lollipop xt1068
Same problem here. But no enconding is on thou.
Can't flash anything - stuck on black screen after boot animation.
XT1068 Unlocked bootloader, stock lollipop, no root, no Motorola service in my country.
Once this devices gone hardbrick, after freaky TWRP could not backup or do anything else. Just could not turn in on at all.
Recovered with jtag riff drivers, but this seems to help bootup, not to flash firmwares - so its not applicable for this case.
RSD Lite 6.1.6 can't see phone, ADB sideload form stock recovery gives no device for adb or windows device manager, but fastboot is okay.
Tryed different computers, different drivers, different stock roms, different fastboot\mfastboot tools, recover scripts.
Hi, guys. I'd face the same problem, but I can boot up, using a Nokia phone charger. Don't know how to explain, but the moto g 2014 charger can't charge enough to boot, when the battery is 0%, then come back to the black screen. With the nokia charger, my moto g boot up normally.
Sorry for my bad english.
Nico
For all those users with soft-bricked "nothing changes after any actions", what if we try to use:
Fastboot erase all
If this would work - bootloader will be dead. We will get the hard brick.
But I have experience of successful recovering xt1068(exactly this one) from hard-brick state, when decice does not turn on at all in any way or mode since bootloader is missing or corrupted.
But PC still can see it over USB cable as QBULC_USB. This one would not work with Motorola drivers nor with any other, but JTAG Riff drivers for QUALCOMM.
Then special low-level tool will load up bootloader.
So? Any suggestions about this?
I think it is not good idea. With fastboot erase all you will erase your imei along with psd partition and your phone will be unrecoverable.
Sent from my XT1068 using XDA Free mobile app
Tonal4Nagual said:
I think it is not good idea. With fastboot erase all you will erase your imei along with psd partition and your phone will be unrecoverable.
Click to expand...
Click to collapse
No way of backing up this data?
I remember some of mine old RAZR - I had some backup of unique data for it.
BTW I have the box with IMEI on it, CID saved in notepad, what else...
Stock fw with no root and THIS with no reason.
Also - right before stucked - phone has drained battery from 60% to 0% in pretty short time, then this happened.
Maybe there is some hardware problem with electric circuit..
Tonal4Nagual said:
I think it is not good idea. With fastboot erase all you will erase your imei along with psd partition and your phone will be unrecoverable.
Sent from my XT1068 using XDA Free mobile app
Click to expand...
Click to collapse
With my device bricked like this I have tried, CHMOD which has unable to alter the partitions, as well as CHOWN & CHGRP(in both TWRP & ADB), Fastboot erase does nothing along with ADB wipe, TWRP does nothing and no changes can be made as nothing is overwritten, as well as with using Fastboot flash, there have been rumors that Philz can fix it but since nothing can be flashed I cannot try (Unless someone has a way to flash it to SD and let it boot from there, Let me know)
Now with my limited knowledge of android and its partitions and since none of the above methods having any effect I believe that this issue is in fact a hardware one not software related, therefore I think 'Fastboot erase all" will have no effect, that is my opinion gathered from more than two weeks testing, wiping & hoping, if there are any senior users/devs who want to correct me they may, Also if they have any other options I will be glad to try it out.
EDIT: This is purely a hardware fault and no software changes can do anything, I ran Fastboot erase all
...and a reboot later and my device is exactly the same, even boots into recovery fine and fastboot barcodes still shows my original IMEI and Serial number, ADB getvar_cid still also shows the correct CID for my device.
I would upload pictures but I haven't got enough posts to link to tinypic

Flashing seems OK, but i got original recovery

Hello guys
Sorry about my bad english.
I aready flashed twrp, philz,CM recovery but I still got the original recovery instead.
The CMD windows says OK.
My phone is stuck in the aqua splash logo, looping the splash.
"C:\Users\Guilherme\Downloads\New folder>fastboot flash recovery twrp-2.8.5.0-titan.img
target reported max download size of 536870912 bytes
sending 'recovery' (9694 KB)...
OKAY [ 0.329s]
writing 'recovery'...
OKAY [ 0.195s]
finished. total time: 0.527s"
ghtmiyashiro said:
Hello guys
Sorry about my bad english.
I aready flashed twrp, philz,CM recovery but I still got the original recovery instead.
The CMD windows says OK.
My phone is stuck in the aqua splash logo, looping the splash.
"C:\Users\Guilherme\Downloads\New folder>fastboot flash recovery twrp-2.8.5.0-titan.img
target reported max download size of 536870912 bytes
sending 'recovery' (9694 KB)...
OKAY [ 0.329s]
writing 'recovery'...
OKAY [ 0.195s]
finished. total time: 0.527s"
Click to expand...
Click to collapse
Download the latest TWRP: https://dl.twrp.me/titan/
Here is the link for the motorola fastboot: https://www.androidfilehost.com/?fid=95916177934532795
"TWRP Install (Requires TWRP 2.8.4 or higher already installed):
Download the latest TWRP image file (.img) from the download link and boot TWRP. Go to install and find and select the Images... button. Browse to the image that you downloaded and select it. Choose recovery and swipe to flash."
so boot to recovery: mfastboot.exe boot recovery twrp-2.8.6.0-titan.img Don't forget to run CMD as admin
then flash the .img recovery
I can't boot twrp.
tried flashing and boot directly from fastboot( mfastboot boot twrp.img) but got a flashing screen.
the only recovery i can boot from fastboot is the CM.

Stuck on mi boot screen avec flashing boot and recovery using fastboot

Hello everyone,
I'm trying to install TWRP + Boot on my Mi5 in order to install Xiaomi.eu rom later.
I have been following these steps: https://xiaomi.eu/community/threads...r-xiaomi-mi5-unlocked-bl-only-released.31231/
All went well:
Code:
C:\Miflash_tool_gemini\Google\Android>fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (40072 KB)...
OKAY [ 0.977s]
writing 'recovery'...
OKAY [ 1.815s]
finished. total time: 2.795s
C:\Miflash_tool_gemini\Google\Android>fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (37248 KB)...
OKAY [ 0.918s]
writing 'boot'...
OKAY [ 0.341s]
finished. total time: 1.260s
C:\Miflash_tool_gemini\Google\Android>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.995s]
booting...
OKAY [ 1.180s]
finished. total time: 2.177s
Until the moment to reboot to TWRP.
It just displays the mi logo forever and doesn't boot. It's been 10min now.
Is that normal?
Should I continue to wait?
Thx
After 30min with no progress I decided to stop the phone.
I pressed the power button for few seconds. The mi logo disappeared. I stopped pressing. But straight away the phone is trying to reboot and displays again the mi logo forever
F*********************ck!
Managed to enter in Fastboot mode! Don't ask me how.
No I guess, from what I read in various places I need to flash a fastboot DEV ROM using MiFlash?
Seem to be the procedure when you are in bootloop.
I guess I'll have to unlock again the phone once this ROM will be flashed?
Ok I'm back on track. I've downloaded the last Mi5 Global DEV fastboot ROM (gemini_global_images_6.5.30_20160516.0000.22_6.0_global_9cee9512c7.tgz)
I flashed it using MiFlash. But I kept the storage. I probably should have flashed all because now it keeps on say it can't find the device ID and I get some java stack trace errors complaining about SQLite access problems.
Tomorrow I'll try again to flash TWRP. We will see if it does the same :-/
That's it I've managed to flash TWRP + xiaomi.eu stable rom.
I think the part that generated the bootloop was the fact that I didn't run the following command after flashing TWRP:
Code:
fastboot reboot
I rebooted manually using power button + vol. up.
Now everything is working fine.
Foobrother said:
Hello everyone,
I'm trying to install TWRP + Boot on my Mi5 in order to install Xiaomi.eu rom later.
I have been following these steps: https://xiaomi.eu/community/threads...r-xiaomi-mi5-unlocked-bl-only-released.31231/
All went well:
Code:
C:\Miflash_tool_gemini\Google\Android>fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (40072 KB)...
OKAY [ 0.977s]
writing 'recovery'...
OKAY [ 1.815s]
finished. total time: 2.795s
C:\Miflash_tool_gemini\Google\Android>fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (37248 KB)...
OKAY [ 0.918s]
writing 'boot'...
OKAY [ 0.341s]
finished. total time: 1.260s
C:\Miflash_tool_gemini\Google\Android>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.995s]
booting...
OKAY [ 1.180s]
finished. total time: 2.177s
Until the moment to reboot to TWRP.
It just displays the mi logo forever and doesn't boot. It's been 10min now.
Is that normal?
Should I continue to wait?
Thx
Click to expand...
Click to collapse
my phone also got stuck on the logo when i flashed supersu which i think was quite old..
i then flashed a newer zip and everything went back to normal.happy to see that you were able to fix your phone. iwas devastated for the 15min that my phone wasnt working
---------- Post added at 01:55 PM ---------- Previous post was at 01:54 PM ----------
Foobrother said:
Ok I'm back on track. I've downloaded the last Mi5 Global DEV fastboot ROM (gemini_global_images_6.5.30_20160516.0000.22_6.0_global_9cee9512c7.tgz)
I flashed it using MiFlash. But I kept the storage. I probably should have flashed all because now it keeps on say it can't find the device ID and I get some java stack trace errors complaining about SQLite access problems.
Tomorrow I'll try again to flash TWRP. We will see if it does the same :-/
Click to expand...
Click to collapse
have you figured out why this error came in the first place??

Waiting for any device :)

im stuck with this piece of sh*t phone and "waiting for any device". I flashed TWRP 142314 times on my phone, and today this bloody problem comes out and i cant f*king solve it. My drivers and everything is up to date, expect something named "S1 Boot Fastboot" (warning sing near that in device manager). I have no idea what the hell is that and i cant flash twrp and install custom rom. Any ideas, excpet that one about uninstalling win10 )))
yey, a new problem:
C:\Users\nevas\Desktop\sony\ADB\platform-tools-latest-windows\platform-tools>fastboot flash recovery twrp.img
target didn't report max-download-size
sending 'recovery' (10704 KB)...
OKAY [ 0.350s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.356s
nevenx said:
yey, a new problem:
C:\Users\nevas\Desktop\sony\ADB\platform-tools-latest-windows\platform-tools>fastboot flash recovery twrp.img
target didn't report max-download-size
sending 'recovery' (10704 KB)...
OKAY [ 0.350s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.356s
Click to expand...
Click to collapse
You can't flash TWRP to the recovery partition on the Xperia Z. It doesn't use the recovery partition; instead, it uses the FOTAKernel partition, which is inaccessible by Fastboot. If you want to destroy your old stock firmware and install custom ROM, flash TWRP to boot partition. The phone should not boot to the firmware and boots straight to TWRP.

how to unlock bootloader on bricked mobile?

Hello
my mobile is blocked on the HUAWEI logo
when I press VOL- and POWER I go to FASTBOOT & RESCUE MODE (mobile connected to the PC)
PHONE Locked
FRP Lock
my questions:
* if the bootloader is blocked, it is not possible to flash the BOOT, RECOVERY, SYSTEM, etc. with ADB?
* If the mobile is bricked, it is not possible then to unlock the bootloader?
* why, when I introduce an SD card with a LOAD folder, containing UPDATE.APP the mobile does not perform the firmware installation?
I try I do not know how many firmware and I have not yet managed to unblock.
if someone has had the same problem, I want their help.
otherwise, tell me clearly that it is not possible to unlock and the mobile will end up in the trash ...
it will save me from tearing off the rest of hair on my head
iblda said:
Hello
my mobile is blocked on the HUAWEI logo
when I press VOL- and POWER I go to FASTBOOT & RESCUE MODE (mobile connected to the PC)
PHONE Locked
FRP Lock
my questions:
* if the bootloader is blocked, it is not possible to flash the BOOT, RECOVERY, SYSTEM, etc. with ADB?
* If the mobile is bricked, it is not possible then to unlock the bootloader?
* why, when I introduce an SD card with a LOAD folder, containing UPDATE.APP the mobile does not perform the firmware installation?
I try I do not know how many firmware and I have not yet managed to unblock.
if someone has had the same problem, I want their help.
otherwise, tell me clearly that it is not possible to unlock and the mobile will end up in the trash ...
it will save me from tearing off the rest of hair on my head
Click to expand...
Click to collapse
You are totally bricked.. Must have luck to unbrick this but try with DC-Phoenix unlocker, but It"s paid.. I was have same problem and this one help to me
cxyqqz said:
You are totally bricked.. Must have luck to unbrick this but try with DC-Phoenix unlocker, but It"s paid.. I was have same problem and this one help to me
Click to expand...
Click to collapse
I paid 15 € !!
I have this message on DC phoenix
Writing rescue_recovery partition with file recovery
rescue_recovery partition UPDATE ...OK
Looking for device in upgrade mode...
and the mobile is on fastboot & rescue mode ..
if i try to pass the mobile with flight + & power, it shows me the same screen as the departure:
Error!
Func NO: 10 (boot image)
Error NO: 1 (security verify failed)
this morning another test with DC phoenix
error 10
error 1
iblda said:
this morning another test with DC phoenix
error 10
error 1
Click to expand...
Click to collapse
try : https://www.youtube.com/watch?v=8E43DkUQGMM
cxyqqz said:
try : https://www.youtube.com/watch?v=8E43DkUQGMM
Click to expand...
Click to collapse
dc unlocker does not detect my mobile
only DC phoenix detects it
using the tab "update oeminfo" on DC Phoenix 0.0.0.63, I manage to put the mobile in "PHONE UNLOCKED"
from there I take the opportunity to try to flash BOOT, RECOVERY, SYSTEM with ADB commands.
everything goes smoothly and without error but by restarting the mobile always the same screen with the error in red.
message ADB:
Microsoft Windows [version 10.0.17134.407]
(c) 2018 Microsoft Corporation. Tous droits réservés.
C:\Users\José>cd c:/adb
c:\adb>fastboot erase cache
erasing 'cache'...
OKAY [ 0.020s]
finished. total time: 0.021s
c:\adb> fastboot flash boot boot.img
target reported max download size of 471859200 bytes
sending 'boot' (22688 KB)...
OKAY [ 0.539s]
writing 'boot'...
OKAY [ 0.683s]
finished. total time: 1.227s
c:\adb>astboot flash recovery recovery.img
'astboot' n’est pas reconnu en tant que commande interne
ou externe, un programme exécutable ou un fichier de commandes.
c:\adb> fastboot flash recovery recovery.img
target reported max download size of 471859200 bytes
sending 'recovery' (36166 KB)...
OKAY [ 0.894s]
writing 'recovery'...
OKAY [ 1.079s]
finished. total time: 1.981s
c:\adb>fastboot flash system system.img
target reported max download size of 471859200 bytes
sending sparse 'system' (460798 KB)...
OKAY [ 18.360s]
writing 'system'...
OKAY [ 8.003s]
sending sparse 'system' (442517 KB)...
OKAY [ 20.055s]
writing 'system'...
OKAY [ 7.675s]
sending sparse 'system' (459746 KB)...
OKAY [ 17.637s]
writing 'system'...
OKAY [ 7.992s]
sending sparse 'system' (444901 KB)...
OKAY [ 18.492s]
writing 'system'...
OKAY [ 7.729s]
sending sparse 'system' (438286 KB)...
OKAY [ 17.082s]
writing 'system'...
OKAY [ 7.612s]
sending sparse 'system' (150611 KB)...
OKAY [ 5.483s]
writing 'system'...
OKAY [ 2.622s]
finished. total time: 138.805s
c:\adb>
I do not know how I managed to unbrick with a rom NOVA LITE PRA-LX3
how to get back to p8lite ROM now and without the brick again?
EDIT:
I do not know how I managed to unbrick with a rom NOVA LITE PRA-LX3
how to get back to p8lite ROM now and without the brick again?
I took the risk and I flashed again with DC Phoenix with the ROM:
* Prague-L31_C432B100_Firmware_Portugal_Switzerland_France_Germany_Spain_Sweden_Austria_Hungary_Greece_Bulgaria_Macedonia_Nonspecific.APP
but the mobile is still NOVA LITE with imei 000000XXXX
the camera does not work, black screen, photo and selfie
iblda said:
I do not know how I managed to unbrick with a rom NOVA LITE PRA-LX3
how to get back to p8lite ROM now and without the brick again?
EDIT:
I do not know how I managed to unbrick with a rom NOVA LITE PRA-LX3
how to get back to p8lite ROM now and without the brick again?
I took the risk and I flashed again with DC Phoenix with the ROM:
* Prague-L31_C432B100_Firmware_Portugal_Switzerland_France_Germany_Spain_Sweden_Austria_Hungary_Greece_Bulgaria_Macedonia_Nonspecific.APP
but the mobile is still NOVA LITE with imei 000000XXXX
the camera does not work, black screen, photo and selfie
Click to expand...
Click to collapse
Boot into eRecovery (Volume up whilw connected to PC, or when it shows "bootloader unlocked" warning, hold volume up.) Update to lates firmware
also if you get opportunity to update via HiSuite or from phone settings update it. Try as many times as you can to succed. It will aventually flash latest and greatest firmware.
Another method is to use update.app for servicing phones. Downlaod it from here, http://androidhost.ru/K5, place the update.app on external_sdcard inside of a "dload" folder. IN the phone app type *#*#2846579#*#* and select sdcard upgrade. It should work
Wish you luck
aciupapa said:
Another method is to use update.app for servicing phones. Downlaod it from here, http://androidhost.ru/K5, place the update.app on external_sdcard inside of a "dload" folder. IN the phone app type *#*#2846579#*#* and select sdcard upgrade. It should work
Wish you luck
Click to expand...
Click to collapse
this method does not work
the mobile does not exceed 5% and then displays SOFTWARE INSTALL FAILED
Try using HurUpdater. Flash twrp, the download all these files.
1. http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1727/g1647/v146015/f1/full/update.zip dont change name
2.For dualsim
http://update.hicloud.com:8180/TDS/...l/PRA-L31_hw_eu/update_full_PRA-L31_hw_eu.zip (change filename to update_all_hw.zip)
For single sim http://update.hicloud.com:8180/TDS/...l/PRA-L11_hw_eu/update_full_PRA-L11_hw_eu.zip (change filename to update_all_hw.zip)
3. http://update.hicloud.com:8180/TDS/...15/f1/full/public/update_data_full_public.zip (change filename to update_data_public.zip)
4. http://www.mediafire.com/file/ze5z78dq7zu3sxb/HuRUpdater_0.3.zip dont change filename
put all thesw files in one folder on an external sdcard
.
Flash or boot twrp on your phone, and do a "fornat data" commad. wipe all partitions except for the external sd. Flash the HuRupdater_0.3.zip file and confirm flashing by pressing
volume down. After flashing is complete Reboot your phone. ic everything works, it works. If it does not work, do a wipe data and cache in the stock recovery (hurupdater installs stock recovery from the update package automatically)
aciupapa said:
.
Flash or boot twrp on your phone, and do a "fornat data" commad. wipe all partitions except for the external sd.
Flash the HuRupdater_0.3.zip file and confirm flashing by pressing volume down.
After flashing is complete Reboot your phone. ic everything works, it works.
If it does not work, do a wipe data and cache in the stock recovery (hurupdater installs stock recovery from the update package automatically)
Click to expand...
Click to collapse
I flash how?
with what?
where is trwp?
How do I install it?
sorry, I'm starting to be lost ..
this is what I get with the twrp that I downloaded with ADB:
PS C:\Users\José\Documents\MOBILES\huawei\P8\zzzzzz> fastboot flash recovery TWRP-3.2.1-0.img
target reported max download size of 471859200 bytes
sending 'recovery' (8486 KB)...
OKAY [ 0.226s]
writing 'recovery'...
FAILED (remote: image verification error)
finished. total time: 0.256s
WITH MULTI-TOOL FOR HUAWEI:
target reported max download size of 471859200 bytes
sending 'recovery' (23942 KB)...
OKAY [ 0.637s]
writing 'recovery'...
FAILED (remote: image verification error)
finished. total time: 0.653s
my big problem is the installation of a recovery custom.
I can not install it.
the mobile is good in fastboot with bootloader unlocked
but there is no way to flash the recovery:
c: \ adb> fastboot flash recovery twrp-2.8.7.1-p8.img
target reported download size of 471859200 bytes
sending 'recovery' (25880 KB) ...
OKAY [0.676s]
writing 'recovery' ...
FAILED (remote: image verification error)
finished. total time: 0.707s
this is the message I have for all recovery.
EDIT:
and now I have no access unlocking the bootloader with DC phoenix.
Looking for a device in fastboot mode
Device found: 9DCDU17124012020
05/12/2018 23:00:16 Starting to write device in FASTBOOT mode...
Device found: 9DCDU17124012020
IMEI: 862551034926948
Build number: RA-LX1C432B211
Product model: PRA-LX1
Batery state: 4279mv
Not enough credits
he was talking about 72 hours, the time is over.
it's really stealing this dunking thing. the mobile never finally landed, when it was back again it was blocked again.
really **** these huawei as soon as it's bricked.
RIP​
[emoji34][emoji35][emoji34][emoji35][emoji34][emoji35]
​
thanks anyway for your help, even if it did not work ..
Envoyé de mon MHA-L29 en utilisant Tapatalk
iblda said:
I flash how?
with what?
where is trwp?
How do I install it?
sorry, I'm starting to be lost ..
this is what I get with the twrp that I downloaded with ADB:
PS C:\Users\José\Documents\MOBILES\huawei\P8\zzzzzz> fastboot flash recovery TWRP-3.2.1-0.img
target reported max download size of 471859200 bytes
sending 'recovery' (8486 KB)...
OKAY [ 0.226s]
writing 'recovery'...
FAILED (remote: image verification error)
finished. total time: 0.256s
WITH MULTI-TOOL FOR HUAWEI:
target reported max download size of 471859200 bytes
sending 'recovery' (23942 KB)...
OKAY [ 0.637s]
writing 'recovery'...
FAILED (remote: image verification error)
finished. total time: 0.653s
Click to expand...
Click to collapse
------------------------
In your command line you write: fastboot flash recovery TWRP-3.2.1-0.img
just write: fastboot boot TWRP-3.2.1.0.img.. Then TWRP will open.
Now in TWRP you can install TWRP recovery, after reboot you will be able yo use it.
I hope this help you.

Categories

Resources