Question [SOLVED] - Bootloop with completely new OPO9pro after oem unlock - OnePlus 9 Pro

Hello,
just received the phone (EU), updated latest online udpate. (no Google account etc added, just fast setup)
Enabled developer options, OEM unlocking and USB debugging.
After update, 1*reboot.
then another reboot to bootloader, and executed "fastboot oem unlock".
Phone rebooted to recovery. Wiped data, another reboot, now i have only the Red & white dots.....
Any suggestions/hints?
Thanks
Edit:
Entered fastboot mode, did a fastboot oem lock -> same, Red and white dots.

When I unlocked the bootloader I had to wait a much longer time than normal (about 8 minutes) for the dot splash screen to transition to the setup screen and for the phone to boot up fully.
I apologize if this is sort of a "duh I already did that" suggestion. Hope it can help.

Unfortunately not, i waited around 1 hour.
But thanks 4 your comment!

Booting the stock boot.img posted here on XDA -> same result.
Tried to swap the boot slot -> FAILED (remote: Slot Change is not allowed in merging state)
(bootloader) has-slot:system:no
(bootloader) current-slot:b
(bootloader) has-slot:boot:yes
(bootloader) slot-retry-count:b:7
(bootloader) slot-unbootable:b:no
(bootloader) slot-successful:b:yes
(bootloader) slot-retry-count:a:7
(bootloader) slot-unbootable:a:no
(bootloader) slot-successful:a:yes
(bootloader) slot-count:2
(bootloader) secure:yes
(bootloader) serialno:3d12cbee
(bootloader) product:lahaina
(bootloader) snapshot-update-status:merging
(bootloader) is-userspace:no
(bootloader) max-download-size:805306368
(bootloader) kernel:uefi
all:
finished. total time: 0.605s

Waiting msm

empty.cad said:
Waiting msm
Click to expand...
Click to collapse
Regarding MSM: if i understood correctly, this is something OPO does not provide, but is "extracted" by some guys here? (key extraction etc??)
So this may take some time.... Probably RTM (cancel order) next week.

yeah once I unlocked BL in fastboot and rebooted, the subsequent next boot took close to 10 minutes, but did boot into a wiped device after

Regarding the error "FAILED (remote: Slot Change is not allowed in merging state)" when swapping the slot, i found tha a
snapshot-update merge — Completes a merge operation, booting to recovery/fastbootd if necessary. This command is valid only if snapshot-update-status is merging, and is only supported in fastbootd.
May help.
But they talk also about
If merging or snapshotted, issue snapshot-update cancel.
But i prefer to ask here before executing, as i have no idea what this does

Well, i could not wait.
After doing a fastboot snapshot-update merge
i rebooted. Same issue.
Booted stock kernel -> issue
Swapped active slot -> Qualcom crash dump
Rebooted to fastboot, oem lock -> phone boots again.
Rebooted twice normally to confirm
Again fastboot oem unlock
Boot fine now. No idea what happened on first oem unlock.

I haven't tried this yet, but I found this link which seems to give a different fastboot command to use. Not sure how much difference it'll make for other users but thought I'd link to it just in case it helps others. I'll probably try it either tomorrow or over the weekend.

I did not use the fastboot oem unlock but the fastboot flashing unlock on the OP9P Global and worked the first time.

Related

HTC One M9 stuck on fastboot bootloader

Hi !
One of my friend ask me to try to save his One M9 phone, that seems to be bricked.
Here is the context :
- I absolutely don't know what he did, and it seems he don't either...
- The phone state is : Software status : Modifed, S-ON, and LOCKED
- I can't have another screen that Fastboot bootloader
The only options in the bootloader menu are :
REBOOT : it works
REBOOT TO BOOTLOADER : it works
BOOT TO DOWNLOAD MODE : does not work (Failed to boot to download mode)
BOOT TO RECOVERY MODE : does not work (Failed to boot to recovery mode)
POWER DOWN : it works
I tried a lt of things, and read a lot of threads before posting this one.
What i can say for the moment is :
- RUU flash using exe : does not work, i get an error saying the battery is too low
- RUU flash using SD card (extract rom.zip, renamed 0PJAIMG.zip, and put on the root of SD card) : zip is not detected at boot
- Getting bootloader unlocked : does not work, because fatboot oem get_token_identifier command seems unknown (probably because oem commands only work in download mode for this phone)
- Getting S-OFF : seems impossible without OS, as it needs Sunshine app installed...
- Few fastboot commands are OK (devices, getvar all, ...) but most of it are refused because of S-ON
- No adb commands are working
Here is the output of fastboot getvar all :
Code:
D:\ANDROID\RUU\RUU>htc_fastboot getvar all
(bootloader) version: 0.5
(bootloader) max-download-size: 0x20000000
(bootloader) partition-type:cache: ext4
(bootloader) partition-size:cache: 0x14000000
(bootloader) partition-type:userdata: ext4
(bootloader) partition-size:userdata: 0x5e0000000
(bootloader) partition-type:system: ext4
(bootloader) partition-size:system: 0x118000000
(bootloader) serialno: FA56GYJ01267
all:
finished. total time: 0.094s
htc_fastboot finished. total time: 0.718s
So, from your experts point of view, is this phone definitely bricked, or is there a way to save it ?
Thanks for your precious help guys !
Hey! I have the exact same problem. Anyone knows how to fix that?
I unrooted, stocked and relocked the bootloader. Everything went fine first, was using the phone about two days. But after a restart I'm stuck in bootloader and can't boot to download nor recovery mode.
Phone is only working with fastboot commands.
I also tried these steps OP tried and everything is the same.
I tried to flash hosd file and this works, but still not able to boot to download mode.
The HTC One is an unbranded EU model with 3.35.401.12 (<- but I think there's nothing on the phone right now)
i am also facing same problem with 2 htc one m9 which i have, i also have XTC2CLIP box which is professional tool for all htc devices, i can S-off with this box of all htc phone even no os needed, but phone should accept bootloader mode & ftm mode, & in this case where we can only goto fastboot mode, S-off command not working in state... i spend lot of time but no luck... but i still believe its only software bug & can be solve with fastboot commands. because i aslo read about same problem on htc X model. & they use fastboot command for this problem. but these commands not working on m9 case.
no solution for this? I have one m9 here exatly with the same situation, already did all your debuging with the same results
Hi there! I'm new here, created an account specially for replying to this thread:
So I'm having the same problem, phone (EU M9) died on it's own. Everything is stock.
Tried all of the above, also no results...
Here is my log from "fastboot getvar all"
Code:
C:\Android>fastboot getvar all
(bootloader) version:0.5
(bootloader) variant:MTP eMMC
(bootloader) secure:yes
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) max-download-size: 0x20000000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0x14000000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x5e0000000
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0x118000000
(bootloader) serialno:HT54NYJ04596
all:
finished. total time: 0.147s
If anyone has any ideas left, I'm happy to try them. For now, it's an ugly paperweight
If it died on its own and in a stock state then you can safely assume it's dead. Most likely nand failure.
Ps, dont all m9 serials start with an "F"?.
Beamed in by telepathy.
thank you
My guess is it tried to do an OTA update overnight, don't know exactly where it went wrong.
By the way, I do get some ADB communication:
First reboot to bootloader (so it doesn't say "Security Warning"), then select 'boot to Recovery Mode' and wait for the red triangle.
If it doesn't reach that point, reboot to bootloader once more. If it does reach the red triangle: hold the Power button and press the Volume Up button once. You can then release the Power button and Recovery Mode should become visible. Note that I tried several options in this menu including "Install from ADB" and "Install from SD Card", but both gave errors.
Hope someone can use this information.
I have exactly this same issue. Sounds like NAND failure? Nothing to be done about it?
KaiLoi said:
I have exactly this same issue. Sounds like NAND failure? Nothing to be done about it?
Click to expand...
Click to collapse
If it's spewing failed to mount errors then yes, dead phone. Only htc will be able to fix it.
Beamed in by telepathy.

Soft-bricked when going back to factory

I have bricked my Pixel C :crying: when I was trying to restore it back to how it was when I got it from the factory, because my girlfriend has been using it lately and complained about the message when booting. I thought maybe all I have to do is a factory reset, but that only wiped the data, so I foolishly :silly: figured this would be extremely easy, all I would have to do is pull down the newest factory image and flash it using the included script. That failed when trying to flash the bootloader saying something like "unknown command" sorry, didn't capture the exact wording, but that is pretty close. After that I rebooted the device and it wouldn't boot, as you could've guessed from me posting, instead it sat at the google screen. I left it for the night because for all I know, it was encrypting stuff or something.
I can still get to the custom recovery(TWRP) and fastboot, but I can't get into actual android. I tried applying an OTA update through TWRP after that figuring it will have access, but now instead of hanging at the google logo, I get bounced over to the recovery system.
At this point, I decided I need to slow down and do some more research, maybe even reach out for help. Could you guys help me troubleshoot my/soon to be my girlfriend's tablet? You can find the output of fastboot getvar all below, I can see mismatched versions and secure set to yes, but unlocked set to yes. I don't know what to be concerned about or what to do(I was about to research how to set the secure flag to no, but I realized how deep this hole is becoming.)
Code:
(bootloader) version: 0.3
(bootloader) version-bootloader: Google_Smaug.7900.27.0
(bootloader) version-baseband: N/A
(bootloader) product: dragon
(bootloader) secure: yes
(bootloader) max-download-size: 0x10000000
(bootloader) partition-type:boot: ext4
(bootloader) partition-type:kernel-a: ext4
(bootloader) partition-type:kernel-b: ext4
(bootloader) partition-type:recovery: ext4
(bootloader) partition-type:kernel: ext4
(bootloader) partition-type:system: ext4
(bootloader) partition-type:system-a: ext4
(bootloader) partition-type:vendor: ext4
(bootloader) partition-type:vendor-a: ext4
(bootloader) partition-type:cache: ext4
(bootloader) partition-type:data: ext4
(bootloader) partition-type:userdata: ext4
(bootloader) partition-type:metadata: ext4
(bootloader) partition-type:lnx: ext4
(bootloader) partition-type:misc: ext4
(bootloader) partition-type:persistent: ext4
(bootloader) partition-type:system-b: ext4
(bootloader) partition-type:vendor-b: ext4
(bootloader) partition-size:boot: 0x2000000
(bootloader) partition-size:kernel-a: 0x2000000
(bootloader) partition-size:kernel-b: 0x2000000
(bootloader) partition-size:recovery: 0x2000000
(bootloader) partition-size:kernel: 0x2000000
(bootloader) partition-size:system: 0xe0000000
(bootloader) partition-size:system-a: 0xe0000000
(bootloader) partition-size:vendor: 0x13000000
(bootloader) partition-size:vendor-a: 0x13000000
(bootloader) partition-size:cache: 0x19000000
(bootloader) partition-size:data: 0xd76b00000
(bootloader) partition-size:userdata: 0xd76b00000
(bootloader) partition-size:metadata: 0x4000000
(bootloader) partition-size:lnx: 0x2000000
(bootloader) partition-size:misc: 0x400000
(bootloader) partition-size:persistent: 0x80000
(bootloader) partition-size:chromeos: 0xe8f800000
(bootloader) partition-size:mbr: 0x200
(bootloader) partition-size:gpt: 0x4200
(bootloader) partition-size:RO_SECTION: 0x3f0000
(bootloader) partition-size:RO_VPD: 0x10000
(bootloader) partition-size:RW_SECTION_A: 0x580000
(bootloader) partition-size:RW_SECTION_B: 0x580000
(bootloader) partition-size:bootloader: 0x1000000
(bootloader) unlocked: yes
(bootloader) off-mode-charge: 1
(bootloader) battery-voltage: 4319 mV
(bootloader) variant:
(bootloader) battery-soc-ok: yes
(bootloader) Bdev-size:mmc: 62537072640
(bootloader) Bdev-size:flash: 16777216
(bootloader) Gbb-flags: 0x0
(bootloader) Oem-version:RO: Google_Smaug.7132.226.0
(bootloader) Oem-version:RW_A: Google_Smaug.7900.27.0
(bootloader) Oem-version:RW_B: Google_Smaug.7900.27.0
all: Done!
finished. total time: 0.460s
Try "fastboot continue"
Just tried that, it booted me back to the recovery. The only thing that it said on my computer's side is "resuming boot..." and some time statistics. Any commands I can run to help you guys help me?
techy121592 said:
Just tried that, it booted me back to the recovery. The only thing that it said on my computer's side is "resuming boot..." and some time statistics. Any commands I can run to help you guys help me?
Click to expand...
Click to collapse
Format data, not wipe, inside twrp.
If you still have problems, Install system vendor and boot.img again.
followmsi said:
Format data, not wipe, inside twrp.
If you still have problems, Install system vendor and boot.img again.
Click to expand...
Click to collapse
Ok, will try that and come back to you. Thank you.
I tried formatting the data partition, which didn't seem to make much of a difference, also I tried installing the boot and vendor images through twrp last night. Then vendor image applied without any problems, but the boot image didn't get installed, it looked like it was trying to reference the boot image like it is a directory.
Would I want to extract the image and then reference the directory? Though I don't know if twrp will let me point at a directory rather than a file.
Whenever I flashed roms, I tend to use fastboot, and then root it with twrp. Instead of that, would I be able to install the factory image zip from google? Or could I safely install all of the images(except recovery) through twrp individually? Do you think there is a flag or setting that I need to set in android, if so do you think I could install a custom rom and set the setting?
Sorry if these questions make me sound like a noob, but I am trying to be thorough.
Just use wugs or skipsoft toolkit to flash to stock or if you know how together around in fastboot flash stock. You could just download pure nexus and flash it via twrp. These are just suggestions, attempt at your own risk.
techy121592 said:
I tried formatting the data partition, which didn't seem to make much of a difference, also I tried installing the boot and vendor images through twrp last night. Then vendor image applied without any problems, but the boot image didn't get installed, it looked like it was trying to reference the boot image like it is a directory.
Would I want to extract the image and then reference the directory? Though I don't know if twrp will let me point at a directory rather than a file.
Whenever I flashed roms, I tend to use fastboot, and then root it with twrp. Instead of that, would I be able to install the factory image zip from google? Or could I safely install all of the images(except recovery) through twrp individually? Do you think there is a flag or setting that I need to set in android, if so do you think I could install a custom rom and set the setting?
Sorry if these questions make me sound like a noob, but I am trying to be thorough.
Click to expand...
Click to collapse
As we don't know the full story and we want to get your Pixel C back to normal ..
Pls install all partitions from latest google factory image via fastboot .. start with the bootloader.
Code:
fastboot flash bootloader bootloader-dragon-google_smaug.7900.27.0.img
fastboot reboot-bootloader
Pls delete boot first - before you flash it.
Code:
fastboot erase boot
fastboot flash boot boot.img
Do this for all partitions except recovery .. keep TRWP.
Do not boot into system and boot directly into TWRP and flash SuperSU.zip.
Reboot into system ..
Clockcycle - after I failed to use Google flash-all script, I swapped to using wugs. When I tried skipsoft like 8+ months ago it didn't support the final release of Android Nougat, only the rc's. Nowadays, is skipsoft better than wugs?
Clockcycle & followingmsi - Thank you for your suggestions, I'm out and about, so I'll try it once I get back home tonight; I didn't want you to think I was being unresponsive.
I got the results that I was expecting, it doesn't mean anything to me, but maybe you guys will know. I typed, "fastboot flash bootloader bootloader-dragon-google_smaug.7900.27.0.img" and got the following.
Code:
target reported max download size of 268435456 bytes
sending 'bootloader'...
OKAY [ 0.624s]
FAILED (remote: unsupported command)
finished. total time: 0.640s
and when I typed, "fastboot erase boot" I got the following.
Code:
******** Did you mean format this ext4 partition?
erasing 'boot'...
FAILED (remote: unsupported command)
finished. total time: 0.016s
Because of that, I tried formatting also, it gave me some output that looked like it was formatting it(showed me the inodes and everything,) but that was followed by the same "FAILED" message that you can see above.
When I was going through the menu to get to fastboot, I noticed that the bootloader must've got applied successfully the first time, when I was originally using the flash-all script, which is when this whole "adventure" began, because I saw that I had bootloader 7900.27.
I really feel like I am missing something that is staring me right in the face.
Found the solution...
https://forum.xda-developers.com/pixel-c/help/flashing-to-stock-android-npd90g-twrp-t3424863
In short running the following from the adb shell fixes it.
Code:
fwtool vbnv write dev_boot_fastboot_full_cap 1
techy121592 said:
I got the results that I was expecting, it doesn't mean anything to me, but maybe you guys will know. I typed, "fastboot flash bootloader bootloader-dragon-google_smaug.7900.27.0.img" and got the following.
Code:
target reported max download size of 268435456 bytes
sending 'bootloader'...
OKAY [ 0.624s]
FAILED (remote: unsupported command)
finished. total time: 0.640s
and when I typed, "fastboot erase boot" I got the following.
Code:
******** Did you mean format this ext4 partition?
erasing 'boot'...
FAILED (remote: unsupported command)
finished. total time: 0.016s
Because of that, I tried formatting also, it gave me some output that looked like it was formatting it(showed me the inodes and everything,) but that was followed by the same "FAILED" message that you can see above.
When I was going through the menu to get to fastboot, I noticed that the bootloader must've got applied successfully the first time, when I was originally using the flash-all script, which is when this whole "adventure" began, because I saw that I had bootloader 7900.27.
I really feel like I am missing something that is staring me right in the face.
Click to expand...
Click to collapse
Looks like you need to update your SDK.
So literally yesterday i had my Pixel C doing same thing after i unlocked bootloader and it got stuck on Erasing screen and then after hard reboot got stuck on google Splash screen. contacted google for help they didnt know crap. haha go figure. Of course this was after i tried a few things myself. They were sending me a new device which i canceled cause i fixed it later.
i was returning same crap for fastboot everytime couldnt do anything, from what i understand we messed up the Partitions somehow. So how to fix it, what might work for you as it worked for me.
I was on 7.1.1 Build number not important. I booted into Bootloader fastboot then to android recovery (stock), press PWR+VOL up to see menu for it as least for my pixel for other devices to each is own. Do a cache wipe and factory reset. when complete hold power and vol down to reboot.
Update system to latest firmware. somehow by letting OTA updates i did like 4 of them to get to 7.1.2 and then rebooted into Bootloader Fastboot Magically worked again so i preceded with root and what have you. all working Perfect now. Guess the OTA 7.1.2 update fixed all the partitions. Forget what specifically was missing from the partition but yeah. fastboot wouldn't let me do anything myself. IE flash all bat flash or boot anything. and ADB wouldn't flash anything.
of course i had to relock the bootloader in order for all this to work. Something about 7.1.2 just seemed to let me do what i want. on 7.1.1 it did not like unlocked bootloader not sure why. But im not a expert. =)
Back in day just used Odin to get back to factory not sure if thats a possiblity these days if someone knows let me know i would like to understand better.

Endless bootloop. Can't get into recovery even with fastboot commands

Been stuck with this one for days. Endless searches gets me as far as loading the bootloader (button longpress method) and flashing the usual images with fastboot. I used both the preview and post preview developer images. After successfully flashing (indivisually and clicking flash-all), the phone reboots over and over- never into the system or recovery. Any insight is extremely appreciated. Warranty is recently expired too so that's not an option unfortunately.
kt006 said:
Been stuck with this one for days. Endless searches gets me as far as loading the bootloader (button longpress method) and flashing the usual images with fastboot. I used both the preview and post preview developer images. After successfully flashing (indivisually and clicking flash-all), the phone reboots over and over- never into the system or recovery. Any insight is extremely appreciated. Warranty is recently expired too so that's not an option unfortunately.
Click to expand...
Click to collapse
Wait, so you can get into the fastboot menu, but you can't get into the recovery menu? What happens when you select the recovery menu from the fastboot menu?
As for the problem, the only thing I can think of that might be causing this is if you changed your data partition to f2fs for use with the Negalite custom rom. You'll need to change it back to ext4 either by using TWRP, formatting with the stock recovery menu or using the command fastboot erase userdata.
When trying to enter recovery mode, either with Fastboot command or button press, the phone just restarts and bootloops. I'll try your method later tonight.
TheSt33v said:
Wait, so you can get into the fastboot menu, but you can't get into the recovery menu? What happens when you select the recovery menu from the fastboot menu?
As for the problem, the only thing I can think of that might be causing this is if you changed your data partition to f2fs for use with the Negalite custom rom. You'll need to change it back to ext4 either by using TWRP, formatting with the stock recovery menu or using the command fastboot erase userdata.
Click to expand...
Click to collapse
Tried the fastboot erase userdata and followed with flash-all.bat. What's frustrating is that all the fastboot commands finish with no reported errors. Until it tries to boot into recovery and starts bootlooping again. It's like the watch can't access the recovery. Tried flashing twrp and fastboot boot twrp.img- still bootlooped.
kt006 said:
Tried the fastboot erase userdata and followed with flash-all.bat. What's frustrating is that all the fastboot commands finish with no reported errors. Until it tries to boot into recovery and starts bootlooping again. It's like the watch can't access the recovery. Tried flashing twrp and fastboot boot twrp.img- still bootlooped.
Click to expand...
Click to collapse
Very strange. Did you make any sort of modifications before this started happening? Custom rom, root, etc?
TheSt33v said:
Very strange. Did you make any sort of modifications before this started happening? Custom rom, root, etc?
Click to expand...
Click to collapse
Only the bootloader was unlocked and the developer preview was flashed.
Edit* This is what I get when using getvar all. Anyone notice anything unusual that might be the cause?
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) version:0.5
(bootloader) boardid:7N3BDH15BJ065725
(bootloader) macbt:2400BA712168
(bootloader) macwlan:2400BA712167
(bootloader) battery-soc-ok:yes
(bootloader) battery-voltage:4134mV
(bootloader) variant:
(bootloader) off-mode-charge:0
(bootloader) unlocked:yes
(bootloader) secure:yes
(bootloader) version-bootloader:STURGEONV3.8
(bootloader) version-baseband:N/A
(bootloader) display-panel:
(bootloader) charger-screen-enabled:0
(bootloader) max-download-size: 0x3d00000
(bootloader) partition-type:boot:emmc
(bootloader) partition-size:boot: 0x1400000
(bootloader) partition-type:recovery:emmc
(bootloader) partition-size:recovery: 0x1400000
(bootloader) partition-type : oem:ext4
(bootloader) partition-size: oem: 0x9678000
(bootloader) partition-type : cache:ext4
(bootloader) partition-size: cache: 0x20000000
(bootloader) partition-type : userdata:ext4
(bootloader) partition-size:userdata: 0x94ffbe00
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0x20000000
(bootloader) serialno:MQB*************
(bootloader) kernel:lk
(bootloader) product:sturgeon
all:
finished. total time: 0.078s
kt006 said:
Only the bootloader was unlocked and the developer preview was flashed.
Edit* This is what I get when using getvar all. Anyone notice anything unusual that might be the cause?
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) version:0.5
(bootloader) boardid:7N3BDH15BJ065725
(bootloader) macbt:2400BA712168
(bootloader) macwlan:2400BA712167
(bootloader) battery-soc-ok:yes
(bootloader) battery-voltage:4134mV
(bootloader) variant:
(bootloader) off-mode-charge:0
(bootloader) unlocked:yes
(bootloader) secure:yes
(bootloader) version-bootloader:STURGEONV3.8
(bootloader) version-baseband:N/A
(bootloader) display-panel:
(bootloader) charger-screen-enabled:0
(bootloader) max-download-size: 0x3d00000
(bootloader) partition-type:boot:emmc
(bootloader) partition-size:boot: 0x1400000
(bootloader) partition-type:recovery:emmc
(bootloader) partition-size:recovery: 0x1400000
(bootloader) partition-type : oem:ext4
(bootloader) partition-size: oem: 0x9678000
(bootloader) partition-type : cache:ext4
(bootloader) partition-size: cache: 0x20000000
(bootloader) partition-type : userdata:ext4
(bootloader) partition-size:userdata: 0x94ffbe00
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0x20000000
(bootloader) serialno:MQB*************
(bootloader) kernel:lk
(bootloader) product:sturgeon
all:
finished. total time: 0.078s
Click to expand...
Click to collapse
My readout looks exactly the same except in fields where one would expect it to be different (serial number, mac addresses). The only exception is that I'm on bootloader version 4.2. I'm currently running the most recent official firmware version (the post-preview version is an older version than the most recent. I took several OTAs after I flashed it when I decided I didn't like the wear 2.0 preview), but I don't see why that would matter or cause the problem you're having since your bootloader is unlocked and should therefore not be enforcing anything. When you flash the wear 2.0 preview, does your bootloader version change?
Yes, when flashing the preview it changes to 4.1. I'm looking into kernels. Hopefully it'll get me somewhere
kt006 said:
Yes, when flashing the preview it changes to 4.1. I'm looking into kernels. Hopefully it'll get me somewhere
Click to expand...
Click to collapse
If the kernel was the problem, it would dump you into the fastboot menu instead of bootlooping. Or if it did bootloop, it would be at the bootanimation and not at the initial Huawei screen. The boot logo (not animation) is stored somewhere in the bootloader for many android devices (with some exceptions, but I've never heard of it being stored on /system or anything like that). Also, you flash the kernel at the same time as everything else when you double click on flash-all, so whatever kernel is there should match whatever you flashed. The fact that it isn't loading anything except fastboot and the boot logo makes me think that your bootloader is pretty pissed off. My theory is either it didn't get the memo when you unlocked it and it's still trying to enforce whatever version was on the phone when you did that, or it's totally borked and has lost the ability to understand that all the partitions have officially signed images on them.
TheSt33v said:
If the kernel was the problem, it would dump you into the fastboot menu instead of bootlooping. Or if it did bootloop, it would be at the bootanimation and not at the initial Huawei screen. The boot logo (not animation) is stored somewhere in the bootloader for many android devices (with some exceptions, but I've never heard of it being stored on /system or anything like that). Also, you flash the kernel at the same time as everything else when you double click on flash-all, so whatever kernel is there should match whatever you flashed. The fact that it isn't loading anything except fastboot and the boot logo makes me think that your bootloader is pretty pissed off. My theory is either it didn't get the memo when you unlocked it and it's still trying to enforce whatever version was on the phone when you did that, or it's totally borked and has lost the ability to understand that all the partitions have officially signed images on them.
Click to expand...
Click to collapse
The strangest thing happened. I disconnected the internal battery overnight. When I reconnected it the watch booted into the system perfectly fine. Then after restarting the watch because of a pairing error, I'm back to square one again.

bricked htc one m8s

Hi all,
@THE company I work we found a htc one m8s that when I booted it went straight to bootloader menu.
I want to get it working again so I started reading here on the forums, download some stuff from ruu.lalleman.net that I found in one of the other treads. In the end i'm still stuck and i'm hoping to get some advice through this channel.
Here is my current status
when the devices is connected to the PC it boots ALWAYS straight to bootloader with the following info
software status : Modified
unlocked
m8QL_UL PVT SHIP S-ON
HBOOT-3.19.0.000
[email protected]
OS-1.16.401.10
eMMC-boot 2048MB
aug 13 2015
Fastboot USB with the normal stuff
when I try to load a RUU through the exe I reboot the device and then keeps waiting with in the end a disconnect (saying I need to connect my device) the device itself is already back in bootloader window.
when I try to use htc_fastboot to flash a recovery it gives me
fastboot flash recovery recovery.img
sending 'recovery' (6002 KB)... OKAY
writing 'recovery'... OKAY
Execution time is 1(s)
but then on reboot it's straight back to bootloader menu no recovery
when I try to lock the device I get
fastboot oem lock
... (bootloader) [PGFS] partition_update_pgfs: pg1fs_security
(bootloader) TZ_HTC_SVC_ENC ret = 0
(bootloader) [PGFS] partition_update_pgfs: pg2fs_sec_recovery
(bootloader) Lock successfully...
(bootloader) deinit_lcd
(bootloader) mipi display off
(bootloader) TZ_HTC_SVC_DISABLE ret = 536739196 (0x1FFDFD7C)
(bootloader) [ERR] Failed to disable wdog debug: 15
(bootloader) [INFO] Calling SCM to disable SPMI PMIC arbiter
(bootloader) [ERR] Cannot halt SPMI arbiter!!
(bootloader) [INFO] Rebooting device
(bootloader) [INFO] Rebooting device arbiter!!I PMIC arbitery-
FAILED (unknown status code)
Execution time is 1(s)
I did get it unlocked (as it was locked before but relocking is not working)
Also fastboot devices shows me the devices but adb devices shows nothing (tried both htc drives and general android ones)
These are my var all info
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: [email protected]
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.16.401.10
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8ql_ul
(bootloader) platform: hTCBmsm8939
(bootloader) modelid: 0PKV10000
(bootloader) cidnum: HTC__031
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 1d456ef7
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
(bootloader) mfg-name: 0001
all: Done!
Execution time is 28(ms)
Hoping on any help from here
Greetings
Tom
Little update:
I kept on trying different versions from recovery / boot / ruu's in the hope that one works but nothing so far.
In another topic somewhere I did found that as long as my device is unlocked it will not work to use RUU, so locking the device again will be my first step.
I did notice that when I ended my adventure yesterday evening I wasn't able to turn the phone off, I always rebooted (in like a millisecond) back to bootloader as long as it was connected to the pc. I had to remove the usb connection and then try couple of times with volume-up / power to turn it off.
I did do the 2 minutes bright licht / volume up + down + power button trick to reset the battery but that didn't change anything.
also as a last minute addition
when I do the fastboot -> image CRC i'm getting a 0X0 on sbl2 - sbl3 - boot and recovery so it seems that what ever I do with htc_fastboot flash is not sticking.
Going to look into trying to get it locked again now first in combination with trying to find out why I can't write to the damn phone (adb isn't working ether so maybe driver problem also ?)
The adventure continues
Tom
adb works only while on running OS or in custom recovery (don't know whether it works on stock recovery) not on fastboot/bootloader.
Only fastboot (generic) or htc_fastboot works on fastboot.
Is the RUU that you tried
0PKVIMG_M8_QL_UL_L50_SENSE60_HTC_Europe_1.16.401.1 [email protected]_15.00_016_F_release_450 409_combined_signed.zip ?
ckpv5 said:
adb works only while on running OS or in custom recovery (don't know whether it works on stock recovery) not on fastboot/bootloader.
Only fastboot (generic) or htc_fastboot works on fastboot.
Is the RUU that you tried
0PKVIMG_M8_QL_UL_L50_SENSE60_HTC_Europe_1.16.401.1 [email protected]_15.00_016_F_release_450 409_combined_signed.zip ?
Click to expand...
Click to collapse
That is indeed the RUU i tried, i got it based on the fastboot var all i did.
Still trying to get my Phone locked again as that is holding back the ruu upgrade now from what i see.
Have you tried using htc_fastboot to relock ?
It seems fastboot generic mostly not working for M8s.
ckpv5 said:
Have you tried using htc_fastboot to relock ?
It seems fastboot generic mostly not working for M8s.
Click to expand...
Click to collapse
Yhea i did it with the htc_fastboot version.
another update,
After some more trial and error while aiming for the locking of my phone i'm still stuck.
Both my boot and my recovery are empty it seems (the 0x0 from the image crc) and all the others still have 0xA.....B or what ever value in them
All the writing I do like
C:\tel>htc_fastboot.exe flash recovery recovery_signed.img
sending 'recovery' (30080 KB)... OKAY
writing 'recovery'... OKAY
Execution time is 3(s)
seems to be working but that doesn't change the crc value's nether does it allow me to use the recovery from the hboot menu.
also when I type stuff like htc_fastboot oem rebootRUU it brings me straight back to the bootloader menu, no black screen to do htc_fastboot flash zip rom.zip.
What I didn't try yet is using a SD-card and see if that fixes it (I could put that card in my other phone, write stuff to it and use it in the M8s.
Anybody got any expereance for using a sdcard to flash the device back to stock.
@ this moment I will be kind of happy with anything that advances me a step
Tom
I got it to work
You may as well give up.
Android will continue to suck and be a deep state tool.
kruc Ire said:
I got it to work
You may as well give up.
Android will continue to suck and be a deep state tool.
Click to expand...
Click to collapse
How do you mean give up ?
is there no way arround based on your opinion from what i posted above ?
I Always hoped it was my lack of knowledge that was holding me back in fixing it ...
Ok if you wanna do it like i did you gotta use the sd card. It should work. Call it by its shortened name and relock the phone first. It can take a long time in several stages.
I was a bit down on android since google keeps screwing with it like taking away panoramio and adding miles upon miles of bloat and force resetting my permissions which I believe I have finally found a solution to in m8s.
If you wanna do it you can. Use that same 1.8 GB firmware we can find on the web. And rename it to the m8s required: 0PKVIMG.zip (i am going offa memory but this looks right to me???) and put it in the root of your microSD. The bootloader should be "relocked" anything I forgot? You don't have to reflash the std recovery first unless I forgot
Then once these things are inplace you should see a full flash after bootin ta bootloader.
kruc Ire said:
Ok if you wanna do it like i did you gotta use the sd card. It should work. Call it by its shortened name and relock the phone first. It can take a long time in several stages.
I was a bit down on android since google keeps screwing with it like taking away panoramio and adding miles upon miles of bloat and force resetting my permissions which I believe I have finally found a solution to in m8s.
If you wanna do it you can. Use that same 1.8 GB firmware we can find on the web. And rename it to the m8s required: 0PKVIMG.zip (i am going offa memory but this looks right to me???) and put it in the root of your microSD. The bootloader should be "relocked" anything I forgot? You don't have to reflash the std recovery first unless I forgot
Then once these things are inplace you should see a full flash after bootin ta bootloader.
Click to expand...
Click to collapse
I did those things and placed the file on the SD card ( 0PKVIMG.zip )
When I go to the phone then and run it it gives me the following error:
Device halted due to Large Image update fail!
press <power> to reboot.
I looked into that and seems I need to do a partial flash for that but didn't found more info on that yet.
Also i'm still stuck on the htc_fastboot OEM lock error i'm getting (see above)
Tom
TomBrunson said:
I did those things and placed the file on the SD card ( 0PKVIMG.zip )
When I go to the phone then and run it it gives me the following error:
Device halted due to Large Image update fail!
press <power> to reboot.
I looked into that and seems I need to do a partial flash for that but didn't found more info on that yet.
Also i'm still stuck on the htc_fastboot OEM lock error i'm getting (see above)
Tom
Click to expand...
Click to collapse
You need to have plenty of space. I have seen large image update fail at some time before. I'll see if I can find my photos from the flash on my m8 (I used the m8 to document the m8s firmware flash). It doesn't have to be "locked", "relocked" is enough
I made that video but if the F'N censors won't let me put up the lyrics of a song they HATE in their pinheads then I won't be posting their garbage they WOULD view.
I'll keep putting up large videos though just to chew up this sh!tty world's resources. If it's a world of creeps it's
Music videos mostly. Ooh how they HATE my beautiful music...and I can hear the little b##ch there in her fuzzy chair. Like she spoke directly into my head. And if it hadn't taken me so long to make a thumbnail she wouldn't have been able to install her trick. Literally FFFF youtube.
kruc Ire said:
You need to have plenty of space. I have seen large image update fail at some time before. I'll see if I can find my photos from the flash on my m8 (I used the m8 to document the m8s firmware flash). It doesn't have to be "locked", "relocked" is enough
Click to expand...
Click to collapse
Is there a different command to Relock as to Lock ?
I couldn't find anything else then htc_fastboot oem lock
Tom
Ok i'm over it. I attached a different (worse) song and reuploaded it. No censorship now.
HTC M8s firmware flash in photos:
Please note I only started making a video because I noticed that time bar on upper right about 15 minutes into the (uninterrupted) flash. So that took a long time and I was concerned about the messed up and overprinted text and made photos during every new screen between the third or fourth at the start (when I caught up with my camera) up till the time of video starting.
So yeah what I am trying to say is it seemed to take very long, with many seemingly false starts and failures. Only by waiting did it finally achieve correctness.
thank you for the video
Seems so that it's still the same issue for me as I don't get my phone locked or relocked
i'll keep on looking aint giving up that quick
TomBrunson said:
thank you for the video
Seems so that it's still the same issue for me as I don't get my phone locked or relocked
i'll keep on looking aint giving up that quick
Click to expand...
Click to collapse
Are you sure you have the correct command? There is a lot of bad info out there. Better get a 2nd source and third for commands. Did you be sure to enable adb bridge in dev options? Can't forget to do that. Go through the entire thing at HTC.dev and do all it says and download their fastboot. Then be sure to have adequate space on phone and storage. You have a nandroid? Then you could try wiping and starting from zero with the flash. This may have been what I done. I definitely did something like that similarly very recently and I think it was cause I was trying the new Los rom just before I gave up on it and decided to do this firmware.
kruc Ire said:
Are you sure you have the correct command? There is a lot of bad info out there. Better get a 2nd source and third for commands. Did you be sure to enable adb bridge in dev options? Can't forget to do that. Go through the entire thing at HTC.dev and do all it says and download their fastboot. Then be sure to have adequate space on phone and storage. You have a nandroid? Then you could try wiping and starting from zero with the flash. This may have been what I done. I definitely did something like that similarly very recently and I think it was cause I was trying the new Los rom just before I gave up on it and decided to do this firmware.
Click to expand...
Click to collapse
When I got the phone it was locked, I then did all the steps to unlock it as I hoped that would be the solution. Those steps did work but it didn't solve the problem. I think wanted to do the RUU thing but therefor the phone needs to be locked or relocked (htc_fastboot oem lock) but hat gives me errors as I posted before.
I'm still in the process of reading as much as possible to find different ways to lock or relock the phone in order to do the RUU update.
Greetings,
Tom
You have never gotten it to lock? I thought you said you couldn't get the zip to work?
---------- Post added at 06:53 PM ---------- Previous post was at 06:38 PM ----------
TomBrunson said:
When I got the phone it was locked, I then did all the steps to unlock it as I hoped that would be the solution. Those steps did work but it didn't solve the problem. I think wanted to do the RUU thing but therefor the phone needs to be locked or relocked (htc_fastboot oem lock) but hat gives me errors as I posted before.
I'm still in the process of reading as much as possible to find different ways to lock or relock the phone in order to do the RUU update.
Greetings,
Tom
Click to expand...
Click to collapse
What output does your cmd window give u? Can you show a screenshot of what your command is and the output.
I see. You are trying to put a lollipop. Still first ya gotta lock it does anyone remember the rules for firmware flash? Is it going to screw up the phone to flash the MM 60 sense 70 ? Dude are you in Europe? The 60 70 I flashed from my microSd was a EUROPE.

Help with factory resetting Moto g5

I rooted my moto g5 and installed pisxel experience on it back in novemeber and now it's stopped working and won't start past the "device cant be trusted" screen. I have already emailed someone about it but I might get a quicker response on here. This is my email; (it describes what has happened)
I was just using my phone while i was coming back from a grocery store and when i got home, the screen wouldn't turn on, even when i plugged it in to charge it. I took out the battery and put it back in and tried to turn it on, I won't turn on and it will stay in the screen that says "your device has been unlocked and cant be trusted" even though it says it will boot in 5 seconds. I can get into the boot loader and do all of the options. I'm wondering if I can just factory reset it because it is an option in there but I don't want to break my phone even more if it can be salvaged. You're one of the only people out there who make sense and know what to do in a situation like this. I checked your video again and it says do not factory reset as you could lose your imei number. This is my only phone and I kinda need it to work. If you have any ideas that could help me it would be very appreciated if you can. I made a backup but I think it was lost when i changed SD cards because the one kept getting "corrupt" (This was a problem before I installed the ROM). I heard now that the official 8.1 ROM is out on moto g5s and I would like to keep my root but go to the official one. i have no problem rooting it again but I don't want to have Pisxel Experience anymore. If I have to keep it that's fine I guess. I tried to boot into recovery from boot loader but it wont get past the twrp loading screen.
If anyone can help me factory resetting this thing I would be so grateful. Also Someone will say something about me rooting and doing this to my only phone, but I was stupid and did it anyway. I know everyone says they're not responsible for bricked devices and I'm not blaming anyone. But this has happened once before and a battery removal fixed the problem, but now it wont.
shAen123 said:
I rooted my moto g5 and installed pisxel experience on it back in novemeber and now it's stopped working and won't start past the "device cant be trusted" screen. I have already emailed someone about it but I might get a quicker response on here. This is my email; (it describes what has happened)
I was just using my phone while i was coming back from a grocery store and when i got home, the screen wouldn't turn on, even when i plugged it in to charge it. I took out the battery and put it back in and tried to turn it on, I won't turn on and it will stay in the screen that says "your device has been unlocked and cant be trusted" even though it says it will boot in 5 seconds. I can get into the boot loader and do all of the options. I'm wondering if I can just factory reset it because it is an option in there but I don't want to break my phone even more if it can be salvaged. You're one of the only people out there who make sense and know what to do in a situation like this. I checked your video again and it says do not factory reset as you could lose your imei number. This is my only phone and I kinda need it to work. If you have any ideas that could help me it would be very appreciated if you can. I made a backup but I think it was lost when i changed SD cards because the one kept getting "corrupt" (This was a problem before I installed the ROM). I heard now that the official 8.1 ROM is out on moto g5s and I would like to keep my root but go to the official one. i have no problem rooting it again but I don't want to have Pisxel Experience anymore. If I have to keep it that's fine I guess. I tried to boot into recovery from boot loader but it wont get past the twrp loading screen.
If anyone can help me factory resetting this thing I would be so grateful. Also Someone will say something about me rooting and doing this to my only phone, but I was stupid and did it anyway. I know everyone says they're not responsible for bricked devices and I'm not blaming anyone. But this has happened once before and a battery removal fixed the problem, but now it wont.
Click to expand...
Click to collapse
So does your phone actually boot into the TWRP or it doesn't?
If it doesn't, download this 64bit TWRP https://androidfilehost.com/?fid=673956719939821589, copy it into the adb folder and flash it using the command below:
Code:
fastboot flash recovery name_of_file.img
Then, reboot the bootloader using command below and try to boot into the TWRP as you normally would.
Code:
fastboot reboot bootloader
If the TWRP boots, try to wipe cache and dalvik cache at first, then try to boot into the OS. If it won't help, wipe everything except system, microsd and USB-OTG (however, you will loose your data), then try to boot into the OS again.
Let me know the results.
Just few more things to note:
None of the G5s's (montana) ROMs (custom, stock, doesn't matter) won't work with G5 (cedric).
For sure, you can't wipe your IMEI just by factory resetting your phone. It may get wiped if erase modem commands are executed with broken persist or by reverting to stock using fastboot with anything 64bit installed at least once. However, there's already a fix for stock Nougat ROM, which fixes ownership of some persist files and brings back the IMEI. In case of lost IMEI, just flash this zip: https://androidfilehost.com/?fid=3700668719832240875
Andrej_SK said:
So does your phone actually boot into the TWRP or it doesn't?
If it doesn't, download this 64bit TWRP, copy it into the adb folder and flash it using the command below:
Code:
fastboot flash recovery name_of_file.img
Then, reboot the bootloader using command below and try to boot into the TWRP as you normally would.
Code:
fastboot reboot bootloader
If the TWRP boots, try to wipe cache and dalvik cache at first, then try to boot into the OS. If it won't help, wipe everything except system, microsd and USB-OTG (however, you will loose your data), then try to boot into the OS again.
Let me know the results.
Just few more things to note:
None of the G5s's (montana) ROMs (custom, stock, doesn't matter) won't work with G5 (cedric).
For sure, you can't wipe your IMEI just by factory resetting your phone. It may get wiped if erase modem commands are executed with broken persist or by reverting to stock using fastboot with anything 64bit installed at least once. However, there's already a fix for stock Nougat ROM, which fixes ownership of some persist files and brings back the IMEI. In case of lost IMEI, just flash this zip:
Click to expand...
Click to collapse
Yeah sorry if the email thing was confusing, after I read it over a few times it didnt make too much sense. I cannot get into TWRP, also adb is not working for me. I installed it and ran the abd thing and it just opened, spit a lot of code and then quit. I tired to follow the picture guide to get the device n stuff but the phone wont show in device manager. Is there a way I can pm you on discord or something? I think I can be more helpful on there and we can talk at the same time.
EDIT#1: Never mind, i got into adb, i just forgot that you had to do the command window thing.
EDIT#2: I did the command and it sits at waiting for device. It wont go past that, I think i should install moto drivers because i reset my pc which got rid of them. Ill update once done.
shAen123 said:
Yeah sorry if the email thing was confusing, after I read it over a few times it didnt make too much sense. I cannot get into TWRP, also adb is not working for me. I installed it and ran the abd thing and it just opened, spit a lot of code and then quit. I tired to follow the picture guide to get the device n stuff but the phone wont show in device manager. Is there a way I can pm you on discord or something? I think I can be more helpful on there and we can talk at the same time.
Click to expand...
Click to collapse
Where's your adb folder located?
Maybe I might help you using remote access (TeamViewer) tomorrow (it's 11:30 p.m. here actually), if things will be more broken than they seems to be right now.
EDIT: Remember that while the phone is in the bootloader menu, the main word of the each command is "fastboot" (e.g. "fastboot flash...", "fastboot boot..."), not "adb".
Andrej_SK said:
Where's your adb folder located?
Maybe I might help you using remote access (TeamViewer) tomorrow (it's 11:30 p.m. here actually), if things will be more broken than they seems to be right now.
Click to expand...
Click to collapse
Its okay i got it working, heres what happened
PS C:\adb> fastboot flash recovery twrp-3.2.1-0-cedric.img
target reported max download size of 536870912 bytes
sending 'recovery' (14660 KB)...
OKAY [ 0.465s]
writing 'recovery'...
(bootloader) Image not signed or corrupt
OKAY [ 0.564s]
finished. total time: 1.030s
PS C:\adb> fastboot reboot bootloader
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
format <partition> format a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
continue continue with autoboot
reboot reboot device normally
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache (and format
if supported by partition type)
-u do not first erase partition before
formatting
-s <specific device> specify device serial number
or path to device port
-l with "devices", lists device paths
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address. default: 0x10000000
-n <page size> specify the nand page size. default: 2048
-S <size>[K|M|G] automatically sparse files greater than
size. 0 to disable
PS C:\adb>
I have a feeling that the reboot didnt work, I tried to boot into twrp and it still is being stuck on the loading screen (teamwin)
shAen123 said:
Its okay i got it working, heres what happened
PS C:\adb> fastboot flash recovery twrp-3.2.1-0-cedric.img
target reported max download size of 536870912 bytes
sending 'recovery' (14660 KB)...
OKAY [ 0.465s]
writing 'recovery'...
(bootloader) Image not signed or corrupt
OKAY [ 0.564s]
finished. total time: 1.030s
PS C:\adb> fastboot reboot bootloader
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
format <partition> format a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
continue continue with autoboot
reboot reboot device normally
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache (and format
if supported by partition type)
-u do not first erase partition before
formatting
-s <specific device> specify device serial number
or path to device port
-l with "devices", lists device paths
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address. default: 0x10000000
-n <page size> specify the nand page size. default: 2048
-S <size>[K|M|G] automatically sparse files greater than
size. 0 to disable
PS C:\adb>
I have a feeling that the reboot didnt work, I tried to boot into twrp and it still is being stuck on the loading screen (teamwin)
Click to expand...
Click to collapse
The only one solutions seems to be flashing the correct stock FW right now, if even TWRP refuses to boot.
Btw, sorry for my mistake, but even the correct command is "fastboot reboot-bootloader" (missing dash between "reboot" and "bootloader" words), I don't think it's gonna help.
Andrej_SK said:
The only one solutions seems to be flashing the correct stock FW right now, if even TWRP refuses to boot.
Click to expand...
Click to collapse
So if i go into the bootloader and factory it, would it erase the imei number? if twrp flashed properly i should be okay? I can try and boot into os normally again
Oops, I didnt see the edit in time Ill do that
I think it worked, screen went black, then back into bootloader, adb said okay. Ill try and boot into twrp
shAen123 said:
So if i go into the bootloader and factory it, would it erase the imei number? if twrp flashed properly i should be okay? I can try and boot into os normally again
Click to expand...
Click to collapse
Yes, give a boot into the OS a try at first.
Your IMEI will get wiped if you decide to flash stock ROM, but fortunately, there's a fix. Just flash stock Nougat (rather don't flash bootloader and gpt), boot into the OS, install TWRP, flash 2 zips (links below) and boot into the OS again.
https://androidfilehost.com/?fid=3700668719832240875 fixes ownership of some persist files and brings IMEI back
https://build.nethunter.com/android-tools/no-verity-opt-encrypt/ use the 6.0 version, avoids bootloop on stock ROM
Andrej_SK said:
Yes, give a boot into the OS a try at first.
Your IMEI will get wiped if you decide to flash stock ROM, but fortunately, there's a fix. Just flash stock Nougat (rather don't flash bootloader and gpt), install TWRP and flash 2 zips (links below):
fixes ownership of some persist files and brings IMEI back
use the 6.0 version, avoids bootloop on stock ROM
Click to expand...
Click to collapse
okay, also im kind of a "noob" at this, correct me if im wrong but in the bootloader menu there is an option called factory mode. My guess is that it factory resets the phone. Is this what you mean by "flashing the stock rom"?
(I know how to do things, its just terms I'm not good at)
shAen123 said:
okay, also im kind of a "noob" at this, correct me if im wrong but in the bootloader menu there is an option called factory mode. My guess is that it factory resets the phone. Is this what you mean by "flashing the stock rom"?
Click to expand...
Click to collapse
Nope. You have to flash stock ROM using fastboot commands. Type "fastboot getvar all" while yours phone is in the bootloader mode and copy the entire output into your next reply. I'll have a look at it in the morning (it's halfnight right now here, in the Slovakia) and send you link for an appropriate version of stock ROM which won't brick your phone.
Andrej_SK said:
Nope. You have to flash stock ROM using fastboot commands. Type "fastboot getvar all" while yours phone is in the bootloader mode and copy the entire output into your next reply. I'll have a look at it in the morning (it's halfnight right now) and send you link for an appropriate version of stock ROM which won't brick your phone.
Click to expand...
Click to collapse
okay man will do, thanks for your help tonight, heres the stuff;
PS C:\adb> fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8937-B8.25
(bootloader) product: cedric
(bootloader) board: cedric
(bootloader) secure: yes
(bootloader) hwrev: P5
(bootloader) radio: 6
(bootloader) storage-type: emmc
(bootloader) emmc: 16GB SAMSUNG QE13MB RV=08 PV=07 FV=0000000000000007
(bootloader) ram: 2GB SAMSUNG LP3 DIE=8Gb M5=01 M6=05 M7=00 M8=1F
(bootloader) cpu: MSM8937
(bootloader) serialno: ZY3223TPZK
(bootloader) cid: 0x0032
(bootloader) channelid: 0x81
(bootloader) uid: A33500F600000000000000000000
(bootloader) securestate: flashing_unlocked
(bootloader) verity-state: enforcing
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: 351871081161092
(bootloader) meid:
(bootloader) date: 04-17-2017
(bootloader) sku: XT1670
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Thu Jan 1 0: 0:23 UTC 1970"
(bootloader) ro.build.fingerprint[0]: motorola/cedric/cedric:7.0/NPPS25.
(bootloader) ro.build.fingerprint[1]: 137-93-14/21:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.25.351.21.cedric.ret
(bootloader) ro.build.version.full[1]: ail.en.US
(bootloader) ro.build.version.qcom: LA.UM.5.6.r1-01900-89xx.0
(bootloader) version-baseband: M8937_22.29.02.56.01R CEDRIC_LATAM_CUST
(bootloader) kernel.version[0]: Linux version 3.18.31-perf-g4a0c859-0002
(bootloader) kernel.version[1]: 5-g7f05384 ([email protected]) (gcc ver
(bootloader) kernel.version[2]: sion 4.8 (GCC) ) #1 SMP PREEMPT Tue Jun
(bootloader) kernel.version[3]: 19 06:51:25 CDT 2018
(bootloader) sbl1.git: git=MBM-NG-VB8.25-0-g0cc8007
(bootloader) rpm.git: git=3f612e6-dirty
(bootloader) tz.git: git=87b19b9-dirty
(bootloader) devcfg.git: git=87b19b9-dirty
(bootloader) keymaster.git: git=87b19b9-dirty
(bootloader) cmnlib.git: git=87b19b9-dirty
(bootloader) cmnlib64.git: git=87b19b9-dirty
(bootloader) prov.git: git=MBM-NG-VB8.0C-0-g283f623
(bootloader) aboot.git: git=MBM-NG-VB8.25-0-gb74f6bf
(bootloader) qe: qe 0/0
(bootloader) frp-state: no protection (77)
(bootloader) ro.carrier: bwaca
all: listed above
finished. total time: 0.071s
Again, thanks for the help
shAen123 said:
okay man will do, thanks for your help tonight, heres the stuff;
PS C:\adb> fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8937-B8.25
(bootloader) product: cedric
(bootloader) board: cedric
(bootloader) secure: yes
(bootloader) hwrev: P5
(bootloader) radio: 6
(bootloader) storage-type: emmc
(bootloader) emmc: 16GB SAMSUNG QE13MB RV=08 PV=07 FV=0000000000000007
(bootloader) ram: 2GB SAMSUNG LP3 DIE=8Gb M5=01 M6=05 M7=00 M8=1F
(bootloader) cpu: MSM8937
(bootloader) serialno: ZY3223TPZK
(bootloader) cid: 0x0032
(bootloader) channelid: 0x81
(bootloader) uid: A33500F600000000000000000000
(bootloader) securestate: flashing_unlocked
(bootloader) verity-state: enforcing
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: 351871081161092
(bootloader) meid:
(bootloader) date: 04-17-2017
(bootloader) sku: XT1670
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Thu Jan 1 0: 0:23 UTC 1970"
(bootloader) ro.build.fingerprint[0]: motorola/cedric/cedric:7.0/NPPS25.
(bootloader) ro.build.fingerprint[1]: 137-93-14/21:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.25.351.21.cedric.ret
(bootloader) ro.build.version.full[1]: ail.en.US
(bootloader) ro.build.version.qcom: LA.UM.5.6.r1-01900-89xx.0
(bootloader) version-baseband: M8937_22.29.02.56.01R CEDRIC_LATAM_CUST
(bootloader) kernel.version[0]: Linux version 3.18.31-perf-g4a0c859-0002
(bootloader) kernel.version[1]: 5-g7f05384 ([email protected]) (gcc ver
(bootloader) kernel.version[2]: sion 4.8 (GCC) ) #1 SMP PREEMPT Tue Jun
(bootloader) kernel.version[3]: 19 06:51:25 CDT 2018
(bootloader) sbl1.git: git=MBM-NG-VB8.25-0-g0cc8007
(bootloader) rpm.git: git=3f612e6-dirty
(bootloader) tz.git: git=87b19b9-dirty
(bootloader) devcfg.git: git=87b19b9-dirty
(bootloader) keymaster.git: git=87b19b9-dirty
(bootloader) cmnlib.git: git=87b19b9-dirty
(bootloader) cmnlib64.git: git=87b19b9-dirty
(bootloader) prov.git: git=MBM-NG-VB8.0C-0-g283f623
(bootloader) aboot.git: git=MBM-NG-VB8.25-0-gb74f6bf
(bootloader) qe: qe 0/0
(bootloader) frp-state: no protection (77)
(bootloader) ro.carrier: bwaca
all: listed above
finished. total time: 0.071s
Again, thanks for the help
Click to expand...
Click to collapse
As you have the latest Nougat firmware (NPPS25.137-93-14), use Lenovo Moto Smart Assistant (Rescue function, in dropdown menu choose "XT1670") to download it. Make sure, it offers you NPPS25.137-93-14 firmware to download, not an older one, which might brick your phone. If it offers you Oreo firmware (build number starts with letter "O" instead of "N"), you can use it to repair your phone too, but if you want to stay with Nougat one, let me know and I'll upload NPPS25.137-93-14 (which I downloaded through LMSA earlier) somewhere - however, it will take a "while" because my upload speed is quite poor.
Andrej_SK said:
As you have the latest Nougat firmware (NPPS25.137-93-14), use Lenovo Moto Smart Assistant (Rescue function, in dropdown menu choose "XT1670") to download it. Make sure, it offers you NPPS25.137-93-14 firmware to download, not an older one, which might brick your phone. If it offers you Oreo firmware (build number starts with letter "O" instead of "N"), you can use it to repair your phone too, but if you want to stay with Nougat one, let me know and I'll upload NPPS25.137-93-14 (which I downloaded through LMSA earlier) somewhere - however, it will take a "while" because my upload speed is quite poor.
Click to expand...
Click to collapse
Thank you man, Where do I go to get the Lenovo Moto Smart Assistant?(If I'm guessing right it is an online thing) If it has an official Oreo build for the g5, I'd like to use that because Oreo is great. Also is there a way to boot back into what I have now because I need to save some game stuff to their cloud services.
Oh and another thing, in the bootloader there is an option called factory mode. From what I've heard from you and what I know, that option factory resets the phone and I wont get my imei number erased? Because if that's an easier option to do, then install the official updates to Oreo from the android updater or whatever, I might want to do that instead.
And I'll stay with the Nougat for now I guess and I can update it myself later if I want.
EDIT#1: Okay so I went to the Lenovo site and tried to download the Smart Assistant but it downloaded a .7z file? I'm kinda confused about that
EDIT#2: Nevermind, since I reset my pc I never got winzip/rar again (Whups)
EDIT#3: Okay! So I got the rescue working after a few tried as it wouldn't do the target image thing. It's showing me CEDRIC_OPP28.85-13_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip, is this the right image? I know it's oreo because if the O, also I think its newer and it wont work? because the nougat is 25.137-93-13 and this is only 28.85-13. But it's showing that I could download it and use that. I think they would be right and I can try it
EDIT#4: Okay so I did some searching myself. Someone did it and it worked fine, their device structure is XT1676 but still had the name npps as me, and updated to the opp28.85-13. he was having problems installing and he said it wouldn't. People suggested to take out the sd card, he did it and the update worked properly because he had 2 partitions. One adopted memory and one portable. I did the same thing with my sd card and I think i should follow this, it is on the official lenovo forums so I think I will be safe.
Its okay man, I figured it out and I have my backup, so all my games are here and I'm on official 8.1 with a few system updates waiting for me lol
shAen123 said:
Thank you man, Where do I go to get the Lenovo Moto Smart Assistant?(If I'm guessing right it is an online thing) If it has an official Oreo build for the g5, I'd like to use that because Oreo is great. Also is there a way to boot back into what I have now because I need to save some game stuff to their cloud services.
Oh and another thing, in the bootloader there is an option called factory mode. From what I've heard from you and what I know, that option factory resets the phone and I wont get my imei number erased? Because if that's an easier option to do, then install the official updates to Oreo from the android updater or whatever, I might want to do that instead.
And I'll stay with the Nougat for now I guess and I can update it myself later if I want.
EDIT#1: Okay so I went to the Lenovo site and tried to download the Smart Assistant but it downloaded a .7z file? I'm kinda confused about that
EDIT#2: Nevermind, since I reset my pc I never got winzip/rar again (Whups)
EDIT#3: Okay! So I got the rescue working after a few tried as it wouldn't do the target image thing. It's showing me CEDRIC_OPP28.85-13_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip, is this the right image? I know it's oreo because if the O, also I think its newer and it wont work? because the nougat is 25.137-93-13 and this is only 28.85-13. But it's showing that I could download it and use that. I think they would be right and I can try it
EDIT#4: Okay so I did some searching myself. Someone did it and it worked fine, their device structure is XT1676 but still had the name npps as me, and updated to the opp28.85-13. he was having problems installing and he said it wouldn't. People suggested to take out the sd card, he did it and the update worked properly because he had 2 partitions. One adopted memory and one portable. I did the same thing with my sd card and I think i should follow this, it is on the official lenovo forums so I think I will be safe.
Click to expand...
Click to collapse
You can download LMSA from this site https://support.lenovo.com/sk/sk/downloads/ds101291.
"Factory Mode" doesn't factory reset your phone or install stock ROM at all. It just runs CQATest app and deny access to the cellular network (even it asks for PIN at boot, you will get "No signal" in the notification panel). After the normal reboot, CQATest app disappears and the cellular network works.
Oreo is newer than Nougat, so that's why there wasn't any problem flashing it. However, next time, if you're not sure which firmware is newer while comparing by build numbers (e.g. you're comparing two Nougat builds, each with different build number), look at the security patch.
Most probably, the problem what you've been reading about (updating while sdcard inserted) was made by the person, who just installed the update with his sdcard formatted as an adoptable memory (that means the sdcard expands the internal storage and behave as its part).
shAen123 said:
Its okay man, I figured it out and I have my backup, so all my games are here and I'm on official 8.1 with a few system updates waiting for me lol
Click to expand...
Click to collapse
So is your problem fully fixed now?
Andrej_SK said:
You can download LMSA from this site https://support.lenovo.com/sk/sk/downloads/ds101291.
"Factory Mode" doesn't factory reset your phone or install stock ROM at all. It just runs CQATest app and deny access to the cellular network (even it asks for PIN at boot, you will get "No signal" in the notification panel). After the normal reboot, CQATest app disappears and the cellular network works.
Oreo is newer than Nougat, so that's why there wasn't any problem flashing it. However, next time, if you're not sure which firmware is newer while comparing by build numbers (e.g. you're comparing two Nougat builds, each with different build number), look at the security patch.
Most probably, the problem what you've been reading about (updating while sdcard inserted) was made by the person, who just installed the update with his sdcard formatted as an adoptable memory (that means the sdcard expands the internal storage and behave as its part).
So is your problem fully fixed now?
Click to expand...
Click to collapse
Yes it is, I was able to boot and go through an update to give me the lastest security patch. After some downloading/backup retrieving my phone is working normally and I have my iemi and stuff. I might go and root it again at a later date but for now its going to be completely stock. Sorry for the long wait

Categories

Resources