Database Info

[Q] New (virgin/stock) TF700 to CROMI 3.2 - is this right?

Hi there, been loitering on the sidelines for a while, reading many many threads and now ready to leap in. I have bought a TF700 Infinity and want to get it fully modded, enhanced, streamlined and dripping in XDA goodness. I want to know if the things I have planned are a) in the correct order, b) are the correct/most suitable methods and c) are inadvisable or unecessary for any reason.
Root the device
- Using the DebugFS method (details HERE and HERE).
Unlock Bootloader
- Using the ADB tool from blackmambazzz
- If the ADB tool doesn't work then I'll use the download from the Asus website
Install recovery (TWRP)
- I will try using GooManager first (hence the reason to root)
- If GooManager doesn't work then I will try the ADB tool again (option 1)
- If I get problems with the latest version I will try TWRP v2.3.1.0 (as some people have reported that this could be better)
Flash JB bootloader
- Boot into recovery (as per the instructions in the All-In-One Guide For Asus Infinity post)
- Flash the 10.4.4.25 JB bootloader found in this post
Flash ROM (CROMi 3.2)
- Using the downloads from the CleanROM Inheritance 3.2 post, flash CleanROM Inheritance and choose my options through the Aroma installer
Flash stock kernel (by _that)
- Use TWRP to flash the stock kernel through the CROMi installer v1.6 found in the CleanROM Inheritance 3.2 post
Hopefully that will get me from out of the box virgin TF700 to a fully charged awesome tablet/laptop that is smooth and powerful. Hopefully I've done my research and got it right but please let me know if there is anything incorrect. Thanks!

The procedure depends which firmware is installed your new TF700.
If 9.4.5.26 or earlier: Do not install ANY updates before you read the [BRICKPROOF] thread in the dev forum about nvflash, then decide on further steps.
If 10.4.4.x: You can't root this version directly. Either you downgrade to 9.4.5.30 first, or you simply unlock directly and continue with installing TWRP via fastboot.
Also, when you install CROMI, you can directly select the modified stock kernel, it's not a separate step.

hello! i am stuck in a point installing CROMI.
I have unlocked tf700 and installed cmw recovery.
every thing is fine.
i have put the zip file with CROMI in the internal memory but cwm is not seeing it.
it says also can't mount mmc when i try to look for the files inside...
where am i wrong?
thanks!

marci4na said:
hello! i am stuck in a point installing CROMI.
I have unlocked tf700 and installed cmw recovery.
every thing is fine.
i have put the zip file with CROMI in the internal memory but cwm is not seeing it.
it says also can't mount mmc when i try to look for the files inside...
where am i wrong?
thanks!
Click to expand...
Click to collapse
Try power off your device, wait a few seconds, then boot back into cwm see if that helped!

If all else fails I would switch over to TWRP I prefer it way more then cwm.

_that said:
The procedure depends which firmware is installed your new TF700.
If 9.4.5.26 or earlier: Do not install ANY updates before you read the [BRICKPROOF] thread in the dev forum about nvflash, then decide on further steps.
If 10.4.4.x: You can't root this version directly. Either you downgrade to 9.4.5.30 first, or you simply unlock directly and continue with installing TWRP via fastboot.
Also, when you install CROMI, you can directly select the modified stock kernel, it's not a separate step.
Click to expand...
Click to collapse
Thanks _that, your work on the stock kernel is most appreciated and I can't wait to experience the fruits of your hard work. My confusion with needing to apply it afterwards was that your kernel was included in the 3.2.1 of CROMi last night (24th Jan). At the time of the post it was still a post-ROM activity.
I should get the TF700 today so will check out the firmware version. Initially I was confused about the 9.4 / 10.4 version numbers on the forums but I think that this refers to the 'Build Number' in Menu > Settings > About Tablet menu. Assuming the tablet is on 10.4.4.x, my plan is to:
Unlock using ADB tool or Asus unlock app
Install TWRP recovery using ADB tool (if this does not work, root and use GooManager)
Flash CROMi from TWRP using Aroma installer to select the _that stock kernel and browser2ram
Allow to settle for 5-10 minutes
Enjoy
I'm not including the root step as I understand that CROMi is pre-rooted.

mrlee1980 said:
My confusion with needing to apply it afterwards was that your kernel was included in the 3.2.1 of CROMi last night (24th Jan). At the time of the post it was still a post-ROM activity.
Click to expand...
Click to collapse
3.2 already contained "my" kernel, 3.2.1 contains the nodpi variant.
mrlee1980 said:
I should get the TF700 today so will check out the firmware version. Initially I was confused about the 9.4 / 10.4 version numbers on the forums but I think that this refers to the 'Build Number' in Menu > Settings > About Tablet menu.
Click to expand...
Click to collapse
Correct.
mrlee1980 said:
Assuming the tablet is on 10.4.4.x, my plan is to:
Unlock using ADB tool or Asus unlock app
Install TWRP recovery using ADB tool (if this does not work, root and use GooManager)
Flash CROMi from TWRP using Aroma installer to select the _that stock kernel and browser2ram
Allow to settle for 5-10 minutes
Enjoy
I'm not including the root step as I understand that CROMi is pre-rooted.
Click to expand...
Click to collapse
Looks good. Note that the ADB tool has no error handling. If it does not work, it makes sense to invest some time to get adb and fastboot working on your PC, it is always helpful.
If you don't have any apps installed yet, you don't even need to let it settle - just don't expect absolute smoothness in the first minute, while it's still doing some background stuff.

OK, having fun with this. The TF700 arrived with 4.1.1 and boot loader 10.4.4.16, so I unlocked (pushed unlock APK to tablet through the ADB tool v6) and installed TWRP 2.3.3.0 through the ADB tool. I backed up and then flashed CROMi 3.2.1 ODEX and got through the entire process 'successfully' and rebooted.
Then nothing. I got stuck at the "Android is updating" / "Finishing boot" screen for 20 minutes. Got nervous, searched the forums and found that while some people see the screen for 5 secs, there was one person who hit the problem and a reboot sorted it out. Tried a few reboots but to no avail (battery depleting all the time) and I tried reflashing the ODEX version 3 more times but got stuck at the same point each time.
I reverted to my backup and tried to flash the JB bootloader ZIP (in case it was the 10.4.4.16 bootloader) from TWRP but couldn't get it working. The ZIP would appear to load successfully, I rebooted into Android and selected the firmware update option in the notifications area. I selected 'Install' at the pop-up and the tablet rebooted but no change to the bootloader when I checked in settings.
In the end I flashed the DEODEX version and this seemed to work. I'll try again with the ODEX (MD5 checked out OK) later.

mrlee1980 said:
OK, having fun with this. The TF700 arrived with 4.1.1 and boot loader 10.4.4.16, so I unlocked (pushed unlock APK to tablet through the ADB tool v6) and installed TWRP 2.3.3.0 through the ADB tool. I backed up and then flashed CROMi 3.2.1 ODEX and got through the entire process 'successfully' and rebooted.
Then nothing. I got stuck at the "Android is updating" / "Finishing boot" screen for 20 minutes. Got nervous, searched the forums and found that while some people see the screen for 5 secs, there was one person who hit the problem and a reboot sorted it out. Tried a few reboots but to no avail (battery depleting all the time) and I tried reflashing the ODEX version 3 more times but got stuck at the same point each time.
I reverted to my backup and tried to flash the JB bootloader ZIP (in case it was the 10.4.4.16 bootloader) from TWRP but couldn't get it working. The ZIP would appear to load successfully, I rebooted into Android and selected the firmware update option in the notifications area. I selected 'Install' at the pop-up and the tablet rebooted but no change to the bootloader when I checked in settings.
In the end I flashed the DEODEX version and this seemed to work. I'll try again with the ODEX (MD5 checked out OK) later.
Click to expand...
Click to collapse
Have you tried to flash .25 JB bootloader and reflash cromi ODEX 3.2.1 with _that stock no dpi kernel? make sure wipe cache and dalvik cache first before flashing.

mrlee1980 said:
I reverted to my backup and tried to flash the JB bootloader ZIP (in case it was the 10.4.4.16 bootloader) from TWRP but couldn't get it working. The ZIP would appear to load successfully, I rebooted into Android and selected the firmware update option in the notifications area. I selected 'Install' at the pop-up and the tablet rebooted but no change to the bootloader when I checked in settings.
Click to expand...
Click to collapse
The settings screen does not show the bootloader version. The bootloader version is only displayed when you hold down Volume-down while powering on - tiny text in the upper left corner while the bootloader menu is shown.

CWM & CM10/10.1 problem (hung on "The device is unlocked")

Hi,
On my TF300T I flashed the CWM 5.5.0.4 using fastboot and installed CM 9.1 with the CWM - boots & works fine
I want to install CM10 or 10.1 (using the steps I found in the CM Wiki) but the TF300T always stops on "The Device is unlocked".
Now I found a new CWM (6.0.2.3, recovery-jb.img) for using with JB here at xda-developers - finally to install CM10 or 10.1.
But after flashing the recovery-jb.img with fastboot I want to boot into recovery mode, but the TF300T stops on "booting recovery kernel image".
A boot into the previous installed CM9.1 is still possible.
How can I upgrade to CM10 or CM10.1?
Thank you for any help!

cyaneo said:
Hi,
On my TF300T I flashed the CWM 5.5.0.4 using fastboot and installed CM 9.1 with the CWM - boots & works fine
I want to install CM10 or 10.1 (using the steps I found in the CM Wiki) but the TF300T always stops on "The Device is unlocked".
Now I found a new CWM (6.0.2.3, recovery-jb.img) for using with JB here at xda-developers - finally to install CM10 or 10.1.
But after flashing the recovery-jb.img with fastboot I want to boot into recovery mode, but the TF300T stops on "booting recovery kernel image".
A boot into the previous installed CM9.1 is still possible.
How can I upgrade to CM10 or CM10.1?
Thank you for any help!
Click to expand...
Click to collapse
What is your bootloader version? Si it fresh enough?

Bootloader...(!)
I was using ww_epad-9.4.3.30-20120604 - so I upgraded to stock ww_epad-user-10.4.2.20 (using CWM 5.5.0.4), after this I flas the recovery-jb.img (6.0.2.3) - now I can boot into CWM 6.0.2.3 recovery and install CM10. :laugh:
Thank you!

cyaneo said:
Bootloader...(!)
I was using ww_epad-9.4.3.30-20120604 - so I upgraded to stock ww_epad-user-10.4.2.20 (using CWM 5.5.0.4), after this I flas the recovery-jb.img (6.0.2.3) - now I can boot into CWM 6.0.2.3 recovery and install CM10. :laugh:
Thank you!
Click to expand...
Click to collapse
Yeap,.. Bloody bootloader
No problem

Sorry for reopening but - I's crazy!
Heres what I've tried (using Bootloader 1.00e (ww_epad-10.4.2.20-20121226 A03):
First flashing cm 6.0.2.3 and install cm10 and also tried the cm10.1 nightly. Installation works without errors, but on reboot the tf300 freeze on "the device is unlocked"
So I try it with twrp (2.4 jb). The installation of cm10 and also cm10.1 failed with the error "assert failed: getprop"
I also cannot mount /data, no matter what I try.
I've wiped data, cache and dalvik cache every time before I try to install one of the ROMs.
At this time I can do nothing with my TF300, only boot to cwm or twrp!
What the heck is wrong?

cyaneo said:
Sorry for reopening but - I's crazy!
Heres what I've tried (using Bootloader 1.00e (ww_epad-10.4.2.20-20121226 A03):
First flashing cm 6.0.2.3 and install cm10 and also tried the cm10.1 nightly. Installation works without errors, but on reboot the tf300 freeze on "the device is unlocked"
So I try it with twrp (2.4 jb). The installation of cm10 and also cm10.1 failed with the error "assert failed: getprop"
I also cannot mount /data, no matter what I try.
I've wiped data, cache and dalvik cache every time before I try to install one of the ROMs.
At this time I can do nothing with my TF300, only boot to cwm or twrp!
What the heck is wrong?
Click to expand...
Click to collapse
But U probably haven't format /system, right? It's another mandatory thing to do when switching roms.
If it fails, using fastboot try to flash system with original blob file (get it from archive of latest official release) - it will fix /data problem - been there, done that
U can also try to install official rom from zip... IF it fails, try fastboot method.
Let system boot, reboot into recovery again and do full wipe with /system format and install newest cm10.1

szulco said:
But U probably haven't format /system, right? It's another mandatory thing to do when switching roms.
If it fails, using fastboot try to flash system with original blob file (get it from archive of latest official release) - it will fix /data problem - been there, done that
U can also try to install official rom from zip... IF it fails, try fastboot method.
Let system boot, reboot into recovery again and do full wipe with /system format and install newest cm10.1
Click to expand...
Click to collapse
- now I formatted data and system and also wiped all possible parts
- flashing cwm 6.0.2.3 and installing asus stock ROM (ww_epad-user-10.4.2.20), reboot
- cannot access cwm recovery, so I reeflash it with fastboot method
- access cwm recovery and install latest 10.1 nightly, reboot, done.
Thank you so much!

I'm having the same issue.
I bought my TF300T when if first came out. I finally decided to play around with it.
I unlocked it with the Google Play app.
Used fastboot to push the latest ASUS JB4.2 firmware (US_V10.6.1.8)
My bootloader says: (1.00 e) released by "US_epad-10.6.1.8-20130225" A03
I rooted and installed TWRP v2.4.4.0
Everything is working fine for me and I have taken a solid backup, so I'm able to restore back to that when things fail.
I loved using CM7 on my phone, so I wanted to try CM10 on my tablet.
I have tried installing the stable CM 10.0, and I've tried all of the CM 10.1 Nightlies.
Every single time, the install goes perfectly fine, but when I reboot I just get the plain white Asus screen and then it freezes.
I have tried installing with and without installing the gapps.
Every time I install I do a Factory Reset, wipe the Cache, Dalvik Cache, and System. The only thing I didn't do is wipe Data as I'd prefer not to lose my files. (is that the problem, is the data-wipe required?)
Is there something obvious that I'm missing or a step I left out?
Any help would be greatly appreciated.

I tried doing it again with wiping all my data too...that didn't make a difference either. Still freezes on the white asus screen.

Hi, I just registered to reply, as seems noone did. And Ive been there myself, also with the 10.6.1.8 bootloader. Thats the issue. Cyanogenmod isnt compatible yet with the newest bootloader 10.6.1.8.
I hope it will in the future, Im awaiting it too. Until then I just rooted the stock rom, and using it that way. You could try the CROMI-X rom, but its also stock based, I havent tried it yet, maybe ill give the newest update a try (4.3) which will be available in a couple of days, as I really love their newest boot animation(wich I believe isnt included in the 4.2 version)
Till then, no Cyanogenmod for us with the newest bootloader.....also downgrading is not worth the risk if you ask me,,, even if its possible. So Ill wait for the Cyanogenmod team to update their version to ours.
Advice: dont mess with the bootloader nor the recovery img files. Always read carefully if you wanna change recovery if its compatible with your bootloader. If its not, and you flash it...tada....youre the owner of a cool and expensive brick. Dont wipe data in the bootloader, cuz as I understood reading posts here at xda, it will wipe your entire device, including bootloader...then your kinda screwed. So stick to what you have and let the devs do their work to update their roms for the 10.6.1.8 bootloader...MOST importantly, DONT store your device with the keyboard dock closed...(like a laptop)...your screen will crack eventually.I gathered this info on youtube as well as here, and Ive a friend, who was using the device with the dock till last month like that, had it from last august...result, screen cracked 3 weeks ago...its a design flaw in the transformers, the screen is under heavy pressure while in the keydock..I just got my dock last week,, Im storing it separately, and I never close it, only use it for typing, battery and usb.
im writing all this as I think I wont find this post again to reply if you read it.

Updating Android 4.1

Hey there, guys. I've been around XDA a while & have messed around with different ROMS. I had found one that I liked (decent battery life is the most important for me) & stuck with ParanoidAndroid 3.60 (4.2 based ROM) for Android 4.1 (I believe the firmware version is 10.4.2.20). TWRP is 2.5.0.0. This was around 1-2 years ago, and I finally decided it was time to upgrade it.
Can anyone point me the direction on where to start? I would like to update to the latest (or most stable) android version, if possible. I have a basic knowledge of fastboot & how it works.:fingers-crossed:

First, you will have to upgrade your bootloader to the latest version to run the latest recovery. I don't know if there's an easier way of doing this, but I'd suggest installing a stock ROM and then unlocking/rooting/installing recovery again.
You can download the latest official firmware from here (assuming you have a TF300T model): http://www.asus.com/Tablets_Mobile/ASUS_Transformer_Pad_TF300T/HelpDesk_Download/
Make sure to select the one with the correct SKU.
Then, follow this guide: http://forum.xda-developers.com/showthread.php?t=1757077
This will wipe all your data so make sure to backup all the files you need.
The bootloader will most likely remain unlocked, so what you need now is root and recovery. There are plenty of guides for those, so find the right one for you. You can download the latest TWRP from here: http://teamw.in/project/twrp2/97
An installation guide is on the same page, but make sure to download the one ending with 4.2 since you will be on the latest firmware version (here's the name of the file you'll probably need if you have a TF300T model: openrecovery-twrp-2.6.3.0-tf300t-4.2.blob).
Hope this will help

Duchman said:
First, you will have to upgrade your bootloader to the latest version to run the latest recovery. I don't know if there's an easier way of doing this, but I'd suggest installing a stock ROM and then unlocking/rooting/installing recovery again.
You can download the latest official firmware from here (assuming you have a TF300T model): http://www.asus.com/Tablets_Mobile/ASUS_Transformer_Pad_TF300T/HelpDesk_Download/
Make sure to select the one with the correct SKU.
Then, follow this guide: http://forum.xda-developers.com/showthread.php?t=1757077
This will wipe all your data so make sure to backup all the files you need.
The bootloader will most likely remain unlocked, so what you need now is root and recovery. There are plenty of guides for those, so find the right one for you. You can download the latest TWRP from here: http://teamw.in/project/twrp2/97
An installation guide is on the same page, but make sure to download the one ending with 4.2 since you will be on the latest firmware version (here's the name of the file you'll probably need if you have a TF300T model: openrecovery-twrp-2.6.3.0-tf300t-4.2.blob).
Hope this will help
Click to expand...
Click to collapse
Thanks for replying! I got it to boot, but it stays stuck on the Asus logo with the loading circle. I installed the correct TWRP recovery. I tried rebooting, but it says no OS installed. Furthermore, it does not mount the External storage. I can browse the files through the file Manager in TWRP.
EDIT: It rebooted & I have everything back. It just took forever to reboot. Thanks for your help!!

boxer3310 said:
Thanks for replying! I got it to boot, but it stays stuck on the Asus logo with the loading circle. I installed the correct TWRP recovery. I tried rebooting, but it says no OS installed. Furthermore, it does not mount the External storage. I can browse the files through the file Manager in TWRP.
EDIT: It rebooted & I have everything back. It just took forever to reboot. Thanks for your help!!
Click to expand...
Click to collapse
I'm glad I was able to help. Could you tell me the order of your actions and what happened after what? I'm a bit confused as to why it'd get stuck like this.
Also, you might need a newer recovery for more recent ROMs. There are both 2.7.0.1 and 2.7.1.0 versions available in the development section.

Duchman said:
I'm glad I was able to help. Could you tell me the order of your actions and what happened after what? I'm a bit confused as to why it'd get stuck like this.
Also, you might need a newer recovery for more recent ROMs. There are both 2.7.0.1 and 2.7.1.0 versions available in the development section.
Click to expand...
Click to collapse
I did everything as you posted:
1. Downloaded the most current firmware for the TF300T from the Asus site.
2. Pushed it to my device using fastboot
3. Installed custom recovery for my version of Android
4. Rebooted.
The Installation bar completed after I pushed the firmware & recovery. It just took long to reboot. I read that you have to let the ROM "stabilize," so I suspect it might have been the cause of the hang. Everything went pretty smooth after the reboot, though. I installed TWRP 2.7.1.0 (as you posted above) and installed a new ROM. Thank you very much for taking the time to reply. I love this update! :victory:

[Q] recovery partition not found

Hello,
First off, I am a total noob and probably should not have been messing with my phone before knowing exactly what I was doing. I have a Nexus 5 that I rooted with towelroot. I had xposed framework installed with some other cool tweaks. I should have stopped there. I followed the tutorial on PhoneArena yesterday titled How to download and install the Android L beta update on your Nexus 5. I downloaded and flashed the modified kernel, the SuperSU mode, and the new radio.
I had a backup kernal and recovery set up through Flashify/TWRP. The flash and installation worked. When I tried to flash the N5_L_PREV_LPV79.zip to the newer N5_L_PREV_LPV81C.zip my phone said "your recovery partition couldn't be found. You won't be able to flash recovery images. You can still flash images. It said the same thing about my boot partition. Is there anything I can do to get these partitions back? I know I shouldn't have been jacking with everything without proper knowledge. I appreciate any help you can give me.
Thank you,
Patrick

[Completed] I think i broke my Nexus 6p. Help Needed!

Hi all, I'm in a bit of a sticky situation and need your help on getting my device back to work.
Here's some information:
Device: Huawei Nexus 6P
OS: Stock with Goodies v M1.a
Unlocked and rooted. (Root access worked fine)
TWRP installed
What I was trying to do that might have broken the phone:
Trying to flash Xposed for Marshmallow
This file : http://dl-1.va.us.xda-developers.co....apk?key=i2lArbjft_pNfvyVk6EeZg&ts=1448991697
What has happened:
Well, TWRP works, fastboot works and the bootloader can be loaded as well. But I can't boot to system. It for some reason gets stuck at the white google splash screen in the boot process.
What I tried to do:
1. restore my TWRP backup after wiping system, data, dalvik and cache - Didn't work
2. Wipe everything and re-flash default rom - Didn't work
3. Flash a custom ROM - Didn't work
4. Used fastboot flash system to flash the official system image - Didn't work (stuck at the same place after boot)
5. Locked the bootloader to try and get TWRP to run the RecoveryScript - Didn't work
Did I hard brick my phone? If not, what should I do? Any required information will be provided upon request. I just don't know what you might want to post it with the OP.
Also, I'm really really sorry if i'm posting in an irrelevant section, or am asking a question that vaguely resembles someone else's. But I really do need your help.
Thanks so much.

Got it fixed.. No thanks to any one of you. Mods can close this this thread or whatever smh