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

Root Memory full

S

solly72

Newbie
Hi everyone,
I have a desire which I decided to root a couple months ago. In that time I have tried a few rims and all went well. The last Rom I installed which was I think runny Rom and had good support for a2sd, installed fine but was lagging a lot. I tried to install a different Rom and that's when my problems started.

After the install of the new Rom it was showing 'memory almost full' with 2 disc icons on the top left of screen and continuous force close errors without letting me access the phone because the force close errors just keep coming all the time. I tried installing other Roms with same result.

Where I'm at now is that I have also lost my recovery screen where you can install from zip, wipe etc. When I go into recovery it just shows a triangle with red exclamation mark.

I have tried everything I can think of. I'm stuck and don't know what else to do. I have done clear storage, full wipe, you name it.

I have since bought the velocity 4g but still really keen to fix it.

Somebody please help me I'm going bonkers.

Thanks in advance,

John
 
What was the Rom ,after runny?

That red triangle means you've got HTC stock recovery.

Are you definitely going into recovery the same way?

Are you s-off?

Gsm or cdma?

How big is your ext partition on sd card?
 
The ROM that was installed before everything started happening was Runnymede AIO 6.1. The ROM I ried to install after was Icecream sense v2 bravo.

Definately going into recovery the same way. The ext partition that i had made on my sd card was 2 Gig.

This is what comes up onmy phone when i powerup holding down vol down.

Alpharev Fatsys
BRAVO PVT1 SHIP S-OFF
HBOOT-6.93.1002
MICROP-031d
TOUCH PANEL-SYNT0101
RADIO-5.17.05.23
Aug 10 2010, 17:52:10

I have the GSM version, I think it's the A8181.

I also did manage to run the RUU v2.3 I think. I reckon that's when I lost my old recovery screen where I was able to load ROMS. So I have the 2.3 stock ROM on there with the problem I describedin my first post. I can't understand why it would show me low and full memory when I have wiped the whole system, and even tried it without sd card and same problem. The lock screen looks normal but can still see the 2 disc icons on top left.

When I unlock the phone is when the continuous force close errors happen and they don't stop.

Thanks SUroot for the reply
 
Ok what you need to do is download a recovery.img. I recommend the 4ext touch from xda. Fastboot flash it because you are still s-off.

Then format system, data and cache via that recovery.

If you want sense, I don't recommend anything over sense 2.0. Maybe a 2.0 + 3.0 mix. 3.5 is a no no if you want speed and stability. Same with ice cream sandwich

So pick a stable Rom that is not above. After all formats, try and flash it.

Keep me posted. Read my adb and fastboot faq if you get stuck. Skip adb as not relevant today
 
Hey,
I did exactly what you told me to do and even in the order you said. I had no problem installing a recovery imge (very easy afte reading your tutorial). formatted data, system and cache, install a ROM and same thing, fist thing that tells me it hasn't worked is when I see the 2 disc icons on top left of screen show up, and sure enough, when I unlock the lockscreen continuous force close errors. ontop of the memory full message.

I just can't work out how itcan be when I wipe / format everything on the phone, it still shows the full disc message, and the force close errors. The only thing i haven't done is "format boot". I don't know what the consequences would be after doing that. Maybe if someone could tell me what to expect by doing that and whether I should or not.

Maybe my phone is cactus beyond help.
 
Did you fastboot flash a different hboot first before trying different rom? What rom are you trying to flash?

That fatsys hboot creates a large system partition with a tiny data partition, and needs one of the INT2SD scripts to work properly. You need to change the hboot (eg from AlphaRev) to one that will suit the rom, then flash the rom.

Also would recommend re-partitioning sd card (use Gparted) as anything above a max of 1GB can also cause some problems.
 
It's nothing to do with boot. Boot.img is flashed with every Rom.

Can you use adb? Boot into.recovery, use adb to:
mount /data
ls

That should list data content which should be empty

Also
mount /sd-ext

To see if anything is on ext. Also.should be empty
 
Hi,

I got into adb and checked /data and /sd-ext. I see three columns of forders in there, although the folders seem to be empty. Is that mormal? it has the folders "data, datadata,boot, cache, default.prop,dev,emmc,etc.init,init.rc,prc,res,root,sbin,sd-ext,sdcard,sys,system,tmp,ueventd.goldfish.rc and uevend.rc

The thing I find weird is that these folers are showing up whether I do mount /data or /system or /sd-ext, the same folders are showing but there's nothing in the folders.
 
I tried all the folders including the ones you mentioned and there's nothing in there. I'll stuff around with it a bit more and see what happens. I'll keep you posted.

Thank you very much for trying to help out, much appreciated.

PS. Weird thing, it doesn't really bother me if its stuffed, I just want to fix it so I know what was wrong with it. I hate it when technology beats me.
 
solly72 said:
The ROM that was installed before everything started happening was Runnymede AIO 6.1. The ROM I ried to install after was Icecream sense v2 bravo.

Definately going into recovery the same way. The ext partition that i had made on my sd card was 2 Gig.

This is what comes up onmy phone when i powerup holding down vol down.

Alpharev Fatsys
BRAVO PVT1 SHIP S-OFF
HBOOT-6.93.1002
MICROP-031d
TOUCH PANEL-SYNT0101
RADIO-5.17.05.23
Aug 10 2010, 17:52:10

I have the GSM version, I think it's the A8181.

I also did manage to run the RUU v2.3 I think. I reckon that's when I lost my old recovery screen where I was able to load ROMS. So I have the 2.3 stock ROM on there with the problem I describedin my first post. I can't understand why it would show me low and full memory when I have wiped the whole system, and even tried it without sd card and same problem. The lock screen looks normal but can still see the 2 disc icons on top left.

When I unlock the phone is when the continuous force close errors happen and they don't stop.

Thanks SUroot for the reply
Click to expand...

Sure its not related to this hboot?
 
I haven't changed hboot since I had problems. Doesn't matter what Rom I try to flash I either get force close errors but mostly the phone will either hang or restart loop after an install.

What hboot do you recommend? And where's the best place to get it?
 
Ive never seen one of our Hboots say "Alpharev Fatsys".

Maybe fastboot flash teh bravo stock one from the alpharev website.
 
Pretty sure its not helping, that hboot creates huge Sys partition and leaves 5mb for cache and 5mb for data. As I said in earlier post you won't be able to install any Roms that don't have INT2SD script. Suggest you check hboot requirements for Rom you want, then download suitable AlphaRev hboot, fastboot flash it then flash new Rom.
 
SUroot said:
Ive never seen one of our Hboots say "Alpharev Fatsys".

Maybe fastboot flash teh bravo stock one from the alpharev website.
Click to expand...

SU looks to have been created using thalamus tool by one of the Rom dev, can't remember which Rom on xda though.

OP don't you remember flashing it in first place?
 
Ah interesting.

OP may not remember. OFten these ROM devs put step by step guides and people follow them not entirely sure what theyre doing.

Definitely go back to bravo stockfirst then.
 
I don't remember flashing a hboot.

Anyway, I have just flashed the stock hboot and am about to chose a ROM and see what happens.
 
Well guys,

After flashing the stock hboot, I loaded the Aurora v6 (special Edition), created a 1 Gig ext4, and it all worked. No force close errors, (not even one) no low memory, nothing.

Big thanks to SUroot and Saltire for the help. I never would've thought the hboot would've given me so many problems. I wonder if runnymede AIO v6.1 could've changed the hboot! That was the last ROM before things started happening, or maybe the ROM I tried to load after which is why everything started happening.

Anyway, I have definately learned alot from this. YOU GUYS ARE AWESOME
 
solly72 said:
I wonder if runnymede AIO v6.1 could've changed the hboot! That was the last ROM before things started happening, or maybe the ROM I tried to load after which is why everything started happening.
Click to expand...

Nope - at least afaik this has always needed user to change this themselves, bit worrying if it's part of rom flash process as like yourself folk might not realise the system critical hboot has changed, get themselves into problems, try other things in desperation and end up really doing some permanent damage.
 
You've never put a file called PB99IMG.zip onto your SD card and booted into HBOOT? That's the other way hboot is updated, but the method doesn't actually tell you that it's changing hboot (you could, with the right stuff in the zip, update anything this way), so could perhaps do that without knowing what it was changing?

I can't see anything in the Coolexe or Runnymede sites/threads to suggest that they actually change hboot during installation, but the INT2SD thread at XDA does reference this hboot and also links to the Runnymede thread. So if it was in any way connected to a ROM install, it was most likely that one.
 
Yes you're right, I did flash that file I remember so my system could support int2sd I remember. But I didn't know or care at the time what that file did to my system.
 
It's always good to know what is being done. For example, if you tried to update the radio by flashing a zip from recovery without realising that you now had a small cache partition the result could have been terminal.
 
You must log in or register to reply here.
Back
Top Bottom