Develop Bugs

[Q] Infinite Reboot

I have been rooted for a while now and had bakedsnack 1.4 installed for about 2 months now. Everything was stable until a few days ago when it started rebooting randomly then much more often so I decided it was to time to update...went for Ava v9. After reseting factory defaults, wiping cache, wiping dalvik, I installed the rom. Immediate infinite loop reboot, tried this rom 2 more times then the newest baked snack then the plain rooted stock. All are infinite reboot loops...I have wiped numerous times now and can't seem to find a problem, I have updated my radios and everything trying to fix this to no avail. I could really use some help...here is a catlog of my bootup and 2 of the infinite reboots after a clean install.
pastebin.com/jBub3Upf
Also using amon-ra recovery and my root is full nand unlock.

same thing is happening to me. plz help. ava v9 running both stock kernel and kings 10 cfs. plz help. plz. i have the exact same problem. plz. i am bagging you. plz.
plz.
dk

Have you guys tried running a stock PC36IMG? That is the first thing I would try if I was in your shoes.
link to file: http://forum.xda-developers.com/showthread.php?t=791019

_MetalHead_ said:
Have you guys tried running a stock PC36IMG? That is the first thing I would try if I was in your shoes.
link to file: http://forum.xda-developers.com/showthread.php?t=791019
Click to expand...
Click to collapse
i have tried unrooting and rerooting, but not flashing a stock pc36img.zip. thanks for the link. megafileupload is wired do you mind sending me a mirror? i will post results. if that doesnt work, i am unrooting nd trying again. if that still doesnt work, i am bricked

dkdude36 said:
i have tried unrooting and rerooting, but not flashing a stock pc36img.zip. thanks for the link. megafileupload is wired do you mind sending me a mirror? i will post results. if that doesnt work, i am unrooting nd trying again. if that still doesnt work, i am bricked
Click to expand...
Click to collapse
devs, i'm not sure you get how serious this problem is, and how badly it needs fixing. i reboot any time i open a network connection. for example, when i boot up, even before htc sense loads, i reboot. i cannot stay up for more than 15 seconds. i have forcefully deleted all apps that even remotely might require data, and still somehow, i sync to my voicemail. boot up, pull down lock, reboot, stuck. plz help me i want to be able to use my phone.

dkdude36 said:
i have tried unrooting and rerooting, but not flashing a stock pc36img.zip. thanks for the link. megafileupload is wired do you mind sending me a mirror? i will post results. if that doesnt work, i am unrooting nd trying again. if that still doesnt work, i am bricked
Click to expand...
Click to collapse
Have you been able to get it downloaded? I just tried to dl it from megaupload again and it worked no prob.

Downloading it now, will try it out. Thanks!

download went fine. about to push and flash. wish me luck... i just want my evo back waaaaa

flashed it. first try, boot failed because of a pu fail. stuck in bootloader. tried agian, and worked fine. my phone is rebooting as we speak. lets see if it worked...
and the big question: should i stick with ava v9 or what other rom should i try? i have never tried fresh, and cyanogen is too unstable for me. i have pretty much only tried ava, omj, and cm. plz recommend the must tries etc. i'm not asking you to choose for me, just tell me what to try.
dk

SHOOT IT STILL WONT WORK! i booted just fine, and was able to set up just the google account. the second i hit finish for the google account only and it tried to sync contacts, reboot. please help me knowledgable people!
EDIT: once i rebooted, i dragged down unlock screen and BAM! reboot... sad me i just want my evo back

dkdude36 said:
flashed it. first try, boot failed because of a pu fail. stuck in bootloader. tried agian, and worked fine. my phone is rebooting as we speak. lets see if it worked...
and the big question: should i stick with ava v9 or what other rom should i try? i have never tried fresh, and cyanogen is too unstable for me. i have pretty much only tried ava, omj, and cm. plz recommend the must tries etc. i'm not asking you to choose for me, just tell me what to try.
dk
Click to expand...
Click to collapse
I had the EXACT same problem as you. Was the PU fail next to the boot line during the update? If so, then I think you've got bad blocks in your boot partition and I hate to say it but you might not be able to flash any custom kernels anymore. Once I finally got mine booted, the only kernel that worked was a stock one. I was able to flash Fresh, but HAD to keep the kernel stock. I ended up calling Asurion and filed a claim. Got my new evo today and am having no issues.

SHOOT IT STILL WONT WORK! i booted just fine, and was able to set up just the google account. the second i hit finish for the google account only and it tried to sync contacts, reboot. please help me knowledgable people!
EDIT: once i rebooted, i dragged down unlock screen and BAM! reboot... sad me i just want my evo back
Click to expand...
Click to collapse
That sucks man. Do what I did, file an insurance claim and get a new phone. They ship it out next day.

same problem I'm having:
http://forum.xda-developers.com/showthread.php?t=808280

ok i think i finally have it. but now, what rom to use? please tell me. i might be going with the cm nightlies. but plz give your opinion. thanks for the stock pc...zip. tweetqit, thanks for letting me overrun your thread..ha
TO GET IT TO WORK, ONCE YOU ARE STUCK IN BOOTLOADER, JUST RE-UPDATE AND THE BAD BLOCKS WILL GO AWAY. OR AT LEAST THAT WORKED FOR ME.

Yup, failed for me the first time but worked the second. My phone was never the same after I went through that ordeal. No custom kernels worked, terribly sluggish performance, constant reboots. That's why I said f*ck it and had Asurion send me a new one.

dkdude36 said:
ok i think i finally have it. but now, what rom to use? please tell me. i might be going with the cm nightlies. but plz give your opinion. thanks for the stock pc...zip. tweetqit, thanks for letting me overrun your thread..ha
TO GET IT TO WORK, ONCE YOU ARE STUCK IN BOOTLOADER, JUST RE-UPDATE AND THE BAD BLOCKS WILL GO AWAY. OR AT LEAST THAT WORKED FOR ME.
Click to expand...
Click to collapse
what'd you do? what exactly did it fix? everything?

On first try, boot: fail-PU. I guess this is a common problem? pretty lame. Will post after I try again.

Ok so now that, that failed..how do I try it again? when I reboot into recovery it just checks the PC36IMG.ZIP and dumps me back to the bootloader without asking me to install it...

I've done what I think dkdude36 did [install PC36IMG] and did get PU fail, and now i'm stuck in HBOOT/BOOTLOADER as expected. Now I only have the few options in bootloader and don't know what to do. I've rebooted and gotten the bootloops then wen't back into bootloader and it loads PC36IMG but it doesn't give me the option to update again. Am I supposed to do something in order for it to give me that option again? If so, what? As of now, I'm stuck and am bricked (hopefully not permanently).

Tweeqit2 said:
Ok so now that, that failed..how do I try it again? when I reboot into recovery it just checks the PC36IMG.ZIP and dumps me back to the bootloader without asking me to install it...
Click to expand...
Click to collapse
what if we run:
fastboot erase boot
fastboot erase recovery
what will happen? will it prompt me to update with PC36IMG.zip as it did the first time?

SOLVED! [Q] HELP! User data keeps disappearing after reboot!

"I don't know what specific directory or partition is messed up but every single time my phone reboot I think I lose my user data or something. All of my apps force close and the tutorial about how to use my phone keyboard starts as if I just flashed a new Rom. This keeps happening no matter which Rom I use. I don't know why this is happening. I've tried 2 different SD cards and it still happens. Please Help!"
I didn't exactly figure out what was wrong but I found a solution. There was something wrong with my cache partitions.
http://forum.cyanogenmod.com/topic/6433-solved-messed-up-partitions-on-internal-storage/

aznbatman said:
I don't know what specific directory or partition is messed up but every single time my phone reboot I think I lose my user data or something. All of my apps force close and the tutorial about how to use my phone keyboard starts as if I just flashed a new Rom. This keeps happening no matter which Rom I use. I don't know why this is happening. I've tried 2 different SD cards and it still happens. Please Help!
Click to expand...
Click to collapse
What ROM(s) are you using? From the Terminal Emulator, have you tried running fix_permissions? I run Redemption, and when I install a new version of it that's the first thing I do, then reboot.

RMarkwald said:
What ROM(s) are you using? From the Terminal Emulator, have you tried running fix_permissions? I run Redemption, and when I install a new version of it that's the first thing I do, then reboot.
Click to expand...
Click to collapse
I'm running redemptive 1.9 and I've tried multiple other roms and still have the same problem. Fix permissions didn't work either. I get an error with the packages.XML file. This problem happens no matter what rom I try.

Hey guys. I had the same $#it happen to me last week! I was sitting on the couch and cleaning my rooted Droid with stock Rom... and when I held the power button to shutdown phone I got a long vibrate instead of the usual short one! This got my attention, and sure enough, when I finally took out the battery and reported, I got the UIDs are inconsistent.... error along with the I'm feeling lucky button. Force Closes, galore! I fixed it by doing a hard reset and basically returning my phone to factory setting. Still rooted, but lost all my contacts,favorites, texts, apps... basically everything that wasn't on the SD card...:-/ still trying to restore all my settings... it was perfectly set to how I wanted it.
Sent from my ADR6300 using XDA App

Uber kingdom revo 3d rls7

Installed, went to reboot system, all it does it go to the htc incredible screen, reboot, htc incredible screen, then goes to recovery. wtf over?
so i formated the cache, dalvik, and fixed permissions and still no luck.
what do i do next?

I second this...
In fact, today was the very first day it wouldn't do that when I flashed a Sense 3.0 ROM... now it's back to not flashing them anymore.

They weren't kidding in the instructions where it says to wipe cache/data three times. I started from scratch, wiped everything a bunch of times, reinstalled and it worked. My phone is very picky, because when I flash any ROM, it will never load the first time unless I go back and re-wipe everything. It's a pain, but it's a nice rom. Only thing i found that doesn't work is the flash on my camera, and the flashlight.??

RMinor205 said:
They weren't kidding in the instructions where it says to wipe cache/data three times. I started from scratch, wiped everything a bunch of times, reinstalled and it worked. My phone is very picky, because when I flash any ROM, it will never load the first time unless I go back and re-wipe everything. It's a pain, but it's a nice rom. Only thing i found that doesn't work is the flash on my camera, and the flashlight.??
Click to expand...
Click to collapse
What version of Clockworkmod are you using?

I had made sure I had done it several times.... and it's very arbitrary to be honest it seems whether a ROM will flash or not. RLS7 seems to flash just fine... but I can't get .5 on there again... I'll see what I can do..

Yeah... so apparently my phone is an exception of sorts... it seems like I've been having trouble flashing any sort of Gingersense ROM... but I am able to get RLS7 onto my phone. It's booting now. But I can't for the life of me seem to be able to get .5 on there. What's the difference anyways? Anyone.\lol
**By the way, I am 100% sure I wiped everything 3 times... and it would still get stuck on splash screen.

BrettApple said:
What version of Clockworkmod are you using?
Click to expand...
Click to collapse
3.0.0.8
i'm going to update to RLS 0.5... maybe. Just to see if that fixes the bug.
It says "flash disabled due to cold weather, low battery, or use of an app that uses a lot of battery power".
I live in Florida, have a full battery, and haven't re installed any apps.

Installing 0.5 - hopefully it worked.

Wiping several times DOES NOTHING. No matter if you say it did or not. The way to fix that, as I have had it happen is simply flash the rom again without wiping. So, say you wipe and flash, reboot, it goes back to recovery, just install zip again.

I also have the "flash disabled due to cold weather, low battery, or use of an app that uses a lot of battery power". Full battery, no high power apps running.

[Q] TWRP - what's it doing?

OK, admitted n00b here. Go easy on me. I turn 60 next week
Anyways, I had no problem installing TWRP on my Kindle Fire. Made a backup. For some reason it didn't install Superuser so I installed that and OTA Rootkeeper. I can not for the life of me remember if I installed FFF (and I just did this yesterday). I used KFU and had no issues with drivers or connectivity or any of that. Following prompts it appeared to be doing exactly what one would expect.
NOW, however, I booted to TWRP to look around. Version is 2.2.1.
On screen at the upper right is a home icon, a back icon, and another one that looks like a little notepaper that I have absolutely no idea what it's for.... BUT (and it's a big but) I must have touched it as I was setting the Kindle in it's upright position in it's case.
I says:
* Verifying filesystems...
* Verifying partition sizes...
And there it sits. Been sitting here about 10 minutes. I have no idea what that icon in the far upper right corner does or what process I may have started. But it seems stuck.
So what's it doing? (Or what's it SUPPOSED to be doing?)
Thanks
Charlie

cjparker said:
OK, admitted n00b here. Go easy on me. I turn 60 next week
Click to expand...
Click to collapse
Nice
I can not for the life of me remember if I installed FFF.
Click to expand...
Click to collapse
FFF is your bootloader. It is the very first thing you see in action when you turn the device on. It will either be a blue Kindle Fire logo, Kindle Fire logo w/Android, or yellow triangle. If you don't see any of the aforementioned boot logos at startup, you don't have FFF installed.
and another one that looks like a little notepaper that I have absolutely no idea what it's for....
Click to expand...
Click to collapse
That is nothing more than a log. It allows you to go back over everything and look at error messages or whatever. Nothing to worry about.
I says:
* Verifying filesystems...
* Verifying partition sizes...
Click to expand...
Click to collapse
This may be from the backup you just created, but if you aren't experiencing any adverse effects such as inability to install ROMs or your backups not bring created, I wouldn't worry about.
And if worse comes to worse and there is something wrong with your device, there is an extremely good chance that it can get fixed pretty easily.

soupmagnet said:
Nice
FFF is your bootloader. It is the very first thing you see in action when you turn the device on. It will either be a blue Kindle Fire logo, Kindle Fire logo w/Android, or yellow triangle. If you don't see any of the aforementioned boot logos at startup, you don't have FFF installed.
That is nothing more than a log. It allows you to go back over everything and look at error messages or whatever. Nothing to worry about.
This may be from the backup you just created, but if you aren't experiencing any adverse effects such as inability to install ROMs or your backups not bring created, I wouldn't worry about.
And if worse comes to worse and there is something wrong with your device, there is an extremely good chance that it can get fixed pretty easily.
Click to expand...
Click to collapse
OK, well now I feel even more n00b-ish. Since you said it was a log, I touched the icon again and it went back to TWRP main screen.
Sheesh.... all those years in IT at the university taught me SQUAT... hehehe.
When the Fire boots up now I see Kindle Fire with the word "Fire" in blue. It says at the bottom to press the power button for boot menu. If I touch nothing it changes so the word "Fire" is yellow (or yellow-orange-ish) and it boots normally.
So I've obviously installed TWRP. How do I know if I installed FFF?
Finally, and I swear I've looked for this, is there a post that has step-by-step how to flash a new ROM? Like once you have TWRP installed and you aren't having connection/driver issues, here's what you do. There's a lot of information on this, but some is old and it gets tough to see what's the most current. It *LOOKS* (to this n00b) like I put a ROM.zip into the /sdcard directory, boot to TWRP and Install it from there. Then I see various mentions of "you should wipe first". Ok, wipe what? There are lots of choices what to wipe when I look in TWRP.
I am assuming (and I hate doing that) that I can get back to where I am now by restoring the backup I made yesterday.
And when I boot to Windows 7 (I normally use linux) to run KFU< WHEN I plug in the Kindle using the USB, the Kindle tells me I can transfer files. I haven't really looked again, but can I just copy a whatever-ROM.zip over to the /sdcard right from the windows file manager?
Apologies for all the questions, and I have read the suggested n00b stuff, and I really do kinda understand what's going on, but I think I hae analysis paralysis

cjparker said:
How do I know if I installed FFF?
Click to expand...
Click to collapse
The blue (and white) Kindle Fire logo is FFF.
And when installing a new ROM, wipe System and Factory Reset. Everything else, you seem to have under control.

soupmagnet said:
The blue (and white) Kindle Fire logo is FFF.
And when installing a new ROM, wipe System and Factory Reset. Everything else, you seem to have under control.
Click to expand...
Click to collapse
See what happens when you get old? You get CRS.... Can't Remember S.......stuff .....
Ok. Gonna see if I can find a ROM that sounds interesting and reliable and see if I can do this without brickin' it. At least once.
Thanks!

cjparker said:
See what happens when you get old? You get CRS.... Can't Remember S.......stuff .....
Ok. Gonna see if I can find a ROM that sounds interesting and reliable and see if I can do this without brickin' it. At least once.
Thanks!
Click to expand...
Click to collapse
Nice. I have a new ROM (CM10+3.x Kernel)
It wiped my Draw Something games with my wife. We were up yo over 150 drawings. Can't seem to find the login I used. Maybe I shouldn't have flashed the gapps.zip onto it.
Oh well. Live and learn. Seems to run nice.
Thanks again. At this point it loks like I can actually flash a new ROM without ever having to reconect to my PC. I just download it to the Fire, move it to /sdcard, reboot to TWRP and away we go.
Thanks again!

Yep.
You made a backup of your last ROM, correct? Restore it and install Titanium Backup. Use it to back up all of your apps and app data onto the sdcard so you can install it your new ROM.

soupmagnet said:
Yep.
You made a backup of your last ROM, correct? Restore it and install Titanium Backup. Use it to back up all of your apps and app data onto the sdcard so you can install it your new ROM.
Click to expand...
Click to collapse
Okay. Makes sense.
I knew there had to be an easier way to keep the apps and settings or folks wouldn't be so quick to try new ROMs.
Thanks AGAIN, soupmagnet.
And yepper on the backup. I've restored it twice just trying new stuff.
Time to restore it again and install Titanium Backup... hehehe

:good:

[Q] Help needed- Bootlooping

HI,
I am facing a peculiar kind of a problem. I recently rooted my Desire Z following the cyanogen wiki to the letter. I have tried many ROMS but whichever ROM I install, I am facing this problem. For the first few days of Install, my phone works perfectly. But after a few days if I reboot, my phone gets stuck is a bootloop( i dont know if thts the right word, coz it boots and it starts the android but before the launcher is started it restarts again.
First I was using Flinny's CM10.1 test builds, and then I changed it cause I thought that was the problem. Now I am using Andromadus' Mimicry 1.5 which is also giving me same problem.
Everytime this happens I have to use the PCIMG10 file to restore it and then root it again and then install the ROM..
Is there any way to solve this problem.. I'll provide logs if u require... I am desperate..

yes a log cat would help much maybe a cat /proc/last_kmsg or have adb running during the bootloop and post here.
seems a strange issue and may just be an evil app installed or something else entirely but without more info i would just be guessing. and do actually have to reroot? i mean what would happen if you were just to wipe clean and install a new rom via recovery? also it may help so could you provide all that is on your bootloader screen
also see HERE for some more help, feel free to post in there as well (trying to reduce the clutter in these forums)

demkantor said:
yes a log cat would help much maybe a cat /proc/last_kmsg or have adb running during the bootloop and post here.
seems a strange issue and may just be an evil app installed or something else entirely but without more info i would just be guessing. and do actually have to reroot? i mean what would happen if you were just to wipe clean and install a new rom via recovery? also it may help so could you provide all that is on your bootloader screen
also see HERE for some more help, feel free to post in there as well (trying to reduce the clutter in these forums)
Click to expand...
Click to collapse
I have a logcat from when I was running Flinny's CM10.1 test builds.. I faced this many times with that ROM and so I took a log last time it happened.
BootLoopLog_CM10.1
The latest time since I was in a hurry to get my phone back to working condition couldnt get a log. But soon after, it happened again. I installed only "Explorer" and "What'sapp" when this happened again. I have captured the logs and here it is.
BootLoopLog_Mimicry1.5
And ya I did try and restore a previous backup, and I also tried wiping and installing the ROM, but in both the cases the Phone will hang at the boot animation screen or restart again. Here attached is a log of the phone restarting after a clean wipe and fresh install of the ROM.
BootLoopLog_Mimicry1.5-after reinstall
Code:
Bootloader screen info
VISION PVT ENG S-OFF
HBOOT-0.84.2000 (PC1011000)
MICROP-0425
RADIO-26.03.02.18_M3
eMMC-boot
Sep 8 2010,15:56:30
Please help me out... this is kind of frustrating.
P.S- I did see that thread.. but since my phone was not bricked, I didnt post it over there..

are you sure you did a full wipe? there was definitely more than just a couple user apps installed, could be some leftovers from last rom. there isnt anything im seeing too specifically in the logcats to show your issue, all of them seem to bootloop in slightly different times but while running some java system frameworks
anyhow, if you were to start completely fresh, unroot, reroot, flash rom, etc - all works fine? lets say you just signed into gmail, then reboot phone, would it loop? or do you need to run the os for some time then turn it off and then it happens?
for now how about this, flash THE DZ ONE through bootloader as described in the thread,
then flash SUPERWIPE through recovery
then when all is done flash rom of choice, for fun lets do mimicry, let it boot, sign into google, let phone sit like 10min, choose reboot and see what happens

demkantor said:
are you sure you did a full wipe? there was definitely more than just a couple user apps installed, could be some leftovers from last rom. there isnt anything im seeing too specifically in the logcats to show your issue, all of them seem to bootloop in slightly different times but while running some java system frameworks
anyhow, if you were to start completely fresh, unroot, reroot, flash rom, etc - all works fine? lets say you just signed into gmail, then reboot phone, would it loop? or do you need to run the os for some time then turn it off and then it happens?
for now how about this, flash THE DZ ONE through bootloader as described in the thread,
then flash SUPERWIPE through recovery
then when all is done flash rom of choice, for fun lets do mimicry, let it boot, sign into google, let phone sit like 10min, choose reboot and see what happens
Click to expand...
Click to collapse
What I mean by full wipe is.. First I would do the factory reset from recovery, then proceed to wipe the "cache partition" , dalvik cache, battery stats, and then in the mounts and storage menu, again do a format of cache, data and system... Is there anything else I should do to do a clean wipe?
And If i start fresh, nothin happens immediately.. u need to let the OS run for a day or two and then this happens..
Anyways.. i'll try what you suggested and get back to you.... thanks for all the help..

manujosephv said:
What I mean by full wipe is.. First I would do the factory reset from recovery, then proceed to wipe the "cache partition" , dalvik cache, battery stats, and then in the mounts and storage menu, again do a format of cache, data and system... Is there anything else I should do to do a clean wipe?
And If i start fresh, nothin happens immediately.. u need to let the OS run for a day or two and then this happens..
Anyways.. i'll try what you suggested and get back to you.... thanks for all the help..
Click to expand...
Click to collapse
I did what you suggested.. and the phone is not rebooting as of now... I'll run the OS for a couple of days..and see what happens.. i'll keep you posted..

manujosephv said:
I did what you suggested.. and the phone is not rebooting as of now... I'll run the OS for a couple of days..and see what happens.. i'll keep you posted..
Click to expand...
Click to collapse
Guess what... That worked... My phones been running without bootloop till now.. :good:
Everytime I reboot, my heartbeat increases.. but it comes through smoothly at the end.. thanks a lot..
P.S - Completely off the topic.. Mimicry ROM is giving me insane battery life.. Running the phone more than 1 day without charging.. :laugh: