Related
so I know just enough to be dangerous.... apparently.
I decided to start fresh, completely... wiped user data, dalvik, cache and did the factory reset thing. then I reflashed warm 2.2 and can not get past the white htc evo 4g screen. I have done a nandroid backup that is still there and I have tried to restore that, but it still goes to white screen and stays... I keep it on the white screen and after 15 minutes I try again after removing the battery... any ideas would be great... I am not an expert but I have installed different ROMs in the past without any real issue.
So, to summerize.
I have a rom on the device,
I can boot into recovery, hboot, etc
I can flash rom's, or the backup but can not get past white screen...
Thanks!
Maybe your SD card is going or the files on there are messed up try flashing different Rom something basic like fresh and see what happens
Sent from my PC36100 using XDA App
so what is the easy way to put a new rom on when you cant get the phone to boot up? Do I have to do it from a reader? Sorry, told ya I know enough to be dangerous.
resolved
put a different kernel on it, and it booted, thanks for the help though!
Before I went to sleep last night I decided to backup my phone via recovery. After it backed up I rebooted and I had no service and a service called com.phone or something like that would force close every 5 seconds. I went back into recovery and reflashed CM7 and it bootlooped. I went back into recovery and restored a backup from the day before and it worked flawlessly. I hadn't changed any type of settings, I had just installed the new Swiftkey Beta and Robot Unicorn Attack between the 2 backups. Through trial and error and many reboots into recovery I found out that it is the data portion of the backup that was causing the problems. Does anyone know why this happened? I am a little nervous about doing another backup for fear of not being able to use my phone.
CM7 Stable
Incredikernal (latest)
hboot .92
3.0.0.8 recovery
I suspect the backup had nothing to do with it. I'd bet you would have had the same problems after a simple reboot.
As far as I know, a nandroid backup simply reads from the phone and writes to the SD. I don't see how it could have changed anything on the phone itself.
That's what I thought. I can't remember if I had recently rebooted at that point but after getting the phone working through a restore of the previous backup I tried one last time and restored the backup that had caused the problem and the problem persisted.
How much free space do you have on data/data?
Sent from my ADR6300 using XDA App
Am trying to do a nandroid backup using Amon-Ra 2.3, and it just keeps laying down line after line of dots, taking much longer than I would expect, and never finishes. I've tried the suggestions in this thread on the issue, and I'm still having no luck.
Anyone have any suggestions/wisdom to offer? I've let it go for 20-30 minutes on a couple of occasions, and it's still not working -- I just end up with a screen full of dots.
Part of the reason I'm doing this is that I've been having issues with my wireless, data, etc toggling on and off on its own lately, so I thought a fresh start with a new ROM might be worth a go. Doubt that's related, but who knows, so I'm throwing that out there in case it matters.
Thanks!
PS Currently running VirusROM Airborne RC 6, to the extent it makes a difference.
What rom are you trying to restore?
If you wanted to start fresh, than you can install your new rom fresh, then restore all your apps+data, just not system settings.
I wasn't trying to restore anything, I was just trying to do a nandroid backup so I could flash another ROM. With that said, I've tried to restore an older backup to make sure I had one that worked, and that isn't working, either -- just an endless stream of dots. If I pull the battery in the midst of a restore, will I screw anything up?
jrtoastyman said:
I wasn't trying to restore anything, I was just trying to do a nandroid backup so I could flash another ROM. With that said, I've tried to restore an older backup to make sure I had one that worked, and that isn't working, either -- just an endless stream of dots. If I pull the battery in the midst of a restore, will I screw anything up?
Click to expand...
Click to collapse
No it shouldn't.
http://dl.dropbox.com/u/19699565/PC36IMG.zip Place that on your sdcard, and flash it in the bootloader, that'll re-flash amon_ra 2.3; hopefully that should fix it.
thanks man, I'll give it a try.
Aye aye, and I shall be around if it doesn't work.
well, I'm stuck in the back end of the boot animation now. Hmmm, very frustrating. How horrible would it be to just do a factory reset of the phone? Would I have to re-root?
jrtoastyman said:
well, I'm stuck in the back end of the boot animation now. Hmmm, very frustrating. How horrible would it be to just do a factory reset of the phone? Would I have to re-root?
Click to expand...
Click to collapse
If you do a factory reset, that just erases all data. You should always wipe the factory/data, cache, and dalvik cache in recovery before flashing a rom for the first time. You don't have to re-root, just restore your apps from titanium backup.
OK, so here's where I'm at:
1. I can't perform a nandroid backup
2. I can't restore any of my previous backups
3. I can't boot the phone to allow me to flash the new Amon-Ra you provided.
With all of that being the case, I feel like I'm sort of out of options at this point -- maybe just wipe it and flash the new ROM, hope for the best, and perform a nandroid after the flash? Can't really get any more screwed than I am now, right?
jrtoastyman said:
OK, so here's where I'm at:
1. I can't perform a nandroid backup
2. I can't restore any of my previous backups
3. I can't boot the phone to allow me to flash the new Amon-Ra you provided.
With all of that being the case, I feel like I'm sort of out of options at this point -- maybe just wipe it and flash the new ROM, hope for the best, and perform a nandroid after the flash? Can't really get any more screwed than I am now, right?
Click to expand...
Click to collapse
What do you mean you can't get to the bootloader?
Power the phone off/battery pull, upon turning on, hold vol+down till you see the white android screen, then it'll scan for the PC36IMG, which you apply update, then reboot. And it can still be saved.
I guess the question was how do I get the file onto my phone when I can't get the phone to boot up, but it occurs to me that I can pull the card out and load it on there that way, so let me give that a go and follow those steps. Now, I've just got to find that little card adapter thingy...
Thanks again, appreciate the assistance
Ah yes...the adapter...tis why I just always leave it in my laptop. But that will work, and you're welcome.
that did the trick, back up and running. Whew!
Much appreciated!
Glad that it worked.
I'm on an EVO 4G running Fresh 3.5.0.1 with Netarchy Toastmod 4.3.4 cfs havs-less no sbc. I'm currently using ClockworkMod recovery 2.6.0.1.
Last weekend, I wanted to try Synergy with GodMode. I don't know if it wasn't in the thread when I read it (I see the thread's been updated since my attempt), or if I just missed it, but either way, I was unaware that I couldn't install the GodMode ROM with ClockworkMod.
So I did a Nandroid backup and attempted install (I'll admit, I initially forgot to wipe data/davlik/cache). It seemed to install fine, but then couldn't make it past the boot splash. So I figured I'd cut my losses and just restore my backup. After restoring, it once again got stuck at the bootsplash (never had this issue in the past). And when I say stuck, I mean I let it sit at the boot splash screen for 5-10 minutes, pulled the battery, repeated (including wiping everything), and it could never get past it. To get the phone working again, I had to restore to a much earlier Gingerbread Deck backup that I had made while fooling around with that ROM, then I was able to restore the most recent backup without issue.
Fast forward to this evening. I figured I'd try again, but now I know I need Amon_RA's recovery. So my plan was to do another Nandroid backup, install Amon_RA, and try Synergy with GodMode. I never made it past the first step... after creating the backup (no changes were made, just the backup created), the phone wouldn't progress past the boot splash. I had to go to an earlier restore point (last weekend's) to get the phone to work. Tried restoring today's backup after getting it to work on the old backup, no luck.
Thinking perhaps the attempted GodMode install messed something up, I did a fresh install of Fresh 3.5.0.1 (pun semi-intended), fresh install of my kernel, and then tried restoring the most recent backup. Once again, couldn't get past the boot splash.
I feel like something is seriously wrong, and I don't feel comfortable going into recovery to make any changes until I have some insight into what the issue is.
To make matters worse, I rely on 4G tethering for internet, and have no landline, so if the phone is bricked while trying to resolve this issue, I'll have no resources to get help.
Any help is GREATLY appreciated. I've searched, but it seems that the problems everyone has that are like this occur immediately after changes are made and are remedied by wiping data/davlik/cache. I made no changes this evening, and wiped everything multiple times in my many attempts.
Edit: Almost forgot, some things did stand out as I was trying to get it to work.
While whiping Davlik, I was given the line:
E:Can't mount /dev/block/mmcblk0p2
(File exists)
While restoring today's backup:
sd-ext.img not found. Skipping restore of /sd-ext/.
There was a nandroid restore issue using a previous version of twrp that was remedied by restoring nandroid and then flashing the rom over top of the nandroid. Maybe try that
Sent From My Pocket
Ok I had the same problem. I wiped everything three times also wiped dilvak (might have spelled wrong) cache, and wiped battery stats. Then flashed it. It took forever also close to 15 mins. This is what I did I hope it helps.
Just a followup: I decided I could do without restoring to that specific backup (tried restoring it after wiping data a few more times, but oh well). I only installed a couple apps and changed a couple other things since the last backup that worked, so I installed Amon_Ra since it seems to be the consensus that it's a better recovery and made a backup with that... rebooted just fine afterwards.
Just to preface, I have been flashing ROMs for 2 years now, and am by no means new to the game. However, I'll be the first to say that I'm not immune to making stupid mistakes. So if I'm being stupid, you can tell me and not hurt my feelings
I will give a history of what I have done with my phone since Monday after I picked it up, and some quirks I have noticed.
- Set up my phone, accounts etc
- Let Google backup/restore download and install all of my apps
- Installed OTA to ALJC
- Installed Note2 Toolkit on my PC, drivers load, adb recognizes.
- Rooted & Installed CWM recovery
- Flashed stock de-odexed ALJC
- Installed 5x6 launcher & ALJC 4x1 reboot options (rebooted and proceed to setup my homescreens, icons, etc.) (I noticed when trying to flash items from "internal" sd card, it says there are not any
- inserted my SD Card from my OG Epic (Titanium backups in place)
- Restored text messages from .xml file via TB
- None of the games I wanted to transfer data from would run after restoring data from my TB backups, had to clear data and apps run fine, except for NBA Jam (guessing b/c they were from a CM10 ROM and a different device)
-Got all my apps setup, wiped all the bogus data I got from my prior TB backups. After playing with the phone, running apps for several hours, did a full Titanium backup of my phone
- Booted to CWM & Saved a nandroid backup to external SD Card
- Flashed (dirty) ULE 1.0 ALJC Rom (I thought by flashing dirty, it would preserve all my data, apps, etc. = I was wrong)
- Attempted to restore all of my Titanium backups (only ~60% would restore...still trying to figure this out).
- Attempted to restore the backed up 5x6 launcher (with my screens/icons setup intact) via TB. This kind of worked, it definitely changed the icon setup, but it was NOT 5x6, and it did not have my previous layout (probably b/c it was trying to fit a 5x6 on a 4x4).
- Figured that the dirty flash screwed things up, so I would restore my nandroid and go back to square one, where I had stock deodexed with 5x6 & reboot options, and launcher screens intact. So I booted CWM and restored that nandroid.
- After restoring and rebooting, I'm not sure if anything happened at all. I had a 4x4 launcher, no reboot options, and several of my apps were missing (particularly, the ones that would not restore from TB before)
- Figured I aught to factory reset and then restore, same result as above.
- Currently downloading stock ALJ1 tar so I can start all over again
Click to expand...
Click to collapse
I know this is long-winded, but I wanted to put it all out there in case I am doing something categorically wrong with my Note II, so I do not replicate this problem. It has always been the case that a nandroid backup gets me back EXACTLY where I was when I made it (on both my Touchpad & Epic). For whatever reason, this did not happen in this case, even after a factory reset/wipe.
Perhaps CWM isn't working properly? Perhaps I need to try TWRP so that I can manually wipe /system (as far as I can tell you can't manually do that in CWM, but if I understand correctly, this is done when you flash a ROM or restore a nandroid).
Am I doing something wrong? Also, why won't CWM see any of the files I downloaded to the internal memory? Several times now I have booted CWM and when I try to flashing things I downloaded, I have to reboot and move them to my external SD card so that CWM can see them.
Are there settings that are being saved to my external SD card that are causing problems (I highly doubt it)?
Thanks to any and all suggestions/guidance/advice.
Looking forward to learning more and more about these awesome devices.
MeetFace said:
Just to preface, I have been flashing ROMs for 2 years now, and am by no means new to the game. However, I'll be the first to say that I'm not immune to making stupid mistakes. So if I'm being stupid, you can tell me and not hurt my feelings
I will give a history of what I have done with my phone since Monday after I picked it up, and some quirks I have noticed.
I know this is long-winded, but I wanted to put it all out there in case I am doing something categorically wrong with my Note II, so I do not replicate this problem. It has always been the case that a nandroid backup gets me back EXACTLY where I was when I made it (on both my Touchpad & Epic). For whatever reason, this did not happen in this case, even after a factory reset/wipe.
Perhaps CWM isn't working properly? Perhaps I need to try TWRP so that I can manually wipe /system (as far as I can tell you can't manually do that in CWM, but if I understand correctly, this is done when you flash a ROM or restore a nandroid).
Am I doing something wrong? Also, why won't CWM see any of the files I downloaded to the internal memory? Several times now I have booted CWM and when I try to flashing things I downloaded, I have to reboot and move them to my external SD card so that CWM can see them.
Are there settings that are being saved to my external SD card that are causing problems (I highly doubt it)?
Thanks to any and all suggestions/guidance/advice.
Looking forward to learning more and more about these awesome devices.
Click to expand...
Click to collapse
Well I personally use twrp and have had no issues so I cannot speak on your nandroid issues...I do know however that in twrp after selecting internal or external sd card, you sometimes have to manually navigate to the respective sdcard...as for your TB not seeing your back ups from your prior device, go to preferences< backup location< detect and select scan whole device
Sent from my SPH-L900 using xda app-developers app
Just to clarify your remarks to avoid confusion. I can clearly see my TB backups.
I did have to go and do those steps first. About only half of them would restore though. Kind of odd. Maybe some data corruption? Didn't matter if I did them one at a time or during batch mode. Also didn't matter which of the 3 processing modes I selected in TB. Once one of the offending backups was being processed in batch mode, the restore process would hang until I force stopped TB or rebooted.
How much free storage does your internal sd have remaining? I ask because my wife's s3 would do the same when it was below 1gig
Multiple GB, probably 7 or 8. I store everything on my external, music, pics, etc. Haven't had that much chance to fill up the internal yet =]
I don't know. ..Very irritating isn't
It is indeed. But that's the risk of being a flashaholic
...and of being a first-mover on a brand new device =]
Beginning to wonder if me rooting with SuperSu, and then flashing (dirty) ULE which uses superuser, may have caused any problems. Perhaps binaries were conflicting?
MeetFace said:
Just to clarify your remarks to avoid confusion. I can clearly see my TB backups.
I did have to go and do those steps first. About only half of them would restore though. Kind of odd. Maybe some data corruption? Didn't matter if I did them one at a time or during batch mode. Also didn't matter which of the 3 processing modes I selected in TB. Once one of the offending backups was being processed in batch mode, the restore process would hang until I force stopped TB or rebooted.
Click to expand...
Click to collapse
Oh okay I see what you mean now...I have no idea whats going on there lol. ..I hope you can somehow get that figured out because I know how much it sucks to lose app Data
Sent from my SPH-L900 using xda app-developers app
I am really puzzled now, I just odined back to stock and then up through all rooting/etc to get to ULE again. Totally wiped everything. TB is still giving me fits. I'm assuming they backups were bad. Half work, half don't.
I was able to restore apps from a nandroid I made on my OG Epic a month ago. So that's helpful. I'm going to delete all my TB backups once I get everything situated and start fresh (possibly b/c I made backups while on an odexed ROM and restored them on a deodexed ROM?).
I think I'm going to stick with TWRP for now. I don't know if CWM was working properly at all, and TWRP has a few more features. TB wasn't able to see a single app to restore from the two CWM nandroids I made. Not sure what's up with that.
I was going to mention the codex stuff but it really shouldn't matter as you are backing up the data portion not the system. Still you might have a look at setting/storage. USB debug on ...all that jazz
Sent from my Nexus 7 using xda premium