Hello,
I have a very strange problem. A few weeks ago I flashed my XT1563 single sim Moto X with the Brazilian 6.0 retail version (after flashing 5.1.1 brazilian lollipop). Everything went great except the phone stopped charging. It would detect power, it even detected the Turbo Charger but it just didin't charge. I downgraded to the stock rom for my model and after downgrading the motorola sensor services firmware as adviced in a notification when I first booted.
Problem solved, BUT.. a few days ago I recieved the OTA update for 6.0. Awesome, I downloaded and upgraded. Surprise, the device doesn't charge again, even though it was my exact phone's ROM. I downgraded again and I'm stuck in lollipop. Any advice?
Thanks!
alfreedom said:
Hello,
I have a very strange problem. A few weeks ago I flashed my XT1563 single sim Moto X with the Brazilian 6.0 retail version (after flashing 5.1.1 brazilian lollipop). Everything went great except the phone stopped charging. It would detect power, it even detected the Turbo Charger but it just didin't charge. I downgraded to the stock rom for my model and after downgrading the motorola sensor services firmware as adviced in a notification when I first booted.
Problem solved, BUT.. a few days ago I recieved the OTA update for 6.0. Awesome, I downloaded and upgraded. Surprise, the device doesn't charge again, even though it was my exact phone's ROM. I downgraded again and I'm stuck in lollipop. Any advice?
Thanks!
Click to expand...
Click to collapse
after flashing 6.0 try factory wiping your device. see if it helps.
bablu048 said:
after flashing 6.0 try factory wiping your device. see if it helps.
Click to expand...
Click to collapse
After flashing I wiped cache and user data, nothing worked
does anybody else have this problem? I can't be the only one, the phone works flawless in lollipop
Related
I have a problem with my Samsung Galaxy Express (GT-I8730), international version.
I updated my firmware using Odin to a newer build. The firmware was downloaded from SamFirmware.com.
After the update finished and my phone restarted I've got no sound at all. I tried doing a factory reset but no luck. I thought the firmware was corrupted and after downloading and installing a new one, the exact same thing happened.
In the video posted below I am doing a factory reset from recovery, just to show you that I'm doing everything from the beginning.
The phone vibrates but there is no sound.
Before the update I had build version : I8730XWAMB8. After the update I tried with : I8730XWAMD7 and I8730XWAMC4. All these builds have the version number 4.1.2.
If I reinstall the I8730XWAMB8, I have sound but this build is branded and I'm very mad that I can't install other versions. This thing won't happen on my Note 2. I can install what firmware I want from SamFirmware.com.
I also saw that with all these builds my phone will randomly power-off at different times. It can be 5 minutes after I turn it on or it can be 18 hours. After the power-off I need to take out the battery.
What is wrong with the phone? Before these updates everything worked perfectly (before trying these updates, with the initial build I had sound and there were no random power-offs).
Any suggestion would be appreciated.
I also wanted to de-brand my i8730 and had similar issues as you. I tried 4 different firmwares, and the only firmware that really works OK is the original, branded one. With other firmwares (same version, same country but different branding) got me the occasional shutdowns like you described and wifi constantly disconnecting and connecting again.
Now I went back to the XWAMB8, rooted the phone and with Titanium Backup removed all the branded apps.
If you don't want to root your device you can always hide the apps, from the app list click on the Menu button and choose the option Hide applications.
Isn't that weird? I had a lot of Samsung smartphones and flashed a lot of firmwares (both stock and custom) and never experienced something like this. Can you tell me where you bought the phone from (what carrier and country)? Thanks.
ssweays composed
It is indeed very weird. My phone is branded to Portuguese Vodafone, I tried flashing other portuguese firmwares and also from other countries, the only stable one is the original one.
I think the phone is designed to be like that.
Sent from my GT-I8730 using xda-developers app
It is happened to me too, this power of thing in XWAMC4 firmware. (it is happened after less then 5 minuts after i turned out the screen)
finally i went back to the XWAMB8 and it's all work great.
No sound at all - not a problem in Australia
I updated and Optus branded i8730 with the plain vanilla variety and have had no problem.
Is your phone network locked?
99% sure mine is not and that may be what is causing it.
Bazzan
Well, it was a Vodafone Romania firmware but not really branded. I mean, it only had some apps installed by Vodafone. However, I'm getting my hands on an unbranded grey Galaxy Express today. Let's see what's going to happen with this one..
Something similar happened to me. I rooted it via motochoper from my linux desktop. Played a bit with root stuff, and later then I had no sim detection and no more speaker sound. I reflashed /system and got sim detected but still no speaker sound. Now I'm affraid of rooting the new one (I got lucky with my carrier). Something is weird about that phone...
Edit: In fact it seems to be TB that messed up the device... Everything fine now...
viges666 said:
Something similar happened to me. I rooted it via motochoper from my linux desktop. Played a bit with root stuff, and later then I had no sim detection and no more speaker sound. I reflashed /system and got sim detected but still no speaker sound. Now I'm affraid of rooting the new one (I got lucky with my carrier). Something is weird about that phone...
Edit: In fact it seems to be TB that messed up the device... Everything fine now...
Click to expand...
Click to collapse
I've got the same problem, no sound, when i call someone i can't hear the voice of my friend.
Base band version : I8730XWAMB7
Kernel version: 3.4.0-100842
[email protected]#1
Version number: JZO54K.I8730XWAMB8
Do you have any soluce to fixe this probleme ?
Thanks a lot
Wipe and full reflash with odin or heimdall...
Try full wipe and full reflash of original firmware with odin or heimdall...
Does somebody was able to flash a ROM released for a different carrier and still have sound working on this phone?
I either have no sound at all (after burning a new ROM for different carrier) or have strange sound (like "ET call home" - not my problem description, just found it on this forum too) after mixing new ROM with my original MODEM file.
Of course, everything is fine after burning back my original ROM.
ionutzm05 said:
I have a problem with my Samsung Galaxy Express (GT-I8730), international version.
I updated my firmware using Odin to a newer build. The firmware was downloaded from SamFirmware.com.
After the update finished and my phone restarted I've got no sound at all. I tried doing a factory reset but no luck. I thought the firmware was corrupted and after downloading and installing a new one, the exact same thing happened.
In the video posted below I am doing a factory reset from recovery, just to show you that I'm doing everything from the beginning.
The phone vibrates but there is no sound.
Before the update I had build version : I8730XWAMB8. After the update I tried with : I8730XWAMD7 and I8730XWAMC4. All these builds have the version number 4.1.2.
If I reinstall the I8730XWAMB8, I have sound but this build is branded and I'm very mad that I can't install other versions. This thing won't happen on my Note 2. I can install what firmware I want from SamFirmware.com.
I also saw that with all these builds my phone will randomly power-off at different times. It can be 5 minutes after I turn it on or it can be 18 hours. After the power-off I need to take out the battery.
What is wrong with the phone? Before these updates everything worked perfectly (before trying these updates, with the initial build I had sound and there were no random power-offs).
Any suggestion would be appreciated.
Click to expand...
Click to collapse
I have this exact same problem!! Ughh.
Any fix?
Flash I8730XWAMK1, will work and you will not have the brand logo. I use this one and is perfectly ! Good Luck ! :good::good:
hi All
have the same problem
original firmware is AP I8730XWAMB8 / CP I8730XWAMB7 / CSC I8730BOGAMB1
phone freeze , restart , no sound ..........
Solved with I8730XWANE1_OXXANF1 , all is OK , sound OK
After I flashed LineageOS 14.1 for GT-I8730T (mine is GT-I8730) the sound doesn't work, video player and music players too, they open and I can fast forward it, but it doesn't play. I changed it back to I8730UBAMD2 and CM 13.1 but nothing. Please help me!
Since I'm experiencing a lot of glitches with Android 7, I want to downgrade my phone to android 6 B10, hoping this will stop malfunctioning.
I downloaded the update B10 from the ZTE website and placed it on my sd card.
System Update finds the update, if I press update, will this downgrade my phone without bricking my device?
I know I will lose my internal memory but will I keep my EMEI info and sd card memory?
It won t harm your phone. It will just downgrade.
sent from zte axon 7 with tapatalk
If fully stock, I don't think you'll be able to downgrade to MM. Lemme know if you are successful though!
oleung4 said:
If fully stock, I don't think you'll be able to downgrade to MM. Lemme know if you are successful though!
Click to expand...
Click to collapse
You can downgrade without problems. I've done it a few times already (from 7.1.1 b01). I'm full stock, locked bl and unrooted.
I downgraded today, not without problems. It rebooted fine, than went back to the Axon screen, vibrating sometimes, so it was some sort of bootloop. I went into recovery mode and did a factory reset. After, it restarted and worked fine, I'm now back on android 6 with a factory reset, unfortunately, for me, problems from Nougat update still persist.
Mysteryman22 said:
I downgraded today, not without problems. It rebooted fine, than went back to the Axon screen, vibrating sometimes, so it was some sort of bootloop. I went into recovery mode and did a factory reset. After, it restarted and worked fine, I'm now back on android 6 with a factory reset, unfortunately, for me, problems from Nougat update still persist.
Click to expand...
Click to collapse
Which problems?
Anyone managed to do this downgrade successfully with stock rom not rooted? I dont have my country language to choose after latest nougat update.
Edit:
I managed to downgrade to b10 V1.0. Because of the Nougat update I was not able to update via external SD card although my card was 64GB.
I unzipped the file and placed it to root of internal SD. Did the normal update via settings and all went fine until it started to boot.
Somehow it asked password which I thought it was normal unlock code which i had placed previously, it wasn't.
Factory reset via recovery cleared that problem. All running normally now with marshmallow...
There is not much experts here to just to compare op3 Devs..
Mysteryman22 said:
Since I'm experiencing a lot of glitches with Android 7, I want to downgrade my phone to android 6 B10, hoping this will stop malfunctioning.
I downloaded the update B10 from the ZTE website and placed it on my sd card.
System Update finds the update, if I press update, will this downgrade my phone without bricking my device?
I know I will lose my internal memory but will I keep my EMEI info and sd card memory?
Click to expand...
Click to collapse
i want to downgrad like my phone without unloacking bootloader but from oreo to marshmallow , help me please how did u do that and if u do that without unoacking bootloader , my phone is "zte axon 7 a 2017 g"
joaste said:
You can downgrade without problems. I've done it a few times already (from 7.1.1 b01). I'm full stock, locked bl and unrooted.
Click to expand...
Click to collapse
tell me please can i downgrading from oreo to marshmallow on my phone a2017g without unloack bootloader !!
joaste said:
You can downgrade without problems. I've done it a few times already (from 7.1.1 b01). I'm full stock, locked bl and unrooted.
Click to expand...
Click to collapse
please tell me the version that u used and from where if u can give me the link ,
hey guys
i just brick my phone (no idea how, flashed android 7 firmware) after flash my phone was working for like 2 hours, then i let himself update a security options. After update my phone went brick
As far i found :
- installed Qualcoom QDLOADER 9008 driver
- found QFIL programmer
i need to have programmer path (something related to JTAG) and build xmp path
Where i can find them? Or is it a other way to resscue my phone?
I feel your pain. My timeline:
- The phone was unlocked but still in Stock Nougat (7.0?). Got that from OTA in Brazil.
- I tried to update to LineageOS 7 via TWRP. After a full wipe (everything, system, data, card, cache etc) I installed the new ROM. Turned on, bootlooped forever.
- Searching around I found out that there was no modem in the Nougat roms and for some reason I needed to flash a Marshmallow modem for my region to make that work (I think there is no Nougat modems around or something).
- I found a LA_DS modem for 6.0, flashed that using TWRP, still bootloop. Tried other roms using TWRP, still bootloop.
- I then downloaded a full stock old 6.0 firmware to go back to stock but the phone wouldn't accept some files ("preflash validation failed").
- Searched around and found out that you can't downgrade a bootloader from Moto.
- Using fastboot, I flashed the files the phone was willing to accept and it finally booted the 6.0 Marshmallow stock rom, but with no networking (radio/modem/baseband/IMEI missing).
- Flashed the 6.0 modem for my region again and everything worked. Connected on WiFi, dual sim cards detected etc.
- I started to install every update the phone showed to try to update it back to latest MM version.
- The three first updates went ok, the fourth turned off the phone to never turn on again.
Looks like there is no way out of this. My phone is pretty old and MotoCare in Brazil will charge a lung and a half for repair.
dsnunes said:
I feel your pain. My timeline:
- The phone was unlocked but still in Stock Nougat (7.0?). Got that from OTA in Brazil.
- I tried to update to LineageOS 7 via TWRP. After a full wipe (everything, system, data, card, cache etc) I installed the new ROM. Turned on, bootlooped forever.
- Searching around I found out that there was no modem in the Nougat roms and for some reason I needed to flash a Marshmallow modem for my region to make that work (I think there is no Nougat modems around or something).
- I found a LA_DS modem for 6.0, flashed that using TWRP, still bootloop. Tried other roms using TWRP, still bootloop.
- I then downloaded a full stock old 6.0 firmware to go back to stock but the phone wouldn't accept some files ("preflash validation failed").
- Searched around and found out that you can't downgrade a bootloader from Moto.
- Using fastboot, I flashed the files the phone was willing to accept and it finally booted the 6.0 Marshmallow stock rom, but with no networking (radio/modem/baseband/IMEI missing).
- Flashed the 6.0 modem for my region again and everything worked. Connected on WiFi, dual sim cards detected etc.
- I started to install every update the phone showed to try to update it back to latest MM version.
- The three first updates went ok, the fourth turned off the phone to never turn on again.
Looks like there is no way out of this. My phone is pretty old and MotoCare in Brazil will charge a lung and a half for repair.
Click to expand...
Click to collapse
Pretty similar situation on my part. I downgraded back to 6.0 and when it tried to take the December update I ended up with the same thing as you. I ended up getting a replacement from Moto for under 100 dollars which was worth it rather than trying to find a solution that doesn't exist.
Hello, i have a Moto g4 Amazon edition (XT1625) and all of a sudden, it got into a bootloop for no reason. it is not bootloader unlocked, not rooted, totally stock. so i did some research and tried some things, wiping cache, wiping data and nothing. so my next bet was to try to flash the same firmware or anything that would make the phone Boot up.
I tried flashing the 6.0 firmware, 7.0 firmware, at least, i tried 6-7 different firmware with no success (all of them said pre-validation error, like i was trying to flash a older version) but one. the only one that actually flashed, got me booting into recovery saying "this is an unauthorized sw" and that's it.
i got another exact same phone fully working and i noticed it recieved the OTA update NPJS25.93-14.7-3 and as far as i know this the December Security patch.
is there any link to download the full ROM with this update? or the September 2017?
i'm guessing those are the only firmware that could resurrect this phone right now...
Try this link for stock firmware
https://firmware.center/firmware/Motorola/Moto G4 (Plus)/Stock/
Thanks for the reply.
i downloaded the rom and tried flashing it without the .gpt and the bootloader.img for safety reasons...
it flashed all okay and when it booted it shows the moto logo and turns off every time i try to turn it on... if it's connected to my computer, it just reboots into boot logo.
and yes, i then tried flashing the rom with the .gpt and bootloader file and no result.
is there any way i can fix this bootloop?
this was actually the first problem the phone had, no root, no unlocked bootloader and all of a sudden went into bootloop..
mtvictor said:
Thanks for the reply.
i downloaded the rom and tried flashing it without the .gpt and the bootloader.img for safety reasons...
it flashed all okay and when it booted it shows the moto logo and turns off every time i try to turn it on... if it's connected to my computer, it just reboots into boot logo.
and yes, i then tried flashing the rom with the .gpt and bootloader file and no result.
is there any way i can fix this bootloop?
this was actually the first problem the phone had, no root, no unlocked bootloader and all of a sudden went into bootloop..
Click to expand...
Click to collapse
You found some solution, I have the same problem.
mauri550 said:
You found some solution, I have the same problem.
Click to expand...
Click to collapse
Nothing has worked so far, the phone is laying like a brick for the moment.
Hi devs,
My Moto G4+ was having some battery issues like it abruptly got switched off even if it had 80+% charge and I had to keep it in charge all the time. I thought it was some OS issue. Recently, Oreo OTA update came and I updated the phone but still the issue persisted. So, day before yesterday, similarly, the phone got switched off and I was not in a situation to plug it on charge. I came back home, plugged it to charge and switched on the phone. It got stuck in the Lenovo logo but the important thing is that messages and calls are coming, even I can attend calls but I can't enter into the OS. "Hey Google" command also works but the answer to the query is "phone is not getting signal" something like that. I suppose this might be some boot animation issue. Is there any way that I can flash the stock Oreo Update again without loosing my data? I somehow want my data back. Please help.
Thanks in advance.
Akhil_Vijay said:
Hi devs,
My Moto G4+ was having some battery issues like it abruptly got switched off even if it had 80+% charge and I had to keep it in charge all the time. I thought it was some OS issue. Recently, Oreo OTA update came and I updated the phone but still the issue persisted. So, day before yesterday, similarly, the phone got switched off and I was not in a situation to plug it on charge. I came back home, plugged it to charge and switched on the phone. It got stuck in the Lenovo logo but the important thing is that messages and calls are coming, even I can attend calls but I can't enter into the OS. "Hey Google" command also works but the answer to the query is "phone is not getting signal" something like that. I suppose this might be some boot animation issue. Is there any way that I can flash the stock Oreo Update again without loosing my data? I somehow want my data back. Please help.
Thanks in advance.
Click to expand...
Click to collapse
Hey mate!
Regarding that switching off issue that's a battery issue you need to change the battery with a new one and about flash stock oreo again yes you can flash I am attaching the link to stock oreo firmware and just don't run the fastboot erase userdata command and you'll have your data.
https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
And here's the link to the stock firmware flashing guide/helping thread https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
aadityaraj1 said:
Hey mate!
Regarding that switching off issue that's a battery issue you need to change the battery with a new one and about flash stock oreo again yes you can flash I am attaching the link to stock oreo firmware and just don't run the fastboot erase userdata command and you'll have your data.
https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
And here's the link to the stock firmware flashing guide/helping thread https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
Click to expand...
Click to collapse
Thank you mate, it was indeed battery issue. The problem is solved. Actually the battery is bulged and when I took it to the service center (Not authorized) they just removed the battery and re-installed it and it just booted up as normal. They said I need to change the battery. Thank you for the reply and the link shared.