Hi all,
I’d would really appreciate some comments or suggestions on how to solve following problem.
I bought an Essential phone on ebay this week (Sprint “unlocked”), and it came with Android 9 Pie. I initially put a simcard from an operator here in my country and it worked fine.
Due to work reasons I need the phone to be rooted with Android 7.1.1 Nougat (compatibility issue with a software used for testing celullar networks), so as a first step I flashed one of the Nougat images available in Essential’s website. This wasn’t a problem since I had already done this procedure with other Essential phones.
After successfully flashing Nougat, when I inserted back the simcard the phone did not recognize it. I upgraded back to 9.0, and the simcard was working again. The same happened when I downgraded to Oreo for testing.
Does anyone have any suggestions on how could I proceed to solve this issue? I really need it to run Nougat.
Thank you in advance for your feedback!
Make sure you unlocked the critical partitions, that's needed for the full image to flash and produce a fully functioning device, else there may be incompatibilities in the radio/modem/hardware/bootloader.
lecc18 said:
Hi all,
I’d would really appreciate some comments or suggestions on how to solve following problem.
I bought an Essential phone on ebay this week (Sprint “unlocked”), and it came with Android 9 Pie. I initially put a simcard from an operator here in my country and it worked fine.
Due to work reasons I need the phone to be rooted with Android 7.1.1 Nougat (compatibility issue with a software used for testing celullar networks), so as a first step I flashed one of the Nougat images available in Essential’s website. This wasn’t a problem since I had already done this procedure with other Essential phones.
After successfully flashing Nougat, when I inserted back the simcard the phone did not recognize it. I upgraded back to 9.0, and the simcard was working again. The same happened when I downgraded to Oreo for testing.
Does anyone have any suggestions on how could I proceed to solve this issue? I really need it to run Nougat.
Thank you in advance for your feedback!
Click to expand...
Click to collapse
You need to do a full wipe of the data when going backwards.
There is some setting hanging around that is not compatible.
I have seen this also
Related
I have switched to a new device and no longer use this phone but i see many others facing this issue as well so I am keeping this thread open, please do not message me regarding the solution to this issue cause all i did to get out of this mess was getting a new phone.
Hello !
Due to some error while flashing stock rom on Moto G4 Plus XT-1643 my Moto G4 Plus has changed into Moto G4 but the model no shown in the "About Phone" section is correct.
I have lost one Imei no. fingerprint option is no where sim or mobile network doesn't work other than that the phone is fully functional(WiFi,Camers,Audio etc)
There are multiple threads on the same issue but no solution is available I would be highly grateful if anyone could find out any solution to this issue.
P.S : I have tried flashing multiple ROMs available on the forum specific to XT-1643 i.e Indian Version
Also I flashed the OTA file for the Android 7.0 Soak Test due to which I cannot relock the bootloader.
I am currently on Stock Marshmallow 6.0.1 139-63 Rooted&TWRP installed
The phone is basically an iPod without fingerprint sensor
I had the same issue. I relocked the bootloader and sent to service center. They flashed the original firmware. Stock roms roaming here are not exactly stock roms.
this happened to my phone (1640 - brazilian moto g 4 plus), and I tried every single rom out there for moto g 4 plus, and it is only identified as Moto G 4, without fingerprint or any modem activity.
i still cannot recover previous bootloader, because it don't downgrade bootloader version. nothing worked for me so far.
i'll be watching this thread to see if anyone comes with any alternative.
sabithmk said:
I had the same issue. I relocked the bootloader and sent to service center. They flashed the original firmware. Stock roms roaming here are not exactly stock roms.
Click to expand...
Click to collapse
Umm, so according to you too it's a software issue and not a hardware one right ?
The first thing that I do when I boot in TWRP, I do a full backup of all the phone's partitions, and save a copy on my PC, so I can restore the phone in cases like this.
Guys, maybe you need to read this thread:
http://forum.xda-developers.com/showthread.php?t=2617276
if you flashed android 7.0 and then downgraded to android 6.0.1 then expect some bugs because your bootloader gets updated you have to do clean flash but you cannot actually completely downgrade to android 6.0.1 after you updated to 7.0 soak test bootloader still remains updated and your phone will brick when you click update after you receive 7.0 official OTA i warned you this happened to lot of moto x users do some research before you do anything if the phone is your primary device
Soureen said:
Umm, so according to you too it's a software issue and not a hardware one right ?
Click to expand...
Click to collapse
I think so. May be if we flash a wrong modem, the right one never flashes correctly. I don't know how do they managed to flash it correctly.
For me its a software issue... looks like it messed with the bootloader, and since you cannot rollback to an older bootloader, the phone works like an iPod Touch. haha
I hope that when Motorola releases the final 7.0 version for 1640, I'll be able to flash again the right bootloader and that will fix the phone.
SoNic67 said:
The first thing that I do when I boot in TWRP, I do a full backup of all the phone's partitions, and save a copy on my PC, so I can restore the phone in cases like this.
Guys, maybe you need to read this thread:
http://forum.xda-developers.com/showthread.php?t=2617276
Click to expand...
Click to collapse
I did a full flash of an older 6.0.1 ROM, and it still doesn't work. Since the only thing that I couldn't flash is the bootloader, and the phone identify itself as Moto G 4 (and not Moto G 4 Plus) my guess is that the problem is with the bootloader.
I guess i'll have to wait for the official 7.0 for my specific phone (1640) to fully replace this broken bootloader.
Yeah, that's why I didn't upgrade to the N yet, I was sure that the bootloader will be different.
I also have saved the partitions with Partitions Backup & Restore app, after rooting.
Did you try the ElementalX kernel?
http://forum.xda-developers.com/moto-g4-plus/development/kernel-elementalx-g4-0-01-t3424836
I was also having same issue,got my bootloader locked and went to service center and they replaced the motherboard for free????
Lucky you
Has anyone found a solution to get the plus (fingerprint) back to the phone?
Nope funny thing no one knows anything ??
I am waiting for the Android 7.0 official update so that I can relock my bootloader and send it for service.
That's a bummer but there might be some solution. The phone version number shouldn't be that hard to find if you'd knew witch file that flashes it.
How do you do these backups for they don't look at all as twrp backups so I guess twrp is second best to something. But what?
What is the different with 7.0 coming up? Can't you just relock a backup?
Soureen said:
Nope funny thing no one knows anything ??
I am waiting for the Android 7.0 official update so that I can relock my bootloader and send it for service.
Click to expand...
Click to collapse
I have the same issue, I have seen people with XT1643 having athene_f in build fingerprint but I have only athene. Which one is correct, could this be the issue?
Managed to solve the issue at least to get the signal. This is what I have done
- Restore my first TWRP backup.
- Booted directly into bootloader and NOT system, flashed modem for the build.
- Rebooted and I am getting the signal!!!
m.swastik said:
Managed to solve the issue at least to get the signal. This is what I have done
- Restore my first TWRP backup.
- Booted directly into bootloader and NOT system, flashed modem for the build.
- Rebooted and I am getting the signal!!!
Click to expand...
Click to collapse
Radio is working after TWRP backup + modem flash. Still fingerprint is not working and it is pointing out as athene not as athene_f
(bootloader) ro.build.fingerprint[0]: motorola/athene/athene:6.0.1/MPJ24
(bootloader) ro.build.fingerprint[1]: .139-63/64:user/release-keys
Click to expand...
Click to collapse
l2o88j said:
Radio is working after TWRP backup + modem flash. Still fingerprint is not working and it is pointing out as athene not as athene_f
Click to expand...
Click to collapse
I have spent 1 whole week to get the signal working, at least be glad that you can now use your phone and press thanks if I helped. Regarding athene in build fingerprint you can easily change that in build.prop but it won't help. I think fingerprint service is disabled because ROM thinks that our phone is G4 and not G4 plus. I have tried few things to enable it but not getting it to work, will update if any of my experiment is successful.
m.swastik said:
I have spent 1 whole week to get the signal working, at least be glad that you can now use your phone and press thanks if I helped. Regarding athene in build fingerprint you can easily change that in build.prop but it won't help. I think fingerprint service is disabled because ROM thinks that our phone is G4 and not G4 plus. I have tried few things to enable it but not getting it to work, will update if any of my experiment is successful.
Click to expand...
Click to collapse
I found this trick early and I am using it now. I thought you cracked the last part (fingerprint sensor) which my post was about. I think that the issue is with gpt bin as I tried different bootloader versions along with all possible combinations. Gud to see someone else is working on the same. Will update if found any.
find the correct firmware for the device and flash it else it would lead to such errors
Hi All
Hoping you can help as i am struggling to understand how this all works with this manufacturer. I got this tablet yesterday and love it so far ... upon starting the tablet i was greeted with an update notification that i initially figured was for 7.0 - turns out this was a patch for 6.0.
This is all great except i noticed in another thread that someone with the same version and based in the uk received the update. Mine wont find it. I tried the PC software to see if this would work as it used to on other manufacturers (Sony for example) but it said i was up to date.
I would prefer to update the official way if possible (not my first BBQ, have had more android tablets than you can poke a stick at - have resorted to all sorts of ways to get the next software before)
Any ideas anyone ? least possible effort as i don't want to corrupt this awesome piece of kit !
From what I can tell they roll it out in waves based on the device's IMEI. I also haven't received it in Italy when some people in neighbouring countries have. I guess all you can do is wait. By the way, corrupting the device is not that easy, if you want to test Nougat right now, you can get it using Firmware Finder, then you can roll back to the regular version using a rollback package you can find on Huawei's website. Worst case scenario, you will have to factory reset, but it won't be a big deal I guess since you just got it. I was able to roll back from a failed flash of Nougat just fine, then reflashed the correct version of Nougat and used it for a while, then rolled back again because I heard the official ota is coming, and it always worked just fine.
Ok great thanks for confirming. i almost went for the galaxytab s2 again (my wife swindled me out of my old one ! ) but glad i didn't - this one runs better on 6.0 than the s2 on 7.0 i noticed.
Greetings devs and members:
I have recently begun using a Moto G5 Plus (XT1687 - N. American SKU) that was never updated (due to being in a drawer someplace).
I know that many things have been unlocked and improved by the devs for this particular handset. My question is simply this:
How should I update it? Should I update it?
Should I go OTA (retus) (currently blocking), or should I bypass everything and go directly to Oreo (using the update file, after a factory reset and such)?
Or, hell should I stick with Nougat right now? It seems that lots of folks are having issues, and I just wanted a more informed opinion.
Thank you.
sinister008 said:
Greetings devs and members:
I have recently begun using a Moto G5 Plus (XT1687) that was never updated (due to being in a drawer someplace).
I know that many things have been unlocked and improved by the devs for this particular handset. My question is simply this:
How should I update it? Should I update it?
Should I go OTA (retus) (currently blocking), or should I bypass everything and go directly to Oreo (using the update file, after a factory reset and such)?
Or, hell should I stick with Nougat right now? It seems that lots of folks are having issues, and I just wanted a more informed opinion.
Thank you.
Click to expand...
Click to collapse
To stay with Nougat is not a bad choice, it's a well working system.
If you want to get to Oreo just apply all the OTA updates until you're there. No need to do anything else if your device isn't rooted or the system has been tampered in any other way.
Both firmwares seem to work well.
If the phone is not rooted, then OTA updates are the easiest. Make sure the phone is fully charged or plug it in first. Go to about phone, go to check system updates, accept OTAs until it says up to date, which is likely be Oreo. If it stops at -18 the it may take a few days before the phone alters you to Oreo update.
Need Help! I'm very used to Android SW/FW but this has me stumped. We put a Three UK SIM in my girlfriends unlocked P Smart (FIG-LX1 C782), she bought it brand new, unlocked from Argos a year ago.
A few hours after using the Three SIM, she gets a system update and promptly updates it. Ever since, when it boots it Shows the Three/3 Logo on boot and shutdown and has pre-installed a load of Three apps. It was not bought from Three!
I'm trying to follow instructions from huaweiflash.com and have downloaded stock firmware files from there. I can get it to begin the update, but it always fails at about 5%. The software has never been rooted or anything, so the phone is locked. I just want to revert it to the stock, non-branded Huawei software it originally had before we put the bloody Three SIM card in it! Can anyone help!?
Fixed! - I followed the downgrading instructions only in part of this thread, using the download linked in the thread and it installed and I'm back to stock ROM (No Three/3!)
https://forum.xda-developers.com/huawei-p-smart/how-to/guide-downgrading-huawei-p-smart-t3927808
FIRMWARE: https://androidhost.ru/3c9
( FIGO-L31 FIG-L31 FIG-LX1 8.0.0.128A(C432) FIRMWARE ANDROID 8.0.0 EMUI 8.0.0 05014XMW )
Iggy82 said:
Fixed! - I followed the downgrading instructions only in part of this thread, using the download linked in the thread and it installed and I'm back to stock ROM (No Three/3!)
https://forum.xda-developers.com/huawei-p-smart/how-to/guide-downgrading-huawei-p-smart-t3927808
FIRMWARE: https://androidhost.ru/3c9
( FIGO-L31 FIG-L31 FIG-LX1 8.0.0.128A(C432) FIRMWARE ANDROID 8.0.0 EMUI 8.0.0 05014XMW )
Click to expand...
Click to collapse
Thanks for this. I had the exact same scenario, bought from Argos, unlocked yadayada and put my Three sim in. Shortly afterwards got the same as you described. I complained to Three who told me to complain to the manufacturer as this was impossible from just putting in a sim.
diskonot said:
Thanks for this. I had the exact same scenario, bought from Argos, unlocked yadayada and put my Three sim in. Shortly afterwards got the same as you described. I complained to Three who told me to complain to the manufacturer as this was impossible from just putting in a sim.
Click to expand...
Click to collapse
You're welcome, please click on 'Thanks!' button to right of this post if you didn't already
I had a T-Mobile branded 6t that was some locked so I converted to international version and sim unlocked it. Everything went smoothly except now I randomly get permission resets as well as a Bluetooth issue that won't play any media through headphones ect. When connected via BT the audio still plays through phone. Research suggests it was bug fixed in the latest update. Currently I am on O.O.S 9.0.11. my question and concern is can I safely update to the most current version of OSS. Will doing so brick my phone? How do I safely resolve the BT and permission issues? Any insight would be greatly appreciated. If there is anything specific info wise that I missed or needed I apologise in advance I'm not familiar with troubleshooting. Thanks again.
BoSavageYo said:
I had a T-Mobile branded 6t that was some locked so I converted to international version and sim unlocked it. Everything went smoothly except now I randomly get permission resets as well as a Bluetooth issue that won't play any media through headphones ect. When connected via BT the audio still plays through phone. Research suggests it was bug fixed in the latest update. Currently I am on O.O.S 9.0.11. my question and concern is can I safely update to the most current version of OSS. Will doing so brick my phone? How do I safely resolve the BT and permission issues? Any insight would be greatly appreciated. If there is anything specific info wise that I missed or needed I apologise in advance I'm not familiar with troubleshooting. Thanks again.
Click to expand...
Click to collapse
I also have a t-mobile branded phone that I converted to the international version. You can totally update your phone to 9.0.17 safely. I did this update rooted though using twrp.
I would highly recommend going to the Guides section of the 6T forums since there's a gold mine of info and links.
NOTE: If I were you, don't update to the first stable build of Android 10 yet. It's buggy and unstable. There are threads on this topic as well. :good:
sameog said:
I also have a t-mobile branded phone that I converted to the international version. You can totally update your phone to 9.0.17 safely. I did this update rooted though using twrp.
I would highly recommend going to the Guides section of the 6T forums since there's a gold mine of info and links.
NOTE: If I were you, don't update to the first stable build of Android 10 yet. It's buggy and unstable. There are threads on this topic as well. :good:
Click to expand...
Click to collapse
Update: here's the file https://forum.xda-developers.com/oneplus-6t/how-to/official-oxygenos-9-0-4-ota-oneplus-6t-t3860953
Exactly what he said, look on the forum for the update to 9.0.17 file and local upgrade, no need to backup or just for security since it will not wipe storage. I'm running this too and works like it should. Don't do Android 10 update yet, it's super buggy.
Just to clarify since I've not come across a solid answer but I've downloaded and moved 9.0.17 to parent directory. I have unlocked bootloader and sim via rebrand to international 9.0.11. I have dev options #1 usb deg #2 verify apps via USB both on. Is that all that needs to ensure a smooth flash in local upgrade? Do I need to turn on advanced reboot? I vaguely remember seeing somewhere about issues concerning adv reboot. I just want to be sure before I flash the update and wipe cache. Thanks again.
BoSavageYo said:
Just to clarify since I've not come across a solid answer but I've downloaded and moved 9.0.17 to parent directory. I have unlocked bootloader and sim via rebrand to international 9.0.11. I have dev options #1 usb deg #2 verify apps via USB both on. Is that all that needs to ensure a smooth flash in local upgrade? Do I need to turn on advanced reboot? I vaguely remember seeing somewhere about issues concerning adv reboot. I just want to be sure before I flash the update and wipe cache. Thanks again.
Click to expand...
Click to collapse
I enable advanced reboot to bring up the full menu, as in and in this order(power off, restart, recovery, bootloader, and screenshot)
It's a personal preference for me and at the same time, convenience.
Ok well I will enable it as well and see it it suits me. I suppose I'm going to root so wish me luck lmao
BoSavageYo said:
Ok well I will enable it as well and see it it suits me. I suppose I'm going to root so wish me luck lmao
Click to expand...
Click to collapse
Luck!
BTW: Christmas came early and oneplus just released open beta 2 for Android 10. I just installed it and running great -- of course, I'm going to give it the "weekly workout" and see if the bugs were ironed out and can "leave" pie or revert back.
Seems I've successfully flashed to 9.0.17. hopefully that removes the annoying bug that randomly resets app data and permissions. I believe I fixed the BT issue prior but I'm still aggravated by the app data stuff. Hopefully this works out. I appreciate the assistance and have one last request. Could someone please point me to the proper guide to root my international 9.0.17 6T. Thanks again ?