Huawei released, probably final, update for P8 with android 6 Marshmallow
Download here
You can upgrade directly from B200, but i highly recommend to you factory reset after upgrade, otherwise phone can be slow, laggy and battery can drain fast.
ROOT link was deleted due pirated content, if i will see legal way i will update
Updated from b200 and everythings seems fine. Had an error during install but phone seems ok with B317. Battery seems to go a bit fast but need tot test for a couple of days
[email protected] said:
Updated from b200 and everythings seems fine. Had an error during install but phone seems ok with B317. Battery seems to go a bit fast but need tot test for a couple of days
Click to expand...
Click to collapse
i suggest to full wipe data and cache after update, there could be some probles if you wont and battery drain in B317 should be noticable better than b200
00471 said:
i suggest to full wipe data and cache after update, there could be some probles if you wont and battery drain in B317 should be noticable better than b200
Click to expand...
Click to collapse
It's done automaticly during install, it's not a real upgrade the wipe is default
Hi, last weekend i tried the Beta and wasnt satisfied and rolled back to B200.
System was always on and whatsapp en mail notifications didnt pushed true, eventough i had all the settings right.
I want to try this version but does anyone knows if there is a rollback to B200 if i dont like it?
djg269 said:
Hi, last weekend i tried the Beta and wasnt satisfied and rolled back to B200.
System was always on and whatsapp en mail notifications didnt pushed true, eventough i had all the settings right.
I want to try this version but does anyone knows if there is a rollback to B200 if i dont like it?
Click to expand...
Click to collapse
of course, there is way to rollback, im testing it, i will let to know for all later
[email protected] said:
Updated from b200 and everythings seems fine. Had an error during install but phone seems ok with B317. Battery seems to go a bit fast but need tot test for a couple of days
Click to expand...
Click to collapse
Yeah battery goes faster at yellow zone mobile signal, but when red or green it seems not bad.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
link dosent work !!
the file you are trying to download is no longer available
im sorry, i forgot to edit OP, link was deleted because of pirated PRO copy of SuperSU and i can not reupload it
It worked only partially.
I was on B200, rooted and with TWRP installed. In order to use this update I've flashed back stock recovery.
Update went well half way and then crashed with some errors. Phone rebooted and surprise, was updated to Marshmallow 6.0 B317.
Biggest problem is, I've lost stock recovery and can't flash TWRP or stock recovery anymore. Fastboot says it is flashed:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery twrp2871.img
target reported max download size of 471859200 bytes
sending 'recovery' (25880 KB)...
OKAY [ 0.550s]
writing 'recovery'...
OKAY [ 0.339s]
but phone does not go to recovery just bootloops few times and then booting the system normally.
I'm also unable to relock bootloader. No factory reset or wiping cache works anymore.
I'm in a mess now.
i have the same problem. nothing seems to work. no stock recovery and no twrp.
Download the file used to root b313. It contains twrp_new.img that will work. No other recoveries will work. If you want to root, download the latest superSU 2.67. That will automatically patch your boot image and root. To install busybox, download BuzyBox Free and install using that. Remember to install into system/xbin for compatibility with apps like Viper.
The easiest way to boot into recovery or bootloader is via adb.
tomtro74 said:
I was on B200, rooted and with TWRP installed. In order to use this update I've flashed back stock recovery.
Update went well half way and then crashed with some errors. Phone rebooted and surprise, was updated to Marshmallow 6.0 B317.
Biggest problem is, I've lost stock recovery and can't flash TWRP or stock recovery anymore. Fastboot says it is flashed:
Click to expand...
Click to collapse
You have to re-flash b317 using three buttons (power, vol+, vol-)
mai55 said:
You have to re-flash b317 using three buttons (power, vol+, vol-)
Click to expand...
Click to collapse
No luck there as it forces the update through recovery, same like update with the service menu from the stock phone app.
Problem is, there is NO stock or custom recovery in the device and I don't know the way to flash it other than through fastboot and this method does not work.
I need to get the stock recovery working first, before I can flash anything else.
rodlane said:
Download the file used to root b313. It contains twrp_new.img that will work. No other recoveries will work. If you want to root, download the latest superSU 2.67. That will automatically patch your boot image and root. To install busybox, download BuzyBox Free and install using that. Remember to install into system/xbin for compatibility with apps like Viper.
The easiest way to boot into recovery or bootloader is via adb.
Click to expand...
Click to collapse
Thanks but I can't find a link to this file
i will upload it for you in about 5 hours, still got that root package
i can't find a link this recovery
irgendeinname said:
i can't find a link this recovery
Click to expand...
Click to collapse
im gonna upload twrp recovery for marshmallow today, dont worry, be patient
http://forum.xda-developers.com/showthread.php?p=65499548
thank you
Related
I've got an HTC one which is unlocked and S-Off with CWM and still running 1.29.401.13.
I received a notification of an OTA (2.24.401.1, which includes android 4.2.2) the other day..
I downloaded it and chose to install it. Once I did, my phone booted into CWM and instead of a new ROM, I'm shown an error:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I've also found the downloaded OTA.zip and tried to install it manually through CWM, but I get this:
Could anyone point me in the direction of the cause or fix please?
Thanks in advance,
'tunes
mad_tunes said:
I've got an HTC one which is unlocked and S-Off with CWM and still running 1.29.401.13.
I received a notification of an OTA (2.24.401.1, which includes android 4.2.2) the other day..
I downloaded it and chose to install it. Once I did, my phone booted into CWM and instead of a new ROM, I'm shown an error:
I've also found the downloaded OTA.zip and tried to install it manually through CWM, but I get this:
Could anyone point me in the direction of the cause or fix please?
Thanks in advance,
'tunes
Click to expand...
Click to collapse
flash stock recovery and relock your bootloader for official OTA updates. you can't install OTA's with a custom recovery and an unlocked bootloader.
herwegan said:
flash stock recovery and relock your bootloader for official OTA updates. you can't install OTA's with a custom recovery and an unlocked bootloader.
Click to expand...
Click to collapse
Thanks herwegan. I've just flashed a stock recovery and relocked my bootloader (now shows relocked).
I let the phone re-download the OTA and chose to install it. Now, it restarts and stops at this:
any more ideas please?
mad_tunes said:
Thanks herwegan. I've just flashed a stock recovery and relocked my bootloader (now shows relocked).
I let the phone re-download the OTA and chose to install it. Now, it restarts and stops at this:
any more ideas please?
Click to expand...
Click to collapse
is your device rootet? if yes, unroot it temporary for OTA
herwegan said:
is your device rootet? if yes, unroot it temporary for OTA
Click to expand...
Click to collapse
I've unrooted it and tried the same again... and got the same.
I've found that I get stuck at the same screen as above if I try to do a factory reset from within the bootloader too.
.. I also can't sideload a ROM, The ROM's copied to my phone, but I'm then told:
E:\ cant open /tmp/update.zip (bad)
installation aborted
I think I might be making some progress.
After setting every back to as stock as possible, I was still finding the same problem.
So, I found and installed an old RUU, which installed OK on the second attempt. (I was oriignally running .13, the RUU was an older .7)
This has let me run through the OTAs back up to .12 so far, it's re-downloading the latest one atm. I'm hoping it'll install OK like the .12 and then I can re-unlock everything.
edit:
the latest OTA installed just fine.
Thanks for the suggestions
I thought I'd got this sorted out but something's still not right.
Everything looks fine once booted but whatever I backup from within CWM, it runs through as you'd expect but its not shown when I browse my SDCard once booted.
inside CWM, I see just
0/
clocworkmod/
legacy/
obb/
the contents of the sdcard are shown as being inside 0/, it's like CWMs working at a folder higher up the tree then it has for me before.
that means I cant delete or copy backup from a pc..
does anyone know what might be wrong please?
mad_tunes said:
I thought I'd got this sorted out but something's still not right.
Everything looks fine once booted but whatever I backup from within CWM, it runs through as you'd expect but its not shown when I browse my SDCard once booted.
inside CWM, I see just
0/
clocworkmod/
legacy/
obb/
the contents of the sdcard are shown as being inside 0/, it's like CWMs working at a folder higher up the tree then it has for me before.
that means I cant delete or copy backup from a pc..
does anyone know what might be wrong please?
Click to expand...
Click to collapse
you're running 4.2.2 now, so this is normal, you need to move your backup files to the sd card folder to be able to see them on a pc.
get a root explorer, the cwm backup files are now in mnt/shell/emulated/clockworkmod/backup
cheers
i had just been doing some reading and have backups moving to I can pull them off onto my laptop.
Thanks a ton though, that could have cracked it if I hadnt kept searching.
The OTA has just come. I have rooted phone with twrp recovery installed.
What to do now?
As I have read the forum, I should from http://forum.xda-developers.com/ascend-p7/development/recovery-t2811965 install back “Huawei Ascend P7-L10 thanks to XQC”, and that is it?
The phone will be unrooted, so I have to root it again.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Is there anything else?
=kriticar;59281321
Is there anything else?
Click to expand...
Click to collapse
Yes,on B.609 twrp doesn't work,you must use chinese cwm translated to english and you will have not full root with stock kernel unless you flash via adb custom kernel.
gregysk said:
Yes,on B.609 twrp doesn't work,you must use chinese cwm translated to english and you will have not full root with stock kernel unless you flash via adb custom kernel.
Click to expand...
Click to collapse
For now I would like to try stock rom.
The zip file (* Huawei Ascend P7-L10 thanks to XQC) on [RECOVERY][ Unofficially Open Recovery TWRP 2.8.1.0 ][ 09/11/2014 ] thread consists of two recoveries: recovery.img and recovery2.img.
I believe that I should flash recovery.img, shuldn't I?
After flasnih recovery I will just start the update.
Regards,
Zoran
kriticar said:
I believe that I should flash recovery.img, shuldn't I?
After flasnih recovery I will just start the update.
Regards,
Zoran
Click to expand...
Click to collapse
1.Yes,flash (stock)recovery.img
2.Tap download and install and let the phone do the upgrade
gregysk said:
1.Yes,flash recovery.img
2.Tap download and install and let the phone do the upgrade
Click to expand...
Click to collapse
OK, thanks. I will do the procedure now.
Regards, and thanks again.
Well, the update has failed.
I am informed to go to the http://www.emui.com/motiondownload.php?mod=restore which doesn't work.
I was able to shutdown the phone and to reboot it again.
Apon booting the phone I got the message that update has failed and by clicking on it I went to the update screen.
Looks like huawei is checking wheather the phone is rooted or something else.
What to do now?
Install stock recovery and then update through OTA. You cannot use OTA with custom recovery.
You didnt read update notes ("make sure your phone has not been rooted...").
Ne citas upute zemo
ibeqa said:
Install stock recovery and then update through OTA. You cannot use OTA with custom recovery.
Click to expand...
Click to collapse
I have installed stock recovery in the following way:
1. I have downloaded a zip file (* Huawei Ascend P7-L10 thanks to XQC) from [RECOVERY][ Unofficially Open Recovery TWRP 2.8.1.0 ][ 09/11/2014 ] thread
2. I have unpacked recovery.img from zip file
3. As a root, I have used adb reboot bootloader, fastboot flash recovery recovery.img, fastboot reboot
4. Now I have downloaded and started the update
I believe that this is enough.
Do I have to unroot the phone before update?
Is the stock recovery from the twrp thread OK for this update?
gregysk said:
You didnt read update notes ("make sure your phone has not been rooted...").
Ne citas upute zemo
Click to expand...
Click to collapse
How to unroot the phone?
kriticar said:
How to unroot the phone?
Click to expand...
Click to collapse
Try with RootGenius,unroot option.
I have, but the update is still failing.
Does someone know what update procedure checks before upgrade?
kriticar said:
I have, but the update is still failing.
Does someone know what update procedure checks before upgrade?
Click to expand...
Click to collapse
check this http://forum.xda-developers.com/ascend-p7/help/unable-to-downgrade-ascend-p7-l10-b609-t3050761
for this guy it worked (you don't need to downgrade to 2.3 if you don't want)
ibeqa said:
check this http://forum.xda-developers.com/ascend-p7/help/unable-to-downgrade-ascend-p7-l10-b609-t3050761
for this guy it worked (you don't need to downgrade to 2.3 if you don't want)
Click to expand...
Click to collapse
Well, I am still on 2.3, but I cannot go up.
After starting the update, the phone boots to the recovery, than:
finding update package
opening update package
verifying update package
instaling update
huawei factory resizing
update failed please try again
I have option to shutdown the phone and that is basically it.
kriticar said:
Well, I am still on 2.3, but I cannot go up.
After starting the update, the phone boots to the recovery, than:
finding update package
opening update package
verifying update package
instaling update
huawei factory resizing
update failed please try again
I have option to shutdown the phone and that is basically it.
Click to expand...
Click to collapse
man tell me what recovery you have currently on ?
How to check that?
Download full ROM 609 and copy dload folder to SD card. Start install process by holding vol+ vol- and power button at the same time
Sent from my novo9-Spark using Tapatalk
I cannot install official download in that way.
kriticar said:
I cannot install official download in that way.
Click to expand...
Click to collapse
Let's go in this step by step!
1. Confirm which recovery you have installed, 2.3 or 3.0. If you did not flash official Emui 3.0 than you need emui 2.3 official recovery. Official recovery you can extract from official Emui 2.3 ROMs (you will need 2.3 ROM also for flashing).
2. Flash the needed recovery (if needed).
3. After downloading official 2.3 ROM, open it and check if there is a folder "dload". On that folder should be a file "update.app". Copy the folder "dload" together with it's content on the root of your SD card.
4. Go to settings -> update -> local update and start update (local update) , if local update does not work than try force update.
5. Confirm on the forum
How to confirm recovery version?
<3e>?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Download : Google Drive
How to flash?
1. Shutdown your Z5C
2. Connect to PC in Fastboot mode
3. Flash with this command
Code:
fastboot.exe flash recovery twrp_recovery.img
Do NOT forget to hit Thanks button :fingers-crossed:
Credits : bbs.gfan.com
Contributor : @grayleshy
Seriously, someone took my recovery and changed the theme and all?
grayleshy said:
Seriously, someone took my recovery and changed the theme and all?
Click to expand...
Click to collapse
I don't know it is yours or not? How can you be sure?
Did you left any #comment# for this? If you did I will add you as a contributor.
delete
grayleshy said:
ro.build.host=grayleshy-virtualbox
Click to expand...
Click to collapse
I see, thanks. I edit the post.
grayleshy said:
delete
Click to expand...
Click to collapse
sorry I did not go through your consent then modify the TWRP, sorry again.
your work are very nice!
thanks again.
@sceryavuz What sources did you use to compile? I tried Dirty Unicorn's and Omnirom's but I had lot of errors with both.
DJHasis said:
@sceryavuz What sources did you use to compile? I tried Dirty Unicorn's and Omnirom's but I had lot of errors with both.
Click to expand...
Click to collapse
Here : https://forum.xda-developers.com/crossdevice-dev/sony/twrp-3-1-0-z5-z5c-z5p-t3571050
this work on 7.1.1?
sceryavuz said:
GreyLeshy said:
Seriously, someone took my recovery and changed the theme and all?
Click to expand...
Click to collapse
I don't know it is yours or not? How can you be sure?
Did you left any #comment# for this? If you did I will add you as a contributor.
Click to expand...
Click to collapse
isn't there a rule about not doing this?
it's flashing well but it doesn't work on 7.1.1.
I'm new to the Z5C and currently not sure about choosing the best approach for installing TWRP.
Ilko said:
it's flashing well but it doesn't work on 7.1.1.
I'm new to the Z5C and currently not sure about choosing the best approach for installing TWRP.
Click to expand...
Click to collapse
What do you mean "it doesn't work"? How did you install TWRP?
I meant what I said, after flashing, rebooting into recovery has no effect, it boots normally. I know that I'm doing it wrong for now but looking for the right method.
BTW, just found that for being as up-to-date as possible the only way seems to flash a .33 firmware first. I already miss my ZR, everything was easier...
When I give twrp permission to modified system partition my phone fail to boot to system is there any fix for that?
I am using Xperia z5 compact E5803
Android version: 7.1.1
Build number: 32.4.A.0.160
Kernel: 3.10.48-perf-g5e25a09 (stock)
Mostafa8296 said:
When I give twrp permission to modified system partition my phone fail to boot to system is there any fix for that?
I am using Xperia z5 compact E5803
Android version: 7.1.1
Build number: 32.4.A.0.160
Kernel: 3.10.48-perf-g5e25a09 (stock)
Click to expand...
Click to collapse
I don't know what's the problem but when I flashed Greenkernel every thing works fine.It maybe the stock Kernel was the problem
Lost TWRP
I lost twrp tried to flash in fastboot mode but having errors..
I connect pc via fastboot
opening command screen
fastboot flash recovery recovery.img and getting this error
-target reported max download size of 536870912
sending recovery (19800 KB )
OKAY ( 0,757s )
writing recovery ...
failed ( remote: image is not a boot image, nor ELF )
finished. total time : 0,777s
It s first time i am having this problem.. I can flash a kernel bot cant flash a recovery.
Also not working this command too fastboot boot recovery recovery.img
I dont think i have a driver problem ( i checked many times )
Ilko said:
I meant what I said, after flashing, rebooting into recovery has no effect, it boots normally. I know that I'm doing it wrong for now but looking for the right method.
BTW, just found that for being as up-to-date as possible the only way seems to flash a .33 firmware first. I already miss my ZR, everything was easier...
Click to expand...
Click to collapse
I have the same problem you had. The device simpy wont boot into recovery. Did you manage to get it working with a .33 firmware? did you use Stock kernel?
maxi*king said:
I have the same problem you had. The device simpy wont boot into recovery. Did you manage to get it working with a .33 firmware? did you use Stock kernel?
Click to expand...
Click to collapse
Yes, in fact, it was a problem that I wasn't expecting. I was trying to boot into recovery via reboot menu or app, but it's not actually working. Simply try VolDown+power while the device is off. You can release when it vibrates.
Sent from my Funky Z5C
Ilko said:
Yes, in fact, it was a problem that I wasn't expecting. I was trying to boot into recovery via reboot menu or app, but it's not actually working. Simply try VolDown+power while the device is off. You can release when it vibrates.
Click to expand...
Click to collapse
Thank you so much! :good:
Now it works
I can't believe that I flashed my phone multiple times because I didn't manage to start into recovery :cyclops:
Can´t get twrp to work on z5c
Hi guys!
I just bought a new Z5C and already saved TA, unlocked bootloader and flashed twrp (twice - 3.0.2 with rootkernel, this 3.1.1 with fastboot). All on Android 5.1.1 (32.0.A.6.200) stock rom. Now the phone is working and rooted with SuperSU.
Problem:
I can only start the old 3.0.2 twrp inside the kernel with pressing volume up when led is yellow but I can´t start 3.1.1 with power + volume down. I don´t get a purple led and most of times it just starts Android. Sometimes it gets stuck on Sony bootscreen (guess this happens when I did correct button combination but twrp fails to start?).
Any idea where the problem is?
fastboot flash recovery twrp_recovery.img results in:
sending 'recovery' (19800 KB)...
OKAY [ 0.459s]
writing 'recovery'...
OKAY [ 0.170s]
finished. total time: 0.636s
Click to expand...
Click to collapse
So everything should be ok, right?
Kernel can not be the problem as I understand as kernel has nothing to do with recovery, right?
Disclaimer: No guarantees. Follow at your own risk. I am not responsible for bricked phones.
Credits to 4PDA
Prerequisites:
Knowledge of OEM unlocking from Developer options, adb, and fastboot
Knowledge of QPST in case you encounter bootloop, so you can revert to a reliable stock ROM
Unlocked bootloader (from here)
1) Get your bootloader unlocked, if you haven't already.
- Visit https://www.zui.com/iunlock
- Enter the IMEI1 (Second number when you call *#06# with the phone)
- Enter the Device ID from the Bootloader/Fastboot (Hold VOL- and Power, while device is off)
- Enter your email and captcha and set the checkmark to acknowledge voiding your warranty.
- If you get an error saying that your IMEI1 is wrong, put in a sim card and wait a few hours. If it still doesn't work, write an email to [email protected]
- In the developer settings in android, enable usb debugging and oem unlock.
- Flash the sn.img file you receive with fastboot (again, hold vol- and power while the device is off). Command is 'fastboot flash unlock sn.img'. You need compatible usb drivers, qualcom drivers and adb/fastboot to do that. Use google or write me a PM if you have trouble with that.
- execute 'fastboot oem unlock-go'
- This allows you to use fastboot to flash custom system/boot/vendor/vbmeta images
Click to expand...
Click to collapse
@wzsx150's recovery-TWRP-3.3.1-1015-LENOVO_Z5S-CN-wzsx150.img MEGA Google Drive
@wzsx150's TWRP for Android 10 TWRP-3.3.2B-0508-LENOVO_Z5S-10.0-CN-wzsx150-fastboot.7z (extract the IMG file and flash using fastboot)
3) Now you can flash TWRP.
- Download ...
- Flash it from the Bootloader with 'fastboot flash recovery recovery-TWRP-3.3.1-1015-LENOVO_Z5S-CN-wzsx150.img'
- Press VOL UP / VOL DOWN to navigate to recovery.
Click to expand...
Click to collapse
11.3.169: L78071_11.3.169_DEV_FullOTA.zip
11.5.096 Update: ZUI_11.3.169_DEV_TO_ZUI_11.5.096_ST.zip
11.5.111 Update: ZUI_11.5.096_TO_ZUI_11.5.111_ST.zip
Other files, use at your own risk
Disable_Dm-Verity_ForceEncrypt_08.18.2019.zip
Official TWRP for jd2019
In recovery, Format data, then wipe Dalvik/ART Cache, Cache, Data
Reboot to recovery
Install in order, without rebooting, 11.3.169 -> 11.5.096 Update -> 11.5.111 Update.
Install Magisk 20.4
Install TWRP for Android 10 (above) using fastboot if the update replaces stock recovery after rebooting
Edited out from original
Wipe Data and flash Disable_Dm-Verity_ForceEncrypt_08.18.2019.zip
In order not to encrypt Data in the future, install Official TWRP immediately after installing updates. Install > Install Image > twrp-3.3.1-0-jd2019.img
Install GApps
Note: I do not know if the 11.5 update relocks the bootloader. It doesn't lock the bootloader.
I had bootloop from OpenGApps. 4PDA post advises to use BiTGApps. You can install Google Play Store from the built-in Lenovo App Center and that's what I did.
Haven't tried disabling dm-verity and forceencrypt.
Good job, my man, I'll check it out tonight and prepare ourselves an updateable package for people coming from any rom to avoid the hassle of going through all of that. As soon as I get it working will release a new TWRP for Android 10.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
carlshark said:
View attachment 5036881
Click to expand...
Click to collapse
Nice job man, so the update works as it should? I'm patching the images and will upload a full ota update to make it easier to move between Pie and 10. Regarding recoverys, did you test any twrp? Any decryption working? What about this official twrp, does it actually work? Thanks for the files man, this will make everything much easier
jacoghi said:
Nice job man, so the update works as it should? I'm patching the images and will upload a full ota update to make it easier to move between Pie and 10. Regarding recoverys, did you test any twrp? Any decryption working? What about this official twrp, does it actually work? Thanks for the files man, this will make everything much easier
Click to expand...
Click to collapse
I've been using the phone on 11.5.111 for a couple of days now.
I flashed both the 3.3.2 TWRP of @wzsx150 and the official TWRP and they seem to be working. I didn't turn off encryption so it seems to work well.
Happy to have helped in a small way. Thank you for your hard work!
links not works
vesdan said:
links not works
Click to expand...
Click to collapse
Thanks for the heads up, apparently the original poster removed the links. Will be uploading the ones I used.
Reuploading done.
Thank you very much
Thanks for the rom my friend.
Can you please upload the latest update cause i am rooted and it cannot be installed via the system.
Also guys ,does anyone knows if i can put the latest android 10 with multilanguage rom ?Thank you for everything ,i appreciate.
thx for the post, i am wondering if the ota will be avaliable, because the bootloader unlock site does not approve my imei number
sorry guys, i rushed and flashed the gapps and now facing a bootloop, i prepared qpst and a stock rom but i verz rom i am missing a content.xml file, can anyone please help me?
galardo_2 said:
sorry guys, i rushed and flashed the gapps and now facing a bootloop, i prepared qpst and a stock rom but i verz rom i am missing a content.xml file, can anyone please help me?
Click to expand...
Click to collapse
https://mega.nz/folder/PegDDQ7I#bmCCIt1lAWAe7ui_gkmwSQ/folder/fOAQ1QCa
here is many ROMS
Do not install gapps on ZUI !!!!
vesdan said:
https://mega.nz/folder/PegDDQ7I#bmCCIt1lAWAe7ui_gkmwSQ/folder/fOAQ1QCa
here is many ROMS
Do not install gapps on ZUI !!!!
Click to expand...
Click to collapse
but the qpst app need an aditional content.xml file, where can i get one
Install global via fastboot, all is included or in qfil ROM is all in zip file
vesdan said:
Install global via fastboot, all is included or in qfil ROM is all in zip file
Click to expand...
Click to collapse
I tried and failed again
i tired and failed again
galardo_2 said:
thx for the post, i am wondering if the ota will be avaliable, because the bootloader unlock site does not approve my imei number
Click to expand...
Click to collapse
I tried unlocking 2 Lenovo phones. The first attempt had sent me an email, but the second attempt did not. The unlock procedure went through though. So I tried changing the link provided in the first email http://cdn.zui.lenovomm.com/developer/lenovoboot/xxxxxxxx/sn.img (xxxxxxxx - serial number of phone) and it worked. This might not work for you though.
As for the OTA, I really am not sure... Probably
carlshark said:
I tried unlocking 2 Lenovo phones. The first attempt had sent me an email, but the second attempt did not. The unlock procedure went through though. So I tried changing the link provided in the first email http://cdn.zui.lenovomm.com/developer/lenovoboot/xxxxxxxx/sn.img (xxxxxxxx - serial number of phone) and it worked. This might not work for you though.
As for the OTA, I really am not sure... Probably
Click to expand...
Click to collapse
after a few atempts (3-4 days) the imei number got accepted, but now i have another problem as you can see, i flashed the gapps and now i have the bootloop and i dont have a clue how to undone it
hello friends I have all the updates installed, but it tells me that there is a new one, where can I download it?
On the other hand, what difference is there between installing by twrp and qfill?
galardo_2 said:
i tired and failed again
Click to expand...
Click to collapse
This is problem with program, drivers sahara. Try fastboot
Help me guys so i have my phone rooted via patched boot.img provided by Magisk but then decided to grab my stock boot.img to patch it again so i can update to v22.0 then i restart my device to access for fastboot and everything went blackscreen(i can't even see anything literally) luckily for me i memorize the key command to access fastboot so i flashed my stock boot.img , recovery.img and vendor.img but now my phone won't start
This thing shows up
https://imgur.com/a/fVDp06e
yes it's provably stupid to flash stock boot.img , recovery.img and vendor.img but i panic everything went all black even the BLU logo is black (no backlight phone)
What phone do you have? I think one way to try is to flash the boot.img, then boot into recovery from adb and try instaling full android from there. I haven't tried this yet but in a few hours I just might
Oliie23 said:
What phone do you have? I think one way to try is to flash the boot.img, then boot into recovery from adb and try instaling full android from there. I haven't tried this yet but in a few hours I just might
Click to expand...
Click to collapse
well that escalated quickly i just want fully update Magisk now i need to install full stock rom
ineedroot69 said:
well that escalated quickly i just want fully update Magisk now i need to install full stock rom
Click to expand...
Click to collapse
If I'm thinking correctly you won't lose data. Just dirtyflash it and it should work fine
Update ::
I flashed my stock system.img via fastboot and it fuking fix the issue
and would you look at that good as new
i thought Magisk is systemless but somehow my system.img got corrupted
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
ineedroot69 said:
Update ::
I flashed my stock system.img via fastboot and it fuking fix the issue
and would you look at that good as new
i thought Magisk is systemless but somehow my system.img got corrupted
Click to expand...
Click to collapse
Great news. So how did you obtain the system.img? Did you flash just that and it booted? Do you have a custom recovery?
Oliie23 said:
Great news. So how did you obtain the system.img? Did you flash just that and it booted? Do you have a custom recovery?
Click to expand...
Click to collapse
no i don't have custom recovery like TWRP the development for my device is quite dead
also i use this thread https://forum.xda-developers.com/t/amazing-temp-root-for-mediatek-armv8-2020-08-24.3922213/ to dump all my device partition just in case something like this happen
ahh it fixed now my mother won't kill me
ineedroot69 said:
no i don't have custom recovery like TWRP the development for my device is quite dead
also i use this thread https://forum.xda-developers.com/t/amazing-temp-root-for-mediatek-armv8-2020-08-24.3922213/ to dump all my device partition just in case something like this happen
Click to expand...
Click to collapse
Did you lose data? And have you dumped the files before and that's how you've had the system.img?
Oliie23 said:
Did you lose data? And have you dumped the files before and that's how you've had the system.img?
Click to expand...
Click to collapse
look like completely factory default the bloatware are back
Just tried the update - completely messed up the phone - bootlooping, unable to flash a prev vers of magisk - doing a dirty flash....
Sebi673 said:
Just tried the update - completely messed up the phone - bootlooping, unable to flash a prev vers of magisk - doing a dirty flash....
Click to expand...
Click to collapse
ahaha this Magisk update v22.0 is bonker
Sebi673 said:
Just tried the update - completely messed up the phone - bootlooping, unable to flash a prev vers of magisk - doing a dirty flash....
Click to expand...
Click to collapse
Let me know how it goes, please
ineedroot69 said:
look like completely factory default the bloatware are back
Click to expand...
Click to collapse
Are your apps all gone? It's basically like clean flash, right?
Oliie23 said:
Let me know how it goes, please
Click to expand...
Click to collapse
dirty flash worked, reinstalled prev magisk v. magisk hide got stuck and did not complete with custom name, yet after a restart it asked to dl something something and worked - banking app does not see magisk. will stick to the prev magisk v
Sebi673 said:
dirty flash worked, reinstalled prev magisk v. magisk hide got stuck and did not complete with custom name, yet after a restart it asked to dl something something and worked - banking app does not see magisk. will stick to the prev magisk v
Click to expand...
Click to collapse
Wonderful news. So in your case it would stay in Fastboot and wouldn't launch? What did you do then?
Oliie23 said:
Wonderful news. So in your case it would stay in Fastboot and wouldn't launch? What did you do then?
Click to expand...
Click to collapse
tried flashing the new version via twrp but i was met by an error right after unpacking. At that point i couldn't save the logs sadly.
followed by device corruption warn on boot w/ the usual bootloop.
twrp, fastboot and flashmode were ok but simply flashing the boot img didn't work - had to do a full sys flash and then magisk.
[updatee] screens attached
Sebi673 said:
tried flashing the new version via twrp but i was met by an error right after unpacking. At that point i couldn't save the logs sadly.
followed by device corruption warn on boot w/ the usual bootloop.
twrp, fastboot and flashmode were ok but simply flashing the boot img didn't work - had to do a full sys flash and then magisk.
Click to expand...
Click to collapse
Mine won't go into TWRP from the Fastboot unfortunately. It just stays there. I've managed to get TWRP to launch from ADB but I'm not sure if I should just flash the ROM that way. Should I?
[duplicate]