Hello, I would like some help since I got this device just yesterday.
I got it with the EMUI 4 Android 6.0 stock installed on it. Since there was no update for it I unlocked the bootloader installed twrp rooted and manually flashed EMUI 5 7.0. Everything worked fine.
I created a backup through TWRP and restored it succefully multiple times.
Then I installed the Meticulus TWRP (since I was told it is a prerequisite for the AOSP). I Flashed the AOSP but it stuck during the boot animation (30 minutes afterwards I powered it off).
I reflashed my old TWRP and tried restoring my backup. IT fails with the explanation "Cannot wipe /vendor" while at the top it says "Cannot mount /vendor (invalid argument)" "Cannot mount /product (invalud argument)".
Anyone has a clue how to fix this? Fastboot adb all works so there should be a way to boot into an OS properly?
Since AOSP was not booting i guess you forgot formatting /data partition to ext4... And did u Used Stock vendor and not openkirin ones ?
Gesendet von meinem Honor 6X mit Tapatalk
As said I have replaced the custom TWRP with the default one so I think this should not apply anymore?
The "cannot mount vendor/product" messages came from the default TWRP after I reflashed it again.
At the top it says "cannot mount /vendor" either so I guess that is the actual problem?
It would be nice to get teh AOSP up but I really want to be able to boot into something first honestly.
And did u Used Stock vendor and not openkirin ones
Click to expand...
Click to collapse
Can you please explain? When I flashed your ROM i was on your TWRP. Does this even matter anymore?
At best I would be able to restore my backup.
To me it appears to be caused by the vendor partition.
Is there any way I can manually create that through TWRP?
algg said:
To me it appears to be caused by the vendor partition.
Is there any way I can manually create that through TWRP?
Click to expand...
Click to collapse
Yes you can but not creating it through twrp, but flashing it by fastboot mode: this is because
image (.img) files needs to be flashed by fastboot mode to avoid any kind of problem.
So, you should look for the last version of stock firmware on which you was before going custom, like BLN-L21CXXXB368 for example; tell me your build number and I'll find the package for you. Then, extract from the UPDATE.APP (a very big file that contains every partition in your phone like recovery, vendor, data, ecc. - you'll find this file inside the zip archive that contains the downloaded update) the vendor.img using Huawei Update Extractor, and then flash it through fastboot mode using the command "fastboot flash vendor vendor.img".
Otherwise, you could rely on dload method to reflash a full update package, and this should really fix everything since that it'll be like a new and clean installation of the OS. Then, unlocking the bootloader again and reflash TWRP to finally restore your previous backup made when it was working would be the final step.
Feel free to ask for further help
Thanks for the reply first really appreciate it.
I got the device on EMUI 4 Marshmallow rooted it and unlocked the bootloader then installed the BLN-L21C185B140 which worked smoothly.
I used that update.zip and extracted into dload root folder and started the huawei recovery installer but it said "package not found".
I tried flashing something to vendor before with fastboot but it said command not allowed.
Maybe I am doing something wrong?
algg said:
Thanks for the reply first really appreciate it.
I got the device on EMUI 4 Marshmallow rooted it and unlocked the bootloader then installed the BLN-L21C185B140 which worked smoothly.
I used that update.zip and extracted into dload root folder and started the huawei recovery installer but it said "package not found".
I tried flashing something to vendor before with fastboot but it said command not allowed.
Maybe I am doing something wrong?
Click to expand...
Click to collapse
Latest build on Nougat after the update was BLN-L22C185B140 so? If yes, the package that you need to download is that one. Unluckily i can't help about dload method, i never had fortune using dload because package verification always failed at 5%, i tried every combination but without success.
Command not allowed while flashing vendor image... but flashing others, like recovery or boot.img is allowed? If yes, i don't know what's causing this sorry... I'm sure that my friend @shashank1320 could surely help more than me about how using dload method correctly. Check his signature, it should contain a guide on how to use it
RedSkull23 said:
Latest build on Nougat after the update was BLN-L22C185B140 so? If yes, the package that you need to download is that one. Unluckily i can't help about dload method, i never had fortune using dload, i never be able to using it successfully because package verification always failed at 5%.
Command not allowed while flashing vendor image... but flashing others, like recovery or boot.img is allowed? If yes, i don't know what's causing this sorry... I'm sure that my friend @shashank1320 could surely help more than me about how using dload method correctly. Check his signature, it should contain a guide on how to use it
Click to expand...
Click to collapse
For fastboot yes flashing recovery or boot do work but vendor does not. Maybe the ISO is corrupted somehow I will try it again on a different machine now with the tool.
The link you posted the dload method from is the one where I initially found it as well so yea.
Also it shouldn't matter what I install since the only thing I need is the actual vendor (and product?) partition to work. I have a functional backup just TWRP cannot create/mount the partitions. So even a way to just create them without any data would actually fix my problem (at least I hope so?)
When trying to use Fastboot to flash the vendor/product img I get remote: Command not allowed (yes my bootloader is unlocked) although I can flash the recovery without any problem.
The dload method does not work as said. I placed the extracted content of the update.zip into the dload folder but the software "cannot find" the package.
algg said:
When trying to use Fastboot to flash the vendor/product img I get remote: Command not allowed (yes my bootloader is unlocked) although I can flash the recovery without any problem.
The dload method does not work as said. I placed the extracted content of the update.zip into the dload folder but the software "cannot find" the package.
Click to expand...
Click to collapse
@RedSkull23, thanks for the tag mate.
@algg, No need to flash the vendor image as you already had the stock vendor img.
Now what else you can try is to flash the stock recovery, boot to stock recovery, select factory reset and reboot. It should most probably fix the issue.
If not, reflash the TWRP, a regular TWRO available and not specific to elite or meticulous, but generic one given by OldDroid.
I hope you have downloaded the content for dload, if not, download these for B140.
Flash this via TWRP- http://update.hicloud.com:8180/TDS/...afnaf/update_data_full_BLN-L21_hw_meafnaf.zip
no further changes and Then use dload method for this file- http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1756/g1755/v105054/f1/full/update.zip
Try above and provide feedback. This is what I could think of best possible way to have everything with all system app working.
If not, let me know and I will try to help further.
Hi, I thought I need the vendor image since TWRP (all versions) tell me "Could not mount/wipe vendor" and "Could not mount/wipe product" "invalid argument" for both.
I tried the factory reset before but it does not work. It stops at 23% then shows a red exclamation mark and just goes to the original screen with the 3 buttons (restart, shutdown and wipe).
I am currently trying to get it to recognize my sd card. But somehow it does not work through TWRP it just does not recognize the 8GB SD Card. Also I am currently on the TWRP I was before all of this happened (3.1 openkirin). Without the SD Card recognized I can't put the dload files for it on it and in turn I can't use the dload.
I mean technically it should very well be possible to fix the device since it isn't a real brick and even TWRP and Fastboot load. It's just that all those little things are somehow ruining it.
Edit: I will get a new micro sd for some reason this one does nt work. I'll say then whether the flash then dload worked.
@shashank1320
Mind explaining why I should first use TWRP to flash something and then on top of it use dload?
And why those specific files?
algg said:
Edit: I will get a new micro sd for some reason this one does nt work. I'll say then whether the flash then dload worked.
@shashank1320
Mind explaining why I should first use TWRP to flash something and then on top of it use dload?
And why those specific files?
Click to expand...
Click to collapse
Sure, let me explain.
The first file is the data file which will install few systems apps like file manager, updater, themes, clock, fm radio etc. This will work via dload as well but the installation time is around 3-7 seconds so, over the course of time and flashing few times, i realised that these PV files cannbe flashed via TWRP and it works perfectly fine specific to PV files( twrp won't supoort other stock zips). We foash this first so that it updates your buld number and also does not replace the recovery with stock (as if you flash the main update zip first, it will replace with stock recovery so flashing the 2nd file will be quick but with unstable system apps, sometime).
Now we flash the main zip file with update.app via dload and it Install the main firmware for boot, vendor, recovery, system, usrdata etc.
Hope this explanation helps, if not let me know and I will rephrase myself.
It does help. I did all of this and now in the dload app I get "Software install failed Incompatibilty with current version please download the correct update package".
When I flashed the zip you linked me with TWRP it said "cannot mount /data /vendor /product". Appearently data cannot be mounted since it is encrypted.
Any clue as to what I am doing wrong? Or is this device now a real brick with functioning recovery but without OS?
Is there any way I can "debug" what is going on while the boot animation is playing?
What is confusing me is that the boot animation plays just normal but it simply does not continue to the actual OS.
algg said:
It does help. I did all of this and now in the dload app I get "Software install failed Incompatibilty with current version please download the correct update package".
When I flashed the zip you linked me with TWRP it said "cannot mount /data /vendor /product". Appearently data cannot be mounted since it is encrypted.
Any clue as to what I am doing wrong? Or is this device now a real brick with functioning recovery but without OS?
Click to expand...
Click to collapse
Not bricked..its just Data is not mounted or encryption. Should never encrypted it. NVM.
Do one thing, boot to twrp recovery. Try flashing and get error, then go to main TWRP page and click on reboot, select recovery out of 4 options( power off, system, bootloader and recovery). It will boot to recovery, now try flashing it again and see. Most if the time it helps.
Else, go to main page, select wipe, click on format rather than wipe here, it will prompt for typing Yes to confirm. Biit to recovery from main twrp page ( as mentioned above). And try this same thing of formatting data couple of times and then flash the zip and then dload.
I know these are tedious steps but inhave revived my device many a times with all these tricks after some efforts.
Good luck
YAY it works.
Just to recap what I did:
I flashed your thing first through TWRP tried to flash your other link with dload (which did NOT work)
Then I flashed the thing (emui5 Android 7 for Europe) through TWRP played in my old backup of exactly this through TWRP cleared dalvik & cache.
Then I waited 20 minutse and now it started.
Really thanks to all of you very nice people here. I would be very baffled if it wasnt able to repair the device since Fastboot and Recovery still work.
But Huaweis recovery is beyond terrible.
algg said:
YAY it works.
Just to recap what I did:
I flashed your thing first through TWRP tried to flash your other link with dload (which did NOT work)
Then I flashed the thing (emui5 Android 7 for Europe) through TWRP played in my old backup of exactly this through TWRP cleared dalvik & cache.
Then I waited 20 minutse and now it started.
Really thanks to all of you very nice people here. I would be very baffled if it wasnt able to repair the device since Fastboot and Recovery still work.
But Huaweis recovery is beyond terrible.
Click to expand...
Click to collapse
It is terrible indeed. Glad your phone working.
Thanks to @RedSkull23 for tagging, else I may have not responded as he was already involved and was helping as usual.:good:
algg said:
Really thanks to all of you very nice people here. I would be very baffled if it wasnt able to repair the device since Fastboot and Recovery still work.
But Huaweis recovery is beyond terrible.
Click to expand...
Click to collapse
I'm happy for you man, indeed it would be so bad, especially because you got this device 3 or 4 days ago if i didn't read bad, anyway what matters is that now it works. Are you able to restore the previous backup through TWRP now? (But before trying... Make a backup of your actual OS )
shashank1320 said:
It is terrible indeed. Glad your phone working.
Thanks to @RedSkull23 for tagging, else I may have not responded as he was already involved and was helping as usual.:good:
Click to expand...
Click to collapse
Are you joking man? I just tagged you for more help, but practically you helped him in everything, not me; I'm sure that you would noticed the thread and helped as always even without my tag, i just speeded up things for being helpful to algg.
algg, I'd like to apologize myself; i didn't vanished after tagging shashank, today i just was at work and obviously i was busy for help, but as i saw with pleasure he already helped you to restore your OS and that was the objective. Nice one, guys!
Related
So I unlocked this without much trouble, and then when I was attemoting to use adb to flash images to recovery partition, one would just not work, and I stupidly tried to force it, and now it boots and just sits there.
I've seen a different website saying the Q can run Jellybean, and it also has info on getting the stock rom back .. but NO files. I know how to use the damn recovery tools once theyre booted up - those articles were completely useless. I don;t know what else to do. I tried to get the files that argghhhh jad posted to dropbox but they are not available anymore.
Stuck and been trying to fix this for the last 12 hours
EDIT:
Found stock recovery stuff, but I dont think it's going to help any...
Nevermind I suppose
I see that I can try the stock rar file posted for someone else in here to put into recovery, hope it works, I just dont know if the nernel is ok, but I would think so. It stops at the "unlocked"notificaton screen. anyay, yeah. If I get jellybean on instead ill share the info,
I believe you need to fastboot your recovery, not adb. Then you may be able to flash something back on there.
Sent from my XT897 using xda premium
tetrabyt said:
I believe you need to fastboot your recovery, not adb. Then you may be able to flash something back on there.
Sent from my XT897 using xda premium
Click to expand...
Click to collapse
Thanks for the repl! S I actually have been using fastboot because adb for some reason just will not see the device (I checked the version and its correct supposedly). So what I did was take the WWRP rar, pull the contants out and make them into a .zip.and instaled with fastboot flash. The output looked ok:
sending 'userdata' (319120 KB)... OKAY [ 29.814s]
writing 'userdata'... OKAY [ 92.421s]
finished. total time: 122.235s
but what about all the other partitions? I jad done system earlier frok out of the stock zipfile. i think i may just try the entire Stock file insead, or maybe I am missing the fact that I beed to install the kernek into /boot, Any thoughts Thanks much!
EDIT: first im going to fastboot the recovery wit tue TWRP zip file, and try to install it from
I am a little confused, did you manage to get the recovery working? Looks like you were trying to flash the recovery img to your user data partition... Am I misreading your post.
-Saint
Whoaa just saw that. should have unzipped the recovery image and flashed it to the recovery partition with
Fastboot flash recovery recoveryfile.img
Then you can boot into recovery and flash one of the system dumps that these devs have generously posted for when we mess up like this...
Sent from my XT897 using xda premium
tetrabyt said:
Whoaa just saw that. should have unzipped the recovery image and flashed it to the recovery partition with
Fastboot flash recovery recoveryfile.img
Then you can boot into recovery and flash one of the system dumps that these devs have generously posted for when we mess up like this...
Sent from my XT897 using xda premium
Click to expand...
Click to collapse
is this the basic method at present for a stock restore? i was looking at the thread with the files for RSD lite, but i was confused as to whether that was working. thx!
ok so I messed up what to flash from recovery. I had grabbed copies of the system, data, boot, etc for all the partitions thinking i needed to do them all from outside using fastboot,
Herby6262 said:
ok so I messed up what to flash from recovery. I had grabbed copies of the system, data, boot, etc for all the partitions thinking i needed to do them all from outside using fastboot,
Click to expand...
Click to collapse
Ok, the easiest way to get your phone up and running again is to push the newest TWRP from here, put it in your tools folder and push w fastboot:
fastboot flash recovery openrecovery-twrp-2.3.1.0-asanti_c.img
fastboot reboot recovery
Make a backup to your external sd card so that TWRP creates the directory needed to restore the stock system & boot. You should delete this first backup later since it will be broken.
Then download a system & boot image from here, unzip to the /TWRP/BACKUPS/"serial#"/ folder on your external sd. Do full wipes for system, dalvik, & factory reset; then restore Stock from within TWRP. Should be good to go.
:edit:
Just saw that tetrabyt already hit on this, consider this post a more detailed revision.
i must be retardedly doing this the wrong way, i quickly get twrp into recovery and can get in there, and I have the stock photon .zip in 1 big zip and in separate pieces, but how do you get them to the external card.. windows 7 fails to recognize the phone with some message MTP device unknown so I can't transfer it that way ... I dont know. Im about to chuck this thing out the window and be done with it. The whole purpose was to be able to install apps to the sdcard, originally. Only fastboot works from a command prompt, adb doesnt do a damn thing, trying multiple versions of it. I give up
Herby6262 said:
i must be retardedly doing this the wrong way, i quickly get twrp into recovery and can get in there, and I have the stock photon .zip in 1 big zip and in separate pieces, but how do you get them to the external card.. windows 7 fails to recognize the phone with some message MTP device unknown so I can't transfer it that way ... I dont know. Im about to chuck this thing out the window and be done with it. The whole purpose was to be able to install apps to the sdcard, originally. Only fastboot works from a command prompt, adb doesnt do a damn thing, trying multiple versions of it. I give up
Click to expand...
Click to collapse
Do you have an sd adapter or another device you can plug the sd into to transfer from your pc? Does adb fail when booted into TWRP also? Tried uninstalling/re-installing drivers?
Might be able to make a data img you could flash through fastboot, so long as the folder structure was correct... then use recovery from internal storage. Not certain on this: /data/media/sdcard/TWRP/BACKUP/"serial#"/
Maybe someone else can jump in here, this would be my last resort. Use any way possible to get it on external sd first.
-Saint
fallnSaint said:
Do you have an sd adapter or another device you can plug the sd into to transfer from your pc? Does adb fail when booted into TWRP also? Tried uninstalling/re-installing drivers?
Might be able to make a data img you could flash through fastboot, so long as the folder structure was correct... then use recovery from internal storage. Not certain on this: /data/media/sdcard/TWRP/BACKUP/"serial#"/
Maybe someone else can jump in here, this would be my last resort. Use any way possible to get it on external sd first.
-Saint
Click to expand...
Click to collapse
I believe there is a system.img floating around here somewhere.
Check out this thread
http://forum.xda-developers.com/showthread.php?t=1894575
Sent from my XT897 using xda premium
tetrabyt said:
I believe there is a system.img floating around here somewhere.
Check out this thread
http://forum.xda-developers.com/showthread.php?t=1894575
Sent from my XT897 using xda premium
Click to expand...
Click to collapse
Thanks a ton for the help Saint, and others. I finally got it back in working order .. yay! Now to install that powermenu update someone made, and see about making android 4 opeate like the older versions, where you could install apps onto the external SD card. Am I correct in assuming they just F'ed it up by changing the /mnt names, while the software was not updated to accomodate those changes? Why the hell is internal memory now "sdcard" ... so odd. I have a friend whose internal storage is named "USB storage" on his phone. It's USB accessible .. but its a freakin flash card. So odd, and stupid. I really felt like 4.0 was a downgrade, personally. What improved? I see nothing, only things taken away (Im sure the underlying scheduler and thread management/memory mgmt is better, but you know what I mean .. anything visible?)
Herby6262 said:
Thanks a ton for the help Saint, and others. I finally got it back in working order .. yay! Now to install that powermenu update someone made, and see about making android 4 opeate like the older versions, where you could install apps onto the external SD card. Am I correct in assuming they just F'ed it up by changing the /mnt names, while the software was not updated to accomodate those changes? Why the hell is internal memory now "sdcard" ... so odd. I have a friend whose internal storage is named "USB storage" on his phone. It's USB accessible .. but its a freakin flash card. So odd, and stupid. I really felt like 4.0 was a downgrade, personally. What improved? I see nothing, only things taken away (Im sure the underlying scheduler and thread management/memory mgmt is better, but you know what I mean .. anything visible?)
Click to expand...
Click to collapse
Good to hear, glad you got her working again. As for how she runs, definitely snappier than older versions of android. Maybe just hardware, but I still see improvements w the wifes epic running ics, guessing that we will see better results once CM is dropped for this phone.
-Saint
Tried this, still stuck on Bootloader Unlocked Screen. TWRP restores don't seem to work right. I tried restoring an old backup I had of the boot/recovery/system with no luck. Everytime I wiped system/dalvik/cache/factory reset before restore. No errors show up.
So, I can go into fastboot, and I can flash files.
I tried RSD Lite 5.7 with this Zip
It flashes everything until RSD wants me to reboot. Then it reboots and gets stuck on the bootloader unlocked screen.
Any ideas?
[Edit] I flash CWM and found out that I can't mound /sdcard which doesn't seem right...
fallnSaint said:
Ok, the easiest way to get your phone up and running again is to push the newest TWRP from here, put it in your tools folder and push w fastboot:
fastboot flash recovery openrecovery-twrp-2.3.1.0-asanti_c.img
fastboot reboot recovery
Make a backup to your external sd card so that TWRP creates the directory needed to restore the stock system & boot. You should delete this first backup later since it will be broken.
Then download a system & boot image from here, unzip to the /TWRP/BACKUPS/"serial#"/ folder on your external sd. Do full wipes for system, dalvik, & factory reset; then restore Stock from within TWRP. Should be good to go.
:edit:
Just saw that tetrabyt already hit on this, consider this post a more detailed revision.
Click to expand...
Click to collapse
After RSD Lite, it might not have booted up because the system image was removed from the file to make it work. Probably if you flash TWRP after doing the RSD file, and restore Rangerbry's system backup, you might be good..
No Luck.
Just tried this.
Got the following Errors during only system restore:
E:Unable to mount '/cache'
E:unable to mount '/data'
Still stuck on Unlocked bootloader screen.
My emmc might be corrupted I think
I do have sprint insurance. Think they can reflash stock?
yogi2010 said:
After RSD Lite, it might not have booted up because the system image was removed from the file to make it work. Probably if you flash TWRP after doing the RSD file, and restore Rangerbry's system backup, you might be good..
Click to expand...
Click to collapse
coolroman123 said:
No Luck.
Just tried this.
Got the following Errors during only system restore:
E:Unable to mount '/cache'
E:unable to mount '/data'
Click to expand...
Click to collapse
Was that in CWM or TWRP recovery? Just trying to make sure the process was correct, haha. I have only started using TWRP on this device, but i think the 2 recoveries use different backup formats?
coolroman123 said:
Tried this, still stuck on Bootloader Unlocked Screen. TWRP restores don't seem to work right. I tried restoring an old backup I had of the boot/recovery/system with no luck. Everytime I wiped system/dalvik/cache/factory reset before restore. No errors show up.
So, I can go into fastboot, and I can flash files.
I tried RSD Lite 5.7 with this Zip
It flashes everything until RSD wants me to reboot. Then it reboots and gets stuck on the bootloader unlocked screen.
Any ideas?
[Edit] I flash CWM and found out that I can't mound /sdcard which doesn't seem right...
Click to expand...
Click to collapse
Can you boot to bootloader or just to fastboot? There are two control files in that RSD zip, one doesn't flash bootloader, try removing that one and forcing the reflashed bootloader. Then try restoring again. About all I can think of if it successfully flashes the other components... Maybe just restore system and not boot or data?
-Saint
Everything you need is here to return to stock WITH ota update.
http://forum.xda-developers.com/showthread.php?t=2001226
The only thing simple is the belief in simplicity.
Hi There, need some help if you can...any educated and experienced help would be appreciated thanks.
After downloading my stock firmware and extracting via Huawei update Extractor all the image files ( System, user data, Cache, etc) I backed up oeminfo and cust files via Rayglobe Knife and saving the extracted update.app file to my dload folder on SDCard and successfully resetting my phone to factory using the vol+/- and power method I was quietly confident to make the jump and flash a rom the Android 7.0 (N) Nougat beta on Huawei posted by Somboons
I followed the instructions and dirty flashed this thru TWRP as instructed which seemed to go ok until I tried to reboot, the phone booted to stock recovery so I wiped Dalvik, Cache and Factroy reset, this completed and it all went down hill from there, basically now just stuck at boot screen saying that its about to reboot but never moves unless I use button combos
(OK so yes I feel stupid now and I'll beat myself up so you don"t have to, but I reallyt thought that I could always get back to stock via my SDCard)
What I can do...
Phone can only boot to eRecovery ( with WIFI failed message )
I can go into fastboot ( shows Bootloader and FRP unlocked)
What i can't do...
Cant access my update file on SDCard....Trying to boot using vol+/- and power to access my dload/update.app file on my SDCard just freezes at initial boot screen and tells me to push vol up button for 3 second and this takes me to eRecovery where all i can do is reboot or shut down.
I can't adb sideload files " no SU Binary detected"
What I've tried...
I have tried Rayglobe knife UNBRICK option placing my extracted boot, cust, system, recovery .img files but his fails with my PC popping up and saying this operation can't be performed on this PC please contact developer so this fails.
I then tried to fastboot flash all the image files which seemed to work successfully but no changes to the situation.
I have tried to fastboot flash the update.app which went thru the sparse process of all seven files and then come up with error command can not complete ( something in those words)
I have tried to fastboot new stock recovery from my rom as well as TWRP recovery but nothing works even if it says seems to have completed in the adb command prompt.
I have a feeling this is to do with the encryption of the rom and now my system cannot recognise my partition and without recovery I have no way of mounting my sdcard.
Thank god I have my old and reliable Lumia 1520 to fall back on untill I get this sorted.
Any Help would be appreciated....thanks in advance
Are you able to boot into Huawei recovery?
Mickie.C said:
Hi There, need some help if you can...any educated and experienced help would be appreciated thanks.
After downloading my stock firmware and extracting via Huawei update Extractor all the image files ( System, user data, Cache, etc) I backed up oeminfo and cust files via Rayglobe Knife and saving the extracted update.app file to my dload folder on SDCard and successfully resetting my phone to factory using the vol+/- and power method I was quietly confident to make the jump and flash a rom the Android 7.0 (N) Nougat beta on Huawei posted by Somboons
I followed the instructions and dirty flashed this thru TWRP as instructed which seemed to go ok until I tried to reboot, the phone booted to stock recovery so I wiped Dalvik, Cache and Factroy reset, this completed and it all went down hill from there, basically now just stuck at boot screen saying that its about to reboot but never moves unless I use button combos
(OK so yes I feel stupid now and I'll beat myself up so you don"t have to, but I reallyt thought that I could always get back to stock via my SDCard)
What I can do...
Phone can only boot to eRecovery ( with WIFI failed message )
I can go into fastboot ( shows Bootloader and FRP unlocked)
What i can't do...
Cant access my update file on SDCard....Trying to boot using vol+/- and power to access my dload/update.app file on my SDCard just freezes at initial boot screen and tells me to push vol up button for 3 second and this takes me to eRecovery where all i can do is reboot or shut down.
I can't adb sideload files " no SU Binary detected"
What I've tried...
I have tried Rayglobe knife UNBRICK option placing my extracted boot, cust, system, recovery .img files but his fails with my PC popping up and saying this operation can't be performed on this PC please contact developer so this fails.
I then tried to fastboot flash all the image files which seemed to work successfully but no changes to the situation.
I have tried to fastboot flash the update.app which went thru the sparse process of all seven files and then come up with error command can not complete ( something in those words)
I have tried to fastboot new stock recovery from my rom as well as TWRP recovery but nothing works even if it says seems to have completed in the adb command prompt.
I have a feeling this is to do with the encryption of the rom and now my system cannot recognise my partition and without recovery I have no way of mounting my sdcard.
Thank god I have my old and reliable Lumia 1520 to fall back on untill I get this sorted.
Any Help would be appreciated....thanks in advance
Click to expand...
Click to collapse
I have solved so
https://www.dc-unlocker.com/DC-Phoenix-flash-repair-tutorial
warsangel said:
I have solved so
https://www.dc-unlocker.com/DC-Phoenix-flash-repair-tutorial
Click to expand...
Click to collapse
A very big thanks ....this worked with no hitches except I now have no service now have to find unlock code for sim and get rid of the Ascend 7 splash screen that appears before the original Huawei Boot screen.?
After the above issues with thanks to warsangel's suggestion to use DC_Phoenix, I have managed to get my phone back up and running...got sim working so I now can detect my network and call and text using HCU client.
I now want to get rid of the annoying splash screen on bootup that shows Huawei Ascend spalsh screen before the mate 8 factory Huawei animated boot up screen. I still cannot access my dload folder on SDCard using vol-/+ and power button combo and if I dial in to manufacturers settings using*#*#2846579#*#* when i select upgrade from sd card i get a "PT failed do you still want to continue" if i click yes it re installs the firmware but makes no changes at all. Does any one have any other ideas. Of how to clear the splash screen and get the phone working back on Mate 8 button and bootup settings. Everything else works perfectly just a couple of things that will niggle at me...just want to get it back to out of the box as I have the Original Firmware zip file for this phone and region. cheers
bluheart said:
Are you able to boot into Huawei recovery?
Click to expand...
Click to collapse
Hi blueheart...no I can't, I think this is my problem, I can get to fast boot and I can't fastboot anything now because the boot loader is locked with a different code than the original one that I paid for with dc-unlocker. I have manged thru HCU cLIENT to get my original imei number and serial number but this serial number doesnt show up when I fastboot devices, lists one that come with the Phoenix firmware I flashed which is an Ascend as this was a NXT image closest to my NXT-L09.
My problem still is that I seem to go in to 2G and lose the signal all the time, I'm thinking I need to enter more details in CDMA repair in HCU Client or am I going about this the wrong way???
Oh bru, no idea!
HCU client is good enough. Keep trying dload if your bootloader is locked, it will flash for sure. Phone isn't easy to brick.
bluheart said:
Oh bru, no idea!
HCU client is good enough. Keep trying dload if your bootloader is locked, it will flash for sure. Phone isn't easy to brick.
Click to expand...
Click to collapse
Cheers Mate, managed to get to dload/update now but this doesnt seem to give a full reset, but modem is holding a signal but intermittently will drop into no service. I managed via HCU to re enter my imei and serial but a different serial number showsup in my settings still ??? getting back to where i need to but the signal dropping is a real problem. The next step is to try and get bootloader unlocked....any advice from any one.... if I fastboot flash modem will this be enough to bring my base band back or is there another file I should be looking at? cheers
You need to have cust and oem info of your own area for best signal
bluheart said:
You need to have cust and oem info of your own area for best signal
Click to expand...
Click to collapse
Thanks....I have my backup oeminfo it isnt a .img or .app file it just says oeminfo (type=file) can i fast boot this ? or do I have to use SRKtool as I don't want to unlock bootloader.
DC-Phoenix tool lets me fastboot .img files via backdoor and app files can I convert the oeminfo file to and .img file?
Cheers
How did you do the back up?
You can flash via fastboot
bluheart said:
How did you do the back up?
You can flash via fastboot
Click to expand...
Click to collapse
Backup was done through Rom Manager but the back up isn't an image it's a series of files like system.ext4, boot.emmc.win etc with MD5 info files. I've re-rooted device and tried to use rom manager to restore but when it boots to TWRP recovery nothing happens??? and I can't see any of the files if I go into the twrp folder on the SDcard because they aren't zip or img file.
My biggest problem even after doing full factory reset, wipe cache or install my original firmware update.app file, it doesn't seem to over write the image file that I used to recover my phone with the DC-Phoenix app, every thing indicates that it has been successful, but when I boot up,, It never goes to the stock setup mode where you would normally, choose your region, set your pin etc....it's like my install is only a shell or part of my install is not overwriting the dgtks firmware file I used which was a Huawei Ascend 7. The system re-defaults after rest to this firmware. Anyone help me to get rid of it and get back to my stock please?
I can use my stock update.app but it's not installing over the NXT AL10_M00A095_Factory_firmware_Android_6.0_EMUI_4.0.dgtks that I use ( this was the closest firmware that they had ) I think I need to format my whole system to ext4 ??? especially the partition that it storing this data that is preventing me to get my stock firmware back....any help or advice on this ...thanks
Yes format via Huawei recovery then flash
Or
Root and flash via TWRP after unzipping
bluheart said:
Yes format via Huawei recovery then flash
Or
Root and flash via TWRP after unzipping
Click to expand...
Click to collapse
just to update....I tried formatting and resetting all partitions to ext4 format most of the partitioning was successful with the exception of Systrem and Cust...TWRP would allow me to do these....I did numerous wipes via TWRP and Stock RECOVERY but unfortunately even with a full update.app via sdcard / dload folder and fastboot update.app (my firmware) via DC-Phoenix I couldn't seem to get a full factory stock install, same problems as discussed above and file system always goes to Encrypting screen and then I end up with the Ascend 7 screen and settings with obviously the wrong base band for my region. So I hate to admit defeat, but I've relocked bootloader, reset as much as I can and sent off to the Huawei Workshop to see if they can reset all the partitons back to normal.
Hahaha
Cool, let's see
bluheart said:
Hahaha
Cool, let's see
Click to expand...
Click to collapse
Update: well I dodged a bullet today....I sent my Mate 8 away 5 days ago to the Huawei tech support up the other end of the country and it arrived back today, back to stock and they replaced the main board with no cost to me at all. I was sure that they would call foul play and charge me but I obviously did such a number on the phone and then cleaned up all traces that they couldn't make that call lesson learn't and I see a few other people having similar problems with the Beta Nougat Rom....that you may need to post a big warning and send them to this posting so they are fair warned. I think this thread is done....I might just leave my phone alone and no tweaking for a while
Absolutely true!
XDA is not a playground for kids
You need courage to keep the Mate's balls on fire and get burnt with the nuclear reactions while keeping the blame on self
spent the last 3 weeks ( NO LIE ) trying every method under the sun to get my device rooted
easy recowvery
Hard Recowvery
manual ADB and flashing img
tot updates
kdz downgrades
basically everything
im not sure what else to do if its even possible at this point
Device details
tmobile locked LG G5 (h830)
OEM unlocked
its on 20a firmware ( coming from 20i )
ive rooted and installed twrp on may phones so i have a vast knowledge of these things
a few observations are
phone seems like its rewriting stock recovery on each reboot
fastboot won't accept any commands, i get "writing 'recovery'...FAILED (remote: unknown command)"
both hard recowvery and easy recowvery work up to the part of twrp install then it reboots to nothing
FINAL NOTE
im wondering if t-mobile is blocking the fastboot commands since im on temp unlock via device unlock app
if thats not a thing idk whats wrong im hoping one of you great minds can help this poor soul
Anyone?
Did you check oem unlock in developer options
rflores said:
Did you check oem unlock in developer options
Click to expand...
Click to collapse
thanks for replying ,
yes i did
its greyed out now but its been off
the fastboot commands says its unlocked as well
Did you make sure to download the recovery image and put in the root directory of the device storage and rename it recovery? If not then non of the recowvery methods will work. Also twrp needs to be the newest image. When using easy recowvery you should hit option 5 and enter then option 7 and enter and then option 0 and enter then option 2 and enter. Select y for yes when prompted and let the program do its thing. You should be prompted to boot into recovery at the end and it will go into tarp recovery. Hit cancel when it asks for password. Then go to wipe and format. After formatted, you need to install no-opt enc or root and then you're done. If you want to update all you have to do is get latest firmware from this forum. Also' if you update you need to also re flash no opt enc or root again and I also delete recovery from boot.p file in recovery. Should be good to go!
speters04 said:
Did you make sure to download the recovery image and put in the root directory of the device storage and rename it recovery? If not then non of the recowvery methods will work. Also twrp needs to be the newest image. When using easy recowvery you should hit option 5 and enter then option 7 and enter and then option 0 and enter then option 2 and enter. Select y for yes when prompted and let the program do its thing. You should be prompted to boot into recovery at the end and it will go into tarp recovery. Hit cancel when it asks for password. Then go to wipe and format. After formatted, you need to install no-opt enc or root and then you're done. If you want to update all you have to do is get latest firmware from this forum. Also' if you update you need to also re flash no opt enc or root again and I also delete recovery from boot.p file in recovery. Should be good to go!
Click to expand...
Click to collapse
thanks for this reply
i will try this as soon as i get home
thanks in advance
speters04 said:
Did you make sure to download the recovery image and put in the root directory of the device storage and rename it recovery? If not then non of the recowvery methods will work. Also twrp needs to be the newest image. When using easy recowvery you should hit option 5 and enter then option 7 and enter and then option 0 and enter then option 2 and enter. Select y for yes when prompted and let the program do its thing. You should be prompted to boot into recovery at the end and it will go into tarp recovery. Hit cancel when it asks for password. Then go to wipe and format. After formatted, you need to install no-opt enc or root and then you're done. If you want to update all you have to do is get latest firmware from this forum. Also' if you update you need to also re flash no opt enc or root again and I also delete recovery from boot.p file in recovery. Should be good to go!
Click to expand...
Click to collapse
providing an update
Ive just tried everything listed in you post specifically and failed , so i tried like 2 more time ,
it reboots into stock recovery so still no TWRP ,
boot loader is unlocked , cause i just checked again , and its still not accepting any commands
Adb flash commands do not work for the lg g5... You have to root with either easy recowvery or hard recowvery. You have to be on 20a firmware.
speters04 said:
Adb flash commands do not work for the lg g5... You have to root with either easy recowvery or hard recowvery. You have to be on 20a firmware.
Click to expand...
Click to collapse
thanks for reply;
none of those work for me either, I've been trying all this time
it says its successful in deploying commands, but when it restarts I see the LG logo two times, then it boots back up
( i assume its rewriting recovery there )
Can you explain the exact process you are trying? It is kinda hard to diagnose the issue without knowing the full process you are trying. I have rooted several lg g5 phones with the autorecowvery tool.
I had the same issue after returning from 20k to 20a. I didn't have this problem doing the same from 20f. T-Mobile might've introduced some security kink at 20i that sticks across updates. I was only able to flash twrp after flashing 20a with UPPERCUT to enter LGUP, booting into 20a, allowing debug in developer options, then running easyrecowvery with verification disabled (press 5 for advanced options, then 7 I think, then 0 to return to main menu, then 1 or 2). With verification enabled, easyrecowvery will just take you to the non-existent Android recovery screen and leave you there. I think that's where you're stuck??
speters04 said:
Can you explain the exact process you are trying? It is kinda hard to diagnose the issue without knowing the full process you are trying. I have rooted several lg g5 phones with the autorecowvery tool.
Click to expand...
Click to collapse
well lets use Autorecowvery for example
ive exhausted all options there and Ive gotten the success messages , does its fancy restarts and success messages all around , but when it restarts to install the "no-verity-opt-encrypt" it reboots and comes right back to android . ( note it reboots 2 times at this point , so i know its rewriting stock recovery )
see below
https://ibb.co/eq5ctR
It seems like you have a recovery flash. Have you tried adv reboot recovery? If not then you need to try that. You can also use hardware combination to get into recovery. You have to select yes both times and it will reboot to recovery. If it doesn't then start over with the auto recowvery. Also, it is very important that you download twrp and copy it to your internal storage on the root. Also, once it is there you have to name it to recovery. Don't use the .img when renaming it because you end up with recovery.img.img... Sometimes it takes a few tries on the recowvery method... Hope this helps!
speters04 said:
It seems like you have a recovery flash. Have you tried adv reboot recovery? If not then you need to try that. You can also use hardware combination to get into recovery. You have to select yes both times and it will reboot to recovery. If it doesn't then start over with the auto recowvery. Also, it is very important that you download twrp and copy it to your internal storage on the root. Also, once it is there you have to name it to recovery. Don't use the .img when renaming it because you end up with recovery.img.img... Sometimes it takes a few tries on the recowvery method... Hope this helps!
Click to expand...
Click to collapse
well ive used
- "adb reboot recovery"
- hardware keys ( whenever i do this it wipes the phone ) , so i wont be trying that much cause i have stuff on it now , phones not encrypted tho
ive tried all 4 versions of twrp and renamed them all , countless times ive tried everything ive searched and read
When you first get into TWRP for the very first time, I believe it is a must to "FORMAT DATA" before you flash supersu and 'no-verify' zips
dtgo said:
well ive used
- "adb reboot recovery"
- hardware keys ( whenever i do this it wipes the phone ) , so i wont be trying that much cause i have stuff on it now , phones not encrypted tho
ive tried all 4 versions of twrp and renamed them all , countless times ive tried everything ive searched and read
Click to expand...
Click to collapse
I know this might sound silly, but have you extracted the twrp file and then renamed it to recovery? Have you tried downloading on your phone and then extracting it on your phone and then renaming it? After I looked at the image you shared it seems like the flash seems to have an error and the only thing that makes any sense to me is a bad download of twrp or an unextracted version. I've ran into that error before and it drove me nuts until I figured it out...
poog said:
When you first get into TWRP for the very first time, I believe it is a must to "FORMAT DATA" before you flash supersu and 'no-verify' zips
Click to expand...
Click to collapse
well ive been working to get to this screen it NEVER happens , i already know im set when im there
the phone isnt encrypted so i know i wont have to format data , since , format data removes encryption
speters04 said:
I know this might sound silly, but have you extracted the twrp file and then renamed it to recovery? Have you tried downloading on your phone and then extracting it on your phone and then renaming it? After I looked at the image you shared it seems like the flash seems to have an error and the only thing that makes any sense to me is a bad download of twrp or an unextracted version. I've ran into that error before and it drove me nuts until I figured it out...
Click to expand...
Click to collapse
ive tried both your suggestions plus more
copied to the phone and renamed
downloaded on the phone then renamed
dowloaded on pc and renamed then copied to phone
used adb to push and rename to phone
still having challenges with this
do you think its a dead case guys
OP isn't the only one with this hair-pulling problem...I too downgraded a new H830 from 20M (? I can't remember which one exactly since I've LG-Uppercutted 20A and troubleshooted this constant problem so many times now)---I get the exact same error as OP, also with the highly suspicious 'greyed-out OEM Unlock' (in the Developer Options of the Settings).
Hello, today while trying to get back to stock i wierdly bircked my honor 8
I flashed the stock recovery and stock boot img
Then i flashed a rollback package and a marshmallow package which i used for this same thing before.
Now the phone didnt start for a solid 30 minutes and ive decided to reflash the rollback and marshmallow package, but after i flashed the rollback got stuck at the boot logo, not even the stock bootanimation showing up.
The phone doesnt reboot neither in any of the recoveries nor in bootloader.
Any help would be appreciated.
Stephen
Okay so after all of this i managed to reboot to bootloader and get my hands on one of my previous unlock codes. So now ive got an unlocked bootoader, but after fashing twrp the phone is stuck at the 'your device is booting now' when im trying to get in it
I thing you have flashed the wrong TWRP, check for the latest version or at least the one for your build
uh well, hello there again.
i've tried to do the dload method which failed(i used lots of versions tho none worked)
and i've tried flashing marshmallow twrp, which at the moment, well, it cannot mount anything. no partition can get mounted.
Does any of you guys have an idea of what i could try?
thanks in advance
Does it mean that you have access to TWRP ? if TWRP cannot mount a partition, go into mount section, tick system, data, boot, vendor and then reboot to TWRP again. Then try your previous operation. If it cannot mount data, go into wipe, advanced wipe, and click on format data, then restart TWRP and try again
seems like i somehow broke the partition table, cause it shows every storage as 0 mb and mounting isn't available, cant tick the option. Looks like i will have to find some service center to repair it by my own cost, by the end of the month. Though im giving it around the 25th so i got some more time till then, so maybe i find some solution to this problem.
Hey, so I managed to make the phone work again.
I have flashed boot cust recovery recovery2 and system from the italian marshmallow firmware, then I flashed that same firmware using dload method(tho it failed at 99%)
ØG_SQUAÐ said:
Hey, so I managed to make the phone work again.
I have flashed boot cust recovery recovery2 and system from the italian marshmallow firmware, then I flashed that same firmware using dload method(tho it failed at 99%)
Click to expand...
Click to collapse
You tried only once? Maybe you should now try to flash TWRP recovery and restore a backup made by TWRP. I can provide you one but for FRD-L09, not another. Another method would be to flash the rollback package and then retry flashing an EMUI 4.X ROM (dload method for both), hope you'll figure it out
I think i expressed myself wrong.
That was how i got the phone to work.
Oh lol I misunderstood because of the "it failed at 99%" and I thought the phone wasn't rebooting , no matter I'm glad you succeeded
Hi senior Devs. I hope you can help with this. I'll start off by saying that sometines, with simple things, I can be a bit noobish so to speak. So I have a couple of silly instinctive questions first before I explain.
1 - if I have no boot partition, will the phone still boot up and just hang on that "your phone is unlocked and can't be trusted" message
2 - if boot partition is still there, where in twrp can I see it and flash the necessary boot.img?
I know you guys are busy so I'll show as much mercy as possible by making a long story short. I'll explain what I did in point form.
-Phone - 64gb variant, build L29C1856B200
-I tried to rebrand with SRK tool to L29C432. OEM change was successfully and phone rebooted automatically.
-Change robuild.display.id was successfull. In about phone-build number was showing C900B200. After that phone was supposed to reboot and automatically install update from as card.
-Rebooted the phone and went into bootloop.
-Booted into twrp and flashed L29C432B560, the update zip and the hw mumbo jumbo zip. Both failed with sparse and writing errors.
-Someone suggested flashing system images to phone which made sense sort of, so I flashed boot.img to boot partition ( which I now believe was the wrong thing to do ) and flashed recovery and system images to system.
-Nothing worked, still had bootloop.
-Then I thought I needed to wipe, format, etc and reflash c432b560 zip files. Did that and this time I had same bootloop but no twrp. Only Huawei recovery and rescue mode only, hence my earlier post in q/a which I recently renamed as the title was wrong.
-for the last 4 days, I had no fastboot. Until last night. Don't know how or why but I've got fastboot now so I tried rayglobe unbrick.
-Flashed custom.img, recovery.img, boot.img and system.img from L29C432B560 successfully, much to my surprise. I took video because was expecting lots of errors. Not one error. Everything was written and flashed according to rayglobe.
-Still nothing.
-At 6am ( still havent slept yet ) Went back to SRK tool and reflashed twrp 3.0.2, prompt asked me if I wanted to over write, yes, flashed and rebooted into twrp. Relief of sorts.
-In twrp if I click on restore, it shows backup file for C900B200. Just like it did before.
I really really appreciate any senior developer who takes time to read this and I simply ask for instructions for what to do next. Knowing my luck it probably isn't as complicated as it seems.
With a lot of help from danwalkert, my mate 8 lives again. Flashed c432b330 emui 4.1 stock via 3 button method.
you can not restore a Backup from Nougat to MM.This can not boot into System.
You must flash the B560 again and after flashing must use the Rollback UPDATE.APP to go to MM.
After Rollback flash B192/B180 or B211 via dload Method.
Flash twrp,root or what you want