Database Info

RC30 download link

Hot off the presses. Get it here.
That file is the crappy "patch" version that tries to patch you from RC29 to RC30.
Here is the full update, which should be much more reliable
Obviously, don't install it unless you want to lose root access
Update for those who are interested: I went ahead and bought myself a new G1. One of the stores in the area had a couple. It still had RC28 (not RC29) on it, so I'm back in business. I'll just unlock my RC30 one and sell it on ebay.

OMG how stupid can they be... look what I see in the update script
# delete unneeded files
delete SYSTEM:system/bin/telnetd
Click to expand...
Click to collapse
Can we patch this like today cause I kinda think there is more to this than just doing that.

neoobs said:
OMG how stupid can they be... look what I see in the update script
Can we patch this like today cause I kinda think there is more to this than just doing that.
Click to expand...
Click to collapse
There is. They added a kernel option "console=null", which I suspect basically makes it so that the physical keyboard no longer sends input to the console device. Note that there is still a root shell running on the console though.. it's just that now there isn't any way to send keypresses to that root shell.
Plus there are a ton of patches to the android apps and framework jars and such. Not sure what all changed there.
I'm in the process of modifying the patch, to apply to my phone without losing root access. More to come

What does the "applypatch" piece do?
That part looks different.
Interesting that it's only a 4 meg update, and that it only contains a new recovery.img and a new boot.img - I wonder what is different in those images. I hope they are keeping the recovery stuff in the open source branch updated - because, well, that's the nice thing for them to to do
Jesus Freke - when you get your patched-up version ready, please post it somewhere for us lazy bastards who want to ride your coat-tails

I just noticed something. This update doesn't wipe the system partition. If you had created a setuid copy of the shell ("su", or whatever), I don't think it will get deleted if you applied the update as-is.

but didn't you say it removes the use of keyboard in shell? If so we would still be up the creek. you know what a notice this update came really fast i never got and OTA until this(fishy) i had to force OTA. Well hope you work your magic JesusFreke.

Arg! dangit. I accidentally applied RC30 and lost my root access. I copied the wrong update file to my sdcard... grrrr!
So I'm out of the game. Sorry.
Oh, btw - I was wrong about the update keeping the setuid shell around. It completely wipes the permissions of the system folder, so if you did have a setuid copy of the shell, it will be set back to normal non-setuid status by the update. duh.

Sh**!! You were the shining hope , one question can you still get root through the adb shell? cuz if so you can save your a**

Nope. Like I said, I'm out of the game. Unless someone wants to trade me for a RC19/RC29 phone. Or until another root exploit is found. *sigh*

DOH! That sucks! Sorry to hear that, and thanks for taking one for the team.
So if an update does try to install do we just need to turn off the phone until a solution is found? I may need to go back to my Dash for a while until this all gets figured out!
The update that you meant to put on the card- was it a test? If the worst that will happen is the update will take maybe someone that doesnt mind the update could test it for you?

JesusFreke said:
Arg! dangit. I accidentally applied RC30 and lost my root access. I copied the wrong update file to my sdcard... grrrr!
So I'm out of the game. Sorry.
Click to expand...
Click to collapse
I'm sorry about that!
Also, I'm confused. Hadn't you updated the keys in your bootloader to prevent an update? Or does that simply prevent the phone from downloading an update?

Can not we flash back that old RC29 File again ????

The update zip contains the boot.img and the recovery.img. so when the update starts it rewrites JesusFreke's mod recovery.img

spoofing
could we spoof the version # on our device? thus ending the nag and the ability to force the upgrade, for the time being?
bhang

RegGuheert said:
I'm sorry about that!
Also, I'm confused. Hadn't you updated the keys in your bootloader to prevent an update? Or does that simply prevent the phone from downloading an update?
Click to expand...
Click to collapse
Yes. But I had accidentally re-signed the full update with the new key and updated my phone with it. I was in the process of modifying the update, and had grabbed the wrong file to sign and update.

JesusFreke said:
Yes. But I had accidentally re-signed the full update with the new key and updated my phone with it. I was in the process of modifying the update, and had grabbed the wrong file to sign and update.
Click to expand...
Click to collapse
Ahh! That's a pain in the arse... the usb mass storage process is running as root, any chance of a buffer exploit there?

JesusFreke said:
Yes. But I had accidentally re-signed the full update with the new key and updated my phone with it. I was in the process of modifying the update, and had grabbed the wrong file to sign and update.
Click to expand...
Click to collapse
koush said:
mount -oremount,rw /dev/block/mtdblock3 /system
You can't remount that directory that unless you have root.
Use the dd command to copy stuff around (the cp command is not available). I should mention I'm a Windows guy, and am pretty clueless with Linux: my coworker figured the rest of this out once I got to a root prompt.
Incidentally, in the /system/bin directory there is a flash_image executable that changes the recovery.img used when you hard reset the device. I've noticed that I can run this without root access from a standard adb shell. Maybe we never needed to root the device after all... I think we can flash it without root access... I'm too scared to mess with that at all though.
Click to expand...
Click to collapse
I found this, you may want to look into it.

syrusfrost said:
I found this, you may want to look into it.
Click to expand...
Click to collapse
Thanks. But you have to have root access for the flash_image command to work. Or more precisely, you have to have write access to the /dev/mtd/mtd# device that you are trying to flash.

I am also the same unlucky guy who had Press Update Button and now we are in RC30
Now what are the chances of our device to get root access or ability to flash Test_Signed code in RC30

well i removed( # delete unneeded files delete SYSTEM:system/bin/telnetd )and replaced the boot.img and recovery.img with jesusfreke's anything else i should edit before i try to resign and update?

Simpler instructions for installing modified recovery image

Here are some instructions for installing JesusFreke's modified recovery image. You have to install the modified recovery image before you can install modified firmwares. These instructions are simpler than the existing ones because they don't require the use of adb or telnet.
Firstly, you need to already have firmware version RC29 or RC7. To check which version you have go to "Settings" and then "About phone". At the bottom you will see a "Build number" which will include "RC" and then a number. If you have RC30 or RC8 then you need to downgrade. THAT WILL WIPE ALL THE DATA/APPLICATIONS ON YOUR PHONE. Instructions for downgrading are here.
Now that you have RC29/RC7:
Download 'AndroidMod.zip' from one of the links in JesusFreke's post
Extract 'recovery_testkeys.img' from that zip and copy it to your SD card.
Download 'install.zip' which is attached to this post below.
Extract 'install' from that zip and copy it to your SD card.
Put the SD card in the phone or disconnect the phone if it is attached by USB.
Reboot the phone (switch it off and then on again).
When it has finished booting type the following at the home screen. It will start searching your contacts, but don't worry about that. Also, you won't see any visible sign that the first command worked. Just go ahead and type the second command straight afterwards:
cd sdcard<press enter>
sh install<press enter>
After a moment your phone should reboot itself. To check that the flashing worked, switch off the phone and then hold down the home key while you switch it on again. Keep the home key held down until you see the recovery screen (with the "!" triangle and the picture of the phone). Then press Alt+L on the keyboard and if you see "Using test keys" on the second line of text then the modified recovery image is installed and you can now install a modified firmware.

Cool! Thanks for that... much simpler... anyone else tried this yet?
I'm going to attempt all this later.
Phil

i just tried it and it works. confirmed.

great for beginners!
Hey tried it and it works!! Now how about one on restoring data after backup.

thanks for this just tryed it and worked first time.

First off thanks for all information here. Am I correct that after I downgrade to rc29 I then follow the instructions in this thread and then I can install jf 1.3 rc30. Or do I have this all wrong?

gottifour said:
First off thanks for all information here. Am I correct that after I downgrade to rc29 I then follow the instructions in this thread and then I can install jf 1.3 rc30. Or do I have this all wrong?
Click to expand...
Click to collapse
you are correct. once you have the modded recovery image, you can use jfs update zips.

korndub said:
you are correct. once you have the modded recovery image, you can use jfs update zips.
Click to expand...
Click to collapse
Sweet! Thanks for the reply. I will attempt this real soon. Do you have any suggestions before I begin? After I modify the firmware I will not get ota updates anymore right? Lets say the cupcake update, or any other for that matter, does come out. I would just have to wait untill a smarter person then me converts it to a new modified image to flash to my phone? Is that right? Thanks for any help. I'm sure this is probably the worng place to ask all of these questions. d

gottifour said:
Sweet! Thanks for the reply. I will attempt this real soon. Do you have any suggestions before I begin? After I modify the firmware I will not get ota updates anymore right? Lets say the cupcake update, or any other for that matter, does come out. I would just have to wait untill a smarter person then me converts it to a new modified image to flash to my phone? Is that right? Thanks for any help. I'm sure this is probably the worng place to ask all of these questions. d
Click to expand...
Click to collapse
in one of the zips from JF is an app that will REsign any update.zip, so when an ota comes you just have to wait for the update.zip to show up then you could REsign it with the dev keys, pretty easy, but it will probably show up pretty fast now that almost every G1 is probably running that keyset.
bhang

UPDATE..
Its working now...I wasn't doing it in the telnet client. I was just typing it in randomly and it didnt work that way for some reason.
Ok. I have downgraded to rc29 and copied the two images two my sd card. but I'm not sure if I even have root. When I try to change directory it doesnt happen. I have to have root by installing the modified rc29 right? I did type telnetd at the home screen and pushed enter. nothing happened. I know I'm missing something just not sure what yet? I did install the telnet client from the market as well. I'm not understanding something it appears. Anyone?

gottifour said:
UPDATE..
Its working now...I wasn't doing it in the telnet client. I was just typing it in randomly and it didnt work that way for some reason.
Ok. I have downgraded to rc29 and copied the two images two my sd card. but I'm not sure if I even have root. When I try to change directory it doesnt happen. I have to have root by installing the modified rc29 right? I did type telnetd at the home screen and pushed enter. nothing happened. I know I'm missing something just not sure what yet? I did install the telnet client from the market as well. I'm not understanding something it appears. Anyone?
Click to expand...
Click to collapse
use the telnet client to telnet to localhost. *then* you will have root. (note: that's only applicable for RC29. to get root on JFv1.3, just type su in terminal emulator).
To know if you have root access, check the prompt you get. if you get #, then you have root access. if you get $, you don't have root access.

JJC1138 said:
Here are some instructions for installing JesusFreke's modified recovery image.
Click to expand...
Click to collapse
well this is a big help for many people thank you for your addition

JesusFreke said:
use the telnet client to telnet to localhost. *then* you will have root. (note: that's only applicable for RC29. to get root on JFv1.3, just type su in terminal emulator).
To know if you have root access, check the prompt you get. if you get #, then you have root access. if you get $, you don't have root access.
Click to expand...
Click to collapse
I got the #
Thanks so much for everything so far..This is really awesome!!

gottifour said:
UPDATE..
Its working now...I wasn't doing it in the telnet client. I was just typing it in randomly and it didnt work that way for some reason.
Click to expand...
Click to collapse
Hi there. I just wanted to clarify that if you're following the instructions I posted then you don't need telnet.
gottifour said:
Ok. I have downgraded to rc29 and copied the two images two my sd card. but I'm not sure if I even have root. When I try to change directory it doesnt happen. I have to have root by installing the modified rc29 right?
Click to expand...
Click to collapse
No, you don't need the modified RC29 to do this. After you type the "cd sdcard<enter>" command nothing visible should happen. It works because the bug in RC29 which we are exploiting executes everything you type on a hidden root console, so the cd command works, but it just doesn't show you anything. Then you enter the second "sh install<enter>" command and that runs a script that does all the good stuff and then reboots.

JJC1138 said:
Hi there. I just wanted to clarify that if you're following the instructions I posted then you don't need telnet.
No, you don't need the modified RC29 to do this. After you type the "cd sdcard<enter>" command nothing visible should happen. It works because the bug in RC29 which we are exploiting executes everything you type on a hidden root console, so the cd command works, but it just doesn't show you anything. Then you enter the second "sh install<enter>" command and that runs a script that does all the good stuff and then reboots.
Click to expand...
Click to collapse
Thanks for the reply and for simplifying this for everyone. I was confused at first but now I understand better. I have the modified RC30 working now with the dev boot loader as well. Oh and a new theme too. Thanks again!!!

JJC1138 said:
Hi there. I just wanted to clarify that if you're following the instructions I posted then you don't need telnet.
No, you don't need the modified RC29 to do this. After you type the "cd sdcard<enter>" command nothing visible should happen. It works because the bug in RC29 which we are exploiting executes everything you type on a hidden root console, so the cd command works, but it just doesn't show you anything. Then you enter the second "sh install<enter>" command and that runs a script that does all the good stuff and then reboots.
Click to expand...
Click to collapse
Correct, this is a really good idea! Instead of typeing telnetd to start it as root, you are typing in and running the script that will root your phone-- as root! I'll update my sticky post shortly.

worked for me now do i delete the install file, DREAIMG file and Recovery test keys files or do i have to keep em?

l0uisz said:
worked for me now do i delete the install file, DREAIMG file and Recovery test keys files or do i have to keep em?
Click to expand...
Click to collapse
You can delete them off your SD card after they're installed.

Us sprint 2.1 rom leaked.its exe file . For non rooted

http://www.4shared.com/file/WU7XiKt-/RUU_Hero_C_Sprint_2206511_sign.html
to all dev. its said the leak for sprint 2.1 .is exe file.non rooted phone can upgrade it. heard everyyhing work fine. im gsm version. im not respondsible for any damage or bricked of your phone.
the source from facebook htc hero page.
Sent from my Hero using Tapatalk

IS FOR SPRINT. NOT GSM. BE ALERT
Sent from my Hero using Tapatalk

orangeclanz said:
http://www.4shared.com/file/WU7XiKt-/RUU_Hero_C_Sprint_2206511_sign.html
to all dev. its said the leak for sprint 2.1 .is exe file.non rooted phone can upgrade it. heard everyyhing work fine. im gsm version. im not respondsible for any damage or bricked of your phone.
the source from facebook htc hero page.
Sent from my Hero using Tapatalk
Click to expand...
Click to collapse
Nice to see the CDMA Hero has it's official 2.1 fame .. but come on lazy HTC, where is 2.1 for the GSM cousin? Let's hope tomorrow is THE day..

Looks like it's working
EDIT: However, this is exactly the same as Villain 5.2 (the same leak that is).

Pretty stable
It does work well.. What an improvement from the previous version

HomerSp said:
Looks like it's working
Click to expand...
Click to collapse
But not on GSM Hero's - grrrrrrrrrrrrrrrr

Didn't the GSM hero come out before the CDMA one? How come the CDMA one came out first?

hkr said:
But not on GSM Hero's - grrrrrrrrrrrrrrrr
Click to expand...
Click to collapse
It does if you port it (I only have gsm) ;-)

HOW LEGIT IS THIS RUU THOUGH? who can co-sign it? my buddy wants to use it but doesn't want to take any chances..

someonenewhere said:
Who can co-sign it?.
Click to expand...
Click to collapse
What?
I need a Mercedes? Can someone co-sign it?
Just playing

Old news >> http://forum.xda-developers.com/showthread.php?t=661057
All of our dev's 2.1 builds are already based on this build.
FYI, when the final (non-test) build .exe comes out, flashing your phone with it may render your phone unrootable.

someonenewhere said:
HOW LEGIT IS THIS RUU THOUGH? who can co-sign it? my buddy wants to use it but doesn't want to take any chances..
Click to expand...
Click to collapse
I put it on my Hero with no problems. My guess is its very close to the RC. Or he could just wait!!

Once you have used this leaked RUU from Sprint, how do you go and flash one of the ROMs here? When I attempt to do it, I get a pic of a generic HTC phone with a red triangle and a red exclamation point. I have to do a battery pull to get it to go away.

Don't flash a ruu that doesn't have root. The exploits used to gain root are probably patched. Also this will over write your custom recovery. Leaving you with no way to flash custom roms. Wait until someone puts out a build with root.

tedya said:
Once you have used this leaked RUU from Sprint, how do you go and flash one of the ROMs here? When I attempt to do it, I get a pic of a generic HTC phone with a red triangle and a red exclamation point. I have to do a battery pull to get it to go away.
Click to expand...
Click to collapse
Sounds like you already installed the ruu I'm guessing?..lol.
You need flash a custom recovery to the phone now to be able to flash custom ROMs.
Manually push flash_image to /system/bin >> You have to give flash_image permissions with adb
Code:
adb shell chmod 0755 /system/bin/flash_image
>> Root and reflash recovery (use this guide, except substitute 1.6.2 instead of 1.5.2 recovery (or use whatever recovery you want)>> Then reboot into recovery and nandroid backup your phone first thing >> Next you choose flash .zip and choose any custom ROM signed .zip on your sdcard to flash. >> After it flashes, reboot.
I included flash_image if you need it to push. This is not a .zip file, but I had to add .zip to attach it here. Rename it without the .zip or push it by typing
Code:
adb remount
adb push flash_image.zip /system/bin/flash_image

danknee said:
Sounds like you already installed the ruu I'm guessing?..lol.
You need flash a custom recovery to the phone now to be able to flash custom ROMs.
Manually push flash_image to /system/bin >> You have to give flash_image permissions with adb
Code:
adb shell chmod 0755 /system/bin/flash_image
>> Root and reflash recovery (use this guide, except substitute 1.6.2 instead of 1.5.2 recovery (or use whatever recovery you want)>> Then reboot into recovery and nandroid backup your phone first thing >> Next you choose flash .zip and choose any custom ROM signed .zip on your sdcard to flash. >> After it flashes, reboot.
I included flash_image if you need it to push. This is not a .zip file, but I had to add .zip to attach it here. Rename it without the .zip or push it by typing
Code:
adb push flash_image.zip /system/bin/flash_image
Click to expand...
Click to collapse
Hi Dankee. I am having difficulties pushing flash_image. This is what I type/get:
C:\android-sdk-windows\tools>adb push flash_image /system/bin/flash_image
failed to copy 'flash_image' to '/system/bin/flash_image': Read-only file system
Any ideas? Thanks so much.

tedya said:
Hi Dankee. I am having difficulties pushing flash_image. This is what I type/get:
C:\android-sdk-windows\tools>adb push flash_image /system/bin/flash_image
failed to copy 'flash_image' to '/system/bin/flash_image': Read-only file system
Any ideas? Thanks so much.
Click to expand...
Click to collapse
you cant gain root in any other way now theres no known exploit for 2.1 yet so your basically screwed till someone finds a exploit next time gather information before you run some random program that hasnt even really been verified

Yeah, I have learned my lesson I think. I think I am going to wait around until there is an exploit for 2.1 before I end up bricking this thing. I ended up getting the flash_image pushed but now I can't reboot and use the recovery image. It goes straight to a HTC with red triangle and red exclamation point. Luckily I was able to do a battery pull and it rebooted straight to the RUU 2.1 ROM. I thought I had bricked the thing. Whew! I'll see what some of the masterminds come up with here.
I think all I am missing is being able to go into bootloader and do the v1.6.2 recovery image and then flash a custom ROM.

http://forum.androidcentral.com/htc-hero-roms-hacks/9542-how-repair-your-bootloader-a
http://forum.androidcentral.com/htc-hero-roms-hacks/9542-how-repair-your-bootloader-after-using-2-1-ruu.html
This worked for me thanks to GBhil!

Thanks SooooneR! This worked for me. I am flashing one of DamageControl's ROMs right now. Very cool.

[Q] Cant boot after changing /system attributes using CHMOD

Hi,
i was trying to change the /system permissions using adb shell... commands shown in the attached screenshot
my main purpose was to install CWM for which we need to push modified recovery into /system/bin which requires rw permissions....
to do that i used the command chmod 6 /system from root and then tried to mv recovery file from sd root to /system/bin but that failed
when i checked the /system attributes using stat -c %A /system it returned "d------rw-"
after that i tried to mount the system from shell command but failed... then the phone got hanged and when i removed the USB cable it rebooted straight into recovery...
since the ive tried to check directory listing with adb ls /system command but it returns nothing... adb ls /data also shows only 3 files... i had taken a backup of /system using adb pull but i dont knw how much that'll help...
i did not take any backups before that... was trying to install CWM so that i could take rom backup....
im not able to boot the phone normally...
i would like to know if i can go back to original state?? if not is ther any other solution like flashing a new ROM or something...??
i would like to extract contacts nd messages if possible...
System config:
- Samsung Galaxy S 4G... everything stock
- Rooted!!
thanks in advance...

chi_visor said:
Hi,
i was trying to change the /system permissions using adb shell... commands shown in the attached screenshot
my main purpose was to install CWM for which we need to push modified recovery into /system/bin which requires rw permissions....
to do that i used the command chmod 6 /system from root and then tried to mv recovery file from sd root to /system/bin but that failed
when i checked the /system attributes using stat -c %A /system it returned "d------rw-"
Click to expand...
Click to collapse
'chmod 6 /system' did what you asked it to do. chmod, on a basic level, uses three (3) sets of permissions: global, group, and user. What you effectively did was set the user permissions to rw but blanked out everything else (like chmod 006).
If you can get into the shell, do this:
chmod 755 /system
That should put it back the way it was (7 = rwx for global, 5=rx for group, 5=rx for user)
See if that helps. Report back and let me know.
Real quick; I had my permissions backward. Although you still want 755 it should've read like this:
rwx for user
rx for group
rx for global
I had them backward.

Thanks stephen_w for ur reply...
I cant get into shell when i enter adb shell it throws this message
- exec '/system/bin/sh' failed: Permission denied (13)
any idea??

chi_visor said:
Thanks stephen_w for ur reply...
I cant get into shell when i enter adb shell it throws this message
- exec '/system/bin/sh' failed: Permission denied (13)
any idea??
Click to expand...
Click to collapse
I was worried about something like that. My guess is that your best bet is to see if you can get into download mode and flash a new ROM. Were you on Froyo or GB before? If you were on Froyo & you're trying to get to GB you'll need to insure you flash a ROM with the right boot loaders first, like chadster's KG4 (http://forum.xda-developers.com/showthread.php?t=1183413).
Let me know if I can be of help.

I was worried that I would have to flash a new ROM. Not that i mind doing it but ive not backed up anything!! I'd atleast like to see my contacts somewhere... let me know if that's possible...
So there's no other way to come out of this deadlock??
Im on Froyo... If its possible to roll back to stock Froyo it'll be great... If not i'll go for GB... Ive nothing against GB but i'd like to be sure everything works the way it was b4...
Its great to know you have and understanding of my problem... thanks mate...

chi_visor said:
I was worried that I would have to flash a new ROM. Not that i mind doing it but ive not backed up anything!! I'd atleast like to see my contacts somewhere... let me know if that's possible...
So there's no other way to come out of this deadlock??
Im on Froyo... If its possible to roll back to stock Froyo it'll be great... If not i'll go for GB... Ive nothing against GB but i'd like to be sure everything works the way it was b4...
Its great to know you have and understanding of my problem... thanks mate...
Click to expand...
Click to collapse
If your contacts were set to sync with Google or your carrier, then they will sync back to your phone after you flash. Given you were on Froyo, you can grab one of the Froyo ROMs from the bible (http://forum.xda-developers.com/showthread.php?t=1117554). Those will likely be rooted, deodexed, or something along those lines. If you want pure stock, you can grab that from samfirmware.com. You'll have to register to navigate to the firmware, though. I'd post a link but it wouldn't work right. Just go to the 'mobile' link and look for the SGH-T959V stuff. Either way, KD1 was the latest Froyo out there from Samsung.

Yup... I'll check on samfirmware.com..
sad abt contacts cuz dint sync the latest ones with google...
anyway i'll try the other method...
thanks..

Sorry man. Best of luck to you. Let me know if you get it fixed.

hi stephen_w,
I downloaded the T959VUVKD1 firmware from samfirmware.com....
I used odin to flash it...
after switchin on the phone in download mode... i flashed the firmware by browsing the file in PDA and leaving PIT, BOOTLOADER, Phone and CSC blank...
the process started and after cache.fs... below it was message:Complete(Write) operation failed.... it stopped nd showed fail in red...
i held the power key for a long time but then it started to show a phone linked to the computer with a yellow exclamation sign...
what does this mean?? im not able to boot into either recovery or download mode now...
please help...

ODIN will still see it when it looks that way, so don't fret! I had similar issues before but mine was a faulty download. Try using this one. It's not 100% stock as it's been deodexed, but it should work:
http://www.multiupload.com/7L5YDG8X8V

Ya im downloading tat one... Odin is detecting nd working... so i guess re-flashing should do the trick...
Jus to confirm I should leave fields other than PDA blank rite?

Yes, PDA only & let ODIN decide what should be checked.
Sent from my SGH-T959V using XDA App

Up and running jus like b4...
Thanks bro...

No worries; glad you're working again!

[Q] Samsung Stellar Verizon SCH-I200 Stock Firmware

So I accidentally bricked the new Samsung Stellar and my backups got wiped during the process.
Can anyone find the stock firmware/kernel for the Samsung Stellar?
Much appreciated.

sovereign73811 said:
So I accidentally bricked the new Samsung Stellar and my backups got wiped during the process.
Can anyone find the stock firmware/kernel for the Samsung Stellar?
Much appreciated.
Click to expand...
Click to collapse
mines isnt bricked but im looking for the same thing. Deleted some stuff I shouldnt have and no getting system ui force close. Let me know if you have an luck. Ill do the same

Do you still have the stock recovery? I may be able to get into my old OS if you can get the stock recovery pulled off.
Unfortunately I'm not sure how you will extract the recovery ROM off of your phone...I'll keep looking around.

mcarrion78 said:
mines isnt bricked but im looking for the same thing. Deleted some stuff I shouldnt have and no getting system ui force close. Let me know if you have an luck. Ill do the same
Click to expand...
Click to collapse
I'm curious, have you reinstalled the pesky stock apps to see if the OS crashes would stop? There may be something to that.
Also I possibly can help you get an image but I need a recovery image. If you're still rooted, download this:
http://android.podtwo.com/romdump/
Download Terminal Emulator from the Google Play Store and then follow these instructions:
http://forum.xda-developers.com/showthread.php?t=1771347
If I can get back into my phone by restoring the stock recovery, I may be able to get you an image that works.

Uh...OK...feel free to; it keeps the topic up fresh on the first page! lol.
Anyways I managed to theorize that a recovery is all I need....dang, looks like that's both of us now eh?

Im still rooted. im trying to figure out how to pull the recovery myself to possibly help in building CWM for the phone. I know removing some stock apps is what caysed my force close i just dont know all of the ones i deleted. I didn't think to back any of them up

I've got something up there that should help you pull out the stock recovery as well.
Romdump should work and should not brick anything so please give it a try.
sovereign73811 said:
Also I possibly can help you get an image but I need a recovery image. If you're still rooted, download this:
http://android.podtwo.com/romdump/
Download Terminal Emulator from the Google Play Store and then follow these instructions:
http://forum.xda-developers.com/showthread.php?t=1771347
If I can get back into my phone by restoring the stock recovery, I may be able to get you an image that works.
Click to expand...
Click to collapse

used romdump and this is what i get. it leaves me a text file thats 2.46 know that cant be it
c:\SDK\platform-tools>adb shell
[email protected]:/ $ su
su
[email protected]:/ # /data/local/romdump
/data/local/romdump
Android ROM dumper v0.82b
(c)2011 Sebastian404
Device : IMM76D.I200VRALG4
Creating required files... cat: can't open '/proc/mtd': No such file or directory
Opening mtd table... Segmentation fault
139|[email protected]:/ #

mcarrion78 said:
used romdump and this is what i get. it leaves me a text file thats 2.46 know that cant be it
c:\SDK\platform-tools>adb shell
[email protected]:/ $ su
su
[email protected]:/ # /data/local/romdump
/data/local/romdump
Android ROM dumper v0.82b
(c)2011 Sebastian404
Device : IMM76D.I200VRALG4
Creating required files... cat: can't open '/proc/mtd': No such file or directory
Opening mtd table... Segmentation fault
139|[email protected]:/ #
Click to expand...
Click to collapse
That's complicated. It looks like you use ADB from your PC. I'm curious, is your phone stable enough to run the Romdump from the phone itself? You will need terminal emulator to do this.
There is also a method that just works for recovery and boot partitions (the ones I and a few others need). Take a look here and scroll down to the heading that says "Alternative Method If The Above Does Not Work:".
http://www.addictivetips.com/mobile...es-boot-recovery-and-system-partition-images/

i get the same thing using terminal on my phone

http://www.addictivetips.com/mobile...es-boot-recovery-and-system-partition-images/
Have you looked at this link? It even has an alternate way to use romdump.

I don't know if this has anything to do with what we need for a stock ROM but here's something interesting:
http://androidforums.com/elite-all-things-root/551775-well-lets-get-ball-rolling-11.html
Again to any of you who have a rooted Samsung Stellar, please help us with a Stock ROM image!

heres the verizon stuff you were looking for
https://www.dropbox.com/sh/chkru9gi16k9ar8/G-DHp6SgnD

Thanks, although we already have that and we got a phone fixed for it...too bad not mine.
Hey did you get the message? Here I'll post it again:
OK people: here's a tip I've received from an XDA developer expert:
Quote:
a quick and dirty explanation (need root)
Code:
dd if=/dev/block/mmcblk0p1 of=/sdcard/output.img
this will save the partition mmcblk0p1 to output.img
now, to determine what partitions are
on my device its:
Code:
ls -l /dev/block/platform/msm_sdcc.1/by-name/
but you're scheme and directory structure there might be a little different, so adjust accordingly
Longer Version:
http://www.darkyrom.com/index.php?th...with-adb.8059/

yeah i got that message and i got the output.img just havent uploaded it

What were you able to extract by chance?
If you could find a recovery partition, that would be great.

even in recovery its actually loaded to RAM and not mounted (this allows you to flash to it while in recovery)
do:
Code:
ls -l /dev/block/platform/msm_sdcc.1/by-name
(its msm_sdcc.1 on my device, yours may be different but it should be similar)
Click to expand...
Click to collapse
Another tip to extract and backup the stock recovery.

stock rom
hey so im reading the threads and i wanted to know some kind of update. Did people test out the stock rom yet? Any good news?

Yes, thankfully we've got them working (thanks invisiblek!) and I'll make a further update in a few hours.

Where is the thread for this at?
Has this been dropped all together? I was looking for some stock and/or stock-rooted roms for this thing. Any hope out there?