Related
So I left Apple, came to Android, rooted my VZW GS3. First time I've ever done anything like this, so I'm new to it. I backed up EVERYTHING using TiBu, did the IMEI backup, Full system/image backup using CWM, unlocked bootloader, etc. Then I flashed to Synergy r46 (august 20th - yesterday's release).
Now I'm at work and my back-up pulled my contacts via Verizon's server, but how do I get back EVERYTHING else? SMS/MMS logs, call logs, apps, app data, etc? Do I need to download TiBu again (fresh from google market) and then load my backups off my Ext-SD card, or what? I guess I'm a bit confused as to where my TiBu items were even stored/saved...I assume it was the ExtSD card, otherwise I would have lost them all upon flashing to Synergy, correct?
Any help to get all my apps and data back on my newly Synergized phone would be awesome!!!! Thanks in advance!!!
Yes download titanium and then point it to the directory you had your back ups saved to (its sd card by default, and which is your phone storage btw) then tab to backup/restore click the check, then once your app data populates, and select run next to restore apps and data.
Sent from my SCH-I535 using Tapatalk 2
---------- Post added at 02:56 PM ---------- Previous post was at 02:55 PM ----------
And no flashing roms will not wipe all your user data unless you do a complete wipe.
Sent from my SCH-I535 using Tapatalk 2
I used titanuium backup pro to back up all my Apps and system data. And when I flash a new rom I just redownload titanium pro and it automatically restores all my Apps and system data. It is the easiest app I have used. So to answer ur question.....back up ur apps with titanium then after flashing a new rom go and redownload titanium and restore your system data and apps or just apps alone if that's what u prefer? Does that answer ur question or would u like more detailed instructions?
Sent from my SCH-I535 using xda app-developers app
Welcome to android!
Sent from my SCH-I535 using Tapatalk 2
Another very nice feature of Titanium Backup is its ability to pull data from CWM nandroids. There have been a few times where I was quick to flash a new rom without doing a backup of my apps. This has saved me much time from having to re-flash the nandroid backup, backup via TB, then re-flash to the new rom.
voodoomanx said:
And no flashing roms will not wipe all your user data unless you do a complete wipe.
Click to expand...
Click to collapse
This is one thing that scares me...I don't quite understand what's being wiped or how to perform a full wipe. I hope I don't do this on accident on day...When I flashed the ROM, I basically booted into CWM recovery and installed from there....I was unable to install by opening the ROMs ZIP file via ROM Manager. When I tried to install this way, it failed.
Can somebody confirm if I flashed correctly, just to put my worries to rest? Here's how I did it...
I backed everything up, unlocked bootloader, and tried to install Synergy r46 via ROM manager, but I had problem. I had the ZIP for the ROM downloaded to my Ext-SD card, like the installation instructions say. I then opened ROM Manager and went to "install ROM from SD card." The phone rebooted and opened in CWM to install...But kept having problems finding some "path" or something.
So I decide to wing it and rebooted into CWM. I cleared davik cache(sp?), then user data, then navigated to my Ext-SD and selected the ROM ZIP to install. Now, everything seems fine and it says it installed successfully, but I still think I installed in a way that wasn't described.
Is this a legit install and is this how most people flash ROMs, from booting directly into CWM, or should ROM manager have worked for me via "install ROM from SD card???" If so, why didn't ROM Manager work for me?
Rather urgent question: When I restore my items, do I want to click "RESTORE MISSING APPS + ALL SYSTEM DATA?" ill this restore the bloatware that was on my phone prior to flashing????? If so, is there any way around it
Thanks a bunch! Just waiting on an answer to the later questions before I restore.
Weioo said:
This is one thing that scares me...I don't quite understand what's being wiped or how to perform a full wipe. I hope I don't do this on accident on day...When I flashed the ROM, I basically booted into CWM recovery and installed from there....I was unable to install by opening the ROMs ZIP file via ROM Manager. When I tried to install this way, it failed.
Can somebody confirm if I flashed correctly, just to put my worries to rest? Here's how I did it...
I backed everything up, unlocked bootloader, and tried to install Synergy r46 via ROM manager, but I had problem. I had the ZIP for the ROM downloaded to my Ext-SD card, like the installation instructions say. I then opened ROM Manager and went to "install ROM from SD card." The phone rebooted and opened in CWM to install...But kept having problems finding some "path" or something.
So I decide to wing it and rebooted into CWM. I cleared davik cache(sp?), then user data, then navigated to my Ext-SD and selected the ROM ZIP to install. Now, everything seems fine and it says it installed successfully, but I still think I installed in a way that wasn't described.
Is this a legit install and is this how most people flash ROMs, from booting directly into CWM, or should ROM manager have worked for me via "install ROM from SD card???" If so, why didn't ROM Manager work for me?
Rather urgent question: When I restore my items, do I want to click "RESTORE MISSING APPS + ALL SYSTEM DATA?" ill this restore the bloatware that was on my phone prior to flashing????? If so, is there any way around it
Thanks a bunch! Just waiting on an answer to the later questions before I restore.
Click to expand...
Click to collapse
I am wondering if you didn't do the full wipe. If you are using CWM v6.0.1.0 then there is no option labeled "user data" it is "wipe data/factory reset" which is the full wipe like I mentioned.
As far as doing it correctly, as you may have already noticed there is more than one way to do about anything. Personally, I still use CWM v6.0.1.0 and flash the zips there.
P.S. I see you are enjoying your freedom of losing your apples!
Also, tell me how your r46 is working ... I have held off at r23 while they are playing around with kernels and ramdisk tweaks for awhile.
Hi, I'm pretty much in the same boat as the OP coming from an iphone and this is my first android phone. My problem is that all of the synergy roms (r39, 46, 50 and 1.7) I tried were unstable and kept rebooting randomly. I unlocked the boot loader and believe I did everything right. Did I miss a step? I restored back my nandroid after several attempts at Synergy. I like the responsiveness and tweaks of Synergy but I couldn't deal with the random reboots. Sometimes it would just continue in a boot loop too.
dan_joegibbsfan said:
I am wondering if you didn't do the full wipe. If you are using CWM v6.0.1.0 then there is no option labeled "user data" it is "wipe data/factory reset" which is the full wipe like I mentioned.
As far as doing it correctly, as you may have already noticed there is more than one way to do about anything. Personally, I still use CWM v6.0.1.0 and flash the zips there.
P.S. I see you are enjoying your freedom of losing your apples!
Also, tell me how your r46 is working ... I have held off at r23 while they are playing around with kernels and ramdisk tweaks for awhile.
Click to expand...
Click to collapse
I'm fairly certain I did "wipe data/factory reset," I just wasn't sure how it was labeled when I typed that out, but that's really ringing a bell. I think I may have gotten the errors before (using ROM Manager) because I hadn't factory reset? Seems to me I'm good to go! However, my question regarding TiBu still remains.
Edit: In regards to informing you about r46, I'm not sure what to report as I've never used a previous Synergy and have no idea how to compare, other than to the rooted stock ROM. I have heard reports of battery life being worse than the stock ROM, and I can confirm this. I've barely used the phone since I flashed to Synergy and it's dropped 15% battery life in ~3 hours. Seems faster than before but I'm unsure.
nguyenvn said:
Hi, I'm pretty much in the same boat as the OP coming from an iphone and this is my first android phone. My problem is that all of the synergy roms (r39, 46, 50 and 1.7) I tried were unstable and kept rebooting randomly. I unlocked the boot loader and believe I did everything right. Did I miss a step? I restored back my nandroid after several attempts at Synergy. I like the responsiveness and tweaks of Synergy but I couldn't deal with the random reboots. Sometimes it would just continue in a boot loop too.
Click to expand...
Click to collapse
I started getting that sort of behavior so I just restored back to my stock rooted backup and reflashed Synergy 1.7 r23 and then reflashed the theme I'm using. I thought my issues came from other modifications I had tried so I will try to remember to report back to this post tomorrow and tell you if I'm still having those similar issues or if I'm stable again.
dan_joegibbsfan said:
I started getting that sort of behavior so I just restored back to my stock rooted backup and reflashed Synergy 1.7 r23 and then reflashed the theme I'm using. I thought my issues came from other modifications I had tried so I will try to remember to report back to this post tomorrow and tell you if I'm still having those similar issues or if I'm stable again.
Click to expand...
Click to collapse
Was 1.7 r23 supposed to be a really stable release? I read through some of the Synergy thread and didn't see anyone having the issues I had. I felt like I was doing something wrong.
nguyenvn said:
Hi, I'm pretty much in the same boat as the OP coming from an iphone and this is my first android phone. My problem is that all of the synergy roms (r39, 46, 50 and 1.7) I tried were unstable and kept rebooting randomly. I unlocked the boot loader and believe I did everything right. Did I miss a step? I restored back my nandroid after several attempts at Synergy. I like the responsiveness and tweaks of Synergy but I couldn't deal with the random reboots. Sometimes it would just continue in a boot loop too.
Click to expand...
Click to collapse
I have never had a hot boot or boot loop using any version of synergy. I've been running it since 1.3 and flashed last night's rom as well. What method of unlock did you use for the bootloader unlock? Did you see the custom kernel loaded into phone settings?
Sent from my SCH-I535 using Tapatalk 2
voodoomanx said:
I have never had a hot boot or boot loop using any version of synergy. I've been running it since 1.3 and flashed last night's rom as well. What method of unlock did you use for the bootloader unlock? Did you see the custom kernel loaded into phone settings?
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
I used the EZ-unlock app in the play store. I did see that a custom kernel was loaded however when i flashed back to my nandroid (stock rooted) I am back on the orignal kernel. Would the way I rooted have an effect on the reboots? I used the non flash method by Noxious Ninja.
voodoomanx said:
I have never had a hot boot or boot loop using any version of synergy. I've been running it since 1.3 and flashed last night's rom as well. What method of unlock did you use for the bootloader unlock? Did you see the custom kernel loaded into phone settings?
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
I agree I have yet to have Synergy boot loop although I'm still on 1.7. I would try to wipe cache and dalvik cache and see if that helps or you could be over clocking to high.
Sent from my Transformer TF101 using xda premium
nguyenvn said:
Was 1.7 r23 supposed to be a really stable release? I read through some of the Synergy thread and didn't see anyone having the issues I had. I felt like I was doing something wrong.
Click to expand...
Click to collapse
I don't know the answer to that specifically. All I know was that I was stable before another modification I made (that said it wouldn't work but I tried it anyway). Since restoring from backup and reloading Synergy and theme I have not seen any weird rebooting anymore.
nguyenvn said:
Would the way I rooted have an effect on the reboots? I used the non flash method by Noxious Ninja.
Click to expand...
Click to collapse
I'm not familiar with that method. I've only used Odin, even when I did have to redo everything I used Odin to stock de-bloated rooted .md5 then CWM'd from there.
So I'm giving it another shot on r50. I made sure to clear dalvik, cache and data. After flashing It gave me the reboot problems again. I installed system tuner to change the cpu back to 1.5. Maybe it's from the overclock but we'll see how it goes. Is everyone leaving it overclocked on 1.9 not having issues?
nguyenvn said:
So I'm giving it another shot on r50. I made sure to clear dalvik, cache and data. After flashing It gave me the reboot problems again. I installed system tuner to change the cpu back to 1.5. Maybe it's from the overclock but we'll see how it goes. Is everyone leaving it overclocked on 1.9 not having issues?
Click to expand...
Click to collapse
That may very well be the issue. 1.9ghz is a very aggressive overclock, and i wouldn't be surprised if was unstable on a good number of phones. Synergy's supposed to boot at 1.5ghz max by default - I don't know whether that was successfully implemented. I personally think it's silly to OC such a capable phone, anyway. Back in the days of the Droid 1, an overclock from the stock 550mhz to 800mhz-900mhz was an enormous improvement. Today, the only thing OCing the S3 gets you is a <10% improvement in Quadrant, more heat, possible instability, and no perceptible difference outside of those silly synthetic benchmarks.
Anyway, in this thread, there seems to be a fair bit of confusion as far as what's what in the android partitions. I'll give you a short rundown.
"aboot" is what's referred to here as the bootloader. It checks to see whether the next partition in the boot sequence, "boot", is authorized. When you unlocked your bootloader, you overwrote aboot with a version that does not perform that check.
"boot" contains your kernel. If your ROM has a custom kernel, it contains a boot.img to overwrite boot.
"system" is the meat of the OS. This is primarily what ROMs flash.
"data" contains all of your apps and settings. When you perform a factory reset, you're reformatting data. If you're flashing a ROM that is significantly different from what you're on now, some of those old settings and data can cause errors, force closes, random reboots, and boot loops. When in doubt, wipe data before flashing a new ROM. When going from one version of a ROM to a newer, very similar version of the same ROM (nightly to nightly), you probably don't need to wipe data, but make a backup just in case. dalvik-cache is also in data; if you wipe data, you've automatically wiped the dalvik cache. It's redundant to wipe data and then wipe dalvik cache.
"cache" is just that, the cache partition. Clearing it won't make you loose anything, at least not anything Android won't silently replace.
So far it seems to be pretty stable on r50. I installed system tuner and brought it down to 1.5 Ghz. I'm not sure why 1.9 is set to default. Doesn't seem like a good idea to me. Thanks all for the help/advice.
NOTE: This is for the Verizon Wireless Samsung Galaxy S3 SCH-I535
Since I'm a new member I wasn't allowed to post this into the developers forum and before I continue: YES, I have searched valiantly for a fix to my particular problem and I spent the entire day new years and most of the day today trying to get CM10.1 to run on my SCH-I535 but ran into problem after problem. Every time I installed any version of CM10 or higher I ran into multiple problems: mainly being that I wasn't able to attain signal, the keyboard wouldn't load or there would be multiple problems with initial setup including having to restart during install so many times I gave up. In the past two days I have Odined back to stock at least 15+ times trying to get CM to run and now that it finally is I believe this is worth sharing.
Before I continue I should mention that your phone should be properly working so if you're in stock and you can't make phone calls or your IMEI is messed up then none of what I'm about to mention is going to work. After you Odin to stock using Root66.tar (http://www.megashare.com/4384479) then type *2767*3855# to reset to factory defaults everything should be running correctly. If not you may have bricked your phone or you have bigger problems for which I cannot help you and I apologize. There's also a torrent file available of the above stock tar file that downloads much faster here: http://forum.xda-developers.com/showthread.php?t=1840030.
So I assume, before I start this, that if you're on these boards you know how to properly root, unlock and flash then recover your phone through CWM 6+. If you do not know how to do this, then you will need to before continuing on.
Use this link: http://forum.xda-developers.com/showthread.php?t=1762709
Now follow Section 1 and pay attention to detail because if you don't you can mess something up and end up having to backtrack which can take valuable time and be amazingly frustrating.
Once these things are done you will need to reboot your phone back out of Recovery mode so you can properly move the necessary zip files onto your internal SD card.
Download CM10 Stable, you can find this here: http://get.cm/?device=d2vzw&type=stable
And download Gapps 4.2.1 here: http://www.teamandroid.com/gapps/ (I used version gapps-jb-20121212-signed.zip)
Put these files on your internal SD card and use EZ Recovery to Flash and then Reboot Recovery, I need to mention as well that when I dragged both of these zip files onto my internal SD I had EZ Recovery open while doing so. I don't know if that had anything to do with it but I thought it was worth mentioning. Clear the cache and data/factory reset then install CM10 followed by Gapps that you installed on the SD earlier.
Once you boot up you should have the phone working but the keyboard will constantly flash a message that it can't run, don't worry about that right now. Now download a nightly version of CM10.1 located here:http://get.cm/?device=d2vzw&type=nightly
(I used cm-10.1-20121231-NIGHTLY-d2vzw.zip)
Now put this on your internal SD card as well and hold the power button for 2 seconds and press restart then select recovery. Now that you're back into the recovery menu CLEAR ONLY CACHE then install the new CM10.1 nightly you just put on your internal SD and then re-install Gapps 4.2.1 from before and reboot. This all worked for me and writing this message is the first thing I wanted to do afterward to make sure no one has to go through the frustration and heartache of constantly failing at installing the ROM they want. I hope this helps at least one person, if you have any questions I will try and answer them to the best of my knowledge but I'm fairly new to all of this.
Or you can just flash CM10.1 first and do this.......
Tap the 4 corners of the screen to bypass activation screen then go into settings> more> mobile networks> and change CDMA Subscription to RUIM/SIM and System Select to Automatic then reboot...
Click to expand...
Click to collapse
Dirty flashing CM10.1 over CM10 is a much longer way then just clicking a couple buttons Its simply the fact that CM10.1 doesnt have the correct cdma subscription on default boot for our phone.
x714x said:
Or you can just flash CM10.1 first and do this.......
Dirty flashing CM10.1 over CM10 is a much longer way then just clicking a couple buttons Its simply the fact that CM10.1 doesnt have the correct cdma subscription on default boot for our phone.
Click to expand...
Click to collapse
I have everything working properly now but I wish I would've known this was the matter that would've fixed my problem without all these extra issues. Now my phone app is crashing in the 12-31-12 version of CM10.1. It just suddenly started happening and I can't seem to get around it.
Bosli said:
I have everything working properly now but I wish I would've known this was the matter that would've fixed my problem without all these extra issues. Now my phone app is crashing in the 12-31-12 version of CM10.1. It just suddenly started happening and I can't seem to get around it.
Click to expand...
Click to collapse
Clear it's cache APPS > ALL > PHONE APP > Clear Cache.
x714x said:
Or you can just flash CM10.1 first and do this.......
Dirty flashing CM10.1 over CM10 is a much longer way then just clicking a couple buttons Its simply the fact that CM10.1 doesnt have the correct cdma subscription on default boot for our phone.
Click to expand...
Click to collapse
What are the correct settings?
I have been doing this a while... and I was already on the 10.0 stable build. So I flashed the 10.1 nightly... Now Play Store closes immediately after opening. I have tried to uninstall and install from .apk without success. CWRM opens and closes immediately , also uninstalled and reinstalled from .apk without success (You can get to it from booting to it with the phone off ). My Gmail app and account nowhere to be found. My attempt to go back to 10.0 were unsuccessful.
I apologize in advance for being a noob, this is my first go at customizing ANYTHING android.
I got my Asus Transformer TF300T in January, had some hardware issues with it and exchanged it. I JUST got it back and decided to go custom before i got it all set up and then i would have to start over.
So I followed THIS guide and successfully installed Baked 7, Initially I used CWM as the guide told, but I could not get a boot image backup, so I used the same method and installed the most recent TWRP and it worked flawlessly.. I was unhappy with how the notification bar was at the top, I liked the stock where it was at the bottom. I could not find initial details on how to revert back to stock rom, so i decided to give some other custom roms a try. I was very interested in scottsmods CleanROM, but their website does not have the download anymore(that I could find) and thats where all the links in guides point to. So instead I installed CyanogenMod using THIS Guide. I immediatly noticed problems with this rom. It did not pick up my SD card, there was an error window that would pop up and go away before i could read it. It would not get on wifi.
I did further research into going back to stock, so I followed THIS guide its not directly XDA, but it followed the same style that i had learned previously(fastboot, etc) I did change to the support page of just the TF300T on the asus site, the guide links to the 3g one. I could not find my SKU in my device because the cyanogen rom changed the "Build" number. So I have tried each from the asus site and flashed them and would get stuck on the asus boot screen. I waited over an hour on each one before i decided it was frozen and to move to the next.
I didnt get any of the stock firmwares working. So I reflashed to TWRP, and attempted to go back to baked. I couldnt get the zip to install in twrp. but i was able to get cynogen to install again. It doesnt have the error window thing and the wifi works but still no SD.
I want to go back to stock, or baked if stocks not possible.
Stocks already been tried to the best of my ability, so i tired baked. Baked is on my external SD card, as in cynogen I cant access the internal one to move the files over.
Baked gives me an error saying unable to open zip file.
What am I missing? I cant seem to figure this out. Any and all help or ideas would be greatly appreciated!
well, first off, you went from Baked 4.1 to cyo 4.2, now as i understand it . They moved the file system around in 4.2, and if you want to go back to 4.1 you have to wipe everything, I use TWRP 2.4.1.0 . Now I can understand not wanting to lose everything you've had set up.. Always do a back up before any major Flash. Just incase if your on a rom now thats decent save your files, perform a wipe, flash a rom , Clean rom in the xda threads is what im using.. Running great BTW. lemme know if it helped or didn't... lol Clean ROM Inheritance is a stock based rom. with an oc kernel which makes the tab perform like its supposed to. just be sure if you do decide to flash it you choose a kernel in the installer with T = Wifi, G=3G, 4G, etc. you want the T G
Sent from my ASUS Transformer Pad TF300T using Tapatalk HD
Goddly said:
well, first off, you went from Baked 4.1 to cyo 4.2, now as i understand it . They moved the file system around in 4.2, and if you want to go back to 4.1 you have to wipe everything, I use TWRP 2.4.1.0 . Now I can understand not wanting to lose everything you've had set up.. Always do a back up before any major Flash. Just incase if your on a rom now thats decent save your files, perform a wipe, flash a rom , Clean rom in the xda threads is what im using.. Running great BTW. lemme know if it helped or didn't... lol Clean ROM Inheritance is a stock based rom. with an oc kernel which makes the tab perform like its supposed to. just be sure if you do decide to flash it you choose a kernel in the installer with T = Wifi, G=3G, 4G, etc. you want the T G
Sent from my ASUS Transformer Pad TF300T using Tapatalk HD
Click to expand...
Click to collapse
Is the 4.1 the same as 7? because 7 was the latest version available from team baked.
Edit: wait a sec... i think I understand. You mean baked 7 was 4.1 android and cyo was 4.2 android?
as far as data goes, i've already done all that. i did factory reset, wipe cache/wipe davik thing each time, no bueno. I have no data on the device as it was brand new outta the box. in TWRP, theres an option for wipe data, but factory reset says it wipes data and cache. should i still do the wipe data option instead of factory reset? so... wipe data/wipe cache/wipe davik instead of factory reset/wipe cache/wipe davik?
And also, I'm trying to flash a rom, back to baked from cyo because atleast baked worked. but it tells me its unable to open my zip files.
Do you have a link to the download of CleanROM? I've checked the official threads here and the download links take me to scottsroms.com and their download page only has the nexus10 and nexus 7 along with a bunch of phones.
Talvir said:
Is the 4.1 the same as 7? because 7 was the latest version available from team baked.
Edit: wait a sec... i think I understand. You mean baked 7 was 4.1 android and cyo was 4.2 android?
as far as data goes, i've already done all that. i did factory reset, wipe cache/wipe davik thing each time, no bueno. I have no data on the device as it was brand new outta the box. in TWRP, theres an option for wipe data, but factory reset says it wipes data and cache. should i still do the wipe data option instead of factory reset? so... wipe data/wipe cache/wipe davik instead of factory reset/wipe cache/wipe davik?
And also, I'm trying to flash a rom, back to baked from cyo because atleast baked worked. but it tells me its unable to open my zip files.
Do you have a link to the download of CleanROM? I've checked the official threads here and the download links take me to scottsroms.com and their download page only has the nexus10 and nexus 7 along with a bunch of phones.
Click to expand...
Click to collapse
Wipe everything.. data from 10.1 is not supported... do you not have a useable backup? If you do restore it. Y o u have to be able to put stuff in storage. Or wipe what i told you, and reflash baked if you already have it.
http://forum.xda-developers.com/showthread.php?t=2049322
Clean rom.. download deodex, 3.3. Put it on the root of sdcard0 (first screen when you press storage, sdcard0 ,)
Wipe, in twrp, in the wipe options, cache, dalvik, factory, system, data.. then f
Sent from my ASUS Transformer Pad TF300T using Tapatalk HD
Goddly said:
Wipe everything.. data from 10.1 is not supported... do you not have a useable backup? If you do restore it. Y o u have to be able to put stuff in storage. Or wipe what i told you, and reflash baked if you already have it.
http://forum.xda-developers.com/showthread.php?t=2049322
Clean rom.. download deodex, 3.3. Put it on the root of sdcard0 (first screen when you press storage, sdcard0 ,)
Wipe, in twrp, in the wipe options, cache, dalvik, factory, system, data.. then f
Sent from my ASUS Transformer Pad TF300T using Tapatalk HD
Click to expand...
Click to collapse
So I managed to install cleanROM but its stuck on the boot screen now. its been sitting here spinnging for 20 minutes. the link you gave me says to let it stabilize for around 10 minutes. is it spinning the stabilizing part? should i let it keep going?
I used the TF300 kernel and the 160 thing as specified in the guide. everything else default with the exception of adding the go launcher HD and hacked hulu plus apps....
I did a format data(which wiped my internal sd and the zip file i was installing from so i had to reload to cya and recopy the zip to my internal sd card. i did factory reset and wiped cach/dalvik prior to installing. then after install i wiped cache/dalvik again as the guide said.
any ideas?
Talvir said:
So I managed to install cleanROM but its stuck on the boot screen now. its been sitting here spinnging for 20 minutes. the link you gave me says to let it stabilize for around 10 minutes. is it spinning the stabilizing part? should i let it keep going?
I used the TF300 kernel and the 160 thing as specified in the guide. everything else default with the exception of adding the go launcher HD and hacked hulu plus apps....
I did a format data(which wiped my internal sd and the zip file i was installing from so i had to reload to cya and recopy the zip to my internal sd card. i did factory reset and wiped cach/dalvik prior to installing. then after install i wiped cache/dalvik again as the guide said.
any ideas?
Click to expand...
Click to collapse
Yes.. which kernel did you choose? You need to flash the stock kernel.. what version of twrp are you using?
Sent from my ASUS Transformer Pad TF300T using Tapatalk HD
Talvir said:
So I managed to install cleanROM but its stuck on the boot screen now. its been sitting here spinnging for 20 minutes. the link you gave me says to let it stabilize for around 10 minutes. is it spinning the stabilizing part? should i let it keep going?
I used the TF300 kernel and the 160 thing as specified in the guide. everything else default with the exception of adding the go launcher HD and hacked hulu plus apps....
I did a format data(which wiped my internal sd and the zip file i was installing from so i had to reload to cya and recopy the zip to my internal sd card. i did factory reset and wiped cach/dalvik prior to installing. then after install i wiped cache/dalvik again as the guide said.
any ideas?
Click to expand...
Click to collapse
OK! so I got my tablet working with cleanROM at last!!!
I figured out why the zip files werent opening. for some reason my tab was only able to install from zips DIRECTLY on the internal sd card. whenever it tried one from the external sd card, despite being mounted, it was always unable to open the zip and would fail.
CleanROM got stuck initially because i used the WW version instead of the US version. Once i reflashed with the US version it worked great! had an issue with the start wizard crashing, but that went away after it stabilized. I stared customizing and playing and had no issues other than the SD card notification. That was an option i didnt choose to patch because i didnt know prior how annoying that notification was. it wouldnt get out of my notification window! so I flashed again, with that option enabled so that the sd card didnt bug me in the notification window.
I just got it back up and running, after the second flash with that modification added, and other than the start wizard still crashing(again, i let it sit a while and now it worked) it seems to be working great!
I hope my experiences can help newbies in the future that may have similar issues!
Talvir said:
OK! so I got my tablet working with cleanROM at last!!!
I figured out why the zip files werent opening. for some reason my tab was only able to install from zips DIRECTLY on the internal sd card. whenever it tried one from the external sd card, despite being mounted, it was always unable to open the zip and would fail.
CleanROM got stuck initially because i used the WW version instead of the US version. Once i reflashed with the US version it worked great! had an issue with the start wizard crashing, but that went away after it stabilized. I stared customizing and playing and had no issues other than the SD card notification. That was an option i didnt choose to patch because i didnt know prior how annoying that notification was. it wouldnt get out of my notification window! so I flashed again, with that option enabled so that the sd card didnt bug me in the notification window.
I just got it back up and running, after the second flash with that modification added, and other than the start wizard still crashing(again, i let it sit a while and now it worked) it seems to be working great!
I hope my experiences can help newbies in the future that may have similar issues!
Click to expand...
Click to collapse
So.. which kernel did you choose? You should download the 2.0 kernel installer on the same thread, and choose the Unters tf300tG because you have 3g.. you will find your tablet runs ALOT smoother and faster than stock, but you need to flash the stock kernel first. Its a good way to do kernel flashes.
Sent from my ASUS Transformer Pad TF300T using Tapatalk HD
Also, you might want to get a different micro SD card, since the one you are using is having issues.
mike-y said:
Also, you might want to get a different micro SD card, since the one you are using is having issues.
Click to expand...
Click to collapse
??? it s jut a notification mod..
and dont be afraid to thank my posts! lol i would appreciate it..
Sent from my ASUS Transformer Pad TF300T using Tapatalk HD
The kernel I used was the stock one.
I actually dont have 3G. mine is just a TF300T wifi only. Unless its the software that makes it 3G? But i dont think thats the case...
Would that alternate kernel give any other benefits other than 3G support?
Oh yea. Youll see a dramatic change in performance to say the least. Now. Im running a tf 700 kernel. But I would recommend you yo get the Unters TF300t kernel in the 2.0 Kernel Installer. Put the Installer zip on internal. Flash. Choose your kernel. Wipe cache and dalvik . Then reboot. You will not regret it.
Sent from my SPH-D710 using Tapatalk 2
I started with a factory wiped system when I bought it.
I unlocked and rooted
I installed CROMI-X 4.68 and patched to 4.69 with _that v3+ (I think that is one of the stock options for CROMI)
I then installed the MAX kernel RC1 and everything was running pretty well. Still a little laggy here and there but not bad
I had been making Nandroid backups along the way so I felt pretty confident
Then I heard that doing a clean install might be even better and I wasn't exactly sure what options I had selected when installing CROMI the first time so I decided to try a clean install
I got a microsd card and put all of my ROMs and kernels on it
I rebooted into TWRP an went to Wipe-->Advanced Wipe and selected everything but the microSD and wiped it
I then formatted the data partition (I don't think that I had to do this but it felt like it was even more clean somehow)
I then installed CROMI 4.6.8 (this time I selected to disable fsync where I am pretty sure that i didn't last time because I didnot know what it did)
It rebooted fine
Installed 4.6.9 patch
It rebooted fine
Installed MAX RC1 (just like I had before)
Started booting, updated 37 apps and the hung on the starting apps dialog.
Waited a while and rebooted manually and it would hang on the boot animation toward the end
I got a little worried so I tried restoring my last Nandroid backup
Seemed to restore fine but again hung on the boot animation
Started to get more worried now because I thought that this was always my safety net and it didn't seem to be working
Wiped everything again (same as above)
restored the stock JB backup that I had and it booted fine. whew...
Tried a factory reset through stock JB ( I thouugh tthat this would put me back in a situation like I was in during the first install so I could reinstall CROMI and the MAX kernel and be on my way
Again, I then installed CROMI 4.6.8 (disabled fsync again)
It rebooted fine
Installed 4.6.9 patch
It rebooted fine
Installed MAX RC1 (just like I had before)
Started booting, updated 37 apps and the hung on the starting apps dialog.
Waited a while and rebooted manually and it would hang on the boot animation toward the end
This was all done around midnight ladst night and I need to get some sleep so I could come to work today (and write this post )
I am not sure what to do at this point. I really just want a nice clean install of CROMI 4.6.9 with the MAX kernel that I can start using like I want to. I would also like to try disabling fsync to see if it is any less laggy but at this point I may try all of the above steps but leave it enabled to see if that is the variable that is causing my problem. I will try fooling with it again tonight to see if I can get it working. I even re-downloaded all of the zip files in case one of them got corrupt somehow (just trying to cover my bases.
Any thoughts on what I am doing wrong would be greatly appreciated.
sorry for the long post
Jeff
gixxer340 said:
I started with a factory wiped system when I bought it.
I unlocked and rooted
I installed CROMI-X 4.68 and patched to 4.69 with _that v3+ (I think that is one of the stock options for CROMI)
I then installed the MAX kernel RC1 and everything was running pretty well. Still a little laggy here and there but not bad
I had been making Nandroid backups along the way so I felt pretty confident
Then I heard that doing a clean install might be even better and I wasn't exactly sure what options I had selected when installing CROMI the first time so I decided to try a clean install
I got a microsd card and put all of my ROMs and kernels on it
I rebooted into TWRP an went to Wipe-->Advanced Wipe and selected everything but the microSD and wiped it
I then formatted the data partition (I don't think that I had to do this but it felt like it was even more clean somehow)
I then installed CROMI 4.6.8 (this time I selected to disable fsync where I am pretty sure that i didn't last time because I didnot know what it did)
It rebooted fine
Installed 4.6.9 patch
It rebooted fine
Installed MAX RC1 (just like I had before)
Started booting, updated 37 apps and the hung on the starting apps dialog.
Waited a while and rebooted manually and it would hang on the boot animation toward the end
I got a little worried so I tried restoring my last Nandroid backup
Seemed to restore fine but again hung on the boot animation
Started to get more worried now because I thought that this was always my safety net and it didn't seem to be working
Wiped everything again (same as above)
restored the stock JB backup that I had and it booted fine. whew...
Tried a factory reset through stock JB ( I thouugh tthat this would put me back in a situation like I was in during the first install so I could reinstall CROMI and the MAX kernel and be on my way
Again, I then installed CROMI 4.6.8 (disabled fsync again)
It rebooted fine
Installed 4.6.9 patch
It rebooted fine
Installed MAX RC1 (just like I had before)
Started booting, updated 37 apps and the hung on the starting apps dialog.
Waited a while and rebooted manually and it would hang on the boot animation toward the end
This was all done around midnight ladst night and I need to get some sleep so I could come to work today (and write this post )
I am not sure what to do at this point. I really just want a nice clean install of CROMI 4.6.9 with the MAX kernel that I can start using like I want to. I would also like to try disabling fsync to see if it is any less laggy but at this point I may try all of the above steps but leave it enabled to see if that is the variable that is causing my problem. I will try fooling with it again tonight to see if I can get it working. I even re-downloaded all of the zip files in case one of them got corrupt somehow (just trying to cover my bases.
Any thoughts on what I am doing wrong would be greatly appreciated.
sorry for the long post
Jeff
Click to expand...
Click to collapse
I hoped that you had a latest bootloader and TWRP. You can try to follow the procedures below. It works fine for me every time.
1. Boot into TWRP and select "Wipe"
2. Use "Format" instead of Wipe Caches and Data. They are probably the same but I prefer Format method.
3. Install Cromi X V4.6.8. When it is finished, install Patch V4.6.9 on top of V4.6.8 in the Same Session.
4. When you see install the Successful message, now you can reboot and let it update.
5. When you see the Setup Screen, leave it there for about 1 minute and boot it back into TWRP and install the Kernel that you prefer
6. After the Kernel is completed, you can reboot your device and start using it. Good luck and please report back, thanks.
BTW, you don't have to disable FSync during install process. You can manually toggle it on/off after you are happy with your installation and with all the update. If you have some kind of root file manager, you can navigate to this folder: system/ect/init.d and add this line at the end of the 50CleanTWEAKS file: echo 0 > /sys/devices/virtual/misc/fsynccontrol/fsync_enabled. 0 is disable and 1 is enable.
I have TWRP 2.5, not sure about the version of the bootloader.
I will try your suggestions but i do have one question though.
You say "5. When you see the Setup Screen, leave it there for about 1 minute and boot it back into TWRP and install the Kernel that you prefer"
Do you mean when I see the white setup screens just wait for 1 minute and then power off back to recovery? Don't finish the setup?
Thanks again
Jeff
gixxer340 said:
I have TWRP 2.5, not sure about the version of the bootloader.
Jeff
Click to expand...
Click to collapse
This may be the clue!
Boot the tablet with Volume Down and Power buttons and read the tiny script. You should be on the 10.6.1.14.4 or 10.6.1.14.8 bootloader.
If you are not, grab the bootloader/TWRP package from the CROMi-X OP, flash it in TWRP and reboot.
gixxer340 said:
I have TWRP 2.5, not sure about the version of the bootloader.
I will try your suggestions but i do have one question though.
You say "5. When you see the Setup Screen, leave it there for about 1 minute and boot it back into TWRP and install the Kernel that you prefer"
Do you mean when I see the white setup screens just wait for 1 minute and then power off back to recovery? Don't finish the setup?
Thanks again
Jeff
Click to expand...
Click to collapse
Yes, you are correct.
---------- Post added at 01:49 PM ---------- Previous post was at 01:46 PM ----------
berndblb said:
This may be the clue!
Boot the tablet with Volume Down and Power buttons and read the tiny script. You should be on the 10.6.1.14.4 or 10.6.1.14.8 bootloader.
If you are not, grab the bootloader/TWRP package from the CROMi-X OP, flash it in TWRP and reboot.
Click to expand...
Click to collapse
Bootloader Version: 1.00e and Released by Firmware Version: 10.6.1.14.8 :good:
My bootloader is 10.6.1.14.4. is that new enough?
Jeff
gixxer340 said:
My bootloader is 10.6.1.14.4. is that new enough?
Jeff
Click to expand...
Click to collapse
I believed that the bootloader version is the same on both 10.6.14.4 and 10.6.14.8 firmwares. Maybe, someone with a better knowledge can confirm it.
LetMeKnow said:
I hoped that you had a latest bootloader and TWRP. You can try to follow the procedures below. It works fine for me every time.
1. Boot into TWRP and select "Wipe"
2. Use "Format" instead of Wipe Caches and Data. They are probably the same but I prefer Format method.
3. Install Cromi X V4.6.8. When it is finished, install Patch V4.6.9 on top of V4.6.8 in the Same Session.
4. When you see install the Successful message, now you can reboot and let it update.
5. When you see the Setup Screen, leave it there for about 1 minute and boot it back into TWRP and install the Kernel that you prefer
6. After the Kernel is completed, you can reboot your device and start using it. Good luck and please report back, thanks.
BTW, you don't have to disable FSync during install process. You can manually toggle it on/off after you are happy with your installation and with all the update. If you have some kind of root file manager, you can navigate to this folder: system/ect/init.d and add this line at the end of the 50CleanTWEAKS file: echo 0 > /sys/devices/virtual/misc/fsynccontrol/fsync_enabled. 0 is disable and 1 is enable.
Click to expand...
Click to collapse
I followed your recipe exactly and it seems to have worked like a charm. I did leave fsync enabled this time as well. I am now setting everything back up. Thanks a lot for the help.
Jeff
gixxer340 said:
I followed your recipe exactly and it seems to have worked like a charm. I did leave fsync enabled this time as well. I am now setting everything back up. Thanks a lot for the help.
Jeff
Click to expand...
Click to collapse
It is great that you got your tablet going. About the FSync, you don't have to hurry to disable it. You can manually toggle it off later when everything is running good. It improves your I/O speed quite bit. Just to remember to enable it when you do a major update or app installations. Good luck.
gixxer340 said:
My bootloader is 10.6.1.14.4. is that new enough?
Click to expand...
Click to collapse
LetMeKnow said:
I believed that the bootloader version is the same on both 10.6.14.4 and 10.6.14.8 firmwares. Maybe, someone with a better knowledge can confirm it.
Click to expand...
Click to collapse
The 10.6.1.14.4 and 10.6.1.14.8 bootloaders are identical (except for version number and build date).
_that said:
The 10.6.1.14.4 and 10.6.1.14.8 bootloaders are identical (except for version number and build date).
Click to expand...
Click to collapse
Thanks _that for the confirmation. :good:
gixxer340 said:
I followed your recipe exactly and it seems to have worked like a charm. I did leave fsync enabled this time as well. I am now setting everything back up. Thanks a lot for the help.
Jeff
Click to expand...
Click to collapse
For completeness sake I would like to add a couple other things that I did differently from my previous attempts. I don't know if they made a difference or not.
1. Reformatted the microSD card to FAT32 instead of exFAT
2. Redownloaded all images and verified their MD5 sum after copying them to the SD card/
Again, not sure if it made a difference but I am up and running now.
Thanks again
Jeff
I installed the latest Cromi which went well for a week or two until the tablet started shutting off about 10 seconds after the home screen loaded. I[m pretty sure it has nothing to do with the ROM, but I still want to go back to stock and flash it all over again. How do I go back to complete stock if I had TWRP?
ocstew said:
I installed the latest Cromi which went well for a week or two until the tablet started shutting off about 10 seconds after the home screen loaded. I[m pretty sure it has nothing to do with the ROM, but I still want to go back to stock and flash it all over again. How do I go back to complete stock if I had TWRP?
Click to expand...
Click to collapse
Download the latest stock firmware from asus, extract it once then flash it with twrp. But this could be unnecessary. You might wanna try flash _thats kernel and see if it shows any difference.
ocstew said:
I installed the latest Cromi which went well for a week or two until the tablet started shutting off about 10 seconds after the home screen loaded. I[m pretty sure it has nothing to do with the ROM, but I still want to go back to stock and flash it all over again. How do I go back to complete stock if I had TWRP?
Click to expand...
Click to collapse
You maybe selected your sleep mode with a 15 second in your system setting. You can go to your system setting and select display. Your sleep mode will pop up and pick a different time for your sleep mode..
JoinTheRealms said:
Download the latest stock firmware from asus, extract it once then flash it with twrp. But this could be unnecessary. You might wanna try flash _thats kernel and see if it shows any difference.
Click to expand...
Click to collapse
I tried flashing the stock kernel that came with the Chromi install but the same thing continued to happen. I also overclocked the CPU to 1.7 Ghz using the Hunds kernel, resulting in the tablet crashing. I did this multiple times. Is it possible that my hardware is damaged?
LetMeKnow said:
You maybe selected your sleep mode with a 15 second in your system setting. You can go to your system setting and select display. Your sleep mode will pop up and pick a different time for your sleep mode..
Click to expand...
Click to collapse
I don't think so, I'm actively touching the screen and then the tablet will be unresponsive and shut down.
ocstew said:
I tried flashing the stock kernel that came with the Chromi install but the same thing continued to happen. I also overclocked the CPU to 1.7 Ghz using the Hunds kernel, resulting in the tablet crashing. I did this multiple times. Is it possible that my hardware is damaged?
I don't think so, I'm actively touching the screen and then the tablet will be unresponsive and shut down.
Click to expand...
Click to collapse
Sorry, misread your post..
Edit:
Did you do a clean install? Hund's kernel has a thermal throttle which reduces the CPU speed if it reaches a certain temperature that I believed.
It is more likely a software problem.
ocstew said:
I tried flashing the stock kernel that came with the Chromi install but the same thing continued to happen. I also overclocked the CPU to 1.7 Ghz using the Hunds kernel, resulting in the tablet crashing. I did this multiple times. Is it possible that my hardware is damaged?
Click to expand...
Click to collapse
Very unlikely, Is it possible during the cromix install you selected the option to undervolt? this could be the cause of the instabilities, More likely you have installed a root app thats failing during loading and bringing the system down. is the reboots consistently 10 after reaching the homescrren or the times vary?
Best option is to wipe and reflash cromix (or stock, but stock requires reflashing twrp with fastboot) with nothing but the default options and see if the issue persists
---------- Post added at 05:21 PM ---------- Previous post was at 05:12 PM ----------
LetMeKnow said:
Sorry, misread your post..
Edit:
Did you do a clean install? Hund's kernel has a thermal throttle which reduces the CPU speed if it reaches a certain temperature that I believed.
It is more likely a software problem.
Click to expand...
Click to collapse
Hmm this shouldn't be the issue. Hunds may have modified the default thermal throttling settings (from memory its high 70c) but it even should be safe up til low 80c (if your tablets running that hot you should really think about hoping out of the volcano your currently in )
Im far from a kernel expert but off the top of my head if the issue was kernel related it would be because once android init processes are finished a flag is passed allowing the kernel to scale to higher frequencies, at this point it might be crashing because at those high frequencies the tablet isn't allowing enough voltage to stay stable.
LetMeKnow said:
Sorry, misread your post..
Edit:
Did you do a clean install? Hund's kernel has a thermal throttle which reduces the CPU speed if it reaches a certain temperature that I believed.
It is more likely a software problem.
Click to expand...
Click to collapse
That's what I'm trying to do but it isn't working. I'm not sure how to use TWRP to reset my system back to its original state. I press factory reset, but it completes incredibly quickly, signalling that nothing is actually being reset. How do I revert my system back to stock, erasing all the data on my tablet?
JoinTheRealms said:
Very unlikely, Is it possible during the cromix install you selected the option to undervolt? this could be the cause of the instabilities, More likely you have installed a root app thats failing during loading and bringing the system down. is the reboots consistently 10 after reaching the homescrren or the times vary?
Best option is to wipe and reflash cromix (or stock, but stock requires reflashing twrp with fastboot) with nothing but the default options and see if the issue persists
---------- Post added at 05:21 PM ---------- Previous post was at 05:12 PM ----------
Hmm this shouldn't be the issue. Hunds may have modified the default thermal throttling settings (from memory its high 70c) but it even should be safe up til low 80c (if your tablets running that hot you should really think about hoping out of the volcano your currently in )
Im far from a kernel expert but off the top of my head if the issue was kernel related it would be because once android init processes are finished a flag is passed allowing the kernel to scale to higher frequencies, at this point it might be crashing because at those high frequencies the tablet isn't allowing enough voltage to stay stable.
Click to expand...
Click to collapse
No I didn't select that option. I suspect you're right. It always happens within a certain time interval, which is why I'm trying to completely erase everything on my tablet and start from stock. I flashed this ROM: http://forum.xda-developers.com/showthread.php?t=2223918
....And now it's been on "android is upgrading - starting apps" for 5 minutes now
ocstew said:
That's what I'm trying to do but it isn't working. I'm not sure how to use TWRP to reset my system back to its original state. I press factory reset, but it completes incredibly quickly, signalling that nothing is actually being reset. How do I revert my system back to stock, erasing all the data on my tablet?
It always happens within a certain time interval.
Click to expand...
Click to collapse
Use the method i just posted to get back to stock, twrp's factory reset doesn't do that, it wipes /system and cache partitions to remove android completely.
JoinTheRealms said:
Very unlikely, Is it possible during the cromix install you selected the option to undervolt? this could be the cause of the instabilities, More likely you have installed a root app thats failing during loading and bringing the system down. is the reboots consistently 10 after reaching the homescrren or the times vary?
Best option is to wipe and reflash cromix (or stock, but stock requires reflashing twrp with fastboot) with nothing but the default options and see if the issue persists
---------- Post added at 05:21 PM ---------- Previous post was at 05:12 PM ----------
Hmm this shouldn't be the issue. Hunds may have modified the default thermal throttling settings (from memory its high 70c) but it even should be safe up til low 80c (if your tablets running that hot you should really think about hoping out of the volcano your currently in )
Im far from a kernel expert but off the top of my head if the issue was kernel related it would be because once android init processes are finished a flag is passed allowing the kernel to scale to higher frequencies, at this point it might be crashing because at those high frequencies the tablet isn't allowing enough voltage to stay stable.
Click to expand...
Click to collapse
Thanks for the information. I am using the balance mode most of the time and it is max out around 51C. I think that I have a better luck than some people so far without any problem with Cromi X and Hund. About the throttle information on Hund's kerneI, I just want to mess around with it. I think that Hund sets it at level 0 onTegra_table0...
JoinTheRealms said:
Use the method i just posted to get back to stock, twrp's factory reset doesn't do that, it wipes /system and cache partitions to remove android completely.
Click to expand...
Click to collapse
I've been trying to find the stock firmware but the Asus website only has some manuals: http://support.asus.com/Download.aspx?SLanguage=en&m=ASUS+Transformer+Pad+Infinity+TF700T&p=28&s=1
Can you link me? And when you say "flash" do you mean press Install in TWRP and select a zip, etc?
ocstew said:
I've been trying to find the stock firmware but the Asus website only has some manuals: http://support.asus.com/Download.aspx?SLanguage=en&m=ASUS+Transformer+Pad+Infinity+TF700T&p=28&s=1
Can you link me? And when you say "flash" do you mean press Install in TWRP and select a zip, etc?
Click to expand...
Click to collapse
http://support.asus.com/Download.aspx?SLanguage=en&m=ASUS+Transformer+Pad+Infinity+TF700T&p=28&s=1
Im assuming your in the US if so make sure you use the US version. Yes where people here might say "flash" they mean install. Flash is the terminology of writing data to ROM memory
ocstew said:
That's what I'm trying to do but it isn't working. I'm not sure how to use TWRP to reset my system back to its original state. I press factory reset, but it completes incredibly quickly, signalling that nothing is actually being reset. How do I revert my system back to stock, erasing all the data on my tablet?
No I didn't select that option. I suspect you're right. It always happens within a certain time interval, which is why I'm trying to completely erase everything on my tablet and start from stock. I flashed this ROM: http://forum.xda-developers.com/showthread.php?t=2223918
....And now it's been on "android is upgrading - starting apps" for 5 minutes now
Click to expand...
Click to collapse
If you want to reset, you need to boot into the TWRP and select Wipe, then Advance Wipe. In Advance wipe, you need to check Dalvik, Cache, and Data to do a factory reset. I hope that helps.
Edit:
Do you have an external SD in your device?
LetMeKnow said:
If you want to reset, you need to boot into the TWRP and select Wipe, then Advance Wipe. In Advance wipe, you need to check Dalvik, Cache, and Data to do a factory reset. I hope that helps.
Edit:
Do you have an external SD in your device?
Click to expand...
Click to collapse
Yes I do. I think I did something stupid though, I flashed the ROM in the link using my external sdcard. It all worked fine until it stayed on "Starting Apps" for 5 minutes, at which I used the hardware reset buttons. My tablet cannot go beyond the spinning circle thingy and TWRP seems to have disappeared. My ignorance of Android is astounding haha :laugh:
I selected the "wipe" option when you hold down power and volume down. And it seems to have booted into the original start up screen, yay!
ocstew said:
I've been trying to find the stock firmware but the Asus website only has some manuals: http://support.asus.com/Download.aspx?SLanguage=en&m=ASUS+Transformer+Pad+Infinity+TF700T&p=28&s=1
Can you link me? And when you say "flash" do you mean press Install in TWRP and select a zip, etc?
Click to expand...
Click to collapse
I see absolutely no reason why you should flash the stock firmware. You'll just loose TWRP and root and have to start all over again.
Try this:
Put the your CROMI-X zip on a microSD.
Boot into TWRP and choose Wipe > Advanced > Format Data. This will erase your entire data partiton, so make sure everything is backed up.
Flash CROMI-X from the microSD. The Aroma installer will format your system partition before installing the new rom, wiping cache and Dalvik is the default selection as well.
Choose the stock kernel or _that's kernel for stability.
Oh, btw, what bootloader/recovery are you on? If you're not on 10.6.1.14.8 and TWRP 2.5/2.6, flash the package from the OP first, boot back into system, then proceed as described.
Sent from my DROID4 using Tapatalk 2
---------- Post added at 11:29 PM ---------- Previous post was at 11:25 PM ----------
ocstew said:
Yes I do. I think I did something stupid though, I flashed the ROM in the link using my external sdcard. It all worked fine until it stayed on "Starting Apps" for 5 minutes, at which I used the hardware reset buttons. My tablet cannot go beyond the spinning circle thingy and TWRP seems to have disappeared. My ignorance of Android is astounding haha :laugh:
I selected the "wipe" option when you hold down power and volume down. And it seems to have booted into the original start up screen, yay!
Click to expand...
Click to collapse
Jeez! Just saw this! You chose Wipe Data from the bootloader menu?? Consider yourself lucky that you're not hard bricked! Slow down! Don't do anything else before you're sure what you're doing!
Sent from my DROID4 using Tapatalk 2
What are the repercussions of wipe data? Everything seems to have reverted to normal and my tablet is running properly now. Thanks for the caution.
My build number has the string: 10.6.1.14.4-20130329
ocstew said:
What are the repercussions of wipe data? Everything seems to have reverted to normal and my tablet is running properly now. Thanks for the caution.
My build number has the string: 10.6.1.14.4-20130329
Click to expand...
Click to collapse
I am glad that you got your tab working again.. :good: What berndblb said is correct. People have had brick their devices using Wipe from the bootlloader if their bootloader and custom recovery are not compatible. The good practice is not using it because when the bootloader is not working, you can do anything unless you can update the bootloader binary.
ocstew said:
What are the repercussions of wipe data? Everything seems to have reverted to normal and my tablet is running properly now. Thanks for the caution.
My build number has the string: 10.6.1.14.4-20130329
Click to expand...
Click to collapse
Guys don't get paranoid about the Wipe Data option . That option caused bricks only when the users used a custom recovery which wasn't compatible with the device's bootloader. Using Wipe Data when no custom recovery is actually the only easy way to do a Factory Reset (especially for people on stock firmware and locked bootloader) and personally it also helped me repair a corrupted partition, so my advice is to read first and flash after.
Pretoriano80 said:
Guys don't get paranoid about the Wipe Data option . That option caused bricks only when the users used a custom recovery which wasn't compatible with the device's bootloader. Using Wipe Data when no custom recovery is actually the only easy way to do a Factory Reset (especially for people on stock firmware and locked bootloader) and personally it also helped me repair a corrupted partition, so my advice is to read first and flash after.
Click to expand...
Click to collapse
Best advice yet never be hasty when flashing stuffs. By the way im confused at how that would cause a soft brick? im not sure how or why it would affect fastboot access
JoinTheRealms said:
Best advice yet never be hasty when flashing stuffs. By the way im confused at how that would cause a soft brick? im not sure how or why it would affect fastboot access
Click to expand...
Click to collapse
AFAIK an incompatibility between a custom recovery and the bootloader was only causing a bootloop to recovery and also some corrupted partition, but the bootloader was ok. The bad part was that the user couldn't reach the fastboot mode anymore because the device always restarted to recovery (so no bootloader menu when pressing Volume Down + Power) but about two months ago _that managed to find a way to kick the device out of the recovery bootloop and once you did it you can recover the device just fine.
Pretoriano80 said:
AFAIK an incompatibility between a custom recovery and the bootloader was only causing a bootloop to recovery and also some corrupted partition, but the bootloader was ok. The bad part was that the user couldn't reach the fastboot mode anymore because the device always restarted to recovery (so no bootloader menu when pressing Volume Down + Power) but about two months ago _that managed to find a way to kick the device out of the recovery bootloop and once you did it you can recover the device just fine.
Click to expand...
Click to collapse
Note that this unbricking method *requires* a working rooted Android image, which the user whom I helped luckily still had. In other cases it is still a hard brick (because the recovery cannot access the eMMC so it is impossible to remove the reboot-to-recovery command or flash anything), so I recommend never using "wipe data" from the bootloader menu, or "install update" from within Android with a custom recovery.