Hi all,
is there a way to get the stock bootloader and other booting related binaries off of the phone with a locked bootloader ? I.e. are they in some OTA Updates or otherwise available ?
This is my first post and it should probably be under the development section, but I can't post there, sry.
Best regards
ff
Related
hi everybody, got this phone from my wife but I have been with Nexus for so long so I am a little bit behind the scene. Could anyone answer my questions? I don't see too many people here though.
I have unlocked the phone and installed TWRP, I think I have accidentally agreed to install the TWRP app suggested by TWRP but I don't have a system image backup, so it means I can never go back to OTA upgrade? now the boot loader say
*** software status: modified ***
seems HTC is not releasing factory image for the phone? I can't find it anywhere except this
https://forum.xda-developers.com/u-ultra/development/ruu-htc-ultra-unlocked-1-09-617-12-t3563948
I am not sure how many different hardware versions are there? and they are taking the same ROM? I am using a asia dual sim ver
at first the official TWRP doesn't boot, and I installed this one. but this TWRP ask me for a disk mount password, while I don't have any. I was busy and so I have put down the phone for 2 weeks. I installed the offical TWRP again yesterday and it worked. so...
https://forum.xda-developers.com/u-ultra/development/recovery-twrp-touch-recovery-t3558540
after installing super su the system boot up screen has a red text saying "This build is for development purposes only do not distribute outside of HTC without HTC's permission..." I think it come from supersu? is it expected?
The red text at boot is normal, I believe it's because of the unlocked boot loader.
Hey there,
There seems to be 2 hardware variants. U-1u (Dual Sim) and U-1h (single sim). not sure on interoperability of FW at present.
@mobilevil which sofware number are you running. Can be found in settings > about > sotware information, or from download mode. Asking as there can be found an official RUU for x.xx.617.x devices. If you're on US unlocked that'd be a possibility to return to full stock and receive OTA.
5m4r7ph0n36uru said:
@mobilevil which sofware number are you running. Can be found in settings > about > sotware information, or from download mode. Asking as there can be found an official RUU for x.xx.617.x devices. If you're on US unlocked that'd be a possibility to return to full stock and receive OTA.
Click to expand...
Click to collapse
Hi I am using 1.09.708.12. I did some OTA until it reported no update before rooting.
it is an unlocked dual sim ver and I bought it here in HK.
it is not very comfortable for me to have no official firmware image ready in hand.
sephstyler said:
Hey there,
There seems to be 2 hardware variants. U-1u (Dual Sim) and U-1h (single sim). not sure on interoperability of FW at present.
Click to expand...
Click to collapse
yes looking back I flashed an recovery without checking for hardware variants, I wasn't careful enough!
I thought that all would like to know that the new BLU-VIVO-8 has received Yesterday (December 30), a new Firmware update, which updates this phone to the Android Security Patch Level dated: November 5, 2017, and also brings some corrections to the Android Nougat-7 system and Google Play Store update...
As I has noticed that the new Gionee-M7-Power and also other phones, have been launched with the latest Android Nougat v7.1.1 and AMIGO 5.0, that it is the same AMIGO-UI system that the New BLU-VIVO-8 uses...
At first I thought that maybe BLU would surprise all of us with this Android Nougat v7.1.1 + AMIGO-UI 5.0 System, or perhaps with the newer Android-Oreo-8, but unfortunately they were neither, because although this update file has more than 650 MB, it was only for minor corrections and for updating the Android Security Patch to a more recent one.
We need more split ups in various BLU Models. Because this is the forum for the R1 HD.
We need some custom rom for this device
Can any one help?
Has anyone unlocked this bootloader? "Fastboot oem unlock" didn't work for me.
Barthvader said:
Has anyone unlocked this bootloader? "Fastboot oem unlock" didn't work for me.
Click to expand...
Click to collapse
Don't have that phone, but believe I saw others confirm it on a different thread. Don't remember where.
So that leaves questions on your setup.
Does "fastboot devices" confirm you are connected and have drivers installed.
Did you enable oem unlock in developer options?
mrmazak said:
Don't have that phone, but believe I saw others confirm it on a different thread. Don't remember where.
So that leaves questions on your setup.
Does "fastboot devices" confirm you are connected and have drivers installed.
Did you enable oem unlock in developer options?
Click to expand...
Click to collapse
Yes to both of those. I have multiple installs of adb and drivers, etc. So maybe there is a clash somewhere. I know that the Gionee A1 is supposed to be a clone of this phone and those steps should work. I think i am going to try XN Rootkit if trying again on a new fresh pc doesnt work. I would love to hear confirmation from an owner of this phone if there are any around on the steps neccessary to unlock the bootloader.
Barthvader said:
Yes to both of those. I have multiple installs of adb and drivers, etc. So maybe there is a clash somewhere. I know that the Gionee A1 is supposed to be a clone of this phone and those steps should work. I think i am going to try XN Rootkit if trying again on a new fresh pc doesnt work. I would love to hear confirmation from an owner of this phone if there are any around on the steps neccessary to unlock the bootloader.
Click to expand...
Click to collapse
I think maybe I am mistaken.
What i read was for ViVo XL 2
There is forum for VIVO 8L -- but it is different chip so when there device gets root it will be different.
https://forum.xda-developers.com/blu-vivo-8l
Stock Firmware [use for development, unbrick and flashing]
Download Link- http://www.mediafire.com/file/6axy0fifg0ag2pd/Blu_V0150UU_MT6755_V7.0.03.05_REPAIR_T7016.zip
i have take it from here https://romprovider.com/2018/01/install-official-firmware-blu-vivo-8/
BLU_V0150UU_V7.0.04.03_GENERIC_21-03-2018 09:25 need ROM
Please help me i need BLU_V0150UU_V7.0.04.03_GENERIC_21-03-2018 09:25BLU_V0150UU_V7.0.04.03_GENERIC_21-03-2018 09:25
This firmware please give me link
Hello XDA-mates !
I own a Moto X Play 32 GB, Dual Sim - XT1562. I had unlocked the bootloader, Flashed TWRP and rooted using SuperSu, all is well.
I no longer wish to have an unlocked bootloader and root and wanna fallback to Stock ROM with Locked bootloader.
Which as per my knowledge can be done by flashing a stock Rom.
The problem now is I am not able to find it in Motorola's portal / repository, and customer care was of no help.
'https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images#'
Coming to the questions now..
- Is it necessary to flash Entire ROM package or would just flashing the recovery and bootloader by extracting it from the compressed package work as I am already on Stock ?
- Has Motorola provided Rom's For XT-1562 at-all ? (not XT-1563, its there for XT-1563)
- How can I trust Stock ROM's available on XDA forums or Github, there is no authentication / checksum ( MD5 / SHA #) nor information about the source / origin of those files.
- How did the up-loader's get those files ?
- How can I get those ROM files ? while OTA updates download ? How ?
Thank you for going through the post
KHEMS91 said:
First u need to know that, once u relock the bootloader, u can't able to unlock it and even if u relock the bootloader, u can't rid of bootloader unlocked warning (it can be hide by flashing custom bootlogo)
My suggestion is that don't worry leave it unlocked and flash custom bootlogo that can hide bootloader unlocked warning.
After do that, If u want flash stock rom, just skip logo.bin file.
There is so many nougat roms for MXP, u should try one of them.
Flash this file from AnoopKumar's thread, this can hide the bootloader unlocked warning.
Fastboot command: (fastboot flash logo logo.bin)
Mfastboot command: (mfastboot flash logo logo.bin)
Click to expand...
Click to collapse
---------------------------
Is that right ? Once locked.... bootloader cannot be unlocked again ?
arshar01 said:
---------------------------
Is that right ? Once locked.... bootloader cannot be unlocked again ?
Click to expand...
Click to collapse
I have never tried relocking but "fastboot oem lock" seems to lock in most cases.
And also, " fastboot oem unlock <UNIQUE_KEY_FOR_YOUR_DEVICE>" unlocks it and once the key is obtained it should be reusable!
Though I would request the veterans to comment on it.
---------- Post added at 12:46 PM ---------- Previous post was at 12:37 PM ----------
arshar01 said:
Hello XDA-mates !
I own a Moto X Play 32 GB, Dual Sim - XT1562. I had unlocked the bootloader, Flashed TWRP and rooted using SuperSu, all is well.
I no longer wish to have an unlocked bootloader and root and wanna fallback to Stock ROM with Locked bootloader.
Which as per my knowledge can be done by flashing a stock Rom.
The problem now is I am not able to find it in Motorola's portal / repository, and customer care was of no help.
'https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images#'
Coming to the questions now..
- Is it necessary to flash Entire ROM package or would just flashing the recovery and bootloader by extracting it from the compressed package work as I am already on Stock ?
- Has Motorola provided Rom's For XT-1562 at-all ? (not XT-1563, its there for XT-1563)
- How can I trust Stock ROM's available on XDA forums or Github, there is no authentication / checksum ( MD5 / SHA #) nor information about the source / origin of those files.
- How did the up-loader's get those files ?
- How can I get those ROM files ? while OTA updates download ? How ?
Thank you for going through the post
Click to expand...
Click to collapse
I won't comment on your security concerns but I used this repository https://github.com/motoxplay/stock and it seems to work out for my Moto X play XT1562 Dual Sim 16 GB model. I am an active user of the XT1562 ROM on 7.1.1 and Build no. NPD26.48-24-1 for Asia and Dual sim. No apparent security issues faced!
Would be awaiting for more answers..
Thank you Smyaknti,
Currently I have installed Lineage, loving it.
But have downloaded the Roms from Github for any urgent future necessity.
It's strange was checking Asus site they provide all software stuff easily, even kernel source..
Wondering have I not searched enough ? they must have provided it some where... only then custom kernels were made right.. so Roms, Kernel's would be available somewhere, maybe in some specific region or some moto dev portal..
arshar01 said:
Thank you Smyaknti,
Currently I have installed Lineage, loving it.
But have downloaded the Roms from Github for any urgent future necessity.
It's strange was checking Asus site they provide all software stuff easily, even kernel source..
Wondering have I not searched enough ? they must have provided it some where... only then custom kernels were made right.. so Roms, Kernel's would be available somewhere, maybe in some specific region or some moto dev portal..
Click to expand...
Click to collapse
Here is your gateway to the Open Source heaven of Motorola!
https://github.com/MotorolaMobilityLLC
And the Nougat Sources for the Kernel of your phone!
https://github.com/MotorolaMobilityLLC/kernel-msm/tree/nougat-7.1.1-release-lux
Thank me later!
Hello so I tried to install a recent Rom and I get an error like this " This package supports bootloader(s) 0xA050, 0xA052; this device has bootloader 0xA048 " Any help pointing me in the right direction (tutorials/post) on this matter. BTW I did a search on the section in this site could not find anything.
Thanks in advance
A little more info would be helpful. What model, baseband, and/or stock system version were you on before trying to flash? What ROM were you trying to flash? Just based off what little you have given you need to "upgrade" but knowing specifics allows for pointing you in the right direction.
One thing to note is that there is a lot of discussion on XDA regarding bootloader issues during a flash. Most are involved with ROMs developed for the stock MM baseband vs stock nougat and their incompatibilities. There are some caveats and limitations you need to read up on before you proceed. A Google search for your error with the word XDA should net you quite a bit of what you need to know.
Sorry about that, I am out of town for the holidays. Once I get back in town I will provide that information for you guys...sorry again and Happy Holidays !!!
muelo1000 said:
Sorry about that, I am out of town for the holidays. Once I get back in town I will provide that information for you guys...sorry again and Happy Holidays !!!
Click to expand...
Click to collapse
No problems. Enjoy and Happy Holidays to everyone.
Before anyone calls me on it, I know the reply is late.
The ROM in question is likely Optimized Lineage OS, as it has a bootloader check in its install script to prevent installs on incompatible bootloaders, i.e. the Android 7.x bootloader. The OP could have found this out for himself however just by searching the development thread for the ROM he's trying to install. As to updating the bootloader itself, unless someone has extracted the bootloaders from the official ROM updates, taking an OTA is the only way to change the bootloader. Otherwise, flashing a new bootloader using fastboot using the command "fastboot flash bootloader bootloader.img", where bootloader.img is the name of the bootloader file, should work.
I'm running latest MIUI ROM global as of this moment . Will this break the OTA updates once I altered the bootloader and recovery?
no it would not.
Unlock bootloader make this device not certified
You should be able to update it .. but you won't be able to update certified apps
I see, thanks for the input guys
waiting for mine to unlock, what twrp version did you use?
this phone is not completely certified and the author of this rveviev believes that his low price is a consequence of non-affirming.
I do not know if this can move the discussion.