please help. my TF101 won't boot past ASUS screen. - Eee Pad Transformer Q&A, Help & Troubleshooting

Hi guys! I've joined this forum solely for this and I hope you can help. To start, I have had my Transformer for almost 4 years now. I haven't tried to root or add some custom firmware on this. So everything is "stock" so to speak. Recently my Transformer just turned off and restarted. I thought this was the usual "random restart" the transformer does but this time it wont get past the Asus boot screen with the spinning circles. I kinda left it till it'll run out of battery hoping this was a one time thing but when I tried charging it back up again, it still won't get past the boot screen to the desktop. I've tried cold-booting and also doing the "recovery kernel" thing but no luck. I've read about hard and soft bricks around the internet. I also read about bricks usually having bootloops. It doesn't seem like my tab is bootlooping but I'm still kinda leaning to the possibility that my loved TF101 is bricked. ( I haven't tried doing a whole factory reset because I still have some valuable files in my tab. Is there a way fix this thing or even just a way to recover my files before doing the factory reset? ANY HELP? ( please explain some terms and steps as simply as you can. I'd really appreciate it.

Try using EasyFlasher to flash TWRP recovery to it
http://forum.xda-developers.com/showthread.php?t=1688012
If you manage to get TWRP installed, you have a load of other options that can help get it booting again, and if not, you will be able to flash a new custom ROM to it instead

*Detection* said:
Try using EasyFlasher to flash TWRP recovery to it
http://forum.xda-developers.com/showthread.php?t=1688012
If you manage to get TWRP installed, you have a load of other options that can help get it booting again, and if not, you will be able to flash a new custom ROM to it instead
Click to expand...
Click to collapse
so the link presented me with two options. one is for flashing recovery. the other is for unbricking/flashing ASUS stock firmware. what do you suggest i do first?

Flash TWRP - you're gonna need TWRP for new ROMs anyway, old CWM recovery bricks the TF with JB+ ROMs
From TWRP you have the choice to either try to get back into your current ROM, back it up, or wipe and flash a new one

*Detection* said:
Flash TWRP - you're gonna need TWRP for new ROMs anyway, old CWM recovery bricks the TF with JB+ ROMs
From TWRP you have the choice to either try to get back into your current ROM, back it up, or wipe and flash a new one
Click to expand...
Click to collapse
Got it to work! Thank you, thank you! :victory: So I got to install KatKiss and I noticed it came with this Trebuchet launcher. I wanted to install another launcher from the store but when I start it up, it runs reeeeeeeally slow. The Trebuchet launcher works really smooth but for some reason the other launchers don't. Is there anyway to fix this?

If you're running KatKiss 4.4.x you need to disable "System Wallpaper Rendering" in Settings > Display > Wallpaper Mode/Disable (Speed Increase)
The latest KatKiss 4.4.2_r2 #23 (Released yesterday) has this set as default but I haven't tried it with another launcher yet, Im liking the new Trebuchet launcher atm
http://forum.xda-developers.com/devdb/project/dl/?id=4539
But the problem is then you need a launcher that uses Internal Wallpaper Rendering otherwise you end up with no wallpaper and unfortunately there are not a great deal of them out there, Next Launcher has it, Trebuchet does, a couple of those 3D launchers do.... I think Go Launcher does too
If you want to use Launchers like Apex and Nova, flash the last 4.3.1 version of KatKiss and change the Interface Mode from Phablet back to Tablet UI
It's the Phablet UI with the top dropdown notifications layer that our poor old TF's can't handle, removing the wallpaper layer fixes it but you need a launcher that can replace the walls
KatKiss 4.4.x don't have Tablet UI any more

*Detection* said:
If you're running KatKiss 4.4.x you need to disable "System Wallpaper Rendering" in Settings > Display > Wallpaper Mode/Disable (Speed Increase)
The latest KatKiss 4.4.2_r2 #23 (Released yesterday) has this set as default but I haven't tried it with another launcher yet, Im liking the new Trebuchet launcher atm
http://forum.xda-developers.com/devdb/project/dl/?id=4539
But the problem is then you need a launcher that uses Internal Wallpaper Rendering otherwise you end up with no wallpaper and unfortunately there are not a great deal of them out there, Next Launcher has it, Trebuchet does, a couple of those 3D launchers do.... I think Go Launcher does too
If you want to use Launchers like Apex and Nova, flash the last 4.3.1 version of KatKiss and change the Interface Mode from Phablet back to Tablet UI
It's the Phablet UI with the top dropdown notifications layer that our poor old TF's can't handle, removing the wallpaper layer fixes it but you need a launcher that can replace the walls
KatKiss 4.4.x don't have Tablet UI any more
Click to expand...
Click to collapse
I'm currently using the stable KatKiss-4.3.1_029 version. It's good you mentioned that they have released 4.4.x versions. Thanks. So once I download this, do i have to follow these steps again? Or is there a quicker way?:
.Backup everything !
.Go to recovery
.Make a full wipe / factory reset (you can skip this step if you're already on KatKiss-4.4, if ever you encounter a problem do the full wipe and try again before reporting )
.Format /system
.Flash the rom
.Flash optional kernel
.Flash gapps
.Wipe cache/dalvik
.Reboot
I'm kinda new to this and I guess I just need to familiarize myself with these basics.

If you're already using the #29 of 4.3.1 you can change Settings > User Interface > Interface Mode (Might be slightly different in 4.3.1) and change UI mode back to Tablet UI and you should have nice smooth experience with all launchers again
To move over to another ROM, if you're moving up 4.3.x > 4.4.x you can just wipe CACHE, DALVIK CACHE and SYSTEM, then flash the new ROM and Gapps, Wipe CACHE and DALVIK CACHE again, then reboot into your new ROM and all your apps etc will still be there
Not the case for going backwards though, 4.4.x to 4.3.x, you'll need to wipe both the caches and system, and data this time, which will remove all your apps
You can use an app called "Titanium Backup" to make a backup of your apps before wiping, and then again to restore them once you are in your new ROM
Or Make a full backup in TWRP, then you can also use Titanium Backup to restore from that TWRP (Nandroid) backup
You don't need to flash optional kernels if you're using the TF101 iirc (I don't)
Best thing to do is get your TF running 100%, then make a full Nandroid backup in TWRP, then you can wipe and flash to your hearts content, if it all goes pear shaped, you can restore your backup and return exactly to how it was when you made the backup
In short:
Going up in Android versions:
Wipe both CACHEs and System > Flash > Wipe Caches > Reboot
Going down in Android versions:
As above, but wipe DATA too
EDIT - Apologies for the rushed reply, Im on my way out, if you get stuck let me know and I'll explain it better when I get back

*Detection* said:
If you're already using the #29 of 4.3.1 you can change Settings > User Interface > Interface Mode (Might be slightly different in 4.3.1) and change UI mode back to Tablet UI and you should have nice smooth experience with all launchers again
To move over to another ROM, if you're moving up 4.3.x > 4.4.x you can just wipe CACHE, DALVIK CACHE and SYSTEM, then flash the new ROM and Gapps, Wipe CACHE and DALVIK CACHE again, then reboot into your new ROM and all your apps etc will still be there
Not the case for going backwards though, 4.4.x to 4.3.x, you'll need to wipe both the caches and system, and data this time, which will remove all your apps
You can use an app called "Titanium Backup" to make a backup of your apps before wiping, and then again to restore them once you are in your new ROM
Or Make a full backup in TWRP, then you can also use Titanium Backup to restore from that TWRP (Nandroid) backup
You don't need to flash optional kernels if you're using the TF101 iirc (I don't)
Best thing to do is get your TF running 100%, then make a full Nandroid backup in TWRP, then you can wipe and flash to your hearts content, if it all goes pear shaped, you can restore your backup and return exactly to how it was when you made the backup
In short:
Going up in Android versions:
Wipe both CACHEs and System > Flash > Wipe Caches > Reboot
Going down in Android versions:
As above, but wipe DATA too
EDIT - Apologies for the rushed reply, Im on my way out, if you get stuck let me know and I'll explain it better when I get back
Click to expand...
Click to collapse
I GOT IT TO UPDATE! Thank you for giving me a step by step process with this. I really appreciate it. I got my TAB off a brick and now I'm enjoying the newest KatKiss. Cheers!:good:

Great :good:

Related

[Q] Installing a non stock rom

I have TF300T rooted and unlooked with stock Jellybean 4.1.1 . I was thinking of installing clean rom 2.5 or another Jellybean one. If i do that am I able to go back to stock to get updates. If you could help me to get through the steps, I would be very grateful.
Thanks in advance for helping an old girl.
Linda
Well, the first thing that you need to know is that you need to make a nandroid backup using a custom recovery. Strange things happen. If you don't have a custom recovery installed (and I can't imagine why), visit the link below for instructions to install TWRP recovery.
http://www.androidauthority.com/transformer-pad-tf300t-install-twrp-recovery-97757/
After you have your recovery, make a nandroid backup. Next is the fact that you do NOT have to do a factory reset prior to installing any JB roms, to my knowledge. Wipe Cache/Dalvik Cache & System. Next step, flash the rom of your choice. CleanROM 2.5 uses AROMA Installer, and instead of me explaining what it is, simply try to flash and you will find out. You can easily follow the prompts to complete your install.
Lastly, REBOOT! When it finishes, if you experience a lot of force closes, like the dreaded "process.android.acore," only THEN should you try a factory reset. However, being that you are coming from JB, I wouldn't expect you to have this problem.
There...now that wasn't so hard?
P.S.: MAKE SURE that you download the new ROM before wiping. Pushing files onto the tablet can be quite a pain at times.

Procedure for updating a ROM...

I'm just wondering if my procedure for updating my ROM is correct, as I've only owned a smartphone for about a month, and have only flashed once.
Basically before I was running AOKP build 2 and Franco kernel r79 (or thereabouts) on my Nexus 4. I wanted to upgrade to AOKP build 3, so I backed stuff up, booted up in recovery, wiped my data, cleared the cache, then cleared the Dalvik cache before rebooting. Then it took me back to the initial setup screen, but I got confused when AOKP and Franco Kernel was still installed. I figured I should just open up the browser, download build 3 to the device (since everything is wiped), and then I'll flash that on top of build 2.
Am I supposed to flash back the stock ROM and kernel, or does it not matter since I will be running the same custom ROM?
Likewise, if I wanted to change my custom ROM (like install PA3 or something), then I would definitely need to flash back the stock rom and kernel before proceeding, am I right?
Smeghead_ said:
I'm just wondering if my procedure for updating my ROM is correct, as I've only owned a smartphone for about a month, and have only flashed once.
Basically before I was running AOKP build 2 and Franco kernel r79 (or thereabouts) on my Nexus 4. I wanted to upgrade to AOKP build 3, so I backed stuff up, booted up in recovery, wiped my data, cleared the cache, then cleared the Dalvik cache before rebooting. Then it took me back to the initial setup screen, but I got confused when AOKP and Franco Kernel was still installed. I figured I should just open up the browser, download build 3 to the device (since everything is wiped), and then I'll flash that on top of build 2.
Am I supposed to flash back the stock ROM and kernel, or does it not matter since I will be running the same custom ROM?
Likewise, if I wanted to change my custom ROM (like install PA3 or something), then I would definitely need to flash back the stock rom and kernel before proceeding, am I right?
Click to expand...
Click to collapse
Well since I really only have experience with a tablet and older cell phone I can only speak of my experiences with those. My tablet runs 4.2.2 and the phone 2.2. With both devices I have never had to flash them back to stock to flash an update. Usually a data and cache wipe was sufficient although I will wipe the whole system when flashing a huge update on the tablet.....like from GB to JB.
What helpful people told me when I asked the same question was...
When going to a very different (including the same ROM going to a new android version, ie 4.1 => 4.2) ROM (as in, not just doing a small update on the current one) :
Wipe both caches, wipe /system, wipe /data, and wipe internal sd card and factory reset.
Then flash what you want - ROM => Kernel (if desired) => GAPPs
Wipe caches again.
Done!
I don't know about your particular phone and those ROMs. Is AOKP 2 to 3 a big change ? If so, simply writing 3 over 2 could cause some major problems. I totally messed up and did something like that once and while it wasn't a huge deal I had to start over and do it again because it wasn't usable.
In regards to your description of what you did, you didn't wipe /system, so you didn't wipe your system and so it was still installed like you saw. You'll need to "start over" and wipe everything again. Since the N 4 doesn't have an external SD, I'm guessing you guys wipe /system and like, push the ROM to be flashed to the internal storage ? Maybe ? I have no idea - I've always had an external SD, but since it's a Nexus device I'm sure the procedure is well-covered !
My Kindle Fire tablet also does not actually have an SD card either.....the 8GB memory has been partitioned and originally I would have 5GB available out of 8 which would act as the SD card and 1.09GB for internal or "phone" memory. I have mine even more scrapped down as this one has the ability to either boot into CM7(GB) or the newest CM10.1(JB).
Say for example I went from Android 4.1.2 to 4.2.2.....that's a pretty big update......I would do a full wipe meaning doing it in this order: factory reset, wipe cache, wipe dalvik, and wipe system.
If I wanted to flash a little update of my current 4.2.2 where only some slight tweaks were applied I would just wipe cache and dalvik only. There are times when this simple flash wipe technique WON'T work and you'll probably realize it real quick. There could be any one of a million bugs that could occur and usually they are pretty noticeable. If that happens (sometimes it will, sometimes it won't) the worst case scenario is just going ahead and doing the full wipe.
I'm not knowledgeable on AOKP ROMs so I don't want to venture there. Boot loops are a whole different story and you might want to educate yourself as much as possible because they can happen. I had a couple occurances with a boot loop not too long ago as I was messing with a system font editor and it caused a boot loop. I didn't panic.....I already researched how to handle them so getting it back online was quite easy.
Hope my rambling has helped even a little bit.....
As long as you are just updating the same Rom, you can usually just flash it over (unless the Rom-maker says different).
If there are some fundamental changes in the Rom update, or you are switching to another Rom, then you should wipe it all.
To make it all a bit easier, you can use the Megawipe script:
http://forum.xda-developers.com/showthread.php?t=1832326
Along with the Aroma installer, it's just a few clicks to clean it all up, and ready for a fresh install

Pac-Man 4.2.2 Rom Question?

Hi, I am currently running stock TouchWiz 4.1.2 ROM, using CWM Recovery, I tried to install the Pac-Man Rom, but after phone rebooted it kept hanging on the PAC-MAN image with the ghosts, phone hung there for a bit, tried to reboot "removed the battery", went back to CWM Recovery, reflashed the Pac-Pam ROM and latest gaps, rebooted phone and the same thing happened,at some point it wiped out my CWM recovery, so I got fed up and reinstalled the TouchWiz factory 4.1.2 image using ODIN, had to reload all my apps and what not.
I want to give this one more try, but do not want to go through all this trouble again. I did a casche wipe and devlick cache wipe, but no data/factory wipe "heard people had success with a dirty flash routine", do I need to do a factory/data wipe for this to work.
I am not new to flashing, but have not flashed a non stock ROM yet, kind of leary after the PAC-Man fiasco, by the way what do you guys think of Cynogenmod or AOKP. Do I have to wipe all my data every time I try a new ROM. Is there a stock, pure android JB 4.2.2 ROM out there. Thanks again.
You have to wipe data/factory reset before flashing. Two different bases. One heavily nodded framework to stock(ish) won't work. Also, if you use something like titanium backup, you don't have to worry about losing things as much.
Sent from my SCH-I535 using Tapatalk 2
tylerlawhon said:
You have to wipe data/factory reset before flashing. Two different bases. One heavily nodded framework to stock(ish) won't work. Also, if you use something like titanium backup, you don't have to worry about losing things as much.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
So you are saying I can not flash this ROM do to it beign a 4.2.2 fro stock 4.1.2. So what ROM should I try before trying PAC-Man, I love PAC-Man
cybertec69 said:
So you are saying I can not flash this ROM do to it beign a 4.2.2 fro stock 4.1.2. So what ROM should I try before trying PAC-Man, I love PAC-Man
Click to expand...
Click to collapse
He is saying do not dirty flash ROMs you MUST do a factory reset as none of these ROMs are the same. By dirty flashing you are flashing one ROM over another which is a boneheaded move as you are likely to be stuck on the bootloader. The ONLY time you should dirty flash is when you are flashing a newer version of the same ROM.
jmxc23 said:
He is saying do not dirty flash ROMs you MUST do a factory reset as none of these ROMs are the same. By dirty flashing you are flashing one ROM over another which is a boneheaded move as you are likely to be stuck on the bootloader. The ONLY time you should dirty flash is when you are flashing a newer version of the same ROM.
Click to expand...
Click to collapse
Thank you sir, don't be angry at me, by the way it is much appreciated.
Basically. Don't dirty flash an aosp ROM over a touchwiz and vice versa
Sent from my SCH-I535 using Tapatalk 2
---------- Post added at 10:24 PM ---------- Previous post was at 10:23 PM ----------
Also don't dirty flash if the Android version is different.
Sent from my SCH-I535 using Tapatalk 2
My advice is to do a clean flash every time, and also a full backup. Here's what I do -
- backup all apps using your choice of app - I use MyBackup, there's also Titanium, Rom Toolbox and many others
- backup all sms, call logs
- backup launcher settings
- nandroid backup
- factory reset, wipe system/boot
- make sure you don't wipe internal or external sd card
- update to latest radio or rpm if needed
- flash rom
- flash kernel if needed
- flash gapps
- setup new rom, don't let google restore apps
- install your backup app and launcher
- restore apps, sms, calls etc
- restore launcher and android system
once you get comfortable with this procedure it doesn't take long. And it guarantees a clean phone with the latest apps and new rom with no issues.
ECrispy said:
My advice is to do a clean flash every time, and also a full backup. Here's what I do -
- backup all apps using your choice of app - I use MyBackup, there's also Titanium, Rom Toolbox and many others
- backup all sms, call logs
- backup launcher settings
- nandroid backup
- factory reset, wipe system/boot
- make sure you don't wipe internal or external sd card
- update to latest radio or rpm if needed
- flash rom
- flash kernel if needed
- flash gapps
- setup new rom, don't let google restore apps
- install your backup app and launcher
- restore apps, sms, calls etc
- restore launcher and android system
once you get comfortable with this procedure it doesn't take long. And it guarantees a clean phone with the latest apps and new rom with no issues.
Click to expand...
Click to collapse
Ok everything went fine, installed the Pac-Man ROM 4.2.2. seems much smoother and faster, my first question is how do I enable car mode where all my text messages are spoken out when received, including phone calls, my other question is now my screen is more cluttered by the on screen buttons at the bottom, the back home and systems button. The full clean wipe did help, thanks again.
Please read forum rules before posting
Questions and help issues go in Q&A
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator

[Q] LiquidSmooth 2.7 [S2 I9100]

Hey guys, I downloaded the official LiquidSmooth v2.7 installed it on my Galaxy S2 i9100 following the usual installation procedures. The problem is when I try to reboot it, it can't go beyond the new boot animation. I tried to re-install it but same problem persists. I would like to hear your advice, please.
LiquidSmooth Bootloop
spectator123 said:
Hey guys, I downloaded the official LiquidSmooth v2.7 installed it on my Galaxy S2 i9100 following the usual installation procedures. The problem is when I try to reboot it, it can't go beyond the new boot animation. I tried to re-install it but same problem persists. I would like to hear your advice, please.
Click to expand...
Click to collapse
Sounds like you have corrupt system files. You might need to start from scratch here. Try downloading the ROM again with a solid internet connection. A big factor is if you are coming from a different rom or stock android. Use Titanium Backup Pro or GO Backup Pro to back your phone up. The official Roms are from [goo.im] then navigate to your model make sure you have the correct one. Make sure you aren't crossing any data from a different rom including app data this can corrupt system files unless you are coming from a previous version of LiquidSmooth. If you are coming from a different rom you need to factory reset > wipe cache partition > then wipe dalvik cache all in the CWM recovery menu or whichever recovery you have then don't forget it to install your gapps zip. If you are trying to upgrade from a older version of Liquid Smooth before you install you need to wipe the cache partition and dalvik cache > Install Liquid 2.7 > wipe dalvik cache again > then install your gapps zip again I had to. If you are still having problems you might have to [format the sdcard] also in the recovery menu but can be risky. This is your last resort to try I've had to format mine before. Let me know if this helps. If not then you'll need to use a different rom or flash stock android back to your phone.

[Q] Factory reset doesn't unmodify so I can update my software

Way back when, I modified my 4.1.2 tab so I could use the Switchme app. Since it hasn't had a software update since then, I need to unmodify my system, so I did a hard reset but that doesn't seem to unmodify it so I can get it updated. Do I have to flash to a stock ROM, or won't that help either? I've done a hard reset twice now and restoring my Samsung account does seem to work either. Help PLEASE!
Nope it does not.
Stoney60 said:
Way back when, I modified my 4.1.2 tab so I could use the Switchme app. Since it hasn't had a software update since then, I need to unmodify my system, so I did a hard reset but that doesn't seem to unmodify it so I can get it updated. Do I have to flash to a stock ROM, or won't that help either? I've done a hard reset twice now and restoring my Samsung account does seem to work either. Help PLEASE!
Click to expand...
Click to collapse
Factory reset only Clears out use added content apps and Personal Settings. To get back to stop you will ..
1 Download the Correct Latest Version Of Android From Sam-mobile or Samsung For your Device.
2. Download odin for your device
3. Make sure you can access your device from windows or os your using.
4. Follow instructions for getting into download mode and flashing the samsung firmware with odin from your computer.
5 . Reboot the device and Leave it be..
Never flash anything on any Device until you know how to get back.
There are many Threads with step by step details on the above. even many youtube videos..
Good Luck
Hey,
I don't think you have to flash back to a stock ROM in order to upgrade to a different ROM. I was able to upgrade my tab with 4.1.2 (I can't remember what ROM it was) right to GNABO then a few hours later to Carbon, and a few hours later to Hyperdive and I'ts running fine with no issues besides the Aroma freezing, but what else is new...
You shouldn't have to flash back to a stock ROM to flash to a modified ROM, reason being is the modified ROM Flashes over the current ROM on the device, so the original ROM will be deleted anyways. The new ROM contains the updates for you, that's the advantage of androids. I recommend trying a few OS's before you pick the one for you stick with it. If you want to go stock there is a thread somewhere in the DEV section with the stock ROM just do some searching.
Make sure when you install a ROM to ;
Backup your device and make sure to keep a copy of the backup to your pc!
Boot into CWM Recovery or TWRP
Wipe data / factory reset
Wipe cache
Wipe dalvik cache
Install ROM from SD
Good Luck

Categories

Resources