Related
Hello,
Problem - Device keep on rebooting showing Mi logo (every 2 sec), Does not boot into system
What I did?
exteneded system partition to 1.2 gb - success
flash Marshmellow custom rom - success
misinstalled system ui of theme - system ui stopped
reinstalled clean rom from custom recovery - success
then it does not boot into system - keep on rebooting at mi logo (every 2 sec)
tried fastboot rom - failed (remote size too large)
rebooted into recovery
flash stock partition via adb - success
fastboot flash (with flash all) - success (says miflash - operation compeleted successfully)
Still it does boot into system - keep on rebooting at mi logo (every 2 sec)
Help?
if you can access recovery now then go to recovery and take a backup of current rom. The wipe everything except internal storage and then restore the backup.
maybe it'll fix it because thats what happened to me too after flashing the MM custom rom. Every time i was rebooting the phone kept bootlooping at Mi Logo.
Hmm i ll try but i have to install twrp from adb for backup.
Cwm backup not promising.
You think there ll be problem in hardwere?
No problem in hardware.
and yes do it twrp only. never try cwm.
the thing is i am not able to enter into recovery mode at all.
No recovery and fastboot accessible.
Then connect it to PC and tell me what name the device manager shows for the device.
fastboot is accessible.
i've flashed fastboot rom from miui. successfully completed. but it won't boot.
yesterday it booted into system so i was charging the phone, as soon as i removed charger it went the same boot looping.
now,
clicking flash_all_except_storage from fastboot command
it shows one line in every process - 'target reported max size 80909989 '
process goes on and success.
but does not boot into system. same bootloop.
one strange thing is,
when i connect to pc, - just by pressing vol down button i'm entering to fastboot. (even without holding power button)
does this mean there's something wrong with power button which causing cont. reboot? i mean it cont. forcing system to on and off? :s
Nothing is wrong with the hardware. In this situation the phone boots into fastboot by pressing vol when plugged in.
You didn't answer my question. What does it show in device manager on PC.
sorry for late reply , net connection loss
device manager
1st one is android booloader interface
other devices - bluetooth peripheral devices
Did you use miflash tool to flash fastboot rom
yes,
flashed successfully says miflash.
While flashing using miflash did you select all files in advanced menu properly.
Like all the bat, mbn and xml files.
i didnt try all the file separatly.
trying now.
Then go to advance and choose all the respective files properly.
1st one - flash_all_except_storage.xml
2nd one - nvflash_all.bat (leave it as it is)
3rd one - MPRG8974.mbn
4th one - 8974_msimage.mbn
5th one - rawprogram0.xml
6th one - patch0.xml
i found
flash_all.bat
could not find nvboot script
flash programmer
boot image
could not find kernelflinger image
could not find UFS provision image
RAW xml file
patch xml file
should i go with files?
Which MiFlash tool are you using.
I used the 2014.05.09.0 version
Try this one.
And extract the fastboot ROM twice till you get the images folder inside the "cancro_images_V7.0.****" folder. There you'll fill all the files.
Then in miflash click browse and select that images folder.
And in advanced options select the respective files which are there outside the images folder.
2015.10.28 version
i ll leave the navboot as it is.
giving it a try.
appreciate your help brother.
If it doesn't work then try my version.
It has proper names of files. To avoid confusion.
And all files are there in fastboot ROM except nvboot
i checked on miui
no halos.bin
tz.bin
these all files?
p.s.
operation completed successfully but same boot loop.
trying your version now.
Where I can find official ROM for asus me375cl based on android 5.1.1?
Finaly, i find zip with official ROM on 4pda:
4pda-ru/forum/index.php?showtopic=799982
(put '.' (dot) instead '-' in url)
A special thank to alexoid79 for instruction.
little_pindos said:
Finaly, i find zip with official ROM on 4pda:
4pda-ru/forum/index.php?showtopic=799982
(put '.' (dot) instead '-' in url)
A special thank to alexoid79 for instruction.
Click to expand...
Click to collapse
Thank you so much for posting where you found this, this is exactly what I needed!!! You saved my tablet, it is much appreciated! :good:
Flashing Factory Image
The following instructions worked for me when trying to reflash the factory firmware for the ATT Asus MemoPad 7 LTE (ME375CL). I did originally try using the Asus Flash Tool and the raw firmware file (link below) but the tool said it could not unzip the package for some reason or another. So the steps below show how I did it using ADB with fastboot.
I ASSUME NO LIABILITY SHOULD THIS GO WRONG FOR YOU! However, it probably shouldn't matter if you are bricked, I doubt it will make it any worse Either way, I will not replace your tablet or be responsible for troubleshooting it should you mess it up more...
This scenario is based on the tablet stuck on the Asus boot screen and not going any further. I was trying some in depth rooting attempts and bricked it badly. I was then trying to install a custom recovery and that is why I could not reset it and bricked it.
PRE-REQS:
1. ADB installed - Download: https://drive.google.com/open?id=0B0fKccJIuWsna04wMjY1eG9YREU
2. Asus Drivers installed
3. Firmware - Download: https://drive.google.com/open?id=0B0fKccJIuWsnWGhwYzA0Vkluc2s (file is 1 Gb + in size, may take a bit)
SETUP:
If you already have a working ADB setup, do not download the one above. If you are using the one above, I extracted the folder into my C: drive, so the path for ADB would be C:\adb (to keep it simple and less typing).
MAKE SURE THE ASUS DRIVERS ARE INSTALLED! If you have plugged the tablet in to a pc before, they should already be there. Otherwise search, download and install the appropriate drivers.
INSTRUCTIONS:
Extract the firmware zip file to somewhere easily accessible like your desktop. In there, you should see the boot.img, recovery.img and system.img files, copy/paste those files to your ADB folder (for easier typing later on). There are also additional files like these but start with "unsigned_", do NOT use those!
1. Ensure you probably have at least 30% battery charge, I would still recommend more though.
2. Put the tablet in Fastboot mode by ensuring the tablet is completely powered down and then press/hold the VOLUME UP and POWER keys at the same time. When the Asus screen appears, let go of the POWER button but continue to hold the VOLUME UP button. Let go of the VOLUME UP button when the fastboot screen appears.
3. Plug the tablet in to the computer and then open a CMD prompt as administrator.
4. The following uses the ADB downloaded and placed in the folder as listed above, you may need to adjust the location path as needed if you already have ADB installed or located in a different path.
Type in the following without the quotes: "cd c:\adb" (this will change the path to the ADB files for the CMD prompt)
Type in the following without the quotes: "fastboot devices" (you should then see a device listed)
Type in the following without the quotes: "fastboot flash recovery recovery.img" (flashes the factory recovery image)
Type in the following without the quotes: "fastboot flash system system.img" (flashes the factory system image, may take a while to flash)
Type in the following without the quotes: "fastboot flash boot boot.img" (flashes the factory boot image)
5. Once those 3 images have been flashed, you should have seen a message that says "OKAY" after each one. You should be fine as long as you do not have any red error messages on your tablet.
Type in the following without the quotes: "fastboot reboot" (reboots device normally)
6. If all goes well, it should now boot to the Asus screen and then go to the ATT screen. If so, it will stay on the ATT screen for a while, just wait it out. Mine took about 12-15 minutes and then it opened to the new setup screen to set the tablet up as if its new!
This is how I was able to recover my bricked tablet, hopefully it can help someone else that may run into this.
John, thank you for the write-up. Just bought my ME375CL with 4.4.4.4.
When I try to flash the recovery partition, I get the following error:
C:\Users\Myself\Desktop\adb>fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (11312 KB)...
OKAY [ 1.047s]
writing 'recovery'...
(bootloader) Official image.
FAILED (remote: flash_cmds error!
)
finished. total time: 2.344s
Click to expand...
Click to collapse
and on the tablet's screen:
FASTBOOT CMD WAITING...
RECEIVE DATA...
E:recovery flash failed!
FLASH FAILED!
RESULT: FAIL(flash_cmds error! )
Click to expand...
Click to collapse
I haven't tried the other commands for system.img or boot.img as I don't want to do anything out of order from the write-up. Ever run into this?
The firmware in the download is 5.1.1, not 4.4.4. That is probably the issue. If you are running good on that, I would try rooting it instead. If you are just wanting to upgrade, you will need to have an active AT&T SIM in the tablet to upgrade over the air. I am not sure if there is a flashable upgrade or not somewhere.
Oh ok John. I misread the title of the thread. I thought it was for updating from 4 to 5.
Quick question then: Is it possible, using the adb / fastboot tools, to backup the current 4.4.4.4 before I allow the tablet to update to Lollipop? After reading around, I understand that Lollipop can't be rooted but I have no real concern for it. But just in case I need the tablet to do something else in the future, I'd like to be able to return it to kit kat to be able to root.
Once you upgrade to lollipop, there is no downgrading for this tablet. There really is not much development for this device. I have kind of been working on a lollipop root when I can. Between my limited time and knowledge of android, I can't promise anything.
Overcoming red messages?
Dear John,
Thank you very much for your help. My device runs KitKat 4.4, I can't upgrade over the air, as I damaged my sim slot struggling to remove a stuck nano sim, which I had inserted before I realized that it required a micro sim. (I'd wrongly assumed that by now the world uses only nano).
I followed the steps above, which you wrote so clearly for lay men, thank you a lot.
The flash for recovery.img and system.img worked fine (no red error messages on device).
The flash for boot.img had a red error message.
Might you have an idea or workaround on how I can address this?
If it refuses, is it possible to factory reset?
Thank you very much again for any words of advice and kind regards.
Gor- said:
Dear John,
Thank you very much for your help. My device runs KitKat 4.4, I can't upgrade over the air, as I damaged my sim slot struggling to remove a stuck nano sim, which I had inserted before I realized that it required a micro sim. (I'd wrongly assumed that by now the world uses only nano).
I followed the steps above, which you wrote so clearly for lay men, thank you a lot.
The flash for recovery.img and system.img worked fine (no red error messages on device).
The flash for boot.img had a red error message.
Might you have an idea or workaround on how I can address this?
If it refuses, is it possible to factory reset?
Thank you very much again for any words of advice and kind regards.
Click to expand...
Click to collapse
Sounds odd that it did 2 out of 3 flashes. After you flashed those and rebooted, are you still on KitKat or did it actually update to Lollipop (5.1)? I ask because I assume the system image that flashed would be the operating system.
I still want to stress that this post is for recovering a bricked tablet that will not boot at all. I would not suggest using this as a flashing upgrade as I do not know if it will truly work. If you are still on KK (even after flashing) you could try installing the Asus Flash Tool and use the raw firmware that you downloaded and try it that way. It did not work for me so that is why I used fastboot. It might work for you.
Here is a link for the Asus Flash Tool:
https://drive.google.com/open?id=0B0fKccJIuWsndXJUa1FEbXVzTjA
johnkirchner said:
Sounds odd that it did 2 out of 3 flashes. After you flashed those and rebooted, are you still on KitKat or did it actually update to Lollipop (5.1)? I ask because I assume the system image that flashed would be the operating system.
I still want to stress that this post is for recovering a bricked tablet that will not boot at all. I would not suggest using this as a flashing upgrade as I do not know if it will truly work. If you are still on KK (even after flashing) you could try installing the Asus Flash Tool and use the raw firmware that you downloaded and try it that way. It did not work for me so that is why I used fastboot. It might work for you.
Here is a link for the Asus Flash Tool: ]
Click to expand...
Click to collapse
As a follow up on your question above, Tab restart stalled at a screen (after the Asus logo), presenting some options to do recovery, reboot, factory reset, etc. (factory reset did not help), and red error messages at bottom.
To the GOOD news for anyone interested. I used the Asus Flash Tool and the firmware zip for 5.1.1 (many thanks for the advice).
Note: Tool did not install correctly on Win10 pc, citing error in installing some devcon.exe or similar file (guess that may be a firewall/antivirus issue).
Flash tool took some 15 or so mins unzipping firmware, after which I saw some action on the tab. Another 15 mins, and it rebooted to the At&t logo, stayed here for another 15 mins and unraveled a whole new device on Android 5.1
Glad to hear it worked for you and that I guess you can use this to flash upgrade from kitkat!
There is working way to root our device on lollipop! It is for the other Asus model, but it works for our
http://4pda.ru/forum/index.php?s=&showtopic=640814&view=findpost&p=53047686
I will check this out!
The root works, installed without any issues and verified with a root checker!
Here is a direct download from my Drive folder: https://drive.google.com/open?id=0B0fKccJIuWsnN21ZbnZpc2F6b1E
1. Download the file above.
2. Extract the zip contents.
3. Plug your ME375CL tablet in to pc via usb cable.
4. Make sure you have enabled Developer Mode and allowed USB Debugging first!
5. Open the folder you extracted and double click the "Root-One-Click.cmd" file.
6. It should reboot to fastboot mode and flash the needed files and then reboot again.
You should now have root access. Verify this by installing a root checker app from the play store. Keep in mind, it may say root not installed on the first run. Sometimes it will take a moment for superuser to initially run or prompt for access.
Side note: the root uninstall did not seem to work, got an error...but oh well, the point is to have root!
Thanks go to @little_pindos for finding this file...you are a rockstar!
Anyone get xposed on LP?
ATT Boot Up Sound
Tired of the ATT boot sound? If you used the rooting method above, then you can get rid of the annoying ATT startup sound by doing the following:
1. Install a Root Browser app (I recommend Rom Toolbox Pro, it has a built in file manager)
2. Navigate to the following path:
root/system/media
3. Find the file named "powerup.wav"
4. Simply rename the file by adding .bak to the end (ex - powerup.wav.bak)
5. Make sure it took the name change (some file managers have issues with that)
6. Reboot and see if it got rid of the sound!
You can also use your own startup sounds as long as they are in a .wav format, I believe. Make sure that the name of the file is powerup.wav.
You can also change your boot animation with "boot animation" app.
Best tweak IMO is adding "ro.config.low_ram=true" to build prop, or installing the low ram device xposed module if we can get it to work (both do the same thing). You gain about 100mb more free RAM on average.
TimmyP said:
You can also change your boot animation with "boot animation" app.
Best tweak IMO is adding "ro.config.low_ram=true" to build prop, or installing the low ram device xposed module if we can get it to work (both do the same thing). You gain about 100mb more free RAM on average.
Click to expand...
Click to collapse
I'll have to try that!
AT&T no longer has updates in system for this tablet
Gor- said:
Dear John,
Thank you very much for your help. My device runs KitKat 4.4, I can't upgrade over the air, as I damaged my sim slot struggling to remove a stuck nano sim, which I had inserted before I realized that it required a micro sim. (I'd wrongly assumed that by now the world uses only nano).
I followed the steps above, which you wrote so clearly for lay men, thank you a lot.
The flash for recovery.img and system.img worked fine (no red error messages on device).
The flash for boot.img had a red error message.
Might you have an idea or workaround on how I can address this?
If it refuses, is it possible to factory reset?
Thank you very much again for any words of advice and kind regards.
Click to expand...
Click to collapse
AT&T removed the last update for this tablet months ago and no longer supports it. ASUS states AT&T has all the updates. Total cluster.
hi,
I bought a new Huawei P10 lite phone, unlocked the bootloader, installed TWRP and with this I installed SuperSU via microSD card.
Everything worked fine, until now. Now I want to backup my current modified stock ROM, but TWRP failes.
I got the problem very fast: TWRP can read all files and folders on the microSD car, but not in the internal storage folder.
The file structure is like the following:
acct
boot
cache
config
data
...
etc
external_sd <-- the microSD card
mnt
...
sbin
sdcard
storage
...
Click to expand...
Click to collapse
Everything can be read by TWRP, except the sdcard folder.
Here he only shows strange names (crypted I guess):
something like:
2h8P9lGY8I1A884LMsBjaA
2u+nb0LdBNopRSa5LehsvB
75aTrCvYkWG+R+lrcRz6WA
DcwYkwSKokq8Rm5lYc4YYC
...
Click to expand...
Click to collapse
This strange folders occure within TWRP itself and also if I mount the storage to the computer via TWRP.
I also can not modify, delete or add anything in this cryted folder.
So what am I doing wrong? Why is this crypted and can not be read?
During my research I found this post on reddit with the same problem. But the solution is not clear to me and also not working.
Thanks for any help
greetings
Christopher
PS.: Here some specific information about the phone:
brand new Huawei P10 lite
model WAS-LX1A
build nr. WAS-LX1AC432B102
no updates avaible, checked twice
EMUI 5.1 with Android 7.0
TWRP v3.1.0-2 from here (named "TWRP_P10_Lite_Beta.img")
Hey
It's because your files are encrypted due to forceecnryption and dm-varity in the kernel you can try formating the data to see if it removes the encryption from the data.
My infos may not be correct you can read more about dm-varity and forceecnryption in the internet
aburezk said:
Hey
It's because your files are encrypted due to forceecnryption and dm-varity in the kernel you can try formating the data to see if it removes the encryption from the data.
My infos may not be correct you can read more about dm-varity and forceecnryption in the internet
Click to expand...
Click to collapse
Ok, thanks a lot. This was helful so far.
From what I read, I now must flash a new "boot.img" in order to disable force encryption. But where do I get such a file for my Huawei P10 lite (WAS-LX1A)? I did not found one. Maybe the phone is too new? Or am I just blind?
greetings
christopher2007 said:
Ok, thanks a lot. This was helful so far.
From what I read, I now must flash a new "boot.img" in order to disable force encryption. But where do I get such a file for my Huawei P10 lite (WAS-LX1A)? I did not found one. Maybe the phone is too new? Or am I just blind?
greetings
Click to expand...
Click to collapse
you can't find it anywhere
aburezk said:
you can't find it anywhere
Click to expand...
Click to collapse
Ok, so too new ... damn. That is very bad.
christopher2007 said:
Ok, so too new ... damn. That is very bad.
Click to expand...
Click to collapse
I managed to disable force encryption on my device
Download this and flash it
Backup your data and wipe data from twrp
https://build.nethunter.com/android-tools/no-verity-opt-encrypt/
I tryed no-verity-opt-encrypt-6.0.zip but now do not start anymore... I have restore boot and system but none... what can I do? I think i will sell this p10 lite...
simona70 said:
I tryed no-verity-opt-encrypt-6.0.zip but now do not start anymore... I have restore boot and system but none... what can I do? I think i will sell this p10 lite...
Click to expand...
Click to collapse
i had the same issue by using no-verity-opt-encrypt-6.0.zip. The phone was brick after that.
Do you know your Build of your Phone ? If yes you can download the right Update.app from Huawei and extract the BOOT.IMG, RECOVERY.IMG and the SYSTEM.IMG (Maybe CUST.IMG) and restore it in the fastboot Mode. After that it started again to the UI.
If you dont know the Build of your Phone there will be some Fastboot oem commands to get it (i dont have them in my mind right now).
I flashed the ZIPs in TWRP after that with an external SD card witch arent crypted names...
ChipCollector said:
i had the same issue by using no-verity-opt-encrypt-6.0.zip. The phone was brick after that.
Do you know your Build of your Phone ? If yes you can download the right Update.app from Huawei and extract the BOOT.IMG, RECOVERY.IMG and the SYSTEM.IMG (Maybe CUST.IMG) and restore it in the fastboot Mode. After that it started again to the UI.
If you dont know the Build of your Phone there will be some Fastboot oem commands to get it (i dont have them in my mind right now).
I flashed the ZIPs in TWRP after that with an external SD card witch arent crypted names...
Click to expand...
Click to collapse
I solved using "update_data_full_public.zip" and clearing /data, after restoring previuos boot.img and system.img .
My phone was WAS-LX1AC432B102 4gb EMUI5.1 Android 7.0. I had bricked before and the only way to unbrick was to use "Warsaw-L21_C432B182_EU_SERVICE_androidhost.ru"
I do not trust to install data into a phone i can't backup and restore with TWRP... there is another way to make /data not crypted?
Exist the hope one day TWRP read also crypted /data or it is better search another phone?
ChipCollector said:
i had the same issue by using no-verity-opt-encrypt-6.0.zip. The phone was brick after that.
Do you know your Build of your Phone ? If yes you can download the right Update.app from Huawei and extract the BOOT.IMG, RECOVERY.IMG and the SYSTEM.IMG (Maybe CUST.IMG) and restore it in the fastboot Mode. After that it started again to the UI.
If you dont know the Build of your Phone there will be some Fastboot oem commands to get it (i dont have them in my mind right now).
I flashed the ZIPs in TWRP after that with an external SD card witch arent crypted names...
Click to expand...
Click to collapse
Hey, I am having the exact same problem, my phone is soft bricked after no-verity-opt-encrypt-6.0.zip. (https://forum.xda-developers.com/p10/help/stuck-device-booting-flashing-rom-t3713503).
I know the build of my phone, and I downloaded the update.app and extracted it to boot.img, recovery.img, system.img, but how exactly can I restore it in the fastboot mode. What commands?
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
---------- Post added at 04:35 PM ---------- Previous post was at 04:32 PM ----------
Anymore I think P10lite is a lost cause. I sell to my mother. I bought a xiaomi redmi note 4 global. Never again a Huawei. What a disappointment.
You'll sale your phone to your? Mother? To your mother?
Anyway the same story is on redmi note and all xiaomi
Phones
All the Chinese are difficult to modify.
I was have all Nexus thru 2011 very easy phones but the Chinese... My...
I have a doubt, I have bundled it when trying to install root on my device and I ended up in bootloop what I did was install a (official) rom which when entering the internal files, the folders were with strange names appear, so you recommend removing the credentials (decrypt), to be able to install root? My Device is Xiaomi mi A2
Bro did you find a solution..I am having same problem help
Had my phone bricked two days ago after a failed Motorola system update. Decided do ditch it and go with LineageOS, wich I got working after a few failed install attempts. When I tried to acess my internal storage, I had only those randomly named folders. Deleted them all, but couldn´t write to my storage after. Even tried a camera app, and it said that couldn´t work without a sdcard.
SOLUTION: boot recovery on TWRP > Wipe > Advanced Wipe> select ONLY internal storage > swipe to wipe :good:
Rebooted after internal storage wipe and everything is fine now. It seems all the install attempts made some sort of mess.
chimeralounge said:
Had my phone bricked two days ago after a failed Motorola system update. Decided do ditch it and go with LineageOS, wich I got working after a few failed install attempts. When I tried to acess my internal storage, I had only those randomly named folders. Deleted them all, but couldn´t write to my storage after. Even tried a camera app, and it said that couldn´t work without a sdcard.
SOLUTION: boot recovery on TWRP > Wipe > Advanced Wipe> select ONLY internal storage > swipe to wipe :good:
Rebooted after internal storage wipe and everything is fine now. It seems all the install attempts made some sort of mess.
Click to expand...
Click to collapse
Legend. This fixed the same issue we were facing on the t510 Samsung tablet. Saved us a lot of trouble. Thanks for this.
memz180 said:
Legend. This fixed the same issue we were facing on the t510 Samsung tablet. Saved us a lot of trouble. Thanks for this.
Click to expand...
Click to collapse
-----------
Cool, glad to help! In fact, this issue happened to me once again a few weeks back, when LegacyOS updated. I had this "f*** here we go again" moment, but before wiping, I decided to use TWRP > Advanced > Fix Content. Not only I got the system working again, but *all my data was intact*. System updates are messing file tables, apparently.
I want to marry TWRP.
chimeralounge said:
Had my phone bricked two days ago after a failed Motorola system update. Decided do ditch it and go with LineageOS, wich I got working after a few failed install attempts. When I tried to acess my internal storage, I had only those randomly named folders. Deleted them all, but couldn´t write to my storage after. Even tried a camera app, and it said that couldn´t work without a sdcard.
SOLUTION: boot recovery on TWRP > Wipe > Advanced Wipe> select ONLY internal storage > swipe to wipe :good:
Rebooted after internal storage wipe and everything is fine now. It seems all the install attempts made some sort of mess.
Click to expand...
Click to collapse
God bless you! i've struggle with this s]+t for hours!
what worked for me is installing siankatabg-twrp , now i can see names fine
after that i changed back to official version (which was missy before) and still fine !!!!!!!!
then installed orange fox (which was missy before) and still fine !!!!!!!!
WTH !!!!!!!!!!!!
so i think best shot (if u dont have siankatabg-twrp) is installing codeworkx (Lineage recovery) make sure all good then go back to ur favorite.
lemme know if its works
So I have a p10, and decided to see what i could do with it. Having little experience, I managed to get somewhere. Unlocked the bootloader, got twrp, installed it with the command fastboot flash recovery recovery.img and got:
target reported max download size of 471859200 bytes
sending 'recovery' (32034 KB)...
OKAY [ 1.012s]
writing 'recovery'...
OKAY [ 0.200s]
finished. total time: 1.222s
WOOT! Awesome! No problems! Then I issued: fastboot boot recovery.img
And got
downloading 'boot.img'...
OKAY [ 1.020s]
booting...
FAILED (remote: Command not allowed)
finished. total time: 1.030s
WTF?!
So after a bit, I misread and flashed boot.img with: fastboot flash boot boot.img
I guess I flashed the wrong image. I dunno. But now it boots into the screen that tells me "Your device is unlocked and can'r be trusted" tells me its booting, reboots, goes to the same screen again, says its rebooting again, then brings me to Huawei eRecovery. I connect to my wifi network, telling it to download the latest version and recover, and it says "getting package info failed" So I ma stuck with a device that won't boot.
Oh yes, and down volume and power don't bring me to fastboot anymore.
Begging for help here please.
Do the whole rebranding to unbrick, not sure if you flashed wrong image on boot.
Advice: When flashing recovery boot it by powering off and using key combo. Or adb command. Not from fastboot as IMG.
I did a google search on rebranding to unbrick, and found a guide on the 9. So I assume its similar. It first tests me to boot into twrp. I can't. Twrp never got installed. The next step is to get the offical firmware and put it on the SD card. I can't find it. I am in Canada, and can't find any firmware for canada, nevermind anything north american. It is however possible I have found the wrong guide, as I don't really know what I am doing. As a complete noob, links to guides would be nice when possible and available when making recommendations.
The guide is the same for Mate 9/pro and P10/plus
Original: https://forum.xda-developers.com/mate-9/how-to/guide-mate-9-flash-update-package-t3593108
Explained as easy as posible:
Unlock bootloader (check again that boot loader is unlocked)
Download Update ZIP. I suggest rebrand to VTR-L29 C432 !
A. Get ROM update link through hwmt.ru. Click "filelist.xml". ---> http://hwmt.ru/hwmtsite/firmware-database/?firmware_model=VTR-L29&firmware_page=0
B. Observe "update.zip" size, choose more than 1GB file size FULL OTA . Example VTR-L29C432B164 filelist Link, all three update files and path are in the filelist.xml content.
update.zip: Change URL last "filelist.xml" to "update.zip" download file.
update_data_public.zip: Change URL last "filelist.xml" to "public/update_data_full_public.zip" download file, and rename it to "update_data_public.zip"
update_all_hw.zip: Change URL last "filelist.xml" to "hw/spcseas/update_full_hw_spcseas.zip" download file, and rename it to "update_all_hw.zip" Where spcseas is the model of the file you are downoloading.
Update Package (Download these at original post)
Base: HWOTA_2017050101_Base.zip
OS: Windows -> HWOTA_2017050101_Windows.zip
Model: P10 -> HWOTA_2017050201_VTR.zip [Thanks to @crucky verify]
Put HWOTA on pc desktop and on your external SD card (if you have one, otherwise update process will took a couple of minutes more)
Those 3 downloaded files goes on UPDATE dir, inside HWOTA
Run batch file "update.bat" for same model update or rebrand with/without sdcard.
Select rebrand chose what model is desired (Must be the same as the update package)
Always check the process continues (Sometimes it stucks on twrp or need reconnect to PC)
Once finished Factory default reset will start
Do the process twice! select "Same model update" on the second time.
After update successfully, device might be locked again.
smariob said:
The guide is the same for Mate 9/pro and P10/plus
Original: https://forum.xda-developers.com/mate-9/how-to/guide-mate-9-flash-update-package-t3593108
Explained as easy as posible:
Unlock bootloader (check again that boot loader is unlocked)
Download Update ZIP. I suggest rebrand to VTR-L29 C432 !
A. Get ROM update link through hwmt.ru. Click "filelist.xml". ---> http://hwmt.ru/hwmtsite/firmware-database/?firmware_model=VTR-L29&firmware_page=0
B. Observe "update.zip" size, choose more than 1GB file size FULL OTA . Example VTR-L29C432B164 filelist Link, all three update files and path are in the filelist.xml content.
update.zip: Change URL last "filelist.xml" to "update.zip" download file.
update_data_public.zip: Change URL last "filelist.xml" to "public/update_data_full_public.zip" download file, and rename it to "update_data_public.zip"
update_all_hw.zip: Change URL last "filelist.xml" to "hw/spcseas/update_full_hw_spcseas.zip" download file, and rename it to "update_all_hw.zip" Where spcseas is the model of the file you are downoloading.
Update Package (Download these at original post)
Base: HWOTA_2017050101_Base.zip
OS: Windows -> HWOTA_2017050101_Windows.zip
Model: P10 -> HWOTA_2017050201_VTR.zip [Thanks to @crucky verify]
Put HWOTA on pc desktop and on your external SD card (if you have one, otherwise update process will took a couple of minutes more)
Those 3 downloaded files goes on UPDATE dir, inside HWOTA
Run batch file "update.bat" for same model update or rebrand with/without sdcard.
Select rebrand chose what model is desired (Must be the same as the update package)
Always check the process continues (Sometimes it stucks on twrp or need reconnect to PC)
Once finished Factory default reset will start
Do the process twice! select "Same model update" on the second time.
After update successfully, device might be locked again.
Click to expand...
Click to collapse
okay, i know you are trying to be helpful, but I just can't follow it...
You said "Download Update ZIP. I suggest rebrand to VTR-L29 C432 !" Which one of them? Is the B just a build number, and I should get the latest? please remember, you are talking to a noob.
You talk about 3 files, update.zip, update_data_public.zip and update_all_hw.zip Do I need them all? If so the last one, where I change filelist.xml to all /cn/update_full_all_cn.zip doesn't work. See the following link http://update.hicloud.com:8180/TDS/.../v92067/f2/full/all/cn/update_full_all_cn.zip
Also, rename the file, "Where spcseas is the model of the file you are downoloading" Huh? I know I have to replace the word spcseas with something, but with that?
Now it says to run update.bat Whats the point? I have not been directed to plug the phone into the computer, and even if I did, the computer won't recognize it because I can't get it into any mode... Where do I put these files? They all go in the same directory? I just can't follow this guide as much as I try..
THERE IS GOOD NEWS HOWEVER!
I have been able to get it into TWRP! This means I can get into fastboot, which means I can re-flash the correct boot.img, IF I can get my hands on it (and assuming that's the actual issue It likely is. It was working until I flashed this other boot.img file.). So if I can get direction on how to get it, I should be okay. Double triple and quadruple bonus points for just providing me a direct link to the boot.img file to use without having to play around trying to follow guides I can't seem to understand.
UPDATE!!
Now although I can get into TWRP, its hit and miss, but I can get there eventually, it will no longer boot into fastboot/recovery. When I click reboot, and choose bootloader in TWRP, it just freezes..
This is getting frustrating. Apparently getting into the bootloader is hit and miss, but i can do it.
Search for Huawei update extractor in order to get BOOT.IMG from update.app (inside update zip) I could upload one myself, but I'm not at home right now.
TWRP doesn't support reboot atm. You must power off completly. To boot to recovery press power on and vol + until huawei logo appears, then relase power. It should boot to recovery TWRP in this case.
For boot bootloader you press vol - when you are connecting usb cable to PC.
smariob said:
The guide is the same for Mate 9/pro and P10/plus
Original: https://forum.xda-developers.com/mate-9/how-to/guide-mate-9-flash-update-package-t3593108
Explained as easy as posible:
Unlock bootloader (check again that boot loader is unlocked)
Download Update ZIP. I suggest rebrand to VTR-L29 C432 !
A. Get ROM update link through hwmt.ru. Click "filelist.xml". ---> http://hwmt.ru/hwmtsite/firmware-database/?firmware_model=VTR-L29&firmware_page=0
B. Observe "update.zip" size, choose more than 1GB file size FULL OTA . Example VTR-L29C432B164 filelist Link, all three update files and path are in the filelist.xml content.
update.zip: Change URL last "filelist.xml" to "update.zip" download file.
update_data_public.zip: Change URL last "filelist.xml" to "public/update_data_full_public.zip" download file, and rename it to "update_data_public.zip"
update_all_hw.zip: Change URL last "filelist.xml" to "hw/spcseas/update_full_hw_spcseas.zip" download file, and rename it to "update_all_hw.zip" Where spcseas is the model of the file you are downoloading.
Update Package (Download these at original post)
Base: HWOTA_2017050101_Base.zip
OS: Windows -> HWOTA_2017050101_Windows.zip
Model: P10 -> HWOTA_2017050201_VTR.zip [Thanks to @crucky verify]
Put HWOTA on pc desktop and on your external SD card (if you have one, otherwise update process will took a couple of minutes more)
Those 3 downloaded files goes on UPDATE dir, inside HWOTA
Run batch file "update.bat" for same model update or rebrand with/without sdcard.
Select rebrand chose what model is desired (Must be the same as the update package)
Always check the process continues (Sometimes it stucks on twrp or need reconnect to PC)
Once finished Factory default reset will start
Do the process twice! select "Same model update" on the second time.
After update successfully, device might be locked again.
Click to expand...
Click to collapse
smariob said:
Search for Huawei update extractor in order to get BOOT.IMG from update.app (inside update zip) I could upload one myself, but I'm not at home right now.
TWRP doesn't support reboot atm. You must power off completly. To boot to recovery press power on and vol + until huawei logo appears, then relase power. It should boot to recovery TWRP in this case.
For boot bootloader you press vol - when you are connecting usb cable to PC.
Click to expand...
Click to collapse
Thats good to know. I was getting TWRP more often when I did it from off. What was happening was I would holds power and volume up, release power when the logo appeared, and MOST of the time I would boot into TWRP. Sometimes it would just reboot, I would continue to hold up, and it would either reboot, or boot into TWRP. Occasionally I would get the recovery that came with the phone ?!?!
In any event, I managed to get into TWRP, boot into recovery, extract the boot.img, flash it... AND IT WORKED! Phone booted!
So after all this, I backed up EVERYTHING I could using TWRP. The Boot partition, System partition, EVERYTHING! It kept failing on the Data partition, but from my research that wasn't that important anyway. I then installed SuperRoot_noverity_nocrypt.zip, rebooted, installed phh's SuperUser, installed Root Checker, and finally, I have root!!
Thank you so much for the help. About to go "thank clicking" for all the help you provided.
He guys,
as you've read I bricked my phone and I don't know how or where I did the mistake?
Status before brick:
-) FW: EMUI 8.xxx (not exactly sure which one it was)
-) TWRP: 3.2.3.0
-) Rooted
-) BL: unlocked
-) PHONE Unlock
-) FRP Unlock
What I wanted to do:
-) FW Update to: EMUI 9.0 via FirmwareFinder
What I've done:
-) Did a Titanium Backup
-) Installed Firmware Finder
-) Downloaded the Firmware CLT-L29C432E5R1P9B195 (9.0.0.195) (BUT there were ONLY 2 files)
-) 1. file was "update.zip"
-) 2. file was "update_full_CLT-L29_hw_eu.zip"
-) Renamed the files to
-) 1. kept file name "update.zip"
-) 2. file renamed "update_full_CLT-L29_hw_eu.zip" --> update_all_hw.zip
-) Put the 2 files + hurupdater_04.zip + recovery.img (TWRP 3.2.1.0.img) to a folder in Root on my device
-) Reboot to recovery -> TWRP
-) TWRP -> Install -> hurupdater_04.zip
ERRORS:
-) first I saw a message --> "CLT-L09 "Firmware installing --> how can that happened, if I downloaded the CLT-L29 version?
-) Then it aborted the installing process
Current situation:
-) TWRP is installed again --> TWRP 3.2.1.-0 by Pretorian
-) PHONE Unlock
-) FRP Unlock
-) no OS
!! Cannot access my files either via TWRP or Windows explorer --> all files are encrypted and have totally weird names
So please, please help me installing an OS again!
!! And is there a chance to get access to my pictures back???
I appreciate every helpfull advise.
Thanks in advance!!!
He guys,
nobody has an idea to solve/help me with my issues/situation?
I searched the forum and also other forums and pages to find a solution to "my" problem, but without any helpful results.
I am afraid of doing an eRecovery restore because of losing all my data.
I have currently: TWRP installed -> Files/folders with weird names (shown in TWRP & Phone connected to PC "Explorer")
What can I do to save, restore, copy my pictures and files from phone to PC?
Please give me some hints.
This way brought me back
Try downloading the firmware here: FIRMWARE
Then follow these instructions: HEREhttps://forum.xda-developers.com/huawei-p20-pro/development/huawei-p20-pro-charlotte-l29c432b131-8-t3809964
Got me out of a pinch a few times.
Vedrick said:
Try downloading the firmware here: FIRMWARE
Then follow these instructions: HEREhttps://forum.xda-developers.com/huawei-p20-pro/development/huawei-p20-pro-charlotte-l29c432b131-8-t3809964
Got me out of a pinch a few times.
Click to expand...
Click to collapse
Thanks for the help and the links.
BUT before I'll start doing this, there is just one issue left: the encrypted "storage / files" (pics etc.) in TWRP.
BEFORE I want to say, that I've removed all the security barriers like fingerprint, pattern and faceID !!!!
I tried using this https://forum.xda-developers.com/huawei-p20-pro/development/recovery-twrp-3-2-1-0-t3779400
with different kinds of TWRP versions:
TWRP 3.2.1-0.img
twrp_clt_0.1.img frome here
https://forum.xda-developers.com/huawei-p20-pro/development/recovery-twrp-3-2-1-0-t3779400
twrp-3.2.1-0-charlotte-mod.img frome here
https://forum.xda-developers.com/huawei-p20/how-to/how-to-how-to-unbrick-clt-l29c432-t3878714
twrp-3.2.3-4-charlotte.img
But nothing works, my files shown in TWRP -> storage are still encrypted and still shown with weird gibberish names?
Do you know how to solve this, or where I can get the right TWRP version?
I'm totally at the end of ideas and not finding the right way to get access to my pictures and stuff again.
Da_Hausa said:
Thanks for the help and the links.
BUT before I'll start doing this, there is just one issue left: the encrypted "storage / files" (pics etc.) in TWRP.
BEFORE I want to say, that I've removed all the security barriers like fingerprint, pattern and faceID !!!!
I tried using this https://forum.xda-developers.com/huawei-p20-pro/development/recovery-twrp-3-2-1-0-t3779400
with different kinds of TWRP versions:
TWRP 3.2.1-0.img
twrp_clt_0.1.img frome here
https://forum.xda-developers.com/huawei-p20-pro/development/recovery-twrp-3-2-1-0-t3779400
twrp-3.2.1-0-charlotte-mod.img frome here
https://forum.xda-developers.com/huawei-p20/how-to/how-to-how-to-unbrick-clt-l29c432-t3878714
twrp-3.2.3-4-charlotte.img
But nothing works, my files shown in TWRP -> storage are still encrypted and still shown with weird gibberish names?
Do you know how to solve this, or where I can get the right TWRP version?
I'm totally at the end of ideas and not finding the right way to get access to my pictures and stuff again.
Click to expand...
Click to collapse
I honestly don't think any twrp will work, another reason i'll never buy a huawei again. You could try extracting the image files from the update.app that you get from the update.zip file. then manually flash:
You can extract the image files using EMUI Extractor Application.
fastboot flash cust cust.img
fastboot flash system system.img
I believe the pictures are located on the userdata partition. be sure to flash the right android version as it may depend on what framework you have and how far you got when it was updating. You may want to verify the location of those pictures first.
SO I replicated your soft brick, after I backup up my photos. I ccouldn't save them. I'm up and running though. Turns out I had to first manually flash those image files located in update.app. Then I had to do this
Modified\Updated (Bricked device fix)
1) Try downloading the firmware here: FIRMWARE
2) Extract the update.app file from the update.zip, then use EMUI extractor to extract all the image files. You'll then need to manually flash a few of them: (You can move all these images into the main folder of the Reflash tools located in step 3, then run CMD-HERE)
Commands: (Some might error, i forget which but its alright)
fastboot flash cust cust.img
fastboot flash cache cache.img
fastboot flash kernel kernel.img
fastboot flash recovery_ramdisk recovery_ramdis.img (Very Important)
fastboot flash recovery_vbmeta recovery_vbmeta.img
fastboot flash recovery_vendor recovery_vendor.img
fastboot flash vbmeta vbmeta.img
fastboot flash vector vector.img
fastboot flash system system.img
fastboot reboot, unplug the USB-C cable and hold the volume up button. this will put you into recovery mode.
Then you'll need to format data using with the EMUI recovery and if given the option format cache.
Reboot back into bootloader\Download mode.
3) Then follow these instructions: HEREhttps://forum.xda-developers.com/huawei-p20-pro/development/huawei-p20-pro-charlotte-l29c432b131-8-t3809964
Got me out of a pinch a few times.
Unfortunately I seem to have the same issue. I followed @Vedrick's tutorial.
However after fastboot reboot I'm stuck on 'Your device is booting now...'
Any ideas?
I worry that perhaps the 'boot image' on my p20 is messed up. However in the .APP file I can't find the boot image to restore. I do however see 2 SYSTEM images.
nvm! Got it! Had to fastboot erase userdata.