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
Related
I have transformer tf101 (Honeycomb 3.2.1 + 16GB + Dock) that I purchased in August 2011. For first 6 months I was on stock ROM and everything was working fine. After that I flashed Android Revolution HD 2.2.0 on my tablet and then it started behaving crazily . Whenever I open browser it will automatically start zooming in/out, scrolling. It will totally go haywire and will start clicking left/right.
I searched on net and found that some of other unlucky guys are facing the same issue . I have attached a .txt file that contains the link to you tube video depicting the problem.
I have tried many ways such as using superwipe script and then reinstalling the ROM's. Even, I have tried with new ROMS(ICS one's) that are there but still the problem does not seem to go away. I have searched a lot but could not find the solution to this issue. Can somebody please guide me how to get rid of this problem. I believe this is the best android forum where I am hoping that someone will help me with this problem.
This is really basic but have you tried cleaning the screen?
Other then that, have you tried going back to a HC rom and see if you don't have any issues. I understand you want the latest and greatest version rom but to determine a fix and narrow down the problem maybe you should try all the alternatives.
Thanks for replying. I had cleaned up my screen and there was not a single app/widget on my homescreens. I flashed back to HC ROM but still the problem persist . I have tried all ways of flashing th ROM's but still the problem doesn't seem to go away. I have not tried the stock ROM for HC that came with my tablet (i didn't take the backup when I flashed new ROM).
Looking at the issue it seems to me as if this problem is software related rather than the hardware.If this would have been hardware related then I should have got this on day1 of my purchase.
stryke504 said:
This is really basic but have you tried cleaning the screen?
Click to expand...
Click to collapse
I think he meant literally "clean the screen." Like with a towel and some cleaner.
typci said:
I think he meant literally "clean the screen." Like with a towel and some cleaner.
Click to expand...
Click to collapse
And dont forget to wash your hands (Im serious, that actually affects the responsiveness of the screen)
I cleaned my screen (Literally ). The problem is still there . Can it be because of the browser. I am currently using Dolphin HD browser for my browsing. I will probably install stock browser and will check with it.
Your text file is rubbish too...no link, it's actually the HTML code for an error 404..which is funny.......not only is it not a working link, or even a link at all, it's a 404 in HTML..LMAO
Sorry for the bad attachment. I have the link.doc containing the link.
Yesterday, I tried with the stock ROM and everything was working fine till the point I connected my tablet to Wifi and upgraded my Google Market to Play store. As soon as the app was updated the same problem started recurring. Now I have uninstalled the updates for google play store but the problem is still there. But the good part is that the frequency of the random zooming/clicking has decreased and it happens in browser only. Earlier it was happening in all the apps. Can somebody please direct me to the link to US stock ROM (for HC 3.2.1). As of now I am running WW_ stock rom. I just want to try out the same with US_ stock ROM as well.
First of all, don't use super wipe script. Just wipe normally with CWM.
Do these options in CWM
1. factory reset/wipe data
2. clear cache partition
3. wipe dalvik cache
4. mounts and storage -> format /system
5. mounts and storage -> format /data (this is done by factory reset but just to be sure)
Get the official ICS rom from Asus' website. US or WW doesn't matter.
Flash it with CWM after doing the wipe procedure above.
Don't let google sync or anything restore any kind of back up.
If the same problem happens again, you got a problem that requires RMA.
Honestly it already sounds like you need to RMA but you should make sure before wasting money and time on RMA.
I will try these steps today. I never did these 2 steps while flashing ROM's
1. clear cache partition
2. wipe dalvik cache
I am just curious to know as to how this problem started when it was not there till the point I flashed a custom ROM.
I have a big problem with RMA. I purchased my tablet in US and so it has North American Warranty. I am not residing in US. Thus for RMA, I have to ship my tablet back to US which will be expensive as well as an overhead . So I am planning of trying all the possible steps before I have to ask the Asus support in my native country. Please let me know if you know any stable version of Stock ROM. I read and found that some of the stock ROM's are having serious issues with Wifi/GPS etc.
harshbedi said:
I am just curious to know as to how this problem started when it was not there till the point I flashed a custom ROM.
Click to expand...
Click to collapse
Something could have gone bad during flashing.
What version of CWM are u using?
---------- Post added at 07:55 AM ---------- Previous post was at 07:51 AM ----------
harshbedi said:
I will try these steps today. I never did these 2 steps while flashing ROM's
1. clear cache partition
2. wipe dalvik cache
Click to expand...
Click to collapse
YOU HAVE TO DO THOSE. Wipe dalvik cache is under Advanced.
I am using CWM 3.2.0.1 for recovery.
I am just hoping that it should be software/flashing issue.I just don't want to go for RMA .
harshbedi said:
I am using CWM 3.2.0.1 for recovery.
I am just hoping that it should be software/flashing issue.I just don't want to go for RMA .
Click to expand...
Click to collapse
i would first get on the newest version of recovery:
http://forum.xda-developers.com/showthread.php?p=16557195
it is touch based, but i just went into cwm and the regular method of volume and power keys work fine. AND you have to store the rom on the internal sd card in order to flash, it can't access the external card once you update.
and personally i'd wipe EVERYTHING like 3 times seems kinda of the standard.. i'm super ocd so i wipe it all 5 times before i flash.. might want to pick up an ASOP rom like
EOS:
http://forum.xda-developers.com/showthread.php?t=1520764
or KANG:
http://forum.xda-developers.com/showthread.php?t=1542302
see how that works.. could always pick up the stock ASUS rom though
FYI: to flash those new EOS and KANG roms you NEED to be on that version of cwm i linked
I have tried with various ROM's that are there in Development section but the problem does not seem to go away. I will upgrade my CWM and will check with stock ROM first. Once this is done then I will go for other versions of ROM's.
Just a quick question, for flashing the stock ROM for ICS i.e 9.2.17, I have to download the firmware from ASUS website and then flash it normally the way we do for other ROM's ?
harshbedi said:
I have tried with various ROM's that are there in Development section but the problem does not seem to go away. I will upgrade my CWM and will check with stock ROM first. Once this is done then I will go for other versions of ROM's.
Just a quick question, for flashing the stock ROM for ICS i.e 9.2.17, I have to download the firmware from ASUS website and then flash it normally the way we do for other ROM's ?
Click to expand...
Click to collapse
All this could have been caused by you never wiping cache and dalvik cache.
Yea, download the ICS firmware from Asus website. It will be in a zip. You extract it once. It will have another zip. That's the flashable zip.
You flash it in CWM like you would do for any other ROM.
Yes, I never wiped cache and dalvik cache.
I will check this today and will post my observations. I am keeping my fingers crossed and hoping that this should solve the problem.
Thanks for the info.
Thanks horndroid for the lovely info...It worked.
I cleared the cache and dalvik cache and then I flashed the new revolution 3.2.0 (ICS) Rom and as of no complaints. I have been using the tablet continuously for last 3-4 hours and no issues as of now. I am hoping that it continues to work the way it is functioning right now. I am loving my transformer again . I will use it for few more hours and will update my observations. I am still keeping my fingers crossed.
Moreover, Revolution 3.2.0 is awesome(Thanks to Mike and his team). Very stable and the GPS is awesome. Sitting in my room it acquired my position(No Wifi) within seconds.
horndroid said:
YOU HAVE TO DO THOSE. Wipe dalvik cache is under Advanced.
Click to expand...
Click to collapse
Yes. This is worth pointing out again and again.
Most roms (in my experience) wont even boot unless you wipe cache and dalvik.
And the roms that do boot runs like ****.
Now I have used my tablet for 16 hours..No issues..Running perfectly fine. I believe wiping cache has solved the issue.
I was reading about dalvik cache and came to know that during boot Android always create this cache (if it is not there). So if this problem comes again, can I wipe the cache and dalvik cache without flashing a new ROM. Is this advisable?
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.
Hi all, I've been rooting and installing custom roms on lots of devices for a couple of years now. I didn't consider myself a noob after successfully getting cyanogen 9 or 10 on tenderloin and cm10.2 on tate.
However, it seems that I have completely missed something while installing EOS4 20130705-199 on the Motorola Xoom.
I had no problems with SDK install, adb, fastboot, got TWRP running w/ root. All this is from stock, mind you, if that makes any difference.
So then I decided to grab teamEOS's EOS4 and run that as the newest Android OS (that is arguably stable) that has been ported to the Xoom.
Well, I think I must have rebooted at a point that I wasn't supposed to, because I lost the ability to load the EOS-stingray-20130705-199.zip via ADB.
So I went into TWRP recovery and attempted to ADB sideload the rom file. Seemed to work for transferring, but after wiping caches and rebooting, I'm stuck on MOTO dual-core logo. I can get back into TWRP, though so I tried doing factory reset, wiping caches, and installing from an 8GB microSD card (/sdcard). Wiped caches again and then reboot... Same result, MOTO dual-core logo.
Ok, so now to barebones... Boot into fastboot mode and flash boot.img from EOS-stingray-20130705-199.zip and then boot back into TWRP and install rom again.... Same result, MOTO dual-core logo.
As you can probably guess at this point I'm getting a bit frustrated. I'm about ready to see how a Xoom flies when launched from a skeet clay launcher. Pull!..... BLAM! Just kidding, but I really do need to get this device back running.
Does anybody have any suggestions?
199 may be bad (and be why it's not booting), try EOS-stingray-20130617-197 instead.
Format system partition first (in TWRP it's in Wipe->advanced), factory reset, then flash the EOS-stingray-20130617-197.zip AND an appropriate Gapps. Do not factory reset after the rom or gapps (for various reasons I am to tired to go into.) Assuming you have a good copy of the 197 it should boot.
airesch said:
199 may be bad (and be why it's not booting), try EOS-stingray-20130617-197 instead.
Format system partition first (in TWRP it's in Wipe->advanced), factory reset, then flash the EOS-stingray-20130617-197.zip AND an appropriate Gapps. Do not factory reset after the rom or gapps (for various reasons I am to tired to go into.) Assuming you have a good copy of the 197 it should boot.
Click to expand...
Click to collapse
Thanks for the reply. I shall give -197 a try.
As an aside, you don't need to feel obligated to explain your reasons for suggestions (re: Do not factory reset). The advice alone is worth it's weight in gold.
Bad news.
I just downloaded -197 fresh from goo, in fact I did it twice because I couldn't believe the results.
It actually fails to install giving the error "cannot open zip file" -199 never did that.
I also tried -131 (cdma) just to prove to myself that I have the right model. Same results, MOTO logo no boot.
Can't actually believe i am saying this, looks like goo's version is corrupt (my md5 doesn't match theirs and I just looked up the cached version of the webpage and it has d81cded40671c9c0963f95273859dbdd (which is what mine is.)
I will try to pm you a link of the file I have on my dropbox in a bit.
Thanks for this AIRESCH
Your version of -197 is working perfectly.
I think we need to sound the alarm here at XDA, because there are going to be a bunch of pissed off people (like me) who think they have a good image to flash when actually they have a bin of gibberish!
Thanks again.
punishermoose said:
Thanks for this AIRESCH
Your version of -197 is working perfectly.
Click to expand...
Click to collapse
Excellent
punishermoose said:
I think we need to sound the alarm here at XDA, because there are going to be a bunch of pissed off people (like me) who think they have a good image to flash when actually they have a bin of gibberish!
Click to expand...
Click to collapse
Not sure this is necessary, goo has been replacing/upgrading hardware and may not have everything up yet (none of the files were there for a good week at the start of the month.) They may get the right files back up before too long. It does suck for anyone trying to get the files right now tho.
I'm glad your up and working.
Do not factory reset after the rom or gapps (for various reasons I am to tired to go into.)
As an aside, you don't need to feel obligated to explain your reasons for suggestions (re: Do not factory reset).
Click to expand...
Click to collapse
ah, but you don't learn if it's not explained
Reason is: the Xoom only has a 256MB system partition and unfortunately the OS+Gapps (which normally resides in system) as of 4.1 or 4.2 comes to well over this amount. The rom developers HAVE been (they are currently trying to change this) making it so that some of Gapps gets enough copied into the data partition to make everything fit and symlink the files back into system. This has the positive effect of being able to have everything work even without enough space. However the downside is that if you factory reset it will wipe out the files in the data partition, leaving broken symlinks pointing to nothing, and makes it so some of it doesn't work anymore (how much depends on what gapps your using.)
In short: We have awesome devs that are still trying to fix the problem, but their current solution requires you to re-flash gapps (at a minimum, i normally recommend re-flashing both system and gapps) after a factory reset (which is not the end of the world (unless you don't have them both anymore.))
Can someone please share a link with me or pm me please? I still haven't found a working copy of 197 anywhere.
Sent from my SAMSUNG-SGH-I717 using XDA Premium 4 mobile app
SgtTeabag said:
Can someone please share a link with me or pm me please? I still haven't found a working copy of 197 anywhere.
Sent from my SAMSUNG-SGH-I717 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I'm in the same boat. Need a good download/copy of 197, please! The goo.im 197 download is borked!!
Hi guys, I just registered @ xda because it looks like it's the only serious and feedback active community available. In 10 minutes I found most of the info I was looking for, but I still want to make sure what Im planning to do is fine before I mess up again. Here's the issue:
I was fooling around with the tablet and had just rooted it so I could get rid of some bloatware, and decided to go further and install cyanogen, just for the looks. So I got this thing cm-10.1-20130411-EXPERIMENTAL-p3110-M3 from the official site, which was I put on a folder inside the tablets storage (not on the 16gb SDcard it had in it). I downloaded Rom Manager and skipped through the "search and download rom" and went for the option of looking for it inside the SD card. I had the Backup options and the wipe cache and data ON.
So I proceeded and it booted, started to do the backup and at some final point it had an error, something like "could not backup Data!". I had the options of rebooting, some other stuff and the option of installing a rom from the SD Card. I went for it and searched for the .zip inside the storage, and installed it. It did it withouth trouble, and when it finishd it prompted me to install an update, which I didn't (don't know why).
Then, I went for the reeboot option and when it started I get the normal samsung's black screen with the device's name on it, but then I get a fast glitching image that sweeps through the screen and the cyanogen startup logo which gets stuck for ever.
Click to expand...
Click to collapse
Now Im past it, I can get to download or recovery mode, so I moved onto getting the original firmware so I can clean-install again. I got it from sammobile, chose the one belonging to Chile (that's where I got the tablet), and it's 729mb of data. The tablet is a Samsung Galaxy Tab 2 7.0 P3110
If I flash it with Odin will everything be fine? All I have to do is that thing in downloadmode when I rooted it, but with that 729mb file? Should I put it in the external SD or is it more convenient to place it in the internal storage?
I appreciate your help in advance, I know this is as basic as it gets but messing up again would cost me dearly, since I have to do other stuff.
forum.xda-developers.com/showthread.php?t=1900055 read here, all the information you will need.
It's fine to flash through odin, you will back at stock provided you don't overlook small details and do exactly like the way it is shown. Don't worry, Don't panic. Just be careful to use the files meant for your device only. Second be extra careful when you are dealing with kernel file, pit file or reparation in odin in future.
Third, get root and custom recovery,twrp.
Fourth, after your device start running take backup from twrp recovery. That will save you from most of the trouble.
Most of the details and instructions are already here
billysam said:
forum.xda-developers.com/showthread.php?t=1900055 read here, all the information you will need.
It's fine to flash through odin, you will back at stock provided you don't overlook small details and do exactly like the way it is shown. Don't worry, Don't panic. Just be careful to use the files meant for your device only. Second be extra careful when you are dealing with kernel file, pit file or reparation in odin in future.
Third, get root and custom recovery,twrp.
Fourth, after your device start running take backup from twrp recovery. That will save you from most of the trouble.
Most of the details and instructions are already here
Click to expand...
Click to collapse
hey thanks a lot, im feeling better ow. There's just one issue left: I cant download the original firmware (it's 699mb, and the download keeps stopping midway through it). What happens if I go into clockwork recovery mode and do a factory reset? would that bring me to the original OS? Im kinda scared of downloading an erroneous file again.
EDIT: im doing a factory reset and then flashing this rom called AOSP Project Android 5.1.1 Lollipop on Samsung Galaxy Tab 2 7.0 P3110 which is a 161mb file. Will that work?
aguscanzani said:
hey thanks a lot, im feeling better ow. There's just one issue left: I cant download the original firmware (it's 699mb, and the download keeps stopping midway through it). What happens if I go into clockwork recovery mode and do a factory reset? would that bring me to the original OS? Im kinda scared of downloading an erroneous file again.
EDIT: im doing a factory reset and then flashing this rom called AOSP Project Android 5.1.1 Lollipop on Samsung Galaxy Tab 2 7.0 P3110 which is a 161mb file. Will that work?
Click to expand...
Click to collapse
Factory reset is just clearing data and cache, if you have made changes in kernel or system, factory reset won't reset them, in your case, system has been altered so you will have to format system, then flash the new rom. If you were on jelly bean stock, you are good to flash it.
billysam said:
Factory reset is just clearing data and cache, if you have made changes in kernel or system, factory reset won't reset them, in your case, system has been altered so you will have to format system, then flash the new rom. If you were on jelly bean stock, you are good to flash it.
Click to expand...
Click to collapse
You guys have helped me a lot. I've worked everything out and now i've got to reinstalling android on it, AOSP's 5.1.1 Lollipop. It's beautiful. There's just one problem: Since it came with no apps at all, I wanted to install everything on it again. Problem is, when I go to google play, it shows that i've already got my apps installed, so it wont let me download them, and it doesn't matter if I place the APK's inside the tablet as there's no manager to open them. Even if I download apk's through the tablet's own web browser, it says it can't open the file. Any ideas on this?
So once in a while i reboot my tablet for optimizing purposes however when it boots up to android is starting.. It reboots again then hangs for a few sec and poof "Android process has stop" then its normal again.
Unlocked: yes
Rooted: yes
custom rom: yes - just the optimized rom with blob(pushed with fastboot)
Kernel: stock
Anything that i did wrong why it reboots again?
Did you flash anything besides the stock optimized(excluding the dtb?) Also do you wipe dalvik cache when you reboot, as I can't figure out why your tablet would be optimizing apps everytime you reboot?
Questions aside I would do a system, data, cache, dalvik cache wipe in your custom recovery and reflash the ROM to see if that fixes things. Just note to backup anything in your internel SD card if you decide to go the full wipe route instead. If you do a full wipe you'll need to flash the ROM from a external SD card or a USB via OTG.
Just a small disclaimer I would note to know what everything is doing before following my suggested potential fix if you choose to go that route. I'm guessing you do but just a friendly safety precaution!
Gapps(open) and the zip for xposed, respectively, thats it. Every week i purposely restart the device so everything is in good condition.
I did that before i installed the rom and etc. All the files where in the SD card am not putting any flashable files in the internal.
Bitcloud30 said:
Gapps(open) and the zip for xposed, respectively, thats it. Every week i purposely restart the device so everything is in good condition.
I did that before i installed the rom and etc. All the files where in the SD card am not putting any flashable files in the internal.
Click to expand...
Click to collapse
So you are using the Optimized Stock ROM from GtrCraft correct? If so I will tell you right now that Gapps does not need to be flashed with that ROM as it comes preloaded with Gapps and that could have possibly caused these errors(Any devs, correct me if I'm wrong here.) I would wipe system in that case, reflash the ROM, SuperSU, Xposed in that order and see if the problems exist. If that doesn't work I suggest doing what I suggested in my first reply. Android OS can go a little haywire over the smallest things and it seems something you flashed caused the problems you are having.
@KentuckyGuy447 will try that very soon! Yes that is the rom that i am using. No doubt about that but it lacks a more information about the rom xD, any how. Thanks for the help . I didnt know that in the first place cuz it didn't say anything about Gapps thats why i DL right away and installed above it.
Bitcloud30 said:
@KentuckyGuy447 will try that very soon! Yes that is the rom that i am using. No doubt about that but it lacks a more information about the rom xD, any how. Thanks for the help . I didnt know that in the first place cuz it didn't say anything about Gapps thats why i DL right away and installed above it.
Click to expand...
Click to collapse
Yeah I understand where your coming from. Just as future reference any ROM over the size of 350mb usually has a lot going on behind the scenes. I would try my suggested fixes and see if they will work. If not just notify us in your thread and I'm sure someone with more knowledge as I will try to help. Have a great day friend!