Related
Sorry for posting this here, but I couldn't really find a suitable place since most of the Android action is right here.
These past weeks I've noticed an increase of irrelevant threads and clutter being made in regards to Android development in the HTC Dream forum and every other Android development forum on xda. A lot of Android devices out on the market now are not made by HTC. This of course is causing a problem since this forum is for HTC devices only.
Maybe it would be a good idea if a new forum was created that accounts for all native Android devices (Motorola Droid/Milestone, Motorola Cliq/Dext, Samsung Galaxy, etc...). That way, a lot of the clutter would surely be resolved and a considerate load would be taken off of this server (Gotta hate the horrible load on xda these days...).
I'm sure there are quiet a few people on here that have an HTC device and are fully satisfied with it (Me included!). That doesn't mean that everyone else has to feel the same way. People that choose to go with Samsung, Motorola, etc. for their next Android device should not be left out. That's why I believe there should definitely be a forum that serves everyone.
To put up a new forum specifically for this matter takes no time at all, but it does take participation. So if you feel like this is something you would like to see, please feel free to leave a comment.
What are you're opinions on this matter? Agree? Disagree?
Discuss.
EDIT: If there's enough people interested in this project, would there be anyone willing to help getting things started in terms of hosting space or something similar?
my thoughts are that the few changes that have been recently made should help if they are utilized. now we have a forum for general android development for devs, and the rom releases are in the device specific forums. Here was my idea, but i think they made the right choice. http://forum.xda-developers.com/showpost.php?p=4795376&postcount=1
jaaronmoody said:
my thoughts are that the few changes that have been recently made should help if they are utilized. now we have a forum for general android development for devs, and the rom releases are in the device specific forums. Here was my idea, but i think they made the right choice. http://forum.xda-developers.com/showpost.php?p=4795376&postcount=1
Click to expand...
Click to collapse
It's a start. But I don't think xda is going to put up more sub forums for each new device out there. Thus, development and ROM threads for Motorola and other devices will be left out. Unless I understood your post incorrectly
no, you're right, i just dont think xda WANTS to keep up with every brand that uses android. they apparently keep their focus on HTC devices. there are gonna be a FLOOD of manufacturers utilizing droid in the future, and unless xda wants to change their focus, they will stick with one brand
jaaronmoody said:
no, you're right, i just dont think xda WANTS to keep up with every brand that uses android. they apparently keep their focus on HTC devices. there are gonna be a FLOOD of manufacturers utilizing droid in the future, and unless xda wants to change their focus, they will stick with one brand
Click to expand...
Click to collapse
Yea that's exactly my point.
There WILL be a flood of Android devices from all kinds of manufacturers and it would be nice if there was a place for all of them come together. That way, everyone can keep track of specific development without having to switch between dozens of forums.
My $0.02.
good luck, my friend. Most likely it will take someone to else to start a new site to accomplish. funny, i was fooling around a couple days ago and did this. http://www.new.facebook.com/group.php?gid=176593179336&v=wall
not saying this is the solution, but you are not alone in your concerns.
I see that a few agree with me, care to share your point of view? Maybe it will spark this thing.
So you came at XDA-Developers to find help? Well, this is your thread!
"Give a man a fish and you feed him for a day. Teach a man to fish and you feed him for a lifetime"
Hello new user and welcome to XDA-Developers. We are a developer’s forum, with the purpose of development. Our work can be used in several ways, and, we know that sometimes it could help you. So, in order to maintain our forums clean and properly organized maintaining a proper development environment while at the same time to give you a chance to join our forums we created this thread.
This thread is for sensible questions from new or inexpert users. If you think your question may be a little basic for a developer forum then this is the place to ask it.
Here you shall find an atmosphere free of prejudice, where we will try to help you in your problem, answer yourmost basic questions and aid you on troubleshooting your device. We know that learning all the technicalities takes time, however they are necessary in order to interact with us.
Bare in mind that we are not technical support, we do not work for any company or get paid to help, we are just independent developers gathered in a community called XDA-Developers. Therefore all we will do is guide you into troubleshooting your device yourself, but under no circumstance we are abided to do so.
We want you to become the kind of user we see as productiveto a developer’s community, and why not?, to be a developer yourself!
Note to General users:
This is a chance for more advanced users to “give back” at XDA-Developers the knowledge we have gathered together in a decade of development. This is a thread to behave in a tolerant way, taking into consideration that the user posting queries might have never even heard words such as “adb” or “ROM", so, if you are not willing to be helpful, I kindly invite you to browse into another thread.
"Time has changed, Users have changed and so will XDA-Developers"
Moderators will not tolerate "flaming" or "trolling" in this thread as it is specifically provided for those who are still learning the basics.. We will delete and sanction without warning any post that show intention other than to help the new user.
Okay, then, I have a newbie question: can someone explain exactly what "S-Off" means?
Take S-Off for Security Off. With S-Off you can directly write to kernel, bootladers and radio, while S-On devices would need a second device (a PC) to write to those areas. Its like a protection mechanism for us not to brick our phones (at least not as easy).
There is plenty of explanations at our forums if you want t get into technical details or just want another explanation. Just try using the search button in the right top corner of XDA pages, you will be amazed how much you can find .
D.O.C
XDA Developers Senior Moderator
I'd go on with another newbie question.
If I'm not wrong rooting breaks warranty (in most of the cases at least) but I think (again im not sure) we can reboot our device to factory settings before giving it to technical service to fix its problems.
What happens if the device is not working? Is there an external way to fix the rooted system back to normal?
I am going to go with a NO in that subject.
Although there are plenty of methods that have been successful in several handsets in the past by using third party hardware, it can get complicated even for a advanced users to do so, since it might involve technichal aspects only manufacturers know about.
Normally, these methods are developed and posted here, depeding on the handset, it might be easy or not. Not so many years ago, these methods were as easy as flashing a "untouched" firmware, but lately, manufacturers have been implementing methods to detect if we have touched the bootloader and have increasingly making it harder for developers to break them, thus returning to a "factory untouched" state is getting harder with every new device.
In short, If you want your warranty intact beyond the existence of any doubt, do not root.
And why is my galaxy tab crushing with cm 10 mod with latest gapps. I dont really think it is a noob question.
Guys, please keep your questions device specific.
We can't be discussing Galaxy Tabs here.
Thanks
I have a problem and I'm new here, so I just reply in this topic. I'm sorry for my little English.
I have a HTC One S and I dropped it a few days ago, now the volume down button is dented and I can not use it anymore. Since you can still set te volume by pushing the volume up button and swipe the volume down, i thought it was ok.
Now I wanted to turn my phone off and this is what I've got:
*** LOCKED ***
VLE PVT SHIP S-ON RL
HBOOT-2.15.0000
Radio-1.11.50.05.28
OpenDSP-v31.1.0.45.0815
eMMC-boot
Dec 14 2012, 17:10:57:-1
HBOOT
<VOL UP> to previous item
<VOL DOWN. to next item
<POWER> to select item
FASTBOOT
RECOVERY
FACTORY RESET
CLEAR STORAGE
SIMLOCK
IMAGE CRC
SHOW BARCODE
Using the volume up button I can select one of the items, but pressing the powerbutton brings me nothing. I have no idea what to do or how I can fix this.
Please help!
I see this is the wrong topic but I am unable to delete this message, I'm sorry.
Well, it is a hardware fault since its broken, so not much we can help you here. Try maybe reading the HTC One S specific forums to find a workaround, but honestly, you better replace the handset.
I have two good question. What is the difference between the HTC One developer edition and the regular one (ha).
What I've seen made it look you would struggle with putting roms on the regular one.
Also, how soon is the one likely to have roms and people putting the latest android on it (like pure nexus jelly bean)? Like a couple months, a year?
Thanks for your help
TaderTot said:
I have two good question. What is the difference between the HTC One developer edition and the regular one (ha).
What I've seen made it look you would struggle with putting roms on the regular one.
Also, how soon is the one likely to have roms and people putting the latest android on it (like pure nexus jelly bean)? Like a couple months, a year?
Thanks for your help
Click to expand...
Click to collapse
The difference of the Developer Edition and regular one is that it is already S-Off, unlocked bootloader(no need to go to HTC dev) and has 64GB storage. And it comes only on one variant which is a US LTE type. So LTE won't work on Europe or Asia.
Regarding AOSP(pure nexus ROM) probably less than a month after the release of kernel source code by HTC on which I dunno when it would come.
So this will be my first non-nexus device. Will there be custom roms that will be up to date with the latest version of Android so I don't have to wait for HTC? If so, how will their stability be?
xGary said:
So this will be my first non-nexus device. Will there be custom roms that will be up to date with the latest version of Android so I don't have to wait for HTC? If so, how will their stability be?
Click to expand...
Click to collapse
Give it time and there will be. I'm sure they'll be stable enough when released anyway.
I'm also coming from a Nexus and is a first for me to be getting a HTC.
It is possible to use the EU version of the HTC One in the US? I'm debating between the developer version and the EU since I'm located in the US (and want an unlocked bootloader), but it looks like the EU version would work on AT&T?
HSPA/WCDMA:
Europe/Asia: 850/900/1900/2100 MHz
GSM/GPRS/EDGE:
850/900/1800/1900 MHz
LTE:
EU: 800/1800/2600 MHz
US (AT&T): 700/850/AWS/1900 MHz
US (TMO): 700/AWS MHz
US (Sprint): 1900 MHz
Asia: 1800/2600 Mhz
Click to expand...
Click to collapse
Yeah it looks like it, but, if you want an unlocked bootloader, developers edition should be your choice (that is what I would do)
Hi ! i am totaly new to Android Os so plz help me !!!
Hi
recently i bought HTC Desire A8181(Bravo).
i want to upgrade its software to Android v4.xxx . so i need help which firmware should i install on my HTC Desire so it work perfectly and has no Bugs ... Plz help me and guide me so i update my Phone
Thanks and also plz tell me Whats are Those ROMS ???
naeembabakheil said:
Hi
recently i bought HTC Desire A8181(Bravo).
i want to upgrade its software to Android v4.xxx . so i need help which firmware should i install on my HTC Desire so it work perfectly and has no Bugs ... Plz help me and guide me so i update my Phone
Thanks and also plz tell me Whats are Those ROMS ???
Click to expand...
Click to collapse
Hi naeembakakheil.
First thing you might want to do when looking for firmwares for your mobile device, is look in the correct section. Try here for your device specific info.
Second, please browse through those forums, read the OP of each thread which includes the description of the ROM you are about to flash, and then, read through the replies your fellow users have left to see their impressions, you can usually find all the help you need by reading. This would be a good place to start. If you still have any doubts, then ask in the appropriate thread. If after extensive search you still do not find the appropriate answer to your question, then ask in the Q&A forum of the device (although if you do know how to search, you will hardly ever need to open a new thread, almost every question is already answered).
What you must not do ever is.....ask without reading or even worst, read the incorrect information (as in not your phone's forum), you could easily break your device useless by making that mistake.
When can we expect 4.2 ROMs for the HTC One?
amarshonarbangla said:
When can we expect 4.2 ROMs for the HTC One?
Click to expand...
Click to collapse
No one can possibly tell you that. As a matter of fact, XDA was founded because of the same queries arouse between members...until they started building themselves. So, I kindly invite you to join our developer communitty and build yourself a 4.2 or at least get invokved in the process.
I wouldnt recommend coming to xda with expectations of the arrival of something, since it can be a very long and boring time . Its best to be involved in the making of things here at xda, that way I guarantee you will not get bored and eventually, you will get what you want.
D.O.C said:
No one can possibly tell you that. As a matter of fact, XDA was founded because of the same queries arouse between members...until they started building themselves. So, I kindly invite you to join our developer communitty and build yourself a 4.2 or at least get invokved in the process.
I wouldnt recommend coming to xda with expectations of the arrival of something, since it can be a very long and boring time . Its best to be involved in the making of things here at xda, that way I guarantee you will not get bored and eventually, you will get what you want.
Click to expand...
Click to collapse
I am a long time iOS user who recently switched to Windows Phone 8. Seeing how customizable Android is, I am thinking of making the jump soon. I have a lot of things to learn about this wonderful operating system, which is why I joined XDA
What goes into making a custom ROM? Do we need any specific files/firmwares/kernels/drivers from HTC to make a 4.2 ROM? Are there not any devs working on 4.2 ROMs for the One?
This is a discussion thread for all things custom; Building steps and tips, problem solving and issue discussion. All questions and/or comments are welcome. Be aware, although I build and customize ROMs, I am not a professional developer and cannot promise a solution for your problem. But, hopefully, we can work together to come up with practical solutions for any problems here at m7spr.
So..The things you were shut down on. Were they CM related, or Sense stuff?
Did they involve you working solo, or with a team? Give more details, get the word out.
Felnarion said:
So..The things you were shut down on. Were they CM related, or Sense stuff?
Did they involve you working solo, or with a team? Give more details, get the word out.
Click to expand...
Click to collapse
I really am leery of pointing fingers at specific people because I'm new here and don't want to make a name for myself as a whiner. But, basically it is both. The custom ROMs I am working on have all been built before by me on other devices, so that's not the issue. I have inquired about possibly collaborating with other devs on some Sense related stuff and was looking into why there was no official or unofficial release of the current CM10.2. The sense stuff really isn't my bag as much, but i was/am interested. Others are working on the CM, but with no official release in play, no one wants to put theirs out. I have built it successfully, but have no intention of trying to lay it out there when other devs have been working on it before I got here. My thing is this: when I got tired of waiting for devs to come up with new things, I was told to put up or shut up. It was good advice; I have no coding experience specifically, but I like to learn and have been successful at not only compiling and maintaining custom builds, but also starting 'Learn to do it yourself' threads in two different device forums. I like to learn and compile and share. That's it. I don't need (or want) attention or grateful fans or any of that crap. All I want to do is open the doors for more builds and more users getting off their asses and building for themselves. It seems like a win-win to me, but I feel resistance and it is disappointing. I will get off my soapbox now
I typically touch base with any dev who is the creator/maintainer of any ROM I am interested in pursuing. My experience has been more of a quick 'try it out and see what you get' response or 'it can't be done'. This is after I have asked for not only a blessing, but for relevant information and possibly assistance. Maybe I am just hitting up devs who are already frustrated and don't want someone like me asking a bunch of questions, I don't know....
BMP7777 said:
I really am leery of pointing fingers at specific people because I'm new here and don't want to make a name for myself as a whiner. But, basically it is both. The custom ROMs I am working on have all been built before by me on other devices, so that's not the issue. I have inquired about possibly collaborating with other devs on some Sense related stuff and was looking into why there was no official or unofficial release of the current CM10.2. The sense stuff really isn't my bag as much, but i was/am interested. Others are working on the CM, but with no official release in play, no one wants to put theirs out. I have built it successfully, but have no intention of trying to lay it out there when other devs have been working on it before I got here. My thing is this: when I got tired of waiting for devs to come up with new things, I was told to put up or shut up. It was good advice; I have no coding experience specifically, but I like to learn and have been successful at not only compiling and maintaining custom builds, but also starting 'Learn to do it yourself' threads in two different device forums. I like to learn and compile and share. That's it. I don't need (or want) attention or grateful fans or any of that crap. All I want to do is open the doors for more builds and more users getting off their asses and building for themselves. It seems like a win-win to me, but I feel resistance and it is disappointing. I will get off my soapbox now
I typically touch base with any dev who is the creator/maintainer of any ROM I am interested in pursuing. My experience has been more of a quick 'try it out and see what you get' response or 'it can't be done'. This is after I have asked for not only a blessing, but for relevant information and possibly assistance. Maybe I am just hitting up devs who are already frustrated and don't want someone like me asking a bunch of questions, I don't know....
Click to expand...
Click to collapse
you can start by helping to get things working in sense 4.2.2 beta rom
flex360 said:
you can start by helping to get things working in sense 4.2.2 beta rom
Click to expand...
Click to collapse
I looked your thread up and I think we'd get along great. Anybody who says 'if you don't like me, GOOD' is someone I wanna hang with. It's also funny you should mention helping with that sense version because that's exactly what I was trying to do. Sense aint even my bag, but I was going to look into it from the SVD side to see what I could learn. Maybe I just rubbed that guy the wrong way or something. Regardless, I can't promise how much help I will actually be, but I'm willing to give it a shot. Tell me what you need and the right places to look and I'll do whatever I can. Be cool
BMP7777 said:
I looked your thread up and I think we'd get along great. Anybody who says 'if you don't like me, GOOD' is someone I wanna hang with. It's also funny you should mention helping with that sense version because that's exactly what I was trying to do. Sense aint even my bag, but I was going to look into it from the SVD side to see what I could learn. Maybe I just rubbed that guy the wrong way or something. Regardless, I can't promise how much help I will actually be, but I'm willing to give it a shot. Tell me what you need and the right places to look and I'll do whatever I can. Be cool
Click to expand...
Click to collapse
do you have google hangout?
I think one issue is that there is an update to 4.3 looking for the Sprint One. This will undoubtely contain new radios and firmware that will help our phones run on 4.3+. Since this is a know update, many devs have decided to forego work on the the current 4.1.2 Sense ROMs. Some are working on the 4.2.2 Sense ROM, but with no leak, or Sprint version it is much harder work. Also, there is only source for up to 1.29. The source from the 1.31 update is not available and it has caused issues with ROMs based on that update.
Personally I don't get your complaint though. There is a lot of development and a wide selection of ROMs available from Stock Android 4.1 to 4.3 to Stock Sense, to heavily themed Sense ROMs. What exactly is not available that you want?
flex360 said:
do you have google hangout?
Click to expand...
Click to collapse
[email protected]
raptoro07 said:
I think one issue is that there is an update to 4.3 looking for the Sprint One. This will undoubtely contain new radios and firmware that will help our phones run on 4.3+. Since this is a know update, many devs have decided to forego work on the the current 4.1.2 Sense ROMs. Some are working on the 4.2.2 Sense ROM, but with no leak, or Sprint version it is much harder work. Also, there is only source for up to 1.29. The source from the 1.31 update is not available and it has caused issues with ROMs based on that update.
Personally I don't get your complaint though. There is a lot of development and a wide selection of ROMs available from Stock Android 4.1 to 4.3 to Stock Sense, to heavily themed Sense ROMs. What exactly is not available that you want?
Click to expand...
Click to collapse
This really wasn't meant to be some complaint thread with a bunch of whining; just the opposite, really. I just wanted feedback on how I am perceiving things around here. I'm cool with being told I have it wrong; was hoping for it actually. And you pointed out exactly what I mean in part. Sense this and stock that is the rule of the day here. That's ok. Everyone is allowed to like whatever they want and if sense and stock are the most wanted builds then so be it. But, I am a self-proclaimed customization junkie, for better or for worse. Personally, I like more fully custom ROM choices and have been beating my head against the wall trying to get some Beanstalk love here but without success to this point. BS is already set in 4.3 and matched with CMs 10.2 releases, so I'm stumped. If you have knowledge, I would be happy to show you some of my errors. I do think you make a great point about the whole place being in flux due to the impending 4.3 release. Like I said before, I just want to open up some development doors and get more interest in development in general. Maybe I have hit up the wrong devs or caught them at bad times. It happens.
BMP7777 said:
[email protected]
This really wasn't meant to be some complaint thread with a bunch of whining; just the opposite, really. I just wanted feedback on how I am perceiving things around here. I'm cool with being told I have it wrong; was hoping for it actually. And you pointed out exactly what I mean in part. Sense this and stock that is the rule of the day here. That's ok. Everyone is allowed to like whatever they want and if sense and stock are the most wanted builds then so be it. But, I am a self-proclaimed customization junkie, for better or for worse. Personally, I like more fully custom ROM choices and have been beating my head against the wall trying to get some Beanstalk love here but without success to this point. BS is already set in 4.3 and matched with CMs 10.2 releases, so I'm stumped. If you have knowledge, I would be happy to show you some of my errors. I do think you make a great point about the whole place being in flux due to the impending 4.3 release. Like I said before, I just want to open up some development doors and get more interest in development in general. Maybe I have hit up the wrong devs or caught them at bad times. It happens.
Click to expand...
Click to collapse
Part of the issue might be that users are afraid of using Cm as it has a nasty habit of bricking phones that no one of notoriety has looked into, acknowledged, or found a solution to.
Kraizk said:
Part of the issue might be that users are afraid of using Cm as it has a nasty habit of bricking phones that no one of notoriety has looked into, acknowledged, or found a solution to.
Click to expand...
Click to collapse
I haven't really been looking at it after my first run (I personally like Sense a lot, and AOSP didn't have a good way of dealing with the limited hardware options for me), but wasn't the brick-spree killed a while back?
Rirere said:
I haven't really been looking at it after my first run (I personally like Sense a lot, and AOSP didn't have a good way of dealing with the limited hardware options for me), but wasn't the brick-spree killed a while back?
Click to expand...
Click to collapse
A couple of people developed a "consensus" that it had been fixed. then 2 more people bricked their phones. ALLEGEDLY the CPU has a tendency to over clock itself and lock at 1.7 Ghz
This is all fine and dandy yet no one can figure out why or how to stop it.
I thought so too
Sent from my One using XDA Premium 4 mobile app
BMP7777 said:
I thought so too
Sent from my One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Like I said no one ever figured out why or how to stop it. A consensus was reached but then more people bricked. No developers could be bothered to take time out of their day to look into it though.
Kraizk said:
Like I said no one ever figured out why or how to stop it. A consensus was reached but then more people bricked. No developers could be bothered to take time out of their day to look into it though.
Click to expand...
Click to collapse
I saw one guy who was addressing it and taking names and such, but then I guess it just faded away. Do you know of ongoing issues like this? Can all of the bricks be undoubtedly proven to be from no other cause? I think that would be the defining characteristic of lack of support; difficulty in proving cause. My build of CM10.2 runs fine as long as I don't try to change the font with Font Installer. And I am reasonably certain that it isn't from CM all by itself. I have the same issue with Illusion ROM 4.2.2. Anybody know why we can't change the font? My thread; I can change topic if I want to
BMP7777 said:
I saw one guy who was addressing it and taking names and such, but then I guess it just faded away. Do you know of ongoing issues like this? Can all of the bricks be undoubtedly proven to be from no other cause? I think that would be the defining characteristic of lack of support; difficulty in proving cause. My build of CM10.2 runs fine as long as I don't try to change the font with Font Installer. And I am reasonably certain that it isn't from CM all by itself. I have the same issue with Illusion ROM 4.2.2. Anybody know why we can't change the font? My thread; I can change topic if I want to
Click to expand...
Click to collapse
It is the only common factor in permanent bricks. Phone gets hot, phone wont charge. All other "bricks" are user induced because people did not understand what S-Off meant, what wiping in TWRP means, what GSM means etc etc.
So how many confirmed permanent bricks and when was the last? Has anyone proven a cause? Contacted HTC or CM or Sprint? If there were twenty cases with only 5 confirmed, then it isn't that big from a larger standpoint. See what I mean? That would explain what you see as a lack of support? Has this happened to you?
BMP7777 said:
I thought so too
Sent from my One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Check your hangouts.
BMP7777 said:
Why does there seem to be very little development going on here and why is the development that is taking place so closely guarded? I thought everyone wanted more choices and new options..... I see that there is current and ongoing 10.2 development (hell, I've even built it), but no one wants to release it. I'm hearing that the last guy who did that got banned. So, if everyone is waiting for OFFICIAL builds to be released first, why are there none being officially worked on? Two times in the last three weeks I have inquired about wanting to work on some new development and have either been told straight out not to release or been effectively threatened with reporting before I have even begun an attempt. I don't know if maybe there has been a rash of jerks who are trying to claim ownership of work that does not belong to them or what, but I've never seen as much negativity about new builds in any thread I have been a part of. I want to claim ownership of nothing; I only want to open doors. I guess I'll just work on things for my own use and leave this forum to the guys currently running it. HMPH :angel:
Click to expand...
Click to collapse
You could build us a GSM version ROM that works on the sprint HTC One. You'd be a hero if you could do that. We've already unlocked our phones and are able to connect to the ATT / TMO but only manually. When the signal is lost it seems to still be looking to auto connect to sprint...I would think this should be a simple setting software but I know nothing about phone ROMs.
Beck04vall said:
You could build us a GSM version ROM that works on the sprint HTC One. You'd be a hero if you could do that. We've already unlocked our phones and are able to connect to the ATT / TMO but only manually. When the signal is lost it seems to still be looking to auto connect to sprint...I would think this should be a simple setting software but I know nothing about phone ROMs.
Click to expand...
Click to collapse
Man, if I could do that I'd be a GOD. :angel:
I love lamp
Haha Naw but I see your point but I love and appreciate every devolepers effort here on this forum ..there not a a lot but a bunch of smart and quietly brilliant devs here ...I'm comfortable but the more the merrier
Sent from my HTCONE using XDA Premium 4 mobile app
Hello,
I'm new here and I've never done something like flashing a CustomROM.
I have a LG P970 with cracked screen and malfunctioning power button and USB port (they share the same connector which I [kind of] fixed).
My phone is currently running CynagenMod (one of the stable ones I think) but I don't know much more. (I didn't do anything to it, I got it like this)
I am looking forward to play with my phone while I wait for the OPO to be widely released.
My main idea was to put KitKat on it because I heard of the RAM optimization and so on, but I'm not sure if an inexperienced user like me should go that far, should I?
nonlosoproprio said:
Hello,
I'm new here and I've never done something like flashing a CustomROM.
I have a LG P970 with cracked screen and malfunctioning power button and USB port (they share the same connector which I [kind of] fixed).
My phone is currently running CynagenMod (one of the stable ones I think) but I don't know much more. (I didn't do anything to it, I got it like this)
I am looking forward to play with my phone while I wait for the OPO to be widely released.
My main idea was to put KitKat on it because I heard of the RAM optimization and so on, but I'm not sure if an inexperienced user like me should go that far, should I?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1111771
http://forum.xda-developers.com/showthread.php?t=1487105
Read through the above links thoroughly. Then come back and ask questions. These are both awesome resources to new users, and many users have asked many of the exact same questions you'd like to ask.
You need to develop a general understanding of both the Android operating system and the methodology and tools used by "hackers" to enhance their phones. Once you get this knowledge, questions are more direct and specific.
androcraze said:
http://forum.xda-developers.com/showthread.php?t=1111771
http://forum.xda-developers.com/showthread.php?t=1487105
Read through the above links thoroughly. Then come back and ask questions. These are both awesome resources to new users, and many users have asked many of the exact same questions you'd like to ask.
You need to develop a general understanding of both the Android operating system and the methodology and tools used by "hackers" to enhance their phones. Once you get this knowledge, questions are more direct and specific.
Click to expand...
Click to collapse
That's an amazing help!
It's going to take a while but I'm downloading my first customROM, hopefully I'll soon understand better the process and feel confident enough about it.
There is so much stuff to read!
Thank you!
Do not ask for an ETA
Once the mods start getting onto people for asking, I'll take my dev work off site. I don't want to upset mods and admin over people being impatient.
I've been looking and root isn't available yet for the Snapdragon version. I've created root access for a few devices so far, be it years ago. I want root, so I've decided to start dev work on my own. Can't say how long it will take, or if I will be able to, but anyone that is willing to test or help, feel free to comment and say so, since help would be greatly appreciated. Testers are needed.
First off though, what advancements have been made so far? Several posts I've seen have dead links to data, so to start, I'll need to know what's been done already. No need to reproduce failed outcomes.
Reserved for future links.
drakaina said:
Do not ask for an ETA
Once the mods start getting onto people for asking, I'll take my dev work off site. I don't want to upset mods and admin over people being impatient.
I've been looking and root isn't available yet for the Snapdragon version. I've created root access for a few devices so far, be it years ago. I want root, so I've decided to start dev work on my own. Can't say how long it will take, or if I will be able to, but anyone that is willing to test or help, feel free to comment and say so, since help would be greatly appreciated. Testers are needed.
First off though, what advancements have been made so far? Several posts I've seen have dead links to data, so to start, I'll need to know what's been done already. No need to reproduce failed outcomes.
Click to expand...
Click to collapse
One guy flashed a combination version of the firmware and got the OEM unlock toggle to show on a SM-G960U. It switched on and off but I am not sure if it actually unlocked the bootloader or not. There is a TWRP already ported to the Snapdragon version as well, although only for the Chinese and Hong Kong version, it should work on our device if you can get the bootloader unlocked first. I have been scouring online and in the forums since the phone came out and that's all I nave found thus far. Im sure you already know these things, but I figured I would say it just in case you weren't aware. Hope you get it figured out! Good luck! ?
The only development I've heard of is one user claiming he got a diagnostic boot with SElinux permissive. (In the S9 root dev forum/thread) I also have a source who is NOT trying to be identified publicly because he works for google, but he informed me that "the android O build for SAMSUNG DEVICES, was developed with special instructions in it to automatically kick a KERNEL PANIC , if ANY app NOT on some internal White List attempts to access, modify, or send SU commands through any NOT LISTED app with those permissions granted already." ... now I'm not an Android level programmer, but I'm an old Linux dev/ penetration systems tester (lol) and from what I am gathering is that the patches or whatever that Samsung added to the O.S. also included an encrypted or hidden white list, which he says is VERY small, (as in number of items actually in the list) , but even he said they do not have any access nor knowledge of where they stored this. He did tell me that they delivered an incomplete or infant code for Samsung Snapdragon Model Note 8,9 and s8,9, and it was so crude that not only would it not compile because of missing crap Samsung deliberately did not supply them with... but he said that it was NOT lockable in that state, so Samsung either inserted their own locked kernel and whatever to create this B.S. broke down version of Android that is Root crippled. BUT the only clue he could give me was that "On no level can an E-fuse provide an unbreakable chain of trust, and that if an extreme modded were to actually break down the system board of an S9, they could in theory remove or add some sort of device that would bypass the Qualcomm Secure boot completely!" ... now this ain't a best friend or nothing so truthfully I'm surprised I got this much from him... but I've known who he was and that hes worked for Google nearly 12 years as a developer and software engineer. So I dont know if any of that info helps... but my contribution is that I can get my device (s9+ from Sprint USA Sm-g965U) replaced with little to no hassle, so I'm 100% willing to do any tests u need, providing that you give me at least a basic level of instruction, as to each set of commands or package u want me to flash. I'm pretty android savvy considering it's just a linux derivative... and I know Samsung 100% .. I've had every S - galaxy since day 1 . BUT throwing blind commands at my device that I have 0 understanding of their impact, makes me feel like a squirrel running across the freeway during rush hour! Plz Do me a favor and shoot me a private message and I'll give you my cell number and email so u can reach me quicker when you have something u need tested! Now please people don't berate me if something he said to me was not correct or you have different data to disprove what he said. I literally took notes by hand and had him confirm them, so I'm just the messenger/informant and u gotta realize that as a google employee, he #1 is partially not knowledgeable of ways to exploit the O.S. which is what the hackers come into play for. And make the developers work **** tons harder to FIX the hole the ****ed up in the 1st place! ? Lol... and #2. I did ask about the possibility of a $$$$ number he would take in order to provide an actual Eng-boot like that of the S8, and he said that "Those are developed by each individual corporation after they are provided the build source code", and that "google has no interest in possessing or archiving any such file because the O.S. does not need it to provide a developers version of the O.S., which is as far as Google goes in providing a new system to the companies.... so for something like that, reach out to one of the underpaid factories full of workers and I'm sure they would happily give you what you want for much cheaper than you imagine!" Ok that was very long winded but I wanted to cover all I could because I prob wont check this thread anymore.... plz PM me bro so I can get you my info ... and let's put this Flashing Guinea Pig (me) to work in getting this ***** at least hack rooted or maybe full!!!
Hello, i've just finished reading all above and from what I've read I can tell that not all hopes are lost as well I'm offering my help to be a (TESTER) for any attempts you wanna try, however, please note that I'm NO DEV just a user who would like to his phone rooted ASAP that's all, so please explain the commands that you would give me and the steps. plz PM me so I can get you my contact info
It ain't happening with the known exploits.
Ok, so far I have a few routes I plan to take that have worked on other devices. Working on the first, but not at the moment. The rude comment compelled me to post my own. Devs don't follow old ways of doing things so get that out of your head if you want to think forward, not backwards. I have found what could be an exploit in the rom itself that "might" be the starting point to get root access. This is NOT an ETA but hopefully we can start testing in the next few weeks.
I'll say it now, don't get overly excited a possible exploit has been found. I make no guarantee on it being THE exploit needed. Just be patient, and if you have insight on a way to attack this or another possible exploit, do say so.
If anyone knows of the bootloader partition already having been copied, post a link. I share mine at the moment so I don't always have it around, so any of the bootloader data would help greatly.
drakaina said:
Ok, so far I have a few routes I plan to take that have worked on other devices. Working on the first, but not at the moment. The rude comment compelled me to post my own.
Click to expand...
Click to collapse
I saw no rude comment, just a dose of reality for you, a little thin skinned are we?
You're continuing to be rude and attempting to derail the point of the thread. Meh, I'm getting back to work since it not good to feed trolls.
Pretty sure placeholder threads are not allowed on XDA...
I am making presence known now. I will be watching this closely
Technicly this thread don't even need to exist right now.
drakaina said:
Do not ask for an ETA
First off though, what advancements have been made so far? Several posts I've seen have dead links to data, so to start, I'll need to know what's been done already. No need to reproduce failed outcomes.
Click to expand...
Click to collapse
Myself and a handful of other people involved in us snapdragon s8/s8+/n8+ took a brief crack at it a little while ago to no avail. I don't want to go into too many details on here as 1) Samsung is watching surely and 2) the contents from the peanut gallery get old quick but here are the cliff notes. Feel free to pm me here or on telegram for more details. (Backstory on me, I created samfail which was the first/only n8 root method and the second for the s8/s8+ and the only published one beyond bootloader v1.
- samfail is 100% patched. No known way to modify system
- you can't mix combo boot with stock images anymore. Samsung got wise to that. Figured out how to track it if we can force write a system image
- there is a ton of new system level security because they had to move out of the boot image due to treble. Probably the first big nail in the coffin I'm.
- don't waste your time on the oem unlock toggle in the combo/factory rom. No it doesn't unlock the bootloader. The us snapdragons don't respect it's value outside of turning off frp, but that was with the s8 idk if it is still true on the s9.
- the other poster is right about the anti root thing. It's in the open source kernel code. If anything being exexuted under uid 0 matches a list of common/known root mods/not stuff that is supposed to be there, instant kernel panic. Things like "binary is called BusyBox" are on that list.
This was the point I gave up. Partially because I don't have the device so testing is extremely difficult (I wised up this year and purchased a intl. Snapdragon sm-g9650 which has full oem unlock just like the exy).
In sure there's things in forgetting right now and again, being too transparent here results in root method bring patched faster, hit me up if you want more brain dump
drakaina said:
You're continuing to be rude and attempting to derail the point of the thread. Meh, I'm getting back to work since it not good to feed trolls.
Click to expand...
Click to collapse
Although I have seen a lot worse on these threads, his comment was pretty negative, which is what we do not need in this thread. I wish people would just keep their thoughts to themselves if they have nothing to add to the discussion. I also will test so let me know if there is anything I can do to help.
i also have a g965u and have been trying various mwthods to no avail at this point.. we need new exploits to be found.. all the obvious stuff will not work
It is because of this is why I will never buy another Galaxy phone. I need root.
zzEvilGeniuszz said:
It is because of this is why I will never buy another Galaxy phone. I need root.
Click to expand...
Click to collapse
Just don't buy snapdragon, the Exynos S9s are unlocked
*Detection* said:
Just don't buy snapdragon, the Exynos S9s are unlocked
Click to expand...
Click to collapse
You cannot buy Exynos from a carrier. You have to buy directly from Samsung for that. I know because I requested a Exynos variant. Sprint said they couldn't (or wouldn't) give me one.
edit: nvm not worth it.
zzEvilGeniuszz said:
You cannot buy Exynos from a carrier. You have to buy directly from Samsung for that. I know because I requested a Exynos variant. Sprint said they couldn't (or wouldn't) give me one.
Click to expand...
Click to collapse
i talked to samsung a couple months ago before i got my s9 and they told me they wont sell you one directly with the Exynos. I was going to get the s8 with the exynos if they would of sold me one. They wouldn'ty so i bought a tmobile s9 with my carrier.
has anyone been able to reboot phone into edl mode?