Hi all, I decided I'd return my tf101 to ASUS stock firmware from TeamEos 4.2. So I duly flashed the f/w and all seemed to take OK, until I rebooted, the tf got stuck at the Android is updating stage, I tried reflashing everything but no good. This is not a request for help but more of a WTF. I have it working now thanks to NVFlash but I would like to understand why my first effort didn't work.
Different bootloader for JB, perhaps.
Related
I have combed these threads as hard as possible but still can't find a clear answer/fix.
I had a custom rom installed a while back, and it started freezing and not coming out of sleep mode. It has done this with asus official rom as well. Is there a specific process to wiping and installing the correct rom so this won't be an issue. It was running fine for at least 2 months before it started doing this and I can't seem to reverse this. I don't care if i have a custom rom or official, i just want my transformer to be used again!
thanks!
Hi all I decided to try and run a custom ics build a couple days ago everything went smoothly, I got the lastest AOKP build running with tastymeh kernel. Well tonight I disabled the boot animations and it seems as though I'm stuck bootlooping into the latest cwm(touch). I've tried reflashing the rom/kernal/wipe dalvik/etc to no avail. And my Nandroid backup isn't showing up to make matters worse. I can't even power down my device it just keeps bootlooping. I was wander what the best method to return to complete stock rom? Thanks everyone
Brand New said:
Hi all I decided to try and run a custom ics build a couple days ago everything went smoothly, I got the lastest AOKP build running with tastymeh kernel. Well tonight I disabled the boot animations and it seems as though I'm stuck bootlooping into the latest cwm(touch). I've tried reflashing the rom/kernal/wipe dalvik/etc to no avail. And my Nandroid backup isn't showing up to make matters worse. I can't even power down my device it just keeps bootlooping. I was wander what the best method to return to complete stock rom? Thanks everyone
Click to expand...
Click to collapse
Go here for instructions on how to fix
http://forum.xda-developers.com/showthread.php?t=1530337
Hope someone can help please, i have been using the Iconian rom since release and everything has been fine, i have been running on the unlocked a700 ics bootloader, today i tried to be to darn smart and flashed the iconian firmware update (to jellybean bootloader) now the a700 reboots but my touchscreen is dead. ive tried restoring my nandroid backup but it does nothing and the jb bootloader is still showing and touchscreen still dead. help please.
oxide32 said:
Hope someone can help please, i have been using the Iconian rom since release and everything has been fine, i have been running on the unlocked a700 ics bootloader, today i tried to be to darn smart and flashed the iconian firmware update (to jellybean bootloader) now the a700 reboots but my touchscreen is dead. ive tried restoring my nandroid backup but it does nothing and the jb bootloader is still showing and touchscreen still dead. help please.
Click to expand...
Click to collapse
i'd just flash the official firmware for JB via sd card.
If that fails to fix the screen see if any points work as it may be the touch bug where it needs a large amount of force to acknowledge anything till you go > sett > display > touch sensetivity > high
oxide32 said:
Hope someone can help please, i have been using the Iconian rom since release and everything has been fine, i have been running on the unlocked a700 ics bootloader, today i tried to be to darn smart and flashed the iconian firmware update (to jellybean bootloader) now the a700 reboots but my touchscreen is dead. ive tried restoring my nandroid backup but it does nothing and the jb bootloader is still showing and touchscreen still dead. help please.
Click to expand...
Click to collapse
I updated to 2.0 and flashed the new firmware....All went well for me. Maybe flash the whole thing again? Possibly do a wipe?
Thanks for taking time to look all, I changed from cwm touch to non touch and reflashed the iconian firmware and upon reboot it showed updating ebt . not sure why it made a difference but its now working again. Thanks again all.
First of all, thanks for all the hard work you guys do.
I have a problem with my tf101 running a Cyanomod. I tried searching on the forum, but there are so many keywords i don't even know how to input a proper query, so sorry if the problem has already been covered.
My tf101 was working just fine, i mounted a new rom (a nightly based on Jelly Bean 4.1.2), everything was nice and smooth, until one day i forgot to plug the charger to my tablet. The battery ran down to 0%, the first time it ever happened. Since then, everytime i try to power my tablet it gets stuck on the cyanogenmod rotating logo. I have to force reboot it several times before it starts working again, even if the battery id completely charged.
The first time it happened i tried wiping all data as well as the cache, i also tried reinstalling the rom but the only thing that seemed to work was reverting to a stable rom and then installing the nightly. Until the battery accident, everything was perfect.
Why is this happening? Is there a way to fix it?
You have said:
Code:
i also tried reinstalling the rom but the only thing that seemed to work was reverting to a stable rom and then installing the nightly.
So does you tablet boot into Android or not?
Because you have TF101 not G or Slider, you can NVflash the tablet to stock and try everything from beginning (root, custom recovery...).
Link to NVflash method
Sincerely,
Žiga
ZigaG said:
You have said:
Code:
i also tried reinstalling the rom but the only thing that seemed to work was reverting to a stable rom and then installing the nightly.
So does you tablet boot into Android or not?
Because you have TF101 not G or Slider, you can NVflash the tablet to stock and try everything from beginning (root, custom recovery...).
Link to NVflash method
Sincerely,
Žiga
Click to expand...
Click to collapse
Yeah it does, but only after countless attempts. If i do nothing and let it go, it gets stuck on the cyanogen logo forever.
I will try your solution and let you know, thanks.
Which recovery are you using ?
TWRP is the one to use, CWM has issues
Hi all,
I am using OMNIROM 4.4.4 bigpart in my old EU Wingray XOOM 32GB but I have lots of performance and stability issues (browser crashes, apps freezing, very slow system....). After reinstalling it I still have problems and I want to check if it's due to the device itself...
To test that, I would like to go back to the stock Android 4.0.4 ICS that I was using in my European xoom before the jump to EOS, CM and OMNI.
Could anybody help me on how to go back to stock? Where to download the stock rom? how to remove bigpart? Is it really required to remove bigpart to install the stock rom?
Thanks for any help given.
The best way to go back to factory image is to go back to Android 3.1 honeycomb , firmware HW169
http://morningbeat.blogspot.ca/2012/02/convert-uk-or-other-motorola-xoom-to.html
once you are back to android 3.1, keep check update. until you get the latest 4.12 or stop at 4.0.4 if you wish.
valent|n0 said:
The best way to go back to factory image is to go back to Android 3.1 honeycomb , firmware HW169
http://morningbeat.blogspot.ca/2012/02/convert-uk-or-other-motorola-xoom-to.html
once you are back to android 3.1, keep check update. until you get the latest 4.12 or stop at 4.0.4 if you wish.
Click to expand...
Click to collapse
Thanks a lot for answering.
So... I have to download the original Honeycomb software, "reflash it" and update until I get 4.0.4 or 4.1.2 ...
My doubt is ... do I have to "undo" the "bigpart"? Or will the stock firmware install perfectly in my "bigpart" xoom?
Thanks!
the bigpart issue I am not to sure of
Of course you need to undo BigPart. It's well document in Xoom Android development section of this forum.
You need to flash the non-big-part TWRP (2.8.0 or other), wipe everything, reboot intot TWRP, format Data, wipe everything again, reboot into TWRP again. Then you can flash original image using fastboot.
Just to stick my nose in, (and go slightly off topic) have you tried My Android Jellybean 4.2? before you go back to honeycomb you might want to give it a go, runs very smooth and very few bugs (if any!)
machina77 said:
Just to stick my nose in, (and go slightly off topic) have you tried My Android Jellybean 4.2? before you go back to honeycomb you might want to give it a go, runs very smooth and very few bugs (if any!)
Click to expand...
Click to collapse
... Sorry
jkd said:
... Sorry
Click to expand...
Click to collapse
Eh?
I didn't find anything in forum, could somebody help me how can i go back from bigpart to stock partition?
I tried to go back to stock last month and it was a nightmare trying to get it to boot back after the update. My only advise is to leave the thing alone. Or do a wipe in twrp or cwm. BTW, I still can not get my device to boot or enter recovery after my dumb ass tried to get back stock firmware.
nomadman said:
I tried to go back to stock last month and it was a nightmare trying to get it to boot back after the update. My only advise is to leave the thing alone. Or do a wipe in twrp or cwm. BTW, I still can not get my device to boot or enter recovery after my dumb ass tried to get back stock firmware.
Click to expand...
Click to collapse
I just flashed mine from omni bigpart back to stock 3.1 cause my 1yr old daughter can't keep her hands off my phone...was time consuming researching how to do it. But it works perfectly...I wound up running some script somebody wrote and it pretty much did everything for me... not in front of my PC at the moment but if you are still fighting it PM me and I'll give ya everything you need...