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
Related
I'm going to probably get a lot of hate for this because there are a ton of forums that might get me here. I did search for about 3 hours tonight and discovered some things but am still confused. I hope someone can help this be more simple. So a friend has a Nexus S that isn't working (I have a Nexus S by the by too). It's unlocked but no ClockWork on it. I can press volume up and power to get to fastboot mode. When I click on "reboot," the phone will just loop on the Google logo. If I click recovery, it starts to boot then shows the triangle with the exclamation mark. From there, I can press power and up or down on volume to get the blue screen which says reboot system now, apply update, wipe, wipe. You get it. I'm stuck...I can also turn off the phone, hold volume up/down and plug in the usb to get to "downloading..."
I want to get this phone working and back to stock. I have the SDK Manager (my phone isn't rooted so I use it to take screenshots) and pda net (which I still don't understand why or how to use with this) and two versions of Odin. It seems like Odin can get this working but I can't get it to work or find a clear guide on how to use it and which ones to use. This is a Tmob Nexus S, I think the i9020. Any help would be so greatly appreciated and I will give you all the credit. Oh, and i can pull up the device on ddms with the sdk manager and can explore the files but there is nothing. I can't find a way to drag a file on the phone to "apply update from /sdcard." Sorry again and thanks again!
callison.168 said:
I'm going to probably get a lot of hate for this because there are a ton of forums that might get me here. I did search for about 3 hours tonight and discovered some things but am still confused. I hope someone can help this be more simple. So a friend has a Nexus S that isn't working (I have a Nexus S by the by too). It's unlocked but no ClockWork on it. I can press volume up and power to get to fastboot mode. When I click on "reboot," the phone will just loop on the Google logo. If I click recovery, it starts to boot then shows the triangle with the exclamation mark. From there, I can press power and up or down on volume to get the blue screen which says reboot system now, apply update, wipe, wipe. You get it. I'm stuck...I can also turn off the phone, hold volume up/down and plug in the usb to get to "downloading..."
I want to get this phone working and back to stock. I have the SDK Manager (my phone isn't rooted so I use it to take screenshots) and pda net (which I still don't understand why or how to use with this) and two versions of Odin. It seems like Odin can get this working but I can't get it to work or find a clear guide on how to use it and which ones to use. This is a Tmob Nexus S, I think the i9020. Any help would be so greatly appreciated and I will give you all the credit. Oh, and i can pull up the device on ddms with the sdk manager and can explore the files but there is nothing. I can't find a way to drag a file on the phone to "apply update from /sdcard." Sorry again and thanks again!
Click to expand...
Click to collapse
It seems your boot.img file either corrupted or missing.
Find a working copy of file, flash it via ADB interface or fastboot. Flash recovery file CWM. If that doesnt work, Try flashing CM7 Rom or someother ROM.
Did you check http://forum.xda-developers.com/showthread.php?t=895545 ?
Odin should be your last resort, if nothing really works for you.
If you want to return to stock, simply flash the NAND backup found here: http://forum.xda-developers.com/showthread.php?t=884093 .
Disclaimer : I take no responsibility of what so ever happens to your phone, however you should be good if you follow proper steps.
Thanks so much for the quick reply. I think I've made some headway...I can "see" the device with cmd by typing adb devices. After that though, I don't understand how to get the stock nexus s rom on the phone. How do I move that file to my phone (what's the line of code I type)? I've tried "adb install <c:\grh78> but it says the syntax isn't correct. Any more help is so greatly appreciated and I appreciate the already prompt response. Thanks!!!
callison.168 said:
Thanks so much for the quick reply. I think I've made some headway...I can "see" the device with cmd by typing adb devices. After that though, I don't understand how to get the stock nexus s rom on the phone. How do I move that file to my phone (what's the line of code I type)? I've tried "adb install <c:\grh78> but it says the syntax isn't correct. Any more help is so greatly appreciated and I appreciate the already prompt response. Thanks!!!
Click to expand...
Click to collapse
Download your rom of choice (stock, custom)
Flash Cwm via fastboot if you haven't already
Boot into recovery.
Use adb push to push your zipped rom to the sdcard (adb push file.zip /sdcard/file.zip)
Use cwm to flash this zip.
Sent from my Nexus S using xda premium
callison.168 said:
Thanks so much for the quick reply. I think I've made some headway...I can "see" the device with cmd by typing adb devices. After that though, I don't understand how to get the stock nexus s rom on the phone. How do I move that file to my phone (what's the line of code I type)? I've tried "adb install <c:\grh78> but it says the syntax isn't correct. Any more help is so greatly appreciated and I appreciate the already prompt response. Thanks!!!
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=9866675
http://forum.xda-developers.com/showthread.php?t=884093
These threads should be a complete solution to your issue.
Disclaimer : I take no responsibility of what so ever happens to your phone, however you should be good if you follow proper steps.
Wow fast responses. I bet it's annoying to help yet another person having issues (again, phone was given to me like this but yeah...) while you guys or gals already know how to do these things very well. Here's where I'm stuck. I enter this code in cmd:
fastboot flash recovery recovery-clockwork-5.0.2.0-crespo.img
and it just says < waiting for device >.
Here's a pic of the screen that I'm on with my phone when i enter the command.
http://imgur.com/Pey3W
If I'm just in the first screen by holding volume up and power, the computer won't read the phone. So I click recovery, the screen shows it's trying to install something then the triangle exclamation mark, i press volume up/down with power and get this screen and the computer can "see" my phone on cmd.
How do I get this flipping clockwork on this phone or get the stock image on my sd card? Thanks again for helping me out guys. I have taken a look at the links you have sent me and that's where i found the download as well as the code to enter. I will keep looking at them but if you find a faster solution, please let me know.
One more thing to be super clear on...when I'm on the screen on the Nexus S that says Fastboot Mode on top in red and Lock State - Unlocked...my computer won't read the phone, therefore I cannot fastboot the recovery img...
callison.168 said:
One more thing to be super clear on...when I'm on the screen on the Nexus S that says Fastboot Mode on top in red and Lock State - Unlocked...my computer won't read the phone, therefore I cannot fastboot the recovery img...
Click to expand...
Click to collapse
So you already tried "fastboot devices" while in fastboot mode?
Edit: Actually it sounds you really want stock so download the complete stock OTA ROM (including boot.img etc.), rename it to update.zip and put it on the root of your sdcard. Boot into the stock recovery like you did already and hit apply update.
EDIT: Go here to download the correct OTA http://forum.xda-developers.com/showthread.php?t=1056062
Find the correct 2.3.6 "Full ROM" for your phone model. Sounds like in those instructions you don't need to rename to update.zip. Haven't seen stock recovery for a while so I don't remember.
If there is a wipe option in the stock recovery then do that first.
Yes I have tried fastboot devices in fastboot mode but nothing because my computer doesn't read the phone in that mode. And yes, I want to put the stock rom on there but that's the key, I can't get access to the root of my sdcard. I can't push anything into the sdcard to flash it. Any ideas what to type or how to access the sdcard? Thanks a million, billion.
Also, I can't get the phone to boot at all, like I can't get passed the Google Logo if I reboot so I can't access the sdcard in the traditional way.
callison.168 said:
Yes I have tried fastboot devices in fastboot mode but nothing because my computer doesn't read the phone in that mode. And yes, I want to put the stock rom on there but that's the key, I can't get access to the root of my sdcard. I can't push anything into the sdcard to flash it. Any ideas what to type or how to access the sdcard? Thanks a million, billion.
Click to expand...
Click to collapse
Connect with adb and type this:
adb shell mount /sdcard
Then type:
adb push rom.zip /sdcard/update.zip
callison.168 said:
Yes I have tried fastboot devices in fastboot mode but nothing because my computer doesn't read the phone in that mode. And yes, I want to put the stock rom on there but that's the key, I can't get access to the root of my sdcard. I can't push anything into the sdcard to flash it. Any ideas what to type or how to access the sdcard? Thanks a million, billion.
Click to expand...
Click to collapse
If fastboot devices returns NOTHING then this is most likely a driver issue. Remove the device through device manager, make sure you have a recent SDK (for the USB driver) and let it re-detect.
callison.168 said:
Also, I can't get the phone to boot at all, like I can't turn on the phone so I can't access the sdcard in the traditional way.
Click to expand...
Click to collapse
If you can get into the boot loader and get a proper USB driver you should be able to flash a recovery.
Once you've flashed Clockwork Mod (recovery) you'll be able to push to the sdcard using ADB or possibly mount the sd card through the CWM menu (although I've yet to have that work).
In order to get a recovery flashed though you need to get fastboot to see your device (unless you can already boot into recovery, then just use ADB).
irishrally said:
Connect with adb and type this:
adb shell mount /sdcard
Then type:
adb push rom.zip /sdcard/update.zip
Click to expand...
Click to collapse
If he's stuck at the Google logo and has a trash boot.img it's not likely he'll be able to get a shell via ADB. Now, if the system is hanging starting a device or looping during boot then that's possible.
krohnjw said:
If he's stuck at the Google logo and has a trash boot.img it's not likely he'll be able to get a shell via ADB. Now, if the system is hanging starting a device or looping during boot then that's possible.
Click to expand...
Click to collapse
He said he can access stock recovery and has connected with adb, unless I read wrong.
irishrally said:
He said he can access stock recovery and has connected with adb, unless I read wrong.
Click to expand...
Click to collapse
Indeed - I saw no clockwork and figured he'd toasted his recovery image as well, but it does look like stock recovery is there. ADB should push fine to the sdcard from recovery then.
More...so if i type in adb reboot bootloader in the recovery screen, it does just that...great. But then my computer makes a noise, a double tap if you will...like a dun dun, like something didn't work. When you plug in something to the computer it usually goes like dun na...but the phone clearly won't read when I'm in bootloader/fastboot mode. So when I type a command, nothing will work...
callison.168 said:
More...so if i type in adb reboot bootloader in the recovery screen, it does just that...great. But then my computer makes a noise, a double tap if you will...like a dun dun, like something didn't work. When you plug in something to the computer it usually goes like dun na...but the phone clearly won't read when I'm in bootloader/fastboot mode. So when I type a command, nothing will work...
Click to expand...
Click to collapse
That noise is that it detects a device has been connected (assuming a recent version of windows). If you want to flash CWM you need to get the driver sorted for the device. No amount of plugging/unplugging is going to fix it.
If you have the stock recovery you can boot into the stock recovery, use adb to push the full OTA package to the sd card and then just flash that from the stock recovery.
callison.168 said:
More...so if i type in adb reboot bootloader in the recovery screen, it does just that...great. But then my computer makes a noise, a double tap if you will...like a dun dun, like something didn't work. When you plug in something to the computer it usually goes like dun na...but the phone clearly won't read when I'm in bootloader/fastboot mode. So when I type a command, nothing will work...
Click to expand...
Click to collapse
Go to the stock recovery like you have done before and type the adb command I wrote above.
Thanks is all I can say. Okay so when I type in the command, this is what I get:
- exec '/system/bin/sh' failed: No such file or directory (2) -
the "stock recovery" I can get into is the picture I posted a link for. That's what I can access as well as the fastboot mode when I first turn on the phone with volume up/power. But when my computer makes the noise that it's connected (using Windows 7 64bit) it makes a different sound then the normal "device connected." Like it's corrupted.
by the way...if we can get this working, I'll post a picture of me holding the fixed phone!
All im getting is the TWRP menu, even after holding the vol down & power. Wont get to the rck screen. Any ideas?
spooky71 said:
All im getting is the TWRP menu, even after holding the vol down & power. Wont get to the rck screen. Any ideas?
Click to expand...
Click to collapse
What happened?
This is a common result if you flash a non-4.2 twrp on a 4.2 bootloader, which will cause a fastboot flash brick.
You will need adb drivers installed on pc, then while in recovery connect your tab to pc, open a command prompt and cd to you android-sdk/platform-tools folder and type
Code:
adb devices
if adb is setup correctly you will get a response with your devices s/n. If this is ok then type
Code:
adb reboot-bootloader
which will reboot your tab to the bootloader screen.
The problem is that whenever I boot up, all i get is the TWRP menu, not letting the pc see the pad. On device manager I get Transformer under other devices. Ive downloaded the drivers, but its not installing them. When I run adb reboot-bootloader, I get device not found.
Have a look here, scroll down and follow on from the where you see the device manager image - this worked for me to get adb working from recovery.
So did this happen after you flashed twrp 2.4.4.0-4.2? or did you flash another twrp or cwm?
Heading out now for a few hours but will be back later
pjc21 said:
Have a look here, scroll down and follow on from the where you see the device manager image - this worked for me to get adb working from recovery.
So did this happen after you flashed twrp 2.4.4.0-4.2? or did you flash another twrp or cwm?
Heading out now for a few hours but will be back later
Click to expand...
Click to collapse
Still nothing. Whats killing me is that it cant detect different sd cards.
Purchased an Lg Gpad 7 Wifi tablet (v400) 2 weeks ago. Came with preinstalled Lollipop android so i couldnt install a recovery rom to flash any other custom roms. Downgraded to Kitkat version following the instructions on Xda forums and succesfully installed Twrp. When i installed Cyanogenmod 12.1 through Twrp i got stuck in fastboot screen.
Any suggestions and / or solutions would be greatly appreciated.
I had a similar problem.. Only mine was stuck at the bootloader. Go in TWRP and repair /data and other partitions. My data partition gave me an error since F2FS is a little flaky and some ROMs corrupted it (claimed they supported it). I would recommend erasing the system, cache and data partition if you can't get into TWRP.
The problem is i cant get out of fastboot whatever i try. It says start on bootloader but the tablet just restarts on an empty screen doing nothing.
Hakalai said:
The problem is i cant get out of fastboot whatever i try. It says start on bootloader but the tablet just restarts on an empty screen doing nothing.
Click to expand...
Click to collapse
if you have an sd card, try removing that, then reboot.
if that doesnt work, try entering fastboot command, fastboot continue
Tried without sdcard and i get the same fastboot screen.
How can i give any commands? The only options i have are Restart Bootloader / Restart / Power off. Tried restarting bootloader but i get nothing in return tablet just stays on with nothing on screen.
Hakalai said:
Tried without sdcard and i get the same fastboot screen.
How can i give any commands? The only options i have are Restart Bootloader / Restart / Power off. Tried restarting bootloader but i get nothing in return tablet just stays on with nothing on screen.
Click to expand...
Click to collapse
you said it was stuck on fastboot, if thats the case, install any needed drivers on your pc, connect device to it, open a terminal in the fastboot dir (after you go get fastboot), then try those commands i gave. you could also try, fastboot reboot dont think i mentioned that before.
bweN diorD said:
you said it was stuck on fastboot, if thats the case, install any needed drivers on your pc, connect device to it, open a terminal in the fastboot dir (after you go get fastboot), then try those commands i gave. you could also try, fastboot reboot dont think i mentioned that before.
Click to expand...
Click to collapse
Did as you said but every command i gave gives me an error message in adb terminal. There are new lines in fastboot menu in tablet now. Bottom two are SECURE BOOT - enabled & LOCK STATE - locked.
Hakalai said:
Did as you said but every command i gave gives me an error message in adb terminal. There are new lines in fastboot menu in tablet now. Bottom two are SECURE BOOT - enabled & LOCK STATE - locked.
Click to expand...
Click to collapse
hmm, ok, im guessing it would have said that normally, when not broken. all the command does is try to release it past where its stuck. it doesnt actually flash, lock, unlock, or change anything.
imo, this seems good, because now we know fastboot is working.
i own lg devices, but not your specific device. i would hate to give you some bad advice and make your tablet broken more, but if it were me in this situation, i would try to flash the factory KK firmware you used to downgrade with odin or however you did it. hopefully, that will clean everything up and let it boot properly.
if for whatever reason you cant do that, we could try extracting the factory file, and just flashing recovery and system, those should be the only things that got changed putting on twrp and cm normally.
Sorry, I have the serious proplem wtih my LG pad V400, I rooted it and using <LG Flash Tool 2014> with <V40010c_00.kdz> to downgrate the firmware but their is error then my LG pad stuck in fastboot menu as with just turn off, restart and restart bootloader. if i seclect one one them the tablet just logged again the fastboot menu
it stuck on the fastboot menu and i cannot do nay think with it. I can restart with factory restore mode but when select yes to restore, it will restart and log in fastboot menu again.
I downloaded adb and fastboot program and put in one folder <Minimal ADB and Fastboot> in C:\Program Files (x86)\Minimal ADB and Fastboot
I dont have recovery image so i download file <cm-13.0-20160421-NIGHTLY-v400-recovery.img> form your link to download TWRP file
move it to folder of fastboot programe and changed its name to <recovery.img>
I turn on the tablet and it waited at fastboot menu
when i run the command <fasboot flash recovery recovery.img> and they said some thing wrong like in picture
please help me
Okay, so I had been out of the flashing game for a while now, and recently got a Pixel 128Gb after using my trusty Nexus 6P, and I attempted to do Fastboot boot-to-root.img, which now has me stuck in a weird bootloop issue.
It boots, gives me the stupid can't be checked for corruption ****, gets to the white Google Screen, then there is a weird visual glitch, a blue line appears near the bottom of the screen, then the phone immediately reboots and does it all over again after doing a ramdump.
I can't even get into recovery to manually flash the stock image, as soon as I try to select RECOVERY it jumps to the boot screen where it tells me again that it cant be checked for corruption, and then starts the bootloop all over again.
ADB cant recognize it for whatever reason either. So now I'm probably not your average ****ed, I'm advanced ****ed.
Any body have any ideas?
boot-to-root is for Android O, you have to follow this guide
I had this same exact problem and I was able to fix it by reflashing the factory image. You said adb cannot recognize your device. But what about fastboot? If you reboot into the bootloader, connect to your PC, and execute "fastboot devices", does your device show? Download the latest factory image here. Extract it and execute flash-all.bat. Let me know if this helps.
You don't understand. When you attempt to reboot and go into recovery the manual way, the moment you select Recovery, the phone reboots and attempts to boot up, fails, performs write to ext4 ramdump, then loops over and over. ADB won't work because it wiped with the fastboot oem unlock which wiped the device, meaning no developer mode, which means no usb debugging.
Doesn't matter. Google is sending me a new one.
:/
jdkzombie said:
You don't understand. When you attempt to reboot and go into recovery the manual way, the moment you select Recovery, the phone reboots and attempts to boot up, fails, performs write to ext4 ramdump, then loops over and over. ADB won't work because it wiped with the fastboot oem unlock which wiped the device, meaning no developer mode, which means no usb debugging.
Doesn't matter. Google is sending me a new one.
:/
Click to expand...
Click to collapse
Fastboot and recovery are two different things. If you hold volume down + power it'll show you the bootloader screen (fastboot), this is where you'd usually select recovery. But if you stay on that screen, you can flash images to your phone. To fix your bootloop, download the boot.img from the stock ROM and use these commands in fastboot:
fastboot flash --slot _a boot boot.img
fastboot flash --slot _b boot boot.img
Then reboot normally.
falsh factory image inside the bootloader, don't need to go to recovery.
Step by Step
Thanks to previous experience with hacking devices (Android, Sony, etc.), patience and only allowing myself to freak out for a few seconds. A couple Google searches lead me to reflashing my Google Pixel 128GB and not sending it back to OEM.
So for the less patient I will break down the steps to do stop the bootlooping.
DON'T PANIC
Either hold down power until your phone turns completely off or wait for the bootlooping to do it for you. It usually only loops a few times before powering down.
Hold Power + Volume Down until it boots into the Fastboot mode.
[This is the screen that says you Phone Stats (serial #, cpu, ram, etc.) and has an Android picture on it laying down.]
Connect your Phone to your computer using a USB 3.0 port.
[My PC wouldn't recognize my phone at all when connected to USB 2.0]
Download from Full Factory Image from Google. { https://developers.google.com/android/images }
[Mine was "7.1.2 (N2G47O, May 2017)" for my Project Fi 128GB Pixel, but make sure you get the one for your phone]
Navigate to where your SDK/Fastboot folder is on your PC
[Unless you moved it, it is usually "C:\Users\USERNAME\AppData\Local\Android\Sdk" by default.]
Unzip the Contents of your Full Factory Image zip file to this location in it's own directory (for cleanliness).
Open a Command Prompt with a Right-Click "Run as Administrator" and navigate you your new zip file's directory.
["\platform-tools\sailfish-n2g47o" or whatever version of the Full Factory Image you used was.]
Type in "flash-all.bat" and wait for your phone to finish its installation. Your phone will restart itself into Fastboot Mode many times during this process.
Once it is finished, you phone should boot into its normal "First Boot Sequence" like you just started it up for the very first time.
At this point you can try flashing something else or use a different technique to update your recovery mode or ROM.
Good Luck.
Hello there. I am writing here because my tablet which i didn't use for a long long (lend it to my grandma) time caught my attention. I wanted to install some custom rom and recovery but when i go to bootloader, I can see 4 things to choose and when i choose RCK or USB the device stops working. Adb works perfectly fine but fastboot not at all. Im attaching photos of what it looks like and all system info You may need in order to help me. On boot logo it says that the device is unlocked.
Also, Happy Easter
Deviss said:
Hello there. I am writing here because my tablet which i didn't use for a long long (lend it to my grandma) time caught my attention. I wanted to install some custom rom and recovery but when i go to bootloader, I can see 4 things to choose and when i choose RCK or USB the device stops working. Adb works perfectly fine but fastboot not at all. Im attaching photos of what it looks like and all system info You may need in order to help me. On boot logo it says that the device is unlocked.
Also, Happy Easter
Click to expand...
Click to collapse
First of all you should get your tablet on the last Asus update on Android 4.2 Jell Bean. That means you must download the latest Asus firmware for TF 300T from here:
https://www.asus.com/Tablets/ASUS_Transformer_Pad_TF300T/HelpDesk_BIOS/
Generally you may install it manually. After download unzip the zip file once. Then copy the "blob" file into the intern memory of your tablet. After rebooting the device the firmware is gonna to being installed automatically. This might be the first and most important step to prepare your device for flashing a custom rom of your choice.
Thanks for response,but after rebooting the device with blob file inserted, system launched normally and no updates procceded :/
Edit: now that I think of that, it looks like i don't have recovery because when i enter it from bootloader all i see is red triangle with "dead robot"
Deviss said:
Thanks for response,but after rebooting the device with blob file inserted, system launched normally and no updates procceded :/
Click to expand...
Click to collapse
Go ahead and try to flash the blob file.
If you don't have, you need „Minimal ADB and Fastboot“, download it from the Internet. The USB driver must be installed on your PC.
Install "Minimal ADB and Fastboot". Then put the blob file in your fastboot folder. Open cmd on your PC as administrator and type: "-i 0x0B05 flash staging blob" without " ".
Let it run. It seems that nothing happens. The whole thing can take up to 20 Minutes, so just stay calm and wait till it’s finished.
Well that's not gonna happen since as i stated in the topic i don't have access to the fastboot option(USB Icon in bootloader). when i pick the option from bootloader it just freezes and and stays like that frever untill i manually pinch the reset button with a needle, also the device is not listed in the command "fastboot devices". I will try running fastboot flash overnight, maybe then it will work...
Deviss said:
Well that's not gonna happen since as i stated in the topic i don't have access to the fastboot option(USB Icon in bootloader). when i pick the option from bootloader it just freezes and and stays like that frever untill i manually pinch the reset button with a needle, also the device is not listed in the command "fastboot devices". I will try running fastboot flash overnight, maybe then it will work...
Click to expand...
Click to collapse
I'm sorry, but I cannot understand what you are doing with the icons.
When you start your device with "power on" and "volume down" together you will reach the fastboot modus automatically shown at your third screenshot. That's it!
There is no need to touch any icon. Keep in mind never ever use the wipe icon. In that case your device gets bricked harshly.