I'm attempting to fix a OP7P I've had laying around for a while, but I am having trouble getting it to boot anything. It does boot into fastboot and EDL but the bootloader is locked, and any attempts I've made to revert the firmware with the MSM Tool doesn't get me past the OnePlus logo with the "Powered by Android" blurb at the bottom. I've both tried the stock T-Mobile MSM Tool and the method to convert to international, but neither booted. I'm posting here with the hope that someone has any ideas on what's going on and how I might go about fixing it. I can't quite remember if I had done any modifications in the past either, but I don't believe I had since I didn't use it for very long at all.
deltajordan said:
I'm attempting to fix a OP7P I've had laying around for a while, but I am having trouble getting it to boot anything. It does boot into fastboot and EDL but the bootloader is locked, and any attempts I've made to revert the firmware with the MSM Tool doesn't get me past the OnePlus logo with the "Powered by Android" blurb at the bottom. I've both tried the stock T-Mobile MSM Tool and the method to convert to international, but neither booted. I'm posting here with the hope that someone has any ideas on what's going on and how I might go about fixing it. I can't quite remember if I had done any modifications in the past either, but I don't believe I had since I didn't use it for very long at all.
Click to expand...
Click to collapse
It stuck on logo ?
This is what the screen looks like that it's stuck on. Does this for both recovery and system. (Not my phone, just an example image)
deltajordan said:
I'm attempting to fix a OP7P I've had laying around for a while, but I am having trouble getting it to boot anything. It does boot into fastboot and EDL but the bootloader is locked, and any attempts I've made to revert the firmware with the MSM Tool doesn't get me past the OnePlus logo with the "Powered by Android" blurb at the bottom. I've both tried the stock T-Mobile MSM Tool and the method to convert to international, but neither booted. I'm posting here with the hope that someone has any ideas on what's going on and how I might go about fixing it. I can't quite remember if I had done any modifications in the past either, but I don't believe I had since I didn't use it for very long at all.
Click to expand...
Click to collapse
Use my boot image and intro post here
Post in thread 'urgent: oneplus 7 pro TWRP bootloop' https://forum.xda-developers.com/t/urgent-oneplus-7-pro-twrp-bootloop.4413775/post-86554665.
Related
Hello, I've bricked my device (( moto g xt1032, I bought the device from Tesco back in 2013 and I just wanted to get the lollipop update on my phone, I looked online and found this video: watch?v=-L44JqysUy8 it didnt do as intended it rebooted and my device was ok, so I looked again and came accross a thread here on XDA: http://forum.xda-developers.com/moto-g/general/gpe-ota-lrx21z-5-0-1-xt1033-xt1032-t2969847
first mistake I made was doing step 2.1 instead of going straight to 2.2, my phone rebooted and got stuck in a boot loop (i think, it was a black powered by android screen) I looked on google yet again and found an article that told to clear the cache in recovery I did that and it didnt work, boot loop again, then I found a forum post saying that having bluestacks on your machine will cause a conflict I uninstalled that and started from scratch with the same problem, I re did the steps seen in the above youtube video thinking that would put my device back to normal and still stuck in bootloop with the blue motorola m logo, I cant enter recovery of the fast boot menu anymore and my battery doesnt seem to be charging, its essentially a paperweight.
paulh2k8 said:
Hello, I've bricked my device (( moto g xt1032, I bought the device from Tesco back in 2013 and I just wanted to get the lollipop update on my phone, I looked online and found this video: watch?v=-L44JqysUy8 it didnt do as intended it rebooted and my device was ok, so I looked again and came accross a thread here on XDA: http://forum.xda-developers.com/moto-g/general/gpe-ota-lrx21z-5-0-1-xt1033-xt1032-t2969847
first mistake I made was doing step 2.1 instead of going straight to 2.2, my phone rebooted and got stuck in a boot loop (i think, it was a black powered by android screen) I looked on google yet again and found an article that told to clear the cache in recovery I did that and it didnt work, boot loop again, then I found a forum post saying that having bluestacks on your machine will cause a conflict I uninstalled that and started from scratch with the same problem, I re did the steps seen in the above youtube video thinking that would put my device back to normal and still stuck in bootloop with the blue motorola m logo, I cant enter recovery of the fast boot menu anymore and my battery doesnt seem to be charging, its essentially a paperweight.
Click to expand...
Click to collapse
im now back to the boot loop thing not much better lol, is it fixable or should i just not bother
If it is booting up, then probably it is soft bricked. Not hard bricked.
If it can detect in ADB, re-flash the recovery?
Thankyou both for your replies, I dont know why I bothered back in the day symbian was so much easier lol, im an absolute noob when it comes to this so how would i go about getting to the recovery you mention, i can get to the fastboot menu but after selecting recovery the phone just loops at the boot logo
SInce it is bootlooping, I'm not sure which ROM is currently on your phone.
Try and flash the recovery from the ROM you tried to install by finding the recovery.img file, boot the phone into fastboot, and type "fastboot flash recovery recovery.img" or, if using mfastboot commands, type "mfastboot flash recovery recovery.img".
If you can't get into recovery, flash the recovery from your original ROM.
If you still can't get into recovery, flash your stock ROM, one partition at a time.
In fastboot, which bootloader version is on your phone?
the last thing I flashed was the link provided in the youtube vdeo if that helps, ive done the recovery thing and it still loops, my bootloader hmm im not sure heres the details from the fast boot screen..
AP Fastboot Flash Mode (S)
41.13 (sha-7dc8e78, 2014-06-16 16:33:29)
Device is locked Status Code (0)
is it because my bootloader is locked, I fail
You need to unlock your bootloader via the motorola website.
Thanks for your reply it turns out its not eligible for unlock for some reason so I'm deciding its a decent paper weight and giving up, I really appreciate the replies and the time the posters have taken out to help, I'll know to take my time to read every detail if I decide to do this again, thankyou!!
Are you sure it's not eligible? I thought my Telus xt1032 was not eligible but it turns out I mistyped a couple of numbers.
I tried a few hours later and I got the code from Motorola.
audit13 said:
Are you sure it's not eligible? I thought my Telus xt1032 was not eligible but it turns out I mistyped a couple of numbers.
I tried a few hours later and I got the code from Motorola.
Click to expand...
Click to collapse
I copied and pasted direct from the cmd, I read on another forum that you needed to be logged into the phone with the Motorola account which I didn't
I don't recall logging into the phone, I just recall logging into the Moto site with a google ID.
Don't worry bro just try and you will be successful. I'm also bricked my Micromax Canvas A1 on first try.
audit13 said:
I don't recall logging into the phone, I just recall logging into the Moto site with a google ID.
Click to expand...
Click to collapse
Thanks ill try it again
lol i need to wake up, I had spaces when iIcopied from the cmd its working now... and I have the code!!!
and im unlocked ! so what do i do know, i dont want to ruin it all now
Excellent. Boot into fastboot and post your bootloader version. It should be 41.xx.
41.13 ? thats on the second line in the boot menu
You have a KK bootloader. I suggest downloading the stock 4.4.4 ROM for your carrier and flash everything except the gpt and motoboot file. Once you finish flashing all partitions via fastboot, use the phone's volume button to boot into recovery, wipe perform a full wipe, and reboot.
So, i`m pretty sure my phone is hard bricked.
I was running with it for several months with no issues, so today i decided to flash EK 1.15 and then rebooted my phone, but instead of booting it went to CrashDump Mode and i can`t get it to boot or enter fastboot.
I`ve tried to use MSMtool but to software does not recognize my phone and on the device manager it shows as `Qualcomm HS-USB Diagnostics 900E`, on the CrashDump it shows `Could Not Decompress Initial ramdisk image.rd_load_disk`.
I`m opening a ticket with OnePlus, but as i live in Brazil and this phone was imported i think i`m fu****
Does anybody had this problem or knows if it is indeed a hardbrick?
So looks like i was trying to enter fastboot the wrong way...
I was able to boot into fastboot and then booted from there the TWRP image and then flash the stock image and TWRP and Magisk, after that i was able to boot normally.
Thank you guys anyway, as all the info was already on the forum, all i did was do a deep search.
bmonteiro said:
So looks like i was trying to enter fastboot the wrong way...
I was able to boot into fastboot and then booted from there the TWRP image and then flash the stock image and TWRP and Magisk, after that i was able to boot normally.
Thank you guys anyway, as all the info was already on the forum, all i did was do a deep search.
Click to expand...
Click to collapse
I'm so glad you got it up and running again! There's nothing worse than thinking there's no way out!
bmonteiro said:
So looks like i was trying to enter fastboot the wrong way...
I was able to boot into fastboot and then booted from there the TWRP image and then flash the stock image and TWRP and Magisk, after that i was able to boot normally.
Thank you guys anyway, as all the info was already on the forum, all i did was do a deep search.
Click to expand...
Click to collapse
Glad to see you got it. I had the same issue few days ago and, indeed, it was quite hard to run fastboot mode.
Sent from my GM1913 using XDA Labs
Good recovery! Cheers
I had a OnePlus 6t around the time they first came out and I ended up in crash dump mode probably 12-15 times, sometimes just randomly without doing anything to my phone..I would look at it and it was in crash dump. I recall the devs saying something about a fix for it back then... I have a OnePlus 7 pro 1917 global model now and I bought it used and only had it about one week now. Same exact cinereous. I looked down at my device on day one of me having it and there it was, crash dump mode. Since then on my Guac I've seen crash dumb four times. I've only flashed dotOS and DerpFest but the first crash dump I experienced on this phone was before I flashed anything. I was stock with TWRP installed.. I'm back at my home base now so if and when it happens again ill grab logs and share them. I have always been lucky enough to be able to get control of my device back by holding down power+ volume until I boot to bootloader and then tap power at the "start" screen and ive always booted back up. Have you all experienced crash dump mode often on 7 pro? Hopefully this will be fixed we some point.
I was trying to fix boot loop and completely hard bricked my phone. I can only get into AP Fastboot Flash Mode (Secure) in bootloader. I have been trying to flash it with windows batch file copied into firmware folder but not getting anywhere.
'No valid operating system could be found' on the screen when its not in bootloader.
Please help flash the stock ROM.
Thanks
How I fixed my Z4 XT1980-3
TLDR, try downloading and using the Lenovo Moto Smart Assistant (LMSA) tool
Yesterday I was trying to root my new Z4 and flashed a magisk patched boot img after I got the bootloader unlocked, and I'm pretty sure I ended up exactly where you are. I panicked, tried to do a recovery, a factory reset, nada and got suck in fastboot (apparently that's a Motorola thing). Then I stumbled on a thread elsewhere referring to the Lenovo Moto Smart Assistant (LMSA) tool.
I downloaded it thinking it couldn't hurt. After I started the program and waited through the stupid splash screen, I connected my device (which my PC could no longer detect) and it immediately began installing the Motorola drivers (by that point I had uninstalled just about everything).
I used the rescue function, chose my model, and it downloaded the stock rom. After about an hour, it finished and I started the rescue process. It went through fine until it got to 47%, and then it seemed to hang. After I waited (probably not long enough), I restarted fastboot and unplugged then plugged my phone back in, and it installed the rom and restarted. Back to stock! Not rooted, but working with the BL still unlocked. Yay!
I was shocked at how easy it was, I got cocky and immediately proceeded to soft brick it again. I thought I was better off this time because I wasn't stuck in fastboot, but using the LMSA program was not successful several times. Some times it told me my device wasn't compatible, other times it would just fail. After messing around with it all afternoon, I was where I was the night before--no phone. I was bummed and figured I deserved it, but kept messing with it. I rebooted and had the program redownload the rom, tried it again, and it worked!
No idea if this is the same problem or if it can work for you, but probably can't make it worse? --A
aurelya.hyjal said:
TLDR, try downloading and using the Lenovo Moto Smart Assistant (LMSA) tool
Yesterday I was trying to root my new Z4 and flashed a magisk patched boot img after I got the bootloader unlocked, and I'm pretty sure I ended up exactly where you are. I panicked, tried to do a recovery, a factory reset, nada and got suck in fastboot (apparently that's a Motorola thing). Then I stumbled on a thread elsewhere referring to the Lenovo Moto Smart Assistant (LMSA) tool.
I downloaded it thinking it couldn't hurt. After I started the program and waited through the stupid splash screen, I connected my device (which my PC could no longer detect) and it immediately began installing the Motorola drivers (by that point I had uninstalled just about everything).
I used the rescue function, chose my model, and it downloaded the stock rom. After about an hour, it finished and I started the rescue process. It went through fine until it got to 47%, and then it seemed to hang. After I waited (probably not long enough), I restarted fastboot and unplugged then plugged my phone back in, and it installed the rom and restarted. Back to stock! Not rooted, but working with the BL still unlocked. Yay!
I was shocked at how easy it was, I got cocky and immediately proceeded to soft brick it again. I thought I was better off this time because I wasn't stuck in fastboot, but using the LMSA program was not successful several times. Some times it told me my device wasn't compatible, other times it would just fail. After messing around with it all afternoon, I was where I was the night before--no phone. I was bummed and figured I deserved it, but kept messing with it. I rebooted and had the program redownload the rom, tried it again, and it worked!
No idea if this is the same problem or if it can work for you, but probably can't make it worse? --A
Click to expand...
Click to collapse
I really appreciate your reply.
I have tried LMSA tool but it's failing once I select the model number "Failed to match the connected device. Please plug it out and try again.". I have attached the screenshot.
Motorola ADB Interface driver is installed just like you described.
I think the bootloader is locked (Verizon ver.) and don't think there is any way to unlock it.
Thanks again for looking into this.
pate201 said:
I really appreciate your reply.
I have tried LMSA tool but it's failing once I select the model number "Failed to match the connected device. Please plug it out and try again.". I have attached the screenshot.
Motorola ADB Interface driver is installed just like you described.
I think the bootloader is locked (Verizon ver.) and don't think there is any way to unlock it.
Thanks again for looking into this.
Click to expand...
Click to collapse
UPDATE:
I managed to flashed stock ROM successfully without any error. But the phone is still in boot loop at logo instead of bootloader screen. Baseband is <not found> when booting into fastboot mode. LMSA tool still failing to to match the connected device. Verizon Software Upgrade Assistant is recognizing the phone in fastboot mode and trying to repair but software is not installing downloaded updates; it is stuck at 0% even won't do anything.
I think, I need to fix the Baseband but not sure what to do.
Thanks
I'm pretty confused where you are in the process.
Your device is Verizon? My understanding (and I could be wrong) is that Verizon devices can't have their bootloader unlocked, and without unlocking the bootloader, you can't flash a new ROM.
So, is your BL unlocked?
I specifically got the unlocked Amazon variant Z4 XT1980-3 hoping I could unlock the BL and root. I was able to do both, but I could only root after I got the BL unlocked.
I think I could upload my baseband file if you want to play around, but I have no idea if you're gonna brick your device. I'd check around in other forums/online and see what you can find out. I got the z4 because it was super cheap (comparatively) so if I killed it I wouldn't feel too bad buying a replacement. But $$'s still $$.
GL man!
aurelya.hyjal said:
I'm pretty confused where you are in the process.
Your device is Verizon? My understanding (and I could be wrong) is that Verizon devices can't have their bootloader unlocked, and without unlocking the bootloader, you can't flash a new ROM.
So, is your BL unlocked?
I specifically got the unlocked Amazon variant Z4 XT1980-3 hoping I could unlock the BL and root. I was able to do both, but I could only root after I got the BL unlocked.
I think I could upload my baseband file if you want to play around, but I have no idea if you're gonna brick your device. I'd check around in other forums/online and see what you can find out. I got the z4 because it was super cheap (comparatively) so if I killed it I wouldn't feel too bad buying a replacement. But $$'s still $$.
GL man!
Click to expand...
Click to collapse
You are right, it is a Verizon (XT1980-4) device and I cannot get the bootloader unlocked. I was only trying flash stock to unbrick it. I flashed the stock VZW firmware that I found somewhere without any error using fastboot.
Sure, I can give it a try with your baseband file. I already have stock Flash ready to re-flash it if necessary, and my device is not in working condition so nothing to loose.
Thanks for you reply.
I'll try to do that tonight when I get home from work. Sorry my responses have been so dumb. I'm still figuring it all out.
I would also need help to flash stock ROM. I have Z4 XT1980-3 with BL LOCKED. Already tried to reflash factory image via fastboot after an unsuccessful OTA upgrade. I can flash all parts except of boot, dspso and vbmeta. For these I get a "Preflash validation failed" error. So I have not been able to flash an entire factory image. I can only go to fastboot mode, nothing else. LMSA says my device is not compatible. RSD Lite says my device can not be switched to fastboot mode (but I already am in fastboot mode ???). So no joy with these. Can anybody give me any advice how to reanimate my device?
Maheshwara said:
I would also need help to flash stock ROM. I have Z4 XT1980-3 with BL LOCKED. Already tried to reflash factory image via fastboot after an unsuccessful OTA upgrade. I can flash all parts except of boot, dspso and vbmeta. For these I get a "Preflash validation failed" error. So I have not been able to flash an entire factory image. I can only go to fastboot mode, nothing else. LMSA says my device is not compatible. RSD Lite says my device can not be switched to fastboot mode (but I already am in fastboot mode ???). So no joy with these. Can anybody give me any advice how to reanimate my device?
Click to expand...
Click to collapse
I am also on same boat with Z4 XT1980-4 Verizon model. Bootloader is locked and Baseband missing on the fastboot screen. Please help if anyone have recover their phone from this.
Thanks
Hi, so thought things where going well and here I am.
Just as a prewarning I often get overwhelemed with a lot of phone terms so sorry if I dont pick up straight away or make sense myself.
Basically wanted to Root my old google pixel xl, and I managed to unlock the bootloader, download magisk get the img and to the point where I had my patched file, all based on the guide on High on android . com
However once I ran the boot process of the patched file, it didn't work. I got stuck in wht I think was a boot loop, where the G would load up and then just be loading forever.
So I figured I did something wrong and went to load back the original Boot.img since that was their advice and this seems to have only made the problem worse, now I didn't even reach the G, instead google appears before flicking to a No command screen where there a dead lil androidian? idk what the green dude is) but yeah not good I assume.
So this is what I've tried to do so far;
I can still get to the bootloader page and have tried again to no success, even the patched file does the same and the original now.
I have tried the android recovery memory and doing a factory reset, and still have the issue
Turning the device off and leaving it and coming back
Applying an update from ADB within the recovery menu, which I tried both the og boot and patched and didn't work.
I did also notice that when following the tutorial and copying my device number I used Marlin but on the recovery screen now it says Sailfish, so I'm not sure if I used the wrong one? I have tried using the boot img from Sailfish but this did nothing.
Any help or is it better off to stop here?
Its not the end of the world but Id rather know before giving it away for parts or something
Hi all.
I read that my oneplus 9 was able to test the beta of android 12 and found that I could do so in developer options and choose the dsu loader. Did that and now my device won't work at all. I can't get into recovery and factory reset it or anything it just restarts itself and i get an error message saying the device is corrupted and won't boot. Is it any way to fix this or have my own foolishness killed this phone? Please help
Illusions_887 said:
Hi all.
I read that my oneplus 9 was able to test the beta of android 12 and found that I could do so in developer options and choose the dsu loader. Did that and now my device won't work at all. I can't get into recovery and factory reset it or anything it just restarts itself and i get an error message saying the device is corrupted and won't boot. Is it any way to fix this or have my own foolishness killed this phone? Please help
Click to expand...
Click to collapse
Not all hope is gone. If there is an msm tool for your variant your in luck. I have the global unlocked op9 and there isn't one yet. Although you can use a fastboot rom from xda. And there is always last resort of calling OnePlus customer service and getting a remote session . Explain to them you tried the beta release and now phone is unuseable . Hope you get it fixed as I bricked my op8 a month or so ago and it's a bad feeling. I also read the developer previews were not for north American devices. Maybe you saw that as well.
Illusions_887 said:
Hi all.
I read that my oneplus 9 was able to test the beta of android 12 and found that I could do so in developer options and choose the dsu loader. Did that and now my device won't work at all. I can't get into recovery and factory reset it or anything it just restarts itself and i get an error message saying the device is corrupted and won't boot. Is it any way to fix this or have my own foolishness killed this phone? Please help
Click to expand...
Click to collapse
If you can boot to fastboot mode. Then fastboot format userdata I think
Didn't work. Think my bootloader is locked as well since I haven't unlocked it at all. Just read online that you could test the android beta by using that dsu thing and now my phone is gone. It was completely stock hadn't touched a thing except that I got into developer options. I didn't think i could brick a phone without mixing with ROMs and stuff.
Can you get it to bootloader?
Power off completely, then 3-button hold (vol up + vol down + power) till bootloader screen.
If you can, and you can get fastboot to recognize the device, you might have a shot at fastboot oem unlock, and then possibly a fastboot rom.
If not, then you might ask Oneplus support for an MSM tool
reaper000 said:
Can you get it to bootloader?
Power off completely, then 3-button hold (vol up + vol down + power) till bootloader screen.
If you can, and you can get fastboot to recognize the device, you might have a shot at fastboot oem unlock, and then possibly a fastboot rom.
If not, then you might ask Oneplus support for an MSM tool
Click to expand...
Click to collapse
No luck with OEM unlock. Contacted oneplus here in sweden and will send the phone to them on Monday hoping they can fix it. Never thought i could mess upp a phone so much by just tinkering with settings within the phone but you live and learn all the time i guess. Bit sad since I got the phone two days ago