hi all, i am new here. so, please pardon me if i do any mistake.
here is problem,
as i am interested in technical things, my friend asked me to update his HTC one m8 into lollipop. at that time the mobile had custom rom with twrp version 7.0.2
android version: 4.4.2, sense version: 6.0, software number: Android Revolution HD 5.0 by mikel 1986, API level: 6.17
so i looked for resources and found a link. i could not add the link.
so i followed the steps and flashed the boot via fastboot with boot.img of new custom rom. the upon restart the mobile got stuck into bootloop. I could not go into recovery according to hardware button combination described there. Later once i found right combination i managed to go to recovery mode of twrp. then, i tried the remaining steps that is installing custom rom and gapps from zip file being in the recovery. Every command i gave got executed but still i could not get into system. even thought i had flashed the boot.img as an early step while starting the hboot it shows there are no images to load. So, i tried to restore from twrp recovery and i failed again. I tried to update the twrp image to run the image file of the custom rom from the twrp. but the update failed. so, i gave it to a repair shop and the repair man managed to get it working. he installed stock 5.0.1 version and in bootloader option it says software as official and relocked which showed tampered and unlocked before. BUt the problem is there are few settings that are grayed out. cant be changed. like brightness, developers option, wifi. I thought of updating os from within the set but wifi did not work.
SO, now how i can install a proper stock rom in that mobile? please help
ya you can install stock rom on your mobile..you can find your stock rom from XDA developers only......
kiranchaitanya said:
ya you can install stock rom on your mobile..you can find your stock rom from XDA developers only......
Click to expand...
Click to collapse
thank you.. i will find the rom from here. but how should i install it as i tried a process as i mention and failed. will this present rom conflict in any way? u can direct me to the point where i can find how to install the stock from the present state i m ..
naziullah said:
thank you.. i will find the rom from here. but how should i install it as i tried a process as i mention and failed. will this present rom conflict in any way? u can direct me to the point where i can find how to install the stock from the present state i m ..
Click to expand...
Click to collapse
try this once
http://forum.xda-developers.com/htc-one-m8/development/rom-stock-unlocked-developer-sense-7-t3262894
kiranchaitanya said:
try this once
http://forum.xda-developers.com/htc-one-m8/development/rom-stock-unlocked-developer-sense-7-t3262894
Click to expand...
Click to collapse
Thank you again..and sorry i had been busy and away. Could not response early. The phone was given to repair shop by my friend.
So I followed the step by step to root my phone from the FAQ sticky and everything was fine up until I tried installed the superSU zip file the link under Q7. I used the custom recovery from Q6 (which flashed and worked fine) to install the zip file for root and now when my phone turns on it gets stuck on the 'Warning Bootloader Unlocked' screen. It does not past that screen.
When I started this I was on Marshmallow 6.0
I didn't make a backup (since I didnt have anything on my phone) so it seems now that I must flash a recovery img but had a few questions on doing do. I have the US unlocked XT1540 2GB version.
I see the following thread, http://forum.xda-developers.com/2015-moto-g/development/rom-stock-motorola-rom-collection-t3296964 which has the Xt1540 2GB version but it is a lolipop build that won't OTA back to Marshmallow.
I also see a factory image on this thread, http://forum.xda-developers.com/2015-moto-g/general/index-moto-g-factory-firmware-images-t3169639 but it does not have a marshmallow XT1540 for the 2GB variant.
Is there a marshmallow for the Xt1540 2GB variant out somewhere?
Also is there a way I can just flash the .zip image in twrp recovery and not have to re unlock my bootloader and reinstall recovery all again?
If I can't flash any of the above stock images through a .zip file in twrp, is it safe if I just flash the latest nightly build from the following thread? http://forum.xda-developers.com/2015-moto-g/orig-development/rom-cyanogenmod-moto-g-3rd-gen-t3174926
It's a lolipop build but I was on Marshmallow 6.0 before getting stuck on the warning bootloader screen.
Why not flash the MM XT1540 1GB?
I would have recommended the instructions here to root MM.
Also, I wish all of the rooting instructions & FAQs would recommend a TWRP backup prior to flashing SupeSU. So many have experienced the same as you which could be easily recovered with a back up to the SD Card.
I have the same issue as you, exactly and the same problem. Hope we can find a solution soon.
EDIT:Saved the day my friend.
Use this https://www.androidfilehost.com/?fid=24052804347805576
EXACTLY as http://forum.xda-developers.com/2015-moto-g/general/guide-fastboot-flashing-factory-t3187750 says
you're going to get an error at the second flash, keep going with the others.
Worked for me, i am back in lollipop, hope you have the same luck my friend!
EDIT: I'm unable to update to marshmallow. If any one can help me with that i would be very gratefull.
EDIT: My phone was shipped to mexico, is it safe to flash the xt1542 1gb marshmallow variant on my 2gb xt1542 ?
EDIT: Welp, long night but everything seems to be working ok, flash the corresponding 1gb firmware of your model, it doesn't matter.
After today i will finally go by the golden xda rule: ALWAYS MAKE A BACKUP. ALWAYS
FINAL EDIT: i just rooted the phone, i don't know why but it seems latest version of super su doesn't get along with our phone, so flash the EXACT versions that the previous post said and you'll be fine.
1dtms said:
... root my phone... gets stuck on the 'Warning Bootloader Unlocked' screen. It does not past that screen on Marshmallow 6.0....
. I have the US unlocked XT1540 2GB version.... Is there a marshmallow for the Xt1540 2GB variant out somewhere?
Click to expand...
Click to collapse
Same version here, same issue. I tried several times, using a few different versions of SuperSU, each time re-flashing the 5.1.1 firmware to reset my soft bricked phone, but with no joy. The full 6.0 firmware image for the 2GB US XT1540 hasn't been released yet, so until then I'm running the 5.1.1 OS, rooted. I stopped the update to Marshmallow nag screen by freezing Motorola Update Services with SD Maid.
I guess we have to just keep an eye out for the 6.0 2GB images. It shouldn't be long.
So I got the same error after flashing the newest SuperSu - unfortunately. So is itthe right way now to flash the Rom from here http://forum.xda-developers.com/2015-moto-g/general/ota-moto-g3-marshmallow-ota-links-t3284308 via Twrp and then install the older SuperSu? It did not quite understand the above instructions with fastboot and so on - so =)
Thank you for your help
Moto G4 Plus US Variant XT1644
Build# MPJ24.139-64 Android 6.0.1
Stock Unmodified TWRP Backup
Stock Recovery.img & Logo.bin
Description:
I could not find ANY stock images for the US XT1644 variant so I made my own for others that have modified their system partition and wish to restore to a factory state and take the 7.0 update. Backup created on a factory reset unmodified stock build (not previously rooted/xposed/modified in any way) via fastboot booting TWRP w/system write disabled. Stock recovery and logo extracted via DD from stock rooted rom after TWRP backup was made. I pulled the recovery and logo images as these are the most commonly modified partitions (other than the system). This backup will work if you stayed on 6.0.1 and rooted/exposed/changed boot logo/etc. If you played with the 7.0 updates made for other variants, I honestly don't know if this will work for you to take the OTA as the bootloader/modem were likely modified - Test and let us know.
Directions:
-Have ADB working on your PC (google it, not getting into that here)
-Download TWRP backup here: https://mega.nz/#F!vBgU3QJB!R5J5RgZkvUiWHwmIfN6BkA
-Move backup to your proper TWRP backup location on your sd or external sd
-Restore backup via TWRP and reboot
-Download stock recovery & logo images here: https://mega.nz/#F!eBpB3Z5C!J6hoLKdfcObSLavWCsLnyw
-Power off device/plug into pc/hold volume down for 5 seconds/press and hold power & volume down until fastboot appears
-Move files to adb location (Windows) or open terminal where you downloaded the files (Linux) on your pc
-Verify connection
Code:
fastboot devices
-Restore stock recovery:
Code:
fastboot flash recovery recovery.img
-Restore stock logo (if you changed it previously to get rid of warning):
Code:
fastboot flash logo logo.bin
-Reboot and enjoy stock 6.0.1 and be able to take OTA
You are the mvp here!
I have the exact model, and it worked out great
When I was setting up as a new device, it showed some errors like SystemUI stopped working, and File Manager, theres a way to fix that?
Will it show any problems in the future? Of those same ones?
My Compilation Number is "MPJ24.139-48", should be ...64
In stock recovery says i'm at MPJ24.139-64/65
Edit* I had to flash a XT1625-XT1644 MPJ24.139-64 Firmware, then I wiped the OS with TWRP, then I restored your backup and worked like a charm, now running 6.0.1 MPJ24.139-64 with no problems :laugh::good:
panchoarcia said:
You are the mvp here!
I have the exact model, and it worked out great
When I was setting up as a new device, it showed some errors like SystemUI stopped working, and File Manager, theres a way to fix that?
Will it show any problems in the future? Of those same ones?
My Compilation Number is "MPJ24.139-48", should be ...64
In stock recovery says i'm at MPJ24.139-64/65
Click to expand...
Click to collapse
You must have been on the release prior to the one I was on when I got the phone this December. Something is not matching up. You likely have a different bootloader, and modem. When I get a chance I'll extract as many partitions that I can get access too for fastboot flashing. I'll try to do it later on this evening. It really sucks Moto won't give us full firmware for this phone.
Sent from my XT1575 using Tapatalk
annoyingduck said:
You must have been on the release prior to the one I was on when I got the phone this December. Something is not matching up. You likely have a different bootloader, and modem. When I get a chance I'll extract as many partitions that I can get access too for fastboot flashing. I'll try to do it later on this evening. It really sucks Moto won't give us full firmware for this phone.
Click to expand...
Click to collapse
I Will flash stock xt1644 firmware 64, then i restore your backup
Does XT1644 have an OTA available now? I didn't think it was pushed yet.
pupamonkey said:
Does XT1644 have an OTA available now? I didn't think it was pushed yet.
Click to expand...
Click to collapse
It's not available, we're still waiting for it, that's why we flashing stock firmware again
Thanks for doing this! It's essentially what I did to get the marshmallow update (restore stock system & boot via TWRP, then recovery & logo via fastboot).
Please let us know when you see moto/Lenovo push out the nougat update via OTA!
Sent from my Moto G4 Plus using Tapatalk
you are the champ!! i have exact same model but i am yet to update to 64 release as i just got the phone today. Just doing some research before i grease my hands! thanks man!
Sigh... Sitting here in California with an XT1644. I restored the last official stock firmware (Marshmallow Build #: MPJ24.139-64), and the OTA update simply check says my "Software is up to date!". With India variants having received Nougat back in December, I'm wondering WTF is taking so long?
I'm mostly interested in getting the updated baseband, as I'm now running @Silesh.Nair's unofficial LinageOS Nougat with few issues. I guess I'll keep waiting for the official modem update for this device in this country.
Hmmph.
bmeek said:
Sigh... Sitting here in California with an XT1644. I restored the last official stock firmware (Marshmallow Build #: MPJ24.139-64), and the OTA update simply check says my "Software is up to date!". With India variants having received Nougat back in December, I'm wondering WTF is taking so long?
I'm mostly interested in getting the updated baseband, as I'm now running @Silesh.Nair's unofficial LinageOS Nougat with few issues. I guess I'll keep waiting for the official modem update for this device in this country.
Hmmph.
Click to expand...
Click to collapse
Yeah, the US variant xt1644 still has not gotten the 7.0 update. So friggen annoying!! That's basically what I'm doing too, waiting for is the official OTA just for the radio. I'd rather have the 7.0 baseband/firmware before I start flashing any custom roms.
where to check?
i have the us variant from best buy as well , but i twicked it a lot .
How can i know when a nougat release is available? where can i check .
panchoarcia said:
You are the mvp here!
I have the exact model, and it worked out great
When I was setting up as a new device, it showed some errors like SystemUI stopped working, and File Manager, theres a way to fix that?
Will it show any problems in the future? Of those same ones?
My Compilation Number is "MPJ24.139-48", should be ...64
In stock recovery says i'm at MPJ24.139-64/65
Edit* I had to flash a XT1625-XT1644 MPJ24.139-64 Firmware, then I wiped the OS with TWRP, then I restored your backup and worked like a charm, now running 6.0.1 MPJ24.139-64 with no problems :laugh::good:
Click to expand...
Click to collapse
Where did you find file XT1625-XT1644 MPJ24.139-64 Firmware?
Did you flash it in TWRP as a zip file or fastboot?
Did you still have to fastboot stock recovery & logo images?
I'm on a unlocked bootloader/TWRP installed/rooted on MPJ24.139-48. Trying to get back to STOCK.
Hymizzle said:
Where did you find file XT1625-XT1644 MPJ24.139-64 Firmware?
Did you flash it in TWRP as a zip file or fastboot?
Did you still have to fastboot stock recovery & logo images?
I'm on a unlocked bootloader/TWRP installed/rooted on MPJ24.139-48. Trying to get back to STOCK.
Click to expand...
Click to collapse
If you flash a XT1625-XT1644 firmware and you use it "normally" on a XT1644, at some point you will have ghost touch even with low brightness, but...
For upgrading, I'll recommend flashing XT1625-XT1644, (cause there's no
...139-64 XT1644 firmware, just a firmware for both)
Flash it via fastboot, boot it up, flash TWRP recovery, wipe the full system with it, download the TWRP backup that was posted here, restore it, then via fastboot flash the stock recovery (for removing TWRP) and stock logo, then you will have MPJ24.139-64 with no problems, just waiting for nougat OTA for retus version.
Here's the link for retus firmwares: https://mirrors.lolinet.com/firmware/moto/athene/official/RETUS/
didn't work from be coming back from flashing nougat firmware, didnt expect it to just pointing it out
TheDude1998 said:
didn't work from be coming back from flashing nougat firmware, didnt expect it to just pointing it out
Click to expand...
Click to collapse
Yeah I wouldn't think so, but thanks for letting us know.
Sent from my XT1575 using Tapatalk
getting the Nougat OTA
annoyingduck said:
Yeah, the US variant xt1644 still has not gotten the 7.0 update. So friggen annoying!! That's basically what I'm doing too, waiting for is the official OTA just for the radio. I'd rather have the 7.0 baseband/firmware before I start flashing any custom roms.
Click to expand...
Click to collapse
So now that an update to Nougat is getting pushed to xt1644 devices in the 'States, I'm having some challenges successfully applying the update with my unlocked bootloader.
I believe I've got the correct system, boot, logo & recovery images; I'm able to boot up, download the OTA, and initiate the update. Unfortunately, the update process eventually displays the green android character on its back with the red error symbol.
I was hoping to get the update, with the proper local and updated baseband, without going all the way back to stock with the locked bootloader, etc.
I know i had taken the October Marshmallow security update OTA with an unlocked bootloader... Can anyone share the minimum requirements for the current Nougat OTA?
Edit: I went ahead and returned my US xt1644 to the latest stock Marshmallow firmware (MPJ24.139-64) via fastboot and the script commands listed in this post by @yeshwanthvshenoy. Though I left the bootloader unlocked, the phone booted up and went through the OTA Nougat update process without any issue.
I stayed on the new/updated stock Nougat ROM just long enough to confirm that it's working well I'm on my network (Verizon LTE/CDMA), then I flashed @Shreps' build of TWRP 3.1 and backed up every partition before restoring @Silesh.Nair's LineageOS-based InvictaOS. At last I have an up-to-date baseband (M8952_70030.25.03.62R) and appear to have no issues on custom Nougat ROMs - fingerprint registration works fine, for example.
Sent from my Moto G4 Plus using Tapatalk
bmeek said:
So now that an update to Nougat is getting pushed to xt1644 devices in the 'States, I'm having some challenges successfully applying the update with my unlocked bootloader.
I believe I've got the correct system, boot, logo & recovery images; I'm able to boot up, download the OTA, and initiate the update. Unfortunately, the update process eventually displays the green android character on its back with the red error symbol.
I was hoping to get the update, with the proper local and updated baseband, without going all the way back to stock with the locked bootloader, etc.
I know i had taken the October Marshmallow security update OTA with an unlocked bootloader... Can anyone share the minimum requirements for the current Nougat OTA?
Edit: I went ahead and returned my US xt1644 to the latest stock Marshmallow firmware (MPJ24.139-64) via fastboot and the script commands listed in this post by @yeshwanthvshenoy. Though I left the bootloader unlocked, the phone booted up and went through the OTA Nougat update process without any issue.
I stayed on the new/updated stock Nougat ROM just long enough to confirm that it's working well I'm on my network (Verizon LTE/CDMA), then I flashed @Shreps' build of TWRP 3.1 and backed up every partition before restoring @Silesh.Nair's LineageOS-based InvictaOS. At last I have an up-to-date baseband (M8952_70030.25.03.62R) and appear to have no issues on custom Nougat ROMs - fingerprint registration works fine, for example.
Click to expand...
Click to collapse
If i fash stock mm via adb will my bootloader still unlock? and if upgrade via ota, bootloader still unlock too?
dedik46 said:
If i fash stock mm via adb will my bootloader still unlock? and if upgrade via ota, bootloader still unlock too?
Click to expand...
Click to collapse
Yes your bootloader will still be unlocked unless you specifically enter the oem lock command. Read the tutorials, they all explain how to keep your bootloader unlocked.
Sent from my XT1575 using Tapatalk
bmeek said:
So now that an update to Nougat is getting pushed to xt1644 devices in the 'States, I'm having some challenges successfully applying the update with my unlocked bootloader.
I believe I've got the correct system, boot, logo & recovery images; I'm able to boot up, download the OTA, and initiate the update. Unfortunately, the update process eventually displays the green android character on its back with the red error symbol.
I was hoping to get the update, with the proper local and updated baseband, without going all the way back to stock with the locked bootloader, etc.
I know i had taken the October Marshmallow security update OTA with an unlocked bootloader... Can anyone share the minimum requirements for the current Nougat OTA?
Edit: I went ahead and returned my US xt1644 to the latest stock Marshmallow firmware (MPJ24.139-64) via fastboot and the script commands listed in this post by @yeshwanthvshenoy. Though I left the bootloader unlocked, the phone booted up and went through the OTA Nougat update process without any issue.
I stayed on the new/updated stock Nougat ROM just long enough to confirm that it's working well I'm on my network (Verizon LTE/CDMA), then I flashed @Shreps' build of TWRP 3.1 and backed up every partition before restoring @Silesh.Nair's LineageOS-based InvictaOS. At last I have an up-to-date baseband (M8952_70030.25.03.62R) and appear to have no issues on custom Nougat ROMs - fingerprint registration works fine, for example.
Sent from my Moto G4 Plus using Tapatalk
Click to expand...
Click to collapse
I had the exact same issue, and your solution worked perfectly. It's unfortunate how difficult Motorola has made it to find the stock firmware for the XT1644.
vishnureddy17 said:
I had the exact same issue, and your solution worked perfectly. It's unfortunate how difficult Motorola has made it to find the stock firmware for the XT1644.
Click to expand...
Click to collapse
Which of these 5 download? .
Hi, I'm having a lot of trouble trying to install a custom recovery. I had it working a couple months back but wanted to go with official again for dumb reasons and now i want to go back but it won't let me flash TWRP, i can't find a TWRP specifically for this version either. It's Android 10 with March security patch.
I hope someone can help me.
Thanks.
Please only create one thread per topic. I've removed the duplicate thread you started on this topic.
As far as your issue goes, I don't actually know much about Samsung specifics, but I believe that particular message means you haven't unlocked your bootloader. You'll need to do that before you can flash custom stuff.
Didgeridoohan said:
Please only create one thread per topic. I've removed the duplicate thread you started on this topic.
As far as your issue goes, I don't actually know much about Samsung specifics, but I believe that particular message means you haven't unlocked your bootloader. You'll need to do that before you can flash custom stuff.
Click to expand...
Click to collapse
actually Im also having the same problem even though i have unlocked my bootloader.. I had previously installed twrp and was trying custom os until one os (evolution x) for some bricked my phone and i had to flash the stock firmware and after that when i try to re-flash twrp through odin it is saying officail binary can be flashed.
Parthiv Shaji said:
actually Im also having the same problem even though i have unlocked my bootloader.. I had previously installed twrp and was trying custom os until one os (evolution x) for some bricked my phone and i had to flash the stock firmware and after that when i try to re-flash twrp through odin it is saying officail binary can be flashed.
Click to expand...
Click to collapse
Like I said, I'm not 100% on Samsung shenannigans, but have you checked to verify that you didn't lock the bootloader as a part of flashing the stock firmware?
OEM unlock toggle in Developer's Options
Hi ¡...
1. You have to reinstall via odin the latest version 9 (AP, BL...etc)
2. On reboot do the entire TWPR flashing process for android 9
The current problem is that there is no TWPR for android 10.
Cheers
Yesterday, I tried to unlock using lineage16, using twrp3.31 version. . In the first system version of emui9, flashing lineage. Failure, error7 is prompted. . I carried out several system updates, (the latest emui9) installed twrp, flashing lineage16. Still failed.
Finally, I carried out the wrong operation, recovery cleared the data, and now rec and erac can not enter I think I should go to the sale to solve this problem.
My device is a Chinese version, the model is al20 (as far as I know, the hardware is no different from the US version, except for the baseband)
This is my system version, and various parameters. . I hope you can get your help I have unlocked the device protection lock. The only problem is error7. This phone does not have the rom I like in China. . . . I have checked some information, it may be that the rom and the phone model are wrong, or the underlying firmware is wrong (I used the official recovery tool to restore to emui9) Now, I can only guess. . . . The problem with rom, may not be considered by the developers, and it is not known that the Chinese version can be unlocked.
My friend told me to delete the rom model verification, I do n’t know if it is useful (after I am modified, use twrp to flash, error7)
He asked me to delete the first four columns
Don’t know if u r still using this device or not, the official 3.3.1 twrp will get error of unable to mount partitions on too new firmware version such as emui 9.1.337, downgradeing the firmware version may help, and lineage 16 will not work on Chinese's specific device such as al00 and al20, it would only work for some US specific model, in this case you can use other rom like aosip, i just flashed this rom and it is booting normally, but my al20 was sucked in installing magisk, after flashing the patched recovery the device will not boot or boot into the system without magisk......too many time were wasted on this device, and i don't want to play with it anymore..