Develop Bugs

[Info] P6 Bootloader is UNLOCKED by default

Just tried it, fastboot tells that P6 bootloader is unlocked, so we can flash everything in our P6
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Maybe, this is the reason why Huawei don't tell anything about our bootloade
Already reported that flash can be done in htcmania, with the method from 4pda.ru :cyclops:
How to check if your bootloader is unlocked:
-Open a cmd console
-Type: adb reboot-bootloader
-Type: fastboot oem get-bootinfo
-Done

S34Qu4K3 said:
Just tried it, fastboot tells that P6 bootloader is unlocked, so we can flash everything in our P6
Maybe, this is the reason why Huawei don't tell anything about our bootloade
Already reported that flash can be done in htcmania, with the method from 4pda.ru :cyclops:
How to check if your bootloader is unlocked:
-Open a cmd console
-Type: adb reboot-bootloader
-Type: fastboot oem get-bootinfo
-Done
Click to expand...
Click to collapse
Code:
:~$ fastboot oem get-bootinfo
< waiting for device >
nothing more...
---------- Post added at 05:15 PM ---------- Previous post was at 05:13 PM ----------
S34Qu4K3 said:
Just tried it, fastboot tells that P6 bootloader is unlocked, so we can flash everything in our P6
Maybe, this is the reason why Huawei don't tell anything about our bootloade
Already reported that flash can be done in htcmania, with the method from 4pda.ru :cyclops:
How to check if your bootloader is unlocked:
-Open a cmd console
-Type: adb reboot-bootloader
-Type: fastboot oem get-bootinfo
-Done
Click to expand...
Click to collapse
Code:
:~$ fastboot oem get-bootinfo
< waiting for device >
nothing more...
edit: P6-U06, Germany

TheProd said:
Code:
:~$ fastboot oem get-bootinfo
< waiting for device >
nothing more...
---------- Post added at 05:15 PM ---------- Previous post was at 05:13 PM ----------
Code:
:~$ fastboot oem get-bootinfo
< waiting for device >
nothing more...
edit: P6-U06, Germany
Click to expand...
Click to collapse
You did adb reboot-bootloader?? Make sure that phone is in MTP mode and you have the drivers

S34Qu4K3 said:
You did adb reboot-bootloader?? Make sure that phone is in MTP mode and you have the drivers
Click to expand...
Click to collapse
I did this at my linux notebook!
On Windows fastboot cmds are working (hisuite driver)... and bootloader is unlocked! :cyclops:

TheProd said:
I did this at my linux notebook!
On Windows fastboot cmds are working (hisuite driver)... and bootloader is unlocked! :cyclops:
Click to expand...
Click to collapse
Great news! We can flash now everything on our phone *0*

It has already been said that the bl shows up as unlocked. However noone has managed to flash a new kernel, and that is why they consider it to be encrypted.

zordo said:
It has already been said that the bl shows up as unlocked. However noone has managed to flash a new kernel, and that is why they consider it to be encrypted.
Click to expand...
Click to collapse
An user in htcmania flashed de b115 kernel in a b107 rom sucessfully, and somebody in Huawei official twitter said that some things can be flashed
Sent from my HUAWEI P6-U06 using xda app-developers app

Hello!
My device seems to be unlocked....but I can not managed to flash stock kernel !
The same kernel (stock) was succesfully flased by this command :
# dd if=/sdcard/boot.img of=/dev/block/......

If you want to do it, do:
-adb reboot-bootloader
-fastboot flash boot boot.img
-fastboot reboot
It should work, and remember, do it at your own risk

S34Qu4K3 said:
If you want to do it, do:
-adb reboot-bootloader
-fastboot flash boot boot.img
-fastboot reboot
It should work, and remember, do it at your own risk
Click to expand...
Click to collapse
Hi!
As I told you, on my device I can not flash stock kernel !
Please take a look here and follow all my posts to understand better !
Thanks :good:

surdu_petru said:
Hi!
As I told you, on my device I can not flash stock kernel !
Please take a look here and follow all my posts to understand better !
Thanks :good:
Click to expand...
Click to collapse
I read somewhere that you need to flash this to get it work:
fastboot fastboot.img
fastboot flash efi efi.img
fastboot flash modemimage modemimage.img
fastboot flash boot boot.img
Try it if you want

Reyncla in htcmania make this script. Work
https://mega.co.nz/#!4Y5hyILD!GzQny36sJ-Ec0wErtk4BAxD398pJFaEhHE8Z67zp0u4

JoySu said:
Reyncla in htcmania make this script. Work
https://mega.co.nz/#!4Y5hyILD!GzQny36sJ-Ec0wErtk4BAxD398pJFaEhHE8Z67zp0u4
Click to expand...
Click to collapse
Hi!
Do you tested with this script ?
Will be ok if someone can test it....I'm on holliday
Begining September I can try to make an custom cwm/twrp and also some custom roms....:good:
---------- Post added at 05:54 PM ---------- Previous post was at 05:52 PM ----------
S34Qu4K3 said:
I read somewhere that you need to flash this to get it work:
fastboot fastboot.img
fastboot flash efi efi.img
fastboot flash modemimage modemimage.img
fastboot flash boot boot.img
Try it if you want
Click to expand...
Click to collapse
Hi!
Already tried...and not work on my unlocked bl device...

Scrip works
I'm setting up a linux vm to try to port CWM I hope to make some advance in a few days
Sent from my HUAWEI P6-U06 using xda app-developers app

S34Qu4K3 said:
Scrip works
I'm setting up a linux vm to try to port CWM I hope to make some advance in a few days
Sent from my HUAWEI P6-U06 using xda app-developers app
Click to expand...
Click to collapse
Hi!
...would be nice
I can help you....but later...
Also you can send me a PM....

I'll do it, i want to port it well i don't want any brick
Sent from my HUAWEI P6-U06 using xda app-developers app

surdu_petru said:
Hi!
Do you tested with this script ?
Will be ok if someone can test it....I'm on holliday
Begining September I can try to make an custom cwm/twrp and also some custom roms....:good:
This script created by reyncla of HTCMania works in windows for p6. Only makes it easy to check if the device is locked or unlocked. The unlocked bootloader test said.
Click to expand...
Click to collapse

All this script does is automate the exact process that is outlined on the OP.
Code:
:ACTUALIZA
CLS
color 3f
ECHO. =================================================
echo. Buscando telefono...
echo.
[B]adb reboot-bootloader
fastboot oem get-bootinfo[/B]
echo.
[B]fastboot reboot[/B]
echo.
echo Oprima cualquier tecla para salir...
echo.
ECHO. =================================================
ping 127.0.0.1 -n 5 >NUL
pause >NUL 2>NUL
exit
It doesn't do anything more then tell the user the bootloader information we already gained from the manual procedure.
Edit: Ahh didn't see you'd already commented on this JoySu, my bad. Oh well double clarification.
Best Regards,
s89

fastboot boot boot.img can't be done... So i think, bootloader locked :/

Someone in our german forum told me, that she had a huawei before and there was a similar problem like here.
There was a way to flash the boot img, just set some settings before:
* # * # 2846579 # * # *
Project menu --- set back-----USB Port Configuration-----production mode -> (reboot)
* # * # 2846579 # * # *
Project menu-------LOG setting-------LOG open------LOG level-----set "VERBOSE"
adb reboot bootloader
Click to expand...
Click to collapse
I dont know if it works with our P6.

Htc m9 corruted bootloader blue screen,Please HELP

When I enter in RUU mode (download mode) blue screen comes.
Before this I locked my bootloader to flash ota firmware,but it stuck on htc screen, then I relocked my bootloader but it gives me error.
Please help what to do?

are you soff?

blue screen error
plz some one help..
htc m9 asia tw
s-on
firmware update to 5.1 sudden mobile reset and now when it on after gives blue blank screen just....
just bootloader screen come while pressing vol + and vol - and power button. bt no recovery no download mode no RUU mode while going to download mode blue screen error plz someone help. what to do.

You can flash the stock files in the bootloader screen. Fastboot commands work. Just extract the ruu and flash the partitions individually.

philicibine said:
You can flash the stock files in the bootloader screen. Fastboot commands work. Just extract the ruu and flash the partitions individually.
Click to expand...
Click to collapse
fastboot command in bootloader screen gives error FAILED (remote: cannot flash this partition in s-on state)
please someone help to solve this problem.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This screen comes every time and reset htc logo and then same blue screen

Maybe try fastboot boot recovery.img and see if that works??

philicibine said:
Maybe try fastboot boot recovery.img and see if that works??
Click to expand...
Click to collapse
FAILED (remote: Not allow when s-on)

mnhs1010 said:
When I enter in RUU mode (download mode) blue screen comes.
Before this I locked my bootloader to flash ota firmware,but it stuck on htc screen, then I relocked my bootloader but it gives me error.
Please help what to do?
Click to expand...
Click to collapse
Is your error solved or are you still stuck with the blue screen as I am also the effected

LineArc said:
Is your error solved or are you still stuck with the blue screen as I am also the effected
Click to expand...
Click to collapse
Still same problem dear blue screen...

mnhs1010 said:
Still same problem dear blue screen...
Click to expand...
Click to collapse
Maybe u should take a look here their potential is to recover ur device with some fund ....better than going to HTC and screwing up alot of money

sa3d12 said:
Maybe u should take a look here their potential is to recover ur device with some fund ....better than going to HTC and screwing up alot of money
Click to expand...
Click to collapse
did your problem solved >>>>>

mnhs1010 said:
did your problem solved >>>>>
Click to expand...
Click to collapse
U mean you solved your problem or you are asking me? ..
Anyway i dont have problems with my device

hello my English is bad but i have solved this problem.
you need Minimal ADB and Fastboot
you need Firmware of your phone. (try with 3.35)
unzip your firmware zip in the minimal ADB and fastboot folder
open fastboot cmd
start your smartphone in bootloader
copy all files .img with fastboot
fastboot flash aboot aboot_signed.img
fastboot flash boot boot.img
fastboot flash adsp adsp.img
fastboot flash hosd hosd_signed.img
fastboot flash hyp hyp-8994-1.img
fastboot flash pg2fs pg2fs_ship_signkey.img
fastboot flash pmic pmic-8994-1.img
fastboot flash radio radio.img
fastboot flash recovery recovery.img
fastboot flash rpm rpm-8994-1.img
fastboot flash sbl1 sbl1-8994-1.img
fastboot flash sdi sdi.img
fastboot flash sensor_hub sensor_hub.img
fastboot flash tz tz-8994-1.img
fastboot reboot
Click to expand...
Click to collapse
done your blue screen is off and all acces to your download mode, Ruu.
need to reinstall recovery, and firmware again

I think you only need to flash the hosd

VashSV said:
hello my English is bad but i have solved this problem.
you need Minimal ADB and Fastboot
you need Firmware of your phone. (try with 3.35)
unzip your firmware zip in the minimal ADB and fastboot folder
open fastboot cmd
start your smartphone in bootloader
copy all files .img with fastboot
done your blue screen is off and all acces to your download mode, Ruu.
need to reinstall recovery, and firmware again
Click to expand...
Click to collapse
Thanks a lot! You have been avoided a heart attack hehe!

You my friend are a star... I thought my HTC M9 was a brick for sure.
Just to add people, remember do not try and copy through ADB installer (As I did to begin with)... It will not detect your phone... Use the Fastboot application within CMD.
VashSV said:
hello my English is bad but i have solved this problem.
you need Minimal ADB and Fastboot
you need Firmware of your phone. (try with 3.35)
unzip your firmware zip in the minimal ADB and fastboot folder
open fastboot cmd
start your smartphone in bootloader
copy all files .img with fastboot
done your blue screen is off and all acces to your download mode, Ruu.
need to reinstall recovery, and firmware again
Click to expand...
Click to collapse

VashSV said:
hello my English is bad but i have solved this problem.
you need Minimal ADB and Fastboot
you need Firmware of your phone. (try with 3.35)
unzip your firmware zip in the minimal ADB and fastboot folder
open fastboot cmd
start your smartphone in bootloader
copy all files .img with fastboot
done your blue screen is off and all acces to your download mode, Ruu.
need to reinstall recovery, and firmware again
Click to expand...
Click to collapse
does anyone have for m9 verizon ?

@VashSV, I already pressed thanks button but want to write and say thanks to you. You save my phone. Happy new year 2017

Many many many thanks to you!!! I what in this blue screen loop, thanks to your commande list I managed to write .img by .img, you are the boss.

Exact same problem
philicibine said:
You can flash the stock files in the bootloader screen. Fastboot commands work. Just extract the ruu and flash the partitions individually.
Click to expand...
Click to collapse
Hello, a bit late but I have the exact same problem with my HTC one M9, can you please help me? I am s-off, unlocked and my phone is T-MOB010 with N7 corrupted firmware :/ pleaseeee

[Guide] Persist error fix in YUREKA / PLUS [21-Apr-2016]

PERISIST ERROR IN TWRP WHILE FLASHING ANY ZIP.....? THEN HERE IS THE GUIDE
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I am not responsible for anything that may happen to your phone as a result of installing custom roms and/or kernels. you do so at your own risk and take the responsibility upon yourself.
What is the persist partition?
Persist is partition mounted at /persist. It has ext4 file system. DRM releated files, sensor reg file (sns.reg), wifi and bluetooth mac addresses are stored there.
If you experience the following issues:
1. You get "e: cannot mount /persist" in recovery
2. Can't access to internal storage.
3. Boot loop on Lollipop 5.0 and above
4. IMEI number is lost even after formating cache and fastboot flash cache.img
5. No signal even after formating cache and fastboot flash cache.img
Then your persist partition have to be fixed​
Follow instructions carefully to solve this issue
NOTE : UNLOCK your device bootloader first before doing this
1. Download this " persist file & ADB+&+Fastboot of yureka " provided by @Annabathina
2. extract them in PC
3. open ADB+&+Fastboot of yureka
4. place presist.img file which you have extracted in ADB+&+Fastboot folder
5. Hold shift key and right click on mouse and select Open command window here
6. Connect your device to pc..... and make sure that drivers are installed properly..... ( VERY VERY IMPORTANT )
a. Type : adb devices
If your device is connected you will get it in connected devices list
b. Type : adb reboot-bootloader
Your phone will restart into bootloader.
c. Type : fastboot -i 0x1ebf flash persist persist.img
7. Disconnect your device from PC and REBOOT​
ADB+&+Fastboot : link
persist : link
Useful links
ADB for pc : link
YU usb drivers : link
PdaNet drivers : link
@Annabathina............................for Guide
Ricks ............... for Presist file
YU YUREKA
YU YUREKA PLUS​
XDA:DevDB Information
[Guide] Persist error fix in YUREKA / PLUS [21-Apr-2016], Tool/Utility for the YU Yureka
Contributors
Annabathina
Version Information
Status: Stable
Stable Release Date: 2016-04-21
Created 2016-04-21
Last Updated 2016-04-23

Reserved

Reserved

I dont get a multirom function in the advanced settings menu. Is it because im using twrp 3.0.... Or is it bcoz of persist partition ?
Sent from my AO5510 using XDA-Developers mobile app

After booting into fastboot mode .. i put the commands and then it just says "waiting for device"..

Bazilbycom said:
After booting into fastboot mode .. i put the commands and then it just says "waiting for device"..
Click to expand...
Click to collapse
Have you solved it?

saurav007 said:
Have you solved it?
Click to expand...
Click to collapse
Yes! .. All you have to do is install proper drivers for your device .
Use PDAnet and Google Usb Drivers

Hi,
For me the message is : is not possible to erase this partition
Thanks a lot for your help

still same error.....what to do now..??

Bazilbycom said:
Yes! .. All you have to do is install proper drivers for your device .
Use PDAnet and Google Usb Drivers
Click to expand...
Click to collapse
Earlier i was getting error even after installing all the drivers, all i needed was to update PDAnet on phone as well & it does everything.
Thank you it worked well!

still stucking
i was suffering of problem error persist but using this method it solved the error is gone but not still my device stuck on boot i tried many custom roms stock rom formats and all but still it stuck after 2 of android logo. in twrp recovery in mount option the system, persist, firmware are uncheck .i think it means they are not mount right??? i click many time to check and reboot but still logo stuck problem please give me solution!!!!!!!
Thank You

Can I flash this zip by twrp
Sent from my YU5510 using Tapatalk

vijaysingh1996 said:
Can I flash this zip by twrp
Sent from my YU5510 using Tapatalk
Click to expand...
Click to collapse
This isn't TWRP flashable zip. You have to flash via fastboot (see OP) after extracting the img from downloaded zip file.

Failing on my Pantech Sky Vega Iron 2 IM-A910S (codename: ef63) and bootloader unlocked.
In Fedora Linux the command continues to display "waiting for device" message even though the device is detected by "fastboot devices" command, although its serial number is not displayed and ???????? is display in that place.
While in Windows 7 (64-bit), the following error message is displayed after execution of the command "fastboot -i 0x1ebf flash persist persist.img":
target reported max download size of 1610612736 bytes
sending 'persist' (4324 KB)...
OKAY [ 0.165s]
writing 'persist'...
FAILED (remote: It is not surpport in user build.)
finished. total time: 0.186s
Any one please help...

In my device it showing can't load persist
After typing last line

shekarsahani said:
In my device it showing can't load persist
After typing last line
Click to expand...
Click to collapse
Can you post CMD screenshot?
Make sure the file name is same as in CMD.

Unfortunately I can't is send cmd screenshot it is not uploading..
When I type fastboot -i 0x1ebf flash persist persist.img then it shows error cannot load 'persist.img'

How to re-lock Bootloader of all Potter version

Hi guys, finally I succed in relock my XT1685 Bootloader on RETEU, so I will guide you to relock your bootloader.
DISCLAIMER:
Code:
I am not responsible for bricked devices, dead SD cards,
thermonuclear war, or you getting fired because the alarm app failed.
YOU are choosing to make these modifications,
and if you point the finger at me for messing up your device, I will laugh at you.
and I am also not responsible for anything happens as a result of flashing these files
What you need :
1- Motorola drivers :
64-bit
32-bit
2- Minimal ADB and Fastboot:
Minimal ADB and Fastboot
3- Stock Fastboot flashable official firmware.
Here is the donwload of NPNS25.133-37-11 it should be perfect for lock BL for all RETEU users:
Mirror 1 (MEGA)
Mirror 2 (GoogleDrive)
ATTENTION:
You will need the appropriate version of the firmware according to your device version
You need the same or later version of firmware that you have when you unlock your BL
Example: If when you unlock your bl you was on NPNS25.137-33-11 you need the same (or later) complete firmware because you can't downgrade.
Now let's start with the guide.
1- Install Minimal ADB and Fastboot.
2- Extract stock firmware to any folder.
3- Now copy all the stuff that is in Minimal ADB and Fastboot folder in the folder where you extract the firmware.
4- Connect your device in fastboot mode (power off the device and while you press VOL down button insert the USB cable).
5- Open ADB and Fastboot terminal (press SHIFT+right click on the folder where you extract the firmware and select "open command window here").
6- Now type in Fastboot terminal "fastboot devices" (without commas) to be sure that your device is recognized.
7- Type these command one by one on terminal
Code:
fastboot oem lock
fastboot oem lock
fastboot flash oem oem.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 boot boot.img
fastboot oem lock
Now your device will restart and your BL will be locked.
Now for be sure reflash all the complete firmware repeat the point from 5 to 7 but insert this code now
Code:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.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 modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
fastboot reboot
Now you will be able to receive the OTA update with your locked BL.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Thanks to @Nirbhay2

aSaro12 said:
You will need the appropriate version of the firmware according to your device version
You need the same or later version of firmware that you have when you unlock your BL
Click to expand...
Click to collapse
Thank you!
I like to comment that these two topics are the key points to do it right. :highfive:

manos78 said:
Thank you!
I like to comment that these two topics are the key points to do it right. :highfive:
Click to expand...
Click to collapse
Yes, this is a little but important thing. :good::good:

Duplicate Thread
Read before posting
There is already thread for relocking bootloader : https://forum.xda-developers.com/g5-plus/how-to/lock-bootloader-moto-g5-plus-indian-t3638835

siddhesh9146 said:
Duplicate Thread
Read before posting
There is already thread for relocking bootloader : https://forum.xda-developers.com/g5-plus/how-to/lock-bootloader-moto-g5-plus-indian-t3638835
Click to expand...
Click to collapse
That thread is specific for Indian Variant.
And if you read carrefully I've mentioned the writer of the thread that you've posted.

Thank you!!
That worked perfectly on XT1685. Much appreciated.

Thanks
It's works. I'm successfully re-locked my bootloader. But i have a question.
Can i get OTA updates if bootloader says me "Software status: Modified"?

SeRi0uS007 said:
It's works. I'm successfully re-locked my bootloader. But i have a question.
Can i get OTA updates if bootloader says me "Software status: Modified"?
Click to expand...
Click to collapse
My Software status is also Modified and I never got ota's I always had to manually clean flash stock images. If someone found a way I would love to know how to get ota's on stock rom.

Thank you. my phone can get OTG now.

I tried yesterday on a XT1685 with the RETAIL firmware... and I broke something because my g5 plus cannot connect to GSM anymore (PIN asked but no LTE and no call possible). Bootloader is locked so I try to send back my phone to amazon for repair (exchange)... Sometimes **** happens !

pfufux said:
I tried yesterday on a XT1685 with the RETAIL firmware... and I broke something because my g5 plus cannot connect to GSM anymore (PIN asked but no LTE and no call possible). Bootloader is locked so I try to send back my phone to amazon for repair (exchange)... Sometimes **** happens !
Click to expand...
Click to collapse
same as here... revert back to stock but no signal..
i had xt1685 RETAIL too.. what did you flashed?
what happen with Amazon?

tufoz said:
same as here... revert back to stock but no signal..
i had xt1685 RETAIL too.. what did you flashed?
what happen with Amazon?
Click to expand...
Click to collapse
I don't remember what I flashed... but I think it's what I found in this post (NPNS25.133-37-11). I sent my phone to Amazon (fr) and it should be back today; I think I won't try again to flash Lineage or other because it seems to cause some troubles with IMEI when returning to stock, as I saw here and here.

pfufux said:
I don't remember what I flashed... but I think it's what I found in this post (NPNS25.133-37-11). I sent my phone to Amazon (fr) and it should be back today; I think I won't try again to flash Lineage or other because it seems to cause some troubles with IMEI when returning to stock, as I saw here and here.
Click to expand...
Click to collapse
My phone is back with a new motherboard... and so, a new IMEI. More details :
BASEBAND : M8953_37.46.07.47R POTTER_EMEADSDS_CUST
BUILD : NPN25.137-93

pfufux said:
My phone is back with a new motherboard... and so, a new IMEI. More details :
BASEBAND : M8953_37.46.07.47R POTTER_EMEADSDS_CUST
BUILD : NPN25.137-93
Click to expand...
Click to collapse
Everyone else is getting the 137-92 update, why does yours say 137-93?

I don't know but the update came from OTA.

pfufux said:
I don't know but the update came from OTA.
Click to expand...
Click to collapse
you confirm me that amazon replaced your phone? i think i will do the same thing

Ok .. i tried the procedure again.. I used 137.33.11 cid 50 NPNS but i got this error messages..
when flashing system: invalid signed image
when flashing bootloader "security downgrade version"...
any hint?

tufoz said:
you confirm me that amazon replaced your phone? i think i will do the same thing
Click to expand...
Click to collapse
I confirm Amazon changed the motherboard of my phone. I have a new IMEI number.

I can't re lock bootloader
Hi, i am trying to install stock rom and relock bootloader because after installing custom rom, i am not getting network in my device. but now after installing stock rom(see below image for version), i cant relock my bootloader. it gives me error like security downgrade issue.

Thanks a lot
:good::good::good::good:
the indian variant relock is not correctly explained
You Have Explained It
Listen all
You will need the firmware which you were using before unlocking your bootloader then only you can relock it again
Now i can give it for warranty Thanks a Lot

[ROM][10][UNOFFICIAL] OmniROM

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Download :
GApps : https://dl.omnirom.org/tmp/def/
microG : https://dl.omnirom.org/def/
Kernel source
Device tree source
MAJOR BUGS:
you tell me
FLASHING
Android 10 shipped devices have fastboot like we know it and its pretty much useless. and they have the new fastbootd (google it).
Get into fastbootd.
option a) from old fastboot, type: fastboot reboot fastboot (funny eh ?) another google miracle to not name it fastbootd.
option b) if you have a running os with adb: adb reboot fastboot
You should see a recovery like screen with a red "fastbood" message
Extract payload.bin using payload dumper (google it for tutorials)
fastboot -w (warning : this will wipe all your data)
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash system system.img
fastboot flash product product.img
fastboot flash vbmeta vbmeta.img
fastboot reboot
UPDATE
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash system system.img
fastboot flash product product.img
fastboot flash vbmeta vbmeta.img
fastboot reboot
Telegram group for One Hyper : https://t.me/MotoOneHyper
XDA:DevDB Information
OmniROM, ROM for the Motorola One Hyper
Contributors
vache
Source Code: https://github.com/omnirom/
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
ROM Firmware Required: Unlocked bootloader
Based On: AOSP
Version Information
Status: Beta
Beta Release Date: 2020-02-02
Created 2020-02-02
Last Updated 2020-08-15

I unlocked my bootloader of my Motorola One Hyper and tried to install this rom.
The flashing is ok untill the flashing of the system. When I run :
fastboot flash system system.img
Resizing 'system_b' FAILED (remote: '')
fastboot: error: Command failed
I get an error as response. Any clue ?

orimigato said:
I unlocked my bootloader of my Motorola One Hyper and tried to install this rom.
The flashing is ok untill the flashing of the system. When I run :
fastboot flash system system.img
Resizing 'system_b' FAILED (remote: '')
fastboot: error: Command failed
I get an error as response. Any clue ?
Click to expand...
Click to collapse
I don't get why it's trying to flash on slot b, did you get an OTA since you got the phone ?

vache said:
I don't get why it's trying to flash on slot b, did you get an OTA since you got the phone ?
Click to expand...
Click to collapse
Yes I got an OTA when I got my phone today.

orimigato said:
Yes I got an OTA when I got my phone today.
Click to expand...
Click to collapse
Download stock ROM that match your current version from https://mirrors.lolinet.com/firmware/moto/def/official/
Then flash super image and try to flash ROM again.
Code:
fastboot flash super super.img_sparsechunk.0
fastboot flash super super.img_sparsechunk.1
fastboot flash super super.img_sparsechunk.2
fastboot flash super super.img_sparsechunk.3
fastboot flash super super.img_sparsechunk.4
fastboot flash super super.img_sparsechunk.5
fastboot flash super super.img_sparsechunk.6
fastboot flash super super.img_sparsechunk.7

vache said:
Download stock ROM that match your current version from ...
Then flash super image and try to flash ROM again.
Code:
fastboot flash super super.img_sparsechunk.0
fastboot flash super super.img_sparsechunk.1
fastboot flash super super.img_sparsechunk.2
fastboot flash super super.img_sparsechunk.3
fastboot flash super super.img_sparsechunk.4
fastboot flash super super.img_sparsechunk.5
fastboot flash super super.img_sparsechunk.6
fastboot flash super super.img_sparsechunk.7
Click to expand...
Click to collapse
I have downloaded the official firmware (RETEU) which matches my device and carried out the flashing steps as you described. After that I tried to reflash your your rom and now got the following error :
fastboot flash system system.img
Resizing 'system_a' FAILED (remote: '')
fastboot: error: Command failed

orimigato said:
I have downloaded the official firmware (RETEU) which matches my device and carried out the flashing steps as you described. After that I tried to reflash your your rom and now got the following error :
fastboot flash system system.img
Resizing 'system_a' FAILED (remote: '')
fastboot: error: Command failed
Click to expand...
Click to collapse
Weird.
1. Are you sure that you're in fastbootd and not bootloader mode ?
2. Make sure to run the latest version of fastboot : https://dl.google.com/android/repository/platform-tools-latest-windows.zip

vache said:
Weird.
1. Are you sure that you're in fastbootd and not bootloader mode ?
2. Make sure to run the latest version of fastboot : https://dl.google.com/android/repository/platform-tools-latest-windows.zip
Click to expand...
Click to collapse
That was the problem. When I did a fastboot reboot fastboot and retried the install. It succeeded.
Rom is now succesfully installed. First impression : its really fast compared to stock !
Thanks for your kind and quick help !!!

orimigato said:
That was the problem. When I did a fastboot reboot fastboot and retried the install. It succeeded.
Rom is now succesfully installed. First impression : its really fast compared to stock !
Thanks for your kind and quick help !!!
Click to expand...
Click to collapse
Wew cool it worked, i was running out of ideas xD

First impression after a few days of running this rom :
-Stable
-Uptime good
-Fast
-Clean
A few things that are not working/not present :
-I have 3 bluetooth devices. 2 headsets, and one car (profile audio & telephone). The 2 headsets will connect fine, but no audio is send trough the bluetooth connection. Audio is still output to the internal speaker. The car is connecting to telephone bluetooth profile but will refuse to connect to bluetooth audio profile.
-The camera does not include support for the wideangle (0,5x zoom) camera (or I cant find it...)
-The interal SIP client is not working. It says it is connected and accepting calls but no calls are received. I used the same SIP account with exactly the same settings on my other phone running Lineage with the same internal SIP client, and this one is running fine and receiving calls.
One note : I turned off all google apps including Play services and Google partner setup. However when switching these on, I got the same issues as described above.
Very happy with this ROM so far, keep up the good work !

orimigato said:
First impression after a few days of running this rom :
-Stable
-Uptime good
-Fast
-Clean
A few things that are not working/not present :
-I have 3 bluetooth devices. 2 headsets, and one car (profile audio & telephone). The 2 headsets will connect fine, but no audio is send trough the bluetooth connection. Audio is still output to the internal speaker. The car is connecting to telephone bluetooth profile but will refuse to connect to bluetooth audio profile.
-The camera does not include support for the wideangle (0,5x zoom) camera (or I cant find it...)
-The interal SIP client is not working. It says it is connected and accepting calls but no calls are received. I used the same SIP account with exactly the same settings on my other phone running Lineage with the same internal SIP client, and this one is running fine and receiving calls.
One note : I turned off all google apps including Play services and Google partner setup. However when switching these on, I got the same issues as described above.
Very happy with this ROM so far, keep up the good work !
Click to expand...
Click to collapse
Thanks for the detailed report.
1. About bluetooth, noticed that later while testing, already fixed.
2. You'd better install back Moto Camera 2 from Play Store if you want to get all stock features.
3. Never used that feature tbh, could you grab some logs ? (i'll make some tests on my side anyway)
I'll try to release the new build later today.
Edit : Created an account here : https://www.linphone.org/freesip/home
Then used https://freephonebox.net/ to call me, and it seems to work. (see attached screenshots)

SIP
Retried the SIP and now it is working. Possible was not working earlier since my old phone was still registered. Thanks for checking:good:

Any idea when you could have a build available? Thanks in advance for your efforts :good:

orimigato said:
Any idea when you could have a build available? Thanks in advance for your efforts :good:
Click to expand...
Click to collapse
Sorry, it was delayed cause i was working on dolby. Ill post it tomorrow.
Edit : New build ->https://www.androidfilehost.com/?fid=4349826312261718849 (check OP for update instruction)
Changelog :
- Fix bluetooth audio playback
- Added Dolby audio (Use QS Tile to open it for now)
- Added Google Feed to launcher
- February security patch
- Fixed tap to wake
- Synced kernel source with CAF
https://gerrit.omnirom.org/q/status:merged
https://github.com/boulzordev/device_motorola_def/commits/android-10
https://github.com/boulzordev/kernel_motorola_sm6150/commits/android-10

Bluetooth works perfectly now. Dolby is also very nice. Many thanks!

Can we install magisk and install root apps
Also what is the camera sensor used in this phone, Sony IMX686 or Samsung GW1?

htcmusic said:
Can we install magisk and install root apps
Also what is the camera sensor used in this phone, Sony IMX686 or Samsung GW1?
Click to expand...
Click to collapse
Yes what's the best root method you guys using?

young-ster said:
Yes what's the best root method you guys using?
Click to expand...
Click to collapse
I will receive this phone next week (US version) and I will use patching boot.img method

mingkee said:
I will receive this phone next week (US version) and I will use patching boot.img method
Click to expand...
Click to collapse
I'm waiting around first to see more updates, also patching boot.img I could not find the same firmware version. mine ends with a 7

young-ster said:
Yes what's the best root method you guys using?
Click to expand...
Click to collapse
young-ster said:
I'm waiting around first to see more updates, also patching boot.img I could not find the same firmware version. mine ends with a 7
Click to expand...
Click to collapse
I see it
https://mirrors.lolinet.com/firmware/moto/def/official/RETUS/