Problems After Rooting Nougat. - X Style (Pure) Q&A, Help & Troubleshooting

Recently I rooted nougat using 'BETA-SuperSU-v2.74-2-20160519174328-forced-systemless' zip. After that wifi wasnt working and sim card didnt get detected. I downgraded to 6.0 and the problem remained the same. I tried flashing lineage OS 14.1 but stucked into bootloop. Only 6.0 based roms are working, currently Iam using Lineage OS 13 ,wifi and sim card is working but 'security settings' stops working whenever i try to setup a pin or pattern for the lockscreen.
What can I do to get back to proper stock nougat or marshmallow?
Help!!
#noob

amans2274 said:
Recently I rooted nougat using 'BETA-SuperSU-v2.74-2-20160519174328-forced-systemless' zip. After that wifi wasnt working and sim card didnt get detected. I downgraded to 6.0 and the problem remained the same. I tried flashing lineage OS 14.1 but stucked into bootloop. Only 6.0 based roms are working, currently Iam using Lineage OS 13 ,wifi and sim card is working but 'security settings' stops working whenever i try to setup a pin or pattern for the lockscreen.
What can I do to get back to proper stock nougat or marshmallow?
Help!!
#noob
Click to expand...
Click to collapse
You should've just reflashed 7.0, I might be fuzzy with this one but once you upgrade I believe you can't downgrade. Try and reflash 7.0 stock and see what you get

cdiamond said:
You should've just reflashed 7.0, I might be fuzzy with this one but once you upgrade I believe you can't downgrade. Try and reflash 7.0 stock and see what you get
Click to expand...
Click to collapse
I am looking for the stock asian 7.0 firmware. Can't find any mirrors. Thought of OTA update through marshmallow again but the wifi isnt working.

Your device is xt1752 right?
Sent from my XT1575 using Tapatalk

@amans2274
You shouldn't ask here.
You have to flash the newest stock 6.0.x for your model.
There isn't 7.0 for fastboot.

dzidexx said:
@amans2274
You shouldn't ask here.
You have to flash the newest stock 6.0.x for your model.
There isn't 7.0 for fastboot.
Click to expand...
Click to collapse
i know how to flash it but the wifi and sim card isnt working..orelse wouldnt have asked..and sorry for posting in the wrong section
cdiamond said:
Your device is xt1752 right?
Sent from my XT1575 using Tapatalk
Click to expand...
Click to collapse
yes

amans2274 said:
yes
Click to expand...
Click to collapse
I mean I would do what the other guy said, flash the right files for YOUR device. And see if you can get to 7.0 via ota
Sent from my XT1575 using Tapatalk

cdiamond said:
I mean I would do what the other guy said, flash the right files for YOUR device. And see if you can get to 7.0 via ota
Sent from my XT1575 using Tapatalk
Click to expand...
Click to collapse
I did flash the correct files....but problem remains the same as i said in the main post.
Should i consider giving it in service centre because its still in warranty.

amans2274 said:
I did flash the correct files....but problem remains the same as i said in the main post.
Should i consider giving it in service centre because its still in warranty.
Click to expand...
Click to collapse
May not be in warranty - unlocked bootloader.
Read again this:
https://forum.xda-developers.com/moto-x-style/general/guide-flashing-stock-firmware-t3637235 #1 (important), #4 root,
https://forum.xda-developers.com/moto-x-style/help/to-stock-wi-fi-t3652039
Stock download - my signature.
RetAsia - single sim, RetAsiaDS - dual sim.

dzidexx said:
May not be in warranty - unlocked bootloader.
Read again this:
https://forum.xda-developers.com/moto-x-style/general/guide-flashing-stock-firmware-t3637235 #1 (important), #4 root,
https://forum.xda-developers.com/moto-x-style/help/to-stock-wi-fi-t3652039
Stock download - my signature.
RetAsia - single sim, RetAsiaDS - dual sim.
Click to expand...
Click to collapse
Zip ...58-5 is good.
Maybe you should flash modem(radio) twice.
Repeat only this:
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot flash bluetooth BTFM.bin
what basically i have to do?...paste each code twice in the cmd?...please bear with me really a noob
'fastboot flash partition gpt.bin' getting prevalidation error again n again

amans2274 said:
Zip ...58-5 is good.
Maybe you should flash modem(radio) twice.
Repeat only this:
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot flash bluetooth BTFM.bin
Click to expand...
Click to collapse
You should flash full stock 6.0.x, every command should end with ok.
/Only bootloader & gpt will end with error, doesn't matter/
Repeat(qouted) - all 5 commands and repeat 5 again.
---------- Post added at 09:28 AM ---------- Previous post was at 09:23 AM ----------
Give here screenshots from pc(cmd, fastboot flashing).
Or upload to GDrive and give link.

dzidexx said:
You should flash full stock 6.0.x, every command should end with ok.
/Only bootloader & gpt will end with error, doesn't matter/
Repeat(qouted) - all 5 commands and repeat 5 again.
---------- Post added at 09:28 AM ---------- Previous post was at 09:23 AM ----------
Give here screenshots from pc(cmd, fastboot flashing).
Or upload to GDrive and give link.[/QUOTE
Worked like a charm:good:Thank you sooo much.
Getting OTA Nougat now. can i flash lineage 14.1 through twrp on stock nougat?
Click to expand...
Click to collapse

amans2274 said:
dzidexx said:
You should flash full stock 6.0.x, every command should end with ok.
/Only bootloader & gpt will end with error, doesn't matter/
Repeat(qouted) - all 5 commands and repeat 5 again.
---------- Post added at 09:28 AM ---------- Previous post was at 09:23 AM ----------
Give here screenshots from pc(cmd, fastboot flashing).
Or upload to GDrive and give link.[/QUOTE
Worked like a charm:good:Thank you sooo much.
Getting OTA Nougat now. can i flash lineage 14.1 through twrp on stock nougat?
Click to expand...
Click to collapse
For any custom 14.1 you have to downgrade radios.
Again these commands , only 4 commands(without BT).
Click to expand...
Click to collapse

I can root the stock ROM 7.0 nougat with magistick

Related

New factory 5.1 image just posted

New factory 5.1 image just posted
https://developers.google.com/android/nexus/images
I also saw this have you tried it yet?
arodhr13 said:
I also saw this have you tried it yet?
Click to expand...
Click to collapse
Na i'll wait for developer to post a twrp flashable version. Interested to see what they fixed though.
Yeah me to.
thats the same version number as is on the Verizon version...
cmh714 said:
thats the same version number as is on the Verizon version...
Click to expand...
Click to collapse
Did anyone ever figure out what the changes between D and E are?
at the very least the radios are different....95 in the D image and 98 in the E image.
So I have a Motorola Nexus 6 that I just flashed the OTA for (LMY47D). Did I screw up not waiting for this version since I use this on Verizon?
Huh I sideloaded the OTA so I guess to get the new radio I need to unlock the bootloader and flash just the radio?
I'm flashing the new radio now. (t-mobile)
---------- Post added at 12:16 PM ---------- Previous post was at 12:16 PM ----------
Gage_Hero said:
Huh I sideloaded the OTA so I guess to get the new radio I need to unlock the bootloader and flash just the radio?
Click to expand...
Click to collapse
Yup, assuming that is the only change.
phoenixus said:
So I have a Motorola Nexus 6 that I just flashed the OTA for (LMY47D). Did I screw up not waiting for this version since I use this on Verizon?
Click to expand...
Click to collapse
no, not really....the 47D radio works fine on VZW.....some have reported that the 47E works better, others have said its the same.....YMMV
I havent flashed the 98 radio yet but more than likely will
---------- Post added at 09:27 AM ---------- Previous post was at 09:18 AM ----------
The E version from Google is 16MB smaller than the VZW version as well....
I didn't notice any change from the radio that was in 5.01, just sideloaded on Sunday but the few data tests show LTE to be worse than before.... wifi on the other hand did improve. I guess I'll just wait and see what others have to say about radio 98 as opposed to 95...
cmh714 said:
at the very least the radios are different....95 in the D image and 98 in the E image.
Click to expand...
Click to collapse
boot.img, recovery.img and system.img are also different, according to 'diff'.
Will give this a whirl later this evening...
mijkz said:
boot.img, recovery.img and system.img are also different, according to 'diff'.
Will give this a whirl later this evening...
Click to expand...
Click to collapse
So if those are all different, there must be an OTA out there or on the way also?
phoenixus said:
So I have a Motorola Nexus 6 that I just flashed the OTA for (LMY47D). Did I screw up not waiting for this version since I use this on Verizon?
Click to expand...
Click to collapse
No, you didn't screw up. That "was" (LMY47D) the latest factory image posted for the Nexus 6, this is "now" (LMY47E) the latest factory image for the Nexus 6. Just flash the newer one now....if you want.
phoenixus if you did a side load like me, to use the factory image, you need to unlock the bootloader... just be aware this will wipe the device so save anything you want to keep to your PC first..... picture, songs, etc......
mijkz said:
boot.img, recovery.img and system.img are also different, according to 'diff'.
Will give this a whirl later this evening...
Click to expand...
Click to collapse
OK, so I've flashed LMY47E on my stock 5.1 (rooted and TWRP) and it's working fine (3 UK network):
Rebooted to bootloader
fastboot flash radio radio.img
fastboot reboot-bootloader
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash cache cache.img (maybe not necessary for such a minor update)
fastboot reboot
Warning: this sets recovery back to stock (even if you don't flash recovery.img) so you have to then:
fastboot flash recovery openrecovery-twrp-2.8.5.0-shamu
IMMEDIATELY reboot into recovery by scrolling to the recovery option in the bootloader and pressing the power button
flash SuperSU
Reboot and you're done.
Anyone figure out what the changes are?
From Android Police :
People, this is the firmware variant that shipping on devices purchased from Verizon. Pre-orders have shipped and people are beginning to receive them today. If you own a Nexus 6 that wasn't purchased from Verizon, you won't be getting LMY47E over the air or anything else. The two branches will be merged with the next OTA, presumably.
There is, for all intents and purposes, no reason to use this over LMY47D, unless you're using your phone on Verizon and/or want the newer radio. And even if you are using Verizon, LMY47D works fine.
So I am slightly confused.... in this thread, everyone talks about flashing the factory images with fastboot.... in this thread http://forum.xda-developers.com/nexus-6/general/stock-verizon-nexus-6-firmware-image-t3053052/page9 they are all talking about mfastboot. I am going to guess booting into recovery and issuing adb commands that have been repeated here a few times (after unlocking the bootloader of course) will get the job done correct?

How to Upgrade to Android 5.1: 23.16.3 (FOR MOTO X Pure Edition ONLY)

For Moto X Pure Edition(XT1095) ONLY
There has been a bit of confusion on how to do this, or the instructions are deep inside the other threads. So this is just to make it easier to find
Despite what people are saying on Reddit DO NOT DOWNGRADE TO Android 4.4.4, IT IS A HUGE RISK AND COULD POSSIBLY HARD BRICK YOUR DEVICE
IF YOU ARE ON 23-11-14 SKIP TO PART B ON THE #3 POST BELOW
PART A
Motorola released the new Android 5.1 OTA (23.16.3) and of course as of right now the original soak test users(23.1.28) have been left out. Now unfortunately in order to install the new OTA you must downgrade back to Android 5.0 ,which requires you to unlock your bootloader( Now, because you have the XT1095 Pure Edition this will NOT void your warranty). However you can relock the bootloader AFTER downgrading.
Proof that it doesn't void warranty found here >>>>> http://forum.xda-developers.com/moto-x-2014/general/unlocking-bootloader-moto-x-pure-t3004779
-The Guide to do this can be found on Motorola's site here >>>>> https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images
The guide is at the bottom below downloads.... Make Sure you follow those instructions carefully as I am NOT RESPONSIBLE for you bricking your device!
DO NOT FLASH bootloader (motoboot) and partition table (gpt) Thanks JulesJam
-Android 5.0, link found here >>>>>> http://www.graffixnyc.com/motox.php
MAKE SURE YOU DOWNGRADE TO Android 5.0: 22.21.11(Full Image) NOT 22.11.5 or 22.11.6 AS THOSE ARE OLD SOAK TEST VERSIONS
-After you downgrade to Android 5.0 you can then upgrade to the new OTA found here >>>>> http://www.graffixnyc.com/motox.php
CONGRATS you are now on the latest version of Android 5.1(23.16.3)
I will be updating this guide as I receive feedback so please be patient and keep the thread clear so users can get help as needed
THANKS
PART B
IF YOU ARE ON SOAK TEST(23.1.28) PLEASE GO TO PART A ABOVE AS THIS WILL NOT WORK FOR YOU
So as it turns out you can actually upgrade from the 5.1 soak test(23-11-14) directly to the new OTA(23.16.3). All you need to do is download the ZIP below and boot into recovery and select install/update from SD and locate the file on your phone.
https://drive.google.com/file/d/0B4wdtquycD9rMGtGZUVMc19VV0k/view
What about your data on the phone?
Do you wind up losing it ?
phonepersonality said:
What about your data on the phone?
Do you wind up losing it ?
Click to expand...
Click to collapse
Yes, unlocking the boot loader requires your phone to be wiped, after that you will be able to install each subsequent update with needing to wipe
jrdnkasparek said:
After you downgrade to Android 4.4.4 you then have to update to Android 5.0, link found here >>>>>> https://onedrive.live.com/?cid=227F163CB35629DA&id=227f163cb35629da!28119&authkey=!AMWPTB3ICDtezYs
MAKE SURE YOU UPDATE TO 22.21.11 NOT 22.11.5 or 22.11.6 AS THOSE ARE OLD SOAK TEST VERSIONS
Click to expand...
Click to collapse
People on the 60.16 bootloader have bricked doing that. I would NOT do that if you are on the 60.16 bootloader. Instead, do not downgrade to 4.4.4 - simply downgrade to the 5.0 images (system, kernel, modems, baseband, recover) by flashing them.
---------- Post added at 08:07 PM ---------- Previous post was at 08:04 PM ----------
jrdnkasparek said:
After you downgrade to Android 4.4.4
Click to expand...
Click to collapse
There is ABSOLUTELY NO REASON TO DOWNGRADE ALL THE WAY TO 4.4.4 AND IT IS DANGEROUS TO DO THIS AND THEN TAKE THE 5.0 OTA AFTER YOU HAVE BEEN ON 5.1!!!
The safer thing to do is to simply flash the full 5.0 images (except for the bootloader (motoboot) and partition table (gpt)). Why on earth would you flash back to 4.4.4 when the 5.0 stock images are available for your device? It makes no sense at all and people with XT1095's have bricked when they were on 5.1 then flashed back to 4.4.4 and took the 5.0 OTA.
It just makes no sense to do it this way.
JulesJam said:
People on the 60.16 bootloader have bricked doing that. I would NOT do that if you are on the 60.16 bootloader. Instead, do not downgrade to 4.4.4 - simply downgrade to the 5.0 images (system, kernel, modems, baseband, recover) by flashing them.
---------- Post added at 08:07 PM ---------- Previous post was at 08:04 PM ----------
There is ABSOLUTELY NO REASON TO DOWNGRADE ALL THE WAY TO 4.4.4 AND IT IS DANGEROUS TO DO THIS AND THEN TAKE THE 5.0 OTA AFTER YOU HAVE BEEN ON 5.1!!!
The safer thing to do is to simply flash the full 5.0 images (except for the bootloader (motoboot) and partition table (gpt)). Why on earth would you flash back to 4.4.4 when the 5.0 stock images are available for your device? It makes no sense at all and people with XT1095's have bricked when they were on 5.1 then flashed back to 4.4.4 and took the 5.0 OTA.
It just makes no sense to do it this way.
Click to expand...
Click to collapse
This is just what I was told in the other threads and on Reddit. I will Edit Thanks!
jrdnkasparek said:
This is just what I was told in the other threads and on Reddit. I will Edit Thanks!
Click to expand...
Click to collapse
Ok well I will bump my thread about the OTA again. Just flash back to 5.0 directly (not the BL (motoboot) or the PT (gpt) though - leave those alone).
JulesJam said:
Ok well I will bump my thread about the OTA again. Just flash back to 5.0 directly (not the BL (motoboot) or the PT (gpt) though - leave those alone).
Click to expand...
Click to collapse
Do you have a download link I could post, only one I can find is the OTA from 4.4.4 > 5.0
NVM found it!
jrdnkasparek said:
Do you have a download link I could post, only one I can find is the OTA from 4.4.4 > 5.0
NVM found it!
Click to expand...
Click to collapse
Patrick has been hosting them - everyone should download them b/c he can pull them down at any time if he doesn't want to host them any longer.
http://www.graffixnyc.com/motox.php
So, if I'm on stock v5.0 rooted with TWRP and unlocked bootloader, I could simply unroot and flash back to stock recovery and then sideload the OTA, correct? Haven't seen a clear answer on this.
the orange bandit said:
So, if I'm on stock v5.0 rooted with TWRP and unlocked bootloader, I could simply unroot and flash back to stock recovery and then sideload the OTA, correct? Haven't seen a clear answer on this.
Click to expand...
Click to collapse
Here is a tutorial for the MX13, works same for MX14 but obviously, you use the MX14 files. And I would flash stock system before I did it.
How to SIDE LOAD an OTA.ZIP via this process
http://forum.xda-developers.com/moto-x/general/ref-return-to-stock-recovery-rooted-t3027079
Do you have to install the radios as well?
https://onedrive.live.com/?cid=804EF0BE56E7A96F&id=804ef0be56e7a96f!3262
phamine said:
Do you have to install the radios as well?
https://onedrive.live.com/?cid=804EF0BE56E7A96F&id=804ef0be56e7a96f!3262
Click to expand...
Click to collapse
What have you done to your device? Just rooted 5.0 and installed a custom recovery? Or did you take the 5.1 soak OTA? Did you flash any different radios?
What you need to do depends on what you have done.
Noob question here... The 5.0 factory image file has the system.img file separated in several sparsechunk files. How can I flash those, or put them back together into 1 file?
And... another question, do I need to use motorola's fastboot commands or is it ok with normal android ones?
Thanks a lot!!
gabrielss said:
Noob question here... The 5.0 factory image file has the system.img file separated in several sparsechunk files. How can I flash those
Click to expand...
Click to collapse
Regular fastboot.
fastboot flash system system_sparsechunk1.img
do each one until they are done.
---------- Post added at 05:25 AM ---------- Previous post was at 05:25 AM ----------
gabrielss said:
And... another question, do I need to use motorola's fastboot commands or is it ok with normal android ones?
Click to expand...
Click to collapse
sparsechunks can be flashed with regular fastboot. A single file system.img needs to be flashed with mfastboot.
JulesJam said:
What have you done to your device? Just rooted 5.0 and installed a custom recovery? Or did you take the 5.1 soak OTA? Did you flash any different radios?
What you need to do depends on what you have done.
Click to expand...
Click to collapse
I was on the the 5.1 soak.
I downgraded to 5.0 based on the guide and the below commands
$ fastboot flash logo logo.bin
$ fastboot flash boot boot.img
$ fastboot flash recovery recovery.img
$ fastboot flash system system.img
$ fastboot flash modem NON-HLOS.bin
$ fastboot erase modemst1
$ fastboot erase modemst2
$ fastboot flash fsg fsg.mbn
$ fastboot reboot
$ fastboot erase userdata
$ fastboot erase cache
Then I just sideloaded the 5.1 OTA in the guide.
Baseband version
MSM8974bp_4235210.110.09.11R
VICTARA_TMO_CUST
phamine said:
$ fastboot flash system system.img
Click to expand...
Click to collapse
Did you use mfastboot b/c regular fastboot won't boot a single file system.img.
JulesJam said:
Did you use mfastboot b/c regular fastboot won't boot a single file system.img.
Click to expand...
Click to collapse
Yes. I installed each sparsechunk.
Is the radio version the current 5.1 OTA radio?
phamine said:
$ fastboot flash modem NON-HLOS.bin
$ fastboot erase modemst1
$ fastboot erase modemst2
$ fastboot flash fsg fsg.mbn
Click to expand...
Click to collapse
If you did this using the stock 5.0 images, then you are back on the 5.0 radios.

New Modified emmc file for unlocking Bootloader without permission from Xiaomi.

So this a new modified emmc_appsboot.mbn for unlocking bootloader via unofficial way.
Whats changed?
Fixed the bug of red LED blinking continuously during charging.
For those who unlocked bootloader via unofficial way from this thread http://forum.miui.co.in/forum/mi-de...5165-redmi-note-3-snapdragon-unlock-the-beast, just use this method to flash the new emmc file:-
1) Reboot to fastboot mode
2) Open CMD and type
fastboot flash aboot emmc_appsboot.mbn
fastboot flash abootbak emmc_appsboot.mbn
The emmc file must inside the anf folder
For new comers, you can use the same method as the previous one by MAGDAG, just use this new emmc file instead of his.
This new emmc file needs thorough testing, maybe this will also cause hardbricks if MIUI roms are flashed without deleting their default emmc file (inside their rom), maybe this will not cause any such issues but nobody will take the risk of testing that. Just use this new emmc with precautions just like the previous one. How to flash MIUI roms via TWRP after unofficially unlocking bootloader? follow this guide made by me http://en.miui.com/thread-256464-1-1.html
This is not the edited version of MAGDAG's emmc file. This one's is new and needs to be tested.
I'M NOT RESPONSIBLE FOR ANY BRICKED DEVICES.
Please provide feedback if this worked for you.
How to revert back to locked state ?
fcukmayank said:
How to revert back to locked state ?
Click to expand...
Click to collapse
flash any fastboot rom in edl mode using miflash
Rajdip said:
flash any fastboot rom in edl mode using miflash
Click to expand...
Click to collapse
Will it not hardbrick if i have twrp and root ?
fcukmayank said:
Will it not hardbrick if i have twrp and root ?
Click to expand...
Click to collapse
no, I tested it
Cool . thanks for the info
But i hv global stable 7.2.3.0 and modified boot image is not yet available
I tried downgrading to 7.1.8.0 but it bootlooped at mi logo
I had to flash 7.1.8.0 again
This all drama when i have permission to unlock the xiaomi but stuck at 50% error
fcukmayank said:
Cool . thanks for the info
But i hv global stable 7.2.3.0 and modified boot image is not yet available
I tried downgrading to 7.1.8.0 but it bootlooped at mi logo
I had to flash 7.1.8.0 again
This all drama when i have permission to unlock the xiaomi but stuck at 50% error
Click to expand...
Click to collapse
I can understand, If I find the link for full 7.2.3 recovery rom today, I'll post it, if you need modified boot.img you have to first downgrade to 7.1.3.0 and use updater app, it will give a full recovery rom of 1gb for update, find the boot.img of 7.2.3.0 from that zip and modify it then flash.
P.S:- never forget to delete the original emmc_appsboot file in each rom.
Rajdip said:
I can understand, If I find the link for full 7.2.3 recovery rom today, I'll post it, if you need modified boot.img you have to first downgrade to 7.1.3.0 and use updater app, it will give a full recovery rom of 1gb for update, find the boot.img of 7.2.3.0 from that zip and modify it then flash.
P.S:- never forget to delete the original emmc_appsboot file in each rom.
Click to expand...
Click to collapse
I can downgrade to 7.1.8.0 but i hv to flash twice to overcome bootloop
Just scared of using this unofficial method as last time i bricked it and the service center had to replace the motherboard
fcukmayank said:
I can downgrade to 7.1.8.0 but i hv to flash twice to overcome bootloop
Just scared of using this unofficial method as last time i bricked it and the service center had to replace the motherboard
Click to expand...
Click to collapse
it will brick if you forget to delete the emmc_appsboot file from each rom you are flashing, otherwise you are safe to go. guide to flash without harbrick is in OP
Rajdip said:
it will brick if you forget to delete the emmc_appsboot file from each rom you are flashing, otherwise you are safe to go. guide to flash without harbrick is in OP
Click to expand...
Click to collapse
Yes
That i realised after hardbricking
Wanted root for adblocker but now i found this app called adguard
So trying to live without root
fcukmayank said:
Yes
That i realised after hardbricking
Wanted root for adblocker but now i found this app called adguard
So trying to live without root
Click to expand...
Click to collapse
:good:
Rajdip said:
:good:
Click to expand...
Click to collapse
I think i have solved the problem of 50%error
Gonna try it and apply for unlocking again
Only sd?
Sent from my Redmi Note 3 using XDA-Developers mobile app
qweewq22 said:
Only sd?
Sent from my Redmi Note 3 using XDA-Developers mobile app
Click to expand...
Click to collapse
yeah this is for snapdragon variant
Rajdip said:
yeah this is for snapdragon variant
Click to expand...
Click to collapse
Name of the zip rom : miui_HMNote3ProGlobal_V7.2.3.0.LHOMIDA_74136dde89_5.1.zip
fcukmayank said:
I think i have solved the problem of 50%error
Gonna try it and apply for unlocking again
Click to expand...
Click to collapse
Is the process of removing emmc file also required for bootloaders which have been unlocked officially ?
And hv u compared the 2 files of unofficial and official method
fcukmayank said:
Is the process of removing emmc file also required for bootloaders which have been unlocked officially ?
And hv u compared the 2 files of unofficial and official method
Click to expand...
Click to collapse
no only for unofficial method, and I compared both the official and unofficial file they are different but I know of a way by which we can unlock bootloader unofficially but it'll work just like the official way. Need someone who unlocked via official way, then flash twrp version 3.0.0-0(other versions wont work) and reboot to twrp and select backup and then scroll down and select aboot and abootbak, we can use that aboot for us and solve all problems of hardbrick, but no one's helping me :crying:
Rajdip said:
no only for unofficial method, and I compared both the official and unofficial file they are different but I know of a way by which we can unlock bootloader unofficially but it'll work just like the official way. Need someone who unlocked via official way, then flash twrp version 3.0.0-0(other versions wont work) and reboot to twrp and select backup and then scroll down and select aboot and abootbak, we can use that aboot for us and solve all problems of hardbrick, but no one's helping me :crying:
Click to expand...
Click to collapse
I have got permission twice from 2 different accounts but still stuck at 50%error
I bricked my device and the motherboard had to be replaced which took 8 days :/
---------- Post added at 04:04 PM ---------- Previous post was at 03:48 PM ----------
Keep working
The moment my official unlock happens i m gonna pull these files for u
Rajdip said:
So this a new modified emmc_appsboot.mbn for unlocking bootloader via unofficial way.
Whats changed?
Fixed the bug of red LED blinking continuously during charging.
For those who unlocked bootloader via unofficial way from this thread http://forum.miui.co.in/forum/mi-de...5165-redmi-note-3-snapdragon-unlock-the-beast, just use this method to flash the new emmc file:-
1) Reboot to fastboot mode
2) Open CMD and type
fastboot flash aboot emmc_appsboot.mbn
fastboot flash abootbak emmc_appsboot.mbn
The emmc file must inside the anf folder.........................................)
Click to expand...
Click to collapse
Thx for mod
my redmi n3p have lock bootloader now
Reacap:
1- flash the global stable 7.1.8 (Magdag metod) with repalce emmc_appsboot.mbn modified by you
2- flash twrp
2- update rom to twrp but deleting the stock emmc_appsboot.mbn inside zip file
It's all correct?
To return to original stock rom flash the latest global stable via EDL?
fcukmayank said:
I have got permission twice from 2 different accounts but still stuck at 50%error
I bricked my device and the motherboard had to be replaced which took 8 days :/
---------- Post added at 04:04 PM ---------- Previous post was at 03:48 PM ----------
Keep working
The moment my official unlock happens i m gonna pull these files for u
Click to expand...
Click to collapse
thanks a lot man

System Staus- " Modified"

Hello Xdians, I am running G4 Plus XT1643
I recently flashed elemental x on MM
After flashing that i am getting system status as Modified instead of Official ... Can anybody help!!
Is it because of elemental x
I tried a clean flash of custom rom but issue still persists ....
I have to sell the phone ..Pls help
T h a n k s
Downgrade to lower version of MM (139-23, i think, not sure ) and you will receive latest update of MM (139-63)... It will make it official...
Sharp404 said:
Hello Xdians, I am running G4 Plus XT1643
I recently flashed elemental x on MM
After flashing that i am getting system status as Modified instead of Official ... Can anybody help!!
Is it because of elemental x
I tried a clean flash of custom rom but issue still persists ....
I have to sell the phone ..Pls help
T h a n k s
Click to expand...
Click to collapse
That's because you flashed EX kernel. This overwrites your stock kernel (boot.img) with EX kernel. Your bootloader only considers stock (Motorola) ROM files as 'official' including the kernel.
Obviously when you flashed a custom ROM it won't have Moto files as they have their own kernels.
To get it it back to official you need to revert to stock MM using this guide:
https://r.tapatalk.com/shareLink?ur...share_tid=3460695&share_fid=3793&share_type=t
This should solve your issue
Note: It will wipe all your files and remove root, etc as it will make your phone just like how you got it when purchased.
Sent from my Moto G (4) using Tapatalk
Sharp404 said:
I have sideloaded the latest Nougat Ota/ soak ( debatable) ..it still persists
Thanks
Click to expand...
Click to collapse
Move your question here from development thread, i clearly said OTA, sideloading zip is not OTA...
Once you unlock the bootloader it will always show modified in the bootloader. You can't revert back to official once it's unlocked therefore modified. I already reverted back to stock firmware using fastboot and it's still considered modified.
daverobinson88 said:
Once you unlock the bootloader it will always show modified in the bootloader. You can't revert back to official once it's unlocked therefore modified. I already reverted back to stock firmware using fastboot and it's still considered modified.
Click to expand...
Click to collapse
I am not sure if what you said was right. Unlocking bootloader won't change the status to unofficial on the screen but it does essentially void your warranty. Even if you unlock, the device will still show it as official until and unless you decide to play with /system or /oem or root or custom kernel. Other than that, I believe it will still show it as official even though unlocked.
System status changes if you modify stock firmware.
It doesnt have to do anything with locked or unlocked bootloader.
I successfully changed my system status from modified to official even with unlocked bootloader.
ASB41 said:
System status changes if you modify stock firmware.
It doesnt have to do anything with locked or unlocked bootloader.
I successfully changed my system status from modified to official even with unlocked bootloader.
Click to expand...
Click to collapse
How did you do that?
D4N6L4CK said:
How did you do that?
Click to expand...
Click to collapse
He would've flashed the stock MM image via fastboot.
Sent from my Moto G (4) using Tapatalk
1chrome said:
He would've flashed the stock MM image via fastboot.
Sent from my Moto G (4) using Tapatalk
Click to expand...
Click to collapse
I already tried that, but it didn't work.
ASB41 said:
System status changes if you modify stock firmware.
It doesnt have to do anything with locked or unlocked bootloader.
I successfully changed my system status from modified to official even with unlocked bootloader.
Click to expand...
Click to collapse
Tell me the full process
@a-2-k @D4N6L4CK
Flash older version of MM,
Then you will receive OTA of latest MM..
it will make it OFFICIAL again...
I do the same process but I am not succes still show status modified
---------- Post added at 10:43 AM ---------- Previous post was at 10:41 AM ----------
Sorry I flash the old stock rom and I used my phone 15 days but I did not receive any ota update...sorry for my bad english
a-2-k said:
Sorry I flash the old stock rom and I used my phone 15 days but I did not receive any ota update...sorry for my bad english
Click to expand...
Click to collapse
What is version of old stock you flashed..?
What is your phone's Model no. ??
__Madddy said:
What is version of old stock you flashed..?
What is your phone's Model no. ??
Click to expand...
Click to collapse
Xt1643
MPJ24.139-13.1
a-2-k said:
Xt1643
MPJ24.139-13.1
Click to expand...
Click to collapse
I also have xt1643 and i tried old MM (139-23.1) and successfully received MM (139-63) with OFFICIAL status..
Get old MM from here http://forum.xda-developers.com/showpost.php?p=68780680&postcount=26
First I Downgrade nougat to MM (MPJ24.139.13.1)
I am using my phone after downgrade 15 days but still not get any ota update can you give me cmd you type when you flash your phone .....
I am downgrade my phone this method
fastboot flash boot boot.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot erase userdata
fastboot reboot
If my method is wrong to receive any ota then you tell me the solution to flash stock rom
---------- Post added at 11:08 AM ---------- Previous post was at 11:04 AM ----------
__Madddy said:
I also have xt1643 and i tried old MM (139-23.1) and successfully received MM (139-63) with OFFICIAL status..
Get old MM from here http://forum.xda-developers.com/showpost.php?p=68780680&postcount=26
Click to expand...
Click to collapse
Just tell me your method to flash stock rom nd which code do u use to flash ...your rom
@a-2-k go here http://forum.xda-developers.com/showpost.php?p=67031808&postcount=4
If Gpt.bin gives error, just skip that command line...
D4N6L4CK said:
How did you do that?
Click to expand...
Click to collapse
1. Download older firmware :- MPJ139-23.1.
2. boot into twrp & format dalvik/cache/system/data/internal storage & then poweroff device.
3. GOTO :- http://forum.xda-developers.com/moto-g4-plus/how-to/how-to-downgrade-nougat-to-marshmallow-t3487201
Use that code to flash firmware using fastboot.
4. Now after booting you will get ota update around 500mb. Update & you will get official status.
5. That's all i did. It worked perfectly for me. I've xt1643 model.
ASB41 said:
1. Download older firmware :- MPJ139-23.1.
2. boot into twrp & format dalvik/cache/system/data/internal storage & then poweroff device.
3. GOTO :- http://forum.xda-developers.com/moto-g4-plus/how-to/how-to-downgrade-nougat-to-marshmallow-t3487201
Use that code to flash firmware using fastboot.
4. Now after booting you will get ota update around 500mb. Update & you will get official status.
5. That's all i did. It worked perfectly for me. I've xt1643 model.
Click to expand...
Click to collapse
Going try this method

Baseband file for XT1643 (ATHENE_INDIA) needed

No network on any ROM (stock & LOS-based ROMs). I might have flashed the wrong baseband file, can someone please give me the baseband specifically for India? Baseband required - M8952_70030.25.03.62.01R ATHENE_INDIA_DSDS_CUST
meraj99 said:
I'm on RR Remix N and have TWRP 3.1.1 shreps for the recovery. I can flash RR without any issues but whenever I try flashing either a JX series ROM or a fully stock ROM, TWRP says 'Invalid Zip File Format'. I have access to both bootloader and recovery, everything else works fine. Can someone please guide me on what to do? Do I have to sideload the ROM via ADB? If so, please enlighten me about the procedure
Click to expand...
Click to collapse
Why not trying to reflash the twrp(may try another one from official website or of silesh nair on his thread).
I think you might have turn on md5 checksum or another this which keeps verifying the zip and no signature is found.
Reflashing is a good course as it do not erase any data of yours.
DgnrtnX said:
Why not trying to reflash the twrp(may try another one from official website or of silesh nair on his thread).
I think you might have turn on md5 checksum or another this which keeps verifying the zip and no signature is found.
Reflashing is a good course as it do not erase any data of yours.
Click to expand...
Click to collapse
I used 3 different versions of TWRP Still didn't help. And the MD5 checksums matched, zip signature verification has been disabled too
meraj99 said:
I used 3 different versions of TWRP [emoji14] Still didn't help. And the MD5 checksums matched, zip signature verification has been disabled too
Click to expand...
Click to collapse
Try this and report. After installing wipe cache, dalvik.
If flashing recovery is problem, reflash stock rom w/ stock recovery n boot ans try again to flash twrp, might sovle the issue
Link : https://drive.google.com/file/d/1EGS-uU1QBDbrP3G4lFUSVqDSHC_ZGpMR/view?usp=sharing
Sent from my Moto G4 Plus using Tapatalk
DgnrtnX said:
Try this and report. After installing wipe cache, dalvik.
If flashing recovery is problem, reflash stock rom w/ stock recovery n boot ans try again to flash twrp, might sovle the issue
Link : https://drive.google.com/file/d/1EGS-uU1QBDbrP3G4lFUSVqDSHC_ZGpMR/view?usp=sharing
Sent from my Moto G4 Plus using Tapatalk
Click to expand...
Click to collapse
can you please tell me how to use the stock recovery? It just says 'No Command' everytime I boot into it
meraj99 said:
can you please tell me how to use the stock recovery? It just says 'No Command' everytime I boot into it
Click to expand...
Click to collapse
Its power button followed by vol up, but hey that recovery ain't gonna help you. Im just saying you to reflash it as it will erase all the data of current twrp recovery which might interfere with another recovery(changes are negligible, but then too).
I gave you link to a 64-bit twrp made by dreamester and silesh nair. Try it and see if it works.
You can not flash stock ROM from TWRP or other custom recovery. You need a PC with Moto Drivers and fastboot tools installed. Then you have to flash the stock rom from fastboot (generally instructions are given inside rom zip in a file called 'flashfile.xml'). I can't say about flashing JX series ROM (maybe it needs you to be on stock first or something like that) but here are the files needed to install Motorola ADB and FASTBOOT drivers and ADB & FASTBOOT tools on windows pc:
https://firmware.center/software/Android/platform-tools/win/ and https://firmware.center/software/Motorola/
---------- Post added at 10:15 PM ---------- Previous post was at 10:11 PM ----------
meraj99 said:
can you please tell me how to use the stock recovery? It just says 'No Command' everytime I boot into it
Click to expand...
Click to collapse
To get into stock recovery press VOLUME UP while pressing and holding POWER button but you can't flash custom ROM or wipe SYSTEM from there. For that purpose use Official latest TWRP recovery from their website.
JackFrost said:
You can not flash stock ROM from TWRP or other custom recovery. You need a PC with Moto Drivers and fastboot tools installed. Then you have to flash the stock rom from fastboot (generally instructions are given inside rom zip in a file called 'flashfile.xml'). I can't say about flashing JX series ROM (maybe it needs you to be on stock first or something like that) but here are the files needed to install Motorola ADB and FASTBOOT drivers and ADB & FASTBOOT tools on windows pc:
https://firmware.center/software/Android/platform-tools/win/ and https://firmware.center/software/Motorola/
---------- Post added at 10:15 PM ---------- Previous post was at 10:11 PM ----------
To get into stock recovery press VOLUME UP while pressing and holding POWER button but you can't flash custom ROM or wipe SYSTEM from there. For that purpose use Official latest TWRP recovery from their website.
Click to expand...
Click to collapse
I already have these installed! But when I run RDS and connect my phone in fastboot mode to the computer, RDS doesn't detect it in the program. I mean, the device doesn't show up in the boxes below. But when I run 'fastboot devices' in CMD I can see my device connected. And can you pleeease tell me how to flash ROMs through the stock recovery?
meraj99 said:
I already have these installed! But when I run RDS and connect my phone in fastboot mode to the computer, RDS doesn't detect it in the program. I mean, the device doesn't show up in the boxes below. But when I run 'fastboot devices' in CMD I can see my device connected. And can you pleeease tell me how to flash ROMs through the stock recovery?
Click to expand...
Click to collapse
Stock recovery don't flash roms, thats why we use customs recovery. As he mentioned just flash the stock rom, enable usb debugging and oem unlocked. Just flash the files and again flash the recovery which ever suits you and thats it.
Note : take backup first as it wipes your internal storage.
DgnrtnX said:
Stock recovery don't flash roms, thats why we use customs recovery. As he mentioned just flash the stock rom, enable usb debugging and oem unlocked. Just flash the files and again flash the recovery which ever suits you and thats it.
Note : take backup first as it wipes your internal storage.
Click to expand...
Click to collapse
well, how do I flash...? When I try to flash using TWRP it gives the error. I've tried almost all available TWRP v3+ recoveries
meraj99 said:
well, how do I flash...? When I try to flash using TWRP it gives the error. I've tried almost all available TWRP v3+ recoveries
Click to expand...
Click to collapse
Go into bootloader and then flash the file linked below from computer.
Note : usb debugging is must.
Link : https://www.google.co.in/amp/s/foru...tock-rom-npjs25-93-14-4-march-1-t3608138/amp/
DgnrtnX said:
Go into bootloader and then flash the file linked below from computer.
Note : usb debugging is must.
Link : https://www.google.co.in/amp/s/foru...tock-rom-npjs25-93-14-4-march-1-t3608138/amp/
Click to expand...
Click to collapse
yoooo!!! IT worked! Thank you so much! ^_^
DgnrtnX said:
Go into bootloader and then flash the file linked below from computer.
Note : usb debugging is must.
Link : https://www.google.co.in/amp/s/foru...tock-rom-npjs25-93-14-4-march-1-t3608138/amp/
Click to expand...
Click to collapse
erm, my SIM isn't being detected... WiFi works fine
meraj99 said:
erm, my SIM isn't being detected... WiFi works fine
Click to expand...
Click to collapse
Just flash twrp and which ever rom you like, and see if they are working or not.
DgnrtnX said:
Just flash twrp and which ever rom you like, and see if they are working or not.
Click to expand...
Click to collapse
Not working
meraj99 said:
Not working
Click to expand...
Click to collapse
I think reflashing the stock rom is the only thing to do. Read carefully whatever is written in that thread. And see if all the commands are properly exicuted.
I dont know any work around for sim as i have never had that issue. Tell me if its solved or not for just a bit of knowledge.
Edit : just for reference you are not using moto g4 play device, are you?
Standard ROM and recovery cannot be flashed by TWRP, only in fastboot mode.
DgnrtnX said:
I think reflashing the stock rom is the only thing to do. Read carefully whatever is written in that thread. And see if all the commands are properly exicuted.
I dont know any work around for sim as i have never had that issue. Tell me if its solved or not for just a bit of knowledge.
Edit : just for reference you are not using moto g4 play device, are you?
Click to expand...
Click to collapse
nah, G4+. Problem is with the baseband
meraj99 said:
nah, G4+. Problem is with the baseband
Click to expand...
Click to collapse
I flashed that firmware 2 days ago and is working fine for me, try flashing baseband then. Idk link for it search in Google for it
DgnrtnX said:
I flashed that firmware 2 days ago and is working fine for me, try flashing baseband then. Idk link for it search in Google for it
Click to expand...
Click to collapse
that's what I'm looking for. I need the Indian baseband file, do you know where i can get it

Categories

Resources