Database Info

Easy way to install the latest update manually?

I'm running a 100% stock sensation and the OTA update hasn't hit my phone yet.
Is there an easy way to install it from my sd card? I read somewhere that i'd need to boot into recovery, but I can't get that to work either.
Any help would be greatly appreciated.

download the zip file
rename it to update.zip
put it on the root of your microsd card.
boot into recovery.
either TURN OFF FAST BOOT in the power menu and turn off phone, or pull the battery and put it back in
hold down volume down and power.
you'll get into bootloader.
use the volume buttons to go up/down and select recovery. press power to select.
you'll get triangle with ! on it.
press power then volume up real quick/at the same time
you'll get the stock recovery.
go down to select install update.zip.

Download the OTA to the root of the sd card. Then take batt out. Put batt back in. Then hold- vol down + power. That will take to you the hboot menu. Let it look for the .img and then it will take you to a new menu. From there click on 2nd icon, recovery. It will either start for you or you will get a red triangle. If you get the red triangle. press vol up+ power. then click on update from sd card, then click on the update file. Hope this helps.
Edit- I was too slow typing

Root folder would just be /sdcard if I'm using root explorer, right?
Can't get it to work, I'm sure I'm doing something stupid and not realizing it.

When I select 'apply update from sdcard' it says Invalid Operation and then reboots the phone without updating anything
It also says: "E:Can't open/cache/recovery/command" when I open up that second console.
Any clue why that's happening?

RuizGT said:
Root folder would just be /sdcard if I'm using root explorer, right?
Can't get it to work, I'm sure I'm doing something stupid and not realizing it.
Click to expand...
Click to collapse
Yes. If you have custom recovery, it's not going to work. Has to be stock recovery.

mtbaird5687 said:
When I select 'apply update from sdcard' it says Invalid Operation and then reboots the phone without updating anything
It also says: "E:Can't open/cache/recovery/command" when I open up that second console.
Any clue why that's happening?
Click to expand...
Click to collapse
Did you rename the zip file to update.zip?

nxt said:
Yes. If you have custom recovery, it's not going to work. Has to be stock recovery.
Click to expand...
Click to collapse
That's what I'm using. Phone is still stock.

Yep I renamed it to update.zip. Below is what shows up right after I click 'install update from sd card'
--Invalid Operation--
success rebooting by reasonem-00

mtbaird5687 said:
Yep I renamed it to update.zip. Below is what shows up right after I click 'install update from sd card'
--Invalid Operation--
success rebooting by reasonem-00
Click to expand...
Click to collapse
Same here.

This is really frustrating, I hope it doesn't affect my ability to get the OTA update.
Does anyone have any idea why we're getting the "Illegal Operation" error?

I didn't rename the OTA. It kept it as it was.... all though one thing that I did notice was that I would continue to get an error until the OTA was at the top of the list... Sounds weird but just keep trying.

Ok, on my phone when it downloaded the update, it put it in the /download/ folder on my microsd card.
You guys should try that maybe.

nxt said:
Ok, on my phone when it downloaded the update, it put it in the /download/ folder on my microsd card.
You guys should try that maybe.
Click to expand...
Click to collapse
I'll try that right now.
nope, same thing.I'll try to re-dl and keep the regular file name.
Double edit; tried the full file name in download folder, same thing again.

nxt said:
download the zip file
rename it to update.zip
put it on the root of your microsd card.
boot into recovery.
either TURN OFF FAST BOOT in the power menu and turn off phone, or pull the battery and put it back in
hold down volume down and power.
you'll get into bootloader.
use the volume buttons to go up/down and select recovery. press power to select.
you'll get triangle with ! on it.
press power then volume up real quick/at the same time
you'll get the stock recovery.
go down to select install update.zip.
Click to expand...
Click to collapse
Do you know which one I would need for Canada's Virgin Mobile and where I can find it? I tried Searching and I couldn't find it.

mtbaird5687 said:
When I select 'apply update from sdcard' it says Invalid Operation and then reboots the phone without updating anything
It also says: "E:Can't open/cache/recovery/command" when I open up that second console.
Any clue why that's happening?
Click to expand...
Click to collapse
I am getting the same error.stock ROM never rooted...may be European update don't work for Asian....
Sent from my HTC Sensation Z710e using XDA App

Asian HTC Sensation Z710e
no go for me either. I get a same error message...
I've used OTA file for European and also US T-Mobile phones. It just wont work on my (Asian WWE) HTC Sensation.
It seems like I am destined to wait until end of September before I get my update...
I have purchased my phone at negrielectronics.com
Any other users of this version of Sensation? What's your experience?

I gave up, did s-off, and did a 1.45 based rom instead, heh.

I was lucky enough to get the OTA today and the other errors I had didn't prevent me from getting the update.
Good luck guys!

mtbaird5687 said:
I was lucky enough to get the OTA today and the other errors I had didn't prevent me from getting the update.
Good luck guys!
Click to expand...
Click to collapse
Nice. I work at a tmo retailer, the demo sensation had the ota update symbol in the notification bar when I was unplugging phones this morning, it installed fine, just pissed me off more about mine. :|

[Q] only booting into recovery after updates/more please help

Hi all I've been an idiot and am hoping I haven't done any permanent damage to my unlocked/rooted tf300 so before I continued doing anymore I wanted to make a post here asking for any help possible.
I hadn't updated to the 4.2.1 build yet and finally decided to bite the bullet an hour or two ago since I wanted to try out the newest version of cromi. I was using the patched 2.4 twrp and initially updated to the 10.6.1.8 update using fastboot, then decided I might as well do the 10.6.1.15.3 using the fastboot again and finally updated to the 2.5 twrp using fastboot. As the jb updates were happening I would get the message that the tablet wasn't rooted and to install SuperSU, and because I'm a dumb creature of habit both times I just instinctively swiped to install, only realizing what I had done after the fact.
After all of this I was still able to at least turn on my tablet and get to the home screen, but unable to do a factory reset in recovery (the log would say "unable to" on every task, but the final message would still say successful?) or have any options to install a rom within it. I had also noticed that I wasn't rooted anymore. I used motochopper and was rooted again for the time being and used a couple apps that required root just to make sure that was the case. At this point I rebooted the tablet and holding down the power button/volume down, I think this is the point where my tablet would just boot straight into recovery, unable to boot into anything except recovery since even if I hold down the power button/volume down.
I've tried to do a factory reset and get the same response as earlier and I get a "failed" message when I try to do a data format. I know there will be at least a couple glaring red flags within this message to anybody who knows much more than I do, but I'm hoping this isn't the end of my tablet and would greatly appreciate any assistance provided. If you need any extra information please let me know I'll do the best I can with providing whatever would be useful, thank you in advance for your time and help.

did you install the 4.2 recovery version?

if you have TF300T (not TG or TL), you need to flash openrecovery-twrp-2.5.0.0-tf300t-4.2.blob which you can download from the TWRP official website.
On 10.6.1.15.3, to enter fastboot mode, you need to reboot your tablet and hold volume down button until you see 3 icons (RCK, Android logo, and Wipe). At this point, release the volume down, but do not select any option and do not press volume up. Without doing anything, you are now in fastboot mode.
Do the usual thing you did... connect your tablet to PC via your USB cable, run cmd.exe and change your path to where you have fastboot and the "openrecovery-twrp-2.5.0.0-tf300t-4.2.blob" file. Type:
fastboot -i 0x0B05 flash recovery openrecovery-twrp-2.5.0.0-tf300t-4.2.blob
wait until you see a blue progress bar on your tablet. When that completes without error, type:
fastboot reboot
Enter TWRP recovery, Wipe dalvik and cache, try flashing the official ASUS 10.6.1.15.3 stock ROM again. Do not swipe to install SuperSU to root at this point. Just tap "Do not install." If installation goes well, reboot, and re-flash "openrecovery-twrp-2.5.0.0-tf300t-4.2.blob", as installing the official stock ROM may have overwritten your TWRP recovery.
To root, use motochopper like you did. Or alternatively, flash a custom 10.6.1.15.3 stock-compatible kernel and let TWRP install SuperSU (Swipe to install) when prompted before you reboot system. You will get a SuperSU installer app on your launcher. Run that app and choose "Play" or "install from recovery" option. I can confirm that both method works without apparent issues. Choosing Play would be easier and faster than having to go to recovery to flash SuperSU binaries.
I hope this works for you.

matt95 said:
did you install the 4.2 recovery version?
Click to expand...
Click to collapse
Thank you here's hopefully where the problem lies, I accidently downloaded the -JB version, not the -4.2.
How would I be able to fix this? In response to both this and ImmovableObject's post, holding down the power/volume down buttons doesn't take me to the screen with the 3 icons anymore where I can run fastboot, it just sends me into recovery mode without those options ever showing up.

peerpressure said:
Thank you here's hopefully where the problem lies, I accidently downloaded the -JB version, not the -4.2.
How would I be able to fix this? In response to both this and ImmovableObject's post, holding down the power/volume down buttons doesn't take me to the screen with the 3 icons anymore where I can run fastboot, it just sends me into recovery mode without those options ever showing up.
Click to expand...
Click to collapse
there is no solution to this unfortunately, your tab is bricked... we have to wait for a fix but it will take some time

matt95 said:
there is no solution to this unfortunately, your tab is bricked... we have to wait for a fix but it will take some time
Click to expand...
Click to collapse
That's too bad I'm leaving for a month and was hoping to be able to use it while I was gone, oh well nobody to blame but myself looks like I'll be without a tablet for a while. Thank you guys for your time and help I really appreciate it, hopefully the fix will come at some point soon in the near future.

I apologize for this last post feel free to ignore it because it's moreso just asking for an opinion but I thought I might as well ask, if you (or anybody else) were in this position would you wait for a solution to hopefully come out or cut your losses and try to sell the tablet on somewhere like ebay as a nonfunctioning unit?
edit: and if I did sell it would I have to worry about this problem being fixed and the buyer would have access to everything currently on the tablet or is that information inaccessible/wiped?

peerpressure said:
I apologize for this last post feel free to ignore it because it's moreso just asking for an opinion but I thought I might as well ask, if you (or anybody else) were in this position would you wait for a solution to hopefully come out or cut your losses and try to sell the tablet on somewhere like ebay as a nonfunctioning unit?
edit: and if I did sell it would I have to worry about this problem being fixed and the buyer would have access to everything currently on the tablet or is that information inaccessible/wiped?
Click to expand...
Click to collapse
probably this will be fixed, i don't know why but we are working onto it... i won't sell it just for few dollars.... it's not worth it

One idea (although I haven't tested it) to install TWRP 4.2 inside of TWRP, then reboot. If this doesn't work, then I suggest buying another motherboard off of eBay and replace it with the one in your tablet.

c0ded said:
One idea (although I haven't tested it) to install TWRP 4.2 inside of TWRP, then reboot. If this doesn't work, then I suggest buying another motherboard off of eBay and replace it with the one in your tablet.
Click to expand...
Click to collapse
Thank you so much for the response, would there be a way to go about getting the 4.2 version onto my tablet though if it only boots into recovery, even when you hold down the power button/volume down? When I plug the tablet into my computer it isn't able to be recognized (I'm assuming just because it only gets to the recovery screen).

Try running "fastboot devices" on your computer while in the bootloader. Does it show anything?
Correct me if I'm wrong, but I remember reading somewhere the when in the bootloader, fastboot automatically launches on 4.2.
---------- Post added at 08:48 PM ---------- Previous post was at 08:31 PM ----------
It IS possible to flash recovery while you're in recovery. Here's how (from tobdaryl; twrp can be gotten from here: techerrata.com/file/twrp2/tf300t/openrecovery-twrp-2.4.4.0-tf300t-4.2.blob):
adb push openrecovery-twrp-2.4.4.0-tf300t-4.2.blob /sdcard/openrecovery-twrp-2.4.4.0-tf300t-4.2.blob
adb shell
su
dd if=/sdcard/openrecovery-twrp-2.4.4.0-tf300t-4.2.blob of=/dev/block/mmcblk0p4
adb reboot
An then to flash stock (once again, from tobdaryl; roms can be gotten from here: forum.xda-developers.com/showthread.php?t=1697227):
adb push blob /sdcard/blob
adb shell
su
dd if=/sdcard/blob of=/dev/block/mmcblk0p4
adb reboot

Oh, well it hasn't been letting me go into the bootloader on the tablet, just boots into recovery regardless, but for what it's worth the options/commands still show up as shown in the attachment. I don't know if that's something they do anyways though.

What about "adb devices"?

c0ded said:
What about "adb devices"?
Click to expand...
Click to collapse
The list of devices attached doesn't show any it looks like it can't find it

Have you tried flashing 4.2 within TWRP?

How would I be able to go about doing that? (sorry for the inexperience and delays in response, have to wait five minutes between posts)

Download the 4.2 rom (http://www.androidfilehost.com/?fid=22926241640219416), extract it, and put the extracted zip file on to a MicroSD card. Boot into TWRP and install it from the external MicroSD (I don't know how to go about that since I don't have TWRP).
Also, you shouldn't be waiting 5 minutes between each response. You are over 10 posts.
---------- Post added at 09:12 PM ---------- Previous post was at 09:06 PM ----------
Oops. I just read the statement carefully and realized that you have to be verified by a moderator, not have over 10 posts.

I tried it out but sadly it looks like the external microsd is unable to mount so I can't pull anything off of it
edit: It gives me the option to mount a system when the ext. microsd is in but not when it is out, I don't know if that is of any help? Every other option isn't possible though.

What type of MicroSD card are you using?

A sandisk 32gb class 4 microsdhc, it's the same one I had been using with the tablet previously before this all happened

I need help rooting my New Tab 7.7 i815 guys!

I have searched all over the web and this forum and after literally days of searching all I have found seem to be from late 2011. And none of the several methods will to root my Galaxy Tab 7.7 i815 Verizon LTE tablet. My question is, is there a current way to root my tablet? I really want to root and custom rom my tablet, but I am ready to pull my hair out. I have rooted my Galaxy S4 and flashed a custom rom and it was so easy, and is just so much better. I woulsd love to flash a Jelly Bean rom on this tablet, thats my goal. Any help would be hugely appreciated. Thanks

ddrumbum said:
I have searched all over the web and this forum and after literally days of searching all I have found seem to be from late 2011. And none of the several methods will to root my Galaxy Tab 7.7 i815 Verizon LTE tablet. My question is, is there a current way to root my tablet? I really want to root and custom rom my tablet, but I am ready to pull my hair out. I have rooted my Galaxy S4 and flashed a custom rom and it was so easy, and is just so much better. I woulsd love to flash a Jelly Bean rom on this tablet, thats my goal. Any help would be hugely appreciated. Thanks
Click to expand...
Click to collapse
You don't need to root to install a custom ROM. You need to flash a recovery, and then use that to flash the ROM. I'm not sure if Verizon added more difficulties to install a recovery, though; my P6800 was as easy as it gets to go from Honeycomb to anything else.
Recoveries: http://forum.xda-developers.com/showthread.php?t=2352967
JB ROMs: http://forum.xda-developers.com/showthread.php?t=2139766
Good luck!

Steve_max said:
You don't need to root to install a custom ROM. You need to flash a recovery, and then use that to flash the ROM. I'm not sure if Verizon added more difficulties to install a recovery, though; my P6800 was as easy as it gets to go from Honeycomb to anything else.
Recoveries: http://forum.xda-developers.com/showthread.php?t=2352967
JB ROMs: http://forum.xda-developers.com/showthread.php?t=2139766
Good luck!
Click to expand...
Click to collapse
Thanks Steve! I feel like an idiot looking all over for a root and not a flash. Ok could you tell the steps to flash this please. Please forgive my noobness, and thank you so much for your reply! I think I have an idea how to do it, but I just want to be certain.

I need the same thing. Let me know how it works out

ddrumbum said:
Thanks Steve! I feel like an idiot looking all over for a root and not a flash. Ok could you tell the steps to flash this please. Please forgive my noobness, and thank you so much for your reply! I think I have an idea how to do it, but I just want to be certain.
Click to expand...
Click to collapse
taiwwa said:
I need the same thing. Let me know how it works out
Click to expand...
Click to collapse
I'd rather let someone who actually owns an i815 give you exact instructions, but the general idea for Samsung devices is:
- Get Odin on your PC, for example, from here
- Reboot your device to download mode (power off, then power it on while holding volume down or volume down + home)
- open Odin
- Put the recovery .tar (or .tar.md5) file on "PDA", DON'T CHANGE ANYTHING ELSE, and click "start". The file will flash, and then the device will reboot
- To enter the recovery, power on while holding power+vol. up
- Make a backup
- Factory reset
- Install the ROM .zip
I can't tell you if this works on the Verizon version, though; or if there is anything else involved. I have an international P6800, where this works fine. Maybe someone who has the same version can help?

Steve_max said:
I'd rather let someone who actually owns an i815 give you exact instructions, but the general idea for Samsung devices is:
- Get Odin on your PC, for example, from here
- Reboot your device to download mode (power off, then power it on while holding volume down or volume down + home)
- open Odin
- Put the recovery .tar (or .tar.md5) file on "PDA", DON'T CHANGE ANYTHING ELSE, and click "start". The file will flash, and then the device will reboot
- To enter the recovery, power on while holding power+vol. up
- Make a backup
- Factory reset
- Install the ROM .zip
I can't tell you if this works on the Verizon version, though; or if there is anything else involved. I have an international P6800, where this works fine. Maybe someone who has the same version can help?
Click to expand...
Click to collapse
okay, well,
First of all, I couldn't find the backup option so I just wiped the device.
Secondly, I have one of the CWM 10.1 zips on my sdcard. I keep on getting the error "failed to verify the whole file structure."
edit: okay, this is the real problem. I can't get the CWM or the TWRP recovery on the samsung tab 7.7 via Odin. That is the real problem.

Okay, I figured it out. Basically, the hiccups come from two things: have to make sure USB debugging is selected in the developer options in the settings.
Secondly, it appears that CWM needs to not have the USB plugged in when you want to activate its recovery mode.
Now, all I need to do is figure out how to install the play store.
And...I"m afraid that from now on, system updates means that the entire device gets wiped?
CM10.1 JB is sooo much better than the lousy Samsung touchwiz or whatever junk that they came up with.

It's all up and running with GAPPS too. Weirdly, for GAPPS, it's not a good idea to download your GAPPS while on a mac. Download on PC. The mac seems to automatically decompress zip files, and then if you recompress them, it does so in a way that CWM does not recognize.
Otherwise, it's okay. Some hiccups and oddities. I am running a build made in July 2013, by a guy in Hong Kong, I believe. Cyanogen updates don't come up with anything, not even old versions. Also, the lock screen is always in landscape mode for some reason, never portrait.
But this is how to do it...
Basically, the way it goes is this. You have to replace the recovery bootloader with a custom bootloader in order to load the custom build. You do this by Odin.
First step is getting the tablet ready. It has to be in USB debugging mode. You then have to power it off. Power it on again while holding on to the volume down button. get through the screen and wait. Then you connect it to the computer and run Odin. On the "PDA" tab, you select the CWM .tar file and hit "start."
Second step is to download a build of CWM and put it on a micro-sd card. Has to be in .zip format. Also, download the CWM GAPPS .zip file and put it on the microsd.
Third step is to unplug the device from USB, and go into recovery mode. You do this by turning it off. Then turn it on again while holding volume up.
You should see the CWM screen. Make sure to clear/reset the device and wipe out all caches. Then install from external sd card. I think you can also install the GAPPS after installing the OS.
Then reboot and you're good.
edit: landscape lock screen is just a checkbox in the setting.
New problem: really slow transfers to sd card through USB. Really really slow. Like 3-4x as slow as just connecting sd card to sd card reader.

taiwwa said:
It's all up and running with GAPPS too. Weirdly, for GAPPS, it's not a good idea to download your GAPPS while on a mac. Download on PC. The mac seems to automatically decompress zip files, and then if you recompress them, it does so in a way that CWM does not recognize.
Otherwise, it's okay. Some hiccups and oddities. I am running a build made in July 2013, by a guy in Hong Kong, I believe. Cyanogen updates don't come up with anything, not even old versions. Also, the lock screen is always in landscape mode for some reason, never portrait.
But this is how to do it...
Basically, the way it goes is this. You have to replace the recovery bootloader with a custom bootloader in order to load the custom build. You do this by Odin.
First step is getting the tablet ready. It has to be in USB debugging mode. You then have to power it off. Power it on again while holding on to the volume down button. get through the screen and wait. Then you connect it to the computer and run Odin. On the "PDA" tab, you select the CWM .tar file and hit "start."
Second step is to download a build of CWM and put it on a micro-sd card. Has to be in .zip format. Also, download the CWM GAPPS .zip file and put it on the microsd.
Third step is to unplug the device from USB, and go into recovery mode. You do this by turning it off. Then turn it on again while holding volume up.
You should see the CWM screen. Make sure to clear/reset the device and wipe out all caches. Then install from external sd card. I think you can also install the GAPPS after installing the OS.
Then reboot and you're good.
edit: landscape lock screen is just a checkbox in the setting.
New problem: really slow transfers to sd card through USB. Really really slow. Like 3-4x as slow as just connecting sd card to sd card reader.
Click to expand...
Click to collapse
FANTASTIC! THANK YOU SO MUCH! One last question. You said "Second step is to download a build of CWM and put it on a micro-sd card. Has to be in .zip format. Also, download the CWM GAPPS .zip file and put it on the microsd" So which ones did you use? I just don't want to screw anything up. Thanks again.

HELP!!
taiwwa said:
It's all up and running with GAPPS too. Weirdly, for GAPPS, it's not a good idea to download your GAPPS while on a mac. Download on PC. The mac seems to automatically decompress zip files, and then if you recompress them, it does so in a way that CWM does not recognize.
Otherwise, it's okay. Some hiccups and oddities. I am running a build made in July 2013, by a guy in Hong Kong, I believe. Cyanogen updates don't come up with anything, not even old versions. Also, the lock screen is always in landscape mode for some reason, never portrait.
But this is how to do it...
Basically, the way it goes is this. You have to replace the recovery bootloader with a custom bootloader in order to load the custom build. You do this by Odin.
First step is getting the tablet ready. It has to be in USB debugging mode. You then have to power it off. Power it on again while holding on to the volume down button. get through the screen and wait. Then you connect it to the computer and run Odin. On the "PDA" tab, you select the CWM .tar file and hit "start."
Second step is to download a build of CWM and put it on a micro-sd card. Has to be in .zip format. Also, download the CWM GAPPS .zip file and put it on the microsd.
Third step is to unplug the device from USB, and go into recovery mode. You do this by turning it off. Then turn it on again while holding volume up.
You should see the CWM screen. Make sure to clear/reset the device and wipe out all caches. Then install from external sd card. I think you can also install the GAPPS after installing the OS.
Then reboot and you're good.
edit: landscape lock screen is just a checkbox in the setting.
New problem: really slow transfers to sd card through USB. Really really slow. Like 3-4x as slow as just connecting sd card to sd card reader.
Click to expand...
Click to collapse
ddrumbum said:
FANTASTIC! THANK YOU SO MUCH! One last question. You said "Second step is to download a build of CWM and put it on a micro-sd card. Has to be in .zip format. Also, download the CWM GAPPS .zip file and put it on the microsd" So which ones did you use? I just don't want to screw anything up. Thanks again.
Click to expand...
Click to collapse
OK I followed your steps flawlessly, and my screen will not go past the paranoidandroid 3+ boot screen. Please help me I'm freaking out

Try framaroot. Install the app, usb debug on and root.
Now you can install recovery with a lot of apps.
Habby rooting

[Q] HKC P776A Android tablet stuck in twrp/cwm bootloop

Ok I finally got this tablet rooted using some chinese oneclick root tool worked great do to it was the only kit that was able to root it and i installed supersu apk to replace to chinese version worked and i went to update supersu and hit the twrp (not knowing what it was at the tim stupid right i know lol) and now it is stuck in the twrp/cwm bootloop and i cant get into recovery mode when i try it says updating img blah blah and restarts back into the bootloop. It is running 4.1.1 JB and has a micro sd card slot.There is a pic in the atachment because i dont know how to upload it to this post but it is just a pic no "extras" are included no viruses maleware ect just a pic

parkourgamer said:
Ok I finally got this tablet rooted using some chinese oneclick root tool worked great do to it was the only kit that was able to root it and i installed supersu apk to replace to chinese version worked and i went to update supersu and hit the twrp (not knowing what it was at the tim stupid right i know lol) and now it is stuck in the twrp/cwm bootloop and i cant get into recovery mode when i try it says updating img blah blah and restarts back into the bootloop. It is running 4.1.1 JB and has a micro sd card slot.There is a pic in the atachment because i dont know how to upload it to this post but it is just a pic no "extras" are included no viruses maleware ect just a pic
Click to expand...
Click to collapse
Super old I know but my kids tablet is doing this now. Did you ever find a fix?

KilluminatiStyle said:
Super old I know but my kids tablet is doing this now. Did you ever find a fix?
Click to expand...
Click to collapse
Pro tip: Don't bumb old threads like this. You might not even have similar problems. Instead create a new thread regdaring your issue.
Now, post your tablet info HERE:
Root staus?
Can you boot in recovery? If yes what recovery do you have?
Tablet model
Android version
What happened
What have tried to fix it

janekmuric said:
Pro tip: Don't bumb old threads like this. You might not even have similar problems. Instead create a new thread regdaring your issue.
Now, post your tablet info HERE:
Root staus?
Can you boot in recovery? If yes what recovery do you have?
Tablet model
Android version
What happened
What have tried to fix it
Click to expand...
Click to collapse
Root Status = ROOTED
I cannot boot into recovery mode (but when i try i get this, look in pic 2&3)
Tablet Type = HKC (NOT HTC) p776a
ANDROID Version I think (98% shure) is 4.1.1 beta JB
What happened = A few years ago 2013 i think a got this tablet then i learned about rooting, roms, and such so i spent the next year or two trying to root the tablet. I finally got it rooted with a chinese root program and all was well (i don't remember the name of the program) then there was a update for su and i pressed the twrp/cwm mode on accident (I think I was talking to someone at the time) and now it does what is shown in the image 1 it is on some boot loop. When I try to access the hboot menu it does what is shown in these images 2&3. Also my tablet has a MicroSD card slot and the battery can not be taken out. the regular bootloop picture is image file 1 that is what it looks like when it does its continuous bootloop and P.S. the tablet turns off and on automatically during the bootloop. To try and fix it i have let it do its bootloop for hours on end turn it on and off tried looking for a compatible rom (to no avail) and let the battery completely die that is about it.

parkourgamer said:
Root Status = ROOTED
I cannot boot into recovery mode (but when i try i get this, look in pic 2&3)
Tablet Type = HKC (NOT HTC) p776a
ANDROID Version I think (98% shure) is 4.1.1 beta JB
What happened = A few years ago 2013 i think a got this tablet then i learned about rooting, roms, and such so i spent the next year or two trying to root the tablet. I finally got it rooted with a chinese root program and all was well (i don't remember the name of the program) then there was a update for su and i pressed the twrp/cwm mode on accident (I think I was talking to someone at the time) and now it does what is shown in the image 1 it is on some boot loop. When I try to access the hboot menu it does what is shown in these images 2&3. Also my tablet has a MicroSD card slot and the battery can not be taken out. the regular bootloop picture is image file 1 that is what it looks like when it does its continuous bootloop and P.S. the tablet turns off and on automatically during the bootloop. To try and fix it i have let it do its bootloop for hours on end turn it on and off tried looking for a compatible rom (to no avail) and let the battery completely die that is about it.
Click to expand...
Click to collapse
Okay. Just a few more questions.
Does your tablet boot into recovery (picture 1) even if you try to boot normally? (fastboot maybe)
Can you boot into anything else other than recovery? (try different button combinations)
Does ADB recognise your tablet when it's in recovery mode? (if you don't know about this, just post your computer OS and if you have ADB/Fastboot drivers installed on your PC)
If the anwser the the first question is no:
Does ADB recognise the device while it's in the bootloop.

janekmuric said:
Okay. Just a few more questions.
Does your tablet boot into recovery (picture 1) even if you try to boot normally? (fastboot maybe)
Can you boot into anything else other than recovery? (try different button combinations)
Does ADB recognise your tablet when it's in recovery mode? (if you don't know about this, just post your computer OS and if you have ADB/Fastboot drivers installed on your PC)
If the anwser the the first question is no:
Does ADB recognise the device while it's in the bootloop.
Click to expand...
Click to collapse
sorry, i forgot to clarify the hboot. it pops up the "words" or whatever then automatically reboots there is no way to select options or keep the device on so i cant use fastboot unless there is a way i dont know of. P.S. the tablet restarts automatically so it is on for like 25 maybe 30 seconds then shuts off then turns back on and repeats till the battery is dead. My thought originally to fix it was to get a rom put it on the sdcard and see if that works but the manufacture does not supply the rom for my model only the p771a. and the only physical buttons are the home, power, the pinhole reset button, the volume and such buttons are virtual on the screen when it is fully on. And picture 1 i dont fully know what that screen symbol is the hboot one is similar but not that but yes it does but to picture 1 nomadder what i do even if i try to get to hboot menu. Sorry if this is a "little" scattered having explaining it. If it would help i can make a video and rar it and upload it here.

parkourgamer said:
sorry, i forgot to clarify the hboot. it pops up the "words" or whatever then automatically reboots there is no way to select options or keep the device on so i cant use fastboot unless there is a way i dont know of. P.S. the tablet restarts automatically so it is on for like 25 maybe 30 seconds then shuts off then turns back on and repeats till the battery is dead. My thought originally to fix it was to get a rom put it on the sdcard and see if that works but the manufacture does not supply the rom for my model only the p771a. and the only physical buttons are the home, power, the pinhole reset button, the volume and such buttons are virtual on the screen when it is fully on. And picture 1 i dont fully know what that screen symbol is the hboot one is similar but not that but yes it does but to picture 1 nomadder what i do even if i try to get to hboot menu. Sorry if this is a "little" scattered having explaining it. If it would help i can make a video and rar it and upload it here.
Click to expand...
Click to collapse
here is the video

parkourgamer said:
sorry, i forgot to clarify the hboot. it pops up the "words" or whatever then automatically reboots there is no way to select options or keep the device on so i cant use fastboot unless there is a way i dont know of. P.S. the tablet restarts automatically so it is on for like 25 maybe 30 seconds then shuts off then turns back on and repeats till the battery is dead. My thought originally to fix it was to get a rom put it on the sdcard and see if that works but the manufacture does not supply the rom for my model only the p771a. and the only physical buttons are the home, power, the pinhole reset button, the volume and such buttons are virtual on the screen when it is fully on. And picture 1 i dont fully know what that screen symbol is the hboot one is similar but not that but yes it does but to picture 1 nomadder what i do even if i try to get to hboot menu. Sorry if this is a "little" scattered having explaining it. If it would help i can make a video and rar it and upload it here.
Click to expand...
Click to collapse
1. Download fixcache.bat.zip on your computer. Extract cachefix.bat from the file.
2. Run it. It should say just "Waiting for device..."
3. Now reset your tablet with the reset button and QUICKLY plug it into the computer and wait a few minutes.
Now try to get to that text in picture 1 and tell me what happends.
Also post the text you see on the computer from the file I sent you.
Tell me if

janekmuric said:
1. Download fixcache.bat.zip on your computer. Extract cachefix.bat from the file.
2. Run it. It should say just "Waiting for device..."
3. Now reset your tablet with the reset button and QUICKLY plug it into the computer and wait a few minutes.
Now try to get to that text in picture 1 and tell me what happends.
Also post the text you see on the computer from the file I sent you.
Tell me if
Click to expand...
Click to collapse
this is what happens to the .bat fikle when i open it

parkourgamer said:
this is what happens to the .bat fikle when i open it
Click to expand...
Click to collapse
also would there be any way to pop the hood and flip a switch to reset it like on a pc tower?

parkourgamer said:
also would there be any way to pop the hood and flip a switch to reset it like on a pc tower?
Click to expand...
Click to collapse
Umm, you said there is a reset button on the tablet so pressing that would probably reset it.
The error you are getting is because adb is not installed on your PC. Use this simple adb installer to instal adb. When installing just press yes to everything. MAKE SURE THE PHONE IS PLUGGED IN THE COMPUTER WHILE INSTALLING AND THAT IT'S ON!
Now run the file again.
If you want you can add me on Skype: janekmuric
---------- Post added at 13:51 ---------- Previous post was at 13:26 ----------
If you want to know what is happening:
You are in what's called a recovery bootloop. It's when you can't get out of the recovery. What is happening in this case is that Superuser app tried to install it's binaries via recovery. Because some people don't know how to install binaries manually, the app puts a file on the cache partition so the recovery automaticly installs the zip upon booting. Now, this would be good so you don't mess up your device, but the zip file it's trying to install is faulty so it just breaks the device.
My attept at fixing this is to delete the /cache/recovery folder so it doesn't just install the file, and instead boots into a working recovery.

janekmuric said:
Umm, you said there is a reset button on the tablet so pressing that would probably reset it.
The error you are getting is because adb is not installed on your PC. Use this simple adb installer to instal adb. When installing just press yes to everything. MAKE SURE THE PHONE IS PLUGGED IN THE COMPUTER WHILE INSTALLING AND THAT IT'S ON!
Now run the file again.
If you want you can add me on Skype: janekmuric
---------- Post added at 13:51 ---------- Previous post was at 13:26 ----------
If you want to know what is happening:
You are in what's called a recovery bootloop. It's when you can't get out of the recovery. What is happening in this case is that Superuser app tried to install it's binaries via recovery. Because some people don't know how to install binaries manually, the app puts a file on the cache partition so the recovery automaticly installs the zip upon booting. Now, this would be good so you don't mess up your device, but the zip file it's trying to install is faulty so it just breaks the device.
My attept at fixing this is to delete the /cache/recovery folder so it doesn't just install the file, and instead boots into a working recovery.
Click to expand...
Click to collapse
That would be great but i cant keep my tablet on for more than like 30 seconds before it auto shuts off and it automatically tries to go into recovery when i add power to the device it wont just boot to the OS

parkourgamer said:
That would be great but i cant keep my tablet on for more than like 30 seconds before it auto shuts off and it automatically tries to go into recovery when i add power to the device it wont just boot to the OS
Click to expand...
Click to collapse
30 seconds is more than enough. Especally with an automated script like the one I sent you.
The first thing we have to do to fix your tablet is to establish a working ADB connection. Use the ADB installer i sent you. And look up on how to install Google USB driver for ADB.

janekmuric said:
30 seconds is more than enough. Especally with an automated script like the one I sent you.
The first thing we have to do to fix your tablet is to establish a working ADB connection. Use the ADB installer i sent you. And look up on how to install Google USB driver for ADB.
Click to expand...
Click to collapse
ok will try

Official Marshmallow 6.0 OTA for canadian xt1563 (telus, koodo, public mobile...)

Marshmallow OTA for canadian xt1563 : https://mega.nz/#!1pxWiSIS!u279kerhsu1HspzFZ4-wrzYfWgtSUqb3o8K8ffLw4lM
For the procedure, look down. Someone posted it on 1st page.
If you altered system ( ex:root) you'll need to go back to stock:
http://forum.xda-developers.com/showpost.php?p=62708260&postcount=5
Root (optional)
TWRP recovery (after applying the OTA) : http://forum.xda-developers.com/moto-x-play/orig-development/recovery-twrp-2-8-7-0-t3194656
The correct SuperSU: http://forum.xda-developers.com/showpost.php?p=64161125

The X Play is actually XT1563. This firmware is for the Moto G.
Update: the above statement is wrong. I can confirm this update is running perfectly on my Koodo X Play!

bngrybt said:
The X Play is actually XT1563. This firmware is for the Moto G.
Click to expand...
Click to collapse
Yeah, but the file listed on mega has lux_retca in its name. Moto X Play is codenamed as Lux, so maybe it is in fact the right file for XT1563? Maybe, it was just an error from poster MerlinMerlinMerlin?

Hmm... I have a Koodo X Play and just checked for the OTA and it wasn't available for me yet, but that has me wondering now. I don't wanna risk it until I'm sure though. Hopefully this means the OTA is out soon though.

Oops! I messed up the title.
Corrected the incorrect xt1053 by the correct xt1563

Just finished installing it through ADB sideload (I'm a Canadian Koodo user), I reinstalled the stock firmware before so that I could start on a fresh image. I had trouble getting into stock recovery at first. I was seeing a no command message when trying to enter it but, then I found the solution:
To get passed that point, you have to use the hold power + vol up button solution but, it's tricky, I had to try 3-4 times before getting it right. This part is kind of messed up, if you hold power button for too long, the phone interpret it as a reboot command. What worked best for me was holding vol up button alone for 5-6 seconds and then, I'd tap and release power button while still holding volume up button.
Click to expand...
Click to collapse
It worked perfectly...

How do you install it? Simply install it in recovery or do we need to install it by adb?

baskwo said:
How do you install it? Simply install it in recovery or do we need to install it by adb?
Click to expand...
Click to collapse
First, you need to have stock recovery, if you installed TWRP custom recovery, you will need to reinstall stock recovery. Entering stock recovery can be tricky, at first you may get an Android robot laying down with a "No command" message.
To get passed that point, you have to use the hold power + volume up button solution but, it's tricky, I had to try 3-4 times before getting it right. This part is kind of messed up, if you hold power button for too long, the phone interpret it as a reboot command. What worked best for me was holding vol up button alone for 5-6 seconds and then, I'd tap and release power button while still holding volume up button.
Edit: a user reported that this method work better (your mileage may vary)
Press and hold the Power Button for 2-5 seconds, while holding it, press and release the Volume Up button. You should now be seeing all the Recovery options.
Click to expand...
Click to collapse
Once you are booted in stock recovery mode, you can simply follow those steps:
Setup ADB and Fastboot on your PC.
Download the OTA update .zip file on your PC and rename it to ota.zip.
Enable USB debugging:
Go to your phone’s settings » About phone » and tap “Build number” Seven times. This will enable Developer options on your phone.
Now go to Settings » Developer options » and tick the USB debugging check box.
Connect your phone to PC.
Now open the folder where you downloaded the OTA update .zip file and then open a command window inside the folder. To do that, do a “Shift + Right click” on any empty white space inside the folder and select “Open command window here” from the context menu.
Now issue the following window to command window to reboot your device into recovery mode:
adb reboot recovery
└ Check your phone’s screen, if it asks for “Allow USB debugging”, accept it by selecting OK/Yes.
Once in recovery mode, use Volume buttons to navigate up and down between options and Power button to select an option.
Select the “Apply update from ADB” option.
Now issue the following command to finally begin installing the OTA:
adb sideload ota.zip
└ This will begin the OTA installation.
Once the OTA zip is installed, select reboot from the main menu of recovery.
Click to expand...
Click to collapse
Please take note that once Marshmallow is installed, nothing is stopping you from reinstalling TWRP and then, it will work as if nothing ever happened. If you need SuperSU, make sure to use SuperSU 2.62, earlier version may cause problem with Marshmallow. Also, if TWRP , ask if you want to install Root, click "Do not install" as it would install an older version of SuperSU. That's why you need to flash SuperSU 2.62 zipfile.

And if I want to keep TWRP?

Any chance someone could post a TWRP backup after installing the OTA?

baskwo said:
And if I want to keep TWRP?
Click to expand...
Click to collapse
You'll just have to reinstall TWRP after. No big deal, you can easily reinstall it afterward. That's what I did and TWRP is working perfectly as if nothing ever happened.

Nico3d3 said:
You'll just have to reinstall TWRP after. No big deal, you can easily reinstall it afterward.
Click to expand...
Click to collapse
Alright, thank you boy! <3 Where can I find the stock recovery?

baskwo said:
Alright, thank you boy! <3 Where can I find the stock recovery?
Click to expand...
Click to collapse
Just grab it from the original firmware zip file... : http://forum.xda-developers.com/moto-x-play/general/official-stock-firmwares-added-xt1562-t3195364

Nico3d3 said:
Just grab it from the original firmware zip file... : http://forum.xda-developers.com/moto-x-play/general/official-stock-firmwares-added-xt1562-t3195364
Click to expand...
Click to collapse
Does the XT1563_LUX_RETLA_DS_5.1.1_LPD23.118-32_cid12_subsidy-DEFAULT_CFC_v2.xml.zip file is ok if I'm from Koodo? Sorry I'm new to the Moto X Play I worked on a S3 before..

baskwo said:
Does the XT1563_LUX_RETLA_DS_5.1.1_LPD23.118-32_cid12_subsidy-DEFAULT_CFC_v2.xml.zip file is ok if I'm from Koodo? Sorry I'm new to the Moto X Play I worked on a S3 before..
Click to expand...
Click to collapse
Yes, it would work but, knowing how slow download from filefactory is, it would be probably take a looonnnggg time to download. That's why I uploaded the correct recovery.img file on my Google Drive, for the benefit of everyone: https://drive.google.com/file/d/0B-OWWP0oC4yLRDhsSDV0Mng3cVk/view?usp=sharing

Nico3d3 said:
Yes, it would work but, knowing how slow download from filefactory it would be probably take a looonnnggg time to download. That's why I uploaded the correct recovery.img file on my Google Drive, for the benefit of everyone: https://drive.google.com/file/d/0B-OWWP0oC4yLRDhsSDV0Mng3cVk/view?usp=sharing
Click to expand...
Click to collapse
Do you have a link the 5.1.1 fw?
I'd like to do a total fresh install then kick off the ota.

Anyone tested this on the xt1562?
Sent from my XT1562 using XDA Free mobile app

I misread last post, sorry about it, that's why I'm editing my post

Nico3d3 said:
Pleaaassseee, at least take the time to read a bit, no more than one page ago, you will have all informations regarding installation and how it worked.
Click to expand...
Click to collapse
There is nothing on that page about the xt1562, Just asking if anyone tested it on that device
Sent from my XT1562 using XDA Free mobile app

Nico3d3 said:
Pleaaassseee, at least take the time to read a bit, no more than one page ago, all informations regarding installation and how it worked are there.
Click to expand...
Click to collapse
Lol, you should read first before telling someone else
Sent from my Nexus 5 using Tapatalk