Related
got a bricked N5
tried to install stock from fastboot but after each reboot bootloader relocks
so wanted to install TWRP and go from there
Code:
C:\>adb2\fastboot flash recovery recovery-twrp-3.0.2.0-hammerhead.img
target reported max download size of 1073741824 bytes
sending 'recovery' (14524 KB)...
OKAY [ 0.629s]
writing 'recovery'...
OKAY [ 1.104s]
finished. total time: 1.736s
but when i boot to recovery get stock 6.0.1 recovery
ideas?
iakovl said:
got a bricked N5
tried to install stock from fastboot but after each reboot bootloader relocks
so wanted to install TWRP and go from there
but when i boot to recovery get stock 6.0.1 recovery
ideas?
Click to expand...
Click to collapse
Since it's keep relocking bootloader, it's time to say goodbye, unfortunately. Memory chip is done.
Sent from my Nexus 5 using XDA Labs
Any hope left? Goes to boot menu. Goes to recovery but just stuck on bootloop
Sent from my SM-N920I using Tapatalk
iakovl said:
Any hope left? Goes to boot menu. Goes to recovery but just stuck on bootloop
Click to expand...
Click to collapse
As far as I've been reading about that exact problem, no hope. It was always the same answer, eMMC is damaged.
Sent from my Nexus 5 using XDA Labs
When unlocking the bootloader, it should take more than a few seconds to format and reset. If the process is done in a few seconds, this is also an indication the memory chip is defective.
I have seen threads but nothing related to the 6.0.1 version. Please do help
jerry94 said:
I have seen threads but nothing related to the 6.0.1 version. Please do help
Click to expand...
Click to collapse
6.0 or 6.0.1... no difference, must do manual systemless install
acejavelin said:
6.0 or 6.0.1... no difference, must do manual systemless install
Click to expand...
Click to collapse
how to do that?
Already answered google it
Sent from my MotoG3 using Tapatalk
flash supersu zip in twrp.. to simple
HelpMeruth said:
flash supersu zip in twrp.. to simple
Click to expand...
Click to collapse
This doesn't work... if you just flash the latest SuperSU in TWRP, a 3rd/4th Gen Moto device will fail to boot because SuperSU's install script does not recognize that this device must have a systemless install. You must start TWRP and before flashing go to Advanced - Terminal and enter "echo SYSTEMLESS=true>>/data/.supersu" so the SuperSU install script will parse the file and know it has to do a systemless install.
jerry94 said:
I have seen threads but nothing related to the 6.0.1 version. Please do help
Click to expand...
Click to collapse
Check this tutorial
forum.xda-developers.com/2015-moto-g/general/guide-install-twrp-root-xposed-t3294588
Or this one(better)
forum.xda-developers.com/2015-moto-g/general/root-how-to-root-moto-g-2015-android-t3320113e
Nikos dima said:
Check this tutorial
forum.xda-developers.com/2015-moto-g/general/guide-install-twrp-root-xposed-t3294588
Or this one(better)
forum.xda-developers.com/2015-moto-g/general/root-how-to-root-moto-g-2015-android-t3320113e
Click to expand...
Click to collapse
C:\Program Files\Minimal ADB and Fastboot>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.313s]
booting...
FAILED (remote failure)
finished. total time: 0.391s
C:\Program Files\Minimal ADB and Fastboot>fastboot flash recovery recovery.img
target reported max download size of 268435456 bytes
sending 'recovery' (8122 KB)...
OKAY [ 0.313s]
writing 'recovery'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.344s
C:\Program Files\Minimal ADB and Fastboot>
I tried to flash Twrp but iam getting this
Root 6.0.1
jerry94 said:
I have seen threads but nothing related to the 6.0.1 version. Please do help
Click to expand...
Click to collapse
I was also facing the same problem First of all u need to unlock bootloader then at bootloader "fastboot boot recovery.img" change your name twrp to recovery after that you will gets boot into twrp from there flash https://www.androidfilehost.com/?fid=24269982087018189 this file
Hit like if I'm helped you
I followed all the steps of unlocking the bootloader using AdB and Fastboot. After I enter my unique key it sends some commands rather than showing that the device is unlocked.
jerry94 said:
I followed all the steps of unlocking the bootloader using AdB and Fastboot. After I enter my unique key it sends some commands rather than showing that the device is unlocked.
Click to expand...
Click to collapse
Check this video to unlock bootloader. https://youtu.be/BCRpCEtcZ_c and if you are getting errors just search in google for solution
jerry94 said:
I followed all the steps of unlocking the bootloader using AdB and Fastboot. After I enter my unique key it sends some commands rather than showing that the device is unlocked.
Click to expand...
Click to collapse
Can you screenshot it and post it here?
Sent from my Motorola XT1575 using XDA Labs
acejavelin said:
Can you screenshot it and post it here?
Sent from my Motorola XT1575 using XDA Labs
Click to expand...
Click to collapse
I have unlocked the bootloader and flashed twrp now. It opened the twrpmode.i booted the fone.But after that while opening the recovery mode in fastboot it is showing 'no command'
jerry94 said:
I have unlocked the bootloader and flashed twrp now. It opened the twrpmode.i booted the fone.But after that while opening the recovery mode in fastboot it is showing 'no command'
Click to expand...
Click to collapse
If you are getting "No command" that is not TWRP, it is the factory recovery...
When you install TWRP with `fastboot flash recovery twrp.img` you must start TWRP, allow it to make changes to the system, then go to TWRP's reboot menu and select Reboot to Recovery. This action will permanently set TWRP as the recovery, otherwise the OS has a script which will restore the stock recovery on boot.
Proper way to flash TWRP, in my opinion, on a new (to TWRP) Moto device once the bootloader is unlocked:
1) fastboot boot twrp.img
2) do NOT tick "Never show this screen again on boot" and select Keep Read Only button
3) do a complete backup in TWRP, preferably to the microSD card. Make a copy of this backup and store it away safely for possible future use and keep a copy on the device if possible
4) reboot into bootloader
5) fastboot flash recovery twrp.img
6) start Recovery (TWRP)
7) tick "Never show this screen again on boot" and swipe to allow modification
8) go to Reboot and select Recovery **IMPORTANT** this step allows TWRP to "lock" itself in and prevent the OS from replacing it with the stock recovery again
9) TWRP should start again, and it should not prompt you at all and just go to the TWRP menu
10) Do what you wish in TWRP (flash SuperSU, install ROM, or whatever) if anything
11) Reboot - System
Replace twrp.img with the appropriate filename from http://twrp.me for the device. If you have already made changes to the system, just start at step #4
acejavelin said:
<< Proper way to flash TWRP, in my opinion, on a new (to TWRP) Moto device once the bootloader is unlocked:
1) fastboot boot twrp.img
2) do NOT tick "Never show this screen again on boot" and select Keep Read Only button
3) do a complete backup in TWRP, preferably to the microSD card. Make a copy of this backup and store it away safely for possible future use and keep a copy on the device if possible
4) reboot into bootloader
5) fastboot flash recovery twrp.img
6) start Recovery (TWRP)
7) tick "Never show this screen again on boot" and swipe to allow modification
..
..
.. >>
Click to expand...
Click to collapse
I've seen these steps a few times (OK, many times, with all the threads started on this exact question).
I'm just curious.. Why does it work? i.e. How is rebooting into TWRP without installing it, then immediately turning around, installing it, and running it... how is that different from just installing it first thing and running it? Like, what's going on internally that makes those two things different?
Thanks x
Sent from my Nexus 7 using XDA Labs
beachfl said:
I've seen these steps a few times (OK, many times, with all the threads started on this exact question).
I'm just curious.. Why does it work? i.e. How is rebooting into TWRP without installing it, then immediately turning around, installing it, and running it... how is that different from just installing it first thing and running it? Like, what's going on internally that makes those two things different?
Thanks x
Sent from my Nexus 7 using XDA Labs
Click to expand...
Click to collapse
OK... Booting TWRP without installing has nothing to do with functionality of TWRP, it is only to get a clean backup or if you want to root without installing TWRP. TBH, this entire piece is optional and could be skipped, but if you can get a clean backup it sure can makes things easier down the road.
When you flash TWRP, it is flashed... it is written into the recovery partition of your device, but if you start the operating system at this point there is a script (or something, going from my memory of the Nexus 4 which has a script that sat in /system that ran on each boot, so this has been an issue for a while in some devices) that re-writes the recovery it isn't "official". But, but flashing TWRP, allowing it to make changes, then rebooting into TWRP again, it gives TWRP a chance to do something that stops the restoring to official process to stop. I am not sure of the specific details, and I am not sure it really matters, but it works.
acejavelin said:
... Booting TWRP without installing has nothing to do with functionality of TWRP.. .
Click to expand...
Click to collapse
I get that thank you!
Sent from my Nexus 7 using XDA Labs
Going through some of the threads here got me as far as being able to use fastboot on my bricked Shield.
I would like to ask if anyone can give me some pointers what to try next.
The previous owner tried to flash Lineage OS onto the Tablet using CWM but this failed and he probably wiped some needed partition.
I tried to flash new partitions and this works but I can not start the Shield and it won't boot into CWM. The strange thing is that I tried flashing TWRP and even though that started it did not boot through. And after a simple Shield reboot the CWM logo popped upmagain.....:confused
I was convinced I could fix this but I am beginning to think that this Tablet is a goner...
Any thoughts would ne appreciated.
What happens if you download an original recovery image from Nvidia for your model, and flashboot flash all 5 (recovery, boot, system, userdata, blob)? Do you get any fastboot errors? If the partition structure is corrupted, you'll see some sort of error message.
If the blob is messed up sometimes TWRP won't start. I suggest getting a factory image and trying again, then giving it a long time to boot. Once mine took 20 minutes at the Nvidia screen.
I did try flashing the original image from Nvidia including the other 4 images. One of the first things I tried. I woyld like to get it back to factory default. This went without issues an no errors. I might not have given it enough tine to but but still CWM seems to be on.
Will give it another try and post a screenshot.
Sent from my SM-G935F using Tapatalk
Here is a dump of the flash log. After flashing I reboot and the CWM logo pops up after a few minutes and gets stuck.
D:\Downloads\Shield Fix\Drivers\ADB FastBoot\Minimal ADB and Fastboot>fastboot flash recovery recovery.img
target reported max download size of 100663296 bytes
sending 'recovery' (9758 KB)...
OKAY [ 0.384s]
writing 'recovery'...
OKAY [ 0.320s]
finished. total time: 0.709s
D:\Downloads\Shield Fix\Drivers\ADB FastBoot\Minimal ADB and Fastboot>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.394s]
booting...
OKAY [ 0.017s]
finished. total time: 0.417s
Think it is done for, after flashing TWRP numerous times it let me get to the start screen for TWRP it then hangs. When you reboot the Shield and want to go to the recovery again you get the dead android.
PS. I can sometimes get into TWRP but it fails on everything I do. Would there be a terminal solution for this? Like re-creating partitions?
Unlock your bootloader?
Sent from my ZTE A2017U using Tapatalk
It is already unlocked I am afraid.
Sent from my SM-G935F using Tapatalk
sn0r said:
It is already unlocked I am afraid.
Sent from my SM-G935F using Tapatalk
Click to expand...
Click to collapse
Try to flash the attached file. Remember to unzip it first! Flash with:
"fastboot flash dtb tegra124-tn8-p1761-1270-a04-e-battery.dtb"
Flashed the battery file and did another flash of NVIDIA's recovery image and even-tough it says everything is flashed correctly when I reboot I get the CWM logo and nothing more. When I do get into TWRP and try to flash a ROM I get messages errors like attached.
sn0r said:
Flashed the battery file and did another flash of NVIDIA's recovery image and even-tough it says everything is flashed correctly when I reboot I get the CWM logo and nothing more. When I do get into TWRP and try to flash a ROM I get messages errors like attached.
Click to expand...
Click to collapse
Then my guess would be some problems with the internal storage which may not be repairable.
Using fastboot try the following
Fastboot erase cache
Fastboot format cache
Fastboot format userdata
Make sure your tablet is in bootloader mode first though.
Sent from my pa_osprey using Tapatalk
My Honor View10 is stuck at 'Your device is booting now', cannot enter recovery. I tried rectifying my twrp that couldn't unmount anything and wiped up almost everything, but ended up with a boot loop.
Now my device is stuck at 'Your device has been unlocked and can't be trusted. Your device is booting now' screen. I tried using the dload method to restore everything back but the device won't go past this screen.
I tried flashing it using fastboot mode by flashing system, ramdisk and what not, did get a success every time, still, the device won't go past this.
I need genuine help on this, please. Anyone? @2WildFirE? @Einwod? @shashank1320 @oreopie
All this perhaps happened because I tried changing the file system of data and system from twrp.
ankan1993 said:
My Honor View10 is stuck at 'Your device is booting now', cannot enter recovery. I tried rectifying my twrp that couldn't unmount anything and wiped up almost everything, but ended up with a boot loop.
Now my device is stuck at 'Your device has been unlocked and can't be trusted. Your device is booting now' screen. I tried using the dload method to restore everything back but the device won't go past this screen.
I tried flashing it using fastboot mode by flashing system, ramdisk and what not, did get a success every time, still, the device won't go past this.
I need genuine help on this, please. Anyone? @2WildFirE? @Einwod? @[email protected]
All this perhaps happened because I tried changing the file system of data and system from twrp.
Click to expand...
Click to collapse
Why you tried changing filesystem on data?
Twrp isn't ready for pie ? atm
Flash stock recovery and erecovery, then boot to erecovery and restore from there
2WildFirE said:
Why you tried changing filesystem on data?
Twrp isn't ready for pie ? atm
Flash stock recovery and erecovery, then boot to erecovery and restore from there
Click to expand...
Click to collapse
Because custom recovery wouldn't mount anything.
Had no idea that twrp isn't ready for pie.
For both stock and ereccovery, do I use ramdisk_recovery command?
2WildFirE said:
Flash stock recovery and erecovery, then boot to erecovery and restore from there
Click to expand...
Click to collapse
How exactly would one go about this?
fastboot flash erecovery_ramdisk ERECOVERY_RAMDI.img for example only results in FAILED (remote: 'Command not allowed').
Bootloader is unlocked.
If I'm right, try fastboot flash erecovery erecovery.img
2WildFirE said:
If I'm right, try fastboot flash erecovery erecovery.img
Click to expand...
Click to collapse
Sadly there is no erecovery.img and if i try to flash either of the many erecovery files into what i assume would be their respective partitions i get the same error.
Which i thought was a good sign because that might have meant that i couldn't have ****ed them up. But maybe it isn't.
OK try erecovery ramdisk and erecovery kernel to flash
PHP:
fastboot flash erecovery_kernel ERECOVERY_kerne.img
Sending 'erecovery_kernel' (24576 KB) OKAY [ 0.587s]
Writing 'erecovery_kernel' FAILED (remote: 'Command not allowed')
Finished. Total time: 0.614s
for example, the result is always the same.
2WildFirE said:
Why you tried changing filesystem on data?
Twrp isn't ready for pie ? atm
Flash stock recovery and erecovery, then boot to erecovery and restore from there
Click to expand...
Click to collapse
UPDATE: When I reboot the smartphone it displays "Data partition was damaged seriously! and you are recommended to format it to recover your phone".
Smartphone works, but even after a factory reset it still displays that message when it boots up it gets stuck at 'Booting up'.
What can I do @2WildFirE?
180190 said:
PHP:
fastboot flash erecovery_kernel ERECOVERY_kerne.img
Sending 'erecovery_kernel' (24576 KB) OKAY [ 0.587s]
Writing 'erecovery_kernel' FAILED (remote: 'Command not allowed')
Finished. Total time: 0.614s
for example, the result is always the same.
Click to expand...
Click to collapse
Because this is not the right command to give. I am not sure what the right command would be though.
Okay, so I have recovered my phone after spending a sleepless night working on it.
Tried several combinations to see this resolved.
But, what really worked out for me was that I discharged my device twice and kept trying flashing stock rom and several relative recoveries.
After flashing stock recovery I discharged my device. Once it came back, it took me to erecovery.
From there, I started downloading the file from the recovery and did a reboot after the installation.
My Honor is working fine now.
ankan1993 said:
But, what really worked out for me was that I discharged my device twice and kept trying flashing stock rom and several relative recoveries.
After flashing stock recovery I discharged my device.
Click to expand...
Click to collapse
What exactly have you done?
Sinerty said:
What exactly have you done?
Click to expand...
Click to collapse
Flashed the 9.0 full ota files several times, flashed full otas of 8.0. Flashed a random recovery from an older ota. I then discharged my device as I was totally out of options. When I put it on charge it turned back on and after few minutes took me to erecovery.
And now I cannot root my device as twrp isn't there for pie yet. Honor sucks.
Thread closed since it's a duplicate.
Please read here: https://forum.xda-developers.com/honor-view-10/help/honor-view10-stuck-device-booting-enter-t3889376
My OnePlus 7 Pro keep booting into fastboot mode. Neither I can access recovery nor can start the phone. It's always comes back to recovery.
Please help me getting it done.
Bootloader is unlocked.
You haven't given enough info, tell us step by step how your "Bootloader is unlocked".
We would need to know if you did it properly, you probably need to go into the recovery and perform a "Full wipe". Unlocking the bootloader usually does that anyway.
The normal method is:
Enabled developer settings by pressing the version number in the about section 7 times and entering your pin
Copy the adb developer folder from the mounted OnePlus driver partition you usually get on your computer when attaching the phone, into a folder on your hard drive, and enable adb in developer settings.
In developer settings enable "OEM unlocking"
Reboot into fastboot mode
Open a command window (with admin privileges) in the folder you copied to your hard drive (In Windows, hold down shift and right click inside the folder, then click "Open Command Window..."
Run the command "fastboot oem unlock"
Accept the prompt shown on the phone
This will wipe the phone back to factory reset so ensure you have backed up your data, although you should be doing that before you even start.
Flash the appropriate TWRP recovery partition (which afaik isn't even available yet so I'm not sure why you would unlock the bootloader so soon to be honest
If you didn't perform those steps or performed them in the wrong order then you've done it wrong.
Performing a factory reset in the recovery partition may get it booting again but it's hard to know with the minimal information you've provided.
Although again, why are you unlocking the bootloader when there hasn't been a TWRP version released yet? You won't be able to flash anything, not even Magisk.
I've unlocked bootloader by command of OEM unlocking.
After than the unlock, I rebooted it's again And installed some Magisk file, which made it stuck at fastboot.
I can't access the Recovery nor can restart Phone.
All I can do is switched it off And get back into fastboot again after.
Yeah, you can't flash things with the default recovery (That's just made for flashing the default builds), that's most likely why. Magisk was made to be flashed with TWRP.
Did you use the test TWRP here? If so, then go to that thread for help.
If you can get into the OnePlus recovery you could maybe grab a build from here and flash the default rom back, then start again using the guide I showed you but, tbh, I would wait until a good TWRP build is established and Magisk is confirmed to be working.
That thread also looks like it has the default recovery image too so you can flash that back on the phone with :
fastboot flash recovery filename (Just put the recovery image into the same folder as your adb.exe and fastboot.exe
Then see if you can reboot into it and flash the stock rom back on from the same thread.
How can I get things done back, all I've is fastboot.
It's a New set, please help (
dmishra639 said:
How can I get things done back, all I've is fastboot.
It's a New set, please help (
Click to expand...
Click to collapse
If you have fastboot, I've just told you how to get the default recovery back in above.
---------- Post added at 05:45 PM ---------- Previous post was at 05:28 PM ----------
Reading that thread again, flashing recovery is not as simple as it used to be due to the A/B partition model used now, so you'll need to read the instructions shown for recovery. My guess is that you didn't read them properly and flashed the recovery to the wrong partition. If you have flashed that TWRP then you need to seek support in that thread.
It's not gonna work with me,
Even if I'll download the zip file it's only flashable with a Twrp or Stock recovery. As stock recovery is not working.
Even if I'll try to flash a Twrp recovery it's showing up an error to me :
PS C:\adb> fastboot devices
420bdc60 fastboot
PS C:\adb> fastboot boot C:\adb\recovery.img
downloading 'boot.img'...
OKAY [ 0.585s]
booting...
FAILED (remote: unknown command)
finished. total time: 0.636s
PS C:\adb> fastboot flash recovery C:\adb\recovery.img
target reported max download size of 805306368 bytes
sending 'recovery' (18828 KB)...
OKAY [ 0.575s]
writing 'recovery'...
FAILED (remote: (recovery_b) No such partition)
finished. total time: 0.580s
PS C:\adb>
dmishra639 said:
It's not gonna work with me,
Even if I'll download the zip file it's only flashable with a Twrp or Stock recovery. As stock recovery is not working.
Even if I'll try to flash a Twrp recovery it's showing up an error to me :
PS C:\adb> fastboot devices
420bdc60 fastboot
PS C:\adb> fastboot boot C:\adb\recovery.img
downloading 'boot.img'...
OKAY [ 0.585s]
booting...
FAILED (remote: unknown command)
finished. total time: 0.636s
PS C:\adb> fastboot flash recovery C:\adb\recovery.img
target reported max download size of 805306368 bytes
sending 'recovery' (18828 KB)...
OKAY [ 0.575s]
writing 'recovery'...
FAILED (remote: (recovery_b) No such partition)
finished. total time: 0.580s
PS C:\adb>
Click to expand...
Click to collapse
This will sound stupid, but I had similar issues with the pixel and it was due to drivers and the port. Tried from a different machine and worked. Do you have the luxury to do so ?
Man, I've flashed like tons of Custom ROMs and Twrp from the same machine everytime.
I used to be a Xioami Redmi Note 5 pro user, And I've flashed almost every ROMs And root and everything, and same with my Redmi Note 3.
I don't think the machine have some fault some how.
It was Just like I had unlocked the bootloader And just after I flashed some Magisk ISO file which got flashed completely, And then all I'm stucked with the Fastboot, everything Stopped working, And everytime I'm dragged info fastboot.
And also as I said, can't flash Twrp.
dmishra639 said:
Man, I've flashed like tons of Custom ROMs and Twrp from the same machine everytime.
I used to be a Xioami Redmi Note 5 pro user, And I've flashed almost every ROMs And root and everything, and same with my Redmi Note 3.
I don't think the machine have some fault some how.
It was Just like I had unlocked the bootloader And just after I flashed some Magisk ISO file which got flashed completely, And then all I'm stucked with the Fastboot, everything Stopped working, And everytime I'm dragged info fastboot.
And also as I said, can't flash Twrp.
Click to expand...
Click to collapse
Grab this fastboot rom and flash...
https://forum.xda-developers.com/oneplus-7-pro/how-to/rom-stock-fastboot-roms-oneplus-7-pro-t3931424
Why are you trying to flash recovery partitions when they don't exist on this device? Recovery is on the boot partition.
dmishra639 said:
Man, I've flashed like tons of Custom ROMs and Twrp from the same machine everytime.
I used to be a Xioami Redmi Note 5 pro user, And I've flashed almost every ROMs And root and everything, and same with my Redmi Note 3.
I don't think the machine have some fault some how.
It was Just like I had unlocked the bootloader And just after I flashed some Magisk ISO file which got flashed completely, And then all I'm stucked with the Fastboot, everything Stopped working, And everytime I'm dragged info fastboot.
And also as I said, can't flash Twrp.
Click to expand...
Click to collapse
Since you are familiar with custom rom,unlocked bootloader etc you should had known already that you must NOT flash any kind Magisk staff without having proper and functional twrp.
Even if it flashed successful that doesn't mean will work after reboot and normal restart.
That why you've brick your device.
And on the other hand with A/B partition things has changed dramatically evolving all custom made staff and how they works.
Oneplus device not work the same way as Xiaomi you've described.
Sent from my iPad using Tapatalk Pro
LLStarks said:
Why are you trying to flash recovery partitions when they don't exist on this device? Recovery is on the boot partition.
Click to expand...
Click to collapse
paatha13 said:
Since you are familiar with custom rom,unlocked bootloader etc you should had known already that you must NOT flash any kind Magisk staff without having proper and functional twrp.
Even if it flashed successful that doesn't mean will work after reboot and normal restart.
That why you've brick your device.
And on the other hand with A/B partition things has changed dramatically evolving all custom made staff and how they works.
Oneplus device not work the same way as Xiaomi you've described.
Sent from my iPad using Tapatalk Pro
Click to expand...
Click to collapse
Any post that describe exactly what changed? I havent flashed custom roms/kernels in close to two years due to OOS being satisfying enough. What I have done is fastboot into twrp and flash magisk(I believe). Will I still be able to do that with OP7 Pro?
dmishra639 said:
My OnePlus 7 Pro keep booting into fastboot mode. Neither I can access recovery nor can start the phone. It's always comes back to recovery.
Please help me getting it done.
Bootloader is unlocked.
Click to expand...
Click to collapse
I forget the command, but change the boot slot and try to reboot.
tech_head said:
I forget the command, but change the boot slot and try to reboot.
Click to expand...
Click to collapse
Fastboot flash boot C://path/to/recovery.img
SysAdmNj said:
Any post that describe exactly what changed? I havent flashed custom roms/kernels in close to two years due to OOS being satisfying enough. What I have done is fastboot into twrp and flash magisk(I believe). Will I still be able to do that with OP7 Pro?
Click to expand...
Click to collapse
You can read over here on 6T device details of how thing work with A/B partition.
https://forum.xda-developers.com/on...overy-unofficial-twrp-touch-recovery-t3861482
https://twrp.me/oneplus/oneplus6t.html
https://www.xda-developers.com/how-...ess-updates-affect-custom-development-on-xda/
Also follow this thread about 7 Pro situation and how well work over time
[RECOVERY][3.3.1-2][guacamole]Unofficial TWRP recovery for OnePlus 7 Pro(Testing)
Sent from my iPad using Tapatalk Pro
joemossjr said:
Fastboot flash boot C://path/to/recovery.img
Click to expand...
Click to collapse
Man, thank you so much
You literally made my day,
Wht I've did wrong in a flow was I had given the command: fastboot flash boot and the magisk location.
That was a stupidity, all I forgot was the command.
Now I used the same command and then used oxygen os fastboot flashable all bat file, as suggested by a member.
And here's my phone back. )
Thanks
In case, I'm completely New to OnePlus
It someone suggest me how to Root OnePlus 7 Pro normally, cuz I've to edit the build prop due to some reason.
My bootloader is unlocked but can't flash custom recovery.
dmishra639 said:
In case, I'm completely New to OnePlus
It someone suggest me how to Root OnePlus 7 Pro normally, cuz I've to edit the build prop due to some reason.
My bootloader is unlocked but can't flash custom recovery.
Click to expand...
Click to collapse
I remember when I edit the buildi prob on my v20 to be recognized as a pixel so google assistant can work and that bricked my device.
Robert235 said:
I remember when I edit the buildi prob on my v20 to be recognized as a pixel so google assistant can work and that bricked my device.
Click to expand...
Click to collapse
Man I've a 2gb daily add on (for 3 months), which will only gonna work with my previous device (Redmi note 5 pro).
So, I've to change OnePlus as Note 5 Pro as same.
I've did that tons of time on my past phone,it never did a brick TBH.