Related
As per screenshot 5.1 OTA update for Retail GB is out.
Files:
--> Retail.en.GB 4.4.4 FXZ. (Full ROM) (Google Drive)
--> Retail.en.GB 5.1 OTA zip. (3 Parts) (Google Drive)
--> Retail.en.GB 5.1 OTA zip. (1 Part) (Mega) [May be having issues]
--> Retail.en.GB 5.1 OTA zip. (1 Part) (Google Drive)
--> Numerous 5.1 & 4.4.4 FXZ (FULL ROMS) (FileFactory)
Credits:
@mlodykaras
@beljim7419
NB: REMEMBER TO BE ROOTED BEFORE SO YOU CAN ACCESS /CACHE PARTITION AFTER DOWNLOAD OF THE OTA ZIP HAS FINISHED. I learnt this the hard way.
NB: SO FAR MOTOROLA DOWNLOAD MANAGER DOESN'T WORK FOR NEWER PHONES UPDATING.
NB: REMEMBER TO HIT THAT THANKS BUTTON AND TO RATE THE THREAD. THANKS :good:
Last Updated: (YYYY-MM-DD)
2015-07-04
Bugs:
--> Dialog for bluetooth file sending progress is still KK.
--> Wave to wake up (I know they removed it therefore its a bug in my eyes)
--> I'm having Wi-Fi issues with not seeing certain routers and connecting, even though its saved and even after a radio cache clear using fastboot.
--> I'm having YouTube video playback issues in the YouTube App, even after I set to use the old AwesomePlayer.
--> I'm having general UI lag and apps hanging.
--> For me boot animation lag is now a norm, even after I updated Moto Boot Services. On KK it was extremely rare.
--> YOU LET ME KNOW...!
Last Edited: (YYYY-MM-DD)
2015-07-04
Reserve No. 2
To trick MDM into seeing the update, put your phone into airplane mode, reboot to recovery, erase cache, reboot normally, then connect to MDM and check for updates.
How do i clear cache in stock recovery?
stealtheye said:
How do i clear cache in stock recovery?
Click to expand...
Click to collapse
In stock recovery, you will see an option to clear cache.
_litz said:
To trick MDM into seeing the update, put your phone into airplane mode, reboot to recovery, erase cache, reboot normally, then connect to MDM and check for updates.
Click to expand...
Click to collapse
kenosis said:
In stock recovery, you will see an option to clear cache.
Click to expand...
Click to collapse
Only the see the open android with red triangle?
Edit: Got the menu.
Edit 2: This is taking quite a while. Normal?
Yes, it can take 10-20 minutes.
_litz said:
To trick MDM into seeing the update, put your phone into airplane mode, reboot to recovery, erase cache, reboot normally, then connect to MDM and check for updates.
Click to expand...
Click to collapse
Should the cache erasing take a while. Its quite long now.
_litz said:
Yes, it can take 10-20 minutes.
Click to expand...
Click to collapse
Oh wow ok thanks.
stealtheye said:
Only the see the open android with red triangle?
Edit: Got the menu.
Edit 2: This is taking quite a while. Normal?
Click to expand...
Click to collapse
Yes, Normal. you will see "M" in Green colour circle for a few minutes before it boots
Yeah, beats me why stock recovery takes so long to do something TWRP does in 2 seconds.
_litz said:
Yes, it can take 10-20 minutes.
Click to expand...
Click to collapse
Nope MDM still says no update.
_litz said:
Yeah, beats me why stock recovery takes so long to do something TWRP does in 2 seconds.
Click to expand...
Click to collapse
MDM still saying no update. Should I just OTA?
That's very strange ... it SHOULD be detecting the update.
If you can get the FXZ/SBF file from another source then you may as well take the OTA, or just get the full file from elsewhere and use RSD-Lite directly (just like you would have done otherwise).
sometimes you have to unplug/replug your device a few times with MDM ... also if it says "current version : NA" then try enabling USB Development mode, unplugging and replugging.
If everything is working OK, it should say either no update, or update, and then list your device's current version.
_litz said:
That's very strange ... it SHOULD be detecting the update.
If you can get the FXZ/SBF file from another source then you may as well take the OTA, or just get the full file from elsewhere and use RSD-Lite directly (just like you would have done otherwise).
sometimes you have to unplug/replug your device a few times with MDM ... also if it says "current version : NA" then try enabling USB Development mode, unplugging and replugging.
If everything is working OK, it should say either no update, or update, and then list your device's current version.
Click to expand...
Click to collapse
Yeah it lists device correctly but says no update.
I'll just OTA for now and use the FXZ later if it appears. It may be due to the fact that moto have only allowed OTAs for now.
_litz said:
That's very strange ... it SHOULD be detecting the update.
If you can get the FXZ/SBF file from another source then you may as well take the OTA, or just get the full file from elsewhere and use RSD-Lite directly (just like you would have done otherwise).
sometimes you have to unplug/replug your device a few times with MDM ... also if it says "current version : NA" then try enabling USB Development mode, unplugging and replugging.
If everything is working OK, it should say either no update, or update, and then list your device's current version.
Click to expand...
Click to collapse
I've downloaded the OTA. But i wasn't rooted and need to be to capture the OTA. Can I flash TWRP and then SU zip without losing the OTA downloaded in cache? Or is there a way to get it without root? I tried the ADB way...not very well but kept on getting access denied when I remounted.
PLEASE ANY HELP!?
I think you're going to have to go to one of the "capture the OTA" specific pages for help on that, but I think you can flash TWRP and grab it from cache directly in TWRP.
Moto X, unfortunately, doesn't support booting TWRP from fastboot.
_litz said:
I think you're going to have to go to one of the "capture the OTA" specific pages for help on that, but I think you can flash TWRP and grab it from cache directly in TWRP.
Moto X, unfortunately, doesn't support booting TWRP from fastboot.
Click to expand...
Click to collapse
Ya the problem there aren't many of those and helpful ones. Ill just Install it. If i need to wipe I'll just factory reset. I'm sure others in a while will get the file or the FXZ will eventually make its way out. But thanks for your help. Had I known I had to be rooted I would,ve done it before. But i don't want to try now and loose the file in cache. It may clear it when I shutdown or reboot up to install anyway and then I'll also have to remove root if its there to copy. TOO MANY MISSIONS. But thanks bro!
I have got the OTA file.
The problem is now to upload it somewhere. My home ADSL upload speed is abysmal (no, really, 0.5MegaBit/s is about the standard here) and my work connection is behind a proxy that blocks EVERYTHING.
drive.google is blocked, but docs.google isn't... I'll try to find a workaround.
btw file name is: Blur_Version.212.44.26.ghost_row.Retail.en.GB.zip (669 MB (701.692.377 byte))
You can find it here: ftp://fw.ydevices.com/YotaPhone2/Firmwares/RU/
Install either via OTA update if you're already on the 1.87 RU ROM like I am. On my device it first wanted to install the update only, about 67MB, but it failed to install; then the next time I checked for updates after reboot through the settings update menu, it downloaded the full file, about 0,99 GB. Then the update went all the way through. SuperSU is lost on the way, I will try if it still works through the recovery installation.
You can also install through Yotaflasher like it's explained here: http://forum.xda-developers.com/showthread.php?t=3247356
Didn't have time to test things out, but it's still Lollipop 5.0, so only bugfixes and some new yotapanel features I guess.
Enjoy!
Thanks for that muchly dude, hadn't checked that for a while.
Update seems to be stability improvements, power efficiency improvements and some yotamirror and panel improvements and features.
Its not 5.1, but it's an update, I'll take it.
And yeah, super glad moved to the RU ROM. Backing up now, will OTA flash update once that's done. SuperSU has been flashable everytime after an update so far so fingers crossed.
All up and running .
I was rooted, running RU 1.87 with TWRP - phone handled it all just fine - downloaded OTA, pressed install - it went to TWRP > flashed stock recovery back over itself > rebooted and installed.
Phone booted up, all working fine. Lost root - simple reboot and flash the SU.zip had sitting there from the last update. Cache and Dalvik wiped for good measure.
Reboot and all is well and back to normal but with a few improvements, lovely.
About as easy as it's even been done really.
Hope everyone else gets to enjoy the update through similarly smooth procedures .
Yeah, I ended up doing a fresh installation plus rooting, everything smooth. I'm never too sure what an update leaves behind.
It's really a great device, hopefully they'll keep updating things for a while. Of course version 6.0 would be welcomed... Apparently, by the numbering they use, next step would be either 1.2.xx with Android 5.1 or 2.x.xx with 6.0. Let's see.
Fair play, I toyed with idea of it, but was fresh from last install and honestly don't have the time to set everything up again.
My hope is they take all their good ideas from this and can at least join someone else in making a great device.
Saw a working bendy phone the other day, lets you turn pages on reading app by bending corner as you would a book etc. I thought if that could be combined with yota tech, then you have damn near the perfect tablet.
Honestly I don't think we'll get 5.1, let alone 6.0. They're refining their ideas in prep for Yotaphone 3, that and the possible tablet are their main focus right now.
Interestingly, the update flashed it's stock recovery over twrp - someone prepared for the possibility of root owners this time around. So they are still paying attention .
So any idea what's the difference between the EU and the RU rom? I mean there has to be some reason they are two separate roms.
To answer my own question: there isn't too many differences between EU and RU roms. I did a diff between the RU1.1.59 and EU1.1.60, and out of 2092 files, roughly 1900 of the files inside system.img were identical. The APKs were slightly different, but only slightly. So probably the difference comes from some differently named resources.
The RU version also has some additional apps which the EU version does not have, such as Esquire, Questions, Strelka and Vector. These are probably the main reason why they have different ROMs. They might only work in Russia.
Jeopardy said:
To answer my own question: there isn't too many differences between EU and RU roms. I did a diff between the RU1.1.59 and EU1.1.60, and out of 2092 files, roughly 1900 of the files inside system.img were identical. The APKs were slightly different, but only slightly. So probably the difference comes from some differently named resources.
The RU version also has some additional apps which the EU version does not have, such as Esquire, Questions, Strelka and Vector. These are probably the main reason why they have different ROMs. They might only work in Russia.
Click to expand...
Click to collapse
FYI the difference is essentially the product package configuration (app bundles that are pre-loaded) but there are also some differences between the resources used for the stock apps. One in particular (my personal fav ) is the dialler - the RU variant includes cyrillic characters regardless of language/locale setting (feature). The EU will give you a regular english-only dialler if you're using english locale settings
Vuche said:
You can find it here: ftp://fw.ydevices.com/YotaPhone2/Firmwares/RU/
Install either via OTA update if you're already on the 1.87 RU ROM like I am. On my device it first wanted to install the update only, about 67MB, but it failed to install; then the next time I checked for updates after reboot through the settings update menu, it downloaded the full file, about 0,99 GB. Then the update went all the way through. SuperSU is lost on the way, I will try if it still works through the recovery installation.
You can also install through Yotaflasher like it's explained here: http://forum.xda-developers.com/showthread.php?t=3247356
Didn't have time to test things out, but it's still Lollipop 5.0, so only bugfixes and some new yotapanel features I guess.
Enjoy!
Click to expand...
Click to collapse
Ho to flash the update zip file? I m stuck on 4.4.3...
does nyone know how to flash the file zip into the phone?? i have no idea how it works and i dont find any infos
Does the new update solve the keyboard sensitivity issue??
zute333 said:
numerous guides and how to's in this forum and across XDA, as well as google.
download fastboot + adb > boot to download mode > flash twrp via fastboot commands > boot into twrp > flash zip.
There's obviously more to it than that, up to you to do the research.
Click to expand...
Click to collapse
i'm using this post as a minimalistic guide for myself (so i keep it up with my "discoveries" )
and ofc for been helped by everyone who wants to help me because i am completely new to android world cause this is my first android phone ever!
so.. let's get started!
i downloaded [TOOL] [WINDOWS] ADB, Fastboot and Drivers - 15 seconds ADB Installer v1.4.3
version 1.4.3 doesnt works for me so i downloaded the 1.3 as suggested and worked.
then i enabled the download mode following the procedure:
Turn off the phone, then press and hold the volume down key + the power key at the same time. This should boot you into download mode.
Click to expand...
Click to collapse
note: phone MUST be disconnected form pc to be turned off.
now..
*does install twrp invalidate warranty?
EDIT: answer is YES cause of
TWRP 2.8.5.0 YotaPhone 2 recovery image said:
Warning: It is currently not known how to re-lock the bootloader. This means you cannot completely undo the next step as of yet. This might have consequences for sending the device in for repairs, if they check for this, and deem it a (warranty) problem
Click to expand...
Click to collapse
*is installing TWRP a mandatory step?
EDIT: the answer is NO. it seems that the mandatory part is to unlock the bootloader (the bad part for the warranty.. and that can erase ur data..) and this can be done following this guide How to Install TWRP Recovery on YotaPhone 2 untill point 6 included - which i am reporting here for easy of use.
How to Install TWRP Recovery on YotaPhone 2 said:
How to Flash TWRP Recovery on YotaPhone 2
1 - Setup ADB and Fastboot on your Windows PC.
2 - Enable USB debugging from developer options on your YotaPhone 2.
3 - Connect it to PC with a USB cable, if it asks for debugging authorization, permit it.
4 - Go to the folder where you downloaded the TWRP recovery image from the download link above on your PC and open a command window inside that folder by doing “Shift + Right click” on any empty white space inside the folder, then select “Open command window here”.
5 - (Skip this if your bootloader is already unlocked) Now to unlock the bootloader, type in the following command:
└ Beware that unlocking the bootloader may wipe your phone’s data. Make sure to backup first before proceeding.
adb reboot bootloader
Click to expand...
Click to collapse
└ This will reboot your phone to bootloader mode
fastboot oem unlock
Click to expand...
Click to collapse
└ This will unlock bootloader on your device.
6 - Now if your phone has rebooted and is no longer in the bootloader mode, then boot it back into bootloader mode with the “adb reboot bootloader” command.
Click to expand...
Click to collapse
i already downloaded yotaflasher and the last RU firmware 5.0.0-RU1.1.99.zip
NOTE: Russian firmware seems to contain English language. i dont know how to change it later to the favorite one.
NOTE: you need to move the firmware files to the same location as the Flasher tool. Default one is C:\Program Files (x86)\yotaphone_flasher
i tryed to use yotaflasher right now while phone is in download mode and it says:
error: cannot open 'firmware/emnc_appsboot.mbn'
error: cannot open 'firmware/boot.img'
error: cannot open 'firmware/system.img'
error: cannot open 'firmware/recovery.img'
error: cannot open 'firmware/cache.img'
error: cannot open 'firmware/radio/NON-HLOS.bin'
error: cannot open 'firmware/radio/sbli.mbn'
error: cannot open 'firmware/radio/rpm.mbn'
error: cannot open 'firmware/radio/tz.mbn'
error: cannot open 'firmware/enmc_appsboots.mbn'
Would you like to flash userdata[Y/N]:
Click to expand...
Click to collapse
EDIT: placing the firmware in the right folder and unzipping ip let me flash my phone without using any bootloader. now i dont know why but is stucked showing android logo.
i dont know if this happened cause i used the last RU firmware on my stock 4.4.3 android or what..
what do i have to do?:crying::crying::crying:
tnx
Hello guys, I downloaded Lollipop from the ftp but installation fails: no MD5 file found!
I downloaded all russian versions and also the 1.6 EU version... but no way I always get this error.
I'm using TWRP 2.8.5, I guess the last one, and in the tutorials I see this version...
Does anyone know how to solve? :crying:
giocorrado said:
does nyone know how to flash the file zip into the phone?? i have no idea how it works and i dont find any infos
Click to expand...
Click to collapse
The info is described in various posts across the yotaphone forum. Are you rooted? If not then there also many many guides across the internet for that.
Not walking you through the whole process, sorry. We all had to learn, once you do it's all much easier.
It happens also to me...don't panic! press Volume up and the power button and when you enter in the bootloader select the downloading options, it will restart the phone with the "downloading" status
in the meanwhile with the yotaflasher select the option to downloads a firmware and try a different one. When the download is finished try to flash once again.
Melting Blaze said:
i already downloaded yotaflasher and the last RU firmware 5.0.0-RU1.1.99.zip
NOTE: Russian firmware seems to contain English language. i dont know how to change it later to the favorite one.
NOTE: you need to move the firmware files to the same location as the Flasher tool. Default one is C:\Program Files (x86)\yotaphone_flasher
i tryed to use yotaflasher right now while phone is in download mode and it says:
EDIT: placing the firmware in the right folder and unzipping ip let me flash my phone without using any bootloader. now i dont know why but is stucked showing android logo.
i dont know if this happened cause i used the last RU firmware on my stock 4.4.3 android or what..
what do i have to do?:crying::crying::crying:
tnx
Click to expand...
Click to collapse
I placed like you the rom downloaded through website in the firmware folder and flash got wrong. I was blocked on "powered by android" logo like you.
After this almost-bricking experience, I flashed 4.4.3 downloaded all through Flasher and phone was working again.
Then I tried to substitute 5.0 system.img in the folder downloaded through Flasher but no way... after flashing phone didn't boot.
I reflashed 4.4.3 back again and now is working.
I think that we can't put files in folder for Yota Flasher...
I cannot download last 5.0 EU version, like described here: http://forum.xda-developers.com/yot...ially-dead-t3312382/post65839167#post65839167
TKPL said:
I placed like you the rom downloaded through website in the firmware folder and flash got wrong. I was blocked on "powered by android" logo like you.
After this almost-bricking experience, I flashed 4.4.3 downloaded all through Flasher and phone was working again.
Then I tried to substitute 5.0 system.img in the folder downloaded through Flasher but no way... after flashing phone didn't boot.
I reflashed 4.4.3 back again and now is working.
I think that we can't put files in folder for Yota Flasher...
I cannot download last 5.0 EU version, like described here: http://forum.xda-developers.com/yot...ially-dead-t3312382/post65839167#post65839167
Click to expand...
Click to collapse
yeah i've done the same.
i founded the trick i hope
after my big mistake i have done this:
*i downloaded the last 4.4.3-S01-003-EU1.0.3.61a.zip then i flashed it. reminding to unzip it and put it in the right folder of the flasher. remind that this will delete ur data too prob.
*i checked for update on the phone in setting--> about phone --> sistem update
*it downloaded lollipop (android 5.0 Lollipop - 1Gb to download) :laugh:
*i took the 5.0.0-RU1.1.99.zip and flashed it
*u can choose english when the phone boot so dont worry about firmware to be RU
*i checked the firmware version doing the combo "Volume up and the power button" (press it while restarting)
*i changed the language of the phone in setting --> language (there is plenty of languages to choose. i choose mine, italian, but sometimes it happens to find something in english )
i downladed some app etc etc but i never used it for calls cause of the requested nano sim that i'm going to take tomorrow probably cause today i get stucked with trouble about my contacts.
hope to solve the problem for pass my contacts form my nokia N8 to yotaphone 2 quickly!
please let me know if it works for u too
JAMMANDROID said:
It happens also to me...don't panic! press Volume up and the power button and when you enter in the bootloader select the downloading options, it will restart the phone with the "downloading" status in the meanwhile with the yotaflasher select the option to downloads a firmware and try a different one. When the download is finished try to flash once again.
Click to expand...
Click to collapse
yeah. is exactly what i did, but super panicing like a chicken without head
Melting Blaze said:
yeah i've done the same.
i founded the trick i hope
after my big mistake i have done this:
*i downloaded the last 4.4.3-S01-003-EU1.0.3.61a.zip then i flashed it. reminding to unzip it and put it in the right folder of the flasher. remind that this will delete ur data too prob.
*i checked for update on the phone in setting--> about phone --> sistem update
*it downloaded lollipop (android 5.0 Lollipop - 1Gb to download) :laugh:
*i took the 5.0.0-RU1.1.99.zip and flashed it
*u can choose english when the phone boot so dont worry about firmware to be RU
*i checked the firmware version doing the combo "Volume up and the power button" (press it while restarting)
*i changed the language of the phone in setting --> language (there is plenty of languages to choose. i choose mine, italian, but sometimes it happens to find something in english )
i downladed some app etc etc but i never used it for calls cause of the requested nano sim that i'm going to take tomorrow probably cause today i get stucked with trouble about my contacts.
hope to solve the problem for pass my contacts form my nokia N8 to yotaphone 2 quickly!
please let me know if it works for u too
yeah. is exactly what i did, but super panicing like a chicken without head
Click to expand...
Click to collapse
I saw also an update this morning at home on wifi (I wait for the SIM too) because yesterday I flashed the 4.4.3-S01-003-EU1.0.51a: is not the 61 like yours and I received an update alert to 4.4.3-S01-003-EU1.0.3.56. I'm at work, I'll try this evening.
I haven't updated this morning because I was downloading a previous 5.0, the EU 1.44, but when flashing I had error "cannot load firmware/system.img". So I reflashed 4.4.3... I'll try again this evening
giocorrado said:
does nyone know how to flash the file zip into the phone?? i have no idea how it works and i dont find any infos
Click to expand...
Click to collapse
Hi, download YotaFlasher, it permits you to download and flash firmwares in an easy way, and you don't need to know any shell command
---------- Post added at 09:37 AM ---------- Previous post was at 09:25 AM ----------
giocorrado said:
does nyone know how to flash the file zip into the phone?? i have no idea how it works and i dont find any infos
Click to expand...
Click to collapse
TKPL said:
I saw also an update this morning at home on wifi (I wait for the SIM too) because yesterday I flashed the 4.4.3-S01-003-EU1.0.51a: is not the 61 like yours and I received an update alert to 4.4.3-S01-003-EU1.0.3.56. I'm at work, I'll try this evening.
I haven't updated this morning because I was downloading a previous 5.0, the EU 1.44, but when flashing I had error "cannot load firmware/system.img". So I reflashed 4.4.3... I'll try again this evening
Click to expand...
Click to collapse
Hello! I have 5.0!
After flashing and old version of 4.4.3 (my phone went with a 4.4.something branded Vodafone Italy, and they evidently don't give a fork about updates). With the 4.4.3 rev 1.0.51a I immediately received he update to 1.0.56a: I downloaded the 114MB, rebooted, and then got the update to 1.0.61a, around 63MB. I rebooted and then got finally the update to 5.0, 1GB :laugh:
I have only one problem now: the device doesn't recognize when I'm looking at the ink screen, and power button powers on the amoled... Even unlocking through swiping from bottom to top doesn't work. Option is correctly set, I tried to uncheck, reboot, wipe cache and check the option again but it not working well yet.
I have only one problem now: the device doesn't recognize when I'm looking at the ink screen, and power button powers on the amoled... Even unlocking through swiping from bottom to top doesn't work. Option is correctly set, I tried to uncheck, reboot, wipe cache and check the option again but it not working well yet.
Click to expand...
Click to collapse
seems that is the same for a lot of people if not everyone..
cause of this problem i am using this app gravity screen on/off.
it halves the problem cause now i have no problem for the amoled. and for problem i mean use the pwer button instead of simply swipe.
for the e-ink panel i still have to use the power button, only way it works.
I have bootloader unlocked, I downloaded nougat 7.0 firmware and tried to update manually, everything installs normally, but at the time of calling it says that the system is corrupted.
I already tried to put the boot and recovery of the version 7.0, already tried to put of the old, but always of the same thing, only version that works is previousor, someone knows how to do?
luizflb said:
I have bootloader unlocked, I downloaded nougat 7.0 firmware and tried to update manually, everything installs normally, but at the time of calling it says that the system is corrupted.
I already tried to put the boot and recovery of the version 7.0, already tried to put of the old, but always of the same thing, only version that works is previousor, someone knows how to do?
Click to expand...
Click to collapse
Whats the link for the manual download, ill experiment with it when i can update
Sm0k3r83 said:
Whats the link for the manual download, ill experiment with it when i can update
Click to expand...
Click to collapse
i used this link: http://dlcdnet.asus.com/pub/ASUS/Ze...ser.zip?_ga=1.245707268.1656347377.1488140054
Finished the update, all went well. Was a little laggy at first, so i cleaned the cache. Then rooted. Everything seems to be fine for me
same issue here. I can't update both with trwp and stock recovery. Originally my zenfone 3 was TIM SKU. Should be that the reason?
Hai.... someone could help me, I need recovery.image for asus ze520kl
zulfikarbugis said:
Hai.... someone could help me, I need recovery.image for asus ze520kl
Click to expand...
Click to collapse
mega.nz/#F!ok0V0RIA!5WKtHe98opzjVI3NPbM7Ww
Nobody knows a solution? I have tried to change the reocvery and the boot to the nougat version, and install the firmware manually, everything installs normally without errors, but when it connects it appears the following message "your device software can not be checked for corruption, Please lock the bootloader".
The cell phone is just that and I have to go back to the previous version!
I already took root, xposed and everything, and it always gives the same thing!
luizflb said:
Nobody knows a solution? I have tried to change the reocvery and the boot to the nougat version, and install the firmware manually, everything installs normally without errors, but when it connects it appears the following message "your device software can not be checked for corruption, Please lock the bootloader".
The cell phone is just that and I have to go back to the previous version!
I already took root, xposed and everything, and it always gives the same thing!
Click to expand...
Click to collapse
Same issue here =(
luizflb said:
Nobody knows a solution? I have tried to change the reocvery and the boot to the nougat version, and install the firmware manually, everything installs normally without errors, but when it connects it appears the following message "your device software can not be checked for corruption, Please lock the bootloader".
The cell phone is just that and I have to go back to the previous version!
I already took root, xposed and everything, and it always gives the same thing!
Click to expand...
Click to collapse
Updating thru TWRP results in an Error 7.
mxdxl said:
Updating thru TWRP results in an Error 7.
Click to expand...
Click to collapse
You did not understand, I installed the original recovery, both the last version of 6.0 and the version of 7.0, all install the update without error, but when it goes online does not work and I have to go back to the previous version
Raw firmware
I have the same issue. My phone was branded "tim italy". When i bought it, I flashed the WW version via asus flash tool, and I'm currently able to update till the last M version, which is the ......152.
If i try to update to Android N, my phone will not boot, giving me the corruption message and shutting down after 10 seconds. I also tried to perform the dm restore procedure; the dm error disappeared but the system is stuck on the Asus boot screen
I believe that the only solution is to flash a Nougat RAW firmware via asus Flash tool. Does Anyone have a download link for the N version ?
I have the same problem .. is there who can help?
`same problem can't update to nougat but my error is signature verification
hope someone can help us both
---------- Post added at 11:00 AM ---------- Previous post was at 10:48 AM ----------
Sm0k3r83 said:
Finished the update, all went well. Was a little laggy at first, so i cleaned the cache. Then rooted. Everything seems to be fine for me
Click to expand...
Click to collapse
Did you unlocked before updating?
same problem here....i downloaded the update and put it in internal storage...it automatically detected system update but when i try to update it it failed during installation....anyone help pls
mxdxl said:
Updating thru TWRP results in an Error 7.
Click to expand...
Click to collapse
if you want to update with twrp you must modify the update-script file placed in
UL-ASUS_Z012D-WW-14.2015.1701.8-user/META-INF/com/google/android
i have uploaded my one, if you can't modify the file you can download it and replace it in zip file
ExperienceTesla said:
if you want to update with twrp you must modify the update-script file placed in
UL-ASUS_Z012D-WW-14.2015.1701.8-user/META-INF/com/google/android
i have uploaded my one, if you can't modify the file you can download it and replace it in zip file
Click to expand...
Click to collapse
This works well? I have unlocked the bootloader and root my device. if this works for it?
zulfikarbugis said:
This works well? I have unlocked the bootloader and root my device. if this works for it?
Click to expand...
Click to collapse
The solution to the picture is Flash through the course
JadeKubPom said:
The solution to the picture is Flash through the course
Click to expand...
Click to collapse
I've done this but still fails. My phone will not boot, giving me the corruption message and shutting down after 10 seconds.
zulfikarbugis said:
I've done this but still fails. My phone will not boot, giving me the corruption message and shutting down after 10 seconds.
Click to expand...
Click to collapse
mine does the same even with the right update-script.
When i try to update using stock recovery i get failed signature message
Who has the Nokia 6 TA-1000, without the update function or some language lingo, IT'S FOR YOU !!!
Is this a full version of the firmware?
If I hold down both the volume up and down button, my device just keeps shutting off.
Trying to load it from bootloader mode the QFIL software says no Port Available.
I have not enabled USB debugging as I tried installing a zip of one of the updates and was not aware that my phone had been modded so now I cannot get into anything but recovery mode and bootloader mode.
aNorthernSoul said:
Is this a full version of the firmware?
If I hold down both the volume up and down button, my device just keeps shutting off.
Trying to load it from bootloader mode the QFIL software says no Port Available.
I have not enabled USB debugging as I tried installing a zip of one of the updates and was not aware that my phone had been modded so now I cannot get into anything but recovery mode and bootloader mode.
Click to expand...
Click to collapse
Yes, this is the full version of the firmware!
Read carefully § 4 - 9! And do as described!
I had the same problem with the phone as you do, but now everything works fine !!!
I will answer questions if that is not clear.
(I have English through an interpreter)
Evgeny_14 said:
Yes, this is the full version of the firmware!
Read carefully § 4 - 9! And do as described!
I had the same problem with the phone as you do, but now everything works fine !!!
I will answer questions if that is not clear.
(I have English through an interpreter)
Click to expand...
Click to collapse
Yeah, I got it figured out. It's sending to the phone now. Thanks!
---------- Post added 23rd July 2017 at 12:00 AM ---------- Previous post was 22nd July 2017 at 11:34 PM ----------
Thanks again! You saved my soft bricked phone. It is not seeing the July update. Should this rom be able to get new updates automatically?
I have a Nokia 6 TA-1000 Prototype Phone, but I need to backup it before flashing it.
Can I repost the firmware to Chinese forums like DOSPY?
Or, do you have any idea of how to backup the firmware? Or build a TWRP for Nokia 6 TA-1000? My Nokia 6 Prototype has an unlocked bootloader.
Evgeny_14 said:
Who has the Nokia 6 TA-1000, without the update function or some language lingo, IT'S FOR YOU !!!
In the firmware all languages are present, Android 7.1.1 with update function !!!
So:
1. Download firmware (all in one folder), kindly provided by CECT-SHOP.com
2. You need a cable (Flash Cabel),
I made it from the cable that came with the phone (it was not a pity).
It is important to do as in the picture!
3. Unzip the firmware!
4. Turn off the phone
5. Connect the cable to the phone, but do not connect to the computer!
6. IMPORTANT !!! While holding down the volume and volume keys -
Close the black and green wire connect to the computer
7. Hold down the + and - keys to separate the contacts but keep the keys squeezed !!!
8. run the QFIL program and select the files from the Nokia_6 folder, BUT KEYS + and - HOLD !!!
9. Press Download and hold the keys for 5 more seconds and release.
10.The firmware will begin.
After about 5 minutes you will see a blue line of the process, when the phone is flashed, you will hear the sound of rebooting the phone.
11. Everything is ready!
P.S. If you do not hold both the + and - keys at the same time, you will get an error in the firmware process.
Click to expand...
Click to collapse
Thanks! This solution works!
It will flash the firmware as 00CN_3_17B, the Android security patch level is updated till 1 May 2017.
The "System Updates" feature is there, thou it seems unable to get any updates.
Probably is a TA-1003 firmware, but it is very good, better than my phone is stuck at recovery mode.
A point of note, if your firmware downloading fails, it probably because you need to update the "HS-USB QDLoader 9008" driver to the Qualcomm ones.
Please try to upload firmware on google drive or some file hosting website
maroof.saeed said:
Please try to upload firmware on google drive or some file hosting website
Click to expand...
Click to collapse
Cerrected
FEE
:good:Flash cable...
Cut down black and green cable
am i right
koba420 said:
:good:Flash cable...
Cut down black and green cable
am i right
Click to expand...
Click to collapse
Yeah, I found just the green one was enough. It basically allows you to plug in the phone without it powering on, then you reconnect it where instructed and it powers on. It's what gets the phone into Emergency Download Mode so that the phone is ready, the correct drivers load and the flashing software can talk to the phone.
Updates still don't work though and manually installing one still soft bricked my phone and I had to flash it a second time.
aNorthernSoul said:
Yeah, I found just the green one was enough. It basically allows you to plug in the phone without it powering on, then you reconnect it where instructed and it powers on. It's what gets the phone into Emergency Download Mode so that the phone is ready, the correct drivers load and the flashing software can talk to the phone.
Updates still don't work though and manually installing one still soft bricked my phone and I had to flash it a second time.
Click to expand...
Click to collapse
Basically for updates, we must make sure our phone current firmware is exactly the same as indicated in the update.zip, check the version in the "metadata".
It sure fails when the update package detected that the phone firmware is different from the package requirement.
I have an update.zip but it requires to update from 00CN_3_17A, but my flashed firmware is 00CN_3_17B, can't use it hahaha :crying:
iammrwesley said:
Basically for updates, we must make sure our phone current firmware is exactly the same as indicated in the update.zip, check the version in the "metadata".
It sure fails when the update package detected that the phone firmware is different from the package requirement.
I have an update.zip but it requires to update from 00CN_3_17A, but my flashed firmware is 00CN_3_17B, can't use it hahaha :crying:
Click to expand...
Click to collapse
My firmware was 00CN_1_320 the phone did not work.
Now it's 00CN_3_17B and it works fine.
Evgeny_14 said:
My firmware was 00CN_1_320 the phone did not work.
Now it's 00CN_3_17B and it works fine.
Click to expand...
Click to collapse
That's what mine is. Are they getting updates automatically or manually installing successfully? Mind pointing me to the update you installed if manually?
iammrwesley said:
Basically for updates, we must make sure our phone current firmware is exactly the same as indicated in the update.zip, check the version in the "metadata".
It sure fails when the update package detected that the phone firmware is different from the package requirement.
I have an update.zip but it requires to update from 00CN_3_17A, but my flashed firmware is 00CN_3_17B, can't use it hahaha :crying:
Click to expand...
Click to collapse
According to this, I'd guess this is actually firmware for the TA-1003. That's what the B stands for. Sigh...
http://nokiamob.net/2017/05/06/may-...a-6-android-7-1-1-update-for-ta-1003-variant/
aNorthernSoul said:
According to this, I'd guess this is actually firmware for the TA-1003. That's what the B stands for. Sigh...
Click to expand...
Click to collapse
Sad to say, yes. V3.17B is the firmware for TA-1003 HK/Taiwan region, the next minor update around 150MB and there is no version number, hence I can't find the update.zip.
But really thanks the thread starter to provide the ROM, we have at least something to use. Meanwhile we just use along and see if anybody release the stock ROM for TA -1000
iammrwesley said:
Sad to say, yes. V3.17B is the firmware for TA-1003 HK/Taiwan region, the next minor update around 150MB and there is no version number, hence I can't find the update.zip.
But really thanks the thread starter to provide the ROM, we have at least something to use. Meanwhile we just use along and see if anybody release the stock ROM for TA -1000
Click to expand...
Click to collapse
Yup, totally agree on all counts.
I had wrote to CECT-shop.
They had only this ROM, and nothing else.
They seems unaware that this ROM is for TA-1003.
No luck with China forums either.
So the ones that have T-1000 with april modified rom donot flash this rom? or i guess we have to flash this rom so that we can get the google apps plus the updates too?
iammrwesley said:
Thanks! This solution works!
It will flash the firmware as 00CN_3_17B, the Android security patch level is updated till 1 May 2017.
The "System Updates" feature is there, thou it seems unable to get any updates.
Probably is a TA-1003 firmware, but it is very good, better than my phone is stuck at recovery mode.
A point of note, if your firmware downloading fails, it probably because you need to update the "HS-USB QDLoader 9008" driver to the Qualcomm ones.
Click to expand...
Click to collapse
iammrwesley said:
I had wrote to CECT-shop.
They had only this ROM, and nothing else.
They seems unaware that this ROM is for TA-1003.
No luck with China forums either.
Click to expand...
Click to collapse
Can you guide yourself better?
What is the picture follow? What does the cable do?
The volume hold button is also down.
My phone is TA-1000.
In Recovery mode are: Power button + volume up + cable connection, in logo Android 5s release volume button still hold power button.
The power button + decrease the volume + connect the cable, in the logo Android 5s release the volume down button to keep the power button then it to Download mode.
Can you help me....
maroof.saeed said:
So the ones that have T-1000 with april modified rom donot flash this rom? or i guess we have to flash this rom so that we can get the google apps plus the updates too?
Click to expand...
Click to collapse
Coz my phone was already soft bricked, so this thread is of a great help.
If your phone is without Google apps, pls go ahead.
But if your phone is already working fine, then DON'T. This ROM security update is only until May 2017, where in fact the actual update is already until July 2017.
Hello everyone, have been a long time
I have a VNS-L21 (P9 Lite 2016) from Colombia, it worked fine but I started to get more and more ads over the time so I decided to unlock the bootloader and root it, and I did it, after almost a year of working just fine, the phone start to restart by itself with no reason around 1 or 2 days per month, they were not scheduled or something.
Last night the phone started to restart by itself again, but this time after it turned on completely it went off some minutes later and started to restart several times without reason, I got frustrated so I decided to uninstall root (thought it was the problem) but the problem was still there, turn on and after some minutes it went off and restart.
Then I decided to check for updates and it had a pending update so I chose to install it but after restart, it won’t come on and kept in an endless boot loop.
Can anyone help me and tell me what to do? Thanks in advance...
fr4nk32 said:
Hello everyone, have been a long time
I have a VNS-L21 (P9 Lite 2016) from Colombia, it worked fine but I started to get more and more ads over the time so I decided to unlock the bootloader and root it, and I did it, after almost a year of working just fine, the phone start to restart by itself with no reason around 1 or 2 days per month, they were not scheduled or something.
Last night the phone started to restart by itself again, but this time after it turned on completely it went off some minutes later and started to restart several times without reason, I got frustrated so I decided to uninstall root (thought it was the problem) but the problem was still there, turn on and after some minutes it went off and restart.
Then I decided to check for updates and it had a pending update so I chose to install it but after restart, it won’t come on and kept in an endless boot loop.
Can anyone help me and tell me what to do? Thanks in advance...
Click to expand...
Click to collapse
Hello,
I bet that along with the root you also had a custom recovery.
So if before you install the update you have re-flashed the stock recovery, simply hold vol + and power button until it restarts in e-recovery mode. At this point make a factory reset and wipe cache.
Reboot system, done.
If instead you have not reinstalled the stock recovery, download one for the system you use (android 6 or 7) and install it via fastboot. ( you can download a rom the same version you use and extract recovery with extractor.
There are two recovery.img in the rom, just take recovery, NOT recovery2 ).
Try to reboot with vol + and power until you turn it on,
then factory reset in custom recovery.
Reboot in fastboot mode, install stock recovery, reboot system and launch again the update.
Happy holidays and good luck
Dadditz said:
Hello,
I bet that along with the root you also had a custom recovery.
So if before you install the update you have re-flashed the stock recovery, simply hold vol + and power button until it restarts in e-recovery mode. At this point make a factory reset and wipe cache.
Reboot system, done.
If instead you have not reinstalled the stock recovery, download one for the system you use (android 6 or 7) and install it via fastboot. ( you can download a rom the same version you use and extract recovery with extractor.
There are two recovery.img in the rom, just take recovery, NOT recovery2 ).
Try to reboot with vol + and power until you turn it on,
then factory reset in custom recovery.
Reboot in fastboot mode, install stock recovery, reboot system and launch again the update.
Happy holidays and good luck
Click to expand...
Click to collapse
Hello, thanks for answer
Yes, I still have the custom recovery and I was using nougat, where can I find an stock recovery for nougat? I wasn't able to use firmware finder (didn't understand how to use it).. does the recovery in rollback package works for this? just asking...
or can someone provide an stock rom compatible with my phone?
sorry for my bad engish and my little knowledge of all this, thanks in advance.
fr4nk32 said:
Hello, thanks for answer
Yes, I still have the custom recovery and I was using nougat, where can I find an stock recovery for nougat? I wasn't able to use firmware finder (didn't understand how to use it).. does the recovery in rollback package works for this? just asking...
or can someone provide an stock rom compatible with my phone?
sorry for my bad engish and my little knowledge of all this, thanks in advance.
Click to expand...
Click to collapse
No worries dude my english is very bad too......
So, you're in nougat L21, but what is your complete firmware ? (example L21C432B504)
Then download from official THREAD Firmware Finder for PC and unzip in a folder on your desktop.
Launch FF and go to COMMON BASE tab.
Type your complete firmware into search space and click on the search button...
Find FULL OTA MF firmware, tap on FILELIST tab, a pop up will appear...
Select the whole link of ONLY update.zip and copy/past into your browser for download...
Once downloaded, unzip to a folder on your desktop.
Download Huawei Update Extractor you find here on XDA...
Launch HUE and select UPDATE.APP you find into folder you just unzipped from upadate.zip...
Now you'll see two recovery, just select recovery.img and with mouse's* right key extract somewere on your desktop...
Done dude you have stock recovery....
Copy that .img recovery into your adb/fastboot folder (very important) and reboot in fastboot mode.
If you don't have adb/fastboot just download here from XDA..
From PC with terminal launch "fastboot flash recovery
(name.of.recovery).img" and recovery will be flashed.
Now you have stock recovery and can make stock ota update correctly.
Hope all will take right way, feel free to ask.
Good luck :fingers-crossed:
edit: * added
Dadditz said:
No worries dude my english is very bad too......
So, you're in nougat L21, but what is your complete firmware ? (example L21C432B504)
Then download from official THREAD Firmware Finder for PC and unzip in a folder on your desktop.
Launch FF and go to COMMON BASE tab.
Type your complete firmware into search space and click on the search button...
Find FULL OTA MF firmware, tap on FILELIST tab, a pop up will appear...
Select the whole link of ONLY update.zip and copy/past into your browser for download...
Once downloaded, unzip to a folder on your desktop.
Download Huawei Update Extractor you find here on XDA...
Launch HUE and select UPDATE.APP you find into folder you just unzipped from upadate.zip...
Now you'll see two recovery, just select recovery.img and with mouse's* right key extract somewere on your desktop...
Done dude you have stock recovery....
Copy that .img recovery into your adb/fastboot folder (very important) and reboot in fastboot mode.
If you don't have adb/fastboot just download here from XDA..
From PC with terminal launch "fastboot flash recovery.img" and recovery will be flashed.
Now you have stock recovery and can make stock ota update correctly.
Hope all will take right way, feel free to ask.
Good luck :fingers-crossed:
edit: * added
Click to expand...
Click to collapse
Hello again
thanks for your help, your guide is really useful
One more thing (excuse me for my little knowledge about this) I don't know what's the exact firmware for my phone, I mean I know it is VNS-L21 and should end B3xx but don't know which C... (I didn't check before the cellphone started to bootloop).
I search around the web and found some recommend the C432 one so I download the update.zip from it, would it have any problem if I flash the recovery from there?
And last thing, Can I flash recovery with P9 lite Toolkit? or just through adb? thanks in advance.
fr4nk32 said:
Hello again
thanks for your help, your guide is really useful
One more thing (excuse me for my little knowledge about this) I don't know what's the exact firmware for my phone, I mean I know it is VNS-L21 and should end B3xx but don't know which C... (I didn't check before the cellphone started to bootloop).
I search around the web and found some recommend the C432 one so I download the update.zip from it, would it have any problem if I flash the recovery from there?
And last thing, Can I flash recovery with P9 lite Toolkit? or just through adb? thanks in advance.
Click to expand...
Click to collapse
Dude at this step how can you tell you were on nougat ?
Is your device branded / unbranded one ?
I searched for Colombia firmware and L21 device don't exist, please check behind the cover,
it's wrote at the bottom. ( maybe L23 one ? )
Try to someway backup your stuff then
reboot with vol+ and power button to recovery, tap WIPE then SWIPE to factory reset.
If boot correctly see inside wich is your complete firmware.
C432 are for european area devices, teoratically should work, but will not risk...
Recovery.img can be easily be flashed with toolkit, i used it a lot of times...
Dadditz said:
Dude at this step how can you tell you were on nougat ?
Is your device branded / unbranded one ?
I searched for Colombia firmware and L21 device don't exist, please check behind the cover,
it's wrote at the bottom. ( maybe L23 one ? )
Try to someway backup your stuff then
reboot with vol+ and power button to recovery, tap WIPE then SWIPE to factory reset.
If boot correctly see inside wich is your complete firmware.
C432 are for european area devices, teoratically should work, but will not risk...
Recovery.img can be easily be flashed with toolkit, i used it a lot of times...
Click to expand...
Click to collapse
Hey dude
You really know about this, I'm sure because I updated the phone to Nougat before unlock and root it, time after an update came but I ignore it (I know it was a security updated not sure which one).
Yes, I just checked my phone in the backpart and it is L23, my bad, when you say branded it means if it is related to a phone/internet company? No, it is not tied to any company, I bought it free from internet.
I really don't care about backing up, if it starts from zero or is back to previous stage is fine for me since it can turn on and use it .
Cheers!
fr4nk32 said:
Hey dude
You really know about this, I'm sure because I updated the phone to Nougat before unlock and root it, time after an update came but I ignore it (I know it was a security updated not sure which one).
Yes, I just checked my phone in the backpart and it is L23, my bad, when you say branded it means if it is related to a phone/internet company? No, it is not tied to any company, I bought it free from internet.
I really don't care about backing up, if it starts from zero or is back to previous stage is fine for me since it can turn on and use it .
Cheers!
Click to expand...
Click to collapse
OK, since from first time i saw this post i thinked was a hardware problem, hope no....
You have to reboot to recovery holding vol+ and power button until a recovery will appear.
Then make a factory reset as already wrote in previous post.
Dadditz said:
OK, since from first time i saw this post i thinked was a hardware problem, hope no....
You have to reboot to recovery holding vol+ and power button until a recovery will appear.
Then make a factory reset as already wrote in previous post.
Click to expand...
Click to collapse
Hi there
Sorry for the late reply...
I managed to turn on the phone updating it through dload method (installing stock kernel and trying to update it with erecovery didn't work) without your help I wouldn't know how to to download the right firmware for my phone. Now, my phone is working "properly".
BUT my phone show a new update, when I tried to install it, it says "your device fail verification and may not work properly" and won't install the update, after that if I reboot the phone it will show your device... sign in red letters and won't turn on without choosing continue (when I was using custom kernel, it will show some letters in orange I think, but will turn on by itself without pressing continue) when I installed the firmware through dload I didn't see that message till I try to update the phone.
Thanks in advance and a very happy new year!.
fr4nk32 said:
Hi there
Sorry for the late reply...
I managed to turn on the phone updating it through dload method (installing stock kernel and trying to update it with erecovery didn't work) without your help I wouldn't know how to to download the right firmware for my phone. Now, my phone is working "properly".
BUT my phone show a new update, when I tried to install it, it says "your device fail verification and may not work properly" and won't install the update, after that if I reboot the phone it will show your device... sign in red letters and won't turn on without choosing continue (when I was using custom kernel, it will show some letters in orange I think, but will turn on by itself without pressing continue) when I installed the firmware through dload I didn't see that message till I try to update the phone.
Thanks in advance and a very happy new year!.
Click to expand...
Click to collapse
Dear forgive me, even for me English it's not my main language and maybe
i did not grab everything you posted. Did you use the dload method?
So you were on EMUI 4 / android 6, but now? If I understand correctly when you turn
on the device, see the red lines and press the power button to boot into the system?
If so, unlock again the bootloader.
If you want to post some screenshots so as to simplify ...
Best regards
Dadditz said:
Dear forgive me, even for me English it's not my main language and maybe
i did not grab everything you posted. Did you use the dload method?
So you were on EMUI 4 / android 6, but now? If I understand correctly when you turn
on the device, see the red lines and press the power button to boot into the system?
If so, unlock again the bootloader.
If you want to post some screenshots so as to simplify ...
Best regards
Click to expand...
Click to collapse
Hi there
I have been so busy these days, and I'm thinking in get another phone.
The red letters are still appearing, I cant install updates and it is driving me crazy.
Yes, i did use dloaad method and it turned on but after that it doesnt install the updates neither through dload method. I'm on EMUI 5, it says the bootloader is already unlocked
here are some pictures....
fr4nk32 said:
Hi there
I have been so busy these days, and I'm thinking in get another phone.
The red letters are still appearing, I cant install updates and it is driving me crazy.
Yes, i did use dloaad method and it turned on but after that it doesnt install the updates neither through dload method. I'm on EMUI 5, it says the bootloader is already unlocked
here are some pictures....
Click to expand...
Click to collapse
Hey dude,
Don't worry about replying soon or late,
we all have our personal stuff to do in our lifes...
You' ve been lucky you don't bricked your device using dload method
on your nougat/android 7 rom version.
This is allowed only to downgrade to a precedent android version (in your case android 6/Marshmallow...)
Even it says your bootloader is unlocked, it isn't, so backup your stuff and unlock it again.
Once unlocked, factory reset will start. When finished do wipe cache too...
Booting into the system will now show yellow (not red) lines and after a bit will automatically boot.
Will take some minutes... ( prepare a coffee )
Set up your phone and look forward for updates...
If all will take right direction, new update will completely lock the bootloader
and at the reboot no yellow or red lines will appears. :fingers-crossed:
Voilà, complete stock with latest firmware.
Take your coffee and enjoy :laugh:
Best regards
P.S.: Remove or obscure the screenshot with imei codes ( it's sensitive datas )
Dadditz said:
Hey dude,
Don't worry about replying soon or late,
we all have our personal stuff to do in our lifes...
You' ve been lucky you don't bricked your device using dload method
on your nougat/android 7 rom version.
This is allowed only to downgrade to a precedent android version (in your case android 6/Marshmallow...)
Even it says your bootloader is unlocked, it isn't, so backup your stuff and unlock it again.
Once unlocked, factory reset will start. When finished do wipe cache too...
Booting into the system will now show yellow (not red) lines and after a bit will automatically boot.
Will take some minutes... ( prepare a coffee )
Set up your phone and look forward for updates...
If all will take right direction, new update will completely lock the bootloader
and at the reboot no yellow or red lines will appears. :fingers-crossed:
Voilà, complete stock with latest firmware.
Take your coffee and enjoy :laugh:
Best regards
P.S.: Remove or obscure the screenshot with imei codes ( it's sensitive datas )
Click to expand...
Click to collapse
Hi there
Hey didn't know about the IMEI codes, already deleted the picture.
I did as you said and my phone is fully stock now (no red or yellow letters) and the ads are back ,anyway thank you so much for your patience and time for helping me out.
I really appreciated your help, take care and see you around. :victory:
fr4nk32 said:
Hi there
Hey didn't know about the IMEI codes, already deleted the picture.
I did as you said and my phone is fully stock now (no red or yellow letters) and the ads are back ,anyway thank you so much for your patience and time for helping me out.
I really appreciated your help, take care and see you around. :victory:
Click to expand...
Click to collapse
Ok i'm glad to see that worked..
I wish to thank in a special way Firmware Finder TEAM that with their
programs gave us the chance to solve many problems, THX guys. :good:
See you