Hello,
I've rooted my Pixel 3 as described here in the forum.
Everything went well and I was booting in TWRP without any problems; Bootloader is still unlocked. I didn't installed a custom ROM or anything else. After I've selcted "restore backup" my backup (which I've made before with TWRP) my phone is now messed up:
It's starting in Bootloader (Warning Screen for unlocked Bootloader) and than is switching on an white screen with Google logo for ca. 3-4 sec. and than it's jumping back into the Bootloader in an endless Loop.
Any idea what I can do to rescue my phone?
Thanks, Mags
MMoes said:
Hello,
I've rooted my Pixel 3 as described here in the forum.
Everything went well and I was booting in TWRP without any problems; Bootloader is still unlocked. I didn't installed a custom ROM or anything else. After I've selcted "restore backup" my backup (which I've made before with TWRP) my phone is now messed up:
It's starting in Bootloader (Warning Screen for unlocked Bootloader) and than is switching on an white screen with Google logo for ca. 3-4 sec. and than it's jumping back into the Bootloader in an endless Loop.
Any idea what I can do to rescue my phone?
Thanks, Mags
Click to expand...
Click to collapse
In bootloader mode can you get your computer to recognize the phone. If so, download the latest update from Google website and install using adb. This will wipe the phone but will get it restored. I've had to do this in my pixel 2 before. I don't have the pixel 3 yet as I just ordered it today.
MMoes said:
Hello,
I've rooted my Pixel 3 as described here in the forum.
Everything went well and I was booting in TWRP without any problems; Bootloader is still unlocked. I didn't installed a custom ROM or anything else. After I've selcted "restore backup" my backup (which I've made before with TWRP) my phone is now messed up:
It's starting in Bootloader (Warning Screen for unlocked Bootloader) and than is switching on an white screen with Google logo for ca. 3-4 sec. and than it's jumping back into the Bootloader in an endless Loop.
Any idea what I can do to rescue my phone?
Thanks, Mags
Click to expand...
Click to collapse
FilthyFord said:
In bootloader mode can you get your computer to recognize the phone. If so, download the latest update from Google website and install using adb. This will wipe the phone but will get it restored. I've had to do this in my pixel 2 before. I don't have the pixel 3 yet as I just ordered it today.
Click to expand...
Click to collapse
You can also edit the flash-all file to remove the -w and not completely wipe your phone. This way, your data will remain and it still resets the important factory stuff.
FilthyFord said:
In bootloader mode can you get your computer to recognize the phone. If so, download the latest update from Google website and install using adb. This will wipe the phone but will get it restored. I've had to do this in my pixel 2 before. I don't have the pixel 3 yet as I just ordered it today.
Click to expand...
Click to collapse
Thanks, I‘ve tried with adb devices & no device found. So obviously my computer doesn‘t recognize the Pixel
sliding_billy said:
You can also edit the flash-all file to remove the -w and not completely wipe your phone. This way, your data will remain and it still resets the important factory stuff.
Click to expand...
Click to collapse
Thanks. Loosing my data isn‘t the Problem. Actually I‘m even not able to connect to the phone and flash anything.
MMoes said:
Thanks. Loosing my data isn‘t the Problem. Actually I‘m even not able to connect to the phone and flash anything.
Click to expand...
Click to collapse
Have you hard powered the device down and then rebooted to BL with key combo to check connectivity?
sliding_billy said:
Have you hard powered the device down and then rebooted to BL with key combo to check connectivity?
Click to expand...
Click to collapse
No, could you please descripe the process what to do exactly. Would love to give it a try. Thank you
MMoes said:
No, could you please descripe the process what to do exactly. Would love to give it a try. Thank you
Click to expand...
Click to collapse
Hold down the power button until the phone completely shuts off. Hold power while holding the volume down button (start by holding the volume down and then immediately start holding the power button - it's is technically holding both at the same time but starting with volume down just a moment before keeps you from pressing power first). That should get you to fastboot.
MMoes said:
Thanks, I‘ve tried with adb devices & no device found. So obviously my computer doesn‘t recognize the Pixel
Click to expand...
Click to collapse
ADB doesn't work when booted to the bootloader. It only works when you're booted to the OS. To see if the computer recognizes the phone when in the bootloader, use fastboot devices instead of adb devices.
sliding_billy said:
Hold down the power button until the phone completely shuts off. Hold power while holding the volume down button (start by holding the volume down and then immediately start holding the power button - it's is technically holding both at the same time but starting with volume down just a moment before keeps you from pressing power first). That should get you to fastboot.
Click to expand...
Click to collapse
Holding the power button didn't had any effect, but holding volume - and holding power button at the same time was starting the bootloader and so I was now able to start TWRP Manager.
So if you could help me from here to fix the OS would be great, e.g. is there any chance to copy the original OS from Google or an custom ROM from my computer (e.g. I wotk on MAC and is there a way to copy via Terminal?) or does TWRP offers any way to reset/ reinstall?
robocuff said:
ADB doesn't work when booted to the bootloader. It only works when you're booted to the OS. To see if the computer recognizes the phone when in the bootloader, use fastboot devices instead of adb devices.
Click to expand...
Click to collapse
Yes, the computer recognizes the phone (via Terminal on my MAC)
MMoes said:
Holding the power button didn't had any effect, but holding volume - and holding power button at the same time was starting the bootloader and so I was now able to start TWRP Manager.
So if you could help me from here to fix the OS would be great, e.g. is there any chance to copy the original OS from Google or an custom ROM from my computer (e.g. I wotk on MAC and is there a way to copy via Terminal?) or does TWRP offers any way to reset/ reinstall?
Click to expand...
Click to collapse
Sorry, but I do not know the Mac commands, but if you are in Fastboot and the device shows/connects it is just a matter of running the flash-all and resetting. If you are not connecting in Fastboot but can get into TWRP, I would start with a reset in TWRP.
sliding_billy said:
Sorry, but I do not know the Mac commands, but if you are in Fastboot and the device shows/connects it is just a matter of running the flash-all and resetting. If you are not connecting in Fastboot but can get into TWRP, I would start with a reset in TWRP.
Click to expand...
Click to collapse
The commands on the MAC are almost the same and with your flash-all (flash.all.sh Mac Command) it worked very well with the factory image from google. Now I'm back in the race and my P3 is running again.
Thank you all guys!
MMoes said:
The commands on the MAC are almost the same and with your flash-all (flash.all.sh Mac Command) it worked very well with the factory image from google. Now I'm back in the race and my P3 is running again.
Thank you all guys!
Click to expand...
Click to collapse
Excellent news. On another note... if all you need from TWRP is to install Magisk to root, you do not need to permanently install TWRP. Just fastboot boot the [twrp].img file, install the Magisk .zip and keep stock recovery.
From messing around, it seems that trying to restore system from twrp is messed up. Data backup works fine. The only other way I got bootlooped was by messing with boot, vbmata, and vendor partitions. Out of those three, I think boot is the most likely to get messed up by normal users. I know this is sorted now, but in the future try to just reflash boot.img and see if it boots.
-The vbmeta and vendor thing is specific because I need to get the radio to work here.
Related
You all probably noticed that if the Settings->Power->Fastboot setting is enabled, Power+Vol_down will not work and the phone will do a standard boot. Is there anyway to force booting the phone into hboot? If not, this is a possible way to get bricked in case your ROM is messed up and the phone's last mode was to Fastboot.
netboy3 said:
You all probably noticed that if the Settings->Power->Fastboot setting is enabled, Power+Vol_down will not work and the phone will do a standard boot. Is there anyway to force booting the phone into hboot? If not, this is a possible way to get bricked in case your ROM is messed up and the phone's last mode was to Fastboot.
Click to expand...
Click to collapse
That's exactly why we leave fastboot off in the settings
Maybe I don't understand the question. Could you not just use:
adb reboot bootloader
or
adb reboot recovery
cntryby429 said:
Maybe I don't understand the question. Could you not just use:
adb reboot bootloader
or
adb reboot recovery
Click to expand...
Click to collapse
You can only use those if adbd is running which means you either were successful in booting into recovery (and you can't do it as power+vol_down doesn't work), or you have a working ROM (see the OP).
xRogerxC said:
That's exactly why we leave fastboot off in the settings
Click to expand...
Click to collapse
I wish it was that simple. The ability to get to the menu seems to be related to the bootloader's ability to access /data. If the bootloader can't get to /data it looks to defaulting to NOT showing the hboot menu. I've noticed this on my phone. I have my phone encrypted which doesn't allow access to /data until you decrypt it. If you cancel out of the decrypt prompt then reboot the phone, you will not be able to power+vol_down (though I never changed the fastboot setting).
netboy3 said:
You all probably noticed that if the Settings->Power->Fastboot setting is enabled, Power+Vol_down will not work and the phone will do a standard boot. Is there anyway to force booting the phone into hboot? If not, this is a possible way to get bricked in case your ROM is messed up and the phone's last mode was to Fastboot.
Click to expand...
Click to collapse
If you are rooted you can use the app quick boot to reboot to hboot without having to do the shutdown but.
Sent from my HTC6525LVW using Tapatalk
dottat said:
If you are rooted you can use the app quick boot to reboot to hboot without having to do the shutdown but.
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
See the OP. Assuming your ROM is messed up and is not booting (happens a lot when your'e a flashoholic), you can't run any apps or even get to adb. I've never seen a phone that will not allow you to always be able to cold-boot into the bootloader. This is a serious problem for folks that plan to experiment with lots of ROM flashing.
netboy3 said:
See the OP. Assuming your ROM is messed up and is not booting (happens a lot when your'e a flashoholic), you can't run any apps or even get to adb. I've never seen a phone that will not allow you to always be able to cold-boot into the bootloader. This is a serious problem for folks that plan to experiment with lots of ROM flashing.
Click to expand...
Click to collapse
In that case you hold power and volume buttons until the phone tells you it's going to restart or vibrates or you see the screen flash. Depending on what mode you are in it will do different things. At this point you can release power and move to only volume down.
If timed correctly you will land in hboot. Practice makes perfect.
Sent from my HTC6525LVW using Tapatalk
dottat said:
In that case you hold power and volume buttons until the phone tells you it's going to restart or vibrates or you see the screen flash. Depending on what mode you are in it will do different things. At this point you can release power and move to only volume down.
If timed correctly you will land in hboot. Practice makes perfect.
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
dottat, thank you for your post. You are correct. This requires quite a bit of proper timing to succeed. To recap: In case you are in fast-boot power mode and/or have your phone encrypted and power+vol_down doesn't get you into hboot:
1. Power down the phone.
2. Hold volume_up and power.
3. Keep holding the above, you should see the animated HTC splash show up.
4. Keep holding the above, the screen will go dark.
5. Once the screen goes dark, quickly release power and volume_up and press volume_down.
6. If timed perfectly, you should land in hboot menu.
Thanks again to dottat for pointing it out.
I recently broke the screen and the touchscreen of my OPO and bought a new Glass+LCD+Digitizer+Middle Frame from Aliexpress. I just installed all the parts and afterwards my OPO booted happily into recovery. Touchscreen and Display etc are working fine. I wiped everything via TWRP 2.8.7.0 and wanted to do a clean install of CM12.1. But no matter what I do now, the phone always(!) boots directly into recovery mode. I can't even get into fastboot! I already tried all sorts of things.. any ideas?
http://forum.xda-developers.com/oneplus-one/general/tool-oneplusrecovery-tool-v1-0-restore-t2991851
use this url
If I power off my phone and plug it into the computer it immediately turns on. If I leave it plugged in and then shut it off via recovery, it reboots instead of turning off. Only if I unplug it from the computer, I can shut it off. So I'm afraid this link won't work for me
Bannix said:
If I power off my phone and plug it into the computer it immediately turns on. If I leave it plugged in and then shut it off via recovery, it reboots instead of turning off. Only if I unplug it from the computer, I can shut it off. So I'm afraid this link won't work for me
Click to expand...
Click to collapse
did you press and hold volume up when plugging it to the computer?
Yes I tried everything. It will only boot in recovery.
brah it will work. i was in same situation. it fixed my phone. try it.
I managed to do the whole "unbrick" process... now my recovery looks a little bit different but I still can't get into the bootloader!
When I boot up the phone, a split second before it enters recovery mode this picture shows up. The recovery is now stock CM recovery. ADB now doesn't work either..
TWRP has an option to reboot to bootloader. Did you try that as well?
Yes, I did. It booted into recovery...
Bannix said:
Yes, I did. It booted into recovery...
Click to expand...
Click to collapse
When you connect your phone to your PC while it's in recovery does it show up as a drive?
Heisenberg said:
When you connect your phone to your PC while it's in recovery does it show up as a drive?
Click to expand...
Click to collapse
No, it doesn't. However if go into the "install update via adb sideload" option in the recovery, the phone gets recognized as A0001, but the driver on my PC doesn't work. ADB doesn't work either in this case.
deletedpost
I did it with color OS, and now the phone always boots into ColorOS recovery I replaced the ColorOS recovery.img with the TWRP one, and now i got TWRP and ADB back. Phone gets recognized as SD Card now. Could it be that something on the hardware side of things broke my bootloader?
Please help
Bannix said:
I did it with color OS, and now the phone always boots into ColorOS recovery I replaced the ColorOS recovery.img with the TWRP one, and now i got TWRP and ADB back. Phone gets recognized as SD Card now. Could it be that something on the hardware side of things broke my bootloader?
Click to expand...
Click to collapse
I got exactly the same now , let me know what worked for you?
Bannix said:
I did it with color OS, and now the phone always boots into ColorOS recovery I replaced the ColorOS recovery.img with the TWRP one, and now i got TWRP and ADB back. Phone gets recognized as SD Card now. Could it be that something on the hardware side of things broke my bootloader?
Click to expand...
Click to collapse
Well its possible, that one of the volume butten is pressed permanent(that u even don't take notice) due bad hardware and replacement. Therefore, the device would only boot into recovery, no matter what u try. Take a voltmeter and check the buttons.
BTW: stop using these dirty "toolbox" around here, they are pure cancer for your device
Hey, thanks for your reply. The volume down button being permanently pressed was actually the case! I found out myself and fixed it by soldering a new volume flex cable. Phone works fine again
Hi everyone im stuck on the resurection of my device (moto g 2013 8GB updated to 5.1 with [5.1 GPE 1 click] from This forum.
I've tried everything or almost for now, cant get it out of that loop.
*Battery pulling.
*hard buttons combinations.
*fastboot and ADB. (not in fastboot mode so.. And as i did flash de 1click before the loop USB Dbgn isn't enabled)
*i think i've tried every toolkit on this forum.
*Raped google search for over a week trying every posible method-
*Only thing left is to take it to church for a blessing. but im not a believer D:
ADD: i've rooted with a "boot.img" from this forum i think it was a 2015 file.
before this i had not 1 issue with the phone. just unlockd the bootloader a few days ago and updated to 5.1 from 5.0.2 becouse of a wifi issue (unknow mac adress) i had to reboot it like 10 times until it appeared again (original mac adress from device, still wrote it down i have it somewhere.)
I think this would be my first post on this forum and it took me over a week to do it becouse this (asking you-comunity) is my last resource.
PS: i had it going betwen 5.0.2 and 5.1 like 4 times to try solving the wifi issue.. only thing it got me was the "line" on the screen like if it where a problem with vertical sync. (i think you are all very familiar with that issue after downgrading the kernel i think.)
the phone just turns it self on everytime. (everytime)
i was able to boot into recovery before the last flash touching the place were the hardware volume button goes (with a neddle) untill it didnt workd anymore and i send it to a store to repair the volume rockers. still no recovery or bootloader boot.
my pc (laptop with 7-32bit recognices it as xt1032. and the one with xp as MTP.)
I've installed every posible thing that i found to bring it back to life even the android sdk full every pkg from 5.0.2 to 5.1 and extras, Motorola drivers and ADB. tried online searching automated from windows and listing it from a folder with the google one. tried adding the hardware manualy and have every ADB thing that i found on device mng but everyone is wit a yellow triangle. (No USB Debuging enabled so why bother anymore.)
I think that's about it.
You seem to be making things massively over-complicated.
Flash latest TWRP from here: http://forum.xda-developers.com/moto-g/development/recovery-twrp-2-8-2-0-touch-recovery-t2980621
Example fastboot command:
fastboot flash recovery twrp.img
If you cannot enter TWRP, use ONLY this fastboot command:
fastboot erase userdata
Via TWRP, flash latest GPE Optimized ROM from here: http://forum.xda-developers.com/moto-g/development/rom-stock-motorola-lollipop-rom-t3017510
i m sorry for my english, isnt my native lang. And for making it over complicated.
i cant enter fastboot mode or give any order to the phone trough fastboot on a console.
I have installed a TWRP touch, just cant acces it. dont know if it is the hardware button (Vol -) or what.
so it dosnt show up on fastboot devices nor adb devices.
am i not understanding something ?
Thanks for replying and taking the time to help!
Enter fastboot mode by turning on phone while holding Volume Down.
lost101 said:
Enter fastboot mode by turning on phone while holding Volume Down.
Click to expand...
Click to collapse
tried again just in case. No luck, wont boot into recovery or bootloader mode. vol (-) or power and vol (-)
it just "tries" to boot up normaly and gets stuck on "android starting" untill "initializing apps" 4 colours flying and reboots again.
dieguitwow1 said:
tried again just in case. No luck, wont boot into recovery or bootloader mode. vol (-) or power and vol (-)
it just "tries" to boot up normaly and gets stuck on "android starting" untill "initializing apps" 4 colours flying and reboots again.
Click to expand...
Click to collapse
If the volume rocker is not broken, then you should be able to enter fastboot mode. Hold power button until phone turns off completely.
If the volume rocker is not broken, then you should be able to enter fastboot mode. Hold power button until phone turns off completely.
Click to expand...
Click to collapse
did that, tried pulling the battery off and holding the keys (down and power or just vol down) and starting it. no way it goes into bootloader or recovery. When i do any of those things the phone just powers back up it self and boots into system or tries to, and get stuck in bootloop.
Im gonna try a gtag cable or something like that tomorrow from a friend. would it work to send it to bootloader or recovr?
dieguitwow1 said:
did that, tried pulling the battery off and holding the keys (down and power or just vol down) and starting it. no way it goes into bootloader or recovery. When i do any of those things the phone just powers back up it self and boots into system or tries to, and get stuck in bootloop.
Im gonna try a gtag cable or something like that tomorrow from a friend. would it work to send it to bootloader or recovr?
Click to expand...
Click to collapse
You said you had the volume rocker repaired - but it seems at least, vol down is not working. I have no experience with jtag kits or commands.
lost101 said:
You seem to be making things massively over-complicated.
Flash latest TWRP from here: http://forum.xda-developers.com/moto-g/development/recovery-twrp-2-8-2-0-touch-recovery-t2980621
Example fastboot command:
fastboot flash recovery twrp.img
If you cannot enter TWRP, use ONLY this fastboot command:
fastboot erase userdata
Via TWRP, flash latest GPE Optimized ROM from here: http://forum.xda-developers.com/moto-g/development/rom-stock-motorola-lollipop-rom-t3017510
Click to expand...
Click to collapse
lost101 said:
Enter fastboot mode by turning on phone while holding Volume Down.
Click to expand...
Click to collapse
lost101 said:
You said you had the volume rocker repaired - but it seems at least, vol down is not working. I have no experience with jtag kits or commands.
Click to expand...
Click to collapse
i think it's not repaired properly, or the last time i flashed it fastboot might have send a command like "fastboot normalboot" or something like that. Would that be stoping me from entering recovery mode or fastboot?
dieguitwow1 said:
i think it's not repaired properly, or the last time i flashed it fastboot might have send a command like "fastboot normalboot" or something like that. Would that be stoping me from entering recovery mode or fastboot?
Click to expand...
Click to collapse
If you power phone off completely, then no commands are remembered. The button is broken.
lost101 said:
If you power phone off completely, then no commands are remembered. The button is broken.
Click to expand...
Click to collapse
Thanks! so, what should i do now? is there any way to fix it or bypass it ?
i was "touching" the button with a niddle until it stoped working is there a fix for it? :fingers-crossed:
dieguitwow1 said:
Thanks! so, what should i do now? is there any way to fix it or bypass it ?
i was "touching" the button with a needle until it stopped working is there a fix for it? :fingers-crossed:
Click to expand...
Click to collapse
Sorry, I can't help you with that. If you know someone good with a soldering iron, maybe they can fix it - otherwise, try another repair shop.
its still seen by my PC with XP. As xt1032 on the bootloop can i do something ? moto device mngr starts with de Moto logo on the sys tray..
dieguitwow1 said:
its still seen by my PC with XP. As xt1032 on the bootloop can i do something ? moto device mngr starts with de Moto logo on the sys tray..
Click to expand...
Click to collapse
adb reboot bootloader
lost101 said:
adb reboot bootloader
Click to expand...
Click to collapse
even if "USB Debuging" isn't enabled?
Edit: Result= [ Error: device ´<null>´ not found ]
dieguitwow1 said:
even if "USB Debuging" isn't enabled?
Edit: Result= [ Error: device ´<null>´ not found ]
Click to expand...
Click to collapse
Yes, USB Debugging would need to be enabled.
lost101 said:
Yes, USB Debugging would need to be enabled.
Click to expand...
Click to collapse
so, apart from taking it to repair again for the button, what can i do?:fingers-crossed:
dieguitwow1 said:
so, apart from taking it to repair again for the button, what can i do?:fingers-crossed:
Click to expand...
Click to collapse
I am not aware of any other options.
i managed to recover the phone it works normaly but screen goes off and on all the time, every 5 sec. Except on Bootloader Mode.
dieguitwow1 said:
i managed to recover the phone it works normaly but screen goes off and on all the time, every 5 sec. Except on Bootloader Mode.
Click to expand...
Click to collapse
What has changed? Did you get the vol button fixed?
I (stupidly) decided to repartition my Moto G3 using this guide. Now, when trying to turn my phone on, the screen stays blank and there's no indication that it's working but it reboots once every two to five seconds or so (telling you how I can tell it's rebooting would be a long story and I'm sure it's irrelevant to the issue).
Am I just hooped or is there hope?
Can you boot in to bootloader?
If yes just flash stock firmware (should include partition layout)
HelpMeruth said:
Can you boot in to bootloader?
If yes just flash stock firmware (should include partition layout)
Click to expand...
Click to collapse
Nope, all attempts to get into the bootloader fail. The screen just stays blank with no indication that it's doing anything at all (although behind the scenes it's actually rebooting once every few seconds). My (uneducated) guess is it can't even access any of the partitions.
sensi277 said:
Nope, all attempts to get into the bootloader fail. The screen just stays blank with no indication that it's doing anything at all (although behind the scenes it's actually rebooting once every few seconds). My (uneducated) guess is it can't even access any of the partitions.
Click to expand...
Click to collapse
Try to connect it to your pc and see if adb/fastboot sees the device.
michkost858 said:
Try to connect it to your pc and see if adb/fastboot sees the device.
Click to expand...
Click to collapse
adb shell doesn't see anything.
sensi277 said:
adb shell doesn't see anything.
Click to expand...
Click to collapse
Hey, since according to what you say your device is currently stuck in a boot-loop, I suggest you first take out the battery out for a few seconds and then put it back then enter recovery mode using the device buttons right after. only then connect your device to PC and use adb...
Jewshua said:
Hey, since according to what you say your device is currently stuck in a boot-loop, I suggest you first take out the battery out for a few seconds and then put it back then enter recovery mode using the device buttons right after. only then connect your device to PC and use adb...
Click to expand...
Click to collapse
Or, since the battery is not officially removable, wait till the battery dies and then try to boot into bootloader.
Volume down broken
Hi! My mom's phone started to heavily slow down with its stock firmware so I tried to install a custom firmware since I installed one on mine and we both have Moto G3s.
Thing is, it bricked and the volume down button is dead since a few month so I don't have access to the bootloader, otherwise I would just flash the stock firmware. Only buttons working are volume up and on/off buttons.
Is there any way to access the bootloader with this button or am I screwed on this one ?
tyty48 said:
Hi! My mom's phone started to heavily slow down with its stock firmware so I tried to install a custom firmware since I installed one on mine and we both have Moto G3s.
Thing is, it bricked and the volume down button is dead since a few month so I don't have access to the bootloader, otherwise I would just flash the stock firmware. Only buttons working are volume up and on/off buttons.
Is there any way to access the bootloader with this button or am I screwed on this one ?
Click to expand...
Click to collapse
Can you boot the ROM?
If so, you should be able to turn on usb debugging and run 'adb reboot recovery' and reflash from there
---------- Post added at 05:27 PM ---------- Previous post was at 05:26 PM ----------
sensi277 said:
adb shell doesn't see anything.
Click to expand...
Click to collapse
what about fastboot devices (with admin/root privileges) ?
Hello There,
Recently, I had brought an OnePlus Nord 2T, Indian Variant specifically. I was trying to root the device by installing TWRP but the TWRP wasn't having any access to the storage because I had wiped the Internal Storage in TWRP before I could do that, which didn't give me any access to the storage of the device. Even if I connected my PC.... Or Disabling/Re-Enabling MTP.
Long story short, I eventually gave up and decided to try again sometime later and proceeded to lock the bootloader. But after relocking the BL the phone would boot and show the error
"The current image(boot/recovery) have been destroyed". I have tried everything to get it to boot into Fastboot but it just won't boot into it.
Pressing Volume Down + Volume Up + Power Button will only display the same error with a small "Recovery Mode" at the bottom left of the screen! I could have tried booting from Recovery but it just doesn't works cause I think that there is no stock recovery because the phone hadn't booted to the OOS yet. Any help as to how can i get it to boot into fastboot mode???? Please!!!!!!!!
Please anybody respond!
The current image(boot/recovery) have been destroyed!
I recently tried to unroot my Oneplus Nord 2T and after locking the bootloader the phone entered this state. There is no connection between my phone and pc. Pressing Volume Down+Power Button brings back to same page. Urgent need help. Edit: The...
forum.xda-developers.com
PattasuBalu said:
The current image(boot/recovery) have been destroyed!
I recently tried to unroot my Oneplus Nord 2T and after locking the bootloader the phone entered this state. There is no connection between my phone and pc. Pressing Volume Down+Power Button brings back to same page. Urgent need help. Edit: The...
forum.xda-developers.com
Click to expand...
Click to collapse
There is no MSM tool for the device! I don't know how can I fix it
ArmashOnXDA said:
There is no MSM tool for the device! I don't know how can I fix it
Click to expand...
Click to collapse
There is no fix currently for this problem. The only way to fix it now is to give it to a oneplus repair shop.
PattasuBalu said:
There is no fix currently for this problem. The only way to fix it now is to give it to a oneplus repair shop.
Click to expand...
Click to collapse
Ahhhhhhhhh- That sucks. OnePlus isn't the same as it once used to be. Is OnePlus ever even gonna release the blessed keys to the public to help thelucky one's who managed to brick their device?
ArmashOnXDA said:
Hello There,
Recently, I had brought an OnePlus Nord 2T, Indian Variant specifically. I was trying to root the device by installing TWRP but the TWRP wasn't having any access to the storage because I had wiped the Internal Storage in TWRP before I could do that, which didn't give me any access to the storage of the device. Even if I connected my PC.... Or Disabling/Re-Enabling MTP.
Long story short, I eventually gave up and decided to try again sometime later and proceeded to lock the bootloader. But after relocking the BL the phone would boot and show the error
"The current image(boot/recovery) have been destroyed". I have tried everything to get it to boot into Fastboot but it just won't boot into it.
Pressing Volume Down + Volume Up + Power Button will only display the same error with a small "Recovery Mode" at the bottom left of the screen! I could have tried booting from Recovery but it just doesn't works cause I think that there is no stock recovery because the phone hadn't booted to the OOS yet. Any help as to how can i get it to boot into fastboot mode???? Please!!!!!!!!
Click to expand...
Click to collapse
What you need to do if you have a data Cable is connect to the computer that way you can install adv and boot into fastboot
791853 said:
What you need to do if you have a data Cable is connect to the computer that way you can install adv and boot into fastboot
Click to expand...
Click to collapse
Could you explain it more in detail? Like giving me the exact instructions as to what i have to do.
Also, What do you mean by "adv"?
791853 said:
What you need to do if you have a data Cable is connect to the computer that way you can install adv and boot into fastboot
Click to expand...
Click to collapse
This will not work if you have a bad boot partition. There was a way to flash boot.img via brom mode but it is patched now. So only now is to give it to Oneplus service center.
PattasuBalu said:
This will not work if you have a bad boot partition. There was a way to flash boot.img via brom mode but it is patched now. So only now is to give it to Oneplus service center.
Click to expand...
Click to collapse
How long does the service center take to fix the device? Hours? Days? Months?
It usually takes 1-2 days. If you are lucky you get it fixed on the spot.
I had the same issue. Got a new device from my provider in exchange.
Maybe brom mode could work in your case.
Your build has to be A.14 or lower as A.15 received the patch.