Hello I am still dealing with a weird problem that I posted on this forum over a year ago that was never resolved. Basically my tablet is stuck running Android version 4.1.1 (Build JRO03C.US_epad-10.4.4.25-20121228) because if I upgrade to any new versions (whether I do it as OTA or via micro USB) my wifi card stops functioning (it does not see any networks). Anyways I even went so far as to RMA it and Asus said they fixed it, shipped it back to me, but in reality all they did was roll me back to 4.1.1, saw the wifi was working and shipped it back to me saying they "fixed" it. Well of course the second I got it back I installed the OTA and wifi broke again... So I just rolled back to 4.1.1 and said screw it, I just won't update it anymore. Well this week I figured I'd try installing the latest OTA and hoped that this version would not kill my wifi, unfortunately the same exact issue has occurred and thus I have once again rolled back to v4.1.1 and my wifi works perfectly...
TLDR; Anyways apologize for the rant/story but basically I am stuck with using version 4.1.1 of Android and am considering flashing a custom rom to try and resolve some issues I am having with the stock rom's wifi, however the official bootloader unlock tools only say they work on version 4.0 (ICS) or version 4.2 (JB). I'm stuck on v4.1.1 so which tool should I use (or am I out of luck)? Thanks
v7 worked your JB version, but I think v8 will work as well. Just try them both - it's just an app. Either it works or not....
But that is the weirdest thing I've heard in a while (reg. WiFi).
What have you done on your router side? I cannot believe this is a problem with the tablet's wifi card.
Is this 'wifi not working' consistent on any router, any network?
Did you reset the router, change the channel?
Do you have possible interference: microwave, bluetooth speakers, bluetooth enabled or any other device that uses radio waves anywhere in the vicinity of the tablet?
berndblb said:
v7 worked your JB version, but I think v8 will work as well. Just try them both - it's just an app. Either it works or not....
But that is the weirdest thing I've heard in a while (reg. WiFi).
What have you done on your router side? I cannot believe this is a problem with the tablet's wifi card.
Is this 'wifi not working' consistent on any router, any network?
Did you reset the router, change the channel?
Do you have possible interference: microwave, bluetooth speakers, bluetooth enabled or any other device that uses radio waves anywhere in the vicinity of the tablet?
Click to expand...
Click to collapse
Thanks appreciate the reply - I just wasn't sure if using the wrong unlocker could brick my device... I'll give 8 a try first then 7 if necessary. The ironic part is that it requires a network connection to complete the unlock operation (I guess so Asus can cross your S/N forever off of their list of devices under warranty).
I agree that this is a strange problem as I have not seen anyone else report it. Basically I tried resolving this about 13 months ago with the help of this board and as mentioned I finally had to RMA it, but ASUS just rolled the version back instead of fixing anything and at that point I just wanted to enjoy using my tablet more than I wanted to fight with ASUS's customer service reps who effed up the first RMA job (the language barrier was also apparent in my interactions with them)...
Since over a year has gone by since the last time I tried an OTA, I hoped that the latest update would not have the same issues but alas, I'm not that fortunate.
As far as what I've tried - I have tried connecting to different networks and changing router channels and checking for interference, but the thing is, I'm quite certain the problem is with the tablet. When I first had the problem I lived in an apt building where I could 'see' 10+ wifi networks at any given time on all different channels with different routers/security settings etc. As soon as I applied the OTA the tablet could no longer 'see' any of them (even as I sat with my laptop/phone connected to wifi right next to it). I now live in a house (and have a different ISP, and a different router) and tablet works perfectly when on version 4.1.1. I don't have as many wifi networks visible from my house, but can still see a few of my neighbor's wifi networks both on the tablet (v4.1.1) and on other devices. But the second that I upgrade, all of them disappear from the tablet's view (but continue to be visible/work on other devices). I have turned wifi on/off, turned airplane mode on/off, tried connecting via wifi direct, rebooted, cold booted, booted into recovery, factory reset all data, etc. but nothing works because the tablet cannot see any wifi networks. And the second that I rollback to version 4.1.1 the wifi works perfectly... I have upgraded and rolled back probably at least 6 times and it is always the same result.
I do also get another weird side affect when I upgrade - the tablet refuses to turn off when I'm on any version higher than 4.1.1. So if I press "Shut Down", the tablet displays "shutting down" and the screen goes black and becomes non-responsive (as do the buttons, just as you would expect when turning off), but it does NOT actually shut down because if I come back 30 mins, an hour, 2 hours later I can feel it running very hot. The only way to truly shut it down is to let the battery drain...
So maybe a better question on my part would have been, do you think installing a custom ROM will even help resolve this issue? Or should I continue using 4.1.1 and not risk making the situation worse with custom ROMS?
WiFi problems are often kernel related..... Did you always take the update OTA?
Did you ever try to flash the latest firmware version manually? OTA updates do go wrong sometimes....
Although repeatedly???? It's weird. Maybe the server your tablet pulled the OTA from hosts a bad copy????
If you do not want to unlock, manually flashing the firmware would be one thing to try. OTA's patch the existing system, replace old files with new ones where necessary. Manually flashing the firmware replaces everything - a totally new installation of everything: bootloader, recovery, kernel, system and data.
But you cannot make it worse by flashing a custom rom. You unlock, flash a custom recovery (which does not change anything else on your system), then you make a nandroid (backup) of your current 4.1.1 system before you flash a rom. So you would always be able to go back to where you are now. On a custom rom you could even try out different kernels, which often are the root cause of wifi problems..
The thing is: If you want to flash a current custom rom like CROMi-X, based on Asus JB 4.2.2, or CROMBi-KK/CM11 which are KK roms, you always have to update your bootloader first. Your .25 bootloader is too old for any current rom.
You can easily do it once you have a custom recovery installed, but even easier would be to update to the latest Asus firmware 10.6.1.14.10 (after unlocking), then flash the custom recovery (TWRP 2.8.1.0), then flash a rom of your choosing.
Downside of this route would be you wouldn't have that 4.1.1 nandroid I mentioned earlier.....
Nahhh - thinking about it, I would recommend you go this route:
Unlock,
flash an older version of TWRP compatible with your current bootloader (TWRP 2.6.1.0 is ok)
make a nandroid of your current system
do a full wipe of cache, Dalvik and data in recovery
flash the 10.6.1.14.10 bootloader in recovery (I can talk you through it)
flash TWRP 2.8.1.0
flash a rom of your choice
Check out my guide, link in my signature, and let me know if you have questions
Thanks - I was able to successfully unlock my device with v7 of the unlock tool (v8 wouldn't even install). Thanks too for the advice on how to flash a custom rom safely. I've never flashed a custom rom before (have rooted a different android device before tho), so I appreciate any help.
I downloaded the blob file for TWRP 2.6.1.0 from here (techerrata.com/browse/twrp2/tf700t), but not sure how to proceed next, (also I don't see a link in your signature to your guide, but I am running a bunch of script blocking addins so maybe that's why) seems like all the guides I am finding say I need to get a copy of a fastboot program (but don't provide links), where can I find that? Again, I appreciate the help.
Sorry, my bad, I don't have a signature on XDA - wrong forum. LOL
My thread is here: http://forum.xda-developers.com/showthread.php?t=2688891
Ask any questions you may have in that thread, but it should cover your questions - I hope
Q&A for [ROM][5.X][XT1028/XT1031] CyanogenMod 12.1 for Moto G [METICULUS]
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROM][5.X][XT1028/XT1031] CyanogenMod 12.1 for Moto G [METICULUS]. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
no calls or data
I have an xt1031 flashed to page plus. I have bootloader 41.19 from a failed lollipop update attempt. I flashed the 4/8 build and I can't make calls and do not have 3g. The network shows as 31000. What should I do?
I have been trying each of his builds and anything newer than 4/8 data hasnt worked I'm on boost if that makes any difference
Verizon?
Good morning,
I'm on an XT1028 still with service through Verizon Prepaid; my bootloader is unlocked and I'm on an optimized KK stock ROM at the moment. I've been following the development of Meticulus' CM12.1 through the primary thread and there has been a lot of discussion as to problem solving and issues on the XT1031 and various carriers but little mention as to the status of the latest weekly builds on the XT1028 still on Verizon in terms of functionality or hiccups from users. Does anyone have the latest versions running on their 1028? Are any of the data or service issues present when running it on Verizon?
Thanks.
Followup: Installed the latest 4/25 weekly on my XT1028 on Verizon Prepaid. Installed fine, got phone and SMS, but the network is identified as Boost Mobile and I have no mobile data. Is there a fix? Is a build.prop edit necessary for Verizon? Thanks.
Reboot then bootloop
Hi, I've been trying to get my installation of this ROM working for two days now, but keep running into an issue that I cannot seem to solve
My device is a 2013 Moto G XT1031 (Boost Mobile) with Bootloader version 41.05 and the latest CWM recovery.
The issue has been occurring on build 4/8, 4/25, and 5/2.
The exact steps I have been taking to install this ROM (for all builds) and then what happens:
Bootloader is unlocked
Going into recovery and wiping dalvik cache then factory reset (wipe)
Installing CM11 (latest snapshot) [on my first attempts only, not afterwards since it made no difference anymore]
Factory reset again (just to be certain)
Installing the zip for a build specified above
Installation always succeeds with no errors
Installing gapps-L-3-28-15 with success
Reboot into android
First boot always succeeds (and takes appropriate length of time)
Set up the phone (connect to wifi, google account, restore my apps [18 of them, just common popular ones, mostly Google actually], and apply a theme
Use it for a couple minutes (enable root and usb debug in Developer Settings, set my apps up, etc)
Restart two or three times without any hiccups
Suddenly, after a random reboot, the boot animation happens twice (instead of only once how it supposed to be)
Phone boots and shows "Android is starting..." and optimizes the apps (104 of them) one by one
Goes to "Starting apps..." and succeeds
The phone shows the lockscreen, but only for approximately 1-2 seconds
Phone reboots
CM boot animation runs twice, once for a long time then again for a shorter period of time
Phone goes through process described above (Android is starting, optimizes, then flashes lockscreen)
This just happens again and again and again
Steps I've taken to try and remedy the issue:
Run: "adb reboot" from computer while phone is optimizing apps
Hard reset the phone by holding the power button for 15 seconds
Run: "adb reboot bootloader" from computer when possible, then go into recovery and wipe both dalvik and normal cache
Swipe on the lockscreen as soon as I see it to see if I can get in (lockscreen does not respond though)
Go into recovery and shut the phone off, then start again
Let it loop for about 2 hours
I had also tried leaving the phone overnight looping, and when I woke, it was still looping, but after a eight or so more hours, I came back and found that it had booted and stayed on (and was working completely normally).
The phone was running stock 4.4.2 completely fine before this (with no reboot issues). I attempted installing the latest version of BlissPop, which exhibits a similar but still different issue (it would always boot into android [and not loop], but after a couple restarts, it showed an error about the System UI crashing that would pop up every time I dismissed it, and continued doing so after each restart after that). CM11 seems to be running well on the phone (but only in my very limited test while transitioning between ROMs and such).
I unfortunately cannot provide a log due to not being able to run any logging app during bootup, but hopefully I have provided enough details above to allow understanding of the issue and maybe bring suggestions on how to fix it. I can provide any more information needed on request. I really would like to get this phone back up and running (and especially on this ROM as I do love the work the creator has put into it).
Sorry for the very large wall of text :| Thank you in advance for any suggestions on how to proceed from here
tartilc said:
My device is a 2013 Moto G XT1031 (Boost Mobile) with Bootloader version 41.05 and the latest CWM recovery.
Click to expand...
Click to collapse
Having not experienced your issue I can't say for certain, but it may be possible you need to update the bootloader to at least 41.13, which is the 4.4.4 KitKat BL? I'd run it past @Meticulus and see if he might have some direction, there. Also, does the theme you apply have a different bootanimation, by any chance? There is a known issue/potential memory leak related to large boot animations on Lollipop that can cause failures at boot or bootloops.
a_gert said:
Having not experienced your issue I can't say for certain, but it may be possible you need to update the bootloader to at least 41.13, which is the 4.4.4 KitKat BL? I'd run it past @Meticulus and see if he might have some direction, there. Also, does the theme you apply have a different bootanimation, by any chance? There is a known issue/potential memory leak related to large boot animations on Lollipop that can cause failures at boot or bootloops.
Click to expand...
Click to collapse
Thank you for the advice I have downloaded a file with the name of falcon_boost_user_4.4.4_KXB21.14-L1.57_57_release-keys-cid9.xml.zip, unzipped it, then flashed according to the directions posted on how to restore the stock firmware. Everything during installation seemed to go smoothly, but at this point, I am stuck again. When I try to boot up, it just shows the splash screen ("Warning Bootloader Unlocked") and stays there indefinitely :| I have hard reset the phone and got into boootloader, which states that I am now on 41.13, but it just stays at that splash screen Should I boot into TWRP and try flashing an update.zip of the stock 4.4.4 Boost ROM? What else can I try?
EDIT: Flashing the stock update did not work, but I was able to install CM11 (so I'm am on bootloader 41.13 with CM11 currently)
EDIT TWO: Yes! I'm on bootloader 41.19 now and official CM12.1 nightly is booting!!
EDIT THREE: NOOOO It just started bootlooping again! CM animation twice, "Android is starting...", lockscreen, then cycle again. It happened after I changed my DPI from 320 to 280 (never restarted, just looped from then on).
I now have a logcat! I'm having trouble understanding what it is talking about, but I started logging as soon as the "Android is starting..." box changed status from "Optimizing apps x of x" to "Starting apps" and then stopped logging after a couple seconds of the boot animation. It is attached below (split into three parts).
EDIT: Attached what might be a better logcat reading (recording started right before lockscreen showed, I tried unlocking it, then stopped as soon as I saw the blue animation)
tartilc said:
Thank you for the advice I have downloaded a file with the name of falcon_boost_user_4.4.4_KXB21.14-L1.57_57_release-keys-cid9.xml.zip, unzipped it, then flashed according to the directions posted on how to restore the stock firmware. Everything during installation seemed to go smoothly, but at this point, I am stuck again. When I try to boot up, it just shows the splash screen ("Warning Bootloader Unlocked") and stays there indefinitely :| I have hard reset the phone and got into boootloader, which states that I am now on 41.13, but it just stays at that splash screen Should I boot into TWRP and try flashing an update.zip of the stock 4.4.4 Boost ROM? What else can I try?
EDIT: Flashing the stock update did not work, but I was able to install CM11 (so I'm am on bootloader 41.13 with CM11 currently)
EDIT TWO: Yes! I'm on bootloader 41.19 now and official CM12.1 nightly is booting!!
EDIT THREE: NOOOO It just started bootlooping again! CM animation twice, "Android is starting...", lockscreen, then cycle again. It happened after I changed my DPI from 320 to 280 (never restarted, just looped from then on).
Click to expand...
Click to collapse
Whoa, that's a lot of jumps! Be careful with the bootloader, as once you're on the Lollipop BL (and it appears you've already made that jump), you're kind of locked into LP ROMs from this point out. The point you were failing on the 4.4.4 stock would probably have been a good time to go in and manually restore things via fastboot just to make sure all your partitions were straight. What did you use to update your bootloader to 41.19? And have you tried a ROM specifically designated for the CDMA-only XT1031/Boost? I've only used the Meticulus and the unofficial Linaro CM12.1 buld by Cody on my XT1028 specifically because I know they're CDMA compatible, so I'm not sure where the official CM12.1 sits on that right now.
I know there exists an actual legitimate stock 5.0.2 Boost ROM and it's possible that may be able to be restored manually as a last resort, so don't move too hastily.
XPOSED on Meticulous Rom?
Is there any way to get XPOSED working? I really want gravity box for LL.
Awesome. I was going to download this from your site today but it is showing an error with connecting to its database. None of the computers i have access to can get on your site.
no wifi no cellular network
and after i flashed cynogenmod 12.0 in my moto g 2014, there is no wifi nor network :'( what am i suppose to do now?
Ui crash
Is there anything special i need to do to flash this update? i'm running on the 408 build and every time i try ti go the next version there is an issue. Either data stops working or i get a system Ui crash like on the 530 build. I would love to get this issue fixed with the 606 build. Besides that, great job.
a_gert said:
Whoa, that's a lot of jumps! Be careful with the bootloader, as once you're on the Lollipop BL (and it appears you've already made that jump), you're kind of locked into LP ROMs from this point out. The point you were failing on the 4.4.4 stock would probably have been a good time to go in and manually restore things via fastboot just to make sure all your partitions were straight. What did you use to update your bootloader to 41.19? And have you tried a ROM specifically designated for the CDMA-only XT1031/Boost? I've only used the Meticulus and the unofficial Linaro CM12.1 buld by Cody on my XT1028 specifically because I know they're CDMA compatible, so I'm not sure where the official CM12.1 sits on that right now.
I know there exists an actual legitimate stock 5.0.2 Boost ROM and it's possible that may be able to be restored manually as a last resort, so don't move too hastily.
Click to expand...
Click to collapse
Yeah that is a lot of jumps I'd be hella nervous myself lol
K well guys today is your day , as a_gert stated there is a boost 5.02 , and it does work fine on any cdma xt1031 so first flash that
-depending on signal you may wish to update your modem also there is only 4.4 modem for boost public
Buuuutttt nvm all that for now
The problem the ONLY problem I have had when bootlooping was that it was not prepped correctly and my phone came with 41.19 and came unlocked-
1.) Make sure you are on c/O SuperR-Developer -- PhilZ-Touch-6.59.0_LPK .img OR twrp * twrp-2.8.6.0.1-falcon_STOCK.img
**Notice For Even PhilZ I only Named the -IMG- Version which means flash it with adb properly please
***if ever after you flash it via recovery it will show partition mismatch which apparently is no problem just that the custom recovery does not match the factory one is all.. ..
1.) Download PhilZ-Touch-6.59.0-LPK.img to PC
2.) Reboot to bootloader
3.) Plug phone into PC
4.) Open terminal in directory where the img is located
5.) Issue the following command:
Code:
fastboot flash recovery twrp-2.8.6.0.1-falcon_STOCK.img
2.) Do a format of System w/EXT4 AND REBOOT INTO RECOVERY
3.) Format dalvik/art + Cache + Data w/EXT4 & REBOOT INTO RECOVERY
4.) Format Data PLUS data/media with f2fs then Do the 'factory wipe' then manually format data/media with f2fs again please ..
- SIDELOAD THE ATTACHED STOCK LOLLIPOP NO GAPPS GIVE IT TEN MINUTES REBOOT FEW TIMES/ POWER DOWN ONCE & REBOOT AGAIN
5.) Reboot into recovery and flash the first zip I have attached (I_nomodem is just IF you find your 4.4 radio baseband worked better and want to format it for LP again in the future WITHOUT LP radio included)
****EDIT - SEE VERY BOTTOM OF POST CENTERED AREA LOL
6.) Power off & reboot into recovery manually
7.) Flash your Rom (OR STOCK LOLLIPOP DEBLOATED AGAIN) + Kernel(if any custom one) + Gapps -wait 5-15 minutes for initial boot
* I recommend AeroKernel for the included stock lollipop 5.0 debloated if not the stock kernel or after flashing and few reboots to settle ,just follow instructions from that thread if any are needed..
Please anyone with any moto g don't think updating your bootloader is needed or even really safe whatsoever it is THE main reason moto phones get bricked or messed up otherwise it is not necessary or any kind of improvement yes once you are on an LP one leave it be..
Other flashing yeah okay, bootloader no if so proceed with utmost caution.
After this your modem will be updated with the cdma LolliPop one, if you have any signal issues or what not go to the stock modems section for your specific phone and flash the one for your specific carrier and/or find the "update RIL" flash thingie on here in moto G section and follow instructions but the boost modems work on all cdma variants of Moto G..
For whatever reason I could not upload files to xda I tried five times it kept dying so here there are on googldrive :good:
**Do not Click individual Item Use the Download Arrow At the Very Top of Page to DL the zip properly plz
1.) Falcon LolliPop Part Updater + Modem
2.) Falcon LolliPops Part Updater (No Modem)
_____________________________________________________________________________________________________________________________
--EDIT #2-- LolliPop 5.0 Falcon XT1031 debloated
SIDENOTE: IF YOU FORMAT DATA/MEDIA & DO NOT KNOW HOW TO SIDELOAD THE ABOVE STOCK DEBLOATED ZIP I'M PRETTY SURE YOU'RE NOT GONNA LIVE TO TELL BOUT IT
BE PREPARED TO SIDELOAD - REBOOT IMMEDIATELY AFTER SIDELOAD THE ZIP ROM IS COMPLETE NOT INTO RECOVERY NOT ANYWHERE ELSE SYSTEM REBOOT
-And wait 5-10 Minutes For First Boot - You Only Need to Do this for the first LP rom loadin after that normal flashing do NOT format data/media anymore after this initial setup
--You can try to just use the script, but it did not work for me after many tries the above was the real solution and has been perfect since
2,3,4,5,6,7
·Install flashable (Boost Mobile/CDMA XT1031 only):
·Download falcon_PhilZ-Touch-6.59.0_LPK.zip to phone
·Reboot into current custom recovery
·Flash zip
·Enjoy!
Use the script again to prepare you partition properly anytime you are about to flash a new rom clean after factory wipe/ format is done..
As I said before data/media is never necessary again after this and MAY not be this time but it is the only thing that kept me out of bootloops ,and if you do it yeah it will force you to sideload your rom it erases all leftovers and your rom zips off the internal card and formats them for fresh start The script does not format /media guys k no worries
------TWRP 2.8.6..1 does not seem to restore properly- -system write only thing .. PhilZ-Touch is fine as is twrp-2.8.6..0 also
Nice, got 41.19 BL!
I tested this and works fine, now i have my shiny new moto g running AICP. Thanks @shoobiedoobiiwhompwop!
rammsteinaus said:
I tested this and works fine, now i have my shiny new moto g running AICP. Thanks @shoobiedoobiiwhompwop!
Click to expand...
Click to collapse
K welcome
Arrite guys for a little clearer step by step see here please apologies carrying on and on I have been gone quite some time here http://forum.xda-developers.com/mot...-moto-g-xt1031-lollipop-t3132974#post61346260
It actually Runs really nice, really REALLY nice once the system app package I am adding shortly was used and tweaked out ..
Is it safe to flash cyanogenmod onto the verizon moto G - 1028 4.3 plus
Hello community ,
I had serious problems flashing cyanogenmod onto a galaxy S3 that was running stock 4.3 , verizon bricked my S3 , and said that the software was not authorized by Verizon. Does this problem exist across the board for any verizon phone running 4.3 or higher ?? If so ... then anything to do with flashing cyanogenmod onto a verizon phone should have warnings in BIG RED LETTERS ... because you cannot even buy a new phone with 4.2 on it anymore.
Issues flashing cm12.1 on XT1031 Please Help
Tried flashing the second to last release on 2 of my moto g xt1031's and I keep getting diff issues. This is what I did:
I had complete stock 4.4.4
unlocked bootloaders,
flashed latest TWRP,
Did a factory wipe
Flashed CM12.1
Flashed Gapps
Rebooted
Stuck in boot loop--> waited over 30mins and rebooted a few times. No luck.
I heard to try flashing CM11 first, then flashing 12.1 so I did this:
Back to TWRP -->factory wipe
Flash cm11
reboot to cm11
reboot to TWRP -->factory wipe
Flash CM12.1
Now I can get past the boot logo and begin setup, however, it will randomly reboot to the boot logo and then back to setup after a minute or so- erasing anything I've already input. Sometimes I could make it through the setup to the desktop, but then it would do the same thing. Had this same exact issue on both of my xt1031s with the same process used for both.
After this I tried doing a factory wipe and then also wiping /data and /system in the advanced wipe options and then flashing cm12.1 and still had the same issue of the rebooting. At some point I must have done somthing, but I started trying to just flash cm12.1 several times over to see if it would stick and I noticed when I did the factory wipe I was getting a parsing error so I tried doing a full data format, and fix data filesystem. I'm not sure what format it was supposed to be so I did a ex4. THat stopped the parsing error, but still having the same issues.. any help would be appreciated.
Moto G CDMA issues
citizen3rased said:
Tried flashing the second to last release on 2 of my moto g xt1031's and I keep getting diff issues. This is what I did:
I had complete stock 4.4.4
unlocked bootloaders,
flashed latest TWRP,
Did a factory wipe
Flashed CM12.1
Flashed Gapps
Rebooted
Stuck in boot loop--> waited over 30mins and rebooted a few times. No luck.
I heard to try flashing CM11 first, then flashing 12.1 so I did this:
Back to TWRP -->factory wipe
Flash cm11
reboot to cm11
reboot to TWRP -->factory wipe
Flash CM12.1
Now I can get past the boot logo and begin setup, however, it will randomly reboot to the boot logo and then back to setup after a minute or so- erasing anything I've already input. Sometimes I could make it through the setup to the desktop, but then it would do the same thing. Had this same exact issue on both of my xt1031s with the same process used for both.
After this I tried doing a factory wipe and then also wiping /data and /system in the advanced wipe options and then flashing cm12.1 and still had the same issue of the rebooting. At some point I must have done somthing, but I started trying to just flash cm12.1 several times over to see if it would stick and I noticed when I did the factory wipe I was getting a parsing error so I tried doing a full data format, and fix data filesystem. I'm not sure what format it was supposed to be so I did a ex4. THat stopped the parsing error, but still having the same issues.. any help would be appreciated.
Click to expand...
Click to collapse
Hello Citizen 3 , You are farther along than me. I have only successfully flashed cyanogenmod once , and that was on an S3 so it was straightforward. I still have not unlocked my bootloader. I have not been able to copy and paste the long strings of characters from motorola , inside command prompt. It would be so nice if Meticulus or one of the other developers could get this to be an official release. The Moto G , and a few other inexpensive phones ( LG realm , Kyocera Hydro latest version ) would work like greased lightning , if they were running CM12. Any help that you could offer with pasting the strings of unlock code would be so appreciated.
[First time poster here, so please be gentle . Any forum ediquet faux pas are accidental, and great constructive feedback!]
Currently running XT1900-1 variant of Motorola X4. Currently does not have a SIM card (only used on wifi).
A couple weeks ago, I flashed a bad ROM (IIRC I flashed a non-Android One ROM) and got the device into a bootloop. Immediately upon doing so, I was pulled away from the device for around half an hour. Upon returning to the device, I flashed the stock Android One image, and started to go through the initial device setup. Once I reached the "connect to Wifi", the device couldn't find any wirelesss networks. Unfortunately there's no way to bypass this stage of the setup without either having a SIM card installed or connecting to WiFi, so i ended up stuck at this point without USB Debugging Enabled.
I have tried repulling & flashing the Stock ROM again (incase it got corrupted), but I hit the same problem. I then pulled and flashed the latest LegacyOS for the device, and was able to get through the initial setup process (you can skip WiFi and SIM setup) and enabled USB debugging to poke around.
Under LegacyOS, when I try to enable WiFi, the WiFi symbol lights up, but after about 15 seconds, turns off again. This kinda matches the observed behavior running the stock ROM, although I cannot confirm for sure. What surprised me was that the device was able to find Bluetooth devices, leading me to believe the wireless hardware isn't entirely toasted...
A quick look around this forum didn't reveal any similar sounding issues.
I'm currently looking for a DMESG log to from the stock ROM on an Android One device which I can compare against mine (obtainable from TWRP).
Any other additional debug ideas would be appreciated.
From what I have read, it's okay to flash a non-One fi ROM to a One fi phone, so that, in itself, shouldn't cause any problems.
Def flash the latest one from lolinet fi.
So you are saying that you have something transmiting wifi, like a router or somesuch? and the phone can't see it.
I would also encourage you to connect it to lmsa and see what rom it offers to flash and flash it.
lolinet fi: https://mirrors.lolinet.com/firmware/moto/payton/official/FI/
lmsa = lenovo motorola smart assistant: https://www.motorola.com/us/lenovo-motorola-smart-assistant
EDIT: check any command set you use to flash a rom to assure it does NOT have a command to relock the bootloader. DO NOT under any circumstances attempt to re-lock your bootloader!
After updated to Lineage 17.1 i am facing problems with Wifi. In Lineage 17.1 everything works fine (except wifi-calling and volte). When flashing back to Stock (via Oreo-RUU or TWRP Restore) i don't get any wifi-connection. If turning on wifi, system turns off immediately. In settings I found, that mac address is 02:00:00:00:00:00... searching this problem, i found out, that this problem happened often via update from android 5 -> 6. Flashing Stock ROMs didn't help, restore of prior LeeDroid Backup neither.
Did anybody face this problem in former times? Does anybody know where MAC is stored / what the problem may be?
masi79 said:
After updated to Lineage 17.1 i am facing problems with Wifi. In Lineage 17.1 everything works fine (except wifi-calling and volte). When flashing back to Stock (via Oreo-RUU or TWRP Restore) i don't get any wifi-connection. If turning on wifi, system turns off immediately. In settings I found, that mac address is 02:00:00:00:00:00... searching this problem, i found out, that this problem happened often via update from android 5 -> 6. Flashing Stock ROMs didn't help, restore of prior LeeDroid Backup neither.
Did anybody face this problem in former times? Does anybody know where MAC is stored / what the problem may be?
Click to expand...
Click to collapse
I am experiencing the exact same issue. Same MAC address, same wifi issue. I tried flashing to stock Oreo, same issue. I'm going to try flashing stock Nougat, but I have doubts about that working. I also tried clean flashing the RR-P 7.0.2 ROM, and the same issue happens there too. I could not fin a way to restore the MAC address. I was able to look up the original address from my router's device log . . .
My HTC is the US T-Mobile version. @Golv can you help us with this new issue?
-UPDATE-
So far, going to stock Nougat INSTANTLY works. Right on the setup menus, all the wifi networks show up. Odd how stock Oreo gave us issues, but Nougat didn't. Will be going to RR-P 7.0.2 and seeing if the fix sticks I removed the SIM card when I put the phone back to Nouagt BTW if that affects anything.
-UPDATE 2-
Flashed stock Oreo after flashing Nougat, and in the setup menus, the wifi networks are showing up in STOCK OREO. Still with SIM removed. Now to flash the RR-P rom and see if I'm all set.
-FINAL UPDATE-
Flashed RR-P 7.0.2. Everything is back to normal.
Ikarbb said:
I am experiencing the exact same issue. Same MAC address, same wifi issue. I tried flashing to stock Oreo, same issue. I'm going to try flashing stock Nougat, but I have doubts about that working. I also tried clean flashing the RR-P 7.0.2 ROM, and the same issue happens there too. I could not fin a way to restore the MAC address. I was able to look up the original address from my router's device log . . .
My HTC is the US T-Mobile version. @Golv can you help us with this new issue?
-UPDATE-
So far, going to stock Nougat INSTANTLY works. Right on the setup menus, all the wifi networks show up. Odd how stock Oreo gave us issues, but Nougat didn't. Will be going to RR-P 7.0.2 and seeing if the fix sticks I removed the SIM card when I put the phone back to Nouagt BTW if that affects anything.
-UPDATE 2-
Flashed stock Oreo after flashing Nougat, and in the setup menus, the wifi networks are showing up in STOCK OREO. Still with SIM removed. Now to flash the RR-P rom and see if I'm all set.
-FINAL UPDATE-
Flashed RR-P 7.0.2. Everything is back to normal.
Click to expand...
Click to collapse
Thank you very much! I checked whether the sim card has an effect, removed it and flashed Stock Oreo -> problem still exists. Then i flashed Nougat an experienced the same effect: Wifi worked right on the setup menu.
@Golv do you have any idea why this happens? I think, this problem should affect anybody, who wants to go back to prior versions.
masi79 said:
Thank you very much! I checked whether the sim card has an effect, removed it and flashed Stock Oreo -> problem still exists. Then i flashed Nougat an experienced the same effect: Wifi worked right on the setup menu.
@Golv do you have any idea why this happens? I think, this problem should affect anybody, who wants to go back to prior versions.
Click to expand...
Click to collapse
I believe it is related to the hosd_signed.img file that likely writes over the persist partition. By downgrading, we are overwriting the hosd and the nougat ruu then formats and rewrites a new MAC address. It was interesting to see this happening, but I'm glad I found a workaround.
Sorry for the delay in reply. For some reason notifications stopped coming to me ...
Most likely you should change Mac address setting from random to device’s Mac address before switching to stock (Settings - Network - Wifi - Network details - Advanced - Privacy - USE DEVICE MAC).
Golv said:
Sorry for the delay in reply. For some reason notifications stopped coming to me ...
Most likely you should change Mac address setting from random to device’s Mac address before switching to stock (Settings - Network - Wifi - Network details - Advanced - Privacy - USE DEVICE MAC).
Click to expand...
Click to collapse
Hi Glov,
cant find these steps in U11 Leedroid. can you throw some more light please.