Related
A friend has an S4 (i9505) from Vodafone Spain (ATL), unlocked and using another operator microSIM (Jazztel). Last week, via OTA, she received the latest update available: http://www.sammobile.com/firmwares/download/59777/I9505XXUHOJ4_I9505VFRHOF3_ATL/
After installing that OTA update, the signal level is very low, even none inside buildings, etc. This was not happening before.
In addition, the 2 soft keys (on both sides of the Home button) are not responding anymore, not even lighting up.
The Home button works, so... I think that it's not a hardware problem. Too much coincidence that the update and that hypothetical hardware problem happened at the same time...
First I did was a total hard reset, to factory settings, etc. No success, both problems (signal and soft keys) were still there.
Second, I flashed ROM manually via Odin. I flashed latest PHE one, so no Vodafone bloatware anymore: http://www.sammobile.com/firmwares/download/59311/I9505XXUHOJ2_I9505YXXHOJ1_PHE/
No success, still the same. I then did again a hard reset to factory setting, with Wipes first... and nothing.
Next thing I will do (when i have the phone in my hands again) is flashing with Odin the previous PHE one, and crossing fingers: http://www.sammobile.com/firmwares/download/48153/I9505XXUHOE3_I9505PHEHOE1_PHE/
Anyone with the same problem? Any solution/suggestion?
Flashed next-to-last Stock ROM for PHE http://www.sammobile.com/firmwares/download/48153/I9505XXUHOE3_I9505PHEHOE1_PHE/ and no success
Then I flashed Base HOH2 (4files+PIT) with Odin and... nothing either.
No idea what to try next. Suggestions?
Same here, after OTA no menu/back buttons (neither backlight or functionality)
Current status:
- seems to affect quite a lot of people, there are more threads like this on various sites
*e.g. here, here, here
- happenning after both OTA or ODIN based update to latest 5.0.1 ROM (for me it was i9505XXUHOJ2)
My findings so far:
- NO rom change seems to fix this
- it seems that touch keys' FW is updated (physically on the chip) along with the update (to version 0x12)
- Touch key FW update in menu *#2663# not applicable as it says that it won't update - versions are the same (you can check the version of driver used by ROM and the actual FW in chip on this page)
NOTE. my girlfriend has the buttons working after successful update and has both in version 0x12
Conclusion:
- It seems that the FW flashing process of the touch keys controllers somehow failed => phone says that it's also ver. 0x12 (same as android driver) but it is probably corrupted
- Re-flashing of the chip could solve the problems, however there are problems with this:
NOTES.
Menu *#2663# won't let us do the flash because of the version check - Can we use ADB to force the update on a rooted phone? Does anybody know how?
There is a slight chance, that it'll be fixed if Samsung will release some newer update which updates also the keys' FW
Samsung could release a fix, that will flash this manually as a lot of people have problem with this
!EDIT:
I've found very similar problem + solution on the Vietnamese forum bellow (don't use the files as it's for different phone!):
- to sum it up - force downgrading the FW, the update again... (any ROM cook that could help?)
see here
regards,
J.
I completely agree with you. I also tried the *#2663# path, the phone also has 0x12 touch keys FW, and it doesn't let me reflash it, either. Don't know what FW was there before the OTA update.
I have been told about the first German 5.0.1 stock ROM: http://www.sammobile.com/firmwares/download/44821/I9505XXUHOB7_I9505OXAHOB7_DBT/ and also about the last 4.4.2 one: http://www.sammobile.com/firmwares/download/40046/I9505XXUGNK4_I9505OXAGNK4_DBT/
Maybe one of those... makes something again on the Touch Keys FW?
I couldn't try anymore bcs I gave the phone back to my friend (with accesibility touch keys on-screen)
HI, have you found a solution? My Italian S4 suffered the same bug after the same upgrade. I tried to contact samsung and they said I need to replace the screen because upgrading the firmware put the electronic under stress and they got broken. I don't believe them because too many people have the same problem + my screen is two days old! Please help me!
Same problem for my S4! how we can flash/reflash/downgrade soft touch fw?
Has anyone tried the first first German 5.0.1 stock ROM: http://www.sammobile.com/firmwares/d...05OXAHOB7_DBT/ or the last 4.4.2 one: http://www.sammobile.com/firmwares/d...05OXAGNK4_DBT/ ?
A friend of mine (another one) told me that he fixed it with German HOA7 one, and then updated again to latest with no problem: https://mega.nz/#!VwcgXSQC!uGAhPxEuRrl-luS3sw8JmoPnjP4ybxrlsY4XcfFaWKE
I can't try it myself bcs I gave back the S4 to the owner. If anyone tries, please leave here the results!
oiluj said:
Has anyone tried the first first German 5.0.1 stock ROM: http://www.sammobile.com/firmwares/d...05OXAHOB7_DBT/ or the last 4.4.2 one: http://www.sammobile.com/firmwares/d...05OXAGNK4_DBT/ ?
A friend of mine (another one) told me that he fixed it with German HOA7 one, and then updated again to latest with no problem: https://mega.nz/#!VwcgXSQC!uGAhPxEuRrl-luS3sw8JmoPnjP4ybxrlsY4XcfFaWKE
I can't try it myself bcs I gave back the S4 to the owner. If anyone tries, please leave here the results!
Click to expand...
Click to collapse
I've tried a lot of ROMs - 4.4.2, also older 5.0.1 with no result...
I haven't tried UHOA7 I've tried UHOB7 instead, so I'll probably give it the shot, but I can't imagine how it could fix this issue (maybe if it for some reason has the touch-cypress FW update forced...)
- I've seen that on some German forums reverting back helped, but it wasn't my case (+it didn't fix the problem for many others...)
As I've wrote before, they've created modified kernel (with forced touch key FW reflash - bypassed version check) for a little bit different phone on the Vietnamese forum (see the link in my previous post) and it seems that it would be quite easy for somebody who has some knowledge with kernel compilation... (it would just need small modification in the "if" condition of 1 kernel source file) I've tried to do some research, but it takes some time to understand the process of building the kernel and to figure out how to properly pack it again... Also the sources are a little bit different for i9505.
kosmodisk said:
I've tried a lot of ROMs - 4.4.2, also older 5.0.1 with no result...
I haven't tried UHOA7 I've tried UHOB7 instead, so I'll probably give it the shot, but I can't imagine how it could fix this issue (maybe if it for some reason has the touch-cypress FW update forced...)
- I've seen that on some German forums reverting back helped, but it wasn't my case (+it didn't fix the problem for many others...)
As I've wrote before, they've created modified kernel (with forced touch key FW reflash - bypassed version check) for a little bit different phone on the Vietnamese forum (see the link in my previous post) and it seems that it would be quite easy for somebody who has some knowledge with kernel compilation... (it would just need small modification in the "if" condition of 1 kernel source file) I've tried to do some research, but it takes some time to understand the process of building the kernel and to figure out how to properly pack it again... Also the sources are a little bit different for i9505.
Click to expand...
Click to collapse
No idea, another friend of mine (different than the one who gave me her "broken" i9505 for fixing), who had the same problem with his own i9505 told me that with the I9505XXUHOA7_OXAHOA7 he fixed it. And sent me the Mega link, as it's not on SamMobile (or I didn't find it): https://mega.nz/#!VwcgXSQC!uGAhPxEuRrl-luS3sw8JmoPnjP4ybxrlsY4XcfFaWKE
I couldn't try it by myself, because I gave back the "broken" i9505 I was trying to fix to her owner before I was told about HOA7.
U know a lot more about this than me. Maybe you can give a try to that HOA7 Mega link, and see if it really works, or if my friend was extremely extremely lucky, and still doesn't know it (and ofc, doesn't know what the hell fixed his phone, and how).
Anyway, if u decide to give a try to the I9505XXUHOA7_OXAHOA7 one, don't forget to come back to tell us if it worked or... nothing. I keep fingers crossed!!!
Oh, and ofc: THANK YOU!!!
oiluj said:
No idea, another friend of mine (different than the one who gave me her "broken" i9505 for fixing), who had the same problem with his own i9505 told me that with the I9505XXUHOA7_OXAHOA7 he fixed it. And sent me the Mega link, as it's not on SamMobile (or I didn't find it): https://mega.nz/#!VwcgXSQC!uGAhPxEuRrl-luS3sw8JmoPnjP4ybxrlsY4XcfFaWKE
I couldn't try it by myself, because I gave back the "broken" i9505 I was trying to fix to her owner before I was told about HOA7.
U know a lot more about this than me. Maybe you can give a try to that HOA7 Mega link, and see if it really works, or if my friend was extremely extremely lucky, and still doesn't know it (and ofc, doesn't know what the hell fixed his phone, and how).
Anyway, if u decide to give a try to the I9505XXUHOA7_OXAHOA7 one, don't forget to come back to tell us if it worked or... nothing. I keep fingers crossed!!!
Oh, and ofc: THANK YOU!!!
Click to expand...
Click to collapse
I got the problem but only the back button was not working. Did factory reset and it did not help.
Then i flashed I9505XXUHOA7_OXAHOA7 from your link with Odin 3.10 and YES!!! i can confirm it is working again So happy now.
It is my Moms Phone now and she loves it!!. I was unly helping her doing the OTA so she realy hated me and SAM for F****** up her phone.
This tread realy saved my ass
Can confirm this is happening to me as well. All firmwares starting from HOF2 seem to have this problem so if you encounter this, downgrading to a HOE/HOD firmware should correct this bug. The downside is that without a proper fix, you won't be able to update.
BUBA0071 said:
I got the problem but only the back button was not working. Did factory reset and it did not help.
Then i flashed I9505XXUHOA7_OXAHOA7 from your link with Odin 3.10 and YES!!! i can confirm it is working again So happy now.
It is my Moms Phone now and she loves it!!. I was unly helping her doing the OTA so she realy hated me and SAM for F****** up her phone.
This tread realy saved my ass
Click to expand...
Click to collapse
@kosmodisk, did u read that? have u tried I9505XXUHOA7_OXAHOA7 by urself? Ur conclusions?
@BUBA0071:
- Did u look before (and after) flashing HOA7 which FW had (and have now) the touch keys? Remember: *#2663#
- After flashing HOA7, did u update again to latest one? Did the update work well this time, and now u have latest version with touch leys working?
MoLoCEL said:
Can confirm this is happening to me as well. All firmwares starting from HOF2 seem to have this problem so if you encounter this, downgrading to a HOE/HOD firmware should correct this bug. The downside is that without a proper fix, you won't be able to update.
Click to expand...
Click to collapse
I tried with a HOE1 one and... didn't work. Couldn't try one even older, but HOE1 seems to keep the same problem.
the file is corrupted when i try to extract it ? any other files that i can try ? im having the same problem right now with my s4.. have been looking for quiet some times now, and this is my only hope, hope this way will works smoothly...
wild081 said:
the file is corrupted when i try to extract it ? any other files that i can try ? im having the same problem right now with my s4.. have been looking for quiet some times now, and this is my only hope, hope this way will works smoothly...
Click to expand...
Click to collapse
download it again
@oiluj
HOE3 works for me. Problems start from HOF onwards.
I have also tried flashing HOA7 DBT and upgrading. Problem persists. My touchkey firmware is 0x1a and won't update no matter what Firmware package I tried. Up to now i have tried: GNG2, GNI2, GNK4, HOA7, HOB7, HOD7.
I'm pretty sure a rom (custom or early kitkat/lollipop leaks) caused this, altough I never flashed the initial chinese leak.
MoLoCEL said:
[MENTION=3170873]I'm pretty sure a rom (custom or early kitkat/lollipop leaks) caused this, altough I never flashed the initial chinese leak.
Click to expand...
Click to collapse
The phone that that girl gave to me, for fixing... was completely in official status. Always official ROMs, and official OTA updates, from first minute. And the problem was caused by latest official OTA update available: http://www.sammobile.com/firmwares/download/59777/I9505XXUHOJ4_I9505VFRHOF3_ATL/
So the problem was not caused by any custom ROM or a not official one.
oiluj said:
@kosmodisk, did u read that? have u tried I9505XXUHOA7_OXAHOA7 by urself? Ur conclusions?
@BUBA0071:
- Did u look before (and after) flashing HOA7 which FW had (and have now) the touch keys? Remember: *#2663#
- After flashing HOA7, did u update again to latest one? Did the update work well this time, and now u have latest version with touch leys working?
I tried with a HOE1 one and... didn't work. Couldn't try one even older, but HOE1 seems to keep the same problem.
Click to expand...
Click to collapse
Hardware key firmware 0X12 parth 0X1a (when it was not working, dont know if it have changed after german firmware flash). I have not updated again, think my CSC is blocking. It stayed on NEE after update to German firmware.
It was NEE I9505XXUPOJ2 firmware that F***** up my Phone
BUBA0071 said:
Hardware key firmware 0X12 parth 0X1a (when it was not working, dont know if it have changed after german firmware flash). I have not updated again, think my CSC is blocking. It stayed on NEE after update to German firmware.
It was NEE I9505XXUPOJ2 firmware that F***** up my Phone
Click to expand...
Click to collapse
unfortunately I've tried I9505XXUHOA7_OXAHOA7 with no luck (even with repartition when flashing) - the buttons still don't respond
BUBA0071, I'd like to ask which custom ROM have you tried? It seems that your keys have FW of version 0x1a which should be newer than 0x12, so this could lead to some sollution. Was it some cyanogen mod or MIUI?
thx
kosmodisk said:
unfortunately I've tried I9505XXUHOA7_OXAHOA7 with no luck (even with repartition when flashing) - the buttons still don't respond
BUBA0071, I'd like to ask which custom ROM have you tried? It seems that your keys have FW of version 0x1a which should be newer than 0x12, so this could lead to some sollution. Was it some cyanogen mod or MIUI?
thx
Click to expand...
Click to collapse
Wups it have been some time since it was custum, but in any cace it must have been some of the first lollipop roms. I gave to my mom 13 feb 2015 and i did a lot of flashing before that, i think one of the roms i tryed was Project Chaos. but also i tryed all the google editition roms for i9505 and cyanogen.
but when it whent back to stock it i used PDA I9505XXUHOD7 CSC I9505NEEHOD2 NEE firmware
I've got a question. When you flash the HOA7 file from the Mega link, do you use only the AP file, or you use AP,BL,CP, CSC and PIT files?
I'm gonna try to fix my S4 but i'm not sure about the right process I should follow.
Thank you!
I've been willing to change rom for a while now but after digging a little, I haven't found anyone with the same build number of mine.
Also it says my system is the latest version and I cannot update.
imad283 said:
I've been willing to change rom for a while now but after digging a little, I haven't found anyone with the same build number of mine.
Also it says my system is the latest version and I cannot update.
Click to expand...
Click to collapse
it strange that your system doesn't show any update. You should be on 232 now (android 6.0). YOu can try to manually flash the complete rom through sptool or update manually one by one using the inbuilt updater.
Read Here
http://www.techolite.com/35528/lenovo-k4-note-marshmallow-6-0-update-official.html
will this void my warranty?
and thanks a lot for the reply
imad283 said:
I've been willing to change rom for a while now but after digging a little, I haven't found anyone with the same build number of mine.
Also it says my system is the latest version and I cannot update.
Click to expand...
Click to collapse
Your ROM is intended for a specific Telco and more likely you will not receive any update unless your Telco will release the update. If you click system update it will always say it's the latest version. Same case with me here but I already updated to S232. Normally warranty will not be void if you flash using stock ROM. But if you unlock the bootloader the warranty will be void.
atomlife_074 said:
Your ROM is intended for a specific Telco and more likely you will not receive any update unless your Telco will release the update. If you click system update it will always say it's the latest version. Same case with me here but I already updated to S232. Normally warranty will not be void if you flash using stock ROM. But if you unlock the bootloader the warranty will be void.
Click to expand...
Click to collapse
Can you tell me how you updated it yourself, i'd like to do the same for my phone.
Also thanks a lot for the reply <3
I followed the instruction from this post.
[LP][MM] Lenovo K4 Note STOCK Roms (S152) (S232 volte) by anshubham
- Since it was my first time to flash K4 Note, I flashed it with S152 from S102 without unlocking bootloader to preserve the warranty. Of course the FW became generic instead of the original with operator name in it. After I got S152 , I updated it via OTA, a series of updates until I got S232. I hope this helps.
atomlife_074 said:
I followed the instruction from this post.
[LP][MM] Lenovo K4 Note STOCK Roms (S152) (S232 volte) by anshubham
- Since it was my first time to flash K4 Note, I flashed it with S152 from S102 without unlocking bootloader to preserve the warranty. Of course the FW became generic instead of the original with operator name in it. After I got S152 , I updated it via OTA, a series of updates until I got S232. I hope this helps.
Click to expand...
Click to collapse
I Did flashed it to S152 but it seems i've lost my IMEI, how can I get them back? if i update via ota will it be restored? help pls ;-;
Hello, i just receive my new phone with CN firmware ZTE_A2017V2.1.1B07. It come with international languages and google play installed so no OTA update available. Now, i don't want to take too many risk so i just want to be able to use my phone with nougat 7.1 and my question is can i directly install from recovery mode the B13 7.1 version or did i need 1st to install the full B09 and after OTA for B13, then reinstallation of googplay ? If i'm right every time i install a new full firmware i will have to reinstal googleplay ?
t7gc7 said:
Hello, i just receive my new phone with CN firmware ZTE_A2017V2.1.1B07. It come with international languages and google play installed so no OTA update available. Now, i don't want to take too many risk so i just want to be able to use my phone with nougat 7.1 and my question is can i directly install from recovery mode the B13 7.1 version or did i need 1st to install the full B09 and after OTA for B13, then reinstallation of googplay ? If i'm right every time i install a new full firmware i will have to reinstal googleplay ?
Click to expand...
Click to collapse
To install google play and make the phone works for your country, the seller must had messing around with your phone.
So before make any risk, you should unlock bootloader, then you can flash recovery and install A2017U or A2017G (depend on where you live). It have google service pre-install, english without chinese craps.
That could be my next step but i'm not really confident doing this right now (newbee). My concern is will my 2/3/4G work well with a A2017G on a CN phone, no modem or band problem ? Of coure that would be more simple because after i will be able to do all updates with OTA. Anybody can confirm that going from A2017 to A2017G work 100% ? Is there a guide A2017 (CN) to A2017G ? I see a lot of good informations here on xda but i don't want to brick my new phone . So if someone can provide me a step by step or a link with the full procedure that will help me a lot.
t7gc7 said:
That could be my next step but i'm not really confident doing this right now (newbee). My concern is will my 2/3/4G work well with a A2017G on a CN phone, no modem or band problem ? Of coure that would be more simple because after i will be able to do all updates with OTA. Anybody can confirm that going from A2017 to A2017G work 100% ? Is there a guide A2017 (CN) to A2017G ? I see a lot of good informations here on xda but i don't want to brick my new phone . So if someone can provide me a step by step or a link with the full procedure that will help me a lot.
Click to expand...
Click to collapse
I myself run A2016U on chinese model. Work fabulous (wifi, cellurar, mobile network) - as long as you flash right modem.
My phone is already unlock bootloader when seller gives it to me, and I do plenty things (even run into EDL only, but not dead still, chinese model rule!!).
Yes the key point is the modem ... I'm too newbee to make the sorcer apprentice ... I really need some help to do that right.
t7gc7 said:
Yes the key point is the modem ... I'm too newbee to make the sorcer apprentice ... I really need some help to do that right.
Click to expand...
Click to collapse
Okay I also ordered the same phone (A2017 China version) from AliExpress and the seller installed Google play and international language support. My phone came with B07 (same as yours).
Now read this really carefully, your phone is not stock, to install Google play and language support the seller messes around with the phone at the system level, so the phone will not receive OTA updates and will not flash OTA update files, the Chinese recovery is also useless. Any attempt to forcefully update the device will soft brick your phone.
You can keep running the B07 ROM but of you want to update you will have to unlock bootloader, root and install TWRP on your phone.
I have created a rar file with all the files you need to root and unlock bootlader:
https://ufile.io/980b3
Follow the instructions here:
Follow the instructions here.
https://forum.xda-developers.com/axon-7/how-to/newbies-guide-to-unlocking-rooting-axon-t3496234
Remember to run the backup program "axon7backup.exe" to backup your recovery and boot before rooting.
Also update twrp using fastboot once you have unlocked the bootloader.
After installing the latest twrp you can update to the latest nougat chinese build using this:
https://forum.xda-developers.com/axon-7/how-to/a2017-nougat-twrp-flashable-djkuz-t3571714
PM me if you have anymore questions
Thanks Vurio, doing like you said bring me to A2017 B13 Nougat 7.1 in chinese version right ? Is that preferable and more easier to do this than trying to go on A2017G ? I'm in Switzerland and the phone work great 2G/4G so i don't really need to be on G version. Just one more newbee question, every time i put a new firmware i will need to reinstall all my apps and of course Googplay ?
If I flash the u or g version on this phone. Are the LTE bands 20 unlocked like one the g version?
I have the Chinese version. All i done when i got it was flashed the full Chinese firmware and installed Google services and apps. I've been getting the ota updates and am now on 7.1.1. Which came ota Sunday. I did not need to root or anything.
I'm in uk.
Sent from my ZTE A2017 using Tapatalk
Thanks for your reply Alom5, difference with your situation is that they allready put googleplay and international language before sending the phone to me... I would love to be in your situation but it same that it's not the case ...
t7gc7 said:
Thanks Vurio, doing like you said bring me to A2017 B13 Nougat 7.1 in chinese version right ? Is that preferable and more easier to do this than trying to go on A2017G ? I'm in Switzerland and the phone work great 2G/4G so i don't really need to be on G version. Just one more newbee question, every time i put a new firmware i will need to reinstall all my apps and of course Googplay ?
Click to expand...
Click to collapse
Everytime you flash a new ROM, you need to wipe data, so yes you need to reinstall Google play and all your apps. But if you are rooted you can use titanium backup and that makes restoring apps really easy and quick.
About the firmware, axon 7 has 3 versions, Chinese, European and american. Each one comes with its own set of 4g bands and that cannot be changed no matter what you flash.
The Chinese and the american versions are most compatible with each other. You can use the American rom on the Chinese version but the changes will be aesthetic only. You will get rid of all the annoying Chinese text and apps and your phone will look and feel more "global". The modem of the phone will still remain Chinese so the bands won't change.
Ok so titanium is a must because we will have some new firmware this year ...
I'm not a newbie on computer thing but Android .... I discover it on my shield tv 2 monthes before ... I'm not scared to try but it's the fact to try and not to be sure 100% that work.
Your solution same to be the one but i see now that some (other) chinese seller propose A2017 CN version with A2017G installed ... How they do that ? Did they also flash the modem ?
I repeat i dont really need A2017G but i want to apply the most optimal option for my situation and when you don't really know what you do, it's not easy ... Also when you just pay some $$ to a brand new phone ...
t7gc7 said:
Ok so titanium is a must because we will have some new firmware this year ...
I'm not a newbie on computer thing but Android .... I discover it on my shield tv 2 monthes before ... I'm not scared to try but it's the fact to try and not to be sure 100% that work.
Your solution same to be the one but i see now that some (other) chinese seller propose A2017 CN version with A2017G installed ... How they do that ? Did they also flash the modem ?
I repeat i dont really need A2017G but i want to apply the most optimal option for my situation and when you don't really know what you do, it's not easy ... Also when you just pay some $$ to a brand new phone ...
Click to expand...
Click to collapse
The modem will not work. The modem will only work for the particular device. The seller on AliExpress never have the best reputation.
I am guessing that they would flash the European ROM but leave the modem Chinese. This is possible but European compatibility is not the best with Chinese version.
The american on the other hand has the best compatibility and even received updates faster. For eg. American version is on 7.1.1 whereas the European version is on 7.0.
And I completely agree with your sentiments on your new phone. One should always be careful and have complete information before messing around with a phone.
Also titanium backup only works on rooted phones. Titanium and adaway are the only reason that the first thing I do when I get a new phone is root it ??
t7gc7 said:
Thanks for your reply Alom5, difference with your situation is that they allready put googleplay and international language before sending the phone to me... I would love to be in your situation but it same that it's not the case ...
Click to expand...
Click to collapse
I bought mine from aliexpress. They done the same thing and put a note saying you shouldn't do anything... Or something to that effect. Trust me, your in exactly the same situation. There's a few threads on here from a few months ago. All you need to do is flash the stock firmware. Flag the Google apps and update them and away you go. Check the threads, I'm out so ain't got time to look but i think they were in the general section. Definately easy as pie. I've not had to write my phone since. Have had a couple of ota updates and no problems
Sent from my ZTE A2017 using Tapatalk
alom5 said:
I bought mine from aliexpress. They done the same thing and put a note saying you shouldn't do anything... Or something to that effect. Trust me, your in exactly the same situation. There's a few threads on here from a few months ago. All you need to do is flash the stock firmware. Flag the Google apps and update them and away you go. Check the threads, I'm out so ain't got time to look but i think they were in the general section. Definately easy as pie. I've not had to write my phone since. Have had a couple of ota updates and no problems
Click to expand...
Click to collapse
Did you flash the official firmware without rooting and installing TWRP?
Yes. I have never rooted the phone or installed any other recovery. Just flashed the firmware by having it on the internal sd card and update software.
Please read through the thread where this is discussed in detail and works easy before you start.
I followed info from that thread and it went fine.
Sent from my ZTE A2017 using Tapatalk
Ok alom5 you got my attention now. I'm really not in hurry f you can give me the thread (when you have some time) tomorow or later. This phone is so great, i will take my time to make the right think. Just to be clear you receive OTA after flashing ? So i need to flash the stock A2017 B07 ( i presume), then reinstall "properly" googplay and after i will receive all news OTA update ? Sound great ... Could be the easiest way for me ... When you flash back to stock and restart can you choice the language or are you only in chinese ?
I'm searching in the forum and if i see right i can directly flash the B13 version for SD ? http://www.zte.com.cn/china/sitecor...rt/detail?id=B4C0ACE418834F588FED0C72D6046C78 I'm downloading right now ... 9 hours remaining ...
This thread should help you.
https://forum.xda-developers.com/showthread.php?t=3487085
Sent from my ZTE A2017 using Tapatalk
Thanks alom5 ... I'm still downloading the ROM ... I will give feedback tomorow
Hi all,
I just recently went back to complete stock, from CM, as I want to hand it over to a friend.
I successfully switched back to C432B160 last week.
But still not a single update does show up, though that build is from November 2016.
It always tells me, that there are no updates. I am aware that Updates will show up with Hisuite, but shouldn't the stock updater present updates, too?
(I am not even talking about Nougat)
I already successfully tried a factory reset.
The only idee I have, is that I now have a DS oeminfo on an originally SS phone.
Does anyone have an idee, what might be wrong?
fireburner-de said:
Hi all,
I just recently went back to complete stock, from CM, as I want to hand it over to a friend.
I successfully switched back to C432B160 last week.
But still not a single update does show up, though that build is from November 2016.
It always tells me, that there are no updates. I am aware that Updates will show up with Hisuite, but shouldn't the stock updater present updates, too?
(I am not even talking about Nougat)
I already successfully tried a factory reset.
The only idee I have, is that I now have a DS oeminfo on an originally SS phone.
Does anyone have an idee, what might be wrong?
Click to expand...
Click to collapse
well, if you have ds oeminfo while your phone is ss, try flashing ss oeminfo and then the stock rom again
mjz2cool said:
well, if you have ds oeminfo while your phone is ss, try flashing ss oeminfo and then the stock rom again
Click to expand...
Click to collapse
Well the phone was SS at the beginning, but now I have oeminfo for DS and Stock Rom for DS (B160)
I wiped all and completely new flashed B160.
I did not setup any account (Google, Huawei), but only connected the phone to my WIFI.
Still neither Update nor HiCare show any available updates.
Does this need a SIM Card to be in the phone? Are there any other precautions?
I have no idea why it behaves like this.
edit: both frp and bootloader are locked according to the Bootloader Menu
I might add 2 weeks ago when coming from CM, there were no updates in update menu but HiCare, so I went fo Nougat. Nougat did not work properly, so I went back to B160 in order to start again, but since then, I never saw any update in menu, nor HiCare.
Might Huawei block DS Roms for IMEIS of originally SS phones?
Push, maybe @k1ll3r8e has an answer for me?
fireburner-de said:
Push, maybe @k1ll3r8e has an answer for me?
Click to expand...
Click to collapse
Heyho,
sounds really wired...
-
Here is what u can try,
1) bring the device back to stock (unrooted, loader closed)
2) do a factory reset and also the cache clear which is offered in the stock recovery
-
Start the device, do a dummy setup (only wlan is needed) check if the device offers an update. If not, well, try to manually update from C432B160 to C432B210 and check the update app again.
About this issue, i'm not sure, but maybe Huawei have a "downlaod limit" for an IMEI, that u can only download the update for example 10 times or so... I don't know^^ - I can only say, my device "L31 - Single-SIM - T-Mobile" modded to C432B380 dual-SIM have no issues with updates... I got since B130 every update via the normal update app. - But i also know that the updates will be released in waves, i don't know how they exclude/include devices in such an wave. But maybe, u have an oeminfo from an device which wasn't in the "current wave list". - As already mentioned i don't know how they manage those waves or what the trigger is...
Hope i could help u a bit
Regards
Sebastian
fireburner-de said:
I wiped all and completely new flashed B160.
I did not setup any account (Google, Huawei), but only connected the phone to my WIFI.
Still neither Update nor HiCare show any available updates.
Does this need a SIM Card to be in the phone? Are there any other precautions?
I have no idea why it behaves like this.
edit: both frp and bootloader are locked according to the Bootloader Menu
I might add 2 weeks ago when coming from CM, there were no updates in update menu but HiCare, so I went fo Nougat. Nougat did not work properly, so I went back to B160 in order to start again, but since then, I never saw any update in menu, nor HiCare.
Might Huawei block DS Roms for IMEIS of originally SS phones?
Click to expand...
Click to collapse
So, did you try upgrade on N using Firmware finder?
If not, try it and you will see if your device in black list. I also use DS firmware for SS model and just last night I upgraded normaly from B160 to B370 Ota, and after that to B380 Ota.
@k1ll3r8e
Yes it already is a dummy setup. I will manually upgrade to B210 and try again, Thanks alot! @Alexxxx1
Firmware Finder is the Windows tool, isn't it? If above progress won't work I might boot my Windows partition and check on that.
Is there by chance any other way to check if the device is somehow blacklisted?
@all
Would Huawei push the updates to my device, if I would contact them? (I ask because of the altered oeminfo. Or would the refuse support in that case, which is what I guess)
edit: Does by chance anyone have a link to the C432B210 ROM?
fireburner-de said:
@k1ll3r8e
Yes it already is a dummy setup. I will manually upgrade to B210 and try again, Thanks alot! @Alexxxx1
Firmware Finder is the Windows tool, isn't it? If above progress won't work I might boot my Windows partition and check on that.
Is there by chance any other way to check if the device is somehow blacklisted?
@all
Would Huawei push the updates to my device, if I would contact them? (I ask because of the altered oeminfo. Or would the refuse support in that case, which is what I guess)
edit: Does by chance anyone have a link to the C432B210 ROM?
Click to expand...
Click to collapse
Heyho,
if u have an L31, go to my FTP (oeminfo) and go a few folders back, then u'll find a Huawei folder there are several versions stored.
Edit:
Here is the link (just back on my PC)
Regards,
Sebastian
Sent from my HUAWEI VNS-L31 using XDA Labs
Firmware finder is android app. You can find it in google play store as a free tool for upgrade huawei devices. In Ffinder you will find option for checking autorization of official firmware for your device, is it allowed or not for your device.
Regards
I did flash B210, but no Updates withiin 1 day. (I think time was to short)
I then flashed B370 Full-PV via Firmware Finder.
B380 should come automatically sometime, hopefully.
I think its time to hand it over to my friend now.
Only thing I am curious about is:
settings -> about phone -> certification: Serbia
I guess this is normal for C432?
Only thing I am curious about is:
settings -> about phone -> certification: Serbia
I guess this is normal for C432?
Click to expand...
Click to collapse
Yes, its normally for C432 if device was purchased in Serbia
Alexxxx1 said:
Yes, its normally for C432 if device was purchased in Serbia
Click to expand...
Click to collapse
It was bought from T-Mobile in Germany. But well.
fireburner-de said:
It was bought from T-Mobile in Germany. But well.
Click to expand...
Click to collapse
No worries about that
I bought mine also from T-Mobile DE, and mine shows also "Serbia"... I searched a bit for similar issues and it seems that also the P8 with C432 is for "Serbia" at least a unknown amount of it, sooo i think it comes from the "ROM" not from the device. Maybe they only certify the ROM for a "law based standart" to "Serbia". - Who knows...^^
Regards,
Sebastian
good day everyone,
Please forgive me for asking this about the VNS-L23. I know there are tons on similar issues on the forum, I've been reading but non specific to my model. I also know that some of the solutions may work on the VNS-L23 variant as well but, I'm swamped and a bit confused. Can someone please assist in helping me restore the VNS-L23 back to stock OR the latest OS/firmware that is available?
I tried flashing a Nougat firmware, flash was successful but, when phone rebooted it would not go past the Huawei eRecovery, no matter what i try.
I tried flashing other VNS-L23 firmwares via 3 button method...no success
I tried 'Download latest version and recovery'...no success
I am able to get into Fastboot mode.
I tried to flash TWRP...i was unsuccessful (ADB did recognize device).....on FASTBOOT screen i see Phone: Locked FRP: unlocked...failed...command not allowed (i think)
I tried to use DC unlock-er to make some headway, of course i have to make a purchase costing 15 pounds. I always support these things but, i do not want to purchase and it still does not work.
According to DC unocker's detection:
Firmware: VNS-L23C605B120
FB LockState: Locked
USER LockState: Locked
You guys are awesome here and i know I'll get back my device to work....Please, I just bought it, not even 2 days and i cant even use it now because of this issue.
Many thanks in advance....Ronald
Is this the 2016 or 2017 model?
2016
Use the dload method to restore stock firmware (use a external sdcard for this) then you will be able to unlock bootloader flash twrp and whatever u want ect...ect... If you have no idea what I'm on about just reply or priv msg me.
Exiatron00 said:
Use the dload method to restore stock firmware (use a external sdcard for this) then you will be able to unlock bootloader flash twrp and whatever u want ect...ect... If you have no idea what I'm on about just reply or priv msg me.[/QUOTE
thank you....I've tried that too, with many firmwares.. all has failed. Even if it says VNS-L23, still it fails. I have a firmware now that was paid for, I tried the forced update and it keeps saying package not found.
can you assist me please?
if you have telegram we can converse better there...+18683527996
Click to expand...
Click to collapse
Exiatron00 said:
Use the dload method to restore stock firmware (use a external sdcard for this) then you will be able to unlock bootloader flash twrp and whatever u want ect...ect... If you have no idea what I'm on about just reply or priv msg me.
Click to expand...
Click to collapse
wich files did you use?
@grymmy @arturohergo
Hey guys did you solve your issues ?
Tell me if not, maybe i can help.
Cheers
Dadditz said:
@grymmy @arturohergo
Hey guys did you solve your issues ?
Tell me if not, maybe i can help.
Cheers
Click to expand...
Click to collapse
I just wanna known wich files i have to use for make a rollback
Guys...I tried and tried and tried. Was most frustrating so I resorted to someone from Pakistan with software and programs to bring my P9 lite back to life. If you guys want I can put you on to the person. Or, if we can sort it out here then better because, of course it comes with a small fee to restore my device back to normal but I was desperate. I will say though, I didn't regretted it.
arturohergo said:
I just wanna known wich files i have to use for make a rollback
Click to expand...
Click to collapse
Hi dude, ok, if you tell device version and exact stock firmware
a little possibility to find some rollback package still exist.
But what are exactly your issue ?
Maybe you don't need rollback files...
Can you boot to system ?
Cheers
Dadditz said:
Hi dude, ok, if you tell device version and exact stock firmware
a little possibility to find some rollback package still exist.
But what are exactly your issue ?
Maybe you don't need rollback files...
Can you boot to system ?
Cheers
Click to expand...
Click to collapse
My version is vns-L23C212B336
I have two problems:
1. When I'm on horizontal (for example whatching a vodeo in YouTube, or playing in a game) the screen rotates itself, and the comeback, even when the autorotate is off.
2. When I'm going to type something the keyboard hides itself and I have to open it again.
And that's all, I hope you can help me.
By the way, I have tried to make a factory reset but it didn't work.
arturohergo said:
I just wanna known wich files i have to use for make a rollback
Click to expand...
Click to collapse
Well, looking onto the UNIFIED HELP THREAD, in post #6
there is "UNBRICKING AND DOWNGRADING FROM EMUI 5" section.
Here are some rollback packages but not for L23...
You need that package and need the full ota L23C212B130 firmware
from which extract update.app.
I don't know how to grab those files. I've searched with
Firmware Finder but B130 full ota isn't there...
So, go to next step...
arturohergo said:
My version is vns-L23C212B336
I have two problems:
1. When I'm on horizontal (for example whatching a vodeo in YouTube, or playing in a game) the screen rotates itself, and the comeback, even when the autorotate is off.
2. When I'm going to type something the keyboard hides itself and I have to open it again.
And that's all, I hope you can help me.
By the way, I have tried to make a factory reset but it didn't work.
Click to expand...
Click to collapse
B336 seems to be the latest firmware and no update are available.
If you want play a bit with your device you should consider
a rebrand but it is a bit difficult to find correct L23oeminfo file and firmware.
Maybe it can be converted to L21 or L31 version but never tried, i won't risk..
Some payed services should exist to assist you...
That's all dude, feel free to ask.
Cheers
edit: modified the link to UHT thread.
well, i think i will resign.
Thanks for your help anyway.
grymmy said:
Guys...I tried and tried and tried. Was most frustrating so I resorted to someone from Pakistan with software and programs to bring my P9 lite back to life. If you guys want I can put you on to the person. Or, if we can sort it out here then better because, of course it comes with a small fee to restore my device back to normal but I was desperate. I will say though, I didn't regretted it.
Click to expand...
Click to collapse
Hi, I have the same problem with my Vns l23, could you tell me what firmware did you use to fix it?