Can TWRP 2.x, specifically 2.5 since its the latest, be compiled for the glacier/myTouch 4g? if so, is there any reason it hasn't been? since 4ext is old now (runs like a champ, but still), and realistically the 4ext guy might not continue support for it going forward with his upcoming rebuild of 4ext.
The TWRP team says they're "interested" in the device anyway...and their code is open.
I'm potentially willing to try doing it myself, but i'd have to set up an environment and all that. it'd be easier if a dev who has it all set up to make it (not trying to add to their workload or anything, just being realistic)
anitgandhi said:
Can TWRP 2.x, specifically 2.5 since its the latest, be compiled for the glacier/myTouch 4g? if so, is there any reason it hasn't been? since 4ext is old now (runs like a champ, but still), and realistically the 4ext guy might not continue support for it going forward with his upcoming rebuild of 4ext.
The TWRP team says they're "interested" in the device anyway...and their code is open.
I'm potentially willing to try doing it myself, but i'd have to set up an environment and all that. it'd be easier if a dev who has it all set up to make it (not trying to add to their workload or anything, just being realistic)
Click to expand...
Click to collapse
Old? The last update was a few weeks ago.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Why do you care how new the recovery is? If it ain't broke, don't fix it. I am pretty sure i am still rocking RC3. Flashes roms just fine
Related
Yea, a ship s-off unit.
How long before root?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Full size pic attached below.
Ok. I know its not as high profile as the Evo3D or Sensation but it was released at a similar time and hopefully has similar exploits that I will test tomorrow. (or as soon as work allows).
Feel free to comment as I will add to the first post any new details.
Use any random rooting tool like superoneclick(usb) z4mod(phone) or gingerbreak(phone) if you have s-off
Sent from my Milestone 2
The Xtc clip now supported chacha.
Rooting is made easy for everyone then, just run any of the apps I mentioned above. Being S-OFF means the device is able to run custom recoveries as well. Could any s-off user contact me? I'll try compiling a recovery for you all to test.
Mikevhl said:
Rooting is made easy for everyone then, just run any of the apps I mentioned above. Being S-OFF means the device is able to run custom recoveries as well. Could any s-off user contact me? I'll try compiling a recovery for you all to test.
Click to expand...
Click to collapse
Any Luck Guys???
Guys, looking for a clean ROM with no telco pre installed software in it, in order to free up some ram and space. Tried downloaded pocket god.apk but seems like not enough ram to run the game. haiz...
hope the dev team can help out this little cute phone.
i don't have any S-Off.
Is it possible to Port this Rom to our Device?
[2.3.8][OFFICIAL][BUILD #7]CyanMobileX
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
[GitHub]CyanMobileX
I was reading the specs of that device and, well it is not a very powerful device either.
Also I was reading the post and it says that the rom runs smoothly in that Phone
and i was wondering how it would Run in ours.
~ Any answers are appreciated
Thanks.
My quick look at it is that it is a Gingerbread ROM. If someone wanted to spend the time, it could probably be made to work.
Big "if" on that one, in my opinion, for a GB ROM. There are already several solid, stable, and well-proven GB ROMs out there for the SGS4G.
jeffsf said:
Big "if" on that one, in my opinion, for a GB ROM. There are already several solid, stable, and well-proven GB ROMs out there for the SGS4G.
Click to expand...
Click to collapse
GB roms are the funnest to modify (for this phone, anyways).
bhundven said:
GB roms are the funnest to modify (for this phone, anyways).
Click to expand...
Click to collapse
They are!, they're the most stable and well, battery Life is still the best on GB for this device in my opinion
Im gonna give it a try and see how hard is to port this to our devices Xp
Well, speaking of GB... I've started on yet another cleanup kernel, except this time I'm getting some help from jeffsf.
Gonna post something in development here soon.
I had My HTC One S working fine with an unlocked bootloader, CWM Recovery, and CyanogenMod 10.2. One day, I get a notice that there's a system update, so I thought, hey that's cool, over the air updates for CyanogenMod. So I do it and now when it boots it looks like this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
With some difficulty, I was able to get into the bootloader then into CWM. I cleared everything and re-flashed the original CyanogenMod ROM, but it still does this when it boots. It also does not appear to turn on properly. Does anybody know what's going on here?
polybius said:
I had My HTC One S working fine with an unlocked bootloader, CWM Recovery, and CyanogenMod 10.2. One day, I get a notice that there's a system update, so I thought, hey that's cool, over the air updates for CyanogenMod. So I do it and now when it boots it looks like this:
With some difficulty, I was able to get into the bootloader then into CWM. I cleared everything and re-flashed the original CyanogenMod ROM, but it still does this when it boots. It also does not appear to turn on properly. Does anybody know what's going on here?
Click to expand...
Click to collapse
Your link doesn't work.
I also cannot see any picture of your screen, but I think you mean freaky colours on your screen.
This is due to updated display drivers some time ago on CMs side.
Which means if you use a newer ROM, you also have to use a newer kernel to get the correct colours back.
If you are S-On your kernel won`t be updated by just flashing the firmware, you have to fastboot the kernel afterwards.
Is it possible to port kitkat from One mini? The same hardware phone with the exception of resolution.
@Modding.MyMind
Oh yes it is, but the only thing is we do not have an active kernel dev.....that's the most important thing when porting is complete.....without kernel port also, the ROM might be a perfect port but the the kernel will not allow it to boot or connect data or bla bla bla....
Totally possible port, if we had a kernel developer that didn't have a real life with school, work, ladies.....Lol
Kernel is the same for both devices.Some config files differ and a few drivers.The most important thing is a right ramdisk.Thats all what we need.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Full report
https://drive.google.com/file/d/0B9DrEEiA1eKRb1lvQkxjS2R3enc/edit?usp=sharing
Definitely possible if provided with the proper kernel. Only problem is the resolution. Would require going through all the apps and a lot of files and then resizing them for our resolution. That can take a very long time to do.
I dont agree.We could stay on our sense 5. And edit new kernel only.Maybe resize a few files in /APP
I think its not difficult to make it.
Cause we dont get KitKat its only one and simple variant to make it.
Modding.MyMind said:
Definitely possible if provided with the proper kernel. Only problem is the resolution. Would require going through all the apps and a lot of files and then resizing them for our resolution. That can take a very long time to do.
Click to expand...
Click to collapse
Not so long.. In 1-2 hours it will be done.
xpirt
And where it is?
rollon76 said:
And where it is?
Click to expand...
Click to collapse
I don't think he was talking about doing it himself, but in general terms.
Sent from my C525c using Tapatalk
Hey everyone,
I have this issue with my device hopefully you know something about it: a while ago I rooted it, got Magisk on it all that. The device was just out so updates were still coming strong--or maybe I payed more attention to them than I do now, IDK--the case is that I accepted one of them and it undid the root and updated MIUI to something-something, regardless, since then I'm unable to flash a recovery image.
I thought the partitions got messed up or something and flashed the official system with the official Xiaomi spyware/adware suite "tools" hoping it would rewrite what needed rewriting then I tried flashing the recovery (TWRP) but no luck.
I'm using the XiaomiADBFastbootTools Java applet. It seemingly flashes the thing successfuly then it boots right into the system again, not in recovery. If I use force a recovery reboot through adb or with the buttons (which I've already forgot which were) the recovery the comes up is the official one, not TWRP.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Every time finishes "successfully", then the device reboots taking just tiny bit longer then I see the MIUI logo with the sort of paint-spill animation covering it and then I'm back on stupid Mars again (the stock pseudo-interactive wallpaper). Not even my information is lost--not that I'd want to, but at least it'd be something.
Since I removed most bloat the phone became pretty much useless and I wasn't even thorough because there's stuff that just can't be removed. Rooting would allow me to get some utility back out of it. Can it be fixed at all??