• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root Strange reboot problem

R

Ruswit

Newbie
Hi, a while back I rooted my desire and well frankly it was getting unbearably slow.

Today I finally knuckled down and found a nice AOSP oxygen mod ( [ROM] OxygenZM 1.2 [Complete] - xda-developers ) to be specific.

Now after doing a full wipe and freshly flashing the mod everything seems to be amazing, it runs super smooth and Im loving the ICS style UI.

HOWEVER , whenever I try and install a new app from the play store, the phone reboots, I just get the oxygen splash screen and it then goes to my unlock screen and the phone searches for signal again (like it had just booted up )


Any Ideas? This rom seems so perfect and id hate to lose it over such a small annoyance :(

I'm using an amon Ra recovery not the 4ext touch one, however that is only recommended not a requirement, surely that cant be the cause

thanks

Edit : I think previously had dark tremors (or some other form of data2sd) installed for my old rom, would this affect me now? ( I did a full wipe before installing the new rom) ( I have a partition on my sd card)

Edit: Just deleted and re partitioned (ext4 +fat32) my sd card , re flashed, still having the same problems!

Edit : Just flashed a different rom, this time a redux ([ROM] Redux2 ZM4.5 [Complete] (CM7r2 / Stock) - xda-developers) and the same problem is occurring , the ROM seems to work seamlessly in all other respects ! grrr
 
A full wipe plus a ROM flash should clear everything from a previous ROM. So this is really strange.

If the same thing is happening with 2 roms we should be looking for a common factor. That could be a software element present in both (but many people have used these), your partition, or...?

Does it happen when you start to download, or during the install? Can you restore apps from Titanium Backup? Is the partition being used (do you have an app that can show this, e.g. Titanium)? What did you use to partition the card?

Just trying to get the picture. If you are wondering why the partition has come up so often it's because installing an app will use that, whereas the ROM itself won't. But that's not a diagnosis (especially if you were using DarkTremor before).
 
I used "mini tool partition wizard" as recommended by XDA (SD card partitioning - XDA-Developers ) , I did this with my phone in recovery whilst in USB mode. It happens when the app is trying to install, the download performs fine (in the Redux rom the crash seems to happen a second or 2 later into the install process, but this might just be the rom being slightly slower).

Surely a full card wipe + format would leave it fresh and problem free!

I managed to successfully Nandroid restore to my old sense rom and reflashed the data2sd I had and that seems to work fine, downloaded some apps etc.

Could this just be because the nandroid saved some settings? Im really stuck for ideas here o_O
 
Actually we here do not recommend Minitool - GParted handles Linux file formats (ext) better. But if the partition works with a different ROM it's hard to see that as the cause of something as drastic as this (I assume your previous ROM is actually using the partition - DarkTremor a2sd for example sometimes has to be activated first).

What happens if you try to install an apk directly, rather than through the market? Have you been able to put any apps on other than those in the ROM?

If you do a full wipe before flashing a ROM there should be no hold-over from the previous one. The nandroid is just a set of images on the fat32 partition, so shouldn't affect this. Likewise I don't recall Amon Ra users having any problems with ext partitions.

If you are S-Off (or fancy editing a zip and reflashing) you could try the following test: remove the script 10app2sd (or similar name) from /system/etc/init.d then reboot. That would remove a2sd from one of these roms. If you could then install apps it would tell us that it's either the script or your partition. If not it would absolve the partition.
 
I know its supposedly better to partition running off a booted cd/usb, but the partition never had trouble before (apart from being slow but im not sure if that was the problem with the partition or the actual rom) .

Im sOn actually but I will try and deletethe a2sdscript, how do I do this? Trying to delete it from the zip file results in an error and if i unzip, then delete and rezip the rom wont flash properly. It says couldnt find the update file in my recovery

edit : right i tried a different mod : http://forum.xda-developers.com/showthread.php?t=1561843

This one let me install apps however my home button doesnt appear to be functional in this rom so i cant really use it...
 
Actually if you are S-On there may be an easier way to do it, if you have ADB set up (the "adb and fastboot faq" tells you how if you haven't but want to try). You can't remove system files when running Android if you are S-On, but should be able to do so using adb from recovery. Boot into recovery, connect to computer via usb, then try the command "adb devices" just to check it's working. Then if the script is where I said earlier (that was from memory, and I don't have it on my phone) something like "adb shell rm /system/etc/init.d/10apps2sd" should do the trick. If it complains about permissions, make that "adb shell sudo rm .....". "adb shell" just means "execute linux shell commands via the Android Debug Bridge", and "rm <filename>" is the linux delete command.

Otherwise, it's easiest to edit the zip on a computer, but I'm not a Windows user and can't remember what SUroot always recommended. You can do it on the phone with Astro - enter the zip, find the file, delete it, back out of the zip. Then go back in again to check it's actually gone! It's slow, but usually works.

Reflashing the ROM from that zip will then remove the script. If you have nothing on your ext then reflashing without a wipe would be fine, but if you're just doing this to investigate I guess a wipe (to ensure the ext is clear) would be better. Actually since you can't install apps using the ROMs that are having problems I guess you'd be doing this with your old ROM, so a wipe would be needed anyway - probably for the best!

I'd do it with a copy of the ROM zip, because if you'll want the script back at some point :)

This could all be a wild goose chase! I'm only thinking of the partition because that's something that the ROMs that are failing would have in common, and because it fails during the install (which is the point at which the partition would be used), but it may be something different. The fact that it works with a different ROM/script is a point against that theory, but it's just about imaginable that a different script might behave differently.

A bad partition could slow the phone (misaligned partitions are a common result when using Minitool), but usually only when writing to the partition. So a general slow-down is more likely to be the ROM. If it was actually using data2sd that might explain the slowness by itself.
 
Well after wiping that cron mond, I decided to try the oxygen one again, and bizarrely it now works! Honestly i can't think of anything that I did differently apart from having the cron mod before. The a2sd seems to be working fine but I'll keep a progress update.

Thanks for your help
 
Good result. I usually like to understand why, but between an explanation and no solution or solution but no explanation I'll always choose the second :)
 
Yeah, asides from my messages app crashing when i try and restore my backed up messages it all seems to be fine!
When I have an empty inbox it works great but when i back them up it just crashes... bizarre
 
Im using "sms backup and restore" an app which I found on the market, it makes and restores xml documents? It worked fine before, just on this root it seems having restored messages makes the messages app freeze and become inoperable. Is there another way?

It seems it could a problem of the messages app trying to refresh the addition of around 17,000 extra messages, seems i have to do each conversation individually, but if the problem persists!

Yeah it seems that scrolling up through the messages takes a VERY long time as it seems to freeze for a bit very regularly, however once ive scrolled to a certain point it lets me scroll back problem free...
 
There are other apps - SMS Backup+ backs up to your GMail account (can be automated, very reliable in my experience, bit slow restoring, not sure if MMS restore works properly yet as I basically don't use MMS), MyBackup can back up messages (though with some ROMs I had trouble with timestamps on restored messages), and the paid version of Titanium Backup now backs up messages to XML as well (have made backups, have not tried restoring one yet).

But it's odd because SMS Backup & Restore is one I've often heard recommended (though a market search reveals there are at least 4 apps of that name).
 
The one im using appears to be the highest rated one , i've never had any problems with it before, it only appears to be this one thread which is actually giving me any issues (which coincidentally is the largest one with the messages i want to keep the most GRR )

Is there anyway to divide a message thread file to reduce the size?

I found a previous backup of the thread, which has around half the number of messages, this should suffice for now, as long as I have the whole thread backed up and can then merge them (back them up without duplicates) when I finally fork out for a new phone. Hopefully an Lte s3 or One Xl when LTE finally hits the uk :P
 
You must log in or register to reply here.
Back
Top Bottom