Hi all,
My one plus one bricked when updating to CM12s via OTA. Since then, I have tried everything, but I am stuck on the oneplus screen. I cannot get to recovery no matter what. Bootloader still works though
This is what I have tried
1. Flashed cm12s, cm11s via fastboot. Still didnt wake it up
2. Used the color OS+MSM8974 tool to flash color os, still stuck on the red oneplus logo
3. Used the color OS+MSM8974 tool to flash color os, then flashed cm11s, still stuck on the oneplus logo
4. Used the oneplus recovery tool, still stuck on the oneplus logo.
In all this scenarios, I cannot access recovery, I even flashed TWRP, and still cannot access recovery.
Bootloader is unlocked.
Of note, when using the MSM8974 tool, I get the following message when I check the logs:
userdata.img: FAILED
userdata_64G.img: FAILED
boot.img: FAILED
cache.img: OK
persist.img: FAILED
recovery.img: FAILED
Click to expand...
Click to collapse
Related
hello
i've bought used moto g 2015 from spain.
the problem is that the device is locked with status code 0.
i've been trying to unlock it, but with no luck.
everything gives the error failed(remote failure)
recently i've used windroid toolkit to unlock bootloader and install twrp like in some tutorials, the app says it's done, but after i enter a recovery the phone hangs and boots again to fastboot.
any help will be appreciated
EDIT:
invoking "mfastboot flash partition gpt.bin" command gives the error too so i am unable of installing stock firmware too
EDIT2:
i've successfully installed stock package but there is still a problem - boot loop.
you need to flash stock rom to remove boot loop.
here is the link
http://forum.xda-developers.com/2015-moto-g/general/index-moto-g-factory-firmware-images-t3169639
sachin09 said:
you need to flash stock rom to remove boot loop.
here is the link
http://forum.xda-developers.com/2015-moto-g/general/index-moto-g-factory-firmware-images-t3169639
Click to expand...
Click to collapse
I have already flashed the rom but now i think it could be a bad package. My phone is from spain and i installed before:
XT1541_OSPREY_ORAES_6.0_MPI24.65-33_cid7_subsidy-DEFAULT_CFC.xml
now i'm downloading
XT1541_OSPREY_RETES_6.0_MPI24.65-33_cid7_subsidy-DEFAULT_CFC.xml.zip
is there any way to find out which package should i use for sure?
the last package i mentioned doesnt change anything. phone boots to bootloader not to system.
any news i have the same thing with my device everything was flashed but i get boot faillure ??
nothing... i'll get my money back i guess
Hello friends,
i wanted to update my twrp from the very first on to the latest 3.3. I did this in the recovery itself. after i could not boot into twrp anymore. Neither through Updater app, nor through Button Combo.
It all sent me to bootloader. So i tried flashing the twrp img through fastboot.
First: always in cmd fastboot flash recovery twrp.img; but result was that cmd gave no answer at all or failure
Second: i tried fastboot boot twrp.img.; Result was a successful flash, but no boot into recovery afterwards
AND AFTER THAT I cant boot into system anmyore
Edit:
on another pc I got Miflash running and installed latest global rom. Now im stuck till mi recovery. Phone is still unlocked
Edit2:
Got TWRP installed and after newest xiaomi eu rom. Still lost all my data, because everything was still encrypted..
So I've got a weird issue here, and after a sleepless night of Googling and using the MSM download tool, I still haven't figured this out. Basically, something got royally FUBARed while I was trying to flash LineageOS 16 to my OP6, and my phone got stuck in a point where not even TWRP would boot, and fastboot only brought up a black screen with a blue LED. After a bit of searching, I ended up using the MSM download tool to re-flash the stock ROM and recovery. I attempted to install TWRP after unlocking the bootloader, but every time I try to fastboot boot TWRP, it brings up that same black screen with blue LED, whether I use the official TWRP image or the blue_spark TWRP image.
TLDR; I got bricked, fastboot flashed back to stock, and now I can't boot TWRP to flash TWRP to my OP6. Anybody out there know what I should do?
Cheers,
Ph0enix_216 said:
So I've got a weird issue here, and after a sleepless night of Googling and using the MSM download tool, I still haven't figured this out. Basically, something got royally FUBARed while I was trying to flash LineageOS 16 to my OP6, and my phone got stuck in a point where not even TWRP would boot, and fastboot only brought up a black screen with a blue LED. After a bit of searching, I ended up using the MSM download tool to re-flash the stock ROM and recovery. I attempted to install TWRP after unlocking the bootloader, but every time I try to fastboot boot TWRP, it brings up that same black screen with blue LED, whether I use the official TWRP image or the blue_spark TWRP image.
TLDR; I got bricked, fastboot flashed back to stock, and now I can't boot TWRP to flash TWRP to my OP6. Anybody out there know what I should do?
Cheers,
Click to expand...
Click to collapse
With MSM tool your oneplus 6 is locked again...Maybe you should look if bootloader is locked!
Unlock BL
After its done you'll have to enable debug in developer options
Then fastboot boot twrp
Flash twrp
whizeguy said:
Unlock BL
After its done you'll have to enable debug in developer options
Then fastboot boot twrp
Flash twrp
Click to expand...
Click to collapse
My bootloader is unlocked. Still can't get into TWRP.
Ph0enix_216 said:
My bootloader is unlocked. Still can't get into TWRP.
Click to expand...
Click to collapse
Did you enable debug?
Sounds like you may have the active slot set to an unbootable OS. Check the active slot with fastboot getvar all, then use this to change to the other slot.
fastboot --set_active=[a or b depending on which is inactive]
Was this the end of this? I'm in the same boat. I was recovering from a google account remove device wipe and so I went to restore my TWRP back-up and it succeeds so I reboot. Device is bricked into fastboot mode only. So I msm restore and boot system, enable debugging, unlock bootloader, still can't get into TWRP or versions that worked before, just that taunting blue light.. I found this and changed my active slot but the issue is the same and I'm kind of at a dead end, any help would be appreciated. I can boot into 5.1.5 OOS and stock recovery fine.
Nevermind I had to incrementally update the ROM
angelsenvy said:
Nevermind I had to incrementally update the ROM
Click to expand...
Click to collapse
You can download both twrp zip & img from here: https://drive.google.com/drive/folders/1bnGBrkL5XE3yt7DmIRSDD2v4J6MzFOsH?usp=sharing
fastboot flash boot twrp-3.4.0-1-enchilada-Q-mauronofrio.img instead of fastboot boot .
That will work
I recently unlocked my bootloader on my sprint oneplus 7 pro 5g, but i screwed up afterwards and accidentally wiped the entire system, i've tried msm downloader and reflashing to no avail. sometimes when i reboot the boot loader it gives me the unlocked warning screen extremely briefly before entering the boot loader again. when i try to boot into twrp using fastboot it gives me a "remote: 'failed to load/authenticate boot image: load error" however occasionally the boot image will send but it wont actually boot it just gets stuck on the oneplus logo fastboot mode screen. When i try to use msmdownload tool it gives me a "device not match image" message. i've also attempted to reflash every partition individually by unpacking the oxygenOS zip and flashing each image one at a time. immediate assistance would be greatly appreciated.
aero_dreams said:
I recently unlocked my bootloader on my sprint oneplus 7 pro 5g, but i screwed up afterwards and accidentally wiped the entire system, i've tried msm downloader and reflashing to no avail. sometimes when i reboot the boot loader it gives me the unlocked warning screen extremely briefly before entering the boot loader again. when i try to boot into twrp using fastboot it gives me a "remote: 'failed to load/authenticate boot image: load error" however occasionally the boot image will send but it wont actually boot it just gets stuck on the oneplus logo fastboot mode screen. When i try to use msmdownload tool it gives me a "device not match image" message. i've also attempted to reflash every partition individually by unpacking the oxygenOS zip and flashing each image one at a time. immediate assistance would be greatly appreciated.
Click to expand...
Click to collapse
Have you checked out this and tried this?
https://forum.xda-developers.com/oneplus-7-pro/how-to/sprint-msmdownloadtool-unbrick-t3989841/amp/
Sent from my OnePlus 7 Pro using Tapatalk
aero_dreams said:
I recently unlocked my bootloader on my sprint oneplus 7 pro 5g, but i screwed up afterwards and accidentally wiped the entire system, i've tried msm downloader and reflashing to no avail. sometimes when i reboot the boot loader it gives me the unlocked warning screen extremely briefly before entering the boot loader again. when i try to boot into twrp using fastboot it gives me a "remote: 'failed to load/authenticate boot image: load error" however occasionally the boot image will send but it wont actually boot it just gets stuck on the oneplus logo fastboot mode screen. When i try to use msmdownload tool it gives me a "device not match image" message. i've also attempted to reflash every partition individually by unpacking the oxygenOS zip and flashing each image one at a time. immediate assistance would be greatly appreciated.
Click to expand...
Click to collapse
Gm1920 or gm1925? Pm sent.
hi....i'm having the same problem....everything was working until i flashed majick in twrp and then got stuck in fastboot......and nothing will work....thanks in advance.....i have an account but my google account was compromised and lost all credentials.......thanks again for finding a way to unlock the bootloader
Hi Guys,
I think I f...ed up big time...
My device was rooted and I tried to unroot/factory reset to give it to my wife. Since I'm now sitting here for about 5 hrs I try to summarize what I've been doing:
1. I started with trying to Flash a Factory Image with the ALL-IN-ONE Tool
- My Device was on the Latest Oxygen OS 11 and I just stupidly followed the instructions of the Tool and downloaded a OOS 10 based Stock Rom and flashed it (thats where my nightmare began)
- After I flashed the OOS 10 Stock Rom I was Stuck in at the Open Bootloader warning screen ("the boot loader is unlocked and software integrity cannot be guaranteed ...")
2. Since there is no (at least I couldn't find one for the life of me) OOS 11 fastboot stock ROM I tried to downgrade via an OOS Beta ROM I found in a downgrade guide
- That didn't work either and I ended up stuck at the same Screen
3. After some googling I came across this guide and tried to manually flash a none fastboot OOS 11 ROM by manually extracting all the images of the payload.bin
- After I extracted all the images I flashed them one by one as mentioned in the guide via fastboot and this ended up with
Qualcomm Crash Dump mode dm-verity device corrupted force dump Kernel restart
Click to expand...
Click to collapse
4. After that I panicked a little since I've never seen this error before and tried to Flash the OOS 10 based Stock rom via the ALL-IN-ONE Tool again
- This worked with no errors but now I'm still stuck in the "Open Bootloader warning Screen"
Since then I tried Step 4 with another OOS 11 none fastboot ROM but now I keep getting following error everytime I try to flash one of the extracted images via fastboot (which worked before):
FAILED (remote: Flashing is not allowed for Critical Partitions
Click to expand...
Click to collapse
I did some research, seems like this error indicates a locked bootloader which is wrong, bootloader is still unlocked.
Even if I try to unlock the bootloader again I get the reply that bootloader cannot be unlocked since it already is unlocked.
So now I'm stuck with a completely f...ed up device with absolutely no clue if and how I can fix this.
I really hope anyone of you guys can help ...
Apologies for the bad writing but it's 5 am and I'm tired and frustrated af ...
greetings from Germany.
Timo
EDIT: Oh and yes, I know about the MSM-Tool and tried it but I can't get it to work since my device is not showing. I followed this guide several time but nothing is happening and my device is not even showing in the device manager. Only time it shows in the device manager is when in fastboot mode.
Guys I finally did it.
I deinstalled all stale/inactive drivers and reinstalled the Qualcomm drivers and finally managed to get the MSM Tool up and running and revived the phone.