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
Related
I used rom manager to flash to clockworkmod recovery the other day. When it prompted me to confirm my device it said "Huawai U8160" this was wrong my device is ascend II M865. I figured since it was the same company and it didn't give me any other option maybe it would work on my phone too but no dice. When I go to recovery, it just stays at the white huawai splash screen. I have downloaded the ascend II recovery img file from the rom manager site, but don't know how to install it. I looked all over with no luck. Do I need to put it in a specific directory for the 'use other clockwork recovery' thing to recognize it, or does that just look for them online? I read one post that said to replace the .img file in /sdcard/clockworkmodrecovery/download or something but the only file in there is 'tether' and .settings. pls help i need my recovery back
you need to download this here ----> http://playfuldroidz.com/media/recoveries/Ascend2/CWM_4.0.1.4-M865.zip
it's clockworkmod recovery for your device, within the zip are varies files, if you are familiar with fastboot then you can flash manually using that.
If you are not then extract the zip to the root of your C drive, connect your device to the computer with a USB and boot the phone on with volume down and the power button which puts you into fastboot (it may be volume up but i think for your device it is volume down) then double click on the install-recovery-windows.bat and you should be ok
well it wouldn't boot into fastboot it just stayed at the white splashscreen, so i ran the three files from cwm and it worked! So if anybody else has this problem, if you can't boot into fastboot(recovery mode) you can still load the files from your pc using the standard method. I didn't think I could but it worked! Thanks for your help matt!
No worries, and just an FYI fastboot mode stays at the splash screen, so you were actually in fastboot mode
lmao well that exlains a whole lot i am great with computers but phones are new to me learning fast tho..
First things first, I am using the SL101 but as I could not find a place for that, I figured this is the best place for this post.Also I hate posting and creating new threads but there is absolutely no other thread like this, I have been searching for 3 days.
So I rooted my SL101 using vipermod with ease, then downloaded ROM manager but I think here is where I hit an issue, When cwm was installed it asked for me to confirm my device and the only device available to click was "Asus Transformer". As every other transformer tf101 firmware has worked on my tablet, I thought it would be fine. Then I was in the process of flashing Revolver 4.2.1 and my battery went flat so that was not ideal and this is when the issues began.
I booted into cwm recovery (vol- + power and then vol+ on the splash screen) and tried to "install zip from sdcard", I got the "Cant mount sdcard" dialog. I then rebooted and tried to flash the rom from ROM manager, when it rebooted, cwm went through a 20 second loop waiting for sdcard, and it did not find the sdcard so the operation was aborted. I tried a factory reset through cwm and when it rebooted, I would get the splash screen and the ASUS logo with the spinning dots loading, but it would not go past that (bootloop?). From here I could not access the OS at all.
Again into cwm and used the peri OneClick R&R Easyrecoveryv0.4. It went through all the unbricking dialog with three reboots, but one of the commands said it could not find "sdcard/recoveryblob". The system still did not work. I then put it into APX mode (vol+ and power) and installed the APX driver, used the download.bat method but the minute it opens commandprompt, it immediately disconnects the APX driver, the tablet remains in APX mode. This method did not work.
Somewhere along the lines I also managed to format the system and data so not when I turn it on it just goes into the splashscreen with the EEEpad logo and nvidia Tegra.
Also tried adb push to push revolver rom onto the system /sdcard/ directory, that works fine but then again it cant mount sdcard so I cant actually do anything with it. adb devices lists the device as 0123456789ABCDEF recovery. Finally I did try boot twrp.img using fastboot with the "fastboot boot twrp.img" command but it hangs on "waiting for device". fastboot devices also does not list any devices.
So I basically have a tablet whose cwm cant mount sdcard, adb works, fastboot doesnt see the device and I can only go onto cwm on the tablet or splashscreen. Can somebody help me out? I have spent a long time trying to fix this.
Fixed
Hi again, sorry for the double post but after posting that I realised the answer was pretty much staring me in the face and now this has been fixed. so this thread can be closed by the bigdogs.
For future reference to anybody who has this or a similar problem, especially if you format the system and fastboot is not working, the issue is cwm v6.0.1.3 (cant mount sdcard issue), I used the PERI oneclickrecovery v0.4. The unbrick selection did not work for my slider as I had already pretty much wiped any data from the system that could have been salvaged by the unbrick, but if you press "r" in the main menu it flashes a new recovery tool over cwm, and this new tool can access external sdcard so just upload the rom zip file onto there and flash. :fingers-crossed: Revolver 4.2.1 is now flashed and working. :victory:
I have a Xoom WiFi on Android 4.1.2
I was trying to Unlock, Flash Recovery, Root and then Flash a Rom. I have Flashed on my phone a couple of times so I am a little familiar with the process.
I did the following:
1.
adb reboot bootloader
fastboot oem unlock
fastboot reboot
2.
adb reboot bootloader
fastboot flash recovery "name of file".img. (the file i used was "recovery-clockwork-touch-6.0.3.1-wingray.img").
3.
Once you have verification on your device that this has been flashed, reboot your device by holding volume up + power.
Then 3 seconds after you see the Motorola logo, hit volume down. You should now see "Android Recovery" in the top left corner. Hit volume up to boot into recovery.
This is where things go wrong.
Upon reboot,
I press down volume upon seeing the logo.
It then says Android Recovery.
I then press up volume.
then it says entering Android Recovery Mode
reading ODM Fuse:1
Then the Green Android man shows up with the red triangle.
It sits there for a while then boots into Android normally.
I have been searching for a solution since this morning. Everything I found about this has not helped.
Earlier in the day I did Flash a different Recovery so I think I have two. I installed the ROM manger app. It shows two installed.
ClockworkMod Recovery
Team Win Recovery Project (TWRP)
I am stuck as to what to do... Please help.
Thanks
Jim
jbfoster said:
I have a Xoom WiFi on Android 4.1.2
I was trying to Unlock, Flash Recovery, Root and then Flash a Rom. I have Flashed on my phone a couple of times so I am a little familiar with the process.
I did the following:
1.
adb reboot bootloader
fastboot oem unlock
fastboot reboot
2.
adb reboot bootloader
fastboot flash recovery "name of file".img. (the file i used was "recovery-clockwork-touch-6.0.3.1-wingray.img").
3.
Once you have verification on your device that this has been flashed, reboot your device by holding volume up + power.
Then 3 seconds after you see the Motorola logo, hit volume down. You should now see "Android Recovery" in the top left corner. Hit volume up to boot into recovery.
This is where things go wrong.
Upon reboot,
I press down volume upon seeing the logo.
It then says Android Recovery.
I then press up volume.
then it says entering Android Recovery Mode
reading ODM Fuse:1
Then the Green Android man shows up with the red triangle.
It sits there for a while then boots into Android normally.
I have been searching for a solution since this morning. Everything I found about this has not helped.
Earlier in the day I did Flash a different Recovery so I think I have two. I installed the ROM manger app. It shows two installed.
ClockworkMod Recovery
Team Win Recovery Project (TWRP)
I am stuck as to what to do... Please help.
Thanks
Jim
Click to expand...
Click to collapse
Please follow the Root Method mentioned in the 2nd Post of LAIOT thread . You can easily find it within the Development Forum , or my signature.
"This Story Ends Where It Began" - Octavarium (Dream Theater)
Sent from my GT-I9505
One of the files link is broken.
The requested URL /atftas/OEM/Motorola/XOOM/Xoom-Universal-Root.zip2 was not found on this server.
I have another problem.
Now I have two devices. If I unplug the Xoom it still finds emulator 5554. What is emulator 5554?
Thanks
Jim
I got around the emulator 5554 problem by using the -d option. I followed everything and all went fine. I installed the app Root Checker Basic but it says Sorry! this device does not have proper root access.
All steps completed with no errors.
I guess I'm stuck again.
Jim
I flashed back to stock. Did all the steps again and the same thing.
I tried several more times and it still would not work.
I went to another site and downloaded the root.zip and it worked this time. The root file on this site would not work for for some reason.
The Android man with the red triangle problem is also gone. Not sure what fixed it. I assume that it was because I flashed back to stock and used a different root.zip file.
Thanks for all the help
Jim
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.
Hi
My Max (M1) does not boot into recovery mode. I have researched and tried all key option, but I can only ever get the bootloader or a normal boot.The only way it works is via adb reboot recovery, fastboot reboot recovery gives me a normal boot.
The problem is that when booting after a recovery flash the partition seems to be overwritten again, so when I boot recovery from bash I only ever get the standard recovery manager, not the one I flashed. So I guess I would have to do it via the phone keys after flashing, right?
Am I missing something?
hiya there!
do your volume keys work correctly? the phone should boot into recovery if the vol- is detected while the phone is starting up (while its showing the asus logo/powered by android)
the only way you could stop the OS from overwriting your custom recovery is by booting straight into it right away (fastboot reboot-recovery doesn't usually work, atleast for my phone).
are you sure you're flashing the correct recovery? if the recovery is corrupt (or atleast not for your specific phone), the phone tends to just ignore and boot to the OS
does vol- while powering on the phone work when its running the standard recovery?
keep in mind, your phone's model is usually listed as one of those (as long as its a legit Max (M1)):
X00PD
X00P (i dont find a diff. between this and X00PD, considering that the stuff made for it works on it aswell)
Z555KL
Z556KL