Develop Bugs

Looking for some help...

Ok all, i think i have hit my limit of what i can think to do to fix my phone so i'm throwing this out looking for some help.
So i have run into a major problem. Starting back on the first i flashed from CyanogenMod Nightly 175 to nightly 181, 181 FC's alot on the google processes framework and such, and it was unusable so i went back to my Nightly 175 restore i had created. It was working fine until today and it became unusable, FC's for everything.
So i first started by trying to get into Safe Mode to do a restore, and RomManager FC'ed before i could get it to do anything
Then i tried to get into the restore area, same thing, FC
Tried to use the notification Tray icon to "update" to 181, same thing FC
All these steps were attempted again after a normal reboot
None worked
I then went to reboot into recovery, and it only would reboot into the Bootloader
Once in the Bootloader i tred to do the Recovery option, but all it does is reboot into the bootlaoder
I do know that i had just updated the RomManager recovery option to 5.0.2.0 or whatever the latest was. I'm wondering if there is a problem with that?
My phone was originally reflashed with unrevoked 3.
i went to dougpiston.com and got the RUU program from there after searching through some forums, but that program when run says it is unable to communicate with my phone when attempting to verify software on my phone
I also tried un-sync'ing all of the google accounts on the phone and a factory reset, but even after the reboot the last account is still there and it appears as if the factory reset did not work
I also have this posted over in CM's forums, but i was hoping maybe someone here could help.
anything is appreciated at this point

garaxiel said:
Ok all, i think i have hit my limit of what i can think to do to fix my phone so i'm throwing this out looking for some help.
So i have run into a major problem. Starting back on the first i flashed from CyanogenMod Nightly 175 to nightly 181, 181 FC's alot on the google processes framework and such, and it was unusable so i went back to my Nightly 175 restore i had created. It was working fine until today and it became unusable, FC's for everything.
So i first started by trying to get into Safe Mode to do a restore, and RomManager FC'ed before i could get it to do anything
Then i tried to get into the restore area, same thing, FC
Tried to use the notification Tray icon to "update" to 181, same thing FC
All these steps were attempted again after a normal reboot
None worked
I then went to reboot into recovery, and it only would reboot into the Bootloader
Once in the Bootloader i tred to do the Recovery option, but all it does is reboot into the bootlaoder
I do know that i had just updated the RomManager recovery option to 5.0.2.0 or whatever the latest was. I'm wondering if there is a problem with that?
My phone was originally reflashed with unrevoked 3.
i went to dougpiston.com and got the RUU program from there after searching through some forums, but that program when run says it is unable to communicate with my phone when attempting to verify software on my phone
I also tried un-sync'ing all of the google accounts on the phone and a factory reset, but even after the reboot the last account is still there and it appears as if the factory reset did not work
I also have this posted over in CM's forums, but i was hoping maybe someone here could help.
anything is appreciated at this point
Click to expand...
Click to collapse
You're problem is ClockworkMod. Version 5 is a steaming heap of crap that's caused this sort of problem, not only for dInc users, but Tbolt and other device users. The solution seems to be flashing back to an older recovery. And if it works, don't fix. I'm still running version 3.something on my Tbolt and have no plans to change that. I NEVER use ROM Manager and recommend nobody ever touch it except for a few things. I almost never have it installed on any device.

OK then dumb question but if RomManager FC's on me, how do i flash back to a working version or to an alternate version entirely? i have been unable to find other ways of flashing outside of RomManager

Older Recovery versions are available on "dougpiston.com" just follow the directions.

www.dougpiston.com has what you're looking for under "recoveries". They're flashed in hboot like a radio, RUU, splash screen, etc.

Also if that doesn't work, which it probably will, you can also flash a PB31IMG which essentially is the RUU but you do not need a PC. You put that on the root of the SD (as in, not in any folders. Probably know that already...) and reboot into HBOOT (Power and volume down) and itll load it up.
Note: Make sure the file is PB31IMG.zip and not PB31IMG.zip.zip

Ha!!! got it back (well on the road to back anyways)
Was able to find a PB31IMG on dougpiston.com and hboot flashed it in (3.0.0.8). I had one on my PC but it must have been corrupt because it didn't work before. once that was working i was able to get into recovery get a restore back to my 175 nightly and am in the process now of flashing nightly 181 on there cleanly and rebuild the whole phone from scratch. damn i hope this works thanks all for help and ideas.

Nice, I actually had the same problem when I updated cwm but it was way back when they first updated to the 2.x.x recoveries. I was freakin for a bit lol....glad you got it working. Does anyone know why whenever I flash a different version of cwm I have to flash it twice?
Sent from my ADR6300 using xda premium

pete_kowalski83 said:
Nice, I actually had the same problem when I updated cwm but it was way back when they first updated to the 2.x.x recoveries. I was freakin for a bit lol....glad you got it working. Does anyone know why whenever I flash a different version of cwm I have to flash it twice?
Sent from my ADR6300 using xda premium
Click to expand...
Click to collapse
No idea...are you using ROM Manager?

DEFY running on CM7 in Boot Loop

Hi All,
I am noob. I recently flashed my stock froyo and rooted the phone and loaded CM7. It had bee working good till today. I think I messed with perfomance under Cyanogenmod settings.
When I got my phone rebooted, its stuck in the boot loop. First google with Motorola logo appears.Then CM7 skater board logo appears.Then phone vibrates.Again CM7 skaterboard logo appears.It goes on.I dont know what to do.Please help me out.

yep you definitely screwed up something! LOL
Im assuming you still have access to bootmenu, I would enter custom recovery (not stock recovery) and wipe the phone. If you are concerned about losing your data try wiping just the cache and dalvik cache. If that doesn't work then wipe data. If that doesn't work you will have to wipe data and reflash cm7. If that doesn't work you will have to start from scratch by wiping in stock recovery and using RSD to flash a froyo sbf.

@zyxwvut:Thanks buddy.
I didnt have access to the custom recovery. I flashed the froyo sbf.Now my defy boots into the stock froyo. I need to get back the cm7.
I rooted it. downloaded 2nd init.
But now when I am installing 2nd init recovery, the app is giving ('downloading files...will install after downloading) and it starts downloading(over wifi) but later the app is not responding and i have to close it again.
What should I do.I am not confident enough to use adb shell

I have a couple thoughts on this... One is that you should be sure usb debugging is enabled in order for this to install properly, I'm wondering if it is downloading but when it gets to the install it is failing because usb debugging is not enabled.
If all else fails you can install the old school tenfar's recovery, I believe this will work just fine. If it doesn't then I guess the worst that would happen is that you would need to start from scratch again.
Tenfar's recovery can be found here http://www.multiupload.com/8T81G1Q8MY
Like I said I'm pretty sure it will work to install cm7 however there a couple things you must know.
1. Usb debugging must be ENABLED to install this custom recovery
2. Once it is installed you MUST DISABLE usb debugging or it will not boot to recovery
3. You must open the app and select boot to recovery to enter custom recovery
4. 2nd init is included in the cm7 zip file so it will be automatically installed
5. You must cross your fingers and keep one eye closed during this process.... j/k

Thank you..
I had kept USB debugging on. After pressing 'wait' on not responding window.I got a command 'no root detected, is superuser installed?'. I had rooted and kept superuser to 'allow' command.but still i have the same no root message coming.Should I root the phone again?
If everything fails, I will try TenfARS RECOVERY. Can you please tell me whether it would create any problem if I do update sdcard .zip from stock recovery instead of custom recovery?

Now wait a second! It's not granting root permissions? Did you reboot the phone after rooting it? You MUST reboot after rooting or SU will not work properly.
Since the bootloader and stock recovery are locked down, the custom update.zip will not properly pass signature checks in stock recovery. ie: not signed my MOTO
Just a hunch but I think you need to reboot your phone and try installing 2nd init again and SU should work properly. Thats what is going on, I'm almost sure of it

Thanks zyxwvut
I rebooted the phone. Still there was some problem.I cleaned the data in su.The it told my su binary is outdated.So I downloaded the new binary.
I uninstalled the 2nd init I downloaded.And again downloaded it. Then installed the recovery and this time too it failed.
I browsed net for possible answers and in one forum I found a thread that when superuser is set to 'always allow' it brings some problem.Then I set the super user to 'prompt' and that worked.I could install custom recovery and install CM7.My defy is now running on CM7.
Thanks to you and this forum

Interesting.... I never would have thought of that. Of course in every situation that I've rooted SU is ALWAYS set as default to 'prompt' for access. That's probably why I have never seen this problem, but it is definitely good to know. Anyway I'm glad you got it figured out, CM7 is by far superior in terms of performance and I'm sure you will love it on your Defy. FYI you can play around with cpu frequencies and voltages in bootmenu to achieve ultimate performance and battery life. I wouldn't recommend going above 1300 Mhz (1000 Mhz is default) and keep vsel3 no lower than 56 (thats just my opinion though) you will know the vsel is too low if the phone reboots randomly or simply doesn't boot. Every cpu is different so the default settings are "safe" settings but can definitely be adjusted. I keep the clock settings default but I run vsel1=22 vsel2=38 vsel3=56. Be sure to 'save' settings after adjustment. These settings work great for me (after months of playing around) with no problems but your mileage may vary.
Cheers!

Thanx buddy
Can you tell me what is meant by VM heap size?

[Q] phone keeps restarting. need help

i bought the phone rooted already. its running aokp milestone 5 and franco.kernal milestone 3. i restarted the phone the other day and i got the android is upgrading..optimizing applications #of#. after it finished it would crash and reboot and ill get the android is upgrading message again and it would crash and reboot and repeat the whole process. i tried wiping the data through cwm and it would do the same. i tried restoring the backup and it would do that same. can anyone help me with this problem? im stuck with a blackberry until i can fix my phone. i already tried searching. thanks

antn said:
i bought the phone rooted already. its running aokp milestone 5 and franco.kernal milestone 3. i restarted the phone the other day and i got the android is upgrading..optimizing applications #of#. after it finished it would crash and reboot and ill get the android is upgrading message again and it would crash and reboot and repeat the whole process. i tried wiping the data through cwm and it would do the same. i tried restoring the backup and it would do that same. can anyone help me with this problem? im stuck with a blackberry until i can fix my phone. i already tried searching. thanks
Click to expand...
Click to collapse
wipe and reflash the rom. or wipe and try another rom and kernel. every time you wipe, you want to reflash.

yea i already tried doing that and it would do the same thing.

I would try going into recovery and load a restore point first, hopefully there IS one.
I had this happen a few times to me while over flashing and restoring fixed the problem.

I'd rather flash the takju build via fastboot using efrants step by step instructions. If I were to buy a used phone I'd want to do all the rooting and flashing as if it were a new device.
- Google

kvirus11 said:
I would try going into recovery and load a restore point first, hopefully there IS one.
I had this happen a few times to me while over flashing and restoring fixed the problem.
Click to expand...
Click to collapse
restore point? lmao! theres no such thing. you can restore a nandroid backup, but i doubt the previous owner would leave it in your sd storage considering all his/her personalinformation/data would be contained in it.

i got it to work now. i was able to learn and unroot the phone through the guide. at first i thought it wouldnt work cause i couldnt access the phone to put it in debugging mode but i guess it was already on and i did the whole unrooting process and flash stock image with no problems. thanks guys

Seem to have soft bricked my SGH-i747

I'd like to start by apologizing for what is probably the 9,000th "help, I've bricked my phone!" thread. I did some searching, and while I found many, I wasn't able to find one that both dealt with my specific issue, and did so assuming a level of newbishness appropriate for me.
Months ago, I rooted my AT&T Galaxy SIII, and installed CM10. It's been all candy and rainbows since. This morning, I somewhat foolishly decided to update from a nightly I installed in October/November, to the January 7 CM 10.1 nightly, using the built-in updater I had previously used to switch to a nightly.
It worked...sort of. I guess I should have cleared my cache or something ahead of time, because almost all of my GAPPS stopped working. Woops! Figuring that I should probably stop dicking around with my phone until I learned a bit more, I just went back and told the phone to switch back to the nightly I from October/November that I was previously using.
It didn't work. My phone now reaches the CM boot animation and just...sits there. And sits there. And sits there. To complicate the issue, I cannot get the phone to boot into recovery mode (although admittedly, I'm too thick to know what I'm meant to do once I'm there anyway). I CAN get the phone into download mode, but not being sure what I should do there, I thought it best to consult you all on what to do next.
I'm happy to give any additional information needed, and I hope it goes without saying that I am extremely thankful for any help you all can offer.

Try to get it back into recovery by taking the battery out, putting it back in and then holding volume up, home, and power. If you are sure you can't get it into Recovery, but know for sure you can get it into Download, go into Download and flash stock and go from there. These aren't bricks. These are just whoops. Lol.

If you can reach download mode, you'll be okay. What you want to do is use Odin to flash a rooted stock image; from there, you should be able to get back to a point where you can re-install a custom recovery of your choice and try flashing your favourite ROM again.
For the record, it's always a good idea to clear data/cache when changing ROMs, or changing between major revisions of a ROM (such as CM10 -> CM10.1) to avoid this sort of problem.

Actually, you should always wipe cache and dalvik when flashing the update. If it is a major update like 4.1.2 to 4.2.1, then you should wipe cache, wipe dalvik, Factory Reset, Format System then flash your ROM.

Move important files to SD using twrp file manager. Put rom on SD with gapps. Format internal, wipe caches, format system, factory reset, load ROM, load gapps. Reboot.
Sent from a Horny Pink Pony

smelenchuk said:
If you can reach download mode, you'll be okay. What you want to do is use Odin to flash a rooted stock image; from there, you should be able to get back to a point where you can re-install a custom recovery of your choice and try flashing your favourite ROM again.
For the record, it's always a good idea to clear data/cache when changing ROMs, or changing between major revisions of a ROM (such as CM10 -> CM10.1) to avoid this sort of problem.
Click to expand...
Click to collapse
I did this, being careful to follow all the instructions provided. Odin seemed to think everything worked, and after about 10 minutes, it rebooted the phone.
However, it still gets stuck. Now, since CM is no longer installed, it just sits at the SAMSUNG logo forever.
It still boots into download mode, and will now boot into recovery as well. Any suggestions?

naporeon said:
It still boots into download mode, and will now boot into recovery as well. Any suggestions?
Click to expand...
Click to collapse
Boot to recovery and clear data and cache.

smelenchuk said:
Boot to recovery and clear data and cache.
Click to expand...
Click to collapse
Worked like a charm, thanks! Can't believe after all that trouble, I didn't think to do that myself. >.<

[Q] [ROM][10 Sep][4.0.4][Sense 4.1 Lite][OTA|HUB|EQS... -- stuck bootscreen

Greetings,
I would have liked to post this questions, where it belongs to, but I'm new to this forum, so I put it here.
Last September I've updated my DHD following the instructions given in the thread mentioned in the headline and everything was fine. Yesterday in the evening, I got the notification to restart using the recovery mode, because something in the context of the superuser should be updated or modified. Because it was not the first time, I just did it. But this time, after rebooting, the device stopped with the HTC bootscreen (green HTC on white background).
After 10 minutes I took out the battery and restarted again. Again I was able to choose recovery mode, but while starting the DHD got stuck with the bootscreen. I decided to wait and just put it aside showing the boot screen, but the result this morning was that the battery is empty and nothing changed.
Does someone know about that issue and what do I need to do to get the device to work again? Why was this update needed in the first place?
Thanks a lot in advance...

im not sure why
but have you tried re-flashing the ROM?

PHOENIX-9 said:
im not sure why
but have you tried re-flashing the ROM?
Click to expand...
Click to collapse
Not yet. I was afraid to loose all data and maybe exchaning a file would also do the job. I mean, the update of the superuser component has changed something and this could be corrected again.

If you don't wipe your data partition (dirty flash) and you flash the exact same ROM, you shouldn't lose data.

KKrittel said:
Not yet. I was afraid to loose all data and maybe exchaning a file would also do the job. I mean, the update of the superuser component has changed something and this could be corrected again.
Click to expand...
Click to collapse
try to back up your ROM
do a clean install..then restore only the data (advanced restore)..wipe dalvik and cashe
if it didnt boot..you can restore your data using titanium backup pro from the CWM back up

PHOENIX-9 said:
try to back up your ROM
do a clean install..then restore only the data (advanced restore)..wipe dalvik and cashe
if it didnt boot..you can restore your data using titanium backup pro from the CWM back up
Click to expand...
Click to collapse
Tried to make a backup, but it recovering did not work. Doesn't matter. I just flashed the same image again, downloaded 'my' apps and restored the status from before the crash.
Nevertheless the same notification showed up, saying that the superuser kernel needs to be updated and I should use 'recovery mode' again. With a bad feeling, I did it again, but this time it works.
So to sum it up: device was useless for some days, restored it with some effort and now it works again. But I need to get prepared for the next time and to think of an app to backup all apps including app-data.
...but as always, this is a task for laaaaater
Thx,
Karl