Database Info

[OTA][S-OFF]OTA_Chacha_HTC_Europe_1.54.401.2-1.33.401.1

hey guys,
I just randomly checked for updates from my stock 1.33 EU ROM and it finds me a 1.54 OTA with Android 2.3.5 update.
Since i am using a ClockworkMod Recovery Image as of now, I would need to shift back to Stock Recovery In order to check out this OTA Update..
I googled a lot to find if this update file was ever noticed before, but i did not find any results on any of the forums.. So i think its kinda new
So, anybody running Stock Recovery can update this from a (unrooted?) S-OFF with a superCID chacha device i think..
Correct me if i am wrong..
Or if you want to shift back from CWM to Stock Recovery, check this >>
http://forum.xda-developers.com/showthread.php?t=1164468
(Credits to Mikevhl and Alex C. for their contributions)
Here is the link to the OTA file >>
http://www.mediafire.com/?111mjddqzda8u2p
Before it gets deleted from the mediafire servers, and if this OTA was worth the find, i would like Alex C. t upload the file to his server for further use of the users here..
INSTRUCTIONS :
1. Install Stock Recovery using CWM
>> Download http://www.mediafire.com/?c39i9ubm11ukggn and rename it to PH06IMG.ZIP and place it in sd card root and install via bootloader
{OR}
install a fresh 1.33 ROM using http://alex.swtesting.ro/downloads/....3033H_7.48.35.14_2_release_204385_signed.exe
2.Rename the OTA_Chacha_HTC_blabla.zip file to update.zip and place it on the SD card root folder.
3. Boot into Bootloader menu (Vol DWN+Power) and select recovery using VOL keys and power button to select.
4. Press Vol Up+Power and install update.zip
5. Wait till update completes.
DEVS, pls post in your comments and changes in this update..
I just found out the OTA file, its upto you guys to find out whats in it and i hope it will be of use to you guys in some way..
thanks again
UPDATE :
you can download a CWM backup of 1.54 here:
http://www.schoelli.cc/media/ChaCha1.54CWM.zip
extract it and put it into root of your sd and restore it via CWM
(CREDITS : schölli)

Will this OTA take my S-OFF..?

sathara said:
Will this OTA take my S-OFF..?
Click to expand...
Click to collapse
I dont think so.. Can any f the DEVs there confirm this pls ??

sathara said:
Will this OTA take my S-OFF..?
Click to expand...
Click to collapse
why should it?
and if it would really happens, just S-OFF it again ))
btw....the download link doesn't work for the 1.33 rom file

confirmed.. it DOES NOT S-ON !!

i am not able to install this update
i installed fresh 1.33 with 1.33....exe
installed afterwards cwm, because the fresh installed wiped it away.
booted into bootloader and then into recovery
wiped dalvik cache and made factory reset
but when i try to install it via zip file it aborts after some time with error 7
It says
E:Error in /sdcard/update.zip
(Status 7)
Installation aborted.

schölli said:
i am not able to install this update
i installed fresh 1.33 with 1.33....exe
installed afterwards cwm, because the fresh installed wiped it away.
booted into bootloader and then into recovery
wiped dalvik cache and made factory reset
but when i try to install it via zip file it aborts after some time with error 7
It says
E:Error in /sdcard/update.zip
(Status 7)
Installation aborted.
Click to expand...
Click to collapse
you cannot install this update via CWM..
Read the OP carefully..
Boot into STOCK RECOVERY.. Not CWM..
ie, install 1.33...exe again and you will get back stock recovery..

abraham89 said:
you cannot install this update via CWM..
Read the OP carefully..
Boot into STOCK RECOVERY.. Not CWM..
ie, install 1.33...exe again and you will get back stock recovery..
Click to expand...
Click to collapse
aaaah now i now what you mean by stock recovery...sry, didn't got it. you mean the original htc recovery with the android figurine and the exclemation mark )
ups my fault

schölli said:
aaaah now i now what you mean by stock recovery...sry, didn't got it. you mean the original htc recovery with the android figurine and the exclemation mark )
ups my fault
Click to expand...
Click to collapse
yea !!! exactly.. u're right

device is back up....now i did it correctly... 1.54 is on the device
CWM is also installable and superuser through CWM works also
su binary update also works this time (which didn't work correctly on 1.52)
i am trying to upload a factory reseted CWM backup
---------- Post added at 01:12 PM ---------- Previous post was at 01:07 PM ----------
you can download a CWM backup of 1.54 here:
http://www.schoelli.cc/media/ChaCha1.54CWM.zip
extract it and put it into root of your sd and restore it via CWM

schölli said:
device is back up....now i did it correctly... 1.54 is on the device
CWM is also installable and superuser through CWM works also
su binary update also works this time (which didn't work correctly on 1.52)
i am trying to upload a factory reseted CWM backup
---------- Post added at 01:12 PM ---------- Previous post was at 01:07 PM ----------
you can download a CWM backup of 1.54 here:
http://www.schoelli.cc/media/ChaCha1.54CWM.zip
extract it and put it into root of your sd and restore it via CWM
Click to expand...
Click to collapse
ill update that to the OP..
Did you notice any changes on this build ??

abraham89 said:
ill update that to the OP..
Did you notice any changes on this build ??
Click to expand...
Click to collapse
nope....everything is a little bit smoother, but i think that was also with the 1.52 version....seems that they only fixed some bugs so far

Oh yeah, nice one.. I'll have to test this as it's official, unlike the leaked ones we had. Great job!
As a side note, you won't get S-ON if you have S-OFF'ed via XTC Clip when doing ROM updates. So it's safe

Alex C. said:
Oh yeah, nice one.. I'll have to test this as it's official, unlike the leaked ones we had. Great job!
As a side note, you won't get S-ON if you have S-OFF'ed via XTC Clip when doing ROM updates. So it's safe
Click to expand...
Click to collapse
we need devs like you to try it out..
I've been using it for two days..
And i feel a very bad WiFi performance.. I dont know if this is ROM dependent..
Can you check that out ??

abraham89 said:
hey guys,
I just randomly checked for updates from my stock 1.33 EU ROM and it finds me a 1.54 OTA with Android 2.3.5 update.
Since i am using a ClockworkMod Recovery Image as of now, I would need to shift back to Stock Recovery In order to check out this OTA Update..
I googled a lot to find if this update file was ever noticed before, but i did not find any results on any of the forums.. So i think its kinda new
So, anybody running Stock Recovery can update this from a (unrooted?) S-OFF with a superCID chacha device i think..
Correct me if i am wrong..
Or if you want to shift back from CWM to Stock Recovery, check this >>
http://forum.xda-developers.com/showthread.php?t=1164468
(Credits to Mikevhl and Alex C. for their contributions)
Here is the link to the OTA file >>
http://www.mediafire.com/?111mjddqzda8u2p
Before it gets deleted from the mediafire servers, and if this OTA was worth the find, i would like Alex C. t upload the file to his server for further use of the users here..
INSTRUCTIONS :
1. Install Stock Recovery using CWM
>> Download http://www.mediafire.com/?c39i9ubm11ukggn and rename it to PH06IMG.ZIP and place it in sd card root and install via bootloader
{OR}
install a fresh 1.33 ROM using http://alex.swtesting.ro/downloads/....3033H_7.48.35.14_2_release_204385_signed.exe
2.Rename the OTA_Chacha_HTC_blabla.zip file to update.zip and place it on the SD card root folder.
3. Boot into Bootloader menu (Vol DWN+Power) and select recovery using VOL keys and power button to select.
4. Press Vol Up+Power and install update.zip
5. Wait till update completes.
DEVS, pls post in your comments and changes in this update..
I just found out the OTA file, its upto you guys to find out whats in it and i hope it will be of use to you guys in some way..
thanks again
UPDATE :
you can download a CWM backup of 1.54 here:
http://www.schoelli.cc/media/ChaCha1.54CWM.zip
extract it and put it into root of your sd and restore it via CWM
(CREDITS : schölli)
Click to expand...
Click to collapse
are there any changes in the new version???

carstenheuer said:
are there any changes in the new version???
Click to expand...
Click to collapse
y do u need to quote the whole post & size5 your words? i felt it kinda rude...
---------- Post added at 11:08 PM ---------- Previous post was at 11:06 PM ----------
schölli said:
device is back up....now i did it correctly... 1.54 is on the device
CWM is also installable and superuser through CWM works also
su binary update also works this time (which didn't work correctly on 1.52)
i am trying to upload a factory reseted CWM backup
---------- Post added at 01:12 PM ---------- Previous post was at 01:07 PM ----------
you can download a CWM backup of 1.54 here:
http://www.schoelli.cc/media/ChaCha1.54CWM.zip
extract it and put it into root of your sd and restore it via CWM
Click to expand...
Click to collapse
so su binary 3.0.3,3.05,3.07 works? gonna give a try thx mate

e.japonica said:
y do u need to quote the whole post & size5 your words? i felt it kinda rude...
---------- Post added at 11:08 PM ---------- Previous post was at 11:06 PM ----------
so su binary 3.0.3,3.05,3.07 works? gonna give a try thx mate
Click to expand...
Click to collapse
sorry!!!
is the default android lockscreen still faulty?

is the default android lockscreen still faulty?
Click to expand...
Click to collapse
what do you mean by faulty? as i don't face any problem with the lock screen in previous version?
---------- Post added at 01:07 AM ---------- Previous post was at 12:48 AM ----------
can i request a clean 1.54 zip without su/or a backup without su? (without any modification) Thanks in advance :0

e.japonica said:
what do you mean by faulty? as i don't face any problem with the lock screen in previous version?
---------- Post added at 01:07 AM ---------- Previous post was at 12:48 AM ----------
can i request a clean 1.54 zip without su/or a backup without su? (without any modification) Thanks in advance :0
Click to expand...
Click to collapse
I am getting another ChaCha today (those are now our new company phones) and i will s-off it, update it to 1.54 and will zip it without any modification tonight.
hope you can wait a little bit )

I'm unable to Install Stock Recovery img, everytime after the bootloader loading the file,
a line saying "parsing PH06IMG.zip" then nothing happened, retun to bootloader,
and cwm image still there

Unable to install 5.0 on rooted N5

Hi guys ,
I have a rooted nexus 5 running on original stock rom with clockwork recovery installed. I have been getting pop ups to download Andriod 5.0 for last 10 days , Every time I download it , it takes me to recovery and than gives me a message "unable to open the package etc." and cancels the install.
I have tried clearing up the cache , did factory reset , same result everytime.
Any suggestions what can i do ?

You need to be 100% stock (including recovery) to accept the OTA. Restore your phone to full stock and try again.

_MetalHead_ said:
You need to be 100% stock (including recovery) to accept the OTA. Restore your phone to full stock and try again.
Click to expand...
Click to collapse
How do I do that ?
This is wifey's phone , if she looses her data 1 more time than I m dead.

Flash the newest factory image in fastboot, just dont flash the userdata image.

Lokke9191 said:
Flash the newest factory image in fastboot, just dont flash the userdata image.
Click to expand...
Click to collapse
So If I just download 5.0.1 (LRX22C) from https://developers.google.com/android/nexus/images and flash it via Fastboot , It will take phone back to Factory state and root will be lost ?

namz said:
So If I just download 5.0.1 (LRX22C) from https://developers.google.com/android/nexus/images and flash it via Fastboot , It will take phone back to Factory state and root will be lost ?
Click to expand...
Click to collapse
Ya root will be lost. Just unzip that image fully. Then flash everything but userdata individually. She wont lose her data or setup. Then fastboot flash twrp. Boot into twrp and install supersu. Good to go.

Lokke9191 said:
Ya root will be lost. Just unzip that image fully. Then flash everything but userdata individually. She wont lose her data or setup. Then fastboot flash twrp. Boot into twrp and install supersu. Good to go.
Click to expand...
Click to collapse
Thanks So i assuming userdata is one of the files that will come once I unzip the downloaded file ?

namz said:
Thanks So i assuming userdata is one of the files that will come once I unzip the downloaded file ?
Click to expand...
Click to collapse
Ya itll be on there. Also you dont need to flash the bootloader either, being that its the same as the 5.0 one.

Lokke9191 said:
Ya itll be on there. Also you dont need to flash the bootloader either, being that its the same as the 5.0 one.
Click to expand...
Click to collapse
Cool Thanks , Btw its on 4.4 atm , so I have flash bootloader file. Will give a try !!

namz said:
Cool Thanks , Btw its on 4.4 atm , so I have flash bootloader file. Will give a try !!
Click to expand...
Click to collapse
wait
---------- Post added at 10:03 PM ---------- Previous post was at 10:01 PM ----------
Lokke9191 said:
wait
Click to expand...
Click to collapse
If its on 4.4 you should do a clean install as its a big upgrade. To save her data, flash the 4.4 recovery, and boot images. That should bring you back to stock so you can just take the ota.
Thatll work as long as you haven't made any further modifications.

Lokke9191 said:
wait
---------- Post added at 10:03 PM ---------- Previous post was at 10:01 PM ----------
If its on 4.4 you should do a clean install as its a big upgrade. To save her data, flash the 4.4 recovery, and boot images. That should bring you back to stock so you can just take the ota.
Thatll work as long as you haven't made any further modifications.
Click to expand...
Click to collapse
Hmm where do I get 4.4 recovery and boot images from

Uh oh. I think you were too late.

namz said:
Hmm where do I get 4.4 recovery and boot images from
Click to expand...
Click to collapse
Is the 4.4 image available from google site?
---------- Post added at 10:08 PM ---------- Previous post was at 10:06 PM ----------
Lokke9191 said:
Is the 4.4 image available from google site?
Click to expand...
Click to collapse
They are here just unzip the proper image
https://developers.google.com/android/nexus/images

lbingham said:
Uh oh. I think you were too late.
Click to expand...
Click to collapse
Lol. I thought he was already on 5.0. Glad i caught him in time. I know how pissed my wife gets when I mod or flash stuff to her phone and she doesn't like the outcome, or the version is buggy, or she has to re setup her stuff. Glad I can help other avoid that

Lokke9191 said:
Is the 4.4 image available from google site?
---------- Post added at 10:08 PM ---------- Previous post was at 10:06 PM ----------
They are here just unzip the proper image
https://developers.google.com/android/nexus/images
Click to expand...
Click to collapse
OK. So download 4.4.4 and unzip and flash only recovery and boot images via fastboot ( boot images would be files ending with .img , i.e. more than 1 file ?

namz said:
OK. So download 4.4.4 and unzip and flash only recovery and boot images via fastboot ( boot images would be files ending with .img , i.e. more than 1 file ?
Click to expand...
Click to collapse
Flash "boot.img" its only one file. Then flash "recovery. img" also one file. So two files total.

[Q] Back to stock recovery B137SP03 without recovery image

Hello all,
I have been going slightly mad today trying to get my mate 7 2GB back from CWM to stock recovery. The main problem is that I do not have a stock recovery image. But after being shown where to find one, I noticed that I could not get it successfully flashed either.
Since I do not really know how to do this, I used flashify, but that did not work and either returned me to the CWM or sent me to rescue.
Can someone help me to a) get a stock recovery image for the Mate 7 version MT7-L09 and b) show me how to properly flash it?

Find stock recovery is easy.. only a question why flashify don't work for you? It work fine for me... your device is rooted?

djzero86 said:
Find stock recovery is easy.. only a question why flashify don't work for you? It work fine for me... your device is rooted?
Click to expand...
Click to collapse
Hi @dzjero86, my device is rooted and I am on the B137SP03 version atm, using CWM. Don't know why Flashify is not working for flashing a recovery image. It works fine to flash a CWM recovery. Maybe I have the wrong stock recovery... If you can find it, can you send me the link or add it as an attachment here?

Please guys help me to . i have that same problem i have been trying to flash the stock recovery again but i couldn't even with flashify after i flash i takes me to bootloader screen and it shows me a fun_error message
I have a tl-10 device

dekraan said:
Hi @dzjero86, my device is rooted and I am on the B137SP03 version atm, using CWM. Don't know why Flashify is not working for flashing a recovery image. It works fine to flash a CWM recovery. Maybe I have the wrong stock recovery... If you can find it, can you send me the link or add it as an attachment here?
Click to expand...
Click to collapse
A way to find the stock recovery is : download the whole B137SP03 Rom from the Huawei site , and use a tool called "Firmware unpacker for Huawei" whit this tool you can extract the recovery.img from the Rom and try to flash it using flashify
Firmware unpacker
http://forum.xda-developers.com/mate-7/development/firmware-unpacker-huawei-t2879754
Rom
http://forum.xda-developers.com/mate-7/general/firmware-huawei-ascend-mate-7-b137sp03-t3041629
Pd : I am not a developer or anything similar but I have some years of experience rooting and etc ...
---------- Post added at 10:12 AM ---------- Previous post was at 10:00 AM ----------
Ali_adel_medo said:
Please guys help me to . i have that same problem i have been trying to flash the stock recovery again but i couldn't even with flashify after i flash i takes me to bootloader screen and it shows me a fun_error message
I have a tl-10 device
Click to expand...
Click to collapse
You have a unlocked bootloader???

Yes i have unlocked and rooted the phone using the cwm recovery and now a i can't flash the stock recovery any more

Ali_adel_medo said:
Yes i have unlocked and rooted the phone using the cwm recovery and now a i can't flash the stock recovery any more
Click to expand...
Click to collapse
Do you tried flash via fastboot ?
fastboot flash recovery recovery.img
Or try to use this tool
http://forum.xda-developers.com/mat...custom-recovery-tool-mt7-l10-l10-mt7-t3022424
This should work.

The fast boot just stucks at waiting for device
And the tool you send says that the stock recovery works only on tl_09 and my device is tl_10

djzero86 said:
A way to find the stock recovery is : download the whole B137SP03 Rom from the Huawei site , and use a tool called "Firmware unpacker for Huawei" whit this tool you can extract the recovery.img from the Rom and try to flash it using flashify
Firmware unpacker
http://forum.xda-developers.com/mate-7/development/firmware-unpacker-huawei-t2879754
Rom
http://forum.xda-developers.com/mate-7/general/firmware-huawei-ascend-mate-7-b137sp03-t3041629
Pd : I am not a developer or anything similar but I have some years of experience rooting and etc ...
---------- Post added at 10:12 AM ---------- Previous post was at 10:00 AM ----------
You have a unlocked bootloader???
Click to expand...
Click to collapse
Ok, I couldnt access your firmware unpacker, but I did manage to use the tool you suggested.
I have a different recovery screen, but is this the right one? It has EMUI large in centre screen and the options reboot system now, wipe data/factory reset and wipe cache partition.
If this is the correct one, and I am already on the D137SP03 ROM, I should be able to locally update right?
I tried this, and got a lot further this time, but my phone gave an error message during the update. Do I need to flash the original B137SP03 rom again, even though I am already on it?

I think you maybe can flash using adb commands and also you need adb drivers working
---------- Post added at 11:23 AM ---------- Previous post was at 11:15 AM ----------
dekraan said:
Ok, I couldnt access your firmware unpacker, but I did manage to use the tool you suggested.
I have a different recovery screen, but is this the right one? It has EMUI large in centre screen and the options reboot system now, wipe data/factory reset and wipe cache partition.
If this is the correct one, and I am already on the D137SP03 ROM, I should be able to locally update right?
I tried this, and got a lot further this time, but my phone gave an error message during the update. Do I need to flash the original B137SP03 rom again, even though I am already on it?
Click to expand...
Click to collapse
Ok.... you have the stock recovery now???

djzero86 said:
I think you maybe can flash using adb commands and also you need adb drivers working
---------- Post added at 11:23 AM ---------- Previous post was at 11:15 AM ----------
Ok.... you have the stock recovery now???
Click to expand...
Click to collapse
I think so. If stock looks like I described: black screen, large EMUI logo, and the options reboot system now, wipe data/factory reset and wipe cache partition?

That's right... you have stock recovery... sometimes the update fail if the UPDATE.APP is on the internal storage.. try to flash from a micro sd card or re-download the update ....
English is not my first language...

djzero86 said:
That's right... you have stock recovery... sometimes the update fail if the UPDATE.APP is on the internal storage.. try to flash from a micro sd card or re-download the update ....
English is not my first language...
Click to expand...
Click to collapse
Great, thank you for your fantastic help!
I will get a new micro-sd card tomorrow, and will try it right away!

Good luck... come back to report

djzero86 said:
Good luck... come back to report
Click to expand...
Click to collapse
No luck so far.... I've downloaded the update.zip, put it in my mnt/ext_sdcard/dload folder and start the local update. It begins OK, as the progress bar moves along. But after about 25% it shoots to the end, and then I get an update failed screen with a red exclamation mark.
What could I try to get it to work??

dekraan said:
No luck so far.... I've downloaded the update.zip, put it in my mnt/ext_sdcard/dload folder and start the local update. It begins OK, as the progress bar moves along. But after about 25% it shoots to the end, and then I get an update failed screen with a red exclamation mark.
What could I try to get it to work??
Click to expand...
Click to collapse
Ok, I just reinstalled the B137P03 version from the how to install lollipop thread, and that went successful. Now going to try the update.zip! Keep you posted

Ah, now we're talking It seems to have worked. Phone is now showing 'Android is upgrading' and 'optimising app.....'
Great! It does seem strange I had to reinstall the B137SP03 rom, but that did the trick!

Recovery stock EVA-L09

Hello, does someone have the stock recovery for EVA-L09 ?

marmottator said:
Hello, does someone have the stock recovery for EVA-L09 ?
Click to expand...
Click to collapse
If you download this OTA and unzip it there are recovery file in it.
http://www.huaweiblog.de/software/android/marshmallow/huawei-p9-firmware-update-ota-b135/
But i dont know if it works! Try it on your own risk.

Thx for that, but i don't try, risk of brick lol

marmottator said:
Thx for that, but i don't try, risk of brick lol
Click to expand...
Click to collapse
I understand.
If you check this guide on how to root there are recovery file in the download that is for EVA-L09.
http://forum.xda-developers.com/showthread.php?t=3367800
Sent from my Nexus 5X

220volt said:
I understand.
If you check this guide on how to root there are recovery file in the download that is for EVA-L09.
http://forum.xda-developers.com/showthread.php?t=3367800
Sent from my Nexus 5X
Click to expand...
Click to collapse
Oh yes, thx, i see in this folder but i forget where lol
Now, i just find to return full stock and update firmware

marmottator said:
Oh yes, thx, i see in this folder but i forget where lol
Now, i just find to return full stock and update firmware
Click to expand...
Click to collapse
Have you tried the recovery in that folder? Does it work?
Sent from my Nexus 5X

Not yet, but i found in the SRKTool a recovery stock too
I test recovery stock in the srktool. it's work correctly

Back to Vodafone Rom
Does anyone have a backup of the stock UK Vodafone Rom to go back to after testing this Rom?

Martyp9 said:
Does anyone have a backup of the stock UK Vodafone Rom to go back to after testing this Rom?
Click to expand...
Click to collapse
possibly be able to go back to it using the hisuite on windows

Thank you for your reply. I have already flashed the Rom. I was looking for a way back just in things go wrong.

220volt said:
I understand.
If you check this guide on how to root there are recovery file in the download that is for EVA-L09.
http://forum.xda-developers.com/showthread.php?t=3367800
Sent from my Nexus 5X
Click to expand...
Click to collapse
I have uploaded here if it helps anyone.
Stock Recovery Download
You can either use fastboot to flash or the bat file included in this zip file.

Hi all im new in this forum p9. I work with mate7 but now i need some help from you. I need stock recovery.img from EVA-L09C432B383. Can any one upload for me. Thanks

chudy_85 said:
Hi all im new in this forum p9. I work with mate7 but now i need some help from you. I need stock recovery.img from EVA-L09C432B383. Can any one upload for me. Thanks
Click to expand...
Click to collapse
Extracted them from the B383 update.
But im wondering why there are 2 Recovery files, both are the same size but they give back different md5hash sum, that mean that there is something different about them.
But here you are:
https://drive.google.com/file/d/0B2ZDxrvrYT7gQXNWbUJNVmpOTTg/view?usp=sharing

smohanv said:
I have uploaded here if it helps anyone.
Stock Recovery Download
You can either use fastboot to flash or the bat file included in this zip file.
Click to expand...
Click to collapse
Download Links don´t work.
---------- Post added at 06:07 PM ---------- Previous post was at 06:06 PM ----------
xtcislove said:
Extracted them from the B383 update.
But im wondering why there are 2 Recovery files, both are the same size but they give back different md5hash sum, that mean that there is something different about them.
But here you are:
https://drive.google.com/file/d/0B2ZDxrvrYT7gQXNWbUJNVmpOTTg/view?usp=sharing
Click to expand...
Click to collapse
Download link - gDrive- doesn´t work either.

derJack said:
Download Links don´t work.
---------- Post added at 06:07 PM ---------- Previous post was at 06:06 PM ----------
Download link - gDrive- doesn´t work either.
Click to expand...
Click to collapse
look at my signature

I got an issue with an P9 [EVA l_09] after upgrading from latest Marshmallow C432 single SIM to Nougat via SD Card update.app and restart. I did similar updates on 5-10 different devices w/o an issue.
Fist part went fine, but with the second [HW_init] it went into this:
http://www.derjackistweg.de/img_20170601_142722_resized_20170601_022749113
I was not able to flash ANY different update.app after that via SD card [weather Marshmallow 1rst or later version]
The device is stock - NO change in Bootloader
I do not have any recovery from before or whatever.
I do want to use this device in whatever Firmware!
PS: I cannot post by myself. Though my account is 11 (!) years old - I am not experienced enough Back in the day I had more posts of course, XDA made changes over the years.

ROOT-TWRP-UNLOCK BOOTLOADER FOR LENOVO K6 NOTE (K53a48)

I am not responsible if you don't know
what you are getting into and end up messing up your phone
In order to root K6 Note you need to do the following,
1. Unlock boot loader. how to do that follow here >>
http://lenovo-forums.ru/topic/21685-lenovo-vibe-k6-note-разблокировка-bootloader
( It will Wipe all Data)
2. Install Twrp from here>>
http://lenovo-forums.ru/topic/21687-lenovo-vibe-k6-note-rasshirennoe-rekaveri-twrp-by-sevenmaxs/
3. Modify boot image and flash modified boot image with Carliv Image Kitchen from here >>
https://forum.xda-developers.com/android/development/tool-cika-carliv-image-kitchen-android-t3013658
4. Changing Values in boot.img
Unpack the boot image using the above tool, once unpacked go the unpack folder then into ramdisk folder and edit the default.prop using notepad++ or wordpad
Change the value of the following lines
1. ro.secure=1 to ro.secure=0
2. security.pref_harden= 1 to security.pref_harden= 0
(Change only 1 to 0 nothing else & do not forget to save the file )
3.Once done repack the boot image using the above tool.
5 .Flash the modified boot.image through fastboot, how to flash through fastboot refer here>>
https://forum.xda-developers.com/showthread.php?t=1752270
6. Reboot into recovery and flash supersu from here>>
https://download.chainfire.eu/1001/S…perSU-v2.78-20
The supersu installation should be successful now. reboot and you will see supersu app in the app drawer. Cheers :good::good::good::good:
(P.S I have attached the modified boot image for firmware k53_s123_170216_ROW, so no need to modify the boot image if you are on this firmware.)

Where is the attached k53_s123_170216_ROW boot image ?

mehmet6ok said:
Where is the attached k53_s123_170216_ROW boot image ?
Click to expand...
Click to collapse
Boot.img updated. Cheers

Sounds interesting thanks as I keep getting errors trying to flash SuperSU or Magisk.
I'm on firmware k53_s123_170216_ROW so I will be able to use your boot.img but how would one go about getting the boot.img to modify ? The Nandroid backup is in the boot.emmc.win format and the whole partition I suppose ?
---------- Post added at 08:36 AM ---------- Previous post was at 08:27 AM ----------
Oops so I flashed your boot.img :
tools>fastboot flash boot boot.img
target reported max download size of 535822336 bytes
sending 'boot' (24894 KB)...
OKAY [ 0.816s]
writing 'boot'...
OKAY [ 0.331s]
finished. total time: 1.151s
Click to expand...
Click to collapse
At the end on the screen it says in green at the top "flashing boot ...", rebooted into TWRP 3.0.3.0 with long "VOL UP+VOL DOWN" + "POWER" press.
Tried to install :
- UPDATE-SuperSU-v2.78-20160905010000.zip (the one you mention)
- SuperSU-v2.79-201612051815.zip
- Magisk-v12.0.zip
But they all fail unfortunately, same error message as before flashing your boot.img :
Magisk12 error :
"Unable to unpack boot.img"
SuperSU error :
"-Extracting ramdisk
--- Failure, aborting"
My model is K53a48
---------- Post added at 08:50 AM ---------- Previous post was at 08:36 AM ----------
ok, I updated to TWRP-3.1.0.1_K53a48_by_SevenMaxs.7z and I was able to flash SuperSU-v2.79-201612051815.zip without errors. All booted up and SuperSU in the app drawer and rooted, thanks for the tips, man !
A few more questions if I may :
- is there a stock recovery to put back the K6 Note in factory mode ?
- how does one go about getting the boot.img out of a device for patching ?

If will not modify the boot.img what will gonna happen?
Thanks to this furom....Really help for me

webvan said:
Sounds interesting thanks as I keep getting errors trying to flash SuperSU or Magisk.
I'm on firmware k53_s123_170216_ROW so I will be able to use your boot.img but how would one go about getting the boot.img to modify ? The Nandroid backup is in the boot.emmc.win format and the whole partition I suppose ?
---------- Post added at 08:36 AM ---------- Previous post was at 08:27 AM ----------
Oops so I flashed your boot.img :
At the end on the screen it says in green at the top "flashing boot ...", rebooted into TWRP 3.0.3.0 with long "VOL UP+VOL DOWN" + "POWER" press.
Tried to install :
- UPDATE-SuperSU-v2.78-20160905010000.zip (the one you mention)
- SuperSU-v2.79-201612051815.zip
- Magisk-v12.0.zip
But they all fail unfortunately, same error message as before flashing your boot.img :
Magisk12 error :
"Unable to unpack boot.img"
SuperSU error :
"-Extracting ramdisk
--- Failure, aborting"
My model is K53a48
---------- Post added at 08:50 AM ---------- Previous post was at 08:36 AM ----------
ok, I updated to TWRP-3.1.0.1_K53a48_by_SevenMaxs.7z and I was able to flash SuperSU-v2.79-201612051815.zip without errors. All booted up and SuperSU in the app drawer and rooted, thanks for the tips, man !
A few more questions if I may :
- is there a stock recovery to put back the K6 Note in factory mode ?
- how does one go about getting the boot.img out of a device for patching ?
Click to expand...
Click to collapse
Big Question
If I will not patch the boot.img and flash the new 3.1.0.1_K53a48_by_SevenMaxs.7z and then flash the
SuperSU-v2.79-201612051815.zip
will it be successfull?
Yeah I can't flash SuperSU-v2.79-201612051815.zip
In old twrp...SuperSu App never apper in my home drawer...
---------- Post added at 06:29 AM ---------- Previous post was at 06:06 AM ----------
Do you have a custom kernel?

Why don't you want to use the patched boot.img ?
You tried with the new TWRP-3.1.0.1 and it doesn't work ?

firemax13 said:
Big Question
If I will not patch the boot.img and flash the new 3.1.0.1_K53a48_by_SevenMaxs.7z and then flash the
SuperSU-v2.79-201612051815.zip
will it be successfull?
Yeah I can't flash SuperSU-v2.79-201612051815.zip
In old twrp...SuperSu App never apper in my home drawer...
---------- Post added at 06:29 AM ---------- Previous post was at 06:06 AM ----------
Do you have a custom kernel?
Click to expand...
Click to collapse
webvan said:
Why don't you want to use the patched boot.img ?
You tried with the new TWRP-3.1.0.1 and it doesn't work ?
Click to expand...
Click to collapse
So I need to flash the modified boot.img to flash the updated twrp and then to flash the supersu.zip successfully?
I Mean flash the modified boot.img and the updated twrp will work?

firemax13 said:
So I need to flash the modified boot.img to flash the updated twrp and then to flash the supersu.zip successfully?
I Mean flash the modified boot.img and the updated twrp will work?
Click to expand...
Click to collapse
You cannot flash supersu without the modified boot image.
You need to flash the recovery and modified boot image to successfully flash supersu.

adilrenzu said:
You cannot flash supersu without the modified boot image.
You need to flash the recovery and modified boot image to successfully flash supersu.
Click to expand...
Click to collapse
Thanks to your reply.....sorry Im so curious about it.....
So we gonna still receiving the OTA updates after flashing the modified boot.img and twrp and ROOT? .....Or we can still update our devices after all the things happen??
sorry for noob question and bad ass english

firemax13 said:
Thanks to your reply.....sorry Im so curious about it.....
So we gonna still receiving the OTA updates after flashing the modified boot.img and twrp and ROOT? .....Or we can still update our devices after all the things happen??
sorry for noob question and bad ass english
Click to expand...
Click to collapse
To receive OTA's you need to be on stock recovery, and stock boot image without any modification to the system partition.

Can the stock recovery be downloaded anywhere ? Thanks !

adilrenzu said:
To receive OTA's you need to be on stock recovery, and stock boot image without any modification to the system partition.
Click to expand...
Click to collapse
Again thanks to your reply
Still waiting for official custom rom and official custom recovery.......I hope lineage os listening to us.....

firemax13 said:
Again thanks to your reply
Still waiting for official custom rom and official custom recovery.......I hope lineage os listening to us.....
Click to expand...
Click to collapse
as for custom roms i dont think thats gonna happen anytime soon, and there is nothing like official custom recovery, there is only custom recovery like TWRP or CMW.

Hi there, mate. If I do this process, will I be able to remove TWRP if needed (for updating reasons), if so, what would the process be?

adilrenzu said:
as for custom roms i dont think thats gonna happen anytime soon, and there is nothing like official custom recovery, there is only custom recovery like TWRP or CMW.
Click to expand...
Click to collapse
So you can't reflash the original recovery ? So that means no more OTA updates, but would it still work with an official update that was downloaded, assuming one becomes available ? Thanks !

adilrenzu
I was able to unlock bootloader, installed twrp and root according to your guide
and
also successfully returned to original stock 6.0 rom, stock recovery according to androidmtk's Lenovo_K53_USR_S107_1609131839_Q00380_ROW firmware.
This is a new toy for me now. Many thanks...:laugh:

Can you explain how you went back to stock?

webvan said:
Can you explain how you went back to stock?
Click to expand...
Click to collapse
Hi
Device cant update via ota. I dont really know K53_USR_S107_1609131839_Q00380_ROW firmware is last for some region or not. So Im trying to update to stock K53_S123_170216_ROW firmware. After testing and solving ota I will write all steps.

ok, thanks, I suppose it need to be downloaded first somewhere ?