Here is the STOCK ROM and STOCK RECOVERY for HTC DESIRE 820q Dual Sim
For those guys who have flashed custom recovery on their D820q dual sim and are searching for stock one, here I provide you the links for both the Stock Recovery and the Stock Rom.
Credits :
* EZN-74 for the Recovery he had provided me and I have flashed it on my D820q and it worked.
* fergy for providing the Stock Rom/Firmware. However I didn't test the Rom and I don't know if it will work with other than the Indian Variant of D820q Dual Sim. (BTW I don't know much about flashing this Rom)
Downloads :
* STOCK RECOVERY
(Before flashing, I suggest you to rename the recovery from recovery 820q.img to just recovery.img)
* STOCK ROM
* I think most of you know how to flash the recovery as you have already flashed the custom ones. And for the Noobs who don't know how to flash, can flash the recovery provided by me by using the commands as provided HERE
** Do at your own risk, I am not responsible if you brick your device or void your warranty **
HOW TO GET INTO STOCK RECOVERY
1. Flash the stock recovery
2. Turn on device and untick Fast boot from Settings >Power and then Power off
3. Hold Vol Down + Power to get into HBOOT menu
4. Scroll to Recovery option using volume keys and use power button to select
5. The device will display the Recovery icon with an Exclamation mark
6. Wait 10 seconds and Hold Vol Up and then press Power button
7. And Boom, you get into recovery.:good:
Don't forget to Hit that Thanks button
CURRENTLY I DON'T OWN THIS DEVICE, SO THIS THREAD IS PROBABLY CLOSED.
this post should not be in original android developement. This thread is for posting something that u developed urself. Kindly ask mods to move it so that people are not mislead. When i saw this post i thought it contains a custom recovery for 820q. :sad:
sziraqui said:
this post should not be in original android developement. This thread is for posting something that u developed urself. Kindly ask mods to move it so that people are not mislead. When i saw this post i thought it contains a custom recovery for 820q. :sad:
Click to expand...
Click to collapse
This thread contains original rom and recovery files, so I posted it here. Where do you think this thread should be ?
rizwan.mahai said:
This thread contains original rom and recovery files, so I posted it here. Where do you think this thread should be ?
Click to expand...
Click to collapse
u didnt get me my friend, 'Original Development' is for posting something which you BUILD. for example, custom recovery or a custom rom which u made urself. This thread should be in 'General'. However mods know it better, So Ask any moderator to move it to the right place. To do this click on the "triangle" in bottom left of YOUR post.
sziraqui said:
u didnt get me my friend, 'Original Development' is for posting something which you BUILD. for example, custom recovery or a custom rom which u made urself. This thread should be in 'General'. However mods know it better, So Ask any moderator to move it to the right place. To do this click on the "triangle" in bottom left of YOUR post.
Click to expand...
Click to collapse
Ok buddy, I will ask a moderator to do so.
rizwan.mahai said:
Here is the STOCK ROM and STOCK RECOVERY for HTC DESIRE 820q Dual Sim
For those guys who have flashed custom recovery on their D820q dual sim and are searching for stock one, here I provide you the links for both the Stock Recovery and the Stock Rom.
Credits :
* EZN-74 for the Recovery he had provided me and I have flashed it on my D820q and it worked.
* fergy for providing the Stock Rom/Firmware. However I didn't test the Rom and I don't know if it will work with other than the Indian Variant of D820q Dual Sim. (BTW I don't know much about flashing this Rom)
Downloads :
* STOCK RECOVERY
(Before flashing, I suggest you to rename the recovery from recovery 820q.img to just recovery.img)
* STOCK ROM
Click to expand...
Click to collapse
bro the stock rom you posted is not flashable by any recovery. It doesnt contain updater script at all. It contains boot.img, and some .hdr files. but not even system.img. Frankly speaking, i dont know how to flash this. If you know it please help me out
I think it should be flashed through Recovery Mode.
sziraqui said:
bro the stock rom you posted is not flashable by any recovery. It doesnt contain updater script at all. It contains boot.img, and some .hdr files. but not even system.img. Frankly speaking, i dont know how to flash this. If you know it please help me out
Click to expand...
Click to collapse
I didn't try flashing the rom on my device. However you can contact the developer @fergy who has provided the rom and ask him how to flash.
rizwan.mahai said:
I didn't try flashing the rom on my device. However you can contact the developer @fergy who has provided the rom and ask him how to flash.
Click to expand...
Click to collapse
did you have any working TWRP for D820H please ?
Does that device exists ?
the me said:
did you have any working TWRP for D820H please ?
Click to expand...
Click to collapse
Desire 820H ?? BTW I have the stock recovery for 820q.
D820h same of 820q
rizwan.mahai said:
Desire 820H ?? BTW I have the stock recovery for 820q.
Click to expand...
Click to collapse
thank you , im looking for custom recovery .
the me said:
thank you , im looking for custom recovery .
Click to expand...
Click to collapse
No custom recovery yet.
How To Flash RUU file
sziraqui said:
bro the stock rom you posted is not flashable by any recovery. It doesnt contain updater script at all. It contains boot.img, and some .hdr files. but not even system.img. Frankly speaking, i dont know how to flash this. If you know it please help me out
Click to expand...
Click to collapse
rizwan.mahai said:
I think it should be flashed through Recovery Mode.
Click to expand...
Click to collapse
How to Flash RUU(for HTC Desire 820q Dual SIM):
1- Download the *.zip(RUU) file from here:
ir-file.com/portal/index.php?dir=Firmware/HTC/HTC_Android/A50_DTUL
Note: The zip will not extract, you have to use it directly without extracting. So don't bother trying to extract the zip, it will always give you error.
2- Rename the file to "0PF6IMG.zip"
3- Put the file on SD card and insert it into mobile!
4- Reboot into bootloader and it will ask you if you want to update.
Note: Turn off your phone, press and hold POWER and VOL DOWN.
5- Press VOL UP to say yes.
6- Wait about 20-30 minutes!
7- Done! You've flashed RUU file successfully!
BTW I tested this RIGHT NOW on my phone and it works!
I used this: 0PF6IMG_A50_DTUL_K44_DESIRE_SENSE60_hTC_Asia_India_1.01.720.2_Radio_01.01.010_U1030433_08.01.1017_release_398545_combined_signed.zip
EZN-74 said:
I used this: 0PF6IMG_A50_DTUL_K44_DESIRE_SENSE60_hTC_Asia_India_1.01.720.2_Radio_01.01.010_U1030433_08.01.1017_release_398545_combined_signed.zip
Click to expand...
Click to collapse
yup it works, but will this work on a bricked Htc? One guy told me you can flash this after renaming it to firmware.zip using-
Code:
fastboot oem rebootRUU
fastboot flash zip firmware.zip
Can you try this and post back? I want to build a rom for this device but i dont have the official firmware which i can use to unbrick it (if it the phone bricks). Official Rom files like system.img, boot.img and recovery.img are not available for this device anywhere on internet, i have been searching since 2 months but i got only this 0PXXIMG which you and OP posted. (i got the same file on other websites after searching a LOT)
bro,
I have locked htc desire 820 dual sim with off debugging option. Its boatloader has been corrupted and it cant show boater options. Any help??
sziraqui said:
yup it works, but will this work on a bricked Htc? One guy told me you can flash this after renaming it to firmware.zip using-
Code:
fastboot oem rebootRUU
fastboot flash zip firmware.zip
Can you try this and post back? I want to build a rom for this device but i dont have the official firmware which i can use to unbrick it (if it the phone bricks). Official Rom files like system.img, boot.img and recovery.img are not available for this device anywhere on internet, i have been searching since 2 months but i got only this 0PXXIMG which you and OP posted. (i got the same file on other websites after searching a LOT)
Click to expand...
Click to collapse
yeah I also tried that but didn't work! (The problem is our "*.zip" RUU file is to large to be transferred through fastboot USB! the error was something like this: the file is to large!)
And also, if a device is bricked(hard bricked; not soft bricked), you cannot use fastboot commands! Because you can't access bootloader to use fastboot and "fastboot oem rebootRUU"!
EZN-74 said:
yeah I also tried that but didn't work! (The problem is our "*.zip" RUU file is to large to be transferred through fastboot USB! the error was something like this: the file is to large!)
And also, if a device is bricked(hard bricked; not soft bricked), you cannot use fastboot commands! Because you can't access bootloader to use fastboot and "fastboot oem rebootRUU"!
Click to expand...
Click to collapse
i mean, if bootloader is accessible, does this work on a device which has a custom rom installed (or in general, on a modified system).
sziraqui said:
i mean, if bootloader is accessible, does this work on a device which has a custom rom installed (or in general, on a modified system).
Click to expand...
Click to collapse
If you access bootloader, you can use both ways!(either you have stock or custom ROM) But I guess the "fastboot" method does not work with 1.0 GB files or larger!
EZN-74 said:
If you access bootloader, you can use both ways!(either you have stock or custom ROM) But I guess the "fastboot" method does not work with 1.0 GB files or larger!
Click to expand...
Click to collapse
thanks..
And you are right regarding file size limit, fastboot allows only files upto 256mb on moto e. I dont know if this is an issue with fastboot our with device under consideratron.
Thanks for testing
EZN-74 said:
How to Flash RUU(for HTC Desire 820q Dual SIM):
1- Download the *.zip(RUU) file from here:
ir-file.com/portal/index.php?dir=Firmware/HTC/HTC_Android/A50_DTUL
Note: The zip will not extract, you have to use it directly without extracting. So don't bother trying to extract the zip, it will always give you error.
2- Rename the file to "0PF6IMG.zip"
3- Put the file on SD card and insert it into mobile!
4- Reboot into bootloader and it will ask you if you want to update.
Note: Turn off your phone, press and hold POWER and VOL DOWN.
5- Press VOL UP to say yes.
6- Wait about 20-30 minutes!
7- Done! You've flashed RUU file successfully!
BTW I tested this RIGHT NOW on my phone and it works!
I used this: 0PF6IMG_A50_DTUL_K44_DESIRE_SENSE60_hTC_Asia_India_1.01.720.2_Radio_01.01.010_U1030433_08.01.1017_release_398545_combined_signed.zip
Click to expand...
Click to collapse
Well, it is good to now that someone finally tested this rom and it worked.
Related
Guys don't use this guide for now, don't use official unlocking method for now..
TO flash the CM12.1 in your Zf2 you must unlock the bootloader [WARNING: it will void the warranty]
I'm not responsible for bricked phone,try on your own risk
and official ASUS warning for unlocking bootloader ,its long so read it by clicking show content
Before you download, install, and use the Unlock Device App you acknowledge and assume complete risk to the quality and performance of this App, including but not limited to the following: once you activate the App you will not be able to recover your ASUS product (“Original Product”) back to original locked conditions; the Original Product with the activated App will not be deemed the Original Product; the Revised Product will no longer be covered under the warranty of the Original Product; the software of Revised Product will no longer be deemed the software of the Original Product and can no longer receive ASUS software updates; your purchased digital content may also be affected.
You also acknowledge ASUS does not guarantee service satisfaction to any Revised Product, including events involving paid service requested by you to be performed to the Revised Product.
Furthermore, such repaired Revised Product will not be covered under the warranty of the Original Product; the software of the repaired Revised Product will not be deemed the software of the Original Product and will not receive ASUS software updates.
It is strongly advised that you avoid activating this App unless you fully understand and accept the risks that may arise.
What this guide giving steps for:[just more like summary]
Files Needed and Required before Steps: - Just basic drivers to activate adb,fastboot system wide
Steps For Flashing CM12.1 : - unlocking bootloader, flashing twrp recovery and then flashing CM12.1,gapps and supersu.zip
Files Needed and Required before Steps:
Drivers for Asus Zenfone 2 installed on PC from here [mostly it will auto installed]
ADB installed on your PC (https://drive.google.com/file/d/0B0MKgCbUM0itVVFWRC02Q0VBQnc/view?pli=1),download and install this
And some more,which will be mentioned below
Steps For Flashing CM12.1 :
unlock bootloader instructions:
Update your software image to V2.20.40.59 or latest version
download app for ZE551ML[all 2gb,4gb] here and for ZE550Ml here
install, and use the Unlock Device App downloaded from above step
Download untethered twrp from here (zooa is for all ze551ml,z008 is for ze550ml),
if the .img you just downloaded doesnt have name as twrp.img [it may have version along it] then please rename that to twrp.img[remove those versions] and turn off ur phone, plug the usb cable in ur phone port,hold the VOL UP[no need to press the power] and connect the other end of cable to PC port,wait for few seconds till the green Android robot appears. You should see a blue line below saying "Waiting Fastboot command or Continue the fastboot process"
select the folder where you are having the twrp.img by pressing Shift + Right Click.. Then select "Open command here"...[in case you are wondering where and how see pics here or here]
Copy and paste the following command in the command prompt window
Code:
fastboot flash recovery twrp.img
after it finish the flashing[it will take less than 10sec only],u can unplug the phone, boot the phone.
download CM12.1 latest version or nightly from here [NOTE:see the date of the build to know the latest version]
get the gapps from here
get the supersu.zip from here
after downloading all zips,..place all in your micro SDCARD
now power off, Once it is off, hold down the volume up button and hold on to the power button until the phone vibrates. After the vibration stops, release the power button and continue pressing the volume up button until the green Android robot appears. You should see a blue line below saying "Waiting Fastboot command" ,Now here click vol down till you see Recovery mode in top big rectangle box,click power button
it will enter twrp,first take the backup of ur current OS[tick everything], choose sdcard for backup,so u can restore if u want to use stock at some point[even the apps will be there,but if you kept the obb,data in internal,it will be wiped,so better copy android folder to pc]
now click wipe,click advanced wipe,select everything except the microsd [be careful],if u want to keep the internal files,then untick internal storage also
Click the install,choose externalSD, search for those zip,and install CM.zip ,then install Gapps.zip,then supersu.zip,now reboot..
Enjoy the CM12.1 in ZF2
For bugs ,discussion please goto Main Thread: here
BUGS: here
Credits : there are lot of ppl who contributed to have CM12.1 in zf2 than those who i mentioned below,thanks for them also..
@sorg for new unlocked bootloader without root
@shakalaca for old unlocked bootloader with root
@ravian29 for unlocking guide
@TheSSJ for TWRP ,thread is here
@jrior001 , @crpalmer , @hharte for CM12.1
This ROM is only for the Z00A?
Sent from my ASUS_Z008D using Tapatalk
Added to index, thanks for your work!
GreatItami said:
This ROM is only for the Z00A?
Sent from my ASUS_Z008D using Tapatalk
Click to expand...
Click to collapse
551ml (z00A and z00ad)
For now not supported for 550ml..
Okay. Nice tutorial.
Sent from my ASUS_Z008D using Tapatalk
OK, so far I'm unlocked. But, I'm stuck on step 3 - select the folder where you are having the twrp.img by pressing Shift + Right Click.. Then select "Open command here"
EDIT:Got it! I had to open the actual folder first with TWRP in it (adb is where I put it) in my C drive then the right click + shift works as you said within the folder - thanks so much for this tutorial!
Is it neccessary to be on 2.19.40.22? There wasn't much of a difference between 2.19.40.20 and 2.19.40.22. Would I have to flash the OTA then flash CM? Also, do you recommend wiping cache/dalvik after flashing GAPPS just in case?
PS: Thank you Ansebovi! All your guides are easy to read and follow.
texla said:
OK, so far I'm unlocked. But, I'm stuck on step 3 - select the folder where you are having the twrp.img by pressing Shift + Right Click.. Then select "Open command here"
EDIT:Got it! I had to open the actual folder first with TWRP in it (adb is where I put it) in my C drive then the right click + shift works as you said within the folder - thanks so much for this tutorial!
Click to expand...
Click to collapse
I did it by downloading Terminal for Android and putting the image on the internal storage and then opening Terminal and did this
su
dd if=/sdcard/twrp.img of=/dev/block/by-name/recovery
reboot recovery
CM12 zip is downloading really slow...i know its only 350mb but is going at barely 45kb/s ..is this normal? i know its not my connection -.-
texla said:
OK, so far I'm unlocked. But, I'm stuck on step 3 - select the folder where you are having the twrp.img by pressing Shift + Right Click.. Then select "Open command here"
EDIT:Got it! I had to open the actual folder first with TWRP in it (adb is where I put it) in my C drive then the right click + shift works as you said within the folder - thanks so much for this tutorial!
Click to expand...
Click to collapse
http://forum.xda-developers.com/attachment.php?attachmentid=3419717&stc=1&d=1437962670
http://forum.xda-developers.com/attachment.php?attachmentid=3419716&stc=1&d=1437962670
both works
Ntrasme said:
Is it neccessary to be on 2.19.40.22? There wasn't much of a difference between 2.19.40.20 and 2.19.40.22. Would I have to flash the OTA then flash CM? Also, do you recommend wiping cache/dalvik after flashing GAPPS just in case?
PS: Thank you Ansebovi! All your guides are easy to read and follow.
Click to expand...
Click to collapse
i updated from .20 and i had the mtp bug which others didnt have,..so i think its better to have .22 , try with .20 and look for bugs..only problem,u cant report the bug to them,since they are seeing with .22
cjvzla said:
CM12 zip is downloading really slow...i know its only 350mb but is going at barely 45kb/s ..is this normal? i know its not my connection -.-
Click to expand...
Click to collapse
no i downloaded the zip with 700KBps-1MBps ,definitely no problem from their side
ansebovi said:
http://forum.xda-developers.com/attachment.php?attachmentid=3419717&stc=1&d=1437962670
http://forum.xda-developers.com/attachment.php?attachmentid=3419716&stc=1&d=1437962670
both works
i updated from .20 and i had the mtp bug which others didnt have,..so i think its better to have .22 , try with .20 and look for bugs..only problem,u cant report the bug to them,since they are seeing with .22
no i downloaded the zip with 700KBps-1MBps ,definitely no problem from their side
Click to expand...
Click to collapse
OK, thank you. BTW do you know if TWRP can sideload the ota zips? Is there a conflict if I use ProjectT kernel while sideloading OTA? You are more knowledged than me.
ansebovi said:
TO flash the CM12.1 in your Zf2.....
Click to expand...
Click to collapse
...wow this a great rom
excuse me for asking but is this already running in 64bit mode?
or it is still 32bit?
Thanks. Worked flawlessly.
berlyshells said:
...wow this a great rom
excuse me for asking but is this already running in 64bit mode?
or it is still 32bit?
Click to expand...
Click to collapse
they used asus stock .22 latest update as base,so it should be x86 till the asus release x64bit and Cm updated to that firmware ...
Ntrasme said:
OK, thank you. BTW do you know if TWRP can sideload the ota zips? Is there a conflict if I use ProjectT kernel while sideloading OTA? You are more knowledged than me.
Click to expand...
Click to collapse
ota have patch for boot and recovery,..not a gud idea to flash ota with twrp,custom kernel...it may end up in failure
hi, finished downloading needed files, unlocked bootloader succesfully (white splash screen) , rooted, and installed unthetered twrp just like in the steps, however, when i tried to enter recovery for the first time just showed android on the floor with ERROR and red triangle logo...nothing happens so just rebooted and wating for a tip...thanks.
EDIT: sorry i did not read the same problem being resolved on page 1... got twrp running now.
Bro is there any bugs ? Please post bug list
himesh1994 said:
Bro is there any bugs ? Please post bug list
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=62014498&postcount=2
btw dont quote the whole op anywhere in xda please..edit ur post and delete the quote
Ntrasme said:
Is it neccessary to be on 2.19.40.22? There wasn't much of a difference between 2.19.40.20 and 2.19.40.22. Would I have to flash the OTA then flash CM? Also, do you recommend wiping cache/dalvik after flashing GAPPS just in case?
PS: Thank you Ansebovi! All your guides are easy to read and follow.
Click to expand...
Click to collapse
sry i forgot to answer the other qn before...no need to wipe cache after installing gapps as we wiping before the installation of both
and thanks for compliment
ansebovi said:
http://forum.xda-developers.com/showpost.php?p=62014498&postcount=2
btw dont quote the whole op anywhere in xda please..edit ur post and delete the quote
sry i forgot to answer the other qn before...no need to wipe cache after installing gapps as we wiping before the installation of both
and thanks for compliment
Click to expand...
Click to collapse
OK, thanks. Now to go on the long process of resetting everything so I can apply OTA. Restore stock recovery, restore stock kernel, unfreeze apps, uninstall framework, uninstall busybox, unroot.
Ntrasme said:
OK, thanks. Now to go on the long process of resetting everything so I can apply OTA. Restore stock recovery, restore stock kernel, unfreeze apps, uninstall framework, uninstall busybox, unroot.
Click to expand...
Click to collapse
haha ,thats really headache ... btw use manual ota for safety
For 500CL ?
I can't wait for this rom for the 500cl Zenfone 2. The original rom is awful, with the huge amount of bloatware any so many bugs ! Any chance to have this rom for the zenfone 2 500cl ?
Hi all,
I want to share with you the result of my work.
I'm not a dev and my English is not very good, I'm just a user who found a way to root his device
For that I will not make an other tuto, just release my file and make a quick explanation.
YOU MUST UNLOCK YOUR BOOTLOADER BEFORE CONTINUE.
Files are for F3112 (dual sim) ONLY. F3111 use a different kernel.
TWRP is fully working but if internal memory is encrypted by default you can't backup userdata and mount internal memory.
You must know and understand what you are doing.
If you have a problem after flashing files I will help you but I repeat, I'm not a dev.
You can reflash firmware to stock with Flashtool v0.9.22.3
You have to do all steps again after an update
Free to you to distribute, modify files or make a nice tuto but please link this thread as source.
FOLLOWING GUIDE AND FILES ARE OUTDATED, PLEASE FOLLOW THIS ONE:
http://forum.xda-developers.com/xperia-xa/how-to/f31xx-how-to-root-xperia-xa-noob-t3430170
1) Download this zip:
33.2.B.2.35: https://mega.nz/#!NgISUKrR!JFss5mQLOg1VTa5AKDZuYx0zVvnkSKmNrYCWnmEMa2w (Deleted)
33.2.B.2.73: https://mega.nz/#!4txXxSzS!CQjuqhU347SE6arwEjX5KTFXM_DtR8Z85R_qCedy6AY (Deleted)
2) Unzip it and copy "UPDATE-SuperSU-v2.76-20160630161323.zip" on your MircoSD
3) Enter the phone in Fastboot mode (when power off, hold Vol+ and plug the phone). Led is blue.
4) Flash recovery and boot with "fastboot flash boot boot.img" and "fastboot flash recovery recovery.img" commands. Simple way is to use fastboot from Flashtool in x10flasher folder, copy recovery and boot in it, open command prompt, flash and delete them after.
5) Unplug the phone, hold "Vol-" and "Power" buttons. Release all buttons after phone vibrate.
6) You are in TWRP 3.0.2 recovery, on password prompt press "Cancel"
7) On next screen press "Keep Read Only". NEVER SWIPE TO ALLOW !!
8) Go to "Install", "Select Storage", click "Micro SDCard"
9) Go to your zip directory and click on it to install.
10) Reboot the phone, during init the phone will reboot one more time.
11) Your phone is rooted
If you want to unroot, you flashed on wrong model or stuck in bootloop, reflash stock boot and FOTAKernel (unchek all others) with Flashtool/Xperifirm.
Have a nice day
Please tell me
How to Unlocked BL Sony Xperia xa Dual
thank
rrvuhpg said:
Hi all,
I want to share with you the result of my work.
I'm not a dev and my English is not very good, I'm just a user who found a way to root his device
For that I will not make an other tuto, just release my file and make a quick explanation.
YOU MUST UNLOCK YOUR BOOTLOADER BEFORE CONTINUE.
Files are for F3112 (dual sim) ONLY. F3111 use a different kernel.
Don't use TWRP for backups, I have ported it from Elephone M3 device and is not fully fuctionnal.
You must know and understand what you are doing.
If you have a problem after flashing files I will help you but I repeat, I'm not a dev.
You can reflash firmware to stock with Flashtool v0.9.22.3
Free to you to distribute, modify files or make a nice tuto but please link this thread as source.
1) Download this zip:
https://mega.nz/#!NgISUKrR!JFss5mQLOg1VTa5AKDZuYx0zVvnkSKmNrYCWnmEMa2w
2) Unzip it and copy "UPDATE-SuperSU-v2.76-20160630161323.zip" on your MircoSD
3) Enter the phone in Fastboot mode (when power off, hold Vol+ and plug the phone). Led is blue.
4) Flash recovery and boot with "fastboot flash boot boot.img" and "fastboot flash recovery recovery.img" commands.
5) Unplug the phone, hold "Vol-" and "Power" buttons. Release all buttons after phone vibrate.
6) You are in TWRP 3.0.2 recovery, on password prompt press "Cancel"
7) On next screen press "Keep Read Only". NEVER SWIPE TO ALLOW !!
8) Go to "Install", "Select Storage", click "Micro SDCard"
9) Go to your zip directory and click on it to install.
10) Reboot the phone, during init the phone will reboot one more time.
11) Your phone is rooted
I will try to update root and recovery for 33.2.B.2.73. I tried to compile kernel with Opensource archive from Sony but have errors and can't finish the job. Anyway, the doors are now open for Devs.
Have a nice day
Click to expand...
Click to collapse
New it was to good to be true oh well. Nice work but I'll be getting a lte model hopefully later on today so no use to me and coding is way out of my league. Surprised the kennels are different, on M2 5.1 across all models lte or dual, kernel is the same and firmware version. Oh well back to the drawing board. Beginning to think may be I should pay the extra after all and get the Qualcomm powered x
emmiiz said:
Please tell me
How to Unlocked BL Sony Xperia xa Dual
thank
Click to expand...
Click to collapse
https://www.youtube.com/watch?v=nSNDSyeys2g&authuser=0 Watch the video.
thank. @hp6830s
@aidy.lucas, but my device is F3116
after i Flash boot and recovery, my device boot loop to TWRP. T_T
@aidy.lucas, for me kernels are different because I have to choose between single or dual defconfig before compiling kernel. I will look closer at defconfigs to see what is different. Or if anyone can test on F3111 and feedback
rrvuhpg said:
@aidy.lucas, for me kernels are different because I have to choose between single or dual defconfig before compiling kernel. I will look closer at defconfigs to see what is different. Or if anyone can test on F3111 and feedback
Click to expand...
Click to collapse
Picked it up this morning f3111 wow it's stunning
Sent from my Xperia XA using XDA Labs
aidy.lucas said:
Picked it up this morning f3111 wow it's stunning
Sent from my Xperia XA using XDA Labs
Click to expand...
Click to collapse
gz...so will u try the root method ,described above. This phone must be rooted in order to fix % of battery. 56% used in the last 11 hours / 4g turned off,20-30% screen....
rrvuhpg, Thank you. I got root successfully. :good:
@emmiiz, I think your bootloop is because the firmware is different (probably just a little). If you compare you will see F3111, F3112, F3113 are LTE and F3115, F3116 are TD-LTE. Maybe I'm wrong but it can do the difference (already seen on other devices). Link to compare: http://www.plusmobile.fr/comparer/m...al-f3112-vs-sony-xperia-xa-dual-f3116/3504635
An other thing, CDA numbers (customisation) are different between all 5 devices for the same firmware and same name of customisation, I think it's not for fun lol.
And are you sure your bootloader is unlocked ? To be sure, reflash only original boot and recovery (fotakernel) with Flashtool, boot to Android and on the phone dialer enter *#*#7378423#*#* It will open hidden service menu. Now go to "service info" and "configuration". Have you "Bootloader unlocked: Yes" ?
@Horofox, I'm really happy for you it worked ? Your device is the F3112 ?
@rrvuhpg, thank.
My device "Bootloader unlocked: Yes"
I think boot.img it's not yet to work for F3116 T_T
sorry if this is a stupid question , i have 3113 , boot loader unlocked etc international version. is this safe to try?
ayuready1989 said:
sorry if this is a stupid question , i have 3113 , boot loader unlocked etc international version. is this safe to try?
Click to expand...
Click to collapse
I think each different models gonna need it's own kernel+recovery I'm running a f3111
Sent from my Xperia XA using XDA Labs
aidy.lucas said:
I think each different models gonna need it's own kernel+recovery I'm running a f3111
Sent from my Xperia XA using XDA Labs
Click to expand...
Click to collapse
welp, everything went well besides cell radio lol, sim card missing etc . i guess I'm going to try n refresh my original boot.img and see if i can get my radio back =
ayuready1989 said:
welp, everything went well besides cell radio lol, sim card missing etc . i guess I'm going to try n refresh my original boot.img and see if i can get my radio back =
Click to expand...
Click to collapse
Should be fine just re-flashing the stock kernel and at most wipe cache
Sent from my Xperia XA using XDA Labs
aidy.lucas said:
Should be fine just re-flashing the stock kernel and at most wipe cache
Sent from my Xperia XA using XDA Labs
Click to expand...
Click to collapse
you know how i could get the kernel to reflash .. downloaded the firmware using xperifirm . from what in understand i need to remake a boot.img .. which files do i use from the firmware etc?
ayuready1989 said:
you know how i could get the kernel to reflash .. downloaded the firmware using xperifirm . from what in understand i need to remake a boot.img .. which files do i use from the firmware etc?
Click to expand...
Click to collapse
Pretty sure you just need to flash stock kernel via flashtool unticking everything else. Personally I'd probably flash the whole thing myself to avoid any other problems especially if it's new.
Sent from my Xperia XA using XDA Labs
aidy.lucas said:
Pretty sure you just need to flash stock kernel via flashtool unticking everything else. Personally I'd probably flash the whole thing myself to avoid any other problems especially if it's new.
Sent from my Xperia XA using XDA Labs
Click to expand...
Click to collapse
won't be that easy unfortunately . will need the boot image for 3113 to be present when booted into recovery to run the updatesu script . just reflashed kernel .. su app is there but no root
---------- Post added at 08:12 PM ---------- Previous post was at 07:54 PM ----------
ayuready1989 said:
won't be that easy unfortunately . will need the boot image for 3113 to be present when booted into recovery to run the updatesu script . just reflashed kernel .. su app is there but no root
Click to expand...
Click to collapse
would you be able to share the commands used to mkbootimg?
Root for 33.2.B.2.73 released ! First post updated.
@ayuready1989 I don't use this tool, I use Carliv Image Kitchen. But you can take these settings to suit mkbootimg:
Page size : 2048 (0x00000800)
Base address : 0x40078000
Kernel address : 0x40080000
Kernel offset : 0x00008000
Ramdisk address : 0x45000000
Ramdisk offset : 0x04f88000
Second address : 0x40f78000
Tags address : 0x44000000
Tags offset : 0x03f88000
Cmdline : 'bootopt=64S3,32N2,64N2'
****** I DO NOT TAKE ANY RESPONSIBILITY FOR ANY BRICKS/BOOT LOOPS/Mi LOGO BRICK. I AM SHARING THE STEPS THAT I HAVE USED AND YOU USE THESE STEPS AT YOUR OWN RISK ******
Use Android Image Kitchen to decompress and Recompress.
Unzip the whole Kitchen and ROM files through 7 Zip * mode.
Copy the "boot.img" to the Android Kitchen Unzipped Folder.
Follow the following steps:
Step 1. Decompress the boot.img file through Android Image Kitchen (unpackimg.bat)
Step 2. Open the file "fstab.qcom" via notepad / notepad++.
Step 3. Remove the ".verify" from it and save the file. Do not change the file extension. (Though it should not ask/or do). (This unlocks bootloader over server).
Step 4. Open default.prop via notepad / notepad++.
Step 5. Change "ro.secureboot.devicelock=1" to "ro.secureboot.devicelock=0" (This unlocks the bootloader).
- Additional Amendments if you want, like enabling adb, debug, etc, then do Step 6, else go to Step 7. STep 6 somehow seems to have some error on WiFi access. In case you do not want that, do not perform Step 6. a. and 6.b.,.
Step 6. Change:
a. "ro.secure=1" to "ro.secure=0"
b. "ro.adb.secure=1" to "ro.adb.secure=0"
These enable OEM Unlock over Server and over Developer mode.
c. "ro.debuggable=0" to "ro.debuggable=1".
This turns on USB Debug.
d. "persist.sys.usb.config=none" to "persist.sys.usb.config=adb"
This turns on ADB mode.
e. "persist.sys.timezone=Asia/Shanghai" to "persist.sys.timezone=Asia/XXX".
One can set the default locale from here. (This does not seem to work on Beta ROM's, as the server denies setting locale). (Though it should not ask/or do).
- Save the file. Do not change the file extension.
Step 7. Recompress these files back through repackimg.bat."
A new file "image-new.img" will be created. Rename the file to "boot.img" and replace the same to the unzipped folder of the ROM.
You now have a cooked/modded boot.img within the ROM, and your device is bootloader unlocked. Now Flash the ROM through MIFlash.
Also note: Rename the TWRP/Custom Recovery image to "recovery.img" and replace it with the Stock Recovery within the ROM. Now you have Custom Recovery ROM.
These steps take no more then 5-6 minutes, and are pretty easy.
Happy Flashing.
N.B.: I have attached the Android Kitchen File here.
Is this equivalent to unofficial unlock or the official one?
BlueJeans said:
Is this equivalent to unofficial unlock or the official one?
Click to expand...
Click to collapse
Actually None. I mean not the official, nor the unofficial one.
I am on unlocked bootloader myself.
These are the steps I did to unlock my bootloader.
I have even rooted my RN3QC within 10 days from purchase.
I just wanted to unlock and have even custom TWRP 3.0.2-2.
can miflash just flash the boot.img?
meangreenie said:
can miflash just flash the boot.img?
Click to expand...
Click to collapse
Nope, I tried, and it went to bootloop once and second time to mi logo.
The easiest way to install the boot.img and the recovery.img are:
If you want TWRP to be your recovery and that too after flashing the ROM, I will ask you to replace the default recovery file within the unzipped ROM with the TWRP Recovery File. The default recovery path is within the images folder and called recovery.img.
Just rename the TWRP Recovery image file to recovery.img and replace it in images folder, and flash through MIFlash. Done.
And if you want to flash boot.img, then flash through TWRP. That is the easiest method.
Safe and no bricks.
N.B.: FYI: Few Stable ROM's have a verity check on even after official unlock. That just means that the server has not yet updated their unlock, and if it is not done manually, then it will remain locked on server.
Nice tutorial , this will be helpful to those people who are still stuck on 50% error ,Good work !
NVDX11 said:
Nice tutorial , this will be helpful to those people who are still stuck on 50% error ,Good work !
Click to expand...
Click to collapse
Hope that moderator is not here too.
vdbhb59 said:
Hope that moderator is not here too.
Click to expand...
Click to collapse
Haha , yep :laugh:
So this should work on redmi 3s too ? gonna give it a try now. thanks dude.
Btw are you the guy who got banned on miui forum ? i had bookmarked a post similar to this but when i actually got time to read it, it was deleted by mod.
Edit : does not work lol, was stuck on Qualcomm HS-USB Diagnostics 900E mode, and couldn't get it to fasboot/edl mode. tried many different key combinations and and now finally got it fixed. so i guess it works only on RN3. now gotta wait for them to fix their db.
kraatus90 said:
So this should work on redmi 3s too ? gonna give it a try now. thanks dude.
Btw are you the guy who got banned on miui forum ? i had bookmarked a post similar to this but when i actually got time to read it, it was deleted by mod.
Edit : does not work lol, was stuck on Qualcomm HS-USB Diagnostics 900E mode, and couldn't get it to fasboot/edl mode. tried many different key combinations and and now finally got it fixed. so i guess it works only on RN3. now gotta wait for them to fix their db.
Click to expand...
Click to collapse
R3S it should not work, and as you confirmed it does not work.
Yes I am thr guy whose post got deleted, and the Mod is still adamant on saying it does not unlock bootloader.
They have changed the method to unlock on MM, so this apparently is only for LP.
vdbhb59 said:
Step 6. Change:
a. "ro.secure=1" to "ro.secure=0"
b. "ro.adb.secure=1" to "ro.secure=0"
These enable OEM Unlock over Server and over Developer mode.
Click to expand...
Click to collapse
Noob question, due to I need to ensure something.
Point 6.b.
It is correct, change "ro.adb.secure=1" to "ro.secure=0"
Since this is different command.
Anyway, thanks for your share.
abihary said:
Noob question, due to I need to ensure something.
Point 6.b.
It is correct, change "ro.adb.secure=1" to "ro.secure=0"
Since this is different command.
Anyway, thanks for your share.
Click to expand...
Click to collapse
Thanks for pointing this out bro. My typing error.
It is ro.adb.secure
vdbhb59 said:
Thanks for pointing this out bro. My typing error.
It is ro.adb.secure
Click to expand...
Click to collapse
You're welcome. I need to share this simple way to my friend, thats why i read it carefully to avoid any problem. For myself, already unlocked few weeks ago.
Anyway, thanks for your feedback.
abihary said:
You're welcome. I need to share this simple way to my friend, thats why i read it carefully to avoid any problem. For myself, already unlocked few weeks ago.
Anyway, thanks for your feedback.
Click to expand...
Click to collapse
Any day welcome.
For kenzo or hennessy?
zenex01 said:
For kenzo or hennessy?
Click to expand...
Click to collapse
For kenzo
zenex01 said:
For kenzo or hennessy?
Click to expand...
Click to collapse
Kenzo and unfortunately currently limited to LP.
Searching for MM and N pattern to unlock.
What MIUI version you using? @vdbhb59
I tried with 7.3.2.0 after flashing then check bootloader but still locked. I skip step 6.
MiripRedmoon said:
What MIUI version you using? @vdbhb59
I tried with 7.3.2.0 after flashing then check bootloader but still locked. I skip step 6.
Click to expand...
Click to collapse
I am on 6.9.9 Global Beta. I had unlocked when I was on 6.8.18 Global Beta.
You need to check the steps properly, or if you want, attach your boot.img filehere, and I will change and reattach it here for you.
vdbhb59 said:
I am on 6.9.9 Global Beta. I had unlocked when I was on 6.8.18 Global Beta.
You need to check the steps properly, or if you want, attach your boot.img filehere, and I will change and reattach it here for you.
Click to expand...
Click to collapse
So you are back to a locked bootloader when you moved to 6.9.9?
And for doing that you just flashed the fastboot tgz file in edl mode?
Btw, overall comment -> u mean to say .. using this process there is no need to replace/ flash the modded emmc_appsboot.mbn file?
Okay guys first let me tell you why I have created a new thread just for updating the BL and Firmware ,
I know we already have methods of updating like:
1. flashing the full OOS3 zip through stock recovery ,this method is quite simple for the ones who are on stock recovery and just want to update their OOS version.If you fall in this category then you have no purpose here,you may leave.
2. Is method provided by our fav helping hand @Joshwin Aranha ,that method is sure for the rest of us who dont fall in the above category,but is way too long,although simple and effective still "long".
I created this thread to help the CM13(Official or Sultan's)//any custom rom using new BL,users who want to update their BL without flashing the OOS through the tedious way just to update BL and users who are stuck on bootlogo due to old BL with roms using new BL.
Here I will guide you through the required steps to update our bootloader "In easiest and fastest way without wiping and restoring anything".
So what are we waiting for ,lets start .
Prerequisites
you will need two files for this process,nothing else.
1 . First one is BLUpdater zip --->Here.
2. Second is TWRP compiled from latest sources use either This or the one from Here<--use v41 or use Sultan's from Here OR if you are Martin's fan like me and want to use his MutiRom TWRP goHere.
PS:I am assuming you have Unlocked Bootloader and have either
official/blu_spark/sultan's/ Multirom TWRP installed,in a working condition on OOS2.x BL(if not what are you doing here).
Note: make sure oem unlocking is checked in developer options in your current rom,else updating the BL may cause it to get locked ,and you will have to unlock it again and flash the recovery manually through fastboot itself.
Now the steps
1.First copy both of the above files in your sdcard or otg or ext-sdcard,any place accessible in recovery.
2. Now boot into recovery Choose Install and choose the "OPXBLUpdateOOS3.1" zip and flash it.
3. Don't reboot now ,go to Install again ,this time use "Install Image" button in lower right corner,navigate to folder where you copied the new TWRP,you should be able to see the file,select it ,choose recovery in the next menu and flash.
NOTE:If you chose to use Sultan's recovery.zip then just flash it normally.
4. Don't reboot come back to TWRP home ,goto reboot and recovery ,if TWRP says no OS installed ignore it.
Now voila you should have updated your firmware/BL.Congrats.
You can now install any rom that supports the new BL.Older roms won't boot on the new MM BL.So check the rom thread before installing the rom and later on quacking here about your device being stuck at bootlogo.
Notes
i)Neither I nor XDA will be responsible if your OPX bricks or explodes or ditches you and flies to space.
ii)We are not touching system partition so last installed ROM will be intact.
iii)This guide will leave you into bootable rom only if you have a rom installed that works on latest firmware.
iv)This can also be used to restore all your OPX partitions back to OOS3.x partition state,if you messed any.
v)In case you are using latest nightly (cm13) and face bootloop - go Here
psst:If you are not diggin the new BL,and wanna downgrade again ,back to old BL,check this post.
PS: (second one,I know) This guide was made by taking inspiration from Joshwin's post and devtry method.
Also click Thanks if I helped you
matwaking said:
Okay guys first let me tell you why I have created a new thread just for updating the BL and Firmware ,
I know we already have methods of updating like:
1. flashing the full OOS3 zip through stock recovery ,this method is quite simple for the ons who are on stock recovery and just want to their OOS version.If you fall in this category then you have no purpose here,you may leave.
2. Is method provided by our fav helping hand @Joshwin Aranha ,that method is sure for the rest of us who dont fall in the above category,but is way too long,although simple and effective still "long".
So I created this thread just to shorten the process provided by Joshwin.I also created this thread to help the official CM13 users who have problem with latest nightlies due to new bootloader or are stuck in bootlogo.
...
PS: (second one,I know) This guide was made by taking inspiration from Joshwin's post and devtry method.
Also click Thanks if I helped you
Click to expand...
Click to collapse
Booomshkalaka!!!
Great guide, can't test (already have new bootloader and too lazy to switch back but look very good.
Thx to all
Kurt
Kurt Krummbein said:
Booomshkalaka!!!
Click to expand...
Click to collapse
Lol .
Thanks mate.
Will this work if I'm in bluspark twrp but the previous version..? Or do I have to change to official twrp?
jonrodz said:
Will this work if I'm in bluspark twrp but the previous version..? Or do I have to change to official twrp?
Click to expand...
Click to collapse
Will work with any twrp,no requirement of official one.
Thanks, bro. One more doubt. I'm currently on DU rom with custom kernel... Do you think rom will boot after this..?
jonrodz said:
Thanks, bro. One more doubt. I'm currently on DU rom with custom kernel... Do you think rom will boot after this..?
Click to expand...
Click to collapse
No it wont,right now almost all the custom roms need to update to support new firmware.Only latest cm13 nightlies are booting now,also aosp compiled by olddroid for new BL(shh its only for testers right now)
also maybe the MIUI8 port ,just posted in the forums.
I'm a litte bit confused.
Currently I'm on nighty October 1st. (cm-13.0-20161001-NIGHTLY-onyx.zip)
Can i update the Bootloader with your method and after that booting up my current nightly version?
Or do I have to update after the bootloader update to nightly version 12 (the currently latest)?
jerikooo said:
I'm a litte bit confused.
Currently I'm on nighty October 1st. (cm-13.0-20161001-NIGHTLY-onyx.zip)
Can i update the Bootloader with your method and after that booting up my current nightly version?
Or do I have to update after the bootloader update to nightly version 12 (the currently latest)?
Click to expand...
Click to collapse
no update the BL using the steps above ,then flash the latest nightly.That way it would be good.
Or you can flash nightly first then update BL.Choice is yours.I recommend updating the BL first.
I followed your guide with a locked bootloader, and now I'm in bootloops . Just suggest you put a big red "make sure your bootloader is unlocked" in the steps, not in the footnote.
Duplicate post.Deleted
ccaappton said:
I followed your guide with a locked bootloader, and now I'm in bootloops . Just suggest you put a big red "make sure your bootloader is unlocked" in the steps, not in the footnote.
Click to expand...
Click to collapse
Reboot into fastboot mode and
Code:
fastboot oem unlock
And using a custom recovery and custom rom makes me assume one have unlocked bootloader
matwaking said:
Reboot into fastboot mode and
Code:
fastboot oem unlock
And using a custom recovery and custom rom makes me assume one have unlocked bootloader
Click to expand...
Click to collapse
Thanks! I actually relocked my bootloader not long after installed cm13, and disabled "unlock oem" in "developer settings"(I don't know why I did this). So both system and rec is inaccessible, and fastboot is useless in this case. Fortunately I followed the unbrick guide: http://forum.xda-developers.com/oneplus-x/general/guide-mega-unbrick-guide-hard-bricked-t3272108 and get the old bootloader back. Now I could enter CM13-09-28 with all my data intact.
Just hope to let people know the hard lesson I learned, and how to deal the bootloops.
And guys, NEVER RELOCK BOOTLOADER AGAIN!
ccaappton said:
Thanks! I actually relocked my bootloader not long after installed cm13, and disabled "unlock oem" in "developer settings"(I don't know why I did this). So both system and rec is inaccessible, and fastboot is useless in this case. Fortunately I followed the unbrick guide: http://forum.xda-developers.com/oneplus-x/general/guide-mega-unbrick-guide-hard-bricked-t3272108 and get the old bootloader back. Now I could enter CM13-09-28 with all my data intact.
Just hope to let people know the hard lesson I learned, and how to deal the bootloops.
And guys, NEVER RELOCK BOOTLOADER AGAIN!
Click to expand...
Click to collapse
Well no fix without any problems hehehe,.Haapy 4 u.
Click that button if you think my posts are useful
Is this enough to install CM14 or do i have to install the whole room and them flash CM14?
Manelit said:
Is this enough to install CM14 or do i have to install the whole room and them flash CM14?
Click to expand...
Click to collapse
taking you wanna flash ashwins cm14 right. You just wanna follow the instructions in first post and then flash the cm14.No need to install the whole Oos zip.
This way you should have updated BL and working cm14.
Just flash the cm14 after booting into new TWRP
I've just followed the procedure from OP and all went smooth as butter. Thanks
Directly after that (without reboot) I've installed the latest CM13 (with GApps) and Arsenic R24. Working as a charm
slaav said:
I've just followed the procedure from OP and all went smooth as butter. Thanks
Directly after that (without reboot) I've installed the latest CM13 (with GApps) and Arsenic R24. Working as a charm
Click to expand...
Click to collapse
Press that sweet sweet button mate
1.First copy both of the above files in your sdcard or otg or ext-sdcard,any place accessible in recovery.
2. Now boot into recovery Choose Install and choose the "OPXBLUpdateOOS3.1" zip and flash it.
3. Don't reboot now ,go to Install again ,this time use "Install Image" button in lower right corner,navigate to folder where you copied the new TWRP,you should be able to see the file,select it ,choose recovery in the next menu and flash.
4. Don't reboot come back to TWRP home ,goto reboot and recovery ,if TWRP says no OS installed ignore it.
Click to expand...
Click to collapse
Hi, everyone
I'm accidentally reboot device after second step. Now device freezing on "+1 powered by android". Can I remove this zip, or... what can I do next?)
walsash said:
Hi, everyone
I'm accidentally reboot device after second step. Now device freezing on "+1 powered by android". Can I remove this zip, or... what can I do next?)
Click to expand...
Click to collapse
u can flash bluespark twrp via fasboot
Sent from my ONE E1003 using XDA-Developers mobile app
Hi guys. M currently usimg Nephilim Rom V2. I was trying to flash b594 stock rom. Whenever i tried to install it with stock recovery it just says no update.app is found. Even though i extracted the update.zip file and put it in internal storage in dload folder. I cant even flash it through fastboot because it gives error even though i extracted the img files through Huawei extractor. Can anyone help!!!!
What kind of error fastboot method gives you? I always have went back to stock rom by flashing a rom in fastboot and never had problems with it
While flashing system.img i got error cant load system.img. even though it's in the same folder as adb is. There was also an error whule flashing recovery extracted from update.zip. i was flashing the recovery.img only and it says errot:too many links.
Try to re-download your adb and its related files
cheapster8 said:
Try to re-download your adb and its related files
Click to expand...
Click to collapse
Done that to same result...
So you want your original firmware correct ? If so , go here: http://consumer.huawei.com/nl-en/support/downloads/detail/index.htm?id=82749
Change region (if needed) find your phone and download that.
Once you downloaded it:
1. put it on your sd card
1.1 Since when you download the file, its gonna be in .zip or .rar format, you are gonna need to extract that and what you get out of that file (its gonna be a folder called dload) put that whole thing "dload" on to your sdcard. ( put in in a main folder of your sd card its called root folder, its where your main folders are like pictures, DCIM etc.)
2. turn off your phone leave it for a sec
3. then hold all 3 buttons ( power ,volume up , volume down) and it should start installing the thing.
Hope this helps.
Check this
https://forum.xda-developers.com/honor-4x/how-to/install-emui-4-1-4x-4c-g-play-g-play-t3515702
It's on honor 4x forum but it says it works on p8lite android 5.0 or higher.
Are you able to install stock recovery through adb? If you are, you can easily use Huawei's recovery to flash the stock firmware
cheapster8 said:
Are you able to install stock recovery through adb? If you are, you can easily use Huawei's recovery to flash the stock firmware
Click to expand...
Click to collapse
I guess u havent read my post coz i had clearly stated that i had tried flashing update through stock recovery but it says no update.app found.
keikari said:
Check this
https://forum.xda-developers.com/honor-4x/how-to/install-emui-4-1-4x-4c-g-play-g-play-t3515702
It's on honor 4x forum but it says it works on p8lite android 5.0 or higher.
Click to expand...
Click to collapse
Thanks man it was of some help. I now have b896.
hussam.aleem said:
I guess u havent read my post coz i had clearly stated that i had tried flashing update through stock recovery but it says no update.app found.
Click to expand...
Click to collapse
Ahh, sorry, I meant to say that you could try after flashing stock recovery to use EMUI updater to start the flashing.. anyway good that you got it to work