Develop Bugs

Error with CM 7

I have Clockworkmod revovery v5.0.2.0
When I try to install CM7:
Instaling update...
assert failed: getprop ("ro.product.device") =="vivo" || getprop ("ro.build.product ") == "vivo" || getprop ("ro.product.board") == "vivo" |
E: Error in /sdcard/update-cm-7.1.0-RC1-IncS-signed.zip
(Status 7)
Installation aborted.

Maybe try redownloading it. Could possibly be a corrupt download. Also check the md5 sum to make sure. You should be able to get an app in the market called md5checker or something.
Sent from my Droid Incredible 2 HD

unkota said:
I have Clockworkmod revovery v5.0.2.0
When I try to install CM7:
Instaling update...
assert failed: getprop ("ro.product.device") =="vivo" || getprop ("ro.build.product ") == "vivo" || getprop ("ro.product.board") == "vivo" |
E: Error in /sdcard/update-cm-7.1.0-RC1-IncS-signed.zip
(Status 7)
Installation aborted.
Click to expand...
Click to collapse
Its not for Inc 2, its for Incredible S.
You need to download Nightly - Vivow http://download.cyanogenmod.com/?device=vivow
Download #79. I heard there's problems between #80~88.

xHoLyx said:
Its not for Inc 2, its for Incredible S.
You need to download Nightly - Vivow http://download.cyanogenmod.com/?device=vivow
Download #79. I heard there's problems between #80~88.
Click to expand...
Click to collapse
Sorry, but:
"Not Found
The requested URL /cm/nightly/vivow/cm_vivow_full-79.zip was not found on this server"
Also I need to formad SD card from current FAT32 to XT4? If I do this my verizone phone lost unlock?

85 works fine. That's what I'm running
Sent from my Incredible 2 using Tapatalk

unkota said:
Sorry, but:
"Not Found
The requested URL /cm/nightly/vivow/cm_vivow_full-79.zip was not found on this server"
Also I need to formad SD card from current FAT32 to XT4? If I do this my verizone phone lost unlock?
Click to expand...
Click to collapse
Have you tried using ROM Manager? Or is this error generated when trying to download from ROM Manager?

digitalsynner85 said:
Have you tried using ROM Manager? Or is this error generated when trying to download from ROM Manager?
Click to expand...
Click to collapse
I got this error when I install CM from CWM recovery. Anyway I found 79 and this version installed without any problems. Thanks you guys. But I have another problem: I can't install PG32IMG_vivo_radio_3805.04.03.22. Hboot say wrong image. Also my prone say no service.

unkota said:
I got this error when I install CM from CWM recovery. Anyway I found 79 and this version installed without any problems. Thanks you guys. But I have another problem: I can't install PG32IMG_vivo_radio_3805.04.03.22. Hboot say wrong image. Also my prone say no service.
Click to expand...
Click to collapse
When flashing a radio, be very careful to check the md5 sum, and if they match, make sure your radio is named exactly "PG32IMG.zip" and place it on the root of your sdcard or hboot will give you that error. Your phone says no service because you tried to flash a radio image that was misnamed.

artvandelay440 said:
When flashing a radio, be very careful to check the md5 sum, and if they match, make sure your radio is named exactly "PG32IMG.zip" and place it on the root of your sdcard or hboot will give you that error. Your phone says no service because you tried to flash a radio image that was misnamed.
Click to expand...
Click to collapse
Just to expound upon what he said, just get rid of all that extra stuff in the name and leave the PG32IMG.zip, and if you're using a computer make extra sure it doesn't name it with .zip.zip due to it seeing it's a .zip file.

artvandelay440 said:
When flashing a radio, be very careful to check the md5 sum, and if they match, make sure your radio is named exactly "PG32IMG.zip" and place it on the root of your sdcard or hboot will give you that error. Your phone says no service because you tried to flash a radio image that was misnamed.
Click to expand...
Click to collapse
I don't know what radio need for my phone and cm Please give me advice and download link

unkota said:
I don't know what radio need for my phone and cm Please give me advice and download link
Click to expand...
Click to collapse
try the 722 radio-it seems to work well for the most users:
http://forum.xda-developers.com/showthread.php?t=1134451
it's the last one under gingerbread-based ruu's and ends with number 722.

artvandelay440 said:
try the 722 radio-it seems to work well for the most users:
http://forum.xda-developers.com/showthread.php?t=1134451
it's the last one under gingerbread-based ruu's and ends with number 722.
Click to expand...
Click to collapse
I already have .722. Sadly.
When CM started, I got activation screen, but my phone could not call. I don't know why, maybe because I had unlocked phone and live out of verizon network.
Now phone don't have connect...

unkota said:
I already have .722. Sadly.
When CM started, I got activation screen, but my phone could not call. I don't know why, maybe because I had unlocked phone and live out of verizon network.
Now phone don't have connect...
Click to expand...
Click to collapse
You have an unlocked phone- so do you mean you are using GSM band? Correct me if i'm wrong, but i don't believe cm7 has gsm support on the inc2, which would explain why you don't have service.

artvandelay440 said:
You have an unlocked phone- so do you mean you are using GSM band? Correct me if i'm wrong, but i don't believe cm7 has gsm support on the inc2, which would explain why you don't have service.
Click to expand...
Click to collapse
Yes I had GSM and unlocked phone. But I didnt unlock phone. I bought an unlocked already.
So I can't use CM7 on my phone? You know any custom FW for Inc2 with GSM support?

skyraider has gsm support, I believe gingerbang sense does as well, that's weird though because I seen a few different people say cm7 supports gsm I personally don't know I don't have a need for gsm

oxlong27 said:
skyraider has gsm support, I believe gingerbang sense does as well, that's weird though because I seen a few different people say cm7 supports gsm I personally don't know I don't have a need for gsm
Click to expand...
Click to collapse
I think that gsm on cm7 involved putting in the APN for whatever network you were going to be on and rebooting, but it's honestly been so long, i don't hardly remember much about cm7, lol.

What custom ROM without sense support GSM?

unkota said:
What custom ROM without sense support GSM?
Click to expand...
Click to collapse
I don't think there are any aosp roms with gsm at the moment. If anybody knows otherwise, let me know.

cant confirm if it works or not but for gsm in cm7 you have to go into wireless & networks then mobile networks and choose network type gsm/WCDMA auto

Sic123
Oh... You know, I can't bypass CM activation because I can't call to activation number and can't connect with NO SERVICE. I should press "SKIP" but after that "mobile network" in settings just vanished. Why do I need this f*** activation?

How to get rid of JB update nag.

I googled for 5 mins and can't find the answer. Anyone know how?
One of the methods is using titanium backup to delete the updater, but I don't rly like that method, and I don't know what to do.

So I'm assuming you're on a custom ROM and don't want to be bothered by it? Pretty sure you can simply change your build.prop and it'll no longer identify you phone as "needing" the update.

martonikaj said:
So I'm assuming you're on a custom ROM and don't want to be bothered by it? Pretty sure you can simply change your build.prop and it'll no longer identify you phone as "needing" the update.
Click to expand...
Click to collapse
Yea, I have a custom rom, and I don't know hot to change the buildprop.

I have the same inquiry
convolution said:
Yea, I have a custom rom, and I don't know hot to change the buildprop.
Click to expand...
Click to collapse
I can see the build.prop file using Root Explorer (from play store). Read in another thread that need to change the following lines:
ro.build.description=...
ro.build.fingerprint=...
with whatever is written there after applying the OTA update, but..., don´t have those strings since haven´t applied the update.
Any clue?
Note: in the build.prop file there is a note telling #do not try to parse ro.build.description or fingerprint... anyone knows why?
Thank you, C.

I know how to change the buildprop, im at 240 dpi. But I am not sure what to change the description and fingerprint to, like you said. Does anyone have it?

no one?

What used to work in older versions of Android, and which may work in JB, is changing the ro.build.fingerprint to match the latest version. So, change it to:
ro.build.fingerprint=google/takju/maguro:4.1.1/JRO03C/398337:user/release-keys

works!

[Q] Problem with UPDATING from 4.2.2 to 4.3 !

Hello guys,
I have a problem with my Galaxy Google Nexus GT-I9250 ! Of course, the update for 4.3 JB came up on my phone. When I pressed the button to install it, after a few second the installation stopped. It said : "Installation aborted" and then "Signature Verification Failed" . I tried to search through the other forums and threads, but as I`m a kind of a newbie with that technology I would be really pleased if someone explain me how to fix that, maybe, silly problem.
Oh, and also what is this thing named OTA.zip ?
Thanks.

It's exactlly the same thing that's happening to me
I opened a new thread but didn't include that detail, but it cant update.

irvingh30 said:
It's exactlly the same thing that's happening to me
I opened a new thread but didn't include that detail, but it cant update.
Click to expand...
Click to collapse
yes..hopefully someone explain us how to fix it... :\

stefangrozev68 said:
Hello guys,
I have a problem with my Galaxy Google Nexus GT-I9250 ! Of course, the update for 4.3 JB came up on my phone. When I pressed the button to install it, after a few second the installation stopped. It said : "Installation aborted" and then "Signature Verification Failed" . I tried to search through the other forums and threads, but as I`m a kind of a newbie with that technology I would be really pleased if someone explain me how to fix that, maybe, silly problem.
Oh, and also what is this thing named OTA.zip ?
Thanks.
Click to expand...
Click to collapse
something you have on your phone isnt stock. thats why it fails.
what did you modify on your phone?

Zepius said:
something you have on your phone isnt stock. thats why it fails.
what did you modify on your phone?
Click to expand...
Click to collapse
Well, I recently rooted the phone. There is also SuperSU on it.. I don`t know whether this changes something.

Zepius said:
something you have on your phone isnt stock. thats why it fails.
what did you modify on your phone?
Click to expand...
Click to collapse
In my case I bought it like this, how can i know if something is not stock?
you mean i have to go back to stock and flash it again through Odin?
I saw a post from someone here showing how to do that, but i wasn't quite sure either...

stefangrozev68 said:
Well, I recently rooted the phone. There is also SuperSU on it.. I don`t know whether this changes something.
Click to expand...
Click to collapse
depends on if you changed something else. if you just have root, no. but if you installed busybox, i know it modifies some system files
http://forum.xda-developers.com/showthread.php?t=1626895
follow that. easiest way to go back to stock. if you dont want to lose you data, just dont flash userdata.img
DONT USE ODIN.

Zepius said:
depends on if you changed something else. if you just have root, no. but if you installed busybox, i know it modifies some system files
http://forum.xda-developers.com/showthread.php?t=1626895
follow that. easiest way to go back to stock. if you dont want to lose you data, just dont flash userdata.img
DONT USE ODIN.
Click to expand...
Click to collapse
My Phone is encrypted, does that make any difference?

irvingh30 said:
My Phone is encrypted, does that make any difference?
Click to expand...
Click to collapse
In a short answer, yes. The OTA update needs to verify that the software on your phone matches what it needs to update. This is why you will get a "signature verification failed" message. If you phone is encrypted, the OTA updater will not be able to verify that software. Decrypt your phone, once complete goto settings - about phone - system updates and retry to download and install the OTA update.
---------- Post added at 10:40 AM ---------- Previous post was at 10:38 AM ----------
Let's keep this simple guys... If you want the OTA update to work properly and reliably you must be completely stock. No root, no mods, no encryption, no nothing! Most people having issues with the OTA not working fail to mention some little mod they installed making them not "completely stock".

jaizero said:
[/COLOR]Let's keep this simple guys... If you want the OTA update to work properly and reliably you must be completely stock. No root, no mods, no encryption, no nothing! Most people having issues with the OTA not working fail to mention some little mod they installed making them not "completely stock".
Click to expand...
Click to collapse
this and always this. there have been so many of these threads i feel like im on repeat

I don't know about any mods or anything I just bought the phone a few months ago.
The screen shot may throw a little more light here and tell you guys exactly what I have.
Sent from my Galaxy Nexus using xda app-developers app

But how?
jaizero said:
In a short answer, yes. The OTA update needs to verify that the software on your phone matches what it needs to update. This is why you will get a "signature verification failed" message. If you phone is encrypted, the OTA updater will not be able to verify that software. Decrypt your phone, once complete goto settings - about phone - system updates and retry to download and install the OTA update.
---------- Post added at 10:40 AM ---------- Previous post was at 10:38 AM ----------
Let's keep this simple guys... If you want the OTA update to work properly and reliably you must be completely stock. No root, no mods, no encryption, no nothing! Most people having issues with the OTA not working fail to mention some little mod they installed making them not "completely stock".
Click to expand...
Click to collapse
Sorry for my ignorance here again man
but, how do I do that, do you mean i have to factory reset the phone..?

Everything went successfully! Thank you all friends!! :highfive:

Problem installing the OTA...Where can I find a default build.prop file?

I am trying to run the OTA.
I'm rooted, s-off, etc. so, in order to do this, I had to flash stock recovery and also enable all the apps that I had disabled.
When I try to run the OTA, it fails. The log says "unexpected content in system/build.prop".
I then realized that some "root" apps modify the build.prop, so I uninstalled all of them and rebooted the phone. However that didn't work —OTA still fails for the same reason.
Could someone could tell me what RUU (or stock nandroid or other file) I should download which would allow me to extract a default build.prop??
Thanks!

syntropic said:
I am trying to run the OTA.
I'm rooted, s-off, etc. so, in order to do this, I had to flash stock recovery and also enable all the apps that I had disabled.
When I try to run the OTA, it fails. The log says "unexpected content in system/build.prop".
I then realized that some "root" apps modify the build.prop, so I uninstalled all of them and rebooted the phone. However that didn't work —OTA still fails for the same reason.
Could someone could tell me what RUU (or stock nandroid or other file) I should download which would allow me to extract a default build.prop??
Thanks!
Click to expand...
Click to collapse
Are you SuperCID? If so, there is no need to return to stock.
If not, here are the instructions:
S-OFF ONLY! How to get supercid
1. Have adb and fastboot set up. There are guides all over xda and google
2. Connect phone to PC and open terminal
3. Type "adb devices" to make sure phone is connected to PC
4. Type "adb reboot bootloader"
5. Once in fastboot type "fastboot devices" to make sure fastboot sees your device
6. Type "fastboot oem rebootRUU"
7. Once in black screen that says HTC you are in ruu mode
8. Type "fastboot oem writecid 11111111"
9. After a successful cid overwrite type "fastboot reboot-bootloader"
10. Profit! You are now supercid!!
(via @skulldreamz from this thread)
Once you do that, you will never need to get an OTA. You will always have the latest and greatest before your carrier does.
---------- Post added at 07:42 PM ---------- Previous post was at 07:37 PM ----------
But yes, your problem probably lies with your /system partition being modified.
If you have Xposed installed, that would also lead to these problems, since it modifies /system

xunholyx said:
Are you SuperCID? If so, there is no need to return to stock.
If not, here are the instructions:
{...}
[/COLOR]But yes, your problem probably lies with your /system partition being modified.
If you have Xposed installed, that would also lead to these problems, since it modifies /system
Click to expand...
Click to collapse
Ok.. then it's xposed. Thanks!
If I do superCID (something I never thought was necessary since I am probably going to stay with t-mobile), then how do I install the OTA? I have a copy of the OTA which already automatically downloaded (saved a copy on Google Drive). How does having superCID bypass the updater-script which does all those pre-update checks?

syntropic said:
Ok.. then it's xposed. Thanks!
If I do superCID (something I never thought was necessary since I am probably going to stay with t-mobile), then how do I install the OTA? I have a copy of the OTA which already automatically downloaded (saved a copy on Google Drive). How does having superCID bypass the updater-script which does all those pre-update checks?
Click to expand...
Click to collapse
If you are SuperCID, you won't need OTAs. As soon as the newest version comes out, you'll be able to install it way before your carrier updates (unless your carrier gets the first HTC update, good luck with that).
As soon as the new stuff comes out, being SuperCID means you can use firmware from any carrier (gsm or cdma dependant) and update to the newest version.
5.0 is coming soon ~ might be up to a three month wait if not SuperCID. Just sayin.............

Even if I am using the stock? What you are describing sounds like AOSP or genuine nexus-type android updates. I wouldn't even know how to install them. I have never actually dealt with "updates" before. In the past on other phones on which I ran custom ROMs, "updates" typically came when whoever was creating the Rom, generated a new Rom which included the android update.

syntropic said:
Even if I am using the stock? What you are describing sounds like AOSP or genuine nexus-type android updates. I wouldn't even know how to install them. I have never actually dealt with "updates" before. In the past on other phones on which I ran custom ROMs, "updates" typically came when whoever was creating the Rom, generated a new Rom which included the android update.
Click to expand...
Click to collapse
Of course not stock. Updates from the ROM developer.
If you wanted to stay "stock", there are custom ROMs that are like that. The devs make it into a zip that is available and flashable for the rooted user.
EDIT: If you want help you can PM me.
That's not an invitation to others.

xunholyx said:
Of course not stock. Updates from the ROM developer.
If you wanted to stay "stock", there are custom ROMs that are like that. The devs make it into a zip that is available and flashable for the rooted user.
EDIT: If you want help you can PM me.
That's not an invitation to others.
Click to expand...
Click to collapse
I will pm you to ask some more questions, however I am leaving tomorrow for work for 3 days, and I wanted to run this update (and then flash TWRP) before I left.
So, right now, can you tell me what 2.22 stock file (nandroid or a .img or a .zip) that could be downloaded, and then from which I could unzip/unpack to get a default build.prop?
I don't want to reset everything or do a factory reset... just hoping I can use the default build.prop and run this OTA.
Or, if anyone is reading who has successfully ran the OTA--can you just copy the build.prop file for me (you can just paste the contents if that's easier)?
I am very interested in going through it line by line to figure out what the "unexpected contents" actually are.

How To Get Working Apn + Hotspot After Upgrade to NCQ26.69-64+ or With SPerry XT1766.

You Need From firmware.center / firmware / Motorola / Moto%20E4 / Stock / XT1766 /
SPERRY_SPRINT_NCQ26.69-48_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip Which Is Not For The XT1766 if You Flash This You Will Loose The Baseband And SoftBrick The Phone .
And From firmware.center / firmware / Motorola / Moto%20E4 / Stock / XT1766 /
XT1766_SPERRY_SPRINT_7.1.1_NCQ26.69-56_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip This One Have The Ratio And Modem And FsG images Of Your Phone Thats Why We Need It .
Lets Begin , if You Have This Phone You Had Noticed That After Upgrade To The Last Version The Ability To Add Apn And Modify Them And The Hotspot Wont Work Any More This Is Because The Locked Everything Up For No Reason Well Money Is the Reason , We need to Extract XT1766_SPERRY_SPRINT_7.1.1_NCQ26.69-56_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip in a folder and SPERRY_SPRINT_NCQ26.69-48_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
in other folder , you must know your way to flash servicefile.xml on linux or windows no details here and bootloader unlocked , well that is easy , now we have to put the files : the 2 OEM files , the 4 System Files , boot.img ,
{{{ bootloader "NO NEED" This Work Before Just Because v48 and v56 have the same bootloader version }}} , recovey.img from SPERRY_SPRINT_NCQ26.69-48_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip inside the folder that have the XT1766_SPERRY_SPRINT_7.1.1_NCQ26.69-56_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip firmware and replace those files , optional for rooting you can replace recovery.img with the Squid2 TWRP recovery.img file and The boot.img Patched Fixed F2FS kernel which is based in the stock firmware kernel sources that we are going to flash here and then flash supersu inside twrp , Well Thats It after Flashing This Downgrade Custom stock you will have back the ability to ADD apn's Again And Use The Hotspot included in the Stock Firmware , Cheers , Thanks To All The People Involved in the development for Perry Moto E4 Thanks Everybody i hope this help somebody with the XT1766. :laugh:
EDIT HELLO
Things Have Changed Dont Try To Downgrade Bootloader or The Phone Will Get Hard Bricked , Why well bootloader versions on new firmwares have been upgraded please check all the information on the Bootloader/Fastboot
MODE Of The Phone Which Version You Have , Now For Example If You Are On Version NCQS26.69-64-5 you will need SPERRY_SPRINT_NCQS26.69-64-5_cid50_XT1766-SS_7.1.1_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml full package then extract and now you will need SPERRY_SPRINT_NCQ26.69-48_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml extract it too , Now Just Move The 2 Oems Images And 4 System Images And Boot Image To SPERRY_SPRINT_NCQS26.69-64-5_cid50_XT1766-SS_7.1.1_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml Folder Next Look for RSD_Lite_Motorola_XML_To_Batch_Script on Google Download it And Watch The Video Of Rootjunky on how to use it. Very Simple Wish All Of You Luck And im Not Responsible Of Any Damage Of Your Phone Use This Guide On Your Own Terms.

ozmage said:
You Need From firmware.center / firmware / Motorola / Moto%20E4 / Stock / XT1766 /
SPERRY_SPRINT_NCQ26.69-48_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip Which Is Not For The XT1766 if You Flash This You Will Loose The Baseband And SoftBrick The Phone .
And From firmware.center / firmware / Motorola / Moto%20E4 / Stock / XT1766 /
XT1766_SPERRY_SPRINT_7.1.1_NCQ26.69-56_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip This One Have The Ratio And Modem And FsG images Of Your Phone Thats Why We Need It .
Lets Begin , if You Have This Phone You Had Noticed That After Upgrade To The Last Version The Ability To Add Apn And Modify Them And The Hotspot Wont Work Any More This Is Because The Locked Everything Up For No Reason Well Money Is the Reason , We need to Extract XT1766_SPERRY_SPRINT_7.1.1_NCQ26.69-56_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip in a folder and SPERRY_SPRINT_NCQ26.69-48_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
in other folder , you must know your way to flash servicefile.xml on linux or windows no details here and bootloader unlocked , well that is easy , now we have to put the files : the 2 OEM files , the 4 System Files , boot.img , bootloader , recovey.img from SPERRY_SPRINT_NCQ26.69-48_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip inside the folder that have the XT1766_SPERRY_SPRINT_7.1.1_NCQ26.69-56_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip firmware and replace those files , optional for rooting you can replace recovery.img with the Squid2 TWRP recovery.img file and The boot.img Patched Fixed F2FS kernel which is based in the stock firmware kernel sources that we are going to flash here and then flash supersu inside twrp , Well Thats It after Flashing This Downgrade Custom stock you will have back the ability to ADD apn's Again And Use The Hotspot included in the Stock Firmware , Cheers , Thanks To All The People Involved in the development for Perry Moto E4 Thanks Everybody i hope this help somebody with the XT1766. :laugh:
Click to expand...
Click to collapse
I flashed the Sprint firmware and had data working on my XT1766 after it got it's carrier update, the Sprint firmware does not soft brick the phone as I flashed it and can confirm it doesn't soft brick it, so you are incorrect in saying that.

I'm not sure if I did something wrong but after trying this, my phone kept saying, "phone stopped working". I had backed up my phone so I restored it. Any ideas on what might have happened?

dlinderaz said:
I'm not sure if I did something wrong but after trying this, my phone kept saying, "phone stopped working". I had backed up my phone so I restored it. Any ideas on what might have happened?
Click to expand...
Click to collapse
Yeah, don't try to restore system apps. Phone app has some quirks, it's in oem. There are oem hide xml files and so on. Why try to restore phone?

madbat99 said:
Yeah, don't try to restore system apps. Phone app has some quirks, it's in oem. There are oem hide xml files and so on. Why try to restore phone?
Click to expand...
Click to collapse
I restored the entire thing after flashed the indicated files causing the error message.

dlinderaz said:
I restored the entire thing after flashed the indicated files causing the error message.
Click to expand...
Click to collapse
Oh, I never tried this method. I used rsd lite to flash the firmware (the one op says will brick you, it didn't by the way). After flashing new firmware I restored only data, nothing system or boot related, and have had no issues.

madbat99 said:
Oh, I never tried this method. I used rsd lite to flash the firmware (the one op says will brick you, it didn't by the way). After flashing new firmware I restored only data, nothing system or boot related, and have had no issues.
Click to expand...
Click to collapse
Thank you so much for the info. I'll give that a try tomorrow. I appreciate your time and help.

dlinderaz said:
Thank you so much for the info. I'll give that a try tomorrow. I appreciate your time and help.
Click to expand...
Click to collapse
Keep in mind I have the virgin mobile version (sprint xt1766). Don't know which one you have. Some have had trouble with rsdlite on Windows 10, it worked fine for me though.
I used rsdlite from here
The newest one, 6.2.4 I think

Apn Xt1766
I just want to add apn and want to use hot spot again
As the phone is updated on latest build ..
I don't want the root access..
What's should I try then from previous build , can anyone
Guide me easy steps plz.

Xt1766 how to get working apn
Will anyone confirm

danishamini.saifi said:
Will anyone confirm
Click to expand...
Click to collapse
The steps are there. Just don't use the root part if you don't want root. Once you switch the files, flash the service file.xml with rsdlite.

madbat99 said:
The steps are there. Just don't use the root part if you don't want root. Once you switch the files, flash the service file.xml with rsdlite.
Click to expand...
Click to collapse
Thanks, ill try and share the result.

I've tested it.. It worked for me but there is an issue
With this method occurred as well..
While Turing on the phone " BAD KEY" msg pops up on
Black display for 4-5 seconds and then mobile shows Motorola logo...
Now what is suppose to be done to get rid off BAD KEY msg.

danishamini.saifi said:
I've tested it.. It worked for me but there is an issue
With this method occurred as well..
While Turing on the phone " BAD KEY" msg pops up on
Black display for 4-5 seconds and then mobile shows Motorola logo...
Now what is suppose to be done to get rid off BAD KEY msg.
Click to expand...
Click to collapse
That's normal if you unlock the bootloader. Flash the no verity opt encrypt, or magisk, and it will change from bad key to n/a. But there will always be a message if you unlock the bootloader.
I know you said you don't need root, so that bad key message is there to stay.

madbat99 said:
That's normal if you unlock the bootloader. Flash the no verity opt encrypt, or magisk, and it will change from bad key to n/a. But there will always be a message if you unlock the bootloader.
I know you said you don't need root, so that bad key message is there to stay.
Click to expand...
Click to collapse
oh... i got it, thanks...
just one thing more please, if i go towards rooting the phone as well, will this be removed or N/A or something will be there?

danishamini.saifi said:
oh... i got it, thanks...
just one thing more please, if i go towards rooting the phone as well, will this be removed or N/A or something will be there?
Click to expand...
Click to collapse
N/A will be there. But you can flash a new boot logo to kinda hide it. Instead of a black screen, any logo you want, maybe with a white strip at the top to hide it. I'll get you a link.
Here are some good ones. https://forum.xda-developers.com/mo...om-boot-logos-converted-t3759320/post75787882
And here is the guide to make your own
https://forum.xda-developers.com/moto-e4/how-to/replace-n-boot-image-t3687212/post74118155

@madbat99
Everything you shared was perfect I made my own logo to hide bad key apn working ..
Now I want to have thebroot access in my phone XT1766..
TWRP IS ALREADY ISTALLED ON THE PHONE AS I AM FLASHING LOGOS..
WHAT SHOULD I INSTALLED TO GET ROOT ACCESS ..
SUPER USER ETC.. PLZ SHARE WITH ME..
and the main reason to have the root access is, I want to block or disable OTA update ..
Plz confirm, how will it be possible ..as I downgraded to get working APN But phone updated again now.
I want the phone to be stopped from being updated..
Plz help me out fixing this..
Thanks

danishamini.saifi said:
@madbat99
Everything you shared was perfect I made my own logo to hide bad key apn working ..
Now I want to have thebroot access in my phone XT1766..
TWRP IS ALREADY ISTALLED ON THE PHONE AS I AM FLASHING LOGOS..
WHAT SHOULD I INSTALLED TO GET ROOT ACCESS ..
SUPER USER ETC.. PLZ SHARE WITH ME..
and the main reason to have the root access is, I want to block or disable OTA update ..
Plz confirm, how will it be possible ..as I downgraded to get working APN But phone updated again now.
I want the phone to be stopped from being updated..
Plz help me out fixing this..
Thanks
Click to expand...
Click to collapse
Just don't accept the update. You can root by flashing magisk. You will still receive update notification. You'll need to disable the moto update app. I forget which one exactly. But your phone shouldn't be able to do ota updates once you are rooted with twrp installed. The update will fail.
here is the root thread.

madbat99 said:
Just don't accept the update. You can root by flashing magisk. You will still receive update notification. You'll need to disable the moto update app. I forget which one exactly. But your phone shouldn't be able to do ota updates once you are rooted with twrp installed. The update will fail.
here is the root thread.
Click to expand...
Click to collapse
Thank you. I wish I had known this. I had to flash the stock recovery, etc for the updates to work. A little bit of an unnecessary hastle.

dlinderaz said:
Thank you. I wish I had known this. I had to flash the stock recovery, etc for the updates to work. A little bit of an unnecessary hastle.
Click to expand...
Click to collapse
Ota updates will likely always fail if you have twrp, or have modified the system in any way. The ota performs many checks (assert props) to see if the system is clean. If any asserts fail, the ota will fail. Even restoring the stock recovery doesn't guarantee the ota will work.