[ROM]Wintergreen
- Thread starter GPOT
- Start date
This is a disaster! I hope I didnt brick anyones phone! You can odin back to stock in case I did. I will post an Odin image ASAP.
Sprint releasing Gingerbread update for Replenish. That was unexpected... I thought they dead ended my phone. If I did brick anyone's phone. I am sorry and you probably should have read the system requirements on the OP: they said untested on 64 bit. I personally have had no success on flashing this rom to my phone. It worked for my brothers because he was running a 32 bit OS, but it hasnt worked for me. I have everything but the build.prop though so that was pretty successful. For those that have been successfully using this rom, I will have a gingerbread version released within a week of me getting this update from sprint. The new rom will be GINGERBREAD.EK18 based.
For anyone who may have had a problem with this ROM/Flasher, please check back to the OP for instructions on how to fix your phone.
Now that I have obtained the Gingerbread update - thanks firehak - I will start work on version 0.2. You may have seen mention of a so called 0.2 earlier in this thread but I ran into a problem with the flasher and that is that it doesnt like to update. It sends the phone into a boot loop because it doesnt replace the right files and instead duplicates them. Version 0.2 will be up as soon as I write a new flasher, which could take anywhere from a day to a few months. If you cant wait for gingerbread, restore your phone to stock with the instructions in the original post. Update to EF27, and then update to EK18 or see the gingerbread update thread to download the zip. Finally, sprint did something good with this phone!
Hey GPOT - gonna be hard to create a ROM without root access to the phone. No way to get all the files off of the phone to create the ROM from. Also won't be able to get the file on in the right way. Unless you know of a way to root this thing, we are dead in the water.
With some exploits such as zergRush being open sourced, I'm sure someone will figure something out. I believe Shabby told me there was no way zergRush would work for a Replenish the way it is written, but it's only one in a million exploits all over the place. I've had no success rooting either, whether on the home screen or in recovery mode.
No it doesnt work, never mind
Last edited:
Actually using xUltimate I was able to dump the files off of the phone just fine. The problem is getting them back on
Xultimate can not dump an entire image of your phone. Just some directories. In lieu of rooting, we need a full dump of the phone (kernel and all) so that someone more skilled than I can hack it into a rooted rom. Unfortunately this dump seems impossible to create with root :-(
What about the dd command on linux. U don't need rw permissions to download the files from the phone.
You need to run the DD command on the phone in a terminal shell (or through ADB shell). And since we don't have read permits to all the directories, we won't get all the data. And when you connect via USB, you only get access to the files on the SD card. You can also use ADB PULL to get files on the actual phone, but again, not from the directories that we don't have read access to. So we are still unable to get all the data off the phone.
I noticed I have some ability to read into a few directories that I probably shouldn't have when browsing in file expert, but I'm by no means rooted. I took a look around a noticed that I still have su, superuser, my busybox installation, etc.
Yeah i noticed that too. The only thing that doesnt work is some programs like wifi tether and I cant su from the adb shell.
The update did not delete that stuff - correct. However the kernel is booting in a mode that does not allow permissions for us to run su, which is in effect what needs to happen for us to get super user permissions in any linux environment (android runs on linux). The fact that the update did not delete those files may be of some use to us. I am investigating if there is a potential to go back to a pre GB state (I believe this can be done with the odin files we have on this forum), and re-root the phone. Then, find an exe loaded on the phone that we know will be left intact post GB update, and that we know will be called post GB update, and that we know will have root access when run. We then modify the source code for that program to give us root access on GB. Re-update to GB, and there we have it.
The problem with this approach - I don't know if there is such an exe that exists. If there is, and if there is SRC code for it, I can modify it to do that we need. I just don't know if it exists.
If anyone has time to ODIN back to pre-GB, this may be of service later.
The problem with this approach - I don't know if there is such an exe that exists. If there is, and if there is SRC code for it, I can modify it to do that we need. I just don't know if it exists.
If anyone has time to ODIN back to pre-GB, this may be of service later.
If the kernel is "booting" into a mode that does not allow super user, and android is based off of the linux kernel, then why couldnt you interupt the kernel boot process and select a certain mode like you can on linux?
If you could do that, then you have found a new exploit. When the kernel is first loading, you don't have any access to the phone. ADB is not yet operational. The only control we have over the boot process is holding down U while powering up (for recovery) or Space+P while powering up (for download mode). I am not aware of any other control we have.
Then it looks like we have some experimenting to do. I am posting from my phone right now so I can't do some research but look into key combos on other phones and see what they do and we can try those keys plus any other possible combos. Just so we know in what ways we can interupt the kernel.
Similar threads
Trending Posts
-
Did anyone get the new silicone case from Samsung?- Started by ansa82
- Replies: 7
-
-
-
-
Facebook
Twitter
Instagram