Related
Being that so many DEV guy's are crapping on ROM Manager should I be requesting a refund from the ROM Manager owners as I had purchased this a while ago and if it is no good then I want my money back for purchasing a flawed product. Thoughts?
Blackberrynomore said:
Being that so many DEV guy's are crapping on ROM Manager should I be requesting a refund from the ROM Manager owners as I had purchased this a while ago and if it is no good then I want my money back for purchasing a flawed product. Thoughts?
Click to expand...
Click to collapse
unfortunately I feel you won't get your money back...the refund terms are very specific and clearly outlined
the dev guys aren't crapping on it..it is crap
seriously though...coming from other devices..NO ONE uses it lol
I was shocked that so many around here don't know how to manually flash something from recovery
Blackberrynomore said:
Being that so many DEV guy's are crapping on ROM Manager should I be requesting a refund from the ROM Manager owners as I had purchased this a while ago and if it is no good then I want my money back for purchasing a flawed product. Thoughts?
Click to expand...
Click to collapse
It's not that it's a bad produce per-se, it's that it hasn't been updated to work with the Infuse correctly. For THAT reason most devs dump on it. The other related reason is that it's not really a necessity item. It's more a convenience that for most, becomes more inconvenient. ;-)
Is there a thread that gives the steps to flash a ROM without ROM manager. I got it but not really sure I could again.
msnyder said:
Is there a thread that gives the steps to flash a ROM without ROM manager. I got it but not really sure I could again.
Click to expand...
Click to collapse
Just about all the ROM download threads have instructions for you.
Boot into recovery, wipe what you need to wipe, tell it to install a zip, done.
It's not hard to do at all.
00mred00 said:
unfortunately I feel you won't get your money back...the refund terms are very specific and clearly outlined
the dev guys aren't crapping on it..it is crap
seriously though...coming from other devices..NO ONE uses it lol
I was shocked that so many around here don't know how to manually flash something from recovery
Click to expand...
Click to collapse
I actually learned how to flash manually first before trying ROM Manager. I just liked it because of the convenience. No real big advantage to using it over the manual method just more convenient.
This recovery every one is speaking of, could it be the one created by Koush? Personally. Rom manager has been a great asset to me. It's like any other peice of code. It won't always behave the same way across a broad range of device's. I have no knowledge of cooking roms or writing code, but is it really necessary to make thread just to flame something? If you don't like it don't use it.
My 2¢.
Sent from my SAMSUNG-SGH-I997 using xda premium
shadow65781 said:
This recovery every one is speaking of, could it be the one created by Koush? Personally. Rom manager has been a great asset to me. It's like any other peice of code. It won't always behave the same way across a broad range of device's. I have no knowledge of cooking roms or writing code, but is it really necessary to make thread just to flame something? If you don't like it don't use it.
My 2¢.
Sent from my SAMSUNG-SGH-I997 using xda premium
Click to expand...
Click to collapse
Everyone uses Koush's Clockworkmod Recovery. The problem is that ROM Manager insists on using a crippled version of Clockworkmod ("green" CWM) that doesn't play nice with Voodoo Lagfix.
The problem is that instead of accessing whatever recovery the system comes with, ROM Manager insists on going to an "alternate" recovery (known as "green" CWM) which is crippled compared to the recovery included with almost all alternate kernels. Green CWM used to flash on any device with active Voodoo Lagfix = softbricked phone. It creates way too many support requests to developers, and also there's the issue I previously stated where downloading ROMs through ROM Manager causes people to go to ROM threads and not read the first post.
As to "if you don't like it, don't use it" - I don't, neither do any of the other devs. But other people do and we get all sorts of ridiculous support requests because of people who are too lazy to read threads on XDA, they want their ROMs spoonfed to them with ROM Manager.
Thanks for expanding my knowledge on the subject,
Sent from my SAMSUNG-SGH-I997 using xda premium
Apex rom
Hey everyone, question for you.
I'm running the Apex Rom and when I play my music, I can't forward or pause the music and when I try to forward or pause it, it FC.
Is anyone running this rom and don't have any problems playing music?
any feedbacks will be appreciated. Thx
Just wondering if anybody saw this. Here's a link for everybody to check out.
http://community.developer.motorola...-2-development-resources-available/td-p/19569
Sent from my MB865 using Tapatalk
tylercarter said:
Just wondering if anybody saw this. Here's a link for everybody to check out.
http://community.developer.motorola...-2-development-resources-available/td-p/19569
Sent from my MB865 using Tapatalk
Click to expand...
Click to collapse
Yeah, unfortunately it is not the source code yet, just the parts for the emulator and pieces needed for Devs to write apps specifically for the Atrix2.
I wish there was more there for us to use to get this thing cracked open. Hopefully we can get a ROM developer to jump in here soon and help us collect what they need to get started on ROM development. Although we will need someone like Th3ory who is not afraid of making ROMs for devices with locked bootloaders, because I have a feeling it will be after ICS before we have an unlocked bootloader.
An emulator as in a full emulation of our phone? So if one were to try to develop a ROM for this thing could that be used to test rather than risking a brick?
jimbridgman said:
Yeah, unfortunately it is not the source code yet, just the parts for the emulator and pieces needed for Devs to write apps specifically for the Atrix2.
I wish there was more there for us to use to get this thing cracked open. Hopefully we can get a ROM developer to jump in here soon and help us collect what they need to get started on ROM development. Although we will need someone like Th3ory who is not afraid of making ROMs for devices with locked bootloaders, because I have a feeling it will be after ICS before we have an unlocked bootloader.
Click to expand...
Click to collapse
Jim I'm curious. What recovery are you using? Bionic bootstrapper? And is it safe yet? I've read on it a little. Is it one of those things where unless your a bit of a dev not to try it?
Sent from my MB865 using Tapatalk
@PeteSeiler2010:
Yes this could be used to test a Developed ROM, however until we get a hold of some kind of code for this thing, there can't be too much development of ROMs and such, unless someone knows something I don't. And "code" can be anything from an fxz to the released source code for the Atrix 2 build.
@tylercarter:
For a "Recovery" this is the one you want, link below. And yes it is not 100% yet, but it does what we need it to right now, the only issue is if you crash, you can't get back to it on boot, you have to use the bootstrap to boot into it, from your app drawer. This is again something that can be done after a bootloader unlock. This will allow back up and restores though.
http://forum.xda-developers.com/showthread.php?t=1346977
----EDIT----
I use the emulator for a lot of the work I have been doing to see what will happen, without risking a screwup on my phone directly. Then once I have tested it out there, on the phone it goes. You can even test apps from the market as well, just to see. It is really for app developers, to do their testing of the apps they build, but we can also do something similar for our "hacking".
Thanks for info Jim, I am going to download it and check it out and see if there is anything I do with it.
Also, Jim, have you done many restores on your phone? I have been hesitant to try one...its just so risky without the sbf.
PeteSeiler2010 said:
Thanks for info Jim, I am going to download it and check it out and see if there is anything I do with it.
Also, Jim, have you done many restores on your phone? I have been hesitant to try one...its just so risky without the sbf.
Click to expand...
Click to collapse
Not a FULL restore, but there are others who have tried one of the updates in the bootloader unlock forum, that have been able to restore back to before the update successfully.
I have restored files, and even directories, but not the whole thing yet.
It looks like we need to come out with a new OTA base, some of the newer ROM's threads are being closed. Also, there is rumor that some devs are getting banned for posting ROMS's based on original OTA in RootzWiki. Being very new to this whole thing I can help, I attempted to make my my own but ended up rooted and S-ON (fixed now).
In any event I reverted back to stock, no root, did the OTA upgrade (what originally caused be problems since it updated HBOOT to 1.08). I was able to root it and do a backup. Now I am back to S-OFF and rooted, so I want to see what we can do with the backup, as far as I know the boot.img is the missing link. The one that came with OTA ICS installs 1.08 HBOOT (f5e16f3f55ddfb0ec10c8f9a75b35bed boot.img) which is not good.
I think we should create a completely open source version of the OTA and allow anyone and anybody to customize it as they see fit. Let's face it the TBolt lifecycle is at it's end so those of us that are left should work together.
Danm that sucks, I was wondering what was going on.
I love your idea, if I knew anything about this stuff I would help. When I saw the threads were locked for that reason it annoyed the hell out of me. What happened to Android being open source like its supposed to be.
Sent from my ADR6400L using xda premium
Nevermind I see whats going on here. I read Santod040 post in the other thread and he makes some valid points. I wish I could help tho.
I agree with Santod040 as well that is why I am doing this. I will probably not be able to do this all on my own, mostly because I have been basically an ROM end user. By the time I learn all I need to build my own ROM I will hopefully be on another device.
You have to do a system dump using adb. I'm not 100% certain but it may have to be done before it is altered. In other words 100% stock ota.
Sent from my ADR6400L using Tapatalk 2
Good idea!
I also wish I knew more. My simple successes have so far been related to theming of icon color in Browser.apk including some simple string edits, and custom colored or fully transparent LATIN_IME.apks.
I already have Ubuntu on a dual boot PC and Eclipse, and also have an updated SDK, but some 'clif notes' to get me started would be helpful. I've browsed around before and read many threads all over.
I like the idea of us all joining up to see what we can do!
The command for that should be listed with the other adb commands when you type adb in a terminal. You will need tools for splitting the boot.img as well since to make the ota a flashable you will have to package the boot.img in a zip.
Sent from my ADR6400L using Tapatalk 2
disconnecktie said:
The command for that should be listed with the other adb commands when you type adb in a terminal. You will need tools for splitting the boot.img as well since to make the ota a flashable you will have to package the boot.img in a zip.
Sent from my ADR6400L using Tapatalk 2
Click to expand...
Click to collapse
Isn't HBOOT packaged with the boot.img? For the backup that I did I have all that. What is the difference between doing a backup and doing a system dump with adb?
I finally found OTAUpdate.zip, I am going to dissect that and see what I can come up with. I was just about to downgrade and redownload the otaupdate.zip, saved me some time.
The nand is different because it isn't flashable the same way that a rom is. Theoretically you could upload the nand and people could use that to get the base but it just isn't the typical practice. It is better to have a flashable zip. The otaupdate.zip is not like a normal file especially since the update is a whole lot of patches that have to be applied to the stock gb base. That is why it took santod almost a day to assemble it into a flashable zip.
Sent from my ADR6400L using Tapatalk 2
Yeah it's sad it comes to this though. The community is who loses out in the end. As long as someone isnt profiting off your work I dont see what the problem is with them kanging it. Dev's are all supposed to have the same goal here, enrich the community with roms. They only do it because they are generous and enjoy helping out, especially a dying community such as the Thunderbolt. We need as much dev support as we can get, no matter where it comes from. If your goal is to help the community then you should be happy that they are enjoying your work, it's not like we dont know where the stuff comes from anyway.
Look guys just use the Unlock your bootloader on ICS Method, Get root, Install the recovery, backup the rom. Copy the backup from /clockwork to computer. Zip it and send to me. All we need is the System partition. The rest we will find
disconnecktie said:
The nand is different because it isn't flashable the same way that a rom is. Theoretically you could upload the nand and people could use that to get the base but it just isn't the typical practice. It is better to have a flashable zip. The otaupdate.zip is not like a normal file especially since the update is a whole lot of patches that have to be applied to the stock gb base. That is why it took santod almost a day to assemble it into a flashable zip.
Sent from my ADR6400L using Tapatalk 2
Click to expand...
Click to collapse
I see FOTA in OTAUpdate, I am assuming that is where HBOOT is being updated. That is what I was planning on doing, getting last GB RUU and manually running the scripts to come up with OTA. But the boot.img is what I don't understand, it seems the various boot.img is various ROM's are different (having different MD5's), are these built?
Guys can we please cut out the name calling and puerile acrimony?
I know that development can be a passion, but we need to work out our differences peacefully and sublimate our passion into development and this verbal venom.
As of right now let's cut out the nonsense, I am going to clean the thread up a bit and attempt to get some specifics, then we can discuss the issues without resorting to flaming.
ViperZ28 said:
I see FOTA in OTAUpdate, I am assuming that is where HBOOT is being updated. That is what I was planning on doing, getting last GB RUU and manually running the scripts to come up with OTA. But the boot.img is what I don't understand, it seems the various boot.img is various ROM's are different (having different MD5's), are these built?
Click to expand...
Click to collapse
Again I'm not 100% certain but i am sure that the new hboot is needed to assemble the ota because the patches in the ota are encrypted and the hboot decrypts those patches and assembles them.
Sent from my ADR6400L using Tapatalk 2
orangekid said:
Guys can we please cut out the name calling and puerile acrimony?
I know that development can be a passion, but we need to work out our differences peacefully and sublimate our passion into development and this verbal venom.
As of right now let's cut out the nonsense, I am going to clean the thread up a bit and attempt to get some specifics, then we can discuss the issues without resorting to flaming.
Click to expand...
Click to collapse
You see who started it. If he wants to troll n call people out he should expect a reply. As long as I've been here and been in this community I've never had to give reports to mods over a user. He should learn to control his mouth and he wouldn't get a Ill mannered response. He thinks he's all perfect then after all the fight gladly advertises and sends you to infected ROM forums and continues to get away with it. He's lost the respect of many over this one.
Sent from my DROID BIONIC using Tapatalk 2
---------- Post added at 09:28 PM ---------- Previous post was at 09:26 PM ----------
And good job deleting my post but leaving his up. Tbolt community on xda i'm sorry. But you just flat lined. Enjoy
Sent from my DROID BIONIC using Tapatalk 2
[SP]JESTER said:
You see who started it. If he wants to troll n call people out he should expect a reply. As long as I've been here and been in this community I've never had to give reports to mods over a user. He should learn to control his mouth and he wouldn't get a Ill mannered response. He thinks he's all perfect then after all the fight gladly advertises and sends you to infected ROM forums and continues to get away with it. He's lost the respect of many over this one.
Sent from my DROID BIONIC using Tapatalk 2
---------- Post added at 09:28 PM ---------- Previous post was at 09:26 PM ----------
And good job deleting my post but leaving his up. Tbolt community on xda i'm sorry. But you just flat lined. Enjoy
Sent from my DROID BIONIC using Tapatalk 2
Click to expand...
Click to collapse
I am going to leave this post here to make a point.
The fact is that you too should learn to control your own "mouth" (or keyboard as it were).
This isn't about who is right or wrong, I honestly don't even know what is going on at this point as I am still trying to figure exactly what the problem is, but this is not the place to go off like an atomic warhead about whatever is going on here. If you allow someone to bait you into these types of remarks, then you are giving that person control over your emotions and your reactions and you then take on the role of villain.
Whatever is going on you can PM a mod or get it sorted out through proper channels, some of our mods and Admin are developers and know the stuff inside out, they can sort out who is actually the instigator here.
End of discussion on this please. PM me if you still have issue. I will figure out what is happening and act on it.
Be civil, I refuse to believe that that is beyond your or anyone else's ability.
RunNgun42 said:
Yeah it's sad it comes to this though. The community is who loses out in the end. As long as someone isnt profiting off your work I dont see what the problem is with them kanging it. Dev's are all supposed to have the same goal here, enrich the community with roms. They only do it because they are generous and enjoy helping out, especially a dying community such as the Thunderbolt. We need as much dev support as we can get, no matter where it comes from. If your goal is to help the community then you should be happy that they are enjoying your work, it's not like we dont know where the stuff comes from anyway.
Click to expand...
Click to collapse
It could be looked at as a dev is getting donations off another devs hard work. So basically he or she is profiting off another's work. It's always best to ask another if they can use their work. I know liquid went through this with cm team. If a dev doesn't ask and just uses another's work. They should expect to get a nastygram from the dev who did the work. Free or paid stealing work is still stealing.
Sent from my ADR6425LVW using Tapatalk 2
Aghhh, can we get back on topic....we need to create a new OTA base.
I own a One SV. I'm on Jelly Bean. I successfully rooted it via the newest superuser apk and twrp. But when I try to remove ANY file under /system (including apps) using Titanium Backup it require reboot device, after a reboot or battery run out it is mystically restored and apps installed removed either. But if I restart without mentions above it ok!!! Where the hell do the files come from? I've searched the entire phone memory but couldn't find anything. Have I missed something?
Search this forum for my posts and keywords system write protection
I have answerd this question 20 times and more.
old.splatterhand said:
Search this forum for my posts and keywords system write protection
I have answerd this question 20 times and more.
Click to expand...
Click to collapse
Thanks appreciate, I really unknown which cause come from and how to solve this issue because it's my friend device so I must post an question. I also have had some quick search but still out even through your reply with keyword suggestion
tnfsmith said:
Thanks appreciate, I really unknown which cause come from and how to solve this issue because it's my friend device so I must post an question. I also have had some quick search but still out even through your reply with keyword suggestion
Click to expand...
Click to collapse
The reason the apps are returning when you've rebooted your phone is because your not s-off I would recommend using rumrunner.....
Sent from my *super modded* HTC one SV ......
Xceeder said:
The reason the apps are returning when you've rebooted your phone is because your not s-off I would recommend using rumrunner.....
Sent from my *super modded* HTC one SV ......
Click to expand...
Click to collapse
If you flash a boot.img which has a modified kernel for write protection being removed then that too will also resolve the issue and thus S-Off wouldn't be necessary, but of course, going S-Off only makes it better and more convenient.
Modding.MyMind said:
If you flash a boot.img which has a modified kernel for write protection being removed then that too will also resolve the issue and thus S-Off wouldn't be necessary, but of course, going S-Off only makes it better and more convenient.
Click to expand...
Click to collapse
Hhhmm you learn something new everyday , and just want to say I think you are very clever I've seen the posts you've done on XDA and I'm a big fan just one little question is the modified boot.img file available on XDA for the one sv or would it have to be created , I don't need it I'm just curious I'm already s-off ......
Sent from my Nexus 7
Xceeder said:
just one little question is the modified boot.img file available on XDA for the one sv or would it have to be created , I don't need it I'm just curious I'm already s-off ......
Sent from my Nexus 7
Click to expand...
Click to collapse
Hard to say. Back when this device was a bit more active I would tell you, yes, but as of now that is a different story. Links could be bad but if you check old.splatterhands thread where everything needed to know about this forum is compiled then you may find that answer you are looking for.
With that said, it also depends on which K2 device you have. It's important that the correct kernel be used since they have their differences internally.
However, it is very easy to take the kernel source, remove write protection from it's source, then compile the kernel into a binary and apply it to your device. This is usually the approach I take for my own personal development and gain.
https://github.com/ModdingMyMind/an...mmit/c34ea02e20b758e78cae9f8b8bc975d268accd84
If you take a look at that link I just shared you will see the changes I made to the kernel source regarding the K2_CL (Boost Mobile) variant. Everything in green is what was added so the kernel would have Selinux support and everything in red is what I deleted to remove write protection from the kernel.
https://github.com/ModdingMyMind/an...mmit/86a317157a741ef12042426696e3c84eeed3e263
This next commit shows the changes I made to the kernel source for disabling Module Support so that when I make a new build with a new version number the kernel binary will work with the devices old modules thus saving me the hassle of building new modules and replacing the old with the new. More of a convenience in my opinion. Not many people disable module support for some reason which is why you will hear a lot about people flashing a new boot.img/kernel binary and then their WiFi breaking. It's usually the result of the kernel version not matching the old modules which prevents them from working properly or at all.
That is very informative , thank you for your time and knowledge.....
Sent from my Nexus 7
Xceeder said:
That is very informative , thank you for your time and knowledge.....
Sent from my Nexus 7
Click to expand...
Click to collapse
No problem. I still own the K2_CL. Wanting to get a new phone but until Boost offers something worth my interest I will continue to use this device as my primary. The phone has been out a long time now and is falling behind in the Android World but nevertheless, it is still a great phone and I use it for most of my Android Development projects since I don't always have time to sit in front of a computer.
I have the European version and yeah they are good phones they don't sell them anymore here in the UK , I'm trying to get into android development myself but I think its a bit too hard , I read once on the internet that the best way to learn to code is to first find a fault or something you'd like to change in an app and look at the code so I'm going to keep researching and obviously looking at posts from professionals such as yourself ......
Sent from my Nexus 7
Wondering about root doesn't seem we are getting much development on our u11 life
twinnfamous said:
Wondering about root doesn't seem we are getting much development on our u11 life
Click to expand...
Click to collapse
Wondering the same thing or maybe it take time to get us root...it was easy to unlock bootloader for me no problem...but twrp is a no good on T-Mobile U Life[emoji22] as of right now for me anyway
Sent from my HTC U11 life using XDA-Developers Legacy app
The lack of releases at this time is probably related to this phone being less than ten days old.
iamxaq said:
The lack of releases at this time is probably related to this phone being less than ten days old.
Click to expand...
Click to collapse
Exactly haha. Not sure why people are jumping the gun on development for this phone already. My Moto g5 plus took longer than this from its initial release to get development going. And now that phone is very active in the community.
Anyway, point is, just give it some time like this guy said. The phone isn't exactly a flagship anyway. And the Android one version hasn't even been released here yet.
dpryor88 said:
Exactly haha. Not sure why people are jumping the gun on development for this phone already. My Moto g5 plus took longer than this from its initial release to get development going. And now that phone is very active in the community.
Anyway, point is, just give it some time like this guy said. The phone isn't exactly a flagship anyway. And the Android one version hasn't even been released here yet.
Click to expand...
Click to collapse
thanks for the comments. how long have you been in the developer scene with HTC. Also nobody is jumping the gun. We aren't allowed to go to devs and ask for eta's so I just made this thread so they may see and hopefully give some love to this phone. All I need is root and a recovery I can do the rest.
Look on the bright side, pixel 2 been out for a month. And even we are slow on development. You'll get root and probably a few roms, it will take time though.
Also the fact that bootloader is unlockable when phone cost less than $400 is kinda big deal
twinnfamous said:
thanks for the comments. how long have you been in the developer scene with HTC. Also nobody is jumping the gun. We aren't allowed to go to devs and ask for eta's so I just made this thread so they may see and hopefully give some love to this phone. All I need is root and a recovery I can do the rest.
Click to expand...
Click to collapse
I could ask you the same question. If you've been in it so long yourself, why don't you figure this problem out yourself? Hah.
dpryor88 said:
I could ask you the same question. If you've been in it so long yourself, why don't you figure this problem out yourself? Hah.
Click to expand...
Click to collapse
Very well put. I only usually get the flagship HTC phones but this time I chose this since it was T-Mobile specific. And I waited to long to get u11 so using this till next HTC flagship comes. I look forward to seeing you around.
HTC phones from my experience don't take too long to get root. They average about a month or so. Keep in mind my last HTC was the EVO LTE.
You don't need a custom recovery for root.
You can use Magisk to patch a stock boot.img for your device (for example, one found here) and flash the patched image via fastboot. Then you're rooted, and you didn't even need TWRP.
I won't be purchasing this device, so unfortunately I can't build a TWRP for it (that and I'm retiring in 8 posts). If someone else wants to pursue building it, I'm willing to offer minimal assistance.
Captain_Throwback said:
You don't need a custom recovery for root.
You can use Magisk to patch a stock boot.img for your device (for example, one found here and flash the patched image via fastboot. Then you're rooted, and you didn't even need TWRP.
I won't be purchasing this device, so unfortunately I can't build a TWRP for it (that and I'm retiring in 8 posts). If someone else wants to pursue building it, I'm willing to offer minimal assistance.
Click to expand...
Click to collapse
Thanks so much for the info. I'm on to something now. About building it what can I use as a pre-built kernel or will I have to wait for source to drop? Sorry for using your last posts to help us
twinnfamous said:
Thanks so much for the info. I'm on to something now. About building it what can I use as a pre-built kernel or will I have to wait for source to drop? Sorry for using your last posts to help us
Click to expand...
Click to collapse
There's a thread on xda about building TWRP. I've never built TWRP before, but I know about using build environments and whatnot. Google "how to build TWRP" I believe haha, as simple as it sounds it should come up in the top few results.
Anyway, I think you and I should help each other out here like you said. I'm using an older imac since I sold my old PC. It only has 4gb ram, but I'm going to install Ubuntu tomorrow on the Mac as a partition, and then hopefully I can get a build environment going quickly and start work.
What are you doing so far? Are you able to build too? Or maybe we can both research and bounce ideas off each other while I try it out. Whatever you prefer. Just PM me I guess.
dpryor88 said:
There's a thread on xda about building TWRP. I've never built TWRP before, but I know about using build environments and whatnot. Google "how to build TWRP" I believe haha, as simple as it sounds it should come up in the top few results.
Anyway, I think you and I should help each other out here like you said. I'm using an older imac since I sold my old PC. It only has 4gb ram, but I'm going to install Ubuntu tomorrow on the Mac as a partition, and then hopefully I can get a build environment going quickly and start work.
What are you doing so far? Are you able to build too? Or maybe we can both research and bounce ideas off each other while I try it out. Whatever you prefer. Just PM me I guess.
Click to expand...
Click to collapse
I can build I have a great machine and all ready downloaded the source. The only difference in building twrp for a new device is we have to make our own files from scratch. And it would be nice if we had an ruu to restore back from if things don't go well during testing. We can figure it out. Help is always good more people trying different things usually gets results faster.
twinnfamous said:
I can build I have a great machine and all ready downloaded the source. The only difference in building twrp for a new device is we have to make our own files from scratch. And it would be nice if we had an ruu to restore back from if things don't go well during testing. We can figure it out. Help is always good more people trying different things usually gets results faster.
Click to expand...
Click to collapse
I read somewhere about an emulator sorta program for testing your TWRP build without messing up your device.
twinnfamous said:
I can build I have a great machine and all ready downloaded the source. The only difference in building twrp for a new device is we have to make our own files from scratch. And it would be nice if we had an ruu to restore back from if things don't go well during testing. We can figure it out. Help is always good more people trying different things usually gets results faster.
Click to expand...
Click to collapse
Did you try that magisk rooting (without TWRP) method? I haven't tried it yet.
---------- Post added at 11:56 AM ---------- Previous post was at 11:50 AM ----------
Captain_Throwback said:
You don't need a custom recovery for root.
You can use Magisk to patch a stock boot.img for your device (for example, one found here) and flash the patched image via fastboot. Then you're rooted, and you didn't even need TWRP.
I won't be purchasing this device, so unfortunately I can't build a TWRP for it (that and I'm retiring in 8 posts). If someone else wants to pursue building it, I'm willing to offer minimal assistance.
Click to expand...
Click to collapse
Happen to know where there may be stock boot.img files for the Life that are free? I don't want to pay for a membership on that site you linked..
dpryor88 said:
Did you try that magisk rooting (without TWRP) method? I haven't tried it yet.
---------- Post added at 11:56 AM ---------- Previous post was at 11:50 AM ----------
Happen to know where there may be stock boot.img files for the Life that are free? I don't want to pay for a membership on that site you linked..
Click to expand...
Click to collapse
that's gonna be the hard part. Finding a boot.Img for T-Mobile version. There's no links to software anywhere that I've seen. We may be stuck waiting for an update just to get the files we need
twinnfamous said:
that's gonna be the hard part. Finding a boot.Img for T-Mobile version. There's no links to software anywhere that I've seen. We may be stuck waiting for an update just to get the files we need
Click to expand...
Click to collapse
Yeah I think we're at a road block right now
dpryor88 said:
Yeah I think we're at a road block right now
Click to expand...
Click to collapse
I'm not giving up I'm still gonna try whatever I can on my end.
Hopefully something good or I'll end up with a bricked device till ruu comes
I would love to eventually see a ROM that gives the T-Mobile variant a similar appeal as the Android One version. I bought the U11 Life as a backup to my Pixel 2 (and to benefit from T-Mobile's Carrier Freedom promo, as well) and I was very surprised as to how much I actually enjoyed using the phone!
Brought me back to the days when I had the One M7.
Just so everyone is aware...... Once you unlock your bootloader you can then go super CID, once you are super CID you can flash ANY GSM boot.img , so there is no roadblock on that end. The roadblock is no custom recovery, if we had a custom recovery then we are open to a world of wonders and amazement. So get to work......