Database Info

Rooted, Backed-Up, Flashed to Synergy...First timer...How to load backups now?

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.

CleanROM question and a slight problem

I just received my TF700T for Christmas so I'm still a noob, please excuse my mistakes. Today I unlocked, rooted and flashed the ODEXED CleanROM 2.7 onto my TF700T and then proceeded to flash the 2.7.2 patch and then the 3.0.4 patch (3.0.4 is DEODEXED). I didn't have a problem until I enabled USB Debugging. When I enabled it the first time it caused my tablet to freeze and reboot, but when I tried to enable it again I didn't have a problem until I tried to disable USB Debugging and this caused the tablet to freeze and reboot each time I tried it. I was thinking that this problem could have possibly been caused by flashing the DEODEXED 3.0.4 patch over the 2.7 ODEXED CleanROM base/2.7.2 patch (Not sure if ODEXED or DEODEXED).
**FIXED (Recovery was not effected, rebooted into recovery and flashed CleanROM 3.0.3) But will leave the description up in case someone else has the same problem
That was my question but now I have a problem... I wanted to wipe the system and then flash 3.0.3 and then the 3.0.4 patch to see if that would fix the problem but I ended up fudging up the process. I started by wiping the cache/dalvik and then wiping the system but when I went to flash CleanROM 3.0.3 I noticed that I didn't have my microSD card in my tablet. I guess I had forgotten to replace it after transferring 3.0.3 to my microSD card from my PC. Now, I can't reboot the system because it says 'No OS Installed!' and I can't access my microSD card when I plug it into my tablet. I have everything that I need, including 3.0.3, the 3.0.4 patch and my TWRP backups on my microSD card. What can I do here? Can I somehow access my microSD card through some terminal command or just reboot the system and try to get into recovery? I haven't tried to reboot or anything in fear of some sort of brick (I just got my TF700T so I'm a little skittish and I want to be sure before I do something).

boot into recovery
Stran93r said:
I just received my TF700T for Christmas so I'm still a noob, please excuse my mistakes. Today I unlocked, rooted and flashed the ODEXED CleanROM 2.7 onto my TF700T and then proceeded to flash the 2.7.2 patch and then the 3.0.4 patch (3.0.4 is DEODEXED). I didn't have a problem until I enabled USB Debugging. When I enabled it the first time it caused my tablet to freeze and reboot, but when I tried to enable it again I didn't have a problem until I tried to disable USB Debugging and this caused the tablet to freeze and reboot each time I tried it. I was thinking that this problem could have possibly been caused by flashing the DEODEXED 3.0.4 patch over the 2.7 ODEXED CleanROM base/2.7.2 patch (Not sure if ODEXED or DEODEXED). That was my question but now I have a problem... I wanted to wipe the system and then flash 3.0.3 and then the 3.0.4 patch to see if that would fix the problem but I ended up fudging up the process. I started by wiping the cache/dalvik and then wiping the system but when I went to flash CleanROM 3.0.3 I noticed that I didn't have my microSD card in my tablet. I guess I had forgotten to replace it after transferring 3.0.3 to my microSD card from my PC. Now, I can't reboot the system because it says 'No OS Installed!' and I can't access my microSD card when I plug it into my tablet. I have everything that I need, including 3.0.3, the 3.0.4 patch and my TWRP backups on my microSD card. What can I do here? Can I somehow access my microSD card through some terminal command or just reboot the system and try to get into recovery? I haven't tried to reboot or anything in fear of some sort of brick (I just got my TF700T so I'm a little skittish and I want to be sure before I do something).
Click to expand...
Click to collapse
Just hold down vol- & power then after the four icons come up press vol+. This should put you back in recovery.

totaleras said:
Just hold down vol- & power then after the four icons come up press vol+. This should put you back in recovery.
Click to expand...
Click to collapse
Just saw this in another thread, I was able to restart the device into recovery and I am now flashing CleanROM 3.0.3. I finally have an OS installed! Woot!
EDIT: So I was able to flash 3.0.3 and then patch it with 3.0.4, I set a few things up and then went to check the developer's options and to my dismay all the options were greyed out, the could be selected but not changed or anything. I then found that I had to manually turn the developer's options 'on' in the upper left hand corner before I could interact with the options. I do not remember having to do so when I had gone from 2.7 -> 2.7.2 -> 3.0.4. Could flashing the the DEODEXED 3.0.4 over the ODEXED 2.7/2.7.2 have somehow screwed with the system files in some way? Knowing that I hadn't had the option to enable the developer's options but was still able to interact with the options seems like a plausible reason for why the interaction caused my tablet to reboot.

Stran93r said:
Just saw this in another thread, I was able to restart the device into recovery and I am now flashing CleanROM 3.0.3. I finally have an OS installed! Woot!
EDIT: So I was able to flash 3.0.3 and then patch it with 3.0.4, I set a few things up and then went to check the developer's options and to my dismay all the options were greyed out, the could be selected but not changed or anything. I then found that I had to manually turn the developer's options 'on' in the upper left hand corner before I could interact with the options. I do not remember having to do so when I had gone from 2.7 -> 2.7.2 -> 3.0.4. Could flashing the the DEODEXED 3.0.4 over the ODEXED 2.7/2.7.2 have somehow screwed with the system files in some way? Knowing that I hadn't had the option to enable the developer's options but was still able to interact with the options seems like a plausible reason for why the interaction caused my tablet to reboot.
Click to expand...
Click to collapse
It does seem likely that something went terribly wrong with your previous flash, as the enabling of Dev Options has been there since JB -- I ran into it as well, as I hadn't updated any of the other devices in the household yet. All's good that ends well, I'd say. Enjoy your working 700 now, and till next time. :victory:

The problems are caused by going from the 10.4.4.20 base to the 10.4.4.23 patch without updating the other system files first.
The 2 frameworks are different; 2.7.x being US and odexed and 3.0.4 being WW based and deodexed. The 2 don't mix as you found out.
Flashing 3.0.3 wipes the system partition first thus doing a clean install. My patch files just update the system files with no wipe. In this case 3.0.4 updates 3 framework files.
Anyway glad you had an easy fix.

sbdags said:
The problems are caused by going from the 10.4.4.20 base to the 10.4.4.23 patch without updating the other system files first.
The 2 frameworks are different; 2.7.x being US and odexed and 3.0.4 being WW based and deodexed. The 2 don't mix as you found out.
Flashing 3.0.3 wipes the system partition first thus doing a clean install. My patch files just update the system files with no wipe. In this case 3.0.4 updates 3 framework files.
Anyway glad you had an easy fix.
Click to expand...
Click to collapse
Ahhh I see. I'm curious as to why flashing the 2.7.x over 3.0.x cause the developer's options to already be turned on. I understand why the reason for the crash but wouldnt both bases, the 2.7.x and 3.0.x, need to have the developer's options turned on? Or does the US ODEXED base not require the user to turn on developer's options?
Sent from my SCH-I535 using xda premium

Stran93r said:
Ahhh I see. I'm curious as to why not flashing the 2.7.x over 3.0.x cause the developer's options to already be turned on. I understand why the reason for the crash but wouldnt both bases, the 2.7.x and 3.0.x, need to have the developer's options turned on? Or does the US ODEXED base not require the user to turn on developer's options?
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
Neither requires them turned on. Some options are turned on by me when installing
You may have a weird mixed and matched set when mixing bases like you did.

sbdags said:
Neither requires them turned on. Some options are turned on by me when installing
You may have a weird mixed and matched set when mixing bases like you did.
Click to expand...
Click to collapse
For some reason the whole incident has spiked my curiosity. I kind of want to redo it and get a logcat of what's going on. But testing my luck could end up badly
Sent from my SCH-I535 using xda premium

[Q] Tablet always shuts off after 10 seconds

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.

[Q] Need Help!...Hope this isn't a brick...

I finally got the tf700t rooted/unlocked and thought everything was working well. I downloaded a ROM from GooManager and started to see what difference it would make on the tablet. For a few hours it seemed to be working fine. Then I noticed the screen was black and would not come back on. I then did a cold boot and that's when the tablet started power cycling. Please tell me this can be fixed. When I tried to restore the TWRP backup file it said "Restore Failed", and went back to power cycling/resetting. Have I bricked it?

mrchocklit said:
I finally got the tf700t rooted/unlocked and thought everything was working well. I downloaded a ROM from GooManager and started to see what difference it would make on the tablet. For a few hours it seemed to be working fine. Then I noticed the screen was black and would not come back on. I then did a cold boot and that's when the tablet started power cycling. Please tell me this can be fixed. When I tried to restore the TWRP backup file it said "Restore Failed", and went back to power cycling/resetting. Have I bricked it?
Click to expand...
Click to collapse
It is more likely that you have a bootloop.. As long as your bootloader is working, you can do a lot of things that can bring your tablet back..

Also sounds like /data is corrupted.
Choose the wipe button in twrp and then format data.
Be warned you will lose everything on the tab but it will get you booting again.
Which kernel combination did you flash on CROMi-X 5?

sbdags said:
Also sounds like /data is corrupted.
Choose the wipe button in twrp and then format data.
Be warned you will lose everything on the tab but it will get you booting again.
Which kernel combination did you flash on CROMi-X 5?
Click to expand...
Click to collapse
I didn't use CROMi-X. I downloaded a ROM from GooManager. How can I get CROMi-X and should I no longer use GooManager? I took your advice however and everything worked out well- thanks for that. I was still rooted and unlocked but I'd like to know exactly what I need to do in order to enjoy the tablet without 'messing' it up again.

mrchocklit said:
I didn't use CROMi-X. I downloaded a ROM from GooManager. How can I get CROMi-X and should I no longer use GooManager? I took your advice however and everything worked out well- thanks for that. I was still rooted and unlocked but I'd like to know exactly what I need to do in order to enjoy the tablet without 'messing' it up again.
Click to expand...
Click to collapse
Just follow the instructions in the CROMi-X first post
I don't know how other ROMs set themselves up.

Random lockups, new roms failed to install

Hello.
I've been experimenting with my TF700t now.
Tried to install CM11, and it got random reboots all the time. I needed Clockwork so i recovery (had twrp before). I finally managed to get past the setup (basically skip and next on all settings) but it was "ready" it still freezes and random reboots.
I'm not really sure what boot loader i have.
Maybe the one i have is to old?
I had CleanRom before i started playing around with it.
If i cant fix it the trash bin is very close, but if i can get it to work again it would be nice.
It haven't been much used since i got my Note3 phone.
Any suggestion for what i should try? Im open for everything.

rvenes said:
I'm not really sure what boot loader i have.
Maybe the one i have is to old?
Click to expand...
Click to collapse
Yes, that can be the reason.

_that said:
Yes, that can be the reason.
Click to expand...
Click to collapse
LOL
Yes, that and wrong recovery, no or insufficient wipes before flashing the new rom - lots of possibilities.
Before you fire into the trash send it to me! I could use a tablet to recklessly experiment on

rvenes said:
Hello.
I've been experimenting with my TF700t now.
Tried to install CM11, and it got random reboots all the time. I needed Clockwork so i recovery (had twrp before). I finally managed to get past the setup (basically skip and next on all settings) but it was "ready" it still freezes and random reboots.
I'm not really sure what boot loader i have.
Maybe the one i have is to old?
I had CleanRom before i started playing around with it.
If i cant fix it the trash bin is very close, but if i can get it to work again it would be nice.
It haven't been much used since i got my Note3 phone.
Any suggestion for what i should try? Im open for everything.
Click to expand...
Click to collapse
No trash! The TF700 is an awesome tablet.
I would start over. Go to the Zombi-X thread and install that rom, *after* making sure you've got the boot loader mentioned in the first posting in that thread. Then, install TWRP (the latest version rather than the 2.6 one mentoined in the thread -- I think it is up to 2.8.01 or so). Then install Zombi-X. If you have an external micro-sd card, go for the ROM2SD install as well. If not, no worries. You'll be so glad you did. But again, the Zombi-X thread will step you through the entire process. They've done a fantastic job. And your tablet will impress.

I haven't had time to look at it yet! So many other gadgets to use.
Will find time sometime this xmas.

If you were on CleanROM, you're bootloader is probably way too old.
Also you HAVE to do a clean install = wipe of cache, Dalvik and data before installing a new rom.