Related
Hey all still a newb here so posting the question here. Now Ive got myself to 3.2.2 rooted it and then got stock rooted 4.0.3 ics on it. Everything run sweet after ready threads I think the Team EOS build seems better.
So my question is how would I go to the build from what I have now. Ive read the thread but it lacking a bit of info and somewhat confusing. Im thinking I do a complete wipe from recovery (which is clockwork) then flash build zip from sd. then flash gapp.zip (google apps) from sd...
Is this correct? I just want to make sure.
Thanks everyone!
MYYZTIK said:
Hey all still a newb here so posting the question here. Now Ive got myself to 3.2.2 rooted it and then got stock rooted 4.0.3 ics on it. Everything run sweet after ready threads I think the Team EOS build seems better.
So my question is how would I go to the build from what I have now. Ive read the thread but it lacking a bit of info and somewhat confusing. Im thinking I do a complete wipe from recovery (which is clockwork) then flash build zip from sd. then flash gapp.zip (google apps) from sd...
Is this correct? I just want to make sure.
Thanks everyone!
Click to expand...
Click to collapse
This is correct.
Wipe Data (Factory Reset), wipe cache, wipe dalvik-cache and battery stats.
flash the build zip and gapp.zip from SD and you're all set.
thanks!
hoopsdavis said:
This is correct.
Wipe Data (Factory Reset), wipe cache, wipe dalvik-cache and battery stats.
flash the build zip and gapp.zip from SD and you're all set.
Click to expand...
Click to collapse
Battery stats eh? cool didnt know that one! Thanks man! Going to rock this now.
MYYZTIK said:
Hey all still a newb here so posting the question here. Now Ive got myself to 3.2.2 rooted it and then got stock rooted 4.0.3 ics on it. Everything run sweet after ready threads I think the Team EOS build seems better.
So my question is how would I go to the build from what I have now. Ive read the thread but it lacking a bit of info and somewhat confusing. Im thinking I do a complete wipe from recovery (which is clockwork) then flash build zip from sd. then flash gapp.zip (google apps) from sd...
Is this correct? I just want to make sure.
Thanks everyone!
Click to expand...
Click to collapse
If you have CWM recovery installed you can just flash the most current Eos nightly build --if you're wifi-only then it's wingray build #44, and then right after, flash the Eos GApps v 10.3. You will have to wipe your cache partitions and go to advanced and wipe dalvik cache. You might get away without a data wipe, but if things get unstable (due to new version of GApps) you'll have to wipe.
Make sure to make a nandroid backup first.
nice.
okantomi said:
If you have CWM recovery installed you can just flash the most current Eos nightly build --if you're wifi-only then it's wingray build #44, and then right after, flash the Eos GApps v 10.3. You will have to wipe your cache partitions and go to advanced and wipe dalvik cache. You might get away without a data wipe, but if things get unstable (due to new version of GApps) you'll have to wipe.
Make sure to make a nandroid backup first.
Click to expand...
Click to collapse
Thanks everyone for the help rocking EOS!
lol i just wish you didnt have to wipe everything....
lucky
alex94kumar said:
lol i just wish you didnt have to wipe everything....
Click to expand...
Click to collapse
I was lucky and hadn't put too much on it. So the wipe wasn't a big deal, if I'm right don't have to wipe every time to update build so was worth it. As a lot say my Xoom a lot snappier now. Would recommend doing it!
Wiping is usually the best way to go. There are workarounds, but the effort it takes to do so kinda outweighs the result.
so my question is....
im new over here, and fairly new to xoom and modding and what not.... anyway would i let the xoom update to 4.0.3 then flash to the nightly?
this is where im lost cause im on 3.2 right now, im unlocked, rooted and have cwm 3.2.0.0 ( US ver wifi only )
i want to finally get a custom rom on here but not sure what to go with?
TheLostXoom said:
im new over here, and fairly new to xoom and modding and what not.... anyway would i let the xoom update to 4.0.3 then flash to the nightly?
this is where im lost cause im on 3.2 right now, im unlocked, rooted and have cwm 3.2.0.0 ( US ver wifi only )
i want to finally get a custom rom on here but not sure what to go with?
Click to expand...
Click to collapse
I went from a rooted tiamat 3.2 rom to a nightly and it worked fine. I would do a wipe within clockwork recovery before flashin the new rom. Also remember to use titanium backup to backup your stuff first...
Sent from my ADR6350 using xda premium
bacon612 said:
I went from a rooted tiamat 3.2 rom to a nightly and it worked fine. I would do a wipe within clockwork recovery before flashin the new rom. Also remember to use titanium backup to backup your stuff first...
Sent from my ADR6350 using xda premium
Click to expand...
Click to collapse
the other thing is im trying to find a walkthough ish or something goin from 3.2 to the nightly.. i cant find to to much on this.. or maybe i havent searched enough anyway .... and i dont have anything installed right now on it other then the rom manager ....
so would i just go about flashin it the same as i did when i did the full restore? still a little confused
TheLostXoom said:
the other thing is im trying to find a walkthough ish or something goin from 3.2 to the nightly.. i cant find to to much on this.. or maybe i havent searched enough anyway .... and i dont have anything installed right now on it other then the rom manager ....
so would i just go about flashin it the same as i did when i did the full restore? still a little confused
Click to expand...
Click to collapse
Are you still rooted and do you have CWM recovery installed? If yes, it's easy to flash Eos ICS. You go to the correct thread for your device, download the latest Eos ICS rom, the latest Eos GApps v 10.3, put them on your micro sdcard (or internal storage, depending on what CWM recovery you have), boot into recovery, do a nandroid backup, do a data wipe/factory reset, wipe cache and dalvik cache, then flash the rom and the GApps zips one after the other all in the same recovery session, without a reboot inbetween. Then, reboot into Eos ICS goodness! Get all set-up and you're good to go. It will help if you do a full backup of all user apps and data in Titanium Backup and then, after your wipe, do a batch restore of "missing apps and data."
okantomi said:
Are you still rooted and do you have CWM recovery installed? If yes, it's easy to flash Eos ICS. You go to the correct thread for your device, download the latest Eos ICS rom, the latest Eos GApps v 10.3, put them on your micro sdcard (or internal storage, depending on what CWM recovery you have), boot into recovery, do a nandroid backup, do a data wipe/factory reset, wipe cache and dalvik cache, then flash the rom and the GApps zips one after the other all in the same recovery session, without a reboot inbetween. Then, reboot into Eos ICS goodness! Get all set-up and you're good to go. It will help if you do a full backup of all user apps and data in Titanium Backup and then, after your wipe, do a batch restore of "missing apps and data."
Click to expand...
Click to collapse
When first flashing a nightly a nandroid backup is recommended but it's not that necessary when going from your first nightly to another nightly. At least I don't do that because I'd rather hasten the whole data wipe/flash process and it works for me.
So I was running CM10.1 nightlies with Franco Kernel and decided to make the jump to CM10.2. The ROM and gApps flash went just fine, but like a dummy, I flashed the version of Franco kernel that I'd been using before, which I guess is not compatible with 4.3. The phone seemed to be softbricked and would just hang at the Cyanogen boot animation. I can get into recovery and I've tried to reflash both CM10.1 and CM10.2 - both hang at the boot animation. I can go back to my stock backup just fine, but then when I try to flash CM again (either version), I have the same hanging problem. Does CM store like a memory of the kernel that you have flashed and try to revert to that? Why can't I flash CM again once I've gone back to stock (and the stock kernel)? Would reflashing the stock image fresh (rather than using a TWRP backup) change anything? I'm pretty inexperienced with this and would appreciated any help. Thanks in advance!
alphamini said:
So I was running CM10.1 nightlies with Franco Kernel and decided to make the jump to CM10.2. The ROM and gApps flash went just fine, but like a dummy, I flashed the version of Franco kernel that I'd been using before, which I guess is not compatible with 4.3. The phone seemed to be softbricked and would just hang at the Cyanogen boot animation. I can get into recovery and I've tried to reflash both CM10.1 and CM10.2 - both hang at the boot animation. I can go back to my stock backup just fine, but then when I try to flash CM again (either version), I have the same hanging problem. Does CM store like a memory of the kernel that you have flashed and try to revert to that? Why can't I flash CM again once I've gone back to stock (and the stock kernel)? Would reflashing the stock image fresh (rather than using a TWRP backup) change anything? I'm pretty inexperienced with this and would appreciated any help. Thanks in advance!
Click to expand...
Click to collapse
Just to be sure how much juice was left while you were flashing CM rom?? Reading your problem I would suggest you to do a fresh Stock image installation and then try flashing CM 10.2.
Have you tried restoring your NANDROID backup, if you made one??
Rohit02 said:
Just to be sure how much juice was left while you were flashing CM rom?? Reading your problem I would suggest you to do a fresh Stock image installation and then try flashing CM 10.2.
Have you tried restoring your NANDROID backup, if you made one??
Click to expand...
Click to collapse
I have restored the NANDROID backup successfully, but unfortunately I was lazy and only have the backup from when I first got the phone.
I backed everything up with Titanium Backup right before I tried to flash CM10.2. If I do a complete stock reflash, do I lose all the data I backed up with TB? I do have some app data that I would really like to keep if possible.
One other resort I thought of was flashing a different custom ROM (Paranoid Android maybe?) and then restoring my TB backup. Would there be any reason that I shouldn't be able to reflash CM after I've restored the stock NANDROID?
alphamini said:
I have restored the NANDROID backup successfully, but unfortunately I was lazy and only have the backup from when I first got the phone.
I backed everything up with Titanium Backup right before I tried to flash CM10.2. If I do a complete stock reflash, do I lose all the data I backed up with TB? I do have some app data that I would really like to keep if possible.
One other resort I thought of was flashing a different custom ROM (Paranoid Android maybe?) and then restoring my TB backup. Would there be any reason that I shouldn't be able to reflash CM after I've restored the stock NANDROID?
Click to expand...
Click to collapse
Try this.
As you are able to go in recovery,
Wipe cache , dalvik cache, system, data install PA 3.97 flash pa_gapps then supersu v1.51(for root,also enable app+adb from developer option)
wipe cache and dalvck again and reboot..
P.S : Charge your battery first to 80% minimum and flash the rom.
If the above doesn't help,
Backup all you valuable data into pc, backup app+data through TB move it to pc and flash the factory image through fastboot.
Rohit02 said:
Try this.
As you are able to go in recovery,
Wipe cache , dalvik cache, system, data install PA 3.97 flash pa_gapps then supersu v1.51(for root,also enable app+adb from developer option)
wipe cache and dalvck again and reboot..
P.S : Charge your battery first to 80% minimum and flash the rom.
If the above doesn't help,
Backup all you valuable data into pc, backup app+data through TB move it to pc and flash the factory image through fastboot.
Click to expand...
Click to collapse
I ended up flashing the stock image and completely wiping all data. I then tried to install CM10.2 again and it still hung at the CM boot animation for about 15 minutes. It shouldn't take that long to flash, right?
alphamini said:
I ended up flashing the stock image and completely wiping all data. I then tried to install CM10.2 again and it still hung at the CM boot animation for about 15 minutes. It shouldn't take that long to flash, right?
Click to expand...
Click to collapse
Did you use the Franco.Kernel for the JSS build?
Sent from my Nexus 4 using Tapatalk 4
Here is what happened.... I had stock 4.2.2 on my rooted nexus 4. This is when i made the twrp backup of my system and data and recovery I flashed cyanogen Mod. I flashed back to stock. Then while still rooted i upgraded to 4.3 from the device... then i rerooted. When i rerooted i flashed the newest version of twrp recovery 2.6. and i cant restore from my backup for some reason.... I tried to flash old versions of twrp and restore with no luck ... please help because i need the files for titanium backup to work. How do i get the data from that backup?
Try Nandroid Manager on the Play Store.
OneChaos said:
Try ]Nandroid Manager on the Play Store.
Click to expand...
Click to collapse
I am trying it now but it just keeps decompressing over and over and when i check to see if there is any user apps or data it says none but i know the backup has it
I recently made a backup of my stock rom using TWRP, I then flashed cyanogenmod 12.1 and due some random reboots I wanted to restore my stock rom.. I went into TWRP, did a wipe on everything but the external sd card then restored the backup of the samsung rom boot, data, system. When it booted it said it was upgrading all the android apps then starting apps then all the apps it tried to start crashed and was left with a blank screen. Is there something you have to do, to be able to restore a stock rom after flashing cyanogen?
No, that should have worked, but I have seen that crash black screen after clearing caches in TWRP, I pulled the battery, booted again and it was fine
*Detection* said:
No, that should have worked, but I have seen that crash black screen after clearing caches in TWRP, I pulled the battery, booted again and it was fine
Click to expand...
Click to collapse
Wierd, yeah I tried a couple of reboots and it always crashes once it starts apps after a restore.
Try flashing a stock ROM with ODIN to get the phone back to 100% stock
Then root and flash TWRP again and see if you can restore the backup then, if not, try restoring the backup without restoring DATA which is where the apps are
If that works, you could use Titanium Backup to restore the DATA partition iirc, see if you can get around it that way
Hey guys,
I unlocked my bootloader and flashed a recovery succesfully. When I entered into recovery mode, I enter into TWRP, get to install SuperSU, but when I reboot my device, it is stuck on "warning etc..."
What could I have done wrong? How can I fix this? Any help would be very much appreciated.
I have a MXP XT1563
I installed this TWRP http://forum.xda-developers.com/devdb/project/?id=11587#downloads
And this SuperSU https://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip
I honestly can't remember what fastboot files I download, but I suppose it was ok since I got to enter my unlocking code and unlock it.
Thanks in advance.
Regards from Mexico
When I enter into TWRP and enter somewhere, for instance Install, I can see my folders: amazon, kindle, whatsapp, etc... I suppose that's good news.
I've tried doing a factory reset from Wipe, no sucess.
Please help! I will be uncommunicated until I solve this
you should have read the forums first. did you take a nandroid before flashing su? of yes then restore that,
you need su 2.62-3
download the su then flash it again. here is the su.forum.xda-developers.com/moto-x-play/general/root-how-to-root-6-0-easly-t3277202
bablu048 said:
you should have read the forums first. did you take a nandroid before flashing su? of yes then restore that,
you need su 2.62-3
download the su then flash it again. here is the su.forum.xda-developers.com/moto-x-play/general/root-how-to-root-6-0-easly-t3277202
Click to expand...
Click to collapse
hi bablu048, I did not "nandroid" before flashing su. I did it after I flashed it and when I try to restore it it says it's read only.
Do I download su 2.62-3, copy it into my storage and flash it again, no matter all I've done by now?
when it asks to keep read only refect it select allow modifications,
yes, download that su , copy it to storage and flash.
bablu048 said:
when it asks to keep read only refect it select allow modifications,
yes, download that su , copy it to storage and flash.
Click to expand...
Click to collapse
ok, this is what I did: I downloaded the su, put in internal storage, went into recovery mode, got into twrp, installed new su.
Now it gets past the warning, but gets stuck now in the water-ish motorola logo...
When I go into Restore, I can see two back ups, when I try to restore any of them, it says "cannot restore system - - mounted read only" and no option to modify it.
thanks a lot for your help! I'm trying to follow your every advice as best as I understand it
DO NOT restore the old backup it has the old su you will be back to where you started.
]boot into twrp clear cache/dalvic cache and leave the phone on the watery logo for a few minutes..it takes some time to boot
bablu048 said:
DO NOT restore the old backup it has the old su you will be back to where you started.
]boot into twrp clear cache/dalvic cache and leave the phone on the watery logo for a few minutes..it takes some time to boot
Click to expand...
Click to collapse
I see... actually I didnt get to restore any of them. I cleared both caches and now I'm waiting in the watery logo.
In case I don't make it, I'll have to let it for a while like this: on the watery logo, the MXP is quite hot now... no problem if I let it like that for half a day? I'm worried about that
In case it doesn't pass from there... is downloading twrp backups still an option? I just finished downloading RSD lite.
fsae3 said:
I see... actually I didnt get to restore any of them. I cleared both caches and now I'm waiting in the watery logo.
In case I don't make it, I'll have to let it for a while like this: on the watery logo, the MXP is quite hot now... no problem if I let it like that for half a day? I'm worried about that
In case it doesn't pass from there... is downloading twrp backups still an option? I just finished downloading RSD lite.
Click to expand...
Click to collapse
just let it on the watery logo for 15-20 minutes if it's still not going any further you can download the backups and wipe the system, cache, dalvic cache then restore the backup
RSD lite is used to flash the original factory firmware then you have to root again.
bablu048 said:
just let it on the watery logo for 15-20 minutes if it's still not going any further you can download the backups and wipe the system, cache, dalvic cache then restore the backup
RSD lite is used to flash the original factory firmware then you have to root again.
Click to expand...
Click to collapse
I went to sleep and it didn't pass from the watery logo.
I manually backed up my files, so I'm not worried about anything I might have on the phone; still, I think flashing a new firmware will factory reset my MXP correct?
Is the original factory firmware the same as a stock image? I found this list of resources: https://github.com/motoxplay/stock. Under XT1563 - México, I can see my carrier, Iusacell. Will this do it?
Please do let me know.
fsae3 said:
I went to sleep and it didn't pass from the watery logo.
I manually backed up my files, so I'm not worried about anything I might have on the phone; still, I think flashing a new firmware will factory reset my MXP correct?
Is the original factory firmware the same as a stock image? I found this list of resources: https://github.com/motoxplay/stock. Under XT1563 - México, I can see my carrier, Iusacell. Will this do it?
Please do let me know.
Click to expand...
Click to collapse
yes it will wipe,
that's the correct firmware. 6.0.1
always take a nandroid before flashing su 2.62-3
after flashing twrp again when you boot into twrp do "swipe to allow modifications to /system"..you didn't do this that's why you were not able to restore backups.
bablu048 said:
yes it will wipe,
that's the correct firmware. 6.0.1
Click to expand...
Click to collapse
hi bablu048,
I found in here a "unSu" guide. I ran it, it deleted Su, then ran Su you recommended and I still got suck in the watery logo.
Then I "unSu" it again, now didn't run any Su, reeboted device and it finally started.
I think su is the problem. Where can I check what su should I use?
great first take a nandroid.
finding the correct su is hit and trial method. generally su 2.62-3 worked. try other su's 2.65,2.66
bablu048 said:
great first take a nandroid.
finding the correct su is hit and trial method. generally su 2.62-3 worked. try other su's 2.65,2.66
Click to expand...
Click to collapse
Ok, I get it now. I backup my device with nandroid to make sure I have it there in case something goes wrong. If I have no info I want to save (my phone is blank, it's factory resetted from the bootloader unlocking) is it still necessary to nandroid? It's necessary in case a su fails right?
nandroid backup takes a backup of your OS with data and everything.
I think you didn't allow/system to be modified when you first booted into twrp. that's why su is failing, as su modifies the /system partition.
bablu048 said:
nandroid backup takes a backup of your OS with data and everything.
I think you didn't allow/system to be modified when you first booted into twrp. that's why su is failing, as su modifies the /system partition.try
Click to expand...
Click to collapse
by now, my MXP is factory resetted, I'm trying to read more before doing anything.
Since is factory resetted, it doesn't have developer mode (oem unlocking, usb debugging). I still see TWRP in recovery mode.
I suppose if I want to try another SU, I have to enable develper of course, oem-usb, obviously. Do I have to flash TWRP again? Or can I just try a SU? Of course, after having done a nandroid.
fsae3 said:
by now, my MXP is factory resetted, I'm trying to read more before doing anything.
Since is factory resetted, it doesn't have developer mode (oem unlocking, usb debugging). I still see TWRP in recovery mode.
I suppose if I want to try another SU, I have to enable develper of course, oem-usb, obviously. Do I have to flash TWRP again? Or can I just try a SU? Of course, after having done a nandroid.
Click to expand...
Click to collapse
you don't need to take nandroid backup always, once is sufficient unless you want to backup the latest data. no need to flash twrp again. just flash su.
take a nandroid backup once (everything system, boot, data) . after successfully flashing su you can keep another backup that contains su.
bablu048 said:
you don't need to take nandroid backup always, once is sufficient unless you want to backup the latest data. no need to flash twrp again. just flash su.
take a nandroid backup once (everything system, boot, data) . after successfully flashing su you can keep another backup that contains su.
Click to expand...
Click to collapse
ok, finally! My device is rooted. Thanks a lot!
I think I forgot to select external storage when taking a nandroid, so it went into internal storage, it filled a little more than 5 GB. I can't see this backup neither in TWRP, PC or an android file explorer. How can I get rid of those 5 GB? I take a nandroid on external storage and already copied it in my PC.
Is there a way via TWRP to get rid of it? Wiping something? I'm very cautios from now on.
it's stored at /data/media/twrp delete those backups. or boot into twrp >restore> it'll show all the backups delete those.
edit: Im stuck in the "watery logo" I need help unistalling SU can some1 point me to that guide?
I've already flashed SuperSU 2.62-3
edit 2: I flashed SU 2.65 and it did the trick! solved, i think
original post:
Hi guys hope you can help me
I have a XT1563, single sim. I unlocked bootloader, flashed recovery, went directly to TWRP to flash SuperSU v2.46, it finished, I restarted using TWRP option but hasnt restarted is stuck in the warning screen "Warning bootloader unlocked...your device's bootloader has been unlock...." I do not know what to do
I press power-off and any key combination and it doesnt do anything is just stuck at that warning screen. Unlike the OP I dont get the watery logo