Related
I have my rooted transformer and am trying to update but stow a quarter way throught the install and gives me an android Guy with a triangle with a "!" Sign in it... stock everything just rooted please help
Sent from my GT-I9000 using XDA Premium App
Fixed!!!!! I used Brks Asus transformer rootkit script to root which installs an insecure bootimage to work and this is what caused the problem, I just plugged my trandormer in and restored my original files then the update went on fine first try!!!! Thanks for the help!!!!
Did you install Clemsyn/Blades OC kernel? More than likely this is causing your problem.......
I'm getting the same error. Running 3.2 stock but rooted, no modified kernel. Only thing I modified was the Netflix patch which doesn't seem like it's needed now. Is there a flash able zip for this new update?
You can't update the normal way after rooting.
Sent from my Transformer TF101 using XDA Premium App
magicdave26 said:
You can't update the normal way after rooting.
Sent from my Transformer TF101 using XDA Premium App
Click to expand...
Click to collapse
Actually, thats not true. I was running on stock 8.6.5.6 rooted, and was able to update sucessfully. I verified the update in the settings. I have also verified with root checker that i am no longer rooted, as i was before the update. I bought my transformer only a few weeks ago. It came with 3.1 and i updated to 3.2 before rooting. Wonder if that or the rooting method has something to do with why i was able to update while rooted.
I rooted using the method in this thread:
http://forum.xda-developers.com/showthread.php?t=1125714
oilerseberle14 said:
I have my rooted transformer and am trying to update but stow a quarter way throught the install and gives me an android Guy with a triangle with a "!" Sign in it... stock everything just rooted please help
Sent from my GT-I9000 using XDA Premium App
Click to expand...
Click to collapse
Same happened to me. As I understand it just rooting doesn't prevent future OTA updates, hence why I was prompted to download this latest, but why it now after failing it tells me there is no longer an update available is beyond me. I can only think ASUS has pulled it for some reason.
---
Sent from my Asus Transformer using Tapatalk
Taomyn said:
Same happened to me. As I understand it just rooting doesn't prevent future OTA updates, hence why I was prompted to download this latest, but why it now after failing it tells me there is no longer an update available is beyond me. I can only think ASUS has pulled it for some reason.
Click to expand...
Click to collapse
You only get it offered the once. Your device is then marked as updated at Asus end. If it didn't work because you were rooted, then tough...
cavsoldier19d said:
Actually, thats not true. I was running on stock 8.6.5.6 rooted, and was able to update sucessfully. I verified the update in the settings. I have also verified with root checker that i am no longer rooted, as i was before the update. I bought my transformer only a few weeks ago. It came with 3.1 and i updated to 3.2 before rooting. Wonder if that or the rooting method has something to do with why i was able to update while rooted.
Click to expand...
Click to collapse
Hmm interesting.
Which method did you use to root it?
Maybe we can pin point why the updates are failing for some people after rooting. I would like to root mine if it was 100% that the OTA updates would still work, even if I had to root it again after each one.
magicdave26 said:
Hmm interesting.
Which method did you use to root it?
Maybe we can pin point why the updates are failing for some people after rooting. I would like to root mine if it was 100% that the OTA updates would still work, even if I had to root it again after each one.
Click to expand...
Click to collapse
I'm having problems with OTA updates and have used Brk's ASUS Transformer HC3.2 RootKit Script to root my device.
I probably did something very stupid...in which I factory reset the device, but noticed that "superuser" is still installed in the apps list. I'm wondering now if i have to re root the device to uninstall superuser and then do another factory reset and then see if the OTA update works? suggestions appreciated
I always look at the updater script in the package before I update. This script contains a bunch of asserts that check the integrity of certain files before it will apply the update. If you can get the update package just open " \META-INF\com\google\android\updater-script" with notepad and that will show everything that's happening when the update occurs including the file asserts it makes. If you've modified these files then it will not update. 8.6.5.6 initially didn't work for me but by checking the script I found the problem was my srs_processing.cfg file because I tried to fix my speaker balance and this was a file that the script asserted. After restoring the original file I was able to update with stock recovery even though I had modified other system files. As long as the specific files the update checks are ok the update will proceed.
aSIMULAtor said:
I'm having problems with OTA updates and have used Brk's ASUS Transformer HC3.2 RootKit Script to root my device.
I probably did something very stupid...in which I factory reset the device, but noticed that "superuser" is still installed in the apps list. I'm wondering now if i have to re root the device to uninstall superuser and then do another factory reset and then see if the OTA update works? suggestions appreciated
Click to expand...
Click to collapse
You need to UnRoot it, I don't think factory reset makes any difference to rooting
http://forum.xda-developers.com/showthread.php?t=1198303
magicdave26 said:
Hmm interesting.
Which method did you use to root it?
Maybe we can pin point why the updates are failing for some people after rooting. I would like to root mine if it was 100% that the OTA updates would still work, even if I had to root it again after each one.
Click to expand...
Click to collapse
The above post about altering certain files appears it might have something to do with it. I rooted using this method... http://forum.xda-developers.com/showthread.php?t=1198303
But it was V2 when i used it. It is now currently V4.
You can re-download the update if you clear your DMClient cache.
Follow the instructions in this thread.
http://forum.xda-developers.com/archive/index.php/t-1106054.html
I had the error with the Android + exclamation mark so I unrooted (reflashed both the stock ROM AND the stock recovery - to get rid of clockworkmod) then cleared the DMClient cache and was I able to update OTA.
As far as I am aware the OTA will not install if you have clockwork Mod flashed for recovery. But if you have rooted without flashing over stock recovery ie clockwork mod not installed the OTA should work but you will lose root by updating.
DT39 said:
As far as I am aware the OTA will not install if you have clockwork Mod flashed for recovery. But if you have rooted without flashing over stock recovery ie clockwork mod not installed the OTA should work but you will lose root by updating.
Click to expand...
Click to collapse
Good point. I did not have clockwork mod recovery installed. Had stock recovery, stock ROM rooted.
Sent from my Inspire 4G using XDA App
I used brk's rootkit script and just restored the original bootimage and it installed perfect let me know if it worked for you guys as well
Sent from my Transformer TF101 using XDA Premium App
I tried flashing back original boot and recovery image, update still failed, and now it fota won't come back. Cleared DMClient cache and hard reset. Guess I'm out of luck until someone releases a flashable version of the update?
Hizpanick said:
I tried flashing back original boot and recovery image, update still failed, and now it fota won't come back. Cleared DMClient cache and hard reset. Guess I'm out of luck until someone releases a flashable version of the update?
Click to expand...
Click to collapse
Same thing happened to me. Tried all the above, and can't get the update to come back.
Have any of you changed original system files whilst rooted? That's why it was failing for me. I managed to get the update again but it failed. I got it once more after it rebooted but took a copy first, unrooting made no difference. Unlike the downloadable firmwares from the ftp site which I checked out, the update script checks the integrity of a ton of files mainly the system apps that cannot be changed without root. If any have changed the script aborts.
Unfortunately even though I had backed up all of them with Titanium Backup, it wouldn't restore them and TB just hung. I tried all its options but nothing helped - a little worrying.
In the end I copied off the TB backup directory to a USB stick and used the NVflash recovery to restore back to factory. I then performed the upgrade again to both the tablet and dock without issues. Four hours later I have it almost back to where I want it.
Hope this helps some of you, even though it's not the best process, but the update imho is worth it
---
Sent from my Asus Transformer using Tapatalk
my A500 has been rooted, but can not upgrapde to 3.2 via OTA everytime it reboot.
Help pls
thx
Yea, i'm also unable to receive the 3.2 OTA. I'm not rooted however, so I dont think thats the problem. Sometime it will finish the download but then say the file is corrupted and starts back at square one....
Sent from my A500 using xda premium
To the OP, you basically have to unroot it to update via to OTA file. Specifically, you cannot update with the OTA file using the non-stock Recovery system.
Ashy: Are you downloading it over wifi or 3g? If 3g, try downloading it via wifi...
I'm also having issues updating. I get past the download, the reboot to recovery, but the install fails with the bee/exclamation screen.
I've read recently to put the tablet in portrait orientation when installing and will try that tonight.
I remember that worked in the past for me.
Sent from my GT-I9100M using Tapatalk
Groaner, are you rooted? And if so, did you install the stock recovery back on it before trying to update?
Yes. I've tried every version of.com roms but none of them let me. I have not tried the.07 one so maybes that will be next.
Portrait orientation did not help unfortunatly.
I'm currently trying Taboonay 2.1 first.
Sent from my GT-I9100M using Tapatalk
I don't think it was really the ROM being used that matter, but that you should have the stock/factory recovery installed. I had to completely unroot my device before I could update from the OTA download.
LindtSH said:
my A500 has been rooted, but can not upgrapde to 3.2 via OTA everytime it reboot.
Help pls
thx
Click to expand...
Click to collapse
If you are rooted anyway, I wouldn't suggest the OTA update. You will lose root and if you need it then this isn't the best way to do it. What you should do is install the acer recovery from the market, use that to install CWM (if you don't have it already) and then download the ZIP of an already rooted 3.2 and install that.
View attachment 923053so here's my story;
i rooted my transformer a while back and was messin around with nvflash and got it semi-bricked, so i flashed the nvflash stock rom and it saved my ass. so i stayed on stock unrooted for a while (it's been about a month), but i was on a previous firmware, i think 8.5.6.19, so i headed over to asus's download website, got the .21 firmware and updated my tab to that about a week ago.. so im on 8.6.5.21, US sku tf101 (NOT tf101g). Any thoughts to why i haven't recieved a notification to update to ICS? i rebooted, fully discharged and recharged, and checked the forums... plus Ive been mashing the "check update" button for two days now....... -_- if anyone has a non-root solution, it would be greatly appreciated. Thanks in advance!
View attachment 923053
Sent from my Transformer TF101 using xda premium
There is a prerooted version of ice available in the Dev subforum. I used that to upgrade.
Sent from my NookColor using Tapatalk
jerrykur said:
There is a prerooted version of ice available in the Dev subforum. I used that to upgrade.
Thanks for the reply!
Did that require clockworkmod? Cause i'm on the stock rom with stock recovery...
Sent from my Transformer TF101 using xda premium
Click to expand...
Click to collapse
Do you have CWM Recovery (or non-stock recovery) installed? This will block OTA updates.
Beyond that, try going to Settings - Apps - Manage - All - DMClient - Force Close then Clear Data. Repeat for CMClient.
Reboot.
Check for updates.
frederuco said:
Do you have CWM Recovery (or non-stock recovery) installed? This will block OTA updates.
Beyond that, try going to Settings - Apps - Manage - All - DMClient - Force Close then Clear Data. Repeat for CMClient.
Reboot.
Check for updates.
Click to expand...
Click to collapse
I'm on completely stock rom, and the recovery is stock as well (i used it to install the update from asus's website.)
I tried your suggestion about clearing Dmclient and Cmclient data after they were force closed. after i rebooted, i waited about 30 seconds then went to check for update and im still getting the "there is no update available for your device currently" message
Anything else i should try?
Sent from my Transformer TF101 using xda premium
Since you can NVflash, suggest you root your device and nvflash CWM. Then install the ICS update floating around through CWM.
zook79 said:
I'm on completely stock rom, and the recovery is stock as well (i used it to install the update from asus's website.)
I tried your suggestion about clearing Dmclient and Cmclient data after they were force closed. after i rebooted, i waited about 30 seconds then went to check for update and im still getting the "there is no update available for your device currently" message
Anything else i should try?
Sent from my Transformer TF101 using xda premium
Click to expand...
Click to collapse
You need to do a cold reboot instead of just reboot. You also need to delete the cache for dmclient and cmclient, not just data.
Force stop DMClient, Clear data, Clear cache
Force stop CMClient, Clear data, Clear cache
COLD REBOOT. You do this by powering off your TF(also unplug your power/usb cable) and then starting it up by holding down [volume down] and [power] together. Keep the buttons pressed for at least 6 seconds. Then you will see 2 icons in the center of screen. The right icon is cold reboot and is selected by default. Wait 10 seconds and it will start cold boot automatically.
Check for update.
I think someone mentioned on the forum that ASUS pulled out ICS from the servers - until reboot issue is fixed.
irekz said:
I think someone mentioned on the forum that ASUS pulled out ICS from the servers - until reboot issue is fixed.
Click to expand...
Click to collapse
Stop spreading misinformation.
horndroid said:
Stop spreading misinformation.
Click to expand...
Click to collapse
Only logical to try to stop bugs from spreading further if you're aware of your mistakes???
Thiesen said:
Only logical to try to stop bugs from spreading further if you're aware of your mistakes???
Click to expand...
Click to collapse
The issue isn't whether or not it's "logical," the issue is whether or not it's true. Which it's not.
I have the same problem, .. not OTA ICS love
stock of course
interestingly enough, 2 of my friends got it yesterday, .. but when i tried today, "no update available"
I tried the following
- Cold boot
- C and D clients force close and clear cache + cold boot
- Factory Reset
nothing worked, .. it is as if there is no update what so ever.
guess will have to wait and see, no rush.
if anyone have some suggestions though, throw em at me
cheers
Well no offense but there is a quick and easy method and thats to NVFlash CWM and manually flash it... or sit and wait your turn.
I don't know why people are so afraid to have a "rooted" device. All it does it gives you admin rights to perform tasks typically not allowed to the stock user account. It's like logging on as Administrator to your Windows machine.
The ICS OTA flashable rom running around IS COMPLETELY STOCK with the exception that the user account has admin rights (ie "rooted").
The only MAIN reason to stay completely stock is to get OTA updates first... but as you see this isn't the case. The OTA may not even be available for your area yet. Custom roms only DISABLE the OTA check because it can unroot your phone and cause incompatibilities.
ClockWorkMod also is just a custom recovery which allows for full backup/restoration of your system. CWM is worth nvflashing JUST for that reason alone.
Triplanetary said:
The issue isn't whether or not it's "logical," the issue is whether or not it's true. Which it's not.
Click to expand...
Click to collapse
Maybe its just a rumor, cant verify this, but here is the source:
http://forum.xda-developers.com/showpost.php?p=23024840&postcount=26
i had wiped everything for both clients and had already tried a coldboot and factory reset (from recovery) and still no update.
Of course the easy route would be to root, as i did before, but im actually just wondering why i haven't recieved the update at all... if it isnt resolved in the next 24 hours, ill just root and flash the stock rooted firmware. thanks for the help guys!
Sent from my Transformer TF101 using xda premium.
so i called asus and they said some of the tablets wouldnt get the update yet but that it was definitely on the way. he said that i should wait at least a week...
another thing, he said nothing about asus pulling the update from the server, and was pretty clear that the update was being sent out to the tablets, some were just slower to receive the update
Sent from my Galaxy Nexus using xda premium
Well, in my case i NEVER succeeded to get OTA upgrading, and it is knowing problem in my country (Israel).
You can download the 4.0.3 ICS update from ASUS now...
I just downloaded the .21 update......it did nothing for allowing me to OTA update to ICS. Went back to ASUS and they now had the new ICS update to download. Downloaded and installed.
irekz said:
Maybe its just a rumor, cant verify this, but here is the source:
http://forum.xda-developers.com/showpost.php?p=23024840&postcount=26
Click to expand...
Click to collapse
Well. Well. Well. This is exactly what i read and was referring to yesterday.
tcrews said:
You can download the 4.0.3 ICS update from ASUS now...
I just downloaded the .21 update......it did nothing for allowing me to OTA update to ICS. Went back to ASUS and they now had the new ICS update to download. Downloaded and installed.
Click to expand...
Click to collapse
thanks....
Hello,
Trying to root my TF300TG with the "1-Click Transformer Root" failed and my fastboot/recovery is damaged.
Trying to boot with vol-down and power key ends with a android lying on the back
Trying to root my pad with this http://forum.xda-developers.com/showthread.php?t=1706588 worked perfectly.
So I have root, but no recovery.
Is there a way to bring them back?
Thanks
Chris
blackynet said:
Hello,
Trying to root my TF300TG with the "1-Click Transformer Root" failed and my fastboot/recovery is damaged.
Trying to boot with vol-down and power key ends with a android lying on the back
Trying to root my pad with this http://forum.xda-developers.com/showthread.php?t=1706588 worked perfectly.
So I have root, but no recovery.
Is there a way to bring them back?
Thanks
Chris
Click to expand...
Click to collapse
Unfortunately I don't know how to get back your recovery.
But I thank you for warning about "1-Click Transformer Root" in combination with the .40 firmware.
I can confirm, that rooting my TF300TG with .40 firmware using http://forum.xda-developers.com/showthread.php?t=1706588 works without problems.
Edit: I tried to get into the (stock) recovery and I can't get into it, too. Instead I get the lying robot with the warning sign. Seems that something during the rooting process kills the recovery.
I want to root mine, but do any of you know to get back the recovery or any recovery at all?
I also want to know if you do the root before the .40 update will you have recovery after?
Thank you big
slide200sx said:
I want to root mine, but do any of you know to get back the recovery or any recovery at all?
I also want to know if you do the root before the .40 update will you have recovery after?
Thank you big
Click to expand...
Click to collapse
I root after the .40 update and no I have not found a way to fix my recovery for now.
I first use a tool that did root and flash a new recovery. But I did not get root and my recovery was broken.
The debugfs tool did only root your pad, so I think there will nothing happend with your recovery.
regards
Sent from my ASUS Transformer Pad TF300TG using XDA Premium HD app
Your recovery is fine. Nothing has changed unless you rooted successfully. Your recovery has not been touched yet to my knowledge. Does your tab boot to the operating system? If so you are fine.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
---------- Post added at 02:48 AM ---------- Previous post was at 02:47 AM ----------
I think you can only flash the new recovery AFTER you unlock the boot loader.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
I don't know but can't you just flash a recovery.img or recovery.blob via fastboot? or is an unlocked bootloader needed for this?
(I did this and it worked, will also work for you if your PC still recognises the fastboot device...again, I'm unsure whether unlocked bootloader is needed)
I unlocked bootloader and then used adb to push the cwm recovery, then used the root zip
worked for me, i had just got mine and feeling bad that the update just downloaded and wanted to install .40 all it all time but after i did it was still good....plus i had to learn adb to do it as the commands given had been wrong and didnt work,,,lol
blackynet said:
Hello,
Trying to root my TF300TG with the "1-Click Transformer Root" failed and my fastboot/recovery is damaged.
Trying to boot with vol-down and power key ends with a android lying on the back
Trying to root my pad with this http://forum.xda-developers.com/showthread.php?t=1706588 worked perfectly.
So I have root, but no recovery.
Is there a way to bring them back?
Thanks
Chris
Click to expand...
Click to collapse
For my case rooting worked with the one clock tool ???
blackynet said:
Hello,
Trying to root my TF300TG with the "1-Click Transformer Root" failed and my fastboot/recovery is damaged.
Trying to boot with vol-down and power key ends with a android lying on the back
Trying to root my pad with this http://forum.xda-developers.com/showthread.php?t=1706588 worked perfectly.
So I have root, but no recovery.
Is there a way to bring them back?
Thanks
Chris
Click to expand...
Click to collapse
Hello ...
First, sorry for my bad english, I'm from Germany and use the google translator
Similar with me...
I rooted my TF300TG with the '1-Click Transformer root '.
It worked and I have root. However, I have now tried to boot into recovery I get after a while the lying Android.
My firmware version is ww_9.4.4.40
The tablet is working properly, I only have no recovery. Do I get now no more OTA updates? How can I fix the Recovery?
Who can help?
Regards, Wolf
Wolf Hamburg said:
Hello ...
First, sorry for my bad english, I'm from Germany and use the google translator
Similar with me...
I rooted my TF300TG with the '1-Click Transformer root '.
It worked and I have root. However, I have now tried to boot into recovery I get after a while the lying Android.
My firmware version is ww_9.4.4.40
The tablet is working properly, I only have no recovery. Do I get now no more OTA updates? How can I fix the Recovery?
Who can help?
Regards, Wolf
Click to expand...
Click to collapse
Are you saying you had recovery before? That version number is stock, so either you unlocked the bootloader previously and loaded recovery then lost it, or you never had it. In any case, to get it, you must unlock the bootloader to do it.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
funnel71 said:
Are you saying you had recovery before? That version number is stock, so either you unlocked the bootloader previously and loaded recovery then lost it, or you never had it. In any case, to get it, you must unlock the bootloader to do it.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
Click to expand...
Click to collapse
yes, i know... the 9.4.4.40 is stock ics.
i never tries before i have rooted to boot in recovery. i thought each version, if stock or custom, has a recovery?
my bootloader is locked end i never flashed e recovery.
so it is normal that the stock 9.4.4.40 ics has no recovery? but when i boot with power/volume down and then volume up, the tf300tg tries to boot in recovery and after a little while the android lay down... ist this normal behavior for the stock 9.4.4.40 ?
Wolf Hamburg said:
yes, i know... the 9.4.4.40 is stock ics.
i never tries before i have rooted to boot in recovery. i thought each version, if stock or custom, has a recovery?
my bootloader is locked end i never flashed e recovery.
so it is normal that the stock 9.4.4.40 ics has no recovery? but when i boot with power/volume down and then volume up, the tf300tg tries to boot in recovery and after a little while the android lay down... ist this normal behavior for the stock 9.4.4.40 ?
Click to expand...
Click to collapse
You do not have recovery by default, and you cannot have it without unlocking the bootloader.
Fortunately you can still root on ICS. Search the Dev section for the debugfs method for rooting on ICS.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
no, i have root. the one click tool has worked fine without errors... how it looks for ota updates? I read somewhere that i must have stock recovery for ota updates?! but with an open bootloader ota updates???
Wolf Hamburg said:
no, i have root. the one click tool has worked fine without errors... how it looks for ota updates? I read somewhere that i must have stock recovery for ota updates?! but with an open bootloader ota updates???
Click to expand...
Click to collapse
I'm told unlocked bootloader cancels ota but you can still manually update.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
funnel71 said:
You do not have recovery by default, and you cannot have it without unlocking the bootloader.
Fortunately you can still root on ICS. Search the Dev section for the debugfs method for rooting on ICS.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
Click to expand...
Click to collapse
Wolf Hamburg said:
yes, i know... the 9.4.4.40 is stock ics.
i never tries before i have rooted to boot in recovery. i thought each version, if stock or custom, has a recovery?
my bootloader is locked end i never flashed e recovery.
so it is normal that the stock 9.4.4.40 ics has no recovery? but when i boot with power/volume down and then volume up, the tf300tg tries to boot in recovery and after a little while the android lay down... ist this normal behavior for the stock 9.4.4.40 ?
Click to expand...
Click to collapse
Well. I have a TF300TG with stock 9.4.4.40 firmware (never tried to root, mod or anithing else) and I would like to simply root it...
I've seen many comments saying that after rooting, the stock recovery is lost (lying Android robot after Power+VolDown key press), and other replies stating that this is normal and that there isn't any stock recovery on the pad.
My five cents to this thread are that on my fresh pad I've tried to start from poweroff with Power+VolDown and I get something like a raw menu, with two icons at the center of the screen, giving me the option to make a full wipe or a cold boot (and maybe something else but I hadn't have time to go deeper inside it due to the timeout).
In any case, I don't get any lying Android robot!
Now, I'm a little scared to go on rooting my pad until this matter becomes definely clear...
Cheers
optigiu said:
...My five cents to this thread are that on my fresh pad I've tried to start from poweroff with Power+VolDown and I get something like a raw menu, with two icons at the center of the screen, giving me the option to make a full wipe or a cold boot (and maybe something else but I hadn't have time to go deeper inside it due to the timeout).
In any case, I don't get any lying Android robot!
Click to expand...
Click to collapse
Yes, this menu also comes to me.
But if I by power / volume down when the top left of the logo appears, press volume up, the pad trying to boot into recovery.
in your virginal system as well?
optigiu said:
Well. I have a TF300TG with stock 9.4.4.40 firmware (never tried to root, mod or anithing else) and I would like to simply root it...
I've seen many comments saying that after rooting, the stock recovery is lost (lying Android robot after Power+VolDown key press), and other replies stating that this is normal and that there isn't any stock recovery on the pad.
My five cents to this thread are that on my fresh pad I've tried to start from poweroff with Power+VolDown and I get something like a raw menu, with two icons at the center of the screen, giving me the option to make a full wipe or a cold boot (and maybe something else but I hadn't have time to go deeper inside it due to the timeout).
In any case, I don't get any lying Android robot!
Click to expand...
Click to collapse
Wolf Hamburg said:
Yes, this menu also comes to me.
But if I by power / volume down when the top left of the logo appears, press volume up, the pad trying to boot into recovery.
in your virginal system as well?
Click to expand...
Click to collapse
Ok, I've tried to press Power/VolDown and then, soon after the ASUS logo appeared at the center of the screen and a couple of rows of (small fonts) text were displayed at the top left, I released the two buttons and pressed just the VolUP; the result was that the screen was cleared and a standing green android robot appeared at the center with (kinda of) a blue progress bar under it; then, after about 1 sec, the figure was substituted by a lying green android robot having an open door at his "stomach" and a yellow triangle with an exclamation mark inside.
Is there any other check we can make on my fresh and your rooted systems in order to verify that rooting a TF300TG with 'one click transformer root' is safe? (what version did you use, 1.0 or 1.1?)
Edit: only now I've read this ... so it should be safe :fingers-crossed:
optigiu said:
...Edit: only now I've read this ... so it should be safe :fingers-crossed:
Click to expand...
Click to collapse
yes, now we can relax and wait for Jelly Bean
If itt. Is just your recovery that is lost no worries use fast boot and flash twrp or cwm
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
slide200sx said:
I unlocked bootloader and then used adb to push the cwm recovery, then used the root zip
worked for me, i had just got mine and feeling bad that the update just downloaded and wanted to install .40 all it all time but after i did it was still good....plus i had to learn adb to do it as the commands given had been wrong and didnt work,,,lol
Click to expand...
Click to collapse
Could you write a step by step guide about how to unlock bootloader and push the cwm recovery? Thanks.
Hey everyone. My 8013 has been rooted and running like a champ. Today I ran the OTA update via Kies and it said it successfully installed. I show that Im on build UEALH2.
I was having issues where it looked like the OTA didnt install all the way because I was getting notifications again that it was available. I rebooted into CWM and cleared the cache and dalvik, rerooted and booted into the device again. It went through the OTA installer again. This time when it was done, I checked and no software updates available. Sweet.
But now Im having issues with my screen not responding to touch inputs. The screen is still working, because I can remove the pen and the side bar loads, plus widgets are still updating... but it wont accept any inputs from my fingers or the pen? I did a factory reset to see if that would fix it, but what happens is when it starts up I have control of the touch screen. If I lock the device and then try to unlock it, the screen is immediately unresponsive to touch input. I was going to flash using Odin and the latest stock rom but the only post I saw where the latest rom was posted at shows the file is down: http://forum.xda-developers.com/showthread.php?t=1847706
Any ideas on what could be wrong or where I should go from here? Ive never ran into any issues like this with past devices.
GaresTaylan said:
Hey everyone. My 8013 has been rooted and running like a champ. Today I ran the OTA update via Kies and it said it successfully installed. I show that Im on build UEALH2.
I was having issues where it looked like the OTA didnt install all the way because I was getting notifications again that it was available. I rebooted into CWM and cleared the cache and dalvik, rerooted and booted into the device again. It went through the OTA installer again. This time when it was done, I checked and no software updates available. Sweet.
But now Im having issues with my screen not responding to touch inputs. The screen is still working, because I can remove the pen and the side bar loads, plus widgets are still updating... but it wont accept any inputs from my fingers or the pen? I did a factory reset to see if that would fix it, but what happens is when it starts up I have control of the touch screen. If I lock the device and then try to unlock it, the screen is immediately unresponsive to touch input. I was going to flash using Odin and the latest stock rom but the only post I saw where the latest rom was posted at shows the file is down: http://forum.xda-developers.com/showthread.php?t=1847706
Any ideas on what could be wrong or where I should go from here? Ive never ran into any issues like this with past devices.
Click to expand...
Click to collapse
Same issues here. Have been speaking with entropy and another member to try to fix this. I am at a loss as well.
Things I have tried:
*MD5 Post-update*
*Wipe Data/Cache via stock recovery*
*Re-flash MD5*
I am now in the process of locating a UEALGB recovery/kernel. If any member has a link to it or can help its certainly appreciated.
vanillanesquik said:
Same issues here. Have been speaking with entropy and another member to try to fix this. I am at a loss as well.
Click to expand...
Click to collapse
Are you just having OTA update issues or is your screen not responding properly to touch as well?
GaresTaylan said:
Are you just having OTA update issues or is your screen not responding properly to touch as well?
Click to expand...
Click to collapse
No touch, no pen input. Its worst-case.
vanillanesquik said:
No touch, no pen input. Its worst-case.
Click to expand...
Click to collapse
If you find the UEALGB recovery/kernel please let me know and provide the steps you used to fix the issue.
Guess thats what I get for jumping the gun on the update.
GaresTaylan said:
If you find the UEALGB recovery/kernel please let me know and provide the steps you used to fix the issue.
Guess thats what I get for jumping the gun on the update.
Click to expand...
Click to collapse
The update restored touch function but the pen functions are completely derped.
A pre-rooted full package is being uploaded by entropy in the next 2 hours so I am crossing my fingers that this will fix it.
I have the same issues I\m trying all things to get it to work just like you are to no avail, Samsung update now things are all screwed up
Alright (For N8013) who have lost pen/touch:
1. Wipe data/cache via stock recovery/kernel flashed in ODIN: http://forum.xda-developers.com/show...9&postcount=45
2. Flash root injected system via ODIN: http://stockroms.net/file/GalaxyNote...ctedSystem.zip
3. Re-kies to new firmware via WINDOWS
vanillanesquik said:
Alright (For N8013) who have lost pen/touch:
1. Wipe data/cache via stock recovery/kernel flashed in ODIN: http://forum.xda-developers.com/show...9&postcount=45
2. Flash root injected system via ODIN: http://stockroms.net/file/GalaxyNote...ctedSystem.zip
3. Re-kies to new firmware via WINDOWS
Click to expand...
Click to collapse
top link is dead, btw i lost touch functions LOL
anyway i will fix it
I'm not sure why any rooted user would take an OTA?
Sent from my EVO using Tapatalk 2
I had the same issue and flashed this via Odin: http://forum.xda-developers.com/showthread.php?t=1847706
Fixed it and now i'm running the latest update.
I lost touch and pen and now i have them back. Heres how:
1. IM AWESOME!
2. Rebooted my computer.
3. Wiped everything.
4. ODIN root injected original firmware.
5. Kies update.
6. ODIN Clockwork Recovery
7. Flash Superuser.
Boom, everything works.
** DISCLAIMER - There is a strong possibility this worked only due to #1. YMMV.
Sent from my GT-N8013 using Tapatalk 2
-viperboy- said:
I'm not sure why any rooted user would take an OTA?
Sent from my EVO using Tapatalk 2
Click to expand...
Click to collapse
Thank you!!! I have been saying this in other threads. Why would you use anything from Samsung knowing you have modified files to have root. :banghead:
Sent from my Galaxy Note 10.1 using Tapatalk
BigAtrain said:
Thank you!!! I have been saying this in other threads. Why would you use anything from Samsung knowing you have modified files to have root. :banghead:
Sent from my Galaxy Note 10.1 using Tapatalk
Click to expand...
Click to collapse
I took the OTA via Kies because it was listed in the OTA update thread that it was ok to do so? And that root was working fine afterward?
BigAtrain said:
Thank you!!! I have been saying this in other threads. Why would you use anything from Samsung knowing you have modified files to have root. :banghead:
Sent from my Galaxy Note 10.1 using Tapatalk
Click to expand...
Click to collapse
Because we are dangerous, exciting and chicks dig us.
Sent from my GT-N8013 using Tapatalk 2
-viperboy- said:
I'm not sure why any rooted user would take an OTA?
Sent from my EVO using Tapatalk 2
Click to expand...
Click to collapse
The root method 2 specified that OTA was viable with stock recovery. I flashed stock recovery and the OTA failed. We were then forced to update via KIES and touch/pen functions were then bugged. The best way is my method above.
vanillanesquik said:
Alright (For N8013) who have lost pen/touch:
1. Wipe data/cache via stock recovery/kernel flashed in ODIN: http://forum.xda-developers.com/show...9&postcount=45
2. Flash root injected system via ODIN: http://stockroms.net/file/GalaxyNote...ctedSystem.zip
3. Re-kies to new firmware via WINDOWS
Click to expand...
Click to collapse
I tried this method and when my note boots up s note keeps crashing every 15 seconds or so without my even opening it.
BigAtrain said:
Thank you!!! I have been saying this in other threads. Why would you use anything from Samsung knowing you have modified files to have root. :banghead:
Sent from my Galaxy Note 10.1 using Tapatalk
Click to expand...
Click to collapse
In many cases, if you ONLY have added su and Superuser.apk - you can safely apply an OTA. However if you've touched anything else in /system - boom
Standard practice is to reimage back to stock then apply OTA but the full image wasn't available via Kies until this update came out. This will be less of issue going forward as there's a full image now.
mi7chy said:
Standard practice is to reimage back to stock then apply OTA but the full image wasn't available via Kies until this update came out. This will be less of issue going forward as there's a full image now.
Click to expand...
Click to collapse
OK so o tried vanillas order and kies froze or disconnect me or something so I odined the md5 tar of the new update and back to no touch screen but like 5 mins so I shut it off and resume later.
What is the best thing to do to get all fixed up?
Sent from a Baked Black Jelly Belly