B70/B80 unrooted? Let's Donate to the Devs! - Eee Pad Transformer General

Nevermind, it's DONE!
http://forum.xda-developers.com/showthread.php?t=1345049
---
Hi people,
I've seen many people like me, sad to know after buying this great device that it is as up this moment "unrootable" and therefore cannot be customized with custom ROMs and custom Kernels. Most of them on this thread.
I exchanged this message with brk the dev responsible to the topic:
brk said:
FabricioGS said:
@brk
Just out of curiosity, what do you and other developers need to unlock the bootloader? Do you depend on sources from Asus/Nvidia or is just plain basic reverse engeneering and testing?
I don't want to put pressure or anything like that, just trying to understand why SBK v1 is possible to bypass/ or open and the new one is not.
Click to expand...
Click to collapse
The dev who made this rooting method is working in breaking the new SBK, the major problem that he and his team have is that they don't own a B70 or B80 with new SBK Asus eee pad transformer, so it's difficult for them to test things since they don't have where to test them. They aren't going to buy a new transformer just to find a way to root, they are trying to find some kind of solution.
The lastest news is that it seam that the old nvflash binary doen't work with the new sbk, they are trying to modify the binary so ti can work with new sbk.
Click to expand...
Click to collapse
After his response I decided to create a thread to help the devs buying a new Transformer with the new SBK v2 so they can help us all. Please consider that they are trying hard to do it but they lack of a current device to test and debug it (here http://androidroot.mobi/2011/10/03/...r-yet-another-post-about-the-current-state/):
RaYmAn said:
No, we haven’t given up or: Yet another post about the current state
Hi, been a while since our last post…
Rumors are starting to surface that indicates that we have given up on working on this. This is by no means the case. We are still hard at work. Things are definitely taking longer than expected.
There is one main issue:
The BootROM in B70+ devices has been bumped to a newer revision. Nvflash works by sending a miniloader to the device, which then handles receiving the actual bootloader.bin. The miniloader included in current nvflash binaries appears to crash well before the bootloader.bin is sent.
So, how do we move on?
Well, I hate to say it, but I really need to get my hands on a new SBK device (B70 or B80). Bricked is OK. As long as APX mode works over USB, it’s ok. Heck, even a broken screen is OK.
Requirements:
- Cheap
- APX Mode works
- Within EU
- Can charge ok
- Cheap
There’s no requirement that any accessories are included. I already have a B50 TF with working charger.
Click to expand...
Click to collapse
So please, let's unite and DONATE TO THEM!!!!
Let's help the devs so they can help the community!
Here's the link to their donation page: http://androidroot.mobi/donations/
I'll organize a list here so we can see all donators.

While I'm sure they appreciate the sentiment, rayman has said that he doesn't like the idea of a donation fund in one of the comments on the latest androidroot.mobi post. (I can't post links yet)

^ he's right. said he'd rather borrow one then accept donations. good try though
ahh here it is: Per Rayman
"While I appreciate the idea of setting up a donation fund, it’s not really realistic. Even if all the money came in, taking donations for specific things in advance creates expectations. I’m fairly certain we can crack this, but who knows what issues might arise as we get further.
Wrt. borrowing, that’s probably the best solution. Getting people to execute code is too complex to be a viable solution.
If any of you danish guys offering to lend me a b80 lives in the copenhagen area shoot me an email at rayman android root.mobi"

Keep 'em coming
I am the recipient of a lovely, un-rootable B70 and I donated a few bucks to show my support (5 bucks, ain't much, but if we got a LOT of those small donations, these guys can make things happen.) It's like the price of a sandwich, you know? It's not too fair to ***** and moan that you got a raw deal, and then expect someone else to solve your dillema.
Come on, if you need the devs to make things possible, and you have no technical contribution, at least donate waht you can. It could mean the dif between waiting 2 more moths, or actually seeing this soon.

Well.. even if they do not want it, it's certainly a good incentive anyways.. I think it wont hurt them right?

FabricioGS said:
Hi people,
I've seen many people like me, sad to know after buying this great device that it is as up this moment "unrootable" and therefore cannot be customized with custom ROMs and custom Kernels. Most of them on this thread.
I exchanged this message with brk the dev responsible to the topic:
After his response I decided to create a thread to help the devs buying a new Transformer with the new SBK v2 so they can help us all. Please consider that they are trying hard to do it but they lack of a current device to test and debug it (here http://androidroot.mobi/2011/10/03/...r-yet-another-post-about-the-current-state/):
So please, let's unite and DONATE TO THEM!!!!
Let's help the devs so they can help the community!
Here's the link to their donation page: http://androidroot.mobi/donations/
I'll organize a list here so we can see all donators.
Click to expand...
Click to collapse
Hi folks, the idea seems fair to pay , if only to make the effort ... and that I do not often donate but because he deserves the wonderful EEPAD deflowered! apple bottom! good health to the dedicated decoders and greetings to everyone ..

Related

[OFFER] Functional A500 available to borrow for reputed devs.

OK, here is the skinny which I hope wont be deleted by the mods.
Due to bad luck circumstances I currently have two devices, Both legal, no stolen devices or what have you. Basically one was dropped and the digitizer (not the scren itself) crackedin one corner, Despite this the device t works like a charm, the areas where ghe digitizer is torn react to touch input perfectly.
I have warranty on that that covers this incident for another ten months. Realistically in insurance terms the device is shot and needs replacement, They will ask for send in and keep it.
My hope / vision is that some developer, preferably on the european mainland could use a experimentation device to pull the stunts that might endanger his asset. If The device goes brick it is not a loss any more than before. I benefit from developers work and rooting attempts for a long time now and I hope that this is something I can gice back to the community to speed up the process of pwning the bootloader.
You can keep it up to three months.
Please enquire by PM or comment here. (BTW if you are sketched about a first poster with an offer like this, I frequent the forum more often under different nicknames.
Great! Should be a sticky!
Sent from my A500 using Tapatalk
Tweet @paulobrien and see if he wants to have a look at it? Or maybe try and get in touch with him some other way.
Budadank said:
Tweet @paulobrien and see if he wants to have a look at it? Or maybe try and get in touch with him some other way.
Click to expand...
Click to collapse
Thats quite a splendid idea. I hate Twitter but I know where to look for him in IRC.
Although if there are still any other takers let me know...
well..
in the desire community there is snq- which is very talented in the modifying kernel and files...
u can contact him.. may be he is willing to help us

Assemble Dev Team for an ICS ROM

As our device is dying in support I feel that we need to develop a large development team (10+ people) that will work on ICS for our gtablet. I mean after all our device is capable of running it ( Tegra 250). If you would like to be part of this team shoot an email to [email protected] explaining why you want to be part of this team and what you can contribute. Thank you.
You know that you need a new kernel for ICS to work properly right? Ch3vr0n5 and dpw13 are currently working on it over at slatedroid.
lol. i was gonna post something similar to this in the next couple days. I made the n1 ics port and started work today trying to get ics booting on my gtab. I think first order of business is to start a room on freenode.
#tegratab_ics_dev
all interested parties please join
btw im drewis
texasice said:
lol. i was gonna post something similar to this in the next couple days. I made the n1 ics port and started work today trying to get ics booting on my gtab. I think first order of business is to start a room on freenode.
#tegratab_ics_dev
all interested parties please join
btw im drewis
Click to expand...
Click to collapse
guys,
pm jazzruby, tek112 or fosser2, ch3vron..they are also over @ slatedroid viewsonic gtablet forum..
they have been working on a kernel with hw accel for HC3.2 and ICS. There are been some teaser pics by fosser with ics running on his gtablet.
I'm sure they could use your help...
kernel dev in the gtablet laboratory forum as well.
Cyanogen: Our goal is to provide continued support to all CM7 devices back to the QSD8250 series of devices such as the Nexus One. (12/2/2011)
Click to expand...
Click to collapse
The CyanogenMod team has also said they will continue to support our gTabs so I am looking forward to CM9 which hopefully will drop some time in January.
sjmoreno said:
The CyanogenMod team has also said they will continue to support our gTabs so I am looking forward to CM9 which hopefully will drop some time in January.
Click to expand...
Click to collapse
uhm based on what you quote nothing is said there we dont have qsd in our gtabs...
If anyone is interested and has dev experience shoot me a pm and i'll get you up to date. thanks
Yea upon further investigation there are already a few people working on this. In fact a quick google search will find you a booting cm9 for gtab. (i dont want to post the link since it is pre alpha and not my rom) but the gtab is not lacking devs by any means. (they just arent on xda)
oh and forget my post about the irc room there is already one. but again you must find it yourself
dont know why the pic is green but whatever
texasice said:
Yea upon further investigation there are already a few people working on this. In fact a quick google search will find you a booting cm9 for gtab. (i dont want to post the link since it is pre alpha and not my rom) but the gtab is not lacking devs by any means. (they just arent on xda)
oh and forget my post about the irc room there is already one. but again you must find it yourself
dont know why the pic is green but whatever
Click to expand...
Click to collapse
I appreciate that you didn't post the link to this, and please anyone else who "finds" this build (yes its out there) please do not post it anywhere either. It is extremely beta and has many problems (to the point where you would have to open your tablet to push the internal reset button). Thanks
i really don't appreciate this elitist dev crap. "yeah there's a place where you can talk about it, and a build you can get to try it, but i'm not going to tell you where." i completely understand that the devs are doing work that we (I) can't do and that they're entitled to a bit of leeway for that but if they're going to talk about their work in public and post shots, they're just doing it to get a rise out of people. there is no valid reason to restrict people from trying out alpha builds except to keep others out of their club.
of course, if you want to install something against the advice of someone who knows a lot more than you do, that's your perogative but you assume all responsibility. it does absolutely make sense that the devs want ZERO whining or "bug reporting" from alpha builds. ostensibly, the devs and those with technical acumen are trying to protect newbs who might fry their tabs. to my thinking however, nothing would make someone learn faster not to flash random **** than a $300 brick. we're all intelligent humans and not children, however, so
links:
cm9 alpha (install script edited)
gapps
original file
note: THIS IS NOT A DAILY DRIVER. i tested it on a 1.2BL tab. i had to turn off the getprop script asserts to get it to install, which is usually bad form. it boots, but we have no hw acceleration, no wifi, no camera, no sound, no usb storage or adb... etc. this is just a taste, proof that work is being done.
irc is freenode #gtab_kerneldev
Notion ink adam is getting official ICS, I suppose that will help a lot?
iammuze said:
i really don't appreciate this elitist dev crap. "yeah there's a place where you can talk about it, and a build you can get to try it, but i'm not going to tell you where." i completely understand that the devs are doing work that we (I) can't do and that they're entitled to a bit of leeway for that but if they're going to talk about their work in public and post shots, they're just doing it to get a rise out of people. there is no valid reason to restrict people from trying out alpha builds except to keep others out of their club.
of course, if you want to install something against the advice of someone who knows a lot more than you do, that's your perogative but you assume all responsibility. it does absolutely make sense that the devs want ZERO whining or "bug reporting" from alpha builds. ostensibly, the devs and those with technical acumen are trying to protect newbs who might fry their tabs. to my thinking however, nothing would make someone learn faster not to flash random **** than a $300 brick. we're all intelligent humans and not children, however, so
links:
cm9 alpha (install script edited)
gapps
original file
note: THIS IS NOT A DAILY DRIVER. i tested it on a 1.2BL tab. i had to turn off the getprop script asserts to get it to install, which is usually bad form. it boots, but we have no hw acceleration, no wifi, no camera, no sound, no usb storage or adb... etc. this is just a taste, proof that work is being done.
irc is freenode #gtab_kerneldev
Click to expand...
Click to collapse
I realize you're just trying to show people where it is, but if the devs don't want you pouring out THEIR work to the world just yet, I think it's best to listen.
iammuze said:
i really don't appreciate this elitist dev crap. "yeah there's a place where you can talk about it, and a build you can get to try it, but i'm not going to tell you where." i completely understand that the devs are doing work that we (I) can't do and that they're entitled to a bit of leeway for that but if they're going to talk about their work in public and post shots, they're just doing it to get a rise out of people. there is no valid reason to restrict people from trying out alpha builds except to keep others out of their club.
of course, if you want to install something against the advice of someone who knows a lot more than you do, that's your perogative but you assume all responsibility. it does absolutely make sense that the devs want ZERO whining or "bug reporting" from alpha builds. ostensibly, the devs and those with technical acumen are trying to protect newbs who might fry their tabs. to my thinking however, nothing would make someone learn faster not to flash random **** than a $300 brick. we're all intelligent humans and not children, however, so
links:
cm9 alpha (install script edited)
gapps
original file
note: THIS IS NOT A DAILY DRIVER. i tested it on a 1.2BL tab. i had to turn off the getprop script asserts to get it to install, which is usually bad form. it boots, but we have no hw acceleration, no wifi, no camera, no sound, no usb storage or adb... etc. this is just a taste, proof that work is being done.
irc is freenode #gtab_kerneldev
Click to expand...
Click to collapse
There are good reasons why the devs don't want this posted. Its not to spite anyone or rub it in their faces. 1 they don't want to be liable for someone elses damaged tablet, 2 do you know if the voltage regulators aren't correct it could fry your gtablet permanently, 3 they're a good hard working group who is doing this for zero dollars in their spare personal time and only want to put out a good working product. Have a little respect for their wishes. Be warned that alpha build could permanent damage your gtablet.
iammuze said:
i really don't appreciate this elitist dev crap. "yeah there's a place where you can talk about it, and a build you can get to try it, but i'm not going to tell you where." i completely understand that the devs are doing work that we (I) can't do and that they're entitled to a bit of leeway for that but if they're going to talk about their work in public and post shots, they're just doing it to get a rise out of people. there is no valid reason to restrict people from trying out alpha builds except to keep others out of their club.
of course, if you want to install something against the advice of someone who knows a lot more than you do, that's your perogative but you assume all responsibility. it does absolutely make sense that the devs want ZERO whining or "bug reporting" from alpha builds. ostensibly, the devs and those with technical acumen are trying to protect newbs who might fry their tabs. to my thinking however, nothing would make someone learn faster not to flash random **** than a $300 brick. we're all intelligent humans and not children, however, so
links:
cm9 alpha (install script edited)
gapps
original file
note: THIS IS NOT A DAILY DRIVER. i tested it on a 1.2BL tab. i had to turn off the getprop script asserts to get it to install, which is usually bad form. it boots, but we have no hw acceleration, no wifi, no camera, no sound, no usb storage or adb... etc. this is just a taste, proof that work is being done.
irc is freenode #gtab_kerneldev
Click to expand...
Click to collapse
Well aren't you cool, learning how to use google and ****.
EDIT: Ok now that I'm done fuming about this. The release that was posted is an early build of CM9. It is based off of Android 4.0.3. The kernel that is included with that release is linux 2.6.36. Since then, we have now moved onto 2.6.39. In no way is the "dev" group elitist. At any time anyone could have joined the IRC group and asked for a download link to the latest kernel/rom. The reason this has not been released yet is because of the "power button" script. When the power button is tripped at random times it causes the entire tablet to freeze up. The only way to "reset" the tablet is to open it up and press the internal reset button, thereby voiding any warranty from Viewsonic. Another issue that I have seen with using this kernel is possible damage to the camera. Just a few days ago I learned that while running this kernel the camera heats up and is hot to the touch, almost to the point of burning yourself. I have since then, unplugged the camera from the mainboard, to hopefully stop damage to the camera (I'm guessing that whoever has run this already without unplugging their camera, has potentially fried it). In short, installing this rom does give you some latest and greatest software to play with, but with it comes risks. DO NOT INSTALL THIS ROM/KERNEL IF YOU DO NOT WANT TO RISK DAMAGING YOUR TABLET.
ps. As a dev. team, we will be releasing HC with a .36 kernel that supports hw accel very soon. Keep your heads up for that release. Hopefully this release can hold people over until everything becomes more stable. Thank you all for patiently waiting.
fosser2 said:
Well aren't you cool, learning how to use google and
ps. As a dev. team, we will be releasing HC with a .36 kernel that supports hw accel very soon. Keep your heads up for that release. Hopefully this release can hold people over until everything becomes more stable. Thank you all for patiently waiting.
Click to expand...
Click to collapse
Kids.....they think they know everything! Haha, just kidding but hopefully maybe people understand why now. Im pumped about the HC release! Im tired of froyo and can't wait to play the THD games that required 2.3+. Thank you and the rest of the team so much for your hard work. Im not a programmer but im going to start digging for the technical info you need for the camera.
fosser2 said:
Well aren't you cool, learning how to use google and ****.
EDIT: Ok now that I'm done fuming about this. The release that was posted is an early build of CM9. It is based off of Android 4.0.3. The kernel that is included with that release is linux 2.6.36. Since then, we have now moved onto 2.6.39. In no way is the "dev" group elitist. At any time anyone could have joined the IRC group and asked for a download link to the latest kernel/rom. The reason this has not been released yet is because of the "power button" script. When the power button is tripped at random times it causes the entire tablet to freeze up. The only way to "reset" the tablet is to open it up and press the internal reset button, thereby voiding any warranty from Viewsonic. Another issue that I have seen with using this kernel is possible damage to the camera. Just a few days ago I learned that while running this kernel the camera heats up and is hot to the touch, almost to the point of burning yourself. I have since then, unplugged the camera from the mainboard, to hopefully stop damage to the camera (I'm guessing that whoever has run this already without unplugging their camera, has potentially fried it). In short, installing this rom does give you some latest and greatest software to play with, but with it comes risks. DO NOT INSTALL THIS ROM/KERNEL IF YOU DO NOT WANT TO RISK DAMAGING YOUR TABLET.
ps. As a dev. team, we will be releasing HC with a .36 kernel that supports hw accel very soon. Keep your heads up for that release. Hopefully this release can hold people over until everything becomes more stable. Thank you all for patiently waiting.
Click to expand...
Click to collapse
Thanks to all the Devs working on this stuff for us! That said if you guys need any testing done just shoot me a PM, I rarely use my tablet any more and have cracked it open plenty of times for other hardware testing. I don't have much time to work on software anymore, but am more than willing to test stuff for you if you don't wish to risk your tablets. Again thanks for all your work.
Sent from my Nexus S using XDA App
MOD EDIT:
FORUM RULES:
Encouraging members to participate in forum activities on other phone related sites is prohibited.
Off-site downloads are permitted if the site is non-commercial and does not require registration.
Closing this thread - this is just getting out of hand folks.

Tester

Just putting it out there that I would love to be a tester for the Galaxy SII, I have the original one, I have flash and went through 90% of every ROM up for it in both sections the original section and regular section, I just love flashing and going through Roms and would love to just help out someone with there Rom and do whatever it is they need me to do as far as testing, please hit me back. I hope I posted this is the right place if not, I will watch the Noob video 20 times in a row for punishment.
ah ok...... that's an idea
Original SGS II ? No kidding! :|
At first, I thought of this as just a pointless thread - but you got me thinking... What if we were to create a thread where people can nominate themselves as alpha/beta/etc. testers for ROM/Kernel developers? The difference lying in that to be eligible for a position, you'd have to prove that you have basic knowledge of how to recover from, for example, a bootloop, or a device that won't even boot, or constant FCs, etc. etc., along with again, pretty basic ADB knowledge, how to create and restore a NANDroid backup, and things like that. It'd come with the usual disclaimer stating that all responsibilities lie with the user, not the developer, and while the developer may be willing to provide support for bugs, etc., they are not liable for any damage resulting either directly or indirectly from the use of their software.
This would solve two things - it would satisfy those who just can't stand to wait for the release of something, who like to always live on the bleeding edge of development, and it would provide the developers a huge testing platform.
In review, though, this provides to main issues: 1) people would only be able to test one thing at a time, e.g. you're not going to be allowed to test a beta ROM with an alpha kernel, for example - it creates too many variables, and makes it harder for the developers to isolate and fix problems - but this shouldn't be an issue for people, just pick what you want and stick with it, and 2) people who leak the otherwise tester-restricted software for the masses - but this can be solved easily: maintain a list of official testers. Anyone who comes begging for support because they went ahead and flashed some leaked ROM/kernel/whatever, and ended up without a working device without being on the list, can be denied support for breaking the rules. Moreover, they, along with the leaker, could potentially face site-imposed bans?
I'll cut the rambling here, but I think it's a good idea?
As a ROM developer, its a great idea.
Sent from HydrOG3N MOD S2.
Technology Evolves, Android Evolves.
HydrOG3N is THE Revolution.
Thinking about it, not bad idea. But to back sceamworks up a bit, there should be a number of post limit, Some form of history for the dev`s to see who is a Noob (sorry Noobs) and who is not...
I'm in
Sent from my GT-I9100 using XDA App
I like the idea and I too would be glad to help people testing there ROMs.
It also seems nice to have a thread where people (like me or the OP) can set them self available for testing.
Most real developers pick their team from watching the threads and see how is willing to put the time in and know how to properly test as well as offer ideas on fixes. But not a bad idea I guess for new rom developers
lodger said:
Thinking about it, not bad idea. But to back sceamworks up a bit, there should be a number of post limit, Some form of history for the dev`s to see who is a Noob (sorry Noobs) and who is not...
Click to expand...
Click to collapse
I agree completely, I'd say 50-100 would be a fair starting point? I might PM some devs sometime soon with a proper proposal, and if I get a positive response from a majority of them, I might draft something, and get some official names on-board.
zelendel said:
Most real developers pick their team from watching the threads and see how is willing to put the time in and know how to properly test as well as offer ideas on fixes. But not a bad idea I guess for new rom developers
Click to expand...
Click to collapse
I considered this, and I think if anything brings the idea down, it'll be that - it's a hard sell to make, and I'd love to say that there's no harm in trying, but really, there is, so I guess execution is everything?
Good idea, im in....

Galaxy Note 10.1 2014 Exynos Developer Device

Hello everyone,
most of you probably don't know me since I did not develop for Samsung devices for quite some time now.
I would be interested in aiding the Exynos 5420 development scene (in particular on the Galaxy Note 10.1) and prepare a custom Android distribution for it (Team EOS 5.0 - Lollipop).
I can get all the required drivers and binaries I need for development, since most of it is open source luckily.
And the Nexus 10 (manta) can still be used as reference for many things.
All I need is a development device to debug on.
It is particularly important that this is the Galaxy Note 10.1 EXYNOS (WiFi-only variant), and not the LTE (Qualcomm) variant.
I created this thread to ask whether someone has a spare device lying around, maybe because of the little development on Exynos 5 devices, or if people would be willing to donate a device (I'm a university student and unfortunately can not afford the full price for a new device. I'm willing to dive into the Exynos development scene and spend time on this device though, including extensive debugging).
You can leave a reply in this thread or contact me on gmail: [email protected]
I have a better idea. Sending device is a problem. But we can donate to you, and then u can purchase P600 or P601 on SWAPA or EBAY. not new but fully working
I would be glad to see working AOSP/MAHDI or other ROMs runnig on my P601
Yeah, that was the initial idea.
I would pay any shipping costs or parts of a device (a used one is perfectly fine).
The issue I see is that probably not enough people willing to donate enough small amounts of money, hence I asked if someone had a spare device I could buy or pay the shipping costs.
RaymanFX said:
Yeah, that was the initial idea.
I would pay any shipping costs or parts of a device (a used one is perfectly fine).
The issue I see is that probably not enough people willing to donate enough small amounts of money, hence I asked if someone had a spare device I could buy or pay the shipping costs.
Click to expand...
Click to collapse
I think it would be better to ask for donations because there is not a lot of people here although it would be hard. There have been previous instances where at least 2 different devs raised donations for this device before stopping development shortly after so people do have some trust issues. It would take a while but i'm sure people would donate considering you are offering an AOSP experience. If you renamed this thread to something like: Donations needed for new device- AOSP rom development. Then it would catch a lot of eyes because that's what a lot of people want The question remains whether people would actually donate. The average cost for you would be around 250-300 euros I think. That means you would need around 28 people (10 each). Whatever way you decide to go down, I wish you luck and I look forward to any rom developments if you do manage to get the device :good:
You seem to have quite a respectable history (in both Rom & kernel developement), so I think getting enough donations should be doable (and I'd be willing to donate a few bucks myself)
But I do have a few questions:
1) What about warranty? Some devs who had collected donations for a (used) device, have bricked their devices -> no more developement
Therefore P600 owners might be scared / hard to convince
2) what exactly is "Team EOS 5.0" and what makes it different from other Roms? Would you perhaps consider developing other Roms / kernels as well? (like porting over PA for example?)
Or would you maybe consider becoming the official P600 CyanogenMod maintainer (since we don't have one, yet)? [<- I think this one would be reason enough to donate]
Last but not least:
You could ask one of the XDA members who managed the previous donation-collections for help (they have successfully done it before, so they might be able to do it again :fingers-crossed: )
PS: The Note 10.1 2014 is great for college, trust me - I'm a student, too . All you need is the Papyrus-App from the Play Store.
Thank you two for your reasonable thoughts.
I think the main reason why the previous developers stopped developing for this device rather quickly is the Exynos chip.
The main difference between me and anyone else is (or so I believe) the fact that I am especially interested in developing for the Exynos 5420 chip and the drivers for it (mainly from the Insignal forum source).
As far as bricked devices, I can say I had a Samsung device before, and as long as the bootloader is unlockable and access to ODIN (The firmware flashing tool) is granted, a hard brick is rather hard to achieve. I see little risk here, and I assume my previous development experience will prevent me from making major mistakes in that regard.
A new device would cost me approximately 350€, so if we could collect about 300$ with donations (which would equal something like 270€), I'd pay the remaining costs.
People are of course free to check my development history and/or references first and see if they think I would benefit the aosp development scene for this device.
The ROM I mentioned (Team EOS 5.0 lollipop) is essentially AOSP 5.0 with selected features that we code ourselves, like EOS Weather, or the NX gesture interface.
If people however see the need for an official CM maintainer, I'd be happy to become this as well, all I need is a device to debug and develop on, I'd be willing to spend the time to officially maintain this device.
Other developers and/or contributors should also expect support from me in areas of kernel development or AOSP custom ROM development. I believe in 'sharing is caring', so all my knowledge and achievements on this device shall benefit the community.
If some of you could maybe contact the people who raised donations before, I'd be thankful and gratious for the support. All donations will be listed here and the whole process shall be as transparent as possible.
RaymanFX said:
Thank you two for your reasonable thoughts.
I think the main reason why the previous developers stopped developing for this device rather quickly is the Exynos chip.
The main difference between me and anyone else is (or so I believe) the fact that I am especially interested in developing for the Exynos 5420 chip and the drivers for it (mainly from the Insignal forum source).
As far as bricked devices, I can say I had a Samsung device before, and as long as the bootloader is unlockable and access to ODIN (The firmware flashing tool) is granted, a hard brick is rather hard to achieve. I see little risk here, and I assume my previous development experience will prevent me from making major mistakes in that regard.
A new device would cost me approximately 350€, so if we could collect about 300$ with donations (which would equal something like 270€), I'd pay the remaining costs.
People are of course free to check my development history and/or references first and see if they think I would benefit the aosp development scene for this device.
The ROM I mentioned (Team EOS 5.0 lollipop) is essentially AOSP 5.0 with selected features that we code ourselves, like EOS Weather, or the NX gesture interface.
If people however see the need for an official CM maintainer, I'd be happy to become this as well, all I need is a device to debug and develop on, I'd be willing to spend the time to officially maintain this device.
Other developers and/or contributors should also expect support from me in areas of kernel development or AOSP custom ROM development. I believe in 'sharing is caring', so all my knowledge and achievements on this device shall benefit the community.
If some of you could maybe contact the people who raised donations before, I'd be thankful and gratious for the support. All donations will be listed here and the whole process shall be as transparent as possible.
Click to expand...
Click to collapse
Hi. Here's the most recent donation thread which was successful :good:
http://forum.xda-developers.com/showthread.php?t=2742793
I don't see why another thread is needed though. I don't mind opening one up for you but you might as well use this one if you just rename it and state your intentions in the op.
22sl22 said:
Hi. Here's the most recent donation thread which was successful :good:
http://forum.xda-developers.com/showthread.php?t=2742793
I don't see why another thread is needed though. I don't mind opening one up for you but you might as well use this one if you just rename it and state your intentions in the op.
Click to expand...
Click to collapse
Okay, so if maybe one of you guys, with good contact to the community, could open a new donatiion thread to collect the ~300$, I'd be grateful.
Or maybe @drrasii could chime in here and edit his first donation thread and link here as a reference to let people know what I want to do.
As I said above, I'd be willing to become the official CM maintainer, or if CM refuses to accept this for some reason, I'd host the needed sources for the device on my personal GitHub and keep it updated so people can build whatever ROM they want.
Of course, the first goal would be to get Lollipop running on this tablet, which I'd start with as soon as the device is ordered/has arrived.
Hey guys. That donation thread I started a while ago was on a whim cause I wanted Hyperdrive by sbreen on my Note. Was lucky enough to have him commit and get enough people chipping in for the tablet which was met with success. I'm by no means a great organizer or somebody with tight connections here on XDA . Probably would be best if someone who wanted to head it up would start a new thread stating the case.
Best of luck!
RaymanFX said:
Okay, so if maybe one of you guys, with good contact to the community, could open a new donatiion thread to collect the ~300$, I'd be grateful.
Or maybe @drrasii could chime in here and edit his first donation thread and link here as a reference to let people know what I want to do.
As I said above, I'd be willing to become the official CM maintainer, or if CM refuses to accept this for some reason, I'd host the needed sources for the device on my personal GitHub and keep it updated so people can build whatever ROM they want.
Of course, the first goal would be to get Lollipop running on this tablet, which I'd start with as soon as the device is ordered/has arrived.
Click to expand...
Click to collapse
Thanks for the quick answer.
Could one of you guys (@22sl22 or @r4yN) then open a new donation thread and explain a bit about this thread and my plans?
If we manage to handle this process rather quickly, people should be able to enjoy L on this tablet soon hopefully.
RaymanFX said:
Thanks for the quick answer.
Could one of you guys (@22sl22 or @r4yN) then open a new donation thread and explain a bit about this thread and my plans?
If we manage to handle this process rather quickly, people should be able to enjoy L on this tablet soon hopefully.
Click to expand...
Click to collapse
Sure, i'll open one now :good:
I'll also post a message in here after the new thread has been created so that people know http://forum.xda-developers.com/galaxy-note-10-2014/general/rumours-plans-to-android-5-0-t2861225
EDIT: before I open the thread, how much do you actually need? $300 is about 240 Euros, not 270 so we will need a bit more, say $350, would that be OK?
Thank you very much.
Actually, 300$ (240$) is enough, I'd be willing to pay the other 100€ myself if it needs to be.
I want to get started rather quickly and have L running on this device, so I'd order the device as soon as the 300$ are collected.
Why a P600 model and not the P601 model?
The p601 to develop is exactly the same from p600 plus the phone side.
Sent from my SM-P601 using XDA Free mobile app
Why the delay? Here are the first 10 €!
RaymanFX said:
Thank you very much.
Actually, 300$ (240$) is enough, I'd be willing to pay the other 100€ myself if it needs to be.
I want to get started rather quickly and have L running on this device, so I'd order the device as soon as the 300$ are collected.
Click to expand...
Click to collapse
Hi RaymanFX!
Glad to see that a real dev wants to take our device and port CM11 for us.
I do not make many words, but simply push the first $ 12.12 to you.
That's the current rates for 10, -€.
Hope it works as good as for sbreen (dev from HyperdriveRom) and many people jumps like lemmings behind me. :good: Haha!
Hope also we get the money quickly together and will try to continue to encourage people to make a small donation.
10,-€
Transaktionscode:
7R473626855605042
You also get a short pm
Hey RaymanFX, excited for asop 5.0 but curious about some of the stock features that make this tablet. Is there any way to preserve multi window support or s-pen features ?

Now what?

Considering that our project that shall not be mentioned was successful, I was wondering about what can be expected in terms of custom roms for this device. I don't know if ASUS released decent sources for the Ze533KL, so can we expect an eventual daily driver release or shall we expect more experimental builds? Of course I'm not asking for ETA, just wondering about what can actually be achieved for this phone.
The thing I really wanted to have with this phone is some kind of burn-in protection (which is implemented in LOS as far as I know). My phone is still under warranty, and I can already see marks of the keyboard and other icons when displaying a white image.
Since the actual thread was closed, maybe this one could be used as a bulletin board for any new unfoldings.
Cheers.
sure thing, I also thought about creating new thread where we can inform each other about our initiative. I believe that McFy is waiting for his unit to arrive. Then there will be LOS hopefully. I'm rooting for him
As far as Lineage OS features I think it is OK to ask a question here and wait for some research and answer about it.
Let's keep our fingers crossed
"Now what?" is a fantastic name for the thread.
Exactly my feeling.
Ironicaly, XDA killed the iniatitive on the day it reached its goal. So, there was no reason at all to do what was done.
About a custom ROM for the device, I have no preferences. Whatever suits the developer is good for me as long as the final product is stable and runs well.
hello everyone,
I bought the device and got it today, I downloaded stock rom, kernel sources and flashed twrp on it, I did a first build for this device but it didn't boot. Don't ask any ETA as I will not be able to tell the amount of work until I get something working. I will share with you the progress but can't give any date.
Regards and thanks for the support
bro pls give an unofficial process to unlock this device because official unlock tool not working it shows "unknown network error".
@McFy any news?
please share a working process of unlock bootloader without asus unlock tool apk....i m waiting for 3 years
McFy said:
hello everyone,
I bought the device and got it today, I downloaded stock rom, kernel sources and flashed twrp on it, I did a first build for this device but it didn't boot. Don't ask any ETA as I will not be able to tell the amount of work until I get something working. I will share with you the progress but can't give any date.
Regards and thanks for the support
Click to expand...
Click to collapse
Not asking for an ETA but noticed this is your last post on XDA - everything ok?
NANDO1413 said:
ajuda dos brasileiros
Click to expand...
Click to collapse
Nando, I don't have a Telegram account, but if someone starts building and need testers I would gladly volunteer. Just let me know here either on this topic or via pm.
NANDO1413 said:
ajuda dos brasileiros
Click to expand...
Click to collapse
I'll be honest - I don't know what any of that says and for the next ten days I'm stuck on mobile (vacation!!) so if you could translate that would be great.
koimr said:
I'll be honest - I don't know what any of that says and for the next ten days I'm stuck on mobile (vacation!!) so if you could translate that would be great.
Click to expand...
Click to collapse
Basically, a dev named Erik will try to contact Mcfly so that they both could work on porting the official Zenfone 3 Lineage to Zenfone 3 Zoom.
predatorian said:
Basically, a dev named Erik will try to contact Mcfly so that they both could work on porting the official Zenfone 3 Lineage to Zenfone 3 Zoom.
Click to expand...
Click to collapse
Thank you for that.
?
Oh well, don't wanna jump the gun here, but it seems like the dude took the money and spent on something else, or he's been really busy since then, as he no longer even commented on any xda posts.
In any case, It's a shame. Now we know why XDA doesn't allow group funding for this kind of thing. Not asking for eta is something, but you can't volunteer to develop for a device, take the money and disappear and expect people not to distrust you.
My advice for all others that contributed would be to next time buy a phone with a greater dev community, and never donate if there's no ongoing project.
Really hope I'm wrong here, please @McFy, show up and prove me wrong.
Mrkblo said:
Oh well, don't wanna jump the gun here, but it seems like the dude took the money and spent on something else, or he's been really busy since then, as he no longer even commented on any xda posts.
In any case, It's a shame. Now we know why XDA doesn't allow group funding for this kind of thing. Not asking for eta is something, but you can't volunteer to develop for a device, take the money and disappear and expect people not to distrust you.
My advice for all others that contributed would be to next time buy a phone with a greater dev community, and never donate if there's no ongoing project.
Really hope I'm wrong here, please @McFy, show up and prove me wrong.
Click to expand...
Click to collapse
I don't think you're jumping the gun - it's almost three months since @McFy last posted to us that he obtained the phone and even his github project named "android_device_asus_zenfone3_zoom" (which I presume this was for) doesn't appear to have any work done on/to it whatsoever - I don't think it's unreasonable to have gotten some kind of status update within that time, even if it's negative.
Without knowing what happened for certain I will unfortunately have to think the obvious.
Hey guys sorry for not updating you, I don’t want to tell my private life but my gf have health problems and it made me busy driving her/ spend time with her, I definitely didn’t forget you and am in touch with the project, I achieved to boot but lot of stuffs are broken; zenfone 3 have now new trees since it is now official and I am working on it; I went in touch with the dev. Fyi I did buy the device for real as I said, I am someone you can trust and in the case the situation of my gf isn’t getting better I will give that phone to another developer at my fees; I also want to mention It’s not on my habit to share wip builds or push trees change until it’s not on a state I judge nice enough.
Best regards and I hope you will understand. I totally apologize but I went inactive in all dev scene I am on and it’s hard for me as well to come back like this..
If you have any questions I can answer them if they are not personals.
I sincerely hope that you guys won’t get mad at me.
McFy said:
Hey guys sorry for not updating you, I don’t want to tell my private life but my gf have health problems and it made me busy driving her/ spend time with her, I definitely didn’t forget you and am in touch with the project, I achieved to boot but lot of stuffs are broken; zenfone 3 have now new trees since it is now official and I am working on it; I went in touch with the dev. Fyi I did buy the device for real as I said, I am someone you can trust and in the case the situation of my gf isn’t getting better I will give that phone to another developer at my fees; I also want to mention It’s not on my habit to share wip builds or push trees change until it’s not on a state I judge nice enough.
Best regards and I hope you will understand. I totally apologize but I went inactive in all dev scene I am on and it’s hard for me as well to come back like this..
If you have any questions I can answer them if they are not personals.
I sincerely hope that you guys won’t get mad at me.
Click to expand...
Click to collapse
First off, I am sorry to hear of your gf's health problems - and I truly mean that. I hope that she recovers and you don't need to tell us any more information because that is personal.
Next - the heads-up is absolutely appreciated. Thank you! I do hope you can also see from our point of view how it was looking to us and understand that we were getting puzzled. Now we know why.
Thank you again.
koimr said:
First off, I am sorry to hear of your gf's health problems - and I truly mean that. I hope that she recovers and you don't need to tell us any more information because that is personal.
Next - the heads-up is absolutely appreciated. Thank you! I do hope you can also see from our point of view how it was looking to us and understand that we were getting puzzled. Now we know why.
Thank you again.
Click to expand...
Click to collapse
That’s me who owe you that and more.
Yes I ofc can see from your point of view and that’s why I went back on the forums, I got emails and more so I realized I got the phone since enough time for you to think I might have forgotten you,
Thanks for your message it’s really appreciated!
So, another month's passed. Any news?
anyone in contact with the developer?
so sad. that money was important to me. now the z3z is kinda past on my life. won't judge others, but by the delay, i guess i can judge myself injuried.

Categories

Resources