Related
I got a ZF3 Deluxe from Italy, is TIM branded, and stuck on MM 6.0, no updated released for this brand, so a friend of mine told me there is of course android 7 for ZF3Deluxe, so i wanted to manually upgrade system to 7.0 Nougat, i downloaded the Stock ROM from asus (2.15ghz cpu, i've checked of course) but when i try to flash it from the Stock Recovery i get this error (see the attachment) i also attach the software informations, (looking at the error i receive it may see the archive is corrupted, but i've tried to download it from Asus many and many times)
You have a carrier rom on your phone and the international version fails the upgrade check.
If you could get your bootloader unlocked that would be a way around it but you need to upgrade to a certain rom version to do that and the carrier hasn't supplied that rom...
You're essentially screwed until the carrier either releases the bootloader unlockable rom or upgrades the rom to nougat...
LeGrim said:
I got a ZF3 Deluxe from Italy, is TIM branded, and stuck on MM 6.0, no updated released for this brand, so a friend of mine told me there is of course android 7 for ZF3Deluxe, so i wanted to manually upgrade system to 7.0 Nougat, i downloaded the Stock ROM from asus (2.15ghz cpu, i've checked of course) but when i try to flash it from the Stock Recovery i get this error (see the attachment) i also attach the software informations, (looking at the error i receive it may see the archive is corrupted, but i've tried to download it from Asus many and many times)
Click to expand...
Click to collapse
You should try to flash stock recovery of WW in fastboot.
And then flash 6.0 WW rom by WW recovery.
Even though ,I didn't sure that if it will work(because I don't have Z016S),but you can try it.
samson1357924 said:
You should try to flash stock recovery of WW in fast boot.
And then flash 6.0 WW rom by WW recovery.
Even though ,I didn't sure that if it will work(because I don't have Z016S),but you can try it.
Click to expand...
Click to collapse
Ok thanks, i can give a try, but where i can download the WW stock recovery? There is no recovery.img inside the WW_user.zip ROM
LeGrim said:
Ok thanks, i can give a try, but where i can download the WW stock recovery? There is no recovery.img inside the WW_user.zip ROM
Click to expand...
Click to collapse
Here it comes~
ZenFone 3 Deluxe ZS570KL_WW stock recovery
Ok guys, i think i've found a way to debrand my Zenfon 3 Deluxe, im testint the procedure right now, i will post the whole procedure if i succeed
Install : ADB & Minimal Fastboot.
Install : pyton 3.6 https://www.python.org/downloads/
Download the latest WW-4.12.40.1698 (For 2.15GHz CPU or 2.40GHz CPU) from Asus WebSite.
Download "Dat to img by stupdroid.com" (search it with google).
Extract Dat to img by stupdroid.com in a Folder.
Open the Firmware ZIP and copy system.new.dat, system.transfer.list e file_contexts in the Dat2IMG's folder.
Execute system.new.dat 2 flashable img converter.exe and just press ENTER and wait till the end of procedure, you will receive 2 files : system.raw.img e system.new.img.
Copy system.new.img in your Fastboot's folder.
Put the Phone into Fastboot mode.
Open fastboot and put this command: " fastboot flash system system_new.img "
Wait the end of flash procedure and type : Fastboot Reboot.
Enter recovery wipe data and cache.
Done.
LeGrim said:
Install : ADB & Minimal Fastboot.
Install : pyton 3.6 https://www.python.org/downloads/
Download the latest WW-4.12.40.1698 (For 2.15GHz CPU or 2.40GHz CPU) from Asus WebSite.
Download "Dat to img by stupdroid.com" (search it with google).
Extract Dat to img by stupdroid.com in a Folder.
Open the Firmware ZIP and copy system.new.dat, system.transfer.list e file_contexts in the Dat2IMG's folder.
Execute system.new.dat 2 flashable img converter.exe and just press ENTER and wait till the end of procedure, you will receive 2 files : system.raw.img e system.new.img.
Copy system.new.img in your Fastboot's folder.
Put the Phone into Fastboot mode.
Open fastboot and put this command: " fastboot flash system system_new.img "
Wait the end of flash procedure and type : Fastboot Reboot.
Enter recovery wipe data and cache.
Done.
Click to expand...
Click to collapse
I forgot to say, after this procedure, just flash the stock WW recovery via Fastboot, then download from asus the lastest 7.0 firmware SKU WW, all perfect. tested by me.
Ok I already have system.new.img, I copied it to the root folder of the SD. Device restart in Fastboot mode (power + vol.up key). Exit screen with message Fastboot mode and does nothing.
Install in the computer the pyton 3.6, I suppose that it serves for the process of generating system.new.img.
I do not know how to do the first step "Install: ADB & Minimal Fastboot.".
Thank you and forgive my translator
If i want to unlock the bootloader for root and unbrand this phone what i have to do? I need unbranded nougat with root but the phone is TIM branded
Ryder. said:
If i want to unlock the bootloader for root and unbrand this phone what i have to do? I need unbranded nougat with root but the phone is TIM branded
Click to expand...
Click to collapse
What version is your phone right now??
Now only have official unluck
For 2.15GHz:8996(None-PRO) UnlockTool
For 2.4GHz:8996P(PRO) UnlockTool
If you are WW version right now,try these tools.
samson1357924 said:
What version is your phone right now??
Now only have official unluck
For 2.15GHz:8996(None-PRO) UnlockTool
For 2.4GHz:8996P(PRO) UnlockTool
If you are WW version right now,try these tools.
Click to expand...
Click to collapse
It's not WW. I'ts from italy and it's tim branded
Ryder. said:
If i want to unlock the bootloader for root and unbrand this phone what i have to do? I need unbranded nougat with root but the phone is TIM branded
Click to expand...
Click to collapse
Try this
or try flash ZenFone 3 Deluxe ZS570KL_WW stock recovery of 4.12.40.1698 and flash UL-Z016-WW-4.12.40.1698-user.zip in recovery (by micro sd or adb sideload)not sure if it work(need verification,I wish you to try first).
Please help me, my model is the Z016S
I can convert UL-Z016-WW-4.12.40.1698-user.zip img and flash with fastboot.
Reboot and it works, but I do not know how to get into recovery.
I have also installed the Z016-WW-4.11.40.1085_recovery.img. The TIM DISAPPEARED
Then I copied the UL-Z016-WW-5.14.44.1898-user.zip into the internal memory and it does not install well.
I have proven the same with UL-Z016-WW-5.14.44.1898-user.zip and it does not work me it stays in a non-comands and will not boot.
greetings and thanks
P.S. At least you do not see the TIM anywhere.
barbapapa said:
Please help me, my model is the Z016S
I can convert UL-Z016-WW-4.12.40.1698-user.zip img and flash with fastboot.
Reboot and it works, but I do not know how to get into recovery.
I have also installed the Z016-WW-4.11.40.1085_recovery.img. The TIM DISAPPEARED
Then I copied the UL-Z016-WW-5.14.44.1898-user.zip into the internal memory and it does not install well.
I have proven the same with UL-Z016-WW-5.14.44.1898-user.zip and it does not work me it stays in a non-comands and will not boot.
greetings and thanks
P.S. At least you do not see the TIM anywhere.
Click to expand...
Click to collapse
So,what is your system version right now?4.12.40.1698?
Why not flash the recovery of 4.12.40.1698?
samson1357924 said:
So,what is your system version right now?4.12.40.1698?
Why not flash the recovery of 4.12.40.1698?
Click to expand...
Click to collapse
This is my situation
samson1357924 said:
So,what is your system version right now?4.12.40.1698?
Why not flash the recovery of 4.12.40.1698?
Click to expand...
Click to collapse
I have done this and it installs,
fastboot flash recovery Z016-WW-4.12.40.1698_recovery.img
reboot, boot system, detect update file is installed, reboot and then gives error (3) unknown.
barbapapa said:
I have done this and it installs,
fastboot flash recovery Z016-WW-4.12.40.1698_recovery.img
reboot, boot system, detect update file is installed, reboot and then gives error (3) unknown.
Click to expand...
Click to collapse
Tow solution you can try
1.install the rom of 4.12.40.1698 again(some of tile,such as xbl,devcfg,devcfgbak..... may be still TIM versio.install it in recovery may turn it into WW version)
2.If fail, try flash these files in fastboot.(I will upload these files for you to flash,also you can draw by yourself)
Ok already worked, the solution is to unlock as you put in # 11.
Thank you
barbapapa said:
Ok already worked, the solution is to unlock as you put in # 11.
Thank you
Click to expand...
Click to collapse
Good!
Can you share what step did you do? Which might help another TIM user.
Requirements for this to work.
1. You need to be on emui 4.1/4.0 before hand
If not you can rollback. downloads and instructions
Are on huawei website (you do need a sd card to do this)
2. A computer with Huawei update extractor and adb tools
3.unlocked bootloader (rolling back locks it again)
4. Twrp recovery from the website not the Chinese method. (Twrp website version has bugs which is important)
5. Es file explorer already installed with root permissions on (even though you're not rooted)
FOR PEOPLE WHO STAYED ON EMUI 4.0
For everyone else on emui 5.0 rollback to emui 4.0 unlock the bootloader and flash twrp threw adb and. Follow the guide after you done that.
If you stayed on emui 4.0 for root permissions good for you . You have a shortcut all you need to do is flash twrp from their website and download the emui 4.0 firmware from Huawei's website extract the UPDATE.APP onto the desktop and drag it into the Huawei update extractor. After that you're going to extract the boot.img from the tool by right clicking then you're going to have to flash the stock boot.img you just extracted to remove root . You'll keep twrp so don't worry. Now all you have to do is let the update to emui 5.0 download to 100% now hit update. It's going to reboot into twrp to update. It will loop so DO NOT WORRY that's the bug I'm talking about it will force twrp to update you will see the terminal as twrp flashes the update after it stops looping then the screen will go black and show erecovery finishing the update.
when it boots unlock your phone open Es File Explorer when you open the application on screen will say "new files" there will be 2 zip files one of them will say update.zip.
Tap on it to open that folder. Notice that the files are going to be under the storage/emulated/0 folders which you can only get to with root copy or move both zip files to your /sdcard/download directory connect your phone to your computer open the update.zip folder and drag the update.app to the Huawei update extractor and extract the boot.img take the boot.img and put it back on your phone in the download folder.
Open magisk manager tap install and then tap on patch to boot.img now go to the magiskmanager folder copy the patched boot.img to downloads if your download folder and extract it to your desktop. After that adb your phone into bootloader mode and flash the boot.img reboot and you'll be rooted with magisk!
This is exactly how I rooted my honor 6x USA version and I know lots of people where wanting root on emui 5.0 and if you run into any bootloops or brick your phone you already have the backup stock images to try again if you want . I do apaolgize about how this looks messy and how long the guide is but it works ! I would have just uploaded the boot.img I patched but I'm new to xda and they won't let me post outside links so try it out !
But there are already guides for emui 4 and 5.
No need to rollback just to root.
There is one in my signature for emui 5
shashank1320 said:
But there are already guides for emui 4 and 5.
No need to rollback just to root.
There is one in my signature for emui 5
Click to expand...
Click to collapse
Well that was something I couldn't find I've looked forever. And I did flash twrp but it would never boot into the recovery on 5.0 that's why I did this process so I guess this is for the people who are having the same problem with their u.s version of the phone. Thanks for letting me know .
:crying:Last night, I installed the Android 8 update package on the forum.
Halfway through, an error is displayed and then exit.
I tried eRecovery and Hisuite, but all failed.
I tried it and found that the original recovery partition became recovery_ramdisk. It looks like the partition has changed.
What can I do to be able to return to emui5?
I have imagined "fastboot flashall", but I do not know how? Forgive my lame English
zzkeier said:
:crying:Last night, I installed the Android 8 update package on the forum.
Halfway through, an error is displayed and then exit.
I tried eRecovery and Hisuite, but all failed.
I tried it and found that the original recovery partition became recovery_ramdisk. It looks like the partition has changed.
What can I do to be able to return to emui5?
I have imagined "fastboot flashall", but I do not know how? Forgive my lame English
Click to expand...
Click to collapse
recovery_ramdisk. is the new name of recovery partition. EMUI8/Oreo flashing has started means the partitions etc have changed already so right now you can't go back to EMUI 5 as rollback images are not available yet. You can try to flash again properly with proper download for your specific model. I guess you are missing some echo commands.
thank you very much
SVR said:
recovery_ramdisk. is the new name of recovery partition. EMUI8/Oreo flashing has started means the partitions etc have changed already so right now you can't go back to EMUI 5 as rollback images are not available yet. You can try to flash again properly with proper download for your specific model. I guess you are missing some echo commands.
Click to expand...
Click to collapse
I extract the update.app(oreo) file and then i flash the system.img. Now it works..Thank you
hey how did you did that?
zzkeier said:
I extract the update.app(oreo) file and then i flash the system.img. Now it works..Thank you
Click to expand...
Click to collapse
I also have similar problem I installed different model rom using firmware finder and now I can only use my phone when I unlock bootloader when I lock it it will not open directly go into the erecovery and nothing is working I tried everything twrp,erecovery,force updating nothing worked all failed.please help
shrey2204 said:
I also have similar problem I installed different model rom using firmware finder and now I can only use my phone when I unlock bootloader when I lock it it will not open directly go into the erecovery and nothing is working I tried everything twrp,erecovery,force updating nothing worked all failed.please help
Click to expand...
Click to collapse
well,I flash the system.img by fastboot,and then make a factory reset.Bootloader unlock needed.
i have the same problem
I tried to upgrade phone to Oreo after unlock, in update progress it got error and restart phone! Now it shows:
Code:
Error Mode
Attention!
Please update system again
Error!
Func No : 11 (recovery image)
Error No : 2 ( load failed )
I just have access to fastboot
i did flash system.img and tried install twrp on ramdisk recovery. but always same
:crying::crying::crying::crying:
Hi
I have a problem with my Honor 7X L21.
Because online update dose not work for this model I decided to updated my smartphone offline.
I downloaded Oreo update file
Unlock my phone
install twrp
update phone
every thing is going well until here
then I decided to root my phone but I saw there is no twrp on my phone
I search and I found a thread here that show how install twrp with adb use recovery ramdisk.
I install twrp on recovery ramdisk and try to root my phone. its OK but when my phone want to start its stuck on google page "just a sec..."
I boot my device on twrp and I did factory reset but the problem was still exist.
then I decided to flash update again.
I copy update file on SD card and wright code on twrp
but at the end when I reboot the recovery, twrp except stock recovery came up and my stock recovery was gone.
I reboot the system but Its loop on this page that says:
ERROR MODE
Attention!
Please update system again.
Error!
Func NO : 11 (recovery image)
Error NO : 2 (load failed!)
Please help me!!!
I try to install stock recovery and twrp with adb and huawei multi tools but it didn't work.
it shows:
"FAILED (remote: partition length get error)"
I try to unbrick my phone too but it shows same message that "FAILED (remote: partition length get error)"
Helllllp lpeaeaeaeaeaseeee!!!
Mohammadreza76646 said:
Hi
I have a problem with my Honor 7X L21.
Because online update dose not work for this model I decided to updated my smartphone offline.
I downloaded Oreo update file
Unlock my phone
install twrp
update phone
every thing is going well until here
then I decided to root my phone but I saw there is no twrp on my phone
I search and I found a thread here that show how install twrp with adb use recovery ramdisk.
I install twrp on recovery ramdisk and try to root my phone. its OK but when my phone want to start its stuck on google page "just a sec..."
I boot my device on twrp and I did factory reset but the problem was still exist.
then I decided to flash update again.
I copy update file on SD card and wright code on twrp
but at the end when I reboot the recovery, twrp except stock recovery came up and my stock recovery was gone.
I reboot the system but Its loop on this page that says:
ERROR MODE
Attention!
Please update system again.
Error!
Func NO : 11 (recovery image)
Error NO : 2 (load failed!)
Please help me!!!
I try to install stock recovery and twrp with adb and huawei multi tools but it didn't work.
it shows:
"FAILED (remote: partition length get error)"
I try to unbrick my phone too but it shows same message that "FAILED (remote: partition length get error)"
Helllllp lpeaeaeaeaeaseeee!!!
Click to expand...
Click to collapse
Doing the update second time is fine, and best way to restore full stock. But you needed to use Oreo version of no-check recovery and the Oreo partition to flash it to.
So if still able to get into twrp, can try with correct no-check recovery and correct partition it's flashed to.
Also
With multi tool , make sure you put check mark on emui 8. Up in upper right corner. That way it uses Oreo partition names and file not nougat.
The partition length over message usually means nougat file or partition name used on Oreo system
mrmazak said:
Doing the update second time is fine, and best way to restore full stock. But you needed to use Oreo version of no-check recovery and the Oreo partition to flash it to.
So if still able to get into twrp, can try with correct no-check recovery and correct partition it's flashed to.
Also
With multi tool , make sure you put check mark on emui 8. Up in upper right corner. That way it uses Oreo partition names and file not nougat.
The partition length over message usually means nougat file or partition name used on Oreo system
Click to expand...
Click to collapse
Thank you for your answer.
But I try to extract update.app (oreo version) but its failed! huawei update extractor cant open it and 7zip cant extract it with (unexpected error...)!
And unfortunately my TWRP dos not work anymore
Mohammadreza76646 said:
Thank you for your answer.
But I try to extract update.app (oreo version) but its failed! huawei update extractor cant open it and 7zip cant extract it with (unexpected error...)!
And unfortunately my TWRP dos not work anymore
Click to expand...
Click to collapse
I give my phone to a friend to work on it. If he can't fix it I try new multi tools version to flash phone.
Mohammadreza76646 said:
Thank you for your answer.
But I try to extract update.app (oreo version) but its failed! huawei update extractor cant open it and 7zip cant extract it with (unexpected error...)!
And unfortunately my TWRP dos not work anymore
Click to expand...
Click to collapse
On the extractor app. On options tab uncheck the verify header option, it should extract then.
Then perhaps first do these three partitions.
Kernel.img
Ramdisk.img
Then
twrp_ramdisk or for stock use recovery_ramdisk
Mohammadreza76646 said:
Hi
I have a problem with my Honor 7X L21.
Because online update dose not work for this model I decided to updated my smartphone offline.
I downloaded Oreo update file
Unlock my phone
install twrp
update phone
every thing is going well until here
then I decided to root my phone but I saw there is no twrp on my phone
I search and I found a thread here that show how install twrp with adb use recovery ramdisk.
I install twrp on recovery ramdisk and try to root my phone. its OK but when my phone want to start its stuck on google page "just a sec..."
I boot my device on twrp and I did factory reset but the problem was still exist.
then I decided to flash update again.
I copy update file on SD card and wright code on twrp
but at the end when I reboot the recovery, twrp except stock recovery came up and my stock recovery was gone.
I reboot the system but Its loop on this page that says:
ERROR MODE
Attention!
Please update system again.
Error!
Func NO : 11 (recovery image)
Error NO : 2 (load failed!)
Please help me!!!
I try to install stock recovery and twrp with adb and huawei multi tools but it didn't work.
it shows:
"FAILED (remote: partition length get error)"
I try to unbrick my phone too but it shows same message that "FAILED (remote: partition length get error)"
Helllllp lpeaeaeaeaeaseeee!!!
Click to expand...
Click to collapse
I ever have similiar problem with you dude, but it's solved now, if you always stuck on " its OK but when my phone want to start its stuck on google page "just a sec...", its call google accont verification, i'll by bypass with this script, save as to .bat and put on adb folder
adb devices
adb shell content insert --uri content://settings/secure --bind name:s:user_setup_complete --bind value:s:1
adb shell am start -n com.google.android.gsf.login/
adb shell am start -n com.google.android.gsf.login.LoginActivity
pause
in fastboot type:
fastboot -w
after all it's works to me to bypass google account verification
and if now your problem is
ERROR MODE
Attention!
Please update system again.
Error!
Func NO : 11 (recovery image)
Error NO : 2 (load failed!)
i solve with re-flash system from this
https://androidfilehost.com/?fid=673956719939830152
fastboot flash system system.img
and doing TWRP Flashing
https://forum.xda-developers.com/devdb/project/?id=25826#downloads
fastboot flash recovery_ramdisk complete_twrp_ramdisk.img
and voila my problem solved..
mrmazak said:
On the extractor app. On options tab uncheck the verify header option, it should extract then.
Then perhaps first do these three partitions.
Kernel.img
Ramdisk.img
Then
twrp_ramdisk or for stock use recovery_ramdisk
Click to expand...
Click to collapse
Hello again dude.
Finally I flashed my phone and I got the system installed.
But now my phones IMEI is lost. and I cant put sim on it!!!
what should I do now???
FRP is locked! (
Mohammadreza76646 said:
Hello again dude.
Finally I flashed my phone and I got the system installed.
But now my phones IMEI is lost. and I cant put sim on it!!!
what should I do now???
FRP is locked! (
Click to expand...
Click to collapse
So now is locked frp. Does phone have twrp or stock now.?
I think when you tried to install the oreo update for second time, you followed same tutorial as the first time. And that made you problem worse. The tutorial has you flash no-check recovery to 2 partition by block number. 22 & 29. On nougat that is "recovery" and "recovery2". On Oreo partion table it is "reserved2" & "erecovery_vendor"
I don't know how to fix imei. Have hope that if to ucan have a full ota install , maybe can be fixed.
There is available a "service rom" (used to fix most all problem) for Europe region with l21.
I can share link to site with service rom if you want , but I have not used it myself so not gonna be much help with it.
Link is to rusian language page. Google should translate for you.
https://4pda.ru/forum/index.php?showtopic=879524&view=findpost&p=73818595
mrmazak said:
So now is locked frp. Does phone have twrp or stock now.?
I think when you tried to install the oreo update for second time, you followed same tutorial as the first time. And that made you problem worse. The tutorial has you flash no-check recovery to 2 partition by block number. 22 & 29. On nougat that is "recovery" and "recovery2". On Oreo partion table it is "reserved2" & "erecovery_vendor"
I don't know how to fix imei. Have hope that if to ucan have a full ota install , maybe can be fixed.
There is available a "service rom" (used to fix most all problem) for Europe region with l21.
I can share link to site with service rom if you want , but I have not used it myself so not gonna be much help with it.
Link is to rusian language page. Google should translate for you.
https://4pda.ru/forum/index.php?showtopic=879524&view=findpost&p=73818595
Click to expand...
Click to collapse
It have stock recovery.
Mohammadreza76646 said:
It have stock recovery.
Click to expand...
Click to collapse
in summery. because i have been going back and forth in multiple different groups, multiple problem, i cant remember it all.
you have broken system, from failed root attempt, followed by failed update.
device condition is as follows.
--system not booting
--stock recovery loads
--fastboot/bootloader loads, but is in frp lock status
options are limited, at best.
I think "dload" method with service rom is best.
other option is maybe paid service like dc-unlock. But I can recall some note on there service about frp-unlock, that can only be used on device with working system. (of course if was working system, wouldn't need dc-unlock)
mrmazak said:
in summery. because i have been going back and forth in multiple different groups, multiple problem, i cant remember it all.
you have broken system, from failed root attempt, followed by failed update.
device condition is as follows.
--system not booting
--stock recovery loads
--fastboot/bootloader loads, but is in frp lock status
options are limited, at best.
I think "dload" method with service rom is best.
other option is maybe paid service like dc-unlock. But I can recall some note on there service about frp-unlock, that can only be used on device with working system. (of course if was working system, wouldn't need dc-unlock)
Click to expand...
Click to collapse
No. System boot successfully!
I will send you screenshot:
Mohammadreza76646 said:
No. System boot successfully!
I will send you screenshot:
Click to expand...
Click to collapse
here you are
Mohammadreza76646 said:
here you are
Click to expand...
Click to collapse
what about the "about phone" screen
what does it show for version?
If is all stock you should be able to go into deveolper options and enable "oem unlock". If it is greyed out and cannot switch it. Try First to remove google account (all accounts ). and reboot. See if can change then. If not, try Second to do "fastboot oem relock [enter your bootloader code here]
after relock and rebooted oem switch should be enabled again.
****RELOCK IS ONLY ADVISED IF 100% STOCK ROM****
otherwise relock could make more trouble.
Still not sure how to get IMEI back even if unlocked frp though.
**And please stop posting in other threads , the same problem , because you are getting help here.
your post in recovery thread is off topic to that thread and just makes the forum harder to maintain.
mrmazak said:
what about the "about phone" screen
what does it show for version?
If is all stock you should be able to go into deveolper options and enable "oem unlock". If it is greyed out and cannot switch it. Try First to remove google account (all accounts ). and reboot. See if can change then. If not, try Second to do "fastboot oem relock [enter your bootloader code here]
after relock and rebooted oem switch should be enabled again.
****RELOCK IS ONLY ADVISED IF 100% STOCK ROM****
otherwise relock could make more trouble.
Still not sure how to get IMEI back even if unlocked frp though.
**And please stop posting in other threads , the same problem , because you are getting help here.
your post in recovery thread is off topic to that thread and just makes the forum harder to maintain.
Click to expand...
Click to collapse
Thanks )
I'm so sorry for my posts, it's because I don't have a stable connection and I can't see notification of my thread.
I gave my phone to friend an he fix IMEI (I don't know how)
But OEM is steel lock.
I think he did it with using special box.
Mohammadreza76646 said:
Hi
I have a problem with my Honor 7X L21.
Because online update dose not work for this model I decided to updated my smartphone offline.
I downloaded Oreo update file
Unlock my phone
install twrp
update phone
every thing is going well until here
then I decided to root my phone but I saw there is no twrp on my phone
I search and I found a thread here that show how install twrp with adb use recovery ramdisk.
I install twrp on recovery ramdisk and try to root my phone. its OK but when my phone want to start its stuck on google page "just a sec..."
I boot my device on twrp and I did factory reset but the problem was still exist.
then I decided to flash update again.
I copy update file on SD card and wright code on twrp
but at the end when I reboot the recovery, twrp except stock recovery came up and my stock recovery was gone.
I reboot the system but Its loop on this page that says:
ERROR MODE
Attention!
Please update system again.
Error!
Func NO : 11 (recovery image)
Error NO : 2 (load failed!)
Please help me!!!
I try to install stock recovery and twrp with adb and huawei multi tools but it didn't work.
it shows:
"FAILED (remote: partition length get error)"
I try to unbrick my phone too but it shows same message that "FAILED (remote: partition length get error)"
Helllllp lpeaeaeaeaeaseeee!!![/QUOTE
Are u able.to boot into twrp ?
Click to expand...
Click to collapse
Hello I have a Huawei Mate-SE (with bootloader unlocked and rooted with magisk v16). I have been using the android custom rom RRO v6 (RR-O-v6.0.0-20180401-bnd-OpenKirin) for around a month now. I got this exact same problem about the White Screen saying "ERROR MODE Attention...." since I updated the Magisk to latest version (from the installed application) and rebooted my phone. SInce I rebooted I am getting that same error which makes the phone loops into it for a few times and then it loads the Huawei eRecovery that offers me some options that I am not sure what would do to my phone.
I have been trying to connect to adb tools/fastboot but it doesn't detect the phone and im pretty sure I have the device drivers installed on my computer since nothing have changed in my pc for a month now since I flashed RRO on it.
Is there any other mode besides recovery that would allow me to connect adb/fastboot to it? Or does anyone knows how should I proceed?
IonDEfeso said:
Hello I have a Huawei Mate-SE (with bootloader unlocked and rooted with magisk v16). I have been using the android custom rom RRO v6 (RR-O-v6.0.0-20180401-bnd-OpenKirin) for around a month now. I got this exact same problem about the White Screen saying "ERROR MODE Attention...." since I updated the Magisk to latest version (from the installed application) and rebooted my phone. SInce I rebooted I am getting that same error which makes the phone loops into it for a few times and then it loads the Huawei eRecovery that offers me some options that I am not sure what would do to my phone.
I have been trying to connect to adb tools/fastboot but it doesn't detect the phone and im pretty sure I have the device drivers installed on my computer since nothing have changed in my pc for a month now since I flashed RRO on it.
Is there any other mode besides recovery that would allow me to connect adb/fastboot to it? Or does anyone knows how should I proceed?
Click to expand...
Click to collapse
I have seen where the magisk update screwed up and patches the kernel intead of the ramdisk.
Power off , long press power button.
Hold volume down and plug in USB from PC.
This should cause it to boot into fastboot mode.
Then flash the stock kernel. And the stock or first patched ramdisk. (From earlier root)
mrmazak said:
I have seen where the magisk update screwed up and patches the kernel intead of the ramdisk.
Power off , long press power button.
Hold volume down and plug in USB from PC.
This should cause it to boot into fastboot mode.
Then flash the stock kernel. And the stock or first patched ramdisk. (From earlier root)
Click to expand...
Click to collapse
Hi thank you I was able to finally detect the device now. I am unsure about the kernel is that the recovery.img or system.img files I downloaded (i saved every file i used when I installed the rom) or do I need to look for the kernel somewhere else? I do have the complete_twrp_ramdisk.img file though.
Edit, I did more research and found the stock kernel is withing the boot.img file which I dont have so I looked up for the official BND-L34 oreo update and im currently downloading to extract the stock boot.img from the update.zip and flash it. Since that download was going to take me a while anyway i tried flashing the twrp recovery file without success (didn't changed anything) so i guess I should follow the instructions you gave me by flashing the kernel first then the twrp recovery.
mrmazak said:
I have seen where the magisk update screwed up and patches the kernel intead of the ramdisk.
Power off , long press power button.
Hold volume down and plug in USB from PC.
This should cause it to boot into fastboot mode.
Then flash the stock kernel. And the stock or first patched ramdisk. (From earlier root)
Click to expand...
Click to collapse
Do you know what the boot.img files name is after extraction?
I have extracted all 3 update zips and cannot find anything called boot.img
By the way, thank you.. After updating magisk I have been dealing with failed recovery and failed boot for over a week and this is the first reply anywhere that looks promising
IonDEfeso said:
Hi thank you I was able to finally detect the device now. I am unsure about the kernel is that the recovery.img or system.img files I downloaded (i saved every file i used when I installed the rom) or do I need to look for the kernel somewhere else? I do have the complete_twrp_ramdisk.img file though.
Edit, I did more research and found the stock kernel is withing the boot.img file which I dont have so I looked up for the official BND-L34 oreo update and im currently downloading to extract the stock boot.img from the update.zip and flash it. Since that download was going to take me a while anyway i tried flashing the twrp recovery file without success (didn't changed anything) so i guess I should follow the instructions you gave me by flashing the kernel first then the twrp recovery.
Click to expand...
Click to collapse
if you were on oreo. then there is not a boot.img, instaed there is seperate ramdisk.img and kernel.img.
i have all the files already extracted for oreo and a backup from nougat as well.
https://androidfilehost.com/?w=files&flid=265998
make sure you know what you are doing before flashing.
for example. on oreo the boot and recovery share one kernel image. SO if kernel is messed up you will not be able to boot "boot" or "recovery"
EMUI 8 Stock ROMs:
3.2.1-0 by pretoriano80 (with data decryption on Android 8 )
https://mega.nz/#!Fgd0xa4R!1o5ejzDnkLJLG2tAZG-STtlJ4nnNCHfwwZdOlmOkrVw
EMUI 8 Custom ROMs:
3.2.1.0 by Catuva21:
https://mega.nz/#!JlkRVY7b!Hz0QTmbgmMNeCaU-PmVRBGKsdd9pslmWNkOZpE6I8ZA
3.2.3-0 by Askuccio
https://mega.nz/#!h9903SqS!aRXc9x6Kuz_GclVy_3ZExCLDSdnp7Ee8VIgfqOG9x8k
Chinese ROMs (inc. KangVip):
3.2.1-0
https://mega.nz/#!sp0UyCDR!bq10MAyh0sddUCPi0zecQzrmLfCESFvNlCiQ3vkPMqI
EMUI 9.1 Stock ROM & Custom ROMs:
3.2.1-0 GAGUGA Edition
https://mega.nz/#!tkcTlATI!A8UJGPBGtxJbLcUOJoxCGJj5PFZXzCnjbb3OkwqKTP8
EMUI 9.1 Custom ROMs:
3.4.0-0-emui9_eR by @S_mak
https://mega.nz/#!B8kWgJDC!_hj7xkTzF9Uj66wKjtrWPHEV5Dbkk7Q256tuiKg7FQU
On [A12], [A12.1] GSIs use 3.4.0-0-emui9_eR .
Do you mean you can install these over erecovery partition?
adamfirari said:
Do you mean you can install these over erecovery partition?
Click to expand...
Click to collapse
These TWRPs allow you to install any compatible TWRP over eRecovery.
Hi!
Is there a recovery that is able to make a full backup (modem nvm ecc..)?
TureX said:
Hi!
Is there a recovery that is able to make a full backup (modem nvm ecc..)?
Click to expand...
Click to collapse
Hello,
I never use Nandroid backup, so I don't know. Test it and let us know
hi all,
addonsu.zip works?
my output trying to flash via twrp
...
Installing su addon...
set_metadata: Error on lstat of "/system/addon.d/51-
addon.su": No such file or directory
Updater procedd ended with ERROR: 7
Error installing zip file '/sdcard/Download/addonsu-
16.0-arm-signed.zip'
...
twrp seems work fine, i can flash los and gapps without problem...
thank you
wax_77 said:
hi all,
addonsu.zip works?
my output trying to flash via twrp
...
Installing su addon...
set_metadata: Error on lstat of "/system/addon.d/51-
addon.su": No such file or directory
Updater procedd ended with ERROR: 7
Error installing zip file '/sdcard/Download/addonsu-
16.0-arm-signed.zip'
...
twrp seems work fine, i can flash los and gapps without problem...
thank you
Click to expand...
Click to collapse
HI!
Which vendor are you using? And which twrp shared are you using? Does lineageos 16 official boot keeping twrp installed?
Thanks in advance
wax_77 said:
hi all,
addonsu.zip works?
my output trying to flash via twrp
...
Installing su addon...
set_metadata: Error on lstat of "/system/addon.d/51-
addon.su": No such file or directory
Updater procedd ended with ERROR: 7
Error installing zip file '/sdcard/Download/addonsu-
16.0-arm-signed.zip'
...
twrp seems work fine, i can flash los and gapps without problem...
thank you
Click to expand...
Click to collapse
Hello,
I successfully installed the addonsu-16.0-arm64 using
TWRP
You have to enable root in Developer options. Works fine...
Hi there,
which TWRP can I use to downgrade to Oreo via HuRupdater?
Thanks.
Fjord1 said:
Hi there,
which TWRP can I use to downgrade to Oreo via HuRupdater?
Thanks.
Click to expand...
Click to collapse
3.2.1-0 by pretoriano80 .
Note: If you don't have the required files stored somewhere, then it's just an academic question - Firmware finder is ďead.
-Alf- said:
Firmware finder is ďead.
Click to expand...
Click to collapse
It makes me sad...
And what about dload method?
Fjord1 said:
downgrade to Oreo
Click to expand...
Click to collapse
Fjord1 said:
dload method
Click to expand...
Click to collapse
you will get absolutely no success, it may even brick your phone.
Hi all. I am trying to recover content from a MediaTab T5 with a Damaged screen (no picture). I've managed to install these recoveries and reboot into them. However none of them provide an adb interface for shell access, only a virtual usb cd rom drive appears. How can I obtain recovery adb access? I need to enable USB debugging and push adbkey...
Anyone have any clues how I can work around this please. Is patched boot img the only way forward?
OK good news I Successfully booted into recovery and have adb access. I think the key was to power on with vol+, but WITHOUT the USB cable attached. If USB cable is attached then it tries to boot to system regardless
-Alf- said:
Hello,
I never use Nandroid backup, so I don't know. Test it and let us know
Click to expand...
Click to collapse
hi, I was just wondering incase something goes wrong, can you link me some thread or guide to go back to stock firmware (I do have the full firmware files)
Mahad Habib said:
hi, I was just wondering incase something goes wrong, can you link me some thread or guide to go back to stock firmware (I do have the full firmware files)
Click to expand...
Click to collapse
I'm not sure I fully understand your question :
- go back to stock from custom ROM?
- what full FW do you have?
-Alf- said:
I'm not sure I fully understand your question :
- go back to stock from custom ROM?
- what full FW do you have?
Click to expand...
Click to collapse
yes that's my question.
the one I have is
"Huawei P20 Lite ANE-L21 Anne-L21 8.0.0.144(C185) Firmware Android 8.0.0 EMUI 8.0.0"
I know this works because I used it to downgrade.
Mahad Habib said:
yes that's my question.
the one I have is
"Huawei P20 Lite ANE-L21 Anne-L21 8.0.0.144(C185) Firmware Android 8.0.0 EMUI 8.0.0"
I know this works because I used it to downgrade.
Click to expand...
Click to collapse
Yes, you can revert to stock flashing this Service ROM , if yot are running EMUI 8. For EMUI 9.1 use Service ROM 9.1.0. This process will erase all your data and lock the BL again!
Or, simply flash SYSTEM.img extracted from Service ROM using Huawei
update extractor. This procedure will not erase your data ,bootloader remains unlocked etc.
Hey Alf,
Were you able to flash any of the recoveries over the erecovery?
The 3.2.1-0 GAGUGA Edition has a built in option but it didn't work for me, no failures but when I hold down vol + I still get erecovery. I tried flashing 3.4.0-0-emui9_eR by @S_mak to erecovery_ramdisk but got a command not allowed.
PRA-LX1 on a C432 base, got CAOS11 system and Magisk in recovery. Since the recovery partition is occupied by Magisk having TWRP on erecovery would be ideal.
Thank you for your posts, they've been useful.
hopeless_bricker said:
Hey Alf,
Were you able to flash any of the recoveries over the erecovery?
The 3.2.1-0 GAGUGA Edition has a built in option but it didn't work for me, no failures but when I hold down vol + I still get erecovery. I tried flashing 3.4.0-0-emui9_eR by @S_mak to erecovery_ramdisk but got a command not allowed.
PRA-LX1 on a C432 base, got CAOS11 system and Magisk in recovery. Since the recovery partition is occupied by Magisk having TWRP on erecovery would be ideal.
Thank you for your posts, they've been useful.
Click to expand...
Click to collapse
flash TWRP , run command
fastboot flash recovery_ramdisk (TWRP's_name).img
(Since A8 and above you can not install TWRP over eRecovery from fastboot, only from TWRP),
- Copy TWRP file to the SD card, and also copy to card Stock Recovery_ramdisk.
- Enter TWRP, select storage - SD Card, select "Install image", find TWRP file and mark eRecovery, swipe.
- Go back, find Stock recovery_ramdisk file, (or magisk-patched recovery_ramdisk on EMUI 9) , mark Recovery, swipe. Reboot system.
P.S.: as far as i know the PRA-LX1 hasn't received an upgrade to Pie (correct me if I'm wrong) , so i don't understand
hopeless_bricker said:
Since the recovery partition is occupied by Magisk
Click to expand...
Click to collapse
-Alf- said:
flash TWRP , run command
fastboot flash recovery_ramdisk (TWRP's_name).img
(Since A8 and above you can not install TWRP over eRecovery from fastboot, only from TWRP),
- Copy TWRP file to the SD card, and also copy to card Stock Recovery_ramdisk.
- Enter TWRP, select storage - SD Card, select "Install image", find TWRP file and mark eRecovery, swipe.
- Go back, find Stock recovery_ramdisk file, (or magisk-patched recovery_ramdisk on EMUI 9) , mark Recovery, swipe. Reboot system.
P.S.: as far as i know the PRA-LX1 hasn't received an upgrade to Pie (correct me if I'm wrong) , so i don't understand
Click to expand...
Click to collapse
I got it wrong, it's a ANE-LX3! Mixed up with my other phone, sorry. In principle that method works, thank you. I didn't get to actually test it because it seems the Magisk recovery overrides the boot procedure so it always boots to recovery automatically.
Handy but I can't boot into the erecovery with the button combo now.
P.S.: I'm having issues with audio device switching. If I get a phone call with headphones inserted it routes to the speaker and I can't change it. If I remove the headphones then the mic doesn't work. I also have a bit inconsistent connection over bluetooth, sometimes it is connected but still plays over the speakers. I have the Huawei switch method enabled in the phh options. Did you experience this?