[Q] Delayed Bootloops after setting up new ROMs - Desire Q&A, Help & Troubleshooting

Hi guys,
I could not find the exact same problem anywhere else, so here we go:
I have been running on [STOPPED][ROM ICS 15 Jul] slim rom for Desire [based on Sandvold .15 & K900 build 40] successfully for some months with only slight problems. One of those being an occasional (hot) reboot out of the blue. Recently, without any particular trigger, I encountered a bootloop on one such occasion. When I removed the SD card, I was able to boot, but obviously had no data and apps did not start, so I had to reset some things.
Since then, I made a lot of full wipes in 4ext recovery, formatted and re-partitioned my SD card, even tried out another SD card, and installed several different ICS ROMs, e.g. Sandvold or AOKP. The systems always work in the beginning - I can boot and set up my stuff. At some point afterwards, I get into a bootloop again on the next reboot I make. I can always enter recovery without problems, though.
[edit: Additionally, removing the SD card now does not help anymore: bootloops seem definite]
I have not been able to completely narrow down a possible trigger. However, I noticed that without setting up my Google Account, I seem to be able to keep the phone running & booting for days. If I do enter google data, I at some point get the bootloop, whether I check the "sync/save my phone via google" or not (though not immediately after entering the account - it seems to take some time - some corrupt data to be synched perhaps?). Obviously, I am not keen on starting a new google account and losing all my apps and data, and running the phone without google at all is, let's just say, limited. I do not really see how a bootloop can be caused by some data that is coming in via google, but it comes up with an annoying certainty.
One last thing: the 4ext app currently pops up a news window regarding bootloops on some users' devices, but their recommended solution is to check in superuser whether the su binary is up-to-date. Unfortunately, it seems to be (3.1.1).
So if anybody out there has seen something like this or some suggestions as to narrow down the problem, I would much appreciate it!
Thanks in advance and best wishes from Germany!

This might be related to the google play store updating to the latest version. It is known to cause a boot loop on every restart for some ICS ROMs. Try this if it helps: http://forum.xda-developers.com/show...ostcount=16742

Thanks so much for pointing me in this direction!
Although your link seems to be broken, it gave me the correct idea on what to search for.
I followed steps that are discussed in http://forum.xda-developers.com/showthread.php?t=1944766 as well as http://forum.xda-developers.com/showthread.php?t=1355660&page=1661 and seem to be finally bootloop-free again even after setting up all my stuff!
For people who might need to follow the procedure, I did the following things:
Full Wipe
Install Sandvold ROM
Download modded Play Store APK file called: Vending-3.8.15.noupdate.norestrictions
Rename APK to "Vending.apk" and push to sdcard
Mount data, system, sdcard in Recovery
Enter "adb shell"
cd /system/app
rm Vending.apk
cd /data/app (might also be /data/data or something)
rm -r com.android.vending
rm -r com.android.vending.updater
cp /sdcard/Vending.apk /system/app/
(Dalvik wipe if ROM is not a fresh install)
Boot Up

Glad it worked for you. I followed almost the same steps myself. Unfortunately this happened to me while I was travelling and I was stranded with a brick for a week.
P.S: No idea why the link got eaten up...

Related

[Q] Major confusing Google-apps problem

Have run into a major problem i think, need some of you experts to help me out on this one...all my ideas have failed.
I have been using cmod 6.0.1 for a while now, remember I had some problems to add gapps to that rom, and now the problem is reversed...
No matter how much i whipe/clean/clear I can't get rid of market, facebook, twitter, car home and probably some other app i don't remember right out of my head.
I have entered clockwork, I made a factory reset, cleared cache, and then the part that got my attention. When I press the trackball on option "wipe dalvik cache" (the title, before i press yes) i get this message:
E:Can't mount /dev/block/mmcblk0p2
(File exists)
Although this it says Dalvik has been cleared successfully when I have pressed OK to clear.
I recon this might be the problem, but I'm far from certain, I'm still a noob in the progress of learning.
After all this, I have managed to successfully flash cmod 6.1.1, which I at first thought he added some gapps despite Googles opinion about that. Did not fins _any_ parts of those gapps in the rom-package.
Went forward to flash cmod 6.0.1 which I KNOW don't contain there apps (cus I had big problems adding them on that rom in the beginning).
Now I ask you far more learned guys, what can be wrong, and how could I solve this? All i can think of, is that IF they somehow managed to get their way onto a recovery-partition of the phone, but i really don't know...just wild guessing.
On the even more weird side, those gapps is installed onto the regular path "root/system/apps"
I really cant find anything that could put them there, nor find any reference to those .apk-files to even install them in the first place.
Running a GSM Desire.
EDIT: Have read a bit more about the mmcblk0p2-thing, and wow, i have no idea of how to get myself out of that. Most solutions seems to be trough ADB (if im even on the right track?), and I were not at all familiar with linux of any kind before this phone. I am a quick learner, but that doesn't solve what I have yet to learn.
I somehow managed to clear out hose apps, but the thing with dalvik remains (the "file already exists"-thing).
Now im just looking for someone who can tell what could have been the problem, and if the dalvik-thing is normal behavior? I dont have partioned anything nor running any app2sd other than stock.
Could that be it, that theres no extra dalvik-cache on a user-created partition?
...I dunno, just pulling strings here right now.
I believe it's just a message that it can't find a second partition on your SD card, which makes sense since you haven't partitioned it. Shouldn't make any difference.

Marvel keep's bugging all the time...

Hello guy's,
I'm new to the rooting business, and i've unlocked the bootloader and installed CWM for my Wildfire S(Marvel),
I have a quite few problems(bugs), in these few weeks of using it:
1. SU binary wont work besides the 2.3.1-ef version, and i've tried updating it through SuperUser, and flashing the binary through the CWM.
After the restart, all aps lose root access becoming unusable, not accepting or prompting for privileges. I've tried multiple ROM's and the SU Update fixer from the market...nothing has worked...
2. CWM(although re-flashed) wont backup my data(gets stuck at: error while making a backup image of /sd-ext). I am using an ext2 1gb 2nd partition for my apps.
3. The phone freezes at random(usually when some app is opened). I am using Stock ROM currently, flashed with Dust 9.0 and updated adreno 200 libs. I've scored 2000 on the antutu benchmark(without any bugs whatsoever). Im using smartassv2/noop on 400mhz/768mhz.
4. The internal storage of the phone(/user) jumps from 100mb to 70mb(even to 20mb), even if there are no apps installed, and the current apps are linked to sd-ext via Link2SD.
5.The phone keeps syncing at random, and lasts until i manually cancel it. It really isnt doing anything, just sits there...and when i manually sync it, it doesn't take as that long to finish...
Hope someone can tell my why my phone if full of gremlin's...
EDIT: Im testing CM10 and none of these bugs have appeared(except for CWM theoretically)
PetarVlad said:
Hello guy's,
I'm new to the rooting business, and i've unlocked the bootloader and installed CWM for my Wildfire S(Marvel),
I have a quite few problems(bugs), in these few weeks of using it:
1. SU binary wont work besides the 2.3.1-ef version, and i've tried updating it through SuperUser, and flashing the binary through the CWM.
After the restart, all aps lose root access becoming unusable, not accepting or prompting for privileges. I've tried multiple ROM's and the SU Update fixer from the market...nothing has worked...
2. CWM(although re-flashed) wont backup my data(gets stuck at: error while making a backup image of /sd-ext). I am using an ext2 1gb 2nd partition for my apps.
3. The phone freezes at random(usually when some app is opened). I am using Stock ROM currently, flashed with Dust 9.0 and updated adreno 200 libs. I've scored 2000 on the antutu benchmark(without any bugs whatsoever). Im using smartassv2/noop on 400mhz/768mhz.
4. The internal storage of the phone(/user) jumps from 100mb to 70mb(even to 20mb), even if there are no apps installed, and the current apps are linked to sd-ext via Link2SD.
5.The phone keeps syncing at random, and lasts until i manually cancel it. It really isnt doing anything, just sits there...and when i manually sync it, it doesn't take as that long to finish...
Hope someone can tell my why my phone if full of gremlin's...
EDIT: Im testing CM10 and none of these bugs have appeared(except for CWM theoretically)
Click to expand...
Click to collapse
1. Try SuperSU, uninstall superuser, install supersu from market and update. I never had such problem.
2. A pretty common problem. Maybe ext2 is to be blamed? I use ext4 and it worked for me..
3. Dust kernel had a problem of random freezes. try cake kernel, Set minimum frequency to 245 Mhz for less battery drain.
4. Link2sd doesn't link data files. Also mostly the cache is stored in internal memory. Clear cache and reboot. When rebooting it'll link library files which can free up some space.
5. There are many things that need syncing in our phone. For example: calendar, contacts, whats app, bla bla. Don't get bothered by syncing sign. Its just doing its job. I examined the data usage when it was sycing and its not more than 5 kb/ps. so I guess it is meant to be slow to allow free browsing and usage of data for other apps.
sukhjit321 said:
1. Try SuperSU, uninstall superuser, install supersu from market and update. I never had such problem.
2. A pretty common problem. Maybe ext2 is to be blamed? I use ext4 and it worked for me..
3. Dust kernel had a problem of random freezes. try cake kernel, Set minimum frequency to 245 Mhz for less battery drain.
4. Link2sd doesn't link data files. Also mostly the cache is stored in internal memory. Clear cache and reboot. When rebooting it'll link library files which can free up some space.
5. There are many things that need syncing in our phone. For example: calendar, contacts, whats app, bla bla. Don't get bothered by syncing sign. Its just doing its job. I examined the data usage when it was sycing and its not more than 5 kb/ps. so I guess it is meant to be slow to allow free browsing and usage of data for other apps.
Click to expand...
Click to collapse
Thanks for the reply
1. SuperSU starts looping while updating the su binary, especially after superuser tries to update it. If its clean then it gives me this error: "there is no su binary installed, and supersu cannot install it. this is a problem!"
2. It has been backuping perfectly until yesterday...i just cant see why this could be a problem all so sudden...ill try to experiment with ext4 as soon as im finished testing CM10
3. I'll try Cake kernel then
4. Really weird with those jumps, sometime its jumps from 77 to 100mb and freezes...
5. I understand, but its really weird that there is no animated sync icon in any tasks it should sync...everything is blank yet it still standing
EDIT:
Did a full format, reflashed adreno 200 libs and Cake kernel...no dice...stuck on a reboot cycle at random times
Reformatted and repartitioned the sdcard and sd-ext to see weather the backup could work
Reflashed CWM
I'll update as soon as i get a working ROM
EDIT2: None of the custom ROM's work...freezes the phone in the middle of the setup or begins a reboot loop(although i wiped it)
Stock rom boots, but SuperUser or SuperSU dont insert the su binary, thus acting like its never been rooted at all...
It seems that my phone wont simply become normally rooted at all and there is no help
Does anyone have the original recovery.img?
The one with the memory optimizer from 2.26 ruu?
I would like to revert my phone back to stock since it wont cooperate...
(sry for double posting)
EDIT: Found it in the RUU's zip(i would delete my post but i cant)

GNexus Can not access "sdcard" or "sdcard0" - AOKP 4.2.1

Hello!
Background:
I flashed aokp_maguro_jb-mr1_build-3 yesterday and everything worked fine until I wanted to change kernel to a franco one. I already had the fraco.kernel updater free installed so I figured I'd just download and flash it automaticly. though somehow it downloaded and flashed an older version (milestone4 I think) so after I rebooted it got stuck at "Google".
I tried rebooting a few times and changed to a kernel.zip I had on the phone from earlier (not the one that came with the original aokp) and the phone got stuck at "starting apps" after the upgrading android sequence.
Anyhow I then read up on some stuff on how to push a proper kernel and pushed the newest nightly franco(r364) through adb.
The actual problem:
So I now had a phone that booted properly again! Only problem was that somewhere along the line something happened and now non of my apps have access to the storage..
If I use my phone explorer total commander I can access the file system root but under /storage there's only a file that takes 0B that's called "sdcard0". All the stuff I had on my sdcard is still under /data/media/0/. There's also the /data/media/legacy and /data/media/obb.
Something to note is that I can still use clockwork recovery as normal and access the sdcard through /sdcard/0/.
What I'm wondering now is what my next course of action should be. I read that some people with similar problems didn't get it fixed through a simple wipe/reflash so I figured I'd ask the pros here first before I do something more stupid..
If something is unclear, feel free to ask and I'll try to rephrase it or explain it further.
Thank you for your time!
Update: Grew tired and factoryreset/wipe + dalvik wipe and reflash seems to have sorted the issue. rebooted a few times and changed kernel to the same franco nightly as before and I still don't get the problem again.
although my stuff seems to be mirrored to a few places now including in storage where I'm used to be seeing the stuff (storage/0) but also under legacy and in root where there's a new folder called "sdcard". But I'm guessing this is normal with 4.2.

[Q] Getting Gapps on [JUNE 17][4.2.2] PARANOIDANDROID v3.60 | HALO

A first post here, please be gentle with me, and huge thanks to everyone who has made posting here unnecessary until now.
After a long time using CynogenMod 7.1 on my Desire, when I came to switching SIMs on it, I decided to look for a new ROM too because I was having a problem with shortage of app space and I was missing a few features I have become used to on JellyBean.
A look at the options found the one in the title by WoH (development forum link). It separates out the ROM and the Google Apps. I can install the ROM, and I like it a lot. I can't get the Google Apps to install.
Tried: flashing the zip file at http://woh-roms.weebly.com/gapps.html via the recovery menu, and installing a2sd. It has the right MD5 and appears to go OK, but the apps don't appear when the phone is rebooted, or appear in the list of things moved by a2sd. I have made repeated attempts, both with wiping user data before and afterwards, and doing it before rebooting after installing the ROM and after an initial boot with it, all without success.
Tried: reading the instructions there. However I don't have adb installed and because I don't have Google Play, I can't install a file manager that unzips files (the one in the ROM doesn't appear to - no unzip option is given).
Tried: installing the ROM mentioned in the development subforum thread by timvdlinde which does have Google Play. That works, but I am not so keen on the ROM itself. This may be incredibly shallow, but I liked WoH's use of the Nexus boot animation, and the timvdlinde ROM has the Nova launcher which I am not interested in.
The phone: an unlocked, rooted, AMOLED GSM Desire. The recovery is the Clockworkmod ROM Manager one. I don't remember ever changing the hboot settings. There is a sizeable ext4 partition on the SD card and it is being used by a2sd.
lovingboth said:
A first post here, please be gentle with me, and huge thanks to everyone who has made posting here unnecessary until now.
After a long time using CynogenMod 7.1 on my Desire, when I came to switching SIMs on it, I decided to look for a new ROM too because I was having a problem with shortage of app space and I was missing a few features I have become used to on JellyBean.
A look at the options found the one in the title by WoH (development forum link). It separates out the ROM and the Google Apps. I can install the ROM, and I like it a lot. I can't get the Google Apps to install.
Tried: flashing the zip file at http://woh-roms.weebly.com/gapps.html via the recovery menu, and installing a2sd. It has the right MD5 and appears to go OK, but the apps don't appear when the phone is rebooted, or appear in the list of things moved by a2sd. I have made repeated attempts, both with wiping user data before and afterwards, and doing it before rebooting after installing the ROM and after an initial boot with it, all without success.
Tried: reading the instructions there. However I don't have adb installed and because I don't have Google Play, I can't install a file manager that unzips files (the one in the ROM doesn't appear to - no unzip option is given).
Tried: installing the ROM mentioned in the development subforum thread by timvdlinde which does have Google Play. That works, but I am not so keen on the ROM itself. This may be incredibly shallow, but I liked WoH's use of the Nexus boot animation, and the timvdlinde ROM has the Nova launcher which I am not interested in.
The phone: an unlocked, rooted, AMOLED GSM Desire. The recovery is the Clockworkmod ROM Manager one. I don't remember ever changing the hboot settings. There is a sizeable ext4 partition on the SD card and it is being used by a2sd.
Click to expand...
Click to collapse
Repartition your sd-card by using the partitioning guide in my sig.
onknope what
abaaaabbbb63 said:
Repartition your sd-card by using the partitioning guide in my sig.
Click to expand...
Click to collapse
Thanks, but I did that before starting this. I used gparted, ending up with a large FAT32 partition, followed by a smaller ext4 and finally a small swap.
lovingboth said:
Thanks, but I did that before starting this. I used gparted, ending up with a large FAT32 partition, followed by a smaller ext4 and finally a small swap.
Click to expand...
Click to collapse
Theres no need for a swap partition. If you are using PA it will just act as a waste of space, since the rom doesnt utilize it in any way.
Try doing a full wipe and reflash the rom. Then flash these gapps. I can guarantee those work, as i use the same rom with those gapps and everything is fine. After flashing run the a2sd script through terminal.
chromium96 said:
Try doing a full wipe and reflash the rom. Then flash these gapps. I can guarantee those work, as i use the same rom with those gapps and everything is fine. After flashing run the a2sd script through terminal.
Click to expand...
Click to collapse
To quote Napoleon Wilson, you can't argue with a confident man even if that's the file I've been trying - same source, same MD5
OK, I'm about to give it another go.
(And apologies if you don't identify as a man!)
lovingboth said:
To quote Napoleon Wilson, you can't argue with a confident man even if that's the file I've been trying - same source, same MD5
OK, I'm about to give it another go.
(And apologies if you don't identify as a man!)
Click to expand...
Click to collapse
Lol, weird. Im on the same rom and used the same gapps. Everything worked fine.
chromium96 said:
Lol, weird. Im on the same rom and used the same gapps. Everything worked fine.
Click to expand...
Click to collapse
Not for me. I took some photos of the process, which I can put somewhere, but it was...
Repartition the SD card
Boot into recovery
Wipe data
Wipe cache
Install ROM.zip (using the one downloaded from the right place, no reported problems)
Install Gapps.zip (ditto)
Reboot
Notice that the Google apps aren't there
Do the su / mount / a2sd install anyway
Reboot (through saying yes to the third question)
Notice that the progress of the move to the ext4 partition says its moving 59 items, none of which are Google apps
Confirm that the Google apps still aren't there
I'm about to try again with another SD card on the basis of 'why not'
lovingboth said:
Not for me. I took some photos of the process, which I can put somewhere, but it was...
Repartition the SD card
Boot into recovery
Wipe data
Wipe cache
Install ROM.zip (using the one downloaded from the right place, no reported problems)
Install Gapps.zip (ditto)
Reboot
Notice that the Google apps aren't there
Do the su / mount / a2sd install anyway
Reboot (through saying yes to the third question)
Notice that the progress of the move to the ext4 partition says its moving 59 items, none of which are Google apps
Confirm that the Google apps still aren't there
I'm about to try again with another SD card on the basis of 'why not'
Click to expand...
Click to collapse
Go to system/app. Are the google apps installed? What permissions do they have?
abaaaabbbb63 said:
Go to system/app. Are the google apps installed? What permissions do they have?
Click to expand...
Click to collapse
Ah, no they're not.
About sixty are, owned by root, with rw (owner) and r (group and global) permissions.
I am being tempted to bite the bullet, install the ADK on something and try the adb method.
What about /sd-ext/gapps/system/app. Anything there?
chromium96 said:
What about /sd-ext/gapps/system/app. Anything there?
Click to expand...
Click to collapse
Yep, they are there, with what I presume are the right permissions: as above, owned by root, rw-r-r.
Doing some more nosing around, and looking at the alternative installation instructions on woh-roms.weebly.com/gapps.html
$ adb shell ls /sd-ext/gapps/system
app etc framework lib usr
Click to expand...
Click to collapse
Yes, doing
ls /sd-ext/gapps/system
produces that.
# enable extgapps (quotes needed)
$ adb shell "echo x > /sd-ext/gapps/.extgapps"
# gapps dir should look like this (if .extgapps doesnt exist the init script wont run)
$ adb shell ls -a /sd-ext/gapps/
.extgapps system
Click to expand...
Click to collapse
Yes, doing
ls -a /sd-ext/gapps/
produces that.
.extgapps is a zero byte file, rather than one byte containing 'x' as there, but the root explorer instructions would produce a zero byte file, so presumably a) there's no touch command and b) it's the presence of the file that's important, not what it contains.
BUT...
... if I do
logcat -C
(after doing logcat -c, going oops, rebooting, and getting it right )
then the lines that are supposed to be there aren't.
I'll get the email working, email the output to myself and stick it in a pastebin or similar.
pastebin.com/Qtrps3A8 has the whole thing.
At the start, various links are possibly not set up:
I/run-parts( 75): ln: /system/etc/permissions/com.google.android.maps.xml: Out of memory
I/extgapps( 155): Created /system/etc/permissions/com.google.android.maps.xml
Click to expand...
Click to collapse
is just one example, then later
D/AlarmScheduler( 1300): No events found starting within 1 week.
I/Goo Parser( 839): GAPPS: No file, skipping item 0
I/Goo Parser( 839): GAPPS URL: http://goo.im/devs/paranoidandroid/roms/gapps/pa_gapps-full-4.2-20130702-signed.zip
I/AlarmReceiver( 839): gooVer: 3601
Click to expand...
Click to collapse
.. so what file is it looking for, and is this down to trying to do things with the card before it is ready?
What has changed:
The search 'app' has gone from the list - I can see from the logs that it is supposed to be replaced, but here it's just missing.
The browser is now very like Chrome... and I don't remember that being the case.

Help! Cannot write or delete from internal memory!

Here is my issue I cannot create folders or delete anything on the internal sdcard.
Background info: I just got this gs3 its on boost mobile. I am on NJ3 I used CF-auto-root method to get root. Everything went fine updated Supersu installed a bunch of apps including Titanium Backup and made backups of all apps on the phone. Everything finished fine. I have not deleted any apps yet nor have I installed a custom record very or any ROMs its still!l stock. I have a 64gb sdcard installed which is new and empty so I wanted to put my backups on it but could not. While looking for a fix I noticed that even the default INTERNAL sdcard had a red folder on top with "cannot write to this location" . so now I cannot use TB. It gives an "insufficient storage" message and fails
I then went to ES File Explorer and tried to make a folder on the internal card and could not, also tried to delete and could not !! I have Googled this problem and come up with a number of solutions but most are very old threads. Can anyone give me some help fixing this? The phone seems to otherwise work but I fear it will only get worse with time.
edit I can install apps though even now.
Oh I left out that I did recieve an update for Security policy update. Which I understand has something to do with SElinux. I also found a fix for what appears to be my problem related to this it is;
SU
restorecon -FR /data/media/0
I decided to try it but get a message that -F is invalid
syntax is restorecon (--nRrv-- )
From what I can google the version of restorecon I have on my phone does not include that switch!!! Just my luck, can anyone help me figure out if I can change the binary to an updated one so I can use this?
Well I am disappointed 45 views and not one reply, oh well.
I eventually bit the bullet and did a factory reset from the settings menu, it cleared up the issue and I still had root!! Google reinstalled all my apps and SuperSu disabled Knox for me. I also unchecked auto update for security updates so that Samsung does not send another one to me without my knowledge. also disabled autoupdate for Samsung apps.
know everything is golden again.

Categories

Resources