Is there any way to do this without having to do a factory wipe?
It may be possible, however it is HIGHLY recommended to do a factory reset in recovery. If you choose not to, I do not even want to think about what will crash going from Honeycomb to JellyBean 4.2/4.3
Here is what I would do. First, install GooManager from the play store. Update the recovery to TWRP 2.3.2.3. I have seen a LOT of users with issues using CWM on android 4.2 and later. Some swear it works great, but I would not trust it myself. After installing the GooManager, tap the menu button in the top right and choose the Install OpenRecovery Script.
Next, use Titanium Backup to back up your user apps. Do not back up system apps. Restoring these can cause some issues on newer versions of Android, especially since there are no Jelly Bean ROMs based on stock Asus Firmware.
Download your ROM of choice, and any GAPPS or kernels that you want to install.
Boot to recovery.
Backup your current setup as a fail safe.
Next, wipe the following partitions:
Cache
Davlik Cache
System
Data (Factory Reset). This will wipe the /data/ partition without wiping /data/media/ (aka /sdcard/) so your files on the internal storage will still remain. I would HIGHLY recommend doing a FORMAT DATA and fully wiping the /sdcard/ to help your device run faster. The files on /sdcard/ are not backed up by recovery's backup function so if you choose to do this be sure you backed up your entire /sdcard/ to microSD/SD/USB/PC/Cloud storage before formatting it.
Now go to the Install menu and install the ROM. Also install GAPPS and kernel if required.
I always wipe cache & davlik again after flashing then reboot. Set up the new ROM and then install TiBu and restore your apps. Once again, be sure not to restore any system apps or data as it can cause random reboots, SOD and app crashes.
Thanks for such a quick and detailed reply. I do have TB so that is not the problem. My problem is I do not want to lose my custom HUB that I created and am not sure how to back that up. Also I have been fairly happy with this HC rom other than a few browser crashes and the occasional overnight battery drain. Is JB that much better than HC?
thorin33 said:
Thanks for such a quick and detailed reply. I do have TB so that is not the problem. My problem is I do not want to lose my custom HUB that I created and am not sure how to back that up. Also I have been fairly happy with this HC rom other than a few browser crashes and the occasional overnight battery drain. Is JB that much better than HC?
Click to expand...
Click to collapse
It will be night and day.
As far as your HUBS, are you using a custom launcher? If so it should be backed up with the launcher settings. If not, you will have to set it up again....which I know how much time that takes.
frederuco said:
It will be night and day.
As far as your HUBS, are you using a custom launcher? If so it should be backed up with the launcher settings. If not, you will have to set it up again....which I know how much time that takes.
Click to expand...
Click to collapse
Plus 1. I hesitated to upgrade because I was "comfortable" with the ROM I was on (Megatron). I decided to update to KatKiss 4.3 mostly cause I was bored and wanted to flash something. Glad I did as it's a big different.:good:
Thanks again. I am using ADW and saved my configuration. I may just have to bite the bullet and just do it.
That is where I am at. I am very comfortable with this ROM and quite happy with it. Just wondering if the grass is greener.
thorin33 said:
That is where I am at. I am very comfortable with this ROM and quite happy with it. Just wondering if the grass is greener.
Click to expand...
Click to collapse
MUCH greener - Honeycomb is an ancient slow laggy build of Android, Jellybean is a fast smooth build
The user experience using Jellybean is immensely improved
Its the difference between Vista and 8.1, if not more, maybe XP > 8.1
Just make a Nandroid backup with TWRP recovery, then wipe everything, flash KatKiss #226 and Gapps and play around with it
Guarantee you will not want to return to HC
On the off chance you do want to return, just boot back into TWRP and restore your backup, you'll be back to exactly the state you were in when you made the backup, nothing lost
frederuco said:
It will be night and day.
As far as your HUBS, are you using a custom launcher? If so it should be backed up with the launcher settings. If not, you will have to set it up again....which I know how much time that takes.
Click to expand...
Click to collapse
Does anyone happen to know if my HUBS using ADW will look and act the same in JB?
thorin33 said:
Does anyone happen to know if my HUBS using ADW will look and act the same in JB?
Click to expand...
Click to collapse
I don't know anyone using HUBS myself. I am not sure how ADB works with JB. I moved on to APEX myself.
I think the BEST option is to make a backup of PRIME. Install, restore your apps (I would restore ADW last after all widgets and such are restored) and test it out.
If it does not work like you wanted, restore the PRIME backup in recovery and you will be right where you left off.
Well I figured I would give it a go. I installed Goo Manager and tried to install OpenRecovery. I just get the notifiation that it is downloading then a force close of Goo Manager. Not sure what to do now. I have tried to re-install Goo Manager but still get the same thing. I have rebooted, cleared Dalvik.
thorin33 said:
Well I figured I would give it a go. I installed Goo Manager and tried to install OpenRecovery. I just get the notifiation that it is downloading then a force close of Goo Manager. Not sure what to do now. I have tried to re-install Goo Manager but still get the same thing. I have rebooted, cleared Dalvik.
Click to expand...
Click to collapse
Use Easyflasher to flash TWRP, then Goo Manager to update it
http://forum.xda-developers.com/showthread.php?t=1688012
Or if Frederuco would be kind enough to link to his updated version, you can flash the newest TWRP in one shot
thorin33 said:
Well I figured I would give it a go. I installed Goo Manager and tried to install OpenRecovery. I just get the notifiation that it is downloading then a force close of Goo Manager. Not sure what to do now. I have tried to re-install Goo Manager but still get the same thing. I have rebooted, cleared Dalvik.
Click to expand...
Click to collapse
*Detection* said:
Use Easyflasher to flash TWRP, then Goo Manager to update it
http://forum.xda-developers.com/showthread.php?t=1688012
Or if Frederuco would be kind enough to link to his updated version, you can flash the newest TWRP in one shot
Click to expand...
Click to collapse
I was thinking the same thing.
See here:
frederuco said:
Since this tool has not been updated for newer recoveries, I repacked the zip with the two latest versions of TWRP:
EasyFlasher with TWRP 2.3.2.3
EasyFlasher with TWRP 2.5.0.0
EasyFlasher with TWRP 2.6.0.0
EasyFlasher with TWRP 2.6.1.0
EasyFlasher with TWRP 2.6.1.0-b This version has the microSD mounted as /MicroSD/ instead of /sdc/
EasyFlasher with TWRP 2.6.1.0-c This version has the the storage mounted as sdcard0 for internal storage and microSD is mounted as sdcard1
EasyFlasher with TWRP 2.6.3.0 Fixes the SuperSU nag during reboot.
NOTE - It STILL has the TWRP version listed as 2.2.1.1 in the dropdown, but it WILL INSTALL 2.3.2.3, 2.5.0.0 or 2.6.X.X I cannot update the dropdown.
I have tested all of these on my TF101 and all of them worked successfully.
Click to expand...
Click to collapse
You can follow my rooting guide here for detailed instructions on how to use EasyFlasher: http://www.transformerforums.com/fo...nt/31927-frederucos-guide-root-rom-tf101.html
frederuco said:
EasyFlasher with TWRP 2.6.3.0 Fixes the SuperSU nag during reboot.
Click to expand...
Click to collapse
Frederuco - do I have to use the EasyFlasher version with ADB to flash the TWRP 2.6.3.0? Although I updated to TWRP 2.6.3.0-c today and then updated to KatKiss 4.3 v24 and the nag hasn't appeared again (yet)
Theziggy said:
Frederuco - do I have to use the EasyFlasher version with ADB to flash the TWRP 2.6.3.0? Although I updated to TWRP 2.6.3.0-c today and then updated to KatKiss 4.3 v24 and the nag hasn't appeared again (yet)
Click to expand...
Click to collapse
If you have a custom recovery installed, just flash the zip file in sidneyk's TWRP thread to update to a different version.
http://forum.xda-developers.com/showthread.php?t=2434422
frederuco said:
If you have a custom recovery installed, just flash the zip file in sidneyk's TWRP thread to update to a different version.
http://forum.xda-developers.com/showthread.php?t=2434422
Click to expand...
Click to collapse
Oh I know how to flash the zip file Frederuco (as my sig shows - I have recently updated to 2.6.3.0-3 using this method), I was wondering what the advantage of the EasyFlasher version was - or is that for people who are just starting to root their tf101?
Theziggy said:
Oh I know how to flash the zip file Frederuco (as my sig shows - I have recently updated to 2.6.3.0-3 using this method), I was wondering what the advantage of the EasyFlasher version was - or is that for people who are just starting to root their tf101?
Click to expand...
Click to collapse
EasyFlasher is mainly to install a custom recovery when you are still stock so you can root and/or ROM and also to flash the stock firmware if you bricked your tablet and it won't boot to recovery or to a ROM.
It can be used to update to a newer version of TWRP or other recovery, but it is much easier to just flash the zip file in recovery as you do not need to have a PC to make it happen.
That's what I was kinda thinking Frederuco, thanks for clarifying it for me :good: :good: :good:
Finally found some time to do a little bit more on my upgrade path (Having a 5 month old sucks up most of my free time). I was able to just install the zip from sidneyk. Did my nandroid and hopefully will find time to flash Katkiss.
Thanks for all the help so far everyone.
I noticed that when I went to do my backup I got the following message:
Updating partition details
E: Unable to locate ui.xml in zip file
E: An internal error has occured.
It proceeded to backup and said it was successful. Is this normal?
TIA
Related
Hi Folks.
Ok here is my situation, I have a rooted and unlocked TF700.
I flashed Zeus 4 and all worked well, then flashed (after full wipe) PARANOIDANDROID 2.15 and again everything was great,
Yesterday I flashed Baked Bean 4 (again after a full wipe) and apart from some SD issues all seemed ok,
I then decided to restore my TWRP backup of Zeus as I needed to use my 64gig msd card.
After a full wipe and restore Zeus started up but the dpi was messed up (160) I think (way small)
I was seeing loads of FC's and file manager showed my internal SD as being empty. Rebooted to recovery and tried the "Format Data" option
It failed right away with this message "E: Unable to format data."
I have tried flashing the stock .26 rom via TWRP and I have the same issue, dpi set to 160 and internal sd not mounted.
It seems my Internal sd is corrupt
What is the procedure to reformat it via ADB or fastboot? (I have searched but the results I found relate to other devices and I dont want to simply follow instructions that might cause further harm to my TF700)
I have followed the NVflash brick proof procedure and have all relevant files backed up (I did this before flashing the last 2 roms)
Please can some one point me in the right direction
Thanks a lot
Jules
I always wipe cache, system, internal, davic and then do a factory reset.
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
When you said that you tried to flash the stock .26 you meant installing not restoring a backup, right? What rom you have on your device right now?
Pretoriano80 said:
When you said that you tried to flash the stock .26 you meant installing not restoring a backup, right. What rom you have on your device right now?
Click to expand...
Click to collapse
Yip extracted the zip from the zip file and copied it to my ext sd and flashed it via TWRP
I have an unusable Zeus4,
Im about to try a full wipe again and then flash .26 again
EDIT
After flashing .26 and selecting reboot I get the "No OS installed! Are you sure you wish to reboot?" message
Looks like the system partition is corrupted, but i'm not sure. I think you should come here on IRC and maybe someone with more experience will help you - - http://webchat.freenode.net/?channels=asus-transformer
Thanks so much Pretoriano80!
With his help on IRC I was able to solve the problem,
In the end I had to return to complete stock, It seems CM10 caused some problems,
You are a a legend dude Thanks!!
:good:
ZaJules said:
Thanks so much Pretoriano80!
With his help on IRC I was able to solve the problem,
In the end I had to return to complete stock, It seems CM10 caused some problems,
You are a a legend dude Thanks!!
:good:
Click to expand...
Click to collapse
This same thing happened to me with my Prime when I was getting ready to send it off for RMA because of a broken HDMI port. Since I was unlocked I was advised to restore to stock before sending it in. However, before I got the chance to do that I started getting the "E: Unable to format data." error that you were. I ended up erasing all partitions from fastboot and putting a note in the box that it wouldn't boot after an OTA. I managed to get away with it and wasn't charged for fixing it
For future reference it would be really helpful to know how you fixed this. Did you do something like what is in this thread: http://forum.xda-developers.com/showthread.php?t=1803343.
Did you ever figure out how CM10 messed up your Infinity? I was running CM9 on my Prime when I got this error. Thanks!
It's hard to say if it was CM10 (or any other custom rom) or TWRP to mess the things up but we managed to get back to stock by replacing the twrp with CWM recovery and installing a modified .30 update package. Was a tricky one but we didn't had to mess with the partitions and that's good.
Pretoriano80 said:
It's hard to say if it was CM10 (or any other custom rom) or TWRP to mess the things up but we managed to get back to stock by replacing the twrp with CWM recovery and installing a modified .30 update package. Was a tricky one but we didn't had to mess with the partitions and that's good.
Click to expand...
Click to collapse
Why did you switch to CWM? Do you have any thoughts on the advantages and disadvantages of TWRP vs CWM?
paddycr said:
Why did you switch to CWM? Do you have any thoughts on the advantages and disadvantages of TWRP vs CWM?
Click to expand...
Click to collapse
Switched to CWM just to make sure it wasn't twrp recovery that somehow was failing to flash the partitions correctly. Tbh so far both do their job and both share the same limitation so far, meaning both fail to restore the boot partition (kernel) so in order to restore successfully (from a nandroid backup) you need to flash the right kernel after restoring is done. Otherwise i like TWRP better and never had issues with it, but i miss the advanced option from CWM, the one that let you format each partition individually.
Pretoriano80 said:
Switched to CWM just to make sure it wasn't twrp recovery that somehow was failing to flash the partitions correctly. Tbh so far both do their job and both share the same limitation so far, meaning both fail to restore the boot partition (kernel) so in order to restore successfully (from a nandroid backup) you need to flash the right kernel after restoring is done. Otherwise i like TWRP better and never had issues with it, but i miss the advanced option from CWM, the one that let you format each partition individually.
Click to expand...
Click to collapse
I'm not certain what you're referring to here. I've restored many times from different TWRP backups (for each custom rom that successfully boots and is half-decent, I make and keep a backup in case I want to jump around and try new things) and I've never had any issues. I am still on the .26 firmware update because I plan to do the nvflash thing. Are you saying that between Zeus v4 (ICS) and various Jelly Bean roms I've been on the same kernel? I gues I just haven't checked.
Anyway, I really love the TWRP recovery and use it with Xoom and Nexus 7 as well. It's so easy to use and always has been reliable.
okantomi said:
I'm not certain what you're referring to here. I've restored many times from different TWRP backups (for each custom rom that successfully boots and is half-decent, I make and keep a backup in case I want to jump around and try new things) and I've never had any issues. I am still on the .26 firmware update because I plan to do the nvflash thing. Are you saying that between Zeus v4 (ICS) and various Jelly Bean roms I've been on the same kernel? I gues I just haven't checked.
Anyway, I really love the TWRP recovery and use it with Xoom and Nexus 7 as well. It's so easy to use and always has been reliable.
Click to expand...
Click to collapse
For me moving between various roms by just restoring a backup never worked like it should. Let's say i'm on CM10 and i want to restore from a stock rom backup, the restore process is done, after reboot the device gets stuck to the first Asus screen and will stay there. Now if i get back to recovery and flash an update. zip containing the stock kernel the device will boot just fine, so definitely the boot image doesn't get restored in my case (with . 26 bootloader ).
Edit: @okantomi: You are using the internal storage or a MicroSD for backup / restoring? I'm really curious how this could work for some and not work for others, i mean same device, same recovery, same bootloader version...
Pretoriano80 said:
For me moving between various roms by just restoring a backup never worked like it should. Let's say i'm on CM10 and i want to restore from a stock rom backup, the restore process is done, after reboot the device gets stuck to the first Asus screen and will stay there. Now if i get back to recovery and flash an update. zip containing the stock kernel the device will boot just fine, so definitely the boot image doesn't get restored in my case (with . 26 bootloader ).
Edit: @okantomi: You are using the internal storage or a MicroSD for backup / restoring? I'm really curious how this could work for some and not work for others, i mean same device, same recovery, same bootloader version...
Click to expand...
Click to collapse
Ok, I only flash a new zip from the internal storage...made myself a "Flashworthy" folder which I keep stocked with newest versions of roms/gapps. I save my TWRP backups to my external microsdcard, as well as my TiBu backups. I have never had a problem restoring from TWRP this way, honestly.
okantomi said:
Ok, I only flash a new zip from the internal storage...made myself a "Flashworthy" folder which I keep stocked with newest versions of roms/gapps. I save my TWRP backups to my external microsdcard, as well as my TiBu backups. I have never had a problem restoring from TWRP this way, honestly.
Click to expand...
Click to collapse
Well, in this case i really have no clue why restoring works for some users but not for all.Dees_Troy, the dev behind Twrp recovery told me that .26 bootloader is to blame for the recovery failing to restore the boot partition, but looks like you have that bootloader version and restoring works good for you... interesting.
Pretoriano80 said:
Well, in this case i really have no clue why restoring works for some users but not for all.Dees_Troy, the dev behind Twrp recovery told me that .26 bootloader is to blame for the recovery failing to restore the boot partition, but looks like you have that bootloader version and restoring works good for you... interesting.
Click to expand...
Click to collapse
It is a mystery. Is there any other info that might be relevant to see why the difference in results? I ask because I would like to understand this device better, as well as potentially help others.
okantomi said:
It is a mystery. Is there any other info that might be relevant to see why the difference in results? I ask because I would like to understand this device better, as well as potentially help others.
Click to expand...
Click to collapse
I don't know, maybe the twrp version and the backup options, like if you are using compression or not, which partitions do you backup (boot, system, data, recovery, cache)...
Pretoriano80 said:
I don't know, maybe the twrp version and the backup options, like if you are using compression or not, which partitions do you backup (boot, system, data, recovery, cache)...
Click to expand...
Click to collapse
I'm using TWRP 2.2.2.1, I back up boot, system and data only, and I don't use compression.
First, I have H-BOOT 1.09, and I am rooted, I have TWRP v3
Now, I had ViperROM 1.2.0 installed, and decided to install Trickdroid v7, and it failed. I thought it was weird, so I restarted the phone. It was just on the boot screen, and after rebooting into Recovery, I noticed that when I tried rebooting, it would say that no OS was installed.
I downloaded ViperROM 1.2.0 and checked the MD5 and it checked out. Thinking they might of fixed the Aroma full wipe, I ran it with a full wipe, and of course it didn't work. So, I rebooted into recovery, wiped Cache, Dalvik, Factory and System. Tried installing ViperROM again, this time with out the full wipe, it gets to 7% and then ask me to reboot. If I try rebooting, it tells me no OS is installed. Right now I am running CM10 but I don't want it. I want ViperROM.
I had this same issue before, but I was exactly sure what I did in order to get it to install. So now I am stumped, and I don't know how to use ADB.
If you use latest TWRP 2.3.x, it will not work. You need to go back to TWRP 2.2.2.0
cat2115 said:
If you use latest TWRP 2.3.x, it will not work. You need to go back to TWRP 2.2.2.0
Click to expand...
Click to collapse
I feel really stupid because I didn't check the last 30 pages of that topic, although it seems its because System is mounted, which I had absolutely no idea WTF that meant.
Does that mean that the latest TWRP is the reason why Trickdroid didn't install?
I could never get either to install using any version of TWRP and i'm on hboot 1.06. I always had to fastboot flash the boot.img first, clear caches. It's weird and no one involved could explain it...been flashing other ROMs fine via TWRP 2.3
Hgaara said:
I feel really stupid because I didn't check the last 30 pages of that topic, although it seems its because System is mounted, which I had absolutely no idea WTF that meant.
Does that mean that the latest TWRP is the reason why Trickdroid didn't install?
Click to expand...
Click to collapse
If you download gooManager from Play. it will install the latest TWRP. If you need TWRP 2.2.2.0, you can find it in ToolKit Rooting. Inside the folder there' s a TWRP 2.2.2.0
Use that img and do a fastboot
fastboot flash recovery TWRP.img
Click to expand...
Click to collapse
Hope this help you.
Or you can try
older devices will probably encounter several zips that need to be updated. If needed, you can try using this update-binary that was compiled with current sources. It goes in your zip file in the META-INF/com/google/android folder.
Click to expand...
Click to collapse
at http://forum.xda-developers.com/showthread.php?t=1677670&highlight=twrp+recovery
below "CHANGELOG for 2.3.0.0:" you find a download link to "update-binary"
Hi All,
I have posted this on the GooManager thread but there hasn't been much activity there recently so asking here as well. Noob question on GooManager...I have the AOKP rom installed on my Sensation and GooManager notifies me of updates to my ROM every now and then. I just want to know if updating my ROM build with GooManager will reset all my custom ROM settings and preferences or will they all be preserved? I'd like to keep my ROM up to date but if it means spending all the time again to setup my preferences and icons/widgets/home screens etc. then I'd rather stick with what I have.
TIA!
I'd recommend to use GooManager only to download the newest ROM and flash it from recovery.
I asume you're using AOKP Swagger from frankenstine, the same I use.
I just download the update from GooManager, boot to recovery, flash ROM, gapps and 4.2 stuff and are ready to go.
All my settings are their after updating - only AdAway needs a reconfiguration and a reboot (and I need to set my alarm clock since I'm overwriting that). Basically you keep all your settings except those you made to the kernel.
Regards
lolmachine4 said:
I'd recommend to use GooManager only to download the newest ROM and flash it from recovery.
I asume you're using AOKP Swagger from frankenstine, the same I use.
I just download the update from GooManager, boot to recovery, flash ROM, gapps and 4.2 stuff and are ready to go.
All my settings are their after updating - only AdAway needs a reconfiguration and a reboot (and I need to set my alarm clock since I'm overwriting that). Basically you keep all your settings except those you made to the kernel.
Regards
Click to expand...
Click to collapse
Oh perfect, yes indeed I am using that exact ROM.
OK so when I boot to recovery, I shouldn't do any wiping? Just simply flash the new file? Will the updated gapps package be in the download I get from GooManager?
freddysensation said:
Oh perfect, yes indeed I am using that exact ROM.
OK so when I boot to recovery, I shouldn't do any wiping? Just simply flash the new file? Will the updated gapps package be in the download I get from GooManager?
Click to expand...
Click to collapse
I only wipe dalvik & cache after each update.
I can't say something about what GooManager downloads as "gapps", I use some I downloaded some weeks ago + some old version of 4.2 stuff. I might need to update my flash-setup too
lolmachine4 said:
I only wipe dalvik & cache after each update.
I can't say something about what GooManager downloads as "gapps", I use some I downloaded some weeks ago + some old version of 4.2 stuff. I might need to update my flash-setup too
Click to expand...
Click to collapse
Thanks lolmachine, for the benefit of anyone who might have the same question as me the following worked:
- Downloaded latest build of my AOKP Rom via GooManager
- Downloaded latest gapps package for my ROM via GooManager
- Boot to Recovery
- Flash new ROM file and then gapps package
- Restart.
My only question is, I didn't wipe davlik and cache so should I, and what difference does it make if I don't?
I used Goo the other day to flash, ummm, bugger, can't remember if it was an update or a new rom.
Oh now I remember, the latest one was an update to Bruce's Rom. I do believe when I tapped flash rom it booted to recovery (the one it installs) and I may have had to select "Install" from there, don't think so though. Either way, I used Goo to handle the install.
I didn't do a wipe. From what I've picked up, wiping is a good way to cover your butt. So if you're having issues and didn't wipe, you go back and do it all again with a wipe. Doing the wipe to start with means you can eliminate those types of issues from the start.
Someone can correct me if I'm wrong (which I probably am )
Hi there, I also received an update to my ROM via Goo Manager. It is CyanogenMod 10.1 by Albinoman887 for my HTC Sensation XE. I am using the EXT4 bootloader. I just installed it a few nights ago so I am completely new to rooting. My question is that there is no option to wipe dalvik cach. EXT4 just says wipe cache, wipe data and wipe system. Does wipe cache wipe dalvik cache as well. Also do I need to re-flash gapps as well after updating and will this wipe my gmail accounts etc?
Thanks,
Adam
thisisadamh said:
Hi there, I also received an update to my ROM via Goo Manager. It is CyanogenMod 10.1 by Albinoman887 for my HTC Sensation XE. I am using the EXT4 bootloader. I just installed it a few nights ago so I am completely new to rooting. My question is that there is no option to wipe dalvik cach. EXT4 just says wipe cache, wipe data and wipe system. Does wipe cache wipe dalvik cache as well. Also do I need to re-flash gapps as well after updating and will this wipe my gmail accounts etc?
Thanks,
Adam
Click to expand...
Click to collapse
You want to select "wipe dalvik+cache" option when you flash an update.
There's no need to flash gapps after a ROM update.
Sent from my Ouya
AndroidSupporter318 said:
You want to select "wipe dalvik+cache" option when you flash an update.
There's no need to flash gapps after a ROM update.
Sent from my Ouya
Click to expand...
Click to collapse
Thanks very much, downloading it now.
Help
im using albinoman's jelly bean rom
excuse me for noob doubts but
1) goo manager shows i have an update, so ive downloaded it. its a zip just like the rom n not just a small update. i have downloaded it now what should i do?
2) if i have to go to the recovery and flash the zip then i have to wipe only the cache right? Im using 4ext recovery.
3) will all my apps get uninstalled? what about the app data?
4) what about gapps? i have a gapps zip file, will i have to flash it again after the update?
Please reply thanks
I finally rooted phone after silly VMUNE7 thing on Verizon but after I get the install openrecoverscript and hit reboot recovery it does not go to teamwiz bootload instead I get something with a green driod on the bottom saying downloading but above it saying in red can't download Odin mode?? Please help I want to run cleanrom for better battery and less bloatware and keep my touchwiz. :crying:
all3rd said:
I finally rooted phone after silly VMUNE7 thing on Verizon but after I get the install openrecoverscript and hit reboot recovery it does not go to teamwiz bootload instead I get something with a green driod on the bottom saying downloading but above it saying in red can't download Odin mode?? Please help I want to run cleanrom for better battery and less bloatware and keep my touchwiz. :crying:
Click to expand...
Click to collapse
sorry man but i think you are talking for a samsung device am i right?
if yes then this is only for sensation/XE/4G devices
yasho170 said:
im using albinoman's jelly bean rom
excuse me for noob doubts but
1) goo manager shows i have an update, so ive downloaded it. its a zip just like the rom n not just a small update. i have downloaded it now what should i do?
2) if i have to go to the recovery and flash the zip then i have to wipe only the cache right? Im using 4ext recovery.
3) will all my apps get uninstalled? what about the app data?
4) what about gapps? i have a gapps zip file, will i have to flash it again after the update?
Please reply thanks
Click to expand...
Click to collapse
Simple.
Go to recovery.
For s-on you must enable smartflash.
Do a nandroid backup.
Dirty flash the update (meaning flash over the previous rom without wiping).
Dirty flash gapps (signed only).
Wipe cache + dalvik.
Reboot.
If it can't boot/run properly then you can just restore the backup or do a clean flash.
First off I'm not experienced in any way, got my Sensation unlocked, rootet and installed Sultanxda's 4.4.2 ROM for sensation. I'm on S-On, too, if anyone wonders.
Updating didnt affect my apps as far as I can tell. Everything seems to be the way as before and everything seems to be working.
What I did was download the ROM manually since the download with goomanager didn't work. I downloaded gapps as backup because I didnt have the zip on my SD, just in case anything would go wrong.
You only need to boot into recovery, with S-On make sure smartflashing or something like that is on, select the zip, flash it and then select wipe cache +dalvik.
It's pretty much what AndroidSupporter318 wrote, just wanted to give feedback and say what I did in detail in case anyone was still wondering.
LxMaD
I guaranted 4EXT Recovery for this type of problem. U don't need to boot into recovery and work with 4ext is very simple.
Looking for some input on clean ROM on the TF300T,
This is my second time trying to install it and both times it was successful, however as soon as the boot image loads up it stays stuck loading... I did download the file again thinking it may have been corrupted.
It has been sitting there loading for 20 minutes now.
I am using cwm the latest version and I did not install a kernel still running stock
Any ideas on what could cause this?
chibra said:
Looking for some input on clean ROM on the TF300T,
This is my second time trying to install it and both times it was successful, however as soon as the boot image loads up it stays stuck loading... I did download the file again thinking it may have been corrupted.
It has been sitting there loading for 20 minutes now.
I am using cwm the latest version and I did not install a kernel still running stock
Any ideas on what could cause this?
Click to expand...
Click to collapse
CWM has issues on this unit. Many, many complaints. I use twrp. If you decide to use twrp be sure to choose JB and tf300t version.
Clean ROM is freaking amazing! Seriously just do it I love the mods I can make for it too! Can't wait till I get my volume long press seek mod done! Love this device!
Sent from my SGH-T999
"So I put my phone into airplane mode and threw it... worst transformer ever. -.-" -My friend
tobdaryl said:
CWM has issues on this unit. Many, many complaints. I use twrp. If you decide to use twrp be sure to choose JB and tf300t version.
Click to expand...
Click to collapse
I initially when i first rooted intalled Twrp however i was not able to flash anything at all with it, it would give me errors.... that is the only reason i went to cwm.... I was able to make backups and restores with but ROMs flashing would just fail
chibra said:
I initially when i first rooted intalled Twrp however i was not able to flash anything at all with it, it would give me errors.... that is the only reason i went to cwm.... I was able to make backups and restores with but ROMs flashing would just fail
Click to expand...
Click to collapse
OK. It was just a suggestion since the problem you are experiencing is usually cleared by using twrp.
oryhight sullivan
tobdaryl said:
OK. It was just a suggestion since the problem you are experiencing is usually cleared by using twrp.
Click to expand...
Click to collapse
i m going to give twrp another shot...
i installed http://tinyw.in/5foT
JB version for the TF300T
This is the Rom i m trying to install
http://forum.xda-developers.com/showthread.php?t=2049322
Kernel is still stock and i ve left it that way through the aroma installer
Everytime i flash and reboot i get a boot loop
chibra said:
i installed http://tinyw.in/5foT
JB version for the TF300T
This is the Rom i m trying to install
http://forum.xda-developers.com/showthread.php?t=2049322
Kernel is still stock and i ve left it that way through the aroma installer
Everytime i flash and reboot i get a boot loop
Click to expand...
Click to collapse
I'm sorry it is hard to tell since you have chosen an older twrp to install. The current is five versions later and was updated as the kernels were updated to account for changes. The rom you are flashing is based on 10.4.4.25.
chibra said:
i installed http://tinyw.in/5foT
JB version for the TF300T
This is the Rom i m trying to install
http://forum.xda-developers.com/showthread.php?t=2049322
Kernel is still stock and i ve left it that way through the aroma installer
Everytime i flash and reboot i get a boot loop
Click to expand...
Click to collapse
Use TWRP 2.4.1.0
You are using a very old version of TWRP that has bugs with AROMA installer. So that is most likely where your issues are.
What ROM are you ccoming from? What boot loader are you on.
Sounds to me like you need to upgrade your boot loader and possibly do a full wipe - make sure you are on latest TWRP first otherwise you could brick if you use an older recovery!
sbdags said:
What ROM are you ccoming from? What boot loader are you on.
Sounds to me like you need to upgrade your boot loader and possibly do a full wipe - make sure you are on latest TWRP first otherwise you could brick if you use an older recovery!
Click to expand...
Click to collapse
Wise words. Nobody likes to listen to me so im glad someone else suggested it!
elesbb said:
Use TWRP 2.4.1.0
You are using a very old version of TWRP that has bugs with AROMA installer. So that is most likely where your issues are.
Click to expand...
Click to collapse
Updated the TWRP to the version you mentioned still stuck in boot loop.
sbdags said:
What ROM are you ccoming from? What boot loader are you on.
Sounds to me like you need to upgrade your boot loader and possibly do a full wipe - make sure you are on latest TWRP first otherwise you could brick if you use an older recovery!
Click to expand...
Click to collapse
The only ROM i was able to flash that was fully functioning is cm10.1,
i have also flashed PA 2.9 but had some bugs i couldn't stand (screen rotation not working, extended desktop with no pie)
as for boot loader it says 1.00e by "US _Epad-10.4.2.20-20121228" A03
I just updated the TWRP as recommended on the other post (v2.4.1.0)
on every flash i wipe dalvik / Cache / Factory reset.
Before attempting to boot into Clean Rom i also followed the steps on screen saying to wipe cache and dalvik.
I m hoping PA releases a 3.0 for this device and/or i m able to get Clean rom running
chibra said:
The only ROM i was able to flash that was fully functioning is cm10.1,
i have also flashed PA 2.9 but had some bugs i couldn't stand (screen rotation not working, extended desktop with no pie)
as for boot loader it says 1.00e by "US _Epad-10.4.2.20-20121228" A03
I just updated the TWRP as recommended on the other post (v2.4.1.0)
on every flash i wipe dalvik / Cache / Factory reset.
Before attempting to boot into Clean Rom i also followed the steps on screen saying to wipe cache and dalvik.
I m hoping PA releases a 3.0 for this device and/or i m able to get Clean rom running
Click to expand...
Click to collapse
If you are coming from cm10.1 you will definitely need to do a full wipe as it is non stock. It does say this in the first post. You only do a dalvik and cache wipe when upgrading from the same ROM or in CROMI's case from stock.
Do a data wipe in recovery, make sure you have a titanium backup or equivalent if you want to restore apps.
Success!!!
It worked perfectly fine after i install the back up i did before i flashed my 1st costume rom,
I rooted made a back up at stock/rooted... It just would not install from a full wipe,
it install fine once i flashed that specific backup and dirty flashed then wiped dalvik and cache before booting.
Hello!
I am sorry if this is the incorrect place to post, but I have a very annoying issue with my OnePlus One!
A few days ago I took the OTA update from Android 4.4.4 all the way to 5.1.1. However, there are quite a few bugs with this version, and the "Material UI" is seriously getting on my nerves so I would like to revert back to my previous version. This should be doable because I performed a Nandroid backup with TWRP before updating the phone. My backup is saved on a USB stick which I connect to the phone via a USB OTG cable, which is perfectly mountable in the Recovery.
My phone is rooted and WAS running TWRP Recovery before I upgraded to Lollipop, this replaced TWRP with Cyanogens stock. When I re-rooted my phone I had to reinstall a custom recovery. For some reason, ADB installing TWRP was just not working (No errors, it just didnt install no matter what) so I opted to try a CWM recovery which did the trick.
Now my issue is that my recovery is unable to mount /sdcard which prevents it from performing backups or restores.
I could really use some help here.
Did you update your backup (TWRP?) as well? What version of it are you on?
JeffDC said:
Did you update your backup (TWRP?) as well? What version of it are you on?
Click to expand...
Click to collapse
I am not sure what you mean by updating the backup. The backup is backed up and left in the state it was when I took it, that is to say Android 4.4.4 and the version of TWRP (The date I installed TWRP the first time) is mid February 2015.
The phones recovery right now is PhilzRecovery which as far as I understand is CWM. Latest version.
Try installing twrp from the CWM recovery.. And before restoring the phone from nandroid try installing the clean stock rom at 4.4.4 and then do the nandroid restore.
Sent from OPO using Tapatalk
Press on thanks if I helped you
ashuthosh.heda said:
Try installing twrp from the CWM recovery.. And before restoring the phone from nandroid try installing the clean stock rom at 4.4.4 and then do the nandroid restore.
Sent from OPO using Tapatalk
Press on thanks if I helped you
Click to expand...
Click to collapse
And to do this, I would just drop the .img for TWRP into my phones storage and chose it from inside the recovery? Would this really work? It might be my inexperience, but it sounds somewhat risky.
NodCom said:
And to do this, I would just drop the .img for TWRP into my phones storage and chose it from inside the recovery? Would this really work? It might be my inexperience, but it sounds somewhat risky.
Click to expand...
Click to collapse
Don't know if CWM recovery supports installing img. Twrp supports img flashing. Check the features of CWM recovery and proceed.
Sent from my A0001 using Tapatalk
ashuthosh.heda said:
Don't know if CWM recovery supports installing img. Twrp supports img flashing. Check the features of CWM recovery and proceed.
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
Well... I am not sure how I just managed this, but I was tinkering about inside my TWRP application and tried the "Install TWRP recovery" setting a second time (I tried it before making this thread, the first time it failed), it actually was successful because it booted into TWRP. From here I selected the TWRP-backup I kept and it installed it successfully (With one note, that it during the installation said something among the lines of "Restoring backup without deleting /data/media" or something like that. The phone rebooted itself after it finished updating, and the old Cyanogen/OPO bootanimation plays. But at login (My device is encrypted since long) it tells me my password is incorrect?!
How could this to happen? I've only ever used a single password (numbers only) for my phone encryption. This is very odd.
NodCom said:
Well... I am not sure how I just managed this, but I was tinkering about inside my TWRP application and tried the "Install TWRP recovery" setting a second time (I tried it before making this thread, the first time it failed), it actually was successful because it booted into TWRP. From here I selected the TWRP-backup I kept and it installed it successfully (With one note, that it during the installation said something among the lines of "Restoring backup without deleting /data/media" or something like that. The phone rebooted itself after it finished updating, and the old Cyanogen/OPO bootanimation plays. But at login (My device is encrypted since long) it tells me my password is incorrect?!
How could this to happen? I've only ever used a single password (numbers only) for my phone encryption. This is very odd.
Click to expand...
Click to collapse
I guess it's a side effect of restoring up a backup of 4.4.4 on lollipop. Try factory reset from twrp and then flash the backup. I would still suggest to first install the stock firmware of 4.4.4 and flash it and then do a restore of 4.4.4.
Sent from OPO using Tapatalk
Currently on Resurrection Remix
Thank me if I helped you.
Also make sure you are using the most recent version of TWRP, as it provides better 'outs' and reliability for newer OP OS versions.