Related
Hey guys, long time lurker, first time poster.
I finally gave in and fully rooted my EVO and successfully flashed the newest damagecontrol rom. Afterwards, I took some time and set up my phone like how it used to be with the apps, settings, etc. Just a few questions from after this.
If I wanted to flash a different ROM, it is recommended to do a data wipe, correct? And also a NAND backup. Does this mean that my phone will be reset to factory settings again - using the new ROM as a base? In other words, would I have to rearrange my screens, settings, etc. if I wanted to try out a new ROM?
If not a different ROM, but an updated version of my current ROM, do I just flash that on top of what I have? (i.e. DC4.0 is released, do I have to wipe everything again before upgrading?)
If the answer is yes to both these questions, what are the easiest/quickest ways to get my phone looking/acting the way I like when getting a new ROM?
also, I followed toast's method step by step, and got the Amon Ra recovery on my phone as well. What is the function of this? Sorry for all the questions, I have everything working fine, but I'm just curious as to what and how things work on the phone. What is the difference between the amon ra recovery and following steps to use clockword for recovery?
Thanks a lot
baxtercat said:
Hey guys, long time lurker, first time poster.
I finally gave in and fully rooted my EVO and successfully flashed the newest damagecontrol rom. Afterwards, I took some time and set up my phone like how it used to be with the apps, settings, etc. Just a few questions from after this.
1. If I wanted to flash a different ROM, it is recommended to do a data wipe, correct? And also a NAND backup. Does this mean that my phone will be reset to factory settings again - using the new ROM as a base? In other words, would I have to rearrange my screens, settings, etc. if I wanted to try out a new ROM?
2. If not a different ROM, but an updated version of my current ROM, do I just flash that on top of what I have? (i.e. DC4.0 is released, do I have to wipe everything again before upgrading?)
If the answer is yes to both these questions, what are the easiest/quickest ways to get my phone looking/acting the way I like when getting a new ROM?
Click to expand...
Click to collapse
baxtercat said:
also, I followed toast's method step by step, and got the Amon Ra recovery on my phone as well. What is the function of this? Sorry for all the questions, I have everything working fine, but I'm just curious as to what and how things work on the phone. What is the difference between the amon ra recovery and following steps to use clockword for recovery?
Thanks a lot
Click to expand...
Click to collapse
Hello there, iv done videos on this rom for youtube, if you want the links let me know but ill go as it follows.
Ok, if you want to test out new roms, just do a nand backup of the one you have now, after that. WIPE both Factory and Delvic cache. Then flash the new rom in your phone adn you will be fine.
Ok, i know DC does this, i dont know about the others yet, But if a new update comes out, just flash that DC update over yours and it will be fine. All user data will be there. YOU shouldn't have boot loop ether. If so, then you will have to wipe again. I didn't and im fine. ( I use fresh evo right now. loving it. )
As for the NAND backup. This saves EVERYTHING so once you are tired of a old rom and wanna try another, just restory the back up and your fine.
super-6-1 said:
Hello there, iv done videos on this rom for youtube, if you want the links let me know but ill go as it follows.
Ok, if you want to test out new roms, just do a nand backup of the one you have now, after that. WIPE both Factory and Delvic cache. Then flash the new rom in your phone adn you will be fine.
Ok, i know DC does this, i dont know about the others yet, But if a new update comes out, just flash that DC update over yours and it will be fine. All user data will be there. YOU shouldn't have boot loop ether. If so, then you will have to wipe again. I didn't and im fine. ( I use fresh evo right now. loving it. )
As for the NAND backup. This saves EVERYTHING so once you are tired of a old rom and wanna try another, just restory the back up and your fine.
Click to expand...
Click to collapse
Wow, thanks for the quick reply! That cleared up a lot of things for me.
So if I have everything set up the way I want, it is recommended to do a NAND backup at this point?
Also, what are the pros/cons of using Rom Manager (marketplace)?
Thanks a lot
baxtercat said:
Wow, thanks for the quick reply! That cleared up a lot of things for me.
So if I have everything set up the way I want, it is recommended to do a NAND backup at this point?
Also, what are the pros/cons of using Rom Manager (marketplace)?
Thanks a lot
Click to expand...
Click to collapse
well if i was you, wait till you wanna flash something else THEN do a nand back up.
as far as rom manager goes, i dont use it. I just come on here and see whats new and what going on, you get a lot more from here then on rom manager, Plus, its free
super-6-1 said:
well if i was you, wait till you wanna flash something else THEN do a nand back up.
as far as rom manager goes, i dont use it. I just come on here and see whats new and what going on, you get a lot more from here then on rom manager, Plus, its free
Click to expand...
Click to collapse
This is what I was thinking as well. Thanks
could you be kind enough to explain the different recovery files and their uses?
baxtercat said:
This is what I was thinking as well. Thanks
could you be kind enough to explain the different recovery files and their uses?
Click to expand...
Click to collapse
what do you mean? like the different kinds of recoverys? Really i just stay with toasts, his is more stable and as far as the clockmod one, It has issues with formatting the Factory cashe.
Honestly, for someone that is completely new to flashing roms, backing up etc., Rom Mgr. is the best thing for you. You may not have the absolute cutting edge of available roms, but it makes flashing/backing up extremely easy and straightforward. That is how I got started with my previous Droid until I felt comfortable enough to flash the old fashion way. I have literally flashed and backed up hundreds of times using clockwork mod (rom manager recovery) and have not had a single issue. Plus, the app is only a couple bucks if I remembe correctly. I would start there to gain some experience, then move on to flashing zips from here.
just my opinion.
Will rom manager work if I have Amon RA's Recovery?
I think it may replace your recovery
Now, I thought, "hey, I'm not a novice with flashing ROM images, nor am I a *nix or system notice..." So, I decided to cook a ROM using the Online ROM kitchen: http://evo.feeder.pk/
I had run unrevoked3 + unrevoked forever, so I had clockwork recovery.
So, I copied the zipped ROM generated off the online ROM kitchen to the sdcard and then via clockwork installed /sdcard/update.zip (the ROM).
So, everything installed okay, then upon reboot, it seems to go into a reboot loop.
Lucky for me I performed a nandroid backup before installing the newly built ROM, and I'm in them middle of performing a nandroid restore; which I hope will resolve the problem.
1) Will the nandroid restore actually restore my entire phone back to how it was previously?
2) How do I actually install another ROM properly?
These are pretty n00b questions, but any help is appreciated.
Thanks,
Matt
branded said:
Now, I thought, "hey, I'm not a novice with flashing ROM images, nor am I a *nix or system notice..." So, I decided to cook a ROM using the Online ROM kitchen: http://evo.feeder.pk/
I had run unrevoked3 + unrevoked forever, so I had clockwork recovery.
So, I copied the zipped ROM generated off the online ROM kitchen to the sdcard and then via clockwork installed /sdcard/update.zip (the ROM).
So, everything installed okay, then upon reboot, it seems to go into a reboot loop.
Lucky for me I performed a nandroid backup before installing the newly built ROM, and I'm in them middle of performing a nandroid restore; which I hope will resolve the problem.
1) Will the nandroid restore actually restore my entire phone back to how it was previously?
2) How do I actually install another ROM properly?
These are pretty n00b questions, but any help is appreciated.
Thanks,
Matt
Click to expand...
Click to collapse
1) Its supposed to...
2) From what it sounds like, you installed everything okay, just with a bad ROM image. Installing any of the other ROMs already posted should relieve you of your bootloops (as should the nandroid). Unless you try overclocking, which some folks experience bootloops when overclocked over 1.15.
nol3n said:
1) Its supposed to...
2) From what it sounds like, you installed everything okay, just with a bad ROM image. Installing any of the other ROMs already posted should relieve you of your bootloops (as should the nandroid). Unless you try overclocking, which some folks experience bootloops when overclocked over 1.15.
Click to expand...
Click to collapse
Thank you sir. nandroid obviously did restore everything back to normal (wasn't sure to what extent nandroid backed up the device, but it looks like every single thing was backed up).
As for a ROM, I really just want the stock froyo ROM, but rooted... Do you have any suggestions? I can't go OTA since I have clockwork recovery.
Thanks,
Matt
branded said:
Thank you sir. nandroid obviously did restore everything back to normal (wasn't sure to what extent nandroid backed up the device, but it looks like every single thing was backed up).
As for a ROM, I really just want the stock froyo ROM, but rooted... Do you have any suggestions? I can't go OTA since I have clockwork recovery.
Thanks,
Matt
Click to expand...
Click to collapse
I have flashed most of the ROMs here, but I have mostly been using CM6 (Cyanogenmod 6) since it came out. I did try Baked Snack, which is a very nice ROM with a beautiful theme, but it is Sense based and if by any chance you wanted to use a Wiimote for emulators, you cant. It is based off the HTC bluetooth stack, CM6 is not. Its kinda nice to get nightly (experimental) updates to flash if you want to also.
Its all a matter of personal preference, but my BEST results have been with CM6 - benchmark, features, and otherwise.
*E* You also may want to consider posting something like this in the Q&A forum next time...
Uhhhh Ohhhh wrong section
nol3n said:
I have flashed most of the ROMs here, but I have mostly been using CM6 (Cyanogenmod 6) since it came out. I did try Baked Snack, which is a very nice ROM with a beautiful theme, but it is Sense based and if by any chance you wanted to use a Wiimote for emulators, you cant. It is based off the HTC bluetooth stack, CM6 is not. Its kinda nice to get nightly (experimental) updates to flash if you want to also.
Its all a matter of personal preference, but my BEST results have been with CM6 - benchmark, features, and otherwise.
Click to expand...
Click to collapse
Very cool. I'll take a look but I really want Sense, which I'm not sure if CM6 has. Thanks.
Sporkman said:
Uhhhh Ohhhh wrong section
Click to expand...
Click to collapse
Just flag the post and request a mod move it. There's really little reason to post a reply. It seemed like the best place given the descriptions of all the EVO sub-forums.
branded said:
Thank you sir. nandroid obviously did restore everything back to normal (wasn't sure to what extent nandroid backed up the device, but it looks like every single thing was backed up).
As for a ROM, I really just want the stock froyo ROM, but rooted... Do you have any suggestions? I can't go OTA since I have clockwork recovery.
Thanks,
Matt
Click to expand...
Click to collapse
Just get netarchys rooted stock rom and you should be ok... just make sure you get the rooted version
Next time do a wipe of your davik cache before installing any rom
playya said:
Just get netarchys rooted stock rom and you should be ok... just make sure you get the rooted version
Click to expand...
Click to collapse
Thanks playya...
http://forum.xda-developers.com/showthread.php?t=740520
http://forum.xda-developers.com/showthread.php?t=719763
evolol said:
Next time do a wipe of your davik cache before installing any rom
Click to expand...
Click to collapse
http://forum.androidcentral.com/htc...-clockwork-clears-dalvik-cache-just-fine.html
http://forum.xda-developers.com/showpost.php?p=4535156&postcount=4
http://androidforums.com/all-things-root-eris/76110-what-dalvik-cache.html#post710236
And thank you both for ignoring that racist bag of donkey twats that responded earlier.
branded said:
Thanks playya... do you have a link?
http://forum.xda-developers.com/showpost.php?p=4535156&postcount=4
http://androidforums.com/all-things-root-eris/76110-what-dalvik-cache.html#post710236
And thank you both for ignoring that racist bag of donkey twats that responded earlier.
Click to expand...
Click to collapse
no problem quote from last response at that forum
Quote:
Originally Posted by Tamasabian View Post
Ok. So I should just clear it when I do a data wipe to flash a new rom? Will it be a problem if I just do a data wipe and flash a new rom without doing the dalvik cache?
i have had issues when i dont clear the dalvik cache, but never had issues when i do. just cear it, nothing bad will happen and only good can come of it
Sporkman said:
Uhhhh Ohhhh wrong section
Click to expand...
Click to collapse
agreed, theres a section for Q&A
evolol said:
no problem quote from last response at that forum
Quote:
Originally Posted by Tamasabian View Post
Ok. So I should just clear it when I do a data wipe to flash a new rom? Will it be a problem if I just do a data wipe and flash a new rom without doing the dalvik cache?
i have had issues when i dont clear the dalvik cache, but never had issues when i do. just cear it, nothing bad will happen and only good can come of it
Click to expand...
Click to collapse
Cool thank you I will do that and attempt to reflash this ROM that I cooked.
Rocklee99 said:
agreed, theres a section for Q&A
Click to expand...
Click to collapse
Flag the thread and request a mod move it. Glad that you all really want to up your post count so badly, shows real dedication to the forums cleanliness.
Your welcome...now show your dedication to this forum by following instructions & quit cluttering the development section with basic Questions
Not to delf: seems like I fall under a ClockworkRecovery user who's dalvik cache doesn't actually clear. (http://forum.xda-developers.com/showthread.php?t=719763) Kick ass!
I have the same problem as you!!!! I posted it in the wrong forum though so I'll briefly psot my problem and maybe someone can help me. I was trying to update my radio to the latest radio and it worked. I then realized I didn't have a 4g signal and the mod I was using supports 4g. So I tried updating to the latest wimax and then my phone started rebooting. After it boots android it reboots after a bout a minute or 2.
I FIXED it with a nandroid restore which had my 2.1-1 back up which I made during the idiot proof guide. So thinking that I can always use that backup as a restore I tried re-installing the radios because I don't see how they could not work on my phone and thought maybe I had a corrupt file, but voila my phone started rebooting again, but this time nandroid restore tells me to fix it via adb restore, BUT my usb isn't working either. So I'm stuck and have no idea on how to get this thing to load my restore. Any help would be appreciated.
I didn't read you're reply. But after installing RA, I think I'll be alright...
Here's the deal from start to finish...
download and install the android SDK
install all the necessary drivers
restart in recovery mode ( adb restart recovery or hold volume down when powering on the device)
use adb shell to access the shell while the device is in recovery
1) install RA recovery using adb method (http://forum.xda-developers.com/showthread.php?t=705026) This may or may not be okay with or without running unrevoked first... not sure if flash_image was placed on the device by unrevoked.
2) reboot into recovery
3) flush dalvik cache via RA recovery.
4) flush cache via RA recovery.
5) use adb push to copy a downloaded ROM zip to /sdcard/update.zip (using RA recovery to mount the /sdcard/ partition)
- I've downloaded http://forum.xda-developers.com/showthread.php?p=7512117
6) Install update.zip from sdcard in RA recovery
- After booting into the new ROM one time, I allowed it to start and configured... then performed 3,4,5 against flashing a new kernel: http://forum.xda-developers.com/showthread.php?t=719763
And that should be that. I'm currently downloading the ROM, so I don't know how it'll be.
http://www.clockworkmod.com/forum/viewtopic.php?f=4&t=179
I created a thread there but i know there are more people active here that will read it.
this is to see how many people this has affected but also a work around if you encounter issues
OK, I have been testing the Unrevoked rc3.21 that comes bundled with clockworkmod
There seems to be an issue with how it does the nandroid backup. I have tested on my own device and another collegues
We are both running stock 2.2 2.10.508.2 hboot .93
flash went fine, rebooted to recovery, did nandroid backup of rom, reboot from recovery = boot loop
on my friends we did the same but this time reapplied clockwork from rom manager, did nandroid backup from rom manager - boot loop
To resolve the issue you simply restore the very same backup you just created
This leads me to believe that there is something going on where the backup process is actually corrupting system files after it has take a backup of it.
as said this has been duplicated and on top of that other people have reported it on unrevoked's bugreport list
I know you are not part of unrevoked but it seems to be clockwork mod with these new versions of desire that is causing a problem
http://git.unrevoked.com/redmine/projects/unrevoked3-testers/issues
Click to expand...
Click to collapse
Rastaman-FB said:
http://www.clockworkmod.com/forum/viewtopic.php?f=4&t=179
I created a thread there but i know there are more people active here that will read it.
this is to see how many people this has affected but also a work around if you encounter issues
Click to expand...
Click to collapse
I can confirm this.
Just did a nandroid backup with the same version of Clockwork Mod - on my Desire running stock 2.2 2.10.508.2 hboot .93
Phone went into boot loop, and I had to pull battery to get back into recovery.
I restored my backup, and phone booted normally again...
gosa said:
I can confirm this.
Just did a nandroid backup with the same version of Clockwork Mod - on my Desire running stock 2.2 2.10.508.2 hboot .93
Phone went into boot loop, and I had to pull battery to get back into recovery.
I restored my backup, and phone booted normally again...
Click to expand...
Click to collapse
was it you i was talking too on freenode yesterday?
what clock work recovery are you on?
i dont have this issue clockwork recovery 2.5.0.7 Hboot .83.001 Personal 2.10 modded rom.
Juggalo_X said:
what clock work recovery are you on?
i dont have this issue clockwork recovery 2.5.0.7 Hboot .83.001 Personal 2.10 modded rom.
Click to expand...
Click to collapse
the very same clockwork and to rule anything out we also reflashed the recovery using rom manager too.
same thing
its to do with the .93 hboots and the ruu version of froyo used i think. clockworks backup borks it lol
Rastaman-FB said:
was it you i was talking too on freenode yesterday?
Click to expand...
Click to collapse
yeah, that was me...
Also on 2.5.0.7 and with recently flashed RUU from HTC.
And btw -
I've seen a lot of incidents ("tickets") on Unrevokeds site about Desires getting stuck in boot loop after backup.
I do not know however we can reach all of them to get more people to verify. Maybe speak with the developers of Unrevoked?
well you would expect they are reading the tickets. its probably a clockwork problem but unrevoked bundle it so should be aware of the pitfalls
Yet to see a reply from the clockwork team
Rastaman-FB said:
well you would expect they are reading the tickets. its probably a clockwork problem but unrevoked bundle it so should be aware of the pitfalls
Yet to see a reply from the clockwork team
Click to expand...
Click to collapse
Could you take a few minutes and try making a backup again? It seems like the next backup you make might not give boot loop...
gosa said:
Could you take a few minutes and try making a backup again? It seems like the next backup you make might not give boot loop...
Click to expand...
Click to collapse
im scared,
im on a custom rom now though so i dont know if that makes a difference?
are you on a custom rom or still on default build?
Rastaman-FB said:
im scared,
im on a custom rom now though so i dont know if that makes a difference?
are you on a custom rom or still on default build?
Click to expand...
Click to collapse
Still on stock.
The reason I'm asking is because I've been emailing Joshua at UNrevoked about this, and when he asked me to give some feedback about the boot loop I went in and made a new backup - and that one didn't put the phone into loop.
I'm going to try to run Unrevoked another time this weekend and see if I can reproduce, but it would be nice if someone else could test to see if the second backup loops the phone or not.
gosa said:
Still on stock.
The reason I'm asking is because I've been emailing Joshua at UNrevoked about this, and when he asked me to give some feedback about the boot loop I went in and made a new backup - and that one didn't put the phone into loop.
I'm going to try to run Unrevoked another time this weekend and see if I can reproduce, but it would be nice if someone else could test to see if the second backup loops the phone or not.
Click to expand...
Click to collapse
im running leedroid now. ill run a backup of it as we speak and see what it does.
i hope its recoverable lol. wish me luck
EDIT:
SUCCESS in backing up leedroid.
so it looks like this maybe a 1st time backup issue?
odd, only way to really prove it would be to completly RUU the device back to full stock with recovery, wiped, and then do the process again.
Rastaman-FB said:
im running leedroid now. ill run a backup of it as we speak and see what it does.
i hope its recoverable lol. wish me luck
EDIT:
SUCCESS in backing up leedroid.
so it looks like this maybe a 1st time backup issue?
odd, only way to really prove it would be to completly RUU the device back to full stock with recovery, wiped, and then do the process again.
Click to expand...
Click to collapse
I'm going to begin with running Unrevoked again to see if I can reproduce. If that doesn't work... well.. Not sure I want to go through the RUU again... but on the other hand - with a good backup I suppose I could try.
gosa said:
I'm going to begin with running Unrevoked again to see if I can reproduce. If that doesn't work... well.. Not sure I want to go through the RUU again... but on the other hand - with a good backup I suppose I could try.
Click to expand...
Click to collapse
aye, can understand that. its up to you really
im surprised clockwork mod havent passed comment on it though on their own forums.
I confirm the same problem
Stuck in boot loop with the first backup after the root process, it worked after restore
i tried an immediate second backup after that and the problem didn't occur
weird, i'll report this to unrevoked, i'm running dbranded stock 2.10 with hboot 0.93
hamdir said:
I confirm the same problem
Stuck in boot loop with the first backup after the root process, it worked after restore
i tried an immediate second backup after that and the problem didn't occur
weird, i'll report this to unrevoked, i'm running dbranded stock 2.10 with hboot 0.93
Click to expand...
Click to collapse
thanks for coming here and reporting this, the more info we get to them about it the quicker theyll try and fix it as if this is about on full release there is gonna be some spammage about bricked desires
Sorry to ask i know this is probably a noob question (actually it is because i am a noob lol)...
The problem you mentioned is ween i try to make a full system back up after the root process with the latest unrevoked right?
priestnot said:
Sorry to ask i know this is probably a noob question (actually it is because i am a noob lol)...
The problem you mentioned is ween i try to make a full system back up after the root process with the latest unrevoked right?
Click to expand...
Click to collapse
yes
10char
But its only for those who have the 0.93? I have a 0.92 do i have to worry?
priestnot said:
But its only for those who have the 0.93? I have a 0.92 do i have to worry?
Click to expand...
Click to collapse
I cant answer that as i dont have .92 and ive not seen anyone report it on .92
Has this been fixed yet??
I am trying to make a backup of my current rom so that i can try another rom. It gets to where it says "backing up SD-EXT" and then hangs there forever. Anybody know whats goin on? I am running one of the Cyanogen nightlies.
jasonb1985 said:
I am trying to make a backup of my current rom so that i can try another rom. It gets to where it says "backing up SD-EXT" and then hangs there forever. Anybody know whats goin on? I am running one of the Cyanogen nightlies.
Click to expand...
Click to collapse
So it never finishes or just stays there for an extended period of time then finishes? Also are you backing up thru recovery or rom manager? And which recovery? 3.0.0.7, 3.0.0.8?
it just hangs there forever.... ive let it go for about a half hour and it just hangs there and never finishes. this is through recovery, not rom manager.
i just updated to the latest recovery, also tried doing the backup right through rom manager..... still hangs in the same exact spot.
jasonb1985 said:
i just updated to the latest recovery, also tried doing the backup right through rom manager..... still hangs in the same exact spot.
Click to expand...
Click to collapse
I've heard nothing but bad things about 3.* versions of clockwork.
Downgrade or amon_RA?
GRZLA said:
I've heard nothing but bad things about 3.* versions of clockwork.
Downgrade or amon_RA?
Click to expand...
Click to collapse
i also just reverted back to an older version 2 of clockwork mod and it still hangs in the same spot... idk what the deal is. i just wiped everything and am flashing a new rom. it just would have been nice to have had my current rom to go back to in case i dont like the rom im switching to, but whatever.
The only thing i can think of off the top of my head is a possibly corrupt SD-EXT partition. Also, just some good advice in general when downgrading (or upgrading, for that matter) recoveries is to check the Erase Recovery box in RM (or use a HBOOT file)
jasonb1985 said:
I am trying to make a backup of my current rom so that i can try another rom. It gets to where it says "backing up SD-EXT" and then hangs there forever. Anybody know whats goin on? I am running one of the Cyanogen nightlies.
Click to expand...
Click to collapse
I hate to be "that guy", but this isn't an issue for the dev forum. General or Q&A perhaps, but it's out of place here.
Assume there is ample space on the SD, and it's formatted as FAT32?
smtom said:
Assume there is ample space on the SD, and it's formatted as FAT32?
Click to expand...
Click to collapse
yes... of course
jasonb1985 said:
yes... of course
Click to expand...
Click to collapse
So did you go into RM and check the erase recovery box in settings yet? I would do that and reflash recovery with 3.0.0.8. Then try to make another backup. I'm curious if that will help.
So I attempted to upgrade my girlfriend's Galaxy Nexus from 4.1.2 to 4.2.2 (this is on Verizon. Was using a Xenon HD version from last August and attempted to update to the newest version).
Well, since I'm an idiot, I didn't read up on the file system changes and now I can't figure out how to get everything working properly. I have the sdcard/0 now and haven't been able to move the files over from sdcard/0 to the sdcard.
All I want to do at this point is just restore a nandroid backup and start over from scratch. Any help would be greatly appreciated.... I'm also having driver issues, so if there's any way to do this without using ADB, that would help immensely.
Thanks in advance.
The SDcard/0 is supposed to exist. Take 10 minutes to do the tiniest bit of searching and all your problems will solve themselves.
can you boot into recovery? what do you mean you cant get things working properly
slimb9 said:
can you boot into recovery? what do you mean you cant get things working properly
Click to expand...
Click to collapse
Yeah I can get into recovery but when I try to restore nandroid it says there are no files, and I know there is a backup.
I did a half hour of searching, but thanks for the help. I must not be searching for the right thing....
so can the phone turn on? or can you only boot into recovery
slimb9 said:
so can the phone turn on? or can you only boot into recovery
Click to expand...
Click to collapse
Yeah I can turn it on. Gapps didn't install, though, so I don't have a keyboard and can't install goomanager from the play store to update recovery. I also can't move files in the file manager because it times out very time.
if you still have the old xenon rom .zip file on the phone you could just flash that after wiping/clearing everything. then from there boot into recovery and see if you can see your nandroid backup of the old xenon she was on. not sure if this will help but worth a try. looks like the new xenon rom required a full wipe so something may be messed up that you could fix by flashing an older version
Asterdroid said:
Well, since I'm an idiot, I didn't read up on the file system changes and now I can't figure out how to get everything working properly. I have the sdcard/0 now and haven't been able to move the files over from sdcard/0 to the sdcard.
Click to expand...
Click to collapse
063_XOBX said:
The SDcard/0 is supposed to exist. Take 10 minutes to do the tiniest bit of searching and all your problems will solve themselves.
Click to expand...
Click to collapse
As 063_XOBX said, sdcard/0 is supposed to exist. Considering your comment later in the thread about not being able to find old backups, it sounds like you have an outdated recovery that doesn't understand the new file structure. Update your recovery rather than screwing with Google's intended file structure.
Asterdroid said:
I'm also having driver issues, so if there's any way to do this without using ADB, that would help immensely.
Click to expand...
Click to collapse
What driver issues? You haven't been overly clear with the actual problems that you're having. You said you had a problem with Gapps. Why not download and flash a Gapps package?
i p.m. him without a response. im sure he figured out he was doing something wrong. it helps to read instructions