Database Info

[Q] Only Android Logo in Recovery. Wifi Model

Hey guys, just wondering if any of you know a fix for this on my WIFI only xoom
Using the guide from here about Wifi Unlocking and rooting Ive unlocked the bootloader on my Xoom. Ive flashed Clockwork and am up to the part where I have to boot into clockwork recovery to install the root tool, however there is no option to enter 'Android Recovery' when I push the Down key on the dual core boot screen, during the first 3 seconds of the first boot after flashing. Theres NVFlash, fastboot and another but no recovery.
I am able to get into recovery via the ADB REBOOT RECOVERY command however I dont get into Clockwork and am stuck on a screen with a green android logo in the center. Pushing any manner of buttons does nothing and the tab automatically resets after 2 or 3 mins in that mode. Has anyone else seen this and know of a fix?? Ive since learned that if you allow the tab to boot into honeycomb it installs the stock recovery and you have to start over by reflashing clockwork, as stated tho no Android Recovery option appears. Any ideas?

recovery is not installed properly.
put your recovery file in fastboot folder
rename it to recovery.img
in fastboot run: fastboot flash recovery recovery.img
this recovery file is not zip file but .img file(rename it for ease of typing)

I've done it exactly like that, 3 times now. all the messages seem to indicate its flashed correctly. Heres what it says on the tab:
Flashing allowed for partition recovery
OneWire: Charger not connected
Battery Level 82%
Flashing Stormgr partition recovery Status:- done!
And i get the OKAY's in the terminal box as well. Still no Android recovery menu. I read in a dev post reguarding this same procedure a few other ppl had the same issue. I was hoping sum1 had a fix

Is my Xoom bricked?

Hey All,
I know there are a lot threads like this on here, so I made sure I tried everything possible before asking for help.
First off, It is a MZ604 wifi version.
Ok, upon powering up my Xoom, it will get to the Motorola screen/ dual core and stall.
I am able to get into recovery, however the version I am running, 5.8.3.1 apparently does not allow sd card mounting, so I am unable to restore or flash a new rom.
A factory reset/ data wipe does nothing.
I have tried to flash a new rom via ADB, however my computer will not install the Xoom drivers. It will say "installing device drivers" for about 2 minutes or so before failing. I have tried using moto helper and the other Motorola usb drivers
I am unable to boot into android to enable usb debugging
I have tried all of the above on my laptop too and to the same result.
My question is, is this a brick? or can it be solved.
Thanks for your time

Yes it can be fixed, if you can access recovery then it means you can access fastboot. So what you do is once you're in the fastboot protocol, is flash in TWRP recovery http://forum.xda-developers.com/showthread.php?t=1782235
With that recovery you can mount SD cards, so use a computer to download the ROM you want then flash. Hopefully you get the idea, but I can post in more detail if you want.

Chaosgod27 said:
Yes it can be fixed, if you can access recovery then it means you can access fastboot. So what you do is once you're in the fastboot protocol, is flash in TWRP recovery http://forum.xda-developers.com/showthread.php?t=1782235
With that recovery you can mount SD cards, so use a computer to download the ROM you want then flash. Hopefully you get the idea, but I can post in more detail if you want.
Click to expand...
Click to collapse
Thanks for responding, I appreciate it. The thing is that my xoom cannot connect to my computer, and therefore and cannot use fastboot to send it the image correct?
I could fix all of this if I could just get the drivers to install, but because of my xoom's condition, the drivers cannot install no matter what.

Hmm usually fastboot drivers should automatically install. Does your recovery have an option to boot into fastboot? Once you're in fastboot it should automatically install the drivers, and in the android sdk folder in CMD (assuming you're running windows) put in this command: fastboot devices
It should show up your XOOM if not install this http://www.motorola.com/Support/AU-EN/Support-Homepage/Software-and-Drivers/USB-PC-Charging-Drivers
And try again

Hi all!
I got the same problem...
I can connect it to PC and do fastboot, I've flashed it many times, but it didn't affect my Xoom, i've reflashed the recovery to a lower version (tiamat rc4) but the recovery still shows version 5.8.3.1...
I even tried RSD, but it still the same...
no errors, and no effects...
is my Xoom bricked?

^I heard of this before, sounds like your new recovery image just gets overwritten by the current recovery. Though I thought it was only for stock recovery.

but, how can I overwrite it? it seems like they are read only...

It's all about timing, to access recovery once you see the Moto logo wait 2-3 seconds then vol + then vol + again. This is right after you flashed in your new recovery.
You can also access your fastboot like that as well, instead of pressing vol + again, press vol - then vol +.

Chaosgod27 said:
It's all about timing, to access recovery once you see the Moto logo wait 2-3 seconds then vol + then vol + again. This is right after you flashed in your new recovery.
You can also access your fastboot like that as well, instead of pressing vol + again, press vol - then vol +.
Click to expand...
Click to collapse
that's not the problem... of course I can access the recovery, fastboot and RSD, the problem is that I whatever I do to the xoom just don't work... and it reports no error at all... it's just succeed, but nothing happened... It's like a PC running windows with DeepFreeze installed...
Anyone got the same problem? can anybody help me?:crying:

No you're missing the whole point, after you flashed your new recovery it may get overwritten if you don't reboot into recovery straight way. It never happened to me but I have read that people has that issue.

Not getting into 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

Need help flashing Katkiss 6.0.1 , Recovery Partition Not Found / Nothings Working

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

Problems Rooting Blackview BV5500Pro

Hi there. I got trouble rooting my Blackview BV5500Pro with Android 9.0
Its not the first smartphone im rooting, so im not new to this. But im also not a professional or something, even english is not my native language so sorry for my bad grammar.
At first i tried the way i done this bevore to my smartphones:
1. Unlock OEM via Fastboot
2. Flash TWRP 3.3.0 (The only working twrp i found) to Recovery
3. Boot into TWRP.
To this point everything works fine.
But when i install Magisk 21.4. i get a bootloop.
also when i install SuperSu 2.8.2
So i tried to patch the boot image via Magiskmanager App 8.0.7.. Everything works fine. I can flash the patched boot image via fastboot, twrp or sp flash tool. But when i open Magisk after booting the patched image, there is no option to install Magisk or root the Phone. Only to patch the boot image. Even when i boot the patched image directly with fastboot.
Maybe somone here can help me.
Best regards, Jules.
Edit: I Also treid to install Liniage OS 17 and 18. Via fastboot, twrp and sp flash tool, but also get a bootloop.

Hi
I'm sorry, I cant't answer your question, but I have one to you: I'm trying to install LineageOS on a bv5500pro too (by the guide from here), but I'm stuck at the TWRP installation. Can you tell me how you managed to do it and do you have perhaps a link to the TWRP you used?
I did unlock the bootloader by toggling OEM Unlock in developer settings, then via fastboot: fastboot flashing unlock. Then reboot.
Then I pushed TWRP 3.2 (from this source here, from the tutorial here) by fastboot flash recovery recovery.img. When I tried then to boot directly after flashing into twrp recovery by holding vol up + power, then selecting recovery mode and confirming with vol down, it tries to boot normally instead of recovery. I think, my TWRP flashing didn't work properly. Booting into TWRP by fastboot boot recovery.img doesn't work either, there it reboots and tries to boot normally too. fastboot tells me that it loses connection (normal, since my phone reboots, I think?):
Code:
fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 1.017s]
booting...
FAILED (status read failed (No such device))
finished. total time: 23.457s
What I have to confess, is that I did wipe the system, data and cache partitions using fastboot erase <partition>, perhaps someone knows if I have problems with twrp because of that? (I know that I shouldn't have done this, sometimes curiosity is equal to stupidity...) I did this because I tried to install LineageOS without twrp. Was a bad idea, I know now...
I am on a HP proBook using Debian 10 with adb and fastboot installed. Not sure if MK65xx drivers are installed. Might this pose problems?
Thanks in advance to all here!
EDIT: Sorry, I forgot to mention a lot of things. I corrected some of them here. A more complete overview in another post can be found here.

hi, at least im not alone having trouble with the BV5500pro. I don't remember where i got the twrp exactly, but i uploaded it for you.
File-Upload.net - recovery-verified.rar
Datei: recovery-verified.rar. Die Datei wurde von einem User hochgeladen. Laden Sie auch kostenlos Dateien hoch mit File Upload.
www.file-upload.net
At first i flashed TWRP with fastboot. But then everytime i could boot in twrp only one time. After the next reboot the stock Recovery was reinstalled. So i used the Stock images
Blackview BV5500 Pro factory firmware (flash file)
This Blackview BV5500 Pro firmware flash file (stock ROM) can help you easily un-brick or restore your device to its default or factory state. If you have previously rooted or modified the system (or other) partition of the phone in any way, flashing this stock ROM will overwrite all existing...
www.leakite.com
and replaced the recovery-verified.img with the TWRB image and fashed everyting wit sp flashtool on my phone. After that TWRP was permanent.

Ok, great, thanks for your fast reply. I'll try it again with your image.
GiRonimoon said:
At first i flashed TWRP with fastboot. But then everytime i could boot in twrp only one time. After the next reboot the stock Recovery was reinstalled.
Click to expand...
Click to collapse
How did you boot into TWRP then? By Volume up + power, then selecting recovery mode and confirm with vol down? or by terminal/fastboot command?
edit: small grammar

By Volume up + power.

Thank you
Ok, quick update: Flashing worked, but reboot not, I think. I managed to boot into TWRP, but I managed too once with my image before (I forgot to mention), where the screen was then not responding. A complete description of my case can be found here on xda. Sorry for the late corrections that are made in this post, I'll correct them above...
Now after the flash with the image from GiRonimoon above, I can boot into TWRP and the TWRP start screen shows: TWRP Recovery Project 3.3.0-by *nemo-nemo* (4pda.ru), and when I'm in, the screen is not responding. It was like this with my first TWRP image too, so perhaps the flashing didn't work and I have still my old image which is not working?
GiRonimoon said:
By Volume up + power.
Click to expand...
Click to collapse
Ok. But when I boot into recovery, the exact things I do is:
1. phone powered off
2. Hold volume up + power until boot mode selection screen appears
3. Select recovery mode with volume up, then confirm with volume down
4. the phone reboots (screen goes black for about 1 sec), Blackview logo is shown (as well as a 'orange state' warning message), 5 sec delay because of orange state.
5. screen goes black for 1/2 sec
6. TWRP is open, screen not responding, asking for password for decryption
Exactly the same for booting into recovery via terminal/fastboot (just insert fastboot command at 1.). So since the phone reboots once in between, is it possible that my new TWRP is erased every time? Do your BV5500pro behaves also like this (except the orange state, I think)?
Thanks in advance

How long you are waiting? In my case TWRP needs a long time to start. At first i was thinking that it freezes at startup.
I just foubnd out that every boot into twrp causes a boot loop.. Even when i just boot twrp to see the versionnumber, and then reboot normaly.

GiRonimoon said:
How long you are waiting? In my case TWRP needs a long time to start. At first i was thinking that it freezes at startup.
I just foubnd out that every boot into twrp causes a boot loop.. Even when i just boot twrp to see the versionnumber, and then reboot normaly.
Click to expand...
Click to collapse
When I manage to boot into TWRP it's rather fast - I have to wait around 7 sec or so, maybe 10. But I only manage sometimes. Normally I have to do fastboot boot recovery.img, and after that do the normal steps to boot into recovery. If I try to boot into recovery, it just tries to boot normally (which ends in a bootloop)...
But I think I'll try to flash a stock rom and retry from there, as it was suggested here.