Related
Hi all, I'm quite new to this forum and I hope I dont break any netiquette with my question.
Now I have a N1 I bought on ebay, used, rooted and perfectly functioning.
I don't remember how, but I was able to update it to FRG83D downloading the rom, renaming it, copying on my sdcard etc ...
Now ...
I can't update to FRG83D.
I understood that having a rooted N1 NO OTA UPDATE shall ever work for me, not the manual update is available.
I was able to skip the "no signature verification" error suing clockwork mod, but i can't install the patch anyway, the system alway replies "assert failed: apply_patch_ckeck (" stystem app accountandsyncsetting . apk" ... then a serie of letters and number follows.
I know nothing about this, I must confess, but my suspect is that the update fails because something doesn't match between the update and the ROM which is working on my N1 (which is by the way the original one build frg83d
baseband version
32.36.00.28U_4.06.00.12_7
kernel
2.6.32.9-27240-gbca5320 android-build apa26 #1
Any sugestion ?
I mean and idea about where I can download a FRG83D version suitable for my phone ?
If you just want stock with very little tweaks, may i suggest Geo's Rom. It's basically the latest stock rom w/ superuser, busybox, trackball alert etc. Runs amazing too =)
As for breaking any netiquette, you're suppose to post this in the questions forum not the general. Have fun with your phone.
worked!
Thanks Mokurex!
It worked.
It's unbelievable.
I spent three nights in search of an answer, and then you solved it in few seconds.
I'm new to Android, and I must confess that I'm quite disoriented.
There hare hundred of versions, produced by individuals, companies, etc ... The one I used, I mean the one you suggested me, seems to be the fruit of an individual's work in the US.
It's ok to me, sounds and works good.
But It's not the original one, I mean the one released by ... Google ? or ... what ?
It doesn't matter, but I just want to say that it would be easier for us all, newbies, to have some clear guidelines on this, an online guide for dummies, something or somebody who would explain us the difference between a odexed or deodexed versions, what are the pro and cons of rooting a N1, the fact that rooted phones loose the OTA update (which is very VERY painful for us newbies, etc ...).
I understand that we can rely of forums and on kind people like you, but having some clear cut guidelines would be very useful.
... and looking at the future ... I guess I'll have the same problems when I'll have to update to Gingerbread.
I's very frustrating to search the web for a suitable ROM for your phone ...
stefanopelloni said:
[snip]
But It's not the original one, I mean the one released by ... Google ? or ... what ?
Click to expand...
Click to collapse
No, it's not the original. That one is deodexed, so any future OTA updates will not work (as Google's stock ROMs and updates and not de-odexed). You will have to wait until someone repacks the update, then apply it.
stefanopelloni said:
[snip]
It doesn't matter, but I just want to say that it would be easier for us all, newbies, to have some clear guidelines on this, an online guide for dummies, something or somebody who would explain us the difference between a odexed or deodexed versions, what are the pro and cons of rooting a N1,
Click to expand...
Click to collapse
Did you read the wiki? There are lots of posts/threads/guides available.
stefanopelloni said:
[snip]
the fact that rooted phones loose the OTA update (which is very VERY painful for us newbies, etc ...).
Click to expand...
Click to collapse
What are you trying to say? Phones running a rooted, but otherwise stock ROM will certainly received the OTA updates. Now if you use a non-stock ROM, you may or may not receive the OTA update. But whether you receive it or not, you will not be able to apply it as is, until someone repacks it (unless you are using the stock ROM, rooted or not).
I believe you have to use the stock recovery as well if you wanted to update via OTA.
If you want to get Gingerbread by way of OTA, then revert to stock rom and recovery. Everything you need is in the sticked thread in the development section.
Mokurex said:
I believe you have to use the stock recovery as well if you wanted to update via OTA.
[snip]
Click to expand...
Click to collapse
No, you do not. You just need a newer version of Amon_RA (1.9+) or CWM.
Thank you for the correction.
Efrant, Mokurex,
perhaps it's my problem.
My original plan was to restore my phone is a status capable of receiving OTA updates. Considering that I'm not an IT expert it would be easier for me ho have such a phone.
Wandering on the web, I discovered that rooted phones are not eligible for OTA updates.
And most important of all, I'm not eligible to manually update is as well using the patches on the net (signature verification errors ... and many others seen above).
Mokurex helped me a lot (actually, solved my problem by now) suggesting that version of the ROM (I mean Geo's one) but it's the fruit of a work of an individual. I'm very grateful to him as well, but who knows about the future. Will Geo provide a similar version of Gingerbread as well ? Because without him I can't upgrade.
Efrant, got your remark.
I have CWM, latest version, I also bought the premium version (in oder to show to the programmer of it my appreciation) but in my case it just doesn't work.
With it, I can bypass the signature issue, but then I got stuck at assert failed: apply_patch_ckeck (" stystem app accountandsyncsetting . apk
Oh, by the way, I also tried to go back to ERE27 or something like that (unrooted version etc ...) but the mobile just doesn't work at all ...
I understood that the only way to unroot my phone (actually, any phone) and qualify for the OTA is via SDK.
... but I'm afraid it's just a bridge too far for my poor knowledge.
Geo has been quick to update his rom to the newest version. To upgrade to gingerbread, i'd assume that it would be like flashing any other custom rom, but there might be a bit more steps involved.
If you want completely stock, no root whatsoever, go here.
stefanopelloni said:
[snip]
Wandering on the web, I discovered that rooted phones are not eligible for OTA updates.
And most important of all, I'm not eligible to manually update is as well using the patches on the net (signature verification errors ... and many others seen above).
Click to expand...
Click to collapse
I said it before, and I'll say it again: rooting has no bearing on the phone's ability to receive and install OTA updates -- what matters is which ROM you have. I rooted my phone when I bought it, and it had Eclair on it. I have received EVERY OTA update without any problem.
stefanopelloni said:
[snip]
Efrant, got your remark.
I have CWM, latest version, I also bought the premium version (in oder to show to the programmer of it my appreciation) but in my case it just doesn't work.
With it, I can bypass the signature issue, but then I got stuck at assert failed: apply_patch_ckeck (" stystem app accountandsyncsetting . apk
Click to expand...
Click to collapse
That is probably because you were not using a stock ROM...
stefanopelloni said:
Oh, by the way, I also tried to go back to ERE27 or something like that (unrooted version etc ...) but the mobile just doesn't work at all ...
I understood that the only way to unroot my phone (actually, any phone) and qualify for the OTA is via SDK.
... but I'm afraid it's just a bridge too far for my poor knowledge.
Click to expand...
Click to collapse
If you want a stock ROM, you can go here: http://developer.htc.com and download a Nexus One image to your sdcard, rename it to PASSIMG.zip and boot the phone into bootloader (by holding the trackball and powering up the phone). It should automatically detect the file and allow you to flash it.
Files from the site are official. If you get them from anywhere else, you can't really know what's been modified.
Dear Efrant,
if you were a girl, and in Italy, I would probably kiss you.
Now I have a bright-clear picture of the situation.
During the next holiday, I'll try and flash a stock version of the OS and then try the OTA update.
By now, the version mokurex suggested me work brilliantly and after so many nights wasted in a desperate search of an answer my myself i'm going to have a break.
... but thanks a lot. thanks indeed !!!
Sorry to disturb you again Eftant.
The fact is that today decided eventually to follow your step, but encountered another unexpected problem.
downolaed the original HTC rom - done
renamed it passimg.zip - done
turned on the N1 pressing trackball - done
expected detection of PASSIMG.zip - done
opening passimg.zip - done
checking passimg.zip - done
and then .. nothing
once the N1 load the passimg.zip file (i notice it from a loading bar on the upper right conder of the phone) it just allow me to
1)run bootloader agan
2) lock sim
3) restore something ...
... and that !
No possibility to "flash" rom as you wrote.
Did I miss anything ?
I see from the web that a lot of people bring back the N1 to the stock image using SDK from PC (MAC in my case) but the steps are not so clear considering the fact that I'm not that comfortable with the shell and the Android SDK is not intuitive (... to me).
Thanks in any case for your attention!
Try wiping your device then download the FRF91 image from the same site, rename it to PASSIMG.zip and save it to the root of your sdcard. Put your sdcard back into your device, and boot into the bootloader (by holding down the trackball as you push the power button). Once it flashes, wait for the OTA to FRG83G. Some users have said that the later images don't work using, particularly if you have updated to the 0.35 version of the bootloader.
So I've searched for a answer but nothing worked.
I have the ALE-L21 model, and it bootloop-ed when I was trying to root the phone.
I've tried to put an update from the sd card by pressing volume up and down + power button and it just said failed from the start.
I've tried entering fastboot mode and flashing boot.img, recovery.img, but i it didn't worked.
Sorry for the bad english, please help me.
first off all...
Whe need al little more information.
dual/single sim?
What build number are you on?
Did you unlock your bootloader? (i think that's your problem)
do you have a goldfish?
If you can answer these questions we can help you
Hi! I have same issue with my P8 Lite single sim from Vodafone. Before i went into bootloop i had B181 branded software.
My bootloader is locked (how i can get unlock code when emui site is down?). Is there any way to rescue my phone without unlocking bootloader?
Maybe it will be possible to flash (vol+,vol-,power) it once again with vodafone rom, but i can't find it anywhere.
Thanks for support.
benjiamin said:
Hi! I have same issue with my P8 Lite single sim from Vodafone. Before i went into bootloop i had B181 branded software.
My bootloader is locked (how i can get unlock code when emui site is down?). Is there any way to rescue my phone without unlocking bootloader?
Maybe it will be possible to flash (vol+,vol-,power) it once again with vodafone rom, but i can't find it anywhere.
Thanks for support.
Click to expand...
Click to collapse
Is the site down again?as far as i can tell it's online https://emui.huawei.com/en/plugin.php?id=unlock&mod=detail
you can't flash anything with bootlaoder locked. don't try it.
just unlock your boatloader after that's done come back
the first step is online but at next step i have "We're sorry but the server is busy.." since yesterday
benjiamin said:
the first step is online but at next step i have "We're sorry but the server is busy.." since yesterday
Click to expand...
Click to collapse
try this one http://huaweip8lite.blogspot.be/2016/03/bootloader-huawei-p8-lite-14-huawei.html
i don't know if it's works but its from one of our best developers Sokkoban
hint use google translate.
websit site is online again, bootloader unlocked what are next steps ?
Edit: ok i've used P8-lite multitool and phone is back but i do not have imei number and in software version i have "balongc50b311" how to fix it now?
benjiamin said:
websit site is online again, bootloader unlocked what are next steps ?
Edit: ok i've used P8-lite multitool and phone is back but i do not have imei number and in software version i have "balongc50b311" how to fix it now?
Click to expand...
Click to collapse
Oh you got the balong bug that's beautiful...
before i can give you antyhing i must know what version did you updated to?
Lordbannakaffalatta said:
Oh you got the balong bug that's beautiful...
before i can give you antyhing i must know what version did you updated to?
Click to expand...
Click to collapse
I'm not 100% sure now but it should be ALE-L21C432B133_Europe Channel_single Software from official huawei site
In that build there should be a floder named vendor with an small update.app in it. put that one in your sdcard/internal memory and go trough settings-> updater-> menu-> local update and select that. let it do and everything should be fine
Lordbannakaffalatta said:
In that build there should be a floder named vendor with an small update.app in it. put that one in your sdcard/internal memory and go trough settings-> updater-> menu-> local update and select that. let it do and everything should be fine
Click to expand...
Click to collapse
Everything works, thank you so much but it seems that this ROM is bit laggy and when I'm tryning to delete some ****ty games it's restarting and games remain.
Can i update it now to Android 6.0? Will it be possible via OTA? Right now i have info that my current version is latest one.
benjiamin said:
Everything works, thank you so much but it seems that this ROM is bit laggy and when I'm tryning to delete some ****ty games it's restarting and games remain.
Can i update it now to Android 6.0? Will it be possible via OTA? Right now i have info that my current version is latest one.
Click to expand...
Click to collapse
you have to update manually if you want MM i will post a link with descriptions once i uploaded that. (seriouslt i typed this like a 1000 times)
here you go http://forum.xda-developers.com/p8lite/general/mega-thread-root-unbricking-updating-t3400994
SO...
I went through and followed the instructions word for word of the gentleman in this link:
http://forum.xda-developers.com/p8lite/general/mega-thread-root-unbricking-updating-t3400994
My current Phone info is:
Model- hi6210sft
Build Number ALE-L21C432B551
EMUI-4.0
Android Version-6.0
Now my problem is that in order to make any progress in installing 6.0, I had to install an earlier build as it states in the link above. Now the link I selected for the earlier build number was for single-sim yet for whatever reason my phone is now telling me that I have two sim slots. Which is cool, I don't mind that. My phone has 1 Sim slot an 1 SD slot so thankfully this build didn't mess with my SD slot. Now it was said that downgrading would be followed with an OTA update, however I was not actually able to access an OTA update and the Balong glitch came up with the next upgrade I think. Everything I have done so far has been manual and I am worried that something may be wrong with that. Even now when I check for OTA's it states that no updates are available and yet higher build numbers are available. On top of all this, my region is New Zealand and the region of the current build I'm using is for Europe I believe. Will that be causing any problems? Lack of OTA support? Glitches in general (I have had a few of those with this build of MM, multiple messenger and/or contacts app icons appearing on home screen, themes glitching out and doubling up in the theme store under my downloaded themes menu and the one annoying me most is my camera now no longer taking full screen pictures rather now the image i see in the camera is a box instead of full screen).
Anyway, any tips on what I should do and where I should go for further info, please let me know in the comments. Any assistance is appreciated immensely. I am very new to this whole phone thing but not completely ignorant.
I have also attached some screenshots to show the sort of glitches I mentioned.
Few questions:
1) Are you still on b551?
2) Did you change your oeminfo file (one that changes your region)?
If you're still on b551 and have balongbug issue then head over to b170 (or b052) and apply the vendor update..
If you haven't changed your oeminfo file then you need to change it
https://yadi.sk/d/3eMg8bG0p8pU8 download this file and change it
change where? here's the location : /dev/block/platform/hi_mci.0/by-name
yeah you need to be rooted to change it...
1) Are you still on b551? Yes
2) Did you change your oeminfo file (one that changes your region)? No. Didn't think you could but given you have to be rooted I now know why lol
If you're still on b551 and have balongbug issue then head over to b170 and apply the vendor update.
-The version I upgraded from to get b551 I think had the balong bug. I don't have it anymore thankfully. Spent the past three days reading these forums about all this stuff, sounds like the balong really stuffs people up.
If you haven't changed your oeminfo file then you need to change it.
-If I don't have Balong bug do I still need to change oeminfo file? Or is that so I can get OTA? We don't get a whole lot of OTA stuff in NZ to my knowledge...
On that subject, if the firmware is European then I wouldn't get OTA at all would I? Or is that why changing the oeminfo file is important?
Thanks for responding btw. If I had any thanks thumbs, you earned it
Horacio55555 said:
1) .
If you haven't changed your oeminfo file then you need to change it.
-If I don't have Balong bug do I still need to change oeminfo file? Or is that so I can get OTA? We don't get a whole lot of OTA stuff in NZ to my knowledge...
On that subject, if the firmware is European then I wouldn't get OTA at all would I? Or is that why changing the oeminfo file is important?
Thanks for responding btw. If I had any thanks thumbs, you earned it
Click to expand...
Click to collapse
Oeminfo file changes your region and hence you'll get the OTA's for that region..
Doea your build number show balong or hisoft?
Sent from my ALE-L21 using XDA-Developers mobile app
---------- Post added at 16:06 ---------- Previous post was at 16:05 ----------
amageek said:
Oeminfo file changes your region and hence you'll get the OTA's for that region..
Doea your model number show balong or hisoft?
Sent from my ALE-L21 using XDA-Developers mobile app
Click to expand...
Click to collapse
Sent from my ALE-L21 using XDA-Developers mobile app
So as you probably saw on the other thread, my model number showed hisoft but build came through fine. Something to do with changed made in MM for sure...
I have gone through and started from scratch everything I did and will see how that turns out! I will also seriously look into rooting my device, hopefully i dont brick it after all this work. But i mean... I am in nz and we dont have MM available for p8 lite and from what i hear we wont even get it here. big bummer
Horacio55555 said:
So as you probably saw on the other thread, my model number showed hisoft but build came through fine. Something to do with changed made in MM for sure...
I have gone through and started from scratch everything I did and will see how that turns out! I will also seriously look into rooting my device, hopefully i dont brick it after all this work. But i mean... I am in nz and we dont have MM available for p8 lite and from what i hear we wont even get it here. big bummer
Click to expand...
Click to collapse
I am out of Europe too.. I am from Nepal, Asia.. We dont have MM here too (except in China)...
So don't worry you can do it
Sent from my ALE-L21 using XDA-Developers mobile app
UPDATE!!!
So I attempted last night to downgrade using this guys instructions. http://forum.xda-developers.com/p8lite/general/guide-debranding-converting-single-sim-t3305977
Apparently I botched it up somehow and lost my IMEI file. So I went back to this guys thread.
http://forum.xda-developers.com/p8lite/general/mega-thread-root-unbricking-updating-t3400994
Starting from B133 I worked my way up to B565 Single Sim European Nordic MM firmware using this site. This fixed my lost IMEI file thankfully.
http://www.carbontesla.com/2016/06/...te-b565-marshmallow-update-single-sim-europe/
Still have the Balong bug. As I said last night, I attempted to use a vendor update, which I obtained from the Mega thread linked above (second link), to rectify this but it failed.
For some reason, all these updates I have done also got rid of the ugly Spark Mobile startup screen as well which is nice lol.
If I can get the Balong bug sorted then I will try root. Until then, as always, help is wholly appreciated.
Hi everyone !
i have many issues and limitations on my ZTE Axon 7 like battery drain and problems to connect with google account, remove or change it etc. Basically I'm not allowed to do anything telling me I dont have admin rights.. I tried already many solutions to sort these issues but none worked. Even if I do a factory reset I will still encounter same issues. I have european version of the phone I'm on build number ZTE A2017GV1.0.0B11, MIFavor UI 4.0, Android 6.0.1, Kernel 3.18.20 and I want to upgrade it to B35 or a much more recent version. The update in the settings is telling me 'software up to date' so cant do it automatically.
Which version would you advise to have the most efficient and less limitative interface (maybe even avoid overlayers from zte) ? could you help me explaning how to choose and do an upgrade with all detailed steps? also I am wondering if any problem with upgrading and my phone doesnt work can I do a factory reset or nothing and do I lose the warranty doing so? I am looking for most simple way to do so (for a newbie)
thanks a lot !
Download the A2017G B08 Nougat ROM, put the update.zip in the root of SD and use the system update app. From that ROM there is a new Nougat B10 update as a precursor to updating to Oreo soon.
yann360 said:
Hi everyone !
i have many issues and limitations on my ZTE Axon 7 like battery drain and problems to connect with google account, remove or change it etc. Basically I'm not allowed to do anything telling me I dont have admin rights.. I tried already many solutions to sort these issues but none worked. Even if I do a factory reset I will still encounter same issues. I have european version of the phone I'm on build number ZTE A2017GV1.0.0B11, MIFavor UI 4.0, Android 6.0.1, Kernel 3.18.20 and I want to upgrade it to B35 or a much more recent version. The update in the settings is telling me 'software up to date' so cant do it automatically.
Which version would you advise to have the most efficient and less limitative interface (maybe even avoid overlayers from zte) ? could you help me explaning how to choose and do an upgrade with all detailed steps? also I am wondering if any problem with upgrading and my phone doesnt work can I do a factory reset or nothing and do I lose the warranty doing so? I am looking for most simple way to do so (for a newbie)
thanks a lot !
Click to expand...
Click to collapse
B35 is US. You have to use B08 or 09. But yeah, just update to B08
The Nougat V1.2.0B10 just released. You may get it from the ZTE Germany page.
@ko_wei13 is it compatible to update from ZTE A2017G V1.0.0B11 to V1.2.0B10 ? if I download it from the german website can I set any language after update?
@RobboW on which website can I find / download right package of the A2017G B08 Nougat ROM compatible with my build version?
yann360 said:
@ko_wei13 is it compatible to update from ZTE A2017G V1.0.0B11 to V1.2.0B10 ? if I download it from the german website can I set any language after update?
Click to expand...
Click to collapse
http://www.ztemobile.de/support/downloads/?product_id=2100
Yes, minimum requirement to update to Nougat is V1.0.0B11. So you can download the file and place it under the root directory of your phone storage and the system update will automatically detect it.
For language, there is no issue for you to change it as the ROM is for global, not limit to German.
I flashed it on my G. Had a couple of glitches but mostly ok. They say you should do a major update after a factory reset. I didn't but the glitches were minor and it seems to be working ok now.
thanks worked great !
@yann360,
Hi,
Yeah, you can set most language in your phone. You can upgrade your phone via SD card.
Thanks!
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?