I have rooted my device without issue but now I would like to install CWM. I tried it once before but picked the Xoom rom before I knew there was a custom recovery for the transformer. When I try to go into recovery now, it does not work. I have read that adb reboot recovery does not work. I have also tried putting EP101_SDUPDATE.zip on an sdcard to flash but it won't work with the latest android update. Is there a way to flash it either through adb or console? I am familiar with the dangers of typing incorrect commands in linux (I use Arch Linux on my home PC) so any hard command to manually overwrite such files is cool with me.
Thank you for your help in advance.
just use RecoveryInstaller by Gnufabio
Sent from my Transformer TF101 using Tapatalk
That fixed my issue. Thank you very much! Now... if only I had an extra microsd card lying around.... hmmm...
Related
Hi folks,
Strange question I know, but...
I've ubuntu maverick on my Xoom(chroot), I need to patch the kernel and recompile it, and I prefer to need not to connect it to a pc just for this one stupid step. Instead i would like to be able to run fastboot flash boot blabla directly from my xoom shell or just remount a drive and put the new kernel there.
Thanks
GhostOfTheNet said:
Hi folks,
Strange question I know, but...
I've ubuntu maverick on my Xoom(chroot), I need to patch the kernel and recompile it, and I prefer to need not to connect it to a pc just for this one stupid step. Instead i would like to be able to run fastboot flash boot blabla directly from my xoom shell or just remount a drive and put the new kernel there.
Thanks
Click to expand...
Click to collapse
On the Evo, we use a binary called "flash_image" to flash recovery from a terminal emulator. However, i would be careful on trying to flash boot.img booted up. but if you're feeling brave, give it a shot and let me know how it goes
bigrushdog said:
On the Evo, we use a binary called "flash_image" to flash recovery from a terminal emulator. However, i would be careful on trying to flash boot.img booted up. but if you're feeling brave, give it a shot and let me know how it goes
Click to expand...
Click to collapse
There's a separate binary called tegra_flash_image. It works on my gtab for flashing recovery.
Ok thanks, i'll try. When i do a failure, i can reflash with a clean boot.img from pc so there should be no problem. I'll tell you what happened, but i need to wait until the tiamat kernel sources are updated. Maybe in the evening.
Sent from my Xoom using XDA App
I was able to root the latest update 9.2.1.21 without downgrading I used wolfs method 3 http://forum.xda-developers.com/showthread.php?t=1622628 to install cwm using cwm recoveryblob then i downloaded wolf su+superuser.apk from the OP and flashed it on using cwm now ihave a rooted 9.2.1.21 without downgrading
NB i used a different recoveryblob than what wolf posted i used the one that usually get place on sdcard when i had installed cwm using gnufabio recoveryinstaller.apk on previous firmware but u could use the one in wolf post it cwm based
what are the commands to enter adb, I have installed the sdk manager and update the usb tablet, but I can not, please help
Sent from my Transformer TF101 using xda premium
max_105 said:
what are the commands to enter adb, I have installed the sdk manager and update the usb tablet, but I can not, please help
Sent from my Transformer TF101 using xda premium
Click to expand...
Click to collapse
In sdk manager select android platform tools and asus drivers and install them once thats done open command prompt and go to the directory containing adb for me it was c:/android-sdk/platform-tools
Ensure debbuging mode and asus sync are turned on on your tf101 plug it up and the run the command
adb devices
this will tell if adb sees your device. If it does then run the command
adb shell
then just follow rest of instructions under method 3 in wolf post http://forum.xda-developers.com/showthread.php?t=1622628
jays473 said:
I was able to root the latest update 9.2.1.21 without downgrading I used wolfs method 3 http://forum.xda-developers.com/showthread.php?t=1622628 to install cwm using cwm recoveryblob then i downloaded wolf su+superuser.apk from the OP and flashed it on using cwm now ihave a rooted 9.2.1.21 without downgrading
NB i used a different recoveryblob than what wolf posted i used the one that usually get place on sdcard when i had installed cwm using gnufabio recoveryinstaller.apk on previous firmware but u could use the one in wolf post it cwm based
Click to expand...
Click to collapse
I just tried this after installing the new 9.2.1.24 (downloaded from Asus), and it seems to work. I followed Wolf's method 3 without any modifications. I have a TF101, US model.
nikolam said:
I just tried this after installing the new 9.2.1.24 (downloaded from Asus), and it seems to work. I followed Wolf's method 3 without any modifications. I have a TF101, US model.
Click to expand...
Click to collapse
What BLOB file did you use
well yes, through CWM one can install su-binary then.
but through CWM you will loose OTA-updates!
just look at the time between .21 and now .24... it is quite comfortable as it is.
why can't we use such a "file linking trick" to mount /system and install su-bin directly?
You can't write to /system as it's mounted read only.
What you can do is keep a copy of mmcblk0p4 before writing the new recovery, then flash it back after rooting. That way you keep your ability to upgrade next time around.
good idea!
I'm still a bit unsure about this RECOVERYBLOB flashing,
but if nothing else comes up I can resort to this.
ty
Hi. I'm not new to android or custom roms, but am new to the a500. I got mine used with stock hc 3.2.1, which I discovered is not rootable (score one for rule #1). Do I downgraded to hc 3.0 via an update.zip and rooted via iconia root app.
ARI doesn't work because I have no recovery. It only shows bootloader 3.01 for recovery and won't install any other recovery.
I also cannot get into adb. I've installed drivers on my Windows 8 pc and also the adb tool. It won't find the a500. I see it in My computer as a flash drive, but the adb utility won't find the device.
So I can't get a new recovery on it.
I would like to eventually put cm10 on it.
Can I get an update.zip of ics with bl8?
Any ideas?
Sent from here
Anyone? Bueller?
ADB is installed properly on my pc, but reports an error #10 and says it cannot connect.
I've tried easy ADB from the play store, but can't get the PC to connect to the tablet.
Blackthund3r a500 manager will not see the tablet no matter what I try.
I'm on windows8 64bit.
Tablet is a500 downgraded to 3.0 and rooted .then OTA to 3.1. Rooted with busybox, verified with root checker.
I've tried various USB ports and cables.
I really want to update the bootloader so I can start flashing.
Any help would be appreciated.
Sent from here
Got access to a machine that's running something other than win8? That or Ubuntu is your only option
Sent from my GT-I9300 using Tapatalk 4 Beta
Odd. This morning I tried Acer recovery installer again and it worked! I guess prayer helps!
Running lightspeed ics now.
Sent from my SAMSUNG-SGH-I727 using XDA
So i have an A500 i rooted awhile ago.
It runs android 4.1.2
CM10
cwm bootloader 5.5.0 x thor2002ro rev 1.7
i think i installed it from cm10-flex_v6Supercharged_rev2.3_gappsIncl_public....
now i'm thinking about upgrading to android 4.4, as there seems to be one out for A500.
of course it says i need to upgrade my CWM to 6.0.4.5...
this file of course says i need to install Skrilax bootloader.
And skrilax says i need nvflash to install it.
so considering what i currently have installed, is this the correct and easiest way to go about installing a new rom`?
(i keep getting dizzy every time i try upgrading my tablet, because all these guides are soooo confusing, always referring to something that's not explained in the guides.)
well made it as far as getting the skrilex loader installed..
now i'm trying to fastboot in, and it returns
? fastboot
googling it haven't found any idea as to what is wrong
took a leap of faith.. the ? still allowed it to work..
duckforceone said:
took a leap of faith.. the ? still allowed it to work..
Click to expand...
Click to collapse
The ? means you have a connection between your pc and tab.
You are able to issue fastboot commands from yr pc. If you have a recovery.img file you can ' fastboot flash '.
The other way to flash a custom recovery is to use a 'flashable zip'. You could have used this method, by copying the zip to yr sdcard and booting to your cwm RECOVERY and using the flash zip option in the menu.
No matter tho, u sussed it out yrself, sweet
dibb
Sent from my HTC_PN071 using Tapatalk
Hi I'm looking for the recovery of the stock LG G PAD tablet 7 "LTE I am root backup with TWRP but I can not go back to Recovery Stock.
Before flashing the TWRP I forgot to make a backup of Recovery
Sorry for my bad English.
thanks
exebuera said:
Hi I'm looking for the recovery of the stock LG G PAD tablet 7 "LTE I am root backup with TWRP but I can not go back to Recovery Stock.
Before flashing the TWRP I forgot to make a back of Recovery
Sorry for my bad English.
thanks
Click to expand...
Click to collapse
here's a link to an image I made before flashing twrp on my v410. I've restored it with dd and flashify and it works fine. https://docs.google.com/file/d/0B1l3W9XHAqEgX0ZCUWc1QTlfWjg/edit?usp=docslist_api
jason2678 said:
here's a link to an image I made before flashing twrp on my v410. I've restored it with dd and flashify and it works fine. https://docs.google.com/file/d/0B1l3W9XHAqEgX0ZCUWc1QTlfWjg/edit?usp=docslist_api
Click to expand...
Click to collapse
hey @jason2678 thanks, but how did i flash this if i dont have twrp installed? can i use fastboot or adb?
dreamtheater17 said:
hey @jason2678 thanks, but how did i flash this if i dont have twrp installed? can i use fastboot or adb?
Click to expand...
Click to collapse
I'd recommend flashify to flash recovery images. You can download it from the play store. So easy to make a typo and mess things up with adb and dd.
You could do it with a terminal or adb shell. Say you store the image in /sdcard
Code:
su
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p14
Verify mmcblk0p14 is recovery before you try this. I'm pretty sure that's right, but I don't have my tablet right now and you can make a serious mess of your device this way if you overwrite the wrong partition. Check it by listing your partitions with this:
Code:
su
ls -al /dev/block/platform/*/by-name
By default this little tablet does not have fastboot, but you can enable it with this method. I've zeroed out my laf partition and verified I can boot into fastboot mode, but I've never actually used it to flash anything. It just seemed like a good idea to have fastboot available to fall back on rather than LG download mode since there was no kdz available for the V410 for a long time.
jason2678 said:
I'd recommend flashify to flash recovery images. You can download it from the play store. So easy to make a typo and mess things up with adb and dd.
You could do it with a terminal or adb shell. Say you store the image in /sdcard
Code:
su
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p14
Verify mmcblk0p14 is recovery before you try this. I'm pretty sure that's right, but I don't have my tablet right now and you can make a serious mess of your device this way if you overwrite the wrong partition. Check it by listing your partitions with this:
Code:
su
ls -al /dev/block/platform/*/by-name
By default this little tablet does not have fastboot, but you can enable it with this method. I've zeroed out my laf partition and verified I can boot into fastboot mode, but I've never actually used it to flash anything. It just seemed like a good idea to have fastboot available to fall back on rather than LG download mode since there was no kdz available for the V410 for a long time.
Click to expand...
Click to collapse
Thank you! the thing is i bricked my g pad, i really dont know much about the tab because the lack of support it has. I was using it with cm12.1 and i use a stock recovery founded in Android central to revert back to stock, but in TWRP i flashed the img as recovery and also as boot, so the g pad entered in a bootloop were only enters in stock recovery, my Windows 10 laptop doesn't recognize the tab when in adb sideload, and doesn't know much about adb Shell, i'm following the comandas you wrote but i'm always getting error: closed.
i know how to get back to stock using the kdz, but using the kdz will make the partition issue and will have to folllow a looong looong process.
If you could give me a hand with this i would really apprecciate it
Sorry I've never encountered the adb closed problem myself, but I have heard about it before. Some people have reported the following series of commands fixes it:
Code:
adb usb
adb devices
adb kill-server
adb start-server
The first two commands normally don't really do anything and its pretty obvious what the second two do, but some people have reported success doing this.
Some people have reported the closed error was fixed by updating their adb binary. If you're using the android-sdk update platform-tools, or if you're using a standalone adb consider looking for an update for it.
Good luck. That procedure to get things back to normal following using the kdz to restore sounds messy.
dreamtheater17 said:
Thank you! the thing is i bricked my g pad, i really dont know much about the tab because the lack of support it has. I was using it with cm12.1 and i use a stock recovery founded in Android central to revert back to stock, but in TWRP i flashed the img as recovery and also as boot, so the g pad entered in a bootloop were only enters in stock recovery, my Windows 10 laptop doesn't recognize the tab when in adb sideload, and doesn't know much about adb Shell, i'm following the comandas you wrote but i'm always getting error: closed.
i know how to get back to stock using the kdz, but using the kdz will make the partition issue and will have to folllow a looong looong process.
If you could give me a hand with this i would really apprecciate it
Click to expand...
Click to collapse
hi, i have the same problem than u, i wanna know if i can flash the US CELLULAR kdz for solve the partition issue? because i already flash the kdz test from ATT
jason2678 said:
here's a link to an image I made before flashing twrp on my v410. I've restored it with dd and flashify and it works fine. https://docs.google.com/file/d/0B1l3W9XHAqEgX0ZCUWc1QTlfWjg/edit?usp=docslist_api
Click to expand...
Click to collapse
I flashed stock rooted 4.4.2, and I want to OTA to Stock Lollipop, but it says there is no update. Any ideas of how I can get back to fully stock? Would flashing this stock recovery make it work? Is being rooted blocking the OTA update from seeing an available update?
mxpxboi said:
I flashed stock rooted 4.4.2, and I want to OTA to Stock Lollipop, but it says there is no update. Any ideas of how I can get back to fully stock? Would flashing this stock recovery make it work? Is being rooted blocking the OTA update from seeing an available update?
Click to expand...
Click to collapse
If you applied an OTA with a custom recovery installed it might soft brick your tablet, but I don't see why that would stop it from detecting and downloading the update. It is always safest to flash stock recovery, fully unroot, and undo any modifications you've made to /system before taking an OTA, but some devices are more picky than others. With what you're describing I'm afraid that even if you do unroot and flash stock recovery your tablet still won't find the OTA.
Do you have a nandroid backup of an unmodified stock ROM you could restore?
And just so you know that lollipop bootloader is not vulnerable to the bump exploit, so no custom recovery or ROMs if you get it to apply.
Whenever I type "reboot recovery" in terminal emulator, it boots straight to factory reset. I have tried this multiple times with both dd and flashify. Do you know what causes this? I'm downloading the OTA right now, I hope it doesn't wipe then too...
please help
i was a dumbass and accidently flashed my boot instead of recovery do you by chance have a boot.img that i can use to reflash my boot.img please help as im really stuck..thanks in advance
Devil911 said:
i was a dumbass and accidently flashed my boot instead of recovery do you by chance have a boot.img that i can use to reflash my boot.img please help as im really stuck..thanks in advance
Click to expand...
Click to collapse
Download the timmytim stock ROM, and extract the boot.img from it. There are probably quicker ways, but having the stock ROM on hand is a good idea.
Sent from my Amazon Fire using XDA Labs
Thank you...
I resolved my issue i had forgotten in my haste i posted the same question in two different sections. However after fixing everything my tablet was broke not the out glass but the inner display. I cant afford another one or a replacement part to even fix mine. So unless i can find one someone who bricked theirs completely or get a handme down im tabless for awhile.... Thank you though for the reply. The original boot file wouldnt work properly i had to use the boot file from the stock rooted rom and not the timmytim deoxedized rom.. i dont know why unless the bootfile is specific to each rom. Maybe i did something wromg during the flash. But i had gotten it fixed nevertheless.
Devil911 said:
I resolved my issue i had forgotten in my haste i posted the same question in two different sections. However after fixing everything my tablet was broke not the out glass but the inner display. I cant afford another one or a replacement part to even fix mine. So unless i can find one someone who bricked theirs completely or get a handme down im tabless for awhile.... Thank you though for the reply. The original boot file wouldnt work properly i had to use the boot file from the stock rooted rom and not the timmytim deoxedized rom.. i dont know why unless the bootfile is specific to each rom. Maybe i did something wromg during the flash. But i had gotten it fixed nevertheless.
Click to expand...
Click to collapse
The stock rooted is by timmytim ?
I forgot about deodexed, actually.
Glad you fixed boot, shame your tablet broke ?
Sent from my Amazon Fire using XDA Labs