Database Users

De-crypting Marshmallow encrypted MicroSD

Hi,
Lately, I got a Marshmallow update for my Moto X Play to which I upgraded and as I wasn't quite aware of the Encryption Policy for the same, I tried mixing my 64 GB Samsung MicroSD with my internal storage. It worked fine until I started having problems using the new Marshmallow upgrade. I decided to downgrade, did not bothered about decrypting the card before downgrading.
As soon as I downgraded the device to Lollipop, I found that I was no longer able to use the MicroSD in the same way I used to do it earlier. It was write protected and I was not able to decrypt in any way.
Googling didn't quite helped, and it looks like very few people have had similar problem.
Anyone having same issue? And any solution to this?

I think if you reformat the card you can start using it again, but you will lose all data.

New stock Stock ROM Elephone P9000_Android 6.0_20160715 OTA update supported

Download link: https://mega.nz/#!joEFGYrL!Lmi-YtYO-mLDLVc3EHEi0yOmWT22RtNFvet_l0QS6q4
ROM flashing tutorial: http://bbs.elephone.hk/thread-1037-1-1.html#.VWgkX_RAU-0
Any bugs just reply here, please do not create a new thread.
Changelog：
1. Restoration of spanish translation
2. Optimization of GPS
3. Optimization of gyroscope
4. Optimization of battery performance

Great thx

Fingers crossed it means the GPS works now
Sent from my P9000 using Tapatalk

iv flashed the rom successfully but it just stayed on the elephone boot logo and wouldn't go past it. So then i flashed 20160608 and it worked straight away
---------- Post added at 03:07 PM ---------- Previous post was at 02:39 PM ----------
haidar123 said:
iv flashed the rom successfully but it just stayed on the elephone boot logo and wouldn't go past it. So then i flashed 20160608 and it worked straight away
Click to expand...
Click to collapse
problem fixed by downloading rom from elsewhere. the link posted here hasnt got the tee1 and tee2 files therefore the rom does not install correctly
the working link is https://mega.nz/#!joEFGYrL!Lmi-YtYO-mLDLVc3EHEi0yOmWT22RtNFvet_l0QS6q4

how?
i need this rom, im so annoyed with the phone, biggest issue for me is the gps, can anyone confirm if it fixes the issues?
if so whats the dangers of loading the rom (i dont know how) and will it invalidate my warranty
thanks
scott

stredwizard said:
i need this rom, im so annoyed with the phone, biggest issue for me is the gps, can anyone confirm if it fixes the issues?
if so whats the dangers of loading the rom (i dont know how) and will it invalidate my warranty
thanks
scott
Click to expand...
Click to collapse
Although I've had no issues with my GPS, my brother (whom I recommended the phone too) does have issues. The GPS was all over the place tbh.
As a temporary fix he installed GPS Status & Toolbox (from Playstore) and it kinda stabilises his GPS, must admit it does seem to be much better for him now, well atleast usable.
Maybe worth a try until Elephone get their finger out & release this as an actual update on the phone itself, my brother is just using Stock Rom (the latest update 20160608) and he ain't exactly techy minded like me as I've rooted mine etc. So I can understand your frustration.
The problem I see with Elephone (as much as I love my P9000) is that they too quickly move onto the next model and any support (well if Elephone support ever existed in the first place lol) stops for the "last model" .
As regards to "warranty" - personally for me I dont care whether it voids it or not rooting etc .. but I doubt it would. And anyway, the support Elephone would probably offer would be so "awful" (I would imgine from what I read up on them) that probably going out and buying another handset would be less frustrating in the long run ;0)
I'm going to update my P9000 now to check this update out, more to see if battery optimisation is any better for my handset.
Edit: Sorry I noticed you stated you didn't know how to root & install customer recovery (TWRP), basically first follow steps here:
http://forum.xda-developers.com/elephone-p9000/how-to/how-to-root-stock-rom-t3396908
You can then update via TWRP recovery to the 20160715 by using the flashable zip file found here:
http://forum.xda-developers.com/ele...rom-stock-rom-elephone-p9000android6-t3400608
Hope it helps ;0)

Thanks
Thanks for the help, I have already tried the gps status app which has made no difference with the phone laying flat on the worktop the compass is never still, but is this a sensor issue rather than a GPS issue, I'm not sure
I reccomended the p9000 to my partner, her GPS is terrible as well, but she bought hers from amazon, so we could probably return hers without an issue, mine came from eBay......
I tried to install twrp but I can't get it to work, fast boot reports boot loader not unlocked or similar even though I have enabled this in developer options, can't do it inside fast boot either becuase volume up button doesn't work.
Thanks for help
Scott

Why is this not available via ota?

ask elephone not xda
maybe this is another leaked beta from 4pda
best regards

freddy5 said:
ask elephone not xda
maybe this is another leaked beta from 4pda
best regards
Click to expand...
Click to collapse
I contacted with Elephone support a few days ago about some questions , one of them next update and this is what they said.....
"Cant confirm at present ,please wait with patience .
Best regards,
Teresa"
I think That's not a regular update from Elephone.
Just my feelings....

Very nice OTA

Yup..now available via ota

I tried the wireless update and it didn't work. Retrying now but here's what happened:
Phone powered off showing Elephone logo first
Powered back on showing elephone logo
The update.zip is corrupted.
Installation aborted.
OTA failed! Please power off the device to keep it in this state and file a bug report!
Just tried it again, same exact thing.
---------- Post added at 07:26 PM ---------- Previous post was at 07:26 PM ----------
I tried the wireless update and it didn't work. Retrying now but here's what happened:
Phone powered off showing Elephone logo first
Powered back on showing elephone logo
The update.zip is corrupted.
Installation aborted.
OTA failed! Please power off the device to keep it in this state and file a bug report!
Just tried it again, same exact thing.

Impressed by P9000, except the GPS.
Just updated OTA to Elephone_P9000_20160715. It does say it has a GPS fix, hope so because apart from that I do like the phone.
I have found that using "HERE" instead of Google maps everything stays on route (Most of the time) I will try the phone Google maps now and see if it has improved.

b33p_ said:
I tried the wireless update and it didn't work. Retrying now but here's what happened:
Phone powered off showing Elephone logo first
Powered back on showing elephone logo
The update.zip is corrupted.
Installation aborted.
OTA failed! Please power off the device to keep it in this state and file a bug report!
Just tried it again, same exact thing.
---------- Post added at 07:26 PM ---------- Previous post was at 07:26 PM ----------
I tried the wireless update and it didn't work. Retrying now but here's what happened:
Phone powered off showing Elephone logo first
Powered back on showing elephone logo
The update.zip is corrupted.
Installation aborted.
OTA failed! Please power off the device to keep it in this state and file a bug report!
Just tried it again, same exact thing.
Click to expand...
Click to collapse
I just got the same error in the Recovery Mode stating the update.zip is corrupted. I remembered this issure from a previus OTA update and solved it by removing my SD card and putting my SIM card in slot 1. After that the OTA update ran through perfectly. I hope this helps! :good:
EDIT: I found another yet easier solution in a German forum. [Unfortunately I am a too new user in this forum to post a link. So you have to live without a source]. Summoned up: Go to preferences > Storage & USB and remove the SD card by tapping the "eject" symbol. After the update, do not forget to set your SD card as the standard storage again.

PimpWizkid said:
I just got the same error in the Recovery Mode stating the update.zip is corrupted. I remembered this issure from a previus OTA update and solved it by removing my SD card and putting my SIM card in slot 1. After that the OTA update ran through perfectly. I hope this helps! :good:
edit: I found another easier solution in a german forum. [Unfortunately I am a too new user in this forum to post a link. So you have to live without a source] Summoned up: Go to preferences > Storage & USB and remove the SD card by tapping the "eject" symbol. After the update do not forget to set your SD card as the standard storage.
Click to expand...
Click to collapse
Thanks it works
have someone issues with BT on 20160715?

This has been released as OTA, and installed fine on my P9000. Remember - switch both sims off, in settings, before downloading, and make sure you keep the screen on whilst downloading. Also good idea to delete a few fingerprints, just in case the fingerprint problem comes back.
So far no problems, but no AndroidPay as the phone stills fails the SafetyNet API call.
Honestly I'm a bit surprised that Elephone are sill updating this phone, delighted, but surprised. Well done, Elephone! But please, if you can, get the AndriodPay working?
W.

is this rom also flashable on P9000 lite ?

Nice home screen update, swiping all the way across brings you back to the start again

Fast charging still not restored for me.

How can manually upgrade to 7.1.1 when on unrooted build A2017GV1.1.0B01

Hey.
Bought my A2017G from Italy and am in the UK trying to work out how to update it to 7.1.1.
I upgraded it from marshmallow via a manual update but now the build is A2017GV1.1.0B01 and all the sites with the latest update say I need B11 to upgrade to the B05 Spanish June release.
I have had a few niggles with the phone such as I call someone and they can't hear me and hang up. Internet reception isn't great on giff gaff o2 either.
I'm sort of hoping an update might solve these issues.
My phone is not rooted as I want to keep my 2 year warranty. I've contacted ZTE Europe on Facebook but they are not replying.
Does anyone know if I can flash the B05 Spanish 7.1.1 directly over my b01 or not?
I thought I'd take the phone out the box and it will would just get the ota updates.

You should be able to just flash the B05 with Updater or in stock recovery.

Just download the full B05 ROM and unzip to root directory of your internal storage or SD card. Then open the system update and it should detect the ROM right away.

Want to upgrade. Still in original situation as OP - advice?
Re OP. I realise this is a year old now and maybe this is called bumping (I don't know) but I'm still in nougat 7.0 B01.
After I wrote OP, I got sidetracked with life (mother of toddler and no time to decode cryptic advanced phone stuff anymore) lucky if i get a hot cup of tea! ?
Now I'm still suffering from calls where person other end can't hear me when i call them till i turn speaker phone on and off and on. Phone is slow too and battery not great. Have never had an OTA update (in UK.)
If I get any time ever I need a super clear process I can follow.
So. Do I need to
A/ back up all my internal data
B/ make sure battery fully charged
C/ Can I then just download the latest 7.1.1 b10 firmware and install it over my 7.0 b01? Or, do I need to go through each update first e.g. b02, b03, b04 etc etc? How do I know a firmware is the full file not an update?
D/ Can I send my IMEI to ZTE to apply for OTA updates and if so who do I email? Exactly like for the UK?
Sorry for sounding dumb but I really just don't have the time to learn it figure this stuff out and I've read so many threads tonight on here but no one seems to have my ancient firmware still.
Thanks for replying in advance ?

fluttershutter said:
Re OP. I realise this is a year old now and maybe this is called bumping (I don't know) but I'm still in nougat 7.0 B01.
After I wrote OP, I got sidetracked with life (mother of toddler and no time to decode cryptic advanced phone stuff anymore) lucky if i get a hot cup of tea! ?
Now I'm still suffering from calls where person other end can't hear me when i call them till i turn speaker phone on and off and on. Phone is slow too and battery not great. Have never had an OTA update (in UK.)
If I get any time ever I need a super clear process I can follow.
So. Do I need to
A/ back up all my internal data
B/ make sure battery fully charged
C/ Can I then just download the latest 7.1.1 b10 firmware and install it over my 7.0 b01? Or, do I need to go through each update first e.g. b02, b03, b04 etc etc? How do I know a firmware is the full file not an update?
D/ Can I send my IMEI to ZTE to apply for OTA updates and if so who do I email? Exactly like for the UK?
Sorry for sounding dumb but I really just don't have the time to learn it figure this stuff out and I've read so many threads tonight on here but no one seems to have my ancient firmware still.
Thanks for replying in advance ?
Click to expand...
Click to collapse
Literally charge it, download the full Nougat B10 update file (update.zip of 2.7Gb), put it in the root of an SD card or internal storage (prefer SD), go to settings/system update and the app will see the update file. Go from there. No need to go up in steps when already on a Nougat system. Always good to back up but these updates preserve user data provided it all goes smooth.
ZTE won't help you at all. Don't need to do anything with the IMEI. People can lose their number when flashing the wrong things but what you're doing is just a standard update. The main thing is, if you have a US, Chinese or international model, use the correct ROM for it and your IMEI is not lost. From what you've posted, your phone should be an A2017G which is printed on the back of the phone.
ZTE A2017GV1.2.0B10 is the latest official Nougat for the G (international).

Collection of potential camera fixes for Nougat (Black screen, crashes) - Suggestions

Hi all,
I finally managed to get a Nougat ROM running on my device - except for the camera. It keeps showing a black screen (closes and pops up in intervals of about 1s). I of course searched the forum but it looked like noone has really managed to find a reliable solution. First some background for my device: VNS-L31 (Dual Sim) which was running on fully stock/fully working C432B160 firmware (no root, locked bootloader, after factory reset) and then upgraded to Nougat C432B370 using FirmwareFinder (FullOTA-MF-PV). Installation worked fine, everything running as expected except for the camera - as said. I exactly followed the steps outlined in this thread here: https://forum.xda-developers.com/hu...android-7-emui-5-0-vns-l-cb360-links-t3565117
Factory resetting after upgrading doesn't solve the issue. After upgrading to B370, I also updated to C432B388 - but to no avail. What I find a little strange is this: Connecting the device to the computer and investigating the device info correctly shows build/device/manufacturer etc. However, in build.prop it shows information about the NRD90M test-keys release with generic_a15 device. Could this hint at some issue? Also, checking the device info with
Code:
*#*#2846579#*#*
shows this: Manufacture information: NEMO_L21E_VB. I actually expected something with "L31" there - but well, I also don't really know what this specific thing stands for.
Now, here are certain things I came across when looking for solutions:
Suggestion by @Meticulus: https://forum.xda-developers.com/showpost.php?p=69990309&postcount=226
I tried the suggestion by Meticulus, but unfortunately it didn't work. Does there exist a modification for newer builds that might work? (I just don't understand why that should help - to me it looks moreorless like restarting the camera).
Some fix in build.prop mentioned by @danielegta : https://forum.xda-developers.com/showpost.php?p=72280947&postcount=7
I have absolutely no idea what the build.prop modification is supposed to be. Can anyone elaborate?
A TWRP related fix: http://www.htcmania.com/showpost.php?p=25093316&postcount=31
A bit afraid to try the TWRP fix by BadWolf. It seems to be for B328 builds... So I am a bit unsure whether I should try it on newer build. According to members in the German android-hilfe.de forum, it once solved these issues, but as said for older builds.
Edit: I tried the fix on B370 but it has no effect.
Use the fix in #3, but reflash system.img if the fix doesn't help: https://forum.xda-developers.com/showpost.php?p=70069246&postcount=26
Unfortunately this also didn't work for me
Use TWRP-flashable .zip files as given in this thread here: https://forum.xda-developers.com/huawei-p9lite/how-to/nougat-official-firmware-t3512932
I tried this today, but unfortunately it ends up in the same state as I was when upgrading B160 -> B370 using Firmware Finder. Everything except for the camera works.
Edit: I notice that in TWRP there are always errors about not being able to mount /data and /cust. Is this normal or does it hint at some error/malfunction when updating via flashable zip?
Use TWRP-flashable .zip as in #5 but instead of flashing the two .zip without restarting the device, first flash update.zip, then restart phone, flash Nougat TWRP, flash update_data_full_VNS_Lxx_xx_xx.zip as described in this post: https://forum.xda-developers.com/showpost.php?p=70704697&postcount=7
Tried this in the following way: stock MM -> unlock bootloader and flash TWRP -> flash update.zip -> flash Nougat TWRP -> flash update_data_. Doesn't help. Also I cannot confirm what I read somewhere here on xda (some user mentioned that his camera was working when he only flashed the update.zip - this is not true for me).
Other things I tried for uprading the OS that are not necessarily meant to fix the camera issue, but might:
Use B336 as intermediate step: B160 => B336 => B370 (=> B388) as suggested by @vozilo here: https://forum.xda-developers.com/huawei-p9lite/how-to/how-to-b388-nougat-maybe-b381-guide-t3612072
Unfortunately this does not solve the issue. The camera doesn't work in any of the versions flashed after B160.
Go from B160 direcly to B388: didn't help
Does anyone know of something else that might help or could someone maybe comment on the "known" fixes, especially if there might be some changes that could be done to commands/build.prop or even local.prop that eventually help?
Thank you very much,
theluk

_theluk_ said:
Hi all,
I finally managed to get a Nougat ROM running on my device - except for the camera. It keeps showing a black screen (closes and pops up in intervals of about 1s). I of course searched the forum but it looked like noone has really managed to find a solution. First some background for my device: VNS-L31 (Dual Sim) which was running on fully stock/fully working C432B160 firmware and then upgraded to Nougat C432B370 using FirmwareFinder. Installation worked fine, everything running as expected except for the camera as said. I exactly followed the steps outlined in this thread here: https://forum.xda-developers.com/hu...android-7-emui-5-0-vns-l-cb360-links-t3565117
Factory resetting doesn't solve the issue. Afterwards, I also updated to C432B388 to no avail. What I find a little strange is this: Connecting the device to the computer and investigating the device info correctly shows build/device/manufacturer etc. However, in build.prop it shows information about the NRD90M test-keys release with generic_a15 device. Also, checking the device info with shows this: Manufacture information: NEMO_L21E_VB. I actually expected something with "L31" there - but well, I also don't really know what this specific thing stands for.
Now, here are certain things I came across when looking for solutions:
Suggestion by Meticulus: https://forum.xda-developers.com/showpost.php?p=69990309&postcount=226
I tried the suggestion by Meticulus, but unfortunately it didn't work. Does there exist a modification for newer builds that might work? (I just don't understand why that should help - to me it looks moreorless like restarting the camera).
Some fix in build.prop: https://forum.xda-developers.com/showpost.php?p=72280947&postcount=7
I have absolutely no idea what the build.prop modification is supposed to be. Can anyone elaborate?
A TWRP related fix: http://www.htcmania.com/showpost.php?p=25093316&postcount=31
A bit afraid to try the TWRP fix by BadWolf. It seems to be for B328 builds... So I am a bit unsure whether I should try it on newer build. According to members in the German android-hilfe.de forum, it once solved these issues, but as said for older builds.
Does anyone know of something that might help or could someone maybe comment on the "known" fixes?
Thank you very much,
theluk
Click to expand...
Click to collapse
I had the same problem, and i fixed it by (un)rooting and (un)rooting again

Could you please elaborate a little bit more on what you exactly did? Because for me I was fully stock (including locked bootloader) when upgrading from B160 to B370. Right after the upgrade finished I did a factory reset and the problem already appeared. Are you suggesting to root, unroot and root again? I mean I can try, but I don't see why this could help, so please let me know if I got your point correctly

_theluk_ said:
Could you please elaborate a little bit more on what you exactly did? Because for me I was fully stock (including locked bootloader) when upgrading from B160 to B370. Right after the upgrade finished I did a factory reset and the problem already appeared. Are you suggesting to root, unroot and root again? I mean I can try, but I don't see why this could help, so please let me know if I got your point correctly
Click to expand...
Click to collapse
Ok so usually u should upgrade like 160>b336>b370... The problem might be that you missed a step, not sure though. Try to factory reset first, then go back to b160 and to b336 and then to b370

Unfortunately your suggestion didn't work for me. But it also looks like FF didn't "send" all of the update package to the updater. I chose the 1.6GB FullOTA-MF-PV for B336 but in the system updater it only downloaded 1.2GB. I suspect the data update wasn't downloaded which surely caused issues. Will have to try that again, I guess

_theluk_ said:
Unfortunately your suggestion didn't work for me. But it also looks like FF didn't "send" all of the update package to the updater. I chose the 1.6GB FullOTA-MF-PV for B336 but in the system updater it only downloaded 1.2GB. I suspect the data update wasn't downloaded which surely caused issues. Will have to try that again, I guess
Click to expand...
Click to collapse
try updating through the stock updater

mjz2cool said:
try updating through the stock updater
Click to expand...
Click to collapse
Unfortunately the stock updater doesn't show any updates. So I have to enforce this by using the proxy method provided in Firmware Finder. As I understood this is the "fully" official way of updating, since it does use the "system update" feature provided inside settings of the phone. I will try it again later today to see what could've gone wrong. Maybe I'll just try one of the other B336 firmwares that are listed as FullOTA in FF.

Major update to OP - including new stuff and new information about what I tried. Any other suggestions? I am out of ideas for now and will probably have to live with MM until Huawei has solved this issue

After a suggestion to try VNS-L21 firmware I did, after flashing the corresponding oeminfo. And indeed this worked nicely. Upgrading to Nougat B370 worked and camera is working as well.

_theluk_ said:
after flashing the corresponding oeminfo
Click to expand...
Click to collapse
Hello,
Sorry but I'm a noob, can you explain to me what do you mean by "flashing the corresponding oeminfo" ? Does it mean you had to somehow "trick" your phone so it believes it's L21 instead of L31 or something ?
I have the same problem on the phone of my girlfriend (although I don't recall it's a dual sim one), I'd really like to solve this.
Thank you

_theluk_ said:
...
Suggestion by @Meticulus: https://forum.xda-developers.com/showpost.php?p=69990309&postcount=226
I tried the suggestion by Meticulus, but unfortunately it didn't work. Does there exist a modification for newer builds that might work? (I just don't understand why that should help - to me it looks moreorless like restarting the camera).
...
Click to expand...
Click to collapse
Ah, one of number of my statements taken out of context. When I worked on CM13, initially only the P9 Lite was supported. After a NEMO user tested this, which was proof of concept that the nemo camera could work on my p9 lite ROM, I added support for NEMO in my AOSP ROMs. So, the reason this helped was that it restarted the camera to work with NEMO and not VENUS, for which it was originally started.
As for your problem, Developer Options -> Take Bug Report ->FULL and post?

Unexpected Update: N950USQU8DVB1 2022-02-22

My Verizon Note 8 just received an update (N950USQU8DVB1) but I had thought that the phone was out of support and was not going to get any more updates. I don't see mention of this one on the Verizon update page. Does anyone know what this is about and why we are getting an update after the support window is over?

Hmmm. Just got the Verizon update also..it does show on web page now as available.
No idea why this came in a year after support ended...lots more than just security updates it seems. Glad I kept it

Can anyone confirm if this update made voLTE available?
Does anyone have the files available yet to download and flash?
I don't see them on sammobile.com yet, but I would like to get a copy if anyone can help.

This updated broke my phone. I updated last night and now I have a "No sim card" message. I took my phone to a repair shop and they couldn't fix it. They suggested maybe a flash/roll back, but they wouldn't do it for me. My phone was perfectly fine before I updated. Good times..............

Try booting to recovery mode and wiping the cache partition. My friend had a dual sim version and sim not found message happened to him, wiping cache and double checking network was set to auto fixed it for him.
Another method may be trying to connect to windows and download Verizon software assistant and select repair phone. Takes a while to download everything so be patient until it finishes. I recall it took a half hour. Hope it helps.