I did some errors trying to update stock firmware from twrp, now I'm stuck on twrp 3.4 and I cannot install anything to solve it because of the message:
Failed to mount '/odm' ( invalid argument )
What is working:
- Boot to twrp
- Boot to Emui recovery ( it connects to wifi but it do not download/install recovery/firmware )
-- Factory reset from emui recovery
What can I try?
florstat said:
I did some errors trying to update stock firmware from twrp, now I'm stuck on twrp 3.4 and I cannot install anything to solve it because of the message:
Failed to mount '/odm' ( invalid argument )
What is working:
- Boot to twrp
- Boot to Emui recovery ( it connects to wifi but it do not download/install recovery/firmware )
-- Factory reset from emui recovery
What can I try?
Click to expand...
Click to collapse
Most probably you have modified the oem partition and changed the device model this is the reason for not downloading in huawei erecovery.
I had the same error like /odm but my device boots fine and works normal apart from the battery drain
Thank you. I solved it flashing /odm partition with fastboot using this method:
[GUIDE] UN-BRICK Huawei P8 Lite 2017 (And maybe other devices)
THIS IS NOT GUARANTEED TO WORK! If it does not work, feel free to let me know here and i will do what i can to help, but remember I probably can't help everyone. IMPORTANT: ON XDA-LABS APP THIS POST IS KINDA BROKEN IDK WHY SO LOAD IT IN...
forum.xda-developers.com
Thanks to HuRu method, after a lot of reboots and reinstall and erecovery and factory resets I managed to reboot stock rom.
Unfortunately I'm not able to boot any custom rom ( tried all Darkjoker's rom ), but I will make another thread for this.
Honestly I had no idea that modding this phone would have been so difficult, it usually takes me very little time with other devices while in this case every little step requires to solve a lot of troubles.
florstat said:
Thank you. I solved it flashing /odm partition with fastboot using this method:
[GUIDE] UN-BRICK Huawei P8 Lite 2017 (And maybe other devices)
THIS IS NOT GUARANTEED TO WORK! If it does not work, feel free to let me know here and i will do what i can to help, but remember I probably can't help everyone. IMPORTANT: ON XDA-LABS APP THIS POST IS KINDA BROKEN IDK WHY SO LOAD IT IN...
forum.xda-developers.com
Thanks to HuRu method, after a lot of reboots and reinstall and erecovery and factory resets I managed to reboot stock rom.
Unfortunately I'm not able to boot any custom rom ( tried all Darkjoker's rom ), but I will make another thread for this.
Honestly I had no idea that modding this phone would have been so difficult, it usually takes me very little time with other devices while in this case every little step requires to solve a lot of troubles.
Click to expand...
Click to collapse
Most probably you are not following the instruction clearly. I was able to use DarkJoker rom
Related
Hello,
I own a Huawei P8 L09, bootloader unlocked, rooted and with TWRP recovery.
I tried this morning to flash a new rom using TWRP recovery.
Problem is that I do believe I wiped to many partitions and I ended up with a bootloop.
I could at first access 3 times the emui erecovery (btw, Wifi recovery failed) but not anymore (is it related to the battery level ? I don't know how much I still have)
Following a lot of threads here and on some other forums (I've been searching now for approx. 7 hours...) :
I downloaded a update stock ROM (B170 something), I extracted Boot, System, Recovery and Cust
I entered bootloader mode (it's the only mode I can go to; recovery No, Download mode neither)
and on my computer I typed in the cmd "fastboot flash recovery recovery.img" same with system, cust and boot.
All of them said "Okay" but the bootloop is still there and I can't acess any other mode or shut the device off.
Also, my bootloader indicate that i'm "unlocked" but when I try to do something as :
"fastboot erase cache" it says "remote: not allowed" or something like that.
I tried the SD card flash method but I can't even acess the 3-button mode (doesn't work - bootloop again).
Finally, I've got 2 questions :
1) Is there a solution ? Is there/was there anybody in the same situation ?
2) Does the battery level influence wether I may or not enter any mode ? like b.e. under 30% I can't access recovery or something like that ?
Thanks in advance for your help and sorry for my bad english.
Greetings from Belgium !
Jules
Hi!
I have the same situation as you do, All i know is that you can access the eRecovery only if you're plugged in.
But it's completely useless. Have you found any solutions yet?
Edit:
i struggled and i'm still struggling but i figured out that I need the recovery and boot img of the version i was on previously. In my case that is B350.
The main mirror is down but i managed to find another one: https://mega.nz/#!NAcgQY7Y!I4eRfkaq62J31csv_wZ8_nTzmUbWPX71JUicDysjus8
after flashing them i was able to partially flash (using vol+-&pwr) B170 (it only went up to 90% with my USB attached, fails without USB)
At my surprise it booted B170 even if it didn't complete, however right now it keeps rebooting every minute. I'll update if i manage to fix this
I have the same problem as you both. To flash boot.img and other files by fastboot we need to unlock bootloader. To unlock bootloader we need to have Imei, Product Id and SN, but I can't read it because phone won't turn on.
Anyone know how to get this info?
you can read these info from the packaging box!
I managed to fix my issues (i believe) by continuously flashing and flashing versions. I never really managed to fully OTA update to 100% due to some "CUST error" but from B350 i managed to "update" to B170, then to B200, then to B321a.
Now i just installed TWRP and rooted it and on the process of installing xposed (if possible).
I wasted a good 6-7 hours on everything already
Well now I actually sent my phone in repair, given that it still was under warranty.
If they return it unrepeared, i will try it your way, Nikooo777. Thanks.
TukAliveFra said:
Well now I actually sent my phone in repair, given that it still was under warranty.
If they return it unrepeared, i will try it your way, Nikooo777. Thanks.
Click to expand...
Click to collapse
you gonna pay for the repair..
Hello everyone, I have a huawei p8 vodafone it branded.
I decided to root it, unblocked the bootloader and everything was good so far...
I tried to flash a custom recovery but failed for some reason and I decided to stick with stock recovery.
Now I installed an app as system app and my phone got bricked. my fault..
At first It went trough a bootloop and I was not able to access the huawei recovery or the fastboot, after a while it started to boot into a error message where it was saying that it was impossible to read user data partition, and give me some choices like backup, update to the latest version, or data factory.. I choose data factory twice but it went trough a bootloop again only to give me back to the same page after a while.
I can access huawei erecovery but it gives me getting info package failed when it says that I have to update it with wifi.
I can access fastboot mode and it says me that the phone is unlocked.
I really don't know what to do as I'm not expert, I tried to read various topics but never saw anyone with this message where it was saying impossible to read user data partition..
I had emui 3.1 5.1.1 with vodafone it brand... In case I have to flash it which firmware I should look for? Or is there a way to get my phone alive again without flashing?
http://forum.xda-developers.com/huawei-p8/how-to/guide-how-to-unbrick-huawei-p8-failed-t3260704
silvano2 said:
http://forum.xda-developers.com/huawei-p8/how-to/guide-how-to-unbrick-huawei-p8-failed-t3260704
Click to expand...
Click to collapse
Hey thank you silvano, can you tell me which firmware I need to flash it? Is it okay if I use a b170 even if I had the 5.1.1 emui 3.1 version?
Nothing, I can't seem to make it work, I've flashed the boot.img recovery.img system.img and cust.img successfully(b170) but still stuck in bootloop, I can enter bootloader mode, and recovery.. but when I enter recovery it says me that I need to update it and I can't update it because it says me that getting info package failed... tried with different wifis, same result..... The excatly same thing happens with the b132 stock rom too and I cant factory reset or even wipe cache if I dont make this update first as is the only option avaible on huawei eRecovery.
As last attemp I tried to force an upgrade with putting UPDATE.APP inside the sdcard and press vol up vol down and power for booting but this combination of buttons doesnt work...
I'm hopeless, I really don't know what to do... any help would be much appreciated
Hello,
Ok, here is the situation
I have a Zuk Z1 with last COS update 12.1 with locked bootloader, no root etc ... (I didn't touch anything).
Yesterday, it reboot by itself but I got bootloop (starting apps then again lenovo boot image ...)
I try to factory reset by using the recovery metohd, it's start normally (optimizing apps ...) but then reboot and again bootloop ...
So I try to sideload the official COS ROM from Cyanogen Support (cm-12.1-YOG4PAS9IG-ham-signed-d4fc2c5394.zip), but the sideload stuck at 47% and saying total xfer: 1.00x and the phone go back to recovery but still have boot loop ...
I try to boot in fastboot and use the All In One tool to flash official ROM but didn't work (Its say that the bootloader is lock)
I find without knowing this menu a debugging hardware tool test, and then I run the test, its say SD : Fail and in another I got SD : Fail and no sd fuse in dir
I saw many thread here and on google, and some say that we have to use qfil/qpst method, and find this which seems complete : http://www.androidbrick.com/lenovo-zuk-phones-qfil-roms-unbrick-guide/
But as I don't know if its hardware issue or soft brick ...
Could someone help me to recover my phone to COS or CM by using the right method ?
Thank you !
wackou said:
Hello,
Ok, here is the situation
I have a Zuk Z1 with last COS update 12.1 with locked bootloader, no root etc ... (I didn't touch anything).
Yesterday, it reboot by itself but I got bootloop (starting apps then again lenovo boot image ...)
I try to factory reset by using the recovery metohd, it's start normally (optimizing apps ...) but then reboot and again bootloop ...
So I try to sideload the official COS ROM from Cyanogen Support (cm-12.1-YOG4PAS9IG-ham-signed-d4fc2c5394.zip), but the sideload stuck at 47% and saying total xfer: 1.00x and the phone go back to recovery but still have boot loop ...
I try to boot in fastboot and use the All In One tool to flash official ROM but didn't work (Its say that the bootloader is lock)
I find without knowing this menu a debugging hardware tool test, and then I run the test, its say SD : Fail and in another I got SD : Fail and no sd fuse in dir
I saw many thread here and on google, and some say that we have to use qfil/qpst method, and find this which seems complete : http://www.androidbrick.com/lenovo-zuk-phones-qfil-roms-unbrick-guide/
But as I don't know if its hardware issue or soft brick ...
Could someone help me to recover my phone to COS or CM by using the right method ?
Thank you !
Click to expand...
Click to collapse
Go with qpst/qfil method to recover your phone
And did you tried changing the USB port or cable while side loading cos ROM .. Cause most of issues are solved by the changing USB port or cable.. So try this.. Or else qfil is the option
shubhambhise said:
Go with qpst/qfil method to recover your phone
And did you tried changing the USB port or cable while side loading cos ROM .. Cause most of issues are solved by the changing USB port or cable.. So try this.. Or else qfil is the option
Click to expand...
Click to collapse
Hello,
I got help on the telegram group, we try many thing, the result is that I can only get ZUI working, if flashing COS via QFIL, I get the same result, if I flash ZUI, unlock bootloader, flash TWRP, wipe everything, then sideload CM13, TWRP say that no os is installed and I get a bootloop at the bootloader ...
ZUI is good, but I get some error regarding notification.
If you have any other idea ?
wackou said:
Hello,
Ok, here is the situation
I have a Zuk Z1 with last COS update 12.1 with locked bootloader, no root etc ... (I didn't touch anything).
Yesterday, it reboot by itself but I got bootloop (starting apps then again lenovo boot image ...)
I try to factory reset by using the recovery metohd, it's start normally (optimizing apps ...) but then reboot and again bootloop ...
So I try to sideload the official COS ROM from Cyanogen Support (cm-12.1-YOG4PAS9IG-ham-signed-d4fc2c5394.zip), but the sideload stuck at 47% and saying total xfer: 1.00x and the phone go back to recovery but still have boot loop ...
I try to boot in fastboot and use the All In One tool to flash official ROM but didn't work (Its say that the bootloader is lock)
I find without knowing this menu a debugging hardware tool test, and then I run the test, its say SD : Fail and in another I got SD : Fail and no sd fuse in dir
I saw many thread here and on google, and some say that we have to use qfil/qpst method, and find this which seems complete : http://www.androidbrick.com/lenovo-zuk-phones-qfil-roms-unbrick-guide/
But as I don't know if its hardware issue or soft brick ...
Could someone help me to recover my phone to COS or CM by using the right method ?
Thank you !
Click to expand...
Click to collapse
Hope this will help you
Check this out
http://forum.xda-developers.com/zuk-z1/help/helpppp-t3505990
http://forum.xda-developers.com/zuk-z1/general/guide-how-to-unlock-root-install-twrp-t3394037
This will help you
Hello All,
I flashed Android Nougat on my ZUK Z1 by rooting it.
I was using it for quite some time comfortably but then due to some reasons i formatted my phone and unfortunately my OS got deleted probably due to which i got stuck in boot loop.
However TWRP was working, I can even log into fastboot.
I tried installing stock ROM using ADB sideload feature.
The install starts , shows percentage of completion and then gets completed but then when i reboot the system it opens the TWRP screen again.
I have tried the following steps :
1. wipe cache and dalvik , Installing stock rom , wipe cache and dalvik again
2. at times it gives me error of zip verification failed , And so as suggested in one of the threads I disabled zip verification through recovery.
3. at times after the flashing is completed, when i reboot it says NO OS INSTALLED, you still want to reboot?
4. at times while flashing through ADB sideload , it says "unmount of /system failed ; no such volume Script succeeded result was [ ]"
5. at times it says script succeeded: result was [ t ]
basically so many threads and so many options tried but the phone keeps booting into TWRP.
Any help will be greatly appreciated guys ... Please get back with your expertise !!
Ratneshpathak12 said:
Hello All,
I flashed Android Nougat on my ZUK Z1 by rooting it.
I was using it for quite some time comfortably but then due to some reasons i formatted my phone and unfortunately my OS got deleted probably due to which i got stuck in boot loop.
However TWRP was working, I can even log into fastboot.
I tried installing stock ROM using ADB sideload feature.
The install starts , shows percentage of completion and then gets completed but then when i reboot the system it opens the TWRP screen again.
I have tried the following steps :
1. wipe cache and dalvik , Installing stock rom , wipe cache and dalvik again
2. at times it gives me error of zip verification failed , And so as suggested in one of the threads I disabled zip verification through recovery.
3. at times after the flashing is completed, when i reboot it says NO OS INSTALLED, you still want to reboot?
4. at times while flashing through ADB sideload , it says "unmount of /system failed ; no such volume Script succeeded result was [ ]"
5. at times it says script succeeded: result was [ t ]
basically so many threads and so many options tried but the phone keeps booting into TWRP.
Any help will be greatly appreciated guys ... Please get back with your expertise !!
Click to expand...
Click to collapse
QFIL method is your way
QFIL
Thanks but Can you please tell me where to get information about it I haven't tried it ever.
Any links in XDA group would be greatly helpful.
QFIL
strongst said:
QFIL method is your way
Click to expand...
Click to collapse
Thanks , bt Can you please tell me where to get information about QFIL.
I haven't done it ever , any links from XDA group will be greatly helpful.
Or if u can let me know what exactly to search for, ill do that.
Ratneshpathak12 said:
Thanks , bt Can you please tell me where to get information about QFIL.
I haven't done it ever , any links from XDA group will be greatly helpful.
Or if u can let me know what exactly to search for, ill do that.
Click to expand...
Click to collapse
Using Google search you find tons of guides like this one.
Also in xda forums searching by qfil there's enough.
hi - I hope someone can help me. I have a LTE enabled Lenovo Tablet 2 1050L which I attempted to root using the instructions given here ... https://forum.xda-developers.com/thinkpad-tablet/general/how-to-root-yoga-tablet-2-t3251571 ... but I have managed to brick my device. I successfully installed SuperSU but then read that Magisk was better and tried the same procedure with that but it didn't work. Now when the tablet starts up, I get a message which says ... "EFILINUX ERROR [android_image_start_buffer:737] boot image digital signature verification failed : 0000001A" which appears over the initial Lenovo splash screen. I then get to the Android system recovery menu but I can't get the table any further than this. I have tried wiping data / factory resetting but this does not work.
I can boot the tablet into recovery mode using CWM or TWRP but I have no idea what to do now. I guess I shouldn't have messed. I hope someone can help - I've tried the official Lenovo forums but no one has answered in a week.
Kind regards
I've downloaded this ROM ... lenovo-forums.ru/files/file/1074-yoga-tablet-2-10-yt2-1050l_s100192_151119_row_los-50 ... and flashed this onto my tablet using the Intel flash tool and everything seems to be back up and running.
Can someone confirm that this is safe to do? Can I trust this ROM as it's not from an official source?
Thanks