Related
Ok, im am trying to re-compile a SMG file that i have unpacked with unyaffs.
this is what i am trying to do before everyone starts shouting that you can just use a update.zip
Where i work we are about to start reselling Verizon Wireless under a different name, we buy our phones from Verizon.
i am trying to "de-Verizon" the phone and put some of our own customizations on it ie: Carrier text, boot screen ect...
any way, i need to do this in the least intrusive way so that i can show the AE's how to do it before giving to customer, or can be done by some one else.
The RSD-lite method looks the best, i have already successfully changed the moto logo and go that working, but now i am trying to edit the Carrier Text "eri.xml" in the stock load WITH OUT rooting.
Once i unyaffs the file i can do what i need to do but what steps do i need to take to compile it back into a smg file?
does anyone have a better suggestions for what i am trying to do?
Thanks, this forum has been a GREAT help
So, I have an XT1053 that I unlocked and got to 4.4.4 using the T Mobile stock ROM.
Everything was fine, I rooted it, it went all fine.
Then I installed the XPosed framework, got me some modules, and it was fine.
Then I got the Gravity Box to tweak my stuff.
Rebooted to activate it, and it was all fine and dandy until I changed setting that required a further reboot, like "show network activity indicators on WiFi/signal bars" and the navbar customizer.
I was hoping to come back and do some sweet customizations but instead, at reboot, my phone wouldnt get service, even though the SIM is detected, I have an IMEI and my SIMs phone number shows up on the About phone > status screen.
WiFi wont turn on, neither does bluetooth.
I disabled and uninstalled all the xposed components and modules but it stayed the same.
So I figured out all I had to do was come back to my clean, 4.4.4 stock nandroid backup.
No luck, issue persists. Did a factory reset (with the TWRP recovery might I add) but no such luck.
Downloaded both the AT&T and Verizons 4.4.4 versions, but I cant flash them using RDS lite, apparently the preflash verification fails, it mentions the gpt. I guess I need to flash the TMobile 4.4.4, but there is no such file at sbf developers, only 4.4.3, Will flashing this brick my phone?
This guy https://forums.motorola.com/posts/41d92959b1 has the same symptoms as me, but as you all can see, no follow up.
Any idea what can I do to fix this?
I totally place blame on the gravitybox network activity indicators settings, but who knows.
Added screenshots, edited out some stuff.
Thanks in advance, Ive spent most of my morning trying to figure this out.
No one?
:c
no_un_bot said:
So, I have an XT1053
WiFi wont turn on, neither does bluetooth.
I disabled and uninstalled all the xposed components and modules but it stayed the same.
So I figured out all I had to do was come back to my clean, 4.4.4 stock nandroid backup.
No luck, issue persists. Did a factory reset (with the TWRP recovery might I add) but no such luck.
Click to expand...
Click to collapse
Well, at first I thought maybe your phone somehow got stuck in airplane mode that for some reason wouldn't let go. So I put my phone in airplane mode to compare Status. It looks very similar except mine still shows WiFi Mac address and my voice and data shows radio off not out of service. signal strength looks the same.
A few suggestions:
- whenever you suspect Xposed might be responsible for something serious, you should usually do a full uninstall by flashing the Xposed Disabler zip that was automatically placed in your storage (check the Xposed folder in /sdcard/android/data or in just /sdcard or do a search).
- since you already tried FDR and nandroid restore, clearly something has been messed up that wasn't backed up before and that persists thru fdr. if you read around you'll notice there are some partitions, like the persist partition, that don't usually get backed up in a twrp or cwm nandroid. if you haven't already, read thru the thread (start post 5) that discusses recovering Wi-Fi and Bluetooth by manually restoring files in the persist folder. http://forum.xda-developers.com/moto-x/moto-x-qa/moto-x-xt1060-issues-wifi-bluetooth-t2813308
FYI it seems philz touch recovery can provide a more complete backup that includes those pesky partitions http://forum.xda-developers.com/moto-x/development/xt10xx-philz-touch-t2612149
- so yeah I'd attack the problem that way, see if you can restore WiFi and Bluetooth, then see what you can do with your signal strength and voice/data service. they could all be related to persist partition.
dtg7 said:
Well, at first I thought maybe your phone somehow got stuck in airplane mode that for some reason wouldn't let go. So I put my phone in airplane mode to compare Status. It looks very similar except mine still shows WiFi Mac address and my voice and data shows radio off not out of service. signal strength looks the same.
A few suggestions:
- whenever you suspect Xposed might be responsible for something serious, you should usually do a full uninstall by flashing the Xposed Disabler zip that was automatically placed in your storage (check the Xposed folder in /sdcard/android/data or in just /sdcard or do a search).
- since you already tried FDR and nandroid restore, clearly something has been messed up that wasn't backed up before and that persists thru fdr. if you read around you'll notice there are some partitions, like the persist partition, that don't usually get backed up in a twrp or cwm nandroid. if you haven't already, read thru the thread (start post 5) that discusses recovering Wi-Fi and Bluetooth by manually restoring files in the persist folder. http://forum.xda-developers.com/moto-x/moto-x-qa/moto-x-xt1060-issues-wifi-bluetooth-t2813308
FYI it seems philz touch recovery can provide a more complete backup that includes those pesky partitions http://forum.xda-developers.com/moto-x/development/xt10xx-philz-touch-t2612149
- so yeah I'd attack the problem that way, see if you can restore WiFi and Bluetooth, then see what you can do with your signal strength and voice/data service. they could all be related to persist partition.
Click to expand...
Click to collapse
Welp, somehow my persist folder is completely blank.
Guess I´d need for someone to upload theirs right?
An would an XT1060 persist folder work?
Thanks a bunch man, this has helped me lots.
no_un_bot said:
Welp, somehow my persist folder is completely blank.
Guess I´d need for someone to upload theirs right?
An would an XT1060 persist folder work?
Thanks a bunch man, this has helped me lots.
Click to expand...
Click to collapse
Totally empty looks fishy...are you sure you're running ES File Explorer with root permissions. If you don't give it root it will open that folder (and any other root read folder) as empty. check /data folder if it's empty you haven't set ES as root capable. You can do so from Fast Access -> Tools -> Root Explorer.
Yeah you can post a Request thread for the xt1053 persist files. a helpful person has already posted xt1060 persist folder on post #3 here ( http://forum.xda-developers.com/moto-x/moto-x-qa/wifi-isnt-t2760479 ) and he thinks it's probably the same for all variants. But keep in mind that post is from May so obviously it's before 4.4.4. On the other hand persist clearly persists, so it might also persist through updates. So I'd wait to see if anyone posts for xt1053 on 4.4.4 (try asking in that thread also) and only use the old upload if desperate. if you do use it worst case scenario if you encounter worse problems like boot loop or something you should be able to use your custom recovery's file manager to delete the files. make sure you read that thread all the way through though, taking note of the permissions you have to set. and also refer to the thread mentioned previously.
dtg7 said:
Totally empty looks fishy...are you sure you're running ES File Explorer with root permissions. If you don't give it root it will open that folder (and any other root read folder) as empty. check /data folder if it's empty you haven't set ES as root capable. You can do so from Fast Access -> Tools -> Root Explorer.
Yeah you can post a Request thread for the xt1053 persist files. a helpful person has already posted xt1060 persist folder on post #3 here ( http://forum.xda-developers.com/moto-x/moto-x-qa/wifi-isnt-t2760479 ) and he thinks it's probably the same for all variants. But keep in mind that post is from May so obviously it's before 4.4.4. On the other hand persist clearly persists, so it might also persist through updates. So I'd wait to see if anyone posts for xt1053 on 4.4.4 (try asking in that thread also) and only use the old upload if desperate. if you do use it worst case scenario if you encounter worse problems like boot loop or something you should be able to use your custom recovery's file manager to delete the files. make sure you read that thread all the way through though, taking note of the permissions you have to set. and also refer to the thread mentioned previously.
Click to expand...
Click to collapse
Boy oh boy was I wrong.
I fixed it, going to post what I did.
Turns out the /persist folder was not empty, root explorer showed everything was ok. he I thought, "Hey, XPosed + GravityBox caused (afaik) this mess, maybe it will get me out of it too. Maybe, as pointed out, xosed touched some partitions not normally accessible, lets see if they can do it again". So I installed those apps again, did the very same I did las time, and then uninstalled using the Xposed disabler .zip. Didnt work.
It was time to try and flash another stock ROM.
As Ive said before, I originally got into 4.4.4 with TMobiles ROM (my keyboard tilde key is broken, so bear with me), and attempting to flash AT&T/Verizon/BR Retail etc 4.4.4 stock ROMs would fail because of a security downgrade as far as gpt.bin goes.
I "fixed" this taking the gpt.bin file out of TMobiles OTA zip (the one that upgrades 4.4.3 to 4.4.4) and replacing the one on the ROM I was trying to flash with this. Meaning, I flashed the BR Retail 4.4.4 having replace gpt.bin with TMobiles OTA one.
Everything flashed ok, and, at the very last step, instead of using the command
Code:
fastboot oem config carrier vzw
like every guide out there says, I went for
Code:
fastboot oem config carrier ghost_retail
as per this page: https://github.com/CyanogenMod/android_device_motorola_ghost .
Phone rebooted with his Brazilian version and lo and behold, it was NOT working. Same symptoms.
I dug deeper, and the I remembered how someone with the same issues on another phone model fixed it by swapping his SIM for a friends, then using his again. I had already tried this, I even bough a SIM (because no one close to me uses a nano SIM) and it hadnt worked, but it did gave me some insight, maybe some sort of registration was not getting done.
Looking up stuff, I stumbled upon the "secret" testing menu on our Moto X, accessible by dialing *#*#4636#*#*
There I saw, to my horror, how my IMEI was 0.
Before giving up, I looked up how to fix this, turns out the BR modem was not quite right for Mexico. I flashed my country modem, getting he files from this video description (its in spanish, and the files are for Mexicos bands, but someone might find it useful): https://www.youtube.com/watch?v=oNSVRGvaKfY .
Rebooted, and to my relief, I had an IMEI again, though still no service, no wifi and no bluetooth.
Now, this special menu had some toggles that intrigued me, for they referenced to a possible registration, so I decided I should give it a go.
The toggles are pictured on the attached screenshot. These toggles, minus the CellInfoListRate, are only on and off.
I switched them so they would read "Turn radio off" (meaning it was on), "Turn off IMS regisration required" (meaning it was on, and my #1 suspect), "Turn off SMS over IMS" (seemed logical). I didnt play with the other 2 toggles.
Since I was cleaning, I left my phone on a table while I was sweeping, when suddenly the notification ringtone, one I hadnt heard in th past 2 days, sounded. I ran to my phone, and as angelic choirs played somewhere, I finally had signal bars, and an SMS had just gotten in.
Feeling relief, I was a bit let down when I still wasnt able to turn neither WiFi nor Bluetooth services. I called my brother, and when the call actually connected, I decided I might as well set my google account before anything else happened.
Now I had my contacts and data connection. I decided to turn the toggles that fixed this whole ordeal back to what I thought should be (thus now being as pictured on my screenshot) before rebooting.
Holding my breath, I rebooted and guess what: WiFi and bluetooth ould now be turned on, and connect.
This is the story of how I fixed this, hoping to help somebody out there.
Thanks to everyone who tried to help.
Moto X, you are a wild ride, but I love you.
Hi Guys. First off I'm posting this for information in hopes to help anyone else having this problem. I'll go over the problem I was having. What caused the problem for me and the steps I took to resolve it.
Problem:
A Handsfree activation bootloop. More specifically, no matter which rom, RUU, OTA, recovery or firmware I flashed, my phone would go threw a HFA and PRL update, say that it was successful and reboot on it's own and start the process over again. If at some point by chance I could catch it and disable the vDM.apk would be the only way I could stop it and boot normally. I tried resetting my profile, factory resets, Sprint support (which was completely useless) and everything else mentioned above. I even threw the kitchen sink in for good measure. lol. I was able to make phone calls, receive text and mms. I even had LTE and 3G service. But my wifi calling and sprint zone didn't work. So I knew something wasn't activating properly.
Cause:
Well for me it started when I accidentally flashed a M7 rom. Yeah don't laugh, it happens. Anyway, in recovery it said it failed but not before it formatted "/dev/block/mmcblk0p37" which is the system partition on the M7. But on the M8, it's the /carrier partition. So it erased all my info and filled it with a bunch of s**t. To the point that the partition was full and activation couldn't write to it. It also injected a bunch of s**t in "/dev/block/mmcblk0p39" which is the /devlog partition on the M8. So just a big mess. This is just how I got to this point. I'm not saying this your cause but the fix might help you.
Fix:
1 Get your self to a point that you are booted up to a rom. If you can't, try flashing an international rom made for sprint like "insert coin" for example. Those don't HFA bootloop from my experience.
2 Download MSL reader from the market. And get your MSL you'll need it later.
3 With a good root explorer, go to /carrier folder, do a backup of it (just in case) open the folder and delete everything in the folder.
4 Go to /devlog folder, open it and delete everything in there. (You don't need this stuff, it will rewrite itself).
5 Download the zip at the bottom of the post, extract it and copy the contents to your /carrier folder. Don't worry about the /devlog folder. leave it empty.
6 Now your going to flash a RUU. Download the one you want. I used https://www.androidfilehost.com/?fid=95784891001604379 (Don't worry it won't get you S-on or lock your bootloader). It will probably do a HFA again and it should fail. If not, try disabling it. Because we need to get to the dialer.
7 In your dial pad enter ##786# and go to edit mode. Enter your MSL if it asks you. Go to the menu button at the upper right and hit reset. Go threw the promps, the phone should reboot and restore. Let it boot up. It will go threw HFA again. But now you'll notice it activated properly. At this point your all done. Flash a custom recovery again. Profit.
Special Thanks to @Captain_Throwback You rock.
Let me know if this helps. Please post any questions and I'll try guiding you threw.
Dude iv been having some serious issues with data. I'm going to try this and see what happens thanks.
sprkat85 said:
Dude iv been having some serious issues with data. I'm going to try this and see what happens thanks.
Click to expand...
Click to collapse
Hope it helps.
Macropoutsis said:
Hope it helps.
Click to expand...
Click to collapse
It definitely helped out. Thanks for posting this again.
sprint htc one m8 h/k edition
u have mentioned in point 3 download root explorer
but in my case I am facing hands free activation page with emergency button .. and cant go further
how can I get rid of it ..
please help me .. i shall be very thankful to you
sprkat85 said:
It definitely helped out. Thanks for posting this again.
Click to expand...
Click to collapse
hello guys ..
I am facing the bitter problem in m8
after installing custom rom ,,as u told in your method for hands free activation loop fix,, I am facing the hands free activation loop ...
is there anything I can do to avoid it.???
otherwise its an phone for incoming calls only..
help me out guys
I ended going completely stock running an ruu then took steps to flash the newest firmware after I rooted. The problem I had was I flashed the wrong firmware. I do not have the HTC one m8 anymore.
gag_dhiman said:
hello guys ..
I am facing the bitter problem in m8
after installing custom rom ,,as u told in your method for hands free activation loop fix,, I am facing the hands free activation loop ...
is there anything I can do to avoid it.???
otherwise its an phone for incoming calls only..
help me out guys
Click to expand...
Click to collapse
What ROM?
If it is stock based you can try this, either go through TWRP and select file manager or do this in the zip before flashing.
Go to system/app/HtcOMADM_SPCS and rename the apk by adding .bak after .apk.
After the phone boots and you pass setup you can always rename the file by removing the .bak
You might get better results by posting this question in that ROM thread, or make a thread in the Q&A and put the ROM name in the title of the thread.
gag_dhiman said:
hello guys ..
I am facing the bitter problem in m8
after installing custom rom ,,as u told in your method for hands free activation loop fix,, I am facing the hands free activation loop ...
is there anything I can do to avoid it.???
otherwise its an phone for incoming calls only..
help me out guys
Click to expand...
Click to collapse
Hey bud. Didn't get my notifications on this thread. Are you still having a problem?
Hello senior.
I am ising the stock rom in sprint m8 harman kardon edition.
I still facing the problem. Cant rename htc omadm. Spcs file.
Moreover . In notifications area one line is written ( device management is running)
Sorry senior. For late reply.. i was in roaming.
Do guide me
HFA loop !!!!!!!!!!!!!!!!!1 never ending
I installed twrp .. in bootloader under twrp recovery,then advanced and in file manager /.. I go through system folder but no app folder is there .. and I am still facing the hands free activation loop/... do something seniors.....
dopy25 said:
What ROM?
If it is stock based you can try this, either go through TWRP and select file manager or do this in the zip before flashing.
Go to system/app/HtcOMADM_SPCS and rename the apk by adding .bak after .apk.
After the phone boots and you pass setup you can always rename the file by removing the .bak
You might get better results by posting this question in that ROM thread, or make a thread in the Q&A and put the ROM name in the title of the thread.
Click to expand...
Click to collapse
gag_dhiman said:
I installed twrp .. in bootloader under twrp recovery,then advanced and in file manager /.. I go through system folder but no app folder is there .. and I am still facing the hands free activation loop/... do something seniors.....
Click to expand...
Click to collapse
You have to mount system first.
Yes ... Seniors ... Yes... Got the solution... Thanks a lotttt..
hi i have bought on aliexpress a htc one m8 looks is m8 sprint from imei .my phone show bootloader unlocked
m8 whl pvt ship s-off
cid-11111 hboot -3.16.0.000
radio -1.00.20.0.120
running on kitkat 4.4.4
can any one help i try this tutorial but not show gsm network
Does Sprint M9 work with this method?
For the past half a year, I have been using Carbon rom on my Lenovo K3 Note, and it was fine, until it started slowing down. So, I decided to change it to another rom (Nexus), and the next thing I know, my SIM card is no longer detected.
Turns out, the IMEI was wiped.
How would I go about restoring this?
The things I have done:
MauiMETA = Never detects my phone. Places it into meta mode, but the light never turns yellow. Tried on 3 computers, and had no success on getting it to work. For two of the three, I couldn't find drivers for mt65xx and CDC.
MTK Droid Tool: The option to change the IMEI remained permanently greyed out, and was never given the option to change it.
Official rom: Didn't work. Currently using it, and still the same error (Null). Tried factory resetting it, no change.
Engineering mode: Always gave me an error when trying to enter command, never accepted it.
IMEI.EXE: Everything worked, except the IMEI's never changed in my device.
Have tried multiple roms, multiple wipes, SPFlash, CWM (Even ended up installing it again because I wiped my entire phone with SPFlash), and pretty much every trick I could find.
I need this think working in 12 hours.
EDIT: Problem was resolved with trying "official" roms until one allowed me to update within the rom. The Update that was installed via Lenovo's bootloader fixed it. The finished product was that of an untouched phone; I had to reinstall a bootloader, root, and a new rom.
If flashing stock doesn't help, and you have no kind of backup of where the imei resides, you likely need a service center to hopefully help.
But know that any talk of manually inputting imei numbers is not allowed on XDA, as its illegal in most areas.
Good luck!
Darth said:
If flashing stock doesn't help, and you have no kind of backup of where the imei resides, you likely need a service center to hopefully help.
But know that any talk of manually inputting imei numbers is not allowed on XDA, as its illegal in most areas.
Good luck!
Click to expand...
Click to collapse
So it isn't as simple as entering the two codes under my battery into some location, and rebooting?
I'm currently in Europe, and have no idea how any of that works (Studying abroad).
RocketPenguin1 said:
So it isn't as simple as entering the two codes under my battery into some location, and rebooting?
I'm currently in Europe, and have no idea how any of that works (Studying abroad).
Click to expand...
Click to collapse
That talk is not allowed, as I said. Inputting numbers falls under tampering and is illegal in most areas, as I said.
So try flashing stock, if you can. But without some sort of backup, you may be out of luck unfortunately.
Please keep number inputting talk off XDA, or I will need to close this thread. :good:
UPDATE: So, I flashed another "official" rom, which initially didn't work. However, it did give me the option to upgrade, which I did. With that upgrade, the IMEI is back, and my SIM card works.
Thing is, the ROM is almost entirely in Chinese.
How would I change my rom without wiping the IMEI?
Please post the link to download the ROM you used.
I have the same issue and even service centers failed to attempt this.
Thanx and regards
Raju
Chennai
You can easily rewrite imei number using snwriter tool, google it.
I have been struggling with this issue for the past few days now. My phone is showing no IMEI and no service. When I check the IMEI through the dialer, (*#06#) it shows that all the numbers related to that particular output as being zeros. However when I do a fastboot command (getvar all) the output shows that I have the correct IMEI number in the bootloader. I also noticed that the meid number is blank, I'm not sure if one has to do with the other but I have not been able to receive cell service since the issue of the IMEI number gone missing. I have spoken directly to Motorola and as my bootloader is unlocked they told me that my bootloader unlocking is what wiped out my IMEI number, as I know this to be wildly untrue and only used as an excuse to not have to deal with me or my problem, they then pushed me off on the Lenovo community forums. There I discussed the same problem and wouldn't you know it the only people that answered or Motorola employees. Which of course they said "send it in". Of course that's only because they didn't know that Motorola had already told me that they cannot fix it. There's an issue with the writing of the software version of the IMEI and I'm not certain as to the source of this issue. Considering no one will openly discuss much about IMEI numbers I've been getting absolutely zero help, with only a few suggestions of sending it to somebody else. I have worked on my own devices for the past 20 years and have only rarely sent in any electronic device to be repaired by the factory or manufacturer. This all happened when I restored a backup that apparently had corrupted files in it this was done through TWRP for both back up and restore. I have even asked, after becoming frustrated with the broken record repeating the same answer over and over, that I would willingly send my device in if someone could just tell me what it is that Motorola is going to do that I simply cannot. I couldn't even get an answer for that. This has become very frustrating and I am running out of places to ask this question. Everyone I have spoken to all agree with me that this is the premier source for developers and being able to connect with experts, I can only hope that my question is answerable. If anyone knows how to remedy this situation aside from paying Motorola to use their secret Harry Potter wand I would greatly appreciate your help. Thank you for your time and patience,
I have attached two pictures the first one is of the bootloaders barcode screen, the second is using the *#06# dialer code.
Noobie T.
I have solved it. It was just a matter of finding the correct combination of both fresh flashing a ROM and restoring of certain partitions back to the freshly flashed ROM. As it turns out the partitions that were the problem seems to be the EFS partitions as well as the persist partition. Wednesday I found a non-corrupted copy of a backup I was able to flash the ROM that was installed on the device at the time of the backup, after which I was able to restore just those partitions. After that once I rebooted my IMEI number showed up in the dialer code output. However, I would like to keep this thread open as the baseband, when shown in the fast boot screen, still seems to be <not found>. As well as does the ro.build.version.full , and the fpr-state variable says "no protection (77)". As this is a custom ROM and I am still relatively new I am not sure if this is because of the wrong itself or because of the issues that I had. I will keep a close eye on this and post updates.
So update, trying to install magic last night, after flashing TWRP, my network connectivity dropped again. Well trying to restore my phone with the RSA I came across a post that had a zip file containing batch files that turned the XML files in the ROM zip that's downloaded by the RSA into batch files that can be run from the command line. I had to make some adjustments to the files but was able to use the batch file to fully restore the phone back to factory settings and got back network activity. I had only adjusted the resulting batch files that are used to flash all the partitions for my phone not the original batch files used to create those batch files from the XML files. I will adjust the original batch files and post a link to them.