I tried to install Android's ROM and got ERROR 7, then I wiped out cache, data, internal storage, where was twrp.apk installed.
After that I cant get into boot menu (with Install, Wipe... buttons).
Then I copied twrp to the phone:
sudo fastboot flash recovery <twrp.img>
Tried versions 3.2.1-0 and 3.4.0-0, because I heard for certain phone (I have Xiaomi Mi4) it's necessary to use proper version, though I don't know which.
What's going on now: I can successfully can get to the nice splash screen using Volume Down + Power, then on my PC I give sudo fastboot reboot command and press Volume Up + Power and here is the problem: It has no effect, it just keeps rebooting (I see only Xiaomi's logo).
Related
Hi Guys, I'm in a bit of a panic with my Nexus.
Looked in my pocked yesterday and the phone was randomly in a boot loop, just getting up to the google logo, then rebooting.. this was weird as the phone was working throughout the day. The day before I had installed Faux v5 (and I have cataclysms rom)..
Followed the instructions from [TUTORIAL] How to flash a factory image | Return to stock | Unroot your Nexus 5
to rever to stock image.
I run the flash-all.bat (using method 1 from Post1), which seems to complete successfully (writes to the device and it reboots a few times), but after this the phone gets stuck at the Google logo,
I cant get to the final two steps (which is wipe data/factory data reset), because in the step before where I select recovery, it just boots back to the google logo - no recovery. It will stay there all day, unless I hold power & volume down, then I can get back to the bootloader.
Since this failed (I have flashed the flash-all batch twice using different usb ports... but no joy.
If I run the fastboot device info, - it correctly shows my bootloader is unlocked...
I have tried to relock it, but hit the same problem, (if I run the fastboot boot c:\twrp.img etc) - it just wont boot into a recovery..
I am at a loss.. any help would be greatly appreciated...
I have also tried flashing a custom recovery (twrp & cwm), and I have the same problem with both.. they flash, but then I can get to the bootloader, but cant launch a recovery.. just gets stuck in a bootloop...
THANKS!
reboot bootloader (power + vol down)
go into recovery (the red triangle)
open up the recovery menu (power + vol up)
wipe cache
The problem I am having is I cant get into recovery.
I get into fastboot mode, I then hit volume up twice (to change from start > to recovery >).
I then hit power. But instead of a red! I get the Google Logo.. and I am back where I started.
Volume up & power does nothing, all I can do is Vol down & power, then I am back at the bootloader.. no recovery..
I'm not able to get into recovery.
After doing something stupid on my phone, i wanted to flash a new rom (crDroid). But the recovery gave an error 7. So i wanted to flash the recovery from the thread. I wasn't near a pc so i downloaded an app called Rashr to flash the recovery.img. But then my phone wouldn't boot or get into recovery.
So i used the official flashtool from sony to flash the official software to reset my phone and now my phone works again, but i still wanted crDroid. I downloaded a permissive kernel from zach and installed it through fastboot. I also installed the recovery through fastboot but when i booted, no yellow light came up and holding the volume up button wouldn't work as well.
Any suggestions?
Edit: Also fastboot boot recovery.img results in the phone being stuck at the sony logo
When you have recovery installed in FOTA partition, you can enter it by holding VOL DOWN + Power button while the phone is off.
The way you described only applies when recovery is installed in boot partition.
serenize said:
When you have recovery installed in FOTA partition, you can enter it by holding VOL DOWN + Power button while the phone is off.
The way you described only applies when recovery is installed in boot partition.
Click to expand...
Click to collapse
This only works with 100% reliability after flashing at least .160 Nougat firmware via FTF (XperiFirm),
then flashing twrp/recovery via
Code:
fastboot flash recovery recovery.img
and the behavior varies from country to country (or even firmware to firmware, among network operators / giving the name "custom firmware" credit :silly.
This time [2nd flash of .160 firmware, different operator] the notification led lights up violet for me, previously it was something else (a form of red, orange) and recovery almost instantly booted up,
now it takes several seconds - if not 30 seconds until it's in TWRP.
Okay so i'm on 34.4.A.0.160. I flashed some different recovery images by now but still no change in the situation. I did al the recovery flashing using the 'fastboot flash recovery recovery.img' code and fastboot gave no errors and it looked like it works everytime. But when i boot there is no led light during the entire boot sequence.
Also booting to recovery with volume down + power button when phone is off, didn't work. It just boots normal. I tried it serveral times and every time i changed some things, like pressing the volume button or power button for a longer time. Also once again, here no led indicators appear....
My led light is not broken as it still lights up when i get a message.
I installed a old lolipop firmware through flashtool, installed the Androplus permissive kernel and recovery, also from Androplus, through fastboot. Now when the phone boots it gets a yellow led indicator. When pressing volume up during the indicator, the light turn orange but the phone does not boot into recovery, but instead reboot itself.
Once again, no idea what is happening. Fastboot is working fine or i would not be able to flash the permissive kernel and get a yellow led light. But why won't my phone boot to recovery? I tried multiple different variants of twrp by different people. Tried multiple firmwares. I think there is something wrong with the partition where the recovery is stored. Is this possible? And if so, how would i fix it?
*i think it is against the rules, but here is a BUMP*
No one any idea ? I can't flash anything without recovery
Same here
I had a similar experience. What worked for me was
"fastboot erase recovery" before fastboot flash recovery etc.
Might work.
Wow - folks there you have your answer - but no one seems to care or read it:
serenize said:
When you have recovery installed in FOTA partition, you can enter it by holding VOL DOWN + Power button while the phone is off.
The way you described only applies when recovery is installed in boot partition.
Click to expand...
Click to collapse
well, I flash twrp to the recovery partition (FOTA huh ?)
Code:
fastboot flash recovery twrp.img
after both steps were [OK]
you can disconnect the cable (= phone off)
Now press VOL DOWN + POWER at the same time,
wait for the Sony logo/screen to appear,
wait 1-3 seconds and release the POWER button - keep the VOL DOWN button pressed [probably can release ALL but still ...]
the phone should boot into TWRP/recovery after quite some time
Just boot the recovery:
$ fastboot boot twrp.img
Hey guys, I was running LOS 15.1 on my OPO with TWRP and Magisk installed. I was flashing PA 7.3.1 for stability, and to do that I went to TWRP, factory reset the phone (I didn't fully format the device), cleared the cache, and then flashed PA. Now, the device just stays on the boot screen for PA, I tried volume up + power and it won't go to fastboot, and won't go to recovery with volume down + power, is there anything I can do? Windows makes a sound when I plug the device in, but it doesn't show up in my computer, and in cmd line, adb shell returns null, and it doesn't display anything for fastboot devices or adb devices. Please help!
TheRedViper said:
Hey guys, I was running LOS 15.1 on my OPO with TWRP and Magisk installed. I was flashing PA 7.3.1 for stability, and to do that I went to TWRP, factory reset the phone (I didn't fully format the device), cleared the cache, and then flashed PA. Now, the device just stays on the boot screen for PA, I tried volume up + power and it won't go to fastboot, and won't go to recovery with volume down + power, is there anything I can do? Windows makes a sound when I plug the device in, but it doesn't show up in my computer, and in cmd line, adb shell returns null, and it doesn't display anything for fastboot devices or adb devices. Please help!
Click to expand...
Click to collapse
@bmark240
@Timmmmaaahh
You didn't perform a backup first?
Try this.
Hold the power button on its own. Keep it pressed as it shuts off. It should then vibrate & the OnePlus Logo should appear. This is known as a hard power off & on. Sometimes there will be a conflict with corrupted software that has caused this problem.
If that doesn't work, you will have to check that you have ADB setup.
Make sure that your computer software is updated too if it makes a pop up sound then your phone is recognized.
Then follow this guide:
https://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732
Hopefully that should give you back a barebones system to work from.
So, I just decided to try and Flash the old TF101 with Katkiss 6.0.1 and Gapps, but I always get stuck on the same problem.
My TF101 is running Android 4.0.3 ICS and USB Debugging is on
I downloaded TWRP app on the transformer, as well as the latest .blob flash file through the app.
Before this, I rooted the tablet using Kingroot.apk, which worked. When I went to flash the tablet with the recovery, the app noted "Recovery Partition not found".
I tried to boot into recovery mode on my own, (Pressing Pwr + Volume down , Then hitting Volume Up), The android screen popped, up and then flashed to a fallen android with a red triangle.... The screen stays on this for a minute and then boots into the normal system. I can't even boot into recovery through ADB, using the
Code:
adb reboot recovery
, The tablet will just reboot normally, not into recovery mode.
The Device does recognize through ADB....
Is my recovery partition just non existent? Even when I just let the system though without pressing volume up, it only gives me the option of (Android) or (Erase Data). when I click erase data, ill stay on the asus loading screen indefinitely and nothing will happen until i turn it off and on.
I just cant seem to boot into TWRP for some reason, and that means I just cant install the downloaded custom ROM.
How Can I fix this and boot into TWRP? I've tried for hours and have been hung up due to the same problem each time, even after rooting.
Did you already solve that problem? I also need a solution.Thanks
Hi. I have a Samsung Galaxy Note 10 5G (d1x) device, rooted with magisk. The recovery key combo (Power+VolUp) is not working on the second reboot since flashing magisk (exiting download mode to be the first), pressing the key combo only gets me into a unrooted os. Issuing adb reboot recovery command from a pc will only get me into Magisk-enabled os, whether VolUp is long-pressed or not. After I tried to flash a TWRP image patched by the Magisk App using Odin, the situation remained same: key combo not working, adb command gets me into Magisk-enabled os. But if I use the Reboot to Recovery option inside the Magisk App, the phone blacks out for a few seconds after the Note 10 splash screen, and then reboots and gets into unrooted os.
So my question is: Is there something wrong with my method (patching the TWRP image from their official site with Magisk App, renaming it into recovery.img and flashing a tarball containing it with Odin), and how can I get both Magisk and TWRP working (and also how can I fix the recovery key combo).
REPLY:Both TWRP and Magisk work properly after the third reboot.
Hi, I have the same problem. Note 10+ and root from Magisk (Patching AP). Every time I normally reset the phone, I lose root. Then, to recover root, I have to combine on computer with the commands "adb reboot" plus a combination of PWR + Vol Up keys on the first inscription "Samsung" immediately after launching this restores root. It doesn't matter if the phone will reset 1 or 5 times. I will always lose root after a regular reset without a combination of PWR + Vol Up. I have enough of it. What am I doing wrong ?