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

Root oldest firmware for slcd?

scotty85

scotty85

Extreme Android User
anyone know what is the oldest firmware i could flash on an slcd and still be able to see the screen?

once we know that info,anyone have a link to to an RUU or PB31IMG of that firmware? :D

messing with my spare junk incredible again. :)
 
i believe only 2.2 and up will work. But i guess it would be possible to put a froyo kernel and radio and run eclair...not sure though.
 
i cant really change anything with an s-on hboot. :mad: whatever is wrong with it prevents unrevoked from running to get s-off. im trying to get it s-off,and get a custom recovery so i might have some more options to figure out what its prollem is.

the software on it is 3.26.605.1,wich i believe is the november OTA. i found a 3.21.605.1,wich is a little older,not sure by how much. i assume the 1.xx.xxx.x builds ive come across are eclair...

know of anything older than 3.21.605.1?
 
scotty85 said:
i cant really change anything with an s-on hboot. :mad: whatever is wrong with it prevents unrevoked from running to get s-off. im trying to get it s-off,and get a custom recovery so i might have some more options to figure out what its prollem is.

the software on it is 3.26.605.1,wich i believe is the november OTA. i found a 3.21.605.1,wich is a little older,not sure by how much. i assume the 1.xx.xxx.x builds ive come across are eclair...

know of anything older than 3.21.605.1?
Click to expand...

Does z4root work?
 
I THINK 3.21.605.1 was the earliest Froyo and it was leaked, most likely by XDA user Football. Leaked late Aug, early Sep 2010 range??? If there was anything before that, I don't remember it.
 
You have GB on it now right scotty? I wonder what is different about that phone that doesn't allow your other thread to apply?
 
sdrawkcab25 said:
Does z4root work?
Click to expand...

I can usually get temp root to work,sometimes even sign in,download astro and rom manager,and flash clockwork with rom manager. But it never sticks,presumably because z4 is giving access to /system,but not disabling emmc write protect. I've only got a few minutes before things start force closing like crazy and the phone is useless :eek:

If I attempt permanent root it usually freezes. If it gets past that,it loses the root during the reboot. :mad:
 
iowabowtech said:
You have GB on it now right scotty? I wonder what is different about that phone that doesn't allow your other thread to apply?
Click to expand...
No,I'm on 3.21.605.1 now. I'm able to use zergrush and rewriting the misc image to go backwards. I took myself down to 3.26.605.1 wen zergrush came out.

The prollems with running 3.22 or 3.31 are that it forgets its settings on reboot. I have to turn USB debugging back on each time,and even re-sign in and resync with Google. All user apps disappear. Its almost like a factory reset each boot.

It also gives me a weird error message that the SD card has had an unexpected prollem,and is mounted read only. I tap the message in the pull down and it disappears. :confused: it seems to function correctly... USB mounting works,and I can read and write to it.
 
That certainly is odd. So if you just run the ruu without unrevoked, everything is fine? Or does it happen then too?
 
The factory reset affect? Happens every time... unrevoked or not. Thinking its a hardware issue maybe?
 
scotty85 said:
No,I'm on 3.21.605.1 now. I'm able to use zergrush and rewriting the misc image to go backwards. I took myself down to 3.26.605.1 wen zergrush came out.

The prollems with running 3.22 or 3.31 are that it forgets its settings on reboot. I have to turn USB debugging back on each time,and even re-sign in and resync with Google. All user apps disappear. Its almost like a factory reset each boot.

It also gives me a weird error message that the SD card has had an unexpected prollem,and is mounted read only. I tap the message in the pull down and it disappears. :confused: it seems to function correctly... USB mounting works,and I can read and write to it.
Click to expand...


Sounds like the original incredible I sent back to Verizon... Mine was an AMOLED though.
 
Well, since you're an experimenting type and more than capable, I suggest trying this Scotty:

SOLVED: messed up partitions on internal storage - CyanogenMod Forum

Focus particularly on post #7 of that thread. I've been through this process twice but a long time ago and recovered a few phones that were showing "spiraling death" type sypmptoms. It's the only idea I have left short of calling it a hardware failure which means a non-useful phone anyway.
 
I'd add that you have to do quite a bit of reading between the lines on those instructs but all things that make sense. For example, he doesn't mention adb shell, you just have to know that's the case. Another example, when pushing the parted files, you have to cd to /sbin, that sort of thing. Probably goes without saying in your case but just a heads up.
 
iowabowtech said:
Well, since you're an experimenting type and more than capable, I suggest trying this Scotty:

SOLVED: messed up partitions on internal storage - CyanogenMod Forum

Focus particularly on post #7 of that thread. I've been through this process twice but a long time ago and recovered a few phones that were showing "spiraling death" type sypmptoms. It's the only idea I have left short of calling it a hardware failure which means a non-useful phone anyway.
Click to expand...

lol great minds think alike,sir :D i had seen that before,and its in fact the only reason im still messing with it... and why im working toward getting s-off and a working recovery,since from post#7 you need these things:

Here's what you'll need:
1.Working recovery, basic knowledge of adb & the shell
2.Parted (download here)
3.stock PB31IMG.zip
Click to expand...

2 and 3 are no prollem. if i can get a recovery,im going to give it a shot for sure. :cool:
 
I could be wrong Scotty, but I think you can make this work with the stock recovery and in our case (HTC) even working hboot. Unless I'm off base, there's nothing you absolutely NEED a custom recovery for to actually fix the partitions. Now they are sometimes loading a rooted rom at the end of the process, but if you could even get the stock rom loaded up...and stable...(may have to factory reset via stock recovery afterward, although not sure why after loading the PB31IMG), then I think you could perhaps root with new Unrevoked and not have all the FC's and settings not being retained issue. I'm guessing if it's not hardware, maybe it's a data retrieval problem from the internal storage.
 
Hmmmm...just noted that you're having trouble with stability during temp root. Perhaps that could be a downer after all. I was kinda banking on that.
 
hmm. i actually hadnt read much past that post,aster seeing the "working recovery" part. i think ill give this a shot later,cant curt for sure.for now i gotta go to work :(

as far as temp root,i actually havent had any prollems with it temp root remaining when in a command window. its just when i try and use z4 or visionary,or something else that requires the phone to do things and reboot ;)

the downgrade went just fine. i tried getting temp root and running "wpthis" to unlock the emmc,but it failed for some reason :mad: also tried to rewrite mmcblk0p21 with clockwork,but without unlocking the mmc it just boots to the stock recovery,even tho it looks like it worked :(

Code: 
c:\mini-adb_inc>[COLOR="Red"]adb push psneuter /data/local/[/COLOR]
1429 KB/s (585731 bytes in 0.400s)

c:\mini-adb_inc>[COLOR="red"]adb push busybox /data/local/[/COLOR]
1393 KB/s (1062992 bytes in 0.745s)

c:\mini-adb_inc>[COLOR="red"]adb push recovery.img /data/local[/COLOR]
1593 KB/s (3137536 bytes in 1.923s)

c:\mini-adb_inc>[COLOR="red"]adb shell chmod 777 /data/local/psneuter[/COLOR]

c:\mini-adb_inc>[COLOR="red"]adb shell chmod 777 /data/local/busybox[/COLOR]

c:\mini-adb_inc>[COLOR="red"]adb shell /data/local/psneuter[/COLOR]
property service neutered.
killing adbd. (should restart in a second or two)
c:\mini-adb_inc>[COLOR="Red"]adb shell /data/local/busybox md5sum /data/local/recovery.img[/COLOR]
ea382ca5809cb872d0582aa22741d592  /data/local/recovery.img

c:\mini-adb_inc>[COLOR="red"]adb shell dd if=/data/local/recovery.img of=/dev/block/mmcblk0p21[/COLOR]
6128+0 records in
6128+0 records out
3137536 bytes transferred in 0.078 secs (40224820 bytes/sec)

c:\mini-adb_inc>[COLOR="red"]adb shell /data/local/busybox md5sum /dev/block/mmcblk0p21[/COLOR]
ea382ca5809cb872d0582aa22741d592  /dev/block/mmcblk0p21

c:\mini-adb_inc>[COLOR="red"]adb reboot recovery[/COLOR]
 
Well if you can get temp root, perhaps try pushing the "parted" files with emulator, unless you can make it happen with the Windows cmd.
 
You must log in or register to reply here.
Back
Top Bottom