Root Problem flashing Stock Froyo and suggestion for sense based ROM

[koshac]

Hello Everyone!

First of all again a thanks to SUroot and Hadron for their very helpful informations which brought me so far!

After S-OFFing my Desire I managed to flash Teppics stock Froyo ROM over mine, but now I realised slight problems.

After each boot I get a message that my sim has changed and when I choose it I only get a black screen which states "Choose carrier" at the top, the other thing is that I lost my Wifi-Connection. After the Upgrade it says "Obtaining IP-Adress" and cannot connect anymore, I also removed this connection and reconnect, but the problem persists!

I fear I have to do a complete wipe in order to get things run normally, so if I have to do a wipe I can possibly go for another ROM which should be sense based! Does anyone of you have a suggestions for a good ROM?

Thanks in advance for your help!

Regards,
Guido

 

[SUroot]

The idea of flashing this rom was to try and get root to run backup applications. Can you get to the app drawer at all? Did you have a file manager previously?

 

[koshac]

The idea of flashing this rom was to try and get root to run backup applications. Can you get to the app drawer at all? Did you have a file manager previously?

Yes, everything except the things I mentioned are working! I use Ghost Commander as a file manager!

I wanted to make a backup with My Backup Pro, but the root features are greyed out, so there is something missing!?

Regards,
Guido

 

[SUroot]

Try using titanium backup.. see if it works with root.

 

[koshac]

Try using titanium backup.. see if it works with root.

Managed to get MyBackup Pro to work, it required Busybox (what really is this?) and now I could backup everything with root access, so that's really good to start with a new ROM at last O It is time because I only have 10 MB of free internal storage left :-(

Regards,
Guido

Edit:

Due to the fact that my Desire became very much unresponsive with only 10 MB internal storage left I recovered a Nandroid Backup, but now I am stuck on the bootscreen with the HTC Logo! Did pull the battery and restored the Backup again, but problem persists :-/
Now I am lost again...

 

[koshac]

Managed to get MyBackup Pro to work, it required Busybox (what really is this?) and now I could backup everything with root access, so that's really good to start with a new ROM at last O It is time because I only have 10 MB of free internal storage left :-(

Regards,
Guido

Edit:

Due to the fact that my Desire became very much unresponsive with only 10 MB internal storage left I recovered a Nandroid Backup, but now I am stuck on the bootscreen with the HTC Logo! Did pull the battery and restored the Backup again, but problem persists :-/
Now I am lost again...

Meanwhile I have managed to flash a prerooted stock Gingerbread ROM with A2SD+ which works very well and my storage problems are gone at last

I would really like to test out other custom ROMs, but after the recovery problem with my last Nandroid Backup I am a little unsure what to do!?

The last thing I did is to update the 4Ext Touch Recovery to v1.0.0.4 RC3!

Regards and have a nice Weekend,
Guido

 

[Hadron]

Don't know why there would have been a problem with the nandroid. I'd suggest taking a new one, now that you have a working ROM, and hope it was a one-off. I've not heard of anyone else having a problem with 4Ext. Maybe the critically-low storage was a factor, but the nandroid restore should put you back to where you were when you took the backup.

I suppose one thing would be to take a full app/data backup (Ti), a new nandroid, then restore the nandroid. If it restores it gives you some confidence. If it doesn't, it means repeating the setting up you just had to do, which would be a pain, but we would know for sure what doesn't work.

You do want to test other custom ROMs - that's the fun bit

 

[koshac]

Don't know why there would have been a problem with the nandroid. I'd suggest taking a new one, now that you have a working ROM, and hope it was a one-off. I've not heard of anyone else having a problem with 4Ext. Maybe the critically-low storage was a factor, but the nandroid restore should put you back to where you were when you took the backup.

Well the Nandroid Backup state was a low memory with about 18MB, possibly a problem!? The curios thing is that stuck on the HTC bootsreen I flashed the prerooted stock GB ROM and after the reboot it booted just fine!

I suppose one thing would be to take a full app/data backup (Ti), a new nandroid, then restore the nandroid. If it restores it gives you some confidence. If it doesn't, it means repeating the setting up you just had to do, which would be a pain, but we would know for sure what doesn't work.

That

 

[koshac]

@Hadron

I did as you suggested and ran a Nandroid Backup with 4Ext!

To do this I started the 4Ext Recovery Control and chose new backup with the Option not to stay in recovery after backup finished.

My Desire rebooted in recovery and performed the backup without any problems then rebooted and got stuck on the HTC bootscreen!?

I pulled the battery twice and restarted afterwards with no change

I then booted in recovery and only restored the boot partition of the previously created backup and stuck again!

Next step was to first format the boot partition and then restore it from the backup (possibly unnecessary because when restoring boot 4Ext does erase the boot partition before it recovers it anyway!?) and stuck again!

Now I am at a point where I do not know what to do next and I find it really disturbing that I cannot even rely on the creation of a Nandroid backup nor the recovery of it!

Is it possible that this might have something to do with the version of HBOOT I use? It is the one revolutionary flashed during S-OFF!

Is there anything else I can do now?

Regards,
Guido

 

[Hadron]

It shouldn't be the hboot - we're mostly using alpharev hboots of some sort, and you haven't been changing it before reboot.

Interesting thing here is that you just made a backup then got stuck on reboot, so the first time you had not even tried to restore anything. Now there was historically a quirk where that would happen the first time (and only the first time) someone made a backup with ClockWorkMod, and the fix there was to restore (fully) the backup you had just made. But this doesn't sound the same.

I would certainly contact 4Ext's developer, as he may have ideas and will surely want to know.

Otherwise it's a matter of how much messing/investigating you want to do. I would try reflashing the ROM without a wipe. If your data are Ok and it's something else corrupted there's a good chance that will work. Perhaps format /system and wipe cache from recovery first, to play safe (or on a second go if the flash alone doesn't do it).

If that doesn't work it may mean that data have been corrupted. Could then try a wipe & see if it will boot (you have a Ti backup?). If it does then perhaps go back to recovery and try restoring just /data, sd-ext and .android_secure - if it then fails we know the problem was inside one of those. If it only boots after a wipe then it's time for the Ti restore.

Good luck & tell us what you find.

 

[koshac]

It shouldn't be the hboot - we're mostly using alpharev hboots of some sort, and you haven't been changing it before reboot.

Interesting thing here is that you just made a backup then got stuck on reboot, so the first time you had not even tried to restore anything. Now there was historically a quirk where that would happen the first time (and only the first time) someone made a backup with ClockWorkMod, and the fix there was to restore (fully) the backup you had just made. But this doesn't sound the same.

I would certainly contact 4Ext's developer, as he may have ideas and will surely want to know.

Otherwise it's a matter of how much messing/investigating you want to do. I would try reflashing the ROM without a wipe. If your data are Ok and it's something else corrupted there's a good chance that will work. Perhaps format /system and wipe cache from recovery first, to play safe (or on a second go if the flash alone doesn't do it).

If that doesn't work it may mean that data have been corrupted. Could then try a wipe & see if it will boot (you have a Ti backup?). If it does then perhaps go back to recovery and try restoring just /data, sd-ext and .android_secure - if it then fails we know the problem was inside one of those. If it only boots after a wipe then it's time for the Ti restore.

Good luck & tell us what you find.

Thank again for the quick reply!

I will try these things and certainly report back any findings, because that

 

[Hadron]

I'd be tempted to send a PM, explaining that you can't post in the thread yet. Or you can post any old stuff in a few other threads until you are able to post in the dev thread (I assume the limit is number of posts rather than time? It's been a while for me).

Or you can find an email address from the market page for 4Ext Recovery Control.

 

[koshac]

I'd be tempted to send a PM, explaining that you can't post in the thread yet. Or you can post any old stuff in a few other threads until you are able to post in the dev thread (I assume the limit is number of posts rather than time? It's been a while for me).

Or you can find an email address from the market page for 4Ext Recovery Control.

The limit is 10 Posts!

I created a new Thread in the Desire Q&A section and also finally send him a PM and he came back directly, but won

 

[koshac]

So after a newly try to recover my latest backup this also failed :-(

I got no errors, but after reboot I got stuck again on bootscreen!

I then reflashed the ROM I am using and to my surprise that worked!

I really don't know what the problem is with recovery, but it's getting a little frustrating...

Regards,
Guido

 

[Hadron]

Hmm, reflashing ROM without wipe => phone boots implies that some part of the ROM had been corrupted. But why?

But I'm guessing that with the phone working again you don't want any more experiments today

 

[koshac]

Hmm, reflashing ROM without wipe => phone boots implies that some part of the ROM had been corrupted. But why?

But I'm guessing that with the phone working again you don't want any more experiments today

Not really

Is there a way to check where exactly the boot process got stuck?

Regards,
Guido

 

[SUroot]

Yes, with a logcat. You need to do this in adb. Please read adb faq.

Then command would be:
adb logcat

You do this when you boot the phone. You may not learn anything though

 

[koshac]

Yes, with a logcat. You need to do this in adb. Please read adb faq.

Then command would be:
adb logcat

You do this when you boot the phone. You may not learn anything though

Hmm, then why do it at all?

Regards,
Guido

 

[SUroot]

Because you may?

 

[koshac]

Because you may?

Ok...you have a point here

Regards,
Guido

 

[koshac]

Hmm, reflashing ROM without wipe => phone boots implies that some part of the ROM had been corrupted. But why?

But I'm guessing that with the phone working again you don't want any more experiments today

I am now in contact with the 4Ext developer and he suspects a corrupted ext3 could be the problem!?

But why does flashing the ROM again without any wipe corrects the problem?

As I know so far there is nothing done to the filesystem during flashing!?

Very strange!

Regards,
Guido

 

[SUroot]

As I know so far there is nothing done to the filesystem during flashing!?

A file system is almost literally a database of data and it's location on disk. Any Writing to disk (or wiping of) affects the file system as the data is wiped / created, so is a corresponding database entry.

 

[koshac]

A file system is almost literally a database of data and it's location on disk. Any Writing to disk (or wiping of) affects the file system as the data is wiped / created, so is a corresponding database entry.

Your right! I forgot that the flashing itself modifies the filesystem! Shame on me

But does the flashing modify anything on the ext3 partition? I really don

 

[Hadron]

That depends on the ROM. ROMs using a Sense version newer than what comes with the Desire generally do, others generally do not.

 

[koshac]

That depends on the ROM. ROMs using a Sense version newer than what comes with the Desire generally do, others generally do not.

Thanks! I didn