Hello, I am new here so I will try to be as detailed as possible.
My One Plus 7 Pro seems to be bricked and I have been trying for the past two days to try and make some head way. I have searched and used all versions of the MSM Tool for this phone but after flashing I get the logo, the spinning animation comes up then the screen goes dark. A boot loop begins just like before and then it eventually goes dark.
The boot state is locked so I cannot flash with fastboot through CMD or Powershell. Is there anything else I can try?
PS. The phone came up at random one of the times but when I clicked on "agree" on the terms and condition page, it just ended up going dark and then back to square one. Was trying to unlock the boot state through developer tools but I failed.
I did a root rm -rf / in recovery adb, I couldnt even get the thing to vibrate but MSM tool got it back up and running. keep trying ;p
RolandStoner said:
I did a root rm -rf / in recovery adb, I couldnt even get the thing to vibrate but MSM tool got it back up and running. keep trying ;p
Click to expand...
Click to collapse
I used the global. It was the only one that seems positive to a point. The one plus logo comes up, the spinning animation comes next...but it then freezes mid spin then the screen goes dark. I am not sure why it doesn't seem to be working all the way.
Related
Hello everybody here at XDA, ( this is my first post here so bare with me here)(english is not my native language either)
My device:
Nexus 5 - hammerhead D821(H) 16GB
BL version - HHZ12h
BB version M8974A-2.0.50.2.26
Secure boot enabled
lock state unlocked
today i got a "broken" nexus 5 that is in boot loop with the google logo and it wont boot into any .img
At the start i read the pinned posts and found this tutorial: http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
followed it step by step. but unfortunatly it didnt help my situation. there werent any errors or such kind.
i also tried this tutorial with other images but nothing worked.
When i go to the recovery mode and press the power button the phone get into the google logo and i can see some sort of strange stripes in like a milisecond but then it just gets into the boot loop.
i really think ive tried everything accept for relocking the bootloader but cant imaging that this could be the problem.
If you guys need more info please just ask me.
Hope you guys can help me out here.
Martin
Really thought XDA forums would be able to help me.
Any admins or mods or any other veteran that could help me out?
If that's not working for you, you can try using the Nexus Root Toolkit just to be sure.
If that doesn't work, than it could be hardware related, and not much you can do about that.
Hi All,
I have boot-loop problem for Nexus5 as described earlier .
As I was able to boot in Fastboot
I went for factory reset, and saw FAILED (remote: flash write failure).
I have tried to flash countless time with same error.
Then I read this thread and considered phone memory is toasted.
LG service-center have quoted me around $180 for mother board replacement.
Today I tried twrp project to boot in openrecovery and start an adb shell.
I was able to see file system of my phone.
These following folders are empty:
/boot
/cache
/data
In system folder there is only bin folder and which is empty.
/system
I have gotten this far, is internal memory roasted
Any direction or suggestions welcomed :good:
mesh120673 said:
Hi All,
I have boot-loop problem for Nexus5 as described earlier .
As I was able to boot in Fastboot
I went for factory reset, and saw FAILED (remote: flash write failure).
I have tried to flash countless time with same error.
Then I read this thread and considered phone memory is toasted.
LG service-center have quoted me around $180 for mother board replacement.
Today I tried twrp project to boot in openrecovery and start an adb shell.
I was able to see file system of my phone.
These following folders are empty:
/boot
/cache
/data
In system folder there is only bin folder and which is empty.
/system
I have gotten this far, is internal memory roasted
Any direction or suggestions welcomed :good:
Click to expand...
Click to collapse
Are you sure your bootloader is unlocked?
When you boot the phone in Fastboot mode, does the "lock state" say UNLOCKED?
If so, then yeah, your internal memory could be huffed.
spookytay said:
Are you sure your bootloader is unlocked?
When you boot the phone in Fastboot mode, does the "lock state" say UNLOCKED?
If so, then yeah, your internal memory could be huffed.
Click to expand...
Click to collapse
It says Locked.
I unlock it using ./fastboot oem unlock
I just got my N5 and was messing around. Rooted it and loaded a rom, but it would just seem to hang at the spinning dots forever. Though I didn't wait THAT long like some users did and had success.
I can't find the link I used, but googling around should get you there. I ended up restoring a factory image via fastboot. I ended up using THIS PROGRAM to root the phone. This program also has a restore option and gives an option to check in case you are in boot loop status. Give it a shot.
Yes I do believe you have to unlock the bootloader as well.
Nurmi_CEO said:
I just got my N5 and was messing around. Rooted it and loaded a rom, but it would just seem to hang at the spinning dots forever. Though I didn't wait THAT long like some users did and had success.
I can't find the link I used, but googling around should get you there. I ended up restoring a factory image via fastboot. I ended up using THIS PROGRAM to root the phone. This program also has a restore option and gives an option to check in case you are in boot loop status. Give it a shot.
Yes I do believe you have to unlock the bootloader as well.
Click to expand...
Click to collapse
Yes the bootloader must be unlocked before you can do ANYTHING to the phone, it's what's there to protect it from being hacked/changed or whatever. So before you can write anything to your phone, you need to make sure you OEM UNLOCK the bootloader.
[Solved!] Nexus 5 boot loop at Google logo
I found a solution on Youtube comment (can't post url, too new user).
You just have to press quickly the Power button durint 1-2 minutes (continue untill the Android animation start, don't stop when the Google logo appear)3
As crazy as it sounds, IT WORKS
Wow .. i had the exact same problem (Startup loop on Nexus 5 that shows the Google logo and restarts, over and over), and i pressed the power button quicky about 30 or 40 time until after I saw the startup animation and my phone came back to life. I have been charging it with cables other than the one that came with the phone for a few months now, and it has been acting strangely while plugged in (randomly clicking things on the screen, and enabling my camera and taking pictures on its own, etc.). So, to avoid problems in the future, I think I'll invest in a wireless charger. Thanks JackNUMBER for the easy solution. I hope this works for others as well. Saved me a trip to the store.
So a few weeks ago I flashed the Android P preview on my Bluetooth Hwatch 2. All was well until yesterday I decided to check out some other roms. It was late and I should not have done this but I got into twrp and then decided I wanted to fall asleep. I decided to reboot out of TWRP assuming it would boot back into the watch (I had not deleted anything to my knowledge). Now it is stuck on the Huawei logo. When I hold down both buttons I get "Device software cannot be checked for corruption" and it lets me pause the boot for a moment but then it goes back to the Huawei logo. Plugging it in does not get me fastboot or ADB from my PC and I cannot seem to turn it off.
Any ideas?
Thanks
Bigsam411 said:
So a few weeks ago I flashed the Android P preview on my Bluetooth Hwatch 2. All was well until yesterday I decided to check out some other roms. It was late and I should not have done this but I got into twrp and then decided I wanted to fall asleep. I decided to reboot out of TWRP assuming it would boot back into the watch (I had not deleted anything to my knowledge). Now it is stuck on the Huawei logo. When I hold down both buttons I get "Device software cannot be checked for corruption" and it lets me pause the boot for a moment but then it goes back to the Huawei logo. Plugging it in does not get me fastboot or ADB from my PC and I cannot seem to turn it off.
Any ideas?
Thanks
Click to expand...
Click to collapse
Same here. Stuck on Huawei logo. Did you fix yours?
borijess said:
Same here. Stuck on Huawei logo. Did you fix yours?
Click to expand...
Click to collapse
I did not. I gave up on it and then had to go out of town on a business trip. I switched back to my Gear fit 2 for now. If someone has a fix I will gladly do it though.
Hi, I did the same thing with my watch and thought I had broke it beyond repair, I flashed the Bluetooth ROM on the 4g model and had the exact same problem. I flashed the boot.img again and done a factory reset. Worked for me so I would advise giving it a try.
Bigsam411 said:
So a few weeks ago I flashed the Android P preview on my Bluetooth Hwatch 2. All was well until yesterday I decided to check out some other roms. It was late and I should not have done this but I got into twrp and then decided I wanted to fall asleep. I decided to reboot out of TWRP assuming it would boot back into the watch (I had not deleted anything to my knowledge). Now it is stuck on the Huawei logo. When I hold down both buttons I get "Device software cannot be checked for corruption" and it lets me pause the boot for a moment but then it goes back to the Huawei logo. Plugging it in does not get me fastboot or ADB from my PC and I cannot seem to turn it off.
Any ideas?
Thanks
Click to expand...
Click to collapse
Yeah, once you unlock your bootloader I dont know of anyway to access recovery or fastboot unless over adb, it's because of the damn prompt huawei put in to pause the boot. I waish they did waht lg did with the g watch (Just shows a little unlocked lock, no stupid prompt) So if you brick the watch like that, I doubt they'll honor the warranty either. (Especially if they find TWRP)
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.
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
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.