Develop Bugs

Trying to manually restore apps, greeted with boot loop

This is quite a story I've got here, but just bear with me while I tell it.
Two days ago, I spotted a fps unlock kernel on the Development board here on XDA. I was feeling a bit reckless, so I decided to flash the kernel without doing a Titanium backup. At this point, I was running Fresh 0.5.3. After installing the kernel and rebooting the device, I was greeted with a looping boot animation. Needless to say, I wasn't a happy camper. I flashed every previous version of this kernel, as well as the original kernel, with no success. A Nandroid restore proved to be futile as well. I also tried flashing a fresh copy of the rom onto my phone without doing a complete wipe. No go on that attempt. Finally, I did the stupidest thing I've done with this device and did a complete wipe (data/cache/dalvik,sd:ext), followed by a fresh flash of Fresh (har har). That did the trick. Keep in mind that before performing this last step, I copied the app and app-private folders from my SD card in case of anything.
However, it was then that I realized that my stupid ass had no way of restoring the apps! You see, at least a hundred of the apps on my phone are non-market apk files that would take FAR too long to reflash individually. With that in mind, I installed a bootable version of Ubuntu onto my flash drive, which I used with my netbook in order to access the ext3 partition on my Evo. Afterward, I copied over all of the data from app and app-private onto my SD card. I thought I had finally succeeded in doing something that could have been done so much more easily had I waited to back my **** up previously!
Anyway, that last part occurred about an hour ago. After the files had copied, I exited recovery mode and restarted my phone. I was greeted with the glorious 'FRESSSSHHHHH' boot animation. And then it greeted me again. And again. AND AGAIN AND AGAIN AND AGAIN AND AGAIN RAAARRGH. Anyway, that's where I'm currently at in this whole dilemma. I thought the boot loop meant that the apks in the two app folders were being installed, but an hour is an awfully long time for that to happen.
So now, I am here begging for help from you, the fine people at XDA developers. Is this boot loop animation normal when I've just copied all those files over to the app and app private folder? If not, is there any way to restore my apps without installing them individually through adb or the phone itself?

i don't have fresh, but i use dc 3.2.3 and had a similar issue. i don't honestly remember exactly what i did, but i do know i did a bunch of stuff without backing up and got the boot loop.
here's my thread on it:
http://forum.xda-developers.com/showthread.php?t=722072
i'd link you to the solution we found, but as it's not the exact rom, maybe the troubleshooting steps will resolve your issue. i ended up flashing the engineering build to get access to android, and then flashing dc again to get up to speed.
good luck and let us know how it goes!

shift_ said:
i don't have fresh, but i use dc 3.2.3 and had a similar issue. i don't honestly remember exactly what i did, but i do know i did a bunch of stuff without backing up and got the boot loop.
here's my thread on it:
http://forum.xda-developers.com/showthread.php?t=722072
i'd link you to the solution we found, but as it's not the exact rom, maybe the troubleshooting steps will resolve your issue. i ended up flashing the engineering build to get access to android, and then flashing dc again to get up to speed.
good luck and let us know how it goes!
Click to expand...
Click to collapse
It's not so much fixing the bootloop that I'm worried about. I've already experienced it three times this week, and that can be fixed by wiping the phone clean. What I'm wondering is whether I can install the apps I have backed up by copying over the files from app and app-private
Needless to say, I'll read the thread you linked me to. It might have some useful information .

Need Help!!

Hey
I apologize if a thread like this has appeared before, but i have just about had it with playing about with my desire after i tryed to flash a new ROM, il try and explain is as best detail as i can, and hopefully, one of you will be able to help me get back to normal, as im tearing my hair out over this now...
So...Last night, i noticed that LeeDroid (The custom rom i use) had updated his firmware to 3.0, and in the interest of keeping my phone upto date, i went ahead, downloaded the rom, put it on my SD, did a nandroid backup, wiped and flashed as i would normally
the install seemed to go fine, but when i rebooted the phone, it hung on the HTC screen for about 15-20 mins, so i figured the flash hadnt worked, so i went back, wiped again and restored my backup
this is where the issues begin, the bacup restores fine, BUT, when the phone reboots and loads up, ALL of my apps etc have gone, no longer apparently anywhere on my SD card (which is where most of them were stored) I now had a bare bones android, with no apps (not even market, as that was updated manually too)
at this point, i start to panic, i have seemingly lost everything off the phone (apart from the SD backup i had performed before), and only have a bare bones version of the LeeDroid rom i was using before, with no apps what so ever
so, i thought, i might as well start afresh, so i boot back into recovery, wipe again and re-flash a fresh Leedroid rom, which seemingly again, goes fine, but again, hung on boot
getting more worried still, my SD-EXT then stops mounting, giving me an error, so i re-partition it, format it, and try again, and again, it still hangs on boot
at this point, i realize im screwed, and just restore the bare bones backup i had saved on my computer (nandroid), which at least allows the phone to boot and be semi-usable
i have no idea what im doing wrong here, nothing wants to flash anymore, it just hangs, and i cant even seem to un-root the phone, all the RUU's i use just give me a "CUSTOMER ID ERROR" which i have no idea how to fix
can anyone PLEASE point me in the right direction, im panicing here, i cant seem to get anything to work, and i have been going around in circles for almost 7 hours now...
thanks very much

Looks like you'll need to start from sguare 1 again. Seems like the SD issue, might have corrupted the SD card.
My suggestion, is that you format the sd card (backup all files to the pc)
Create a new gold card again.
Flash to stock again if need be, then root.
You can download googleapps and flash it also. There are some downloadable links in this site you can save to your sd card. Or you can download it at cyanogenmod.com (where I downloaded mine I believe).

i thought going back to square one would be the way forward too, except that i cant seem to find an RUU that will work, as i mentioned, all of the ones i have tryed give me the CUSTOMER ID error, which i have no idea what to do with...
so, im a little stumped..

Your Gold Card is good? Better re-do it again. Because if your partitions blew away on your SD card, it probably cooked all of it.
You shouldn't have any problems finding a stock froyo ROM.

Moscow Desire said:
Your Gold Card is good? Better re-do it again. Because if your partitions blew away on your SD card, it probably cooked all of it.
You shouldn't have any problems finding a stock froyo ROM.
Click to expand...
Click to collapse
i have a stock froyo RUU, should i apply the goldcard, then try the update again then?
im new to this, so im probably going to need taking through all this
edit: so i made my SD into a goldcard. and now it wont mount on the phone, and when i run the RUU, it still gives me the CID error..
im going insane here, someone help >.<

ok, i got it
after doing some reasearch, i found that alot of people were saying that the phone needed to be S-OFF to flash it correctly
so, after reading up, and S-OFFing, i wiped, partitioned and flashed...
and, finally, after 9 hours of tinkering, errors etc, it has flashed and booted
this can be locked now, thanks

partitioned th sd card,
works sometimes, but glad we could somewhat lead you in the right direction, by proxy........
Little puzzeled by the s-off, but hey, it's fixed!!!

[Q] Please Help! Looping

Ok... here's the deal. I just decided to switch roms finally to see what is new out there. I had been running an old version of Uber Kingdom. Here is the problem I am having. It is boot looping. Relatively simple problem to fix usually. But wait, there's more! It is boot looping in every single rom I install. Sometimes it won't boot to clockwork properly either and I have to pull the battery. Is there someway I can fix this? Or is this a hardware problem (which I kind of doubt)? I just don't understand what the heck is going on. I have been flashing different roms left and right for the past few hours trying to get this thing to stabilize. Sometimes it will boot up into the rom, I will get mostly through the google accounts setup, and then it will restart, and then loop. Other times it won't even get past the white incredible screen, and then sometimes it will make it into the rom splash screen. I have attempted to install CM7 nightly, Uber kingdom, and Synergy so far. I can flash the new rom, I can mount the SD card in clockwork, but then it begins to loop again as soon as I leave clockwork.
Let me know if you need any other information.
Is there a way to just completely redo EVERYTHING, clockwork, rom, everything, just to make sure I have a nice clean slate?
Thanks a ton for reading through this novel. I am extremely frustrated.
~Will
PS, I may not get back to this thread until morning. I have to get to sleep for work. Sorry if I don't respond right away to information requests. Thanks again!

If you can mount the SD card, download the stock RUU from www.dougpiston.com, put it on the root of the SD card named exactly PB31IMG.zip, and boot into hboot to install it. Your phone should be restored to stock, a clean slate.

Tried a different SD?
Sent from my ADR6300 using XDA Premium App

How are you downloading and flashing the ROM? I had this problem when trying to do everything through Rom Manager. Even trying to flash in recovery with a ROM downloaded through ROM Manager would loop.

Update
Well, I was just getting ready to flash the original RUU when I tried one last time to restore my old Uber rom setup and it worked (whereas the last 3 times of doing exactly the same process didn't). It stopped looping at least, even though I am still running the same rom I was before. I think tonight I am still going to attempt to flash the RUU anyway and start over anew.
To answer the questions before, No, I did not try a different SD. I didn't know it could make that much difference. Still on the original one that came with the phone.
As the downloading and flashing process goes, I was downloading direct from the XDA forums on my laptop, then transferring the files via USB. I have never really liked using the Rom Manager. It cuts me out of the XDA loop and I don't get to see all the bleeding edge discussions, etc...
So I will try to flash everything new tonight, and then post my results for anyone who is curious. Thanks for the help guys!

[Q] Epic Failure... Any ideas?

Okay, so here's what happened:
I was minding my own business, listening to Pandora at work. Out of nowhere, the music had an increasing amount of pauses due to bad music loading, or so I though. I figured it was just the crappy Sprint network around here, but I figured I would restart it and hope it would work again.
Boy, was I wrong. At the first reboot, it got stuck in a bootloop where it would start my boot animation all the way from the start after it got into it's little animation loop for a while. So I pulled the battery and tried it again. This time, it made it through and loaded up to the lock screen.
Once I unlocked it, I got an error message that said something along the lines of "hardware UIC doesn't match, please wipe your data partition" (can't pull the exact wording out of it anymore, I can't reproduce it) I acknowledged that message and then I got a ****LOAD of FC's left and right for just about everything under the sun, and then some. All of my system apps were FC'ing, and it was just one after the other after the other, and it would even loop them around and the same system apps would pop up FC's again.
Okay...maybe I can fix this by wiping my data like it said. Nope. Maybe I can flash my ROM again and fix it... Nope. Now it loads up to the setup screens, and then about halfway through, the sytem just locks up on me.
****. Alright, let's try flashing a stock ROM back to it. Well, this doesn't work either. Same results.
I have no idea why it started doing this, and I really don't want to have to go get myself another phone, since I don't have any kind of warranty on my phone.
So does anybody out there have any other ideas on what I can try to do to fix this? It's been driving me crazy all night.

Run stock ruu
Sent from my nike hating evo!

Before you run the RUU, reformat your SD Card, I don't know what recovery you have, but use Amon Ra to wipe EVERYTHING Except the option for SDCard:, dalvik cache and cache 2 times, then flash your ROM in recovery.
If that doesn't work, try running RUU

Additional details about my phone:
HBOOT 6.16.1002
ClockworkMod Recovery v5.0.2.2
Also, I can't seem to find an RUU that my phone will take... They've so far been failing on me, but I'll keep looking...
Also, wiping, flashing ROMs, wiping again, has not produced anything fruitful. Will be going the RUU route. I seem to have found one that *should* take, fingers crossed.

Problem number 1. Clockwork Recovery Mod. Get rid of it and get Amon Ra and do as I posted above.
Here, download this, rename it to PC36IMG.zip, out it on the root of your SD Card, not in any folders, and reboot to Hboot (Vol dwn-pwr til hboot comes up).
It'll scan and ask you to update, say yes, it will flash Amon Ra. Now go back to Recovery, go to Wipe and do as I said above.
http://www.mediafire.com/download.php?v453e5wg0on3pzt

[RESOLVED] [Q] Epic failure... Any ideas?
CM REcovery hasn't led me wrong yet, but I have tried both of them... Personal preference, I think.
The RUU took and the phone is usable again for the most part. The only issue I have now is an error that pops up after every boot... "SD card unexpectedly removed" But I'll be digging around to figure that one out.
Thank you guys for your help, I was beginning to think it was a hardware issue for a while there.

CWM is leading you wrong and you just don't know it. For one, you can't do a proper wipe before flashing a new ROM. Also, there are issues with flashing Radios, if you ever need to upgrade.
There's a reason why the majority of users use Amon Ra. Your choice, though.
Maybe you need to reformat that card, or try a different card.

Wound up going back to work before I could finish everything I wanted to, however I was able to get S-OFF, and I went and flashed RA Recovery. The sd card issue was caused due to a bad sd card. Unfortunately I was unable to save everything from it, but I should be able to get most of my files back relatively quickly. Should be able to have Synergy flashed on it again before I go home in the morning.
Sent from my PC36100 using XDA App

Help! "wrong UIDs" right after flashing Stock!? and lots of other Problems.

This is a very sad story about my NoteII going bad.
I would describe myself as computer savvy and moderately experienced with Android. I equipped half of the family with various ROM-customized Android phones and am an enthusiastic Note user since it came out in 2011. Until now, I never had to ask a question in the forum.
Let me start in December 2012 when my NoteII arrived. I updated it, then came cwm and the monxdified ROM. For about a month I was a very, very pleased NoteII user.
Then, one day in Mid-January, I installed an app called "(root) Uninstaller pro", which began to auto-backup up all my apps to internal SD in a background process while I didnt notice. I only realized something had gone wrong when apps began to FC because no space was left on sdcard0. I removed the app and all the backups.
From the day after that , Play Store began to "randomly" refuse to update or install apps, because of "Not enough storage space available‎". Which was bull****. I literally had Gigabytes of free space on internal and external storage. For example, Play Store would refuse to update my tiny TB Pro key apk for "Not enough space" reasons but then happily install Asphalt7 and update Titanium Backup and Dolphin for me. Moreover, every affected app also does not install "manually" from apk. When removed, it can not be reinstalled, except via update.zip from the recovery.
Of course, I googled the error. I found no root cause explanation, just a bunch of hints. I deleted all app data from play store and various store-related apps. I deleted and re-setup my Play Store account. The usual suspects, cache and dalvik, got their wipe. Nothing helped. I downloaded the latest monx ROM and updated it from TWRP. Problem still there. Then my job required my full attention so I left the thing running with only partial updates for several weeks. After all, it still worked petty well.
Then, lately, I decided to tackle the issue again. I went to Settings and did a full factory reset WITH internal SD reformat. In TWRP, I did another factory reset and full wipe, then I flashed the latest (DMB2) monx ROM and restored from my TB backup.... "Not enough storage space available‎".
A friend suggested I should try "Fix permissions". Boy, what a bad Idea. From that moment, LBE Security guard caused a Hot Reboot every time I tried to use Active Protection. Many resets and wipes later, it still does today. I can only install it via update.zip, though, not properly reinstall it: "Not enough storage space available‎".
But all this still is only the beginning. I decided it was time to clean up the mess and factory resetted again (no SD wipe this time, after all it didnt help last time), took good old ODIN and completely reflashed with Stock XXDMB2. Result: Boot Loop. TWRP told me "cannout mount /data" and claimed internal and external SD to be empty (which was not the case). So I reverted to cwm6 and did a fullwipe/reset. Only after that, the newly flashed Stock DMB2 suddenly booted. I went on and reinstalled monxdified DMB2 (the very same zip that had worked before!). But regardless of what I tried, all I got was another boot loop.
Back to Odin, Stock again. This time (and every time after) it booted right away without needing help from cwm, BUT on the very first GUI ("choose country") it told me that UIDs were wrong and suggested to reformat /data. Wait, wasnt that what Odin just did? Instantly after this error, com.google.gapps did an FC. CWM to the rescue. This time, "fix permissions" seemed to actually fix them.
To make this long story a bit shorter, I reiterated though quite a number of futile attempts to install a booting custom ROM until 2am, and failed. Now I am on Stock DMB2 with a non-working LBE and only a handful of the most important apps restored. The "Not enough storage space available‎" problem is still here.
I wonder how the "Not enough storage" problem was able to survive so many flashes and resets. I am utterly helpless about how a Stock ROM, flashed from Odin can expose UID problems and FCs on first boot. Could this be a sign of a malfunction on the internal flash storage? If so, how would I be able to find out? Or could it be that this "uninstaller" did something nasty to the secure storage system of JB (which I dont have any idea of how it works and what it needs at all), at a point that all my wipes and flashes did not actually reach?
What else could I do to really, really reset every possible bit on this otherwise wonderful piece of hardware and possibly get rid of all those pesky problems (and back into a Custom ROM)?
Please help me to make this baby shine again!

Re: Help! "wrong UIDs" right after flashing Stock!? and lots of other Problems.
Ive read your story and i feel really bad for you. Good luck m8, if I had some knowledge id help you for sure but im new to android ) goodluck! Dont give up x
Sent from my GT-N7100 using xda premium

Re: Help! "wrong UIDs" right after flashing Stock!? and lots of other Problems.
Do a mega wipe with recovery. Then install stock rom and nothing else. Don't restore stuff. Instead download them from play store.
Sent from my GT-N7100

Re: MegaWipe
UtkarshGupta said:
Do a mega wipe with recovery. Then install stock rom and nothing else. Don't restore stuff. Instead download them from play store.
Click to expand...
Click to collapse
Ok. So I found MegaWipe and put it on my SD-Card. I started it and the aroma Installer presented to me the Mega Wipe Option which I chose. A text screen appeared which said, that several partitions had been wiped but it happened in less than a second which I foudn to be suspicious. Then, when tapping "Next" again in the MegaWipe Aroma Tool, I found out Aroma was frozen and the recovery system did not react to any key press or tap anymore. I had to press the Power button for a while to get back into recovery where I flashed a ROM, then rebooted.
Guess what: all my apps were still present, the SMS history and Launcher fully intact. Dalvik had been wiped apparently (all apps re-optimized), though, and my Wifi AP settings were gone. Of course, the "not enough memory" problem is still here, too!
It appears like whatever problem I have, it also prevents me from using MegaWipe properly. Any more ideas?

Re: Help! "wrong UIDs" right after flashing Stock!? and lots of other Problems.
Try again.
Sent from my GT-N7100

Re: MegaWipe
UtkarshGupta said:
Try again.
Click to expand...
Click to collapse
Tried again. Twice. Internal SD contents were gone. Froze again after "Installation complete". Maybe that "Mega Wipe" took two seconds instead of one this time. The second time I tried flashing Omega after the wipe just for the kicks and that (full wipe Option in Aroma) apparently took my user data away, finally.
To my not-so-big surprise it greeted me with "Inconsistend System UIDs" right after startup, completely with the gapps FC I had already seen with stock so many times, now. This does not feel like real progress.
I have read around a bit. Maybe I should try to flash a multipart ROM in Odin with repartition? Appears to be pretty dangerous, though, and I dont know where to find one that matches my "DBT" CSC properly...

Re: Help! "wrong UIDs" right after flashing Stock!? and lots of other Problems.
Flash latest stock rom for your country.
Sent from my GT-N7100

Flashing stock that wipe ur internal and format sdcard.
Some stock rom dont wipe fully internal thus issue still exist even u flashing stock rom.

Re: Help! "wrong UIDs" right after flashing Stock!? and lots of other Problems.
u use CWM? i had a problem with cwm if i use aroma it always freeze use a other recovery and do the megawipes?? iam not very good at this but i wish you all the luck ..
Sent from my GT-N7100 using xda app-developers app

Re: MegaWipe
UtkarshGupta said:
Flash latest stock rom for your country.
Click to expand...
Click to collapse
XXDMB2 *is* the latest Stock ROM for my country. In my first post I described how I flashed it and it did not work out very well.
nameejokerx said:
Flashing stock that wipe ur internal and format sdcard.
Some stock rom dont wipe fully internal thus issue still exist even u flashing stock rom.
Click to expand...
Click to collapse
Yes, and which one would be such a ROM? I was not very adventurous with ROMS until now and did never flash multipart ROMs. I am afraid bad things could happen if I flash something with wrong CSC. Where exactly should I look for such a ROM and what do I have to take care of? Of course HOWTO pointers are welcome, too.
Sorry if this sounds too clueless but I really dont want to make things even worse.

Maybe SDS
Hi all,
after some more wiping and flashing, fiddling and tiddling and basically reinstalling everything from scratch, mostly without help from Titanium, I got my NoteII back to work. I only restored my most important app data, all apks reloaded from play store instead from backup, made several backups with twrp during this process. Two times, the "no space" problem came back and both times I basically reverted back to the last working backup from twrp. This way, I managed to turn it back into a usable system.
Not for long though, because two hours ago, in the midde of buying an ebook in kindle, my NoteII screen went black and now the whole thing is completely dead. I took out the battery for 10 minutes, but it won't come back on again; not even a download screen or battery loading animation.
So my problems might just have been the harbingers of its future death. I just read that "SDS" also affects some Note2 models and it has something to do with the internal storage which would be sort of a match for the symptoms I experienced. Looks like I'll have to send it in. Because of all the flashing and restoring I had not yet encrypted my internal storage and will have to change all passwords. Duh
I really should have stayed with my trusty old Note1 which never failed on me...