Develop Bugs

[Q] CM7 Random Reboot and RE Setup Issue

Hi,
I am having a really odd and very frustrating issue with the latest CM7 Stable Build on my device.
I have been using the latest stable since its release back in November.
I ensured a clean wipe and install of CM 7.1.0.1 and setup my phone accordingly and Nandroid Back Up around a Week later as the Device was behaving as intended.
Sadly, I am now plagued with the following issue which occurs without any common trigger....
I will be using the device which will be behaving normally and it will suddenly, normally when screen is off... reboot and enter a Boot Loop (CM7 Robot will either be frozen solid or will keep rebooting to CM7 Robot) which seems to continue until a battery pull.
I will then restart the device and it sometimes boots straight away though sometimes hangs for a while. Once booted it boot to the 'Setup your device' Screen, from which point onwards you are required to Re-Enter your Logins for Google and such like. All settings and sync profiles are normally missing/deleted so requires setting up of all apps requiring logins etc.
As you can imagine, the above is quite an inconvenient as it normally happens when I actually need to use the device
I have tried reinstalling a clean CM7 over the top as well as wiping and formatting the SD card.
Neither seem to have solved the issue.
Any help anyone can give would be greatly appreciated.
It is also worth noting that while the device will charge off USB, it will not allow usb tethering or any form of USB Mounting etc.
Cheers
Jason
Device Spec:
Phone: HTC Wildfire Alpharex S-Off
Android: 2.3.7
OverClocked: 518.4MHz-691.2MHz (SmartAssV2)
VM Heap Size: 24m
ROM: CyanogenMod-7.1.0.1-buzz
Radio: 13.55.55.24H_3.35.20.10
Recovery: ClockworkMod 2.5.0.7
Kernel: 2.6.35.14-nFinity arco(at)tuxbox #1
Custom MTD Partitons using S2E

cm7 issues.
sounds like your in quite a pickle my friend.
i used to get your reboot issues (the bootloops) but that was because my phone was overclocked to over 700. i never got the setup device screen though.
when you say youve tried a clean install over cm7 have you factory reset the device as well as deleteing the dalvik cache??
also my sound stupid but have you tried your backup to see if it starts again??
it sounds like something has became quite corrupted.
have you installed any new apps recently or changed anything in the system files of the phone?
also when you have to go through the set up are all your apps still there afterwards? And when you first flashed it did the tethering work at all?
Heavy_metal_man.

heavy_metal_man said:
when you say youve tried a clean install over cm7 have you factory reset the device as well as deleteing the dalvik cache??
Click to expand...
Click to collapse
Yup
heavy_metal_man said:
also my sound stupid but have you tried your backup to see if it starts again??
it sounds like something has became quite corrupted.
Click to expand...
Click to collapse
Yup and while it does restore to a point where I can use my phone quite quickly after however I'm very cautious after - typically it happens a couple of weeks later
heavy_metal_man said:
have you installed any new apps recently or changed anything in the system files of the phone?
Click to expand...
Click to collapse
No real new recent apps installed and no mods to the system files that I can recall.
heavy_metal_man said:
also when you have to go through the set up are all your apps still there afterwards? And when you first flashed it did the tethering work at all?
Heavy_metal_man.
Click to expand...
Click to collapse
All my apps are still installed but many apps require re-setup or accounts for sync require re-adding. Phonebook requires import of contacts however messages remain in place.
I can't recall I think it did or at least USB-Storage did

Do you have a SD ext partition?
I ask because I had similar problems (randomly losing data) with an ext 4 partition, repartitioning my card using ext 3 solved it, also put your dalvik cache and data back into phone memory if it isn't already as that can also cause instability.
Sent from my HTC Wildfire using xda premium

Try this....
Run an RUU for wildfire.
- Download (RUU_Buzz_HTC_WWE_1.14.405.2_R_C_Radio_13.45.55.24 _ 3.35.15.19_release_141106_signed) from android forums.
- Connect phone to PC and run RUU
- This downgrads phone OS to eclair (android 2.1)
- Let it do the bizniss
- Re-root with unrevoked 3
- Re-Flash CM7 and gApps

Many thanks Scratch and Arkose,
Since my post last week I have since formatted the SD Card as well as Wiping the Phone as much as possible.
I then flashed and installed the latest CM7 Stable, Radio Package as well as re-setting up the EXT Partition this time as Type 3.
Once up and running I reinstalled all Apps.
Seems to be running okay so far.
Long may it last hopefully.
If not will try last suggesion

Great stuff. Let us know how it goes
Sent from my HTC Wildfire using XDA App

A quick update...
Still having issues
I'm noticing that randomly phone process will crash for no apparent reason/cause, normally when off Wifi and on Mobile Data.
Last night was the worst its even been though... at a critical moment when I needed the phone to work... it decided it was having none of it.
Phone kept switching Airplane Mode On and Off causing process.android.com to crash along with most other services So I rebooted only to find that it now was either stuck in Airplane Mode or couldnt enable to Radio (No Phone Signal at all) so I did a battery pull while trying to walk home in the pitch black and rebooted.
The Saga continued even after a battery pull, I eventually as I got in the door was able to use the 'Torch' and recieve a phonecall before all the processes crashed once more...
So I did a battery pull, left the phone for five mins and rebooted. All was well for a while, enabled Wifi, phone seemed happy.
Had to reboot a short while ago, after recieiving a phonecall and text.... grrr... anyone have any suggestions?

I had problem with process restarting. Adw launcher process I downloaded Go Launcher ex I have no problems now.
Sent from my HTC Wildfire using Tapatalk

[Q] Suddenly lost 3G on my Arc S (solved)

Yesterday I flashed CM 7.2.0 FXP109 on my Xperia Arc S.
3G worked perfectly.
Later I installed AdFree, and set my phone on the table. I do not remember if I rebooted it first. About an hour later when I picked up the phone again, I had no 3G signal. Still nothing today. Tried re-flashing CM7.2 FXP109, whilst first wiping data/cache/dalvik. Still nothing.
Tried to put it into airplane mode, waiting 10 seconds and turning it back off, checked all the settings (and the APN settings are set the way they should).
Also, after having wiped the phone data and cache and re-flashing, somehow USB Debugging and Unknown Sources are still turned on. Shouldn't that reset?
Either way, something is wrong and I'm at a loss. I have no idea what to do, and I just bought the phone yesterday. Before that I had an X8 with GingerDX, so it's not my first time installing a bootloader, and I haven't had these problems on my old phone.
Any help would be greatly appreciated!
EDIT:
I found a (possible) solution, at least it seemed to have worked for me.
I flashed a different kernel (and thus got a different version of CWM), formatted, wiped cache/dalvik cache and flashed back to the kernel needed for FXP109. Then I installed FXP109 CM7.2 and GAPPS again. Problem solved.
My guess is that for some reason, I had to flash to a different kernel and back to solve it.
Cheers!
-Zareph

(A Type of) Random Reboot Problem Solved?

Short version:
Use CWM or TWRP to (1) format sdcard, (2) erase dalvik cache, (3) erase cache and (4) factory reset. This seems to resolve at least one source of random reboots. If installing a new ROM, do that first and then followed by the four steps, then boot into the new ROM. Step (1) may be the important one (in which case it might, in principle, be possible to solve the problem while saving userdata), but I don't know.
UPDATE: It was working fine and I had to spoil it all by installing MIUI, just for kicks. Now, the old problem is back and the solution above doesn't seem to work. Looks like this is not a completely reliable solution...
* * * * *
Long version:
My wife's GNex was in a very bad way. It is entirely stable in Android 4.0.2. But if either upgraded or flashed to anything else, will randomly reboot. Actually, it's not even that random--it will reboot on its own within a couple of minutes of idle with the screen off. I tried all sorts of things--flashed different ROMs, radios, etc.--factory reset multiple times. Googling turns up lots of chatter about random reboots but little by way of viable solution. I figured that the problem may be hardware related. But all Samsung's servicing did for me is to return the unit to 4.0.2. At that time, 4.0.4 was just released and the local servicing centre hadn't even received their copy of the ROM (for yakjuwx). In the end, I 'solved' the problem by rooting and disabling the OTA update notification. (My wife wasn't bothered by the fact that she wasn't running the latest Android version. And the phone works fine in 4.0.2 otherwise.) Work and life caught up and I didn't think much of the matter after that.
That was about a year ago.
Recently, I migrated my wife to a brand new GNex, and took the opportunity to try my hand at solving the problem again. I flashed the latest 4.3 ROM, the latest stable CM10.1, Paranoidandroid, etc. But no matter what I tried, somehow, the phone is stable only with Android 4.0.2 (ICL53F). A chance find online mentioned something about data corruption on the sdcard as a source of problem, and that the usual factory reset doesn't actually reformat the sdcard (it only marks it as empty). Putting 1 and 1 together, I used CWM to do the things listed above (see "short version") and now, the phone is running stock 4.3 (JWR66V), stable CM10.1 and Paranoidandroid without random reboots so far. So now, I am a happy camper, though with one extra, fully functional white GNex.
Footnote: If you don't understand what I said in the short version, it's best you don't try doing anything yourself without first reading up on fastboot commands. This is one place to start. I am not responsible for anyone bricking their device fooling around.
Thanks for reading.

Update to my adventure.
Just about resigned to the fact that the phone is back to its old ways. The old tricks no longer work. What happened next?
1. Left off for more than a day (I gave up).
2. Installed AOSPA PARANOIDANDROID 3.96--using CWM, installed ROM, GApps, wipe dalvik, wipe cache, format sdcard.
Weirdly, the phone now seems fine. It hasn't rebooted by itself after 30+min in sleep. The old problem was that it will invariably reboot by itself in within 2 minutes from screen off so even if there are other problems, the old one is not there anyway.
Something in the steps above seems to have made a difference.
Still monitoring.

[Q] Can't turn wifi on. Tried with 5.1 and 4.4.4

I should mention that this phone is not mine and it was brought to me to fix. It could not get past the samsung bootup animation screen.
So I installed TWRP 2.8.6.0 and wiped everything. Then the first rom I flashed was [ROM][5.1.1][AOSPA] ParanoidAndroid 5.1 (5/21/2015) Then flashed gapps 5-22-15 from euroskank/banks. I wiped dalvik & cache (Is this necessary?) and rebooted.
The intro screen did not let me skip the wifi connecting part (I thought it was a bug in that version) and it told me to turn on wi-fi to connect.
So I tried the same thing with the version before that and it let me skip. After that I managed to turn it on once? But it the phone crashed and soft rebooted.
I tried other 5.1 roms and the wifi doesn't work still. It doesn't let me turn it on. Same with 4.4.4 with cm11. Also, the Wi-Fi MAC address says unavailable. Don't think that's supposed to happen?
Does anyone have a fix?
Edit: I took out the SIM card to see if that did anything. Then all of a sudden the grayed out On button turned blue and wifi networks appeared... But I couldn't do anything else since it made me restart. It stopped working after a reboot :/ Tried it several more times and couldn't get it to do the same thing..

stevenx37 said:
I should mention that this phone is not mine and it was brought to me to fix. It could not get past the samsung bootup animation screen.
So I installed TWRP 2.8.6.0 and wiped everything. Then the first rom I flashed was [ROM][5.1.1][AOSPA] ParanoidAndroid 5.1 (5/21/2015) Then flashed gapps 5-22-15 from euroskank/banks. I wiped dalvik & cache (Is this necessary?) and rebooted.
The intro screen did not let me skip the wifi connecting part (I thought it was a bug in that version) and it told me to turn on wi-fi to connect.
So I tried the same thing with the version before that and it let me skip. After that I managed to turn it on once? But it the phone crashed and soft rebooted.
I tried other 5.1 roms and the wifi doesn't work still. It doesn't let me turn it on. Same with 4.4.4 with cm11. Also, the Wi-Fi MAC address says unavailable. Don't think that's supposed to happen?
Does anyone have a fix?
Edit: I took out the SIM card to see if that did anything. Then all of a sudden the grayed out On button turned blue and wifi networks appeared... But I couldn't do anything else since it made me restart. It stopped working after a reboot :/ Tried it several more times and couldn't get it to do the same thing..
Click to expand...
Click to collapse
Hope you had read the posts, it should had said the Rom is not "stable"
If your friend are going use their phone for daily driver, then I recommend you not have the 5.1 Roms for now because it's not really suitable for that right now.....
I'm not sure the CM11 you have flashed is unoffical or is offical. Offical onces are still work in progress and have most of the things broke (I think)
Here is a Kitkat Rom for SGH-T989
If your friend really wanted to have a Lollipop running on his/her phone, then I will recommend this one. Make sure you read the instruction CAREFULLY if you do wanted to install this one since it's a bit complicated with it's "virtual partition"
Or, if you wanted it to be just stock. Odin it back to normal, here is a instruction (with video too).
This is all the possible way to fix your friend's phone that I can think of, if you have encounter any error or have anymore question, feel free to reply :fingers-crossed::good::highfive:
P.S: yes, wiping dalvik & cache is a way to prevent any error caused by another old Rom if you decided to flash a new one. It's a good way to prevent error during Rom flash process

Thanks! I'll try the 4.4.4 rom you sent me. I'll post an update when I get to it.
Uh and about the 5.1 you linked. For the virtual repartition part in his post, I couldn't open the phone's internal storage on the computer after formatting it to ext4. So I'm confused about that step.

stevenx37 said:
Thanks! I'll try the 4.4.4 rom you sent me. I'll post an update when I get to it.
Uh and about the 5.1 you linked. For the virtual repartition part in his post, I couldn't open the phone's internal storage on the computer after formatting it to ext4. So I'm confused about that step.
Click to expand...
Click to collapse
For the virtual partition, it's best for you to have it on the External SD card. Since TWRP transporting file to Internal Storage after that seems bugged (not working)

Galaxy Note 10.1 SM-P600 Reboot Loop

Hi All,
Having some issues with my Galaxy Note 10.1 which I've had for quite a while now. It's rooted but with Android 5.0 stock rom and a custom kernel.
Just now (like 20mins ago) I tried to enable Adblock plus app, the app said it can't automatically change the settings - even though SuperSU was installed and had no issues with it previously. So like all things thought I'd give it a reboot that ought to clear it out. That didn't work, so tried clearing cache (Dalvik/ART/Cache), Still no joy.
I'm a s/w engineer, but not and android/bootloader expert, so I've tried to grab the dmesg and boot logs which I've attached, I've got some stuff on the internal SD (app data) which I'd like to keep, hence I'm not going for the full wipe.
Please take a look at the logs and see if you can determine how to fix this issue, my initial thoughts were there are some issues with the flash storage (bad sectors/partition table?), if I could grab the image and dd the image again I'd be OK - but I don't know much about about android boot loader/kernel etc so can't say.

Ok it has been fixed by wiping data - but I've lost my data and installed apps!
Is there anyway to find out which file/app is causing the boot loop so I can restore data, delete the offending file?

Well, I shall give a bump to this topic, with a little more info. Though probably not really useful.
First I had stock 5.1.1 deodex pre root etc ROM that, after I tried to insert a nano sim card (mine is a 601 3G model) that got stuck, it entered on a bootloop, I had to open it, take the sim card out, and it was still on a boot loop. Tried to install another image, still bootloop, tried to reinstall the original one I had, still bootloop, wiped data, worked fine.
Then almost 2 weeks later, everything worked fine, went to watch a video, the sound was mute, tried to turn it on but everything looked fine, decided to restart because it would probably fix the problem. Got a bootloop. Wiped the data, everything was fine again.
Now, a little more than 2 weeks later, seems like the wifi is not working, thought all my other devices are, guess it's the same problem, decided to restart it, and bootloop again. I'm currently trying to update my TWRP, and gonna try a different ROM, and wait to see if something like that happens, until then, I wonder what could be happening... I remembered an Asus Device that I had that had different firmware versions for 4.4 and 4.1, so if I tried to flash a 4.4 on a 4.1 firmware it wouldn't work, and for downgrade, the same problem happened, and wondered if Samsung has some difference between versions 4 and 5.

ssj4maiko Let me know if you find a more stable rom - I went back to pretty much stock, but with root as I wanted to use all the Samsung apps, but this constant random bootloops are annoying!