Develop Bugs

OCLF is not safe, DO NOT TRY IT

DO NOT TRY OCLF, if you can not go to factory reset.
I have read almost all the threads answer etc. on many forums, How many people faced the problem and I think I am latest victim after having OCLF, phone doesn't start anymore, does not go in hard reset..nothing just vibration and 2 lights in bottom nothing else.
It just screwed me, OCLF 2.2, with Z4Root , Android 2.2 froyo on SGS....installed and you are gone. still you want it go ahead, feel free....I am angry on myself not on anybody else but I thought, I better write something to save few people at least, opposed to other people who are also bricked and praised the fix to not to stand alone.
Finally I gave phone back, not sure if I get a new one or get same repaired ( in warranty or I have to pay if they can detect that It was me not the hardware or something else...), will post what happens but for now, its not safe, do not go for it and remember there is very thin line between bravery and foolishness. decide yourself.

There are numerous ways to recover your SGS, all you had to do was have a read on here, don't panic and use the search function.
I'm new to all this and i've been in the same position as you and have thought I had bricked my phone at least 5 or more times. But thanks to others on XDA they have same me and my SGS )

sorry but if you dont know what you are doing, why are you doing it?
and btw there are alot of things you can do to recover your phone, even if its totally bricked.
you saying you read all threads etc? i dont think so cuz then you would know what to do.
and OCLF IS SAFE, if you know what you doing and have to do if its going wrong.
ps: if you need help, pm me i will explain you what to do, but only if you have the phone in front of you.

There should be a big banner in the development section which says "Don't try these if you are a n00b and not willing to read and learn before flashing anything!"

That is a thoughtless, misinformed thread title maligning a good developer's excellent work.
Think hard before you post in future........
doc jpy 7.1, jpx, k12i.

OCLF pertains to the Software Level. I see no reason for the Hardware to be affected. You should always be able to go the Download Mode after removing the battery for sometime.

i just say OMG.. i "bricked" (like you) my device about 7-8 times... no problem! i also BRICKED my device 1 time... no problem! don't panic, sgs is very strong! use search function of forum, the problem is not OCLF itself, is a "dead" sd-card (i don't know exactely, i'm a noob) it's a problem connected with the mount of an internal memory, i personally discovered that it might be also connected with a wrong flash of the csc (personal experience!)
Next time (yes it will be) don't panic there's a solution

No panic, just another way of adding some more info for OCLF
Well well well, I am not in panic, I have had galaxy for 5 days only and of-course a new comer for Android, I didn't hesitate for the fix, tried to figure out pros and cons (unfortunately didn't see complains for the problem I had after reboot, until I became the victim) and to be clear not trying to blacken the founder of OCLF with due respect.
Thanks for the fellows offering help, I don't have phone with me as I was not willing to play around with other fixes as I can get it fixed by service center but it would be great if you can blog about it or mention steps here for a problem of a phone stuck on Galaxy screen and can't go in recovery mode and does not connect with odin. what you get is black screen, 2 lightning button in the bottom and vibration when you press any key in bottom or screen.
I was already expecting the several responses and staring eyes but if its safe then why you have so many thread complaining a frozen phone. If this fix is safe then why its removed from Market? (arrg Google norms..but for a good thing and open source system, don''t understand, make it an enhancement, put it already in ROM)
and why OCLF app does not warn, if you have a temp root or permanent root? before making the fix. if its not possible in this context then place info window as it will fail with temp root.
ODIN thing will only work with rooted phone what if its temp rooted and do you want any user to open their phone's mother board for making some soldering to re flash.
Please somebody make a detailed instruction page, if its safe and get proper steps and don'ts list, I won't mind doing it again once I get phone back and keeping fingers crossed that they won't charge me for this out of warranty. Not sure I'll get replacement or repaired one.
Again its not safe until and unless in any case you are ready for using other fixes (which may or may not be applicable for your situation)to fix the phone.There are chances that you loose important data(if not backup). Go for it, if you have enough time and nothing else to do, if it works, good for you, if not don't panic..............
and don;t forget its not your development machine, open in front of you, for free by company, which has corrupted passwd file or something and not booting up....it's your costly new smart phone.
yeah criticize me but its doesn't feel nice when your brick your new phone.
in the end some more things to remember based on my exp for prevention:
1. Back up data
2. make sure you have hard reset option available
3. Root permanent
Please add more if you know. anyways thanks for all the responses.

Tried once to have a bricked phone, my first try actually..
Formated the system by mistake, to high i guess.. LOL..
Non the less, had black-screen ofc, System format, in more than 5 hours, till I tried odin with the org firmware, and brick gone
Sure, thought Sh!!!!!t at first, but then started reading, that was what I've spent the 5 hours on, and 7mins later up and running.. No worries for brick no more
So, think you could have made it your self, instead of returning it, sry
Or maybe you couldn't go into DL mode? I could with formated system?
Just like dhiru1602 wrote, DL mode should be in place, it was on mine like I said

SandeepSharma said:
Well well well, I am not in panic, I have had galaxy for 5 days only and of-course a new comer for Android, I didn't hesitate for the fix, tried to figure out pros and cons (unfortunately didn't see complains for the problem I had after reboot, until I became the victim) and to be clear not trying to blacken the founder of OCLF with due respect.
Thanks for the fellows offering help, I don't have phone with me as I was not willing to play around with other fixes as I can get it fixed by service center but it would be great if you can blog about it or mention steps here for a problem of a phone stuck on Galaxy screen and can't go in recovery mode and does not connect with odin. what you get is black screen, 2 lightning button in the bottom and vibration when you press any key in bottom or screen.
I was already expecting the several responses and staring eyes but if its safe then why you have so many thread complaining a frozen phone. If this fix is safe then why its removed from Market? (arrg Google norms..but for a good thing and open source system, don''t understand, make it an enhancement, put it already in ROM)
and why OCLF app does not warn, if you have a temp root or permanent root? before making the fix. if its not possible in this context then place info window as it will fail with temp root.
ODIN thing will only work with rooted phone what if its temp rooted and do you want any user to open their phone's mother board for making some soldering to re flash.
Please somebody make a detailed instruction page, if its safe and get proper steps and don'ts list, I won't mind doing it again once I get phone back and keeping fingers crossed that they won't charge me for this out of warranty. Not sure I'll get replacement or repaired one.
Again its not safe until and unless in any case you are ready for using other fixes (which may or may not be applicable for your situation)to fix the phone.There are chances that you loose important data(if not backup). Go for it, if you have enough time and nothing else to do, if it works, good for you, if not don't panic..............
and don;t forget its not your development machine, open in front of you, for free by company, which has corrupted passwd file or something and not booting up....it's your costly new smart phone.
yeah criticize me but its doesn't feel nice when your brick your new phone.
in the end some more things to remember based on my exp for prevention:
1. Back up data
2. make sure you have hard reset option available
3. Root permanent
Please add more if you know. anyways thanks for all the responses.
Click to expand...
Click to collapse
Did u read the info screen that pops up when u first started oclf? I guess u didnt coz there are very clear instructions on what u have to do to apply the lagfix sucessfully...
Edit: btw ockf is on market again he just had to remove the abillity to root...
Sent from my GT-I9000 using Tapatalk

SandeepSharma said:
Well well well, I am not in panic, I have had galaxy for 5 days only and of-course a new comer for Android, I didn't hesitate for the fix, tried to figure out pros and cons (unfortunately didn't see complains for the problem I had after reboot, until I became the victim) and to be clear not trying to blacken the founder of OCLF with due respect.
Thanks for the fellows offering help, I don't have phone with me as I was not willing to play around with other fixes as I can get it fixed by service center but it would be great if you can blog about it or mention steps here for a problem of a phone stuck on Galaxy screen and can't go in recovery mode and does not connect with odin. what you get is black screen, 2 lightning button in the bottom and vibration when you press any key in bottom or screen.
I was already expecting the several responses and staring eyes but if its safe then why you have so many thread complaining a frozen phone. If this fix is safe then why its removed from Market? (arrg Google norms..but for a good thing and open source system, don''t understand, make it an enhancement, put it already in ROM)
and why OCLF app does not warn, if you have a temp root or permanent root? before making the fix. if its not possible in this context then place info window as it will fail with temp root.
ODIN thing will only work with rooted phone what if its temp rooted and do you want any user to open their phone's mother board for making some soldering to re flash.
Please somebody make a detailed instruction page, if its safe and get proper steps and don'ts list, I won't mind doing it again once I get phone back and keeping fingers crossed that they won't charge me for this out of warranty. Not sure I'll get replacement or repaired one.
Again its not safe until and unless in any case you are ready for using other fixes (which may or may not be applicable for your situation)to fix the phone.There are chances that you loose important data(if not backup). Go for it, if you have enough time and nothing else to do, if it works, good for you, if not don't panic..............
and don;t forget its not your development machine, open in front of you, for free by company, which has corrupted passwd file or something and not booting up....it's your costly new smart phone.
yeah criticize me but its doesn't feel nice when your brick your new phone.
in the end some more things to remember based on my exp for prevention:
1. Back up data
2. make sure you have hard reset option available
3. Root permanent
Please add more if you know. anyways thanks for all the responses.
Click to expand...
Click to collapse
READ!!!!!!!!!!!!!!!!! SEARCH!!!!!!!!!!!!!!!!!!!!!!!!!!!! READ!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! SEARCH!!!!!!!!!!!!!!!!!!!!!!!!! BREATH IN!!!!!!!!!!!!!!!!!!!!!!! BREATH OUT!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
1. You didn't read instructions clearly
2. You created a misleading thread title
3. You are now asking for step by step instructions when there is already numerous guides and answers on how to get your phone going again
4. You now look like a lazy, ignorant and upset kid that broke his new toy because he was too rough with it and now expects to be spoon fed instead of actually learning from his mistake.
5. I am not usually this hard on anybody but I am annoyed by this thread

you're funny. maybe you can discuss why it's so bad with RyanZA himself?
herpderp.

If you hadn't have badmouthed his work, you'd have found Ryan extremely helpful, in fact, he's such a good bloke, he'd probably still help you if it was necessary.
doc jpy 7.1, jpx, k12i.

@OP: Please change the thread's title to something more respectful for RyanZA's hard work.
A good title like : "too lazy to read before doing something potentially dangerous to my expensive smartphone, I've bricked it (in fact probably not...) while trying OCLF..."
___________________________________
Sent from my GT-I9000 ××× DocRambone®'s XXJPY_Kitchen, Hardcore®'s SpeedMod K12I, ext4-all ××× using Tapatalk Pro®

its ok now guys, he is new to android and galaxy. Close this thread pls.
pm me if you got your phone back and i still will help you and explain everything.

Just plug it into the computer and use adb reboot recovery. Should work, it did for me.
Sent from my GT-I9000 using XDA App

madfix said:
@OP: Please change the thread's title to something more respectful for RyanZA's hard work.
A good title like : "too lazy to read before doing something potentially dangerous to my expensive smartphone, I've bricked it (in fact probably not...) while trying OCLF..."
___________________________________
Sent from my GT-I9000 ××× DocRambone®'s XXJPY_Kitchen, Hardcore®'s SpeedMod K12I, ext4-all ××× using Tapatalk Pro®
Click to expand...
Click to collapse
@OP (original poster) please change the title or delete the thread.
I installed OCLF about 2 weeks ago on my new Froyo install (!!>after reading<!!) and had no problems at all. I used version 1.1 on Eclair and version 2 on Froyo. Ryanza has made a brilliant tool and does not at all deserve to be tainted like this

A ignorant noob like u dont even deserve the help! Uve read? Where?? In every instruction its writte try this at ur own risk.. I had the same problem..Didnt u read abt the 3 button combo?? Z4root and OCLF dont always work well together! AH m very annoyed cuz i really respect Ryan's work!! READ ----- READ----- then again READ--

no point flaming him too much. just report his post

all i can say is LOL

Little nevous so I have to ask.

I am thinking about rooting using unrevoked 3. I am pretty sure that is strait forward. After that I should install titanium back up and do a nand back up? Then after that I should be able to delete the sense apk and htc lock apk screen and it should be stock vanilla 2.2 right. If I want to restore for a OTA can I just use the nand backup?
Then if I want to try flashing Roms what should I do? Is the Rom manager app all I need?

I usually try to ignore these threads but jesus man read a lill first
Sent from space

venom_762 said:
I am thinking about rooting using unrevoked 3. I am pretty sure that is strait forward. After that I should install titanium back up and do a nand back up? Then after that I should be able to delete the sense apk and htc lock apk screen and it should be stock vanilla 2.2 right. If I want to restore for a OTA can I just use the nand backup?
Then if I want to try flashing Roms what should I do? Is the Rom manager app all I need?
Click to expand...
Click to collapse
OK.
First, wrong section. This should be in Q&A whether anyone responds to it there or not.
Second, Titanium doesn't do NAND backups. That's a job for the recovery.
Third, deleting two apks will not make the ROM "vanilla". It will only mess things up and ruin your experience. If you want "vanilla", there are plenty of AOSP ROMs you can flash after you root.
Fourth, you don't do OTAs after you're rooted. It would unroot you, and you'd have to start all over, and there's no guarantee there would be root available for the new OTA. You should just stick to flashing rooted stock ROMs.
Fifth, I would personally advise against ROM Manager and tell you to learn to do it manually. It's not difficult at all, just a matter of learning a specific sequence of simple steps.
I think that about covers everything. I'm sure someone else will fill in the pieces I've missed.

venom_762 said:
I am thinking about rooting using unrevoked 3. I am pretty sure that is strait forward. After that I should install titanium back up and do a nand back up? Then after that I should be able to delete the sense apk and htc lock apk screen and it should be stock vanilla 2.2 right. If I want to restore for a OTA can I just use the nand backup?
Then if I want to try flashing Roms what should I do? Is the Rom manager app all I need?
Click to expand...
Click to collapse
You should probably do some more reading. Titanium back up only backs up apps. If you want a nand back up you do it through recovery. Deleting that stuff does not make it vanilla lol. If you want a vanilla build run a AOSP rom. I don't use Rom manager it crap I flash manually
Sent from my PC36100 using XDA Premium App

Please post your source codes along with the ROM/APP/Development you are doing in this thread.
if not then you realize this is not in the right section. not to be rude but its pretty straight forward with the unrevoked..dont be a ***** and just do it. Otherwise just leave your phone alone.
THIS MIGHT HELP YOU
http://www.xda-developers.com/announcements/a-reminder-from-the-xda-moderator-team/

Google is your friend, learn to use it. Also not trying to scare you, but you could get stuck in bootloops so its better to read everything first then try flashing something.
Your post shows that you are completely clueless, so I really recommend that you read and research before you even attempt to do anything to your device.
Google the following:
1) how to root android
2) how to install custom roms
3) how to use Titanium backup
4) Difference between ASOP and Sense
5) Search in this forum "How to unroot your Evo in two easy steps" if you dont understand or cant follow the instructions there, you may want to reconsider rooting your device. Since if something goes wrong, you will need to unroot the device before taking it to Sprint, etc.
Also dont get offended by these comments because XDA isnt usually like this. But when its very clear that a member hasn't done any research, and expects to be spoonfed all the info, you will get flamed.
How did OP even start this thread in this section? He only has 5 posts... Did the rules change?

wow, my mistake. I'll just stick to Android central.

venom_762 said:
wow, my mistake. I'll just stick to Android central.
Click to expand...
Click to collapse
The reason you got the response you did is because you posted in the wrong section. Whike I know you are new to the forum out is always a good idea you read the stickies on any forum you visit.
Tons of new people make the same mistake.i wouldn't let it turn you of but use it as a learning experience.
Xda is an amazing forum (if you are willing to take the time to search post in correct places and do a little work yourself by researching.)
If you aren't willing to do those things then you will find it a cold unfriendly place.
Fort better or worse it is not always newbie friendly. On the plus most of the major developers are here so once you learn you have tons of resources.
Sent from my PC36100 using Tapatalk

As others have stated previous, irritation arose due to posting in the wrong section (initially) and coming to the table without having first exhausted all resources outside making a new thread (see: Google, searching XDA, other forums, YouTube, even).
There are many guides to help you out there, many on these forums specifically. As one other said previously, as well, don't let this shown irritation from other users discourage you from using these forums. XDA is, by far, the best place regarding the rooting, flashing, development, and customization of our phones. You would be wise to stick around and learn the ropes a bit.
Next time, if you have a question, try posting what you did in the body, explaining what research you have done and what did or didn't work before you decided to post a new thread. This will help others see that you have indeed looked around some and tried some things out instead of rushing to post a new thread without seeing if your question(s) was/were already answered.
Overall, your experience can be very good and you can learn a lot from these forums. I'm still pretty new myself, but I visit these forums every single day and read up on things and just take it all in.
Have fun with everything! If you have any specific questions, feel free to PM me and I'll do my best to help. But do some research before, if you do!

I would suggest reading and asking lots of questions and reading and asking lots of questions and reading and asking lots of questions before doing anything to your phone....
I think all of these responses would make me a little nervous as well...

EndlessDissent -
I have found Rom Manager to be quick and painless, why would you advise against using it?
fyi - I use it w/clockwork recovery instead of Amon-RA. And have downgraded it because of some kind of edify scripting problems. is this less than optimal?

Ok I think I have read all I can and watched all the youtube videos I can handle. It looks pretty strait forward and seems to be easier that the palm pre.
Now can anyone recommend a GB Rom? I would love a pure nexus s expirence. I plan to get it when it comes out.

I would recommend CM7, but some would say no cuz of weird instances that happened to a couple people. Evervolv, Salvage, king's ultra, and miui all have gingerbread though.

venom_762 said:
Ok I think I have read all I can and watched all the youtube videos I can handle. It looks pretty strait forward and seems to be easier that the palm pre.
Now can anyone recommend a GB Rom? I would love a pure nexus s expirence. I plan to get it when it comes out.
Click to expand...
Click to collapse
I second CM7. There are thousands of users, thus lots of potential help. It is a ROM that has been for awhile and they have really worked out quite a good percentage of the bugs that will inevitably come with any GB ROM.
Flash CM7 and get a good feel for it before you start hopping ROMs. Also do yourself a favor and make sure you use the search button liberally before you post questions/issues in the CM7 threads and provide some info on what you did to resolve your issues (you will have issues). If you do that the chances you'll get help rather than flames goes up 10,000%.
I would strongly recommend against MIUI. It is unquestionably the best ROM I have ever used, but it is really not a good ROM for an EVO rookie. The quirks in the flashing process are plentiful and the preciseness required by the nature of the ROM will suit you much better a month from now.
I'm sure there will be people who disagree with me, but I help people everyday who would not have needed help if they had learned a little more about the process on a more basic ROM with lot's of support and fewer bells and whistles. Just my two cents.
The options in teh roxxorz's post are good options as well.

teh roxxorz said:
... miui ... gingerbread...
Click to expand...
Click to collapse
Here I edited teh roxxorz's post to weed out the erroneous stuff and highlight what's important.

Porting Roms from *** To the Evo

I assume this is the correct forum otherwise please move this.
What is the best article(s) to read if you want to start learning how to port roms from other android phones to the Evo? I've been searching on here and on google and it seems most articles are either outdated or only talk about editing existing cooked roms so I finally broke down and posted this. Yes I do use Linux and I do program in Java and .NET and do have a bachelors in software development but I have just never looked into doing this type of work until now.
Thank you, any direction I'm pointed in is appreciated.

I'll direct to you the Q&A forum.

Side Note:This goes in General,but im nice so ill answer you question.
There is no real BOOK to read, a java book is a good start, but you say you know java, so you can probably skip that.
Basically, this is all you have to do.
Download "Dsixda's Kitchen" to your linux distro(amazing software)
Grab a rom from another device.
Grab one of our(evo)stock roms(deodexed Stock 3.70 is good for froyo port,4.12 for gingerbread)
Open the kitchen, and find the option(#19 i think it is), and follow the steps to port it(hold on, your not done yet)
From there you will need do some manual work by tinkering with libs,tinkering with the boot.img, bascally just tinkering with everything related to booting(libs,ramdisk,hw-libs,etc.) untill you can get it to boot or bootloop.
If it boots, thats great, if it bootloops, youlle need to logcat it then debug it.
If you need help with something, pm me, other than that, thats basically(*note: i said basic, more complexed roms like sense 3.0 and non-htc device rom may require extra work)(*note2:alot of times, its going to be a no-booter, but just keep trying.)

sirmx said:
I'll direct to you the Q&A forum.
Click to expand...
Click to collapse
Thanks sirmx, I did do a search there but again came up short.

ThatSmartB0y said:
Side Note:This goes in General,but im nice so ill answer you question.
There is no real BOOK to read, a java book is a good start, but you say you know java, so you can probably skip that.
Basically, this is all you have to do.
Download "Dsixda's Kitchen" to your linux distro(amazing software)
Grab a rom from another device.
Grab one of our(evo)stock roms(deodexed Stock 3.70 is good for froyo port,4.12 for gingerbread)
Open the kitchen, and find the option(#19 i think it is), and follow the steps to port it(hold on, your not done yet)
From there you will need do some manual work by tinkering with libs,tinkering with the boot.img, bascally just tinkering with everything related to booting(libs,ramdisk,hw-libs,etc.) untill you can get it to boot or bootloop.
If it boots, thats great, if it bootloops, youlle need to logcat it then debug it.
If you need help with something, pm me, other than that, thats basically(*note: i said basic, more complexed roms like sense 3.0 and non-htc device rom may require extra work)(*note2:alot of times, its going to be a no-booter, but just keep trying.)
Click to expand...
Click to collapse
Sounds good, what I'll do is go ahead and start one, nothing special maybe even ones that already been done just to get the experience under my best.

ThatSmartB0y said:
Side Note:This goes in General,but im nice so ill answer you question.
There is no real BOOK to read, a java book is a good start, but you say you know java, so you can probably skip that.
Basically, this is all you have to do.
Download "Dsixda's Kitchen" to your linux distro(amazing software)
Grab a rom from another device.
Grab one of our(evo)stock roms(deodexed Stock 3.70 is good for froyo port,4.12 for gingerbread)
Open the kitchen, and find the option(#19 i think it is), and follow the steps to port it(hold on, your not done yet)
From there you will need do some manual work by tinkering with libs,tinkering with the boot.img, bascally just tinkering with everything related to booting(libs,ramdisk,hw-libs,etc.) untill you can get it to boot or bootloop.
If it boots, thats great, if it bootloops, youlle need to logcat it then debug it.
If you need help with something, pm me, other than that, thats basically(*note: i said basic, more complexed roms like sense 3.0 and non-htc device rom may require extra work)(*note2:alot of times, its going to be a no-booter, but just keep trying.)
Click to expand...
Click to collapse
Don't forget some of the most important stuff is in the build.prop and update-script.
Word of advice, look at a sense 2.1 and check out the base that was used. You can also use beyond compare and basically skip Linux all together. Using kitchen to deodex the ruu is a good first step. Choose option 11 in the menu.
Personally, I would start off with a working port and changing apps and moving stuff around. Also get a good list at which libs are associated with what. But use stock bins, etc, xbin, hw libs, and ported apks, framework, and software associated libs. Stock boot.img and a good updater-script. Also know key
Things like the EVO density is 160, vold_stab is usb, amkd is rotation, gsl hw accel stuff like that.
But first things first, Google is ur friend and use the q&a section.
Sent from my PC36100 using Tapatalk

Leoisright said:
Don't forget some of the most important stuff is in the build.prop and update-script.
Word of advice, look at a sense 2.1 and check out the base that was used. You can also use beyond compare and basically skip Linux all together. Using kitchen to deodex the ruu is a good first step. Choose option 11 in the menu.
Personally, I would start off with a working port and changing apps and moving stuff around. Also get a good list at which libs are associated with what. But use stock bins, etc, xbin, hw libs, and ported apks, framework, and software associated libs. Stock boot.img and a good updater-script. Also know key
Things like the EVO density is 160, vold_stab is usb, amkd is rotation, gsl hw accel stuff like that.
But first things first, Google is if friend and use the q&a section.
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
ah yes, forgot about build.prop,and i think the kitchen takes care of updater script(unless the device has specific mount pointsor you want text or to clear cache and system). i was just getting the basics to boot, from ther he can debug the errors out of the log.

What about something A LOT simpler like adding the CRT animations to a ROM? any pointers? Any TUT you can point me to?

ThatSmartB0y said:
ah yes, forgot about build.prop,and i think the kitchen takes care of updater script(unless the device has specific mount pointsor you want text or to clear cache and system). i was just getting the basics to boot, from ther he can debug the errors out of the log.
Click to expand...
Click to collapse
Oh I hear ya. Just throwing in my 2 cents. Found that having a clean updater-script is half the battle.
Sent from my PC36100 using Tapatalk

I'm actually glad this thread is still here we don't get to learn much from the devs here. I mean its mostly do it yourself but a getting started guide isn't a bad thing. Mods are quick to move and people are quick to flame but I say leave it, where else is the knowledge pool? Can you really learn this stuff in Q and A seems like it would be mostly help my phone doesn't boot...
Sent from my PC36100 using XDA App

Check out the APKTool, APKManager threads. Lots of great valuable information in there.
I sometimes wish XDA focused more on the "HOW TO" and less on the delivery aspect. The more folks developing, the further we will be along
Another great way to get started is to mentor with another established developer.

evomattnc said:
I'm actually glad this thread is still here we don't get to learn much from the devs here. I mean its mostly do it yourself but a getting started guide isn't a bad thing. Mods are quick to move and people are quick to flame but I say leave it, where else is the knowledge pool? Can you really learn this stuff in Q and A seems like it would be mostly help my phone doesn't boot...
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Well said. People love to flame anyways and XDA is famous among other Android forums for being so harsh. This thread helped me out big time, and it's especially nice to see Leoisright and myn in here giving up a few pointers, because I too was curious about porting. I never worked up the confidence to ask, just too worried about it being passed over or getting flamed because I'm young and curious.
Sent from my PC36100 using XDA App

Yah, Q&A never got me anywhere, i learned off of trial and error, still learning now.
EDIT:OP:IF you want you can ombine mine and leo's tuts together, to make this thread permanent.

Subscribed!!!!!!!!
Good stuff!
Sent from my PC36100 using Tapatalk

Yeah I want to thank the devs that have stopped by so far and gave tips, already using them . Hopefully most of them drop In at least once and leave one tid bit that would make this thread awesome!
Sent from my PC36100 using XDA App

Ha, you taking applications for an apprentice myn?
myn said:
Check out the APKTool, APKManager threads. Lots of great valuable information in there.
I sometimes wish XDA focused more on the "HOW TO" and less on the delivery aspect. The more folks developing, the further we will be along
Another great way to get started is to mentor with another established developer.
Click to expand...
Click to collapse
Sent from my PC36100 using XDA App

Yes I was afraid to post this at first which isn't good, you shouldn't be afraid to ask questions but I get that sometimes the same questions have been answered 100 times prior so I understand the quick to judge portion of it. But I want to thank everyone who has contributed tips, advise and places to start. Thank you.

Leoisright said:
Don't forget some of the most important stuff is in the build.prop and update-script.
Word of advice, look at a sense 2.1 and check out the base that was used. You can also use beyond compare and basically skip Linux all together. Using kitchen to deodex the ruu is a good first step. Choose option 11 in the menu.
Personally, I would start off with a working port and changing apps and moving stuff around. Also get a good list at which libs are associated with what. But use stock bins, etc, xbin, hw libs, and ported apks, framework, and software associated libs. Stock boot.img and a good updater-script. Also know key
Things like the EVO density is 160, vold_stab is usb, amkd is rotation, gsl hw accel stuff like that.
But first things first, Google is ur friend and use the q&a section.
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
So I've been looking at beyond compare, did you use this from everything and just edit all the non evo files to match existing evo ones from within windows?

[Q] Root issue

I installed eclipse 4.1.1, it has superuser in it. Tibu works, but when I try to use trickster mod, it says I don't have root access. I used root checker, and sure enough it says I don't have root access on my phone. What's going on with that? What can I do?

I'm not sure of the technicalities causing your issues.
But I can recommend flashing SuperSU in ClockworkMod after installing TricksterMod. Also make a backup beforehand.
Sent from my Galaxy Nexus using Tapatalk 2

Just tried that, didn't work. I don't understand how I don't have root access but one app that required it works and another doesn't.

tried to re-root the phone using the nexus toolkit, no go either. tibu still works but not trickster.

dont use a toolkit. srsly, since you dont know what the hell you're doing.
Sent from my i9250

Thanks, that was real helpful.

Try updating the su binaries from super su app... That's worked for me before. If that doesn't work try flashing an updated rom since they all have su built in.
Sent from my Galaxy Nexus using Tapatalk 2

Tried that too.ended up going to baked black bean ROM.thanks for the input.

bk201doesntexist said:
dont use a toolkit. srsly, since you dont know what the hell you're doing.
Sent from my i9250
Click to expand...
Click to collapse
There's no need to be rude to him. We've all been new at this at some point.
Sent from my Galaxy Nexus using Tapatalk 2

Thank warner. I don't know why some people think if you own a certain phone you should know right away how to do everything the "right" way. If you shouldn't use the toolkit, then take it off the forum. Otherwise people are going to use it like me.

t1.8matt said:
Thank warner. I don't know why some people think if you own a certain phone you should know right away how to do everything the "right" way. If you shouldn't use the toolkit, then take it off the forum. Otherwise people are going to use it like me.
Click to expand...
Click to collapse
just because you find a tool on the table doesn't mean you should take an engine apart without any knowledge before hand.
Some things to search before rooting:
1. What does "root" mean and what does it change?
2. Why do I 'need' root?
3. Differences between soft and hard bricks and how to recover from them.
4. What is and how to use ADB.
5. an extra but, if you were to make this phone unrecoverable or unusable for a degree of time, is this a possibility you can accept? (i ask this because ive worked with those that brick their phone they use for work and then they rush through trying to fix it and make it worse).
We aren't trying to be mean or chase away new users, it's always a great thing when people learn to use their phones. The only thing that can cause bitterness is when users buy a phone and come home and root it because they heard thats what you do with android phones and how to get cool stuff or free apps. Im not saying that is you, likely it isn't from what i've read.
Bottom line, read and learn as much as you can because there is no such thing as too much knowledge. There is nothing more satisfying than figuring out the problem yourself and fixing it instead of 'calling tech support for help' on xda.

I do understand what you're saying. I'm not trying to come off as cocky or I know it all but I have been doing these things with android for a while and do understand how some things work and how to do them. This whole unlocked phone is new to me, and I've never been completely comfortable or able to use fast boot methods which I know is the right way to do most things. I try to learn things about these phones on a daily basis which is why I ask questions and try new things all the time. I appreciate what you have said and am trying to learn how to do things properly, this is just new to me and I appreciate people who have patience to help people like me out.

Darunion said:
just because you find a tool on the table doesn't mean you should take an engine apart without any knowledge before hand.
Some things to search before rooting:
1. What does "root" mean and what does it change?
2. Why do I 'need' root?
3. Differences between soft and hard bricks and how to recover from them.
4. What is and how to use ADB.
5. an extra but, if you were to make this phone unrecoverable or unusable for a degree of time, is this a possibility you can accept? (i ask this because ive worked with those that brick their phone they use for work and then they rush through trying to fix it and make it worse).
We aren't trying to be mean or chase away new users, it's always a great thing when people learn to use their phones. The only thing that can cause bitterness is when users buy a phone and come home and root it because they heard thats what you do with android phones and how to get cool stuff or free apps. Im not saying that is you, likely it isn't from what i've read.
Bottom line, read and learn as much as you can because there is no such thing as too much knowledge. There is nothing more satisfying than figuring out the problem yourself and fixing it instead of 'calling tech support for help' on xda.
Click to expand...
Click to collapse
I do agree that learning as much as we can and being able to fix a problem ourselves without asking for help is extremely satisfying. At the same time though this is the q&a forum and he did try to fix the problem himself through the use of a toolkit, which I agree cuts out a lot of the learning that can be achieved through using fastboot and adb. I think in this forum especially it is better to try to help and make constructive comments than to be rude and post a reply that doesn't help and could possibly chase off a newcomer to modding their device. I appreciate your comment though trying to explain the benefits of learning yourself in a respectful way.
Sent from my Galaxy Nexus using Tapatalk 2

Exactly. I'm not asking anyone to come to my house and fix my phone. But it helps when someone explains what I'm doing wrong and how I can fix my errors in what I'm doing. Thanks for your help everyone who did but I'm going to move on and learn from this experience.

Yes it's a Q&A, but this is a question that asked a lot.
A little bit of reading tell you how to use the forum properly, and you probably find the answer already solved.
Toolkits have there place & for newbies i guess it's the fastest way to get it done, but if you read through the Q's you will find most rooting issues are related to the use of toolkits. Great if they work, but as soon as there is an issue, users are left in the situation you are in now.
efrant & jubakuba have guides in the Q&A section on unlocking, rooting and installing roms with the use of fastboot/adb, all the commands are given.
Good luck

If root is not working as it should, just re-flash the superuser package again. See here.
It's likely an issue with out-dated files or with permissions.

if you use a toolkit, you're on your own - since neither you or us know what happened. it's your fault, for rushing things.
google won't help you either. that's why we say things like that.

Ok, got it. Thanks. Bye.

t1.8matt said:
Ok, got it. Thanks. Bye.
Click to expand...
Click to collapse
Hey I'm a seasoned user here and I'm having the exact same problem with Trickster Mod... you fanboys need to kick it back a notch and try to help someone once in awhile.

Thanks for the info. For now I moved on to Epic V5, maybe when Nitro comes out with the 16 update I'll try it again, cause I really do like that dark eclipse Rom.

[Q] SuperSU on TW4.3

SuperSU on TW ROMs running 4.3 (regardless of version, source of version and how you got it) is frustrating. Apps that need root do sometimes able to get root access, and most often than not wont' be able to.
YES !!! I have done more of my share of reading. And please do NOT treat users with less than 10 posts like idiots.
*** The only solution is to change between Default Access modes. Going from grant, to prompt. Doing so for some strange reasons wakes up SuperSU***
The following solutions DO NOT WORK (meaning the problem resists)
1. Flash Antenna (regardless of which, even with the one provided by OP on their threads)
2. Flash insecure kernel zip
3. Download the version form Play and Update
Hope this help any of you that are experiencing some crazy frustrations like me.
*** Not to offend anyone, but the rule of 10 post or less = No reply/post on dev. forum is beyond me ***
*** I have tried to report my experience with certain ROMs, but Nooooooooooo.... <10 amigo ***
--- One more, since I think I am going be booted because of offending Seniors Party Members. ---
Can anyone tell me the logic of formatting a partition 3 times ??? I found this ridiculously offending being an engineer myself.
I do appreciate every single one of the developers who spends countless hours to make the word "FREE" as free as possible.

@mrbackdoor
Whoa Cool down Bro. Take a deep breath. Now tell me what precise are your problems ? I got the part with SuperSU making you go Ape. But what's with Roms and 10 Wipes ? I have no Idea what you are getting at.
So about SuperSU. If that app is making you go nuts, why don't you try SuperUser by @ChainsDD ? There's also a great Superuser app from CM team. But without knowing your Rom, I won't recommend it.
Do Kindly note, some Root apps are not compatible with 4.3. So you may get weird errors. Others like Nandroid Manager have their own limitations on Root access.
P.S. - Your Current Post Count is 1. I did respond right ?

LOL... thanks man. I am positively NOT HOT
what's with Roms
>>> TW 4.3 ATT leak on Tmobile LTElessS3
>>> I was just venting the fact that a member CAN NOT post on Development Forums because he/she has less than 10 posts.
>>> That's like filling 10 forms before you are able to download a file. Similar to registration process that just drive you nut.
>>> One engineering note is wiping a partition 3 times. The wipe process before installing a new ROM.
>>> I just don't get it... Why 3 ??? "insanity according to Albert Einstein"
Superuser..But without knowing your Rom, I won't recommend it.
>>>Superuser - NOT an option, not even working
Do Kindly note, some Root apps are not compatible with 4.3. So you may get weird errors. Others like Nandroid Manager have their own limitations on Root access.
>>> YES sir. Fully understood
P.S. - Your Current Post Count is 1. I did respond right ?
>>> call me up when you want a beer... or couple shots of the good sh****

@mrbackdoor
I don't have the ATT S3 Let alone the leaked Rom so can't comment. I hate TouchWiz anyway. I don't want to comment on the rules. They are there for a reason. Yes they may be an irritant but they keep Noobs away. You my dear friend is a Newb. There's a difference.
Whoever asked you to wipe the same partition 3 times needs to get their head examined. But then I am jumping ahead without knowing full circumstances. So if you don't mind, show me the thread link.
Are you trying to get the Leaked ATT Rom with a working Root ?
Now you too sir, have been guilty as well. I need to have full problem statement, which I am sorry I have not got as yet. So can you kindly explain what precisely are you trying to do and where does SuperSU come into play ?

Ok, first, please don't assume we are all jerks who are going to belittle you or treat you horribly and then ban you from OUR playground. I personally felt it a little insulting that your first post, coming to us for help, was so defensive and presumptuous.
Yes, we want you to do as much on your own as you can. No, most of us do not consider a low post count an indicator of idiocy. We might, however, judge how much we want to help depending on the quality of your post, or any other OP by anyone. If you do your best to find your own answers, and post clearly and respectfully, it'll show.
And there absolutely are reasons for all the rules here, and no one wants to hear anyone complain about them. (And if you haven't actually read them, please do so). The 10 post rule is to prevent spammers and bots from being able to post in the most important sections. And it's just 10 posts...see you're already on your way!
So if you'd care to try starting over on a better note, here are my points regarding your issues.
There is no real benefit to formatting something more than once. This is something that apparently began with some old device where the recovery wouldn't always format correctly. So people got in the habit of wiping several times rather than the king after each time. They then spread out across xda and push this practice like gospel sometimes, even though it gives no benefit and imo shortens the life of the device. I have tried to point out to folks this is not necessary, but gave up long ago! To each his own.
Enewman found a bit of a workaround for the su issues. It's not perfect but does seem to help a little.
Find these files
/etc/install-recovery.sh
/etc/init.d/dameonsu (or similar named script)
Find this line
/system/xbin/daemonsu --auto-daemon &
Delete --auto
Reboot
Hopefully that helps. And fyi, I'm going by memory, but am pretty sure I've been fairly accurate.
But also keep in mind that it's a combo of things, you do also need the insecure kernel. And Knox is still gonna screw with it if it's not been removed.
Also, try to remember, all of this stuff is brand new to all of us. Do not expect miracles, it takes time to relearn everything for everyone. But if it's really that bad, then consider going back to an older Rom for now.
These are after all leaked builds and should not be expected to be fully functional and bug free.
Sent from my SGH-T999 using Tapatalk

Dr. and Perseus
To you both, thank you, thank you and thank you. It would have been more appropriate on the General thread. Anyhow:
Perseus
If needed, I can point you to the threads. You are kind. I do appreciate that.
Dr.
I think you know exactly what I was talking about. So to you I do apology if my post is offended. In fact, to anyone who do feel the same. My bad.
please don't assume we are all jerks who are going to belittle you or treat you horribly and then ban you from OUR playground. I personally felt it a little insulting that your first post, coming to us for help, was so defensive and presumptuous.
>>>No Sir, no way in any shapes or forms I do assume people are jerks. Like I stated before, I was just venting on the fact that the rule cripples members ability to contribute and alienates them as well.
And there absolutely are reasons for all the rules here, and no one wants to hear anyone complain about them. (And if you haven't actually read them, please do so). The 10 post rule is to prevent spammers and bots from being able to post in the most important sections. And it's just 10 posts...see you're already on your way!
>>> Understood. Complain is absolutely not my thing. If there is a way to monitor users' footprints, you will find out that I have been here for a while, and it just not my style to complain or ask unless I have read just about anything posted.
So if you'd care to try starting over on a better note, here are my points regarding your issues.
>>> Of course.
There is no real benefit to formatting something more than once.
>>> Got it. Now's that is at the core. That's exactly what I was looking for. Instead banging my head trying to understand how partitions are being formatted and the file system that is basically associated to the NIX for a long time . Basically what I posted is the workaround that I use for now.
Hopefully that helps. And fyi, I'm going by memory, but am pretty sure I've been fairly accurate.
>>> Correct.
But also keep in mind that it's a combo of things, you do also need the insecure kernel.
>>> Appreciate your time Dr.
Statement below is my initial love your developers. That has not changed. Just "kang" members that I do find .... well.... you got my drift.
"I do appreciate every single one of the developers who spends countless hours to make the word "FREE" as free as possible."
Whenever you two do find your way to America Finest City... ring me up. A few rounds on me, if not all.
Again, thanks.

mrbackdoor said:
you will find out that I have been here for a while, and it just not my style to complain or ask unless I have read just about anything posted.
Whenever you two do find your way to America Finest City... ring me up. A few rounds on me, if not all.
Click to expand...
Click to collapse
Actually your join date of May '11 is the first thing I noticed. Pretty big time Reading on your part if you didn't ask before.
I am afraid we are still missing the problem you posted for aren't we ? Or what steps Doc suggested about the leak solved your problem ?

I'm on the app most of the time, so I can't readily see post counts, join dates, junior/senior member status, etc. But anyway, thanks for the reply op. I lurked around the forums for about a year before my first post, reading and learning all I could, so I can appreciate that you seem to have done so as well!
I was slightly off earlier, when you find those files, change this:
/system/xbin/daemonsu --auto-daemon &
To this:
/system/xbin/daemonsu --daemon &
Had to go look it up again. Sorry bout that!
@Perseus71
I'm pretty sure his main issue was that root wouldn't always work. After a little while sometimes root apps will lose their root access, which can be annoying, obviously! Some have just resorted to opening and closing the app a bunch of times till it regained root.
If I'm not mistaken it's due to seLinux blocking root. And by removing auto from the script, it forces the daemon to run persistently, as opposed to just when it's called, thereby helping to retain root access.
Another workaround I read somewhere was to tell SuperSU to ignore the apps permissions, or something like that. Not positive on what they meant right now, I'll have to try and find it again to be sure.
The other part of this is the insecure kernel. This will set seLinux status from enforcing to permissive. You may have to reboot or even reflash the kernel if it doesn't change from what I hear. I've not seen this myself though.
And then there's Knox. If it's not removed it can also cause problems with root access.
Sent from my SGH-T999 using Tapatalk

DocHoliday77 said:
@Perseus71
I'm pretty sure his main issue was that root wouldn't always work. After a little while sometimes root apps will lose their root access, which can be annoying, obviously! Some have just resorted to opening and closing the app a bunch of times till it regained root.
If I'm not mistaken it's due to seLinux blocking root. And by removing auto from the script, it forces the daemon to run persistently, as opposed to just when it's called, thereby helping to retain root access.
Another workaround I read somewhere was to tell SuperSU to ignore the apps permissions, or something like that. Not positive on what they meant right now, I'll have to try and find it again to be sure.
The other part of this is the insecure kernel. This will set seLinux status from enforcing to permissive. You may have to reboot or even reflash the kernel if it doesn't change from what I hear. I've not seen this myself though.
And then there's Knox. If it's not removed it can also cause problems with root access.
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
Oh I see. Honestly on my 4.3.1 rom that I had, I never experienced this problem. Possible its related to the leaked Rom's implementation of SELINUX?

I have got no idea at all what you are so angry about, if it's kangers like myself well we never claimed to be true developers. The developers do they developing, and we do modifications to make things how we want them and hopefully others enjoy it too, that's all.
To OP, we're aware this SuperSU problem was annoying, we were one of the first few dealing with non-stop before bringing the leak from AT&T and debloating it over here.
enewman17 and his infinite knowledge did some poking around in the files and found a way to make root more persistent, albeit this is a leak, and we have Samsung KNOXing at our door. Things are bound to be broken, and especially because myself and others working on the leak are not professional Android developers nor do we ever claim to be, more like hobbyists who try to learn on their own by reading, or their own personal knowledge of NIX' and shell scripting.
Rest assured, we're all doing what we can to find workarounds, and make the transition from 4.1.2 to 4.3 as painless as possible because believe me, it is painful. The SDcard structure lining up with the AOSP file structure change from 4.2+, KNOX, SELinux, things just got a bit harder.

All
Dr. has it right about the issue (I'm pretty sure his main issue was that root wouldn't always work.). I can work around it. No biggie. Will try the recommended method.
I have got no idea at all what you are so angry about, if it's kangers like myself well we never claimed to be true developers.
>>> Sir, I am not angry. I did explained couple times on previous posts. I just find certain rules and their enforcers hinder members' contributions. Whether that is just saying thanks or report something back. .The process in my opinion alienates the excitement of new members who are willing to do what it takes in hope to return something back. And so I did vent about it, Probably on the wrong forum. And I did apologize. If you want we can table this offline to show you what I meant.
nor do we ever claim to be
>>> Nor did I
Rest assured, we're all doing what we can to find workarounds, and make the transition from 4.1.2 to 4.3 as painless as possible because believe me, it is painful. The SDcard structure lining up with the AOSP file structure change from 4.2+, KNOX, SELinux, things just got a bit harder
>>> I wouldn't doubt you. I've seen your work.
>>> The point is not about developers, contributors, members. Just rules and the re-reinforcement. I personally believe any voice is constructive and beneficial. I am not a NIX person, but I do find the creation of the linux kernel and its distributions since then fascinating. Awesome technologies have been built due to the collaboration of community sharing and giving back. I am almost certain xda was also created on the same principle.

mrbackdoor said:
All
Dr. has it right about the issue (I'm pretty sure his main issue was that root wouldn't always work.). I can work around it. No biggie. Will try the recommended method.
I have got no idea at all what you are so angry about, if it's kangers like myself well we never claimed to be true developers.
>>> Sir, I am not angry. I did explained couple times on previous posts. I just find certain rules and their enforcers hinder members' contributions. Whether that is just saying thanks or report something back. .The process in my opinion alienates the excitement of new members who are willing to do what it takes in hope to return something back. And so I did vent about it, Probably on the wrong forum. And I did apologize. If you want we can table this offline to show you what I meant.
nor do we ever claim to be
>>> Nor did I
Rest assured, we're all doing what we can to find workarounds, and make the transition from 4.1.2 to 4.3 as painless as possible because believe me, it is painful. The SDcard structure lining up with the AOSP file structure change from 4.2+, KNOX, SELinux, things just got a bit harder
>>> I wouldn't doubt you. I've seen your work.
>>> The point is not about developers, contributors, members. Just rules and the re-reinforcement. I personally believe any voice is constructive and beneficial. I am not a NIX person, but I do find the creation of the linux kernel and its distributions since then fascinating. Awesome technologies have been built due to the collaboration of community sharing and giving back. I am almost certain xda was also created on the same principle.
Click to expand...
Click to collapse
Glad to know we could be of assistance. Glad to clear that up with you. Feel free to post more, don't be such a lurker!