Hi guys, I have rooted and unlocked my TF700 few days ago. Currently with CWM recovery and CM10.1. I would like to change to Cromi-X for its faster performance. I am pretty new to this kind of stuff. From the Cromi-x TF700 developer page, it says TF700 user should be on stock 4.2.1. before flashing this ROM. Is there other way of doing it? What are the instructions to do so? Factory reset using custom recovery? install TWRP and bootloader? Step-by-Step instructions would be the best! Thank you so much! Would really appreciate it.:laugh::laugh:
FIY: I was on stock 4.2.1 before flashing CM10.1.
LexGoh said:
Hi guys, I have rooted and unlocked my TF700 few days ago. Currently with CWM recovery and CM10.1. I would like to change to Cromi-X for its faster performance. I am pretty new to this kind of stuff. From the Cromi-x TF700 developer page, it says TF700 user should be on stock 4.2.1. before flashing this ROM. Is there other way of doing it? What are the instructions to do so? Factory reset using custom recovery? install TWRP and bootloader? Step-by-Step instructions would be the best! Thank you so much! Would really appreciate it.:laugh::laugh:
FIY: I was on stock 4.2.1 before flashing CM10.1.
Click to expand...
Click to collapse
This post has all the information and instructions that you need and all the Cromi X downloads... Good luck and have fun..
Link: http://forum.xda-developers.com/showthread.php?t=2223492
Thanks a lot for your swift reply LetMeKnow! Yea that was the forum I was talking about. Just that I am not quite sure about few things in the OP.
From the OP:
"STEP 2 TF700 ONLY – I have a custom recovery installed but not the latest bootloader
If you are currently unlocked and on a JB 4.1.1/10.4.4.25 based custom rom like CleanROM Inheritance 3.x and have a custom recovery installed:
I recommend you install the appropriate Bootloader Recovery package below as the safest route to upgrade to CROMi-X. This can be flashed from any custom recovery "
1) I am on 4.2.1, can I still proceed with the same method?
2) So I am supposed to flash TWRP and bootloader using the CWM recovery that I already have? Or should I use the fastboot command method? Just to make sure as I don't wanna brick my tablet.
Appreciate your help! :good::good::good:
LexGoh said:
Thanks a lot for your swift reply LetMeKnow! Yea that was the forum I was talking about. Just that I am not quite sure about few things in the OP.
From the OP:
"STEP 2 TF700 ONLY – I have a custom recovery installed but not the latest bootloader
If you are currently unlocked and on a JB 4.1.1/10.4.4.25 based custom rom like CleanROM Inheritance 3.x and have a custom recovery installed:
I recommend you install the appropriate Bootloader Recovery package below as the safest route to upgrade to CROMi-X. This can be flashed from any custom recovery "
1) I am on 4.2.1, can I still proceed with the same method?
2) So I am supposed to flash TWRP and bootloader using the CWM recovery that I already have? Or should I use the fastboot command method? Just to make sure as I don't wanna brick my tablet.
Appreciate your help! :good::good::good:
Click to expand...
Click to collapse
I would love to help you further but I never use CWM. Therefore, it would be safe if someone has a better knowledge to help you out. _that, Sbdags, and others will have a good answer for you. They are very active in helping others users like you and me..
You can flash latest Cromix on top of CM10.1 even if you are using CWM (btw using CWM for CM roms is not mandatory,TWRP will work fine too).
I do recommend a clean install ( factory restore before flashing Cromi) but you could also try a "dirty" flash ( so your apps are not wiped) first and see if all works fine.
On a side note you should also try the CM10.2 experimental build,it's working nice here .
peace estreew
Pretoriano80 said:
You can flash latest Cromix on top of CM10.1 even if you are using CWM (btw using CWM for CM roms is not mandatory,TWRP will work fine too).
I do recommend a clean install ( factory restore before flashing Cromi) but you could also try a "dirty" flash ( so your apps are not wiped) first and see if all works fine.
On a side note you should also try the CM10.2 experimental build,it's working nice here .
Click to expand...
Click to collapse
Thank you so much Pretoriano! Would carefully proceed to flash it tonight, hopefully nothing will go wrong. In your opinion, do you think Cromi-X has better performance(in terms of speed and smoothness) over CM? Because I still find lags and what not in CM10.1.
LexGoh said:
Thank you so much Pretoriano! Would carefully proceed to flash it tonight, hopefully nothing will go wrong. In your opinion, do you think Cromi-X has better performance(in terms of speed and smoothness) over CM? Because I still find lags and what not in CM10.1.
Click to expand...
Click to collapse
Not using Cromi-X so i can't tell but you should try different roms yourself, trust me on that.But don't expect miracles from any rom,this device it is what it is.sometimes works nice then at some point starts to lag,self-reboot and act like crap.Latest CM10.2 looks good so far but the best way to prove it is to install all your usual apps and use it for some time,then decide if it's a keeper.
As for Cromi-X or other roms,i don't know if Journaling is disabled by default,but if it is keep in mind that is just a workaroud which trade stability for performance.
Personally i've build a custom rom for myself based on Asus firmware,removed some bloatware,patched to have the advanced power menu,used some init.d scripts wich you can find here on XDA and honestly performs just fine,no dangerous tweaks applied or task manager.
LexGoh said:
Thank you so much Pretoriano! Would carefully proceed to flash it tonight, hopefully nothing will go wrong. In your opinion, do you think Cromi-X has better performance(in terms of speed and smoothness) over CM? Because I still find lags and what not in CM10.1.
Click to expand...
Click to collapse
You definitely should switch to TWRP recovery. It's working fine with both CM and stock based roms like CROMi-X, whereas there have been issues if you use CWM with stock based roms.
You do have to do a clean install if you go from CM to CROMi-X.
Sent from my ASUS Transformer Pad TF700T using Tapatalk HD
berndblb said:
You definitely should switch to TWRP recovery. It's working fine with both CM and stock based roms like CROMi-X, whereas there have been issues if you use CWM with stock based roms.
You do have to do a clean install if you go from CM to CROMi-X.
Sent from my ASUS Transformer Pad TF700T using Tapatalk HD
Click to expand...
Click to collapse
Appreciate your help berndblb! By the way do I have to do clean install using "backup&reset" or wipe/factory reset using custom recovery?
LexGoh said:
Appreciate your help berndblb! By the way do I have to do clean install using "backup&reset" or wipe/factory reset using custom recovery?
Click to expand...
Click to collapse
You always should do a nandroid backup of your old setup/rom before you flash anything new.
In TWRP 'Factory Reset' is the default selection under the 'Wipe' menu. It will wipe your /data partition except for your /data/media/ folder where your personal stuff lives.
Naturally, you should have a backup of all your stuff anyway!
Data nor backed up is data not yet lost
Edit: To literally answer your question: A clean install is wiping data and system partitions as well as cache and Dalvik. If you flash CROMi-X (and I believe that's true for most custom roms), the system partition will get formatted before the new rom installation as part of the installation process. Wiping Cache and Dalvik is the default when installing CROMi-X, so you don't need to do that either. Just factory reset before flashing and you'll be good.
If you want to go squeaky clean, you would do a format data in TWRP (under the Wipe > Advanced menu). But that will erase your entire data partition, so you definitely have to have everything you care about backed up.
Sent from my ASUS Transformer Pad TF700T using Tapatalk HD
gedbyWe memoirs
berndblb said:
You always should do a nandroid backup of your old setup/rom before you flash anything new.
In TWRP 'Factory Reset' is the default selection under the 'Wipe' menu. It will wipe your /data partition except for your /data/media/ folder where your personal stuff lives.
Naturally, you should have a backup of all your stuff anyway!
Data nor backed up is data not yet lost
Edit: To literally answer your question: A clean install is wiping data and system partitions as well as cache and Dalvik. If you flash CROMi-X (and I believe that's true for most custom roms), the system partition will get formatted before the new rom installation as part of the installation process. Wiping Cache and Dalvik is the default when installing CROMi-X, so you don't need to do that either. Just factory reset before flashing and you'll be good.
If you want to go squeaky clean, you would do a format data in TWRP (under the Wipe > Advanced menu). But that will erase your entire data partition, so you definitely have to have everything you care about backed up.
Sent from my ASUS Transformer Pad TF700T using Tapatalk HD
Click to expand...
Click to collapse
That's a very clear explanation from you!:good::good: Certainly helps me a lot. One last question berndblb, can I flash TWRP over my current CWM directly(worry that it will cause or brick or whatsoever) before doing a factory reset? Or it is advisable to do a factory reset using CWM only then I flash the TWRP? Sorry if my question sounds dumb, because I am really new to all these stuff.
LexGoh said:
That's a very clear explanation from you!:good::good: Certainly helps me a lot. One last question berndblb, can I flash TWRP over my current CWM directly(worry that it will cause or brick or whatsoever) before doing a factory reset? Or it is advisable to do a factory reset using CWM only then I flash the TWRP? Sorry if my question sounds dumb, because I am really new to all these stuff.
Click to expand...
Click to collapse
Your first step should be to replace the CWM recovery. A factory reset only affects your data partition - no need to do that in CWM.
The main thing is that you have at all times a compatible bootloader/recovery combination. If you have the 10.6.1.14.4 or 10.6.1.14.8 bootloader, you can download GooManager, tap the 3 dots in the upper right corner and select "Install Open Recovery Script". It will install the latest TWRP version 2.6 over CWM. I am not sure if your CM version is compatible with TWRP 2.6 - so better check on that.
But once you have TWRP installed, you can proceed as described earlier.
Your questions are absolutely fine. Read everything you can find 5 times, ask 3 times, flash once - if and when you're sure! :Good:
One more thing: If you decide you do a factory reset or format data in TWRP, make sure you have the rom you want to flash (and I highly recommend CROMi-X 4.7) on your external microSD - it's safer that way. You may have to navigate to your microSD in TWRP under the 'Install' menu. By default TWRP shows your internal SD. Just tap that field and navigate to your external, select the CROMi-X zip and flash it.
The microSD has to be FAT32. It you never changed the factory format, you're good.
Sent from my ASUS Transformer Pad TF700T using Tapatalk HD
You can flash twrp on top of cwm no probs. I do it all the time. CROMi-X does work fine on cwm 6.0.3.0+
You will 100% need to wipe data (factory wipe good enough) before flashing CROMi-X. Good luck.
LexGoh said:
That's a very clear explanation from you!:good::good: Certainly helps me a lot. One last question berndblb, can I flash TWRP over my current CWM directly(worry that it will cause or brick or whatsoever) before doing a factory reset? Or it is advisable to do a factory reset using CWM only then I flash the TWRP? Sorry if my question sounds dumb, because I am really new to all these stuff.
Click to expand...
Click to collapse
You are a lucky person. All the people are trying to help you out are all experts around here. You will be safe if you are following their advices. You will be happy with Cromi X. Cromi X is running very smooth IMO... :good:
LetMeKnow said:
You are a lucky person. All the people are trying to help you out are all experts around here. You will be safe if you are following their advices. You will be happy with Cromi X. Cromi X is running very smooth IMO... :good:
Click to expand...
Click to collapse
You make me blush...
Sent from my DROID4 using Tapatalk 2
berndblb said:
Your first step should be to replace the CWM recovery. A factory reset only affects your data partition - no need to do that in CWM.
The main thing is that you have at all times a compatible bootloader/recovery combination. If you have the 10.6.1.14.4 or 10.6.1.14.8 bootloader, you can download GooManager, tap the 3 dots in the upper right corner and select "Install Open Recovery Script". It will install the latest TWRP version 2.6 over CWM. I am not sure if your CM version is compatible with TWRP 2.6 - so better check on that.
But once you have TWRP installed, you can proceed as described earlier.
Your questions are absolutely fine. Read everything you can find 5 times, ask 3 times, flash once - if and when you're sure! :Good:
One more thing: If you decide you do a factory reset or format data in TWRP, make sure you have the rom you want to flash (and I highly recommend CROMi-X 4.7) on your external microSD - it's safer that way. You may have to navigate to your microSD in TWRP under the 'Install' menu. By default TWRP shows your internal SD. Just tap that field and navigate to your external, select the CROMi-X zip and flash it.
The microSD has to be FAT32. It you never changed the factory format, you're good.
Sent from my ASUS Transformer Pad TF700T using Tapatalk HD
Click to expand...
Click to collapse
sbdags said:
You can flash twrp on top of cwm no probs. I do it all the time. CROMi-X does work fine on cwm 6.0.3.0+
You will 100% need to wipe data (factory wipe good enough) before flashing CROMi-X. Good luck.
Click to expand...
Click to collapse
Thanks to all experts that help me a lot!!!:good::good::good: Really really appreciate it! :laugh::laugh:
Related
Hi, i just want to return back to stock ICS 4.0.3 (unrooted).
My TF101 is now rooted. Below are some details for my TF101
Kernel Version..... 2.6.39.4
Build number..... IML74.WW_epad-9.2.1.17-20120312
Serial number ..... B80
Recovery ..... Rogue XM Recovery 1.3.0 (CMM-Based Recovery v5.0.2.7)
My TF101 is currently working just fine. I had a problem leaving recovery CMW but i managed to change it as above.
I have been looking for 5 days to find an NVFlash solution for my B80 tablet but no luck. Can you please help me restore it back to stock?
NVFlash will NOT work on B8O TF
Just download the official stock firmware from Asus website.
Extract it to get to the zip inside, put it on your sd card and flash with CWM.
(Wipe data, cache and dalvik ect... like flashing any other ROM)
Once rebooted you'll be on stock firmware and stock recovery
baseballfanz said:
NVFlash will NOT work on B8O TF
Just download the official stock firmware from Asus website.
Extract it to get to the zip inside, put it on your sd card and flash with CWM.
(Wipe data, cache and dalvik ect... like flashing any other ROM)
Once rebooted you'll be on stock firmware and stock recovery
Click to expand...
Click to collapse
Hi, and thanks for replying.
Do i need to install zip to mini sdcard?
If i do i wipe data/factory resest is ok?
Should i unroot it first?
Sorry for that but i am new to flashing
baseballfanz said:
NVFlash will NOT work on B8O TF
Just download the official stock firmware from Asus website.
Extract it to get to the zip inside, put it on your sd card and flash with CWM.
(Wipe data, cache and dalvik ect... like flashing any other ROM)
Once rebooted you'll be on stock firmware and stock recovery
Click to expand...
Click to collapse
I think it work just fine!!! Thank you so much.
Did what you said. Wipe data, cash and dalvik.
Then flash ww_epad-user-9.2.1.17 and reboot.
After that my TF101 was not rooted (checked with -Root Check Basic)
I also reboot to recovery and what a lying down adroid with red triangle.
Thank you so much for everything.
P.S. This means that my TF101 is back to manufactures' stock rom?
original21 said:
I think it work just fine!!! Thank you so much.
Did what you said. Wipe data, cash and dalvik.
Then flash ww_epad-user-9.2.1.17 and reboot.
After that my TF101 was not rooted (checked with -Root Check Basic)
I also reboot to recovery and what a lying down adroid with red triangle.
Thank you so much for everything.
P.S. This means that my TF101 is back to manufactures' stock rom?
Click to expand...
Click to collapse
Wow it wipe out your money too? LOL
Yeah you are completely stock
baseballfanz said:
Wow it wipe out your money too? LOL
Yeah you are completely stock
Click to expand...
Click to collapse
Let just say it didnt wipe my 450 euros
I did all the things you can think of and never thought of this
Why don't you make a threat for this issue. From what i was reading the past few days there are a lot of people facing the same issue and didn't know what to do. Also everyone (like me) was looking for an nvflash for their B70 + B80 TF101 devices to install the stock rom.
Rooting my nexus s and flashing different roms (am running CybergrMod V.9) was much more easier!
Once again thank you so much.
If this is true then what if the purpose of NVflash? I've been so worried about flashing roms because my serial is C10. I have the same setup as you listed. I guess NVflash would only be needed if you couldn't get into CWM?
Here's a good thread about almost everything
http://forum.xda-developers.com/showthread.php?t=1494230
baseballfanz said:
Here's a good thread about almost everything
http://forum.xda-developers.com/showthread.php?t=1494230
Click to expand...
Click to collapse
I never read the unroot section. I feel much better now about flashing ROMs. Still wish they would release the NVflash. thanks!
Hi Folks.
Ok here is my situation, I have a rooted and unlocked TF700.
I flashed Zeus 4 and all worked well, then flashed (after full wipe) PARANOIDANDROID 2.15 and again everything was great,
Yesterday I flashed Baked Bean 4 (again after a full wipe) and apart from some SD issues all seemed ok,
I then decided to restore my TWRP backup of Zeus as I needed to use my 64gig msd card.
After a full wipe and restore Zeus started up but the dpi was messed up (160) I think (way small)
I was seeing loads of FC's and file manager showed my internal SD as being empty. Rebooted to recovery and tried the "Format Data" option
It failed right away with this message "E: Unable to format data."
I have tried flashing the stock .26 rom via TWRP and I have the same issue, dpi set to 160 and internal sd not mounted.
It seems my Internal sd is corrupt
What is the procedure to reformat it via ADB or fastboot? (I have searched but the results I found relate to other devices and I dont want to simply follow instructions that might cause further harm to my TF700)
I have followed the NVflash brick proof procedure and have all relevant files backed up (I did this before flashing the last 2 roms)
Please can some one point me in the right direction
Thanks a lot
Jules
I always wipe cache, system, internal, davic and then do a factory reset.
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
When you said that you tried to flash the stock .26 you meant installing not restoring a backup, right? What rom you have on your device right now?
Pretoriano80 said:
When you said that you tried to flash the stock .26 you meant installing not restoring a backup, right. What rom you have on your device right now?
Click to expand...
Click to collapse
Yip extracted the zip from the zip file and copied it to my ext sd and flashed it via TWRP
I have an unusable Zeus4,
Im about to try a full wipe again and then flash .26 again
EDIT
After flashing .26 and selecting reboot I get the "No OS installed! Are you sure you wish to reboot?" message
Looks like the system partition is corrupted, but i'm not sure. I think you should come here on IRC and maybe someone with more experience will help you - - http://webchat.freenode.net/?channels=asus-transformer
Thanks so much Pretoriano80!
With his help on IRC I was able to solve the problem,
In the end I had to return to complete stock, It seems CM10 caused some problems,
You are a a legend dude Thanks!!
:good:
ZaJules said:
Thanks so much Pretoriano80!
With his help on IRC I was able to solve the problem,
In the end I had to return to complete stock, It seems CM10 caused some problems,
You are a a legend dude Thanks!!
:good:
Click to expand...
Click to collapse
This same thing happened to me with my Prime when I was getting ready to send it off for RMA because of a broken HDMI port. Since I was unlocked I was advised to restore to stock before sending it in. However, before I got the chance to do that I started getting the "E: Unable to format data." error that you were. I ended up erasing all partitions from fastboot and putting a note in the box that it wouldn't boot after an OTA. I managed to get away with it and wasn't charged for fixing it
For future reference it would be really helpful to know how you fixed this. Did you do something like what is in this thread: http://forum.xda-developers.com/showthread.php?t=1803343.
Did you ever figure out how CM10 messed up your Infinity? I was running CM9 on my Prime when I got this error. Thanks!
It's hard to say if it was CM10 (or any other custom rom) or TWRP to mess the things up but we managed to get back to stock by replacing the twrp with CWM recovery and installing a modified .30 update package. Was a tricky one but we didn't had to mess with the partitions and that's good.
Pretoriano80 said:
It's hard to say if it was CM10 (or any other custom rom) or TWRP to mess the things up but we managed to get back to stock by replacing the twrp with CWM recovery and installing a modified .30 update package. Was a tricky one but we didn't had to mess with the partitions and that's good.
Click to expand...
Click to collapse
Why did you switch to CWM? Do you have any thoughts on the advantages and disadvantages of TWRP vs CWM?
paddycr said:
Why did you switch to CWM? Do you have any thoughts on the advantages and disadvantages of TWRP vs CWM?
Click to expand...
Click to collapse
Switched to CWM just to make sure it wasn't twrp recovery that somehow was failing to flash the partitions correctly. Tbh so far both do their job and both share the same limitation so far, meaning both fail to restore the boot partition (kernel) so in order to restore successfully (from a nandroid backup) you need to flash the right kernel after restoring is done. Otherwise i like TWRP better and never had issues with it, but i miss the advanced option from CWM, the one that let you format each partition individually.
Pretoriano80 said:
Switched to CWM just to make sure it wasn't twrp recovery that somehow was failing to flash the partitions correctly. Tbh so far both do their job and both share the same limitation so far, meaning both fail to restore the boot partition (kernel) so in order to restore successfully (from a nandroid backup) you need to flash the right kernel after restoring is done. Otherwise i like TWRP better and never had issues with it, but i miss the advanced option from CWM, the one that let you format each partition individually.
Click to expand...
Click to collapse
I'm not certain what you're referring to here. I've restored many times from different TWRP backups (for each custom rom that successfully boots and is half-decent, I make and keep a backup in case I want to jump around and try new things) and I've never had any issues. I am still on the .26 firmware update because I plan to do the nvflash thing. Are you saying that between Zeus v4 (ICS) and various Jelly Bean roms I've been on the same kernel? I gues I just haven't checked.
Anyway, I really love the TWRP recovery and use it with Xoom and Nexus 7 as well. It's so easy to use and always has been reliable.
okantomi said:
I'm not certain what you're referring to here. I've restored many times from different TWRP backups (for each custom rom that successfully boots and is half-decent, I make and keep a backup in case I want to jump around and try new things) and I've never had any issues. I am still on the .26 firmware update because I plan to do the nvflash thing. Are you saying that between Zeus v4 (ICS) and various Jelly Bean roms I've been on the same kernel? I gues I just haven't checked.
Anyway, I really love the TWRP recovery and use it with Xoom and Nexus 7 as well. It's so easy to use and always has been reliable.
Click to expand...
Click to collapse
For me moving between various roms by just restoring a backup never worked like it should. Let's say i'm on CM10 and i want to restore from a stock rom backup, the restore process is done, after reboot the device gets stuck to the first Asus screen and will stay there. Now if i get back to recovery and flash an update. zip containing the stock kernel the device will boot just fine, so definitely the boot image doesn't get restored in my case (with . 26 bootloader ).
Edit: @okantomi: You are using the internal storage or a MicroSD for backup / restoring? I'm really curious how this could work for some and not work for others, i mean same device, same recovery, same bootloader version...
Pretoriano80 said:
For me moving between various roms by just restoring a backup never worked like it should. Let's say i'm on CM10 and i want to restore from a stock rom backup, the restore process is done, after reboot the device gets stuck to the first Asus screen and will stay there. Now if i get back to recovery and flash an update. zip containing the stock kernel the device will boot just fine, so definitely the boot image doesn't get restored in my case (with . 26 bootloader ).
Edit: @okantomi: You are using the internal storage or a MicroSD for backup / restoring? I'm really curious how this could work for some and not work for others, i mean same device, same recovery, same bootloader version...
Click to expand...
Click to collapse
Ok, I only flash a new zip from the internal storage...made myself a "Flashworthy" folder which I keep stocked with newest versions of roms/gapps. I save my TWRP backups to my external microsdcard, as well as my TiBu backups. I have never had a problem restoring from TWRP this way, honestly.
okantomi said:
Ok, I only flash a new zip from the internal storage...made myself a "Flashworthy" folder which I keep stocked with newest versions of roms/gapps. I save my TWRP backups to my external microsdcard, as well as my TiBu backups. I have never had a problem restoring from TWRP this way, honestly.
Click to expand...
Click to collapse
Well, in this case i really have no clue why restoring works for some users but not for all.Dees_Troy, the dev behind Twrp recovery told me that .26 bootloader is to blame for the recovery failing to restore the boot partition, but looks like you have that bootloader version and restoring works good for you... interesting.
Pretoriano80 said:
Well, in this case i really have no clue why restoring works for some users but not for all.Dees_Troy, the dev behind Twrp recovery told me that .26 bootloader is to blame for the recovery failing to restore the boot partition, but looks like you have that bootloader version and restoring works good for you... interesting.
Click to expand...
Click to collapse
It is a mystery. Is there any other info that might be relevant to see why the difference in results? I ask because I would like to understand this device better, as well as potentially help others.
okantomi said:
It is a mystery. Is there any other info that might be relevant to see why the difference in results? I ask because I would like to understand this device better, as well as potentially help others.
Click to expand...
Click to collapse
I don't know, maybe the twrp version and the backup options, like if you are using compression or not, which partitions do you backup (boot, system, data, recovery, cache)...
Pretoriano80 said:
I don't know, maybe the twrp version and the backup options, like if you are using compression or not, which partitions do you backup (boot, system, data, recovery, cache)...
Click to expand...
Click to collapse
I'm using TWRP 2.2.2.1, I back up boot, system and data only, and I don't use compression.
Hey everybody.
EDIT: Thanks to berndblb and all the others who replied, it works again like a charm.
I just got my Asus Transformer back from RMA because it wouldn't latch with the dock anymore.
Now I'm getting random reboots when the tablet boots up. Sometimes it makes it to the lockscreen, but in this case it freezes immediately.
I now tried reinstalling CM 10.0 and 10.1.2 after wipping all the data from the Tablet.
I then tried installing the cleanrom with the data2sdcard fix, but I have now the same problem as before.
Additional Infos:
Recovery: TWRP 2.5.0.0
Rom at the moment: CleanROM Inheritance 3.4.7 http://forum.xda-developers.com/showthread.php?t=2049274
Data2SD http://forum.xda-developers.com/showthread.php?t=1962507
Bootloader: 10.4.4.25-20131228
If you have any questions or need more logfiles don't hesitate to ask. Somehow I can't get logcat to work before it shutdowns, so I can only provide log which are stored on the filesystem. (I can access the shell within the recovery and push and pull files).
Thanks in advance for your help and for your time in which you read this text.
Maybe an old bootloader? Check the version displayed in the bootloader menu.
I've got the 10.4.4.25-20131228 Version, which is recommended to install CleanROM.
http://forum.xda-developers.com/showthread.php?t=2049274
Nahakiole said:
I now tried reinstalling CM 10.0 and 10.1.2 after wipping all the data from the Tablet.
Click to expand...
Click to collapse
Nahakiole said:
I've got the 10.4.4.25-20131228 Version, which is recommended to install CleanROM.
Click to expand...
Click to collapse
Try installing the bootloader recommended for the ROM you are trying to install.
Nahakiole said:
I then tried installing the cleanrom with the data2sdcard fix, but I have now the same problem as before.
Click to expand...
Click to collapse
Sorry if I wasn't clear enough. At the moment I am trying to install cleanrom, because I thought the problem was with cm.
But now as I do have the exact same problem with cleanrom as with cm I think it isn't the rom.
Nahakiole said:
Sorry if I wasn't clear enough. At the moment I am trying to install cleanrom, because I thought the problem was with cm.
But now as I do have the exact same problem with cleanrom as with cm I think it isn't the rom.
Click to expand...
Click to collapse
You can try to remove the External SD card and reboot without it. Please report back so we all know what is happening, thanks..
Nahakiole said:
Sorry if I wasn't clear enough. At the moment I am trying to install cleanrom, because I thought the problem was with cm.
But now as I do have the exact same problem with cleanrom as with cm I think it isn't the rom.
Click to expand...
Click to collapse
"Wiping all your data" means exactly what? Have you done a factory reset in TWRP? If yes, try formating your data partition.
Plus, you are trying to install an outdated rom that is no longer supported.
sbdags has moved on to CROMi-X, the JB 4.2.1 based rom for this tablet. Look for the thread in the development section.
Flash the bootloader/TWRP package from the first post, boot back into your old rom.
Then do a factory reset in TWRP which will wipe your data partition and flash the latest CROMi-X rom.
Sent from my ASUS Transformer Pad TF700T using Tapatalk 4
berndblb said:
"Wiping all your data" means exactly what? Have you done a factory reset in TWRP? If yes, try formating your data partition.
Plus, you are trying to install an outdated rom that is no longer supported.
sbdags has moved on to CROMi-X, the JB 4.2.1 based rom for this tablet. Look for the thread in the development section.
Flash the bootloader/TWRP package from the first post, boot back into your old rom.
Then do a factory reset in TWRP which will wipe your data partition and flash the latest CROMi-X rom.
Sent from my ASUS Transformer Pad TF700T using Tapatalk 4
Click to expand...
Click to collapse
I'll try that. I wasn't sure if the newer Version supported the Data2SD Mod so I tried installing the older Version.
But I see now that it's supported.
@LetMeKnow
As I'm using the Data2SD Mod, I get the error message "Encryption unsuccessful".
Which means it's really installed on the SD-Card.
I also am able to start it up to the setup process, but before I can finish the setup, the tablet randomly reboots.
http://forum.xda-developers.com/showthread.php?t=1962507
Is there any way to do this without having to do a factory wipe?
It may be possible, however it is HIGHLY recommended to do a factory reset in recovery. If you choose not to, I do not even want to think about what will crash going from Honeycomb to JellyBean 4.2/4.3
Here is what I would do. First, install GooManager from the play store. Update the recovery to TWRP 2.3.2.3. I have seen a LOT of users with issues using CWM on android 4.2 and later. Some swear it works great, but I would not trust it myself. After installing the GooManager, tap the menu button in the top right and choose the Install OpenRecovery Script.
Next, use Titanium Backup to back up your user apps. Do not back up system apps. Restoring these can cause some issues on newer versions of Android, especially since there are no Jelly Bean ROMs based on stock Asus Firmware.
Download your ROM of choice, and any GAPPS or kernels that you want to install.
Boot to recovery.
Backup your current setup as a fail safe.
Next, wipe the following partitions:
Cache
Davlik Cache
System
Data (Factory Reset). This will wipe the /data/ partition without wiping /data/media/ (aka /sdcard/) so your files on the internal storage will still remain. I would HIGHLY recommend doing a FORMAT DATA and fully wiping the /sdcard/ to help your device run faster. The files on /sdcard/ are not backed up by recovery's backup function so if you choose to do this be sure you backed up your entire /sdcard/ to microSD/SD/USB/PC/Cloud storage before formatting it.
Now go to the Install menu and install the ROM. Also install GAPPS and kernel if required.
I always wipe cache & davlik again after flashing then reboot. Set up the new ROM and then install TiBu and restore your apps. Once again, be sure not to restore any system apps or data as it can cause random reboots, SOD and app crashes.
Thanks for such a quick and detailed reply. I do have TB so that is not the problem. My problem is I do not want to lose my custom HUB that I created and am not sure how to back that up. Also I have been fairly happy with this HC rom other than a few browser crashes and the occasional overnight battery drain. Is JB that much better than HC?
thorin33 said:
Thanks for such a quick and detailed reply. I do have TB so that is not the problem. My problem is I do not want to lose my custom HUB that I created and am not sure how to back that up. Also I have been fairly happy with this HC rom other than a few browser crashes and the occasional overnight battery drain. Is JB that much better than HC?
Click to expand...
Click to collapse
It will be night and day.
As far as your HUBS, are you using a custom launcher? If so it should be backed up with the launcher settings. If not, you will have to set it up again....which I know how much time that takes.
frederuco said:
It will be night and day.
As far as your HUBS, are you using a custom launcher? If so it should be backed up with the launcher settings. If not, you will have to set it up again....which I know how much time that takes.
Click to expand...
Click to collapse
Plus 1. I hesitated to upgrade because I was "comfortable" with the ROM I was on (Megatron). I decided to update to KatKiss 4.3 mostly cause I was bored and wanted to flash something. Glad I did as it's a big different.:good:
Thanks again. I am using ADW and saved my configuration. I may just have to bite the bullet and just do it.
That is where I am at. I am very comfortable with this ROM and quite happy with it. Just wondering if the grass is greener.
thorin33 said:
That is where I am at. I am very comfortable with this ROM and quite happy with it. Just wondering if the grass is greener.
Click to expand...
Click to collapse
MUCH greener - Honeycomb is an ancient slow laggy build of Android, Jellybean is a fast smooth build
The user experience using Jellybean is immensely improved
Its the difference between Vista and 8.1, if not more, maybe XP > 8.1
Just make a Nandroid backup with TWRP recovery, then wipe everything, flash KatKiss #226 and Gapps and play around with it
Guarantee you will not want to return to HC
On the off chance you do want to return, just boot back into TWRP and restore your backup, you'll be back to exactly the state you were in when you made the backup, nothing lost
frederuco said:
It will be night and day.
As far as your HUBS, are you using a custom launcher? If so it should be backed up with the launcher settings. If not, you will have to set it up again....which I know how much time that takes.
Click to expand...
Click to collapse
Does anyone happen to know if my HUBS using ADW will look and act the same in JB?
thorin33 said:
Does anyone happen to know if my HUBS using ADW will look and act the same in JB?
Click to expand...
Click to collapse
I don't know anyone using HUBS myself. I am not sure how ADB works with JB. I moved on to APEX myself.
I think the BEST option is to make a backup of PRIME. Install, restore your apps (I would restore ADW last after all widgets and such are restored) and test it out.
If it does not work like you wanted, restore the PRIME backup in recovery and you will be right where you left off.
Well I figured I would give it a go. I installed Goo Manager and tried to install OpenRecovery. I just get the notifiation that it is downloading then a force close of Goo Manager. Not sure what to do now. I have tried to re-install Goo Manager but still get the same thing. I have rebooted, cleared Dalvik.
thorin33 said:
Well I figured I would give it a go. I installed Goo Manager and tried to install OpenRecovery. I just get the notifiation that it is downloading then a force close of Goo Manager. Not sure what to do now. I have tried to re-install Goo Manager but still get the same thing. I have rebooted, cleared Dalvik.
Click to expand...
Click to collapse
Use Easyflasher to flash TWRP, then Goo Manager to update it
http://forum.xda-developers.com/showthread.php?t=1688012
Or if Frederuco would be kind enough to link to his updated version, you can flash the newest TWRP in one shot
thorin33 said:
Well I figured I would give it a go. I installed Goo Manager and tried to install OpenRecovery. I just get the notifiation that it is downloading then a force close of Goo Manager. Not sure what to do now. I have tried to re-install Goo Manager but still get the same thing. I have rebooted, cleared Dalvik.
Click to expand...
Click to collapse
*Detection* said:
Use Easyflasher to flash TWRP, then Goo Manager to update it
http://forum.xda-developers.com/showthread.php?t=1688012
Or if Frederuco would be kind enough to link to his updated version, you can flash the newest TWRP in one shot
Click to expand...
Click to collapse
I was thinking the same thing.
See here:
frederuco said:
Since this tool has not been updated for newer recoveries, I repacked the zip with the two latest versions of TWRP:
EasyFlasher with TWRP 2.3.2.3
EasyFlasher with TWRP 2.5.0.0
EasyFlasher with TWRP 2.6.0.0
EasyFlasher with TWRP 2.6.1.0
EasyFlasher with TWRP 2.6.1.0-b This version has the microSD mounted as /MicroSD/ instead of /sdc/
EasyFlasher with TWRP 2.6.1.0-c This version has the the storage mounted as sdcard0 for internal storage and microSD is mounted as sdcard1
EasyFlasher with TWRP 2.6.3.0 Fixes the SuperSU nag during reboot.
NOTE - It STILL has the TWRP version listed as 2.2.1.1 in the dropdown, but it WILL INSTALL 2.3.2.3, 2.5.0.0 or 2.6.X.X I cannot update the dropdown.
I have tested all of these on my TF101 and all of them worked successfully.
Click to expand...
Click to collapse
You can follow my rooting guide here for detailed instructions on how to use EasyFlasher: http://www.transformerforums.com/fo...nt/31927-frederucos-guide-root-rom-tf101.html
frederuco said:
EasyFlasher with TWRP 2.6.3.0 Fixes the SuperSU nag during reboot.
Click to expand...
Click to collapse
Frederuco - do I have to use the EasyFlasher version with ADB to flash the TWRP 2.6.3.0? Although I updated to TWRP 2.6.3.0-c today and then updated to KatKiss 4.3 v24 and the nag hasn't appeared again (yet)
Theziggy said:
Frederuco - do I have to use the EasyFlasher version with ADB to flash the TWRP 2.6.3.0? Although I updated to TWRP 2.6.3.0-c today and then updated to KatKiss 4.3 v24 and the nag hasn't appeared again (yet)
Click to expand...
Click to collapse
If you have a custom recovery installed, just flash the zip file in sidneyk's TWRP thread to update to a different version.
http://forum.xda-developers.com/showthread.php?t=2434422
frederuco said:
If you have a custom recovery installed, just flash the zip file in sidneyk's TWRP thread to update to a different version.
http://forum.xda-developers.com/showthread.php?t=2434422
Click to expand...
Click to collapse
Oh I know how to flash the zip file Frederuco (as my sig shows - I have recently updated to 2.6.3.0-3 using this method), I was wondering what the advantage of the EasyFlasher version was - or is that for people who are just starting to root their tf101?
Theziggy said:
Oh I know how to flash the zip file Frederuco (as my sig shows - I have recently updated to 2.6.3.0-3 using this method), I was wondering what the advantage of the EasyFlasher version was - or is that for people who are just starting to root their tf101?
Click to expand...
Click to collapse
EasyFlasher is mainly to install a custom recovery when you are still stock so you can root and/or ROM and also to flash the stock firmware if you bricked your tablet and it won't boot to recovery or to a ROM.
It can be used to update to a newer version of TWRP or other recovery, but it is much easier to just flash the zip file in recovery as you do not need to have a PC to make it happen.
That's what I was kinda thinking Frederuco, thanks for clarifying it for me :good: :good: :good:
Finally found some time to do a little bit more on my upgrade path (Having a 5 month old sucks up most of my free time). I was able to just install the zip from sidneyk. Did my nandroid and hopefully will find time to flash Katkiss.
Thanks for all the help so far everyone.
I noticed that when I went to do my backup I got the following message:
Updating partition details
E: Unable to locate ui.xml in zip file
E: An internal error has occured.
It proceeded to backup and said it was successful. Is this normal?
TIA
HI, i have been having isues with my asus tf101 baterry, about one month ago it suddenly charge and discharges, like: 10%-25%-40%-70%-80%-100%...I made a factory reset but nothing. 2 weeks ago, it solved alone, without do anything, and was ok for 2 weeks, now again i have the problem..
i have installed cwm recovery, i want to change to android revolution rom, to see if the problem finish:
1 question: How i change from cwm to twrp recovery? installing twrp from cwm using a zip? is there no problem?? or downloading goomanager, installing recovery script?? Is there any problem to use cwm or twrp( i have read, to instal kk i dont use cwm)?
2 question, what rom is stable to try to solve this? i see kk 4.3 etc, but i just one my baterry works ok...
3 question, is there any way to clean absolutely the stock rom? i tried wipe cache, dalvik, factory reset(again) but nothing solve.
4 question, is possible to wipe ALL including system, and install the asus stock rom using zip¿?
Thanks for your atention, please be the most specifically possible because i am new on this, and i just one my tablet for study(read books).
I have a asus tf101 b70 root, with CWM recovery is a old version 5.0.26 something..
cesar_cjx said:
HI, i have been having isues with my asus tf101 baterry, about one month ago it suddenly charge and discharges, like: 10%-25%-40%-70%-80%-100%...I made a factory reset but nothing. 2 weeks ago, it solved alone, without do anything, and was ok for 2 weeks, now again i have the problem..
i have installed cwm recovery, i want to change to android revolution rom, to see if the problem finish:
1 question: How i change from cwm to twrp recovery? installing twrp from cwm using a zip? is there no problem?? or downloading goomanager, installing recovery script?? Is there any problem to use cwm or twrp( i have read, to instal kk i dont use cwm)?
2 question, what rom is stable to try to solve this? i see kk 4.3 etc, but i just one my baterry works ok...
3 question, is there any way to clean absolutely the stock rom? i tried wipe cache, dalvik, factory reset(again) but nothing solve.
4 question, is possible to wipe ALL including system, and install the asus stock rom using zip¿?
Thanks for your atention, please be the most specifically possible because i am new on this, and i just one my tablet for study(read books).
I have a asus tf101 b70 root, with CWM recovery is a old version 5.0.26 something..
Click to expand...
Click to collapse
Q1: I think you can just flash the new recovery via the current recovery if you have the new recover zip file.
Q2: Kat Kiss works fine for me.
Q3: If you want to completely return to stock, you would have to use NVFlash. There are tons of instructions on the Dev thread. I primarily use Tubuntu for flashing with NVFlash. [http://forum.xda-developers.com/showthread.php?t=1995157]
You can find other images as well. I used a stock image once to RMA the tablet but now I'm not sure where I got it. This method will ensure that every bit in your memory is exactly as it left the factory. Including the bootloader, recovery partition and everything else.
Q4: Refer Q3.
Download flashable TWRP 2.6.3.11 zip for TF101:
http://forum.xda-developers.com/devd...ct/dl/?id=3280
You should use TWRP for KatKiss ROMs, do not use CWM
Flash that Zip from CWM then reboot fully into your current ROM, then reboot into Recovery to check it has flashed properly
From TWRP you can wipe everything and flash KatKiss & Gapps
*Detection* said:
Download flashable TWRP 2.6.3.11 zip for TF101:
http://forum.xda-developers.com/devd...ct/dl/?id=3280
You should use TWRP for KatKiss ROMs, do not use CWM
Flash that Zip from CWM then reboot fully into your current ROM, then reboot into Recovery to check it has flashed properly
From TWRP you can wipe everything and flash KatKiss & Gapps
Click to expand...
Click to collapse
Is this the same process for going from TWRP to TWRP? just "install" the newest version from recovery and do the reboots?
stache12 said:
Is this the same process for going from TWRP to TWRP? just "install" the newest version from recovery and do the reboots?
Click to expand...
Click to collapse
Yep, so long as you reboot into your ROM after flashing the new TWRP before booting back into recovery
Thanks for your reply, i will tray soon. So i want to clean the asus stock room to see if battery goes ok, i tried wipe data, cache, dalvik, with cwm, but nothing.
If i install twrp what more options can i try before change the rom? what more wipe do i need?? and finally, if i change the rom, is possible to go back to asus stock just flashing from recovery? or how should i do?
Apart from wiping the ROM (SYSTEM) there's not much else you can wipe, you could try wiping the same as you have already done, but from TWRP, see if that makes any difference, maybe the battery is coming to the end of its life
You can flash stock ASUS ROMs back again from TWRP yes, but you will wipe your recovery & ROM back to 100% stock by doing it
Best thing to do is to make a full Nandroid Backup from TWRP before flashing any custom ROMs, save it to MicroSD Card, then if you want to go back to the way it is now, just restore the backup from TWRP
That way you keep TWRP and can switch between as many ROMs as you like and always have your stock backup to go back to whenever you want
46999589
*Detection* said:
Apart from wiping the ROM (SYSTEM) there's not much else you can wipe, you could try wiping the same as you have already done, but from TWRP, see if that makes any difference, maybe the battery is coming to the end of its life
You can flash stock ASUS ROMs back again from TWRP yes, but you will wipe your recovery & ROM back to 100% stock by doing it
Best thing to do is to make a full Nandroid Backup from TWRP before flashing any custom ROMs, save it to MicroSD Card, then if you want to go back to the way it is now, just restore the backup from TWRP
That way you keep TWRP and can switch between as many ROMs as you like and always have your stock backup to go back to whenever you want
Click to expand...
Click to collapse
Thanks!! I will try, but apart from wipe system(rom) what more wipes can i try without erase the rom?..I think not, because a week ago the battery was perfect working...i hope so.
CACHE,
DALVIK CACHE,
FACTORY RESET,
INTERNAL STORAGE,
FORMAT DATA
Only other 2 options are SYSTEM & EXTERNAL STORAGE