so, i was trying to install twrp, but i made a stupid mistake, instead of fastboot flash recovery i did fastboot flash boot, now it tells me: "the current image(boot/recovery) have been destroyed", when i go into bootloader, and attack the cable (both before and after) restarts itself.
things I tried: flash the original boot (it gave "FAILED (Write to device failed (no link))", obviously before the bootloader happened) change usb cable, flash the stock rom (obviously before the bootloader happened)), redownload adb /fastboot drivers, phone drivers, and google drivers. this is all i remember trying to do, i'm desperate, could someone help me please?
update: now i can use bootloader
update: I fixed it, in case this situation happened to you, I solved it like this: I had a windows update, while it was doing it, I connected the phone to the pc, in the end it no longer rebooted by itself (the phone) , then do fastboot flash boot (original boot), if it doesn't work, reboot the bootloader , from the bootloader, if it doesn't work, do the same thing downloading the drivers again, then do fastboot flash boot (original boot.img), if you want to download costum recovery, do fastboot flash recovery (costum recovery.img). I fixed it like this, now I have a costum recovery, costum rom and root!
Hello friend, I have a question. I closed the bootloader and when I closed it, the recovery image was destroyed.
Now I can't enter my cell phone and it stays in an infinite boot
any solution with locked bootloader
Angel1104 said:
Hello friend, I have a question. I closed the bootloader and when I closed it, the recovery image was destroyed.
Now I can't enter my cell phone and it stays in an infinite boot
any solution with locked bootloader
Click to expand...
Click to collapse
try going into the bootloader and re-unlocking it
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
That happened to me when I wanted to block the boot, so I think the boot was blocked and only stayed in the realme recovery like the following photo
Angel1104 said:
View attachment 5798249That happened to me when I wanted to block the boot, so I think the boot was blocked and only stayed in the realme recovery like the following photo
Click to expand...
Click to collapse
I don't understand if the recovery works or not, it's a bootloop with locked bootloader and you can go into recovery or locked bootloader without accessing recovery? you are confusing me, however, if you have access to recovery download the stock rom from the recovery, if not, try to unlock the bootloader again by doing fastboot flashing unlock, then flash the stock recovery and then download the stock rom from the recovery
And how do you enter that mode without the application?
enter bootloader and do fastboot reboot recovery, in bootloader you can't perform flashing actions and many other things (bootloader locked) but some things, like reboot should work
in case you get the same error for the recovery you have to unlock the bootloader again
Can I send you a private message?
yes
Did you solve it? I'm facing the same issue.
Gamer_Mida said:
update: I fixed it, in case this situation happened to you, I solved it like this: I had a windows update, while it was doing it, I connected the phone to the pc, in the end it no longer rebooted by itself (the phone) , then do fastboot flash boot (original boot), if it doesn't work, reboot the bootloader , from the bootloader, if it doesn't work, do the same thing downloading the drivers again, then do fastboot flash boot (original boot.img), if you want to download costum recovery, do fastboot flash recovery (costum recovery.img). I fixed it like this, now I have a costum recovery, costum rom and root!
Click to expand...
Click to collapse
I am having trouble understanding what you did exactly. I am getting this same error with a Xiaomi Mi 8 Lite.
Edit: got it working by disconnecting all usb ports and trying another port.
Angel1104 said:
Hello friend, I have a question. I closed the bootloader and when I closed it, the recovery image was destroyed.
Now I can't enter my cell phone and it stays in an infinite boot
any solution with locked bootloader
Click to expand...
Click to collapse
same as me i dont know what to do
Related
Hi... i tried to flash CWM and enter recovery mode a couple of times and not once am i successful. I keep getting a white HTC screen with red text "This build is for development purposes only, not to be distributed.. etc etc"
No matter which CWM i tried it just would not work... i noticed some people have this problem but no solution? Does the latest One S have some kind of block or something that does not let us run these images?
Wrong section !!!
Anyway, Are you flashing the CWM recovery image in fastboot ? Do you have unlocked bootloader ? Have you tried a different recovery image ?
First person I have heard of not being able to flash recovery. Unlock bootloader. Then go to appstore and download goomanager. Download and flash TWRP thru goomanager.....done
Sent from my HTC VLE_U using XDA Premium HD app
Moved To Q&A
Please post questions in the Q&A section
azzledazzle said:
Wrong section !!!
Anyway, Are you flashing the CWM recovery image in fastboot ? Do you have unlocked bootloader ? Have you tried a different recovery image ?
Click to expand...
Click to collapse
I can flash it...Yes flashing in fastboot, yes tried a few img...official, Paul and twcm... I can click the option too...but all still bring me to that screen. I cannot use goomanager because without cwm I can't root,
Am I missing something? My bootloader does show unlocked ... so it means my boot loader is successfully unlocked right
onlinechi said:
I can flash it...Yes flashing in fastboot, yes tried a few img...official, Paul and twcm... I can click the option too...but all still bring me to that screen. I cannot use goomanager because without cwm I can't root,
Am I missing something? My bootloader does show unlocked ... so it means my boot loader is successfully unlocked right
Click to expand...
Click to collapse
Yes, If it says unlocked then it is unlocked did YOU unlock it ?
Are the recovery images flashing successfully ? without any errors ? you could try and use adb to reboot in to recovery.
If that fails, You could try and fastboot boot recovery, You can flash almost anything this way
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This is what I get.... yes I did unlock it. Yes I did successfully flash. Its just when I reboot and enter bootloader and choose recovery... I keep getting that despite trying multiple images ... what is the meaning of that screen anyway... if we know what it does perhaps we can know what is wrong
--duplicate post--
That writing you see is normal, It happens as soon as you put non official software on the device. I cant figure out why it wont boot into recovery.
You could try to flash stock recovery,
Then fastboot erase cache.
Then reflash CWM and hope for the best.
Dont give up, Ill have a look around for some kinda fix for you !
EDIT: Also try Hasoons All In One Tool until i figure this out
when I click recovery in the bootloader... it shows that and just stays there.... may I know where the link is to a stock recovery as I did not back up mine...
https://dl.dropbox.com/u/69014495/stock recovery.zip
Does the phone boot ?
Did you try fastboot erase cache ?
Hi.. i tried flashing the stock recovery with Hasoons tool... I still get to the screen which shows... "this build is for development purposes only. Do not distribute.. etc etc..." Thats so strange. Logically it should should just show that for awhile then go on to the recovery isnt it? Why does it just stay there?
By the way.. how do i erase cache? Is it possible to be done without entering recovery?
I tried flashing the stock recovery. Locking the bootloader... then unlocking it all over again. Then flashing the CWM recovery... then boot to recovery.. still.... the same. :-(
so the phone does never boot ??
If i was you i'd run an RUU and start all over again
Oh no... the phone is perfectly fine.. its just the Recovery in to which its stuck. The normal operation of the phone is totally OK. I read something.. if i had flashed a recovery image... it should show my phone as "tampered" in the bootloader. Mine does not show that.. it just shows "Unlocked".. Is there something i missed?
Btw... i do not know if it matters.. but my phone is from Singapore.
it will only show tampered when you replace the stock recovery. Your phone believes it still has this.. which indicates that CWM didnt flash, even tho adb said it did
I came across a post where someone said erasing cache helped. So perhaps you could try this, It wont reset your phone, Just erases the cache, Boot into fastboot and type: fastboot erase cache
then try to get into recovery, if not try the command again and flash cwm recovery without rebooting.
I had the same problem. I did not know how to fix it directly.
Installing it using the app Rom Manager got CWM installed properly, though.
jayelbird said:
I had the same problem. I did not know how to fix it directly.
Installing it using the app Rom Manager got CWM installed properly, though.
Click to expand...
Click to collapse
How did you use Rom Manager when you dont have root?
azzledazzle said:
it will only show tampered when you replace the stock recovery. Your phone believes it still has this.. which indicates that CWM didnt flash, even tho adb said it did
I came across a post where someone said erasing cache helped. So perhaps you could try this, It wont reset your phone, Just erases the cache, Boot into fastboot and type: fastboot erase cache
then try to get into recovery, if not try the command again and flash cwm recovery without rebooting.
Click to expand...
Click to collapse
MMM.... Does not work.. I tried this
Boot into boot loader.. did the erase cache. Was ok. Did a reboot.
Reboot in to bootloader.. install recovery.. reboot
Reboot then attempted enter recovery.. still the same... Stuck at the red text
I then tried this
Boot into boot loader... did the erase cache.. was ok.. no reboot
Flash the recovery.. no reboot
Enter recovery.. still the same.. stuck at red text
Reboot.. enter recovery.. also the same.. stuck at red text...
:-( I have had HTCs.. Samsungs... and rooted all of em.. this is the first time i have been unsucessful.. heck i even rooted a China Device before....
Bootloop
Hi there, i was on cm7, than i found this rom "Desire XS version 1.1" and I decided to install it, after aroma installation, I rebooted it and now i'm in bootloop and i can't access to hboot, what should I do?
Hi, I assume you are s-on with unlock bootloader? If yes, then enter fastboot(if my memory serves me right, hold vol down and power on). The instructions can be found here. I assume u have already wipe/format and flash the rom, so the next thing to do is flash the boot.img in fastboot, found in the link, step 4.
Thank you for your reply, but i think that i can't access to fastboot
evilken9555 said:
Thank you for your reply, but i think that i can't access to fastboot
Click to expand...
Click to collapse
pull the battery out for a min then put back in, u should be able to boot into bootloader then select fastboot in the menu
Got an update :
Both of the suggestions didn't work, so i've tried to connect my phone to a PC and tried to use adb to access into fastboot mode, once I've got into fastboot I've tried to install the stock firmware through ruu, but I get an error : USB error
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
#Fear said:
Hi, I assume you are s-on with unlock bootloader? If yes, then enter fastboot(if my memory serves me right, hold vol down and power on). The instructions can be found here. I assume u have already wipe/format and flash the rom, so the next thing to do is flash the boot.img in fastboot, found in the link, step 4.
Click to expand...
Click to collapse
i can't find boot.img :|
edit: i've found the boot.img, now the problem is that when i connect my phone to the pc when it is in fastboot mode, after a bit a notification with a yellow exclamation mark appears and says "Usb device not recognized", i have windows 8.1, could it be the problem?
evilken9555 said:
i can't find boot.img :|
edit: i've found the boot.img, now the problem is that when i connect my phone to the pc when it is in fastboot mode, after a bit a notification with a yellow exclamation mark appears and says "Usb device not recognized", i have windows 8.1, could it be the problem?
Click to expand...
Click to collapse
the ruu wont work coz ur bootloader is "unlocked". u need to relock it then run the ruu. and yes windows 8 is a problem with fastboot, theres a few guides here on xda how to use fastboot with windows 8. so either find a way to get fastboot working then flash custom rom in recovery then flash the boot.img via fastboot or relock the bootloader (ul need fastboot commands working for that too) and then run ur ruu. either way, get fastboot working first.
jmcclue said:
the ruu wont work coz ur bootloader is "unlocked". u need to relock it then run the ruu. and yes windows 8 is a problem with fastboot, theres a few guides here on xda how to use fastboot with windows 8. so either find a way to get fastboot working then flash custom rom in recovery then flash the boot.img via fastboot or relock the bootloader (ul need fastboot commands working for that too) and then run ur ruu. either way, get fastboot working first.
Click to expand...
Click to collapse
thank you for your support guys, i'll try this in the afternoon =).
I wanted to thank you so much guys, thank you for your help and kindess, i've finally installed the original sense rom =).
Have a good day!
no custom recovery loading
I am currently using moto G first generation xt1033 indian dual sim version.
I have soft bricked my phone.
WHAT I HAVE: I have access to fastboot
My bootloader is unlocked
Access to stock recovery
PROBLEM: I have tried to flash twrp , cwm and philz recovery but every time i boot into recovery mode stock recovery loads.
I cannot access USB Debugging mode since the phone is soft bricked.
I have also tried to flash stock firmware no change seen.
I would be glad if you all can help me.
@ravibhat i have read your thread and my starting problem was same as yours @lost101 please help me as well.Thank You
Ok.Post pics,videos so that we know it's the same problem.
Go to a service centre when you can and share what they've told.
did u use these steps ?
fastboot erase recovery
fastboot flash recovery ur_recover_zip_name.zip
try different versions of recovery, i suggest u use CWM V6.0.4.7
If that works, use the adb sideload feature to flash the ROM
thank you for the reply
@ankur.walia
i tried the erase recovery command this was the output
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
and when i tried to lock bootloader this was the ouput
mrawal031 said:
@ankur.walia
i did not try the erase recovery command but i tried to flash it directly.
ill try this and revert i hope it wouldn't pose a problem if i directly flash the .img file
Click to expand...
Click to collapse
yes, and try the version i mentioned because i was also facing the problem like u and only this specific versions worked for me
still no change
@ankur.walia @ravibhat
i tried the command you told me to. There is no change im unable to boot in flash recovery also now xD.
i also went to the service centre they said there is nothing they can do for this phone as the only thing they know is to flash the stock firmware.
mrawal031 said:
@ankur.walia @ravibhat
i tried the command you told me to. There is no change im unable to boot in flash recovery also now xD.
i also went to the service centre they said there is nothing they can do for this phone as the only thing they know is to flash the stock firmware.
Click to expand...
Click to collapse
are u not able to go in fastboot mode now?
if u are, then ls try different versions of the recoveries...
and yes...what actually is happening? are u able to see the boot logo? its stuck in bootlogo screen?..or is it struck in recovery's logo screen?
are it is not even booting itself?
ankur.walia said:
are u not able to go in fastboot mode now?
if u are, then ls try different versions of the recoveries...
and yes...what actually is happening? are u able to see the boot logo? its stuck in bootlogo screen?..or is it struck in recovery's logo screen?
are it is not even booting itself?
Click to expand...
Click to collapse
I can go to the bootloader after entering stock recovery no combination of keys can display the option.
my phone starts normally shows logo and all booting animation but after that it gets stuck on a blank screen showing nothing and no touch response. I have tried aprox 4-5 variants of custom recoveries but i can flash none of them even after trying your command and getting success written on screen.
mrawal031 said:
I can go to the bootloader after entering stock recovery no combination of keys can display the option.
my phone starts normally shows logo and all booting animation but after that it gets stuck on a blank screen showing nothing and no touch response. I have tried aprox 4-5 variants of custom recoveries but i can flash none of them even after trying your command and getting success written on screen.
Click to expand...
Click to collapse
well if u got the successful execution of recovery flashing then it should go to recovery mode, try holding powe and volume down together for quite some time (5-6 seconds by the clock) and then release it
ankur.walia said:
well if u got the successful execution of recovery flashing then it should go to recovery mode, try holding powe and volume down together for quite some time (5-6 seconds by the clock) and then release it
Click to expand...
Click to collapse
https://drive.google.com/file/d/0B6y6POATHFhrLVhpUThNVUc1VXc/view?usp=sharing
you can see the condition even after flashing the custom recovery i get booted into stock recovery
My phone (2nd nexus5, not my daily driver nexus) is stuck in a bootloop (stuck at the booting animation) after updating via the OTA updtes, never rooted or touched any setting in the dev options in the setting menu.
The phone stays like that for hours, doesn't even reboot on its own, just keeps playing the bootanimation for hours and hours until the battery dies.
I have access to the bootloader, and default(stock) recovery.
tried oem unlock, but it doesn't work, and shows no errors.
Tried hard reset from the stock recovery and got numerous E: Failed to mount ..... errors. (check attached photo)
All attempts to wipe or format anypart of the phone fail with the same error,
ADB side load of a custom recovery ( TWRP ) also failed with the same error.
Please help me out, data loss is not an issue as i had no imp data and used it mainly for calls and emails.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Try flashing twrp.
fastboot flash recovery (ur recovery name).img
Then unmount system from advance and flash a custom rom
pranavmali said:
Try flashing twrp.
fastboot flash recovery (ur recovery name).img
Then unmount system from advance and flash a custom rom
Click to expand...
Click to collapse
It shows an error
FAILED (remote: not supported in locked device)
Like I said, oem unlock doesn't work.
As soon as i give the oem unlock command, it will ask for conformation, after hitting yes,
it will even show LOCK STATE - unlocked.
But as soon as the phone reboots or re-enters bootloader, the phone is back to a locked bootloader.
On unlocking bootloader, flashing TWRP via fastboot, when i enter recovery mode, i am still taken back to the stock recovery.
Try Wug fresh's tool kit! To unlock bootloader
Does the give give an error message when issuing the fastboot oem unlock command?
pranavmali said:
Try Wug fresh's tool kit! To unlock bootloader
Click to expand...
Click to collapse
No effect, still stuck the same way.
below is the live log from the NRT toolkit
Live log initiated [2016-05-19]:
Analyzing factory image; please be patient...
Further extracting contents of factory image package for use in 'Force Flash Mode'...
Checking ADB/FASTBOOT Connectivity
adb devices
fastboot devices
04bfc514002e14ea fastboot
Connectivity Status: Fastboot Device Connected
+ Bootloader Status: Locked.
Checking ADB/FASTBOOT Connectivity
adb devices
03670030215d290e device
fastboot devices
04bfc514002e14ea fastboot
Connectivity Status: Fastboot Device Connected
+ Bootloader Status: Locked.
fastboot oem unlock
Rebooting your device...
and then suck at bootanimation loop
audit13 said:
Does the give give an error message when issuing the fastboot oem unlock command?
Click to expand...
Click to collapse
when i give the fast boot oem unlock command, it will get executed, my phone will ask for me to manually go to the yes key, hit power button to conform,
I am taken back to the bootloader screen, it shows lock state- unlocked
and the word "erasing..." flashes under it for less than 1 second and thats it...no other change what so ever, as soon as i reboot to bootloader or reboot the phone or do anything, the phone is back to the locked bootloader state.
The emmc is damaged or defective and can only be fixed with a motherboard replacement.
audit13 said:
The emmc is damaged or defective and can only be fixed with a motherboard replacement.
Click to expand...
Click to collapse
is there a sure-shot way of determining that my emmc is damaged ..?
the state that my phone is in now, it would make more sense to just buy a new device rather than replace the motherboard.
or
another option i can consider is the thread - http://forum.xda-developers.com/google-nexus-5/help/nexus-5-64gb-t3350533 for getting a new emmc and replacing, but before i take any actions i would like to know that there is no other option left.
Since you now appear to have nothing to lose, try installing the full N5 OTA image:
https://developers.google.com/android/nexus/ota#hammerhead-for-nexus-5-mobile
The instructions are on the page, or NRT has an OTA option (Advanced utilities/Sideload OTA update).
It may not work if your bootloader is genuinely locked or if the EMMC is really fried, but worst case you can't do any more damage, right?
I was attempting to root my OnePlus 7 so that I could increase the volume limits (I'm hearing impaired) via TWRP and then eventually Magisk, however it seems many things went wrong along the way. I managed to get TWRP working on my phone but then it wasn't finding any of my stored memory and therefore the TWRP Zip file I needed to finally root the phone. In my efforts to correct that I have bricked my phone (not sure if it's hard bricked or soft bricked) but currently it will only boot into the fastboot menu and selecting any option brings me right back to the fastboot menu again.
I tried getting back to the TWRP but no luck when I try to boot it I get the error message FAILED (remote: Failed to load/authenticate boot image: Load Error)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
After reading online for a bit of help I thought it might be hard bricked so I tried to use the MSM tool but again I had no luck due to Param Preload - Device not match image
I have attached screenshots for both issues, I've also tried guides for soft bricked OP7P and despite showing as successful they reboot right back into the fastboot menu as if nothing has happened.
Please I'd really appreciate some help I've been trying for days to fix this mess!
Darhk Citadel said:
I was attempting to root my OnePlus 7 so that I could increase the volume limits (I'm hearing impaired) via TWRP and then eventually Magisk, however it seems many things went wrong along the way. I managed to get TWRP working on my phone but then it wasn't finding any of my stored memory and therefore the TWRP Zip file I needed to finally root the phone. In my efforts to correct that I have bricked my phone (not sure if it's hard bricked or soft bricked) but currently it will only boot into the fastboot menu and selecting any option brings me right back to the fastboot menu again.
I tried getting back to the TWRP but no luck when I try to boot it I get the error message FAILED (remote: Failed to load/authenticate boot image: Load Error)
After reading online for a bit of help I thought it might be hard bricked so I tried to use the MSM tool but again I had no luck due to Param Preload - Device not match image
I have attached screenshots for both issues, I've also tried guides for soft bricked OP7P and despite showing as successful they reboot right back into the fastboot menu as if nothing has happened.
Please I'd really appreciate some help I've been trying for days to fix this mess!
Click to expand...
Click to collapse
How did you unlock the boot loader?
tech_head said:
How did you unlock the boot loader?
Click to expand...
Click to collapse
I enabled USB Debugging on my phone and then used "Shift + Right Click" from within the folder with twrp file and used the command "fastboot oem unlock"
Was in this situation. If you have an unlocked bootloader, try to search for the fastboot ROMs on xda. Not sure if there is a 5g version though. With a try. Best of luck.
Darhk Citadel said:
I enabled USB Debugging on my phone and then used "Shift + Right Click" from within the folder with twrp file and used the command "fastboot oem unlock"
Click to expand...
Click to collapse
Look here https://forum.xda-developers.com/oneplus-7-pro/how-to/rom-stock-fastboot-roms-oneplus-7-pro-t3931424
toonstra said:
Look here 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, I tried that this morning perhaps I did it wrong, but when I used the same cmd window as I did to "unlock" the bootloader nothing happened. It went through the process and finally finished with no errors and said "press any key to exit" -But as for my phone it did not reboot in fact there was no change at all, it remained on the bootloader screen as normal. When I tried to reboot for a normal load it looped back to the bootloader, when I tried to reboot to recovery it booted back to recovery. It was as if the fastboot ROM was completely ineffective.
Darhk Citadel said:
Thanks, I tried that this morning perhaps I did it wrong, but when I used the same cmd window as I did to "unlock" the bootloader nothing happened. It went through the process and finally finished with no errors and said "press any key to exit" -But as for my phone it did not reboot in fact there was no change at all, it remained on the bootloader screen as normal. When I tried to reboot for a normal load it looped back to the bootloader, when I tried to reboot to recovery it booted back to recovery. It was as if the fastboot ROM was completely ineffective.
Click to expand...
Click to collapse
So I just tried to flash a recovery.img and I got this error "failed (remote (recovery_a) no such partition)" which leads me to believe that my phone is a lot worse than I originally thought...
Any help would be greatly appreciated I fully accept that I messed this up BIG TIME!
Darhk Citadel said:
So I just tried to flash a recovery.img and I got this error "failed (remote (recovery_a) no such partition)" which leads me to believe that my phone is a lot worse than I originally thought...
Any help would be greatly appreciated I fully accept that I messed this up BIG TIME!
Click to expand...
Click to collapse
Ok so I finally managed to get to the root of the problem and my phone is now back up and running without any issues, I completely missed the correct MSM too package that I needed for my phone and region as I have a UK OnePlus Pro 7 5G I needed to use this specific package to reset my phone back to stock: [OP7PRO 5G EU][OOS 9.5.11 GM27BA]
Appreciate all the help everyone hopefully someone else can use this to avoid making the same mistake I did!