Database Develop

[Q] The phone have problems with the network

Hey everyone, since yesterday I've been having some issues and I hope you can help me with it...
My Captivare wont let me send sms or calls, and on the screen says "mobile network not available"I was using the CM7 last build, so all I did was flash it again, hoping that would solve the problem, but that didn’t do anything, later I tried going back to Stock... so I used Odin to go back to 2.2, but now my phone says ” PHONE NOT ALLOWED MM#6” when it boots, and when I try to call someone says “data network not available”.
When I use the SIM in another phone works perfect, so the network is working.
What can I do to fix this ??
Sorry for my english

Sounds like your IMEI is incorrect. Some carriers outside the US do block the generic IMEI for Captivates. Try checking these posts and see if that helps you fix it. If not, Mobiletechvideos can rebuild your IMEI for a fee.
http://forum.xda-developers.com/showthread.php?t=1264021
http://forum.xda-developers.com/showthread.php?t=881162

@Red_81 Mobiletechvideos build IMEI for free where and from when did they started this for free, the charges are $30 in the link posted by u.

ridhi said:
@Red_81 Mobiletechvideos build IMEI for free where and from when did they started this for free, the charges are $30 in the link posted by u.
Click to expand...
Click to collapse
Huh? Can I get a translation? I'm guessing English isn't your first langauge and it is making it hard for me to understand the point you're trying to get across.
Where and from when did they started this for free? ??????
I don't think they do it for free. But I would love it if they did because I will be using their service sometime in the future.

Ridhi, I think the misunderstanding is that Red_81 said MobileTechVideos will do it for a fee, not that they would do it for free.

Reading and comprehension are two skills that are sadly lacking in the forums.

ridhi said:
@Red_81 Mobiletechvideos build IMEI for free where and from when did they started this for free, the charges are $30 in the link posted by u.
Click to expand...
Click to collapse
He said "for a fee," not "for free."

Apologies friends i think i need to get the eye test done.

Hi everyone again, after 3 days of struggle with my phone I've been able to fix it.
Red_81 thanks for you response the problem was the IMEI but none of the links you gave me works for me
After a lot of searching I found a guide that solves the problem of my phone these are the steps:
- Make sure you are on Froyo (whatever ROM, it worked for me on the stock UCJI6 )
- You need to be Root and have Busybox installed
- Now download the version of Galaxy_S Unlock that is at the end of this post into your phone
- Go to your download folder and click to unzip, then launch the .apk file
- If Android doesn't let you install go to Settings > Applications > tick Unknown sources and try again
0. Go to the tab > Signal fix problem
1. Save efs folder
2. Delete nv_data.bin files + reboot
3. Restore data + reboot
4. Create bak files
- Last step that is "restore efs folder" is only there for if the fix didn't work. It's very clear in the app.
That's it !
Now my phone is fully functional thank to this guide and Thanks all who tried to help me.
Source of this guide: darkyrom.com/community/index.php?threads/imei-issue-showing-004999010640000-instead-of-unique-original-number.1876 (the forum don't let me post a link...)

Did you get the original IMEI back for your phone or do you have the test one that starts with 0049?
Sent from my SAMSUNG-SGH-I897 using XDA App

It's the test one but works fine.
Do you know wich may be the consecuences if I keep this IMEI ?

There shouldn'tbe any issues with that one staying on your phone. Some other carriers block this IMEI but none of the American carriers seem to.
Sent from my SAMSUNG-SGH-I897 using XDA App

Felixcm88 said:
Hi everyone again, after 3 days of struggle with my phone I've been able to fix it.
Red_81 thanks for you response the problem was the IMEI but none of the links you gave me works for me
After a lot of searching I found a guide that solves the problem of my phone these are the steps:
- Make sure you are on Froyo (whatever ROM, it worked for me on the stock UCJI6 )
- You need to be Root and have Busybox installed
- Now download the version of Galaxy_S Unlock that is at the end of this post into your phone
- Go to your download folder and click to unzip, then launch the .apk file
- If Android doesn't let you install go to Settings > Applications > tick Unknown sources and try again
0. Go to the tab > Signal fix problem
1. Save efs folder
2. Delete nv_data.bin files + reboot
3. Restore data + reboot
4. Create bak files
- Last step that is "restore efs folder" is only there for if the fix didn't work. It's very clear in the app.
That's it !
Now my phone is fully functional thank to this guide and Thanks all who tried to help me.
Source of this guide: darkyrom.com/community/index.php?threads/imei-issue-showing-004999010640000-instead-of-unique-original-number.1876 (the forum don't let me post a link...)
Click to expand...
Click to collapse
Will try this, Thanks!!

Hope it works for you too

[Q] XT1053 issues, WiFi wont turn on, SIM detected but not connected to a network.

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.

Moto X mobile data not working.. i messed up

Hi. I am in the UK and have the first gen moto x. i was dicking around with roms etc and i ended up accidentally erasing internal storage. I managed to the get the phone back to how it was apart from the fact that it cannot make calls, text, get 3g signal. it is essentially a small tablet. when i use the dialler code to show the imei number it is 0. i tried reinstalling modems etc and none have worked. i have tried differnet roms and even flashing lollipop. I am wondering if the modems files i am using are not working because they are US files and I need some kind of EU file? Idk.
I had my imei written down so i was going to try and change it to that on the phone but engineer tools does not open or even seem to exist on the phone. i cant try using the stock rom etc because it is on a site (something like sbf developers ) that says it is forbidden. i literally have tried everything. can anyone help? :crying:

azerouz said:
Hi. I am in the UK and have the first gen moto x. i was dicking around with roms etc and i ended up accidentally erasing internal storage. I managed to the get the phone back to how it was apart from the fact that it cannot make calls, text, get 3g signal. it is essentially a small tablet. when i use the dialler code to show the imei number it is 0. i tried reinstalling modems etc and none have worked. i have tried differnet roms and even flashing lollipop. I am wondering if the modems files i am using are not working because they are US files and I need some kind of EU file? Idk.
I had my imei written down so i was going to try and change it to that on the phone but engineer tools does not open or even seem to exist on the phone. i cant try using the stock rom etc because it is on a site (something like sbf developers ) that says it is forbidden. i literally have tried everything. can anyone help? :crying:
Click to expand...
Click to collapse
Hey! If you've installed a US ROM, you are using the wrong baseband files to access your service provider network ( XT1053- US ; XT1052- UK)
Try installing an XT1052 based rom and report back . Also, be careful while flashing your new chosen ROM. Ensure that it does not downgrade / modify your current bootloader as you may end up bricking your phone (since you've upgraded to LP)
Best of luck mate .

Bhargav4591 said:
Hey! If you've installed a US ROM, you are using the wrong baseband files to access your service provider network ( XT1053- US ; XT1052- UK)
Try installing an XT1052 based rom and report back . Also, be careful while flashing your new chosen ROM. Ensure that it does not downgrade / modify your current bootloader as you may end up bricking your phone (since you've upgraded to LP)
Best of luck mate .
Click to expand...
Click to collapse
Ty for the reply. I just tried flashing a rom for the 52 instead of the 53 and twrp gives an error message of "This package is for the device: xt1052 ghost, xt1052 ghost etc.. this device is ." the etc is just a couple more models but the device doesnt seem to know what it is? its saying becuase it is for the 52 it cannot install even though the device is the 52.

azerouz said:
Ty for the reply. I just tried flashing a rom for the 52 instead of the 53 and twrp gives an error message of "This package is for the device: xt1052 ghost, xt1052 ghost etc.. this device is ." the etc is just a couple more models but the device doesnt seem to know what it is? its saying becuase it is for the 52 it cannot install even though the device is the 52.
Click to expand...
Click to collapse
Strange . Do elaborate as to what rom you are flashing and which rom you are currently using (The one that has a problem).
Also, are you wiping the system before flashing ?

Bhargav4591 said:
Strange . Do elaborate as to what rom you are flashing and which rom you are currently using (The one that has a problem).
Also, are you wiping the system before flashing ?
Click to expand...
Click to collapse
Hi again. i googled xt1052 rom and found a few. the one i tried was cyanhacker(obviously based on cm). after i got that error i tried editing the updater script to skip over the process in which it checks what device it is on. after that it appeared to flash successfully but when i tried to boot it showed the bootloader unlocked screen, vibrated then restarted and just kept doing that bootloop.

azerouz said:
Hi again. i googled xt1052 rom and found a few. the one i tried was cyanhacker(obviously based on cm). after i got that error i tried editing the updater script to skip over the process in which it checks what device it is on. after that it appeared to flash successfully but when i tried to boot it showed the bootloader unlocked screen, vibrated then restarted and just kept doing that bootloop.
Click to expand...
Click to collapse
1. Please download the correct ROM for your device from here: http://forum.xda-developers.com/moto-x/general/official-collection-firmwares-fxz-sbf-t3146628
2. Head over here: http://forum.xda-developers.com/moto-x/general/guide-moto-x-return-to-100-stock-using-t2446515 and follow the Instructions. CAUTION: If you decide yourself for manual flashing DO NOT PASTE THIS CODE:
Code:
fastboot oem config carrier vzw
Or you'll end up, like me: http://forum.xda-developers.com/moto-x/moto-x-qa/carrier-retail-devices-t3174988
In case I could help you with some guidance, I would be happy, if you could help me, in my thread.
//EDIT: Your battery should be on 70% or more, before you try to do anything! Keep this in mind, else flashing could be interrupted!
Kind regards

Xanthales said:
1. Please download the correct ROM for your device from here: http://forum.xda-developers.com/moto-x/general/official-collection-firmwares-fxz-sbf-t3146628
2. Head over here: http://forum.xda-developers.com/moto-x/general/guide-moto-x-return-to-100-stock-using-t2446515 and follow the Instructions. CAUTION: If you decide yourself for manual flashing DO NOT PASTE THIS CODE:
Code:
fastboot oem config carrier vzw
Or you'll end up, like me: http://forum.xda-developers.com/moto-x/moto-x-qa/carrier-retail-devices-t3174988
In case I could help you with some guidance, I would be happy, if you could help me, in my thread.
//EDIT: Your battery should be on 70% or more, before you try to do anything! Keep this in mind, else flashing could be interrupted!
Kind regards
Click to expand...
Click to collapse
Thankyou so much. did what you said. tinkered in twrp. flashed a lollipop rom and made a call. My man right here <3

azerouz said:
Thankyou so much. did what you said. tinkered in twrp. flashed a lollipop rom and made a call. My man right here <3
Click to expand...
Click to collapse
No problem, im glad to hear, that I could help you!
Maybe you can help me here?: http://forum.xda-developers.com/moto-x/moto-x-qa/carrier-retail-devices-t3174988
This would be awesome, if you got a retail device!

Remove the Red Text From Firmware zip and Aboot - S-OFF Only!

**Warning! This is a potentially hazardous procedure! Do not proceed unless you are willing to deal with the consequences if you do something wrong.** I am not responsible if you brick, blow up, catch on fire, or do any other damage to your phone. Do this at your own RISK! Now that I have that out of the way.
If you feel that you have the necessary skills then proceed. You don't have to wait for someone to make a No Red Text firmware zip, or flashable aboot. It is so easy to create your own no red text aboot zip, or a no-red-text firmware zip. This will work on all M9's and other HTC devices. M8, M7, etc hboot's.
You will need 7zip, and a hex editor. Just open up the firmware zip with 7zip, and extract the signed-aboot. Now open the aboot with a hex editor. In search type the first couple of words of the red text "This Build", and hit enter. That will take you to the line you need to edit to remove that annoying Red Text. On the M9 I believe it will be line 00086F2E or 0008EF3A. Once you have found the lines that appear in red on your screen after you unlocked your bootloader, navigate to the numbers on the left that coincide with the letters. Don't remove any! Type in 20,and watch the letters disappear. Do this for the entire text, and only for that text. The 20 creates a blank space that won't show on the screen. Save it, and put it back in the zip. Flash in download with fastboot. Enjoy. To make a flashable aboot take your modified aboot and android_info.txt from your device, and zip them up together. Then flash in download with fastboot.
You can also do the fake locked mod the same way. Just type in unlocked, in search, and look for the place that has locked, unlocked, and relocked together. Then do the same thing you did for the development warning to the "un" in "unlocked".
Cheers
I Truly Enjoy XDA-Developers. Com with this Fabulous HTC One M9

thanx
thanx its working

thank you.

singhshb said:
thanx its working
Click to expand...
Click to collapse
You're welcome!
daydream3r said:
thank you.
Click to expand...
Click to collapse

batinica said:
This no doubt a noob question but when you say "Just open up the firmware zip with 7zip, and extract the signed-aboot" how do I go about get the zip from my device?
Click to expand...
Click to collapse
You don't get the zip from your device. What you need to do is search for a firmware zip here on XDA and use it. You will probably find someone who has already made a no red text firmware zip and use the ABOOT from it, but where's the fun in that. You could make your own firmware zip, but that's not the purpose of this thread. Search for a thread on XDA to teach you how to make a firmware zip if you are interested in doing that as well.
Using XDA to unleash the power of Android on my S6 Edge Plus & HTC One M9

help please
my brother installed this new 6.0 mm rom and then he was trying to remove red text
he did some mistake and my m9 got messed up
he said he typed this command in bootloader mode "fastboot flash aboot no-redtextaboot.zip"
and now my phone is doesnt power on and i tried holding power volume up and down and all that stuff not working
please help i got soo crazy that i got a crewcut please help any one

bakh1 said:
my brother installed this new 6.0 mm rom and then he was trying to remove red text
he did some mistake and my m9 got messed up
he said he typed this command in bootloader mode "fastboot flash aboot no-redtextaboot.zip"
and now my phone is doesnt power on and i tried holding power volume up and down and all that stuff not working
please help i got soo crazy that i got a crewcut please help any one
Click to expand...
Click to collapse
Sorry my friend but looks like hard brick if it won't power on. there's nothing you can do but jtag.
This is a dangerous thing to do and could destroy your device. You are hex editing the a boot, which is cannot be compromised in any way or you will end up with a paperweight. You see, your bootloader is no longer operational. That's why your phone won't power on. In this case, allowing somebody to do it, that had no clue what they were doing, was extremely risky and foolhardy and looks to have destroyed your device.

bakh1 said:
my brother installed this new 6.0 mm rom and then he was trying to remove red text
he did some mistake and my m9 got messed up
he said he typed this command in bootloader mode "fastboot flash aboot no-redtextaboot.zip"
and now my phone is doesnt power on and i tried holding power volume up and down and all that stuff not working
please help i got soo crazy that i got a crewcut please help any one
Click to expand...
Click to collapse
I'm sorry to hear that your brother made a mistake editing the ABOOT. Like @Behold_this said you are now going to have to take your phone to a repair shop that has the professional tools to restore your phone to a working condition. If you are with T-Mobile and bought the phone through them you may be able to take it to them and get it replaced. Just don't mention that you modified the ABOOT. Also, if you are a US customer and you haven't used your Uh-Oh protection you can try that. I know that Mo Versi had said rooting your phone would not void the Uh Oh protection, but I don't know about modifying the ABOOT. They're all worth a try. I wish you the best with this. There's always a risk when you modify a device like we do here on XDA. The key is to always follow directions carefully, and if you're not a 100% sure of what you are doing don't do it.
Using XDA to unleash the power of Android on my S6 Edge Plus & HTC One M9

please help me
i am currently out of us and not going back soon so i gave to local repair shop here they said they cant help me because jtag can only be done on m8 not m9 something like that and my brother said give me one more try he said something about htc unbrick project what should i do please

bakh1 said:
i am currently out of us and not going back soon so i gave to local repair shop here they said they cant help me because jtag can only be done on m8 not m9 something like that and my brother said give me one more try he said something about htc unbrick project what should i do please
Click to expand...
Click to collapse
As far as I know that project was for the M7 and won't work on the M9. Besides that method required for the phone to boot to bootloader or fastboot I believe. Since your phone won't boot at all the only thing I can think to do is go through your carrier or HTC. HTC has repaired or replaced many bricked devices free, but I have heard of a few cases where they would charge. If you don't mind not telling them the complete truth about how it was bricked you could tell them it was in the process of updating when it happened. That has actually happened on the M7. This is the first time I have actually heard first hand of a M9 hard bricking. All of the other ones I have heard about were able to boot to download, htc ftm, or bootloader mode and could be recovered. You have tried to boot to htc ftm by holding the power and volume up buttons continuously?
Using XDA to unleash the power of Android in my S7 Edge, One M9, and S6 Edge Plus

jbfountain said:
**Warning! This is a potentially hazardous procedure! Do not proceed unless you are willing to deal with the consequences if you do something wrong.** I am not responsible if you brick, blow up, catch on fire, or do any other damage to your phone. Do this at your own RISK! Now that I have that out of the way.
If you feel that you have the necessary skills then proceed. You don't have to wait for someone to make a No Red Text firmware zip, or flashable aboot. It is so easy to create your own no red text aboot zip, or a no-red-text firmware zip. This will work on all M9's and other HTC devices. M8, M7, etc hboot's.
You will need 7zip, and a hex editor. Just open up the firmware zip with 7zip, and extract the signed-aboot. Now open the aboot with a hex editor. In search type the first couple of words of the red text "This Build", and hit enter. That will take you to the line you need to edit to remove that annoying Red Text. On the M9 I believe it will be line 00086F2E or 0008EF3A. Once you have found the lines that appear in red on your screen after you unlocked your bootloader, navigate to the numbers on the left that coincide with the letters. Don't remove any! Type in 20,and watch the letters disappear. Do this for the entire text, and only for that text. The 20 creates a blank space that won't show on the screen. Save it, and put it back in the zip. Flash in download with fastboot. Enjoy. To make a flashable aboot take your modified aboot and android_info.txt from your device, and zip them up together. Then flash in download with fastboot.
You can also do the fake locked mod the same way. Just type in unlocked, in search, and look for the place that has locked, unlocked, and relocked together. Then do the same thing you did for the development warning to the "un" in "unlocked".
Cheers
I Truly Enjoy XDA-Developers. Com with this Fabulous HTC One M9
Click to expand...
Click to collapse
I finally found your effort of writing this "recipe".
Thanky for sharing!

Is the "red text" referred to here the notice about the reporting software and that HTC will collect information about what your phone is doing, etc.? If so, will the procedure actually remove the software or stop it from running, or does it just get rid of the notice?
ETA: Is that reporting software an issue to worry about for battery use/privacy/whatever else reasons?

drfarmkid said:
Is the "red text" referred to here the notice about the reporting software and that HTC will collect information about what your phone is doing, etc.? If so, will the procedure actually remove the software or stop it from running, or does it just get rid of the notice?
ETA: Is that reporting software an issue to worry about for battery use/privacy/whatever else reasons?
Click to expand...
Click to collapse
The red text that appears on your phone after unlocking it doesn't have any functionallity. Some just do not want to see it. That's what this is all about. If you don't want to see it use this method. If it doesn't bother you don't do it.
Cheers
Sent from my HTC 10 using XDA Labs

Nexus 6 No LTE with IMEI correct, Bad "0" IMEi I have LTE?!?!?!? Heeeeelp!

Ok, Ladies and Gentleman I need some deep thought processing here for some help with a Motorola Nexus 6. In brief here is what the problem is, a while back when flashing Pure Nexus rom, I experienced a loss of my IMEI. I can restore my IMEI but if and when I do, I lose any 4g and LTE connectivity. The phone functions in 3g with data and phone etc... just slow as molasses but if I restore my IMEI to the one that doesn't show up my IMEI correctly I get back LTE/4g and all works fine also. I've tried going all the way back to the original firmware which was saved to computer and restoring it. Same thing, I have IMEI but no LTE/4g. restore bad efs and get LTE/4g back. I've tried going through all the factory firmware's and flashing by ADB and or TWRP and nothing firmware wise will allow me to restore the IMEI and have LTE/4g signal. If I restore the bad efs and get OOOOOOOO for IMEI when using the *#06# on any firmware version, I regain LTE/4g functioning! I am using Pure Nexus 7.1 now and can still see the 00000000 as a IMEI, if I restore my efs and get IMEI back showing correctly, no LTE/4g signal! My phone can only function as it should as long as the IMEI doesn't show correctly! I have tried just flashing base bands and other segments of any rom and still the problem persist! I have even tried restoring an EFS from another nexus 6 and still no help. It's not the sims because I've tried AT&T sims and Verizon sims from other phones and it does the same thing! I've tried flashing with a sims in the phone and without. Any ideas??? It's like somehow a correlating segment of a file is not being recognized when the correct IMEI is present, like some thing some where in the efs, IMEI, and radio are not taking to each other so to speak, unless it shows the zero's! Brain waves come on and help me out here!!

Have you tried doing a fresh install of a complete factory nexus image? (i.e. entirely wiping the device)

jbaumert said:
Have you tried doing a fresh install of a complete factory nexus image? (i.e. entirely wiping the device)
Click to expand...
Click to collapse
Thanks, and Yes, about 30 different times, using Google developer site original factory firmware, using ADB and or TWRP all the way back to original image, which I have saved as I said in the original post! I don't have a problem restoring IMEI it's just if I do, the phone will not connect to LTE/4g no way no how. I have to have a "0" IMEI for the phone to function as it should actually function and the LTE/4g radio to work, something strange is a miss!

TheWacoKid said:
Thanks, and Yes, about 30 different times, using Google developer site original factory firmware, using ADB and or TWRP all the way back to original image, which I have saved as I said in the original post! I don't have a problem restoring IMEI it's just if I do, the phone will not connect to LTE/4g no way no how. I have to have a "0" IMEI for the phone to function as it should actually function and the LTE/4g radio to work, something strange is a miss!
Click to expand...
Click to collapse
Alrighty, no need to yell.... The factory image is flashed with "fastboot" NOT adb or TWRP. Just wanted to clarify how you were returning the phone to stock.

jbaumert said:
Alrighty, no need to yell.... The factory image is flashed with "fastboot" NOT adb or TWRP. Just wanted to clarify how you were returning the phone to stock.
Click to expand...
Click to collapse
Yes I said thanks because I was yelling! Jezz, get a grip THIS IS YELLING! ADB/Fastboot both tools are used to flash, extract etc.. with your computer, so obviously one cannot flash/restore etc... without using the proper tools via computer!

Try this:
1) Install "Change APN" app from Google store
2) Open ChangeAPN and click the "option" ( the 3 vertical dots) in the upper right-hand corners.
3) click "reset to default"
4) exit the app
5) perform carrier reset ##3282#
6)If needed: after the phone reboots, perform PRL/Device config update. That's it and you should have LTE data.

Dixon Butz said:
Try this:
1) Install "Change APN" app from Google store
2) Open ChangeAPN and click the "option" ( the 3 vertical dots) in the upper right-hand corners.
3) click "reset to default"
4) exit the app
5) perform carrier reset ##3282#
6)If needed: after the phone reboots, perform PRL/Device config update. That's it and you should have LTE data.
Click to expand...
Click to collapse
Thanks! Ok, Itried that, restored my IMEI, "reset APN to default" Tried Carrier reset ##3282# and it says "NO Cellular Network" even though I am showing my network and 3G. So, I rebooted and same thing, went to PRL and tried to update and it says "update error" but it will refresh!

TheWacoKid said:
Yes I said thanks because I was yelling! Jezz, get a grip THIS IS YELLING! ADB/Fastboot both tools are used to flash, extract etc.. with your computer, so obviously one cannot flash/restore etc... without using the proper tools via computer!
Click to expand...
Click to collapse
You clearly don't know the difference between a recovery, the bootloader and the operating system.
ADB is used when the phone is on and is not how you flash a factory image. Fastboot is used in the bootloader and is the proper method of restoring to factory.

admiralspeedy said:
You clearly don't know the difference between a recovery, the bootloader and the operating system.
ADB is used when the phone is on and is not how you flash a factory image. Fastboot is used in the bootloader and is the proper method of restoring to factory.
Click to expand...
Click to collapse
No, I guess not, that's how I've been flashing, restoring and unbricking cells for years, I just don't understand anything!

TheWacoKid said:
No, I guess not, that's how I've been flashing, restoring and unbricking cells for years, I just don't understand anything!
Click to expand...
Click to collapse
You know some magic we don't? There is no way you've flashed a ROM with ADB...

@admiralspeedy
I was very gratified when I noticed that I'd overnight become a Senior Member - until I realised that it had nothing to do with the wisdom I'd imparted in my posts, but only that I'd posted 100. So seniority doesn't imply knowledge, which I think you're beginning to demonstrate in this thread as well as in another where I've seen this same strange unnecessarily belligerent attitude.
TheWacoKid is asking for help, which I'd be happy to offer if I had any ideas. I feel absolutely no desire to tell him that he has no idea what he's doing. And nor should you.
Stop trolling and become a properly-active member of the community.

dahawthorne said:
@admiralspeedy
I was very gratified when I noticed that I'd overnight become a Senior Member - until I realised that it had nothing to do with the wisdom I'd imparted in my posts, but only that I'd posted 100. So seniority doesn't imply knowledge, which I think you're beginning to demonstrate in this thread as well as in another where I've seen this same strange unnecessarily belligerent attitude.
TheWacoKid is asking for help, which I'd be happy to offer if I had any ideas. I feel absolutely no desire to tell him that he has no idea what he's doing. And nor should you.
Stop trolling and become a properly-active member of the community.
Click to expand...
Click to collapse
Actually, I wouldn't have jumped on him like that if he hadn't come out swinging with snarky comments when people tried to help him.

admiralspeedy said:
You know some magic we don't? There is no way you've flashed a ROM with ADB...
Click to expand...
Click to collapse
Look, I came on here to discuss a situation and or problem, which is what I thought this web site was known for, which I havent run into before, in that way not only do I get some help and or suggestions which might help me but help others at the same time who might have the same problem and or will have in the future and find possible solutions! If you don't have anything positive to add to the conversation/situation/problem at hand you are wasting my time, others time and most of all just making a fool out of yourself being childish and immature. Most on here come for solutions not looking to nitpick and try and belittle others like they know everything, which you don't, otherwise you would have given a solution! So you can continue to act like a troll or just leave the situation be and by the way, you ever hear of ADB Sideload??

Use method 2 , you will get everything definitely
https://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008

TheWacoKid said:
Look, I came on here to discuss a situation and or problem, which is what I thought this web site was known for, which I havent run into before, in that way not only do I get some help and or suggestions which might help me but help others at the same time who might have the same problem and or will have in the future and find possible solutions! If you don't have anything positive to add to the conversation/situation/problem at hand you are wasting my time, others time and most of all just making a fool out of yourself being childish and immature. Most on here come for solutions not looking to nitpick and try and belittle others like they know everything, which you don't, otherwise you would have given a solution! So you can continue to act like a troll or just leave the situation be and by the way, you ever hear of ADB Sideload??
Click to expand...
Click to collapse
I'm "belittling" you because your first two replies to someone who tried to help you were snarky and rude. In your own words, get a grip.

admiralspeedy said:
Actually, I wouldn't have jumped on him like that if he hadn't come out swinging with snarky comments when people tried to help him.
Click to expand...
Click to collapse
Time for you to go back and read some more...
You can flash a ROM with adb... Now unless you can help him... Shaddyup

rignfool said:
Time for you to go back and read some more...
You can flash a ROM with adb... Now unless you can help him... Shaddyup
Click to expand...
Click to collapse
No, you can use ADB sideload to flash a ROM which requires you to be in the recovery. Standard ADB cannot be used to flash a ROM.

admiralspeedy said:
I'm "belittling" you because your first two replies to someone who tried to help you were snarky and rude. In your own words, get a grip.
Click to expand...
Click to collapse
Amazing to any one with half a brain how you a Troll can think from typed response that someone is yelling, swinging, snarky and rude but your the one with an attitude that is all the above because like I said your a childish troll! I can't believe this site would even allow someone like you to be a member paid or otherwise! Your attitude is all your own and based on your own weak assumptions! Now go back to playing with your legos!

drmuruga said:
Use method 2 , you will get everything definitely
https://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
Click to expand...
Click to collapse
Thanks, I've used both of those methods, I have even tried just flashing individual parts all by themselves to see if just one part would give an error of some kind while flashing, no errors on any flash of any kind, the only difference being that if I read them correctly that on those methods it said to wipe data factory reset in recovery, before reboot, the Flashall bat file reboots automatically into image just flashed, I usually reboot as last command, if that makes any difference, I've even tried wiping then just flashing the new bootloader after a wipe, because it basically acts like a security checkpoint and partition manager, then rebooting and flashing the rest of one of the google firmware versions for the nexus 6.

TheWacoKid said:
Thanks, I've used both of those methods, I have even tried just flashing individual parts all by themselves to see if just one part would give an error of some kind while flashing, no errors on any flash of any kind, the only difference being that if I read them correctly that on those methods it said to wipe data factory reset in recovery, before reboot, the Flashall bat file reboots automatically into image just flashed, I usually reboot as last command, if that makes any difference, I've even tried wiping then just flashing the new bootloader after a wipe, because it basically acts like a security checkpoint and partition manager, then rebooting and flashing the rest of one of the google firmware versions for the nexus 6.
Click to expand...
Click to collapse
So was there a solution? The thread just ended. I also have this problem but I'm no where as technical as thewacokid.
But I do know how to follow steps