Related
Hey guys, love all the work that goes on in this forum.
I've run into a bit of a problem. My mate gave me his phone to try and fix after he interrupted a factory reset. It's stuck in a bootloop.
It's a RAZR HD and was originally from Telstra (Aus).
I've managed to unlock the bootloader, but quickly after that everything has gone to hell.
When I turn the phone on, it gives the bootloader is unlocked message. Then the android installation guy comes up and after about 5 seconds of trying to install the phone bootloops.
I am able to enter the Android System Recovery (3e) and have done factory reset/wipe data and wipe cache options, however does not change anything. When I press reboot system, the bootloop continues as if I did nothing. I have tried installing a ROM from an SD card however it fails at the Verifying Package stage. I am unable to adb push anything as usb debugging wasn't turned on.
I am able to enter into fastboot and can see my device however cannot flash any images from there for some reason using the fastboot commands (it comes up with a <bootloader> variable not supported! error: cannot load '[name of image file]'
I was able to use RSD Lite to flash the official Telstra ROM to the phone, however at the very end of the installation when it rebooted, it just went into the bootloop again.
Any help would be muchly appreciated.
Thanks guys!
Anyone?
I was able to get adb sideload to work (I had the wrong path name to the zip file) but still no luck...
piCARSO said:
Anyone?
I was able to get adb sideload to work (I had the wrong path name to the zip file) but still no luck...
Click to expand...
Click to collapse
try mfastboot and flash the partition table first, if that fails, there is no hope of saving the device. if it passes, flash the rest of the files, including the wipe command.
bweN diorD said:
try mfastboot and flash the partition table first, if that fails, there is no hope of saving the device. if it passes, flash the rest of the files, including the wipe command.
Click to expand...
Click to collapse
Thanks for the reply. When you say flash the partition table first, would that be the partition_signed file (aka mfastboot flash partition partition_signed)?
piCARSO said:
Thanks for the reply. When you say flash the partition table first, would that be the partition_signed file (aka mfastboot flash partition partition_signed)?
Click to expand...
Click to collapse
yes, thats correct.
i rooted my deviced. Used systemless root. in the hope OTA would work when a update arrived.
Now there is a update but.... it says the update fails. (in dutch).
I used supersu unroot, but it still says update failed.
I tried using the MDM tools as here: https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/91996
... but that is giving a bogus cannot connect to internet message (I think it just means that there is no server for the g4 phone, internet is fine and fast on phone and pc)
I want the update but Now i am stuck:
-I do not want to re-lock the phone
-I do want the update. (euret -> may to juli security update)
Questions:
-Are there any meaning full error messages.. anywhere?
-are there other ways to flash the OTA?
-I see flashing stock should work. But is my unrooted rom different from stock?
You don't need to relock your bootloader to take the OTA-Update. Maybe the SuperSU "unroot" option was not 100% successful and the boot.img is still modified in anyway. And maybe you had make some other changes to your /system partition, any changes result in an error.
First you have to download the stock-rom for your device -> http://www.filefactory.com/folder/c6cdedc45a775d27/?sort=created&order=DESC&show=100
Then flash only boot.img, recovery.img and all system.img_sparsechunk.0-7 files via fastboot.
Edit: With only flashing boot, recovery and system no data should be lost.
Edit: and maybe logo.bin when you had removed the unlocked warning
After that your are able to take the OTA-Update and root it again with this guide -> http://forum.xda-developers.com/moto-g4-plus/how-to/root-systemless-rooting-supersu-2-74-2-t3405772
downloading XT1642_ATHENE_MPJ24.139-48_cid50_subsidy-DEFAULT_CFC.xml.zip now.
is only option anyway because after trying to flash supersu it won't boot anyway. (but still boots into fastboot mode.. no brick yet)
thx
have you used xposed? or custom kernel?
Bender1987 said:
You don't need to relock your bootloader to take the OTA-Update. Maybe the SuperSU "unroot" option was not 100% successful and the boot.img is still modified in anyway. And maybe you had make some other changes to your /system partition, any changes result in an error.
First you have to download the stock-rom for your device -> http://www.filefactory.com/folder/c6cdedc45a775d27/?sort=created&order=DESC&show=100
Then flash only boot.img, recovery.img and all system.img_sparsechunk.0-7 files via fastboot.
Edit: With only flashing boot, recovery and system no data should be lost.
After that your are able to take the OTA-Update and root it again with this guide -> http://forum.xda-developers.com/moto-g4-plus/how-to/root-systemless-rooting-supersu-2-74-2-t3405772
Click to expand...
Click to collapse
Thank you for this information Bender. I was wondering the exact same thing. I am rooted on a Moto G4 and i was wondering if a OTA update, or reflashing stock would wipe my data + all installed apps.
If i do it your way it shouldn't be any concerns?
srgudhka said:
have you used xposed? or custom kernel?
Click to expand...
Click to collapse
no only supersu and modified hosts file with adaway (main reason for root is titanium backup)
flashed boot, recovery and system with
Code:
fastboot oem fb_mode_set
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 system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
system boots now with all user data intact in may 2016 update.
However system update nows says it is up to date. .... maybe they retracted the update temporary? ... patience.... (reteu).
@leuk_he
I have a RETEU version here in germany and download the XT1621-XT1622-XT1642_ATHENE_MPJ24.139-23.4_cid50_subsidy-DEFAULT_CFC.xml.zip file, which had the same build no as my g4+.
If you try to flash files from the wrong rom, you get an error while flashing or lost temporary your WiFi and IMEI till you find and flash the right one.
So compare the build no on your phone and the stock rom file.
@Zajbot
As long as you don't wipe cache or data or use fastboot erase userdata, all your data should be there.
I have done the same yesterday and all data is still on my phone
---------- Post added at 13:16 ---------- Previous post was at 13:11 ----------
You don't need the OEM fb_mode_set.
Try it again in few hours or reboot, the update should pop-up again, don't worry.
Wifi and imei info are correct(NL) I checked the XT1642_ATHENE from the bootloader screen (did not know this number)
but... patience is a hard one.... :crying::crying: ... and if people say "don't worry... i worry..." bad habit.
Build number accorindg to phoneinfo is MPJ24.139-48 ... but i think that is what i just flashed. Not sure if that is what was in the phone before.
i added the oemset becuase it cried about wrong signature on boot.img it still did afterwards.
@leuk_he
Then you have maybe the wrong ROM. I flashed boot recovery and system and had no errors. But my build no. matches before the update.
You can download my OTA-update zip from my drive and sideload it manually with stock recovery.
If the update have a wrong build no. you only get an error.
https://drive.google.com/file/d/0B8Pa0dVQxQjHcm8xU2ZfcGk4VUE/view?usp=drivesdk
Bender1987 said:
@leuk_he
You can download my OTA-update zip from my drive and sideload it manually with stock recovery.
If the update have a wrong build no. you only get an error.
https://drive.google.com/file/d/0B8Pa0dVQxQjHcm8xU2ZfcGk4VUE/view?usp=drivesdk
Click to expand...
Click to collapse
How does the sideload works?
Thanks
@Marv42
1. Download the .zip file to SD card.
2. Reboot into Stock Recovery -> Hold "Volume DOWN" while starting your phone.
3. Hold "Power + Volume UP" few seconds, then you get to recovery menu.
4. Choose "Apply update from SD card".
5. Choose .zip file.
6. Wait and watch the log, take +20min, then there is an "error" or "success" msg.
7. "Reboot system now"
Bender1987 said:
@Marv42
1. Download the .zip file to SD card.
2. Reboot into Stock Recovery -> Hold "Volume DOWN" while starting your phone.
3. Hold "Power + Volume UP" few seconds, then you get to recovery menu.
4. Choose "Apply update from SD card".
5. Choose .zip file.
6. Wait and watch the log, take +20min, then there is an "error" or "success" msg.
7. "Reboot system now"
Click to expand...
Click to collapse
Didn't work for me. I get the bootloadermenu and when I switched to RECOVERY I got the ANDROID-Picture with "No Command".
Flashing a new recovery.img don't change anything.
Is a sideload flah with adb possible?
@Marv42
When the dead Android shows up -> Power + Volume UP
Try it few times, then the recovery menu shows up.
Bender1987 said:
@Marv42
When the dead Android shows up -> Power + Volume UP
Try it few times, then the recovery menu shows up.
Click to expand...
Click to collapse
I think there is a problem with my recovery. I flashed the recovery from rom-zip
Edit: get the recovery
Edit 2.: Give up, get with my and yours OTA.zip a sideload mistake (number 7). Now I wait for the next OTA, next days will be hard without ROOT
@Marv42
You can easily root with the method mentioned in post #2, just boot into TWRP and make sure you follow ALL steps in the guide.
Bender1987 said:
@Marv42
You can easily root with the method mentioned in post #2, just boot into TWRP and make sure you follow ALL steps in the guide.
Click to expand...
Click to collapse
thanks for your hint, I start it tomorrow, have a good night
For the root, in the future, don't FLASH the TWRP, just BOOT into it, so you can apply SU for systemless root. Don't skip the step of creating the extra file.
This way you are still having the standard recovery.
SoNic67 said:
For the root, in the future, don't FLASH the TWRP, just BOOT into it, so you can apply SU for systemless root. Don't skip the step of creating the extra file.
This way you are still having the standard recovery.
Click to expand...
Click to collapse
I haven't flash the TWRP, I always boot by mfastboot to TWRP
Bender1987 said:
@leuk_he
You can download my OTA-update zip from my drive and sideload it manually with stock recovery.
If the update have a wrong build no. you only get an error.
https://drive.google.com/file/d/0B8Pa0dVQxQjHcm8xU2ZfcGk4VUE/view?usp=drivesdk
Click to expand...
Click to collapse
Tried sideloading with twrp , but it gave error 7 on build number. "this device has . "
thx anyway for sharing.
I will now try load older system images with older build number.
/edit:
Flashed MJP-..23 like bender and it now says a update is availble.
interesting side note. when using the build-48 it already showed battery indicator on motowake screen but still at may-2016 security update.
Hi. I was trying to install cm13 on my honor 8. I unlocked the bootloader, but while trying to install twrp recovery I think I deleted everything off the phone. The huawei erecovery doesn't work, and I tried sooooo many fastboot commands. I can't do adb commands. I can only get into fastboot mode. Is there anyway for me to get out of this? I tried flashing the system.img and boot.img from fastboot but it fails.
LuneTech said:
Hi. I was trying to install cm13 on my honor 8. I unlocked the bootloader, but while trying to install twrp recovery I think I deleted everything off the phone. The huawei erecovery doesn't work, and I tried sooooo many fastboot commands. I can't do adb commands. I can only get into fastboot mode. Is there anyway for me to get out of this? I tried flashing the system.img and boot.img from fastboot but it fails.
Click to expand...
Click to collapse
Was ur bootloader and frp in unlocked state ?
Sent from my KIW-L22 using Tapatalk
gopinaidu77 said:
Was ur bootloader and frp in unlocked state ?
Click to expand...
Click to collapse
Yes. And it still is
LuneTech said:
Yes. And it still is
Click to expand...
Click to collapse
So u can still recovery your phone
Sent from my KIW-L22 using Tapatalk
LuneTech said:
Hi. I was trying to install cm13 on my honor 8. I unlocked the bootloader, but while trying to install twrp recovery I think I deleted everything off the phone. The huawei erecovery doesn't work, and I tried sooooo many fastboot commands. I can't do adb commands. I can only get into fastboot mode. Is there anyway for me to get out of this? I tried flashing the system.img and boot.img from fastboot but it fails.
Click to expand...
Click to collapse
Hi, i have the exact same problem...
Have you figgerd it out?
Lucas Napik said:
Hi, i have the exact same problem...
Have you figgerd it out?
Click to expand...
Click to collapse
Yes. I installed a roll back update (something like that) by getting into the force update mode. After it finished, I had to then apply the full stock firmware. The problem was that I somehow put the firmware of another phone, because my model number was from a different Huawei phone.
trying to get back to stock
gopinaidu77 said:
So u can still recovery your phone
Sent from my KIW-L22 using Tapatalk
Click to expand...
Click to collapse
Hi. I got tired of CM13, so I tried to go back to stock. I checked a guide online which told me to flash 2 files using TWRP. after that, I lost twrp and now my bootloader is locked. What do I do? I manually did an update with the update.app file, and it says update success, but when it reboots it stays on the honor 8 screen, I waited for 25 minutes and it's still there.
LuneTech said:
Hi. I got tired of CM13, so I tried to go back to stock. I checked a guide online which told me to flash 2 files using TWRP. after that, I lost twrp and now my bootloader is locked. What do I do? I manually did an update with the update.app file, and it says update success, but when it reboots it stays on the honor 8 screen, I waited for 25 minutes and it's still there.
Click to expand...
Click to collapse
Try going into stock recovery and doing a factory reset after you use the update.app. You'll have to unlock the bootloader again and flash twrp if you want root.
Restoring to MM using a full image will typically lock the bootloader.
It happened to me too, it is possible you still didn't use the right image.
This is how I recovered mine:
1. Go here to download the latest firmware for your model: https://www.androidfilehost.com/?w=files&flid=129406
2. Use the Huawei Update Extractor to extract files from the "Update.app". (Ignore the 'profile' drop down list in the app.)
3. Unlock your phone's bootloader.
4. Flash these four images (extracted using the tool from step 2):
fastboot flash boot boot.img
fastboot flash cust cust.img
fastboot flash recovery recovery.img
fastboot flash system system.img
5. Boot into recovery and do a factory reset. This is needed to reformat the internal storage (and make it encrypted I think). (Power+Vol Up)
6. Put the Update.app file inside the "dload" folder in your SDcard.
7. Boot into flash mode to let the phone flash the Update.app (Power+Vol Up+Vol Down).
eksasol said:
It happened to me too, it is possible you still didn't use the right image.
This is how I recovered mine:
1. Go here to download the latest firmware for your model: https://www.androidfilehost.com/?w=files&flid=129406
2. Use the Huawei Update Extractor to extract files from the "Update.app". (Ignore the 'profile' drop down list in the app.)
3. Unlock your phone's bootloader.
4. Flash these four images (extracted using the tool from step 2):
fastboot flash boot boot.img
fastboot flash cust cust.img
fastboot flash recovery recovery.img
fastboot flash system system.img
5. Boot into recovery and do a factory reset. This is needed to reformat the internal storage (and make it encrypted I think). (Power+Vol Up)
6. Put the Update.app file inside the "dload" folder in your SDcard.
7. Boot into flash mode to let the phone flash the Update.app (Power+Vol Up+Vol Down).
Click to expand...
Click to collapse
2 things, 1 is that there are 2 recovery files in the UPDATE.APP, and 2 is that I can't do a factory reset from the recovery, because it brings me to the erecovery and it doesn't give me the option to factory reset.
LuneTech said:
2 things, 1 is that there are 2 recovery files in the UPDATE.APP, and 2 is that I can't do a factory reset from the recovery, because it brings me to the erecovery and it doesn't give me the option to factory reset.
Click to expand...
Click to collapse
You need to hold VOLUME UP and POWER button with the phone off to get into the recovery to do a factory reset. Once the honor logo pops up, you can release the power and volume up buttons.
Recovery.img = Stock recovery
Recovery2.img = eRecovery
eksasol said:
It happened to me too, it is possible you still didn't use the right image.
This is how I recovered mine:
1. Go here to download the latest firmware for your model: https://www.androidfilehost.com/?w=files&flid=129406
2. Use the Huawei Update Extractor to extract files from the "Update.app". (Ignore the 'profile' drop down list in the app.)
3. Unlock your phone's bootloader.
4. Flash these four images (extracted using the tool from step 2):
fastboot flash boot boot.img
fastboot flash cust cust.img
fastboot flash recovery recovery.img
fastboot flash system system.img
5. Boot into recovery and do a factory reset. This is needed to reformat the internal storage (and make it encrypted I think). (Power+Vol Up)
6. Put the Update.app file inside the "dload" folder in your SDcard.
7. Boot into flash mode to let the phone flash the Update.app (Power+Vol Up+Vol Down).
Click to expand...
Click to collapse
I just did everything exactly the way you said. But it still stays at the honor boot logo. I don't mind waiting over night for it to boot up if I have to, but I've never had a phone take this long to boot up, even on first boot.
For a "brick" thread, it seems odd that the model is never mentioned so that someone can really point you to the right spot. If you keep going to erecovery, then it has to do with whether or not your cable is plugged in (likely you've been keeping it plugged in for your fastboot attempts, or that's a guess). I only go to erecovery with both up/down & power if the cable is plugged in. If I want to get to stock recovery (regardless of what the hell is in the "recovery" partition, TWRP, or who knows?) then I unplug it before trying any key combo from power off to get there.
Lastly, if you use this sort of thing as a template (I'm just going to use one for the frd-l09 as an example, but stick the right model in there for you) ::
Example to plug into Google to find your rollback with instructions:: site:consumer.huawei.com honor 8 frd-l09 rollback
Click to expand...
Click to collapse
So if you've got an frd-l04 then plug that in where frd-l09 is. It'll just look on the site consumer.huawei.com just above where the various country/variant breakdowns are, like US/ZH/HU/Etc. are.
Pick the one out that is closest to what it seems you want. All the pages are in the local languages so I'm guessing the .pdf that explains what to do is in the language you'll want as well.
Good luck:: Let us know what model phone you have.
More: Contents of first "intermediate" update.app is 8 image files. I'm sure the 2nd one that is specifically your own phone's version of b162 has a lot more files in it. I've not looked for awhile but I think it's 21 or 22 files. This is a two step process, first is all the crap that comes in update.app from the rollback page (just a 100K file which sets you up in intermediate state for rollback) and 2nd you find your exactly right b162 for your model phone, and pretty much repeat the process.
Yet More: One odd thing about the Honor 8: I've not seen it on other phones is the partition layout is not really "trustworthy" unless you really have gotten to understand it. There appears to be at least 3 or 4 places you can get to that I used to think would all have to be in the recovery partition, but apparently the Honor 8 works differently, so no matter how bleak your odds seem, .. maybe not. I got to both erecovery and stock recovery and rollback while TWRP was installed and it worked just following the directions from their website.
Agreed on this thing.
eksasol said:
It happened to me too, it is possible you still didn't use the right image.
This is how I recovered mine:
1. Go here to download the latest firmware for your model: https://www.androidfilehost.com/?w=files&flid=129406
2. Use the Huawei Update Extractor to extract files from the "Update.app". (Ignore the 'profile' drop down list in the app.)
3. Unlock your phone's bootloader.
4. Flash these four images (extracted using the tool from step 2):
fastboot flash boot boot.img
fastboot flash cust cust.img
fastboot flash recovery recovery.img
fastboot flash system system.img
5. Boot into recovery and do a factory reset. This is needed to reformat the internal storage (and make it encrypted I think). (Power+Vol Up)
6. Put the Update.app file inside the "dload" folder in your SDcard.
7. Boot into flash mode to let the phone flash the Update.app (Power+Vol Up+Vol Down).
Click to expand...
Click to collapse
Thank you very much, you saved me and my phone !!!
I made a mistake: my phone was under android m and I flashed by mistake the rollback update (to go m from n), then my honor was bricked on bootloop, no recovery, no update by dload....nothing worked....
Your solution was the right one !! again thank you very much
Interesting observation with the eRecovery (recovery2 partition). So I have TWRP installed, the system partition modified and user storage not encrypted. I was still able to to use eRecovery to connect to WiFi and download the factory image and it automatically repaired the phone to factory state. I noticed it doesn't re-lock the bootloader afterward. This seems to be the easiest method to unbrick.
Getting into eRecovery.
hi! Or extract the files? sorry for my english
eksasol said:
It happened to me too, it is possible you still didn't use the right image.
This is how I recovered mine:
1. Go here to download the latest firmware for your model: https://www.androidfilehost.com/?w=files&flid=129406
2. Use the Huawei Update Extractor to extract files from the "Update.app". (Ignore the 'profile' drop down list in the app.)
3. Unlock your phone's bootloader.
4. Flash these four images (extracted using the tool from step 2):
fastboot flash boot boot.img
fastboot flash cust cust.img
fastboot flash recovery recovery.img
fastboot flash system system.img
5. Boot into recovery and do a factory reset. This is needed to reformat the internal storage (and make it encrypted I think). (Power+Vol Up)
6. Put the Update.app file inside the "dload" folder in your SDcard.
7. Boot into flash mode to let the phone flash the Update.app (Power+Vol Up+Vol Down).
Click to expand...
Click to collapse
Ok after the factory reset (which is peppered with mounting errors)...
failed to mount /data (invalid arguments)
unable to mount storage
When I try to flash cust.img and system.img they both fail.
I cannot check what firmware I was on before I started all this, but I believe it was the latest one. This is a FRD-04. I flashed TWRP 3.1.0.1 erecovery and I can access it and fastboot.
I have tried various different things and nothing I do can unbrick the phone. Any help would be appreciated.
menriquez said:
Ok after the factory reset (which is peppered with mounting errors)...
failed to mount /data (invalid arguments)
unable to mount storage
When I try to flash cust.img and system.img they both fail.
I cannot check what firmware I was on before I started all this, but I believe it was the latest one. This is a FRD-04. I flashed TWRP 3.1.0.1 erecovery and I can access it and fastboot.
I have tried various different things and nothing I do can unbrick the phone. Any help would be appreciated.
Click to expand...
Click to collapse
have the same problem as you on my FRD-09.
I don't have this phone anymore, but the easiest way I find to restore it is using eRecovery.
The issue I am having is that my honor 8 (FRD-L14) is stuck on "your device is booting now.." and it does not shut down. If I hold the power button until it shuts down then it restarts by itself and it keep doing the same thing over and over.
When it first starts and the blue screen and the logo come up the phone vibrate twice and then it displays "your device is booting now..." and it gets stuck there
Here is what I can and cant do:
I can go into fastboot and it shows that the phone is unlocked and the FRP is unlocked
I can flash TWRP from there and I can go into TWRP
When I check in TWRP for partitions I can see CUST or DATA and it shows that the INTERNAL STORAGE size is ZERO
I was able to create the system partition but I am not sure if I did it right.
the dload folder on the SD Card has the role back but the three finger thing (vol+ and vol- and power does not start the system restore from update.app) instead it gets stuck on " your device is booting now..."
I tried Huawei_Multi-Tool and I chose the "unbrick option"...I extracted system.img, boot.img, recovery.img and cust.img and the tool was able to push all images to the device but still the device does not start.
The original stock recovery is not accessible either even if I flash the stock recovery image from TWRP
Any tips on how to resolve this?
Thanks in advance guys
fidzi_1981 said:
The issue I am having is that my honor 8 (FRD-L14) is stuck on "your device is booting now.." and it does not shut down. If I hold the power button until it shuts down then it restarts by itself and it keep doing the same thing over and over.
When it first starts and the blue screen and the logo come up the phone vibrate twice and then it displays "your device is booting now..." and it gets stuck there
Here is what I can and cant do:
I can go into fastboot and it shows that the phone is unlocked and the FRP is unlocked
I can flash TWRP from there and I can go into TWRP
When I check in TWRP for partitions I can see CUST or DATA and it shows that the INTERNAL STORAGE size is ZERO
I was able to create the system partition but I am not sure if I did it right.
the dload folder on the SD Card has the role back but the three finger thing (vol+ and vol- and power does not start the system restore from update.app) instead it gets stuck on " your device is booting now..."
I tried Huawei_Multi-Tool and I chose the "unbrick option"...I extracted system.img, boot.img, recovery.img and cust.img and the tool was able to push all images to the device but still the device does not start.
The original stock recovery is not accessible either even if I flash the stock recovery image from TWRP
Any tips on how to resolve this?
Thanks in advance guys
Click to expand...
Click to collapse
You said you can go into TWRP right. Just rebrand the device to L19 :angel:
First format data
Then flash the rebrand.zip
Then reboot and if it doesn't boot first go into recovery and factory reset then let it boot up again.
Try flashing stock recovery.img using fastboot. Can you now enter into the 3-button combination mode?
wasiq224 said:
Try flashing stock recovery.img using fastboot. Can you now enter into the 3-button combination mode?
Click to expand...
Click to collapse
He said he tried to enter recovery with no luck, and he also tried the 3 button dload method.
wasiq224 said:
Try flashing stock recovery.img using fastboot. Can you now enter into the 3-button combination mode?
Click to expand...
Click to collapse
I tried flashing the stock recovery but it does not work. I also tried the 3-buttons and it did not work either
when I go into TWRP it shows that the size of the internal storage is ZERO
damenbm said:
You said you can go into TWRP right. Just rebrand the device to L19 :angel:
First format data
Then flash the rebrand.zip
Then reboot and if it doesn't boot first go into recovery and factory reset then let it boot up again.
Click to expand...
Click to collapse
Where can I find the rebrand.zip file?
Here are the full instructions :victory:
https://forum.xda-developers.com/honor-8/how-to/guide-honor-8-to-frd-l19-t3632220
damenbm said:
Here are the full instructions :victory:
https://forum.xda-developers.com/honor-8/how-to/guide-honor-8-to-frd-l19-t3632220
Click to expand...
Click to collapse
Thanks. I will give it a try and flash it and see if it can re-create the missing partitions :fingers-crossed::fingers-crossed:
fidzi_1981 said:
Thanks. I will give it a try and flash it and see if it can re-create the missing partitions :fingers-crossed::fingers-crossed:
Click to expand...
Click to collapse
Best of luck :angel: let me know how it goes please!
damenbm said:
He said he tried to enter recovery with no luck, and he also tried the 3 button dload method.
Click to expand...
Click to collapse
Yes, but he tried the dload method before flashing stock recovery, and he was flashing stock recovery using twrp rather than fastboot.
Thanks but I tried dload after I flashed the stock recovery.
And I tried flashing the stock recovery using facebook and twrp and neither ways succeeded
fidzi_1981 said:
Thanks but I tried dload after I flashed the stock recovery.
And I tried flashing the stock recovery using facebook and twrp and neither ways succeeded
Click to expand...
Click to collapse
Did the rebrand work? Did it make you go back to stock?
damenbm said:
Did the rebrand work? Did it make you go back to stock?
Click to expand...
Click to collapse
Not yet. I'm at work. I'll give it a go tonight
For me it worked after trying to get my FRD-L09 back to work again after I couldnt flash system and not boot anywhere but twrp.
Thanks for the help!
fidzi_1981 said:
Not yet. I'm at work. I'll give it a go tonight
Click to expand...
Click to collapse
I had the same exact issue 5 days ago.
Here's what I did to solve it
NOTE - This is FRD-L14 SPECIFIC
First, Download these files -
1) FRD-L04 Original Recoveries and Boot Image
2) FRD-04 Rollback Package from Huawei
3) FRD-L04 Official MM ROM from Huawei
4) FRD-L14 Specific Stock MM ROM Update.zip
Assuming Bootloader is unlocked
Here's what you should do
-Unzip the Recoveries and Boot image folder
-Unzip Rollback Package
-Make a folder called "dload" (without the quotes) in the root of your SD Card
-Place the Update.app from the Rollback Package in there
-Make sure you have ADB and Fastboot installed - Installer
-Boot into fastboot by Plugging in your USB Cable and Holding Power + Volume Down. This may take multiple tries and multiple reboots to get it right depending on the reboot loop.
-Once phone is in Fastboot, go into the Recoveries and Boot folder, hold Shift and right Click. Click on open Command Window Here.
-If the option says "Powershell" instead, open Command prompt manually, and cd to that directory, or change this option in your settings.
-With command prompt open, do -
Code:
fastboot flash recovery recovery.img
Code:
fastboot flash recovery2 recovery2.img
Code:
fastboot flash boot boot.img
IMPORTANT - Make sure you unplug the cable from the phone and are ready to press both volume buttons at the same time after it reboots
If you dont get it the first time,hold all 3 buttons at the same time to make it reboot and go into that mode.
Code:
fastboot reboot
-Remove cable, press both Buttons at the same time
-It should go into stock recovery and start flashing the Rollback package
-Wait for it to finish, it should reboot automatically
-After it reboots, you should notice that it went back to the same state it was, so reboot into fastboot and flash recovery, recovery2, and the boot image again.
-This time, put the Update.app from the Official L04 Rom you downloaded from the Huawei website in the "dload" folder of the SDCard
-Fastboot Reboot, Remove cable, and Press buttons again. This time it will flash the Official ROM, so it will take longer.
-If it says error right at 99%, reboot, it flashed correctly but it displays an error.
-If it says error anytime before the end of flash, reboot and try again.-After it reboots, you will notice you are able to boot again. BUT, you are not able to update due to it being branded as L04, sooooo
-Place the Update.app from the 4th link (L14 Specific ROM) in the "dload" folder of SD Card
-Three button method into the recovery flash again.
-It will start to flash the L14 Specific ROM on top of the L04 one.
-After it flashes it and reboots, reboot one more time once you are inside android so it encrypts the ROM.
-(Optional) Update to Nougat, apply other updates after that (There's like 3 Updates I think)
-At this point you have a 100% Stock FRD-L14 Honor 8 but, you can also
-(Optional) Reunlock Bootloader
-Profit?
JvaOneShotzXprX said:
I had the same exact issue 5 days ago.
Here's what I did to solve it
NOTE - This is FRD-L14 SPECIFIC
First, Download these files -
1) FRD-L04 Original Recoveries and Boot Image
2) FRD-04 Rollback Package from Huawei
3) FRD-L04 Official MM ROM from Huawei
4) FRD-L14 Specific Stock MM ROM Update.zip
Assuming Bootloader is unlocked
Here's what you should do
-Unzip the Recoveries and Boot image folder
-Unzip Rollback Package
-Make a folder called "dload" (without the quotes) in the root of your SD Card
-Place the Update.app from the Rollback Package in there
-Make sure you have ADB and Fastboot installed - Installer
-Boot into fastboot by Plugging in your USB Cable and Holding Power + Volume Down. This may take multiple tries and multiple reboots to get it right depending on the reboot loop.
-Once phone is in Fastboot, go into the Recoveries and Boot folder, hold Shift and right Click. Click on open Command Window Here.
-If the option says "Powershell" instead, open Command prompt manually, and cd to that directory, or change this option in your settings.
-With command prompt open, do -
Code:
fastboot flash recovery recovery.img
Code:
fastboot flash recovery2 recovery2.img
Code:
fastboot flash boot boot.img
IMPORTANT - Make sure you unplug the cable from the phone and are ready to press both volume buttons at the same time after it reboots
If you dont get it the first time,hold all 3 buttons at the same time to make it reboot and go into that mode.
Code:
fastboot reboot
-Remove cable, press both Buttons at the same time
-It should go into stock recovery and start flashing the Rollback package
-Wait for it to finish, it should reboot automatically
-After it reboots, you should notice that it went back to the same state it was, so reboot into fastboot and flash recovery, recovery2, and the boot image again.
-This time, put the Update.app from the Official L04 Rom you downloaded from the Huawei website in the "dload" folder of the SDCard
-Fastboot Reboot, Remove cable, and Press buttons again. This time it will flash the Official ROM, so it will take longer.
-If it says error right at 99%, reboot, it flashed correctly but it displays an error.
-If it says error anytime before the end of flash, reboot and try again.-After it reboots, you will notice you are able to boot again. BUT, you are not able to update due to it being branded as L04, sooooo
-Place the Update.app from the 4th link (L14 Specific ROM) in the "dload" folder of SD Card
-Three button method into the recovery flash again.
-It will start to flash the L14 Specific ROM on top of the L04 one.
-After it flashes it and reboots, reboot one more time once you are inside android so it encrypts the ROM.
-(Optional) Update to Nougat, apply other updates after that (There's like 3 Updates I think)
-At this point you have a 100% Stock FRD-L14 Honor 8 but, you can also
-(Optional) Reunlock Bootloader
-Profit?
Click to expand...
Click to collapse
Thanks! i will give this a try since flashing the rebranding zip file that was suggested in one of the posts did not work out for me.
However, do you think that this w=method will work despite the fact that I do not have a valid DATA or CUST partitions?
Thanks again for responding to my post!!
fidzi_1981 said:
Thanks! i will give this a try since flashing the rebranding zip file that was suggested in one of the posts did not work out for me.
However, do you think that this w=method will work despite the fact that I do not have a valid DATA or CUST partitions?
Thanks again for responding to my post!!
Click to expand...
Click to collapse
No problem!
That shouldn't matter, this will get you to 100% stock, so all of those partitions will be reflashed.
JvaOneShotzXprX said:
No problem!
That shouldn't matter, this will get you to 100% stock, so all of those partitions will be reflashed.
Click to expand...
Click to collapse
It worked!!!
Thanks a lot!
but this is what happened:
After i flashed recovery, recovery2 and boot images, I rebooted the phone and it went straight to stock recovery and it asked me download stock firmware and stock recovery which was 1.66GB so I allowed and it downloaded it and flashed everything and did a reset and the phone booted normally.
The stock firmware that it downloaded and flashed was B122 MM.
One question though, does the flashing sequence of the recovery, recovery2 and boot matter?
Before you posted your post, I had tried flashing these three files in the following order: boot, then recovery then recovery2 but it never worked.
Also, the three images that tried to flash were extracted from the update.app from this firmware (FRD-L14C567B162_FULL) so I was not sure what was going wrong.
Thanks again for your help!! :victory::good::highfive:
fidzi_1981 said:
It worked!!!
Thanks a lot!
but this is what happened:
After i flashed recovery, recovery2 and boot images, I rebooted the phone and it went straight to stock recovery and it asked me download stock firmware and stock recovery which was 1.66GB so I allowed and it downloaded it and flashed everything and did a reset and the phone booted normally.
The stock firmware that it downloaded and flashed was B122 MM.
One question though, does the flashing sequence of the recovery, recovery2 and boot matter?
Before you posted your post, I had tried flashing these three files in the following order: boot, then recovery then recovery2 but it never worked.
Also, the three images that tried to flash were extracted from the update.app from this firmware (FRD-L14C567B162_FULL) so I was not sure what was going wrong.
Thanks again for your help!! :victory::good::highfive:
Click to expand...
Click to collapse
It shouldn't matter, but I included it because sometimes those get corrupted like what happened to me. I'll probably be testing it out completely and making a guide. Looks like you had it better than I did though! I'm glad you got it fixed! :highfive:
JvaOneShotzXprX said:
It shouldn't matter, but I included it because sometimes those get corrupted like what happened to me. I'll probably be testing it out completely and making a guide. Looks like you had it better than I did though! I'm glad you got it fixed! :highfive:
Click to expand...
Click to collapse
Thanks for the help again. I would not have been able to rescue the phone without your tips. :good::highfive:
I'm not so happy with EMUI 8/Oreo on my Mate 9. Several widgets don't update, requiring me to change the screen resolution during the day (weird temporary fix). I'd rather run Nova but EMUI pushes against that. I have a pretty good backup phone (ZTE Axon 7) so I thought I would give a generic system image a try. The last time I rooted and installed an alternative ROM was 2014, so I'm rusty. I successfully put minimal fastboot on a PC, unlocked the bootloader and installed TWRP 3.2.1-0 (something may have gone wrong already at this point since I accessed it by vol up + power, rather than vol up + vol down + power). Then I installed the generic system image. It booted, but gave error messages at boot. Perhaps all I needed to do was install it a second time, but instead I tried installing a different image, achieved bootloop, made matters worse, and was rescued by the amazing and wonderful FunkyHuawei.
I am thinking about trying again, but I wondered if an expert would write a more patient guide that provides the exact steps to flashing a generic system image. By the exact steps, I mean with links to files and what you type in minimal fastboot (if indeed that is the right program), or when it is best to install from an SD card. I'm sure such a guide would get more people to try other ROMs besides the generic ROM.
prestonmcafee said:
I'm not so happy with EMUI 8/Oreo on my Mate 9. Several widgets don't update, requiring me to change the screen resolution during the day (weird temporary fix). I'd rather run Nova but EMUI pushes against that. I have a pretty good backup phone (ZTE Axon 7) so I thought I would give a generic system image a try. The last time I rooted and installed an alternative ROM was 2014, so I'm rusty. I successfully put minimal fastboot on a PC, unlocked the bootloader and installed TWRP 3.2.1-0 (something may have gone wrong already at this point since I accessed it by vol up + power, rather than vol up + vol down + power). Then I installed the generic system image. It booted, but gave error messages at boot. Perhaps all I needed to do was install it a second time, but instead I tried installing a different image, achieved bootloop, made matters worse, and was rescued by the amazing and wonderful FunkyHuawei.
I am thinking about trying again, but I wondered if an expert would write a more patient guide that provides the exact steps to flashing a generic system image. By the exact steps, I mean with links to files and what you type in minimal fastboot (if indeed that is the right program), or when it is best to install from an SD card. I'm sure such a guide would get more people to try other ROMs besides the generic ROM.
Click to expand...
Click to collapse
By a generic system image, you are referring to wanting to install an aosp image (treble ROM), correct?
Yes.
prestonmcafee said:
Yes.
Click to expand...
Click to collapse
And obviously you still have your bootloader unlock code?
Also what Mate 9 version do you have and what exact firmware is it running?
I can help ya out no problem. Just obviously want to make sure you avoid going through that again
Thanks, Wirmpolter! I have the unlock code, but it shows as unlocked, at least I get the dire warning about the device being unsafe on boot. I have the US model, build number MHA-L29 9.0.0.360 (C567), with both Android and EMUI versions listed as 8.0.0.
Sorry, MHA-L29 8.0.0.360 (C567)
prestonmcafee said:
Thanks, Wirmpolter! I have the unlock code, but it shows as unlocked, at least I get the dire warning about the device being unsafe on boot. I have the US model, build number MHA-L29 9.0.0.360 (C567), with both Android and EMUI versions listed as 8.0.0.
Click to expand...
Click to collapse
Oh...You're already bootloader unlocked that makes it even easier.
I'm using the system.IMG form the thread below this paragraph. Tried a few different aosp ROMs and it seems to be the best so far. Aside from a couple things of course. And the honor 8 Pro is the same CPU, GPU found in the mate 9.
https://forum.xda-developers.com/honor-8-pro/development/rom-t3758564.
In the main post of that thread, just follow step 2 and 3 and you'll be good to go for having an aosp ROM.
As for magisk/root... You can follow my guide below that I posted the other day. Just let the aosp ROM boot up once first. Also I can extract the ramdisk.IMG you'll need if you can't once you check it over.
https://forum.xda-developers.com/mate-9/how-to/guide-install-magisk-mate-9-running-t3773878
Basically in a nutshell to get setup on an aosp ROM is as follows
1 Download the ROM from the first thread i posted
2 Extract the system.img to where your adb folder is
3 Run command prompt from there
4 With your phone powered off. Hold the volume up button and connect it to your computer (fastboot screen)
5 Run command fastboot flash system system.img
6 Then type fastboot reboot but when you goto run this command get ready to hold the volume up button when the screen goes off so you can get the phone into stock recovery
7 Once in the recovery, perform a factory reset
8 Reboot the phone and should be good to go
Need to do first boot on its own before rooting
Thanks!!!
It will be about a week before I can try again but I'm looking forward to it. Are you pretty happy with it?
prestonmcafee said:
Thanks!!!
It will be about a week before I can try again but I'm looking forward to it. Are you pretty happy with it?
Click to expand...
Click to collapse
Yeah, fairly happy about it. A few bugs though but nothing major. Get better standby drain and about the same SOT time as EMUI. The only thing that is lacking is the camera in aosp doesn't use both cameras.
There is the stock camera port (works with magisk) but it's lacking a few things like video recording doesn't work... And umm not sure what else.
I needed to install an update, enable developer options and enable OEM unlocking (which was greyed out) before it would install. Here is my earlier post:
Dang, didn't work. Here is what I did.
-reset phone, but did not enable developer options.
-extracted and placed system.img in the minimal fastboot and adb folder. Ran a command prompt with administrative rights (win 10)
-shut off and connected Huawei mate 9 by USB, holding vol up
-vol up brought the EMUI restore screen. Shut off and tried again, same outcome. So shut off and tried vol down, and that brought up the fastboot screen. It reported phone unlocked but FRP locked.
-ran command "fastboot flash system system.img" and get:
target reported max download size of 471859200 bytes
sending sparse 'system' 1/4 (460796 KB)...
OKAY [ 11.167s]
writing 'system' 1/4...
FAILED (remote: Command not allowed)
finished. total time: 11.183s
I suspect this is due to the FRP locked condition.
Now I've run into a different problem: the EMUI screen gives me the options of
Download latest version and recovery
Reboot
Shutdown
It does not give me the option of a factory reset. What seemed to work was holding volume down through a couple of boots, when EMUI gave me the option of a factory reset. This gave me what appears to be a fully functioning system!
prestonmcafee said:
Now I've run into a different problem: the EMUI screen gives me the options of
Download latest version and recovery
Reboot
Shutdown
It does not give me the option of a factory reset. What seemed to work was holding volume down through a couple of boots, when EMUI gave me the option of a factory reset. This gave me what appears to be a fully functioning system!
Click to expand...
Click to collapse
Yeah, the FRP lock would prevent fastboot commands from working.
So, your system is back up and running?
OK, now that I have it up and running, here is the procedure I used, fixing what are either typos or variations because my system was slightly different. I unlocked the bootloader using instructions from:
http://www.teamandroid.com/2017/04/08/huawei-mate-9-unlock-bootloader/
I used Minimal ADB and Fastboot from
https://forum.xda-developers.com/showthread.php?t=2317790
I downloaded and extracted the system image from the link Wirmpolter provided:
https://forum.xda-developers.com/honor-8-pro/development/rom-t3758564
Here is a slightly edited set of instructions that worked for me:
a. unlock bootloader
b. reset phone
c. enable developer mode (settings/system/about phone tap on build number until developer mode is enabled), enable OEM unlock and USB debugging
d. check that FRP unlock and bootloader unlock worked by booting into fastboot screen (for me, hold VOL DOWN while booting)
1 Download the ROM from the thread above
2 Extract the system.img to where your adb folder is
3 Run command prompt from there (or use MA&F's desktop icon, which does the same thing)
4 With your phone powered off. Hold the volume DOWN button and connect it to your computer (fastboot screen)
5 Run command: fastboot flash system system.img
6 Then type fastboot reboot but when you goto run this command get ready to hold the volume up button when the screen goes off so you can get the phone into stock recovery
7 Once in the recovery, perform a factory reset [eRecovery didn't have this option, so I rebooted a couple of times while holding vol up and it eventually gave me the option to factory reset]
8 Reboot the phone and should be good to go
Up and Running!
Wirmpolter said:
Yeah, the FRP lock would prevent fastboot commands from working.
So, your system is back up and running?
Click to expand...
Click to collapse
I'm up and running. Thanks! So far, the only glitches are:
While Android can see and format the SD card (a Samsung 64GB), the SD card is invisible over a USB connection and Google Maps and my music player can't see it. File explorer and copy files to the SD card, so the SD card works.
The camera is terrible, but you have a fix for that.
I'm quite lost about how to install Magisk and a camera module
At the risk of asking too much, I have another request. I'm looking at how to install the stock camera on my Mate 9 with the AOSP, and here is my pathetic understanding of the steps.
First, I looked at your (Wirmpolter) instructions:
1. Install latest Magisk Manager from the Official Thread: https://forum.xda-developers.com/app...mless-t3473445
Follow the instructions of "Install Via Magisk Manager" in the main thread, but instead of providing the boot image (which these devices do NOT have), provide the stock ramdisk.img extracted from your Update.app using Huawei Update Extractor.
2. If you are using Mate 9 with model MHA-L29636 running on firmware ending in B362, you can download the stock ramdisk.img I extracted from official OTAs in the attachments
If you have stock ramdisk images for other devices, please share them and I'll add them to the OP.
3. Pull the patched image with adb pull /sdcard/MagiskManager/patched_boot.img, and flash the patched ramdisk via fastboot:
fastboot flash ramdisk patched_boot.img
Reboot and you shall have a properly rooted device passing SafetyNet, start playing with some Magisk modules!
Here are some questions:
1. Huawei update extractor
https://forum.xda-developers.com/showthread.php?t=2433454
I probably need help using this. The item I need extracted is the update.app, but where do I get the update.app that I extract from? And I'm extracting ramdisk.img?
2. download file for my phone that will be the source of the update.app in #1 (MHA-L29 8.0.0.366(C567)) from FunkyHuawei? Firmware finder? or from the phone itself? (see, I'm pretty lost)
3. install magisk manager (from https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445):
This method does not need root, and also does not require a custom recovery.
However, you MUST have a stock boot image dump beforehand, and you also have to be able to flash the patched boot image, either through fastboot/download mode or ODIN
Install the latest Magisk Manager -- this is an android app? Do I sideload it?
If you're planning to flash the patched boot image through ODIN, go to Settings > Update Settings > Patched Boot Output Format, and select .img.tar. For normal users leave it as the default .img
Press Install > Install > Patch Boot Image File, and select your stock boot image file
Magisk Manager will now patch your boot image, and store it in [Internal Storage]/MagiskManager/patched_boot.img[.tar]
Copy the patched boot image to your PC. If you can't find it via MTP, you can pull the file with ADB:
adb pull /sdcard/MagiskManager/patched_boot.img[.tar]
Flash the patched boot image to your device and reboot. Here is the command if using fastboot:
fastboot flash boot /path/to/patched_boot.img
Magiskmanager is an android app. How do I install on my phone? I was expecting this to be a windows app that would install magisk on my phone, so was thrown when it was an .apk.
Finally, the camera image is here:
https://forum.xda-developers.com/showpost.php?p=75848917&postcount=2
It isn't clear to me how to flash using Magisk, but perhaps that will be obvious once I have magisk operating.
prestonmcafee said:
1. Huawei update extractor
https://forum.xda-developers.com/showthread.php?t=2433454
I probably need help using this. The item I need extracted is the update.app, but where do I get the update.app that I extract from? And I'm extracting ramdisk.img?
2. download file for my phone that will be the source of the update.app in #1 (MHA-L29 8.0.0.366(C567)) from FunkyHuawei? Firmware finder? or from the phone itself? (see, I'm pretty lost)
Click to expand...
Click to collapse
Firmware Finder (they have Windows desktop and Android apps for it, and there's also http://pro-teammt.ru/firmware-database/ which does the job just as well, though it's all in Russian.)
Find the FullOTA-MF firmware that corresponds to your model, download the 'update.zip' that goes with it - on the website, it's under the link 'update' in the same row. If you do it on your phone in the Firmware Finder app, hit "Download" on the relevant detail screen and it'll prompt you for which files you want.
Once you've got the update.zip, extract it, you'll find a file UPDATE.APP, which is what the extractor wants. If it throws up an error, disable CRC checking of the extracted content. (I don't recall what the label for it is and I don't have it installed on the machine in front of me...); and yes, you'll want RAMDISK.img from it.
prestonmcafee said:
3. install magisk manager (from https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445):
Magiskmanager is an android app. How do I install on my phone? I was expecting this to be a windows app that would install magisk on my phone, so was thrown when it was an .apk.
Click to expand...
Click to collapse
Magisk Manager wants to create a patched ramdisk image. When it updates, it'll want to update the ramdisk image on your device (which it'll be able to do since it's running with root privileges itself anyway), but for the first pass, it needs that image provided and for you to manually flash it.
Thanks!
That is perfect. I downloaded the correct file from FF and I will try installing Magisk tomorrow or Sunday.
prestonmcafee said:
That is perfect. I downloaded the correct file from FF and I will try installing Magisk tomorrow or Sunday.
Click to expand...
Click to collapse
The magisk manager app apk you just run on your phone to install it, no side loading required.
Thanks! Magisk installed! To flash the camera app, I first extract and flash kernel.img from update.app with fastboot, put the camera zip (extract first?) in the magisk folder on the phone to install it with magisk?
That worked
prestonmcafee said:
Thanks! Magisk installed! To flash the camera app, I first extract and flash kernel.img from update.app with fastboot, put the camera zip (extract first?) in the magisk folder on the phone to install it with magisk?
Click to expand...
Click to collapse
That seems to have worked.