I was trying to upgrade to Oreo (7.0 to 8.x) I started at NPJS25.93-14-10 trying to go toNPJS25.93-14-18 so I could load the OTA of Oreo. Model is XT1644. It wouldn't verify. Tried Bootloader.img and gpt.bin witch didn't work and now everything I try Phone always goes to Bootloader Logs and tell me to go to Software Assistant on computer. I don't know what that is. Please help, I just need my phone to work. Don't care if I have Oreo. Bootloader is locked according to Fastboot. Thanks!
Edit: I got it fixed with the RSA tool.
Related
So, From where i start, Ahh Actually I recently updated my phone to Nougat from Marshmallow and Luckly After some days of installation my phone had some nice contact with water which somehow disturbed the ROM and it stucked into bootloops.
Situation as follows :-
*I can't Access into Rom or Recovery or Anything except past the Boot logo
*Bootloader is Locked
*On top of that OEM is locked and the permission to do so is not granted ( Developer Options > Allow OEM Unlock ) is not checked thus i can't unlock the bootloader with official code and fastboot
*Only Fastboot is Accessable and my phone is not charging at all
Now, I know i can't revert back to Marshmallow after the update wihtout unlocking the bootloader as I tried and it failed. It won't allow me to downgrade the security and validation fail.
So,
Here is the catch as per my view that i need to flash a fastboot flashable nougat zip as i can't flash the marshmallow one because when i flash gpt.bin of marshmallow i got the error but when i get the gpt.bin of nougat from update.zip it flashes easily without any error. So could someone here solve my situation please as i can't able to find a nougat fastboot zip anywhere on the internet.
Or can you suggest me some other way to make my phone work.
You will have to wait for stock nougat images,
Since nougat is not yet rolled out for everyone, i don't think Motorola is going to provide stock images in short time. Only you can is wait wait wait...!!
Post your model and maybe someone can use flashfire to create fastboot images for you.
@Damon7771 Like someone earlier had pointed out, it may take upto 1 or 2 months for firmware images to pop up. I am pretty much sure the water hasn't in anyway disturbed the ROM. It was something else. If you would like to revert back to stock marshmallow, then do as in http://forum.xda-developers.com/showpost.php?p=67031808&postcount=4 but skip gpt.bin and bootloader.img and everything should work fine. If you still got issues, take the device to the service center and they will do it for you. If it doesn't charge, I am not sure how you could even flash it since it requires device with atleast 60% battery.
Hi guys, I will appreciate if someone can help me. The things is:
I erase system.img from recovery and I backup from XT1706. After I found a site with stock XT1700 rom I downloaded last version which is the S503 I used SP Flash Tools and everything goes well. But when I tried to unlock Bootloader again adb windows said: This operation is not allowed. I tried everything but I wasn't able to unlock Bootloader again. So I downloaded the first version (S116) and surprisingly I could unlock Bootloader. But I get no notification of OTA updates it says that phone has the last version which is not true. Any ideas of what could be happening here? Thanks of hand for you help.
If you downloaded the ROMs from http://motorolastockrom.com/motorola-moto-e3-xt1700 then I suspect the problem is the ROMs have locked boot loaders. I tried installing the S503 version and the S302 version and had the same problem as you. In the end I ended up installing an XT1706 firmware and was able to unlock the bootloader, but sadly it is the same release date and adroid patch version as the XT1700 ROM I was on to begin with (S124)
Hi there, let me explain...
I f*ckup re-installing the latest Oreo stock fastboot image onto my Lineage 16 December firmware, and guess what, without paying attention I choose "Flash all and lock".
So now I am bootlooping, I cannot flash anything (twrp/rom or other) through fastboot.
I can EDL flash, but since December Pie beta brought us rollback protection, flashing the latest stock Oreo fastboot with EDL image won't fix my problem.
I guess my one and only solution is to flash a Pie Fastboot image through edl. I tried with this one (https://www.theandroidsoul.com/how-to-download-mi-a1-android-pie-update/) but unfortunately mi flash tool gives my this error: "programmer file not found", I looked into the " flash_all.bat provided" and everything look fine...
So I am seeking you help. And maybe someone over here might be able to provide me a stock pie fastboot image?
Thanks in advance, cheers
I also faced this problem bro!!!
I enterd in fastboot mode and boot into twrp recovery then flashed only linegeOs 15.1 that means 8.1 then my mobile boots into system ?
i was also searching for pie fastboot image,,, but right now its not availabe,, so can you try this.. i am also using this pie https://forum.xda-developers.com/mi-a1/development/twrp-stock-8-1-0-t3856328
@Manojyaligar @taran181
Thanks for replying, my problem is I cannot flash anything through Fastboot as my phone's bootloader is actually locked.
So the only way I have to flash anything is through EDL, and I don't think that you can boot into TWRP from EDL.
Unipo said:
@[email protected]
Thanks for replying, my problem is I cannot flash anything through Fastboot as my phone's bootloader is actually locked.
So the only way I have to flash anything is through EDL, and I don't think that you can boot into TWRP from EDL.
Click to expand...
Click to collapse
You can try flashing a nougat fastboot image. That might allow you to boot up and enable unlocking the bootloader.
Unipo said:
@Manojyaligar @taran181
Thanks for replying, my problem is I cannot flash anything through Fastboot as my phone's bootloader is actually locked.
So the only way I have to flash anything is through EDL, and I don't think that you can boot into TWRP from EDL.
Click to expand...
Click to collapse
just flash oreo 8.1.1.0 version january patch 2018... you will be able to boot ... there is a chance you will loose imei,, but then flash pie through twrp you will get imei back and phone will be normal
@taran181
Will I be able to flash this ROM despite the anti-rollback protection?
Anyway I am going to give it a shot tomorrow, thank you.
Wow that was something
So tried to follow the guide on "Guides, news and discutions". But end up loosing my imei, and nothing worked I flashed nougat January and Oreo march and november, unable to recover imei.
I had to downgrade to nougat, and write back imei on nvram.
But it's all sorted now :victory:
I had hardbricked my devices while installing an OTA update and the device was Hardbricked .
I blank flashed the device and it booted and bootloader.
Now the problem starts here.
I flashed the OEM_Lock.bat as I wanted to relock the bootloader. I'm not sure what went wrong but the flash didn't complete and stuck in middle.
The problem remains here is it shows
Fastboot Reason: Failed to initialize partition table
I am unable to flash anything now. Recovery.img fails, bootloader.img fails, twrp flashing fails.
Nothing flashes as Bootloader is locked.
I went to Motorola Service Centre. They also couldn't do anything and simply said that their software doesnt read the phone.
Is there anyone whoe can really help me out with anything left to do?
Any method to force flash recovery, even twrp?
Phone is detected as Fastboot athene_16mp S in computer. It doesnt detect as "Qualcomm HS-USB QDLoader 9008".
What firmware are you attempting to flash?
Your device looks like it's still on the blank flash provided bootloader, which means you have to flash at least the GPT and bootloader. The lack of a serial number and the generic identifier implies you have not been able to flash an actual GPT and bootloader. Also, OEM_locked is normal until you get an actual bootloader flashed over the blank flash bootloader, which usually means trying to flash a GPT and bootloader at least as new as the latest version you had on your device (regardless of downgrades).
I'd suggest downloading the latest Nougat stock ROM we have from here. Do not use any of the scripts at this time.
https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
Unzip the file, delete any old stock ROMs from your ADB folder and copy over the new stock ROM. Try to flash just the GPT and bootloader then reboot to fastboot. See if you reboot into a fastboot screen with details.
If you do, I would proceed to flash the rest of the new ROM without locking your bootloader. If your device boots then, then you can reflash with the locking commands.
Edit - also, this post probably is better suited to the Q and A section...
echo92 said:
What firmware are you attempting to flash?
https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
Unzip the file, delete any old stock ROMs from your ADB folder and copy over the new stock ROM. Try to flash just the GPT and bootloader then reboot to fastboot. See if you reboot into a fastboot screen with details.
If you do, I would proceed to flash the rest of the new ROM without locking your bootloader. If your device boots then, then you can reflash with the locking commands.
Click to expand...
Click to collapse
The files in mentioned firmware did the trick. It flashed GPT and Bootloader and showed the needed info.:highfive: After that I flashed the same firmware via fastboot commands and device has booted to the stock 7.0 - Bootloader Unlocked. How crazy was I to ignore the proper files to flash? I probably tried 100 times to flash files (wrong once for sure). Thanks alot though for providing the link and instructions. :silly:
Now one last thing, should I flash OEM_Lock file to lock the bootloader so that I can get the lastest Oreo update? I might even think fo selling the device after locking the bootloader. Need your genuine opinion on this as well.
mysteryno46 said:
The files in mentioned firmware did the trick. It flashed GPT and Bootloader and showed the needed info.:highfive: After that I flashed the same firmware via fastboot commands and device has booted to the stock 7.0 - Bootloader Unlocked. How crazy was I to ignore the proper files to flash? I probably tried 100 times to flash files (wrong once for sure). Thanks alot though for providing the link and instructions. :silly:
Now one last thing, should I flash OEM_Lock file to lock the bootloader so that I can get the lastest Oreo update? I might even think fo selling the device after locking the bootloader. Need your genuine opinion on this as well.
Click to expand...
Click to collapse
Eh, you live and learn. Besides, you've now got your device running now!
Honestly, it's up to you. Having a locked or unlocked bootloader will not affect your ability to receive OTA updates - you should still receive updates so long as your firmware matches your software channel (and since your device was XT1643, the NPJS25.93-14-18 April 2018 security update should be the correct firmware). At this moment in time, you'll have to use the NPJS25.93-14-18 firmware to re-lock your bootloader - we don't have the stock Oreo firmware at this time. Thus, if you update to stock Oreo, you will not be able to re-lock your bootloader until you can get a leak of the Oreo firmware.
If you're selling, I'd choose to re-lock the bootloader. Else, a potential buyer who is not used to flashing custom ROMs might wonder if there's any tampering with the device (the bootloader unlocked warning, to someone not used to flashing custom firmware, might scare off potential buyers).
Back to Locked Bootloader, complete stock.
echo92 said:
Eh, you live and learn. Besides, you've now got your device running now!
If you're selling, I'd choose to re-lock the bootloader. Else, a potential buyer who is not used to flashing custom ROMs might wonder if there's any tampering with the device (the bootloader unlocked warning, to someone not used to flashing custom firmware, might scare off potential buyers).
Click to expand...
Click to collapse
I am back to Locked Bootloader as feel the same as you said that anyone buying might get scared by looking the warning sign. Thanks for helping out. :highfive:
Oreo Update via OTA has already started rolling out as per the news I've been reading. I just wanted to see the oreo 8.1 before I sell the phone.
Anyways I got a new device now, Realme C1, 3|32GB as my smartphone usage has declined a lot recently and might remain similar. This device will suffice my requirements.
Thanks for the help and support. :victory:
Hi all, a few minutes ago I tried to roll back from Q beta to P, so I followed the essential's official instructions, that I found on their site, and I unlocked bootloader and critical. Then I downloaded the latest official Pie release but I could't install it via flashall.bat file, becuause I got stucked on sending 'nvdef_a'. So after this failed attempt i tried to relock the bootloader via fastboot flashing lock command but nothing happened. I then tried to do a fastboot devices and my device was connected, so I don't know why it didn't work. Should I relock critical first?
And do you know why I couldn't flash the original firmware? I was thinking of removing the '_a' commands in the flashall.bat, since i'm currently on partition _b, but i'm afraid of bricking the phone.
Thanks, Andrea.