Hallo guys,
So first of all, I know "why didn't you bought the hardware from the manufacturer you like" blabla. I love the S6E but what I also love is the HTC software. So my question, is IT eventually possible to port completly a manufacturer Rom?
I found some Tutorials and also trying them out right now. But have also some concerns about a hardbrick or eventually a complete phone kill. How possible might this scenario be? If we assume I port everything properly?
Thanks in advance :good:
seitzik said:
Hallo guys,
So first of all, I know "why didn't you bought the hardware from the manufacturer you like" blabla. I love the S6E but what I also love is the HTC software. So my question, is IT eventually possible to port completly a manufacturer Rom?
I found some Tutorials and also trying them out right now. But have also some concerns about a hardbrick or eventually a complete phone kill. How possible might this scenario be? If we assume I port everything properly?
Thanks in advance :good:
Click to expand...
Click to collapse
Hi seitzik
Thanks for asking.
There are some software portions you won't be able to handle as they intensively interact with the hardware you have, which harware itself isn't portable
Modem & Booloader you probably wont be able to mess with in anyway.
Recovery & Kernel can be customized indeed but not as far as from an alien Manufacturer.
EDIT: The above pieces of software are the ones that could lead to a brick so be careful.
What leaves you with System ( / <- root and forward). Within system there are a LOT (I mean it ... a lot) of binary libraries that interact directly with devices sensors and their absence would, at least, disable its functions.
The other way around would be true ... HTC apps would require their own libraries that would not find the associated hardware necessary to work properly.
IMHO, seems I huge and painful endeavour.
EDIT: if one were interested in the looks of HTC, there are some launchers over there that could bring it closer to you.
But, as it seems, you already dressed XDA T-Shrit "DIY" and, as so, please keep us updated.
Have fun.
.
Thank you very much for your reply!
Related
Is possible use Android Rom from HTC Tattoo? In the future. Ofcourse. Becouse hardware is similar as hardware from touchcruise.
No way!
Greetings
why?
could you please elaborate "no way"? What is the obstacle? I am sure may of us would love to see Iolite with Android.
Thanks
atsamoulis said:
could you please elaborate "no way"? What is the obstacle? I am sure may of us would love to see Iolite with Android.
Thanks
Click to expand...
Click to collapse
because porting android needs a lot of rewritting the drivers and how to speak to youre phones hardware
and even the great phones like my blackstone dont have android running
and they are trying to acomplish that for over a half year now
and many other huge phones dont have a working android for there phone
and it arnt that many people here with the iolite so i think we dont have programmer how can make it for us ive it would ever be accomplished on other phones
best regards
miniterror
I don´t can better say this.
Greetings!
HI!
Sorry for stupid questions...but I dont understand why someone should write new driver? Hardware are (almost) the same. Why you can't use tattoo's drivers without changing?
Best Regards!
Andraz
well its like putting diesel in a benzine car
its booth fuell but will brick if you take the wrong one for youre car
You have a kind of alternative called Androkidd.......http://forum.xda-developers.com/showthread.php?t=540428
See if you like it....
Sharp has made a pretty nice Keitai-style Android phone: sh7218u , but has crippled the OS only to run chinese apps. (They call it DimSim)
What would be the best way on approaching a potential "uncrippling" of this software.. and installing a full blown Andorid on it ?
All suggestions welcome, (I don't wanna hear any "buy a HTC instead" replys) 'cause they don't make clamshell androids)
Thanks ,
The Keitai'ist
bump for you! Would like to know this as well.
Rooting software available.
Found a WHOLE bunch of software for the Sharp 72xx on a Chinese BBS, PM me for files... & guides
Anybody has more info on functioning of the SH7218U outside China, namely in EU? Been thinking about this phone as my second (private phone), I'll be able to order one from China in August... Is it worth the hassle and the risk?
Thanx
Alright everyone, I'm in love with this phone, anyone feel the same? Well, you're about too.
Here's a link to install and enable Gapps, use a translator if ya want.
http://modiako.blogspot.com/2011/05/sharp-sh7218u-android.html
Also, anyone familiar with the SH-01B? And it's really nice-looking big clock for the external display? I have the files for making yours look like that as well. Just PM me if ya want. Or just get it from this link.
http://www.msharp.cn/forum/t356876/page1/
Oh yeh, z4root roots this device fine btw.
Now, I don't really know how to read Chinese well so Ive gotten all this info from lurking Chinese forums searching for keywords or just finding these because of others. So, if anyone can help me out with translating this link I'm about to give, ALOT of helpful things will result since it's basically a thread on SH7218U optimization.
http://www.mobile01.com/topicdetail.php?f=525&t=2175932&last=30798785
Also, if you check out this vid, http://www.youtube.com/watch?v=rmTf300BhpI ,this guys SH7218U is modded so the notification and virtual android buttons have a different look to them. I asked the guy and this is what he said, "It is similar to how to modify the status bar is other android phone (which you can search from google or XDA forum), but the tricky part is instead of modify the frame-res.apk. you do the modification on dianxinos-res.apk". Now that seems simple enough but I can't find any guide on HOW to do this, and him not replying any further didn't help me out.. SO yeh, if anyone can read/write Chinese lets look up on how to mess with the SH7218Us framework.apk and dianxinos-res.apk, as for now Ide rather not mess with those important files without a clear English guide.
So let's try and get something going here possibly maybe perhaps?
Lamenting over my hard-bricked SGP 4.0, a pretty naive thought occurred to me, that is, what if the so-called internal SD card really is a "card" and can be replaced? Of course not, but I had to see it myself, so I just disassembled it and took some photos of the internals. SGP 4.0 US is pretty easy to disassemble, I guess, and here are a few photos (with S/N airbrushed). My hardware assembly experience is back in early 90s, so it won't apply to modern day assembly technologies at all, but it looks like the Toshiba is the internal SD memory chip (wonder why Samsung uses Toshiba flash chip for its memory?). I didn't peel off the sticker, but the chip under the white sticker looks like the CPU. Near the presumably Toshiba flash chip, there does seem to be a socket for an external programmer, so I guess if I can get this to a service center (like in Korea), I guess they might be able to reflash the internal flash memory chip using their programmer device, but it's purely my totally naive imagination. Anyone have some comments? Anyway, enjoy!
Also, I didn't want to start another thread for this, but I'm wondering if anyone could point me to the right direction about the ICS port going on in the development board for SGP 5.0 US? I'm not sure if it's intentional or not, but I'm finding that the dialer is missing there (is it that ICS totally is without a dialer? I doubt so), and seeing a player like SGP as a VoIP device, I think it's still important to still have a dialer. I can't yet post a question there as a noob, so I'm wondering if someone could see this and convey this comment to the developers there. I'd also love to try tinkering with the sources, build the rom image and try those with my SGPs. I'll probably first try to do it with ambrice's CM7 for SGP 5.0 US, and if I can get any assistance or advice from anyone, I'd greatly appreciate it. Thanks for all your great work!
Nice post! But sorry to hear that your player got hard bricked.
I have noticed that you have both versions if the players. If you truly have no use for your 4.0 anymore, maybe you could consider donating it to a dev who specializes in hardware (like adamoutler or someone else?)? I'm sure he or someone else could make good use of your device, and maybe possibly even prevent your situation from happening to someone else in the future with an unbrickable mod. Or maybe some experienced dev could unbrick it and come help with the ics progress... We certainly do need all the devs we can get.
Again, this is just a suggestion; I hope I didn't sound selfish or anything.
Sent using Tapatalk 2 Beta 4.
klin1344 said:
Nice post! But sorry to hear that your player got hard bricked.
I have noticed that you have both versions if the players. If you truly have no use for your 4.0 anymore, maybe you could consider donating it to a dev who specializes in hardware (like adamoutler or someone else?)? I'm sure he or someone else could make good use of your device, and maybe possibly even prevent your situation from happening to someone else in the future with an unbrickable mod. Or maybe some experienced dev could unbrick it and come help with the ics progress... We certainly do need all the devs we can get.
Again, this is just a suggestion; I hope I didn't sound selfish or anything.
Sent using Tapatalk 2 Beta 4.
Click to expand...
Click to collapse
I'd be happy to follow your suggestion (and you don't sound selfish at all), but unfortunately the device is not my personal property, not at my disposal... Sorry... Maybe I should revive my old-days hardware experience and try to make some contribution with this... Thanks.
Hello guys,
So first of all, I know "why didn't you bought the hardware from the manufacturer you like" blabla. I love the S6E but what I also love is the HTC software. So my question, is IT eventually possible to port completly a manufacturer Rom?
I found some Tutorials and also trying them out right now. But have also some concerns about a hardbrick or eventually a complete phone kill. How possible might this scenario be? If we assume I port everything properly?
Thanks in advance :good:
No because of alot of them are coded for the hardware and drivers built by the oem.
Thank you very much for your reply !
Hi everyone.
So I've been with this question in my mind for some time now... Are they really unbrickable? I have a ZTE Blade L3 on which flashed infinite times ROMs on it. Some completely bricked it - it couldn't even charge. It has a MT6582M processor on it. It was COMPLETELY bricked. And I always got it to work again. Never bricked it for good - and I did many stupid things on it, many experiments. And after a bit, SP Flash Tool would always flash stuff back to it even by flashing wrong ROMs on it.
I also believe I flashed a wrong ROM to a friend's Elephone P8000 B which has a MT6753 processor on it. I thought I had bricked it (this is why I think I flashed a wrong ROM on it) - but SP Flash Tool got back working after a few tries. I did what I wanted with the phone and it didn't brick.
So my thought is that ANY device with a MediaTek chipset with a ROM and a scatter file available and an always unlocked bootloader (preferably - as my Blade L3 had, I believe - since I never heard of this until weeks ago), might be unbrickable. I, supposedly, can do whatever I want on it and I'll always be able to unbrick it.
Is this true what I just wrote? If it is, then I'll try to never leave MediaTek powered devices.
Note: A thread confirmed this thought I had for some time until I found this thread, but it only says it about MT65xx devices, not all the others: https://forum.xda-developers.com/showthread.php?t=1943442 --> "Added on Nov 23, 2012 - MT65xx is truly UNBRICKABLE".
Note 2: Also....... After now reading back a bit of the thread, I found out I did exactly ALL the opposite they recommend there in caps and the phone always unbricked....... XD. So I'm a bit confused with all the careful people are about MediaTek powered devices when I was not careful (stupidly, I know), though it always worked. I have the phone since 2015 and stopped using it last year, but I believe I did the opposite of those things, even though I'm not completely sure. And again, never permanently bricked.
Thank you for any informations!
I'm not going to lie to you, your probably not going to get any other replies to the book you wrote above... I will answer your question however. There is not a single mobile device out there that cannot be unbricked as long as the issues that occurred to cause said brick remains at the software level. It don't matter what brand or carrier it is. If it is a software related issue then it can be fixed as long as you have the knowledge and tools required to do so. As for your experimentation using root, I have done many experiments myself and there are many many things you can do using root that will permanently brick your device. Sounds to me like you got lucky. Simple as that. I'll end this by saying, please do not post your entire relationship with your favorite phone in a single thread like you did. Nothing personal but many probably did not stay long enough to finish what you wrote. You have a valid question. However the rest was just unnecessary and to many, a waste of their time. Hope I helped.
Hi. I didn't even remember about this anymore. This last year I was told I write too much unnecessary things - just like you did. I've been trying to correct that and I believe I improved (no idea if much or not). When you said "the book you wrote" I got embarassed in advance because I knew what was going next, and when I scrolled up I got scared and even more embarassed and it's still increasing as I think more about it . Christ, how did I even post that. I'm very sorry........ I guess we learn as time goes by.... (hopefully haha). Hopefully now it's good enough. If it's still bad, I'll be happy to receive the advice, as I am with the one you gave. Thank you. For everything you said, actually.
Spoiler: Not needed, just curiosity of why I wrote it so big
EDIT: Just a small explanation of the why I wrote the text so big, which was I'd prefer to give all the informations right at the start so people can know exactly what was done and say things according to that. Instead of assuming I did things I might not have done and answer something that might not be correct in my case. But then I write a book and that's beyond stupid. So I've been trying to correct that. That's the wrong point of the view and I think I still need a bit more time, but hopefully I'm getting there - maybe I should start posting on Reddit hahaha. Posting things is not that old for me. Started a few years ago (21 years old - a bit late for my age, I guess, but I didn't go on Internet that much before).
My intent was not to embarass you. I apologize. I should have checked the date this was originally posted. I do hope i was able to answer your question though. That was my true intent.
Tofor said:
My intent was not to embarass you. I apologize. I should have checked the date this was originally posted. I do hope i was able to answer your question though. That was my true intent.
Click to expand...
Click to collapse
Ah no problem at all. Gotta be corrected in some way . That happens with me when I see an enormous stupidity made by me which I did not realize at the time - and this one is 5 months old, which puts it worse haha.
That shall work so I won't forget of not doing this again in the far future xD. Before, some people would tell me about and I'd notice it was a wall of text (like once a person told me). And I appreciate all those who warned me about it. Sooner or later I'll get to a decent amount of text, depending on the forum. I think I didn't know what a paragraph was, as a start xD (though, what you saw there was already an update....). It's still a big post, I think, but hopefully it's readable now. If it's not, I'll cut more of it.
But yes, you did answer the question. Thank you. But to complement it, if you remember, at least, what experiments with root can completely brick a phone? (So I know I won't try them, as a start, but it's also a curiosity.)
Well a good example of some things not to do is changing the system files to allow the device to operate at a level it was not designed to operate at. For example. Messing with the kernel to make the processor run at a higher speed, same goes for the RAM. This will cause it to overheat and will basically fry the system board. Also if you are not sure what you are changing then dont change them. Nothing like accidently changing the EFI settings to where it no longer knows where the internal storage addresses are and does not know it has any type of storage to boot to. However a lot of the efi should be copywrite protected where even a root user cannot modify them but trust me... its possible and may still be repairable but only by the manufacturer who has that level of access and definitely not worth what it would cost. Keep an eye on any files you modify for a copywrite at the top of the file. Changing copywrite files will most likely get you in a whole lot of trouble. If you end up having a web adress listed in the build.prop on every android device you own that brings you to the developers terms and conditions then stop messing with system files. This is more or less a warning telling you that you are breaking the terms and conditions. I would libe to continue but then i would be contridicting myself on my comment about very large messages in the forums. If you would like to know anything else please feel free to PM me and lets put an end to this thread lol.
Guys, speaking of devices with MT chipset, I have a Hannspad HSG1341 that was running Android 5.1 and wanted to root the pad using some tutorial I saw with magisk by installing the APK on this device which creates a modified boot.img. Then using SP Flash Tool I tried to reinstall the stock firmware by replacing the boo.img created by magisk and now the pad would not power on, I have tried searching for means to restore this pad but nothing. Even SP flash tool is now displaying s_ft_enable_dram failed (4032). So please off anyone has any idea how to resolve or is the pad dead for good. The chipset is MT8163. Let me know if you need more info to help out
thanks