I try this -> [ROM]ASU-JellyBean-Hydro 1.4.6-(8/29) Project melted butter smooooth
I have problem.
I use "COMING FROM ICS BOOTLOADER OR MY PREVIOUS ROM "
All ok, and when call this in cmd "fastboot -i 0x0b05 flash recovery"
get error "error: neither -p product specified nor ANDROID_PRODUCT_OUT set"
And i can't go to CWM, it show andoid with !
Then i use "fastboot -i 0x0B05 flash recovery twrp.blob"
Now only snow ASUS logo and i cant use power + volume down. Only show assus logo. I cant reboot.
Please Help
hi !
no fastboot mod ?
when you plug your tablet on usb, does your pc recognize ?
Hi,
Unfortunately not. Nothing happens. Just asus logo. After a long hold Power button, the screen goes off and then after 10 seconds the logo appears without pressing power button.
So logo stand until the battery runs out.
Is there any way to go back to ICS?
Image is in attachment.
Thanks in advance.
I have the same problem and I found any solution at his time . I hope someone can help us
Did you by any chance try to wipe the data in the bootloader menu?
We haven't any access to bootloader menu
I tried wipe the data, since I did not get into the cold boot (power + volume).
So, this is happening to me since I did wipe the data.
All the time is asus logo, and so until the battery died.
When recharge the battery, all the same thing happening.
EDIT:
I've tried various combinations of buttons. I just noticed that when you hold all three buttons at the same time (vol up, vol down and power), windows show "Unknown device".
It also happened to me when I had problems with the drivers. I guess I'm close decision. Are they now need special drivers for this?
I successfully installed the driver.
As you can see in the picture.
The devices is "Android ADB Interface"
But when I run the following command "fastboot -i 0x0B05 flash recovery twrp.blob" just standing "< waiting for device >" .
To do this -> hold all three buttons at the same time (vol up, vol down and power).
Does anyone know what to do next?
Regards.
I dont think your properly connected. Try reinstalling drivers and check to see if your connected by "adp devices" or "fastboot devices".
Sent from my VS840 4G using xda premium
I had similiar issue, when battery died i recharged and got back into fastboot. Do uhave fastboot option at all? Try a differebpnt computer ive screwed up my usb on 1 device before. Had to recover computer to get access to device again.
Sent from unbricked tf300t.
My mistake,
It is the APX driver for NvFlash, not for fastboot.
The problem is that it has not yet appeared NvFlash for tf300.
Nothing else left but to wait for it to appear.
akicay said:
I successfully installed the driver.
As you can see in the picture.
The devices is "Android ADB Interface"
But when I run the following command "fastboot -i 0x0B05 flash recovery twrp.blob" just standing "< waiting for device >" .
To do this -> hold all three buttons at the same time (vol up, vol down and power).
Does anyone know what to do next?
Regards.
Click to expand...
Click to collapse
you almost have it right. the proper command is (fastboot -i 0x0B05 flash recovery recovery.img ) without the parentheses. check out AllAboutAndroid's video on how to do this just use whatever recovery you want here is the link http://www.youtube.com/watch?feature=player_embedded&v=zSTf6ZY4NGo i hope this helps you guys out
p.s. if it works please do not forget to thank him
hey guys i had a similar problem and this thread tells you how i fixed it
http://forum.xda-developers.com/showthread.php?t=1857719
robgee789 said:
hey guys i had a similar problem and this thread tells you how i fixed it
http://forum.xda-developers.com/showthread.php?t=1857719
Click to expand...
Click to collapse
We don't have fastboot. We are in APX mode. We need an NvFlash solution.
sorry mate my mistake (that will teach me to read while half asleep lol)
Happened to me too. I'm hoping that ASUS will fix it for a reasonable price. Otherwise I'm just going to get a Nexus 7.
Hey All,
My Dad's Xoom died over the weekend - 13months after purchase so is not covered by the warranty. He was browsing a site, it came up with a "Internet is not responding - do you want to continue to wait" message and he clicked Wait - after a second the tablet knocked off. It will not come on by pressing Power and only turns on by pressing Power and Vol +
It gets past the Motorolo logo screen and the device starts the boot animation, about 20 seconds into this it freezes and reboots - this continues in a loop. It's been GEDified and was running the last OTA update 4.1.2 - no root etc.
I can get into the stock recovery and performed a factory reset - but the same thing happens. I've also tried Update From USB with an OTG cable but the screen just shows Choose a package to install and under it has /sdcard but nothing else. I have a dummy zip on both the Flash disk and SD card so it's not reading either.
I've also tried to perform update via ADB - when I select it and connect to a PC (Win 7 32bit) it tries to install drivers but I see In Computer Management that it shows under Unknown. ADB Devices returns List of devices message but nothing under it.
I've also selected the fastboot command at boot, tried fastboot devices and the command does see the Xoom.
So my questions
1) Anyone seen anything like this issue before and know how to fix it?
2) Is it best to try to reinstall the ROM? If so, how do you suggest I can see it with ADB?
3) As I have Fastboot command, could I try to install CWM and see if that sees a ZIP on the sdcard - so I can install a new ROM.
Any help much appreciated :good:
so...I've just done a fastboot oem unlock
and then tried to flash the CWM recovery using the fastboot commands - no errors, press reboot and go into Recovery but still getting Android system recovery 3e :crying:
claned said:
so...I've just done a fastboot oem unlock
and then tried to flash the CWM recovery using the fastboot commands - no errors, press reboot and go into Recovery but still getting Android system recovery 3e :crying:
Click to expand...
Click to collapse
So just to add to this, I found the stock recovery.img, boot.img, userdata.img and system.img and used the fastboot commands to send all to the motorola - all succeeded without error....still the same problem though.
I installed RSD lite and tried a few SBF files but I'm getting an INI error - off to google possible solutions to that now
Hello.
Earlier today I wanted to try a new JB rom to replace ICS so I transfered it into SD card and tried to reboot into recovery.
Instead of getting to recovery, I got stuck in fastboot mode, so I'm assuming recovery has been damaged.
After a whole afternoon of researching this forum I tried for several times this tutorial in order to install a recovery and afterwards a ROM (http://forum.xda-developers.com/showthread.php?t=1088046) and similar ones in both Mac OS X and Windows 7 (tried both USB 2.0 and USB 3.0 so its not a problem from USB) and I didn't succeed at all.
When I am using Windows 7, when I use "fastboot erase recovery", I keep receiving this message "waiting device". If I write "fastboot devices", I don't get results.
When using Mac OS X, I can get via command line to the folder "platform-tools" where fastboot is located but if I write "fastboot erase recovery" or something, it says "command not found". I've read it could be because I have to set fastboot as an environmental variable, but I having trouble setting it (Mac OS Lion).
Thank you so much for reading. Please help me!!! Any clues would be really appreciated!
-----
UPDATE: I finally managed to communicate with the device.
I used the following commands from this tutorial http://androidforums.com/optimus-m-all-things-root/382525-guide-get-out-fastboot-mode-2.html
fastboot erase boot
fastboot erase recovery
fastboot erase system
fastboot flash recovery
The problem is, now I'm stuck at LG Logo, can't access fastboot... Please help, I think it's even worse now.
boot rom, pull out battery and boot normal, it does or not? if it does use terminal emulator or adb push to install custom recovery, adb will work in fastboot if you had checked android debugging
http://forum.xda-developers.com/showthread.php?t=1007244
http://forum.xda-developers.com/showthread.php?t=1146566
grigtm said:
boot rom, pull out battery and boot normal, it does or not? if it does use terminal emulator or adb push to install custom recovery, adb will work in fastboot if you had checked android debugging
http://forum.xda-developers.com/showthread.php?t=1007244
http://forum.xda-developers.com/showthread.php?t=1146566
Click to expand...
Click to collapse
I don't understand what you mean by boot rom. Every time I turn on the phone, (normal or as POWER+HOME+VOL DOWN) it goes into fastboot. When I pull out the battery, and power again it goes again into fastboot...
techdani said:
I don't understand what you mean by boot rom. Every time I turn on the phone, (normal or as POWER+HOME+VOL DOWN) it goes into fastboot. When I pull out the battery, and power again it goes again into fastboot...
Click to expand...
Click to collapse
ok, read here http://forum.xda-developers.com/showthread.php?t=1088046 do exactly what says in this thread
I have 2 Xoom tablets, in Germany, and I took the SD Card from one of them to put it on a new phone, the Tablet kept working fine until last week that I forgot to plug it and the battery ran out. When I charged it and started it, it didn´t work again, I got the Encryption message, nothing happens when I click the Reset Tablet either, I tried putting the SD card from my other Xoom but still nothing. I enter the Recovery mode and did a Factory Reset and the tablet was OK.
Battery run out again yesterday and got the same problem once again, but now factory reset is not working, tablet stays stuck at the "M" logo after doing it, I have repeat the operation a zillion times and nothing, it stays on the M. Plus I can´t turn it off either.
The model is the MZ604 and Android Version 4.0.4
I connected the xoom to the computer after installing the drives but it won´t recognize it. I got to do the fastboot and flashed motorolas images but nothing. I can´t do the adb reboot bootloader command because ADB won´t work, because I don´t have USB Debbuging checked, but I can´t check it now because I can´t get to settings (
What can I do to recover the tablet?
Anyone, is driving me crazy, no matter how many time I flash new images it always stays on the original, so I can´t flash any special recoveries either
I tried RDS too and after the reboot stays the same in the M logo, nothing changes. What can I do?
No ideas? :crying:
I want to save the tablet if possible.
Hi, could you explain exactly what you've tried?
In particular what you mean by "I got to do the fastboot and flashed motorolas images but nothing." and "no matter how many time I flash new images it always stays on the original, so I can´t flash any special recoveries either"
By flashed Motorola's images do you mean you flashed the stock images?
And when you say you flash new images but it always stays on the original, I assume you mean the recovery stays as Xoom default?
Let me know and I'll see if I can help.
alecbond said:
Hi, could you explain exactly what you've tried?
In particular what you mean by "I got to do the fastboot and flashed motorolas images but nothing." and "no matter how many time I flash new images it always stays on the original, so I can´t flash any special recoveries either"
By flashed Motorola's images do you mean you flashed the stock images?
And when you say you flash new images but it always stays on the original, I assume you mean the recovery stays as Xoom default?
Let me know and I'll see if I can help.
Click to expand...
Click to collapse
Yes I mean stock images, and yes, it always stays on Xoom default, it never changes no matter which Recovery image I flash.
The recovery is likely reverting to default because the Xoom does this automatically each boot.
We might be able to give you a recovery that stays put but the booting issue may or may not be something worse.
Being able to fix the recovery in place is reliant on adb working from recovery itself, which I'm unsure is possible.
Whilst you seem to have reasonable knowledge of flashing and using adb/fastbbot, I'll give full instructions.
I assume you have the necessary files for fastboot so I'll skip that.
Place your chosen recovery image in your fastboot folder. (I recommend ClockworkMod Touch recovery from here)
Hold shift and right click the folder containing your recovery image and fastboot files, then select 'open command prompt here'
Your PC is now setup for the fastboot process.
Connect your Xoom to your PC.
Power on your Xoom and once you see the Motorola logo, wait about 3 seconds, and press volume down.
The screen should show the Motorola logo in the center and '--> Android Recovery' in the top left.
Press volume down twice more until the top left says fastboot then press volume up.
The screen will say 'Starting Fastboot protocol support'
Now on your PC, in command prompt run the following:
fastboot flash recovery xxxx.img
Rename xxxx.img to whatever your recovery .img file is namedOnce verified, reboot by holding Volume up and Power. (Keep connected to PC and keep command prompt open)
Again, when you see the Motorola logo wait about 3 seconds and hit volume down. You should see 'Android Recovery' in the top left corner, now press volume up to enter recovery, you should now see your flashed recovery.
This is where I'm unsure. Try running the following:
adb remount
adb shell mv /system/recovery-from-boot.p /system/recovery-from-boot.p.old
adb shell mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.oldIf you are able to run this, this will rename the files that are reverting the recovery to default and prevent it happening again. If not, we can go ahead with attempting to flash stock images anyway.
To flash stock images download Build H.6.2-24 for Retail Europe (found here.)
Extract the files to your fastboot folder.
Again, reboot your Xoom, either by holding volume up and power, or from recovery.
And again, after about 3 seconds press volume down 3 times until the top left says '--> Fastboot' then press volume up.
Now run the following from command prompt:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot oem lockThis will wipe all data on the Xoom, and hopefully reset it to stock.
Finally, run:
fastboot rebootand you should boot into Android 3.2(?), fingers crossed.
If you require further clarification or help let me know.
alecbond said:
The recovery is likely reverting to default because the Xoom does this automatically each boot.
We might be able to give you a recovery that stays put but the booting issue may or may not be something worse.
Being able to fix the recovery in place is reliant on adb working from recovery itself, which I'm unsure is possible.
Whilst you seem to have reasonable knowledge of flashing and using adb/fastbbot, I'll give full instructions.
I assume you have the necessary files for fastboot so I'll skip that.
Place your chosen recovery image in your fastboot folder. (I recommend ClockworkMod Touch recovery from here)
Hold shift and right click the folder containing your recovery image and fastboot files, then select 'open command prompt here'
Your PC is now setup for the fastboot process.
Connect your Xoom to your PC.
Power on your Xoom and once you see the Motorola logo, wait about 3 seconds, and press volume down.
The screen should show the Motorola logo in the center and '--> Android Recovery' in the top left.
Press volume down twice more until the top left says fastboot then press volume up.
The screen will say 'Starting Fastboot protocol support'
Now on your PC, in command prompt run the following:
fastboot flash recovery xxxx.img
Rename xxxx.img to whatever your recovery .img file is namedOnce verified, reboot by holding Volume up and Power. (Keep connected to PC and keep command prompt open)
Again, when you see the Motorola logo wait about 3 seconds and hit volume down. You should see 'Android Recovery' in the top left corner, now press volume up to enter recovery, you should now see your flashed recovery.
This is where I'm unsure. Try running the following:
adb remount
adb shell mv /system/recovery-from-boot.p /system/recovery-from-boot.p.old
adb shell mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.oldIf you are able to run this, this will rename the files that are reverting the recovery to default and prevent it happening again. If not, we can go ahead with attempting to flash stock images anyway.
To flash stock images download Build H.6.2-24 for Retail Europe (found here.)
Extract the files to your fastboot folder.
Again, reboot your Xoom, either by holding volume up and power, or from recovery.
And again, after about 3 seconds press volume down 3 times until the top left says '--> Fastboot' then press volume up.
Now run the following from command prompt:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot oem lockThis will wipe all data on the Xoom, and hopefully reset it to stock.
Finally, run:
fastboot rebootand you should boot into Android 3.2(?), fingers crossed.
If you require further clarification or help let me know.
Click to expand...
Click to collapse
Thanks for the info, sadly I have done almost all that, I can´t use adb commands because I never allowed the tablet to do USB Debbuging, since I wasn´t doing anything that needed that and never thought I would need it. I think I didn´t kept the tablet connected to the PC, so I will try again and let you know if it works.
Like I said before, I'm unsure whether it'll work as I'm not an expert.
However, you may find this helps:
Whilst in recovery and connected to your PC, open Device Manager, find your Xoom, usually under 'Other devices'.
Then right click on your Xoom > Update driver software... > Browse my computer for driver software > Let me pick from a list of device drivers on my computer > Pick your Xoom (either one if there's two shown)
Windows should confirm the driver installed then adb should work in recovery.
I believe ClockworkMod Recovery enables USB debugging anyway, through modifying default.prop
I'd recommend trying the above, and/or if that fails for any reason download Motorola USB Drivers here.
Thanks again but nothing works, I tried rebooting being connected to the PC and the same thing happens, the default recovery from the Xoom stays there, fastboot shows on the command Prompt and in the tablet that everything went ok and the new image was flashed but the rebooting kills it, and I can´t use any ADB commands because of the stupid USB Debugging, if something like this can happen, Motorola should have left it open from default or at least have a fail safe in case something like this could happen. RDS also flashes an image but when it rebbots the whole thing goes to hell, it stays on the damn logo with the same images. I think I can throw the tablet to the trash :crying:
Unless its a serious hardware issue, I wouldn't trash it! It clearly has life as you're able to successfully flash and such.
I'd recommend having a look at the FAQ.
alecbond said:
Unless its a serious hardware issue, I wouldn't trash it! It clearly has life as you're able to successfully flash and such.
I'd recommend having a look at the FAQ.
Click to expand...
Click to collapse
Thanks, but I have done everything, what is the good thing of a successful flash when the tablet returns to it´s previous state as soon as it reboots?
Plus I can´t use one of the most important things, adb, because of the usb debugging, I can´t get into the tablet to activated it, and even if there are recoveries which bypass this thing, I can´t flash them into the tablet, well I can, they just aren´t there after the reboot. And all this because the tablet run out of battery :crying:
ClockworkMod recovery itself allows the use of adb regardless of USB debugging setting.
I believe the command adb remount should allow it.
If adb is denied you can try what I said earlier
Whilst in recovery and connected to your PC, open Device Manager, find your Xoom, usually under 'Other devices'.
Then right click on your Xoom > Update driver software... > Browse my computer for driver software > Let me pick from a list of device drivers on my computer > Pick your Xoom (either one if there's two shown)
Windows should confirm the driver installed then adb should work in recovery.
Click to expand...
Click to collapse
alecbond said:
ClockworkMod recovery itself allows the use of adb regardless of USB debugging setting.
I believe the command adb remount should allow it.
If adb is denied you can try what I said earlier
Click to expand...
Click to collapse
The problem lies with the recovery, I only have the default recovery from the xoom, it doesn´t matter how many times I flash it and everything seems to work correctly, when I restart the tablet I get the default recovery. I don´t understand why this happens, command prompt and the tablet in fastboot mode tell me the recovery has been flashed, but to use it I have to reboot and when I do I always find the same good for nothing recovery.
recovery
Hello,
I don't really understand your problem with the recovery ?
When you flash a custom recovery with fast boot, you restart the tab and after 2 or 3 second you see the Motorola Logo you push the volume down
and volume up button to enter in the new recovery.
If you flash custom recovery but restart completely the TAB without manually enter in the custom recovery, each time you retrieve the original recovery.
pots22 said:
Hello,
I don't really understand your problem with the recovery ?
When you flash a custom recovery with fast boot, you restart the tab and after 2 or 3 second you see the Motorola Logo you push the volume down
and volume up button to enter in the new recovery.
If you flash custom recovery but restart completely the TAB without manually enter in the custom recovery, each time you retrieve the original recovery.
Click to expand...
Click to collapse
Here is what happens, I flash new recovery, I restart the xoom with power and volume up, when the logo appears, after 3 seconds, I push volume down, recovery option shows, I press volume up and the default recovery is still there, not the new one I just flashed.
Is really no one out there that can help? :crying:
There's nowhere stated that, however I believe you already have unlocked your bootloader, didn't you? Because it's REALLY weird that it can't flash the recovery, I mean, you left the battery run out, then after charging you wasn't able to boot normally again.
I'll think a little, but give a check if your bootloader is really unlocked, the device should have installed the recovery, and as you didn't restart it entirely (let it go after the dual core logo), the recovery should be there...
"We think so supersonic and we make our bombs atomic" - Eagle Fly Free (Helloween)
Sent from my Nexus 10 using Tapatalk HD
I have done the fastboot oem unlock command, should I do it everytime? I can´t use adb, because like I said, I never check the USB Debugging, which I have done in my other tablet now, don´t want the same thing to happen twice.
is it dead?
hgokuh said:
is it dead?
Click to expand...
Click to collapse
I unfortunately believe that yes, however I'm still thinking about it! So don't give up! As soon as I have another answer I shall post something
"We think so supersonic and we make our bombs atomic" - Eagle Fly Free (Helloween)
Sent from my Nexus 10 using Tapatalk HD
Hi, I have a OnePlus 6 that was running Pie Beta 3. Yesterday it rebooted on it's own and kept going to qualcomm crash dump mode. At that time, I was able to get into FastBoot but not recovery. I then used the MSMDownload Tool which completed successfully but now it only vibrates with a black/blank screen when I try to turn it on. If I keep holding the power button down, it vibrates every 3 seconds or so. Now I can't get into recovery or fastboot. The only thing I can do is see my phone in device manager by holding down vol+ when connecting it to my laptop.
Any ideas would be appreciated.
Thanks!
Update, now it keeps taking me to fastboot mode every time I turn it on (even while only pressing the power button). I still can't get in Recovery mode.
If you're in fastboot, you already won.
Get TWRP on the start (preferably from eng.stk) > plug in to your PC > fastboot boot twrp.img
You can also find the Stock boot image and run it, see if that helps. fastboot boot <whicheverfile>.img
matteosaeed said:
You can also find the Stock boot image and run it, see if that helps. fastboot boot <whicheverfile>.img
Click to expand...
Click to collapse
I found the stock image but I'm not sure how to put it on the phone with fastboot. Is there a tutorial some where?
I knew to all this stuff.
Thanks in advance!
Patrick
preilly44 said:
I found the stock image but I'm not sure how to put it on the phone with fastboot. Is there a tutorial some where?
I knew to all this stuff.
Thanks in advance!
Patrick
Click to expand...
Click to collapse
It is easy, you do not need to put it on the phone
You'll use this in cmd
fastboot boot (filename).img
Have you used fastboot before ?
matteosaeed said:
It is easy, you do not need to put it on the phone
You'll use this in cmd
fastboot boot (filename).img
Have you used fastboot before ?
Click to expand...
Click to collapse
Unfortunately, I have not used Fastboot before. I did install it with ADB but that's it.
I just connected the phone (device manager shows it's connected) and typed fastboot devices and it doesn't show any. I also tried fastboot boot filename.img and it just sits there "waiting for device" (even though DM shows it connected).
Any help would be appreciated. OnePlus remoted in and used the MSM tool which was successful but it still wouldn't boot so they told me to RMA it which will take about 10 days. I'm hoping to avoid that.
preilly44 said:
Unfortunately, I have not used Fastboot before. I did install it with ADB but that's it.
I just connected the phone (device manager shows it's connected) and typed fastboot devices and it doesn't show any. I also tried fastboot boot filename.img and it just sits there "waiting for device" (even though DM shows it connected).
Any help would be appreciated. OnePlus remoted in and used the MSM tool which was successful but it still wouldn't boot so they told me to RMA it which will take about 10 days. I'm hoping to avoid that.
Click to expand...
Click to collapse
Send me a message. I'll see what I can do.