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

Root GPartition - Well stumped

SD Card: I looked at it briefly before I formatted it via Windows and it was EXT3, but then after I formatted it the partition's status was "Unknown" although the size - 488Mb - was the same.

Hmmm.... Well.... The phone started up ok yesterday, I flashed GV 1.6 and Eviollet 1.3 kernel, and did a Titanium reinstall. All good. Last night I shut the phone down to recharge it fully.

I turned it on this morning, and..... Stuck on the Joker boot screen. So I pulled the battery and restarted. Stuck on the Joker book screen again. I pulled thew battery 4 times in the end. On the fifth I booted to recovery, remembered that I hadn't taken a Nandroid backup yesterday, sighed, and reflashed GV 1.6. When I restarted the phone started ok and everything was as it was last night (I then did a Nandroid backup!).

I get the impression something is still up here. It can't be right that I still get boot-up freezing after sorting out the SD card can it? It appears that the common denominator here is shutting down to recharge overnight - problems always happen after that. Now I know some will undoubtedly say "well don't shut down then" but that's not the point. The phone shouldn't be acting like this. It should be starting correctly every time I turn it on; I don't want to have to be pulling batteries and running Nand restores or ROM reflashes every time I turn the bloody thing on. I'm also concerned that this is a symptom of a larger and yet-to-become-apparent problem.

Any other pointers guys? Really sorry about all this, I really appreciate all the info / advice!
 
Can you tell me what options used exactly and what you are restoring via titanium please?

Could you check if this issue persists with no data please? i.e do a wipe and reboot it a few times? Then do a restore and reboot it a few times?

Are you set up to use adb on your PC? A logcat might be handy (although I am not very good at readign them).
 
Sure thing.

After I did the reformat and re-EXT3 in GP, I restarted the phone and it rebooted normally and quickly, kicking off Defrost 6 (as the current ROM). I then turned it off and plugged it in for the night.

Yesterday morning I restarted the phone to make sure everything was ok, then rebooted in Recovery, did a data wipe and factory reset, then flashed GV 1.6 and Eviollet. The phone restarted nice and quickly. I then ran through the initial set-up (Google account details, etc) and installed Terminal from Ti (> Run restore missing apps with data, and then deselected everything except for Terminal), initiated DarkTremor, and then restarted. There was a nervy moment when the phone seemed to take a while on the Joker screen but that could just have been me being jumpy! The phone then booted up fine, I checked the SD memory and it was as it should be, so I started Ti restore. Again, I chose Restore missing apps with data.

Just so I understand, I'll now do the following:

1. Boot to recovery, do a full factory reset (wipe) and format data
2. Restart
3. Shut down
4. Restart
(a couple of times)
5. Restore missing apps WITHOUT DATA
6. Shut down
7. Restart
(a couple of times)

That correct? If so, that's all cool. I'll try and do this at lunchtime, but more likely tonight. I'll be interested to see what happens here too. I suspect a subsequent test will be what happens once I've shut down and recharged over night as that's when the problems appear to be most prevelant... We'll see, eh?!?

ADB: Don't use it habitually but I'm sure I could get to grips with it fairly quickly. How do I go about grabbing a logcat?
 
Also try flashing GV over DF without a wipe.. I did this when I first moved and had no problems.
 
To run a logcat

Download this:

http://db.tt/DPOZOiC

And follow these instructions to set up:

http://db.tt/Pw37gip

**Thanks to rastaman for these**

Then, open command prompt. START > Run "cmd" [OK]

Connect phone whilst off via USB (whilst in state where you have this problem)...

Turn on phone.

In CMD, type "adb logcat" [Enter]
 
depends what the missing apps are, if some of those missing apps are system apps then it could be problematic afaik
cannot be certain though
 
Rastaman-FB said:
depends what the missing apps are, if some of those missing apps are system apps then it could be problematic afaik
cannot be certain though
Click to expand...


Yes definitely. I went through all my titanium backups and deleted all sense stuff to avoid this. Wish you could set app location to only /data/app.

Seeing quite a few issues caused by titanium restores on GV right now in teh XDA thread and here. I'm working on 3 right now ;)
 
Titanium tries to separate those two: 1) Restore Missing Apps 2) Restore Missing apps + system data.
I've tried the 2nd once and had problems. Since then I do only the 1st. Then again, there also you need to go through the list and exclude anything that you can suspect causing issues between different ROMs.
 
Usta said:
Titanium tries to separate those two: 1) Restore Missing Apps 2) Restore Missing apps + system data.
I've tried the 2nd once and had problems. Since then I do only the 1st. Then again, there also you need to go through the list and exclude anything that you can suspect causing issues between different ROMs.
Click to expand...


Well its:

1) Restore missing apps with data
2) restore missing apps + system data

Yes, its the first one. "With"
 
Yep.
And with the first one you get to select: App+Data, App only, Data Only.
I just do App+Data.
 
Indeed. But like you (and I) said, you have to go through the list first before selecting batch and weed out anything from roms you will not be using again.
 
Hmmm, sounds like I need to go through my list and do some weeding. Or perhaps that should be deforestation... May help...
 
I thought you would be and even if not, I wouldnt think it would cause these problems. Just since we're making a checklist ;)
 
Right. News. (You're starting to get bored with this, aren't you.)

In order to maintain the "control test", I turned my phone off last night - it was working fine - and recharged it overnight. This morning..

- Turned it on
- Froze on Joker screen
- Pulled the battery and turned it on again
- Froze on Joker screen
- Pulled the battery and restarted in recovery
- Wiped data / Factory reset, then restarted
- Froze on Joker screen
- Pulled the battery and turned it on again
- Froze on Joker screen
- Pulled the battery and restarted in recovery
- Wiped cache partition, wiped data / factory reset, then restarted
- Froze on Joker screen
- Pulled the battery and restarted in recovery
- Ran nandroid recovery, recovering the image I took yesterday morning after setting up GV
- Started ok.

I then shut my phone down on the way to work, and restarted it, and it started it ok. There's somethign funny here. The constant is the phone being shut down for an extended period and being recharged during that period. To be honest I haven't tried truning it off and leaving it overnight without charging it, that will be my test tonight. FYI, I'm using the charger that came with the phone, not some eBay / third party affair.
 
Yes turn it off without charge that would be interesteing.

Ive found recently that my phone if started whilst connected, doesnt get a signal (no service) until I pull out the USB cable.

This isnt everytime, but sometimes its like being connected causes it to not start up properly.
 
I want to make ext3/4 partition to my 8GB microSD card using Ububtu live CD. Will it be any issue?
If I use a ext3/ext4 partition along with FAT32 in my microSD card in my Desire (Froyo), will there be any conflict? or work smoothly.
If a microSD card (with ext3 and FAT32 both partition) is used in Froyo, shall I be able to move the application to ext3/4 partition? or Moving App in Froyo always go to FAT32 partition?

For Gingervillain what the supported and recommended maximum size of ext3/ext4 partition?
 
Sorry about the delay in responding, work got a bit hectic today. Anyway.... So I charged my phone up yesterday evening to make sure I had enough juice for today, then unplugged it and shut it down to see what would happen if I left it off for a long period of time but not charging. I turned the phone on this morning and it started first time. Odd.

I'm now going to revert back to the original routing, I'll keep using it as usual tonight and then shut it down and recharge overnight. I'll start it tomorrow without unplugging it (as usual) and if I have bootup problems then I'll know it's something to do with the charging / booting up plugged in process. It has to be. On this basis, tomorrow night I'll charge overnight again but on Saturday I'll unplug before booting up to see if that makes a difference.

Don't you just love scientific experiments?!?
 
Hmmm.... Maybe. The phone strted first time again yesterday morning and I thought I'd got it sorted. I then turned to off last night, forgot to do something, turned it back on again almost immediately and.... nothing. Back to square one. Frustrated, I plugged it in and left it to charge. I turned the phone on this morning (unplugging it first) and still nowt. I tried data wipe / factory reset, wipe of cache, wipe of cache then wipe data / factory reset... Nothing. In the end I had to Nand recover again (from an image I took on Wednesday, which also annoyed me!).

So I'm still stumped. Just dunno guys. I REALLY can't be arsed to Ti backup and NAND backup EVERY DAY just in case I need it, the phone shouldn't be working like this and I shouldn't have to do this. Grrr.

Rastaman - If I flash a non-rooted RUU ROM, won't I lose rooting on my phone?
 
You must log in or register to reply here.
Back
Top Bottom