Related
Hello,
I have recived the OTA today and I flashed it and now I dont have a custom recovery and root. What steps do I need to take to get those things back? I have tried to use this guide https://forums.oneplus.net/threads/...oader-install-custom-recovery-and-root.64487/ but after flashing recovery.img through ADB I still have normal CM recovery.
Go to Developer Options in Settings and disable the "update CM recovery" option.
Transmitted via Bacon
It has been disabled the whole time
Ok. So you say you're flashing the recovery through adb but that's impossible so I'm assuming you're flashing with fastboot, right?
Transmitted via Bacon
I'm not really good in those names.. I have isnerted a screenshot from this program.
xamilek555 said:
I'm not really good in those names.. [emoji14] I have isnerted a screenshot from this program.
Click to expand...
Click to collapse
Looks ok. Where are you getting the recovery from? Did you rename it to "recovery.img" for a reason?
Transmitted via Bacon
I've got that file from TWRP website and I renamed it to recovery.img. I have succesfully booted into this recovery with a command "fastboot boot recovery.img" which allowed me to flash root and xposed form it but after rebooting the phone the old recovery remains...
I have the same problem. Flash TWRP says it's flashed OK, but when I reboot to recovery it's still stock.
Linnyuk said:
I have the same problem. Flash TWRP says it's flashed OK, but when I reboot to recovery it's still stock.
Click to expand...
Click to collapse
Try updating the Android SDK. That's what worked for me. ?
Sent from my A0001 using Xparent BlueTapatalk 2
I've downloaded fresh verison today so it isnt the solution in my case :/
Somebody gave me this solution and it worked!
fastboot erase recovery
fastboot reboot-bootloader
fastboot flash recovery recovery.img
xamilek555 said:
I've downloaded fresh verison today so it isnt the solution in my case :/
Somebody gave me this solution and it worked!
fastboot erase recovery
fastboot reboot-bootloader
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
Same situation here...this solution isn't working for me, same problem, always Cyanogen based recovery...
After flashing new recovery, when you go to reboot, hold down Vol-Down and Power before it boots into the OS and it should load the new recovery. Had this problem myself earlier today, if you let it boot to the OS, it flashes back the CM recovery.
mozyman said:
After flashing new recovery, when you go to reboot, hold down Vol-Down and Power before it boots into the OS and it should load the new recovery. Had this problem myself earlier today, if you let it boot to the OS, it flashes back the CM recovery.
Click to expand...
Click to collapse
It works! I think it because of the dev settings into CM12S which force the recovery to be CM12S' one.
Thanks
Messatsu said:
It works! I think it because of the dev settings into CM12S which force the recovery to be CM12S' one.
Thanks
Click to expand...
Click to collapse
I'm having the same problem, can someone go over start to finish how they fixed this issue?
What worked for me
I previously had TWRP installed, wiped and did the C12S flash but didn't flash SuperSu before rebooting. This removed TWRP and brought me to Cynogen Recovery whenever going into recovery mode (Vol Dwn + Power). This also removed the root from my phone. To fix this took some digging and I came up with the following solutions as long as you had TWRP installed at one point. If not then unlock your boot loader and re install. I named my TWRP File Recovery just to keep things simple, but whatever your TWRP Filename is put that in at #5.
1) Enter Fastboot Mode (Vol Up + Power)
2) On your computer open command prompt (Ctrl R)
3) Plug your phone in
4) Type the following minus the quotes
"cd desktop/android-sdk-windows/platform-tools"
5) fastboot boot recovery.img
This will boot your TWRP, you can then go to flash your SuperSu file and you're done!
im having this issue too : /
mozyman said:
After flashing new recovery, when you go to reboot, hold down Vol-Down and Power before it boots into the OS and it should load the new recovery. Had this problem myself earlier today, if you let it boot to the OS, it flashes back the CM recovery.
Click to expand...
Click to collapse
I've tried so many things today, this is the only thing that worked. Thank You!
mozyman said:
After flashing new recovery, when you go to reboot, hold down Vol-Down and Power before it boots into the OS and it should load the new recovery. Had this problem myself earlier today, if you let it boot to the OS, it flashes back the CM recovery.
Click to expand...
Click to collapse
It works! I had the issue and this procedure solved it ! Thanks !!! :good::good::good:
Hi all,
I have just installed CM12s on my OPO and it was meant to install TWRP but each time i go into recovery to install SuperSU its still CM Recovery
1) Enter Fastboot Mode (Vol Up + Power)
2) On your computer open command prompt (Ctrl R)
3) Plug your phone in
4) Type the following minus the quotes
"cd desktop/android-sdk-windows/platform-tools"
5) fastboot boot recovery.img
Click to expand...
Click to collapse
I have done that and yey TWRP appeared and i Installed SuperUser but when i clicked on the app it said there was an issue with the binary, so i thought i would reboot into recovery and install it again...but CM recovery appeared again
Originally Posted by mozyman
After flashing new recovery, when you go to reboot, hold down Vol-Down and Power before it boots into the OS and it should load the new recovery. Had this problem myself earlier today, if you let it boot to the OS, it flashes back the CM recovery.
Click to expand...
Click to collapse
I thought i would give that a try but nothing seems to happen, the screen just goes black. Im reboting my OPO and when the white OPO logo appears im holding the buttons down....is this too soon or too late?
Originally Posted by xamilek555
I've downloaded fresh verison today so it isnt the solution in my case :/
Somebody gave me this solution and it worked!
fastboot erase recovery
fastboot reboot-bootloader
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
I have even attempted to do that but it doesnt seem to work....
Can someone help me out here....
After flashing new recovery, when you go to reboot, hold down Vol-Down and Power before it boots into the OS and it should load the new recovery. Had this problem myself earlier today, if you let it boot to the OS, it flashes back the CM recovery.
Click to expand...
Click to collapse
it works thank you...!!
Hello everyone. I am new around here and totally new with android devices. I got my tf300t, installed twrp and flashed to the newest android version. Then my dad suddendly pressed something like restore to the manufactory setting and after that it rebooted and just keep booting with teamwin logo. I can not access twrp recovery mod, it is just in boot loop. I managed to get adb to work, but no fastboot since it does not boot into recovery mode. When I am in adb I can browse the device but the adb reboot bootloader does not work at all. It just hangs there. I can not power off the device because it does not let me, I can not boot into recovery mode with powerbutton and volume down button. After a long power button press it only reboots. I even tried with hard reset button but still the same. Could You please help me somehow? I really need that device for school and I would like to get back into the stock android. Thank you so much for any help.
//edit : I also forget to mention, when I execute adb deviced it shows:
List of devices attached
0123456789ABCDEF recovery
Also the device is unlocked.
Did you tried: adb reboot recovery ?
Did you tried to flash recovery again?
Be sure to use the right recovery for your bootloader. Did you upgraded bootloader to latest ASUS one? One then you're able to flash current recoveries like TWRP like 2.8.5.0 oder 2.8.7.0.
Edit: Also take a look here -> http://droidmodderx.com/prime/?page_id=74
Hello sir. Thank you for answering. I tried adb reboot recovery and it just hangs to be executed... But the tablet is still flashing the teamwin logo. I have the same bootloop as the guy on youtube called Francis Domingo and video called Samsung s5 stuck at TWRP Recovery boot loop (unfortunately I can not add link here).
//edit: Thank you for the link. It look like I have to use option 1a. Is it safe to use that command and I will not make it even more bricked? Thank you so much
//edit2: Now I just realized how to turn off the device to stop from rebooting. I just long pressed power button and up volume button and after the screen went black I kept holding the up volume button. I didn't work with down volume button or if I stopped holding the up volume button after black screen it rebooted again.
//edit3 : Let's say if I get to the twrp mode with option 1a from the link, what do I have to do next to get back to the stock rom (I think it was something like 4.0.3) ? Thank you
What the guy does in 1a is wiping mmcblk0p3.
Afaik mmcblk0p3 is the staging partition. That would be my guess anyway if you had access to fastboot. Usally when you can't boot into recovery, something is wrong in staging. I got the same problem 2 days ago. In this case you usually wipe staging partition via fastboot.
Since you got no fastboot access, you have to try with adb.
After cleaning the staging partition you can flash any recovery you want back again.
The recovery must be flashed to mmcblk0p4 <- 4!!! is the recovery partition. (but you should wipe mmcblk0p3 (3!!!) before)
So I would say, try what solution 1a suggests.
Edit: You can go back to stock android if you want, but there is no reason for this. My advice would be to unlock and root your device, upgrade to latest boot loader (which is done by upgrading to latest stock rom), then flash TWRP 2.8.5.0 and then a useful ROM on top. I'm using the one from timduru which is very nice. You can find it here: http://forum.xda-developers.com/transformer-tf300t/development/rom-t2932783
Thank you for the answer. Could you please write a step by step to get out of brick and to get the stock version, because the newer one I installed was many times slower. The reason why I would like to have step by step is because I don't wanna mess it even more than it is. Thank you so much.
//the stock rom was much more faster than the one I have installed, I mean... the boot time wad unbelievable slow, same with responses and wifi problem. If there is any other faster rom than stock I would be happy but I don't wanna mess with any bugs or slow boot speed and I can not wait minutes until it boots.
Hm, try the Option 1a from the link.
If done, boot into current recovery. Tell me which version and which recovery do you have.
Top on this we can decide what to do to flash a good ROM.
I had the exact same thing happen to me yesterday. Option #1 worked for me.
I did the steps from option #1 and powered down using the volume up + power. I then tried to boot into TWRP recovery, which only reproduced the same issue.
I redid the option #1 steps, and this time powered down using the power + volume down. I powered back up normally, and it rebooted normally into the ROM.
The tablet now works normally, and I can also boot back into TWRP recovery with no issues.
Thanks for the thread and the link.
Thank you so much Catscratch! After I executed both command from option 1a I can get into the screen, where it shows three options: RCK, Android, Wipe Data
In the top left corner, there is written:
Key driver not found.. Booting OS
Android cardhu-user bootloader <1.00 e> released by "WW_epad-10.6.1.27.5-20130902" A03
Starting Fastboot USB download protocol
The tablet can boot into the last ROM but as I said, I would like to have the faster and less buggy rom than this. When I open the settings and click about button there is written: CyanongenMod: 12.1-20150814-NIGHTLY-tf300t and Android version 5.1.1.
If I start RCK it just brings me back to the loop, but now I have fastboot available as it said above and I can list the fastboot devices on computer, which I couldn't before. Should I just execute this command from the computer "fastboot -i 0x0B05 flash system blob" and then "fastboot reboot" or should I download ROM from asus.com/Tablets/ASUS_Transformer_Pad_TF300T/HelpDesk_Download/ -> OS Android -> Firmware and now I don't know which should I choose: If JP or CN or WW or US or TW (Probably US right?). After that should I execute "fastboot -i 0x0B05 flash recovery firmware.img" and then "fastboot reboot" ? Or which ROM should I download to make it even faster and less buggy than stock ROM? Thank you so much again, You saved my tablet
//After I unzipped downloaded US ROM there is no img file. If I remember right the img file is only recovery to reflash the actual one and then when I start the twrp recovery I will select zip file with rom right?
OK, first of all to continue...I assume you got root access. (I think you should have, because you already got CM installed)
Next. Downloads.
Download: https://twrp.me/devices/asusTF300T.html
Also Download ROM+SuperSU: http://forum.xda-developers.com/transformer-tf300t/development/rom-t2932783
And GApps: http://forum.xda-developers.com/android/software/app-minimal-gapps-gapps-lp-20150107-1-t2997368
Push all files to sdcard with "adp push" or in CM. Like you want.
Flash TWRP. (you can skip this step if you already got TWRP 2.8.5.0 or higher version). You don't need latest one.
fastboot -i 0x0b05 flash recovery twrp.img
fastboot reboot
- or -
adb reboot recovery
Now, go into recovery and wipe everything:
- cache
- dalvik
- system
- data
After that flash ZIPs from sdcard. (use "add more zips" option)
1. ROM
2. Gapps
3. SuperSU
Next: Wipe cache and dalvik again (only these two).
Reboot and wait. First boot can take some minutes.
Thank you so much again. Everything work perfectly The rom looks a lot faster than the older one I had there. No issues yet at all. Just awesome. Thank you so much. Really appreciate your kindness and help. You have a nice day !
Thanks. Have fun with your tf300.
HTCDreamOn said:
A word of advice: I strongly recommend temporarily booting any images (be it recoveries or kernels) you are about to flash to your device. This is simply a case of using the command "fastboot boot blahblah.img" whether blahblah.img is a recovery or kernel.
Click to expand...
Click to collapse
We know you can boot to TWRP vice flash to your device by using the command:
Code:
fastboot boot twrp.img
But how do you proceed from here? Are you required to use ADB commands at this point or can you unplug your USB cable and use TWRP as if it was installed, I.E. , back up current ROM, and install new zip.
purplepizza said:
We know you can boot to TWRP vice flash to your device by using the command:
Code:
fastboot boot twrp.img
But how do you proceed from here? Are you required to use ADB commands at this point or can you unplug your USB cable and use TWRP as if it was installed, I.E. , back up current ROM, and install new zip.
Click to expand...
Click to collapse
Sorry if I wasn't clear. Yes you can unplug usb and use as normal, it just means twrp isn't flashed to the device so it won't be there when you reboot.
I just recommend this step because I'm paranoid. Once you've confirmed the image works you should reboot to bootloader and fastboot flash the image, then you'll be able to boot into twrp whenever you want.
HTCDreamOn said:
Sorry if I wasn't clear. Yes you can unplug usb and use as normal, it just means twrp isn't flashed to the device so it won't be there when you reboot.
I just recommend this step because I'm paranoid. Once you've confirmed the image works you should reboot to bootloader and fastboot flash the image, then you'll be able to boot into twrp whenever you want.
Click to expand...
Click to collapse
This is a good step to do, and if the device supports it it should be used... for example the Moto G (if unlocked) fully supports fastboot boot commands, devices like the HTC One M7 do NOT support this anymore...
To the OP, what is really happening here is that TWRP or the boot.img (kernel) is being loaded from USB into RAM and executed normally, instead of the standard /boot partition which is skipped when executing fastboot boot. TWRP (and recovery in general) is really just a specialized micro-sized android distribution and when started via fastboot boot is executed as if it was the boot image. Once the image is transferred into RAM, the boot continues normally per the instructions of TWRP or the boot image, and no further action via USB is required. USB is just the medium to load the image into RAM and nothing more.
fastboot boot - used to manually load a boot image (or recovery) and execute from RAM, it is not flashed to the device, on the next reboot it will return to it's previous state
fastboot flash boot/recovery - used to actually flash the boot image or recovery image to the it's appropriate partition on the device, it does not execute it. On a reboot or factory default this information will stay in the device.
acejavelin said:
This is a good step to do, and if the device supports it it should be used... for example the Moto G (if unlocked) fully supports fastboot boot commands, devices like the HTC One M7 do NOT support this anymore...
To the OP, what is really happening here is that TWRP or the boot.img (kernel) is being loaded from USB into RAM and executed normally, instead of the standard /boot partition which is skipped when executing fastboot boot. TWRP (and recovery in general) is really just a specialized micro-sized android distribution and when started via fastboot boot is executed as if it was the boot image. Once the image is transferred into RAM, the boot continues normally per the instructions of TWRP or the boot image, and no further action via USB is required. USB is just the medium to load the image into RAM and nothing more.
fastboot boot - used to manually load a boot image (or recovery) and execute from RAM, it is not flashed to the device, on the next reboot it will return to it's previous state
fastboot flash boot/recovery - used to actually flash the boot image or recovery image to the it's appropriate partition on the device, it does not execute it. On a reboot or factory default this information will stay in the device.
Click to expand...
Click to collapse
Thanks. So it seems there is no reason to ever flash TWRP unless you don't want the PC dependence to use the TWRP tool.
purplepizza said:
Thanks. So it seems there is no reason to ever flash TWRP unless you don't want the PC dependence to use the TWRP tool.
Click to expand...
Click to collapse
Well, sort of... but the point is once you flash anything via twrp, you are no longer stock, so why not flash twrp to make it easier to flash other things?
The smartest thing would be to unlock, boot TWRP, make a nandroid backup before you do anything at all, then flash TWRP and do your thing...
acejavelin said:
Well, sort of... but the point is once you flash anything via twrp, you are no longer stock, so why not flash twrp to make it easier to flash other things?
The smartest thing would be to unlock, boot TWRP, make a nandroid backup before you do anything at all, then flash TWRP and do your thing...
Click to expand...
Click to collapse
I understand what you are saying. The only flash I planned on was SuperSU. I thought when a system upgrade is available, I could simply use SU to unroot and be ready for the update. Would this work?
If I followed your recommendation, could I feasibly, flash TWRP, then when an upgrade is ready, flash nandroid backup (which I assume removes TWRP) then accept system update, then re-flash TWRP. I could restore apps by using TB. Does this make sense? Or does TWRP remain in place after flashing nandroid backup?
purplepizza said:
I understand what you are saying. The only flash I planned on was SuperSU. I thought when a system upgrade is available, I could simply use SU to unroot and be ready for the update. Would this work?
If I followed your recommendation, could I feasibly, flash TWRP, then when an upgrade is ready, flash nandroid backup (which I assume removes TWRP) then accept system update, then re-flash TWRP. I could restore apps by using TB. Does this make sense? Or does TWRP remain in place after flashing nandroid backup?
Click to expand...
Click to collapse
TWRP remains in place after restoring a nandroid (I think, I haven't installed on my Moto G, but in most devices it doesn't backup/restore recovery), but you can easily restore the original recovery via fastboot.
acejavelin said:
TWRP remains in place after restoring a nandroid (I think, I haven't installed on my Moto G, but in most devices it doesn't backup/restore recovery), but you can easily restore the original recovery via fastboot.
Click to expand...
Click to collapse
Just curious, how did you go from 5.1.1 to 6.0?
purplepizza said:
Just curious, how did you go from 5.1.1 to 6.0?
Click to expand...
Click to collapse
OTA... part of soak test on December 22.
acejavelin said:
OTA... part of soak test on December 22.
Click to expand...
Click to collapse
Hey thanks for helping to answer this, your explanation was much better I thought it had something to do with loading into RAM but wasn't sure. I didn't know some devices don't allow fastboot boot commands though, I've always relied on them. Part of the reason I'm avoiding htc now.
@purplepizza I agree with everything acejavelin has said: essentially you really do want to make sure your have twrp flashed.
To answer your nandroid question: It basically just takes an image of the partitions you choose, usually /system, /data, and /boot (where kernel stuff is) which is the least you need to boot back with all your data. It doesn't backup recovery and when you restore it doesn't write anything to recovery, so yes twrp will still be in place. In general you should only ever flash stuff to the recovery partition whilst in fastboot mode (i.e. using fastboot flash recovery recovery.img), I know on some devices you can flash recoveries as zip files in the recovery itself but you shouldn't.
I've seen quite a few people querying about the 6.0 OTA: in short, I wouldn't worry about it because once they start rolling out, people always catch the OTA and post here on xda. You can flash that and it'll return you to stock 6.0 anyway, at which point you can reroot and everything if you want.
acejavelin said:
Well, sort of... but the point is once you flash anything via twrp, you are no longer stock, so why not flash twrp to make it easier to flash other things?
The smartest thing would be to unlock, boot TWRP, make a nandroid backup before you do anything at all, then flash TWRP and do your thing...
Click to expand...
Click to collapse
One more question, when making the first nandroid backup. do you just back up system and data or do you include boot as well?
purplepizza said:
One more question, when making the first nandroid backup. do you just back up system and data or do you include boot as well?
Click to expand...
Click to collapse
My opinion is always backup everything, you can always choose what to restore
Sent from my MotoG3 using Tapatalk
acejavelin said:
My opinion is always backup everything, you can always choose what to restore
Sent from my MotoG3 using Tapatalk
Click to expand...
Click to collapse
So what is boot? I know I am kind of going back to my previous question, but if I restore boot, is that the boot loader? I would assume this would not commonly need restored?
And I now assume the bootloader is completely independent from recovery.
purplepizza said:
So what is boot? I know I am kind of going back to my previous question, but if I restore boot, is that the boot loader? I would assume this would not commonly need restored?
And I now assume the bootloader is completely independent from recovery.
Click to expand...
Click to collapse
It is not the bootloader... It is the /boot partition of the phone, basically the kernel and RAM disk. If you screw things up and need to restore, you typically want to restore /boot, /system, and /data, and occasionally /cache (if you want to restore to save time and get an exact duplicate of the previous image, otherwise many people skip /cache and let it rebuild on the first boot which takes 10-15 minutes extra).
acejavelin said:
Well, sort of... but the point is once you flash anything via twrp, you are no longer stock, so why not flash twrp to make it easier to flash other things?
The smartest thing would be to unlock, boot TWRP, make a nandroid backup before you do anything at all, then flash TWRP and do your thing...
Click to expand...
Click to collapse
HTCDreamOn said:
@purplepizza I agree with everything acejavelin has said: essentially you really do want to make sure your have twrp flashed.
Click to expand...
Click to collapse
So I am following your advice. I booted to TWRP, made Nandroid backup.
Rebooted and flashed TWRP, see below:
Code:
sudo fastboot flash recovery twrp.img
target reported max download size of 268435456 bytes
sending 'recovery' (7772 KB)...
OKAY [ 10.635s]
writing 'recovery'...
OKAY [ 0.141s]
finished. total time: 10.776s
All seems OK.
Scrolled to recovery, selected recovery. TWRP was there. I then powered down.
After that I held power and volume down, system boots to dead Android with message “No command” Held power then volume up, I see stock boot loader. Is TWRP flashed somewhere or is it gone? So what did I do wrong.
purplepizza said:
So I am following your advice. I booted to TWRP, made Nandroid backup.
Rebooted and flashed TWRP, see below:
Code:
sudo fastboot flash recovery twrp.img
target reported max download size of 268435456 bytes
sending 'recovery' (7772 KB)...
OKAY [ 10.635s]
writing 'recovery'...
OKAY [ 0.141s]
finished. total time: 10.776s
All seems OK.
Scrolled to recovery, selected recovery. TWRP was there. I then powered down.
After that I held power and volume down, system boots to dead Android with message “No command” Held power then volume up, I see stock boot loader. Is TWRP flashed somewhere or is it gone? So what did I do wrong.
Click to expand...
Click to collapse
I have no idea, you did it right... selecting recovery from the bootloader should start TWRP, not stock recovery, that should be gone.
acejavelin said:
I have no idea, you did it right... selecting recovery from the bootloader should start TWRP, not stock recovery, that should be gone.
Click to expand...
Click to collapse
Any recommendations how to proceed?
I also need help with my soft bricked moto g3
Moto g3 (xt 1550, Indian dual sim 16 gb version)
I officially upgraded to 6.0.0 via ota and my objective was to root my phone and use xposed modules. I am not interested in any other custom rom (I'd rather keep stock rom just for moto display and ota upgrades) or custom recovery like twrp(I'm afraid it may cause ota upgrades to fail).
I used the method described here in the question- http://android.stackexchange.com/qu...rsu-using-play-store-versus-a-custom-recovery
So I first successfully unlocked my bootloader using the official motorola method.
I then proceeded to use google's backup settings to re-install all the apps that were uninstalled due to unlocking the bootloader. I also put supersu.zip version 2.46 on internal sd card.
I then proceeded to (without rebooting) enter fastboot where i used minimal adb to temporarily boot into twrp version2.8.7 r5 (link - http://forum.xda-developers.com/2015-moto-g/orig-development/twrp-twrp-moto-g-2015-t3170537 ).
Once in twrp, I located and flashed the supersu.zip. It flashed successfully. I procceded to clear dalvik cache and then after clearing cache I tried to reboot my phone using twrp.
However, it did not go beyond the "Warning - Bootloader Unlocked" screen that you get on unlocking a motorola bootloader. I left it for over 10 minutes (usb was still plugged in, I had >80% battery) but it did not proceed.
Long -pressing the power button causes the phone to vibrate and again attempt to boot, stuck at the same initial screen. Adb quite understandably does not work here.
I can press vol down+power and enter fastboot , where adb works fine.
I can enter stock recovery from the fastboot sceen too.
Using adb in fastboot, I am able to boot twrp . In fact, I tried to re-install supersu.zip. I retried version 2.46 and then tried version 2.56. On all occcassions, it was able to successfully flash it, but gets hung on the initial boot screen.
USB Debugging is also enabled, and I have a backp of my sd card data.
I tried taking a backup of the system and apps in twrp (3 gb in total) and tried to reflash it, but it still hangs at the same screen.
Is there any way I can unbrick my device and- (in decreasing order of preference)
1. Keep my stock rom and recovery?
2. Keep stock rom with twrp? (It should not be a problem)
3. Custom rom with custom recovery - perhaps official cm. Least preferred as I want Moto Display and stock/vanilla android.
Also, is SELinux involved anywhere with my phone getting bricked? I also read that a custom kernel is required for rooting 6.0, which I don't have. Supersu Version 2.56 is said to prevent soft bricks if the kernel is incorrect (systemless root), yet even after flashing the newer one it is still bricked. Where am I going wrong? What should I do? Thanks in advance! :good:
purplepizza said:
Any recommendations how to proceed?
Click to expand...
Click to collapse
Try the flash again? Sorry, but I don't really know help... if you are successfully rooted, perhaps try to flash TWRP image with Flashify? (select your file, don't let it auto-grab an image)
acejavelin said:
Try the flash again? Sorry, but I don't really know help... if you are successfully rooted, perhaps try to flash TWRP image with Flashify? (select your file, don't let it auto-grab an image)
Click to expand...
Click to collapse
I have not rooted yet. I guess I can try by booting TWRP then flashing SuperSU.
Can you think of any reasons not to try fastboot again the re-flash TWRP?
Hi! My Oneplus One is stuck in boot (the oneplus logo).
I can get into fastboot but not recovery. I have followed some softbrick guides and the problem that I have is that even after flashing twrp as recovery I cant get into recovery. when I try to start it to recovery (volume up + power) I only get to the oneplus logo again. and when I use "fastboot boot twrp.img" the backlight comes on but the fastboot image stays, fastboot doesnt recognize it from this point so i have to restart it into fastboot mode again.
i have tried to flash the factory images, but nothing seems to change.
I dont know what to do, pls help..
After flashing recovery from fastboot, do NOT issue the reboot command. Press and hold the power button till phone powers off. If you issue the reboot command from fastboot, custom recovery will be lost. Also, don't know which twrp version you are trying to flash, but I would suggest flashing 2.8.6.0 first, then after you know you can get into recovery, you can flash another version.
Additionally, to boot to recovery you have to hold
volume down + power
volume up + power brings you to fastboot
Last but not least,
fastboot boot twrp.img
does not boot the recovery which is on your device, but the recovery image which is located inside your fastboot folder on your pc.
kenboyles72 said:
After flashing recovery from fastboot, do NOT issue the reboot command. Press and hold the power button till phone powers off. If you issue the reboot command from fastboot, custom recovery will be lost. Also, don't know which twrp version you are trying to flash, but I would suggest flashing 2.8.6.0 first, then after you know you can get into recovery, you can flash another version.
Click to expand...
Click to collapse
Ok, I did not know that the reboot command removes the custom recovery. Im almost certain that i've tried just powering down and trying recovery before too tho.
I was trying to flash twrp 3.0.0.0 so i'll try 2.8.6.0 asap
AcmE85 said:
Additionally, to boot to recovery you have to hold
volume down + power
volume up + power brings you to fastboot
Last but not least,
fastboot boot twrp.img
does not boot the recovery which is on your device, but the recovery image which is located inside your fastboot folder on your pc.
Click to expand...
Click to collapse
oops, i ofcourse ment that i try to get to recovery by volume down+power, and i know fastboot boot twrp.img boots from the .img on the computer, i just think its peculiar that nothing happens.
nothing has really happend after this, so i still need help.
summary: bump
I don't really get what you say. Perhaps i don't experiences before. @kenboyles72 is correct, official ROM may delete custom recovery (you can change the setting). Then @AcmE85 gives you an option, but it does not work.
Here is my option:
1. download any custom rom. The best idea is as minimum MB as possible. (Flash ROM directly from your PC)
2. flash your recovery, do NOT reboot. (fastboot flash recovery rec.img)
3. flash your ROM. (fastboot flash zip rom.zip)
Let's see if this would help you.
I had some issues a while back, where I was caught in a bootloop and flashing another rom. So I followed this guide, https://www.reddit.com/r/oneplus/comments/31sf0x/guide_how_to_return_from_oxygenos_to_stock_cm11s . You can skip flashing the userdata.img to keep all data on sdcard. Also you can substitute flashing twrp recovery img for stock recovery. I myself went ahead and flashed all stock just to make sure everything booted correctly, then went into dev options and disabled update cm recovery, booted back to fastboot and flashed twrp 2.8.6.0. Evey thing worked like a charm.
Flasing stock rom did not affect anything noticeably.. phone is still stuck in boot/fastboot
Just to confirm, have you tried either/both of these:
http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541
http://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732
I have followed the return to stock guide, but not the unbrick, since my phone is softbricked, not hardbricked.
I have followed this guide tho, to no avail https://m.reddit.com/r/oneplus/wiki/devices/one/brickguide
the strange thing is that i didnt cause this. The phone started randomly overheating and one time it just never booted up.
1. bootloader is unlocked and confirmed
2. im running on a Realme Q latest Stock Rom RMX1971_11_C.08
3 ADB and USB debuging are properly setup.
4. I have tried the following recoveries, none working.
-recovery-TWRP-3.3.2B-0227-REALME_Q-CN-wzsx150.img
-OrangeFox-HOMEMADE-RMX1971.img
-OrangeFox-R11.0_0-Stable-RMX1971.img
-twrp-RMX1971-20191121.img
ABD always confirm to push the recovery file succesfully but everytime I boot in recovery, I get the Realme UI recovery.
What I'm I doing wrong ?????
jungl1st said:
1. bootloader is unlocked and confirmed
2. im running on a Realme Q latest Stock Rom RMX1971_11_C.08
3 ADB and USB debuging are properly setup.
4. I have tried the following recoveries, none working.
-recovery-TWRP-3.3.2B-0227-REALME_Q-CN-wzsx150.img
-OrangeFox-HOMEMADE-RMX1971.img
-OrangeFox-R11.0_0-Stable-RMX1971.img
-twrp-RMX1971-20191121.img
ABD always confirm to push the recovery file succesfully but everytime I boot in recovery, I get the Realme UI recovery.
What I'm I doing wrong ?????
Click to expand...
Click to collapse
Ah yes. I've ran into similar issues last time I tried to revert from Pixel Experience Android 11 to stock RMQ firmware. I noticed if you start sending the recovery with fastboot flash recovery twrp.img, the fastboot cmd waits for device, you enter fastboot mode and then connect to the PC via usb 2.0 port the recovery will be successfully flashed BUT only that one file, whatever you want to flash next time for example vbmeta or system, vendor.img you'll have to repeat the cycle. Disconnect the usb cable, enter the flashing command to fastboot cmd on PC, boot back again to fastboot mode on your phone then connect the usb cable. This solved the issue for me.
greenys' said:
Ah yes. I've ran into similar issues last time I tried to revert from Pixel Experience Android 11 to stock RMQ firmware. I noticed if you start sending the recovery with fastboot flash recovery twrp.img, the fastboot cmd waits for device, you enter fastboot mode and then connect to the PC via usb 2.0 port the recovery will be successfully flashed BUT only that one file, whatever you want to flash next time for example vbmeta or system, vendor.img you'll have to repeat the cycle. Disconnect the usb cable, enter the flashing command to fastboot cmd on PC, boot back again to fastboot mode on your phone then connect the usb cable. This solved the issue for me.
Click to expand...
Click to collapse
Thank you very much for the tip ! I shall give it a try as soon as I'm back home , since I'm on holiday now and don't have the device !
jungl1st said:
Thank you very much for the tip ! I shall give it a try as soon as I'm back home , since I'm on holiday now and don't have the device !
Click to expand...
Click to collapse
It's worth a try for sure. Yesterday it took me more than 6 hours to set up a working RUI after Pixel Experience. One of these issues was that I couldn't flash custom recovery and vbmeta. I Always keep a modified vbmeta and twrp.img on my external SD card once I successfully managed to boot up into twrp after fastboot flash. Remember, keeping custom recovery installed should be your number one priority for you can pretty much solve anything with it.
greenys' said:
It's worth a try for sure. Yesterday it took me more than 6 hours to set up a working RUI after Pixel Experience. One of these issues was that I couldn't flash custom recovery and vbmeta. I Always keep a modified vbmeta and twrp.img on my external SD card once I successfully managed to boot up into twrp after fastboot flash. Remember, keeping custom recovery installed should be your number one priority for you can pretty much solve anything with it.
Click to expand...
Click to collapse
indeeed, custom recovery is the turning point to recover almost anything ! given the point that one manages to install it in the first place
greenys' said:
It's worth a try for sure. Yesterday it took me more than 6 hours to set up a working RUI after Pixel Experience. One of these issues was that I couldn't flash custom recovery and vbmeta. I Always keep a modified vbmeta and twrp.img on my external SD card once I successfully managed to boot up into twrp after fastboot flash. Remember, keeping custom recovery installed should be your number one priority for you can pretty much solve anything with it.
Click to expand...
Click to collapse
Hi, I actually managed to flash the recovery, how ever it seem not to properly overwrite the original recovery.
I mean, i can flash and boot in to TWRP, only once at a time, once I exit TWRP and reboot into recovery, I land into the Realme recovery again !!!!! dont know whats wrong