Develop Bugs

The Official XDA Support thread for Android Phones (Updated)

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
HELP AND SUPPORT
​
DESCRIPTION OF THIS THREAD
Back in 2011 I sat down and wondered what I could do to help a community that helped me so much and continues to help people everyday from bricked phones to shiny new things on their respective devices and this is what I created, with the guidance of certain moderators of course.
[*]I wanted to create a thread in which any question can be asked, be it porting related or anything and we all help each other out, this has been going for a few years now and has been a huge success so I have updated the quick start guide and I will be a more ever-present force in the thread to answer any help and such that you may need, because if we all help each other this place can be a more user-friendly and more interactive place to visit.
Please also note you may PM me if you wish to ask anything in private, or if you feel the need to just say hello.
Please also note that this thread was indeed a sticky at one time however I had other commitments in 2011 (College and such) and it was removed by November 2011.
[*]For donations, I would kindly ask you to donate to the Macmillan cancer care and support, however if you wish to donate to me I will donate it to the charity anyway, myself and Macmillan thank you for your support, no one should have to face cancer alone.
HERE IS A GUIDE TO GET STARTED​
GENERAL KNOWLEDGE v1.0
Rooting - Gives you complete root system access allowing things to be done that usually would be denied.
[*]S-OFF - (HTC Devices) Basically means you can flash ROM's to the SYSTEM partitions and such.
[*]Write Protection - This can mean a variety of things, from a locked boot-loader to SD card access, consult your device forum for information.
[*]Bricked(Soft) - Soft brick means that it can be recovered using appropriate methods found in your device forum.
[*]Bricked(Hard) - Very hard to fix usually means it's beyond repair but can be fixed in certain circumstances and at a local repair dealer for your phone.
[*]Kernels - The backbone of the phone, they are responsible for making everything run, the CPU, Schedulers and such are configurable using the kernel.
[*]CPU0 - Different for each phone however CPU0 is usually the 1st logical processor followed by 1,2,3 for quad core phones.
[*]Dual Core/Quad Core - Dual core means you get CPU0 and CPU1, Quad core means CPU0, CPU1, CPU2 and CPU3 are all available.
[*]Chip-set - This is your main-board, it means what your phone is built upon.
[*]Lib files - Found in /system/lib usually however this can be different, they control the software to firmware gaps on your phone, so they enable sound, camera, video; the major things live here, don't touch it unless you know what you're doing.
[*]Battery Stats - These control how long your battery lasts, they are reset when you delete the file from the system however it's strongly recommended you don't delete them.
[*]AOSP - Basically means the original Google Android software as a bare-bone OS.
[*]Partitions - These are different for each phone and should be treated with great care for example flashing a puppy to the radio partition would be a foolish action.
[*]Launchers - They change the UI of the phone, there are many out there so try them all until you find one that suits you just right.
[*]Logcat - This is only useful if you have an error with your phone, it's a simple adb logcat command however I prefer to use QTADB which is a nice GUI style logct application.
[*]ROM's - You flash these on phones that are able to flash Custom software, you can get many varieties however the main ones are 'Stock' the original phone OS, 'CM' which is AOSP, 'MIUI' An AOSP/AOKP style crossover mimics the iOS UI.
[*]Recovery - When flashed; custom recovery allows you to make changes to the different partitions inside the phone for example flashing a custom ROM.
[*]Flashing - Basically writing information to a partition or making a fool of yourself in public (the latter is not recommended due to laws)
[*]Over-clocking - This means pushing your hardware beyond its manufacturers original settings, this can be useful to create a faster phone but treat it with care as you can damage phone hardware.
[*]Under-clocking - This means lowering the stress on the system by making the hardware run slower than it's intended to do, great for saving battery.
[*]Under-volting - This means under-volting your CPU or GPU, this can cause stability issues but on the plus side can save battery, it's all about striking a balance.
[*]Benchmarking - This means to test your phone to its max and find out how it stacks up against other devices.
[*]IO Schedulers- They control how the system reacts in different situations, there are different types of Schedulers available so use each until you find one suitable for you (protip: Use fiops or noop)
[*]CPU Governors - They control the CPU frequencies and such for example "Performance governor" will give you constant speed, whereas "Conservative governor" will give you low speed.
[*]GPU Governors - They do the same as their CPU counterparts except they control the graphical section of the hardware.
[*]Radios - They control the baseband aspects of a phone (your network and such) they have different names for each device, they are very dangerous to mess around with.
Note:
Updated as of 12/06/13
So what are you waiting for? Ask questions!​​

comnd promt is responding
I hav managed the ss number and when put in the beta f oth d par revolutionary it come from the cmd promt to root the htc evo any ideas

alsworld said:
I hav managed the ss number and when put in the beta f oth d par revolutionary it come from the cmd promt to root the htc evo any ideas
Click to expand...
Click to collapse
i didn't really understand all that, but from what i got, you want to root it? or s-off it?
try the revoluitonary.io site

i used revolutionary cwm, loaded rmk's root zip, and wound up in a permanent bootscreen. so i flashed rmk gingersense r1 rom, and now i dont have cwm anymore. it just boots normal. wtfdid? do i need to reinstall cwm every time i flash the rom? any tips would be appreciated. total root newb if you couldn't tell.

inspire rooting
samuel2706 said:
HELP AND SUPPORT
From now on, i shall be conducting a help session for ANYONE with any kind of problem relating to android, be it a brick or a problem with fastboot or you can't root your phone, hell we have all been there, so maybe i could help you.
it shall be
If you have any other problems or need help or even want to learn about android and become a developer then just post in the thread, i'll get back to you. ALL OF YOU.
so don't worry if i don't get back within the first hour or so, i'll help you don't worry.
I'm not doing this for my own benefit, i'm doing it for yours, i'm patient and i understand how daunting places like this must be, i felt the same way when i first joined, i was scared about rooting my phone and still get a bit scared when it doesn't boot straight away but once you know the basics things just flow to you
i want to help you, help yourselves. so drop by with any questions about android, i'm going to be there from the moment this is posted
Click to expand...
Click to collapse
i have an inspire 4g with gingerbread i want to root it and put coredroid in it i tried bubbys method and also the hack it kit and both did not root my device i live in india and my inspire is carrier unlocked please suggest me a simple method to root my phone

vamsi4012 said:
i have an inspire 4g with gingerbread i want to root it and put coredroid in it i tried bubbys method and also the hack it kit and both did not root my device i live in india and my inspire is carrier unlocked please suggest me a simple method to root my phone
Click to expand...
Click to collapse
This should work
i know you said you had tried it but try again, DO everything as it says, even if it's as simple as case sensitive names..

Do you know any methods of rooting 2.3.4? The device I'm looking to root is a Kyocera Echo running GB 2.3.4. Gingerbreak, SuperOneClick, and z4root (lol), have all failed in rooting the device.
As far as I know, there's no locked bootloaders or anything that should be in the way except for no recovery. The Echo has fastboot if there's actually a method of rooting through there.
Thanks.

just tried it not working after some time it says device connected do u think coredroid is worth all the trouble?

Jamin13 said:
Do you know any methods of rooting 2.3.4? The device I'm looking to root is a Kyocera Echo running GB 2.3.4. Gingerbreak, SuperOneClick, and z4root (lol), have all failed in rooting the device.
As far as I know, there's no locked bootloaders or anything that should be in the way except for no recovery. The Echo has fastboot if there's actually a method of rooting through there.
Thanks.
Click to expand...
Click to collapse
Z4ROOT is apparently said to work, there isn't a lot on the forums for this device but i will keep my eyes peeled and PM you when i find something out

vamsi4012 said:
just tried it not working after some time it says device connected do u think coredroid is worth all the trouble?
Click to expand...
Click to collapse
do you have the drivers installed? download the SDK and install the drivers pal

samuel2706 said:
Z4ROOT is apparently said to work, there isn't a lot on the forums for this device but i will keep my eyes peeled and PM you when i find something out
Click to expand...
Click to collapse
That was probably for Froyo but maybe it does. I'm thinking if someone could get a custom recovery working, we could root it by just flashing Superuser.
Sent from my M9300 using XDA Premium App

i did all that i have teh sdk installed

vamsi4012 said:
i did all that i have teh sdk installed
Click to expand...
Click to collapse
Hmmm so you have tried all sorts of things? and z4root doesn't work?

mcsplatt said:
i used revolutionary cwm, loaded rmk's root zip, and wound up in a permanent bootscreen. so i flashed rmk gingersense r1 rom, and now i dont have cwm anymore. it just boots normal. wtfdid? do i need to reinstall cwm every time i flash the rom? any tips would be appreciated. total root newb if you couldn't tell.
Click to expand...
Click to collapse
Nah man you shouldn't need to install it every single time bro, you got any logcats or things you could send me?

or a recovery log? that would be awesome, if you don't know how to get these i'll teach you just pop over to the IRC if not then i'll tell you on here, it's fine

How can I sign a ROM or a bootloader for Samsung Recovery 3E?

Where was this thread 4 months ago when I was not getting any sleep. Thanks.

I'd like to try and become a developer, mainly because my Samsung Droid Charge hasn't received any AOSP love yet and I want to try and help the dev(s) that are working on it, also I would like to make my own rom. But I have no idea where to start, and I have questions like do I need Linux, do I need to/where do I learn terminal commands, how does smali/baksmali work, how to compile/decompile, how does github work, what is a toolchain, do I need to know how to code, do I need to know any languages, what is Eclipse...stuff like that. I'm a complete noob at this kind of stuff and I feel it's a bit far out of my reach but I'm willing to give it a shot if I can get a decent start. I realize it won't just happen overnight, I have the patience to keep learning and doing research to figure it out, but I would like help getting started.

@samuel2706: I have a Droid x2 and as you it has a locked bootloader. I also have a Galaxy Tab 7" which does NOT have a locked bootloader. I've been in Android for a very very long time, I am an experience flasher and rooter, but I want to get into the development side.
Could you direct me to what I need to read up on and learn about and do for me to become a developer? I would like to develop from my devices, I know that a locked bootloader steeply limits what I can do, that's why I am more interested in developing for my tablet. I mean a lot of things interest me. I look at my logcat on my devices, I see errors, and I just want to go in and fix them, I want to make my device smooth as butter, lol.
I'm also interested in finding an exploit of some sort for my Droid x2 so that I can crack it. There has gotta be a way to crack it open.
Thanks!!!

Stock rooted Gingerbread for HTC Inspire
Hey Samuel. Thanks for doing this. I got my Inspire about a weeks ago, rooted it the day I got it, and have been lurking these forums since. Saw this opportunity to ask a n00b question, and registered. So, I'm looking for a stock, rooted Gingerbread ROM. It was suggested I don't return my phone to stock, update, and then re-root. Not sure why, but I'll listen. Thanks in advance, and thanks for doing this.
-MM

[Jailbreak]Take Note Verizon - Root/Jailbreak/Recovery

Update: this will not work on the recent firmware updates.
Hey, you can't jailbreak an Android.. yeah, i know, but "Jailbreak" is a protected act under the USA DMCA Exemption of 2012 and "Unlocking" is illegal without carrier permission. There will be no misunderstandings here.
WARNING:
This is not a normal bootloader unlock. This is even higher. It's an IROM unlock. This device went from the most secure Galaxy Note 10.1 to the least secure. After performing the technique in this thread your device will allow you to flash a Justin Beiber MP3 over your bootloaders (that means a hard brick). BE VERY CAREFUL and never flash with Odin or Heimdall unless you're absolutely sure it is intended for a SCH-I925. Odin or Heimdall can easily brick your device.
Introduction
CASUAL will guide you through the process of unlocking your bootloader using exploits developed by Lee Harrison. It works on Windows, Linux, and Mac. Put your device into “Developer Mode>USB Debugging”. Click the do it button. Any problems will be addressed with updates. See the About CASUAL section below.
Overview
You are expected to be STOCK.... Stock anything, but stock. This will install a stock kernel and that may affect non-stock roms. You will need to download and execute the CASUAL application below. Make sure you're connected to the internet. Then click the Do It! button. You need Java. Do you have Java?.
Windows 32/64 Users: CASUAL will put your device into Download Mode. It will automatically flash everything. If drivers are required, jrloper's CADI (CASUAL Automated Driver installer) will handle it. Make sure you're connected to the internet.
Linux 32/64/raspberry pi Users There may be a permission escalation in order to install heimdall, either way sit back and relax. CASUAL automates the entire process.
Please run the following in a terminal first:
Mac Users: Mac works easierr than any other system at the time of this release on 32bit systems. Please report problems.
Download
Take Note Verizon CASUAL(R478b) CASUAL is used to automate the process. The exploit was developed by Elite Recognized Developer Ralekdev and packaged by AdamOutler. To run CASUAL you need Java. Do you have Java?
Note: Please don't mirror this file. Link to this thread for download. d-h.st is a fast server. If I find people mirroring old versions of CASUAL, i will throw the killswitch and their browser will bring them back here to download the new one so they end up downloading it twice, otherwise I have to support multiple versions.
Videos
Demonstration on Linux. It is roughlty the same on Windows and Mac, but if anyone wants to make a video I will put it here.
About CASUAL
CASUAL stands for Cross-platform ADB Scripting, Univeral Android Loader. CASUAL jar files are a wrapper for the CASUAL scripting language. CASUAL allows rapid and accurate deployment of hacks and exploits. CASUAL is an Open Format, meaning, you can find out as much as you need to about how it works because they're easily taken apart and modified with WinZip. CASUAL is also secure. At any time, if a serious problem is detected with any script, the kill-switch will be flipped and you will be brought to a support page (most likely here) so you can download the latest version. Otherwise for minor corrections, new CASUAL scripts can be deployed remotely.
Here's a picture of CASUAL and a Verizon GNote10.1 running Team Win Recovery
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Change Log
3May13: Initial Release
6May13: Updated Recovery to support Internal SD. -R478b

This unlock was basically identical to the second Galaxy Note 2 unlock except I had to add a few more tweaks because we're shoving a modified N8010 bootloader onto the i925.

great work guys as usual! you guys never cease to amaze me

Does this install the same TWRP version as Dees-Troy is working on in this forum? Just curious because that one is pretty rough with touch issues and it would be great to have a more functional one. I have the 8013...
Sent from my note 2

I have the U.S. Cellular i925u. Is there anyway to get this to work. I'm not interested in keeping the 4g capability. I'm ok with using WiFi only. I tried using the Casual install but it failed.

JasonGeiger said:
Does this install the same TWRP version as Dees-Troy is working on in this forum? Just curious because that one is pretty rough with touch issues and it would be great to have a more functional one. I have the 8013...
Sent from my note 2
Click to expand...
Click to collapse
This was packaged from the TWRP nightly released last night.
pro_b said:
I have the U.S. Cellular i925u. Is there anyway to get this to work. I'm not interested in keeping the 4g capability. I'm ok with using WiFi only. I tried using the Casual install but it failed.
Click to expand...
Click to collapse
CASUAL will let you root, but it won't install files that will damage your device. Even if it would, it's a bad idea. This is an IROM unlock, intended for Verizon devices only. IROM unlock means you can flash anything you want including files that destory your device.
You don't need this if you can flash custom kernels and ROMs. We have taken down all defenses here. If the U.S. Cellular version is locked down and you cant flash kernels/ROMs without it, I can release a new, updated version.

beanstown106 said:
great work guys as usual! you guys never cease to amaze me
Click to expand...
Click to collapse
This is so awesome man. Great stuff, beans is right, you guys really never cease to amaze. Now I need jellybeans Rom on my jail broken note 10.1. Ahem..................... I think we know who I'm talking to.
Sent from my HTC6435LVW using Tapatalk 2

AdamOutler said:
This was packaged from the TWRP nightly released last night.
CASUAL will let you root, but it won't install files that will damage your device. Even if it would, it's a bad idea. This is an IROM unlock, intended for Verizon devices only. IROM unlock means you can flash anything you want including files that destory your device.
You don't need this if you can flash custom kernels and ROMs. We have taken down all defenses here. If the U.S. Cellular version is locked down and you cant flash kernels/ROMs without it, I can release a new, updated version.
Click to expand...
Click to collapse
Thanks Sir. The U.S. Cellular version is locked down like the Verizon version as far as I can tell. Since the US Carriers decided to do the same crap with the bootloaders. I have root using framaroot but I'm unable to install a recovery or flash a kernel.

pro_b said:
Thanks Sir. The U.S. Cellular version is locked down like the Verizon version as far as I can tell. Since the US Carriers decided to do the same crap with the bootloaders. I have root using framaroot but I'm unable to install a recovery or flash a kernel.
Click to expand...
Click to collapse
Hit me up on an email with the output of terminal emulator command "cat /system/build.prop"

Update: rebooted windows 8 and the install went through fine.

Adam,
So here is what I am seeing, see the pictures attached

Alright guys. I'm uploading two new packages....
The first one is the latest copy of the Take Note Verizon jailbreak. It includes a modified Recovery by Dees_Troy. Our Note 10.1's are different than the other ones.
Differences: The partition structure is totally different. The kernels are totally different. This means you will soft-brick your device by flashing anything in these forums involving a recovery or a kernel other than this one. That being said..... It may be a good idea to get a separate forum. If you are interested, please start a *NEW THREAD* in General forums listing all the i925 specific threads which could be moved.
Alright. For the second part, I'm uploading a Rooted back-to-stock which I packaged from my own device before unlocking it and flashing stuff. Here's the technique used. http://forum.xda-developers.com/showthread.php?t=2082951 . This file is large so it will be a while before it's uploaded. The files included are basically everything needed to safely get back from a custom ROM and be rooted stock again.
Files included: boot.img, hidden.img, modem.bin, param.bin, recovery.img, system.img
We don't have a way to remove the modified system status currently. There is no completely back to stock.

AdamOutler said:
Alright guys. I'm uploading two new packages....
The first one is the latest copy of the Take Note Verizon jailbreak. It includes a modified Recovery by Dees_Troy. Our Note 10.1's are different than the other ones.
Differences: The partition structure is totally different. The kernels are totally different. This means you will soft-brick your device by flashing anything in these forums involving a recovery or a kernel other than this one. That being said..... It may be a good idea to get a separate forum. If you are interested, please start a *NEW THREAD* in General forums listing all the i925 specific threads which could be moved.
Alright. For the second part, I'm uploading a Rooted back-to-stock which I packaged from my own device before unlocking it and flashing stuff. Here's the technique used. http://forum.xda-developers.com/showthread.php?t=2082951 . This file is large so it will be a while before it's uploaded. The files included are basically everything needed to safely get back from a custom ROM and be rooted stock again.
Files included: boot.img, hidden.img, modem.bin, param.bin, recovery.img, system.img
We don't have a way to remove the modified system status currently. There is no completely back to stock.
Click to expand...
Click to collapse
Looking forward to trying this

So does N8010 boot loader mean N8010 ROMs or no...
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2

DJsCrIBbLe said:
So does N8010 boot loader mean N8010 ROMs or no...
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
Click to expand...
Click to collapse
no. The hardware is different. The bootloaders are similar. You need a different kernel
As a note: Never flash an N8010 bootloader. this is a SPECIAL bootloader based on the N8010 bootloader. Just pretend it has nothing to do with N8010. For all practical purposes, this is an I925 bootloader we crafted out of an N8010 because we didn't have a i925 to work with.

Ok thanks, mostly just curious as i own the N8013 but considered the verizon version or selling and getting the unlocked international.

Thanks a ton Adam! Worked perfectly.
So if I have this correctly, we will be running stock until we get a dev to start working on our variant? I would assume that the other roms wouldn't install correctly with the partitions being different correct?

*Madmoose* said:
Thanks a ton Adam! Worked perfectly.
So if I have this correctly, we will be running stock until we get a dev to start working on our variant? I would assume that the other roms wouldn't install correctly with the partitions being different correct?
Click to expand...
Click to collapse
Yeah... don't flash nothin' or you will die. . We need a ROM dev.

Great work Adam, almost sent you a PM begging you to take this project on about 6 weeks ago... thanks!
But I had some problem as I ran the script, it stopped after it had rebooted and was stuck in Download Mode and asked me for my XDA username for some pastebin. The last information in that pastebin was:
Initialising connection...
Detecting device...
Claiming interface...
Setting up interface...
Checking if protocol is initialised...
Protocol is not initialised.
Initialising protocol...
ERROR: Protocol initialisation failed!
Releasing device interface...
[ERROR]
[Heimdall Error Report] Detected:
Heimdall failed to initialize protocol; Script halted
[/Heimdall Error Report]
[DEBUG]HALT RECEIVED
[DEBUG]Finishing remaining commands:$SENDLOG
[DEBUG]Sendlog Command Issued!
No remaining commands
[DEBUG]Pastebin Login Successful
Click to expand...
Click to collapse
After unpluging and holding the power down for a few secs it rebooted as usually, but I dont know if it completed or not... how do I know if the bootloader got unlocked?
If you would like to see the pastebin then I'd be glad to be able to help, just let me know.
Thanks again,

Snarlster said:
Great work Adam, almost sent you a PM begging you to take this project on about 6 weeks ago... thanks!
But I had some problem as I ran the script, it stopped after it had rebooted and was stuck in Download Mode and asked me for my XDA username for some pastebin. The last information in that pastebin was:
After unpluging and holding the power down for a few secs it rebooted as usually, but I dont know if it completed or not... how do I know if the bootloader got unlocked?
If you would like to see the pastebin then I'd be glad to be able to help, just let me know.
Thanks again,
Click to expand...
Click to collapse
Use a different usb cable and port on your computer. There is a problem with the communications.

[Q] Modding on HTC 10

Hi,
any leak, prevision about modding for this device?
I mean, will CM, AOSPA, AOKP etc support it officially? How is the situation with the other HTC's flagships?
Can it be unlocked as M7 with HTC dev site?
Thank you guys

davide136 said:
Hi,
any leak, prevision about modding for this device?
I mean, will CM, AOSPA, AOKP etc support it officially? How is the situation with the other HTC's flagships?
Can it be unlocked as M7 with HTC dev site?
Thank you guys
Click to expand...
Click to collapse
Bit early considering we aren't even positive what the final product's hardware will entirely be Can't wait though

can't wait too that's why i have written xD i don't know what to buy, my s6 is the worst phone for modding and updates, 1 year and i still have not rooted anything! I was getting used to root the first day when i was buying new phones don't want my next phone to be like s6

davide136 said:
can't wait too that's why i have written xD i don't know what to buy, my s6 is the worst phone for modding and updates, 1 year and i still have not rooted anything! I was getting used to root the first day when i was buying new phones don't want my next phone to be like s6
Click to expand...
Click to collapse
Exactly that's what I'm afraid of, too. If I decide to buy a new phone, I'd like to compile ROMs for it by myself, too, but therefore the vendor, device and kernel tree need to be published by HTC. I've just been looking around how custom development for the HTC One M9 looks like. Although I couldn't find many ROMs, there are official Cyanogenmod versions and open device and kernel trees. Thus I could compile many ROMs for the One M9. This gives me hope regarding the HTC 10. The Galaxy S6 instead didn't have no huge moding posibilities. There's only an unofficial, unstable device and kernel tree alongside a bugy CM-version. Just like the S6 the S7 probably won't get huge development support as well. This is what gives me hope regarding the HTC 10.
The only question I'm currently asking myself is if I should buy the HTC 10 or wait for the Oneplus 3 which will be published later in Q2 2016. Compared to the OP2 and OP1 it'll be a bit more expensive but it'll also be better equiped. Furthermore the price will probably be much lower than the price of the HTC 10. What are your expectations and what have you been able to definitely find out so far?

I'm still tryng to figure out what to do...lg has dropped support for rooted or bootloader unlocked device in italy, and the g5 seems to be a bit strange te me, i mean, it's not as premium as g4..regarding oneplus devices, for the 1 and 2 i read about bad screens and something else wich i don't remember, never saw one...i'd prefer staying on a strong brand...samsung obviously is exhiliated from any decision...sony maybe but no xD never liked the screens in the past...
My old nexus 5 make me wish about a decent nexus around 5" screen, I'd really love it, especially powered from a snapdragon 820 cpu..
Mi5 is lovable, but, you know...it's xiaomi...china brand, china support, 30 days for travelling a device if something happens, and that is for 2 times...its frightening xD
Htc 10 seems to be the best choice, ut will surely be premium, even if it does not have a good camera i don't care, just bought an eos 700d xD i just hope there will be a lot of modding, that is why i asked here
Htcdev.com is still working good for all the other htc, it must have decent modding, i think I'll go for it. At least, that's what I'm thinking now...but who knows
Inviato dal mio SM-G920F utilizzando Tapatalk

Yeah, Xiaomi is a brand I've been looking at over the last two years. I recommended Xiaomi phones to friends who wanted to have good and cheap devices. They are lucky all together but the only phone by Xiaomi I'd buy is the Mi Note Pro as a phone should have 5,7 inch in my opinion. I'd also like to have an AMOLED-Display in my next device so I hope HTC will release a bigger version of the 10 as well. The LG G5 is not really what I am looking for since it's a bit strange to have several components you can choose from. I think I'll buy a OP3 when it's published as it'll probably be more developer friendly but maybe the 10 by HTC will convince me, too. I'm really excited about the upcoming devices especially because my Nexus 4 from 2012 becomes slower and slower. Very anoying. Maybe a new Nexus will be released at the Google IO this year. This would be awesome. Anyway, I hope the potent upcoming phones will come sooner than later as I don't know how long my N4 will survive.

Very informed you guys are. I like this thread cause' I think a lot like you.
Sent from my Nexus 5 using XDA-Developers mobile app

Also looking for an answer on this: I was tempted by the Galaxy S7, but the huge issues I've had running anything but TouchWiz based ROMs on my S4 (and so issues running anything Marshmallow based) have put me right off.
How easily moddable have HTC phones been in recent years?

Rohaq said:
Also looking for an answer on this: I was tempted by the Galaxy S7, but the huge issues I've had running anything but TouchWiz based ROMs on my S4 (and so issues running anything Marshmallow based) have put me right off.
How easily moddable have HTC phones been in recent years?
Click to expand...
Click to collapse
The M7, M8, M9, and A9 are all very easy to do basic modding on. Getting s-off and deep modding is a different story. On the M8, at least, you can flash custom ROMs and kernels without s-off, so basically everything most people needs

Anonaru said:
The M7, M8, M9, and A9 are all very easy to do basic modding on. Getting s-off and deep modding is a different story. On the M8, at least, you can flash custom ROMs and kernels without s-off, so basically everything most people needs
Click to expand...
Click to collapse
Well, looks like it paid to wait then, come on, release day!

Anonaru said:
The M7, M8, M9, and A9 are all very easy to do basic modding on. Getting s-off and deep modding is a different story. On the M8, at least, you can flash custom ROMs and kernels without s-off, so basically everything most people needs
Click to expand...
Click to collapse
does it mean that with m9 if you do not s-off you can't touch system, boot or recovery partition? ( i'm still leaving in the time when you did fastboot oem unlock and everything was ok )

davide136 said:
does it mean that with m9 if you do not s-off you can't touch system, boot or recovery partition? ( i'm still leaving in the time when you did fastboot oem unlock and everything was ok )
Click to expand...
Click to collapse
No, the things you can't do without S-Off are:
*flash unsigned firmware packages
*flash firmware packages that don't match CID/MID
*flash RUUs that don't match CID/MID
*change CID/MID
*restore "locked" status (without you can only get "relocked" status)
*restore "software status: official" flag in bootloader (flag sets to "software status: modified" if you flash anything)
What you can do without S-Off:
*unlock bootloader (via HTCdev)
*flash recovery
*root (via superSU package or your favorite custom ROM)
*flash ROMs

0verdaflow said:
When is this gonna be released ??
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Click to expand...
Click to collapse
we will know tomorrow on the announcement but the leaks lead so far for beginning of May release

JEANRIVERA said:
we will know tomorrow on the announcement but the leaks lead so far for beginning of May release
Click to expand...
Click to collapse
Maybe there's another HTC phone to come in early may, hopefully a phablet but let's see...

Anyone know how we will get root on the unlocked version?

km8j said:
Anyone know how we will get root on the unlocked version?
Click to expand...
Click to collapse
By flashing TWRP Recovery then flashing the current SuperSU package ( or use the built-in TWRP option to flash SuperSU if available)

Behold_this said:
By flashing TWRP Recovery then flashing the current SuperSU package ( or use the built-in TWRP option to flash SuperSU if available)
Click to expand...
Click to collapse
Is this a big process? Is everything already available? Does any part of the rooting process wipe the device? If so, may make more sense to just do it right out of the box to avoid losing info

TWRP can already be found and downloaded; at least if one will look for it at the right place . I already downloaded it. SuperSU can as well be downloaded for MM devices. By this I'd guess the root procedure can be done as it always has been.
Sent from my HTC One M9 using XDA Labs

HTCNerdYoda said:
TWRP can already be found and downloaded; at least if one will look for it at the right place . I already downloaded it. SuperSU can as well be downloaded for MM devices. By this I'd guess the root procedure can be done as it always has been.
Click to expand...
Click to collapse
But does the bootloader unlock wrote y the phone?

km8j said:
But does the bootloader unlock wrote y the phone?
Click to expand...
Click to collapse
If you meant wipe the phone, then yes, it does.

[REQUEST] We need havos os for op7t (hotdogb)

Hello my friends, we want to participate in the largest number of members to support oneplos 7T ( hotdogb ) For his support of Rom havos os
As you know, support stopped at the beginning of the year and we want support for this Rom .
Do you support the idea?
تم الإرسال من HD1903 باستخدام Tapatalk

slsl20005 said:
Hello my friends, we want to participate in the largest number of members to support oneplos 7T ( hotdogb ) For his support of Rom havos os
As you know, support stopped at the beginning of the year and we want support for this Rom .
Do you support the idea?
تم الإرسال من HD1903 باستخدام Tapatalk
Click to expand...
Click to collapse
The dev of those old builds doesn't have the device. He was blind building and decided not to continue. So I don't think this will happen unless you know someone willing to maintain for the device.

I support too. I miss using Havoc OS after shifting from OP6 to OP7T.

shaunakdsilva said:
I support too. I miss using Havoc OS after shifting from OP6 to OP7T.
Click to expand...
Click to collapse
The same thing [emoji21]
تم الإرسال من HD1903 باستخدام Tapatalk

I'm thinking about buying the 7T but I'm not sure because I have been using Havoc for years on my Moto and really love it. Hope Havoc comes to 7T soon.

havoc? that's a mess...why people like that [email protected]#@%

We've got RR

There is no scope for development of more roms unless a proper working recovery is available on op7t

0402Aman said:
There is no scope for development of more roms unless a proper working recovery is available on op7t
Click to expand...
Click to collapse
There is no need of recovery to have roms developed for this device. There are already two fully functional roms MSM Xtended and RR available and being used.
The issue anyway I believe is a lot of developers choose to go with Pro series like 7Tpro 7Pro or 8 series. So less developers results in less development.
Sent from my HD1901 using Tapatalk

Who wants to build when flashing is such a pita no proper functioning twrp/recovery is the main reason we have such limited development for 7t series . Also Android 10 out of the box hasn't helped. I believe the decryption issued faced in the development of twrp for 7t isn't present in op8 or the Nord. The issue is with OnePlus and how they have implemented broken decryption on the 7t but not on the op8 or Nord.

slsl20005 said:
Hello my friends, we want to participate in the largest number of members to support oneplos 7T ( hotdogb ) For his support of Rom havos os
As you know, support stopped at the beginning of the year and we want support for this Rom .
Do you support the idea?
تم الإرسال من HD1903 باستخدام Tapatalk
Click to expand...
Click to collapse
No flame, but that was legit my genuine reaction at this post
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
That rom was (and probably still is) just a big mess, why would you even want something like that when you have already other better options such as AOSiP?
If it will come, it will come, i don't think there's need to make a post just to let other people know you want it, that's my 2 cents
See ya.

0402Aman said:
There is no scope for development of more roms unless a proper working recovery is available on op7t
Click to expand...
Click to collapse
TWRP has absolutely nothing to do with lack of development.
People who owns this device simply do not have enough resources to build ROMs. The actual work is already laid out.
---------- Post added at 11:26 AM ---------- Previous post was at 11:23 AM ----------
a g bell said:
Who wants to build when flashing is such a pita no proper functioning twrp/recovery is the main reason we have such limited development for 7t series . Also Android 10 out of the box hasn't helped. I believe the decryption issued faced in the development of twrp for 7t isn't present in op8 or the Nord. The issue is with OnePlus and how they have implemented broken decryption on the 7t but not on the op8 or Nord.
Click to expand...
Click to collapse
It's a PITA? Tell whatever rom "dev" to build correctly then.
I installed a custom rom with literally 2 commands, it was easier without TWRP if I'm being honest.
Hint; AOSiP developer knows what he is doing.
(And decryption is only a problem on OOS so unrelated to custom ROMs).
And, read my comment above.

Why not ask for lineage OS? I already heard the news of carbon rom support coming months ago. We got omni too but God knows what's happening. This device is going down to be the least active custom development in One Plus history....

Lossyx said:
TWRP has absolutely nothing to do with lack of development.
People who owns this device simply do not have enough resources to build ROMs. The actual work is already laid out.
---------- Post added at 11:26 AM ---------- Previous post was at 11:23 AM ----------
It's a PITA? Tell whatever rom "dev" to build correctly then.
I installed a custom rom with literally 2 commands, it was easier without TWRP if I'm being honest.
Hint; AOSiP developer knows what he is doing.
(And decryption is only a problem on OOS so unrelated to custom ROMs).
And, read my comment above.
Click to expand...
Click to collapse
Sorry you installed and fixed any possible issues locally without a pc or another device with fastboot enabled ? the fact is flashing is easier with twrp working . I wouldn't test my go to Devs build for this reason not because it would be unstable but he is not that arrogant to think his build couldn't have issues. I use my device as a daily driver and don't want to carry otg and two phones around with me in case l needs fastboot. Sorry but l disagree but respect what you mean.

a g bell said:
Sorry you installed and fixed any possible issues locally without a pc or another device with fastboot enabled ? the fact is flashing is easier with twrp working . I wouldn't test my go to Devs build for this reason not because it would be unstable but he is not that arrogant to think his build couldn't have issues. I use my device as a daily driver and don't want to carry otg and two phones around with me in case l needs fastboot. Sorry but l disagree but respect what you mean.
Click to expand...
Click to collapse
>Who wants to build when flashing is such a pita no proper functioning twrp/recovery
This is what you said. I am simply correcting you that it's completely false.
I understand that TWRP is convenient in case any issues appear, however, I have been running an unofficial build for the last 5 months now (including 3 weeks where I was without PC) and never had any issues that forced to me clean flash(or any use of twrp/fastboot).
Most ROMs don't and shouldn't have any issues that cause clean/dirty flash, rather in most cases, it's a user error, which is completely unrelated on why the lack of ROM development.

Lossyx said:
>Who wants to build when flashing is such a pita no proper functioning twrp/recovery
This is what you said. I am simply correcting you that it's completely false.
I understand that TWRP is convenient in case any issues appear, however, I have been running an unofficial build for the last 5 months now (including 3 weeks where I was without PC) and never had any issues that forced to me clean flash(or any use of twrp/fastboot).
Most ROMs don't and shouldn't have any issues that cause clean/dirty flash, rather in most cases, it's a user error, which is completely unrelated on why the lack of ROM development.
Click to expand...
Click to collapse
Most roms shouldn't have issues most don't but sometimes when updates happen things go borked as l am sure you know. To say what l have said is completely false kind of contradicts saying twrp is convenient meaning finding a device with fastboot can be more of a pita than simply booting twrp recovery. I am sure that there are many people who have bought the op7t and are disappointed that twrp is the way it is.
Betting there put off by having to use command line to do stuff that they have done on most of there previous devices using twrp.
Some ROM /kernel developers build to share and get known others don't of course. The ones that do would be thinking what's the point of building if only 10 people are going to flash.Which in my opinion will reduce the amount of roms/kernels being developed for the op7t.

The blame is simply in oneplus's lap.i have read a post stateing the next update description will be fixed I'd post a link but about to crash.leta hope they were truthful

rob420p said:
The blame is simply in oneplus's lap.i have read a post stateing the next update description will be fixed I'd post a link but about to crash.leta hope they were truthful
Click to expand...
Click to collapse
Lol was that my post in twrp thread?

a g bell said:
Lol was that my post in twrp thread?
Click to expand...
Click to collapse
By truthful I sent oneplus

Lossyx said:
TWRP has absolutely nothing to do with lack of development.
People who owns this device simply do not have enough resources to build ROMs. The actual work is already laid out.
---------- Post added at 11:26 AM ---------- Previous post was at 11:23 AM ----------
It's a PITA? Tell whatever rom "dev" to build correctly then.
I installed a custom rom with literally 2 commands, it was easier without TWRP if I'm being honest.
Hint; AOSiP developer knows what he is doing.
(And decryption is only a problem on OOS so unrelated to custom ROMs).
And, read my comment above.
Click to expand...
Click to collapse
Me and a few others built everything over the last 10 months since 7t release. Mostly we all settled on something to stick with. Twrp is no issue, I agree, but people acting like there is none is kinda shortsighted. The Chinese twrp is absolutely impeccable on oos or custom.

Question Lack of development?

There has been 0 talk about any ROMs or development for the OP9 and it's been over a month since release. Does anyone know if any developers are working on one??

The OP9 and OP9 Pro don't even have unofficial or official TWRP support yet, so a custom ROM is kinda out of the question until TWRP is on the devices. OP9 Pro literally just got it's first custom kernel 2 days ago. I don't know what the time frame is for custom ROM development but a lot of it hinges on getting TWRP support for the phones.
Side note: You said OP9 in the OP9 Pro forums so I'm gonna assume you were referring to the OP9 Pro. Regardless my statement about needing TWRP support first applies to both phones.

GreaterLesser said:
The OP9 and OP9 Pro don't even have unofficial or official TWRP support yet, so a custom ROM is kinda out of the question until TWRP is on the devices. OP9 Pro literally just got it's first custom kernel 2 days ago. I don't know what the time frame is for custom ROM development but a lot of it hinges on getting TWRP support for the phones.
Side note: You said OP9 in the OP9 Pro forums so I'm gonna assume you were referring to the OP9 Pro. Regardless my statement about needing TWRP support first applies to both phones.
Click to expand...
Click to collapse
TWRP is absolutely not necessary and will most likely never come out for later OP devices, including the 9, unless they figure out the decryption problem. See the 8's etc, plenty of dev and none of the TWRP.
Regarding dev, it's happening, but no need for discussion here until something is at least in a semi-stable beta build.

craznazn said:
TWRP is absolutely not necessary and will most likely never come out for later OP devices, including the 9, unless they figure out the decryption problem. See the 8's etc, plenty of dev and none of the TWRP.
Regarding dev, it's happening, but no need for discussion here until something is at least in a semi-stable beta build.
Click to expand...
Click to collapse
I apologize for my lack of knowledge of what happened in the OnePlus 8 scene as I didn't have that phone. I came from the 6T. But looking through the 8, 8 Pro, and 8T forums, it seems a custom recovery is still needed for custom ROMs. Only difference was the custom recovery was provided by the ROM Dev and not TWRP.

It's early in the game.... will be happening!

ddizzy81 said:
There has been 0 talk about any ROMs or development for the OP9 and it's been over a month since release. Does anyone know if any developers are working on one??
Click to expand...
Click to collapse
We don't have a TWRP build yet, I've been looking to build one but there's a problem with Android Image Kitchen which should hopefully be fixed soon, I'm guessing that's why no-one else has built a recovery. You can read more about it here.
Custom roms are kinda a non-starter without TWRP (or another custom recovery)
OnePlus has been messing up with their source for a while now too, not to mention that we're still getting regular updates to the original release which might mess with kernels too.
We might be another month before you'll start seeing enough stability to start getting custom roms.
EDIT : Looks like AIK might be working properly now, gonna have a look and see if I can get a TWRP build working, although there's no other phones with the same resolution so that might be a problem to get some resources. LG G3 has a similar resolution but not exactly the same, it's very important for the touchscreen setup for TWRP or else the buttons on screen won't be where you're actually tapping.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
For anyone else who fancies trying their hand at it, there's a porting guide here.

To add to what @craznazn said, a custom recovery isn't 100% necessary for custom ROMs. The 7T didn't require it to flash any, as a fastboot method is doable. Developing them is another story, though. Some custom ROMs were based on OOS, while AOSP ones still had some bases from OOS (YAAP, for example, was a Pixel-themed ROM but required you to have OOS11, in some shape or form, installed prior to flashing it because it needed vendor files and so on.

djsubterrain said:
We don't have a TWRP build yet, I've been looking to build one but there's a problem with Android Image Kitchen which should hopefully be fixed soon, I'm guessing that's why no-one else has built a recovery. You can read more about it here.
Custom roms are kinda a non-starter without TWRP (or another custom recovery)
OnePlus has been messing up with their source for a while now too, not to mention that we're still getting regular updates to the original release which might mess with kernels too.
We might be another month before you'll start seeing enough stability to start getting custom roms.
EDIT : Looks like AIK might be working properly now, gonna have a look and see if I can get a TWRP build working, although there's no other phones with the same resolution so that might be a problem to get some resources. LG G3 has a similar resolution but not exactly the same, it's very important for the touchscreen setup for TWRP or else the buttons on screen won't be where you're actually tapping.
View attachment 5298703
For anyone else who fancies trying their hand at it, there's a porting guide here.
Click to expand...
Click to collapse
The Samsung Galaxy S20, and S20 Plus have a very close resolution to the OP9P
OP9P: 1440x3216
SGS20/SGS20+: 1440x3200
And they already have an unofficial twrp build too.
SGS20/SGS20+ TWRP:
[RECOVERY][UNOFFICIAL] TWRP for Galaxy S20 Series (Snapdragon)
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and...
forum.xda-developers.com
Hope this helps.

GreaterLesser said:
The Samsung Galaxy S20, and S20 Plus have a very close resolution to the OP9P
OP9P: 1440x3216
SGS20/SGS20+: 1440x3200
And they already have an unofficial twrp build too.
SGS20/SGS20+ TWRP:
[RECOVERY][UNOFFICIAL] TWRP for Galaxy S20 Series (Snapdragon)
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and...
forum.xda-developers.com
Hope this helps.
Click to expand...
Click to collapse
Sorry to say. But portions are what we are talking about. Resolution has no bearing on getting TWRP working. Ex op7tpro

toolhas4degrees said:
Sorry to say. But portions are what we are talking about. Resolution has no bearing on getting TWRP working. Ex op7tpro
Click to expand...
Click to collapse
Portions...? As in dimensions? It is true the screens are different sizes, as well.
In regards to OP's post that there's been 0 development talk, well, not exactly zero, as unlocking and rooting, as well as conversion from T-Mobile to global, enabling dual-SIM, and the MSM and QPST tools needed for such, have been ongoing for some time. There's no custom ROMs, sure, and I get that a custom kernel was just released, but a massive part of development is simply discussion, throwing around ideas, research, testing, etc. It also helps if more devs happen to purchase our particular device (and thankfully this is something we won't have to worry about for long). It's worse when a device gets little to no development because it simply isn't popular enough to warrant much development. I do get the sentiment that it's been a while, but I guess we'll just have to be patient.

GuyInDogSuit said:
Portions...? As in dimensions? It is true the screens are different sizes, as well.
In regards to OP's post that there's been 0 development talk, well, not exactly zero, as unlocking and rooting, as well as conversion from T-Mobile to global, enabling dual-SIM, and the MSM and QPST tools needed for such, have been ongoing for some time. There's no custom ROMs, sure, and I get that a custom kernel was just released, but a massive part of development is simply discussion, throwing around ideas, research, testing, etc. It also helps if more devs happen to purchase our particular device (and thankfully this is something we won't have to worry about for long). It's worse when a device gets little to no development because it simply isn't popular enough to warrant much development. I do get the sentiment that it's been a while, but I guess we'll just have to be patient.
Click to expand...
Click to collapse
Partitions sorry typo. Also they just released kernel sources not very long ago. In order to build you need these. The dev here had this up and running on his device for a while, but just like ROM devs the first two or three bases they make are not for public and take a long time to work out bugs. Secondly twrp is not required to flash a custom ROM did it via fastboot on my op7tpro. Development is up to owners. You have an unlocked bootloader and kernel sources. If everyone is *****in about development start developing. Download a Linux distro or wubi and and build one for the community. Everyone *****es and doesn't contribute.

toolhas4degrees said:
Partitions sorry typo
Click to expand...
Click to collapse
Ahhh. That makes more sense now.

GreaterLesser said:
The OP9 and OP9 Pro don't even have unofficial or official TWRP support yet, so a custom ROM is kinda out of the question until TWRP is on the devices. OP9 Pro literally just got it's first custom kernel 2 days ago. I don't know what the time frame is for custom ROM development but a lot of it hinges on getting TWRP support for the phones.
Side note: You said OP9 in the OP9 Pro forums so I'm gonna assume you were referring to the OP9 Pro. Regardless my statement about needing TWRP support first applies to both phones.
Click to expand...
Click to collapse
Op8 doesn't even have a working twrp for A11 yet. So that's not it at all. Twrp does nothing for our devices as far as roms or kernels. You flash a kernel through a kernel manager and All the roms flash through fastboot & fastbootd. That's def not it. But it will however take time. We need msm tools prior to messing with things anyway. Or we will all be in a brick like state. And a main dev for aospa which is Paranoid Android has a 9 . That will be soon I'm guessing.

mattie_49 said:
Op8 doesn't even have a working twrp for A11 yet. So that's not it at all. Twrp does nothing for our devices as far as roms or kernels. You flash a kernel through a kernel manager and All the roms flash through fastboot & fastbootd. That's def not it. But it will however take time. We need msm tools prior to messing with things anyway. Or we will all be in a brick like state. And a main dev for aospa which is Paranoid Android has a 9 . That will be soon I'm guessing.
Click to expand...
Click to collapse
Thanks - Someone already explained this earlier.