Hello everyone
as an object the twrp does not install me any rom.
I tried everything.
I can only enter bootloader and recovery and fastboot commands work.
the installation process seems to be successful, but when I reboot, recovery always comes back to me.
1.) I deleted and then reinstalled twrp via adb, nothing.
2.) I used the adb sideload command to install the rom nothing, I always restart the twrp
tips?
Related
OK so phone was rooted with twrp installed. decided to update to latest ota 30b only I wiped and just flashed boot file and supersu without the actual rom. I know. now the phone goes straight into fastboot mode... I would think twrp is still installed but dont seem to be able to boot into it. I had adb and fastboot on my pc from before but havent used this in some time. if I try to open either of these the command window pops up and quickly closes.. What can I do ?.
new info: fadtboot is working in fact i have wrote a twrp recovery but still cant boot out of fastboot... adb device not listed. i reinstalled minimal adb and fastboot. help
I have lineageos 14.1 with TWRP and want to sell my phone, so I wanted to wipe everything and install stock rom and recovery.
In the TWRP, I made Advanced Wipe and selected everything, but not USB-OTG. After that, I made "format data".
Now, I would like to install stock recovery and stock rom.
However, when I go into the bootloader, the adb does not recognize my phone.
"adb shell" results in: error: device '(null)' not found.
I also cannot simply boot my smartphone, then I am stuck in a bootloop.
How can I fix this?
Can you use fastboot in the bootloader ? If yes just use the command "fastboot flash recovery stock-recovery.img" then "fastboot oem lock" and finally in the recovery go in adb and use the command "adb sideload stockoxygenos.zip"
Puddies said:
I have lineageos 14.1 with TWRP and want to sell my phone, so I wanted to wipe everything and install stock rom and recovery.
In the TWRP, I made Advanced Wipe and selected everything, but not USB-OTG. After that, I made "format data".
Now, I would like to install stock recovery and stock rom.
However, when I go into the bootloader, the adb does not recognize my phone.
"adb shell" results in: error: device '(null)' not found.
I also cannot simply boot my smartphone, then I am stuck in a bootloop.
How can I fix this?
Click to expand...
Click to collapse
very easy
https://forum.xda-developers.com/oneplus-5/how-to/unbrick-tool-oneplus-5-t3648169/page1
Tried to flash OB3 and SuperSu on my encrypted OP5 with TWRP. Was stuck at OP logo.
Tried to go back to stable Oreo build for OP5. Again, was stuck at OP logo.
Now the screen is unresponsive in TWRP (can't even swipe to allow modifications on the first screen!).
If I install stock recovery, I can navigate recovery with buttons. I tried installing OOS 5 with stock recovery from internal storage. It doesn't work. I tried to adb sideload. The computer throws a bad_alloc error.
Anyone in the same boat, or good enough to advice?
pentruexperiment said:
Tried to flash OB3 and SuperSu on my encrypted OP5 with TWRP. Was stuck at OP logo.
Tried to go back to stable Oreo build for OP5. Again, was stuck at OP logo.
Now the screen is unresponsive in TWRP (can't even swipe to allow modifications on the first screen!).
If I install stock recovery, I can navigate recovery with buttons. I tried installing OOS 5 with stock recovery from internal storage. It doesn't work. I tried to adb sideload. The computer throws a bad_alloc error.
Anyone in the same boat, or good enough to advice?
Click to expand...
Click to collapse
but u'll lost your data
i had this too, you need to flash stock recovery from cmd in yor pc by:
"fastboot flash recovery recovery_name.img"
then wipe everything,
reboot again into recovery
click on adb
and then download the stable firmware oreo 5
in adb mode with stock recovery put firmware in the same folder
and input - adb sideload name_of_firmware.zip
That fixed my phone, i'll hope and yours will be fixed
sk.c0de said:
but u'll lost your data
i had this too, you need to flash stock recovery from cmd in yor pc by:
"fastboot flash recovery recovery_name.img"
then wipe everything,
reboot again into recovery
click on adb
and then download the stable firmware oreo 5
in adb mode with stock recovery put firmware in the same folder
and input - adb sideload name_of_firmware.zip
That fixed my phone, i'll hope and yours will be fixed
Click to expand...
Click to collapse
Thanks,
The device is recognized well by the computer (when I write 'adb devices'). But when I try to sideload ('adb sideload OOS5.zip'), it gives me an error with bad_alloc. any ideas?
pentruexperiment said:
Thanks,
The device is recognized well by the computer (when I write 'adb devices'). But when I try to sideload ('adb sideload OOS5.zip'), it gives me an error with bad_alloc. any ideas?
Click to expand...
Click to collapse
Try unbrick method I think it's the quickest way to get back your device.
Dear readers,
I've no idea what happened but after trying to root my phone with Supersu I got stuck into this bootloop.
So what happened?
I flashed TWRP on my phone.
Once in TWRP I tried to install Supersu but unfortunately I couldn't find the zip file.
I restarted my phone.
This time I downloaded Supersu and put it in a location I would be able to find.
Once again flashed TWRP.
Got into TWRP.
Had to decrypt by password which I was unable to do.
So now TWRP was unable to read my internal storage (0mb internal storage).
Reading the forums I ended up backingup my device.
Then used the formatting function in TWRP.
Restored back my backup.
Still couldn't find the Supersu file.
Rebooted to stystem.
Now whatever I do I can't get out of Fastboot Mode.
Tried adb command: Fastboot reboot
No results.
I believe that I somehow should get the stock ROM (?) on my phone?
Fixed it!
Used adb to push the Supersu download to my phone in recovery. After that everything worked!
Bear with me, I had an older version and maybe just my method but I had messed up the custom rom I had on so I went to put a new one on and wanted to update TWRP at same time.
I installed the new custom rom, then installed TWRP and correctly clicked recovery.
However now recovery just goes into fastboot mode, I went into the dev settings and put usb debugging on, authorised it but each time it goes into fastboot it is not recognised and when I reboot into phone usb debugging has been disabled.
So now I can't get into recovery to flash a new rom, nor can I put twrp on by fastboot.
Stuck at what to do
Using Havoc OS
Try booting into the recovery from fastboot
Boot into fastboot and type
Fastboot boot recovery.img (recovery.img is the file saved on your pc)