HELP PLEASE! Phone bootlooping. Missing key ro.build info. - Moto G7 Power Questions & Answers

Moto G7 Power is missing ro.build.baseband, ro.build.fingerprint and ro.build.version.full all listed as not found when running getvar all command. Have flashed stock firmware multiple times. All flashes okay but neither fixes the bootloop or the missing info. I have been messing with Motorola phone for years now and never seen this before. Any help would be greatly appreciated. Thanks in advance.

eluallen said:
Moto G7 Power is missing ro.build.baseband, ro.build.fingerprint and ro.build.version.full all listed as not found when running getvar all command. Have flashed stock firmware multiple times. All flashes okay but neither fixes the bootloop or the missing info. I have been messing with Motorola phone for years now and never seen this before. Any help would be greatly appreciated. Thanks in advance.
Click to expand...
Click to collapse
U on stock rom or custom right now

Stock with locked bootloader. Was doing a standard update after it sat turned off for 7 months. I got it to try to boot but it said failed to load kennel. Can't get a boot image to flash now tho

Here's a picture of what the screen said the one time it tried to boot and failed.

eluallen said:
Stock with locked bootloader. Was doing a standard update after it sat turned off for 7 months. I got it to try to boot but it said failed to load kennel. Can't get a boot image to flash now tho
Click to expand...
Click to collapse
Locked bootloader is your problem.

Stock firmware can be flashed in a locked bootloader and it shouldn't have had any effect on the OTA. While LMSA won't flash because of missing info fastboot will flash it fine. I just wrote my own batch file to making flashing multiple times easier. All flashes end with okay but does nothing for the missing info.
I also figured out the issue with flashing the boot image. As long as they're not altered in any way the files will flash on locked bootloader.

eluallen said:
Stock firmware can be flashed in a locked bootloader and it shouldn't have had any effect on the OTA. While LMSA won't flash because of missing info fastboot will flash it fine. I just wrote my own batch file to making flashing multiple times easier. All flashes end with okay but does nothing for the missing info.
I also figured out the issue with flashing the boot image. As long as they're not altered in any way the files will flash on locked bootloader.
Click to expand...
Click to collapse
You are soft bricked u need blank flash file for carrier easy fix moto drivers qail com drivers and the right blank flash pc with terminalhttps://t.me/joinchat/MmtXRlRyFn498KnQGBsmyw. Go here

The link isn't working for me. How do I run the blank-flash batch file when I can't get to edl mode. Have functional fastboot so it won't go to edl. Can you run blank-flash.bat file in fastboot mode as well? And again I appreciate any and all help I get.

eluallen said:
The link isn't working for me. How do I run the blank-flash batch file when I can't get to edl mode. Have functional fastboot so it won't go to edl. Can you run blank-flash.bat file in fastboot mode as well? And again I appreciate any and all help I get.
Click to expand...
Click to collapse
IF you follow the link in post #7 when offered you will get the immediate help you need instead of piecemeal hours between answers help.

As I said in the next post that link isn't working when I try it. Sorry bud.
Simply says "sorry this post does not seem to exist".

As I said follow the link when it's offered. Sometimes the links don't work the next day.

eluallen said:
As I said in the next post that link isn't working when I try it. Sorry bud.
Simply says "sorry this post does not seem to exist".
Click to expand...
Click to collapse
https://t.me/joinchat/MmtXRlRyFn498KnQGBsmyw

Couldn't get the link to work from the LG phone I'm using. Once I got the Moto working it went to the link no problem. Only issue now is no IMEI. Flashing NON-LOS and fsg don't help Making an EDL cable to force boot to EDL mode. Fastboot command came back restricted command and did nothing. Maybe flashing from EDL will make a difference.

Couldn't get the link to work from the LG phone I'm using. Once I got the Moto working it went to the link no problem. Only issue now is no IMEI. Flashing NON-LOS and fsg don't help Making an EDL cable to force boot to EDL mode. Fastboot command came back restricted command and did nothing. Maybe flashing from EDL will make a difference.

eluallen said:
Couldn't get the link to work from the LG phone I'm using. Once I got the Moto working it went to the link no problem. Only issue now is no IMEI. Flashing NON-LOS and fsg don't help Making an EDL cable to force boot to EDL mode. Fastboot command came back restricted command and did nothing. Maybe flashing from EDL will make a difference.
Click to expand...
Click to collapse
U need blank flash for ur phone carrier

roadkill42 said:
U need blank flash for ur phone carrier
Click to expand...
Click to collapse
I didn't know the blank-flash files were carrier specific. How do you find out which carrier they are for? I have for PCOS29.114-134-2 but that number is used for multiple carriers. And when using edl cable is the phone supposed to be off to use it? If you've ever used that method.
Never mind about the phone needing to be off. Just found a video about using the cable that said it needs to be off.

You tell by the model number. For example, mine is XT1955-5 (MetroPCS).

fddm said:
You tell by the model number. For example, mine is XT1955-5 (MetroPCS).
Click to expand...
Click to collapse
If ur metro T-Mobile or on consumer celuiar u can use retus firmware less bloat

Related

LG ARISTO [LG M210 T mobile]

Hey guys! How ya doing?
Im pretty straightforward so I'll make this fast.(like myself in bed with a 10/10)
I need some help on my LG Aristo (T-Mobile).
The problem is I rooted it via fastboot with twrp and everything went great for the first few days until it started to flash gray and wanted to become an alien.
I wasn't worrying cause im a thug.
So I attempted a re-flash & I erased the recovery then re-flashed it.
Until the blinky gray alien screen started happening again.
For a few days I tried everything and the gray flashing screen wouldn't go away.
So I did the following fastboot commands and it went away.
Fastboot erase cache
Fastboot erase userdata
Fastboot erase system
Fastboot erase recovery
Satisfied that the gray flashing finally went away I reflashed it with the twrp recovery.
Only this time when I booted into twrp to install No-verity and SU all I seen was
Failed to mount :/system
Failed to mount :/userdata
Failed to mount :/recovery
And the phone did a reboot and was acting funny.
I then re-flashed the boot, recovery and the modem imgs that I extracted from the KDZ myself. And it actually booted but stays stuck at the LG Logo.
I couldn't flash the system img as I kept getting a "max target size download of 190840823 bytes" error.
I looked into it and a friend mentioned to forget it and to just flash the KDZ File with a LG flash tool.
I tried this only every flash tool I used did not pick up my device model. (yes I had all correct LG Drivers installed)
Aftering searching online I also tried to replace the fastboot exe with mfastboot. But it did not work as I keep getting the same error but it said target -max-download size of: 250mb and my system.img is about 2GB+..
Also, the mfastboot was made for moto devices (I found a XDA thread that linked it) and not lg. But it didn't work anyway.
I really think everything will be solved once I flash my system img but I keep getting errors about the size limit. (If you know of a way to fix this let me know.)
:good:I've already tried the following so please don't bring them up::good:
*Erasing everything via fastboot ( doesn't do anything)
*Putting phone into DL mode to flash KDZ and TOT file with phone dll via LG flash tools.(2014 and 2016) ( kept getting a (s) failed to load error)
*Re-flashed stock imgs (done it all but system img. I don't know why It keeps giving errors, yes I put it in android sdk platform tools folder)
* Put phone in dl mode and use LGUP/uppercut method. ( Kept getting "No handsets connected" errors". Phone wasn't recognized no matter what drivers I used.)
*Try different ports on pc and latest drivers. ( Yeah, I spent a week searching for all drivers and my pc isnt a virgin anymore as I stuck in the usb in all her holes)
*Relentlessly search XDA and other forums for solutions to no prevail. (This phone is irrelevant and no one cares about it)
:good:What I haven't tried::good:
*Breaking the mother****er and just buying a s5.
Greatly appreciate any help and also can XDA add the LG Aristo to the "my devices"? I had to pick a s8 so I didn't look broke.:silly:
I didn't seen an LG Aristo and There is NO forums for this problem or even for this phone in that matter.
Confxsed said:
I really think everything will be solved once I flash my system img but I keep getting errors about the size limit. (If you know of a way to fix this let me know.)
Click to expand...
Click to collapse
No one has a fix for this?
Dayuuum
Fuuu, that's hardcore.
Where is the dang lg m210 developers section? It's a very popular device and there is a ton of interest in rooting it. I can't seem to find the device thread here on XDA. ..
Sent from my SM-N910T using XDA-Developers Legacy app
Are you trying to root it? I can give you the twrp for the device and such and a rooting method. I rooted mine successfully its just I think I messed it up by stepping on it lmao
how did u root it
1118niranjan said:
how did u root it
Click to expand...
Click to collapse
I would post a link but I cant. Just google it and look for the getandroidtips website. I rooted it by working with friends on android forums. But that website getandroidtips has a better understanding.
Confxsed said:
I would post a link but I cant. Just google it and look for the getandroidtips website. I rooted it by working with friends on android forums. But that website getandroidtips has a better understanding.
Click to expand...
Click to collapse
pm then
Need some to dump the firmware of LG M210.
Now i have LG UP tool to dump all partitions from LG M210, But i need to find a working LG M210 phone.
Also, if anyone who need to bypass LG M210 Goolge FRP can PM me, Let me try the Chip erase feature on LG UP
---------- Post added at 12:04 PM ---------- Previous post was at 12:02 PM ----------
Confxsed said:
No one has a fix for this?
Click to expand...
Click to collapse
I think the chip erase feature on LG UP can fix the issue you mentioned, after erase the chip, flash kdz firmware with LG UP tool.
But the chip erase feature do erase IMEI information too..
---------- Post added at 12:04 PM ---------- Previous post was at 12:04 PM ----------
Confxsed said:
No one has a fix for this?
Click to expand...
Click to collapse
I think the chip erase feature on LG UP can fix the issue you mentioned, after erase the chip, flash kdz firmware with LG UP tool.
But the chip erase feature do erase IMEI information too..
if you like to try, PM me and let us works together on teamviewer to fix it.
Confxsed said:
Are you trying to root it? I can give you the twrp for the device and such and a rooting method. I rooted mine successfully its just I think I messed it up by stepping on it lmao
Click to expand...
Click to collapse
Think I could get a copy of rhythm twrp not root method
frp lock
i bought this phone from a pawn shop for cheap but i find out im frp locked out.. how can i get passed this?
Use Uppercut with MS210 Firmware Typically, if you can't get LG Bridge to recognize device you should pull the battery out with the cable disconnected, reinstall the batter and then hold the Volume Up button and then plug the USB cable in while it's connected to yuor PC. Welcome to the miserable world of LG
Any solution for frp lg ms210?
Has anyone had any luck unlocking this phone?I would like to switch from T-mobile to Freedompop.
Confxsed said:
Hey guys! How ya doing?
Im pretty straightforward so I'll make this fast.(like myself in bed with a 10/10)
I need some help on my LG Aristo (T-Mobile).
The problem is I rooted it via fastboot with twrp and everything went great for the first few days until it started to flash gray and wanted to become an alien.
I wasn't worrying cause im a thug.
So I attempted a re-flash & I erased the recovery then re-flashed it.
Until the blinky gray alien screen started happening again.
For a few days I tried everything and the gray flashing screen wouldn't go away.
So I did the following fastboot commands and it went away.
Fastboot erase cache
Fastboot erase userdata
Fastboot erase system
Fastboot erase recovery
Satisfied that the gray flashing finally went away I reflashed it with the twrp recovery.
Only this time when I booted into twrp to install No-verity and SU all I seen was
Failed to mount :/system
Failed to mount :/userdata
Failed to mount :/recovery
And the phone did a reboot and was acting funny.
I then re-flashed the boot, recovery and the modem imgs that I extracted from the KDZ myself. And it actually booted but stays stuck at the LG Logo.
I couldn't flash the system img as I kept getting a "max target size download of 190840823 bytes" error.
I looked into it and a friend mentioned to forget it and to just flash the KDZ File with a LG flash tool.
I tried this only every flash tool I used did not pick up my device model. (yes I had all correct LG Drivers installed)
Aftering searching online I also tried to replace the fastboot exe with mfastboot. But it did not work as I keep getting the same error but it said target -max-download size of: 250mb and my system.img is about 2GB+..
Also, the mfastboot was made for moto devices (I found a XDA thread that linked it) and not lg. But it didn't work anyway.
I really think everything will be solved once I flash my system img but I keep getting errors about the size limit. (If you know of a way to fix this let me know.)
:good:I've already tried the following so please don't bring them up::good:
*Erasing everything via fastboot ( doesn't do anything)
*Putting phone into DL mode to flash KDZ and TOT file with phone dll via LG flash tools.(2014 and 2016) ( kept getting a (s) failed to load error)
*Re-flashed stock imgs (done it all but system img. I don't know why It keeps giving errors, yes I put it in android sdk platform tools folder)
* Put phone in dl mode and use LGUP/uppercut method. ( Kept getting "No handsets connected" errors". Phone wasn't recognized no matter what drivers I used.)
*Try different ports on pc and latest drivers. ( Yeah, I spent a week searching for all drivers and my pc isnt a virgin anymore as I stuck in the usb in all her holes)
*Relentlessly search XDA and other forums for solutions to no prevail. (This phone is irrelevant and no one cares about it)
:good:What I haven't tried::good:
*Breaking the mother****er and just buying a s5.
Greatly appreciate any help and also can XDA add the LG Aristo to the "my devices"? I had to pick a s8 so I didn't look broke.:silly:
I didn't seen an LG Aristo and There is NO forums for this problem or even for this phone in that matter.
https://www.youtube.com/watch?v=
Click to expand...
Click to collapse
Upssss, may be too late but... Did you find a solution for your issue?
I'm going to break this M*****F*****
can someone make a damn video guide to firmware rebooting this damn phone I'm going through hell Z.Z
DarkKingKiyo said:
can someone make a damn video guide to firmware rebooting this damn phone I'm going through hell Z.Z
Click to expand...
Click to collapse
What is the exact issue?
What did you do that cause the trouble?
What have you already test to fix this problem?
can plzz share how you root the lgm210..really some help rooting my device
can plzz share how you root the lgm210..really some help rooting my device
Shatrel said:
can plzz share how you root the lgm210..really some help rooting my device
Click to expand...
Click to collapse
https://messi2050.blogspot.com/2017/02/root-twrp-v3-for-lg-aristo-metropc-t.html?m=1
Pretty sure applies to Tmo and Metro
wamz100 said:
Think I could get a copy of rhythm twrp not root method
Click to expand...
Click to collapse
I need a twrp backup .zip file for this phone. I accidentally wiped my system

One Plus 7 Pro 5G UK - Bricked PLIS HELP.

Yep, thats right, another thread about a bricked OPO
I made the mistake of deciding to unlock bootloader, flash TWRP and run a custom rom, after about 10 minutes of being awake.
Long story short, my device is now stuck in bootloop. I have no recovery on the device anymore, not even stock OPO, and obviously no rom.
I belive this is because i ran the fastboot command, 'fastboot flash boot twrp.img' instead of 'fastboot boot twrp.img' either way....
Device will boot into fastboot, and I THINK, it boots into EDL. The device shows in device manager, and in MSM software, but there is no notice on the screen of the device.
I have tried to get back up and running using both methods below to no joy.
Flashing
https://forum.xda-developers.com/oneplus-7-pro/how-to/rom-stock-fastboot-roms-oneplus-7-pro-t3931424
MSM
https://forum.xda-developers.com/oneplus-7-pro/how-to/op7pro-collection-unbrick-tools-t3956595
On the back of my device, there is a sticker, which displays my IMEI number, Serial etc etc, and shows the model of my device being GM1920, a model number I see no where in this forum. So now I'm thinking, "Do I have a device thats not compatable with all this, all i see is GM21AA, GM21AB etc etc.
Some body please give me something to go off, I've had android devices for 10+ years and have never managed to brick a phone into non exsistance. I can provide as much detail as you would like, anything that would help you to help me.
Check your pms
Whoareyou said:
Check your pms
Click to expand...
Click to collapse
Heya, Ive checked em.
I've managed to fix the issue now, as you probably know, I was being a derp, and just not getting the right varient of fastboot rom for my device, I just didnt have my head screwed on properly lol. Anyway, the device works, I have stock rom, recovery, phone boots into EDL and displays the message as it should, everythings working right. Just need to get TWRP flashed and get a custom rom running now.
Appreciate your reply!! Can I still join in telegram? Would be nice to be in a community with GM1925/GM1920 users.
jkebwdn said:
Heya, Ive checked em.
I've managed to fix the issue now, as you probably know, I was being a derp, and just not getting the right varient of fastboot rom for my device, I just didnt have my head screwed on properly lol. Anyway, the device works, I have stock rom, recovery, phone boots into EDL and displays the message as it should, everythings working right. Just need to get TWRP flashed and get a custom rom running now.
Appreciate your reply!! Can I still join in telegram? Would be nice to be in a community with GM1925/GM1920 users.
Click to expand...
Click to collapse
Please do!
im having the same issue but im stuck in bootloader, unable to flash firmware through fastboot and cant find msm tool for 1920 variant.
stevoswifty said:
im having the same issue but im stuck in bootloader, unable to flash firmware through fastboot and cant find msm tool for 1920 variant.
Click to expand...
Click to collapse
https://forum.xda-developers.com/on...o-5g-eu-unbrick-tool-to-restore-t4078827/amp/
Whoareyou said:
https://forum.xda-developers.com/on...o-5g-eu-unbrick-tool-to-restore-t4078827/amp/
Click to expand...
Click to collapse
I have sorted it now bud but still can't flash ROMs first phone I haven't managed it on in years ha.

NV Backup Warning - Dynamic partition invalid. Quite the riddle.

UPDATE: So hopefully this title and OP update take as I don't want to spam the forum with threads. Despite have dozens of Android phones since the original G1 I am stumped by this, but I imagine a guru could solve this puzzle. Here we go:
I messed up my phone partition table when I messed up the last step from the dual boot TWRP thread. I tried fixing my newly bricked phone using MSM tools but it's a converted GM1915 Tmobile OP7P running global firmware. The Tmobile stock MSM recovery pack MEGA link has gone dead, so I tried the Tmo to Int'l conversion files again. The phone booted, but I kept getting "NV Backup warning - dynamiic partition is invalid". I could make calls, but had no orientation sensor, no mobile data, baseband shows blank in fastboot mode, etc. I've tried flashing fastboot ROMs as well but no matter what, the dynamic partition invalid message pops up.
It seems ike this is an EFS issue, so late last night I tried a few more things. IIRC, I was able to flash that persist.img via "fastboot flash persist persist.img", and in any case most everything seems to work now, including the sensors. But, I'm still getting that dynamic partition invalid error and no baseband shows on my bootloader screen. I
'm guessing there's still some corruption in EFS? I'd understood from reading that even with persist.img one good thing was to erase the modem files and persist first, because then they will regenerate, according to this post.
So, I tried these commands with plans to then flash persist.img again....
fastboot erase modemst1
fastboot erase modemst2
fastboot erase persist
It won't let me erase them though, as it says the critical partitions are locked. Do you think this path might fix whatever issue is triggering this message, and if so, does anyone know how to do it? I think I may have use dd, but I'm not sure which partitions I'll be looking to erase and how to do it that way, either.
Maybe try this: https://forum.xda-developers.com/oneplus-7-pro/how-to/rom-stock-fastboot-roms-oneplus-7-pro-t3931424
¿GotJazz? said:
Maybe try this: https://forum.xda-developers.com/oneplus-7-pro/how-to/rom-stock-fastboot-roms-oneplus-7-pro-t3931424
Click to expand...
Click to collapse
Thanks, but that's what I've been trying. No joy so far. I need to check because actually it may have hung on params or some other issue that an L2 driver update could fix. Of course me figuring out how to fix that will be the next feat, LOL.
Updated thread title and OP with new info. Phone almost back to 100%, but still getting an error message.
So another update as I learn. Now that I've gotten TWRP and Magisk back on it, I realized there is another odd thing with the phone now. Just before the bootloader unlocked warning screen, for a fraction of a second there's a message that says SMT Download Failed. More reading seems to suggest that using an SMT recovery in conjunction with MSM tool can fix the SMT Download Failed message. Most of these say you need to have an EFS backup, which some suggest that you can wipe EFS (as indicated in OP) and it will regenerate.
I've taken a TWRP backup of EFS, but I'm not sure whether I should proceed with the wipe processes with so many saying you should have an EFS backup (lesson learned, yes you should - and don't delete/misplace it like I did). Anyway, I'm wondering if going through that process might resolve that, as it could be a flag that didn't get set right, or whether or not there's some issue with my EFS that means my backup from the current state is worthless.
Maybe my EFS isn't corrupt after all, maybe it was the persist.img that needed to fix the sensores and now I'm good except for some flag that's triggering the SMT Download Failed message and the subesquent dynamic partition invalid message?
Maybe you could do that on twrp by terminal commands, some fastboot command dont work on Bootloader but in twrp work
yulian6766 said:
Maybe you could do that on twrp by terminal commands, some fastboot command dont work on Bootloader but in twrp work
Click to expand...
Click to collapse
That's actually an idea I was kicking around for my next move. I was hoping that before I do that, though, I could get a sense from one of the gurus as to whether I'll be able to recover my IMEI and such afterwards.
vettejock99 said:
That's actually an idea I was kicking around for my next move. I was hoping that before I do that, though, I could get a sense from one of the gurus as to whether I'll be able to recover my IMEI and such afterwards.
Click to expand...
Click to collapse
Your problem is recover your IMEI?
yulian6766 said:
Your problem is recover your IMEI?
Click to expand...
Click to collapse
The phone shows IMEI right now, and calls and mobile data work, so except for the weird " SMT download failed!!! please check your download flow is right" message at boot start and the NV Backup UI warning Dynamic partiton invalid messages the phone otherwise seems just fine. I'm pretty comfortable with system, boot, and data partition stuff from all my time at this, but I'm just being extra cautious that by erasing my modems via some sort of commands or SMT flash that I can at least get it back to where it is now even if I can't get back to an error-free state.
Have you tried flashing QCN file?
yulian6766 said:
Have you tried flashing QCN file?
Click to expand...
Click to collapse
I had heard about and used QPST before, but QCN is new to me. I did a quick search and it sounds like on some phones like ASUS ROG, you REALLY need to have one to recover from erasing your modems. Oneplus phones recreate those if they are erased, don't they?
Create a QCN backup from QPST of your phone and flash it again, maybe that will fix your problem.
Hey man I know I posted the other one up with the issue too but thanks for this after seeing you flashing the persist fixed your sensors I tried and walla they are good now! I still have the same SMT failed and NV Backup warning but at least the phone can auto rotate.
Velrix said:
Hey man I know I posted the other one up with the issue too but thanks for this after seeing you flashing the persist fixed your sensors I tried and walla they are good now! I still have the same SMT failed and NV Backup warning but at least the phone can auto rotate.
Click to expand...
Click to collapse
Good stuff. I'll definitely post a resolution here if I get it all. Just glad to have the phone working again for sure!
yulian6766 said:
Create a QCN backup from QPST of your phone and flash it again, maybe that will fix your problem.
Click to expand...
Click to collapse
I went and installed QPST again and I can get it to see the phone in EDL mode, but I don't believe I have the drivers to get it into diagostnic mode. If I try it shows GM1915 with unknown USB drivers, but I've downloaded some and they don't seem to be able to get the device recognized properly. Until I figure that out, I can't pull QCN, I don't think.
I did go ahead and try a SMT flash. Unfortunately, while I've gotten it to start, it ultimately gets to "Param preload" then I see the Status of Connection change to N/A and then it just hangs....grrrr...
vettejock99 said:
I went and installed QPST again and I can get it to see the phone in EDL mode, but I don't believe I have the drivers to get it into diagostnic mode. If I try it shows GM1915 with unknown USB drivers, but I've downloaded some and they don't seem to be able to get the device recognized properly. Until I figure that out, I can't pull QCN, I don't think.
Click to expand...
Click to collapse
You have to install the right drivers
https://forum.xda-developers.com/rog-phone-2/how-to/guide-restoring-imei-efs-erasing-t4071159
This drivers should work for me
yulian6766 said:
You have to install the right drivers
https://forum.xda-developers.com/rog-phone-2/how-to/guide-restoring-imei-efs-erasing-t4071159
This drivers should work for me
Click to expand...
Click to collapse
That's the one I was using. Just downloaded and compared the hashes. Now that I think about it, I chose WWAN-DHCP mode. Should I have chosen ETHERNET-DHCP?
vettejock99 said:
That's the one I was using. Just downloaded and compared the hashes. Now that I think about it, I chose WWAN-DHCP mode. Should I have chosen ETHERNET-DHCP?
Click to expand...
Click to collapse
I choose the same option
yulian6766 said:
I choose the same option
Click to expand...
Click to collapse
So if we're both choosing WWAN-DHCP for the driver mode, I'm not sure why it wouldn't work. Right now everything is working and I told the NV Backup UI notification to Never Show so it will probably be a few days before I get around to trying to get the whole thing to flash properly. My OCD is really the only thing that would drive me to do it

Question Is unbricking possible?

Good morning all, I tried relocking my bootloader using the command "fastboot oem asus-csc lk" and at first, it seemed to be a success. However I restarted my device and was met with this error message. "Your device is corrupt. It can't be trusted and will not boot." I've tried searching high and low and it seems that I'm royally screwed, just wanted to confirm that I was though. Thanks for reading my post and any input is appreciated.
If your boot.img is not stock before locking you will get this error. Try flashing stock boot.img. I had a similar experience with realme phone but not encountered this issue with ROG 5
Edit: Sorry since you locked the bootloader i think you cant flash it unless you unlock it again. Give a try with EDL firmware
This is becoming a pretty common issue. I think it's time we make a WARNING thread.
WARNING: Read BEFORE Locking Bootloader
DO NOT LOCK THE BOOTLOADER WHILE ROOTED! When locking the bootloader while rooted, the boot image will fail verification and the system will fail to boot. You cannot flash a stock boot image with a locked bootloader. Locking the bootloader will...
forum.xda-developers.com
jhosharath said:
If your boot.img is not stock before locking you will get this error. Try flashing stock boot.img. I had a similar experience with realme phone but not encountered this issue with ROG 5
Edit: Sorry since you locked the bootloader i think you cant flash it unless you unlock it again. Give a try with EDL firmware
Click to expand...
Click to collapse
How would I go about doing that? If you don't mind telling me of course. I've tried doing some research on it but it seems there isn't much on this phone at all
Jdotswift said:
How would I go about doing that? If you don't mind telling me of course. I've tried doing some research on it but it seems there isn't much on this phone at all
Click to expand...
Click to collapse
ROG Phone 5(s) Help Index
"Quick Filters" let you see all posts of a certain type. This can make finding posts easier, but what if a guide began as a "Question"? This thread aims to bridge that gap. You will find nearly all of the common things new owners are trying to...
forum.xda-developers.com
twistedumbrella said:
ROG Phone 5(s) Help Index
"Quick Filters" let you see all posts of a certain type. This can make finding posts easier, but what if a guide began as a "Question"? This thread aims to bridge that gap. You will find nearly all of the common things new owners are trying to...
forum.xda-developers.com
Click to expand...
Click to collapse
Thanks for your help so far but I'm having issues putting the phone into edl mode. I'm trying to follow what was suggested in the tutorial but it isn't working. I also tried the fastboot command that was done in the video and to no avail. Google isn't giving much either. Am I missing something?
Edit: Made it into Edl mode but when trying to flash the ww image folder, I'm met with an error message saying "Object reference not set to an instance of an object". It seems like there is no fix for this at the moment
Jdotswift said:
Thanks for your help so far but I'm having issues putting the phone into edl mode. I'm trying to follow what was suggested in the tutorial but it isn't working. I also tried the fastboot command that was done in the video and to no avail. Google isn't giving much either. Am I missing something?
Edit: Made it into Edl mode but when trying to flash the ww image folder, I'm met with an error message saying "Object reference not set to an instance of an object". It seems like there is no fix for this at the moment
Click to expand...
Click to collapse
That's likely because the bootloader is locked. It was possible that EDL mode could still allow a full restore, but also quite possible it wasn't going to work because of that.
twistedumbrella said:
That's likely because the bootloader is locked. It was possible that EDL mode could still allow a full restore, but also quite possible it wasn't going to work because of that.
Click to expand...
Click to collapse
Well thanks for your help. I admit defeat but learned a very valuable lesson
Jdotswift said:
Well thanks for your help. I admit defeat but learned a very valuable lesson
Click to expand...
Click to collapse
You may still want to contact Asus and tell them you don't know what happened. They may be able to restore it. I wouldn't tell them you unlocked the bootloader, since it's locked if they ask.
As long as bootloader mode works, You can flash a RAW file to boot the phone back.
Ensure the phone has enough battery power left for a 20 min+ flash,
USB Cable to be connected on the side port, (not bottom charging port - fastboot doesn't work there)
and to use the exact raw firmware file which matches the device model and variant.
Latest WW Raw file is here
JazonX said:
As long as bootloader mode works, You can flash a RAW file to boot the phone back.
Ensure the phone has enough battery power left for a 20 min+ flash,
USB Cable to be connected on the side port, (not bottom charging port - fastboot doesn't work there)
and to use the exact raw firmware file which matches the device model and variant.
Latest WW Raw file is here
Click to expand...
Click to collapse
Hopefully this time is different, but every report so far has been that it fails. I believe we still need the firehose to use any programs that override the bootloader security on fastboot.
twistedumbrella said:
Hopefully this time is different, but every report so far has been that it fails. I believe we still need the firehose to use any programs that override the bootloader security on fastboot.
Click to expand...
Click to collapse
Can confirm it one hundred percent works. Mine was the American variant purchased directly from Asus' website. I don't think that had anything to do with it but my phone is up and running with a locked bootloader now. I really appreciate the help fellas
Jdotswift said:
Can confirm it one hundred percent works. Mine was the American variant purchased directly from Asus' website. I don't think that had anything to do with it but my phone is up and running with a locked bootloader now. I really appreciate the help fellas
Click to expand...
Click to collapse
Glad to hear it. Apparently, the issue was people not following instructions...

OnePlus 8 TMO Missing IMEI and can't unlock bootloader

Hey yall, I really need some help.
So some back story:
I started using a oneplus 8 TMO version and wanted to unlock the bootloader to get android 12 and root the phone. So I went through the process of getting an unlock token and when I finally got it, unlocked my bootloader, flashed the global version of oxygen os, and got it updated to android 12. Everything was working great. So then I wanted to root the phone so I downloaded twrp, booted into fastboot, and tried flashing it. The phone then booted into the system even though I told it to boot into recovery. After about a minute or so it froze and rebooted into a kernal panic. I unfortunately do not have what it said and cant repeat the process, but it booted into recovery and I clicked reason for boot and it said something about the kernal. So after a reboot it then went into crash dump mode. So I had to use the msm download tool (unfortunately I only had the tmo msm version and thought I could just repeat the process because I had slow internet and didnt want to download the global msm tool) to get the phone working again. So booted into edl mode, reflashed the phone, and it booted up. The problem now is that I do not have an IMEI number. I have a wifi address, bt address, and everything else that makes me assume that the efs partition is still ok (but I dont know enough to debate that) but it does not recognize my sim card. The phone also freezed and restarts approximately every 30 seconds.
And now my problem and what I have tried:
Because I have no IMEI I cannot enable oem unlocking in developer settings, cant flash anything in the bootloader - including the unlock token - and can barely do anything in the system because it only stays on for small amounts of time. I have tried many imei write tools such as qualcomm smartphone write imei, readnwrite tool, fastboot imei writer, miracle box, and I think some others but none of them recognize my phone. Ive also tried the oneplus debloat and oem unlock script to try and bypass the setting but it didnt do anything. I have dialed *#801# and was able to enable engineering mode and diag toggle but it still didnt do anything for me. So I really dont know what to do any more. When in the bootloader or recovery the phone does not reboot, so I can stay there as long as I need. Any help on this would be greatly, greatly, greatly appreciated.
Have you tried using the MSMTool again?
Xryphon said:
Have you tried using the MSMTool again?
Click to expand...
Click to collapse
Yeah unfortunately that hasn't worked... I've done it miltiple times with the T-Mobile one and can't use any other one because I don't have an unlocked bootloader... If I had a way to bypass the oem unlocking option in the settings then I might have a chance to fix it but don't know how to do that...
try using this version of msmtool(i use MsmDownloadTool V4.0_Win7 on windows 10). it's a bit newer version(5.2.89) i extracted from OP9Pro file. replace the version from whichever unbrick file you download. worked for me. but don't upgrade to android 12 again, the same issue will happen
gingerboy92 said:
try using this version of msmtool(i use MsmDownloadTool V4.0_Win7 on windows 10). it's a bit newer version(5.2.89) i extracted from OP9Pro file. replace the version from whichever unbrick file you download. worked for me. but don't upgrade to android 12 again, the same issue will happen
Click to expand...
Click to collapse
Thanks for the response! And I am so sorry but what do you mean by unbrick file? I just had to download the tmobile version of the msm tool. I mean to be fair it was uploaded by someone so they probably pre programmed it but I unfortunately dont have the knowledge for that. I am also using msmdownloadtool v4.0. Do you happen to have the links to what you are referring to?
Heres the link to the one that I have downloaded: https://forum.xda-developers.com/t/...l-to-restore-your-device-to-oxygenos.4093043/
Thanks!
EDIT: so once you said that I actually went to the link and there were various versions. So I tried another one and it didn't work but then tried one more and my IMEI was back! I have no idea why that happened but thanks for the idea! I was so happy.
shubbyshoes said:
Thanks for the response! And I am so sorry but what do you mean by unbrick file? I just had to download the tmobile version of the msm tool. I mean to be fair it was uploaded by someone so they probably pre programmed it but I unfortunately dont have the knowledge for that. I am also using msmdownloadtool v4.0. Do you happen to have the links to what you are referring to?
Heres the link to the one that I have downloaded: https://forum.xda-developers.com/t/...l-to-restore-your-device-to-oxygenos.4093043/
Thanks!
EDIT: so once you said that I actually went to the link and there were various versions. So I tried another one and it didn't work but then tried one more and my IMEI was back! I have no idea why that happened but thanks for the idea! I was so happy.
Click to expand...
Click to collapse
yeah, that's it. it's related to version of msmdownloadtool. some of them must have a newer version. i had the idea from someone else on this forum too. glad it helps. be careful not upgrade to android 12 for now. i think it's because of the way oos12 detects phone varient causing the modem to go crazy. not sure tho. would love to see someone figures it out
gingerboy92 said:
yeah, that's it. it's related to version of msmdownloadtool. some of them must have a newer version. i had the idea from someone else on this forum too. glad it helps. be careful not upgrade to android 12 for now. i think it's because of the way oos12 detects phone varient causing the modem to go crazy. not sure tho. would love to see someone figures it out
Click to expand...
Click to collapse
Yeah, OOS 12 messed up my phone for a bit until I was able to get OOS 11 back on both slots.
shubbyshoes said:
Thanks for the response! And I am so sorry but what do you mean by unbrick file? I just had to download the tmobile version of the msm tool. I mean to be fair it was uploaded by someone so they probably pre programmed it but I unfortunately dont have the knowledge for that. I am also using msmdownloadtool v4.0. Do you happen to have the links to what you are referring to?
Heres the link to the one that I have downloaded: https://forum.xda-developers.com/t/...l-to-restore-your-device-to-oxygenos.4093043/
Thanks!
EDIT: so once you said that I actually went to the link and there were various versions. So I tried another one and it didn't work but then tried one more and my IMEI was back! I have no idea why that happened but thanks for the idea! I was so happy.
Click to expand...
Click to collapse
which worked for you?

Categories

Resources