[Q] Help, can't install any rom (fully) - Asus Transformer TF700

Won't bore you with all the details...
Was unhappy on TWRP 2.5 with Chromi 4.6.7
I knew that you had to install CWM to go to Cyanogenmod, but I couldn't get clockworkmod to let me change the recovery option even after I downloaded a compatible tf700 .img file.
So I got fearless (read stupid) and just used TWRP to install Cyanogenmod.
It worked, but not completely, I have no Play Store, many apps missing. Browser is working, wifi is up, but it never asks me for my google account, and I can't finish installing apps (in particular I wan't to install RomManager so I can try to get CWM installed).
Going back to Stock or Chromi doesn't seem to work. It says "Successful" but it won't boot, I get to an animation which just spins eternally.
Bob Graham

Well, it's probably the details that will matter... as in: which steps you exactly took to get into this mess...
ASFAIK TWRP is totally fine with CM roms, but did you do a clean install, a full wipe when going from CromiX to CM and then again back?
Also, it sounds as if you did not flash the GAPPS package after you flashed the CM rom.
I would suggest you flash back to CM, flash the GAPPS package and see if you can boot.
Good luck....
Sent from my ASUS Transformer Pad TF700T using Tapatalk HD

Having no Play Store does signal to me you might have forgotten to flash the GAPPS package.

rvgraham said:
Won't bore you with all the details...
.
Bob Graham
Click to expand...
Click to collapse
You're both right. Got help from moderator on CM forum and got everything working.
Thank you.

Related

[Q] question about aokp install

Hi, i have a question about the install, it is said the latest recovery is needed.
I experimented some troubles on my transformers, my recovery was blocked, but i found a post here to install another. So i was able to install ics by recovery.
That is nice but i want the aokp rom, i tried on my sgs and i would like to have on my tf. I'm ok with the flash, i did 200 times on the 3 sgs at home, so i'm not new to this.
The recovery i now have on my tf is the rogue XM recovery 1.3.0 (CWM-based Recovery v5.0.2.7)
can i use this recovery to flash the aokp or do i need to update to another recovery, if yes, plz tell me how to do.
Thx
http://goo-inside.me/devs/aokp/tf101/aokp_tf101_milestone-6.zip
Direct link.
http://aokp.co/index.php/releases/_/milestone-6-r27
Release page.
Just flash the .zip file in CWM, no need to use AROMA or other fancy stuff.
Thx, that worked for the install, got a bootloop, but after a wipe and flash again, it worked.
But now, another problem, i'm in france, my dock is phisically in azerty, but when used, it is in qwerty.
Edit : i found the option, so no more problem with dock, i can enjoy the aokp as i did on my sgs.
ulstar said:
Thx, that worked for the install, got a bootloop, but after a wipe and flash again, it worked.
But now, another problem, i'm in france, my dock is phisically in azerty, but when used, it is in qwerty.
Edit : i found the option, so no more problem with dock, i can enjoy the aokp as i did on my sgs.
Click to expand...
Click to collapse
and what about installing guevor's kernel v22.6 on aokp milestone 6? after reboot nothing changes, and can't install gapps too. tried with several recovery versions, cwm, touch and rogue.

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.

[Q] Installing Any New ROM, No Boot, Stuck in Standard ROM FOREVER

I hate myself, for I am a noob.
Actually, I have just never posted because someone else has always posted the issue and fix for my problems, but this one make me want to paint the walls with my brains.
Obviously I have an Asus TF300T, and I have successfully unlocked and installed a custom recovery. I have TWRP 2.5.0.0 because apparently ClockWorkMod does not like the Asus 4.2 bootloader.
So I have the TWRP 2.5.0.0 Custom Recovery and Asus Stock Android 4.2.1, and every time that I install a new ROM and reboot I get stuck in the "Asus" window, the window it shows right before it loads the oparating system. So it tells me that it cannot read or there is no operating system found. I am doing a wipe Dalvik Cache, System, Cache, and Data before I do the install of the new ROM, but it never gets to the new operating system.
I am wanting to get to CyanogenMod, and I have tried all versions of if with the same result. I have also tried AOKP and Baked Bean and I still get the same thing.
So I found another post earlier and they suggested there was an issue with the Asus 4.2 BootLoader, and I was excited because I was sure that was the problem all along! ... Not...
So I was able to get the .zip of the Asus Stock Android 4.1.1, and I was able to get into TWRP and install that. Magically, that worked and I am now on Asus Stock Android 4.1.1, which to my understanding should mean I have the Asus 4.1 Boodloader. Since the OS Version changed, I also had to change the version of TRWP. It is still TWRP 2.5.0.0, but for Asus 4.1. So I install a new ROM and I get the same exact issue as before...
At this point, I have no idea. I feel ashamed to have to post a question and ask, but does anyone have any ideas what else I might be able to try? Or it looks like I am stuck with the default version of Android and I should have never unlocked it.
Thank you!
Mostly Fixed
I was able to finally get to CM 10.1, but only after I installed Asus 4.1 Boot loader.
But all versions of CM 10.2 just get to the ASUS menu and it flashes and goes back to that screen every 45 seconds. Any ideas, or I suppose I should go to a CM forum at that point?
JEYoung4545 said:
I was able to finally get to CM 10.1, but only after I installed Asus 4.1 Boot loader.
But all versions of CM 10.2 just get to the ASUS menu and it flashes and goes back to that screen every 45 seconds. Any ideas, or I suppose I should go to a CM forum at that point?
Click to expand...
Click to collapse
If you itch so much to install CM 10.2 on your tab, the dedicated thread in development recommends that you run it with 4.2 bootloader. Give it a try to see if it solves your problem.
if you want to run cm10.2 just upgrade to latest stock, flash twrp2.6.0.1/ 2.6.0.0 and flash cm10.2.
cheers
Buster
Sent from my GT-I9505 using XDA Premium 4 mobile app

[Q] Stuck on boot animation Cromi X 5.2.2 Help

So finally took the plunge and flashed Cromi-X 5,2,2. Current set up is bootloader 10.8, TWRP 2.5.0 unlocked and rooted. I was running fine for a couple of days and decided to try cromi control to turn of a couple of notifications.I didnt reboot from cromi control as I read there was a bug. I powered off using the power button and when powering back on I was stuck on boot animation. Options I chose on the original flash was _thatv4 10.8 with defaults. No ET / OV / OC / No tweaks. So i decided to dirty flash 5.2.2 again without formating data I got to upgrading apps and when it rebooted, back stuck on animation. I am going to try flashing my original stock asus nandroid.prior to 5.2.2 just to get it working for the evening.
Doing a search of the thread now... See this has been covered on 5.2.1. I may have to wipe / format data IDK
Any suggestions?
Thanks
Update
Restored my nandroid and back up and running.. Guess I have some reading to do.
Would updating to 8.10 and latest TWRP help any? Maybe try that and use _thatv7 next go around.
GPWILL said:
Restored my nandroid and back up and running.. Guess I have some reading to do.
Would updating to 8.10 and latest TWRP help any? Maybe try that and use _thatv7 next go around.
Click to expand...
Click to collapse
It is always good to have the latest bootloader and TWRP. What is your firmware or bootloader now? What do you want to achieve or usage on your device? _that v7 on Cromi X is a nice combo with speed and stability...
GPWILL said:
Restored my nandroid and back up and running.. Guess I have some reading to do.
Would updating to 8.10 and latest TWRP help any? Maybe try that and use _thatv7 next go around.
Click to expand...
Click to collapse
Glad you got it working again. It's strange - what happened is typical for rebooting from the Cromi app, but you didn't.....
Did you do a factory wipe in TWRP before installing CROMi-X?
Also, it certainly wouldn't hurt to update your recovery. Just flash the bootloader/TWRP package in the CROMi-X OP and reboot to system.
My current working is 10.6.1.14.8 from ASUS and TWRP 2.5.0. I did a factory wipe in TWRP before flashing Cromi 5.2.2. Everything went smooth. I let google restore my apps when running thru the setup wizard. A little painful but only took 30 minor so. I didnt restore any apps or data from my TB. So I let it run for a couple of days with no issues. I ran into trouble with the chromi control. Wanted to get rid of that annoying external card notification. Powered off using the power button and boom. Things went south. I am not a overclock / tweak poweruser. Just wanted a little tweak since it looks like ASUS is not going to update anymore. My tab is a little over a year old and my only complaints have been browser lag and the painful lag of using the tablet when apps updates. My intent is to get 5.2.2. Run thru set up / installer a couple of times so I could get use the installer and then at some point venture into rom2sd or data2sd. Next go around I will get 5.2.2 working and nandroid that. I had tried B2R and it works ok. But with 5.2.2 it seems to give the tab a big 'push'. The browser worked way faster. I tried both stock and Chrome with 5.2.2 and was nice and smooth..
Thanks for the responses. If you think of anything else I appreciate it. Been on this forum for awhile and you guys are great!
GPWILL said:
My current working is 10.6.1.14.8 from ASUS and TWRP 2.5.0. I did a factory wipe in TWRP before flashing Cromi 5.2.2. Everything went smooth. I let google restore my apps when running thru the setup wizard. A little painful but only took 30 minor so. I didnt restore any apps or data from my TB. So I let it run for a couple of days with no issues. I ran into trouble with the chromi control. Wanted to get rid of that annoying external card notification. Powered off using the power button and boom. Things went south. I am not a overclock / tweak poweruser. Just wanted a little tweak since it looks like ASUS is not going to update anymore. My tab is a little over a year old and my only complaints have been browser lag and the painful lag of using the tablet when apps updates. My intent is to get 5.2.2. Run thru set up / installer a couple of times so I could get use the installer and then at some point venture into rom2sd or data2sd. Next go around I will get 5.2.2 working and nandroid that. I had tried B2R and it works ok. But with 5.2.2 it seems to give the tab a big 'push'. The browser worked way faster. I tried both stock and Chrome with 5.2.2 and was nice and smooth..
Thanks for the responses. If you think of anything else I appreciate it. Been on this forum for awhile and you guys are great!
Click to expand...
Click to collapse
With your current firmware, 10.6.1.14.8, you should have the latest bootloader but you still need to update your TWRP to a later version, 2.6.1.0 or 2.6.3.0.. You need to pick one. I am still using 2.6.1.0 and it works fine at the moment and no plan to update to 2.6.3.0. I am very sure that you know how to update your custom recovery, TWRP,
If I am not mistaken, you have the old backup but not the 5.2.2 backup before it crashed... It is always a good idea to backup your good working current setup so you can go back or restore if something is going wrong.. One more thing about backup, it would be nice if you can keep your backup and personal stuff on your External SD, Not the internal SD...
Rom and kernel selections: Cromi v5.2.2 is the latest and the fastest in my opinion so it is your first choice unless you something else in mind.. You only have a few selections on kernel and they are all good and serve with a different purposes. sbdags is very closed to stock with a minimal modifications. _that v7 is the latest and more modifications comparing to sbdags. However, it is faster and more stable or most stable of all according to testers and users... Hund's kernel is the fastest of all with even more modifications and options for users to change settings. Testers and users report back with a little less stable comparing to _that but I don't have a single problem with this kernel... However, it is running a little warmer than sbdags and _that because it is running with higher frequency...Max kernel is another option but it seems like there is no supports at the moment. No one knows where he is, haha... Hopefully, we can hear back from him again...
Installation: Totally clean installing because you are already having issue...
1. Backup anything that you want to save including your personal data and files
2. Copy cromi and kernel that you want to install to your External SD because you want to format your data partition
3. Format your data partition and I mean Format, not wipe.
4. Wipe everything on your device including your system but not your external SD..
5. Install cromi and kernel of your choices
6. Reboot and let it sits for a few minutes, then you can do your setup from the setup wizard
7. Go back to your TWRP and do a nandroid backup to your External SD, just in case so you restore it
8. Install your apps or whatever you want from the google store, not from your TB so you can have a good and stable backup
9. After you are done with all the apps and games installation, you may want to do another backup in the TWRP
10. Now you can do whatever you want from this point and if you have more settings to do, you may want to do another backup as a Final backup and a good working one... You can delete the other backup from the previous if you have the final and working backup. You just need one good working backup..That is it..
You can always go back to TWRP to restore just your data or just a system or a whole backup. Those are the options that you can restore and good luck...:fingers-crossed:
LetMeKnow said:
With your current firmware, 10.6.1.14.8, you should have the latest bootloader but you still need to update your TWRP to a later version, 2.6.1.0 or 2.6.3.0.. You need to pick one. I am still using 2.6.1.0 and it works fine at the moment and no plan to update to 2.6.3.0. I am very sure that you know how to update your custom recovery, TWRP,
If I am not mistaken, you have the old backup but not the 5.2.2 backup before it crashed... It is always a good idea to backup your good working current setup so you can go back or restore if something is going wrong.. One more thing about backup, it would be nice if you can keep your backup and personal stuff on your External SD, Not the internal SD...
Rom and kernel selections: Cromi v5.2.2 is the latest and the fastest in my opinion so it is your first choice unless you something else in mind.. You only have a few selections on kernel and they are all good and serve with a different purposes. sbdags is very closed to stock with a minimal modifications. _that v7 is the latest and more modifications comparing to sbdags. However, it is faster and more stable or most stable of all according to testers and users... Hund's kernel is the fastest of all with even more modifications and options for users to change settings. Testers and users report back with a little less stable comparing to _that but I don't have a single problem with this kernel... However, it is running a little warmer than sbdags and _that because it is running with higher frequency...Max kernel is another option but it seems like there is no supports at the moment. No one knows where he is, haha... Hopefully, we can hear back from him again...
Installation: Totally clean installing because you are already having issue...
1. Backup anything that you want to save including your personal data and files
2. Copy cromi and kernel that you want to install to your External SD because you want to format your data partition
3. Format your data partition and I mean Format, not wipe.
4. Wipe everything on your device including your system but not your external SD..
5. Install cromi and kernel of your choices
6. Reboot and let it sits for a few minutes, then you can do your setup from the setup wizard
7. Go back to your TWRP and do a nandroid backup to your External SD, just in case so you restore it
8. Install your apps or whatever you want from the google store, not from your TB so you can have a good and stable backup
9. After you are done with all the apps and games installation, you may want to do another backup in the TWRP
10. Now you can do whatever you want from this point and if you have more settings to do, you may want to do another backup as a Final backup and a good working one... You can delete the other backup from the previous if you have the final and working backup. You just need one good working backup..That is it..
You can always go back to TWRP to restore just your data or just a system or a whole backup. Those are the options that you can restore and good luck...:fingers-crossed:
Click to expand...
Click to collapse
Been awhile since I played with fastboot. Can I just flash the bootloader and twrp zip from the 5.2.2 Cromi thread and be ok? I know to flash this first and reboot into rom before flashing 5.2.2 again. Otherwise I will get fastboot going again.
"10.6.1.14.10 US Bootloader and TWRP 2.6.1.0 DOWNLOAD 1" This is in scenario 2 which doesnt really apply because I dont have a custom rom installed yet at this point.
I am saving these notes for future reference. Thanks for the time in writing these up.
GPWILL said:
Been awhile since I played with fastboot. Can I just flash the bootloader and twrp zip from the 5.2.2 Cromi thread and be ok? I know to flash this first and reboot into rom before flashing 5.2.2 again. Otherwise I will get fastboot going again.
"10.6.1.14.10 US Bootloader and TWRP 2.6.1.0 DOWNLOAD 1" This is in scenario 2 which doesnt really apply because I dont have a custom rom installed yet at this point.
I am saving these notes for future reference. Thanks for the time in writing these up.
Click to expand...
Click to collapse
I think that it would fine since you are running TWRP 2.5. Please be careful when you install custom recovery and bootloader. If you make a mistake, it could brick your device, just my two cents.. Please ask a lot of questions to be sure...
Note: From your TWRP 2.5, install 10.6.1.14.10 first and reboot so the blob can update your bootloader. When it boots into the system, then you need to reboot it back into your TWRP 2.5 and install the TWRP 2.6.1.0. When it is done, then you need to shut it down and use your power button and volume down to boot back into your new TWRP...Good luck..:fingers-crossed:
Always check your download "MD5 Sum" to verify that you have a good download....
You have my attention now and I will take your offer to ask questions. So if I understand correctly the bootloader and twrp zip from above will allow to flash them individually? In twrp point to the zip and it gives you options to flash the bootloader without twrp? I would do this:
1. boot into twrp and choose install.
2. choose zip from above
3. choose bootloader only?
4. reboot into rom. let it sit for a few.
5 reboot into twrp
6 choose new twrp?
7 reboot into rom.
Just trying to be clear so no brick...
I would upgrade in goomanager. Thats how I got twrp to begin with. But I have read it doesnt work anymore?
GPWILL said:
You have my attention now and I will take your offer to ask questions. So if I understand correctly the bootloader and twrp zip from above will allow to flash them individually? In twrp point to the zip and it gives you options to flash the bootloader without twrp? I would do this:
1. boot into twrp and choose install.
2. choose zip from above
3. choose bootloader only?
4. reboot into rom. let it sit for a few.
5 reboot into twrp
6 choose new twrp?
7 reboot into rom.
Just trying to be clear so no brick...
I would upgrade in goomanager. Thats how I got twrp to begin with. But I have read it doesnt work anymore?
Click to expand...
Click to collapse
I never use the method from cromi thread but I trust sbdags as a great developer and so many users used this method without a problem...
If you are still running stock firmware version 10.6.1.14.8, then you still can use goomanager to update your TWRP... If you prefer it that way, then goo still works for you...If you are on stock version 10.6.1.14.8, you are already on the latest bootloader unless you want the latest stock firmware V14.10 which you will update it with Cromi any way...
1. Use goo to update the correct TWRP, 2.6.3.0 or 2.6.1.0
2. Boot into your new TWRP and install the Cromi and follow the instructions that I wrote earlier
Good luck..:fingers-crossed:
GPWILL said:
You have my attention now and I will take your offer to ask questions. So if I understand correctly the bootloader and twrp zip from above will allow to flash them individually? In twrp point to the zip and it gives you options to flash the bootloader without twrp? I would do this:
1. boot into twrp and choose install.
2. choose zip from above
3. choose bootloader only?
4. reboot into rom. let it sit for a few.
5 reboot into twrp
6 choose new twrp?
7 reboot into rom.
Just trying to be clear so no brick...
I would upgrade in goomanager. Thats how I got twrp to begin with. But I have read it doesnt work anymore?
Click to expand...
Click to collapse
Not quite.
You cannot flash BL or TWRP separately from that package. It's either both or none.
But flashing the package would be the easiest and safest method to get you on a current recovery in my opinion.
GooManager: For a few weeks now Goo did not support flashing recoveries anymore. I've read it often enough that I consider that information confirmed - although I have not tested it myself.
Now - just yesterday I read a post where a user reported that Goo got an update and he flashed TWRP successfully. That's one report I know of - if you want to give it a try, go for it. It can't hurt.
The thing is, to use GooManager you have to root the stock rom you are running.
I don't know if the stock rom you are running is rooted, but why bother if you can just flash sbdags package??
Sounds like choosing _thatv7 from the 5.2.2 also upgrades the bootloader also to 10? I assumed you needed the correct bootloader already installed.
I will give goo a go and see what happens.
GPWILL said:
Sounds like choosing _thatv7 from the 5.2.2 also upgrades the bootloader also to 10? I assumed you needed the correct bootloader already installed.
I will give goo a go and see what happens.
Click to expand...
Click to collapse
Well goomanager didnt work for me. Just sits on "downloading" forever. only option was to upgrade to 2.6.3.1
Off to get fastboot working..
GPWILL said:
Sounds like choosing _thatv7 from the 5.2.2 also upgrades the bootloader also to 10? I assumed you needed the correct bootloader already installed.
I will give goo a go and see what happens.
Click to expand...
Click to collapse
_thatv7 is one of the kernel choices - changing a kernel does not do anything to the bootloader.
Look at these elements of the system as parts of an engine: If the bootloader is the starter motor, the kernel may be the distributor.....
Thanks for trying Goo, the score is 1:1
Anyway, to get fastboot working is worth the effort. It's great for troubleshooting or pulling logs and such. It's very helpful to have a working fastboot connection BEFORE you run into some trouble and really need it to work
I guess my question is if I choose _thatv7 will bootloader .8 work? The 10 after the kernel choice is what has put me down this road.
fastboot and adb working. So getting there albeit slowly.
This thread really helped a lot in my learning process..
http://forum.xda-developers.com/showthread.php?t=2546420&highlight=flash+10+6+1+14+10+fastboot
Thanks again for all the info and help.
GPWILL said:
I guess my question is if I choose _thatv7 will bootloader .8 work? The 10 after the kernel choice is what has put me down this road.
fastboot and adb working. So getting there albeit slowly.
This thread really helped a lot in my learning process..
http://forum.xda-developers.com/showthread.php?t=2546420&highlight=flash+10+6+1+14+10+fastboot
Thanks again for all the info and help.
Click to expand...
Click to collapse
There's hardly anything different between the. 8 and . 10 bootloader. V7 works fine with either.
Sent from my DROID4 using Tapatalk
berndblb said:
There's hardly anything different between the. 8 and . 10 bootloader. V7 works fine with either.
Sent from my DROID4 using Tapatalk
Click to expand...
Click to collapse
Update:
Updated TWRP to 2.6.1
fastboot and adb working
Flashed 5.2.2 Cromi-X _thatv7 this time around. (used the advice from above)
Set up apps
I will def nandroid this working config..
All good now.
Thanks to everyone!
FYI I updated goomanager and tried it again on my old setup and it still did not work updating twrp. Stuck on downloading app...
GPWILL said:
Update:
Updated TWRP to 2.6.1
fastboot and adb working
Flashed 5.2.2 Cromi-X _thatv7 this time around. (used the advice from above)
Set up apps
I will def nandroid this working config..
All good now.
Thanks to everyone!
FYI I updated goomanager and tried it again on my old setup and it still did not work updating twrp. Stuck on downloading app...
Click to expand...
Click to collapse
Fastboot is a prefer method to use...:good: I always use fastboot for this stuff. It is fast and easy without any hassle...
How is it running? It should be running very reasonable speed and smoothness...
LetMeKnow said:
Fastboot is a prefer method to use...:good: I always use fastboot for this stuff. It is fast and easy without any hassle...
How is it running? It should be running very reasonable speed and smoothness...
Click to expand...
Click to collapse
It is running pretty nice. Stock browser and Chrome are a little faster than my stock setup with B2R. I have had a few " laucher has stopped" errors. This happened before I installed any apps with thatV7. Didnt get a single laucher error before on thatv4. Stock laucher. Nice and smooth on apps and such. Both stock browser and chrome are faster but not anything like "WOW". Just a little better. Nice to have it built in. I am going to give this a few more days and see if the laucher errors settle down. If it stablizes I will get another nandroid of it and try the ROM2SD to see if I can get the wow factor going.

[Q] Return to stock issue

I am selling my TF700 and wanted to return to stock before selling it(currently have chromi-x 5.3). I downloaded the 4.2.1 stock rom from the Asus website, unzipped, copied the rom zip to the sd card of the tablet. Rebooted to TWRP and installed the zip. Everything seemed to install fine. The tablet rebooted and the lock screen came up. But when I swipe to unlock, I get a 'Unfortunately, Launcher has stopped' message. I can hit Ok, but the message just keeps repeating. Any help would be greatly appreciated.
keeferb said:
I am selling my TF700 and wanted to return to stock before selling it(currently have chromi-x 5.3). I downloaded the 4.2.1 stock rom from the Asus website, unzipped, copied the rom zip to the sd card of the tablet. Rebooted to TWRP and installed the zip. Everything seemed to install fine. The tablet rebooted and the lock screen came up. But when I swipe to unlock, I get a 'Unfortunately, Launcher has stopped' message. I can hit Ok, but the message just keeps repeating. Any help would be greatly appreciated.
Click to expand...
Click to collapse
Make sure you wipe data first in TWRP?
But you'll have to install TWRP again to do that
Personally I would have just left CROMI-X on it - better customer service
sbdags said:
Make sure you wipe data first in TWRP?
But you'll have to install TWRP again to do that
Personally I would have just left CROMI-X on it - better customer service
Click to expand...
Click to collapse
Thanks for the quick response. And you're right, I should have just left it alone and sold it as is.
Any advice on how to get TWRP re-installed? I believe the first time around I did it by installing GooManager from the Play Store. Since I can't get there that option won't work.
keeferb said:
Thanks for the quick response. And you're right, I should have just left it alone and sold it as is.
Any advice on how to get TWRP re-installed? I believe the first time around I did it by installing GooManager from the Play Store. Since I can't get there that option won't work.
Click to expand...
Click to collapse
You'll have to install it over fastboot - the instructions are in the TWRP thread in the dev section
keeferb said:
I am selling my TF700 and wanted to return to stock before selling it(currently have chromi-x 5.3). I downloaded the 4.2.1 stock rom from the Asus website, unzipped, copied the rom zip to the sd card of the tablet. Rebooted to TWRP and installed the zip. Everything seemed to install fine. The tablet rebooted and the lock screen came up. But when I swipe to unlock, I get a 'Unfortunately, Launcher has stopped' message. I can hit Ok, but the message just keeps repeating. Any help would be greatly appreciated.
Click to expand...
Click to collapse
I assume you downloaded the correct SKU since you did everything else correct.
My guess is: a bad flash.
Try booting into recovery. If you get the dead Android, the stock recovery installed fine. If you have the Asus firmware on your microSD, rename it to EP201_768_SDUPDATE.zip and boot into recovery. It should recognize the file and flash it.
Alternatively, you could flash TWRP in fastboot and flash the firmware again.
Side note: I will never understand why people flash the tablet back to the lousy stock rom to sell it.... Anybody doing the least bit of research should know that this tablet with CROMi-X installed is 10x better - that actually only custom ROMing makes it useable.....
I would offer it here on the XDA market as: "TF700 in mint condition with a clean installation of any bootloader/recovery/kernel/rom you desire"
I re-installed TWRP via fastboot, formatted data, and reflashed stock. Worked this time. Thanks for your help.

Categories

Resources